Configuration

The new Configure icon is now visible for devices. Is configuration for existing and new devices supported from now on?

Yes. Details on the supported functionality are available in Provision the Network.

Can device-level configurations, such as interface IP for a gateway, be pre-staged a few days before bringing up the new gateway?

Yes. You can use the Inventory card in the NOC to assign the device to a function before it is moved from a Classic Central group to a HPE Aruba Networking Central group. In this state, the device-level scope is unlocked and the configuration can be staged. Interface profiles can also be used to apply standard port configurations at the device level.

Where can I find prerequisites for configuration?

Refer to the Central Configuration Readiness document.

What tool is available for configuration troubleshooting?

The Configuration Health tool provides detailed visibility into the configuration synchronization status of devices. It identifies any mismatches with HPE Aruba Networking Central, highlights their root causes, and suggests the corresponding corrective actions.

Figure 1: Configuration Health Card

Figure 2: Configuration Health Table

If a user creates a stack before onboarding devices, does HPE Aruba Networking Central automatically create a VSF profile for those devices? What happens if a VSF profile already exists?

Yes. When devices are onboarded, HPE Aruba Networking Central automatically generates a stack profile as part of the onboarding and configuration absorption workflow. This automatic creation applies only to newly onboarded devices.

If a VSF profile already exists, HPE Aruba Networking Central ensures that there is no conflict. The new profile is created only when required and does not interfere with any existing VSF profiles in the system.

Can a switch port be configured as a colorless port in the same way as setting static access or trunk ports?

Yes. Colorless port configuration is supported. For additional details, refer to AAA Authentication Profile.

Can interface profiles be assigned to a device? What if I need to have more than one profile for different switches at a site?

Yes. You can create port profiles and reuse them as needed. In the Interface Configuration panel, select a port profile and assign it to device interfaces. Multiple interfaces can be configured with the same profile using the Apply Port Profile option. Additionally, you can use Device Groups to deploy profiles across multiple switches at a site.

For additional details, see Interfaces Profiles.

What is the easiest way to identify the source of a profile applied to a switch - whether it is originating from the global, site collection, site, or local level? Can this be checked for a single switch or across multiple switches?

The device-level view displays all applied profiles along with the hierarchy level from which each profile originates. This view clearly indicates whether a profile is inherited from global, site collection, site, or local configuration of the device.

What is the recommended way to view the configuration of a switch without navigating to each profile?

To view the switch configuration, navigate to the Troubleshoot page, then select the Commands tab. Scroll down and use the Show Running-Config option.

In Classic Central, the administrator password was inherited from the group level by default. What is the default CLI password for administrators in HPE Aruba Networking Central for switches?

There is no default CLI password. The password is determined by the user administration profile and must be configured by the administrator.

Can multiple port profiles be created within a single site? Is it possible to apply different profiles based on specific requirements, such as floor-wise or department-wise configurations?

Yes. Multiple port profiles can be created within a site. However, only one interface profile can be assigned for a specific switch persona at a time. Bulk deployment of port profiles is supported.

How can the same configuration be applied to all uplinks on a switch?

A port profile can be configured to create Link Aggregation Groups (LAGs). Assigning the same port profile to multiple switch ports generates a LAG with the specified ID, and this configuration can be deployed in bulk using interface profiles at the site or global level.

If a LAG is used as an uplink during HPE Aruba Networking Central onboarding and the native VLAN needs to be changed, can this workflow be automated in HPE Aruba Networking Central?

LAGs must currently be configured at the device level. The native VLAN can be modified manually on the device.

Does a VSF stack need to be formed before moving the conductor to a HPE Aruba Networking Central group or site?

A stack can be formed before onboarding. A VSF profile is also available post onboarding stacking. If the intention is to stack after onboarding, the auto stacking workflow is easier to execute due to automatic configuration import.

When multiple policies are assigned to a role under role-based policies, are they enforced in a top-down order of precedence?

Yes. Policies and rules follow a top-down precedence order.

Can the static IP address be left blank since it may change from site to site, or is it better to create it at the site level rather than the library level?

No. The static IP address must be created at the device level. While the configuration profile that allows static IP can be defined at a higher scope (Site or Library), the unique IP value itself is a device-specific parameter and must be manually configured at the device scope.

The static IP address or device-level parameter is not visible for a profile. Where can I find them?

Device-level parameters are not displayed in shared profiles because they cannot be shared across multiple devices. The local profile option must be used to access and configure these parameters.

Under the Device Function for gateways, only Mobility Gateway is listed. However, Branch Gateway and VPNC are missing.

Currently, HPE Aruba Networking Central supports only the Mobility Gateway device function. Future updates will provide support for Branch Gateway and VPNC.

Are there any limitations on WLAN or AP Overlay configuration scope?

Yes. WLAN configuration, including the assignment of override roles, is typically managed hierarchically.

Is there a way to reduce the number of clicks required to configure something?

Yes. Device profiles can be used to streamline configuration, which reduces the number of interactions needed after the initial setup.

Does HPE Aruba Networking Central display any message or indication that a device is synchronizing configuration or that the configuration is out of sync?

Yes. You can check the configuration health status in one of the following pages:

  • NOC View—

    1. Select the site, then click Network.

    2. From the Devices table, open the Table menu, and click Customize Columns.

    3. Select Configuration Status check box, and click Apply.

  • Audit Trail—Review the logs for configuration sync details.

Do access points and switches typically support Rollback feature?

Yes, access points and switches can rollback to a previously known working configuration for enhanced reliability.

What happens if I make configuration changes while a device is in Support Mode, Disaster Recovery mode, or when HPE Aruba Networking Central is disabled?

In HPE Aruba Networking Central, configuration changes made while a device is in Support Mode, Disaster Recovery mode, or when HPE Aruba Networking Central is disabled are not saved in the configuration database. As a result, these changes are not retained or synchronized when the device reconnects.

You must make configuration changes only through the HPE Aruba Networking Central WebUI or APIs. Changes made outside of HPE Aruba Networking Central may be overwritten or lost.

What is required for HPE Aruba Networking Central to manage an AP device for configuration?

• The AP device must be associated with a site.

• The AP device must be moved into a HPE Aruba Networking Central group.

Should I create roles or policies before creating an underlay WLAN profile?

No, HPE Aruba Networking Central automatically creates a default rule under Policy > sys_allow_all.

Does HPE Aruba Networking Central support Instant AP configuration?

Currently, HPE Aruba Networking Central does not support Instant AP configuration.

Does HPE Aruba Networking Central support Microbranch AP configuration?

Currently, HPE Aruba Networking Central does not support Microbranch AP configuration.

What happens when my AP managed by a Classic Central group is moved to HPE Aruba Networking Central?

When an AP is moved from a Classic Central–managed group to HPE Aruba Networking Central, its configuration is immediately managed by HPE Aruba Networking Central. The Classic Central configuration is no longer applied, and the AP will adopt the configuration settings defined in HPE Aruba Networking Central for its new group.

Where can I set the AP hostname when I am unable to find it in the Library?

You can set the AP hostname under Device Level > System Information.

Where can I configure the country code of the AP?

You can configure the country code of the AP under AP System > Country Code. The country code is automatically configured by default. When the AP is associated with the correct site, it inherits the proper country code without manual configuration.

What is the default access username and password of the AP?

• Default access username/password: admin/<AP SN>, unless an AP admin profile is created.

• You can update the initial admin password during onboarding under User Administrator > admin.

What should I do to override the configuration and change the profile scope?

To override the configuration, select Save as a local profile in the Edit Profile page to set a local override and change the profile scope. The scope remains unchanged when a profile is updated to prevent users from selecting an undesired scope. However, updating a profile will always affect its hierarchy level, regardless of whether the profile is shared or local. For more information on configuring the local profile, see Local Profiles.

How can I bulk update AP hostnames?

Currently, bulk hostname update is not supported in the HPE Aruba Networking Central WebUI. This feature is planned for future sprints.

What should I pay attention while creating policies or rules for AP devices?

For AP devices, the source must always be roles while creating rules.

Why cannot I access Classic Central configuration WebUIs for groups that are managed by HPE Aruba Networking Central while navigating HPE Aruba Networking Central from Classic Central?

Because HPE Aruba Networking Central takes over AP configuration, the system does not allow configuration from both Classic Central and HPE Aruba Networking Central at the same time. This is expected behavior.