174
IPv4 route backup for a VPNv4 route
Figure 61 Network diagram
As shown in
, 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.
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)
MPLS L3VPN configuration task list
Tasks at a glance
Specifying the VPN label processing mode on the egress PE
Configuring BGP AS number substitution
Enabling SNMP notifications for MPLS L3VPN
CE 2
CE 1
VPN 1
VPN 1
MPLS
backbone
PE 2
PE 1
PE 3
Primary link
Backup link
Содержание FlexNetwork 5510 HI Series
Страница 9: ...vii Remote support 460 Documentation feedback 460 Index 462 ...
Страница 318: ...309 Request list 0 Retransmit list 0 ...
Страница 363: ...354 Verify that CE 1 and CE 2 can ping each other Details not shown ...
Страница 446: ...437 The MCE has redistributed the OSPF routes of the two VPN instances into the EBGP routing tables of PE 1 ...