Supported Platforms
Related Documentation
- EX, MX Series
- Configuring a VLAN
- Configuring VLAN Identifiers for VLANs and VPLS Routing Instances
- Configuring a Layer 2 Virtual Switch
- Example: Configuring E-LINE and E-LAN Services for a PBB Network
- vlans
- M, MX, T Series
- Configuring VLAN Identifiers for Bridge Domains and VPLS Routing Instances
- MX Series
- Configuring a Bridge Domain
- Configuring Bridge Domains as Switches for Layer 2 Trunk Ports
- Configuring a Layer 2 Virtual Switch
- MX, SRX Series
- bridge-domains
- SRX Series
- Example: Configuring Interfaces and Routing Instances for a User Logical System
vlan-id (Bridge Domain or VLAN)
Syntax
Hierarchy Level
Release Information
Statement introduced in Junos OS Release 8.4.
Support for Layer 2 trunk ports added in Junos OS Release 9.2.
Support for SRX 3400, SRX 3600, SRX 5600, and SRX 5800 devices added in Junos OS Release 9.6.
Support for logical systems added in Junos OS Release 9.6.
Statement introduced in Junos OS Release 12.3R2 for EX Series switches.
Description
Specify a VLAN identifier (VID) to include in the packets sent to and from the bridge domain or VLAN, or a VPLS routing instance.
 | Note: When configuring a VLAN identifier for provider backbone bridge (PBB) routing instances, dual-tagged VIDs and the none option are not permitted. |
Options
number—A valid VLAN identifier. If you configure multiple bridge domains or VLANs with a valid VLAN identifier, you must specify a unique VLAN identifier for each. However, you can use the same VLAN identifier for bridge domains or VLANs that belong to different virtual switches. Use this option to send single tagged frames with the specified VLAN identifier over VPLS VT interfaces.
| Note: If you specify a VLAN identifier, you cannot also use the all option. They are mutually exclusive. |
all—Specify that the bridge domain or VLAN spans all the VLAN identifiers configured on the member logical interfaces.
| Note: You cannot specify the all option if you include a routing interface in the bridge domain or VLAN. |
none—Specify to enable shared VLAN learning or to send untagged frames over VPLS VT interfaces.
| Note: Multichassis link aggregation (MC-LAG) does not support the none option with the vlan-id statement with bridge domains or VLANs. |
Required Privilege Level
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related Documentation
- EX, MX Series
- Configuring a VLAN
- Configuring VLAN Identifiers for VLANs and VPLS Routing Instances
- Configuring a Layer 2 Virtual Switch
- Example: Configuring E-LINE and E-LAN Services for a PBB Network
- vlans
- M, MX, T Series
- Configuring VLAN Identifiers for Bridge Domains and VPLS Routing Instances
- MX Series
- Configuring a Bridge Domain
- Configuring Bridge Domains as Switches for Layer 2 Trunk Ports
- Configuring a Layer 2 Virtual Switch
- MX, SRX Series
- bridge-domains
- SRX Series
- Example: Configuring Interfaces and Routing Instances for a User Logical System
Published: 2013-04-03
Supported Platforms
Related Documentation
- EX, MX Series
- Configuring a VLAN
- Configuring VLAN Identifiers for VLANs and VPLS Routing Instances
- Configuring a Layer 2 Virtual Switch
- Example: Configuring E-LINE and E-LAN Services for a PBB Network
- vlans
- M, MX, T Series
- Configuring VLAN Identifiers for Bridge Domains and VPLS Routing Instances
- MX Series
- Configuring a Bridge Domain
- Configuring Bridge Domains as Switches for Layer 2 Trunk Ports
- Configuring a Layer 2 Virtual Switch
- MX, SRX Series
- bridge-domains
- SRX Series
- Example: Configuring Interfaces and Routing Instances for a User Logical System
