Avatar of MichaelBalack
MichaelBalackFlag for Singapore asked on

esxi VM moved to different clustered host in power off condition, why?

This is the same 2-node esxi 5.5 hosts setup for HA in my previous posted questions. 2 Volumes were made available from iscsi san storage. both esxi hosts can simultaneously access to both volumes. In volume 1, 2 VMs are stored, which 3 VMs are stored in volume 2.

Using vCenter, a cluster is formed to take care of the above 2 hosts and 5 VMs. I also configured the 2 VMs that stored in volume 1, hosted by esxi host 1; whereas, other 3 VMs hosted by esxi host 2.

Now, in order to test the cluster, I shut down the esxi host 1, I can see that 2 VMs from volume 1, are not hosted by esxi host 2, but, both VMs are in the power off state. Can I set in such the way that these VMs, while migrating, is in the power on state?

thanks in advance.
VMware

Avatar of undefined
Last Comment
MichaelBalack

8/22/2022 - Mon
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)

VMware HA - restarts VMs on a Host Failure.

otherwise, you will need to migrate the VMs off the host before shutting down!

Shutting down a Host is not a host failure, because it's controlled.

Just pull out the power cable to simulate a Host Failure.
ASKER
MichaelBalack

Okay, will try it tomorrow while onsite
Steve M

In case you don't like pulling the power cord on your server, you can also pull the Network cables, or disable the switch ports they are connected to initiate an HA failover (as long as host monitoring is enabled in HA).
I started with Experts Exchange in 2004 and it's been a mainstay of my professional computing life since. It helped me launch a career as a programmer / Oracle data analyst
William Peck
ASKER
MichaelBalack

Hi isk-ck,

Tried pull out the power cable, and all VMs failover with system reboot. Does this behaviour normal?

There are 3 nic in nic teaming configured in the same vswitch fot all vm. I pulled out alk 3cables, and there wasn't failover, why? The vm wasn't powered off
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)

CORRECT - VMware HA, RESTARTS the VMs on other HOSTS!

Completely Normal for VMware HA

They are not rebooted, they have failed......because the host has failed, so they are restarted on new hosts!
ASKER
MichaelBalack

Hi Hanccocka,

That means pulling out the cables doesn't trigger a failover?
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)

We normally test by pulling out the power.

VMs should then restart on other hosts.
ASKER
MichaelBalack

Hi Hanccocka,

How about if all the network ports/cables have  to take as well?
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)

Not quite sure I understand "How about if all the network ports/cables have  to take as well? "
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.
rwheeler23
ASKER
MichaelBalack

Hi Hanccocka,

That means if all the nic for vm are detected offline, can ha take care and trigger a failover?
ASKER CERTIFIED SOLUTION
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
See how we're fighting big data
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
SOLUTION
Log in to continue reading
Log In
Sign up - Free for 7 days
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
ASKER
MichaelBalack

Hi isk-ck,

Vcenter ran as a vm on one of the host. Ever tested that it was able yo failover to another host on power failure.
Steve M

If I understand correctly, when vcenter is a vm on a host, if it is on the same host that you pulled the nic cables from, then it would likely still be able to communicate with the one host and vm's on that same vSwitch, so likely a failover would not be initiated. I've never actually tested that, but it would make sense.

Is your vcenter guest on the same host that you unplugged the nics?
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
ASKER
MichaelBalack

Hi isk-ck,

I actually tried to pull cable of the host where vcenter wasn't located.
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)

VMware HA is conducted by the HA Agents on the Host Servers. vCenter Server is only used to configure VMware HA.

e.g. if the host fails, and vCenter Server is a VM, HA Agents control restarting....
Steve M

Ah thanks Hanccocka, I hoped it would be that way.

MichaelBalack; Using the vSphere WebClient, have you looked at the vSphere HA runtime information page?
(located by selecting your cluster, then monitor tab, then vSphere HA tab)

This page should show you if everything is configured - how many hosts are connected to the master, who is the master host, and what datastores are used for heartbeat, etc.

Maybe that will show something.
Experts Exchange has (a) saved my job multiple times, (b) saved me hours, days, and even weeks of work, and often (c) makes me look like a superhero! This place is MAGIC!
Walt Forbes
ASKER
MichaelBalack

Hi both,

Thanks for showing all the guidelines.

Hanccocka pointed a very good guide - vCenter is only used for configuring HA, it doesn't need to make ha work.

I suspect the problem lies on the vSwitches. vSwitch0 had configured for VM, Management; vSwitch1 had configured for IP Storage (iSCSI), Storage heartbeat, and vMotion. I think I should configure vMotion on vSwitch0 instead of current vSwitch1.

Please see few of my corrective works to be done:

        1. Configure correct IP in Software > DNS and routing; as both hosts are added-in in
            IP addresses. Put in the correct FQDNs in internal DNS server
        2. on vSwitch0, no default gateway is configured. I will configure it to point to switch
        3. Move vMotion VMkernal port group to vSwicth0
        4. Review Cluster settings for Host monitoring, and VM monitoring
   
As Isk-ck pointed out, there is no reason the ha failover didn't occurred for the following tests:

        a. pull the power cable of the host
        b. disconnect the network cables
        c. off the all NICs

I did checked through the cluster summary, not abnormality found.
SOLUTION
Log in to continue reading
Log In
Sign up - Free for 7 days
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)

Can you upload screenshots of networking?

Are your default gateways reachable or the isolation address.

Networking DNS default gateways all have to be correct eg DNS resolution and reverse DNS
ASKER
MichaelBalack

Hi hanccocka,

Please see the networking screenshots as attached.

On vSwitch0, default gateway/isolation address is not reachable or hence not defined
on vSwitch1, default gateway defined and pingeable.

DNS resolution and reverse DNs for  2 hosts? not defined

Would these be the root cause?
Networkings.docx
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)

The default gateway is that which is defined on your management interface

Eg ip address and hostname of host.
Can this be pinged from all hosts?
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)

Isolation address does not need to be the default gateway but usually is or can be any man interface which is reachable 24/7 but then must be specified also not having working DNS will not help
ASKER
MichaelBalack

Hi hanccocka,

Okay, I will put those needed settings when i am onsite tomorrow. Will update you guys about the progress...
Experts Exchange is like having an extremely knowledgeable team sitting and waiting for your call. Couldn't do my job half as well as I do without it!
James Murphy
ASKER
MichaelBalack

Hi hanccocka,

2 main changes I did: create a new VMkernel for vmotion on vSwitch0; and secondly, configure the DNS hosts and related IPs, and thirdly, change the default gateway.

Now, the testing on plugging off all the network cables, can triggered a host isolation, and subsequent a failover occurred.
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)

Very good, it's often network configuration which causes HA to fail, and not failover!

Glad it's fixed.
ASKER
MichaelBalack

Thanks a lot on both experts, that provided details info/leads to eventually got the problem resolved.
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.