Issue: re-installed the ESXi 5.5 on cisco UCS blade and after that the ESXi management IP was not pinging and not able to connect it to vcenter.
finding:
up on checking the esxi configuration, found that somehow vmk0 mac address of the issue ESXi host is same as physical mac address of other production ESXi host mac address and because of this mac-address conflict, I was unable to ping the management IP. usually vmk0 mac-address would be automatically generated by ESXi (00:50:56:xx:xx:x)
Solution:
deleted, the vmk0 configuration as below and created again and now the ESXi generated the VMware mac-address and now I'm able to ping the ESXi host management IP.
refer to: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1031111
esxcfg-vmknic -d -p 'Management Network' this command could delete all the vmknic on management network port group
00:50:56:xx:xx:xx mac address automatically assigned to vmk0
finding:
up on checking the esxi configuration, found that somehow vmk0 mac address of the issue ESXi host is same as physical mac address of other production ESXi host mac address and because of this mac-address conflict, I was unable to ping the management IP. usually vmk0 mac-address would be automatically generated by ESXi (00:50:56:xx:xx:x)
Solution:
deleted, the vmk0 configuration as below and created again and now the ESXi generated the VMware mac-address and now I'm able to ping the ESXi host management IP.
refer to: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1031111
esxcfg-vmknic -d -p 'Management Network' this command could delete all the vmknic on management network port group
00:50:56:xx:xx:xx mac address automatically assigned to vmk0
No comments:
Post a Comment