CV0-003 · Question #41
An administrator has created a new virtual server according to specifications and verified that TCP/IP settings are correct. When the VM is powered on, however, an error message indicates that a…
The correct answer is A. Remove the virtual NIC and configure another one. MAC address conflicts on VMs typically occur after cloning or importing without regenerating hardware identifiers. Removing and re-adding the virtual NIC forces the hypervisor to assign a new unique MAC address.
Question
An administrator has created a new virtual server according to specifications and verified that TCP/IP settings are correct. When the VM is powered on, however, an error message indicates that a network card MAC address conflict exists. Which of the following would resolve this issue?
Options
- ARemove the virtual NIC and configure another one.
- BAdd an additional NIC with a loopback interface.
- CPing the IP address to determine the location of the conflict.
- DChange the MAC to ff:ff:ff:ff:ff:ff and obtain a new address.
How the community answered
(26 responses)- A81% (21)
- B4% (1)
- C12% (3)
- D4% (1)
Why each option
MAC address conflicts on VMs typically occur after cloning or importing without regenerating hardware identifiers. Removing and re-adding the virtual NIC forces the hypervisor to assign a new unique MAC address.
Removing the virtual NIC and adding a new one causes the hypervisor to generate a fresh, globally unique MAC address for the VM, eliminating the conflict at Layer 2. MAC conflicts in virtual environments most commonly arise when VMs are cloned or copied and the MAC address is not regenerated during the process. This is the standard resolution method supported by platforms such as VMware vSphere and Microsoft Hyper-V.
Adding a NIC with a loopback interface addresses internal host routing and does not resolve a duplicate MAC address conflict on the virtual switch.
Pinging an IP address tests Layer 3 connectivity and detects IP address conflicts, not Layer 2 MAC address conflicts.
ff:ff:ff:ff:ff:ff is the Layer 2 broadcast address reserved for broadcast frames and cannot be assigned as a valid unicast MAC to any network interface.
Concept tested: Resolving virtual NIC MAC address conflicts in VMs
Source: https://kb.vmware.com/s/article/219
Topics
Community Discussion
No community discussion yet for this question.