1
Diagnostic step 1
Identify collisions without downtime: run 'esxcli network vm list' and compare MACs across hosts to find duplicates; capture ARP tables on upstream switches to confirm which ports are advertising the duplicate MACs.
FULL AI ANALYSIS
Duplicate MAC addresses after cross-cluster VM migration causing ARP flaps and intermittent VM network loss
Generated Oct 3, 2026, 12:35:03 AM
Analysis summary
Duplicate MACs typically arise from manual/static MAC assignments, cloning without MAC regeneration, or importing VMs between vCenter instances where the MAC allocation pools overlap. When two VMs present the same MAC on the network, upstream switches and hypervisor virtual switches generate ARP flaps and connectivity issues. Fixes involve regenerating MACs in a controlled manner and enforcing policies so future migrations allocate unique addresses.
Possible causes
Manual/static MAC assignments retained during migration or template cloning, leading to collisions when VMs coexist on the same L2 network.
90%Imported/registered VMs from other vCenter instances with MACs that overlap the current MAC allocation pool.
80%Bug or misconfiguration in the vCenter migration workflow that prevented MAC reallocation on vMotion/import.
30%Third-party automation scripts that set VM MACs for licensing or legacy reasons and do not coordinate uniqueness.
25%Suggested fixes
2
Diagnostic step 2
For each collided VM, change the MAC in vCenter by editing the VM's network adapter and enabling 'Generate MAC address' (or set a new MAC within your allowed range). Do this one VM at a time for minimal disruption; reboot of the VM's network interface or a quick VM power-cycle may be required (reversible by reassigning the previous MAC if needed).
3
Diagnostic step 3
Audit cloning and import processes: ensure templates and automation do not preserve MAC addresses; enable 'Generate new MAC' during cloning or importing workflows.
4
Diagnostic step 4
Enforce MAC allocation policies at vCenter level and, if supported, use distributed switch settings to prevent manual MAC overrides. Maintain a documented MAC pool to avoid overlapping ranges between vCenter instances.
5
Diagnostic step 5
If large-scale remediation is needed, schedule a maintenance window and script MAC reassignment in batches while monitoring switch ARP tables. Escalation: If duplicate MACs persist after remediation or vCenter refuses to reassign MACs, escalate to virtualization platform admin or VMware Support — possible issues could include database inconsistencies in vCenter or bugs in cross-cluster import tooling.