HAT-420 · Question #11
A customer has a Hitachi Unified Storage (HUS) system model 110 configured with iSCSI I/O interface boards. They now want to connect it to a FC-SAN and have purchased the FC-Option upgrade to do so…
Correct Answers: A and C Installing and enabling the FC-Option (C) is required because it is the purchased upgrade that unlocks FC protocol support on the HUS 110 - without activating it, the FC ports remain non-functional regardless of physical configuration. Setting the FC…
Question
A customer has a Hitachi Unified Storage (HUS) system model 110 configured with iSCSI I/O interface boards. They now want to connect it to a FC-SAN and have purchased the FC-Option upgrade to do so. Which two tasks must be performed on the HUS system? (Choose two.)
Options
- ASet the HUS FC port topology as Fabric.
- BSet the HUS FC port topology as Point-to-Point.
- CInstall and enable the FC-Option on the HUS.
- DInstall and enable the FC Expansion Board.
Explanation
Correct Answers: A and C
Installing and enabling the FC-Option (C) is required because it is the purchased upgrade that unlocks FC protocol support on the HUS 110 - without activating it, the FC ports remain non-functional regardless of physical configuration. Setting the FC port topology to Fabric (A) is necessary because connecting to a FC-SAN means connecting through FC switches in a switched fabric environment, which requires Fabric topology mode.
Why the distractors are wrong:
- B (Point-to-Point) is incorrect because Point-to-Point topology is for direct, switch-free connections between two FC devices - the opposite of a SAN fabric environment.
- D (FC Expansion Board) is a fabricated distractor; the HUS 110 architecture uses I/O interface boards (the iSCSI boards already present), and the correct FC upgrade path is via the FC-Option software/license, not a separate expansion board.
Memory tip: Think "FAN = Fabric And eNable" - when joining a FC-SAN (a Fabric network), you must set topology to Fabric ANd enable the FC-Option. Point-to-Point is for peer-to-peer, never for SANs.
Topics
Community Discussion
No community discussion yet for this question.