A storage administrator managing a Hitachi Device Manager (HDvM) environment has used Hitachi Storage Navigator Modular to create a LUN on an HUS110 system. What should be done next for this change…

Question

Options

• APerform a LUN refresh.
• BPerform a host refresh.
• CExecute the save function.
• DPerform a subsystem refresh.

• A
  4% (1)
• C
  4% (1)
• D
  93% (26)

Explanation

Option D is correct because when a LUN is created using Hitachi Storage Navigator Modular (an external tool operating directly on the array), HDvM is unaware of the change - it still holds its old view of the subsystem. A subsystem refresh tells HDvM to re-query the HUS110 and synchronize its database with the array's actual current configuration, including the new LUN.

Why the distractors are wrong:

• A (LUN refresh): HDvM does not have a standalone "LUN refresh" operation; discovery of configuration changes happens at the subsystem level, not per-LUN.
• B (Host refresh): A host refresh updates HDvM's view of host-side data (HBAs, paths, mappings) - it has no effect on what's configured on the storage array itself.
• C (Save function): "Save" applies when you've made changes within HDvM that need to be committed; since the change was made externally in Storage Navigator Modular, there is nothing pending inside HDvM to save.

Memory tip: Match the scope of the change to the scope of the refresh - the LUN was created at the subsystem level, so you refresh at the subsystem level to bring HDvM back in sync.

No community discussion yet for this question.