Gateway serviceability

Learn about HPE Aruba Networking serviceability features for gateways which ensure continuous device management. Topics include automatic rollback mechanisms, auto re-provisioning capabilities, and disaster recovery procedures for maintaining uninterrupted connectivity between gateways and the Central platform.

To ensure continuous reachability to gateways, the HPE Aruba Networking Central management platform facilitates essential operations such as configuration, monitoring, debugging, and general management.

Upon initial boot, HPE Aruba Networking AOS-10 gateways in factory default state establish a WebSocket connection with Central through provisioning data obtained via zero-touch provisioning or manual setup.

Subsequent connectivity disruptions might arise from user-initiated configuration errors, network anomalies, or device malfunctions. To mitigate these disruptions, robust device-side recovery mechanisms are supported.

Automatic recovery

Auto rollback

The following configuration errors, including but not limited to those listed, can all disrupt communication between the gateway and HPE Aruba Networking Central:

  • Incorrect uplink VLAN settings
  • Uplink port misconfiguration
  • Bandwidth contract policy restrictions
  • Access control list conflicts

For example, these errors could stem from simple typographical mistakes, rendering corrective actions impossible once connectivity is lost.

Example output for the show switches command showing a configuration state of rollback:

Output for show switches from an HPE Aruba Networking gateway

To address this, AOS-10 gateways implement automatic rollback to the last known good configuration upon detection of connectivity loss due to configuration service updates.

Furthermore, the gateway will communicate the rollback event to the Central configuration service, enabling user visibility and diagnostic capabilities.

Auto re-provisioning

HPE Aruba Networking Central provides an automated solution for connectivity loss detection and restoration, minimizing user intervention to the correction of erroneous configurations.

In scenarios where the initial connection to Central fails due to inaccurate provisioning parameters (e.g., incorrect management URL), or where automatic rollback is unsuccessful (e.g., expired certificates), gateways support self-reprovisioning from the Activate service. Upon user modification of provisioning data, the gateway will initiate a reset and reconnect to Central using the provided information.


Last modified: August 1, 2025 (3d5d521)