Sun Cluster 3.1 Installation

Filesystems (minimum required)

/                    65Mb free (/ =40Mb, /usr = 25Mb)
/var                 100Mb free (for log files after installation)
/opt                 5 Mb free
swap                 750mb   (minimum)
/globaldevices       512Mb (used by the cluster)

Note: remember to save a 100mb each for the veritas and/or ODS partitions

Installation

The below installation was carried out on two ultra30’s with 512Mb of ram in each. Each server had one 4 Gb hard disk running Solaris 8. Both servers were attached to a D1000 contain 5 x 9gb hard disks, also both servers had a quad ethernet card installed.

Before installing make sure that both servers can remote shell into each other without requesting for a password (update /.rhosts files)

# scinstall

*** Main Menu ***

Please select from one of the following (*) options:

  • 1) Install a cluster or cluster node

2) Configure a cluster to be JumpStarted from this install server
3) Add support for new data services to this cluster node

  • 4) Print release information for this cluster node
  • ?) Help with menu options
  • q) Quit

Option:   1
—————————————————————————
*** Install Menu ***

Please select from any one of the following options:

1) Install all nodes of a new cluster
2) Install just this machine as the first node of a new cluster
3) Add this machine as a node in an existing cluster

?) Help with menu options
q) Return to the Main Menu

Option:   1
——————————————————————————
*** Installing just the First Node of a New Cluster ***

This option is used to establish a new cluster using this machine as
the first node in that cluster.

Once the cluster framework software is installed, you will be asked
for the name of the cluster. Then, you will have the opportunity to
run sccheck(1M) to test this machine for basic Sun Cluster
pre-configuration requirements.

After sccheck(1M) passes, you will be asked for the names of the
other nodes which will initially be joining that cluster. In
addition, you will be asked to provide certain cluster transport
configuration information.

Press Control-d at any time to return to the Main Menu.

Do you want to continue (yes/no) [yes]?   yes
—————————————————————————————
>>> Software Package Installation <<<

Installation of the Sun Cluster framework software packages will take
a few minutes to complete.

Is it okay to continue (yes/no) [yes]?   yes
——————————————————————————————
** Installing SunCluster 3.1 framework **
SUNWscr…..done
SUNWscu…..done
SUNWscsck…done
SUNWscnm….done
SUNWscdev…done
SUNWscgds…done
SUNWscman…done
etc…………………………..
—————————————————————————
>>> Software Patch Installation <<<

If there are any Solaris or Sun Cluster patches that need to be added
as part of this Sun Cluster installation, scinstall can add them for
you. All patches that need to be added must first be downloaded into
a common patch directory. Patches can be downloaded into the patch
directory either as individual patches or as patches grouped together
into one or more tar, jar, or zip files.

If a patch list file is provided in the patch directory, only those
patches listed in the patch list file are installed. Otherwise, all
patches found in the directory will be installed. Refer to the
patchadd(1M) man page for more information regarding patch list files.

Do you want scinstall to install patches for you (yes/no) [yes]?   no
———————————————————————————
>>> Cluster Name <<<

Each cluster has a name assigned to it. The name can be made up of
any characters other than whitespace. Each cluster name should be
unique within the namespace of your enterprise.

What is the name of the cluster you want to establish?   prod
————————————————————————————-
>>> Check <<<

This step allows you to run sccheck(1M) to verify that certain basic
hardware and software pre-configuration requirements have been met.
If sccheck(1M) detects potential problems with configuring this
machine as a cluster node, a report of failed checks is prepared and
available for display on the screen. Data gathering and report
generation can take several minutes, depending on system
configuration.

Do you want to run sccheck (yes/no) [yes]?   yes
—————————————————————————————
>>> Cluster Nodes <<<

This Sun Cluster release supports a total of up to 16 nodes.

Please list the names of the other nodes planned for the initial
cluster configuration. List one node name per line. When finished,
type Control-D:

Node name:   sun1
Node name:   sun2
Node name (Control-D to finish):   ^D

This is the complete list of nodes:

sun1
sun2

Is it correct (yes/no) [yes]?   yes
————————————————————————————–
Attempting to contact “sun2” … done

Searching for a remote install method … done

The remote shell (see rsh(1)) will be used to install and configure
this cluster.

Press Enter to continue:
—————————————————————————————–

>>> Cluster Transport Adapters and Cables <<<

You must identify the two cluster transport adapters which attach
this node to the private cluster interconnect.

Select the first cluster transport adapter for “sun1”:

1) hme0
2) qfe0
3) qfe1
4) qfe2
5) Other

Option:   1

Searching for any unexpected network traffic on “hme0” … done
Verification completed. No traffic was detected over a 10 second
sample period.

——————————————————————————————
Select the second cluster transport adapter for “sun1”:

1) hme0
2) qfe0
3) qfe1
4) qfe2
5) Other

Option:   3

Searching for any unexpected network traffic on “qfe1” … done
Verification completed. No traffic was detected over a 10 second
sample period.

Is it okay to begin the installation (yes/no) [yes]? yes
—————————————————————————————–

During the installation process, sccheck(1M) is run on each of the
new cluster nodes. If sccheck(1M) detects problems, you can either
interrupt the installation process or check the log files after
installation has completed.

Interrupt the installation for sccheck errors (yes/no) [no]? no
——————————————————————————————
Installation and Configuration

Log file – /var/cluster/logs/install/scinstall.log.24537

Testing for “/globaldevices” on “sun1” … done
Testing for “/globaldevices” on “sun2” … done

Checking installation status … done

The Sun Cluster software is already installed on “sun1”.
The Sun Cluster software is not installed on “sun2”.

Generating the download files … done

Started download of the Sun Cluster software to “sun2”.

Started installation of the Sun Cluster software on “sun2”.
—————————————————————————————–
Starting discovery of the cluster transport configuration.

The following connections were discovered:

sun1:hme0   switch1   sun2:hme0
sun1:qfe1   switch2   sun2:qfe1

Completed discovery of the cluster transport configuration.

Started sccheck on “sun1”.
Started sccheck on “sun2”.

sccheck failed for “sun1”.
sccheck failed for “sun2”.

The sccheck command passed on both of the nodes.

Refer to the log file for details.
The name of the log file is /var/cluster/logs/install/scinstall.log.5748.

——————————————————————————————