2 Replies Latest reply on Nov 12, 2019 1:21 AM by Amin Masoudifard

    dvSwitch Doubt

    txemavtr Lurker
    txemavtr Nov 11, 2019 10:57 PM

      Hello, everybody;

       

       

      I had a doubt that I could not solve by looking at the technical documentation of VmWare, I do not know if there will be someone here who can solve the doubt.

       

       

      We are going to deploy in the company 3 ESXi with version 6.5 and we are going to subway in Cluster. We plan to create 2 Virtual Switch distributed and the Uplink of the 3 ESXi will be connected to a pair of Switch Cisco Catalyst 9500 that will be in vStack. 4 physical links of each ESXi will go an uplink associated to a distributed virtual switch and the other two (are 6 physical links per server) will go associated to another distributed virtual switch.

       

       

      The doubt we have is if for each ESXi we have to create a port channel in the Cisco Switch, that would be 3 + 3 Port-Channel (one for each dvSW) or duties to create only in one port channel, since in theory the Virtual Switch distributed that share the 3 ESXi are "logically" the same Switch.

       

       

      From this we have another question, what kind of information do the ESXi share about the distributed virtual switches, that is .... if there is a Spanning-Tree loop for example, is this information shared? ... What we have a certain "fear" is if there is a bad configuration of a port channel in the switch that does not affect the entire distributed virtual switch.

       

       

       

       

       

      Thank you in advance.

       

       

       

       

       

      Greetings

      • 98 Views
      • Tags:
        • 1. Re: dvSwitch Doubt
          scott28tt Champion
          Community WarriorsVMware EmployeesUser Moderators
          scott28tt Nov 12, 2019 12:04 AM (in response to txemavtr)

          Moderator: Moved to vSphere vNetwork

          • 2. Re: dvSwitch Doubt
            Amin Masoudifard Expert
            Amin Masoudifard Nov 12, 2019 1:21 AM (in response to txemavtr)

            Generally, VDS acts as a proxy switch for each connected ESXi host to it. So when you create a link aggregation group (port-channel), a LAG object (with the same number of ports) is also created on the proxy switch of every host. As VMware mentioned on the vSphere Networking guide :  "On a host proxy switch, you can connect one physical NIC to only one LAG port. On the distributed switch, one LAG port can have multiple physical NICs from different hosts connected to it."

            and also about LACP configuration on physical networking, you should know for each host you must create a separate LACP port-channel on the physical switch. The LAG that is created on the distributed switch must have equal uplinks as the number of ports that have been defined on LACP of physical switch. (also Port Speed and Duplex config and Hashging algorithm must be same on Physical and Virtual)

            Please mark my comment as the Correct Answer if this solution resolved your problem