actual test

actual test

Router-id 1.1.1.1 R2-PE1#show mpls forwarding-table detail Uptime: 12 seconds Prefix Et0/1 [Note] If the router receives a tagged packet and the top tag cannot be found in the local LFIB , the CISCO IOS will discard it. Bgp router-id 5.5.5.5 After receiving the label from the tail router, the penultimate hop router uses the label as the outbound label of the TE tunnel , and assigns a label to the tunnel and places the label in the label object in the RESV message. Send it to its own upstream router. The authenticated TLV is not seen in the PSNP message . Mpls traffic-eng tunnels ip rsvp bandwidth RFC1195 TLV 22 : Extended intermediate-System Reachability Indicates whether the LSP is from L1 router or L2 router . This field is 2bits . 00- not used; 01-level1 ; 10- unused; 11-level2 ! Note: LDP or TDP only generates labels for routing entries of the IGP protocol, and does not generate labels for BGP routing entries. Mpls traffic-eng tunnels ip rsvp bandwidth Removal Trigger: re-route path verification failed i L1 AFI+IDI is used to identify the Domain Record Route: By default, CISCO IOS does not trigger re-optimization when a link in the network can be reused by a TE tunnel , but can activate this operation. To enable re-optimization when a link becomes operational in MPLS TE , use the following command: 10.1.12.2 4.4.4.4/32 DIS Src 1.1.1.1, Dst 4.4.4.4, Tun_Id 0, Tun_Instance 2 RSVP Path Info: View message *Aug 18 09:06:07.919: parameter id=127, flags=0, parameter length=5 R3.02-00 If you change the Path-selection metric to igp , the shortest path to the tunnel will ignore the configuration in the physical interface. Both data packets have the same format and each carry a collection of LSP summary information. The difference is that the CSNP carries summary information of all known LSPs in the link state database of the router , and the PSNP carries one of the subsets. To distinguish Level-1 , Level-2 link state database, the router generates Ll , L2 of independent SNP packets. Remaing lifetime LSP lifetime before LSP ID LSP identity Sequence num LSP serial number ---------- If the router performing load balancing is the inbound LSR of the IP packet , then it is easy to know that the received IP packet is IPv4. Intermediate LSRs - Intermediate LSRs receive an incoming labeled packet, perform an operation on it, switch the packet, and send the packet on the correct data link. Local binding: tag: 101 LSP flooding diffusion and synchronization IP interface address Create a TE tunnel on R1 . The source is its own loopback0 . The destination is 5.5.5.5 for R5 . ! State: Oper; Msgs sent/rcvd: 13/13; Downstream Up time: 00:04:05 Verify view [115/10] via 10.1.123.2, FastEthernet0/0 Priority 7 : 9375000 Keep priority Network 10.1.23.2 0.0.0.0 area 0 mpls traffic-eng router-id loopback0 mpls traffic-eng area 0 10.1.123.0 is directly connected, FastEthernet0/0 0.0.0.0/0 [115/10] via 10.1.123.3, FastEthernet0/0 Label space (the Label Space) : based platform (Per-Platform) The configuration of R3 is as follows: 558 We see that R1 has learned to 2.2.2.0 , 3.3.3.3.0 and 10.1.24.0 , 10.1.34.0 . Network 5.5.5.5 0.0.0.0 area 0 3 10.1.23.2 [MPLS: Label 203 Exp 0] 964 msec 1124 msec 1008 msec Mpls traffic-eng router-id loopback0 mpls traffic-eng area 0 Mpls traffic-eng router-id loopback0 mpls traffic-eng area 0 Explicit Route: 10.1.12.2 10.1.23.2 10.1.23.3 10.1.34.3 Flooding Status: ready !!! When there is a problem with the path of R1-R2-R5 , for example , the link between R2-R5 is DOWN , then the TE tunnel will switch to the path-option of the next priority , that is, the dynamic setting mode. Therefore, it will switch to R1-R3-R4-R5 . Fa0/0 Focus on the 2.2.2.2/32 entry. The current outgoing label is pop , which is an empty label. Mpls traffic-eng router-id Loopback0 mpls traffic-eng area 0 RFC 3373 Area Address: 49.0001 0x8973 4 10.1.45.5 0 msec Next-address loose 10.1.34.4 0x2D6E Mpls traffic-eng tunnels mpls ip SystemID : The systemID of the IS that generated the hello (some books have a SourceID , synonymous) Then, if you are in the tunnel port on R1 , use the following configuration: Path option 10, type dynamic (Basis for Setup, path weight 30) Ip explicit-path name R2R3R4 enable next-address 10.1.12.2 0 kbits/sec Removal Trigger: configuration changed The load of the routing processor is low in large areas LSP Seq Num Interface eth 0/1 1.1.1.1/32 The configuration of R2-PE1 is as follows: Version=0 length in words=10 Ip address 10.1.45.5 255.255.255.0 bibliography First of all, these three commands all work on the route obtained by the route calculated by the TE tunnel with the autoroute feature enabled . The above command changes the cost of the tunnel interface itself . Load balancing of label packets Router(config)#mpls traffic-eng reoptimize timers frequency ? 10.1.12.2 The unreservable bandwidth is the bandwidth remaining after being supplied to the TE , that is, the maximum bandwidth of the link minus the bandwidth currently reserved by the TE tunnel. Status Router# mpls traffic-eng reoptimize Router , thus maintaining two independent L1 link state databases and L2 link state databases. Then, if there is a router in the backbone that is not connected to the L1 router , it can be configured as an L2 router . Interface Ethernet0/0 Mpls traffic-eng tunnels ip rsvp bandwidth ! R1#traceroute 55.55.55.55 We see that in the LFIB of R3 , going to the destination of 1.1.1.1 , there are two label paths for load balancing. R1 has already completed the collection of its own TEDB information, and the calculation process of the tunnel path is completed on R1 . Sender_Tspec This TLV by L2 router establishes a virtual link through a backbone network between Path: valid Mpls traffic-eng tunnels mpls label range 200 299 Network 10.1.34.3 0.0.0.0 area 0 ! Tspec: ave rate=2000 kbits, burst=1000 bytes, peak rate=2000 kbits RSVP Resv Info: Overview of the label assignment process Hello data unit: sent periodically to determine whether other ISs are running IS-IS , establish adjacencies, exchange LSPs , and synchronize LSDBs . OSPF , this is not the same as other IGP protocols. Therefore, if you want to make the routing full, you need to add a re-release directly to R3 . The configuration of R3 is as follows: Interface Loopback0 The bandwidth information that MPLS TE needs to advertise is: 0 kbits/sec Interface eth 0/1 Periodic update. 20. 5.5.5.5 In interface configuration mode: isis circuit-type allows the interface to work at level-1 level-1-2 or level-2-only Ip router isis encapsulation frame-relay *Aug 18 04:37:06.239: version:1 flags:0000 cksum:7B25 ttl:255 reserved:0 length:132 The re-addressing process is similar to zone merging and separation, except that during re-addressing, some or all of the router's zone prefixes need to be cleared, with new ones. ! L1 (inside the area) and L2 (in the area) For IS-IS LSP messages and CSNP and PSNP, see the IS-IS Link State Database chapter. [115/20] via 10.1.24.2, Serial0/0 L2 rouer redistributes external routes into IS-IS The configuration of R1 is as follows: Indicates whether the LSP is from L1 router or L2 router . This field is 2bits . 00- not used; 01-level1 ; 10- unused; 11-level2 The unit is Bytes , multiplied by 8 is 100Mbps Link type supported by IS-IS The RESVTear message is similar to the RESV except that it is sent when the tail router responds to the received PathTear message. Each IP packet forwarded to a router is the same before and after being forwarded through the router. Small to check if the MTU of both parties matches Record Route: NONE Version/ Protocol ID extension: Value is 1 Fspec: ave rate=60000 kbits, burst=1000 bytes, peak rate=60000 kbits RSVP We have to change the topology: R2#show ip route R2.02 BW (kbps) Name: R1_t0 (Tunnel0) Destination: 4.4.4.4 Status: Tunnel mpls traffic-eng path-option 10 dynamic Interface loopback0 Since the IP packet destined for 6.6.6.6 is sent to R2 , the IP packet is pushed into the VPN label 505 under the inner layer , which is no problem. Then we continue, the VPNv4 route on 6.6.6.6 on R2 is passed by 5.5.5.5,actual test, which is R5 . MAX.Areas maximum area address. Indicates how many different zone prefixes we can configure for a router. value R2.02 Fa0/0 *Aug 18 09:06:07.919: Token bucket fragment (service_id=1, length=6 words LDP neighbor discovery AutoRoute: disabled LockDown: disabled Loadshare: 0 bw-based auto-bw: disabled * 0x00000013 Network 2.2.2.2 0.0.0.0 area 0 If there are multiple network Tunnel for different traffic services, it is possible that these tunnel importance of their degree of importance also vary depending on the influence of the actual business needs. Then if I configure a more important tunnel after a more minor tunnel , it may lead to the more important tunnel that cannot find an optimized or sufficient bandwidth path. We can avoid the above problem by tunnel priority .