1/4
Troubleshooting Mindset Series #018: When a VM Works on One Host but Fails After Migration
  

rizzuan Lv3  Posted 2026-Sep-17 11:00

Scenario / Issue Description
A VM is running normally on one HCI host, but after being migrated to another host, users start experiencing network connectivity issues.
The VM configuration has not changed.
At this point, it is easy to suspect the VM, guest OS, or application.
But if the problem follows the host, the investigation should move toward the host-specific network path.

Troubleshooting Approach
Instead of immediately changing the VM configuration, compare the working and affected host.
1. Confirm the behaviour
First establish:
  • Does the VM work normally on Host A?
  • Does the issue appear after moving to Host B?
  • Does moving it back to Host A restore connectivity?

This gives us an important troubleshooting clue.

2. Compare the virtual network configuration
Check whether both hosts have consistent:
  • Virtual switch configuration
  • VLAN configuration
  • vNIC/network mapping
  • Network segment
  • MTU settings


A configuration difference between hosts can produce a problem that appears to be VM-related.


3. Check the physical uplink
Compare the affected host with the healthy host:
  • Physical NIC status
  • NIC bonding/team configuration
  • Uplink connectivity
  • Switch port configuration
  • VLAN allowed on the switch port



4. Check the physical switch
If the HCI host configuration looks correct, verify the corresponding switch ports.
Look for differences in:
  • VLAN
  • Trunk/access configuration
  • LACP
  • Port errors
  • Link flaps
  • STP events


5. Compare before making changes
If possible, compare:
Working Host → Affected Host
Rather than changing multiple settings at once.
The difference between the two hosts can often provide the strongest clue.

Common Mistakes
“The VM configuration is correct, so the VM must be the problem.”
When the same VM behaves differently depending on which HCI host it runs on, the host-specific network path deserves attention.
Changing the VM configuration repeatedly may only hide the real difference.
Troubleshooting Mindset
When a problem changes after VM migration, ask:
“What changed because the VM moved?”
The VM may have moved to a different:
vSwitch → vNIC path → Physical NIC/Uplink → Switch Port
That difference is often more useful than repeatedly checking the VM itself.

Key Takeaway
When the same VM behaves differently on different hosts, compare the hosts before changing the VM.
A useful troubleshooting sequence is:
VM Placement → Virtual Network → Physical Uplink → Switch → Compare Differences
Sometimes the VM didn't change. The path underneath it did.

#Sangfor #HCI #Troubleshooting #Networking #Virtualization #TroubleshootingMindset

Like this topic? Like it or reward the author.

Creating a topic earns you 5 coins. A featured or excellent topic earns you more coins. What is Coin?

Enter your mobile phone number and company name for better service. Go

Newbie900829 Lv2  Posted 2026-Sep-17 11:18
  
VM Works on One Host But Network Issue on Another Host After Migration - My Troubleshooting Steps

Issue Summary
I faced an issue where a VM was working fine on one HCI node. Once I migrated it to another node in the same cluster, the network started dropping. The VM settings were exactly the same, so at first I thought the problem was inside the guest OS.
But when I moved the VM back to the original host, the network became normal again. That confirmed the issue is not with the VM, but with the host-side network path.

How I Troubleshoot This Type of Case

Step 1: Validate the VM movement
- Check if VM is reachable on Host-A
- Migrate to Host-B and test connectivity
- Migrate back to Host-A to confirm if issue follows the host
This simple test gives you a clear direction.

Step 2: Check Virtual Network on Both Hosts
Make sure both hosts have the same:
- vSwitch name and configuration
- VLAN ID settings
- vNIC to vSwitch mapping
- Port group / network segment
- MTU value
Sometimes a small mismatch here creates an issue that looks like a VM problem.

Step 3: Verify Physical Uplink of the Problematic Host
Compare Host-A vs Host-B for:
- Physical NIC link status
- Bond / Aggregate configuration
- Uplink cable status
- Switch port VLAN allowed list

Step 4: Check Physical Switch End
If host side looks okay, check the TOR switch:
- Access vs Trunk mode
- Native VLAN and allowed VLANs
- LACP status
- Interface errors, drops, flaps
- STP blocking

Step 5: Don't Change Multiple Things at Once
Always compare Working Host vs Non-Working Host first. Find the difference, then fix only that part.

My Learning
If same VM shows different behavior on different hosts, don't keep changing VM settings. Focus on what is different under the VM.
I follow this path: VM Location > Virtual Switch > Physical NIC > Switch Port > Comparison.
In many cases, VM is same, but the network path below it is different.
Newbie585065 Lv3  Posted 2026-Sep-17 11:45
  
Thanks for sharing!
Arsalan Israr Lv2  Posted 2026-Sep-17 12:20
  
Thanks for sharing
Humayun Ahmed Lv4  Posted 2026-Sep-17 12:34
  
Thanks to share!
Newbie006434 Lv2  Posted 2026-Sep-17 12:39
  
Thanks for sharing
Prosi Lv4  Posted 2026-Sep-17 13:00
  
Hi,
If host connectivity works but fails after migration, use host dependencies as a troubleshooting guide. Compare network paths before making changes to the guest operating system or applications.
ND Lv4  Posted 2026-Sep-18 14:15
  
I would like to add MAC/ARP behavior on migration. A real-world cause of this exact symptom. Stale ARP/MAC tables on the physical switch, or a host that hasn't sent a gratuitous ARP/RARP after live migration.

Otherwise, a solid piece of troubleshooting documentation!