Table of Contents
Advertisement
Configuring a Secondary HP VMA SAN Gateway Node
Configuring a secondary SAN Gateway node is similar to configuring an additional node in a SAN
Gateway cluster (a standby or normal node).
If you are configuring an additional node in a cluster, you should have successfully completed
Note:
the procedure described in
23.
• Standby node: The second node added to the cluster is automatically designated as the
secondary node. Should the master node fail, the secondary node replaces it and becomes the
master node and cluster management traffic is automatically redirected to the new master
node.
All global cluster parameters defined on the master node are automatically inherited by the
secondary node added to the redundant pair. Consequently, the configuration of the secondary
node requires only seven steps as compared to the 25 steps required to configure the master
node.
• Normal nodes: Each additional SAN Gateway added to the cluster is defined as a normal node.
During the course of vCLUSTER operation, a normal node can assume the role of standby or
master. There is always only a single master and at most a single standby node.
Prerequisite
You will need the following information:
• Public interface name—public interface name defined for the secondary node
• Public interface IP address—public interface IP address for this Secondary Gateway
• Public interface netmask—netmask for the public interface IP address
• Hostname—hostname for this secondary Gateway
• Cluster interface name—the interface name configured on the master node
• Cluster ID—cluster ID is pre-configured with HP VMA SAN gateway and should not be
changed at this time.
Configuring a Node
To configure a HP VMA SAN Gateway node as a redundant pair, refer to the Redundant Gateway Pair-
ing Process Guide at http://www.hp.com/go/vma-docs
AM456-9025A
Configuring a HP VMA SAN Gateway Master/Standalone Node
HP VMA SAN Gateway Installation and Configuration Guide
on page
29
Advertisement
Table of Contents
