A configuration node is a single
node that manages configuration activity of the system.
The configuration node also handles the following functions:
Accepts user logins to the management GUI and CLI via the IP address that is bound to Ethernet
port 1 and optionally to the second management IP address that is bound to Ethernet port 2.
Sends system configuration changes to the other nodes in the system.
Sends call home and system notifications on behalf of the system.
If the configuration node fails or is taken offline, the system chooses a new
configuration node. This action is called configuration node failover. The new configuration node
takes over the management IP addresses. Thus, you can access the system through the same IP
addresses although the original configuration node failed. During the failover, there is a short
period when you cannot use the command-line tools or management GUI.
For correct failover operation, all nodes of the system must be connected to the same subnet and
the management IP configuration must be valid on the subnet.
Figure 1 shows an example of a clustered system that contains four
nodes. Node 1 is the configuration node. User requests ( 1 ) are handled
by node 1.Figure 1. Configuration node
