zxin10 sacp imp platform installation guide

Internal Use Only▲

All Rights reserved, No Spreading abroad without Permission of ZTE of 55

ZXIN10 SACP

IMP Platform Installation Guide

ZTE CORPORATION



Revision History

Document No. Version No. Drafted

by/Modified by

Examined

by

Drafted/Mod

ified on Reasons

Major

Modifications

R1.1 Wan Heng Wan Heng 2010-05-14 SOP document

compilation in 2010

Reviewed

modifications



Contents

Chapter 1 Overview ........................................................................................................................ 5

1.1 Introduction ............................................................................................................................ 5

1.2 Installation Environment Plan ................................................................................................ 5

1.3 Procedure Description of Installation and Configuration ....................................................... 6

1.3.1 Flow Chart .................................................................................................................... 6

1.3.2 Procedure Description ................................................................................................. 6

Chapter 2 Installation of IMP Master Node Software .................................................................. 8

2.1 Overview ................................................................................................................................ 8

2.2 Installation of IMP Platform.................................................................................................... 8

2.3 Configuration of IMP Platform .............................................................................................. 11

2.3.1 Configuring imp.ini File ............................................................................................... 11

2.3.2 Configuring itcom.ini File ............................................................................................ 18

2.3.3 Configuring module.ini File ........................................................................................ 23

2.4 Running IMP Configuration Script ....................................................................................... 26

2.5 Starting IMP Platform ........................................................................................................... 27

2.6 Ending IMP Platform ............................................................................................................ 28

2.7 Restarting IMP Platform ...................................................................................................... 28

2.8 Checking IMP Log ............................................................................................................... 29

Chapter 3 Installation of IMP Slave Node Software .................................................................. 31

3.1 Overview .............................................................................................................................. 31

3.2 Installation of IMP Slave Node ............................................................................................ 31

3.3 Starting IMP Platform ........................................................................................................... 32

3.4 Checking IMP Log ............................................................................................................... 33

Chapter 4 Installation of Cluster System Software ................................................................... 34

4.1 Overview .............................................................................................................................. 34

4.2 Preparation before Configuring NewStartHA ...................................................................... 34

4.3 Configuring NewStartHA Service ........................................................................................ 35

4.3.1 Initialization Configuration .......................................................................................... 36



4.3.2 Method of Modifying Configuration ............................................................................ 42

4.3.3 Check on Configuration ............................................................................................. 43

4.4 Check on Cluster Status ...................................................................................................... 49

4.4.1 Check Whether Floating IP Address Is Activated ...................................................... 49

4.4.2 Check on IMP Software Procedure ........................................................................... 50

4.4.3 Check on Starting Log ................................................................................................ 50

4.4.4 Check on Cluster HA Starting Status ......................................................................... 51

4.5 Cluster Switchover Test ....................................................................................................... 52

Chapter 5 SACP IMP System Debugging ................................................................................... 54

5.1 Overview .............................................................................................................................. 54

5.2 Debugging Procedure Description ...................................................................................... 54

5.2.1 Flow Chart .................................................................................................................. 54

5.2.2 Procedure Description ............................................................................................... 54

ZXIN10 SACP IMP Platform Installation Guide Internal Use Only▲


1 Overview

1.1 Introduction

ZXIN10 SACP IMP, the interface between SACP system and its peripheral

system such as BOSS system, provides such functions as message interaction

and processing of subscriber relevant service data between SACP system and

other systems. This document is to guide the installation and configuration of

SACP IMP platform.

Chapter 2 describes the installation of IMP master node software.

Chapter 3 presents the installation of IMP slave node software.

Chapter 4 introduces the installation and configuration of the cluster system.

Chapter 5 describes the debugging of SACP IMP system.

1.2 Installation Environment Plan

Environment Description

ZXIN10 SACP IMP uses SUSE9 SP4 operating system. The cluster uses

Newstartha cluster software.

Software Version Description

1. This guide is applicable to IMP platform version baseline:

ZXINOS2.1-IMPV2.1.14

2. The location of IMP platform version files:

ZXINOS2.1-IMPV2.1.14\impver\imp32_for_suselinux

Note:

Version No. in the guide is only used for examples. For the actual version,

please refer to the Commissioning Task Statement.

Installation Plan

For the naming rule, IP address plan, and module No. plan of SACP IMP cluster,

please refer to Table 1.2-1. Please plan according to the specific situation on

site.



Table 1.2-1 Installation Plan of SACP IMP

Host Name Service IP Address Heartbeat IP

Address

Module

No.

Floating IP

address

IMP1_1 10.131.33.158 192.168.12.4 160 10.131.33.160

IMP1_2 10.131.33.159 192.168.12.5 160

1.3 Procedure Description of Installation and Configuration

1.3.1 Flow Chart

IMP master node

software installation

Start

IMP slave node


Cluster


End

SACP interface

system Debugging

Figure 1.3-1 Procedure of SACP IMP installation and configuration

1.3.2 Procedure Description

Purpose

To complete the installation and configuration of IMP platform of ZXIN10 SACP

system to provide the running environment for each interface

Background

ZXIN10 SACP IMP platform provides a unified running environment and each

interface of SACP service must run on this platform. The platform monitors each

process and its running status through zxmoni, and enables the master/slave

function cooperated with the cluster software. When faults occur on the master



node, IMP cluster system will switch over to the slave node to recover the

service.

Prerequisites

1. The operating system of IMP master/slave has been installed.

2. The version has been downloaded from the customer service center.

3. The cluster software disks have been sent to the site.

Personnel

ZXIN10 SACP IMP devices debugging engineers on site

Procedure Description

1. Complete the installation and configuration of IMP in the master node.

For detailed information, please refer to Chapter 2.

2. Complete the installation and configuration of IMP in the slave node. For

detailed information, please refer to Chapter 3.

3. Install and configure the cluster system of the master and slave. For


4. Perform the integrated debugging for SACP IMP cluster and service. For




2 Installation of IMP Master Node Software

2.1 Overview

This chapter mainly presents the installation of IMP platform master node, and

describes the configuration files of the platform.

Section 2.2 introduces the installation of IMP platform.

Section 2.3 describes the configuration of IMP platform, mainly the

configuration of imp.ini, itcom.ini, and module.ini.

Section 2.4 presents the method and function of running the configuration script

after editing the configuration files.

Sections 2.5, 2.6, 2.7, and 2.8 describe the method of starting and ending the

platform, and the way of checking logs.

2.2 Installation of IMP Platform

Purpose

To install the setup script in the program by executing IMP software to create the

running environment for IMP on the server

Prerequisites

1. The operating system of IMP master node has been installed.

2. The version has been downloaded from the customer service center.


The following is the operation procedure to create the running environment for

IMP software.

1. Log in as user root. Execute the following commands to create the

installation path.

# mkdir /home/setup

# chmod 777 /home/setup

2. Upload the version file imp_linux.Z via FTP in binary mode to the

directory /home/setup of IMP master node as user root.

3. Execute the following commands to decompress the software package.

# cd /home/setup



# gzip –d imp_linux.Z

# tar xvf imp_linux

After decompressed, the files and directories generated under the directory

/home/setup are shown in Table 2.2-1.

Table 2.2-1 Contents of Running Environment Package after Decompressing

Directories or Files Description

setup Install the script.

bin/* imp.tar (all the running environment of

zxin10 users) etc/*

lib/*

Suseha/* The cluster script using skybility cluster

software.

newstartha/* The cluster script using newstartha

cluster software.

setup.post Imp configuration script

4. Execute the following command in the directory /home/setup, and run

the installation script of IMP platform.

# ./setup os=linux db= none lang=gbk cluster dev=imp

During the installation, IMP 2.1 platform does not prompt to enter the user

name and password of zxin10. The defaulted password of zxin10 user by the

script is os10+ZTE.

Notice:

Setup script completes the following tasks:

1. Check whether various software packages are all installed in the cluster

environment.

2. Check the size of the system file (if it is less than 6 GB, it should be

expanded).

3. Create Sybase group and the zxin10 user and Sybase user of the group.

4. Set the environment variables of all the users.

5. Copy IMP software to the relevant directory, and modify the home

directory and right.

The specific method to use setup script is as follows:



./setup [os={operation system name}] [db={database name}] [silence]

[cluster|nocluster] [lang={langauge}] dev=imp

Parameters of the command lines (except dev=imp) are all optional and case

sensitive. The value of the parameter is not case sensitive, and space is

allowed before and after ―=‖. For specific parameter description, please refer to

Table 2.2-2.

Table 2.2-2 Parameter Description of Setup Script

Parameter Description

os (operating system name) This item explicitly identifies the OS name and is used

when the tool cannot identify correctly the running OS

currently (tool report "un-support database system,

exit.")The supported options currently are:

os=HPUX, os=AIX, os=SunOS, os=Linux

db (database name) This item specifies the database system name. Thus,

this tool does not prompt the user to select the database

system name during the following execution. The

supported options currently are:

db=none, db=sybase, db=sybase12, db=sybase12_5,

db=sybase, db=sybase92

They are respectively corresponding to none

database (not establish Sybase database and database

software), sybase ASE11.9.2 version, sybase ASE12.0

version, sybase ASE12.5 version, sybase8.1.7 version

and Sybase version.

Silence This tool does not print progress prompt words like

standard output during the execution, but it still records

LOG and generates the file of zxin_inst_log in the

currently enabled directory.

cluster|nocluster It decides whether to pre-configure CLUSTER

environment. If these parameters are not configured,

the tool would take whether CLUSTER software

package is installed as the foundation to pre-configure

CLUSTER environment. If CLUSTER is assigned but

the CLUSTER software package is not installed, setup

would exit.

Lang (langauge) It decides the language environment. If this parameter

is not configured, the default is simplified Chinese. If the

corresponding language environment is not installed in

the OS, setup would exit. The supported options

currently are:

Lang=gbk, lang=big5, lang=enu

They are respectively corresponding to simplified



Parameter Description

Chinese (GBK), traditional Chinese (BIG5) and English.

Dev (device type) This parameters means the type of the current device

(whether it is IMP device).The only supported option

currently is:

During the installation of IMP, configure dev=imp.

2.3 Configuration of IMP Platform

2.3.1 Configuring imp.ini File

Background

Imp.ini is the basic configuration file of IMP platform and is mainly used to

configure such basic properties used by the platform as interface program, log

path and database connection.

Prerequisites

The installation script of IMP platform has been successfully executed.


The procedure of imp.ini configuration is as follows:

1. Log in the IMP master node as user zxin10.

2. Enter the directory /home/zxin10/etc.

$cd /home/zxin10/etc

3. Edit the configuration file imp.ini.

$vi imp.ini

The example is as follows. For the detailed configuration information, please

refer to Table 2.3-1.

[general]

alarm = 2 ; alarm module enabling flag: 1 – enable, 2

– enable the virtual node alarm at the same time, others – not enable

comm = 1 ; communication module enabling flag: 1 –

enable, others – not enable

activeNewComm = 1 ; new communication module enabling flag: 1 –

enable, others – not enable, the default is 1

dbconn = 0 ; number of database connections: idf1,

idf2 ...

logfilenum = 30 ; number of IMP log files, 500 at most

interfacecount = 0 ; number of IMP: interface1, interface2…



ftpcnt = 0 ; number of FTP thread: ftpap1, ftpap2…

cdrconvertcnt = 0 ; number of cdrconvert dll, cdrconvert1,

cdrconvert2..., the largest is 10

monitor = 0 ; Monitor auto switchover enabling flag (only

valid on Windows): 1 – enable, others – not enable

;log storage position, default is c:\zxin10\log

logfilepath = /home/zxin10/log

Modify each parameter of imp.ini file according to the requirement of

interface loading on site.

4. After edition, execute the following command to close imp.ini file.

: wq!

Configuration Item Description

Table 2.3-1 Configuration Item of imp.ini File

Item Parameter Meaning Parameter Configuration

[general]

Parameters in general are

the core configuration

parameters of IMP.

Configuration of these

parameters decides whether to

start the corresponding

functions of IMP or not.

-

Alarm

It defines whether any alarm

of IMP has been sent to sms

alarm platform of SMP.

1 – enable, 2 – enable the

virtual node alarm at the same

time, others – not enable,

default value: 0

comm It defines whether IMP starts

itcom.ini configuration or not.

1 – enable, others – not

enable. When comm=1,

itcom.ini configuration file

valid; otherwise, itcom.ini is

not valid.

dbconn

It defines whether IMP

needs to connect with

database and the number to

connect with database. When

dbconn is N > 0, it is

necessary to configure the

specific database under [idf*],

and 30 database connection

can be configured at most.

idf1; idf2; … idfN should be

configured according to the

number of N (N>0) configured.

logfilenum It defines the log number of

IMP and the number can be

The number of IMP log files,

is 150 at most and the default




150 at most. IMP log is always

in the directory of

/home/zxin10/impsys/log.As

for the platform version above

IMP1.3.18; log path can be

configured freely.

number is 30.

interfacecount

It defines whether IMP

mounts to service***.dll

application and the application

number. When interfacecount

is the value of N > 0, it is

necessary to configure specific

database under [interface*].

100 IMP application can be

configured at most.

interface1; interface2; …

interfaceN should be

configured according to the

number of N (N>0) configured.

ftpcnt

It defines thread number of

started FTP. When ftpcnt is the

value of N > 0, it is necessary

to configure specific FTP

under [ftpap*].30 FTP

functions can be enabled at

most.

ftpap1; ftpap2; … ftpapN

should be configured

according to the number of N

(N>0) configured.

Cdrconvertcnt

It is only be valid for the

version above IMP1.4. It can

mount to the program of

converting standard CDR to

DLL and it can mount to

10such programs at most.

Cdrconvert;

cdrconvert2; …cdrconvertN

should be configured

according to the number of N

(N>0) configured.

monitor

Monitor automatically

switchovers enabling flag (it is

valid on the Windows platform

only)


enable

logfilepath It is the position of log

directory.

The default path is

c:\zxin10\log\

[idf*]

idf* mainly configures

specific database connection

and configures separately

database IP address,

database type, connection

number, username, password,

etc.

-

dbmodule It is the database server

module No. For example, 133




ipaddr It is the IP address to be

connected to database server. For example,10.40.90.116

servertype It is the server type of

connected database.

0 - MS SQL Server; 1 –

Sybase; 2 – Oracle; 3 - ODBC

of Informix

idfnum It is the connected number

of database server. The default value is 5.

bdusername It is the username of

connected database server. The default is zxin_smap.

dbpasswd

It is the password of

connected database server

username.

The default is zxin_smap.

conntype It is the connected type of

database server.

0 – plain mode, 1 –

non-plain mode

spacecheck It is the database server

space check flag.


enable, only applicable to

database type 1

Port

It is the port No. of

connected database server

and is valid when the database

is XBASE.

For example, 8433

[interface*]

It is the applied configuration

of specific IMP and is

configured according to IMP

application.

-

mainpno

It is the mainline program

applied by IMP. The number in

the name of application file is

the mainline program No. of

the application.

For example, 304

slavepno

It is the applied thread

program No of IMP. Generally,

there is no sub-thread No. for

IMP application. Please refer

to the specification document

of the version to ensure

whether there is sub-thread of

the application. When there

are several sub-threads, use

comma to separate each

sub-thread No.

Complete according to

specific application and it

needs not to complete if there

is no sub-thread.

dllname It the applied name of IMP,

that is, the file name of IMP For example, service304.dll




application.

stacksize It is the stack size of thread,

and its unit is KB. The default is 64.

servicekey

If multi-CP is adopted, when

a message is sent to CP to

trigger the service, a CP will be

selected according to the

service key.

The default value is 0.

[imptrace]

It configures IMP trace

function, adds thread No. of

the trace. IMP software will

print corresponding thread log

in the file of

c:\zxin10\log\imptrace_*.dat.

For example, the range of

FTP thread is 400~429. To add

400, the platform will print the

process log of [ftpap1] in the

file of

c:\zxin10\log\imptrace_0.dat.

logwrite It is to trace log-writing flag.

1 – buffer mechanism (when

the flow is large and Trace log

is written frequently), others –

write the Trace log directly.

tracepno

It is to trace thread No., and

be separated by comma. It is

configure through IMPTrace

for configuration items.

For example, 400

encyptfname

It is the configuration name

allowing coding. If there are

several file, use comma to

separate.

To fill with "all" is to enable

this function for all the other

configuration files.

[assist] It is mainly used to read out

card number segment of SMP. -

cardmap It is to read out card number

segment flag. 1 – read, others – not read

getzxin10 It is to get zxin10 password

flag. 1 – read, others – not read

getdevice It is to get CP information. 1 – read, others – not read

impstat It is the statistics report flag: 1 – enable, others – not

enable

synctimeofsmp

It is to synchronize the

system time (according to the

time on SMP, presently HPUX

does not support it).

The default value is 0.

dbtype It is the default database

type.


Sybase; 2 – Oracle; 3 -

Informix

versionflag It is the default version flag. 1 - V3.4; 2 - V3.4.1; 3 -




V3.50; and the default value is

3.

[vmalarm]

It is to enable virtual alarm

configuration. IMP alarm can

be checked on the sms of

SMAP software. When the

parameter of alarm in [general]

is configured 2, it will be valid;

otherwise, it will be not used.

-

ftpaddr It is the IP address of SMP

service processing server. For example,10.40.90.133

ftpuser It is the username of SMP

service processing server. The default is zxin10.

ftppwd It is the FTP password of

service processing server. The default is zxin10.

ftpflag It is the SMP office ID. 0 – plain mode, 1 –

non-plain mode

remotepath It is the FTP remote path. For example, ./dbs/

dbtype It is the database type.


Sybase; 2 – Oracle; 3 -

Informix

[monitor]

It is the special configuration

of imp monitor, and it is not

used generally.

monitortime1 It is the monitoring duration,

and its unit is s.

It will stop reading the

succeeding information when

it is 0.

threadpno1

It is corresponding to the

monitoring duration thread

No., separated with comma.

For example, 304

[ftpap*]

It enables FTP function of

IMP application, and it enables

such general operations of

FTP as download of

configuration files and upload.

-

ftpgetaddress

It is to download IP address

of file server. When it is null, it

indicates files are not

downloaded.

For example,10.40.90.112

ftpgetusername It is to download FTP server

username. The default is zxin10.

ftpgetpassword It is to download the

password of FTP server The default is zxin10.




username.

ftpgetdir

It is the directory of filed

acquired. When ftpgetaddress

is null, it is the local path of

downloaded files.

For example, cdr

ftpgetscp It is the downloading type of

FTP server.

0 – download file with plain

mode, others – obtain the

password from SCP.

ftpputaddress It the IP address of

uploading file server.

When it is null, it does not

upload files.

ftpputusername It is the username to upload

FTP server. For example, wxp

ftpputpassword It is the username password

to download FTP server. For example, 4321

ftpputdircount

It is the number of the saved

directories. It is valid only

when to download file to local

path.

For example, 3

ftpputdir

It is the directory of saving

files. It is the local path of

uploading files when

ftpputaddress is null. 10 local

directories can be set at most,

separated with the comma.

The following directories can

be set to other drive letters.

For example,

c:\zxin10\cdrdowndir\

putdirproperty It is the property of

uploading file directory.

0 – save as original, 1 –

save according to the date,

corresponding to ftpputdir. It is

valid only when files are

downloaded to the local path.

putdirbakdays It is the file backup time of

uploading file directory.

0 – forever, others – backup

date, corresponding to

ftpputdir. It is valid only when

files are downloaded to the

local path.

ftpputscp It is the uploading type of

FTP server.

0 – download file with plain

mode, others – obtain the

password from SCP.

opertype It is the FTP file mode. 0 – BIN; 1 – ASC

filename It is the file name. Generally, it is *.r.

dealflag It is the operation performed

on the original file after it is

0 – no operation, 1- delete, 2

– save to another directory, 3 –




retrieved. change the file suffix. When

dealFlag is 2, it is another

directory (The default is the

backup directory); when

dealFlag is 3, it is the new file

suffix (The default is old).

tempdir It is temporary directory.

When dealFlag is 2, it is

another directory (The default

is the backup directory); when

dealFlag is 3, it is the new file

suffix (The default is old).

begintime

It is the beginning time of

FTP operation and its form is

DDHHMISS.

The default is 00000000.

endtime

It is the end time of FTP

operation and its form is

DDHHMISS.


interval

It is the time interval of FTP

operation, and its unit is s, and

it is defaulted as 3600s (1

hour).

The default is 60.

[cdrconvert*] It is the configuration only in

the version of IMP1.4. -

dllname It is the converted dll name. For example,

spmcconvert.dll

convertdir

It is the directory of files

needing conversion, and

should be the directory to store

original CDR of $ftpputdir

configuration in [ftp*].

For example,

c:\zxin10\cdrdowndir\

interval

It is the conversion time

interval, and CDR files under

the directory are converted at

the interval.

The default is 120.

inpostfix It is the file suffix needing

conversion. The default is.r.

2.3.2 Configuring itcom.ini File

Background



itcom.ini is the configuration file for IMP to communicate with other NEs. It

configures such basic parameters as IP address, port of IMP as the client,

server terminal, or communication.

Only when comm item of [general] in imp.ini file is 1, can the configuration file

itcom.ini be valid.

Prerequisites

1. The script has been installed successfully.

2. Determine communication mode: client or server, long connection or

short connection.


The following is the configuration procedure of itcom.ini file.

1. Log on as the user zxin10.



3. Open the configuration file itcom.ini.

$vi itcom.ini

4. Edit the contents of itcom.ini file, as shown below.



[general]

module = 160 ; Node No.

postoffice = 16 ; Office ID

areacode = 21 ; Area code

myipaddress = 0.0.0.0 ; the IP address of the host

alarmmodule = 133 ; Alarm node No.

servercnt = 0 ; server terminal configuration number

clientcnt = 0 ; client configuration number

; Support WINNTTCP connection to use non-5000 port (5000 port connection is

always WINNTTCP connection)

; 1 – support (peermodule configured of the client is valid all the time. To make it

ordinary connection, peermodule must be 0). The default is 0 (to make it internal

connection, the port No. should be 5000).

noLimitPort = 0

[server1]

mainpno = 306 ; bindind thread No. (invalid for internal connection)


port = 5001 ; port No.

socketnum = 2 ; the maximum connection number allowed

Whether WINNTTCP connects to service terminal (It is valid when noLimitPort is 1 and

is not valid when port No. is 5000.)

isWinnttcp = 0

[client1]

mainpno = 306 ; bindind thread No. (invalid for internal connection)


peeripaddress = 10.40.90.106 ; the IP address of peer end.

port = 5000 ; port No. of peer end

peermodule = 133 ; It is the module No. or node No., and can be valid when

peer end is IN system.

peerpost = 16 ; It is the office ID of the peer end and can be valid

when peer end is IN system.

socketnum = 1 ; connection number

longconn = 1 ; Whether it is the long connection. 1 – long

connection.

commpno = 101 ; assigned thread No. of the connection.

Please modify each parameter of itcom.ini file according to the

requirement of loading the interface on site.

5. After the file is edited, close itcom.ini file using the following command.

: wq!

Description of Configuration Items



Table 2.3-2 Configuration Items of itcom.ini File


[general]

Parameter configuration

of general decides IMP

communicates with other

programs as server or

client. When

communicating, it

determines only one

communication connection

through module, postoffic

and thread No.

Only when comm of

[general] segment in imp.ini

file is 1, can the

configuration file of itcom.ini

be valid.

module

It is the module No. of

IMP itself and it is the only

one of all network.

The range of module is

133~254 and usually, it is

more than 155.

postoffice

It is the office ID of IMP

and should be the same

with the whole network.

For example, 16

areacode It is the area code. For example, 21

myipaddress It is the IP address of the

host.

When there are several

IP addresses of IMP

machine, myipaddress

should assign the IP

address. When there is only

one IP address, it can be

directly configured as

0.0.0.0.

alarmmodule It is the alarm module No.

When SCP and SMP are

installed together, the

module No. is 133, and the

default value is 133.

servercnt

It is the configuration

number of server terminal. It

the number when this IMP

is as the server terminal of

the communication.

To make the

communication between

IMP as service terminal and

other programs valid, the

number of connected client

should be the value of

service terminal.

clientcnt

It is the configuration

number of client, and it is

the number when this IMP

is as the client.

To make the

communication between

IMP as client and other

programs valid, the number

of connected server should

be the value of the client.




noLimitPort

Whether it supports

WINNTTCP to connect

non-5000 port.

1 – support (peermodule

configured of the client is

valid all the time. To make it

ordinary connection,

peermodule must be 0).

The default is 0 (to make it

internal connection, the port

No. should be 5000).

[server*]

It should be configured

when IMP communicates

with other programs as

server.

-

mainpno It is the binding thread. For example, 304


host. The default is 0.

Port It is the port No. The default is 5001.

socketnum It is the maximum

connection number allowed.

Each socketnum

corresponds to one thread

No.

isWinnttcp

Whether WINNTTCP

connects to service terminal

(It is valid when noLimitPort

is 1 and is not valid when

port No. is 5000.)

1 – yes, 0 (default) – no.

[client*]

It should be configured

when IMP communicates

with other programs as

client. IMP is as client only

when it connects

SMP&SCP service

processing server.

-

mainpno It is the binding thread. For example, 308


host. The default is 0.

peeripaddress It is the IP address of

peer end.

For

example,10.40.90.106

Port

When the port No. of peer

end is 5000, the fixed peer

end is IN system.


peermodule

It is the module No. or

node No., and can be valid

when peer end is IN

system.

For example, 133




peerpost

It is the office ID of the

peer end and can be valid

when peer end is IN

system.

For example, 16

socketnum It is the connection

number. For example, 1

longconn Whether it is long

connection. 1 – long connection.

commpno It is the assigned

communication thread.

It ranges from 101~254,

and each socketnum

corresponds to one thread

No.

2.3.3 Configuring module.ini File

Purpose

To configure the start process of the application program, which decides the

service to be started

Background

IMP platform decides which programs are started together with it according to

module.ini.

Prerequisites

The platform installation script has been executed successfully.


The following is the configuration procedure of module.ini file.

1. Log on as the user zxin10.



3. Open the configuration file module.ini.

$vi module.ini

4. Edit the contents of module.ini as shown below. The item in black must

be modified. For the meaning of each process, please refer to Table

2.3-3.



[general]

ipcmode=0

ctimode=0

isenglish=0

isimpmode=1

modulecount=4

iszxinitexit=0

zxshmem=1

zxshsize=100

zxshhead=0x40000000

chkshmrate=90

[module1]

startscript=impcomm

[module2]

startscript=R01MML

RestartProcessOnly=1

[module3]

startscript=impservice


[module4]

startscript=impassist


Please modify each parameter of module.ini file according to the

requirement of networking on site.

5. After the file is edited, close module.ini file by executing the following

command.

: wq!

Description of Configuration Items

Configuration of [GENERAL] section in the module.ini file is as follows.

Table 2.3-3 Configuration Items of module.ini File

Item Parameter Parameter Meaning Requirement

General ctimode Whether it is CTI

mode.

It is not used any

longer.

general ipcmode ZXOS

communication mode

When it is 1, the office

ID needs to be judged;

when it is 0, only the node

No. and PNO need to be

judged. The default is 0.

General isenglish Whether it is the 1 represents English




English version. version, 0 Chinese

version. The default is 0.

general modulecount Application number

It determines the

number of module

segments. The default is

0.

general isimpmode Whether Zxinos is

IMP mode.

When xinos is used as

IMP support, this item

must be configured to be

1. the default value is 0,

i.e., non-IMP support

mode.

general chkinterval

Time interval from

the exception of

monitoring application

program to restart, unit:

second; and the default

value is 10.

It is mainly used for

some OSs. When the

application is writing core,

the process kill would

cause the incompletion of

the file core.

general zxshmem

Whether the

configuration uses the

shared memory.

When it is 0, it means

not using the shared

memory.

When it is 1, it means

using the shared memory.

When zxinos operates

in IMP mode, this item

must be configured to be

1.

general zxshsize

The size of the

shared memory and its

unit is M.

When zxinos operates

in IMP mode, this item

must be configured and

its configuration value

must be not less than

100.

general zxshhead

It is to configure the

head address of the

shared memory and its

default value is

0x40000000.

In Windows2000, the

head address of the

shared memory starts

from 0x4000000. In

Windows XP, it must be

modified to be

0x30000000. In

Unix/Linux, it is decided

by zxinit and it is written

into configuration file.




Other processes read out

the head address from

this configuration file.

general chkshmrate The used threshold

of the shared memory.

When the used shared

memory is exceeding the

threshold, zxinit exits. The

platform is restarted by

zxmoni.

module startscript The command line

for starting the process

The name of process

started actually, for

example, the R01MML

process is started, so the

value is R01MML.

module RestartProcessO

nly

When the process is

abnormal, it decodes

whether to restart the

single process.

0/null means to restart

the whole system.

1 means to restart the

single process.

Note: when the

parameter of the process

is assigned to be 1, if the

process is abnormal, the

system only restarts this

process and it does not

affect other processes.

2.4 Running IMP Configuration Script

Prerequisites

The configuration of IMP platform has been completed.

Background

The configuration for IMP to run the software contains the following contents:

1. Add default task.

2. Add file directory link.

3. Set the environment variables.

4. Encrypt the configuration file


The following is the configuration procedure of IMP programs.



Log on to the IMP active node as the user root to execute the IMP configuration

script.

# cd /home/setup

# ./setup.post

2.5 Starting IMP Platform

Purpose

To start IMP main program after installing and configuring IMP platform software

and application software

Prerequisites

Before the operation, please confirm:

The platform installation script has been executed successfully.

Each configuration file has been configured successfully.

The platform configuration script has been executed successfully.


The following is the startup procedure of IMP software.

1. Log in the IMP master node as user zxin10.

2. Start the IMP software.

$zxstart

3. Check the started processes.

$zxstat

Result

The number of started processes should be the same as that configured

in module.ini. The example is as follows.

zxin10@IMP1_1:~/etc> zxstat

zxin10 17702 1 0 04:50 ? 00:00:00 zxinit

zxin10 17872 1 1 04:50 ? 00:00:00 impcomm

root 17890 1 0 04:50 ? 00:00:00 R01MML

zxin10 17895 1 0 04:50 ? 00:00:00 impservice



zxin10 17900 1 0 04:50 ? 00:00:00 impassist

zxstat OK!

Sun Feb 21 04:51:33 PST 2010

2.6 Ending IMP Platform

Purpose

To test whether the platform can be ended normally

Prerequisites

SACP IMP platform works normally.


The following is the operation procedure to end the IMP software.

1. Log in to the server system as the user zxin10.

2. End the IMP software.

$zxstop


$zxstat

Result

Check the started processes and confirm that all the applications have been

ended.

2.7 Restarting IMP Platform

Purpose

To restart IMP program to make the modification take effect

Prerequisites

IMP platform works normally.


The following is the operation procedure to end the IMP software.

1. Log in to the server system as the user zxin10.

2. End the IMP software.



$zxstop;zxstart


$zxstat

Result

The number of started processes should be the same as that configured in

module.ini.

2.8 Checking IMP Log

Background

IMP platform and other interface programs will print log of each operation. The

history running state of IMP platform and interface programs can be known

through checking the corresponding logs of IMP platform.

The path of the log file is /home/zxin10/log.

Prerequisites

IMP platform has been started.


1. Log on as the user zxin10 to enter the log path.

$cd /home/zxin10/log

$tail –f imptrace.dat

2. If there is no obvious error reported in the output, then the platform runs

normally.

References

1. Description of imptrace.dat:

The imptrace.dat file records the operation history of imp.exe, including

the start of imp.exe, error report and the time for each operation.

When imp.exe is started, check the log to see whether the program has

been started normally. When the log shows the following:

!!!IMP start!!!

It means that the program has been started normally; otherwise, there

would be relevant exception prompt.

If imp.exe has started relevant FTP thread, it will be also recorded in the

log. If the FTP thread with the thread No. 400 has been started (the



range of the FTP thread No. of IMP is 400~429), the log will show the

following:

ftpap400 : start

2. Description of imptrace_*.dat

The imptrace_*.dat file has recorded detailed information including

interface service operation and message interaction of each specific

service in IMP.



3 Installation of IMP Slave Node Software

3.1 Overview

This chapter mainly presents the installation of IMP platform slave node.

Section 3.2 presets the installation method of the slave node IMP platform,

which is mainly copy the relevant files of the installed master node to the slave.

Sections 3.3 and 3.4 introduces the debugging after installation.

3.2 Installation of IMP Slave Node

Background

After the installation of IMP software on the master node, the installation and

configuration on the slave node only requires synchronizing the directory

/home/zxin10/etc.

Prerequisites

1. The installation of IMP slave node OS has been completed.

2. Installation and configuration of master node have been completed.

3. IMP platform of master node has been ended.

Procedure

1. Log on to the slave node as the user root and execute the following

commands.

# mkdir /home/setup

# chmod 777 /home/setup

2. Upload the version file imp_linux.Z via FTP in binary mode to the

directory /home/setup of IMP slave node as the user root.

3. Execute the following commands to decompress the software package.

# cd /home/setup

# gzip –d imp_linux.Z

# tar xvf imp_linux

4. Execute the following command in the directory /home/setup.

# ./setup os=linux db= none lang=gbk cluster dev=imp



5. Log on to the master node as the user zxin10 and enter the directory

/home/zxin10/etc.


6. Compress the above-mentioned directory.

$tar cvf etc.tar *

Copy etc.tar of the master node to the directory /home/zxin10/etc of the

slave node.

$scp etc.tar IMP1_2:/home/zxin10/etc

8. Log on to the slave node as the user zxin10 and enter the directory

/home/zxin10/etc.


9. Delete all the initial configuration files.

$ rm *.ini

10. Decompress the tar file.

$tar xvf etc.tar

11. Switch to the user root

$su – root

Input the password as prompted.

#cd /home/setup

12. Execute the configuration script setup.post.

#./setup.post

Note:

Path of each directory of the slave node should be the same as that of the

master node. Especially note the path of the log, which is defaulted as the

directory /home/zxin10/log. If modified, the one of the master/slave should be

modified synchronously.

3.3 Starting IMP Platform

Purpose

To start IMP main program to test the running of each interface



Prerequisites

The installation of the slave node has been completed.


The following is the startup procedure of IMP software.

1. Log in the IMP slave node as user zxin10.

2. Start the IMP software.

$zxstart


$zxstat

Result

The number of started processes should be the same as that configured in

module.ini.

3.4 Checking IMP Log

Purpose

To check whether the slave node of IMP platform runs normally

Prerequisites

The slave node IMP platform has been enabled.


1. Log on as the user zxin10 to enter the log path.

$cd /home/zxin10/log

$tail –f imptrace.dat

2. If there is no obvious error reported in the output, then the platform runs

normally.



4 Installation of Cluster System Software

4.1 Overview

Fundamental Knowledge

To configure NewStartHA cluster software, you firstly need to confirm that IMP

software of the current node has been installed and configured normally;

otherwise, there would be unpredictable error during the process of configure or

the configuration of the cluster software cannot be completed normally.

Procedure

The configuration procedure of NewStartHA is as follows.

1. Make preparations before configuring New StartHA.

2. Configure NewStartHA cluster software.

Contents introduced in this chapter are as follows:

Operation Contents Page

Section 4.2 Preparation before configuring New StartHA. 34

Section 4.3 Configuring NewStartHA Service 35

Section 4.4 Check on Cluster Status 49

Section 4.5 Cluster Switchover Test 52

4.2 Preparation before Configuring NewStartHA

1. Start ssh service on each node of the cluster to ensure that each node

can visit one another. ssh is the connection mode as the heartbeat link

between two nodes. Take SLES9 as an example.

#service sshd start

2. All the installation requires the right of the user root and the shell used

by the user root must be bash.

3. Set the host name of OS according to the system plan and check the

following file:

#vi /etc/HOSTNAME

4. Configure the IP address for each NIC and the file /etc/hosts. Note that

the node name must be the same as the result of uname –n. Add

manually the IP addresses of two nodes (corresponding to the IP



address of one heartbeat) and the corresponding node name to the file

/etc/hosts. Keep the file /etc/hosts on the two nodes the same.

Make sure that IP address of the master/slave node, heartbeat address,

floating IP address have been all configured. For the detailed information,

please refer to Table 4.2-1. The configuration of the master node and the

slave node should be the same.

Table 4.2-1 IP Address Plan for the Cluster System

NIC IP Address Host Name/Server

Alias Description

bond0 10.131.33.158 IMP1_1

Configure the IP

address on the NIC

bond0, i. e., master node

to be 10.131.33.158.

bond0 10.131.33.159 IMP1_2

Configure the IP

address on the NIC

bond0, i. e., slave node to

be 10.131.33.158.

Eth2 192.168.12.4 hbserver1 Heartbeat IP address

of the master node

Eth2 192.168.12.5 hbserver2 Heartbeat IP address

of the slave node

10.131.33.160 IMP1

The floating IP address

is configure to be

10.131.33.160.

4.3 Configuring NewStartHA Service

1. Log on to the master node as the user root and execute # cli to enter into

the command line window.

2. Description of cli (command line window) operation style:

The configuration tool cli of NewStartHA is the command line window. It

can be used for the operations of configuration and application.

The following is the prompt when using cli.

(1) When inputting a property value and if the property owns the old value or

a default value, press the Enter key directly to keep the old value or

accept the default value.

(2) Tab key can also be used to complement the input of the command line

automatically just like bash shell.

(3) cli would check the validity of the property value input (of the local node



or remote node). If there is an error checked out, the error message will

be output and it will prompt to input again.

(4) Click the above arrow button to show the command used before.

(5) Use help <cluster command> to check the function of the command.

(6) When the command cluster-stat is run, press Ctrl+C to return to cli.

Otherwise, the press of Ctrl+C would exist cli.

(7) Double click Tab button or run help to show all the commands of the

cluster, as shown in the following:

cli:~>

check-config cluster-start quit service-modify

check-script cluster-stat service-add service-show

clear-fault cluster-stop service-delete service-start

cluster-init exit service-disable service-stop

cluster-modify heartbeat-add service-enable show-status

cluster-restart heartbeat-delete service-init smartraid-init

cluster-show help service-migrate ssh-config

4.3.1 Initialization Configuration

Purpose

After installing HA, execute the command cli on one node. If it is used for the

first time, the command prompt that appears is shown as follows.

clusternode1:~/h # cli

NewStartHA High Available System. Version 2.x, release xxxx.

Copyright 2006 Guangdong NewStart Technology Service Ltd.

Can not find cluster configuration file.

Please run cluster-init to initialize cluster configuration.

Can not fine services configuration file.

Please run service-init to initialize services configuration.

Command abstract:

No. Command Function Description

1 cluster-init Initialization configuration of the cluster.

Format: cluster-init.

2 service-init Initialization configuration of the service.

Format: service-init.

Contents

1. cluster-init



Generally, this command is only used in the cluster initialization

configuration. Once the initialization configuration is completed, the

subscriber should not execute the command; otherwise the original

configuration would be lost. However, there is one exception. If the

configuration files of the nodes are different (maybe caused by

man-made modification of the configuration file), cli would prompt the

subscriber to execute the command.

In the following configuration example, heartbeat uses two crossed

straight-through cables and a serial port line. Actually, two crossed

straight-through cables and one crossed straight-through cable can also

be used.

Note:

The configuration file is in Linux, that is, /etc/ha.d/ha.cf.



cli:~>cluster-init

======================================

Cluster Initialization Utility

======================================

Version: 2.1 Built: Mon Dec 11 21:45:37 2006

This utility sets up the initialization information of a 2-node cluster.

It prompts you for the following information:

- Hostname

- Information about the heartbeat channels

- How long between heartbeat

- How long to declare heartbeat fails

WARNING: cluster-init will break the origin configuration file of the cluster.

Input node name(only need to input remote host name):clusternode2 Input the host

name of another node.

Please wait for a moment, check if the host is alive.

Maybe need to input password of root on the host.

ssh test host clusternode2 ok.

Cluster member set to: clusternode2

Input log file[/var/log/ha-log]: The saved path of the log file, press the Enter key.

running mode:

0) normal

1) debug: normal mode does not print the debugging information.

/var/log/ha-log saves ordinary information of the user. Debug mode means to print the

debugging information in /var/log/ha-debug. The log information of one month is defaulted

to be saved. Log rotation is enabled through logrotate. The ordinary information of the user

only occupies little space of the disk. If debugging information output is opened, the

maximum space of the log of a month is within 1G.. Please note to reserve enough space

when installing. Select a running mode [0, 1]: 0—select the normal mode generally. When

to record the detailed information of HA operation, select debug mode mainly because it is

convenient to check the detail problems of HA operation. How long between heartbeats(in

seconds)[1]: interval of heartbeat, unit: second. To use the default value is to press of

Enter key.

How long to declare heartbeat fails(in seconds)[15]: How long there is no heartbeat, i.e.,

confirm the heartbeat connection failed, unit: second. To use the default value is to press

of Enter key(do not reduce the value).

Input multicast heartbeat channel[eth0 225.0.0.1]:eth2 225.0.0.1 Input the NIC device

name and multi-cast address of the heartbeat connection.



Another multicast heartbeat channel? (yes/no)[yes]:yes Whether extra NIC

heartbeat connections are needed.

Input multicast heartbeat channel[eth0 225.0.0.1]:eth3 225.0.0.1 Input the NIC device

name and multi-cast address of the heartbeat connection.

Do you want to add a serial heartbeat channel? (yes/no)[yes]: Whether to add serial port

heartbeat connection. If there is connection serial lines between the two nodes, select Yes.

Input serial heartbeat channel[/dev/ttyS0]: The default is the path of serial port.

Another serial heartbeat channel? (yes/no)[yes]:no Whether extra serial port heartbeat

connections are needed.

Please run service-init to initialize you services.

And run cluster-start to start the HA system.

cli:~>

2. service-init

The indication of this command is as follows.

Note:

The configuration file is in Linux, that is, /etc/ha.d/haservices.xml.

cli:~>service-init

======================================

Service Initialization Utility

======================================

This utility sets up the initialization information of the service in the HA system.

It prompts you for the following information:

- Service information

- Application resource information

- Public net work interface information

- Floating IP address information.

- Block Disk information

- Mount information

- Raw Disk information

Input service name: cluster Input the service name.

Is it enabled?(yes/no)[yes]: yes Whether this service is managed by the cluster.

Input preferred node: When pressing the Enter key, it means not to assign the privileged

node. If the privileged node needs to be assigned, when the privileged node enables HA

or the NIC fault of the privileged node is recovered, this service would automatically

migrate to the privileged node to operate.



Input start time out[30]: Input 300 to enable the time of time-out service, unit: second.

Input stop time out[30]: Disable the time of time-out service, unit: second, Enter key

Input check inter value[30]: 5 Interval of monitoring service status, unit: second.

Input check time out[30]: Define the time of a time-out service check. If it is timed out, it

means the check failed, unit: second.

Input max error count[1]: Define the maximum times of continuous error of service

check . If it exceeded the number, it means the service check failed. Select service 1-9 and

press the Enter key here.

Restart after check result is failed?(yes/no)[no]: Check whether the service restarts in

the local after ending, and pres the Enter key here.

====== Application ======

Input name of application[cluster_app]: service script name, pres the Enter key

Input script of application[/etc/init.d/cluster]: /home/zxin10/newstartha/zxinclc Input the

service script path.

Add another application? (yes/no)[no]: no Whether to add other scripts.

====== PubNIC ======

Input PubNIC name[cluster_net_card]: Input the public NIC name, pres the Enter key.

====== member ======

Node of the cluster:

0) clusternode1

1) clusternode2

Select a node: [0, 1]:0 It needs to configure the network of the working connections for

the two nodes separately. It should be noted that each node can only be configured once.

Input device[eth0]:bond0 Select NIC of the working connection IP address used by the

node.

Note: Any part of the binding NIC cannot be used separately to other working

connections (PubNIC).

Add another member? (yes/no)[yes]: Pres the Enter key.


0) clusternode1

1) clusternode2

Select a node: [0, 1]: 1 Network configuration of the working connection for the other

node.

Input device[eth0]:bond0 This node is used for the NIC f working connection IP

address.

Add another member? (yes/no)[yes]:no It is not added here because the

configurations of NIC for the two nodes have been completed.

Add another public? (yes/no)[no]: Whether to set other working connections for the

service. To press the Enter key is to select no.

====== IP ======

Input IP name[cluster_ip]: Input the floating IP name, and press the Enter key.



Input IP address: 192.168.1.133 Input the floating IP address and it should be in the

same network segment with the NIC IP address.

Input netmask[255.255.255.0]: Input subnet mask.

PubNIC of service:

0) cluster_net_card

Select a PubNIC: [0, 0]:0 Select the public NIC name in the same service. The floating

IP and public NIC IP should be in the same network segment. The service is provided to

the outside through the host network port assigned by the public NIC.

Add another IP? (yes/no)[no]:no Whether to add other IP.

Do you want to add a block disk? (yes/no)[no]: yes Whether to add block device.

====== BlockDisk ======

Input block disk name[cluster_disk]: Input the name of disk mounted, and press the

Enter key.

====== member ======


0) clusternode1

1) clusternode2

Select a node: [0, 1]:0

Input block disk device[/dev/hda1]:/dev/sdb1

Add another member? (yes/no)[yes]:


0) clusternode1

1) clusternode2

Select a node: [0, 1]:1

Input block disk device[/dev/hda1]:/dev/sdb1

Add another member? (yes/no)[yes]:no

Add another block disk? (yes/no)[no]: Press the Enter key.

Do you want to add a mount point? (yes/no)[yes]: Press the Enter key.

====== Mount ======

Input mount name[cluster_mount]: Name of mount point, press the Enter key.

Input mount point: /zxindata mount point of device and there must be the same mount

point between the two nodes.

Input type of file system[ext3]: type of file system of the mount directory

Input user[root]: sybase operation user of the mount directory.

Input group[root]: sybase group of the operator

Input mode[755]: 775 the right of the mount directory.

Input option[rw,sync]: operation right of the shared resource by the mount directory, it

is read/write and synchoronization on Linux.

BlockDisk of service:

1) cluster_disk

Select a BlockDisk: [0, 1]:1 the name of the shared disk resource mounted.



Add another block disk? (yes/no)[no]: Press the Enter key.

Add another service? (yes/no)[no]: Press the Enter key.

Please run cluster-start to start the HA system,

or run cluster-restart to restart the HA system.

cli:~>cluster-restart

[clusternode1]Stopping High-Availability services:

[clusternode2]Stopping High-Availability services:

done

..done

[clusternode1]Starting High-Availability services:

done

[clusternode2]Starting High-Availability services:

..done

4.3.2 Method of Modifying Configuration

The initial configuration can be modified and some of the modification

commands is as follows:


1 heartbeat-add Add heartbeat connection. Format:

heartbeat-add.

2 heartbeat-delete Delete heartbeat connection. Format:

heart-delete.

3 Cluster-modify Modify the initialization configuration of the

heartbeat connection. Format: cluster-modify.

4 Service-add

Add service to the configuration file. Format:

service-add. Add service configuration to the

configuration file /etc/ha.d/cli/haservices.xml as

prompted after operating. After enabling the

cluster via cli, copy the file to the directory

/etc/ha.d.

5 Service-modify Modify the configuration information of a

service. Format: service-modify.

6 Service-delete Delete the service configuration from the

configuration file. Format: service-delete.



Note:

After modifying the parameter configuration and heartbeat configuration, cli

must be used to restart the cluster. After adding, deleting, and modifying the

service, the cluster needs to be restart to be valid. If the configuration files of the

two nodes are not synchronous, cli would prompt the failure of the

synchronizing the configuration files when modifying the configuration files.

Then, recover the file before modification and check whether the heartbeat

channel and the two nodes work normally.

4.3.3 Check on Configuration

After configuration, use the following commands to check whether the

configurations are correct.


1 service-show Show the configuration information of the assigned

service. Format: service-show.

2 check-script

Check the correctness of the self-written script via

executing the script and checking the return value.

Format: check-script. Before running, use cluster-stop

to end the cluster. The command can automatically

enable the script the service resource of the node. The

notice items are as follows.

3 check-config Check the correctness of the service configuration.

Format: check-config.

Note:

Parameters in ―<>‖ are required.

1. service-show

Check the monitoring service configuration information command

service-show, and the example of command operation is as follows:



cli:~>service-show

Current service:

0) name: cluster

1) cancel

Select a(n) service [0,2]:1

service

------

name: cluster

enabled: yes

preferrednode: clusternode1

starttimeout: 30

stoptimeout: 30

checkinterval: 30

checktimeout: 30

maxerrcount: 1

restartaftercheckfail: no

Application

------

script: /etc/init.d/named

PubNIC

------

name: cluster_net_card

member

------

nodename: clusternode1

device: bond0

member

------

nodename: clusternode2

device: bond0

IP

------

name: cluster_ip

ipaddr: 172.16.100.29

netmask: 255.255.255.0

PubNICResName: cluster_net_card

Show other service? (yes/no)[no]: Press the Enter key.



2. check-script

check-script is used to check whether the application script compiled by

the user meets the demand of NewStartHA. This command complete 12

tests of the script compatibility for a time (if the script is totally

compatible).

There are various resources in a service. The application program to be

tested is started at last and ended at first. It depends on such resources

as IP, file system. In order to check the application program resource, its

in depended resources must be started first. After all the resources of the

service are successfully started, the service is truly started successfully.

After all the resources of the service is ended, the service is ended

successfully.

Note:

Before using the command, please end the cluster via cluster-stop first. The

command is executed on one node of the same cluster at the same time. Never

execute check-scriptto check the script on the cli window at the same time on

the two nodes of the same cluster. Otherwise, it will lead to read and write the

data on the shared storage at the same time, which will cause the damage and

missing of the data.

Auto check procedure of check-script:

Preparation:

Start the dependant resources of the application program.

(1) Start the application program.

Operation result:

pass: the start of the application program is successful and then go on

with the next test.

failed: the start of the application program is failed and then check the

starting function parts of the script. The execution of the command is

completed.

(2) Check the application program status.

Operation result:

pass: the test of the application program status is successful and then go

on with the next test.



failed: check on the application program status failed. The reason of the

failure may be that step 1 has started the application program

successfully, and also may be the test script does not comply with the

specification. Please check the starting function part and test of the script.

The execution of the command is completed.

(3) Start the application program again.

Operation result:

pass: the re-start of the application program is successful and then go on

with the next test.

failed: re-start of the application program failed. The reason for the failure

is that after the application is started, use the script start program and the

return is errored. The start function part of the script does not comply

with the specification, and please check the start function part of the

script. The execution of the command is completed.


Operation result:

pass: the test of the application program status is successful and then go

on with the next test.

failed: check on the application program status failed. The reason for the

failure is that although the return of the start application program in step

3 is successful, it damages the original status of the program. Please

check the starting function part and test of the script. The execution of

the command is completed.

(5) End the application program.

Operation result:

pass: the ending of the application program is successful and then go on

with the next test.

failed: the ending of the application program failed. Please check the

ending function part of the script. The execution of the command is

completed.


Operation result:

pass: the test of the application program status is failed, the test passes

and then go on with the next test.



failed: the test of the application program status is successful (the

application program still runs). The reason for the failure of the test may

be that step 5 does not truly end the application program, and also may

be the test script does not comply with the specification. Please check

the starting function part and test of the script. The execution of the

command is completed.

(7) End the application program.

Operation result:

pass: the ending of the application program is successful and then go on

with the next test.

failed: the ending of the application program failed. The reason for the

failure is that after the application is ended, use the script ending

program and the return is errored. The ending function part of the script

does not comply with the specification, and please check the ending

function part of the script. The execution of the command is completed.


Operation result:

pass: the test of the application program status is failed and then go on

with the next test.

failed: check on the application program status successful. The reason

for the failure is that although the return of the ending application

program in step 7 is successful, it damages the original status of the

program. Please check Please check the ending function part and test of

the script. The execution of the command is completed.

(9) End the application program forcibly

Operation result:

pass: the forced ending of the application program is successful and then

go on with the next test.

failed: the forced ending of the application program failed. Please check

the forced ending function part of the script. The execution of the

command is completed.

(10) Test the program status.

Operation result:

pass: the test of the program status is failed and then go on with the next



test.

failed: check on the program status is successful. The reason for the

failure of the test may be that step 9 does not truly end the application

program, and also may be the test script does not comply with the

specification. Please check the forced starting function part and test of

the script. The execution of the command is completed.

(11) End the application program forcibly.

Operation result:

pass: the forced ending of the application program is successful and then

go on with the next test.

failed: the forced ending of the application program failed. The reason for

the failure is that after the application is ended, use the script ending

program and the return is errored. The ending function part of the script

does not comply with the specification, and please check the ending

function part of the script. The execution of the command is completed.

(12) Test the program status.

Operation result:

pass: test of the program status is failed and the test is ended.

failed: check on the program status is successful. The reason for the

failure is that although the return of the forced ending application

program in step 11 is successful, it damages the original status of the

program. Please check the forced ending function part and test of the

script. The execution of the command is completed.

3. check-config

Check whether the service configuration is correct. The example of

normal operation for the command is shown in the following.

cli:~>check-config

Configuration file checked ok.

When checking whether the service configuration is incorrect, the example is as

follows.



cli:~>check-config

======Check <PubNIC> node error.

IP: The ipaddr 172.16.100.222 and the IP address of the

network interface bond0 are not in the same net.







======Check <IP> node error.

Configuration file checked error

4.4 Check on Cluster Status

Purpose

To check the cluster status of HA

Contents

It mainly contains the following contents:

Table 4.4-1 Check in NewStartHA Cluster Contents

Contents Page

4.4.1Section 4.4.1 Check Whether Floating IP Address Is Activated 49

Section 4.4.2 Check on IMP Software Procedure 50

Section 4.4.3 Check on Starting Log 50

Section 4.4.4 Check on Cluster HA Starting Status 51

4.4.1 Check Whether Floating IP Address Is Activated

Purpose

To configure NewStartHA cluster software, ensure the NewStartHA cluster

software can be switched over normally between the master node and the slave

node. Confirm the floating IP address has been correctly configured to ensure

the normal switchover of the NewStartHA cluster software.

Procedure

The following is the operation procedure to check whether the floating IP

address is activated.

1. Log on to the master node as the user root.

2. Execute the following command.



# ip addr

Result

It is shown that the floating IP address has been bound to bond0.

4.4.2 Check on IMP Software Procedure

Purpose

To check whether IMP software procedure is normal

Procedure

The following is the operation procedure to check the IMP software.


2. #su – zxin10

3. $ zxstat

Result

The following information should be displayed.

zxin10@linux:~> zxtool -p

zxin10 319734 1 0 December 2 - 1:35 zxinit

zxin10 926116 1 0 December 2 - 0:27 impcomm

appsvc 716808 1 0 December 5 - 0:00 R01MML

zxin10 807422 1 0 December 2 - 12:41 sdfpro

zxin10 1044918 1 0 December 2 - 1:58 impassist

zxin10 667902 1 0 December 2 - 2:44 impservice

zxin10 999790 1 0 December 2 - 0:53 almcol

4.4.3 Check on Starting Log

Purpose

The cluster software records the starting information in detail during the starting

process. Though checking the starting log, it can be clearly seen that what

errors exist in the starting process of the cluster. This sub-section presents how

to check the starting log. As to the checking method of the log contents, it will

not be introduced in this manual.

Procedure

The following is the operation procedure to check the starting log.


2. #su – zxin10



3. $vi /home/zxin10/log/impcom.log

Result

There should be IMP starting information in this file.

4.4.4 Check on Cluster HA Starting Status

Purpose

To check whether the status of the cluster HA is normal

Preparations

Before the operation, please confirm:

Login to any node of cluster as the user root and execute

# cli

cli:~>cluster-stat

Procedure

If the returned result is as follows: the host of the two nodes are in the state of

UP and the working connections and heartbeat connections of the two nodes

are in the state of ONLINE, and the service is running on one node, it is normal.

cli:~>cluster-stat

Member status:

member status

clusternode1 UP

clusternode2 UP

Work link status:

nodename PubNIC status

clusternode1 bond0 ONLINE


Heartbeat link status:

clusternode1 clusternode2 type status

eth2 eth2 network ONLINE


/dev/ttyS0 /dev/ttyS0 serial ONLINE

Service status:

Name clusternode1 clusternode2 Enable

cluster running stopped YES



4.5 Cluster Switchover Test

Purpose

After the configuration of NewStartHA in completed, the last procedure is

needed: switchover test of the cluster. Through the test, you can check whether

the whole NewStartHA cluster software are installed and configured

successfully.

Simulate application faults or stop the CLUSTER service to check whether the

cluster can be switch over and check the status after the switchover. The

following is the switchover test performed in the normal mode, based on which

many other switchover tests can be performed. For example, pulling out the

network cable of the master node outside service, ending or restarting the

master node can also perform the switchover test.

Procedure

The following is the procedure of the cluster switchover test:

1. End the cluster service on the master node.

Switchover due to application fault

#superstop

CLUSTER would detect the application fault and then cluster switchover

is performed.

Switchover due to shutdown of CLUSTER service

# cli

cli:~> cluster-stop

The cluster would be switched over immediately and this node would not

be closed. If it needs to switch over from the slave to the master, the

CLUSTER service should be enabled manually again. The command to

enable the CLUSTER service is:

# cli

cli:~> cluster-start

2. Log on to the slave node to check the cluster status.

# cli

cli:~>cluster-stat

If the following is shown, the service has been switched over to the slave

successfully.



cli:~>cluster-stat

Member status:

member status

clusternode1 UP

clusternode2 UP

Work link status:

nodename PubNIC status



Heartbeat link status:

clusternode1 clusternode2 type status



/dev/ttyS0 /dev/ttyS0 serial ONLINE

Service status:

Name clusternode1 clusternode2 Enable

cluster stopped running YES

3. Check whether IMP software has been run in the slave. For the

procedure, please refer to Table 4.5-1.

Table 4.5-1 Check on Running Condition of the Cluster on the Slave

Contents Page

Section 4.4.1 Check Whether Floating IP Address Is Activated 49

Section 4.4.2 Check on IMP Software Procedure 50

4. Execute the following command on the master node to switch over the

application service of the cluster back to the master node.

# /etc/init.d/hadaemons stop

# cli

cli:~>cluster-start

cli:~>service-migrate



5 SACP IMP System Debugging

5.1 Overview

After completing the installation of IMP dual computer cluster system and IMP

platform program, the integral test of IMP is needed. This chapter presents

common debugging method of IMP system.

5.2 Debugging Procedure Description

5.2.1 Flow Chart

Begin

IMP Platform Start Test

IMP Platform Restart Test

End

IMP Platform Stop Test

IMP Cluster Switch test

IMP Platform Log Check

5.2.2 Procedure Description

Purpose

To debug the IMP system

Prerequisites

1. The installation and configuration of the master node and the slave node

of the IMP platform have been completed.

2. The installation and configuration of cluster have been completed.

Personnel



Debugging SACP devices engineers on site


1. Starting test of the IMP platform. For the details, please refer to Section

2.5.

2. Ending test of the IMP platform. For the details, please refer to Section

2.6.

3. Restarting test of the IMP platform. For the details, please refer to the

Section 2.7.

4. Log checking of the IMP platform. For the details, please refer to Section

2.8.

5. Cluster switchover test. For the details, please refer to Section 4.5.

zxin10 sacp imp platform installation guide

Documents

installation of imp

configuration of imp

ending imp platform

restarting imp platform

imp configuration script

checking imp log

permission of zte page

installation environment