translation-vni

Syntax

Hierarchy Level

Description

Configure a VXLAN network identifier (VNI) to which a Juniper Networks switch will translate a VNI in a packet that it is forwarding.

The device translates the VNI while it is forwarding traffic in the following seamless EVPN-VXLAN stitching use cases:

From one EVPN-VXLAN point of delivery (POD) to another within a data center.
From one EVPN-VXLAN data center to another. This use case is also known as data center interconnect (DCI).

In these use cases, a device that supports the seamless EVPN-VXLAN stitching feature can serve as either a spine or super spine device that interconnects the PODs or data centers through an EVPN-VXLAN WAN network.

Note:

When you configure a translation VNI for Layer 2 Data Center Interconnect (DCI) stitching on QFX5120 switches, you must also include the vxlan-trans-vni-enable setting (see that option here—evpn-vxlan), as follows:

The packet forwarding engine (PFE) restarts when you set or delete this configuration item, which causes the associated FPC and interfaces to restart.

When configuring the interconnection, you can set up a single routing instance of type virtual-switch or evpn on each spine or super spine device. Or, you can use the default switching instance.

The type of instance that you use determines the hierarchy level at which you must include the translation-vni configuration statement. Table 1 outlines the instance types and the hierarchy levels at which you must include translation-vni for each type.

Table 1: Interconnection Instance Types and Hierarchy Levels at Which to Include translation-vni Configuration Statement
Instance Types	Hierarchy Levels
Routing instance of type `virtual-switch`	`[edit routing-instances routing-instance-name vlans vlan-name vxlan]`
Routing instance of type `evpn`	`[edit routing-instances routing-instance-name vxlan]`
Default switching instance	`[edit vlans vlan-name vxlan]`

The Juniper Networks switch translates the VNI only if you have included the translated VNI in the interconnected VNI list. For information about configuring this list, see interconnected-vni-list.

To understand how VNI translation works, Data Centers 1 and 2 are interconnected through an EVPN-VXLAN WAN network. In this topology, Super Spine 1 connects Data Center 1 and the WAN network, and Super Spine 2 connects Data Center 2 and the WAN network.

A routing instance named evpn-vxlan is configured on both Super Spines 1 and 2. In this routing instance, VLAN 100 is configured on each super spine device. However, the VNI mapped to VLAN 100 is different on each super spine device.

Table 2 provides a summary of the VNI-related attributes configured on each super spine device.

Table 2: Summary of VNI-Related Configurations on Super Spines 1 and 2
VNI-Related Configurable Attributes	Super Spine 1 evpn-vxlan Routing Instance Configuration	Super Spine 2 evpn-vxlan Routing Instance Configuration
VLAN ID	100	100
VNI	100	300
Translated VNI	200	200
Interconnected VNI List	Includes VNI 200	Includes VNI 200

As shown in Table 2, Super Spine 1 maps VNI 100 to VLAN 100, and Super Spine 2 maps VNI 300 to VLAN 100. Both super spine devices include VNI 200 in their interconnected VNI lists. As a result, when the super spine devices forward VLAN 100 traffic to the WAN network, the VNI is translated to 200.

Options

vni

Numeric value that represents the VNI to which the VNI in a packet is translated.

Range: 1through 16777214

Required Privilege Level

admin—To view this statement in the configuration.

admin-control—To add this statement to the configuration.

Release Information

Statement introduced in Junos OS Release 20.3R1.

ON THIS PAGE