cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2527
Views
10
Helpful
19
Replies

AIR-CAP1532I-E-K9 unable to join WLC5508 2022

tanner.zaitt
Level 3
Level 3

Hi Cisco  Community.

I have an issue with AP AIR-CAP1532I-E-K9 with image LW ap1g3-k9w8-tar.153-3.JK7.tar.
It's not able to join WLC.


My WLC is:

NAME: "Chassis" , DESCR: "Cisco 5500 Series Wireless LAN Controller"
PID: AIR-CT5508-K9, VID: V03

The version of the IOS is:

Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 8.0.152.0
Bootloader Version............................... 1.0.1
Field Recovery Image Version..................... 6.0.182.0
Firmware Version................................. FPGA 1.7, Env 1.8, USB console 2.2
Build Type....................................... DATA + WPS

System Name...................................... WC1
System Location.................................. Location 2, R1
System Contact...................................
System ObjectID.................................. 1.3.6.1.4.1.9.1.1069
Redundancy Mode.................................. Disabled
IP Address....................................... 192.168.1.99
IPv6 Address..................................... ::
Last Reset....................................... Software reset
System Up Time................................... 481 days 22 hrs 55 mins 38 secs
System Timezone Location......................... (GMT +2:00) Jerusalem
System Stats Realtime Interval................... 5
System Stats Normal Interval..................... 180

Configured Country............................... BG - Bulgaria

--More-- or (q)uit
Operating Environment............................ Commercial (0 to 40 C)
Internal Temp Alarm Limits....................... 0 to 65 C
Internal Temperature............................. +38 C
External Temperature............................. +23 C
Fan Status....................................... OK

State of 802.11b Network......................... Enabled
State of 802.11a Network......................... Enabled
Number of WLANs.................................. 7
Number of Active Clients......................... 126

Burned-in MAC Address............................ E2:C7:24:AA:79:80
Power Supply 1................................... Present, OK
Power Supply 2................................... Absent
Maximum number of APs supported.................. 500
System Nas-Id....................................
WLC MIC Certificate Types........................ SHA1


The error logs on the AP are:

Jul 14 07:22:03.471: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.1.99
*Jul 14 07:22:08.471: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.1.99
*Jul 14 07:22:08.471: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.1.99
*Jul 14 07:22:08.471: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.1.99:5246
*Jul 14 07:22:08.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.1.99 peer_port: 5246
*Jul 14 07:22:08.475: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.1.99 peer_port: 5246


Do you have any idea what is the reason for this error?

Thank you in advance.
Best Regards.

 

19 Replies 19

Rich R
VIP
VIP

15.3(3)JK7 is the very latest 8.10.171.0 CAPWAP AP software which includes CAPWAP protocol changes for compatibility with the latest 9800 software versions.

The WLC is running 8.0.152.0 which is very old.  I suggest you manually downgrade the AP to 15.3(3)JA12 (for 8.0.152.0 AireOS) then try to join it.  I suspect the new CAPWAP protocol standard simply won't work with 8.0.152.0.
https://software.cisco.com/download/home/284620606/type/280775090/release/15.3.3-JA12

Hi, thank you.

I will try with image  15.3(3)JA12.

tanner.zaitt
Level 3
Level 3

Hi, with the old image  the issue has been resolved.

Thank you to all for your attention regarding the topic.

Best Regards.

Rich R
VIP
VIP

Thanks for the update @tanner.zaitt - I think that confirms my suspicion that the CAPWAP protocol changes in 8.10.171.0 are not recognised by 8.0.152.0.

Yes, I accepted your answer as a solution.

Thank you again ^^

Review Cisco Networking for a $25 gift card