Install on AWS

For Releases 16.1R2 and later.

This article describes how to install the Versa headend components on AWS.

Before You Begin

Before you install the Versa headend infrastructure on AWS:

• From Versa Networks Customer Support, obtain the CloudFormation template link to host the AWS CloudFormation
template. The CloudFormation templates are described in the next section.
• Edit the Mapping section of the JSON template, adding the AMI ID for the images shared by Versa Networks
Customer Support in the Tenant Account section and in the region where headend is to be deployed.
• Ensure that your AWS account can access the Versa headend AMIs. To have Versa provide access to the AMIs,
contact Versa Customer Support and give them your account ID.
• Locate or create the key pair to use to launch the AWS stack. You need this key pair to log in to Versa Analytics,
Versa Director, and Versa SD-WAN Controller. If you do not have this key pair, generate it by logging in to the AWS
console as the AWS admin user.

Note that if you have never run an Ubuntu instance in your AWS account, you must accept the AWS terms and
conditions before you can launch a CloudFormation template. To accept the terms, go to the EC2 console page,
manually launch an instance of Ubuntu 14.04, and accept the terms and conditions. You can then immediately terminate
or delete this instance.

CloudFormation Templates
You use AWS CloudFormation templates to deploy a set of AWS resources. A template is a simple text file that
describes a stack, which is a collection of AWS resources that you want to deploy together as a group. Here, the cloud
resources are the Versa headend infrastructure, which consists of Versa Director, Versa Analytics, and Versa Controller.
(You can also provision a standalone Versa provider edge (PE) router using CloudFormation templates.) When you
launch a stack, the Versa headend infrastructure described in the template is provisioned. Placing all the cloud
resources in a single stack allows you to manage them together as a group instead of having to manage the individual
resources.

The AWS CloudFormation template is a JSON or YAML formatted text file. Versa Networks provides the JSON files to
use as AWS CloudFormation templates. To obtain these files, contact Versa Networks Customer Support, at

https://docs.versa-networks.com/Getting_Started/Deployment_and_Initial_Configuration/Headend_Deployment/Installation/In…
Updated: Thu, 06 Aug 2020 19:23:06 GMT
Copyright © 2020, Versa Networks, Inc.
1
[email protected].

Versa Networks leverages CloudFormation template capabilities to bring up the headend infrastructure, which consists
of Director, Analytics, and Controller. To provision standalone PE router, you use variants of the CloudFormation
template.

The following table lists the Versa JSON CloudFormation template files and describes the resources that each template
creates. Note that while a PE router is not a headend component, it is required for some topologies.

EIP Availab
Template Vera Versa Versa Versa PE VPC
(for VPC Zone
Name Analytics Controller Director Router Gateway
Transport) Selecti

aws-basic-
1 1 1 — — 1 No No
headend.json

aws-basic-
single- — — — 1 1 1 No No
flexvnf.json

aws-basic-
single-flexvnf-
— — — 1 2 1 No No
dual-
transport.json

aws-direct-
1
connect-sf-sc- 2 1 1 — 1 Yes No
(Standalone)
sd-da.json

aws-direct-
connect-sf-sc- 1
2 1 1 — 1 Yes No
sd-da- (Standalone)
backup.json

single-
— — — 1 1 — No No
FlexVNF.json

aws-sf-sc-sd-
1 1 1 1 per VPC
sa- — 2 Yes Yes
per VPC per VPC per VPC (Standalone)
primary.json

aws-sf-sc-sd-
3 1 1 1 per VPC
sa-da- — 2 Yes Yes
per VPC per VPC per VPC (Standalone)
secondary.json

Note that last template in the table, aws-sf-sc-sd-sa-da-secondary.json, provisions a single Versa FlexVNF PE router
(sf), a single Versa Controller (sc), a single Versa Director (sd), a single Versa Analytics (sa) and a dual Versa Analytics
(da).

https://docs.versa-networks.com/Getting_Started/Deployment_and_Initial_Configuration/Headend_Deployment/Installation/In…
Updated: Thu, 06 Aug 2020 19:23:06 GMT
Copyright © 2020, Versa Networks, Inc.
2
The CloudFormation templates perform the following actions:

• Creates all the necessary infrastructure to host the Versa headend infrastructure. An example of the infrastructure is
illustrated in the figure in Set Up Headend Infrastructure, below.
• Creates the following infrastructure:
◦ Amazon Virtual Private Cloud (VPC) and the default VPC network 10.234.0.0/16
◦ Subnetworks to connect your headend nodes
◦ Routing tables
◦ Network interfaces for each headend component
◦ Public IP addresses for Versa Director and Versa SD-WAN Controller
◦ Security group rules
◦ Internet gateway for the VPC
◦ EC2 instances for Versa Director, and Versa SD-WAN Controller, and Versa Analytics
• Generates a client certificate for Versa Director and copies it to Versa Analytics
• Executes Versa Director and Versa Analytics initialization scripts
• Edits the /etc/ssh/sshd_config path in Versa Controller to enable password-based login from the Versa Director
management address. Note that all other password-based login to the EC2 instances is disabled for security
reasons. By default, only public key–based authentication is allowed.
• Sets up appropriate routing configurations on all the EC2 instances
• Installs static routes 10.0.0.0/16 and 10.1.0.0/16 in the Versa Director towards the branches

Set Up Headend Infrastructure

To install the Versa headend components on AWS, you use CloudFormation templates to set up the infrastructure for
the headend:

1. Log in to the AWS Management Console.

2. In the Services tab:
a. Select Management & Governance > CloudFormation.
b. Click Create Stack.

3. In the Create Stack menu, click Select Template. Choose a template and Specify an Amazon template URL to
form the CloudFormation template. Then click Next.

https://docs.versa-networks.com/Getting_Started/Deployment_and_Initial_Configuration/Headend_Deployment/Installation/In…
Updated: Thu, 06 Aug 2020 19:23:06 GMT
Copyright © 2020, Versa Networks, Inc.
3
4. In the Create Stack menu:
a. Click Specify Details.
b. Select Amazon EC2 Parameters, and from the drop-down menu select a key pair to use to log in to your
instances.
c. Click Next.

5. In the Create Stack menu:

a. Click Options.
b. Configure Tags, Permissions, Rollback Triggers, and Advanced options.
c. Click Next.

6. In the Create Stack menu:

a. Click Review.
b. Verify the Template, Details, and Options information.
c. Click Create.

https://docs.versa-networks.com/Getting_Started/Deployment_and_Initial_Configuration/Headend_Deployment/Installation/In…
Updated: Thu, 06 Aug 2020 19:23:06 GMT
Copyright © 2020, Versa Networks, Inc.
4
After you create the stack, wait for at least 10 minutes before logging in to any of the Versa headend infrastructures.
During this time, additional scripts are running that complete the creation of the Versa headend infrastructure and set up
connectivity details.

The figure below illustrates a sample headend topology deployed in AWS. The first two bytes of the IP addresses,
shown in the figure as X.X, are taken from the IPv4 address you entered for the VPC. The second two bytes of the IP
address are assigned by the CloudFormation template.

Access Versa Headend EC2 Instances

For out-of-band management access to the EC2 instances for Versa headend components, you open an SSH
connection to the eth0 nterface using the key pair PEM file for authentication. The eth0 interface is used for out-of-band
management.

To access the Versa Director EC2 instance:

ssh -i /path_to_key/my_key.pem Administrator@<Director IP address>

To launch the Versa Director user direction, use the following command:

https://<Director IP address>

;To access the Versa Analytics EC2 instance:

ssh -i /path_to_key/my_key.pem versa@<Analytics IP address>

To access the EC2 instance of the FlexVNF that is acting as the Versa Controller or of the provider edge (PE) router:

https://docs.versa-networks.com/Getting_Started/Deployment_and_Initial_Configuration/Headend_Deployment/Installation/In…
Updated: Thu, 06 Aug 2020 19:23:06 GMT
Copyright © 2020, Versa Networks, Inc.
5
 ssh -i /path_to_key/my_key.pem admin@<Controller IP address>
ssh -i /path_to_key/my_key.pem admin@<PE router IP address>

Software Release Information

Releases 16.1R2 and later support all content described in this article.

Additional Information
Hardware and Software Requirements for Headend
Headend Initial Configuration
Headend Overview
Headend Verification
Qualified AWS and Azure Instances

https://docs.versa-networks.com/Getting_Started/Deployment_and_Initial_Configuration/Headend_Deployment/Installation/In…
Updated: Thu, 06 Aug 2020 19:23:06 GMT
Copyright © 2020, Versa Networks, Inc.
6