vCenterServer Problem after IP Address change - Outgoing connection to the old IP

[normanm]

Hi,

I got some problems after I changed the IP Address of my vcenterserver version 5.0.0. I followed this blog http://blog.torh.net/2011/09/29/changing-name-on-a-vmware-vcenter-server/ and read some vmware kb articles. Finally i got problems with vcenter health status. But after reading this post http://communities.vmware.com/thread/226681 i can solve the problem and everything looked good. I could connect with vSphere Client and everything worked as expected.

Now i saw on the firewall that the vcenterserver tries to reach its old IP Address on Port 443. Netstat says the connection comes from java.exe.

After checking the log bundle, I found only entries in the log with the old IP Address/DNS Name in vcsupport-x-xx-xxxx-xx-xx\Inventory Service\logs\ds.log

[2012-03-29 12:18:23,426 pool-20-thread-200  INFO  com.vmware.vim.query.server.servlets.QueryServlet] Received new query request from 192.168.100.60
[2012-03-29 12:18:23,428 pool-18-thread-6470  INFO  com.vmware.vim.query.server.query.impl.ServiceImpl] Provider of type VASA not found
[2012-03-29 12:18:30,272 pool-20-thread-204  INFO  com.vmware.vim.query.server.servlets.QueryServlet] Received new query request from 192.168.100.60
[2012-03-29 12:18:40,591 pool-14-thread-4  ERROR com.vmware.vim.dataservices.provider.VcProvider] com.vmware.vim.vmomi.core.exception.InternalException: org.apache.http.conn.HttpHostConnectException: Connection to https://old.DNS.name:443 refused
[2012-03-29 12:18:40,591 pool-14-thread-4  WARN  com.vmware.vim.query.server.provider.impl.ProviderManagerServiceImpl] com.vmware.vim.query.server.provider.impl.ProviderManagerServiceImpl$FeedPump@5b0a5c37
com.vmware.vim.query.server.store.exception.UnauthorizedException: not connected
    at com.vmware.vim.query.server.provider.AbstractAtomPullProviderBase.checkFeed(AbstractAtomPullProviderBase.java:89)
    at com.vmware.vim.query.server.provider.impl.ProviderManagerServiceImpl$FeedPump.run(ProviderManagerServiceImpl.java:542)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
    at java.util.concurrent.FutureTask.run(FutureTask.java:138)
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98)
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    at java.lang.Thread.run(Thread.java:662)
[2012-03-29 12:19:01,591 pool-14-thread-4  ERROR com.vmware.vim.dataservices.provider.VcProvider] com.vmware.vim.vmomi.core.exception.InternalException: org.apache.http.conn.HttpHostConnectException: Connection to https://old.DNS.name:443 refused
[2012-03-29 12:19:01,591 pool-14-thread-4  WARN  com.vmware.vim.query.server.provider.impl.ProviderManagerServiceImpl] com.vmware.vim.query.server.provider.impl.ProviderManagerServiceImpl$FeedPump@5b0a5c37
com.vmware.vim.query.server.store.exception.UnauthorizedException: not connected
    at com.vmware.vim.query.server.provider.AbstractAtomPullProviderBase.checkFeed(AbstractAtomPullProviderBase.java:89)
    at com.vmware.vim.query.server.provider.impl.ProviderManagerServiceImpl$FeedPump.run(ProviderManagerServiceImpl.java:542)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
    at java.util.concurrent.FutureTask.run(FutureTask.java:138)
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98)
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    at java.lang.Thread.run(Thread.java:662)

Got someone an idea?

Thank you in advance!

Any help would be appreciated!

[vGuy]

Can you please check vCenter Server settings –> Runtime Settings --> Managed IP address is displaying the right IP.

[normanm]

Ok, I checked the setting. The Managed IP Address field is empty. Should I enter the IP Address? The Manual says something about multiple vcenterserver Server's.

■ Configure Runtime Settings

You can change the port number the server is using for communications. You can also change the vCenter Server ID and the vCenter Server Managed IP address. Usually, you do not need to change these settings, but you might need to make changes if you run multiple vCenter Server systems in the same environment.

I will try tomorrow to set the IP Address and see if it still connects to the old address.

[normanm]

So I set the Managed IP Address but the problem is still there.

[vGuy]

Normanm - I suggest to try to reboot the vCenter server if you have not already tried.

I suspect there maybe few files/processes which are still referencing the old IP and rebooting the server may refresh them...hth!

[normanm]

This was my first guess too. But unfortunately this didn't help. I even searched in all config files with an extra tool and looked for entries with the old IP Address and old DNS Name until I can't find anymore. After changing these files I restarted the server (also when I changed the Managed IP Address). The Windows Registry is also scanned for old entries. But it still attempt to connect to the old IP.

I have no idea what this could be.

[ESXi35]

Do you have any plugins that are registered with the vCenter server?

[normanm]

Thanks for your help vGuy. I solved the Problem now!

I found 4 things which I changed. So im not sure what solved the problem. I post all I did maybe some else will help this.

First I took a deeper look in the SQL Server 2008. It runs on the same machine. I have to say that im not a SQL Expert. The Database works in local mode. It is not configured to listen on a TCP Port. After some google I looked into the SQL Server Configuration Manager. Under SQL Server Network Configuration -> Protocols for MSSQLSERVER -> TCP/IP the old IP was still entered and I corrected this. For me the option "Enable" has the value "No".

After that I spend some time to double check Windows Registry. I still found some Keys with the old IP and I changed them to new IP Settings.

• HKEY_CURRENT_USER\Software\Microsoft\Ldp\Connection -> Server "xxx.xxx.xxx.xxx"
• HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\services\{BD1FC715-F655-4951-838B-87E60D784123}\Parameters\Tcpip  IP Address "xxx.xxx.xxx.xxx" and Gateway "xxx.xxx.xxx.xxx
• HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\services\{BD1FC715-F655-4951-838B-87E60D784123}\Parameters\Tcpip -> IP Address "xxx.xxx.xxx.xxx" and Gateway "xxx.xxx.xxx.xxx

After reboot the machine there is no connection attempt to the old IP. Problem solved!

Thanks for Help!

[vGuy]

Great!! And thanks for sharing your findings!