cancel
Showing results for 
Search instead for 
Did you mean: 

How to remove alerting for unwanted / used trunk in CUCM cluster

Venkata
05 Base Camper

How to remove alerting for unwanted / used trunk in CUCM cluster

Hello Team,

 

There is an unwanted/decommissioned  trunk in our CUCM and I need to suspend monitoring for that trunk as it is generating alerts as trunk down which is noise for us.

 

Can someone help to sort out this situation.

 

Thanks,

Venkata.

Tags (2)
1 ACCEPTED SOLUTION

Accepted Solutions

Re: How to remove alerting for unwanted / used trunk in CUCM cluster

Hi @Venkata,

 

Assuming the alert is being generated by the CmaTrunkDownErr condition of the cmaDeviceAlerts threshold, you could  exclude the trunk by refining the where clause to exclude that trunk. For example, adding the clause:

      AND DEVNAME <> "[device name of the trunk you don't want to alert on]"

This should prevent that condition from generating alerts for that specific trunk. This is what it would look like in the threshold properties:

Filter using exact Device Name.jpg

 

If you've removed the trunk from CUCM, the change may not reflect in Prognosis until the following day because the device list is normally only refreshed once per day during the 4am maintenance window. If you need to force it to update immediately, restarting the Prognosis cluster collector should pick up the change providing it is reflected in the configuration data supplied by the CUCM.

 

I hope this helps!

Regards,

Scott Clement

View solution in original post

2 REPLIES 2

Re: How to remove alerting for unwanted / used trunk in CUCM cluster

Hi @Venkata,

 

Assuming the alert is being generated by the CmaTrunkDownErr condition of the cmaDeviceAlerts threshold, you could  exclude the trunk by refining the where clause to exclude that trunk. For example, adding the clause:

      AND DEVNAME <> "[device name of the trunk you don't want to alert on]"

This should prevent that condition from generating alerts for that specific trunk. This is what it would look like in the threshold properties:

Filter using exact Device Name.jpg

 

If you've removed the trunk from CUCM, the change may not reflect in Prognosis until the following day because the device list is normally only refreshed once per day during the 4am maintenance window. If you need to force it to update immediately, restarting the Prognosis cluster collector should pick up the change providing it is reflected in the configuration data supplied by the CUCM.

 

I hope this helps!

Regards,

Scott Clement

Venkata
05 Base Camper

Re: How to remove alerting for unwanted / used trunk in CUCM cluster

Hi Scott Clement,

 

Thanks for your detailed explanation.

 

Your solution worked and I can able to stop monitoring for single as well as multiple trunks in the CUCM cluster.

 

Thanks,

Venkata.

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
Top Liked Members