解決了所有的組態問題之後,您可以移轉組態。移轉組態時,會在 NSX-T Data Center 環境中進行組態變更以複寫 NSX-v 組態。

If needed, you can roll back the configuration that is migrated. Rolling back does the following:
  • Remove the migrated configuration from NSX-T.
  • Roll back all the resolved issues in the previous step.

See 復原或取消 NSX-v 移轉 for more information.

必要條件

確認您已完成解決組態步驟。

程序

  1. From the Migrate Configuration page, click Start.
    The NSX-v configuration is migrated to NSX-T.
  2. 確認所有已移轉的組態皆顯示在 NSX-T 環境中。

    您可以在 NSX-T NSX Manager 介面中或透過執行 NSX-T API 來確認已移轉的組態。

    重要:
    • 移轉組態步驟中,NSX-v 中的安全性標籤不會移轉至 NSX-T。因此,在此步驟完成後,NSX-T 中以安全標籤移轉的動態群組,以及具有靜態成員資格的群組,將會是空的。原因是安全性標籤在 NSX-v 中是一個物件,而在 NSX-T 中,標籤是虛擬機器的屬性。只有在移轉主機步驟期間將工作負載移轉至 NSX-T 後,這些標籤才會套用至工作負載虛擬機器。
    • When the configuration is migrated to NSX-T, the configuration changes are made in the NSX-T NSX Manager database, but it might take some time for the configuration to take effect. You must verify that all expected NSX-v configurations appear on the NSX Manager interface or API in NSX-T before you proceed to the Migrate Edges step. For example, firewall configuration, logical switches, transport zones.
    注意: This caution note applies only when you are using an NSX for vShield Endpoint license in your virtualized environment. This license is included in all vSphere editions. It enables you to use NSX-v to offload only anti-virus processing (Guest Introspection service) on VMs to service appliances that are provided by VMware partners.

    In a Guest Introspection service migration, Security Groups with only dynamic VM membership criteria are supported. If tags-based dynamic Security Groups are used in your NSX-v environment, the Security Tags are not migrated to NSX-T. As no host migration is involved, the migrated dynamic Groups in NSX-T are empty. After the Migrate Configuration step is finished, you must manually create the equivalent tags in NSX-T, and attach them to the VMs that require an endpoint protection.

結果

After this procedure is completed, the fp-eth0, fp-eth1, and fp-eth2 interfaces on the Edge nodes are set to "administratively down". Do not reboot the Edge nodes. Otherwise the fp interfaces will come up and inadvertently advertise the NSX-T networks.