H,
i want check the 3PAR with cli, i found this script for nagios. It is possibile to use for prtg?
https://github.com/kishikawa/3par/blob/master/check_3par here is the script.
Thx
SNMP Settings. The Onboard Administrator supports SNMP Version 1 and several groups from the standard MIB-II MIB. Additional information about the enclosure infrastructure is available in the HP Rack Information MIB. BMC Performance Manager Express for HP 3PAR. BPM Express for HP 3PAR. BMC Performance Manager Express for HP EVA. Connect to the HP Virtual Connect Manager; In the left tree-view. Select MIB-2 Standard SNMP Agent – Network Interfaces and click Next.
How about using the MIB file from the 3PAR admin tools CD.
Convert the MIB to a OIDLIB using Paesslers MIB converter. In PRTG, you will add an SNMP Library sensor and use the new OIDLIB file.
For more details on converting MIB files to OIDLIB files please see http://kb.paessler.com/en/topic/733-how-can-i-import-my-mib-files-into-prtg
No function, because 3PAR use a trap, and the beta sensor no function. The powershell script is the unique possibility to check the status.
Dear all
Is there in meantime any option to monitor a HP 3PAR 8200 System with SNMP ? Does somebody have some experience with this issues. Does it work with and MIB Files and converting to OIDLIB Files ?
@ PRTG Support : Are any HP 3PAR Sensors planned ?
Thanks for any help
Currently, there are no plans for 3PAR storage servers. The only way to go here would be to test the SSH SAN sensors or the trap receiver sensors. The former one might not work as its not tested for comptability with the 3PARs.
I am also interested in 3PAR sensors
Unfortunately, as stated in the 3par MIB:
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 |
This means that regular SNMP GET monitoring won't work, importing the MIB won't help. You may want to try the TRAPS approach:
The other alternative would be to create a custom script which interacts with the 3par in a different way (HTTP API, SSH, etc)
Best Regards,
Luciano Lingnau [Paessler Support]
We have recently developed a pack of 6 sensors for HPE 3Par.
Have a look at our website
Have a look at our website
Best regards, Yigal, KMC Technologies
I am also interested in 3PAR sensors. We have some 3par Systems and we need to monitor them.
I am also interested in 3 par sensors.
Please log in or register to enter your reply.
Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.
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
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 <port_number> – Specifies the port number where the manager receives traps. The default port 162
- -pw <password> – Specifies the manager’s access password, if the manager has one
- -r <number> – Specifies the number of times the system will attempt to resend the trap if the manager is not available. The default is 2
- -t <seconds> – 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:
3 You can view your 3PAR SNMP configuration with the following command
4 Finally you can send a test trap to make sure everything is working OK
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 LinkedIn and Twitter.