Cisco Catalyst SD-WAN Multitenancy Guide, Releases 26.x and Later
Is this content helpful?
Thank you for your feedback. Your response has been recorded.
AI responses are currently only available to logged in users. Log in
Only ask questions about this document. To ask questions about this product as a whole, go to Technical Documentation .
Suggestions
Sorry, we couldn't generate a response for this query.
Cisco Catalyst SD-WAN Multitenancy Guide, Releases 26.x and Later
Updated: September 25, 2026
Want to summarize with AI?
Log inDescribes how to onboard WAN edge devices at the provider level by uploading and validating the serial number file, bootstrapping the device, handling enterprise certificate installation if required, and attaching the device to a configuration template.
Follow these steps to onboard WAN edge devices at the provider level.
Log in to Cisco SD-WAN Manager as the provider admin user.
Upload the device serial number file to Cisco SD-WAN Manager. While uploading the file, choose the option to validate and send the device list to controllers.
Bootstrap the device using bootstrap configuration generated through Cisco SD-WAN Manager or manually create the initial configuration on the device.
If you are using Enterprise Certificates to authenticate the device, download the Certificate Signing Request (CSR) from Cisco SD-WAN Manager and get the CSR signed by the Enterprise CA. Install the certificate on Cisco SD-WAN Manager.
Create a configuration template for the device and attach the device to the template.
While configuring the device, configure the service provider organization name as sp-organization-name and the tenant organization-name.
Need help?
(Requires a Cisco Service Contract)
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.