Introduction
Feature Overview
The RUCKUS Edge device is developed to provide distributed services to meet latency and fault tolerance requirements. The following are core principles in developing the RUCKUS Edge:
- The RUCKUS Edge device is developed using cloud-native design principles and interfaces.
- The infrastructure and application services are designed to run in any cloud-native compliant operating system.
- The RUCKUS Edge device's infrastructure and application services run in standard server hardware and on virtual machines.
Requirements
Ensure one of the following requirement is available to onboard a RUCKUS Edge device.
Prerequisites
The following are the prerequisites to onboard a RUCKUS Edge device.
- A hypervisor on which to install RUCKUS Virtual Edge.
- A RUCKUS One account.
- A RUCKUS Edge virtual device (RUCKUS Virtual Edge) distribution package (.OVA file), available for download from the RUCKUS Support website.
- A Virtual Machine (VM) with recommended system resources for the number of APs and wireless clients to manage the network.
- For RUCKUS Edge to be
managed by RUCKUS One, and to
function properly, configure your firewall to allow for outbound
connectivity according to the following guidelines.
Outbound HTTPS (TCP 443) from APs, Switches, and RUCKUS Edge to:
- https://ap-registrar.ruckuswireless.com
- https://sw-registrar.ruckuswireless.com
- https://ruckus.cloud
- https://eu.ruckus.cloud
- https://asia.ruckus.cloud
- https://device.ruckus.cloud
- https://device.eu.ruckus.cloud
- https://device.asia.ruckus.cloud
- https://storage.googleapis.com
- https://edge-docker-registry.asia.ruckus.cloud
- https://edge-docker-registry.eu.ruckus.cloud
- https://edge-docker-registry.ruckus.cloud
- https://registrar.ruckuswireless.com
- https://us-docker.pkg.dev
Outbound HTTP (TCP 80) from APs, Switches, and RUCKUS Edge to:
Outbound SSH (TCP 22) from APs, Switches, and RUCKUS Edge to:
-
Configuring Firewall Rules for AP–Edge Tunnels: When Access Points (APs) and Edge devices communicate over a public network (such as the Internet), IPSec encryption is used to secure AP-to-Edge tunnels. In these deployments, the Edge device is typically located behind a firewall, so you must configure firewall rules to allow tunnel traffic.
If Tunnel Encryption is disabled, configure the following inbound rules on the firewall:
-
IP destination Edge IP and UDP destination port 4790
Purpose: VXLAN-GPE tunnel traffic to Edge
-
IP destination Edge IP and IP protocol ICMP
Purpose: PMTUD from AP to Edge (required if PMTU mode is set to auto)
If Tunnel Encryption is enabled, configure the following inbound rules on the firewall:
-