
378
Display routes destined for 4.4.4.4/32 on PE 1. You can see that the active route has a backup
next hop.
[PE1] display ip routing-table vpn-instance vpn1 4.4.4.4 verbose
Routing Table : vpn1
Summary Count : 2
Destination: 4.4.4.4/32
Protocol: BGP Process ID: 0
Preference: 255 Cost: 0
IpPrecedence: QosLcId:
NextHop: 2.2.2.2 Interface: NULL0
BkNextHop: 3.3.3.3 BkInterface: NULL0
RelyNextHop: 0.0.0.0 Neighbor : 2.2.2.2
Tunnel ID: 0x64000C Label: 65536
BKTunnel ID: 0x64000A BKLabel: 1026
State: Active Adv GotQ Age: 00h00m16s
Tag: 0
Destination: 4.4.4.4/32
Protocol: BGP Process ID: 0
Preference: 255 Cost: 10
IpPrecedence: QosLcId:
NextHop: 3.3.3.3 Interface: NULL0
BkNextHop: 3.3.3.3 BkInterface: NULL0
RelyNextHop: 0.0.0.0 Neighbor : 3.3.3.3
Tunnel ID: 0x64000A Label: 1026
BKTunnel ID: 0x64000A BKLabel: 1026
State: Inactive Adv GotQ Age: 00h00m16s
Tag: 0
Example 2 for configuring MPLS L3VPN FRR
Network requirements
CE 1 and CE 2 belong to VPN 1. The route target used by VPN 1 is 111:1.
Configure EBGP between the CEs and PEs to exchange VPN route information.
Between the PEs, configure OSPF to enable them to communicate, and configure MP-IBGP to
exchange VPN route information.
Configure FRR on PE 2 so that when the link between PE 2 and CE 2 fails, traffic from CE 1 to CE 2
can be switched to the link PE 2—PE 3—CE2.