Configuring Sun Java System Messaging Server 6.3 With Sun Cluster

Configuring Sun JavaTM System Messaging Server 6.3

With SunTM Cluster 3.1 Software

Durga Deep Tirunagari June 2007 (Updated August 2007)

Abstract: This document describes how to install and configure a two-node, asymmetric, high availability (HA) cluster for Sun Java System Messaging Server 6.3 with Sun Cluster 3.1 software. This document also shows how to unconfigure the same two-node cluster. These instructions are valid on both x86 and SPARC®platforms.

Copyright © 2007 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights reserved.

U.S. Government Rights - Commercial software. Government users are subject to the Sun Microsystems, Inc. standard license agreement and applicable provisions of the FAR and its supplements. Use is subject to license terms. This distribution may include materials developed by third parties.

Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in the U.S. and in other countries, exclusively licensed through X/Open Company, Ltd. X/Open is a registered trademark of X/Open Company, Ltd.

All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the US and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc.

Sun, Sun Microsystems, the Sun logo, Java, Solaris, Solstice DiskSuite, Sun Cluster, and Sun Fire are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries.

This product is covered and controlled by U.S. Export Control laws and may be subject to the export or import laws in other countries. Nuclear, missile, chemical biological weapons or nuclear maritime end uses or end users, whether direct or indirect, are strictly prohibited. Export or reexport to countries subject to U.S. embargo or to entities identified on U.S. export exclusion lists, including, but not limited to, the denied persons and specially designated nationals lists is strictly prohibited.

DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.

Configuring Sun Java System Messaging Server 6.3 With Sun Cluster 3.1 Software 2

Table of Contents1. Installing and Configuring an Asymmetric Cluster ..............................................................................5

1.0 Install Sun Cluster 3.1 Software......................................................................................................51.1 Prepare Both Nodes of the Cluster..................................................................................................6

1.1.1 Edit the /etc/hosts File.............................................................................................................61.1.2 Create the Mount Points..........................................................................................................61.1.3 Create the Messaging Server User...........................................................................................7

1.2 Install the Sun Java System Messaging Server 6.3 Binaries on Both Cluster Nodes.....................81.3 Install the Messaging HA Agent Package (SUNWscims) on Both Cluster Nodes.........................81.4 Configure the Cluster......................................................................................................................8

1.4.1 Register the Resource Type Registration Files and Verify the Registration...........................81.4.2 Create a Failover Resource Group for This Instance of the Software...................................101.4.3 Create a Logical Host Name Resource..................................................................................101.4.4 Create an HAStoragePlus Resource......................................................................................101.4.5 Enable the HAStoragePlus Resource.....................................................................................111.4.6 Test the Creation of the Resource Group..............................................................................11

1.5 Configure Sun Java System Messaging Server 6.3 on the Primary Node ...................................121.6 Configure Sun Java System Messaging Server 6.3 on the Secondary Node ...............................121.7 Run the HA Configuration Program (ha_ip_config).....................................................................13

1.7.1 Run ha_ip_config on the Primary Node (nemo.example.com) ............................................131.7.2 Fail Over to the Secondary Node...........................................................................................141.7.3 Run ha_ip_config on the Secondary Node (dory.example.com)...........................................14

1.8 Create the Sun Java System Messaging Server HA Resource......................................................141.9 Verify That Everything Is Working .............................................................................................15

2. Unconfiguring the Asymmetric Cluster ..............................................................................................162.1 Take the Resource Group Offline.................................................................................................162.2 Disable the Messaging Server Resource.......................................................................................162.3 Disable the Logical Host Name Resource.....................................................................................162.4 Disable HAStoragePlus Resource.................................................................................................162.5 Remove the Messaging Server Resource......................................................................................172.6 Remove the Logical Host Name resource.....................................................................................172.7 Remove the HAStoragePlus Resource..........................................................................................172.8 Remove the Resource Group.........................................................................................................172.9 Unregister the Resource Types That Are Not in Use....................................................................17

3. Installing Sun Cluster 3.1 Software.....................................................................................................173.1 Install Solaris 10 Operating System on Both Nodes of the Cluster..............................................183.2 Install Sun Cluster 3.1 Software Using the Java Enterprise System (Java ES) Installer..............193.3 Configure the Sun Cluster 3.1 Software .......................................................................................21

4. Installing Sun Java System Messaging Server 6.3...............................................................................224.1 Select Sun Java System Messaging Server 6.3 in the Installation Wizard....................................224.2 Specify the Installation Directories...............................................................................................234.3 Choose the Configure Later Option..............................................................................................24

5. Configuring Sun Java System Messaging Server 6.3..........................................................................255.1 Run the Configuration Wizard......................................................................................................265.2 Specifying the Fully Qualified Host Name ..................................................................................26


5.3 Specify the Directory in Which to Store the Messaging Server Configuration............................275.4 Specify the Messaging Server User...............................................................................................285.5 Verify That the Configuration Was Successful.............................................................................29

6. Creating File Systems Using Solaris Volume Manager.......................................................................306.1 Create the Diskset..........................................................................................................................30

6.1.1 Create the State Database Replicas........................................................................................316.1.2 Verify the State Database Replicas........................................................................................316.1.3 Create the Diskset..................................................................................................................32

6.2 Add Mediator Hosts......................................................................................................................336.2.1 Take Ownership of the Diskset..............................................................................................336.2.2 Add the Mediator Hosts.........................................................................................................336.2.3 Verify That the Mediator Hosts Were Successfully Added..................................................33

6.3 Add Drives to the Diskset.............................................................................................................346.4 Create Volumes.............................................................................................................................34

6.4.1 Create Disk Stripes and Mirrors............................................................................................346.4.2 Verify the Creation of Disk Stripes and Mirrors...................................................................346.4.3 Create a Soft Partition............................................................................................................35

6.5 Modify the md.tab File on Both Nodes.........................................................................................356.5.1 Modify md.tab on the Primary Node.....................................................................................356.5.2 Modify md.tab on the Secondary Node.................................................................................36

6.6 Create UFS File Systems...............................................................................................................366.6.1 Create the New UFS File Systems on the Raw Disks...........................................................366.6.2 Verify the Creation of the File System..................................................................................37

7. Useful Sun Cluster Administration Commands...................................................................................377.1 Determine the Cluster Status.........................................................................................................377.2 Bring the Resource Group Online.................................................................................................387.3 Verify That the Resource Group Is Online...................................................................................387.4 Display the Status of the Quorum Device.....................................................................................387.5 Display the Status of the Cluster Nodes........................................................................................387.6 Display the Configuration of the Cluster......................................................................................387.7 Check the Validity of the /etc/vfstab File......................................................................................39

8. Enabling Cluster Debugging................................................................................................................398.1 Log Messages From the Messaging Server Agents......................................................................398.2 Edit the syslog.conf File................................................................................................................39

9. Example Output From Commands......................................................................................................399.1 Output of scinstall.........................................................................................................................409.2 Output of scstat..............................................................................................................................439.3 Output of scstat -g.........................................................................................................................469.4 Output of scstat -q.........................................................................................................................479.5 Output of scconf ...........................................................................................................................47

10. References..........................................................................................................................................4711. For More Information........................................................................................................................48


1. Installing and Configuring an Asymmetric Cluster To configure a two-node, high availability, asymmetric cluster for Sun Java System Messaging Server 6.3, you perform the following steps:

● Install the Sun Cluster 3.1software.

● Prepare both nodes of the cluster.

● Install Sun Java System Messaging Server 6.3 binaries on both cluster nodes.

● Install the Sun Java System Messaging Server HA agent package (SUNWscims) on both cluster nodes.

● Configure the cluster.

● Configure Sun Java System Messaging Server 6.3 on the primary node.

● Configure Sun Java System Messaging Server 6.3 on the secondary node.

● Run the HA configuration program (ha_ip_config).

● Create the Sun Java System Messaging Server HA resource.

● Verify that everything is working.

1.0 Install Sun Cluster 3.1 Software

Install Sun Cluster software using the Java Enterprise System Installer on both nodes. For example, in this document, the two nodes are named nemo.example.com and dory.example.com. After the installation is complete, you must configure the two-node cluster. For the example installation in this document, the cluster name is messagingcluster.

Section 3 of this document contains instructions on installing and configuring Sun Cluster 3.1 software.


1.1 Prepare Both Nodes of the Cluster

1.1.1 Edit the /etc/hosts File

For example, the two nodes in the cluster have the physical host names nemo.example.com and dory.example.com. The two-node clusterhas the logical host name crush. The logical host name crush is assigned a logical IP address. For example, the /etc/hosts file looks like the following:

Output from cat /etc/hosts on primary node nemo.example.com looks like this:

127.0.0.1 localhost100.10.100.221 nemo.example.com nemo loghost100.10.100.222 dory.example.com dory # Cluster Node

100.10.100.223 crush.example.com crush << This is a logical IP address associated with the logical host name crush.example.com >>

Output from cat /etc/hosts on secondary node dory.example.com looks like this:

127.0.0.1 localhost100.10.100.221 dory.example.com dory loghost100.10.100.222 nemo.example.com nemo # Cluster Node

100.10.100.223 crush.example.com crush << This is a logical IP address associated with the logical host name crush.example.com >>

1.1.2 Create the Mount Points

Create the required file systems. For information on how to create the file systems, see Section 6 of this document.

After the file systems have been created on the shared storage (/SharedDisk), create the required mount points on both the primary and the secondary nodes. For example, on each node, perform the following command:

# mkdir -p /SharedDisk

After you are done creating the file systems, verify that your /etc/vfstab file looks like one of the following.


If your mount point is a cluster file system (CFS):

As shown below in bold, the /dev/md/polarbear/dsk/d2000 line should be identical on both nodes of the two-node cluster. That is, /etc/vfstab should have this line on both nemo.example.com and dory.example.com.

# cat /etc/vfstab#device device mount FS fsck mount mount#to mount to fsck point type pass at boot options#/dev/md/polarbear/dsk/d2000 /dev/md/polarbear/rdsk/d2000 /SharedDisk ufs 2 yes global,logging

If your mount point is a failover file system (FFS):

As shown below in bold, the /dev/md/polarbear/dsk/d2000 line should be identical on both nodes of the two-node cluster. That is, /etc/vfstab should have this line on both nemo.example.com and dory.example.com.

# cat /etc/vfstab#device device mount FS fsck mount mount#to mount to fsck point type pass at boot options#/dev/md/polarbear/dsk/d2000 /dev/md/polarbear/rdsk/d2000 /SharedDisk ufs 2 no logging

On the primary node, nemo.example.com, mount the shared disk on /SharedDisk:

# mount /SharedDisk

1.1.3 Create the Messaging Server User

Create the Messaging Server user, and then add the user to the group. For the examples that follow, the user is named mailsrv and the group is named mail. The mailsrv user must exist on all nodes of the cluster, and each instance of mailsrv must use the same UID. In this example, the /etc/passwd entry for mailsrv shows the UID 207038, which should be identical on all nodes of the cluster.


# cat /etc/passwdmailsrv:x:207038:6::/export/mailsrv:/bin/sh

1.2 Install the Sun Java System Messaging Server 6.3 Binaries on Both Cluster Nodes

Install the Sun Java System Messaging Server 6.3 binaries on both nodes, nemo.example.com and dory.example.com. In the examplesthat follow, the default Messaging Server root, /opt/SUNWmsgsr, was chosen for the installation.

During the installation process, choose to configure later.

For more information on installing Sun Java System Messaging Server 6.3, see Section 4 of this document.

1.3 Install the Messaging HA Agent Package (SUNWscims) on Both Cluster Nodes

Using the Java Enterprise System (Java ES) installer, install the Messaging HA agent package (SUNWscims) on both nodes of the cluster.

1.4 Configure the Cluster

To configure the cluster, perform the steps described in this section. All of the following commands assume that the PATH environment variable is set to /usr/cluster/bin on both nodes of the cluster.

1.4.1 Register the Resource Type Registration Files and Verify the Registration

On the primary node, add the two required Resource Type Registration (RTR) files, SUNW.ims and SUNW.HAStoragePlus. This configures the cluster and makes it aware of the resource types that will be used. Unless


otherwise stated, run the following commands on the primary node (nemo.example.com).

To register the Messaging Server RTR file, SUNW.ims, use the following command:

# scrgadm -a -t SUNW.ims

Verify that this RTR file has been successfully registered:

# scrgadm -pv -t SUNW.ims

Res Type name: SUNW.ims (SUNW.ims) Res Type description: HA iPlanet Mail Server Resource Type (SUNW.ims) Res Type base directory: /opt/SUNWscims/bin (SUNW.ims) Res Type single instance: False (SUNW.ims) Res Type init nodes: All potential masters (SUNW.ims) Res Type failover: True (SUNW.ims) Res Type proxy: False (SUNW.ims) Res Type version: 1.0 (SUNW.ims) Res Type API version: 2 (SUNW.ims) Res Type installed on nodes: <All> (SUNW.ims) Res Type packages: SUNWscims (SUNW.ims) Res Type system: False

To register the HAStoragePlus RTR file, SUNW.HAStoragePlus, use the following command:

# scrgadm -a -t SUNW.HAStoragePlus

Verify that this RTR file has been successfully registered:

# scrgadm -pv -t SUNW.HAStoragePlus

Res Type name: SUNW.HAStoragePlus:4 (SUNW.HAStoragePlus:4) Res Type description: HA Storage Plus (SUNW.HAStoragePlus:4) Res Type base directory: usr/cluster/lib/rgm/rt/hastorageplus (SUNW.HAStoragePlus:4) Res Type single instance: False (SUNW.HAStoragePlus:4) Res Type init nodes: All potential masters (SUNW.HAStoragePlus:4) Res Type failover: False (SUNW.HAStoragePlus:4) Res Type proxy: False (SUNW.HAStoragePlus:4) Res Type version: 4 (SUNW.HAStoragePlus:4) Res Type API version: 2 (SUNW.HAStoragePlus:4) Res Type installed on nodes: <All> (SUNW.HAStoragePlus:4) Res Type packages: SUNWscu (SUNW.HAStoragePlus:4) Res Type system: False


1.4.2 Create a Failover Resource Group for This Instance of the Software

Create a failover resource group called MAIL-RG with nemo.example.com as the primary node and dory.example.com as the failover (secondary) node.

# scrgadm -a -g MAIL-RG -h nemo,dory

1.4.3 Create a Logical Host Name Resource

Create a logical host name resource called crush, and add this to the resource group MAIL-RG. After creating the failover resource group, bring it online on the primary node.

# scrgadm -a -L -g MAIL-RG -l crush# scrgadm -c -j crush -y R_description="LogicalHostname resource for crush"# scswitch -Z -g MAIL-RG

Verify that the logical host name has been added to the resource group:

# scrgadm -pv -j crush

(messaging-rg) Res name: crush(messaging-rg:crush) Res R_description: LogicalHostname resource for crush(messaging-rg:crush) Res resource type: SUNW.LogicalHostname:2(messaging-rg:crush) Res type version: 2(messaging-rg:crush) Res resource group name: MAIL-RG(messaging-rg:crush) Res resource project name: default(messaging-rg:crush{nemo}) Res enabled: True(messaging-rg:crush{dory}) Res enabled: True(messaging-rg:crush{nemo}) Res monitor enabled: True(messaging-rg:crush{dory}) Res monitor enabled: True

1.4.4 Create an HAStoragePlus Resource

Create an HAStoragePlus resource called messaging-hasp-resource. This resource will manage the mount point /SharedDisk. In the examples, both the CFS and the FFS are used.


# scrgadm -a -j messaging-hasp-resource -g MAIL-RG -t SUNW.HAStoragePlus -x FileSystemMountPoints ="/SharedDisk" -x AffinityOn=TRUE

1.4.5 Enable the HAStoragePlus Resource

Enable the HAStoragePlus resource created in the previous step.

# scswitch -e -j messaging-hasp-resource

1.4.6 Test the Creation of the Resource Group

Perform a failover to the secondary node and run the df and ping commands to test the following things:

● The mount point, /SharedDisk, is accessible by both nodes.

● The logical host name is online.

● The resource group MAIL-RG is functioning.

Perform a failover to the secondary node by issuing the following command:

# scswitch -z -g MAIL-RG -h dory

Make sure the mount point is accessible by running the following command:

# df -kh#/dev/md/polarbear/dsk/d2000 33G 101M 33G 1% /SharedDisk

Run ping on dory.example.com:

# ping crush.example.com

crush.example.com is alive


You can repeat the same exercise by failing back and forth between the two nodes and repeating the same experiment of running the df and ping commands to make sure that the logical host name (crush.example.com) and the mount point (/SharedDisk) are accessible from both the nodes.

1.5 Configure Sun Java System Messaging Server 6.3 on the Primary Node

Fail over so that you are back on the primary node, nemo.example.com.

While on the primary node, run the Messaging Server configuration program.

During the configuration, you are prompted for the fully qualified host name. Enter the fully qualified logical host name (crush.example.com, in the example).

When the program prompts you to "Select directory to store configuration and data files," specify the mount point (/SharedDisk, in the example).

Section 5 of this document contains sample screen shots of the configuration program.

1.6 Configure Sun Java System Messaging Server 6.3 on the Secondary Node

After you have finished configuring the primary node, fail over to the secondary node (dory). It is not necessary to run the Messaging Server configuration program again. However, to ensure that you perform the exact same configuration on the secondary node, run the useconfig utility, located under the /opt/SUNWmsgsr/sbin directory.


Run the useconfig program on the secondary node (dory).

# cd /opt/SUNWmsgsr/sbin# useconfig /SharedDisk/setup/configure_20071201124116

cp /SharedDisk/setup/configure_20071201124116/Devsetup.properties/opt/SUNWmsgsr/lib/config-templates/Devsetup.properties/usr/sbin/groupadd mail/usr/sbin/useradd -g mail -d / mailsrv


/usr/sbin/usermod -G mail mailsrvsed -e "s/local.serveruid/mailsrv/" -e "s/local.serveruid/mail/" -e "s:<msg·RootPath>:/opt/SUNWmsgsr:" /opt/SUNWmsgsr/lib/config-templates/devtypes.txt.template > /opt/SUNWmsgsr/lib/config-templates/devtypes.txtsed -e "s/local.serveruid/mailsrv/" -e "s/local.serveruid/mail/" -e "s:<msg·RootPath>:/opt/SUNWmsgsr:" /opt//SUNWmsgsr/lib/config-templates/config.ins.template > /opt/SUNWmsgsr/lib/config-templates/config.ins/opt/SUNWmsgsr/lib/devinstall -l sepadmsvr:pkgcfg:config -v -m -i /opt/SUNWmsgsr/lib/config-templates/config.ins /opt/SUNWmsgsr/lib/config-templates /opt/SUNWmsgsr/lib/jars /opt/SUNWmsgsr/libdevinstall returned 0crle -c /var/ld/ld.config -s/usr/lib/secure:/opt/SUNWmsgsr/lib:/opt/SUNWmsgsr/lib:/opt/SUNWmsgsr/lib -s /opt/SUNWmsgsr/lib

See /opt/SUNWmsgsr/install/useconfiglog_20071211155037 for more details.

1.7 Run the HA Configuration Program (ha_ip_config)

Use the Messaging Server ha_ip_config command to modify the Messaging Server configuration file. This command sets parameters in the file, such as local.autorestart andservice.listenaddr.

1.7.1 Run ha_ip_config on the Primary Node (nemo.example.com)

# /opt/SUNWmsgsr/sbin/ha_ip_config

Please specify the IP address assigned to the HA logical host name. Use dotted decimal form, a.b.c.d

Logical IP address: 100.10.100.223 << This is the IP address of our logical host name >>

Please specify the path to the top level directory in which iMS is installed.

iMS server root: /opt/SUNWmsgsr << This is where the Messaging Server is installed >>

The iMS server root directory does not contain any slapd-* subdirectories. Skipping configuration of LDAP servers.

Logical IP address: 100.10.100.223 iMS server root: /opt/nemo/SUNWmsgsr

Do you wish to change any of the above choices (yes/no) [no]?

Updating the file /opt/nemo/SUNWmsgsr/config/dispatcher.cnf Updating the file /opt/nemo/SUNWmsgsr/config/job_controller.cnf Setting the service.listenaddr configutil parameter Setting the local.snmp.listenaddr configutil parameter Setting the service.http.smtphost configutil parameter Setting the local.watcher.enable configutil parameter Setting the local.autorestart configutil parameter Setting the metermaid.config.bindaddr configutil parameters Setting the metermaid.config.serveraddr configutil parameters


Setting the local.ens.port parameter Configuration successfully updated

1.7.2 Fail Over to the Secondary Node

# scswitch -z -g MAIL-RG_dory -h nemo

1.7.3 Run ha_ip_config on the Secondary Node (dory.example.com)

# /opt/SUNWmsgsr/sbin/ha_ip_config

Please specify the IP address assigned to the HA logical host name. Use dotted decimal form, a.b.c.d

Logical IP address: 100.10.100.223 << This is the IP address of our logical host name >>

Please specify the path to the top level directory in which iMS is installed.

iMS server root: /opt/dory/SUNWmsgsr << This is where the Messaging Server is installed >>

The iMS server root directory does not contain any slapd-* subdirectories. Skipping configuration of LDAP servers.

Logical IP address: 100.10.100.223iMS server root: /opt/SUNWmsgsr

Do you wish to change any of the above choices (yes/no) [no]?

Updating the file /opt/SUNWmsgsr/config/dispatcher.cnf Updating the file /opt/SUNWmsgsr/config/job_controller.cnf Setting the service.listenaddr configutil parameter Setting the local.snmp.listenaddr configutil parameter Setting the service.http.smtphost configutil parameter Setting the local.watcher.enable configutil parameter Setting the local.autorestart configutil parameter Setting the metermaid.config.bindaddr configutil parameters Setting the metermaid.config.servraddr configutil parameters Setting the local.ens.port parameter Configuration successfully updated

1.8 Create the Sun Java System Messaging Server HA Resource

Create the Messaging Server HA resource and specify its dependency on the HAStoragePlus resource and the logical host name.


In the example that follows, the resource is named messaging-ms-resource, and it has a dependency on the HAStoragePlus resource (messaging-hasp-resource) and the logical host name (crush). The Messaging Server is installed at /opt/SUNWmsgsr.

# scrgadm -a -j messaging-ms-resource -t SUNW.ims -g MAIL-RG -x IMS_serverroot=/opt/SUNWmsgsr -y Resource_dependencies=crush,messaging-hasp-resource

Enable the Messaging Server resource:

# scswitch -e -j messaging-ms-resource

1.9 Verify That Everything Is Working

Fail over the resource group (MAIL-RG). For example, fail over MAIL-RG from the primary node to the secondary node. Then try failing over from one node to the other multiple times, making sure the failover is successful each time.


Try connecting on the logical host name (crush) on the IMAP port (for example, 143).

# telnet crush 143Trying 100.10.100.223...Connected to crush.example.com.Escape character is '^]'.* OK [CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ NAMESPACE UIDPLUS CHILDREN BINARY UNSELECT SORT LANGUAGE XSENDER X-NETSCAPE XSERVERINFO X-SUN-SORT X-SUN-IMAP X-ANNOTATEMORE AUTH=PLAIN] dory.example.com IMAP4 service (Sun Java(tm) System Messaging Server (built Jun 2007))e logout* BYE LOGOUT receivede OK CompletedConnection to crush.example.com closed by foreign host.

Also try killing any of the Messaging Server processes, for example, pkill imapd. Do this multiple times. The Messaging Server should fail over from one node to the other.


2. Unconfiguring the Asymmetric Cluster

To unconfigure the cluster, you perform the following steps:

● Take the resource group offline.

● Disable the Messaging Server resource.

● Disable the logical host name resource.

● Disable HAStoragePlus resource

● Remove the Messaging Server resource.

● Remove the logical host name resource.

● Remove the HAStoragePlus resource.

● Remove the resource group.

● Unregister the resource types that are not in use.

2.1 Take the Resource Group Offline

# scswitch -F -g MAIL-RG

2.2 Disable the Messaging Server Resource

# scswitch -n -j messaging-ms-resource

2.3 Disable the Logical Host Name Resource

# scswitch -n -j crush

2.4 Disable HAStoragePlus Resource

# scswitch -n -j messaging-hasp-resource


2.5 Remove the Messaging Server Resource

# scrgadm -r -j messaging-ms-resource

2.6 Remove the Logical Host Name resource

# scrgadm -r -j crush

2.7 Remove the HAStoragePlus Resource

# scrgadm -r -j messaging-hasp-resource

2.8 Remove the Resource Group

# scrgadm -r -g MAIL-RG

2.9 Unregister the Resource Types That Are Not in Use

# scrgadm -r -t SUNW.HAStoragePlus

# scrgadm -r -t SUNW.ims

3. Installing Sun Cluster 3.1 SoftwareTo install the Sun Cluster 3.1 software, you perform the following steps:

● Install the SolarisTM 10 Operating System on both nodes of the cluster.

● Install Sun Cluster 3.1 software using the Java Enterprise System (Java ES) installer.

● Configure the Sun Cluster 3.1 software.


3.1 Install Solaris 10 Operating System on Both Nodes of the Cluster

Make sure your local file system layout (on both the cluster nodes) looks like the following before installing the Solaris 10 OS. While installing the Solaris OS, make sure you create a file system layout like the following. The following file system table shows the layout of the disk slices.

File System Allocation

Slice Contents Size Allocation

Description

0 / 30GB Remaining free space on the disk after allocating space to slices 1 through 7. Used for the Solaris OS, Sun Cluster software, data-services software, volume-manager software, Sun Management Center agent, Sun Cluster module agent packages, root file systems, and database and application software.

1 swap 2GB Remaining bytes for the Solaris OS. 512 Mbytes for Sun Cluster software.

2 overlap 33GB The entire disk.

3 /globaldevices 1024MB The Sun Cluster software later assigns this slice a different mount point and mounts the slice as a cluster file system.

7 volume manager 100MB Used by Solstice DiskSuiteTM or Solaris Volume Manager software for the state database replica, or used by VxVM for installation after you free the slice.


After installing the Solaris 10 OS, the partition table looks like the following example:

partition> pCurrent partition table (original):Total disk cylinders available: 24620 + 2 (reserved cylinders)

Part Tag Flag Cylinders Size Blocks 0 root wm 0 - 22365 30.81GB (22366/0/0) 64615374 1 swap wu 22366 - 23817 2.00GB (1452/0/0) 4194828 2 backup wm 0 - 24619 33.92GB (24620/0/0) 71127180 3 unassigned wm 23818 - 24543 1.00GB (726/0/0) 2097414 4 unassigned wm 0 0 (0/0/0) 0 5 unassigned wm 0 0 (0/0/0) 0 6 unassigned wm 0 0 (0/0/0) 0 7 unassigned wm 24544 - 24614 100.16MB (71/0/0) 205119

3.2 Install Sun Cluster 3.1 Software Using the Java Enterprise System (Java ES) Installer

The following are example screen shots of the Java ES installer.

After you launch the installation wizard and accept the licence agreements, you are prompted for inputs by the System Install wizard.


Select the Sun Cluster 3.1 software from the installation wizard.


3.3 Configure the Sun Cluster 3.1 Software

After installing the Sun Cluster software, first register both nodes (dory.example.com and nemo.example.com) as the two nodes of the cluster. The name of the newly created cluster is messagingcluster.

Then, run the configuration program, scinstall, located under the /usr/cluster/bin directory. After the installation completes, reboot all the nodes in the cluster.

# pwd/usr/cluster/bin

# ls -rlt scinstall

-r-xr-xr-x 1 root bin 74027 Aug 20 2006 scinstall


Here is an excerpt from running ./scinstall. The cluster named messagingcluster has been created.

# ./scinstall

<< Excerpt from Sun Cluster software installation >>

Your responses indicate the following options to scinstall:

scinstall -i \ -C messagingcluster \ -F \ -T node=nemo,node=dory,authtype=sys \ -w netaddr=172.16.0.0,netmask=255.255.248.0,maxnodes=64,maxprivatenets=10 \ -A trtype=dlpi,name=qfe0 -A trtype=dlpi,name=qfe1 \ -B type=switch,name=switch1 -B type=switch,name=switch2 \ -m endpoint=:qfe0,endpoint=switch1 \ -m endpoint=:qfe1,endpoint=switch2 \ -P task=quorum,state=INIT

Are these the options you want to use (yes/no) [yes]? Are these the options you want to use (yes/no) [yes]? Do you want to continue with this configuration step (yes/no) [yes]?

Checking device to use for global devices file system ... done :::

<< Omitted lines. See the Section 9.1 for detailed output. >>

Initializing cluster name to "messagingcluster" ... done (/dev/did/rdsk/d2s2) added; votecount = 1, bitmask of nodes with configured paths = 0x3.Nov 17 16:32:15 dory cl_runtime: NOTICE: CMM: Cluster members: nemo dory.Nov 17 16:32:15 dory cl_runtime: NOTICE: CMM: node reconfiguration #6 completed.

4. Installing Sun Java System Messaging Server 6.3To install the Sun Java System Messaging Server 6.3, you perform the following steps:

● Select Sun Java System Messaging Server 6.3 in the installation wizard.

● Specify the installation directories.

● Choose the Configure Later option.

4.1 Select Sun Java System Messaging Server 6.3 in the Installation Wizard

Using the Sun Java Communications Suite 5 Installer, install Sun Java System Messaging Server 6.3.


Select Messaging Server 6.3 from the Choose Software Components screen. You must run the Directory Preparation tool after the installation is complete. For instructions on running the Directory Preparation Tool, see the Sun Java Communications Suite Installation Guide.

4.2 Specify the Installation Directories

At the Specify Installation Directories screen, choose the default Messaging Server installation root, /opt/SUNWmsgsr.


4.3 Choose the Configure Later Option

Select the Configure Later option. See Section 5 of this document for information on how to configure Sun Java System Messaging Server 6.3.


5. Configuring Sun Java System Messaging Server 6.3To configure the Sun Java System Messaging Server 6.3, you perform the following steps:

● Run the configuration wizard.

● Specify the fully qualified host name.

● Specify the directory in which to store the Messaging Server configuration.

● Specify the Messaging Server user.

● Verify that the configuration was successful.


5.1 Run the Configuration Wizard

Bring up the configuration wizard by running the Messaging Server configure program.

# cd /opt/SUNWmsgsr/sbin

# ./configure

The following screen shot shows the first screen of the Messaging Server configuration wizard. In the examples that follow, only the screens important to the high availability configuration are shown. The intervening screens are not shown. For those screens, fill in the appropriate information and continue until you reach the next screen shot shown in this example.

5.2 Specifying the Fully Qualified Host Name

Answer the appropriate questions and when prompted for the fully qualified host name, choose the logical host name (in our example, crush.example.com).


5.3 Specify the Directory in Which to Store the Messaging Server Configuration

When prompted for the directory in which to store configuration and data files, choose the directory mounted on the shared disk.


5.4 Specify the Messaging Server User

When asked for the Messaging Server user and group, enter mailsrv as the user name and mail as the group.


5.5 Verify That the Configuration Was Successful

When you choose the Configure Now option, verify that the configuration completed successfully.


6. Creating File Systems Using Solaris Volume ManagerTo create the file systems using Solaris Volume Manager, you perform the following steps:

● Create the diskset.

● Add mediator hosts.

● Add drives to the diskset.

● Create volumes.

● Modify the md.tab file on both nodes.

● Create UFS file systems.

6.1 Create the Diskset

Create a diskset using the steps in the sections that follow.


6.1.1 Create the State Database Replicas

Before you create the state database replicas, check to see if there are already existing disksets on both nodes. If not, create state database replicas on each node.

For example, to check if there are already existing disksets on both nodes, use the metadb command on each node.

# metadbmetadb: nemo: there are no existing databases

# metadbmetadb: dory: there are no existing databases

For example, create the state database replicas using the metadb -a -f -c command.

On Node 1 (nemo):

# metadb -a -f -c 3 c2t0d0s7

On Node 2 (dory):

# metadb -a -f -c 3 c2t0d0s7

6.1.2 Verify the State Database Replicas

Verify the state database replicas on each node using the metadb command.

On Node 1 (nemo):

# metadb flags first blk block count a u 16 8192 /dev/dsk/c2t0d0s7 a u 8208 8192 /dev/dsk/c2t0d0s7 a u 16400 8192 /dev/dsk/c2t0d0s7

On Node 2 (dory):

# metadb flags first blk block count a u 16 8192 /dev/dsk/c2t0d0s7 a u 8208 8192 /dev/dsk/c2t0d0s7 a u 16400 8192 /dev/dsk/c2t0d0s7


6.1.3 Create the Diskset

The following example shows creating a diskset named polarbear.

You can run this command on either node.

# metaset -s polarbearmetaset: nemo: setname "polarbear": no such set

Create the diskset:

# metaset -s polarbear -a -h nemo dory

Verify the creation of the diskset:

# metaset -s polarbearSet name = polarbear, Set number = 1

Host Ownernemo dory

To determine which disks are shared, use the command shown in the following example.

# scdidadm -L1 telstra:/dev/rdsk/c0t6d0 /dev/did/rdsk/d12 telstra:/dev/rdsk/c1t0d0 /dev/did/rdsk/d22 shaw:/dev/rdsk/c1t0d0 /dev/did/rdsk/d23 telstra:/dev/rdsk/c1t1d0 /dev/did/rdsk/d33 shaw:/dev/rdsk/c1t1d0 /dev/did/rdsk/d34 telstra:/dev/rdsk/c1t4d0 /dev/did/rdsk/d44 shaw:/dev/rdsk/c1t4d0 /dev/did/rdsk/d45 telstra:/dev/rdsk/c1t6d0 /dev/did/rdsk/d55 shaw:/dev/rdsk/c1t6d0 /dev/did/rdsk/d56 telstra:/dev/rdsk/c2t1d0 /dev/did/rdsk/d67 telstra:/dev/rdsk/c2t0d0 /dev/did/rdsk/d78 shaw:/dev/rdsk/c0t6d0 /dev/did/rdsk/d89 shaw:/dev/rdsk/c2t1d0 /dev/did/rdsk/d910 shaw:/dev/rdsk/c2t0d0 /dev/did/rdsk/d10

From the output above you can determine that the following disks are shared:

/dev/did/rdsk/d2/dev/did/rdsk/d3/dev/did/rdsk/d4/dev/did/rdsk/d5


6.2 Add Mediator Hosts

6.2.1 Take Ownership of the Diskset

From the primary node, nemo, take ownership of the diskset.

# metaset -s polarbear -t

6.2.2 Add the Mediator Hosts

# metaset -s polarbear -a -m nemo dory

6.2.3 Verify That the Mediator Hosts Were Successfully Added

Run the medstat command to verify that the mediator hosts were successfully added to the polarbear diskset.

# medstat -s polarbear

Mediator Status Goldennemo Ok Nodory Ok No


6.3 Add Drives to the Diskset

Add drives to the polarbear diskset and verify that the drives were added.

# metaset -s polarbear -a /dev/did/rdsk/d2 /dev/did/rdsk/d3

# metaset -s polarbear

Set name = polarbear, Set number = 1

Host Ownernemo Yesdory

Driv Dbase

d2 Yes

d3 Yes

6.4 Create Volumes

6.4.1 Create Disk Stripes and Mirrors

Create disk stripes and mirrors, as shown in the following example.

# metainit -s polarbear d20 1 1 /dev/did/rdsk/d2s0polarbear/d20: Concat/Stripe is setup

# metainit -s polarbear d30 1 1 /dev/did/rdsk/d3s0polarbear/d30: Concat/Stripe is setup

# metainit -s polarbear d200 -m d20polarbear/d200: Mirror is setup

# metainit -s polarbear d300 -m d30polarbear/d300: Mirror is setup

6.4.2 Verify the Creation of Disk Stripes and Mirrors

Verify that the disk stripes and mirrors have been successfully created, as shown in the following example.

# metastat -s polarbear -p

polarbear/d300 -m polarbear/d30 1


polarbear/d30 1 1 /dev/did/rdsk/d3s0polarbear/d200 -m polarbear/d20 1polarbear/d20 1 1 /dev/did/rdsk/d2s0

6.4.3 Create a Soft Partition

Create a volume in the shared diskset with soft partitions, as shown in the example that follows.

# metainit -s polarbear d2000 -p d200 10gd2000: Soft Partition is setup

# metainit -s polarbear d3000 -p d300 10gd3000: Soft Partition is setup

6.5 Modify the md.tab File on Both Nodes

6.5.1 Modify md.tab on the Primary Node

On node nemo, run the following command to modify the /etc/lvm/md.tab file.

cd /etc/lvmcp md.tab md.tab.backmetastat -s polarbear -p >> /etc/lvm/md.tab

This causes the md.tab file to look like this on primary node nemo.example.com:

cat /etc/lvm/md.tab on nemo## Hot Spare Pool of devices## hsp001 /dev/dsk/c1t0d0s0# blue/hsp001 /dev/dsk/c2t0d0s0## 100MB Soft Partition## d1 -p /dev/dsk/c1t0d0s1 100M# blue/d1 -p /dev/dsk/c2t0d0s1 100Mpolarbear/d300 -m polarbear/d30 1polarbear/d30 1 1 /dev/did/rdsk/d3s0polarbear/d200 -m polarbear/d20 1polarbear/d20 1 1 /dev/did/rdsk/d2s0polarbear/d2000 -p /dev/md/orion/rdsk/d200 -o 209715264 -b 209715200polarbear/d3000 -p /dev/md/orion/rdsk/d300 -o 32 -b 209715200


6.5.2 Modify md.tab on the Secondary Node

Edit the /etc/lvm/md.tab file on secondary node dory.example.com, and copy the same entries from md.tab on node nemo.example.com.

vi /etc/lvm/md.tab

cat /etc/lvm/md.tab on dory

## Hot Spare Pool of devices## hsp001 /dev/dsk/c1t0d0s0# blue/hsp001 /dev/dsk/c2t0d0s0## 100MB Soft Partition## d1 -p /dev/dsk/c1t0d0s1 100M# blue/d1 -p /dev/dsk/c2t0d0s1 100Mpolarbear/d300 -m polarbear/d30 1polarbear/d30 1 1 /dev/did/rdsk/d3s0polarbear/d200 -m polarbear/d20 1polarbear/d20 1 1 /dev/did/rdsk/d2s0polarbear/d2000 -p /dev/md/orion/rdsk/d200 -o 209715264 -b 209715200polarbear/d3000 -p /dev/md/orion/rdsk/d300 -o 32 -b 209715200

6.6 Create UFS File Systems

6.6.1 Create the New UFS File Systems on the Raw Disks

Create the new UFS file systems on the raw disks using the newfs command.

# newfs /dev/md/polarbear/rdsk/d3000newfs: construct a new file system /dev/md/polarbear/rdsk/d3000: (y/n)? yWarning: 4432 sector(s) in last cylinder unallocated/dev/md/polarbear/rdsk/d3000: 71118512 sectors in 11576 cylinders of 48 tracks, 128 sectors 34725.8MB in 724 cyl groups (16 c/g, 48.00MB/g, 5824 i/g)super-block backups (for fsck -F ufs -o b=#) at: 32, 98464, 196896, 295328, 393760, 492192, 590624, 689056, 787488, 885920,Initializing cylinder groups:..............super-block backups for last 10 cylinder groups at: 70190368, 70288800, 70387232, 70485664, 70584096, 70682528, 70780960, 70879392, 70977824, 71076256

# newfs /dev/md/polarbear/rdsk/d2000newfs: construct a new file system /dev/md/polarbear/rdsk/d2000: (y/n)? yWarning: 4432 sector(s) in last cylinder unallocated/dev/md/polarbear/rdsk/d2000: 71118512 sectors in 11576 cylinders of 48 tracks, 128 sectors 34725.8MB in 724 cyl groups (16 c/g, 48.00MB/g, 5824 i/g)super-block backups (for fsck -F ufs -o b=#) at:


32, 98464, 196896, 295328, 393760, 492192, 590624, 689056, 787488, 885920,Initializing cylinder groups:..............super-block backups for last 10 cylinder groups at: 70190368, 70288800, 70387232, 70485664, 70584096, 70682528, 70780960, 70879392, 70977824, 71076256

6.6.2 Verify the Creation of the File System

Check both disks to verify that the file systems were successfully created.

# fstyp /dev/md/polarbear/dsk/d2000 ufs

# fstyp /dev/md/polarbear/dsk/d3000 ufs

7. Useful Sun Cluster Administration CommandsThis section contains information on commands you can use to do the following:

● Determine the cluster status.

● Bring the resource group online.

● Verify that the resource group is online.

● Display the status of the quorum device.

● Display the status of the cluster nodes.

● Display the configuration of the cluster.

● Check the validity of the /etc/vfstab file.

7.1 Determine the Cluster Status

# scstat -pvv

Detailed output of this command is displayed in Section 9.2 of this document.


7.2 Bring the Resource Group Online

# scswitch -Z -g MAIL-RG

7.3 Verify That the Resource Group Is Online

# scstat -g


7.4 Display the Status of the Quorum Device

# scstat -q


7.5 Display the Status of the Cluster Nodes

# scstat -n

-- Cluster Nodes --

Node name Status ----------- ----- ------

Cluster node: nemo Online Cluster node: dory Online

7.6 Display the Configuration of the Cluster

# ./scconf -p | grep -i cluster



7.7 Check the Validity of the /etc/vfstab File

The configuration check utility verifies that the mount points exist. If there are no errors, nothing is returned. This utility verifies that the /etc/vfstab file entries are correct on both nodes of the cluster.

# sccheck

8. Enabling Cluster DebuggingTo enable cluster debugging, you perform the following steps:

● Log messages from the Messaging Server agents.

● Edit the syslog.conf file.

8.1 Log Messages From the Messaging Server Agents

mkdir -p /var/cluster/rgm/rt/SUNW.imsecho 9 > /var/cluster/rgm/rt/SUNW.ims/loglevel

8.2 Edit the syslog.conf File

Add the following line to syslog.conf. This will log all the debug messages tothe file /var/adm/sunclusterlog.

daemon.debug /var/adm/sunclusterlog

Then, restart the syslogd daemon.

# pkill -HUP syslogd

9. Example Output From CommandsThis section provides the output from commands used in previous sections.


9.1 Output of scinstall

Initializing authentication options ... doneInitializing configuration for adapter "qfe0" ... doneInitializing configuration for adapter "qfe1" ... doneInitializing configuration for switch "switch1" ... doneInitializing configuration for switch "switch2" ... doneInitializing configuration for cable ... doneInitializing configuration for cable ... doneInitializing private network address options ... done

Setting the node ID for "nemo" ... done (id=1)

Checking for global devices global file system ... doneUpdating vfstab ... done

Verifying that NTP is configured ... doneInitializing NTP configuration ... done

Updating nsswitch.conf ... done

Adding cluster node entries to /etc/inet/hosts ... done

Configuring IP multipathing groups ...done

Verifying that power management is NOT configured ... doneUnconfiguring power management ... done/etc/power.conf has been renamed to /etc/power.conf.111706161631Power management is incompatible with the HA goals of the cluster.Please do not attempt to re-configure power management.

Ensure that the EEPROM parameter "local-mac-address?" is set to "true" ... done

Ensure network routing is disabled ... doneNetwork routing has been disabled on this node by creating /etc/notrouter.Having a cluster node act as a router is not supported by Sun Cluster.Please do not re-enable network routing.

Log file - /var/cluster/logs/install/scinstall.log.12414

Rebooting ...

Connection to nemo closed.Nov 17 15:47:44 nemo last message repeated 2 timesNov 17 16:16:32 nemo reboot: rebooted by softwareRunnerNov 17 16:16:32 nemo syslogd: going down on signal 15syncing file systems... donerebooting...Resetting ...

screen not found.keyboard not found.Keyboard not present. Using ttya for input and output.

Sun Fire 280R (2 X UltraSPARC-III+) , No KeyboardCopyright 1998-2002 Sun Microsystems, Inc. All rights reserved.OpenBoot 4.5, 2048 MB memory installed, Serial #53447534.Ethernet address 0:3:ba:2f:8b:6e, Host ID: 832f8b6e.

Rebooting with command: bootBoot device: /pci@8,600000/SUNW,qlc@4/fp@0,0/disk@w21000004cfcb2a60,0:a File and args:SunOS Release 5.10 Version Generic_118833-31 64-bit


Copyright 1983-2007 Sun Microsystems, Inc. All rights reserved.Use is subject to license terms.Configuring devices.Hostname: nemoSUNW,eri0 : 100 Mbps full duplex link upNIS domain name is example.comLoading smf(5) service descriptions: 41/41scdidadm: Could not load DID instance list.scdidadm: Cannot open /etc/cluster/ccr/did_instances.Booting as part of a clusterNOTICE: CMM: Node nemo (nodeid = 1) with votecount = 1 added.NOTICE: CMM: Node nemo: attempting to join cluster.NOTICE: CMM: Cluster has reached quorum.NOTICE: CMM: Node nemo (nodeid = 1) is up; new incarnation number = 1163809224.NOTICE: CMM: Cluster members: nemo.NOTICE: CMM: node reconfiguration #1 completed.NOTICE: CMM: Node nemo: joined cluster.ip: joining multicasts failed (18) on clprivnet0 - will use link layer broadcasts for multicast

did instance 1 created.did subpath nemo:/dev/rdsk/c0t6d0 created for instance 1.did instance 2 created.did subpath nemo:/dev/rdsk/c1t0d0 created for instance 2.did instance 3 created.did subpath nemo:/dev/rdsk/c1t1d0 created for instance 3.did instance 4 created.did subpath nemo:/dev/rdsk/c1t4d0 created for instance 4.did instance 5 created.did subpath nemo:/dev/rdsk/c1t6d0 created for instance 5.did instance 6 created.did subpath nemo:/dev/rdsk/c2t1d0 created for instance 6.did instance 7 created.did subpath nemo:/dev/rdsk/c2t0d0 created for instance 7.Configuring DID devicesobtaining access to all attached disks

nemo console login: Configuring the /dev/global directory (global devices)

nemo console login: Nov 17 16:21:56 nemo svc.startd[8]: system/cluster/scsymon-srv:default misconfigured: transitioned to maintenance (see 'svcs -xv' for details)

nemo console login:nemo console login: Nov 17 16:22:07 nemo java[1726]: pkcs11_softtoken: Keystore version failure.

>>> 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.

Do you want to use autodiscovery (yes/no) [yes]?

Probing .......

The following connections were discovered:

nemo:qfe0 switch1 dory:qfe0 nemo:qfe1 switch2 dory:qfe1

Is it okay to add these connections to the configuration (yes/no) [yes]?

>>> Confirmation <<<

Your responses indicate the following options to scinstall:


scinstall -i \ -C messagingcluster \ -N nemo \ -A trtype=dlpi,name=qfe0 -A trtype=dlpi,name=qfe1 \ -m endpoint=:qfe0,endpoint=switch1 \ -m endpoint=:qfe1,endpoint=switch2

Checking device to use for global devices file system ... done

Adding node "dory" to the cluster configuration ... doneAdding adapter "qfe0" to the cluster configuration ... doneAdding adapter "qfe1" to the cluster configuration ... doneAdding cable to the cluster configuration ... doneAdding cable to the cluster configuration ... done

Copying the config from "nemo" ... done

Copying the postconfig file from "nemo" if it exists ... donedone

Setting the node ID for "dory" ... done (id=2)

Verifying the major number for the "did" driver with "nemo" ... done

Checking for global devices global file system ... doneUpdating vfstab ... done

Verifying that NTP is configured ... doneInitializing NTP configuration ... done

Updating nsswitch.conf ... done

Adding cluster node entries to /etc/inet/hosts ... done

Configuring IP multipathing groups ...done

Verifying that power management is NOT configured ... doneUnconfiguring power management ... done/etc/power.conf has been renamed to /etc/power.conf.111706162651Power management is incompatible with the HA goals of the cluster.Please do not attempt to re-configure power management.

Ensure that the EEPROM parameter "local-mac-address?" is set to "true" ... done

Ensure network routing is disabled ... doneNetwork routing has been disabled on this node by creating /etc/notrouter.Having a cluster node act as a router is not supported by Sun Cluster.Please do not re-enable network routing.

Updating file ("ntp.conf.cluster") on node nemo ... doneUpdating file ("hosts") on node nemo ... done

Log file - /var/cluster/logs/install/scinstall.log.12641

Rebooting ...Rebooting with command: bootBoot device: /pci@8,600000/SUNW,qlc@4/fp@0,0/disk@w21000004cfe49765,0:a File and args:SunOS Release 5.10 Version Generic_118833-31 64-bitCopyright 1983-2007 Sun Microsystems, Inc. All rights reserved.Use is subject to license terms.Configuring devices.Hostname: dorySUNW,eri0 : 100 Mbps full duplex link upNIS domain name is example.comLoading smf(5) service descriptions: 39/4140/41


41/41scdidadm: Could not load DID instance list.scdidadm: Cannot open /etc/cluster/ccr/did_instances.Booting as part of a clusterNOTICE: CMM: Node nemo (nodeid = 1) with votecount = 1 added.NOTICE: CMM: Node dory (nodeid = 2) with votecount = 0 added.NOTICE: clcomm: Adapter qfe1 constructedNOTICE: clcomm: Adapter qfe0 constructedNOTICE: CMM: Node dory: attempting to join cluster.NOTICE: CMM: Node nemo (nodeid: 1, incarnation #: 1163809224) has become reachable.NOTICE: clcomm: Path dory:qfe1 - nemo:qfe1 onlineNOTICE: clcomm: Path dory:qfe0 - nemo:qfe0 onlineNOTICE: CMM: Cluster has reached quorum.NOTICE: CMM: Node nemo (nodeid = 1) is up; new incarnation number = 1163809224.NOTICE: CMM: Node dory (nodeid = 2) is up; new incarnation number = 1163809844.NOTICE: CMM: Cluster members: nemo dory.NOTICE: CMM: node reconfiguration #3 completed.NOTICE: CMM: Node dory: joined cluster.ip: joining multicasts failed (18) on clprivnet0 - will use link layer broadcasts for multicastDID subpath "/dev/rdsk/c1t0d0s2" created for instance "2".DID subpath "/dev/rdsk/c1t1d0s2" created for instance "3".DID subpath "/dev/rdsk/c1t4d0s2" created for instance "4".DID subpath "/dev/rdsk/c1t6d0s2" created for instance "5".did instance 8 created.did subpath dory:/dev/rdsk/c0t6d0 created for instance 8.did instance 9 created.did subpath dory:/dev/rdsk/c2t1d0 created for instance 9.did instance 10 created.did subpath dory:/dev/rdsk/c2t0d0 created for instance 10.Configuring DID devicesobtaining access to all attached disks

dory console login: Configuring the /dev/global directory (global devices)Nov 17 16:32:13 dory cl_runtime: NOTICE: CMM: Cluster members: nemo dory.Nov 17 16:32:13 dory cl_runtime: NOTICE: CMM: node reconfiguration #4 completed.Nov 17 16:32:14 dory cl_runtime: NOTICE: CMM: Votecount changed from 0 to 1 for node dory.Nov 17 16:32:14 dory cl_runtime: NOTICE: CMM: Cluster members: nemo dory.Nov 17 16:32:14 dory cl_runtime: NOTICE: CMM: node reconfiguration #5 completed.Nov 17 16:32:15 dory cl_runtime: NOTICE: CMM: Quorum device 1

9.2 Output of scstat

-- Cluster Nodes --

Node name Status --------- ------ Cluster node: nemo Online Cluster node: dory Online

------------------------------------------------------------------

-- Cluster Transport Paths --

Endpoint Endpoint Status -------- -------- ------

Transport path: nemo:qfe1 dory:qfe1 Path online Transport path: nemo:qfe0 dory:qfe0 Path online

------------------------------------------------------------------


-- Quorum Summary --

Quorum votes possible: 3 Quorum votes needed: 2 Quorum votes present: 3

-- Quorum Votes by Node --

Node Name Present Possible Status --------- ------- -------- ------ Node votes: nemo 1 1 Online Node votes: dory 1 1 Online

-- Quorum Votes by Device --

Device Name Present Possible Status ----------- ------- -------- ------ Device votes: /dev/did/rdsk/d2s2 1 1 Online

------------------------------------------------------------------

-- Device Group Servers --

Device Group Primary Secondary ------------ ------- --------- Device group servers: dsk/d1 - - Device group servers: dsk/d2 - - Device group servers: dsk/d3 - - Device group servers: dsk/d4 - - Device group servers: dsk/d5 - - Device group servers: dsk/d6 - - Device group servers: dsk/d7 - - Device group servers: dsk/d8 - - Device group servers: dsk/d9 - - Device group servers: dsk/d10 - - Device group servers: polarbear dory nemo

-- Device Group Spares --

Device Group Spare Nodes ------------ ----------- Device group spares: dsk/d1 - Device group spares: dsk/d2 - Device group spares: dsk/d3 - Device group spares: dsk/d4 - Device group spares: dsk/d5 - Device group spares: dsk/d6 - Device group spares: dsk/d7 - Device group spares: dsk/d8 - Device group spares: dsk/d9 - Device group spares: dsk/d10 - Device group spares: polarbear -

-- Device Group Inactives --

Device Group Inactive Nodes ------------ -------------- Device group inactives: dsk/d1 - Device group inactives: dsk/d2 - Device group inactives: dsk/d3 - Device group inactives: dsk/d4 - Device group inactives: dsk/d5 -


Device group inactives: dsk/d6 - Device group inactives: dsk/d7 - Device group inactives: dsk/d8 - Device group inactives: dsk/d9 - Device group inactives: dsk/d10 - Device group inactives: polarbear -

-- Device Group Transitions --

Device Group In Transition Nodes ------------ ------------------- Device group transitions: dsk/d1 - Device group transitions: dsk/d2 - Device group transitions: dsk/d3 - Device group transitions: dsk/d4 - Device group transitions: dsk/d5 - Device group transitions: dsk/d6 - Device group transitions: dsk/d7 - Device group transitions: dsk/d8 - Device group transitions: dsk/d9 - Device group transitions: dsk/d10 - Device group transitions: polarbear -

-- Device Group Status --

Device Group Status ------------ ------ Device group status: dsk/d1 Offline Device group status: dsk/d2 Offline Device group status: dsk/d3 Offline Device group status: dsk/d4 Offline Device group status: dsk/d5 Offline Device group status: dsk/d6 Offline Device group status: dsk/d7 Offline Device group status: dsk/d8 Offline Device group status: dsk/d9 Offline Device group status: dsk/d10 Offline Device group status: polarbear Online

-- Multi-owner Device Groups --

Device Group Online Status ------------ -------------

------------------------------------------------------------------

-- Resource Groups and Resources --

Group Name Resources ---------- ---------

Resources: MS-RG crush messaging-hasp-resource messaging-ms-resource

-- Resource Groups --

Group Name Node Name State ---------- --------- ----- Group: MS-RG nemo Offline Group: MS-RG dory Online

-- Resources --

Resource Name Node Name State Status Message


------------- --------- ----- --------------Resource: crush nemo Offline Offline - LogicalHostname offline.Resource: crush dory Online Online - LogicalHostname online.

Resource: messaging-hasp-resource nemo Offline OfflineResource: messaging-hasp-resource dory Online Online

Resource: messaging-ms-resource nemo Offline Offline - Stop SucceededResource: messaging-ms-resource dory Online Online - Start succeeded.

------------------------------------------------------------------

-- IPMP Groups --

Node Name Group Status Adapter Status --------- ----- ------ ------- ------ IPMP Group: nemo sc_ipmp0 Online eri0 Online

IPMP Group: dory sc_ipmp0 Online eri0 Online

------------------------------------------------------------------

9.3 Output of scstat -g

-- Resource Groups and Resources --

Group Name Resources ---------- --------- Resources: MS-RG crush messaging-hasp-resource messaging-ms-resource

-- Resource Groups --

Group Name Node Name State ---------- --------- ----- Group: MS-RG dory Offline Group: MS-RG nemo Online

-- Resources --

Resource Name Node Name State Status Message ------------- --------- ----- -------------- Resource: crush dory Offline Offline - LogicalHostname offline. Resource: crush nemo Online Online - LogicalHostname online.

Resource: messaging-hasp-resource dory Offline Offline Resource: messaging-hasp-resource nemo Online Online

Resource: messaging-ms-resource dory Offline Offline - Stop Succeeded Resource: messaging-ms-resource nemo Online Online - Start succeeded.


9.4 Output of scstat -q

-- Quorum Summary --

Quorum votes possible: 3 Quorum votes needed: 2 Quorum votes present: 3

-- Quorum Votes by Node --

Node Name Present Possible Status --------- ------- ------- -------- ----- Node votes: nemo 1 1 Online Node votes: dory 1 1 Online

-- Quorum Votes by Device --

Device Name Present Possible Status ----------- ------- -------- ------ ------

Device votes: /dev/did/rdsk/d2s2 1 1 Online

9.5 Output of scconf

Cluster name: messagingclusterCluster ID: 0x46153CB8Cluster install mode: disabledCluster private net: 172.16.0.0Cluster private netmask: 255.255.0.0Cluster new node authentication: unixCluster new node list: <. - Exclude all nodes>Cluster transport heart beat timeout: 10000Cluster transport heart beat quantum: 1000Cluster nodes: nemo doryCluster node name: nemoNode private hostname: clusternode1-privCluster node name: doryNode private hostname: clusternode2-privCluster transport junctions: switch1 switch2Cluster transport junction: switch1Cluster transport junction: switch2Cluster transport cables

10. References● Sun Java System Messaging Server 6.3 Administration Guide:

http://docs.sun.com/app/docs/doc/819-4428

● Sun Java Communications Suite 5 Installation Guide:http://docs.sun.com/app/docs/doc/819-7560

● Sun Cluster Software Installation Guide for Solaris OS:http://docs.sun.com/app/docs/doc/817-6543





● Sun Cluster 3.1 Software Installation Guide:http://docs.sun.com/app/docs/doc/816-3388

● Sun Cluster 3.1 System Administration Guide:http://docs.sun.com/app/docs/doc/816-3384

● Solaris Volume Manager Administration Guide:http://docs.sun.com/app/docs/doc/819-2789

11. For More Information

● BigAdmin Communications Suite Hub, with information about Sun Java Communications Suite 5:http://www.sun.com/bigadmin/hubs/comms

● Sun bloggers, such as Jim Parkinson and Jonathan Hawkins:http://www.sun.com/bigadmin/hubs/comms/community/weblogs.jsp

● Related Sun forums:

E-Mail, Calendar, & Collaboration - Sun Java System Messaging Server http://forum.java.sun.com/forum.jspa?forumID=708

Sun Cluster 3.2 Forum: http://forum.java.sun.com/thread.jspa?forumID=842&threadID=5177262

● Sun resources for training:

Sun Cluster training and certification: http://www.sun.com/training/

Sun Java System Communication Services Administration http://www.sun.com/training/catalog/courses/MSG-2379.xml

12. Licensing InformationUnless otherwise specified, the use of this software is authorized pursuant to the terms of the license found at http://www.sun.com/bigadmin/common/berkeley_license.html.


http://www.sun.com/bigadmin/common/berkeley_license.html

http://www.sun.com/training/catalog/courses/MSG-2379.xml

http://www.sun.com/training/

http://forum.java.sun.com/thread.jspa?forumID=842&threadID=5177262

http://forum.java.sun.com/forum.jspa?forumID=708

http://www.sun.com/bigadmin/hubs/comms/community/weblogs.jsp

http://www.sun.com/bigadmin/hubs/comms




Configuring Sun Java System Messaging Server 6.3 With Sun Cluster

Documents

Transcript of Configuring Sun Java System Messaging Server 6.3 With Sun Cluster