Solaris Cluster - New Installation - Attempt To Add Second Node (scinstall) Fails in Autodiscovery - "Unable to get configuration data from "<Sponsor Node>"
(Doc ID 2603824.1)
Last updated on DECEMBER 06, 2021
Applies to:Solaris Cluster - Version 4.3 to 4.4 [Release 4.3 to 4.4]
Information in this document applies to any platform.
When running /usr/cluster/bin/scinstall from Node2:
>>> Autodiscovery of Cluster Transport <<<
If you are using Ethernet or Infiniband adapters as the cluster
transport adapters, autodiscovery is the best method for configuring
the cluster transport.
Unable to get configuration data from "<Node1>".
Press Enter to continue:
This is a new installation. The scinstall command was previously run on Node1 selecting these menu options:
NOTE: Much of the output is not included as it is fairly lengthy.
*** Main Menu ***
* 1) Create a new cluster or add a cluster node
*** New Cluster and Cluster Node Menu ***
2) Create just the first node of a new cluster on this machine
>>> Typical or Custom Mode <<<
>>> Cluster Nodes <<<
This Oracle Solaris Cluster release supports a total of up to 16
List the names of the other nodes planned for the initial cluster
configuration. List one node name per line. When finished, type
Node name (Control-D to finish): <Node1>
Node name (Control-D to finish): ^D
>>> Confirmation <<<
Your responses indicate the following options to scinstall:
scinstall -i \
-C <Cluster_Name> \
-P task=quorum,state=INIT -P task=security,state=SECURE
Are these the options you want to use (yes/no) [yes]?
Do you want to continue with this configuration step (yes/no) [yes]?
/var/cluster/logs/install/scinstall.log.<#> will show something like this:
scinstall -ik -C <Cluster_Name> -F -o -P task=quorum,state=INIT -P task=security,state=SECURE
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document