The Assessment mode of VMware NSX Migration for VMware Cloud Director tool verifies the migration preparedness of organization VDCs of the NSX Data Center for vSphere. It performs discovery of features used in all or specified NSX Data Center for vSphere backed organization VDCs and analyzes the suitability of each for migration. The assessment mode can be run on the VMware Cloud Director instance that has not yet been configured and prepared for NSX-T Data Center. It needs access only to the VMware Cloud Director API endpoint.
The Assessment mode creates Detailed and summary report files in the following format:
<VCD-UUID>-v2tAssessmentReport-DD-MM-YYYY-HH-MM-SS.csv<VCD-UUID>-v2tAssessmentReport-Summary-DD-MM-YYYY-HH-MM-SS.csvThis shows accumulative data of all the organization VDCs combined with the following details:
This shows report per organization VDC with the following details:
Possible values for the Status column in the detailed report:
Note While running the assessment mode, the VMware Cloud Director should be in a stable state. If any organization VDC along with its components (undergoing evaluation) is in a critical or busy state, unexpected assessment failures can occur.
| Features | Mitigation Steps |
|---|---|
| Empty vApps | Delete the empty vApps. |
| Suspended VMs | Power On/Off the suspended VM's. |
| No free interface on edge gateways | Change the routed organization VDC network connection interface type from internal to distributed or subinterface to free up one direct interface. |
| Edge Gateway Rate Limit | After migration, apply equivalent gateway QoS profile to Tier-1 gateway backing the target organization VDC Edge gateway directly in NSX-T Data Center. |
| Independent Disks: Attached VMs are not powered off | Power off the VM to which independent disk is attached |
| DHCP Binding: Binding IP addresses overlap with static IP Pool range | Make sure IPs are not overlapping between DHCP binding and the static pool |
| DHCP Relay: Domain names are configured | Use DHCP relay IP addresses instead of its domain name |
| Gateway Firewall: Any as TCP/UDP port | Change rule to Any / Any without specifying protocol or use specific ports in the rule. |
| Gateway Firewall: Gateway interfaces in rule | Replace with supported source/target (IP Set, security group). |
| Gateway Firewall: Networks connected to different edge gateway used | Replace with IPset based rule. |
| Gateway Firewall: Unsupported grouping object | Change to a supported grouping object (network) or to an IPSet. |
| NAT: Range of IPs or network in DNAT rule | Change to specific IPs. |
| IPsec: Unsupported Encryption Algorithm | Reconfigure the VPN to a supported encryption algorithm. |
| IPsec: CA certificate is missing | Upload CA certificate on the edge gateway |
| User-defined Static Routes | Delete the user-defined static routes on the source edge gateway prior to the migration and configure equivalent rules from NSX-T on the destination external network Tier-0/VRF. |
| LoadBalancer: Default pool not configured | Configure the default pool in all the virtual services. |
| LoadBalancer: Unsupported persistence | Switch to one of the supported persistence methods (client IP, HTTP cookie). |
| LoadBalancer: Unsupported algorithm | Switch to one of the supported algorithms (least connections, round robin, consistent hash). |
| Distributed Firewall: Invalid objects in rule | Replace with equivalent supported objects (networks). |
| Distributed Firewall: Unsupported type in applied to section | Modify rule so it can be applied to the whole organization VDC. |
| Distributed Firewall: Networks connected to different edge gateway used | Replace with equivalent IPset based rule. |
| Distributed Firewall: Layer 2 Rule | Replace with equivalent layer 4 rules. |
| Distributed Firewall: Invalid Security Group objects in the rule | Replace with supported objects in Security Groups |
