A wireless terminal at a certain location cannot be accessed.
- 0 Followed
- 0Collected ，844Browsed
Network Topology
NULL
Problem Description
In the process of troubleshooting the wireless terminal association failure, we need to follow the association process of the terminal in order to rank, and the idea of locating the wireless terminal association problem is: First, we need to pay attention to the scanning process, whether the hidden SSID method is used, and we need to check the settings of the terminal to ensure that the terminal can discover the wireless signal. Then, ensure that the authentication message interaction is successful, where the authentication is simply the interaction of authentication messages between the AP and STA, not the 802.1X or PSK and other advanced authentication we often talk about. Finally, check the association process, the common association success rate is also closely related to this process, the successful association means that the terminal and AP can send and receive normal messages, and then can carry out encryption negotiation or other advanced authentication.
Process Analysis
1) By debug on the AC, the AC receives the authentication request message from the terminal and also sends the authentication response message, but does not receive the following Received association request in the Auth state. The debug on the AP shows that the AP has been sending messages to the AC, and combined with the debug on the AC, we can determine that the authentication response is lost in the intermediate link.
a) Debug on AC:
|
[H3C]*Dec 24 10:26:09:340 2021 H3C STAMGR/7/FSM: [APID: 33] [MAC: b0cc-fe6d-cc55, BSSID: 38a9-1c3c-1b91] Received authentication request in the Unauth state. *Dec 24 10:26:09:340 2021 H3C STAMGR/7/Event: [APID: 33] [MAC: b0cc-fe6d-cc55, BSSID: 38a9-1c3c-1b91] Processed authentication request Processed authentication request successfully, and sent authentication response. *Dec 24 10:26:09:340 2021 H3C STAMGR/7/Timer: [APID: 33] [MAC: b0cc-fe6d-cc55, BSSID: 38a9-1c3c-1b91] Created state timer. *Dec 24 10:26:09:340 2021 H3C STAMGR/7/FSM: [APID: 33] [MAC: b0cc-fe6d-cc55, BSSID: 38a9-1c3c-1b91] Changed the client's state from Unauth to Auth.
|
b) debug on AP
|
*Dec 3 09:46:33:572 2021 38a9-1c3b-4500 CWC/7/SND_PKT: Sent WTP event request with SeqNum 54 to AC 192.168.30.1:5246. *Dec 3 09:46:33:572 2021 38a9- 1c3b-4500 CWC/7/SND_PKT: Verbose info for WTP event request sent to AC 192.168.30.1:5246, length=1343.
|
2) Do traffic statistics on all the devices that pass through in the middle, found that there is an abnormality in the statistics of messages on the poe, the normal terminal associated messages from AP1 up, but the switch sent the AC back packets to another AP2, after checking the core switch configured static arp, arp static 192.168.50.21 38a9-1c3b-c4e0 50 GigabitEthernet2/0/28, its configured IP address and mac address do not correspond, resulting in the core switch in the forwarding of packets abnormal, the packet back to the wrong device.
Solution
Delete the static arp configuration on the core device