Home > Articles > Operating Systems, Server > Solaris

Like this article? We recommend

Section 2.1: Installing and Configuring the Management Server

This section describes how to install the Solaris 8 Operating Environment (Solaris 8 OE), plus patches, on the management server (clustadm).

Key Practice: Ensure that all firmware is installed with the recent versions for all systems and subsystems (for example, for servers, disk arrays, and controllers). For example, on each system (for example, on each SunPlex node), ensure the system EEPROM contains the most current OpenBoot™ PROM version. For the examples presented in this guide, we used OpenBoot 3.15. Additionally, ensure that all subsystems and controllers are configured using the latest versions, as appropriate.

For each SunPlex node, you can find the latest version of the OpenBoot PROM at http://sunsolve.sun.com.

Step 2.1.1—Installing the Solaris OE on the Administrative Workstation

For local (manual) installations, install the Solaris OE on the administrative workstation. In subsequent steps, this workstation will be configured to act as a management server (sometimes referred to as "clustadm").


The same version of the Solaris OE runs on both the administrative workstation (clustadm) and on each cluster node on the SunPlex platform. When configuring the SunPLEX, refer to the actual requirements to determine the appropriate version of Sun Cluster software, plus applications, and to determine the appropriate Solaris OE version and distribution packages to be installed. Determine which, if any, real dependencies exist. For example, selecting "Entire Distribution Plus OEM" may be required if there are any actual dependencies upon third- party software.

Key Practice: Configure a flexible, consistent disk partitioning scheme. For example, configure a consistent partitioning scheme that is flexible enough to allow for the use of either Solstice DiskSuite software or VxVM software.

Implement the following standard partitioning recommendations for boot disks:

  • Partition each disk spindle identically to save time and provide additional configuration flexibility by ensuring consistency across nodes.

  • Reserve cylinders 0–5 (the first six cylinders) on each disk. Both volume managers require these cylinders be left unused and available. For example, Solstice DiskSuite software assigns these cylinders to slice 7 on each disk (for replica metatstate databases). If a volume manager is not configured, there should not be any significant penalties for leaving these cylinders unused.

The following partitioning guidelines can be implemented for the management server (clustadm) boot disk, which reserves approximately 10MB for a volume manager and allocates 1GB (slice 1) for swap space, and assigns all remaining space to "/" (root, on slice 0).

Configure boot disk slices using the following guidelines:

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

Slice 1 = cylinders 7 - 499 assigned to "swap" (approximately 1GB;)

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

Slice 7 = cylinders 1 - 6 "unassigned" (reserve 10MB for use by a volume manager)

{Reserve cylinders 1 - 6: Solstice DiskSuite software would require slice 7; VxXM requires slices 3 and 4.}


Our example assumes an 18GB disk drive with 7506 cylinders. For each configuration, always ensure the slicing information matches the actual disk geometry.


The actual swap space should be sized based on the actual Solaris OE version and the requirements of the applications to be hosted. During the procedures presented in this book, we will not configure a volume manager on the administrative workstation (clustadm).

Step 2.1.2—Verifying the Solaris OE Configuration

To verify that your Solaris OE configuration is correct, log in as the root user on the management server (clustadm) and ensure that the Solaris OE has been installed, as specified in this section, and confirm that the primary boot disk (c0t0) is configured, per the guidelines in this section.


For the examples presented in this guide, the root password is set to abc.

Table 2-1 Solaris OE Configuration



IP address:


Name service:

None (local files)

Set subnet:


Subnet mask:

Default gateway:



The values quoted in the preceding table are sample values. In a live installation, substitute the appropriate site-specific values.

Key Practice: To verify that the Solaris OE installation was successful and that no errors were reported:

  1. Review the /var/sadm/README file to determine the location of the most recent installation logs (for example, to determine the location of /var/sadm/system/logs).

  2. Examine the current Solaris OE installation log files for potential errors (for example, examine begin.log, sysidtool.log, or install.log).

  3. Confirm the cause of any installation error messages that have occurred, resolving failures before proceeding further.

Refer to the SC3.0 U1 Error Messages Manual for error message translations. See Appendix B for information about obtaining this manual.

Step 2.1.3—Tracking Installation Errors

On the administrative workstation, examine the installation logs, ensuring that any Solaris OE installation errors do not go undetected or unresolved. To do this, enter 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 look for installation error messages in the logs.


pkgadd: ERROR: postinstall script did not complete successfully

Step 2.1.4—Obtaining the Latest Solaris OE Patches

For local (manual) installations only, obtain the latest required Solaris OE patches from either the SunSolveSM CD-ROM, or from SunSolve Online at http://sunsolve.Sun.com (click the Patches option on the left column).


SunSolve is a contract service from Sun Enterprise Services. We recommend that you subscribe to this service, especially if you are running a production server. Outside North America, the method you use for obtaining the most recent patches available may deviate from the following procedure, which obtains patches through the http://sunsolve.sun.com web site. Ask your local Sun service provider for the best method for getting the required patch clusters for your current operating environment.

Key Practice: Follow these recommendations when obtaining and using the latest available required Solaris OE patches:

  • Before you install new patches, create a /PATCHES directory on a dedicated server to store the patches. This enables centralized patch management. For example, the Sun BluePrints hands-on lab hardware has been configured with a "master" JumpStart technology server that will serve all software binaries, patches, and act as the repository.

  • Refer to the individual patch README files to review any installation prerequisites before installing patches. Using this practice could prevent conflicts with other patches, software, bootprom variables, or other unknowns.

  • Always install the latest Solaris OE recommended patches from SunSolve. Maintaining the latest recommended patches assures your system provides the highest reliability.

Step 2.1.5—Installing Patches on the Administrative Workstation

For local (manual) installations only, install the latest Solaris OE recommended patches on the administrative workstation. Ensure patches are successfully installed and applied.

Key Practice: Follow these recommendations when installing patches on the administrative workstation.

  • Review the /var/sadm/README file to identify important log files to be examined, including the /var/sadm/install data/Solaris 2.8 Recommended log file.

  • Confirm the cause of any patch installation error messages which may occur.

  • Refer to the SC3.0 U1 Error Messages Manual for error message translations See Appendix B for information about obtaining this manual.

Step 2.1.6—Rebooting the Management Server

For local (manual) installations, reboot the management server after all patches have been successfully installed and applied.

Reboot the system after patches have been installed and applied.


It is often a good idea to reboot the system after changes are made to system software and configuration. For example, at this time, reboot the management server after the patches have been installed to ensure that changes are applied and that a consistent state has been achieved.

Step 2.1.7—Verifying Shell Environment Variables

On the clustadm workstation, log in as the root user. Verify the shell environment variables are established as listed in the following table. Make these settings permanent by editing either the /.profile or /.login (for C shell users) file. Generic examples of each of these files can be found in Appendix A.

Note the following:

  • Export all variables.

  • Use the /.profile or /.login file to make the root user settings.

  • Edit the /etc/passwd file to change the shell—the default shell is /sbin/sh.


Prior to using a text editor (vi) to view and modify files, verify and set your terminal environment variable, as appropriate (for example, set it to TERM=vt220) for proper video display.

Table 2-2 Example Environment Variables








<hostname># {{e.g, clustadm#}}

Add the following to the PATH variable

PATH=$PATH:/usr/bin:/usr/ucb:/etc:/ sbin:/usr/sbin:/opt/SUNWcluster/bin:

Add the following to the MANPATH variable

MANPATH=$MANPATH:/usr/dt/man:/usr/ man:/usr/openwin/share/man:/opt/ SUNWcluster/man:

Summary of Key Practices

Use the JumpStart software to maintain consistency and to fully automate the software installations and configurations of each cluster node.

Ensure all firmware are installed with the most recent required versions for all systems and subsystems (for example, for servers, disk arrays, and controllers). For example, ensure the EEPROM contains the most current OpenBoot PROM version on each cluster node, and that disk subsystems are configured using the latest revisions, as appropriate.

Configure a flexible, consistent disk partitioning scheme.

As part of the initial OS installation preparation, and prior to configuring the system EEPROM, reset the EEPROM to the factory defaults.

Verify that the Solaris OE installation was successful and that all required packages are installed.

Create a /PATCHES directory on a dedicated server to store all patches to enable centralized patch management.

Ensure that no conflicts exist. Refer to the individual patch README files to review any installation prerequisites before installing patches.

Install the latest required Solaris OE patches.

Validate the installation of all patches, reviewing installation logs.

Reboot the system after all patches have been installed and applied.

End of Section 2.1

This completes this section. The Solaris OE has been manually installed and all patches have been applied and verified.

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