Is it possible to stop the conversion from going through the management network?

[KMDComp]

Our management network is on 172.16.0.0/16 and our production network is 10.0.0.0/8

When we try to do P2V conversion, all the traffic is going through the firewall we are using to route between the 2 networks, which is not really set up to handle that much traffic and it's resulting is extremely slow conversions.

Is it possible to get the converter to push that traffic through the production network instead?

system is 3 ESXi hosts clustered within vcenter 5.5.  Storage is on a SAN

[POCEH]

The converter connects to the ESX with its name or IP-address obtained from the VC server, so the data will pass through respective subnet.

Is this answer your question?

[patanassov · Accepted solution]

ESX exposes NFC (network file copy) as a service which Converter uses to perform conversions, and NFC uses the management network. AFAIK this can't be changed.

There is an exception, though - if you do Linux P2V, the cloning goes through the VM network and you won't have this issue.

I think you may have a more general problem with this setup, as NFC is used not only by Converter (e.g. SRM, VMotion, etc...). See this: Why is vMotion using the management network instead of the vMotion network? - frankdenneman.nl for something completely different but that might also cause an issue with this setup.

Regards,

Plamen

[KMDComp]

Thanks for the input guys and I'll take a look at that link. 

The converter is installed on the VCenter server, but currently only has one network interface configured on it.  If we setup another network card on that VM and attached it to the management network,  would that remove the need for the conversion traffic to go through the firewall?  Or does it not actually go through the machine the converter is installed on and instead goes directly from the physical machine to the ESXi cluster using the management network?