VM Gateway not Pinging After Switch Replacement

[DineshReddy1205]

Hi team,

As a result of a physical switch problem, the new switches have been changed. Several of the VM's gateways stopped working once the switch was replaced. The VM started to function when we disconnected and reconnected the VM Network. I'm not a native networker. Is there someone who can elucidate why? Why was it fixed after the virtual machine network disconnect and reconnect issue was fixed? Please share any reference documents or KB articles you may have.

Thanks.

[DineshReddy1205]

Hi ,

Total 5 VM's, all connected to the same port group and operating on the same host.It's going well with two virtual machines.There are just three virtual machine gateway is not reachable.The VM network was simply disconnected and then reconnected the VM's.VM gateway pining followed that.

[NateNateNAte]

So am I clear in restating that your question is why did things start working after you disconnected and reconnected the virtual network?

If that is what you're asking - it comes down to how the VMnet (similar to a switch) has an active running config that it defaults to until there is a forced reboot of sorts.  Your VMnet was mapped to a port that originally looked at config to an old switch (with a unique MAC) and then the new switch was swapped out (new unique MAC at the port level) and essentially removing and rejoining the VMnet is like a reboot - it establishes the new running config and off you go.  

As much as we want everything to be truly plug and play, sometimes it is not and you have to look way down in the OSI stack to start solving problems.  

Glad to hear your network is functioning again.