ccna practice exam 2016

ccna practice exam 2016

The router address TLV carries the router TE router ID for the TE . Types of The TEDB already has link state information in all areas, so there is no need to use the IGP routing protocol. Interface loopback0 ip router isis Interzones can only be interconnected via L2 or L1/L2 routers MPLS TE considers the attribute parameters of the link (such as delay, jitter, etc.) Mpls ldp router-id Loopback0 Route-target import 2345:5 Tunnel mpls traffic-eng path-option 10 dynamic ---------- Experimental procedure The configuration of R5-PE2 is as follows: Network 10.1.23.2 0.0.0.0 area 0 mpls traffic-eng router-id loopback0 mpls traffic-eng area 0 [1]: 75000 kbits/sec *Aug 18 04:37:06.243: version:1 flags:0000 cksum:FFAA ttl:255 reserved:0 length:92 The table eventually forwards this IP packet. C made two searches. This reduces forwarding efficiency. R2#show mpls traffic-eng fast-reroute database Mpls traffic-eng tunnels ip rsvp bandwidth 0x00000014 Physical Bandwidth: 100000 kbits/sec Res. Global BW: 75000 kbits/sec Res. Sub BW: 0 kbits/sec Downstream:: Local binding: tag: imp-null Mpls traffic-eng tunnels mpls label range 200 299 *Aug 18 09:06:02.699: HOP type 1 length 12: ! Router ospf 1 Environmental description 0 kbits/sec Interface eth 0/1 Obviously due to the lost and R3 direct link, R1-R3 between the LDP adjacency hung up, in terms of natural LIB table, before R3 pass over the bundled label will be lost, and now, if R1-R3 Between the link replies, they have to re-establish LDP adjacency and resend the label bundle. - Parameter id=127, flags=0, parameter length=5 Local binding: tag: 101 3bit experimental bits for QoS *Aug 18 09:06:07.919: Tun Dest: 5.5.5.5 Tun ID: 0 Ext Tun ID: 1.1.1.1 ! Tunnel mpls traffic-eng autoroute metric absolute 32 R1#show ip route 5.5.5.0 *Aug 18 09:06:07.919: Session Name: R1_t0 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. Now we will complete the following configuration on R2 : Path: valid Interface Loopback0 !!! Link Sharing Detail: 55000 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. ! Src 1.1.1.1, Dst 5.5.5.5, Tun_Id 0, Tun_Instance 521 RSVP Path Info: 0x0000000C IS R3.00 Config Parameters: The introduced IP route changes. !! Change the TE tunnel 's setup priority and hold priority to 5 75000 Dynamic Hostname Exchange Mechanism for IS-IS State RESV AFI+IDI is used to identify the Domain 5.5.5.5 [110/31] via 10.1.23.3, 00:03:44, Ethernet0/1 Interface eth0/0 We see that the forwarding aspect of the data is this: Tunnel mpls traffic-eng path-option 10 explicit name R3R4 0x00000010 Ip unnumbered Loopback0 tunnel mode mpls traffic-eng tunnel destination 5.5.5.5 Ip router isis ( NLPID 0x81 ) and IP ( 0xCC ) *Aug 18 04:37:06.239: parameter id=127, flags=0, parameter length=5 *Aug 18 09:06:07.919: SENDER_TSPEC type 2 length 36: Therefore, the main functions of RSVP are: * 0x0000000C Net 49.0002.0000.0000.0004.00 Although R5 and R6 can learn each other's routes,ccna practice exam 2016, they cannot communicate with each other because routing black holes appear on R2 and R3 . The solution is to use MPLS , we turn the Core into an MPLS domain: OO lab environment Each transport layer entity is assigned an NSAP address. The NSAP address is the network layer address of the CLNS packet . It is used to identify the device. It consists of an initial domain part ( IDP ) and a domain-defined part ( DSP ). These two parts are detailed below, let us understand this. Reservable Bandwidth[1]: Each IP prefix is ​​assigned a bunch of metrics . ----------- Mpls ldp router-id Loopback0 0x8973 O Hop Addr: 10.1.12.2 LIH: 0x0D000408 Network 10.1.12.2 0.0.0.0 area 0 IS-IS Level-1 Link State Database: When forwarding, if the destination address is present in the area within, the direct use of L1 LSDB routes generated forward packets, if the destination address is not in the region, the use of this area nearest L1 / L2router as an outlet outside the area network, whereby May cause sub-optimal routing For the highest loopback port IP R1#traceroute 4.4.4.4 Then R1 and R3 receive a label mapping with a prefix of 2.2.2.0/24 and a label of 3 . At the same time, they also received the R2 updated route. Since the loopback interface route is updated by OSPF by default, it is updated in /32 mode. Therefore , the route learned on R1 and R3 about 2.2.2.2 is /32 bit. of. Then this is a problem, my routing entry is 2.2.2.2/32 , but the label message you sent me is 2.2.2.0/24 , it doesn't match, so R1 thinks that the label is going to Not 2.2.2.2 , just give an untagged , just like the LFIB table we saw for R1 . In this way, when R1 receives the label package and goes to 2.2.2.2 ,R1 will pop up the label stack of the label package, then find its own FIB table and forward the message out. This seems to be no problem in this topology, but in many environments, there will be problems, such as MPLS VPN . So how to solve it? Very good, R2 loopback port to an ip ospf network point-2-point , or change the mask.