ramakrishnak's Accepted Solutions

also please look at the older post which has the info you are looking for Re: VSAN vs VSA Thanks
Oh. k. so this is vSphere Flash Read Cache (vFRC) feature and nothing to do with VSAN check on the host logs which is throwing this error. esp: /var/log/hostd.log and corresponding timefra... See more...
Oh. k. so this is vSphere Flash Read Cache (vFRC) feature and nothing to do with VSAN check on the host logs which is throwing this error. esp: /var/log/hostd.log and corresponding timeframe /var/log/vmkernel log. this will show what is going on here you may want to check the following a. check whether the SSD LUNS are unused/ no other partition exists # partedUtil getptbl /vmfs/devices/disks/<ssddisk> b. also check that the SSD lun on this host are local and eligible for vflash # esxcli storage vflash device list Thanks,
From the beginning of the vsan sofware, we introduced diskgroup concept where a diskgroup consists of flash tier and capacity tier. flash tier was SSD and capacity tier HDD in hybrid cases ... See more...
From the beginning of the vsan sofware, we introduced diskgroup concept where a diskgroup consists of flash tier and capacity tier. flash tier was SSD and capacity tier HDD in hybrid cases To keep this consistent and simpler for all flash, we introduced the notion of promoting additional SSDs to capacity tier. but still the original requirement of having 1 SSD assigned for flash tier is a must so what you have to do in your case is keep 1 SSD for flash  tier without promoting them to capacity tier. you can remove the satp rule use esxcli vsan storage tag to remove the capacityFlash for one of the SSD disk (as mentioned in cormac's link) that will fix your setup
One new thing you might find interesting is the vSAN health Services. http://www.vmware.com/files/pdf/products/vsan/VMware_Virtual_SAN_Whats_New.pdf apart from that no changes in monitoring a... See more...
One new thing you might find interesting is the vSAN health Services. http://www.vmware.com/files/pdf/products/vsan/VMware_Virtual_SAN_Whats_New.pdf apart from that no changes in monitoring aspect. and observer still plays a main role when it comes to monitoring details Yes, You can expect more details on vRealize integration in near future Thanks,
if you look at our VMware Compatibility Guide: vsan we have posted this info expect this to be available by March 18, 2015 <snip for the website> The Virtual SAN Compatibility Guid... See more...
if you look at our VMware Compatibility Guide: vsan we have posted this info expect this to be available by March 18, 2015 <snip for the website> The Virtual SAN Compatibility Guide is currently being enhanced to support new hardware components (I/O controllers, HDDs and SSDs) and Ready Nodes. Hardware components and Ready Nodes supported on Virtual SAN 6.0 will be listed by March 18, 2015. In the meantime, if you have any hardware compatibility queries relating to Virtual SAN 6.0, please contact vsan-hcl@vmware.com
Virtual SAN enablement is tied to VCenter Clusters The Term vSphere Server in this context means "vCenter" Thanks,
> The policy requires 2 replicas with 1 disks each with 0 bytes free each. Only found 0 such disks This means that all the three nodes in the cluster are not participating in Storage. check wh... See more...
> The policy requires 2 replicas with 1 disks each with 0 bytes free each. Only found 0 such disks This means that all the three nodes in the cluster are not participating in Storage. check whether all 3 nodes have atleast 1 diskgroup and contributing in storage default vsan policy is 1 failure to tolerate which creates two replicas. so you can either make sure all 3 nodes have atleast 1 diskgroup or create a vm storage policy overriding the defaults Thanks,