Home > Articles > Operating Systems, Server > Solaris

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

Section 2.8: Install the Solaris 8 Operating Environment on Each Cluster Node

For local (manual) installations, configure the management server (administrative workstation) as a Solaris OE installation (JumpStart software) server by modifying the JumpStart software configuration to include new class file. These class files should configure a machine to operate as a node within a cluster, according to the following guidelines.

For these hands-on labs, a JumpStart software server has already been configured.


The Solaris OE, plus patch, installation is not performed during these hands-on labs. Instead, each cluster nodes has been previously installed with the Solaris OE and patches.


The same version of the Solaris OE must be installed on the Sun Cluster 3.0 software administrative workstation and each of the cluster nodes in the SunPlex platform. In this procedure, Solaris OE version 8 07/01 is used.

Key Practice: Use the Solaris JumpStart software to maintain consistency and to fully automate the installation of the Solaris OE and additional software packages. The JumpStart software can minimize operator errors that occur during a manual installation process.

Step 2.8.1—Creating a New Class File

For local (manual) installations only, on the management server (the JumpStart software install server), create a new class file (profile) in the /JumpStart directory called cluster_node.class and include the following lines.

install_type initial_install
system_type server
partitioning explicit
cluster  SUNWCXall {{we select Entire Distribution plus OEM}}
usedisk  c0t0d0
filesys  c0t0d0s0  32768  /
filesys  c0t0d0s1  1024  swap


The above code is an example only in which we configure 1 Gbyte of swap space and leave all of the remaining space to root. For Sun Cluster 3.0 software, a minimum of 750 Mbytes of swap space is recommended for each cluster node. For site-specific (actual) implementations, swap size should be configured based on the actual requirements of the application(s) to be hosted. For additional information, see the JumpStart software references in Appendix B.

Step 2.8.2—Ensuring Proper Hostname Configuration

The following sample shows the /etc/inet/hosts file entries required for these exercises. At this time, ensure the correct (site-specific) hostnames are configured, as shown in the following example.

clustadm# more /etc/inet/hosts

. . . {{output omitted}}

xxx.xxx.xx.xxx clustadm loghost
xxx.xxx.xx.xxx clustnode1
xxx.xxx.xx.xxx clustnode2
xxx.xxx.xx.xxx tc nhl-tc

. . . {{output omitted}}

xxx.xxx.xx.xxx lh-hanfs
xxx.xxx.xx.xxx lh-apache

. . . {{output omitted}}


The preceding hostname and IP address information is an example. Carefully note the actual values required at your site. We do not use a naming service or domain name. Instead, we rely on local (/etc) files. For additional configuration information regarding these exercises, see ''Section 2.10: The Solaris OE Post Installation and Configuration'' section on page Module 2-29.

Step 2.8.3—Editing the /JumpStart/rules File

For local (manual) installations, on the JumpStart software install server (management server), edit the /JumpStart/rules file, and add the following lines.

hostname clustnode1 - cluster_node.class set_root_pw
hostname clustnode2 - cluster_node.class set_root_pw


The /JumpStart/rules file should have an entry for each node in the cluster.

Substep 1—Creating a Root Password for Each Cluster Node

For local (manual) installations, on the management server (administrative workstation), edit the /JumpStart/set_root_pw file to create a root password for each cluster node.

Examine the /etc/shadow file, and record the encrypted root password (the UNIX™ software encrypted value).


Previously, we set the password on the management server (administrative workstation) to abc. Because we want to use the same password across all systems (nodes) that have to be started with the JumpStart software, we need to edit the set_root_pw script. The encrypted value of the password (for this lab exercise) is tby83XuShUxKM; however, the value of the password will be different for your installation.


If the password file is not edited to reflect the correct password, the machine will have a password that is unknown. It is possible, though not recommended, to set the root password to null by deleting all of the characters that follow the PASSWD= line in the set_root_pw script.

Substep 2—Editing the /JumpStart/set_root_pw File

For local (manual) installations, edit the /JumpStart/set_root_pw file. Modify the PASSWD= line by entering the encrypted password value recorded in Substep 1, from the /etc/shadow/ file. The edited file should look as follows:

clustadm# more /JumpStart/set_root_pw
# !/bin/sh
#    @(#)set_root_pw 1.6 97/02/26 SMI
# This is an example bourne shell script to be run
# after installation. It sets the system's root
# password to the entry defined in PASSWD. The
# encrypted password is obtained from an existing root
# password entry in /etc/shadow from an installed
# machine.
echo "setting password for root"
# set the root password
PASSWD=tby83XuShUxKM {{edit this line with encrypted
   password value}}
# create a temporary input file

. . .{{the rest of the file has been omitted}}. . .

Step 2.8.4—Verifying the rules and class Files

For local (manual) installations, this final step verifies the rules and class files. A script named check (copied to this directory during a previous step) will be run. This script generates a file named rules.ok, which is read during the JumpStart software installation process.

Execute the /JumpStart/check script and verify the output of the check script, as follows:

clustadm# cd /JumpStart
clustadm# ./check
validating rules...
validating profile standard_load_.class...
The custom JumpStart configuration is ok.

Step 2.8.5—Verifying the rules.ok File

For local (manual) installations, verify that the rules.ok file contains the correct data. Enter the following command, and confirm that the output looks as follows:

clustadm# more rules.ok
hostname clustnode1 - cluster_node.class set_root_pw
hostname clustnode2 - cluster_node.class set_root_pw
# version=2 checksum=5105


The checksum and version values may be different for your installation.

Step 2.8.6—Performing the JumpStart Software Installation

For local (manual) installations, perform a JumpStart software installation for each cluster node (for example, clustnode1 and clustnode2). Enter the following command into the Cluster Console Window for each cluster node being installed:

ok boot net - install
{{note the spaces before and after the hyphen}}


The boot net - install command takes approximately one hour to complete. If error messages appear during this phase, indicating ARP/RARP errors that occur during a boot over the network, the Ethernet address might be incorrect. Before proceeding to the next step, you must troubleshoot and resolve the problem.

You will see Link Down - cable problems? error messages for interfaces that are not connected.

Step 2.8.7—Verifying the Installation

At this point in the installation, verify that each cluster node has been installed successfully. Each node should have been rebooted into multiuser mode, and a login prompt should be displayed.

On each cluster node, log in as superuser (root) from the cconsole:host hostname window for each cluster node.

clustnode1 console login: root
Password: abc
clustnode2 console login: root
Password: abc


Prior to using a text editor (such as, vi) to view or modify files, you must verify that your terminal environment variable is set to TERM=vt220 for proper video display.

Key Practice: Review the /var/sadm/README file to determine the location of the most recent installation logs (for example, /var/sadm/system/logs). Examine the most recently updated log files for potential errors (that is, begin.log, sysidtool.log, or install_log). Confirm the cause of any patch installation error messages that may have occurred. Refer to the Sun Cluster 3.0 U1 Error Messages Manual for error message translations (see Appendix B for information on obtaining this manual).

Step 2.8.8—Verifying the Installation Logs

After the Solaris OE installation is completed, examine the current (that is, the most recent) installation log files, and verify that any installation errors do not go undetected or unresolved on each cluster node, as follows:

# cd /var/sadm/system/logs
# pwd
# ls -t
. . .
. . . {{this output lists the most recently modified files first}})

# more install_log

. . .
{{It is important to look for installation error messages in the logs,
   as in the following example:

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

Note the /var/sadm/README file (when navigating the directory structure). Verify correct log files are referenced (that is, the most recent installation logs). For example, the begin.log and finish.log filenames should have the following form:

begin.log_YYYY_MM_DD and final.log_YYYY_MM_DD (where
YYYY_MM_DD are the install date in year_month_day format)

Step 2.8.9—Verifying the Partitioning

Verify that the primary boot disk was partitioned correctly.


It is easier to use the format(1M) command to calculate the exact number of (even) cylinders to be configured, as when determining the size of the root (/) filesystem. Using these guidelines, the size of the root filesystem is dependent on the actual size of the disk.

On each cluster node, verify that the primary boot disk (c0t0) is partitioned correctly.

The following example is with 18 Gbyte disk:

Slice 0 = cylinders 510 - 7461 assigned to "/" (all unallocated 
space; approximately 10GB)

Slice 1 = cylinders 7 - 500 assigned to "swap" (750MB min.)

Slice 2 = cylinders 0 - 7505 assigned as "backup" (full extent of the

Slice 6 = cylinders 7462 - 7505 assigned to the "/globaldevices"
filesystem (100MB)

Slice 7 = cylinders 1 - 6 assigned to "alternates" for SDS metadata*
(reserve cylinders 1- 6 for use by a volume manager)

*SDS requires slice 7 for storing metadata; VxVM requires slices 3 and 4.


The previous example assumes that the boot disk is an 18 Gbyte disk drive with 7506 cylinders. For each configuration, you must ensure that the slicing information matches the actual disk geometry.

The following example is with 36 Gbyte disk:

Slice 0 = cylinders 510 - 7461 assigned to "/" (approximately 10GB)

Slice 1 = cylinders 7 - 500 assigned to "swap" (750MB min.)

Slice 2 = cylinders 0 - 24619 assigned as "backup" (full extent of
the disk)

Slice 6 = cylinders 7462 - 7505 assigned to the "/globaldevices"
filesystem (100MB)

Slice 7 = cylinders 1 - 6 assigned to "alternates" for SDS metadata* 
(reserve cylinders 1- 6 for use by a volume manager)

*SDS requires slice 7 for storing metadata; VxVM requires slices 3 and 4.


The previous example assumes that the boot disk is a 36 Gbyte disk drive with 24620 cylinders. For each configuration, you must ensure that the slicing information matches the actual disk geometry.


The partition information shown is required to support the Sun Cluster 3.0 software, per the guidelines established in Section 2.1.

Step 2.8.10—Verifying the Hostname Entries

At this time, on each cluster node, verify that the corresponding hostname entries have been created in the /etc/inet/hosts file, as required for the SunPlex platform. Also, verify that any additional or site-specific entries have been created, such as the two logical host entries (as required for our two data services).

# more /etc/inet/hosts

. . . {{output omitted}}

xxx.xxx.xx.xxx clustadm loghost
xxx.xxx.xx.xxx clustnode1
xxx.xxx.xx.xxx clustnode2
xxx.xxx.xx.xxx tc nhl-tc

. . . {{output omitted}}

xxx.xxx.xx.xxx lh-hanfs
xxx.xxx.xx.xxx lh-apache

. . . {{output omitted}}


Example shows standard hostname entries for the cluster. You must verify that your configuration matches the actual (site-specific) installation requirements.

On each node in the SunPlex platform, examine the /etc/inet/hosts file, noting that the site-specific (actual) IP addresses and host names are included, as indicated in the codebox. Specifically, on each cluster node, examine this file, and note the entries for clustnode1, clustnode2, clustadm (the administrative workstation), tc (the terminal concentrator), and lh-hanfs (the first logical host), and lh-apache (the second logical host).

Summary of Key Practices

Use the Solaris JumpStart software to maintain consistency and to fully automate the installation of the Solaris OE and additional software packages.

Verify the Solaris OE installation was successful. Prior to installing the Sun Cluster software, or additional software, ensure each node has been installed correctly, as per site-specific requirements.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020