The V2T Migration Wizard with "object does not exist" error message

Products

• VMware NSX

Issue/Introduction

The message "SecurityGroup configuration is not supported in NSX-T" with referenced instances listed.
The error message indicates the migration thinks there is an object that doesn't exist, but it does.
The VM is active in vCenter and the MOID in vCenter matches what is reported in the error message.

 

NOTE: To verify the VM ID from the vCenter Server UI, select the VM in the UI and view the URL in the browser window (ID highlighted in yellow):

 

 

Environment

VMware NSX

Cause

The format of the section in the script for identifying VM(s) with DHCP is incorrect

Log Location:

/var/log/migration-coordinator/v2t/vc-collection.log 

We see the below error(s) reported in the logs:

2023-07-20 09:43:40,438 __main__     WARNING  10.49.74.117 : Collector is collecting vCenter resources with best effort...
2023-07-20 09:43:40,446 __main__     INFO     10.49.74.117 : Find datacenter DataCenter
2023-07-20 09:43:40,477 __main__     INFO     10.49.74.117 : Processing virtual machines in group ########-####-####-####-############
2023-07-20 09:43:41,534 __main__     INFO     There are 1 vms to be collected in group ########-####-####-####-############ in VC ##.##.##.100
2023-07-20 09:43:41,704 __main__     ERROR    Failed to read config of VM vm-3773 from VC ##.##.##.100: 'dhcp'

Resolution

Before applying the workaround, please rollback to the beginning of the migration and restart the configuration collection for the V2T migration.

To apply the workaround please follow the below steps:

1. Login to the NSX-T manager as root
2. cd /opt/vmware/migration-cordinator-tomcat/bin/v2t/config-collector
3. Open the vc_collector.py file with a text editor
4. In the function _get_dhcp_options() change the line:

vnic_dict['dhcp'][ver] = {'enable': dhcp_ops.enable}   

TO

vnic_dict['dhcp'] = {ver : {'enable': dhcp_ops.enable}} 

NOTE: Please ensure that the indentation is not changed

5. Save and exit the text editor
6. Continue config collection from the UI and with the rest of the migration process