vpxd.log file constantly logs errors "no route to host" referring to the old vCenter Server address (before it was changed)

[Joris85]

Hello,

We are having troubles with configuring High Availability (https://communities.vmware.com/thread/496531), and I think this could be related to this issue.

In the vpxd.log file, we see contant logging of this error.

The system has 2 hosts, 1 vcenter appliance.

During setup, we needed to change the IP of the vCenter server from .133 to .143.

Now I see that in the vpxd-11.log file there are constantly erros being logged, referring to .133.

There are no issues on the platform (vMotion is OK, vCenter is OK), only with High Availability election we have a problem.

I checked both the vpxd.cfg files on both hosts, and they have no references to .133 (<Ip Server> and <Ip> are correct).

So please were is this reference coming from.

Any ideas, any checks I can do?

Best Regards,

Joris

[ExpletiveDelete]

you said that you changed the IP during setup, so this implies that nothing was connected to the vCenter appliance when you made the change?

have you checked the DNS server to verify the vCenter entry? is something replying from .133?

clear ARP and DNS cache and then run a tracert (or similar) to verify name resolution from vCenter.

Also, try adding an entry in the host file.

[Joris85]

Hello thank you for your response,

The IP address of vCenter server was changed while the vCenter was managing the Host.

There is no DNS Server.

Nothing is replying from .133

ARP table of ESX hosts is OK.

ARP table of vCenter is:

# arp -a

? (192.27.224.140) at 00:50:56:ad:77:cd [ether] on eth0

? (192.27.224.138) at 00:50:56:65:36:1d [ether] on eth0

? (192.27.224.133) at <incomplete> on eth0

? (192.27.224.139) at 00:50:56:68:40:62 [ether] on eth0

? (192.27.224.224) at <incomplete> on eth0

So this shows a non existing entry.

Host files on the ESX hosts is OK.

Host file on vCenter appliance, I have not been able to find out how to check it.

Best Regards,

Joris

[rxajoemorrison]

Did you ever resolve this?  I'm having a similar problem.  There was a network problem and the ESXi host had to be hard-rebooted.  The vcenter appliance is now unhappy.  Connecting to vcenter I see the same kind of arp entry, and I can't ping the esxi host from the vcenter appliance.  I can ping the host from other sources on that network, however.  Really strange.  The vcenter appliance can also ping other things.