

-t – Specifies the number of seconds to wait between retries.-r – Specifies the number of times the system will attempt to resend the trap if the manager is not available.


-pw – Specifies the manager’s access password, if the manager has one.-p – Specifies the port number where the manager receives traps.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: Remember the manager is the device that is the trap destination i.e. You will configure SNMP for 3PAR using the CLI, it’s dead easy and I will provide all the steps you will need below.ġ Once you are connected to the 3PAR CLI you will add the SNMP Manager. SMI was launched by SNIA to provide a common framework all storage vendors could adhere to, allowing common management tools across all vendors. You will notice SMI-v2 listed as a compatible standard with 3PAR, SMI stands for Storage Management Initiative. The HP 3PAR SNMP agent supports SNMPv3, SNMPv2c, SMI-v2 standards. The 3PAR MIB is contained within the 3PAR CLI download. 3PAR and SNMPģPAR has its own SNMP agent built into the device. These OID list the characteristics of the devices that can be managed. The MIB’s are a collection of managed objects identified by Object Identifiers (OID). What information can be monitored is defined by a MIB (Management Information Base). The focus of this post is using SNMP as a monitoring tool for alerts.Īn 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.

SNMP is used for configuring and collecting information from network devices including storage. Before we dive into configuring SNMP for 3PAR lets do a quick review of what SNMP is, SNMP stands for Simple Network Management Protocol.
