A customer has installed a D3940 storage module in an existing Synergy frame. However, none of the compute modules can access the shared storage. What is the problem?

Question

Options

• AThe storage module has not been initialized in the composer
• BThere are no SAS modules installed in bays 1 and 4
• CThere are no fibre channel modules installed in bays 1 and 4
• DThe I/O modules have not been initialized in the composer

• A
  9% (4)
• B
  77% (36)
• C
  13% (6)
• D
  2% (1)

Explanation

Option B is correct because the HPE Synergy D3940 Storage Module uses SAS (Serial Attached SCSI) as its connectivity protocol, and the Synergy frame requires SAS Connection Modules installed in interconnect bays 1 and 4 to physically link the D3940 to compute modules - without them, no data path exists regardless of software configuration.

Why the distractors fail:

• A (not initialized in Composer): Initialization is a software step; it's irrelevant if the physical SAS connection doesn't exist yet - you can't configure what isn't physically connected.
• C (no Fibre Channel modules): The D3940 is a direct-attached SAS storage device, not a Fibre Channel target; FC modules are for SAN connectivity, not D3940 access.
• D (I/O modules not initialized): Like option A, this confuses a software configuration step for a missing hardware prerequisite.

Memory tip: Think "SAS in 1 and 4 before the D3940 does more" - the D3940 is SAS-based, and Synergy's interconnect bays 1 and 4 are the dedicated fabric bays that must hold SAS modules to bridge storage to compute. If the physical fabric isn't there, no amount of Composer configuration will help.

No community discussion yet for this question.