Catalyst Center Global Manager API

Catalyst Center Global Manager (CCGM) is a platform that provides you with a single pane of glass (SPoG) interface to easily manage multiple Catalyst Centers. It integrates information from various Catalyst Center platforms into a single display. CCGM supports up to 25 controllers and a maximum of 10 active users. Once controllers join CCGM, they continue to monitor and control networks.

CCGM API is open, standards-based interface that allow programmatic access to the Catalyst Center Global Manager platform. It is designed to facilitate centralized management, monitoring, and automation across multiple Cisco Catalyst Center instances, especially in large-scale, or distributed environments.

What can you do with CCGM API?

  • Centrally manage multiple Catalyst Center controllers.
  • Retrieve unified network health and data.
  • Automate operations and workflows.
  • Aggregate and generate reports.
  • Conduct global search.
  • Monitor alerts and events.

Communication between CCGM and Catalyst Center

Communication between Catalyst Center Global Manager (CCGM) and individual Catalyst Center controllers uses robust security measures. These measures protect data and maintain network integrity. Secure authentication methods, such as certificates, tokens, or API keys, verify the identity of both CCGM and Catalyst Center instances before any data exchange. Administrators manage digital certificates to establish trusted connections.

When the CCGM home page triggers a REST API call, it initiates a new request to the relevant controller. A plugin defines each API and specifies:

  • which controller API to call and how to call them,
  • the controller API required to collect the necessary data,
  • a normalizer to standardize the collected data, and
  • an aggregator function to combine normalized results from each controller into a single, merged response.

When an API request reaches the federation service, it first checks the local cache for a stored response and uses it if available. The service caches responses for 5 minutes. If there is no cached copy, a new request is made by retrieving the list of controllers from the device registry. The system then passes the request and controller list to the Endpoint Configuration to select the appropriate plugin. If the system does not find a matching plugin or controller, it returns an HTTP 404 status.