Deploying more than one SDC for your tenant allows you to manage more devices with your CDO tenant without experiencing performance degradation. The number of devices a single SDC can manage depends on the features implemented on those devices and the size of their configuration files. For the purposes of planning your deployment, however, we expect one SDC to support approximately 500 devices.
CDO support deploys 1 cloud SDC for every tenant and customers can install 4 on-premises SDCs for a maximum number of 5 SDCs per tenant. You cannot have more than one cloud-based SDC per tenant. Customers can also ask CDO support to remove the cloud SDC their tenant is originally provisioned with so that they can replace it with an on-premises SDC.
Additionally, because you can deploy more than one SDC, you can manage devices in isolated network segments with the same CDO tenant. Up to 5 network segments could have their own on-premises SDC. These SDCs would connect the devices in those network segments to the same CDO tenant. Without multiple SDCs, you would need to manage the devices in isolated network segments with different CDO tenants.
Having more than one SDC does not imply load-balancing or a high-availability configuration between the SDCs. However, if you have more than one SDC, you can manually move ASA, AWS VPC, and Meraki MX devices from one SDC to another.
The procedure for deploying a second or subsequent SDC is the same for deploying your first on-premises SDC. You can create the on-premises SDC using an SDC image that CDO provides or you can install a virtual machine or appliance from scratch and install the on-premises SDC. The initial on-premises SDC for your tenant incorporates the name of your tenant and the number 1. Each additional on-premises SDC is numbered in order.