I have a customer with an IP 500V2 with VMPro running on a virtual Windows Server 2016(I believe). Everything was up and running with no issues until last week after their networking provider did a server update and reboot. After that, the service didn't automatically start up(or it failed to start) and I had to manually start it. Again, after that we had no issues for several days until the networking company again decided to do some updates and take the server off the domain and leave it as a local machine.(I'm not familiar with what this means or the ramifications) After that happened, I haven't been able to get VMPro back up. Their network team has given me a remote connection to the server and I can see that it is up and running and the service is running. I rebooted the IPO and still cant hit the VM with *17. I checked it out using SSA and under Alarms/Link I can see that the IPO has lost connection (red alarm) with the VMPro. So, I went down to IP networking and confirmed that I can ping the VMPro from the IPO.
If the machine is up and running, and I can ping back and forth, what would cause the loss of connection between the two?
Red Flag Submitted
Thank you for helping keep Tek-Tips Forums free from inappropriate posts. The Tek-Tips staff will check this out and take appropriate action.
Reply To This Thread
Posting in the Tek-Tips forums is a member-only feature.