Rodos I found the problem, it was the ups software... The UPS has got a TCP/IP shutdown fetcher... But there is a local agent what you can install as swell... Agent was installed...
See more...
Rodos I found the problem, it was the ups software... The UPS has got a TCP/IP shutdown fetcher... But there is a local agent what you can install as swell... Agent was installed on the server and it running in the background... I did not know that so I checked the services and it was running... Like you said, Keep digging, and don't give up. That's what separates average from great IT people. Who know the root problem may be something that could really cause you grief down the track. No stone unturned. If it does not make sense it's not right. thax
Thanks Rodos, It just drops (crach) the VM , VC? Yes, and I have no idea where to go and start looking for the problem... Thanks for all your help so far...
That specific rack with 2 Servers a SAN, switches and routers is on the UPS. It is a APC and it has got network capabilities, but that I disabled because I thought is was that what turned the ...
See more...
That specific rack with 2 Servers a SAN, switches and routers is on the UPS. It is a APC and it has got network capabilities, but that I disabled because I thought is was that what turned the server of over TCP/IP... Once a gene I say it is not the UPS's fault... 4 of the 5 VM's is still running, why then not all dead?
The UPS is not the problem, it is a big UPS and it can run double the amount of blades we are currently running... Why is the rest of the VM's still running? I can understand if all V...
See more...
The UPS is not the problem, it is a big UPS and it can run double the amount of blades we are currently running... Why is the rest of the VM's still running? I can understand if all VM's would drop if the UPS wasn't sufficient... I can tell U that it is not the UPS...
I have ESX 3.0.1 on a server... About 5 vm's running on it... My problem comes in when the power fails and the UPS takes over for 30sec. before the generator kicks in... We once ha...
See more...
I have ESX 3.0.1 on a server... About 5 vm's running on it... My problem comes in when the power fails and the UPS takes over for 30sec. before the generator kicks in... We once had power spikes and the ups took over, even then the VM turned off... One of the five VM's on the ESX server turns off every time... I do not know why... any help would be grateful...
Hi edward, The name is not in there... vmware-cmd -l the server name does not appear, it is only listing the .vmx files of the servers that is currently on the ESX server. Trie...
See more...
Hi edward, The name is not in there... vmware-cmd -l the server name does not appear, it is only listing the .vmx files of the servers that is currently on the ESX server. Tried to run the vmwaere-cmd -s unregister , it gave me an error "the servername could not be found" so cannot unregister something that is not there. Tried to run the migrate again and it gave me the same error "Vim Fault Already Exists" any other suggestion?
Hi all, I have 2 ESX host servers, I cannot migrate a VM from one host to the other without the error message (Vim.Fault.AlreadyExists) . There was a vm with the same name on the host I want to ...
See more...
Hi all, I have 2 ESX host servers, I cannot migrate a VM from one host to the other without the error message (Vim.Fault.AlreadyExists) . There was a vm with the same name on the host I want to migrate to, but I removed it and created a new VM from a template with the same name. Now it gives me the error that “Vim.Fault.AlreadyExists” when I want to migrate the vm to the second ESX host where I deleted it from. Any ideas
I try to import a VM (Microsoft 2003 Server - Standard Edition) from an Workstation 5.5.1 format to ESX 2.5.1. I point the VM Import v2 connection to Virtual Center Client v2.0. I display the 2 E...
See more...
I try to import a VM (Microsoft 2003 Server - Standard Edition) from an Workstation 5.5.1 format to ESX 2.5.1. I point the VM Import v2 connection to Virtual Center Client v2.0. I display the 2 ESX Servers correctly. When the conversion start it fail in 30 seconds with errors that the copy fail. Their is 130 GB share disk available on the ESX Servers. After the failure it left the VM entry on the list of VM's for ESX, but it is corrupt. It also generate a big log about what happen. Is this a bug or what do I not understand or doing wrong. The VM disk image to convert is 12 GB.