Which two traffic types can be enabled on the VMkernel adapters of an ESXi 5.5 host using the
vSphere Web Client? (Choose two.)
A.
Fault Tolerance Traffic
B.
Virtual SAN Traffic
C.
iSCSI Traffic
D.
Virtual Machine Traffic
Explanation:
Which two traffic types can be enabled on the VMkernel adapters of an ESXi 5.5 host using the
vSphere Web Client? (Choose two.)
Which two traffic types can be enabled on the VMkernel adapters of an ESXi 5.5 host using the
vSphere Web Client? (Choose two.)
A.
Fault Tolerance Traffic
B.
Virtual SAN Traffic
C.
iSCSI Traffic
D.
Virtual Machine Traffic
Explanation:
A B are correct
The VMkernel networking layer provides connectivity to hosts and handles the standard infrastructure traffic of vSphere vMotion, IP storage, Fault Tolerance, and Virtual SAN.
http://pubs.vmware.com/vsphere-55/index.jsp?topic=%2Fcom.vmware.vsphere.networking.doc%2FGUID-D4191320-209E-4CB5-A709-C8741E713348.html
This is a poor question – IP storage can be enabled on a VMKernal port which puts the answer at A,B and C
but can IP storage be enabled within the WEB client?
With web client are available:
vMotion traffic
Fault Tolerance logging
Managgement traffic
Virtual SAN traffic
B – for sure, but how about A?
Is “Fault Tolerance logging” equal to “Fault Tolerance Traffic”
yes, “Fault Tolerance logging” equal to “Fault Tolerance Traffic”
which means:
A – correct
B – correct
C – wrong
D – wrong, because name of traffic is “Managment traffic” which also include VM traffic. Simply there is no such option in vSphere as VM traffic. http://ptgmedia.pearsoncmg.com/images/chap8_9780133511086/elementLinks/08fig11_alt.jpg
https://communities.vmware.com/servlet/JiveServlet/showImage/2-2290106-31467/replication.JPG
http://www.unixarena.com/wp-content/uploads/2014/02/How-to-Add-ISCSI-target-to-ESXi-5.5-Host7.jpg
Ask for me the correct answers are A & B. Look this:
http://pubs.vmware.com/vsphere-60/index.jsp?topic=%2Fcom.vmware.vsphere.networking.doc%2FGUID-AA3656B0-005A-40A0-A293-4309C5ACF682.html
Upgrade:
You might notice that two of the services mentioned aren’t shown as services that can be enabled: iSCSI traffic and NFS traffic. The reason is simple—there is no need to tell a VMkernel port that it can talk to iSCSI or NFS storage. All VMkernel ports can do this natively, and we typically just need to make sure that the IP address assigned to the appropriate VMkernel port is on the same subnet as the storage array