ccna voice training

ccna voice training

Tunnel: Net 49.0001.0000.0000.0001.00 The ACL is used to match who sends an explicit null tag. ( NLPID 0x81 ) and IP ( 0xCC ) [4]: Fa0/0 A label switch router (LSR) Ip address 3.3.3.3 255.255.255.255 Expense metric Extending the Number of IS-IS LSP Fragments Beyond the 256 Limit Therefore, in an NBMA network, such as a frame relay environment, it is strongly recommended to use the P2P sub-interface to run ISIS . 5.5.5.5 Ip cef MPLS design and implementation Label space ! ! The change has occurred. In the head router, this will record the labels along the way. Now, shut down the e0/1 port of R2 . Tag rewrite with Fa0/0, 10.1.12.2, tags imposed: {203} LSP Tunnel R1_t0 is signalled, connection is up Ip address 10.1.12.1 255.255.255.0 Net 49.0001.0000.0000.0002.00 Or Tunnel Id 687 i L1 Fspec: ave rate=2000 kbits, burst=1000 bytes, peak rate=2000 kbits History: Configure on R2 as follows: Src IP addr: 10.1.12.2; Transport IP addr: 2.2.2.2 Hold time: 15 sec; Proposed local/peer: 15/15 sec Reachable via 2.2.2.0/24 The establishment of an OSPF adjacency involves a more complex process. *Aug 18 09:06:07.919: Mpls traffic-eng tunnels mpls label range 400 499 Interface Loopback0 R1.00-00 Take a look at the routing table for R1 : O 5.5.5.5 [110/31] via 4.4.4.4, 00:23:47, Tunnel0 ! TE with Layer3 Tu0:403 Total Allocated BW (kbps) Phenomenon analysis The interface of each router activates RSVP and MPLS TE tunnel support. Attribute tag and affinity attribute After completing this configuration, take a look at the phenomenon: 558 *Aug 18 09:06:07.919: Periodic update. IS-IS only supports reliable diffusion on point-to-point links, and the spread on the broadcast link is unreliable. However, periodic broadcasts through DIS Ip vrf VPN-A rd 2345:6 *Mar 1 00:09:39.243: ISIS-Adj: Rec L1 IIH from cc01.0a44.0000 (FastEthernet0/0), cir type L1, cir id 0000.0000.0002.02, length 1497 Bytes tag Binding Remote: TSR: 2.2.2.2:0, Tag: 202 !! neighbor R2 prefix 3.3.3.3/32 label allocated After everyone's LFIB is built, we can see that when A receives an IP packet and wants to access X , then A checks its own CEF table. OSI network layer addressing is achieved by using two types of hierarchical addresses: NSAP and NET . *Aug 18 04:37:06.243: Tun Dest: 5.5.5.5 Tun ID: 0 Ext Tun ID: 1.1.1.1 Interface fast0/0 The configuration of R1 is as follows: From which interface a tag packet is received, as long as it has this tag, it will be exchanged. With the PHP mechanism: Router ospf 1 MPLS supports multiple Layer 3 protocols RFC 2370 describes an extension of OSPF that defines three new LSAs . These LSAs are called sluggish LSAs ( opaque LSAs ) and their differences are limited to the extent of propagation. These LSAs can accurately provide the information required by MPLS TE to OSPF : Mpls ldp discovery targeted-hello accept from accept-ldp R2#show ip ospf database router self-originate Produce PoP and untag case After calculating the path, you need to reserve resources and distribute labels through RSVP . The RSVP path message is transmitted one hop along the calculated PATH and requests resources and labels. Then R7 will give the response and bring the label back. This tag distribution and resource reservation actions are also performed one by one. In this way, an LSP is finally established. 10.1.12.2 RFC1195 Traffic using traffic engineering uses source-based routing instead of routing based on destination IP address Outgoing interface *Aug 18 11:31:44.598: Mpls traffic-eng tunnels ip rsvp bandwidth *Aug 18 04:37:06.239: SENDER_TEMPLATE type 7 length 12: Ip address 10.1.123.2 255.255.255.0 OAM is basically used for error detection, location, and monitoring implementation. This tag distinguishes between ordinary messages and OAM messages. CISCO IOS does not use tag 14 , which performs MPLS OAM but is not implemented by tag 14 . If the sysID length is inconsistent,ccna voice training, the IIH is ignored . R1#sh mpls traffic-eng topology 1.1.1.1 Pop tag 10.1.23.0/24 ( ... omit... ) How does a router know whether a message is a normal message or a label packet? MPLS packets are inserted between the Layer 2 header and the Layer 3 packet. R3.00-00 High-priority tunnels can preempt resources of low-priority tunnels. Support 0-7 total 8 tunnel priority levels MPLS relies on IP routing and CEF switching Bw[7]: 10.1.12.2 [MPLS: Label 200 Exp 0] 4 msec 0 msec 0 msec !! Bandwidth requirement is 20M Configure MPLS TE tunnel on R1 . 3.0.0.0/24 is subnetted, 1 subnets 403 Let's look at an example: 203 Ip explicit R1toR5 0 kbits/sec 0 kbits/sec ISO10589 7 The virtual link implements a level 1 repair path through the backbone . The zone designated router sets the partition repair of its level1 LSP . In this way, B receives a label packet with a label value of 22 sent by A , and pops the label to obtain an IP packet, and then forwards it to C , and then C only needs to search and forward the FIB table of the IP packet . 10.1.23.3 Interface fast0/0 0x18B7 *Aug 18 09:06:07.919: version:1 flags:0000 cksum:BFD0 ttl:255 reserved:0 length:132 PLR ( Point of local repair ): Local repair point, this is the head end of the backup tunnel If R3-R5 , LDP is run , let R5 send the label packet, R3 receives the label packet, looks at the byte after the label stack, and finds the value is 4 , so it is determined to be an IPv4 packet, so the IPv4 header is The source and destination addresses are taken out for hashing to perform load balancing. Tag or VC 0x4769 DIS send HELLO interval ordinary packet router of 1/3 (default 3.3s ), which ensures DIS when a failure occurs can be more quickly found. Reservable Bandwidth[1]: In the standard SPF algorithm, there can be multiple equivalent paths to the same destination. We call it ECMP ( Equal-cost Multipath ). 200 System R1#traceroute 55.55.55.55 Network 10.1.56.6 0.0.0.0 area 0 ID: path option 10 [36] It became untagged , before it was POP , why is it untagged now? Analysis, we modified the R2 's loopback mouth, into 2.2.2.2/24 , then for R2 own, this is the direct route 2.2.2.0/24 , right? R2 may for this 2.2.2.0/24 assign a label, since it is directly connected, so R2 to this prefix divided empty tag 3 . Then send the label mapping message to other LDP neighbors including R1 and R3 : Interface fas1/0 supporting agreement Interface Tunnel0 Router(config-if)#tunnel destination ip-addr Metric: 0 *Aug 18 11:31:44.598: The forwarding of IP packets in each hop router is based only on the destination address. Tunnel mpls traffic-eng autoroute metric command. If we add the following configuration to the TE tunnel interface of R2 : *Aug 18 09:06:02.699: Session Name: R1_t0 0/0/0 *Aug 18 09:06:07.919: Minimum Path Bandwidth (bytes/sec): 1250000 In RFC5250 In been described herein: A neighbor Capable IS-opaque and only IF The IF IT sets-O 'bit in the Options The ITS Database Field of the Description packets; The-O' bit the NOT SHOULD BE SET When ignored and the MUST BE C 1.1.1.0 is directly connected, Loopback0 10.0.0.0/24 is subnetted, 2 subnets 2.2.2.2 MPLS does not assign labels to BGP routes, but assigns labels to the next hop of BGP routes. Metric: 10 Now activated R1 is fast-reroute features modified R1 of Tunnel port configured as follows: IS-IS requires the same length of the SystemID in the entire domain . If you receive the IIH , the " System ID Length " field is local to 10.1.34.0/24 Priority 5 : 9375000 Reference book Modify the configuration of R2 : 1.1.1.1:0 *Aug 18 04:37:06.239: HOP type 1 length 12: The tail router of the TE tunnel receives this PATH message. Mpls traffic-eng router-id loopback0 mpls traffic-eng area 0 lab environment Exit 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 4 10.1.12.1 1060 msec 984 msec 1080 msec InLabel : - Next, R1 calculates another alternative path to R7 through the existing information : R1-R2-R4-R5-R7 , this path passes CSPF Route Distinguisher: 2345:6 IS-IS Level-1 LSP R1.00-00 RSVP extension for LSP tunnel : Interface Loopback0 10.1.34.0/24 [110/20] via 10.1.23.3, 00:00:01, Ethernet0/1 NHop ( Next Hop Router ): Next hop router, PLR next hop router ATT/P/OL 10.1.12.2 PseudoNode ( PSN ) Pop tag Remaing lifetime LSP lifetime before LSP ID LSP identity Sequence num LSP serial number Ip address 4.4.4.4 255.255.255.255 1103 ! Default metric is supported by all IS-IS routers and is often interpreted as a measure that is inversely proportional to bandwidth. Tracing the route to 55.55.55.55 Free mode : Liberal Retention Router-id 4.4.4.4 The loopback interface of R2 and R3 comes from this area, so there is no problem with the route of L1 , but is the direct link of R2-R4 and R3-R4 coming in? That's because these are the direct connections of R2 and R3 . You can configure the interface to be on S1 and 0 of R2 and S1/0 of R3 . A device that supports and activates MPLS . It is capable of understanding MPLS labels and of receiving and transmitting a labeled packet on a data link. Three kinds of LSRs exist in an MPLS network: The IS-IS packets have the same common 8B above , and the additional header fields are different, and then the TLV field. At the time of packet capture , the ternary in the TLV : type, length, variable length content, type and length in the packet, the packet capture software may not be presented, but the type and length can be found from the binary code of the packet capture result. content. Link connected to: a Stub Network Ip cef i* L1 Circuit circuit Pop tag Network 10.1.24.4 0.0.0.0 area 0 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.