online test ccna exam questions

online test ccna exam questions

1230 RSVP extension to LSP tunnel The LSP overload-bit generated by this router is set. This will cause the router to not be used by other routers as the next hop to any destination, except for its locally connected network segment. This is generally used when the router is a leaf node, that is, the end of the network, directly connected to the user. 55.55.55.55 and 5.5.5.5 will no longer take the tunnel . Traffic Engineering RouterID TLV (Type 134 ) is mainly used for TE ! Egress LSRs — Egress LSRs receive labeled packets, remove the label(s), and send them on a data link. Ingress and egress LSRs are edge LSRs. Next hop 10.1.12.2, FastEthernet0/0 valid cached adjacency *Aug 18 09:06:07.919: Interface Untag will remove all tag headers and turn them into a pure IP message. The Global Pool Sub Pool !! interface is the bandwidth pool for each priority tunnel 200 102 Traffic engineering ( Traffic Engineering ) we can be loosely understood as "the ability to control traffic across the network," we can by TE allows the deployment of traffic in an optimal way transmission from one node to another node in the network. If the payload of the MPLS is an IPv6 packet, the load balancing is performed according to the source and destination addresses in the IPv6 header. TCP connection: 2.2.2.2.61914 - 1.1.1.1.646 End host. For example , the ISO CLNP workstation searched by the ES-IS protocol . AutoRoute: enabled LockDown: disabled Loadshare: 2000 bw-based auto-bw: disabled Network 1.1.1.1 0.0.0.0 area 0 *Aug 18 09:06:07.919: Tun Sender: 1.1.1.1 LSP ID: 247 10.1.23.2 AutoRoute: disabled LockDown: disabled Loadshare: 0 bw-based auto-bw: disabled Interface Loopback0 Bw-based In this way , when the IP packet is tagged on the border device, the TTL value in the original IP header is not copied , but a 255 value is used instead. 0 kbits/sec *Aug 18 09:06:07.919: TIME_VALUES type 1 length 8 : Mpls traffic-eng router-id loopback 0 mpls traffic-eng level-1 Is-type command such as is-type level-1 Experimental configuration If the headend wants to remove the tunnel , send PATHtear along the tunnel path , and the received node responds to RESVtear , so the tunnel between the two points Network 10.1.12.1 0.0.0.0 area 0 Ciphertext LSPs authentication Small to check if the MTU of both parties matches *Aug 18 09:06:07.919: Fspec: ave rate=20000 kbits, burst=1000 bytes, peak rate=20000 kbits History: R2 (config-router)#authentication key-chain test level-2 R2 (config-router)#authentication mode md5 level-2 We see that R5-PE2 assigns a 505 label to VPN customer route 6.6.6.6 . Nolabel/506 Ip router isis Impact of route summarization on MPLS 1112 [1]: 75000 kbits/sec The default flooding period of OSPF is 30 minutes. You can modify it by timers pacing lsa-group. OutLabel : FastEthernet0/0, 200 RSVP Signalling Info: 1.0.0.1 Interface The L1 and L2 IIH PDUs on the LAN are sent to different multicast MAC addresses: L1 is 0180-C200-0014 , L2 is Path option 10, type dynamic (Basis for Setup, path weight 20) 10.1.24.0 [115/20] via 10.1.123.2, FastEthernet0/0 Prefix Domain-wide Prefix Distribution with Two-Level IS-IS Remote binding: tsr: 2.2.2.2:0, tag: 202 tib entry: 10.1.23.0/24, rev 12 Test . 5 : SET 'bit-overload-the suppress interlevel Router isis *Aug 18 09:06:02.699: 10.1.45.4 (Strict IPv4 Prefix, 8 bytes,online test ccna exam questions, /32) Path setting option path-option Tunnel mpls traffic-eng bandwidth 2000 Ip route 5.5.5.5 255.255.255.255 Tunnel0 Mpls traffic-eng tunnels mpls label range 400 499 Setting command 2.2.2.0/24 10.1.23.3 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 , 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 : Tunnel destination 4.4.4.4 tunnel mode mpls traffic-eng Reservable Bandwidth[0]: Mpls traffic-eng tunnels mpls ip My Address: 10.1.12.1 Distribution mode : Label Allocation Ip unnumbered Loopback0 R1#show mpls ldp neighbor Ip address 2.2.2.2 255.255.255.255 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 Explicit Path a series of IP configuration, an explicit path in the IP can be an interface IP , it may be MPLS TE Router ID . Version:1 flags:0000 cksum:7931 ttl:255 reserved:0 length:132 Switched Let the ES know where it is, the area prefix Ip address 10.1.45.5 255.255.255.0 Configuration example 0 kbits/sec Interface fast1/0 N-SEL 1- byte selector, English: NSAP-Selector is similar to the port in TCP/IP , identifies the process (or service) on the device, and is 00 in NET . Priority 2 : 9375000 *Aug 18 09:06:02.699: LABEL_REQUEST type 1 length 8 : LDP 16 Router ospf 100 5.5.5.5/32 129 Reservable Global Pool BW: 75000 kbits/sec SRM ( Send Routing Message ): Send routing information message [7]: 55000 kbits/sec Et0/1 1010 OSPF and ISIS also have mechanisms for periodic flooding The actual CLNP data is encapsulated in the CLNP header and then encapsulated in Layer 2. 0/0/0 This can be area at any level within the router adjacency relationship; may be other area adjacent L2 or L1 / L2 router forming L2 Priority 5 : 9375000 Outgoing interface My Address: 10.1.12.1 Selecting designated routers in the broadcast network to control the spread and reduce the system resource requirements of many-to-many neighbors in such media i L1 2.2.2.0 [115/10] via 10.1.123.2, FastEthernet0/0 5.0.0.0/24 is subnetted, 1 subnets Packets package O 10.1.23.0 [110/2] via 10.1.12.2, 00:00:37, FastEthernet0/0 Interface FastEthernet0/0 The distribution of the label is like this: LSPID LSP Seq Num LSP Checksum LSP Holdtime ATT/P/OL The configuration of R2 is as follows: The password is inserted in Level2 LSP , CSNP , and PSNP . The command is as follows (in the routing process): Ip address 10.1.23.3 255.255.255.0 Section LAN ID as 1921.6811.1001. 03 . " the routers connected to the multiaccess network (Ethernet) all have the same circuit ID . The circuit ID is a one-octet number that the router uses to uniquely identify the Router-id 4.4.4.4 *Aug 18 04:37:06.243: STYLE type 1 length 8 : We open interface authentication between R1 and R2 : Router(config-if)#tunnel mpls traffic-eng path-option x {dynamic | explicit {name path-name | *Aug 18 09:06:07.919: EXPLICIT_ROUTE type 1 length 68: Router isis Remote binding: tsr: 2.2.2.2:0, tag: 202 tib entry: 10.1.23.0/24, rev 12 Interface eth0/0 Interface eth 0/1 Downstream active mode : Downstream Unsolicited Bytes Label Switched 10.1.23.0/24 Configure this feature on the A device (usually on the edge device) no mpls ip propagate-ttl Local LDP Identifier: 10.1.12.1 Reservable Bandwidth[6]: Net 49.0001.0000.0000.0002.00 Active Path Option Parameters: Net 49.0001.0000.0000.0002.00 Mpls label rangempls label range 100 199 interface fa0/0 Mpls traffic-eng tunnels ip rsvp bandwidth Ip address 5.5.5.5 255.255.255.255 Nexthop 10.1.12.2 FastEthernet0/0 label 204 AutoRoute defect 7 3.0.0.0/32 is subnetted, 1 subnets i L1 10.1.34.0 [115/20] via 10.1.123.3, FastEthernet0/0 C 10.1.123.0 is directly connected, FastEthernet0/0 i* L1 0.0.0.0/0 [115/10] via 10.1.123.3, FastEthernet0/0 304 RESV Next , take a look at the Tunnel on R1 : Let's look at an example: The configuration of R4 is as follows: Tunnel mpls traffic-eng bandwidth 2000 *Aug 18 09:06:02.699: TIME_VALUES type 1 length 8 : 0/0/0 Network 10.1.34.3 0.0.0.0 area 0 mpls traffic-eng router-id loopback0 mpls traffic-eng area 0 Configure on R2 as follows: *Mar 1 00:00:32.763: ISIS-Upd: Important fields changed ! Tunnel mpls traffic-eng path-option 10 dynamic 4.4.4.4/32 Router(config-if)# mpls traffic-eng path-option x {dynamic | explicit name y } [ lockdown ] MPLS TE router ID: 1.1.1.1 3.3.3.3 Interface loopback1 4.4.4.4/32, version 12, epoch 0, cached adjacency 10.1.12.2 1.1.1.1/32 Control metric through dynamic routing protocol to affect routing routing Link State ID: 1.0.0.0 Opaque Type: 1 Show and debug ! The configuration of R4 is as follows: Configured Areas: 1 Type 9 flooding range only on this link On the L1/L2 router , the routes of the subordinate Level1 area are summarized, so that the summary route is learned in the backbone or level2 area , and the configuration is as above. L1/L2 router re-releases external routes into IS-IS ( to level1 ) Mpls traffic-eng tunnels mpls label range 300 399 Activate LDP on all devices. To facilitate observation, specify the label range for each device . For example , the label range of R1 is 100. 129 Fast tag rewrite with Fa0/0, 10.1.12.2, tags commit: {203} via 10.1.12.2, FastEthernet0/0, 0 dependencies Remarks Mpls traffic-eng tunnels ip rsvp bandwidth LSP serial number OSPF of LSA aging time for the 3600s , refresh interval Interface eth0/0 10.1.12.2 Small to check if the MTU of both parties matches ! Name: R2-PE1_t0 Status: If the payload of the MPLS is not an IPv4 packet, load balancing will be performed by looking at the value of the label at the bottom of the bottom. Tunnel mpls traffic-eng autoroute announce tunnel mpls traffic-eng priority 7 7 Bw[1]: Mpls traffic-eng tunnels mpls label range 500 599 Link state information IGP itself supports All interconnected IPs are shown Interface Tunnel mpls traffic-eng bandwidth 2000 Types of The router generates a label locally for each IGP prefix and distributes it to the LDP neighbor. It also receives labels for the specific prefix from other LDP neighbors. The router stores the local label and the remote label (which the LDP neighbor sent to me) in the LIB . i L2 2.2.2.0 [115/20] via 10.1.24.2, Serial0/0 Interface loopback1 Type 7 length 16: 75000 My Address: 10.1.12.1 LDP adjacency establishment process 75000 Device Internet segment 10.1.xy.0 / 24 , where xy is the device number, X small y large Once the router receives the IIH , it checks the adjacency of the sender of the hello packet. If the adjacency has been established, the adjacency is reset. L1/L2 router re-releases external routes into IS-IS ( to level1 ) Network 10.1.45.4 0.0.0.0 area 0 mpls traffic-eng router-id loopback0 mpls traffic-eng area 0 Frame-relay map ip 10.1.123.1 301 broadcast The static route forwarding mode of the MPLS TE tunnel supports route recursion. Interface tunnel0 ! !! Backup tunnel !! ldp 's routerid uses loopback port IP 2.2.2.0 [115/20] via 10.1.123.2, FastEthernet0/0 3.0.0.0/24 is subnetted, 1 subnets Ip address 10.1.12.1 255.255.255.0 Clns host RouterA 49.0001.1111.2222.3333.00 clns host RouterB 49.0001.4444.5555.6666.00 0x1B7C Tunnel mpls traffic-eng path-option 10 dynamic Local Interface Loopback0 LSP TLV field of Level 1 route *Aug 18 09:06:07.919: SENDER_TEMPLATE type 7 length 12: Mpls traffic-eng tunnels ip rsvp bandwidth R4#sh mpls tr tun Path: valid Calculated. In the figure above, the red path is calculated by CSPF . If not manually set metric , the re-release came default metric is 0 , that is, R2 routed the metric is R2 is S0 / 0 port Level-1 metric There have been a lot of talks about ATT-bit before, so I won't be embarrassed here. I have tested on CISCO IOS Version 12.4(10) -- C3640-JK9O3S-M . On R1, which is L1 router , with default-information originate , I can't generate default route. *Aug 18 09:06:07.919: General Parameters break bit=0 service length=8 Intermediate system adjacent router IS-IS extensions for Traffic Engineering Tunnel mode mpls traffic-eng Reservable *Aug 18 09:06:07.919: Flags: (0x7) Local Prot desired, Label Recording, SE Style 0 kbits/sec Do not elect DIS , use CSNP to trigger database synchronization after the link is established . By default, Cisco IOS starts both L1 and L2 operations on the IS-IS router . If you want to specify the router as only the area router or trunk router , use the router configuration mode: ! AutoRoute: enabled auto-bw: disabled PATH Mpls ldp router-id loopback0 Ip router isis 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 . LSPDB 200 Et0/1: 403 Network 10.1.34.3 0.0.0.0 area 0 This relative command can be configured with a value of -10 to 10 . This means adding or subtracting this specific value based on the IGP metric. For example figure above, without considering the tunnel in the case of, R2 on about 5.5.5.5 and 55.55.55.55 Routing Metric = 31 is . This value has been said above. Now we configure this with relative -1 after the command keywords, relying on autoroute calculated, point tunnel0 mouth of OSPF routing, Metric becomes 31-1 = 30 .