Lab: Deploy vDS & Configure NIC Teaming
Objectives
- Build a vDS with two uplinks and distributed port groups for Management, vMotion and vSAN (Obj 4.1)
- Set teaming per traffic type: load-based for VM/vMotion, explicit failover order for Management and vSAN
- Migrate VMkernel adapters to the vDS without losing management access
- Prove the MTU end to end with vmkping -I <vmk> -d -s 8972
Prerequisites
Holodeck VVF 9.0 instance deployed and healthy
Lab Environment
Holodeck vSphere Foundation 9.0 instance (New-HoloDeckInstance -VVF; -vSANMode OSA by default, ESA where the physical layer supports it): vCenter managing one vSAN cluster of nested ESX hosts, plus VCF Operations. VVF has no SDDC Manager and no NSX. LACP and physical-switch checks are physical-lab only; Holodeck cannot provide them.
Credentials
| System | Username | Password |
|---|---|---|
| vCenter | administrator@vsphere.local | Holodeck documented default (Post Deployment table) |
| Nested ESX hosts | root | Holodeck documented default (Post Deployment table) |
Tasks
Task 1 Deploy vDS & Configure NIC Teaming
Create a new vDS at the current version: vCenter UI → Networking → New Distributed Switch, 2 uplinks; set MTU 9000 on the switch (right-click the switch → Settings → Edit settings → Advanced tab → MTU (Bytes); VCF 9.0.1 docs p.5629)
Create the distributed port groups first: Management, vMotion, vSAN (VLAN 100)
Add the hosts to the vDS: assign vmnics to the uplinks and migrate vmk0 to Management; then create the vMotion vmk on the vMotion TCP/IP stack and the vSAN vmk (MTU 9000)
Set teaming per port group: Route based on physical NIC load for VM and vMotion port groups; explicit failover order (uplink1 active, uplink2 standby) for Management and vSAN
Verify in the vSphere Client → vDS → Configure → Topology, and in Health Check, that both uplinks are up and the VLAN and MTU health checks pass. (Optional, physical lab only: LACP through a LAG set as the sole active uplink — the LAG's load-balancing mode then overrides the port group policy, VCF 9.0.1 docs p.1627; VCF design treats host link aggregation as supported but not recommended, p.1105. Not available in Holodeck.)
Test: vmkping -I vmk2 -s 8972 -d <peer_host_vsan_ip> from each host to every other host (vmk2 = the vSAN vmk; -I takes the interface name, not an IP; -d sets don't-fragment so the 8972-byte payload proves MTU 9000 end-to-end — VCF 9.0.1 docs p.1642); expect under 1 ms RTT between hosts in a single-site cluster (vSAN network requirements: 'Maximum of 1 ms RTT for single site (non-stretched) vSAN clusters')
Validation Gate
Check: After deploying VDS with two uplinks, verify: (a) both uplinks show 'Up' status, (b) VMkernel adapters are on correct port groups, (c) ping test succeeds on management, vMotion, and vSAN networks
Expected: All three network types respond to ping, both uplinks show connected, and teaming policy matches design specification
Common Errors
Final Validation
Gate: every check below passes with the evidence recorded in the lab log.
✓ Uplinks → Both uplinks Up on every host
✓ VMkernel placement → vmk0 on Management, vMotion vmk on the vMotion TCP/IP stack, vSAN vmk on the vSAN port group
✓ Connectivity → vmkping succeeds on all three networks, including the jumbo test on vSAN
Cleanup / Restore
• Leave the vDS in place for later labs, or migrate the VMkernel adapters back before deleting it
Design Reflection (VCDX)
Network design is always challenged in VCDX defense. Panelists ask why you chose specific teaming policies, how you handle NIC failure, and what happens if a physical switch fails. Know your uplink mapping and failover behavior.
Requirements
- Deploy VDS with appropriate teaming policy per traffic type
- Configure VLAN trunking to match physical switch
- Migrate VMkernel adapters from VSS to VDS without losing connectivity
Constraints
- Physical switch must trunk the required VLANs
- VSS to VDS migration must maintain management connectivity throughout
Assumptions
- Physical NICs are correctly cabled to appropriate switch ports
- MTU 9000 is configured end-to-end on the physical network for vSAN traffic (VVF has no NSX overlay)
Risks
- Management network loss during VSS-to-VDS migration
- Silent packet drops from VLAN mismatch between VDS and physical switch