All,
We are working on deploying OME in our production environment. The next Phase of our deployment is the monitoring and management of our ESXi HyperVisors.
Following the provided steps, the hyper-visor owner team is setting up OMSA on their servers. They also set up a root level account for us to do management and discovery with. With this i've been able to correctly discover the two test servers (one M620, one M610). However we're not seeing these come up in the compliance tab for firmware management.
Our environment is all ESXi 5.1, with a good amount of hyper-visors that is growing all the time.
From other forum posts, I've gleamed (though not confirmed) that OME does not support firmware/bio's work directly to the server with ESXi. I assume this is because of the limitations on ESXi from a CLI perspective.
What is the best method for resolving this, in order to get this to work. I've seen some mentions of using DRAC itself to run these updates. That being said, i've had no success in getting OME to get any accurate data from the drac's in production. I've also not found any documentation on how to setup/validate that it can do what it needs to do with a drac.
I've seen mentions of something like a ws-man profile (and when I tried to connect to a idrac6 (at current release) it said that it wasn't able to get a profile) but no real mention of how to validate/set this up.
All attempts i've made to connect to a drac via wsman have failed. I've received profile unable to be pulled, and 'external component has thrown an exception' when utilizing the troubleshooting tool. As i have no previous understanding of these functions I have no context in which to troubleshoot this on my own.
Any guidance on getting this to work, so that we can centrally manage firmware/bio's etc on our hyper-visor's from OME would be greatly appreciated. As stated above, our environment is all M610/M620 for hyper-visors. Our ESXi versions are all up to date, as is our dracs.
Thanks,
Denny Pruitt
