new1234.jpg

Archive

Posts Tagged ‘NetApp’

VMware: Unable to remove an inaccessible NFS datastore

August 27th, 2014 3 comments

The backend storage volume corresponding to the datastore has been removed and the datastore appears as Inactive, when I want to remove (via vSphere Client connected to vCenter server) the NFS datastore I receive this error message:

Unmounting the datastore in vCenter Server fails with the error:
‘Call “HostDatastoreSystem.RemoveDatastore” form object “datastoreSystem-28” on vCenter Server “xxxx” failed. CannotRemove datastore ‘datastore_name’ because Storage I/O control is enabled on it. Correct it and re-try the operation

image

 

Solution:

To resolve this issue, log in directly to each ESXi host that has access to the inactive datastore and manually remove it.

– Connect to the vSphere ESXi host using SSH

– Run this command to list the mounted datastores:

esxcli storage nfs list

image

– Run this command to unmount the NFS datastore:

esxcli storage nfs remove –v datastorename

image

The inactive NFS datastore has been removed

Note: if your datastore display name have some spaces, please use quotes

 

More information: VMware

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: vSphere 5.5 U1 patch released for NFS APD problem

June 12th, 2014 No comments

After installation of VMware vSphere 5.5 Update 1 connectivity to NFS storage could be randomly lost with volumes reporting All Paths Down state. This issue was noticed around mid April and reported here.VMware documented the issue in KB article  2076392 Intermittent NFS APDs on VMware ESXi 5.5 U1

At June 10 VMware released a patch for this issue as described in KB 2077360. The patch can be downloaded using VMware Update Manager or using  VMware download page

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

Categories: VMware Tags: , , , , ,

VMware: Call "FileManager.MakeDirectory" for object "FileManager" on vCenter Server "server.domain.local" failed.

January 9th, 2013 2 comments

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.

image

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: 

image

I added the IP-addresses from the VMkernel ports with Root Access and I was able to create new files to the datastores.

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: Configure NetApp NFS datastore(s) Advanced parameters with PowerCLI

January 7th, 2013 3 comments

The settings that NetApp recommends (across all ESX hosts) are:

– NFS.HeartbeatFrequency(NFS.HeartbeatDelta in vSphere) = 12
– NFS.HeartbeatTimeout = 5 (default)
– NFS.HeartbeatMaxFailures = 10

When the number of NFS datastores are increased, we also recommend increasing the heap values:
– Net.TcpipHeapSize =>’30’  to Net.TcpipHeapMax  => ‘120’

To automate this configuration I’ve wrote a PowerCLI script:

#====================================================================#
#   SCRIPT:        Configure_Advanced_NFS_parameters.ps1             #
#   FUNCTION:      Configure NFS / NetApp best practice              #
#   OWNER:         Sander Daems                                      #
#   VENDOR:        NetApp / FAS2040                                  #
#   VSPHERE:       5.0 Update 1 build 623860                         #
#   CREATED:       07/01/2013                                        #
#   MODIFIED:      20/03/2013                                        #
#   VERSION:       v.1.1                                             #
#====================================================================#
#   CHANGELOG:                                                       #
#                                                                    #
#    v.1.0                                                           #
#    - Created script;                                               #
#                                                                    #
#====================================================================#
#   HOST - Specify host and connect                                  #
#====================================================================#
$ESXiHost = Read-Host "Enter ESXi Host name or IP"
Connect-VIServer $ESXiHost
#====================================================================# 
#   ADVANCED - Update TCP Settings                                   #
#====================================================================#
Set-VMHostAdvancedConfiguration -VMHost $ESXiHost -Name Net.TcpipHeapSize -Value 32
Set-VMHostAdvancedConfiguration -VMHost $ESXiHost -Name Net.TcpipHeapMax -Value 128
#====================================================================#
#   ADVANCED - Update NFS Settings                                   #
#====================================================================#
Set-VMHostAdvancedConfiguration -VMHost $ESXiHost -Name NFS.MaxVolumes -Value 256
Set-VMHostAdvancedConfiguration -VMHost $ESXiHost -Name NFS.HeartbeatMaxFailures -Value 10
Set-VMHostAdvancedConfiguration -VMHost $ESXiHost -Name NFS.HeartbeatFrequency -Value 12
Set-VMHostAdvancedConfiguration -VMHost $ESXiHost -Name NFS.HeartbeatTimeout -Value 5
#====================================================================#
#   SCRIPT FINISHED                                        #
#====================================================================#
Write-Host "Script finished..." -foregroundcolor yellow
#====================================================================#

More information / source: NetApp Whitepaper

More information / source: VMware KB , VMware KB, VMware KB

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn