The device supports L3VPN service activation by device or interface. If L3VPN service resources have been purchased based on the number of ports in the current project, you must allocate these resources to specified ports.
A basic BGP/MPLS IPv6 VPN includes PEs, Ps, and CEs with the Ps residing in a single MPLS domain on the backbone network of one carrier. Each device plays only one role, either PE, CE, or P. After a basic BGP/MPLS IPv6 VPN is configured, the network can provide IPv6 VPN services for customers.
Using a BGP VPNv6 RR can reduce the number of MP-IBGP connections between PEs. The RR not only reduces the burden on PEs, but also facilitates network maintenance and management.
In the hub-spoke networking, an access control device is specified in the VPN, and users communicate with each other through the access control device.
After LDP LSPs are established for the labeled BGP routes of the public network, EBGP connections in multi-hop mode are established between PEs of different ASs to exchange VPNv6 routes.
Multi-VPN-instance can be configured for routing protocols on a customer edge (CE) to isolate different types of services on a local area network (LAN).
IPv6 route import between VPN and public network instances enables IPv6 VPN users to communicate with IPv6 public network users, whereas IPv6 route import between VPN instances enables IPv6 users in different VPNs to communicate.
This section describes how to configure private network IPv6 FRR in the networking where multiple CEs at an IPv6 VPN site access the same PE. This feature can quickly switch traffic to a link connected to another CE if the primary route from a PE to a CE becomes unreachable.
This section describes how to configure IPv6+VPNv6 hybrid FRR in the CE dual-homing networking. If the next hop from a PE to a CE is unreachable, IPv6+VPNv6 hybrid FRR can send traffic to the other PE over a tunnel, and the traffic will be routed to the CE through IP forwarding on the private network. This improves network reliability.
In the process of master/slave control board switchover or the system upgrade, you can configure VPN Graceful Restart (GR) Helper to ensure that VPN traffic is not interrupted on the PE, CE, or P. The NetEngine 8000 F supports only the GR Helper.
After IPv6 route recursion to remotely leaked VPN routes is enabled, the labels and Tunnel IDs of the remotely leaked VPN routes can be inherited, which ensures correct traffic forwarding.
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.