RUCKUS Edge Fallback

In active-active deployments, each AP selects an ordered list of RUCKUS Edge IPs and begins tunneling to the first Edge device in the list. A keepalive probe continuously checks the liveness of this Edge device. If the response to the probe fails, the AP switches to the next Edge in the list. The first RUCKUS Edge device in the list is referred to as the Primary Edge.

Feature Overview

The RUCKUS Edge Fallback feature allows an AP to reconnect to the Primary Edge device according to the user-configured schedule. This helps balance the load of APs across RUCKUS Edge devices within the Data Center (DC) cluster. The AP will attempt to fall back to the Primary RUCKUS Edge only if it is currently connected to a non-Primary Edge device. The fallback schedule offers the following three options for configuring the time interval:

  • Daily: Sets the fallback schedule for the specified time each day.
  • Weekly: Sets the fallback schedule for the chosen day at the specified time.
  • By Interval: Sets the fallback schedule for the designated interval.

Requirements

This feature is disabled by default and can be enabled using the RUCKUS Edge Fallback option toggle switch on the HA Settings page for a specific cluster.

Considerations

By default, the RUCKUS Edge Fallback feature is disabled. When the feature is enabled, the default fallback schedule is set to 4 AM daily (local time zone of the venue to which the cluster is applied).

For DMZ tunnelling, fallback schedule configuration for the DC cluster needs to be configured under the DMZ cluster HA setting.

Limitations

The Fallback scheduled time is not automatically adjusted for Daylight Saving Time. Therefore, when exiting Daylight Saving Time, the RUCKUS Edge device will trigger fallback an hour earlier than the scheduled time and while entering Daylight Saving Time, it will trigger fallback an hour later.

Best Practices

This feature has no special recommendations for feature enablement or usage.

Prerequisites

You must have a RUCKUS Edge Active-Active High Availability cluster configured to use this feature. This feature does not apply to standalone RUCKUS Edge devices.