Download as PDF, PPTX
Uploaded byVMworld
VMworld 2014: vSphere Distributed Switch
This document summarizes a technical deep dive presentation on vSphere Distributed Switches. It discusses the requirements, construction, alternatives, tips and real world use cases of vSphere Distributed Switches. The presenters were Jason Nash from Varrow and Chris Wahl from AHEAD, and they covered topics such as migration from standard to distributed switches, mixing 1Gb and 10Gb networking, and techniques for bandwidth management.
More Related Content
Similar to VMworld 2014: vSphere Distributed Switch
![Getting Started with Apache Spark: Big Data Made Simple [Free Meetup]](https://cdn.slidesharecdn.com/ss_thumbnails/apachesparkgettingstarted-260203175547-8361bcc3-thumbnail.jpg?width=640&height=640&fit=bounds)
VMworld 2014: vSphere Distributed Switch
- 1. vSphere Distributed Switch: TechnicalDeep Dive NET2745 Jason Nash, Varrow Chris Wahl, AHEAD
- 2.
- 3. Senior Solutions Architect@ AHEAD VCDX #104, vExpert Blogger – WahlNetwork.com Author – Networking for VMware Administrators Author – Pluralsight IT Pro training CCNA Data Center, vCloud Director Host – VUPaaS and IT Engine Builders Podcasts
- 4. Chief Technology Officer@ Varrow VCDX #49, vExpert Blogger – JasonNash.com Author – Pluralsight IT Pro training XtremIO, Cisco UCS, Nexus 1000v, vC Ops, + more
- 6. • Overview • Requirements • Construction • Alternatives • Tips • Real World Use Cases
- 8. ü Enterprise Pluslicensing ü VMware skillset ü ESXi host versions ≥ to VDS version
- 10. o Lives invCenter o All 5.1+ features are Web Client only L o VDS is a Data Center level object o VDS database syncs with each ESXi host
- 12. o Lives onthe ESXi host o We suggest • Use Elastic ports • Connect uplinks (vmnics) to a single network segment o If you need multiple network segments • Possible, but requires workarounds
- 13.
- 14.
- 15. o vSphere StandardSwitch (VSS) o Cisco Nexus 1000v o IBM 5000V aka “Chupacabra”
- 16. ü Use 802.1Qtags for port groups ü At least 2 vmnics (uplinks) per VDS ü A 2x 10 GbE configuration can work fine ü Put QoS tagging in VDS or physical, not both ü Use descriptive naming everywhere o No one knows what “dvPortGroup-1” does
- 18. Migration VSS to VDS Mixing1Gb and 10Gb Hosts Handling vMotion Saturation vSphere Replication Bandwidth Quality of Service Tagging Load Based Teaming vs Link Aggregation
- 19. Triggers: Ø Licensing (purchasedEnterprise Plus) Ø Consume features found only in VDS Ø Reduce operational overhead Ø Separate control planes and related responsibilities
- 20. Tips and Advice: Ø Have a detailed plan in place Ø Test the process on a single host with non-prod VMs Ø Test network convergence time and ping drops Ø Become comfortable with the steps Ø Put in a change control Ø Execute change during maintenance window
- 21. Standard Switch Distributed Switch vmnic0 vmnic1 VM Port Group VM VMKs VMK Port Group VMPort Group VMK Port Group
- 22. Standard Switch Distributed Switch vmnic0 VM Port Group VM VMKs VMK Port Group VMPort Group VMK Port Group vmnic1
- 23. Standard Switch Distributed Switch vmnic0 VM Port Group VM VMK Port Group VMPort Group VMK Port Group vmnic1VMKs
- 24. Standard Switch Distributed Switch vmnic0 VM Port Group VMK Port Group VMPort Group VMK Port Group vmnic1VMKs VM
- 25. Standard Switch Distributed Switch VM Port Group VMK Port Group VMPort Group VMK Port Group vmnic1VMKs VM vmnic0
- 26.
- 27. Triggers: Ø Purchase ofnew server / switch hardware Ø Staged migration to 10 GbE Ø Data Center transformation process
- 28. Tips and Advice: Ø Use a single network segment Ø Use a single VDS Ø Hosts should be entirely 1 GbE or 10 GbE Ø VM Traffic can traverse any uplink Ø Control teaming policies on VMK networks
- 29. dvUplinks VM Port Groups VMK1Gb (Mgmt, vMotion, etc) ESXi 1 Gb vmnic1 vmnic2 vmnic3 vmnic4 dvUplink1 1 2 3 4 1 2 3 4 dvUplink2 dvUplink3 dvUplink4 vmnic0 was left off to make the numbers match
- 30. dvUplinks VM Port Groups ESXi1 Gb vmnic1 vmnic2 dvUplink1 VMK 10Gb (Mgmt, vMotion, etc) 1 2 1 2 dvUplink2 dvUplink3 dvUplink4
- 31. dvUplinks VM Port Groups VMK1Gb (Mgmt, vMotion, etc) ESXi 1 Gb vmnic1 vmnic2 vmnic3 vmnic4 ESXi 1 Gb vmnic1 vmnic2 dvUplink1 VMK 10Gb (Mgmt, vMotion, etc) 1 2 3 4 1 2 3 4 1 2 dvUplink2 dvUplink3 dvUplink4
- 32. dvUplinks VM Port Groups ESXi1 Gb vmnic1 vmnic2 dvUplink1 1 2 3 4 dvUplink2 dvUplink3 dvUplink4 No Link
- 33. Triggers: Ø Multiple hostsmigrate VMs to a single host Ø 2+ host maintenance mode Ø DRS migrations Ø DRS affinity and anti-affinity rules
- 34. Tips and Advice Ø Know how Ingress vs Egress works in VDS Ø Use NIOC for source-based control Ø Use Traffic Shaping for destination-based control
- 38. Triggers: Ø Sharing aWAN pipe with other traffic Ø Paying for bandwidth at certain % of peak Ø Multiple VR tenants between data centers Ø Contention with other backup or replication jobs
- 39. Tips and Advice: Ø Use NIOC with Limits (per vmnic) Ø Use Network Resource pool for VR Ø Alternative is to limit based on VR ports
- 41. Ø Run scriptfor different limits during day/night Ø Requires PowerCLI and vCenter service account Short URL = http://goo.gl/dAgqBz
- 42. Triggers: Ø Tag trafficfor various SLAs Ø Use L2 Priority Code Point (PCP) Ø Use L3 Differentiated Services Code Point (DSCP) Ø Data Center Bridging extensions in 802.1 Ø Priority-based Flow Control (PFC) – 802.1Qbb Ø Enhanced Transmission Selection (ETS) – 802.1Qaz
- 43. Tips and Advice: Ø KISS: QoS solves contention problems Ø Pick a place to tag traffic – virtual or physical Ø Try not to enforce QoS in too many ways Ø Use clearly defined tagging when needed Ø Avoid hard limits on traffic flows
- 45. 0 1 23 4 5 6 7
- 49. Triggers: Ø Network andServer teams not cooperating Ø Pop out of those silos! Ø Poor convergence times during link failover Ø Poor use of uplink throughput Ø Excessive Topology Change Notifications (TCN) Ø Excessive vMotion activity
- 50. Load Distribution Ø Assigningworkloads to uplinks based on identifiers Ø Example: L2, L3, L4, and VLAN values Load Balancing Ø Assigning workloads to uplinks based on traffic Ø Example: “Route based on physical NIC load”
- 51. Load Distribution Ø NoiSCSI Binding or Multi-NIC vMotion Ø Potential Layer 2 Path Optimization Load Balancing Ø Imbalanced NIC saturation Ø Network can tolerate TCN and MAC table updates
- 53. Load Distribution Ø LinkAggregation Group (LAG) Ø Static (EtherChannel) or Dynamic (LACP) Load Balancing Ø Set PG to Route based on physical NIC load Ø Also known as Load Based Teaming (LBT)
- 62.
- 63.
- 64. Fill out asurvey Every completed survey is entered into a drawing for a $25 VMware company store gift certificate
- 65. vSphere Distributed Switch: TechnicalDeep Dive NET2745 Jason Nash, Varrow Chris Wahl, AHEAD