Home > Articles > Operating Systems, Server > Solaris

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

Section 2.11: Configure Additional Cluster Management Services

In this section, you will configure additional management services that can help the cluster administrator by making cluster operations more efficient and less error prone.


In future modules, you will be instructed further on how to setup additional Sun Cluster 3.0 software features, as required to complete the Sun Cluster 3.0 software configuration.

Step 2.11.1—Setting Up the syslog(1M) Feature

As per site-specific requirements, we recommend setting up the syslog(1M) facility by configuring the /etc/syslog.conf file on each cluster node and verifing that the messages are logged properly.

Key Practice: On each cluster node, set up the syslog(1M) facility to forward errors and system messages to the management server (administrative workstation). The logged message includes a message header and a message body. The message header consists of a facility indicator, a severity level indicator, a timestamp, a tag string, and optionally the process ID. See the syslogd(1M) and syslog(3C) man pages for additional information.

Step 2.11.2—Implementing a Repository

Implement a repository on the management server (clustadm) for saving a snapshot of site-specific and system configuration files. This includes all modified system files specific to each node. Additionally, for each cluster node, ensure that a valid backup (most recent snapshot) is maintained for each file and that the owner, group, and permissions are preserved correctly.

Key Practice: Simplify cluster administration and management operations by ensuring consistent pathnames within the managed cluster environment. For example, when performing the Sun Cluster 3.0 software installation procedures, you may be required to re-access specific software (applications) or be required to re-enter certain command sequences (steps) repeatedly. This may be necessary if a data entry error occurs or when a given series of setup instructions have failed and the subsequent verification instructions do not produce the intended results. To further simplify the numerous tasks required to successfully complete the setup of a cluster, implement time-saving practices.

Simplify the numerous "management server-to-cluster node" NFS mounting of directories (and NFS exported filesystems) by creating a mount point (directory name) that can be shared from the management server and accessed remotely by each cluster node using the following syntax:


Where mgmt_server is clustadm and directory is the name of the cluster node (for example, clustnode1).

This ensures that the path naming to the referenced resources is consistent, regardless of where the following administration functions are being performed.

Execute the following commands on the management server:

clustadm# mkdir /saved_files/clustnode1
clustadm# mkdir /saved_files/clustnode1
clustadm# chmod -R 777 /saved_files

Key Practice: Decrease administrative overhead of repetitive cluster operations and improve efficiency by implementing a centralized repository for site-specific configuration data files. Whenever any of these site-dependent files are modified, ensure a consistent, valid backup is created on the management sever (the central repository).

When setting up and maintaining the SunPlex platform, certain procedures can become repetitive when configuring multiple cluster nodes, or you may be required to reconstruct the cluster configuration to resolve problems caused by mistakes and operator errors. In theory, almost any system file that has to be modified during the configuration process can be saved to the management server (and easily restored, as needed). For each file, ensure backups are valid (copied without errors) and have retained the proper owner, group, and permissions.

Create a repository for the following site-specific files:

  • /.profile
  • /.cshrc
  • /.login
  • /.rhosts
  • /etc/inet/hosts
  • /etc/ftpusers
  • /etc/defaultlogin
  • /etc/group
  • /etc/inet/ntp.conf

Additional examples of site-specific system files modified during these exercises includes, but are not limited to, the following:

  • /etc/ethers
  • /etc/vfstab
  • /etc/dfs/dfstab
  • /etc/defaultrouter
  • /etc/serialports
  • /etc/notrouter
  • /etc/syslog.conf
  • /kernel/drv/md.conf
  • /etc/lvm/md.tab
  • VTOC information (for all disks and/or types, the output from prtvtoc(1M) is saved)

  • Cluster post-installation information (for example, after the installation is successfully completed, the output from the scconf(1M), scstat(1M), and scrgadm(1M) utilities is saved to document the installation and configuration of the cluster)

Consider the following for each node being managed:

  • Cluster node host ID
  • BIOS information
  • OpenBoot PROM settings
  • Logical host attributes

Step 2.11.3—Setting Up the /saved_files Directory

On the management server (clustadm), create a new entry in the /etc/dfs/dfstab file so that the /saved_files directory is added and made exportable (that is, shared) with read and write (rw) permission for each cluster node. See to Step 2.3.4 and Step 2.3.5 for an example on creating a dfstab entry and sharing the directory.

Verify that the entry created in the /etc/dfs/dfstab file is correct and that the directory is shared correctly and accessible on each cluster node, before proceeding to the next step.

Step 2.11.4—Copying Site-Specific Configuration Files From clustnode1

Copy all of the site-specific configuration files from clustnode1 to the /saved_files/clustnode1 directory on the management server, as in the following example.

clustnode1# cd /net/clustadm/saved_files/clustnode1
clustnode1# pwd 


Step 2.11.5—Copying Site-Specific Configuration Files From clustnode2

Copy all of the site-specific configuration files from clustnode2 to the /saved_files/clustnode2 directory on the management server.

clustnode2# cd /net/clustadm/saved_files/clustnode2
clustnode2# pwd 


Step 2.11.6—Creating a Backup of Site-Specific System Configuration Files

Create a backup of all of the site-specific system configuration files. Execute the following commands on each cluster node:

clustnode1# cp /.profile .
clustnode1# cp /.cshrc .
clustnode1# cp /.login .
clustnode1# cp /.rhosts .
clustnode1# cp /etc/inet/hosts .
clustnode1# cp /etc/ftpusers .
clustnode1# cp /etc/defaultlogin .

Key Practice: When making modifications to the hosts file, always reference the /etc/inet/hosts (source) file because the /etc/hosts file is a link to /etc/inet/hosts.

Step 2.11.7—Verifying the Backup Files

Verify that the files were copied correctly (that is, there is a valid backup), including the correct filenames, owner, group, and permissions. For any system file that gets modified and backed up (and which may need to be restored later, simply reverse the process of copying these files). Care must be taken to know the correct file owner, group, and permission settings for each backup created. Ensure a valid backup was created with the following command:

# ls -lisa

{{Verify snapshot was successful, and files were copied correctly.}}

Key Practice: Create an consistent, automated method for ensuring that all of the site-dependent system files are backed up correctly.

A simple tar(1) command can make an efficient backup method for each cluster node, saving site-specific files and retaining the correct owner, group, and permissions by executing the following commands:

# cd /net/mgmt_server/saved_files/node-specific-directory
# tar cvf ./systemfiles.tar /.profile /.cshrc /.login /.rhosts /etc/inet/hosts 
/etc/ftpusers /etc/defaultlogin 

{{Verify files are copied to the correct destination directory, and a
valid backup was created.}}

Ensure that a valid restoration can be achieved. After verifying the backup is created correctly, ensure that the system files can be restored correctly (that is, a valid restoration) by using the most recent (valid) backup before continuing to build the cluster.

Verify that a complete restoration occurs for all site-specific and system files and that each file retains the correct owner, group, and permissions by executing the following command:

clustnode2# cd /net/mgmt_server/saved_files/clustnode2
clustnode2# tar xvfp ./systemfiles.tar /.profile /.cshrc /.login /.rhosts 
/etc/inet/hosts /etc/ftpusers /etc/defaultlogin 

{{verify files are copied to the correct destination
directory, along with correct owner, group, and
permissions, and a valid system file has been restored
on clustnode2.}}


It is a good idea to re-verify the root login, as part of ensuring a valid restoration of all site-specific and system configuration files because the startup scripts may have been altered. One method is to simply verify that you can remotely log in (rlogin) from clustnode1 to clustnode2 as the superuser (root) (in this example, this can be verified after clustnode2 has been restored and before logging off the clustnode2 console). Verify the superuser login for each node that has been restored, as described.

Summary of Key Practices

On each cluster node, set up the syslog(1M) facility to forward errors and system messages to the management server (Sun Cluster 3.0 software administrative workstation).

Simplify cluster administration and repetitive operations by creating a mount point that can be shared from the management server and accessed remotely by each cluster node.

Decrease administrative overhead of repetitive cluster operations and improve efficiency by implementing a centralized repository for site-specific configuration data (files).

Always reference the /etc/inet/hosts file when making modifications.

Implement a consistent, automated method for saving and restoring site-specific and other system files.

Before logging off the console, verify that the superuser can log in successfully after the system files have been restored from the most recent backup.

End of Module Two

Module 2 is now complete. You have successfully performed the following procedures:

  1. Completed the administrative workstation (management server) setup.

  2. Reviewed the configuration of the JumpStart software services (for example, the Solaris OE and the Sun Cluster 3.0 software, plus all patches).

  3. Configured the terminal concentrator.

  4. Configured the Cluster Console (CCP) utility.

  5. Prepared each cluster node before the Solaris OE installation.

  6. Verified that the Solaris OE installation (plus patches) was successful and performed post installation and configuration procedures on each cluster node.

  7. Configured root workspace on each cluster node.

  8. Backed up (saved) all of the site-specific files.

  • + 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