cisco ccnp test questions

cisco ccnp test questions

Link state messages are used to propagate link and node information in the area (describe the topology of the local network) PSN can reduce the number of flooding spreads and database synchronization. Basic command Then R1 will use the IGP of Metric , and ignore R2 on the configuration of the physical interface adminnitration-weight , so after the entry into force of the above command, go R1 view on the tunnel 's path weight , it turned into a 3 . When there is a problem with the path of R1-R2-R5 , for example , the link between R2-R5 is DOWN , then the TE tunnel will switch to the path-option of the next priority , that is, the dynamic setting mode. Therefore, it will switch to R1-R3-R4-R5 . ! 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 Collect IP routing information obtained through other routing protocols Interface FastEthernet0/0 On CISCO IOS 12.4 , Acl tried it with standard and extended access control lists. If it is unsuccessful, even acl permit any will not work. Matching the route with the prefix list is successful. Then you need the top-level tag, which looks at the next hop. The next hop is 5.5.5.5 , so be sure to find the 5.5.5.5 tag. As we have seen from the routing table, at this point R2 goes to 5.5.5.5 and actually enters the TE tunnel , then: The routing protocol in the IP network forwards the data packet according to the minimum metric principle. There are actually some hidden dangers here. For example, using traceroute may expose the internal structure of the network ( after TTL=0 , the router will return an error message, which may expose network information). LSP 10.1.23.0 [110/65536] via 10.1.12.2, 00:00:48, FastEthernet0/0 Activate record route , which can make the PATH and RESV messages carry the record route object, record the IP passing along the tunnel , and can play a certain anti-ring effect. Of course, there are other important functions, which will be explained later. L1 R3.02 Interface Loopback0 InLabel : - According to the protection object can be divided into: Mpls traffic-eng tunnels ip rsvp bandwidth Three-way handshake mechanism: Router-id 3.3.3.3 10.1.45.4 10.1.45.5 The L1 and L2 IIH PDUs on the LAN are sent to different multicast MAC addresses: L1 is 0180-C200-0014 and L2 is 0180-C200-0015 Dynamic hostname mapping Mpls traffic-eng tunnels mpls label range 400 499 Router(config-if)#tunnel mpls traffic-eng bandwidth BW Options: (No TOS-capability, DC) LS Type: Opaque Area Link LS age: 705 !! Neighbor's SNPA , the interface MAC of the other party in the LAN 5 [3]: 75000 kbits/sec 0 kbits/sec Reservable Bandwidth[2]: *Aug 18 11:26:02.546: 3.3.3.3 Nolabel/506 Router ospf 100 Prefix Detailed LSP header Interface tunnel0 Address-family vpnv4 neighbor 5.5.5.5 activate Device Internet segment 10.1.xy.0 / 24 ,cisco ccnp test questions, where xy is the device number, X small y large O *Aug 18 11:26:02.546: Headend frr information: Protected tunnel Test the transmission process of the data stream, observe the phenomenon Active R3#show ip ospf database router 2.2.2.2 Keep priority tunnel interface can be configured directly IGP Metric , for example, if the running OSPF , directly in the tunnel configuration mouth ip ospf cost can Prefix *Aug 18 09:06:02.699: LABEL_REQUEST type 1 length 8 : Fa0/0 Three-way handshake mechanism: *Mar 1 00:00:32.639: %BGP-5-ADJCHANGE: neighbor 10.1.24.4 Up *Aug 18 09:06:07.919: IS Hops:0 Interface tunnel0 Ip ospf cost 1 *Aug 18 11:31:44.598: Packets package R5.00-00 Interface Loopback0 R5 configuration is as follows The target network segment involved in MPLS is the same as traditional IP forwarding. Router isis * 0x0000000C R2.00-00 Which table is specifically checked depends mainly on the Layer 2 encapsulation of the received data. For example, if the Layer 2 encapsulation is Ethernet (data frame), look at the value of the Type / Length field of the frame header : Record Route: NONE 202 *Aug 18 11:26:02.546: Router(cfg-ip-expl-path)#next-address 10.1.12.2 !! Note the input order Switched Virtual circuit ID of X.25 or ATM Admin: up Oper: up Path: valid Signalling: connected path option 10, type explicit R2R4R5 (Basis for Setup, path weight 30) 10.1.12.2 ! Ip router isis *Aug 18 09:06:07.919: min unit=0 bytes, max pkt size=2147483647 bytes OSPF of LSA aging time for the 3600s , refresh interval Ip address 10.1.123.2 255.255.255.0 Type Block Tunnel mpls traffic-eng path-option 10 dynamic This time we did the test, environmental test just a different, TE the Tunnel tail end now is to R4 of 4.4.4.4 . Packets package PATH/RESV !! ldp 's routerid uses loopback port IP ! Ip address 1.1.1.1 255.255.255.0 ip router isis Tspec: ave rate=0 kbits, burst=1000 bytes, peak rate=0 kbits RSVP Resv Info: Outgoing Look at the routing table for R1 : 0 interfaces: Such as 39.0f01.0002. 0000.0c00.1111 . 00 Protocols support *Aug 18 09:06:02.699: SENDER_TSPEC type 2 length 36: *Aug 18 04:37:06.243: Tun Dest: 5.5.5.5 Tun ID: 0 Ext Tun ID: 1.1.1.1 Next-address 10.1.24.4 366 The CEF entry indicates that to go to 4.4.4.4 , the IP packet needs to be stamped with a value of 203 , and then the packet is dropped to the next hop 10.1.12.2 and thrown out from the Fa0/0 port. FIB SENDER_TEMPLATE Router(config)# mpls ldp backoff initial-backoff maximum-backoff Ensure reliable diffusion of LSPs on point-to-point links Next Hop 10.1.12.2 R2.00-00 Redistribute isis ip level-2 into level-1 route-map test Net 49.0001.0000.0000.0003.00 *Aug 18 11:26:02.546: Area Address: 49.0001 Interface loopback0 Age The Internet segment of the device is shown in the figure, for example, 10.1.23.0/24 , which is the R2-R3 interconnection address segment, then the interface IP of R2 is 10.1.23.2 . *Aug 18 09:06:07.919: SESSION_ATTRIBUTE type 7 length 16: Ip address 10.1.45.5 255.255.255.0 Using domain authentication, IIH packet, CSNP , PSNP is not carrying authentication information, LSP is used to carry the authentication TLV . The previously mentioned IS-IS , which only supports the CLNS network environment, does not support routing information exchange in the IP network environment. Later, the IETF in RFC 1195 are of IS-IS with modifications and extensions, called integrated IS-IS ( the Integrated IS-IS ) or dual- IS-IS ( Dual IS-IS ). Integrated IS-IS was developed to enable it to be applied to both TCP/IP networks and OSI networks, enabling it to provide dynamic routing information exchange for IP networks.