13-2
Cisco Catalyst Blade Switch 3130 and 3032 for Dell Software Configuration Guide
OL-12247-04
Chapter 13 Configuring VLANs
Understanding VLANs
shows an example of VLANs segmented into logically defined networks.
Figure 13-1
VLANs as Logically Defined Networks
VLANs are often associated with IP subnetworks. For example, all the end stations in a particular IP
subnet belong to the same VLAN. Interface VLAN membership on the switch is assigned manually on
an interface-by-interface basis. When you assign switch interfaces to VLANs by using this method, it is
known as interface-based, or static, VLAN membership.
Traffic between VLANs must be routed or fallback bridged. The switch can route traffic between
VLANs by using switch virtual interfaces (SVIs). An SVI must be explicitly configured and assigned an
IP address to route traffic between VLANs. For more information, see the
and the
“Configuring Layer 3 Interfaces” section on page 11-24
Note
If you plan to configure many VLANs on the switch and to not enable routing, you can use the
sdm
prefer vlan
global configuration command to set the Switch Database Management (sdm) feature to the
VLAN template, which configures system resources to support the maximum number of unicast MAC
addresses. For more information on the SDM templates, see
Chapter 8, “Configuring SDM Templates,”
or see the
sdm prefer
command in the command reference for this release.
Supported VLANs
The switch supports VLANs in VTP client, server, and transparent modes. VLANs are identified by a
number from 1 to 4094. VLAN IDs 1002 through 1005 are reserved for Token Ring and FDDI VLANs.
VTP version 1 and version 2 support only normal-range VLANs (VLAN IDs 1 to 1005). In these
versions, the switch must be in VTP transparent mode when you create VLAN IDs from 1006 to 4094.
Cisco IOS Release 12.2(52)SE and later support VTP version 3. VTP version 3 supports the entire
Enclosure 1
Enclosure 2
Engineering
VLAN
Cisco router
Gigabit
Ethernet
Enclosure 3
Marketing
VLAN
Accounting
VLAN
201766