WESM zl Management and Configuration Guide WT.01.28 and greater

2-65
Configuring the ProCurve Wireless Edge Services zl Module
Radio Port Adoption
Note If a firewall separates your RPs from your Wireless Edge Services zl Module, you
must ensure that this firewall allows the RPs adoption messages. The RPs send these
messages on UDP port 24576; do not filter this port.
The next sections describe in more detail the two strategies for enabling Layer 3
adoption of RPs.
Enabling Layer 3 Adoption Through DHCP Option 189
Using DHCP option 189 to adopt RPs at Layer 3 has these advantages:
■ By specifying the IP addresses of up to three Wireless Edge Services zl Modules,
you ensure high availability. If one module happens to be down, the RP can be
adopted by another module.
■ Even if your Wireless Edge Services zl Modules use custom hostnames, you do
not have to pre-adopt RPs. The RPs receive the modules’ IP addresses directly
in option 189, so they do not need to send DNS requests.
However, this strategy does require some extra setup: you must define the private
option 189 on your server and you must add the option to the DHCP configuration
that the RP will receive. Refer to your DHCP server’s documentation for instructions
on adding private options. You must set up the option so that its code is 189 and its
value type is “string” (instead of “byte” or “IP”).
Complete 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.