Netgear WC7520 - ProSafe 20-AP Wireless Controller Manual De Referência
Access Point Discovery and Management
53
ProSafe 20-AP Wireless Controller WC7520
-
UDP port 6650. Used by the control channel between the wireless controller and the
remote access point.
remote access point.
-
UDP port 7890. Used by the multicast discovery process. This port does not need to
be unblocked in a configuration in which remote access points are located behind a
NAT router.
be unblocked in a configuration in which remote access points are located behind a
NAT router.
•
Enable DHCP option 43 (vendor-specific information) on the DHCP server. Specify the
wireless controller’s IP address to allow the access points to receive the wireless
controller’s IP address and the DHCP server to assign IP addresses to the access points.
controller’s IP address and the DHCP server to assign IP addresses to the access points.
The DHCP server on the wireless controller automatically enables DHCP option 43 with
its own IP address.
its own IP address.
•
Access points behind a NAT router first need to be converted to managed access points
and then be installed behind the NAT router.
•
Each access point needs to have an IP address. All access points that are the same
model ship with the same default IP address. With the exception of access points in
factory default state that are in the same Layer 2 network at the remote site, if more than
one access point has the same IP address, then only one of them is discovered at a time.
You have to add the access point to the managed list, change its IP address, and then
run discovery again to discover the next access point with that IP address.
factory default state that are in the same Layer 2 network at the remote site, if more than
one access point has the same IP address, then only one of them is discovered at a time.
You have to add the access point to the managed list, change its IP address, and then
run discovery again to discover the next access point with that IP address.
•
An access point needs to run at least its initial firmware release or a newer version. There
are no other firmware requirements for the access point to function with the wireless
controller.
controller.
Tip:
For management and monitoring purposes, make sure that you give the
remote access points at one site the same location name and that you
create and assign meaningful building and floor names. For information
about creating building and floor names, see
create and assign meaningful building and floor names. For information
about creating building and floor names, see
on page 42; for information about assigning location, building,
and floor names, see
Limitations after Discovery
The following limitations apply after remote access points have been discovered:
•
Seamless Layer 2 roaming is supported for the clients of a remote access points, but
seamless Layer 3 roaming is not supported for the clients across remote access points.
When clients move from one IP subnet to another at the remote site, they are
disconnected from their access point and need to reconnect to another access point.
When clients move from one IP subnet to another at the remote site, they are
disconnected from their access point and need to reconnect to another access point.
•
If a remote access point is disconnected from the wireless controller, for example,
because the VPN connection goes down, the following occurs:
-
The remote access point uses its last known configuration and functions as a
standalone access point while continuously attempting to reconnect to the wireless
controller.
standalone access point while continuously attempting to reconnect to the wireless
controller.
-
If the access point uses WPA-PSK, WPA2-PSK, or WPA-PSK & WPA2-PSK
authentication, it can continue to accept new clients. If the access point uses RADIUS
authentication, it can continue to accept new clients. If the access point uses RADIUS