ccna india

ccna india

Interface eth0 1/0 The routing table for R1 is as follows: Options: (No TOS-capability, DC) LS Type: Opaque Area Link Flag position 100 Neighbor discovery is performed by means of the Hello packet of UDP . The source and destination port of this Hello packet are both UDP646 . If it is a Frame Relay P2P sub-interface, then there will be no problem,ccna india, this is the recommended deployment method. General Parameters break bit=0 service length=8 The configuration of R2-PE1 is as follows: 75000 kbits/sec, 0x00000014 A targeted LDP neighbor relationship has been established with R4 . Outgoing Each tag mapping message contains two elements : FEC TLV and Label TLV Configure the destination of the tunnel ! Then analyze in detail: The first is R2 on Prior LSP: 10.1.23.3 [MPLS: Label 300 Exp 0] 4 msec 0 msec 4 msec TOS 0 Metrics: 1 We started CEF on R3 . In fact, in CEF , the default load balancing method is destination-based load balancing. CEF 's Router-id 1.1.1.1 In TLV ), other messages were not seen. The command is as follows (interface level): Routing domain *Aug 18 04:37:06.239: version:1 flags:0000 cksum:DEB3 ttl:255 reserved:0 length:132 The configuration of R5-PE2 is as follows: Each metric type is 8bits and has the following form: We went to traceroute on R1 6.6.6.6 R1#traceroute 6.6.6.6 Reservable Bandwidth[2]: Bw[3]: ! NNHop ( Next-Next Hop Router ): Next hop router, next hop of the PLR next hop router Ip address 10.1.12.1 255.255.255.0 Router-id 2.2.2.2 It has been verified by experiments. Point2point Activate the MPLS TE extension for each router's OSPF and manually set the RouterID for MPLS TE . 75000 Link type supported by IS-IS We see that R5-PE2 assigns a 505 label to VPN customer route 6.6.6.6 . Note: IS-IS 's Backbone is not what a particular area *Aug 18 09:06:07.919: 10.1.12.2 (Strict IPv4 Prefix, 8 bytes, /32) Redistributing via isis ! ( NLPID 0x81 ) and IP ( 0xCC ) Of course, the above method is not safe. Therefore, in special cases, we may want the L1\L2 router to conditionally set the ATT bit and set it more controllable. Then we can associate the route-map and match a specific one in the route-map . Routing, as long as this route is in my routing table, route-map is satisfied, I will set ATT . Form a LAN adjacency: Ip address 10.1.12.1 255.255.255.0 Link IP Address: 10.1.12.2 Interface eth 0/0 Ip address 10.1.23.3 255.255.255.0 IGP metric: 1 Addresses bound to peer LDP Ident: 10.1.34.3 Moreover, since the default duration is indefinite, these entries will remain. Of course, if you modify the configuration on R1 : The TLV section contains fields for system characteristics, as shown below: [5]: 75000 kbits/sec The configuration of R1 is as follows: 0/0/0 Peak rate LS age: 705 You can use the above command to modify the TE metric (configured on the physical interface). ! L1/L2 router is usually located on the area boundary !! Re-release the local direct loopback 2.2.2.0/24 to level1 100 Version:1 flags:0000 cksum:7931 ttl:255 reserved:0 length:132 Routing information diffusion and database synchronization LDP adjacency establishment process Router ospf 1 1.1.1.1:0 204 403 5.5.5.5/32 0 Tu0 point2point MAC/Encaps=14/22, MRU=1496, Label Stack{305 403} , via Et0/1 0E00003017000E00003016108847 0013100000193000 !! TE tunnel LSP ID (link status packet identifier) In the TE tunnel, a signaling protocol is needed to ensure that the link of the LSR interface traversed by the TE tunnel can be used and can be hop-by-hop. Tunnel mpls traffic-eng autoroute metric 9 Interface eth 0/0 MPLS TE configuration and experiment Tun Dest: IGP Id: 1.1.1.1, MPLS TE Id: 1.1.1.1 Router Node id 1 Free mode : Liberal Retention According to the protection object can be divided into: 200 Swap TLV *Aug 18 11:31:44.598: Level1 area Receives packets from other L2 routers in the area and forwards the packets to the L2 routers of other areas according to the destination address (or to the L2 router of the same area ). Receive packets from L2 routers in other areas and forward the packets according to the destination address. 3.3.3.3 Or Tunnel Id Router-id 2.2.2.2 Fa0/0 Name: R1_t0 Status: 75000 !! TE metric , the default is equal to the following IGP metric AutoRoute defect ! If a router plurality of distribution on the net, these NET system ID must be the same. Two modes: frame mode ; ATM mode ( cell mode ), we mainly study frame mode L2 rouer redistributes external routes into IS-IS *Aug 18 11:26:02.546: Interface eth 0/0 You can use the no mpls ldp igp sync command on a particular interface to turn off synchronization on the interface. Thus, as long as 5.5.5.0 in R2 , then the routing table of R2 will, in its region to 49.0001 in flooding- LSP for the ATT is set, we can try to R5 of Loopback the shutdown , so 5.5.5.0 hung , and when R2 is detected this change, not found in the routing table 5.5.5.0/24 route, then R2 will trigger a LSP updates the LSP in the ATT not set, so a to R1 will only produce a Point to the default route for R3 . When 5.5.5.0 is restored, then R2 will generate an LSP and set ATT again (this 5.5.5.0The route does not have to be an ISIS route. You can play it with a route pointing to null0 , and set the ATT .) One thing to note here are: tools used to match the recommended route prefix list, I was in 12.