iSCSI and vMotion on the same vSwitch
Can iSCSI and vMotion live on the same vSwitch?
vMotion is a feature that is rarely used in our deployments. It is mainly just used when preparing a host for maintenance. We deploy small environments and relatively no DRS events happening. We have been moving to 10GbE for iSCSI connectivity and vMotion and have typically used separate vSwitches and 2X 2port 10GbE NICs. 2 Ports assigned to the iSCSI vSwitch and 2 to the vMotion vSwitch. I am thinking I am wasting resources since vMotion lays dormant most of the time. I would like to create a single vSwitch assign all 4 vmnics to it, create 4 VMKernel Ports for iSCSI to really beef up the throughput and 2 VMKernel ports for vMotion. This would result in some sharing of 2 of the vmnics, but I am thinking since vMotion is so rarely used it should not be a problem. Anyone have thoughts or comments?
vMotion is a feature that is rarely used in our deployments. It is mainly just used when preparing a host for maintenance. We deploy small environments and relatively no DRS events happening. We have been moving to 10GbE for iSCSI connectivity and vMotion and have typically used separate vSwitches and 2X 2port 10GbE NICs. 2 Ports assigned to the iSCSI vSwitch and 2 to the vMotion vSwitch. I am thinking I am wasting resources since vMotion lays dormant most of the time. I would like to create a single vSwitch assign all 4 vmnics to it, create 4 VMKernel Ports for iSCSI to really beef up the throughput and 2 VMKernel ports for vMotion. This would result in some sharing of 2 of the vmnics, but I am thinking since vMotion is so rarely used it should not be a problem. Anyone have thoughts or comments?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Yes we don't all work in Greenfield sites!
ASKER