Repeated configuration of AP manual templates on the AC causes the AP to fail to go online
- 0 Followed
- 0Collected ，661Browsed
Network Topology
Normal
Problem Description
More than 1,000 APs under AC can go online normally, and only 3 APs cannot go online.
The AP can obtain an IP address normally, and can ping the AC, and the test of replacing the POE port shows that the AP still cannot go online.
Process Analysis
After preliminary investigation, the DHCP server address pool is sufficient and Option 43 is correctly configured, the wired link is in normal state, and the AC address specified by wlan ac ip xxx configured on the AP still cannot go online. And the PoE port replacement test of the AP is carried out, so the impact of the link problem is not considered for the time being.
Enable on the AP: debug wlan capwap all
Enable on AC: debug wlan capwap all mac-address H-H-H // MAC address of AP
debug wlan capwap error all
At the same time, in order to avoid printing too many logs on the AC, configure: terminal logging level alert // After debugging, you need to undo terminal logging level
After enabling it, it is observed on the AP side:
|
*Sep 7 00:06:54:990 2020 H3C CWC/7/RCV_PKT: Received discovery response with SeqNum 0 from AC at 172.16.132.10:5246. *Sep 7 00:06:54:990 2020 H3C CWC/7/RCV_PKT: Verbose info for discovery response from AC 172.16.132.10:5246, length=137.
|
// The hex string printed by debug is omitted here
It means that the AC has received the discovery request sent by the AP and responded with a discovery response, which has been received by the AP.
|
*Sep 7 00:06:56:996 2020 H3C CWC/7/TMR: Discovery Interval timer expired.uiAPID = 1. *Sep 7 00:06:56:996 2020 H3C CWC/7/EVENT: Discovered AC by method of IPv4 dhcp option successfully. *Sep 7 00:06:56:997 2020 H3C CWC/7/EVENT: AP selected AC IP 172.16.132.10 Priority 4 successfully. *Sep 7 00:06:56:999 2020 H3C CWC/7/FSM: Enter Join state. *Sep 7 00:06:57:009 2020 H3C CWC/7/EVENT: Fill join req.wtu=1.model=WA5530.wt drv info:[][0000-0000-0000].subslot=0.licensetype= 1. ret=0x40010001. *Sep 7 00:06:57:009 2020 H3C CWC/7/EVENT: Fill join req.ap=1.model=WA5530.licensetype=1.carry wt info is unnecessary. *Sep 7 00:06:57:010 2020 H3C CWC/7/SND_PKT: Sent join request with SeqNum 1 to AC 172.16.132.10:5246. *Sep 7 00:06:57:010 2020 H3C CWC/7/SND_PKT: Verbose info for join request sent to AC 172.16.132.10:5246, length=222.
|
// The hex string printed by debug is omitted here
Indicates that the AP initiates a join request to the AC
|
*Sep 7 00:06:57:013 2020 H3C CWC/7/RCV_PKT: Received join response with SeqNum 1 from AC at 172.16.132.10:5246. *Sep 7 00:06:57:013 2020 H3C CWC/7/RCV_PKT: Verbose info for join response from AC 172.16.132.10:5246, length=24. 00 10 02 00 00 00 00 00 00 00 00 04 01 00 0B 00 00 21 00 04 00 00 00 01
|
The AP received the join response request message from the AC, but it can be observed that the hex string content in it is very small, which is obviously much less than when the normal AP registers and goes online, which seems strange.
|
*Sep 7 00:06:57:019 2020 H3C CWC/7/ERROR: Failed to process Join Response because Result Code was failure.uiAPID=1,uiResultCode=1. *Sep 7 00:06:57:021 2020 H3C CWC/7/EVENT: Close capwap client udp port:11873 *Sep 7 00:06:57:021 2020 H3C CWC/7/FSM: [Tunnel ID: 1] Join -> Idle. *Sep 7 00:06:57:022 2020 H3C CWC/7/EVENT: CAPWAP tunnel to AC 172.16.132.10 went down. Reason: Failed to process response. *Sep 7 00:06:57:022 2020 H3C CWC/7/EVENT: [download-ipe] Reset online download ap-image flag. *Sep 7 00:06:57:031 2020 H3C CWC/7/FSM: Enter Idle state. *Sep 7 00:06:57:031 2020 H3C CWC/7/ERROR: pstAccb->bIsMaster is false *Sep 7 00:06:57:031 2020 H3C CWC/7/EVENT: Start ipv4 dhcp opt43 discover.
|
It can be seen here that the AP found an abnormality when processing the join response message returned by the AC, so it could not proceed to the subsequent steps. The AP status changed from join to idle, and then re-initiated the online request.
It can be judged that the join process of the AP going online is abnormal.
However, looking back at previous cases, no similar errors can be found for reference.
Solution
Since the AP uses a manual template configuration to go online, after carefully checking the configuration of the AC, it is found that two templates have been accidentally configured for the same AP on the AC, namely:
|
wlan ap ap1 model WA6330 vlan 1 serial-id xxxxxxxxxxxxxxxxxxxx wlan ap ap2 model WA6330 vlan 1 mac-address 441a-fa32-27f0 |
In fact, ap1 and ap2 are the same AP, and the templates configured by SN and mac-address were used in the configuration, causing the request sent by the AP to match the two manual templates on the AC at the same time, resulting in a processing error and causing Unable to go online normally.
One of the manual profiles was deleted, and the AP went online normally.
It should be noted that you can use the method of specifying the SN or specifying the mac-address to configure the manual template of the AP on the AC. However, it is necessary to use the same one as much as possible to avoid configuring two manual templates for the same AP.