Link Search Menu Expand Document
calendar_month 17-Nov-25

Central Configuration Example

This chapter explores using Central’s configuration model to configure a WLAN for APs and a Layer-2 access switch. It does not provide a complete reference configuration, but is intended to illustrate the power and functionality of element profiles.

Table of contents

Element Profile Configuration Process

All profiles are created using the same general process. The following steps create an AAA Authentication profile, and assign it a Device Function and Scope. This example can be used to create additional profiles to establish a fully functioning solution.

Step 1 Click the Gear icon in the upper right hand corner of the window to enter configuration mode.

Step 2 Click Library in the left-hand navigation pane to display the configuration context path.

Step 3 Click Manage in the Security tile to view all profile types this category.

Note: Element Profiles are grouped into category tiles. The AAA Authentication profile type is located in the Security tile. Clicking Manage in a tile category displays all the profiles available in that category. Use the buttons at the bottom of a tile to move through the tile’s pages. In this example, the AAA Authentication profile type appears on the first page. When the desired profile type is displayed in the tile, click the profile type to select it.

**Configuration Overview**

Step 4 Click Manage on the AAA Authentication profile type.

**Profiles Management**

Step 5 On the AAA Authentication profile page, click Create Profile.

Create Profile

Step 6 In the Create Profile window, assign the following settings and click Create.

  • Name: New-AAA-Profile
  • Authentication Protocol: 802.1X
  • 802.1X Authentication Server Group: Global Radius
  • Accounting Server Group: Global Radius

AAA Profile

Note: Profiles often reference other profiles in their configuration. In this example, the Global Radius Authentication Server Group and its member servers must be created before the current profile.

After creating the profile, it is added as a shared profile to the Library, but its configuration is not applied to devices until a Device Function and Scope are applied.

Apply Element Profiles

Assigning a Device Function applies the profile to devices based on their role in the network, such as campus access points or aggregation switches. Assigning the scope allows administrators to select which devices are assigned the profile based on organizational structure or device groups. These two two attributes are evaluated together using Central’s inheritance logic to apply the profile to devices.

Step 1 Select the desired element profile in the library, hover the cursor over the profile entry, and click the triple dots (•••).

AAA Selection

Step 2 On the popup menu, click Assign.

AAA Assignment

Step 3 Select the Device Function(s) for the profile, then click the plus sign (+) beside Scopes.

AAA Function

Step 4 In the Add Scope window, select the Scope Level, then click Add.

AAA Scope

Note: When selecting Site Collections, Sites, Device Groups, or Devices as a scope, an additional assignment of a specific instance within the scope is presented in a context-based dropdown menu. For example, when choosing Site as a scope, another dropdown enables selection of one or more sites.

Step 5 Click Assign to assign the Device Function(s) and Scope(s) to the profile.

AAA Final Assign

After completing the assignment, the profile’s configuration is pushed to appropriate devices based on the rules of inheritance.

Configure Global Profiles

Element profiles applied to all or most of an organization are typically assigned at the Global scope. A small number of exceptions can be managed by using profile overrides or by assigning additional profiles at different scopes, which use inheritance to replace the Global profiles with customized settings.

It is common to apply the profiles in the following table globally, since they can often be used across an entire organization and on all device functions.

Each profile is populated with an operating-system agnostic set of parameters. When Central applies the configuration to specific devices, it uses the syntax appropriate for each platform.

The profile list is suggested to establish a base set of configurations for network services. This includes configuring AAA Authentication to define how users and devices are authenticated to the network, and Authentication Server and Authentication Server Group profiles to define a centralized authentication source such as ClearPass. Additionally, System profiles such as NTP Server, DNS Server, and System Administration are set to ensure that all devices have synchronized time, can resolve hostnames, and are configured for secure management access.

Element ProfileDevice FunctionScopeNote
Security > Authentication ServerAllGlobalEach Authentication Server profile defines an individual AAA server, such as a ClearPass server. Multiple Authentication Server profiles are required, one for each AAA server in the network.
Security > Authentication Server GroupAllGlobalEach Authentication Server Group profile defines a group of AAA servers, and multiple groups are treated in an additive manner.
Security > AAA AuthenticationAllGlobalEach AAA Authentication profile defines a method to authenticate network hosts to a AAA server, including 802.1X and MAC-Authentication. Dynamic authorization is enabled to honor AAA server change the authorization (CoA) requests.
System > NTP ServerAllGlobalThe NTP Server profile defines a set of NTP servers to ensure that all devices have synchronized time. Time synchronization is vital for security, logging, and system management. It is best practice to set at least two NTP servers in a profile. Only a single NTP Server profile is applied to each device using the rules of inheritance.
System > DNS ServerAllGlobalThe DNS Server profile defines a set of DNS servers so network devices can resolve hostnames. It is best practice to set at least two DNS servers in the profile. Only one DNS Server is applied to each device using the rules of inheritance.
System > System AdministrationAllGlobalThe System Administration profile configures local, RADIUS, and TACACS authentication types used by SSH, web, and console services.

Configure Access Switch

Access switches inherit the profiles defined above because they were assigned to the Global scope and all Device Functions. The element profiles in the subsections below complete the access switch configuration.

General Switch Configuration

The following element profiles establish the general configuration settings for access switches. Key element profiles to include are VLANs for user traffic and for switch management, Spanning Tree Protocol (STP) to prevent loops in the network, VSF for switch stacking, and a Device Profile to ensure that connected access points are automatically provisioned. Additional profiles are noted with a description of their purpose.

Element ProfileDevice FunctionScopeDescription
System > Switch SystemAccess SwitchSiteThe Switch System profile sets the timezone, enables unsupported transceivers, enables AAA globally on the switch, and enables telemetry for CX switches.
System > Source InterfaceAccess SwitchSite or deviceThe Source Interface profile configures an interface to source traffic originated from the switch, such as RADIUS requests, NTP queries, etc.
Security > UBTAccess SwitchSiteThe UBT profile enables UBT, creates a UBT zone, and associates a gateway cluster to UBT traffic.
VLANs & Networks > VLANAccess SwitchSiteAn individual VLAN profile is created for the management VLAN and each user VLAN.
VLANs & Networks > VLANAccess SwitchDevice (Local Override)A local override is created for each VLAN profile that requires an IP address assignment. An access switch typically requires only one override for the management VLAN. The override forks the profile from the site level and creates a new local profile at the device level.
VLANs & Networks > STPAccess SwitchSiteThe STP profile enables MSTP by default. Access switches typically use the default STP priority of 8 (the STP priority on aggregation switches is generally set to 4).
Routing & Overlays > Static RoutingAccess SwitchSiteThe Static Routing profile is used to create a default route for the in-band management network. A single Static Routing profile can contain multiple static routes, but the profiles are applied in an additive manner, so multiple Static Routing profiles can be applied to the same device.
Network Services > DHCP SnoopingAccess SwitchSiteThis profile enables DHCP snooping and its associated options, including trusted servers.
High Availability > VSFAccess SwitchDevice-GroupThis VSF profile configures Layer 2 VSF stacking for simplified management and redundant Layer 2 connectivity to the aggregation layer.
Interfaces > Device ProfileAccess SwitchSiteA Device Profile defines a set of OUI and system description parameters used to auto-assign access points to the ARUBA-AP role.

An element profile at the device level creates a Link Aggregation Group (LAG) as an 802.1Q trunk. This provides link redundancy to the aggregation layer and allows the uplinks to carry all host VLANs. Also, enable LACP for active-mode port bundling and enable DHCP snooping trust.

Element ProfileDevice FunctionScopeDescription
Interfaces > Switch Interface ConfigurationAccess SwitchDeviceThe Switch Interface Configuration profile for an individual switch or switch stack allows creating a LAG with common parameters such as LACP.

Port Standardization

The following profiles enable the administrator to create and apply a standardized configuration for access switch edge ports. A comprehensive Port Profile is created to define common settings for administrative state, speed, PoE, and VLAN assignment. This profile also incorporates essential security measures such as Loop-Protect and BPDU Guard to protect the network from loops. The Port Profile is then applied to physical switch interfaces, ensuring that all access ports have a consistent and secure configuration.

Element ProfileDevice FunctionScopeDescription
Interfaces > Port ProfileAccess SwitchSiteEach Port Profile contains a standardized switch port configuration. Multiple Port Profiles can be defined to accommodate different port functions (e.g., host facing ports or uplink ports).
Interface > Switch Interface ConfigurationAccess SwitchDeviceThe Switch Interface Configuration profile at the device level is used to assign port profiles to physical and logical switch ports.

Configure Bridged WLAN

In this example of element profiles, a WLAN in bridged mode is configured. The profiles below combined with the Global profiles above support a WLAN configured for WPA3 personal as an authentication method. A full WPA3 Enterprise implementation requires additional profiles (Authentication Server, Authentication Group, and AAA Authentication profiles).

Note: If Mobility Gateway tunneling is implemented, the scope of the element profiles must change from Global or Site to Device Group to support the current implementation of Gateway Clusters.

The switch port connected to an AP used for bridged WLANs requires a trunk port setting, where the native VLAN is typically set to a management VLAN, and WLAN traffic is bridged to a tagged VLAN.

Element ProfileDevice FunctionScopeDescription
VLANs & Networks > Named VLANsCampus Access PointSite or GlobalEach Named VLAN profile contains a list of one or more user VLANs. This profile can then be referenced by WLAN profiles for VLAN assignment of bridged traffic. Each VLAN listed in the profile must have a corresponding VLAN profile created for the switch infrastructure. The VLAN profile for switches is not tied directly to the Named VLANs profile for Campus Access Points.
Interfaces > AP UplinkCampus Access PointGlobalFor a bridged WLAN, the AP Uplink profile defines a trunk port with the native VLAN set to the management VLAN. It is critical to ensure that settings, including allowed VLANs, match the corresponding switch uplink port.
Wireless > WLANCampus Access PointSite or GlobalEach WLAN profile assigns an SSID name, bridge mode, WPA3 PSK password, and the Named VLAN for bridging traffic. A Default Role is auto-created for a bridged SSID and can be later modified in Library > Roles and Policies.