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

• Platform Infrastructure and installation of Crosswork Network Controller components. For more information, refer to the Crosswork Network Controller 7.2 Installation guide.

• Provisioning Layer 2 Virtual Private Network (L2VPN) and Layer 3 Virtual Private Network (L3VPN) services

• Networking technologies and protocols (Border Gateway Protocol - Link State (BGP-LS), Interior Gateway Protocol (IGP) such as Open Shortest Path First (OSPF) and Intermediate System to Intermediate System (IS-IS), Path Computation Element Communication Protocol (PCEP), and model-driven telemetry

• Traffic Engineering (TE) tunnels, including

  • Resource Reservation Protocol-Traffic Engineering (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, see the Crosswork Network Controller 7.2 Installation guide.

Service Health extends the capabilities of Crosswork Network Controller by offering a service-level perspective that goes beyond monitoring devices at a physical level. While Crosswork Network Controller can alert you to a failed link or one that has reached capacity, Service Health assesses the impact of these issues on services traversing the links, including 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 packages ready for use in monitoring common scenarios, such as:

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

• Health monitoring of multipoint L2VPN services (such as 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 components and third party applications with Service Health by using application programming interfaces (APIs) to deliver new capabilities into their network operations.

For more information, see the API documentation on Cisco Devnet.