I moved a VM and responded to create when asked about the UUID, now i cannot connect to any network devices via ping, RDP, etc...
What did i do wrong and how not to do it next time?
I'm gonna ask the obvious questions:
What VMWare product are you using?
Your last post said you are using ESX. Is this still so? If not
what is the host OS?
What kind of networking? (Bridged, NAT?)
What is the guest OS?
What is the output of IPCONFIG or IFCONFIG? (depending on your guest OS.)
I'm going to guess that since you said yes to create a new UUID, you now have a different, and wrong, IP address, gateway, DNS.
Hello,
I'm not going to ask the obvious questions. lol
You can just look them up in the vmware.log file and then change them back to what they were before in the vmx file.
However I don't think that's what the problem is.
That can also happen when you run out of ports on your vswitch. vswitch port capacity is not a criteria the migration wizards take into account.
When you say 'moved', - how did you move it. If the VC as asking for confirm of the UUID it sounds like a manual operation.
I was testing out some vcb backup scripts, and since i was unable to grab the *.vmdk files when doing this i was trying alot of things to troubleshoot the problem, which still exists.
1. Tried to backup the VM using the FullVM method
2. Backups fail to get *.vmdk's (2) one datastore and one RDM
3. Tried Unregistering the VM and re-registering
4. Selected Create at the prompt of UUID generation * based on vmware provided information *
5. Network connections now broken....
6. tried migrations to other ESX servers in the cluster, to no avail.
IPconfig lists what i would expect it to list, i can ping the local machine by its own ip and 127.0.0.1, just cannot ping past that including the GW address.
Thanks,
PNGSYSADMIN