This article explains why the WLA reboots when new bindings are offered by the DHCP server. An example log printout is provided.

WLA reboots due to new bindings offered by the DHCP server.

By default, when half of the configured DHCP lease time has expired, the WLA will send out a renewal request. If the WLA receives from the DHCP server an IP address different from what it is currently configured with, it will reboot.

The following messages are not an indication of a fault on the WLAN side.

Line 5079: 1034141: WLA Nov 18 22:43:01.263704 ALERT AP 230 AP Buffered Log (0): 324008.348 network: dhcp_lease_periodic: DHCP failed to renew, rebooting: dhcp_state=0 my_ip_addr=0a0b0404
Line 5082: 1034144: WLA Nov 19 01:25:07.559500 ALERT AP 93 AP Buffered Log (0): 950405.680 network: dhcp_lease_periodic: DHCP failed to renew, rebooting: dhcp_state=0 my_ip_addr=0a0b02c8
Line 5092: 1034154: WLA Nov 19 08:16:28.632186 ALERT AP 219 AP Buffered Log (0): 162005.057 network: dhcp_lease_periodic: DHCP failed to renew, rebooting: dhcp_state=0 my_ip_addr=0a0b03f2
Line 5106: 1034168: WLA Nov 19 10:44:49.980190 ALERT AP 231 AP Buffered Log (0): 1198815.384 network: dhcp_lease_periodic: DHCP failed to renew, rebooting: dhcp_state=0 my_ip_addr=0a0b0406
Line 5113: 1034175: WLA Nov 19 12:40:43.421738 ALERT AP 302 AP Buffered Log (0): 302415.176 network: dhcp_lease_periodic: DHCP failed to renew, rebooting: dhcp_state=0 my_ip_addr=0a0b04b6
Line 5120: 1034182: WLA Nov 20 04:44:41.046548 ALERT AP 318 AP Buffered Log (0): 777614.719 network: dhcp_lease_periodic: DHCP failed to renew, rebooting: dhcp_state=0 my_ip_addr=0a0b04d4
Line 5123: 1034185: WLA Nov 20 07:11:40.503590 ALERT AP 103 AP Buffered Log (0): 302405.227 network: dhcp_lease_periodic: DHCP failed to renew, rebooting: dhcp_state=0 my_ip_addr=0a0b02e2

If these messages appear in the log buffer of the WLC, make sure that the DHCP server always responds in a consistent fashion to the WLAs.

2020-10-10: Archived article.