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

2-66
Configuring the ProCurve Wireless Edge Services xl Module
Radio Port Adoption
You can easily allow the RP to use the same pool as other stations. The
DHCP server does not send the 189 option unless the device requests it.
If, however, for whatever reason, you want to create a fixed configuration
for the RP, you should specify the RP’s Ethernet MAC address as the client
ID. You can find this MAC address on the undercarriage of a ProCurve RP
210 or 230 or the top face of a ProCurve RP 220.
3. Whichever type of configuration you choose for the RP, add option 189 to
the configuration. For the option’s value, specify up to three IP addresses
of Wireless Edge Services xl Modules. Separate the addresses with spaces.
For example:
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
infrastructure 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. One of the Wireless Edge Services xl Module’s internal ports 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 on the uplink port without further configuration.
Otherwise, you can tag the VLAN on the uplink or downlink port but
not both.
Caution Never tag the uplink and downlink ports for the same VLAN.
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 config-
uration 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 xl 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.