current ccna test

current ccna test

Tu0:403 You can see the main two contents contained in it: one is the directly connected network segment of R1 , here is 10.1.123.0 and 1.1.1.0 , and the other is the direct connection of R1 . *Aug 18 09:06:02.699: 10.1.12.2 (Strict IPv4 Prefix, 8 bytes, /32) R1#show ip route Net 49. 0001 .0000.0000.0001.00 Mpls traffic-eng tunnels ip rsvp bandwidth How labels are handled Interface FastEthernet0/0 Router ospf 1 ! 4 is IPv4 . If it is 6 or IPv6 , the LSR uses this value to determine whether the message is V4 or V6 , and then selects a complex equalization algorithm according to different IP versions. Tag request object It is also IPv6 because it receives an IP packet instead of a label packet. View MPLS forwarding table ( LFIB ) *Aug 18 09:06:07.919: 10.1.45.5 (Strict IPv4 Prefix, 8 bytes, /32) 102 Network 2.2.2.2 0.0.0.0 area 0 Priority 2 : 9375000 *Aug 18 09:06:07.919: SENDER_TSPEC type 2 length 36: The previous experiment used IBGP to establish IBGP adjacency on R1 and R4 to help you understand the MPLS environment. DIS Link State ID: 1.0.0.0 Opaque Type: 1 2 OSPF Router with ID (2.2.2.2) (Process ID 1) Router Link States (Area 0) ! Router# show mpls traffic-eng link-management bandwidth-allocation Router alarm tag ! Ip cef R1#show mpls traffic-eng tunnels There are two types of tunnel priorities: !! means from 13.1 to 34.3 and then to the local ( 34.4 ) 75000 R1#debug isis adj-packets Tunnel mpls traffic-eng autoroute metric 9 ! Ip vrf VPN-A rd 2345:6 Mpls ip *Aug 18 04:37:06.239: ADSPEC type 2 length 48: The configuration of R1 is as follows: The loopback0 address space of all devices is xxxx/32 , and x is the device number. The configuration of R1 is as follows: Ip address 3.3.3.3 255.255.255.255 Ip vrf VPN-A rd 2345:1 Reservable Bandwidth[5]: Interface ! Route metric is 168, traffic share count is 1 4 is IPv4 . If it is 6 or IPv6 , the LSR uses this value to determine whether the message is V4 or V6 ,current ccna test, and then selects a complex equalization algorithm according to different IP versions. Of course, we can also modify the TE metric , for example on the F1/0 port of R2 : Network 10.1.45.5 0.0.0.0 area 0 So in fact, the default here is still load balancing based on the source address pair. From the test results, 10.1.35.55 access 1.1.1.1 The IP forwarding instance does not consider the available bandwidth and load capacity of the link. It is possible that the metric assigned by the link is not the same as the actual metric . IGP metric: 1 Ip address 3.3.3.3 255.255.255.255 Can quickly converge when the network fails Show mpls traffic-eng topology ? The IGP will advertise the link with normal IGP metrics. At this time, the traffic that traverses this interface is the traffic for label switching. Basically, if the LDP session is not established, OSPF will not establish adjacencies on this link, and HELLO will not be sent at all (of course, there is a basic word here, that is, there are two cases) . Restart signaling for IS-IS 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. Tu0 3.3.3.3 Pop tag LSP , using LSP to carry all routing information Label Mapping message R2-PE1#show ip route In fact, it is for CLNS , and it has been expanded to become an integrated IS-IS , which can support IP routing. In IPv4 , the empty tag is 0 , and the ipv6 is 2 . *Aug 18 09:06:02.699: ADSPEC type 2 length 48: Sub Pool All routers run OSPF and the entire network is interconnected. The IP plan is as shown in the figure. Loopback0 of all devices is addressed by xxxx/32 , and x is the device number. Fa0/0 Router-id 6.6.6.6 4.4.4.4 routerID Tunnel mode mpls traffic-eng tunnel destination 4.4.4.4 Router ospf 1 Interface loopback0 0x0000000E We see that in the LFIB of R3 , going to the destination of 1.1.1.1 , there are two label paths for load balancing. Basic experiment 1 Bytes tag switched Device Internet segment 10.1.xy.0 / 24 , where xy is the device number, X small y large LSP Holdtime ! !! The unit is Bytes , multiplied by 8 is 100Mbps 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 BandwidthOverride: disabled LockDown: disabled Verbatim: disabled Router-id 3.3.3.3 In this way, in the route of L2 , the route matched by the route-map will be injected into the level1 area , then R1 can learn 5.5.5.0 . Type IA , i.e. isis the interarea route, i.e. isis inter-area routes. So far, the basic configuration has been completed. Now let 's create a TE Tunnel on R2 : Ip cef Mpls ldp router-id loopback0 mpls label range 100 199 interface fast0/0 75M 10.1.45.0/24 Router(config-if)# ip rsvp bandwidth ? Type escape sequence to abort. Tracing the route to 5.5.5.5 908 ISO10589 ! 1.1.1.0 is directly connected, Loopback0 2.0.0.0/24 is subnetted, 1 subnets The interface of each router activates RSVP and MPLS TE tunnel support. Configuration example 1 : Describes all LSP information in the LSP database . Tunnel mpls traffic-eng priority 6 6 Ip router isis interface Serial0/0 Assuming the bandwidth of the local physical outgoing interface is 100M , the default reservable bandwidth of rsvp is 75% . Here is 75M. Link connected to: another Router (point-to-point) (Link ID) Neighboring Router ID: 5.5.5.5 LDP IP before 4B is when there is a loopback when interfaces, loopback maximum interface IP , if there is no lp interface, is the largest active physical interface IP , use the following command to change: Route summarization must be performed on the originating router of the L2 route, otherwise invalid Related RFCs *Aug 18 09:06:07.919: Et0/1 !! Let R1 become DIS Complete MPLS TE configuration on R1 . Forwarding tagged messages SNPA ( Subnetwork point of attachment ) R2(config)#key chain test R2 (config-keychain)#key 1 Router ospf 1 ! Net 49.0001.0000.0000.0003.00 Area verification is actually the verification of Level1 area . After the area authentication is added to an IS-IS router, it will check the IS-IS packets it receives . If there is no authentication information or error in the packet, it will be ignored. The IS-IS packet generated by the device itself carries the authentication information. If the receiver does not have the configuration area authentication, the device can still learn normally after receiving the packet carrying the authentication information. The authentication information of the area authentication is only included in the LSPs packet. Other packets are not included.