SG0-001 · Question #476
Which of the following is a valid reason to use dual single-port HBAs instead of a single dual-port HBA?
The correct answer is D. To survive a complete HBA failure. Using dual single-port HBAs instead of a single dual-port HBA provides redundancy at the HBA level, allowing the host to maintain connectivity to storage even if one HBA completely fails.
Question
Which of the following is a valid reason to use dual single-port HBAs instead of a single dual-port HBA?
Options
- ATo survive a cable fault with multipathing drivers installed
- BTo survive a storage array failure
- CTo run different versions of drivers on each HBA
- DTo survive a complete HBA failure
How the community answered
(67 responses)- A10% (7)
- B3% (2)
- C4% (3)
- D82% (55)
Why each option
Using dual single-port HBAs instead of a single dual-port HBA provides redundancy at the HBA level, allowing the host to maintain connectivity to storage even if one HBA completely fails.
Both dual single-port HBAs and a single dual-port HBA, when properly configured with multipathing, can survive a cable fault as long as redundant paths are established from the host to the storage.
HBA configuration cannot directly protect against a complete storage array failure; redundant storage arrays are required for that.
Running different versions of HBA drivers on the same host is generally not recommended as it can lead to instability and is not a valid reason for choosing dual single-port HBAs.
Using dual single-port HBAs provides complete redundancy for the Host Bus Adapter component itself. If one HBA completely fails (e.g., hardware malfunction, firmware issue), the host can still communicate with the storage array through the second, independent HBA, ensuring continued operation. This configuration offers a higher level of fault tolerance for the HBA compared to a single dual-port HBA.
Concept tested: HBA redundancy and fault tolerance
Source: https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-storage/GUID-02FB7410-6C91-4475-A050-48866170668F.html
Topics
Community Discussion
No community discussion yet for this question.