ccna exam sample questions pdf

ccna exam sample questions pdf

130 !! Only one interface activates MPLS TE Tspec: ave rate=0 kbits,ccna exam sample questions pdf, burst=1000 bytes, peak rate=0 kbits RSVP Resv Info: Can be used on R5 : Mpls traffic-eng tunnels ip rsvp bandwidth Interface eth 0/0 Metric: 10 Mpls traffic-eng router-id loopback0 mpls traffic-eng area 0 Mpls traffic-eng tunnels ip rsvp bandwidth Router-id 5.5.5.5 Tunnel priority Ip address 5.5.5.5 255.255.255.255 13 Router ospf 1 OSPF is routerID Use the lockdown keyword (note that the above configuration is configured in the TE tunnel port). *Aug 18 11:26:02.546: The HELLO packet is sent to the multicast address 224.0.0.2 , and the source address is the interface IP. Outgoing Ip address 2.2.2.2 255.255.255.255 10.1.24.2 10.1.24.4 75000 !! Set overload-bit to suppress external routing R2-PE1#show mpls traffic-eng tunnels Or Tunnel Id [Supplement] The non-pseudo-node LSP represents a router , including all ISs and LANs connected to this router . RFC 2966 Ip address 4.4.4.4 255.255.255.255 R1 advertisement Loopback route .1.1.1.1 / 32 Route leak The configuration of R4 is as follows: 203 By default, an OSPF area is not a stub and can be configured as a stub. IS-IS packets carry all easily expandable information using TLV fields Net 49.0001.0000.0000.0003.00 Interface eth 0/0 10.1.12.2 OSPF adjacency does not DOWN , then R1 routing table, about 3.3.3.3/32 still choose R2 as the next hop, this is a problem. In the LFIB on R1 , the entry for 3.3.3.3/32 might look like this: R1.00-00 Complete basic IP configuration (configuration omitted) Fspec: ave rate=2000 kbits, burst=1000 bytes, peak rate=2000 kbits History: Types of 10.1.23.3 [MPLS: Labels 300/403 Exp 0] 0 msec 4 msec 0 msec Affinity Bit : 0x0 IGP Metric : 1 R2#sh isis neighbors Reservable Bandwidth[2]: Global Pool BW Unreserved: Calculated. In the figure above, the red path is calculated by CSPF . The LSP overload-bit generated by this router is set. This will cause the router to not be used by other routers as the next hop to any destination, except for its locally connected network segment. This is generally used when the router is a leaf node, that is, the end of the network, directly connected to the user. 2.2.2.2 System Id 0x00000029 Local binding: tag: 103 !! Locally assigned label for prefix 3.3.3.3/32 Virtual circuit ID of X.25 or ATM C 1.1.1.0 is directly connected, Loopback0 2.0.0.0/24 is subnetted, 1 subnets !! This is the mapping of IP Frame-relay map ip 10.1.123.2 102 broadcast The L1 router only forms an adjacency with the L1 router (or L1/L2 router ) in this area. Since the IP packet is generated on the initial router, the CEF table is searched . With the " show ip cef detail " command, you can see from the output whether the route is pushed into the label. The distribution label is based on The prefix in the CEF table is assigned. 2 Indicates whether the LSP is from L1 router or L2 router . This field is 2bits . 00- not used; 01-level1 ; 10- unused; 11-level2 Area address In a network running MPLS , you can set these two paths to different LSPs and use different labels. On R1 , R6 and To add: In the above environment, the loopback interface cost=1 , and the cost of all other physical interfaces =10 . Then if we configure: ! SNPA is equivalent to the Layer 2 address of NSAP or NET . Otherwise, the interface may be considered in MPLS-LDP Discovery Transport interface address , the Transport Address configured as Direct interface IP address. Uptime: 9 minutes, 33 seconds Selection: reoptimation 0xE7D9 Fa0/0 Type 1 length 12: Interface Ethernet0/1 The configuration of R2 is as follows: !! Set overload-bit to suppress external routing MPLS VPN Architecture Volume 2 Explicit Route: 10.1.12.2 10.1.23.2 10.1.23.3 10.1.34.4* The label header has a total of 32 bits and contains the following fields: As with regular IP routes , OSPF floods LSAs when the interface is up or manually modified for IGP interface parameters. Tunnel priority 103 L1/L2 router Another example of causing IGP and LDP to be out of sync is that when the LSR is restarted, the IGP can quickly establish an adjacency, and the LDP session may be set up slowly, that is, the necessary information is loaded in the LFIB . IGP forwarding has already begun before the correct label exchange . The message may then be forwarded incorrectly or dropped somewhere after entering the MPLS network.