Today I created some new NFS volumes at a NetApp FAS2040, after I configured the datastores in vSphere I couldn’t write files and folders, warning message:
Call "FileManager.MakeDirectory" for object "FileManager" on vCenter Server "server.domain.local" failed.
Solution:
I forgot (stupid me) to configure the correct access rights, in the NetApp OnCommand System Manager:
Storage > Exports > select Export Path > add the correct rights + IP addresses for the configured VMware VMkernels:
I added the IP-addresses from the VMkernel ports with Root Access and I was able to create new files to the datastores.
Sander Daems is founder and author of this blog and working as a Lead (Sr.) Consultant by UNICA ICT Solutions. Sander has over 15 years experience in IT, primary focus: virtualization and modern worksplace.
More Posts - Website
Follow Me:
After upgrading the datacenter from vSphere 4.0 to 4.1 I was unable to connect with my service account “esxuser” by putty or console or Veeam to make some backups, warning message: Access denied
I changed my password a few times.. maybe it was changed, I restarted the SSH service.. no luck.. I created a new account with shell access but still the same deny!
Solution:
Connect direct your ESX console by VI client, go to Permissions tab and add your service account with Administrator rights:
Yeah, I was able to connect again with my service account.. 🙂
Sander Daems is founder and author of this blog and working as a Lead (Sr.) Consultant by UNICA ICT Solutions. Sander has over 15 years experience in IT, primary focus: virtualization and modern worksplace.
More Posts - Website
Follow Me:
Since vSphere 4.1 there’s a possibility to connect your ESX server into Microsoft Active Directory, how do you configure this:
– Connect directly to your ESX host
– Make sure your DNS servers are correct configured on the host + add the host by FQDN in your DNS server in your domain;
Read more…
Sander Daems is founder and author of this blog and working as a Lead (Sr.) Consultant by UNICA ICT Solutions. Sander has over 15 years experience in IT, primary focus: virtualization and modern worksplace.
More Posts - Website
Follow Me:
Today on the Dutch VMug forum somebody got some trouble to connect a ESX host after changing the “root” permissions from Administrator to Read-only. Nice problem to find a solution, I created the same situation in my test environment.
Situation:
User: Root – Role: Read-Only
You can’t connect the host anymore with your VI Client..
Solution:
… but you can still login at the console or putty session.. so what to do:
Edit the authorization.xml file: nano /etc/vmware/hostd/authorization.xml
Read more…
Sander Daems is founder and author of this blog and working as a Lead (Sr.) Consultant by UNICA ICT Solutions. Sander has over 15 years experience in IT, primary focus: virtualization and modern worksplace.
More Posts - Website
Follow Me:
Recent Comments