ccna exploration 4.0

ccna exploration 4.0

The routing table for R1 is as follows (direct route is ignored): About flooding 10.1.12.2 The configuration of R3 is as follows: Tag or VC Local binding: tag: imp-null Tunnel: Ip router isis *Aug 18 09:06:02.699: General Parameters break bit=0 service length=8 Ip unnumbered Loopback0 tunnel mode mpls traffic-eng tunnel destination 5.5.5.5 Reservable Bandwidth[2]: 130 Mpls traffic-eng router-id loopback 0 mpls traffic-eng level-1 Mpls traffic-eng tunnels mpls label range 300 399 Mpls traffic-eng tunnels mpls label range 300 399 Mpls traffic-eng reoptimize events link-up Network Services Access Points Next, R3 receives the tag package. Similarly, look at your own LFIB : The routing table for R1 is as follows (direct route is ignored): Router ospf 1 Priority 1 : 9375000 1.1.1.1:0 Interface loopback *Aug 18 09:06:07.919: Hop Addr: 10.1.12.1 LIH: 0x20000403 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 . ES C 1.1.1.0 is directly connected, Loopback0 5.0.0.0/24 is subnetted, 1 subnets Down Thresholds: 100 99 98 97 96 95 90 85 80 75 60 45 30 15 Next hop 10.1.34.3, FastEthernet0/0 via 10.1.15.0/24 valid cached adjacency 0x80000018 0x008F6C 0 Last update from 10.1.123.2 on FastEthernet0/0,ccna exploration 4.0, 00:01:32 ago Routing Descriptor Blocks: Interface Ethernet0/1 Remaing lifetime LSP lifetime before LSP ID LSP identity Sequence num LSP serial number R2#show mpls forwarding-table Explicit Route: 10.1.12.2 10.1.24.2 10.1.24.4 10.1.45.4 Area Address: 49.0001 Interface After the configuration is complete, the tunnel is up. Holding timer : Hold time, default 30S Bw[3]: The configuration of R2 is supplemented as follows: Two processes: neighbor discovery process, session establishment process Ip rsvp bandwidth 2000 This command sets the total reservable bandwidth of the interface to 2M. Understand the forwarding process of data in the MPLS domain Ip cef The interface will be created. We just need to put the traffic into the tunnel port, there are still a lot of methods, we will continue to introduce in the following content. 55.55.55.55 [110/2] via 0.0.0.0, 00:00:01, Tunnel0 The configuration of R2 is as follows: !!tunnel establishment and retention priority IS-IS of IIH will be marked with a lot of padding , the Hello packets filled out the interface MTU . This mechanism will be more vulnerable on low-bandwidth links. You can cancel padding on the interface with no isis hello padding . This command, if you want to play, is recommended to be added at both ends of the link. The result of the experimental pro-test is that if no one drops hello padding , the adjacency can still be established.