Feature Overview

Configuration templates are used by MSPs to standardize configurations across MSP-managed EC accounts. Configuration templates streamline the deployment process, ensure consistency, and reduce the potential for configuration errors.

From the MSP web interface, the MSP administrator can create and manage template instances for venues, Wi-Fi, wired, and services.

After a Wi-Fi template instance is created, the MSP administrator can create and link templates for additional services, such as security policies, quality of service settings, Wi-Fi Calling, or Guest Portal services. Finally, a Venue template is created to encompass the overall setup, including Wi-Fi, switch configurations, and DHCP settings.

An MSP administrator can perform the following actions from the MSP web interface:

• Add, apply, edit, delete, and clone configuration templates.
• Drift Detection: Review configuration drift between MSP templates and EC instances.
• Synchronization: Synchronize EC instance configurations with MSP templates.
• Enforcement: Enforce templates to make EC instance configurations read-only.
• Manage Tags: Assign, update, or remove descriptive tags on configuration templates to improve organization and enable efficient filtering and selection across multiple EC accounts.
• Bundles: Provide a way to view and manage logical groupings of dependent MSP templates. Bundles help streamline multi-tenant operations and improve visibility into template dependencies by organizing templates into a structured, hierarchical model. Bundles inherit all MSP template capabilities, including drift detection, synchronization, and enforcement, allowing these operations to be performed at the Bundle level while maintaining individual template granularity.

From the RUCKUS One for a specific EC account, MSP administrators can view and review template instances associated with each customer account. This visibility helps MSP administrators manage configurations and troubleshoot issues across EC environments. The following Configuration Template categories are supported in the current RUCKUS One interface:

• Wi-Fi: Includes Wi-Fi Network and AP Group templates for defining network security and access configurations and applying them to specific AP groups within venues.
• Venue
• Wired: Covers configurations for network switches using switch profile-based templates.
• Services: Includes configurations for network services and policies such as RADIUS Server, Access Control, VLAN Pool, Syslog Server, Rogue AP Detection, DPSK, DHCP for Wi-Fi, Wi-Fi Calling, and Guest Portal services.
• Webhook

Requirements

Considerations

Consider the following when configuring and using this feature:

• This feature is supported for MSP accounts and applies to MSP-managed EC accounts.
• All templates assigned to a specific MSP account are deleted when the MSP account is deleted.
• Each template type supports only one applied instance at a time, except Venue templates, which can be applied multiple times.
• Applying templates is supported for all configuration template types, while the override functionality is supported only for Venue templates.
• When applying templates from the Bundles page, only the top-level template can be selected to apply the configuration bundle; the downstream templates are read-only.
• Enforcement is supported for selected template types. When enforcement is enabled, applied instances become read-only.
• The Clone operation is supported only for the Wi-Fi Network, Venue, DPSK, Webhook, and Wi-Fi Calling configuration templates. AP Group cloning is triggered by the venue clone process. When you clone a venue instance, all its non-default AP Groups are automatically cloned as part of the venue cloning workflow. AP Group configuration templates cannot be directly, manually cloned.
• Drift detection and synchronization:
  • Drift detection and synchronization are available only for templates applied to MSP-EC.
  • Synchronization applies only to template-controlled configurations.
  • Required dependent templates are automatically applied if they are not already present.
  • If a template has unknown differences, synchronization attempts to synchronize all related template-controlled configurations.

Limitations

Note the following limitations regarding this feature:

• Only one instance of a specific template type can be created within a specific MSP-managed account.
• Viewing configuration details is unavailable for Switch CLI Profile and Switch Regular Profile templates.
• Enforcement applies only to instances created from the template; template details remain editable.

Best Practices

• Create all required templates first, including their dependencies (for example, activating Wi-Fi Network templates on a Venue template), before applying them to an EC account.
• Regularly check the Drift Status and use the Sync option to maintain consistency.
• Enable enforcement only after confirming configurations are finalized.
• Use meaningful template names to simplify identification and management.
• Use the Clone feature to create new templates quickly while reusing existing configuration settings.

Prerequisites

This feature has no prerequisites for enablement or usage.