05-11-2022 06:52 AM
After upgrading Cisco 5520 WLC to 8.10.171.0, APs are causing DHCP BAD_ADDRESS in Window Server 2008 R2, Server 2012 DHCP servers. Our Current AP Models are AIR-AP2802I-B-K9 and AIR-CAP2702I-A-K9. This is related to Cisco Bug ID: CSCuv61271.
Do we have any fix or workaround for this issue?
Regards,
Mohan Kumar
Solved! Go to Solution.
05-11-2022 07:05 AM
When a Cisco WLC is rebooted, the AP tries to associate with the Cisco WLC. During this time, the AP keeps renewing the IP address. Every time the AP releases the current DHCP lease, the AP sends out 3 DHCP release packets. This functionality of sending 3 DHCP release packets is common across all Cisco IOS software-based products. Cisco DHCP servers running on various Cisco devices release the IP address when they get the first DHCP release message, but ignore the later messages. However, the Microsoft DHCP server marks the AP as BAD_ADDRESS when it receives the second and the third DHCP release packets.
A workaround for this issue is to configure DHCP release override and set the number of DHCP releases sent by AP to 1, on a Cisco AP or all APs by entering this command:
config ap dhcp release-override enable {cisco-ap | all}
05-11-2022 07:05 AM
When a Cisco WLC is rebooted, the AP tries to associate with the Cisco WLC. During this time, the AP keeps renewing the IP address. Every time the AP releases the current DHCP lease, the AP sends out 3 DHCP release packets. This functionality of sending 3 DHCP release packets is common across all Cisco IOS software-based products. Cisco DHCP servers running on various Cisco devices release the IP address when they get the first DHCP release message, but ignore the later messages. However, the Microsoft DHCP server marks the AP as BAD_ADDRESS when it receives the second and the third DHCP release packets.
A workaround for this issue is to configure DHCP release override and set the number of DHCP releases sent by AP to 1, on a Cisco AP or all APs by entering this command:
config ap dhcp release-override enable {cisco-ap | all}
05-11-2022 07:29 AM
Thank you, MHM. I think this should fix our problem, we'll test that get back to you.
05-14-2022 05:17 AM
Thank you, MHM. Your recommendation is solved the problem.
11-15-2022 04:30 PM
Hello,
Is there a fix or workaround for Catalyst 9800-40 controllers? We experienced a similar issue during a failover.
the config ap commands are not eligible on the new controllers.
08-14-2024 09:41 AM
Hi,
How did you resolve this with your 9800-40? We are in the process of migrating our wireless infrastructure from 5520 to 9800 and we have had the BAD_ADDRESS issue occur twice at one of our sites. Our DHCP servers are running Server 2022 so it doesn't match the bug exactly. To stabilize our AP's at this site, we implemented a dhcp pool on our core switch and that restored connectivity for our access points at this site. I have a case open and am waiting to hear from them.
05-11-2022 07:16 AM - edited 05-11-2022 07:17 AM
This can be a bug but dont seems to be the one you mention. The bug you mention reffers to versions:
8.0(110.0) 8.0(115.0) 8.0(120.0) 8.0(122.19) 8.1(102.0)
For the version 8.10 we have a log of bugs but no one related to DHCP.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide