Use Migration Coordinator to Move Your VM-Series from NSX-V to NSX-T

Learn how to perform a maintenance-mode migration to move your VM-Series firewall deployment from NSX-V to NSX-T.
Complete the following procedure to migrate your VM-Series firewall configuration from NSX-V to NSX-T using the VMware Migration Coordinator tool in NSX-T. This tool is designed run in-place on the same hardware that is running NSX-V. By migrating your configuration, you can reuse policy and dynamic address groups already configured on Panorama. This procedure refers to information and processes published in VMware documentation as well as steps specific to PAN.
This procedure supports operations-centric NSX-V deployments only. An operations-centric deployment means that your policy rules for redirecting traffic to the VM-Series firewall were created in NSX-V Manager, not Panorama.
This procedure requires NSX-T Manager 3.1.0 or later.
It is recommended that plan for security downtime while performing this migration.
  1. Before you begin, complete the following preparatory tasks.
    • Enable DRS on the cluster to be migrated.
    • VMs should be deployed on shared storage and not a local datastore.
  2. Prepare NSX-T Manager for migration.
    1. Log in to the NSX-T Manager CLI via SSH.
    2. Execute the following command to enable NSX Migration Coordinator.
      start service migration-coordinator
      This will now appear in the NSX-T Manager user interface under
    3. SSH in to the NSX-T Manager CLI as root or as admin.
    4. Execute the following command.
      st e
    5. Navigate under /config.vmware/auth/ and make the following change.
    6. Execute the following command.
      service cm-inventory restart
  3. Configure an NSX-T service definition for each NSX-V service definition in your deployment.
    Do not create new device groups
    ; instead use your existing NSX-V device groups. Using the existing device groups allows you to apply the same security policy rules used on NSX-V to the VM-Series firewalls deployed on NSX-T. If you have policy that reference a particular zone, add the same template stack from your NSX-V service definition to your NSX-T service definition. Additionally, if your device group references a particular template, ensure that you select the template stack that includes the template referenced in the device group.
  4. Configure an NSX-T service manager and associate the NSX-T service definitions to the service manager.
  5. Verify that your NSX-T configuration is present on NSX-T Manager.
    1. Log in to NSX-T Manager.
    2. Select
      Service Deployments
    3. Confirm that your NSX-T service definition is listed.
    4. Select
      Network Introspection Settings
      Service Profiles
    5. Confirm that your zones associated with your NSX-T template are listed.
    Steps 8 through 11 detail the migration workflow to be executed on the migration coordinator tool on NSX-T Manager. For more information, refer to VMware migration documentation for more information.
  6. Uninstall the service instance from NSX-V.
    This step will result in traffic disruption.
    1. Log in to your vSphere client.
    2. Select
      Installation and Upgrade
      Service Deployment
    3. Select your service deployment.
    4. Click
    5. Click
      to confirm.
  7. Resolve Configuration issues on NSX-T Manager. While resolving configuration issues, you must take specific actions to migrate your VM-Series firewall configuration. In most cases, you can accept the recommendations presented by NSX-T Manager.
    1. When resolving service insertion configuration, verify that you selected the correct service definition that you previously configured on Panorama for the VM-Series on NSX-T.
    2. Continue resolving the remaining configuration.
    3. Before moving to
      Migrate Configuration
      , you will be asked to provide a transport zone for the service insertion.
    4. Map the service profiles on NSX-V to the corresponding service profiles on NSX-T.
      1. Auto_PAN_VendorTPL can be skipped.
      2. Map the NSX-T service profile to the corresponding NSX-V service profile.
  8. Verify that your configuration has been migrated successfully.
    1. Select
      to verify that your IP sets and security groups are present. You can click on the security group name to see that the correct IP address are a part of the security group.
    2. Select
      Network Introspection Settings
      Service Segment
      to confirm that a service segment has been created.
    3. Select
      Network Introspection Settings
      Service Chains
      to confirm that a service chain has been created. Click the Profiles link in the Forward Path and Reverse Path columns to view your service profile.
    4. Select
      Network Introspection (E-W)
      to confirm that a traffic redirection rule has been created to direct traffic to the service profile of the VM-Series firewall.
  9. If applicable, modify and migrate edges.
  10. Configure and migrate your hosts.
  11. Add the NSX-T tags to you existing dynamic address groups.
    1. Select
      Address Groups
    2. Click on the name of an existing NSX-V dynamic address group.
    3. Click
      Add Match Criteria
      to display the tags from NSX-V and NSX-T.
    4. Add the NSX-T tag to the dynamic address groups. If you choose not to remove the NSX-V tags, be sure to use the
      operator between the tags.
    5. When you have added all the necessary tags, click
    6. Commit
      your changes.
  12. Launch the VM-Series Firewall on NSX-T (East-West). You do not need to create a new service segment; instead select the service segment created during migration.

Recommended For You