I would say if you are connecting to a NetApp, even if you are not doing a reference design, use the design as a guide for settings. However, if you do as mentioned above use the FlexPod reference design it does state to use 9216 for your settings.
#Vsphere mtu 9000 windows#
You can test from a Windows server using the -f flag.
#Vsphere mtu 9000 full#
Remember the default will be 1500, so you have to enable it on every link of the full path that you expect to pass jumbo frames. We found our original docs used and it had conflicting settings in it as well. The interfaces on the uplink should have the MTU set as well, or you will get fragmentation of packets. You can test whether MTU 9000 works using the vmkping command from one of the ESXi hosts. You cannot set the MTU size to a value greater than 9000 bytes. Click Advanced and set the MTU property to a value greater than 1500 bytes. On the Configure tab, expand Settings and select Properties. This caused the packet to be larger than 9000 and the FI dropped it.Īs stated above there is a lot of information about Jumbo Frames with the NetApp and UCS with conflicting configurations. The MTU needs to be configured from end to end, i.e. On the vSphere Client Home page, click Networking and navigate to the distributed switch. Because of that there is extra packet header information. However, the new UTA2 adapters on the NetApp are CNA cards and act as FCoE even when running Ethernet only traffic. Reason: As I understand it, our other controllers used on straight 10GB Ethernet adapters. Configuration steps for layer-2 interface Change the system jumbo MTU to 9214 with the system jumbomtu 9214 global command. Because jumbo frames are not defined in the IEEE. You cannot set an MTU size greater than 9000 bytes. Jumbo frames are used on local area networks that support at least 1 Gbps and can be as large as 9,000 bytes. You can enable jumbo frames by setting an MTU value greater than 1500. Change the MTU (Bytes) value for the standard switch. Select a standard switch from the table and click Edit settings. The jumbo frame configuration steps are different for layer-2 and layer-3 interfaces. On the Configure tab, expand Networking and select Virtual Switches. Once this was done everything connected and tested fine. 2.2.1 Cisco Nexus 9000 Jumbo Frame Configurations Cisco Nexus 9000 switches support jumbo frame however it is not enabled by default. After over a month of troubleshooting, it came down to the UCS Fabric Interconnections were dropping the Jumbo packets.įix: Change the MTU from 9000 to 9216 in the LAN Cloud QOS System class. We were not able to run Jumbo frame storage connections to these. This worked fine up until we got new controllers for our cluster mode FAS8060 with NetApps UTA2 ports. We are a FlexPod reference design, running iSCSI for our VMware storage.
When we setup our environment over two years ago we set it up with the MTU of 9000 in the LAN Cloud QOS System class. when we are setting jumbo frames it should be same at all nodes from source to destination.
0 kommentar(er)
