Purpose
This document describes the installation, configuration, operation, and maintenance of PRIMECLUSTER Global Link Services (hereafter GLS).
Who should use this document
This document is intended for system administrators who are familiar with GLS operations and cluster control. Anyone who installs, configures, and maintains GLS to increase the availability of the system should read this documentation. A basic knowledge of PRIMECLUSTER is assumed.
Abstract
The document consists of the following chapters, appendices, and glossary:
This chapter explains the redundant line control function of GLS.
This chapter outlines the functions and features of GLS.
Chapter 3 Environment configuration
This chapter discusses how to set up and configure GLS.
This chapter explains how to operate the redundant line control function.
Chapter 5 GLS operation on cluster systems
This chapter explains how to operate the redundant line control on a cluster system.
This chapter focuses on a general approach to troubleshooting. It presents a troubleshooting strategy and identifies commands that are available in Resource Coordinator for finding and correcting problems. Further, it discusses how to collect troubleshooting information.
This chapter outlines GLS commands.
Appendix A Messages and corrective actions
This appendix outlines messages and corrective actions to be taken to eliminate errors.
Appendix B Examples of configuring system environments
This appendix explains how to configure the system environment with redundant network control.
Appendix C Changes from previous versions
This appendix discusses changes to the GLS specification. It also suggests some operational guidelines.
Appendix D Notice of supplemental information
This appendix provides supplemental information regarding GLS.
Related documentation
Please refer to the following documents according to need:
PRIMECLUSTER Installation and Administration Guide
Dynamic Reconfiguration (DR) User's Guide
Dynamic Reconfiguration (DR) User's Guide I/O device edition
PCI Hot Plug User's Guide
PCI Hot Plug User's Guide I/O device edition
Notational convention
The document conforms to the following notational conventions:
Point
Text that requires special attention
Note
Information that users should be cautious of
Information
Information that users can refer to
See
Manuals users find workable
- Oracle Solaris might be described as Solaris or Solaris Operating System.
- Oracle Solaris 8 is abbreviated as Solaris 8.
- Oracle Solaris 9 is abbreviated as Solaris 9.
- Oracle Solaris 10 is abbreviated as Solaris 10.
- Oracle Solaris Containers are abbreviated as Solaris Containers.
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.
Trademark
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.
Ethernet is a trademark of Fuji Xerox Corporation.
PRIMECLUSTER is a registered trademark of Fujitsu Limited.
Other product names that appear in this manual are product names, trademarks, or registered trademarks of respective companies.
Date of publication and edition
April 2015, 1.4 Edition |
High Risk Activity
This Product is designed, developed and manufactured as contemplated for general use, including without limitation, general office use, personal use, household use, and ordinary industrial use, but is not designed, developed and manufactured as contemplated for use accompanying fatal risks or dangers that, unless extremely high safety is secured, could lead directly to death, personal injury, severe physical damage or other loss (hereinafter "High Safety Required Use"), including without limitation, nuclear reaction control in nuclear facility, aircraft flight control, air traffic control, mass transport control, medical life support system, missile launch control in weapon system. You shall not use this Product without securing the sufficient safety required for the High Safety Required Use. If you wish to use this Product for High Safety Required Use, please consult with our sales representatives before such use.
Requests
No part of this document may be reproduced or copied without permission of FUJITSU LIMITED.
The contents of this document may be revised without prior notice.
All Rights Reserved, Copyright (C) FUJITSU LIMITED 2006-2015.
Revision | Location | Manual Code |
|---|---|---|
Deleted the descriptions for the hanetnic command. | 2.1.3.2 Switching function | J2S2-0340-01ENZ0(B) |
Added explanations about HUB monitoring function. | 2.2.7.2.3 Transfer path monitoring on individual virtual interface | |
Added descriptions for Service for Redundant Line Control function. | 2.2.12 User command execution function 3.6.11 Setting User command execution function | |
Added "Redundant line in LDoms environments" in the function column of the table. | 2.3 Other functions | |
Added "2.3.7 Redundant line in LDoms environments". | ||
Added a product provided with a DR function. | 2.3.2 DR (Dynamic Reconfiguration) linkage 4.5 Dynamic operation (Replacement / Expansion) | |
Added a product provided with a PHP function. | 2.3.3 PCI Hot Plug (PHP) linkage 4.5 Dynamic operation (Replacement / Expansion) | |
Added descriptions for shared-IP and exclusive-IP. | 2.3.6 Line control of Solaris container | |
Changed the title. | 2.3.6.1 Shared IP network high-reliability through redundant line control 3.2.1 Checking system resources C.5 Changes from Redundant Line control function 4.1A40 to version 4.2A00 | |
Added descriptions to notes. | 2.4.6 Duplicated operation via GS/SURE linkage mode 3.4.4 NIC switching mode 7.3 stphanet Command 7.14 hanethvrsc Command | |
Changed descriptions in notes. | 2.4.6 Duplicated operation via GS/SURE linkage mode 3.3.4 NIC switching mode 3.4.4 NIC switching mode | |
Added descriptions for checking the network configuration files of OS. | 3.2.2.1 Setup common to modes | |
Added descriptions for default gateway settings. | 3.2.4 Zone setup for Solaris container | |
Added descriptions for configuration methods about an exclusive-IP zone. | ||
Added "3.6.8.1 Transfer route error detection time in GS/SURE linkage mode" and "3.6.8.2 Transfer route recovery detection time in GS/SURE linkage mode". | 3.6.8 Monitoring the remote host | |
Added "3.6.11.3 Settings of the service for Redundant Line Control function". | 3.6.11 Setting User command execution function | |
Added an example how to list the setting file. | 3.7.2.1 Configure environment | |
Added descriptions for creation of the network configuration files. | ||
Added the description that the procedure is performed when PRIMEPOWER is used. | 4.5.2.1 Replacement of PCI card on redundant system 4.5.2.2 Extension of PCI cards with new redundant system 4.5.2.3 Extension of PCI cards to redundant system | |
Added "6.3 Packet Trace". | Chapter 6 Maintenance | |
Added packet traces as common troubleshooting information in each mode. | 6.1 Redundant Line Control function Troubleshooting Data to be Collected | |
Changed descriptions how to specify MAC addresses. | 7.1 hanetconfig Command | |
Added "A.2 Messages Displayed in the Cluster System Logs". | Appendix A Messages and corrective actions | |
Added the message number 224. | A.1.2 Messages Displayed in the Cluster System Logs (numbers 100 to 500) | |
Changed descriptions in the columns of Message and Action for message number 805. | A.1.3 Console output messages (numbers 800 to 900) | |
Added "B.6.7 Example of the Single system in an Exclusive IP-zone (Physical IP takeover)" and "B.6.8 Example of the Single system in LDoms environments (Physical IP takeover)" | B.6 Example of configuring NIC switching mode (IPv4) | |
Changed instructions of procedures and descriptions in notes. | B.6.13 Example of the Cluster system in Physical IP address takeover function II | |
Added descriptions for 4.0 to 4.1A40 in "Appendix C Changes from previous versions". | C.1 Changes from Redundant Control Line function 4.0 to version 4.1A10 C.2 Changes from Redundant Line Control function 4.1A10 to version 4.1A20 C.3 Changes from Redundant Line Control function 4.1A20 to version 4.1A30 C.4 Changes from Redundant Line Control function 4.1A30 to version 4.1A40 | |
Added "D.2.11 SMF service using the GLS virtual IP". | D.2 Trouble shooting | |
Added "D.2.2.7 Services of Redundant Line Control function cannot be started". | D.2.2 Virtual interface or the various functions of Redundant Line Control function cannot be used | |
Changed "GS/SURE linkage mode" in the table. | 2.3.6 Line control of Solaris container | J2S2-0340-01ENZ0(C) |
Changed descriptions in Information. | 2.3.6 Line control of Solaris container | |
Added descriptions in Information. | 2.3.6 Line control of Solaris container | |
Changed descriptions in Note. | 3.2.4 Zone setup for Solaris container | |
Changed a figure. | B.6.7 Example of the Single system in an Exclusive IP-zone (Physical IP takeover) | |
Added a procedure. | B.6.7 Example of the Single system in an Exclusive IP-zone (Physical IP takeover) | |
Added the description for switching a transfer path when a hang-up of the ping command was detected. | 2.2.7.1 Router monitoring function | J2S2-0340-01ENZ0(D) |
Added the script argument that is called from the user command execution function when a transfer path failure is detected. | 3.6.11.1 Settings for NIC switching mode | |
Added the message number: 931. | A.1.3 Console output messages (numbers 800 to 900) | |
Added the commands to collect materials. | 6.1.1 Command to collect materials | J2S2-0340-01ENZ0(E) |
Added the description for the on command. | 7.7 hanetpoll Command | |
Added the message numbers 982, 983, 984, 993, and 994. | A.1.3 Console output messages (numbers 800 to 900) | |
Added "D.2.2.8 Services of Redundant Line Control function cannot be started (when inconsistency of file system occurred)." | D.2.2 Virtual interface or the various functions of Redundant Line Control function cannot be used | |
Changed the title name. | D.2.2.7 Services of Redundant Line Control function cannot be started (when NIC failed) |
