I have an ESX Infrastructure 4.1 latest version with 2 ESX hosts and virtual machine as vCenter Windows 2003/2008 Server with 18 VMs. The hosts are both connected to a Fibre Channel storage 4GB/sec. I bought an iSCSI storage (Netgear 2100) to be used regularly to make clones of backup my VM manually. The problem is that when you launch more than 2 clones simultaneously lose communication with the vCenter and iSCSI storage becomes inaccessible VMs active and have no more problems but can not access the ESX host it through to vCenter vClient; to restore all I have to restart brutally ESX hosts and the iSCSI NAS Netgear.
It seems that the commonly Gigabit iSCSI (vmkernel?) Is saturated and does not allow me even more to be used for access to ESX hosts with vClient. I would also balance the load using another additional NIC for this purpose but I do not understand how to configure Service Console and the vmkernel.
ESX1 - primary Service Console IP: 10.0.75.1 on vSwitch0 (1 physical NIC)
ESX2 - primary Service Console IP: 10.0.75.2 on vSwitch0 (1 physical NIC)
ESX1 - BACKUP Service Console IP: 10.0.75.3 on vSwitch1 (1 physical NIC)
ESX2 - BACKUP Service Console IP: 10.0.75.4 on vSwitch1 (1 physical NIC)
VSwitch0 on each of 2 ESX vmkernel was created with VMotion enabled. On vSwitch1 there is created a vmkernel with VMotion disabled to communicate with the NAS iSCSI.
Attached the print screen of the ESX configuration.
I would not possibly create on the physical switch (Linksys Gigabit) VLAN but I would divide up the network so that there is a dedicated physical NIC for Service Console, VMotion for one another and to communicate with iSCSI. I do not understand how I set vmkernel / SC and how you set it to only a specific physical NIC to communicate with the NAS iSCSI (different subnets?)
I do not know how.