Accepted Solutions
SIOC is a feature of vSphere 4.1 and requires VMFS volumes. My guess, is one of the host that is connected is not running 4.1?
=========================================================================
William Lam
VMware vExpert 2009,2010
VMware scripts and resources at:
Getting Started with the vMA (tips/tricks)
Getting Started with the vSphere SDK for Perl
VMware Code Central - Scripts/Sample code for Developers and Administrators
If you find this information useful, please award points for "correct" or "helpful".
The only other thing is if the hardware itself may not support the feature ... afaik, this is all done in software BUT it may utilize certain hardware features of the CPU or whatnot. Are all your hosts running similar hardware?
I have a script that generates a health check report, you might be able to leverage it and compare the compability features. Here is a sample output: https://dl.dropbox.com/u/8746485/sample_vmware_health_report.html#ESX/ESXi%20Capabilitie%28s%29-1
I don't know how large your environment is, but you can investigate the logs to see which host is throwing the error or if vCenter has more information in it's vpxa logs. I suspect, you should see an error on one of the host when trying to enable SIOC on the datastore that is not supported by one of the hosts.
=========================================================================
William Lam
VMware vExpert 2009,2010
VMware scripts and resources at:
Getting Started with the vMA (tips/tricks)
Getting Started with the vSphere SDK for Perl
VMware Code Central - Scripts/Sample code for Developers and Administrators
If you find this information useful, please award points for "correct" or "helpful".
VMware HCL is what you want to double check, as I mentioned, SIOC is all done in software so it's kind of odd that you're seeing this with all 4.1 hosts. That is the only thing that I would see that would cause it to fail ... Do you know what version of VMFS are you running on this particular VMFS datastore? I might require latest 3.46 versus 3.33
=========================================================================
William Lam
VMware vExpert 2009,2010
VMware scripts and resources at:
Getting Started with the vMA (tips/tricks)
Getting Started with the vSphere SDK for Perl
VMware Code Central - Scripts/Sample code for Developers and Administrators
If you find this information useful, please award points for "correct" or "helpful".
I've not done an upgrade from 3.33 to 3.46, I believe it will be destructive but you'll want to confirm with VMware support before doing so. You may need to evacuate your VMs to another datastore before you upgrade VMFS volume.
Though before you do so, I just realized if login to your vCenter server and click on one of the host over to the Storage tab, you should have a tab that says "Storage I/O Control" and it should say either enabled, disabled or not supported. That might give you a little more information on which host does not support the feature. I'm not 100% sure on VMFS version affecting it, but it would make sense since that is a new feature of 4.1 and with 4.1, there was a minor VMFS version change.
=========================================================================
William Lam
VMware vExpert 2009,2010
VMware scripts and resources at:
Getting Started with the vMA (tips/tricks)
Getting Started with the vSphere SDK for Perl
VMware Code Central - Scripts/Sample code for Developers and Administrators
If you find this information useful, please award points for "correct" or "helpful".
That is what I thought - it requires Enterprise Plus
Maish
VMware Communities User Moderator
- @maishsk
