Cisco AP AIR-AP1852I-E-K9 - BUG?

Hello,
I am looking for solution how to solve problem with Cisco AP - AIR-AP1852I-E-K9, which for some reason disconnect from the WLC and cannot register again.
I tried to reset it on factory - but still.

Version of WLC

AIR-CT5520-K9

8.2.166.0

Here is a part of Console output

[*03/30/2023 05:55:50.9172] Discovery response from MWAR ''running version 0.0.0.0 is rejected.

[*03/30/2023 05:55:50.9172] Failed to decode discovery response.

[*03/30/2023 05:55:50.9172] CAPWAP SM handler: Failed to process message type 2 state 2.

[*03/30/2023 05:55:50.9172] Failed to handle capwap control message from controller - status 4

[*03/30/2023 05:55:50.9172] Failed to process unencrypted capwap packet from 10.1.2.251

[*03/30/2023 05:55:50.9172] Failed to send capwap message 0 to the state machine. Packet already freed.

[*03/30/2023 05:55:50.9172] wtpProcessPacketFromSocket returned 4

[*03/30/2023 05:56:00.4142] CAPWAP State: Discovery

[*03/30/2023 05:56:00.4142] Discovery Request sent to 10.1.2.251, discovery type STATIC_CONFIG(1)

[*03/30/2023 05:56:00.4142] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)

[*03/30/2023 05:56:00.4142] Discovery Response from 10.1.2.251

[*03/30/2023 05:56:00.4142]

[*03/30/2023 05:56:00.4142] This AP model is supported by controller version newer than 7.0.0.0!

[*03/30/2023 05:56:00.4142]

[*03/30/2023 05:56:00.4142] Discovery response from MWAR ''running version 0.0.0.0 is rejected.

[*03/30/2023 05:56:00.4142] Failed to decode discovery response.

[*03/30/2023 05:56:00.4142] CAPWAP SM handler: Failed to process message type 2 state 2.

[*03/30/2023 05:56:00.4142] Failed to handle capwap control message from controller - status 4

[*03/30/2023 05:56:00.4142] Failed to process unencrypted capwap packet from 10.1.2.251

[*03/30/2023 05:56:00.4142] Failed to send capwap message 0 to the state machine. Packet already freed.

[*03/30/2023 05:56:00.4142] wtpProcessPacketFromSocket returned 4

[*03/30/2023 05:56:00.4142] Discovery Response from 10.1.2.251

[*03/30/2023 05:56:00.4142]

[*03/30/2023 05:56:00.4142] This AP model is supported by controller version newer than 7.0.0.0!

[*03/30/2023 05:56:00.4142]

[*03/30/2023 05:56:00.4142] Discovery response from MWAR ''running version 0.0.0.0 is rejected.

[*03/30/2023 05:56:00.4142] Failed to decode discovery response.

[*03/30/2023 05:56:00.4142] CAPWAP SM handler: Failed to process message type 2 state 2.

[*03/30/2023 05:56:00.4142] Failed to handle capwap control message from controller - status 4

[*03/30/2023 05:56:00.4142] Failed to process unencrypted capwap packet from 10.1.2.251

[*03/30/2023 05:56:00.4142] Failed to send capwap message 0 to the state machine. Packet already freed.

[*03/30/2023 05:56:00.4142] wtpProcessPacketFromSocket returned 4

Mar 30 05:56:01 apsw_watchdog: secs_no_lighttpd: 0

Mar 30 05:56:01 apsw_watchdog: secs_no_slowfcgi: 0

Mar 30 05:56:01 apsw_watchdog: secs_no_sync_log: 0

Mar 30 05:56:01 apsw_watchdog: secs_no_syslogd: 0

Mar 30 05:56:01 apsw_watchdog: secs_no_hostapd: 0

Mar 30 05:56:01 apsw_watchdog: secs_no_gateway: 0

Mar 30 05:56:01 apsw_watchdog: secs_no_dnsmasq: 0

Mar 30 05:56:01 apsw_watchdog: secs_no_xmit_mon0: 0

Mar 30 05:56:01 apsw_watchdog: secs_no_xmit_mon1: 0

Mar 30 05:56:01 apsw_watchdog: secs_no_xmit_mon2: 0

Writing reload timestamp (Thu Mar 30 05:56:06 UTC 2023) to disk

[03/30/2023 05:56:07.7919] UBIFS: un-mount UBI device 0, volume 3

The system is going down NOW!

Sent SIGTERM to all processes

[*03/30/2023 05:56:07.9219] device capwap0 left promiscuous mode

[*03/30/2023 05:56:07.9619] device capwap1 left promiscuous mode

Sent SIGKILL to all processes

Requesting system reboot16]

[03/30/2023 05:56:09.9113] Restarting system.

[03/30/2023 05:56:09.9513] Going down for restart now

Find more posts tagged with

Comments

itdept

As per the message, "This AP model is supported by controller version newer than 7.0.0.0!" Have you tried updating to version 8.1 +

FilipV

Yes, I tried to update WLC to 8.10.171, temporary, just to see if this AP will join WLC with new version.
Result is same - AP 1852 not joining the controller with 8.10.171 version.

JDMurray

Per Cisco via GPT4:

The issue of an AP (Access Point) disconnecting and not re-registering with the WLC (Wireless LAN Controller) can stem from various sources. Here are some general troubleshooting steps you can take to resolve the problem:

1. **Check for Basic Connectivity:**
   - Ensure that the AP is powered on.
   - Check the cable connections between the AP and the switch or router.
   - Verify that the AP has an IP address on the correct VLAN and subnet.
   - Test basic connectivity by pinging the AP from the WLC.

2. **Investigate Logs:**
   - Look into the logs on the WLC and the AP to find any error messages or warnings that may provide clues to the issue.

3. **Update or Reapply Firmware:**
   - Verify that the AP is running the correct firmware version, compatible with your WLC version.
   - If everything seems fine, try reapplying the firmware.

4. **Review Configuration:**
   - Confirm that the configuration on both the AP and WLC is correct, especially security settings and IP addressing.
   - Ensure that the AP is properly joined to the correct WLC and that there are no conflicts with other devices.

5. **Examine the Security Settings:**
   - Verify that there are no issues with certificates, authentication methods, or other security-related settings that might prevent registration.

6. **Reset to Factory Defaults (if needed):**
   - If you are still unable to resolve the issue, you may consider resetting the AP to its factory default settings and reconfiguring it.

7. **Isolate the Issue:**
   - Try connecting the AP to a different WLC to see if the issue is related to the specific WLC or the AP itself.

8. **Check for Interference or Other Network Issues:**
   - Investigate if there are any nearby electronic devices causing interference.
   - Check if other devices on the network are functioning as expected, or if there might be a broader network issue.

9. **Contact Cisco Support:**
   - If all else fails, consider contacting Cisco's technical support. They have the tools and expertise to help diagnose and fix the issue.

Please keep in mind that some of these troubleshooting steps might require a certain level of expertise in network administration. If you are not comfortable with some of these steps, it might be a good idea to engage with a network professional or Cisco's support team.

Remember, it's always good to have a backup of the current configuration and any relevant data before making major changes or updates to avoid any potential data loss.

DCD

What switch model are you connecting too?

FilipV

SG300-52P

SW version 1.4.11.5 ( date 08-Apr-2020 time 13:49:34 )

Boot version 1.3.5.06 ( date 21-Jul-2013 time 15:12:10 )

HW version V04

DCD

I could not find the power rating on the ports for the SG300-52P but check the port power rating against the AP need power requirements.

MaryGamble

Have you found the solution?

FilipV

Power Rating is not problem.

Switches support 802.3at PoE+, 802.3af, and Cisco pre-standard (legacy) PoE. Maximum power of 30.0W to any 10/100 or Gigabit Ethernet port for PoE+ supported devices and 15.4W for PoE supported devices, until the PoE budget for the switch is reached

AP require 20.9W and power options.

● 802.3at

● Enhanced PoE

● Cisco power injector, AIR-PWRINJ4=

● Cisco local power supply, AIR-PWR-C=

● Cisco power injector, AIR-PWRINJ5= ( Note: this injector supports 802.3af only)

● 802.3af

DCD

Can you provide the AP show running-config and show version