Table of Contents
Advertisement
Configuring and Managing VLANs
65
VLAN Names
To create a VLAN, you must assign a name to it. VLAN names must be
globally unique across a Mobility Domain to ensure the intended user
connectivity as determined through authentication and authorization.
Every VLAN on a WX switch has both a VLAN name, used for
authorization purposes, and a VLAN number. VLAN numbers can vary
uniquely for each WX switch and are not related to 802.1Q tag values.
You cannot use a number as the first character in a VLAN name.
Roaming and VLANs
WX switches in a Mobility Domain contain a user's traffic within the
VLAN that the user is assigned to. For example, if you assign a user to
VLAN red, the WX switches in the Mobility Domain contain the user's
traffic within VLAN red configured on the switches.
The WX switch through which a user is authenticated is not required to
be a member of the VLAN the user is assigned to. You are not required to
configure the VLAN on all WX switches in the Mobility Domain. When a
user roams to a switch that is not a member of the VLAN the user is
assigned to, the switch can tunnel traffic for the user through another
switch that is a member of the VLAN. The traffic can be of any protocol
type. (For more information about Mobility Domains, see Chapter 5,
"Configuring and Managing Mobility Domain Roaming," on page 107.)
Because the default VLAN (VLAN 1) might not be in the same subnet on
each switch, 3Com recommends that you do not rename the default
VLAN or use it for user traffic. Instead, configure other VLANs for user
traffic.
Traffic Forwarding
A WX switch switches traffic at Layer 2 among ports in the same VLAN.
For example, suppose you configure ports 4 and 5 to belong to VLAN 2
and ports 6 and 7 to belong to VLAN 3. As a result, traffic between port 4
and port 5 is switched, but traffic between port 4 and port 6 is not
switched and needs to be routed by an external router.
Advertisement
Table of Contents
