199
462B
IPv4 route backup for a VPNv4 route
Figure 65 Network diagram
As shown in
784H
Figure 65
, configure FRR on the egress node PE 2, and specify the backup next hop for
VPN 1 as CE 2. When PE 2 receives an IPv4 route from CE 2 and a VPNv4 route from PE 3 (both
routes are destined for VPN 1 connected to CE 2), PE 2 uses the VPNv4 route as the primary link,
and the IPv4 route as the backup link.
Configure BFD for LSPs or MPLS TE tunnels on PE 2 to detect the connectivity of the public tunnel
from PE 2 to PE 3. When the tunnel operates correctly, traffic from CE 1 to CE 2 goes through the
path CE 1—PE 1—PE 2—PE 3—CE 2. When the tunnel fails, the traffic goes through the path CE
1—PE 1—PE 2—CE 2.
In this scenario, PE 2 is responsible for primary link detection and traffic switchover.
233B
Protocols and standards
•
RFC 3107,
Carrying Label Information in BGP-4
•
RFC 4360,
BGP Extended Communities Attribute
•
RFC 4364,
BGP/MPLS IP Virtual Private Networks (VPNs)
•
RFC 4577,
OSPF as the Provider/Customer Edge Protocol for BGP/MPLS IP Virtual Private
Networks (VPNs)
90B
MPLS L3VPN configuration task list
Tasks at a glance
(Required.)
785H
Configuring basic MPLS L3VPN
(Optional.)
786H
Configuring inter-AS VPN
(Optional.)
787H
Configuring nested VPN
(Optional.)
788H
Configuring HoVPN
(Optional.)
789H
Configuring an OSPF sham link
(Optional.)
790H
Specifying the VPN label processing mode on the egress PE
(Optional.)
791H
Configuring BGP AS number substitution and SoO attribute
(Optional.)
792H
Configuring MPLS L3VPN FRR
(Optional.)
793H
Enabling SNMP notifications for MPLS L3VPN