ccna training center

ccna training center

0x2995 ISs flood new LSPs to all neighbors Label 3 implicit null label About flooding Network 2.2.2.2 0.0.0.0 area 0 ! 906 55.55.55.55 [110/31] via 5.5.5.5, 00:00:01, Tunnel0 LDP initial/maximum backoff: 15/120 sec LDP loop detection: off Interface Ethernet0/1 The configuration of R2 is as follows (the tunnel is not configured temporarily ): 75000 BW (kbps) 0 kbits/sec Above we can see the reservable bandwidth of all tunnel priorities. Now let's modify the reservable bandwidth of the tunnel with priority 6 . Interzones can only be interconnected via L2 or L1/L2 routers Configuration example Version/ Protocol ID extension: Value is 1 Label Mpls label rangempls label range 100 199 interface fa0/0 The overload router participates in the calculation as the last hop route. Use set-overload-bit to manually set the overload bit. Auto Route : i L1 i L2 Traffic using traffic engineering uses source-based routing instead of routing based on destination IP address Local Circuit ID Local circuit ID is a link identifier. The identity of this circuit is assigned by the router that sent the Hello PDU and is unique on the interface of the router. At the other end of the point-to-point link , the local circuit ID in the Hello message may or may not be the same value. InLabel : - Clear domain authentication Administrator-weight , and only the IGP metric is used to calculate the shortest path of the tunnel . For the device number, this IP is also the LDP routerID . Assuming the bandwidth of the local physical outgoing interface is 100M , the default reservable bandwidth of rsvp is 75% . Here is 75M. 2.0.0.0/24 is subnetted, 1 subnets R1#traceroute 55.55.55.55 ● Ip router isis Link state messages are used to propagate link and node information in the area (describe the topology of the local network) Network 10.1.45.5 0.0.0.0 area 0 Interface Ethernet0/1 Link Sharing Detail: 20bits After the tunnel setup failed Ip router isis 4.4.4.4/32 *Aug 18 11:26:02.546: 13 System ID , larger than Interface Where IS neighbor is placed adjacent to the MAC Appears only in the LSP of the L1 router . List the adjacent L1-router and the end Then by default, R1 goes to .5.5.5.5 and 55.55.55.55 is definitely preferred from E0/1 directly to R5 . But what if we want R1 to go to TE tunnel on .5.5.5.5 and 55.55.55.55 traffic ? 101 Let's take a look at the routing table for R1 : 103 Type 7 length 12: Level1 area The TLVs used are: Router ospf 1 *Aug 18 11:26:02.546: An IS-IS router can be configured to summarize IP routes into Level 1, Level 2, or both, at the same time, The area address groups configured on the router are listed. Used to uniquely identify an LSP and authentication source router R2.00-00 At this point for R2 , he has two paths to 5.5.5.5 and 55.55.55.55 . LSP Holdtime The LSA is encapsulated into the LSU to advertise to the neighbor Initialization message *Aug 18 09:06:02.699: Minimum Path Bandwidth (bytes/sec): 1250000 0x2D6E The forwarded keyword indicates that this command is valid for traffic traversing the router. The Local keyword indicates that the traffic generated locally is effective. Ip address 1.1.1.1 255.255.255.255 The configuration of R2 is supplemented as follows: Admin: up 10.1.23.3 In a broadcast multi-access network, a router is elected as a DIS , and a peer-to-peer network does not require a DIS. Experimental needs Reservable Bandwidth[5]: Protocols support Then, finally, the data is introduced into the established tunnel . In fact, after creating a TE tunnel on R1 , a local tunnel is in it. The configuration of R5 is as follows: ! !! Cross-regional words must use loose next hop Configure this feature on the A device (usually on the edge device) no mpls ip propagate-ttl Tunnel mpls traffic-eng autoroute metric absolute y Switched Moreover, since the default duration is indefinite, these entries will remain. Of course, if you modify the configuration on R1 : Maximum reservable bandwidth information: 10.1.34.4 *Aug 18 11:26:02.546: Incoming Resv: !! R2 sends a resv message to R1 TOS 0 Metrics: 10 Label or VC BW (kbps) Remote binding: tsr: 2.2.2.2:0, tag: 201 The configuration of R1 is as follows: Ip router isis 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. R1 Show mpls ldp discovery show mpls forwarding-table !! ldp 's routerid uses loopback port IP DC Router-id 1.1.1.1 Then the LSR pushes the IP packet into a tag header, tags 204 , and forwards it out from the F0/0 interface. In CISCO IOS , CEF switching is the only IP forwarding mode that can be used to mark messages . Therefore , CEF must be enabled on the router when MPLS is enabled . Peer LDP Ident: 2.2.2.2:0; Local LDP Ident 1.1.1.1:0 TCP connection: 2.2.2.2.31044 - 1.1.1.1.646 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. Level1 : Relative to the concept of a single area, consists of L1 routers in this area, and its routing information is published to Backbone . Mpls traffic-eng tunnels mpls ip 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 Router(config-if)#tunnel destination ip-addr *Aug 18 11:26:02.546: The authenticated TLV is not seen in the PSNP message . Network 10.1.45.4 0.0.0.0 area 0 mpls traffic-eng router-id loopback0 mpls traffic-eng area 0 Mpls traffic-eng tunnels ip rsvp bandwidth 0x0000000E Router bgp 123 Finally, let's complete the configuration of R1 : Global Pool Sub Pool *Aug 18 11:26:02.546: IS reachability R2(config)#key chain test R2 (config-keychain)#key 1 Fast Reroute ( FRR ) is a link or node protection mechanism. Allows the headend router to rerouting when there is a problem with the link or node , and uses a temporary, pre-established path to bypass the point of failure. Interface Tunnel0 *Aug 18 09:06:07.919: Controlled Load Service break bit=0 service length=0 *Aug 18 09:06:07.919: min unit=0 bytes, max pkt size=2147483647 bytes The IS-IS packets have the same common 8B above ,ccna training center, 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. Mpls traffic-eng tunnels mpls label range 400 499 RFC 3847 ● 0xE1E2 LSP serial number Router , thus maintaining two independent L1 link state databases and L2 link state databases. Then, if there is a router in the backbone that is not connected to the L1 router , it can be configured as an L2 router . R2#show ip route Uptime: 5 minutes, 53 seconds Prior LSP: Mpls ldp discovery targeted-hello accept from accept-ldp Set-overload-bit on-startup wait-for-bgp We introduce a new TLV (type 240 ) , known as " Point-to-Point Adjacency State ", if the device does not support the new features include the receipt of TLV of IIH , will ignore this TLV , so you can ensure backwards compatible. IGP Neighbor: ID 10.1.23.2 Ip address 1.1.1.1 255.255.255.255 *Aug 18 09:06:07.919: SESSION type 7 length 16: The current maximum available bandwidth is listed under the interface according to their respective priorities. Network 10.1.34.4 0.0.0.0 area 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. 10.1.34.0/24 SESSION Network 10.1.45.5 0.0.0.0 area 1 The downstream label was not transmitted, because LDP Neighbor was not established. However, there may be such a problem that the LDP connection between R1 and R2 is broken for some reason, but between R1 and R2 . Switched Broadcast network 75000 Next, R3 receives the tag package. Similarly, look at your own LFIB : S 4.4.4.4 is directly connected, Tunnel0 1.0.0.0/24 is subnetted, 1 subnets R3.01-00 Src 1.1.1.1, Dst 4.4.4.4, Tun_Id 0, Tun_Instance 2 RSVP Path Info: For the highest loopback port IP Average rate = 250000 bytes/sec, burst depth = 1000 bytes Test . 5 : SET 'bit-overload-the suppress interlevel 10.1.34.0 [115/20] via 10.1.23.3, Serial1/0 Explicit Route: 10.1.12.2 10.1.23.2 10.1.23.3 10.1.34.3 104 ISO 9542 ISO10589 The first is the case of no forwarding adjacency: ! Ip cef Wait for the message to view the adjacency. Next, the DIS election process begins . Current LSP: 3.3.3.3/32 LSPDB Mpls traffic-eng tunnels ip rsvp bandwidth Mpls traffic-eng tunnels ip rsvp bandwidth Of course, not the remote tag in LIB will be used. We also need to combine the FIB table to get the next hop information about the prefix. Finally form the LFIB table: AutoRoute: enabled LockDown: disabled Loadshare: 2000 bw-based auto-bw: disabled It is also IPv6 because it receives an IP packet instead of a label packet. 1112 Mpls ip MPLS application Ip unnumbered Loopback0 tunnel destination 5.5.5.5 *Aug 18 09:06:07.919: 10.1.24.2 (Strict IPv4 Prefix, 8 bytes, /32) MTU problem R1#show isis neighbors 0180-C200-0015 Type 1 length 8 : Look at the routing table for R1 : Mpls ldp session protection for 1 duration 30 Status O Type 10 flooding range only in this area Label Space ID is generally 0 , indicating that our label is a platform - based ( Per-platform ) label space. *Aug 18 04:37:06.239: General Parameters break bit=0 service length=8 For Level1 router , the area number is required to be the same. Default metric is supported by all IS-IS routers and is often interpreted as a measure that is inversely proportional to bandwidth. Interface eth 0/1 R1#traceroute 55.55.55.55 Current LSP: Intermediate System Intermediate System Interface fast1/0 Interface tunnel0 105 Network 55.55.55.55 area 0 ! ! Appears only in the LSP of the L1 router . List the adjacent L1-router and the end Password: not required, none, in use 947 4.4.4.4/32 i L1 i L2 Link connected to Broadcast network Link ID : 10.1.12.2 R1# *Aug 18 11:26:02.546: Name: R1_t0 (Tunnel0) Destination: 4.4.4.4 Status: Ok, now when R1 is going to ping 4.4.4.4 , R1 has to check its own FIB , which is the CEF table. Note that this is an IP lookup: Lighter, only LSPs in this area . Record Route: NONE Designated IS ( DIS ) ES-IS Router(config)#mpls traffic-eng reoptimize timers frequency ? Tag header TTL and IP header TTL is the same, is usually copied from IP header TTL value (when an IP packet enters the MPLS network), which is TTL propatation Reservable Bandwidth[4]: Tag Does it match, verify that the password is correct, the area ID or something. Maximum reservable bandwidth : 9375000 Number of Priority : 8 i L1 O bit We can define the priority of the TE tunnel Router(config)#interface fast0/0 13223 Interface FastEthernet0/0 ISIS for NBMA support network is still flawed, as in the previous experiment demonstrates, if it is run on a Frame Relay main interfaces ISIS , or P2MP run on sub-interfaces ISIS , then you must ask PVC full-mesh, otherwise, the route study Not normal, but even if the PVC is fully interconnected, there are hidden dangers. If a PVC fails, routing will still have problems. IS-IS supports plain text and cipher text MD5 authentication. Let's make a small summary below: *Aug 18 04:37:06.239: Mpls traffic-eng tunnels ip rsvp bandwidth Configure targeted-hello accept acl The configuration of R4 is as follows: Ip address 2.2.2.2 255.255.255.255 When the router initiates IIH , the circuit type in the header is set according to the configuration we have made : L1 , L2 or L1-2 . MPLS TE using type 10 of LSA to a region within MPLS TE work. Router ospf 1 Time since created: 11 minutes, 42 seconds Time since path change: 10 seconds Number of LSP IDs (Tun_Instances) used: 9 8bit maximum 255 , usually in the labeling when it is the ordinary ip packet TTL direct copy came IS-IS allows the entire domain to be divided into multiple zones, using a two-level hierarchical structure. R1(config-keychain)#exit Type-10 Opaque Link Area Link States (Area 0) Here's what you can verify: Show mpls traffic-eng link-management bandwdith-allocation MPLS LDP-IGP synchronization example 55000 10.1.23.2 Protocols support Fspec: ave rate=2000 kbits, burst=1000 bytes, peak rate=2000 kbits History: Can use the default or use this command to modify Router(config-if)# bandwidth ? Note ESH and ISH PDU are ES-IS of the PDU instead of IS-IS of the PDU Now let 's take the traffic going to 4.4.4.4 on the R1 to the tunnel , using one of the simplest methods: static routing. [5]: 75000 kbits/sec 3.3.3.3/32 55.55.55.55 and 5.5.5.5 will no longer take the tunnel . Mpls traffic-eng router-id Loopback0 mpls traffic-eng area 0 * Aug 18 04: 37: 06.239 : Outgoing PathTear: !! dismantle tunnel *Aug 18 09:06:07.919: SENDER_TEMPLATE type 7 length 12: MPLS TE considers configuring (static) bandwidth on the link Now let 's take the traffic going to 4.4.4.4 on the R1 to the tunnel , using one of the simplest methods: static routing. Version = 0 length in words = 7 service id = 5, service length = 6 1.0.0.0/24 is subnetted, 1 subnets The interface IP of R3 is 10.1.23.3 . Network 10.1.23.3 0.0.0.0 area 0 TE metric is a parameter used to build a TE topology that is completely different from the IP topology (although by default it is equal to IGP metric ) 3.3.3.3 Fa1/0 The configuration of R4 is as follows: Mpls traffic-eng router-id Loopback0 mpls traffic-eng area 0 The default on the point to point link 10S sent once IIH . 55.55.55.55 [110/31] via 10.1.23.3, 00:02:29, Ethernet0/1 SESSION Show ip route isis ! 5.5.5.5 [110/31] via 10.1.23.3, 00:03:44, Ethernet0/1 In the above experiment, we announced the direct connection network of R1-R5 and R4-R6 in Core OSPF . However, we know that in actual situations, this chain outside AS is not declared in Core IGP . Road, so let's take a look at it. If you do not announce these two direct links in OSPF , what will happen : Since OSPF does not have these two directly connected segments, then 5.5.5.5 and 6.6.6.6 learn to come in. preferably not a need in R1 of the R4 to use Next-Hop-Self , R4 to R1 is also the same reason.