System is three WLC 4404 and WCS 184.108.40.206 with Lightweight Access Point.
After the upgrade from 5.1 to 6.0 I have an issue with the Microsoft DHCP and DNS.
The AP has an IP Address from DHCP Server; however the AP found not the WLC.
This is the boot information from my AP 1252.
*Mar 1 00:00:06.179: %SOAP_FIPS-2-SELF_TEST_IOS_SUCCESS: IOS crypto FIPS self test passed
*Mar 1 00:00:07.011: %SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: RADIO crypto FIPS self test passed on interface Dot11Radio 0
*Mar 1 00:00:07.507: %SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: RADIO crypto FIPS self test passed on interface Dot11Radio 1
*Mar 1 00:00:07.539: %LWAPP-3-CLIENTEVENTLOG: Read and initialized AP event log (contains, 667 messages)
*Mar 1 00:00:08.491: %LINK-3-UPDOWN: Interface GigabitEthernet0, changed state to up
*Mar 1 00:00:09.475: %SYS-5-RESTART: System restarted --
Cisco IOS Software, C1250 Software (C1250-K9W8-M), Version 12.4(21a)JA2, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2009 by Cisco Systems, Inc.
Compiled Mon 02-Nov-09 18:58 by prod_rel_team
*Mar 1 00:00:09.475: %SNMP-5-COLDSTART: SNMP agent on host AP-Test-DP-Pullach is undergoing a cold start
*Mar 1 00:00:10.531: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Mar 1 00:00:10.691: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0, changed state to up
*Mar 1 00:00:10.691: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 1 00:00:10.691: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
*Mar 1 00:00:10.691: %SSH-5-ENABLED: SSH 2.0 has been enabled
*Mar 1 00:00:10.999: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Mar 1 00:00:10.999: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 1 00:00:12.379: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 1 00:00:12.379: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
*Mar 1 00:00:19.403: %DHCP-6-ADDRESS_ASSIGN: Interface GigabitEthernet0 assigned DHCP address 10.110.12.12, mask 255.255.255.0, hostname AP-Test-DP-Pullach
*Mar 1 00:00:28.539: %CDP_PD-4-POWER_OK: 15.4 W power - INJECTOR_CONFIGURED_ON_SOURCE inline power source
*Mar 1 00:00:28.563: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
*Mar 1 00:00:28.583: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 1 00:00:29.395: Logging LWAPP message to 255.255.255.255.
*Mar 1 00:00:29.407: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 255.255.255.255 started - CLI initiated
*Mar 1 00:00:29.535: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
*Mar 1 00:00:29.535: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
Translating "CISCO-CAPWAP-CONTROLLER.de.linde.grp"...domain server (10.134.35.118) [OK]
Translating "CISCO-LWAPP-CONTROLLER.de.linde.grp"...domain server (10.134.35.118) [OK]
*Mar 1 00:00:38.543: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.
*Mar 1 00:02:49.547: %CAPWAP-5-DHCP_RENEW: Could not discover WLC using DHCP IP. Renewing DHCP IP.
Not in Bound state.
Hi Dieter, is the correct address for the AP-Manager (not Management address) 10.134.35.118? If so, is this AP pingable from a different subnet?
Hi, this is the address from the Management, not from the AP-Management and the address range for AP's is pingable from different subnets.
The IP-Address for AP-Management for the three WLC is 10.134.35.119, 10.134.35.121 and 10.134.35.123.
The IP-Address for Management for the three WLC is 10.134.35.118, 10.134.35.120 and 10.134.35.122.
Dieter, are all of these WLCs in the same Mobility Group? If so, then you can use any of the AP-Manager addresses. So what you'll need to do is change your CISCO-LWAPP-CONTROLLER and CISCO-CAPWAP-CONTROLLER DNS entries to reflect one of these AP-Manager addresses and the LWAPP APs should come up.
Yes all WLC's are in the same Mobility Group.
I give this information to my colleagues from Microsoft DHCP/DNS team.
The implementation can take some time. I give you information from the result.
We have changed the IP Address DNS entries from CISCO-LWAPP-CONTROLLER and CISCO-CAPWAP-CONTROLLER to the AP – Management addresses. I have the same issue, the AP not found the WLC’s. I send information from a debug on the AP debug capwap client packet detail and debug lwapp client packet detail.
Dieter, is this an AP that is natively LWAPP or has it been converted from an Autonomous AP? Also, is there anything on the logs of the controller showing that the AP is trying to connect?
Ryan we have native LWAPP AP’s. (Air-LAP1252AG-E-K9).
I have not logging information on the controller side.
Could be several different issues. First step in troubleshooting is to make sure that the date and time on the controllers is correct. This could cause a certificate issue if the time and date are wrong. Next, go to the switch that an AP is plugged into and replace the connection to a laptop to see if you can ping the controller management interface. If not, you have either a routing or trunking issue on the network. Finally, if both of these are working, check in the controller logs to insure you're not having a failing from the certificate or AP authentication to the network. It appears you are running FIPs level code so the AP needs to authenticate against the controller right?
Hi Dennis, thanks for your help.
to first step, time and date on the controller is correct. The controller agrees this from NTP Server.
to step to, I can ping the controller management interface from AP side.
I found the issue, this was a missing DHCP option on Microsoft DHCP Server "Option 3 Router"
Thanks all for your help.
Thanks for the information, I has same problem... this helped me to fix the problem
+5 and double thumps up
We encounter this problem while up-grading the WLC software to version 7. So it means does it was working without router in version 6 of WLC. Question pondering me
Please rate the post that helped you. I see a lot if thank you, but no ratings at all:)
This does help when others search as they might want to just see the marked answers.
Sent from Cisco Technical Support iPhone App