You create - we automate

Perform alarm validation on NMS/EMS and if the routing protocol is down.  Perform ping tests to see if the neighbor is reachable. Record the findings from the routing table, device logs

Perform alarm validation on NMS/EMS and the device. Check utilization graphs and see if there is a trend in the utilization

Perform checks at the network, Virtualization/system, OS, Services, DNS, Application layer to identify the RC of the issue

Perform checks at the network, Virtualization/system, OS, Services, DNS, Application layer to identify the RC of the issue

Perform alarm validation on NMS/EMS and the device. Check utilization graphs and see if there is a trend in the utilization (known patterns – data backup causing high utilization) – check QoS configurations (if any) to show which classes of applications are impacted. 

Initiate a workflow to validate the alarm, ping and traceroute to the Interface (If it is IP enabled), identify weather the device’s gateway is reachable, if it was a transient alert, back-off and try again (either upon alarm clearing or wait for a fixed interval – whichever is easier to implement). Log onto the device and check for the interface status and interesting logs that show why the interface went down.  Inform Ops on slack?

Initiate a workflow to validate the alarm, ping and traceroute to the device, identify weather the device’s gateway is reachable, if it was a transient alert, back-off and try again (either upon alarm clearing or wait for a fixed interval – whichever is easier to implement). Inform Ops on slack?

Checks if  BGP (Border Gateway Protocol) neighbor is down.

(checks and fix neighbor flapping, MTU problem, AS number, peer IP, Keepalive and Hold    timers correctness, multihop configuration, update-source loopback configuration, port 179 access, route correctness, TAC case open/close ticketing )