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 |
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.5 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 six 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: 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 have used PRIMECLUSTER 4.2A00, 4.3A10, 4.3A20, 4.3A40, or 4.5A00.
Contents: This appendix describes the changes made to the specifications of PRIMECLUSTER 4.5A10.
Audience: All users who use PRIMECLUSTER systems
Contents: This appendix lists the main changes in 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 Web-Based Admin View Operation 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 DR/PCI Hot Plug User's Guide
PRIMECLUSTER Messages
FJQSS (Information Collection Tool) User's Guide
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 ($).
In manuals, helps, and messages of PRIMECLUSTER, a section number in a manual page is shown in parentheses after a command name or a file name. Example: cp(1)
For Oracle Solaris 11.4 or later, replace the section numbers as follows:
- "(1M)" to "(8)"
- "(4)" to "(5)"
- "(5)" to "(7)"
- "(7)" to "(4)"
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 "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.
*/
Fujitsu SPARC M12 is sold as SPARC M12 by Fujitsu in Japan.
Fujitsu SPARC M12 and SPARC M12 are identical products.
Fujitsu M10 is sold as SPARC M10 by Fujitsu in Japan.
Fujitsu M10 and SPARC M10 are identical products.
Other product names are product names, trademarks, or registered trademarks of these companies.
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
April 2017, First edition |
Copyright notice
All Rights Reserved, Copyright (C) FUJITSU LIMITED 2017-2019.
Revision | Location | Edition |
|---|---|---|
Changed the description in "Dependency relationship with other services" of the following SMF services: | H.2 SMF Service Lists | 2.1 |
