About Cisco Catalyst Center
Cisco Catalyst Center (formerly Cisco DNA Center) manages campus and branch networks: switches, routers, wireless controllers, and access points, and the site hierarchy they’re placed in. This integration connects Serval to your own Catalyst Center appliance so workflows can read its network device inventory and sites, and sync both into Serval as assets. It connects to the appliance you run, not to a Cisco-hosted service.X-Auth-Token before each API request, so workflows never handle the credentials. Serval sends them only to the appliance hostname saved on the connection. On a connection that runs on self-hosted workers, the username and password also travel with each API request, from your worker to your appliance.
Data sync: No background sync starts when you connect. Data access is on demand through workflows, plus two installable ingestion workflows that sync network devices and sites into Serval as assets.
What the Cisco Catalyst Center integration enables
Get your credentials
Serval needs the hostname of your appliance and a Catalyst Center user it can sign in as. Only a user with SUPER-ADMIN-ROLE can create users in Catalyst Center.Create a dedicated user
svc-serval. A dedicated user keeps the connection working when staff change.Give it a read-only role
Note your appliance hostname
catalyst.example.com. IPv6 addresses aren’t supported.POST, PUT, PATCH, and DELETE requests, including to system APIs under /dna/system/api/. The user’s role is what limits what a workflow can change, so keep it read-only unless you build workflows that need to write.Connect in Serval
Open the Cisco Catalyst Center connect form
Enter the Catalyst Center URL
catalyst.example.com or catalyst.example.com:8443. Serval removes any https:// prefix and path you paste, and always connects over HTTPS.Enter the Username and Password
Save, then check the health checks
Verifying the connection
The connection ships three health checks that make live calls to your appliance:- Validate API connection: exchanges the credentials for a token and counts the network devices that reported in over the last 14 days. Ingestion uses the same 14-day window, so a sync should pick up the same devices.
- List network devices: reads one device from the Assurance inventory.
- List sites: reads one site from the Intent API.
Syncing Catalyst Center inventory into Serval
Install the ingestion workflows you need and use them as asset sync sources:siteId, the Catalyst Center ID of its site, which matches the external ID of that site’s asset.
Gotchas and troubleshooting
Your appliance must be reachable from Serval
Your appliance must be reachable from Serval
The appliance needs a trusted TLS certificate
The appliance needs a trusted TLS certificate
Devices that haven't reported in 14 days aren't synced
Devices that haven't reported in 14 days aren't synced
Device sync needs the Assurance network devices API
Device sync needs the Assurance network devices API
/dna/data/api/v1/networkDevices, and Validate API connection reads its /count endpoint. If your Catalyst Center release doesn’t serve that API, they fail while site sync keeps working.List network devices reports no devices
List network devices reports no devices
Every request signs in again
Every request signs in again
Site sync uses the original site endpoint
Site sync uses the original site endpoint
/dna/intent/api/v1/site. Cisco superseded it with /dna/intent/api/v1/sites in release 2.3.7.6 but still serves it. If a release you upgrade to stops serving it, site sync and that check fail while device sync keeps working.Need help? Contact support@serval.com for assistance with your Cisco Catalyst Center integration.

