WESM zl Management and Configuration Guide WT.01.XX and greater

2-64
Configuring the ProCurve Wireless Edge Services zl 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 zl 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 zl Module.
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 zl
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 zl Module
■ any necessary IP helper addresses on infrastructure devices so that the
RP can reach the DHCP server
■ the internal uplink port on the Wireless Edge Services zl Module tagged
for the VLAN on which the module has its IP address
Note Do not tag the downlink port for this VLAN. (The two internal ports of Wireless
Edge Services zl Module must never be tagged for the same VLAN.) The RP
can be adopted on the uplink port.
■ a PoE device to provide the RP with power
■ optionally, a DNS server that maps the name that the RP knows for the
Wireless Edge Services zl Module to the module’s IP address (required
only if you select the DNS strategy)
• By default, the RP sends a DNS request for this name:
PROCURVE-WESM