l2pt (Destination Tunnels)
Syntax
l2pt { interface name { destination { vxlan-tunnel; } enable-all-ifl; protocol { all; cdp; elmi; gvrp; ieee8021x; ieee8023ah; lacp; lldp; mmrp; mvrp; pvstp; stp; udld; vstp; vtp; } } }
Hierarchy Level
[edit protocols layer2-control]
Description
Enable Layer 2 (L2) protocol tunneling (L2PT) across the encapsulation tunnels in an EVPN network.
Use this statement to enable a device to receive protocol control frames coming in on an
access interface and tunnel those frames across the encapsulation tunnels on the device.
Configure this statement with the interface name
option (required) and each of the following (required):
The
destination tunnel-type
option.The
protocol
option for each bridge protocol data unit (BPDU) type you want the device to tunnel from the access interface across the encapsulation tunnels on the device. Or, specify theall
option to enable L2PT for all of the supported protocols.
When you enable L2PT over VXLAN for a supported protocol, the device transparently forwards the protocol control frames with that protocol destination MAC address. If you enable L2PT for a protocol that has the same destination MAC address as one or more other supported protocols, the device transparently forwards the control frames for all of those protocols.
Options
interface name |
(Required) Interface name on which to enable L2PT across a destination tunnel type on the device. The interface can be a physical interface or an aggregated Ethernet (AE) interface. |
destination tunnel-type |
(Required) Destination tunnel type over which to enable L2PT—you must specify one of the supported encapsulation tunnel types:
|
enable-all-ifl |
Enable L2PT for all the logical interfaces under the specified L2PT-enabled physical interface. This option is required on QFX5130 and QFX5700 switches to ensure any logical interfaces you configure on an L2PT-enabled physical interface end up with the same L2PT settings when you commit the configuration. |
protocol (all | protocol-name) |
(Required) Protocol for which to transparently tunnel control packets from the
specified interface across the destination tunnel type. Some of the available
protocol options might not be supported with all encapsulation tunnel types. We
support the protocol options listed below with the Note:
EX Series and QFX Series with Junos OS don't include the
If you don't want these devices to tunnel xSTP control BPDUs over VXLAN, you can configure the BPDU protection feature on the ingress access interface. See bpdu-block and bpdu-block-on-edge for details on the BPDU protection feature. Specify the
|
Required Privilege Level
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Release Information
Statement introduced in Junos OS Release 24.2R1.