New In This Document

Key Features and Enhancements in SmartZone 7.1.0 Rev B (January 2026)

Feature

Description

Reference

Editorial and terminology updates Updated: Comprehensive editorial cleanup for clarity, consistency, and concision; corrected terminology, grammar, and capitalization; harmonized captions, notes/cautions, and UI naming. Throughout the guide
Expanded IPv6 support and limitations Updated: Clarified that IPv6 is supported across DP functions, but not for northbound SoftGRE tunnels; added explicit NOTE for deployment planning. Introduction to the SmartZone Data Plane; Data Plane Features and Benefits
Enhanced Data Plane configuration procedures New: Expanded and clarified step-by-step instructions for configuring Data Plane interfaces, static routes, DHCP/NAT profiles, and syslog. Managing the Data Plane; Configuring the Data Plane
Improved DP Group and NAT license assignment workflow Updated: Added detailed wizard steps, warnings for over-assigned DPs, and clearer error messages for DP Group and NAT license assignment. Creating a Data Plane Group; Creating DHCP License Assignment
Flexi-VPN feature clarifications Updated: Added explicit requirements, limitations, and best practices for Flexi-VPN, including IPv4-only support and profile assignment behavior. Enabling Flexi-VPN
L3 Roaming enhancements Updated: Clarified prerequisites, controller limits (max 40 DPs), and configuration reset behavior on upgrade; added step-by-step enablement and troubleshooting notes. L3 Roaming
Multi-Tunnel Support for APs New: Expanded guidance for configuring multiple simultaneous tunnels (Ruckus GRE and SoftGRE) per AP and zone, including prerequisites and mapping. Multi-Tunnel Support for Access Points
Updated Split Tunnel Profile limitations New: Added new limitations and clarified existing ones (for example, no DHCP/NAT server support, no wired client support, no IPv6, no mesh, no Express Wi-Fi on same WLAN). Split Tunnel Profile
Improved upgrade and backup/restore procedures New: Added step-by-step instructions for Data Plane upgrade, cluster backup/restore, and network configuration backup to FTP. Upgrading the Data Plane
Expanded CLI Actions and Examples New: Added detailed CLI procedures for Data Plane configuration, including step-by-step commands for interface setup, static routes, DHCP/NAT profile binding, syslog, certificate management, and troubleshooting. Includes sample command outputs and best practices for CLI-based workflows. Managing the Data Plane; Accessing the Data Plane CLI
Data Plane (SDP) Certificates New: Added comprehensive section on Data Plane certificate management, including trusted CA chains, certificate import/export, validation toggles, and best practices for securing controller–AP/DP communication. Data Plane Certificates
  • Feature Column

    The Feature column shows the name of each new, updated, or deleted feature in a separate row.

  • Description Column

    The Description column shows a brief description of the new, updated, or deleted feature.

    The Description need not be too lengthy. Begin each description with the notation New, Updated, or Deleted before including a description of the feature or change.

    Note: Keep in mind that the descriptions are likely to be used in the release notes too.

  • Reference Column

    The Reference column shows a cross-reference (live link whenever possible) to the appropriate section in the document.

There must be some indication of what has been updated in the released document because there must be some form of change that requires the republication of the document. For documents in which there are no new features or only minor changes, some mention of updates to the guide should be included in the table. For example, some forms of general updates could be listed in the following ways:

  • Editorial updates and corrections
  • Addressing reported defects
  • Unsupported software
  • Unsupported hardware
  • Unsupported feature

The reference to these types of changes could be “Throughout the guide” or “References have been removed throughout the guide.” The goal is to indicate that the change or deletion has occurred throughout the document.