1 Network interconnection
2 Management server
3 Host 1
4 Host 2
5 Host 3
SUN Solaris configuration
Requirements
•
Switch zoning or controller level SSP must be used to ensure each single path HBA has an exclusive
path to its LUNs.
•
Single path HBA server can be in the same fabric as servers with multiple HBAs.
•
Single path HBA server cannot share LUNs with any other 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.
HBA configuration
•
Host 1 is a single path HBA host.
•
Host 2 is a multiple HBA host with multi-pathing software.
See
Figure
35.
Risks
•
Single path failure may result in loss of data accessibility and loss of host data that has not been
written to storage.
•
Controller shutdown results in loss of data accessibility and loss of host data that has not been
written to storage.
NOTE:
For additional risks, see
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 not supported.
112
Single Path Implementation
Table 29
on page 124.
6 SAN switch 1
7 SAN switch 2
8 Controller A
9 Controller B