WESM zl Management and Configuration Guide WT.01.28 and greater

1-66
Introduction
Radio Ports
Figure 1-22. Communications Between an RP and the Wireless Edge Services
zl Module
If you must place your RP on a different subnetwork from the Radio Port VLAN, the
messages listed above fail to receive a response from the Wireless Edge Services zl
Module. The RP initiates Layer 3 adoption, sending these messages:
■ DHCP messages—request an IP address and other options such as a default
gateway, a DNS server address, a domain name, and private option 189 (which
specifies up to three IP addresses for Wireless Edge Services zl Modules).
■ DNS requests—request the IP address for the Wireless Edge Services zl Mod-
ule. If the RP does not receive option 189 from the DHCP server, it uses DNS
to discover the module’s IP address. At its factory settings, the RP requests the
IP address for this hostname: PROCURVE-WESM. The RP also adds the domain
suffix that it received in the DHCP configuration. For example:
PROCURVE-WESM.procurve.com
If your Wireless Edge Services zl Module uses a customized hostname, you must
first adopt the RP at Layer 2. After a module adopts the RP, you can change the
hostname for which the RP sends the request. You can then install the RP in its
final location, and the RP can find the module with the customized hostname.
■ Hello messages targeted to the module’s IP address—request that the Wire-
less Edge Services zl Module adopt the RP. The RP is adopted on the VLAN on
which the module receives the message, which is usually one of the module’s
uplink VLANs. (If so, do not tag this VLAN on the module’s downlink port: the
uplink and downlink ports must never carry the same VLANs.) Remember that
because the RP is on a different subnetwork than the module, the RP’s DHCP
configuration must include a default gateway that can route the RP’s messages
to the module.
Figure 1-23 shows the messages that an RP sends as part of Layer 3 adoption.