When configuring a Red Hat High Availability Add-On cluster, you must take the following considerations into account:
Red Hat does not support cluster deployments greater than 16 full cluster nodes. It is possible, however, to scale beyond that limit with remote nodes running the
service. For information on the
service, see Section 9.4, “The pacemaker_remote Service”
The use of Dynamic Host Configuration Protocol (DHCP) for obtaining an IP address on a network interface that is utilized by the
corosync daemons is not supported. The DHCP client can periodically remove and re-add an IP address to its assigned interface during address renewal. This will result in
corosync detecting a connection failure, which will result in fencing activity from any other nodes in the cluster using
corosync for heartbeat connectivity.