Single Tenant (ST)
The supported instance specifications for the Cisco vManage, Cisco vBond Orchestrators, and Cisco vSmart Controllers are as follows:
Note |
The controller and the device software versions should be the same, to achieve the following scale. |
Instance Type | Specifications (Approximation) | Qualified Instance Type | |||
---|---|---|---|---|---|
vCPUs* | RAM* | Storage Size* | Azure | AWS | |
Small |
16 vCPUs |
32 GB RAM |
500 GB |
Standard_F16s_v2 |
c5.4xlarge |
Medium |
32 vCPUs |
64 GB RAM |
1 TB |
Standard_F32s_v2 |
c5.9xlarge |
Large |
32 vCPUs |
128 GB RAM |
5 TB |
Standard_D32ds_v5 |
c5.18xlarge and m6i.8xlarge |
* vCPU, RAM, and Storage Size numbers are on per Cisco vManage basis. The Storage Size numbers can be sized up to 10 TB for on-prem and customer cloud hosted.
Devices | Nodes and Deployment Models with Instance Type | Data Processing Factor | Number of days the data can be stored | Max Daily Processing Volume | Cisco Cloud | On-Prem (UCS) | Customer Cloud |
---|---|---|---|---|---|---|---|
** Cisco SD-WAN Application Intelligence Engine (SAIE) Disabled |
|||||||
<250 |
One Node Small Cisco vManage |
NA |
NA |
NA |
Yes |
Yes |
Yes |
250-1000 |
One Node Medium vManage |
NA |
NA |
NA |
Yes |
Yes |
Yes |
1000-1500 |
One Node Large vManage |
NA |
NA |
NA |
Yes |
Yes |
Yes |
1500-2000 |
Three Node Medium vManage Cluster (All Services) |
NA |
NA |
NA |
Yes |
Yes |
Yes |
2000-5000 |
Three Node Large vManage Cluster (All Services) |
NA |
NA |
NA |
Yes |
Yes |
Yes |
5000-10000 |
Six Node Large vManage Cluster (3 Nodes with ConfigDB) and all nodes messaging server, stats and AppServer |
NA |
NA |
NA |
Yes |
Yes |
Yes |
** Cisco SD-WAN Application Intelligence Engine (SAIE) Enabled |
|||||||
<250 |
One Node Medium vManage |
25 GB/Day |
20 Days |
25 GB/Day |
Yes |
NA |
NA |
<250 |
One Node Large vManage |
50 GB/Day |
30 Days |
50 GB/Day |
NA |
Yes |
Yes |
250-1000 |
One Node Large vManage |
50 GB/Day |
30 Days |
50 GB/Day |
Yes |
Yes |
Yes |
1000-4000 |
Three Node Large vManage Cluster (All Services) |
100 GB/Day |
14 Days |
300 GB/Day |
Yes |
Yes |
Yes |
4000-7000 |
Six Node Large vManage Cluster (3 Node with ConfigDB) and all nodes messaging server, stats, and AppServer |
100 GB/Day |
14 Days |
2 TB/Day* |
Yes |
Yes |
Yes |
7000-10000 |
Six Node Large vManage Cluster (3 Node with ConfigDB) and all nodes messaging server, stats, and AppServer |
100 GB/Day |
14 Days |
1 TB/Day* |
Yes |
Yes |
Yes |
Note |
|
Devices | Nodes and Deployment Models with Instance Types |
---|---|
0-2000 |
Three Node Medium Cisco vManage Cluster |
2000-5000 |
Three Node Large Cisco vManage Cluster |
To achieve scale beyond the numbers mentioned in the tables above, deploy multiple overlays.
Note |
|
Note |
Maximum tested disk size for On-prem is 10 TB per instance. |
Note |
Starting from Cisco vManage Release 20.6.1, you can achieve the above mentioned storage size numbers by modifying the aggregated SAIE size. The aggregated SAIE size is unidimensional and varies when the deployment includes edge devices that run on a mix of releases (Cisco SD-WAN Release 20.6.x and earlier releases). The aggregated SAIE also varies when on-demand troubleshooting is enabled for the devices. Ensure that both the SAIE and aggregated SAIE index sizes are configured to enable on-demand troubleshooting. To modify the aggregated SAIE value,
|
Note |
When SAIE is enabled, you must set the Statistics Collection timer to 30 minutes or higher. To set the Statistics Collection timer,
|
Devices | Number of Cisco SD-WAN Validators | vCPU | RAM | OS Volume | vNICs | Azure | AWS |
---|---|---|---|---|---|---|---|
<1000 |
2 |
2 |
4 GB |
10 GB |
2 (one for tunnel interface, one for management) |
Standard_F2s_v2 |
c5.large |
1000-4000 |
2 |
4 |
8 GB |
10 GB |
2 (one for tunnel interface, one for management) |
Standard_F4s_v2 |
c5.xlarge |
4000-8000 |
4 |
4 |
8 GB |
10 GB |
2 (one for tunnel interface, one for management) |
Standard_F4s_v2 |
c5.xlarge |
8000-10000 |
6 |
4 |
8 GB |
10 GB |
2 (one for tunnel interface, one for management) |
Standard_F4s_v2 |
c5.xlarge |
Devices | Number of Cisco Catalyst SD-WAN Controllers | vCPU | RAM | OS Volume | vNICs | Azure | AWS |
---|---|---|---|---|---|---|---|
<250 |
2 |
4 |
8 GB |
10 GB |
2 (one for tunnel interface, one for management) |
Standard_F4s_v2 |
c5.xlarge |
250-1000 |
2 |
4 |
16 GB |
10 GB |
2 (one for tunnel interface, one for management) |
Standard_D4ds_v5 |
c5.2xlarge |
1000-2500 |
2 |
8 |
16 GB |
10 GB |
2 (one for tunnel interface, one for management) |
Standard_F8s_v2 |
c5.2xlarge |
2500-5000 |
4 |
8 |
16 GB |
10 GB |
2 (one for tunnel interface, one for management) |
Standard_F8_v2 |
c5.2xlarge |
5000-7500 |
6 |
8 |
16 GB |
10 GB |
2 (one for tunnel interface, one for management) |
Standard_F8_v2 |
c5.2xlarge |
7500-10000 |
8 |
8 |
16 GB |
10 GB |
2 (one for tunnel interface, one for management) |
Standard_F8_v2 |
c5.2xlarge |
Note |
|
Hardware SKU | Specifications |
---|---|
UCSC-C240-M5SX |
UCS C240 M5 24 SFF + 2 rear drives without CPU, memory cards, hard disk, PCIe, and PS. |
UCS-MR-X16G1RT-H |
16GB DDR4-2933-MHz RDIMM/1Rx4/1.2v |
UCS-CPU-I6248R |
Intel 6248R 3GHz/205W 24C/35.75MB DDR4 2933MHz Intel(R) Xeon(R) Gold 6330N CPU @ 2.20GHz |
UCS-SD16T123X-EP |
1.6TB 2.5in Enterprise Performance 12G SAS SSD (3X endurance) |
Note |
|
Hardware SKU | Specifications |
---|---|
HXAF240-M5SX |
Cisco HyperFlex HX240c M5 All Flash Node |
HX-MR-X32G2RT-H |
32GB DDR4-2933-MHz RDIMM/2Rx4/1.2v |
HX-CPU-I6248 |
Intel 6248 2.5GHz/150W 20C/24.75MB 3DX DDR4 2933 MHz |
HX-SD38T61X-EV |
3.8TB 2.5 inch Enterprise Value 6G SATA SSD |
HX-NVMEXPB-I375 |
375GB 2.5 inch Intel Optane NVMe Extreme Performance SSD |
Note |
|