encapsulation (Logical Interface)
Syntax
encapsulation (atm-ccc-cell-relay | atm-ccc-vc-mux | atm-cisco-nlpid | atm-mlppp-llc | atm-nlpid | atm-ppp-llc | atm-ppp-vc-mux | atm-snap | atm-tcc-snap | atm-tcc-vc-mux | atm-vc-mux | ether-over-atm-llc | ether-vpls-over-atm-llc | ether-vpls-over-fr | ether-vpls-over-ppp | ethernet | ethernet-ccc | ethernet-vpls | ethernet-vpls-fr | frame-relay-ccc | frame-relay-ether-type | frame-relay-ether-type-tcc | frame-relay-ppp | frame-relay-tcc | gre-fragmentation | multilink-frame-relay-end-to-end | multilink-ppp | ppp-over-ether | ppp-over-ether-over-atm-llc | vlan-bridge | vlan-ccc | vlan-vci-ccc | vlan-tcc | vlan-vpls | vxlan);
Hierarchy Level
[edit interfaces interface-name unit logical-unit-number], [edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number], [edit interfaces rlsq number unit logical-unit-number] [edit protocols evpn]
Description
Configure a logical link-layer encapsulation type. Not all encapsulation types are supported on the switches. See the switch CLI.
Starting in Junos OS Release 20.1R1, aggregated ethernet interfaces supports VLAN TCC (Translational cross-connect) encapsulation on MX series platforms. See Configuring VLAN TCC Encapsulation for more details. Non-ethernet media types, SONET and ATM interfaces are only supported. It is expected that the user will have the member links of aggregated ethernet with supported hardware for configuring VLAN TCC encapsulation and no commit check is performed externally for the aggregated ethernet (AE) interfaces.
Options
atm-ccc-cell-relay
—Use ATM
cell-relay encapsulation.
atm-ccc-vc-mux
—Use ATM virtual circuit (VC)
multiplex encapsulation on CCC circuits. When you use this encapsulation
type, you can configure the ccc
family only.
atm-cisco-nlpid
—Use Cisco ATM network layer
protocol identifier (NLPID) encapsulation. When you use this encapsulation
type, you can configure the inet
family only.
atm-mlppp-llc
—For ATM2 IQ interfaces only,
use Multilink Point-to-Point (MLPPP) over AAL5 LLC. For this encapsulation
type, your router must be equipped with a Link Services or Voice Services
PIC. MLPPP over ATM encapsulation is not supported on ATM2 IQ OC48
interfaces.
atm-nlpid
—Use ATM NLPID encapsulation. When
you use this encapsulation type, you can configure the inet
family only.
atm-ppp-llc
—(ATM2 IQ interfaces and MX Series
routers with MPC/MIC interfaces using the ATM MIC with SFP only) Use
PPP over AAL5 LLC encapsulation.
atm-ppp-vc-mux
—(ATM2 IQ interfaces and MX Series
routers with MPC/MIC interfaces using the ATM MIC with SFP only) Use
PPP over ATM AAL5 multiplex encapsulation.
atm-snap
—(All interfaces including MX Series
routers with MPC/MIC interfaces using the ATM MIC with SFP) Use ATM
subnetwork attachment point (SNAP) encapsulation.
atm-tcc-snap
—Use ATM SNAP encapsulation on
translational cross-connect (TCC) circuits.
atm-tcc-vc-mux
—Use ATM VC multiplex encapsulation
on TCC circuits. When you use this encapsulation type, you can configure
the tcc
family only.
atm-vc-mux
—(All interfaces including MX Series
routers with MPC/MIC interfaces using the ATM MIC with SFP) Use ATM
VC multiplex encapsulation. When you use this encapsulation type,
you can configure the inet
family only.
ether-over-atm-llc
—(All IP interfaces including
MX Series routers with MPC/MIC interfaces using the ATM MIC with SFP)
For interfaces that carry IP traffic, use Ethernet over ATM LLC encapsulation.
When you use this encapsulation type, you cannot configure multipoint
interfaces.
ether-vpls-over-atm-llc
—For ATM2 IQ interfaces
only, use the Ethernet virtual private LAN service (VPLS) over ATM
LLC encapsulation to bridge Ethernet interfaces and ATM interfaces
over a VPLS routing instance (as described in RFC 2684, Multiprotocol Encapsulation over ATM Adaptation Layer 5). Packets from the ATM interfaces are converted to standard ENET2/802.3
encapsulated Ethernet frames with the frame check sequence (FCS) field
removed.
ether-vpls-over-fr
—For E1, T1, E3, T3, and
SONET interfaces only, use the Ethernet virtual private LAN service
(VPLS) over Frame Relay encapsulation to support Bridged Ethernet
over Frame Relay encapsulated TDM interfaces for VPLS applications,
per RFC 2427, Multiprotocol Interconnect over Frame Relay.
The SONET/SDH OC3/STM1 (Multi-Rate) MIC with SFP, the Channelized SONET/SDH OC3/STM1 (Multi-Rate) MIC with SFP, and the DS3/E3 MIC do not support Ethernet over Frame Relay encapsulation.
ether-vpls-over-ppp
—For E1, T1, E3, T3, and
SONET interfaces only, use the Ethernet virtual private LAN service
(VPLS) over Point-to-Point Protocol (PPP) encapsulation to support
Bridged Ethernet over PPP-encapsulated TDM interfaces for VPLS applications.
ethernet
—Use Ethernet II encapsulation (as
described in RFC 894, A Standard for the Transmission of
IP Datagrams over Ethernet Networks).
ethernet-ccc
—Use Ethernet CCC encapsulation
on Ethernet interfaces.
ethernet-vpls
—Use Ethernet VPLS encapsulation
on Ethernet interfaces that have VPLS enabled and that must accept
packets carrying standard Tag Protocol ID (TPID) values.
The built-in Gigabit Ethernet PIC on an M7i router does not support extended VLAN VPLS encapsulation.
ethernet-vpls-fr
—Use in a VPLS setup when a
CE device is connected to a PE router over a time-division multiplexing
(TDM) link. This encapsulation type enables the PE router to terminate
the outer layer 2 Frame Relay connection, use the 802.1p bits inside the inner Ethernet header to classify the packets, look
at the MAC address from the Ethernet header, and use the MAC address
to forward the packet into a given VPLS instance.
frame-relay-ccc
—Use Frame Relay encapsulation
on CCC circuits. When you use this encapsulation type, you can configure
the ccc
family only.
frame-relay-ether-type
—Use Frame Relay ether
type encapsulation for compatibility with Cisco Frame Relay. The physical
interface must be configured with flexible-frame-relay encapsulation.
frame-relay-ether-type-tcc
—Use Frame Relay
ether type TCC for Cisco-compatible Frame Relay on TCC circuits to
connect different media. The physical interface must be configured
with flexible-frame-relay encapsulation.
frame-relay-ppp
—Use PPP over Frame Relay circuits.
When you use this encapsulation type, you can configure the ppp
family only.
frame-relay-tcc
—Use Frame Relay encapsulation
on TCC circuits for connecting different media. When you use this
encapsulation type, you can configure the tcc
family only.
gre-fragmentation
—For adaptive services interfaces
only, use GRE fragmentation encapsulation to enable fragmentation
of IPv4 packets in GRE tunnels. This encapsulation clears the do not
fragment (DF) bit in the packet header. If the packet’ s size
exceeds the tunnel’ s maximum transmission unit (MTU) value,
the packet is fragmented before encapsulation.
multilink-frame-relay-end-to-end
—Use MLFR FRF.15
encapsulation. This encapsulation is used only on multilink, link
services, and voice services interfaces and their constituent T1 or
E1 interfaces, and is supported on LSQ and redundant LSQ interfaces.
multilink-ppp
—Use MLPPP encapsulation. This
encapsulation is used only on multilink, link services, and voice
services interfaces and their constituent T1 or E1 interfaces.
ppp-over-ether
—Use PPP over Ethernet encapsulation
to configure an underlying Ethernet interface for a dynamic PPPoE
logical interface on M120 and M320 routers with Intelligent Queuing
2 (IQ2) PICs, and on MX Series routers with MPCs.
ppp-over-ether-over-atm-llc
—(MX Series routers
with MPCs using the ATM MIC with SFP only) For underlying ATM interfaces,
use PPP over Ethernet over ATM LLC encapsulation. When you use this
encapsulation type, you cannot configure the interface address. Instead,
configure the interface address on the PPP interface.
vlan-bridge
—Use Ethernet VLAN bridge encapsulation
on Ethernet interfaces that have IEEE 802.1Q tagging, flexible-ethernet-services, and bridging enabled and that
must accept packets carrying TPID 0x8100 or a user-defined TPID.
vlan-ccc
—Use Ethernet virtual LAN (VLAN) encapsulation
on CCC circuits. When you use this encapsulation type, you can configure
the ccc
family only.
vlan-vci-ccc
—Use ATM-to-Ethernet interworking
encapsulation on CCC circuits. When you use this encapsulation type,
you can configure the ccc
family only.
vlan-tcc
—Use Ethernet VLAN encapsulation on
TCC circuits. When you use this encapsulation type, you can configure
the tcc
family only.
vlan-vpls
—Use Ethernet VLAN encapsulation on
VPLS circuits.
vxlan
—Use VXLAN data plane encapsulation for
EVPN.
Required Privilege Level
interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration.
Release Information
Statement introduced before Junos OS Release 7.4.
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to determine if a feature is supported on your platform.