\u2022Understanding VLANs, page 11-1
\u2022Configuring Normal-Range VLANs, page 11-4
\u2022Configuring Extended-Range VLANs, page 11-12
\u2022Displaying VLANs, page 11-15
\u2022Configuring VLAN Trunks, page 11-16
\u2022Configuring VMPS, page 11-27
A VLAN is a switched network that is logically segmented by function, project team, or application, without regard to the physical locations of the users. VLANs have the same attributes as physical LANs, but you can group end stations even if they are not physically located on the same LAN segment. Any switch port can belong to a VLAN, and unicast, broadcast, and multicast packets are forwarded and flooded only to end stations in the VLAN. Each VLAN is considered a logical network, and packets destined for stations that do not belong to the VLAN must be forwarded through a router or bridge as shown inFigure 11-1. Because a VLAN is considered a separate logical network, it contains its own bridge Management Information Base (MIB) information and can support its own implementation of spanning tree. SeeChapter 15, \u201cConfiguring STP\u201d andChapter 16, \u201cConfiguring RSTP and MSTP.\u201d
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. A Catalyst 3550 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\u201cSwitch Virtual
The Catalyst 3550 switch supports 1005 VLANs in VTP client, server, and transparent modes. VLANs are identified with a number from 1 to 4094. VLAN IDs 1002 through 1005 are reserved for Token Ring and FDDI VLANs. VTP only learns normal-range VLANs, with VLAN IDs 1 to 1005; VLAN IDs greater than 1005 are extended-range VLANs and are not stored in the VLAN database. The switch must be in VTP transparent mode when you create VLAN IDs from 1006 to 4094.
You configure a port to belong to a VLAN by assigning a membership mode that determines the kind of traffic the port carries and the number of VLANs to which it can belong.Table 11-1 lists the membership modes and membership and VTP characteristics.
A static-access port can belong to one VLAN and is
manually assigned to that VLAN. For more information,
see the\u201cAssigning Static-Access Ports to a VLAN\u201d
the VTP mode to transparent to disable
VTP. To participate in VTP, there must be
at least one trunk port on the switch
connected to a trunk port of a second
limited by configuring the allowed-VLAN list. You can
also modify the pruning-eligible list to block flooded
traffic to VLANs on trunk ports that are included in the
VTP is recommended but not required.
VTP maintains VLAN configuration
consistency by managing the addition,
deletion, and renaming of VLANs on a
network-wide basis. VTP exchanges
VLAN configuration messages with other
switches over trunk links.
by a VMPS. The VMPS can be a Catalyst 5000 or
Catalyst 6000 series switch, for example, but never a
Catalyst 3550 switch.
A voice VLAN port is an access port attached to a Cisco
IP Phone, configured to use one VLAN for voice traffic
and another VLAN for data traffic from a device attached
to the phone. For more information about voice VLAN
ports, seeChapter 13, \u201cConfiguring Voice VLAN.\u201d
network. You configure a tunnel port on an edge switch in the service provider network and connect it to an 802.1Q trunk port on a customer interface, creating an asymmetric link. A tunnel port belongs to a single VLAN that is
This action might not be possible to undo. Are you sure you want to continue?