What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

Dell Compellent Monitoring

Votes:

0

Can anyone help me. I'm trying to monitor a Dell Compellent.

I have downloaded the mib, created the oid and also run a snmp walk to the device. I can't get anything near meaning full from the device.

Which oid's do I use? Do I need a seperate sensore per oid?

I imported the whole of the oid file into PRTG, which slows down the web interface. This allowed me to finish the process but all I got back was response times to volume names etc.

compellent dell devicetemplate paetemplate prtg15 snmp-custom-sensor

Created on Jan 10, 2018 5:26:02 PM

Last change on Nov 30, 2018 2:27:40 PM by  Luciano Lingnau [Paessler]



Best Answer

Accepted Answer

Votes:

0

This article applies to PRTG Network Monitor 16.3.25 or later

Monitoring Dell Compellent and other Dell Storage Systems

While we have some built-in sensors that may work with Dell's Storages, you might be looking for additional metrics/sensors.

We've put together a couple of lookups and a device template, which can be used to automate the deployment of these sensors using auto-discovery.

Adding Custom Sensors using the Auto-Discovery + Template

You can use the device template that we provide below to automatically create custom sensors with the PRTG auto-discovery.

The metrics that are available can vary. The sensors can monitor the following if the data is available:

  • Controller Cache Card
    • Status
    • Battery Status
  • Controller
    • Status
  • Controller Temperature
    • Status
    • Current Reading
  • Logical Disk (Volume)
    • Status
  • Physical Disk
    • Status
    • Healthy (Yes/No)
  • Enclosure Status
    • Status
  • Enclosure Temperature
    • Status
    • Current Reading
  • Global Status
    • Status
  • Storage Center Status
    • Status
    • Ports Balanced
  • Storage Folder
    • Free Space
    • Total Space
    • Used Space

The device template creates the available and compatible sensors based on the data at hand. The sensors implement default alerts whenever possible, but you can still fine-tune most channels by defining additional limits in the sensor channels settings or modifying the lookups included with the template.

Requirements

  • PRTG Network Monitor 16.3.25 or later
  • Because the device template relies on the auto-discovery process, the device you want to monitor needs to be reachable via PING.
  • SNMP must be enabled on the device and the device must support the DELL-STORAGE-SC-MIB from where the data comes from.
  • The device template is expected to be compatible with the following devices:
    • Dell Compellent SC4020 with Dell Storage Center OS (SCOS) version 7.2.31
    • Dell Compellent Series 40
    • Dell Storage SC5020
    • Dell Storage SC5020F
    • Dell Storage SC7020
    • Dell Storage SC7020F
    • Dell Storage SC8000
    • Dell Storage SC9000
    • Dell Storage SCv2000
    • Dell Storage SCv2020
    • Dell Storage SCv2080
    • Dell Storage SCv3000
    • Dell Storage SCv3020

Known Issues and Limitations

  • Depending on the amount of Logical Disks configured on your Storage you may see a very large number of sensors (one per Logical Disk). It is recommended to increase the scanning interval to at least 5 minutes in this case to avoid excessive SNMP queries.
  • The temperature sensors may cause issues in some Firmware/Software versions. Feel free to follow-up if you encounter unexpected errors so that we may investigate.
  • You may get a "Storage Folder: Unassigned" sensor throwing errors by default: "0 GByte (Free Space) is below the error limit of 10 GByte in Free Space" - This sensor can be paused/deleted.
  • Some of the sensors (where a number like (1) or (1.1) is present in the name) are index-based, this means that if the device reboots or is updated the indexes *may* change. If this happens the sensors may become unreliable. If device is updated or rebooted it's advisable to delete these sensors and re-run the auto-discovery afterwards to be safe. The sensors will then be re-created and use the correct/appropriate index.
  • PRTG shows some of the alerts as reported by the monitored device via SNMP using Lookups. If the status is not reported correctly via SNMP, PRTG cannot detect any issues. For additional alerts, please set up limits for additional channels.
  • This device template was created based on data collected from other customers, so we cannot guarantee that the sensors described above will work on your systems or that the default thresholds are optimal for your use case. Use these components at your own risk. Please test and validate the sensors in your environment after deploying them.

Deployment and Usage

  1. Download the required zip archive containing the template's files here.
  2. Extract the archive to your PRTG program directory. By default, this is %ProgramFiles(x86)%\PRTG Network Monitor\.
  3. In PRTG, restart the core server: open Setup | System Administration | Administrative Tools | Restart Core Server and click Go!. This ensures that the MIB and lookups are loaded before you run the auto-discovery.
  4. Create a new device in PRTG with the address (IP or FQDN) of the device that you want to monitor and configure the SNMP credentials accordingly.
  5. Right-click your new device, select Run Auto Discovery with Template, browse for Dell Storage and select the Custom Dell Storage v0.x template from the list.
    Note: Using the auto-discovery with a dedicated device template is convenient here because it automates the creation of the custom sensors in an organized fashion.
  6. The sensors are deployed after a couple of seconds.
  7. You can adjust the channel limits or lookups to your needs later.

Result

The resulting sensors will look like this:

Sensor's Overview

Device Overview

Device Overview Right-click and select Open Image in New Tab for full-screen view

Sensor Overviews

Device Overview Right-click and select Open Image in New Tab for full-screen view

Device Overview Right-click and select Open Image in New Tab for full-screen view

No sensors deployed? :(
Please read ahead for troubleshooting.


Troubleshooting

Have any issues? Please don't hesitate to contact us by replying to this post or via a support ticket. Please make sure to mention this KB post. Please read ahead for troubleshooting steps that you can take in advance.

Auto-Discovery Log

Your auto-discovery log tells you a lot about what went wrong during the sensor's deployment. You can troubleshoot the auto-discovery by inspecting the auto-discovery log. If you get entries like the one below (NOT FOUND), it means that the required protocol or Object Identifier (OID) is not available and the sensors can't be deployed.

[...]
21.08.2017 09:17:17: Template Loaded; Device ID: 22848; Name: Custom Dell Storage v0.3
21.08.2017 09:17:18: Template Check; Device ID: 22848; Check ID: ping; FOUND
21.08.2017 09:17:19: Template Check; Device ID: 22848; Check ID: snmp; FOUND
21.08.2017 09:17:20: Template Check; Device ID: 22848; Check ID: snmp_scCacheTable; NOT FOUND
[...]

In the example above, some sensors were skipped because the device did not respond to the snmp_scCacheTable check. This means that this data is probably not available on your device. You can track this data by looking for the name after snmp_. In this case, a search for scCacheTable will tell you what OID from what MIB is missing.

You can also use this log to identify if the discovery was interrupted because the device did not respond to PING or to a basic SNMP check.

SNMP Data

If the discovery log is not sufficient, you can review the SNMP data directly from your device. To do so, download this file and use it with the Scan Script option in our SNMP Tester. This will allow you to review which SNMP queries succeed and which do not deliver any data. Please have this information at hand when contacting our support team.

Version History

VersionDescription
0.3First Public version/release
0.4Added Storage Folders (Space Free/Usage metrics)



Best Regards,
Luciano Lingnau [Paessler Support]

Created on Nov 30, 2018 1:01:42 PM by  Luciano Lingnau [Paessler]

Last change on Jul 26, 2021 11:41:43 AM by  Maike Guba [Paessler Support] (2,404) 2 1



10 Replies

Votes:

0

Hi there,

Please use our SNMP Tester (https://www.paessler.com/tools/snmptester), run it on the PRTG Host (or host of the Remote Probe), and perform a "Scan OIDlib" with your OIDlib against the target device. Please send us the result logfile from the Tester and the used OIDlib via mail by [email protected]. Please put "PAE979509" in the subject line.

Best regards.

Created on Jan 12, 2018 11:28:13 AM by  Dariusz Gorka [Paessler Support]



Votes:

0

Hi there, i've got the same Problem. The SNMP Tester ist running at the Moment. Can i send you the Mail to [email protected] to?

Best regards Alexander Moritz Siemens AG Fürth / Karlsruhe

Created on Feb 15, 2018 1:03:25 PM



Votes:

0

Hi Alexander,

Sure, please feel free to contact us with additional information under [email protected]. Please also include the following ticket-id in the subject:

PAE996683


Best regards.

Created on Feb 16, 2018 7:53:53 AM by  Dariusz Gorka [Paessler Support]



Votes:

0

Hi,

do you have a solution to monitor dell compellent like volume free size?

Created on May 7, 2018 1:01:52 PM



Votes:

0

Hello janine_sald,
thank you for your reply.

This might be possible. Please contact us via E-mail or via a support bundle in reference to case PAE1032632 and we can have a look at the available SNMP Data. This may allow us to put together a template for free size, but we'll need to compare the SNMP Data to the values on your devices's management interface to make sure that they are correct.

We'll provide instructions on how to obtain this data after you contact-us via Mail or Support Bundle.

Best Regards,
Luciano Lingnau [Paessler Support]

Created on May 7, 2018 1:39:27 PM by  Luciano Lingnau [Paessler]



Votes:

0

Any luck with this yet?

Created on May 22, 2018 10:30:04 PM



Votes:

0

Hello SageHalo,
thank you for your inquiry.

We haven't heard back from janine_sald, but feel free to follow-up via E-mail refering to case PAE1039693 and we'll be happy to assist you further.

Best Regards,
Luciano Lingnau [Paessler Support]

Created on May 23, 2018 10:42:03 AM by  Luciano Lingnau [Paessler]



Accepted Answer

Votes:

0

This article applies to PRTG Network Monitor 16.3.25 or later

Monitoring Dell Compellent and other Dell Storage Systems

While we have some built-in sensors that may work with Dell's Storages, you might be looking for additional metrics/sensors.

We've put together a couple of lookups and a device template, which can be used to automate the deployment of these sensors using auto-discovery.

Adding Custom Sensors using the Auto-Discovery + Template

You can use the device template that we provide below to automatically create custom sensors with the PRTG auto-discovery.

The metrics that are available can vary. The sensors can monitor the following if the data is available:

  • Controller Cache Card
    • Status
    • Battery Status
  • Controller
    • Status
  • Controller Temperature
    • Status
    • Current Reading
  • Logical Disk (Volume)
    • Status
  • Physical Disk
    • Status
    • Healthy (Yes/No)
  • Enclosure Status
    • Status
  • Enclosure Temperature
    • Status
    • Current Reading
  • Global Status
    • Status
  • Storage Center Status
    • Status
    • Ports Balanced
  • Storage Folder
    • Free Space
    • Total Space
    • Used Space

The device template creates the available and compatible sensors based on the data at hand. The sensors implement default alerts whenever possible, but you can still fine-tune most channels by defining additional limits in the sensor channels settings or modifying the lookups included with the template.

Requirements

  • PRTG Network Monitor 16.3.25 or later
  • Because the device template relies on the auto-discovery process, the device you want to monitor needs to be reachable via PING.
  • SNMP must be enabled on the device and the device must support the DELL-STORAGE-SC-MIB from where the data comes from.
  • The device template is expected to be compatible with the following devices:
    • Dell Compellent SC4020 with Dell Storage Center OS (SCOS) version 7.2.31
    • Dell Compellent Series 40
    • Dell Storage SC5020
    • Dell Storage SC5020F
    • Dell Storage SC7020
    • Dell Storage SC7020F
    • Dell Storage SC8000
    • Dell Storage SC9000
    • Dell Storage SCv2000
    • Dell Storage SCv2020
    • Dell Storage SCv2080
    • Dell Storage SCv3000
    • Dell Storage SCv3020

Known Issues and Limitations

  • Depending on the amount of Logical Disks configured on your Storage you may see a very large number of sensors (one per Logical Disk). It is recommended to increase the scanning interval to at least 5 minutes in this case to avoid excessive SNMP queries.
  • The temperature sensors may cause issues in some Firmware/Software versions. Feel free to follow-up if you encounter unexpected errors so that we may investigate.
  • You may get a "Storage Folder: Unassigned" sensor throwing errors by default: "0 GByte (Free Space) is below the error limit of 10 GByte in Free Space" - This sensor can be paused/deleted.
  • Some of the sensors (where a number like (1) or (1.1) is present in the name) are index-based, this means that if the device reboots or is updated the indexes *may* change. If this happens the sensors may become unreliable. If device is updated or rebooted it's advisable to delete these sensors and re-run the auto-discovery afterwards to be safe. The sensors will then be re-created and use the correct/appropriate index.
  • PRTG shows some of the alerts as reported by the monitored device via SNMP using Lookups. If the status is not reported correctly via SNMP, PRTG cannot detect any issues. For additional alerts, please set up limits for additional channels.
  • This device template was created based on data collected from other customers, so we cannot guarantee that the sensors described above will work on your systems or that the default thresholds are optimal for your use case. Use these components at your own risk. Please test and validate the sensors in your environment after deploying them.

Deployment and Usage

  1. Download the required zip archive containing the template's files here.
  2. Extract the archive to your PRTG program directory. By default, this is %ProgramFiles(x86)%\PRTG Network Monitor\.
  3. In PRTG, restart the core server: open Setup | System Administration | Administrative Tools | Restart Core Server and click Go!. This ensures that the MIB and lookups are loaded before you run the auto-discovery.
  4. Create a new device in PRTG with the address (IP or FQDN) of the device that you want to monitor and configure the SNMP credentials accordingly.
  5. Right-click your new device, select Run Auto Discovery with Template, browse for Dell Storage and select the Custom Dell Storage v0.x template from the list.
    Note: Using the auto-discovery with a dedicated device template is convenient here because it automates the creation of the custom sensors in an organized fashion.
  6. The sensors are deployed after a couple of seconds.
  7. You can adjust the channel limits or lookups to your needs later.

Result

The resulting sensors will look like this:

Sensor's Overview

Device Overview

Device Overview Right-click and select Open Image in New Tab for full-screen view

Sensor Overviews

Device Overview Right-click and select Open Image in New Tab for full-screen view

Device Overview Right-click and select Open Image in New Tab for full-screen view

No sensors deployed? :(
Please read ahead for troubleshooting.


Troubleshooting

Have any issues? Please don't hesitate to contact us by replying to this post or via a support ticket. Please make sure to mention this KB post. Please read ahead for troubleshooting steps that you can take in advance.

Auto-Discovery Log

Your auto-discovery log tells you a lot about what went wrong during the sensor's deployment. You can troubleshoot the auto-discovery by inspecting the auto-discovery log. If you get entries like the one below (NOT FOUND), it means that the required protocol or Object Identifier (OID) is not available and the sensors can't be deployed.

[...]
21.08.2017 09:17:17: Template Loaded; Device ID: 22848; Name: Custom Dell Storage v0.3
21.08.2017 09:17:18: Template Check; Device ID: 22848; Check ID: ping; FOUND
21.08.2017 09:17:19: Template Check; Device ID: 22848; Check ID: snmp; FOUND
21.08.2017 09:17:20: Template Check; Device ID: 22848; Check ID: snmp_scCacheTable; NOT FOUND
[...]

In the example above, some sensors were skipped because the device did not respond to the snmp_scCacheTable check. This means that this data is probably not available on your device. You can track this data by looking for the name after snmp_. In this case, a search for scCacheTable will tell you what OID from what MIB is missing.

You can also use this log to identify if the discovery was interrupted because the device did not respond to PING or to a basic SNMP check.

SNMP Data

If the discovery log is not sufficient, you can review the SNMP data directly from your device. To do so, download this file and use it with the Scan Script option in our SNMP Tester. This will allow you to review which SNMP queries succeed and which do not deliver any data. Please have this information at hand when contacting our support team.

Version History

VersionDescription
0.3First Public version/release
0.4Added Storage Folders (Space Free/Usage metrics)



Best Regards,
Luciano Lingnau [Paessler Support]

Created on Nov 30, 2018 1:01:42 PM by  Luciano Lingnau [Paessler]

Last change on Jul 26, 2021 11:41:43 AM by  Maike Guba [Paessler Support] (2,404) 2 1



Votes:

0

Hello,

some sensors were not identified because the OID is incorrect.

Is it possible to change the OID of the installed template or sensor?

Or do I have to create a custom sensor with the OIDs that work?

Thank you.

Created on Jun 6, 2019 3:43:44 AM



Votes:

0

Hi Sandro,

Both options should be possible. The easier option would be to use custom sensors. Alternatively, you could also edit the template linked above.


Kind regards,
Andreas Günther
Tech Support, Paessler AG

Created on Jun 7, 2019 12:08:04 PM by  Andreas Günther [Paessler Support]




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.