Storage susbystems Configuration rules Host bus adapters

All SAN Volume Controller nodes of a cluster must be able to see the same set of storage subsystem ports on each device. Any operation that is in this mode in which two nodes do not see the same set of ports on the same device is degraded, and the system logs errors that request a repair action. This rule can have important effects on storage subsystem such as FAStT, which has exclusion rules that determine to which host bus adapter (HBA) WWNNs a storage partition can be mapped.

A configuration in which a SAN Volume Controller bridges a separate host device and a RAID array is not supported. Typical compatibility matrixes are shown in a document titled Supported Hardware List on the following Web page:

http://www.ibm.com/storage/support/2145

The SAN Volume Controller clusters must not share its storage subsystem devices with hosts. A device can be shared with a host under certain conditions as described in this topic.

Two SAN Volume Controller clusters must not share the same storage subsystem. That is, one device cannot present LUs to two different SAN Volume Controller clusters. This configuration is not supported.

The SAN Volume Controller must be configured to manage only LUNs that are presented by supported disk controller systems. Operation with other devices is not supported.

Unsupported storage subsystem (generic device)

When a storage subsystem is detected on the SAN, the SAN Volume Controller attempts to recognize it using its Inquiry data. If the device is recognized as one of the explicitly supported storage models, then the SAN Volume Controller uses error recovery programs that are potentially tailored to the known needs of the storage subsystem. If the device is not recognized, then the SAN Volume Controller configures the device as a generic device. A generic device may or may not function correctly when addressed by a SAN Volume Controller. In any event, the SAN Volume Controller does not regard accessing a generic device as an error condition and, consequently, does not log an error. MDisks presented by generic devices are not eligible to be used as quorum disks.

RAID array restrictions

A single RAID array must not be shared (by partitioning the RAID into many LUs) between a SAN Volume Controller and a direct attached host.

Split device configurations

In a split device configuration, a RAID array presents LUs to both a SAN Volume Controller (which treats the LU as an MDisk) and to another host. The SAN Volume Controller presents VDisks created from the MDisk to another host. There is no requirement for the pathing driver in the two hosts to be the same (although, if the RAID controller were an ESS, both hosts would use SDD). In Figure 34, the RAID controller is a FAStT, with RDAC used for pathing on the directly attached host, and SDD used on the host that is attached with the SAN Volume Controller. Hosts can simultaneously access LUs, which are provided by the SAN Volume Controller and directly by the device.

Figure 34. Disk controller system shared between SAN Volume Controller and a host
Disk controller system shared between SAN Volume Controller and a host

In the case where the RAID controller is an ESS, the pathing driver in the host would be IBM Subsystem Device Driver (SDD) for the ESS and SDD for the SAN Volume Controller LUs. Figure 35 a supported configuration since the same pathing driver is used for both direct and virtual disks.

Figure 35. ESS LUs accessed directly and via SAN Volume Controller
ESS LUs accessed directly and via SAN Volume Controller

Figure 36 illustrates another configuration.

Figure 36. FAStT direct connection via the SAN Volume Controller on one host
FAStT direct connection and via SAN Volume Controller on one host

(C) Copyright International Business Machines Corporation 2003, 2004