You have been asked to allocate storage from a Hitachi Unified Storage system to a cluster of AIX hosts. The application owner wants you to make sure that the queue depth is set to 16 for all the…

Question

Options

• Aon each LUN
• Bon the server HBAs
• Con the WWNN Target Ports
• Don the WWPN Target Ports

• A
  89% (47)
• B
  6% (3)
• C
  4% (2)
• D
  2% (1)

Explanation

Queue depth on a Hitachi Unified Storage (HUS) system is configured as a property of each individual LUN within the storage management software (e.g., Hitachi Storage Navigator). This per-LUN setting controls how many I/O commands the array will accept simultaneously for that specific logical unit, giving administrators granular control over performance for each workload.

Why the distractors are wrong:

• B (Server HBAs): HBAs do have queue depth settings, but those are host-side parameters controlling the adapter's overall command capacity - not the storage array's per-LUN configuration the question asks about.
• C (WWNN Target Ports): A WWNN (World Wide Node Name) identifies the entire storage node/controller, not a configurable point for queue depth - it's an identity, not a tuning parameter.
• D (WWPN Target Ports): WWPNs (World Wide Port Names) identify individual fabric ports and are used for zoning and access control, not for queue depth settings.

Memory tip: Think "LUN = Lane." Each LUN is like a dedicated traffic lane, and you control how many cars (I/O commands) can queue in that specific lane - not at the highway on-ramp (HBA) or the interchange signs (WWNs).

No community discussion yet for this question.