--- title: Circular Dependencies, VMware NSX-T Edition «... description: A critical look at VMware's official NSX-T documentation for deploying NSX Manager on top of the N-VDS virtual switch it manages — a circular dependency that... canonical: https://daily.dev/posts/circular-dependencies-vmware-nsx-t-edition-ipspace-net-blog-omafwfglv twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Circular Dependencies, VMware NSX-T Edition « ipSpace.net blog | daily.dev og:description: A critical look at VMware's official NSX-T documentation for deploying NSX Manager on top of the N-VDS virtual switch it manages — a circular dependency that... og:url: https://daily.dev/posts/circular-dependencies-vmware-nsx-t-edition-ipspace-net-blog-omafwfglv og:image: https://api.daily.dev/og/posts/OmAfwfGLV.png og:image:alt: Circular Dependencies, VMware NSX-T Edition « ipSpace.net blog og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Circular Dependencies, VMware NSX-T Edition « ipSpace.net blog **[ipSpace.net Blog](https://daily.dev/sources/ipspace)** · 4 min read · 0 upvotes · 0 comments ## Summary A critical look at VMware's official NSX-T documentation for deploying NSX Manager on top of the N-VDS virtual switch it manages — a circular dependency that results in a 17-step procedure (with 10 sub-steps in the last step alone) involving manual JSON editing and curl commands. The author highlights the core problem: if all hosts reboot due to a power failure, the management VM port initializes in a blocked state, effectively bricking the cluster. The post argues VMware should have provided a one-click automated solution with proper rollbacks instead of a fragile manual process, and notes that with vSphere 7.0 and NSX-T 3.1, a simpler VDS-based approach exists that makes the convoluted N-VDS procedure largely unnecessary. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What happens to a VMware NSX-T cluster on N-VDS if all hosts reboot after a power failure? If all four hosts in a single-cluster N-VDS configuration reboot after a power failure, the NSX management VM port initializes in a blocked state, effectively bricking the cluster. This is a documented caveat in VMware's own NSX-T 3.1 installation guide, and recovering from it requires following ten manual sub-steps involving JSON editing and curl commands. _Engineers running NSX-T on N-VDS track failure scenarios and recovery procedures on daily.dev._ ### Is there a simpler alternative to deploying NSX-T on N-VDS in vSphere 7.0? Yes. With vSphere 7.0 and NSX-T 3.1, NSX-T can run on vSphere Distributed Switches (VDS) in parallel with legacy DVS port groups using the same uplinks, which is significantly simpler. VMware's own documentation added a note acknowledging this, making the complex N-VDS procedure largely a legacy path for environments still running ESXi 6.7. _VMware infrastructure teams navigating NSX-T upgrade paths share findings on daily.dev._ ## Similar posts on daily.dev - [Configuring Management IP Addresses to Virtual Network Devices « ipSpace.net blog](https://daily.dev/posts/configuring-management-ip-addresses-to-virtual-network-devices-ipspace-net-blog-ffffzfuyz) · ipSpace.net Blog · 0 upvotes · 0 comments - [Isovalent Networking for Virtualization: migrate VMs without breaking the network](https://daily.dev/posts/isovalent-networking-for-virtualization-migrate-vms-without-breaking-the-network-y4wmyjjvk) · Isovalent · 0 upvotes · 0 comments - [Technology Short Take 189](https://daily.dev/posts/technology-short-take-189-lwjrmfox1) · Scott's Weblog · 0 upvotes · 0 comments - [Amazon EVS now supports multiple VMware NSX Edge Gateways](https://daily.dev/posts/amazon-evs-now-supports-multiple-vmware-nsx-edge-gateways-6yvdoukn0) · AWS · 0 upvotes · 0 comments --- Tags: [#infrastructure](https://daily.dev/tags/infrastructure) [View this post on daily.dev](https://daily.dev/posts/circular-dependencies-vmware-nsx-t-edition-ipspace-net-blog-omafwfglv) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Circular Dependencies, VMware NSX-T Edition « ipSpace.net blog","url":"https://daily.dev/posts/circular-dependencies-vmware-nsx-t-edition-ipspace-net-blog-omafwfglv","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/circular-dependencies-vmware-nsx-t-edition-ipspace-net-blog-omafwfglv"},"datePublished":"2026-08-11T08:54:34.198Z","dateModified":"2026-08-11T09:16:02.784Z","description":"A critical look at VMware's official NSX-T documentation for deploying NSX Manager on top of the N-VDS virtual switch it manages — a circular dependency that...","image":"https://media.daily.dev/image/upload/s--2-1xRawN--/f_auto/v1722860399/public/Placeholder%2011","thumbnailUrl":"https://media.daily.dev/image/upload/s--2-1xRawN--/f_auto/v1722860399/public/Placeholder%2011","isAccessibleForFree":true,"articleSection":"ipSpace.net Blog","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"ipSpace.net Blog","logo":"https://media.daily.dev/image/upload/s--xS7E82MT--/f_auto,q_auto/v1786438303/logos/ipspace?_a=BAMAMicg0","url":"https://daily.dev/sources/ipspace"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/circular-dependencies-vmware-nsx-t-edition-ipspace-net-blog-omafwfglv","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"infrastructure","timeRequired":"PT4M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"ipSpace.net Blog","item":"https://daily.dev/sources/ipspace"},{"@type":"ListItem","position":3,"name":"Circular Dependencies, VMware NSX-T Edition « ipSpace.net blog"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/circular-dependencies-vmware-nsx-t-edition-ipspace-net-blog-omafwfglv#faq","mainEntity":[{"@type":"Question","name":"What happens to a VMware NSX-T cluster on N-VDS if all hosts reboot after a power failure?","acceptedAnswer":{"@type":"Answer","text":"If all four hosts in a single-cluster N-VDS configuration reboot after a power failure, the NSX management VM port initializes in a blocked state, effectively bricking the cluster. This is a documented caveat in VMware's own NSX-T 3.1 installation guide, and recovering from it requires following ten manual sub-steps involving JSON editing and curl commands. Engineers running NSX-T on N-VDS track failure scenarios and recovery procedures on daily.dev."}},{"@type":"Question","name":"Is there a simpler alternative to deploying NSX-T on N-VDS in vSphere 7.0?","acceptedAnswer":{"@type":"Answer","text":"Yes. With vSphere 7.0 and NSX-T 3.1, NSX-T can run on vSphere Distributed Switches (VDS) in parallel with legacy DVS port groups using the same uplinks, which is significantly simpler. VMware's own documentation added a note acknowledging this, making the complex N-VDS procedure largely a legacy path for environments still running ESXi 6.7. VMware infrastructure teams navigating NSX-T upgrade paths share findings on daily.dev."}}]} ```