MSA 2050 Jumbo Frames with Windows Server 2016

[Vint]

I read in a technical paper that jumbo frames are supported at 8900 bytes.

I have enabled jumbo frames on the MSA, network switches, and the Windows Server 2016 NICs. 

However, there is no 8900 option in Windows. I selected 9014 as it seemed to be the best option among 1514, 4088, 9014, and 9336 bytes.

Is 9014 bytes the best option? What issues might I expect to indicate there is a problem?

Thanks,

Vint 

[SUBHAJIT KHANBARMAN_1]

As per the MSA best practice guide, you can see it need to set as 8900

https://h20195.www2.hpe.com/v2/getpdf.aspx/A00015961ENW.pdf (Page no 42)

Now this MTU size HPE fixed because they have tested it in LAB. Anything more than 8900 will create more and more packet fragmentation. Packet fragmentation will not only degrade performance, but flood the links with lots of packet fragmentation.

So I wouldn't recommend using anything else apart from MTU size 8900 with MSA 2050

Hope this helps!
Regards
Subhajit

If you feel this was helpful please click the KUDOS! thumb below!

***********************************************************************************

[Vint]

Not only was that response not helpful, it was non-responsive. It seems that given an almost completely homogenous HPE environment (all except the "Aruba" switches), a simple answer could be had. 

There is no place, either in the MSA (via cli: jumbo-frame enabled), or within the Windows Advanced properties for the NICs, to specify an MTU value of 8900. You must select a value from the list provided and that list does not include 8900, anywhere.

I am using two HPE NICS in each of my three HPE servers to connect to my HPE MSA 2050 iSCSI storage. Neither the HPE Ethernet 10Gb 2-Port 535FLR-T or the HPE Ethernet 10Gb 2-Port 535T Adapter allow me to specify 8900 in the Jumbo Packet pull-down property (see original post). Furthermore, the RoCE MTU Advanced Property also does not allow me to specify a value of 8900. It allows me to select from 256, 512, 1024, 2048, 4096.

[Branden23]

I am looking into the same issue and found that I was able to set a custom MTU size on an interface via NETSH

Windows SHOULD accept the custom value but I have not been able to test this yet.   If you still have your storage array in a lab I would be interested in your results.   We had to put ours into production in a hurry.

This might get you started:

let’s look at the interfaces along with what the current MTU is on each: netsh interface ipv4 show interfaces Then, let’s make the mtu 1464 persistently using the Idx number of the interface to change from the above command in quotes: netsh interface ipv4 set subinterface "10" mtu=1464 store=persistent