Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

TechLibrary
Navigation

vlan-id-list (Ethernet VLAN Circuit)

Syntax

vlan-id-list [ vlan-id vlan-id–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]

Release Information

Statement introduced in Junos OS Release 9.5.

Statement introduced in Junos OS Release 13.2X50-D15 for EX Series switches.

Statement introduced in Junos OS Release 13.2 for the QFX series.

Description

Binds a single-tag logical interface to a list of VLAN IDs. Configures a logical interface to receive and forward any tag frame whose VLAN ID tag matches the list of VLAN IDs you specify.

When you create a circuit cross-connect (CCC) using VLAN-bundled single-tag logical interfaces on Layer 2 VPN routing instances, the circuit automatically uses ethernet encapsulation. For Layer 2 VPN, you need to include the encapsulation-type statement and specify the value ethernet at either 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]

Note: 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

[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.

Note: Configuring vlan-id-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 (not the entire range) needs to be associated with a logical interface. If you specify the entire range (1-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-id-range 1-4094;
}

  • Best Practice

    [edit interfaces interface-name]
unit 0;

Required Privilege Level

interface—To view this statement in the configuration.

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

 

Related Documentation

 

Published: 2013-09-24

Previous Page Next Page