Third-Party Switches

What are the high-level steps for supporting third-party devices in HPE Aruba Networking Central?

The workflow involves the following steps:

1. Provisioning OpsRamp: Perform a one-time deployment and configuration in OpsRamp to enable telemetry collection from third-party switches. This process includes setting up on-premises OpsRamp gateways and configuring SNMP profiles on the switches. The gateway uses these SNMP profiles to collect telemetry data from the third-party switches.

2. Telemetry collection: HPE Aruba Networking Central automatically retrieves telemetry data, such as device states and performance metrics, through the underlying OpsRamp infrastructure.

3. Monitoring in HPE Aruba Networking Central: All third-party switch data is seamlessly integrated into HPE Aruba Networking Central, where you can monitor and analyze the switches alongside native HPE Aruba switches.

What features are currently not supported by Third-Party Device Integration in HPE Aruba Networking Central?

In HPE Aruba Networking Central, the following features are currently not supported for Third-Party Device Integration:

• Connectivity Card

• Topology

• Uplink

• Chassis Switch

• SFP Port Numbering

• Delete Switch from HPE Aruba Networking Central

Do I need a subscription key to enable Third-Party Device Integration?

Yes. To enable Third-Party Device Integration, you must assign an OpsRamp subscription key to your workspace and provision OpsRamp on HPE GreenLake. This allows collection and processing of data from third‑party switches into HPE Aruba Networking Central.

What is the supported mapping of regions and clusters for third‑party device integration in Classic Central?

The following table describes the mapping of the supported deployment regions, cluster names, and corresponding countries.

Table 1: Deployment Regions and Cluster Names Between HPE Aruba Networking Central and OpsRamp

Which OpsRamp account should I select to configure third‑party device integration in Classic Central?

A client account is required to set up the HPE Aruba Networking Central NAC integration and SNMP profiles. This client account is created automatically in OpsRamp. You can select the required client account by navigating to Account Details > Client card, or by fetching it using the Search box.

For more information, see Selecting the Client Account.

Which OpsRamp account should I select to configure third‑party device integration in Classic Central?

You must select the OpsRamp client account that is mapped to your Classic Central account. This ensures that the discovered third‑party devices are correctly exported and displayed in Classic Central.

For more information, see Selecting the Client Account.

Why are there no metric templates associated with the third‑party devices that were discovered?

Metric templates are not automatically associated with third‑party devices after discovery. To enable monitoring, you must enable global policies. This is an essential step to activate all monitoring templates that need to be applied to the discovered devices in order to collect data. In addition, ensure that metrics are enabled at the site level so the devices are monitored correctly.

For more information, see Enabling Global Policies on the Client Account.

How do I configure the Site ID for third‑party devices on OpsRamp so they show up correctly in Classic Central?

To ensure third‑party devices discovered in OpsRamp are displayed under the correct site in Classic Central, you must:

1. Edit the Client – Navigate to the OpsRamp client account that is mapped to your Aruba Central account.

2. Enable Global Policies – Turn on global policies so monitoring templates can be applied to discovered devices.

3. Assign the Site ID – Configure the Site ID in OpsRamp to match the site definitions in Classic Central.

For more information, see Configuring Custom Attributes and Integrations on OpsRamp.

Do I need to enable metric value configuration under Site ID for stats to show up in Classic Central?

Yes. Enabling metric value configuration under the Site ID is required for statistics to be displayed correctly in Classic Central.

For more information, see Configuring Custom Attributes and Integrations on OpsRamp.

Should I change the default query under the Integration page?

No. You should not change the default query.

What kind of gateway should I download to set up the on‑prem SNMP collector?

You should download the Classic Virtual Appliance Gateway (OVA).

What kind of gateway should I download to set up the on‑prem SNMP collector?

You should download the Classic Virtual Appliance Gateway (OVA).

What additional information do I need from OpsRamp to set up the gateway?

You need the API server and activation token from OpsRamp to configure and register the gateway.

Why is the Gateway not able to reach the internet?

Check the Gateway’s web URL (https://<gatewayip>:5480) and verify the network settings. If no proxy is involved, ensure it is set to Direct Connect to Internet. Under General Settings, a correctly registered Gateway should show Registration Status: Registered and Tunnel Status: Established.

How do I move a device from one site to another?

You can move a third‑party switch from one site to another in HPE Aruba Networking Central by updating the site name in OpsRamp.

Why is the Gateway not able to reach the internet?

Check the Gateway’s web URL (https://<gatewayip>:5480) and verify the network settings. If no proxy is involved, ensure it is set to Direct Connect to Internet.

What formats are supported for IP Range in the SNMP profile?

The IP ranges must be in the format IP/Subnet Mask.For example, 192.168.1.0/24.

What protocol options should I select under SNMP configuration?

Under SNMP configuration, you can choose from the following protocol options:

• Discovery only SNMP‑enabled devices

• Use CDP, LLDP

• Link Layer Discovery Protocol (LLDP).

• Use OSPF

• Use BGP