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

SNMP Disk Free Sensor with VMware vCenter Server Virtual Appliance 6.0 (vCSA)

Votes:

0

Why can't I use the "SNMP Linux Disk Free Sensor with vmWare vCSA ?

It fails to find any disks...

disk-free snmp-sensor vcsa6 vmware

Created on Oct 4, 2018 5:44:22 PM by  JR Andreassen [Paessler Support] (220) 3 1



1 Reply

Votes:

0

There appears to be a "bug" in the vCSA snmp implemenmtation for 6.0...

(Tested with VMware-vCenter-Server-Appliance 6.0.0.10000 embedded build 3018521 VMware, Inc x86_64)

The Linux Disk XXX sensors use the MIB-II Host Resources tables:

For the Disk Free sensor we check the hrStorage Table for hrDeviceType(1.3.6.1.2.1.25.2.3.1.2) .hrStorageTypes one of : hrStorageFixedDisk(1.3.6.1.2.1.25.2.1.4) hrStorageRamDisk(1.3.6.1.2.1.25.2.1.8) hrStorageNetworkDisk(1.3.6.1.2.1.25.2.1.10)

With the vCSA 6.0, it returns:

1.3.6.1.2.1.25.2.3.1.2.1 = OID: .1.3.6.1.2.1.25.2.1.4
1.3.6.1.2.1.25.2.3.1.2.2 = OID: .1.3.6.1.2.1.25.2.1.4
1.3.6.1.2.1.25.2.3.1.2.3 = OID: .1.3.6.1.2.1.25.2.1.4
1.3.6.1.2.1.25.2.3.1.2.4 = OID: .1.3.6.1.2.1.25.2.1.4
1.3.6.1.2.1.25.2.3.1.2.5 = OID: .1.3.6.1.2.1.25.2.1.4
1.3.6.1.2.1.25.2.3.1.2.6 = OID: .1.3.6.1.2.1.25.2.1.4
1.3.6.1.2.1.25.2.3.1.2.7 = OID: .1.3.6.1.2.1.25.2.1.4
1.3.6.1.2.1.25.2.3.1.2.8 = OID: .1.3.6.1.2.1.25.2.1.4
1.3.6.1.2.1.25.2.3.1.2.9 = OID: .1.3.6.1.2.1.25.2.1.4
1.3.6.1.2.1.25.2.3.1.2.10 = OID: .1.3.6.1.2.1.25.2.1.4
1.3.6.1.2.1.25.2.3.1.2.11 = OID: .1.3.6.1.2.1.25.2.1.4
1.3.6.1.2.1.25.2.3.1.2.12 = OID: .1.3.6.1.2.1.25.2.1.4
1.3.6.1.2.1.25.2.3.1.2.13 = OID: .1.3.6.1.2.1.25.2.1.4
1.3.6.1.2.1.25.2.3.1.2.14 = "0.0.0"
1.3.6.1.2.1.25.2.3.1.3.1 = "/" 
1.3.6.1.2.1.25.2.3.1.3.2 = "/dev" 
1.3.6.1.2.1.25.2.3.1.3.3 = "/dev/shm" 
1.3.6.1.2.1.25.2.3.1.3.4 = "/boot" 
1.3.6.1.2.1.25.2.3.1.3.5 = "/storage/core" 
1.3.6.1.2.1.25.2.3.1.3.6 = "/storage/log" 
1.3.6.1.2.1.25.2.3.1.3.7 = "/storage/db" 
1.3.6.1.2.1.25.2.3.1.3.8 = "/storage/dblog" 
1.3.6.1.2.1.25.2.3.1.3.9 = "/storage/seat" 
1.3.6.1.2.1.25.2.3.1.3.10 = "/storage/netdump" 
1.3.6.1.2.1.25.2.3.1.3.11 = "/storage/autodeploy" 
1.3.6.1.2.1.25.2.3.1.3.12 = "/storage/invsvc" 
1.3.6.1.2.1.25.2.3.1.3.13 = "/var/spool/snmp" 
1.3.6.1.2.1.25.2.3.1.3.14 = "Real Memory" 

Looking at:

1.3.6.1.2.1.25.2.3.1.2.1 = "1.3.6.1.2.1.25.2.3.1.2.4"
Which is 
 X.n = "X.4"  where 
  X is the OID of hrDeviceType
  n is the Table index
  4 the "Fixed Disk" index of the hrStorageTypes table...
Which is the wrong OID...
It should be:
1.3.6.1.2.1.25.2.3.1.2.1 = "1.3.6.1.2.1.25.2.1.4"
 X.n = "Y"  where 
  X is the OID of hrDeviceType
  Y is the "Fixed Disk" entry in hrStorageTypes table...

With vCSA 6.7, it comes back correctly..

.1.3.6.1.2.1.25.2.3.1.2.1 = OID: .1.3.6.1.2.1.25.2.1.4
.1.3.6.1.2.1.25.2.3.1.2.2 = OID: .1.3.6.1.2.1.25.2.1.4
.1.3.6.1.2.1.25.2.3.1.2.3 = OID: .1.3.6.1.2.1.25.2.1.4
.1.3.6.1.2.1.25.2.3.1.2.4 = OID: .1.3.6.1.2.1.25.2.1.4
.1.3.6.1.2.1.25.2.3.1.2.5 = OID: .1.3.6.1.2.1.25.2.1.4
.1.3.6.1.2.1.25.2.3.1.2.6 = OID: .1.3.6.1.2.1.25.2.1.4
.1.3.6.1.2.1.25.2.3.1.2.7 = OID: .1.3.6.1.2.1.25.2.1.4
.1.3.6.1.2.1.25.2.3.1.2.8 = OID: .1.3.6.1.2.1.25.2.1.4
.1.3.6.1.2.1.25.2.3.1.2.9 = OID: .1.3.6.1.2.1.25.2.1.4
.1.3.6.1.2.1.25.2.3.1.2.10 = OID: .1.3.6.1.2.1.25.2.1.4
.1.3.6.1.2.1.25.2.3.1.2.11 = OID: .1.3.6.1.2.1.25.2.1.4
.1.3.6.1.2.1.25.2.3.1.2.12 = OID: .1.3.6.1.2.1.25.2.1.4
.1.3.6.1.2.1.25.2.3.1.2.13 = OID: .1.3.6.1.2.1.25.2.1.4
.1.3.6.1.2.1.25.2.3.1.2.14 = OID: .1.3.6.1.2.1.25.2.1.4
.1.3.6.1.2.1.25.2.3.1.2.15 = OID: .1.3.6.1.2.1.25.2.1.4
.1.3.6.1.2.1.25.2.3.1.2.16 = OID: .1.3.6.1.2.1.25.2.1.4
.1.3.6.1.2.1.25.2.3.1.2.17 = OID: .1.3.6.1.2.1.25.2.1.4
.1.3.6.1.2.1.25.2.3.1.2.18 = OID: .1.3.6.1.2.1.25.2.1.4
.1.3.6.1.2.1.25.2.3.1.2.19 = OID: .1.3.6.1.2.1.25.2.1.2
.1.3.6.1.2.1.25.2.3.1.3.1 = STRING: "/dev"
.1.3.6.1.2.1.25.2.3.1.3.2 = STRING: "/dev/shm"
.1.3.6.1.2.1.25.2.3.1.3.3 = STRING: "/run"
.1.3.6.1.2.1.25.2.3.1.3.4 = STRING: "/sys/fs/cgroup"
.1.3.6.1.2.1.25.2.3.1.3.5 = STRING: "/"
.1.3.6.1.2.1.25.2.3.1.3.6 = STRING: "/tmp"
.1.3.6.1.2.1.25.2.3.1.3.7 = STRING: "/storage/db"
.1.3.6.1.2.1.25.2.3.1.3.8 = STRING: "/storage/core"
.1.3.6.1.2.1.25.2.3.1.3.9 = STRING: "/storage/netdump"
.1.3.6.1.2.1.25.2.3.1.3.10 = STRING: "/storage/seat"
.1.3.6.1.2.1.25.2.3.1.3.11 = STRING: "/storage/log"
.1.3.6.1.2.1.25.2.3.1.3.12 = STRING: "/storage/dblog"
.1.3.6.1.2.1.25.2.3.1.3.13 = STRING: "/storage/autodeploy"
.1.3.6.1.2.1.25.2.3.1.3.14 = STRING: "/storage/archive"
.1.3.6.1.2.1.25.2.3.1.3.15 = STRING: "/storage/imagebuilder"
.1.3.6.1.2.1.25.2.3.1.3.16 = STRING: "/storage/updatemgr"
.1.3.6.1.2.1.25.2.3.1.3.17 = STRING: "/boot"
.1.3.6.1.2.1.25.2.3.1.3.18 = STRING: "/var/spool/snmp"

Given that this is an error / bug on the part of the Linux Distro used by the vmWare vCSA, Paessler can't change the Sensor to accommodate it...

We recommend upgrading the vCSA to a version that reports the disk type correctly...

Created on Oct 4, 2018 5:52:59 PM by  JR Andreassen [Paessler Support] (220) 3 1

Last change on Oct 4, 2018 6:02:47 PM by  JR Andreassen [Paessler Support] (220) 3 1




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.