Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Minimum Requirements for Servers and VMs

Minimum Hardware Requirements for Servers

For information about the makes and models of servers that you can use, see Hardware and Software Requirements for Contrail Service Orchestration. When you obtain servers for SD-WAN solution, we recommend that you:

  • Select hardware that was manufactured within the last year.

  • Ensure that you have active support contracts for servers so that you can upgrade to the latest firmware and BIOS versions.

Table 1 shows the specification for the servers for SD-WAN solution.

Table 1: Specification for servers

Item

Requirement

Storage

Storage drive can be one of the following types:

  • Serial Advanced Technology Attachment (SATA)

  • Serial Attached SCSI (SAS)

  • Solid-state drive (SSD)

Note:

Solid-state drive (SSD) is preferred storage for better performance.

CPU

One 64-bit dual processor, type Intel Sandybridge, such as Intel Xeon E5-2670v3 @ 2.4 Ghz or higher specification

Network interface

One 1-Gigabit Ethernet or 10-Gigabit Ethernet interface

The number of servers that you require depends on your deployment.

Table 2 shows the required hardware specifications for servers. The server specifications are slightly higher than the sum of the virtual machine (VM) specifications listed in Minimum Requirements for VMs on CSO Servers, because some additional resources are required for the system software.

Table 2: Server Requirements

Server Specifications

 Without Streaming Services With Streaming Services

Resources Required

Resources Required

Number of nodes or servers

3

3

vCPUs per node or server

48 (56 for ESXi)

96

RAM per node or server

256 GB

320 GB

Minimum Requirements for VMs on CSO Servers

See Table 3 for detailed information on the number of VMs needed and minimum requirements for CSO VMs .

For ESXi deployment, do not deploy more than 1 infrastructure or microservice instance on a single server.

For information about the ports that must be open on VMs for all deployments, see Table 4.

Table 3 shows details about the VMs for a CSO deployment.

You need 22 Virtual Machines (VMs) including Virtual Route Reflector (VRR) for deploying all the required services. If you opt for streaming services, then you need 25 VMs. Additionally you require 3 routable IP addresses, 1 IP address for NAT server and 2 IP addresses for VRR.

Table 3: Details of VMs for CSO Deployment

Name of VM or Microservice Collection

Components That Installer Places in VM

Resources Required

startupserver1

Startup server VM

  • 4 vCPUs

  • 16 GB RAM

  • 1.5 TB hard disk storage

infra1

Third-party applications used as infrastructure services

  • 10 vCPUs

  • 64 GB RAM

  • 500 GB hard disk storage

infra2

Third-party applications used as infrastructure services

  • 10 vCPUs

  • 64 GB RAM

  • 500 GB hard disk storage

infra3

Third-party applications used as infrastructure services

  • 10 vCPUs

  • 64 GB RAM

  • 500 GB hard disk storage

microservices1

All microservices, including GUI applications

  • 20 vCPUs

  • 64 GB RAM

  • 500 GB hard disk storage

microservices2

All microservices, including GUI applications

  • 20 vCPUs

  • 64 GB RAM

  • 500 GB hard disk storage

microservices3

All microservices, including GUI applications

  • 20 vCPUs

  • 64 GB RAM

  • 500 GB hard disk storage

monitoring1

Monitoring applications

  • 4 vCPUs

  • 24 GB RAM

  • 500 GB hard disk storage

monitoring2

Monitoring applications

  • 4 vCPUs

  • 24 GB RAM

  • 500 GB hard disk storage

monitoring3

Monitoring applications

  • 4 vCPUs

  • 24 GB RAM

  • 500 GB hard disk storage

contrailanalytics1

Contrail Analytics for a distributed deployment.

    1. 16 vCPUs for ESXi deployment

    2. 12 vCPUs for KVM deployment

  • 48 GB RAM

  • 500 GB hard disk storage

contrailanalytics2

Contrail Analytics for a distributed deployment.

    1. 16 vCPUs for ESXi deployment

    2. 12 vCPUs for KVM deployment

  • 48 GB RAM

  • 500 GB hard disk storage

contrailanalytics3

Contrail Analytics for a distributed deployment.

    1. 16 vCPUs for ESXi deployment

    2. 12 vCPUs for KVM deployment

  • 48 GB RAM

  • 500 GB hard disk storage

proxy1

Proxy VM

  • 2 vCPUs

  • 8 GB RAM

  • 500 GB hard disk storage

proxy2

Proxy VM

  • 2 vCPUs

  • 8 GB RAM

  • 500 GB hard disk storage

k8master1

Kubernetes master node

  • 2 vCPUs

  • 4 GB RAM

  • 500 GB hard disk storage

k8master2

Kubernetes master node

  • 2 vCPUs

  • 4 GB RAM

  • 500 GB hard disk storage

k8master3

Kubernetes master node

  • 2 vCPUs

  • 4 GB RAM

  • 500 GB hard disk storage

vrr1

Virtual route reflector (VRR) VM

  • 4 vCPUs

  • 32 GB RAM

vrr2

Virtual route reflector (VRR) VM

  • 4 vCPUs

  • 32 GB RAM

sblb1

Proxy VM—Southbound

  • 2 vCPUs

  • 8 GB RAM

  • 500 GB hard disk storage

sblb2

Proxy VM—Southbound

  • 2 vCPUs

  • 8GB RAM

  • 500 GB hard disk storage
The following VMs are available only if you installed streaming services.

streaming1

syslog streaming applications

  • 32 vCPUs

  • 64 GB RAM

  • 2 TB hard disk storage

streaming2

syslog streaming applications

  • 32 vCPUs

  • 64 GB RAM

  • 2 TB hard disk storage

streaming3

syslog streaming applications

  • 32 vCPUs

  • 64 GB RAM

  • 2 TB hard disk storage

Storage Requirements

For KVM hypervisor, OS and Data partitions are automated

For the ESXi hypervisor, each VM must be created with a single partition. All the microservices VMs must be created with an additional separate disk for Swift storage.

To create additional hard disk for each for microservices VM in the ESXi hypervisor:

  1. Open the vSphere Web Client.

  2. Right-click a virtual machine in the inventory and select Edit Settings.

  3. On the Virtual Hardware tab, click New Standard Hard Disk.

  4. Select New Hard Disk from the New device drop-down menu at the bottom of the wizard.

  5. Specify the size of the hard disk.

    Note:

    You must allocate at least 100 GB.

  6. Expand New hard disk and select Thin Provision. Mention appropriate location for storage.

  7. Click Save.

A new disk /dev/sdb will be attached to the VMs.

Port Requirements for CSO VMs

Table 4 and Table 5 show the ports that must be open on all CSO VMs and OAM Hubs to enable the following types of CSO communications:

  • External—CSO UI and CPE connectivity

  • Internal—Between CSO components

The deploy.sh script opens these ports on each VM.

Table 4: Ports to Open on CSO VMs

Port Number

Protocol

CSO Communication Type

Port Function

NAT_IP:443

HTTPs

External

UI Access

NAT_IP:83

TCP

External

Network Service Designer UI

NAT_IP:8060

HTTP

External

Certification Revocation List

VRR_publicIP:22

SSH

External and internal

Secure logins

VRR_publicIP:179

BGP

External

BGP for VRR

NAT_IP:7804

TCP/Netconf

External

Device connectivity

SBLB_IP:514

TCP/Syslog

External

Device syslog receiving port

SBLB_IP:3514

TCP/Syslog

External

Device security log receiving port

SBLB_IP:2216

TCP/gRPC

External

Telemetry data from device

SBLB_IP:6514

TCP

External

Device secure syslog over TLS
Note:

The following ports are only used for troubleshooting. You can either enable or disable it with the same or different NAT.

NAT_IP:1947

TCP

External

Icinga UI

NAT_IP:5601

TCP

External

Kibana UI—CSO log visualizer to trouble shoot

NAT_IP:9210

TCP

External

Elasticsearch

NAT_IP: 15672

TCP

External

RabbitMQ management tool

NAT_IP:5000

TCP

External

Keystone public

NAT_IP:3000

TCP

External

Grafana

NAT_IP:8081

External

Contrail Analytics

NAT_IP:8082

External

Contrail Analytics

NAT_IP:8529

TCP

External

ArangoDB
Table 5: Ports to Open on OAM Hub

OAMHUB_IP:500

ISAKMP

External

OAMHUB IPSEC connection

OAMHUB_IP:4500

IPSec

External

OAMHUB IPSEC connection

OAMHUB_IP:50

Encapsulated Security Protocol (ESP)

External

OAMHUB IPSEC connection

OAMHUB_IP:51

Authentication Header (AH)

External

OAMHUB IPSEC connection

Related Documentation