Merge pull request #532 from RichardHoch/vmware_esxi_nfc

NFC-enabled vmkernel NIC migration option
kubev2v · Jul 31, 2024 · 955c65c · 955c65c
2 parents 5be1cf0 + c85e175
commit 955c65c
Show file tree

Hide file tree

Showing 3 changed files with 11 additions and 1 deletion.
diff --git a/documentation/modules/new-migrating-virtual-machines-cli.adoc b/documentation/modules/new-migrating-virtual-machines-cli.adoc
@@ -354,7 +354,9 @@ EOF
 ----
 <1> Specify the name of the VMware vSphere `Provider` CR.
 <2> Specify the Managed Object Reference (MoRef) of the VMware vSphere host.
-<3> Specify the IP address of the VMware vSphere migration network.
+<3> Specify the IP address of the VMware vSphere migration network
+
+include::snip_vmware_esxi_nfc.adoc[]
 
 [start=4]
 . Create a `NetworkMap` manifest to map the source and destination networks:

diff --git a/documentation/modules/selecting-migration-network-for-vmware-source-provider.adoc b/documentation/modules/selecting-migration-network-for-vmware-source-provider.adoc
@@ -10,6 +10,8 @@ You can select a migration network in the {ocp} web console for a source provide
 
 Using the default network for migration can result in poor performance because the network might not have sufficient bandwidth. This situation can have a negative effect on the source platform because the disk transfer operation might saturate the network.
 
+include::snip_vmware_esxi_nfc.adoc[]
+
 .Prerequisites
 
 * The migration network must have sufficient throughput, minimum speed of 10 Gbps, for disk transfer.

diff --git a/documentation/modules/snip_vmware_esxi_nfc.adoc b/documentation/modules/snip_vmware_esxi_nfc.adoc
@@ -0,0 +1,6 @@
+:_content-type: SNIPPET
+
+[NOTE]
+====
+You can also control the network from which disks are transferred from a host by using the Network File Copy (NFC) service in vSphere.
+====