HP StorageWorks 4000s NAS 4000s and 9000s Administration Guide - Page 204

Cluster Administration In preparing for the cluster installation: ■ All software components listed in the SAN connection tool must be installed and the fiber cables attached to the HBA(s) before the cluster installation is started. ■ All shared disks, including the quorum disk, must be accessible from both nodes. When testing connectivity between server and LUN, only one server should be given access to the LUN at a time or the non-testing server should be powered off. ■ All shared disks must be configured as basic (not dynamic). ■ All partitions on the disks must be formatted as NTFS. Network Planning Clusters require more sophisticated networking arrangements than a stand alone NAS device. For example, because a cluster must be deployed into a domain environment, workgroups are not supported. A Windows NT domain or Active Directory domain must be in place to contain the cluster names, virtual server names, and user and group information. A cluster cannot be deployed into a non domain environment. All cluster deployments have at least seven network addresses and network names: ■ The cluster name (Unique NETBIOS Name) and IP address ■ Node A's name and IP address ■ Node B's name and IP address ■ At least one virtual server name and IP address for Node A ■ At least one virtual server name and IP address for Node B ■ Cluster Interconnect static IP addresses for Node A and Node B In multi node deployments additional network addresses are required. For each additional node, three static IP addresses are required. Virtual names and addresses are the only identification used by clients on the network. Because the names and addresses are virtual, their ownership can transition from one node to the other during a failover, preserving access to the shares on the virtual disks. In addition, a cluster will use at least two network connections on each node: ■ The cluster interconnect or "heartbeat" crossover cable connects to the first network port on each cluster node. In more than two node deployments, a private VLAN on a switch or hub is required for the cluster interconnect. ■ The client network subnet connects to a second network port on each cluster node. The cluster node names and virtual server names will have IP addresses residing on these subnets. Note: If the share is to remain available during a failover, each cluster node must be connected to the same network subnet. It is impossible for a cluster node to serve the data to a network to which it is not connected. 204 NAS 4000s and 9000s Administration Guide