Cisco AP's ARP and CDP IPs dont match

[Marc Compher]

We have three 1602 APs that, two of which were used at another site and cabled it to one of our production switches at a new site. The two re-used AP's IP was statically assigned via our WLC and worked successfully.

We moved the APs to a new site, the DHCP scope sits on our domain controller and is configured accurately including the option 43 setting. After the AP fully loads, we see the two re-used APs gets an accurate IP in the ARP table but still holds the previous IP in when doing a show cdp neighbors detail. The third AP gets an accurate AP and connects to our WLC appropriately. For the two APs, we have tried a number of things including:

-creating a local dhcp on the switch

-rebooting the AP

-switching the VLAN to put it on another network

-leaving a blank switch port config

-switching the port config from a trunk port to an access port

Consoling into the AP will be an option in a few days when I am onsite again, just not at the moment. We are looking to expedite getting the APs online if we can do it. 

Please let me know if anyone has any ideas, thanks!

[Rich R]

https://www.cisco.com/c/en/us/td/docs/wireless/access_point/1560/installation/guide/1560hig/1560_ch3.html - Resetting the Access Point

Remember they'll need to be changed to local mode after default.

Next time clear the AP config before you move it! 

Generally better to use DHCP for CAPWAP APs to avoid this type of problem.

Otherwise if you don't have local hands to do the reset and you really want to do it remotely you'll have to put the APs in a VLAN which looks like the one they're configured to work on (same subnet and default gateway) so that it can join the WLC and then you can clear the config and then move back to new location.  If that creates a duplicate subnet for you then you could NAT it to work around that.