ccna practise questions

ccna practise questions

Ip cef PDU length : the length of the entire PDU , including the header ! Route-map test permit 10 router isis Summarize on the L2 router , summarize the locally originated routes, configure as above If the weight issue orders without the level parameter, the default is as shown level2 parameters, that is, inject external routes into level2 in this way level2 area can learn to this external routes, but level1 area in Can't learn because R2 is at level1 (Tunnel0) Destination: 4.4.4.4 Used to publish a complete link state database on a router , CSNP is used to inform other routers of their own database may be outdated or lost LSP . IGP floods TE information when: Untagged Attached-bit Provide the best route for the network The load of the routing processor is low in large areas R3.00-00 Interface fast0/0 For prefix-access-list – the IP access list that selects the destinations for which the labels will be *Aug 18 09:06:07.919: ERROR_SPEC type 1 length 12: Metric: 0 Router ospf 1 Interface eth 0/0 If the L1 / L2 router redistributed external routes to Level-1 , the Level1 area in you can learn the route, but R2 does not route injection Level2 area is Backbone of Interfaces: Fa0/0 Mpls ldp neighbor 3.3.3.3 targeted ldp Activate the fast-reroute feature on R1 and observe the phenomenon ES-IS Routing Protocol 10.1.12.2 Source routing, policy routing, static routing, etc. Redistribute isis ip level-2 into level-1 route-map test Integrated IS-IS ( IS-IS ) enables the IS-IS protocol to propagate routing information for protocols other than CLNP . 2.2.2.2/32 Extended intermediate system reachability TLV (type 22 ) !! Use strict next hop directly in this area Fa0/0 *Aug 18 04:37:06.243: Tun Dest: 5.5.5.5 Tun ID: 0 Ext Tun ID: 1.1.1.1 The default LDP label space is platform-based per-platform or device-based. What do you mean? Let's look at the B router, which bundles the label 34 for the prefix X , and publishes the label binding information to all LDP neighbors, which is the same for everyone, and everyone has a label 34 . This is based on the platform. Then there is an interface-based tag space. Net 49.0001.0000.0000.0002.00 MPLS mode Mpls traffic-eng tunnels ip rsvp bandwidth Interface eth 0/1 1.1.1.1 [110/3] via 10.1.34.4, 00:53:36, FastEthernet1/0 Attribute Flags: 0x00000000 If a tunnel1 establish priority than the tunnel2 high hold priority, then tunnel1 be able to seize tunnel2 If the sysID length is inconsistent, the IIH is ignored . Ip address 3.3.3.3 255.255.255.0 ip router isis Then just fill in the configuration on R2 . I won't go into details here. Support IP classless routing prefix (support VLSM ) Mpls traffic-eng tunnels ip rsvp bandwidth RFC1195 Ip unnumbered Loopback0 tunnel mode mpls traffic-eng tunnel destination 5.5.5.5 Fspec: ave rate=0 kbits, burst=1000 bytes, peak rate=0 kbits History: Network 5.5.5.5 0.0.0.0 area 0 ! Ip router isis Experimental verification Interface eth 0/1 IS-Extended R2.01 0 kbits/sec Interface Tunnel0 If a router does not refresh its generated LSP after the LSP refresh interval , and the LSP remaining timer field has been reduced to 0 , all routers that have the LSP copy will copy the LSP from its own chain after the 60S grace period. Clear in the road state database. This 60S time is ZeroAgeLifetime , zero lifetime, and not configurable. Targeted neighbor relationship establishment 17 Record Route: NONE From the debug information of R1 , you can see: CSPF algorithm working mechanism When R1 recalculates the shortest path, it does not consider passing the R2 out area. Then there is only a default route to R3 on R1 . Of course, the route directly connected to R2 can still be seen on R1 . Remove: The top label is removed. The forwarding of the message depends on the remaining tags in the tag stack, or it is forwarded as an unlabeled message. *Aug 18 09:06:07.919: Incoming PROXY_PATH: Bytes Label Switched When the router receives the IIH , it will perform a series of verification actions, such as whether the length of the SystemID matches, max area address Ip cef Network 2.2.2.2 0.0.0.0 area 0 R1#show mpls forwarding-table System Id Type Interface IP Address State Holdtime Circuit Id The actual CLNP data is encapsulated in the CLNP header and then encapsulated in Layer 2. RFC 3847 Fa0/0 A label switch router (LSR) Cisco Router 's ISO addressing Flooding Protocol: OSPF Header Information:: Ip address 10.1.45.5 255.255.255.0 Protocols support Does it match, verify that the password is correct, the area ID or something. R3 is the ABR , connected area0 and area1 R2-PE1#show mpls ldp neighbor Interface fa0/0 Router-id 2.2.2.2 Interface tunnel0 Link ID *Aug 18 11:31:44.598: Interface eth 0/1 Router bgp 123 R2 . But why? The reason is that the label assigned by R2 to route 10.1.12.0 is PoP , because 12.0 is the directly connected network segment of R2 , and there is a second-end hop pop-up mechanism. Then this IP packet is R2 to stop the meal , because R2 does not have 6.6.6.6 and 5.5.5.5 routing. How to do? Redistribute connected level-1 !! Redistribute the local direct loopback 2.2.2.0/24 to level1 redistribute isis ip level-2 into level-1 route-map test 1.0.0.0/24 is subnetted, 1 subnets We see that due to the updated LSA in R2 , the metric is set to 65535 for the directly connected network segment 10.1.12.0/24 . Therefore, in the routing table of R3 ,ccna practise questions, we see 1.1.1.1/32 and 10.1. The 12.0/24 routing metrics are both bizarre. Look again at the Type 1 LSA produced by R2 : Mpls traffic-eng tunnels mpls ip The integrated IS-IS protocol implemented by CISCO was first released during the period 1991/1992 . Since then a series of improvements and extensions have been made. The large-scale development of the IS-IS protocol in major ISP networks began in 1995 , and another important reason was the US government 's interest in ISO CLNS . Although integrated IS-IS has dual routing capabilities, it is interesting to note that most of today's world's largest ISP networks use IS-IS protocols only for IP routing.