Nimble storage and VMware VCSA sensors

Hi there,

Currently there are no plans to implement Nimble Storage Sensors. You can however try to monitor the device via SNMP and their corresponding MIBs:
https://helpdesk.paessler.com/en/support/solutions/articles/76000041868-how-do-snmp-mibs-and-oids-work
https://https://helpdesk.paessler.com/en/support/solutions/articles/76000041872
https://helpdesk.paessler.com/en/support/solutions/articles/76000041874-how-can-i-import-my-mib-files-into-prtg


About VCSA, you can monitor them already via the "VMWare Virtual Machine Sensor (SOAP)" or the "VMWare Datastore Sensor (SOAP)", the other SOAP sensors have to be added to the ESXi Servers instead of the VCenter:
https://www.paessler.com/manuals/prtg/vmware_host_performance_soap_sensor
https://www.paessler.com/manuals/prtg/vmware_host_hardware_status_soap_sensor


Best regards.

nice one, the SOAP sensors work fine with VCSA 6.5, thank you!

Hi Support....can you urgently develop a Nimble Sensor please as there still doesn't seem to be one. Thank you. Nimbles are very common now.

Hi Mike,

As of now, there are not as many customers requesting this type of sensor: Roundabout 30 since 2016. We'll keep an eye on the necessity for those sensors. If demand rises, we'll take a look.

Kind regards,
Stephan Linke, Tech Support

Hi there, as others have requested it would be great to get Nimble sensors in place.

Hello, we vote also for a nimble sensor.

I'd also like to voice support for a Nimble sensor. It's our main storage and not having a sensor for it is a bummer.

Hello Stephan, I tried the solution and it looks good. Best regards

Nice - does it monitor all important metrics or are you missing something you'd consider important?

Kind regards,
Stephan Linke, Tech Support Team

+1 vote for PRTG native Nimble sensors. Right now i'm monitoring things via SNMP and it's eating up a bunch of SNMP sensors because each individual OID is a single sensor rather than grouped into channels on one sensor.

I will look at the link above and try it, but i would prefer a Paessler supported option.

I was really hopeful about this, but I can't seem to get this to work. I copied the files to their folders in PRTG, rebooted the server and the Nimble device template appears in the auto-discovery list, but nothing is found. I also don't see the sensors if I try to add them manually.

Any ideas?

Hello lonewaffle,

Thank you very much for your reply.

Did you make sure to enable and set-up SNMP properly? What's the result when adding a SNMP System Uptime sensor to the Nimble device within PRTG. Do you receive valid results with this sensor?

Thank you very much in advance.
Sebastian

Sorry, I must've been half asleep that day. I realized after I had submitted my last post that I had forgotten to configure SNMP on the Nimbles themselves. Once I did that, it all started working great.

Thanks!

;)

I too would like to see an integrated sensor. I ran auto discovery using the Nimble template, but it is not working as expected. It is displaying this message: No Such Name (SNMP error # 2) Sensor Vol: [[tableoid].1.3.1]

So far the only sensors I have had sucess with are very basic, ping, http and uptime. Should I expect to see the Nimble sensor when I try to add a sensor ??

Hello Joe,

Thank you very much for your reply.

No, the Nimble template is a Device Template which adds its sensors automatically when running an template based Auto-Discovery on the targeted device.
Please see the corresponding manual article on how and where to save the device templates.

Best regards,
Sebastian

+1 for native nimble sensors. We have 2x SF300

Hi there,

Have you tried the above device template for Nimble Storages?
https://gitlab.com/PRTG/Device-Templates/Nimble-Storage/

Best regards.

I'm going to add my vote for a request for Nimble sensors. I do have the Nimble storage sensors installed, but I'm missing quite a bit of information that I would consider essential - monitoring the overall storage capacity (it shows the capacity for each individual volume, but not for the whole array) nor does it indicate whether there are any dead disks in the array.

Just installed the Nimble storage template - it works! Couple questions:

1) if the volumes on the nimble changes do we just re-run auto-discover? Currently I have it set for daily rediscover.

2) Is there a lead sensor, like a ping or anything? If there's a network issue between PRTG and the Nimble am I going to get 20 alerts, one for each volume?

3) Shows a list of volumes, any way to show the name of the volumes? Vol: [[tableoid].1.3.11] doesn't mean much to me.

Hi there,

1.) New Volumes will be discovered as well as the old ones as long as the table is not changing.

2.) As far as I can see the template only adds the Volumes, otherwise you would see a Ping Sensor. However when you run an auto-discovery, just select both the "Ping Only" and the Nimble template.

3.) That should work, as long as the table holds data on the device under the OID "1.3.6.1.4.1.37447.1.2.1.3". You can check that with our SNMP Tester.

Best regards.

Found this article while searching for native PRTG support for monitoring our new HPE Nimble storage. Has anything happened since 19-09-2018 ? Can't find anything else in the knowledge base (not even a feature request) and the download of the template on Gitlab isn't working anymore and hasn't been maintained in 3 years, so I'm kind of stuck here.

Hi there,

According to our roadmap this is not planned yet: https://www.paessler.com/prtg/roadmap