After the removal of the hierarchical AC architecture at a site, the AP is normally online, but the wireless terminal cannot be online
- 0 Followed
- 0Collected ，881Browsed
Network Topology
NULL
Problem Description
A local office originally used a hierarchical AC architecture, and the local AC used the S5560 converged AC. now it intends to remove the hierarchical AC network and replace it with the traditional network of AC plus fit ap, at this time the S5560 is only used as an access switch.
After removing the layered AC network, I found that the AP could be online normally, but the wireless terminal could not be accessed normally.
The service template has no authentication and only PSK encryption.
Process Analysis
The troubleshooting process is as follows:
1) Confirm that the relevant configuration of the hierarchical AC networking has been completely removed
Delete the following configuration on the Central AC
|
# wlan ap ap1 model WA5620i-ACN control-address enable control-address ip x.x.x.x # wlan local-ac name wlan local-ac name ac1 model S5560 serial-id xxxxxxxxxxxxxx Delete the following configuration on the Local AC #wlan local-ac enable wlan local-ac enable wlan local-ac capwap source-vlan x # wlan central-ac ip x.x.x.x wlan central-ac ip x.x.x.x
|
2) The AP can be online normally but the wireless terminal access is abnormal, suspecting that there is a problem with the capwap data tunnel message interaction
Debug on the AP and find that after the AP sends a keep-alive request, it does not receive a
reply from the AC.
|
<AP>debugging wlan capwap packet data *Jul 30 13:18:14:119 2021 xxh-3f-dianyuanshi CWC/7/DATA: Sent data channel keep-alive message to AC at 10.100.100.1:5247. *Jul 30 13:18:24:118 2021 xxh-3f-dianyuanshi CWC/7/DATA: Sent data channel keep-alive message to AC at 10.100.100.1:5246. *Jul 30 13:18:34:118 2021 xxh-3f-dianyuanshi CWC/7/DATA: Sent data channel keep-alive message to AC at 10.100.100.1:5246. *Jul 30 13:18:44:118 2021 xxh-3f-dianyuanshi CWC/7/DATA: Sent data channel keep-alive message to AC at 10.100.100.1:5246. *Jul 30 13:18:54:118 2021 xxh-3f-dianyuanshi CWC/7/DATA: Sent data channel keep-alive message to AC at 10.100.100.1:5246. *Jul 30 13:19:04:118 2021 xxh-3f-dianyuanshi CWC/7/DATA: Sent data channel keep-alive message to AC at 10.100.100.1:5246.
|
At this time, we can see that the number of Keep Alive messages on the AC side is not increasing, that is, the Keep Alive messages sent by the AP are not delivered to the AC, and are suspected to be intercepted halfway
|
[AC-probe]dis sys int wlan ap mac-address 1111-1111-1111 capwap packet-statistics | inc Keep Data Channel Keep Alive Request/Response: 1629/1629 [AC-probe]dis sys int wlan ap mac-address 1111-1111-1111 capwap packet-statistics | inc Keep Data Channel Keep Alive Request/Response: 1629/1629 [AC-probe]dis sys int wlan ap mac-address 1111-1111-1111 capwap packet-statistics | inc Keep Data Channel Keep Alive Request/Response: 1629/1629 [AC-probe]dis sys int wlan ap mac-address 1111-1111-1111 capwap packet-statistics | inc Keep Data Channel Keep Alive Request/Response: 1629/1629
|
3) When viewing remotely, I happened to find that after starting the Layer 3 interface of the wireless service vlan on the S5560, the wireless service could be restored and the wireless terminal could come online normally. At this time, the AP and AC side information was found to be normal for message interaction.
AP-side data retention messages are going and coming back:
|
<AP>debugging wlan capwap packet data *Jul 30 13:12:22:761 2021 xxh-2f-beicezoulang CWC/7/DATA: Sent data channel keep-alive message to AC at 10.100.100.1:5246. *Jul 30 13:12:22:763 2021 xxh-2f-beicezoulang CWC/7/DATA: Received Data Channel Keep-Alive message from AC. *Jul 30 13:12:32:761 2021 xxh-2f-beicezoulang CWC/7/DATA: Sent data channel keep-alive message to AC at 10.100.100.1:5246. *Jul 30 13:12:32:763 2021 xxh-2f-beicezoulang CWC/7/DATA: Received Data Channel Keep-Alive message from AC. *Jul 30 13:12:42:761 2021 xxh-2f-beicezoulang CWC/7/DATA: Sent data channel keep-alive message to AC at 10.100.100.1:5246. *Jul 30 13:12:42:762 2021 xxh-2f-beicezoulang CWC/7/DATA: Received Data Channel Keep-Alive message from AC. *Jul 30 13:12:52:761 2021 xxh-2f-beicezoulang CWC/7/DATA: Sent data channel keep-alive message to AC at 10.100.100.1:5246.
|
At this time, the capwap packets sent and received on the AC side are not growing, that is, the Keep Alive packets sent by the AP are not delivered to the AC, and are suspected to be intercepted halfway
|
[AC-probe]dis sys int wlan ap mac-address 1111-1111-1111 capwap packet-statistics | inc Keep Data Channel Keep Alive Request/Response: 1629/1629 [AC-probe]dis sys int wlan ap mac-address 1111-1111-1111 capwap packet-statistics | inc Keep Data Channel Keep Alive Request/Response: 1629/1629 [AC-probe]dis sys int wlan ap mac-address 1111-1111-1111 capwap packet-statistics | inc Keep Data Channel Keep Alive Request/Response: 1629/1629 [AC-probe]dis sys int wlan ap mac-address 1111-1111-1111 capwap packet-statistics | inc Keep Data Channel Keep Alive Request/Response: 1629/1629
|
3 When viewing remotely, I happened to find that after starting the Layer 3 interface of the wireless service vlan on the S5560, the wireless service could be restored and the wireless terminal could come online normally. At this time, the AP and AC side information was found to be normal for message interaction.
AP-side data retention messages are going and coming back:
|
<AP>debugging wlan capwap packet data *Jul 30 13:12:22:761 2021 xxh-2f-beicezoulang CWC/7/DATA: Sent data channel keep-alive message to AC at 10.100.100.1:5246. *Jul 30 13:12:22:763 2021 xxh-2f-beicezoulang CWC/7/DATA: Received Data Channel Keep-Alive message from AC. *Jul 30 13:12:32:761 2021 xxh-2f-beicezoulang CWC/7/DATA: Sent data channel keep-alive message to AC at 10.100.100.1:5246. *Jul 30 13:12:32:763 2021 xxh-2f-beicezoulang CWC/7/DATA: Received Data Channel Keep-Alive message from AC. *Jul 30 13:12:42:761 2021 xxh-2f-beicezoulang CWC/7/DATA: Sent data channel keep-alive message to AC at 10.100.100.1:5246. *Jul 30 13:12:42:762 2021 xxh-2f-beicezoulang CWC/7/DATA: Received Data Channel Keep-Alive message from AC. *Jul 30 13:12:52:761 2021 xxh-2f-beicezoulang CWC/7/DATA: Sent data channel keep-alive message to AC at 10.100.100.1:5246. *Jul 30 13:12:52:762 2021 xxh-2f-beicezoulang CWC/7/DATA: Received Data Channel Keep-Alive message from AC.
|
AC-side data keep-alive messages are continuing to grow in pairs:
|
[AC-probe]dis sys int wlan ap mac-address 1111-1111-1111 capwap packet-statistics | inc Keep Data Channel Keep Alive Request/Response: 1629/1629 [AC-probe]dis sys int wlan ap mac-address 1111-1111-1111 capwap packet-statistics | inc Keep Data Channel Keep Alive Request/Response: 1629/1629 [AC-probe]dis sys int wlan ap mac-address 1111-1111-1111 capwap packet-statistics | inc Keep Data Channel Keep Alive Request/Response: 1630/1630 [AC-probe]dis sys int wlan ap mac-address 1111-1111-1111 capwap packet-statistics | inc Keep Data Channel Keep Alive Request/Response: 1630/1630 [AC-probe]dis sys int wlan ap mac-address 1111-1111-1111 capwap packet-statistics | inc Keep Data Channel Keep Alive Request/Response: 1630/1630 [AC-probe]dis sys int wlan ap mac-address 1111-1111-1111 capwap packet-statistics | inc Keep Data Channel Keep Alive Request/Response: 1631/1631 [AC-probe]dis sys int wlan ap mac-address 1111-1111-1111 capwap packet-statistics | inc Keep Data Channel Keep Alive Request/Response: 1631/1631
|
4) This leads to the suspicion that the failure is related to the S5560. Consider uninstalling the AC feature packets on the S5560.
After uninstalling the feature package, the problem is solved and the wireless terminal is connected online normally.
Solution
Uninstall the AC feature package on the converged AC and the problem is solved