3 Replies Latest reply: Sep 15, 2014 12:48 PM by Ray Olander RSS

    VMware dvSwitch Design Question

    Jeremy C. Newbie

      Hi,

       

      I am a future (proud !) owner of a CS210, and I plan to refresh my vSphere design at the same time by switching to dvSwitch.

      So, here is my question concerning dvSwitch and LACP:
      I have 3 esxi with 8 gigabit cards each and a stack of 4 Cisco 3750G.
      I'll use iSCSI (prod) and NFS (backup) as storage protocols.
      I'll also plan to use 2 dvSwitch:

      • 1 with 4 uplinks using LACP for VM traffic, VM management, NFS, and vMotion,
      • 1 with 4 uplinks using iSCSI bindings for iSCSI (of course)

      Is there any “better”/more optimized designs (like only 1 dvSwitch with 8 uplinks and overriding failover order for iSCSI) ?
      Note: 10 gigabits network cards are not an affordable solutions for the moment.
      Thanks for any advice.

       

      Jeremy

        • Re: VMware dvSwitch design question
          Phil Davies Adventurer

          Jeremy,

           

          May be worth having a read of the following article (non-Nimble) about dvSwithes first:

          http://www.yellow-bricks.com/2009/09/24/dvswitch/

          Some discussion on pros/cons.

           

          Can't say I've seen anything specifically about dvSwitches with Nimble.

           

          Given some of the comments in the post I'd probably avoid using 1 dvSwitch with 8 uplinks and overriding failover order for iSCSI and have some (if only logical) seperation between iSCSI traffic and other traffic.

           

          Have you read the Nimble VMWare integration guide on InfoSight:

          https://infosight.nimblestorage.com/cgi-bin/viewPDFFile?ID=ncm/2-1-0-0/Nimble_OS_2_1_3_vmware_integration_guide_2_1_x_PN970_0015_002.pdf

          This gives 2 optons with standard vSwitches, using one vSwitch for all iSCSI with multiple vmnics (and overriding failover order) OR using multiple vSwitches (one vmnic per switch, no overriding failover order required).

           

          If you are using dvswitches then I assume you are running Enterprise Edn of ESX, so also have a look at the Nimble Connection Manager (NCM) where you can use a Nimble PSP, full details in the document link above.

           

          Regards

          Phil

          • Re: VMware dvSwitch Design Question
            Ray Olander Wayfarer

            Hi Jeremy,

             

             

            While there are a number of design criteria to consider for your question, I'll mention just a couple for now. Be aware that VMware recommends putting standard 1500 byte frames on a separate switch than jumbo frames (if you're using jumbo frames). I can't find my reference for this at the moment, but I'm fairly sure that goes for versions of ESXi below v5.5. It will work with both frame sizes on one switch, it's just that it is possible to have problems. Also be aware that the 3750G ASIC, which is the hardware-level switching that happens before the IOS software gets to examine the traffic, has a surprisingly low throughput capability and you may have microburst problems that cause the ASIC to drop packets (as observed in commands such as "sh platform port-asic stats drop gigabitEthernet x/x/x") before QoS gets to see it.

             

            Ray