03-30-2023 11:46 AM
With the error:
Client state transition: S_CO_DELETE_IN_PROGRESS WLC9800
{wncd_x_R0-6}{1}: [client-orch-state] [25366]: (note): MAC: 0030.4449.8a24 Client state transition: S_CO_DELETE_IN_PROGRESS -> S_CO_DELETED
I don't understand why clients are connecting fine on one ap but not the other?
03-30-2023 11:48 PM
- You can debug/monitor client behavior on the particular AP with :
show ap client-trace events mac <CLIENT MAC>
(this command must be executed on the involved access point); use these tools too for client debugging : https://logadvisor.cisco.com/logadvisor/wireless/9800/9800ClientConnectivity
Last but not least have a checkup of the 9800 CL configuration with the CLI command show tech wireless , have the output analyzed by https://cway.cisco.com/wireless-config-analyzer/
M.
03-31-2023 12:08 AM
Are the AP nearby? what AP Models and what IOS code running?
some troubleshooting tips to get more Logs :
03-31-2023 12:18 AM
Have you checked if APs have same configuration and not wrongly spelled Tags on the unable-to-receive-connections one?
03-31-2023 02:21 AM
Hi
Kindly check the radio operational sate of AP, what are the model of AP.
Good Luck
03-31-2023 12:09 PM
Most importantly:
- what model of AP?
- what version of software?
04-03-2023 05:05 AM
The WLC is 9800 on 17.03.06. The APs are 9120 AXE-B. The configuration between the two is the same. The client trying to reach these APs are Cradlepoints that present a certificate. They connect to only one ap, and when that ap is admin down, they won't connect with the other AP.
04-03-2023 05:51 AM
@chtucci Have you already executed the tasks mentioned in my first reply ?
M.
04-03-2023 05:53 AM
Calling for them to test today, and I'll try then.
04-03-2023 09:47 AM
I tried using the config analyzer but no output occurred. I posted some more details to the main thread about testing though.
04-03-2023 10:05 AM
>...I tried using the config analyzer but no output occurred.
- Please note : use CLI show tech wireless , for WirelessAnalyzer , not simple show tech ,
M.
04-03-2023 10:14 AM
Yessir, I sure did. Used that full command. It does dump a tremendous number of lines though.
04-03-2023 10:23 AM
>..It does dump a tremendous number of lines though.
- How do you mean , can you post a (beginning) part of this output e.g. ?
M.
04-03-2023 10:25 AM
It looks like this:
Memory Statistics:
Total Tx Memory Alloc Failure = 0
Largest Message Size = 0
RPC Statistics:
Total RPC Requests Out = 0 Total RPC Requests In = 0
Total RPC Replies Out = 0 Total RPC Replies In = 0
No RPC Request for Rx RPC Reply = 0 RPC Timeouts = 0
Message Bundling Statistics:
Total Rx Bundled Messages = 0 Total Rx Bundled SubMessages = 0
Total Rx NonBundled Messages = 0
Total Rx Bundled Errors = 0
10000.E unicast FIB Master: DFS.process_level.msgs
port_index = 0 seat_id = 0x20000 last sent = 0 last heard = 19070
No of msgs requested = 150142 Msgs returned = 150142
Priority = 0 Mixed priority messages = 0
Total Reassembled messages = 0 Total Fragments received = 0
Total fragments dropped = 0
Sequence Window Info:
seq-window size = 128 number of messages in window = 0
maximum out-of-seq received = 0 maximum pending in window = 0
number of messages dropped = 0 number of window resets = 0
Basic Statistics:
Total Tx Frames = 149506 Total Rx Frames = 150142
Total Tx Frames Sent = 0 Total Rx Frames Delivered = 150142
Total Tx via Platform Drivers = 149506 Total Rx via Platform Drivers = -
Total Tx Acknowledgements = 149506 Total Rx Acknowledgements = 0
Total Tx Frames Dropped = 0 Total Rx Frames Dropped = 0
Last Tx Timestamp = 1w3d Last Rx Timestamp = 1w3d
Errors:
Total Tx Frame Driver Failures = 0 Total Tx Quiesced = 0
Total Tx Test Drops = 0 Total Tx Session Errors = 0
Total Tx Seat Errors = 0 Total Tx Send Errors = 0
Total Rx Duplicate Frames = 0 Total Rx Out of Sequence Frames = 0
Memory Statistics:
Total Tx Memory Alloc Failure = 0
Largest Message Size = 0
RPC Statistics:
Total RPC Requests Out = 0 Total RPC Requests In = 0
Total RPC Replies Out = 0 Total RPC Replies In = 0
No RPC Request for Rx RPC Reply = 0 RPC Timeouts = 0
Message Bundling Statistics:
Total Rx Bundled Messages = 0 Total Rx Bundled SubMessages = 0
Total Rx NonBundled Messages = 150142
Total Rx Bundled Errors = 0
10000.F unicast FIB Master: DFS.interrupt.msgs
port_index = 0 seat_id = 0x20000 last sent = 0 last heard = 30473
04-03-2023 10:34 AM
- You need to save the output of show tech wireless to a file , usually best is to activate a operator logging option such as with PuTTy when connecting to the controller , then you have the output automatically , then you edit the file after the session is finished so that only the output starts with the correct beginning of 'show tech wireless' and also additional stuff at the end from terminating the connection is removed , then you feed the obtained and feed output to : https://cway.cisco.com/wireless-config-analyzer , meaning upload the file and or drag it into the upload field that you see on the screen ,
M.
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