WESM zl Management and Configuration Guide WT.01.28 and greater

2-58
Configuring the ProCurve Wireless Edge Services zl Module
Radio Port Adoption
■ The Wireless Edge Services zl Module’s downlink port must be a tagged member
of the Radio Port VLAN (by default, VLAN 2100).
■ The switch port that connects to the RP must be an untagged member of the
Radio Port VLAN.
■ Each switch interface that carries traffic between the RP and the module must
be either a tagged or untagged member of the Radio Port VLAN, as your network
requires.
For example, you may attach the RPs to a Power over Ethernet (PoE) compatible
infrastructure switch, which is connected, in turn, to the wireless services-
enabled switch. The uplink port on the infrastructure switch must be able to carry
traffic from the Radio Port VLAN. If the uplink port is carrying traffic from other
VLANs, you must make that port a tagged member of the Radio Port VLAN.
Auto-Provisioning on the Wireless Services-Enabled Switch
The wireless-enabled switch automatically creates a default Radio Port VLAN—
VLAN 2100—when you install the Wireless Edge Services zl Module in the Switch
5400zl or Switch 8200zl chassis. If VLAN 2100 is already being used, the wireless
services-enabled switch uses the next available VLAN.
In addition to creating the default Radio Port VLAN, the wireless services-enabled
switch automatically configures the module’s downlink port as a tagged member of
VLAN 2100. The downlink port handles the traffic sent to and from RPs.
If you attach RPs to a PoE module that is installed in the wireless services-enabled
switch, the switch automatically configures each RP’s switch port as an untagged
member of the default Radio Port VLAN. (Because the RP does not support 802.1Q,
it must be an untagged member of the Radio Port VLAN.)
When the appropriate VLAN memberships are established, the RPs can transmit
traffic to the Wireless Edge Services zl Module, and the module can, in turn, detect
the RPs. (See Figure 2-31.) (For more information about the communications
between the RPs and the wireless services-enabled switch, see Chapter 1: “Introduc-
tion.”)