![Vsphere mtu 9000](https://kumkoniak.com/58.jpg)
Interface Port Group/DVPort IP Family IP Address Netmask Broadcast MAC Address MTU TSO MSS Enabled Type sysconfig]# esxcfg-vswitch -A VMkernel vSwitch1 Be careful when using high MTU sizes, as most of the drivers used in the VMKUSB NIC Fling do not support MTU size 9000 and thus, the overlay communication. sysconfig]# esxcfg-vswitch -L vmnic1 vSwitch1 It is critical that the MTU is configured across the whole platform (Network Adapters, Distributed Switches, Physical Switches, NSX-T Uplink profiles). Lets assign a NIC to the newly created vSwitch sysconfig]# esxcfg-vswitch -m 9000 vSwitch1 If you wish you can execute the below command on the fly to your vSwitch without deleting it PortGroup Name VLAN ID Used Ports Uplinks Switch Name Num Ports Used Ports Configured Ports MTU Uplinks
![vsphere mtu 9000 vsphere mtu 9000](https://community.cisco.com/kxiwq67737/attachments/kxiwq67737/6011-discussions-ucs/13773/1/ucs-nic-mtu.png)
In my case vSwitch1 was used as VMkernel for iscsi. Its recommend to start from 0 but if you wish you can enable the jumbo frames on the fly, it won’t throw any errors. Most probably you might have your VMkernel setup with 1500 MTU so we need to delete it and start over again. So let’s activate it, I have used Jumbo frames only with SW initiator not HW one so if some can comment on how it works on HW it would be in for a great benefit. If you are getting sluggish performance then try enabling jumbo frames
- iSCSI with jumbo frames gives better or rather much better performance.
- The network must support Jumbo Frames end‐to‐end for Jumbo Frames to be effective.
- Jumbo Frames allow ESX Server to send larger frames out onto the physical network.
- Conventionally, jumbo frames can carry up to 9,000 bytes of payload.
Jumbo frames are Ethernet frames with more than 1,500 bytes of payload (MTU).
> Lets understand what’s Jumbo Frames first and how it benefits us …