Software Solutions
Software Solutions covers Cisco's management, automation, and assurance platforms and how you choose and drive them: Catalyst Center, Catalyst SD-WAN Manager, the Meraki dashboard, Nexus Dashboard, Intersight, and ThousandEyes, plus licensing tiers, APIs, and model-driven programmability. Items typically present an operational goal and ask which platform, API, or license tier delivers it.
Platform-to-job mapping
- Catalyst Center: campus/branch fabric (SD-Access), Plug and Play onboarding, intent templates, and Assurance for client and device health; northbound Intent API.
- SD-WAN Manager: centralized data, topology, and application-aware routing policy; feature and device templates; per-device CLI for troubleshooting.
- Meraki dashboard: cloud-managed org/network hierarchy, configuration templates, Dashboard API v1 with per-organization rate limiting and Link-header pagination.
- Intersight: UCS and compute lifecycle, server profiles, firmware policies, device claim through the device connector.
- Nexus Dashboard: fabric controller, orchestration, and insights for the data center.
- ThousandEyes: synthetic path and performance visibility from agents.
Automation rules
Authenticate first: Catalyst Center's token endpoint returns an X-Auth-Token from HTTP Basic credentials and the token expires, so scripts must refresh it. Prefer intent templates over raw CLI so re-sync corrects drift. Respect rate limits and paginate; truncated inventories are the classic automation bug. Model-driven programmability means NETCONF/RESTCONF over YANG models, with gNMI/model-driven telemetry for streaming state.
Worked example
You need a nightly report of every switch running an image older than the gold version. Reasoning: for Catalyst Center-managed devices, POST Basic-auth credentials to the token endpoint, capture X-Auth-Token, then GET the network-device intent resource and compare each device's software version to the gold string. For Meraki-managed networks, call the organization devices endpoint with the API key header and read the firmware field per device. Do not scrape the GUI, do not poll faster than the documented rate limit, and cache results - the report only needs one pass per night.
Traps that cost marks
- Treating a term subscription as perpetual, or assuming Assurance keeps working after a license tier lapses.
- Confusing configuration templates (intent) with compliance, which only detects drift.
- Ignoring pagination or rate limits and reporting a partial inventory.
- Assuming Meraki-style cloud management for Catalyst gear, or CLI access where none exists.
- Hard-coding credentials instead of using the token/API-key lifecycle.