HBA configuration
• Host 1 is a single path HBA.
• Host 2 is a dual HBA host with multipathing software.
See Figure 68 (page 143).
Risks
• Single path failure may result in data loss or disk corruption.
NOTE: For additional risks, see “Linux” (page 149).
Limitations
• HP P6000 Continuous Access is not supported with single path configurations.
• Single HBA path at the host server is not part of a cluster, unless in a Linux High Availability
Cluster.
• Booting from the SAN is supported on single path HBA servers.
Figure 68 Linux (32-bit) configuration
5. SAN switch 11. Network interconnection
6. SAN switch 22. Single HBA server (Host 1)
7. Controller A3. Dual HBA server (Host 2)
8. Controller B4. Management server
Linux (Itanium) configuration
Requirements
• Switch zoning or controller level SSP must be used to ensure each single path HBA has an
exclusive path to its LUNs.
• All nodes with direct connection to a disk must have the same access paths available to them.
• Single path HBA server can be in the same fabric as servers with multiple HBAs.
• In the use of snapshots and snapclones, the source virtual disk and all associated snapshots
and snapclones must be presented to the single path hosts that are zoned with the same
Linux (Itanium) configuration 143