GSX Monitor can be configured to forward alerts to any Simple Network Management Protocol (SNMP) aware Enterprise Management System such as HP OpenView or IBM Tivoli.
This article details the SNMP Trap variables at Object Identifier (OID) root .1.3.6.1.4.1.9617 that can be used by any SNMP alert profile configured in GSX Monitor.
If you are using Microsoft SCOM you will not need the definitions below as we provide a SCOM 2007 and SCOM 2012 Management Pack on our support website.
How It Works
SNMP Traps enable an agent (GSX Monitor) to notify the management station (Enterprise Management System) of significant events (alerts) by way of an unsolicited SNMP message. The unsolicited Traps or data packets are sent from the SNMP client to the destination server without being explicitly requested or acknowledged.
Here is a text file containing an example of a SNMP Trap generated by GSX Monitor.
In the above image, we can see the variables [1] - [14]. The alert message details are in variable [1] the trapVars.trapMessage.0 variable: we can see a disk space alert in the message details. The host name generating the alert is in variable [5] trapVars.resource.0. If an alert profile is configured to send SNMP Traps, GSX Monitor will use some custom variables that are defined in the table below.
Enterprise Management Systems must be correctly configured to interpret the content of SNMP traps in order to be able to determine how to handle the alerts received from GSX Monitor.
Variable |
Definition |
Type |
---|---|---|
[1] - trapMessage |
Complete trap message |
DisplayString |
[2] - gsxStationName |
GSX Monitor workstation sending the trap |
DisplayString |
[3] - className |
Class of the alert |
DisplayString |
[4] - alertType |
Type of the alert |
DisplayString |
[5] - resource |
Resource in error |
DisplayString |
[6] - subResource |
Sub-resource in error |
DisplayString |
[7] - status |
Status of the resource sending the trap |
DisplayString |
[8] - severity |
Severity of the error |
Integer |
[9] - date |
Date of error detection, using ticks format |
DisplayString (ticks) |
[10] - alertID |
Unique identifier of the alert |
DisplayString |
[11] - EntityID |
Unique internal GSX Monitor installation identifier |
DisplayString |
[12] - Reminder |
(Is this Alert a Reminder) |
Boolean |
[13] - Escalation |
(Is this Alert an Escalation) |
Boolean |
[14] - Test |
(Is this Alert a Test) |
Boolean |
[15] - Statistics Reset |
Resets all open alerts associated with the EntityID |
Boolean |
[16] - SCOM Severity |
The severity level; info, warning, critical. |
Integer |
[17] - Alert Date |
The date the alert is sent |
DisplayString |
Variable [10] was introduced in GSX Monitor 10.6.
Variables [11 - 17] were introduced in GSX Monitor 10.11.1.
Variable [9] was changed to server tick format in GSX Monitor 10.10.
GSX Monitor uses "public" as the default community string for all traps, follow this article to change this configuration.