Over several days of network operations in NSX-V, you can update the configurations of the on-demand resources that you defined earlier in vRealize Automation.

You can directly use the NSX-V UI or APIs to update the previously defined vRealize Automation resource configurations. The migration coordinator fetches the updated configurations from NSX-V and migrates them to NSX-T.

In the context of migration, the following network operations in NSX-V are supported for vRealize Automation created resources.

Table 1. Supported Operations in NSX-V for vRealize Automation Resources
vRealize Automation Created Resource Supported Network Operations in NSX-V

On-Demand Networks

  • Add or delete VMs from existing on-demand networks that are created using vRealize Automation.
  • Delete an existing on-demand network after deleting or moving workload VMs that are created using vRealize Automation.

On-Demand Security Groups

  • Delete Security Groups that are created using vRealize Automation.
  • Add Security Groups that are created with vRealize Automation to an existing Security Group (out-of-band configuration).
  • Add or change the Security Group in Security Policies that are created with vRealize Automation.
  • Add new firewall rules in Security Policies that are created with vRealize Automation.

DHCP Server configuration

  • Delete or disable DHCP server configuration that is created with vRealize Automation.

Workload VMs

  • Change the network interface (vNIC) assignment of a vRealize Automation created VM from dynamic to static, or reverse, or from static IP1 to static IP2.
  • Change from a single vNIC on a vRealize Automation created VM to multiple vNICs, and reverse.

Load balancer configuration

  • Edit health check related parameters in the load balancer
  • Add or delete pool members
  • Disable load balancer service on the ESG
NAT configuration
  • Modify existing rules
  • Delete existing rules
  • Reorder rules
  • Add port forwarding rules