This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Accept
Reject
RUCKUS Self Help | ASK the Pack Sign In
- Community
- RUCKUS Technologies
- RUCKUS Self-Help
- Admin and Licensing
- Access Points
- ICX
- RUCKUS One
- Cloud
- SZ / vSZ
- Unleashed
- Cloudpath
- RUCKUS AI
- IoT
- RND
- Apps and SPoT
- SCI
- RWG
- Best Practices
- RUCKUS Lennar Support
- Lennar Knowledge Base
- RUCKUS Support for Lennar Homes
- Community Services
- Community and Online Support Services
- Tech Docs
- Training and Certification
- RTF
- RTF Community
- Australia and New Zealand – English
- Brazil – Português
- China – 简体中文
- France – Français
- Germany – Deutsch
- Hong Kong – 繁體中文
- India – English
- Indonesia – bahasa Indonesia
- Italy – Italiano
- Japan – 日本語
- Korea – 한국어
- Latin America – Español (Latinoamérica)
- Netherlands – Nederlands
- Nordics – English
- North America – English
- Poland – polski
- Russia – Русский
- Singapore, Malaysia, and Philippines – English
- Spain – Español
- Taiwan – 繁體中文
- Thailand – ไทย
- Turkey – Türkçe
- United Kingdom – English
- EOL Products
- FlexMaster
- SmartCell Access Points
- RUCKUS Diagnostics Dashboard (RDD)
- ZonePlanner
- ZD
Turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Search instead for
Did you mean:
- RUCKUS Forums
- RUCKUS Technologies
- SZ / vSZ
- Re: downtime between Vsz and AP
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
downtime between Vsz and AP
Go to solution
caesar_chen
New Contributor II
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-04-202311:15 PM
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
Solved!Go to Solution.
1 ACCEPTED SOLUTION
Go to solution
sanjay_kumar
RUCKUS Team Member
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-05-202305:56 AM
@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.
View solution in original post
2Kudos
- All forum topics
- Previous Topic
- Next Topic
4 REPLIES 4
Go to solution
Parik_MN
RUCKUS Team Member
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-05-202305:51 AM
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
0Kudos
Go to solution
sanjay_kumar
RUCKUS Team Member
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-05-202305:56 AM
@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.
2Kudos
Go to solution
midtel_mns_team
New Contributor
In response to sanjay_kumar
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-202410:35 AM
So the AP's will server the customers past the 2 hours because they are working on their last known good config?
0Kudos
Go to solution
caesar_chen
New Contributor II
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-07-202308:04 PM
Thank you all for the reply and sharing. I truly appreciate. Thank you!
0Kudos
Labels
- 92101
- AD1
- AP Controller Connectivity1
- AP Management2
- API Help1
- Client Management3
- er1
- Google1
- Guest Access2
- IP Multicast1
- Proposed Solution3
- RADIUS2
- RUCKUS Self-Help8
- SmartZone4
- SmartZone or vSZ6
- Social Media1
- Solution Proposed3
- string1
- Traffic Management-1
- User Management2
- vSZ2
- Wifi1
- WLAN Management2
- «Previous
- Next»
