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

Document Information

Preface

1.  Introduction to Administering the Geographic Edition Software

2.  Before You Begin

Overview of Oracle Solaris Cluster Administration Concepts

Configuring Resources and Resource Groups

Configuring Logical Hostnames

Managing Device Groups

Overview of Geographic Edition Administration Tasks

Prerequisite Administration Tasks

Geographic Edition Administration Tasks

Example Geographic Edition Cluster Configuration

3.  Administering the Geographic Edition Infrastructure

4.  Administering Access and Security

5.  Administering Cluster Partnerships

6.  Administering Heartbeats

7.  Administering Protection Groups

8.  Monitoring and Validating the Geographic Edition Software

9.  Customizing Switchover and Takeover Actions

10.  Script-Based Plug-Ins

A.  Standard Geographic Edition Properties

B.  Legal Names and Values of Geographic Edition Entities

C.  Disaster Recovery Administration Example

D.  Takeover Postconditions

E.  Troubleshooting Geographic Edition Software

F.  Deployment Example: Replicating Data With MySQL

G.  Error Return Codes for Script-Based Plug-Ins

Index

Overview of Oracle Solaris Cluster Administration Concepts

You must be an experienced Oracle Solaris Cluster administrator to administer Geographic Edition software.

This section describes the Oracle Solaris Cluster administration topics that you need to understand before you administer the Geographic Edition software.

Configuring Resources and Resource Groups

You use either Oracle Solaris Cluster commands or the Oracle Solaris Cluster Manager to create failover and scalable resource groups.

For more information about administering resources and resource groups in Oracle Solaris Cluster software, see the Oracle Solaris Cluster Data Services Planning and Administration Guide.

Configuring Logical Hostnames

The logical hostname is a special high-availability (HA) resource. The geoadm start command configures the logical hostname that corresponds to the cluster name. The IP address and host maps for the logical hostname must be set up before you run this command. Before assigning hostnames, familiarize yourself with the legal names and values that are described in Appendix B, Legal Names and Values of Geographic Edition Entities.

For more information about using the geoadm start command , see Enabling the Geographic Edition Software.


Note - If you are using Sun StorageTek Availability Suite for data replication, a logical hostname is created for each device group to be replicated. For more information, see Chapter 1, Replicating Data With Sun StorageTek Availability Suite Software, in Oracle Solaris Cluster Geographic Edition Data Replication Guide for Sun StorageTek Availability Suite.


The following table lists the Oracle Solaris Cluster and Geographic Edition components that require IP addresses. Add these IP addresses to the following locations:

Table 2-1 IP Addresses Required by Geographic Edition Software

Component
Number of IP Addresses Needed
Oracle Solaris Cluster administrative console
1 per subnet
IP Network Multipathing groups
  • Single-adapter groups – 1 primary IP address. For the Solaris 8 release, also 1 test IP address for each adapter in the group.
  • Multiple-adapter groups – 1 primary IP address plus 1 test IP address for each adapter in the group.

Cluster nodes
1 per node, per subnet
Domain console network interface (Sun Fire 15000)
1 per domain
Console-access device
1
Logical addresses
1 per logical host resource, per subnet
Geographic Edition infrastructure hostname
1 logical IP address per cluster infrastructure.

For example, if you have two clusters in your Geographic Edition infrastructure, you need two IP addresses.

Replication with Sun StorageTek Availability Suite software
1 dedicated logical IP address on the local cluster for each device group to be replicated.

For example, if you have two clusters in your Geographic Edition infrastructure, you need two IP addresses.

For more information about configuring the IP address and host maps during the installation of Oracle Solaris Cluster software, refer to Chapter 2, Installing Software on Global-Cluster Nodes, in Oracle Solaris Cluster Software Installation Guide.

Managing Device Groups

A device group is a hardware resource that is managed by the Oracle Solaris Cluster software. A device group is a type of global device that is used by the Oracle Solaris Cluster software to register device resources, such as disks. A device group can include the device resources of disks, Solaris Volume Manager disk sets, and VERITAS Volume Manager disk groups.

For information about configuring device groups in Oracle Solaris Cluster software, refer to Chapter 5, Administering Global Devices, Disk-Path Monitoring, and Cluster File Systems, in Oracle Solaris Cluster System Administration Guide.

The Geographic Edition software configures Oracle Solaris Cluster device groups to include replication.

For more information about configuring data replication in Geographic Edition software, see Chapter 1, Replicating Data With Sun StorageTek Availability Suite Software, in Oracle Solaris Cluster Geographic Edition Data Replication Guide for Sun StorageTek Availability Suite, Chapter 1, Replicating Data With Hitachi TrueCopy and Universal Replicator Software, in Oracle Solaris Cluster Geographic Edition Data Replication Guide for Hitachi TrueCopy and Universal Replicator, and Chapter 1, Replicating Data With EMC Symmetrix Remote Data Facility Software, in Oracle Solaris Cluster Geographic Edition Data Replication Guide for EMC Symmetrix Remote Data Facility.