Configuring Mpls L3Vpn Frr Through Vpnv4 Route Backup For An Ipv4 Route - HP FlexNetwork 10500 Series Configuration Manual

[PE1-bgp-default-ipv4-vpn1] quit
[PE1-bgp-default-vpn1] quit
# Specify the preferred value as 100 for BGP VPNv4 routes received from PE 2. This value is
greater than the preferred value (0) for routes from PE 3, so PE 1 prefers the routes from PE 2.
[PE1-bgp-default] address-family vpnv4
[PE1-bgp-default-vpnv4] peer 2.2.2.2 preferred-value 100
[PE1-bgp-default-vpnv4] quit
[PE1-bgp-default] quit
Verifying the configuration
# Display detailed information about the route to 4.4.4.4/32 on PE 1. The output shows the backup
next hop for the route.
[PE1] display ip routing-table vpn-instance vpn1 4.4.4.4 32 verbose
Summary Count : 1
Destination: 4.4.4.4/32
Protocol: BGP
SubProtID: 0x1
Cost: 0
IpPre: N/A
Tag: 0
OrigTblID: 0x0
TableID: 0x102
NibID: 0x15000002
AttrID: 0x2
Flags: 0x110060
Label: 1146
BkLabel: 1275
Tunnel ID: Invalid
BkTunnel ID: Invalid
FtnIndex: 0x0
Connector: N/A
Configuring MPLS L3VPN FRR through VPNv4 route backup
for an IPv4 route
Network requirements
CE 1 and CE 2 belong to VPN 1.
Configure EBGP between CEs and PEs to exchange VPN routes.
Configure OSPF to ensure connectivity between PEs, and configure MP-IBGP to exchange VPNv4
routing information between PEs.
Configure MPLS L3VPN FRR on PE 2 to achieve the following purposes:
•
When the link PE 2—CE 2 operates correctly, traffic from CE 1 to CE 2 goes through the path
CE 1—PE 1—PE 2—CE 2.
•
When BFD detects that the link between PE 2 and CE 2 fails, traffic from CE 1 to CE 2 goes
through the path CE 1—PE 1—PE 2—PE 3—CE 2.
Process ID: 0
Age: 00h00m03s
Preference: 255
QosLocalID: N/A
State: Active Adv
OrigVrf: default-vrf
OrigAs: 300
LastAs: 300
Neighbor: 2.2.2.2
OrigNextHop: 2.2.2.2
RealNextHop: 172.1.1.2
BkNextHop: 172.2.1.3
Interface: Vlan-int11
BkInterface: Vlan-int12
TrafficIndex: N/A
265