Hi Nikhil,
This is what I understand of your issue thus far,
IAPs reboot multiple times over a period of time with the reboot cause being 'Gateway unreachable'.
Let me give you a backdrop on the reboot cause
1. When the gateway(Typically your master/uplink) is unreachable for a specific amount of time (~5-6 minutes)
2. When the uplink check (Between VC-master and IAP-slave)fails for the same amount of time (The uplink check fails if the packet stats (for the uplink interface) for Rx do not increment/stay stagnant for the above mentioned time)
The IAP will reboot if the above scenarios occur with the reboot cause: Gateway Unreachable
The gateway may be unreachable for a number of reasons.
To list a few,
1. There may be a new master election
2. The master may be down for some reason
3. Any hop inbetween the VC and the IAP might be facing connectivity issues
The IAPs then try to reconnect to the master like how they would when you add them anew to a network.
They try to arp for the master's IP that they get after a master election.
Now,
- What is the instant version being used.
- How is the master election taking place? Is it Manual or Automatic?
How many hops are there between the IAP-slave and the VC-master?
Do any network devices in between the VC and IAP have DHCP Snooping enabled?
- Is ARP allowed or is there any layer 2 mechanism blocking ARP messages?
- Are you using any other network device with other mechanisms that may possibly block ARP requests?
- ARP is broadcast, so has any feature that blocks/drops broadcast messages enabled?
--Give Kudos: found something helpful, important, or cool? Click Kudos Star in a post.
--Problem Solved? Click "Accepted Solution" in a post.