Risks
• Single path failure may result in data loss or disk corruption.
NOTE: For additional risks, see Table 61 (page 165).
Limitations
• HP Continuous Access EVA is not supported with single path configurations.
• Single path HBA server is not part of a cluster.
• Booting from the SAN is supported on single path HBA servers.
Figure 56 Linux (32-bit) configuration
5 SAN switch 11 Network interconnection
6 SAN switch 22 Host 1
7 Controller A3 Host 2
8 Controller4 Management server
Linux (64-bit) 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
controller. In the case of snapclones, after the cloning process has completed and the clone
becomes an ordinary virtual disk, you may present that virtual disk as you would any other
ordinary virtual disk.
• Linux 64-bit servers can support up to14 single or dual path HBAs per server. Switch zoning
and SSP are required to isolate the LUNs presented to each HBA from each other.
HBA configuration
• Host 1 and 2 are single path HBA hosts.
• Host 3 is a dual HBA host with multi-pathing software.
See Figure 57 (page 161).
160 Single Path Implementation
To Next Page
Loading...
Need help?
General