Cant power on a cloned VM - Its because of a new ESXi host i added in

Hi

I must have missed something when adding to the cluster. - I made a clone of a vm - and I cant power it on - "Unless the new esxi host I added in 2 days ago is powered off. - If its on - I get an error fasul.systemerror.summary - I can see it trying to power on to the new esxi host. - I dont necessarily want it to do this anyway, however it is by default. If I power this new esx host down the clone vm comes on no problem.

I get errors like fault abothe or cannotAccessFileSummary. Ive presented all exact same storage and swap locations to the new host - done DNS - all networking the same - So im wondering what i have missed - can anyone assist please?
LVL 1
philb19Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Peter HutchisonSenior Network Systems SpecialistCommented:
Sounds like a problem with the location of the VM's disk files. Are the disks on a a shared cluster disk? Make sure that the VM's disks are not in use elsewhere, eg not using the same disks and the original VM you cloned form?
0
philb19Author Commented:
Thanks The vmdk - im not sure what your asking? The original vmdk IS in the same datastore as the new clone - (with new vmdk name) - As soon as it tries to power on it tries to place on new host and fails/
0
Peter HutchisonSenior Network Systems SpecialistCommented:
Do you have any error messages or screen shots to help?
What version of vmware are you using?
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

philb19Author Commented:
5.1 version - ive definitly missed something - i cant even create a new vm on the host with wizard - it just immediatly puts it on another host.

i added the host to cluster with wizard - was i meant to do something in vcenter? no just vcentre client? errors im getting are cannotAccessFile.summary and cannot relocate to host or datastore
0
philb19Author Commented:
im getting fault.systemsummary - when i try and vmotion to new esx host ???
0
Peter HutchisonSenior Network Systems SpecialistCommented:
Assuming the new host is listed on the same Cluster then the next thing to check is that the new host can see the same Datastores as the other hosts. on vCenter, select the host, click the configuration tab and click on Storage under 'Hardware' to view the datastores. If none are listed, try 'Rescan for datastores' option on right-click menu to scan for them.
0
philb19Author Commented:
thanks yes it can see all the datastores thats the odd thing. ?? - is there something I missed in adding the host ? - Ive added it using wizard in client. - i did read you need to add the host in  vcenter server? but im not sure what interface to use and what im meant to do. - one other thing is the host are in evaluatioen an mode - but ive had it like that before never been a problem ???
0
Peter HutchisonSenior Network Systems SpecialistCommented:
Use the vSphere Client and go to Home, Inventory, Hosts and clusters and it should list the VM Hosts and VM machines.
The client can be download via the host's web page e.g. http://esxname/
0
philb19Author Commented:
Solved :) :)

It was on the Netapp filer - I gave the host just read-write access to the NFS export - it was able to mount the datastore to the host with this. - i just double checked on the netapp and discovered that the other hosts had 2 x entries for permissions - 1 read write and 1 root access - i was missing the root access permission for the host - added this on the netapp filer and now can vmotion VMs to the new ESXi host.

So for any netapp experts - why is root access required? thanks
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Peter HutchisonSenior Network Systems SpecialistCommented:
Hurray!  Glad to see you solved it.
0
philb19Author Commented:
thanks what are you referring to download here??? - is this something other than the vcenter client -  or a vcenter server manager that i dont know about??

Use the vSphere Client and go to Home, Inventory, Hosts and clusters and it should list the VM Hosts and VM machines.
The client can be download via the host's web page e.g. http://esxname/
0
Paul SolovyovskySenior IT AdvisorCommented:
On the netapp you need read/write and root access to each datastore (asumming NFS here).

If you create a new datastore it's best to do it rhough the Netapp VSC on the cluster, this way it creates the Netapp volume, adds ACLs, permissions, etc.. and mounts it to each host in the cluster.  If you have flexclone you can even test your backups within minutes in a bubble.  Don't forget to install the NFS Plug-in for VAAI, it will make your clones/storage vmotion go much faster
0
philb19Author Commented:
cmsxpjh - i see you are likely talking about the vcenter server - I already have this on a VM and I interface with the client - thanks for tip paulsolov - Yes I also have netapp plugin - i havent used before - will do in the future -these were not new datastores though - i just didnt apply root permsion for new host - why does it need root access - why is read write not sufficiient? thanks
0
Paul SolovyovskySenior IT AdvisorCommented:
Not sure about why but it may have something to do with root_squash.  It is a requirement per Vmware and Netapp including best practice.  To validate this you can create a datastore through the VSC and it will do create the read/write and root permissions for the vmkernel ports.  (Make sure your VSC is configured properly with resources..otherwise it may create the datastore on the wrong interface)

This is from VMware

Ensure the NFS server supports NFSv3 over TCP. ESX/ESXi does not use UDP for NFS.
The NFS server must be accessible in read-write mode by all ESX/ESXi hosts.
The NFS server must allow read-write access for the root system account (rw).
The NFS export must be set for either no_root_squash or chmod 1777 .
Ensure the ESX/ESXi VMkernel IP is allowed to mount the NFS share by inspecting the export list.
Ensure the mount is exported by running exportfs -a to re-export all NFS shares.
Check to ensure that the ESX/ESXi host is correctly configured to use an NFS share:
0
philb19Author Commented:
resolved permissions
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
VMware

From novice to tech pro — start learning today.