about ccna

about ccna

Time since created: 11 minutes, 42 seconds Time since path change: 10 seconds Number of LSP IDs (Tun_Instances) used: 9 ! 75000 ISO10589 i L1 RFC 3358 Experimental results: Path Protection: 2 Common Link(s), 2 Common Node(s) 302 In this way, in the route of L2 , the route matched by the route-map will be injected into the level1 area , then R1 can learn 5.5.5.0 . Type IA , i.e. isis the interarea route, i.e. isis inter-area routes. Ip address 10.1.123.3 255.255.255.0 Prefix adjacent router However, not all messages with the same label belong to one FEC , because the EXP values ​​of these messages may be different and may be performed differently, so they may belong to different FECs . Protection Link (link protection) Local binding: tag: 100 Mpls traffic-eng tunnels ip rsvp bandwidth MPLS TE status If the headend wants to remove the tunnel , send PATHtear along the tunnel path , and the received node responds to RESVtear , so the tunnel between the two points See below for more details. ! Pop tag No bgp default ipv4-unicast neighbor 5.5.5.5 remote-as 2345 Ip address 5.5.5.5 255.255.255.255 10.0.0.0/24 is subnetted, 3 subnets MPLS TE using type 10 of LSA to a region within MPLS TE work. The above is the LDP neighbor shown on R1 . There is an LDP neighbor. Its LDP router ID is 2.2.2.2 and label spaceID=0 . This indicates that the platform is based on the label space. You can use the no mpls ldp igp sync command on a particular interface to turn off synchronization on the interface. Show clns neighbors Describes all LSP information in the LSP database . Bytes Label The overload router participates in the calculation as the last hop route. Use set-overload-bit to manually set the overload bit. The L1 router only has the link state database of Level1 in the area , and contains routing information of all L1 routers in the area. Opaque ID: 0 Comparison of terms between IS-IS and OSPF : Support for diagnosis of LSP tunnel This will cause R2 to calculate the route, from the tunnel0 port to the 5 and 55 route metric becomes 32+1=33 , which is greater than the metric=31 of the route taken from e0/1 . So the routing table of R2 has changed, and the routes of the 5 and 55 network segments have become: MPLS TE packet forwarding is based on labels. Packets are forwarded along the pre-established LSP . Then , after the tunnel is established, how to import traffic into the MPLS TE Tunnel ? The traffic will only enter the LSP if it is on the tunnel . There are three ways: 1/0/0 *Aug 18 04:37:06.239: 1.0.0.0/24 is subnetted, 1 subnets RSVP extension to LSP tunnel We see that the forwarding aspect of the data is this: TE with Layer 2 overlay Router(config-if)#mpls traffic-eng flooding thresholds up/down ? The global configuration command metric-style transition allows the original narrow metric to be smoothly extended to a new width. This command allows a router to accept and transmit both narrow and wide quantities. LSPID Number of Links : 1 Mpls traffic-eng router-id loopback0 mpls traffic-eng area 0 LDP and IGP synchronization 0x80000018 0x008F6C 0 Let's take a look, why is it exposed to network information? Suppose A below router E , E made to be a packet to D under F. , The data packet is A tag the transferred B , assumed that the BC loop appears between subsequent label TTL is decremented to 0 , since the TTL value The setting is very small, so very quickly, the TTL is decremented to 0. At this time, B (message discarder) will send an ICMP error message back to E. Then,about ccna, if B has E route (or label), B will The ICMP error message will be sent directly back to E. If not, B will continue to tag the error message and gradually pass it to D , D.As the PE , about E route, then back to the label and then loaded on E . Then, no matter what the situation, the final E can receive the ICMP error message generated by B.