Cisco Crosswork Network Controller 7.2.x Administration Guide

PDF

Cisco Crosswork Network Controller 7.2.x Administration Guide

Components of Crosswork Data Gateway

Want to summarize with AI?

Log in

Outlines the core components and deployment concepts of Crosswork Data Gateway, including gateway instances, profiles, pools, data destinations, collection jobs, and custom software packages, with emphasis on management, scalability, high availability, and device coverage.


The Data Gateway consists of several core components, each of which plays a crucial role in its deployment, performance, security, and scalability.

The Data Gateway, deployed with Crosswork Infrastructure, is managed by Cisco Crosswork Network Controller and is based on these concepts:

  • Crosswork Data Gateway: A deployed Data Gateway instance that you install, which can be associated with the fully qualified domain name, known as FQDN, of a Network Load Balancer, known as NLB, or assigned a virtual IP address when added to a pool.

  • Profile: Determines the deployment profile for the Data Gateway:

    • Standard: for use with all Crosswork applications except Crosswork Health Insights and Crosswork Service Health (Automated Assurance)

    • Extended: for Crosswork Health Insights and Crosswork Service Health (Automated Assurance)

    Note
    The Standard with Extra Resources profile is a limited-availability feature and must not be used when deploying a Data Gateway in your data center.
  • Crosswork Data Gateway pool: A logical group of one or more Data Gateway instances, with optional high availability. If one instance fails, another instance in the pool replaces it to minimize disruption.

  • Data destination: Internal or external recipients that receive data collected by the Data Gateway. By default, Cisco Crosswork acts as a data destination, but other external destinations can be defined using the Cisco Crosswork UI or APIs.

  • Collection job: A task created to collect data, such as checking device reachability or collecting telemetry data for service and network health. Collection jobs can also be configured for non-Crosswork applications using the Crosswork Network Controller UI or APIs.

  • Custom software packages: Device model definitions and files used to extend device coverage and enable data collection from devices.