IS-IS protocol is extensively used as Interior Gateway Protocol (IGP) in Internet Service Provider (ISP) environment. The scope of this used case is to provide information regarding IS-IS Adjacency in specific L2 Adjacency. Using Crosswork Health Insights application we will enable a Key Performance Indicator on routers using an API - At this point a Zero touch telemetry action has been performed and all the required gets configured on the respective router/device. After the successful execution of above action, the information that we're trying to monitor i.e. IS-IS L2 Adjacency is provided on the Alert dashboard of health insights. All this data that is being reported on Alert dashboard can the queried through an API as well. The provided API's collection helps you enable a KPI, query the state of the KPI and query for alerts (if any). As this is a proactive used case, we've also provided a python script which will forward all the alerts from Crosswork health Insights application to a webex-teams room. In this case the alerts will be reported by a Crosswork BOT.

This concept can be extended to various of combinations different protocols like BGP, OSPF, etc, their health monitoring and helping the operator to detect an issue in the network quickly.

For this use case please use the following JSON file in the repository - https://github.com/CiscoDevNet/postman-for-Cisco-Crosswork/blob/master/API-Collection-Alert-Forwarding.postman_collection.json

Using Crosswork Health Insights and Change Automation we can detect the state of the interface, forward an alert accordingly and perform an action, as per the customer's business logic. This drastically reduces the meantime to detect an issue and perform an action without any manual errors.
In the current use case, we will monitor the health of all the interfaces in large networks.

Whenever there is a continuous transition of the state of the interface we will perform an action to bring the interface down using Health Insights and Change Automation. Using Health Insights we will enable the Key Performance Indicator of Interface State flap detection. This action can be performed by an API or on UI. When we enable this KPI, the respective configuration of telemetry is configured on all the selected routers using NSO (zero-touch to router console). This configuration consists of the YANG Path that will be monitored every minute - in this case, we're monitoring the "state transition" of interfaces on all the routers in the network. Using the feature of Closed-loop remediation from Crosswork Health Insights and Change Automation, we will link the KPI to a playbook.

Playbooks are a part of Change Automation and they execute certain tasks as per the listed logic. For the successful execution of the playbook, we will need to provide the variables during their execution. When we link the KPI and Playbook, these variables are automatically learned from the generated Alert. In our current scenario, we will be learning the name of the Producer (router's name) and the corresponding interfaces from the KPI Alert, and as our action is to shut the interface, the action to be performed by playbook would be "down". All of the above-mentioned steps can be performed using APIs.