Table of Contents
Advertisement
64
C
3: C
HAPTER
ONFIGURING AND
M
P
ANAGING
ORTS AND
A wireless client cannot join a VLAN if the physical network ports on the
WX switch in the VLAN are down. However, a wireless client that is
already in a VLAN whose physical network ports go down remains in the
VLAN even though the VLAN is down.
VLANs, IP Subnets, and IP Addressing
Generally, VLANs are equivalent to IP subnets. If a WX switch is
connected to the network by only one IP subnet, the switch must have at
least one VLAN configured. Optionally, each VLAN can have its own IP
address. However, no two IP addresses on the switch can belong to the
same IP subnet.
You must assign the system IP address to one of the VLANs, for
communications between WX switches and for unsolicited
communications such as SNMP traps and RADIUS accounting messages.
Any IP address configured on a WX switch can be used for management
access unless explicitly restricted. (For more information about the system
IP address, see Chapter 4, "Configuring and Managing IP Interfaces and
Services," on page 77.)
Users and VLANs
When a user successfully authenticates to the network, the user is
assigned to a specific VLAN. A user remains associated with the same
VLAN throughout the user's session on the network, even when roaming
from one WX switch to another within the Mobility Domain.
You assign a user to a VLAN by setting one of the following attributes on
the RADIUS servers or in the local user database:
Tunnel-Private-Group-ID — This attribute is described in RFC 2868,
RADIUS Attributes for Tunnel Protocol Support.
VLAN-Name — This attribute is a 3Com vendor-specific attribute
(VSA).
You cannot configure the Tunnel-Private-Group-ID attribute in the local
user database.
Specify the VLAN name, not the VLAN number. The examples in this
chapter assume the VLAN is assigned on a RADIUS server with either of
the valid attributes. (For more information, see Chapter 13, "Configuring
AAA for Network Users," on page 277.)
VLAN
S
Advertisement
Table of Contents
