What must be setup before adding an HUS110 into Hitachi Device Manager (HDvM) and discovering this storage system?

Question

Options

• Aa Command Device in the HUS110 mapped to the HDvM server
• Ba Storage Management Device in the HUS110 mapped to the HDvM server
• Ca TCP/IP connection between the HUS110 and the HDvM server
• Da SAN connection between the HUS110 and the HDvM server

• A
  3% (1)
• B
  3% (1)
• C
  89% (33)
• D
  5% (2)

Explanation

Option C is correct because the HUS110 is a midrange storage system that communicates with Hitachi Device Manager exclusively over an IP network. Before HDvM can discover and manage the HUS110, a TCP/IP connection must exist between the HUS110's management port and the HDvM server - this is the transport layer HDvM uses to send and receive management data.

Option A is wrong because Command Devices are a feature of enterprise Hitachi systems (such as the VSP family), where HDvM can issue management commands via a specially designated LUN over a SAN connection. The HUS110 does not support or require a Command Device for HDvM integration.

Option B is wrong because "Storage Management Device" is not a real Hitachi HDvM concept - it is a plausible-sounding distractor designed to confuse candidates familiar with Command Devices.

Option D is wrong because a SAN (Fibre Channel) connection is a data path, not a management path. HDvM discovers and manages the HUS110 over IP, not over a SAN fabric.

Memory tip: Think of the HUS110 as a "network-managed" box - the "U" in HUS stands for Unified, and unified/midrange systems talk to HDvM over the same TCP/IP network you use for everything else. Reserve "Command Device + SAN" for when you see enterprise VSP-class systems on the exam.

No community discussion yet for this question.