LIEBERT-GP-NOTIFICATIONS-MIB

All MIBs › LIEBERT-GP-NOTIFICATIONS-MIB

Organization: Liebert Corporation

Last Updated: 2008-07-02

Category: Alarm and Event Management, Domain: Power/UPS, Vendor: Liebert

Description: Defines SNMP notification traps and alerts for Liebert GlobalProducts power and environmental monitoring systems.

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 LIEBERT-GP-NOTIFICATIONS-MIB?

LIEBERT-GP-NOTIFICATIONS-MIB is a Liebert Corporation (now Vertiv) proprietary MIB that defines SNMP notification (trap) OIDs for the Liebert GlobalProducts (GP) family of power and environmental monitoring systems. It is a notification-registration module: it doesn't expose polled runtime tables of its own but defines the trap identifiers used to alert on power and environmental conditions from Liebert UPS, PDU, and precision-cooling units. Its monitoring value is squarely in hardware and environmental fault detection — traps registered here typically cover power supply status, battery/UPS state, and temperature/humidity or cooling-unit alarms in the data center. It is a companion to Liebert's broader GP MIB tree, which holds the actual monitored objects, with this module solely defining the notification OIDs that tree references. It is deployed in data centers and server rooms where Liebert UPS, PDU, and CRAC/cooling units are monitored by a DCIM system or NMS via SNMP traps. Engineers can download the LIEBERT-GP-NOTIFICATIONS-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in LIEBERT-GP-NOTIFICATIONS-MIB. 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

Liebert (Vertiv) GlobalProducts UPS, PDU, and precision-cooling equipment

Monitoring Examples

No sample_objects were captured for this module, so no concrete varbind names can be cited; the module_desc confirms it is scoped to "register Liebert SNMP OIDs" for notifications rather than defining pollable data objects itself. In practice a DCIM or NMS platform would subscribe to these traps to be alerted immediately when a Liebert UPS loses utility power, a battery reaches end-of-life, or a precision cooling unit reports an over-temperature condition, rather than by polling this module directly.

What Can Be Monitored

UPS/battery status alarms
power supply fault notifications
environmental (temperature/humidity) alarms
cooling unit fault notifications

Imported Objects

From LIEBERT-GP-CONDITIONS-MIB

lgpConditionDescr	OBJECT-TYPE
lgpConditionId	OBJECT-TYPE
lgpConditionTableRef	OBJECT-TYPE
lgpConditionTableRowRef	OBJECT-TYPE
lgpConditionTime	OBJECT-TYPE

From LIEBERT-GP-REGISTRATION-MIB

lgpNotifications	OBJECT-IDENTITY
liebertNotificationsModuleReg	OBJECT-IDENTITY

From RFC1213-MIB

sysUpTime

From SNMPv2-SMI

MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-IDENTITY
OBJECT-TYPE

OIDs

OID symbolic	OID numeric	Type	Access	Description
liebertGlobalProductsNotificationsModule	1.3.6.1.4.1.476.1.42.1.4.1			The MIB module used to register Liebert SNMP OIDs. Copyright 2000-2008 Liebert Corporation. All rights reserved. Reproduction of this document is authorized on the condition that the forgoing copyright notice is included. This Specification is supplied 'AS IS' and Liebert Corporation makes no warranty, either express or implied, as to the use, operation, condition, or performance of the Specification.
lgpEventNotifications	1.3.6.1.4.1.476.1.42.3.3.0			Notifications for Liebert Global Products.
NTF lgpEventConditionEntryAdded	1.3.6.1.4.1.476.1.42.3.3.0.1			This notification is sent each time a condition is inserted into the conditions table.
NTF lgpEventConditionEntryRemoved	1.3.6.1.4.1.476.1.42.3.3.0.2			This notification is sent each time a condition is removed from the conditions table.
NTF lgpEventLowBatteryWarning	1.3.6.1.4.1.476.1.42.3.3.0.3			The battery's remaining charge is less than or equal to the agent's configured low threshold 'lgpPwrConfigLowBatteryWarningTime'.
NTF lgpEventLoadTransferedToBypass	1.3.6.1.4.1.476.1.42.3.3.0.4			The device has transferred the load to the bypass source.
NTF lgpEventInternalFault	1.3.6.1.4.1.476.1.42.3.3.0.5			The device has reported an internal fault.
NTF lgpEventBatteryTestFailed	1.3.6.1.4.1.476.1.42.3.3.0.6			The device has reported a battery self-test failure.
NTF lgpEventOutputOverload	1.3.6.1.4.1.476.1.42.3.3.0.7			The device has reported an output overload condition.
NTF lgpEventEstablishedPowerRedundancy	1.3.6.1.4.1.476.1.42.3.3.0.8			The device has transitioned to the user defined redundant state.
NTF lgpEventLostPowerRedundancy	1.3.6.1.4.1.476.1.42.3.3.0.9			The device as transitioned to a non-redundant power state as defined by the user configured threshold.
NTF lgpEventPowerModuleFailure	1.3.6.1.4.1.476.1.42.3.3.0.10			Device power module failure.
NTF lgpEventBatteryModuleFailure	1.3.6.1.4.1.476.1.42.3.3.0.11			Device battery module failure.
NTF lgpEventControlModuleFailure	1.3.6.1.4.1.476.1.42.3.3.0.12			Device control module failure.
NTF lgpEventPowerModuleWarning	1.3.6.1.4.1.476.1.42.3.3.0.13			Device power module warning.
NTF lgpEventBatteryModuleWarning	1.3.6.1.4.1.476.1.42.3.3.0.14			Device battery module warning.
NTF lgpEventControlModuleWarning	1.3.6.1.4.1.476.1.42.3.3.0.15			Device control module warning.
NTF lgpEventAgentFirmwareUpdateSuccessful	1.3.6.1.4.1.476.1.42.3.3.0.16			The firmware update to the agent card has completed successfully. This element has been relocated to lgpAgentFirmwareUpdateSuccessful in the LIEBERT-GP-AGENT-MIB document.
NTF lgpEventAgentFirmwareCorrupt	1.3.6.1.4.1.476.1.42.3.3.0.17			The firmware update to the agent card has failed and the firmware is now corrupt. This element has been relocated to lgpAgentFirmwareCorrupt in the LIEBERT-GP-AGENT-MIB document.
NTF lgpEventConfigModified	1.3.6.1.4.1.476.1.42.3.3.0.18			Configuration for the referenced PDU has been modified.
NTF lgpEventModuleAdded	1.3.6.1.4.1.476.1.42.3.3.0.19			A hot-swappable module has been added to the object specified by the lgpEventParmTableRef and lgpEventParmTableRowRef.
NTF lgpEventModuleRemoved	1.3.6.1.4.1.476.1.42.3.3.0.20			A hot-swappable module has been removed from the object specified by the lgpEventParmTableRef and lgpEventParmTableRowRef.
NTF lgpEventRcpPowerStateChangeOn	1.3.6.1.4.1.476.1.42.3.3.0.21			Receptacle's power state has been changed from OFF to ON.
NTF lgpEventRcpPowerStateChangeOff	1.3.6.1.4.1.476.1.42.3.3.0.22			Receptacle's power state has been changed from ON to OFF.
NTF lgpEventRcpLoadAdded	1.3.6.1.4.1.476.1.42.3.3.0.23			The receptacle's load started drawing power. This notification is asserted when the receptacle power is ON and the associated load was previously not drawing power but is now drawing power. This event is not asserted as a result of turning the receptacle power ON.
NTF lgpEventRcpLoadRemoved	1.3.6.1.4.1.476.1.42.3.3.0.24			The receptacle's load stopped drawing power. This notification is asserted when the receptacle power is ON and the associated load was previously drawing power but is now no longer drawing power. This event is not asserted as a result of turning the receptacle power OFF.
lgpEventParameters	1.3.6.1.4.1.476.1.42.3.3.10			This sub tree describes various parameters/data that are carried in the payload of some notifications.
OID lgpEventParmTableRef	1.3.6.1.4.1.476.1.42.3.3.10.5	OBJECT IDENTIFIER	read-only	This object will be included as a varbind in some lgpEventNotifications. It is a reference to a table object in the MIB. The value of this object will be the OID of a table that the object that the notification applies to is defined. The notification containing this object will also contain a varbind 'lgpEventParmTableRowRef' that will specify which instance (row) in the table the object is defined in. Example: NOTIFICATION: lgpEventConditionEntryAdded varbind: lgpConditionId 6 varbind: lgpConditionDescr lgpConditionRcpBranchBreakerOpen varbind: lgpConditionTime 393884848 varbind: lgpEventParmTableRef lgpPduRbTable varbind: lgpEventParmTableRowRef lgpPduRbEntryId.1.4 In the above example the breaker opened for a Receptacle branch. The specific receptacle branch is specified by the additional varbind (lgpEventParmTableRowRef). In this case the notification is for the 4th receptacle branch on the 1st PDU in the PDU cluster.
OID lgpEventParmTableRowRef	1.3.6.1.4.1.476.1.42.3.3.10.6	OBJECT IDENTIFIER	read-only	This is a reference to the intersection of a row and column (cell) in the table specified by the companion varbind (lgpEventParmTableRef) in this notification. The row in the table where this cell exists represents the object that this notification applies to. Example: NOTIFICATION: lgpEventRcpPowerStateChangeOff varbind: sysUpTime 393885975 varbind: lgpEventParmTableRef lgpPduRcpTable varbind: lgpEventParmTableRowRef lgpPduRcpEntryId.2.4.5 In the above example the power state changed for a Receptacle. The table containing the definition of the receptacle (lgpPduRcpTable) is given by the varbind (lgpEventParmTableRef) The specific receptacle is specified by the varbind (lgpEventParmTableRowRef). In this case the notification is for the 5th receptacle on the 4th receptacle branch on the 2nd PDU in the PDU cluster. If one wanted to retrieve the user assigned label for this receptacle the OID would be: lgpPduRcpEntryUsrLabel.2.4.5

RFC description

Liebert vendor-private MIB for power and cooling system notifications and alarm definitions.

Start monitoring Liebert (Vertiv) GlobalProducts UPS/PDU/precision-cooling equipment (trap OIDs) 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.

Download LIEBERT-GP-NOTIFICATIONS-MIB

What Is LIEBERT-GP-NOTIFICATIONS-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description