Goal is to enable NFS file share so I can map to Tanzu / OCP clusters for POCs
Four node cluster: 10Gb dedicated "vSAN" back end.
VLAN 101 172.16.101.0/24
Port group "Storage_101" VLAN tag 101
I enabled dvswitch settings per: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vsan.doc/GUID-CA9CF043-9434-454E-86...
But still not able to activate file services. I had this option (if my voices are not lying to me)... a few weeks ago but was not ready to activate... but now it is not an option:
<<Update>>
I read powercli tools per some google hits to query vSAN. I recall trying to run this setup but it ran into vSAN snag... maybe this will shine light on issue
PS C:\WINDOWS\system32> Get-Cluster
Name HAEnabled HAFailover DrsEnabled DrsAutomationLevel
Level
---- --------- ---------- ---------- ------------------
cluster False 1 True FullyAutomated
PS C:\WINDOWS\system32> Get-VsanFileServiceDomain -Cluster cluster
Get-VsanFileServiceDomain : 11/24/2021 2:28:11 PM Get-VsanFileServiceDomain VSAN runtime fault on server
'/VIServer=vsphere.local\administrator@vcenter01.penguinpages.local:443/': Unknown server error: ''. See the event log
for details..
At line:1 char:1
+ Get-VsanFileServiceDomain -Cluster cluster
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (:) [Get-VsanFileServiceDomain], ViError
+ FullyQualifiedErrorId : Storage_Impl_VsanServiceImpl_ErrorFetchingFileServiceDomain,VMware.VimAutomation.Storage
.Commands.Cmdlets.Vsan.GetVsanFileServiceDomain
PS C:\WINDOWS\system32> Get-VsanFileServiceOvfInfo
Version UpdateTime
------- ----------
7.0.2.1000-18226214 11/13/2021 12:12:...
PS C:\WINDOWS\system32> New-VsanFileServiceDomain -Cluster cluster -DnsServerAddress 172.16.100.22 -DnsSuffix penguinpages.local -Name fs_vsanDatastore -VsanFileServerIpConfig 172.16.101.121,172.16.101.122,172.16.101.123,172.16.101.124
New-VsanFileServiceDomain : Cannot bind parameter 'VsanFileServerIpConfig'. Cannot convert the "172.16.101.121" value
of type "System.String" to type "VMware.VimAutomation.Storage.Types.V1.Vsan.FileService.VsanFileServerIPConfig".
At line:1 char:153
+ ... verIpConfig 172.16.101.121,172.16.101.122,172.16.101.123,172.16.101.1 ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (:) [New-VsanFileServiceDomain], ParameterBindingException
+ FullyQualifiedErrorId : CannotConvertArgumentNoMessage,VMware.VimAutomation.Storage.Commands.Cmdlets.Vsan.NewVsa
nFileServiceDomain
####
I am not finding great site to define flow to create this / debug via cli tool.. So kind of poking in the dark..
Any idea on this. The field greyed out.. what does it mean? I poked around with Power CLI tool and vSAN File Category | VMware PowerCLI Reference to try to get some suggestion or direction but not finding any means to root cause. I think below is hampered by some basic service enbled within vCenter.
##Draft notes on setup
Step 1: Setup Networking
For DVS switch create port group with MacLearning and Forged Transmits enabled Ex: storage VLAN 101
Step 2: Create share
# Create one IP for each physical host
New-VsanFileServerIpConfig -Fqdn thorfs.penguinpages.local -Gateway 172.16.101.1 -IpAddress 172.16.101.101 -SubnetMask 255.255.255.0
New-VsanFileServerIpConfig -Fqdn odinfs.penguinpages.local -Gateway 172.16.101.1 -IpAddress 172.16.101.102 -SubnetMask 255.255.255.0
New-VsanFileServerIpConfig -Fqdn medusafs.penguinpages.local -Gateway 172.16.101.1 -IpAddress 172.16.101.103 -SubnetMask 255.255.255.0
New-VsanFileServerIpConfig -Fqdn vardafs.penguinpages.local -Gateway 172.16.101.1 -IpAddress 172.16.101.104 -SubnetMask 255.255.255.0
# Define VSAN File Service Domain ???
# Create new File Share from domain <<< Error... >>>>
New-VsanFileShare -FileServiceDomain penguinpages.local -Name vsannfs -FileShareNetworkPermission ReadWrite
New-VsanFileShare : Cannot process argument transformation on parameter 'FileServiceDomain'. Unexpected error occured.
The string wrapper for type VMware.VimAutomation.Storage.Types.V1.Vsan.FileService.VsanFileServiceDomain is not defined
At line:1 char:38
+ New-VsanFileShare -FileServiceDomain penguinpages.local -Name vsannfs ...
+ ~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidData: (:) [New-VsanFileShare], ParameterBindingArgumentTransformationException
+ FullyQualifiedErrorId : ParameterArgumentTransformationError,VMware.VimAutomation.Storage.Commands.Cmdlets.Vsan.
NewVsanFileShare
Suggestions?
<Update>
Back at this task after holidays.
In summary, sorry.. no real root cause, but during the whole last few weeks, I powered down the entire cluster and back up. Now button showing for enable file share.
But... I removed any servers NOT perfectly happy and healthy (well.. as much as vSAN is every happy or heathly...) and not active in hosting data out of vSAN, just to keep it simple
I made sure each esxi host had an IP on the storage VLAN.
What is not clear is that IPs it requests, binds to what seems to be an additional / dedicated IP, My guess is to some OVA appliance it deploys and controls. But I put this on the same VLAN as my vSAN as that is my "storage network"
Questions:
1) Do IPs need to be on storage VLAN?
2) The error seems to be related to DV Switch, is there issues with DVSwitches with this feature?
3) Any suggestion of where the logs are. Something with less cryptic details out of vcenter?
4) is there a CLI deployment guide or set of steps where I can go that route and see better details of what is setup and where error occures?