Search This Blog

Tuesday, October 26, 2021

VCP-DCV 2021

 I am very excited to have completed my 4th refresh of the VCP-DCV Certification on Oct 20th. I even passed with my highest score ever. 412.

I was fortunate enough to get a Tech+ Pass to VMworld 2021 gifted through the VMUG program and I vowed not to let it go to waste.

So after a brief discussion with my wife, I determined that I could complete 2 certification tests using the discounted vouchers between October 4th and November 4th.

One would be a VCP refresh and the other would be a VCAP-Deploy attempt.

I know some folks like stories, so here is how I prepped and passed this test in only 2 weeks.

Let me preface by saying the test was not at all 'easy'. I have now tested on 3 Major version of ESXI , 5.1 , 6.5 and 7.0

The older tests were very much focused on bare technical specifications, troubleshooting and detailed configuration tasks. The current test adds in so much more content for the "modern hybrid cloud datacenter". Trying to remember the technical, the troubleshooting and the configuration while ADDING information about technologies that you may not be seeing yet is no easy feat.

I was fortunate though that there had been an updated release of the Official Certification guide from Pearson. Where the prior guides were very heavy on screenshots and processes, this seemed to be just walls and walls of text. That is not to say that it is bad, it was extremely useful. The alternative is to RTFM on , according to the exam blueprint. At the least the Certification guide provided "Key Points" to narrow the focus a bit.

I read it cover to cover and found myself recharged when reading processes that I was familiar with.

Sometimes though, the best way to remember something is to see it done..

So I FIRED UP THE LAB.... and it died... hmmm.. probably should have swapped out that USB boot media when I had the chance. Probably will need to figure out how to recover vSAN with a lost host...

So I FIRED UP THE OTHER LAB ! And I performed an upgrade of the vCenter to 7.0.3!

I tried to upgrade the hosts, but the boot media on these were internal SD cards... error "not enough space for upgrade"

So I powered off and removed one of the blades to get a closer look at the SD cards. 2GB Mirror in the Dell M520 blades. 2GB?! ah , ok , wow.

So I slotted it back in with the intention of addressing that again later, and thats when one of the RAID controllers failed.

I only know that because I tried to refresh vCenter after repowering the blade and realized it was not loading. A quick look at the hosts showed why. The snapshot chain had become corrupt. Trying to commit the snapshots failed. Trying to consolidate the virtual machine, failed.

At least the domain controller survived..... nope. Black screen , restarted, crashed on boot. Direct to Windows recovery options. I could get into directory services restore mode, but no repairs would stick. Dang.

So vSAN lab is down,  Dell Lab is down.. This would be a great opportunity to learn some things... but I am short on time. 

So, on a prior recommendation from a friend and colleague , I checked out a 7 day trial of CBT nuggets. Fortunately they had an updated course for the VCP-DCV 2021 2V0-21.20 exam presented by Keith Barker. I wanted to see some specific topics so I jumped around a bit, but I did find Keiths style very engaging. More than a few times things didn't go 'as planned', sometimes this was on purpose , other times it was the lab he was using, but it was interesting that some of these things were left in.. because, honestly things do not always go right and it would be wrong to present only 100% success every time.

Ultimately I was able to salvage a domain controller from the vSAN lab, (host 2 is dead in the water though) ... 

I built a new vCenter and Domain controller on the Dell kit.

Read some more, watched Keith for a few hours, ran a couple of scenarios on my labs, ran a couple of scenarios on

Then, I got a good nights rest.

I went to the testing center, sat for the exam, second guessed myself a few times. Reviewed the questions that I had "marked" and determined that it was probably more harm than good to go back to them (it was only 9.. and of those 4 were marked because I thought I might need them)

I clicked the button to submit. AND BANG! Screen says congratulations.

Very relieved. I don't have to take it again, I can sit for the VCAP-DCV Deploy now... so it starts all over again..

Wish me luck on November 2nd!


Thursday, August 5, 2021

"INVALID" machines after vSAN shutdown.

 In some business environments or homelabs it may be necessary to shutdown a vSAN cluster entirely.

VMware has a proper procedure outlined on the documents site.

Shutting Down and Restarting the vSAN Cluster (

Once you have completed your maintenance tasks and fire everything up, you may be startled when you login to each of the hosts and attempt to verify your VMs....

They will probably all display as an "INVALID" status with the GUID Path in the "name" field.

fig.1 - Host 1 - 2 "invalid" machines

fig.2 - Host 2 - 2 "Invalid" machines

This message certainly caught one of my peers off guard during a recent datacenter update. That quick rush of butterflies in your gut that tells you all of your data is now corrupt.

However, I quickly reassured him that nothing was lost and the issue was simply that all of the hosts were still in maintenance mode.

When the vSAN nodes are in maintenance mode after a reboot, none of the stats are correct since none of the vSAN components are allowed to work together. 

fig.3 - 0Byte vsanDatastore

If you have powered on all of the vSAN nodes in the cluster and waited a sufficient amount of time for all the vSAN nodes to communicate, the remediation is actually quite swift.

Remove all the Hosts from Maintenance mode.

fig.4 - Host 2 - Still in Maintenance Mode!

The names will re-appear for each of the Guest objects.

fig.5 - Host 1 - Proper names!

fig.6 - Host 2 - Proper names again!

If all of your workload is on these hosts, you can start your DNS server, then the vCenter server.

fig.7 - vCenter operational again.

Before you know it , you are back in business.

Thursday, February 11, 2021

Congratulations to the vExperts!


Today , VMware released the names of new and returning vExperts for 2021.

vExpert 2021 Award Announcement

I was honored and humbled to be able to stay with this program for my 4th year.

I believe in the VMware eco system and have seen how transformational it has been in my business and I enjoy sharing stories and advice with others on the subject.

I was fortunate enough to join the VMUG in Denver at a great time and found a group of people that understood my language. After being a member for several years, I volunteered my time to hep organize and plan activities for the local groups along with 2 other amazing leaders. The planning and organization of the 2018 Denver UserCon was intense, but attending on the event day was awe inspiring. So many VMware enthusiasts that I spoke with that day thanked us for helping to provide them with so much information about the products and services that could help advance their careers and businesses.

I had to relocate for work to Orlando and immediately sought out the local chapter and immediately volunteered. Once again I found myself connected with passionate leaders and VMware advocates. I was fortunate enough to attend a few in person meetings before the pandemic fully took hold , and I am looking forward to the day that we can get together again.

I am looking for new ways to support and add to the community.

I have started this blog as a way of documenting things that I find interesting and new.

I am looking at the option to livestream some lab sessions.

I answer questions on the Spiceworks forums for those that find themselves in a bind.

Jason Valentine's SpiceWorks

Having access to a community that understands your needs and daily challenges is such a profound help and I am hopeful that I give as much  as I take.


Saturday, January 9, 2021

Updating the DNS Search domains and FQDN Hostname for an ESXi Host.

 Here is a quick tip for anyone that has deployed an ESXi host from a home network or received DHCP values that didn't match your intended configuration.

I deployed a machine that I want to use in my home lab, but my default Comcast domain is displayed as the FQDN.
I have already changed this in the DCUI , but it persists in the vSphere client.

The configuration is found on the default TCP/IP stack, Click Networking

Select the TCP/IP Stacks tab

the DNS configuration shows my Domain name as ,but my proper domain name is in the search domains box. Lets clean this up.

Edit the Default TCP/IP Stack - note the Domain name and Search Domain fields.

Update the Domain name and Search Domains fields to remove and replace the incorrect domain.

Refreshing the host client shows the updated values!

Hope it helps!


Reusing Disks from a Previous vSAN

 This post may be mostly relevant to home-lab builders, but if you have previously configured vSAN on the disks used in host, you may not be able to easily reuse them in a new vSAN.

Lets take a look at my specific use case.

I want to install vCenter 7 and I want to establish vSAN on the host during this process.

For this installation I am going to install on host ESX03 , I previously used the internal disks for a vSAN cluster, but I am upgrading from hybrid to all flash using a 1TB SSD that I recently acquired.

In the datastore part of the installer , I select "Install on a new vSAN cluster containing the target host"
This will create a standalone vSAN node, configuration of the cluster is completed later when additional hosts are added.

Once I get to the section to claim my disks, I can see that I only have one disk and it is the new 1TB disk. My existing 120GB drive does not appear.

On the host I can see that this 120GB disk does exist.

Selecting the disks shows me that there is an existing vSAN partition table. We need to clear this partition.

Select Actions -> Clear Partition Table

Note the warning, erasing this partition is destructive and will remove the data from the disk that is essential for the previous vSAN.
I know that I will not need that data, so I can proceed.

There are no partitions on the disk.

Refreshing the vCenter installer by going back and then forward again. I can now see my 120GB drive available to claim

I select my 1TB drive

and claim it for the capacity Tier. I can now proceed with the remainder of the vCenter deployment

Hope this helps someone 

Saturday, January 2, 2021

Probably a bright spot for HomeLabs in the ESXi 7.0 U1C release.

 I was looking up the release notes for the 7.0U1C update and spotted this bit of good news.

"With ESXi 7.0 Update 1c, you can use the installer boot option systemMediaSize to limit the size of system storage partitions on the boot media."

I remember this being a design consideration for the new stack that I was deploying at work. I needed to have more than 150GB for the boot media.

Considering that I have 512GB per host there, it probably doesn't make sense to use this new option...

but on my homelab with 24GB of RAM per host, or an embedded deployment in VMware workstation... this could save money and space.


Happy New Year!

 This year I am continuing my journey with VMware solutions and I want to share more with the community along the way.

I am currently studying to attempt the VCAP tests for DataCenter Design and Deploy.

I have an expanded homelab with some upgraded components and I will be doing some live streams as I study for the test. 


VCP-DCV 2021

 I am very excited to have completed my 4th refresh of the VCP-DCV Certification on Oct 20th. I even passed with my highest score ever. 412 ...