ccna ccda

ccna ccda

Route Distinguisher: 2345:6 Record Route: NONE Bandwidth: 0 kbps (Global) Priority: 7 7 Affinity: 0x0/0xFFFF Metric Type: TE (default) ! On the initial router, is it looking for FIB or LFIB ? 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: *Aug 18 11:31:44.598: ISO10589 Prior LSP: ! R1#show ip route 5.5.5.0 Router ospf 1 Retention mode (the Label Retention) : free mode (Liberal Retention) Type 2 length 36: Length OO Mpls label range 100 199 !! It can be seen that the f0/0 port has been separated by 33M. Local binding: tag: 101 00 Configure path protection on R2 and observe the phenomenon. (Link ID) Network/subnet number: 2.2.2.2 (Link Data) Network Mask: 255.255.255.255 Number of TOS metrics: 0 Link state information IGP itself supports *Aug 18 09:06:07.919: 10.1.24.4 (Strict IPv4 Prefix, 8 bytes,ccna ccda, /32) ! By default, the OSPF hold time ( dead-interval ) is Run OSPF on the entire network to announce direct connection and loopback interface. Network 10.1.34.4 0.0.0.0 area 0 The LSR route may receive multiple labels of a specific prefix ( distributed by multiple LDP neighbors), but he only needs to use one of them. The IP routing table is used to determine the next hop of the IPv4 prefix ( the construction of the LFIB needs one). IGP routing table, because the next hop of LFIB is calculated from the IGP table). The LSR uses this information to create its LFIB . The label bundled locally in the LFIB is used as an inbound label, and the label advertised by the LDP neighbor is used as an outbound label.