#Vmware mac address conflict alarm full#

Had I done it by hand, I would certainly have driven myself crazy, but PowerCLI made it nice and easy. Somewhere along the lines during the creation of this VM (and others in this particular Cluster) the assigned MAC address conflicted with the reserved MAC ranges from VMware.

Dec 15 09:47:59.848 UTC: IOSXE-4-PLATFORM: Chassis 1 R0/0: cppcp: QFP:0.0 Thread:001 TS:00000000699009892497 SWPORT-4-MACCONFLICT: Dynamic mac from GigabitEthernet2 conflict with SVI, please check the network topology. So, I could only think of one way to figure out what was going on with this conflict: look at the MAC Address assigned to every NIC on every VM in the environment, and figure out what was causing the conflict. Almost in all my 9800-CL HA SSO & standalone deployment I have started seeing SWPORT-4-MACCONFLICT Issues. To my chagrin, I could only find that error message for a single VM in the environment, and that error message wouldn't tell me with which other VM it was conflicting.

#Vmware mac address conflict alarm full#

To determine if your NetBackup release supports the vSphere 6.0 or later release, see the Software. Product (s): NetBackup Problem In VMware vSphere 6.0 U1b and later, a NetBackup Full restore of a virtual machine may trigger a VM MAC address conflict alarm if the original VM was not deleted.

This alarm may occur in all NetBackup releases that support vSphere 6.0 and later. 'Well, that's certainly not good,' I thought, as I poked around at the error message. In VMware vSphere 6.0 U1b and later, a NetBackup Full restore of a virtual machine may trigger a VM MAC address conflict alarm if the original VM was not deleted. At one of my customers' sites today, I saw an error message that I've not seen before: VM MAC Conflict.