Migration

Are migration tools provided to move from Classic Central to HPE Aruba Networking Central?

Currently, migration is a manual process. Future updates will introduce tools and detailed guidelines to simplify migration.

Is site migration possible from Classic Central?

Yes. Any site created in Classic Central is automatically synchronized with HPE Aruba Networking Central. Additionally, device movements within the site are also synchronized and reflected in HPE Aruba Networking Central. However, configuration migration (such as templates) remains a manual process.

Can I still use template groups from Classic Central?

Yes. Template groups will remain available until Classic Central configuration is retired. For new deployments, it is recommended to use HPE Aruba Networking Central’s WebUI or API instead.

How is Classic Central treated during the transition?

Classic Central is considered an existing deployment for transition assistance. This means migration support focuses on helping users move from their current setup to the HPE Aruba Networking Central environment.

For Application Performance and Quality of Service (QoS) mismatch, do switches need Application Recognition and Control (ARC) enabled? Is ARC only applicable to AOS-CX switches?

Yes. ARC must be enabled on switches, and it is supported only on AOS-CX switches that provide DPI (Deep Packet Inspection). QoS alerts are supported on all AOS-CX switches, but application-level information is supported only on specific AOS-CX models that support DPI.

How are custom alert configurations in Classic Central migrated to HPE Aruba Networking Central?

HPE Aruba Networking Central has a new alerting and notification framework with additional configuration and notification options. As a result, any custom alert configurations created in Classic Central such as thresholds, severity levels, and notification settings must be reconfigured in HPE Aruba Networking Central.

How are reports created and scheduled in Classic Central migrated to HPE Aruba Networking Central?

HPE Aruba Networking Central has a new reporting framework with additional customization and scheduling options. As a result, all reports created and scheduled in Classic Central must be recreated in HPE Aruba Networking Central using the new framework.

How are devices without site assignments in Classic Central migrated to HPE Aruba Networking Central?

As part of the Classic Central to HPE Aruba Networking Central migration process, any device that is not assigned to a site in Classic Central is assigned to a site in HPE Aruba Networking Central as follows:

  • If the account already has sites created, a new site named Unmapped is created, and all unassigned devices are moved to that site.

  • If the account has no sites created but has groups, HPE Aruba Networking Central automatically creates a site for each group and assigns devices accordingly.

    For example, if a group is named “Residence Hall,” then a site named “Residence Hall – site” is created.