Aruba Central Online Help

Provisioning Devices Using UI-based Workflows

This section describes the important points to consider when assigning devices to UI groups:

Provisioning Instant APs using UI-based Configuration Method

An Instant AP device group may consist of any of the following:

Aruba Central allows configuration operations at the following levels for a device group with Instant APs.

  • Per group configurationAruba Central allows you to maintain unique configuration settings for each group. However, these settings are applied to all devices within that group. For example, all VCs within a group can have common SSIDService Set Identifier. SSID is a name given to a WLAN and is used by the client to access a WLAN network. settings.
  • Per VC Configuration—Any changes that need to applied at the Instant AP cluster level can be configured on a VC within a group. For example, VCs within a group can have different VLAN configuration for the SSIDs.
  • Per Device Configuration—Although devices are assigned to a group, the users can maintain device -specific configuration such as radio, power, or uplink settings for an individual AP within a group.

When the APs that are not pre-provisioned to any group join Aruba Central, they are assigned to groups based on their current configuration.

Table 1: Instant AP Provisioning

APs with Default Configuration

APs with Non-Default Configuration

If an Instant AP with factory default configuration joins Aruba Central, it is automatically assigned to the default group or an existing group with similar configuration settings.

The administrators can perform any of the following actions:

If an Instant AP with non-default or custom configuration joins Aruba Central, it is automatically assigned to an unprovisioned group.

 

The administrators can perform any of the following actions:

  • Create a new group for the device and preserve device configuration.
  • Move the device to an existing group and override the device configuration.

Ensure that the conductor Instant AP and member Instant APs are assigned to the same group. You must convert the member Instant AP to a standalone AP in order to move the member Instant AP to another group independently.

In the following illustration, Instant APs from three different geographical locations are grouped under California, Texas, and New York states. Each state has unique SSIDs and can support devices from multiple locations in a state. As shown in Figure 1, the California group has devices from different locations and has the same SSID, while devices in the other states/groups have different SSIDs.

When a device with the factory default configuration connects to Aruba Central, it is automatically assigned to the default group. If the device has custom configuration, it is marked as unprovisioned. If you want to preserve the custom configuration, create a new group for the device. If you want to overwrite the custom configuration, you can assign the device to an existing group.

Figure 1  Instant AP Provisioning

For more information on how to configure Instant APs using UI-based configuration workflows, see Deploying a Wireless Network Using IAPs.

To view local overrides and configuration errors, select a template group and navigate to Devices > Access Points > Settings > Configuration Audit page.

Provisioning Switches Using UI-based Configuration Method

Aruba Central allows switches to join UI groups only if the switches are running factory default configuration. Aruba Central assigns switches with factory default configuration to the default group.

The administrators can either move the switch to an existing group or create a new group.

Provisioning and configuring of Aruba 5400R switch series and switch stacks is supported only through configuration templates. Aruba Central does not support moving Aruba 5400R switches from the template group to a UI group. If an Aruba 5400R switch is pre-assigned to a UI group, then the device is moved to an unprovisioned group after it joins Aruba Central

Aruba Central allows the following configuration operations at the following levels for switches in a UI group: 

For more information on how to configure switches using UI-based configuration workflows, see Configuring or Viewing AOS-Switch Properties in UI Groups.

To view local overrides and configuration errors, select a template group and navigate to Devices > Switches > Settings > Configuration Audit page.

Provisioning Aruba Gateways Using UI-based Configuration Method

For SD-Branch deployments with Aruba Gateways, the following recommendations apply:

  • Combine Branch Gateways of identical characteristics and configuration requirements under a single group.
  • Create groups according to your branch requirements.
    • You can create separate groups for the small, medium, and large sized branches.
    • You can also create separate groups for the branch sites in different geographical locations; for example, East Coast and West Coast branch sites. If these groups have similar characteristics with minor differences, you can create the first group and then clone it.
    • You can use either a single group for all their devices or deploy devices in multiple groups. For example, you can deploy 7008 controllers and Aruba 2930F Switch Series with 24 ports in a single group for every branch.
    • You can also deploy 7005 controller and Aruba 2930F Switch Series with 24 ports in one group and provision 7008 controller with Aruba 2930F Switch Series with 48 ports in another group.

Important Points to Note

Example

The following figures shows a few sample group deployment scenarios for Aruba Branch Gateways and VPN Concentrators:

Figure 2  Branch Gateway Groups

Figure 3  VPN Concentrator Groups

For more information on how to configure Aruba using UI-based configuration workflows, see the SD-Branch Configuration section in Aruba Central Help Center.

To view local overrides and configuration errors, select a template group and navigate to Devices > Gateways > Settings > Configuration Audit page.