Weird VMWare issue
-
One of our company critical applications is housed on a new 2012 R2 VM. I was looking in Vsphere last week and noticed that the VM is listed as powered off. However, our employees have been using the server without any issues. I am also able to access it via RDP and VNC.
I noticed this on Thursday evening. Since both me and the other Network Admin were both off on Friday, I opted against rebooting. Today I am staring at the same problem. I can't do anything during the day, but it's definitely bothering me. Has anyone ever seen something like this before?
-
That is REALLY weird. Are you completely confident that the VM that you are looking at is truly the one that you are accessing?
-
@scottalanmiller said:
That is REALLY weird. Are you completely confident that the VM that you are looking at is truly the one that you are accessing?
100% We have 3 of these application servers. 2 of them are 2008 R2 and the one in question is 2012 R2. I can access the application from a web browser using either name or IP of the new server. I can also RDP or VNC using the name or IP.
-
Also we don't use clustering or load balancing on these servers. Desktop Icons are pushed out to certain people using the IP of the particular server we want them to use. None of the users who use this particular server have reported any issues.
-
@IRJ said:
Also we don't use clustering or load balancing on these servers. Desktop Icons are pushed out to certain people using the IP of the particular server we want them to use. None of the users who use this particular server have reported any issues.
Users let you know when they are having issues? Normally I hear about it two weeks later from their boss.
-
Are you accessing via vCenter server and if so do you get the same result if you log in directly to the host? I was just thinking it might be a problem with vCenter server (in which case you can reboot it to fix).
-
@Carnival-Boy said:
Are you accessing via vCenter server and if so do you get the same result if you log in directly to the host? I was just thinking it might be a problem with vCenter server (in which case you can reboot it to fix).
That would be my guess I've seen odd vCenter issues before. if nothing else reboot the host after hours.
-
@Carnival-Boy said:
Are you accessing via vCenter server and if so do you get the same result if you log in directly to the host? I was just thinking it might be a problem with vCenter server (in which case you can reboot it to fix).
Yes, I am. I plan to reboot tonight after hours. I just wanted to see if anyone has seen anything like this before.
-
@IRJ said:
@Carnival-Boy said:
Are you accessing via vCenter server and if so do you get the same result if you log in directly to the host? I was just thinking it might be a problem with vCenter server (in which case you can reboot it to fix).
Yes, I am. I plan to reboot tonight after hours. I just wanted to see if anyone has seen anything like this before.
Try accessing directly first.
-
@coliver said:
@IRJ said:
Also we don't use clustering or load balancing on these servers. Desktop Icons are pushed out to certain people using the IP of the particular server we want them to use. None of the users who use this particular server have reported any issues.
Users let you know when they are having issues? Normally I hear about it two weeks later from their boss.
In this case yes, but in most cases no. You can't go very far without this critical software since we are in banking and every transaction goes through this software.
-
@scottalanmiller said:
@IRJ said:
@Carnival-Boy said:
Are you accessing via vCenter server and if so do you get the same result if you log in directly to the host? I was just thinking it might be a problem with vCenter server (in which case you can reboot it to fix).
Yes, I am. I plan to reboot tonight after hours. I just wanted to see if anyone has seen anything like this before.
Try accessing directly first.
I am going to ask a stupid question.... How do I do that?
-
@IRJ said:
@scottalanmiller said:
@IRJ said:
@Carnival-Boy said:
Are you accessing via vCenter server and if so do you get the same result if you log in directly to the host? I was just thinking it might be a problem with vCenter server (in which case you can reboot it to fix).
Yes, I am. I plan to reboot tonight after hours. I just wanted to see if anyone has seen anything like this before.
Try accessing directly first.
I am going to ask a stupid question.... How do I do that?
Use the VMware Client and put in the IP address of the VMware host.
-
@scottalanmiller said:
@IRJ said:
@scottalanmiller said:
@IRJ said:
@Carnival-Boy said:
Are you accessing via vCenter server and if so do you get the same result if you log in directly to the host? I was just thinking it might be a problem with vCenter server (in which case you can reboot it to fix).
Yes, I am. I plan to reboot tonight after hours. I just wanted to see if anyone has seen anything like this before.
Try accessing directly first.
I am going to ask a stupid question.... How do I do that?
Use the VMware Client and put in the IP address of the VMware host.
I don't know the IP off hand. Anyway to find it through the Vsphere client?
-
I'm sure, just don't have one in front of me at the moment to check what the process is. You can always look for it on your network too.
-
@IRJ said:
@scottalanmiller said:
@IRJ said:
@scottalanmiller said:
@IRJ said:
@Carnival-Boy said:
Are you accessing via vCenter server and if so do you get the same result if you log in directly to the host? I was just thinking it might be a problem with vCenter server (in which case you can reboot it to fix).
Yes, I am. I plan to reboot tonight after hours. I just wanted to see if anyone has seen anything like this before.
Try accessing directly first.
I am going to ask a stupid question.... How do I do that?
Use the VMware Client and put in the IP address of the VMware host.
I don't know the IP off hand. Anyway to find it through the Vsphere client?
Can you do nslookup on the hostname?
-
@coliver said:
@IRJ said:
@scottalanmiller said:
@IRJ said:
@scottalanmiller said:
@IRJ said:
@Carnival-Boy said:
Are you accessing via vCenter server and if so do you get the same result if you log in directly to the host? I was just thinking it might be a problem with vCenter server (in which case you can reboot it to fix).
Yes, I am. I plan to reboot tonight after hours. I just wanted to see if anyone has seen anything like this before.
Try accessing directly first.
I am going to ask a stupid question.... How do I do that?
Use the VMware Client and put in the IP address of the VMware host.
I don't know the IP off hand. Anyway to find it through the Vsphere client?
Can you do nslookup on the hostname?
if I knew the hostname that would work.
-
LOL. You are just having layers of issues here.
-
@IRJ said:
@coliver said:
@IRJ said:
@scottalanmiller said:
@IRJ said:
@scottalanmiller said:
@IRJ said:
@Carnival-Boy said:
Are you accessing via vCenter server and if so do you get the same result if you log in directly to the host? I was just thinking it might be a problem with vCenter server (in which case you can reboot it to fix).
Yes, I am. I plan to reboot tonight after hours. I just wanted to see if anyone has seen anything like this before.
Try accessing directly first.
I am going to ask a stupid question.... How do I do that?
Use the VMware Client and put in the IP address of the VMware host.
I don't know the IP off hand. Anyway to find it through the Vsphere client?
Can you do nslookup on the hostname?
if I knew the hostname that would work.
It isn't reported in VCenter? I haven't touched VMWare in awhile but it should report which server the virtual machine resides on.
-
Do you not have documentation with all this information in it?
-
Is this what I am looking for?
