Link Search Menu Expand Document

Adding a New Appliance

This section discusses solutions to problems that could occur when trying to bring an EdgeConnect device into Orchestrator.

Physical EdgeConnect

When a physical EdgeConnect is connected to the internet, its serial number is registered with Cloud Portal. After bootup, it should appear in the Appliances Discovered tab within Orchestrator.

The following interfaces are found on every physical EdgeConnect:

  • WAN interfaces
  • LAN interfaces
  • Management interfaces

NOTE Virtual EdgeConnect appliances must include vNICs, which are discussed later in this guide.

By default, the WAN interfaces and mgmt0 are DHCP-enabled.

Before booting up the appliance, make sure that all connections are properly made. If the appliance does not appear in Orchestrator, take the following steps:

  1. Make sure internet access is available either directly on the appliance or elsewhere on the network that the appliance can access.
  2. Check that the lights on WAN interfaces (WAN0 and/or WAN1) are lit. If not, stop and troubleshoot the physical connectivity to eliminate a potential cabling issue.
  3. Make sure that WAN0 or WAN1 is connected to the internet.
  4. If a device appears as a discovered device with a green Approve Appliances button, it is healthy. If a device comes up as unreachable, examine other elements such as firewalls, next hop, or configuration.
  5. Pay close attention to the messages received, as an appliance can be in the following modes:
    • Normal. Appliance is discovered and working as expected.
    • Unknown. Appliance is in transition state and trying to come up.
    • Unsupported.Appliance is running a code version not supported by Orchestrator.
    • Unreachable. A possible network issue.

Common Issues

Issue Resolution
By policy, an appliance cannot access the internet. Access the local appliance GUI or CLI and configure the Orchestrator name or IP.
Management traffic to the Cloud Portal and/or Orchestrator goes through a proxy. Newer code revisions add a certificate check, which must be disabled. Contact Support.
No DHCP available. Access the local appliance GUI or CLI and configure a WAN interface or mgmt0 with a static IP address.

Virtual EdgeConnect (EC-V)

Most of the steps for physical appliances apply to an EC-V. The important difference is that the account name and account key are not configured in the default installation image and must be specified during installation. This can be done at the appliance GUI by clicking Administration, and then clicking License & Registration.

  • An EC-V vNIC only comes with a mgmt interface. If the EC-V is not in the correct port group, it will not be able to communicate with Orchestrator. The mgmt0 vNIC usually sits outside the traffic data path.
  • You must add proper vNIC interfaces as part of EC-V networking.
  • Be sure the EC-V has connectivity to the internet and to Orchestrator by doing a ping test from the CLI or the EC-V web UI.

The following screenshot illustrates the port mappings in VMware for vNICs. The first vNIC is always the mgmt vNIC in VMware, as shown below. If the mgmt vNIC is not mapped to mgmt0 on the EC-V, the appliance will be unreachable from Orchestrator.

Port Mappings for vNICs

Note the MAC address highlighted above. You will need to assign the same MAC address to the mgmt0 interface on the EC-V, as shown below. You can reach this screen in the Appliance UI from Configuration > Interfaces or Configuration > Initial Config Wizard.

Assigning MAC Address to mgmt0

For current account information, click Orchestrator, and then click Cloud Portal.

Back to top

© Copyright 2024 Hewlett Packard Enterprise Development LP. The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein. Aruba Networks and the Aruba logo are registered trademarks of Aruba Networks, Inc. Third-party trademarks mentioned are the property of their respective owners. To view the end-user software agreement, go to HPE Aruba Networking EULA.

Open Source Code:

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