A user reports that a host is unable to see the LUNs added with Hitachi Device Manager (HDvM). When troubleshooting, which two actions should you perform? (Choose two.)

Question

Options

• ARestart the HDvM services.
• BVerify the paths between the host and the storage system.
• CVerify the Alerts in HDvM.
• DSet "server.base.initialsynchro=true" in the HDvM server.properties file.

• A
  6% (2)
• B
  83% (29)
• D
  11% (4)

Explanation

When a host can't see newly added LUNs in HDvM, the first instinct should be to check the physical and logical paths between the host and storage (B) - a misconfigured or inactive path means the LUN simply won't be visible, regardless of HDvM configuration. Alongside that, checking HDvM Alerts (C) is the fastest way to surface errors that HDvM itself has already detected and flagged, such as discovery failures, unreachable hosts, or zoning issues.

Why the distractors are wrong:

• A (Restart HDvM services): Restarting services is a blunt, disruptive action and not a diagnostic step - you'd only do this after identifying a service-level fault, not as an initial troubleshooting move.
• D (Set server.base.initialsynchro=true): This property forces a full re-synchronization on server startup and is a corrective action for known sync issues, not a standard troubleshooting step for missing LUNs.

Memory tip: Think "See and Alert" - you can't see a LUN if the path (B) isn't there, and HDvM alerts (C) will tell you why. Both are observe-first actions, which is always the right starting point in troubleshooting before taking any corrective action.

No community discussion yet for this question.