User's Manual

Working with third-party APs
hwc_3rdpartyaps.fm
A31003-W1050-U100-2-7619
, March 2008
280 HiPath Wireless Controller, Access Points and Convergence Software V5 R1 , C20/C2400 User Guide
Step 4 – Define filtering rules for the third-party APs:
1. Because the third-party APs are mapped to a physical port, you must define
the Exception filters on the physical port, using the Port Exception Filters
page. For more information, see Section 6.9, “Configuring filtering rules for a
VNS”, on page 194.
2. Define filtering rules that allow access to other services and protocols on the
network such as HTTP, FTP, Telnet, SNMP.
In addition, modify the following functions on the third-party access point:
• Disable the access point's DHCP server, so that the IP address assignment
for any wireless device on the AP is from the DHCP server at the HiPath
Wireless Controller with VNS information.
• Disable the third-party access point's layer-3 IP routing capability and set the
access point to work as a layer-2 bridge.
Here are the differences between third-party access points and Wireless APs on
the HiPath Wireless Controller, Access Points and Convergence Software
system:
• A third-party access point exchanges data with the HiPath Wireless
Controller's data port using standard IP over Ethernet protocol. The third-
party access points do not support the tunnelling protocol for encapsulation.
• For third-party access points, the VNS is mapped to the physical data port
and this is the default gateway for mobile units supported by the third-party
access points.
• A HiPath Wireless Controller cannot directly control or manage the
configuration of a third-party access point.
• Third-party access points are required to broadcast an SSID unique to their
segment. This SSID cannot be used by any other VNS.
• Roaming from third-party access points to Wireless APs and vice versa is not
supported.