Can't join AIR-CAP2602E-A-K9 to WLC 2504

[maurito_romero]

I have an AP AIR-CAP2602E-A-K9 and a WLC 2504 with software 7.5.102.0. The problem is that the AP can't join this controller:

*Jun 11 11:57:02.411: %CAPWAP-5-SENDJOIN: sending Join Request to 10.3.10.40

*Jun 11 11:57:02.415: %CAPWAP-3-ERRORLOG: Invalid event 10 & state 5 combination.

*Jun 11 11:57:02.415: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 10 state 5.

*Jun 11 11:57:02.415: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Jun 11 11:57:02.415: %CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from 10.3.10.40

I don´t think it is a software version problem but I will upgrade the WLC to version  7.6.120.0 anyway.

Does anyone have the same problem?

Thanks in advanced.

[Leo Laohoo]

The only thing left to consider is that your WLC is configured for the wrong regulatory domain.  Post the WLC output to the command "sh sysinfo".

[Sandeep Choudhary]

HI,

Please paste the output of these commands:

From WLC: sh sysinfo

From AP: sh version

Regards

Dont forget to rate helpful posts

[maurito_romero]

(Cisco Controller) >show sysinfo

Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 7.6.120.0
Bootloader Version............................... 1.0.18
Field Recovery Image Version..................... 1.0.0
Firmware Version................................. PIC 16.0

Build Type....................................... DATA + WPS

System Name...................................... BOController01
System Location..................................
System Contact...................................
System ObjectID.................................. 1.3.6.1.4.1.9.1.1279
IP Address....................................... 10.3.10.40
Last Reset....................................... Software reset
System Up Time................................... 3 days 18 hrs 36 mins 0 secs
System Timezone Location.........................
System Stats Realtime Interval................... 5
System Stats Normal Interval..................... 180
Configured Country............................... BO  - Bolivia
Operating Environment............................ Commercial (0 to 40 C)
Internal Temp Alarm Limits....................... 0 to 65 C
Internal Temperature............................. +25 C
External Temperature............................. +29 C
Fan Status....................................... 3700 rpm

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

Burned-in MAC Address............................ B8:38:61:3F:FA:80
Maximum number of APs supported.................. 10

Show Ver

APb838.6127.9fae#sh version
Cisco IOS Software, C2600 Software (AP3G2-K9W8-M), Version 15.2(4)JA1, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2013 by Cisco Systems, Inc.
Compiled Tue 30-Jul-13 22:57 by prod_rel_team

ROM: Bootstrap program is C2600 boot loader
BOOTLDR: C2600 Boot Loader (AP3G2-BOOT-M) LoaderVersion 12.4(25e)JAY, RELEASE SOFTWARE (fc1)

APb838.6127.9fae uptime is 1 minute
System returned to ROM by power-on
System image file is "flash:/ap3g2-k9w8-mx.152-4.JA1/ap3g2-k9w8-xx.152-4.JA1"
Last reload reason:

This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.

A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html

If you require further assistance please contact us by sending email to
export@cisco.com.

cisco AIR-CAP2602E-A-K9 (PowerPC) processor (revision A0) with 180214K/81920K bytes of memory.
Processor board ID FTX1809J61U
PowerPC CPU at 800Mhz, revision number 0x2151
Last reset from power-on
LWAPP image version 7.5.1.73
1 Gigabit Ethernet interface
2 802.11 Radios

32K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address: B8:38:61:27:9F:AE
Part Number                          : 73-14511-02
PCA Assembly Number                  : 800-37898-01
PCA Revision Number                  : A0
PCB Serial Number                    : FOC18013U5Z
Top Assembly Part Number             : 800-38357-01
Top Assembly Serial Number           : FTX1809J61U
Top Revision Number                  : A0
Product/Model Number                 : AIR-CAP2602E-A-K9

Configuration register is 0xF

[Sandeep Choudhary · Accepted solution]

Hi,

Regulatory domain and wireless software compability is ok.

Can you paste the entire logs from cisco AP.

And I think if its brand new AP then it must be with Mesh image.

May be AP came as a MESH Mode AP. Add the MAC address of that ap to the WLC in the Mac filter list. The ap should then join and you can change it from MESH to normal.

Hope it helps.

[maurito_romero]

This is the entire log

*Jan  8 00:49:43.439: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
*Jan  8 00:49:45.439: %LINK-6-UPDOWN: Interface BVI1, changed state to up
*Jan  8 00:49:46.439: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed state to up
*Jan  8 00:49:48.519: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*Jan  8 00:49:48.531: %PARSER-4-BADCFG: Unexpected end of configuration file.

*Jan  8 00:49:48.547: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Jan  8 00:49:49.519: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Jan  8 00:49:49.551: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Jan  8 00:49:49.559: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Jan  8 00:49:50.579: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Jan  8 00:49:51.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Jan  8 00:49:57.131: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
*Jan  8 00:49:57.243: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 192.9.250.117, mask 255.255.255.0, hostname APb838.6127.9fae

*Jan  8 00:49:57.243: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
*Jan  8 00:49:58.547: %CAPWAP-3-ERRORLOG: Invalid event 29 & state 4 combination.
*Jan  8 00:49:58.547: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message. Event 29, state 4
*Jan  8 00:49:58.547: %CAPWAP-3-ERRORLOG: Failed to handle timer message.
*Jan  8 00:49:58.547: %CAPWAP-3-ERRORLOG: Failed to process timer message.
*Jan  8 00:50:02.311: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
*Jan  8 00:50:02.319: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*Jan  8 00:50:02.347: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
Translating "CISCO-CAPWAP-CONTROLLER.bo.sinteplast.com"...domain server (192.9.250.10)
*Jan  8 00:50:02.347: %IP-4-DUPADDR: Duplicate address 192.9.250.117 on BVI1, sourced by 2c44.fd03.0814
*Jan  8 00:50:03.319: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Jan  8 00:50:03.347: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.
*Jan  8 00:50:03.351: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down [OK]

*Jan  8 00:50:03.359: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Jan  8 00:50:04.439: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Jan  8 00:50:04.447: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Jan  8 00:50:04.455: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Jan  8 00:50:05.475: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Jan  8 00:50:06.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Jan  8 00:50:14.347: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Jun 16 15:15:39.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.3.10.40 peer_port: 5246
*Jun 16 15:15:39.003: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Jun 16 15:15:39.011: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Jun 16 15:15:39.407: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.3.10.40 peer_port: 5246
*Jun 16 15:15:39.407: %CAPWAP-5-SENDJOIN: sending Join Request to 10.3.10.40
*Jun 16 15:15:39.411: %CAPWAP-3-ERRORLOG: Invalid event 10 & state 5 combination.
*Jun 16 15:15:39.411: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 10 state 5.
*Jun 16 15:15:39.411: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller
*Jun 16 15:15:40.003: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Jun 16 15:15:40.031: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Jun 16 15:15:40.039: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Jun 16 15:15:40.047: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Jun 16 15:15:41.067: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Jun 16 15:15:42.067: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Jun 16 15:15:44.407: %CAPWAP-5-SENDJOIN: sending Join Request to 10.3.10.40
*Jun 16 15:15:44.411: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Jun 16 15:15:44.419: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Jun 16 15:15:45.411: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Jun 16 15:15:45.439: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Jun 16 15:15:46.439: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up

[Sandeep Choudhary]

Hi,

*Jan  8 00:49:57.131: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started

Add the MAC address of the MAP to the MAC filter table. In order to do this, choose security > AAA > Mac Filtering > Mac Address / Wlan Id. and then change back to normal mode.

Regards

Dont forget to rate helpful posts

[maurito_romero]

I had the "radius authorization is pending for the ap" message, but after I added the MAC address of the AP to the MAC filter table, the AP finally join the controller, thanks for your help :)

[Sandeep Choudhary]

Yes, Thats the error message comes when you dont have mac address of AP in mac filter list(In case of mesh AP).

I am glad that finally you resolved the issue.

Regards

[maurito_romero]

I added the AP MAC under WLC GUI>>Secuirty>>AAA>AP policies>>Add> (AP mac addr)