Cisco Platforms and Development

Key Concepts

• Cisco DNA Center (DNAC): Intent-based networking platform for network automation, assurance, and management. Uses a REST API (northbound) to integrate with external apps
• Cisco SD-WAN (Viptela): Software-defined WAN solution. Key components: vManage (GUI/API), vSmart (control plane), vBond (orchestration), vEdge/cEdge (data plane)
• Cisco Meraki: Cloud-managed networking. Managed entirely via Meraki Dashboard API (REST). No on-prem controller needed
• Cisco ACI: Data center SDN solution. APIC is the controller. Uses a REST API with XML or JSON. Policy-based model using Tenants, VRFs, Bridge Domains, EPGs
• Cisco DevNet: Developer program providing sandboxes, APIs, and learning resources for Cisco platforms
• Webex APIs: Used to integrate messaging, meetings, and calling. Bot creation uses webhooks to receive events
• Cisco IOS XE: Traditional routing/OS with NETCONF/RESTCONF/gRPC support for programmatic access
• NSO (Network Services Orchestrator): Automates multi-vendor networks using YANG models and NEDs (Network Element Drivers)

How It Works

• DNA Center API flow: Authenticate → get token → use token in X-Auth-Token header → call intent APIs under /dna/intent/api/v1/
• Meraki API flow: Use X-Cisco-Meraki-API-Key header for all calls → base URL https://api.meraki.com/api/v1/
• ACI API flow: POST to /api/aaaLogin.json → get token → use APIC-cookie for subsequent calls
• SD-WAN vManage API: Authenticate via POST, get JSESSIONID + CSRF token, include both in API calls
• RESTCONF: Uses HTTP methods on YANG-modeled data; base path /restconf/data/ on IOS XE devices
• NETCONF: Uses SSH (port 830), XML-encoded RPC calls (<get-config>, <edit-config>, <commit>)

Commands / Syntax / Key Values

Authentication headers: - DNA Center → X-Auth-Token: <token> - Meraki → X-Cisco-Meraki-API-Key: <key> - Webex → Authorization: Bearer <token> - ACI → Cookie: APIC-cookie=<token>

Common DNA Center API endpoints: - GET /network-device — list devices - GET /site — list sites - POST /pnp/workflow — Plug and Play

Exam Gotchas

1. DNA Center vs ACI: Don't confuse them. DNA Center is for campus/branch networks; ACI is for the data center. Both have REST APIs but different auth mechanisms and URL structures
2. Meraki has no on-prem controller — all management is cloud-based. If a question mentions an on-prem controller for Meraki, it's wrong
3. NETCONF uses port 830, not 22 (even though it runs over SSH). Exam loves to test this port number
4. SD-WAN vManage needs TWO tokens — JSESSIONID (cookie) AND `X-