WilliamLam.com

  • About
    • About
    • Privacy
  • VMware Cloud Foundation
    • VMware Cloud Foundation 9.1
    • VMware Cloud Foundation 9.0
  • VKS
  • Homelab
    • Hardware Options
    • Hardware Reviews
    • Lab Deployment Scripts
    • Nested Virtualization
    • Homelab Podcasts
  • VMware Nostalgia
  • Apple
You are here: Home / NSX / Bypassing the ESX Tunnel Endpoint (TEP) 1600 MTU Check in the VCF Installer

Bypassing the ESX Tunnel Endpoint (TEP) 1600 MTU Check in the VCF Installer

01.29.2026 by William Lam // 2 Comments

Before deploying a new VMware Cloud Foundation (VCF) 9.0 environment, the VCF Installer performs a number of validations including network MTU. The minimum MTU that is required to deploy VCF is 1600, which is used for the Tunnel Endpoint (TEP) for NSX traffic between your ESX hosts.

For most environments, this is not an issue and users will typically deploy VCF with Jumbo Frames enabled and configure the MTU with value of 9000. If your environment does not meet the minimum MTU requirement, the VCF Installer will flag this as an error and prevent you from deploying as shown in the screenshot below.


If you can not meet the MTU requirement, you can bypass the validation check so that you can continue with your deployment of the VCF Management Domain.

Step 1 - SSH to the VCF Installer using the vcf user and then run the following two commands:

sudo echo "validation.disable.network.connectivity.check=true" >> /etc/vmware/vcf/domainmanager/application.properties 
sudo echo "nsxt.mtu.validation.skip=true" >> /etc/vmware/vcf/domainmanager/application.properties

Step 2 - Restart the VCF Installer services for the changes to go into effect by running the following command:

echo 'y' | /opt/vmware/vcf/operationsmanager/scripts/cli/sddcmanager_restart_services.sh

Once the VCF Installer services has successfully restarted, you can re-run the validation and it should now allow you to proceed with the deployment.

Categories // NSX, VMware Cloud Foundation Tags // VCF 9.0

Comments

  1. *protectedgabesvirtualworld says

    01/29/2026 at 12:24 pm

    Been struggling with this together with VMware Support but we couldn't solve it. But then suddenly the install wizard allowed me to acknowledge them as warnings instead of faults.

    Today I wiped the whole VCF9 and ESX hosts because of an other issue and again was halted at this point. Finally I decided to deploy through API. After checking the JSON with "$url/v1/sddcs/validations" and seeing that only the MTU size is the last remaining issue, you can force the installation with "$url/v1/sddcs?skipValidations=true".

    But your solution is much easier 🙂

    Reply
  2. *protectedMark says

    04/27/2026 at 6:45 pm

    Thanks for sharing this! By the way does this also work when adding subsequent workload domain?

    Reply

Thanks for the comment!Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Search

Thank Author

Author

William is Distinguished Platform Engineering Architect in the VMware Cloud Foundation (VCF) Division at Broadcom. His primary focus is helping customers and partners build, run and operate a modern Private Cloud using the VMware Cloud Foundation (VCF) platform.

Connect

  • Bluesky
  • Email
  • GitHub
  • LinkedIn
  • Mastodon
  • Reddit
  • RSS
  • Twitter
  • Vimeo

Recent

  • AMD Zen4/Zen5 IPMI Thermal Driver for ESX Fling 05/01/2026
  • Quick Tip: High CPU Utilization on ESX due to Slow Entropy from AMD Zen 4 CPUs 04/29/2026
  • Automating VCF 9.0 Single Sign-On (SSO) with OIDC-based Identity Provider 04/10/2026
  • Automating Lab Optimizations for Post-Deployment of VMware Cloud Foundation (VCF) 04/06/2026
  • Maximizing vSAN ESA Performance on Minisforum MS-A2 03/31/2026

Advertisment

Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.

To find out more, including how to control cookies, see here: Cookie Policy

Copyright WilliamLam.com © 2026

Loading Comments...