ThreeParMIB

All MIBs › ThreeParMIB

Organization: Organization : HP 3PAR

Last Updated: 2013-03-12

Category: Hardware and Chassis Management, Storage

Description: Manages HP 3PAR storage system components, volumes, performance, and fault status.

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 ThreeParMIB?

ThreeParMIB is HP's vendor-specific MIB for its 3PAR enterprise storage arrays, giving management software SNMP access to the storage controller's internal state. It generally exposes data on system inventory, virtual/physical volumes, ports, disks, and overall array health and performance, alongside fault and event notifications. As a hardware/software status MIB it is used to monitor controller node health, disk and physical-drive status, power supply and fan status, and volume/space utilization, letting storage teams catch a failed node, degraded drive, or capacity threshold before it causes an outage. It is a self-contained enterprise MIB with no stated dependency on other MIBs beyond standard SNMPv2 SMI conventions. It is deployed in enterprise/data-center environments where HP (now HPE) 3PAR StoreServ arrays are monitored centrally alongside other SAN infrastructure. Engineers can download the ThreeParMIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in ThreeParMIB. 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/HPE 3PAR StoreServ storage arrays

Monitoring Examples

No object/table names were provided in the source data for this module, so a specific object-level monitoring walkthrough cannot be given without inventing names; in practice this MIB is understood to expose 3PAR system, volume, and hardware-component status tables analogous to those in HP's published 3PAR MIB documentation. An admin would typically poll such tables for controller node state, physical disk status, and volume space usage to catch a failing disk or a node going offline. Confirming exact OIDs would require inspecting the actual MIB source rather than the sample objects given here.

What Can Be Monitored

storage controller/node health
physical disk status
volume/space utilization
power supply and fan status
fault/event notifications

Imported Objects

From SNMPv2-CONF

AGENT-CAPABILITIES

From SNMPv2-SMI

Integer32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-IDENTITY
OBJECT-TYPE
Unsigned32
enterprises

From SNMPv2-TC

DisplayString
TEXTUAL-CONVENTION

OIDs

OID symbolic	OID numeric	Type	Access	Description
threepar	1.3.6.1.4.1.12925			This file specifies management information interface for all HP 3PAR's products. This information is normally used by any management software that utilizes SNMP as management standard. The SNMP agent inside the device provides the specified information.
inserv	1.3.6.1.4.1.12925.1			InServ product
inservAgentCaps	1.3.6.1.4.1.12925.1.4			InServ agent profile
inservAgentCapability	1.3.6.1.4.1.12925.1.4.1			HP 3PAR agent capability. Please note that the HP 3PAR agent supports snmpObsoleteGroup in SNMPv2-MIB instead of snmpGroup.
alertTable	1.3.6.1.4.1.12925.1.7		not-accessible	Contains critical information in notifications sent to SNMP managers. This information is translated from alerts generated by the system.
alertEntry	1.3.6.1.4.1.12925.1.7.1		not-accessible	Row Description
I32 index	1.3.6.1.4.1.12925.1.7.1.1	Integer32	read-only	Index to access entries in alert table. However, the table is empty most of the time because the entry is deleted after sending the trap
INT severity	1.3.6.1.4.1.12925.1.7.1.2	INTEGER	read-only	Severity of the alert. The enumeration is borrowed from Common Information Model (CIM): 0 - fatal: indicates an error occurred, but it's too late to take any actions; 1 - critical: an action is needed immediately and scope of the error is broad; 2 - major: an action is needed, the situation is serious; 3 - minor: an action is needed, but the situation is not serious; 4 - degraded/warning: the user decides whether to take an action; 5 - informational: indicates state change or status change, but it's not an error; 6 - debug: information that are logged for later analysis.
STR timeOccurred	1.3.6.1.4.1.12925.1.7.1.3	DisplayString	read-only	The local time and date when the alert occurred. The format is 'DDD mmm dd hh:mm:ss ZZZ yyyy'. Where: DDD= day of the week (Sun, Mon, ,,,), mmm= month (Jan, Feb, Mar ...), dd= date, hh: hour, mm: minute, ss= second, ZZZ: time zone, yyyy: year.
U32 nodeID	1.3.6.1.4.1.12925.1.7.1.4	Unsigned32	read-only	The node the alert was posted on. The node number starts from 0. The maximum number of node is 32.
STR component	1.3.6.1.4.1.12925.1.7.1.5	DisplayString	read-only	The component which the event applies to; for example, power supply, SCSI disk, BIOS, cage etc...
STR details	1.3.6.1.4.1.12925.1.7.1.6	ThreeparLongDisplayString	read-only	Additional detailed description of the alert. The detail may include things like disk number, cage number the alert applies to.
U32 id	1.3.6.1.4.1.12925.1.7.1.7	Unsigned32	read-only	Unique ID that identifies the instance of an alert. This is a unique number that is generated each time an alert is generated by the system.
U32 messageCode	1.3.6.1.4.1.12925.1.7.1.8	Unsigned32	read-only	Message code is assigned to a particular event type, and is encoded as a 32-bit number in the following way: The MSB 8 bits are reserved. The next 8 bits represent a particular subsystem or component. The LSB 16 bits are the keycode id within the subsystem. For example, Remote Copy Target Down event has a subsystem ID of 37 (remote copy subsystem), and a keycode ID of 1, thus the message code for this event = ((37 << 16) \| 1) = 0x250001 = 2424833. This is shown as 'Message Code' in the CLI 'showalert' display, and also shows up in the Alerts Details Pane in the GUI.
INT state	1.3.6.1.4.1.12925.1.7.1.9	INTEGER	read-only	This provides information about the state of the alert. new - new alert generated by the system acknowledged - an administrator has acknowledged the alert but may or may not have fixed it, depending on whether remedial action is necessary fixed - remedial action has been taken to fix the alert condition removed - the alert has been removed autofixed - the system has taken action to automatically resolve the alert condition.
STR serialNumber	1.3.6.1.4.1.12925.1.7.1.10	DisplayString	read-only	The serial-number of the HP 3PAR InServ system
NTF alertNotify	1.3.6.1.4.1.12925.1.8			Alert notification contains details about an event that may affect system operations and performance. The details include all columns defined in alertTable.

RFC description

Monitors HP 3PAR storage systems including alerts, status, and inventory management for SAN environments.

Start monitoring HP/HPE 3PAR StoreServ storage arrays (controller-node/disk/power-supply health 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.

Download ThreeParMIB

What Is ThreeParMIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description