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
• Provisioning Switches Using UI-based Configuration Method
• Provisioning HPE Aruba Networking Gateways Using UI-based Configuration Method

Provisioning Instant APs using UI-based Configuration Method

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

• Instant AP Cluster—Consists of a conductor Instant AP and member Instant APs in the same VLAN Virtual Local Area Network. In computer networking, a single Layer 2 network may be partitioned to create multiple distinct broadcast domains, which are mutually isolated so that packets can only pass between them through one or more routers; such a domain is referred to as a Virtual Local Area Network, Virtual LAN, or VLAN..
• VC—A virtual controller. VC provides an interface for entire cluster. The member Instant APs and conductor Instant APs function together to provide a virtual interface.
• Conductor Instant AP and Member Instant AP—In typical Instant AP deployment scenario, the first Instant AP that comes up is elected as the conductor Instant AP. All other Instant APs joining the cluster function as the member Instant APs. When a conductor Instant AP is configured, the member Instant APs download the configuration changes. The conductor Instant AP may change as necessary from one device to another without impacting network performance.

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

• Per group configuration—Classic 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 SSID Service 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 Classic 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 Classic 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: Manually assign them to an existing group. Create a new group.	If an Instant AP with non-default or custom configuration joins Classic 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.

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 Classic 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 Configuring Instant APs in Classic Central.

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

Classic Central allows switches to join UI groups only if the switches are running factory default configuration. Classic 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.

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

• Per group configuration— Classic 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 switches within a group can have common VLAN settings.
• Per Device Configuration—Although the Switches inherit group configuration, the users can maintain device-specific configuration, for example, ports or DHCP Dynamic Host Configuration Protocol. A network protocol that enables a server to automatically assign an IP address to an IP-enabled device from a defined range of numbers configured for a given network.  pools.

For more information on how to configure switches using UI-based configuration workflows, see Configuring or Viewing AOS-S 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 HPE Aruba Networking Gateways Using UI-based Configuration Method

For SD-Branch deployments with HPE Aruba Networking 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

• The groups in Classic Central are not device-specific, however, HPE Aruba Networking recommends that you use the following guidelines for provisioning SD-WAN Software-Defined Wide Area Network. SD-WAN is an application for applying SDN technology to WAN connections that connect enterprise networks across disparate geographical locations. Gateways.
  • Assign Branch Gateways and VPN Virtual Private Network. VPN enables secure access to a corporate network when located remotely. It enables a computer to send and receive data across shared or public networks as if it were directly connected to the private network, while benefiting from the functionality, security, and management policies of the private network. This is done by establishing a virtual point-to-point connection through the use of dedicated connections, encryption, or a combination of the two. Concentrators to separate groups. Because the configuration requirements for Branch Gateways and VPN Concentrators are different, the Branch Gateways and VPN Concentrators must be assigned to different groups.
  • Ensure that the configuration group for SD-WAN Wide Area Network. WAN is a telecommunications network or computer network that extends over a large geographical distance. Gateways consists of the same type of devices. For example, Branch Gateways assigned to a group must have the same number of ports.
• Before assigning SD-WAN Gateways to groups, you must set the device persona or role as Branch Gateway or VPN Concentrator.

Example

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

Figure 2  Branch Gateway Groups

Figure 3  VPN Concentrator Groups

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

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