<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: ESXi 4.x vMotion MTU in ESXi Discussions</title>
    <link>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-4-x-vMotion-MTU/m-p/872280#M68001</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;How do i check if the jumbo frames are working because as i said before the mtu size is not set to 9000 on the Vmotion switch and vmk. However when i do&lt;/P&gt;&lt;P&gt;vmkping -s 9000 anotherhostname &lt;/P&gt;&lt;P&gt;or&lt;/P&gt;&lt;P&gt;vmkping -s 9000 VMotionIPaddress of another host&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;both command seems to be working fine but I was expecting it fail&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;see output&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;~ # vmkping p-dc-esx02 -s 9000&lt;BR /&gt;PING p-dc-esx02 (10.1.254.88): 9000 data bytes&lt;BR /&gt;9008 bytes from 10.1.254.88: icmp_seq=0 ttl=64 time=0.278 ms&lt;BR /&gt;9008 bytes from 10.1.254.88: icmp_seq=1 ttl=64 time=0.285 ms&lt;BR /&gt;9008 bytes from 10.1.254.88: icmp_seq=2 ttl=64 time=0.507 ms&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;~ # vmkping -s 9000 10.1.243.5&lt;BR /&gt;PING 10.1.243.5 (10.1.243.5): 9000 data bytes&lt;BR /&gt;9008 bytes from 10.1.243.5: icmp_seq=0 ttl=64 time=0.338 ms&lt;BR /&gt;9008 bytes from 10.1.243.5: icmp_seq=1 ttl=64 time=0.261 ms&lt;BR /&gt;9008 bytes from 10.1.243.5: icmp_seq=2 ttl=64 time=0.331 ms&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;so it seems like the mtu 9000 seems to be working although it is not been set on the dvswitch and vmk. is this correct?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;please note: we don't have NFS/ISCSI storage but FC EMC SAN so the above issue is only relating to vMotion&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 05 Oct 2012 14:29:04 GMT</pubDate>
    <dc:creator>Eagle11</dc:creator>
    <dc:date>2012-10-05T14:29:04Z</dc:date>
    <item>
      <title>ESXi 4.x vMotion MTU</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-4-x-vMotion-MTU/m-p/872278#M67999</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do we have to set the vMotion MTU size 9000 end to end when using ESXi 4.x with EMC FC SAN?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have just Joined new company and i have noticed that the vds is not set to 9000 mtu for vmotion portgroup. also i have checked esxcfg-vmknic -l and the mtu is set to 1500.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have worked before with ESX and ISCSI SAN where i have to set the mtu size to 9000 to the ISCSI and vmotion switchesnd and also the vmk intefaces.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Many thanks for anyhelp&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Oct 2012 09:31:50 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-4-x-vMotion-MTU/m-p/872278#M67999</guid>
      <dc:creator>Eagle11</dc:creator>
      <dc:date>2012-10-05T09:31:50Z</dc:date>
    </item>
    <item>
      <title>Re: ESXi 4.x vMotion MTU</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-4-x-vMotion-MTU/m-p/872279#M68000</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Enabling Jumbo frames for vMotion network is recommended for best performance. if you are using storage through NFS/iSCSI then enabling jumbo frames make sense to increases performance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-vCloud9&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Oct 2012 13:37:09 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-4-x-vMotion-MTU/m-p/872279#M68000</guid>
      <dc:creator>vCloud9</dc:creator>
      <dc:date>2012-10-05T13:37:09Z</dc:date>
    </item>
    <item>
      <title>Re: ESXi 4.x vMotion MTU</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-4-x-vMotion-MTU/m-p/872280#M68001</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;How do i check if the jumbo frames are working because as i said before the mtu size is not set to 9000 on the Vmotion switch and vmk. However when i do&lt;/P&gt;&lt;P&gt;vmkping -s 9000 anotherhostname &lt;/P&gt;&lt;P&gt;or&lt;/P&gt;&lt;P&gt;vmkping -s 9000 VMotionIPaddress of another host&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;both command seems to be working fine but I was expecting it fail&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;see output&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;~ # vmkping p-dc-esx02 -s 9000&lt;BR /&gt;PING p-dc-esx02 (10.1.254.88): 9000 data bytes&lt;BR /&gt;9008 bytes from 10.1.254.88: icmp_seq=0 ttl=64 time=0.278 ms&lt;BR /&gt;9008 bytes from 10.1.254.88: icmp_seq=1 ttl=64 time=0.285 ms&lt;BR /&gt;9008 bytes from 10.1.254.88: icmp_seq=2 ttl=64 time=0.507 ms&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;~ # vmkping -s 9000 10.1.243.5&lt;BR /&gt;PING 10.1.243.5 (10.1.243.5): 9000 data bytes&lt;BR /&gt;9008 bytes from 10.1.243.5: icmp_seq=0 ttl=64 time=0.338 ms&lt;BR /&gt;9008 bytes from 10.1.243.5: icmp_seq=1 ttl=64 time=0.261 ms&lt;BR /&gt;9008 bytes from 10.1.243.5: icmp_seq=2 ttl=64 time=0.331 ms&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;so it seems like the mtu 9000 seems to be working although it is not been set on the dvswitch and vmk. is this correct?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;please note: we don't have NFS/ISCSI storage but FC EMC SAN so the above issue is only relating to vMotion&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Oct 2012 14:29:04 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-4-x-vMotion-MTU/m-p/872280#M68001</guid>
      <dc:creator>Eagle11</dc:creator>
      <dc:date>2012-10-05T14:29:04Z</dc:date>
    </item>
    <item>
      <title>Re: ESXi 4.x vMotion MTU</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-4-x-vMotion-MTU/m-p/872281#M68002</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am little confused, AFAIK, if jumbo frames are not enabled on NIC's/vSwitch/VMK you shouldnt be receiving the response. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-vCloud9&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Oct 2012 14:36:51 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-4-x-vMotion-MTU/m-p/872281#M68002</guid>
      <dc:creator>vCloud9</dc:creator>
      <dc:date>2012-10-05T14:36:51Z</dc:date>
    </item>
    <item>
      <title>Re: ESXi 4.x vMotion MTU</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-4-x-vMotion-MTU/m-p/872282#M68003</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That is exactly my point. it shouldn't work but it is. This is why i posted this question as i dont have experience with ESXi or FC SANs.&lt;/P&gt;&lt;P&gt;is it possible that ESXi does not need Jumbo Frames for vMotion?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Oct 2012 14:51:16 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-4-x-vMotion-MTU/m-p/872282#M68003</guid>
      <dc:creator>Eagle11</dc:creator>
      <dc:date>2012-10-05T14:51:16Z</dc:date>
    </item>
    <item>
      <title>Re: ESXi 4.x vMotion MTU</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-4-x-vMotion-MTU/m-p/872283#M68004</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I remember reading one of VMware docs, clearly stating that for best performance VMware recommends enabling Jumbo frames on vMotion network as well.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-vCloud9&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Oct 2012 14:54:04 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-4-x-vMotion-MTU/m-p/872283#M68004</guid>
      <dc:creator>vCloud9</dc:creator>
      <dc:date>2012-10-05T14:54:04Z</dc:date>
    </item>
    <item>
      <title>Re: ESXi 4.x vMotion MTU</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-4-x-vMotion-MTU/m-p/872284#M68005</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It doesn't "need" jumbo frames, it's just a best practice to improve performance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have little experience with vmkping, but according to this kb, it should be used with -d option too.&lt;/P&gt;&lt;P&gt;&lt;A class="active_link" href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=1003728"&gt;http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=1003728&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does it make any sense?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;elgreco81&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Oct 2012 14:54:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-4-x-vMotion-MTU/m-p/872284#M68005</guid>
      <dc:creator>elgreco81</dc:creator>
      <dc:date>2012-10-05T14:54:26Z</dc:date>
    </item>
    <item>
      <title>Re: ESXi 4.x vMotion MTU</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-4-x-vMotion-MTU/m-p/872285#M68006</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Jumbo Frames are for ethernet network according to this&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" class="active_link" href="https://communities.vmware.com/thread/400100"&gt;http://communities.vmware.com/thread/400100&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;elgreco81&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Oct 2012 14:57:36 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-4-x-vMotion-MTU/m-p/872285#M68006</guid>
      <dc:creator>elgreco81</dc:creator>
      <dc:date>2012-10-05T14:57:36Z</dc:date>
    </item>
    <item>
      <title>Re: ESXi 4.x vMotion MTU</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-4-x-vMotion-MTU/m-p/872286#M68007</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;FC SANs don't use an MTU so you don't need to take that into consideration. MTU and Jumbo Frames are Ethernet concepts. A Jumbo Frame is just frames that are greater than the conventional frames of 1500. As algreco81 said, it is better to have a higher MTU for performance reasons, but it is not a requirement for migrations to work. It only improves VM migrations (copying the running instance of a VM and its active RAM to from one host to another). The storage stays in place.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Oct 2012 15:17:55 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-4-x-vMotion-MTU/m-p/872286#M68007</guid>
      <dc:creator>Andr3201110141</dc:creator>
      <dc:date>2012-10-05T15:17:55Z</dc:date>
    </item>
    <item>
      <title>Re: ESXi 4.x vMotion MTU</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-4-x-vMotion-MTU/m-p/872287#M68008</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi elgreco81&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your reply.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have seen these link before But my question is about vMotion and NOT storage. I do understand that ISCSI storage need MTU 9000 and also vMotion need that as well as i worked before with ESX and ISCSI storage where i had enabled mtu 9000 to vMotion and storage.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But this discussion was about vMotion and ESXi 4.x.&lt;/P&gt;&lt;P&gt;The vmkping -d would have been the correct test but my ESX4.0 the -d option does not exist. See below link&lt;/P&gt;&lt;P&gt;&lt;A href="http://pubs.vmware.com/vsphere-4-esx-vcenter/index.jsp?topic=/com.vmware.vsphere.config_iscsi.doc_41/esx_san_config/cli/c_vmkping_command.html"&gt;http://pubs.vmware.com/vsphere-4-esx-vcenter/index.jsp?topic=/com.vmware.vsphere.config_iscsi.doc_41/esx_san_config/cli/c_vmkping_command.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As a result i cannot test it. and if i use just vmkping -s 9000 that seems to work fine although the mtu is not set on vds and uplink which makes me wonder how it is possible&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Eagle11&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 08 Oct 2012 10:49:10 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-4-x-vMotion-MTU/m-p/872287#M68008</guid>
      <dc:creator>Eagle11</dc:creator>
      <dc:date>2012-10-08T10:49:10Z</dc:date>
    </item>
  </channel>
</rss>

