ccna exam question paper

ccna exam question paper

2.2.2.2/32 The target network segment involved in MPLS is the same as traditional IP forwarding. *Aug 18 04:37:06.239: version=0, length in words=7 The loopback0 address space of all devices is xxxx/32 ,ccna exam question paper, and x is the device number. IGP Area[1] ID:: ospf area 0 System Information:: Interface eth 0/1 Tib entry: 10.1.12.0/24, rev 4 ! R2.00-00 Traditional IP routing only considers metric when routing . For example, if we are running OSPF in the above figure , then R1 to 1.0/24 and 2.0/24 will preferably be from R2 to R3 . Path because the metric is small. Then this directly causes the idle of another optional path and the excessive congestion of the main path. *Aug 18 09:06:07.919: Outgoing PathTear: Mpls traffic-eng tunnels mpls ip MPLS TE tunnels, also known as Traffic trucks , are used to overcome hop-by-hop IP routing defects. Traditional TTL operation Router(config-if)#tunnel mpls traffic-eng path-option x {dynamic | explicit {name path-name | IP external reachability information Mpls traffic-eng reoptimize events link-up 10.1.23.3 [MPLS: Label 300 Exp 0] 4 msec 0 msec 4 msec Interzones can only be interconnected via L2 or L1/L2 routers *Aug 18 09:06:07.919: Minimum Path Bandwidth (bytes/sec): 2147483647 Activate the fast-reroute feature on R1 and observe the phenomenon Note: IS-IS 's Backbone is not what a particular area Types of Mpls traffic-eng tunnels mpls ip Router bgp 2345 Point3 i ia 10.1.24.0 [115/148] via 10.1.123.2, FastEthernet0/0 0 packets, 0 bytes 201 Addresses bound to peer LDP Ident: (Tunnel0) Destination: 4.4.4.4 Router ospf 1 Configure path protection on R2 and observe the phenomenon. Route-target import 2345:5 1.1.1.1 ...... ...... Take a look at the routing table for R1 : For the HDLC (Advanced Data Link Control) interface, SNPA is set to " HDLC " The configuration of R4 is as follows: Router(config)#tunnel mpls traffic-eng path-selection metric igp Router-id 2.2.2.2 Tspec: ave rate=0 kbits, burst=1000 bytes, peak rate=0 kbits RSVP Resv Info: (Link ID) Designated Router address: 10.1.12.1 (Link Data) Router Interface address: 10.1.12.2 Number of MTID metrics: 0 Tunnel mpls traffic-eng bandwidth 60000 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. i L1 This command will cause the tail router to advertise implicit empty labels. (default action notification explicit empty label) 687 Tunnel mpls traffic-eng priority 5 5 R1#show mpls traffic-eng tunnels Keep priority A route 10.1.1.0/24 on E was advertised, and now it is summarized on C. The summary route is 10.1.0.0/16 and is advertised to B. Advertising Router: 1.1.1.1 LS Seq Number: 80000001 Tunnel mpls traffic-eng path-option 10 explicit name R2R4R5 no routing dynamic Network 10.1.45.5 0.0.0.0 area 0 RFC3209 RSVP-TE Extensions to RSVP for LSP tunnels describes the extension of MPLS TE function by RSVP protocol . Tunnel mpls traffic-eng autoroute metric absolute resolution if the configuration of R2 is changed to: A targeted LDP neighbor relationship has been established with R4 . Protocols support Mpls traffic-eng tunnels ip rsvp bandwidth *Aug 18 04:37:06.243: service id = 5, service length = 6 The configuration of R1 is as follows: Bytes tag Remote binding: tsr: 2.2.2.2:0, tag: 200 Router ospf 100 Bw[5]: The first label is applied on the ingress LSR and the label belongs to one LSP. The path of the packet through the MPLS network is bound to that one LSP. All that changes is that the top label in the label stack is swapped at each hop The ingress LSR imposes one or more labels on the packet. The intermediate LSRs swap the top label (the incoming label) of the received labeled packet with another label (the outgoing label) and the transmit the packet on the outgoing link. The egress LSR Of the LSP strips off the labels of this LSP and forwards the packet.