MIBs Depot

ThreeParMIB

Registered at
1.3.6.1.4.1.12925
Last updated
2013-03-12 11:22
Organization
Organization : HP 3PAR
Revisions
2013-03-12 11:22, 2012-08-02 15:22, 2010-10-04 14:45, 2007-10-05 15:00, 2004-12-13 17:00, 2004-12-13 16:40, 2004-06-14 15:45, 2002-04-16 13:27
Namespace
hp
Source file
ThreeParMIB
Digest
sha256:c1387f33e4b5c076ff077a43438e1c4e0551d2a10279d6a75bee101a840878ea

Description

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.

Contact

Contact-info www.hp.com/go/3PAR

Imports

FromSymbols
SNMPv2-CONFAGENT-CAPABILITIES, MODULE-COMPLIANCE, NOTIFICATION-GROUP
SNMPv2-SMIInteger32, MODULE-IDENTITY, NOTIFICATION-TYPE, OBJECT-IDENTITY, OBJECT-TYPE, Unsigned32, enterprises, iso
SNMPv2-TCDisplayString, TEXTUAL-CONVENTION

Imported by

Nothing in this corpus imports this module.

Load order

Every file a consumer needs in order to load this module, dependencies first.

SNMPv2-CONF
SNMPv2-SMI
SNMPv2-TC
ThreeParMIB

Textual conventions

NameOIDSyntaxAccessStatus
ThreeparLongDisplayString
TEXTUAL-CONVENTION
Use this textual convention for display string that can be longer than 255 characters, since DisplayString is defined in SNMPv2-TC as having a maximum size of only 255. A size range will have to be specified when using this convention.
current

Objects

NameOIDSyntaxAccessStatus
inserv
OBJECT-IDENTITY
InServ product
1.3.6.1.4.1.12925.1current
inservAgentCaps
OBJECT-IDENTITY
InServ agent profile
1.3.6.1.4.1.12925.1.4current
alertTable
OBJECT-TYPE
Contains critical information in notifications sent to SNMP managers. This information is translated from alerts generated by the system.
1.3.6.1.4.1.12925.1.7not-accessiblecurrent
alertEntry
OBJECT-TYPE
Row Description
1.3.6.1.4.1.12925.1.7.1not-accessiblecurrent
index
OBJECT-TYPE
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
1.3.6.1.4.1.12925.1.7.1.1Integer32 (1)read-onlycurrent
severity
OBJECT-TYPE
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.
1.3.6.1.4.1.12925.1.7.1.2INTEGER {fatal(0), critical(1), major(2), minor(3), degraded(4), info(5), debug(6)}read-onlycurrent
timeOccurred
OBJECT-TYPE
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.
1.3.6.1.4.1.12925.1.7.1.3DisplayStringread-onlycurrent
nodeID
OBJECT-TYPE
The node the alert was posted on. The node number starts from 0. The maximum number of node is 32.
1.3.6.1.4.1.12925.1.7.1.4Unsigned32 (0..31)read-onlycurrent
component
OBJECT-TYPE
The component which the event applies to; for example, power supply, SCSI disk, BIOS, cage etc...
1.3.6.1.4.1.12925.1.7.1.5DisplayStringread-onlycurrent
details
OBJECT-TYPE
Additional detailed description of the alert. The detail may include things like disk number, cage number the alert applies to.
1.3.6.1.4.1.12925.1.7.1.6ThreeparLongDisplayString (SIZE(0..511))read-onlycurrent
id
OBJECT-TYPE
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.
1.3.6.1.4.1.12925.1.7.1.7Unsigned32 (1..4294967295)read-onlycurrent
messageCode
OBJECT-TYPE
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.
1.3.6.1.4.1.12925.1.7.1.8Unsigned32 (65537..4294967295)read-onlycurrent
state
OBJECT-TYPE
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.
1.3.6.1.4.1.12925.1.7.1.9INTEGER {undefined(0), new(1), acknowledged(2), fixed(3), removed(4), autofixed(5)}read-onlycurrent
serialNumber
OBJECT-TYPE
The serial-number of the HP 3PAR InServ system
1.3.6.1.4.1.12925.1.7.1.10DisplayStringread-onlycurrent

Notifications

NameOIDStatus
alertNotify
NOTIFICATION-TYPE
Alert notification contains details about an event that may affect system operations and performance. The details include all columns defined in alertTable.
1.3.6.1.4.1.12925.1.8current

Conformance

NameOIDStatus
inservAgentCapability
AGENT-CAPABILITIES
HP 3PAR agent capability. Please note that the HP 3PAR agent supports snmpObsoleteGroup in SNMPv2-MIB instead of snmpGroup.
1.3.6.1.4.1.12925.1.4.1current