primecluster™ for sap® business suite™manuals.ts.fujitsu.com/file/7901/o42144e6.pdf ·...

PRIMECLUSTER™ for SAP® Business Suite™ Installation Guide (Linux®)

Edition June 2009

Comments… Suggestions… Corrections…The User Documentation Department would like toknow your opinion of this manual. Your feedback helpsus optimize our documentation to suit your individual needs.

Feel free to send us your comments by e-mail to [email protected].

Certified documentation according to DIN EN ISO 9001:2000To ensure a consistently high quality standard anduser-friendliness, this documentation was created tomeet the regulations of a quality management system which complies with the requirements of the standardDIN EN ISO 9001:2000.

cognitas. Gesellschaft für Technik-Dokumentation mbHwww.cognitas.de

Copyright and Trademarks

© c

ogn

itas.

Ges

ells

chft

für

Tech

nik-

Dok

um

enta

tion

mbH

200

2 th

roug

h 20

09

Pfa

d: D

:\Dat

en\P

CL\

4.2A

20L

x\u4

214

4.6\

e\In

sta

llSA

P\I

nsta

llSA

P.vo

r

Copyright © 2002 through 2009 Fujitsu LIMITED.

All rights reserved.Delivery subject to availability; right of technical modifications reserved.

All hardware and software names used are trademarks of their respective manufacturers.

http://www.cognitas.de

mailto:[email protected]

mailto:[email protected]

U42144-J-Z100-6-76

Contents

1 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1.1 Contents of this manual . . . . . . . . . . . . . . . . . . . . . 9

1.2 PRIMECLUSTER documentation . . . . . . . . . . . . . . . 10

1.3 Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . 111.3.1 Notation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.3.1.1 Prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.3.1.2 Manual page section numbers . . . . . . . . . . . . . . . . 121.3.1.3 The keyboard . . . . . . . . . . . . . . . . . . . . . . . . . 121.3.1.4 Typefaces . . . . . . . . . . . . . . . . . . . . . . . . . . 121.3.1.5 Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . 131.3.1.6 Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . 131.3.2 Command syntax . . . . . . . . . . . . . . . . . . . . . . . . 13

1.4 Notation symbols . . . . . . . . . . . . . . . . . . . . . . . . 14

2 Site planning . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2.1 Planning your site . . . . . . . . . . . . . . . . . . . . . . . 152.1.1 Cluster configuration information . . . . . . . . . . . . . . . . 17

2.2 Disk space requirements . . . . . . . . . . . . . . . . . . . 19

2.3 Pre-installation configuration steps . . . . . . . . . . . . . 20

2.4 Time synchronization . . . . . . . . . . . . . . . . . . . . . 23

2.5 Browser environments . . . . . . . . . . . . . . . . . . . . . 23

2.6 Configuring user groups . . . . . . . . . . . . . . . . . . . . 24

3 Installation with CLI . . . . . . . . . . . . . . . . . . . . . . 27

3.1 Product set installation . . . . . . . . . . . . . . . . . . . . 27

3.2 Installation on an external management server . . . . . . . 29

U42144-J-Z100-6-76

Contents

© c

ogni

tas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH

20

02 th

rou

gh 2

007

P

fad:

D:\D

ate

n\P

CL

\4.2

A20

Lx\

u42

144

.6\e

\Inst

allS

AP

\Inst

allS

AP.

ivz

4 External management servers . . . . . . . . . . . . . . . . . 31

4.1 Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

4.2 Hardware and software requirements . . . . . . . . . . . . . 32

4.3 Package list . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

4.4 Installation procedure . . . . . . . . . . . . . . . . . . . . . . 33

4.5 Uninstall procedure . . . . . . . . . . . . . . . . . . . . . . . 34

5 Web-Based Admin View configuration . . . . . . . . . . . . . 35

5.1 Web-Based Admin View Concepts . . . . . . . . . . . . . . . 35

5.2 Updating /etc/hosts . . . . . . . . . . . . . . . . . . . . . . . 36

5.3 Using wvconf . . . . . . . . . . . . . . . . . . . . . . . . . . 36

5.4 wvconf example . . . . . . . . . . . . . . . . . . . . . . . . . 38

5.5 Checking the configuration . . . . . . . . . . . . . . . . . . . 425.5.1 Checking the configuration using the CLI . . . . . . . . . . . . . 425.5.2 Checking the configuration using the GUI . . . . . . . . . . . . 43

5.6 Save and restore . . . . . . . . . . . . . . . . . . . . . . . . . 495.6.1 Saving the configuration . . . . . . . . . . . . . . . . . . . . . 495.6.2 Restoring the configuration . . . . . . . . . . . . . . . . . . . . 49

6 Installation example . . . . . . . . . . . . . . . . . . . . . . . 51

6.1 Network setup . . . . . . . . . . . . . . . . . . . . . . . . . . 536.1.1 Verifying the cluster interconnect networks . . . . . . . . . . . . 54

6.2 Java environment . . . . . . . . . . . . . . . . . . . . . . . . 54

6.3 Installing the cluster nodes . . . . . . . . . . . . . . . . . . . 54

6.4 PRIMECLUSTER software configuration . . . . . . . . . . . 556.4.1 Web-Based Admin View example . . . . . . . . . . . . . . . . 556.4.2 Signed applets . . . . . . . . . . . . . . . . . . . . . . . . . . 596.4.3 SF example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596.4.4 PCS example . . . . . . . . . . . . . . . . . . . . . . . . . . . 746.4.4.1 Starting PCS . . . . . . . . . . . . . . . . . . . . . . . . . 756.4.4.2 Selecting a node for the PCS session . . . . . . . . . . . . . 766.4.4.3 Creating a new configuration . . . . . . . . . . . . . . . . . 77

U42144-J-Z100-6-76

Contents

6.4.4.4 Selecting nodes . . . . . . . . . . . . . . . . . . . . . . . 786.4.4.5 Viewing the configuration tree . . . . . . . . . . . . . . . . 806.4.4.6 Choosing the application template . . . . . . . . . . . . . . 806.4.4.7 Changing the application name . . . . . . . . . . . . . . . 826.4.4.8 Viewing template information . . . . . . . . . . . . . . . . 836.4.4.9 Selecting nodes for the application . . . . . . . . . . . . . . 846.4.4.10 Setting application parameters . . . . . . . . . . . . . . . . 856.4.4.11 Configuring a subapplication . . . . . . . . . . . . . . . . . 866.4.4.12 Checking application consistency . . . . . . . . . . . . . . 906.4.4.13 Saving the configuration . . . . . . . . . . . . . . . . . . . 916.4.4.14 Activating the configuration . . . . . . . . . . . . . . . . . 91

7 PRIMECLUSTER upgrade . . . . . . . . . . . . . . . . . . . 93

7.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

7.2 Cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

7.3 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . 957.3.1 Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 957.3.2 Upgrade preparation . . . . . . . . . . . . . . . . . . . . . . . 977.3.2.1 Install patches . . . . . . . . . . . . . . . . . . . . . . . . 977.3.2.2 Decide the node upgrade order . . . . . . . . . . . . . . . 977.3.2.3 Save Web-Based Admin View configuration file . . . . . . . 98

7.4 Performing the rolling upgrade . . . . . . . . . . . . . . . . 987.4.1 Switching RMS applications . . . . . . . . . . . . . . . . . . . 997.4.2 Shutdown node A . . . . . . . . . . . . . . . . . . . . . . . . 1007.4.3 Upgrading the software on node A . . . . . . . . . . . . . . . 1017.4.3.1 Manually removing PRIMECLUSTER packages . . . . . . . 1017.4.3.2 Removing the remaining old PRIMECLUSTER packages . . 1027.4.3.3 Verify supported OS level . . . . . . . . . . . . . . . . . . 1037.4.3.4 Installing new PRIMECLUSTER packages . . . . . . . . . 1037.4.4 Joining node A back to the cluster . . . . . . . . . . . . . . . . 1037.4.5 Upgrading the next node . . . . . . . . . . . . . . . . . . . . . 104

7.5 Post-installation . . . . . . . . . . . . . . . . . . . . . . . . 1057.5.1 Restoring Web-Based Admin View configuration . . . . . . . . 1057.5.2 Configuring the new RMS version . . . . . . . . . . . . . . . . 106

7.6 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

U42144-J-Z100-6-76

Contents

© c

ogni

tas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH

20

02 th

rou

gh 2

007

P

fad:

D:\D

ate

n\P

CL

\4.2

A20

Lx\

u42

144

.6\e

\Inst

allS

AP

\Inst

allS

AP.

ivz

8 Manual pages . . . . . . . . . . . . . . . . . . . . . . . . . 113

8.1 Monitoring Agent . . . . . . . . . . . . . . . . . . . . . . . 113

8.2 PCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

8.3 RMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

8.4 RMS Wizards . . . . . . . . . . . . . . . . . . . . . . . . . . 115

8.5 SF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

8.6 Web-Based Admin View . . . . . . . . . . . . . . . . . . . . 116

9 Appendix—Important Web-Based Admin View settings . . 117

10 Appendix—Private network addresses . . . . . . . . . . . 119

11 Appendix—Cluster planning worksheet . . . . . . . . . . . 121

12 Appendix—System parameters . . . . . . . . . . . . . . . 123

12.1 System parameters for RMS configurations . . . . . . . . . 123

13 Appendix—PRIMECLUSTER ports . . . . . . . . . . . . . . 125

14 Appendix—Troubleshooting . . . . . . . . . . . . . . . . . 129

14.1 cluster_install log files . . . . . . . . . . . . . . . . . . . . 129

14.2 cluster_install error messages . . . . . . . . . . . . . . . . 129

14.3 cluster_uninstall error messages . . . . . . . . . . . . . . 133

U42144-J-Z100-6-76

Contents

Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

© c

ogni

tas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH

20

02 th

rou

gh 2

007

P

fad:

D:\D

ate

n\P

CL

\4.2

A20

Lx\

u42

144

.6\e

\Inst

allS

AP

\Inst

allS

AP.

ivz

U42144-J-Z100-6-76 9

1 PrefaceThis guide provides instructions for installing the PRIMECLUSTER suite of products. The primary audience for this guide is the system administrator. This guide assumes that the reader is familiar with the PRIMECLUSTER Concepts Guide and assumes that the hardware has been installed according to the appropriate hardware installation manuals.

This version of PRIMECLUSTER includes the following components:

● Reliant Monitor Services (RMS) 4.2A20

● Wizard Tools (WT) 4.2A20

● PRIMECLUSTER Configuration Services (PCS) 4.2A20

In this manual, Linux stands for the supported Linux distributions as follows:

● Novell SUSE

● Red Hat

I Refer to the release note for versions of the supported distributions of Linux.

1.1 Contents of this manual

This manual is organized as follows:

● The chapter “Site planning” provides hardware and software information for planning your site.

● The chapter “Installation with CLI” provides information on installing the PRIMECLUSTER products by means of the command line interface (CLI) installer.

● The chapter “External management servers” describes how to install Web-Based Admin View software and related GUIs on the management server when the server is a node outside of the cluster.

● The chapter “Web-Based Admin View configuration” details the wvconf command to configure the PRIMECLUSTER GUI.

● The chapter “Installation example” provides a step-by-step example of installing, configuring and starting a sample two-node cluster configuration.

10 U42144-J-Z100-6-76

PRIMECLUSTER documentation Preface

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k01

● The chapter “PRIMECLUSTER upgrade” describes the rolling upgrade process.

● The chapter “Manual pages” contains a listing of PRIMECLUSTER manual pages.

● The chapter “Appendix—Important Web-Based Admin View settings” describes useful Web-Based Admin settings.

● The chapter “Appendix—Private network addresses” defines three address ranges that are set aside for private subnets.

● The chapter “Appendix—Cluster planning worksheet” provides a blank cluster planning worksheet.

● The chapter “Appendix—System parameters” discusses setting system parameters for RMS configurations.

● The chapter “Appendix—PRIMECLUSTER ports” lists the ports used by PRIMECLUSTER.

● The chapter “Appendix—Troubleshooting” provides cluster_install trouble-shooting details and error messages.

1.2 PRIMECLUSTER documentation

The documents listed below provide details about PRIMECLUSTER products. Books can be ordered via the Internet shop http://manualshop.ts.fujitsu.com.

● Release notices for all products—These documentation files are included as HTML files on the PRIMECLUSTER CD. Release notices provide late-breaking information about installation, configuration, and operations for PRIMECLUSTER. Read this information first.

● Concepts Guide (Solaris, Linux)—Provides conceptual details on the PRIMECLUSTER family of products.

● Installation Guide (Linux)—Provides instructions for installing and upgrading PRIMECLUSTER products on Linux.

● PRIMECLUSTER for SAP Business Suite (Linux) Installation Guide—Provides instructions for installing PRIMECLUSTER for SAP Business Suite on Linux.

U42144-J-Z100-6-76 11

Preface Conventions

● PRIMECLUSTER for SAP Business Suite Shutdown Facility (SF) (Linux) Configuration and Administration Guide—Provides instructions for configuring, administering and troubleshooting the PRIMECLUSTER for SAP Business Suite Shutdown Facility.

● PRIMECLUSTER for SAP Business Suite Reliant Monitor Services (RMS) with PCS (Linux) Configuration and Administration Guide—Provides instructions for configuring and administering PRIMECLUSTER for SAP Business Suite Reliant Monitor Services using the PCS (PRIMECLUSTER Configuration Services) interface

● PRIMECLUSTER for SAP Business Suite Reliant Monitor Services (RMS) with Wizard Tools (Linux) Configuration and Administration Guide—Provides instruc-tions for configuring and administering PRIMECLUSTER for SAP Business Suite Reliant Monitor Services using the Wizard Tools interface

● Reliant Monitor Services (RMS) (Solaris, Linux) Reference Guide—Describes diagnostic procedures to solve RMS configuration problems, including how to view and interpret RMS log files. Provides a list of all RMS error messages with a probable cause and suggested action for each condition.

1.3 Conventions

In order to standardize the presentation of material, this manual uses a number of notational, typographical, and syntactical conventions.

1.3.1 Notation

This manual uses the following notational conventions.

1.3.1.1 Prompts

Command line examples that require system administrator (or root) privileges 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 some examples, the notation node# indicates a root prompt on the specified node. For example, a command preceded by shasta2# would mean that the command was run as user root on the node named shasta2.

12 U42144-J-Z100-6-76

Conventions Preface

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k01

1.3.1.2 Manual page section numbers

References to operating system commands may sometimes be followed by their manual page section numbers in parentheses, e.g., cp(1).

1.3.1.3 The keyboard

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.

1.3.1.4 Typefaces

The following typefaces highlight specific elements in this manual.

Typeface conventions are shown in the following examples.

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 in a command line that you must replace with an actual value. May be enclosed in angle brackets to emphasize the difference from adjacent text; for example, <nodename>RMS; unless directed otherwise, you should not enter the angle brackets.

The name of an item in a character-based or graphical user interface. This may refer to a menu item, a radio button, a checkbox, a text input box, a panel, or a window title.

Bold Items in a command line that you must type exactly as shown.

U42144-J-Z100-6-76 13

Preface Conventions

1.3.1.5 Example 1

As an example, several entries from an /etc/passwd file are shown below:

sysadm:x:0:0:System Admin.:/usr/admin:/usr/sbin/sysadmsetup:x:0:0:System Setup:/usr/admin:/usr/sbin/setupdaemon:x:1:1:0000-Admin(0000):/:

1.3.1.6 Example 2

To use the cat command to display the contents of a file, enter the following command line:

$ cat file

1.3.2 Command syntax

The command syntax observes the following conventions.

Symbol Name Meaning

[ ] Brackets Enclose an optional item.

{ } Braces Enclose two or more items of which only one is used. The items are separated from each other by a vertical bar (|).

| Vertical bar When enclosed in braces, it separates items of which only one is used. When not enclosed in braces, it is a literal element indicating that the output of one program is piped to the input of another.

( ) Parentheses Enclose items that must be grouped together when repeated.

... Ellipsis Signifies an item that may be repeated. If a group of items can be repeated, the group is enclosed in parentheses.

14 U42144-J-Z100-6-76

Notation symbols Preface

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k01

1.4 Notation symbols

Material of particular interest is preceded by the following symbols in this manual:

I Contains important information about the subject at hand.

V Caution

Indicates a situation that can cause harm to data.

U42144-J-Z100-6-76 15

2 Site planningThis chapter provides information for planning your site. Both hardware and software planning are discussed.

This chapter discusses the following:

● The section “Planning your site” describes a generic hardware configuration.

● The section “Disk space requirements” lists the space requirements for PRIMECLUSTER products and packages.

● The section “Pre-installation configuration steps” provides a list of additional steps to perform before starting the installation of PRIMECLUSTER.

● The section “Time synchronization” recommends the use of time synchroni-zation to analyze problems in a clustered environment.

● The section “Browser environments” discusses the environments supported by the Web-Based Admin View browser.

● The section “Configuring user groups” discusses configuring user groups with the Web-Based Admin View browser.

2.1 Planning your site

The configuration shown in figure 1 is a typical example of a two-node cluster. The major components of interest are as follows:

● Cluster interconnects—These are Ethernet networks dedicated to the cluster’s use.

● System administration network—This is the network that is used for admin-istrative purposes. It is often a private network for security reasons. However, a public network may also be used.

● Cluster nodes—These are the nodes bound together in a cluster and running the PRIMECLUSTER software.

16 U42144-J-Z100-6-76

Planning your site Site planning

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k02

In addition to the cluster interconnects and system administration network, each cluster node should also have an interface on a public network. For the sake of simplicity, the public network for each node is not shown in figure 1.

Figure 1: PRIMECLUSTER hardware configuration without a console

In figure 1, the power switch is a Network Power Switch (NPS) or Remote Power Switch (RPS). The power plugs of the cluster nodes are inserted into the power switch so that the Shutdown Facility (SF) can eliminate the nodes to resolve split-cluster situations.

If you are using PRIMERGY servers from Fujitsu Technology Solutions, then you may not need the power switch. PRIMERGY BX300 BLADE servers have SNMP accessible management stations that SF can use to eliminate the nodes. PRIMERGY servers with the Intelligent Platform Management Interface (IPMI) can be shut down by SF without using an external power switch.

This guide assumes that the hardware has been installed according to the appropriate hardware installation manuals. Be sure to review the PRIME-CLUSTER Concepts Guide (Solaris, Linux) section on cluster interconnect

Shared

DiskCluster Node

Shared DiskConnection

Cluster Node

System Administration Network(Public or Private)

Cluster Interconnect

Note: The power switch con-nection provides a method for eliminating a cluster node.

Power Line

Node-1 Node-2

Power Switch

Power Line

U42144-J-Z100-6-76 17

Site planning Planning your site

requirements and all release notices to ensure that the cluster interconnect hardware is appropriate (refer to the section “PRIMECLUSTER documentation” for details).

2.1.1 Cluster configuration information

A PRIMECLUSTER for SAP® Business Suite™ configuration requires three or four TCP/IP networks such as the following:

● Public network

● Cluster interconnect consisting of two IP networks

● Optional administrative network

You will need to assign IP addresses and host names for each of the nodes on each of these networks. The worksheet in table 1 should be used as an aid to complete this configuration in an orderly fashion. chapter “Appendix—Cluster planning worksheet” contains a blank worksheet.

Cluster Name SHASTAS

Node 1 Node 2

Node Name shasta1 shasta2


Primary RMS network

Name shasta1RMS shasta2RMS

Address 192.168.1.1 192.168.1.2

AlternateIP RMS networks

Name shasta1rmsAI_0 shasta2rmsAI_0

Address 192.168.2.1 192.168.2.2

Name

Address

Administrative LAN

Name shasta1ADM shasta2ADM

Address 172.25.200.4 172.25.200.5

Public LAN

Name shasta1 shasta2

Address 172.25.222.105 172.25.222.112

Table 1: Cluster site planning worksheet

18 U42144-J-Z100-6-76

Planning your site Site planning

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k02

The cluster interconnect consists of a Primary RMS network and an AlternateIP RMS network. By convention, the names on the Primary RMS network should be the node name with the string RMS attached. In the RMS configuration, the nodeRMS names should be used for the SysNode names.

In normal operation, all RMS communications are carried over the Primary RMS network. However, if a failure occurs on this network, then RMS uses the Alter-nateIP network or networks instead. Each RMS SysNode object should have one or more AlternateIP names defined for it.

I Refer to the PRIMECLUSTER for SAP Business Suite Reliant Monitor Services (RMS) with PCS (Linux) Configuration and Administration Guide or the PRIMECLUSTER for SAP Business Suite Reliant Monitor Services (RMS) with Wizard Tools (Linux) Configuration and Administration Guide for more details on how to configure RMS.

You should ensure that the Primary RMS network and the AlternateIP RMS network or networks use different physical devices on each node. Otherwise, a single device failure could prevent a node from accessing either network.

By convention, names on AlternateIP networks are the node name followed by the string rmsAI_n, where n is an integer (for example 0, 1, 2, and so on).

You should use private IP addresses for the interconnect networks.

The administrative LAN is optional. The recommended naming convention for interfaces on the Administrative LAN is the node name followed by the string ADM. You should use a private IP address for the administrative LAN.

U42144-J-Z100-6-76 19

Site planning Disk space requirements

2.2 Disk space requirements

table 2 lists the approximate space requirements for PRIMECLUSTER products and packages.

Category Package Disk Space in MBs Total in MBs

Shutdown Facility (SF) SMAWskelSMAWsf

.02

.50 .52

Base GUIs FJSVwvbsFJSVwvmpcSMAWrcadm SMAWrcajaSMAWcj2re

3.5 4.5 4.1 .06 20

32.2

Reliant Monitor Services (RMS)

SMAWRrmsSMAWRdfw

3.6 .13

3.7

PCS Wizard Tools SMAWpcsSMAWpcsde

17.7 .90

18.6

PCS Wizard Kit SMAWpcsdbSMAWpcsr3

.98

.10 1.08

HV Wizard Tools SMAWRhv-baSMAWRhv-doSMAWRhv-to

.37 1.4 .50

2.27

HV Wizard Kit SMAWRhv-r3SMAWRhv-db

.35

.25 .6

Table 2: Disk space requirements by category

20 U42144-J-Z100-6-76

Pre-installation configuration steps Site planning

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k02

table 3 lists disk space requirements for installing PRIMECLUSTER Enterprise Edition with default mode.

2.3 Pre-installation configuration steps

At this point, it is assumed that all of the hardware is installed and the intercon-nects are functioning. The following are additional steps to perform before starting the installation of PRIMECLUSTER:

1. To prevent a computer from shutting down, configure the computer in such a way that power management is not active. Power management can be configured in the following places:

– BIOS setup

– Kernel parameters

– Boot options

I Refer to the appropriate software and hardware documentation for disabling power management for your system.

2. Before installing any of the PRIMECLUSTER packages, ensure that the Linux kernel sources (as appropriate) are installed on the machines. The kernel sources would be installed under the /lib/modules/`uname -r`/build/ directory. (This directory is usually a symbolic link to the /usr/src/linux directory). Please refer to the appro-priate Linux documentation to install the kernel sources.

3. Ensure that the hosts entry in /etc/nsswitch.conf lists the files criteria before any other.

File system Mount point Disk space in MBs

root file system / 7.6

usr file system /usr 17.1

var file system /var 4.0 1

1 This number is for initial installation. The actual number for operation is much higher because this is where the log files are stored.

opt file system /opt 60.2

Table 3: Space requirements for PRIMECLUSTER Enterprise Edition

U42144-J-Z100-6-76 21

Site planning Pre-installation configuration steps

The hosts entry is used to determine which services are used for TCP/IP name look-ups, and also determines the order in which the services are tried. For example, name look-up may be done via files (/etc/hosts), nis, and dns.

Also ensure that the order entry in /etc/host.conf lists the hosts criteria before any other.

It is required that cluster node names (and any additional host names needed by RMS) be entered in the /etc/hosts file on all nodes in the cluster.

Putting cluster interconnect names in the /etc/hosts file is important for two reasons:

– Cluster interconnect names should be configured with non-routable IP addresses, so limiting knowledge of them to the cluster is reasonable.

– If DNS is used for the names, DNS and the public network interfaces to the DNS server are potentially single points of failure.

However, the default hosts entry in /etc/nsswitch.conf might not be set up to normally look in the /etc/hosts file. For example, the following entry will only look in the /etc/hosts file if NIS is not available:

hosts: nis [NOTFOUND=return] files

Thus, /etc/nsswitch.conf needs to be changed so that the files entry comes before any other. For the above example to work properly with PRIMECLUSTER, it should be changed to the following:

hosts: files nis

See the nsswitch.conf(5) and host.conf(5) manual pages for more details.

4. In the /etc/hosts file, the local host name may be in the loop back IP address line. This will cause the Web-Based Admin View server to fail to start. Therefore, you must modify the file. For example, 172.25.222.105 is the actual IP address for a node named shasta1, and the /etc/hosts file appears similar to the following:

# Do not remove the following line, or various programs# that require network functionality will fail127.0.0.1 shasta1 localhost.localdomain localhost

22 U42144-J-Z100-6-76

Pre-installation configuration steps Site planning

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k02

This must be changed as follows:

# Do not remove the following line, or various programs# that require network functionality will fail127.0.0.1 localhost.localdomain localhost172.25.222.105 shasta1

5. Edit the /etc/hosts file with a text editor to include all of the nodes in your cluster. The following is a basic example of an edited hosts file:

## hosts This file describes a number of hostname-to-address# mappings for the TCP/IP subsystem. It is mostly# used at boot time, when no name servers are running.# On small systems, this file can be used instead of a# "named" name server.# Syntax:## IP-Address Full-Qualified-Hostname Short-Hostname#127.0.0.1 localhost172.25.222.105 shasta1.usa.fts.net shasta1172.25.222.112 shasta2.usa.fts.net shasta2

6. Enable the echo service for RMS heartbeats as follows:

– For SLES 8, edit the /etc/inetd.conf file and uncomment the entry for tcp echo service. Restart with the following command:

# /etc/init.d/inetd reload

– For RedHat and SLES 9, edit the /etc/xinetd.d/echo file and change the disable field to no. Restart with the following command:

# /etc/init.d/xinetd restart

7. PRIMECLUSTER needs to execute remote command and copy files to remote locations. Standard remote commands allow limitation of access to certain hosts and users only, but do not use encryption of the transferred data.

I The default installations of Linux install a firewall. The use of these firewalls in combination with PRIMECLUSTER has not been tested and is not supported.

To use the remote commands, they need to be installed on the system. The remote commands are installed with the RPM rsh-server. After this package has been installed on the system, ensure that the services are started appropriately.

U42144-J-Z100-6-76 23

Site planning Time synchronization

8. For RMS, you need to setup remote access so that it can function without using a password. This is done by making entries in the /root/.rhost file. For details on how to setup these entries, refer to the rhost(5) manual page.

2.4 Time synchronization

To analyze problems in a clustered environment, you need to compare log files on each node in the cluster. To understand a problem, you will have to correlate events on one node in relation to the events on the other nodes. To put the events in the cluster in order, you normally would use the time stamp of the messages. Sorting by time stamp requires that the clocks on the cluster nodes do not differ considerably. To keep the clocks in synchronization, the use of time synchronization is recommended.

Please refer to the appropriate Linux Administration Guide to setup and analyze time synchronization.

2.5 Browser environments

I The Web-Based Admin View GUIs, such as Cluster Admin, run Java applets in a client's browser. Refer to the Base_GUIs Release Notice on the PRIMECLUSTER CD for information on the supported Java, browser, and Linux versions (refer to the section “PRIMECLUSTER documentation” for more details). The Release Notice also contains important configuration information for supported browsers. For the Java applet to run properly, you may need to configure your browser accord-ingly.

The following client environments are supported:

● Linux:

– Color monitor.

– The supported window managers are KDE or gnome.

– The correct Java plugin version should be used. This plugin is included on the PRIMECLUSTER CD.

● Microsoft Windows 98, 98 SE, ME, NT, 2000, or XP:

– Color monitor.

24 U42144-J-Z100-6-76

Configuring user groups Site planning

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k02

– 16 or 32 bit color configured for the display; the display should not be configured for 24 bit color.

– At least 256 MB main memory.

– At least a 500 MHz Pentium II CPU.

– Only Netscape or Internet Explorer can be used.

– The correct Java plugin version should be used. This plugin is included on the PRIMECLUSTER CD.

2.6 Configuring user groups

An important part of PRIMECLUSTER configuration involves setting up Web-Based Admin View (refer to the chapter “Web-Based Admin View configu-ration”). Web-Based Admin View uses user groups on the management servers to control the privileges a user is allowed when running a particular operation management GUI.

The groups used by the various operation management GUIs that are part of PRIMECLUSTER are given in table 4. The privileges listed in table 4 apply only for these GUIs, and not for any command line executions.

GUI Name Unix Group Name

Privilege

All GUIs wvroot Root privilege. Can do all operations.

Cluster Admin clroot Root privilege. Can do configuration, run administrative commands, and display information

cladmin Administrator privilege. Cannot do configuration. Can run administrative commands and display information.

clmon Operator privilege. Cannot do configuration. Cannot run adminis-trative commands. Can only display information.

Global Disk Services sdxroot Root privileges.

Table 4: GUI user groups

U42144-J-Z100-6-76 25

Site planning Configuring user groups

wvroot is a special group. It is used by the Web-Based Admin View framework itself. Users in the group are given the highest privilege level in Web-Based Admin View and all operation management GUIs.

The operation management GUIs define their own groups as shown in table 4. Using different groups allows system administrators to grant different privilege levels to different users depending on the product they need to access. For example, if a user were in the group clroot but not sdxroot, then that user would have full privileges when running Cluster Admin, but would have no privi-leges running the GUI for Global Disk Services.

You create the above UNIX groups as needed on each system, and you run the Web-Based Admin View on the primary and secondary management servers. You should assign users to these groups as required for your site. Group membership for Web-Based Admin View related groups should be consistent across all management servers associated with a particular cluster.

The root user on a management server is granted maximum privileges regardless of the groups to which root belongs.

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k02

U42144-J-Z100-6-76 27

3 Installation with CLIThis chapter provides information on installing the PRIMECLUSTER products by means of the command line interface (CLI) installer.


● The section “Product set installation” describes how to use the cluster_install command with product groups.

● The section “Installation on an external management server” gives infor-mation on installing PRIMECLUSTER products in a three-tiered archi-tecture.

3.1 Product set installation

The cluster_install command helps users to install PRIMECLUSTER by specifying the name of a product set. This command is used only for initial installation and is supported for non-interactive installation. Refer to the section “Package list” for details on the additional installation of a single product.

Perform the steps below to execute the cluster_install command:

1. Install the PRIMECLUSTER products for SAP® Business Suite™ with the following commands:

# cd <CD1>/Tool

# ./cluster_install -e product_set

In this example, <CD1> is the CD-ROM mountpoint for CD1.

28 U42144-J-Z100-6-76

Product set installation Installation with CLI

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k06

Specify a value for product_set, referring to table 5.

I Once you install the PRIMECLUSTER for SAP® Business Suite™ product set, you cannot install any other PRIMECLUSTER products.

I The cluster_install -e SAP command only installs the PRIME-CLUSTER components for SAP on Linux. It does not install SAP itself.

2. To install Wizards, use the following commands:

# cd <CD1>/Tool

# ./cluster_install -p product_code

The product_code for a particular Wizard is given in table 6.

For example, to install the PCS Oracle Wizard, use the following commands:

# cd <CD1>/Tool

# ./cluster_install -p PKDB

Product set cluster_install product set

PRIMECLUSTER for SAP® Business Suite™ with PCS Wizards

SAP

PRIMECLUSTER for SAP® Business Suite™ with RMS Wizard Tools

SAP_WT

PRIMECLUSTER for SAP® Business Suite™ for a SIS satellite node

SAPSAT

Table 5: Product sets

product_code Description

PKDB PCS Database Wizard

PKR3 PCS SAP R3 Wizard

WKDB RMS Wizard Tools Database Wizard

WKR3 RMS Wizard Tools SAP R3 Wizard

Table 6: PCS Wizard product codes

U42144-J-Z100-6-76 29

Installation with CLI Installation on an external management server

The installation is performed automatically and does not require user inter-action. Processing has proceeded normally when the following message appears:

The installation finished successfully.

This completes the installation of CD1.

3. Once the installation completes normally, reboot the system as follows:

# /sbin/shutdown -t0 -r now

3.2 Installation on an external management server

Web-Based Admin View can be installed on a node outside of the cluster that it manages. In this case, the node would be called an external management server. Refer to the chapter “External management servers” for details about installation on the management server of Web-Based Admin View, and refer to the PRIMECLUSTER Web-Based Admin View Operation Guide for explanations of external management servers and the Web-Based Admin View three-tiered architecture.

I The installation method and packages of Web-Based Admin View for the management server are different than those for the cluster node.

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k06

U42144-J-Z100-6-76 31

4 External management serversThis Chapter describes how to install Web-Based Admin View software and related GUIs on the management server when the server is a node outside of the cluster. This type of management server is referred to as an external management server.

The Chapter discusses the following:

● The section “Benefits” lists the advantages of having the management server outside of the cluster.

● The section “Hardware and software requirements” details the external management server hardware requirements.

● The section “Package list” lists the packages for the external management server.

● The section “Installation procedure” describes the procedure for installing the external management server.

● section “Uninstall procedure” specifies the procedure for uninstalling the packages for the external management server.

4.1 Benefits

Using an external management server offers the following benefits:

● Even when the cluster node is down, the management server keeps running so that the central management of the large-scale PRIMECLUSTER system can be continuously assured.

● The management server overhead is off-loaded from the cluster node.

The software for Web-Based Admin View and the operation management GUIs needs to be installed on the server nodes. No other PRIMECLUSTER software should be installed on an external management server node. No additional license is required to install Web-Based Admin View and related GUIs on an external server.

32 U42144-J-Z100-6-76

Hardware and software requirements External management servers

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k07

4.2 Hardware and software requirements

The management server must be a Linux system with 128 MB or more of memory.

4.3 Package list

table 7 lists all of the packages on the CD that can be installed on the external management server along with the installation names that they are grouped under. You should always install the following:

● PCLsnap—collects troubleshooting information.

● Base_GUIs—includes the Web-Based Admin View packages and the Cluster Admin packages, which are required for all cluster configurations.

● CCBR—contains the Cluster Configuration Backup and Restore.

The other GUI packages control optional software products. If you are not using a particular product, then you do not have to install its GUI.

clu

ster

_in

stal

l co

de

Inst

alla

tio

nO

rder

Pac

kag

en

ame

Ver

sio

n

Des

crip

tio

n

PCLsnap 1 FJSVpclsnap 4.1.4 System information output

HVKSH 2 SMAWhvksh 4.2A20 Used by products that require ksh

Table 7: Packages for an external server

U42144-J-Z100-6-76 33

External management servers Installation procedure

4.4 Installation procedure

The following is the procedure for installing the packages for an external management server:

1. Log in to the external management server as root.

Base_GUIs 3

4

56

7

FJSVwvbs

FJSVwvmpc

SMAWrcadmSMAWrcaja

SMAWcj2re

4.1.4

4.1.4

4.2A204.2A20

Web-Based Admin ViewMenu function for PRIMECLUSTER IN Web-Based Admin View Cluster AdminJapanese translation for Cluster Admin1

Java JRE

CCBR 8 SMAWccbr 4.2A20 Cluster ConfigurationBackup/Restore

1 The SMAWrcaja package provides Japanese translations for Cluster Admin. This package is only necessary if Cluster Admin is to be displayed in the Japanese language.

clu

ster

_in

stal

l co

de

Inst

alla

tio

nO

rder

Pac

kag

en

ame

Ver

sio

n

Des

crip

tio

n

Table 7: Packages for an external server

34 U42144-J-Z100-6-76

Uninstall procedure External management servers

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k07

2. Load and mount CD1 into the CD-ROM drive, and install all packages (refer to table 7) as follows:

# cd <CD1>/Tool

# ./cluster_install -p PCLsnap

# ./cluster_install -p HVKSH

# ./cluster_install -p Base_GUIs

In this example, <CD1> is the CD-ROM mountpoint.

3. Install all the packages in the CCBR category as follows:

# cd <CD1>/Tool

# ./cluster_install -p CCBR

4.5 Uninstall procedure

Perform the following steps to uninstall the PRIMECLUSTER packages on the external management server:

1. Stop all administrative activities on the external management server.

2. Log in to the external management server as root.

3. Remove all the packages as follows:

# cd <CD1>/Tool

# ./cluster_uninstall

Reply to the interactive dialog by entering the letter y to proceed.

The cluster_uninstall removal of PRIMECLUSTER packages is complete when the following message is output:

cluster_uninstall was successful

I cluster_uninstall could fail to remove a package if there is a dependant package that was not installed by cluster_install. The solution to this problem is to uninstall the package with the dependency and then re-execute the ./cluster_uninstall command.

U42144-J-Z100-6-76 35

5 Web-Based Admin View configuration

The PRIMECLUSTER GUIs require that you configure Web-Based Admin View before you can use them. The wvconf command is used to configure Web-Based Admin View on all of the nodes at the same time. Before configuring Web-Based Admin View, you must first install the Base GUIs product from CD1.


● The section “Web-Based Admin View Concepts” introduces basic Web-Based Admin View concepts.

● The section “Updating /etc/hosts” reminds you to update the /etc/hosts file.

● The section “Using wvconf” describes how to use the wvconf command.

● The section “wvconf example” shows an example of using the wvconf command.

● The section “Checking the configuration” describes ways to check your configuration.

● The section “Save and restore” explains how to save and restore Web-Based Admin View's configuration on a node.

5.1 Web-Based Admin View Concepts

Before discussing wvconf, you should understand the following Web-Based Admin View terms:

● Primary management server—performs the following tasks:

– Functions as the central control point for Web-Based Admin View

– Downloads GUI applets

– Checks user passwords and groups

– Relays all communications between the GUIs and the monitored nodes

● Secondary management server—takes over for the primary management server if it goes down. Multiple secondary management servers can back-up a primary management server.

36 U42144-J-Z100-6-76

Updating /etc/hosts Web-Based Admin View configuration

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k03

● Monitored node1—is a node in the cluster.

● External management server—is a management server that is outside of a cluster. An external management server can be either a primary management or a secondary management server.

A primary management server should control only one cluster. You should not configure two separate clusters to use the same management server.

5.2 Updating /etc/hosts

If you have not already done so, update /etc/hosts with the IP addresses and IP names of all the management servers and all the cluster nodes (refer to section “Pre-installation configuration steps” for more information).

5.3 Using wvconf

The wvconf command allows you to configure all Web-Based Admin View nodes from one system with one command, preventing inconsistency between node configurations.

I wvconf is a Perl script. You must have Perl installed on your system to run wvconf. Use the which perl command to determine if Perl is installed on your system. If necessary, Perl can be downloaded from www.perl.com.

The wvconf command performs the following tasks:

● Verifies that the appropriate packages have been installed.

● Gathers existing configuration information from all nodes

● Proposes a primary management server and management network. If there is an existing Web-Based Admin View configuration, then wvconf uses that configuration for the basis of its proposed configuration.

1 The Web-Based Admin View Operation Guide calls these nodes “monitoring nodes” rather than “monitored nodes” because it emphasizes that Web-Based Admin View is doing the monitoring on these nodes.

U42144-J-Z100-6-76 37

Web-Based Admin View configuration Using wvconf

● Verifies the appropriate Java version is installed, and sets the correct java_home path for Web-Based Admin View. If you have PCS installed, wvconf makes sure that the PCS files will be found by the new Java version.

● Writes the configuration files to the nodes and starts Web-Based Admin View.

The wvconf command is found on the installation CD in the Tool directory. It is also installed with the Cluster Admin package in the following directory:

/opt/SMAW/SMAWrcadm/bin

Once it is installed, link is created to /opt/SMAW/bin/wvconf. The syntax for wvconf is as follows:

wvconf <node list>

<node list> is a list of names or IP addresses of the cluster nodes that you want to configure. The order of the nodes is not important. If you are using external management servers, then you should also list them on the command line.

wvconf can be run on any node in the cluster, or even on a node outside the cluster. To use wvconf, you need to configure rsh or ssh without a password required. The node where wvconf is run must have rsh/rcp or ssh/scp access to all of the target nodes. If wvconf determines that ssh is running, then it will offer to set it up for you. The ssh access can be revoked after wvconf is run.

Once invoked, wvconf guides you through the configuration process for Web-Based Admin View. Whenever possible, wvconf tries to use the existing config-uration on the nodes. For example, if you have a three-node cluster where Web-Based Admin View is already configured, and you want to add a fourth node. If you run wvconf for all four nodes, it will try to make the fourth node's configu-ration similar to the first three.

For clusters consisting of four or more nodes, two of which are external management servers, wvconf configures one external as the primary and one as the secondary. In this type of configuration, internal cluster nodes can never become external management servers.

For clusters consisting of three or more nodes and no external management servers, wvconf configures one as the primary management server and the rest are configured for automatic secondary election.

38 U42144-J-Z100-6-76

wvconf example Web-Based Admin View configuration

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k03

5.4 wvconf example

The following example uses the wvconf command to configure shasta1 and shasta2.

Invoke wvconf as follows:

shasta1# cd /opt/SMAW/SMAWrcadm/bin

shasta1# ./wvconf shasta1 shasta2

This command results in the following interactive dialog:

Figure 2: Initial wvconf output

Type the first letter of a command to select it. A letter contained within brackets indicates that the option is the default and can be selected by pressing the [Enter] or [Return] key.

From here you can add or remove nodes to configure.

Ê Press the [Enter] or [Return] key to continue.

Figure 3: No command connectivity output

I wvconf uses sshconf to setup ssh access. For sshconf to function properly, ensure that the ssh_config and sshd_config files have RSAAuthentication and PasswordAuthentication set to yes.

Ê Type in the root password. Press the [Enter] or [Return] key to continue.

Nodes to configure:

shasta1h 2

Testing connectivity to shasta2 …

No command connectivity to shasta2. Please setup cfsh, ssh or rsh access.rsh and ssh require root access without a password.If ssh is already running on shasta2, then wvconf can setup the

U42144-J-Z100-6-76 39

Web-Based Admin View configuration wvconf example

If command connectivity is present, then a screen similar to figure 4 appears.

Figure 4: wvconf checking for management servers

This screen allows you to add or remove management servers. Management Servers only require the packages necessary to run Cluster Admin. Also, if your cluster contains external management servers, wvconf always configures Web Based Admin View to use those nodes as management servers.

For our example, we will not be selecting any external management servers.

Ê Press the [Enter] or [Return] key to continue. A screen similar to figure 5 appears.

Figure 5: wvconf checking configuration files

wvconf examines the networking and Web-Based Admin View configuration files on the nodes. Using this information, it proposes a primary management server and a management network.

To determine the values to propose, wvconf finds the configuration that is used by the largest number of configuration files. For example, if two nodes specify the same value for the primary management server, and a third node specifies something else, wvconf will propose the value used by the two nodes.

The management network is used for all Web-Based Admin View communica-tions between the management servers and the cluster nodes. The URL to access Web-Based Admin View also uses the IP address on the management network.

Testing connectivity to shasta2 ... ssh scp

Gathering information on shasta1 ... networks hosts wvconfigGathering information on shasta2 ... networks hosts wvconfig

Checking packages on shasta1 ... SMAWcj2re FJSVwvbs FJSVwvcnf FJSVwvmpc SMAWrcadmChecking packages on shasta2 ... SMAWcj2re FJSVwvbs FJSVwvcnf FJSVwvmpc SMAWrcadm

40 U42144-J-Z100-6-76

wvconf example Web-Based Admin View configuration

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k03

wvconf displays all the networks in the cluster and a list of interfaces that are detected. You cannot select a network that does not have every node in the cluster on it; although, networks of this type may be displayed.


Figure 6: wvconf change configuration output

figure 6 shows the Web-Based Admin View parameters that wvconf will change if you continue.

Ê Press the [Enter] or [Return] key to accept the changes and continue. A screen similar to figure 7 appears.

Two node cluster, so configuring static backup.The following changes will be made if you continue:

On shasta1: Set local:java_home to /opt/SMAW/SMAWcj2re/jre Set sys:primary-server to 172.25.222.112 Set sys:secondary-server to 172.25.222.105 Set local:mip to 172.25.222.112 Set local:httpip to 172.25.222.112 Set sys:group-addr to 231.25.222.112 Set local:server-election to offOn shasta2: Set local:java_home to /opt/SMAW/SMAWcj2re/jre Set sys:secondary-server to 172.25.222.105 Set local:mip to 172.25.222.105 Set local:httpip to 172.25.222.105 Set local:server-election to off

(B)ack to settings, (Q)uit, [C]ontinue:

U42144-J-Z100-6-76 41

Web-Based Admin View configuration wvconf example

Figure 7: wvconf configuring Web-Based Admin View

The output shown in figure 7 gives you the URL to access Web-Based Admin View. It also gives a short description on how to start the Wizard in Cluster Admin.

Configuring Web-Based Admin View on shasta1 ... stop set startConfiguring Web-Based Admin View on shasta2 ... stop set start

Configuration complete. To use Web-Based Admin View on this cluster,enter the following URL in your browser:

http://shasta1:8081/Plugin.cgi

If CF needs to be configured, login, click on "Global Cluster Services" and then "Cluster Admin". When the initial connection pop-up appears, select any cluster node. When the main Cluster Admin GUI appears, click "Load Driver"if necessary, and then click "Configure". This will start the CF Wizard.

42 U42144-J-Z100-6-76

Checking the configuration Web-Based Admin View configuration

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k03

If desired, you can disable ssh access using the sshconf command as follows:

# sshconf -d <node list>

<node list> is a list of names or IP addresses of the cluster nodes that you want to disable ssh access. The order of the nodes is not important.

After this command is run, the nodes in the node list will not allow ssh root access without a password from the client system where the command was run.

5.5 Checking the configuration

The Web-Based Admin View configuration can be checked by using either the command line interface (CLI) or the GUI.

5.5.1 Checking the configuration using the CLI

To check the Web-Based Admin View configuration, you can use the following commands, which are found in the directory /etc/opt/FJSVwvbs/etc/bin:

● wvGetparam—displays the Web-Based Admin View parameters on the local node

● wvstat—lists the nodes known to the primary server

The wvGetparam command can be used to display the Web-Based Admin View parameters on the local node. Called without any arguments, wvGetparam prints out all Web-Based Admin View parameters for the node on which it is run. You can restrict the output to a particular environment variable by specifying it on the command line as in the following example:

shasta1# /etc/opt/FJSVwvbs/etc/bin/wvGetparam primary-server

sys:primary-server 172.25.219.83

The wvstat command can be used to find out what nodes the primary and secondary management servers know about. You should see all the nodes in the cluster if the cluster is configured properly and if Web-Based Admin View is running on those nodes.

U42144-J-Z100-6-76 43

Web-Based Admin View configuration Checking the configuration

Sample output for wvstat is as follows:

shasta1# /etc/opt/FJSVwvbs/etc/bin/wvstat

primaryServer 172.25.222.105 shasta1ADM http=172.25.222.105 Run 3d+20h46mprimaryServer Sessions: 0primaryServer Nodes: 2172.25.222.105 shasta1ADM Linux-2.4.19-64GB-SMP 3d+20h46m172.25.222.112 shasta2ADM Linux-2.4.19-4GB 3d+20h46msecondaryServer 172.25.222.112 shasta2ADM http=172.25.222.112 Run 4d+15h6msecondaryServer Sessions: 0secondaryServer Nodes: 2172.25.222.112 shasta2ADM Linux-2.4.19-4GB 4d+15h6m172.25.222.105 shasta1ADM Linux-2.4.19-64GB-SMP 3d+20h47m

The first line of the wvstat output gives the IP address and the name of the primary server, in this case shasta1. Next, the wvstat output lists the nodes known to the primary server. In the above example, the nodes shasta1 and shasta2 are known to the primary server.

The first line that begins with the word secondaryServer gives the IP address and name of the secondary server, which in the above example is shasta2. Next, the wvstat output lists the nodes known to the secondary server.

A node may be missing from the list for the following reasons:

● Web-Based Admin View is not running on that node.

● Web-Based Admin View is not properly configured on that node. (For example, it might not have the same primary server configured as the rest of the cluster nodes.)

5.5.2 Checking the configuration using the GUI

You can display Web-Based Admin View parameters via the GUI simply by entering the URL of a management server, as in the following example:


44 U42144-J-Z100-6-76


© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k03

After logging in as root or as a user belonging to the group wvroot, the GUI should look similar to figure 8.

Figure 8: Main Web-Based Admin View screen

If you click on Node List, then Web-Based Admin View displays a pop-up screen listing all the nodes that it knows about (figure 9).

Figure 9: Node list

If a node that should be in the cluster is missing from the node list, then it is either down or its Web-Based Admin View configuration is not correct.

If the primary server is up, the Web-Based Admin View GUI allows Web-Based Admin View parameters to be easily retrieved. Click on Web-Based Admin tools and then click on Environment settings.

U42144-J-Z100-6-76 45


I The system and node environment only appear if you are connected to the primary management server. Refer to the PRIMECLUSTER Web-Based Admin View Operation Guide for more details.

The Environment settings screen appears (figure 10).

Figure 10: Environment setup screen

46 U42144-J-Z100-6-76


© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k03

If you click on the System environment tab and then on the Primary server selection, you can see what primary server has been configured (figure 11).

Figure 11: Displaying IP address of the primary management server

Displaying the primary management server during initial configuration is partic-ularly useful. For example, by logging on to each node in the cluster by means of http://node_name:8081/Plugin.cgi (where node_name is the name of the node), you can check to see if each node believes that it is the primary management server. If each cluster node believes it is the primary management server, then the initial configuration described in this chapter still needs to be done.

U42144-J-Z100-6-76 47


Click the Node environment tab to display the environment for a specific node (figure 12).

Figure 12: Node environment tab

48 U42144-J-Z100-6-76


© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k03

Clicking on the arrow in the Node box in the upper left-hand corner of the screen produces a drop-down list of all the nodes known to the Web-Based Admin View management server.

All the nodes in this list will also be in the pop-up screen produced by clicking on the Node List button on the main Web-Based Admin View screen. For example, in figure 13, two nodes, shasta1 and shasta2, are known to Web-Based Admin View.

Figure 13: Displaying nodes

All of the cluster nodes and all of the management servers should be listed if Web-Based Admin View is configured properly and the nodes are up.

For more details on the capabilities of similar Web-Based Admin View screens, consult the Web-Based Admin View Operation Guide.

U42144-J-Z100-6-76 49

Web-Based Admin View configuration Save and restore

5.6 Save and restore

This section explains how to save and restore Web-Based Admin View's config-uration on a node. Web-Based Admin View stores its configuration in environment variables (not to be confused with UNIX environment variables). These environment variables can be backed-up at any time. Restoring these environment variables will restore Web-Based Admin View's configuration to the state it was in when the back-up was done.

5.6.1 Saving the configuration

Use the wvEnvsave command to save Web-Based Admin View's configuration on a node.

The syntax is as follows:

/etc/opt/FJSVwvbs/etc/bin/wvEnvsave backup-file

backup-file gives the name of the file to which the Web-Based Admin View's environment variables will be saved.

The following is an example of the wvEnvsave command:

# /etc/opt/FJSVwvbs/etc/bin/wvEnvsave /mydir/Base_GUIs.save

16 blockswvEnvsave: all files saved successfully into '/mydir/Base_GUIs.save'

5.6.2 Restoring the configuration

Use the wvEnvload command to restore a previously saved Web-Based Admin View configuration. The configuration should only be restored when Web-Based Admin View is not running. If you are restoring the configuration on a single node and if that configuration is compatible with the Web-Based Admin View configuration on other nodes in the cluster, then only the single node needs to have Web-Based Admin View stopped. However, if you are restoring the config-uration on all nodes, then Web-Based Admin View should also be stopped on all nodes before the restoration begins. After the restoration is done on all nodes, then Web-Based Admin View may be restarted on the nodes.

The wvEnvload command is used to restore a previously saved Web-Based Admin View configuration on a single node.

50 U42144-J-Z100-6-76

Save and restore Web-Based Admin View configuration

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k03

The syntax is as follows:

/etc/opt/FJSVwvbs/etc/bin/wvEnvload backup-file

backup-file is the name of the file containing the previously saved configuration

The following example of the wvEnvload command restores the previously saved Web-Based Admin View configuration:

1. Stop Web-Based Admin View as follows:

shasta1# /etc/init.d/fjsvwvcnf stop

shasta1# /etc/init.d/fjsvwvbs stop

2. Restore the configuration as follows:

shasta1# /etc/opt/FJSVwvbs/etc/bin/wvEnvload /mydir/Base_GUIs.save

When the configuration is restored, the following dialog appears:

16 blocks4 blockswvEnvload: all files restored successfully.

3. Start Web-Based Admin View as follows:

shasta1# /etc/opt/FJSVwvbs/etc/bin/wvCntl start

shasta1# /etc/init.d/fjsvwvcnf start

U42144-J-Z100-6-76 51

6 Installation exampleThis chapter describes the step-by-step procedures to install, configure, and start up a two-node cluster. The same procedure can be used to add additional nodes to a cluster.


● The section “Network setup” discusses installing and configuring the admin-istration network and the networks used for the cluster interconnects.

● The section “Java environment” clarifies issues with the Java environment used in this example.

● The section “Installing the cluster nodes” details the installation of PRIME-CLUSTER.

● The section “PRIMECLUSTER software configuration” describes config-uring SF and RMS with the GUI.

This chapter uses the following example:

● Two Linux systems using two cluster interconnects, consisting of a primary RMS network and a single AlternateIP network

● Shared access disk system

● Four network cards:

– Two for the cluster interconnects

– One administration network

– One public network

● NPS shutdown agent (SA)

● PRIMECLUSTER will be configured to provide high availability for SAP® Business Suite™

52 U42144-J-Z100-6-76

Installation example

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k10

Web-Based Admin View example configuration

One node will be configured as the primary management server and the other will be configured as the secondary management server.

table 8 shows the network configuration worksheet used for this cluster.

Node 1 Node 2

Node Name shasta1 shasta2


Primary RMS network

Name shasta1RMS shasta2RMS

Address 192.168.1.1 192.168.1.2


Name shasta1rmsAI_0 shasta2rmsAI_0

Address 192.168.2.1 192.168.2.2

Name

Address

Administrative LAN

Name shasta1ADM shasta2ADM

Address 172.25.200.4 172.25.200.5

Public LAN

Name shasta1 shasta2

Address 172.25.222.105 172.25.222.112


U42144-J-Z100-6-76 53

Installation example Network setup

figure 14 shows the example cluster.

Figure 14: Example applications and hardware configuration

table 9 lists Web-Based Admin View parameters.

6.1 Network setup

Before installing the PRIMECLUSTER products, the administration network and the networks used for the cluster interconnects must be installed and configured.

Primary server

Secondary server

shasta1 172.25.222.105

172.25.222.112

shasta2 172.25.222.105

172.25.222.112

Table 9: Web-Based Admin View parameters

shasta2

shasta2ADM

shasta2RMS

shasta2rmsAI_0

Public Network

Administration Network

Cluster Interconnects

shasta2shasta1

shasta1

shasta1ADM

shasta1RMS

shasta1rmsAI_0

shasta2shasta1

54 U42144-J-Z100-6-76

Java environment Installation example

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k10

6.1.1 Verifying the cluster interconnect networks

In the example shown in figure 14, the cluster interconnects are directly connected from one cluster node to another cluster node. In this instance, a crossover cable is used to connect shasta1 to shasta2, and another crossover cable is used to connect a different port of shasta1 to another port of shasta2.

6.2 Java environment

In our example, we are running Cluster Admin on a Windows PC; therefore, we made sure that we used a supported browser and had the correct Java plugin. If you are running a Windows PC, it must be Windows 98 or later.

Check the Base_GUIs Release Notice for the browsers and Java plugins that are supported with Web-Based Admin View and Cluster Admin.

6.3 Installing the cluster nodes

The PRIMECLUSTER CD in the CD-ROM drive can be used to install the PRIMECLUSTER software on all cluster nodes using the cluster_install installation tool. Before beginning, mount the CD-ROM drive to each cluster node as follows:

● On shasta1 and shasta2, mount each CD-ROM drive and enter the following commands:

# mount /<CD1>

# cd <CD1>/Tool/

# ./cluster_install -e SAP

<CD1> is the CD-ROM mountpoint.

Refer chapter “Installation with CLI” for detailed information on how to install PRIMECLUSTER.

U42144-J-Z100-6-76 55

Installation example PRIMECLUSTER software configuration

6.4 PRIMECLUSTER software configuration

In our example, we configure PRIMECLUSTER through the Web-Based Admin View GUI. However, before using the GUI, you must first configure it on all nodes in the cluster as described in the section that follows. Refer to the chapter “Web-Based Admin View configuration” for more details on configuring Web-Based Admin View.

6.4.1 Web-Based Admin View example

The following example uses the wvconf command to configure shasta1 and shasta2. Invoke wvconf as follows:

shasta1# cd /opt/SMAW/SMAWrcadm/bin

shasta1# ./wvconf shasta1 shasta2

This command results in the following interactive dialog:

Figure 15: Initial wvconf output

Type the first letter of a command to select it. A letter contained within brackets indicates that the option is the default and can be selected by pressing the [Enter] or [Return] key.

From here you can add or remove nodes to configure.


If wvconf is not able to access the remote host via rsh or ssh, a screen prompting to configure ssh appears. If you respond yes, wvconf will call the sshconf command (figure 16).

Nodes to configure:

shasta1h 2

56 U42144-J-Z100-6-76

PRIMECLUSTER software configuration Installation example

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k10

Figure 16: No command connectivity output

I For sshconf to function properly, ensure that the ssh_config and sshd_config files have RSAAuthentication and PasswordAuthentication set to yes.

Ê Type in the root password. Press the [Enter] or [Return] key to continue.

Testing connectivity to shasta2 …

No command connectivity to shasta2. Please setup cfsh, ssh or rsh access.rsh and ssh require root access without a password.If ssh is already running on shasta2, then wvconf can setup the RSAcertificates to grant this host root access without a password. Would youlike to do this? [Y/n]: yUsing existing RSA key in /root/.ssh/id_rsa.pub.root@shasta2's password:

U42144-J-Z100-6-76 57


If command connectivity is present, then a screen similar to figure 17 appears.

Figure 17: wvconf checking for management servers

This screen allows you to add or remove management servers. For our example, we will not be selecting any management servers.


Figure 18: wvconf checking configuration files

wvconf examines the networking and Web-Based Admin View configuration files on the nodes. Using this information, it proposes a primary management server and a management network.


Testing connectivity to shasta2 ... ssh scp

Gathering information on shasta1 ... networks hosts wvconfigGathering information on shasta2 ... networks hosts wvconfig

No nodes will be external to the cluster.

(D)eclare external node, (Q)uit, [C]ontinue:

Checking packages on shasta1 ... SMAWcj2re FJSVwvbs SMAWrcadmChecking packages on shasta2 ... SMAWcj2re FJSVwvbs SMAWrcadm

Primary management server: shasta1Management network: 172.25.222.0/255 (shasta1, shasta2)HTTP network: 172.25.222.0/255 (shasta1, shasta2)

(S)erver change, (N)etwork change, (H)TTP network change, (Q)uit, [C]ontinue:

58 U42144-J-Z100-6-76


© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k10

A screen similar to figure 19 appears.

Figure 19: wvconf change configuration output

figure 19 shows the Web-Based Admin View parameters that wvconf will change if you continue.

Ê Press the [Enter] or [Return] key to accept the changes and continue. A screen similar to figure 20 appears.

Figure 20: wvconf configuring Web-Based Admin View

The output shown in figure 20 gives you the URL to access Web-Based Admin View. It also gives a short description on how to start the Wizard in Cluster Admin.

Two node cluster, so configuring static backup.The following changes will be made if you continue:

On shasta1: Set local:java_home to /opt/SMAW/SMAWcj2re/jre Set sys:primary-server to 172.25.222.112 Set sys:secondary-server to 172.25.222.105 Set local:mip to 172.25.222.112 Set local:httpip to 172.25.222.112 Set sys:group-addr to 231.25.222.112 Set local:server-election to offOn shasta2: Set local:java_home to /opt/SMAW/SMAWcj2re/jre Set sys:secondary-server to 172.25.222.105 Set local:mip to 172.25.222.105 Set local:httpip to 172.25.222.105 Set local:server-election to off

(B)ack to settings, (Q)uit, [C]ontinue:

Configuring Web-Based Admin View on shasta1 ... stop set startConfiguring Web-Based Admin View on shasta2 ... stop set start

Configuration complete. To use Web-Based Admin View on this cluster,enter the following URL in your browser:


If CF needs to be configured, login, click on "Global Cluster Services" andthen "Cluster Admin". When the initial connection pop-up appears, select anycluster node. When the main Cluster Admin GUI appears, click "Load Driver"if necessary, and then click "Configure". This will start the CF Wizard.

U42144-J-Z100-6-76 59


If desired, you can disable ssh access using the sshconf command as follows:

# sshconf -d <node list>

<node list> is a list of names or IP addresses of the cluster nodes that you want to disable ssh access. The order of the nodes is not important.

After this command is run, the nodes in the node list will not allow ssh root access without a password from the client system where the command was run.

6.4.2 Signed applets

Cluster Admin uses Java applets. The main advantage of trusting signed applets is that Cluster Admin can use the client system’s resources. For example, you can copy and paste messages from the Java window into other applications.

When Cluster Admin is first started, a Java security warning appears.

Click the Run button to proceed.

6.4.3 SF example

I For a more detailed description of the SF configuration, refer to the PRIMECLUSTER for SAP Business Suite Shutdown Facility (SF) Configuration and Administration Guide.

Launch the GUI by entering the following URL in a Java-enabled browser:


This brings up the Web-Based Admin View main window (figure 21).

60 U42144-J-Z100-6-76


© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k10

Figure 21: Cluster Admin start-up window

Enter root in the User name field and the root password and click on OK.

I In this example we are using root and not creating user groups.

Click on the Global Cluster Services button and the Cluster Admin button appears (figure 22).

U42144-J-Z100-6-76 61


Figure 22: Cluster Admin top window

Click on the Cluster Admin button.

The Choose a node for initial connection window appears (figure 23).

Figure 23: Initial connection choice window

Choose shasta1 and click on Ok.

62 U42144-J-Z100-6-76


© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k10

The Cluster Admin main screen appears (see figure 24).

Figure 24: Cluster Admin main screen

Use the Tools pull-down menu to select Shutdown Facility, and then choose Configuration Wizard to invoke the SF Configuration Wizard (see figure 25).

Figure 25: Invoking the SF Configuration Wizard

U42144-J-Z100-6-76 63


A window similar to figure 26 appears.

Figure 26: Selecting the mode of SF configuration

You can choose to create a new configuration file or edit an existing configu-ration, as shown in figure 26. Choose Create and click on the Next button.

64 U42144-J-Z100-6-76


© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k10

Next, you can select to create a Shutdown Facility configuration to be the same for all nodes or to be different for the individual nodes as shown in figure 27.

Figure 27: Choice of common configuration for all nodes

Choose Same configuration on all Cluster Nodes and click on the Next button.

U42144-J-Z100-6-76 65


A window for choosing SAs appears (figure 28).

Figure 28: Choose SA to be added

Choose NPS from the list shown in figure 28 and click on the Next button. Note that the panel in the left window displays the cluster nodes and progressively shows the SAs configured for each node.

66 U42144-J-Z100-6-76


© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k10

Enter the NPS name, password, and choose the action. You can choose the value cycle or leave off for Action (figure 29). These values have to be the same.

Figure 29: Configuring the NPS SA

The action is cycle by default, which means that the node is power cycled after shutdown. Click on the Next button.

U42144-J-Z100-6-76 67


The configured SA with the timeout value appears in the left-panel tree (figure 30). You can continue to add, delete or edit the SAs if you want.

Figure 30: Add, delete, or edit a SA

For our example, select Finish Configuration. Click on the Next button.

68 U42144-J-Z100-6-76


© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k10

The following window lets you enter the timeout values for the configured SA for each node (figure 31). In this window, you can enter the timeout values for each node and for each SA or click on the Use Defaults button. Select Next to accept the defaults and go to the next window.

Figure 31: Configuring the NPS timeouts

Click on the Next button.

U42144-J-Z100-6-76 69


The window for entering node weights and administrative IP addresses appears (figure 32). Node weights should be an integer value greater than 0. You can select the Admin IP from the displayed list of choices or enter your own. Enter node weights and Admin IP addresses for all cluster nodes.

Figure 32: Entering node weights and administrative IP addresses

For our cluster, we will give each node an equal node weight of 1.

Set the Admin IP fields to the node’s interface on the administrative LAN. By convention, these IP interfaces are named nodeADM; although, this is not mandatory. If you don’t have an administrative LAN, then enter the address to the public LAN. For our cluster, we are using the defaults. Click on Next.

70 U42144-J-Z100-6-76


© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k10

The list of configuration files, created or edited, by the Wizard are shown as in figure 33. Click on Next to save the configuration files or click on Back to change the configuration if needed.

Figure 33: SF configuration files

U42144-J-Z100-6-76 71


Choose Yes in the confirmation popup to save the configuration (figure 34).

Figure 34: Saving SF configuration

The window displaying the configuration status of the SAs appears (figure 35). This might take some time, depending on the number of SAs configured. You can also use the Tools pull-down menu, and choose Show Status in the Shutdown Facility selection.

SF has a test mechanism built into it. SF periodically has each SA verify that it can shutdown cluster nodes. The SA does this by going through all the steps to shut down a node, except the very last one which would actually cause the node to go down. It then reports if the test was successful. This test is run for each node that a particular agent is configured to potentially shut down.

The table in figure 35 shows, among other things, the results of these tests. The columns Cluster Host, Agent, SA State, Shut State, Test State, and Init State when taken together in a single row, represent a test result.

If the word InitFailed appears in red in the InitState column, then the agent found a problem when initializing that particular SA.

If the words TestFailed appear in red in the Test State column, then it means that the agent found a problem when testing to see if it could shut down the node listed in the Cluster Host column. This indicates some sort of problem with the software, hardware, or networking resources used by that agent.

72 U42144-J-Z100-6-76


© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k10

If the word Unknown appears in the Shut State, Test State, or the Init State columns, it means that SF has not attempted to shut down, test, or initialize those SAs. For the Test State and the Init State columns, the Unknown state is usually a temporary state that disappears when the actual state is known.

Figure 35: Status of SAs

If you see TestFailed or InitFailed, look at the SA log files. The log files show debugging information on why the SA’s test or initialization failed. Once the problem is corrected, and SF is restarted, the status should change to InitWorked or TestWorked. Refer to the PRIMECLUSTER for SAP Business Suite Reliant Monitor Services (RMS) with PCS (Linux) Configuration and Administration Guide for details on the locations of SA log files.

U42144-J-Z100-6-76 73


Click on the Finish button to exit the SF Wizard. A confirmation popup appears and asks if you really want to exit the Wizard (figure 36). If you click on Yes, then the SF Wizard disappears, and you see the base Cluster Admin window.

If you click on the Back button in the SF Wizard instead of the Finish button, then you can go back and re-edit the SF configuration.

Figure 36: Exiting SF configuration wizard

The Wizard disappears, and the normal screen for running a configuration appears (see figure 37).

Figure 37: Screen for a running a configuration

74 U42144-J-Z100-6-76


© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k10

6.4.4 PCS example

This section gives an example of creating an application using PCS. A similar configuration example is provided in the PRIMECLUSTER for SAP Business Suite Reliant Monitor Services (RMS) with PCS (Linux) Configuration and Administration Guide.

This example uses a simple configuration with a single command line subappli-cation to illustrate the PCS configuration process. The example includes the following steps:

● Starting PCS

● Selecting a node for the PCS session

● Entering a configuration name

● Selecting nodes

● Choosing an application template

● Changing the application name

● Selecting nodes for the application

● Configuring a subapplication

● Saving the configuration

● Activating the configuration

U42144-J-Z100-6-76 75


6.4.4.1 Starting PCS

In the Cluster Admin initial window, select the rms&pcs tab. The RMS adminis-tration window appears (figure 38).

Figure 38: RMS administration window

From the Tools menu, select PRIMECLUSTER Configuration Services (PCS) (figure 39).

Figure 39: Invoking PCS

76 U42144-J-Z100-6-76


© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k10

6.4.4.2 Selecting a node for the PCS session

You will be prompted to choose a node where you will start this PCS session (figure 40).

Figure 40: Selecting a node for PCS session

By default, you will connect to the same node where you started Cluster Admin. If you’re modifying a configuration stored on a different node, you should check the box of that node instead. Click the OK button to connect to the desired node.

U42144-J-Z100-6-76 77


6.4.4.3 Creating a new configuration

To create a new configuration, type the new name directly into the Configuration Name input box (figure 41).

Figure 41: Entering a new configuration name

Click Next to proceed.

78 U42144-J-Z100-6-76


© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k10

6.4.4.4 Selecting nodes

Your first task is to select the nodes to be managed by the new configuration. You should include any node that might be used to run the applications that you want to make highly available (figure 42).

Figure 42: Selecting nodes

Nodes that appear in the right-hand Selected Nodes column will be included in the configuration. By default, PCS automatically detects all online nodes in the local cluster and enters them in the Selected Nodes column. Any nodes that appear in the left-hand Available Nodes column are not included in the present configu-ration.

In most cases, the Available Nodes column is initially empty, but you may want to include machines that are members of another cluster, or currently offline, and therefore not automatically detected by PCS. In such cases, you can manually add nodes to the left-hand Available Nodes column by typing each node name in the Enter Node to be added box and then clicking the + button.

I The list of nodes can also be modified after the configuration has been created.

U42144-J-Z100-6-76 79


You can exclude one or more available nodes in the configuration by moving their names to the left-hand Available Nodes column with the arrow buttons. The << (double left arrow) button moves all selected nodes to the Available Nodes column, and the >>(double right arrow) button moves all available nodes back to the Selected Values column. To move a single node, use the > (single right arrow) button or the < (single left arrow) button.

In this example, keep shasta1RMS and shasta2RMS in the Selected Values column. Click Next to proceed.

PCS displays the Configuration Start window (figure 43).

Figure 43: Configuration Start window

80 U42144-J-Z100-6-76


© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k10

6.4.4.5 Viewing the configuration tree

The configuration name appears in the left pane at the top of the tree. In a new configuration it will initially be the only item, marked as consistent with a blue status icon. Other items such as applications, subapplications, configuration groups, and instances will appear as PCS guides you through the configuration process.

If the real-time consistency check option is selected, items in the tree will change state as you add applications and subapplications:

● A blue status icon indicates a consistent state—all required information for the item (and its subtree, if any) has been entered.

● A red status icon indicates an inconsistent state—the item or a member of its subtree has at least one required parameter or selection missing.

● An orange status icon indicates an optional item—usually a subapplication that is not required by the parent application.

If you save the configuration before it is consistent, PCS will display a warning in the right-hand user input pane.

6.4.4.6 Choosing the application template

You are now ready to configure an application for your configuration. PCS uses templates to make the configuration process easier; in this example, we will make a configuration for an application using the Generic application template.

I The templates that appear in the drop down list depend on the installed software.

U42144-J-Z100-6-76 81


From the Configuration Start window, leave Generic for the Template Name in the drop-down list (figure 44).

Figure 44: Choosing the application template

82 U42144-J-Z100-6-76


© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k10

6.4.4.7 Changing the application name

The Change Application Name window appears (figure 45).

Figure 45: Changing the application name

Note that the tree in the left pane now displays items that are automatically provided by the Generic template as follows:

● The item currently being configured has its name highlighted in light blue, and its associated parameters are displayed in the right-hand user input pane.

● The items marked with red status icons are inconsistent, which means that you must define some additional parameters before RMS can run the config-uration.

By default, PCS automatically names the first application App0. This appears as the first item below the configuration name in the tree and in the corresponding right pane. You can change it by entering any valid name in the text input box.

For our example, accept the default name and click Next to continue.

U42144-J-Z100-6-76 83


6.4.4.8 Viewing template information

The Processing Application window appears, which displays template-specific information (figure 46). No user input is required here. Click the Next button to continue.

Figure 46: Viewing Generic template information

84 U42144-J-Z100-6-76


© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k10

6.4.4.9 Selecting nodes for the application

You must specify a list of nodes where the current application will run. You can choose any or all of the nodes you selected earlier for this configuration (figure 47).

Figure 47: Available nodes for an application

U42144-J-Z100-6-76 85


Add the nodes shasta1RMS and shasta2RMS to the Selected Values column (figure 48).

Figure 48: Selected nodes for an application

Click Next to proceed.

6.4.4.10 Setting application parameters

Click Next to accept the defaults and continue to the next item in the tree.

86 U42144-J-Z100-6-76


© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k10

6.4.4.11 Configuring a subapplication

You advance to the first subapplication in the template. Note that the first two items in the application subtree are now marked as consistent with blue status icons. In this example, we will configure the CommandLine subapplication. Check the Configure this subapplication checkbox in the right pane (figure 49).

Figure 49: Beginning a subapplication configuration

Because this is the first instance of this subapplication, PCS advances automat-ically to the subapplication parameters window (figure 50).

figure 50 uses the following scripts to illustrate how the scripts work:

● Start command: ‘/bin/touch /tmp/HelloWorld’ (creates a file)

● Stop command: ‘rm -f /tmp/HelloWorld’ (removes the file)

● Detector command: ‘ls /tmp/HelloWorld’ (determines if the file exists)

U42144-J-Z100-6-76 87


The operations for the CommandLine subapplication are executed in the following order:

1. The Detector Command is first executed at RMS startup and repeated at regular intervals; by default the interval is 10 seconds. The detector command should return a zero status code when the application is online, and a non-zero status code when the application is offline.

In this example, ‘ls /tmp/HelloWorld’ will return a zero status code if the file exists, and non-zero otherwise. Assuming the file does not exist when RMS starts up, the detector will initially return a non-zero status. RMS inter-prets this to mean the subapplication is offline.

2. The Start Command is executed whenever the application receives a directive to go online. This script is executed automatically if the application’s AutoStartUp option is set to Yes. If AutoStartUp is set to No, the default, the script will be executed when you use the Cluster Admin GUI or the hvswitch command to manually instruct the application to go online. In any case, the start command should return a zero status code to indicate successful completion, and a non-zero status code otherwise.

In this example, ‘/bin/touch /tmp/HelloWorld’ creates the file specified in the detector script and returns a zero status code. Subsequent execution of the detector will return a zero status code as long as the file is present. RMS interprets this to mean the subapplication is online.

3. The Stop Command is executed when a fault occurs or when the application is to be taken offline. During normal operation, the application may be automatically taken offline on the local node before RMS switches it to another node; the application may also be taken offline manually via the GUI or CLI.

In this example, ‘rm -f /tmp/HelloWorld’ removes the file specified in the detector script. Subsequent executions of the detector return a non-zero status code, which RMS interprets to mean the subapplication is offline.

Note that the file could have been deleted manually by the operator, in which case the detector would also return a non-zero status. However, since this happened without an intervening Stop Command, RMS would interpret this as a fault, and it would initiate its standard recovery procedure.

88 U42144-J-Z100-6-76


© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k10

The CommandLine subapplication is now consistent, as shown by its blue status icon (figure 50).

Figure 50: CommandLine subapplication parameters

Click Next to continue.

U42144-J-Z100-6-76 89


The focus (light blue highlight) in the left pane has advanced to the next subap-plication (figure 51). To configure additional subapplications, you would move the focus in the configuration tree, check Configure this subapplication in the right pane, and click Next. You can also use the Skip button to proceed with the config-uration without adding additional applications or subapplications at any stage.

Figure 51: Additional subapplications

In our example, we will skip all other subapplications.

90 U42144-J-Z100-6-76


© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k10

6.4.4.12 Checking application consistency

The blue status icon for the nodes (shasta1RMS and shasta2RMS), the appli-cation (App0), and the subapplication (Command Line) indicates that they are consistent. The other subapplications are optional and are not used in this configuration, so their status icons are orange. Therefore, the demo configu-ration tree is also consistent (figure 52).

Figure 52: Consistent configuration tree

U42144-J-Z100-6-76 91


6.4.4.13 Saving the configuration

To save the configuration with the current name, you can use File –> Save from the menu at any time (figure 53). You can clone the configuration by using File –> Save As, which saves the configuration with a different name.

Figure 53: Saving a configuration with the menu

figure 54 appears after the configuration has been saved successfully. Click Next to continue.

Figure 54: Message after successful save operation

6.4.4.14 Activating the configuration

When the configuration is consistent, you can activate it. Activation consists of the following phases:

● Generation—Generates a complete RMS configuration file, configname.us, which is stored on the local machine.

● Distribution—Copies the configuration file, along with the required detectors and scripts, to all the nodes specified in the configuration.

● Activation—Marks the configuration as the one to load when RMS restarts.

I Before you activate a configuration, you must stop RMS on all nodes in the configuration. By default, RMS will use the most recently activated configuration the next time it starts.

92 U42144-J-Z100-6-76


© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k10

To activate the configuration use Tools –> Activate-> Update (figure 55).

Figure 55: Activating a configuration

When the activation phase completes, the status appears in a message window (figure 56).

Figure 56: Activation succeeded

Next, you can start RMS from the Cluster Admin main window by selecting Tools -> Start RMS.

This PCS configuration example is only a general product demonstration. For a more complete description of PCS options, refer to the PRIMECLUSTER for SAP Business Suite Reliant Monitor Services (RMS) with PCS (Linux) Configuration and Administration Guide.

U42144-J-Z100-6-76 93

7 PRIMECLUSTER upgradeThis chapter describes upgrading PRIMECLUSTER from versions 4.2A00 to version 4.2A20.

I If you are upgrading from a version other than 4.2A00, you must first upgrade to 4.2A00 before continuing. To upgrade to 4.2A00, follow the upgrade instructions as described in the PRIMECLUSTER Installation Guide for SAP® Business Suite™ (Linux) for PRIMECLUSTER 4.2A00.

Upgrading in a clustered environment can have serious implications and should be carefully planned. There may be applications for which this procedure does not work. Contact your Fujitsu Technology Solutions sales team for information concerning specific application updates.


● The section “Overview” describes the rolling upgrade process.

● The section “Cautions” informs you about possible risks during a rolling upgrade.

● The section “Preparation” discusses steps to be considered before doing an upgrade.

● The section “Performing the rolling upgrade” contains instructions for upgrading each node of the cluster.

● The section “Post-installation” details the post-installation modifications needed to complete the upgrade.

● The section “Conclusion” completes the discussion on the rolling upgrade process.

7.1 Overview

A rolling upgrade in a PRIMECLUSTER environment proceeds by taking one node at a time out of the cluster and upgrading the PRIMECLUSTER software on that node. When the upgrade on that node is complete, it is rejoined to the cluster. This process is repeated until all the nodes in the cluster are upgraded. This method of upgrade ensures minimum downtime and minimizes the impact on the availability.

94 U42144-J-Z100-6-76

Cautions PRIMECLUSTER upgrade

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k12

I If the cluster includes software from PRIMECLUSTER CD2, such as Global Disk Services (GDS), Global File Services (GFS), and Global Link Services (GLS), then the rolling-upgrade procedures described in this chapter do not apply.

Only PRIMECLUSTER products from CD1 are supported with the rolling upgrade described in this chapter.

7.2 Cautions

V Caution

A rolling upgrade of PRIMECLUSTER requires that you follow these instructions precisely. Omitting a step might cause loss of availability of an application, or in severe cases, you might lose cluster integrity and corrupt your application data. Planning the details of a rolling upgrade is strongly recommended.

V Caution

Do not make any changes in the configuration until all PRIMECLUSTER packages have been updated on all nodes. The new PRIMECLUSTER packages are compatible with the old PRIMECLUSTER packages, but the old PRIMECLUSTER packages might not necessarily understand the configuration of the new PRIMECLUSTER packages. The cluster might lose functionality if changes are made in the configuration while running two versions of PRIMECLUSTER. This would mean that high availability is not guaranteed.

V Caution

Do not attempt to configure and activate new features in PRIME-CLUSTER until all cluster nodes are upgraded. Configuration and activation for the new features is not part of the rolling upgrade process. Once the entire cluster is upgraded, new features can be configured and activated.

V Caution

Do not use Cluster Admin or Web-Based Admin View until all of the nodes in the cluster are upgraded successfully. If these products are used during the upgrade process, both cluster integrity and high avail-ability could be lost.

U42144-J-Z100-6-76 95

PRIMECLUSTER upgrade Preparation

7.3 Preparation

This section provides you with preparation and planning steps that will help you to achieve a safe and smooth upgrade.

A software upgrade in a clustered environment is more complex because the expectations are higher than for a stand-alone machine. For a stand-alone (non-clustered) machine, you shut down your applications, perform an update, and restart the applications. In a clustered environment, it is assumed that the appli-cation can remain running while the update is performed.

To accomplish this, during an update a cluster will have two versions of the cluster software installed and running at the same time, one version on each of two sub-clusters. During this time, the operations that can be performed on the cluster are highly restricted.

7.3.1 Backup

In the unlikely case that something should go wrong during the upgrade procedure and a restoration needs to be performed, it is important to have a backup made before the upgrade procedure has started. Therefore, it is recom-mended that you make a complete backup, including application production data and the PRIMECLUSTER configuration.

Refer to the documentation of the application software on how to backup the production data, and be aware that if you keep the application running during the upgrade, your production data can diverge from the backup.

96 U42144-J-Z100-6-76

Preparation PRIMECLUSTER upgrade

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k12

table 10 lists the PRIMECLUSTER configuration files.

Packages Configuration files Notes

SMAWsf /etc/opt/SMAW/SMAWsf/*.cfg/opt/SMAW/SMAWsf/etc/SA_wtinps.ver

Actual files may vary, depending on the installed SAs

webview /opt/FJSVwvbs/etc/webview.cnf/opt/FJSVwvbs/etc/wvlocal.cnf

Web-Based Admin View configu-ration file

SMAWRrms /etc/exports1

/etc/group1/etc/hosts1/etc/host.conf1/etc/nsswitch.conf1/etc/passwd1/etc/fstab1/opt/SMAW/SMAWRrms/etc/*/opt/SMAW/SMAWRrms/bin/hvenv.local/opt/SMAW/SMAWRrms/bin/hvgdstartup/opt/SMAW/SMAWRrms/bin/wizard.d/contrib/*/opt/SMAW/SMAWRrms/build/2

1 System files modified for PRIMECLUSTER2 Files, directories, and subdirectories to be saved

Table 10: PRIMECLUSTER configuration files

U42144-J-Z100-6-76 97

PRIMECLUSTER upgrade Preparation

7.3.2 Upgrade preparation

I Before starting the upgrade process, verify that you have enough available disk space for the new PRIMECLUSTER upgrade.

To verify that the upgrade to PRIMECLUSTER will not cause any problems, you need to verify the upgrade capability, and you might need to save or modify the existing cluster configuration. The following steps need to be done before rolling upgrade:

1. Install patches

2. Decide in which order to upgrade the nodes

3. RMS preparation

4. Save Web-Based Admin View configuration file

7.3.2.1 Install patches

For compatibility between nodes in the cluster during rolling upgrade, you need to install one or more patches on all the nodes prior to the rolling upgrade process. Please install the latest available patch level for all PRIMECLUSTER products. Patches may be available to fix problems which were unknown at the time this text was written, but which are needed for rolling upgrade. Not installing these patches could cause incompatibility, preventing the cluster from working properly and, in severe cases, result in data corruption.

The latest patch level can be obtained through your support staff.

V Important

After performing section “Shutdown node A” and before installing the new PRIMECLUSTER software in section “Upgrading the software on node A”, ensure that the operating system (OS) is on a supported level for the new PRIMECLUSTER software. Refer to the CF Release Notice for details on the supported OS level (refer to the section “PRIMECLUSTER documentation”).

7.3.2.2 Decide the node upgrade order

From the existing cluster, you need to select which node(s) should remain running and which single node will be taken out for upgrading.

98 U42144-J-Z100-6-76

Performing the rolling upgrade PRIMECLUSTER upgrade

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k12

While deciding on the node order, ensure that one or more of the remaining nodes in the cluster have all parts of the third-party software. Refer to the appro-priate third-party application software documentation for more details.

7.3.2.3 Save Web-Based Admin View configuration file

During the rolling upgrade, the existing Web-Based Admin View software is removed by cluster_uninstall. Therefore, on each node, you need to save the Web-Based Admin View configuration with the wvEnvsave command:

/etc/opt/FJSVwvbs/etc/bin/wvEnvsave backup-file

backup-file is the name of the file to which the Web-Based View's environment variables will be saved.

The following is an example of the wvEnvsave command with output:

# /etc/opt/FJSVwvbs/etc/bin/wvEnvsave /mydir/Base_GUIs.save

16 blocks

wvEnvsave: all files saved successfully into '/mydir/Base_GUIs.save'

7.4 Performing the rolling upgrade

This section contains instructions for upgrading each node of the cluster.

The first node to be upgraded is referred to as node A. This discussion also assumes that all RMS applications are switched over to a single node, referred to as node B. In general, the RMS applications can be switched over to one or more nodes.

To perform a rolling upgrade on node A:

1. Switch RMS applications from node A to node B

2. Shutdown node A (node A is out of the cluster)

3. Upgrade node A software to the latest PRIMECLUSTER version

4. Rejoin node A to the cluster

Repeat the steps above for each node in the cluster.

When all of the nodes are upgraded to the latest PRIMECLUSTER software, follow the post-installation steps to complete the rolling upgrade process.

U42144-J-Z100-6-76 99

PRIMECLUSTER upgrade Performing the rolling upgrade

7.4.1 Switching RMS applications

I The Cluster Admin GUI must not be used during rolling upgrade. Use the command line for cluster administration.

Before shutting down RMS, determine the applications controlled by RMS that need to be switched over to node B. Switch RMS applications from node A to node B as follows:

1. Run the following command on node A to list applications to be switched:

# hvdisp -T userApplication

In the output, resources of type userApplication without a HostName that are not offline are the RMS applications currently running on node A as in the following example:

Local System: shasta1RMSConfiguration: /opt/SMAW/SMAWRrms/build/websvr.us

Resource Type HostName State -------------------------------------------------------------app1 userApplication Onlineapp2 userApplication Online

2. Switch applications to node B:

# hvswitch userApplication SysNode

userApplication is the name of your RMS application.

SysNode is the name of node B.

The following example shows how an application can be switched from shasta1 to shasta2:

shasta1# hvswitch app1 shasta2

shasta1# hvswitch app2 shasta2

For more details on how to switch an application, refer to the PRIME-CLUSTER for SAP® Business Suite™ Reliant Monitor Services (RMS) with Wizard Tools (Solaris, Linux) Configuration and Administration Guide or the PRIMECLUSTER for SAP® Business Suite™ Reliant Monitor Services (RMS) with PCS (Solaris, Linux) Configuration and Administration Guide.

100 U42144-J-Z100-6-76


© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k12

3. Verify that applications under RMS control from node A are moved to node B with the following command:

# hvdisp -T userApplication

For example, specify the following command from shasta1:

shasta1# hvdisp -T userApplication

The output appears as follows:

Local System: shasta1RMSConfiguration: /opt/SMAW/SMAWRrms/build/websvr.us

Resource Type HostName State -------------------------------------------------------------app1 userApplication Offline app1 userApplication shasta2RMS Onlineapp2 userApplication Offline app2 userApplication shasta2RMS Online

All RMS applications have been switched over to shasta2 as shown by the output because the resources of type userApplication without a HostName are Offline and the resources of type userApplication on shasta2RMS are Online.

In the section “Shutdown node A” that follows, RMS applications still running on node A will be taken Offline without switching over to node B.

7.4.2 Shutdown node A

All of the PRIMECLUSTER products and the applications controlled by PRIME-CLUSTER have to be stopped in order to remove the current PRIMECLUSTER software.

1. Stop any third-party applications that do not need to be moved to node B. Refer to your application software documentation on how to stop the appli-cation.

2. Shutdown RMS locally on node A with the following command:

# hvshut -l

This shuts down RMS and all the applications controlled by RMS on node A only.

U42144-J-Z100-6-76 101


3. Stop the Shutdown Facility as follows:

# /etc/init.d/SMAWsf stop

I In the hvdisp output of the other cluster nodes, Node A will be displayed with the State Offline and the StateDetails Not Joined.

7.4.3 Upgrading the software on node A

To upgrade the software on node A, perform the following steps:

1. Manually remove some PRIMECLUSTER packages

2. Remove the remaining old PRIMECLUSTER packages

3. Verify supported OS level

4. Remove any persisting PRIMECLUSTER kernel drivers

5. Install the new PRIMECLUSTER packages

7.4.3.1 Manually removing PRIMECLUSTER packages

If one or more of the following packages is installed, it must be removed manually:

● SMAWRhv-db

● SMAWRhv-co

● SMAWRhv-de

● SMAWRhv-ns

● SMAWRhv-ws

● SMAWRhv-xp

To check whether a package is installed, use the following command:

# rpm -q package_name

If package_name is installed, your output is similar to:

package_name-4.2A00-11

If package_name is not installed, your output is:

package package_name is not installed

102 U42144-J-Z100-6-76


© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k12

To manually remove the installed package:

# rpm -e package_name

7.4.3.2 Removing the remaining old PRIMECLUSTER packages

Now use cluster_uninstall to remove the remaining PRIMECLUSTER packages. Load the PRIMECLUSTER CD1 of the currently running PRIME-CLUSTER version into the CD-ROM drive and execute the following:

1. # mount /<CD1>

<CD1> is the CD-ROM mountpoint.

2. # cd <CD1>/Tool

3. # ./cluster_uninstall

You will see output similar to the following:

Are you sure to remove PRIMECLUSTER from your system (y or n)?

Reply by entering the letter y to proceed.

Output similar to figure 57 appears.

Figure 57: cluster_uninstall output

The cluster_uninstall removal of PRIMECLUSTER packages is complete when the following message is output:

The uninstallation finished successfully.

I Not all PRIMECLUSTER configurations have all PRIMECLUSTER packages installed. Therefore, the output of cluster_uninstall might show fewer or additional packages.

Uninstalling package <SMAWRhv-or> ... finishedUninstalling package <SMAWRhv-dm> ... finishedUninstalling package <SMAWRhv-r3> ... finishedUninstalling package <SMAWRhv-do> ... finishedUninstalling package <SMAWRhv-ba> ... finishedUninstalling package <SMAWRhv-to> ... finishedUninstalling package <SMAWRrms> ... finishedUninstalling package <SMAWsf> ... finishedUninstalling package <SMAWhvksh> ... finishedUninstalling package <SMAWskel> ... finishedUninstalling package <SMAWrcaja> ... finishedUninstalling package <SMAWrcadm> ... finishedUninstalling package <FJSVwvmpc> ... finishedUninstalling package <FJSVwvbs> ... finishedUninstalling package <FJSVpclsnap> ... finished

U42144-J-Z100-6-76 103


7.4.3.3 Verify supported OS level

PRIMECLUSTER has now been removed from your system, while the PRIME-CLUSTER configuration remains untouched. The next step is to ensure that the OS is on a supported level for the new PRIMECLUSTER software. Refer to the CF Release Notice for details on the supported OS versions and their respective patch level. After updating the base OS, review the disk space requirements.

I Some operating systems configure all interfaces with the node name. By installing a patch, the interfaces with node_nameRMS and node_namermsAI_n might be reset to the node name. Please take the appropriate action to have correct interface names.

7.4.3.4 Installing new PRIMECLUSTER packages

The installation of new PRIMECLUSTER packages follows the same procedure as a new installation. Refer to thechapter “Installation with CLI” for details on the installation process.

I Install the current valid patches for the new software once the installation on this node is completed successfully.

I If you are using SMAWrcmib, verify that the correct version of EMANATE SNMP Master Agent is installed. Refer to the SMAWrcmib readme for the supported version.

7.4.4 Joining node A back to the cluster

Perform the following when the new packages have been installed successfully:

1. Reboot node A by using the following command:

# init 6

This will reboot the node in multi-user mode.

Node A will be part of the cluster again when the node is in multi-user mode, and all the PRIMECLUSTER software is started.

2. Start RMS and start RMS applications on node A, and switch back applica-tions to node A:

104 U42144-J-Z100-6-76


© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k12

V Caution

Do not select Configuration-Activate in the RMS Wizards or Activate in PCS during a rolling upgrade (because different versions of RMS are running in the cluster).

a) Start RMS on node A (issue command on node A):

Depending on the RMS setting, RMS might start during reboot (HV_RCSTART=1). If RMS does not start during a reboot (HV_RCSTART=0), you can now issue the following command:

# hvcm

If the RMS configuration includes node-specific applications for node A, which do not startup during a reboot, you may start them now as follows:

# hvswitch userApplication

b) Remember that switching an application from one node to another causes a brief interruption, and should generally be avoided. Also, now that node A is upgraded, it will remain running for the remainder of the rolling upgrade. Therefore, applications switched to node A will not need to be switched again.

To switch an RMS application to node A, issue the following command on the node currently running the application:

# hvswitch userApplication SysNode

userApplication is the name of your RMS application.

SysNode is the name of node A.

c) Verify that applications have switched back to node A (issue command on node A):

# hvdisp -a

7.4.5 Upgrading the next node

At this point, node A has rejoined the cluster with the new PRIMECLUSTER software. All applications are running on node A.

Return to the section “Performing the rolling upgrade” to upgrade the next node until all the nodes in the cluster are upgraded.

U42144-J-Z100-6-76 105

PRIMECLUSTER upgrade Post-installation

After all the nodes have been upgraded to the latest PRIMECLUSTER software, you need to adjust the configuration to complete the rolling upgrade process, as described in the following section.

7.5 Post-installation

All of the nodes in the cluster are now running the upgraded PRIMECLUSTER software, but with only the earlier software features. The following modifications are needed to complete the upgrade and access the new features:

● Restoring the Web-based Admin View configuration

● Establishing an RMS configuration for the new version of RMS

7.5.1 Restoring Web-Based Admin View configuration

Restore the Web-Based Admin View configuration as follows:

1. Web-based Admin View needs to be stopped before performing the resto-ration. Perform the following on all the nodes to stop Web-based Admin View:

# /etc/init.d/fjsvwvcnf stop

# /etc/init.d/fjsvwvbs stop

2. Use the wvEnvload command to restore the previously saved Web-Based Admin View configuration (refer to the section “Save Web-Based Admin View configuration file”). The configuration should be done on every node and only when Web-Based Admin View is not running. After the restoration is done on all nodes, then Web-Based Admin View may be restarted on the nodes. The syntax is as follows:

/etc/opt/FJSVwvbs/etc/bin/wvEnvload backup-file

backup-file is the name of the file containing the previously saved configu-ration

The following is an example of the wvEnvload command:

# /etc/opt/FJSVwvbs/etc/bin/wvEnvload /mydir/Base_GUIs.save

16 blocks4 blockswvEnvload: all files restored successfully.

106 U42144-J-Z100-6-76

Post-installation PRIMECLUSTER upgrade

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k12

3. Web-based Admin View can be started when all the PRIMECLUSTER software has been upgraded successfully on all the nodes. Perform the following command on all the nodes:

# /etc/opt/FJSVwvbs/etc/bin/wvCntl restart

# /etc/init.d/fjsvwvcnf restart

This starts Web-based Admin View on all the nodes in the cluster.

I While performing the wvCntl restart you might see a message on the console ending in vip: vip_ioctl: default UNKNOWN

This message is only for informational purposes and does not indicate an error condition within this context.

7.5.2 Configuring the new RMS version

The new features in PRIMECLUSTER cannot be accessed until a configuration for the new RMS version is established, and the RMS configuration is regen-erated, redistributed, and restarted. RMS must be shutdown without stopping the application controlled by RMS, and, therefore, failovers are not supported during this procedure. However, it is highly recommended that you perform this step as soon as possible.

Establish, regenerate, redistribute, and restart an RMS configuration for the new RMS version as follows:

WT configuration

1. Execute the following command on one node in the cluster to shutdown RMS clusterwide:

# hvshut -A

This shuts down RMS, but leaves the applications controlled by RMS running.

2. Execute the following command on any node to invoke the RMS Wizard:

# hvw

With the RMS wizard, select Configuration-Activate to regenerate and redis-tribute RMS with the new configuration.

U42144-J-Z100-6-76 107


3. Execute the following command on any node to restart RMS on all nodes:

# hvcm -a

PCS configuration

1. Execute the following command on one node in the cluster to shutdown RMS clusterwide:

# hvshut -A

This shuts down RMS, but leaves the applications controlled by RMS running.

2. Launch the GUI by entering the following URL in a Java-enabled browser:

http://node_name:8081/Plugin.cgi

node_name is the name of a node in the cluster that you are upgrading. For example, shasta1 is the name of one of the cluster nodes in the following:


This brings up the Web-Based Admin View main window (figure 58).

Figure 58: Cluster Admin start-up window

Enter root in the User name field and the root password and click on OK.

108 U42144-J-Z100-6-76


© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k12

3. Click on the Global Cluster Services button and the Cluster Admin button appears (figure 59).

Figure 59: Cluster Admin top window

Click on the Cluster Admin button.

4. The Choose a node for initial connection window appears (figure 60).

Figure 60: Choosing an initial node

Choose a node and click Ok.

U42144-J-Z100-6-76 109


5. In the Cluster Admin initial window, select the rms&pcs tab. The RMS admin-istration window appears (figure 61).

Figure 61: RMS administration window

From the Tools menu, select PRIMECLUSTER Configuration Services (PCS) (figure 62).

Figure 62: Invoking PCS

110 U42144-J-Z100-6-76


© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k12

6. Choose a node for this PCS session (figure 63).

Figure 63: Selecting a node for PCS session

7. Click the arrow next to the Configuration Name menu, and select a PCS configuration from the list (figure 64).

Figure 64: Selecting PCS configuration

U42144-J-Z100-6-76 111


Click Next.

8. From the Tools menu, select Activate -> All Nodes (figure 65).

Figure 65: Activating PCS configuration

When the activation phase completes, the status appears in a message window (figure 66).

Figure 66: Activation succeeded

9. Exit PCS from the main menu by selecting File -> Exit (figure 67).

Figure 67: Exiting PCS

A confirmation pop-up appears. Click OK.

112 U42144-J-Z100-6-76

Conclusion PRIMECLUSTER upgrade

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k12

10.Start RMS from the Cluster Admin main window by selecting Tools -> Start RMS (figure 68).

Figure 68: Starting RMS

7.6 Conclusion

The upgrade of the PRIMECLUSTER software is now complete. Your old PRIMECLUSTER configuration has now been upgraded to the latest PRIME-CLUSTER configuration and the new features are now available. Refer to the product Release Notice for information about the new features.

Because all of the nodes are now running the latest version of PRIME-CLUSTER, and Web-based Admin View has been upgraded as well, the cluster can now be administered using Cluster Admin.

Verify with the Acceptance Test specified in your sales agreement, that the cluster is fully operational.

U42144-J-Z100-6-76 113

8 Manual pagesThis chapter lists the online manual pages for PCS,RMS, RMS Wizards, SF, and Web-Based Admin View.

To display a manual page, type the following command:

$ man man_page_name

8.1 Monitoring Agent

System administration

cldevparamchanges or displays the displays the tunable operation environment for asynchronous monitoring

clmmbmonctlstarts, stops, restarts, and displays the operating system of the MMB asynchronous monitoring daemon

clmmbsetupregisters, changes, deletes, or displays MMB information

8.2 PCS


pcstoolModifies PCS configurations from the command line

pcscuiCharacter-based interface for PCS

pcs_reinstallUtility for re-integrating PCS with dependent products

114 U42144-J-Z100-6-76

RMS Manual pages

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k13

8.3 RMS


hvassertassert (test for) an RMS resource state

hvcmstart the RMS configuration monitor

hvconfigdisplay or save the RMS configuration file

hvdispdisplay RMS resource information

hvdistdistribute RMS configuration files

hvdumpcollect debugging information about RMS

hvgdmakecompile an RMS custom detector

hvlogcleanclean RMS log files

hvrclevchange default RMS start run level

hvresetinterrupt ongoing activities and re-initialize the userApplication graph

hvsetenvmanipulate RMS rc start or AutoStartUp

hvshutshut down RMS

hvswitchswitch control of an RMS user application resource to another node

hvthrottleprevent multiple RMS scripts from running simultaneously

hvutilmanipulate availability of an RMS resource

U42144-J-Z100-6-76 115

Manual pages RMS Wizards

File formats

hvenv.localRMS local environment configuration file

8.4 RMS Wizards

RMS Wizards and RMS Application WizardsRMS Wizards are documented as html pages in the SMAWRhv-do package on the CD-ROM. After installing this package, the documen-tation is available in the following directory: /usr/doc/packages/SMAWRhv-do/wizards.en

8.5 SF


rcsdShutdown Daemon of the Shutdown Facility

sdtoolinterface tool for the Shutdown Daemon

File formats

rcsd.cfgconfiguration file for the Shutdown Daemon

SA_blade.cfgconfiguration file for Blade Shutdown Agent

SA_ipmi.cfgconfiguration file for a Intelligent Platform Management Interface Shutdown Agent

SA_rps.cfgconfiguration file for a Remote Power Switch Shutdown Agent

SA_rsb.cfgconfiguration file for Remote Service Board Shutdown Agent

SA_wtinps.cfgconfiguration file for WTI NPS Shutdown Agent

116 U42144-J-Z100-6-76

Web-Based Admin View Manual pages

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k13

8.6 Web-Based Admin View


fjsvwvbsstop Web-Based Admin View

fjsvwvcnfstart, stop, or restart the web server for Web-Based Admin View

wvCntlstart, stop, or get debugging information for Web-Based Admin View

wvGetparamdisplay Web-Based Admin View's environment variable

wvSetparamset Web-Based Admin View environment variable

wvstatdisplay the operating status of Web-Based Admin View

U42144-J-Z100-6-76 117

9 Appendix—Important Web-Based Admin View settings

I If you are using Global Link Services, refer to the Web-Based Admin View Operation Guide to set up Web-Based Admin View in a GLS environment. Refer to the chapter “Web-Based Admin View configuration” for details on using wvconf to configure Web-Based Admin View.

Web-Based Admin View places a number of significant commands in the following directory:

/etc/opt/FJSVwvbs/etc/bin

The wvSetparam command found in this directory is used to set Web-Based Admin View environment variables. The ones most commonly used in setting up PRIMECLUSTER configurations are listed in table 11.

You can use the wvGetparam command to display the Web-Based Admin View environment variables. Refer to the chapter “Manual pages” for more infor-mation.

Parameter Possible Values

Example Description

primary-server IP address 172.25.200.4 The IP address of the primary management server.

secondary-server IP address 172.25.200.5 The IP address of the secondary management server.

mip IP address or node name

172.25.200.4 or shasta1

This is the IP address or name of the local interface that Web-Based Admin View uses for communica-tions between the monitored node(s) and the management server(s).

Table 11: Important Web-Based Admin View environment settings

118 U42144-J-Z100-6-76

Appendix—Important Web-Based Admin View settings

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k14

I When Web-Based Admin View is initially installed, the IP addresses of the primary and secondary management servers (given by primary-server and secondary-server, respectively) are automatically set to the IP address of the local node. This, in effect, configures the local node to be the primary management server. However, in a clustered environment, all the nodes in the cluster must have the same primary management server. Thus, you must configure Web-Based Admin View on each node in the cluster. You will also need to configure the primary and secondary management server(s) if they are outside the cluster.

httpip IP address or node name

172.25.219.83 or shasta1

This is the IP address or name of the local interface on which Web-Based Admin View's webserver will listen for requests.

The following parameters are associated with secondary server autoselection

server-election on, off on If on, the local node is a candidate for secondary server automatic migration.

server-ha on, off on If set to on on the primary management server, then automatic migration is enabled.

group-addr IP multicast or broadcast address

231.25.219.83 This is the IP group address used in the automatic migration process.

Parameter Possible Values

Example Description

Table 11: Important Web-Based Admin View environment settings

U42144-J-Z100-6-76 119

10 Appendix—Private network addresses

The Internet Assigned Number Authority (IANA) has defined three address ranges that are set aside for private subnets:

Subnet(s) Class Subnetmask10.0.0.0 A 255.0.0.0172.16.0.0 .. 172.31.0.0 B 255.255.0.0192.168.0.0 .. 192.168.255.0 C 255.255.255.0

Packets using addresses from these subnets are guaranteed not to be routed to public networks.

The use of these subnets is recommended for CIP addresses and for PRIVATE declarations in SIS configuration files.

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k15

U42144-J-Z100-6-76 121

11 Appendix—Cluster planning worksheet

table 12 is a blank worksheet to aid in planning your configuration. Refer to the chapter “Site planning” for information on filling out the worksheet.

Cluster Name

Node 1 Node 2

Node Name


Primary RMS network

Name

Address


Name

Address

Name

Address

Administrative LAN

Name

Address

Public LAN

Name

Address


122 U42144-J-Z100-6-76

Appendix—Cluster planning worksheet

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k16

U42144-J-Z100-6-76 123

12 Appendix—System parametersThis appendix discusses setting system parameters for PRIMECLUSTER-based configurations.

12.1 System parameters for RMS configurations

When the RMS package is installed, it will verify that the kernel tunables listed below are at or above the required minimum values. If any tunable is below the listed minimum, it will be automatically increased to the minimum value. The following system tunables are reset with the increased values in /etc/sysctl.conf:

kernel.msgmnb = 4194304kernel.msgmax = 16384kernel.msgmni = 8192

I If above requirements are already met, no change will be made to the system.

The parameters will be removed from /etc/sysctl.conf when the RMS package is removed via the rpm -e command.

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k18

U42144-J-Z100-6-76 125

13 Appendix—PRIMECLUSTER ports

table 13 lists the ports used by PRIMECLUSTER.

Int = Cluster interconnectPL = Public LANAL = Administrative LANCN = Cluster node

I Some of the ports and products mentioned in table 13 may not be available with Linux.

Pro

du

ct

Lo

cati

on

UD

P

TC

P

Net

wo

rk

Sen

d/R

ecei

ve

Co

nfi

gu

rabl

e

Co

mm

ents

Web-Based Admin View

Cluster node

9796 None AL S, R Yes fjwv_g (FJSVwvbs group RMI)

Cluster node

9799 AL S, R Yes fjwv_c (FJSVwvbs client RMI)

Cluster node

9798 AL S, R Yes fjwv_s (FJSVwvbs server RMI)

Cluster node

9797 AL S, R Yes fjwv_n (FJSVwvbs node RMI)

Cluster node

8081* AL S, R Yes fjwv_h (FJSVwvcnf Web Port); * refer to the Section “http port number” that follows.

Table 13: PRIMECLUSTER ports

126 U42144-J-Z100-6-76

Appendix—PRIMECLUSTER ports

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k19

RMS Cluster node

8000 Int S, R No wrapper

Cluster node

9786 Int S, R Yes rmshb

Cluster node

7 (echo) Int S, R Yes Only needed for rsh/rcp

WT Cluster node

9786 Int R Yes hvutil -A API

SF Cluster node

2316 Int S, R Yes rcsd

Cluster node

2137-* AL S, R Yes * number of hosts

Cluster node

23 (telnet)

AL S, R No SA_wtinps

Cluster node

3173 AL S, R No SA_rsb

Cluster node

3173 AL S, R No SA_rps

SNMP Cluster node

161 Int, PL

S, R No Emanate Master Agent

Cluster node

162 Int, PL

S, R No SNMP trap receive

Cluster node

8161 Int, PL

S, R No UCD Master SNMP Agent

Pro

du

ct

Lo

cati

on

UD

P

TC

P

Net

wo

rk

Sen

d/R

ecei

ve

Co

nfi

gu

rab

le

Co

mm

ents

Table 13: PRIMECLUSTER ports

U42144-J-Z100-6-76 127


Changing the http port number

The initial value of the port number for access to a management server from the client Web browser is 8081.

You may need to change the Web-Based Admin View port number if Web-Based Admin View does not operate normally, or the default port number (8081) is competing with Transparent Proxy (tproxy) or other products.

To modify the setup, execute the following command for all management servers and monitoring nodes:

# /etc/opt/FJSVwvbs/etc/bin/wvSetport fjwv-h=<port number>

To ensure that the current port number is set to 8081, execute the following command for all management servers and cluster nodes:

# /etc/opt/FJSVwvbs/etc/bin/wvSetport fjwv-h=8081

I If you change the port number for the Web browser, ensure that you update /etc/services on all management servers and cluster nodes as well.

If a URL is registered as a bookmark, change the URL port number.

After changes are complete, restart Web-Based Admin View and access the management server. Refer also to the PRIMECLUSTER Web-Based Admin View Operation Guide for more details.

128 U42144-J-Z100-6-76


© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k19

U42144-J-Z100-6-76 129

14 Appendix—TroubleshootingThis appendix contains information for troubleshooting PRIMECLUSTER.

14.1 cluster_install log files

If the cluster_install command fails, detailed information can be found in the following log files:

/var/install/logs/cluster_install.1 (log file of CD1)

/var/install/logs/cluster_install.2 (log file of CD2)

You can use these log file to determine and eliminate the cause of an installation failure.

14.2 cluster_install error messages

● Message:Installation failed.

Explanation:The installation process failed.

Solution:Refer to the ERROR message and log file, eliminate the cause of the failure, then retry the command.

● Message:ERROR: syntax error.

Explanation:Invalid command options were specified.

Solution:Check the command syntax, and start with the correct options.

130 U42144-J-Z100-6-76

cluster_install error messages Appendix—Troubleshooting

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k21

● Message:ERROR: To use this installer you will need to be the root user.

Explanation:The user is not a root user.

Solution:Only root users can execute the installer. Start the installer with root user authority.

● Message:ERROR: /tmp needs TMP_LEAST KB at least.

Explanation:The available size of /tmp file system is too small.

Solution:Please check the size of /tmp file system.

● Message:ERROR: /var needs VAR_LEAST KB at least.

Explanation:The available size of /var file system is too small.

Solution:Please check the size of /var file system.

● Message:ERROR: Please install the first CD-ROM at first.

Explanation:The product set installation should be started with CD1.

Solution:Start the product set installation with CD1.

● Message:ERROR: Package <package> of product <product> has already been installed.

Explanation:The package package has been already installed.

Solution:Use the -u (upgrade mode) or -f (force mode) options of cluster_install, or remove the package <package> with cluster_uninstall, then retry the command.

U42144-J-Z100-6-76 131

Appendix—Troubleshooting cluster_install error messages

● Message:ERROR: The installation process is running now.

Explanation:Another installation related process is running.

Solution:Wait for the termination of the other process.

I If this message displays without any other installation-related processes, you need to remove the temporal flag files /tmp/cluster_install and /tmp/cluster_uninstall, then retry the command.

● Message:ERROR: platform <platform> not supported.

Explanation:The detected platform of your system environment is not supported by the installer.

Solution:Check if the PRIMECLUSTER software supports your system environment or not.

● Message:ERROR: product set <product_set> on platform <platform> not supported.

Explanation:The product set is not supported on the platform of your system environment.

Solution:Check if the PRIMECLUSTER software you tried to install supports your system environment or not.

● Message:ERROR: no package of product set <product_set> on CDx

Explanation:Cannot find any packages of the product set on the CD that you are using.

Solution:Check the CD number of mounted PRIMECLUSTER CD, and verify that it contains the software you tried to install

132 U42144-J-Z100-6-76

cluster_install error messages Appendix—Troubleshooting

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k21

● Message:ERROR: no package of product <product> on CDx

Explanation:Cannot find any packages of the product on the CD that you are using.

Solution:Check the CD number of mounted PRIMECLUSTER CD, and verify that it contains the software you tried to install

● Message:ERROR: product <product1> and <product2> contains the same package <package>

Explanation:The products that the installer tried to install have the same package.

Solution:The installer cannot install the products each of which has the same package simultaneously. Check the options that you specified.

● Message:ERROR: failed: rpm *

Explanation:Failed to execute rpm *.

Solution:Consult the manual page for rpm(8).

● Message:ERROR: internal error: <error>

Explanation:An internal error occurred.

Solution:Please make a note of the message and contact customer support.

● Message:Please see the following log file./var/log/install/cluster_install.x

Explanation:Refer to the indicated log file to determine the cause of failure.

U42144-J-Z100-6-76 133

Appendix—Troubleshooting cluster_uninstall error messages

14.3 cluster_uninstall error messages

● Message:Uninstallation failed.

Explanation:The uninstallation process failed.

Solution:Refer to the ERROR message or log file, eliminate the cause of the failure, then retry the command.

● Message:ERROR: syntax error

Explanation:Invalid command options were specified.

Solution:Check the command syntax, and start with correct options.

● Message:ERROR: To use this installer you will need to be the root user.

Explanation:The user is not a root user.

Solution:Only root users can execute the uninstaller. Start the uninstaller with root user authority.

● Message:ERROR: /tmp needs TMP_LEAST KB at least.

Explanation:The available size of /tmp file system is too small.

Solution:Please check the size of /tmp file system.

134 U42144-J-Z100-6-76

cluster_uninstall error messages Appendix—Troubleshooting

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k21

● Message:ERROR: /var needs VAR_LEAST KB at least.

Explanation:The available size of /var file system is too small.

Solution:Please check the size of /var file system.

● Message:ERROR: CF driver is loaded.

Explanation:CF driver is loaded on the current system.

Solution:Unload the CF driver, then retry the command.

● Message:ERROR: there exists GDS object(s)

Explanation:There exists GDS objects on the current system.

Solution:Remove the GDS objects, then retry the command.

● Message:ERROR: The installation process is running now.

Explanation:Another installation-related process is running.

Solution:Wait for the termination of the other process.

I If this message displays without any other installation related processes, you need to remove temporal flag files /tmp/cluster_install and /tmp/cluster_uninstall, then retry the command.

● Message:ERROR: product set <product_set> on platform <platform> not supported.

Explanation:The product set is not supported on the platform of your system environment.

U42144-J-Z100-6-76 135

Appendix—Troubleshooting cluster_uninstall error messages

Solution:Specify a valid product set.

● Message:ERROR: product <product> on platform <platform> not supported.

Explanation:The product is not supported on the platform of your system environment.

Solution:Specify a valid product.

● Message:ERROR: failed: rpm *

Explanation:Failed to execute rpm *.

Solution:Consult the manual page for rpm(8).

● Message:ERROR: internal error: <error>

Explanation:An internal error occurred.

Solution:Please make a note of the message and contact customer support.

● Message:Please see the following log file./var/log/install/cluster_uninstall.x

Explanation:Refer to the indicated log file to determine the cause of failure.

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

002

thro

ugh

200

7

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\c

om

mon

\Ins

tall.

k21

U42144-J-Z100-6-76 137

AbbreviationsAC

Access Client

APIapplication program interface

bmbase monitor

CCBRCluster Configuration Backup/Restore

CFCluster Foundation or Cluster Framework

CIMCluster Integrity Monitor

CIPCluster Interface Provider

CLIcommand-line interface

CRMCluster Resource Management

DLPIData Link Provider Interface

ENSEvent Notification Services

GDSGlobal Disk Services

GFSGlobal File Services

138 U42144-J-Z100-6-76

Abbreviations

© c

ogni

tas.

Ges

ells

chft

für

Tech

nik-

Dok

ume

ntat

ion

mb

H 2

002

thr

oug

h 20

07

Pfa

d: D

:\Dat

en\

PC

L\4

.2A

20L

x\u4

2144

.6\e

\Inst

allS

AP

\Inst

allS

AP.

abk

GLSGlobal Link Services

GUIgraphical user interface

HAhigh availability

ICFInternode Communication Facility

I/Oinput/output

JOINcluster join services module

LANlocal area network

MDSMeta Data Server

MIBManagement Information Base

MMBManagement Board

NICnetwork interface card

NSMNode State Monitor

OEoperating environment

OPSOracle Parallel Server

U42144-J-Z100-6-76 139

Abbreviations

OSDoperating system dependant

PASParallel Application Services

RCCURemote Console Control Unit

RCIRemote Cabinet Interface

RMSReliant Monitor Services

RTPReliant Telco Product

SAShutdown Agent

SANStorage Area Network

SCONsingle console software

SDShutdown Daemon

SFShutdown Facility

SISScalable Internet Services

VIPVirtual Interface Provider

© c

ogni

tas.

Ges

ells

chft

für

Tech

nik-

Dok

ume

ntat

ion

mb

H 2

002

thr

oug

h 20

07

Pfa

d: D

:\Dat

en\

PC

L\4

.2A

20L

x\u4

2144

.6\e

\Inst

allS

AP

\Inst

allS

AP.

abk

U42144-J-Z100-6-76 141

GlossaryItems in this glossary that apply to specific PRIMECLUSTER™ for the SAP® Business Suite™ components are indicated with the following notation:

● (PCS)—PRIMECLUSTER Configuration Services

● (RMS)—Reliant Monitor Services

● (SIS)—Scalable Internet Services

Some of these products may not be installed on your cluster. See your sales representative for more information.

activating a configuration (RMS)Preparing an RMS configuration to be run on a cluster. This involves two major actions: first, the configuration is generated on the host where the configuration was created or edited; second, the configuration is distributed to all nodes affected by the configuration. The user can activate a configuration using PCS, the Wizard Tools, or the CLI.

See also generating a configuration (RMS), distributing a configuration (RMS).

administrative LANAn optional private local area network (LAN) used for administrative commands to the nodes in the cluster. To provide an extra level of security, normal users do not have access to the administrative LAN. In PRIMECLUSTER™ for the SAP® Business Suite™ configurations, the System Console and Cluster Console reside on the administrative LAN if one is present.

See also public LAN.

APISee Application Program Interface.

application (RMS)In the RMS context, an application object is a special resource used to group other resources into a logical collection. Typically, it is used to represent a real-world application or application suite in a high-avail-ability configuration.

142 U42144-J-Z100-6-76

Glossary

© c

ogni

tas.

Ges

ells

chft

für

Tech

nik-

Dok

ume

ntat

ion

mb

H 2

002

thro

ugh

20

07

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\

u42

144

.6\e

\com

mo

n\In

sta

ll.m

ix

Application Program InterfaceA shared boundary between a service provider and the application that uses that service.

application template (RMS)A predefined group of object definition value choices used by PCS, the Wizard Tools, or the PCS Wizard Kit to create object definitions for a specific type of application.

attribute (RMS)The part of an object definition that specifies how the base monitor acts and reacts for a particular object type during normal operations.

automatic switchover (RMS)The procedure by which RMS automatically switches control of a userApplication over to another node after specified conditions are detected.

See also directed switchover (RMS), failover (RMS, SIS), switchover (RMS), symmetrical switchover (RMS).

availabilityAvailability describes the need of most enterprises to operate applica-tions via the Internet 24 hours a day, 7 days a week. The relationship of the actual to the planned usage time determines the availability of a system.

base monitor (RMS)The RMS module that maintains the availability of resources. The base monitor is supported by daemons and detectors. Each node being monitored has its own copy of the base monitor.

Cache FusionThe improved interprocess communication interface in Oracle 9i that allows logical disk blocks (buffers) to be cached in the local memory of each node. Thus, instead of having to flush a block to disk when an update is required, the block can be copied to another node by passing a message on the interconnect, thereby removing the physical I/O overhead.

CCBRSee Cluster Configuration Backup and Restore.

U42144-J-Z100-6-76 143

Glossary

child (RMS)A resource defined in the configuration file that has at least one parent. A child can have multiple parents, and can either have children itself (making it also a parent) or no children (making it a leaf object).

See also resource (RMS), object (RMS), parent (RMS).

clusterA set of computers that work together as a single computing source. Specifically, a cluster performs a distributed form of parallel computing.

See also RMS configuration (RMS).

Cluster AdminA Java-based, OS-independent management tool for PRIME-CLUSTER™ for the SAP® Business Suite™ products such as SIS, RMS and PCS. Cluster Admin is available from the Web-Based Admin View interface.

See also Scalable Internet Services (SIS), Reliant Monitor Services (RMS), PRIMECLUSTER Configuration Services (PCS), Web-Based Admin View.

Cluster Configuration Backup and RestoreCCBR provides a simple method to save the current PRIMECLUSTER™ for the SAP® Business Suite™ configuration information of a cluster node. It also provides a method to restore the configuration information.

Configuration Definition Language (PCS)The syntax for PCS configuration templates.

See also PRIMECLUSTER Configuration Services (PCS).

configuration file (RMS)In the RMS context, the single file that defines the monitored resources and establishes the interdependencies between them. The default name of this file is config.us.

consoleSee single console.

custom detector (RMS)See detector (RMS).

144 U42144-J-Z100-6-76

Glossary

© c

ogni

tas.

Ges

ells

chft

für

Tech

nik-

Dok

ume

ntat

ion

mb

H 2

002

thro

ugh

20

07

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\

u42

144

.6\e

\com

mo

n\In

sta

ll.m

ix

custom type (RMS)See generic type (RMS).

daemonA continuous process that performs a specific function repeatedly.

database node (SIS)Nodes that maintain the configuration, dynamic data, and statistics in a SIS configuration.

See also gateway node (SIS), service node (SIS), Scalable Internet Services (SIS).

detector (RMS)A process that monitors the state of a specific object type and reports a change in the resource state to the RMS base monitor.

DHCPDynamic Host Control Protocol. A standard method of delivering infor-mation to a host at boot time. This is most often used to dynamically assign the host’s IP address and netmask, but many other parameters are possible, including domain names, DNS servers, and time servers.

directed switchover (RMS)The RMS procedure by which an administrator switches control of a userApplication over to another node.

See also automatic switchover (RMS), failover (RMS, SIS), switchover (RMS), symmetrical switchover (RMS).

distributing a configuration (RMS)The process of copying a configuration file and all of its associated scripts and detectors to all nodes affected by the configuration. This is normally done automatically when the configuration is activated using PCS, the Wizard Tools, or the CLI.

See also activating a configuration (RMS), generating a configuration (RMS).

environment variablesVariables or parameters that are defined globally.

U42144-J-Z100-6-76 145

Glossary

error detection (RMS)The process of detecting an error. For RMS, this includes initiating a log entry, sending a message to a log file, or making an appropriate recovery response.

failover (RMS, SIS)With SIS, this process switches a failed node to a backup node. With RMS, this process is known as switchover.

See also automatic switchover (RMS), directed switchover (RMS), switchover (RMS), symmetrical switchover (RMS).

gateway node (SIS)Gateway nodes have an external network interface. All incoming packets are received by this node and forwarded to the selected service node, depending on the scheduling algorithm for the service.

See also service node (SIS), database node (SIS), Scalable Internet Services (SIS).

generating a configuration (RMS)The process of creating a single configuration file that can be distributed to all nodes in the configuration and activated at a later time. This is normally done automatically when the configuration is activated using PCS, the RMS Wizards, or the CLI.

See also activating a configuration (RMS), distributing a configuration (RMS).

generic type (RMS)An object type which has generic properties. A generic type is used to customize RMS for monitoring resources that cannot be assigned to one of the supplied object types.

See also object type (RMS).

graph (RMS)See system graph (RMS).

graphical user interfaceA computer interface with windows, icons, toolbars, and pull-down menus that is designed to be simpler to use than the command-line interface.

146 U42144-J-Z100-6-76

Glossary

© c

ogni

tas.

Ges

ells

chft

für

Tech

nik-

Dok

ume

ntat

ion

mb

H 2

002

thro

ugh

20

07

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\

u42

144

.6\e

\com

mo

n\In

sta

ll.m

ix

GUI See graphical user interface.

high availabilityA system design philosophy in which redundant resources are employed to avoid single points of failure.

See also Reliant Monitor Services (RMS).

Intelligent Platform Management InterfaceA firmware and hardware specification that provides common interfaces for monitoring and managing computers. IPMI operates through an onboard Baseboard Management Controller (BMC) on the target machine to provide OS-independent remote management functions, whether or not the target machine is powered on.

Internet Protocol addressA numeric address that can be assigned to computers or applications.

See also IP aliasing.

Internode Communications facilityThis module is the network transport layer for all PRIMECLUSTER™ for the SAP® Business Suite™ internode communications. It interfaces by means of OS-dependent code to the network I/O subsystem and guarantees delivery of messages queued for transmission to the desti-nation node in the same sequential order unless the destination node fails.

IP addressSee Internet Protocol address.

IP aliasingThis enables several IP addresses (aliases) to be allocated to one physical network interface. With IP aliasing, the user can continue communicating with the same IP address, even though the application is now running on another node.

See also Internet Protocol address.

IPMISee Intelligent Platform Management Interface.

U42144-J-Z100-6-76 147

Glossary

keywordA word that has special meaning in a programming language. For example, in an RMS configuration file, the keyword object identifies the kind of definition that follows.

leaf object (RMS)A bottom object in a system graph. In the configuration file, this object definition is at the beginning of the file. A leaf object does not have children.

link (RMS)Designates a child or parent relationship between specific resources.

local area networkSee public LAN.

local nodeThe node from which a command or process is initiated.

See also remote node, node.

log fileThe file that contains a record of significant system events or messages. The ASCC control and satellite daemons maintain log files on every node on which they run. The Wizard Tools, PCS, the RMS base monitor, and RMS detectors each maintain their own log files as well.

Management BoardOne of the hardware units installed in PRIMEQUEST.

Management Information BaseA hierarchical database of information about the local network device. The database is maintained by network management software such as an SNMP agent.

See also Simple Network Management Protocol.

messageA set of data transmitted from one software process to another process, device, or file.

148 U42144-J-Z100-6-76

Glossary

© c

ogni

tas.

Ges

ells

chft

für

Tech

nik-

Dok

ume

ntat

ion

mb

H 2

002

thro

ugh

20

07

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\

u42

144

.6\e

\com

mo

n\In

sta

ll.m

ix

message queueA designated memory area which acts as a holding place for messages so they can be processed in the same order they were received.

MIBSee Management Information Base.

MMBSee Management Board.

mount pointThe point in the directory tree where a file system is attached.

multihostingMultiple controllers simultaneously accessing a set of disk drives.

native operating systemThe part of an operating system that is always active and translates system calls into activities.

nodeA host that is a member of a cluster.

object (RMS)A representation of a physical or virtual resource in the RMS configu-ration file or in a system graph.

See also leaf object (RMS), object definition (RMS), object type (RMS).

object definition (RMS)An entry in the configuration file that identifies a resource to be monitored by RMS. Attributes included in the definition specify properties of the corresponding resource.

See also attribute (RMS), object (RMS).

object type (RMS)A category of similar resources monitored as a group, such as disk drives. Each object type has specific properties, or attributes, which limit or define what monitoring or action can occur. When a resource is associated with a particular object type, attributes associated with that object type are applied to the resource.

See also generic type (RMS).

U42144-J-Z100-6-76 149

Glossary

online maintenanceThe capability of adding, removing, replacing, or recovering devices without shutting or powering off the node.

Oracle Real Application Clusters (RAC)Oracle RAC allows access to all data in a database to users and applica-tions in a clustered or MPP (massively parallel processing) platform. Formerly known as Oracle Parallel Server (OPS).

parent (RMS)An object in the RMS configuration file or system graph that has at least one child.

See also child (RMS), configuration file (RMS), leaf object (RMS), system graph (RMS).

PCSSee PRIMECLUSTER Configuration Services (PCS).

PCS Wizard Kit (PCS)RMS configuration products that have been designed for specific appli-cations. Each component of the PCS Wizard Kit includes customized default settings, subapplications, detectors, and scripts. These appli-cation wizards also tailor the PCS interface to provide controls for the additional features.

See also PRIMECLUSTER Configuration Services (PCS), Reliant Monitor Services (RMS).

primary node (RMS)The default node on which a user application comes online when RMS is started. This is always the node name of the first child listed in the userApplication object definition.

PRIMECLUSTER Configuration Services (PCS)The graphical configuration interface for PRIMECLUSTER™ for the SAP® Business Suite™ products. PCS uses standard templates written in Configuration Definition Language (CDL) to provide a user-friendly configuration environment for products such as RMS. The standard templates can be modified or replaced to provide a customized interface for specific applications or installations.

150 U42144-J-Z100-6-76

Glossary

© c

ogni

tas.

Ges

ells

chft

für

Tech

nik-

Dok

ume

ntat

ion

mb

H 2

002

thro

ugh

20

07

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\

u42

144

.6\e

\com

mo

n\In

sta

ll.m

ix

private network addressesPrivate network addresses are a reserved range of IP addresses specified by the Internet Corporation for Assigned Names and Numbers (ICANN). Modern switches and routers prevent these addresses from being routed to the Internet, allowing two or more organizations to assign the same private addresses for internal use without causing conflicts or security risks.

private resource (RMS)A resource accessible only by a single node and not accessible to other RMS nodes.

See also resource (RMS), shared resource.

public LANThe local area network (LAN) by which normal users access a machine.

See also administrative LAN.

queueSee message queue.

redundancyThe capability of one component to assume the resource load of another physically similar component in case the original component fails or is shut down. Common examples include RAID hardware and/or RAID software to replicate data stored on secondary storage devices, multiple network connections to provide alternate data paths, and multiple nodes that can be dynamically reprovisioned to maintain critical services in a cluster.

Reliant Monitor Services (RMS)The package that maintains high availability of user-specified resources by providing monitoring and switchover capabilities.

remote nodeA node that is accessed through a LAN or telecommunications line.

See also local node, node.

reporting message (RMS)A message that a detector uses to report the state of a particular resource to the base monitor.

U42144-J-Z100-6-76 151

Glossary

resource (RMS)A hardware or software element (private or shared) that provides a function such as a mirrored disk, mirrored disk pieces, or a database server. A local resource is monitored only by the local node.

See also private resource (RMS), shared resource.

resource definition (RMS)See object definition (RMS).

resource label (RMS)The name of the resource as displayed in a system graph.

resource state (RMS)Current state of a resource.

RMSSee Reliant Monitor Services (RMS).

RMS commands (RMS)Commands that enable RMS resources to be administered from the command line.

RMS configuration (RMS)A configuration made up of two or more nodes connected to shared resources. Each node has its own copy of operating system and RMS software, as well as its own applications.

RMS Wizard Kit (RMS)RMS configuration products that have been designed for specific appli-cations. Each component of the Wizard Kit includes customized default settings, subapplications, detectors, and scripts. These application wizards also tailor the RMS Wizard Tools interface to provide controls for the additional features.

See also RMS Wizard Tools (RMS), Reliant Monitor Services (RMS).

RMS Wizard Tools (RMS)A software package composed of various configuration and adminis-tration tools used to create and manage applications in an RMS config-uration.

See also RMS Wizard Kit (RMS), Reliant Monitor Services (RMS).

152 U42144-J-Z100-6-76

Glossary

© c

ogni

tas.

Ges

ells

chft

für

Tech

nik-

Dok

ume

ntat

ion

mb

H 2

002

thro

ugh

20

07

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\

u42

144

.6\e

\com

mo

n\In

sta

ll.m

ix

SANSee Storage Area Network.

scalabilityThe ability of a computing system to efficiently handle any dynamic change in work load. Scalability is especially important for Internet-based applications where growth caused by Internet usage presents a scalable challenge.

Scalable Internet Services (SIS)The package that dynamically balances network traffic loads across cluster nodes while maintaining normal client/server sessions for each connection.

SCONSee single console.

script (RMS)A shell program executed by the base monitor in response to a state transition in a resource. The script may cause the state of a resource to change.

service node (SIS)Service nodes provide one or more TCP services (such as FTP, Telnet, and HTTP) and receive client requests forwarded by the gateway nodes.

See also database node (SIS), gateway node (SIS), Scalable Internet Services (SIS).

SFSee Shutdown Facility.

shared resourceA resource, such as a disk drive, that is accessible to more than one node.

See also private resource (RMS), resource (RMS).

U42144-J-Z100-6-76 153

Glossary

Shutdown FacilityThe PRIMECLUSTER™ for the SAP® Business Suite™ interface that manages the shutdown and startup of cluster nodes. The SF is automat-ically invoked during failover operations. It also notifies other PRIME-CLUSTER™ for the SAP® Business Suite™ products of the successful completion of node shutdown so that recovery operations can begin.

Simple Network Management ProtocolA set of protocols that facilitates the exchange of information between managed network devices. The protocols are implemented by software agents residing in the devices. Each agent can read and write data in the local Management Information Base (MIB) in response to SNMP requests from other devices on the network.

See also Management Information Base.

single consoleThe workstation that acts as the single point of administration for nodes being monitored by RMS. The single console software, SCON, is run from the single console.

SISSee Scalable Internet Services (SIS).

SNMPSee Simple Network Management Protocol.

stateSee resource state (RMS).

Storage Area NetworkThe high-speed network that connects multiple, external storage units and storage units with multiple computers. The connections are generally fiber channels.

switchover (RMS)The process by which RMS switches control of a userApplication over from one monitored node to another.

See also automatic switchover (RMS), directed switchover (RMS), failover (RMS, SIS), symmetrical switchover (RMS).

154 U42144-J-Z100-6-76

Glossary

© c

ogni

tas.

Ges

ells

chft

für

Tech

nik-

Dok

ume

ntat

ion

mb

H 2

002

thro

ugh

20

07

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\

u42

144

.6\e

\com

mo

n\In

sta

ll.m

ix

symmetrical switchover (RMS)This means that every RMS node is able to take on resources from any other RMS node.

See also automatic switchover (RMS), directed switchover (RMS), failover (RMS, SIS), switchover (RMS).

system graph (RMS)A visual representation (a map) of monitored resources used to develop or interpret the RMS configuration file.

See also configuration file (RMS).

templateSee application template (RMS).

typeSee object type (RMS).

virtual diskA pseudo-device that allows a portion or a combination of physical disks to be treated as a single logical disk. The virtual disk driver is inserted between the highest level of the OS logical input/output (I/O) system and the physical device driver(s), allowing all logical I/O requests to be mapped to the appropriate area on the physical disk(s).

Web-Based Admin ViewA Java-based, OS-independent interface to PRIMECLUSTER™ for the SAP® Business Suite™ management components.

See also Cluster Admin.

wizard (RMS)An interactive software tool that creates a specific type of application using pretested object definitions.

Wizard Kit (RMS)See PCS Wizard Kit (PCS), RMS Wizard Kit (RMS).

Wizard Tools (RMS)See RMS Wizard Tools (RMS).

U42144-J-Z100-6-76 155

Dok

usch

ablo

nen

(OE

CB

ook)

V2.

1a v

om 0

7.03

.200

7by

S. T

hum

sS

ervi

ces&

Tool

s©

cog

nita

s G

mbH

200

2-20

071

8. J

uni 2

009

Sta

nd 1

2:26

.17

Pfa

d: D

:\Dat

en\

PC

L\4

.2A

20L

x\u4

2144

.6\e

\Inst

allS

AP

\Inst

allS

AP.

avz

FiguresFigure 1: PRIMECLUSTER hardware configuration without a console 16

Figure 2: Initial wvconf output . . . . . . . . . . . . . . . . . . . . 38

Figure 3: No command connectivity output . . . . . . . . . . . . . 38

Figure 4: wvconf checking for management servers . . . . . . . . 39

Figure 5: wvconf checking configuration files . . . . . . . . . . . . 39

Figure 6: wvconf change configuration output . . . . . . . . . . . . 40

Figure 7: wvconf configuring Web-Based Admin View . . . . . . . 41

Figure 8: Main Web-Based Admin View screen . . . . . . . . . . . 44

Figure 9: Node list . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Figure 10: Environment setup screen . . . . . . . . . . . . . . . . . 45

Figure 11: Displaying IP address of the primary management server 46

Figure 12: Node environment tab . . . . . . . . . . . . . . . . . . . 47

Figure 13: Displaying nodes . . . . . . . . . . . . . . . . . . . . . 48

Figure 14: Example applications and hardware configuration . . . . 53

Figure 15: Initial wvconf output . . . . . . . . . . . . . . . . . . . . 55

Figure 16: No command connectivity output . . . . . . . . . . . . . 56

Figure 17: wvconf checking for management servers . . . . . . . . 57

Figure 18: wvconf checking configuration files . . . . . . . . . . . . 57

Figure 19: wvconf change configuration output . . . . . . . . . . . . 58

Figure 20: wvconf configuring Web-Based Admin View . . . . . . . 58

Figure 21: Cluster Admin start-up window . . . . . . . . . . . . . . 60

Figure 22: Cluster Admin top window . . . . . . . . . . . . . . . . . 61

Figure 23: Initial connection choice window . . . . . . . . . . . . . 61

Figure 24: Cluster Admin main screen . . . . . . . . . . . . . . . . 62

156 U42144-J-Z100-6-76

Figures

Figure 25: Invoking the SF Configuration Wizard . . . . . . . . . . 62

Figure 26: Selecting the mode of SF configuration . . . . . . . . . 63

Figure 27: Choice of common configuration for all nodes . . . . . . 64

Figure 28: Choose SA to be added . . . . . . . . . . . . . . . . . 65

Figure 29: Configuring the NPS SA . . . . . . . . . . . . . . . . . 66

Figure 30: Add, delete, or edit a SA . . . . . . . . . . . . . . . . . 67

Figure 31: Configuring the NPS timeouts . . . . . . . . . . . . . . 68

Figure 32: Entering node weights and administrative IP addresses . 69

Figure 33: SF configuration files . . . . . . . . . . . . . . . . . . . 70

Figure 34: Saving SF configuration . . . . . . . . . . . . . . . . . 71

Figure 35: Status of SAs . . . . . . . . . . . . . . . . . . . . . . 72

Figure 36: Exiting SF configuration wizard . . . . . . . . . . . . . 73

Figure 37: Screen for a running a configuration . . . . . . . . . . . 73

Figure 38: RMS administration window . . . . . . . . . . . . . . . 75

Figure 39: Invoking PCS . . . . . . . . . . . . . . . . . . . . . . . 75

Figure 40: Selecting a node for PCS session . . . . . . . . . . . . 76

Figure 41: Entering a new configuration name . . . . . . . . . . . . 77

Figure 42: Selecting nodes . . . . . . . . . . . . . . . . . . . . . . 78

Figure 43: Configuration Start window . . . . . . . . . . . . . . . . 79

Figure 44: Choosing the application template . . . . . . . . . . . . 81

Figure 45: Changing the application name . . . . . . . . . . . . . . 82

Figure 46: Viewing Generic template information . . . . . . . . . . 83

Figure 47: Available nodes for an application . . . . . . . . . . . . 84

Figure 48: Selected nodes for an application . . . . . . . . . . . . 85

Figure 49: Beginning a subapplication configuration . . . . . . . . . 86

Figure 50: CommandLine subapplication parameters . . . . . . . . 88

U42144-J-Z100-6-76 157

Figures

Dok

usch

ablo

nen

(OE

CB

ook)

V2.

1a v

om 0

7.03

.200

7by

S. T

hum

sS

ervi

ces&

Tool

s©

cog

nita

s G

mbH

200

2-20

071

8. J

uni 2

009

Sta

nd 1

2:26

.17

Pfa

d: D

:\Dat

en\

PC

L\4

.2A

20L

x\u4

2144

.6\e

\Inst

allS

AP

\Inst

allS

AP.

avz

Figure 51: Additional subapplications . . . . . . . . . . . . . . . . . 89

Figure 52: Consistent configuration tree . . . . . . . . . . . . . . . 90

Figure 53: Saving a configuration with the menu . . . . . . . . . . . 91

Figure 54: Message after successful save operation . . . . . . . . . 91

Figure 55: Activating a configuration . . . . . . . . . . . . . . . . . 92

Figure 56: Activation succeeded . . . . . . . . . . . . . . . . . . . 92

Figure 57: cluster_uninstall output . . . . . . . . . . . . . . . . . . 102

Figure 58: Cluster Admin start-up window . . . . . . . . . . . . . . 107

Figure 59: Cluster Admin top window . . . . . . . . . . . . . . . . . 108

Figure 60: Choosing an initial node . . . . . . . . . . . . . . . . . . 108

Figure 61: RMS administration window . . . . . . . . . . . . . . . . 109

Figure 62: Invoking PCS . . . . . . . . . . . . . . . . . . . . . . . 109

Figure 63: Selecting a node for PCS session . . . . . . . . . . . . . 110

Figure 64: Selecting PCS configuration . . . . . . . . . . . . . . . . 110

Figure 65: Activating PCS configuration . . . . . . . . . . . . . . . 111

Figure 66: Activation succeeded . . . . . . . . . . . . . . . . . . . 111

Figure 67: Exiting PCS . . . . . . . . . . . . . . . . . . . . . . . . 111

Figure 68: Starting RMS . . . . . . . . . . . . . . . . . . . . . . . 112

U42144-J-Z100-6-76 159

TablesTable 1: Cluster site planning worksheet . . . . . . . . . . . . . 17

Table 2: Disk space requirements by category . . . . . . . . . . 19

Table 3: Space requirements for PRIMECLUSTER Enterprise Edition . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Table 4: GUI user groups . . . . . . . . . . . . . . . . . . . . . 24

Table 5: Product sets . . . . . . . . . . . . . . . . . . . . . . . 28

Table 6: PCS Wizard product codes . . . . . . . . . . . . . . . . 28

Table 7: Packages for an external server . . . . . . . . . . . . . 32

Table 8: Cluster site planning worksheet . . . . . . . . . . . . . 52

Table 9: Web-Based Admin View parameters . . . . . . . . . . . 53

Table 10: PRIMECLUSTER configuration files . . . . . . . . . . . 96

Table 11: Important Web-Based Admin View environment settings 117

Table 12: Cluster site planning worksheet . . . . . . . . . . . . . 121

Table 13: PRIMECLUSTER ports . . . . . . . . . . . . . . . . . . 125

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

enta

tion

mbH

200

2 th

rou

gh 2

007

Pfa

d: D

:\D

ate

n\P

CL

\4.2

A20

Lx\u

4214

4.6

\e\In

stal

lSA

P\In

stal

lSA

P.tv

z

U42144-J-Z100-6-76 161

Index

/etc/host.conf 21/etc/hosts 21/etc/nsswitch.conf 21/etc/services 127/etc/sysctl.conf 123

Aadding

applications, PCS 80cluster nodes, PCS 79

administrator privileges 24applets, Java, trusted 59

BBase GUIs

disk space 19FJSVwvbs 19FJSVwvmpc 19SMAWrcadm 19SMAWrcaja 19

Base_GUIs packages 32BIOS setup 20boot options 20browsers

changing port number 127environments 23Java applets 23updating /etc/services 127

Cchoosing nodes 78cladmin 24cldevparam 113CLI

See Command Line Interfaceclmmbmonctl 113clmmbsetup 113clmon 24clroot 24cluster

interconnect networks 54interconnects 15nodes 15nodes, installing 54

Cluster AdminBase_GUIs packages 32Japanese translation package 33Java applets 23package 33privileges 25start-up window 60, 107tabs 75, 109top window 61, 108Windows PC 54

cluster planning worksheet 121cluster_install 34

codes 32error messages 129log files 129

cluster_uninstalloutput 102removing packages 34

Command Line Interfacechecking Web-Based Admin

View 42installer 27installing with 9, 27

commandsMA 113

configuration, initial 46configuring

new configuration 77NPS SA 66, 68power management 20Web-Based Admin View 52

creatingconfigurations 77SF configuration 63

crossover cable 54

162 U42144-J-Z100-6-76

Index

© c

ogni

tas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH

20

02 th

rou

gh 2

007

P

fad:

D:\D

ate

n\P

CL

\4.2

A20

Lx\

u42

144

.6\e

\Inst

allS

AP

\Inst

allS

AP.

six

Ddisabling power management 20disk space requirements 19DNS 21documentation,

PRIMECLUSTER 10

Eerror messages, cluster_install 129example installation 51external management server 32

Ffile system

error message 130opt 20root 20usr 20var 20

FJSVwvbs 19fjsvwvbs 116fjsvwvcnf 116FJSVwvmpc 19

GGeneric application template 80GFS

See Global File ServicesGlobal Disk Services

upgrade 94Global File Services

upgrade 94Global Link Services

upgrade 94Web-Based Admin View

configuration 117GLS

See Global Link Servicesgnome 23group-addr 118

Hhardware

installing 16requirements 32

hosts entry 21See also /etc/hosts

httpip 118hvassert 114hvcm 114hvconfig 114hvdisp 114hvdist 114hvdump 114hvenv.local 115hvgdmake 114hvlogclean 114hvrclev 114hvreset 114hvsetenv 114hvshut 114hvswitch 114hvswitch command 87hvthrottle 114hvutil 114

Iinitial configuration 46Initial Connection Choice

window 61, 108installing

cluster nodes 54example 51preparing for 20product sets 27with CLI 9, 27

interconnectscluster 15cluster network 54

Internet Explorer 24invoking PCS GUI 75IP addresses

assigning 17non-routable 21

U42144-J-Z100-6-76 163

Index

JJava

Cluster Admin 23trusted applets 59

KKDE 23kernel parameters 20

Llocal node 118

MMA commands

cldevparam 113clmmbmonctl 113clmmbsetup 113

management serverdisplaying primary 46primary 117requirements 32secondary 117

manual pagesdisplay 113listing 113

Microsoft WindowsJava environment 54

mip 117modifying /etc/hosts 21

Nname look-up 21names

back up files 49IP 36node list 37nodes 78PCS configuration 74product sets 27user applications 99

Netscape 24network configuration worksheet 52node environment tab 47node names

PCS 78nodes

configuring Web-Based Admin View 35

names 21selecting 78

nsswitch.conf 20

Ooperator privileges 24opt file system 20optional software products 32

Ppackages

checking if installed 101compatibility 94installing 33installing new 103list 32manually removing 101removing old 102

PCSapplication template 80changing the application

name 82checking application

consistency 90configuration start window 79configuring a subapplication 86invoking GUI 75saving the configuration 91selecting nodes 75setting application

parameters 85starting 75viewing template information 83

PCS commandspcs_reinstall 113pcscui 113pcstool 113

pcs_reinstall 113pcscui 113pcstool 113

164 U42144-J-Z100-6-76

Index

© c

ogni

tas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH

20

02 th

rou

gh 2

007

P

fad:

D:\D

ate

n\P

CL

\4.2

A20

Lx\

u42

144

.6\e

\Inst

allS

AP

\Inst

allS

AP.

six

portschanging browser port 127PRIMECLUSTER 125

power management 20primary management server 52primary-server 117PRIMECLUSTER

documentation 10ports 125remote access 22software configuration 55

private network addresses 119privileges 25

administrator 24operator 24

product setsinstalling 27name 27

Rrcsd 115rcsd.cfg 115Red Hat 9requirements

hardware 32large RMS configuration 123management server 32software 32

restoringcluster configuration 33configuration 105Web-Based Admin View

configuration 35, 49, 105RMS commands

hvassert 114hvcm 114hvconfig 114hvdisp 114hvdist 114hvdump 114hvenv.local 115hvgdmake 114hvlogclean 114hvrclev 114

hvreset 114hvsetenv 114hvshut 114hvswitch 114hvthrottle 114hvutil 114

RMS configurations, system parameters 123

root file system 20root privilege 24

SSA_blade.cfg 115SA_ipmi.cfg 115SA_rps.cfg 115SA_rsb.cfg 115SA_wtinps.cfg 115SAs

See Shutdown Agentssaving

back up file 105PCS configuration 91RMS configuration 114SF configuration 71Web-Based Admin View

configuration 35, 49wvEnvsave command 49

sdtool 115sdxroot 24secondary management server 52secondary-server 117selecting

external management servers 39nodes 78

server-election 118server-ha 118setup 45SF commands

rcsd 115sdtool 115

SF configuration 63SF Wizard

choosing Shutdown Agents 65creating 63

U42144-J-Z100-6-76 165

Index

NPS 68Shutdown Agents

choosing 65NPS 66, 68status 71

SMAWrcadm 19SMAWrcaja 19SMAWRhv-ba 19SMAWRhv-do 19SMAWRhv-to 19SMAWRrms 19software requirements 32Standard Remote commands 22starting

CF Wizard in Cluster Admin 41PCS 75

subnets 119SUSE 9system administration network 15system parameters 123

Ttabs, Cluster Admin 75, 109TCP/IP

name look-ups 21networks 17

two-node cluster, components 15

Uuser groups, configuring 24usr file system 20

Vvar file system 20

WWeb-Based Admin View

configuration 52environment 45fails to start 21GUIs 9, 31modifying hosts file 21parameters 53restoring configuration 35, 49saving configuration 35, 49software 9, 31

Web-Based Admin View commandsfjsvwvbs 116fjsvwvcnf 116wvCntl 116wvGetparam 116wvSetparam 116wvstat 116

Windows PC 23, 54Wizard Tools

SMAWRhv-ba package 19SMAWRhv-do package 19SMAWRhv-to package 19

wvCntl 116wvEnvload 49wvEnvsave 49, 50wvGetparam 116wvroot 24, 25wvSetparam 116wvstat 116

© c

ogni

tas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH

20

02 th

rou

gh 2

007

P

fad:

D:\D

ate

n\P

CL

\4.2

A20

Lx\

u42

144

.6\e

\Inst

allS

AP

\Inst

allS

AP.

six

primecluster™ for sap® business suite™manuals.ts.fujitsu.com/file/7901/o42144e6.pdf ·...

Documents