F Hp Clustered Gateway Deployments; Windows; Hba Configuration; Mpio Software - HP StorageWorks P9000 Configuration Manual

F HP Clustered Gateway deployments

Windows

The HP Cluster Gateway and HP Scalable NAS software both use the HP PolyServe software as
their underlying clustering technology and both have similar requirements for the P9000 disk array.
They have both been tested with the P9000 disk arrays and this appendix details configuration
requirements specific to P9000 deployments using HP PolyServe Software on Windows.
For details on installing and configuring the HP PolyServe software, see the HP PolyServe Matrix
Server Installation Guide.
For any P9000-specific requirements, see the Enterprise Scalable NAS Products and Solutions
Compatibility Matrix, which you can download from
support/SupportManual/c01336151/c01336151.pdf.

HBA configuration

HP recommends using the HBA drivers specifically supported by the P9000 array. Other drivers
will work, but may not produce optimal results during failure or failover situations.
While using the HP PolyServe software, many servers could be accessing the same LUNs on the
array and may cause the host servers to put a lot of I/O stress on the LUNs. You may need to
reduce the HBA queue depth to prevent the host servers from overrunning the LUN.

MPIO software

The HP Cluster Gateway and HP Scalable NAS software running on Windows should use the Full
Featured DSM driver for P9000 arrays as their multipath I/O solution.

Array configuration

LUN presentation

To work correctly with the HP PolyServe clustering technology, all LUNs on the disk array need to
be presented identically to all nodes in the cluster. Before using the LUNs for membership partitions
or file systems, create a Windows partition table on the LUNs using a tool such as Logical Disk
Manager or DiskPart, but do not put an NTFS file system on it and do not assign it a drive letter.
The partition table should be created from one node in the cluster. When it is subsequently imported
into the cluster, the other nodes will then have visibility to it.

Membership partitions

HP Scalable NAS uses a set of membership partitions to control access to the SAN and to store
the device naming database, which includes the global device names that HP Scalable NAS
assigns to the SAN disks placed under its control. The membership partitions must be placed on
the SAN, not on local storage.
HP Scalable NAS can use either one or three membership partitions, but to ensure that a membership
partition is always available, we strongly recommend that you use three membership partitions.
HP recommends that you create three LUNs for the membership partitions. Each LUN should be a
minimum of 1 GB in size.

Snapshots

Snapshots are not currently integrated into the HP Scalable NAS software for Windows.

Dynamic volume and file system creation

When the LUNs have been presented to all nodes in the cluster, import them into the cluster using
the GUI or the mx command. After the disks are imported, and you have put a partition table on
158 HP Clustered Gateway deployments
http://bizsupport2.austin.hp.com/bc/docs/