Academy/vSphere Foundation 9.0 Administrator (2V0-16.25)/Lab: Deploy vDS & Configure NIC Teaming
This lab targets VCF 9.0

Lab: Deploy vDS & Configure NIC Teaming

VCF 9.0Intermediatevcp-foundation⏱ 90 min

VVF 9.0 administrator lab (2V0-16.25). Built for a Holodeck VVF instance.

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

SystemUsernamePassword
vCenteradministrator@vsphere.localHolodeck documented default (Post Deployment table)
Nested ESX hostsrootHolodeck documented default (Post Deployment table)

Tasks

Task 1 Deploy vDS & Configure NIC Teaming

VDS deployment and NIC teaming are foundational networking skills. Incorrect teaming policy causes network outages; incorrect VLAN trunking causes silent packet drops. Always verify connectivity after configuration changes.
Step 1

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)

Step 2

Create the distributed port groups first: Management, vMotion, vSAN (VLAN 100)

Step 3

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)

Step 4

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

Step 5

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.)

Step 6

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

Selecting wrong NIC teaming policy for the traffic type
Fix: Route based on originating virtual port is the default on both the standard and distributed switch; Route based on physical NIC load (distributed switch only) must be selected explicitly and rebalances when an uplink passes 75% utilisation. Originating port pins each VM to one uplink — simpler but can leave uplinks unbalanced. Use load-based teaming for VM and vMotion port groups; for vSAN, which does not load-balance across teamed NICs, prefer an explicit active/standby failover order; use originating port for management (predictable failover).
Not configuring failover order correctly for active/standby
Fix: Active uplinks carry traffic; standby activates only when all active uplinks fail. A common mistake: placing all NICs in active without understanding the load distribution implications, or placing the wrong NIC in standby (e.g., the 25GbE NIC as standby while the 10GbE is active).
Forgetting to migrate VMkernel adapters when switching from VSS to VDS
Fix: VMkernel adapters (management, vMotion, vSAN) must be migrated from VSS to VDS. If you delete the VSS first, you lose management connectivity to the host. Always migrate VMkernels to VDS first, verify connectivity, then remove VSS.
VLAN trunk not configured on physical switch port
Fix: VDS port groups with VLAN tags only work if the physical switch port is configured as a trunk carrying those VLANs. A VDS port group tagged VLAN 100 on an access port (VLAN 200) will drop all traffic. Verify physical switch configuration matches VDS VLAN assignments.

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

⚠ Known Pitfalls

Deleting VSS before migrating VMkernel adapters to VDS — this disconnects the host from vCenter.
Assuming VDS VLAN tagging works without verifying physical switch trunk configuration.

References

Was this page useful?
Type to search. ↑ ↓ to move, Enter to open, Esc to close.