Votes:
I'm using the standard PRTG QNAP sensors, but they don't seem to "see" my expansion unit. How can I monitor this? I would like to monitor the expansion unit's hardware and also the disks from these other units.
Created on Mar 2, 2018 2:02:22 PM by
Last change on Apr 20, 2018 1:18:02 PM by
1 Reply
Votes:
This article applies to PRTG Network Monitor 16.3.25 or later
While we have some built-in sensors for QNAP in PRTG (Logical Disk, Physical Disk, System Health) they don't really support expansion units, because QNAP did a separate SNMP implementation for that.
I'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. The sensors will several metrics for any QNAP System (even without Expansion Units).
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:
* = Will display -1 when readings are not available
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 by default.
The resulting sensors will look like this:
Right-click and select Open Image in New Tab for full-screen view
Right-click and select Open Image in New Tab for full-screen view
Right-click and select Open Image in New Tab for full-screen view
No sensors deployed? :(
Please read ahead for 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.
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 QNAP NAS-MIB v0.4 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_enclosureTable; NOT FOUND [...]
In the example above, some sensors were skipped because the device did not respond to the snmp_enclosureTable 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 enclosureTable 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.
If the discovery log is not sufficient, you can review the SNMP data directly from your device. To do so, save the text below (in the white box) as .txt 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.
-------- Walk Default -------- hrSystemUptime walk=1.3.6.1.2.1.25.1.1 -------- MIB-2 System walk=1.3.6.1.2.1.1 -------- Sensor Specific Queries ---- storageManager walk=1.3.6.1.4.1.24681.1.4.1.1 ---
Version History
| Version | Description |
|---|---|
| 0.4 | First Public version/release |
Best Regards,
Luciano Lingnau [Paessler Support]
Created on Mar 2, 2018 2:04:09 PM by
Last change on Jul 26, 2021 11:20:25 AM by
Add comment