nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

downtime between Vsz and AP

caesar_chen

Hi All

Our Vsz is setup as a VM in the cloud, all communication between AP and the controller travel through a site to site VPN setup on the firewall. Recently the firewall had a hardware failure and the VPN tunnel went down for more than 10hours, as a result all the AP went offline after failing to communicate with the controller on the cloud. at the same time the whole environment was experiencing internet failure.

I was trying to explain to the management that the root cause for the internet failure was due to the failure of the firewall hardware ans has nothing to do with the AP failing to communicate with the Vsz controller. My understanding is that the only impact when the AP fail to communicate with the controller is that you couldn't apply and push any policy or changes down. Please let me know if I am right or wrong.

Thank you

Find more posts tagged with

Accepted answers

sanjay_kumar

@caesar_chen
The AP will only have reboot issue if it is not able to contact the controller for more than 2 hours. It is a setting which is configured on the controller GUI under Zone setting.

The APs will hold the configuration locally, so even it is not able to contact the controller, it should still server the clients and provide internet if it is WPA2 SSID or Open SSID (Unless it is not tunneled)

However, SSIDs like Radius (Proxy) Web Auth, WISPr\Hotspot, Guest SSID, Or Tunnel SSIDs, clients connecting to these SSIDs will have issues, as it needs the controller to take care of these traffic.

I hope this helps.

All comments

Parik_MN

Hello @caesar_chen,

Correct, even through the AP loses connectivity with controller they continue to serve the clients. However, the connectivity shouldn't be more than 2 hours, AP reboots to recover the connectivity. By default AP Zone is configured with reboot timer, which reboots after 30 minutes of losing default gateway and 2 hours after losing connectivity with SZ. This can be disabled by setting up the AP Zone >> Advanced settings >> AP reboot timeout value to '0'.

Hope the explanation is helpful.

Regards,

Parik

sanjay_kumar

caesar_chen

Thank you all for the reply and sharing. I truly appreciate. Thank you!

midtel_mns_team

So the AP's will server the customers past the 2 hours because they are working on their last known good config?