Skip to main content

vSphere Distributed Switch Part 3 – Difference between Standard Switch and Distributed switch

I have been asked by lot of people during my training sessions about the difference’s between standard and distributed switch. I decided it’s the time to post the series of posts about distributed switch to help the readers to learn about distributed switch. In this post, I have explained the major differences about standard and distributed switch.
                             VS
Features
Standard Switch
Distributed Switch
Management
Standard switch needs to managed at each individual
host level
Provides centralized management and
 monitoring of the network configuration
 of all the ESXi hosts that are
associated with the dvswitch.
Licensing
Standard Switch is available for all
 Licensing Edition
Distributed switch is only available for
enterprise edition of licensing
Creation & configuration
Standard switch can be created and
 configured at ESX/ESXi host level
Distributed switch can be created and configured
 at the vCenter server level
Layer 2 Switch
Yes, can forward Layer 2 frames
Yes, can forward Layer 2 frames
VLAN segmentation
Yes
Yes
802.1Q tagging
Can use and understand 802.1q
VLAN tagging
Can use and understand 802.1q
VLAN tagging
NIC teaming
Yes, can utilize multiple uplink to
 form NIC teaming
Yes, can utilize multiple uplink to form
 NIC teaming
Outbound Traffic Shaping
Can be achieved using standard switch
Can be achieved using distributed switch
Inbound Traffic Shaping
Not available as part of standard
switches
Only possible at distributed switch
VM port blocking
Not available as part of standard
 switches
Only possible at distributed switch
Private VLAN
Not available
PVLAN can be created as part of dvswitch. 3 types of PVLAN(Promiscuous, 
Community and Isolated)
Load based Teaming
Not available
Can be achieved using distributed switch
Network vMotion
Not available
Can be achieved using distributed switch
Per Port policy setting
Policy can be applied at switch
and port group
Policy can be applied at switch, port group and even per port level
NetFlow
Not available
Yes
Port Mirroring
Not available
Yes
I hope this is informative for you. Thanks for reading !!!!

Comments

Popular posts from this blog

Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware

 🔹 Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware ⸻ 1️⃣ Memory Ballooning (vmmemctl) Ballooning is the first memory reclamation technique used when ESXi detects memory pressure. ➤ Step-by-Step: How Ballooning Works  1. VMware Tools installs the balloon driver (vmmemctl) inside the guest OS.  2. ESXi detects low free memory on the host.  3. ESXi inflates the balloon in selected VMs.  4. Balloon driver occupies guest memory, making the OS think RAM is full.  5. Guest OS frees idle / unused pages (because it believes memory is needed).  6. ESXi reclaims those freed pages and makes them available to other VMs. Why Ballooning Happens?  • Host free memory is very low.  • ESXi wants the VM to release unused pages before resorting to swapping. Example  • Host memory: 64 GB  • VMs used: 62 GB  • Free: 2 GB → ESXi triggers ballooning  • VM1 (8 GB RAM): Balloon inflates to 2 GB → OS frees 2 GB → ESXi re...

ESXi Host Troubleshooting Checklist

  🛠️ ESXi Host Troubleshooting Checklist (With Complete Log Locations) ✅ 1. Host Status & Connectivity Check host state in vCenter (Connected / Not Responding / Disconnected) Review CPU, RAM, and datastore usage Validate HA/DRS recommendations ✅ 2. Hardware Health Monitor hardware sensors (CPU, DIMMs, fans, PSU, RAID) Check RAID controller logs via vendor tools View hardware status in: vCenter → Monitor → Hardware Health DCUI → Hardware Status ✅ 3. Network Validation Verify vSwitches, Port Groups, NIC teaming, VLAN tagging Check vmkernel ports (mgmt, vMotion, iSCSI, vSAN) Test reachability using: Shell vmkping < IP > Show more lines Validate physical NIC status and link speed ✅ 4. Storage & Datastore Checks Confirm datastore accessibility Rescan storage adapters (iSCSI/FC/NFS) Validate multipathing (Round Robin / Fixed / MRU) Check datastore latency with esxtop ✅ **5. Critical Logs & Their Locations (Full List) Here are key ESXi log files that every VMware adm...
  vCenter Troubleshooting Tips, Common Issues & Log Locations 🚀 1. General Troubleshooting Approach A. Check service health first For vCenter Server Appliance (VCSA): Shell https : / / < vcenter - FQDN > : 5480 Show more lines Go to Services → Health to verify: vCenter Server ESXi hosts vSphere Client DNS, NTP, DB connections vpxd, vpxd-svcs, vsphere-ui B. DNS & NTP checks vCenter is highly dependent on correct DNS & time sync. Check: Shell nslookup < vcenter - fqdn > nslookup < esxi - host - fqdn > Show more lines Time drift > 5 minutes causes: Login failures vpxd crashes PSC authentication issues C. Check storage/database health Slow DB/storage = UI slow, tasks hung. For VCSA: Shell df - h du - sh / storage / log / * / var / log Show more lines Free up space if partitions hit >80%. D. Restart critical services safely On VCSA: Shell service - control - - status service - control - - stop - - all service - control - - start - - all ...