Hi,
we have the Enterprise license (not Enterprise+), so no distributed switch.
I would use teaming with ip hash and etherchannels on the cisco side for the client network.
For vmotion, ISCSI and NFS the active/unused configuration allowes me to leave the switches untouched, correct?
Well I'm not sure if NFS or ISCSI, if we use NFS we maybe also want "virtual iscsi" so that a vm machine can
connect via iscsi initiator to a lun. What would you recommend? (Simple and redundant, speed is not top priority)
After reading the postings, I guess this would be ok:
- 4 physical nics for the connection of the client network (VLAN 50) -> vswitch0, 4 nics in active/active mode
- 4 physical nics for vmotion and management (VLAN 100) -> vswitch1
each nic configured with it's own vmkernel port and separate ip like shown in http://pibytes.wordpress.com/2013/01/12/multi-nic-vmotion-in-vsphere-5-x/
- 2 physical nics for the ISCSI (VLAN 101) -> vswitch2
each nic configured with it's own vmkernel port and separate ip
like shown in http://sostech.wordpress.com/2011/08/22/vmware-iscsi-multipath-vsphere5/
- 2 physical nics for the NFS (VLAN 102) -> vswitch3
each nic configured with it's own vmkernel port and separate ip
like shown in http://sostech.wordpress.com/2011/08/22/vmware-iscsi-multipath-vsphere5/
What about the service console? Can it be on the same vswitch as vmotion+management?
Thanks!