ccna online paper

ccna online paper

R2-PE1#show mpls ldp neighbor 906 Router-id 4.4.4.4 By default, IS-IS of the LSP maximum survival time of 1200s , The configuration of R2-PE1 is as follows: The configuration of R2 is modified as follows: After calculating the path, you need to reserve resources and distribute labels through RSVP . The RSVP path message is transmitted one hop along the calculated PATH and requests resources and labels. Then R7 will give the response and bring the label back. This tag distribution and resource reservation actions are also performed one by one. In this way, an LSP is finally established. RFC 2370 describes an extension of OSPF that defines three new LSAs . These LSAs are called sluggish LSAs ( opaque LSAs ) and their differences are limited to the extent of propagation. These LSAs can accurately provide the information required by MPLS TE to OSPF : 9 All routers in the LAN advertise their own connectivity to the pseudonodes in their LSPs (the adjacency relationship between themselves and the pseudonodes) *Aug 18 09:06:07.919: Controlled Load Service break bit=0 service length=0 NSAP Interface Ethernet0/0 IGP Area[1] ID:: ospf area 0 System Information:: When a packet enters the PE , is it a lookup table ( FIB ) or a checklist ( LFIB )? Establish mapping of data link layer address to network layer address ( CLNP address) LSP 75000 ( ZeroAgeLifetime , during which only the header of this LSP is reserved ), it will be deleted when this time is reached. UP 28 IGP System ID: 2.2.2.2 Different TLV field values ​​can be included in the LSP to advertise various different routing information. Ip address 4.4.4.4 255.255.255.255 Seq# Checksum Opaque ID (The router address and link information in the result of capturing the packet are respectively). Interfaces: RFC1195 Policy Routing Policy Route Bw[2]: Fa0/0 Removal Trigger: re-route path verification failed Router ospf 1 Type : 0x8848 (Multicast) The upper layer carries MPLS , looking for LFIB 4 10.1.45.5 8 msec 8 msec * 17 *Aug 18 09:06:07.919: 10.1.24.2 (Strict IPv4 Prefix, 8 bytes, /32) 0 kbits/sec Mpls traffic-eng tunnels ip rsvp bandwidth S 4.4.4.4 is directly connected, Tunnel0 Mpls ldp igp sync holddown msecs In area 49.0001, we can see that all routers flood their own LSPs . LSPs are represented by LSPIDs , such as R1.00-00 . This R1 is the hostname of the device . Here we have the default hostname mapping mechanism. See above. . In addition , 00 after R1 is a pseudo node identifier, and 00 means that the originating router of the LSP is not a DIS , and then the last 00 is a fragmentation flag. Et0/0 *Aug 18 11:31:44.598: Router ospf 100 Router-id 4.4.4.4 *Aug 18 11:26:02.546: Ip unnumbered loopback 0 tunnel destination 5.5.5.5 tunnel mode mpls traffic-eng State Changed: 00:20:27 BGP routing problem, well, now we use the loopback interface on R1 and R4 to establish IBGP adjacency, the problem is solved. At this time R4 ,ccna online paper, the go 5.5.5.5 next hop of the R1 of Loopback port addresses, R4 at destined to 5.5.5.5 of the IP when the pressure package label, use is 1.1.1.1/32 routing tag, The same is true for R3 and R2 , then the label package can be opened through 1.1.1.1/32 . 0x2995 Look at the LDP neighbor on R2 : 202 0x4F65 *Aug 18 09:06:07.919: Ip address 2.2.2.2 255.255.255.255 Reservable Bandwidth[1]: Mpls traffic-eng tunnels ip rsvp bandwidth Or Tunnel Id *Aug 18 11:31:44.598: Auto-bw: disabled *Aug 18 04:37:06.239: HOP type 1 length 12: Bw[7]: 10.1.23.3 [MPLS: Label 300 Exp 0] 4 msec 0 msec 4 msec Solution: R1 and R4 use the loopback interface to establish IBGP neighbor relationships. R1(config)#key chain test R1(config-keychain)#key 1 Interface fast 0/0 ! The configuration of R5 is as follows: An NSAP address with a NSEL value of 0 is used to identify the device, which is the network address of the device, NET . Therefore NET is determined by the area Id and the system ID . In general, the biggest difference between NSAP addressing style and IP addressing style is that NSAP uses only one address to identify a router , while IP is assigned an Ip address for each port . Mpls traffic-eng router-id loopback0 mpls traffic-eng area 1 Interface fast 0/0 Each metric type is 8bits and has the following form: Net 49.0001.0000.0000.0002.00 !! Configure the is-type of the device , the default is level1-2 Prior LSP: RouterID , or the IP address of the interface . 1.0.0.0 Like all IS-IS packets, the HELLO package consists of a header and a TLV . Fa0/0 Tag rewrite with Fa0/0, 10.1.12.2, tags imposed: {203} InLabel : - ! Network 10.1.12.1 0.0.0.0 area 0 The metric configuration only affects the tunnel endpoint router itself, and does not advertise to other neighbors. But the forwarding adjacency feature is different. Moreover, the two methods of modifying the metric are not used. The autoroute needs to match the autoroute keyword to modify the metric and only affect the configurator itself. In the forwarding adjacency, the metric is modified directly in the tunnel interface . For example , if ISIS is used , then the isis metric command. If ospf is used , it is ip ospf cost .