Netgear WFS709TP - ProSafe Smart Wireless Controller サービスマニュアル
3- More than 16 Access Points configured per Wireless Controller
Each controller can only control 16 (sixteen) access points. If more than sixteen access points are
connected, the controller will not provision the additional access points, which results in a test light on the
unprovisioned access point(s). If a provisioned access point is removed from network, an unprovisioned
access point can then be provisioned.
This becomes particularly relevant when more than one wireless controller in the network, as there is
likely going to be more than 16 access points. In this case, make sure that the load is spread correctly
across the different controllers. This can be controlled by either assigning LMS (Local Master Switch) to
particular location codes, or to Access Points singularly.
connected, the controller will not provision the additional access points, which results in a test light on the
unprovisioned access point(s). If a provisioned access point is removed from network, an unprovisioned
access point can then be provisioned.
This becomes particularly relevant when more than one wireless controller in the network, as there is
likely going to be more than 16 access points. In this case, make sure that the load is spread correctly
across the different controllers. This can be controlled by either assigning LMS (Local Master Switch) to
particular location codes, or to Access Points singularly.
4- Incorrect VLAN setup
Incorrect VLAN configuration can cause this issue under several circumstances, but the most notable are
the following:
the following:
Access Point in different VLAN than controller.
If the Access Point is connected to a port that is part of a VLAN that is not configured in the
Wireless Controller, the Access Point will not be able to communicate with the WFS709TP and
accordingly it will not be able to finish the booting procedure.
Wireless Controller, the Access Point will not be able to communicate with the WFS709TP and
accordingly it will not be able to finish the booting procedure.
Access Point unable to reach controller.
Even if all VLANs are configured in the controller, the Access Point may not be able to
communicate with the WFS709TP if the VLAN trunks are not configured properly.
The best way to test communication between the port where the Access Point will be connected
and the WFS709TP is to connect a computer to that port and ping the IP address of the controller.
If the ping is successful, it means that the Access Point should be able to reach the controller.
communicate with the WFS709TP if the VLAN trunks are not configured properly.
The best way to test communication between the port where the Access Point will be connected
and the WFS709TP is to connect a computer to that port and ping the IP address of the controller.
If the ping is successful, it means that the Access Point should be able to reach the controller.
Incorrect IP/DHCP information given to the AP in respect to the VLAN used by controller.
Misconfiguration of the DHCP server or incorrect static IP information can lead to this issue. If the
Access Points are in a different IP range than the one that the VLAN interface for the Wireless
Controller uses, they will be unable to communicate. Likewise, incorrect gateway or DNS settings
could lead to this same issue.
The particular VLAN IP and routing needs to be kept in consideration at the time of deployment.
Access Points are in a different IP range than the one that the VLAN interface for the Wireless
Controller uses, they will be unable to communicate. Likewise, incorrect gateway or DNS settings
could lead to this same issue.
The particular VLAN IP and routing needs to be kept in consideration at the time of deployment.