BedBB
Contributor
Contributor

Message Host not responding - bond 14 days

My environment consists of 4 Hosts with ESXServer 3.5 installed and1

Virtual Center 2.5 (physical machine Windows Server 2003).

HA and DRS enabled cluster set for the 4 Hosts. Number of host failures the cluster can tolerate 2.

The virtual center reports that 3 of the 4 hosts not responding.

4 Hosts and Virtual Center has connectivity. Respond by IP and by

name (DNS). Both the 4 hosts, as the Virtual Center can be accessed via

ssh and remote desktop.

Questions

The virtual center is an important feature that is not a point of

failure in your virtual infrastructure. Even if he fails to guarantee

the operation for a period of 14 days.

The fact that 1 (for 3) Host not respond to the Virtual Center involves opening score of the 14 days?

After 14 days, if restart occurs in 1 of 3 hosts that have multiple VM, what is the impact?

How to restore the connectivity between the hosts and Virtual Center?

It is enough, since the LAN is OK, the hosts command "service mgmt-vmware start" and restart the "network service"?

Thanks

/ Bed

0 Kudos
4 Replies
Troy_Clavell
Immortal
Immortal

it may be a name resolution issue. You can ping both shortname and FQDN of your ESX Hosts from and to each other as well as from and to you vCenter Server?

but if your 14 day grace period expires, you will not be able to power cycle any of your guests.

0 Kudos
BedBB
Contributor
Contributor

Hi Troy Clavell

The network and the DNS are OK.

From the VC or any of the 4 hosts can

"ping" the IP or the short name for any of them.

The virtual center ...

/ drivers / etc / host names short and long associated with the IPs are

correct.

Thanks

Bed

0 Kudos
mlubinski
Expert
Expert

1. this 14 days grace period is "active" when license server goes down (not virtual center) or connection to this server. So if your license server is running all the time (and hosts have connectivity to this license server) then

2. if your hosts disconnect often from VC (host not responding), then you could try to patch these servers (if are not patched), and if they have proper patching, then simply run: service mgmt-vmware restart and service vmware-vpxa restart and service vmware-vmkauthd restart

This should make "not connected" host to reconnect (if he responds to pings and can be accessed via ssh.

If you found this or any other answer useful please consider the use of the Helpful or correct buttons to award points

[I]If you found this or any other answer useful please consider the use of the Helpful or correct buttons to award points[/I]
Troy_Clavell
Immortal
Immortal