JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris Cluster System Administration Guide     Oracle Solaris Cluster
search filter icon
search icon

Document Information


1.  Introduction to Administering Oracle Solaris Cluster

Overview of Administering Oracle Solaris Cluster

Working With a Zone Cluster

Oracle Solaris OS Feature Restrictions

Administration Tools

Graphical User Interface

Command-Line Interface

Preparing to Administer the Cluster

Documenting an Oracle Solaris Cluster Hardware Configuration

Using an Administrative Console

Backing Up the Cluster

Beginning to Administer the Cluster

How to Log Into the Cluster Remotely

How to Connect Securely to Cluster Consoles

How to Access the Cluster Configuration Utilities

How to Display Oracle Solaris Cluster Patch Information

How to Display Oracle Solaris Cluster Release and Version Information

How to Display Configured Resource Types, Resource Groups, and Resources

How to Check the Status of Cluster Components

How to Check the Status of the Public Network

How to View the Cluster Configuration

How to Validate a Basic Cluster Configuration

How to Check the Global Mount Points

How to View the Contents of Oracle Solaris Cluster Command Logs

2.  Oracle Solaris Cluster and RBAC

3.  Shutting Down and Booting a Cluster

4.  Data Replication Approaches

5.  Administering Global Devices, Disk-Path Monitoring, and Cluster File Systems

6.  Administering Quorum

7.  Administering Cluster Interconnects and Public Networks

8.  Adding and Removing a Node

9.  Administering the Cluster

10.  Configuring Control of CPU Usage

11.  Patching Oracle Solaris Cluster Software and Firmware

12.  Backing Up and Restoring a Cluster

13.  Administering Oracle Solaris Cluster With the Graphical User Interfaces

A.  Example


Preparing to Administer the Cluster

This section describes how to prepare to administer your cluster.

Documenting an Oracle Solaris Cluster Hardware Configuration

Document the hardware aspects that are unique to your site as your Oracle Solaris Cluster configuration is scaled. To reduce administration, refer to your hardware documentation when you change or upgrade the cluster. Labeling cables and connections between the various cluster components can also make administration easier.

Reduce the time required by a third-party service provider when servicing your cluster by keeping records of your original cluster configuration, and subsequent changes.

Using an Administrative Console

You can use either a dedicated workstation or a workstation connected through a management network as the administrative console, to administer the active cluster. Typically, you install and run the Cluster Control Panel (CCP) and graphical user interface (GUI) tools on the administrative console. For more information about the CCP, see How to Log Into the Cluster Remotely. For instructions on installing the Cluster Control Panel module for Sun Management Center and Oracle Solaris Cluster Manager GUI tools, see the Oracle Solaris Cluster Software Installation Guide.

The administrative console is not a cluster node. The administrative console is used for remote access to the cluster nodes, either over the public network or through a network-based terminal concentrator.

If your SPARC cluster consists of Oracle's Sun Enterprise 10000 server, you must log in from the administrative console to the System Service Processor (SSP). Connect by using the netcon command. The default method for netcon to connect with a Sun Enterprise 10000 domain is through the network interface. If the network is inaccessible, you can use netcon in “exclusive” mode by setting the -f option. You can also type ~* during a normal netcon session. Either of the previous solutions gives you the option of toggling to the serial interface if the network becomes unreachable.

Oracle Solaris Cluster does not require a dedicated administrative console, but using a console provides the following benefits:

Backing Up the Cluster

Back up your cluster on a regular basis. Even though Oracle Solaris Cluster software provides a highly available environment, with mirrored copies of data on the storage devices, Oracle Solaris Cluster software is not a replacement for regular backups. An Oracle Solaris Cluster configuration can survive multiple failures, but does not protect against user or program error, or catastrophic failure. Therefore, you must have a backup procedure in place to protect against data loss.

The following information should be included as part of your backup.