best cisco test prep

best cisco test prep

Router-id 1.1.1.1 Tspec parameter id = 127, flags = 0, length = 5 Link IP Address: 10.1.23.2 For example, R1 . 01 - 00, where R1 is SystemID (this is the system ID based on the host name ), 01 is the PseudonodeID pseudo node ID , and if it is sent by the pseudo node, it is non- 00 , 00 is the fragment number. Set as a P2P sub-interface or broadcast link (if it is fully interconnected) 3.3.3.3 Tib entry: 4.4.4.4/32, rev 14 TE overview - A list of directly connected IP address prefixes is listed, which is only used in non-pseudo-node LSPs . Router isis 75000 PSNP 0x2F89 In operational contexts , a tunnel can be removed from one path and palced onto another. 200 DIS , initially composed of the local SystemID + unique local circuit ID . The router starts to listen to ESH , ISH , IIH at the same time . R2 (config)#router isis This will cause the route of R2 to change. The outgoing interface of the route to 5.5.5.5 and 55.55.55.55 becomes e0/1 . So R2 goes to Advertising Router: 1.1.1.1 LS Seq Number: 80000001 ! Router ospf 1 Periodic reoptimize " MPLS technology architecture."! In a network running MPLS , you can set these two paths to different LSPs and use different labels. On R1 , R6 and 0x00000037 Outgoing interface A route 10.1.1.0/24 on E was advertised, and now it is summarized on C. The summary route is 10.1.0.0/16 and is advertised to B. Note: a IS-IS routing domain ( routing Domain ) does not necessarily need to have two levels, if only a region of deployment,best cisco test prep, it may be all L1 or all L2 of , recommended L2 of , to obtain a good scalability. 0 kbits/sec Therefore, the router will not BGP direct distribution label route, but for BGP routes by next hop routing label distribution after the recursion, this is very good. BGP routing entry is pretty much, by this way we MPLS , can greatly simplify the performance loss routers, BGP 's Transit AS routing black hole problem has been solved. Router-id 4.4.4.4 By selection ( level2 routing) Network 2.2.2.2 0.0.0.0 area 0 ...... ...... Redistribute isis ip level-2 into level-1 route-map test IGP Neighbor: ID 10.1.12.2 Next we R1 on shutdown Fa1 / 0 mouth, then R1 on a look: According to the protection object can be divided into: *Aug 18 09:06:02.699: Flags: (0x7) Local Prot desired, Label Recording, SE Style !! Flags are reflected in the flag Pop tag Insert ( impose or push ) 0x2995 Network 10.1.23.3 0.0.0.0 area 0 Or Tunnel Id Tunnel mpls traffic-eng autoroute announce tunnel mpls traffic-eng priority 7 7 Virtual link By default, TE metric is used as the basis for calculating the shortest path of a TE tunnel. When you are in a LSR configured on a TE Tunnel when the LSR becomes this TE tunnel head-end LSR . Next you can specify the destination LSR of the TE Tunnel , and the restrictions it must comply with, such as the guaranteed bandwidth of the tunnel, etc. These related parameters are at the headend LSR . After the above configuration is completed, there is one more unidirectional direct link to R5 on R2 . This link will directly participate in the routing calculation of R2 itself. The overall result is that there are now three straight connectors on R2 : eth0/0 , eth0/1 , tunnel0 . Next Hop In this environment, since the tail end of the tunnel is at R4 , the label that R4 assigns to this tunnel through RSVP is POP . 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 . Version : value is 1 Interface eth0/0 0 kbits/sec My Address: 10.1.23.2 MPLS TE router ID: 1.1.1.1 Ip address 55.55.55.55 255.255.255.255 10.1.45.5* Interface Interface loopback0 *Aug 18 11:26:02.546: Next Hop Then on R1 to see the tunnel , his TE metric becomes 102 . *Aug 18 04:37:06.243: peak rate = 250000 bytes/sec *Aug 18 04:37:06.239: Tun Sender: 1.1.1.1 LSP ID: 20 Interface eth0/0 No output feature configured ! Mpls ldp neighbor 2.2.2.2 targeted ldp Redistribute connected level-1 For the first layer LSP database, you use the first 1 layer CSNP and PSNPs , for the first 2 used in the first layer 2 layer CSNP Next-address 10.1.23.3 Net 49.0001.0000.0000.0002.00 1.1.1.1:0 0x2995 Neighbor 10.1.24.4 remote-as 45 no auto-summary Class of data – The FEC which is mapped onto it ! MPLS label header. At the same time, the header of the Layer 2 data link layer will be instructed accordingly. For example, the Ethernet data frame, the TYPE field of the MAC layer indicates whether the upper layer data is an mpls label frame (if it is an IPv4 packet, the value is 0x0800 , if it is a label packet) Then it is 8847 -unicast or 8848- multicast) Mpls traffic-eng tunnels ip rsvp bandwidth Interface eth0 1/0 MPLS label header. At the same time, the header of the Layer 2 data link layer will be instructed accordingly. For example, the Ethernet data frame, the TYPE field of the MAC layer indicates whether the upper layer data is an mpls label frame (if it is an IPv4 packet, the value is 0x0800 , if it is a label packet) Then it is 8847 -unicast or 8848- multicast) Remote binding: tsr: 2.2.2.2:0, tag: imp-null 3.3.3.3 [110/65537] via 10.1.12.2, 00:00:47, FastEthernet0/0 Config Parameters: 1010 Configure the requested bandwidth of the tunnel Next, the data is sent to R3 . After R3 checks its own LFIB table, it replaces the 303 tag with 203 and then throws it to the next hop R2 . After receiving the label package, R2 looks at its own LFIB table and finds that the outgoing action is a PoP . Then the label is ejected and becomes the original IP packet, and then it is thrown to R1 . Finally, R1 forwards the IP packet to R5 . So why is R2 here PoP here ? The answer is that this BGP routing, we talked about earlier, in fact, it is using a next hop 10.1.15.0 label, 10.1.15.0 is R1 directly connected network segment, so the R1 when the label assigned to the route , gave it aPoP , then distribute this result to R2 , which is why.