Link Search Menu Expand Document


A physical EdgeConnect appliance can be connected to the internet, licensed, and brought online easily if certain conditions are met. This section helps troubleshoot potential problems in this process.

EdgeConnect Licensing

There are a few important factors to consider when the appliance is online, but is unable to register with the Orchestrator:

  • Does the new EdgeConnect appliance have the correct account name and key listed? Account name is case sensitive. White spaces, typos, or missing letters prevent the appliance from registering with the Orchestrator.
  • If the appliance connects to the Orchestrator via another EdgeConnect appliance, make sure the intermediate appliance is licensed as well.
  • Appliances manually added to the Orchestrator will not be licensed. An appliance can only be added when Orchestrator discovers it.

For additional troubleshooting tips, see Adding a New Appliance.

Orchestrator Licensing

For customer-hosted Orchestrator configurations, the Orchestrator requires account name and key configuration during setup. Orchestrator must be able to contact the Cloud Portal and establish a web socket for ongoing communication. For hosted configurations (Orchestrator-as-a-Service), these settings are confirmed during deployment.

Use the Cloud Portal tab (Orchestrator > Cloud Portal) to confirm the following:

  • Is the Orchestrator reachable?
    • Does the Orchestrator have HTTPS reachability to the Cloud Portal? If not, troubleshoot security policy and DNS configuration.
    • Does the Orchestrator have web socket reachability to the Cloud Portal? If not, a security configuration issue most likely exists in the network.
  • Is the Orchestrator registered?
    • If this is not the first Orchestrator deployed for the network, the new Orchestrator must be approved by a previously deployed Orchestrator.
    • If the Orchestrator has been approved but is still not registered, open a case with Support.

When reaching out to the Orchestrator hosted in the cloud, make sure that:

  • Proper APIs and ports are allowed through the firewall, if traffic is going through the firewall.
  • The Orchestrator name can be resolved via DNS.

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