This is caused due to no mechanism in place to validate the uniqueness of the vmkernel MAC address across the vCenter.
This is a known issue.
Currently, there is no solution.
To workaround this issue, change the duplicate MAC from the affected vmkernel(s).
Dropped packets, Impact on the storage, VMs ..etc.