Hello,
We have noticed that the LUNs of the Nimble Storage are probably being read incorrectly by the KS host.
The test "VM Host free Datastore space" is used via an ESX host.
Currently there is still 1.36 TB of 5 TB free on LUN001. That would be 27% approx.
However, KS Host only recognizes 8% free space.
Presumably the compression and deduplication of the nimble is not taken into account here.
Are there any other ways of reading this?
Hostmon is version 14.28 on Windows Server 2022
RMA: Version: 8.10 on host: SMON02 Windows Server 2019 Build 17763
Best Regards
HPE Nimble free Datastore value not correct
If HostMonitor is able to perform the test then everything is activated.
But we need hostname/IP, username, password
>Presumably the compression and deduplication of the nimble is not taken into account here
When HostMonitor requests MOB to get free space, MOB does not provide compression and deduplication related information, at least on our system.
May be there is such information on your system, so it would be good to check
Regards
Alex
But we need hostname/IP, username, password
>Presumably the compression and deduplication of the nimble is not taken into account here
When HostMonitor requests MOB to get free space, MOB does not provide compression and deduplication related information, at least on our system.
May be there is such information on your system, so it would be good to check
Regards
Alex
me again ;)
Hi Alex,
Access to the VCenter was rejected by the management. Since the ESX hosts can only see the "falsified" data anyway and the KS Hostmon reads it out via the MOB, this is rather unfavorable anyway since other values are available on the storage itself.
Is there a way to read the LUNs of the Nimble Storage directly without using the ESX host? I would take a look at this with a colleague. Maybe you've had something like this before?
Best regards Felix
Access to the VCenter was rejected by the management. Since the ESX hosts can only see the "falsified" data anyway and the KS Hostmon reads it out via the MOB, this is rather unfavorable anyway since other values are available on the storage itself.
Is there a way to read the LUNs of the Nimble Storage directly without using the ESX host? I would take a look at this with a colleague. Maybe you've had something like this before?
Best regards Felix
Such devices support SNMP, right?
So you may try SNMP Get test or Drive Free Space in SNMP mode.
Hard to say what exactly OIDs supported. HPE MIB files offer thousand counters but most of them does not work on devices we have..
May be counters from this table can be used
https://infosight.hpe.com/InfoSight/med ... 04395.html
volSizeLow Unsigned32 Yes Max. size in MB (low order bytes).
volSizeHigh Unsigned32 Yes Max. size in MB (high order bytes).
volUsageLow Unsigned32 Yes Usage in MB (low order bytes).
volUsageHigh Unsigned32 Yes Usage in MB (high order bytes).
volReserveLow Unsigned32 Yes Reserved MB (low order bytes).
volReserveHigh Unsigned32 Yes Reserved MB (high order bytes).
If you provide SNMP access, may be we can create new tests. Same for Aruba
Regards
Alex
So you may try SNMP Get test or Drive Free Space in SNMP mode.
Hard to say what exactly OIDs supported. HPE MIB files offer thousand counters but most of them does not work on devices we have..
May be counters from this table can be used
https://infosight.hpe.com/InfoSight/med ... 04395.html
volSizeLow Unsigned32 Yes Max. size in MB (low order bytes).
volSizeHigh Unsigned32 Yes Max. size in MB (high order bytes).
volUsageLow Unsigned32 Yes Usage in MB (low order bytes).
volUsageHigh Unsigned32 Yes Usage in MB (high order bytes).
volReserveLow Unsigned32 Yes Reserved MB (low order bytes).
volReserveHigh Unsigned32 Yes Reserved MB (high order bytes).
If you provide SNMP access, may be we can create new tests. Same for Aruba
Regards
Alex