Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

static-remote-vtep-list

Syntax

Hierarchy Level

Description

Statically configure a list of one or more remote virtual tunnel endpoints (VTEPs), and map the list to a particular bridge domain or VLAN.

Note:

If you have previously configured EVPN-VXLAN on a device, then later configure static VXLAN, you must reboot the device to let static VXLAN take effect.

When configuring a static remote VTEP list, keep the following in mind:

  • When specifying remote VTEPs at the bridge domain level in a routing instance, you must also specify the same VTEPs at the global level in the same routing instance. When specifying remote VTEPs at the VLAN level in the default switching instance, you must also specify the same VTEPs at the global level in the default switching instance. To illustrate this point, note the following in sample configurations 1 and 2:

    • Routing instance rt1 and the default switching instance include the VTEPs with the loopback addresses of 10.1.1.1 and 10.1.1.2.

    • Bridge domain bd1 and VLAN-1 include the VTEPs with the loopback addresses of 10.1.1.1 and 10.1.1.2.

    • Bridge domain bd2 and VLAN-2 include the VTEP with the loopback address of 10.1.1.1.

    • Bridge domain bd3 and VLAN-3 don’t include a static remote VTEP list. As a result, bd3 and VLAN-3 inherit all VTEPs specified in routing instance rt1 and the default switching instance (the VTEPs with the loopback addresses of 10.1.1.1 and 10.1.1.2), respectively.

  • To replicate and flood broadcast, unknown unicast, and multicast (BUM) traffic, you must specify the ingress-node-replication configuration statement at the [edit vlans name vxlan], [edit bridge-domains name vxlan], or [edit routing-instances name bridge-domains name vxlan] hierarchy level. In sample configuration 1, ingress-node-replication is configured for all bridge domains in routing instance rt1. In sample configuration 2, ingress-node-replication is configured for all VLANs in the default switching instance.

    Note that this ingress node replication configuration restricts the BUM traffic flood domain to only those VTEPs mapped to a particular bridge domain or VLAN. For example, for sample configurations 1 and 2, the BUM traffic flood domain is restricted as described for each bridge domain and VLAN, respectively:

    • bd1 and bd3; VLAN-1 and VLAN-3—BUM traffic is flooded to the VTEPs with the loopback addresses of 10.1.1.1 and 10.1.1.2.

    • bd2; VLAN-2—BUM traffic is flooded to the VTEP with the loopback address of 10.1.1.1.

Note:

To ensure that BUM traffic is flooded to only those VTEPs mapped to a particular VLAN, we strongly recommend that the static VTEP lists on all QFX5XXX switches are symmetric. We provide this guidance to avoid a situation where, for example, switch 1’s list includes switches 2 and 3, switch 2’s list includes switches 1 and 3, and switch 3’s list includes only switch 2. Because of this asymmetric configuration, when switch 1 sends BUM traffic to switch 3, switch 3 will forward the traffic even though switch 1 is not on its list.

Sample Configuration 1 From MX Router (Routing Instance of Type virtual-switch)

Sample Configuration 2 From QFX5XXX Switch (Default Switching Instance)

Options

static-remote-vtep-list

Specify the loopback address of one or more remote VTEPs in square brackets ([]). You do not need to include a delimiter such as a comma between names.

Required Privilege Level

routing

Release Information

Statement introduced in Junos OS Release 20.4R1.