The barcode device lost connection after a few minutes

[ntlong3]

We are experiencing loss of connection of Barcode devices after migrating wlc AireOS to C9800.

I've tried using only 2.4G, disabling FT, disabling Clean Air, changing session time and idle time but it still doesn't work.

Please help me.

Thanks.

[Leo Laohoo]

What is the firmware of the controller?

What is the model of the APs?

Does the scanner support 5.0 Ghz?

[ntlong3]

Controller firmware 17.6.4

APs model: 2802E

I want to add some more information:
- We have not yet transferred all APs to the new WLC C9800, which means they have the same SSID name on 2 controllers running in parallel.
- Barcode devices are configured with static IP addresses directly on the device

[Mark Elsen]

  >... We have not yet transferred all APs to the new WLC C9800, which means they have the same SSID name on 2 controllers running in parallel.
       This is not recommended  and may lead to trouble , consider  moving to single based WLC C9800 setup ASAP.

 M.

[Leo Laohoo]

---

@ntlong3 wrote:
- We have not yet transferred all APs to the new WLC C9800, which means they have the same SSID name on 2 controllers running in parallel.

---

Are both WLC in the same Wireless Mobility Group?

[ntlong3]

No, we are planning to replace the old WLC AireOS device, and we are experiencing this issue when migrating some APs to the new WLC C9800 for testing.

[Mark Elsen]

          >...- Barcode devices are configured with static IP addresses directly on the device
 Added reply ; consider moving to DHCP for wireless clients as it is more common and  will work better on C9800 deployments (too)

 M,

[Mark Elsen]

 - Debug problematic clients according to https://logadvisor.cisco.com/logadvisor/wireless/9800/9800ClientConnectivity 
   You can have client debugs (so called RadioActive Traces) analyzed with : https://cway.cisco.com/tools/WirelessDebugAnalyzer/

 - Use an advisory software version on the C9800 such as 17.9.4a

 - Have a checkup of the C9800 with the CLI command show tech wireless and feed the output into Wireless Config Analyzer
                                                                                   This procedure should be considered mandatory

 M.

[ntlong3]

Thanks for your help.

 I've done the debugging and analysis as you instructed, but I still haven't found a solution.
Can you check the debugging information in the file below and help me what to do next?

[Mark Elsen]

      >...I've done the debugging and analysis as you instructed, but I still haven't found a solution.
 Below you will find the result of the debugTrace when analyzed with Wireless Debug Analyzer

 Remember to use the WirelessAnalyzer procedure too as outlined in my initial reply with the CLI command show tech wireless and feed the output into : Wireless Config Analyzer
                                                                                 This is very important!

                               debugTrace when analyzed with Wireless Debug Analyzer

TimeTaskTranslated

Connection attempt #1
Connection attempt #2
2024/01/02 09:50:35.151	client-orch-sm	Client made a new Association to an AP/BSSID: BSSID c4b2.39a0.de21, old BSSID bc26.c7aa.b501, WLAN HVN-LET, Slot 0 AP c4b2.39a0.de20, VPC-CAP-R50-AF3T7-213
2024/01/02 09:50:35.152	dot11	Association success for client, assigned AID is: 1
2024/01/02 09:50:35.152	client-orch-sm	Client started layer 2 authentication (either dot1X or PSK)
2024/01/02 09:50:35.178	client-keymgmt	Sent M1 for EAPOL 4-Way Handshake
2024/01/02 09:50:35.276	client-keymgmt	Received and validated M2 for EAPOL 4-Way Handshake
2024/01/02 09:50:35.277	client-keymgmt	Sent M3 for EAPOL 4-Way Handshake
2024/01/02 09:50:35.281	client-keymgmt	Received and validated M4 for EAPOL 4-Way Handshake
2024/01/02 09:50:35.281	client-keymgmt	Negotiated the following encryption mechanism: AKM:PSK Cipher:CCMP WPA Version: WPA2
2024/01/02 09:50:35.282	client-auth	Client successfully completed Pre-shared Key authentication. Assigned VLAN: 29
2024/01/02 09:50:35.282	client-orch-sm	Client passed layer 2 authentication
2024/01/02 09:50:35.282	client-orch-state	Starting Mobility Anchor discovery for client
2024/01/02 09:50:35.282	client-orch-state	Entering IP learn state
2024/01/02 09:50:35.283	client-orch-sm	IP Learn state completed, IP information discovered through: IPLEARN_METHOD_ARP
2024/01/02 09:50:35.283	client-orch-state	Client reached RUN state, connection completed.
2024/01/02 09:50:35.826	client-iplearn
2024/01/02 09:50:35.827	client-iplearn
2024/01/02 09:53:29.153	client-orch-sm	Controller initiated client deletion with code: CO_CLIENT_DELETE_REASON_BSSID_DOWN. Explanation: Triggered by configuration changes, for example WLAN or Policy profile modifications. Actions: None required
2024/01/02 09:53:29.154	dot11	Disassociation packet sent with code status: 252, interpretation: Multiple triggers
Connection attempt #3
2024/01/02 09:53:49.155	client-orch-sm	Client made a new Association to an AP/BSSID: BSSID bc26.c7aa.b501, WLAN HVN-LET, Slot 0 AP bc26.c7aa.b500, VPC2-CAP-R55-AEAF2-93
2024/01/02 09:53:49.156	dot11	Association success for client, assigned AID is: 25
2024/01/02 09:53:49.156	client-orch-sm	Client started layer 2 authentication (either dot1X or PSK)
2024/01/02 09:53:49.161	client-keymgmt	Sent M1 for EAPOL 4-Way Handshake
2024/01/02 09:53:49.165	client-keymgmt	Received and validated M2 for EAPOL 4-Way Handshake
2024/01/02 09:53:49.165	client-keymgmt	Sent M3 for EAPOL 4-Way Handshake
2024/01/02 09:53:49.169	client-keymgmt	Received and validated M4 for EAPOL 4-Way Handshake
2024/01/02 09:53:49.169	client-keymgmt	Negotiated the following encryption mechanism: AKM:PSK Cipher:CCMP WPA Version: WPA2
2024/01/02 09:53:49.169	client-auth	Client successfully completed Pre-shared Key authentication. Assigned VLAN: 29
2024/01/02 09:53:49.169	client-orch-sm	Client passed layer 2 authentication
2024/01/02 09:53:49.169	client-orch-state	Starting Mobility Anchor discovery for client
2024/01/02 09:53:49.171	client-orch-state	Entering IP learn state
2024/01/02 09:53:49.724	client-iplearn
2024/01/02 09:53:49.726	client-iplearn
2024/01/02 09:55:49.171	client-orch-sm	Controller initiated client deletion with code: CO_CLIENT_DELETE_REASON_IPLEARN_CONNECT_TIMEOUT. Explanation: Controller did not learn client IP address in the allowed time. Actions: Check DHCP server and client IP configuration. Validate if DHCP required is set and client is performing DHCP negotiation. If all is correct, collect RA traces and EPC
2024/01/02 09:55:49.172	dot11	Disassociation packet sent with code status: 108

[ntlong3]

I migrated the APs back to the old WLC AireOS system.

Can I still Show tech wireless on the new WLC C9800 to get information or does it have to have APs and Clients?

[Mark Elsen]

       >....Can I still Show tech wireless on the new WLC C9800 to get information or does it have to have APs and Clients?
  - Yes , it is always good practice to use the mentioned WirelessAnalyzer procedure with show tech wireless , before production use of the C9800 , (can be used without APs and clients perfectly)

 M.

[ntlong3]

As I added above, Barcode devices are configured with static IP addresses directly on the device, we don't use DHCP for them

[ntlong3]

Can you tell me more about the behavior of the WLC upgrade process?
As far as I know the APs will upgrade to the same version of WLC, but I don't know when it will do that and will it have to be reboot?

Are there any risks, for example, that it will not rejoin the WLC?

Thank you.

[Mark Elsen]

           >...but I don't know when it will do that and will it have to be reboot?
           >...Are there any risks, for example, that it will not rejoin the WLC?
 - The whole process is steered by the controller upgrade process and there are no risks for a joining failure after an upgrade in normal circumstances ; check the status of the APs after the upgrade according to : 
                       https://www.cisco.com/c/en/us/support/docs/wireless/catalyst-9800-series-wireless-controllers/217738-monitor-catalyst-9800-kpis-key-performa.html#anc4

   - There are special features available for  a smooth AP upgrade sequence  ; 
              https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/17-9/config-guide/b_wl_17_9_cg/m_predwnld_image_ap_ewlc.html?bookSearch=true

 M.