#Vmware mac address table aging update#

If anyone has any suggestions how i could resolve the problem it would be appreciated. If we login to any ESXi host and check the MAC Table corresponding to a given segment. Also TEP-IP of that transport node is stored there. Step 1: When a VM is powered-on a transport node (ESXi), its MAC address is learned and get registered in the MAC table of that node. Their is of course a minor code difference so maybe this could be an issue, but I to get the outage to fix this is really tough so I can't do it unless i'm really confident it will fix it. Formation and updation of MAC table works pretty much same as TEP table. I have read that the arp table timeout value could be a factor but i have yet to find the command to see the set value.

I have looked at the Mac address aging time and its the default 5 minutes on both switches. I only mention VMware because I can replicate the problem from my desk. I have also had the issue with physical connected Windows servers when we physically move their network connection. Its basically any change to a mac address on Switch A causes the VM to go network offline. Now if i do this same test with the same host servers on Switch B the mac-address-table updates in milliseconds and the VM never has any network downtime.ДЄlso if i move a VM between hosts that are on different Switches i also get the problem.

To remedy the problem i manually clear the mac address for the VM on Switch A.

#Vmware mac address table aging update#

To replicate my problem i have a VMware setup with host servers connected to both switches, if i Vmotion a VM from one host on Switch A port X to another host on Switch A port Y the mac-address-table does not update and therefore the VM is un-contactable over the network. I have two 6500's connected together and the other one is running code, Version 12.2(18)SXF17a does not have the issue. I have a problem with the mac-address table not updating on a 6509, running IOS (s222_rp-IPSERVICESK9-M), Version 12.2(18)SXF16