Last updated on OCTOBER 05, 2017
Applies to:Solaris Cluster - Version 3.0 to 4.3 [Release 3.0 to 4.3]
Solaris Cluster Geographic Edition - Version 3.1 to 4.3 [Release 3.1 to 4.3]
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on SPARC (32-bit)
Oracle Solaris on x86-64 (64-bit)
A Solaris cluster reconfiguration can be triggered by a variety of events such as a change in the membership of cluster
(one node that leaves/joines the cluster is a good example of this type) or also by a change in the quorum device configuration (such as Adding/Changing/Removing QD)
All those events mentioned above imply either a change in the configuration or the execution of operations that might be unaffordable at a given time
(such as bringing one node down).
Nevertheless there might be the need to force a Solaris Cluster reconfiguration for testing purposes.
For instance one might want to test the ability to send snmp trap of Solaris Cluster after having configured it.
Forcing a cluster reconfiguration is a good method to generate an event that triggers the sending of a snmp trap by Solaris Cluster.
Such a cluster reconfiguration does not interfere with normal Solaris Cluster activities , it is harmless and doesn't need any change in cluster
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms