ccna logo

ccna logo

Ip vrf VPN-A rd 2345:6 204 Pop Label 5.5.5.5/32 0 Tu0 point2point MAC/Encaps=14/18, MRU=1500, Label Stack{304}, via Et0/1 0E00003017000E00003016108847 00130000 The routing table of R2 is as follows (omit direct route): Eventually this tagged package with 403 and 505 is sent to the TE Tunnel , so: *Aug 18 09:06:02.699: 10.1.12.2 (Strict IPv4 Prefix, 8 bytes, /32) LDP is in Frame Mode . The LSR assigns a label to each route. The local direct route is assigned a POP. 103 *Aug 18 09:06:02.699: Flags: (0x7) Local Prot desired, Label Recording, SE Style !! Flags are reflected in the flag 10.1.23.2 *Aug 18 09:06:07.919: peak rate =250000 bytes/sec Ip address 3.3.3.3 255.255.255.255 Error metric See that no R1 will adjust the cost of the direct link 10.1.12.0 to 65545 . Ip unnumbered Loopback0 Priority 5 : 9375000 Admin: up !! Re-release the local direct loopback 2.2.2.0/24 to level1 Match ip address prefix-list test router isis The SWAP process is well understood. Note that the LSR only processes the top label when it processes the tag data for multiple tags in the tag stack. therefore General Parameters break bit=0 service length=8 If the payload of the MPLS is not an IPv4 packet or an IPv6 packet, load balancing is performed by viewing the value of the bottom label. Bytes tag Outgoing Next Hop Use the lockdown keyword (note that the above configuration is configured in the TE tunnel port). Area-password cisco 2.2.2.2/32 lab environment ISO 9542 Admin: up Oper: up Path: valid Signalling: connected path option 10,ccna logo, type explicit R2R4R5 (Basis for Setup, path weight 30) Ip cef Label_request Ip cef 3.3.3.3 For a router that supports IPv6 , the algorithm for performing load balancing on MPLS packets is as follows: At this time, R2 goes to 55.55.55.55 , and the traditional IP data is taken instead of the LSP . Local binding: tag: imp-null ! Equivalent load balancing in CEF R1#show isis da R1.00-00 detail Support IP classless routing prefix (support VLSM ) Current LSP: Circuit circuit Ip vrf VPN-A rd 2345:6 After the above configuration, we will find, R1 can learn to R2 , R3 route, but R2 , R3 between can not learn the route to the peer. 75000 Router(config)# mpls ldp advertise-labels [for prefix-access-list [to peer-access-list ] ] !! Activate the autoroute feature of the tunnel ! 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. Next Hop We see that due to the updated LSA in R2 , the metric is set to 65535 for the directly connected network segment 10.1.12.0/24 . Therefore, in the routing table of R3 , we see 1.1.1.1/32 and 10.1. The 12.0/24 routing metrics are both bizarre. Look again at the Type 1 LSA produced by R2 : Neighbor 10.1.24.4 remote-as 45 no auto-summary *Aug 18 04:37:06.239: Tun Dest: 5.5.5.5 Tun ID: 0 Ext Tun ID: 1.1.1.1 i L2 1.1.1.0 [115/30] via 10.1.34.3, Serial0/1 *Aug 18 04:37:06.239: SESSION type 7 length 16: End system adjacency routing *Aug 18 09:06:07.919: peak rate =250000 bytes/sec Router(config)#mpls traffic-eng reoptimize timers frequency ? AFI+IDI is used to identify the Domain 200 Net 49.0001.0000.0000.0002.00 16 0180-C200-0015 Summarize on the L2 router , summarize the locally originated routes, configure as above Interface eth0/1 75000 Is-type level-2-only !! R4 is L2 router , so modify the is-type type to level2-only Tunnel mpls traffic-eng autoroute metric absolute 32 Router ospf 1 *Aug 18 04:37:06.239: HOP type 1 length 12: The metric is 31. The calculation method is of course very simple, as follows: When the forwarding adjacency feature is used, the tunnel end and the end must be in the same area, and the tunnel interfaces at both ends must be configured. That is, this must be a bidirectional tunnel, and both tunnel interfaces must activate forwarding adjacency. The way to use static routing is of course the easiest, and the best control, but the scalability is too poor, if there are multiple tunnels, then configuration and maintenance is more troublesome. That is the CEF table 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 . 2.0.0.0/32 is subnetted, 1 subnets AutoRoute: enabled auto-bw: disabled LOOP Detection 200 Et0/1: 403 - Event caused reoptimize Ip vrf forwarding VPN-A RFC1195 Thus, as long as 5.5.5.0 in R2 , then the routing table of R2 will, in its region to 49.0001 in flooding- LSP for the ATT is set, we can try to R5 of Loopback the shutdown , so 5.5.5.0 hung , and when R2 is detected this change, not found in the routing table 5.5.5.0/24 route, then R2 will trigger a LSP updates the LSP in the ATT not set, so a to R1 will only produce a Point to the default route for R3 . When 5.5.5.0 is restored, then R2 will generate an LSP and set ATT again (this 5.5.5.0The route does not have to be an ISIS route. You can play it with a route pointing to null0 , and set the ATT .) One thing to note here are: tools used to match the recommended route prefix list, I was in 12.