configure vlan add ports

configure [ {vlan} vlan_name | vlan vlan_list] add ports [port_list | all] {tagged tag | untagged} {{stpd} stpd_name} {dot1d | emistp | pvst-plus}}

Description

Adds one or more ports in a VLAN.

Syntax Description

`vlan_name`	Specifies a VLAN name.
`vlan_list`	Specifies a VLAN list of IDs.
`port_list`	Specifies a list of ports or slots and ports.
all	Specifies all ports.
tagged `tag`	Specifies the ports should be configured as tagged.
untagged	Specifies the ports should be configured as untagged.
`stpd_name`	Specifies an STP domain name.
dot1d \| emistp \| pvst-plus	Specifies the BPDU encapsulation mode for these STP ports.

Default

Untagged.

Usage Guidelines

The VLAN must already exist before you can add (or delete) ports: use the create vlan command to create the VLAN.

If the VLAN uses 802.1Q tagging, you can specify tagged or untagged port(s). If the VLAN is untagged, the ports cannot be tagged.

Untagged ports can only be a member of a single VLAN. By default, they are members of the default VLAN (named Default). In order to add untagged ports to a different VLAN, you must first remove them from the default VLAN. You do not need to do this to add them to another VLAN as tagged ports. If you attempt to add an untagged port to a VLAN prior to removing it from the default VLAN, you see the following error message:

Error: Protocol conflict when adding untagged port 1:2. Either add this port as tagged or assign another protocol to this VLAN.

Note

This message is not displayed if keyword all is used as port_list.

The ports that you add to a VLAN and the VLAN itself cannot be explicitly assigned to different virtual routers (VRs). When multiple VRs are defined, consider the following guidelines while adding ports to a VLAN:

A VLAN can belong (either through explicit or implicit assignment) to only one VR.
If a VLAN is not explicitly assigned to a VR, then the ports added to the VLAN must be explicitly assigned to a single VR.
If a VLAN is explicitly assigned to a VR, then the ports added to the VLAN must be explicitly assigned to the same VR or to no VR.
If a port is added to VLANs that are explicitly assigned to different VRs, the port must be explicitly assigned to no VR.
Note
User-created VRs are supported only on the platforms listed for this feature in in the Feature License Requirements document. On switches that do not support user-created VRs, all VLANs are created in VR-Default and cannot be moved.

Refer to STP in the ExtremeXOS 16.2 User Guide for more information on configuring Spanning Tree Domains.

Note

If you use the same name across categories (for example, STPD and EAPS names), we recommend that you specify the identifying keyword as well as the actual name. If you do not use the keyword, the system may return an error message.

Beginning with ExtremeXOS 11.4, the system returns the following message if the ports you are adding are already EAPS primary or EAPS secondary ports:

WARNING: Make sure Vlan1 is protected by EAPS. Adding EAPS ring ports to a VLAN could cause a loop in the network. Do you really want to add these ports? (y/n)

Example

The following example assigns tagged ports 1:1, 1:2, 1:3, and 1:6 to a VLAN named "accounting":

configure vlan accounting add ports 1:1, 1:2, 1:3, 1:6 tagged

History

This command was first available in ExtremeXOS 10.1.

The tagged keyword was added in ExtremeXOS 15.4.

The vlan_list option was added in ExtremeXOS 16.1.

Platform Availability

This command is available on all platforms.

Published August 2016prev | next

Email this topic

Print this page Print this page

Leave feedback Feedback