|
|
Alarm Notification Types
Reference Number: AA-02142 Views: 9842 |
0 Rating/ Voters
|
|
When enabled, the LumenVox Manager can send a number of different types of SNMP Trap notifications.
These notifications are typically messages or alerts to indicate some change in state of some monitored object, or a heartbeat message to indicate that the LumenVox Manager is still running. These Trap notifications are sent to all configured TRAP_SERVERS using SNMP v2c protocol by default.
Changes introduced in LumenVox version 15.1 allow any of SNMP V1, V2c or V3 protocol options to be selected when sending SNMP traps. Version 15.0 only supported SNMPv2 protocol when sending trap messages.
Here is a complete list of the Types of Trap message that can be generated by LumenVox:
Trap Type
|
Description
|
lvAlarmHeartbeat
|
This message type is sent to all registered TRAP_SERVERS at the specified HEARTBEAT_INTERVAL. When this HEARTBEAT_INTERVAL is set to 0 (the default), no heartbeat messages will be sent.
This notification type is sent with INFO severity and does not include a CorrelationID field (since it is not an alarm or a clear notification). A count of the current heartbeats sent is sent within the lvTrapAdditionText field.
Specified TRAP_SERVERS can be configured to expect these trap notifications, and if no heartbeat is received within a certain time period, this can be used to indicate a failure of the LumenVox server, or LumenVox Manager Service – either of which should be investigated.
|
lvAlarmCpuOverload
|
There are 3 thresholds (MINOR, MAJOR and CRIT) that can be defined for this type of alarm (in manager.conf). When system CPU utilization exceeds one of the specified thresholds, the corresponding trap notification will be sent with the appropriate severity.
|
lvAlarmCpuAbate
|
Sent when the corresponding lvAlarmCpuOverload alert has abated – when system CPU use has fallen below the specified threshold.
|
lvAlarmMemoryOverload
|
There are 3 thresholds (MINOR, MAJOR and CRIT) that can be defined for this type of alarm. When system memory utilization exceeds one of the specified thresholds, the appropriate corresponding trap notification will be sent with the appropriate severity.
|
lvAlarmMemoryAbate
|
Sent when the corresponding lvAlarmMemoryOverload alert has abated – when system memory use has fallen below the specified threshold
|
lvAlarmCommsFailure
|
When communication with one of the configured LumenVox services is lost, an alert of this type will be generated.
If the service is designated as the Primary (first listed) instance, then a message will indicate this.
Also, if alternate servers of this type remain available, this will be indicated, as well as affect the notification severity. When alternate(s) are available, the message will have MINOR severity. When no alternate is available, the message will have CRIT severity.
|
lvAlarmCommsRestore
|
Sent when the corresponding lvAlarmCommsFailure alert has been removed – when the communication link is restored.
|
lvAlarmNoLicense
|
This message is generated whenever an attempt to request ASR or TTS licenses is made by the Media Server service.
The notification will indicate whether the failure was due to a TTS license request or an ASR license request. The message severity will be CRIT
|
lvAlarmLicenseAvailable
|
Sent whenever the corresponding lvAlarmNoLicense alert has cleared – once a request for the appropriate ASR or TTS license type has succeeded.
|
lvAlarmLowLicenseAlert
|
This is not implemented in the current version (for future use)
|
lvAlarmLowLicenseAbate
|
This is not implemented in the current version (for future use)
|
lvAlarmLowDiskSpaceAlert
|
There are 3 thresholds (MINOR, MAJOR and CRIT) that can be defined for this type of alarm.
When free disk space drops below one of the specified thresholds, the appropriate trap notification will be sent with the corresponding severity.
Note that the disk drive / partition being monitored is the one associated with the LumenVox Manager’s LVLOGS folder – wherever the manager’s logs are stored. We recommend that systems are configured to store their log files to the same disk / partition for all LumenVox services to avoid any confusion, since only this disk/partition is monitored.
|
lvAlarmLowDiskSpaceAbate
|
These messages will be sent when the corresponding lvAlarmLowDiskSpaceAlert alert has abated – whenever free disk space has been raised above the specified threshold.
|
lvAlarmSyncFailure
|
When synchronization communication between the active License Server and the LumenVox licensing nodes in the Internet cannot be performed, an alert of this type will be generated.
If the number of consecutive synchronization attempt failures is below 10, the message will have MINOR severity. When 10 consecutive synchronization attempts have failed, the message will have CRIT severity.
Please verify that no Firewall issues prevent this connection, which is typically the cause of this type of alert.
|
lvAlarmSyncRestore
|
These messages will be sent when the corresponding lvAlarmSyncFailure alert has abated – whenever the license server is able to correctly synchronize with the licensing nodes in the Internet.
|
Note that these trap alert types are defined within the LUMENVOX-SNMP-MIB definition document that can be imported into many standard SNMP systems. The definition of these notifications is shown here:
See the Trap Message Contents article for additional information about the structure of Variable Bindings that are sent within these notification messages.
|
|
|