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

2-63
Configuring the ProCurve Wireless Edge Services xl Module
Radio Port Adoption
■ the correct bootloader code
The bootloader code allows the RP to request a DHCP configuration and
contact the Wireless Edge Services xl Module at Layer 3. If the RP did not
ship with this code, it must first be adopted at Layer 2 by a Wireless Edge
Services xl Module that is running software version 02.XX.
The instructions for enabling Layer 3 adoption explain how to determine
your RP’s bootloader code version, and if necessary, update the code.
Note This guide refers to the process of adopting and configuring an RP before
installing it in its final location as pre-adoption.
In addition to ensuring that your RP meets the requirements for Layer 3
adoption, you must ensure that your network meets the following require-
ments:
■ DHCP server that sends one of these two configurations to the RP:
• an IP address, a default gateway address, and option 189, which
includes the IP address of up to three Wireless Edge Services xl
Modules
• an IP address, a default gateway address, a domain suffix, and a DNS
server address
■ router that acts as the default gateway for the RP and can reach the
Wireless Edge Services xl Module
■ any necessary IP helper addresses on infrastructure devices so that the
RP can reach the DHCP server
■ the internal uplink port tagged for the VLAN on which the module has the
address that the RP contacts
Note RPs can be adopted at Layer 3 on the downlink port. However, the following
rules make this configuration less desirable:
■ The same VLAN cannot be tagged on both the uplink and the downlink
port.
■ Layer 3 RPs must contact the Wireless Edge Services xl Module on the
VLAN with the default gateway (for a module that does not route).
■ The module must have a route back to the Layer 3 RPs through the same
VLAN on which the RPs contact it (for a module that routes).
■ a PoE device to provide the RP with power