Skip to content
Menu
  • CloudThesis-Home
  • Cloud Management
    • VMware Cloud
    • VCF (VMware Cloud Foundation)
    • vRO
    • vRA
    • vRealize Log Insight
    • vCloud Director
    • Hybrid Cloud Extension (HCX)
    • vCloud
    • Cloud on AWS
  • VMware
    • vCenter
    • vSphere
      • Generic vSphere Commands
    • ESXi
    • VMware vRealize Suite Lifecycle Manager –8 Deployment Guide
    • VMware Site Recovery Manager (SRM)
    • vRealize Network Insight
    • VMware Horizon
  • Power CLI
    • PowerCLI Snippets
  • NSX
  • vSAN
    • vSAN 7
  • Nutanix
  • VOIP
  • Microsoft
    • Azure Cloud
    • Microsoft Windows Server
    • Hypervisor
    • Create Azure VMs (Portal)
    • Create Azure VMs – PowerShell
  • Author
  • Contact

Deploying VMware Cloud Foundation (VCF) Management Domain with a Single NSX-T Node

Posted on May 14, 2025

Deploying an SDDC with a Single NSX-T Node

Step 1: Populate Configuration Parameters

Populate all required parameters in the VMware Cloud Foundation (VCF) Configuration Workbook. Ensure accuracy in IP allocations, hostname definitions, and NSX-T node specifications.

Step 2: Transfer the Configuration Workbook

Utilize WinSCP or an equivalent secure file transfer utility to transfer the completed spreadsheet to the Cloud Builder Virtual Machine (VM).

Step 3: Convert Spreadsheet to JSON Format

Execute the following command within the Cloud Builder VM to convert the workbook into a JSON configuration file:

:bash

/opt/vmware/sddc-support/sos --jsongenerator --jsongenerator-input ./VCF-4.4.xlsx --jsongenerator-design vcf-ems

Replace VCF-4.4.xlsx with the actual filename used in your environment. The resulting vcf-ems.json will be saved in:

/opt/vmware/sddc-support/cloud_admin_tools/Resources/vcf-ems/

Step 4: Modify NSX-T Configuration

Open the generated vcf-ems.json file and navigate to the nsxtSpec section.

By default, this section includes multiple NSX-T nodes. Modify it to retain only nsxt01, ensuring that redundant nodes (nsxt02 and nsxt03) are removed. The updated JSON should resemble:json

"nsxtSpec": {
    "nsxtManagerSize": "medium",
    "nsxtManagers": [
        {
            "hostname": "<nsxt01-fqdn>",
            "ip": "<nsxt01-IP>"
        }
    ]
}

Replace <nsxt01-fqdn> and <nsxt01-IP> with the appropriate Fully Qualified Domain Name (FQDN) and IP address of the NSX-T Manager.

Step 5: Transfer and Upload JSON Configuration

Securely transfer the modified JSON file to the machine from which the Cloud Builder UI is accessible.

During the deployment process, upload the modified vcf-ems.json file instead of the original spreadsheet at the “Upload File” page.

This refined version employs precise technical language while maintaining clarity for implementation. Let me know if you need any further refinements or explanations

Upon successful completion of the bring-up process, the deployed Software-Defined Data Center (SDDC) will feature a single NSX-T Manager node as the central control plane component for network virtualization and security policies. This configuration streamlines NSX-T operations by consolidating management functions into a singular instance, optimizing resource utilization while maintaining scalability within the VMware Cloud Foundation environment.

Thanks, I hope this post was insightful and engaging for you!

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Search Topic

Categories

  • Azure Cloud
  • Cloud Management
  • Cloud on AWS
  • Create Azure VMs – PowerShell
  • Create Azure VMs (Portal)
  • ESXi
  • Generic vSphere Commands
  • Hybrid Cloud Extension (HCX)
  • Hypervisor
  • Microsoft
  • Microsoft Azure Cloud and Services
  • Microsoft Windows Server
  • NSX
  • Nutanix
  • Power CLI
  • PowerCLI Snippets
  • vCenter
  • VCF (VMware Cloud Foundation)
  • vCloud
  • vCloud Director
  • VMware
  • VMware Cloud
  • VMware Horizon
  • VMware Site Recovery Manager (SRM)
  • VMware vRealize Suite Lifecycle Manager – 8.0
  • vRA
  • vRealize Log Insight
  • vRealize Network Insight
  • vRO
  • vSAN
  • vSAN 7
  • vSphere
  • Windows Servers
©2025 | WordPress Theme by Superbthemes.com