HP StorageWorks Clustered File System 3.6.0 Windows Storage Server Edition Setup Guide (403102-005, January 2008)

Chapter 2: Configuration Information 8
• HP Clustered File System supports only one “physical” IP address per
subnet per NIC per node. If additional IP addresses are needed on the
same subnet, use HP Clustered File System virtual hosts instead of
adding additional IP addresses directly to the NIC.
• For iSCSI configurations, we recommend that the storage be on a
separate network.
Cluster SAN Configuration Guidelines
Following are guidelines for configuring the cluster SAN to be used with
HP Clustered File System:
• For all FC 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.
• When the cluster is configured for fabric fencing, arrays must operate
in fabric or switch-attached mode (not arbitrated-loop-only devices).
This requirement does not apply for non-fabric fencing
configurations.
• The FC switches managed by the cluster must be from the same
vendor. Switches that will not be managed by HP Clustered File
System 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 different 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.
• Multiple FibreChannel switches are supported; however, they must be
configured in a manner that meets the following requirements:
– Each cluster server must have access to all of the disks to be used
by the cluster.