So since this is a known reason for the mac address conflict and this isn’t a situation of someone trying to spoof a mac address We clear the alarm on the restored VM before we complete the restore. When Commvault restores a VM we do the same thing (assuming no network reconfiguration as part of the restore) we put the vm back with the exact same network settings, but we know that there can be a mac address conflict, and we also know that you requested a VM to be restored. Now vCenter mac address (seen from management console) differs from address that is automatically assigned (seen from esxi, vcenter) and it causes errors / connectivity issues when using network security policies.
#Vmware mac address changes vcenter update#
In my experience, this isn’t “eventually” but “immediately” and the changing of the mac address and the generation of the alarm happen simultaneously. vCenter mac address change after update Hello I updated vCenter from 6.7 to 7.0 and vCenter kept old mac address. The article also states “If there is a mac address conflict, VMware eventually changes the mac address of the new VM”. While VMware changes the mac address an alarm is generated that says a mac address conflict was detected.
Post by eddieho98 » Sun 11:30 am I did follow your advice to remove ssh host keys and rebooted but it didnt help. I suppose changing a network card will face the same issue. Netbackup doesn’t change the mac address, and because they don’t change the mac address, VMware detects the conflict and changes the mac address. It seems that there has been some changes to handle mac address change. The article that you linked isn’t saying the exact same thing here.
0 kommentar(er)
