Skip to main content

NSX 6.3.3 Controller Deployment Status "Deploying" for long time and fails (root password expired issue)

Problem Description:

NSX controllers’ deployment is failing on NSX 6.3.3 version. The controller shows “Deploying” status for around 30-45 mins and later failed/VM is deleted although your entire NSX configuration looks good. During the deployment state, the controller VM is deployed and powered on. But, it is not assigned with IP Address which is specified in the IP Pool.
It looks like that “root password expired” issue with NSX controller VM. The NSX Controller is built-on Photon OS and root password age is set 90 days. This may be cause for the controller machine unable to assign the IP Address during its customization stage.

Work Around:

1. After the controller VM is deployed and powered on, connect the VM and Launch web console.
2. Enter the username as “root” and password “vmware”
3. Enter the new password and note down. (must be 8 chrs and one upper, lower and special chr)
4. Type the following command:
vi /etc/system/network/  
5. Press “I” to insert text in the vi
6. Type "Address=" eg: Address=
7. Type "Gateway="        eg:
8. Press ESC key
9. Then, press :wq to save the file  
10. Then type “reboot” command for rebooting the controller VM and wait for few minutes. Then you can see the IP address is assigned to the Controller VM.  
11. You can see the logs /var/log/. I found password expired error on firstboot log file.  
12. When I ran the “chage –l root” command in the console, found that “root” password is set to expire in 90 days. This may be issue that causing the controller VM is not assigned with IP Address.
13. Wait for few minutes (approx. 5 mins) and try to login back to the controller VM thru web console by using “root” account. If the VM is not allowing you to login, means that Controller VM is joined to the controller-cluster and root account is disabled.
14. SSH to the controllers VM and enter “admin” as user name and password that you mentioned during the time of deployment.
15. Then type “show controller-cluster status”, you can see the VM is joined to the cluster.
16. Repeat the same steps for other Controllers VMs.  
17. After all 3 controllers deployed and verify the node status and no error reported anywhere.  


fahadysf said…
Beautiful.. Thanks for documenting the procedure you followed to get the problem solved.

Popular posts from this blog

vCenter Reinstallation after 60-Days trial expires without losing Database Contents

Many of us still evaluating the vSphere and vCenter in our test environments. Sometimes, it takes more than 60 days to evaluate where trial edition expires. We can't extend the trial edition in ESX host, either we have to reinstall it or license it. vCenter also have to follow the same way as ESX does. But, here we can keep old database contents as it is when you reinstall the vCenter software. This document using vCenter 4.0 and SQLEXPRESS 2005 (built in) database. At the time of installation of vCenter 4.0, it installs SQLEXPRESS 2005 by default unless any other Database specified. Mostly, we are using built-in database is SQLEXPRESS 2005 for testing environment. When you install vCenter 4.0, it installs SQLEXPRESS 2005 and creates a database called "SQLEXP_VIM". You can view this thru SQL Server Configuration Manager console. Start à All Programs à Microsoft SQL Server 2005 à Configuration Tools à SQL Server Configuration Manager Creating DSN Create a Syste

Set VLAN ID to IPMI Address in Nutanix

The IPMI is remote management interface like as HP iLO, DELL DRAC. During the Nutanix cluster deployment, it is not possible to mention the VLAN ID of the IPMI's IP Address. This need to be entered thru command line via ESXi host or Windows Hyper-V. This article talks about ESXi host only. Login to ESXi thru SSH client. Run the following command to enter the VLAN ID (we assume that you already configured IP Address) ~ # /ipmitool lan set 1 vlan id 333 ~ # /ipmitool lan print1 Set in Progress         : Set Complete Auth Type Support       : NONE MD2 MD5 PASSWORD  Auth Type Enable        : Callback : MD2 MD5 PASSWORD                          : User     : MD2 MD5 PASSWORD                          : Operator : MD2 MD5 PASSWORD                          : Admin    : MD2 MD5 PASSWORD                          : OEM      : MD2 MD5 PASSWORD  IP Address Source       : Static Address IP Address              : xx.xx.xx.xx Subnet Mask             : MAC

Changing Thin to Thick disk and vice-versa

You can change the existing Virtual Hard disks (VMware based) from Thick to thin and vice-versa. This can be achieved by either using VMotion/SVMotion or command line tool called " vmkfstools". Using VMotion/SVMotion is required a valid license. Select “Migrate” and choose “Change Datastore” and select the Disk format. If you don’t have a VMotion/SVMotion license, use the following command to achieve the same. From Thick to Thin: vmkfstools –i "Thickdisk.vmdk" -d thin "Thindisk.vmdk" It will start to clone to virtual hard disk in Thin Provision method. After completed, you can attach this disk with VM and power it on. If all looks good, you can delete the original thick disk from the data store. Use the following command to see real-time usage of thin disk: du –h "Thindisk.vmdk" You can notice the big difference of disk usage between of Thin and Thick format disks. From Thin to Thick: vmkfstools –i "Thindisk.vmdk" -d zeroed