This manual serves as your starting point for using PRIMECLUSTER. It explains the workflow of the series of operations from installation to operation management of the PRIMECLUSTER system. Since the PRIMECLUSTER system comprises multiple features, there are several other manuals besides this one for each feature. However, by reading this manual first, you will be able to perform the series of operations because this manual refers readers to other manuals that contain feature-specific information that is necessary for the operations.
This manual also provides a functional overview of products that are supported by the PRIMECLUSTER system and describes operation procedures.
This manual only covers the basic operation of PRIMECLUSTER. For operations using different hardware and software configurations, see "Related Documentation."
The table below shows the operation flow from PRIMECLUSTER installation to the start of operation management and indicates the reference location in this manual for each operation.
PRIMECLUSTER system operation flow | Reference location in this manual | |
|---|---|---|
1 | Understanding the flow of PRIMECLUSTER system building and designing the PRIMECLUSTER system | Part 1 Planning |
2 | Installing the PRIMECLUSTER system | Part 2 Installation |
3 | Monitoring the operation status of the PRIMECLUSTER system | Part 3 Operations |
4 | Changing the PRIMECLUSTER system configuration after system operation has been started | Part 4 System Configuration Modifications |
5 | Backing up and restoring the operation environment of the PRIMECLUSTER system | Part 5 Maintenance |
6 | Building PRIMECLUSTER systems in virtualized environments | Part 6 Virtualized Environments |
7 | Installing products for the PRIMECLUSTER system | Part 7 PRIMECLUSTER Products |
For detailed procedural explanations, refer to the reference manuals that are indicated in the target location of each part.
Target Readers
This manual is intended for all users who use PRIMECLUSTER 4.3 and perform cluster system installation and operation management. It is also intended for programmers who develop applications that operate on PRIMECLUSTER.
Configuration of This Documentation
This manual consists of seven parts, appendices, and a glossary. The contents of each part are described below.
Audience: System administrators who build PRIMECLUSTER systems
Contents: This part describes the overall workflow from installation to operation of the PRIMECLUSTER system.
Audience: System administrators who build PRIMECLUSTER systems
Contents: This part describes operations for software installation, cluster configuration, and application building.
Audience: System administrators who manage system operations
Contents: This part describes operation methods for operations such as monitoring the PRIMECLUSTER system and investigating failure causes.
Audience: System administrators who build PRIMECLUSTER systems
Contents: This part describes necessary work items for additions, modifications, and deletions to the PRIMECLUSTER system configuration.
Audience: System administrators who build PRIMECLUSTER systems
Contents: This part describes the necessary work items for maintaining the operation environment of the PRIMECLUSTER system.
Audience: All users who use PRIMECLUSTER systems in virtualized environments
Contents: This part describes configurations and building procedures when using PRIMECLUSTER systems in virtualized environments
Audience: Users who operate PRIMECLUSTER products on PRIMECLUSTER systems
Contents: This part describes the versions and levels of products that are supported by the PRIMECLUSTER system and provides a functional overview of those products.
Audience: Users who design PRIMECLUSTER systems
Contents: This appendix contains the PRIMECLUSTER System Design Worksheet.
Audience: All users who use PRIMECLUSTER systems
Contents: This appendix describes the online manual pages that are used by the individual features of the PRIMECLUSTER system.
Audience: All users who use PRIMECLUSTER systems
Contents: This appendix describes corrective actions for problems that may occur in the PRIMECLUSTER system. It also explains how to collect data when requesting a problem investigation.
Audience: All users who used the SynfinityCluster system
Contents: This appendix describes feature differences and terminology differences between SynfinityCluster and PRIMECLUSTER.
Audience: All users who use SynfinityCluster-compatible resources
Contents: This appendix describes procedures for registering, changing, and deleting procedure resources when the cluster applications use procedure resources.
Audience: All users who are moving from SafeCLUSTER to PRIMECLUSTER and using the clgettrigger command with a state transition procedure executed from the procedure resources
Contents: This appendix describes the settings for when acquiring the cause of state transition to the cluster service for which the clgettrigger command was used.
Audience: System administrators who build PRIMECLUSTER systems
Contents: This appendix describes scripts and daemons that are started by PRIMECLUSTER.
Audience: System administrators who build PRIMECLUSTER systems
Contents: This appendix describes SMF services and startup daemons for PRIMECLUSTER, and port numbers being used.
Audience: System administrators who clone PRIMECLUSTER systems
Contents: This appendix describes the procedures for cloning the PRIMECLUSTER system.
Audience: All users who use the Remote Power Distribution Unit in the PRIMECLUSTER system environment
Contents: This appendix describes the procedures when using the Remote Power Distribution Unit in the PRIMECLUSTER system environment.
Audience: All users who have used PRIMECLUSTER 4.2A00, 4.3A10, or 4.3A20
Contents: This appendix describes the changes made to the specifications of PRIMECLUSTER 4.3A40.
Audience: All users who use PRIMECLUSTER systems
Contents: This appendix describes the main changes of this manual.
Audience: All users who use PRIMECLUSTER systems
Contents: This section explains terms used to describe the PRIMECLUSTER system.
Related Documentation
Refer to the following manuals as necessary when setting up the cluster:
PRIMECLUSTER Concepts Guide
PRIMECLUSTER Cluster Foundation (CF) Configuration and Administration Guide
PRIMECLUSTER Reliant Monitor Services (RMS) with Wizard Tools Configuration and Administration Guide
PRIMECLUSTER Global Disk Services Configuration and Administration Guide
PRIMECLUSTER Global File Services Configuration and Administration Guide
PRIMECLUSTER Global Link Services Configuration and Administration Guide: Redundant Line Control Function
PRIMECLUSTER Global Link Services Configuration and Administration Guide: Redundant Line Control Function for Virtual NIC Mode
PRIMECLUSTER Global Link Services Configuration and Administration Guide: Multipath Function
PRIMECLUSTER Web-Based Admin View Operation Guide
PRIMECLUSTER Scalable Internet Services (SIS) Configuration and Administration Guide
PRIMECLUSTER DR/PCI Hot Plug User's Guide
PRIMECLUSTER Messages
Note
The PRIMECLUSTER documentation includes the following documentation in addition to those listed above:
PRIMECLUSTER Software Release Guide and Installation Guide
The data is stored on "DVD" of each package. For details on the file names, see the documentation.
Manual Series
Manual Printing
If you want to print a manual, use the PDF file found on the DVD for the PRIMECLUSTER product. The correspondences between the PDF file names and manuals are described in the PRIMECLUSTER Installation Guide that comes with the product.
You will need Adobe Reader to read and print the PDF file. To get Adobe Reader, see Adobe Systems Incorporated's website.
Online Manuals
To allow users to view the online manuals, use the Cluster management server to register each user name to one of the user groups (wvroot, clroot, cladmin, or clmon).
For information on user group registration procedures and user group definitions, see "4.2.1 Assigning Users to Manage the Cluster"
Conventions
Command line examples that require system administrator (or root) rights to execute are preceded by the system administrator prompt, the hash sign (#). Entries that do not require system administrator rights are preceded by a dollar sign ($).
References to the UNIX operating system commands are followed by their manual page section numbers in parentheses - for example, cp(1)
Keystrokes that represent nonprintable characters are displayed as key icons such as [Enter] or [F1]. For example, [Enter] means press the key labeled Enter; [Ctrl-b] means hold down the key labeled Ctrl or Control and then press the [B] key.
The following typefaces highlight specific elements in this manual.
Typeface | Usage |
|---|---|
Constant Width | Computer output and program listings; commands, file names, manual page names and other literal programming elements in the main body of text. |
Italic | Variables that you must replace with an actual value. |
Bold | Items in a command line that you must type exactly as shown. |
Example 1
Several entries from an /etc/passwd file are shown below:
root:x:0:1:0000-Admin(0000):/: sysadm:x:0:0:System Admin.:/usr/admin:/usr/sbin/sysadm setup:x:0:0:System Setup:/usr/admin:/usr/sbin/setup daemon:x:1:1:0000-Admin(0000):/:
Example 2
To use the cat(1) command to display the contents of a file, enter the following command line:
$ cat file
Material of particular interest is preceded by the following symbols in this manual:
Point
Contains important information about the subject at hand.
Note
Describes an item to be noted.
Example
Describes operation using an example.
Information
Describes reference information.
See
Provides the names of manuals to be referenced.
Oracle Solaris might be described as Solaris, Solaris Operating System, or Solaris OS.
If "Solaris X" is indicated in the reference manual name of the Oracle Solaris manual, replace "Solaris X" with "Oracle Solaris 10 (Solaris 10)" or the "Oracle Solaris 11 (Solaris 11)."
Export Controls
Exportation/release of this document may require necessary procedures in accordance with the regulations of your resident country and/or US export control laws.
Trademarks
UNIX is a registered trademark of The Open Group in the United States and other countries.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Microsoft, Windows, and Internet Explorer are registered trademarks of Microsoft Corporation in the United States and other countries.
NetWorker is a registered trademark or trademark of EMC Corporation in the United States and other countries.
lsof is used for this software.
/*
* Copyright 2002 Purdue Research Foundation, West Lafayette,
* Indiana 47907. All rights reserved.
*
* Written by Victor A. Abell
*
* This software is not subject to any license of the American
* Telephone and Telegraph Company or the Regents of the
* University of California.
*
* Permission is granted to anyone to use this software for
* any purpose on any computer system, and to alter it and
* redistribute it freely, subject to the following
* restrictions:
*
* 1. Neither the authors nor Purdue University are responsible
* for any consequences of the use of this software.
*
* 2. The origin of this software must not be misrepresented,
* either by explicit claim or by omission. Credit to the
* authors and Purdue University must appear in documentation
* and sources.
*
* 3. Altered versions must be plainly marked as such, and must
* not be misrepresented as being the original software.
*
* 4. This notice may not be removed or altered.
*/
Other product names are product names, trademarks, or registered trademarks of these companies.
Fujitsu M10 is sold as SPARC M10 by Fujitsu in Japan.
Fujitsu M10 and SPARC M10 are identical products.
Requests
No part of this documentation may be reproduced or copied without permission of FUJITSU LIMITED.
The contents of this documentation may be revised without prior notice.
Date of publication and edition
June 2015, Fifth edition |
Copyright notice
All Rights Reserved, Copyright (C) FUJITSU LIMITED 2012-2018.
Revision | Location | Edition |
|---|---|---|
Added the notes for the following environments: | 2.2.1.1.1 Cluster System Configuration in Oracle VM Server for SPARC Environment | 5.1 |
Added the description for among the different physical partitions (only between guest domains). | 2.2.1.1.2 Migration for a Cluster System in Oracle VM Server for SPARC Environment | |
Changed the descriptions of the number of the cluster applications. | 2.3 Determining the Cluster System Operation Mode | |
Added the description to Point in "Installation and Setup of Related Software." | 3.2.2 Setting Up Disk Unit | |
Changed the descriptions of Live Migration. | 5.1.1 Setting Up CF and CIP | |
Changed the description, procedure, and note for cloning a cluster system. | 5.1.1 Setting Up CF and CIP | |
Added the check items for using the host name to set up the shutdown facility when using the SSH connection. | 5.1.2.1.1 Checking XSCF Information | |
Added the descriptions of SPARC M10-4S environment. | 5.1.2.1.1 Checking XSCF Information | |
Changed the descriptions of the procedure to set the SNMP agent in XSCF. | 5.1.2.1.2 Setting SNMP | |
Added the notes for the survival priority. | 5.1.2.1.3 Using the Shutdown Configuration Wizard | |
Changed the operation procedure when changing the IP address of the public LAN. | 9.2.1 Changing an IP Address on the Public LAN | |
Changed the descriptions of the OS installation, the control domain settings, and the sample configuration of guest domains. | 14.1.1.1 Cluster System Between Guest Domains Within a Same Physical Partitions | |
Changed the description of Single-Node Cluster Operations. | 16.1.2.1 Operation Mode | |
Changed the description of the procedure when setting the IP address of CIP in the exclusive IP (Solaris 10). | 16.2.4.6 Global Zone Environment Setup | |
Changed the descriptions of the procedure of [Configuration change 2]. | 17.2.2 Changing Configuration after Setting Prerequisites | |
Added the descriptions of the following items: | 17.2.3 Performing Live Migration of the Cluster on the Guest Domains | |
Changed the procedure when removing the shared class forcibly. | 18.4 Changing the Setting in the Single-User Mode | |
Added the procedure for registering Gds resources in userApplication. | 18.6 Changing the Setting in the Multi-User Mode and Restoration of the Configuration Information of GFS/GDS | |
Added the descriptions of port numbers and service names to be supported to Remarks of the following services: | H.2 SMF Service Lists | |
Added the descriptions of the dependency relationship with other services to Remarks of the following service. | H.2 SMF Service Lists | |
Added the description for the information that is necessary for setting the shutdown facility. | 5.1.2.1.1 Checking XSCF Information | 5.2 |
Changed the descriptions of the settings for XSCF. | 5.1.2.1.3 Using the Shutdown Configuration Wizard | |
Added the notes for the resource names of patrol diagnosis facility and procedure resources when checking the registration information of a cluster application. | 6.7.2.1 Creating Standby Cluster Applications | |
SPARC T5/T7/S7 series were added to the supported hardware. | 1.7 Notes When Building a System | 5.3 |
Changed the description of "Synchronize time in the slew mode." | 1.7 Notes When Building a System | |
Added the notes. | Chapter 6 Building Cluster Applications | |
Added the note about the environment variables used with the scripts. | 6.6 Setting Up Online/Offline Scripts | |
Changed the description in "Outline" of MONITORONLY. | 6.7.1.1 Creating Cmdline Resources | |
Added the note to "Prerequisites for NFS Lock Failover." | 6.7.1.2.1 Prerequisites | |
Changed the note about the NFS entry of PRIMECLUSTER. | 6.7.1.2.1 Prerequisites | |
Changed the description about the setting contents of the cluster application. | 6.11.1 Setting Contents of a Cluster Application | |
Added the note about the maintenance mode. | 6.12.2.1.4 Notes When Setting the NULLDETECTOR Flag | |
Changed the note about the environment variables used with the scripts. | 6.12.3 Notes on Scripts | |
Added the procedure to clear the fault trace of the failure resource. | 7.4.1.2 Corrective Action for Failed Resources | |
Changed the note. | 16.2.4.6 Global Zone Environment Setup (After Installation of PRIMECLUSTER to the Non-Global Zone) | |
Added the description and changed the note about kernel parameter. | 16.2.4.6 Global Zone Environment Setup (After Installation of PRIMECLUSTER to the Non-Global Zone) | |
Added the description about local class. | Chapter 18 When Using Oracle VM Server for SPARC P2V Tool to Migrating a Cluster System | |
Changed the description about the procedure to change the cluster interconnect in the migration destination. | 18.6 Changing the Setting in the Multi-User Mode and Restoration of the Configuration Information of GFS/GDS | |
Changed the utilized ports and remarks. | H.2 SMF Service Lists | |
Changed the description of "Changes." | K.1.1 hvshut command | |
Added the note when using the legacy file systems. | 6.4.1.1 Design for using ZFS with a Cluster System | 5.4 |
Changed the setting example of HV_NODENAME. | 6.6 Setting Up Online/Offline Scripts | |
Added the information when the cluster application transits to Standby state. | 6.7.3.1 Setting Exclusive Relationships Between Cluster Applications | |
Changed the description in the table of relationship between AutoStartUp and StandbyTransitions. | 6.11.1 Setting Contents of a Cluster Application | |
Deleted the description when registering multiple Cmdlines in userApplication. | 6.12.3 Notes on Scripts | |
Changed the descriptions in Note. | 10.4.1 Adding Fsystem Resource Dynamically | |
Added the description when registering the Cmdline resources for monitoring the guest domain status. | 14.2.1.1 During Installation | |
Added the procedure necessary if the guest domain name was changed. | 17.2.2 Changing Configuration after Setting Prerequisites | |
Changed the setup procedure when building the cluster application. | Appendix F SafeCLUSTER Compatibility Function Settings | |
Changed the descriptions in "Remarks" of the following SMF services: | H.2 SMF Service Lists |
