8 Replies Latest reply on May 10, 2018 8:03 AM by samyar1

    Physical Switch Configuration for vDS

    fr34k7 Lurker

      Hello Folks,

       

      i need your input, i'm new to vDS and at work i've currently doing a migration from vSS to vDS.

      Everything is working fine for the new infrastructure (Dell Poweredge R630 connected to Aruba 5406zl switches via 2 Port 10GBase-T Trunks (LACP))

      vDS has 2 LAG Uplinks

       

      So i wanted to migrate the old Cluster also to the vDS

       

      Old setup was pretty simple:

      HP C3000 Blade Enclosure populated with with 4 passthrough-modules (1 GBit) and 8 BL460c G7 Blades

      Each Blade has minimum 4 nics (2 used for LAN and 2 used for iSCSI traffic on different VSS) each nic (for iscsi or lan) is connected to a different switch to provide redundancy.

       

      i did not change anything on the physical switches just added the hosts to the existing vDS and assigned the two vmnics as uplink for LAG1/0 and LAG1/1 (did not create trunks on the physical switches as both LAN uplink ports are not connected to the same switch).

       

      unfortunatlely this does not work as expected as it seems there is some kind of loop now and i face high packetloss and latency - so as temporary fix i removed one of the vmnics assigned to the uplink

       

      How is the correct configuration on my vDS and  the physical switch?

       

      Will i have to create a new vDS with normal uplinks and use this one instead of the existing vDS with LAG uplinks? or can i fix this behaviour by changing the configuration of my physical switches?

       

      Thanks for your answers

        • 1. Re: Physical Switch Configuration for vDS
          pwilk Hot Shot
          vExpert

          Do you have MLAG enabled on your switches? If not, you shouldn't use LAG in this configuration as LACP protocol is not suited for use in situation where adapters are connected to different switches.

          1 person found this helpful
          • 2. Re: Physical Switch Configuration for vDS
            hussainbte Expert

            put all the active nics in use .. no LAG required..

             

            Use Route Based on Physical NIC Load as the load balancing policy..

             

            this is very simple and equally good..

             

            check the below link for more explanation

             

            https://virtualizationreview.com/articles/2015/03/26/load-balancing-vsphere-vswitch-uplinks.aspx

            1 person found this helpful
            • 3. Re: Physical Switch Configuration for vDS
              daphnissov Champion
              vExpertCommunity Warriors

              As recommended to you by hussainbte, I would also strongly cast a vote for not using any form of LAG if you have an entitlement to use a vDS. LBT is a far better option and requires no physical upstream configuration aside from regularly-provisioned ports and it has even better benefits than LACP or others.

              • 4. Re: Physical Switch Configuration for vDS
                fr34k7 Lurker

                Ok, so my assumption that i have to create an additional vDS with normal uplinks instead of LAG uplinks for those servers was correct.

                I'll create a copy of the existing vDS, change the uplink type and migrate a few hosts some time next week.

                Hopefully then everything is working as intended.

                 

                Thanks a lot for your answers!

                • 5. Re: Physical Switch Configuration for vDS
                  fr34k7 Lurker

                  Configured LAG on the vDS because all uplinks on the newer servers are connected to the same switch

                  • 6. Re: Physical Switch Configuration for vDS
                    daphnissov Champion
                    vExpertCommunity Warriors

                    That's fine, but it's not required, even if they all are connected to the same switch it doesn't require a LAG.

                    • 7. Re: Physical Switch Configuration for vDS
                      fr34k7 Lurker

                      Ok i thought so because without LACP Uplinks i had troubles with packetloss and high latency which disappeared after i set it to LACP and changed the uplink type

                      • 8. Re: Physical Switch Configuration for vDS
                        samyar1 Lurker

                        How to Configure a Private VLAN (PVLAN) and Port Group on your vSphere Distributed Switch (vDS) in VMware vSphere ESXi 5.x : Types of PVLANS : Promiscuous : Primary PVLAN - Default PVLAN and can communicate with any port in the VLAN. Isolated : Secondary PVLAN - Only able to communicate with the promiscuous port. Community : Secondary PVLAN - Able to communicate with other ports on the VLAN and the promiscuous port.     Set the physical switch port to trunk and any PVLANs added on your vDS need to be added to the trunk on the physical switch port.     In the vSphere Client, go to the home screen and click on Networking     Right click on the distributed switch you want to configure a PVLAN and then click on Edit Settings     Click on the Private VLAN tab     Under Primary private VLAN ID, click on [Enter a private VLAN ID here] to input your primary PVLAN ID. NOTE: This will be your promiscuous PVLAN by default     To add secondary PVLANS, click on [Enter a private VLAN ID here] under Secondary private VLAN ID and input a PVLAN ID     From the Type dropdown, choose whether you want an Isolated or Community PVLAN     Click on the OK button     Right click on your distributed switch and click on New Port Group     Input your name for your port group     From the VLAN type dropdown, choose Private VLAN     Choose the Primary VLAN you want to use for this port group and then click on the Next button     Review all of the settings and click on the Finish button Quick Tips content is self-published by the Dell Support Professionals who resolve issues daily. In order to achieve a speedy publication, Quick Tips may represent only partial solutions or work-arounds that are still in development or pending further proof of successfully resolving an issue. As such Quick Tips have not been reviewed, validated or approved by Dell and should be used with appropriate caution. Dell shall not be liable for any loss, including but not limited to loss of data, loss of profit or loss of revenue, which customers may incur by following any procedure or advice set out in the Quick Tips. محصولات بازی | طراحی فروشگاه اینترنتی