- play_arrow Overview
- play_arrow Understanding Contrail Controller
-
- play_arrow Installing and Upgrading Contrail
- play_arrow Supported Platforms and Server Requirements
- play_arrow Installing Contrail and Provisioning Roles
- Contrail Roles Overview
- Downloading Installation Software
- Installing the Operating System and Contrail Packages
- Configuring System Settings
- Installing the Contrail Packages, Part One (CentOS or Ubuntu)
- Setting Up the Testbed Definitions File
- Testbed Definitions File Settings for Deploying Contrail with an Existing OpenStack Node
- Supporting Multiple Interfaces on Servers and Nodes
- Installing the Contrail Packages, Part Two (CentOS or Ubuntu) — Installing on the Remaining Machines
- Configuring the Control Node with BGP
- Adding or Removing a Compute Node in an Existing Contrail Cluster
- Contrail Global Controller
- Role and Resource-Based Access Control
- play_arrow Installation and Configuration Scenarios
- Setting Up and Using a Simple Virtual Gateway with Contrail
- Configuring MD5 Authentication for BGP Sessions
- Configuring OpenStack Nova Docker with Contrail
- Configuring the Data Plane Development Kit (DPDK) Integrated with Contrail vRouter
- Configuring Single Root I/O Virtualization (SR-IOV)
- Configuring Virtual Networks for Hub-and-Spoke Topology
- Configuring Transport Layer Security-Based XMPP in Contrail
- Configuring Graceful Restart and Long-lived Graceful Restart
- play_arrow Using Contrail with VMware vCenter
- play_arrow Using Contrail with Red Hat
- play_arrow Using Server Manager to Automate Provisioning
- play_arrow Extending Contrail to Physical Routers, Bare Metal Servers, Switches, and Interfaces
- Using ToR Switches and OVSDB to Extend the Contrail Cluster to Other Instances
- Configuring High Availability for the Contrail OVSDB ToR Agent
- Using Device Manager to Manage Physical Routers
- SR-IOV VF as the Physical Interface of vRouter
- Using Gateway Mode to Support Remote Instances
- REST APIs for Extending the Contrail Cluster to Physical Routers, and Physical and Logical Interfaces
- play_arrow Installing and Using Contrail Storage
- play_arrow Upgrading Contrail Software
-
- play_arrow Configuring Contrail
- play_arrow Configuring Virtual Networks
- Creating Projects in OpenStack for Configuring Tenants in Contrail
- Creating a Virtual Network with Juniper Networks Contrail
- Creating a Virtual Network with OpenStack Contrail
- Creating an Image for a Project in OpenStack Contrail
- Creating a Floating IP Address Pool
- Using Security Groups with Virtual Machines (Instances)
- Support for IPv6 Networks in Contrail
- Configuring EVPN and VXLAN
- play_arrow Example of Deploying a Multi-Tier Web Application Using Contrail
- play_arrow Configuring Services
- play_arrow Configuring Service Chaining
- play_arrow Examples: Configuring Service Chaining
- play_arrow Adding Physical Network Functions in Service Chains
- play_arrow Configuring High Availability
- play_arrow Configuring Multitenancy Support
- play_arrow Load Balancers
- play_arrow Optimizing Contrail
-
- play_arrow Monitoring and Troubleshooting Contrail
- play_arrow Configuring Traffic Mirroring to Monitor Network Traffic
- play_arrow Understanding Contrail Analytics
- play_arrow Configuring Contrail Analytics
- Analytics Scalability
- High Availability for Analytics
- System Log Receiver in Contrail Analytics
- Sending Flow Messages to the Contrail System Log
- Ceilometer Support in a Contrail Cloud
- User Configuration for Analytics Alarms and Log Statistics
- Node Memory and CPU Information
- Role- and Resource-Based Access Control for the Contrail Analytics API
- play_arrow Using Contrail Analytics to Monitor and Troubleshoot the Network
- Monitoring the System
- Debugging Processes Using the Contrail Introspect Feature
- Monitor > Infrastructure > Dashboard
- Monitor > Infrastructure > Control Nodes
- Monitor > Infrastructure > Virtual Routers
- Monitor > Infrastructure > Analytics Nodes
- Monitor > Infrastructure > Config Nodes
- Monitor > Networking
- Query > Flows
- Query > Logs
- Understanding Flow Sampling
- Example: Debugging Connectivity Using Monitoring for Troubleshooting
- play_arrow Common Support Answers
-
- play_arrow Contrail Commands and APIs
- play_arrow Contrail Commands
- play_arrow Contrail Application Programming Interfaces (APIs)
-
- play_arrow Downloads
Provisioning a Cloud Spoke Site in AWS VPC
Use the following high-level steps to provision a vSRX cloud spoke site in Amazon Web Services (AWS) virtual private cloud (VPC).
Before you begin:
Set up your Amazon Web Services (AWS) account.
Identify the virtual private cloud (VPC) to which the AWS spoke site must be provisioned.
Install licenses to use vSRX features. Choose any of the following AWS vSRX Image Licenses.
Bring Your Own License (BYOL)— If you plan to use a BYOL, then you must install the license to the device before deploying CSO SD-WAN functionality. See https://aws.amazon.com/marketplace/pp/B01LYWCGDX.
License included. See https://aws.amazon.com/marketplace/pp/B01NAUWN0G.
Ensure that you have the supported software version for the AWS spoke.
Reserve two elastic IP addresses on AWS.
Reserve two public IP addresses.
To set up and monitor your network:
Add a Cloud Spoke Site
To add a cloud spoke site:
- Select Sites > Site Management > Add > Cloud Spoke.
- Specify the site information such as, site name, AWS region, VPC ID, management subnet, IP prefix and click Next.
- Specify vSRX as SD-WAN spoke in AWS as the connection
plan. Note
Only Hub-Spoke topology is supported for AWS cloud spoke site.
Only Internet link is supported for WAN underlay connections.
- Provide the WAN details and click Next.
The WAN traffic page appears, displaying a set of values for the WAN link configuration.
- Specify additional requirements and click Next.
- Specify LAN segment information and click Next.
- In the Summary tab, check the configuration and click Edit to modify the settings.
- Click OK to save the changes.
The new cloud spoke site that you created appears in the Sites page.
Configure the Cloud Spoke Site
To configure a cloud spoke site:
- Select Sites > Site Management .
The sites page appears.
- Select the cloud spoke site that you created and click Configure Site.
The configure site page appears.
- In the Connectivity tab, specify the primary hub site detail, overlay tunnel information, and WAN interface details.
- Click Ok.
- Click Devices tab and enter the activation code provided by your service provider.
- Click Ok
The site status is changed to Configured.
Download the Cloud Formation Template
To download the cloud formation template:
- Click Resources > Devices.
- Identify the device that you want to activate.
You can activate a device if it has the status as Expected.
- Select the device and click Activate Device.
The Activate device page appears.
- Enter the activation code supplied by the service provider.
You can download the cloud formation template after you enter the correct activation code.
- Click Download to download the cloud formation
template.
The template is downloaded to your local computer in JSON format.
Provision the Device on AWS Server
CSO creates cloud formation template with stage-1 configuration bundled in JSON format. You must download this template and then upload to AWS to provision the vSRX. The cloud formation template creates the required resources such as subnet, interface, vSRX and so on and applies the stage-1 configuration.
To provision the device on AWS server:
- Log in to your AWS account.
If you have already logged in to your AWS account, the Create Stack page appears.
If you are not logged into your AWS account, a new Web page opens in your browser, displaying the AWS login information. Log in to your AWS account.
TipIf you do not see the Create Stack page when you log in to or access your AWS account, then search for CloudFormation service.
The Create Stack page appears.
- Select CloudFormation > Stacks > Create Stack > Upload a template to Amazon S3.
- Click Choose File and select the cloud formation template that you downloaded in JSON format .
- Click Next.
- Specify the Stack name. For example, Oregonstack.
- Specify the Custom Image Id for the vSRX.
You must ensure that you have the supported software image for the AWS spoke. If the image is unavailable on the AWS marketplace, you must do the following to get the AMI number for your desired region:
- Log in into the Administration Portal.
- Select Resources > Device Templates.
The Device Template page appears.
- Select vSRX as SD-WAN spoke in AWS.
- Select Edit Device Template > Template Settings.
The Template Settings page appears.
- Modify the image ID to the AMI ID for your region.
- Click Save.
- Paste the AMI ID in the CustomImageId field.
NoteYou must specify the Custom Image ID field because not doing so results in failure during stack creation or provisioning.
- In the Parameters section, specify the KeyName for your EC2 instance.
- Click Next.
- Select I acknowledge that AWS CloudFormation might create IAM Resources.
- Click Create.
The Create Stack pages displays a list of existing stacks and indicates that it is creating the stack that you requested. The create stack process takes up to 30 minutes. if the process does not complete in 30 minutes, a timeout occurs and you need to retry the process.
Activate the Device
To activate the device:
- After the create stack process is complete, return to
the Customer Portal and click Next.
The Activate Device page displays a status indicating that CSO is detecting the provisioning agent. This process takes up to 30 minutes. if the process does not complete in 30 minutes, a timeout occurs and you need to retry the process.
NoteYou need not download the cloud formation template again. You can log in to the Customer Portal, access the Activate Device page, enter the activation code and click Next. After the CREATE_COMPLETE message is displayed on the AWS server, click Next on the Activate Device page to proceed with device activation.
If the spoke on AWS has been spawned successfully on AWS, it will contact CSO through outbound SSH connection. The device is detected and normal ZTP, process is triggered. The rest of the workflow is consistent with the normal on-premise workflow.
On Device Activation page, the device is activated through the following steps:
Detecting the device
Applying stage-one configuration to the device
Bootstrapping of device
Activating the device
After each successful step, you can see a green check mark. If any of these steps fails, a red exclamation mark appears.
- After the activation process is complete, click OK.
The Sites page appears. To see the device activation status, hover over the device icon on the Sites page.
