Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Minimum Requirements for Servers and VMs

    Minimum Hardware Requirements for Node Servers and Servers

    For information about the makes and models of node servers and servers that you can use in Contrail Service Orchestration, see COTS Node Servers and Servers Tested in the Cloud CPE Solution. When you obtain node servers and servers for Contrail Service Orchestration, 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 nodes and servers for Contrail Service Orchestration.

    Table 1: Specification for Nodes and Servers

    Item

    Requirement

    Storage

    Greater than 1 TB of one of the following types:

    • Serial Advanced Technology Attachment (SATA)

    • Serial Attached SCSI (SAS)

    • Solid-state drive (SSD)

    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 node servers and servers that you require depends on whether you are installing a demonstration (demo) or a production environment, and whether you require high availability (HA).

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

    Table 2: Server Requirements

    Function

    Demo Environment without HA

    Demo Environment with HA

    Production Environment without HA

    Production Environment with HA

    Contrail Service Orchestration (CSO) Servers

    Note: If you use a demo environment without HA and with virtualized network functions (VNFs) that require Junos Space as the Element Management System (EMS), you must install Junos Space on a VM on another server. This server specification for a demo environment without HA does not accommodate Junos Space. For information on Junos Space VM requirements, see Table 3.

    Number of nodes or servers

    1

    3

    2

    • 1 central server

    • 1 regional server

    6

    • 3 central servers

    • 3 regional servers

    vCPUs per node or server

    48

    48

    48

    48

    RAM per node or server

    256 GB

    256 GB

    256 GB

    256 GB

    Contrail Analytics Servers for a Hybrid WAN or SD-WAN Deployment

    Number of servers

    None—Contrail Analytics is in a VM

    None—Contrail Analytics is in a VM

    1

    3

    vCPUs per node or server

    48

    48

    RAM per node or server

    256 GB

    256 GB

    Contrail Cloud Platform for a Centralized Deployment

    Number of nodes or servers

    1

    4–8

    • 3 nodes for Contrail controller and analytics

    • 1–4 Contrail compute nodes

    4–28

    • 3 nodes for Contrail controller and analytics

    • 1–25 Contrail compute nodes

    4–28

    • 3 nodes for Contrail controller and analytics

    • 1–25 Contrail compute nodes

    vCPUs per node or server

    16

    48

    48

    48

    RAM per node or server

    64 GB

    256 GB

    256 GB

    256 GB

    Total Numbers of Servers

    Centralized deployment

    2

    7–11

    6–30

    10–34

    Hybrid WAN or SD-WAN

    1

    3

    3

    9

    Minimum Requirements for VMs on CSO Node Servers or Servers

    The number and minimum requirements for CSO VMs depends on the deployment environment and whether or not you use HA:

    • For a demo environment without HA, see Table 3.

    • For a demo environment with HA, see Table 4.

    • For a production environment without HA, see Table 5.

    • For a production environment with HA, see Table 6.

    For information about the ports that must be open on all VMs for all deployment environments, see Table 7.

    Table 3 shows complete details about the VMs for a demo environment without HA.

    Table 3: Details of VMs for a Demo Environment

    Name of VM

    Components That Installer Places in VM

    Resources Required

    csp-installer-vm

    • 4 vCPUs

    • 32 GB RAM

    • 300 GB hard disk storage

    csp-central-infravm

    Third-party applications used as infrastructure services

    • 4 CPU

    • 32 GB RAM

    • 200 GB hard disk storage

    csp-central-msvm

    All microservices, including GUI applications

    • 4 vCPUs

    • 32 GB RAM

    • 200 GB hard disk storage

    csp-regional-infravm

    Third-party applications used as infrastructure services

    • 4 vCPUs

    • 24 GB RAM

    • 200 GB hard disk storage

    csp-regional-msvm

    All microservices, including GUI applications

    • 4 vCPUs

    • 24 GB RAM

    • 200 GB hard disk storage

    csp-regional-sblb

    Load balancer for device to Fault Management Performance Management (FMPM) microservice connectivity

    • 4 vCPUs

    • 8 GB RAM

    • 300 GB hard disk storage

    csp-space-vm

    Junos Space Virtual Appliance and database—required only if you deploy virtualized network functions (VNFs) that use this EMS

    • 4 vCPUs

    • 16 GB RAM

    • 200 GB hard disk storage

    csp-contrailanalytics-1

    Contrail Analytics for a distributed deployment

    For a centralized or combined deployment, you use Contrail Analytics in the Contrail Cloud Platform.

    • 8 vCPUs

    • 48 GB RAM

    • 500 GB hard disk storage

    csp-vrr-vm

    Virtual route reflector (VRR)

    • 4 vCPUs

    • 8 GB RAM

    • 200 GB hard disk storage

    csp-central-k8mastervm

    Central K8 Master VM

    • 4 vCPUs

    • 8 GB RAM

    • 200 GB hard disk storage

    csp-regional-k8mastervm

    Regional K8 Master VM

    • 4 vCPUs

    • 8 GB RAM

    • 200 GB hard disk storage

    Note: For non-HA demo configurations, we recommend one server with 48 vCPUs and 256 GB RAM. Non-HA demo configurations have been validated with a server with 24 vCPUs and 256GB RAM, but performance issues may occur over longer periods of time.

    Table 4 shows complete details about the VMs for a demo environment with HA.

    Table 4: Details of VMs for a Demo Environment with HA

    Name of VM or Microservice Collection

    Components That Installer Places in VM

    Resources Required

    csp-installer-vm

    • 4 vCPUs

    • 48 GB RAM

    • 300 GB hard disk storage

    csp-central-infravm1

    Third-party applications used as infrastructure services

    • 4 vCPUs

    • 32 GB RAM

    • 500 GB hard disk storage

    csp-central-infravm2

    Third-party applications used as infrastructure services

    • 4 vCPUs

    • 32 GB RAM

    • 500 GB hard disk storage

    csp-central-infravm3

    Third-party applications used as infrastructure services

    • 4 vCPUs

    • 32 GB RAM

    • 500 GB hard disk storage

    csp-central-lbvm1

    Load-balancing applications

    • 4 vCPUs

    • 16 GB RAM

    • 300 GB hard disk storage

    csp-central-lbvm2

    Load-balancing applications

    • 4 vCPUs

    • 16 GB RAM

    • 300 GB hard disk storage

    csp-central-lbvm3

    Load-balancing applications

    • 4 vCPUs

    • 16 GB RAM

    • 300 GB hard disk storage

    csp-central-msvm1

    All microservices, including GUI applications

    • 8 CPUs

    • 64 GB RAM

    • 500 GB hard disk storage

    csp-central-msvm2

    All microservices, including GUI applications

    • 8 vCPUs

    • 64 GB RAM

    • 500 GB hard disk storage

    csp-central-msvm3

    All microservices, including GUI applications

    • 8 vCPUs

    • 64 GB RAM

    • 500 GB hard disk storage

    csp-regional-infravm1

    Third-party applications used as infrastructure services

    • 4 vCPUs

    • 32 GB RAM

    • 500 GB hard disk storage

    csp-regional-infravm2

    Third-party applications used as infrastructure services

    • 4 vCPUs

    • 32 GB RAM

    • 500 GB hard disk storage

    csp-regional-infravm3

    Third-party applications used as infrastructure services

    • 4 vCPUs

    • 32 GB RAM

    • 500 GB hard disk storage

    csp-regional-msvm1

    All microservices, including GUI applications

    • 8 CPUs

    • 32 GB RAM

    • 500 GB hard disk storage

    csp-regional-msvm2

    All microservices, including GUI applications

    • 8 CPUs

    • 32 GB RAM

    • 500 GB hard disk storage

    csp-regional-msvm3

    All microservices, including GUI applications

    • 8 CPUs

    • 32 GB RAM

    • 500 GB hard disk storage

    csp-regional-lbvm1

    Load-balancing applications

    • 4 vCPUs

    • 16 GB RAM

    • 300 GB hard disk storage

    csp-regional-lbvm2

    Load-balancing applications

    • 4 vCPUs

    • 16 GB RAM

    • 300 GB hard disk storage

    csp-regional-lbvm3

    Load-balancing applications

    • 4 vCPUs

    • 16 GB RAM

    • 300 GB hard disk storage

    csp-space-vm

    Junos Space Virtual Appliance and database—required only if you deploy VNFs that use this EMS

    • 4 vCPUs

    • 16 GB RAM

    • 300 GB hard disk storage

    csp-contrailanalytics-1

    Contrail Analytics for a distributed deployment

    For a centralized or combined deployment, you use Contrail Analytics in the Contrail Cloud Platform.

    • 16 vCPUs

    • 48 GB RAM

    • 300 GB hard disk storage

    csp-regional-sblb1

    Load balancer for device to FMPM microservice connectivity

    • 4 vCPUs

    • 24 GB RAM

    • 300 GB hard disk storage

    csp-regional-sblb2

    Load balancer for device to FMPM microservice connectivity

    • 4 vCPUs

    • 24 GB RAM

    • 300 GB hard disk storage

    csp-vrr-vm

    Virtual route reflector (VRR)

    • 4 vCPUs

    • 8 GB RAM

    • 200 GB hard disk storage

    Table 5 shows complete details about the VMs required for a production environment without HA.

    Table 5: Details of VMs for a Production Environment Without HA

    Name of VM or Microservice Collection

    Components That Installer Places in VM

    Resources Required

    csp-installer-vm

    • 4 vCPUs

    • 64 GB RAM

    • 300 GB hard disk storage

    csp-central-infravm

    Third -party applications used as infrastructure services

    • 16 vCPUs

    • 64 GB RAM

    • 500 GB hard disk storage

    csp-central-msvm

    All microservices, including GUI applications

    • 16 vCPUs

    • 64 GB RAM

    • 500 GB hard disk storage

    csp-regional-infravm

    Third -party applications used as infrastructure services

    • 16 vCPUs

    • 64 GB RAM

    • 500 GB hard disk storage

    csp-regional-msvm

    All microservices, including GUI applications

    • 16 vCPUs

    • 64 GB RAM

    • 500 GB hard disk storage

    csp-regional-sblb

    Load balancer for device to microservice connectivity

    • 4 vCPUs

    • 32 GB RAM

    • 300 GB hard disk storage

    csp-space-vm

    Junos Space Virtual Appliance and database—required only if you deploy VNFs that use this EMS

    • 4 vCPUs

    • 32 GB RAM

    • 300 GB hard disk storage

    csp-central-elkvm

    Logging applications

    • 4 vCPUs

    • 32 GB RAM

    • 300 GB hard disk storage

    csp-regional-elkvm

    Logging applications

    • 4 vCPUs

    • 32 GB RAM

    • 300 GB hard disk storage

    csp-vrr-vm

    VRR

    • 4 vCPUs

    • 8 GB RAM

    • 200 GB hard disk storage

    csp-central-k8mastervm

    Central K8 Master VM

    • 4 vCPUs

    • 8 GB RAM

    • 200 GB hard disk storage

    csp-regional-k8mastervm

    Regional K8 Master VM

    • 4 vCPUs

    • 8 GB RAM

    • 200 GB hard disk storage

    csp-contrailanalytics-1

    Contrail Analytics for a distributed deployment.

    For a centralized or combined deployment, you use Contrail Analytics in the Contrail Cloud Platform.

    • 4 vCPUs

    • 256 GB RAM

    • 300 GB hard disk storage

    Table 6 shows complete details about the VMs for a production environment with HA.

    Table 6: Details of VMs for a Production Environment with HA

    Name of VM or Microservice Collection

    Components That Installer Places in VM

    Resources Required

    csp-installer-vm

    • 4 vCPUs

    • 32 GB RAM

    • 300 GB hard disk storage

    csp-central-infravm1

    Third-party applications used as infrastructure services

    • 16 vCPUs

    • 64 GB RAM

    • 500 GB hard disk storage

    csp-central-infravm2

    Third-party applications used as infrastructure services

    • 16 vCPUs

    • 64 GB RAM

    • 500 GB hard disk storage

    csp-central-infravm3

    Third-party applications used as infrastructure services

    • 16 vCPUs

    • 64 GB RAM

    • 500 GB hard disk storage

    csp-central-lbvm1

    Load-balancing applications

    • 4 vCPUs

    • 32 GB RAM

    • 300 GB hard disk storage

    csp-central-lbvm2

    Load-balancing applications

    • 4 vCPUs

    • 32 GB RAM

    • 300 GB hard disk storage

    csp-central-lbvm3

    Load-balancing applications

    • 4 vCPUs

    • 32 GB RAM

    • 300 GB hard disk storage

    csp-central-msvm1

    All microservices, including GUI applications

    • 16 vCPUs

    • 64 GB RAM

    • 500 GB hard disk storage

    csp-central-msvm2

    All microservices, including GUI applications

    • 16 vCPUs

    • 64 GB RAM

    • 500 GB hard disk storage

    csp-central-msvm3

    All microservices, including GUI applications

    • 16 vCPUs

    • 64 GB RAM

    • 500 GB hard disk storage

    csp-regional-infravm1

    Third-party applications used as infrastructure services

    • 16 vCPUs

    • 64 GB RAM

    • 500 GB hard disk storage

    csp-regional-infravm2

    Third-party applications used as infrastructure services

    • 16 vCPUs

    • 64 GB RAM

    • 500 GB hard disk storage

    csp-regional-infravm3

    Third-party applications used as infrastructure services

    • 16 vCPUs

    • 64 GB RAM

    • 500 GB hard disk storage

    csp-regional-msvm1

    All microservices, including GUI applications

    • 16 vCPUs

    • 64 GB RAM

    • 500 GB hard disk storage

    csp-regional-msvm2

    All microservices, including GUI applications

    • 16 vCPUs

    • 64 GB RAM

    • 500 GB hard disk storage

    csp-regional-msvm3

    All microservices, including GUI applications

    • 16 vCPUs

    • 64 GB RAM

    • 500 GB hard disk storage

    csp-regional-lbvm1

    Load-balancing applications

    • 4 vCPUs

    • 32 GB RAM

    • 300 GB hard disk storage

    csp-regional-lbvm2

    Load-balancing applications

    • 4 vCPUs

    • 32 GB RAM

    • 300 GB hard disk storage

    csp-regional-lbvm3

    Load-balancing applications

    • 4 vCPUs

    • 32 GB RAM

    • 300 GB hard disk storage

    csp-space-vm

    Junos Space Virtual Appliance and database—required only if you deploy VNFs that use this EMS

    • 4 vCPUs

    • 32 GB RAM

    • 300 GB hard disk storage

    csp-central-elkvm1

    Logging applications

    • 4 vCPUs

    • 32 GB RAM

    • 300 GB hard disk storage

    csp-central-elkvm2

    Logging applications

    • 4 vCPUs

    • 32 GB RAM

    • 300 GB hard disk storage

    csp-central-elkvm3

    Logging applications

    • 4 vCPUs

    • 32 GB RAM

    • 300 GB hard disk storage

    csp-regional-elkvm1

    Logging applications

    • 4 vCPUs

    • 32 GB RAM

    • 300 GB hard disk storage

    csp-regional-elkvm2

    Logging applications

    • 4 vCPUs

    • 32 GB RAM

    • 300 GB hard disk storage

    csp-regional-elkvm3

    Logging applications

    • 4 vCPUs

    • 32 GB RAM

    • 300 GB hard disk storage

    csp-regional-sblb1

    Load balancer for device to FMPM microservice connectivity

    • 4 vCPUs

    • 32 GB RAM

    • 300 GB hard disk storage

    csp-regional-sblb2

    Load balancer for device to FMPM microservice connectivity

    • 4 vCPUs

    • 32 GB RAM

    • 300 GB hard disk storage

    csp-regional-sblb3

    Load balancer for device to FMPM microservice connectivity

    • 4 vCPUs

    • 32 GB RAM

    • 300 GB hard disk storage

    csp-vrr-vm

    Virtual route reflector (VRR)

    • 4 vCPUs

    • 32 GB RAM

    • 300 GB hard disk storage

    Table 7 shows the ports that must be open on all CSO VMs to enable the following types of CSO communications:

    • External—CSO user interface (UI) and CPE connectivity

    • Internal—Between CSO components

    The provisioning tool opens these ports on each VM; however, if you provision the VMs manually, you must manually open the ports on each VM.

    Table 7: Ports to Open on CSO VMs

    Port Number

    CSO Communication Type

    Port Function

    22

    External and internal

    SSH

    80

    Internal

    HAProxy

    83

    External

    Network Service Designer

    179

    External

    BGP for VRR

    443

    External and internal

    HTTPS, including Administration Portal and Customer Portal

    514

    Internal

    Syslog receiving port

    1414

    Internal

    Cassandra Java Virtual Machine (JVM)

    1936

    External

    HAProxy status page

    1947

    External

    Icinga service

    2181

    Internal

    ZooKeeper client

    2379

    Internal

    etcd client communication

    2380

    Internal

    etcd peer

    2888

    Internal

    ZooKeeper follower

    3000

    External

    Grafana

    3306

    Internal

    MySQL

    3514

    External

    Contrail Analytics Syslog receiving port

    3888

    Internal

    ZooKeeper leader

    4001

    Internal

    SkyDNS etcd discover

    4505, 4506

    Internal

    Salt communications

    5000

    External

    Keystone public

    5044

    Internal

    Beats

    5543

    Internal

    Logstash UDP

    5601

    External

    Kibana UI

    5665

    Internal

    Icinga API

    5666

    Internal

    icinga nrpe

    5671

    Internal

    RabbitMQ SSL listener

    5672

    Internal

    RabbitMQ client

    6000

    Internal

    Swift Object Server

    6001

    Internal

    Swift Container Server

    6002

    Internal

    Swift Account Server

    6379

    Internal

    Redis

    6543

    Internal

    Virtualized Network Function manager (VNFM)

    7804

    External

    Device connectivity

    8006

    Internal

    Network Service Orchestrator

    8016

    Internal

    Notification engine

    8080

    Internal

    cAdvisor

    8082

    Internal

    Device Management Service (DMS) central

    8083

    Internal

    Activation Service (AS) central

    8085

    Internal

    DMS Schema

    8086

    Internal

    Contrail Analytics

    8090, 8091

    Internal

    Generic container

    8529

    Internal

    ArangoDB

    9042

    Internal

    Cassandra native transport

    9090

    Internal

    Swift Proxy Server

    9091

    Internal

    xmltec-xmlmail tcp

    9101

    External and internal

    HA proxy exporter

    9102

    Internal

    jetdirect

    9160

    Internal

    Cassandra

    9200

    Internal

    Elasticsearch

    10248

    Internal

    kubelet healthz

    15100

    Internal

    Logstash TCP

    15672

    Internal

    RabbitMQ management

    30000-32767

    Internal

    Kubernetes service node range

    30900

    External

    Prometheus

    35357

    Internal

    Keystone private

    Modified: 2018-05-10