HP 3par SAN Storage

Hello,

thank you very much for your KB-Post. I'm very much afraid there a no native sensors for the 3par storages. You could try the new SSH SAN Sensors.
Otherwise, please check if HP offers any MIB-Files that you can import with our MIB-Importer to monitor the target then with SNMP Library Sensors.

best regards.

Hello! I was able to import 3Par MIB file and add it to library, however, when I try to create a sensor based on .oidlib library file I get the following message:

Sorry, the scan for available monitoring items has failed! No available interfaces on this device (code: PE049)

I got a second mib file, confirmed that it was the correct one, and got the same error. Any idea why?

Can't promise anything, but I am working on something since we've purchased PRTG and also own 3PAR arrays.

Hi,
Please download the SNMP Tester and load the oidlib file there. Now scan the target device. What results do you get?

neuralfraud: Hello, I would also be very interested in this, as I have the same issue as [tsalgado] has.

I am also interested in this topic. Are there any conclusions in the meantime because we are gonna using HP PAR 8200 ?

@ Pässler Support : Are there any Sensors planned for 3PAR Storage, because in Gartner Magic Quadrant HP 3PAR is a Leader ?

Thanks for any information.

Hi,
Currently there are no dedicated sensors for HP 3PAR planned. However, your voice has been counted.
Best regards

I am interested in 3PAR sensors as well

I would also like this :) In the mean time does the SSH San Sensor work?

Hello,

Sure, you can try our SSH SAN sensors: https://www.paessler.com/manuals/prtg/available_sensor_types#linux

Best regards

Hello. long time prtg user, I registered just to post this. Please add my vote for HP 3PAR support. thanks

Hello, Please add my vote for HP 3PAR support too!! Best regards Wolfgang

Me2, how many voices you need since the topic is already 3.5 years old?

We appreciate your voices. Thank you for the feedback it is really important to us. Let me explain why such sensors haven't been implemented, why the voices weren't many enough so far. We have to balance the number of requests for a feature always against the total number of installations (200,000 of our software), and of course also necessary effort for development & testing. And then you naturally come to the conclusion that you need a lot more requests. I hope this is understandable.

We have recently developed a sensor pack for 3PAR devices. It is currently being sold and deployed world wide. You can evaluate it for 30 days for free. See the link below: http://www.nms-guru.com/PRTG-Sensors-for-HPE-3Par.html

Kindest regards, Yigal

@Torsten Lindner

Funny, it looks like for a third party there were enough votes around to create a sensor and sell it for $500. Maybe it's because PRTG wasn't doing anything in the past 4 years and 3PAR is just the market leader in this segment.

https://news.hpe.com/gartner-names-hpe-as-a-leader-for-general-purpose-disk-arrays

We aren't disputing anybodies market share or relevance. Nor do we take feature requests for granted. There are 17 voices raised in this thread, 5 of which are responses from us ourselves. That leaves 12 user voices over the time of about 4 years. There are probably a few other KB-Topics to this, we aren't ignoring that. And then we'll put it into perspective of 200,000 installations of our software.
The relation then becomes much much smaller. Which means, only a few users would benefit from the work there. Again, this is not meant to take away that 3Par sensors would be useful for you. It's a question of overlapping market share too. Those storages tend to be used in large networks, whereas PRTG has its sweetspot rather in medium networks. That probably explains the discrepancy.
A lot of other sensor types have been implemented, reworked and improved in those 4 years (so it isn't really the case of haven't done anything). And a lot more users benefited from that. It is always about compromises, because nobody has an infinite amount of developers at their hands.

we also have some 3par systems running and need a 3par sensor for monitor them in PRTG. So add my vote for an 3par sensor.

Please add my vote for Some HPE 3PAR Sensores, too!

I'll also add my voice for a 3par Sensor.

I'm going to add my vote for 3PAR and also an editorial based on what I've read here.

Not every 3PAR admin is going to go to the trouble of creating a Paessler account, activating it, and then adding their vote when they are EVALUATING the efficacy of your solution. If you are basing development priority on the feedback in this forum, that's short-sighted. I like your product, I like that you engage with your audience, but have you considered that support for 3PAR would be a selling point? As stated, it is a market leader. It's the Mercedes C-class of storage, so for you to not support it seems very misguided in my opinion. We're evaluating PRTG but if it can't support our environment, we'll have to look elsewhere.

And since I can't upvote until I post at least 15 times, I want to thank Yigal for the third party add-on. If it works as advertised, I'll be happy to spend our company's money with them to get that functionality - provided PRTG is approved after I complete my assessment. If we can afford the 3PAR, we can pay for the sensor. Perhaps you should offer it as an add-on and enhance your revenue stream.

Another request for HPE StoreServ/3PAR sensors. There is a WSAPI that you can call and grab metrics for. There is also a Service Processor that grabs telemetry from the array system and sends it to HPE that might be of service for this process as well.

StoreServ/3PAR is a pretty prevalent system with integrations built into pretty major applications like Veeam. It would be fantastic if we could get a supported sensor solution.