Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

vlan-tags (Stacked VLAN Tags)

Syntax

Hierarchy Level

Description

Bind TPIDs and 802.1Q VLAN tag IDs to a logical interface. TPID fields are used to identify the frame as an IEEE 802.1Q-tagged frame.

Options

inner tpid.vlan-id

A TPID and a valid VLAN identifier. TPID is a 16-bit field set to a value of 0x8100 in order to identify the frame as an IEEE 802.1Q-tagged frame.

  • Range: (most routers) For VLAN ID, 1 through 4094. VLAN ID 0 is reserved for tagging the priority of frames. For PTX Series, VLAN ID 0 is not supported.
inner-list value

List or a set of VLAN identifiers. You can configure a maximum of 32 inner-lists for an interface.
Note:

This is supported on MX Series routers with Trio-based FPCs.
inner-range tpid. vid1–vid2

Specify a TPID and a range of VLAN IDs where vid1 is the start of the range and vid2 is the end of the range.

Note:

On the network-to-network (NNI) or egress interfaces of provider edge (PE) routers, you cannot configure the inner-range tpid. vid1—vid2 option with the vlan-tags statement for ISP-facing interfaces.

  • Range: For VLAN ID, 1 through 4094. VLAN ID 0 is reserved for tagging the priority of frames.

outer tpid.vlan-id

A TPID and a valid VLAN identifier.

  • Range: (most routers) For VLAN ID, 1 through 511 for normal interfaces, and 512 through 4094 for VLAN CCC interfaces. VLAN ID 0 is reserved for tagging the priority of frames. For PTX Series, VLAN ID 0 is not supported.

Note:

Configuring inner-range with the entire vlan-id range consumes system resources and is not a best practice. The inner-range must 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 Packet Forwarding Engine resources such as VLAN lookup table entries, and so on.

The following examples illustrate this further:

  1. Inefficient

  2. Best Practice
Note:

Configuring inner-range with the entire vlan-id range consumes system resources and is not a best practice. The inner-range must 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 Packet Forwarding Engine resources such as VLAN lookup table entries, and so on.

The following examples illustrate this further:

  1. Inefficient

  2. Best Practice

Required Privilege Level

interface—To view this statement in the configuration.

interface-control—To add this statement to the configuration.

Release Information

Statement introduced before Junos OS Release 7.4.

Related Documentation