Which action should the administrator take to correct this behavior?

An administrator is able to manage an ESXi 6.x host connected to vCenter Server using the vSphere Web Client but is unable to connect to the host directly.
Which action should the administrator take to correct this behavior?

An administrator is able to manage an ESXi 6.x host connected to vCenter Server using the vSphere Web Client but is unable to connect to the host directly.
Which action should the administrator take to correct this behavior?

A.
Restart management agents on the ESXi host.

B.
Disable Lockdown Mode on the ESXi host through vCenter Server.

C.
Disable the ESXi firewall with the command esxcli network firewall unload.

D.
Reboot the ESXi host.

Explanation:
Explanation/Reference:



Leave a Reply 5

Your email address will not be published. Required fields are marked *


SomeDude

SomeDude

I would say this is a case of B being more correct. Yes, management agents having issues may cause the web client to work and SSL cannot connect. Though, Lockdown mode is most likely the issue.

andy75

andy75

‘B’ for sure.
Had there been anything wrong with mgmt agents, vSphere Client (both Web and C#) would not be able to communicate with ESX either.

Fonda ain't got a motor in the back of her Honda

Fonda ain't got a motor in the back of her Honda

https://kb.vmware.com/kb/2040768
To resolve this issue:

Disable lockdown mode through the DCUI and then enable it through the vCenter Server instead.
The vCenter Server does not keep track of lockdown mode state changes that initiated outside of the vCenter Server itself.