Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Configuring VLAN and Extended VLAN Encapsulation

 

To configure encapsulation on an interface, enter the encapsulation statement at the [edit interfaces interface-name] hierarchy level:

The following list contains important notes regarding VLAN encapsulation:

  • Starting with Junos OS Release 8.1, , Gigabit Ethernet IQ, Gigabit Ethernet PICs with small form-factor pluggable optics (SFPs), and MX Series router Gigabit Ethernet, Tri-Rate Ethernet copper, and 10-Gigabit Ethernet interfaces with VLAN tagging enabled can use flexible-ethernet-services, vlan-ccc , or vlan-vpls encapsulation.

  • Starting with Junos OS Release 9.5, aggregated Ethernet interfaces configured for VPLS can use flexible-ethernet-services, vlan-ccc, or vlan-vpls.

  • Ethernet interfaces in VLAN mode can have multiple logical interfaces. In CCC and VPLS modes, VLAN IDs from 1 through 511 are reserved for normal VLANs, and VLAN IDs 512 through 4094 are reserved for CCC or VPLS VLANs. For 4-port Fast Ethernet interfaces, you can use VLAN IDs 512 through 1024 for CCC or VPLS VLANs. For encapsulation type flexible-ethernet-services, all VLAN IDs are valid.

  • For flexible Ethernet services, Ethernet VLAN CCC and VLAN VPLS, you can also configure the encapsulation type that is used inside the VLAN circuit itself. To do this, include the encapsulation statement at the [edit interfaces interface-name unit logical-unit-number] hierarchy level or at the [edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number] hierarchy level.

  • You cannot configure a logical interface with VLAN CCC or VLAN VPLS encapsulation unless you also configure the physical device with the same encapsulation or with flexible Ethernet services encapsulation. In general, the logical interface must have a VLAN ID of 512 or higher; if the VLAN ID is 511 or lower, it will be subject to the normal destination filter lookups in addition to source address filtering. However if you configure flexible Ethernet services encapsulation, this VLAN ID restriction is removed.

  • Gigabit Ethernet, 4-port Fast Ethernet, MX Series router Gigabit Ethernet, Tri-Rate Ethernet copper, 10-Gigabit Ethernet, and aggregated Ethernet interfaces with VLAN tagging enabled can use extended-vlan-ccc or extended-vlan-vpls, which allow 802.1Q tagging.

  • For extended VLAN CCC and extended VLAN VPLS encapsulation, all VLAN IDs 1 and higher are valid. VLAN ID 0 is reserved for tagging the priority of frames.

  • For extended VLAN CCC, the VLAN IDs on ingress and egress interfaces must be the same. For back-to-back connections, all VLAN IDs must be the same.

Release History Table
Release
Description
Starting with Junos OS Release 9.5, aggregated Ethernet interfaces configured for VPLS can use flexible-ethernet-services, vlan-ccc, or vlan-vpls.
Starting with Junos OS Release 8.1, , Gigabit Ethernet IQ, Gigabit Ethernet PICs with small form-factor pluggable optics (SFPs), and MX Series router Gigabit Ethernet, Tri-Rate Ethernet copper, and 10-Gigabit Ethernet interfaces with VLAN tagging enabled can use flexible-ethernet-services, vlan-ccc , or vlan-vpls encapsulation.