The recommendation from VMWare centred around our networking configuration, namely making use from jumbo frames, vlanning and trunking. In addition, there are countless references to flow control causing problems especially related to NFS. I'll post my findings when I have something.
I wonder if someone could help with some sanity checking of our networking design. This design incorporates ESXi5.1, NetApp 3240 files using NFS and HP BL460c G7 blades using quad and dual port mezzanine cards to give a total of 8 NICs.
One vSwtich on VMWare will be configured with 2 NICs for the sole purpose of NFS for the presentation of NFS to the hosts.
From what I understand:
* ESXi 5.1 cannot do LACP (only possible with Enterprise Plus licenses and a distributed switch).
* The NetApp can trunk using LACP, Multimode VIFs or Single mode.
The switch we are using is a single 5406zl chassis with four 24 port modules. I'm sure you've noticed that we're rather exposed in the event of a chassis failure but this is a risk we are prepared to bear. It does have the advantantage of making trunking easier though as everything is going through one switch.
Now, my question is:
1. Do we configure the NICs on the VM host side as a standard trunk (using 'route based on IP')?
2. Should we configure these switch ports as standard trunk (not LACP for reasons given above)?
3. Do we configure the vif on the NetApp side as LACP or a multimode trunk (bearing in mind the filer can do LACP but the VMHosts can't)?
4. Assuming 3 is yes, we would presumably configure the trunks on the switch as LACP too.
Question 3 is probably the important on here.
Help appreciated - you've already been most helpful.
Richard