Hi,
After upgrade from 5.1 to 6, the host lost communication with others hosts on the same vmware cluster. So I decided rollback to 5.1, but the problem persists.
I have many servers on the same lan (storage, esxi), but only can't ping to esxi hosts that are part of the same vmware cluster... It's very strange...
The vmware esxi servers in the cluster are 4: A, B, C, D
ping from A to B, C or D doesn't work
ping from B, C, or D to A doesn't work
ping between B, C or D work like a charm....
ping from any vm inside A to any host on lan work like a charm...
arp table on hosts BCD has the mac address of A
arp table on host A don't have mac address of B, C or D
It's seems to be an arp problem, but i can't add entries to the arp table in 5.1.
Anyone knows what could be the problem ?
Regards
I found the solution.
1) Put the host in maintenance mode
2) Remove the host from cluster
3) Restart the host (When the host boot ping starts to respond)
4) Add host to the cluster
I tested this after upgrade 5.0 to 5.1
If it's an arp issue have you tried clearing the arp-cache on the physical switch?
Beware, this could cause a temporary networking issue, depending how fast your switch can rebuild the updated cache.
From other host outside the cluster I have ping to this esxi...
The networking team says that they can't clear arp, because the traffic is inside a vlan...
I will try 2 things:
- Remove the host from cluster for 2 hours to stop the connections attempts between hypervisors (HA), so, if the problem is arp, 2 hours could be sufficient to clear any entry...
- Change mac addres of the network adapter (I don't know if is possible)
1. You can clear ARP related only this host (ip )
2. you can clear the network settings on the server and create new configuration .
3. configure new vmkernel port ,configure and check its communication or not / vmotion
I found the solution.
1) Put the host in maintenance mode
2) Remove the host from cluster
3) Restart the host (When the host boot ping starts to respond)
4) Add host to the cluster
I tested this after upgrade 5.0 to 5.1