LEFTHAND-NETWORKS-NUS-COMMON-NOTIFICATION-MIB

All MIBs › LEFTHAND-NETWORKS-NUS-COMMON-NOTIFICATION-MIB

Organization: LeftHand Networks, Inc.

Last Updated: 2002-06-25

Category: Alarm and Event Management, Domain: Storage

Description: LeftHand Networks MIB defining SNMP notifications for hardware and software events on LeftHand NUS storage appliances.

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 LEFTHAND-NETWORKS-NUS-COMMON-NOTIFICATION-MIB?

This LeftHand Networks MIB defines the SNMP notifications (traps) used across NUS (Network Unified Storage) devices for signaling hardware and software events. Rather than exposing polled counters, it defines a notification message table that logs discrete events -- such as fault conditions, state transitions, or administrative actions -- each with an index, message text, and timestamp. It is directly used for fault and event monitoring on LeftHand storage appliances, allowing an NMS to receive and log hardware/software alerts (e.g., disk faults, power issues, or software errors) as they occur rather than through periodic polling. It works alongside the base LEFTHAND-NETWORKS-NSM-MIB and status MIB as part of the broader LeftHand/NUS MIB family. It is deployed on HP/LeftHand NUS storage appliances in SAN environments requiring trap-based event monitoring, for which the LEFTHAND-NETWORKS-NUS-COMMON-NOTIFICATION-MIB MIB defines the notification objects used.

IPNetwork Monitor allows you to monitor SNMP objects defined in LEFTHAND-NETWORKS-NUS-COMMON-NOTIFICATION-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

HP/LeftHand Networks NUS storage appliances

Monitoring Examples

An NMS would subscribe to traps generated against notificationMessageTable, then poll notificationMessageEntry fields like notificationMessage and notificationTime to build an event log for a given NUS storage node, using notificationIndex for ordering. A spike in notificationMessageCount over a short period would indicate a burst of hardware or software events worth investigating, such as repeated disk or RAID controller faults. This table effectively serves as an in-band event/alert history for the storage appliance.

What Can Be Monitored

notification/event message log
event timestamps
event count
fault and state-change notifications

Imported Objects

From LEFTHAND-NETWORKS-GLOBAL-REG

lhnModules

OBJECT-IDENTITY

From LEFTHAND-NETWORKS-NUS-COMMON-MIB

lhnNusCommonEvents	OBJECT-IDENTITY
lhnNusCommonGroups	OBJECT-IDENTITY
lhnNusCommonNotification	OBJECT-IDENTITY

From RFC-1212

OBJECT-TYPE

From SNMPv2-CONF

NOTIFICATION-GROUP

From SNMPv2-SMI

MODULE-IDENTITY
NOTIFICATION-TYPE

From SNMPv2-TC

DateAndTime

How to Use in IPNetwork Monitor

Example using notificationMessageCount OID:

Select a HP/LeftHand Networks storage appliance as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type notificationMessageCount into the Find box to locate it in the OID tree, then select it and click OK. It reports number of notification messages. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is an INTEGER-type OID, Value bounds is the most useful condition here — trigger an alert if the count changes from its expected baseline, since that would indicate the underlying set of items changed unexpectedly. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
lhnNusCommonNotificationModule	1.3.6.1.4.1.9804.1.1.15			Notification (Trap) items for NUS Devices
lhnNusCommonEventGroup	1.3.6.1.4.1.9804.3.1.1.1.1.2			Events defined for NUS devices
INT notificationMessageCountEx	1.3.6.1.4.1.9804.3.1.1.2.13.1	INTEGER	read-only	number of notification messages
notificationMessageTable	1.3.6.1.4.1.9804.3.1.1.2.13.2		not-accessible	A table of notification messages for the NUS. The number of entries is given by notificationMessageCount.
notificationMessageEntry	1.3.6.1.4.1.9804.3.1.1.2.13.2.1		not-accessible	A row of notification messages for the NUS.
INT notificationIndex	1.3.6.1.4.1.9804.3.1.1.2.13.2.1.1	INTEGER	read-only	notification message index
OCT notificationMessage	1.3.6.1.4.1.9804.3.1.1.2.13.2.1.2	OCTET STRING	read-only	notification message contents
DAT notificationTime	1.3.6.1.4.1.9804.3.1.1.2.13.2.1.3	DateAndTime	read-only	time notification occurred
NTF userNotification	1.3.6.1.4.1.9804.3.1.1.3.1			A system variable being monitored reached a threshold. The user chose to be notified of this condition via SNMP. A table of messages exists which stores all the notifications issued. This trap will carry the OID referring to the corresponding message stored in this table.

RFC description

LeftHand Networks (acquired by HP) common notification MIB for SAN storage system alerts and traps.

Start monitoring HP/LeftHand Networks storage appliances 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 LEFTHAND-NETWORKS-NUS-COMMON-NOTIFICATION-MIB