Cisco Crosswork Overview

This chapter contains the following topics:

About this guide

This guide explains the requirements and process to install Cisco Crosswork Infrastructure, along with Cisco Crosswork Data Gateway and the Cisco Crosswork applications. It also explains the process to upgrade your Cisco Crosswork to the latest version. This guide is relevant for customers using the Cisco Crosswork Network Controller solution, the Cisco Routed Optical Networking solution, or any of the Crosswork applications.

There are other components that integrate with Cisco Crosswork (see Integrated Components), such as Cisco NSO or Cisco WAE, but they are NOT covered in this document. Please refer to the respective install documentation of those components for more details.

Audience

This guide is for experienced network users and operators who want to use Cisco Crosswork Infrastructure and applications in their network. This guide assumes that you are familiar with the following:

  • Using a Docker container

  • Running scripts in Python

  • Deploying OVF templates using VMware vCenter

  • Deploying using OVF tool

  • Deploying a virtual machine on Cisco Cloud Services Platform (CSP)

Introduction

Cisco Crosswork Infrastructure is a microservices-based platform and is the foundation required for running Crosswork on-premise applications. It employs a cluster architecture to be extensible, scalable, and highly available. The Crosswork cluster consists of at least three VMs or nodes operating in a hybrid configuration. Additional VMs or nodes in a Worker configuration can be added, as needed, to match the requirements of your network. A Hybrid node can run infrastructure and application pods, while a Worker node can run only application pods. The total number of Hybrid and Worker nodes varies based on the size of the network and the applications being run work with Cisco Crosswork to scale the solution correctly for your needs.


Note

Hereafter in this guide, Cisco Crosswork Infrastructure is referred to as "Cisco Crosswork".


Cisco Crosswork uses Cisco Crosswork Data Gateway (CDG), a software package that is separated out into its own Virtual Machine (VM), to gather information from the managed devices and forward it to Cisco Crosswork as well as external destinations. The information is then analyzed and processed by the Crosswork applications, and used to manage the network or respond to changes in the network. The number of Crosswork Data Gateways deployed in your network depends on the number of devices, the amount of data being collected, the overall topology, and your redundancy requirements. Please consult with your Cisco Customer Experience team for guidance on your deployment to best meet your needs.

Integrated Components

Cisco Network Services Orchestrator functions as the provider for Crosswork to configure the devices according to their expected functions, including configuring model-driven telemetry (MDT) sensor paths, if any, for data collection. Cisco NSO is vital in supplying device management and configuration-maintenance services.

Cisco Segment Routing Path Computation Element (SR-PCE) is an IOS-XR multi-domain stateful PCE supporting both Segment Routing Traffic Engineering (ST-TE) and Resource Reservation Protocol Traffic Engineering (RSVP-TE). Cisco Crosswork uses the combination of telemetry and data collected from the Cisco SR-PCE to analyze and compute optimal TE tunnels and/or to discover devices in the network.

Cisco Crosswork can also integrate with other providers (such as Cisco WAE, Syslog and Alert) and servers (TACACS+ and LDAP). For more information, see the "Device Management" chapter in the Cisco Crosswork Infrastructure 4.3 and Applications Administration Guide.

Cisco Crosswork Product Portfolio

Cisco Crosswork Infrastructure provides a flexible platform to deploy different products (Crosswork and non-Crosswork) where each product is downloaded and added to the platform.

The list of Crosswork products are:

  • Cisco Crosswork Network Controller is an integrated Crosswork solution that combines essential components, such as Cisco Network Services Orchestrator, Segment Routing Path Computation Element (SR-PCE), Crosswork Active Topology, and Crosswork Optimization Engine. The solution enables you to proactively manage your end-to-end networks, and it provides intent-based and closed-loop automation solutions to ensure faster innovation, optimal user experience, and operational excellence.

    • Cisco Crosswork Active Topology application is a part of Cisco Crosswork Network Controller and it enables visualization of topology and services on logical and geographical maps.

    • Cisco Crosswork Service Health (Automated Assurance) application is an optional component of Cisco Crosswork Network Controller that overlays a service level view of the environment and makes it easier for operators to monitor if services (for example, L2/L3 VPN) are healthy based on the rules established by the operator.

    • Cisco Crosswork Health Insights application is an optional network health component of Cisco Crosswork Network Controller that performs real-time Key Performance Indicator (KPI) monitoring, alerting, and troubleshooting. Cisco Crosswork Health Insights enables programmable monitoring and analytics, and builds dynamic detection and analytics modules that allow operators to monitor and alert on network events based on user-defined logic.

    • Cisco Crosswork Change Automation application is an optional component of Cisco Crosswork Network Controller that automates the process of deploying changes to the network. Orchestration is defined via an embedded Ansible Playbook and then configuration changes are pushed to Cisco Network Services Orchestrator (NSO) to be deployed to the network.

  • Cisco Crosswork Optimization Engine is a Crosswork application that provides real-time network optimization allowing operators to effectively maximize network capacity utilization, as well as increase service velocity. Leveraging real-time protocols, such as BGP-LS and Path Computation Element Communication Protocol (PCEP) and Segment Routing Path Computation Element (SR-PCE) Cisco Crosswork Optimization Engine enables closed-loop tracking of the network state, quickly reacting to changes in network conditions to support a self-healing network.

  • Cisco Crosswork Zero Touch Provisioning is a Crosswork application that allows users to quickly and easily bring up devices using a Cisco-certified software image and a day-zero software configuration of the customer's choice. After it is provisioned in this way and configured to Cisco NSO, the new device is onboarded to the Crosswork device inventory, where it can be monitored and managed like other devices.

Crosswork Network Controller applications are bundled as Essentials and Advantage packages.

Table 1. Crosswork Network Controller Packages

Crosswork Network Controller package

Contents

Essentials package

Crosswork Optimization Engine

Crosswork Active Topology

Advantage package

Crosswork Optimization Engine

Crosswork Active Topology

Cisco Crosswork Service Health

Cisco Crosswork Health Insights

Cisco Crosswork Change Automation

Crosswork Zero Touch Provisioning

Element Management System (EMS) Services

Aside from Crosswork products, Crosswork Infrastructure supports deployment of the following non-Crosswork application:

  • The Cisco Evolved Programmable Network Manager (EPNM) is designed to provide simplified, converged, end-to-end lifecycle management for carrier-grade networks. It provides device management, network service provisioning, and network assurance across core, edge, aggregation, and access networks consisting of a wide range of Cisco device families.

For information on the installation and configuration requirements of Cisco Crosswork products, see Installation Dependencies for Cisco Crosswork Products.

Resource Allocation

Resource requirements for a cluster and each cluster VM node vary based on the Crosswork components that you use and the deployment size you select. The following tables contain an estimation of resources needed for each scenario:

Table 2. Cluster Requirements

Deployment Size

Use Case

Number of Nodes

Small

Lab only

3 Hybrid nodes

Large

Crosswork Network Controller Essentials package

3 Hybrid nodes + 1 Worker node (to ensure VM resiliency)

You can add more Worker nodes as needed.

Crosswork Network Controller Advantage package1

3 Hybrid nodes + 2 Worker nodes (to ensure VM resiliency)

You can add more Worker nodes as needed.

Extra Large

Evolved Programmable Network Manager (EPNM)

3 Hybrid nodes + 2 Worker nodes (to ensure VM resiliency)

You can add more Worker nodes as needed.

Note 

Use of other Crosswork applications with EPNM is NOT currently supported.

1 The cluster resource estimation is under the assumption that you are using all the applications in the Crosswork Network Controller Advantage package.

Note

A cluster with only 3 Hybrid VM nodes (without any Worker VM nodes) is NOT resilient. If one of the VM fails, it will certainly result in an impaired system performance, as the remaining 2 VMs will not be able to support all the pods being migrated from the failed VM.


Table 3. Resource Footprint per VM node

Component

vCPU

Memory (RAM)

Network Interface Controller (NIC)

Storage

Crosswork Infrastructure

12

96 GB

10 Gbps

1 TB

CDG Standard

12

48 GB

10 Gbps

60 GB

CDG Extended

20

112 GB

10 Gbps

560 GB

NSO (Large)

24

132 GB

10 Gbps

1 TB

NSO (Small) [below 1k devices]

8

64 GB

10 Gbps

250 GB

SR-PCE

8

64 GB

10 Gbps

45 GB