Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I have a distributed application that passes a whole lot of traffic among a number of machines. Currently, those machines share a gigabit network with the rest of the machines in the rack, and I'm starting to see problems (packet collisions). Casting about for solutions, I ran across discussion of jumbo frames, which would definitely solve my problem if it works as advertised. But ...

The servers that I use for the distributed application (it's a type of web crawler) also need access to the Internet, and everything I've read about jumbo frame cautions that for it to work well every device attached to the network has to support jumbo frame. My router might very well handle splitting the jumbo packets before transmitting, but doing so would slow things incredibly.

My servers all have two network cards. Can I set up a private network for the distributed application, making sure that all the machines' first network cards are set for jumbo frame, and use the second card on those machines (with jumbo frame turned off) to connect to the rest of my network and to the outside world. My thinking here is that the heavy traffic internal to the crawler subsystem would then be isolated from the rest of the network, including the Internet traffic, and the use of jumbo frame would improve communication speeds.

The machines are all Dell PowerEdge 1950 servers running Windows 2008. I know that the PE servers' Broadcom GigE network adapters support jumbo frame, but can I configure one with jumbo frame and one without?

Finally, how do I make sure I get a switch that supports jumbo frame? We're using a TP-Link switches that seem to work well currently, but I can't find any information on whether they support jumbo frame.

I know I have a lot of questions. Does what I'm considering sound reasonable?

share|improve this question

3 Answers 3

up vote 2 down vote accepted

Make sure that your NICs exist in separate netblocks when doing this. If you use Linux, packets are routed via the first NIC in the system in the netblock, so, even though eth1 has an MTU of 9000, it could end up routing those packets through eth0.

We set up a separate VLAN to our storage network and had to set up a separate netblock on eth1 to avoid that behavior. Increasing the MTU to 9000 easily increased throughput as that particular system deals with streaming a number of rather large files.

share|improve this answer
    
By "netblock", I assume you mean separate IP ranges. That is, one interface will be set, for example, to 192.168.100.x, and the other would be set to 192.168.200.x? –  Jim Mischel Sep 10 '10 at 17:43
    
correct. more characters to get past the minimum. –  karmawhore Sep 10 '10 at 18:34

Taking a step back for a moment, in a full-duplex switched environment you should not be experiencing collisions. I would investigate the cause of the collisions before going to far down the jumbo frames path.

That being said, individual devices should negotiate their MTU sizes with each other. So you shouldn't have to have it turned on for all devices.

share|improve this answer
    
What do you mean I shouldn't have to have it turned on for all devices. Everything I've read here and on other sites that talk about jumbo frame indicates that if a device that doesn't support jumbo frame is connected to the network, it's quite likely that that device will drop packets that are larger than the Ethernet standard 1,518 bytes. –  Jim Mischel Sep 10 '10 at 17:41
    
Perhaps it's not packet collisions? In situations where I have heavy traffic, I get errors that say "expected preamble". Everything I've been able to find indicates that it's an Ethernet error, typically caused by packet collisions. If I slow things down, I don't get those errors. –  Jim Mischel Sep 10 '10 at 17:50
    
I think what they were referring to was the network equipment (routers / switches / firewalls) needs to support JF. Other devices should I think negotiate a compatible MTU size. More info here: codinghorror.com/blog/2009/03/… –  Peter Sep 10 '10 at 23:34

That should be quite doable. Server NICs on Windows can have different MTU settings for each interface. Otherwise iSCSI, the usual driver of jumbo frames, wouldn't have the uptake it has had.

share|improve this answer

Your Answer

 
discard

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.