This section provides several configuration examples of
BGP/MPLS IPv6 VPN. In each configuration example, the networking requirements,
configuration notes, configuration roadmap, configuration procedures,
and configuration files are provided.
In the networking of Hub and Spoke, an access control device is specified in the VPN, and users communicate with each other through the access control device.
If the AS numbers of different sites in a VPN are the same and EBGP peer relationships are set up between PEs and CEs, AS number substitution needs to be enabled on PEs. Otherwise, CEs will discard the VPN routes that carry the same AS information as their local AS information. As a result, users of the same VPN cannot communicate with each other.
If there are multiple routes from a PE to a remote or local site (2001:db8:12::2), configuring load balancing among IPv6 VPN routes can fully utilize network resources and improve network reliability.
If there are multiple tunnels between PEs on the backbone network, configuring load balancing among tunnels can fully utilize network resources and enhance the reliability of VPN services on the backbone network.
If no MP-IBGP peer relationship is established between PEs and ASBRs, you can use LDP to allocate labels for BGP and implement the inter-AS IPv6 VPN Option C solution.
This section provides an example showing how a Level 2 carrier provides BGP/MPLS IPv6 VPN services when the Level 2 carrier and the Level 1 carrier are in the same AS.
This section provides an example showing how a Level 2 carrier provides BGP/MPLS IPv6 VPN services when the Level 2 carrier and the Level 1 carrier are in different ASs.
Open Shortest Path First (OSPF) multi-VPN-instance can be configured on a customer edge (CE) to isolate different types of services on a local area network (LAN).
This section describes how to configure VPNv6 FRR in the CE dual-homing networking. If a PE fails, VPNv6 FRR can quickly switch IPv6 VPN traffic to the backup route.
Private network IPv6 FRR can be deployed if multiple CEs at an IPv6 VPN site access the same PE. If a route from the PE to a CE is unreachable, this feature quickly switches traffic to a link from the PE to another CE.
If a CE is dual-homed to two PEs, IPv6+VPNv6 hybrid FRR can be configured on PEs to protect the route between either PE and the CE. If the route between either PE and the CE fails, traffic destined for the CE can be switched to the other PE.
If a large number of MP-IBGP peer relationships need to be set up between PEs on the backbone network, configuring an RR can reduce required MP-IBGP peer relationships and workload on PEs.
This section provides an example for configuring basic VPN dual-stack access. After both IPv4 and IPv6 address families are configured in VPN instances, the interfaces bound to the VPN instances can support not only IPv4 VPN access but also IPv6 VPN access. This implementation greatly improves the feasibility of the transition from IPv4 to IPv6.