All MIBs › HP-EMS
Organization: Hewlett Packard Company, Manageability Solutions Lab
Last Updated: 2003-09-19
Category: Alarm and Event Management, Domain: Network Management, Technology: Network Monitoring, Vendor: HP/HPE
Description: HP Enterprise Management System MIB providing event management and alarm notification objects for HP network equipment.
Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.
What Is HP-EMS?
HP-EMS is an HP MIB module dedicated entirely to describing SNMP traps generated by HP's Event Monitor Service (EMS), a fault- and event-notification subsystem for HP network equipment. Rather than defining pollable configuration or counter objects, it defines the trap/notification structure used to alert management stations when the EMS detects noteworthy events on the device. Its monitoring relevance is therefore centered on faults and event alerts rather than continuously polled hardware counters: it enables asynchronous notification of conditions the device's EMS considers significant, which could include hardware or environmental faults depending on the underlying event sources feeding the EMS. As a trap-defining module it depends conceptually on whatever underlying HP hardware/software MIBs supply the actual monitored conditions that trigger EMS events. It is deployed on HP network equipment running the Event Monitor Service, where administrators want push-based alerting rather than only polling. Engineers can download the HP-EMS file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in HP-EMS. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.
Supported Devices
- HP network equipment running Event Monitor Service
Monitoring Examples
No pollable data objects were present in the sample for this module -- it defines trap/notification structures for the Event Monitor Service rather than tables of monitorable counters. An NMS would register to receive HP-EMS traps and react when EMS determines an event has occurred, but the specific trap varbinds are not present in the available sample. Because this module's content is fault-notification-only, no concrete polling scenario can be honestly constructed here.
This MIB depends on
Related MIBs
Imported Objects
From SNMPv2-SMI
| Integer32 | |
| IpAddress | |
| MODULE-IDENTITY | |
| NOTIFICATION-TYPE | |
| OBJECT-TYPE | |
| enterprises |
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| hp | 1.3.6.1.4.1.11 | |||
| nm | 1.3.6.1.4.1.11.2 | |||
| system | 1.3.6.1.4.1.11.2.3 | |||
| general | 1.3.6.1.4.1.11.2.3.1 | |||
| hpEMSMod | 1.3.6.1.4.1.11.2.3.1.7 | This MIB module describes traps generated by the Event Monitor Service (EMS). | ||
| hpEMSTraps | 1.3.6.1.4.1.11.2.3.1.7.0 | |||
| NTF hpEMSNormalEvent | 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, >, >=, \ -R -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 \ -R [-n ] -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 \ -R [-n ] -m | ||
| NTF hpEMSProblemEvent | 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, >, >=, \ -R -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 \ -R [-n ] -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 \ -R [-n ] -m | ||
| NTF hpEMSMonitorReboot | 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 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 | ||
| NTF hpEMSMonitorRestart | 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 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 | ||
| NTF hpEMSNormalSevEvent | 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, >, >=, \ -R -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 \ -R [-n ] -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 \ -R [-n ] -m | ||
| NTF hpEMSWarningEvent | 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, >, >=, \ -R -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 \ -R [-n ] -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 \ -R [-n ] -m | ||
| NTF hpEMSMinorEvent | 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, >, >=, \ -R -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 \ -R [-n ] -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 \ -R [-n ] -m | ||
| NTF hpEMSMajorEvent | 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, >, >=, \ -R -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 \ -R [-n ] -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 \ -R [-n ] -m | ||
| NTF hpEMSCriticalEvent | 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, >, >=, \ -R -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 \ -R [-n ] -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 \ -R [-n ] -m | ||
| hpEMSObjects | 1.3.6.1.4.1.11.2.3.1.7.1 | |||
| hpEMSNotify | 1.3.6.1.4.1.11.2.3.1.7.1.1 | |||
| OCT hpEMSResourceName | 1.3.6.1.4.1.11.2.3.1.7.1.1.1 | OCTET STRING | read-only | Full EMS name of the resource being monitored |
| INT hpEMSRequestID | 1.3.6.1.4.1.11.2.3.1.7.1.1.2 | INTEGER | read-only | A unique identifier for the monitoring request |
| OCT hpEMSOperator | 1.3.6.1.4.1.11.2.3.1.7.1.1.3 | OCTET STRING | read-only | Operator indicates poll, change or threshold condition operator: >, >=, <, <=, ==, != |
| INT hpEMSResourceType | 1.3.6.1.4.1.11.2.3.1.7.1.1.4 | INTEGER | read-only | Integer representing the resource type: 3009 = String 3010 = Sbit32 (signed 32 bit integer) 3011 = Ubit32 (unsigned 32 bit integer) 3012 = Sbit64 (future use) 3013 = Ubit64 (future use) 3014 = Float64 (64 floating point number) 3015 = Enumerated Type 3016 = Error |
| OCT hpEMSResourceValue | 1.3.6.1.4.1.11.2.3.1.7.1.1.5 | OCTET STRING | read-only | Quoted string representing resource value, should be converted using the Resource Type indicated in Variable #4 Not applicable if Resource Type is Error |
| INT hpEMSThresholdType | 1.3.6.1.4.1.11.2.3.1.7.1.1.6 | INTEGER | read-only | Integer representing the threshold type, this is usually the same as resource type. Integer representing the threshold type: 3009 = String 3010 = Sbit32 (signed 32 bit integer) 3011 = Ubit32 (unsigned 32 bit integer) 3012 = Sbit64 (future use) 3013 = Ubit64 (future use) 3014 = Float64 (64 floating point number) 3015 = Enumerated Type 3016 = Error Not applicable if operator is poll or change; or if Resource Type is Error Note: enumerated type is not supported as threshold type. |
| OCT hpEMSThresholdValue | 1.3.6.1.4.1.11.2.3.1.7.1.1.7 | OCTET STRING | read-only | Quoted string representing threshold value, should be converted using the Threshold Type indicated in Variable #6. Not applicable if operator is poll or change; or if Resource Type is Error |
| INT hpEMSUserDataFlag | 1.3.6.1.4.1.11.2.3.1.7.1.1.8 | INTEGER | read-only | Indicates that additional user data is available from EMS 0 = no user data 1 = user (comment) data exists |
| INT hpEMSMonitorDataFlag | 1.3.6.1.4.1.11.2.3.1.7.1.1.9 | INTEGER | read-only | Indicates that additional monitor data is available from EMS 0 = no monitor data 1 = monitor data exists |
| INT hpEMSNotificationTrigger | 1.3.6.1.4.1.11.2.3.1.7.1.1.10 | INTEGER | read-only | Indicates whether normal or problem event 0 = normal 1 = abnormal (threshold is true) 5 = abnormal (severity is normal) 6 = abnormal (severity is warning) 7 = abnormal (severity is minor) 8 = abnormal (severity is major) 9 = abnormal (severity is critical) |
| OCT hpEMSEventType | 1.3.6.1.4.1.11.2.3.1.7.1.1.11 | OCTET STRING | read-only | String representing event type: Poll (for 'At Every Interval') Change (for 'When value changes') Normal (for when threshold condition is not true) Problem (for when threshold condition is true) Error |
| INT hpEMSNotifyID | 1.3.6.1.4.1.11.2.3.1.7.1.1.12 | INTEGER | read-only | Unique identifier for this particular event |
| hpEMSMonitor | 1.3.6.1.4.1.11.2.3.1.7.1.2 | |||
| OCT hpEMSRestartType | 1.3.6.1.4.1.11.2.3.1.7.1.2.1 | OCTET STRING | read-only | REBOOT or RESTART |
| OCT hpEMSMonitorTitle | 1.3.6.1.4.1.11.2.3.1.7.1.2.2 | OCTET STRING | read-only | Title of the monitor affected by the outage |
| OCT hpEMSCommand | 1.3.6.1.4.1.11.2.3.1.7.1.2.3 | OCTET STRING | read-only | Command used to launch the monitor |
| OCT hpEMSVendor | 1.3.6.1.4.1.11.2.3.1.7.1.2.4 | OCTET STRING | read-only | Vendor who supplied the monitor |
| OCT hpEMSVersion | 1.3.6.1.4.1.11.2.3.1.7.1.2.5 | OCTET STRING | read-only | Version of the monitor |
| INT hpEMSPID | 1.3.6.1.4.1.11.2.3.1.7.1.2.6 | INTEGER | read-only | Process ID of the monitor |
| OCT hpEMSMonitorKey | 1.3.6.1.4.1.11.2.3.1.7.1.2.7 | OCTET STRING | read-only | Unique identified for this monitor, to be used for running resdata to get list of resources affected by the monitor outage. |
RFC description
HP/HPE SNMP MIB for enterprise management systems providing management information base objects for querying, updating, and monitoring SNMP variables on HPE storage systems, servers, and network switches.
Start monitoring HP network equipment running Event Monitor Service (EMS traps) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.