VMware Cloud Community
jvm2016
Hot Shot
Hot Shot
Jump to solution

powercli_non responding host

hi Luc,

can yu suggest if nonresponding host is being captured by powercli.

if i run get-vmhost (against vcnter) will the connection state give us right infomationas being non responding??

Reply
0 Kudos
1 Solution

Accepted Solutions
LucD
Leadership
Leadership
Jump to solution

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.


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

View solution in original post

Reply
0 Kudos
8 Replies
LucD
Leadership
Leadership
Jump to solution

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...


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

Reply
0 Kudos
jvm2016
Hot Shot
Hot Shot
Jump to solution

1.I see some unusual results today wherein host was not responding in vcenter but powercli script

Shows connected.

2.Also if you can suggest how powercli fetching information from get commands .is it from vcnter db or some other internal mechanism.

Reply
0 Kudos
LucD
Leadership
Leadership
Jump to solution

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.


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

Reply
0 Kudos
jvm2016
Hot Shot
Hot Shot
Jump to solution

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.

Reply
0 Kudos
LucD
Leadership
Leadership
Jump to solution

It's a work in progress.
A number of the methods are available as REST calls.
William did a series on that, see Exploring new VCSA VAMI API w/PowerCLI: Part 1


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

Reply
0 Kudos
jvm2016
Hot Shot
Hot Shot
Jump to solution

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.

Reply
0 Kudos
LucD
Leadership
Leadership
Jump to solution

Brian did just that, see VSPHERE 6.5 – AUTOMATE VCSA BACKUP


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

Reply
0 Kudos
jvm2016
Hot Shot
Hot Shot
Jump to solution

Thanks I will check this .

Reply
0 Kudos