vlan-tags (Dual-Tagged Logical Interface)
Syntax
vlan-tags inner-list [vlan-id vlan-id–vlan-id ] outer <tpid.>vlan-id;
Hierarchy Level
[edit interfaces interface-name unit logical-unit-number], [edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]
Description
(MX Series routers only) Binds a dual-tag logical interface to a list of VLAN IDs. Configures the logical interface to receive and forward any dual-tag frame whose inner VLAN ID tag matches the list of VLAN IDs you specify.
To create a circuit cross-connect (CCC) using VLAN-bundled
dual-tag logical interfaces on Layer 2 VPN routing instances, you
must include the encapsulation-type statement and specify
the value ethernet-vlan at the one of the following hierarchy
levels:
[edit routing-instances routing-instance-name protocols l2vpn][edit logical-systems logical-system-name routing-instances routing-instance-name protocols l2vpn]
For more information about the encapsulation-type configuration statement and the Layer 2 encapsulation types ethernet and ethernet-vlan, see the Junos OS VPNs Library for Routing Devices.
Options
inner-list [vlan-id vlan-id vlan-id-vlan-id]—A list of valid VLAN ID numbers.
Specify the VLAN IDs individually by using a space to separate each
ID, as an inclusive list by separating the starting VLAN ID and ending
VLAN ID with a hyphen, or as a combination of both.
Range: 1 through 4094. VLAN ID 0 is reserved for tagging the priority of frames.
outer <tpid.>vlan-id—An optional Tag Protocol ID (TPID) and a valid VLAN
ID.
Range: For TPID, specify a hexadecimal value in the format
0xnnnn.
Range: For VLAN ID, 1 through 4094. VLAN ID 0 is reserved for tagging the priority of frames.
Configuring inner-list with the entire vlan-id
range is an unnecessary waste of system resources and is not best
practice. It should be used only when a subset of VLAN IDs of inner
tag (not the entire range) needs to be associated with a logical interface.
If you specify the entire range (1 through 4094), it has the same
result as not specifying a range; however, it consumes PFE resources
such as VLAN lookup tables entries, and so on.
The following examples illustrate this further:
Inefficient
[edit interfaces interface-name] vlan-tagging; unit number { vlan-tags outer vid inner-list 1-4094; }Best Practice
[edit interfaces interface-name] vlan-tagging; unit number { vlan-id vid; }
Required Privilege Level
interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration.
Release Information
Statement introduced in Junos OS Release 9.5.