ccna switching

ccna switching

204 10.1.12.2 Circuit type : 01 means L1 router, 10 means L2 router, 11 means L1/2 router C 10.1.123.0 is directly connected, FastEthernet0/0 i*L1 0.0.0.0/0 [115/10] via 10.1.123.3, FastEthernet0/0 Path: valid ATT/P/OL Assign and distribute labels Untagged Such as OSPF such IGP protocol, configured or interface bandwidth cost calculated the optimal route IPv6 , then it must publish routing information with this NLPID value. 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. [6]: Mpls traffic-eng router-id loopback0 mpls traffic-eng area 0 Ip unnumbered Loopback0 tunnel mode mpls traffic-eng tunnel destination 4.4.4.4 11 LDP IETF standard ( TCP/UDP port number 646 ) TDP CISCO private ( TCP/UDP port number 711 ) Shared-Explicit (SE) FLOWSPEC R1#show mpls ldp bindings (View the LIB table of R1 ) Mpls traffic-eng tunnels mpls label range 500 599 lab environment Set priority Ip router isis interface Serial0/0 10.1.23.0/24 Fa0/0 128 Router-id 3.3.3.3 Fa0/0 IDI Initial Domain Identifier , a variable-length initial domain identifier that identifies a subdomain under AFI R2-PE1#show ip route The routing table of R2 is as follows (omit direct route): ! Neighbor 5.5.5.5 update-source Loopback0 PATH 1921.6800.1024. Contains information such as the tunnel sender address, LSP ID, etc. 75M PHP penultimate jump pop-up mechanism LSP Tunnel R1_t0 is signalled, connection is up InLabel : FastEthernet0/0, 400 In the mechanism implemented by MPLS TE , the head end router of an LSP can learn the topology of the network, and can calculate the optimal route that traverses the network to reach the router at the end of the LSP (not only the metric but also the bandwidth and chain. Road attributes and other elements). Start LSP ID : Start LSP ID . Indicates the first LSP ID of the LSP range described in the TLV field . Ip cef Next, R3 receives the tag package. Similarly,ccna switching, look at your own LFIB : The attribute used to describe the physical link consists of 32 bits . Each bit can represent an attribute of the link (such as whether it is encrypted or not) or a managed policy. There is no specific syntax for this 32bits . Each bit can be set to the latter without moving it. The network designer can think of specifying a specific meaning for a particular bit as needed . Network 10.1.12.2 0.0.0.0 area 0 BW (kbps) *Aug 18 09:06:07.919: peak rate =250000 bytes/sec *Aug 18 09:06:02.699: Minimum Path Bandwidth (bytes/sec): 1250000 Mpls traffic-eng tunnels ip rsvp bandwidth IS-IS Transient Blackhole Avoidance Select the path with the lowest IGP cost NLPID: Extended IP reachability reachability TLV (type 135 ) The TLVs used are: Attached-bit 10.1.23.3 [MPLS: Label 301 Exp 0] 124 msec 96 msec 104 msec 0 kbits/sec Fa0/0 LDP discovery sources: Et0/1 *Aug 18 09:06:02.699: SENDER_TEMPLATE type 7 length 12: *Aug 18 11:26:02.546: Which table is specifically checked depends mainly on the Layer 2 encapsulation of the received data. For example, if the Layer 2 encapsulation is Ethernet (data frame), look at the value of the Type / Length field of the frame header : 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 Two processes: neighbor discovery process, session establishment process Label Space ID is generally 0 , indicating that our label is a platform - based ( Per-platform ) label space. !! The outbound label is 301 *Aug 18 09:06:07.919: ADSPEC type 2 length 48: ! IS-IS adjacency on a multi-access link Basically, the LSP is the path through the MPLS network or a part of it that packets take. // One-way path. In fact, an LSP is a path when a packet traverses an MPLS network or a part of an MPLS network. Alternatively, you can configure the following command on the tail router: Bw[0]: Ip address 10.1.23.2 255.255.255.0 The loopback interface of R2 and R3 comes from this area, so there is no problem with the route of L1 , but is the direct link of R2-R4 and R3-R4 coming in? That's because these are the direct connections of R2 and R3 . You can configure the interface to be on S1 and 0 of R2 and S1/0 of R3 . Type escape sequence to abort. Tracing the route to 4.4.4.4 Attribute tag and affinity attribute Mpls traffic-eng tunnels mpls label range 200 299 Meanwhile, in order to avoid loops, R2 in the area level1 when injected these routes will be marked downbit , As a result, R3 receive this LSP , for these routes, it will not flood the backbone inside. Downstream on Demand max hop count: 255 Downstream on Demand Path Vector Limit: 255 LDP for targeted sessions C . There is a small detail, noted that the distribution of the label no concept of split horizon, that although B may be from C to learn the route to X , but B still will be prefixed with X passed to the bundled label C . C will also put the label passed from B in the LIB , but don't worry about loops, because LDP can prevent loops by means of IGP routing protocol. Basic concept of FRR Router-id 3.3.3.3 Static hostname mapping 55.55.55.55 and 5.5.5.5 will no longer take the tunnel . Link state Protocol Data Unit Link State Data Unit 10.1.34.4 Label Based on the platform ( of Per-Platform ) label space of just a LDPsession , even in the LDP there are multiple redundant links between neighbors 0/0/0 Interface eth 0/0 ISO 10589 The ACL filters out LDP packets. This prevents LDP adjacency between R1 and R4 from being established. Let's observe the phenomenon. ATT/P/OL Local tag: 104 MPLS TE router ID: 1.1.1.1 Then on R1 to see the tunnel , his TE metric becomes 102 . Now we will complete the following configuration on R2 : Designated IS ( DIS ) Traffic using traffic engineering uses source-based routing instead of routing based on destination IP address What is the difference between POP and Untag in Outgoing tag(Label) ? 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 . Ip unnumbered Loopback0 Router bgp 2345 OSPF packets are encapsulated in IP packets, so they are transmitted at the network layer. Mpls traffic-eng tunnels mpls ip Network 1.1.1.1 0.0.0.0 area 0 Router ospf 1 Net 49.0001.0000.0000.0002.00 The configuration of R2 is as follows: The configuration of R2 is as follows: Remaing lifetime LSP lifetime before LSP ID LSP identity Sequence num LSP serial number Explicit Path a series of IP configuration, an explicit path in the IP can be an interface IP , it may be MPLS TE Router ID . OSPF Router with ID (1.1.1.1) (Process ID 1) The fields of the same background color described above are all corresponding. Basic configuration Pay attention to the distinction between autoroute and here . The autoroute feature is not activated in our configuration above . Autoroute feature and autoroute RFC 3787 Mpls traffic-eng tunnels mpls ip *Aug 18 11:26:02.546: R3.02 Ip unnumbered loopback 0 tunnel destination 2.2.2.2 tunnel mode mpls traffic-eng Or Tunnel Id Mpls ldp router-id loopback0 mpls label range 200 299 interface fast0/0 Whether the systemID exists, if it exists, ignores the ISH . If it does not exist, the receiving router creates a new adjacency relationship, which is set to "initialization" state, and the system type is "unknown". The IIH response is then sent . If the router receives an IIH packet from the new neighbor , the router sets the adjacency to UP and the system type is IS . However, there is a problem here. After the local IIH is sent, I don’t know if the other party is If it is received, then there is a possibility that the message will be lost in the middle and the UP side will be DOWN . So we introduced a three-way handshake mechanism, see below.