3.7.0 HP StorageWorks HP Scalable NAS File Serving Software installation guide HP Scalable NAS for Linux (AG513-96004, October 2009)

Cluster SAN configuration guidelines
Following are guidelines for configuring the cluster SAN to be used with HP Scalable
NAS:
For all Fibre Channel switches, it is best practice to place each HBA port and its
storage ports in a separate zone. No other initiator HBA port should be present
in this zone.
IMPORTANT:
If the cluster configuration includes an HP Fibre Channel Virtual Connect Module,
the guideline above must be implemented. If this is not done, the cluster can
experience excessive timeouts and a loss of stability.
The Fibre Channel switches managed by the cluster must be from the same vendor.
Switches that will not be managed by HP Scalable NAS can be from other vendors
only if all of the vendors have approved the configuration.
With fabric fencing, if the servers are connected to switches in multiple fabrics,
the physical ports on each switch must be assigned to unique domain IDs. A dif-
ferent domain ID must be used on each fabric (any given domain ID can exist on
only one fabric in the SAN). For example, if a server is connected to two switches
that are not in the same fabric, switch1 could use domain ID 6 and switch2 could
use domain ID 7. Domain ID 6 must not exist on the fabric containing switch2
and domain ID 7 must not exist on the fabric containing switch1.
To eliminate single points of failure, configure the SAN to use multipath I/O. See
the HP Scalable NAS File Serving Software administration guide for some sample
cluster configurations that include this feature.
Disk Power Management must be disabled on any Windows systems that have
access to the SAN storage.
NOTE:
You can attach a cluster server to other SANs that are not under HP Scalable NAS
control. These SANs can include tape drives and non-PSFS filesystems. You can use
Linux utilities or other applications to access these devices and filesystems.
Configuration information12