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

VM Creation Date & Time from Powercli

Most of the times we have several requirement when we talk about IT environment like designing , deployment , compliance check or for Security auditing the environment.
Somewhere during security auditing we require to provide several information to security team to get successful audit.
One of them is the compliance of Virtual machine auditing of creation date and time.
Here into this post we will explore how to get the creation date and time of virtual machine hosted into the vCenter or ESXi.
To get the details we will use VMware Powercli to extract the details.
By default there is no function added into Powercli to get such details, so here we will add a function of vm creation date.
Below is the function which needed to be copy and paste into the Powercli.
=======================================================================
function Get-VMCreationTime { $vms = get-vm $vmevts = @() $vmevt = new-object PSObject foreach ($vm in $vms) { #Progress bar: $foundString = "       Found: "+$v…

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 permissionUse above command in the command prompt of VCSA : /opt/vmware/share/vami/vami_config_netOpt for option 3 (Hostname)Change the hostname to new nameReboot 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 help of below KB 2112283 article.



Happy Sharin…

Could not connect to one or more vCenter Server systems: https://FQDN:443/sdk

Recently I got a case where vCenter 6.0 where the webclient was not showing inventory while loading. Issue occur when the customer was performing migration activity of virtual machine.
We verified that the vpxd services of vCenter, which is VCSA (Appliance), went into stopped stated just after starting means its crashing.
On VCSA Shell: service-control --status vmware-vpxd shows "stopped" service-control --start vmware-vpxd starts the service starts for a couple of seconds and stops again
VCSA 6.0 is linked with extrnal PSC 6.0. Verified the services of PSC and found all looks into good state.
Tried to power off both the VCSA and PSC and Power on in sequence where we started first PSC and later VCSA. After restarting the VCSA, status of the VPXD services was same as it was getting stopped after couple of seconds.
Checked the VPXD logs and found that the heartbeat between ESXi and VCSA was getting timed out for more than 1032 ms or more.
VCSA has generated the core dump at /var/core. …