Nodes
A SAN Volume Controller node
is a single processing unit within a SAN Volume Controller cluster. Nodes are deployed in
pairs, for redundancy, to make up a cluster. A cluster may have 1 or 2 node
pairs in it. Each pair of nodes is known as an I/O group. Each node
may be in only one I/O group.
At any one time, a single node in the cluster is used to manage configuration
activity. This configuration node manages a cache of the configuration information
that describes the cluster configuration and provides a focal point for configuration
commands. If the configuration node fails, another node in the cluster will
take over its responsibilities.
There are five states in which a node can exist, as described by the following
table:
Table 7. Node state
| State |
Description |
| Adding |
The node was added to the cluster but is not yet synchronized
with the cluster state (see Note). |
| Deleting |
The node is in the process of being deleted from the
cluster. |
| Online |
The node is operational, assigned to a cluster, and
has access to the Fibre Channel SAN fabric. |
| Offline |
The node is not operational. The node was assigned to
a cluster but is not available on the Fibre Channel SAN fabric. Run the Directed Maintenance Procedures to determine the problem. |
| Pending |
The node is transitioning between states and, in a few
seconds, will move to one of the other states. |
 | Note: It is possible that a
node can stay in the Adding state for a long time. If this is the case, delete
the node and then re-add it. However, you should wait for at least 30 minutes
before doing this. If the node that has been added is at a lower code level
than the rest of the cluster, the node will be upgraded to the cluster code
level, which can take up to 20 minutes. During this time the node will be
shown as adding. |
|