Hi,
You can change to v2c in the device settings, no need to delete and re-add.
This may be a Windows problem, do you or anyone else have other machines with >16TB of diskspace on Windows?
For example, until Net-SNMP 5.7 there was no way to correctly monitor/graph/detect disk sizes over 16TB on Linux either. 5.7 added support for larger counters, which we now use.
There may be a similar limitation on Windows. (but I guess it is possible that this requires v2c and you're not using it)
Tom
On 4/07/2013 5:11, DaZZa wrote:
On 4 July 2013 12:59, Michael Sweikata sweikatam1@nku.edu wrote:
I'd try to identify what makes this host unique if you have other Windows boxes being monitored. Do you have a partition size of 8tb and a full disk size of 15tb? Is there RAID involved?
There is RAID involved - the disk space is on an external disk enclosure, and managed by an hardware RAID in the server. It's the only server I have where this type of disk arrangement is used.
The disk size is actually closer to 18 Tb - there are two partitions on the disk (dynamic volumes, Windows calls them), one of around 15 Tb and the other around 3 Tb. The 3Tb volume is reporting its size corectly
SNMPv1 is only the means of identifying the host, it actually reads the data through MIBs.
Yes, but SNMP V2 allows for 64 bit counters, whereas SNMP V1 doesn't - I was wondering if this volume was maybe replying with a greater sector count than SNMP V1 could deal with. I wasn't aware Windows supported SNMP V2, or I would have used that. I may delete the host and re-create it with SNMP V2 and see if that makes a difference.
Thanks.
DaZZa _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium