static-remote-vtep-list

Syntax

Hierarchy Level

Description

Statically configure a list of one or more remote virtual tunnel endpoints (VTEPs) on an Layer 2 (L2) VXLAN gateway device, and map the list to a particular bridge domain or VLAN.

You can configure a static VXLAN configuration at the VLAN level or bridge domain level as follows:

• In the default switch instance, supported on:

  • MX Series routers—Bridge domain and VLAN levels.

  • QFX Series switches—VLAN level.

• In a configured virtual-switch L2 routing instance, supported on:

  • MX Series routers—Bridge domain and VLAN levels.

  • The PTX10000 line of routers (running Junos OS Evolved)—VLAN level.

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 use the remote-vtep-list statement to 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 use the remote-vtep-list statement to 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.

  Note:

  If you configure a global list of VTEPs in a routing instance using the remote-vtep-list statement, but you don't also configure the static-remote-vtep-list statement for a VLAN in the routing instance, then that VLAN inherits all the globally configured remote VTEPs.

  Also, on platforms that support EVPN with VXLAN encapsulation, you can have EVPN-VXLAN and static VXLAN configurations on the same device, as long as the two configurations use different sets of remote peer VTEPs.

• 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.

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

Sample Configuration 2 From QFX5XXX Switch (Default Switching Instance)

Options

Required Privilege Level

routing

Release Information

Statement introduced in Junos OS Release 20.4R1.