Skip to main content

vSphere Distributed Switch Part 1 – Understanding the Architecture of Standard Switch and Distributed Switch

vSphere Standard Switches (vSS) provides network connectivity to hosts and virtual machines. Standard switch can bridge traffic internally between virtual machines in the same VLAN and also link to external networks. Standard switches uses physical Network adapters (NICs) of the ESXi hosts as uplink ports on the standard switch which helps the virtual machines to talk to the outside network. Virtual Machines have it s virtual network adapters (vNICs) that will connect to the port groups on the standard switches. Every port group can use one or more physical NICs of ESXi host attached to it to handle its network traffic.For the Port group with no physical NIC connected to it will allow virtual machines to communicate only with the virtual machines connected on the same port group and will not allow to communicate to external network.
In simple terms, vSphere Standard Switches need to be created on each individual hosts. For example, If you have 2 ESXi host in the cluster, All the port groups (for example Management, vMotion, Test environment and Production) needs to be created same as exact name on both the ESXi hosts for the vMotion to work between the ESXi hosts in the cluster.
vSphere Distributed Switch (vDS) provides centralized management and monitoring of the network configuration of all the ESXi hosts that are associated with the dvswitch. Distributed switch can be created and configured at vCenter server system level and all its settings are propagated to all the hosts that are associated with the switch. dvSwitch is designed to create a consistent switch configuration across every hosts in the datacenter. Network configuration and management for all the hosts that associated with the switch can be performed centralized on the vCenter server system. vDS is only available as part of vSphere Enterprise plus licensing and it’s not created by default.The dvswitch consists of two components, the control plane and the I/O or data plane. vSphere Distributed Switch is also referred as  vDS (vSphere Distributed Switch and dvs (Distributed virtual switch).
The Control plane
Control plane exists at vCenter server and It is responsible for managing and configuring the dvswitch  dvport groups,dvports, uplinks,VLANs,PVLANs and NIC teaming,etc. dvswitch is nothing but a configuration template used to configure the settings on each host which are connected to the dvswitch.
The Data Plane (I/O plane)
Data plane is hidden switch that exists on each host and it is responsible for forwarding the data packets to the relevant uplinks. Because of  this data plane (hidden switch created at each host) network communication continues to work even if your vCenter is down.
I hope this post helps you to understand the architecture of standard switch and distributed switch. Thanks for reading !!!!

Comments

Post a Comment

Popular posts from this blog

  Issue with Aria Automation Custom form Multi Value Picker and Data Grid https://knowledge.broadcom.com/external/article?articleNumber=345960 Products VMware Aria Suite Issue/Introduction Symptoms: Getting  error " Expected Type String but was Object ", w hen trying to use Complex Types in MultiValue Picker on the Aria for Automation Custom Form. Environment VMware vRealize Automation 8.x Cause This issue has been identified where the problem appears when a single column Multi Value Picker or Data Grid is used. Resolution This is a known issue. There is a workaround.  Workaround: As a workaround, try adding one empty column in the Multivalue picker without filling the options. So we can add one more column without filling the value which will be hidden(there is a button in the designer page that will hide the column). This way the end user will receive the same view.  
Post a Comment
Read more

57 Tips Every Admin Should Know

Active Directory 1. To quickly list all the groups in your domain, with members, run this command: dsquery group -limit 0 | dsget group -members –expand 2. To find all users whose accounts are set to have a non-expiring password, run this command: dsquery * domainroot -filter “(&(objectcategory=person)(objectclass=user)(lockoutTime=*))” -limit 0 3. To list all the FSMO role holders in your forest, run this command: netdom query fsmo 4. To refresh group policy settings, run this command: gpupdate 5. To check Active Directory replication on a domain controller, run this command: repadmin /replsummary 6. To force replication from a domain controller without having to go through to Active Directory Sites and Services, run this command: repadmin /syncall 7. To see what server authenticated you (or if you logged on with cached credentials) you can run either of these commands: set l echo %logonserver% 8. To see what account you are logged on as, run this command: ...
Post a Comment
Read more
  The Guardrails of Automation VMware Cloud Foundation (VCF) 9.0 has redefined private cloud automation. With full-stack automation powered by Ansible and orchestrated through vRealize Orchestrator (vRO), and version-controlled deployments driven by GitOps and CI/CD pipelines, teams can build infrastructure faster than ever. But automation without guardrails is a recipe for risk Enter RBAC and policy enforcement. This third and final installment in our automation series focuses on how to secure and govern multi-tenant environments in VCF 9.0 with role-based access control (RBAC) and layered identity management. VCF’s IAM Foundation VCF 9.x integrates tightly with enterprise identity providers, enabling organizations to define and assign roles using existing Active Directory (AD) groups. With its persona-based access model, administrators can enforce strict boundaries across compute, storage, and networking resources: Personas : Global Admin, Tenant Admin, Contributor, Viewer Projec...
Post a Comment
Read more