Prerequisites for HPE Aruba Networking Central

Prerequisites for Optimal Switch Experience

Consider the following pre-requisites for optimal switch experience:

  • The minimum recommended version to leverage all AOS-CX switch features in HPE Aruba Networking Central is 10.13.1110. You can check for any AI-powered switch firmware recommendations in HPE Aruba Networking Central.

  • The minimum recommended firmware version for AOS-S switches is 16.11.0028 or greater.

  • Application Visibility is supported on AOS-CX 6200, 6300, and 6400 switch series.

Prerequisites for Optimal AOS-CX Switch Telemetry

Consider the following pre-requisites for optimal AOS-CX telemetry:

Table 1: Prerequisites
Configuration Use Cases Profile (where configuration must be enabled)

Enable Client IP Tracking (CIPT)
  • Required for Client Insights profiling
  • Required for showing IP address in the Unified Clients List

Switch System Profile(Enabled by default)

Enable Device Fingerprinting (DFP)
  • Required for Client Insights profiling

  • Required for showing hostname in the Unified Clients List

Switch System Profile(Enabled by default)

Enable DHCP snooping and authentication/DHCP Events

Required for wired client connectivity details

DHCP Snooping Profile (Global) and VLAN Profile (At VLAN level)

Enable Traffic Insights and IPFIX

Required for wired client DNS connectivity details

Port Profile for Switches (Enabled by default)

Enable Application Visibility

Required for Application Visibility/TLS from wired clients

App Recognition and Control Profile

Prerequisites for Access Points

Consider the following pre-requisites for optimal access point(AP) experience:

  • All AP platforms. For the complete list of supported AP models, see Supported AP Platforms.

  • Minimum supported firmware version for AP is AOS 10.4.1.7 or greater.

Prerequisites for Gateways

Consider the following pre-requisites for an optimal gateway experience:

  • All gateway platforms. For the complete list of supported gateway models, see Supported Gateway Platforms.

  • Minimum supported firmware version for gateway is AOS 10.4.1.7 or greater.

Prerequisites for HPE GreenLake

Consider the following pre-requisites for HPE GreenLake:

  • HPE GreenLake Scope—Inventory management, subscription management, user login Single Sign-On (SSO), and user role-based access control stay within the HPE GreenLake environment and are not part of HPE Aruba Networking Central. These functions continue to be managed within the HPE GreenLake environment.

  • HPE Aruba Networking Central RBAC—New RBAC resources for HPE Aruba Networking Central are visible for all HPE Aruba Networking Central allow-listed users. These new resources are available in the HPE GreenLake UI under the Identity and Access card.

  • Classic Central—For monitoring inventory, subscriptions, user login SSO, and user role-based access control, utilize the Classic Central UI. HPE Aruba Networking Central does not have the HPE GreenLake banner and these functions are available within the Classic Central UI.

Role-Based Access Control (RBAC)

A role refers to a logical entity used for determining user access to the features available in HPE Aruba Networking Central. Users are always tagged to roles that govern the level of user access to the HPE Aruba Networking Central application and services.

For more information about managing users and roles in the HPE GreenLake portal, see the Manage section in the HPE GreenLake Edge to Cloud Platform User Guide.

If a user's role assignment, including the restricted resource restriction policy (RRP) mapping, has already been configured for HPE Aruba Networking Central application, then when a new region is provisioned under the existing account, the user must update the RRP list to include the groups associated with the newly provisioned region. This ensures uninterrupted access to Classic Central for the newly added region. The role change can take up to 10 minutes to appear in HPE Aruba Networking Central.

Note:

To access HPE Aruba Networking Central, it is recommended that you have built-in roles with full-scope access control . If custom roles are used, users may not observe behavior consistent with the assigned role permissions for applications.

Multi-role support is available in Classic Central and HPE Aruba Networking Central.

For more information, see HPE GreenLake Edge to Cloud Platform User Guide.

For more information about managing users and roles in the HPE GreenLake portal, see the Manage section in the HPE GreenLake Edge to Cloud Platform User Guide.

For more information, see the HPE GreenLake cloud User Guide.