WESM zl Management and Configuration Guide WT.01.28 and greater

2-67
Configuring the ProCurve Wireless Edge Services zl Module
Radio Port Adoption
10.4.1.30 10.4.1.40 10.4.2.35
4. Ensure that all necessary helper addresses are in place in your network infra-
structure so that the RP’s DHCP request can reach the server.
5. Ensure that the RP’s default gateway can reach the IP addresses specified in
option 189.
6. The Wireless Edge Services zl Module’s internal uplink port must be tagged for
the VLAN on which RPs messages arrive—that is, the VLAN on which the
module has the IP address specified in option 189.
The module’s uplink port is probably already tagged for this VLAN. If so, the
RP is adopted without further configuration.
7. Install the RP in its final location, connecting it to a PoE device.
Enabling Layer 3 Adoption Through DNS Lookup
The DNS strategy has the advantage that the RP can receive a DHCP configuration
that is probably already in place on your network’s DHCP server. In fact, the RP
might be able to connect to the network and immediately be adopted at Layer 3.
However, for this to occur, your DNS server must map the default DNS name known
by RPs to the Wireless Edge Services zl Module’s IP address. If you have changed
the module’s DNS name, you must pre-adopt the RPs and configure the module to
push down the new DNS name to them (explained in step 4 on page 2-68).
Follow these steps to enable Layer 3 adoption:
1. Ensure that the RP has the proper bootloader code.
If the RP has the old boot code, you must have the Wireless Edge Services zl
Module pre-adopt the RP at Layer 2. As part of the adoption process, this module
will automatically update the RP’s bootloader code, as you can check in the
Device Information > Radio Adoption Statistics screen (see Figure 2-35).
The code automatically updates.