32G FC and 10Gb Ethernet: checking storage connectivity

Protocol before port speed

FC and Ethernet are different connectivity environments. A similar housing or connector does not establish transceiver compatibility. State how the application accesses block data, which host adapter is installed and which network is available. Protocol support in a product family does not establish that a particular port and licence are ready for that access method.

Record each path separately

Illustrative example: two independent paths

Path A runs from the host adapter through switch A to the array, while path B uses a separate switch B. Label every endpoint and cable in the patch plan. Review physical separation, power and management dependencies. During acceptance testing, verify that I/O continues over the remaining path when one path is lost.

Two four-port modules provide eight physical ports. Adding their nominal rates does not calculate application throughput: traffic distribution, hosts, switches and workload affect the result. Keep port bit/s ratings separate from application byte/s measurements, and identify which ports are actually connected.

Compatibility and handover

Before purchasing, retain the versioned compatibility matrix and approve any exceptions. Include normal I/O, path states and response to path loss in an authorised test window in the acceptance plan. Handover should provide the as-built patch plan, adapter and optic inventory, and confirmation of host settings. Agree who owns changes when a driver or storage release is later upgraded.