If the boot module is newer than v1.13, please upgrade the FW to the
2.23 patch 8.
2 Unstable network connection between controller and managed AP
Ping test between controller and managed AP via SSH to check the
network connection on both directions is stable (no long latency or ping
drop).
AP ping to controller and trace route of AC.
Figure 113
Tera Term >
AP > Router >
ping <AC-IP>
According the result of trace route, you will know which path cost the more
time for response.
Figure 114
Tera Term >
AP> Router >
traceroute <AC-I
P>
Controller ping to AP
Figure 115
Tera Term >
NXC > Router
> ping <AP-
IP>
Note: By default, the maximum number of AP for FW upgrading is 10 units at
one time. If the first group (maximum 10 APs) upgrades firmware failed, the
AP will be released and upgraded again on the next group.
3 Upgrade process could not pass through NAT if Controller or managed AP is
in different network.
Ensure that the firewall does not block CAPWAP port. (The CAPWAP default
port is 5246.)
4 Information collection and report the issue to the HQ.
Capture the related logs file from controller and managed AP.
Collect log files of controller by GUI
Capture the entire category to provide RD completed information.
Figure 116 MAINTENANCE > Diagnostics > Diagnostics > Collect on
Controller > Collect Now.
To Next Page
Loading...
