• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar

Yellow Bricks

by Duncan Epping

  • Home
  • Unexplored Territory Podcast
  • HA Deepdive
  • ESXTOP
  • Stickers/Shirts
  • Privacy Policy
  • About
  • Show Search
Hide Search

C# Client is officially dead…

Duncan Epping · May 19, 2016 ·

Many of you have seen the news by now, yesterday VMware announced that the Windows vSphere Client, usually referred to as the C# Client, is dead. Yes indeed, it has been declared dead and going forward will no longer be made available for future release of vSphere. Now this means that it is still available for all releases out there today (up to 6.0) and it will of course stick to the standard support period.

I have always loved the C# Client, but I don’t have mixed feelings on this one… It needs to go, it has been dead for a long time but it was still walking, it is time for a change and time we put it to rest once and for all. Yes it will be painful for some, but I believe this is the only way to move forward.

That also means for you, the admin / consultant, that there needs to be an alternative. Well one has been in the making for a while and that is the HTML-5 based “Host Client”. The Host Client started out as a fling, but as of vSphere 6.0 U2 is part of the default install of ESXi. Personally I really like the client and I can’t wait for it to be feature complete. What I probably like most, besides the slick interface and the speed, is the fact that you can access it from anywhere and that the developers are out there waiting for feedback and ready to engage and improve on what they released. It gets updated very frequently, just visit the Fling’s page (version 8.1 is up there right now) and if you have feedback engage with the engineers through the fling page, or simply drop a note on twitter to Etienne.

But that’s not it, VMware has also shown that it has the intention to get rid of Flash from the Web Client… Again released as a fling and you can download it and try it out as well, next to the regular Web Client. It was recently updated to version 1.6 and believe me when I say that these developers and the PM are also constantly looking for feedback and ways to improve the experience. The message was loud and clear over the past couple of years and they are doing everything they can to improve the Web Client experience, which includes performance and just generic usability aspects.

I would like to ask everyone to try out both the Host Client and the HTML-5 Web Client and leave feedback on those fling pages. What’s working, what is not, what about performance, different devices etc. And if you have strong feelings about the announcement, always feel free to leave a comment here, or on the announcement blog, as PM and Dev will be reading and commenting there where and when needed.

600GB write buffer limit for VSAN?

Duncan Epping · May 17, 2016 ·

Write Buffer Limit for VSANI get this question on a regular basis and it has been explained many many times, I figured I would dedicate a blog to it. Now, Cormac has written a very lengthy blog on the topic and I am not going to repeat it, I will simply point you to the math he has provided around it. I do however want to provide a quick summary:

When you have an all-flash VSAN configuration the current write buffer limit is 600GB. (only for all-flash) As a result many seem to think that when a 800GB device is being used for the write buffer that 200GB will go unused. This simply is not the case. We have a rule of thumb of 10% cache to capacity ratio. This rule of thumb has been developed with both performance and endurance in mind as described by Cormac in the link above. The 200GB that is above the 600GB limit of the write buffer is actively used by the flash device for endurance. Note that an SSD usually is over-provisioned by default, most of them have extra cells for endurance and write performance. Which makes the experience more predictable and at the same time more reliable,  the same applies in this case with the Virtual SAN write buffer.

The image at the top right side shows how this works. This SSD has 800GB as advertised capacity. The “write buffer” is limited to 600GB however the white space is considered “dynamic over provisioning” capacity as it will be actively used by the SSD automatically (SSDs do this by default). Then there is an additional x % of over provisioning by default on all SSDs, which in the example is 28% (typical for enterprise grade) and even after that there usually is an extra 7% for garbage collection and other SSD internals. If you want to know more about why this is and how this works, Seagate has a nice blog.

So lets recap, as a consumer/admin the 600GB write buffer limit should not be a concern. Although the write buffer is limited in terms of buffer capacity, the flash cells will not go unused and the rule of thumb as such remains unchanged: 10% cache to capacity ratio. Lets hope this puts this (non) discussion finally to rest.

Partition / Isolation and VM flip flopping between hosts?

Duncan Epping · May 16, 2016 ·

Last week I was talking to one of our developers at our R&D offsite. He has a situation where he saw his VM flip flopping between two hosts when he was testing a certain failure scenario and he wondered why that was. In his case he had a 2 node cluster connected to vCenter Server and a bunch of VMs running on just 1 host. All of the VMs were running off iSCSI storage. When looking at vCenter he literally would see his VMs on host 1 and a split second later on host 2, and this would go on continuously. I have written about this behaviour before, but figured it never hurts to repeat it as not everyone goes back 2-3 years to read up on certain scenarios.

In the above diagram you see a VM running on the first host. vCenter Server is connected to both hosts through Network A and the Datastore being used is on Network C and the host management network is connected through Network B. Now just imagine that Network B is for whatever reason gone. The hosts won’t be able to ping each other any longer. In this case although it is an isolation, the VMs will have access through the central datastore and depending on how the isolation response is configured the VMs may or may not be restarted. Either way, as the datastore is still there, even if isolation response is set to “disabled” / “leave powered on” the VM will not be restarted on the second host as the “VM” is locked through that datastore, and you cannot have 2 locks on those files.

Now if simultaneously Network B and C are gone, this could potentially pose a problem. Just imagine this to be the case. Now the hosts are able to communicate to vCenter Server, however they cannot communicate to each other (isolation event will be triggered if configured), and the VM will lose access to storage (network C is down). If no isolation event was configured (disabled or leave powered on) then the VM on the first host will remain running, but as the second host has noticed the first host is isolated and it doesn’t see the VM any longer and the lock on those files are gone it is capable of restarting that VM. Both hosts however are still connected to vCenter Server and will send their updates to vCenter Server with regards to the inventory they are running… And that is when you will see the VM flip flopping (also sometimes referred to as ping-ponging) between those hosts.

And this, this is exactly why:

  1. It is recommend to configure an Isolation Response based on the likelihood of a situation like this occurring
  2. If you have vSphere 6.0 and higher, you should enable APD/PDL responses, so that the VM running on the first host will be killed when storage is gone.

I hope this helps…

Vote now for your fav VMworld sessions and Virt Blogs!

Duncan Epping · May 5, 2016 ·

Time to get voting again. Eric Siebert just published the new list of Top Blogs to vote for. I’ve been honoured to have won a couple of years in a row, but with so many great blogs on the list that is never a given. Personally I just put in my votes, I am not going to tell you who I voted for this year as I don’t want to influence anyone. I hope I produced sufficient useful content again this year for you guys to considering voting for me. I am not going to point you to my articles, as most of you will have fav articles and know what you appreciate and don’t appreciate. Vote here: http://vsphere-land.com/news/voting-now-open-for-top-vblog-2016.html

Also, voting for VMworld is open. I would like to ask you guys to considering voting for the sessions I will be part of. Here is a list of the sessions, and if they sound interesting please consider voting:

  • Ask the Expert vBloggers [7515] (Rick Scherer, Chris Wahl, Chad Sakac, Derek Seaman, Duncan Epping)
    Back for it’s 9th year at VMworld, Ask the Experts is back with an awesome panel of the industries top bloggers. In this session there are no powerpoints, no sales pitches and no rules! Experts in the industry are here to answer the audiences questions while having some fun in the process. Bring your topic, anything from Software-Defined Data Center, End-User Computing, Cloud Native Applications to Hybrid Cloud…Storage, Networking, Security, Applications. No Holds Barred and No Questions are Off Limits!
  • Enforcing a vSphere Cluster Design with PowerCLI Automation [8036] (Chris Wahl – Duncan Epping)
    The amount of vSphere data center, cluster, storage, and network options available to an administrator are massive. Even specific features such as High Availability (HA) and the Distributed Resource Scheduler (DRS) have a ton of different configuration settings provided to meet the needs of your specific virtualized workloads. It can be a challenge, however, to audit the settings and best understand why they were set in the first place – especially as other administrators join and leave your organization! Join VMware’s Duncan Epping, author of the infamous Cluster Deep Dive series, along with Rubrik’s Chris Wahl, PowerShell MVP and author of Networking for VMware Administrators, as they take a look at how to abstract vSphere configuration settings into declarative configuration files. Learn how to audit, track, and enforce consistent settings – with notes and comments – to ensure the availability and standardization of your vSphere environment.
  • Software Defined Storage @ VMware Primer [7650] (Lee Dilworth – Duncan Epping)
    In this session Lee and Duncan will give an overview of the different VMware Software Defined Storage initiatives and how these fit in to the broader SDDC picture. They will cover Virtual Volumes, Virtual SAN and the vSphere APIs for IO Filtering. For each of these 3 they will explain customer use cases and go over some of the basic concepts providing you with a good understanding of how to apply this to your environment.
  • A day in the life of a VSAN I/O [7875] (John Nicholson – Duncan Epping)
    In this session Duncan and John will discuss what a typical day looks like in the life of an I/O (on a VSAN based solution). How does network based RAID-1 or RAID-5 work? Where does checksumming occur? When and how are blocks deduplicated or compressed? What about caching, are there different layers? Can I control where blocks are stored? And how does all of this influence availability and performance of my I/O?
  • Hyperconverged Infrastructure Panel – Deep Dive Review of Solutions [7765] (Stu Miniman, Steve Poitras, Jesse St Laurent, Duncan Epping)
    The hyperconverged infrastructure market has exploded over the last few years. The good news is there’s lots of choice; the bad news is there’s lots of choice. How do you navigate the vendors and solutions landscape? What are they key evaluation criteria? Join us for a moderated panel discussion with a distinguished group of hyperconvergence experts to examine and discuss the challenges IT organizations are facing with virtualization infrastructure and how hyperconverged infrastructure is playing a dramatic role in the evolution of the data center. The panel will answer your questions on topics such as what constitutes hyperconvergence in the converged infrastructure landscape; business and technical benefits of this data center technology; scenarios to leverage hyperconvergence in your organization; how to avoid traps that could derail hyperconvergence implementation; and others posed by the audience.

Thanks and hope to see you guys at the event, either US or EMEA!

How HA handles a VSAN Stretched Cluster Site Partition

Duncan Epping · Apr 25, 2016 ·

Over the past couple of weeks I have had some interesting questions from folks about different VSAN Stretched failure scenarios, in particular what happens during a VSAN Stretched Cluster site partition. These questions were in particular about site partitions and how HA and VSAN know which VMs to fail-over and which VMs to power-off. There are a couple of things I like to clarify. First lets start with a diagram that sketches a stretched scenario. In the diagram below you see 3 sites. Two which are “data” sites and one which is used for the “witness”. This is a standard VSAN Stretched configuration.

How HA handles a VSAN Stretched Cluster Site Partition

The typical question now is, what happens when Site 1 is isolated from Site 2 and from the Witness Site? (While the Witness and Site 2 remain connected.) Is the isolation response triggered in Site 1? What happens to the workloads in Site 1? Are the workloads restarted in Site 2? If so, how does Site 2 know that the VMs in Site 1 are powered off? All very valid questions if you ask me, and if you read the vSphere HA deepdive on this website closely and letter for letter you will find all the answers in there, but lets make it a bit easier for those who don’t have the time.

First of all, all the VMs running in Site 1 will be powered off. Let is be clear that this is not done by vSphere HA, this is not the result of an “isolation” as technically the hosts are not isolated but partitioned. The VMs are killed by a VSAN mechanism and they are killed because the VMs have no access to any of the components any longer. (Local components are not accessible as there is no quorum.) You can disable this mechanism by the way, although I discourage you from doing so, through the advanced host settings. Set the advanced host setting called VSAN.AutoTerminateGhostVm to 0.

In the second site a new HA master node will be elected. That master node will validate which VMs are supposed to be powered on, it knows this through the “protectedlist”. The VMs that were on Site 1 will be missing, they are on the list, but not powered on within this partition… As this partition has ownership of the components (quorum) it will now be capable of powering on those VMs.

Finally, how do the hosts in Partition 2 know that the VMs in Partition 1 have been powered off? Well they don’t. However, Partition 2 has quorum (Quorum meaning that is has the majority of the votes / components (2 our of 3) and as such ownership and they do know that this means it is safe to power-on those VMs as the VMs in Partition 1 will be killed by the VSAN mechanism.

I hope that helps. For more details, make sure to read the clustering deepdive, which can be downloaded here for free.

  • « Go to Previous Page
  • Page 1
  • Interim pages omitted …
  • Page 111
  • Page 112
  • Page 113
  • Page 114
  • Page 115
  • Interim pages omitted …
  • Page 502
  • Go to Next Page »

Primary Sidebar

About the Author

Duncan Epping is a Chief Technologist and Distinguished Engineering Architect at Broadcom. Besides writing on Yellow-Bricks, Duncan is the co-author of the vSAN Deep Dive and the vSphere Clustering Deep Dive book series. Duncan is also the host of the Unexplored Territory Podcast.

Follow Us

  • X
  • Spotify
  • RSS Feed
  • LinkedIn

Recommended Book(s)

Also visit!

For the Dutch-speaking audience, make sure to visit RunNerd.nl to follow my running adventure, read shoe/gear/race reviews, and more!

Do you like Hardcore-Punk music? Follow my Spotify Playlist!

Do you like 80s music? I got you covered!

Copyright Yellow-Bricks.com © 2026 · Log in