Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

TechLibrary
Navigation

Configuring the Native VLAN Identifier (CLI Procedure)

Note: This task uses Junos OS for EX Series switches and Junos OS for QFX3500 and QFX3600 switches with support for the Enhanced Layer 2 Software (ELS) configuration style. If your switch runs software that does not support ELS, see Configuring the Native VLAN Identifier (CLI Procedure). For ELS details, see Getting Started with Enhanced Layer 2 Software.

Switches can receive and forward routed or bridged Ethernet frames with 802.1Q VLAN tags. Typically, trunk ports, which connect switches to each other, accept untagged control packets but do not accept untagged data packets. You can enable a trunk port to accept untagged data packets by configuring a native VLAN ID on the interface on which you want the untagged data packets to be received. The logical interface on which untagged packets are to be received must be configured with the same VLAN ID as the native VLAN ID configured on the physical interface.

To configure the native VLAN ID by using the command-line interface (CLI):

  1. On the interface on which you want untagged data packets to be received, set the interface mode to trunk, which specifies that the interface is in multiple VLANs and can multiplex traffic between different VLANs.:
    [edit interfaces]
    user@switch# set interface-name unit logical-unit-number family ethernet-switching interface-mode trunk
  2. Configure the native VLAN ID:
    [edit interfaces]
    user@switch# set interface-name native-vlan-id vlan-id
  3. Specify that the logical interface that will receive the untagged data packets is a member of the native VLAN:
    [edit interfaces]
    user@switch# set interface-name unit logical-unit-number family ethernet-switching vlan members vlan-id
 

Related Documentation

 

Published: 2014-07-23

Previous Page Next Page