Hi there,
In all honesty, it is going to be hard for someone here to recommend the best architecture without knowing the workloads and requirements.
Ideally this would have been planned prior to the purchase of the hardware and then you can purchase the hardware as per the requirements, so it seems things have been done a bit backwards here.
Firstly, do you need FT in your environment?
Secondly, given there are only two hosts, can we make the assumption the vMotion traffic will be minimal, and likely only be used when maintenance is being performed and a host needs to be placed into maintenance mode?
Will you be using vLANs in your environment?
Assuming dedicated NICs for FT isn't required, you could break them up evenly into the 4 remaining services as per below. But I'd question the benefit on have 2 NICs sit there for vMotion presumably not doing much at all. Then again, the same could be said for ESXi Management.
2 x iSCSI
2 x ESXi Management
2 x vMotion
2 x Virtual Machine
Or you could combine the vMotion and Virtual machine traffic into two NICs and give iSCSI 4 adapters:
4 x iSCSI
2 x ESXi Management
2 x virtual machine and vMotion
Or you could leave some dedicated for vMotion if the requirement needs that, and place ESXi management on the same adapters as virtual machine traffic:
4 x iSCSI
2 x ESXi Management and virtual machine
2 x vMotion
I guess what I'm getting at, is there is a range of combinations, many more than the above, that would be suitable for the environment without knowing anything about it. Are the virtual machine workloads storage heavy? Network heavy? Neither? Both? How often will vMotion be used? Are you using standard or distributed switches?
Cheers, Matt.
VCP6-DCV | VCAP6-DCV Deploy
@mattallford
If you found my answers useful, please help me by marking them as Helpful or Correct!
