My Oracle Support Banner

Solaris Cluster 3.3 in Guest LDom: During ‘scinstall’ when Node/Server/System Joins Cluster the First Time a Panic can occur, the Panic can also occur when Upgrade Oracle Virtual Manager (OVM) in Control Domain (Doc ID 1618131.1)

Last updated on SEPTEMBER 19, 2018

Applies to:

Solaris Cluster - Version 3.3 U1 to 3.3 U2 [Release 3.3]
Oracle Solaris on SPARC (64-bit)

Symptoms

When using Oracle Virtual Manager (OVM) 3.1.0.0.24 with Solaris 10 in the control domain on SPARC systems it is not possible to install Solaris cluster 3.3 into guest domains.
Communication is not possible over the private interconnect of the Solaris Cluster guest LDoms.

This issue

 

A) Example when a 2-node Solaris Cluster 3.3 get installed in guest LDoms

After scinstall process when the second node tries to join the cluster it will panic with:

 

 

Cause

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
Symptoms
 A) Example when a 2-node Solaris Cluster 3.3 get installed in guest LDoms
 B) Example when one of the primary domain is upgraded to OVM 3.1 or later
 C) Example when Control domain and IO domain each handles a private interconnect with different extended-mapin-space setting.
Cause
Solution
 Solutions
 Workaround
 Alternative workaround is to set the parameter extended-mapin-space=off in all guest domains which are running Solaris Cluster 3.3 with:
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.