ccna guide

ccna guide

0/0/0 ! Ip address 3.3.3.3 255.255.255.0 ip router isis First of all, all routers run routing protocols, and the entire network is interoperable. Next,ccna guide, LDP is activated on the interface of the router, and an LDP adjacency relationship is formed between the two routers . Complete basic IP configuration (configuration omitted) Mpls traffic-eng router-id loopback0 mpls traffic-eng area 0 Headend frr information: Protected tunnel i L2 2.2.2.0 [115/20] via 10.1.24.2, Serial0/0 RESV State: explicit path option 10 is active LDP discovery sources: Mpls traffic-eng router-id loopback0 mpls traffic-eng area 0 *Aug 18 04:37:06.243: Hop Addr: 10.1.12.2 LIH: 0x02000403 PATH Set-attached-bit route-map test Then you need the top-level tag, which looks at the next hop. The next hop is 5.5.5.5 , so be sure to find the 5.5.5.5 tag. As we have seen from the routing table, at this point R2 goes to 5.5.5.5 and actually enters the TE tunnel , then: Router(config)# mpls ldp session protection for acl-peer duration sencondes 4.4.4.4/32, version 12, epoch 0, cached adjacency 10.1.12.2 MPLS TE using type 10 of LSA to a region within MPLS TE work. LSP Seq Num Fa1/0 1.1.1.0 is directly connected, Loopback0 2.0.0.0/24 is subnetted, 1 subnets 4.4.4.4/32 Network 10.1.23.2 0.0.0.0 area 0 ! Router isis Then R1 and R3 receive a label mapping with a prefix of 2.2.2.0/24 and a label of 3 . At the same time, they also received the R2 updated route. Since the loopback interface route is updated by OSPF by default, it is updated in /32 mode. Therefore , the route learned on R1 and R3 about 2.2.2.2 is /32 bit. of. Then this is a problem, my routing entry is 2.2.2.2/32 , but the label message you sent me is 2.2.2.0/24 , it doesn't match, so R1 thinks that the label is going to Not 2.2.2.2 , just give an untagged , just like the LFIB table we saw for R1 . In this way, when R1 receives the label package and goes to 2.2.2.2 ,R1 will pop up the label stack of the label package, then find its own FIB table and forward the message out. This seems to be no problem in this topology, but in many environments, there will be problems, such as MPLS VPN . So how to solve it? Very good, R2 loopback port to an ip ospf network point-2-point , or change the mask.