This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.

You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

ESX Detail information confusion

cgregors over 11 years ago

When Looking at some of our ESX servers, I find the following confusing:

The ESX Polling Status is OK

The Operational State is Connected

The ESX Status is DOWN

Can someone explain that to me please?

Top Replies

petrf over 11 years ago in reply to cgregors +2

I can clarify it. "ESX status" corresponds to ManagedStatus in VIM_Hosts table. ManagedStatus is computed from OverallStatus. When VIM gets via VMware API the OverallStatus as Red then it transforms to…

0 mharvey over 11 years ago

Chris,
Usually this is pulled from the VCenter/Vshpere API when logging into it to collect data. If you were to connect to the host using your Vsphere client and look at the status, what does that specific server show in terms of status?
Regards,
Matthew Harvey
Loop1 Systems
http://www.loop1systems.com
Cancel
Vote Up 0 Vote Down

Cancel
0 cgregors over 11 years ago in reply to mharvey

The only thing vSphere shows is a memory usage alarm for this specific ESX. I wouldn't expect that to translate to a "DOWN" status.
Cancel
Vote Up 0 Vote Down

Cancel
0 mharvey over 11 years ago in reply to cgregors

Odd, it seems to be showing the alerted status as down, though, from what I've seen working on this with other versions, it's usually due to a status change on the host itself that would be seen as a yellow triangle or red triangle on the VSphere Client. I wonder if SolarWinds VIM Management in NPM doesn't know how to translate the critical over and is just showing down instead.
Cancel
Vote Up 0 Vote Down

Cancel
0 cgregors over 11 years ago in reply to mharvey

When I look in the netperfmon db for the specific esx in the VIM_Hosts table I see the following:
OverallStatus:      Red
ManagedStatus:     2
HostStatus:          2
ConfigStatus:     Green
ConnectionState:      connected
Does that give any further insight
Cancel
Vote Up 0 Vote Down

Cancel
0 mharvey over 11 years ago in reply to cgregors

I bet it's mapping the critical to a down state. You'd need to open a case with SolarWinds to confirm that so they can see if there are mapping for critical/alerted states of this nature. If you also have SAM installed, are you able to pull the Hardware Health from this ESX host (this will show up as an option in List Resources) and see the memory issue that way?
Cancel
Vote Up 0 Vote Down

Cancel
0 cgregors over 11 years ago in reply to mharvey

Hardware status is A-OK
Ticket opened.
I'll post the reply here.
Cancel
Vote Up 0 Vote Down

Cancel
0 petrf over 11 years ago in reply to cgregors

I can clarify it.
"ESX status" corresponds to ManagedStatus in VIM_Hosts table. ManagedStatus is computed from OverallStatus. When VIM gets via VMware API the OverallStatus as Red then it transforms to ManagedStatus as Dowm.
Red status means that the host has alarms or configuration issues with a red status.
For more information see VMware API documentation:
look for overallStatus - http://pubs.vmware.com/vsphere-51/index.jsp?topic=%2Fcom.vmware.wssdk.apiref.doc%2Fvim.ManagedEntity.html&resultof=%22overallstatus%22%20%22overallstatu%22%20
http://pubs.vmware.com/vsphere-51/index.jsp?topic=%2Fcom.vmware.wssdk.apiref.doc%2Fvim.ManagedEntity.Status.html
Cancel
Vote Up +2 Vote Down

Cancel