What is a recommended design choice in a topology for multipathing iSCSI traffic?
What is a recommended design choice in a topology for multipathing iSCSI traffic?
For a recommended design choice in a topology for multipathing iSCSI traffic, initiators and targets should be in separate subnets. This configuration leverages multiple ports and target portals on different IP subnets to create multiple paths, thereby increasing redundancy and fault tolerance. By keeping the initiator and target ports in different subnets, specific ports can be utilized for path creation, optimizing traffic and ensuring high availability.
D is wrong according to https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus1000/sw/4_2_1_s_v_1_5_1/system_management/configuration/guide/n1000v_system/n1000v_system_13iscsi.html#wp1052813 shouldn't it be C??
you are right - An iSCSI target and initiator should be in the same subnet. C looks like the right option
Multipathing is about multiple IP paths, which rules out any bundling of physical interfaces. D is correct.
D is right, because there will be two subnets for each two initiator and two targets
Per VM documentation https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.storage.doc/GUID-4C19E34E-764C-4069-9D9F-D0F779F2A96C.html Looks like we have 2 answers for this question which is C&D. Port binding on Initiator will allow to create multiple paths to single target. We can create multiple paths by configuring multiple ports and target portals on different IP subnets. In this situation port binding is not in use. In this particular question I would reply C but we should have possibility to choose 2 answers.
https://www.cisco.com/c/en/us/td/docs/switches/datacenter/mds9000/sw/5_0/configuration/guides/ipsvc/nxos/ipsvc/ciscsi.html#53504 As you can see here there are many HA (High availability) solutions but the multi-path one uses different subnets between initiators and targets.
Answer D seems to be correct: You can create multiple paths by configuring multiple ports and target portals on different IP subnets. By keeping initiator and target ports in different subnets, you can force ESXi to create paths through specific ports. In this configuration, you do not use port binding because port binding requires that all initiator and target ports are on the same subnet. https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.storage.doc/GUID-4C19E34E-764C-4069-9D9F-D0F779F2A96C.html
Recommended design is D) C and D are possible options but D) is more recommended. Answer: D)
I found other sources of this same exam, that appears to be a 2 choises question: "What are two recommended design choices in a topology for multipathing iSCSI traffic? (Choose two.) A: two NICs bonded together on the initiator B: dual initiators to a single target with bonded interfaces C: initiators and targets in separate subnets D: dual initiators to dual targets E: single initiator to dual targets" In this case, would be B and C.
A is correct
I think this makes more sense: https://blog.spotodumps.com/index.php/2020/11/10/nov-2020-new-2020-ccie-ccnp-350-601-dccor-dumps-with-vce-and-pdf-from-spoto-update-questions/ The storage system is just what it is, what is usually redundant is the cabling (network) and the initiator of the communication itself, eg two cards in case one fails. So dual initiator instead of dual target.
I think it´s option A. Because multipath it's about redundancy on the destination or target for the initiator, so I think the best answer it´s A.
Any reference, please?