Getting Started
SD-WAN Orchestrator manages all HPE Aruba Networking EdgeConnect appliances in the WAN. From SD-WAN Orchestrator, you can provision, deploy, configure, monitor, and troubleshoot your SD-WAN Orchestrator regardless of the make, model, or deployment type. SD-WAN Orchestrator manages physical, virtual, and cloud-based 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 HPE Aruba Networking 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 “portal.silverpeak.cloud” 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 EdgeConnect appliances, you will need the account name and account key.
NOTE: Existing customers can follow the steps in New Orchestrator in IaaS Customers to retrieve or generate a new account key.
New On-Prem Orchestrator Customers
If you are a new on-prem Orchestrator customer, you will receive the account name and account key from your HPE Aruba Networking SD-WAN representative, or you will receive an email from Silver Peak containing the account name and account key. If you did not receive the account name and account key from your HPE Aruba Networking SD-WAN representative or via email from Silver Peak, you can log in to the HPE Networking Support Portal to locate the account name and account key.
New Orchestrator in IaaS Customers
If you are a new Orchestrator in IaaS customer, you will receive an email from Silver Peak containing the account name and account key. If you did not receive the account name and account key via email from Silver Peak, follow these steps to locate the account name and account key.
NOTE: Only admin users can retrieve or generate a new account key.
To retrieve an existing account key or generate a new account key:
-
Log in to Orchestrator as an admin user.
-
Navigate to Orchestrator > Orchestrator Server > Licensing > Cloud Portal.
The Cloud Portal dialog box opens.
-
Do one of the following:
-
Click the blue padlock in the Account Key field to view the Account Key. You can copy and paste the account key into an Orchestrator deployment or retain in for your records.
-
Click Generate New Key to generate a new account key.
NOTE: If you generate a new key, the key on the HPE Networking Support Portal will not be updated and will no longer be valid.
-
-
Click Close.
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.