After the resource configurations in the vRealize Automation deployment configuration file are migrated from NSX Data Center for vSphere to NSX-T Data Center, the migration coordinator creates an output mapping file in a .json format.
This mapping file contains information about how vRealize Automation created resources in NSX-v map to NSX-T Data Center objects.
vRealize Automation can use this mapping file to update or refresh its own database after the migration is finished. The migration coordinator places this mapping file at the following path on the NSX Manager appliance where the migration coordinator service runs: /var/log/migration-coordinator/v2t.
The migration coordinator creates a partial or an intermediate mapping file for the first time after the Check Realization step is completed. In the subsequent steps of the migration process, the mapping file changes. For example, mapping information about vRealize Automation created Security Policies, VM network interfaces, Security Groups, and so on, are available in the output mapping file after host migration is completed. The final mapping file is generated after all the hosts in the clusters, which are enabled for migration, are migrated to NSX-T Data Center.
- Check Realization step
- Migrate Edges step
- Migrate Hosts step
The information in the mapping file varies depending on the migration stage that is completed.
- The details in the mapping file before host migration and after host migration can change. Before the hosts are migrated, the mapping file does not contain the network interfaces (vNIC IDs) of the workload VMs that are created in vRealize Automation. The network interfaces of the workload VMs are mapped only after the VMs connect to NSX-T segments during host migration.
- The mapping file shows the new network interfaces of the static VM members in the migrated Security Groups only after all the hosts are migrated to NSX-T.
Scenario: Deleted Resources List in Mapping File
- Your deployment configuration file contains several vRealize Automation created resources. One of the resources is an on-demand Security Group.
- Before running the migration coordinator tool, during a day-two operation, you delete this vRealize Automation created Security Group in the NSX-v UI. The NSX-v inventory does not have the Security Group.
- Let us assume that the data about this deleted Security Group is not yet reconciled with the vRealize Automation database. Therefore, the vRealize Automation database continues to reference this deleted Security Group.
- Now, you run the migration coordinator tool.
After migration to NSX-T, the migration coordinator shows the deleted Security Group in the list of "output deleted resources" of the final mapping file. Because the migration coordinator cannot find the ID of the deleted Security Group, the mapping file does not have the path to the corresponding NSX-T Group.