Link Search Menu Expand Document

Reachability Tab

Administration > Tools > Monitoring > Reachability Status

The Reachability tab provides status details on communications between your appliances and Orchestrator, which helps in early detection of network or communication failures that might occur over direct or Portal WebSockets.

Orchestrator provides automatic WebSocket failover from direct WebSocket to Aruba Cloud Portal WebSocket if communications over the direct WebSocket fail or become stale. You can control how quickly failover occurs by selecting one of three failover modes: Aggressive, Normal (default), or Slow. For details, see Select Fast WebSocket Failover Mode below.


The listed appliances reflect all appliances in your network or those selected in the appliance tree.

The Ping Interval (Sec) and Max Idle Time (Sec) columns reflect the current WebSocket failover mode configuration. The other columns show live data. Click the refresh button to update this data. You can also click Export to export the data to a CSV file.

The following table describes fields on the Reachability tab.

Field Description
Appliance Name of the appliance.
Direct WebSocket Status of the appliance connection to Orchestrator by direct WebSocket (Connected or Not Connected).
Appliance Portal WebSocket Status of the appliance connection to Orchestrator by Aruba Cloud Portal WebSocket (Connected, Connected Secure, or Not Connected).

“Connected Secure” indicates that the end-to-end encryption feature is enabled (the endToEndEncryptionEnabled property on the Orchestrator Advanced Properties dialog box is set to “true”) and the appliance is running on an ECOS version that supports the feature.

NOTE: If Air-Gap is enabled, this status is always “Not Connected” because the Aruba Cloud Portal is not being accessed. Appliance activation, license management, and other supporting functions are performed through the Air-Gap Portal. Users manually exchange data between Aruba Cloud Portal and the EdgeConnect SD-WAN network. Air-Gap is available only for self-hosted Orchestrator deployments. For details, see Air-Gap.
Active Channel Currently active communication channel (Via Direct WebSocket or Via Portal WebSocket) that Orchestrator is using to communicate with the appliance.
Last Direct WebSocket Message When the last message (ping or any other message) was received from this appliance. This is the actual time that Orchestrator tracks.
Ping Interval (Sec) Ping interval in seconds. The appliance polls the Orchestrator at the passing of every ping interval to confirm reachability over the direct WebSocket. This value reflects the current WebSocket failover mode selection. To change the mode, see Select Fast WebSocket Failover Mode below.

If Orchestrator does not receive a message on the direct WebSocket within the Redirection Time as configured for the failover mode, Orchestrator redirects communications to the Portal WebSocket if it is available.
Max Idle Time (Sec) Maximum idle time in seconds. Orchestrator closes the direct WebSocket with the appliance if a message is not received from the appliance within the Max Idle Time. This value reflects the current WebSocket failover mode selection. To change the mode, see Select Fast WebSocket Failover Mode below.

The appliance will attempt to re-open the direct WebSocket to Orchestrator. If successful, Orchestrator will redirect traffic to the direct WebSocket.
Sync State Synchronization state of the appliance and Orchestrator databases. Possible synchronization states are:

Normal – The Orchestrator and appliance databases are synchronized, and communications are running normally across the active channel.

Not synchronized – Databases for Orchestrator and the appliance are not synchronized.

Synchronization in progress – Synchronization is occurring between the Orchestrator and appliance databases.

Unknown – The appliance’s transitional state when initially added to the network.

Unreachable – A problem exists in your network. Check your ports, firewalls, and deployment configuration.

Unsupported – The appliance is running on an unsupported ECOS version.

This tab provides the following links:

  • Cloud Portal – Click to view current configuration and registration information for the Cloud Portal connection. You can also view HTTPS and WebSocket reachability statuses.

  • Orchestrator Reachability – Click to view how your appliances are connecting to Orchestrator, including the default Orchestrator IP address or domain name, whether the Orchestrator management IP is being used, and any labels used to connect to Orchestrator.

  • Software Versions – Click to view active and inactive software versions for all appliances in your network or those selected in the appliance tree.

Select Fast WebSocket Failover Mode

You can use the Fast WebSocket Failover Mode dialog box to select a mode for WebSocket failover to the Portal WebSocket when the direct WebSocket fails or becomes stale.

Before you change this mode, consider the following:

  • Changes to failover mode affect all appliances on your network. You cannot set this mode for individual appliances.

  • The WebSocket failover mode feature requires appliance version or later. Appliances on earlier versions remain in Legacy mode. Changing the failover mode on this dialog box does not affect Legacy mode on these appliances.

  • Faster WebSocket failover requires greater resource utilization (such as with CPU or bandwidth).

To change the mode:

  1. Click Change WebSocket Failover Mode on the Reachability tab.

    The Fast WebSocket Failover Mode dialog box opens.

  2. Select a mode.

    The following table describes the WebSocket failover modes. You cannot change the configurations for these modes.

    Field Description
    Aggressive The most optimal mode for most network configurations.

    Mode configurations: 30 seconds for Redirection Time, 60 seconds for Max Idle Time, and 10 seconds for Ping Interval.
    Normal The default mode for appliances running on ECOS version or later.

    NOTE: If Orchestrator is upgraded to version 9.4.2, existing appliances running on ECOS versions earlier than will operate in Legacy mode, even though the setting displayed on this dialog box for those appliances will be Normal (by default). These appliances ignore changes to Aggressive, Normal, or Slow mode and continue to operate in Legacy mode.

    Mode configurations: 60 seconds for Redirection Time, 120 seconds for Max Idle Time, and 20 seconds for Ping Interval.
    Slow Select this mode if you are experiencing resource issues (such as with CPU or bandwidth).

    Mode configurations: 90 seconds for Redirection Time, 180 seconds for Max Idle Time, and 30 seconds for Ping Interval.
    Legacy Appliances running on ECOS versions earlier than operate in this mode regardless of the mode selected on this dialog box. You can also set this mode for all appliances in your network. This mode is not recommended because of latency concerns.

    Mode configurations: 10 minutes for Redirection Time, 10 minutes for Max Idle Time, and 120 seconds for Ping Interval.
  3. Click Save.

    Changes to failover mode are orchestrated. Updates can take a while to propagate across the network. Appliances will rebuild direct WebSocket connections.

Back to top

© Copyright 2024 Hewlett Packard Enterprise Development LP.

To view the end-user software agreement, go to HPE Aruba Networking EULA.

Open Source Code:

This product includes code licensed under certain open source licenses which require source compliance. The corresponding source for these components is available upon request. This offer is valid to anyone in receipt of this information and shall expire three years following the date of the final distribution of this product version by Hewlett Packard Enterprise Company. To obtain such source code, please check if the code is available in the HPE Software Center at but, if not, send a written request for specific software version and product for which you want the open source code. Along with the request, please send a check or money order in the amount of US $10.00 to:

Hewlett Packard Enterprise Company
Attn: General Counsel
WW Corporate Headquarters
1701 E Mossy Oaks Rd Spring, TX 77389
United States of America