Wireless/Redundant Edge Services xl Module Management and Configuration Guide WS.02.xx and greater

2-57
Configuring the ProCurve Wireless Edge Services xl Module
Radio Port Adoption
Network Requirements for Layer 2 Adoption
Before the Wireless Edge Services xl Module can adopt an RP that is con-
nected to your network, the module must detect that RP. Detection is depen-
dent upon network connectivity: all the network interfaces between the
module and the RP must be correctly configured to carry traffic in the Radio
Port VLAN.
■ The Wireless Edge Services xl 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 an 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 xl Module
in the ProCurve Switch 5300xl 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 trans-
mit traffic to the Wireless Edge Services xl 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: Introduction.)