VMware Networking Community
acoelho1984
Contributor
Contributor

Cannot migrate NSX-T Manager to N-VDS segment.

I can migrate any VM as well as vCenter to the N-VDS and maintain connectivity; however, when I try to migrate the NSX Manager VM (nsxmgr01) to vm.network-ls (a segment/logical switch on N-VDS) connectivity is lost.  Any ideas?  Using NSX-T 2.4 Migration Coordinator this topology is completed successfully.  NSX-T manager does lose its connectivity for several seconds but does come back.

nsx-t.png

Tags (1)
5 Replies
RaymundoEC
VMware Employee
VMware Employee

correct me if I wrong but you mean connectivity of everything or just to NSX manager?

so try to reproduce the error but use ssh to one of the ESXi hosts and get a "tail -f /var/log/vmkernel.log" if something goes weirdo will paint there, if possible post it here.

+vRay
0 Kudos
acoelho1984
Contributor
Contributor

VMware has confirmed the issue and I’m awaiting a resolution.  See below:

Hello Adam,

My apologies for the delay in responding.  I have not yet learned of a workaround/solution to the situation in which we've found ourselves.  The Logs show the successful update on the disconnect, but then the NSX Manager appears to lose its connection to itself.

I'll be reaching out to you again as soon as I have a direction.

Thank you for your time,
Daryl Marcus
Staff Network Virtualization Engineer, Escalation Engineer, VCP6-NV, VCIX6-NV, WCNA, CEH, CPT, CEPT
Global Support Services, VMware Inc.

0 Kudos
RaymundoEC
VMware Employee
VMware Employee

oh man, thanks for sharing! send me the TSR number in private if posible.

+vRay
0 Kudos
acoelho1984
Contributor
Contributor

TSR number is SR 19000478706.

Current status is that you must use the migration coordinator service to move the NSX-T Manager appliance over to the N-VDS.  They have sent me the location to the scripts but I do not have the time to review the entire script to find out exactly how the coordination service completes what the GUI is unable to complete.  VMware technical support and myself assume that the script must be creating some manual bindings via API calls to NSX-T before the VM's network is migrated.  I asked that they update the VMware Validated Design documentation to inform fellow engineers.  The support engineer is still investigating this scenario in their lab to hopefully determine a method for successfully migrating the NSX-T manager manually.

ldclancy2
Contributor
Contributor

NSX-T 3.2

(Needs three NSX Managers)

I solve this by deleting one manager at a time (NSX-T GUI > System > Appliances) and recreating a new one on the NVDS (or VDS7) segment.

0 Kudos