HP-EMS
This MIB module describes traps generated by
the Event Monitor Service (EMS).
- Source file
HP-EMS- Last revised
- Identity
hpEMSMod- Base OID
1.3.6.1.4.1.11.2.3.1.7
Imported Objects
| SNMPv2-SMI | enterprises Integer32 IpAddress MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) |
Net-SNMP examples using the hp MIB directory Show commands
These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.
Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'HP-EMS' -M '/opt/observium/mibs/hp:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'HP-EMS::hpEMSMod'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'HP-EMS' -M '/opt/observium/mibs/hp:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'HP-EMS::hpEMSMod'
Objects (28)
Showing 28 of 28 objects
Object legend
Table
Row
Column
Scalar
Node
Object type
Icons distinguish tables, entry rows, columns, scalars, and structural nodes.
SNMPv2-TCTruthValue
Syntax
Blue badges identify the value syntax. Connected badges read as defining module and convention.
IF-MIBifIndex
Table index
Green identifies an index object; yellow names its module when the index is defined elsewhere.
r/w
deprecated
obsolete
Access and status
r/w means read-write. Grey labels mark definitions retained for compatibility.
OBS ✓
Observium use
The indicator appears only when Observium directly references that object.
ifOperStatus
.1.3.6.1.2.1…
Names and OIDs
Object names link to their detail pages. Hover or focus a linked name or badge for available definition details.
.1.3.6.1.4.1.11 |
||
.1.3.6.1.4.1.11.2 |
||
.1.3.6.1.4.1.11.2.3 |
||
.1.3.6.1.4.1.11.2.3.1 |
||
.1.3.6.1.4.1.11.2.3.1.7 |
||
.1.3.6.1.4.1.11.2.3.1.7.0 |
||
.1.3.6.1.4.1.11.2.3.1.7.1 |
||
.1.3.6.1.4.1.11.2.3.1.7.1.1 |
||
|
OctetString
|
.1.3.6.1.4.1.11.2.3.1.7.1.1.1 |
|
.1.3.6.1.4.1.11.2.3.1.7.1.1.10 |
||
|
OctetString
|
.1.3.6.1.4.1.11.2.3.1.7.1.1.11 |
|
.1.3.6.1.4.1.11.2.3.1.7.1.1.12 |
||
.1.3.6.1.4.1.11.2.3.1.7.1.1.2 |
||
|
OctetString
|
.1.3.6.1.4.1.11.2.3.1.7.1.1.3 |
|
.1.3.6.1.4.1.11.2.3.1.7.1.1.4 |
||
|
OctetString
|
.1.3.6.1.4.1.11.2.3.1.7.1.1.5 |
|
.1.3.6.1.4.1.11.2.3.1.7.1.1.6 |
||
|
OctetString
|
.1.3.6.1.4.1.11.2.3.1.7.1.1.7 |
|
.1.3.6.1.4.1.11.2.3.1.7.1.1.8 |
||
.1.3.6.1.4.1.11.2.3.1.7.1.1.9 |
||
.1.3.6.1.4.1.11.2.3.1.7.1.2 |
||
|
OctetString
|
.1.3.6.1.4.1.11.2.3.1.7.1.2.1 |
|
|
OctetString
|
.1.3.6.1.4.1.11.2.3.1.7.1.2.2 |
|
|
OctetString
|
.1.3.6.1.4.1.11.2.3.1.7.1.2.3 |
|
|
OctetString
|
.1.3.6.1.4.1.11.2.3.1.7.1.2.4 |
|
|
OctetString
|
.1.3.6.1.4.1.11.2.3.1.7.1.2.5 |
|
.1.3.6.1.4.1.11.2.3.1.7.1.2.6 |
||
|
OctetString
|
.1.3.6.1.4.1.11.2.3.1.7.1.2.7 |
Dependencies (1) 1 direct Show tree and compile order Hide dependency details
Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.
Dependency tree
Dependency-first compile order
- SNMPv2-SMIrfc
- HP-EMShpselected
Notifications / Traps (9)
| Name | OID | Description |
|---|---|---|
.1.3.6.1.4.1.11.2.3.1.7.0.1 |
The Event Monitoring Service (EMS) has generated an event
for a monitored resource. A Normal Event occurs when the value of the resource is in a 'normal' state and the threshold condition is not true. Monitoring requests configured for initial or return notification may generate this event. Also, the initial notification for a Change event is 'normal'. The data passed with the event: 1) The name of the resource being monitored. 2) The request id, a unique identifier for the monitoring request. This value should be used when using resdata to retrieve additional information about the event. 3) The operator used by EMS to determine when event notifications should be sent. Possible values include: poll, change, >, >=, <, <=, = and !=. 4) The resource type, which defines the type of value being monitored. Possible values include: string, enumerated, integer, and float. 5) The resource value, which is the current value of the resource being monitored. It is converted based on the resource type. 6) The threshold type (usually the same as the resource type) defines the type of value configured for the threshold. Possible values include: string, integer, and float. 7) The threshold value configured for the resource being monitored. 8) The user data flag, which indicates whether or not user data are available. User data are comments provided by the user when the request was configured. User data can be retrieved on the source node by running: /opt/resmon/bin/resdata -r <resource name> \ -R <request id> -u 9) The monitor data flag, which indicates whether or not the monitor has additional data regarding the event. Additional data provided by the resource monitor can be retrieved on the source node by running: /opt/resmon/bin/resdata -r <resource name> \ -R <request id> [-n <notify id>] -m 10) The notification trigger indicates if the resource condition is normal or not. For an EMSNormalEvent trap, the notification trigger is normal. 11) The event type indicates the type of notification being sent. The different types are: Poll - for notification at every interval Change - for notification when the value changes Normal - for notification when the threshold condition for the resource is not true Problem - for notification when the threshold condition for the resource is true Error - for notification when the monitor encountered an error determining the resource value 12) The notify id, a unique identifier for a specific notification event. This value should be used when using resdata to retrieve additional information about the event. Monitor data can be retrieved on the source node by running: /opt/resmon/bin/resdata -r <resource name> \ -R <request id> [-n <notify id>] -m |
|
.1.3.6.1.4.1.11.2.3.1.7.0.2 |
The Event Monitoring Service (EMS) has generated an event
for a monitored resource. A Problem Event occurs when the threshold condition defined for the resource is true. A Change Event occurs when the monitored value changes. Monitoring requests configured for notification when the value changes may generate this event. A Poll Event occurs regularly at the configured polling interval. An Error Event occurs when the value of a monitored resource cannot be obtained from the monitor. The data passed with the event: 1) The name of the resource being monitored. 2) The request id, a unique identifier for the monitoring request. This value should be used when using resdata to retrieve additional information about the event. 3) The operator used by EMS to determine when event notifications should be sent. Possible values include: poll, change, >, >=, <, <=, = and !=. 4) The resource type, which defines the type of value being monitored. Possible values include: string, enumerated, integer, and float. 5) The resource value, which is the current value of the resource being monitored. It is converted based on the resource type. 6) The threshold type (usually the same as the resource type) defines the type of value configured for the threshold. Possible values include: string, integer, and float. 7) The threshold value configured for the resource being monitored. 8) The user data flag, which indicates whether or not user data are available. User data are comments provided by the user when the request was configured. User data can be retrieved on the source node by running: /opt/resmon/bin/resdata -r <resource name> \ -R <request id> -u 9) The monitor data flag, which indicates whether or not the monitor has additional data regarding the event. Additional data provided by the resource monitor can be retrieved on the source node by running: /opt/resmon/bin/resdata -r <resource name> \ -R <request id> [-n <notify id>] -m 10) The notification trigger indicates if the resource condition is normal or not. For an EMSProblemEvent trap, the notification trigger is abnormal. 11) The event type indicates the type of notification being sent. The different types are: Poll - for notification at every interval Change - for notification when the value changes Normal - for notification when the threshold condition for the resource is not true Problem - for notification when the threshold condition for the resource is true Error - for notification when the monitor encountered an error determining the resource value 12) The notify id, a unique identifier for a specific notification event. This value should be used when using resdata to retrieve additional information about the event. Monitor data can be retrieved on the source node by running: /opt/resmon/bin/resdata -r <resource name> \ -R <request id> [-n <notify id>] -m |
|
.1.3.6.1.4.1.11.2.3.1.7.0.3 |
The Event Monitoring Service (EMS) has generated an event
for a monitored resource. A Monitor Reboot Event occurs when monitors are restarted due to a system reboot. The list of resources affected by the restart can be retrieved on the source node by running: /opt/resmon/bin/resdata -M <key> The data passed with the event: 1) The restart event type, which can be restart or reboot. For an EMSMonitorReboot trap, the restart type is reboot. 2) The title of the monitor that is restarted. 3) The command used to restart the monitor. 4) The name of the vendor that provided the monitor. 5) The version of the monitor. 6) The process ID of the restarted monitor process. 7) The monitor key, which may be used with the -M option to the resdata command to return the list of resources being monitored by the restarted monitor. The list of resources can be retrieved on the source node by running: /opt/resmon/bin/resdata -M <monitor key> |
|
.1.3.6.1.4.1.11.2.3.1.7.0.4 |
The Event Monitoring Service (EMS) has generated an event
for a monitored resource. A Monitor Restart Event occurs when EMS detects that a required monitor is no longer running, and restarts the monitor. The list of resources affected by the restart can be retrieved on the source node by running: /opt/resmon/bin/resdata -M <key> The data passed with the event: 1) The restart event type, which can be restart or reboot. For an EMSMonitorRestart trap, the restart type is restart. 2) The title of the monitor that is restarted. 3) The command used to restart the monitor. 4) The name of the vendor that provided the monitor. 5) The version of the monitor. 6) The process ID of the restarted monitor process. 7) The monitor key, which may be used with the -M option to the resdata command to return the list of resources being monitored by the restarted monitor. The list of resources can be retrieved on the source node by running: /opt/resmon/bin/resdata -M <monitor key> |
|
.1.3.6.1.4.1.11.2.3.1.7.0.5 |
The Event Monitoring Service (EMS) has generated an event
for a monitored resource. A Problem Event occurs when the threshold condition defined for the resource is true. A Change Event occurs when the monitored value changes. Monitoring requests configured for notification when the value changes may generate this event. A Poll Event occurs regularly at the configured polling interval. An Error Event occurs when the value of a monitored resource cannot be obtained from the monitor. The data passed with the event: 1) The name of the resource being monitored. 2) The request id, a unique identifier for the monitoring request. This value should be used when using resdata to retrieve additional information about the event. 3) The operator used by EMS to determine when event notifications should be sent. Possible values include: poll, change, >, >=, <, <=, = and !=. 4) The resource type, which defines the type of value being monitored. Possible values include: string, enumerated, integer, and float. 5) The resource value, which is the current value of the resource being monitored. It is converted based on the resource type. 6) The threshold type (usually the same as the resource type) defines the type of value configured for the threshold. Possible values include: string, integer, and float. 7) The threshold value configured for the resource being monitored. 8) The user data flag, which indicates whether or not user data are available. User data are comments provided by the user when the request was configured. User data can be retrieved on the source node by running: /opt/resmon/bin/resdata -r <resource name> \ -R <request id> -u 9) The monitor data flag, which indicates whether or not the monitor has additional data regarding the event. Additional data provided by the resource monitor can be retrieved on the source node by running: /opt/resmon/bin/resdata -r <resource name> \ -R <request id> [-n <notify id>] -m 10) The notification trigger indicates if the resource condition is normal or not. For an EMSProblemEvent trap, the notification trigger is abnormal. 11) The event type indicates the type of notification being sent. The different types are: Poll - for notification at every interval Change - for notification when the value changes Normal - for notification when the threshold condition for the resource is not true Problem - for notification when the threshold condition for the resource is true Error - for notification when the monitor encountered an error determining the resource value 12) The notify id, a unique identifier for a specific notification event. This value should be used when using resdata to retrieve additional information about the event. Monitor data can be retrieved on the source node by running: /opt/resmon/bin/resdata -r <resource name> \ -R <request id> [-n <notify id>] -m |
|
.1.3.6.1.4.1.11.2.3.1.7.0.6 |
The Event Monitoring Service (EMS) has generated an event
for a monitored resource. A Problem Event occurs when the threshold condition defined for the resource is true. A Change Event occurs when the monitored value changes. Monitoring requests configured for notification when the value changes may generate this event. A Poll Event occurs regularly at the configured polling interval. An Error Event occurs when the value of a monitored resource cannot be obtained from the monitor. The data passed with the event: 1) The name of the resource being monitored. 2) The request id, a unique identifier for the monitoring request. This value should be used when using resdata to retrieve additional information about the event. 3) The operator used by EMS to determine when event notifications should be sent. Possible values include: poll, change, >, >=, <, <=, = and !=. 4) The resource type, which defines the type of value being monitored. Possible values include: string, enumerated, integer, and float. 5) The resource value, which is the current value of the resource being monitored. It is converted based on the resource type. 6) The threshold type (usually the same as the resource type) defines the type of value configured for the threshold. Possible values include: string, integer, and float. 7) The threshold value configured for the resource being monitored. 8) The user data flag, which indicates whether or not user data are available. User data are comments provided by the user when the request was configured. User data can be retrieved on the source node by running: /opt/resmon/bin/resdata -r <resource name> \ -R <request id> -u 9) The monitor data flag, which indicates whether or not the monitor has additional data regarding the event. Additional data provided by the resource monitor can be retrieved on the source node by running: /opt/resmon/bin/resdata -r <resource name> \ -R <request id> [-n <notify id>] -m 10) The notification trigger indicates if the resource condition is normal or not. For an EMSProblemEvent trap, the notification trigger is abnormal. 11) The event type indicates the type of notification being sent. The different types are: Poll - for notification at every interval Change - for notification when the value changes Normal - for notification when the threshold condition for the resource is not true Problem - for notification when the threshold condition for the resource is true Error - for notification when the monitor encountered an error determining the resource value 12) The notify id, a unique identifier for a specific notification event. This value should be used when using resdata to retrieve additional information about the event. Monitor data can be retrieved on the source node by running: /opt/resmon/bin/resdata -r <resource name> \ -R <request id> [-n <notify id>] -m |
|
.1.3.6.1.4.1.11.2.3.1.7.0.7 |
The Event Monitoring Service (EMS) has generated an event
for a monitored resource. A Problem Event occurs when the threshold condition defined for the resource is true. A Change Event occurs when the monitored value changes. Monitoring requests configured for notification when the value changes may generate this event. A Poll Event occurs regularly at the configured polling interval. An Error Event occurs when the value of a monitored resource cannot be obtained from the monitor. The data passed with the event: 1) The name of the resource being monitored. 2) The request id, a unique identifier for the monitoring request. This value should be used when using resdata to retrieve additional information about the event. 3) The operator used by EMS to determine when event notifications should be sent. Possible values include: poll, change, >, >=, <, <=, = and !=. 4) The resource type, which defines the type of value being monitored. Possible values include: string, enumerated, integer, and float. 5) The resource value, which is the current value of the resource being monitored. It is converted based on the resource type. 6) The threshold type (usually the same as the resource type) defines the type of value configured for the threshold. Possible values include: string, integer, and float. 7) The threshold value configured for the resource being monitored. 8) The user data flag, which indicates whether or not user data are available. User data are comments provided by the user when the request was configured. User data can be retrieved on the source node by running: /opt/resmon/bin/resdata -r <resource name> \ -R <request id> -u 9) The monitor data flag, which indicates whether or not the monitor has additional data regarding the event. Additional data provided by the resource monitor can be retrieved on the source node by running: /opt/resmon/bin/resdata -r <resource name> \ -R <request id> [-n <notify id>] -m 10) The notification trigger indicates if the resource condition is normal or not. For an EMSProblemEvent trap, the notification trigger is abnormal. 11) The event type indicates the type of notification being sent. The different types are: Poll - for notification at every interval Change - for notification when the value changes Normal - for notification when the threshold condition for the resource is not true Problem - for notification when the threshold condition for the resource is true Error - for notification when the monitor encountered an error determining the resource value 12) The notify id, a unique identifier for a specific notification event. This value should be used when using resdata to retrieve additional information about the event. Monitor data can be retrieved on the source node by running: /opt/resmon/bin/resdata -r <resource name> \ -R <request id> [-n <notify id>] -m |
|
.1.3.6.1.4.1.11.2.3.1.7.0.8 |
The Event Monitoring Service (EMS) has generated an event
for a monitored resource. A Problem Event occurs when the threshold condition defined for the resource is true. A Change Event occurs when the monitored value changes. Monitoring requests configured for notification when the value changes may generate this event. A Poll Event occurs regularly at the configured polling interval. An Error Event occurs when the value of a monitored resource cannot be obtained from the monitor. The data passed with the event: 1) The name of the resource being monitored. 2) The request id, a unique identifier for the monitoring request. This value should be used when using resdata to retrieve additional information about the event. 3) The operator used by EMS to determine when event notifications should be sent. Possible values include: poll, change, >, >=, <, <=, = and !=. 4) The resource type, which defines the type of value being monitored. Possible values include: string, enumerated, integer, and float. 5) The resource value, which is the current value of the resource being monitored. It is converted based on the resource type. 6) The threshold type (usually the same as the resource type) defines the type of value configured for the threshold. Possible values include: string, integer, and float. 7) The threshold value configured for the resource being monitored. 8) The user data flag, which indicates whether or not user data are available. User data are comments provided by the user when the request was configured. User data can be retrieved on the source node by running: /opt/resmon/bin/resdata -r <resource name> \ -R <request id> -u 9) The monitor data flag, which indicates whether or not the monitor has additional data regarding the event. Additional data provided by the resource monitor can be retrieved on the source node by running: /opt/resmon/bin/resdata -r <resource name> \ -R <request id> [-n <notify id>] -m 10) The notification trigger indicates if the resource condition is normal or not. For an EMSProblemEvent trap, the notification trigger is abnormal. 11) The event type indicates the type of notification being sent. The different types are: Poll - for notification at every interval Change - for notification when the value changes Normal - for notification when the threshold condition for the resource is not true Problem - for notification when the threshold condition for the resource is true Error - for notification when the monitor encountered an error determining the resource value 12) The notify id, a unique identifier for a specific notification event. This value should be used when using resdata to retrieve additional information about the event. Monitor data can be retrieved on the source node by running: /opt/resmon/bin/resdata -r <resource name> \ -R <request id> [-n <notify id>] -m |
|
.1.3.6.1.4.1.11.2.3.1.7.0.9 |
The Event Monitoring Service (EMS) has generated an event
for a monitored resource. A Problem Event occurs when the threshold condition defined for the resource is true. A Change Event occurs when the monitored value changes. Monitoring requests configured for notification when the value changes may generate this event. A Poll Event occurs regularly at the configured polling interval. An Error Event occurs when the value of a monitored resource cannot be obtained from the monitor. The data passed with the event: 1) The name of the resource being monitored. 2) The request id, a unique identifier for the monitoring request. This value should be used when using resdata to retrieve additional information about the event. 3) The operator used by EMS to determine when event notifications should be sent. Possible values include: poll, change, >, >=, <, <=, = and !=. 4) The resource type, which defines the type of value being monitored. Possible values include: string, enumerated, integer, and float. 5) The resource value, which is the current value of the resource being monitored. It is converted based on the resource type. 6) The threshold type (usually the same as the resource type) defines the type of value configured for the threshold. Possible values include: string, integer, and float. 7) The threshold value configured for the resource being monitored. 8) The user data flag, which indicates whether or not user data are available. User data are comments provided by the user when the request was configured. User data can be retrieved on the source node by running: /opt/resmon/bin/resdata -r <resource name> \ -R <request id> -u 9) The monitor data flag, which indicates whether or not the monitor has additional data regarding the event. Additional data provided by the resource monitor can be retrieved on the source node by running: /opt/resmon/bin/resdata -r <resource name> \ -R <request id> [-n <notify id>] -m 10) The notification trigger indicates if the resource condition is normal or not. For an EMSProblemEvent trap, the notification trigger is abnormal. 11) The event type indicates the type of notification being sent. The different types are: Poll - for notification at every interval Change - for notification when the value changes Normal - for notification when the threshold condition for the resource is not true Problem - for notification when the threshold condition for the resource is true Error - for notification when the monitor encountered an error determining the resource value 12) The notify id, a unique identifier for a specific notification event. This value should be used when using resdata to retrieve additional information about the event. Monitor data can be retrieved on the source node by running: /opt/resmon/bin/resdata -r <resource name> \ -R <request id> [-n <notify id>] -m |
