Wireless Access

Hello!

Has anyone experience with the adoption of a Layer 3 Radio Points (RP 210) on a WLAN Controller WESM-XL (9001A)?

I have performed the steps as in "Management and Configuration Guide" page 2-56 and following, but the Layer 3 adoption is not working.


Step 1
-->ProCurve (wireless-services-C) (config-wireless) # radio-dns-name <NAME>
-->Entry of the wireless controller in the DNS- Server

Step 2
-->Connecting the RP to the wireless controller, Layer 2 adoption of the RP, OK


Step 3
-->Connecting the RP to a remote VLAN segment with DHCP. Remote Vlan is only reachable over the WL- Controller Uplink-port (default route)


Step 4
"ping" the RP IP-Address from the WLAN controller Console (occasional response from the RP, so DHCP and Routing works)

No adoption of RP by the wireless controller

-------------------------------------
More Information:
! configuration of ProCurveWLANModule wlan-access version WS.02.07!
version 1.0
! 5304xl; E.11.03
-------------------------------------</NAME>

I haven't done this yet, but I was told sent the following DHCP requiremetns for a Windows DHCP server.

"First configure the DHCP scope for the IP range of the VLAN where radios will connect remotely (this may already be done). The radio will need to be connected in an untagged port. On a Windows DHCP server, highlight the server, and go to "Action" and drop down to "set predefined actions" and click "add" button. In the little popup box, give it a name - we called ours "option 189WES" change data type to string, code should be 189 and leave description blank. hit ok. Now go to scope options, under that scope and go to "configure options" select the checkbox for 189 and in the string field type in the IP address of the WES module, click ok."

Hello Robert!
Yes this is the way with using the DHCP option 189.
It should also going only with a DNS- Entry for the Wireless Controller (WLC), after a Layer 2 Adoption of a RP.
1.wireless controller
ProCurve (wireless-services-C) (config-wireless) # radio-dns-name <NAME>
?? <NAME> == full dns name ??
2. on DNS server
dns-name <IP-WLC>
3. Start RP on remote LAN with DHCP- Server (information to RP only: ip- addr., gateway, dns-server)

Has someone to run it?</IP-WLC></NAME></NAME>

Between step 2 and step 3 is en newly adaption of the rp necessary (delete an new found)