Skip to main content

To change the ESXi root password when ESXi host managed by VCD




Recently we got into the issue where I have to change the ESXi host root password which was managed by the vCloud Director.

Changing the root password directly from the ESXi host is not recommended when the ESXi host is managed by vCloud Director. All operation task need to be accomplish through vCD.

NOTE: The test was done on both the ESXi hosts in maintenance mode from VCD and with taking them in to maintenance mode. Since you are performing the ESXi root password change I would suggest to  perform during maintenance mode.

Steps performed to change the root password of the ESXi host.

Step 1) Enable or Disable an ESX/ESXi Host:

You can disable a host to prevent vApps from starting up on the host. Virtual machines that are already running on the host are not affected.

- To perform maintenance on a host, migrate all vApps off of the host or stop all vApps and then disable the host.

Procedure:

1. Click the Manage & Monitor tab and click Hosts in the left pane.
2. Right-click the host name and select Enable Host or Disable Host.

vCloud Director enables or disables the host for all provider virtual datacenters that use its resources.

Step 2) Move Virtual Machines from one ESX/ESXi Host to Another

You can move all the virtual machines from one ESX/ESXi host to other hosts in the same cluster. This ability is useful to unprepare a host, or to perform maintenance on a host without affecting running virtual machines.

Prerequisites:

Disable the host (As mentioned in Step 1)

Procedure:

1.  Click the Manage & Monitor tab and click Hosts in the left pane.
2. Right-click the host name and select Redeploy all VMs.
3. Click Yes.

vCloud Director puts the host into maintenance mode and moves all of its virtual machines to other hosts in the same cluster.

Step 3) Change the root password of the corresponding ESXi host.

Step 4) Prepare the host and then enable the host back in VCD environment.

If you notice any HOST which has issue with the agent communication (As observed during our test), please repair the appropriate HOST:

Repair a Provider Virtual Datacenter ESX/ESXi Host:

Procedure:

1. Click the Manage & Monitor tab and click Provider VDCs in the left pane.
2. Right-click the provider virtual datacenter name and select Open.
3. Click the Hosts tab.
4. Right-click the host name and select Repair Host.



NOTE: vCloud Director repairs the host. This operation affects all provider virtual datacenters that use the host.

Comments

Popular posts from this blog

Changing the FQDN of the vCenter appliance (VCSA)

This article states how to change the system name or the FQDN of the vCenter appliance 6.x You may not find any way to change the FQDN from the vCenter GUI either from VAMI page of from webclient as the option to change the hostname always be greyed out. Now the option left is from the command line of VCSA appliance. Below steps will make it possible to change the FQDN of the VCSA from the command line. Access the VCSA from console or from Putty session. Login with root permission Use above command in the command prompt of VCSA : /opt/vmware/share/vami/vami_config_net Opt for option 3 (Hostname) Change the hostname to new name Reboot the VCSA appliance.   After reboot you will be successfully manage to change the FQDN of the VCSA . Note: Above step is unsupported by VMware and may impact your SSL certificate and face problem while logging to vSphere Web Client. If you are using self-signed certificate, you can regenerate the certificate with the

Collecting Logs from NSX-T Edge nodes using CLI

  This article explains how to extract the logs from NSX-T Edge nodes from CLI. Let's view the steps involved: 1) Login to NSX-T  Edge node using CLI from admin credentials. 2) Use of  " get support-bundle " for Log extraction. get support-bundle command will extract the complete logs from NSX-T manager/Edge nodes. nsx-manager-1> get support-bundle file support-bundle.tgz 3) Last step is to us e of " copy file support-bundle.tgz url " command. copy file will forward your collected logs from the NSX-T manager to the destination(URL) host from where you can download the logs. copy file support.bundle.tgz url scp://root@192.168.11.15/tmp Here, the URL specified is the ESXi host ( 192.168.11.15) under /tmp partition where logs will be copied and from there one can extract it for further log review. Happy Learning.  :)

Removing NSX-T manager extension from vCenter

In NSX-T starting from ver 2.4 NSX-T appliance got decoupled from vCenter where now its not mandatory to run NSX-T on vCenter platform only. Now NSX-T can be managed through standalone ESXi host, KVM or through container platform. As in version 2.4 there is still an option available to connect vCenter to NSX-T using Compute Manager. Here in this blog we will learn how we can unregister and register NSX-T extenstion from vCenter in case of any sync or vCenter connectivity issue with NSX-T. Lets get started.. 1) Login to NSX-T UI Go to -> System ->Compute Manager Here, vCenter is showing in Down status where the status is showing as "Not Registered" 2) When we click on "Not Registered" option its states below error. 3) When try to click on Resolve option its states below. At this stage if the Resolve option doesn't work then its require the remove the NSX-T extenstion from vCenter. To remove the NSX-T e