Troubleshoot Hyper-V Switch Embedded Teaming problems involving physical NICs, virtual switches, VLANs and connectivity.
Start with Check the virtual switch and work through the six diagnostic checks in order.
Record results before changing configuration and validate the original symptom after each controlled change.
Quick checks
Start with the basic checks in this runbook before moving to deeper troubleshooting.
- Confirm the affected service or component is available.
- Check recent configuration or connectivity changes.
- Run the relevant commands and compare the result with the expected state.
Check the virtual switch
Confirm the Hyper-V switch uses the intended Switch Embedded Teaming configuration.
Check member NICs
Verify all physical member adapters are present, connected and operational.
Check VLAN configuration
Validate VM and management VLAN assignments against the network design.
Check physical switch ports
Confirm upstream switch ports allow the required VLANs and match the teaming configuration.
Check adapter health
Review physical NIC state and interface counters for link or hardware problems.
Retest after one controlled change
Make one controlled configuration change at a time and verify host and VM connectivity.
Useful commands
Run these checks from an appropriate administrative session and replace example values with your environment.
SET members
Get-VMSwitchTeam -Name <switch-name>Physical adapters
Get-NetAdapterQuick troubleshooting path
Use this sequence to isolate the failing dependency before changing production configuration.
- Check the virtual switch → Confirm the Hyper-V switch uses the intended Switch Embedded Teaming configuration.
- Check member NICs → Verify all physical member adapters are present, connected and operational.
- Check VLAN configuration → Validate VM and management VLAN assignments against the network design.
- Check physical switch ports → Confirm upstream switch ports allow the required VLANs and match the teaming configuration.
- Check adapter health → Review physical NIC state and interface counters for link or hardware problems.
- Retest after one controlled change → Make one controlled configuration change at a time and verify host and VM connectivity.
What good troubleshooting looks like
Good infrastructure troubleshooting is evidence-driven. Capture the original state, test the dependency that can prove or disprove your hypothesis, make the smallest safe change and repeat the original test.
Symptom → hypothesis → direct test → result → controlled change → validation → documentation