Configuring a VLAN-Bundled Logical Interface to Support a Layer 2 Circuit
To configure a VLAN-bundled logical interface,
specify the list of VLAN IDs by including the vlan-id-list statement or the vlan-tags statement:
interfaces {
ethernet-interface-name {
vlan-tagging; # Support single- or dual-tag logical interfaces
flexible-vlan-tagging; # Support mixed tagging
encapsulation (extended-vlan-ccc | flexible-ethernet-services);
unit logical-unit-number {
encapsulation vlan–ccc; # Required for single-tag
vlan-id-list [vlan-id vlan-id–vlan-id]; # For single-tag
vlan-id-range vlan-id-range; # For single-tag with outer VLAN as a range of VLANs
vlan-tags outer tpid.vlan-id inner-list [vlan-id vlan-id–vlan-id]; # For dual-tag
vlan-tags outer vlan-id inner-range vlan-id-range # For dual-tag with outer VLAN and inner VLAN as a range of VLANs
}
. . .
}
}
You can include the statements at the following hierarchy levels:
[edit][edit logical-systems logical-system-name]
For a single-tag logical interface, include the encapsulation statement and specify vlan-ccc so that CCC circuit encapsulation
is used inside the Layer 2 circuit.
For platforms that support vlan-id-range configurations, you can
configure ranges in two ways:
-
Single VLAN tagged: the outer tag is a VLAN range.
-
Dual VLAN tagged: the outer tag is a single VLAN ID, and the inner tag is configured as a VLAN range.
In the case of a dual-tag logical interface, the Junos
OS automatically uses the vlan-ccc encapsulation type.