When a VM reports a MAC address conflict on a newly created virtual network interface, what is the best first step to resolve the issue?

When a VM reports a MAC address conflict on a newly created virtual network interface, what is the best first step to resolve the issue?

• A. Remove the virtual NIC and reconfigure another one
• B. Add an additional NIC with a loopback interface
• C. Ping the IP address to determine the location of the conflict
• D. Change the MAC address to ff:ff:ff:ff:ff:ff and obtain a new address

Answer: (A)

When a VM reports a MAC address conflict, the issue is that two devices on the same layer-2 network claim the same hardware address. The best first step is to remove the virtual NIC and reconfigure it so the hypervisor assigns a fresh, unique MAC from its address pool. This directly resolves the duplication at the source without manually tweaking addresses. Pinging an IP doesn’t fix a MAC collision; it only tests reachability and doesn’t address the underlying duplicate MAC. Adding a loopback interface won’t impact the conflict on the external network. Changing the MAC to ff:ff:ff:ff:ff:ff is invalid for a NIC and would create more problems. If the conflict recurs, confirm that each VM has a unique MAC and investigate cloning or misconfigurations that caused duplicates.

When a VM reports a MAC address conflict, the issue is that two devices on the same layer-2 network claim the same hardware address. The best first step is to remove the virtual NIC and reconfigure it so the hypervisor assigns a fresh, unique MAC from its address pool. This directly resolves the duplication at the source without manually tweaking addresses.

Pinging an IP doesn’t fix a MAC collision; it only tests reachability and doesn’t address the underlying duplicate MAC. Adding a loopback interface won’t impact the conflict on the external network. Changing the MAC to ff:ff:ff:ff:ff:ff is invalid for a NIC and would create more problems. If the conflict recurs, confirm that each VM has a unique MAC and investigate cloning or misconfigurations that caused duplicates.