- All standalone access points need to have SNMP and SSH enabled.
- The following ports need to be unblocked in the firewall at the site where the wireless controller is located in order for the remote access points to communicate with the wireless controller:
-
- TCP port 22. Used by Secure Shell (SSH) and Secure Copy (SCP) for the transfer of software images and large configuration files and for the transfer over a tunnel.
- UDP port 69. Used by TFTP for software image upgrades of standalone access points.
- UDP port 123. Used by Network Time Protocol (NTP).
- UDP port 138. Used by NetBIOS to resolve names.
- UDP port 161. Used by the SNMP discovery process.
- UDP port 6650. Used by the control channel between the wireless controller and the 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.
- 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.
The DHCP server on the wireless controller automatically enables DHCP option 43 with 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.
- 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.
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 "How do I define and edit buildings and floors when planning RF on my ProSAFE Wireless Controller WC7600?
Last Updated:10/17/2025
|
Article ID: 25670