vni (NVE interface view)

Function

The vni command configures a VXLAN network identifier (VNI) for an NVE interface.

The undo vni command deletes the VNI for an NVE interface, and deletes all configurations for the same VNI on the current NVE interface.

The vni head-end peer-list command configures an ingress replication list that contains the IP addresses of those remote VTEPs for a VXLAN network identifier (VNI).

The undo vni head-end peer-list command deletes the ingress replication list of a VNI.

By default, no VNI is configured for an NVE interface, no ingress replication list is configured for any VNI.

Format

vni vni-id [ head-end peer-list { ip-address } &<1-10> ]

undo vni vni-id [ head-end peer-list { ip-address } &<1-10> ]

Parameters

Parameter	Description	Value
vni-id	Specifies a VNI ID.	The value is an integer ranging from 1 to 16777215.
ip-address	Specifies the IP address of a remote VXLAN tunnel endpoint (VTEP).	The value is in dotted decimal notation.

Parameter

Description

Value

vni-id

Specifies a VNI ID.

The value is an integer ranging from 1 to 16777215.

ip-address

Specifies the IP address of a remote VXLAN tunnel endpoint (VTEP).

The value is in dotted decimal notation.

Views

NVE interface view

Default Level

2: Configuration level

Task Name and Operations

Task Name	Operations
nvo3	write

Usage Guidelines

Usage Scenario

VNIs are similar to VLAN IDs. VXLAN uses VNIs to differentiate VXLAN segments and identify tenants. A VNI identifies only one tenant. Even if multiple terminal users belong to the same VNI, they are considered one tenant. Run this command to configure a VNI for an NVE interface.

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.

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.

Even if a source VTEP connects only to one remote VTEP, you still need to run the vni head-end peer-list command to configure an ingress replication list with the remote VTEP's IP address specified.

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.

Example

# Configure an ingress replication list for VNI 5010, with the remote VTEPs' IP addresses being 2.2.2.2 and 3.3.3.3.

<HUAWEI> system-view
[~HUAWEI] interface nve 1
[*HUAWEI-Nve1] vni 5010 head-end peer-list 2.2.2.2 3.3.3.3

# Configures a VNI for an NVE interface.

<HUAWEI> system-view
[~HUAWEI] interface nve 1
[*HUAWEI-Nve1] vni 10