NSX-T - Disk Space Requirements Not Met

Upgrading NSX-T in the lab, the Host Pre-Check came back with:

Disk space requirements not met. Please ensure 180MB free space is available in tmp partition to proceed with upgrade.

Horror Stories - The Oncer

Over the years you hear some great IT horror stories. Hopefully by sharing it, others can learn and have a good laugh. Names have been changed to protect the innocent.

VCF 4 Multi AZ Networking

In a VCF 4 multi AZ deployment, before stretching the cluster to AZ2, there’s some manual tasks required for the T0 to peer with the ToR switches in AZ2. The process is well documented in the NSX-T Data Center Configuration for Availability Zone 2 for the Management Domain in Region A on the VVD6 documentation pages.

VCF 4 - Failed to Validate the BGP Route Distribution

During a VCF 4 Bring-up of a single Management Domain, the validation tests passed all OK. But during the deployment, it failed during the NSX-T tasks, specifically on the “Verify BGP Route Distribution” - “Failed to validate the BGP Route Distribution result for edge with ID ”.

NSX-T 2.5.2 Release

On the 30th July, 2020, NSX-T 2.5.2 was released. Check out the release notes.

This is a minor update with almost 80 issues marked as fixed.

My VCAP-NV Design Exam Experience

Last month VMware released updated versions of some exams, including the VCAP-NV Design exam based on NSX-T 3.0. In the past year or so I’ve been working a lot more with NSX-T, but.. I’m not a real* networking guy, so I wasn’t confident in taking NV exams.

After passing the VCP-NV on NSX-T 2.4 earlier in the year, I put off the VCAPs because they were based on NSX-T 2.4 or NSX-v 6.x, but with the updated exam out, I was running out of excuses.

You might have heard there’s a pandemic going on, so doing exams remotely is the only option here, and suited me.

Upgrade to ESXi 7.0 Boot Disk Size Error

Finally getting around to upgrading to ESXi 7.0, and I was stuck pretty quickly, with the error: BOOT_DISK_SIZE ERROR.

NSX-T Troubleshooting Tunnel Status

Switching between a mix of different product versions, I forget some of the specifics, and I’ve wasted too much time troubleshooting something that was working OK. Hopefully this saves you some time.

Photon OS in the Lab

Here’s a few tips from what I do when deploying Photon OS in the lab. Keep in mind this is only for troubleshooting and testing, so don’t make the same changes to anything outside of your lab.

NSX-T: Deploy NSX-T Manager 2.5 with OVFtool

If you have the NSX-T Manager OVA on a fileshare or web server you can deploy it from the vCenter GUI, or use any other deployment tool like OVFtool.

Using OVFtool to deploy NSX-T Manager is a great way to deploy a quick and repeatable configuration. It also helps to document the configuration options.

NSX-T Troubleshooting: Compute Manager Already Registered with Another NSX Manager

After adding a compute manager, the Registration Status shows as Not Registered, and Connection Status is Down.

This is usually caused by a previously registered NSX-T Manager to vCenter, that has been deleted. If you remove the Compute Manager via the Delete option in NSX-T Manager, it also removes the registration from vCenter.

Deploying VMware Appliance for Folding@Home With OVFtool

Recently VMware released a Fling of the VMware Appliance for Folding@Home.

It’s great to see the VMware community coming together so quickly to help out.

As part of my love/hate relationship with OVFtool, here’s a few ways you can deploy the VMware Appliance for Folding@Home using OVFtool.


If you try and deploy vRA8 into VMware Cloud on AWS, you’ll get this error:

User has no administrative privileges

vRealize Network Insight (vRNI) Tips

More customers are embracing the suite of applications provided by VMware in managing their environment. I’m seeing customers with vRealize Network Insight (vRNI), but a lot still don’t appreciate all the things it can do.

NSX-v 6.4 End of Support Extended

For those with NSX-v 6.4, they’d know the end of general support date was 16/01/2021, (just over a year from now). If you check the product lifecycle it now shows the end of general support is 16/01/2022.

Product Lifecycle Matrix

Migrate2VCSA Error

When using the Migration Assistant to Migrate from a Windows 5.5 vCenter to 6.5 VCSA, the migration assistant was failing to run on the Windows vCenter server.

It automatically saves the logs on the desktop. When viewing the logs, this part stood out:

2019-07-22T00:31:58.193Z ERROR upgrade.states.component_states vcIntegrity:CollectRequirements: Remote script failed with an error [InternalError()]
2019-07-22T00:31:58.193Z ERROR upgrade.states.component_states vcIntegrity:CollectRequirements: failed with internal error. For details take a look at CollectRequirements_com.vmware.vcIntegrity_2019_07_22_10_31.log.
2019-07-22T00:31:58.209Z WARNING wf.wf_processor State CollectRequirements com.vmware.vcIntegrity has failed.

ESXi 'About to Install...' Hangs

During an upgrade from 5.5 to 6.5, update manager started to do the upgrade, but after the host rebooted, it would boot into the ESXi 6.5 installer, but then display About to install for 15 seconds, then flash an error message, and then go back to About to Install. Leaving it for a few hours didn’t make any difference, and I was unable to alt-F1 and log into the console, as when the error message flashed up, it would reset the login process.

vRNI 4.1 Insufficient capacity on each physical CPU

Deploying vRNI 4.1 you might get an error: Insufficient capacity on each physical CPU.

Insufficient capacity on each physical CPU

Using Ovftool

Ovftool can be pretty awesome, but it can also be very difficult to use. I seem to have a love/hate relationship with it.

Here I will go over some common issues I have with the tool. I’ve only tested on the Windows version of ovftool.

Migrate to Hugo

With plenty of unfinished drafts growing, I thought I’d procrastinate even more by jumping on the static website bandwagon. I’ve migrated from Blogger to Hugo, and hosted on AWS with CloudFront.

Unable to add vCenter to vRB – invalid credentials

A lot of people have probably never tried vRealize Business. As more companies want a cloud like charging model, or to show the true cost of VMs, interest in these tools is picking up.

Faking vCenter alarms

Larger environments tend to integrate their monitoring and ticketing systems. Some also add automated workflows based on alarms. The problem when setting up these workflows is how do you test the workflow is triggered based on specific alarms?

ESXi kickstart with Python

I recently spent some time building kickstart files. Something I hadn’t done much since 2008. The most noticeable change in the process is I’m older and fatter. I re/learnt a few things, and did my first ever python script.

2016 Australian / New Zealand vExperts

The list of 2016 vExperts was officially announced by VMware. This year sees a total of 1374 people awarded the title of vExpert. Australia / New Zealand represent 4.

Combining PowerCLI & ESXCLI to change PSP on a Large Scale

Using PowerCLI you can use Set-ScsiLun -MultipathPolicy “RoundRobin” to set the PSP, but I found it quite slow using it on a large scale. It would update one datastore on one host every 5 seconds.

2015 Australian / New Zealand vExperts

VMware announced the list of 2015 vExperts during the week. Congratulations to all that made it. The list now contains over 1,000 vExperts. For something perhaps a bit more relevant in the A/NZ region, I’ve broken it down for us.

Office Arguments – Maximum VMDK size is NOT 2TB-512bytes

…if you want to use snapshots Pop Quiz Q: What’s the maximum size VMDK you could create in vSphere 5.1 or earlier? A: Most people that have studied for VCP will know the maximum VMDK size is 2TB minus 512 bytes.

Maximum Disks Per SCSI Controller is NOT 15

Pop Quiz Q: What’s the maximum number of disks per SCSI Controller? A: It depends.. On your VCP exam, you would have said 15. Correct. Although if you want to clone or snapshot and quiesce a VM, the maximum is 7 disks per SCSI controller.

SRM – IP Customisation error

During an SRM (5.0) failover, a VM failed during the IP customisation failed at step 11. It was strange as we hadn’t seen this error in quite a while. 11. Power On Priority 3 VMs Error – Cannot complete customization, possibly due to a scripting runtime error or invalid script parameters (Error code: -1).