VMware Networking Community
Thanksgoditsfri
Enthusiast
Enthusiast

NSX-T Migration coordinator

Hi there,

We are planning the migration from NSX-V to NSX-T and we have deployed 3 managers and an Edge Node. NSX-T Managers, Edge Node, ESX hosts, vCenter and NSX-V manager are on the same network and have connectivity.

When we are carrying out the process of importing the NSX-V configuration, it gives us a failure in the process 4- Translate imported configuration: Errors Config translation failed [Reason: [TOPOLOGY] Can not proceed with migration: DFW user-defined rules in topo # 3 candidate.].

Attach picture.

Image 1442.png

 

Any idea?

 

Thanks!

0 Kudos
4 Replies
CyberNils
Hot Shot
Hot Shot

Looks like you have unsupported DFW rules in NSX-V.

Check this out to figure out what may be blocking:

https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.1/migration/GUID-2A39C982-5BCC-400F-8761-F133F...

Also check the log files on NSX-T Manager:
/var/log/migration-coordinator/v2t/

cm.log is a good start.



Nils Kristiansen
https://cybernils.net/
0 Kudos
Thanksgoditsfri
Enthusiast
Enthusiast

Not to mutch for that log. We review https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.1/migration/GUID-FA5EFF22-B7CA-4FF8-A0D3-C0CB0... and I think its good 😞

 

2021-10-13 15:39:45,039 16840 CM.plugins.xlate_plugin DEBUG Loaded 1 objects
2021-10-13 15:39:45,039 16840 CM.plugins.topology_plugin INFO FW/NAT enabled on: edge-9
2021-10-13 15:39:45,039 16840 CM.plugins.xlate_plugin DEBUG Loading configuration from nsx-v backup files named firewall.globalroot-0.config
2021-10-13 15:39:45,047 16840 CM.plugins.xlate_plugin DEBUG Loaded 1 objects
2021-10-13 15:39:45,048 16840 CM.engine.xlate_engine INFO ---------- TOPOLOGY plugin: failed with [TOPOLOGY] Can not proceed with migration: DFW user-defined rules in topo#3 candidate.
2021-10-13 15:39:45,048 16840 CM.engine.xlate_engine INFO This exception requires stage to terminate
2021-10-13 15:39:45,080 16840 CM.engine.xlate_engine INFO
Stored 203 apis

2021-10-13 15:39:45,084 16840 CM.engine.xlate_engine INFO --------------- Stage xlate: error

0 Kudos
Thanksgoditsfri
Enthusiast
Enthusiast

Update! The above error was due to having an ESG applied in a DFW policy. Removing it from DFW policy and disabling the FW on the ESG, fixed.

Still working on it.

 

Image 1447.png

0 Kudos
CyberNils
Hot Shot
Hot Shot

Make sure your topology matches one of the supported ones here:

https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.1/migration/GUID-FA5EFF22-B7CA-4FF8-A0D3-C0CB0...

 



Nils Kristiansen
https://cybernils.net/
0 Kudos