cisco ccna pass for sure

cisco ccna pass for sure

R3 to 304 replace 404 . Note that both 304 and 404 are RSVP- assigned tags, so we should still pay attention to the tunnel when viewing the tags . The above table entry, 2.2.2.2 0[5] , be careful not to make a mistake, not the label corresponding to the prefix 2.2.2.2 , but the label corresponding to this tunnel . Interface fas0/0 Ip unnumbered Loopback0 tunnel mode mpls traffic-eng MPLS TE tunnel Based on the above configuration, modify the configuration of R2 : *Aug 18 04:37:06.239: version=0 length in words=10 OutLabel : Ethernet0/0, 204 RSVP Signalling Info: Mpls traffic-eng router-id loopback0 mpls traffic-eng area 0 17 Tunnel destination 4.4.4.4 tunnel mode mpls traffic-eng 75000 Interface eth 0/1 NSAP address re-addressing LABEL 1/0/0 *Aug 18 09:06:07.919: 10.1.24.4 (Strict IPv4 Prefix, 8 bytes, /32) Ip unnumbered Loopback0 tunnel mode mpls traffic-eng tunnel destination 5.5.5.5 SystemID (DIS) : LAN ID . It consists of the SysID of DIS and a 1- byte pseudonode ID . The LAN ID is used to distinguish the same one. Mpls traffic-eng tunnels ip rsvp bandwidth 1bit is the bottom of the stack (this position is 1 , the last label. You can press a multi-layer label on a data packet, and the Bos bit of the last label is set to 1. When processing to this layer, the upper-layer data packet is normal data. package.) Current LSP: Provide network stability The boundary of the area is on the link Now let 's take the traffic going to 4.4.4.4 on the R1 to the tunnel , using one of the simplest methods: static routing. RSVP and label IS-IS packets carry all easily expandable information using TLV fields The attribute tag is a 32-bit field, which is described in detail later. The loopback0 address space of all devices is xxxx/32 , and x is the device number. Router-id 3.3.3.3 Ip cef Router isis Recommendations for Interoperable Networks using IS-IS In IPv4 , the empty tag is 0 , and the ipv6 is 2 . Record Route: NONE R1(config)#interface fa0/0 The TTL is placed in the label header. Turning off TTL propagation prevents the MPLS network from being exposed (by traceroute ). So far, the basic configuration has been completed. Now let 's create a TE Tunnel on R2 and R5 : 10.1.23.3 Send out from the Fa1/0 port. So, R2 replaces the tag with 300 and then throws it to R3 . R1#sh mpls forwarding-table 103 Router ospf 1 RFC 3719 RSVP Signalling Info: Describes all LSP information in the LSP database . Protection Link (link protection) Basically, the LSP is the path through the MPLS network or a part of it that packets take. // One-way path. In fact, an LSP is a path when a packet traverses an MPLS network or a part of an MPLS network. The boundary of the area is on the link An IP address. *Aug 18 04:37:06.243: tspec parameter id = 127, flags = 0, length = 5 Router ospf 1 Ip cef Net 49.0001.0000.0000.0002.00 0xCC RESV response PATH message, to establish and maintain LSP passage To sum up, I said three commands: Tunnel mpls traffic-eng path-option 10 dynamic Create a TE tunnel on R1 , the source is its own loopback0 , and the destination is 4.4.4.4 of R4 . Router-id 2.2.2.2 Ip router isis router isis Redistributing via isis 3.3.3.3 IS-IS Level-2 Link State Database: Record Route: NONE Network 5.5.5.5 0.0.0.0 area 1 Interface eth0/0 *Aug 18 11:31:44.598: Tunnel mpls traffic-eng fast-reroute R2 (config)#router isis We assume that in the above topology, the bandwidth of all links is 10Mbps . Then after running the IGP protocol, we know that from R1 to R7 , the shortest path is R1-R3-R6-R7 , but because the traffic between R1-R8 in the network has already run on this path, and it takes up a relatively high Bandwidth,cisco ccna pass for sure, the load of the link is too high, the traditional IP routing protocol is not so smart to take this into account, but with MPLS TE , we can let R1 to R7 take a better path. .