Thank you, I figgered out you can only manipulate the filesystem when logged in as root so I did. I created a tn-list with the transport nodes I wanted to migrate as I want to do one or two at a time, again due to vMotion network congestion, and I could only run the migration when logged in as admin.
Note the maintenance-timeout is measured in minutes AFAIK (https://vdc-download.vmware.com/vmwb-repository/dcr-public/4582b1ff-5434-4872-b468-6c1381810d36/afcc1507-3ed1-4f4b-b51e-bfb8f3625c2f/cli_313.html#vds-migrate%20tn-list%20%3Cconfigfile%3E%20[maintenance-timeout%20%3Ctimeout%3E]) as shown here:
Original Message:
Sent: Mar 04, 2025 02:26 AM
From: JohannesWalter
Subject: How do I create a text file on the NSX-T manager appliances?
Good morning!
We have carried out the NVDS migration in the last few weeks.
We also searched in vain for the location where NSX stores the config file after the "vds-migrate precheck" in order to be able to modify it. That's why we then used the API way.
The timeout value seems to be specified in seconds, we set it to 3600.
An overload of the vMotion network is IMHO not to be feared. With "vds-migrate esxi-cluster-name <cluster-name>", the migration tool only takes one host at a time in the specified cluster, evacuates it, switches it to maintenance mode, rebuilds the NVDS->CVDS, releases the host and then moves on to the next one. If the evacuation of a host already jeopardizes your vMotion network, you should urgently reconsider your network design...
To be able to access the NSX Manager with WinSCP, root access must first be permitted: https://knowledge.broadcom.com/external/article/375479/ssh-root-access-for-nsxt-appliance-fails.html
You can then log in directly with root@nsx-manager.lab via ssh; access with WinSCP is then also possible.
BTW: In this article you will find an excellent article (pdf) by Francois Tallet describing the xVDS functions and the migration options: Moving from NVDS to VDS
Original Message:
Sent: Mar 03, 2025 09:04 PM
From: JDMils_Interact
Subject: How do I create a text file on the NSX-T manager appliances?
I'm getting ready to migrate my NVDS switches to VDS (https://techdocs.broadcom.com/us/en/vmware-cis/nsx/nsxt-dc/3-2/administration-guide/host-switches/migrate-host-switch-to-vsphere-distributed-switch/migrate-host-switch-to-vsphere-distributed-switch.html - section "Migrate Host Switch to vSphere Distributed Switch") and am using the CLI. The command I'm using to perform the migrations is:
vds-migrate tn-list <configfile> [maintenance-timeout <timeout>]
I've logged into the CLI on the NSX-T manager appliance however I do not know how to create a file on the local OS to be the "configfile". Can this be done?
I tried to WinSCP to the NSX-T manager however I get this error:
Received too large (622871407 B) SFTP......
Normally when I get this error on a vCenter I just change the default shell, but I'm not sure how to do this on the NSX-T manager appliance.
Side Note: Does anyone know the metric for the option <timeout>? Is it in seconds or minutes?
My migration plan is to perform the migration one-transport node at a time to stop the vMotion network from being overwhelmed when a host automatically goes into maintenance mode and all VMs try to vMotion off the host. I have a PowerShell script to automate this part.
vCenter is 7.0u3t
NSX-T is v3.2.4.0.0.23653566