OceanStor Dorado HyperMetro uses Fast Write to accelerates writes across sites over FC links, which commands are combined into one?

Question

Options

• ATrensfer ready
• BData transfer
• CWrite
• DStatus good

• A
  17% (5)
• B
  77% (23)
• D
  7% (2)

Explanation

In standard Fibre Channel write operations, the sequence normally requires four separate exchanges: Write command, Transfer Ready, Data Transfer, and Status Good. HyperMetro Fast Write optimizes cross-site latency by merging the Write command (C) and Data Transfer (B) into a single combined operation, allowing the initiator to send both the command and the payload without waiting for a Transfer Ready signal from the target - this cuts round-trip overhead over the inter-site FC link.

Transfer Ready (A) is wrong because it is precisely the step that Fast Write eliminates; it is the handshake Fast Write bypasses, not one it combines. Status Good (D) is wrong because it is the final acknowledgment returned by the target after the write completes, and it remains a separate, subsequent step rather than something merged into the write initiation.

Memory tip: Fast Write = "Write + Data go together." Think of it as the host not waiting for permission (Transfer Ready) before sending data - it bundles the command and the payload in one shot to cut latency across sites.

No community discussion yet for this question.