Nodes

Each node is a single processing unit within a system.

For redundancy, nodes are deployed in pairs to make up a system. A system can have one to four pairs of nodes. Each pair of nodes is known as an I/O group. Each node can be in only one I/O group. A maximum of four I/O groups each containing two nodes is supported.

Note: Both nodes in an I/O group must have the same amount of memory installed.

At any one time, a single node in the system manages configuration activity. This configuration node manages a cache of the configuration information that describes the system configuration and provides a focal point for configuration commands. If the configuration node fails, another node in the system takes over its responsibilities.

Table 1 describes the operational states of a node.

Table 1. Node state
State	Description
Adding	The node was added to the clustered system but is not yet synchronized with the system state. The state changes to Online after synchronization is complete. Note: A node can stay in the Adding state for a long time. Wait at least 30 minutes before you take further action. If after 30 minutes the node state is still Adding, you can delete the node and add it again. If the node that has been added is at a lower code level than the rest of the system, the node is upgraded to the system code level, which can take up to 20 minutes. During this time, the node is shown as Adding.
Deleting	The node is in the process of being deleted from the system.
Online	The node is operational, assigned to a system, and has access to the Fibre Channel SAN fabric.
Offline	The node is not operational. The node was assigned to a system but is not available on the Fibre Channel SAN fabric. Run the fix 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.