Hi Everyone, We're seeing these messages in the logs of a couple of WLC's configured to be anchor controllers. The two WLC's each have a dhcp scope that is part of the same network.
WLC1 has a scope of 10.60.48.1-255, a network of 10.60.48.0, a netmask of 255.255.240.0. and a dg of 10.60.63.254
WLC2 has a scope of 10.60.56.1-255, a network of 10.60.56.0, a netmask of 255.255.240.0. and a dg of 10.60.63.254
The alarm is seen when a user of the guest wireless access service connects having used the service the day before. The dhcp client is trying to renew an existing DHCP lease rather than request a new lease. When the client connects they are request a reuse of their current old IP address.
They seem to get an IP address from the DHCP lease pool from both controllers allocated if you analyse the DHCP leases in use on the controllers. Is this normal behavious for the setup using mobility?
If the message DHCP-3-ADDR_NOTIN_POOL is seen in the logs then we see a client connected using their ' old' ip address in one of the WLCs and there's a lease used on the second WLC controller
I have ran into the same issue as you and had a TAC case open because I needed traffic to flow to one anchor controller in one data center and not the the other wlc in another data center. I was told and as you have seen also, there are no configurations to force the foreign WLC to send guest traffic to one instead of another..... I had this in 4.2 and TAC told me that it might be a feature in the new code, but I have not seen it yet.