1000 branches are to be deployed on Prisma SD-WAN with the following constraints:
Devices will be shipped in batches directly to the site
Configuration Management Database (CMDB) has all the necessary details for a site deployment
Field tech will be responsible for rack, stack, and cabling of the IONs at each site
Field tech will need to spend minimum amount of time at each branch site to reduce the cost
The NOC operates in shifts and is responsible for remote cutover support
Which method will achieve the mass deployment in shortest possible time?
For a massive rollout involving 1,000 branch sites, Prisma SD-WAN (formerly CloudGenix) provides a specialized workflow known as Bulk Site Configuration. This method is designed to minimize manual intervention and maximize deployment velocity by leveraging Site Templates and Device Shells.
In this scenario, the primary architectural advantage of Option C is the use of Pre-Staging. By exporting an empty SD-WAN device CSV from the Prisma SD-WAN Controller and populating it with data from the corporate CMDB, administrators can perform a bulk upload to create hundreds or thousands of sites and device shells simultaneously in the management portal. A 'Device Shell' acts as a placeholder for a physical ION device that has not yet connected to the cloud. It contains all the site-specific configuration---such as interface roles, circuit labels, and IP addressing---waiting for a serial number to be associated with it.
When the field technician performs the physical 'rack and stack,' they simply connect the ION device to the internet (via ISP modem or cellular). Through Zero Touch Provisioning (ZTP), the device automatically 'phones home' to the Prisma SD-WAN Cloud Controller using its Manufacturer Installed Certificate (MIC). Because the configuration was pre-created via the CSV bulk upload, the controller recognizes the device (once assigned to its shell) and immediately pushes the complete configuration. This eliminates the need for the field tech to access a console port or perform local configuration, reducing their on-site time to the bare minimum. While APIs (Option D) can be used for automation, the built-in CSV template workflow is the standard, documented 'best practice' for rapidly translating CMDB data into a functioning SD-WAN fabric at this scale.
Currently there are no comments in this discussion, be the first to comment!