Compare SZ and ZD
Compare SZ and ZD
/ ZoneDirector
smartzone benefits
ZD 9.13 / SZ 3.4
Solution Overview
vSZ - E vSZ - H
Feature SZ100 SCG200 ZoneDirector
(Essentials) (High-Scale)
75 / 500 /
Single Node Scale (AP count) 1,000 1,000 10,000 10,000
1,000
Single Node Scale (Client Count) 25,000 25,000 100,000 100,000 2K / 10K / 20K
Multi-Tenant Management - - ✔ ✔ -
SPoT Integration ✔ ✔ ✔ ✔ ✔
SCI Integration ✔ ✔ ✔ ✔ ✔
FlexMaster Integration - - - - ✔
Cloud or Cloud or
License Management Cloud or Local Cloud or Local Local
Local Local
1 or 2
Redundant
(1) Ctrl/Mgmt/ 1 Redundant
Ports per Plane
Port Groups Data - - Group (Ctrl/
(Ctrl/Mgmt/
(2) Ctrl/Mgmt + Mgmt/Data)
Cluster/Data)
Data)
BeamFlex ✔ ✔ DPSK ✔ ✔
ChannelFly ✔ ✔ ZeroIT - ✔
Data Bridging by AP ✔ ✔
Guest Access
BeamFlex ✔ ✔
Feature SmartZone ZoneDirector
Adaptive Mesh ✔ -
WISPr Hotspot ✔ ✔
802.1X Authentication ✔ -
Integrated Guest Portal ✔ ✔
ChannelFly and BGscan ✔ -
Integrated HTTPS Portal - ✔
Band Balancing ✔ ✔
Integrated Guest Passes ✔ ✔
Load Balancing ✔ -
Web Authentication ✔ ✔
Bonjour Gateway ✔ ✔
Guest Self-Registration - ✔
Application Visibility ✔ ✔
HTTPS redirect ✔ ✔
Guest Access ✔ -
Apple CNA Bypass ✔ ✔
L2 MAC ACL ✔ -
SMS Integration ✔ ✔
L3-4 ACL ✔ ✔
OS Fingerprint ✔ -
Client Isolation ✔ ✔
Capacity-Based
✔ -
Admission Control
ZD to SZ Migration For documentation and best practices in a step-by-step migration, contact your Ruckus rep.
Traditional wireless solutions (including ZoneDirector) have focused on providing redundancy by adding
standby controllers, which may incur some extra cost and licensing. To improve scalability, resiliency, and
performance while decreasing cost, the SmartZone architecture was built in a cluster model that allows
Cluster Deployment
all nodes to remain active at all times. All nodes (controllers) in the cluster are managed from a single
console, all licenses are shared across the cluster, and by distributing AP, control, and data load across
the cluster, performance is improved.
The Virtual SmartZone (vSZ) is a single product with two distinct operating modes: Essentials and High-
Scale (previously known as Enterprise and Carrier). The Essentials (E) mode scales up to 1,000 APs per
node (3,000 per cluster) and has a simplified GUI interface designed for enterprise use cases. Due to its
Essentials vs High- lower scale, the GUI interface has optimized reporting with more granular filters for analytics. The High
Scale Mode Scale (HS) mode scales up to 10,000 APs per node (30,000 per cluster) and has a GUI interface that
provides improved scale and network segmentation of APs into different zones and organizational
domains. Further, it includes a multi-tenant design that allows for managed-service, service provider, and
MVNO use cases.
The SmartZone hardware and virtual solutions are designed to be flexible, to meet the variety of use
cases and design priorities of different organization types. Simple enterprise networks often prefer to plug
in a single cable that provides full access to management, AP control, and data tunnels. More
sophisticated organizations want to segment these network functions into different logical or physical
Port Groups
planes (with redundancy) for security, operational, or other network design reasons. SmartZone
hardware allows for interface segmentation into different port groups, while virtual SZ allows for flexibility
in the number of logical interfaces—for the same reason. For more details, please see product
documentation to understand how your solution can integrate seamlessly into different networks.
When a ZoneDirector is deployed behind (i.e. inside) a NAT router, APs deployed outside the NAT router
can connect to the controller for control and data planes as long as the NAT router forwards the
appropriate connection ports to the ZoneDirector (and the APs connect via the public IP address).
In the SmartZone architecture, when the SZ is deployed inside a NAT router, there are caveats and
limitations to the AP connection.
SZ100 and vSZ-E controllers can be configured with a “control NAT IP address,” which allows APs to
Deploying Remote connect to the controller via the NAT router’s outside interface (typically a public IP address). However,
APs with Controller APs deployed inside the NAT router (local to the controller) will also need to connect to the controller via
behind NAT Router the NAT router’s outside address, which means a NAT hairpin will be needed.
If all APs are local to the controller, the control NAT interface should not be configured.
On the SZ100, the control and data planes must be treated differently, with the following guidelines:
Version 3.0.4: vSZ control NAT interface is supported, SZ100 control/data NAT interface not supported
(cannot use SZ for data tunnel)
Version 3.1.1: SZ100 control NAT interface is supported, data NAT interface not supported
Version 3.2: SZ100 data NAT interface will be supported.
The SmartZone OS has two different types of backups: configuration and cluster. Configuration backups
follow the common practice of exporting a configuration file, which can be imported at a later date to
restore a specific configuration (and only configuration). Cluster backups provide a recovery solution for
Cluster Backups
the entire system, and include much more than just the configuration—firmware, database, and
configuration. You can think of a cluster backup as a complete system snapshot that can be used to
restore the system in full. To export the cluster backup, use the CLI with an FTP server.
ZoneDirector software supports a feature that allows the administrator to define a specific tagged VLAN
AP Mgmt VLAN
for AP management traffic. By default, AP management traffic uses the native VLAN of the AP’s
Tagging
switchport. SmartZone software will support VLAN tags for mgmt traffic in 3.2.