If you compare the MAC addresses on the source VM and the VM that the alarm references you will see that VMware has already changed the MAC on the second VM. The MAC Conflict alert is triggered but doesn't clear automatically when the MAC is changes on the replica/backup VM.
We've disabled the MAC Conflict alert on our Prod environment.
-
- Novice
- Posts: 8
- Liked: 2 times
- Joined: Mar 17, 2016 11:56 pm
- Full Name: Matt Brown
- Contact:
-
- Novice
- Posts: 3
- Liked: never
- Joined: Sep 09, 2015 1:40 pm
- Full Name: Ken Sliger
- Contact:
Re: ESXi 6.0 U1b - VM MAC Conflict alarm on Veeam Replicas
Editing the alarm works great, thanks!
-
- Lurker
- Posts: 1
- Liked: 3 times
- Joined: Mar 23, 2019 5:55 am
- Full Name: Joe
- Contact:
Re: ESXi 6.0 U1b - VM MAC Conflict alarm on Veeam Replicas
Go to the VM MAC Conflict alarm definition. It’s in the vCenter inventory object under Manage > Alarm Definitions. Click the alarm and on the right, click Edit.
Under the bottom box that reads, “The following conditions must be satisfied for the trigger to fire”, add a condition that says the VM name does not end with “_replica”. Once applied, the alarm disappears for your replica VMs.
Under the bottom box that reads, “The following conditions must be satisfied for the trigger to fire”, add a condition that says the VM name does not end with “_replica”. Once applied, the alarm disappears for your replica VMs.
Who is online
Users browsing this forum: Google [Bot] and 47 guests