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 126.96.36.199 and 188.8.131.52 on the AIR-CT5508-K9 controller. If the controller is in version 184.108.40.206 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.
Hi everybodyI encountered a problem that the AP automatically dropped and the client could not connect. The AP needs to be restarted to solve the problem, but after one to two days, the same phenomenon occurs. Query the AP logs and found the following err...
Hello Team,Do we have standard WLC sizing guide specially for bandwidth related to management traffic for Cisco WLC.. the requirement is WLC is remote and our company is going to take management of WLC, before that.. they want to know the managment t...
Hi. I have an Aironet 1840i and I want to measure some signal properties such as RSSI, noise and SNR through the controller commandline. I found some documents suggesting show commands with cleanair, but those don't work since 1840i is utilizing a qca chi...
Is there any trick to getting this working? ALl the devices are on the network fine, (it's a flat network, so all the same vlan). however when attempting to browse google devices i.e. google home, or chromecasts, they'e howing as unavailable Run...