ccna 200 120 book pdf

ccna 200 120 book pdf

Fa0/0 8 - Control plane : exchanges Layer 3 routing information (such as OSPF , ISIS , BGP, etc.) and labels (such as TDP , LDP , BGP, and RSVP ). Time since path change: 10 minutes, 34 seconds Number of LSP IDs (Tun_Instances) used: 521 Signalling: connected Type 2 length 48: Based on the information in the link state database, the almost identical algorithm, the SPF algorithm, is used to calculate the optimal route. MTU problem 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. Number of Links : 1 ! Route Distinguisher: 2345:6 L1 !! Note area0 and area1 must activate MPLS TE Supports allocating network resources for explicit LSP tunnels Default change threshold (bandwidth occupancy): !! Change to 33M Complete basic IP configuration (configuration omitted) Network 10.1.12.1 0.0.0.0 area 0 Interface Ethernet0/0 Note that this time R2 generated LSP already set overload-bit up , the R1 on the show isis database to see 10.1.12.2 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 . Version = 0 length in words = 7 service id = 5, service length = 6 Fspec: ave rate=20000 kbits, burst=1000 bytes, peak rate=20000 kbits Area-password cisco Tunnel mpls traffic-eng autoroute announce R1#show isis database verbose R1.00-00 LSPID R3.02-00 Up time: 00:00:33 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. Adjacency relationship Up or Down ; Network 10.1.45.5 0.0.0.0 area 1 Outgoing Label The MPLS TE tunnel itself does not support the IGP routing protocol because: AS 10.1.34.4 [MPLS: Label 400 Exp 0] 4 msec 0 msec 4 msec 2.2.2.2 If the sysID length is inconsistent, the IIH is ignored . LDP neighbor discovery Router(config)#mpls traffic-eng reoptimize timers frequency ? Interface Tunnel0 Ip explicit-path name R3R4 enable next-address 10.1.23.3 Support for recording each site through which the LSP tunnel passes, which can be used to prevent loops Such as LDP ID = 1.1.1.1:0 Metric Type: TE (default) InLabel : - Ip address 10.1.34.3 255.255.255.0 *Mar 1 00:00:32.763: ISIS-Upd: full SPF required *Mar 1 00:00:32.759: ISIS-Upd: Building L2 LSP The configuration of R2 is as follows (all configurations are omitted from the configuration of interface IP ): The local device will actively advertise the generated label mapping message to all LDP neighbors. Interface loopback0 Ip address 10.1.12.2 255.255.255.0 Tunnel mpls traffic-eng path-option 10 dynamic Net 49.0001.1111.2222.3333.00 Remote binding: tsr: 2.2.2.2:0, tag: imp-null tib entry: 3.3.3.3/32, rev 6 IS-IS by Hello PDU padding size to the interface MTU large Mpls traffic-eng tunnels ip rsvp bandwidth Network 10.1.12.2 0.0.0.0 area 0 Path Protection 0x8000001A 0x002ED2 0 204 Mpls ldp router-id loopback0 mpls label protocol ldp 562 Rational use of network resources Router ospf 1 Interface Ethernet0/0 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. About LDP and IGP synchronization Device Internet segment 10.1.xy.0 / 24 , where xy is the device number, X small y large To update the LSDB ,ccna 200 120 book pdf, the LSP will be cleared from the LSDB . After the old LSP is cleared from the LSDB , it will remain for a while. Local The default MaxAge is 1200 seconds and ZeroAgeLifetime is 60 seconds. When the serial number of the LSP sent by an IS reaches Again, as long as set-overload-bit is used , the overload-bit of the LSP sent by R2 will be set. Debug information on R1 Therefore, the MPLS VPN environment, if we MPLS VPN Backbone inherent R1 to R5 establish a TE the Tunnel , is not 10.1.23.2 PATH Network 10.1.45.5 0.0.0.0 area 1 1 Average output rate based on each tunnel NSEL is 00 ( 1B from the right ) The system ID is 0000.0c00.1111 The area ID is 39.0f01.0002 IP lookup and tag lookup LSPID LSP Seq Num LSP Checksum LSP Holdtime ATT/P/OL Interface fast0/0 Peak rate ! By default, if the synchronization is not completed, the IGP does not explicitly know the time to wait before establishing the adjacency relationship. How long in msecs to wait upon flooding a down forwarding adjacentcy System ID 6 -byte system ID , ES or IS identifier, similar to OSPF 's Router ID , each device has a system ID , and the IP network, each interface has an IP , which is the difference between one of . Note: The SystemID must be unique across the entire Area and trunk ( Level2 ). 10.1.34.4 [MPLS: Labels 404/505 Exp 0] 0 ​​msec 0 msec 0 msec IS-IS interface. If the interface is attached to a multiaccess network, the circuit ID is concatenated with the system ID of the DIS ” Default metric R1#traceroute 55.55.55.55 Router-id 2.2.2.2 Is-type level-1 metric-style wide 0/0/0 MPLS TE status Network 10.1.45.5 0.0.0.0 area 0 5.5.5.5 [110/31] via 10.1.23.3, 00:03:44, Ethernet0/1 Then R1 will limit the establishment of targeted session of the peer , is 3.3.3.3 , which is R3 of LDP routerid , in addition, LDP session protection time is 30S , that is to say, 30S If the LDP neighbors yet up, targeted session will fail. Naturally, the protected tag information stored in the LIB is gone. Take a look at the routing table for R1 : IPv6 Reachability : The value of the type is 236 ( 0xEC ). The reachability of the network is described by defining the routing information prefix and metric. 1.3 OSI protocol stack terminology RSVP extension to LSP tunnel 10.1.34.0 [115/20] via 10.1.23.3, Serial1/0 Bandwidth information First R2 routing table: Create a TE tunnel on R1 , the source is its own loopback0 , and the destination is 4.4.4.4 of R4 . Ip address 10.1.12.2 255.255.255.0 The TLVs used are: The IIH is transmitted between ISs . 3.3.3.3 At this time, R2 goes to 55.55.55.55 , and the traditional IP data is taken instead of the LSP . !! The maximum reservable bandwidth is 75M 2 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 Load balancing of label packets 10.1.23.3 Tunnel mpls traffic-eng autoroute metric 9 Router(config-if)# mpls traffic-eng path-option x {dynamic | explicit name y } [ lockdown ] Domain-wide Prefix Distribution with Two-Level IS-IS Options: (No TOS-capability, DC) LS Type: Opaque Area Link Router isis Interface loopback0 ip router isis Next Hop Is-type level-1 metric-style wide Interface loopback0 ip router isis (Link ID) Designated Router address: 10.1.12.1 (Link Data) Router Interface address: 10.1.12.2 Number of MTID metrics: 0 C 10.1.24.0 is directly connected, Serial0/0 C 10.1.45.0 is directly connected, Serial0/2 C 10.1.34.0 is directly connected, Serial0/1 i L2 10.1.123.0 [115/20] via 10.1.34.3, Serial0/ 1 E Tag or VC MPLS label *Aug 18 09:06:07.919: Mpls traffic-eng router-id loopback0 mpls traffic-eng area 0 FastEthernet0/0 (ldp): xmit/recv Enabled: Interface config Ip router isis Ip address 10.1.56.5 255.255.255.0 Explicit Route: 10.1.45.5 5.5.5.5 State: Oper; Msgs sent/rcvd: 9/9; Downstream In the LSP , and if the LSP is divided into different segments, then the TLV word I/E MPLS does not assign labels to BGP routes, but assigns labels to the next hop of BGP routes. As a result, the Level 1 LSP sent by R1 carries the cipher text authentication TLV . However, since R2 does not enable authentication, the LSPs sent by R1 are sent to R2 . R2 ignores the authentication information in the LSP and directly reads the LSP . Therefore, R2 can learn the route advertised by R1 . Of course, there is no R1 routing. Ip cef *Aug 18 09:06:07.919: SENDER_TSPEC type 2 length 36: Interface Tunnel0 As a result, the size of the LSPDB is greatly reduced. Note that the above picture is just an abstraction and simulation concept. The ABCD four routers actually have ISIS adjacencies (in IS-IS broadcast). In the network, adjacencies are formed between routers of the same level on the same network segment, including all non- DIS routers. This is different from OSPF . However , after DIS , everyone The resulting LSP volume is reduced. That is to say, although all routers on the IS-IS broadcast network form an adjacency relationship, the synchronization of the LSDB is still guaranteed by the DIS . The LSP stability and reliability has been guaranteed. The operation of the SPF algorithm is naturally faster.