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

# Configure FRR for VPN instance vpn1 to use routing policy frr.
[PE2-bgp-default] ip vpn-instance vpn1
[PE2-bgp-default-vpn1] address-family ipv4 unicast
[PE2-bgp-default-ipv4-vpn1] fast-reroute route-policy frr
# Specify the preferred value as 200 for BGP routes received from CE 2. This value is greater
than the preferred value (0) for routes from PE 3, so PE 2 prefers the routes from CE 2.
[PE2-bgp-default-ipv4-vpn1] peer 10.1.1.1 preferred-value 200
[PE2-bgp-default-vpn1] quit
[PE2-bgp-default] quit
Verifying the configuration
# Display detailed information about the route to 4.4.4.4/32 on PE 2. The output shows the backup
next hop for the route.
[PE2] 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: 0x2
Cost: 0
IpPre: N/A
Tag: 0
OrigTblID: 0x0
TableID: 0x102
NibID: 0x15000002
AttrID: 0x0
Flags: 0x10060
Label: NULL
BkLabel: 1275
Tunnel ID: Invalid
BkTunnel ID: 0x409
FtnIndex: 0x0
Connector: N/A
Configuring MPLS L3VPN FRR through IPv4 route backup
for a VPNv4 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—PE 3 operates correctly, traffic from CE 1 to CE 2 goes through the path
CE 1—PE 1—PE 2—PE 3—CE 2.
•
When BFD detects that the link between PE 2 and PE 3 fails, traffic from CE 1 to CE 2 goes
through the path CE 1—PE 1—PE 2—CE 2.
Process ID: 0
Age: 01h54m24s
Preference: 10
QosLocalID: N/A
State: Active Adv
OrigVrf: vpn1
OrigAs: 300
LastAs: 300
Neighbor: 10.1.1.1
OrigNextHop: 10.1.1.1
RealNextHop: 10.1.1.1
BkNextHop: 172.3.1.3
Interface: Vlan-int13
BkInterface: Vlan-int15
TrafficIndex: N/A
267