We've been receiving a lot of "false" alerts from cmaServerAlerts. How can we fix this?
Solved! Go to Solution.
If any Perfmon query fails to return data, Prognosis will mark the server as "Not Contactable".
Prognosis sends about 18,000-19,000 queries using SOAP/AXL to each CUCM server every 24 hours. Most of these queries are Perfmon queries.
The best solution is to change the cmaServerDown Condition in the cmaServerAlerts Threshold to check every 60 seconds and only alert after 2 consecutive instances of the CNTBL field = 0.
• A 30 second timer instead of a 60 second timer could be used.
You can change any of these settings to better fit your company policies. I have seen some companies have to raise it to 3 consecutive occurrences.
If any Perfmon query fails to return data, Prognosis will mark the server as "Not Contactable".
Prognosis sends about 18,000-19,000 queries using SOAP/AXL to each CUCM server every 24 hours. Most of these queries are Perfmon queries.
The best solution is to change the cmaServerDown Condition in the cmaServerAlerts Threshold to check every 60 seconds and only alert after 2 consecutive instances of the CNTBL field = 0.
• A 30 second timer instead of a 60 second timer could be used.
You can change any of these settings to better fit your company policies. I have seen some companies have to raise it to 3 consecutive occurrences.
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 webinarMembers | Likes |
---|---|
23 | |
23 | |
14 | |
10 | |
8 |