Yellow Bricks

by Duncan Epping

vSAN File Services IPs not reachable when using NSX-T?

· · Leave a Comment

I’ve had this question a few times, if you enable vSAN File Services and you use NSX-T and it’s not possible to reach the vSAN File Service IP addresses, what should you do? In 999 out of the 1000 cases, it typically is a matter of enabling Mac Learning on the Segment Profile for the segment being used by vSAN File Services. I stole the below screenshot from William, it shows you how to enable it.

You may wonder why this needs to be enabled, well basically because the vSAN File Services VM is not what you are directly communicating with. The IP Address and MAC address you communicate with is associated with the vSAN File Service protocol stack container. As a result, MAC Learning needs to be enabled. I described this already in my FAQ post, but as it comes up frequently I figured I would dedicate a post to it.

Unexplored Territory #006: Event-driven automation (VEBA) with William Lam!

· · Leave a Comment

In this sixth episode, we talk to William Lam, Senior Staff Architect in the Cloud Infrastructure Business Group at VMware about event-driven automation. William explains what event-driven automation is, how customers are using it today, and why you should also consider trying out the VMware Event Broker Appliance! (https://flings.vmware.com/vmware-event-broker-appliance) Enjoy the episode, and if you haven’t done so yet, make sure to subscribe! You can also listen via your podcast apps of course for Apple: apple.co/3pxet9P Spotify: spoti.fi/3mW19dt Google: bit.ly/3pDoUJ3

Why does HA not power-on VMs after a full cluster shutdown?

· · 9 Comments

I received this question and figured I would write a quick post about it, as it comes up occasionally. Why does vSphere HA no power-on VMs after a full cluster is brought back online after a full cluster shutdown? In this case, the customer had a power outage, so their hosts and all VMs were powered off, by an administrator cleanly, as a result of the backup power unit running out of power. Unfortunately, this happens more frequently than you would think.

When VMs are powered off by an administrator, or anyone/anything (PowerCLI etc) else which has permissions to power off VMs, then vCenter Server will mark these VMs as “cleanly powered off”. Next, also the state of the VMs is tracked by vSphere HA. So if a host is powered off, HA will know if the VM was powered on, or powered off at the time the host goes missing.

Now, when the host (or hosts) returns for duty, vSphere HA will of course verify what the last known state was of the cluster. It will read the list of all the VMs that were powered on, and it will restart those that were powered on and are configured for HA. It will also look at a VM property called “runtime.cleanPowerOff”, this property indicates if the VM was cleanly powered off by an Admin or a script, or if the VM was for instance powered off by vSphere HA itself. (PDL response etc.) Depending on the value of the property, the VM will, or will not be restarted.

Having said all of that, when you power off a VM manually through the UI, or via a script, then the VM will be marked as being “cleanly powered off”. This means that HA has no reason to restart it, as the powered-off VM is not the result of a host, network, or storage failure.