Please validate Jumbo Frame configuration on all levels when configuring. Changing either of these values will require a device power cycle. standalone: master (config interface ethernet 1/10) mtu standalone: master (config) interface ethernet 1/10. Configure MTU of 9000 on interface ethernet 1/10. Additionally, a jumbo MTU for 1 Gbps and 10 Gbps interfaces can be allowed up to 9000 bytes. Max MTU supported by the SX10XX switches family is 9216, also known as Jumbo frames. Because jumbo frames are not defined in the IEEE. The maximum MTU is dependent on the hardware platform, but the IEEE 802.3 standards require a minimum MTU of 1500 bytes. Just received an email that all the cases where we thought vSphere HA issues were caused by Jumbo Frames being enabled were actually caused by the fact that it was not configured correctly end-to-end. Jumbo frames are used on local area networks that support at least 1 Gbps and can be as large as 9,000 bytes. To make it crystal clear: disable jumbo frames on your management network with vSphere 5.0 as there’s a problem with it! This problem is currently being investigated by the HA engineering team and will hopefully be resolved. I figured this is probably something that many are not aware of so I copied and pasted his comment:Īnother thing to check if you experience this error is to see if you have jumbo frames enabled on the management network, since this interferes with HA communication. Ive done this and not had to reboot before, but when setting a vSwitch and couple vmkernels to MTU 9000 today I could not do a successful vmkping -d -s 8000 until I had rebooted one host in a two host cluster. I was just reading some of the comments posted today and Marc Sevigny, one of the vSphere HA developers, pointed out something which I did not know. Setting MTU 9000 on ESXi 5.5 U2 hosts requires reboot Weird results.
0 kommentar(er)
