02-09-2017 09:03 AM
I've had an issue with my preferred master IAP crashing when running 'show log provision', and noticed all clients connected on that cluster would lose connectivity for about 10 minutes (until the preferred master IAP came back). This bug brought my attention to how the VC changes IAPs, and what downtime it incurrs.
My understanding of the general process for VC changeover is: When the master IAP crashes or reboots, another IAP will adopt the VC. When the preferred master is back online the adopted VC will reboot, transferring the VC back to the preferred master.
I thought this process was quick, and would have my clients maintain their connection during the VC transition. However it currently takes the whole cluster down and takes some time to get all the clients reconnected. Is this normal, or likely related to a bug?
02-09-2017 09:08 AM
It depends. If your WLAN is Virtual Controller assigned, all traffic is tunneled through the Virtual Controller and source-natted out of it. If there is an outage, that tunnel has to be recreated. For other traffic, the traffic is placed directly onto the network from the AP that clients are on. Those devices should not have a disruption.
Aruba Customer Engineering
Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base
02-09-2017 09:24 AM
All my WLANs are network assigned. One of my WLANs has a dynamic VLAN assignment.
Generally there would be a seamless transition for my scenerio?
I suppose this could be another bug in my delpoyment I'll need TAC to work on. I have had several bugs including the IAPs adding wrong VLAN tags to packets, Captive Portal logins only authenticating when connected to the VC IAP (in one cluster only), VC IAP crashing on certain CLI commands, and CoA not updating Airgroup auth.