In this document Cisco TAC engineer "Siddharth Vij" has explained about the issue seen on 3500 AP Hardware Revision 2 and 1042 AP's Hardware revision 4, connecting to a Layer 3 VLAN switch port only with a broadcast IP address set on the VLAN Interface something other than 255.255.255.255.
If these AP's are connected to a Layer 2 VLAN or the same VLAN as the management interface or the controller, they have no issues in getting an IP address from the DHCP server and joining a WLC running 7.3 or 7.4 codes.
These APs when trying to join a WLC running 7.3 and 7.4 code don't get an IP address assigned to them from the DHCP server, assigning a static IP address manually makes the AP to join the WLC running 7.3 or 7.4 software versions.
This issue is not seen on WLC running 7.2 and below software versions.
The Access Point AIR-LAP1042-A-K9 is not getting IP from the DHCP server with software versions 220.127.116.11 and 18.104.22.168 on the AIR-CT5508-K9 controller. If the controller is in version 22.214.171.124 the AP receives IP by DHCP.
In versions above 7.0 only when configuring static IP (lwapp ap ip address IP MASK) the AP joins the controller. Both AP and controller are in the same VLAN and there is a DHCP server on that network.
Here is a sample of the log in the AP console:
*** *Apr 5 14:39:49.368: CAPWAP-3-ERRORLOG Not sending discovery request AP does not have an Ip !! *Apr 5 14:39:49.372: CAPWAP-3-DHCP_RENEW Could not discover WLC using DHCP IP. Renewing DHCP IP. *Apr 5 14:39:59.373: CAPWAP-3-ERRORLOG Not sending discovery request AP does not have an Ip !! *Apr 5 14:40:09.372: CAPWAP-3-ERRORLOG Not sending discovery request AP does not have an Ip !! *Apr 5 14:40:19.372: CAPWAP-3-ERRORLOG Not sending discovery request AP does not have an Ip !!
*Apr 5 14:40:29.372: CAPWAP-3-ERRORLOG Not sending discovery request AP does not have an Ip !! Not in Bound state. ***
How to make the AP's receive IP from the DHCP server on versions above 7.0?
This issue happens due to the layer 3 VLAN SVI on the switch having a "ip broadcast-address <ip-address>" configured with something other than the default broadcast address "255.255.255.255".
Removing the broadcast address command or making the broadcast ip to default 255.255.255.0 resolves this issue.
My 9800-40 HA stack on 16.12.4a, which is not yet in production lost its sso state.I did a hard reboot of the stack and while I have sso back the active is not hearing/responding to discovery requests. I have 6 9117's and a 1852 which is my lab...
Hello, I'm trying to config a NPS server with WLC, to authenticate on WLAN with AD users.The WLC has various interfaces,10.10.10.10 (Management)10.10.11.10 (LAN)10.10.12.10 (Guest) The NPS Server as an IP add: 10.10.11.99.If in the NPS server, t...
Hello, APs are joined to vWLC C9800. All profiles and tag are configured and puched to APs, but the Operrtation Status are down. Please see the below screenshot. One way we can make it up is to reset APs from factory setting. But we do not think it is nor...