Implementing iSCSI Multipathing on Cisco UCS with VMware
An engineer must implement an iSCSI storage connectivity in the existing Cisco UCS environment. The environment is based on Cisco UCS С-Series rack server, Cisco Nexus 1000V Series Switches, and VMware ESXi hosts. The implementation must meet these requirements: • Provide multipathing and high availability in the event of a critical path failure. • Be cost-effective and not require the purchase of new equipment. Which two components must be selected to meet these requirements? (Choose two.)
Community Votes
100% of anonymous learners picked answer AC. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
It tests the ability to select non-hardware solutions for storage redundancy, specifically combining the host bus adapter type with network path configuration.
This question addresses configuring software iSCSI adapters and uplink pinning to achieve multipathing and high availability in a cost-effective Cisco UCS and VMware ESXi environment.
Candidates often mistakenly choose hardware iSCSI NICs, failing to recognize that the requirement for cost-effectiveness without new equipment points to software-based configurations.
Community Discussion (3 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The scenario requires a cost-effective solution using existing infrastructure, which eliminates the need for purchasing new hardware iSCSI NICs (Option E). Instead, a software iSCSI adapter (Option A) allows the ESXi host to manage the connection via CPU resources. To ensure multipathing and high availability, uplink pinning (Option C) is the critical network configuration. It assigns specific VMkernel ports or traffic types to specific physical uplinks, ensuring that if one path fails, the other can take over, thus meeting the HA requirement.Why the Other Options Are Wrong
Storage binding (Option B) is not a standard term used in this context for configuring multipathing in ESXi; it likely refers to LUN masking or port binding concepts that do not directly solve the physical path redundancy issue described. Hardware iSCSI NICs (Option E) would provide offloading benefits but violate the 'cost-effective' and 'no new equipment' constraints. System VLANs (Option D) are used for management traffic isolation, not for storage data plane redundancy.Community Comment Notes
The community consensus strongly supports options A and C. As user Wasamela noted, "A & B as with the iSCSI adapters on the UCS server and uplink pinning on the ESXi hosts, multipathing and high availability can be provided." However, there was some confusion regarding option B versus C. User lurker8000 questioned why pinning helps, indicating a common gap in understanding how logical pinning maps to physical redundancy. The reference link provided by user b44c199 confirms the use of software iSCSI and uplink pinning for these goals.Official Reference
Exam Strategy
When you see 'cost-effective' and 'existing equipment,' immediately rule out hardware upgrades like HBAs or NICs. Focus on software configurations (like software iSCSI) and logical settings (like uplink pinning or vSwitch policies) that leverage current physical paths.
Frequently Asked Questions
Why is uplink pinning better than load balancing for iSCSI?
Uplink pinning ensures consistent path selection for specific traffic flows, simplifying troubleshooting and ensuring predictable failover behavior in iSCSI environments.
Can I use hardware iSCSI NICs if I already have them?
Yes, if you already own them, they are valid. However, the question specifies 'not require purchase of new equipment,' implying we must use what is available or software alternatives.