Ometa
Contributor
Contributor

Host is disconnected on Vcenter and refuse to connect (ESXi4)

One of the the Host (running on Hp Proliant Dl 570)  with ESXi4 is disconnected and refuse to connect to the vcenter. I was try to reboot the server. From now, I 'm able to ping the server, connect over ssg, but not over Http and Https. All attemps reconnect failed. From Vcenter, when I try to add the same Ip address, I got the error " Call Datacenter.queryconnection failed.

I need you assistance.

Thank you

0 Kudos
38 Replies

then why dont you try from vc console....importing...

Regards, ABFS
0 Kudos
Ometa
Contributor
Contributor

From the critical ESXi Host, I can only ping and make an SSH; no Http or https are available., no possible to connect

0 Kudos
Ometa
Contributor
Contributor

Not possible to import over the VC Console

0 Kudos

dude, is that datastore shared? if yes nice....remove those vm's from inventory and add the vms in the inventory by browsing the vmx file from the datastore where they are located. OR you can import it, but shutdown your esx host before doing this...

Regards, ABFS
0 Kudos
Ometa
Contributor
Contributor

We have a Hp SAN Storage and the datastore is not shared

0 Kudos

oh!............manually copy those vm's to the datastore which is connected to the desired host where you are going to move them...

Regards, ABFS
0 Kudos
onestop
Contributor
Contributor

FYI: I am just trying to get your critical ESXi back online, where as other gentleman attempting to restore your VM's. Just to be clear.

Could you please run this for me "chkconfig --list" on the critical host.

0 Kudos
Ometa
Contributor
Contributor

Here is the output

~ # chkconfig --list
DCUI           on
TSM-SSH        off
TSM            off
usbarbitrator  on
lbtd           on
storageRM      on
sensord        on
vprobed        on
vobd           on
wsman          on
slpd           on
sfcbd-watchdog on
sfcbd          off
ntpd           on
hostd          on
iked           off
lwiod          off
netlogond      off
lsassd         off
vmware-aam     on
.#vmware-aam   off
vmware-vpxa    on
~ #

0 Kudos
onestop
Contributor
Contributor

Thanks. If you compare /etc/opt/vmware/vpxa/vpxa.cfg between 'working' and 'critical', do you see any differences other than the hostkey ? You don't need to send me the output, but let me know the result.

Try /etc/opt/init.d/vmware-vpxa restart, and then paste latest log from /var/log/vmare/vpx/vpxa-xxx.log

0 Kudos
Ometa
Contributor
Contributor

Hello,

All the configuration are the same on vpxa.cfg. You will find attached some log generated on the critical node. When I launch chkconfig --list , the difference is on critical node tsm -ssh and tsm are off, and those parameters are on on the good host. How can I enable tsm-ssh and tsm on the critical node.

Thanks

0 Kudos
jmerchan
Contributor
Contributor

We have same problem on one host HP DL 380 G5 with ESXi 4.1.0 build 260247, the other host works normally

we only can reboot

¿some feedback?

0 Kudos
Ometa
Contributor
Contributor

Hi ,

How many server have you on the critical host? and what is the current status for those servers?

0 Kudos
jmerchan
Contributor
Contributor

two Windows 2003 Servers

what do you mean with status?

Now they are running, we reboot host yesteday

one detail is we dont't have ssh access to host when it disconnects from vcenter

It's as hostd and vpxa daemons on this host go down at the same time and the last solution is to reboot host

0 Kudos
Ometa
Contributor
Contributor

You need to rebuild this host and reconnect it again on  your cluster

After this step, please install all patches and firmware on those two hosts.

Thanks

0 Kudos
jmerchan
Contributor
Contributor

do you mean reinstall host?

and why this problem is not on others hosts?

0 Kudos
Ometa
Contributor
Contributor

Yes, You need to reinstall the host.

Did you make any change on the current host?

0 Kudos
RR9
Enthusiast
Enthusiast

http://kb.vmware.com/kb/1016262

your host might be out of memory.. check this KB  this issue is known.

0 Kudos
jmerchan
Contributor
Contributor

sorry but we have ESXi 4.1, not ESXi 4.0

and we don't add, remove and re-add the host to vcenter

0 Kudos
jmerchan
Contributor
Contributor

no changes on host

now we want to update hostd & vpxa config files to increase size logs so we don't have logs of the day of failure. then we will wait to a new failure and see logs

0 Kudos