ccna 3

ccna 3

.......................................... ! 75000 Mpls label rangempls label range 100 199 interface fa0/0 For the device number, this IP is also the LDP routerID . Of course, if you are running in a single zone, you can use a full L1 router or a full L2 router solution. *Aug 18 11:31:44.598: !! activation level1 of MPLS TE ! Here there is a potential problem, because Level1 Router , do not know level2 routing (outside the region) information, instead of looking for the nearest L1 / L2 router to your destination, then it may appear sub-optimal path In order to solve this problem, IS-IS introduced a mechanism called route leakage. There are two types of tunnel priorities: Moreover, it is not necessary to maintain the matching time of both parties when establishing the adjacency relationship. Src 1.1.1.1,ccna 3, Dst 4.4.4.4, Tun_Id 0, Tun_Instance 2 RSVP Path Info: Name: R1_t0 Status: Network 10.1.23.2 0.0.0.0 area 0 Now, we have to build a TE tunnel from R1 to R6 with a bandwidth requirement of 30M . Note that the available bandwidth in the network at the moment is due to the above. Network 10.1.34.4 0.0.0.0 area 0 *Aug 18 09:06:07.919: Path Latency (microseconds):0 0/0/0 The configuration of R1 is as follows: Collects reachable NSAP prefix information, which is only used for inter-area ISO CLNP roads. Ip cef Ip explicit-path name R2R3R4 enable next-address 10.1.12.2 R2-PE1#show mpls traffic-eng tunnels Interface eth 0/0 ... ... ... ... Pop tag 1.1.1.1/32 4.4.4.4/32 Ip address 55.55.55.55 255.255.255.255 Or ISIS will flood the LSP . Global Pool Label or VC Link IP Address: 10.1.12.2 2.2.2.2/32 Label Mapping message ! Mpls ldp router-id loopback0 mpls label range 400 499 interface fast0/0 *Aug 18 11:26:02.546: (Link ID) Network/subnet number: 2.2.2.2 (Link Data) Network Mask: 255.255.255.255 Number of MTID metrics: 0 Summary of tag processing actions *Aug 18 09:06:07.919: average rate=250000 bytes/sec, burst depth=1000 bytes Tunnel mpls traffic-eng path-option 10 dynamic ! The authenticated TLV is not seen in the PSNP message . twenty two OutLabel : FastEthernet0/0, 200 RSVP Signalling Info: Finally, the path of the second TE tunnel is as follows: 0xA538 OAM is basically used for error detection, location, and monitoring implementation. This tag distinguishes between ordinary messages and OAM messages. CISCO IOS does not use tag 14 , which performs MPLS OAM but is not implemented by tag 14 . Area Address(es): 49.0001 SNPA: cc02.1ab0.0000 ! R2.00-00 ! Ip address 10.1.123.2 255.255.255.0 Interface eth 0/0 ( NLPID 0x81 ) and IP ( 0xCC ) Fspec: ave rate=0 kbits, burst=1000 bytes, peak rate=0 kbits Route summarization on the L1/L2 router ( to level1 ) * 0x0000000C 10.1.12.2 !! The outbound label is 301 ! However, there may be such a problem that the LDP connection between R1 and R2 is broken for some reason, but between R1 and R2 . R3(config-if)#tunnel mpls traffic-eng forwarding-adjacency ? // Prerequisites for advertising a label mapping message to a neighbor locally OSPF is LSADB Network 2.2.2.2 0.0.0.0 area 0 PDU 10.1.12.2 The L1 and L2 IIH PDUs on the LAN are sent to different multicast MAC addresses: L1 is 0180-C200-0014 , L2 is The PATH message is sent to the end of the hop by one hop; the RESV message is sent to the headend router in the opposite direction. Router-id 3.3.3.3 i ia 10.1.24.0 [115/148] via 10.1.123.2, FastEthernet0/0 i ia 10.1.45.0 [115/158] via 10.1.123.2, FastEthernet0/0 i ia 10.1.34.0 [115/158] via 10.1.123.2 , FastEthernet0/0 C 10.1.123.0 is directly connected, FastEthernet0/0 0x00000026 132 ! Affinity property Affinity Attributes and mask *Aug 18 09:06:07.919: version=0, length in words=7 LAN on the MAC or the X.25 , FR or ATM in the virtual circuit ID Explicit Route: 10.1.12.2 10.1.23.2 10.1.23.3 10.1.34.3 Res. Sub BW: 0 kbits/sec Downstream:: Debug ip rsvp dump-messages Down Thresholds: 100 99 98 97 96 95 90 85 80 75 60 45 30 15 FastEthernet0/0, Src IP addr: 10.1.12.2 Addresses bound to peer LDP Ident: 101 !! TE metric , the default is equal to the following IGP metric *Aug 18 04:37:06.239: Tun Dest: 5.5.5.5 Tun ID: 0 Ext Tun ID: 1.1.1.1 1.1.1.1/32 ! Priority 7 : 9375000 *Aug 18 09:06:02.699: Minimum Path Bandwidth (bytes/sec): 1250000 Prefix adjacent router Version:1 flags:0000 cksum:7931 ttl:255 reserved:0 length:132 Ip unnumbered Loopback0 tunnel mode mpls traffic-eng tunnel destination 5.5.5.5 Link state Protocol Data Unit Link State Data Unit The trick of traditional IP routing: 10.1.12.2 [MPLS: Label 203 Exp 0] 200 msec 84 msec 136 msec Et0/0 Layer 1 and Layer 2 set different metrics. *Aug 18 11:26:02.546: MPLS application RFC2966 standardized from Level2 to Level1 leaked routes 10 LSP Holdtime Physical Bandwidth: Physical bandwidth of the 100000 kbits/sec !! interface 10.1.23.0/24 Kbps (Global) Priority: 6 6 Affinity: 0x0/0xFFFF Activate the fast-reroute feature on R1 and observe the phenomenon i ia 5.5.5.0 [115/158] via 10.1.123.2, FastEthernet0/0 10.0.0.0/24 is subnetted, 4 subnets *Aug 18 09:06:07.919: ADSPEC type 2 length 48: 1/0/0 NSAP In the LAN , SNPA refers to the MAC address. Local tag Mpls traffic-eng reoptimize events link-up OO Tunnel mpls traffic-eng bandwidth 2000 Interface Loopback0 The configuration of R1 is as follows ( R2 does not open area password temporarily ): Fa0/0 *Aug 18 11:31:44.598: Nolabel/505 * 0x0000000C ISO10589 *Aug 18 04:37:06.239: version=0, length in words=7 10.1.45.0/24 [110/30] via 10.1.23.3, 00:00:01, Ethernet0/1 IS-IS by Hello PDU padding size to the interface MTU large Outgoing For example, R1 . 01 - 00, where R1 is SystemID (this is the system ID based on the host name ), 01 is the PseudonodeID pseudo node ID , and if it is sent by the pseudo node, it is non- 00 , 00 is the fragment number. Mpls traffic-eng tunnels mpls ip Kbps (Global) Priority: 7 7 Affinity: 0x0/0xFFFF Local 10.1.23.3 [MPLS: Label 300 Exp 0] 108 msec 116 msec 64 msec Untagged CSPF calculates the path R1#show isis database verbose R1.00-00 The configuration of R5 is as follows: The PATHTear packet is similar to the PATH except that it is sent when the TE tunnel LSP created by the headend router needs to be removed . For example, the tunnel interface is manually shut down . Path: valid Link status changes The path calculation of the MPLS TE tunnel requires relevant information to be performed. Then we need to use a link state routing protocol to flood the link information to all routers running TE in the network . After collecting the information, the TE router establishes its own MPLS TE Database .