ThreeParMIB

File: ThreeParMIB.mib (10802 bytes)

Imported modules

SNMPv2-TC SNMPv2-CONF SNMPv2-SMI

Imported symbols

DisplayString TEXTUAL-CONVENTION AGENT-CAPABILITIES
enterprises MODULE-IDENTITY OBJECT-TYPE
NOTIFICATION-TYPE OBJECT-IDENTITY Integer32
Unsigned32

Defined Types

ThreeparLongDisplayString  
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.
TEXTUAL-CONVENTION    
  OCTET STRING  

AlertEntry  
SEQUENCE    
  index Integer32
  severity INTEGER
  timeOccurred DisplayString
  nodeID Unsigned32
  component DisplayString
  details ThreeparLongDisplayString
  id Unsigned32
  messageCode Unsigned32
  state INTEGER
  serialNumber DisplayString

Defined Values

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.
MODULE-IDENTITY    

inserv 1.3.6.1.4.1.12925.1
InServ product
Status: current Access: read-write
OBJECT-IDENTITY    

inservAgentCaps 1.3.6.1.4.1.12925.1.4
InServ agent profile
Status: current Access: read-write
OBJECT-IDENTITY    

alertTable 1.3.6.1.4.1.12925.1.7
Contains critical information in notifications sent to SNMP managers. This information is translated from alerts generated by the system.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    AlertEntry

alertEntry 1.3.6.1.4.1.12925.1.7.1
Row Description
Status: current Access: not-accessible
OBJECT-TYPE    
  AlertEntry  

index 1.3.6.1.4.1.12925.1.7.1.1
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
Status: current Access: read-only
OBJECT-TYPE    
  Integer32 1  

severity 1.3.6.1.4.1.12925.1.7.1.2
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.
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER fatal(0), critical(1), major(2), minor(3), degraded(4), info(5), debug(6)  

timeOccurred 1.3.6.1.4.1.12925.1.7.1.3
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.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

nodeID 1.3.6.1.4.1.12925.1.7.1.4
The node the alert was posted on. The node number starts from 0. The maximum number of node is 32.
Status: current Access: read-only
OBJECT-TYPE    
  Unsigned32 0..31  

component 1.3.6.1.4.1.12925.1.7.1.5
The component which the event applies to; for example, power supply, SCSI disk, BIOS, cage etc...
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

details 1.3.6.1.4.1.12925.1.7.1.6
Additional detailed description of the alert. The detail may include things like disk number, cage number the alert applies to.
Status: current Access: read-only
OBJECT-TYPE    
  ThreeparLongDisplayString Size(0..511)  

id 1.3.6.1.4.1.12925.1.7.1.7
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.
Status: current Access: read-only
OBJECT-TYPE    
  Unsigned32 1..4294967295  

messageCode 1.3.6.1.4.1.12925.1.7.1.8
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.
Status: current Access: read-only
OBJECT-TYPE    
  Unsigned32 65537..4294967295  

state 1.3.6.1.4.1.12925.1.7.1.9
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.
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER undefined(0), new(1), acknowledged(2), fixed(3), removed(4), autofixed(5)  

serialNumber 1.3.6.1.4.1.12925.1.7.1.10
The serial-number of the HP 3PAR InServ system
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

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.
Status: current Access: read-only
NOTIFICATION-TYPE    

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.
Status: current Access: read-only
AGENT-CAPABILITIES