Troubleshoot Hyper-V VLAN connectivity by validating VM VLAN IDs, access versus trunk configuration, SET and physical switch settings.
Start with Identify the VLAN model 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.
Identify the VLAN model
Determine whether the VM requires access, trunk or another supported VLAN configuration.
Check the VM VLAN
Verify the VLAN mode and VLAN ID assigned to the VM network adapter.
Check the virtual switch
Confirm the VM is connected to the intended external virtual switch and SET configuration.
Check the physical switch port
Check whether the physical switch port is configured as access or trunk with the required VLANs.
Test from the guest
Test the guest address, gateway and application connectivity after confirming VLAN configuration.
Verify persistence
Verify the configuration remains correct after VM restart, host restart or migration.
Useful commands
Run these checks from an appropriate administrative session and replace example values with your environment.
VM VLAN
Get-VMNetworkAdapterVlan -VMName <vm-name>Switch configuration
Get-VMSwitchQuick troubleshooting path
Use this sequence to isolate the failing dependency before changing production configuration.
- Identify the VLAN model → Determine whether the VM requires access, trunk or another supported VLAN configuration.
- Check the VM VLAN → Verify the VLAN mode and VLAN ID assigned to the VM network adapter.
- Check the virtual switch → Confirm the VM is connected to the intended external virtual switch and SET configuration.
- Check the physical switch port → Check whether the physical switch port is configured as access or trunk with the required VLANs.
- Test from the guest → Test the guest address, gateway and application connectivity after confirming VLAN configuration.
- Verify persistence → Verify the configuration remains correct after VM restart, host restart or migration.
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