-
null
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Note ● For complete syntax and usage information for the commands used in this chapter, see these publications:
http://www.cisco.com/en/US/products/ps11846/prod_command_reference_list.html
http://www.cisco.com/en/US/products/hw/switches/ps708/tsd_products_support_series_home.html
Participate in the Technical Documentation Ideas forum
The following recommendations apply to Fabric Extender (FEX) VLANs:
If the switch is in VLAN transparent mode, use the copy running-config startup-config command to save the VLAN configuration to the startup-config file. After you save the running configuration as the startup configuration, use the show running-config and show startup-config commands to display the VLAN configuration.
A VLAN is a group of end stations with a common set of requirements, independent of physical location. VLANs have the same attributes as a physical LAN but allow you to group end stations even if they are not located physically on the same LAN segment.
VLANs are usually associated with IP subnetworks. For example, all the end stations in a particular IP subnet belong to the same VLAN. Traffic between VLANs must be routed. LAN port VLAN membership is assigned manually on an port-by-port basis.
Note You must enable the extended system ID to use 4094 VLANs (see the “Information about the Bridge ID” section).
Cisco IOS Release 15.4SY supports 4094 VLANs in accordance with the IEEE 802.1Q standard. These VLANs are organized into several ranges; you use each range slightly differently. Some of these VLANs are propagated to other switches in the network when you use the VLAN Trunking Protocol (VTP). The extended-range VLANs are not propagated, so you must configure extended-range VLANs manually on each network device.
Table 26-1 describes the VLAN ranges.
The following information applies to VLAN ranges:
– Other VLANs: “VLAN vlan_ID ”
Note ● Ethernet VLAN 1 uses only default values.
You can configure the following parameters for VLANs 2 through 1001:
The VLAN locking feature provides an extra level of verification to ensure that you have configured the intended VLAN. When VLAN locking is enabled, you need to specify the VLAN name when you change a port from one VLAN to another. This feature affects switchport commands (in interface configuration mode) that specify the VLANs or private VLANs for access and trunk ports.
For additional information about how to configure access and trunk ports with VLAN locking enabled, see the “How to Configure LAN Interfaces for Layer 2 Switching” section.
For additional information about how to configure ports in private VLANs with VLAN locking enabled, see the “How to Configure Private VLANs” section.
By default, the VLAN locking is disabled. To enable VLAN locking, perform this task:
|
|
---|---|
User-configured VLANs have unique IDs from 1 to 4094, except for reserved VLANs (see Table 26-1). Enter the vlan command with an unused ID to create a VLAN. Enter the vlan command for an existing VLAN to modify the VLAN (you cannot modify an existing VLAN that is being used by a Layer 3 port or a software feature).
See the “Default Settings for VLANs” section for the list of default parameters that are assigned when you create a VLAN. If you do not specify the VLAN type with the media keyword, the VLAN is an Ethernet VLAN.
To create or modify a VLAN, perform this task:
When you create or modify an Ethernet VLAN, note the following information:
When deleting VLANs, note the following information:
This example shows how to create an Ethernet VLAN in global configuration mode and verify the configuration:
A VLAN created in a management domain remains unused until you assign one or more LAN ports to the VLAN.
Note Make sure you assign LAN ports to a VLAN of the appropriate type. Assign Ethernet ports to Ethernet-type VLANs.
To assign one or more LAN ports to a VLAN, complete the procedures in the “How to Configure LAN Interfaces for Layer 2 Switching” section.
For more information about VLAN allocation, see the “VLAN Ranges” section.
Note The internal VLAN allocation policy is applied only following a reload.
To configure the internal VLAN allocation policy, perform this task:
When you configure the internal VLAN allocation policy, note the following information:
This example shows how to configure descending as the internal VLAN allocation policy:
Note ● To avoid spanning tree loops, be careful not to misconfigure the VLAN translation feature.
When translating VLANs, follow these guidelines and restrictions:
|
|
Port Groups |
per Port Group |
per Port Group |
---|---|---|---|---|
See the Release Notes. |
||||
Note To configure a port as a trunk, see the “Configuring a Layer 2 Switching Port as a Trunk” section.
*Following are the different combinations based on the operational port mode on Supervisor Engine 6T:
To translate VLANs on a trunk port, perform this task:
This example shows how to map VLAN 1649 to VLAN 755 Gigabit Ethernet port 5/2:
This example shows how to verify the configuration:
To enable VLAN translation on other ports in a port group, perform this task:
|
|
|
---|---|---|
This example shows how to enable VLAN translation on a port:
The VLAN database is stored in the vlan.dat file. You should create a backup of the vlan.dat file in addition to backing up the running-config and startup-config files. If you replace the existing supervisor engine, copy the startup-config file as well as the vlan.dat file to restore the system. The vlan.dat file is read on bootup and you will have to reload the supervisor engine after uploading the file. To view the file location, use the dir vlan.dat command. To copy the file (binary), use the copy vlan.dat tftp command.
http://www.cisco.com/en/US/products/hw/switches/ps708/tsd_products_support_series_home.html
Participate in the Technical Documentation Ideas forum