
Troubleshooting
199
ProSafe 20-AP Wireless Controller WC7520
• 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 (see Access Point Discovery and Discovery
Guidelines on page 51).
• V
erify that access points that are already installed and working in standalone mode have
SSH and SNMP enabled (which is the default setting).
• Make sure tha
t UDP port number 7890 is unblocked in the firewall.
• With
the exception of 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, 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.
• Make sure tha
t the access points run at least their initial firmware release or a newer
version. For firmware requirements, see NETGEAR ProSafe Access Points o
n page 15.
For local access points that are installed across a Layer 3 network:
Make sure that either one of the following options is enabled:
• Multicast
routing for IP address 254.0.100.250 between the wireless controller and the
access point.
• DH
CP option 43 (vendor-specific information) on the DHCP server. (Specifying a DHCP
server on the wireless controller automatically enables DHCP option 43 with its own IP
a
ddress.)
For remote access points:
• Make sure tha
t DHCP option 43 (vendor-specific information) is enabled on the DHCP
server. (Specifying a DHCP server on the wireless controller automatically enables DHCP
option 43 with its own IP address.)
• Make sure tha
t the following ports are unblocked in the firewall:
- T
CP port 22.
- UDP port
s 69, 123, 138, 161, and 6650. (These ports are in addition to port 7890).
• Make sure tha
t access points behind a NAT router have been converted to managed
access points before they are installed behind the NAT router.
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 is issued by the DHCP server, either one in
the network or one that is configured on the wireless controller. This occurs to ensure that
each managed access point has a unique IP address.
If there is no 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 there is no
DHCP server in the network, configure one on the wireless controller (see Manage the DHCP
Kommentare zu diesen Handbüchern