Did you used to have an air control server on a different IP that managed the devices going down? If they weren't properly unmanaged from the old one, they're still trying to talk to it and behavior will manifest itself as you've described.
On Tue, Nov 8, 2016 at 12:44 PM -0700, "Charles Sprickman" <[email protected]> wrote: Hi all, I’ve not had much luck on the forums, so I thought I’d see if anyone here has some tips on how to track this down. Lots of info in this thread: http://community.ubnt.com/t5/airControl-v2-Beta/Debugging-devices-going-quot-offline-quot/m-p/1717755/highlight/false#M13316 I can find no commonality in the devices that fall off: - I see 5.6.x, 6.x, and 8.x versions getting false downs - I see APs, CPE, ac, n units getting false downs - When checking if the units are reachable, I run my tests from the host running AC2 to eliminate any routing weirdness - The devices always reconnect immediately when I manually ask AC2 to reconnect the device What should be noted, is that AC2 (and all our other stuff) is running on AWS instances. I tunnel the traffic back to each PoP with a VPN from AWS to each tower. The RTT on that link is usually about 50ms. For now, I’d settle on some recommendations to make the check a little less aggressive in case I’m just measuring blips between AWS and Fairpoint. Thanks, Charles _______________________________________________ Ubnt_users mailing list [email protected] http://lists.wispa.org/mailman/listinfo/ubnt_users
_______________________________________________ Ubnt_users mailing list [email protected] http://lists.wispa.org/mailman/listinfo/ubnt_users
