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

Erratic values while monitoring Snapserver XSR

Votes:

0

Hello everybody,

We are trying to monitor our Snapserver disks, using the SNMP Disk Free sensor. However, after selecting the partitions/disks that are to be monitored, only one of them (the root, '\') gives stable readings, even though they are not correct. The other two partitions give erratic results, they are either negative, or positive, constantly changing.

Any ideas?

disk-free snapserver snmp

Created on Oct 12, 2017 11:31:16 AM



5 Replies

Votes:

0

Hey Andre,

Please use the SNMP Linux Disk Free sensor or the SSH Disk Free sensor instead as the SNMP Disk Free sensor is primarily designed for Windows systems.

Best regards,
Sven

Created on Oct 13, 2017 11:25:42 AM by Sven Roggenhofer [Paessler Technical Support]



Votes:

0

Hi Sven,

I've tried that, but to no avail. I get error #223 on the SNMP Linux Free Disk sensor and error PE094 (device is not compatible) on the SSH Free Disk sensor. In PRTG, under the Linux login credencials, I am using the same user/pwd as I use to access the SnapServer web portal (admin access).

PRTG also suggested the active processes and Memory (Swap) Free sensors, and they're up and running, with accurate results. I'm unsure whether these use SNMP or not, though.

Created on Oct 13, 2017 1:52:17 PM



Votes:

0

Hey Andre,

Please refer to this KB-article which might point you in the right direction.

Best regards,
Sven

Created on Oct 16, 2017 6:33:52 AM by Sven Roggenhofer [Paessler Technical Support]



Votes:

0

Hello Sven,

I already had a look at that KB article. The allocation sizes for the disks are, in fact, 4096 bytes. However, the SnapServer uses its own proprietary OS, called GuardianOS, so there is really no possibility of modifying the snmp.conf file.

By querying the SnapServer at OID 1.3.6.1.2.1.25.3.6.1.4, I get the hrdDiskStorage capacity values for all disks:

  • SCSI disk /dev/sda - 819572736
  • SCSI disk /dev/sdb - 819572736
  • SCSI disk /dev/sdc - 819572736
  • SCSI disk /dev/sdd - 819572736
  • RAID disk /dev/md0 - 115572736
  • RAID disk /dev/md1 - 524517376
  • RAID disk /dev/md2 - 524517376
  • RAID disk /dev/md3 - 524517376
  • RAID disk /dev/md4 - 524517376
  • RAID disk /dev/md5 - 524517376
  • RAID disk /dev/md6 - 524517376
  • RAID disk /dev/md7 - 524517376
  • RAID disk /dev/md8 - 524517376
  • RAID disk /dev/md9 - 524517376

According to the SnapServer webportal, I have 4 disks, each with 4.55 TB, and my Data Pool has 13.61 TB of capacity (63% of which are occupied). None of these values above match the figures from the webportal. make sense.

I can't find any Overland Storage MIBs, so I am kind of stuck here.

Created on Oct 24, 2017 1:16:51 PM



Votes:

0

Hey André,

Please contact the vendor's support and ask them for a solution or for a MIB file with the proper OIDs. However, if even the walk does not get correct values, PRTG is not able to gain them as well.

Best regards,
Sven

Created on Oct 25, 2017 8:34:57 AM by Sven Roggenhofer [Paessler Technical 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.