ccna lab questions and answers pdf

ccna lab questions and answers pdf

O 3.3.3.3 [110/3] via 10.1.12.2 , 00:00:37, FastEthernet0/0 *Aug 18 11:31:44.598: The route prefix is ​​learned locally by the IGP , but the next hop router of the route prefix must advertise the label mapping message corresponding to the prefix to the local, and the local will assign a label to the prefix. Active Path Option Parameters: Bw[4]: Fa0/0 Pop Label No synchronization In general, any router that checks for a corrupted LSP will be corrupted by sending a remaining lifetime to 0 . 42000 Pop tag NLPID: Manual re-optimization Router-id 4.4.4.4 Manual re-optimization *Aug 18 04:37:06.243: FILTER_SPEC type 7 length 12: HELLO message Net 49.0001.0000.0000.0002.00 We went to traceroute on R1 6.6.6.6 R1#traceroute 6.6.6.6 Tunnel: Ip address 10.1.123.1 255.255.255.0 75000 The tunnel priority ranges from 0 to 7. The smaller the priority, the higher the priority. Set priority *Aug 18 09:06:07.919: Domain-wide Prefix Distribution with Two-Level IS-IS Mpls ip 968 Select the path with the lowest IGP cost 6bits R1 goes from R2 and then goes to tunnel . The cost of this path is cost=10+1+1=12 Current LSP: Oper: up R1#show ip cef 4.4.4.4 Detailed information Mpls traffic-eng tunnels mpls label range 100 199 Overload Network 1.1.1.1 0.0.0.0 area 0 The configuration of R5 is supplemented as follows: Router isis Configuration command basic concept Ip cef Admin: up 10 bibliography 10.1.34.4 *Aug 18 11:26:02.546: The label can be ejected on the (the penultimate hop). C only needs to find the FIB table to forward the received IP packet. By default, TE metric is used as the basis for calculating the shortest path of a TE tunnel. MPLS TE of AutoRoute characteristics of the TE tunnel as a direct link participating SPF calculation (except R2 themselves) Configure targeted-hello accept acl LDP allows non-directly connected neighbors, so that neighbors discover that they do not need to rely on multicast HELLO packets, but instead use unicast packets. .......................................... Switched Integrated IS-IS ( IS-IS ) enables the IS-IS protocol to propagate routing information for protocols other than CLNP . Located inside the ordinary area !! ldp 's routerid uses loopback port IP Initial database synchronization is performed after the adjacency is established. Affinity Bit : 0x0 IGP Metric : 1 Record Route: Reservable BW (kbps) On the R3 , as shown in the figure, the R3 local routing table does not need a default route, and an IS-IS default route can be generated and passed to 75000 ! Configured on L1/L2 rouer, which is R2 , a default route is generated and flooded to R3 , but not to R1 . PATH Prefix adjacent router ! The labels constituting the LFIB may not be distributed by LDP , and the RSVP allocation label is used in the MPLS traffic engineering . In the MPLS VPN , OutLabel : Ethernet0/1, 305 To add: In the above environment, the loopback interface cost=1 , and the cost of all other physical interfaces =10 . Then if we configure: R4.00-00 100 Metric Type: TE (default) Route-target export 2345:5 How to view opaque LSA-10 on CISOC IOS router ? Net 49.0001.0000.0000.0001.00 IS-IS uses a simple two-layer structure. The IDP and HODSP are combined to be used as the area ID of the Layer 2 route , and the remaining system IDs are used as the first layer of routing. 10.1.23.0/24 Prior LSP: Reservable Bandwidth[5]: Lost LSPs can be requested by PSNP to see an example: *Aug 18 04:37:06.243: min unit = 0 bytes,max pkt size = 1500 bytes Fa0/0 *Aug 18 04:37:06.239: Hop Addr: 10.1.12.1 LIH: 0x02000403 ! 14 Binding Remote: TSR: 2.2.2.2:0, Tag: 202 !! neighbor R2 prefix 3.3.3.3/32 label allocated *Aug 18 11:31:44.598: Type escape sequence to abort. Tracing the route to 6.6.6.6 Mpls ldp discovery targeted-hello accept from accept-ldp 103 R2(config)#key chain test R2 (config-keychain)#key 1 MPLS TE can change the bandwidth and attribute parameters of the link through adaptation. 205 LSP packet structure Local Outgoing Prefix Bytes Label Outgoing Next Hop Label Label or Tunnel Id Switched interface In-label Out intf/label Therefore, in the above figure, if R5 sends an IPv4 packet to R3 , R3 can directly identify and hash the source and destination addresses of the Ipv4 header to implement load balancing. Use the lockdown keyword (note that the above configuration is configured in the TE tunnel port). SENDER_TSPEC Fast Reroute 0 kbits/sec Locally assigned labels are distributed to neighbors, and if there are multiple connections to a single neighbor, the label is valid on all connections. Then regardless of local We found that the attached-bit before the LSP generated by R2 is gone, but the Overload-bit is set . Now let's go look at the routing table. Is a group or flow of packets that are forwarded along the same path and are treated the same with regard to the forwarding treatment. Next-address loose 10.1.34.4 Activate the MPLS TE extension for each router's OSPF and manually set the RouterID for MPLS TE . LSPID LSP Seq Num LSP Checksum LSP Holdtime ATT/P/OL By default, an OSPF area is not a stub and can be configured as a stub. Mpls traffic-eng tunnels ip rsvp bandwidth *Aug 18 04:37:06.243: Tun Dest: 5.5.5.5 Tun ID: 0 Ext Tun ID: 1.1.1.1 Router(config)#mpls traffic-eng tunnels ISO10589 Physical_bw: 100000 (kbps), max_reservable_bw_global: 75000 (kbps) After the above configuration is completed, there is one more unidirectional direct link to R5 on R2 . This link will directly participate in the routing calculation of R2 itself. The overall result is that there are now three straight connectors on R2 : eth0/0 , eth0/1 , tunnel0 . ! But if the router performing load balancing is a P router, what does it receive is a label package with multiple labels? We know that no matter how many tags you have, the tag stack is followed by the IP header, and the first field of the IP packet is version , if Record Route: NONE LSP Path establishment and maintenance 0 kbits/sec R2 (config-router)#authentication key-chain test level-2 R2 (config-router)#authentication mode md5 level-2 The flooding and interaction of LSPs eventually form the IS-IS link state database. *Aug 18 11:31:44.598: Config Parameters: 5135 lab environment Phenomenon observation The RESVTear message is similar to the RESV except that it is sent when the tail router responds to the received PathTear message. The forwarding adjacency feature will cause the TE router to advertise the TE tunnel as a virtual path (direct link) in the IGP routing protocol area, so that all routers know the existence of the tunnel. The IGP protocol here can be OSPF or IS-IS. Remote binding: tsr: 3.3.3.3:0 , tag: 300 tib entry: 2.2.2.2/32, rev 4 0x80000018 0x001C01 1 AutoRoute: disabled LockDown: disabled Loadshare: 33000 auto-bw: disabled 75000 Redistribute connected level-1 *Aug 18 09:06:02.699: version:1 flags:0000 cksum:5878 ttl:255 reserved:0 length:216 MPLS configuration ( frame mode ) ! Mpls traffic-eng router-id loopback0 mpls traffic-eng area 0 Otherwise, the interface may be considered in MPLS-LDP Discovery Transport interface address , the Transport Address configured as Direct interface IP address. Or Tunnel Id Reservable Bandwidth[0]: R1.00-00 Routing information diffusion and database synchronization 10.1.12.2 [MPLS: Label 203 Exp 0] 200 msec 84 msec 136 msec L1 Device Configuration The tunnel priority ranges from 0 to 7. The smaller the priority, the higher the priority. O 3.3.3.3 [110/3] via 10.1.12.2 , 00:00:37, FastEthernet0/0 Network 10.1.34.4 0.0.0.0 area 0 *Aug 18 09:06:02.699: Path MTU: 1500 Bandwidth information O Interface fas0/0 ! Options: (No TOS-capability, DC) LS Type: Router Links Router(config)# mpls ldp discovery holdtime seconds Network 10.1.34.3 0.0.0.0 area 0 Circuit circuit 5.5.5.5 i ia 10.1.24.0 [115/148] via 10.1.123.2, FastEthernet0/0 O Mpls traffic-eng tunnels mpls label range 500 599 2.2.2.0 [115/20] via 10.1.123.2, FastEthernet0/0 3.0.0.0/24 is subnetted, 1 subnets Tunnel mpls traffic-eng path-option 10 explicit name R2R4R5 1.0.0.1 Packets with the same processing mode according to the process or IP DSCP field *Aug 18 11:26:02.546: *Aug 18 04:37:06.243: STYLE type 1 length 8 : Ip address 10.1.255.1 255.255.255.255 10.1.34.4 10.1.45.4 10.1.45.5 5.5.5.5 Each IP packet forwarded to a router is the same before and after being forwarded through the router. R2#show ip route The configuration of R2 is as follows: R1#show mpls ldp neighbor 75000 104 16 Contains information such as the tunnel sender address, LSP ID, etc. ( NLPID 0x81 ) and IP ( 0xCC ) Router ospf 100 *Aug 18 11:31:44.598: Interface Reserved label Retention mode : Label Retention Bytes tag switched Interface eth0/1 Broadcast multi-access link Time since created: 5 hours, 7 minutes Time since path change: 12 seconds Configured on L1/L2 rouer, which is R2 , a default route is generated and flooded to R3 , but not to R1 . 10.1.34.0/24 TE tunnels are an aggregation of traffic flows of the same class (bandwidth , etc.) which are placed inside a common MPLS LSP Exit-address-family Ip address 55.55.55.55 255.255.255.255 Retention mode (the Label Retention) : free mode (Liberal Retention) R2#sh run | A puts the data on the label 23 , goes to B , and ejects the label header to C ( PHP mechanism); C receives the IP packet to find the FIB table, and then presses the package 55 to D , D finally finds LFIB and Pop the label to drop the IP packet to E , and E forward the IP packet to the destination. Wait for the message to view the adjacency. Next, the DIS election process begins . Establish priority R2-PE1#show ip route Type 7 length 16: Tunnel mpls traffic-eng bandwidth 60000 1bit ! The configuration of R1 is as follows: Ip address 10.1.34.3 255.255.255.0 1.1.1.1:0 State Changed: 02:23:31 C . There is a small detail, noted that the distribution of the label no concept of split horizon, that although B may be from C to learn the route to X , but B still will be prefixed with X passed to the bundled label C . C will also put the label passed from B in the LIB , but don't worry about loops, because LDP can prevent loops by means of IGP routing protocol. Network 10.1.12.1 0.0.0.0 area 0 Router(config)#interface tunnel x I/E If there is a loop (usually a problem with the IGP , such as a misconfiguration of the static route), the TTL in the tag header will prevent the tag packet from being forwarded indefinitely. 0x18B7 ! Local binding: tag: 104 Priority 3 : 9375000 In the LSP , and if the LSP is divided into different segments, then the TLV word LSPID LSP Seq Num LSP Checksum LSP Holdtime ATT/P/OL IS-IS Adjacency related packets debugging is on R1# Ip address 10.1.123.3 255.255.255.0 LDP discovery sources: i ia 10.1.24.0 [115/148] via 10.1.123.2, FastEthernet0/0 On the R3 , as shown in the figure, the R3 local routing table does not need a default route, and an IS-IS default route can be generated and passed to *Aug 18 09:06:07.919: EXPLICIT_ROUTE type 1 length 68: *Aug 18 09:06:07.919: Tun Sender: 1.1.1.1 LSP ID: 247 Network 2.2.2.2 0.0.0.0 area 0 Configuration command Network 2.2.2.2 0.0.0.0 area 0 1.0.0.0 R3(config)#Interface tunnel 0 ! 0 kbits/sec PATH *Aug 18 09:06:02.699: State: explicit path option 10 is active R1# traceroute 5.5.5.5 !! OSPF cost of the interface 1.0.0.0/24 is subnetted, 1 subnets Local Label R1 from eth0/1 to R5 , cost=20+1=21 of this path Reservable BW (kbps) Contains information such as the tunnel destination address, tunnel ID , and extended tunnel ID (that is, the tunnel start point) Generate a default route to this device as the egress route by ATT bit with its nearest L1/L2 router Router-id 2.2.2.2 Router isis Perform routing protocol functions in the routing domain Router ospf 1 IS-IS Mpls traffic-eng tunnels ip rsvp bandwidth The loopback0 address space of all devices is xxxx/32 , and x is the device number. Understand the forwarding process of data in the MPLS domain Frame-relay map ip 10.1.123.2 201 broadcast Build an IP routing table All tag mapping messages received locally from the neighbor are saved in the database. 0xD3FB Tunnel mpls traffic-eng path-option 10 dynamic Type block This is 1B , which contains a number of important bits: Enable the MPLS TE tunnel feature globally, which is equivalent to a global switch. Mainly contains TE tunnel bandwidth request Tunnel mpls traffic-eng autoroute metric x For all practical applications, IS-IS only supports broadcast and point-to-point links. The NBMA link is not supported . In the NBMA environment, it can be equipped Res. Global BW: 75000 kbits/sec !! interface's maximum reservable bandwidth Admin: up Remote binding: tsr: 3.3.3.3:0 , tag: 300 tib entry: 2.2.2.2/32, rev 4 Manually reoptimize Tib entry: 10.1.23.0/24, rev 8 Configure on R2 as follows: Note that this 303 obviously, is R3 assigned to this allocation result and then to R4 , R4 is with R3 label assigned to pressure to Ip unnumbered loopback 0 tunnel destination 5.5.5.5 tunnel mode mpls traffic-eng 17 Alternatively, you can configure the following command on the tail router: Additional Knowledge: Label-to-label TTL diffusion behavior in SWAP , PUSH , POP operations 75000 Src 2.2.2.2, Dst 5.5.5.5, Tun_Id 0, Tun_Instance 5 RSVP Path Info: Remote binding: tsr: 2.2.2.2:0, tag: 200 Route-map test permit 10 router isis 10.1.34.3 10.1.34.4 O In a network running MPLS , you can set these two paths to different LSPs and use different labels. On R1 , R6 and To perform the same network segment check (the adjacency must be on the same network segment) Experiment 2 IP interface address Fspec: ave rate=0 kbits, burst=1000 bytes, peak rate=0 kbits History: Mpls traffic-eng tunnels ip rsvp bandwidth System Id Type Interface IP Address State Holdtime Circuit Id ADV Router RFC 2966 Experimental procedure Switched Interface Tunnel0 OutLabel : Ethernet0/1, 305 Prefix Interface eth 0/2 0x2B7C *Aug 18 11:26:02.546: SESSION Therefore, the MPLS VPN environment, if we MPLS VPN Backbone inherent R1 to R5 establish a TE the Tunnel , is not 3.3.3.3 How MPLS LDP-IGP synchronization works 0180-C200-0015 ES-IS Routing Protocol Targeted Hello 1.1.1.1 -> 3.3.3.3, active, passive As above, pay attention to the order of input. 0/0/0 Forwarding tagged messages How long in msecs to wait upon flooding a down forwarding adjacentcy L2 router Record_route R2-PE1#show ip route TE metric: 1, IGP metric: 1, attribute_flags: 0x0 10.1.23.3 Send out from the Fa1/0 port. So, R2 replaces the tag with 300 and then throws it to R3 . TTL TIME_VALUES Mpls traffic-eng tunnels ip rsvp bandwidth Untagged Contains information such as the tunnel sender address, LSP ID, etc. No output feature configured Bandwidth parameter is the bytes as a unit Label space : Label Space 75000 Understand the forwarding process of data in the MPLS domain R2.00-00 The output of the CSPF algorithm is an IP interface address sequence (next hop router address) between the two endpoints of the tunnel . Each LSP has a maximum expiration time ( MaxAge ) in the LSDB . If this time expires, if no new LSP is received. Selecting designated routers in the broadcast network to control the spread and reduce the system resource requirements of many-to-many neighbors in such media Configure the tunnel to use a statically specified path or a dynamic path calculated through the TE topology database. Ip cef HELLO PDU (ESH , ISH and IIH) Provide a loop-free network Interface eth 0/0 Ip unnumbered loopback 0 tunnel destination 5.5.5.5 tunnel mode mpls traffic-eng Let's experiment one by one: ! Net 49.0001.1111.2222.3333.00 UP 28 Fa0/0 0 kbits/sec Explicit empty label ADSPEC 0 kbits/sec CSNP Fa0/0 Mpls traffic-eng router-id loopback0 mpls traffic-eng area 0 ID: path option 10 [36] Router-id 5.5.5.5 Interface fast 0/0 Network 10.1.45.4 0.0.0.0 area 1 Mpls traffic-eng tunnels ip rsvp bandwidth 8bit maximum 255 , usually in the labeling when it is the ordinary ip packet TTL direct copy came Mpls traffic-eng tunnels mpls label range 400 499 Router# mpls traffic-eng reoptimize *Aug 18 09:06:07.919: Network 10.1.45.5 0.0.0.0 area 0 The configuration of R1 is as follows: Interface R1 has already completed the collection of its own TEDB information, and the calculation process of the tunnel path is completed on R1 . Admin: up Oper: up Path: valid Signalling: connected R1.00-00 Bandwidth change Fa0/0 OSI network layer addressing is achieved by using two types of hierarchical addresses: NSAP and NET . Link connected to: a Transit Network LSP TLV field of Level 2 route !! Set overload-bit to suppress external routing Activate RRO with the following configuration: Document number *Mar 1 00:00:32.763: ISIS-Upd: Important fields changed Remote binding: tsr: 2.2.2.2:0, tag: 202 tib entry: 10.1.23.0/24, rev 12 Auto-bw: disabled Let's experiment one by one: ATT/P/OL Router ospf 1 twenty two Tunnel mpls traffic-eng priority 6 6 To update the LSDB , the LSP will be cleared from the LSDB . After the old LSP is cleared from the LSDB , it will remain for a while. OSPF ensures the reliability of diffusion across all links Ip address 10.1.24.2 255.255.255.0 R3.00-00 Complete basic IP configuration (configuration omitted) Peak rate 5.5.5.5 [110/31] via 10.1.23.3, 00:02:29, Ethernet0/1 In interface configuration mode: isis circuit-type allows the interface to work at level-1 level-1-2 or level-2-only Device Internet segment 10.1.xy.0 / 24 , where xy is the device number, X small y large The target network segment involved in MPLS is the same as traditional IP forwarding. Ip cef ! Mpls traffic-eng tunnels ip rsvp bandwidth The POP will only pop the top label header. The packet forwarded by this action can be an IP packet or an MPLS label packet. Ip router isis FastEthernet1 / 0, Src IP addr: 10.1.13.3 Addresses bound to peer LDP Ident: CSPF algorithm working mechanism Redistribute isis ip level-2 into level-1 route-map test !! Cross-regional words must use loose next hop For Level1 router , the area number is required to be the same. 75000 ! Interface fast0/0 Mpls traffic-eng tunnels mpls label range 200 299 Then R1 will limit the establishment of targeted session of the peer , is 3.3.3.3 , which is R3 of LDP routerid , in addition, LDP session protection time is 30S , that is to say, 30S If the LDP neighbors yet up, targeted session will fail. Naturally, the protected tag information stored in the LIB is gone. *Aug 18 04:37:06.239: Tun Dest: 5.5.5.5 Tun ID: 0 Ext Tun ID: 1.1.1.1 Globally activate MPLS TE tunnel and set MPLS label space 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. R1 is isis neighbor directly is empty, because it ignores received on this interface R2 of hello packets. Advertising Router: 1.1.1.1 LS Seq Number: 80000001 !! Change the TE tunnel 's setup priority and hold priority to 5 Ip rsvp bandwidth Reference book 0/0/0 See if you receive HELLO from the other party Is-type level-1 metric-style wide Mpls traffic-eng router-id loopback0 mpls traffic-eng area 0 !! Backup tunnel Explicit Route: 10.1.12.2 10.1.24.2 10.1.24.4 10.1.45.4 Information, as shown below: Fa0/0 Test 2 : SET-overload-ON-Startup 'bit the wait-for-BGP Ip explicit-path name R2R4R5 enable next-address 10.1.12.2 ! A targeted LDP neighbor relationship has been established with R4 . If a router plurality of distribution on the net, these NET system ID must be the same. Regional separation TE metric: 1 FR The DLCI R1#show mpls traffic-eng tunnels 1096 The configuration of R2 is supplemented as follows: Src 1.1.1.1, Dst 5.5.5.5, Tun_Id 0, Tun_Instance 31 RSVP Path Info: R2.00-00 Each ES belongs to a specific area, when the ES finds the nearest IS by listening to the HELLO ( ISH ) grouping of the intermediate system . *Aug 18 04:37:06.239: Tun Sender: 1.1.1.1 LSP ID: 20 Enable the MPLS TE tunnel feature globally, which is equivalent to a global switch. Bw[4]: [Note] Label behavior of Frame Mode <0x0-0xFFFFFFFF> Attribute flags ! Tunnel mpls traffic-eng autoroute announce tunnel mpls traffic-eng priority 7 7 Ip cef Show and debug Name: R1_t0 Status: ... ... ... ... We open interface authentication between R1 and R2 : PUSH is also similarly understood, only for top-level label operations, first the inbound top-level label TTL249 is first decremented by 1 , then the newly pushed label header TTL Bandwidth information ! 10.1.24.0 [115/20] via 10.1.123.2, FastEthernet0/0 O If the LSR receives an IP packet, check the FIB table. Assume that the FIB ( CEF table) related entries are output as follows: ! [4]: 4.4.4.0/24 *Aug 18 09:06:07.919: ADSPEC type 2 length 48: MOSPF extension provides support for IP multicast routing Type block This is 1B , which contains a number of important bits: The interface of each router activates RSVP and MPLS TE tunnel support. 103 Network 10.1.34.4 0.0.0.0 area 0 Here are a few things to note: 0x2D6E The configuration of R3 is as follows: 0/0/0 DIS send HELLO interval ordinary packet router of 1/3 (default 3.3s ), which ensures DIS when a failure occurs can be more quickly found. HELLO PDU (ESH , ISH and IIH) The database is also calculated by the CSPF algorithm, and the result is the path of the tunnel — a sequence of IP addresses. Turn off TTL propagation NLPID: Removal Trigger: configuration changed Tunnel mpls traffic-eng autoroute announce tunnel mpls traffic-eng priority 7 7 ! Experimental phenomena 75000 Ip address 10.1.24.2 255.255.255.0 302 Ip cef 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 : Ciphertext LSPs authentication ( Level2 ) Version=0 length in words=10 We see that on R2 , about 5.5.5.5 and 55.55.55.55, the R5 is the "rear" network at the end of the tunnel . The outgoing interface is tunnel0 . This means that when R2 receives data destined for these two network segments, it is placed directly into the TE tunnel . Compared to the way static routes are placed, the advantages of autoroute are shown. IS-IS Level-1 LSP R1.00-00 !! Set overload-bit to suppress inter - area routing Mpls traffic-eng router-id loopback 0 mpls traffic-eng level-1 Tunnel mpls traffic-eng bandwidth 60000 LDP discovery sources: On CISCO IOS 12.4 , Acl tried it with standard and extended access control lists. If it is unsuccessful, even acl permit any will not work. Matching the route with the prefix list is successful. LS age: 29 Then the LSR pushes the IP packet into a tag header, tags 204 , and forwards it out from the F0/0 interface. In CISCO IOS , CEF switching is the only IP forwarding mode that can be used to mark messages . Therefore , CEF must be enabled on the router when MPLS is enabled . Maximum bandwidth : 12500000 Since the IP prefix in the IS-IS area is the leaf of the SPF tree, part of the route calculation ( PRC ) is more, usually this means that in one *Aug 18 11:26:02.546: The IS-IS related interface is Up or Down . Debug ip rsvp dump-messages 0 interfaces: The attribute tag is a 32-bit field, which is described in detail later. 10.1.45.4 Ip unnumbered Loopback0 tunnel mode mpls traffic-eng tunnel destination 5.5.5.5 Active Path Option Parameters: Three-Way Handshake for IS-IS Point-to-Point Adjacencies neighbor is a neighbor of the LDP routerID accept acl to match the prefix Record Route: NONE Use the following command to see the relevant information: Activate the MPLS TE extension for each router's OSPF and manually set the RouterID for MPLS TE . Use the lockdown keyword (note that the above configuration is configured in the TE tunnel port). SNPA We see that on R1 , the outgoing label of the relevant route prefix is untagged . The R1 's routing table temporarily without any change. In this environment now, although R1 still be able to ping through 3.3.3.3 , but in fact has a problem, because it is a direct walk IPv4 packets, rather than the package label. 5.5.5.5 !! Re-release the local direct loopback 2.2.2.0/24 to level1 10.1.34.4 [MPLS: Label 400 Exp 0] 0 msec 12 msec 8 msec The configuration of R2 is as follows: IP 1.1.1.0 255.255.255.0 IS R3.02 Session_Attibute The level2 route is injected into the level1 area ,ccna lab questions and answers pdf, and these level2 routes can be summarized on the L1/L2 router . The configuration is as above. i ia 5.5.5.0 [115/158] via 10.1.123.2, FastEthernet0/0 10.0.0.0/24 is subnetted, 4 subnets OutLabel : Ethernet0/1, 304 ! MPLS TE considers configuring (static) bandwidth on the link Physical_bw: 100000 (kbps), max_reservable_bw_global: 75000 (kbps) R5 configuration is as follows R1#show isis da R3.02-00 detail 947 Let's experiment one by one: Prefix Network 10.1.12.1 0.0.0.0 area 0 mpls traffic-eng router-id loopback0 mpls traffic-eng area 0 101 If the PSNP acknowledgment is still not received after the retransmission timout , the originating router will retransmit the LSP. Ip address 5.5.5.5 255.255.255.255 0 kbits/sec 0/0/0 Initialization message After the above configuration is completed, there is one more unidirectional direct link to R5 on R2 . This link will directly participate in the routing calculation of R2 itself. The overall result is that there are now three straight connectors on R2 : eth0/0 , eth0/1 , tunnel0 . !! Specify the range of local tags, this can be a great convenience in the experiment Tunnel mpls traffic-eng path-option 10 dynamic Prefix Route-map test permit 10 router isis Clns host RouterA 49.0001.1111.2222.3333.00 clns host RouterB 49.0001.4444.5555.6666.00 OSP PDU R1#show mpls ldp bindings (View the LIB table of R1 ) Router isis 75000 A list of directly connected IP address prefixes is listed, which is only used in non-pseudo-node LSPs . Ip unnumbered loopback 0 tunnel destination 2.2.2.2 tunnel mode mpls traffic-eng IDI Initial Domain Identifier , a variable-length initial domain identifier that identifies a subdomain under AFI Reservable Bandwidth[7]: RFC1195 The L1 router only forms an adjacency with the L1 router (or L1/L2 router ) in this area. [5]: 75000 kbits/sec *Aug 18 09:06:02.699: version=0, length in words=7 Mainly used to replace type 2 TLVs to provide larger metrics. In addition, it also supports IS-IS based MPLS TE *Aug 18 09:06:07.919: Interface eth 0/0 0/0/0 The forwarded keyword indicates that this command is valid for traffic traversing the router. The Local keyword indicates that the traffic generated locally is effective. Network Services Access Points 0 kbits/sec 2.0.0.0/24 is subnetted, 1 subnets The configuration of R4 is as follows: ! The average allocated traffic on the interface. 101 Path: valid Redistribute connected level-1 Frame-relay map ip 10.1.123.2 102 broadcast *Aug 18 11:26:02.546: Label Separation of the specified layer 2 intermediate system Partial sequence number packets ( PSNP ) partial serial number packet RFC 2966 Router(config-if)# mpls traffic-eng path-option x {dynamic | explicit name y } [ lockdown ] 10.1.12.2 Only when a neighbor solicitation label mapping message to the local strip prefix , local will announce the label mapping messages to neighbors Activate RSVP on the interface and configure reserved bandwidth (optional) 2.2.2.2/32 We found that R2 can learn to R1 of the Loopback , R3 of the Loopback , and R3 directly connected interface routing of 34.0 , which is due to R4 pass R3 and R2 passed R3 of LSP did not carry the authentication information, then these LSPs to R3 after, R3 is definitely an error, so R3 will not flood the original LSP sent by R4 to R2 , and 3 will not flood the original LSP sent by R2 to R4 . However, R3 sends out its own LSP.There are R3 directly connected network segments 3.3.3.0 and 10.1.23.0 , 10.1.34.0 . These LSPs are flooded to R2 and R4 . Although LSPs carry TLV information for authentication , R2 and R4 do not open domain. Certification, so they directly ignore the certification information and then start reading LSP , which is the interpretation of the results of our experiments. Of course, if R2 and R4 are configured with domain-password but the password is different from other devices, then it goes without saying that directly discarding LSPs with different passwords will not be read at all.