Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Current »

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:

QFX5110-48S-4C , JUNOS 18.3R1.9
root@QFX5110-2# set interfaces ge-0/0/13 encapsulation ?
Possible completions:
  ethernet-bridge      Ethernet layer-2 bridging
  ethernet-ccc         Ethernet cross-connect
  extended-vlan-bridge  VLAN layer-2 bridging
  flexible-ethernet-services  Allows per-unit Ethernet encapsulation configuration
  vlan-ccc             802.1q tagging for a cross-connect
{master:0}[edit]



Model: ex9208 ,  Junos: 14.2R4.9

root@EX9208-1-RE1# set encapsulation ?
Possible completions:
  ethernet-bridge      Ethernet layer-2 bridging
  ethernet-vpls        Ethernet virtual private LAN service
  extended-vlan-bridge  VLAN layer-2 bridging
  extended-vlan-vpls   Extended VLAN virtual private LAN service
  flexible-ethernet-services  Allows per-unit Ethernet encapsulation configuration
  vlan-vpls            VLAN virtual private LAN service


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:

QFX5110-48S-4C , JUNOS 18.3R1.9
root@QFX5110-2# set interfaces ge-0/0/13.20 encapsulation ?
Possible completions:
  dix                  Ethernet DIXv2 (RFC 894)
  ppp-over-ether       PPPoE encapsulation
  vlan-bridge          VLAN layer-2 bridging
  vlan-ccc             802.1q tagging for a cross-connect
  vlan-vpls            VLAN virtual private LAN service

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.







  • No labels