How to stop alerting on all route groups and just alert on specific important route groups in Cisco

Community Manager

How to stop alerting on all route groups and just alert on specific important route groups in Cisco

Out-of-box alerting is on all Cisco devices when they are down or degraded. Route Group Status Down alerts is one such example.

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Community Manager

Re: How to stop alerting on all route groups and just alert on specific important route groups in Ci

This can be refined by adding to the where clause in the threshold conditions. Here is a short video, as an example, refining the Route Group Status Down alerting "Route Group <RG_name> is down" to just alert on the important route groups.

 

 Steps are:

1. notify Ops team to expect false alerts in change window.

3. identify alerts in Alerts dashboard (such as in the Open Alerts for this kind of "Off Event" alerting that stays Open until the "Off" event closes it)

4. find the threshold condition using the Prognosis Client "IRGUI" by expanding teh node, Thresholds branch. The threshold happens to be the out of box "cmaDeviceAlerts" threshold and the condition in it that is responsible for the route group down alert is the CmaRouteGroupDown condition of the CallManagerRouteGroupShort record with where clause of 'ORDSTAT = 0'

5. Put the where clause into a display of the same record;

6. refined the where clause to, for example this kind of format,

ORDSTAT = 0 AND GRPNAME IN {"RG1_NAME","RG2_NAME", ....} 

 

and verify it in the display and then put it back into the threshold;

7. After clicking Start wait for the threshold check interval, eg, 5 minutes, then verify by observing the new alert(s) in Alerts dashboard to confirm the open alerts are only of the important route groups (that are down).

 

HTH

View solution in original post

Tags (1)
1 REPLY 1
Highlighted
Community Manager

Re: How to stop alerting on all route groups and just alert on specific important route groups in Ci

This can be refined by adding to the where clause in the threshold conditions. Here is a short video, as an example, refining the Route Group Status Down alerting "Route Group <RG_name> is down" to just alert on the important route groups.

 

 Steps are:

1. notify Ops team to expect false alerts in change window.

3. identify alerts in Alerts dashboard (such as in the Open Alerts for this kind of "Off Event" alerting that stays Open until the "Off" event closes it)

4. find the threshold condition using the Prognosis Client "IRGUI" by expanding teh node, Thresholds branch. The threshold happens to be the out of box "cmaDeviceAlerts" threshold and the condition in it that is responsible for the route group down alert is the CmaRouteGroupDown condition of the CallManagerRouteGroupShort record with where clause of 'ORDSTAT = 0'

5. Put the where clause into a display of the same record;

6. refined the where clause to, for example this kind of format,

ORDSTAT = 0 AND GRPNAME IN {"RG1_NAME","RG2_NAME", ....} 

 

and verify it in the display and then put it back into the threshold;

7. After clicking Start wait for the threshold check interval, eg, 5 minutes, then verify by observing the new alert(s) in Alerts dashboard to confirm the open alerts are only of the important route groups (that are down).

 

HTH

View solution in original post

Tags (1)
Webinar: Keep the modern workforce connected

Unified Communications has always been an important part of companies' digital transformation efforts due to its ability to enable rich virtual collaboration and communication. But with COVID-19, we've reached a break-through point.

Join Bill Haskins, Sr. Analyst & Partner, Unified Communications at Wainhouse Research, and John Ruthven, CEO at IR discuss UC challenges companies are experiencing due to the COVOID-19 crisis.

Join webinar