Home > Articles > Programming > General Programming/Other Languages

  • Print
  • + Share This
Like this article? We recommend

Section 1.1: Solaris Configuration (clustadm)

This section describes the steps necessary to install Solaris 8 (plus patches) on the Sun Cluster administrative workstation (clustadm). The same version of Solaris OE must run on both the clustadm workstation and on each of the cluster nodes. The workstation is used for the installation and for basic cluster operations.


At this time, it is assumed that all systems and subsystems have been powered on, and the SunPlex platform is fully configured (as per Figure 1, and Table 1 through Table 5). All hardware components are operational.

Key Practice: Ensure all firmware is installed with the most recent (supported) versions for all systems and subsystems, including all servers, disk arrays, controllers, and terminal concentrators. For example, on each node in the SunPlex platform, ensure the system EEPROM contains the most recent (supported) version of OpenBoot PROM (OBP) such as, OpenBoot 3.15.

Step 1.1.1

For local (manual) installations, it is a good idea to ensure that the clustadm workstation is configured with the most recent version of the OBP. Information about downloading can be obtained from SunSolveSM, at http://sunsolve.sun.com. After upgrading the OBP, manually turn system power off, and then on, before continuing with the next step.

Step 1.1.2

For local (manual) installations, install Solaris OE on the clustadm workstation according to the recommendations listed on the EIS Installation Checklist for SunCluster 3.0 Systems. Specifically, obtain most recent EIS CDs, and follow the guidelines for "Installation of the Administration Workstation," including the EIS "WorkGroup Server" (WGS) checklist.

  • Checklist recommendations include installing the Entire Distribution, choosing the proper locale (english), and the root disk layout. Choose Entire Distribution+OEM, if required.

  • During the installation, don't forget to install the Solaris man pages.

EIS Installation Checklists are located on EIS CD1, under: sun/docs/EISchecklists/pdf


For new cluster installations, obtain all site-specific information by examining the appropriate EIS installation documentation, and completing all EIS preinstallation procedures.

Key Practice: Implement Solaris JumpStart to maintain consistency and fully automate the installation of the Solaris Operating Environment and additional software packages for each node in the SunPlex platform. Solaris JumpStart can improve installations and minimize operator errors that occur during a manual process. Combining Solaris JumpStart and Flash archives enables quick and consistent disaster/recovery operations.

Step 1.1.3

For local (manual) installations, reboot the clustadm workstation after installing Solaris.

Step 1.1.4

Verify the correct Solaris OE configuration. At this time, log in as the root user and ensure Solaris has been configured correctly, on the clustadm workstation.

For these examples, the root password is abc

Example Solaris OE configuration – clustadm workstation

Host name:


IP Address:


Name Service:

None (local files)

Set Subnet:


Subnet Mask:

Default Gateway:



The values quoted in the previous table are sample values. For local (manual) installations, substitute the appropriate site-specific values, as provided on the EIS installation documentation.

Step 1.1.5

Verify that the following partitioning guidelines have been implemented for the clustadm workstation, which reserves space for use by a volume manager, and allocates 2 Gbytes (slice 1) for swap space, then assigns unallocated space to / (root, on slice 0).


It is often easier to use the Solaris format command to calculate the exact number of even cylinders to be configured, as when determining the size of the root file system.

Configure boot disk slices using the following guidelines:

Slice 0 = assigned to "/" (all unallocated space)
Slice 1 = assigned to swap (2 GB)
Slice 2 = assigned as backup (full extent)


These procedures, DO NOT include the steps necessary to configure a volume manager on the clustadm workstation; however, it is a good idea to configure one. For example, implement Solaris™ Volume Manager (SVM) and configure a highly available boot environment (that is, alternate boot disk and controller). At a minimum, data should be protected against failure of any single diskspindle.

Key Practice: Configure a standard, flexible disk partitioning scheme. Partitioning each disk spindle identically can save time, provide flexibility, and maintain consistency across nodes. In this case, use a consistent partitioning scheme that is flexible, allows for using either SVM or VxVM. Implement the following standard partitioning for boot disks:

Reserve the first few cylinders for use by a volume manager. For SVM, the reserved space (20 Mbytes) should be assigned to slice 7. For VxVM, a minimum of two cylinders are required, and slices 3 and 4 must be unassigned. Some customer applications require use of a slice. The alternate boot environment, Live Upgrade requires one slice.


Installing the entire Solaris media kit can require nearly 13 Gbytes. Assuming 36 Gbyte disk drives, this should be more than sufficient for the boot disk layout being proposed here.

Key Practice: Verify that the Solaris OE installation was successful and that any errors reported are resolved before proceeding. Review the /var/sadm/README file to determine the location of the most recent installation logs (for example, /var/sadm/system/logs). Examine the current Solaris OE installation log files begin.log, sysidtool.log, or install_log for potential errors. Confirm the cause of any installation error messages which may occur, resolving failures before proceeding further. Refer to the SC3.0 U3 Error Messages Manual for error message translations.

Step 1.1.6

Examine the installation logs, ensuring that any Solaris OE installation errors do not go undetected, or unresolved. On the clustadm workstation, type the following commands:

clustadm# cd /var/sadm/system/logs
clustadm# pwd

clustadm# ls
begin.log       finish.log       install.log
begin.log_2000_04_13 finish.log_2000_04_13 sysidtool.log {{sample dates only}}
clustadm# more *
{{It is important to resolve any installation error messages noted in the logs.

pkgadd: ERROR: postinstall script did not complete successfully}}

Step 1.1.7

For local (manual) installations, insert the first EIS CD into the clustadm workstation.

Step 1.1.8

Change to the <eis-cd>.../sun/install directory, where the setup-standard.sh script is located. The setup-standard.sh script will set up the EIS environment, and adds Explorer and ACT software. Additionally, this script configures the root user and shell environment, and will dynamically configure your path based upon your actual configuration.

Enter the following commands to set up the EIS environment, on the clustadm workstation:

# cd /cdrom/eis-cd/sun/install
# sh setup-standard.sh
  • Many prompts provide a default value. Accept all default values, except as noted for the following:

  • Enter "n", when asked if you want to "enable the email panic facility", during ACT installation (into the /opt/CTEact directory).

  • When prompted for the SUNWexplo package, enter all site-specific information, as appropriate.

  • Enter a single "-" , when asked "Would you like explorer output to be sent to alternate email addresses at the completion of explorer?"

  • Enter "n", when asked if you "wish to run explorer once a week?"

  • When prompted, DO NOT run /opt/SUNWexplo/bin/explorer -q -e at this time. We will use this tool to gather important cluster configuration data after the installation has been completed.

  • For /opt/SUNWexplo, type "y" when asked if you "want this directory created now?"

  • Enter "y" to proceed with the installation of explorer.

Upon completion, you should see a message indicating the "/.profile was created/modified", along with notification that the "Installation of <SUNWexplo> was successful".

Step 1.1.9

Activate the EIS environment, by invoking a new shell, or simply executing 'su - ' , at this time. If you are connected to the /dev/console port, you should log off and then on again.

Verify that all settings and environment variables are configured, as required.

Example: Environment Variables (settings) - clustadm




ansi or vt100



set prompt


Ensure the following PATH variable settings


Ensure the following MANPATH variable settings


It is important to note that the EIS setup-standard.sh script configures /.profile to ensure the correct EIS installation environment.

Step 1.1.10

Prior to using a text editor (such as vi) to view or modify files, ensure your terminal environment variable, as appropriate. We recommend TERM=ansi; export TERM for proper video display.

  • + Share This
  • 🔖 Save To Your Account