This procedure describes how to set up and use the scinstall(1M) custom JumpStart installation method. This method installs both Solaris OS and Sun Cluster software on all cluster nodes in the same operation and establishes the cluster. You can also use this procedure to add new nodes to an existing cluster.
Perform the following tasks:
Ensure that the hardware setup is complete and connections are verified before you install Solaris software. See the Sun Cluster Hardware Administration Collection and your server and storage device documentation for details on how to set up the hardware.
Determine the Ethernet address of each cluster node.
If you use a naming service, ensure that the following information is added to any naming services that clients use to access cluster services. See IP Addresses for planning guidelines. See your Solaris system-administrator documentation for information about using Solaris naming services.
Address-to-name mappings for all public hostnames and logical addresses
The IP address and hostname of the JumpStart server
Ensure that your cluster configuration planning is complete. See How to Prepare for Cluster Software Installation for requirements and guidelines.
On the server from which you will create the flash archive, ensure that all Solaris OS software, patches, and firmware that is necessary to support Sun Cluster software is installed.
If Solaris software is already installed on the server, you must ensure that the Solaris installation meets the requirements for Sun Cluster software and any other software that you intend to install on the cluster. See How to Install Solaris Software for more information about installing Solaris software to meet Sun Cluster software requirements.
Ensure that Sun Cluster software packages and patches are installed on the server from which you will create the flash archive. See How to Install Sun Cluster Framework and Data-Service Software Packages (Java ES installer).
Determine which mode of the scinstall utility you will use, Typical or Custom. For the Typical installation of Sun Cluster software, scinstall automatically specifies the following configuration defaults.
Component |
Default Value |
---|---|
Private-network address |
172.16.0.0 |
Private-network netmask |
255.255.0.0 |
Cluster-transport junctions |
switch1 and switch2 |
Global-devices file-system name |
/globaldevices |
Installation security (DES) |
Limited |
Solaris and Sun Cluster patch directory |
/var/cluster/patches |
Complete the appropriate planning worksheet. See Planning the Sun Cluster Environment for planning guidelines.
Typical Mode - If you will use Typical mode and accept all defaults, complete the following worksheet.
Component |
Description/Example |
Answer |
|
---|---|---|---|
JumpStart Directory |
What is the name of the JumpStart directory to use? | ||
Cluster Name |
What is the name of the cluster that you want to establish? | ||
Cluster Nodes |
What are the names of the cluster nodes that are planned for the initial cluster configuration? | ||
Cluster-Transport Adapters and Cables |
First node name: | ||
Transport adapters: |
First
|
Second
|
|
Will this be a dedicated cluster transport adapter? |
Yes | No |
Yes | No |
|
If no, what is the VLAN ID for this adapter? | |||
Specify for each additional node |
Node name: | ||
Transport adapters: |
First
|
Second
|
|
Quorum Configuration (two-node cluster only) |
Do you want to disable automatic quorum device selection? (Answer Yes if any shared storage is not qualified to be a quorum device or if you want to configure a Network Appliance NAS device as a quorum device.) |
Yes | No |
Yes | No |
Custom Mode - If you will use Custom mode and customize the configuration data, complete the following worksheet.
Follow these guidelines to use the interactive scinstall utility in this procedure:
Interactive scinstall enables you to type ahead. Therefore, do not press the Return key more than once if the next menu screen does not appear immediately.
Unless otherwise noted, you can press Control-D to return to either the start of a series of related questions or to the Main Menu.
Default answers or answers to previous sessions are displayed in brackets ([ ]) at the end of a question. Press Return to enter the response that is in brackets without typing it.
Set up your JumpStart installation server.
Follow the appropriate instructions for your software platform.
Solaris OS Platform |
Instructions |
---|---|
SPARC |
See one of the following manuals for instructions about how to set up a JumpStart installation server:
See also the setup_install_server(1M) and add_install_client(1M) man pages. |
x86 |
See Solaris 9 Software Installation From a PXE Server in Sun Fire V60x and Sun Fire V65x Server Solaris Operating Environment Installation Guide for instructions about how to set up a JumpStart Dynamic Host Configuration Protocol (DHCP) server and a Solaris network for Preboot Execution Environment (PXE) installations. |
Ensure that the JumpStart installation server meets the following requirements.
The installation server is on the same subnet as the cluster nodes, or on the Solaris boot server for the subnet that the cluster nodes use.
The installation server is not itself a cluster node.
The installation server installs a release of the Solaris OS that is supported by the Sun Cluster software.
A custom JumpStart directory exists for JumpStart installation of Sun Cluster software. This jumpstart-dir directory must contain a copy of the check(1M) utility. The directory must also be NFS exported for reading by the JumpStart installation server.
Each new cluster node is configured as a custom JumpStart installation client that uses the custom JumpStart directory that you set up for Sun Cluster installation.
If you are installing a new node to an existing cluster, add the node to the list of authorized cluster nodes.
Switch to another cluster node that is active and start the scsetup(1M) utility.
Use the scsetup utility to add the new node's name to the list of authorized cluster nodes.
For more information, see How to Add a Node to the Authorized Node List in Sun Cluster System Administration Guide for Solaris OS.
On a cluster node or another machine of the same server platform, install the Solaris OS, if you have not already done so.
Follow procedures in How to Install Solaris Software.
On the installed system, install Sun Cluster software, if you have not done so already.
Follow procedures in How to Install Sun Cluster Framework and Data-Service Software Packages (Java ES installer).
Enable the common agent container daemon to start automatically during system boots.
# cacaoadm enable |
On the installed system, install any necessary patches to support Sun Cluster software.
On the installed system, update the /etc/inet/hosts file with all IP addresses that are used in the cluster.
Perform this step regardless of whether you are using a naming service. See IP Addresses for a listing of Sun Cluster components whose IP addresses you must add.
For Solaris 10, on the installed system, update the /etc/inet/ipnodes file with all IP addresses that are used in the cluster.
Perform this step regardless of whether you are using a naming service.
Create the flash archive of the installed system.
# flarcreate -n name archive |
Name to give the flash archive.
File name to give the flash archive, with the full path. By convention, the file name ends in .flar.
Follow procedures in one of the following manuals:
Ensure that the flash archive is NFS exported for reading by the JumpStart installation server.
See Solaris NFS Environment in System Administration Guide, Volume 3 (Solaris 8) or Managing Network File Systems (Overview), in System Administration Guide: Network Services (Solaris 9 or Solaris 10) for more information about automatic file sharing.
From the JumpStart installation server, start the scinstall(1M) utility.
The path /export/suncluster/sc31/ is used here as an example of the installation directory that you created. In the CD-ROM path, replace arch with sparc or x86 and replace ver with 8 for Solaris 8, 9 for Solaris 9, or 10 for Solaris 10.
# cd /export/suncluster/sc31/Solaris_arch/Product/sun_cluster/ \ Solaris_ver/Tools/ # ./scinstall |
From the Main Menu, choose the menu item, Configure a cluster to be JumpStarted from this installation server.
This option is used to configure custom JumpStart finish scripts. JumpStart uses these finish scripts to install the Sun Cluster software.
*** 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) Upgrade this cluster node * 5) Print release information for this cluster node * ?) Help with menu options * q) Quit Option: 2 |
Follow the menu prompts to supply your answers from the configuration planning worksheet.
The scinstall command stores your configuration information and copies the autoscinstall.class default class file in the jumpstart-dir/autoscinstall.d/3.1/ directory. This file is similar to the following example.
install_type initial_install system_type standalone partitioning explicit filesys rootdisk.s0 free / filesys rootdisk.s1 750 swap filesys rootdisk.s3 512 /globaldevices filesys rootdisk.s7 20 cluster SUNWCuser add package SUNWman add |
Make adjustments to the autoscinstall.class file to configure JumpStart to install the flash archive.
Modify entries as necessary to match configuration choices you made when you installed the Solaris OS on the flash archive machine or when you ran the scinstall utility.
For example, if you assigned slice 4 for the global-devices file system and specified to scinstall that the file-system name is /gdevs, you would change the /globaldevices entry of the autoscinstall.class file to the following:
filesys rootdisk.s4 512 /gdevs |
Change the following entries in the autoscinstall.class file.
Existing Entry to Replace |
New Entry to Add |
||
---|---|---|---|
install_type |
initial_install |
install_type |
flash_install |
system_type |
standalone |
archive_location |
retrieval_type location |
See archive_location Keyword in Solaris 8 Advanced Installation Guide, Solaris 9 9/04 Installation Guide, or Solaris 10 Installation Guide: Custom JumpStart and Advanced Installations for information about valid values for retrieval_type and location when used with the archive_location keyword.
Remove all entries that would install a specific package, such as the following entries.
cluster SUNWCuser add package SUNWman add |
Set up Solaris patch directories, if you did not already install the patches on the flash-archived system.
If you specified a patch directory to the scinstall utility, patches that are located in Solaris patch directories are not installed.
Create jumpstart-dir/autoscinstall.d/nodes/node/patches/ directories that are NFS exported for reading by the JumpStart installation server.
Create one directory for each node in the cluster, where node is the name of a cluster node. Alternately, use this naming convention to create symbolic links to a shared patch directory.
# mkdir jumpstart-dir/autoscinstall.d/nodes/node/patches/ |
Place copies of any Solaris patches into each of these directories.
Place copies of any hardware-related patches that you must install after Solaris software is installed into each of these directories.
If you are using a cluster administrative console, display a console screen for each node in the cluster.
If Cluster Control Panel (CCP) software is installed and configured on your administrative console, use the cconsole(1M) utility to display the individual console screens.
Use the following command to start the cconsole utility:
# /opt/SUNWcluster/bin/cconsole clustername & |
The cconsole utility also opens a master window from which you can send your input to all individual console windows at the same time.
If you do not use the cconsole utility, connect to the consoles of each node individually.
Shut down each node.
# shutdown -g0 -y -i0 |
Boot each node to start the JumpStart installation.
On SPARC based systems, do the following:
ok boot net - install |
Surround the dash (-) in the command with a space on each side.
On x86 based systems, do the following:
When the BIOS information screen appears, press the Esc key.
The Select Boot Device screen appears.
On the Select Boot Device screen, choose the listed IBA that is connected to the same network as the JumpStart PXE installation server.
The lowest number to the right of the IBA boot choices corresponds to the lower Ethernet port number. The higher number to the right of the IBA boot choices corresponds to the higher Ethernet port number.
The node reboots and the Device Configuration Assistant appears.
On the Boot Solaris screen, choose Net.
At the following prompt, choose Custom JumpStart and press Enter:
Select the type of installation you want to perform: 1 Solaris Interactive 2 Custom JumpStart Enter the number of your choice followed by the <ENTER> key. If you enter anything else, or if you wait for 30 seconds, an interactive installation will be started. |
When prompted, answer the questions and follow the instructions on the screen.
JumpStart installs the Solaris OS and Sun Cluster software on each node. When the installation is successfully completed, each node is fully installed as a new cluster node. Sun Cluster installation output is logged in a /var/cluster/logs/install/scinstall.log. N file.
For the Solaris 10 OS, verify on each node that multi-user services for the Service Management Facility (SMF) are online.
If services are not yet online for a node, wait until the state becomes online before you proceed to the next step.
# svcs multi-user-server STATE STIME FMRI online 17:52:55 svc:/milestone/multi-user-server:default |
If you are installing a new node to an existing cluster, create mount points on the new node for all existing cluster file systems.
From another cluster node that is active, display the names of all cluster file systems.
% mount | grep global | egrep -v node@ | awk '{print $1}' |
On the node that you added to the cluster, create a mount point for each cluster file system in the cluster.
% mkdir -p mountpoint |
For example, if a file-system name that is returned by the mount command is /global/dg-schost-1, run mkdir -p /global/dg-schost-1 on the node that is being added to the cluster.
The mount points become active after you reboot the cluster in Step 24.
If VERITAS Volume Manager (VxVM) is installed on any nodes that are already in the cluster, view the vxio number on each VxVM–installed node.
# grep vxio /etc/name_to_major vxio NNN |
Ensure that the same vxio number is used on each of the VxVM-installed nodes.
Ensure that the vxio number is available for use on each of the nodes that do not have VxVM installed.
If the vxio number is already in use on a node that does not have VxVM installed, free the number on that node. Change the /etc/name_to_major entry to use a different number.
(Optional) To use dynamic reconfiguration on Sun Enterprise 10000 servers, add the following entry to the /etc/system file. Add this entry on each node in the cluster.
set kernel_cage_enable=1 |
This entry becomes effective after the next system reboot. See the Sun Cluster System Administration Guide for Solaris OS for procedures to perform dynamic reconfiguration tasks in a Sun Cluster configuration. See your server documentation for more information about dynamic reconfiguration.
To re-enable the loopback file system (LOFS), delete the following entry from the /etc/system file on each node of the cluster.
exclude:lofs |
The re-enabling of LOFS becomes effective after the next system reboot.
You cannot have LOFS enabled if you use Sun Cluster HA for NFS on a highly available local file system and have automountd running. LOFS can cause switchover problems for Sun Cluster HA for NFS. If you enable LOFS and later choose to add Sun Cluster HA for NFS on a highly available local file system, you must do one of the following:
Restore the exclude:lofs entry to the /etc/system file on each node of the cluster and reboot each node. This change disables LOFS.
Disable the automountd daemon.
Exclude from the automounter map all files that are part of the highly available local file system that is exported by Sun Cluster HA for NFS. This choice enables you to keep both LOFS and the automountd daemon enabled.
See Types of File Systems in System Administration Guide, Volume 1 (Solaris 8) or The Loopback File System in System Administration Guide: Devices and File Systems (Solaris 9 or Solaris 10) for more information about loopback file systems.
x86: Set the default boot file to kadb.
# eeprom boot-file=kadb |
The setting of this value enables you to reboot the node if you are unable to access a login prompt.
If you performed a task that requires a cluster reboot, follow these steps to reboot the cluster.
The following are some of the tasks that require a reboot:
Adding a new node to an existing cluster
Installing patches that require a node or cluster reboot
Making configuration changes that require a reboot to become active
From one node, shut down the cluster.
# scshutdown |
Do not reboot the first-installed node of the cluster until after the cluster is shut down. Until cluster installation mode is disabled, only the first-installed node, which established the cluster, has a quorum vote. In an established cluster that is still in installation mode, if the cluster is not shut down before the first-installed node is rebooted, the remaining cluster nodes cannot obtain quorum. The entire cluster then shuts down.
Cluster nodes remain in installation mode until the first time that you run the scsetup(1M) command. You run this command during the procedure How to Configure Quorum Devices.
Reboot each node in the cluster.
On SPARC based systems, do the following:
ok boot |
On x86 based systems, do the following:
<<< Current Boot Parameters >>> Boot path: /pci@0,0/pci-ide@7,1/ata@1/cmdk@0,0:b Boot args: Type b [file-name] [boot-flags] <ENTER> to boot with options or i <ENTER> to enter boot interpreter or <ENTER> to boot with defaults <<< timeout in 5 seconds >>> Select (b)oot or (i)nterpreter: b |
The scinstall utility installs and configures all cluster nodes and reboots the cluster. The cluster is established when all nodes have successfully booted into the cluster. Sun Cluster installation output is logged in a /var/cluster/logs/install/scinstall.log.N file.
From one node, verify that all nodes have joined the cluster.
Run the scstat(1M) command to display a list of the cluster nodes. You do not need to be logged in as superuser to run this command.
% scstat -n |
Output resembles the following.
-- Cluster Nodes -- Node name Status --------- ------ Cluster node: phys-schost-1 Online Cluster node: phys-schost-2 Online |
If you added a node to a two-node cluster, go to How to Update SCSI Reservations After Adding a Node.
If you intend to install data services, go to the appropriate procedure for the data service that you want to install and for your version of the Solaris OS:
Sun Cluster 2 of 2 CD-ROM (Sun Java System data services) |
Sun Cluster Agents CD (All other data services) |
|||
---|---|---|---|---|
Procedure |
Solaris 8 or 9 |
Solaris 10 |
Solaris 8 or 9 |
Solaris 10 |
How to Install Sun Cluster Framework and Data-Service Software Packages (Java ES installer) |
X | |||
X | ||||
X |
X |
|||
How to Install Data-Service Software Packages (Web Start installer) |
X |
Otherwise, go to the next appropriate procedure:
If you installed a single-node cluster, cluster establishment is complete. Go to Configuring the Cluster to install volume management software and configure the cluster.
If you added a new node to an existing cluster, verify the state of the cluster. Go to How to Verify the Quorum Configuration and Installation Mode.
If you installed a multiple-node cluster and chose automatic quorum configuration, postinstallation setup is complete. Go to How to Verify the Quorum Configuration and Installation Mode.
If you installed a multiple-node cluster and declined automatic quorum configuration, perform postinstallation setup. Go to How to Configure Quorum Devices.
If you added a node to a cluster that had less or more than two nodes, go to How to Verify the Quorum Configuration and Installation Mode.
Disabled scinstall option – If the JumpStart option of the scinstall command does not have an asterisk in front, the option is disabled. This condition indicates that JumpStart setup is not complete or that the setup has an error. To correct this condition, first quit the scinstall utility. Repeat Step 1 through Step 10 to correct JumpStart setup, then restart the scinstall utility.
Error messages about nonexistent nodes – Unless you have installed your own /etc/inet/ntp.conf file, the scinstall command installs a default ntp.conf file for you. The default file is shipped with references to the maximum number of nodes. Therefore, the xntpd(1M) daemon might issue error messages regarding some of these references at boot time. You can safely ignore these messages. See How to Configure Network Time Protocol (NTP) for information about how to suppress these messages under otherwise normal cluster conditions.
Changing the private-network address – You cannot change the private-network address and netmask after scinstall processing has finished. If you need to use a different private-network address or netmask and the node is still in installation mode, follow the procedures in How to Uninstall Sun Cluster Software to Correct Installation Problems. Then repeat this procedure to reinstall and configure the node with the correct information.