about ccna course

about ccna course

Explicit Path a series of IP configuration, an explicit path in the IP can be an interface IP , it may be MPLS TE Router ID . Let the ES know where it is, the area prefix The configuration of R2 is as follows: Level2 , using the interface level command: isis circuit-type level2 , then R2 and R3 will not advertise these direct links when advertising LSPs in area 49.0001 . So the routing table for R1 becomes: We see that after the BGP neighbor relationship is up , R2 immediately triggers an LSP , and the overload is set before the LSP is cleared . Next hop 10.1.12.2,about ccna course, FastEthernet0/0 valid cached adjacency Note: LDP or TDP only generates labels for routing entries of the IGP protocol, and does not generate labels for BGP routing entries. Network 3.3.3.3 0.0.0.0 area 0 959 Is an extended form of type 2 TLV *Aug 18 09:06:07.919: Prior LSP: Prefix Discovery Sources: Te use TE metric default is this *Aug 18 04:37:06.239: Controlled Load Service break bit=0 service length=0 !! Activate the autoroute feature of the tunnel ! TE with Layer 2 overlay !! Use strict next hop directly in this area !! The unit is Bytes , multiplied by 8 is 100Mbps 10.1.12.2 We see the above output, R1 , R2 , R3 all generate LSP , and the asterisk entry is issued by R1 itself. In addition, there is a special Conservative mode : Conservative Retention RFC1195 75000 10.1.23.3 Send out from the Fa1/0 port. So, R2 replaces the tag with 300 and then throws it to R3 . Activate the MPLS TE extension for each router's OSPF and manually set the RouterID for MPLS TE . Verify and view Traceroute 1.1.1.1 source 10.1.35.55 Type 1 length 8 : 2 Interface Lighter, only LSPs in this area . LDP discovery sources: Of course, when deploying, we strongly recommend that the same tunnel should have the same priority and priority. Mpls ldp router-id loopback0 2.2.2.2/32 ! IP Address: Metric: 10 6.6.6.6/32 5135 *Aug 18 09:06:07.919: EXPLICIT_ROUTE type 1 length 68: Mpls traffic-eng tunnels mpls label range 200 299 Next Hop If the L1 / L2 router redistributed external routes to Level-1 , the Level1 area in you can learn the route, but R2 does not route injection Level2 area is Backbone of The label is incorrect. This situation only occurs when the IGP is OSPF . Because if the loopback is used as the router-id of the ldp and it is not 32 -bit, OSPF will automatically issue the 32 -bit loopback address. Causes the label to be assigned an error. Type 2 length 48: ! R2#sh mpls tr link-management advertisements *Aug 18 09:06:07.919: IS Hops:0 ! TTL-propagate R5 is also similar: Each IP packet forwarded to a router is the same before and after being forwarded through the router. 1.1.1.0 is directly connected, Loopback0 2.0.0.0/24 is subnetted, 1 subnets Show mpls traffic-eng link-management bandwdith-allocation Calculated. In the figure above, the red path is calculated by CSPF . With the PHP mechanism: Name: R1_t0 Status: This will cause the route of R2 to change. The outgoing interface of the route to 5.5.5.5 and 55.55.55.55 becomes e0/1 . So R2 goes to Ip rsvp bandwidth Tunnel mpls traffic-eng path-option 10 dynamic LSP ID If the payload of the MPLS is an IPv6 packet, the load balancing is performed according to the source and destination addresses in the IPv6 header. To meet the above requirements, IS-IS is designed as a link state routing protocol and uses the SPF shortest path first algorithm to achieve fast convergence and loop-free networks. *Mar 1 00:00:32.759: ISIS-Upd: full SPF required Interface loopback0 Priority 0 : 9375000 See below for more details on how labels are handled. Record Route: 10.1.34.3 10.1.13.1 Interface Serial1/0 10.1.34.0/24 Run the interface configuration command: isis metric value level-1 | level-2 to configure the metric on the same interface. What is the difference between POP and Untag in Outgoing tag(Label) ? Traffic Engineering (TE) automatic bandwidth feature adjusts the bandwidth allocation for TE tunnels based on their measured traffic load: Lighter, only LSPs in this area . Ip rsvp bandwidth Mpls traffic-eng tunnels ip rsvp bandwidth LSP Database LSP database Net 49. 0001 .0000.0000.0001.00 Interface eth0/1 *Aug 18 09:06:07.919: Path Latency (microseconds):0 Remote binding: tsr: 2.2.2.2:0, tag: 203 IP 10.1.123.0 255.255.255.0 Egress LSRs — Egress LSRs receive labeled packets, remove the label(s), and send them on a data link. Ingress and egress LSRs are edge LSRs. Token bucket fragment (service_id=1, length=6 words parameter id=127, flags=0, parameter length=5 By default, if the synchronization is not completed, the IGP does not explicitly know the time to wait before establishing the adjacency relationship. IS-IS We see that the Tunnel is up, and R2 goes to the 5.5.5.5 route, the outgoing interface is tunnel , and the TE tunnel is up. 1.1.1.1 basic concept Local binding: tag: imp-null The forwarding behavior of such IP packets may cause link transitions in some networks, while other links have a low probability of use. Network 10.1.45.5 0.0.0.0 area 1 *Aug 18 09:06:02.699: Outgoing Path: !! The path message sent by R1 has changed. 1.0.0.0 Mpls traffic-eng tunnels mpls label range 500 599 Type 1 length 12: Based on the information in the link state database, the almost identical algorithm, the SPF algorithm, is used to calculate the optimal route. R1#show ip cef 4.4.4.0 detail 4.4.4.0/24, epoch 0 Tunnel mpls traffic-eng path-option 10 dynamic R1#show mpls ldp neighbor Peer LDP Ident: 2.2.2.2:0; Local LDP Ident 1.1.1.1:0 Router(config-router)# max-area-address xx Sender_Tspec R2-PE1#show mpls forwarding-table detail Untag : Pops up all the tags and then forwards them according to the next hop (find FIB table). There are three reasons for the occurrence of untag : EXP *Mar 1 00:00:32.783: ISIS-Upd: Sending L1 LSP 0000.0000.0002.00-00, seq 37, ht 1199 on 968 IS-IS Hello message ( IIH PDU ) All routers in a zone must have the same zone ID Hello data unit: sent periodically to determine whether other ISs are running IS-IS , establish adjacencies, exchange LSPs , and synchronize LSDBs . 5 10.1.56.6 8 msec * 0 msec 101 3.3.3.3/32 Interface Tunnel0 the term 10.1.123.3 Lists the Layer 3 protocol supported by the integrated IS-IS protocol. Currently only CLNP To form an adjacency relationship. O 3.3.3.3 [110/3] via 10.1.12.2 , 00:00:37, FastEthernet0/0 Broadcast network We complete the experiment as long as the R2 and R4 configuration domain-password can, Rl is a zero-configuration ( Domain Authentication actually level2 LSP embedded for authentication TLV ). When the router receives an ISH packet on a point-to-point link , the router checks the local neighboring database to see the source of the packet. Record Route: NONE 75000 Local binding: tag: 101 IP external reachability information R2 is preferably a route from the tunnel port. At this time , the traffic from R2 to 55.55.55.55 is on the tunnel , and the LSP is used for label switching. 100 CLNP is similar to the IP protocol except that it serves the ISO transport layer. IS-IS , ES-IS , and CLNP are network layer protocols that are encapsulated directly in the data link layer frame. Compared with the OSPF packet in TCP/IP , it is hidden behind the IP header. The encapsulation efficiency of the former protocol packet is higher. Router ospf 1 !! Activate the autoroute feature of the tunnel ! OSPF is encapsulated in an IP packet with the protocol number of 89. The allocated bandwidth is periodically adjusted to be the largest sample for the tunnel since the last adjustment No synchronization Explicit Route: 10.1.12.2 10.1.24.2 10.1.24.4 10.1.45.4 Ip address 10.1.34.3 255.255.255.0 BW (kbps) Swap Configuration command FastEthernet0/0, Src IP addr: 10.1.12.2 Addresses bound to peer LDP Ident: About 30.0 / 24 prefix, C allocates a label 23 , the mapping is transmitted to the B ; B local to 30.0 / 24 allocates a label 22 , the mapping is transmitted to the A . 10.1.34. 4 4.4.4.4 R4 configuration is as follows 10.1.56.0/24 ! Fspec: ave rate=20000 kbits, burst=1000 bytes, peak rate=20000 kbits History: Router(config)# mpls ldp discovery holdtime seconds 2.2.2.2/32, Flags: 0x21 (Local Prot Avail/to NHOP, Node-id) POP is the TTL of the top-level tag minus 1 and then pops up. The new TTL value is written to the top-level tag of the outbound data. We see the above output, R1 , R2 , R3 all generate LSP , and the asterisk entry is issued by R1 itself. In addition, there is a special TE can provide a solution to avoid link overload by controlling traffic or partial traffic. Let's make a comparison: Forwarding Adjacency forwarding adjacency Tunnel mpls traffic-eng priority 7 7 tunnel mpls traffic-eng bandwidth 20000 At this time, TTL propagation can be turned off ( CISCO router is enabled by default) Send PATH message to the downstream every 30S head end 10.1.23.3 IS-IS supports ISO connectionless network environment, pay attention to the data link is LDP discovery sources: Mpls traffic-eng tunnels mpls ip Name: R1_t0 Status: Tag MPLS TE router ID: 1.1.1.1 Needless to say this? Et0/1 MPLS coding Clear text area certification - If the L1 / L2 router redistributed external routes to Level-1 , the Level1 area in you can learn the route, but R2 does not route injection Level2 area is Backbone of 3.3.3.3/32 Message type 10.0.0.0/24 is subnetted, 3 subnets Neighbor 5.5.5.5 update-source Loopback0 Mpls ip 2 Level2 area It can be seen that ES-IS plays a role in the CLNS network environment as if the ICMP , ARP and DHCP protocols in the IP network work together. IS-IS can ignore TLVs it does not support Peak rate 0x4F65 Router(config)#mpls traffic-eng reoptimize timers frequency ? *Aug 18 09:06:07.919: Tun Dest: 5.5.5.5 Tun ID: 0 Ext Tun ID: 1.1.1.1 The hostname can be used in the ID instead of the SysID section. This brings great convenience to our network maintenance and troubleshooting. Label description 772 102 Interface loopback 10.1.34.3 10.1.34.4 Reservable Bandwidth[2]: 5.5.5.5 Router(config-if)# mpls traffic-eng path-option x {dynamic | explicit name y } [ lockdown ] LDP discovery sources: Ip address 10.1.123.1 255.255.255.0 Ip cef LS age: 29 ADV Router Clear text area certification (Tunnel0) Destination: 4.4.4.4 Ip address 2.2.2.2 255.255.255.255 R3 configuration is as follows 0x0000000C Bw[3]: PDU Maximum bandwidth : 12500000 value 10.1.34.4 The LSA is encapsulated into the LSU to advertise to the neighbor 10.1.23.0 [110/65536] via 10.1.12.2, 00:00:48, FastEthernet0/0 Domain-wide Prefix Distribution with Two-Level IS-IS MPLS VPN Backbone carried out within for MPLS TE in the OSPF extensions and R1 build on a TE the Tunnel , for their own sources of the Loopback0 , for the purpose of R5 is 5.5.5.5 The Auto Route is configured on the MPLS TE tunnel head-end router and only affects the OSPF route selection of the head-end router . ISO 8348/Ad2 State: Oper; Msgs sent/rcvd: 9/9; Downstream 4.4.4.4/32, version 12, epoch 0, cached adjacency 10.1.12.2 203 So now, we will change the loopback port address of R2 to 2.2.2.2/24 and change it to /24 to see what happens. You can use router(config)# ip rsvp signalling rate-limit to limit the rate at which signaling messages are sent or use router(config-if)# hold-queue x in to limit the rate of reception. ATT/P/OL IS-IS support for IPv6 IS-IS Adjacency related packets debugging is on R1# Mpls traffic-eng tunnels mpls label range 400 499 10.1.34.4 10.1.45.4 10.1.45.5 5.5.5.5 0/0/0 Since we have configured link protection on R2 to protect the link between R2-R4 , when the E0/1 port of R2 is shut down , the path error message sent by R2 to R1 indicates that R1 does not need to be removed. Drop the tunnel . So R1 of the tunnel will not be removed. mode. R1#sh mpls traffic-eng topology 1.1.1.1 (1.1.1.1 is a local router ) My Address: 10.1.12.1 ISO 9542 Verify that you receive the LDP Hello from the other party. Experimental procedure After all the LDP routers have sent the label bundles to each other, everyone gradually builds their own LFIB . 10.1.23.3 [MPLS: Labels 304/505 Exp 0] 4 msec 4 msec 4 msec Solution: R1 and R4 use the loopback interface to establish IBGP neighbor relationships. For the IP prefix of each IGP in the IP routing table , each LSR running the LDP protocol is locally bundled, that is, a label is assigned to the IPv4 prefix, and then the LSR distributes the assigned label to all the labels. LSR neighbor. These received tags are converted to a remote tag remote label , and then the neighbor stores the remote tag and the local tag in a special table, which is the tag information library LIB .