Solaris Cluster 3.3 Panic or Hang at Boot Time with "clcomm: per node IP config clprivnet0" due to Conflict with OpsCenter Agent
Last updated on JULY 25, 2017
Applies to:Solaris Cluster - Version 3.3 to 3.3 U2 [Release 3.3]
Solaris Cluster Geographic Edition - Version 3.2 U3 to 3.3 U2 [Release 3.2 to 3.3]
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on x86-64 (64-bit)
The problems can happen during the boot of a Solaris Cluster node. The key symptom is the presence of these messages regarding "per node IP config" after the join into cluster:
Notice that in such cases, the message could be caused by duplicate IP rather than the issue describe here. Before following this document, it would be necessary to exclude the presence of other hosts using the cluster private IP addresses and therefore causing an actual IP duplication problem. Such a situation can happen if the private network is not isolated and multiple cluster are sharing the same switches and using the same IP addresses.
The customer is using OpsCenter 12.2.x to manage the datacenter. The cluster nodes have been added to OpsCenter as new assets, resulting into configuration of the OpsCenter Agent and related services on each of the nodes.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms