ThreeParMIB: View SNMP OID List / Download MIB

VENDOR: 3PAR DATA


 Home MIB: ThreeParMIB
Download as:   
SNMPv2-CONF, SNMPv2-SMI, SNMPv2-TC

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 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 no-access
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 no-access
Row Description
                         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
                         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. Enumeration: 'info': 5, 'major': 2, 'critical': 1, 'debug': 6, 'degraded': 4, 'fatal': 0, 'minor': 3.
                         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.
                         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.
                         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...
                         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.
                         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.
                         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.
                         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. Enumeration: 'fixed': 3, 'undefined': 0, 'autofixed': 5, 'acknowledged': 2, 'new': 1, 'removed': 4.
                         serialNumber 1.3.6.1.4.1.12925.1.7.1.10 displaystring read-only
The serial-number of the HP 3PAR InServ system
                 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.