If you encounter access point discovery or connection problems, the information in this section might help you to resolve these problems.
Resolve Discovery Problems
If the wireless controller does not discover any or all access points, check the configuration of the wireless controller and access points.
For all access points, check the following:
- Make sure that the wireless controller is connected to the LAN (see How do I resolve problems with access points for my ProSAFE Wireless Controller WC7600?
- Make sure that you have entered the correct IP range if the access points function in different VLANs, are behind an IP subnet, or are already installed and working in standalone mode.
- Make sure that the access points run at least their initial firmware release or a newer version.
- For local access points that are installed across a Layer 3 network, check the following:
- Verify that access points that are already installed and working in standalone mode have SSH and SNMP enabled (which is the default setting).
- Make sure that UDP port number 7890 is unblocked in the firewall.
- Except for access points in factory default state that are in the same Layer 2 network, if more than one access point has the same IP address, only one of them is discovered at a time. You must add the access point to the managed list, change its IP address, and run discovery again to discover the next access point with that IP address.
- Make sure that DHCP option 43 (vendor-specific information) is enabled on an external DHCP server. (Specifying an internal DHCP server on the wireless controller automatically enables DHCP option 43 with the IP address of the wireless controller.)
Resolve Connection Problems
When an access point is converted from standalone AP mode to managed AP mode, its static IP address is changed to an IP address that a DHCP server has issued, either a DHCP server in the network or a DHCP server that is configured on the wireless controller. This change occurs to ensure that each managed access point has a unique IP address.
If the network does not include a DHCP server or if the access point cannot reach the DHCP server, the access point remains in the Connecting state, attempting to obtain an IP address. If the network does not include a DHCP server, configure one on the wireless controller (see How do I manage the DHCP Server on my ProSAFE Wireless Controller WC7600?). When a DHCP server becomes available, the access point can transition from the Connecting state to the Connected state.
If the Power LED of an access point blinks amber, the access point has lost its connection to the wireless controller. In this situation, check the network connectivity between the access point and the wireless controller.
Network Performance and Rogue Access Point Detection
When rogue access point detection is enabled, access points intermittently go off channel for short periods, which can affect network performance. The default rogue access point detection interval is 30 minutes. This interval is not configurable.