Wednesday, February 27, 2019

Vmware vNic failed autonegotiation?

Hello,

The title doesn't really do it justice but its the best I could come up with. We had an interesting problem yesterday at work. There is a Vmware (vSphere 5.5) cluster, in which there are 4 vNics (3 in use). One is connected to a database-server (windows server) which showed up with "unidentified network", so I was unable to reach it via traditional methods, ping etc. We saw in vSphere that it was unable to reach the domain controller, even when it had a static IP assigned.

We traced the cabling and found at the last switch before the VM had adjusted to 100Mbit instead of 1Gbit as it should. It is an older Zyxel switch with a rudimentary web-GUI for management. No explanation as to why it had gone down to 100mbit so we tried to force it to 1Gbit to no avail. Unplugging and plugging in ~8 times did the job, then rebooting the VM. (My contemplation now is a cable is not proper, but it has happened before too apparently).

The lab engineer could not figure out why it just randomly downgrade to 100Mbit, but as it works now, nobody questions this of course. I however, am wondering why the VM was unable to speak to the domain controller on the same subnet. Any ideas?



No comments:

Post a Comment