Controllerless Networks

Hi all.

We have a cluster of IAP's 115,225 and one 175P all together 80 IAP's. We have multiple reboots per day with a reason "Reboot Time and Cause: AP rebooted Wed Sep 9 14:59:54 EEST 2015; Gateway unreachable"

All AP's are on a same VLAN with a gateway (Firewall) so I think it is impossible that GW is unreachable. Have done some ping tests and have not seen packets loss.

What we have done so far:

1. Changed all cables that doesn't comply with 1Gb speeds or give errors

2. Changed firewall that is the gateway

3. Disconnected some AP's

4. Upgraded sofware multible times all the way from 4.1.1.1 to 4.1.1.9

5. Dropped LAN speed to 100M

Nothing helps. Any tips?

BR, Joakim

Make sure there are no duplicate IP addresses on that network the IAPs are in, where either the gateway IP is duplicated or any of the IAPs IPs are duplicated. If the lease time is really short, that may not help. But putting the devices on some kind of IP monitor so you can look at uptime and see if they correlate to outages would be a good start. Another would be to take one IAP that is the worst offender and give it a static outside of the DHCP range to test.

..and if you are still having problems after Jhoward's suggestions, please open a TAC case so they can help you debug..

We had the same issue. 

Every morning the AP would be UP but without connectivity, to hot fix this issue we commisioned an shutdown interface and no shutdown interface on the Access switch and this usually worked til the next morning.

What we found out when checking out the LOG was the following:

Reboot Information
------------------
AP rebooted Wed Dec 31 19:17:33 UTC 1969; Gateway unreachable
-------------------------------------------------------------

The AP installed is an iAP205 with the IP 192.168.50.2 and the virtual controller has the 192.168.20.3.

What could be the issue on this one?

The issue could be specific to your network, like a duplicate ip address taking over the default gateway.  The majority of users do not have this issue, so we have to look into your network to see what the problem is...

Hello Joakim!

I'm assuming you managed to resolve this issue - care to share?

Got a customer with the same symptoms, and while we wait for the upgrade to be done I like to do some research..

Hi John.

The error message depended on firmware and we got several different error messages. And one of them was "Gateway unreachable" and the problem was that not all heartbeat beacons from AP to Virtual master went throught, if you miss enought beacons AP's will boot. When we used Aruba controller based installation prior to IAP's the was no such problems but it hitted after installing IAP's. So we measured and ended up to change about 50 cables and there is no more problems.

- Joakim