Remember that this depends where you are connected.
If connected to a vCenter, the ConnectionState property will show how the vCenter 'sees' the ESXi node.
One of these is indeed 'NotResponding'.
When you connect to the ESXi node directly, the ability to connect indicates if the ESXi node can be reached or not.
If it is pure connectivity you want to check, there are other options like a ping, a vmkping...
1.I see some unusual results today wherein host was not responding in vcenter but powercli script
2.Also if you can suggest how powercli fetching information from get commands .is it from vcnter db or some other internal mechanism.
1. The ESXi node can be in a connected state, but some agents might be having issues.
You will have to look in the logs to try and determine what is causing it.
2. PowerCLI cmdlets use SOAP calls to the vSphere server (beit the vCenter or an ESXi node).
The vCenter itself will then eventually access its DB.
PowerCLI cmdlets themselves will never access the vCenter DB directly, and neither should a user.
The DB schema is not documented and it definitely is not supported.
Thanks.i think earlier yu mentioned soap is being replaced by rest api .is that correct?
I was checking some powershell commands for azure wherein commands ultimately uses rest api and uses json as datatranfer mechanism. But powercli is not using this approach as yu clarified.
Thanks .I am going to check this .
This discussion has gone little out of topic we started .just though of asking if there is a vami api
Which I can use to initiate backup of Vcsa appliance or psc.i m referring to vcsa native backup available in vami.if yu have come across any such api.
Thanks I will check this .