ccna previous year question paper

ccna previous year question paper

*Aug 18 09:06:07.919: Path Latency (microseconds):0 The interface of each router activates RSVP and MPLS TE tunnel support. Version = 0 length in words = 7 service id = 5, service length = 6 Physical Bandwidth: 100000 kbits/sec Res. Global BW: 75000 kbits/sec Res. Sub BW: 0 kbits/sec Downstream:: Bandwidth: 20000 kbps (Global) Priority: 7 7 Affinity: 0x0/0xFFFF Metric Type: TE (default) Ip router isis interface Serial0/0 TE metric is a parameter used to build a TE topology that is completely different from the IP topology (although by default it is equal to IGP metric ) EXP To meet the above requirements, IS-IS is designed as a link state routing protocol and uses the SPF shortest path first algorithm to achieve fast convergence and loop-free networks. Error metric optional, link error probability, not supported Path Protect Parameters: Link[0 ]:Nbr IGP Id: 10.1.12.2, nbr_node_id:8, gen:47 frag_id 0, Intf Address:10.1.12.1 Reservable Bandwidth[5]: Router ospf 1 vrf VPN-A redistribute bgp 2345 subnets network 10.1.56.5 0.0.0.0 area 0 The routing table for R1 is as follows: Priority 2 : 9375000 Two modes: frame mode ; ATM mode ( cell mode ), we mainly study frame mode Global Pool 0xD3FB 0x00000011 The label header has a total of 32 bits and contains the following fields: Mpls traffic-eng tunnels ip rsvp bandwidth Peer LDP Ident: 3.3.3.3:0; Local LDP Ident 1.1.1.1:0 Tun Dest: ! Router-id 1.1.1.1 After the above configuration, we will find, R1 can learn to R2 , R3 route, but R2 , R3 between can not learn the route to the peer. Current LSP: 10.1.12.2 !! Don't forget the mapping of CLNS 3.3.3.3 Prefix Local If the label space of 2B is 0 , then it is based on the label space of the device. If it is non- zero , it means that the interface space is used. In this case, multiple LDP IDs can be used . The first 4 bytes of these LDP IDs are the same, but the last 2 bytes identify different label spaces. The label space based on each interface is used for LC- ATM . Describes all LSP information in the LSP database . Intermediate system IS *Aug 18 09:06:07.919: SENDER_TEMPLATE type 7 length 12: R3 to 304 replace 404 . Note that both 304 and 404 are RSVP- assigned tags, so we should still pay attention to the tunnel when viewing the tags . The above table entry, 2.2.2.2 0[5] , be careful not to make a mistake, not the label corresponding to the prefix 2.2.2.2 ,ccna previous year question paper, but the label corresponding to this tunnel . *Aug 18 09:06:02.699: Hop Addr: 10.1.12.1 LIH: 0x20000403 Basic concept of FRR !! TE metric , the default is equal to the following IGP metric Admin. Weight: 1 Network 10.1.12.1 0.0.0.0 area 0 Ip address 10.1.45.4 255.255.255.0 Configure the requested bandwidth of the tunnel Router(config-if)# mpls traffic-eng path-option x {dynamic | explicit name y } [ lockdown ] Interface eth 0/0 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 , 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 . Router bgp 123 Outgoing interface Indicates whether the LSP is from L1 router or L2 router . This field is 2bits . 00- not used; 01-level1 ; 10- unused; 11-level2 In all remote labels that bundle a particular prefix , the LSR uses only one of the labels to determine the outbound label for the prefix. RIB , which is the routing table, determines what the next hop of the IPv4 prefix is. The LSR selects the label of the next hop in the routing table that reaches the prefix from the remote label received by the downstream LSR . The LSR uses this information to create its own label forwarding information base, LFIB .