An administrator is attempting to enable Storage I/O Control on a datastore, but it is failing.
What is the likely reason for this failure?
A.
The host is connected to a datastore is running on ESX 4.0.
B.
The host is connected to a Fibre Channel storage array.
C.
The datastore has multiple extents.
D.
The datastore is managed by a single vCenter Server.
Explanation:
If you experience problems with SIOC or if the number of hosts connected to the datastore has changed since enabling SIOC:
Disable SIOC and save the changes by clicking OK.
Enable SIOC and save the changes.
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1022091
C.
VMware doesnt currently support multiple extents on a datastore for SIOC
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1022091
0
0
SIOC multiple extent are not not supported in version 4.1 & 5 but version 6.0 are supported
SIOC protocol is not supportd in version 4.0 and less
0
0
SIOC does not support multiple extents in any version. 5,5.5,6 or even 6.5
https://pubs.vmware.com/vsphere-60/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-60-resource-management-guide.pdf
Pg 47
https://pubs.vmware.com/vsphere-65/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-65-resource-management-guide.pdf
pg 50
0
0
I guess the question here is, who answered “A” and passed the exam?
0
0
What’s more, part of that new 85Q 2V0-602 dumps are available here:
https://drive.google.com/open?id=0B-ob6L_QjGLpZGoxeGwzYVZGZmM
Best Regards!
0
0
C
Storage I/O Control does not support datastores with multiple extents.
https://docs.vmware.com/en/VMware-vSphere/6.0/com.vmware.vsphere.resmgmt.doc/GUID-37CC0E44-7BC7-479C-81DC-FFFC21C1C4E3.html
1
0
Answer is A. https://docs.vmware.com/en/VMware-vSphere/6.0/com.vmware.vsphere.troubleshooting.doc/GUID-AF8E79FB-2E62-4F15-8CF9-4838815E746E.html. If there is a host running 4.0 connected to this datastore, the operation fails. To enable Storage I/O control in the datastore, verify that the hosts connected to the datastore are ESX/ESXi 4.1 or later.
2
0
Same language here:
https://kb.vmware.com/s/article/2021530
0
0