This seems to be a common topic......
I have looked through the troubleshooting guide and still have no resolution to the problem. My WLC is not seeing any LWAPP messages come through, as the AP is not resolving the controller address. I can ping the DNS server where the CISCO-LWAPP-CONTROLLER is. Here is a sample of the output from the AP:
Apr 30 09:32:42.120: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to administratively down
Apr 30 09:32:42.134: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
Apr 30 09:32:43.127: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.
Apr 30 09:32:43.158: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER.<removed>.com
Apr 30 09:33:33.164: %CAPWAP-5-DHCP_RENEW: Could not discover WLC using DHCP IP. Renewing DHCP IP.
Not in Bound state.
Apr 30 09:33:43.792: %DHCP-6-ADDRESS_ASSIGN: Interface GigabitEthernet0 assigned DHCP address 10.0.48.51, mask 255.255.255.128, hostname AP0022.bd1a.6368
Apr 30 09:33:48.666: %CAPWAP-3-ERRORLOG: Invalid event 29 & state 4 combination.
Apr 30 09:33:48.666: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message.
Apr 30 09:33:48.667: %CAPWAP-3-ERRORLOG: Failed to handle timer message.
Apr 30 09:33:48.667: %CAPWAP-3-ERRORLOG: Failed to process timer message.
Apr 30 09:33:48.667: %CAPWAP-3-ERRORLOG: Discovery interval timer expiry handler failed.
Apr 30 09:33:48.704: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
Thank you for your time.
Hi, you wrote that you've add a DNS entry for CISCO-LWAPP-CONTROLLER but from the log of the AP you'd see that he contacts the DNS for CISCO-CAPWAP-CONTROLLER.
So have you also set that one !?
Yes as your AP is using CAPWAP instead of LWAPP.
Here a link, search for "DNS discovery" --> http://www.ciscosystems.com/en/US/docs/wireless/wcs/5.2/configuration/guide/5_2ovrv.html#wp1145754
Sorry everyone I have been away from work for a couple days. It was indeed the WLC software version. I am confused how the controller reverted back to 4.x code. It was at 6.x, unplugged and moved, plugged back in and had 6.x code, then rebooted and had 4.x.
Thanks for the help, guess I just overlooked the software because I didn't think there was any way it would magically revert.
I have run into another intersting error. I'm attempting to configure Switch Port Trace through WCS for rogue detection.
I get a failure and the details states that CDP is not enabled on the AP. When i show cdp nei from the AP I don't see anything, however when i show cdp nei from the switch it is connected to, the switch sees the AP.
Below is the error:
May 4, 2010 01:29:35 PM CDT: ERROR: Following error(s) encountered during tracing:
No CDP neighbor(s) found for AP HQ_AP connected to Controller 4402. Please make sure you have enabled Cisco Discovery Protocol (CDP) on the AP and AP is connected to a valid Cisco ethernet switch. Skipping this AP...
Sounds like you may have the switchport configured as a trunk with a native vlan set to something other than 1. If you change it to an access port you should see your cdp neighbor from the AP.