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


Overview of Administering Oracle Solaris Cluster

The Oracle Solaris Cluster highly available environment ensures that critical applications are available to end users. The system administrator's job is to make sure that the Oracle Solaris Cluster configuration is stable and operational.

Familiarize yourself with the planning information in the Oracle Solaris Cluster Software Installation Guide and the Oracle Solaris Cluster Concepts Guide before beginning administration tasks. For instructions on creating a zone cluster, see Configuring a Zone Cluster in Oracle Solaris Cluster Software Installation Guide. Oracle Solaris Cluster administration is organized into tasks among the following manuals.

In general, you can perform Oracle Solaris Cluster administration tasks while the cluster is operational. If you need take a node out of the cluster or even shut down the node, you can do so while the rest of the nodes continue cluster operations. Unless otherwise indicated, Oracle Solaris Cluster administrative tasks should be performed in the global-cluster voting node. For those procedures that require the entire cluster to be shut down, minimize impact on the system by scheduling downtime outside normal working hours. If you plan to shut down the cluster or a cluster node, notify users in advance.

Working With a Zone Cluster

Two Oracle Solaris Cluster administrative commands (cluster and clnode) can also run in a zone cluster. However, the scope of these commands is limited to the zone cluster where the command is issued. For example, using the cluster command in the global-cluster voting node retrieves all information about the voting global cluster and all the zone clusters. Using the cluster command in a zone cluster retrieves information about that specific zone cluster.

When you use the clzonecluster command in a voting node, the command affects all of the zone clusters in the global cluster. Zone cluster commands also affect all nodes on the zone cluster, even if the node is down when the command is issued.

Zone clusters support delegated administration of resources that are under Resource Group Manager (RGM) control. Therefore, zone cluster administrators can view, but not change, zone cluster dependencies that cross zone cluster boundaries. Only the administrator in a voting node can create, modify, or delete dependencies that cross zone cluster boundaries.

The following list contains the major administrative tasks performed on a zone cluster.