advertise route-reoriginate (BGP-VPN instance IPv6 address family view)

Usage Scenario

In an HVPN scenario, UPEs communicate with each other through SPEs and NPEs. If there are a large number of UPEs, the one-label-per-instance mode is configured for VPN instances, and the one-label-per-next-hop mode is configured for the VPNv6 address family on the SPE, the UPEs will receive a large number of labels. If the UPE has a small resource capacity, traffic may be incorrectly forwarded.

To address this problem, you can configure an SPE to leak the received VPNv6 routes into a VPN instance, which regenerates these routes and advertises them to the VPNv6 address family. Then, you can configure the one-label-per-instance mode for the VPN instance, when the re-originated VPNv6 routes are advertised to UPEs, each instance is assigned a label. This reduces the number of VPN labels of VPNv6 routes. To enable a VPN instance to advertise regenerated routes to the VPNv6 address family, run the advertise route-reoriginate command on an SPE. The regenerated routes carry the RD configured for the VPN instance, and the RT of the VPN instance is added to the original routes.

Follow-up Procedure

To enable a device to advertise routes regenerated in the VPNv6 address family to a BGP VPNv6 peer, run the peer advertise route-reoriginated vpnv6 command.

Precautions

If best-route or valid-route is not specified, all routes in the BGP VPN routing table are advertised to the VPN instance and then regenerated.