SmartZone Integration in RUCKUS One

RUCKUS One provides native visibility into existing SmartZone (SZ) controllers through the SmartZone onboarding capability. This integration allows Administrators to view SmartZone cluster information directly within the RUCKUS One interface without logging in to the SmartZone management console.

Feature Overview

The SmartZone integration enables RUCKUS One to securely connect to SmartZone controllers that have been onboarded via RUCKUS AI. After onboarding is complete, SmartZone clusters automatically appear in RUCKUS One under Gateway > SmartZone.

Once a SmartZone cluster is onboarded, RUCKUS One continuously synchronizes deployment metadata, such as cluster status, node count, domains, zones, access points, and firmware versions, enabling administrators to monitor their SmartZone environment.

Through this integration, administrators can perform the following tasks:
  • View high-level SmartZone cluster health and connectivity status
  • Review SmartZone inventory details, including domains, zones, AP groups, and managed devices
  • Track firmware versions and last synchronization timestamps

This capability is designed to simplify operational visibility and reduce the need to switch between management platforms.

Requirements

To display SmartZone controllers in RUCKUS One, the following requirements must be met:
  • SmartZone controllers must be onboarded using the RUCKUS AI onboarding workflow.
  • The onboarding must be completed under the same tenant account used by RUCKUS One.
  • Cloud connectivity between SmartZone and RUCKUS Cloud Services must be enabled and operational.

  • The RUCKUS Cloud authentication and analytics services must be turned on in the SmartZone console under Administration > External Services > Ruckus Services > Ruckus Cloud Services.

Once these conditions are satisfied, SmartZone clusters automatically become visible in RUCKUS One for authorized users.

For detailed onboarding steps, refer to the RUCKUS AI User Guide.

Considerations

Consider the following behaviors and limitations when using SmartZone integration:

  • SmartZone controllers are visible only to RUCKUS One End Customer (REC) accounts.
  • User access to SmartZone data depends on privileges configured in both RUCKUS One and RUCKUS AI.
  • SmartZone data is synchronized periodically and may not reflect real-time changes made directly on the SmartZone controller.

Best Practices

Although no special enablement steps are required, the following best practices are recommended:
  • Verify cloud connectivity and analytics status in the SmartZone console prior to attempting onboarding.
  • Use descriptive cluster names in SmartZone to simplify identification in RUCKUS One.

Prerequisites

The user must have Prime Administrator privileges in both RUCKUS One and RUCKUS AI for the same tenant account.