Onboarding and Access

How do I onboard a new device in HPE Aruba Networking Central?

Refer to the following Quick Start series in the user guide:

What are the key steps for onboarding and pre-provisioning a device in HPE Aruba Networking Central?

  1. In HPE GreenLake, assign the service and subscription for Classic Central to your device to activate its service entitlement.

  2. Create an HPE Aruba Networking Central-enabled Group (labeled New Central in the WebUI) and a Site in Classic Central.

  3. Move devices to the desired Site in Classic Central.

  4. Move devices to the HPE Aruba Networking Central-enabled Group (labeled New Central in the WebUI) in Classic Central.

  5. Assign a device function (for switches only) in HPE Aruba Networking Central and apply the configurations.

For detailed information, refer to the following Quick Start sections:

What steps are essential to ensure a successful pre-provisioning in HPE Aruba Networking Central?

For successful pre-provisioning, ensure that the device is assigned to a Site and an HPE Aruba Networking Central-enabled Group (labeled New Central in the WebUI) in Classic Central. For switches, you must also assign a device function from the Device Inventory page in HPE Aruba Networking Central.

How do I identify an HPE Aruba Networking Central-enabled group?

In the Classic Central WebUI, navigate to Organization > Network Structure > Groups. Look for the New Central label next to the group name in the table. Only these groups support onboarding and pre-provisioning for HPE Aruba Networking Central.

What is a device function, and can it be changed?

Each device must be assigned a device function so it can be managed by HPE Aruba Networking Central. Device functions are assigned as follows:

  • APs and Gateways—The device function is assigned automatically when the device is moved into an HPE Aruba Networking Central-enabled Group (labeled New Central in the WebUI).

  • Switches—The device function must be assigned manually from the Device Inventory page in HPE Aruba Networking Central.

Once a device function has been assigned, it cannot be changed. To modify it, you must unprovision the device from the HPE GreenLake Device Inventory, reprovision it, and then assign the new device function.

How do I verify that my device has been successfully onboarded?

  1. In the Network Overview page, locate the Device Inventory card and click on the device type count.

  2. Search for the device using its MAC Address, Serial Number, or IP Address.

  3. Click the device name to open the device context page.

  4. On the Health card, check the Configuration Status.

    It should display Synchronized if onboarding succeeds.

What firmware version is required for different device types to be onboarded and provisioned successfully in HPE Aruba Networking Central?

  • For details on supported devices and firmware versions per device type, see Supported Devices.

  • Firmware compliance workflows must be managed through Classic Central until firmware management support for AOS-CX is available in HPE Aruba Networking Central.

  • If the firmware version is lower than the supported version, it appears in Configuration Health and cannot be managed for configuration.

Whom should I contact for help with navigation or configuration issues?

You can contact HPE Networking Technical Support via email or hotline for assistance.

How can I provide feedback about a feature or product? How can I submit a Request for Enhancement (RFE) or feature request?

Submit your RFE or feature request in the Innovation Zone.

Do I need to reset the configuration in Classic Central when onboarding gateways?

Yes, if the gateway was previously part of a Classic Central group (including default group) or if the out-of-the-box gateway was not pre-provisioned to a HPE Aruba Networking Central group from Classic Central pre-provision section before connecting to the internet, you need to reset it. However, if the gateway was pre-provisioned and has moved to a HPE Aruba Networking Central group, then resetting the configuration is not required.

What will happen if I skip resetting the configuration in Classic Central and the gateways are working correctly?

If you skip the steps for onboarding gateways into a HPE Aruba Networking Central group and the gateway comes up in a Classic Central (default) group, then you need move the gateway from default group to HPE Aruba Networking Central group and write erase all on the gateway followed by reset config from Classic Central Config Audit section of the HPE Aruba Networking Central group. This will push the initial setup configuration to the cloud as part of the configuration import. If you follow the steps outlined in the documentation, you can avoid issues like the device getting stuck in an update-required state or rolling back.