Link Search Menu Expand Document

Getting Started

SD-WAN Orchestrator manages all Aruba EdgeConnect appliances in the WAN. From SD-WAN Orchestrator, you can provision, deploy, configure, monitor, and troubleshoot your Aruba SD-WAN regardless of the make, model, or deployment type. SD-WAN Orchestrator manages physical, virtual, and cloud-based Aruba EdgeConnect appliances from a single console.

SD-WAN Orchestrator is a virtual appliance and, therefore, requires a suitable host to run on. It must identify an appropriate host machine with adequate resources to host SD-WAN Orchestrator. Typical deployment locations for SD-WAN Orchestrator are in a Network Operations Center (NOC) or a data center, but any location with efficient access to the WAN devices is suitable.

For more information on SD-WAN Orchestrator requirements, refer to the Orchestrator Host System Requirements.

For licensing, the Orchestrator IP address must be able to reach the Aruba Cloud Portal by using the internet. Allocate an appropriate IP address for the SD-WAN Orchestrator appliance and allow it access through any security components in the environment to the “” domain. (Orchestrator requires port 443 access.)

Deployment Options

This guide explains how to install and upgrade self-deployed Orchestrator deployments. You can self-deploy Orchestrator using the following methods:

  • On-Prem Orchestrator: Hosted on a virtual machine (VM)

  • Orchestrator in IaaS: Hosted in the cloud


Before You Begin

Before you set up SD-WAN Orchestrator and deploy Aruba EdgeConnect appliances, make sure you get the following information from your Aruba SD-WAN representative or from the Silver Peak Support Portal.

  • An account name

  • An account key

  • For Aruba EdgeConnect NX and VX appliances, a valid license.

On-Prem Orchestrator Prerequisites for Initial Installation

Before you deploy On-Prem Orchestrator, make sure you have the following:

  • A hypervisor host with CPU and required memory. See Orchestrator Host System Requirements to determine the required memory for your deployment.

  • The IP address for Orchestrator

  • The Stats Collector configuration (integrated or distributed). See Stats Collector Configuration to determine the best configuration for your deployment.

If you are installing On-Prem Orchestrator, see On-Prem Orchestrator - Download, Deploy Orchestrator, and Install.

Orchestrator in IaaS Prerequisites

Before you deploy Orchestrator in IaaS, make sure you have the following:

  • An existing IaaS account

  • Permission to deploy a VM instance from the Cloud Marketplace into a Virtual Network

  • The Stats Collector configuration (integrated or distributed). See Stats Collector Configuration to determine the best configuration for your deployment.

If you are installing Orchestrator in IaaS, see Orchestrator in IaaS - Deploy.

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