Table of Contents
Advertisement
Creating and Modifying VLANs
VLAN Configuration Guidelines
Follow these guidelines when creating and modifying VLANs in your network:
•
•
•
•
•
•
•
•
Cisco ME 3400 Ethernet Access Switch Software Configuration Guide
11-8
The switch supports 1005 VLANs.
Normal-range Ethernet VLANs are identified with a number between 1 and 1001. VLAN numbers
1002 through 1005 are reserved for Token Ring and FDDI VLANs.
The switch does not support Token Ring or FDDI media. The switch does not forward FDDI,
FDDI-Net, TrCRF, or TrBRF traffic.
VLAN configurations for VLANs 1 to 1005 are always saved in the VLAN database and in the
switch running configuration file.
Configuration options for VLAN IDs 1006 through 4094 (extended-range VLANs) are limited to
MTU, RSPAN VLAN, private VLAN, and UNI VLAN. Extended-range VLANs are not saved in the
VLAN database.
Spanning Tree Protocol (STP) is enabled by default for only NNIs on all VLANs. The switch
supports 128 spanning-tree instances. If a switch has more active VLANs than supported
spanning-tree instances, spanning tree can be enabled on 128 VLANs and is disabled on the
remaining VLANs. If you have already used all available spanning-tree instances on a switch,
adding another VLAN creates a VLAN on that switch that is not running spanning tree. If you have
the default allowed list on the trunk ports of that switch (which is to allow all VLANs), the new
VLAN is carried on all trunk ports. Depending on the topology of the network, this could create a
loop in the new VLAN that would not be broken, particularly if there are several adjacent switches
that all have run out of spanning-tree instances. You can prevent this possibility by setting allowed
lists on the trunk ports of switches that have used up their allocation of spanning-tree instances.
If the number of VLANs on the switch exceeds the number of supported spanning-tree instances,
we recommend that you configure the IEEE 802.1s Multiple STP (MSTP) on your switch to map
multiple VLANs to a single spanning-tree instance. For more information about MSTP, see
Chapter 15, "Configuring MSTP."
MSTP is supported only on NNIs.
Note
Each routed port on the switch creates an internal VLAN for its use. These internal VLANs use
extended-range VLAN numbers, and the internal VLAN ID cannot be used for an extended-range
VLAN. If you try to create an extended-range VLAN with a VLAN ID that is already allocated as
an internal VLAN, an error message is generated, and the command is rejected.
–
Because internal VLAN IDs are in the lower part of the extended range, we recommend that you
create extended-range VLANs beginning from the highest number (4094) and moving to the
lowest (1006) to reduce the possibility of using an internal VLAN ID.
–
Before configuring extended-range VLANs, enter the show vlan internal usage privileged
EXEC command to see which VLANs have been allocated as internal VLANs.
–
If necessary, you can shut down the routed port assigned to the internal VLAN, which frees up
the internal VLAN, and then create the extended-range VLAN and re-enable the port, which
then uses another VLAN as its internal VLAN. See the
with an Internal VLAN ID" section on page
Although the switch supports a total of 1005 (normal-range and extended-range) VLANs, the
number of routed ports, SVIs, and other configured features affects the use of the switch hardware.
If you try to create an extended-range VLAN and there are not enough hardware resources available,
an error message is generated, and the extended-range VLAN is rejected.
Chapter 11
"Creating an Extended-Range VLAN
11-11.
Configuring VLANs
78-17058-01
Hide quick links:
Advertisement
Table of Contents
Troubleshooting
