Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm setting up an ESXi 4 server to connect to an NFS datastore. I'd like to bond two of the NICs together and use jumbo frames for the NFS connection on a private (non-management) network. I setup a new switch with the 2 NICs and am able to connect to the NFS share over it, but could use some guidance on getting jumbo frames and link aggregation/bonding/teaming working.

share|improve this question
You understand that bonding is not going to do anything for you performance wise and will only give you additional reliability? Bonding cannot really help you much if you only have connections between two hosts. – Zoredache Jun 9 '10 at 16:25
I would have bonded NICs on both sides of the connection (NFS server and ESXi). I'm guessing you're thinking there would only be a single NIC on the NFS server that would be the bottleneck. – Sysadminicus Jun 9 '10 at 16:34

First off, make sure you can support jumbo frames from end to end of the stack. This means the nics in your storage to the switching and of course the hosts nics. If they aren't all set to jumbo frames or can't all do jumbo frames there is no point in trying - you'll be worse off.

On ESXi the process to setup jumbo frames requires using the command line - there is no method in the vSphere client. However you achieve that (Unsupported mode, vMA, rCLI, etc) you have to be able to use the command line. If you're still good, I'll refer you to an excellent blog post here by Chad Sacak. It is iSCSI centric but has the necessary commands to setup all the jumbo frame esx(i) bits.

Good Luck!

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.