-
- Read Me First
- Compatibility Matrix
- Cisco Catalyst SD-WAN Compatibility Matrix for Cisco Catalyst SD-WAN Control Components Release 20.15.x
- Cisco Catalyst SD-WAN Compatibility Matrix for Cisco Catalyst SD-WAN Control Components Release 20.14.x
- Cisco Catalyst SD-WAN Compatibility Matrix for Cisco Catalyst SD-WAN Control Components Release 20.13.x
- Cisco Catalyst SD-WAN Compatibility Matrix for Cisco Catalyst SD-WAN Control Components Release 20.12.x
- Cisco Catalyst SD-WAN Compatibility Matrix for Cisco Catalyst SD-WAN Control Components Release 20.11.x
- Cisco Catalyst SD-WAN Compatibility Matrix for Cisco Catalyst SD-WAN Control Components Release 20.10.x
- Cisco Catalyst SD-WAN Compatibility Matrix for Cisco Catalyst SD-WAN Control Components Release 20.9.x
- Cisco Catalyst SD-WAN Compatibility Matrix for Cisco Catalyst SD-WAN Control Components Release 20.8.x
- Cisco Catalyst SD-WAN Compatibility Matrix for Cisco Catalyst SD-WAN Control Components Release 20.7.x
- Cisco Catalyst SD-WAN Compatibility Matrix for Cisco Catalyst SD-WAN Control Components Release 20.6.x
- Cisco Catalyst SD-WAN Compatibility Matrix for Cisco Catalyst SD-WAN Control Components Release 20.5.x
- Cisco Catalyst SD-WAN Compatibility Matrix for Cisco Catalyst SD-WAN Control Components Release 20.4.x
- Cisco Catalyst SD-WAN Compatibility Matrix for Cisco Catalyst SD-WAN Control Components Release 20.3.x
- Compatibility Matrix for Cisco SD-WAN Release 20.1.x
- Compatibility Matrix for Cisco SD-WAN Release 19.2.x
- Compatibility Matrix for Cisco SD-WAN Release 18.4.x
- Hypervisor Compatibility Matrix for Cisco Catalyst SD-WAN Control Components and vEdgeCloud
- Hypervisor Compatibility Matrix for Cloud Routers
-
- Recommended Computing Resources
- Recommended Computing Resources for Cisco Catalyst SD-WAN Control Components Release 20.15.x
- Recommended Computing Resources for Cisco Catalyst SD-WAN Control Components Release 20.14.x
- Recommended Computing Resources for Cisco Catalyst SD-WAN Control Components Release 20.13.x
- Recommended Computing Resources for Cisco Catalyst SD-WAN Control Components Release 20.12.x
- Recommended Computing Resources for Cisco Catalyst SD-WAN Control Components Release 20.11.x
- Recommended Computing Resources for Cisco Catalyst SD-WAN Control Components Release 20.10.x
- Recommended Computing Resources for Cisco Catalyst SD-WAN Control Components Release 20.9.x
- Recommended Computing Resources for Cisco SD-WAN Controller Release 20.8.x (Cisco Hosted Cloud Deployment)
- Recommended Computing Resources for Cisco SD-WAN Controller Release 20.8.x (Customer Cloud Hosted on Azure Deployment)
- Recommended Computing Resources for Cisco SD-WAN Controller Release 20.8.x (On-Prem Deployment)
- Recommended Computing Resources for Cisco SD-WAN Controller Release 20.7.x (Cisco Hosted Cloud Deployment)
- Recommended Computing Resources for Cisco SD-WAN Controller Release 20.7.x (Customer Cloud Hosted on Azure Deployment)
- Recommended Computing Resources for Cisco SD-WAN Controller Release 20.7.x (On-Prem Deployment)
- Recommended Computing Resources for Cisco Catalyst SD-WAN Control Components Release 20.6.x (Cisco Hosted Cloud Deployment)
- Recommended Computing Resources for Cisco Catalyst SD-WAN Control Components Release 20.6.x (Customer Cloud Hosted on Azure Deployment)
- Recommended Computing Resources for Cisco Catalyst SD-WAN Control Components Release 20.6.x (On-Prem Deployment)
- Recommended Computing Resources for Cisco SD-WAN Controller Release 20.5.x (On-Prem Deployment)
- Recommended Computing Resources for Cisco SD-WAN Controller Release 20.4.x (On-Prem Deployment)
- Recommended Computing Resources for Cisco SD-WAN Controller Release 20.3.x (On-Prem Deployment)
- Recommended Computing Resources for Cisco SD-WAN Controller Release 20.1.x and earlier releases
Recommended Computing Resources for Cisco SD-WAN Controller Release 20.7.x (Customer Cloud Hosted on Azure Deployment)
Single Tenant
The supported hardware specifications for the Cisco vBond Orchestrator, Cisco vManage, and the Cisco vSmart Controller for Azure are as follows:
Note |
The controller and the device version should be the same, to achieve the below scale. |
Devices |
Aggregated Statistics from Edge Devices |
Nodes and Deployment Models |
vCPUs * |
RAM* |
Storage Size* |
Azure Instance Sizing |
---|---|---|---|---|---|---|
** Cisco SD-WAN Application Intelligence Engine (SAIE) Disabled |
||||||
<250 |
Disabled |
One Node vManage (All Services) |
16 vCPUs |
32 GB RAM |
500 GB |
Standard_F16s_v2 |
250-1000 |
Disabled |
One Node vManage (All Services) |
32 vCPUs |
64 GB RAM |
1 TB |
Standard_F32s_v2 |
1000-1500 |
Disabled |
One Node vManage (All Services) |
32 vCPUs |
128 GB RAM |
1 TB |
Standard_F64s_v2 |
1500-2000 |
Disabled |
Three Node vManage Cluster (All Services) |
32 vCPUs |
64 GB RAM |
1 TB |
Standard_F32s_v2 |
2000-5000 |
Disabled |
Three Node vManage Cluster (All Services) |
32 vCPUs |
128 GB RAM |
1 TB |
Standard_F64s_v2 |
5000-7000` |
Disabled |
Six Node vManage Cluster (3 Nodes with ConfigDB) and all nodes messaging server, stats, and AppServer |
32 vCPUs |
128 GB RAM |
1 TB |
Standard_F64s_v2 |
** Cisco SD-WAN Application Intelligence Engine (SAIE) Enabled |
||||||
<500 |
50 GB/Day |
One Node vManage (All Services) |
32 vCPUs |
128 GB RAM |
10 TB |
Standard_F64s_v2 |
500-2000 |
100 GB/Day |
Three Node vManage Cluster (All Services) |
32 vCPUs |
128 GB RAM |
10 TB |
Standard_F64s_v2 |
2000-7000 |
2.0 TB/Day** |
Six Node vManage Cluster (3 Node with ConfigDB) and all nodes messaging server,Stats, and AppServer |
32 vCPUs |
128 GB RAM |
10 TB |
Standard_F64s_v2 |
Note |
|
* vCPU, RAM, and Storage Size numbers are on per Cisco vManage basis. The Storage Size numbers are the maximum tested values by Cisco, you can allocate smaller storage sizes.
To achieve scale beyond the above mentioned numbers, deploy multiple overlays.
Note |
In Cisco vManage Release 20.5.1 and earlier releases, You can modify the DPI size to the desired value to achieve the above mentioned storage size numbers. |
Note |
Starting from Cisco vManage Release 20.6.1, you can achieve the above mentioned storage size numbers by modifying the aggregated DPI size. The aggregated DPI 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 DPI also varies when on-demand troubleshooting is enabled for the devices. Ensure that both the DPI and aggregated DPI index sizes are configured to enable on-demand troubleshooting. To modify the aggregated DPI value,
|
Note |
When DPI is enabled, you must set the Statistics Collection timer to 30 minutes or higher. To set the Statistics Collection timer,
|
Devices |
vCPUs |
RAM |
OS Volume |
vNICs |
Azure Instance Sizing |
1-50 |
2 |
4 GB |
10 GB |
2 (one for tunnel interface, one for management) |
Standard_F4s_v2 |
51-250 |
2 |
4 GB |
10 GB |
2 (one for tunnel interface, one for management) |
Standard_F4s_v2 |
251-1000 |
2 |
4 GB |
10 GB |
2 (one for tunnel interface, one for management) |
Standard_F4s_v2 |
1001 -1500 |
4 |
8 GB |
10 GB |
2 (one for tunnel interface, one for management) |
Standard_F4s_v2 |
Devices |
vCPUs |
RAM |
OS Volume |
vNICs |
Azure Instance Sizing |
1-50 |
2 |
4 GB |
16 GB |
2 (one for tunnel interface, one for management) |
Standard_F2s_v2 |
51-250 |
4 |
8 GB |
16 GB |
2 (one for tunnel interface, one for management) |
Standard_F4s_v2 |
251-1000 |
4 |
16 GB |
16 GB |
2 (one for tunnel interface, one for management) |
Standard_F8s_v2 |
1001 -1500 |
8 |
16 GB |
16 GB |
2 (one for tunnel interface, one for management) |
Standard_F8s_v2 |