Comments on: Resolution – ESX hosts unexpected disconnect from Virtual Center ( ESX 3.5 update 2 )

By: craig

craig — Tue, 06 Sep 2011 02:05:16 +0000

Hi chris, theoritically it shouldn’t drop any vm traffic but when come to missiom critical always minimize the risk as much as possible, that is my thought

By: Allen White

Allen White — Mon, 05 Sep 2011 13:53:36 +0000

all, we had this issue on esxi 4.5 try the managment service restart
http://www.techieshelp.com/esxi-host-disconnected-in-vcentre/

By: Chris B

Chris B — Mon, 01 Nov 2010 13:46:03 +0000

Thanks for this information. I would just like to confirm that when i issue the command “mgmt-vmware restart” on the ESX console, this will not drop any of my vm guests right? Theoretically they should continue working as normal?

Chris

By: Sharp Admin

Sharp Admin — Fri, 27 Nov 2009 20:51:41 +0000

You should also check out if scratch and / directory has enough space left. Sometimes it’s good to manually delete vpxuser by connecting directly in to the box with the client.

By: Willem

Willem — Tue, 16 Jun 2009 07:16:28 +0000

This one worked great!! thx

By: craig

craig — Tue, 11 Nov 2008 01:15:58 +0000

Hi Alexander, maybe your environment is different may have different impact. Yes, you do need to ensure the correct port and setting within the firewall if you have firewall in between on it. For my case, we do not have firewall within the LAN, the firewall is applied to external public network only. Thanks for your sharing, as it may be useful for all of us

By: Alexander Manfrin

Alexander Manfrin — Mon, 10 Nov 2008 21:04:34 +0000

Hi Craig, I has a problem like yours and found the solution looking to my firewall between networks.

By: Suresh

Suresh — Tue, 23 Sep 2008 17:35:03 +0000

I’ve had this problem a couple of times, and reconnecting the server doesn’t usually work either because it doesn’t recognize the authentication information. Restarting the Management Agent over the console fixes the problem and doesn’t bring down any services.

By: craig

craig — Sat, 30 Aug 2008 07:46:07 +0000

the meaning of turn off the HA and DRS will not impact to the way I manage my farm. I had not specified using resource pool with the farm, that is because I had not seen any bottleneck or performance issue with the environment I am current running, which I am using the R900 with 128 GB memory, and my environment is cross region within Asia, Europe and NA, that meant the peak hour for each VM is different.

agree with your point, is not who right or wrong here, is really a sharing basis about the different environment and different way we could manage the farm. the reason I turn it off just in case any bugs happen for the HA. Not really concern about the DRS actually. I experience before which I can’t reconfigure back the HA after I disable it. No matter how many time i tried. the only solution that time is really re image the entire ESX and it back to normal. So, just in case something go wrong on HA and force the VM to be failed over and incur down time, I prefer to disable the HA ensure no fail over will happen

By: justme

justme — Fri, 29 Aug 2008 22:54:54 +0000

Hi Craig,

I manage 70 esx host daily. So always make sure I don’t bring down a host with running VM’s.

I’m unsure how your way is safer, as you haven’t isolated the host from the VM’s running on it when it disconnected. All you have done is create more work for yourself by turning off HA & DRS. Why do I say that?

I assume cause you turned DRS off, your not using any resource pools? Cause once you turn off DRS, it removes all resource pools from the cluster. So when you turn DRS back on, you have to recreate these pools and settings again.

If you have nested pools and different settings this can take a while to recreate and then move each VM into the correct pool.

All these settings and placements need to be taken note before you turn off DRS!

Its not a your wrong I’m right. It was a different viewpoint of things for others who may have large DRS pools setup.