Starting in vSphere 5.5 we introduced a new concept: the custom TCP/IP Stack. Created via the command line, you could separate vmkernel traffic by configuring a new TCP/IP stack. This would allow for different subnets and default gateways to be used for different vmkernels. However, this also means “mucking about” in the command line. Not bad but the potential for “oops” factor is increased. The command itself is:
esxcli network ip netstack add –N “NFS”
are you using vSphere 5.5? if yes, take a look at following blog post written by Linus Bourque,
vSphere New and Old Feature: TCP/IP Stacks Galore
Quoted text is taken from that blog post.