169. IP

[LinseJames52171]

Anyone come across a situation? Clients connected from one of the APs on the network suddenly valid IP convert to 169. IP and loose the connectivity 

After the restart, the AP will give a valid IP.

2802 models AP and connected Cisco Virtual Wireless Controller (8.5.161.0).

I have checked and there are still available IP`s in the pool. It's happening randomly.

[Flavio Miranda · Accepted solution]

@LinseJames52171 

Yeah, I got a similar issue for 3800 few years ago with the same version. Dont recall the bug ID anymore. It happened because the AP loose ARP entry for network Gateway.

 I recommend move to a newer version.

[LinseJames52171]

Thanks 

[Rich R]

This is a well known bug - see Leo's list below ...
In this case https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvv78719

169 simply means DHCP failed so client self allocates a 169 APIPA IP address:
https://wiki.wireshark.org/APIPA

Your software is severely out of date.  Update to 8.5.182.12 or 8.10.196.0 as per link below & TAC recommended link, and check that all your APs are compatible using the compatibility matrix (link below) and release notes, otherwise you will need to reload the AP every time the bug strikes.