219
Step Command
Remarks
This step is required to enable
MPLS L3VPN FRR in Method 2.
For more information about this
command, see
Layer 3—IP
Routing Command Reference
.
7.
Return to system view.
quit
N/A
8.
Enter BGP instance view.
bgp
as-number
[
instance
instance-name
]
[
multi-session-thread
]
N/A
9.
(Optional.) Use
echo-mode BFD to detect
the connectivity to the
next hop of the primary
route.
primary-path-detect bfd echo
By default, ARP is used to detect
the connectivity to the next hop.
Use this command if necessary in
VPNv4 route backup an IPv4 route.
For more information about this
command, see
Layer 3—IP
Routing Command Reference
.
10.
Enter BGP-VPN instance
view.
ip
vpn-instance
vpn-instance-name
N/A
11.
Enter BGP-VPN IPv4
unicast address family
view.
address-family
ipv4
[
unicast
]
N/A
12.
Enable MPLS L3VPN
FRR.
•
(Method 1) Enable MPLS
L3VPN FRR for the address
family:
pic
•
(Method 2) Use a routing policy
to specify a backup next hop for
the address family:
fast-reroute route-policy
route-policy-name
By default, MPLS L3VPN FRR is
disabled.
Method 1 might result in routing
loops. Use it with caution.
By default, no routing policy is
used.
The
apply fast-reroute
backup-nexthop
command can
take effect in the routing policy that
is being used. Other
apply
commands do not take effect.
For more information about the
command, see
Layer 3—IP
Routing Command Reference
.
99B
Enabling SNMP notifications for MPLS L3VPN
To report critical MPLS L3VPN events to an NMS, enable SNMP notifications for MPLS L3VPN. For
MPLS L3VPN event notifications to be sent correctly, you must also configure SNMP on the device.
For more information about SNMP configuration, see the network management and monitoring
configuration guide for the device.
To enable SNMP notifications for MPLS L3VPN:
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enable SNMP notifications
for MPLS L3VPN.
snmp-agent trap enable l3vpn
By default, SNMP notifications for
MPLS L3VPN are enabled.