Recently, I have introduced a Cisco SG 300 switch in my home lab and with that the possibility to create VLANs. In the new network design, the vCenter Server was moved into a new management network. As a result, I needed to change the vCenter Server’s IP address.
It is home lab, so it is a full featured vCenter Server with options like: vSphere Update Manager, Auto Deploy, Syslog Collector and Dump Collector.
After changing the IP address, the first step was to rejoin the server to the Windows Domain and watch the result. This is what I got:
- ESXi hosts were disconnected. This was expected because the ESXi servers Management Interfaces has also been changed and were placed in the new Management network;
- No more vSphere Update Manager;
- No more Auto Deploy;
- No more Syslog- and Dump Collector.
For a moment, I considered rebuilding the vCenter Server from scratch. On the other hand, I was curious to find out if this issue could be resolved.
Reconnect ESXi hosts
In KB 1001493 “vCenter Server IP address change causes ESX hosts to disconnect” VMware support describes two methods to reconnect a ESX or ESXi host. The main reason for an ESXi host to disconnect is because they store the IP address of the vCenter Server in a configuration file.
For the first method you have to log in as root to the ESXi host. Under normal conditions, there is no shell access, most likely you have to login to the DCUI first to gain shell access.
For ESXi, navigate to the folder /etc/vmware/vpxa and with vi open the file: vpxa.cfg.
Search for the line that starts with: <serverIP> and the change this parameter to the new IP address of the vCenter Server.
Restart the management agents on the ESXI hosts with this command:
Return to the vCenter Server and restart the “VMware VirtualCenter Server” Service.
The second method describes how to Disconnect and Reconnect an ESXi host with the vSphere Client.
vSphere Update Manager
Now my ESXI hosts are reconnected it is time to repair the vSphere Update Manager (VUM). In KB 101322 “Changing the vCenter Update Manager IP address and preserving the Update manger setup”. This KB article starts with this quote “The article is intended for users whose Update Manager and vCenter Server instances are running on different machines, and describes how to change the Update Manager IP address. This document does not deal with changing the vCenter Server IP address.”
Well, let us see if this KB can help and follow the steps in the KB:
- Log in to the machine on which Update Manager is installed. In our case the same vCenter server;
- In Windows Explorer navigate to the Update Manager installation folder.
For vCenter Server 5 on 64-bit Windows, this means go to:
C:\Program Files (x86)\VMware\Infrastructure\Update Manager
- Edit file extension.xmlin any text editor (notepad will do) to find and replace each instance of the old vCenter Server IP address with the new IP address.
BTW 192.168.2.105 is the old IP address.
- Save and close the file.
- Open a command prompt window.
- Navigate to the Update Manager installation folder.The default path in 64-bit Windows is C:\Program Files (x86)\VMware\Infrastructure\Update Manager
- Run the following command for the changes to take effect:
vciInstallUtils.exe –vc <vc_ip> –port <vc_http_port> -U <user_name> -P <password> -S extension.xml -C . -L . -O extupdate<vc_ip> = vCenter Server new IP address. In case VUM runs on vCenter, “localhost” is sufficient;
<vc_http_port> = 80 Do not use 443;
<user_name> and <password> = An account to log in to vCenterServer;Note: In this command, the -O switch is the letter O, not the number 0.
Note: Do not forget to enter the periods after –C and –L
- Remember the VUM database uses a 32-bit DSN. Navigate to the folder:
and start: obcad32.exe.
- Go to the “System DSN” tab and select the VUM databases. Press the Configure button and walk through the steps.
- If the test is successful, it ends with
- Now start the “VMware vSphere Update Manager Service” service.
We also need to enable the “VMware vSphere Update Manger Extension”. As a result we receive this message: “There was an error connecting to VMware vSphere Update Manager – [vc5:443]. Fault.HostNotReacable.summary”.Luckily, the vCenter Service Status gives us a clue where to find a solution.
- Navigate to the folder: C:\Program Files (x86)\VMware\Infrastructure\Update Manager
- Open with notepad the file vci-integrity.xml and search for the parameter <vpxdLocation>, and replace old vCenter Server IP address with the new IP address.
- Now restart the “VMware vSphere Update Manager Service” service and enable the “VMware vSphere Update Manger Extension”. Now the Update Manger has returned under Solutions and Applications.
The vSphere 5 Documentation states that if the IP address of the vCenter Server changes, you must reregister Auto Deploy. Here is the link.
- Edit the setup file located at:
c:\ProgramData\VMware\VMware vCenter Auto Deploy\vmconfig-autodeploy.xml
and specify the new IP address.
- Run the autodepoy-register.exe command-line tool, specifying all required options.
autodeploy-register.exe -R -a <vc_ip> -p <vc_http_port> -u <user_name> -w <password> -s <setup-file-path>The parameters are almost equal as in the previous step using the vciInstallUtils.exe command. The <setup-file-path>= c:\ProgramData\VMware\VMware vCenter Auto Deploy\vmconfig-autodeploy.xml.
- Although, I received a warning, everything seems to be OK.
- Final step, enable the Auto Deploy Plug-in.
I have also found a nice KB on “Troubleshooting vSphere Auto Deploy”.
At this time my vCenter Service Status shows everything OK.
Before this IP change, I did not pay much attention to the Syslog- and Dump collector. Some more work needs to be done to get these running, I will report on that in a new post.
I hope this was helpful. As always, I welcome your comments.