01-05-2021 11:49 PM - edited 07-05-2021 12:58 PM
We have two SSIDs. One of them is connected normally. Another guest SSID cannot connect. Prompt that this network cannot be connected.
The following is the log of debug with a client
WLC:3504
version:8.5.140
AP:2802i
01-06-2021 01:10 AM - edited 01-06-2021 01:11 AM
@ShengxiangZhang67519 wrote:
*DHCP Socket Task: Jan 06 07:21:54.173: 20:68:9d:86:44:6f DHCP chaddr: 20:68:9d:86:44:6f *DHCP Socket Task: Jan 06 07:21:54.173: 20:68:9d:86:44:6f DHCP ciaddr: 0.0.0.0, yiaddr: 10.204.20.106 *DHCP Socket Task: Jan 06 07:21:54.173: 20:68:9d:86:44:6f DHCP siaddr: 0.0.0.0, giaddr: 0.0.0.0 *DHCP Socket Task: Jan 06 07:21:54.173: 20:68:9d:86:44:6f DHCP server id: 1.1.1.1 rcvd server id: 10.204.20.254
I can see the wireless client getting a valid IP address, however, gateway IP address is BLANK/missing.
01-06-2021 01:58 AM
01-06-2021 02:01 AM
I am not sure if it is because of this bug: CSCvk36887.
I configured:config client deauthenticate ,according to the method of this bug. But still useless
01-06-2021 02:17 AM
@ShengxiangZhang67519 wrote:
No, the following logs are connected to normal SSID logs. I re-upload a copy
Is that all you can provide? A debug worth <1 second?
01-06-2021 05:27 PM
01-06-2021 04:59 AM
- Use this tool to have your debugs analyzed , as Leo said the second one is a bit short : https://cway.cisco.com/wireless-debug-analyzer/
Here is the output for your first file which looks normal at first glance :
TimeTaskTranslated
Jan 06 07:21:53.931 | *apfMsConnTask_1 | Client made new Association to AP/BSSID BSSID dc:8c:37:86:28:22 AP COFFE |
Jan 06 07:21:53.932 | *apfMsConnTask_1 | The WLC/AP has found from client association request Information Element that claims PMKID Caching support |
Jan 06 07:21:53.932 | *apfMsConnTask_1 | The Reassociation Request from the client comes with 0 PMKID |
Jan 06 07:21:53.932 | *apfMsConnTask_1 | The Reassociation Request from the client comes with 0 PMKID |
Jan 06 07:21:53.932 | *apfMsConnTask_1 | Client is entering the 802.1x or PSK Authentication state |
Jan 06 07:21:53.932 | *apfMsConnTask_1 | Client has successfully cleared AP association phase |
Jan 06 07:21:53.932 | *apfMsConnTask_1 | WLC/AP is sending an Association Response to the client with status code 0 = Successful association |
Jan 06 07:21:53.935 | *Dot1x_NW_MsgTask_7 | Client will be required to Reauthenticate in 1800 seconds |
Jan 06 07:21:53.935 | *Dot1x_NW_MsgTask_7 | WLC/AP is sending EAP-Identity-Request to the client |
Jan 06 07:21:53.965 | *Dot1x_NW_MsgTask_7 | WLC/AP is sending EAP-Identity-Request to the client |
Jan 06 07:21:53.988 | *Dot1x_NW_MsgTask_7 | Client sent EAP-Identity-Response to WLC/AP |
Jan 06 07:21:54.112 | *Dot1x_NW_MsgTask_7 | RADIUS Server permitted access |
Jan 06 07:21:54.113 | *Dot1x_NW_MsgTask_7 | Client will be required to Reauthenticate in 1800 seconds |
Jan 06 07:21:54.113 | *Dot1x_NW_MsgTask_7 | 4-Way PTK Handshake, Sending M1 |
Jan 06 07:21:54.140 | *Dot1x_NW_MsgTask_7 | 4-Way PTK Handshake, Received M2 |
Jan 06 07:21:54.141 | *Dot1x_NW_MsgTask_7 | 4-Way PTK Handshake, Sending M3 |
Jan 06 07:21:54.149 | *Dot1x_NW_MsgTask_7 | 4-Way PTK Handshake, Received M4 |
Jan 06 07:21:54.149 | *Dot1x_NW_MsgTask_7 | Client has completed PSK Dot1x or WEP authentication phase |
Jan 06 07:21:54.150 | *Dot1x_NW_MsgTask_7 | Client has entered DHCP Required state |
Jan 06 07:21:54.170 | *dtlArpTask | Client has entered RUN state |
Jan 06 07:21:54.171 | *dtlArpTask | Received DHCP ACK, assigning IP Address 10.204.20.106 |
Jan 06 07:21:54.172 | *DHCP Socket Task | Received DHCP request from client |
Jan 06 07:21:54.172 | *DHCP Socket Task | Sending DHCP Request to DHCP Server 10.204.20.254 through gateway 10.204.20.1 requesting 10.204.20.106 on VLAN 200 |
Jan 06 07:21:54.173 | *DHCP Socket Task | Received DHCP ACK from DHCP server |
01-06-2021 05:29 PM
01-06-2021 05:45 PM - edited 01-06-2021 05:52 PM
Kindly raise a TAC Case.
The debug is another <1 second debug output.
What happens if you run this command:
config client deauthenticate 20:68:9d:86:44:6f
01-06-2021 05:49 PM
I reopened a discussion
01-06-2021 06:37 PM
After configuring config client deauthenticate 20:68:9d:86:44:6f, there is no effect. The SSID still cannot connect. Tip: Unable to connect to this network
01-06-2021 06:56 PM - edited 01-06-2021 06:58 PM
20:68:9d:86:44:6f
What OS is this client running on? If Android, what exactly is it running on?
Is this happening to one wireless clients or multiple wireless clients?
Can the wireless client(s) authenticate to an SSID with Open authentication &/or PSK?
01-06-2021 07:07 PM
There are various clients, windows, android, ios, etc.
01-06-2021 07:34 PM
@ShengxiangZhang67519 wrote:
There are various clients, windows, android, ios, etc.
Can the wireless client(s) authenticate to an SSID with Open authentication &/or PSK?
01-06-2021 07:40 PM
I have set up open authentication, but I still can’t connect to this network.And there are three or four others who can connect.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide