Processing Time For cluster_config Might Take Longer On A Head Node With Improved Availability

The cluster_config utility processing time can take approximately ten minutes longer if it is run on a head node that is configured for improved availability with Serviceguard when the remaining nodes of the cluster are up and running.

After the entire system has been imaged and booted, you might need to re-run the cluster_config procedure to modify the node configuration. If the other node in the availability set with the head node is up and running, the Serviceguard daemons attempt to establish Serviceguard related communication with the node when they are restarted. Because the other node in the availability set is not actively participating in a Serviceguard cluster, it will not respond to the Serviceguard communication.

The Serviceguard software on the head node retries this communication until the communication times out. On a system running with the default Serviceguard availability configuration, the timeout is approximately ten minutes.