ccna routing and switching pdf free download

ccna routing and switching pdf free download

Mpls traffic-eng tunnels mpls label range 500 599 *Aug 18 04:37:06.243: Incoming ResvTear: Note that since R1 activates MPLS LDP-IGP synchronization, before the LDP adjacency relationship between R1 and R4 is established, the interface connecting R4 on R1 will not send OSPF HELLO packets, that is, R1-R4 . OSPF adjacencies can never be established. Of course, we don't want to watch the R1-R4 screw up, it's not good for anyone, isn't it? So configure one on R1 : There are three types of PDUs : the IS-the IS of ES-IS and CLNP Ip address 10.1.23.2 255.255.255.0 OutLabel : FastEthernet0/0, 200 RSVP Signalling Info: ID: path option 10 [248] *Aug 18 09:06:07.919: ADSPEC type 2 length 48: Network 10.1.34.4 0.0.0.0 area 0 In the forwarding process, a set of data with the same processing mode can be identified by means of address, tunnel, COS, etc., usually in one set. OutLabel : Ethernet0/0, 200 RSVP Signalling Info: Ip address 2.2.2.2 255.255.255.255 105 Ip address 10.1.12.1 255.255.255.0 Interface fa0/0 mpls ip Network 10.1.12.1 0.0.0.0 area 0 R3.02-00 Configure targeted-hello accept acl Explicit Route: 10.1.23.3 10.1.34.3 10.1.34.4 4.4.4.4 Interface eth 0/0 basic configuration Controlled Load Service break bit=0 service length=0 Mpls traffic-eng router-id loopback0 mpls traffic-eng area 0 0/0/0 Net 49.0001.0000.0000.0002.00 ! Tunnel mpls traffic-eng autoroute metric relative parsing if the configuration of R2 changes as follows: PATHErr is actually sent to the headend router. The main reason for sending the error message is that the link used by the TE LSP fails, or the party LSR receives the PATH message with the forged message. Each metric type is 8bits and has the following form: Interface Loopback0 Assign and distribute labels We found that the attached-bit before the LSP generated by R2 is gone, but the Overload-bit is set . Now let's go look at the routing table. Protection Link (link protection) Explicit Route: 10.1.23.3 10.1.34.3 10.1.34.4 4.4.4.4 Frame-relay map ip 10.1.123.2 102 broadcast Router-id 5.5.5.5 Remote binding: tsr: 2.2.2.2:0, tag: 200 The TLV section contains fields for system characteristics, as shown below: = 250000 bytes/sec R3#sh mpls forwarding-table RFC 3847 If an LSP is continuously destroyed during transmission, it will be continuously cleared by other routers, and the source router will continue to resend. This creates an LSP destruction storm. CISCO IOS allows routers to ignore corrupted LSPs and write errors only to log files locally. Open with the lsp-ignore-errors command. Two routers to establish LDP neighbors, to ensure that the parties to the other side of the LDP ID triple up * 0x0000002B Priority 2 : 9375000 lab environment Level1 area default route 3 Ip address 1.1.1.1 255.255.255.255 2 10.1.34.3 [MPLS: Label 303 Exp 0] 856 msec 1012 msec 1072 msec The label header has a total of 32 bits and contains the following fields: PDU header Length : The number of bytes in the data header field (the total number of bytes includes the number of bytes of the additional header field) If you change the Path-selection metric to igp , the shortest path to the tunnel will ignore the configuration in the physical interface. Label Mapping message LDP adjacency establishment process *Aug 18 11:31:44.598: The LSP carries the TLV for authentication. Mpls label rangempls label range 400 499 interface fa0/0 Basic Experiment 2 ( IS-IS ) Each tag mapping message contains two elements : FEC TLV and Label TLV Imagine if AB link between carrying a lot of the Tunnel , then when this root link DOWN out of time, will likely trigger a large amount in a short time PATHtear and ResvTear , so how to optimize it? Then shut down the e0/1 port of R2 : Ip address 10.1.12.2 255.255.255.0 My Address: 10.1.12.1 So now, we will change the loopback port address of R2 to 2.2.2.2/24 and change it to /24 to see what happens. Oper: up *Aug 18 09:06:07.919: Hop Addr: 127.0.0.1 LIH: 0x00000000 In the LAN , SNPA refers to the MAC address. *Aug 18 09:06:02.699: Session Name: R1_t0 0 kbits/sec When a router receives a tagged message, it searches in the LFIB table. The related matching entries in the LFIB table have outbound actions or labels for the inbound tag, and next hop information. . ! R1#show mpls forwarding-table 4.4.4.0 detail 10.1.13.3 *Aug 18 09:06:07.919: Tun Dest: 5.5.5.5 Tun ID: 0 Ext Tun ID: 1.1.1.1 Record Route: NONE The mere motivation to set up overload due to insufficient device resources is now running out. After all, the performance of the device is getting better and better. MPLS TE tunnels, also known as Traffic trucks , are used to overcome hop-by-hop IP routing defects. *Aug 18 09:06:07.919: version=0 length in words=10 *Aug 18 09:06:07.919: IS Hops:1 10.1.34.4 Interface eth0/0 Is-type level-1 metric-style wide i L1 2.2.2.0 [115/10] via 10.1.123.2, FastEthernet0/0 5.0.0.0/24 is subnetted, 1 subnets 2.2.2.2 0 [5] 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. BGP routing problem, well, now we use the loopback interface on R1 and R4 to establish IBGP adjacency, the problem is solved. At this time R4 , the go 5.5.5.5 next hop of the R1 of Loopback port addresses, R4 at destined to 5.5.5.5 of the IP when the pressure package label, use is 1.1.1.1/32 routing tag, The same is true for R3 and R2 , then the label package can be opened through 1.1.1.1/32 . Tunnel mpls traffic-eng bandwidth 2000 In a network running MPLS , you can set these two paths to different LSPs and use different labels. On R1 , R6 and IS-IS packets are encapsulated in data link layer frames. *Aug 18 09:06:07.919: 5.5.5.5 (Strict IPv4 Prefix, 8 bytes, /32) *Aug 18 09:06:02.699: 10.1.12.2 (Strict IPv4 Prefix, 8 bytes, /32) Route-target export 2345:5 State Changed: 00:20:27 Explicit Route: 10.1.12.2 10.1.23.2 10.1.23.3 10.1.34.3 The first is the case of no forwarding adjacency: Network 10.1.34.3 0.0.0.0 area 0 ( NLPID 0x81 ) and IP ( 0xCC ) PSNP [0]: Keep priority Now let's add R4 . Note that R4 is only equipped with OSPF at this time . First, don't configure mpls ip on the interface connected to R1 (or use Mpls traffic-eng tunnels ip rsvp bandwidth Net 49.0002.0000.0000.0004.00 Tunnel mpls traffic-eng autoroute announce *Aug 18 09:06:07.919: Fa0/0 *Aug 18 04:37:06.239: HOP type 1 length 12: Ip address 10.1.23.2 255.255.255.0 OSPF supports the following network types: P2P , broadcast, NBMA , point-to-multipoint, and on-demand circuits 2 i L2 2.2.2.0 [115/20] via 10.1.24.2, Serial0/0 1.1.1.1/32 *Aug 18 09:06:07.919: parameter id=127, flags=0, parameter length=5 PATH (Tunnel0) Destination: 4.4.4.4 Test the transmission process of the data stream, observe the phenomenon Mpls traffic-eng tunnels ip rsvp bandwidth Ip address 5.5.5.5 255.255.255.255 0/0/0 Ip router isis encapsulation frame-relay The above label, there is another way to see, is to look at the TE Tunnel directly on R2 : It can prevent the structure of the core transmission network from being exposed due to TTL=0 return error message R1#traceroute 4.4.4.4 Interface Ethernet0/0 Neighbors should use PSNP to confirm this LSP And R2 routing table at the moment is such that: 20bits If a router plurality of distribution on the net, these NET system ID must be the same. Outgoing interface 10.1.12.2 8 msec 4 msec 0 msec Here are some examples of FEC : 0/0/0 AutoRoute metric MPLS coding IP subnet Next hop 10.1.34.3, FastEthernet0/0 via 10.1.15.0/24 valid cached adjacency 101 ! Next, R2 receives the tag packet. R2 knows that this is a tag packet from the type field of the Layer 2 Ethernet frame header of this packet, so it looks for its own LFIB table: In CISCO IOS , a re-optimization of a TE tunnel is done every 1 hour by default . In order for the protection feature to work properly, you need to enable this feature on both LSRs . If one end does not support this feature, you can configure the feature in one segment and the mpls ldp discovery targeted-hello accept command on the other end to receive target-hello . 0/0/0 Fa0/0 Here's what you can verify: 0xA339 Router-id 2.2.2.2 Hello interval: 5000 ms; Transport IP addr: 1.1.1.1 LDP Id: 2.2.2.2:0; no host route to transport addr 947 Targeted neighbor relationship establishment Fa0/0 In this way ,ccna routing and switching pdf free download, we can exchange visits between 5.5.5.5 and 6.6.6.6 , on R6 . The loopback0 address space of all devices is xxxx/32 , and x is the device number. 202 Mpls ip Interface Loopback0 Configure the tunnel interface. Next, on the headend LSR , the path calculation PLALC or the restricted SPF ( CSPF ) algorithm can calculate the shortest, all conditions, from the head end LSR to the tail end according to the MPLS TE database mentioned above and the requirements of the tunnel . The path to the LSR . After the completion of the work output is from a tunnel end to a trailing end of the first IP address of the sequence, the guide path . PCALC and CSPF are variants of an SPF algorithm for MPLS TE .