CSCuv61271 - Windows DHCP BAD_ADDRESS for Access Points - 2
To release the "bad addresses", log into your DHCP server, find the DHCP subnet in question, select all of the "BAD_ADDRESS" entries and delete them. The access-points should immediately reacquire an IP address and rejoin the controller.
Thanks for communicating with the cisco community, it is very important to verify that the port where the pc is connected has the correct vlan configuration and the layer 3 device has the help address of the DHCP Server configured, in some cases it does not count only remove the addresses on the server but also locate the layer three device and remove the ARP record on the device or Devices if it has HSRP or VRRP configurator.
Remember to rate this answer as help as this motivates you to continue contributing in the community
Guided workflow allows for automated troubleshooting cases (non-RMA) and RMA creation process for Service Requests (SR) opened for Cisco products.
Less troubleshooting - the IRE (Intelligent RMA Experience) Prediction Engine does ...
1. Asset Recovery EMEAR - Scope2. Cisco Returns Portal – Quick Overview3. Update your RMA – Options and Walkthrough4. POWR Tool and How to Return - Quick guide and Scenarios5. Returned but not closed - Frequent Scenarios6. I cannot return my faulty part. ...
Full analysis if the problem
The root cause behind this problem is the delay in sync between CUCM and CCX.
CCX and CUCM has an automated sync mechanism which might vary from 5 - 10 minutes based on various parameters.
Also there is an option to sync...