This guide is for network administrators who intend to use the Service Health component of Cisco Crosswork Network Controller in their network environment. It assumes familiarity with the following topics:

• Platform Infrastructure and installation of Crosswork Network Controller components. For more information, see the Crosswork Network Controller 7.1 Installation guide.

• Provisioning L2VPN and L3VPN services

• Networking technologies and protocols (BGP-LS, IGP (OSPF and IS-IS), PCEP, model-driven telemetry)

• Traffic Engineering (TE) tunnels, including

  • RSVP-TE tunnel provisioning

  • Segment Routing Traffic Engineering (SR-TE) policy provisioning

Service Health is a component of Crosswork Network Controller's Advantage package. For more information on all Crosswork Network Controller solution components, refer to the Crosswork Network Controller 7.1.0 Installation guide.

Service Health extends the capabilities of Crosswork Network Controller by offering a service-level perspective that goes beyond the physical monitoring of devices. While Crosswork Network Controller can alert you to a failed link or one that has reached its capacity, Service Health assesses how such issues impact the services that traverse these links, such as L2 and L3 VPN services.

Service Health provides operators with the ability to pinpoint exactly where and why a service is degraded, offering targeted tools for service-specific monitoring and assurance.

The application offers APIs and samples for developing additional service monitoring tools as needed. Additionally, it includes ready-to-use packages for monitoring common scenarios, such as:

• Health monitoring of point-to-point L2VPN (for example T-LDP and EVPN) services

• Health monitoring of multipoint L2VPN services (EVPN E-LAN and E-Tree L2VPN EVPN)

• Health monitoring of L3VPN services

• Analysis of health of degraded services to provide information to aid troubleshooting

• Visualization of service health status and its logical dependency tree

Service Health is designed to be extensible, allowing you to add new service monitoring capabilities to meet your requirements.

Users can integrate other Crosswork Network Controller applications and third-party applications with Service Health by using application programming interfaces (APIs) delivering new capabilities into their network operations.

For more information, see the Cisco Crosswork Network Automation API Documentation on Cisco DevNet.