NetDiscover SNMP MIB/OID/TRAP/NOTIFICATION Database Index (no description, no download) URL: /MIBs/ Parent Directory [DIR] [All] Draft/ [DIR] Ent/ [DIR] Standards.
SNMP Primer Before we dive into configuring SNMP for 3PAR lets do a quick review of what SNMP is, SNMP stands for Simple Network Management Protocol. SNMP is used for configuring and collecting information from network devices including storage. The focus of this post is using SNMP as a monitoring tool for alerts.
An SNMP infrastructure is based around two components, the manager which acts as the collection point for all alerts and agents which are software on the end points that report back to the manager. What information can be monitored is defined by a MIB (Management Information Base). The MIB’s are a collection of managed objects identified by Object Identifiers (OID). These OID list the characteristics of the devices that can be managed. 3PAR and SNMP 3PAR has its own SNMP agent built into the device.
The 3PAR MIB is contained within the 3PAR CLI download. The HP 3PAR SNMP agent supports SNMPv3, SNMPv2c, SMI-v2 standards. You will notice SMI-v2 listed as a compatible standard with 3PAR, SMI stands for Storage Management Initiative. SMI was launched by SNIA to provide a common framework all storage vendors could adhere to, allowing common management tools across all vendors. Configuring SNMP for 3PAR You will configure SNMP for 3PAR using the CLI, it’s dead easy and I will provide all the steps you will need below.
1 Once you are connected to the 3PAR CLI you will add the SNMP Manager. Remember the manager is the device that is the trap destination i.e. The SNMP server addsnmpmgr The above command should be sufficient for most situations, but if your manager server requires a password or other config different from the default you can use the following options:.p – Specifies the port number where the manager receives traps. The default port 162.pw – Specifies the manager’s access password, if the manager has one.r – Specifies the number of times the system will attempt to resend the trap if the manager is not available.
The default is 2.t – Specifies the number of seconds to wait between retries. The default is 200 2 When using the addsnmpmgr command the community name will be set to public, if you need to set a custom community name or change the access permissions use the following command: setsnmppw –r (-r = read-only, -w = write-only and -rw = read-write) 3 You can view your 3PAR SNMP configuration with the following command showsnmpmgr 4 Finally you can send a test trap to make sure everything is working OK checksnmp Enabling SMI If your monitoring solution requires SMI you will need to enable it on the 3PAR. Open the 3PAR Command Line Interface (CLI) and connect to the 3PAR system: 1 Enable the SMI-S provider startcim 2 Check status of SMI-S Provider showcim 3 Restarting the SMI-S Provider stopcim –f –x To stay in touch with more 3PAR news and tips connect with me on. Hey Joe You can in fact get lots of SNMP values with a SNMP walk on the system. There are around 140 different values as i remember correctly. But there is no documentation of what they mean.
I think this is from back when 3par was on its own. After they have been bought, HP has no interest in supporting something free like SNMP. They want you to buy their expensive OpenView solution. So i tried to find out what those values mean. From my experience, you can only get standard linux SNMP information out of the 3par box. Things like uptime, CPU load, Ram usage, NIC utilization and so on We were interested in the capacity of virtual volumes and other storage related values. We had to bury that dream.
![Mib Mib](/uploads/1/2/5/6/125671788/363404594.png)
Regards, John.
ThreeParMIB File: (10471 bytes) Imported modules Imported symbols Defined Types TEXTUAL-CONVENTION current STRING SEQUENCE index severity INTEGER timeOccurred nodeID component details id messageCode state INTEGER serialNumber Defined Values 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 1.3.6.1.4.1.12925.1 InServ product OBJECT-IDENTITY 1.3.6.1.4.1.12925.1.4 InServ agent profile OBJECT-IDENTITY 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. OBJECT-TYPE SEQUENCE OF 1.3.6.1.4.1.12925.1.7.1 Row Description OBJECT-TYPE 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 OBJECT-TYPE 1 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.
OBJECT-TYPE INTEGER fatal(0), critical(1), major(2), minor(3), degraded(4), info(5), debug(6) 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. OBJECT-TYPE 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. OBJECT-TYPE 0.31 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.
OBJECT-TYPE 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. OBJECT-TYPE Size(0.511) 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. OBJECT-TYPE 1. 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.