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. Maintaining the PRIMECLUSTER system | Part 5 Maintenance |
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.4 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 five parts, appendixes, 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 building, 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 items related to the maintenance of the PRIMECLUSTER system.
Audience: Users who operate PRIMECLUSTER products on PRIMECLUSTER systems
Contents: This appendix describes the list of products supported by PRIMECLUSTER systems.
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 use PRIMECLUSTER-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 use PRIMECLUSTER systems
Contents: This appendix descries Configuration Update Service for SA.
Audience: All users who use PRIMECLUSTER systems in a KVM environment
Contents: This appendix describes the installation procedures for using the PRIMECLUSTER system in a KVM environment.
Audience: All users who use the migration function in a KVM Environment
Contents: This appendix describes the procedure for using the migration function in a KVM Environment.
Audience: All users who use PRIMECLUSTER systems in a VMware environment
Contents: This appendix describes the installation procedures for using the PRIMECLUSTER system in a VMware environment.
Audience: System administrators who build PRIMECLUSTER systems
Contents: This appendix provides explanations on scripts and daemons that are started by PRIMECLUSTER, and the port numbers being used.
Audience: System administrators who build PRIMECLUSTER systems
Contents: This appendix provides explanations on systemd services and daemons that are started by PRIMECLUSTER, and the port numbers being used.
Audience: All users who use PRIMECLUSTER systems
Contents: This appendix describes the procedure when using Firewall in the PRIMECLUSTER system.
Audience: System administrators who clone PRIMECLUSTER systems
Contents: This appendix describes the procedures for cloning the PRIMECLUSTER system.
Audience: All users who use PRIMECLUSTER 4.0A20, 4.1A20, 4.1A30, 4.2A00, 4.2A30, 4.3A00, 4.3A10, 4.3A20, 4.3A30, or 4.3A40.
Contents: This appendix describes the changes made to the specifications of PRIMECLUSTER 4.4A00.
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 Installation and Administration Guide FUJITSU Cloud Service K5
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 Web-Based Admin View Operation Guide
PRIMECLUSTER Messages
PRIMECLUSTER Wizard for Oracle Configuration and Administration Guide
FJQSS (Information Collection Tool) User's Guide
Interstage Application Server Reference Manual - Command Edition
Interstage Application Server Operator's Guide
PRIMEQUEST 1000 Series User Interface Operating Instructions
PRIMEQUEST 1000 Series Message Reference
PRIMEQUEST 1000 Series Tool Reference
PRIMEQUEST 1000 Series Installation Manual
PRIMEQUEST 1000 Series Administration Manual
PRIMEQUEST 1000 Series ServerView Mission Critical Option User Manual
PRIMEQUEST 1000 SERIES HBA blockage function USER'S GUIDE
PRIMEQUEST 2000 Series Tool Reference
PRIMEQUEST 2000 Series Installation Manual
PRIMEQUEST 2000 Series ServerView Mission Critical Option User Manual
PRIMEQUEST 2000 Series HBA blockage function USER'S GUIDE
Note
The PRIMECLUSTER documentation includes the following documentation in addition to those listed above:
PRIMECLUSTER Software Release Guide and Installation Guide
This Software Release Guide and Installation Guide are provided with each PRIMECLUSTER product package.
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 Software Release Guide for PRIMECLUSTER that comes with the product.
Adobe Reader is required to read and print this 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.3.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 Linux(R) 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:0:root:/root:/bin/bash
bin:x:1:1:bin:/bin:/bin/bash
daemon:x:2:2:daemon:/sbin:/bin/bash
lp:x:4:7:lp daemon:/var/spool/lpd:/bin/bash
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.
Red Hat Enterprise Linux is abbreviated as RHEL.
Red Hat Enterprise Linux AS is abbreviated as RHEL-AS.
RHEL and RHEL-AS are abbreviated as Linux(R).
VMware(R) ESXi(TM) is abbreviated as ESXi.
VMware vSphere(R) is abbreviated as VMware vSphere.
VMware vSphere(R) High Availability is abbreviated as VMware HA.
VMware vSphere(R) Fault Tolerance is abbreviated as VMware FT.
VMware vSphere(R) Distributed Resource Scheduler(TM) is abbreviated as VMware DRS.
VMware vSphere(R) Distributed Power Management (TM) is abbreviated as VMware DPM.
VMware vSphere(R) vMotion(R) is abbreviated as VMware vMotion.
VMware vSphere(R) Storage vMotion(R) is abbreviated as VMware Storage vMotion.
VMware(R) vCenter(TM) Converter(TM) is abbreviated as VMware vCenter Converter.
PRIMEQUEST 2000/1000 Series are abbreviated as PRIMEQUEST.
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
Red Hat is a registered trademark of Red Hat, Inc. in the U.S. and other countries.
Linux is a registered trademark of Linus Torvalds.
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.
VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions.
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 2016, First edition |
Copyright notice
All Rights Reserved, Copyright (C) FUJITSU LIMITED 2016-2020.
Revision | Location | Edition |
|---|---|---|
Added the note about kdump_post in /etc/kdump.conf. | 3.3 PRIMECLUSTER Installation | 2.1 |
Added the note when using a bonding device as the cluster interconnect. | 5.1.1 Setting Up CF and CIP | |
Added the note when executing "sdtool -s" after starting the shutdown facility, and when starting the MMB asynchronous monitoring daemon for the first time. | 5.1.2.4.6 Starting the Shutdown Facility | |
Added the note when creating the userApplication name. | 6.7.2 Setting Up userApplication | |
Added the information about the scripts that can be registered to userApplication. | 6.7.2.1 Creating Standby Cluster Applications | |
Added the note when "none" is set to StopCommands. | 6.7.3.1 Setting Up Cmdline Resources | |
Added the description about "Timeout of Check Script." | 6.11.2.2.4 Timeout of Check Script | |
Added the note about the status icon of userApplication in maintenance mode. | 7.1.3.1 RMS Tree | |
Added the procedure to clear the fault trace of a resource to the corrective action for failed resources. | 7.4.1.2 Corrective Action for Failed Resources | |
Added the procedure to remove the system board by using Dynamic Reconfiguration. | 8.1.2.3 Removing System Board by Dynamic Reconfiguration | |
Changed the command execution example in RHEL7 environment. | 9.2.1 Changing the IP Address of the Public LAN | |
Added the note when all userApplications are deleted. | 10.2.2 Deleting a userApplication | |
Added the attribute to be used as a resource name to "Contents to be changed" of "When a cluster application that is performing standby operation is to be changed." | 10.3 Changing the Cluster Configuration | |
Changed the procedure on how to change the startup priority of the state transition procedure. | D.2.2 Changing the Startup Priority of a State Transition Procedure | |
Changed the procedure on how to change the registration information of a procedure resource. | D.2.3 Changing registration information of a procedure resource | |
Added the note when changing the registration information of the procedure resource. | D.2.3 Changing registration information of a procedure resource | |
Added the note about hot swap of the virtual machine software. | H.1 Cluster Systems in a VMware Environment | |
Changed the description about the settings of the virtual network when installing VMware vSphere. | H.2.1.1 Installation and Configuration of Related Software | |
Added the following scripts to /etc/rc3.d. | I.2 Startup Script Lists | |
Changed the utilized ports of S13SMAWsf. | I.2 Startup Script Lists | |
Changed the utilized ports of smawsf.service. | J.2 systemd Service Lists | |
Added poffinhibit.service. | J.2 systemd Service Lists | |
Changed the procedure to delete the shared disk resources. | L.3.4 Restoring the GDS Configuration Information | |
Changed the description of "Changes" of hvshut command. | Appendix M Changes in Each Version | |
Added the description for FUJITSU Cloud Service K5. | 2.2 System Design | 2.2 |
Added the description when using mirroring among servers. | 3.2.1.1 Host OS setup (before installing the operating system on guest OS) | 2.3 |
Changed the note about synchronizing time. | 1.7.1 Common Notes on PRIMERGY/PRIMEQUEST | 2.4 |
Changed the execution example. | 3.1.6.1 PRIMERGY | |
Changed the note about the timeout value of CF heartbeat. | 3.2.3.3 Building a cluster (Host OS) | |
Added the reference of the manual. | 4.3.3.2 Confirming Web-Based Admin View Startup | |
Changed the description of survival scenarios. | 5.1.2.1 Survival Priority | |
Added the note when "TestFailed" is displayed as the test status. | 5.1.2.3.6 Starting up the Shutdown Facility | |
Changed the output example of sfkvmtool -c message. | 5.1.2.5.6 Setting up the Host OS Failover Function to the Host OS (PRIMEQUEST only) | |
Added the description about Check script exit code. | 6.6 Setting Up Online/Offline Scripts | |
Added the information about the list of attributes settable to userApplication and the details of these attributes, and changed the description of information about the scripts which can be registered to userApplication. | 6.7.2.1 Creating Standby Cluster Applications | |
Changed the description about the attribute changing procedure. | 6.7.3.1 Setting Up Cmdline Resources | |
Added the note about the file system on the volume of LVM. | 6.7.3.2 Setting Up Fsystem Resources | |
Changed the description of how to failover a userApplication in the event of a node failure, resource failure, and RMS stop. | 6.10.1 Setting Contents of a Cluster Application | |
Change the outline of MONITORONLY attribute. | 6.11 Notes When Setting Cmdline Resources | |
Changed the Gls resource status from "Wait" to "Online processing" in the figure. | 6.11.1.5 Flow of the Cmdline Resource Operation | |
Added the note about using the maintenance mode. | 6.11.2.1.4 Notes When Setting the NULLDETECTOR Flag | |
Added the note about Check script exit codes. | 6.11.2.2.3 Check Script Exit Code | |
Added the note about when using PRIMECLUSTER products and setting the NULLDETECTOR flag. | 7.2.2.6 Entering maintenance mode for Cluster Application | |
Changed the description of selecting a resource to be deleted. | 10.5 Deleting a Resource | |
Added the note about the VMware environment where the I/O fencing function is used. | 10.5 Deleting a Resource | |
Deleted hvlogcontrol and config.us. | B.6 RMS | |
Deleted the descriptions about hot clone, Data Recovery and backup by VCB. | Appendix H Using PRIMECLUSTER in a VMware Environment | |
Changed the description of the I/O fencing function when a cluster interconnect error occurs. | H.1 Cluster Systems in a VMware Environment | |
Added the note about when using the forcible stop with the I/O fencing function. | H.1 Cluster Systems in a VMware Environment | |
Added the configuration of PRIMECLUSTER Wizard for SAP HANA in comparison with the forcible stop. | H.1 Cluster Systems in a VMware Environment | |
Changed the description about forcible stop functions. | H.1 Cluster Systems in a VMware Environment | |
Changed the setting of the path policy for the Native Multipathing (NMP) | H.1 Cluster Systems in a VMware Environment | |
Added notes about the cluster application in which Gds resource and Fsystem resource are registered. | H.2 Installation | |
Changed the description about settings for shared disks when using the I/O fencing function. | H.2.1.1 Installation and Configuration of Related Software | |
Added the description about PreOnline script, OfflineDone script and Fault script. | H.2.4.1 Setting Up I/O Fencing Function | |
Added chronyd.service. | J.3 Necessary Services for PRIMECLUSTER to Operate | |
Added the setting when using neither GLS nor takeover network. | L.3.7 Changing the Settings of Cluster Application Information | |
Added the note when using the ntpdate service in a RHEL7 environment. | 3.3 PRIMECLUSTER Installation | 2.5 |
Added the note when setting management servers of Web-Based Admin View. | 4.3.3 Initial Setup of Web-Based Admin View | |
Added the note about setting IP addresses. | 4.3.3.1 Initial setup of the operation management server | |
Changed the description of the example of HV_NODENAME. | 6.6 Setting Up Online/Offline Scripts | |
Added the note while executing the hvw command. | 6.7.1 Starting RMS Wizard | |
Added the description about the definition of mount points. | 6.7.3.2 Setting Up Fsystem Resources | |
Added the note when PRIMECLUSTER Wizard for NAS is used. | 6.7.5 Registering the Cluster Service of a PRIMECLUSTER-compatible product | |
Added the description about a cluster application transiting to the Standby state, to "Information." | 6.7.7 Exclusive Relationships Between Cluster Applications | |
Changed the description of notes when setting a cluster application. | 6.10.2 Notes on Configuration | |
Added the description of timeout values of the Check script. | 6.11.2.2.4 Timeout of Check Script | |
Added the note when creating the Fsystem resource. | 6.12.1 Monitoring Fsystem | |
Added the note when displaying logs from Cluster Admin. | 7.1.3.3 Switchlogs and application logs | |
Changed the note when starting the maintenance mode. | 7.2.2.6 Entering maintenance mode for Cluster Application | |
Added the note when starting a system in a RHEL6 environment. | 7.5 Notes on Operation | |
Changed the procedure when changing the IP address of the public LAN. | 9.2.1 Changing the IP Address of the Public LAN | |
Changed the procedure when changing the IP address of the administrative LAN and added "See." | 9.2.2 Changing the IP Address of the Administrative LAN | |
Changed the description about setting RELIANT_SHUT_MIN_WAIT. | 11.2.1 Changing Timeout Time during RMS Stop Processing | |
Changed the description when changing the host names in the takeover network resources. | L.3.7.2 When Using the Takeover Network |
