Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Minimum Requirements for Servers and VMs

 

Minimum Hardware Requirements for Servers

For information about the makes and models of servers that you can use in the Cloud CPE solution, see . When you obtain servers for the Cloud CPE and 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 the Cloud CPE or 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 in the supported deployments. 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

Function

Standalone Deployment

HA Deployment

Contrail Service Orchestration (CSO) Servers

Number of nodes or servers

1

3

vCPUs per node or server

48

48

RAM per node or server

256 GB

256 GB

Minimum Requirements for VMs on CSO servers

The number of VMs needed and minimum requirements for CSO VMs depend on the deployment environment and whether or not you use high availability (HA):

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

Table 3 shows details about the VMs for a standalone deployment. You need 6 Virtual Machines (VMs) including Virtual Route Reflector (VRR) and 1 public IP address for deploying all the required services.

Note

For ESXi deployment, all the VMs must have 500 GB of hard disk storage. For KVM deployment VM storage requirements, refer to Table 3.

Table 3: Details of VMs for a Standalone Deployment

Name of VM

Components That Installer Places in VM

Resources Required

startupserver_1

Installer VM

  • 4 vCPUs

  • 16 GB RAM

  • 550 GB hard disk storage

k8-infra_1

Third-party applications used as infrastructure services

  • 10 CPU

  • 64 GB RAM

  • 500 GB hard disk storage

k8-microservices_1

All microservices, including GUI applications

  • 8 CPU

  • 64 GB RAM

  • 250 GB hard disk storage

csp-vrr-vm1

Virtual route reflector (VRR)

  • 4 vCPUs

  • 8 GB RAM

monitoring_1

Monitoring VM

  • 6 vCPUs

  • 16 GB RAM

  • 100 GB hard disk storage

contrail_analytics_1

Contrail Analytics server

  • 12 vCPUs

  • 48 GB RAM

  • 500 GB hard disk storage

Table 4 shows details about the VMs for a HA deployment.

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

Note

For ESXi deployment, all the VMs must have 500 GB of hard disk storage. For KVM deployment VM storage requirements, refer to Table 4.

Table 4: Details of VMs for a HA Deployment

Name of VM or Microservice Collection

Components That Installer Places in VM

Resources Required

startupserver_1

Startup server VM

  • 4 vCPUs

  • 16 GB RAM

  • 400 GB hard disk storage

k8-infra_1

Third-party applications used as infrastructure services

  • 10 vCPUs

  • 64 GB RAM

  • 500 GB hard disk storage

k8-infra_2

Third-party applications used as infrastructure services

  • 10 vCPUs

  • 64 GB RAM

  • 500 GB hard disk storage

k8-infra_3

Third-party applications used as infrastructure services

  • 10 vCPUs

  • 64 GB RAM

  • 500 GB hard disk storage

k8-microservices_1

All microservices, including GUI applications

  • 10 CPUs

  • 64 GB RAM

  • 250 GB hard disk storage

k8-microservices_2

All microservices, including GUI applications

  • 10 vCPUs

  • 64 GB RAM

  • 250 GB hard disk storage

k8-microservices_3

All microservices, including GUI applications

  • 10 vCPUs

  • 64 GB RAM

  • 250 GB hard disk storage

monitoring_1

Monitoring applications

  • 4 vCPUs

  • 24 GB RAM

  • 250 GB hard disk storage

monitoring_2

Monitoring applications

  • 4 vCPUs

  • 24 GB RAM

  • 250 GB hard disk storage

monitoring_3

Monitoring applications

  • 4 vCPUs

  • 24 GB RAM

  • 250 GB hard disk storage

contrail_analytics_1

Contrail Analytics for a distributed deployment.

  • 12 vCPUs

  • 48 GB RAM

  • 500 GB hard disk storage

contrail_analytics_2

Contrail Analytics for a distributed deployment.

  • 12 vCPUs

  • 48 GB RAM

  • 500 GB hard disk storage

contrail_analytics_3

Contrail Analytics for a distributed deployment.

  • 12 vCPUs

  • 48 GB RAM

  • 500 GB hard disk storage

proxy_1

Proxy VM

  • 2 vCPUs

  • 8 GB RAM

  • 100 GB hard disk storage

proxy_2

Proxy VM

  • 2 vCPUs

  • 8 GB RAM

  • 100 GB hard disk storage

k8-master1

Kubernetes master node

  • 2 vCPUs

  • 4 GB RAM

  • 100 GB hard disk storage

k8-master2

Kubernetes master node

  • 2 vCPUs

  • 4 GB RAM

  • 100 GB hard disk storage

k8-master3

Kubernetes master node

  • 2 vCPUs

  • 4 GB RAM

  • 100 GB hard disk storage

csp-vrr-vm1

Virtual route reflector (VRR) VM

  • 4 vCPUs

  • 32 GB RAM

csp-vrr-vm2

Virtual route reflector (VRR) VM

  • 4 vCPUs

  • 32 GB RAM

proxy_sblb1

Proxy VM—Southbound

  • 2 vCPUs

  • 8 GB RAM

  • 400 GB hard disk storage

proxy_sblb2

Proxy VM—Southbound

  • 2 vCPUs

  • 8GB RAM

  • 400 GB hard disk storage

Table 5 shows the ports that must be open on all CSO VMs 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 5: 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

NAT_IP:500

ISAKMP

External

OAMHUB IPSEC connection

NAT_IP:4500

IPSec

External

OAMHUB IPSEC connection

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

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

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:90

TCP

External

Apache to salt master