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:
Today a customer told me that he couldn’t vMotion virtual machines between a few hosts, he received this warning message:
Migration to host <<unknown>> failed with error Already disconnected
An unknown error has occurred.
vMotion migration socket connected returned: Already disconnected
Solution:
After some troubleshooting I’ve checked and tested:
– Same VMkernel (+ case sensitive) name;
– Same VLAN;
– Same subnet;
– Same default gateway;
– They configured unique ip-addresses;
– Host A can ping host B, vice versa;
– Ping is stable < 1 ms;
– But…
…reading KB1030267 I checked the MTU size, somebody configured the MTU size with a 9000 value at the Management / vMotion VMkernel..
The 9000 value was configured (at the hosts with the vMotion problem) but not at the physical switches, after revert to default value (1500) I was able to vMotion again, problem solved
Result:
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:
I’m currently working on a project with Citrix Provisioning 6.1 build 1082 / XenApp 6.5 RP1 running on a VMware vSphere 4.1 build 721871 cluster, we discovered some boot “time” problems at the target VM’s, some of our Citrix XenApp 6.5 targets take more then 5 minutes to get past the bootstrap portion of the boot process.
Solution:
BUG0321533: Booting in a VMware environment can take more than 4 minutes to get past the bootstrap portion of the boot process. This has only been reported using ESX 4.1
Download hotfix: here
1. From Provisioning Services server machine, backup the following file: ARDBP32.bin
For Windows 2008 this file is located in (default) "C:\ProgramData\Citrix\Provisioning Services\Tftpboot".
2. Copy the following file included in the hotfix folder to the "Tftpboot" sub-directory indicated above:
ARDBP32.bin
3. Back up the following files from the Provisioning Services-installation-folder\TSBboot folder (Default is C:\Program Files\Citrix\Provisioning Services\TSBboot):
TSBBDM.BIN
4. Copy the following files from the hotfix folder to the Provisioning Services-installation-folder\TSBboot folder (Default is C:\Program Files\Citrix\Provisioning Services\TSBboot):
TSBBDM.BIN
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