Enabling Jumbo Frames for iSCSI on Server Core

I recommend following the instructions in my “Rename a Network Interface from the Command Line” so you can easily distinguish the difference in the network interfaces. Once the network interfaces are renamed, they should look similar to the ones in this image:

If you attempt to ping your SAN at this point with a 8972 byte ping (9000 bytes minus a 20 byte IP header and a 8 byte ICMP header), you’ll receive a message stating “Packet needs to be fragmented but DF set.”:

In this example, I am going to enabled Jumbo frames on the two iSCSI network interfaces (iSCSI1 and iSCSI2). Run the following command to set the MTU to 9000 on the iSCSI1 interface. Repeat for the iSCSI2 interface.

Run the following command to verify the MTU has been set to 9000:

If you rebooted at this point and tried to ping your SAN, you might think it’s working since the result is slightly different, however it’s not quite that simple.

Run regedit.exe:  

Go to HKLM>System>CurrentControlSet>Services>Tcpip>Parameters>Interfaces and find the key(s) that contain the IP address of your iSCSI adapters. Record the key’s name:

Go to HKLM>CurrentControlSet>Control>Class>{4D36E972-E325-11CE-BFC1-08002BE10318} and find the key(s) that contains the name you recorded in the previous step. This will be in the NetCfgInstanceId field. Set the “*JumboPacket” value to 9000:

If you do not have a “*JumboPacket” field, then the network driver you’re using does not support this feature. In that case, download the latest driver for the network adapter and install it. In my example, this procedure is being performed on a Dell PowerEdge R710 with a Broadcom four port onboard NIC and an additional add-in Broadcom dual port NIC. The drivers for these Broadcom network cards can be downloaded from their website.

Warning: There is an issue with the Broadcom version drivers that could cause the network cards to become inoperable if a virtual switch already exists on your Hyper-V host server and it is running the core installation of Windows Server 2008 R2. I have only experienced this issue on Dell PowerEdge R710 Servers. I have run the same process on Dell PowerEdge 2950 Servers with the same network cards and drivers without issue. If you have a Dell PE R710, consider removing the virtual switches before installing this driver or be prepared to reload the Hyper-V host server if you experience this problem.

Install the drivers. If the installation is done across the network, you will temporarily lose your connection.  

I chose yes to enable the TCP Offload Engine (TOE) support:

Once the driver installation is complete, change the “*Jumbo Packet” setting in the registry field specified above and then reboot.

You should now be able to ping your SAN using a packet size of 8972:

One thing to keep in mind is that Jumbo frames must be enabled for the entire path from the server to the SAN for them to be successfully transmitted and received. Be sure to verify that Jumbo frames are enabled on your iSCSI switches. All of the switches I have seen default to disabled for Jumbo frames so this option will need to be explicitly enabled:

And finally, verify your SAN has Jumbo frames enabled. The EqualLogic PS4000XV defaults to having Jumbo frames enabled and there’s no way I’m aware of to disable them:

If you experience issues, I recommend checking the following to see if any updates are available: network card driver versions, switch firmware, and SAN software revision.


Leave a Reply

%d bloggers like this: