The vni head-end peer-list protocol bgp command configures a dynamic ingress replication list generated by the BGP protocol that contains the IP addresses of those remote VTEPs for a VXLAN network identifier (VNI).
The undo vni head-end peer-list protocol bgp command cancels the configuration.
By default, no ingress replication list is configured for any VNI.
Usage Scenario
After the ingress of a VXLAN tunnel receives broadcast, unknown unicast, and multicast (BUM) packets, it replicates these packets and sends a copy to each VTEP in the ingress replication list. The ingress replication list is a collection of remote VTEP IP addresses to which the ingress of a VXLAN tunnel should send replicated BUM packets.
If a source VTEP on a VXLAN connects to multiple remote VTEPs on the same VXLAN segment, run the vni head-end peer-list command to configure an ingress replication list that contains the IP addresses of those remote VTEPs. After the source NVE receives BUM packets, the local VTEP sends a copy of the BUM packets to every VTEP in the list. To use BGP to dynamically establish Layer 2 VXLAN tunnels, run the vni head-end peer-list protocol bgp command.Configuration Impact
Ingress replication allows BUM packets to be transmitted in broadcast mode, independent of multicast routing protocols.
Precautions
If other configurations are performed for the same VNI on the current NVE interface, the command configuration will be overwritten.
BUM packet forwarding is implemented only using ingress replication. To establish a VXLAN tunnel between a Huawei device and a non-Huawei device, ensure that the non-Huawei device also has ingress replication configured. Otherwise, communication fails.