{"id":121,"date":"2013-04-18T10:35:11","date_gmt":"2013-04-18T10:35:11","guid":{"rendered":"https:\/\/www.softwareab.net\/wordpress\/?p=121"},"modified":"2013-04-18T10:46:24","modified_gmt":"2013-04-18T10:46:24","slug":"jumbo-frames-use-case-for-esxi5-netapp-and-cisconetgear-switches","status":"publish","type":"post","link":"https:\/\/www.softwareab.net\/wordpress\/jumbo-frames-use-case-for-esxi5-netapp-and-cisconetgear-switches\/","title":{"rendered":"Jumbo Frames – Use Case for ESXi5, NetApp, and Cisco\/NetGear Switches"},"content":{"rendered":"

Jumbo frames are used for iSCSI (which use 8192 byte frames) to avoid IP fragmentation, thus improving network throughput by reducing the overall number of frames transmitted. Jumbo frames are by convention 9000 bytes which is ample for iSCSI traffic (and any required VLAN tagging). This blog post guides the user through setting up jumbo frames for ESXi5, NetApp FAS2240 storage device, NetGear GS748TS switch, and Cisco-compatible (CatIOS-compatible) blade switches.
\n
\nSetting up jumbo frames is a function of all elements in a communications chain:<\/p>\n

    \n
  1. Network interfaces<\/li>\n
  2. Switch ports<\/li>\n
  3. Routers<\/li>\n<\/ol>\n

    For this use case, jumbo frames are used for iSCSI in a very simple environment: by design, iSCSI traffic is never routed (flat Layer 2 fabric). Thus, jumbo frames affect only network interfaces and switch ports. As a simple switch fabric use case jumbo frames highlight the areas to hit when modifying network communications.<\/p>\n

    Know the Network: VLANs and Subnets<\/h5>\n

    Because VLANs segment network traffic, it\u00e2\u20ac\u2122s important to note that jumbo frames must be enabled at the VLAN interface in addition to the physical network interface. For this use case, assume that the iSCSI (Storage) VLAN ID is 240.<\/p>\n

    Also, the network admin must know which subnet is providing the iSCSI (Storage) function: for this use case this is the 172.28.4\/24 subnet. This network is – by design – non-routable so consumers and providers must be on the VLAN *and* on the related 172.248.4\/24 subnet; failure on either part means that iSCSI can\u00e2\u20ac\u2122t be used.<\/p>\n

    NetApp Filer and Jumbo Frames<\/h5>\n

    The journey starts with the storage appliance supporting the iSCSI consumers, in this case the FAS2240 in the APG Cloud. Log into the appliance and determine the iSCSI interface. Issue command rdfile \/etc\/rc<\/code> and look for the ifconfig<\/code> lines that create and configure VLAN 240:<\/p>\n

    FAS2240001SX> rdfile \/etc\/rc<\/strong>
    \nvlan create e0c 240
    \nifconfig e0c-240 172.28.4.160 netmask 255.255.255.0
    \nifconfig e0c-240 partner e0c-240<\/code><\/p>\n

    In the above NetApp configuration, the interface e0c<\/code> has a VLAN 240 created for it (which creates a *virtual* interface called e0c-240<\/code>). Note that there is no line or setting to modify the MTU to be 9000. To setup jumbo frames, issue command ifconfig e0c-240 mtusize 9000<\/code> and do not forget to update the \/etc\/rc<\/code> file. Then the command ifconfig e0c-240<\/code> will show the following:<\/p>\n

    FAS2240001SX> ifconfig e0c-240<\/strong>
    \ne0c-240: flags=0x1b4c867<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 9000
    \ninet 172.28.4.160 netmask 0xffffff00 broadcast 172.28.4.255
    \nether 00:a0:98:19:e2:58 (auto-1000t-fd-up) flowcontrol full<\/code><\/p>\n

    Note that mtu 9000<\/strong> is now part of the output. Update both NetApp filer heads the same way and the first part is done. The NetApp filer now supports jumbo frames on the iSCSI interface.<\/p>\n

    NetGear Switches and Jumbo Frames<\/h5>\n

    The NetGear GS748TS switches used by this use case are not truly programmable; instead, the sysadmin logs into the Web interface. Also, jumbo frames are not enabled at the port level but instead for the entire switch. Login to each NetGear switch and enable jumbo frames (requires a reboot if the switch doesn\u00e2\u20ac\u2122t already support jumbo frames). The screenshot for the NetGear Switches section below shows jumbo frames enabled for the NetGear switch as a whole.
    \n\"netapp_jumbo_frames\"<\/a><\/p>\n

    Cisco-compatible Switch and Jumbo Frames<\/h5>\n

    This use case is delivering iSCSI to an ESX host that is running on Hitachi CB2000 blades within the Infrastructure rack. The blades communicate to the outside world via a Cisco-compatible switch built into the blade chassis itself; each blade has “lines” (the equivalent of CAT6 cables) that connect each NIC to the relevant switches. Furthermore, the CB2000 chassis switches offer port uplinks that are connected to the NetGear switch at the top of the rack.<\/p>\n

    Note that the CB2000 switches are almost 100% compatible to Cisco IOS-based switches. Thus, these programming instructions will apply almost identically to Cisco switches for jumbo frame support.<\/p>\n

    For this use case, two ports are involved:<\/p>\n

      \n
    1. The dedicated iSCSI (Storage) port connecting the CB2000 switch to the blade.<\/li>\n
    2. The CB2000 switch uplink port connecting to the NetGear switch.<\/li>\n<\/ol>\n

      For this use case these ports are both on Switch Module 1 on the CB2000 (the CB2000 has up to 6 switch modules labeled 0-5 – each blade in the chassis has up to 10 NICs connected to the various switches). The uplink port is Line 1 (which has a physical cable connecting it to the NetGear) and Line 5 (which connects to NIC 1 of blade 0 which is running the ESXi5 host).<\/p>\n

      Login to the CB2000 chassis and set the MTU size for both of these ports within the ENABLE<\/code> mode:<\/p>\n

      login: [enter switch user]<\/em>
      \nPassword: [enter switch user password]<\/em>
      \nCopyright (c) 2005-2010 ALAXALA Networks Corporation. All rights reserved.
      \n> en
      \nPassword: [enter ENABLE mode password]<\/em>
      \n# conf t
      \n(config)# show int gig 0\/1<\/strong>
      \ninterface gigabitethernet 0\/1
      \nflowcontrol send on
      \nmtu 9000
      \nswitchport mode trunk
      \nswitchport trunk allowed vlan 240
      \n!
      \n(config)# show int gig 0\/5<\/strong>
      \ninterface gigabitethernet 0\/5
      \nspeed 1000
      \nduplex full
      \nflowcontrol send on
      \nmtu 9000
      \nswitchport mode trunk
      \nswitchport trunk allowed vlan 240
      \nspanning-tree portfast trunk
      \n!<\/code><\/p>\n

      The above shows that the MTU is set to 9000; if it wasn\u00e2\u20ac\u2122t simply configure each affected interface to have the mtu 9000<\/code> setting and save the configuration.<\/p>\n

      ESXi5 and Jumbo Frames: Host vSwitch and vmknic<\/h5>\n

      The final step in this use case is to extend jumbo frames to ESXi hosts. When setting jumbo frames within ESXi5, there are two considerations: standard virtual switches (vSwitch) and distributed virtual switches (dvSwitch). The setup is similar for both and explored in the following sections.<\/p>\n

      ESXi5, Jumbo Frames, and Standard Switches<\/h6>\n

      Both the ESXi5 host virtual switch (vSwitch) as well as the VMkernel NIC (vmknic) must use an MTU of 9000 as well as the appropriate VLAN. Login to the ESXi5 host and check to see which vSwitch is using the NIC that is connected to the CB2000 switch module:<\/p>\n

      # esxcfg-vswitch -l<\/strong>
      \nSwitch Name\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0 Num Ports\u00c2\u00a0\u00c2\u00a0 Used Ports\u00c2\u00a0 Configured Ports\u00c2\u00a0 MTU\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0 Uplinks
      \nvSwitch0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0 128\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0 4\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0 128\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0 1500\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0 vmnic1
      \nPortGroup Name\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0 VLAN ID\u00c2\u00a0 Used Ports\u00c2\u00a0 Uplinks
      \nVM Network\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0 220\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0 0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0 vmnic1
      \nManagement Network\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0 210\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0 1\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0 vmnic1<\/code><\/p>\n

      Switch Name\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0 Num Ports\u00c2\u00a0\u00c2\u00a0 Used Ports\u00c2\u00a0 Configured Ports\u00c2\u00a0 MTU\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0 Uplinks
      \nvSwitch1\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0 128\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0 4\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0 128\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0 9000\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0 vmnic2
      \nPortGroup Name\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0 VLAN ID\u00c2\u00a0 Used Ports\u00c2\u00a0 Uplinks
      \niSCSI\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0 240\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0 1\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0 vmnic2<\/code><\/p>\n

      In the above output, the virtual switch vSwitch1<\/code> is associated with vmnic2<\/code> (which corresponds to the NIC connected to the CB2000 switch in the previous section). The MTU is already set to 9000; if it wasn\u00e2\u20ac\u2122t, then the command esxcfg-vswitch -m 9000 vSwitch1<\/code> would do the trick.<\/p>\n

      Note also that a portgroup named “iSCSI” has been created; this portgroup must be on the iSCSI (Storage) VLAN 240.<\/p>\n

      Finally, the relevant VMkernel NIC (vmknic) must be created to use that VLAN 240 portgroup; this vmknic must *also* have an MTU of 9000 specified. Here is the command:<\/p>\n

      esxcfg-vmknic -a -i 172.28.4.90 -n 255.255.255.0 -m 9000 iSCSI<\/code><\/p>\n

      That command creates a vmknic on the iSCSI portgroup. Note especially that the IP address is on the configured 172.28.4\/24 subnet.<\/p>\n

      At this point, jumbo frames are in place for the dvSwitch, portgroup, and vmknic.<\/p>\n

      ESXi5, Jumbo Frames, and Distributed Switches<\/h6>\n

      Within a full-blown vSphere \/ vCenter environment and distributed virtual switches (dvSwitch), the setup is the similar to standard switches.<\/p>\n

        \n
      1. The dvSwitch must be set to the correct MTU. The following screenshot shows this in action for the dvSwitch named dvSwitchStorage<\/code>:
        \n\"esxi5_dvs_01\" <\/a><\/li>\n
      2. The related distributed portgroup (dvPortGroup) must have the correct VLAN. The following screenshot demonstrates this for the dvPortGroup dvPgStorage<\/code> assigned to a distributed switch named dvSwitchStorage<\/code>:
        \n        \"esxi5_dvs_02\"<\/a><\/li>\n
      3. Finally, when adding hosts to the dvSwitch the sysadmin must ensure that an appropriate VMkernel NIC (vmknic) has been created *and mapped* to that host within the portgroup. An easy way to do this is to use the vSphere Client; select the host and go to the Configuration tab, then select Networking from the blue links on the left. To create a vmknic select to “Manage Virtual Adapters” and then select to add an adapter (it will only allow a VMkernel adapter type). In the Connection Settings screen, select the dvPortGroup for iSCSI as shown below:
        \n        \"esxi5_dvs_03\"<\/a>
        \nNote that the dvPortGroup dvPgStorage<\/code> has been selected and, because this storage adapter is used for vMotion, the appropriate checkbox is set (which permits the host to advertise this vmknic as supporting vMotion to neighbors within a vSphere cluster).Most likely storage networks will be IP-based so then provide the IP address based on the assigned values from the storage administrator.When finished creating the virtual adapter, go back to the settings and change the MTU to 9000 for this jumbo frames use case. (The default is 1500 which is not big enough.) See the following shot:
        \n        \"esxi5_dvs_04\"<\/a><\/li>\n<\/ol>\n

        At this point, jumbo frames are in place for the dvSwitch, dvPortGroup, and the related virtual adapter that maps to a vmknic.<\/p>\n

        Verifying Jumbo Frames<\/h5>\n

        On the affected ESXi5 host, simply use the vmkping<\/code> command with options set *not* to fragment IP packets and a packet size of 1600. Because the default packet size is 1500, this means that any receiver in the network chain which cannot handle jumbo frames will disregard the packet; this returns an error. See the vmkping<\/code> help for details on the command line options.<\/p>\n

        First run the command against a known target that does not have jumbo frame support (for example, the default router):<\/p>\n

        \/var\/log # vmkping -4 -d -I vmk0 -s 1600 172.24.1.1
        \nPING 172.24.1.1 (172.24.1.1): 1600 data bytes
        \nsendto() failed (Message too long)
        \nsendto() failed (Message too long)
        \nsendto() failed (Message too long)
        \n--- 172.24.1.1 ping statistics ---
        \n3 packets transmitted, 0 packets received, 100% packet loss<\/code><\/p>\n

        That failed as expected; try again against the NetApp filer which should support jumbo frames:<\/p>\n

        \/var\/log # vmkping -4 -d -I vmk1 -s 1600 172.28.4.160
        \nPING 172.28.4.160 (172.28.4.160): 1600 data bytes
        \n1608 bytes from 172.28.4.160: icmp_seq=0 ttl=255 time=0.291 ms
        \n1608 bytes from 172.28.4.160: icmp_seq=1 ttl=255 time=0.290 ms
        \n1608 bytes from 172.28.4.160: icmp_seq=2 ttl=255 time=0.280 ms
        \n--- 172.28.4.160 ping statistics ---
        \n3 packets transmitted, 3 packets received, 0% packet loss
        \nround-trip min\/avg\/max = 0.280\/0.287\/0.291 ms<\/code><\/p>\n

        That succeeded, which proves that jumbo frames are working correctly. At this point the system designer can rest assured that iSCSI traffic can travel as efficiently as possible over the IP network.<\/p>\n","protected":false},"excerpt":{"rendered":"

        Jumbo frames are used for iSCSI (which use 8192 byte frames) to avoid IP fragmentation, thus improving network throughput by reducing the overall number of frames transmitted. Jumbo frames are by convention 9000 bytes which is ample for iSCSI traffic …<\/p>\n

        Jumbo Frames – Use Case for ESXi5, NetApp, and Cisco\/NetGear Switches<\/span> Read More »<\/a><\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6,5,1],"tags":[7,8],"yoast_head":"\nJumbo Frames - Use Case for ESXi5, NetApp, and Cisco\/NetGear Switches - softwareab<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.softwareab.net\/wordpress\/jumbo-frames-use-case-for-esxi5-netapp-and-cisconetgear-switches\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Jumbo Frames - Use Case for ESXi5, NetApp, and Cisco\/NetGear Switches - softwareab\" \/>\n<meta property=\"og:description\" content=\"Jumbo frames are used for iSCSI (which use 8192 byte frames) to avoid IP fragmentation, thus improving network throughput by reducing the overall number of frames transmitted. Jumbo frames are by convention 9000 bytes which is ample for iSCSI traffic … Jumbo Frames – Use Case for ESXi5, NetApp, and Cisco\/NetGear Switches Read More »\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.softwareab.net\/wordpress\/jumbo-frames-use-case-for-esxi5-netapp-and-cisconetgear-switches\/\" \/>\n<meta property=\"og:site_name\" content=\"softwareab\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/cloudraticsolutions\/\" \/>\n<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/cloudraticsolutions\/\" \/>\n<meta property=\"article:published_time\" content=\"2013-04-18T10:35:11+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2013-04-18T10:46:24+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.softwareab.net\/wordpress\/wp-content\/uploads\/2013\/04\/netapp_jumbo_frames-300x260.png\" \/>\n<meta name=\"author\" content=\"Andrew Bruce\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@realcloudratics\" \/>\n<meta name=\"twitter:site\" content=\"@realcloudratics\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Andrew Bruce\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"8 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.softwareab.net\/wordpress\/jumbo-frames-use-case-for-esxi5-netapp-and-cisconetgear-switches\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.softwareab.net\/wordpress\/jumbo-frames-use-case-for-esxi5-netapp-and-cisconetgear-switches\/\"},\"author\":{\"name\":\"Andrew Bruce\",\"@id\":\"https:\/\/www.softwareab.net\/wordpress\/#\/schema\/person\/1337443eaeb75104e0410b508e67f600\"},\"headline\":\"Jumbo Frames – Use Case for ESXi5, NetApp, and Cisco\/NetGear Switches\",\"datePublished\":\"2013-04-18T10:35:11+00:00\",\"dateModified\":\"2013-04-18T10:46:24+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.softwareab.net\/wordpress\/jumbo-frames-use-case-for-esxi5-netapp-and-cisconetgear-switches\/\"},\"wordCount\":1360,\"commentCount\":4,\"publisher\":{\"@id\":\"https:\/\/www.softwareab.net\/wordpress\/#\/schema\/person\/1337443eaeb75104e0410b508e67f600\"},\"image\":{\"@id\":\"https:\/\/www.softwareab.net\/wordpress\/jumbo-frames-use-case-for-esxi5-netapp-and-cisconetgear-switches\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.softwareab.net\/wordpress\/wp-content\/uploads\/2013\/04\/netapp_jumbo_frames-300x260.png\",\"keywords\":[\"iscsi\",\"jumbo frame\"],\"articleSection\":[\"Network\",\"Storage\",\"Teknocratica\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.softwareab.net\/wordpress\/jumbo-frames-use-case-for-esxi5-netapp-and-cisconetgear-switches\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.softwareab.net\/wordpress\/jumbo-frames-use-case-for-esxi5-netapp-and-cisconetgear-switches\/\",\"url\":\"https:\/\/www.softwareab.net\/wordpress\/jumbo-frames-use-case-for-esxi5-netapp-and-cisconetgear-switches\/\",\"name\":\"Jumbo Frames - Use Case for ESXi5, NetApp, and Cisco\/NetGear Switches - softwareab\",\"isPartOf\":{\"@id\":\"https:\/\/www.softwareab.net\/wordpress\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.softwareab.net\/wordpress\/jumbo-frames-use-case-for-esxi5-netapp-and-cisconetgear-switches\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.softwareab.net\/wordpress\/jumbo-frames-use-case-for-esxi5-netapp-and-cisconetgear-switches\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.softwareab.net\/wordpress\/wp-content\/uploads\/2013\/04\/netapp_jumbo_frames-300x260.png\",\"datePublished\":\"2013-04-18T10:35:11+00:00\",\"dateModified\":\"2013-04-18T10:46:24+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/www.softwareab.net\/wordpress\/jumbo-frames-use-case-for-esxi5-netapp-and-cisconetgear-switches\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.softwareab.net\/wordpress\/jumbo-frames-use-case-for-esxi5-netapp-and-cisconetgear-switches\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.softwareab.net\/wordpress\/jumbo-frames-use-case-for-esxi5-netapp-and-cisconetgear-switches\/#primaryimage\",\"url\":\"https:\/\/www.softwareab.net\/wordpress\/wp-content\/uploads\/2013\/04\/netapp_jumbo_frames.png\",\"contentUrl\":\"https:\/\/www.softwareab.net\/wordpress\/wp-content\/uploads\/2013\/04\/netapp_jumbo_frames.png\",\"width\":538,\"height\":468},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.softwareab.net\/wordpress\/jumbo-frames-use-case-for-esxi5-netapp-and-cisconetgear-switches\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.softwareab.net\/wordpress\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"iscsi\",\"item\":\"https:\/\/www.softwareab.net\/wordpress\/tag\/iscsi\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Jumbo Frames – Use Case for ESXi5, NetApp, and Cisco\/NetGear Switches\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.softwareab.net\/wordpress\/#website\",\"url\":\"https:\/\/www.softwareab.net\/wordpress\/\",\"name\":\"softwareab\",\"description\":\"Technocratica, Technopolitik, Technophobia\",\"publisher\":{\"@id\":\"https:\/\/www.softwareab.net\/wordpress\/#\/schema\/person\/1337443eaeb75104e0410b508e67f600\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.softwareab.net\/wordpress\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\/\/www.softwareab.net\/wordpress\/#\/schema\/person\/1337443eaeb75104e0410b508e67f600\",\"name\":\"Andrew Bruce\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.softwareab.net\/wordpress\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/www.softwareab.net\/wordpress\/wp-content\/uploads\/2024\/03\/andy-cartoon.jpg\",\"contentUrl\":\"https:\/\/www.softwareab.net\/wordpress\/wp-content\/uploads\/2024\/03\/andy-cartoon.jpg\",\"width\":400,\"height\":330,\"caption\":\"Andrew Bruce\"},\"logo\":{\"@id\":\"https:\/\/www.softwareab.net\/wordpress\/#\/schema\/person\/image\/\"},\"description\":\"Team-oriented systems mentor with deep knowledge of numerous software methodologies, technologies, languages, and operating systems. Excited about turning emerging technology into working production-ready systems. Focused on moving software teams to a higher level of world-class application development. Specialties:Software analysis and development...Product management through the entire lifecycle...Discrete product integration specialist!\",\"sameAs\":[\"http:\/\/cloudraticsolutions.net\/\",\"https:\/\/www.facebook.com\/cloudraticsolutions\/\",\"https:\/\/twitter.com\/realcloudratics\"]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Jumbo Frames - Use Case for ESXi5, NetApp, and Cisco\/NetGear Switches - softwareab","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.softwareab.net\/wordpress\/jumbo-frames-use-case-for-esxi5-netapp-and-cisconetgear-switches\/","og_locale":"en_US","og_type":"article","og_title":"Jumbo Frames - Use Case for ESXi5, NetApp, and Cisco\/NetGear Switches - softwareab","og_description":"Jumbo frames are used for iSCSI (which use 8192 byte frames) to avoid IP fragmentation, thus improving network throughput by reducing the overall number of frames transmitted. Jumbo frames are by convention 9000 bytes which is ample for iSCSI traffic … Jumbo Frames – Use Case for ESXi5, NetApp, and Cisco\/NetGear Switches Read More »","og_url":"https:\/\/www.softwareab.net\/wordpress\/jumbo-frames-use-case-for-esxi5-netapp-and-cisconetgear-switches\/","og_site_name":"softwareab","article_publisher":"https:\/\/www.facebook.com\/cloudraticsolutions\/","article_author":"https:\/\/www.facebook.com\/cloudraticsolutions\/","article_published_time":"2013-04-18T10:35:11+00:00","article_modified_time":"2013-04-18T10:46:24+00:00","og_image":[{"url":"https:\/\/www.softwareab.net\/wordpress\/wp-content\/uploads\/2013\/04\/netapp_jumbo_frames-300x260.png"}],"author":"Andrew Bruce","twitter_card":"summary_large_image","twitter_creator":"@realcloudratics","twitter_site":"@realcloudratics","twitter_misc":{"Written by":"Andrew Bruce","Est. reading time":"8 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.softwareab.net\/wordpress\/jumbo-frames-use-case-for-esxi5-netapp-and-cisconetgear-switches\/#article","isPartOf":{"@id":"https:\/\/www.softwareab.net\/wordpress\/jumbo-frames-use-case-for-esxi5-netapp-and-cisconetgear-switches\/"},"author":{"name":"Andrew Bruce","@id":"https:\/\/www.softwareab.net\/wordpress\/#\/schema\/person\/1337443eaeb75104e0410b508e67f600"},"headline":"Jumbo Frames – Use Case for ESXi5, NetApp, and Cisco\/NetGear Switches","datePublished":"2013-04-18T10:35:11+00:00","dateModified":"2013-04-18T10:46:24+00:00","mainEntityOfPage":{"@id":"https:\/\/www.softwareab.net\/wordpress\/jumbo-frames-use-case-for-esxi5-netapp-and-cisconetgear-switches\/"},"wordCount":1360,"commentCount":4,"publisher":{"@id":"https:\/\/www.softwareab.net\/wordpress\/#\/schema\/person\/1337443eaeb75104e0410b508e67f600"},"image":{"@id":"https:\/\/www.softwareab.net\/wordpress\/jumbo-frames-use-case-for-esxi5-netapp-and-cisconetgear-switches\/#primaryimage"},"thumbnailUrl":"https:\/\/www.softwareab.net\/wordpress\/wp-content\/uploads\/2013\/04\/netapp_jumbo_frames-300x260.png","keywords":["iscsi","jumbo frame"],"articleSection":["Network","Storage","Teknocratica"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.softwareab.net\/wordpress\/jumbo-frames-use-case-for-esxi5-netapp-and-cisconetgear-switches\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.softwareab.net\/wordpress\/jumbo-frames-use-case-for-esxi5-netapp-and-cisconetgear-switches\/","url":"https:\/\/www.softwareab.net\/wordpress\/jumbo-frames-use-case-for-esxi5-netapp-and-cisconetgear-switches\/","name":"Jumbo Frames - Use Case for ESXi5, NetApp, and Cisco\/NetGear Switches - softwareab","isPartOf":{"@id":"https:\/\/www.softwareab.net\/wordpress\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.softwareab.net\/wordpress\/jumbo-frames-use-case-for-esxi5-netapp-and-cisconetgear-switches\/#primaryimage"},"image":{"@id":"https:\/\/www.softwareab.net\/wordpress\/jumbo-frames-use-case-for-esxi5-netapp-and-cisconetgear-switches\/#primaryimage"},"thumbnailUrl":"https:\/\/www.softwareab.net\/wordpress\/wp-content\/uploads\/2013\/04\/netapp_jumbo_frames-300x260.png","datePublished":"2013-04-18T10:35:11+00:00","dateModified":"2013-04-18T10:46:24+00:00","breadcrumb":{"@id":"https:\/\/www.softwareab.net\/wordpress\/jumbo-frames-use-case-for-esxi5-netapp-and-cisconetgear-switches\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.softwareab.net\/wordpress\/jumbo-frames-use-case-for-esxi5-netapp-and-cisconetgear-switches\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.softwareab.net\/wordpress\/jumbo-frames-use-case-for-esxi5-netapp-and-cisconetgear-switches\/#primaryimage","url":"https:\/\/www.softwareab.net\/wordpress\/wp-content\/uploads\/2013\/04\/netapp_jumbo_frames.png","contentUrl":"https:\/\/www.softwareab.net\/wordpress\/wp-content\/uploads\/2013\/04\/netapp_jumbo_frames.png","width":538,"height":468},{"@type":"BreadcrumbList","@id":"https:\/\/www.softwareab.net\/wordpress\/jumbo-frames-use-case-for-esxi5-netapp-and-cisconetgear-switches\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.softwareab.net\/wordpress\/"},{"@type":"ListItem","position":2,"name":"iscsi","item":"https:\/\/www.softwareab.net\/wordpress\/tag\/iscsi\/"},{"@type":"ListItem","position":3,"name":"Jumbo Frames – Use Case for ESXi5, NetApp, and Cisco\/NetGear Switches"}]},{"@type":"WebSite","@id":"https:\/\/www.softwareab.net\/wordpress\/#website","url":"https:\/\/www.softwareab.net\/wordpress\/","name":"softwareab","description":"Technocratica, Technopolitik, Technophobia","publisher":{"@id":"https:\/\/www.softwareab.net\/wordpress\/#\/schema\/person\/1337443eaeb75104e0410b508e67f600"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.softwareab.net\/wordpress\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":["Person","Organization"],"@id":"https:\/\/www.softwareab.net\/wordpress\/#\/schema\/person\/1337443eaeb75104e0410b508e67f600","name":"Andrew Bruce","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.softwareab.net\/wordpress\/#\/schema\/person\/image\/","url":"https:\/\/www.softwareab.net\/wordpress\/wp-content\/uploads\/2024\/03\/andy-cartoon.jpg","contentUrl":"https:\/\/www.softwareab.net\/wordpress\/wp-content\/uploads\/2024\/03\/andy-cartoon.jpg","width":400,"height":330,"caption":"Andrew Bruce"},"logo":{"@id":"https:\/\/www.softwareab.net\/wordpress\/#\/schema\/person\/image\/"},"description":"Team-oriented systems mentor with deep knowledge of numerous software methodologies, technologies, languages, and operating systems. Excited about turning emerging technology into working production-ready systems. Focused on moving software teams to a higher level of world-class application development. Specialties:Software analysis and development...Product management through the entire lifecycle...Discrete product integration specialist!","sameAs":["http:\/\/cloudraticsolutions.net\/","https:\/\/www.facebook.com\/cloudraticsolutions\/","https:\/\/twitter.com\/realcloudratics"]}]}},"_links":{"self":[{"href":"https:\/\/www.softwareab.net\/wordpress\/wp-json\/wp\/v2\/posts\/121"}],"collection":[{"href":"https:\/\/www.softwareab.net\/wordpress\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.softwareab.net\/wordpress\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.softwareab.net\/wordpress\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.softwareab.net\/wordpress\/wp-json\/wp\/v2\/comments?post=121"}],"version-history":[{"count":4,"href":"https:\/\/www.softwareab.net\/wordpress\/wp-json\/wp\/v2\/posts\/121\/revisions"}],"predecessor-version":[{"id":129,"href":"https:\/\/www.softwareab.net\/wordpress\/wp-json\/wp\/v2\/posts\/121\/revisions\/129"}],"wp:attachment":[{"href":"https:\/\/www.softwareab.net\/wordpress\/wp-json\/wp\/v2\/media?parent=121"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.softwareab.net\/wordpress\/wp-json\/wp\/v2\/categories?post=121"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.softwareab.net\/wordpress\/wp-json\/wp\/v2\/tags?post=121"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}