PRIMECLUSTER™ · SIS eliminates single points of failure and ensures availability as follows: If...

© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.vor

Produktfamilie

PRIMECLUSTER™

Scalable Internet Services Configuration and Administration

RedakteurFujitsu Siemens Computers GmbH Paderborn33094 Paderborne-mail: email: [email protected].: (089) 636-00000Fax: (++49) 700 / 372 00001U42104-J-Z100-5-76Sprachen: En

Edition May 2002

© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.vor

Comments… Suggestions… Corrections…The User Documentation Department would like to know your opinion on this manual. Your feedback helps us to optimize our documentation to suit your individual needs.

Fax forms for sending us your comments are included at the back of the manual.

There you will also find the addresses of the relevant User Documentation Department.

Copyright and Trademarks

Copyright © 2000, 2001, 2002 Fujitsu Siemens Computers Inc and 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.

This manual was produced bycognitas. Gesellschaft für Technik-Dokumentation mbHwww.cognitas.de

This manual is printed on paper treated with chlorine-free bleach.

© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

995

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.ivz

Contents1 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1 Contents of this manual . . . . . . . . . . . . . . . . . . . . . . 11.2 Related documentation . . . . . . . . . . . . . . . . . . . . . . 11.3 Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.3.1 Notation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.3.1.1 Prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.3.1.2 Manual page section numbers . . . . . . . . . . . . . . . . . . . 21.3.1.3 The keyboard . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.3.1.4 Typefaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.3.1.5 Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.3.1.6 Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.3.2 Command syntax . . . . . . . . . . . . . . . . . . . . . . . . . 41.4 Important . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.1 SIS overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.1.1 Service nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . 62.1.2 Gateway nodes . . . . . . . . . . . . . . . . . . . . . . . . . . 62.1.3 Primary database node . . . . . . . . . . . . . . . . . . . . . . 62.1.4 Backup database node . . . . . . . . . . . . . . . . . . . . . . 62.2 Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62.3 SIS architecture . . . . . . . . . . . . . . . . . . . . . . . . . . 82.4 VIPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92.5 Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.6 Proxy addresses . . . . . . . . . . . . . . . . . . . . . . . . . 102.7 Private addresses . . . . . . . . . . . . . . . . . . . . . . . . 102.8 Cluster Admin . . . . . . . . . . . . . . . . . . . . . . . . . . 10

3 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 133.1 Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133.2 Configuration file . . . . . . . . . . . . . . . . . . . . . . . . . 143.2.1 Variable assignments . . . . . . . . . . . . . . . . . . . . . . 143.2.2 NODES declaration . . . . . . . . . . . . . . . . . . . . . . . 153.2.3 GATEWAYS declaration . . . . . . . . . . . . . . . . . . . . . 163.2.4 Interface definitions . . . . . . . . . . . . . . . . . . . . . . . 163.2.4.1 VIP addresses . . . . . . . . . . . . . . . . . . . . . . . . . . 163.2.4.2 Proxy addresses . . . . . . . . . . . . . . . . . . . . . . . . . 213.2.4.3 Private addresses . . . . . . . . . . . . . . . . . . . . . . . . 223.2.5 SIS configuration procedure . . . . . . . . . . . . . . . . . . . 223.3 Configuring with Cluster Admin . . . . . . . . . . . . . . . . . 233.3.1 Starting SIS . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

U42104-J-Z100-5-76

Contents

3.3.2 Logging in to Cluster Admin . . . . . . . . . . . . . . . . . . . 233.3.3 Displaying the SIS GUI main screen . . . . . . . . . . . . . . . 263.4 Starting with an existing configuration file . . . . . . . . . . . . . 273.5 SIS Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293.5.1 Adding nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . 323.5.2 Defining VIP, proxy, and private addresses . . . . . . . . . . . . 333.5.2.1 VIPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343.5.3 Completing the configuration . . . . . . . . . . . . . . . . . . . 483.6 Examples and configuration files . . . . . . . . . . . . . . . . . 55

4 Administration . . . . . . . . . . . . . . . . . . . . . . . . . . 574.1 Administering with Cluster Admin . . . . . . . . . . . . . . . . . 574.1.1 Using the GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . 574.1.1.1 SIS configuration tree . . . . . . . . . . . . . . . . . . . . . . . 584.1.2 Using the menu bar . . . . . . . . . . . . . . . . . . . . . . . . 694.1.2.1 File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694.1.2.2 Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 704.1.2.3 Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 714.1.2.4 Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 814.2 Administering with the CLI . . . . . . . . . . . . . . . . . . . . 844.3 SIS daemon . . . . . . . . . . . . . . . . . . . . . . . . . . . . 864.4 Displaying the status of SIS . . . . . . . . . . . . . . . . . . . . 864.4.1 Status by node . . . . . . . . . . . . . . . . . . . . . . . . . . 874.4.2 Status by service . . . . . . . . . . . . . . . . . . . . . . . . . 874.4.3 Status of SIS connections . . . . . . . . . . . . . . . . . . . . . 894.4.4 Showing the gateway node . . . . . . . . . . . . . . . . . . . . 914.5 Debug messages . . . . . . . . . . . . . . . . . . . . . . . . . 91

5 Syntax rules . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

6 Debugging and troubleshooting . . . . . . . . . . . . . . . . 976.1 dtcpdbg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 976.2 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . 99

7 Manual pages . . . . . . . . . . . . . . . . . . . . . . . . . 101

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

U42104-J-Z100-5-76

© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.k01

1 PrefaceThis guide provides instructions on how to configure and administer the Fujitsu Siemens Computers Inc., SIS (Scalable Internet Services®) product.

The primary audience for this guide is the system administrator.

1.1 Contents of this manual

This manual is organized as follows:

● The Chapter “Introduction” provides a brief overview of SIS (Scalable Internet Services), including terms, concepts, functions, and components.

● The Chapter “Configuration” describes SIS configuration files and how to configure them. In addition, some example configurations are supplied.

● The Chapter “Administration” describes how to administer SIS with Cluster Admin and details the SIS utilities.

● The Chapter “Syntax rules” lists the syntax rules for a SIS configuration file.

● The Chapter “Debugging and troubleshooting” details the dtcpdbg command and answers some common configuration and administration questions.

● The Chapter “Manual pages” lists the manual pages for SIS.

1.2 Related documentation

The following manuals contain information relevant to SIS and may be ordered through your sales representative:

● Concepts Guide

● Installation Guide

● Cluster Foundation Configuration and Administration

I Your sales representative will need your operating system release and product version to place your order.

U42104-J-Z100-5-76 1

Conventions Preface

1.3 Conventions

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) rights to execute are preceded by the system administrator prompt, the hash sign (#). Entries that do not require system administrator rights are preceded by a dollar sign ($).

1.3.1.2 Manual page section numbers

References to the operating system commands are followed by their manual page section numbers in parentheses for example, 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.

2 U42104-J-Z100-5-76

Preface Conventions

© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.k01

1.3.1.4 Typefaces

The following typefaces highlight specific elements in this manual.

Typeface conventions are shown in the following examples.

1.3.1.5 Example 1

Several entries from an /etc/passwd file are shown below:

root:x:0:1:0000-Admin(0000):/:sysadm:x:0:0:System Admin.:/usr/admin:/usr/sbin/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(1) command to display the contents of a file, enter the following command line:

$ cat file

Typeface UsageConstant Width

Computer output and program listings; commands, file names, manual page names and other literal programming elements in the main body of text.

Italic Variables that you must replace with an actual value.Bold Items in a command line that you must type exactly as

shown.

U42104-J-Z100-5-76 3

Important Preface

1.3.2 Command syntax

The command syntax observes the following conventions.

1.4 Important

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.

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.

4 U42104-J-Z100-5-76

© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.k02

2 IntroductionThis section discusses the following:

● The Section “SIS overview” introduces the concepts of SIS and the various SIS components.

● The Section “Benefits” lists the SIS features.

● The Section “SIS architecture” explains the functions of SIS in detail.

● The Section “VIPs” introduces Virtual Interface Providers (VIPs), and it discusses the predefined scheduling algorithms used by SIS to schedule client requests.

● The Section “Failover” describes the failover mechanisms available in SIS.

● The Section “Proxy addresses” discusses the concepts and uses of proxy addresses.

● The Section “Private addresses” details the uses of private addresses.

2.1 SIS overview

SIS provides scalable and fault tolerant network services based on the under-lying PRIMECLUSTER technology. SIS enables PRIMECLUSTER to act as a scalable, reliable, and easily managed network server system. The nodes on a SIS cluster are accessed via one or more Virtual Interface Provider (VIP) addresses and the cluster appears to the clients as a single network server.

Nodes in a SIS cluster share the load for different services. With SIS, you can configure load sharing per service, and you can fine-tune unique application and site needs with a variety of load-balancing algorithms.

SIS eliminates single points of failure and ensures availability as follows:

● If any of the SIS nodes or services fail, SIS schedules requests around the failed nodes.

● If any of the SIS modules fail, they gracefully recover.

● After a failed node restarts and you have started SIS on it, the node will seamlessly join the cluster to restore maximum performance.

The sections that follow discuss the various types of SIS nodes.

U42104-J-Z100-5-76 5

Benefits Introduction

2.1.1 Service nodes

Service nodes offer network services such as web services and directory services. If a service node fails, services are scheduled around it. When a failed node comes back up, it joins the SIS cluster.

2.1.2 Gateway nodes

There is one gateway node per VIP address. All incoming packets are received by this node and forwarded to the service node, depending on the scheduling algorithm for the service. If a gateway node fails, another node assumes the role of the failed gateway node without any interruption.

2.1.3 Primary database node

The primary database node keeps the static and dynamic data of the SIS cluster. The static information may include the list of nodes in the SIS cluster, the VIP address and services offered, and the scheduling algorithms. The dynamic information includes the current list of connections and the current status of the SIS cluster.

2.1.4 Backup database node

The backup database node assumes the role of the primary database node when the primary database node fails for any reason. There can be more than one backup database node. One of the backup database nodes will become the primary database node if the primary database node fails. Each backup database node contains the static configuration details, and SIS collects the dynamic configuration items from all the available nodes; therefore, network disruption is kept to a minimum.

2.2 Benefits

The benefits of SIS are as follows:

● Provides single IP target address for all external users

● Easily adds nodes and services

6 U42104-J-Z100-5-76

Introduction Benefits

© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.k02

● Supports TCP services distributable on a per-port basis

● Supports UDP protocol

● Supplies many load-balancing algorithms

● Handles node failures, service failures, and component failures to ensure that they are available without interruption

● Provides flexible backup-node management

● Allows proxy addresses

● Supports private communication

● Provides software-based solution

● Supplies GUI-based configuration and administration interface

● Works with other PRIMECLUSTER products

U42104-J-Z100-5-76 7

SIS architecture Introduction

2.3 SIS architecture

Figure 1: Example of a SIS cluster

In Figure 1, the SIS cluster consists of one gateway node, two service nodes, and one database node (the service node, the database node, and the gateway node can all reside in one physical node). When the client sends out a network request, the SIS cluster responds as follows:

1. The request reaches the gateway node.

Client system

Internet

Gateway node

Database node

Service node Service node

SIS cluster

8 U42104-J-Z100-5-76

Introduction VIPs

© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.k02

2. The gateway node queries the database node to determine which service node will reply to this network request. The database determines this according to the current configuration and service node availability.

3. The gateway node keeps the result cached for future packets of the same connection.

4. The IP packet is then sent to the service node where it is sent on to the appli-cation.

5. The application on the same node replies directly to the client (without going through the gateway node).

2.4 VIPs

Virtual Interface Providers (VIPs) are IP addresses or names that SIS uses to make network services highly available and to make the cluster appear as a standard network server. SIS schedules client requests by using the following predefined scheduling algorithms:

● Keep local—The gateway node answers the request without any processing overhead.

● Client based—The service node is chosen based on the client’s IP address.

● System load—The system with the minimum system load is chosen. The system load is calculated by SIS using an internal algorithm.

● Round robin—All available nodes are chosen in a circular way.

● Spill over—If the system load on all primary nodes is equal or greater than the configured threshold, a backup node is chosen to lessen the load.

● Weighted connection count—SIS chooses the system with the least number of connections. Each node may be assigned a weight, and the connection count is normalized according to this weight.

U42104-J-Z100-5-76 9

Failover Introduction

2.5 Failover

One or more nodes can be service nodes for each service. Each of these service nodes can have one or more backup nodes. The backup nodes can be either hot standby or nodes which are doing something else. If a node or nodes fail, then the configured backup nodes replace the failed node or nodes as determined by the configuration file.

2.6 Proxy addresses

Proxy addresses can be defined to assign one or more virtual addresses to a node. Since proxy addresses have failover capabilities, they also provide high availability. The possible uses are as follows:

● Co-hosting multiple addresses to one node

● Assigning external connectivity to nodes that do not have connections to the Internet

● Allocating backup nodes to a node

2.7 Private addresses

You can configure private addresses on each of the available nodes in a SIS cluster. These addresses are commonly used for inter-node communication by means of the interconnect and the IP protocol. Private addresses are secure, fast, and use the redundant interconnect to assure high availability.

2.8 Cluster Admin

The Cluster Admin is an administrative graphical user interface (GUI), which has a SIS wizard for creating and editing configuration files. The Cluster Admin can manage the following SIS procedures:

● Configuration

● Administration

● Operations and diagnostics services

10 U42104-J-Z100-5-76

Introduction Cluster Admin

© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.k02

Administration can be done from any node in the cluster or remotely from the Internet. A Java-enabled Web browser serves as the administrative interface; a conventional command-line interface is also available.

U42104-J-Z100-5-76 11

Cluster Admin Introduction

12 U42104-J-Z100-5-76

© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.k03

3 ConfigurationThis chapter describes the configuration file for SIS, and it provides examples of configuration files to assist users with the configuration process.

This chapter discusses the following:

● The Section “Concepts” introduces some basic concepts for SIS.

● The Section “Configuration file” provides a description of the configuration file, including variable assignments, node and gateway declarations, and interface definitions.

● The Section “Configuring with Cluster Admin” describes how to configure SIS using the Cluster Admin GUI.

● The Section “Examples and configuration files” provides examples of some configuration files.

3.1 Concepts

The following concepts and definitions are important in the configuration of SIS:

● SIS cluster—A subset of the CF cluster that provides the scalable and highly available network services of the PRIMECLUSTER suite.

● Database node—Acts as a repository of the current state of the system. It keeps the current configuration, keeps track of the current list of available nodes and services, knows about the current connections and their state, and other housekeeping duties, which ensure the smooth running of SIS.

● Backup database node—A node in the current cluster that takes up the role of the primary database node if the primary database node goes down for any reason. There can be more than one backup database node in the SIS cluster.

● Gateway node—Any node that can communicate to the external world using the IP protocol.

● Services—Network services such as http or ldap.

● Service node—Provides a network service.

● Failover node—Any node which can take over the role of a service node.

U42104-J-Z100-5-76 13

Configuration file Configuration

● Virtual Interface Provider (VIP)—IP addresses or names used by SIS for making network services highly available and for providing a single system image.

● Proxy—IP addresses or names that are assigned to SIS nodes on the public network, which make all services of a node highly available.

● Private addresses—IP addresses or names that are assigned to SIS nodes for them to communicate privately and securely using the CF interconnect.

3.2 Configuration file

The SIS configuration file is used to configure the SIS cluster to provide the scalable and highly available network services of the PRIMECLUSTER suite. The SIS configuration file should be created using the Cluster Admin GUI. (Since it is a text file, it can also be created or edited by using a text editor; however, this is recommended only for experienced users.)

The SIS configuration file is read once from the top down and requires a minimum of one interface definition. The items contained within the configu-ration file must be maintained in the following order:

● Variable assignments—This is an optional section where variables can be assigned for later use.

● Nodes declaration—This section lists all the nodes in the SIS cluster.

● Gateways declaration—This section lists all the nodes in the SIS cluster that have an interface on the public network.

● Interface definitions—This list defines VIP addresses, proxy addresses, and private addresses used by the SIS cluster.

I The hash mark (#) indicates a comment. Everything following the hash mark (#) is ignored until End of Line (EOL).

3.2.1 Variable assignments

This option, if present, should be the first section in the configuration file.

A variable declaration has the following syntax:

variable_name=string_0...string_n;

14 U42104-J-Z100-5-76

Configuration Configuration file

© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.k03

A variable declaration provides a substitution mechanism, which makes it more convenient to confine changes in the configuration to a single location. For example, you can define a group of nodes in the variable section of the config-uration file without having to change service definitions in the body of the VIP definition.

To define a variable, ensure that the following conditions are met:

● Define variables before using them or else SIS treats the variable names as literal strings.

● Reference any variable as long as the variable was defined previously.

● End all variable declarations with a semicolon.

I Do not use the following keywords as variables: VIP, GATEWAYS, SERVICE, PROXY, PRIVATE, NODES, KEEPLOCAL, CLBASED, SYSLOAD, ROUNDROBIN, FAILOVER, CONCOUNT, SPILLOVER, AT, TO, UDP, TCP, NONE, DCL, and DPO.

The following are examples of valid variable assignments:

HTTP_NODES=fuji2 fuji3;

FUJI3 = fuji3;

3.2.2 NODES declaration

NODES defines the membership of the SIS configuration. In other words, you list all the nodes configured for SIS in this declaration. It has the following syntax:

NODES nodedef_1.......nodedef_n

In this definition, nodedef can a node name or a variable (the variable resolves to one or more node names).

The following are examples of valid node definitions:

NODES HTTP_NODES

NODES fuji2 FUJI3

U42104-J-Z100-5-76 15


3.2.3 GATEWAYS declaration

GATEWAYS defines the SIS nodes that have an external interface on the public network. It has the following syntax:

GATEWAYS nodedef_1...nodedef_n

In this definition, nodedef can either be a node name or a variable.

The following are examples of valid gateway definitions:

GATEWAYS HTTP_NODES

GATEWAYS fuji2 FUJI3

I If a node has an external interface on the same network as any of the public SIS services (that is, VIP or proxy), then the node name must be in the GATEWAYS list.

3.2.4 Interface definitions

Interface definitions define the IP addresses used to configure SIS. They can be VIP addresses, proxy addresses, or private addresses. Interface definitions can occur in any order.

3.2.4.1 VIP addresses

VIP addresses are used by SIS to provide a clusterwide network service. The network service is available on all the SIS nodes; however, SIS schedules client requests to these VIP addresses according to a predefined scheduling algorithm. The syntax is as follows:

VIP (interface_1)...(interface_n) { vip_body }

The following terms and conditions apply:

● interface has the form IPAddress netmask [preferred_gateway].

– IPAddress is a resolvable name or IP address.

– netmask is the netmask associated with IPAddress.

– preferred_gateway is an optional field that indicates which node should receive incoming data for the VIP address.

● IPAddress and netmask can be a name, dot notation, or hexadecimal notation.

16 U42104-J-Z100-5-76


© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.k03

The following are examples of valid interface definitions:

www.siscluster.com 255.255.255.0 fuji2www.clustersis.com 255.255.255.0

VIP body

The body of the VIP defines the network services available for this VIP and how client requests for these services are to be scheduled. Each service is defined on a separate line. A service definition has one of the following formats:

● SERVICE portdef scheduling

● SERVICE portdef DCL scheduling

portdef defines a port (network service) and a protocol in the following format: port/protocol. The protocol can be either tcp or udp. If you do not specify a protocol, the default is tcp. port defines the network service and can be any of the following:

● Number (such as 80)

● Symbolic name (such as http)

● Range of numbers (such as 1:17)

The following are examples of portdef:

● 80/tcp

● http

● 2049/udp

● sunrpc/udp

DCL means that SIS remembers a client such that all future connections of the client will go to the same node. The first connection is scheduled based on the scheduling algorithm (for example, ROUNDROBIN or SYSLOAD).

Scheduling for TCP-based services

scheduling defines how incoming requests from clients get assigned to service nodes and the list of nodes that service the client request. The scheduling algorithms are as follows:

● Keep local—A connection request to this service will be established on the gateway node itself with little overhead. The syntax is as follows:

KEEPLOCAL

U42104-J-Z100-5-76 17


● Client based—The service node is chosen based on the client’s IP address. The syntax is as follows:

CLBASED ServiceNodeList

● System load—The node with the lowest system load is chosen for placing a connection. The syntax is as follows:

SYSLOAD ServiceNodeList

SIS uses a sophisticated algorithm for calculating system load, which returns a value between 0 and 1. The algorithm is calculated from the available hardware and various load parameters and depends on the current configuration and system load.

Approximate values from internal tests and calculations are as follows:

– 0.0 to 0.5 is a system with a minimum load

– 0.5 to 0.7 is a reasonably loaded system (use discretion)

– 0.7 and above is a loaded system

● Round robin—All nodes are used in a forced, circular sequence. The syntax is as follows:

ROUNDROBIN ServiceNodeList

● Spill over—SPILLOVER is based on the SYSLOAD algorithm. The node chosen is the one from ServiceNodeList_1 with the lowest load. If this load is higher than the defined limit, the node with the lowest load is chosen from the second group (ServiceNodeList_z). The syntax is as follows:

SPILLOVER ServiceNodeList_1 AT load TO ServiceNodeList_z

Use SPILLOVER to protect important applications.

● Weighted connection count—The node with the lowest number of open connections is used. The syntax is as follows:

CONCOUNT ServiceNodeListElement...ServiceNodeListElement

ServiceNodeListElement is defined as one of the following:

● node:weight

● (NodeList FAILOVER NodeList:weight)

If no weight is attached, a default of 1 is assumed. The raw connection count is normalized by dividing it by weight, and the result is used as the value for the comparison.

18 U42104-J-Z100-5-76


© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.k03

The following example shows a weighted connection count SERVICE definition that schedules telnet among different nodes:

SERVICE telnet CONCOUNT fuji1 fuji2:3 (fuji3 FAILOVER fuji4):4

In this example, fuji3 is selected most of the time if all of the nodes are of similar power and have similar connection loads.

I If weighted connection count is applied to a variable defined in the assignment section, it will be treated as a simple string substitution; for example, you can use variables to configure the following:

SERVICE telnet CONCOUNT fuji1:2 fuji2 fuji3:3 (fuji4 FAILOVER fuji5):4

Use variables for the preceding example as follows:

A = fuji2 fuji3;B = (fuji4 FAILOVER fuji5);

SERVICE telnet CONCOUNT fuji1:2 A:3 B:4

ServiceNodeList is defined as one of the following:

● node_l...node_n

This means that a node from the list is selected according to the algorithm schedule.

● ( node_h...node_r FAILOVER node_s...node_z )

Scheduling for UDP-based services

Because of the nature of UDP packets, packets destined for a port can be scheduled to only one node. However a failover can be used to ensure a node is always up. For UDP scheduling, SIS supplies the scheduling algorithm NONE. This scheduling algorithm can be used only with UDP protocols. The following are examples of UDP-based scheduling:

SERVICE 2049/udp NONE fuji 1

SERVICE 118/udp NONE (fuji1 FAILOVER fuji2 fuji3)

Failover

FAILOVER is used in place of a node or a list of nodes when additional fault tolerance is required in SERVICE or PROXY definitions.

The syntax of FAILOVER for VIP is as follows:

( node_a…node_m FAILOVER node_n…node_z )

U42104-J-Z100-5-76 19


If the service, SIS, or the node itself fail on one or more nodes fromnode_a …node_m, then a functional node from node_n …node_z will replace the failed nodes. When the failed node or service becomes available, the sched-uling reverts back to the original node.

Examples of FAILOVER for VIP can be found in the examples for various sched-uling algorithms.

I Only one node will be used to replace all failed nodes within the same FAILOVER declaration even if more than one replacement node is defined as in the above syntax.

DCL

DCL is an optional qualifier which can be used after the service of a SERVICE definition. Its function is to bind all further connections for a client to the same server, once the very first connection has been selected according to the sched-uling algorithm for this SERVICE.

The following are examples for the use of DCL:

SERVICE ftp DCL ROUNDROBIN fuji2 fuji3SERVICE 8080:8090 DCL ROUNDROBIN fuji2 fuji3

FTP notes

SIS supports the FTP protocol for VIP with the following special limitations:

● You can configure port 21 (ftp) but not port 20 (ftp-data). Service decla-rations that include port 20 will be rejected.

● You can configure KEEPLOCAL and CLBASED service for port 20 without restrictions.

● The use of the DCL qualifier is mandatory for port 21 SERVICE declarations with scheduling algorithms other than KEEPLOCAL and CLBASED.

The following are valid configurations:

SERVICE ftp DCL ROUNDROBIN fuji2 fuji3SERVICE 21 KEEPLOCALSERVICE ftp CLBASED fuji2 fuji3

The following are invalid configuration:

SERVICE ftp-data CONCOUNT fuji1 fuji2SERVICE 20 CONCOUNT fuji2 fuji3SERVICE 19:25 CONCOUNT fuji2 fuji3SERVICE ftp ROUNDROBIN fuji2 fuji3

20 U42104-J-Z100-5-76


© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.k03

3.2.4.2 Proxy addresses

Proxy addresses are provided by SIS to associate a virtual IP address to a node. All client requests to a proxy address are forwarded to the ProxyNode. One or more failover nodes can be associated with this node. The first available node on this list will take over in case the proxy node fails.

PROXY has the following syntax:

PROXY IPAddress netmask ProxyNode [preferred_gateway]

● IPAddress is a resolvable name or IP address.

● netmask is the netmask associated with the above IP address.

● ProxyNode is a node or failover list.

The following are examples of ProxyNode:

fuji2(fuji1 FAILOVER fuji2 fuji3)

The syntax for PROXY FAILOVER is as follows:

( node_a FAILOVER node_n…node_z )

If SIS on node_a or the node itself fails, then a node from node_n…node_z will replace the failed node. When the failed node becomes available, the connections stays on the replacement node.

I PROXY does not provide FAILOVER for a failed service.

● preferred_gateway is an optional field that indicates which node should receive incoming data for the IP address.

● IPAddress and netmask can be a name, dot notation, or hexadecimal notation.

The following are valid examples of proxy configurations:

PROXY ftp.mycompany.com 255.255.255.0 fuji1 PROXY ftp.mycompany.com 255.255.255.0 (fuji1 FAILOVER fuji2)PROXY ftp.mycompany.com 255.255.255.0 fuji1 fuji3 PROXY ftp.mycompany.com 255.255.255.0 (fuji1 FAILOVER fuji2) fuji3

In the first example, packets destined for ftp.mycompany.com are sent to fuji1.

In the second example, packets destined for ftp.mycompany.com are sent to fuji1, but if fuji1 fails, all the packets for ftp.mycompany.com are sent to fuji2.

U42104-J-Z100-5-76 21


The third and fourth examples are like example 1 and 2 but fuji3 acts as the preferred gateway node for ftp.mycompany.com.

3.2.4.3 Private addresses

The private internal interface is used for communication among the nodes in the cluster. When you configure a private address for a node, SIS creates a virtual interface on the interconnect network. The private address cannot be accessed from the outside.

PRIVATE has the following syntax:

PRIVATE IPAddress netmask PrivateNode

For example, if fuji2 and fuji3 are the only nodes of the cluster, then they can be defined in the configuration file as follows:

PRIVATE 192.168.0.1 255.255.255.0 fuji2PRIVATE 192.168.0.2 255.255.255.0 fuji3

The PRIVATE assignments can be placed anywhere after the GATEWAYS assignment, but not in the VIP body.

The following is strongly recommended for private configurations:

● Configure a private interface for each node.

● Select IP addresses from one of the available non-routable subnets.

3.2.5 SIS configuration procedure

Perform the following steps to configure SIS:

1. Select the nodes that will be running SIS.

2. Determine the gateway nodes.

3. Decide on a primary database node.

4. Decide on one or more backup database nodes.

5. Decide on the usage of VIPs, proxies, private interfaces and the corre-sponding addresses, services, and additional functions of these interface definitions.

6. Create the configuration file.

7. Check for syntax errors.

22 U42104-J-Z100-5-76

Configuration Configuring with Cluster Admin

© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.k03

8. Start SIS by first starting the primary database node, then the backup database nodes.

9. Start the service nodes.

3.3 Configuring with Cluster Admin

The following sections discuss how you can create the SIS configuration file using the Cluster Admin GUI, which has a SIS wizard for creating a new config-uration file (refer to Section “Cluster Admin” for more information).

3.3.1 Starting SIS

Start SIS with Cluster Admin as follows:

1. Log in to Cluster Admin.

2. Display the SIS GUI main screen and choose one of the following:

a) Load a pre-saved configuration file

b) Start the SIS configuration wizard

3.3.2 Logging in to Cluster Admin

Launch Cluster Admin and log in to one of the cluster nodes. Refer to the Instal-lation Guide for the necessary prerequisites. Once you have met the prerequi-sites, do the following:

1. Open your browser.

2. Type in the address of the URL for Web-Based Admin View. The URL is the name of the node, the numbers 8081, and /Plugin.html. For example:

The initial node chosen is fuji2. Enter http://fuji2:8081/Plugin.html in your browser to pull up the Web-Based Admin View java-based applet.

After the Java applet has fully loaded, a small top-level screen for Web-Based Admin View appears outside the browser. This top-level screen (see Figure 2) allows you to log in to the GUI.

U42104-J-Z100-5-76 23

Configuring with Cluster Admin Configuration

Figure 2: Login screen

Enter your user name and the password for Web-Base Admin View and click OK to log in. Once you have logged in, select Global Cluster Services (see Figure 3).

24 U42104-J-Z100-5-76

Configuration Configuring with Cluster Admin

© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.k03

Figure 3: Global Cluster Services screen

U42104-J-Z100-5-76 25

Configuring with Cluster Admin Configuration

Select Cluster Admin to go to the Cluster Admin screen (see Figure 4).

Figure 4: PRIMECLUSTER Cluster Admin screen

3.3.3 Displaying the SIS GUI main screen

To display the SIS GUI main screen, click on the SIS tab in the bottom of the left panel to start the SIS portion of the Cluster Admin GUI.

If SIS is not configured on the node, then the SIS Startup Menu pop-up screen appears (see figure Figure 5) with the following options:

● Search all configuration files—Allows you to load a pre-saved configuration file and start SIS with that configuration. This option is also available after you have stopped SIS by means of the Stop All option (refer to the Section “Tools”).

● Start configuration wizard—Invokes the SIS configuration wizard to create a new configuration.

26 U42104-J-Z100-5-76

Configuration Starting with an existing configuration file

© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.k03

Figure 5: SIS startup selection

3.4 Starting with an existing configuration file

After selecting Search all configuration files, the SIS Clusterwide Startup screen appears (see Figure 6).

Figure 6: SIS Clusterwide Startup screen

U42104-J-Z100-5-76 27

Starting with an existing configuration file Configuration

To select an existing configuration file, perform the following:

1. Click on the plus [+] symbol of the node with the desired file.

2. Select the file by clicking on it.

After selecting and checking the configuration file, the Primary Database Node selection list is populated (see Figure 7).

Figure 7: Primary Database Node selection list

To enable the configuration file perform the following:

1. Select the primary database node from the list by choosing it from the selection box.

2. Choose one or more secondary nodes from the Secondary Database Nodes table by clicking on the Selection check box for the node.

3. Click on Check to check the file for syntax errors.

4. A small screen indicates whether the error check passed or failed. Select OK to return to the SIS Clusterwide Startup screen.

5. Select the OK button, which becomes available after the error check passes. SIS starts on all nodes in the correct order.

28 U42104-J-Z100-5-76

Configuration SIS Wizard

© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.k03

3.5 SIS Wizard

The first screen of the wizard is a welcome screen (see Figure 8). Click on the Next button to move on to the next screen. Refer to the Section “Concepts” for details on all of the terminology used.

Figure 8: SIS Wizard welcome screen

The screens after the welcome screen are divided into two panels as follows:

● Left panel—Allows you to view the configuration as you create in either a tree form (see Figure 9) or a textual form (see Figure 10), depending on the tabs you choose at the bottom of the panel.

● The right panel—Takes the configuration input, which is then added to the left-hand panel.

U42104-J-Z100-5-76 29

SIS Wizard Configuration

Figure 9: Viewing the configuration in the tree format

30 U42104-J-Z100-5-76


© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.k03

Figure 10: Viewing the configuration as a text file

U42104-J-Z100-5-76 31


3.5.1 Adding nodes

The screen after the welcome screen allows you to select the CF nodes that you want in the SIS cluster (see Figure 11). You can choose Select all or Clear all for the SIS nodes or the gateway nodes, or you can choose them individually by selecting the check box next to the node name in the Node List table:

● Selection—Choose SIS nodes.

● Gateway—Mark nodes with an external interface to be gateways.

For example, if you select the nodes fuji2 and fuji3 to be in the SIS cluster and both are gateways, the configuration file appears as follows:

NODES fuji2 fuji3GATEWAYS fuji2 fuji3

Click on Next to create the VIP, proxy, and private interface definitions.

Figure 11: Selecting nodes

32 U42104-J-Z100-5-76


© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.k03

3.5.2 Defining VIP, proxy, and private addresses

The screen for defining VIP, proxy, and private addresses is shown in Figure 12.

Figure 12: Define VIP, private, and proxy addresses

The following options are available:

● Define VIP Addresses

● Define Proxy Addresses

● Define Private Addresses

U42104-J-Z100-5-76 33


3.5.2.1 VIPs

Creating a VIP requires the following:

● Defining one or more VIP addresses

● Defining services for the VIP

● Assigning a schedule to each service

● Checking the result

● Saving and activating the configuration

Defining the VIP address

To define a VIP, select the Define VIP Addresses radio button (see Figure 12) and click on the Next button. The resulting screen is shown in Figure 13.

Figure 13: Define VIP Addresses screen

34 U42104-J-Z100-5-76


© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.k03

Define VIPs as follows:

1. Enter the Host/IP address as a resolvable host name or IP address.

2. Select the appropriate netmask from the Netmask field.

3. Select a preferred gateway in the Pref GW field if desired.

4. Click the Add button to add the VIP to the configuration file.

5. Repeat Steps 1 through 4 for each VIP.

The resulting screen should look similar to Figure 14.

Figure 14: Define VIP Addresses screen with VIP added

U42104-J-Z100-5-76 35


Defining services for the VIP

To add services to a VIP definition, select the VIP from the VIP Addresses list and click on the Next button. This takes you to the select TCP services screen (see Figure 15).

Figure 15: VIP TCP services screen

36 U42104-J-Z100-5-76


© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.k03

A list of available TCP services from /etc/services is already in the Available services list (see Figure 15). You can define additional services as follows:

1. Click the Define new service check box (see Figure 16).

2. Enter the starting and ending port numbers.

3. Click the Add button. This puts the newly defined service in the Available services list.

Figure 16: Define new service screen

Next, select one or more of the available services as follows:

1. Select one or more services from the list.

2. Click on the right arrow [>] button to move the service to the Selected services window.

Use the left arrow [<] button to remove the service from the Selected services list. Click on the double right [>>] button to select all services in the Available services list. To remove all the Selected services, click on the double left arrow [<<] button.

U42104-J-Z100-5-76 37


Once you have finished your selection, click on the Next button, which takes you to the define TCP services screen (see Figure 17).

Figure 17: Define TCP services screen

The define TCP service screen shows the list of all services you selected. To add schedules to the services, select them one by one by clicking on the Selection check box. Click on the DCL check box if required, and then click the Next button.

38 U42104-J-Z100-5-76


© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.k03

Next you see the define scheduling algorithm screen (see Figure 18).

Define schedules for each service as follows:

1. Select schedule from the list.

2. Select the service nodes by clicking on the corresponding check boxes in the Service Nodes list.

3. If required, click on the desired Failover Nodes check boxes. You can only select nodes that have not been selected as service nodes.

4. Click on the arrow pointing up to add the definition. You can click on the arrow pointing down to remove the definition.

5. After you are finished with the selections, click on the Next button, which takes you back to the complete configuration screen (see Figure 25).

You can define additional interfaces by selecting the desired radio button and clicking on Next.

Figure 18: Define scheduling algorithm screen

U42104-J-Z100-5-76 39


If you return to the select TCP services screen by selecting the VIP that you configured and clicking on Next, you will see the configured service (see Figure 19). You can add more services here if desired.

Figure 19: Select TCP services—configured

40 U42104-J-Z100-5-76


© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.k03

Once you have completed selecting TCP services for the selected VIP, select Next and proceed to the select UDP services screen (see Figure 20). Select the desired services for UDP in the same manner as TCP services. Click Next when you are done.

Figure 20: Select UDP services screen

U42104-J-Z100-5-76 41


After you finish configuring all of the services, click the Next button to return to the define VIP addresses screen. There will be a check next to each fully configured VIP (see Figure 21). If you need to modify a VIP, select the VIP, click on Modify, and make your changes as necessary. Complete all VIPs in a similar way.

Figure 21: Fully configured VIP screen

42 U42104-J-Z100-5-76


© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.k03

After completing the configuration of all VIPs, our sample configuration file now has the following contents:

NODES fuji2 fuji3

VIP (www.def.com 255.255.255.0 fuji2){

SERVICE shell ROUNDROBIN fuji2 fuji3 SERVICE echo DCL (fuji2 FAILOVER fuji3)

}

VIP (www.mycompany.com 255.255.255.0 fuji3){ SERVICE 8080-8085 ROUNDROBIN fuji2 fuji3 }

FTP Notes

Due to the special limitations when configuring ftp for VIP (refer to Section “VIP addresses”), the GUI also recognizes FTP configurations and enforces the following special rules:

● CLBASED and KEEPLOCAL scheduling are allowed without restrictions.

● For all other scheduling algorithms, the GUI inserts dcl (even if you do not check the DCL button).

● When you try to configure ftp together with other services or ports, you get a pop-up warning and the configuration will not be possible until you deselect the other services from this screen.

● The configuration of port 20 will not be discovered until the syntax check is completed.

U42104-J-Z100-5-76 43


Private and proxy providers

Select the Define Private Addresses option and click on Next to bring up the define private addresses screen (see Figure 22).

Figure 22: Define private addresses screen

After entering the required data, save the information by selecting Add. Figure 22 shows the screen to define a private address and Figure 23 shows the screen to create a proxy address.

44 U42104-J-Z100-5-76


© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.k03

Figure 23: Create proxy addresses

The configuration file created from the information entered from Figure 22 and Figure 23 is as follows:

NODES fuji2 fuji3

GATEWAYS fuji2 fuji3

PROXY www.abc.com 255.255.255.0 (fuji2 FAILOVER fuji3)PRIVATE 192.168.1.1 255.255.255.0 fuji3PRIVATE 192.168.1.2 255.255.255.0 fuji2

Create a private or proxy provider as follows:

1. Enter the Host/IP address.

2. Select the appropriate netmask from the Netmask field.

3. For proxy addresses, you can select a preferred gateway by selecting a node from the Pref-GW pull-down list.

4. Click on the Add button.

U42104-J-Z100-5-76 45


After clicking the Add button, the information is added to the list on the left portion of the screen and the entered Host/IP data is cleared, allowing you to create more interfaces (see Figure 24).

Figure 24: Creating additional addresses

We recommend that you first assign a private address for each node in the cluster. After you have finished creating all of the private addresses, you can create proxy addresses in the same manner. This is done by clicking on the Next button to continue creating the configuration file and choosing from the following options (see Figure 25):

● Add/Edit Interface

● Save file with error check

● Save file without error check

46 U42104-J-Z100-5-76


© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.k03

Select Add/Edit Interface to continue adding VIP, private, and proxy addresses. When you are finished creating all of the intended addresses, click the Next button to return to the complete configuration screen to save the file with or without an error check (see Figure 25). The example configuration file would look similar to the following:

NODES fuji2 fuji3

GATEWAYS fuji2 fuji3

PROXY www.abc.com 255.255.255.0 (fuji2 FAILOVER fuji3) fuji2

PRIVATE 192.168.1.1 255.255.255.0 fuji3PRIVATE 192.168.1.2 255.255.255.0 fuji2

Figure 25: Complete configuration screen

Refer to Section “Completing the configuration” for information on saving your file.

U42104-J-Z100-5-76 47


3.5.3 Completing the configuration

After creating and defining all of the VIPs, the Next button takes you back to the complete configuration screen, which allows you to add or edit more interfaces or to save the file with or without an error check (see Figure 25). If you have finished adding all of the interfaces, select the Save file with error check radio button and click Next. This returns a pop-up box with the error check result of either OK or Error (see Figure 26).

Figure 26: Error check result screen

I An error only occurs if an IP address is not resolvable or if you are editing a configuration file that already contained an error.

48 U42104-J-Z100-5-76


© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.k03

Click on the OK button to see the details of the syntax check in the right-hand side panel (see Figure 27). The left panel shows the configuration that you created in a hierarchical tree structure.

Figure 27: Error check result screen

U42104-J-Z100-5-76 49


Click on the Next button to go to the save configuration screen, where you are given the option to save the file (see Figure 28). Enter a file name in the Save as text box. Select the Start SIS with the new created configuration check box if you want to start SIS with the new configuration, or enter the file name and click Next.

Figure 28: Save configuration screen

50 U42104-J-Z100-5-76


© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.k03

If you do not want to start SIS with this configuration, click on the Next button after entering the filename, which takes you to the SIS Wizard completed screen as shown in Figure 29. Click the Finish button to exit from the wizard.

Figure 29: SIS Wizard completed screen

U42104-J-Z100-5-76 51


If you want to start SIS with the configuration, then you have the option to either restart or rebuild the configuration (see Figure 30).

Figure 30: Restarting SIS from the save configuration screen

52 U42104-J-Z100-5-76


© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.k03

If you select the Restart radio button, and click the Next button, SIS restarts with the new configuration. Next, the SIS Wizard completed screen appears (see Figure 31). Click on Finish to exit from the wizard.

Figure 31: Restart from the SIS Wizard completed screen

U42104-J-Z100-5-76 53


If you select the Rebuild option, you are given additional options as follows:

1. You can select the primary database node from the Primary DB Node list.

2. You can select the backup database node from the Secondary DB Nodes list by clicking on the selection check box.

When you click on the Next button, SIS is rebuilt and restarted with the configu-ration specified.

Figure 32: Rebuild option

Next, the SIS Wizard completed screen appears (see Figure 29). Click the Finish button to exit from the SIS Wizard.

54 U42104-J-Z100-5-76

Configuration Examples and configuration files

© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.k03

3.6 Examples and configuration files

The following are example scenarios and their corresponding configuration files. These examples are provided to illustrate how an actual configuration file would look; however, an actual configuration file should use the IP addresses for the cluster being configured, not the ones that appear in these examples.

Example 1

This example is of an LDAP server (ldap.mycompany.com) on a two-node cluster (fuji2 and fuji3). The LDAP database is replicated on both nodes. Both nodes reply to LDAP queries alternately for the TCP protocol. For UDP, fuji1 replies to all queries, and if fuji1 fails, fuji2 will reply to all UDP queries.

The sample configuration is as follows:

NODELIST = fuji2 fuji3;NODES NODELISTGATEWAYS NODELISTVIP (ldap.mycompany.com 255.255.255.0) {SERVICE ldap NODELISTSERVICE ldap/udp (fuji2 FAILOVER fuji3)}PRIVATE 192.168.1.1 255.255.255.0 fuji2PRIVATE 192.168.1.2 255.255.255.0 fuji3

Example 2

This example is of a four-node cluster with two powerful systems, fuji3 and fuji4, and two not so powerful systems, fuji1 and fuji2. fuji1 and fuji2 answer simple http queries and fuji3 and fuji4 answer the secure https requests. In addition, one customer is hosting a very large web site (www.abc.com) and another customer is hosting a smaller-scale web site (www.def.com).

U42104-J-Z100-5-76 55

Examples and configuration files Configuration

The sample configuration is as follows:

# Powerful systemsM400_NODELIST= fuji3 fuji4;

# Not so powerful systemsM200_NODELIST= fuji1 fuji2;

#All Nodes NODELIST= M400_NODELIST M200_NODELIST

NODES NODELISTGATEWAYS NODELIST

# Vip definitionsVIP (www.mycompany.com 255.255.255.0) {

SERVICE http ROUNDROBIN M200_NODELISTSERVICE https SYSLOAD M400_NODELIST

}

#Proxy definitions PROXY www.abc.com 255.255.255.0 (fuji3 FAILOVER fuji4)PROXY www.def.com 255.255.255.0 fuji1

#Private definitionsPRIVATE 192.168.1.1 255.255.255.0 fuji1PRIVATE 192.168.1.2 255.255.255.0 fuji2PRIVATE 192.168.1.3 255.255.255.0 fuji3PRIVATE 192.168.1.4 255.255.255.0 fuji4

56 U42104-J-Z100-5-76

© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.k04

4 AdministrationThis chapter describes the administration utilities included in SIS. These utilities are commands for such SIS administration tasks as starting, stopping, reconfig-uring, and checking SIS, and for displaying debug messages.


● The Section “Administering with Cluster Admin” details how to use the PRIMECLUSTER graphical user interface (GUI).

● The Section “Administering with the CLI” describes the dtcpadmin command.

● The Section “SIS daemon” describes the dtcpd command.

● The Section “Displaying the status of SIS” describes the dtcpstat command.

● The Section “Debug messages” describes the dtcpdbg program.

4.1 Administering with Cluster Admin

You can administer SIS using the Cluster Admin GUI by logging on to Cluster Admin (refer to the Section “Cluster Admin”) and clicking on the SIS tab at the bottom of the left panel (refer to the Section “Starting SIS”).

4.1.1 Using the GUI

After launching the SIS GUI, you will see the main administration screen (see Figure 33). The main administration screen consists of the following:

● SIS configuration tree on the left—Displays the configuration, the status of the nodes and services, and some basic statistics.

● Clusterwide summary table on the right—Shows a summary table of all of the configured interfaces, their type, IP addresses, netmasks, and the scheduled nodes configured for each service. The details of the services include the name, port number, scheduling and the nodes offering the service.

U42104-J-Z100-5-76 57

Administering with Cluster Admin Administration

Figure 33: Main administration screen

4.1.1.1 SIS configuration tree

The left panel shows a tree depicting the SIS configuration from the following views of the cluster:

● Nodes—Shows the node-interfaces-services hierarchy

● Interfaces—Shows the interface-nodes-services hierarchy

● Services—Shows the service-interfaces-nodes hierarchy

58 U42104-J-Z100-5-76

Administration Administering with Cluster Admin

© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.k04

Nodes view

Click on the Nodes view to see the list of all of the nodes configured for SIS (see Figure 34). The right panel shows the node-summary table with the following node details:

● Node Name

● Type

● State

Figure 34: Nodes view

U42104-J-Z100-5-76 59


Click on a node to display all of the interfaces configured on the node (see Figure 35). The right panel shows the following node details:

● Node Name

● Node Type

● Node Status

● List of services with their details

Figure 35: Node view showing node details

60 U42104-J-Z100-5-76


© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.k04

Click on the IP address of a node interface in the left panel to see the details of the interface. The left panel shows you all of the services configured on that interface, including the node above. The right panel shows the following details (see Figure 36):

● Interface Type—VIP, proxy, or private

● Address—IP address of the interface

● Mask—The netmask of the interface

● Preferred Gateway—Only available if configured

Figure 36: Node view showing interface details

U42104-J-Z100-5-76 61


Click on the service of a node interface in the left panel to see the details of the service. The right panel shows the following details (see Figure 37):

● Service Name/Ports—The name the service and the protocol, which is either tcp or udp.

● Scheduling—The scheduling algorithm for the service

● Details of the service

Figure 37: Node view showing interface details

62 U42104-J-Z100-5-76


© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.k04

Interfaces view

Click on the Interfaces branch on the SIS configuration tree on the left to see the interfaces (see Figure 38). This view shows a table of all of the interfaces with the following details:

● Name

● Interface Type

● IP Address

● Mask (netmask)

Figure 38: Interfaces screen

U42104-J-Z100-5-76 63


In the left panel, click on an interface IP address to see the following details of that interface in the right panel:





You can expand the configuration tree by clicking on an interface IP address or host name. Expanding the tree shows the nodes that are configured for the interface (see Figure 39).

Figure 39: Interface screen showing interface details

64 U42104-J-Z100-5-76


© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.k04

Click on a node in the left panel to see the node details in the right panel (see Figure 40). The node details include the following:

● Node Name

● Node Type

● Node Status

● List of services with their details, which are configured for that interface

Figure 40: Interface screen showing node details

U42104-J-Z100-5-76 65


Services view

To view the services, click on Services in the SIS configuration tree in the left panel. This displays the services configured in the cluster. The right panel shows a summary table of all of the services as configured on the nodes with their status and statistics (see Figure 41).

Figure 41: Services screen

66 U42104-J-Z100-5-76


© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.k04

Click on an interface IP address of a service in the left panel to see the nodes that have the service configured on them. The interface details are shown in the right panel (see Figure 42). The interface details include the following:





Figure 42: Service screen showing interface details

U42104-J-Z100-5-76 67


Click on a node from the list on the left panel to see its details in the right panel (see Figure 43). The node details include the following:

● Node Name

● Node Type

● Node Status

● Failover Nodes

● List of services with their details, which are configured for that interface

Figure 43: Service screen showing node details

68 U42104-J-Z100-5-76


© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.k04

4.1.2 Using the menu bar

The menu bar of the SIS GUI offers some additional features as detailed in the following sections.

4.1.2.1 File

The File menu offers the option to exit.

Exit

The File menu option (see Figure 44) allows you to select the Exit option to leave Cluster Admin.

Figure 44: File menu

U42104-J-Z100-5-76 69


4.1.2.2 Settings

The Settings menu offers the following options (see Figure 45):

● Refresh Now

● Refresh Policy

● Reload Config

Figure 45: Settings menu options

You can refresh the screens with the current status and statistics by clicking on the Refresh Now option.

You can also set periodic updates of the status and statistics by selecting Refresh Policy and selecting one of the following radio buttons from the resulting screen (see Figure 46):

● Refresh Every 10 seconds

● Refresh Every 30 seconds

● No Refresh

70 U42104-J-Z100-5-76


© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.k04

Figure 46: Refresh Policy screen

By selecting the No Refresh option, you can stop the updates altogether.

If there has been a configuration change, and you want to update all of the screens and data with the new configuration, then click the Reload Config option.

4.1.2.3 Tools

The Tools menu offers the following options:

● Start

● Stop

● Pause

● Resume

● Switch Gateway Node

● Add Backup Database Node

● Wizard

Stop, Start, Pause, and Resume options on all cluster nodes

If SIS is up and running, the Start and Resume options are not available. To stop SIS on every node in the cluster, select the Stop option from the menu, which brings up the confirmation dialog box (see Figure 47). Click on Yes to stop SIS. Once SIS is stopped in this manner, the SIS stopped screen appears (see Figure 48). Click on Ok. The data displayed on the panels disappear.

U42104-J-Z100-5-76 71


Figure 47: Stop SIS screen

Figure 48: SIS stopped screen

To start SIS on every node in the cluster, select the Start menu option from the Tools menu. This brings up the SIS Startup Menu screen (see Figure 49). This screen allows you to perform one of the following options:

● Search all configuration files—Searches all of the configuration files on all of the nodes of the SIS cluster.

● Start configuration wizard—Starts the configuration wizard.

● Restore the last session—Starts SIS with the previous configuration (the last configuration used before stopping SIS).

Figure 49: SIS Startup Menu screen

72 U42104-J-Z100-5-76


© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.k04

If you select the Search all configuration files radio button and click Ok, it brings up the SIS Clusterwide Startup screen (see Figure 50). This screen shows the cluster tree in the left panel with the nodes and the configuration files on them (in the default directory /etc/sis/conf).

Figure 50: SIS Clusterwide Startup screen

Use the right-mouse button on the items in the tree in the left panel to raise a small pop-up menu (see Figure 51). The menu items are as follows:

● Reload—Reloads all of the configuration files on the selected node.

● View—Opens a window that enables viewing the configuration file (see Figure 52). Activate this option by right-clicking on the configuration file name in the left-panel tree.

● Edit—Opens the configuration wizard for editing the selected configuration file. Activate this option by right-clicking on the configuration file name in the left-panel tree.

U42104-J-Z100-5-76 73


Figure 51: Startup options

Figure 52: View configuration file screen

Click on one of the nodes to select a predefined configuration file. You can also make selections for the primary and secondary database nodes for the config-uration on the right panel (see Figure 53).

After making all of the selections, the Check button becomes active. Click on the Check button to perform a syntax check on the selected configuration file.

74 U42104-J-Z100-5-76


© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.k04

Figure 53: Selecting file and database node

The syntax check either returns with errors (see Figure 54), or it is successful (see Figure 55). If the syntax check is successful, then click on the OK button and SIS will start with the selected file. If the check was erroneous, select another file and repeat the check.

Figure 54: Syntax check error screen

Figure 55: Syntax check OK screen

U42104-J-Z100-5-76 75


To restore the configuration that was running before you stopped SIS, select the Restore the last session radio button on the SIS Startup Menu screen and click OK. The GUI will automatically start SIS on all of the nodes with the previous config-uration.

To start the wizard and create a new configuration file, select the Start Wizard radio button and click OK. This will start the SIS configuration wizard (as explained in the Section “SIS Wizard”).

For pausing SIS on every node in the cluster, select the Pause option from the Tools menu. This brings up a confirmation dialog box. Click Yes to pause (see Figure 56). After SIS has been paused, the Pause option becomes inactive and the Resume option becomes active.

Figure 56: Pausing SIS

To resume SIS on every node in the cluster, select the Resume option from the Tools menu and click Yes on the confirmation dialog box (see Figure 57). This will inactivate the Resume option and activate the Pause option again.

Figure 57: Resuming SIS

Starting, stopping operations on a single node

For operations on individual nodes, select the node from the SIS configuration tree on the left panel and click the right mouse button. This brings up a small menu list with the Start and Stop options (see Figure 58).

76 U42104-J-Z100-5-76


© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.k04

Select one of the active menu items to bring up a confirmation dialog box (see Figure 59), the same as clusterwide operation. Click OK to perform the operation. Errors are reported back. SIS indicates success by changing the status of the node in the right panel.

Figure 58: Start and stop on an individual node

Figure 59: Stopping individual node bock

U42104-J-Z100-5-76 77


Switch Gateway Node

Choose the Switch Gateway Node option from the Tools menu to change a gateway node from one node to another. Selecting this option brings up the Select Gateway Node screen (see Figure 60).

Figure 60: Select Gateway Node screen

Select the gateway node to be switched to another node from the VIP pull-down list. Select the node that you want to switch. Click on Apply.

78 U42104-J-Z100-5-76


© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.k04

Add Backup Database Node

Choose the Add Backup Database Node option to add a backup database node. This brings up the Add Backup DBs screen (see Figure 61). Select a backup database form the Candidates window and click on Apply.

Figure 61: Add Backup DBs screen

Wizard

The Wizard menu option offers the following choices:

● New Configuration File—Select to create a new file using the wizard (refer to the Section “SIS Wizard”).

● Edit Configuration file—Select to bring up the Edit Wizard screen (see Figure 62). Find the file that you want to edit as follows:

a) Click on the node for the configuration file that you want to edit. This shows all of the SIS configuration files on that node.

b) Select the file that you want to edit.

c) The View and Edit buttons become active. To view the file, click on the View button (see Figure 52). Click the Edit button to open the configu-ration wizard for editing the selected configuration file using the wizard (refer to Section “SIS Wizard”).

U42104-J-Z100-5-76 79


Figure 62: Edit Wizard screen

80 U42104-J-Z100-5-76


© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.k04

4.1.2.4 Help

The Help menu option has help for all of the supported products in the GUI (see Figure 63). The menu items are as follows:

● Content

● About

Figure 63: Help menu options

U42104-J-Z100-5-76 81


Selecting Content opens up another window (see Figure 64). This screen lists all of the help topics per the products supported by the GUI and includes additional details of important procedures and menu items in the GUI.

Figure 64: Help contents

82 U42104-J-Z100-5-76


© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.k04

Selecting About reveals the version details of all of the packages installed on the node, including Cluster Admin (see Figure 65).

Figure 65: About option

U42104-J-Z100-5-76 83

Administering with the CLI Administration

4.2 Administering with the CLI

Use the dtcpadmin command to administer SIS from the command line (CLI).

The dtcpadmin command starts, stops, and reconfigures SIS as well as performing other administrative functions. The following list shows the dtcpadmin options and their meanings:

dtcpadmin -s Starts SIS on the local node.

Run this command on all nodes in the SIS cluster that are not database nodes.

dtcpadmin -u Stops SIS on the local node.

This command will fail on a database node if there are no backup database nodes and there are one or more non-database nodes still active. If the local node is inactive, then SIS will not report an error.

dtcpadmin -r config_file Reconfigures SIS. The new config_file is parsed and the configuration is sent to the designated database nodes.

This command can be used on any active node.

dtcpadmin -c config_file Makes the local node a database node. The node needs to be inactive. The first node called with this command reads content file, configures, and starts SIS on the local node. Additional nodes called with this command need filename to prevent a syntax error; however, the file contents are ignored and SIS starts on the local node. This local node then becomes a backup database node.

This command needs to be executed on at least one node.

To make SIS highly available, rundtcpadmin -c on at least two nodes so the infor-mation will be available for database failover.

84 U42104-J-Z100-5-76

Administration Administering with the CLI

© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.k04

I When executing this command on more than one node, the configuration file must exist and be syntactically correct. SIS disregards the configuration files on the additional nodes (that is, only the first -c is used).

dtcpadmin -g gateway_node vip_address

Changes the gateway node for the VIP address vip_address to the gateway node gateway_node.

dtcpadmin -f Pauses SIS on all nodes (freeze).

When dtcpadmin -f is executed, all incoming packets are ignored. This can lead to dropped connections.

dtcpadmin -w Resumes a paused SIS program (warm up).

dtcpadmin -n Displays the SIS configuration of the local node.

dtcpadmin -p Displays the current SIS configuration in a parsable format.

dtcpadmin -b Sets the given node as a backup database node. if no node name is given, it sets the current node as the backup database node. If the node is already a backup database node, no changes to the node are made.

dtcpadmin -d debug_level Sets debug level (0 to 5). SIS displays the messages on the system console. Refer to the Section “SIS daemon” for redirection information. Debug levels are as follows:

● 0 displays maximum debug information

● 1 through 4 display varying degrees of debug information

● 5 displays critical information (default)

This command can be used in combination with other options.

V Caution

Do not use the -d option unless advised to do so by support personnel. It can have unexpected results on the system.

U42104-J-Z100-5-76 85

SIS daemon Administration

4.3 SIS daemon

The dtcpd command starts the SIS daemon. The daemon is responsible for receiving the VIP definitions from the configuration file and sending them to the TCP stack on the service nodes.

The command has the following syntax:

dtcpd [-a][-d debug_file]

The -a option, used on Solaris platforms, automatically pushes the SIS module onto the network stack. The -d option writes debug messages to the designated debug file instead of the system console.

4.4 Displaying the status of SIS

Use the dtcpstat to display the status of SIS. The following list shows the usage for the dtcpstat command and its options:

dtcpadmin -q When used in combination with other options, this command displays no output (quiet).

dtcpadmin -t config_file Tests config_file for syntax errors and displays configuration information.

dtcpadmin -v Displays the version number of the dtcpadmin command.

dtcpadmin -?|-h Displays usage (help).

dtcpstat -? | -h Shows a brief help message.dtcpstat -N Shows the status of each of the SIS nodes.dtcpstat -l Shows the status of all the configured

services.dtcpstat -g [vip_address] Shows the gateway node associated with

the VIP address vip_address. If no vip_address is specified, it shows the gateway nodes for all the configured VIP addresses.

dtcpstat (without any options) Shows the status of all the connections.

86 U42104-J-Z100-5-76

Administration Displaying the status of SIS

© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.k04

The -q option can be used with any of the above options to suppress unnec-essary headers.

The -n option can be used to show network addresses including host names and service names, such as IP addresses and port numbers respectively.

4.4.1 Status by node

The dtcpstat -N command displays the status of every node in the cluster configured for SIS. Entering the dtcpstat -N command results in output similar to the following:

Type refers to the type of node. The meaning of the output for Type is as follows:

I State refers to the state of SIS on that node, not the state of the node.

4.4.2 Status by service

The dtcpstat -l command displays information about all available SIS services in the cluster. Specifying either of the options node_name or service limits the information to specific nodes or services. Only the services that are both configured and started are shown.

Id Name Type State

0 node1 DGS UP

1 node2 S UP

2 node3 dGS UP

3 node4 GS DOWN

D Database noded Backup database nodeG Gateway nodeS Service node

U42104-J-Z100-5-76 87

Displaying the status of SIS Administration

You can specify both service and node_name, but only one of each at a time. For instance, you can specify either rlogin or telnet for service, but you cannot specify them together. The following are examples of valid and invalid commands:

● Valid command:

dtcpstat -l telnet

● Invalid command:

dtcpstat -l telnet rlogin

I Either a port number or a name can be entered for service.

The output contains the following information:

● Service

● Name of the node on which the service runs

● State of the service (Available, Suspended, or Unknown)

● Connection count (Con count)

● Number of Suspended states for each service

A service is put into the Suspended state if the maximum number of pending connections is reached (see description of the backlog parameter in the listen(3N) manual page).

Con count shows the number of currently established connections for the specified service.

Entering the dtcpstat -l command with any of the options results in output similar to the following:

$ dtcpstat -lService Node Service State Con count Suspends

telnet node1 Available 1 0


login node1 Available 1 0


88 U42104-J-Z100-5-76

Administration Displaying the status of SIS

© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.k04

4.4.3 Status of SIS connections

Entering the dtcpstat command with no options displays information about all SIS connections in the cluster and results in output similar to the following:

$ dtcpstat -qtelnet node1 Available 1 0




$ dtcpstat -l node1Service Node Service State Con count Suspends



$ dtcpstat -l 23Service Node Service State Con count Suspends



$ dtcpstat -l telnetService Node Service State Con count Suspends



$ dtcpstatNode Id Local Address Foreign Address Gateways

node1 0 dtcp.eng.pyramid.login client1.eng.pyra.965 node1

node1 1 dtcp.eng.pyramid.telnet client1.eng.pyra.1141 node1



U42104-J-Z100-5-76 89

Displaying the status of SIS Administration

You can specify the following:

● One node or one service

● Both a node and a service

The service can be either a port number or a name. The output displays connec-tions of the specified node or service. The -n option prints IP addresses in dot decimal notation.

Entering the dtcpstat command with options results in output similar to the following:

$ dtcpstat -nNode Id Local Address Foreign Address Gateways

0 0 129.214.20.119.513 129.214.214.22.965 0

0 1 129.214.20.119.23 129.214.214.22.1141 0

1 0 129.214.20.119.23 129.214.214.28.54108 0

1 1 129.214.20.119.513 129.214.214.28.1015 0

$ dtcpstat node1Node Id Local Address Foreign Address Gateways



$ dtcpstat 23Node Id Local Address Foreign Address Gateways



$ dtcpstat telnetNode Id Local Address Foreign Address Gateways



90 U42104-J-Z100-5-76

Administration Debug messages

© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.k04

Domain names are truncated in the output.

4.4.4 Showing the gateway node

The dtcpstat -g command displays the gateway nodes for all the configured VIPs in the system. A VIP address can be specified after the -g option to show the gateway node only for that VIP address.

Some examples of the dtcpstat -g usage are as follows:

$dtcpstat -g

Vip Gateway (Name) Gateway (Id)www.mycompany.com fuji2 00ldap.mycompany.com fuji3 01$dtcpstat -g www.mycompany.com

Vip Gateway (Name) Gateway (Id)www.mycompany.com fuji2 00

$dtcpstat -gn www.mycompany.com

Vip Gateway (Name) Gateway (Id)192.168.17.1 fuji2 00

4.5 Debug messages

The dtcpdbg program displays debugging information for SIS.

V Caution

Do not use dtcpdbg unless advised to do so by support personnel. It slows down the system significantly.

See the Chapter “Debugging and troubleshooting” for more information on dtcpdbg.

$ dtcpstat node1 telnetNode Id Local Address Foreign Address Gateways


U42104-J-Z100-5-76 91

Debug messages Administration

92 U42104-J-Z100-5-76

© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.k05

5 Syntax rulesThis chapter consists of the Backus Naur Form syntax rules to which the config-uration file must conform.

[Config] ::= [NodeSecton] [GatewaySection] [InterfaceSection] |[AssignmentSection] [NodeSecton] [GatewaySection] [InterfaceSection]

[NodeSection] ::= [NodeDef] | [NodeSection] [NodeDef]

[NodeDef] ::= NODES [List]

[AssignmentSection] ::= [Assignment] |[AssignmentSection] [Assignment]

[Assignment] ::= STRING '=' [List] ';' | STRING '=' '(' [List] FAILOVER [List] ')' ';'

[CCNodeList] ::= [Blist] | [CcNodeList] [Blist]

[ServNodeList] ::= [Alist] |[Alist] [ServNodeList]

UdpServNodeList ::= [IPAddress] |'(' [IPAddress] FAILOVER [List] ')'

[PrivateAlist] ::= [IPAddress]

[ProxyAlist] ::= [IPAddress] |'(' [IPAddress] FAILOVER [List] ')'

[Alist] ::= [IPAddress] |'(' [List] FAILOVER [List] ')'

[Bnum] ::= NUMBER

[Blist] ::= [Alist] |[Alist] ':'[Bnum]

[List] ::= [IPAddress] |[List] [IPAddress]

[InterfaceSection] ::= [InterfaceDef] |[InterfaceSection] [InterfaceDef]

[InterfaceDef] ::= [VipDef] |[ProxyDef] |[PrivateDef]

[VipDef] ::= [VipStart] [VipList] '{' [VipBody] '}'

[VipStart] ::= VIP

[VipList] ::= [VipAddress] |[VipList] [VipAddress]

[FourBytes] ::= HEXNUMBER|DOTNUMBER

U42104-J-Z100-5-76 93

Syntax rules

[IPAddress] ::= [FourBytes] | NUMBER |STRING

[VipAddress] ::= '(' [IPAddress] [IPAddress] ')' |'(' [IPAddress] [IPAddress] [PGateway] ')'

[VipBody] ::= [ServiceSection] |[AssignmentSection] [ServiceSection]

[GatewaySection] ::= [GatewayDef] |[GatewaySection] [GatewayDef]

[GatewayDef] ::= GATEWAYS [List]

[ServiceSection] ::= [ServiceDef] |[ServiceSection] [ServiceDef]

[ServiceDef] ::= [SerStart] [PortList] [Schedule] |[SerStart] [PortListDPO]

[SerStart] ::= SERVICE

[PortList] ::= [PortDef] |[PortList] [PortDef]

[Pgateway] ::= STRING

[PortDef] ::= [PortValue] |[PortValue] DCL

[PortListDPO] ::= [PortDefDPO] |[PortListDPO] [PortDefDPO]

[PortDefDPO] ::= [PortValue] DPO [PortValue]

[PortValue] ::= [pORTrANGE] |[PortVal] |[PortRangeProto] |[PortValProto]

[PortRange] ::= [PortVal] ':' [PortVal]

[PortValProto] ::= [PortVal] '/' [ProtoVal]

[ProtoVal] ::= NUMBER |STRING

[PortVal] ::= NUMBER |STRING

[Float] ::= FLOAT

[Schedule] ::= [KEEPLOCAL] |[CLBASED] [ServNodeList] |[SYSLOAD] [ServNodeList] |[ROUNDROBIN] [ServNodeList]|[SPILLOVER] [ServNodeList] AT [FLOAT] TO [ServNodeList]|[CONCOUNT [CcNodeList] |NONE [UdpServNodeList]]

[ProxyDef] ::= PROXY [IPAddress] [IPAddress] [ProxyAlist] |PROXY [IPAddress] [IPAddress] [ProxyAlist] [Pgateway]

94 U42104-J-Z100-5-76

Syntax rules

© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.k05

Non-terminal symbols are written in mixed case and are enclosed in brackets ([]). The following terminal symbols (upper case) are undefined: INTEGER, STRING, HEXNUMBER, and DOTNUMBER.

Uppercase strings not enclosed in brackets ([]) are keywords. In a configu-ration file, they must be entered literally.

Character literals are shown enclosed in single quotes (''). In a configuration file, they are entered without quotes. If no whitespace is shown between a symbol and a literal, none is allowed.

If [PORT] is specified as a [STRING], it cannot take the value ftp-data, and if it is specified as a [NUMBER], it cannot take the value of 20.

[PrivateDef] ::= PRIVATE [IPAddress] [IPAddress] [PrivateAlist]

U42104-J-Z100-5-76 95

Syntax rules

96 U42104-J-Z100-5-76

© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.k06

6 Debugging and troubleshootingThis chapter contains information about the dtcpdbg command, which is used for debugging purposes. In addition, there is a section on troubleshooting to assist you with common configuration and administration issues.


● The Section “dtcpdbg” describes the dtcpdbg command and provides an example of debug output.

● The Section “Troubleshooting” lists various debugging and troubleshooting solutions for SIS.

6.1 dtcpdbg

V Caution

Do not use dtcpdbg unless directed to do so by support personnel. It slows down the system significantly.

The dtcpdbg command has the following syntax:

Enter the following commands after invoking dtcpdbg:

dtcpdbg -?|-h Displays usagedtcpdbg -G Displays debugging output for all nodes

help Print this list of commands.quit Quit dtcpdbg.stat Show current setting of dtcpdbg.global Start/stop global output (same as -G

option).detail Start/stop displaying detailed output.tocon Stop/continue duplicating output to

system console.[Return] Stop/continue debugging output to tty

screen.redirect file_name Start/stop redirecting output to file.

U42104-J-Z100-5-76 97

dtcpdbg Debugging and troubleshooting

When you execute dtcpdbg, SIS displays the status (the same output as the stat command). SIS displays the output as follows:

node_ID: message_length DETAIL message

DETAIL is shown only if the detail flag has been set by the detail command. It has the following syntax:

debug_level (module_name, line_number)

The default debug_level is PANIC. The amount of output increases as the debug_level increases from PANIC to DEBUG. Debug levels are as follows:

● DEBUG

● TRACE

● LOG

● NOTICE

● WARNING

● PANIC

For example, entering the dtcpdbg command results in output similar to the following:

$ dtcpdbgconsole flag: local tocon detail(NU:DEBUG)(DB:DEBUG)(GW:DEBUG)(SV:DEBUG)(PS:DEBUG)(DM:DEBUG)(VI:DEBUG)(DR:DEBUG)0: (102) TRACE GW (gateway.c, 1202) dtcp_gw_process_arp: req 00:e)b)df:d5:0: (102) TRACE S! (gw_sniffer.c, 365) dtcp_gw_send_arpmsg: to 00:e0:b0:dr_d5:

dup Duplicate output to file and screen.level [module_name|all|ALL] debug_level

Change output level.

98 U42104-J-Z100-5-76

Debugging and troubleshooting Troubleshooting

© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.k06

The amount of debugging information depends on the setting of debug_level. To set the level of output at DEBUG for module NU, perform the following steps:

1. After the system prompt, enter the following:

$ dtcpdbg

2. Enter:

level NU DEBUG

I dtcpdbg has no prompt.

6.2 Troubleshooting

Use the following steps for debugging and troubleshooting SIS:

● Check if CF is functioning and verify that the nodes are up (refer to the CF installation guide for further information).

● Use the following command to check if dtcpd is running:

ps -ef | grep dtcpd

● Verify that the SIS configuration contains the correct nodes and services:

1. Use the dtcpadmin -p command to check the configuration file.

2. Enter the dtcpadmin -r command to reload the configuration.

● Use the following command to verify that the services scheduled are actually running:

ps | grep [httpd] <service>

● Use the following command to verify that the VIPs are configured and functioning:

netstat -ni.

U42104-J-Z100-5-76 99

Troubleshooting Debugging and troubleshooting

The output for the netstat -ni command should look similar to the following:

I The important information is the driver/interface name in the first column. Some of the lines in the above examples have been truncated.

● Check the system logs for any error messages:

1. Use the dmesg command to display the most recent error messages.

2. For additional error messages, look at the following file:

/var/adm/messages

● Check if the services are available to SIS:

1. Use the following command:

dtcpstat -l <service>

2. If the service is configured and appears in dtcpadmin -p but not in dtcpstat -l <service>, then try stopping (killing) and restarting the service.

Some services such as telnet and ftp are started by inetd. To restart these services, you need to restart the inetd.

I To kill the inetd, use a local console to log into the node.

$ netstat -in

Name Mtu Net/Dest Address [truncated]lo0 8232 127.0.0.0 127.0.0.1

hme0 1500 192.168.21.0 192.168.21.14

hme1 1500 192.168.22.0 192.168.22.14

le0 1500 172.25.0.0 172.25.219.14

100 U42104-J-Z100-5-76

© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.k07

7 Manual pagesThis chapter lists the online manual pages for SIS.

To display a manual page, type the following command:

$ man man_page_name

1M. System administration

dtcpadmin(1M)administer SIS

dtcpd(1M) start the SIS daemon for configuring VIPs

dtcpdbg(1M) display debug information about SIS

dtcpstat(1M) display status of connections within SIS

U42104-J-Z100-5-76 101

Manual pages

102 U42104-J-Z100-5-76

© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.six

Index
Aadministering SIS
CLI 84Cluster Admin 57

assigning external connectivity 10Available 88

Bbackup database node 6

Cchecking syntax 75CLBASED 18client based algorithm 9Cluster Admin

administering 57CF 10configuring 23main administration screen 57starting SIS 72

Cluster Foundation 13Cluster Admin 10interconnect 14nodes 32

Clusterwide Operations menu 71clusterwide summary table 57configuration 22

reloading files 73configuration file

creating 79editing 79example 55GATEWAYS 16NODES 15syntax rules 93variables 14viewing 73

configuration wizard 73configuring

Cluster Admin 23text editor 14

creating a configuration file 79

Ddaemon, SIS 86DEBUG 98Debug menu 69debug messages, displaying 91debug_level 98debugging 99displaying

debug messages 91, 97interfaces 60SIS 86status by node 87status by service 87

documentation 1dtcpadmin 84

command 84options 86

dtcpd 86dtcpdbg 91, 97dtcpstat 86–91

Eediting the configuration file 79

Ffailover 10File menu 69

Ggateway nodes 6GATEWAYS 16

HHelp menu 81

U42104-J-Z100-5-76 103

Index

Iinterconnect 14interface definitions 16

PRIVATE 22VIP 16VIP body 17

interfacedef 16interfaces

details 67node view 61, 62

Interfaces view 63IP address 16

Kkeep local algorithm 9KEEPLOCAL 17

Llevel 98list of services 65LOG 98

Mmain administration screen 57manual pages list 101menus

Clusterwide Operations 71Debug 69File 69Help 81Settings 70Tools 71Wizard 79

Nnetmask 16node_name 88NODES 15nodes

CF 32details 60, 65, 68view 59

NOTICE 98

Ooperations on individual nodes 76

PPANIC 98pausing SIS 76prefgateway 16primary database node 6PRIVATE 22proxy addresses 10

Rreconfiguring SIS 84redirect 97refreshing statistics 70reloading configuration files 73restoring the configuration 76resuming SIS 76round robin algorithm 9ROUNDROBIN 18

Sscalability

network services 5SIS 5

scheduling algorithmsCLBASED 18KEEPLOCAL 17ROUNDROBIN 18SPILLOVER 18SYSLOAD 18

service 87service nodes 6, 10Services view 66Settings menu 70SIS

daemon 86network services 5starting 84status 86stopping 84

SIS configuration tree 57, 58spill over algorithm 9SPILLOVER 18

104 U42104-J-Z100-5-76

Index

© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.six

startingindividual nodes 76

starting SISCLI 84Cluster Admin 72clusterwide 72individual node 76

starting SIS daemon 86state of services

Available 88Suspended 88Unknown 88

statistics 70status by node 87status by service 87status, displaying 86stopping individual nodes 76Stopping SIS

individual node 76stopping SIS

CLI 84clusterwide 71

Suspended 88syntax

check 75rules 93

syntax rules 93SYSLOAD 18system load algorithm 9

Ttocon 97Tools menu 71TRACE 98troubleshooting 99

UUnknown 88using the menu bar 69

Vvariables 14viewing the configuration file 73VIP

See Virtual Interface ProviderVirtual Interface Provider 5

body 17interface definition 16

WWARNING 98Weighted Connection Count algorithm

9Wizard menu 79

U42104-J-Z100-5-76 105

Index

106 U42104-J-Z100-5-76

© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.nac

Comments on PRIMECLUSTER Scalable Internet Services Configuration and Administration

U42104-J-Z100-5-76

CommentsSuggestionsCorrections

✁

Submitted by

Fujitsu Siemens Computers GmbHUser Documentation33094 PaderbornGermany

Fax: (++49) 700 / 372 00001

email: [email protected]://manuals.mchp.siemens.de

© S

iem

ens

Nix

dorf

Info

rmat

ions

syst

eme

AG 1

997

Pfad

: C:\B

ooks

502

\SIS

\PC

LSIS

Con

figAd

min

.nac

Comments on PRIMECLUSTER Scalable Internet Services Configuration and Administration

U42104-J-Z100-5-76

CommentsSuggestionsCorrections

✁

Submitted by

Fujitsu Siemens Computers GmbHUser Documentation33094 PaderbornGermany

Fax: (++49) 700 / 372 00001

email: [email protected]://manuals.mchp.siemens.de

Date post:	01-May-2020
Category:	Documents
Upload:	others
View:	4 times
Download:	0 times

PRIMECLUSTER™ · SIS eliminates single points of failure and ensures availability as follows: If...

Documents