Avaya products have evolved in their ability to send alarm notifications to a third-party system.
What once started as text based alarms sent over a modem has now evolved into systems that can use the simple network management protocol (SNMP) to notify system administrators when an issue occurs.
While having SNMP alarming capabilities is helpful, it is not the optimum way to monitor an Avaya system and shouldn’t be the only way we monitor. Commonly used SNMP trap relay services available today make assumptions that ‘no news is good news’; if we don’t receive any SNMP traps the system must be ok, right?
Unfortunately, this is not the case and the absence of alarms does not always mean your Avaya system is healthy. With this type of SNMP alarming there is an assumption that is often overlooked and that is how do you know the Avaya application is even healthy enough to send you an alarm notification?
But if ‘no news is good news’, then everything must be functioning correctly, right? intlx Solutions' Avaya Visualize Monitoring can help you make sure that you not only receive SNMP traps but also make sure your system is online and capable of reporting alarms correctly.
Not only do we receive SNMP Traps and syslog messages but our monitoring tool keeps an active session into both Avaya Communication Manager and the Linux interface of your server to check for alarms.If your Communication Manager server is not available to be queried that will raise an alarm letting your team know there is an issue.
Besides your standard alarms, our Avaya monitoring tool collects system logs and denial event logs. The denial event logs are invaluable to help understand any underlying issues that may be happening on your system.
These denial events may never escalate into an alarm that you would receive from a standard SNMP trap relay system but they are important.
Example of denial events collected from Avaya Communication Manager: