VolumeIndex Incorrect for Agent

bhumphrey

I've got a volume (VolumeID 55) that shows VolumeIndex = 3, but the SNMP Walk on that shows the VolumeIndex = 1 (hrStorageIndex - OID: 1.3.6.1.2.1.25.2.3.1.1). Here's the volume details from Orion:

VolumeID: 55
VolumeIndex: 3
VolumeDescription: C:\ Label: Serial Number 4EBFBD21

Here's the SNMP Walk output:
.1.3.6.1.2.1.25.2.3.1.1.1 = INTEGER: 1
.1.3.6.1.2.1.25.2.3.1.1.2 = INTEGER: 2
.1.3.6.1.2.1.25.2.3.1.1.3 = INTEGER: 3
.1.3.6.1.2.1.25.2.3.1.1.4 = INTEGER: 4
.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.7
.1.3.6.1.2.1.25.2.3.1.2.3 = OID: 1.3.6.1.2.1.25.2.1.3
.1.3.6.1.2.1.25.2.3.1.2.4 = OID: 1.3.6.1.2.1.25.2.1.2
.1.3.6.1.2.1.25.2.3.1.3.1 = STRING: "C:\ Label: Serial Number 4ebfbd21"
.1.3.6.1.2.1.25.2.3.1.3.2 = STRING: "X:\"
.1.3.6.1.2.1.25.2.3.1.3.3 = STRING: "Virtual Memory"
.1.3.6.1.2.1.25.2.3.1.3.4 = STRING: "Physical Memory"

Do agents look at something different to determine volume index? I noticed that there didn't seem to be a way from within Windows to show the same type of volume information as shown via SNMP.

bhumphrey

I worked with support on this and it turns out that Windows agents are polled via WMI and the index value provided by WMI does NOT match the index value provided by SNMP. I got around this by not including ObjectSubtype = Agent nodes in any automation that relied on index values matching from SNMP-based discoveries.