You are not signed in. or register.

Open High Availability Cluster FAQ

HA Clusters Quick Links

Download: Download the latest Open High Availability Cluster source
Participate: Join the OpenSolaris HA Clusters discussions
Contribute: Contribute to Open High Availability Cluster

Last Updated: January, 2008

This page is a list of Questions and Answers about Open High Availability Cluster.

For the general OpenSolaris FAQ, click here.

If you would like to ask a question or provide feedback on this FAQ, please send it to ha dash clusters dash discuss at opensolaris dot org.

Topics in this FAQ

Basics - questions to help you get started
Building Agents - questions about building the Open HA Cluster agents
Installing Sun Cluster - questions about installing Sun Cluster
Sun Cluster Configuration - Sun Cluster configuration questions

Questions:

Answers:

Section 1: Basics

Q: Which parts of Solaris Cluster have been open-sourced?
A: On the product side, most of the Sun Cluster agents have been open-sourced. Here is a complete list. In a second phase Sun Cluster Geo Edition got open sourced in December 2007. Sun Cluster Core has not yet been open-sourced.
On the test side, the CTI for TET framework and the DATS test suite have been open-sourced.

Q: Why aren't all the Sun Cluster agents open-sourced?
A: We are in the process of determining release rights for other agents. We plan to release source code for other agents as those rights are determined.

Q: Can I run the open-source agents on Sun Cluster 3.2 on Solaris 10?
A: Yes, you can run the agents built with these instructions on Sun Cluster 3.2 on Solaris 10.

Q: If I run the agents on Sun Cluster 3.2 / Solaris 10, are they supported?
A: No, there is no official support from Sun Microsystems. However, members of the HA Clusters community will try to help you.

Section 2: Building Agents

Q: What compiler can I use to build the agents?
A: You can use Sun Studio 11, Sun Studio 12, or gcc.

Q: Why does my build fail looking for libyabe.so?
A: You might see an error message in your build log like this:

/opt/SUNWspro//bin/cc -xO3 -xcg89 -Wa,-cg92 -xspace -W0,-Lt -Xa
-DTEXT_DOMAIN=\"\"  -DMESSAGE_DIR=\"/usr/cluster/lib/locale\"
-DSOL_VERSION=200710
-I/builds/ohacds+5.11+sparc/proto/Sol_11-nd/root_sparc/usr/include
-I/builds/ohacds+5.11+sparc/proto/Sol_11-nd/root_sparc/usr/cluster/include
-I/usr/include
-I/opt/scbld/ref_proto/ohac/ohac_latest/root_sparc/usr/cluster/include
-I/opt/scbld/ref_proto/ohac/ohac_latest/root_sparc/usr/cluster/include/rgm -Y
I,/usr/include -I/builds/ohacds+5.11+sparc/usr/src/cmd/ha-services/common -c
/builds/ohacds+5.11+sparc/usr/src/cmd/ha-services/common/ds_utils.c
ld.so.1: acomp: fatal: libyabe.so: open failed: No such file or directory
cc: Fatal error in /opt/SUNWspro/prod/bin/acomp : Killed
*** Error code 9
dmake: Fatal error: Command failed for target `ds_utils.o'
Current working directory /builds/ohacds+5.11+sparc/usr/src/cmd/ha-services/common/sparc

The problem is that your system is missing the SPROlang package, which is part of the "Support Files" in Sun Studio. You need to install the support files in addition to the compiler itself.

Q: The SUNWonbld package creates a user "gk" - what is it used for?
A: Don't worry about it; the Open HA Cluster build doesn't use it. In case you're curious, the password for the gk account is the root password of your machine at the time you installed the SUNWonbld package.

Q: Can I build the agents on Solaris 10 instead of Solaris Express?
A: It's not recommended, but it should work. You must then set OS=5.11 like:

 /opt/scbld/bin/nbuild -Da OS=5.11

Q: Can I build the agents specifically for Solaris 10?
A: No. We don't currently distribute the Core Reference Proto or Agents Closed Binaries for an S10 build.

Q: nbuild doesn't output anything indicating a result-- how do I know if my build succeeded?
A: Two ways:

You should receive an email reporting success or failure (see the next question for customzing the email address).

Look at the logs in

/builds/ohacds+5.11+PLATFORM/log/log.TIMEDATE.NUM/

Q: How do I customize the email address to which the build result email is sent?
A: On the nbuild command-line, set LOGNAME to your email address. For example,

/opt/scbld/bin/nbuild -Da LOGNAME=<your-email-addr>

Q: How can I tell nbuild that my Sun Studio compiler is somewhere other than /opt/SUNWspro/ ?
A: On the nbuild command-line, set SPRO to your compiler path. For example,

/opt/scbld/bin/nbuild -Da SPRO=<your-compiler-path>

Q: Why does my build fail on Solaris Express Community Edition Build 68 or newer looking for /usr/lib/libuuid.so.1?
A: With Solaris Express Comunity Edition Build 68 some libraries got moved from /usr/lib to /lib. Up until now no library from /lib was needed to build the ohacds source. If you try to build the source delivered with ohacds-src-20070626.tar.bz2, you will see an error like this:

/opt/SUNWspro//bin/cc -xO3 -DPOST_S9_BUILD  -W0,-xc99=%none -Xa -DTEXT_DOMAIN=\"SUNW_SC_DNS\" -DMESSAGE_DIR=\"/opt/SUNWscdns/lib/locale\"    -DSOL_VERSION=200710 -I/builds/ohacds+5.11+i386/proto/Sol_11-nd/root_i386/usr/include -I/builds/ohacds+5.11+i386/proto/Sol_11-nd/root_i386/usr/cluster/include     -I/usr/include -I/opt/scbld/ref_proto/ohac/ohac_latest/root_i386/usr/cluster/include -I/opt/scbld/ref_proto/ohac/ohac_latest/root_i386/usr/cluster/include/rgm -Y I,/usr/include -I/builds/ohacds+5.11+i386/proto/Sol_11-nd/root_i386/usr/cluster/include
-I/builds/ohacds+5.11+i386/proto/Sol_11-nd/root_i386/usr/cluster/include/rgm  -I/builds/ohacds+5.11+i386/usr/src/cmd/ha-services/common -s    -o dns_svc_start dns_svc_start.c dns.o -s -L/builds/ohacds+5.11+i386/proto/root_i386/usr/lib -L/builds/ohacds+5.11+i386/proto/root_i386/usr/cluster/lib  -L /usr/lib -L/opt/scbld/ref_proto/ohac/ohac_latest/root_i386/usr/cluster/lib -Y P,/usr/lib -Y P,/opt/scbld/ref_proto/ohac/ohac_latest/root_i386/usr/cluster/lib -R/usr/cluster/lib -lscf -ldsdev -lscha -L/builds/ohacds+5.11+i386/usr/src/cmd/ha-services/common/i386 -lds_common
ld: warning: file libdladm.so.1: required by /usr/lib/libuuid.so.1, not found
Undefined            first referenced
 symbol                  in file
dladm_walk                          /usr/lib/libuuid.so.1
ld: fatal: Symbol referencing errors. No output written to dns_svc_start

The solution is to either apply the following diff to ohacds/usr/src/Makefile.master.cl (revision 1.115):

--- Makefile.master.cl.orig     Wed Jun 13 03:12:55 2007
+++ Makefile.master.cl  Thu Aug  2 19:40:24 2007
@@ -157,8 +157,8 @@
 
 REF_PROTO=
 $(CLOSED_BUILD)REF_PROTO=      $(BUILD_TOOLS)/ref_proto/$(REFERENCE_PROTO)/root_$(MACH)
-REF_LIBS=      $(REF_PROTO)/usr/lib
-REF_LIBS64=    $(REF_PROTO)/usr/lib/$(MACH64)
+REF_LIBS=      $(REF_PROTO)/usr/lib $(REF_PROTO)/lib
+REF_LIBS64=    $(REF_PROTO)/usr/lib/$(MACH64) $(REF_PROTO)/lib/$(MACH64)
 REF_INC=       $(REF_PROTO)/usr/include
 
 #
@@ -274,8 +274,8 @@
 DEV_CM=                "@($(POUND_SIGN))$(DEV_NM) Internal Development: $(VERSION) `$(ECHO) $$LOGNAME` `date +%Y-%m-%d` `$(ECHO) [\`basename $$CODEMGR_WS\`]`"
 
 LIBCC_                 = -lCstd -lCrun
-LIBCC_32       = -L$(REF_LIBS) -lCstd -lCrun
-LIBCC_64       = -L$(REF_LIBS64) -lCstd -lCrun
+LIBCC_32       = $(REF_LIBS:%=-L%) -lCstd -lCrun
+LIBCC_64       = $(REF_LIBS64:%=-L%) -lCstd -lCrun
 LIBCC                  = $(LIBCC_$(CLASS))
 NM                     =/usr/ccs/bin/nm
 
@@ -431,10 +431,10 @@
 ENVLIBS2= $(ENVROOT2:%=-L%/usr/cluster/lib) $(ENVROOT2:%=-L%/usr/lib)
 
 DEFAULT_LPATH= $(ENVLDLIBS1:%usr/ccs/lib=%usr/cluster/lib) \
-               -L $(REF_LIBS) -L$(REF_CL_LIBS) \
+               $(REF_LIBS:%=-L%) -L$(REF_CL_LIBS) \
                $(ENVLDLIBS2:%usr/ccs/lib=%usr/cluster/lib) \
                $(ENVLDLIBS3:%usr/ccs/lib=%usr/cluster/lib)  \
-               $(CCYLIBS)$(REF_LIBS) $(CCYLIBS)$(REF_CL_LIBS) \
+               $(REF_LIBS:%=$(CCYLIBS)%) $(CCYLIBS)$(REF_CL_LIBS) \
                -R/usr/cluster/lib
 
 LDLIBS.cmd =   $(DEFAULT_LPATH)

Or to download the already modified Makefile.master.cl-1.115-fix.txt and copy it to your ohacds/usr/src/Makefile.master.cl. This change is already included in the ohacds-src-20070816.tar.bz2 source archive.

Section 3: Installing Sun Cluster

Q: Where can I find documentation about how to install Sun Cluster 3.2 on Solaris 10?
A: Start with the Sun Cluster Quick Start Guide for Solaris OS, which provides an example of how to install and configure a specific Sun Cluster configuration. The Sun Cluster Software Installation Guide for Solaris OS describes the complete installation process for various kinds of configurations. The easiest way to get started is to install a single-node cluster configuration. There is a blog available, describing an example on how to configure HA Samba failover between non-global zones using ZFS on a single node cluster.

Q: Can I install Solaris 10 and Sun Cluster 3.2 on 32-bit x86 systems?
A: No. Sun Cluster 3.2 does not contain support for 32-bit systems on Solaris 10. However, Solaris Cluster Express has 32-bit support on Solaris Express for x86 systems, read the installing instructions for more details.

Q: Can I install Solaris Cluster Express Community Edition and Solaris Cluster Express on 32bit x86 systems?
A: Yes.
Back to Top

Section 4: Sun Cluster Configurations

Q: Can I use iSCSI with Sun Cluster?
A: Solaris Cluster Express is not yet qualified with iSCSI devices as shared disks. We are not sure as of now when iSCSI support will be available.
Back to Top