AP not showing on Controller

[polleyjb01]

I just setup two new wireless N access points. They are in the right vlan and their status is connected. My problem is when I login to my 4404 controller and go under the wirelss tab, I don't see the new AP's. I see the rest of my access points and they are working.

How can I get my new access points to show up on my controller?

[Nicolas Darchis]

I would suggest you refer to the Controller config guide and various documents explaining the WLC discovery process for an AP.

As a recap, an AP discover a WLC :

-through same-subnet broadcast

-through option 43 if it received that option during DHCP

-through DNS if the AP is aware of a DNS server

Nicolas

[polleyjb01]

One of the AP's in question joined the controller for a few seconds. I even managed to get a screen shot of it under the wireless tab. As soon as I clicked the wireless tab again (to refresh) the ap disappeared...

I found this message log. Can someone tell me what it means?

*Feb 16 09:34:57.980: %DTLS-5-PEER_DISCONNECT: openssl_dtls.c:659 DTLS peer 172.16.22.65 has closed connection.
*Feb 16 09:34:57.878: %CAPWAP-3-DUP_AP_NAME: capwap_ac_decode.c:1077 AP with same name APc471.fed9.3a5f exist. Using default name APc471.fed9.3a5f for this AP.
*Feb 16 09:34:57.875: %DTLS-5-ESTABLISHED_TO_PEER: openssl_dtls.c:559 DTLS connection established to 172.16.22.65
*Feb 16 09:34:53.385: %CAPWAP-3-SEM_RELEASE_ERR: capwap_ac_db.c:103 Could not release exclusive access of AP entry for e0:5f:b9:d6:fd:c0 in the database
*Feb 16 09:34:53.385: %OSAPI-5-MUTEX_UNLOCK_FAILED: osapi_sem.c:995 Failed to release a mutual exclusion object. mutex unlock failed, not owned by the calling thread.
-Traceback:  10523d18 101adf90 1073bf20 1026e6dc 10270604 107361cc 10527088 10ef7aa4 1110b5ec

[Nicolas Darchis]

That means the AP started the joining process without finishing it. It happens if you enable AP authorization onthe WLC and didn't add the mac addresses of the new APs for example.

it's strange that WLC claims that an AP with same name exists ... Looks like something couldn't be deleted the first time the AP left the WLC. Did you try to reboot ?

nicolas

[polleyjb01]

I did reboot the controller yesterday and I just booted the AP from the logs in my office. I could give everything another reset if needed

[Nicolas Darchis]

Please post a "show run-config" from your WLC and also collect "debug capwap events enable" and "debug capwap errors enable" when the APs try to join.

Nicolas

[polleyjb01]

I just plugged in one of our older 1131 Aps. This ap worked fine and made it to the controller. The Problem seems to be the new 3500 Wireless N AP's we are using.

Do you think we need to upgrade our 4404 controllers to a new version? Maybe they don't support these 3500's. Our Software Version is 6.0.199.4 right now

[polleyjb01]

http://www.cisco.com/en/US/docs/wireless/controller/release/notes/crn7.0.html#wp626190

The above links tells me what software version first supports the 3500 AP:

AIR-CAP3502I

7.0.98.0

So I guess I found out whats wrong. I need to upgrade to 7.0.98.0. Does that sound right to you?

[Leo Laohoo]

Correct.  Your controller needs to be running 7.0.98.0 firmware to be able to support 3500 AP.