Hi Team,
storage status info value is unset, how can I change it
I trying to add Esxi to a device monitoring tool via SNMP and it is adding successfully
but in order to get the health status of the hard disk the vendor is saying that value of storage status should be "set"
issue resolved after updating 6.7 to 6.7 EP or latest
Hey nbgiridar,
This value is automatically set when you have sensors available on your host. If you try to check for the Hardware Status on the Web Client, what do you see?
Hi Lalegre
thank you and it shows green
do we have to install HP iLo drivers?
To be honest I am not 100% if that does not already comes inside the Custom ISO. Did you use the Custom ISO to install the HPE server?
no, i used the generic one from VMware
Always use the vendor ISO if possible as it has the required drivers and even some utilities that can be used to integrate with their solutions. I am not saying that is the solution but that is the proper way to install the ESXi.
Try to install it and see if it works.
thank you, but the Esxi is in production
> thank you, but the Esxi is in production
do you have only one host in production?
yes and have only one Esxi
found the issue, the hard disk category is detected as other
how can we change it, it should be storage
[Additional text and screenshot below added from duplicate thread by moderator]
need this to be changed in order to monitor this ESXi's hard disk health on a device monitoring tools
Moderator: Please do not start multiple threads on the same topic.
The second thread you created this morning has been deleted, and the screenshot from that thread added here.
sorry, i can delete this an create another
You may have to reinstall with the HPE image, which you should have used to begin with. Otherwise, you can open a support case with HPE.
thank you
Moderator: I see no need to delete this thread - it has all the information you have shared so far, and active replies from other users.
thank you and I have another ESXi which is detecting the device type correctly
I used the same image
issue resolved after updating 6.7 to 6.7 EP or latest