Which two Hitachi Device Manager procedures would you use to add an HUS system as external storage to a VSP? (Choose two.)

Question

Options

• ASet the Local storage port to Target.
• BSet the external system port to External.
• CDetect external LUNs on the Local system.
• DSet LDEV attributes of the external storage on the Local system.

• A
  18% (6)
• B
  9% (3)
• C
  73% (24)

Explanation

Detecting external LUNs (C) and setting LDEV attributes (D) are the two Hitachi Device Manager steps performed on the local VSP to integrate the HUS as external storage. First, the VSP must discover (detect) the LUNs presented by the HUS over the fabric connection - this is the discovery phase. Then, LDEV attributes must be configured on the local VSP so the system can treat those external volumes as its own logical devices, enabling hosts to access them through the VSP.

Why A is wrong: The local VSP port must be set to External mode (not Target). Target mode is for host-to-storage connections, not storage-to-storage external virtualization.

Why B is wrong: It's backwards - it's the local VSP port that gets set to External mode. The HUS (external system) port is configured as a standard Target; you don't change it to "External."

Memory tip: Both correct steps are actions taken on the local system (VSP) - think "Detect then Define on the local side." If an answer involves configuring the external system or setting a port to the wrong role (Target instead of External on the local side), it's a distractor. The VSP does the work; the HUS just presents its volumes.

No community discussion yet for this question.