Image Removed

...

Image Added

Encapsulation (Physical Interface)

https://www.juniper.net/documentation/en_US/junos12.3/topics/reference/configuration-statement/encapsulation-edit-interfaces-physical.html

Description

Specify the physical link-layer encapsulation type. ( Accept 802.1q or dot1q frame at the Physical interface level )

Interface level:

ethernet-bridge—Use Ethernet bridge encapsulation on Ethernet interfaces that have bridging enabled and that must accept all packets.

ethernet-ccc—Use Ethernet CCC encapsulation on Ethernet interfaces that must accept packets carrying standard Tag Protocol ID (TPID) values.

vlan-ccc—Use VLAN CCC encapsulation on Ethernet interfaces with VLAN tagging enabled. VLAN CCC encapsulation supports TPID 0x8100 only. You must configure this encapsulation type on both the physical interface and the logical interface.

extended-vlan-bridge—Use extended VLAN bridge encapsulation on Ethernet interfaces that have IEEE 802.1Q VLAN tagging and bridging enabled and that must accept packets carrying TPID 0x8100 or a user-defined TPID.

flexible-ethernet-services Allows per-unit Ethernet encapsulation configuration

encapsulation (Logical Interface)

https://www.juniper.net/documentation/en_US/junos/topics/reference/configuration-statement/encapsulation-edit-interfaces-logical.html

Unit level:

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.