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 the Cloud CPE solution, see . When you obtain node servers and 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 node servers and servers for the Cloud CPE or SD-WAN solution.
Table 1: Specification for Node Servers and Servers
Item | Requirement |
|---|---|
Storage | Greater than 750 GB of one of the following types:
|
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 small, medium, or large deployment.
Table 2 shows the required hardware specifications for node servers and 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 Node Servers and Servers, because some additional resources are required for the system software.
Table 2: Server Requirements
Function | Small Deployment | Medium Deployment | Large Deployment |
|---|---|---|---|
Contrail Service Orchestration (CSO) Servers | |||
Note: If you install a small deployment 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 small deployment does not include Junos Space. For information about Junos Space VM requirements, see Table 3. | |||
Number of nodes or servers | 1 | 4 | 9
|
vCPUs per node or server | 40 | 48 | 48 |
RAM per node or server | 224 GB | 256 GB | 256 GB |
Contrail Analytics Servers | |||
Number of servers | None—Contrail Analytics is in a VM | None—Contrail Analytics is in a VM | 3 |
vCPUs per node or server | — | — | 48 |
RAM per node or server | — | — | 256 GB |
Contrail Cloud Platform for a Centralized Deployment Note: These servers are not needed for Hybrid WAN or SD-WAN solutions | |||
Number of nodes or servers | 1 | 4–8
| 4–28
|
vCPUs per node or server | 4 | 48 | 48 |
RAM per node or server | 16 GB | 256 GB | 256 GB |
Total Numbers of Servers | |||
Centralized deployment | 2 | 7–11 | 10–34 |
Hybrid WAN or SD-WAN | 1 | 4 | 9 |
Minimum Requirements for VMs on CSO Node Servers and 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 a small deployment, see Table 3.
For a medium deployment, see Table 4.
For a large deployment, see Table 5.
For information about the ports that must be open on VMs for all deployments, see Table 6.
Use small deployments for managing approximately 450 sites. You cannot configure high availability with small deployments.
Table 3 shows details about the VMs for a small deployment.
Table 3: Details of VMs for a Small Deployment
Name of VM | Components That Installer Places in VM | Resources Required |
|---|---|---|
csp-installer-vm | — |
|
csp-central-infravm | Third-party applications used as infrastructure services |
|
csp-central-msvm | All microservices, including GUI applications |
|
csp-contrailanalytics-1 | Contrail Analytics for a distributed deployment For a centralized or combined deployment, you use Contrail Analytics in the Contrail Cloud Platform. |
|
csp-regional-sblb | Load balancer for device to Fault Management Performance Management (FMPM) microservice connectivity |
|
csp-space-vm (optional) | Junos Space Virtual Appliance and database—required only if you deploy virtualized network functions (VNFs) that use this EMS |
|
csp-vrr-vm | Virtual route reflector (VRR) |
|
csp-central-k8mastervm | Central K8 Master VM |
|
Use medium deployments for approximately 3500 sites. High availability is supported on medium deployments.
Table 4 shows details about the VMs for a medium deployment.
Table 4: Details of VMs for a Medium Deployment
Name of VM or Microservice Collection | Components That Installer Places in VM | Resources Required |
|---|---|---|
csp-installer-vm | — |
|
csp-central-infravm1 | Third-party applications used as infrastructure services |
|
csp-central-infravm2 | Third-party applications used as infrastructure services |
|
csp-central-infravm3 | Third-party applications used as infrastructure services |
|
csp-central-lbvm1 | Load-balancing applications |
|
csp-central-lbvm2 | Load-balancing applications |
|
csp-central-lbvm3 | Load-balancing applications |
|
csp-central-msvm1 | All microservices, including GUI applications |
|
csp-central-msvm2 | All microservices, including GUI applications |
|
csp-central-msvm3 | All microservices, including GUI applications |
|
csp-space-vm | Junos Space Virtual Appliance and database—required only if you deploy VNFs that use this EMS |
|
csp-central-elkvm1 | Logging applications |
|
csp-central-elkvm2 | Logging applications |
|
csp-central-elkvm3 | Logging applications |
|
csp-contrailanalytics-1 | Contrail Analytics for a distributed deployment. For a centralized or combined deployment, you use Contrail Analytics in the Contrail Cloud Platform. |
|
csp-contrailanalytics-2 | Contrail Analytics for a distributed deployment. For a centralized or combined deployment, you use Contrail Analytics in the Contrail Cloud Platform. |
|
csp-contrailanalytics-3 | Contrail Analytics for a distributed deployment. For a centralized or combined deployment, you use Contrail Analytics in the Contrail Cloud Platform. |
|
csp-regional-sblb1 | Load balancer for device to FMPM microservice connectivity |
|
csp-regional-sblb2 | Load balancer for device to FMPM microservice connectivity |
|
csp-vrr-vm1 | Virtual route reflector (VRR) |
|
csp-vrr-vm2 | Virtual route reflector (VRR) |
|
csp-vrr-vm3 | Virtual route reflector (VRR) |
|
csp-vrr-vm4 | Virtual route reflector (VRR) |
|
Use large deployments for managing approximately 5000 sites. High availability is supported on medium deployments.
Table 5 shows details about the VMs for a large deployment.
Table 5: Details of VMs for a Large Deployment
Name of VM or Microservice Collection | Components That Installer Places in VM | Resources Required |
|---|---|---|
csp-installer-vm | — |
|
csp-central-infravm1 | Third-party applications used as infrastructure services |
|
csp-central-infravm2 | Third-party applications used as infrastructure services |
|
csp-central-infravm3 | Third-party applications used as infrastructure services |
|
csp-central-lbvm1 | Load-balancing applications |
|
csp-central-lbvm2 | Load-balancing applications |
|
csp-central-lbvm3 | Load-balancing applications |
|
csp-central-msvm1 | All microservices, including GUI applications |
|
csp-central-msvm2 | All microservices, including GUI applications |
|
csp-central-msvm3 | All microservices, including GUI applications |
|
csp-regional-infravm1 | Third-party applications used as infrastructure services |
|
csp-regional-infravm2 | Third-party applications used as infrastructure services |
|
csp-regional-infravm3 | Third-party applications used as infrastructure services |
|
csp-regional-msvm1 | All microservices, including GUI applications |
|
csp-regional-msvm2 | All microservices, including GUI applications |
|
csp-regional-msvm3 | All microservices, including GUI applications |
|
csp-space-vm (optional) | Junos Space Virtual Appliance and database—required only if you deploy VNFs that use this EMS |
|
csp-central-elkvm1 | Logging applications |
|
csp-central-elkvm2 | Logging applications |
|
csp-central-elkvm3 | Logging applications |
|
csp-regional-elkvm1 | Logging applications |
|
csp-regional-elkvm2 | Logging applications |
|
csp-regional-elkvm3 | Logging applications |
|
csp-regional-sblb1 | Load balancer for device to FMPM microservice connectivity |
|
csp-regional-sblb2 | Load balancer for device to FMPM microservice connectivity |
|
csp-vrr-vm1 | Virtual route reflector (VRR) |
|
csp-vrr-vm2 | Virtual route reflector (VRR) |
|
csp-vrr-vm3 | Virtual route reflector (VRR) |
|
csp-vrr-vm4 | Virtual route reflector (VRR) |
|
csp-vrr-vm5 | Virtual route reflector (VRR) |
|
csp-vrr-vm6 | Virtual route reflector (VRR) |
|
csp-contrailanalytics-1 | Contrail Analytics for a distributed deployment. For a centralized or combined deployment, you use Contrail Analytics in the Contrail Cloud Platform. |
|
csp-contrailanalytics-2 | Contrail Analytics for a distributed deployment. For a centralized or combined deployment, you use Contrail Analytics in the Contrail Cloud Platform. |
|
csp-contrailanalytics-3 | Contrail Analytics for a distributed deployment. For a centralized or combined deployment, you use Contrail Analytics in the Contrail Cloud Platform. |
|
Table 6 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 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 6: 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 |