question

MichaelGilmore-7042 avatar image
0 Votes"
MichaelGilmore-7042 asked XiaoweiHe-MSFT edited

VMMS.exe not listening on port 6600 after restarting server

After setting up Hyper-V for live migrations, the VMMS.exe is listening on port 6600 and works correctly. After restarting the server, the VMMS.exe service is up and running, however it is not listening on port 6600. But if I simply restart the VMMS.exe service, it then is now listening on 6600. I have also set the service to delayed start and that appears to work. However I have to wait until the service starts before I can manage any VM's that run on the local server. Delayed start seems like a Band-Aid fix. Is there any fix for this issue? Is something not in place or running so the VMMs.exe service can bind to port 6600? Firewall is all off while I troubleshoot this issue.

Michael

windows-server-hyper-vmsc-virtual-machine-manager
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

XiaoweiHe-MSFT avatar image
0 Votes"
XiaoweiHe-MSFT answered XiaoweiHe-MSFT edited

Hi,

I meet this issue before, the workaround is like you said, to set the VMMS service to be delayed start.

This issue may due to that, when the server restart, the VMMS service tries to register port 6600 on the Network card before the network card finished initialization.

It seems there's no fix yet just a workaround.

Thanks for your time!
Best Regards,
Anne


If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

· 4
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

So the strange thing is when I first setup this server it worked just fine. Then I ran into Windows update issues that they were failing and I could not figure out why. Since it did not take long to redeploy the OS, I did that and now it fails to bind to port 6600 every time. So at first, this issue was not present.

0 Votes 0 ·
XiaoweiHe-MSFT avatar image XiaoweiHe-MSFT MichaelGilmore-7042 ·

Hi,

So, seems the issue occurred after we re-install the OS? How do we reinstall the OS, clean install, or in-place upgrade? After re-installation, do we re-install the network card driver? If yes, is the network driver version the same as before?

Best Regards,
Anne

0 Votes 0 ·

That is what I initially thought because I had to re-deploy the OS after constant failed Windows updates. I started building a second server and it has the same issue without re-installing the OS. Both servers are from Dell. I have had to delay start the service on both servers to allow it to work after a reboot. The only thing I can think of is the network card(s) are not initialized yet when the vmms.exe service is started. Using 2 Broadcomm NIC's, 1 has 2 10G ports and the other has 2 1GB ports. Each pair are teamed in the OS. This is the NIC description from the packing list, "Broadcom 57416 Dual Port 10GbE BASE-T & 5720 Dual Port 1GbE BASE-T". The latest driver is installed from Dell. These are brand new R740 servers from Dell.

0 Votes 0 ·
Show more comments