EXPRESSCLUSTER X SingleServerSafe 3.3 for

EXPRESSCLUSTER® X SingleServerSafe
3.3 for Windows
Operation Guide
10/02/2017
6th Edition
Revision History
Edition
1st
2nd
3rd
4th
5th
6th
Revised Date
02/09/2015
04/20/2015
01/29/2016
10/03/2016
04/10/2017
10/02/2017
Description
New manual
Corresponds to the internal version 11.31.
Corresponds to the internal version 11.32.
Corresponds to the internal version 11.33.
Corresponds to the internal version 11.34.
Corresponds to the internal version 11.35.
© Copyright NEC Corporation 2015. All rights reserved.
Disclaimer
Information in this document is subject to change without notice.
NEC Corporation is not liable for technical or editorial errors or omissions in the information in this document.
You are completely liable for all risks associated with installing or using the product as described in this
manual to obtain expected results and the effects of such usage.
The information in this document is copyrighted by NEC Corporation. No part of this document may be
reproduced or transmitted in any form by any means, electronic or mechanical, for any purpose, without the
express written permission of NEC Corporation.
Trademark Information
EXPRESSCLUSTER® is a registered trademark of NEC Corporation.
Intel, Pentium and Xeon are registered trademarks or trademarks of Intel Corporation.
Microsoft and Windows are registered trademarks of Microsoft Corporation in the United States and other
countries.
Oracle, Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or
its affiliates.
WebOTX is a registered trademark of NEC Corporation.
Android is a trademark or registered trademark of Google, Inc.
F5, F5 Networks, BIG-IP, and iControl are trademarks or registered trademarks of F5 Networks, Inc. in the
United States and other countries.
Other product names and slogans written in this manual are trademarks or registered trademarks of their
respective companies.
Table of Contents
Preface
.................................................................................................................... vii
Who Should Use This Guide ........................................................................................................................... vii
How This Guide Is Organized ......................................................................................................................... vii
Terms Used in This Guide .............................................................................................................................. viii
EXPRESSCLUSTER X SingleServerSafe Documentation Set ........................................................................ ix
Conventions ....................................................................................................................................................... x
Contacting NEC ................................................................................................................................................ xi
Section I
WebManager Operation Reference ............................................................... 13
Chapter 1
Functions of the WebManager .................................................................. 15
Starting the WebManager ................................................................................................................................ 16
What is the WebManager? .............................................................................................................................................. 16
Starting the WebManager ............................................................................................................................................... 17
Window of the WebManager ........................................................................................................................... 18
Main window of the WebManager window .................................................................................................................... 18
Changing the WebManager operation mode ................................................................................................................... 21
Searching for an alert by using the WebManager ........................................................................................................... 22
Collecting logs by using the WebManager ..................................................................................................................... 23
Updating the WebManager information .......................................................................................................................... 25
Changing the screen layout on the WebManager ............................................................................................................ 26
Checking the time information from the WebManager ................................................................................................... 26
Executing Integrated WebManager from the WebManager ............................................................................................ 28
Operating services on the WebManager .......................................................................................................................... 28
Confirming the license from the WebManager ............................................................................................................... 29
Checking the status of each object in the tree view of WebManager .............................................................. 30
Operations that can be executed from the WebManager ................................................................................................. 30
Checking the status by the WebManager list view .......................................................................................... 39
Displaying information by using the WebManager list view .......................................................................................... 39
Checking the whole status of the server in the WebManager list view ........................................................................... 46
Checking the status of individual server in the WebManager list view ........................................................................... 47
Checking the status of the whole monitor in the WebManager list view ........................................................................ 47
Checking alerts using the WebManager .......................................................................................................... 48
Alert view fields .............................................................................................................................................................. 48
Alert view operations ...................................................................................................................................................... 49
Manually stopping and starting the WebManager ........................................................................................... 50
When you do not want to use the WebManager .............................................................................................. 50
Setting limitations on the connection and operation of the WebManager ....................................................... 51
Types of usage limitations .............................................................................................................................................. 51
Section II
Command Reference .................................................................................... 53
Chapter 2
EXPRESSCLUSTER X SingleServerSafe command reference ............... 55
Operating the cluster from the command line .................................................................................................. 56
EXPRESSCLUSTER commands .................................................................................................................... 56
Displaying the status (clpstat command) ......................................................................................................... 58
Operating the service (clpcl command) ........................................................................................................... 61
Shutting down the server (clpstdn command) .................................................................................................. 65
Operating groups (clpgrp command) ............................................................................................................... 66
Collecting logs (clplogcc command) ............................................................................................................... 69
Collecting logs by specifying a type (-t option) .............................................................................................................. 70
Output paths of log files (-o option) ................................................................................................................................ 72
Specifying a event log type to collect (--evt option) ....................................................................................................... 72
Collecting information on emergency OS shutdown ....................................................................................................... 73
Applying and backing up configuration data (clpcfctrl command) ................................................................. 74
v
Applying configuration data (clpcfctrl --push) ................................................................................................................ 74
Backing up configuration data (clpcfctrl --pull) .............................................................................................................. 78
Adjusting time-out temporarily (clptoratio command) .....................................................................................80
Modifying the log level and size (clplogcf command) .....................................................................................83
Registering the license (clplcnsc command) ..................................................................................................91
Outputting messages (clplogcmd command) ....................................................................................................93
Controlling monitor resources (clpmonctrl command).....................................................................................95
Controlling group resources (clprsc command)................................................................................................ 99
Controlling CPU frequency (clpcpufreq command) .......................................................................................101
Requesting processing to cluster servers (clprexec command) ......................................................................103
Controlling reboot count (clpregctrl command) .............................................................................................106
Estimating the amount of resource usage (clpprer command) ........................................................................108
Checking the process health (clphealthchk command) ................................................................................113
Section III
Release Notes .............................................................................................. 115
Chapter 3
Notes and restrictions ............................................................................. 117
After the system is put into operation .............................................................................................................118
Restrictions during recovery operation .......................................................................................................................... 118
Executable format files and script files not described in the command reference ......................................................... 118
EXPRESSCLUSTER Disk Agent service ..................................................................................................................... 118
Issues with User Account Control (UAC) in Windows Server 2008 environment ........................................................ 119
Screen display of application resource / script resource in the Windows Server 2008 / 2012 environment .................. 120
Environment in which the network interface card (NIC) is duplicated .......................................................................... 120
EXPRESSCLUSTER service login account .................................................................................................................. 120
Monitoring the EXPRESSCLUSTER resident process ................................................................................................. 120
JVM monitor resources ................................................................................................................................................. 120
System monitor resources .............................................................................................................................................. 121
Display of the Interactive services dialog detection pop-up menu in a Windows Server 2008 / 2012 environment...... 121
WebManager ..................................................................................................................................................122
Chapter 4
Error messages ........................................................................................ 123
Messages reported by event log and alert .......................................................................................................124
Appendix
.................................................................................................................. 127
Appendix A
Index .......................................................................................................... 129
vi
Preface
Who Should Use This Guide
The Operation Guide is intended for system administrators who will operate and maintain an introduced
system. It describes how to operate EXPRESSCLUSTER X SingleServerSafe. The guide consists of three
sections: I to III.
How This Guide Is Organized
Section I
WebManager Operation Reference
Chapter 1
“Functions of the WebManager”: Describes how to use WebManager and provides related
information.
Section II
Command Reference
Chapter 2
“EXPRESSCLUSTER X SingleServerSafe command reference”: Describes the usable
commands in EXPRESSCLUSTER X SingleServerSafe.
Section III
Release Notes
Chapter 3
Chapter 4
“Notes and restrictions”: Provides information on known problems and restrictions.
“Error messages”: Lists and describes error messages you might encounter when operating
EXPRESSCLUSTER X SingleServerSafe.
Appendix
Appendix A
“Index”
vii
Terms Used in This Guide
EXPRESSCLUSTER X SingleServerSafe, which is described in this guide, uses windows and commands
common to those of the clustering software EXPRESSCLUSTER X to ensure high compatibility with
EXPRESSCLUSTER X in terms of operation and other aspects. Therefore, cluster-related terms are used in
parts of the guide.
The terms used in this guide are defined below.
Term
Explanation
Cluster, cluster system
A single server system using EXPRESSCLUSTER X SingleServerSafe
Cluster shutdown, reboot
Shutdown or reboot of a system using EXPRESSCLUSTER X
SingleServerSafe
Cluster resource
A resource used in EXPRESSCLUSTER X SingleServerSafe
Cluster object
A resource object used in EXPRESSCLUSTER X SingleServerSafe
Failover group
A group of group resources (such as applications and services) used in
EXPRESSCLUSTER X SingleServerSafe
viii
EXPRESSCLUSTER X SingleServerSafe Documentation Set
The EXPRESSCLUSTER X SingleServerSafe manuals consist of the five guides below. The title and purpose
of each guide is described below:
EXPRESSCLUSTER X SingleServerSafe Installation Guide
This guide is intended for system engineers who intend to introduce a system using EXPRESSCLUSTER X
SingleServerSafe and describes how to install EXPRESSCLUSTER X SingleServerSafe.
EXPRESSCLUSTER X SingleServerSafe Configuration Guide
This guide is intended for system engineers who intend to introduce a system using EXPRESSCLUSTER X
SingleServerSafe and system administrators who will operate and maintain the introduced system. It describes
how to set up EXPRESSCLUSTER X SingleServerSafe.
EXPRESSCLUSTER X SingleServerSafe Operation Guide
This guide is intended for system administrators who will operate and maintain an introduced system that uses
EXPRESSCLUSTER X SingleServerSafe. It describes how to operate EXPRESSCLUSTER X
SingleServerSafe.
EXPRESSCLUSTER X Integrated WebManager Administrator’s Guide
This guide is intended for system administrators who manage a cluster system using EXPRESSCLUSTER with
EXPRESSCLUSTER Integrated WebManager and for system engineers who are introducing the Integrated
WebManager. Details about items required when introducing a cluster system are described in accordance with
actual procedures.
WebManager Mobile Administrator's Guide
This guide is intended for system administrators who manage a cluster system using EXPRESSCLUSTER with
WebManager Mobile, and for system engineers who are introducing WebManager Mobile. Details on the
actual procedures required when introducing a cluster system using WebManager Mobile are described in this
guide.
ix
Conventions
In this guide, Note, Important, and Related Information are used as follows:
Note:
Used when the information given is important, but not related to the data loss and damage to the system and
machine.
Important:
Used when the information given is necessary to avoid the data loss and damage to the system and machine.
Related Information:
Used to describe the location of the information given at the reference destination.
The following conventions are used in this guide.
Convention
Bold
Angled
bracket
within the
command
line
Monospace
(courier)
Monospace
bold
(courier)
Monospace
italic
(courier)
x
Usage
Indicates graphical objects,
such as fields, list boxes, menu
selections, buttons, labels,
icons, etc.
Indicates that the value
specified inside of the angled
bracket can be omitted.
Indicates path names,
commands, system output
(message, prompt, etc),
directory, file names, functions
and parameters.
Indicates the value that a user
actually enters from a command
line.
Indicates that users should
replace italicized part with
values that they are actually
working with.
Example
In User Name, type your name.
On the File menu, click Open Database.
clpstat –s[-h host_name]
c:\Program files\EXPRESSCLUSTER
Enter the following:
clpcl -s -a
clpstat –s [-h host_name]
Contacting NEC
For the latest product information, visit our website below:
http://www.nec.com/global/prod/expresscluster/
xi
Section I
WebManager Operation
Reference
This section provides details about the EXPRESSCLUSTER X WebManager functions. EXPRESSCLUSTER
X SingleServerSafe uses windows common to those of the clustering software EXPRESSCLUSTER X to
ensure high compatibility with EXPRESSCLUSTER X in terms of operation and other aspects. Because the
information contained herein is specific to EXPRESSCLUSTER X SingleServerSafe, see the Reference Guide
for EXPRESSCLUSTER X to obtain an overall understanding of the WebManager.
•
Chapter 1
Functions of the WebManager
13
Chapter 1
Functions of the
WebManager
This chapter describes the functions of the WebManager.
This chapter covers:
•
•
•
•
•
•
•
•
Starting the WebManager ···························································································· 16
Window of the WebManager························································································ 18
Checking the status of each object in the tree view of WebManager ·········································· 30
Checking the status by the WebManager list view ······························································· 39
Checking alerts using the WebManager ··········································································· 48
Manually stopping and starting the WebManager ································································ 50
When you do not want to use the WebManager ·································································· 50
Setting limitations on the connection and operation ····························································· 51
15
Chapter 1 Functions of the WebManager
Starting the WebManager
Some of the windows and terms used to describe the WebManager in this chapter are the same as
those for EXPRESSCLUSTER X WebManager. Therefore, cluster-related terms are used in parts
of the chapter.
Read the guide, assuming that EXPRESSCLUSTER X SingleServerSafe is in a one-node cluster.
What is the WebManager?
The WebManager is a function for setting up EXPRESSCLUSTER, monitoring its status,
starting and stopping servers and groups, and collecting operation logs through a Web browser.
The overview of the WebManager is shown in the following figures.
ExpressCluster X
SingleServerSafe
Web browser window
IP
WebManager service
Builder
Specify the IP address of
the server as the
destination.
Management PC
The Java runtime
environment must be
installed.
The WebManager service on the EXPRESSCLUSTER X SingleServerSafe Server is set up to
start up when the operating system starts up.
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
16
Starting the WebManager
Starting the WebManager
The procedure for starting the WebManager is described below.
1.
Start your Web browser.
2.
Enter the IP address and port number of the server where EXPRESSCLUSTER X
SingleServerSafe is installed in the browser address bar.
http://192.168.0.1:29003/
The port number for the WebManager specified at
installation. (Default value: 29003)
It is the IP address of the server where EXPRESSCLUSTER X SingleServerSafe is installed.
If the local server is used, localhost can be specified.
3.
The WebManager starts.
Section I WebManager Operation Reference
17
Chapter 1 Functions of the WebManager
Window of the WebManager
This chapter provides information about the WebManager window.
Note:
For the language used on the WebManager screen, see "Cluster properties Info tab".
Main window of the WebManager window
The WebManager window consists of two bars and three views.
Menu bar
Toolbar
Tree view
List view
Alert view
Menu bar
The menu bar has the five menus described below. The contents of these menus differ depending
on the config mode and operation/reference mode. The menu items displayed in the
operation/reference mode are described later in this chapter.

File menu

View menu

Service menu

Tool menu

Help menu
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
18
Window of the WebManager
Toolbar
If you click one of the seven icons on the toolbar, you can perform the same operation as when
selecting the corresponding item on the menu bar.
Icon/menu
Operation
Mode
Config
Mode
Reference
Mode
Verification
Mode
Function
Refer to
Changes the WebManager to the operation mode.
This is the same as clicking View on the menu bar and
then selecting Operation Mode.
“Changing the
WebManager
operation mode”
(on page 21)
Changes the WebManager to the config mode (online
version of the Builder). This is the same as clicking
View on the menu bar and then selecting Config
Mode.
“Changing the
WebManager
operation mode”
(on page 21)
Changes the WebManager to the reference mode.
This is the same as clicking View on the menu bar and
then selecting Reference Mode.
“Changing the
WebManager
operation mode”
(on page 21)
Changes the WebManager to the verification mode.
This is the same as clicking View on the menu bar and
then selecting Verification mode.
“Changing the
WebManager
operation mode”
(on page 21)
Searches for an alert. This is the same as clicking
Tool on the menu bar and then selecting Filter Alerts.
“Searching for an alert
by using the
WebManager”
(on page 22)
Collects logs. This is the same as clicking Tool on the
menu bar and then selecting Collecting Cluster
Logs.
“Collecting logs by
using the
WebManager”
(on page 23)
Performs reloading. This is the same as clicking Tool
on the menu bar and then selecting Reload.
“Updating the
WebManager
information”
(on page 25)
Displays options. This is the same as clicking Tool on
the menu bar and then selecting Option.
“Changing the screen
layout on the
WebManager”
(on page 26)
Displays the time information. This is the same as
clicking Tool on the menu bar and then selecting
TimeInfo
When the time information has been updated, the icon
changes accordingly. The icon reverts to its original
form when the time information dialog is displayed.
Displays Integrated WebManager. This is the same
as clicking Tool on the menu bar and then
selecting Integrated WebManager.
Checking the time
information from the
WebManager
(on page 26)
“Executing Integrated
WebManager from
the WebManager”
(on page 28)
Section I WebManager Operation Reference
19
Chapter 1 Functions of the WebManager
Tree view
The statuses of servers and group resources can be confirmed. For further information, see
“Checking the status of each object in the tree view of WebManager” on page 30.
List view
The upper part of the view provides information on the server or other resource selected in the
tree view. The lower part lists the start/stop statuses and comments of each server, group resource,
and monitor resource. If you click the Details button located on the upper right of the view,
further information will be displayed in a dialog box. For further information, see “Checking the
status by the WebManager list view” on page 39.
Alert view
The operation status of EXPRESSCLUSTER X SingleServerSafe is indicated by a message. For
further information, see “Checking alerts using the WebManager” on page 48.
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
20
Window of the WebManager
Changing the WebManager operation mode
The WebManager has the following four operation modes.

Operation mode
This mode allows the user to see the status of and operate the server.
Select Operate Mode on the View menu or click the operation mode icon ( ) on the
toolbar to switch to the operation mode. However, if you used the reference mode password
for login when starting the WebManager or connected to the WebManager from a client that
is not allowed to perform operations, it is not possible to switch to the operation mode.

Reference Mode
This mode allows the user to see the cluster status, but not to operate the server.
Select Reference Mode on the View menu or click the operation mode icon (
toolbar to switch to the reference mode.
) on the

Config Mode
This mode allows the user to set up the server and change the settings. The WebManager in
the config mode is called Builder (online version). For details about operations in the config
mode, see the EXPRESSCLUSTER X SingleServerSafe Configuration Guide.
Select Config Mode on the View menu or click the operation mode icon ( ) on the toolbar
to switch to the config mode. However, if you connected to the WebManager from a client
that is not allowed to perform operations, it is not possible switch to the config mode.

Verification Mode
This mode allows the user to generate a simulated fault in specified monitor resources.
Select Verification mode ( ) on the View menu or the toolbar to switch to the
Verification mode. However, if you connected to the WebManager from a client that is not
allowed to perform operations, it is not possible to switch to verification mode.
If you switch from the verification mode to another mode, a dialog box asks if you want to
cancel the simulated fault status of all the monitor resources. Select Yes to place all the
monitor resources in the simulated fault status back in the normal monitored status. Select
No to switch to another mode while keeping the monitor resources in the simulated fault
status.
Note: When the pop-up window is displayed for Operation Mode, Reference Mode, or
Verification Mode in the WebManager, and if switching to Config Mode is performed, the open
pop-up window closes.
The operation performed on the pop-up window continues.
Section I WebManager Operation Reference
21
Chapter 1 Functions of the WebManager
Searching for an alert by using the WebManager
You can search for an alert by using the WebManager. Searching in this method is useful to view
only a specific type alert.
Note:
For information about alert logs, see “Checking alerts using the WebManager” on page 48.
To search for an alert, click Filter Alerts on the Tool menu or click the alert search icon (
the toolbar. The window for specifying alert log search conditions is displayed.
) on
To search only the specified number of past alert logs:
1.
Select Display only the specified number of alerts.
2.
Enter the number of past alert logs to search, and then click OK. Past alert logs are
displayed as many as you have specified.
Note:
The maximum value to enter is the number specified for Max Number to Save Alert Records.
To configure Max Number to Save Alert Records, right-click the cluster icon in the Builder,
and then click Properties on the shortcut menu. In the properties dialog box, click the Alert Log
tab.
To search by specifying search conditions:
1.
Click Filtering Settings.
2.
Enter the search conditions in each field and start searching.
-
Alert Type: Select the type of alerts.
-
Module Name: Enter the module type.
Server Name: Type in the name of a server whose alerts you want to see.
-
Event ID: Type in an event ID whose alerts you want to see.
For event IDs, see Chapter 4 Error messages.
-
From, To: Select this to search by the time of the event occurrence. Enter the values in
From and To field.
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
22
Window of the WebManager
3.
Enter the number of alerts to display on one page in The number of alerts to be displayed
per page, and then click OK. Research results are displayed based on the time an alert
occurred.
4.
If the results of research are displayed on more than one page, move the page by clicking
Back, Next, and Jump buttons.
Collecting logs by using the WebManager
Clicking Collect Cluster Logs on the Tool menu or clicking the Collect Cluster Logs icon
(
) on the toolbar opens the log collection dialog box.
Check box
Select the check boxes of the servers that have the logs you want to collect.
Pattern
Select the information to be collected. Specify one of Type 1 to Type 4 as the log collection
pattern.
Type 1
Type 2
Type 3
Type 4
(1) Default collection information



-
(2) Event log




(3) Watoson log




(4) User dump


-
-
(5) Diagnosis program report


-
-
(6) Registry



-
(7) Script



-
(8) Logs of ESMPRO/AC and ESMPRO/UPSC



-
(9) Logs of HA
-

-
-
For detailed information of (1) to (9), see Collecting logs (clplogcc command) in Chapter 2
EXPRESSCLUSTER X SingleServerSafe command reference.
OK
Start log collection and displays the dialog box of log collection progress.
Cancel
Close this dialog box.
Info
Display the information for each pattern.
Default
Section I WebManager Operation Reference
23
Chapter 1 Functions of the WebManager
Reset the selections of servers and collect patterns to default values.
When log collection starts, following dialog box appears.
Update
Update the dialog box of the log collection progress.
Abort
Abort the log collection.
Close
Close the dialog box. But, log collection still continues.
At this time, the display of Collect Logs in title view has changed to Progress.
To display the log collection dialog box again, click Progress in Tool menu.
Collect Logs Results
Result
Explanation
Normal
Log collection succeeded.
Abort
Log collection was cancelled by user.
Invalid parameter
Internal error may have occurred.
Communication Error
Connecting error occurred.
Timeout:
Timeout occurred.
Busy
The server is busy.
Compression Error
Error occurred when compressing a file.
File I/O Error
File I/O failed.
Not Enough Free Space
No free space on the disk.
Unknown Error
Failure caused by other errors
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
24
Window of the WebManager
When the log collection completes, the browser displays following dialog box that asks where
you want to save the logs. Save the logs to any location.
(*: This image shows the case when using Internet Explorer 8.0.)
Note:
Please save logs in 10 minutes after above dialog box appeared. Or, you may not save logs
correctly.
Note:
If other modal dialog box is displayed while collecting logs, the file saving dialog box for the log
collection will not be displayed. To display the file saving dialog box, close the modal dialog
box.
Note:
If the log file size exceeds 2GB, log collection may fail depending on the compression format.
Adjust the log to be collected or change the log collection pattern.
Updating the WebManager information
Click Reload on the Tool menu or click the reload icon (
information displayed in the WebManager.
) on the toolbar to update the
Note:
If the client data update method of the WebManager is set to Polling, the information displayed
on the WebManager is periodically updated and the latest status is not immediately displayed
even if the status has changed. To display the latest information, click the Reload icon ( ) or
Reload in the Tool menu after performing an operation.
To configure the automatic reload interval of the WebManager, Open Cluster Properties dialog
- WebManager tab. Click Tuning button and configure the Reload Interval.
Some objects may be displayed in gray when communications to the connecting destination is
disabled or EXPRESSCLUSTER X SingleServerSafe is not working at the access destination.
Section I WebManager Operation Reference
25
Chapter 1 Functions of the WebManager
Changing the screen layout on the WebManager
The WebManager screen layout can be changed by clicking the buttons of the split bars that
divide the screen or by dragging the bars. This is useful to display only a specific view.
The split bars divide the views in the WebManager.
On the bar, click
to maximize the view. Click
to minimize it.
To change the display items on the tree view, click Option on the Tool menu or option icon
( ) on the tool bar.
The following dialog is displayed. Check items you want to display.
Checking the time information from the WebManager
Check the time information from the WebManager by clicking Time info on the Tool menu or
by clicking the time information icon (
) on the toolbar.
Time information displayed on the Server tab

Cluster joined
Displays the most recent time at which each server joined the cluster.
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
26
Window of the WebManager
Time information displayed on the Group tab

Last activation
Displays the time at which the failover group was last activated on each server.

Last activation error
Displays the time at which an activation failure of a group resource was last detected on
each server.

Last deactivation
Displays the time at which the failover group was last deactivated on each server.

Last deactivation error
Displays the time at which a deactivation failure of a group resource was last detected on
each server.
Time information displayed on the Monitor tab

Last error detection
Displays the time at which each monitor resource last transitioned from normal status to
abnormal status on each server.
Note:
Message receive monitor resources isn't dealing.
Section I WebManager Operation Reference
27
Chapter 1 Functions of the WebManager
Clear
Deletes the time information displayed on the current tab.
Update
Acquires the time information for all the tabs.
Close
Closes the time information dialog box.
Note:
If the Client Data Update Method of the WebManager is set to Polling, when clear button was
pushed , Lighting up Time info on the Tool menu. But it's no problem as cluster..
Executing Integrated WebManager from the WebManager
To execute Integrated WebManager from the WebManager, click Integrated WebManager on
the Tool menu or Integrated WebManager icon ( ) on the tool bar.
Operating services on the WebManager
To operate services on the WebManager, select the relevant items shown below from the service
menu.

Suspend Cluster
Suspend EXPRESSCLUSTER Server service. This menu can be selected only when
EXPRESSCLUSTER Server service is running.

Resume Cluster
Resume EXPRESSCLUSTER Server service. This menu can be selected only when
EXPRESSCLUSTER Server service is suspended.

Start Cluster
Start EXPRESSCLUSTER Server service. This menu can be selected only when
EXPRESSCLUSTER Server service is stopped.

Stop Cluster
Stop EXPRESSCLUSTER Server service. This menu can be selected only when
EXPRESSCLUSTER Server service is running.

Restart Manager
Restart WebManager.
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
28
Window of the WebManager
Confirming the license from the WebManager
To confirm the license from the WebManager, click License Information on the Help menu.
License List
Displays the licenses registered on the connection destination server.
You can change the display order by selecting a specific field name on the title bar of the list.
By default, the licenses are sorted in ascending order of Product Name.
OK button
Closes the Detailed License Info dialog box.
Section I WebManager Operation Reference
29
Chapter 1 Functions of the WebManager
Checking the status of each object in the tree
view of WebManager
You can visually check the status of each object in the WebManager window.
On the left pane of the window, a tree is displayed. Check the status by looking at each icon and
object color. For meaning of each icon and object color, see Chapter 1, "Functions of the
WebManager” in Reference Guide for EXPRESSCLUSTER X.
Note:
The tree configuration depends on the version of and optional products used with
EXPRESSCLUSTER X SingleServerSafe.
Operations that can be executed from the WebManager
You can operate a cluster by right-clicking Cluster, Individual server, Individual group, or
Individual resource.
Cluster object
When you right-click a monitor resource object, the following shortcut menu is displayed.

Shut down
Shut down the server. When you select this operation, the following dialog box is displayed
for confirmation.

Reboot
Reboot the server. When you select this operation, the following dialog box is displayed for
confirmation.
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
30
Checking the status of each object in the tree view of WebManager

Service
If you select Service, the items Suspend Cluster, Resume Cluster, Start Cluster, Stop
Cluster and Restart Manager are displayed on the shortcut menu.
Server object
When you right-click a monitor resource object, the following shortcut menu is displayed.

Shut down
Shut down the selected server. When you select this operation, the following dialog box is
displayed for confirmation.

Reboot
Reboot the selected server. When you select this operation, the following dialog box is
displayed for confirmation.
Section I WebManager Operation Reference
31
Chapter 1 Functions of the WebManager

Recover
Recover the selected server. When you select this operation, the following dialog box is
displayed for confirmation.

Service
Start and stop the selected service. When you select Stop, the following dialog box is
displayed for confirmation.
For SingleServerSafe, you can not select Start.

Reset Statistical Data
Reset the statistical data of selected server. When you select this operation, the following
dialog box is displayed for confirmation.

CPU Frequency Settings
Change CPU frequency control setting for the selected server. This function can be used
when Use CPU Frequency Control check box is selected in the Power Saving tab of
Cluster Properties.

Highest Frequency
Set the CPU frequency to the highest (High performance).
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
32
Checking the status of each object in the tree view of WebManager

Lowest Frequency
Set the CPU frequency to the lowest (Power saver).

Auto
Set the CPU frequency controlled automatically depends on server or group status.
Group object
When you right-click a group object, the following shortcut menu is displayed.
Group type is failover.
Group type is virtualmachine.
Section I WebManager Operation Reference
33
Chapter 1 Functions of the WebManager

Start (enabled only when the group is stopped)
Start up the selected group. The dialog box for choosing a server on which to start up the
selected group is displayed.

Stop (enabled only when the group has been started up or when it has an error)
Stop the selected group resource. When you select this operation, the following dialog box
is displayed for confirmation.

Move (enabled only when the group has been started up)
Not used.

Migration (Only selectable when group type is virtualmachine and it is running.)
Not used.
Group resource object
When you right-click a monitor resource object, the following shortcut menu is displayed.

Start (enabled only when the group resource is stopped)
Start up the selected group resource. The dialog box for choosing a server on which to start
up the selected group is displayed.

34
Stop (enabled only when the group resource has been started up or when it has an error)
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
Checking the status of each object in the tree view of WebManager
Stop the selected group resource. When you select this operation, the following dialog box
is displayed for confirmation.
Monitor resource object
When you right-click a monitor resource object, the following shortcut menu is displayed.
When operation mode is selected
When verification mode is selected

Resume (enabled when the resources are stopped temporarily)
Resumes all the currently configured monitor resources. This operation is not performed for
those monitor resources for which the suspending/resuming of monitoring is not possible. A
dialog box for selecting the server on which the monitor resources will be resumed is
displayed.

Suspend (enabled when the resources are monitoring)
Section I WebManager Operation Reference
35
Chapter 1 Functions of the WebManager
Suspends all the currently configured monitor resources. This operation is not performed for
those monitor resources for which the suspending/resuming of monitoring is not possible. A
dialog box for selecting the server on which the monitor resources will be stopped
temporarily is displayed.

Stop Dummy Failure (enabled only when dummy failure is started)
Stops the dummy failure that has been set for all monitor resources. The following dialog
box for selecting the server on which dummy failure in the monitor resources is to be
stopped is displayed.
Individual monitor resource objects
When you right-click an individual monitor resource object, the following shortcut menu is
displayed.
When operation mode is selected
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
36
Checking the status of each object in the tree view of WebManager
When verification mode is selected

Resume (enabled when the resource is stopped temporarily)
Resumes a selected monitor resource. The dialog box for choosing the server on which the
selected monitor resource is resumed.

Suspend (enabled when the resource is monitoring)
Resumes the selected monitor resource. The dialog box for choosing the server on which the
selected monitor resource is stopped temporarily.

Start Dummy Failure (enabled when verification mode is not executed)
Generates a simulated fault in a selected monitor resource. A simulated fault can be
generated only on a server on which Resource Status on Each Server of the relevant
monitor resource is other than Error or Dummy Failure.
Note, however, that the following monitor resources cannot be selected:
Message receive monitor resource

VM monitor resource

Section I WebManager Operation Reference
37
Chapter 1 Functions of the WebManager
The following dialog box for selecting the server on which a dummy failure is generated for
a selected monitor resource is displayed.

Stop Dummy Failure (enabled when verification mode is executed)
Stops the dummy failure generated in a selected monitor resource. The following dialog box
for selecting the server on which the dummy failure is to be stopped for a selected monitor
resource is displayed.
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
38
Checking the status by the WebManager list view
Checking the status by the WebManager list
view
Details about the object selected in the WebManager tree view can be displayed in the list view.
Displaying information by using the WebManager list view
1.
Start the WebManager (http://server IP address:port number (default value is 29003)).
2.
In this tree view, click the object icon
for the whole. In the list view in the right pane of
the window, Name, Comment, and Status are displayed.
3.
In the following dialog box, click the Details button to display the following information. A
dialog box is displayed with the content shown below.
Info
Name:
Cluster name
Comment: Comment for the cluster
Status:
Status of the cluster
Heartbeat I/F
Server Down Notification:
Cast Method:
Not in use
This is the setting for the method to send a heartbeat
(unicast/broadcast). When the IP address of the heartbeat I/F
is IPv6, the broadcast cannot be used.
Section I WebManager Operation Reference
39
Chapter 1 Functions of the WebManager
NP Resolution
Action at NP Occurrence: Action to be taken when a network partition occurs
Timeout
Server Sync Wait Time:
Heartbeat Timeout:
Heartbeat Interval:
Server Internal Timeout:
Timeout Ratio:
Not in use
Heartbeat timeout (in milliseconds)
The interval for sending heartbeats (milliseconds)
Internal communication timeout (in seconds)
Current timeout ratio
Port Number
Server Internal Port Number:
Data Transfer Port Number:
Kernel Mode Heartbeat Port Number:
Client Service Port Number:
WebManager HTTP Port Number:
Alert Sync Port Number:
Disk Agent Port Number:
Mirror Driver Port Number:
Port number for internal communication
Port number for data transfer
Port number for kernel mode heartbeat
Port number for client service
Port number for WebManager
Port number for alert synchronization
Not in use
Not in use
Monitor
Collect System Resource Information: Whether or not to collect System Resource
Information
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
40
Checking the status by the WebManager list view
Recovery
Max Reboot Count:
Maximum number of reboot
Max Reboot Count Reset Time: Time to reset current number of reboot (in seconds)
Use Forced Stop:
Not in use
Forced Stop Action:
Not in use
Forced Stop Timeout:
Not in use
Execute Script for Forced Stop Not in use
Action When the Cluster Service Process Is Failure:
Action When the Cluster Service Process Is Failure
Action to be taken when a cluster service process fails
Recovery Action for HA Agents: Max Restart Count:
Maximum count to restart an HA process if the process
fails
Recovery Action for HA Agents: Recovery Action over Max Restart Count:
Action to be taken when the HA process fails and the
process cannot be restarted even after retrying restart of
the process for the maximum number of retries
Disable Recovery Action Caused by Monitor Resource Failure:
Whether or not to disable the recovery action when the
monitor resource fails
Action at Group Resource Activation or Deactivation Stall:
Action to be taken when group resource activation/
deactivation is stalled
Restrain the shutdown action if only one server is alive (when active group resource
abnormality detected):
Whether to disable shutdown at activation failure in the
case of the last one server
Restrain the shutdown action if only one server is alive (when deactive group resource
abnormality detected):
Whether to disable shutdown at deactivation failure in the
case of the last one server
Restrain the shutdown action if only one server is alive (when monitoring resource
abnormality detected):
Whether to disable shutdown at monitoring failure in the
case of the last one server
Section I WebManager Operation Reference
41
Chapter 1 Functions of the WebManager
Alert Service
E-mail Address:
Use Network Warning Light:
Use Chassis Identify:
Enable Alert Setting:
Alert mail address
Not in use
Not in use
Whether or not to enable setting
Delay Warning
Heartbeat Delay Warning:
Monitor Delay Warning:
COM Delay Warning:
Heartbeat delay warning (%)
Monitor delay warning (%)
Not in use
Disk
Shared Disk Disconnection Retry Threshold:
Shared Disk Disconnection Timeout:
Shared Disk Disconnection Retry Interval:
Shared Disk Disconnection Final Action:
Not in use
Not in use
Not in use
Not in use
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
42
Checking the status by the WebManager list view
Mirror Disk
Auto First Mirror Construction:
Auto Mirror Recovery:
Collect Mirror Statistics:
Mirror Disk Disconnection Retry Threshold:
Mirror Disk Disconnection Timeout:
Mirror Disk Disconnection Retry Interval:
Mirror Disk Disconnection Final Action:
Not in use
Not in use
Not in use
Not in use
Not in use
Not in use
Not in use
Auto Recovery
Auto Recovery: The setting whether a cluster server is automatically returned to the
cluster after the server is rebooted as “Suspension (Isolated)” state.
Power Saving
Use CPU Frequency Control: Whether or not to use CPU frequency control function
Section I WebManager Operation Reference
43
Chapter 1 Functions of the WebManager
JVM Monitor
Java Installation Path:
Maximum Java Heap Size (MB):
Java installation path
Maximum Java heap size
(MB)
Load Balancer Connection Setting:
Load balancer linkage settings
Log Level:
Log level
Generation Count for Stored Log Files:
Number of generations of log
files to be stored
Log Rotation Type:
Log rotation type
Log File Maximum Size (KB):
Maximum log file size (KB)
Time of First Log Rotation:
Time of the first log rotation
Log Rotation Interval (Hours):
Log rotation interval (hours)
Resource Measurement: Retry Count:
Measurement retry count
Resource Measurement: Threshold for Abnormal Judgment: Threshold for abnormal
judgment
Resource Measurement: Default Interval:
Interval for memory and
thread measurement (sec)
Resource Measurement: Interval for Full GC:
Interval for Full GC
measurement (sec)
WebLogic Monitoring: Retry Count:
Measurement retry count
WebLogic Monitoring: Threshold for Abnormal Judgment: Threshold for abnormal
judgment
WebLogic Monitoring: Request Count Measurement Interval: Interval for measuring the
number of requests (sec)
WebLogic Monitoring: Interval for Average measurement: Interval for measuring the
average (sec)
Management Port:
Management port number
Connection Retry Count:
Connection retry count
Time until Reconnect:
Time to wait for reconnection
(sec)
Management Port for Load Balancer Linkage:
Management port number for
load balancer linkage
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
44
Checking the status by the WebManager list view
Health Check Linkage Function:
Directory containing HTML files:
HTML File Name:
HTML Renamed File Name:
Retry Count for renaming:
Wait time for retry:
Management IP Address:
Connection Port:
Whether or not to use the
health check linkage function
HTML storage directory
HTML file name
Renamed HTML file name
Retry count if renaming fails
Time to wait for a renaming
retry (sec)
BIG-IP LTM management IP
address
Communication port number
for BIG-IP LTM
Section I WebManager Operation Reference
45
Chapter 1 Functions of the WebManager
Checking the whole status of the server in the WebManager list
view
1.
Start the WebManager (http://server IP address:port number (default value is 29003)).
2.
In the tree view, select Servers object icon
. In the upper part of the list view in the right
pane, the heartbeat status and network partition resolution status (not in use for
EXPRESSCLUSTER X SingleServerSafe) list of each server are displayed.
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
46
Checking the status by the WebManager list view
Checking the status of individual server in the WebManager list
view
1.
Start the WebManager (http://server IP address:port number (default value is 29003)).
2.
If the object
of a server is selected in the tree view, Comment, Version, Product,
Internal Version, Install Path and Status of the server are displayed.
Comment:
Virtual Infrastructure:
Product:
Internal Version:
Install Path:
Status:
3.
Comment for the server
Virtual infrastructure name
Product name
Internal version of EXPRESSCLUSTER X SingleServerSafe
Install path of EXPRESSCLUSTER X SingleServerSafe
Status of the server
Click Details to display the following in the dialog box.
Name:
Computer name
Mirror Disk Connect IP Address:
Not in use
Network Warning Light IP Address(Type): Not in use
BMC IP Address:
Not in use
CPU Frequency Status:
Current status of CPU frequency
No shutdown when double activation detected:
Not in use
Checking the status of the whole monitor in the WebManager list
view
1.
Start the WebManager (http://server IP address:port number (default value is 29003)).
2.
If you select the object icon
for the cluster in the tree view, Monitor Name and the server
status list are displayed in the list view.
Section I WebManager Operation Reference
47
Chapter 1 Functions of the WebManager
Checking alerts using the WebManager
You can view alerts in the bottom part of the WebManager.
Each field of the alert view is configured as follows.
(1) Alert type icon
(5) Alert sender module
(2) Alert received time
(6) Event ID
(4) Alert sender server
(3) Alert sent time
(7) Alert message
For the meanings of the individual alert messages, see Chapter 4 Error messages. For details
about searching alert messages, see “Searching for an alert by using the WebManager” in this
chapter.
Alert view fields
The meanings of each of the fields in the alert view of the WebManager are as follows.
(1) Alert type icon
Alert type
Meaning
Informational message
Warning message
Error message
(2) Alert received time
The time the alert was received. The time on the server to which the WebManager connects
is applied.
(3) Alert sent time
The time the alert was sent from a server. The time in the alert sender server is used.
(4) Alert sender server
The name of a server that sent the alert.
(5) Alert sender module
The name of a module that sent the alert.
(6) Event ID
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
48
Checking alerts using the WebManager
The event ID number set to each alert.
(7) Alert message
The alert messages.
Alert view operations
By clicking an item on the bar showing the name of each field, you can change the order of
alerts.
When you select an item, the
Mark
or
mark is displayed in the selected field.
Meaning
Sorts alerts in the ascending order of the selected field.
Sorts alerts in the descending order of the selected field.
By default, alerts are displayed in the Time descending order.
By dragging a field name left or right, you can change the order in which the items are displayed.
When you right-click this bar, the pop-up window below is displayed so you can select the items
to display. All items are selected by default.
When you double-click the displayed alert, the following window is displayed where you can
check the detail of the alert.
Section I WebManager Operation Reference
49
Chapter 1 Functions of the WebManager
When you right-click the alert, the following pop-up window is displayed where you can select
the type of the alert to be displayed. All items are selected by default.
Manually stopping and starting the
WebManager
After EXPRESSCLUSTER X SingleServerSafe is installed, the WebManager on the servers is
set up to start up or stop as the OS starts up or stops.
If you wish to stop and start the WebManager specifically, just stop or start
EXPRESSCLUSTER Manager service from the Service Control Manager console of
Administrative Tools.
When you do not want to use the WebManager
If you do not want to use the WebManager for some security reasons, change the settings of
Services of Administrative Tools of your OS or that of the Builder not to start the
WebManager.
When setting in Services of Administrative Tools, change the Startup Type of the
EXPRESSCLUSTER Manager service to Manual.
In Cluster Properties, you can specify the settings for using the WebManager. For details about
these settings, see "WebManager tab" in Chapter 6, "Details about other settings" in the
EXPRESSCLUSTER X SingleServerSafe Configuration Guide.
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
50
Setting limitations on the connection and operation of the WebManager
Setting limitations on the connection and
operation of the WebManager
The limitation in connection and operation of the WebManager can be configured in Cluster
Properties in the Builder. For details about these settings, see "WebManager tab" in Chapter 6,
"Details of other settings" in the EXPRESSCLUSTER X SingleServerSafe Configuration Guide.
Types of usage limitations
There are two ways to set usage limitations:

Limiting the access by using client IP addresses

Limiting the operation by using a password
Limsiting the access by using client IP addresses
This function limits clients who can access the WebManager and operations on the WebManager
by using client IP addresses.
Add IP addresses to IP Addresses of the Accessible Clients on the WebManager tab in the
Cluster Properties of the Builder.
When setting the limitation of the connection of the WebManager, if you attempt to access to the
WebManager from the IP address that is not added to IP Addresses of the Accessible Clients,
the following error messages are displayed.
Example: when using the Internet Explorer
When connecting to the WebManager from the client that is restricted operations for cluster, you
can select only Reference Mode.
The following operations are disabled from the WebManager when operations are limited.

Shutting down or shutting down and then rebooting servers

Starting or stopping groups

Switching to Operation Mode

Switching to Config Mode

Switching to Verification Mode
Section I WebManager Operation Reference
51
Chapter 1 Functions of the WebManager
The limitation by using a password
This function limits viewing and operations on the WebManager by using a password.
To configure this limitation: in Cluster Properties of the Builder, click the WebManager tab,
and then Control connection by using password.
Once password limitation of the WebManager is specified, the following authorization dialog
box is displayed when trying to access the WebManager by setting a password.
You can log on to the WebManager by selecting Operate Mode or Reference Only in
Authorization and entering a correct password.

The authorization dialog box is not displayed when the password limitation is not
configured (you can log on to the WebManager without authorization).

You cannot log on to the WebManager if you enter a wrong password three consecutive
times.
When you login with Reference Only selected for Permission, the WebManager is placed in
reference mode. When you attempt to switch to operation mode, config mode, or verification
mode in this status, the above authorization dialog is displayed, and you are requested to enter a
password for Operation Mode.
Combination of the IP address and password
The operational limitations when using both IP addresses and passwords are the following:
Password limitation
Client IP address
limitation
Operable mode
Reference only
Unable to
operate/view
(authorization
failed)
Operable mode
Operable mode
Reference only
Unavailable
Reference only
Reference only*
Reference only
Unavailable
Cannot access
Cannot access
Cannot access
Cannot access
*Authorization cannot be selected.
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
52
Section II
Command Reference
This section describes the commands available with EXPRESSCLUSTER X SingleServerSafe.
EXPRESSCLUSTER X SingleServerSafe uses commands common to those of the clustering software
EXPRESSCLUSTER X to ensure high compatibility with EXPRESSCLUSTER X in terms of operation and
other aspects. Because the information contained herein is specific to EXPRESSCLUSTER X
SingleServerSafe, see the Reference Guide for EXPRESSCLUSTER X to obtain an overall understanding of
the commands.
•
Chapter 2
EXPRESSCLUSTER X SingleServerSafe command reference
53
Chapter 2
EXPRESSCLUSTER X
SingleServerSafe command
reference
This chapter describes the commands available with EXPRESSCLUSTER X SingleServerSafe.
This chapter covers:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Operating the cluster from the command line ····································································· 56
EXPRESSCLUSTER commands ··················································································· 56
Displaying the status (clpstat command) ·········································································· 58
Operating the service (clpcl command) ············································································ 61
Shutting down the server (clpstdn command) ····································································· 65
Operating groups (clpgrp command) ··············································································· 66
Collecting logs (clplogcc command) ··············································································· 69
Applying and backing up configuration data (clpcfctrl command)············································· 74
Adjusting time-out temporarily (clptoratio command) ·························································· 80
Modifying the log level and size (clplogcf command) ··························································· 83
Registering the license (clplcnsc command) ····································································· 91
Outputting messages (clplogcmd command) ······································································ 93
Controlling monitor resources (clpmonctrl command) ·························································· 95
Controlling group resources (clprsc command) ··································································· 99
Controlling CPU frequency (clpcpufreq command) ··························································· 101
Requesting processing to cluster servers (clprexec command) ··············································· 103
Controlling reboot count (clpregctrl command) ································································ 106
Estimating the amount of resource usage (clpprer command) ················································ 108
Checking the process health (clphealthchk command) ······················································ 113
55
Chapter 2 EXPRESSCLUSTER X SingleServerSafe command reference
Operating the cluster from the command line
EXPRESSCLUSTER X SingleServerSafe provides various commands for performing operations
from the command prompt. These commands are useful in such cases as when you are setting up
a cluster or cannot use the WebManager. You can perform a greater number of operations by
using the command line than by using the WebManager.
Note:
If the monitor resource detects an error when you have specified a group resource (such as an
application resource) as a recovery target in the settings for error detection by a monitor resource,
do not perform the following control operations for any service or group by using a command or
the WebManager during recovery (reactivation -> final action).

Stopping or suspending a service

Starting or stopping a group
If you perform the above-mentioned operations while recovery caused by detection of an error by
a monitor resource is in progress, other group resources of the group with an error may not stop.
However, you can perform them when the final action is completed.
EXPRESSCLUSTER commands
Commands for construction
Command
Explanation
Page
clpcfctrl.exe
Applies the configuration data created
by the Builder to servers.
74
Backs up the configuration data to be
used by the Builder.
clplcnsc.exe
Registers the full or trial version license
of this product.
91
Command
Explanation
Page
clpstat.exe
Displays the status and configuration
data of EXPRESSCLUSTER X
SingleServerSafe.
58
clphealthchk.exe
Check the process health.
113
Command
Explanation
Page
clpcl.exe
Starts, stops, suspends, or resumes
the service.
61
clpstdn.exe
Stops the service and shuts down a
server.
65
clpgrp.exe
Starts and stops groups.
66
clptoratio.exe
Extends or displays the timeout values.
80
clpmonctrl.exe
Suspends or resumes monitor
resources.
95
clprsc.exe
Suspends or resumes group resources.
99
Commands for showing status
Commands for operation
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
56
EXPRESSCLUSTER commands
clpcpufreq.exe
Controls CPU frequency.
101
clprexec.exe
Requests a server to execute a
process.
103
clpregctrl.exe
Controls the reboot count limitation.
106
Command
Explanation
Page
clplogcc.exe
Collects logs and OS information.
69
clplogcf.exe
Changes and displays the log level and
log output file size.
83
Command
Explanation
Page
clplogcmd.exe
Write this command in the script
resource script to output messages to
any destination.
91
Commands for logs
Commands for scripts
Important:
The installation directory contains executable files and script files that are not listed in this guide.
Do not execute these files by using any program other than EXPRESSCLUSTER X
SingleServerSafe. Any problems caused by not using EXPRESSCLUSTER will not be
supported.
System monitor-related commands (when the System Resource Agent is used)
Command
Explanation
Page
clpprer.exe
Estimates the future value from the
tendency of the given resource use
amount data.
108
Section II Command Reference
57
Chapter 2 EXPRESSCLUSTER X SingleServerSafe command reference
Displaying the status (clpstat command)
clpstat:
Displays the status and configuration data of EXPRESSCLUSTER X
SingleServerSafe.
Command line:
clpstat –s [--long]
clpstat –g
clpstat –m
clpstat –i [--detail]
clpstat --cl [--detail]
clpstat --sv [--detail]
clpstat --grp [<grpname>] [--detail]
clpstat --rsc [<rscname>] [--detail]
clpstat --mon [<monname>] [--detail]
Description
Displays the status and configuration data of EXPRESSCLUSTER X
SingleServerSafe.
Option
-s
Displays the status.
None
Return Value
--long
Displays a name of the cluster name and resource
name until the end.
-g
Displays groups.
-m
Displays the status of each monitor resource.
-i
Displays the overall configuration data.
--cl
Displays the configuration data.
--sv
Displays the server configuration information.
--grp [<grpname>]
Displays server group configuration information.
By specifying the name of a server group, you can
display only the information on the specified server
group.
--rsc [<rscname>]
Displays group resource configuration information.
By specifying the name of a group resource, you
can display only the information on the specified
group resource.
--mon
[<monname>]
Displays monitor resource configuration
information. By specifying the name of a monitor
resource, you can display only the information on
the specified monitor resource.
--detail
Displays more detailed information on the setting.
0
Success
251
Double Activation
Other
above
than
the
Failure
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
58
Displaying the status (clpstat command)
Remarks
According to the combination of options, configuration information
shows information in various forms.
Notes
Run this command as a user with Administrator privileges .
The EXPRESSCLUSTER service must be activated on the server where
you run this command.
When you run the clpstat command with the –s option or without any
option, names such as a cluster or a resource will not be displayed
halfway .
Example of
Execution
Examples of information displayed after running these commands are
provided in the next section.
Error Messages
Message
Cause/Solution
Log in as administrator.
Log in as a user with Administrator
privileges.
Invalid configuration file. Create valid
cluster configuration data by using the
Builder.
Create valid cluster configuration data
by using the Builder.
Invalid option.
Specify a valid option.
Could not connect to the server. Check
if the cluster service is active
Check if the EXPRESSCLUSTER
service is operating.
Invalid server status.
Check if the EXPRESSCLUSTER
service is operating.
Server is not active. Check if the cluster
service is active.
Check if the EXPRESSCLUSTER
service is operating.
Invalid server name. Specify a valid
server name in the cluster.
Specify the valid server name in the
cluster.
Invalid heartbeat resource name.
Specify a valid heartbeat resource
name in the cluster.
Specify the valid heart beat resource
name in the cluster.
Invalid network partition resource
name. Specify a valid network partition
resource name in the cluster.
Specify the valid network partition
resolution resource name in the cluster.
Invalid group name. Specify a valid
group name in the cluster.
Specify the valid name of a group in the
cluster.
Invalid group resource name. Specify a
valid group resource name in the
cluster.
Specify the valid name of a group
resource in the cluster.
Invalid monitor resource name. Specify
a valid monitor resource name in the
cluster.
Specify the valid name of a monitor
resource in the cluster.
Connection was lost. Check if there is a
server where the cluster service is
stopped in the cluster.
Check if there is any server on which
the EXPRESSCLUSTER service has
stopped in the cluster.
Invalid parameter.
An invalid value may be specified to
command argument.
Section II Command Reference
59
Chapter 2 EXPRESSCLUSTER X SingleServerSafe command reference
Message
Cause/Solution
Internal communication timeout has
occurred in the cluster server. If it
occurs frequently, set a longer timeout.
A
time-out
occurred
EXPRESSCLUSTER
communication.
in
the
internal
If time-out keeps occurring, set the
internal communication time-out longer.
Internal error. Check if memory or OS
resources are sufficient.
Check if the memory or OS resource is
sufficient.
The cluster is not created.
Create
and
apply
configuration data.
the
cluster
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
60
Operating the service (clpcl command)
Operating the service (clpcl command)
clpcl
Operates the EXPRESSCLUSTER service.
Command line:
clpcl –s
clpcl –t [-w <timeout>] [--apito <timeout>]
clpcl –r [-w <timeout>] [--apito <timeout>]
clpcl –-return [--apito <timeout>]
clpcl –-suspend [--force] [-w <timeout>] [--apito <timeout>]
clpcl –-resume
Description
This command starts, stops, restarts, suspends, or resumes the
EXPRESSCLUSTER service.
Option
-s
Starts the EXPRESSCLUSTER service.
-t
Stops the EXPRESSCLUSTER service.
-r
Restarts the EXPRESSCLUSTER service.
--return
Returns the EXPRESSCLUSTER service.
--suspend
Suspends the EXPRESSCLUSTER service.
--resume
Resumes the EXPRESSCLUSTER service.
-w <timeout>
When --t, --r, or --suspend option is used, specify
the wait time in seconds that the clpcl command
waits for the EXPRESSCLUSTER service to be
completely stopped or suspended.
When timeout is not specified, it waits for unlimited
time.
When "0" is specified for timeout, the command
does not wait at all.
--force
--apito timeout
When the -w option is not specified (default), the
command waits for twice the heartbeat timeout time
(in seconds).
When used with the --suspend option, this option
forcefully suspends the service regardless of the
server status.
Specify the time in seconds to wait for the
EXPRESSCLUSTER service to be stopped,
restarted, or suspended (internal communication
timeout). A value between 1 to 9999 can be
specified.
When the --apito option is not specified, the
command waits according to the value set for the
internal communication timeout in the cluster
property.
Section II Command Reference
61
Chapter 2 EXPRESSCLUSTER X SingleServerSafe command reference
Return Value
Remarks
0
Success
Other than 0
Failure
When this command is executed with the -s or --resume option specified,
it returns control when processing starts on the target server.
When this command is executed with the -t or --suspend option specified,
it returns control after waiting for the processing to complete.
When this command is executed with the -r option specified, it returns
control when the EXPRESSCLUSTER daemon restarts on the target
server after stopping once.
Run the clpstat command to display the started or resumed status of the
EXPRESSCLUSTER daemon.
Notes
This command must be executed by a user with the administrator
privilege.
This command cannot be executed while a group is being started or
stopped.
Before you suspend the EXPRESSCLUSTER service, the service must be
running.
Before you resume the EXPRESSCLUSTER service, use the clpstat
command to make sure that the service is not running.

Suspend and Resume
When you want to update the configuration data or EXPRESSCLUSTER X
SingleServerSafe, you can stop the EXPRESSCLUSTER service while continuing the
operation. This status is called the suspended status. Returning from the suspended status to
normal status is called “resume.”
The suspend and resume operations request processing of the server.
EXPRESSCLUSTER service must be active when you execute a suspend operation.
The
The following functions stop when the cluster is suspended
EXPRESSCLUSTER service stops while active resources stay active.
the
because
•
All monitor resources stop.
•
You cannot perform operations on groups or group resources (start/stop).
•
You cannot display or change the status by using the WebManager or clpstat
command.
•
The following commands are disabled:
clpstat
clpcl options other than --resume
clpstdn
clpgrp
clptoratio
clpmonctrl
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
62
Operating the service (clpcl command)
Error Messages
Message
Cause/Solution
Log in as administrator.
Log in as a user with Administrator
privileges.
Invalid configuration file. Create valid
cluster configuration data by using the
Builder.
Create valid cluster configuration data
using the Builder.
Invalid option.
Specify a valid option
Performed stop processing to the stopped
cluster service.
The stopping process has been executed
to the stopped EXPRESSCLUSTER
service.
Performed startup processing to the active
cluster service.
The startup process has been executed to
the activated EXPRESSCLUSTER
service.
Command timeout.
The command timed out.
Failed to return the server. Check the
status of failed server.
Failed to return the server. Check the
status of the failed server.
Could not connect to the server. Check if
the cluster service is active.
Check if the EXPRESSCLUSTER service
is activated.
Failed to obtain the list of nodes. Specify a
valid server name in the cluster.
Specify the valid name of a server in the
cluster.
Failed to obtain the service name.
Failed to obtain the service name.
Failed to operate the service.
Failed to operate the service.
Resumed the cluster service that is not
suspended.
Resumed the EXPRESSCLUSTER service
that is not suspended.
invalid server status.
Check if the EXPRESSCLUSTER service
is activated.
Server is busy. Check if this command is
already run.
This command may be run already. Check
it.
Server is not active. Check if the cluster
service is active.
Check if the EXPRESSCLUSTER service
is activated.
There is one or more servers of which
cluster service is active. If you want to
perform resume, check if there is any
server whose cluster service is active in
the cluster.
When you execute the command to
resume, check if there is no server in the
cluster on which the EXPRESSCLUSTER
service is activated.
All servers must be activated. When
suspending the server, the cluster service
need to be active on all servers in the
cluster.
When you execute the command to
suspend, the EXPRESSCLUSTER service
must be activated in all servers in the
cluster.
Resume the server because there is one
or more suspended servers in the cluster.
Execute the command to resume because
some server(s) in the cluster is
suspended.
Invalid server name. Specify a valid server
name in the cluster.
Specify the valid name of a server in the
cluster.
Connection was lost. Check if there is a
server where the cluster service is stopped
in the cluster.
Check if there is any server on which the
EXPRESSCLUSTER service has stopped
in the cluster.
invalid parameter.
The value specified as a command
parameter may be invalid.
Section II Command Reference
63
Chapter 2 EXPRESSCLUSTER X SingleServerSafe command reference
Message
Cause/Solution
Internal communication timeout has
occurred in the cluster server. If it occurs
frequently, set the longer timeout.
A timeout occurred in the
EXPRESSCLUSTER internal
communication.
If time-out keeps occurring, set the internal
communication time-out longer.
Processing failed on some servers. Check
the status of failed servers.
If stopping process is executed to all
servers, there is one or more servers on
which the stopping process has failed.
Check the status of the server(s) on which
the stopping process has failed.
Internal error. Check if memory or OS
resources are sufficient.
Check if the memory or OS resource is
sufficient.
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
64
Shutting down the server (clpstdn command)
Shutting down the server (clpstdn command)
clpstdn
Shuts down the server.
Command line:
clpstdn [-r]
Description
This command stops the EXPRESSCLUSTER service of the server and
shuts down all servers.
Option
None
Servers are shut down.
-r
Shuts down and then reboots servers.
0
Success
Other than 0
Failure
Return Value
Remarks
This command returns control when the group stop processing is
completed.
Notes
This command must be executed by a user with the administrator
privilege.
This command cannot be executed while a group is being started or
stopped.
Error
Message
See “Operating the service (clpcl command)” on page 61.
Section II Command Reference
65
Chapter 2 EXPRESSCLUSTER X SingleServerSafe command reference
Operating groups (clpgrp command)
clpgrp
Operates groups.
Command line:
clpgrp -s [<grpname>] [--apito timeout]
clpgrp -t [<grpname>] [--apito timeout]
Description
Starts and stops groups.
Option
-s [<grpname>]
When you specify the name of a group for grpnam,
only the specified group starts up. If no group name
is specified, all groups start up.
-t [<grpname>]
When you specify the name of a group for grpnam,
only the specified group stops. If no group name is
specified, all groups stop.
Specify the time in seconds to wait for groups to be
started, stopped(internal communication timeout). A
value between 1 to 9999 can be specified.
--apito timeout
When the --apito option is not specified, the
command waits according to the value set for the
internal communication timeout in the cluster
property.
Return Value
0
Success
Other than 0
Failure
This command must be executed by a user with the administrator
privilege.
Notes
The EXPRESSCLUSTER service must be running.
Error message
Message
Cause/Solution
Log in as administrator.
Log in as a user with Administrator
privileges.
Invalid configuration data. Create valid
cluster configuration data by using the
Builder.
Create valid cluster configuration data
using the Builder
Invalid option.
Specify a valid option
Could not connect to the server. Check if
the cluster service is active.
Check if the EXPRESSCLUSTER
service is operating.
Invalid server status. Check if the cluster
service is active.
Check if the EXPRESSCLUSTER
service is operating.
Server is not active. Check if the cluster
Check if the EXPRESSCLUSTER
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
66
Operating groups (clpgrp command)
Message
service is active.
Cause/Solution
service is operating.
Invalid server name. Specify a valid
server name in the cluster.
Specify the valid server name in the
cluster.
Connection was lost. Check if there is a
server where the cluster service is
stopped in the cluster.
Check if there is any server on which the
EXPRESSCLUSTER service has
stopped in the cluster.
Invalid parameter.
The value specified as a command
parameter may be invalid.
Internal communication timeout has
occurred in the cluster server. If it occurs
frequently, set a longer timeout.
A time-out occurred in the
EXPRESSCLUSTER internal
communication.
If time-out keeps occurring, set the
internal communication time-out longer.
Invalid server. Specify a server that can
run and stop the group, or a server that
can be a target when you move the
group.
Server that starts and stops the group or
to which the group is moved is invalid.
Could not start the group. Try it again
after the other server is started, or after
the Wait Synchronization time is timed
out.
Start up the group after waiting for the
remote server to start up, or after waiting
for the timeout of the start-up wait time.
No operable group exists in the server.
Check if there is any group that is
operable in the server which requested
the process.
The group has already been started on
the local server.
Check the status of the group by using
the WebManager or the clpstat
command.
The group has already been started on
the other server. To start/stop the group
on the local server, use -f option.
Check the status of the group by using
the WebManager or the clpstat
command.
Specify a valid server.
If you want to start up or stop a group
which was started in a remote server
from the local server, move the group or
run the command with the -f option.
The group has already been stopped.
Check the status of the group by using
the WebManager or the clpstat
command.
Failed to start one or more resources.
Check the status of group.
Check the status of group by using the
WebManager or the clpstat command.
Failed to stop one or more resources.
Check the status of group.
Check the status of group by using the
WebManager or the clpstat command.
The group is busy. Try again later.
The group is now being started or
stopped. Wait for a while and try again.
An error occurred on one or more
groups. Check the status of group.
Check the status of the group by using
the WebManager or the clpstat
command.
Invalid group name. Specify a valid
group name in the cluster.
Specify the valid name of a group in the
cluster.
Server is isolated.
The server has been suspended. The
server is rebooted after it went down.
Some invalid status. Check the status of
The status is invalid. Check the status of
Section II Command Reference
67
Chapter 2 EXPRESSCLUSTER X SingleServerSafe command reference
Message
cluster.
Cause/Solution
the cluster.
Log in as administrator.
Check if the memory or OS resource is
sufficient.
Failed to migrate the group.
If the -l option is used, check whether
the type of the specified group is
“virtualmachine”.
The specified group cannot be migrated.
Check the status of the group.
The specified group is not vm group.
Check if the type of the group is set to
the virtual machine.
Migration resource does not exist.
Check if the virtual machine resource
exists in the group.
Migration resource is not online.
Check if the virtual machine resource
has already started.
Server is not in a condition to start
group. Critical monitor error is detected.
Check the status of each server.
There is no appropriate destination for
the group. Critical monitor error is
detected.
Check the status of each server.
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
68
Collecting logs (clplogcc command)
Collecting logs (clplogcc command)
clplogcc
Collects logs.
Command line:
clplogcc [-t collect_type] [-o path] [--local] [--evt event_type …]
Description
Collects logs and OS information.
Option
None
Logs are collected.
-t collect_type
Specifies a log collection pattern. When this option
is omitted, a log collection pattern will be type 1.
Specifies the output destination of collector files.
When this option is omitted, logs are output under
tmp of the installation path.
Collects logs on the local server without going
through the data transfer server.
Specifies the type of the event log to be collected.
When this option is skipped, application logs,
system logs and security logs will be collected. This
option is enabled only when [--local] option is
specified.
-o path
--local
--evt event_type
For details, see "Specifying a event log type to
collect (--evt option)".
Return Value
0
Success
Other than 0
Failure
Remarks
Because log files are compressed in the cab format, decompress them by
using an appropriate application.
Notes
This command must be executed by a user with the administrator
privilege.
Execution
Result
For this command, the following processes are displayed:
Steps in Process
Explanation
Preparing
Initializing
Connecting
Connecting to the server
Compressing
Compressing log files
Transmitting
Sending log files
Disconnecting
Disconnecting from the server
Completion
Finished collecting logs
The following results (server status) are displayed:
Section II Command Reference
69
Chapter 2 EXPRESSCLUSTER X SingleServerSafe command reference
Result (server status)
Explanation
Normal
Completed successfully
Canceled
Canceled by the user
Invalid Parameters
Parameters are invalid
Compression Error
There was an error while compressing
files.
Communication Error
There was a communication error.
Timeout
Timeout occurred.
Busy
The server is busy.
No Free Space
No free space on the disk.
File I/O Error
There was a file I/O error.
Unknown Error
Failure caused by other errors
Error message
Message
Cause/Solution
Log in as administrator.
Log in as a user with Administrator
privileges.
Invalid option.
Specify a valid option.
Collect type must be specified 'type1' or
'type2' or 'type3'. Incorrect collection type
is specified.
Invalid collection type is specified.
Specifiable number of servers are the
max number of servers that can
constitute a cluster.
The number of servers you can specify
is within the maximum number of servers
for cluster configuration.
Failed to obtain properties.
Failed to obtain the properties.
Failed to obtain the list of nodes. Specify
a valid server name in the cluster.
Specify the valid name of a server in the
cluster.
Invalid server name. Specify a valid
server name in the cluster.
Specify the invalid server name in the
cluster.
Failed to collect log.
Failed to collect logs.
Server is busy. Check if this command is
already run.
This command may be run already.
Check it.
Internal error. Check if memory or OS
resources are sufficient.
Check if the memory or OS resource is
sufficient.
Collecting logs by specifying a type (-t option)
To collect only the specified types of logs, run the clplogcc command with the –t option.
Specify a type from 1 thorough 4 for the log collection.
Type1
Type 2
Type 3
Type 4
(1) Default collection information
y
y
y
n
(2) Event log
y
y
y
y
(3) Dr. Watson log
y
y
y
y
(4) User dump
y
y
n
n
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
70
Collecting logs (clplogcc command)
(5) Diagnostics report
y
y
n
n
(6) Registry
y
y
y
n
(7) Scripts
y
y
y
n
(8) Logs of ESMPRO/AC and ESMPRO/UPSC
y
y
y
n
(9) Logs of HA
n
y
n
n
(y: yes, n: no)
Run this command from the command line as follows.
Example: When collecting logs using type 2
# clplogcc –t type2
When no option is specified, a log type will be type 1.


Information to be collected by default
•
Logs of each module in the EXPRESSCLUSTER Server
•
Attribute information on each module (dir) in the EXPRESSCLUSTER Server
In bin
In alert\bin, In webmgr\bin
In %SystemRoot%\system32\drivers
•
EXPRESSCLUSTER X SingleServerSafe version information
•
OS information
•
Update log
•
CPU license and node license
•
Configuration file
•
Policy file
•
Shared memory dump
•
Local node status of EXPRESSCLUSTER (clpstat --local execution results)
•
Host name and domain name information (hostname execution result)
•
Network information (netstat execution result)
•
IP routing table information (route print execution results)
•
Memory usage status (mem execution result)
•
Process existing status (tasklist execution result)
•
ipconfig (ipconfig execution result)
•
Windows firewall settings (netsh execution result)
•
SNP (Scalable Networking Pack) setting (netsh execution result)
•
Task schedule settings (schtasks execution result)
Event log

•
Application log (AppEvent.Evt, Application.evtx, Application.txt)
•
System log (SysEvent.Evt, System.evtx, System.txt)
•
Security log (SecEvent.Evt, Security.evtx, Security.txt)
Dr. Watson log/Windows Error Report

•
drwtsn32.log (Windows Server 2003)
•
***.wer (Windows Server 2008 or later)
User dump

•
user.dmp (Windows Server 2003)
•
***.hdmp (Windows Server 2008)
•
***.mdmp (Windows Server 2008)
•
***.*dmp (Windows Server 2012)
Diagnostics report
•
The result of running msinfo32.exe
Registry
•
Registry information of the EXPRESSCLUSTER Server
Section II Command Reference

71
Chapter 2 EXPRESSCLUSTER X SingleServerSafe command reference

HKLM\SOFTWARE\NEC\EXPRESSCLUSTER\Alert
HKLM\SOFTWARE\NEC\EXPRESSCLUSTER\MirrorList
HKLM \SOFTWARE\NEC\EXPRESSCLUSTER\RC
HKLM \SOFTWARE\NEC\EXPRESSCLUSTER\VCOM
Registry information of diskfltr
•
Registry information of OS
HKLM\SYSTEM\CurrentControlSet\Services\Disk
HKLM\SYSTEM\CurrentControlSet\Control\Session
Manager\DOS Devices
HKLM\SYSTEM\MountedDevices
HKLM\SYSTEM\CurrentControlSet\Enum\SCSI
HKLM\SYSTEM\CurrentControlSet\Enum\STORAGE
HKLM\SYSTEM\CurrentControlSet\Services\symc8xx
HKLM\SYSTEM\CurrentControlSet\Control\FileSystem
Scripts
Start/stop script for a group that was created with the Builder.
If you specify a user-defined script, it is not included in the log collection information. It
must be collected separately.

ESMPRO/AC and ESMPRO/UPSC logs
Files collected by running the acupslog.exe command

HA logs
•
System resource information
•
JVM monitor log
•
System monitor log
Output paths of log files (-o option)

Log file is named and be saved as server_name-log.cab.

Because log files are compressed in the cab format, decompress them by using an
appropriate application.
If not specifying -o option
Logs are output in tmp of installation path.
When the -o option is specified:
If you run the command as follows, logs are located in the specified c:\tmp directory.
# clplogcc –o C:\tmp
Specifying a event log type to collect (--evt option)
You can specify the type of the event log included in the information obtained at the log
collection.
Specify one or more text strings that represent event log types as shown in the following table
after [--evt] option.
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
72
Collecting logs (clplogcc command)
Event log type
Character string to specify
Application log
app
System log
sys
Security log
sec
Example) Collecting the system log and the security log
# clplogcc --local --evt sys sec

This option is enabled only when the [--local] option is specified.
Collecting information on emergency OS shutdown
The OS resource information is collected when the EXPRESSCLUSTER service fails due to
termination by an internal status error or a similar problem.
Information to be collected is as follows:

Information created by running a command
•
Host name and domain name information (hostname execution result)
•
Network information (netstat execution result)
•
Memory usage status (mem execution result, only for Windows Server 2003)
•
Process existing status (tasklist execution result)
•
ipconfig (ipconfig execution result)
These are collected by default in the log collection. You do not need to collect them separately.
Section II Command Reference
73
Chapter 2 EXPRESSCLUSTER X SingleServerSafe command reference
Applying and backing up configuration data
(clpcfctrl command)
Applying configuration data (clpcfctrl --push)
clpcfctrl --push
Applies the configuration data to servers.
Command line:
clpcfctrl --push [-w] [-x <path>] [-p <portnumber>] [--nocheck]
Applies the configuration data created by the Builder to servers.
Description
Option
--push
Specify this option when applying the data.
This option cannot be omitted.
-x
Specify this option to apply the configuration data in the
specified directory.
-w
Indicates that SJIS encoding is used for the configuration data
file.
In general, it is not necessary to specify this option
-p
Specifies the number of the port used to transfer data.
When this option is omitted, the default value is used. In
general, it is not necessary to specify this option.
--nocheck
Return Value
Omits the check on the operation necessary to apply changes.
0
Success
Other than 0
Failure
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
74
Applying and backing up configuration data (clpcfctrl command)
Notes
Run this command as a user with Administrator privileges.
When the configuration data is applied, the current configuration data is
compared with the configuration data to be applied.
If there is any change in the configuration data, the following message
output. After operating the service or group by following the
instructions in the message, execute the command again.
Message
Solution
Please stop
EXPRESSCLUSTER Server.
Stop the server.
Please suspend
EXPRESSCLUSTER Server.
Suspend the server.
Please stop the following groups.
Stop the group for which the
setting has been changed.
Reboot of a cluster is necessary
to reflect setting.
Shut down and reboot the cluster
to apply the change of settings.
To apply the changes you made,
restart the EXPRESSCLUSTER
Web Alert service.
Restart the Web Alert service to
apply the change of settings.
To apply the changes you made,
restart the EXPRESSCLUSTER
Manager service.
Restart the EXPRESSCLUSTER
Manager service to apply the
change of settings.
Start of a cluster is necessary to
reflect setting.
This is the message displayed at
the initial cluster configuration.
Start the cluster.
The --nocheck option is used only for special purposes including a
maintenance procedure. Do not use the --nocheck option for normal
operations.
Error Message
Message
Cause/Solution
Log in as administrator.
Log in as a user with Administrator
privileges.
This command is already run.
This command has already been run.
invalid option.
This option is invalid. Check the
option.
Invalid mode. Check if -push or -pull
option is specified.
Check if --push is specified.
Invalid host name. Server specified
by -h option is not included in the
configuration
The server specified with -h is not
included in configuration data. Check
if the specified server name or IP
address is correct.
Failed to initialize the xml library.
Check if memory or OS resources
are sufficient.
Check if the memory or OS resources
are sufficient.
Failed to load the configuration file.
Check if memory or OS resources
are sufficient.
Failed to change the configuration
Section II Command Reference
75
Chapter 2 EXPRESSCLUSTER X SingleServerSafe command reference
Message
file. Check if memory or OS
resources are sufficient.
Cause/Solution
Failed to load the all.pol file.
Reinstall the RPM cluster.
Reinstall the EXPRESSCLUSTER
Server.
Failed to load the cfctrl.pol file.
Reinstall the RPM cluster.
Reinstall the EXPRESSCLUSTER
Server.
Failed to get the install path.
Reinstall the RPM cluster.
Reinstall the EXPRESSCLUSTER
Server.
Failed to initialize the trncl library.
Check if memory or OS resources
are sufficient.
Check if the memory or OS resources
are sufficient.
Failed to connect to trnsv. Check if
the other server is active.
Accessing the server has failed.
Check if the other server has been
started up.
Failed to get the list of node. Check
if the server specified by -c is a
member of the cluster.
Check if the server specified by -c is a
cluster member.
File delivery failed. Failed to deliver
the configuration data. Check if the
other server is active and run the
command again.
Delivering configuration data has
failed. Check if other server(s) has
been started.
Multi file delivery failed. Failed to
deliver the configuration data.
Check if the other server is active
and run the command again.
Delivering configuration data has
failed. Check if other server(s) has
been started.
Failed to deliver the configuration
data. Check if the other server is
active and run the command again.
Delivering configuration data has
failed. Check if other server(s) has
been started.
Run the command again after the
server has started up.
Run the command again after the
server has started up.
Run the command again after the
server has started up.
Failed to upload the configuration
file. Check if the other server is
active and run the command again.
Delivering configuration data has
failed. Check if other server(s) has
been started
Canceled to deliver the
configuration file since it failed to
connect to one or more server. If
you want to deliver the configuration
file to servers that can be
connected, run the command again
with "-force" option.
Canceled the delivery of the
configuration data. There are some
servers that failed to connect. If you
want to deliver the configuration data
only to the server that can be
connected, run the command again
by using the --force option.
The directory "work" is not found.
Reinstall the RPM.
Reinstall the EXPRESSCLUSTER
Server.
Failed to make a working directory.
Check if the memory or OS resources
are sufficient.
The directory does not exist.
This is not a directory.
The source file does not exist.
The source file is a directory.
The source directory does not exist.
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
76
Applying and backing up configuration data (clpcfctrl command)
Message
Cause/Solution
The source file is not a directory.
Failed to change the character code
set (EUC to SJIS).
Failed to change the character code
set (SJIS to EUC).
Failed to allocate memory.
Failed to change the directory.
Check if the memory or OS resources
are sufficient.
Failed to make a directory.
Failed to remove the directory.
Failed to remove the file.
Failed to open the file.
Failed to read the file.
Failed to copy the file.
Failed to create the mutex.
Internal error. Check if memory or
OS resources are sufficient.
Failed to check server property.
Check if the server name or ip
addresses are correct by builder.
Please stop the following resources.
Check if the server name and the IP
address of the configuration
information are correctly set.
Stop the resource of which the
configuration has been changed.
Section II Command Reference
77
Chapter 2 EXPRESSCLUSTER X SingleServerSafe command reference
Backing up configuration data (clpcfctrl --pull)
clpcfctrl --pull
Backs up the configuration data.
Command line:
clpcfctrl --pull [-w] [-x <path>] [-p <portnumber>]
Backs up the configuration data to be used by the Builder.
Description
--pull
Option
Specify this option when performing backup.
This option cannot be omitted.
-x
Specify this option when backing up configuration
data in the specified directory.
-w
Save the configuration data with character encoding,
SJIS.
-p
Specifies the number of the port used to transfer
data.
When this option is omitted, the default value is
used. In general, it is not necessary to specify this
option.
Return Value
0
Success
Other than 0
Failure
Run this command as a user with Administrator privileges.
Notes
Error Message
Message
Cause/Solution
Log in as administrator.
Log on as a user with Administrator
privileges.
This command is already run.
This command has already been run.
invalid option.
The option is invalid. Check the option.
Invalid mode. Check if -push or -pull
option is specified.
Check if --pull is specified.
Failed to initialize the xml library.
Check if memory or OS resources are
sufficient.
Check if the memory or OS resources
are sufficient.
Failed to load the configuration file.
Check if memory or OS resources are
sufficient.
Failed to change the configuration file.
Check if memory or OS resources are
sufficient.
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
78
Applying and backing up configuration data (clpcfctrl command)
Message
Cause/Solution
Failed to load the all.pol file. Reinstall
the cluster.
Reinstall the EXPRESSCLUSTER
Server.
Failed to load the cfctrl.pol file.
Reinstall the cluster.
Reinstall the EXPRESSCLUSTER
Server.
Failed to get the install path. Reinstall
the cluster.
Reinstall the EXPRESSCLUSTER
Server.
Failed to initialize the trncl library.
Check if memory or OS resources are
sufficient
Check if the memory or OS resources
are sufficient.
Failed to connect to trnsv. Check if the
other server is active.
Accessing the server has failed. Check
if other server(s) has been started.
The directory "work" is not found.
Reinstall the cluster.
Reinstall the EXPRESSCLUSTER
Server.
Failed to make a working directory.
Check if the memory or OS resources
are sufficient.
The directory does not exist.
This is not a directory.
The source file does not exist.
The source file is a directory.
The source directory does not exist.
The source file is not a directory.
Failed to change the character code
set (EUC to SJIS).
Failed to change the character code
set (SJIS to EUC).
Failed to allocate memory.
Failed to change the directory.
Check if the memory or OS resources
are sufficient.
Failed to make a directory.
Failed to remove the directory.
Failed to remove the file.
Failed to open the file.
Failed to read he file.
Failed to write the file.
Failed to copy the file.
Failed to create the mutex.
Internal error. Check if memory or OS
resources are sufficient.
Section II Command Reference
79
Chapter 2 EXPRESSCLUSTER X SingleServerSafe command reference
Adjusting time-out
command)
clptoratio
temporarily
(clptoratio
Extends or displays the current timeout ratio.
Command line:
clptoratio
clptoratio
clptoratio
-r <ratio> -t <time>
-i
-s
Description
Temporarily extends the following timeout values:
• Monitor resource
• Alert synchronous service
• WebManager service
The current timeout ratio is displayed.
Option
-r ratio
-t time
-i
Remarks
If you specify “1,” you can restore the original ratio
as when using the -i option.
Specifies the extension period.
You can specify minutes for m, hours for h, and
days for d. The maximum period of time is 30 days.
Example:
2m, 3h, 4d
Sets back the modified timeout ratio.
Refers to the current timeout ratio.
-s
Return Value
Specifies the timeout ratio. Use 1 or larger integer.
The maximum timeout ratio is 10,000.
0
Success
Other than 0
Failure
When the server is shut down, the timeout ratio you specified becomes
ineffective.
With the -s option, you can only refer to the current timeout ratio. You
cannot see other information such as remaining time of extended period.
You can see the original timeout value by using the status display
command.
Monitor resource timeout# clpstat --mon monitor_resource_name
--detail
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
80
Adjusting time-out temporarily (clptoratio command)
Notes
This command must be executed by a user with the administrator
privilege.
The EXPRESSCLUSTER service must be running when you execute
this command.
When you set the timeout ratio, make sure to specify the extension
period. However, if you set “1” for the timeout ratio, you cannot specify
the extension period.
You cannot specify a combination such as “2m3h,” for the extension
period.
Examples
Example 1: Doubling the timeout ratio for three days
# clptoratio –r 2 –t 3d
Example 2: Setting back the timeout ratio to original
# clptoratio –i
Example 3: Referring to the current timeout ratio
# clptoratio –s
present toratio : 2
The current timeout ratio is set to 2.
Error Message
Message
Cause/Solution
Log in as administrator.
Log on as a user with Administrator
privileges.
Invalid configuration file. Create valid
cluster configuration data by using
the Builder.
Create valid cluster configuration data
by using the Builder.
invalid option.
Specify a valid option.
Specify a number in a valid range.
Specify a number within a valid range.
Specify a correct number.
Specify a valid number.
Scale factor must be specified by
integer value of 1 or more.
Specify 1 or larger integer for ratio.
Specify scale factor in a range less
than the maximum scale factor.
Specify a ratio that is not larger than
the maximum ratio.
Set the correct extension period.
Set a valid extension period.
ex) 2m, 3h, 4d
Set the extension period in a range
less than the maximum extension
period.
Set the extension period which does
not exceed the maximum extension
period.
Could not connect to the server.
Check if the cluster service is active.
Check that the EXPRESSCLUSTER
service is operating.
Server is not active. Check if the
cluster service is active.
Check that the EXPRESSCLUSTER
service is operating.
Connection was lost. Check if there
is a server where the cluster service
is stopped in the cluster.
Check if there is any server in the
cluster that the EXPRESSCLUSTER
service stopped.
Section II Command Reference
81
Chapter 2 EXPRESSCLUSTER X SingleServerSafe command reference
Invalid parameter.
The value specified as the command
parameter may be invalid.
Internal communication timeout has
occurred in the cluster server. If it
occurs frequently, set a longer
timeout.
A time-out occurred in the
EXPRESSCLUSTER internal
communication.
Processing failed on some servers.
Check the status of failed servers.
There is a server in which the
processing has failed.
If time-out keeps occurring, set the
internal communication time-out
longer.
Check the statuses of servers in the
cluster. Run the command with all
servers in the cluster activated.
Internal error. Check if memory or
OS resources are sufficient.
Check if the memory or OS resources
are sufficient.
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
82
Modifying the log level and size (clplogcf command)
Modifying the log level and size (clplogcf
command)
clplogcf
Modifies and displays log level and log output file size.
Command line:
clplogcf –t <type> -l <level> -s <size>
Description
Option
Modifies the settings of the log level and log output file size.
Displays the currently specified values.
-t
Specifies a module type whose settings will be
changed.
If both -l and -s are omitted, the information set to
the specified module will be displayed. See the list
of “Types that can be specified to the -t option” for
types which can be specified.
-l
Specifies a log level.
You can specify one of the following for a log level.
1, 2, 4, 8, 16, 32
You can see more detailed information as the log
level increases.
-s
Specifies the size of a file for log output.
The unit is byte.
Return Value
None
Displays the entire configuration information
currently set.
0
Success
Other than 0
Failure
Remarks
Each type of log output by EXPRESSCLUSTER X SingleServerSafe
uses two log files. Therefore, it is necessary to have twice the disk space
specified by -s.
Notes
Run this command as a user with Administrator privileges.
To run this command, the EXPRESSCLUSTER Event service must be
started.
Rebooting the server restores the settings to their pre-change values.
Section II Command Reference
83
Chapter 2 EXPRESSCLUSTER X SingleServerSafe command reference
Example 1: Modifying the pm log level
Examples
# clplogcf –t pm –l 8
Example 2: Seeing the pm log level and log file size
# clplogcf –t pm
TYPE, LEVEL, SIZE
pm, 8, 1000000
Example 3: Displaying the values currently configured
# clplogcf
TYPE, LEVEL, SIZE
trnsv, 4, 1000000
xml, 4, 1000000
logcf, 4, 1000000
Error Message
Message
Cause/Solution
Log in as administrator.
Log on as a user with Administrator
privileges.
invalid option.
The option is invalid. Check the option.
Failed to change configuration. Check
if the event service is running.
clpevent may not have been started.
invalid level
The specified level is invalid.
invalid size
The specified size is invalid.
Failed to initialize the xml library.
Check if memory or OS resources are
sufficient.
Check if the memory or OS resources
are sufficient.
Failed to print current configuration.
Check if the event service is running.
clpevent may not be started yet.
Types that can be specified for the -t option (y=yes, n=no)
Type
Module
Description
alert
clpaltinsert.exe
Alert
apicl
clpapicl.dll
API client library
apicl_rc
clpapicl.dll
API client library
apisv
clpapisv.dll
API server
appli
clpappli.dll
Application resource
appliw
clpappliw.dll
Application monitor resource
armdrive
armdrive.exe
Drive letter setting command
bwctrl
clpbwctrl.exe
Cluster activation synchronization wait
processing control command
cfctrl
clpcfctrl.exe
Cluster generation, cluster information and
backup command
cl
clpcl.exe
Cluster startup and stop command
clpdnld
clpdnld.exe
Downloader
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
84
Modifying the log level and size (clplogcf command)
Type
Module
Description
clpgetsvcstat
clptrnsv.exe
Transaction server
clpshmstat
clpshmstat.dll
Node status management library
clsv
clpclsv.dll
Client server
commcl
clpcommcl.dll
Common communication client library
cpufreq
clpcpufreq.exe
CPU frequency control command
diskperf
clpdiskperf.dll
Disk performance log library
diskutil
clpdiskutil.dll
Mirror disk/disk shared library
diskw
clpdiskw.dll
Disk RW monitor resource
down
clpdown.exe
Server shutdown command
event
clpevent.dll
Event log
exping
clpexpng.dll
PING execution management
genw
genw.dll
Custom monitor resource
grp
clpgrp.exe
Group startup, stop, move, and migration
command
hblog
clplanhb.dll
Kernel-mode LAN heartbeat resource
healthchk
clphealthchk.exe
Process health check command
ipw
clpipw.dll
IP monitor resource
lankhb
clplanhb.dll
Kernel-mode LAN heartbeat resource
lcns
clplcns.dll
License library
ledctrl
clpledctrl.exe
Chassis identify control command
logc
clplogcc.exe
Log collection library
logcc
clplogcc.exe
Collect logs command
logcf
clplogcf.exe
Log level and size modification command
logcmd
clplogcmd.exe
Alert producing command
mail
clpmail.exe
Mail Notification
monctrl
clpmonctrl.exe
Monitor resource control command
mgmtagt
clpmgtmib.dll
Library for SNMP Service
miiw
clpmiiw.dll
NIC Link Up/Down monitor resource
monctrl
clpmonctrl.exe
Monitor resource control command
mrw
clpmrw.dll
Message receive monitor resource
mtw
clpmtw.dll
Multi target monitor resource
nm
clpnm.exe
Node map management
oldapi
clpoldapi.exe
Compatible API
oldapi_cnf
clpoldapi.exe
Compatible API
oldapi_evt
clpoldapi.exe
Compatible API
oldapi_if
clpoldapi.exe
Compatible API
oldapi_sts
clpoldapi.exe
Compatible API
pm
clppm
Process management
pmsvc
clppmsvc.exe
Process management
Section II Command Reference
85
Chapter 2 EXPRESSCLUSTER X SingleServerSafe command reference
Type
Module
Description
psw
clppsw.dll
Process name monitor resource
ptun
clpptun.dll
Parameter tuning
ptunlib
clpptun.dll
Parameter tuning
rc
clprc.exe
Group and group resource management
rc_ex
clprc.exe
Group and group resource management
regctrl
clpregctrl.exe
Reboot count control command
resdllc
clpresdllc.dll
Resource control library
rm
clprm.dll
Monitor management
script
clpscript.dll
Script resource
scrpc
clpscrpc.exe
Script
scrpl
clpscrpl.ece
Script
sem
clpsem.dll
Semaphore library
service
clpservice.dll
Service resource
servicew
clpservicew.dll
Service monitor resource
shmcm
clpshmcm.dll
Shared memory library
shmevt
clpshmevt.dll
Event library
shmnm
clpshmnm.dll
Shared memory library
shmrm
clpshmrm.dll
Shared memory library
snmpmgr
clpsnmpmgr.dll
SNMP trap reception library
starup
clpstartup.exe
Startup
stat
clpstat.exe
Status display command
stdn
clpstdn.exe
Cluster shutdown command
toratio
clptoratio.exe
Time-out ratio modification command
trncl
clptrncl.dll
Transaction library
trap
claptrap.exe
SNMP trap command
trnreq
clptrnreq.exe
Inter-cluster processing request command
rexec
clprexec.exe
External monitoring link processing
request command
trnsv
clptrnsv.exe
Transaction server
userw
clpuserw.dll
User space monitor resource
webalert
clpaltd.exe
Alert synchronization
webmgr
clpwebmc.exe
WebManager
xml
xlpxml.dll
XML library
vm
clpvm.dll
VM resource
vmw
clpvmw.dll
VM monitor resource
vmctrl
clpvmctrl.dll
VMCtrl library
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
86
Modifying the log level and size (clplogcf command)
Default log levels and log file sizes
Type
Level
Size (byte)
alert
4
1000000
apicl
4
5000000
apicl_rc
4
5000000
apisv
4
5000000
appli
4
1000000
appliw
4
1000000
armdrive
4
1000000
bwctrl
4
1000000
cfctrl
4
1000000
cl
4
1000000
clpdnld
4
1000000
clpgetsvcstat
4
1000000
clpshmstat
4
1000000
clsv
4
1000000
commcl
4
80000000
cpufreq
4
1000000
diskperf
8
2000000
diskutil
4
1000000
diskw
4
1000000
down
4
1000000
event
4
1000000
exping
4
1000000
genw
4
1000000
grp
4
1000000
hblog
4
1000000
healthchk
4
1000000
ipw
4
1000000
lankhb
4
1000000
lcns
4
1000000
logc
4
1000000
logcc
4
1000000
logcf
4
1000000
logcmd
4
1000000
mail
4
1000000
mgmtagt
4
1000000
miiw
4
1000000
monctrl
4
1000000
Section II Command Reference
87
Chapter 2 EXPRESSCLUSTER X SingleServerSafe command reference
Type
Level
Size (byte)
mrw
4
1000000
mtw
4
1000000
nm
4
2000000
oldapi
4
1000000
oldapi_cnf
4
1000000
oldapi_evt
4
1000000
oldapi_if
4
1000000
oldapi_sts
4
1000000
pm
4
1000000
pmsvc
4
2000000
psw
4
1000000
ptun
4
1000000
ptunlib
4
1000000
rc
4
5000000
rc_ex
4
5000000
regctrl
4
1000000
resdllc
4
2000000
rm
4
5000000
script
4
1000000
scrpc
4
1000000
scrpl
4
1000000
sem
4
1000000
service
4
1000000
servicew
4
1000000
shmcm
4
1000000
shmevt
4
1000000
shmnm
4
1000000
shmrm
4
1000000
snmpmgr
4
1000000
startup
4
1000000
stat
4
1000000
stdn
4
1000000
toratio
4
1000000
trap
4
1000000
trncl
4
2000000
trnsv
4
2000000
trnreq
4
1000000
userw
4
1000000
rexec
4
1000000
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
88
Modifying the log level and size (clplogcf command)
Type
Level
Size (byte)
webalert
4
1000000
webmgr
4
1000000
xml
4
1000000
vm
4
1000000
vmw
4
1000000
vmctrl
4
1000000
Total
190000000 * 2
Monitoring Agent Types that can be specified for the -t option
Type
Module
Description
db2w
clp_db2w.dll
DB2 Monitor (Database Agent)
ftpw
clp_ftpw.dll
FTP Monitor (Internet Server Agent)
httpw
clp_httpw.dll
HTTP Monitor (Internet Server Agent)
imap4w
clp_imap4w.dll
IMAP4 Monitor (Internet Server Agent)
jra
clpjrasvc.exe
JVM monitor resource (Java Resource Agent)
jraw
clpjraw.dll
JVM monitor resource (Java Resource Agent)
odbcw
clp_odbcw.dll
ODBC Monitor (Database Agent)
oscw
clposcw.dll
OracleAS Monitor (Application Server Agent)
ossw
clpossw.dll
Oracle Monitor (Database Agent)
otxw
clposcw.dll
VB Corp CL Monitor (Anti-Virus Agent)
ossw
clpossw.dll
VB Corp SV Monitor (Anti-Virus Agent)
otxw
clp_otxw.dll
WebOTX Monitor (Application Server Agent)
smtpw
clp_smtpw.dll
POP3 Monitor (Internet Server Agent)
psqlw
clp_psqlw.dll
PostgreSQL Monitor (Database Agent)
tuxw
clp_tuxw.dll
SMTP Monitor (Internet Server Agent)
wasw
clp_wasw.dll
SQL Server Monitor (Database Agent)
sra
clpsraserviceproc.exe
System monitor resource (System Resource Agent)
sraw
clpsraw.dll
System monitor resource (System Resource Agent)
tuxw
clp_tuxw.dll
Tuxedo Monitor (Application Server Agent)
wasw
clp_wasw.dll
Websphere Monitor (Application Server Agent)
wlsw
clp_wlsw.dll
Weblogic Monitor (Application Server Agent)
Monitoring Agent Default Values of Log Level/Log File Size
Type
Level
Size (byte)
db2w
4
1000000
ftpw
4
1000000
httpw
4
1000000
imap4w
4
1000000
Section II Command Reference
89
Chapter 2 EXPRESSCLUSTER X SingleServerSafe command reference
Type
Level
Size (byte)
jra
4
1000000
jraw
4
1000000
odbcw
4
1000000
oracleasw
4
1000000
oraclew
4
1000000
oscw
4
1000000
ossw
4
1000000
otxw
4
1000000
pop3w
4
1000000
psqlw
4
1000000
smtpw
4
1000000
sqlserverw
4
1000000
sra
8
1000000
sraw
4
1000000
tuxw
4
1000000
wasw
4
1000000
wlsw
4
1000000
Total
21000000 * 2
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
90
Registering the license (clplcnsc command)
Registering the license (clplcnsc command)
clplcnsc
the clplcnsc command registers the license.
Command line:
clplcnsc -i < licensefile >
Description
Registers the full or trial version license of this product.
Option
-i
Registers the license provided by the specified
license file.
Return Value
0
Success
Other than 0
Failure
Notes
Run this command as a user with Administrator privileges.
This command cannot register the license by specifying its information.
Therefore, when registering the license by using this command, be sure
to specify the license file.
Examples
Example : When registering the license by specifying its license
file(c:\tmp\licensefile)
# clplcnsc -i c:\tmp\licensefile
Section II Command Reference
91
Chapter 2 EXPRESSCLUSTER X SingleServerSafe command reference
Error Message
Message
Cause/Solution
Log in as administrator.
Log on as a user with Administrator
privileges.
Invalid parameter.
Specify a valid option.
License file is not found. filename=%s
The specified license file is not found.
Specify a correct license file.
License information invalid.
The specified license file is invalid.
Specify a correct license file.
License registration failure.
The license registration failed.
Check if the memory or OS resources
are sufficient.
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
92
Outputting messages (clplogcmd command)
Outputting messages (clplogcmd command)
clplogcmd
Registers the specified text into alert.
Command line:
clplogcmd -m message [-i ID] [-l level]
Note:
It is not necessary to run this command during normal setup or operation. You need to write the
command in the script resource script.
Description
Write this command in the script resource script to output messages to
any destination.
Messages are produced in the following format:
[ID] message
Option
-m message
Specifies text to output for message. This option
cannot be omitted. The maximum size of message
is 498 bytes.
You may use alphabets, numbers, and symbols.
-i ID
Specify message ID.
This parameter can be omitted. The default value
1 is set for the ID when the parameter is omitted.
-l level
Level of alert to output.
Select a level of alert output from ERR, WARN,
or INFO. The icon on the alert view of the
WebManager is determined according to the level
you select here.
This parameter can be omitted. The default value
INFO is set to level when the parameter is
omitted.
For details, see "Checking alerts using the
WebManager" in Chapter 1, "Functions of the
WebManager."
Return Value
Notes
0
Success
Other than 0
Failure
This command must be executed by a user with the administrator
privilege.
The specification of the –i option is different from that of the Linux
version. In the Windows version, the event ID displayed in an alert cannot
be changed.
Section II Command Reference
93
Chapter 2 EXPRESSCLUSTER X SingleServerSafe command reference
Examples of command execution
Example 1: When specifying only message
When the following is written in the script resource script, the text is output to the alert.
clplogcmd -m test1
The following alert is displayed on the alert view of the WebManager:
Example 2: When specifying message, message ID, and level:
When the following is written in the script resource script, the text is output to the alert.
clplogcmd -m test2 -i 100 -l ERR
The following alert is displayed on the alert view of the WebManager:
* Notes on using symbols in text:
The symbols below must be enclosed in double quotes (“ ”):
& | < >
(For example, if you specify "&" in the message, & is output.)
The symbols below must have a backslash \ at the beginning:
\
(For example, if you specify \\ in the message, \ is output.)

When there is a space in text, it must be placed in enclosed in double quotes (“ ”).
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
94
Controlling monitor resources (clpmonctrl command)
Controlling monitor resources (clpmonctrl
command)
clpmonctrl
Controls the monitor resources.
Command line:
clpmonctrl -s
clpmonctrl -r
clpmonctrl -c
clpmonctrl -v
clpmonctrl -e
clpmonctrl -n
[-m resource name ...] [-w wait time]
[-m resource name ...] [-w wait time]
[-m resource name ...]
[-m resource name ...]
-m resource name
[-m resource name]
Description
Suspends or resumes monitor resources.
Option
-s, --suspend
Suspends monitoring
-r, --resume
Resumes monitoring
-c, --clear
-v, --view
Initializes the recovery operation count.
-e, --error
-n, --normal
Enables dummy failure. Be sure to specify a monitor
resource name with the -m option.
Disables dummy failure. When a monitor resource name is
specified with the -m option, the function is disabled only
for the resource. When the -m option is omitted, the
function is disabled for all monitor resources.
-m, --monitor
Specifies one or more monitor resources to be controlled.
Displays the recovery operation count.
This option can be omitted. All monitor resources are
controlled when the option is omitted.
-w, --wait
Waits for control monitoring on a monitor resource basis.
(in seconds)
This option can be omitted. The default value 5 is set when
the option is omitted.
Section II Command Reference
95
Chapter 2 EXPRESSCLUSTER X SingleServerSafe command reference
Return
Value
0
Completed successfully.
1
Privilege for execution is invalid.
2
The option is invalid.
3
Initialization error
4
The configuration data is invalid.
5
Monitor resource is not registered.
6
The specified monitor resource is invalid.
10
EXPRESSCLUSTER is not running.
11
The EXPRESSCLUSTER service is suspended
90
Monitoring control wait timeout
128
Duplicated activation
255
Other internal error
Remarks
If you attempt to suspend a monitor resource that is already suspended or
attempt to resume one that is already resumed, this command terminates
successfully without changing the status of the monitor resource.
Notes
Run this command as a user with the administrator privilege.
Check the status of monitor resource by using the status display command
or WebManager.
Before you run this command, use the clpstat command or WebManager to
verify that the status of monitor resources is in either “Online” or
“Suspend.”
In the case of a monitor resource of which monitor timing is “Active”, if a
target resource stops temporarily in the active status, and then the target
resource or the group which the target resource belongs to is activated, the
monitor resource which has been stopped temporarily cannot detect an
error. This is because the monitor resource does not start monitoring.
The following are examples of the case described above:
1. Stops an application monitor that is monitoring application resource
temporarily.
2. Reactivate the application resource or the group that the application
resource belongs to.
This reactivation procedure applies both manual and automatic when a
monitor resource detects an error and reactivates an application by the
recovery operation.
If you execute clpmonctrl command with the -v option, “FinalAction
Count” is script execution count before final action for following setting.
- The Execute Script before Final Action check box is selected.
- Final Action is No operation.
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
96
Controlling monitor resources (clpmonctrl command)
Error Messages
Message
Causes/Solution
Command succeeded.
The command ran successfully.
You are not authorized to run the
command. Log in as Administrator.
You are not authorized to run this command. Log in as
a user with Administrator privileges.
Initialization error. Check if memory or
OS resources are sufficient.
Check if the memory or OS resource is sufficient.
Invalid cluster configuration data.
Check it by using the Builder.
The cluster configuration data is invalid. Check the
cluster configuration data by using the Builder.
Monitor resource is not registered.
The monitor resource is not registered.
Specified monitor resource is not
registered. Check the cluster
configuration information by using the
Builder.
The specified monitor resource is not registered.
The cluster has been stopped. Check
the active status of the cluster service
by using the command such as ps
command.
The cluster has been stopped.
The cluster has been suspended. The
cluster service has been suspended.
Check activation status of the cluster
service by using a command such as
the ps command.
The EXPRESSCLUSTER service has been
suspended. Check the activation status of the
EXPRESSCLUSTER service by using a command
such as ps command.
Waiting for synchronization of the
cluster. The cluster is waiting for
synchronization. Wait for a while and try
again.
Synchronization of the cluster is awaited.
Monitor %1 was unregistered, ignored.
The specified monitor resources %1is
not registered, but continues
processing. Check the cluster
configuration data by using the
Builder. %1: monitor resource name
There is an unregistered monitor resource in the
specified monitor resources, but it is ignored and the
process is continued
Check the cluster configuration data by using the
Builder.
Check the activation status of the
EXPRESSCLUSTER service by using the ps
command.
Try again after synchronization of the cluster is
completed.
Check the cluster configuration data by using the
Builder.
%1: Monitor resource name
The command is already executed.
Check the execution state by using the
"ps" command or some other
command.
The command has already been run. Check the status
by using the ps command.
Internal error. Check if memory or OS
resources are sufficient.
Check if the memory or OS resource is sufficient.
Monitor resource types that can be specified for the -m option
Type
Suspending/Resume
Reset Recovery Count
Dummy Failure Possibility
appliw
O
O
O
diskw
O
O
O
ipw
O
O
O
miiw
O
O
O
mtw
O
O
O
servicew
O
O
O
genw
O
O
O
Section II Command Reference
97
Chapter 2 EXPRESSCLUSTER X SingleServerSafe command reference
Type
Suspending/Resume
Reset Recovery Count
Dummy Failure Possibility
vmw
O
O

mrw
O
O

db2w
O
O
O
ftpw
O
O
O
httpw
O
O
O
imap4w
O
O
O
odbcw
O
O
O
oraclew
O
O
O
oracleasw
O
O
O
oscw
O
O
O
ossw
O
O
O
pop3w
O
O
O
psqlw
O
O
O
smtpw
O
O
O
sqlserverw
O
O
O
tuxw
O
O
O
wasw
O
O
O
wlsw
O
O
O
otxw
O
O
O
jraw
O
O
O
sraw
O
O
O
userw
O
O
O
psw
O
O
O
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
98
Controlling group resources (clprsc command)
Controlling group resources (clprsc command)
clprsc
Controls group resources
Command line:
clprsc -s resource_name [-f] [--apito timeout]
clprsc -t resource_name [-f] [--apito timeout]
Description
This command starts and stops group resources.
Option
-s
Starts group resources.
-t
Stops group resources.
-f
When the group resource is running, all group resources
that the specified group resource depends start up.
--apito
timeout
When the group resource is not running, all group
resources that the specified group resource depends stop.
Specify the time in seconds to wait for group resources to
be started or stopped (internal communication timeout). A
value between 1 to 9999 can be specified.
When the --apito option is not specified, the command
waits according to the value set for the internal
communication timeout in the cluster property.
Return
Value
0
Completed successfully.
Other than 0
Terminated due to a failure.
Notes
This command must be executed by a user with the administrator privilege.
Check the status of the group resources by using the status display
command or the WebManager.
Error Messages
Message
Causes/Solution
Log in as Administrator.
Run this command as a user with Administrator
privileges.
Invalid cluster configuration data. Check it by
using the Builder.
The cluster construction information is not correct.
Check the cluster construction information by
Builder.
Invalid option.
Specify a correct option.
Could not connect server. Check if the cluster
service is active.
Check if the EXPRESSCLUSTER is activated.
Invalid server status. Check if the cluster service
is active.
Check if the EXPRESSCLUSTER is activated.
Section II Command Reference
99
Chapter 2 EXPRESSCLUSTER X SingleServerSafe command reference
Message
Causes/Solution
Server is not active. Check if the cluster service
is active.
Check if the EXPRESSCLUSTER is activated.
Invalid server name. Specify a valid server name
in the cluster.
Specify a correct server name in the cluster.
Connection was lost. Check if there is a server
where the cluster service is stopped in the
cluster.
Check if there is any server with
EXPRESSCLUSTER service stopped in the
cluster.
Internal communication timeout has occurred in
the cluster server. If it occurs frequently, set the
longer timeout.
Timeout has occurred in internal communication
in the EXPRESSCLUSTER.
Set the internal communication timeout longer if
this error occurs frequently.
The group resource is busy. Try again later.
Because the group resource is in the process of
starting or stopping, wait for a while and try again.
An error occurred on group resource. Check the
status of group resource.
Check the group resource status by using the
WebManager or the clpstat command.
Could not start the group resource. Try it again
after the other server is started, or after the Wait
Synchronization time is timed out.
Wait till the other server starts or the wait time
times out, then start the group resources.
No operable group resource exists in the server.
Check there is a processable group resource on
the specified server.
The group resource has already been started on
the local server.
Check the group resource status by using the
WebManager or clpstat command.
The group resource has already been started on
the other server. To start the group resource on
the local server, stop the group resource.
Check the group resource status by using the
WebManager or clpstat command.
The group resource has already been stopped.
Check the group resource status by using the
WebManager or clpstat command.
Failed to start group resource. Check the status
of group resource.
Check the group resource status by using the
WebManager or clpstat command.
Failed to stop resource. Check the status of
group resource.
Check the group resource status by using the
WebManager or clpstat command.
Depending resource is not offline. Check the
status of resource.
Because the status of the depended group
resource is not offline, the group resource cannot
be stopped. Stop the depended group resource or
specify the -f option.
Depending resource is not online. Check the
status of resource.
Because the status of the depended group is not
online, the group resource cannot be started.
Start the depended group resource or specify the
-f option.
Invalid group resource name. Specify a valid
group resource name in the cluster.
The group resource is not registered.
Server is isolated.
The server is suspended. (Rebooting after down)
Internal error. Check if memory or OS resources
are sufficient.
Not enough memory space or OS resource.
Check if there is enough space.
Server is not in a condition to start resource.
Critical monitor error is detected.
Check the status of the server.
Stop the group to start the group resources on the
local server.
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
100
Controlling CPU frequency (clpcpufreq command)
Controlling
command)
CPU
clpcpufreq
frequency
(clpcpufreq
Controls CPU frequency.
Command line:
clpcpufreq --high
clpcpufreq --low
clpcpufreq -i
clpcpufreq -s
Description
This command enables or disables power-saving mode by CPU frequency
control.
Option
--high
Sets the highest CPU frequency.
--low
Sets the lowest CPU frequency to switch to the
power-saving mode.
-i
Passes the CPU frequency control to EXPRESSCLUSTER
X SingleServerSafe.
-s
Displays the current CPU frequency level.
Return Value
high
The CPU frequency is at its highest.
low
The CPU frequency has been decreased because
the CPU is in the power-saving mode.
0
Completed successfully.
Other than 0
Terminated due to a failure.
Remarks
If the Use CPU Frequency Control check box is not selected in the
power saving settings in Cluster Properties, this command results in an
error.
Notes
This command must be executed by a user with the administrator
privilege.
When you use CPU frequency control, it is required that frequency is
changeable in the BIOS settings, and that the CPU supports frequency
control by Windows OS power management function.
Error Messages
Message
Cause/Solution
Log in as Administrator.
Log in as a user with Administrator privileges.
Section II Command Reference
101
Chapter 2 EXPRESSCLUSTER X SingleServerSafe command reference
Message
Cause/Solution
This command is already run.
This command has already been run.
Invalid option.
This option is invalid. Check the option.
Invalid mode.
Check if --high or --low or -i or -s option is
specified.
Failed to initialize the xml library.
Check if memory or OS resources are sufficient.
Check if either of the --high, --low, -I or -s
option is specified.
Failed to change CPU frequency settings.
Check the BIOS settings and the OS settings.
Check to see if the memory or OS resource is
sufficient.
Check if the cluster is started.
Check if the setting is configured so that CPU
frequency control is used.
Failed to acquire CPU frequency settings.
Check the BIOS settings and the OS settings.
Check if the cluster is started.
Check if the setting is configured so that CPU
frequency control is used.
Failed to create the mutex.
Check if the memory or OS resource is sufficient.
Internal error. Check if memory or OS resources
are sufficient.
Check if the memory or OS resource is sufficient.
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
102
Requesting processing to cluster servers (clprexec command)
Requesting processing to cluster servers
(clprexec command)
Issues a processing execution
EXPRESSCLUSTER is installed.
clprexec
request
to
another
server
on
which
Command line:
clprexec --script script_file -h IP [-p port_number] [-w timeout] [-o
logfile_path]
clprexec --notice [mrw_name] -h IP [-k category[.keyword]] [-p
port_number] [-w timeout] [-o logfile_path]
clprexec --clear [mrw_name] -h IP [-k category[.keyword]] [-p
port_number] [-w timeout] [-o logfile_path]
Description
This command is an expansion of the existing clptrnreq command and has additional
functions such as issuing a processing request (error message) from the external
monitor to the EXPRESSCLUSTER server.
Option
--script script_name
Requests script execution.
For script_name, specify the file name of the script to
execute (such as a shell script or executable file).
The script must be created in the work/trnreq folder, which
is in the folder where EXPRESSCLUSTER is installed, on
each server specified using -h.
--notice
Sends an error message to the EXPRESSCLUSTER
server.
Specify a message reception monitor resource name for
mrw_name.
When not specifying the monitor resource name, specify
the monitor type and monitor target of the message
reception monitor resource by using the -k option.
--clear
Requests changing the status of the message reception
monitor resource from "Abnormal" to "Normal."
Specify a message reception monitor resource name for
mrw_name.
When not specifying the monitor resource name, specify
the monitor type and monitor target of the message
reception monitor resource by using the -k option.
-h IP Address
Specify the IP addresses of EXPRESSCLUSTER servers
that receive the processing request.
Up to 32 IP addresses can be specified by separating them
with commas.
* If this option is omitted, the processing request is issued
to the local server.
-k category[.keyword]
For category, specify the category specified for the
message receive monitor when the --notice or --clear
option is specified.
To specify the keyword of the message receive monitor
Section II Command Reference
103
Chapter 2 EXPRESSCLUSTER X SingleServerSafe command reference
resource, specify them by separating them with period
after category.
-p port_number
Specify the port number.
For port_number, specify the data transfer port number
specified for the server that receives the processing
request.
The default value, 29002, is used if this option is omitted.
-o logfile_path
For logfile_path, specify the file path along which the
detailed log of this command is output.
The file contains the log of one command execution.
* If this option is not specified on a server where
EXPRESSCLUSTER is not installed, the log is always
output to the standard output.
-w timeout
Specify the command timeout time. The default, 180
seconds, is used if this option is not specified.
A value from 5 to 999 can be specified.
Return Value
Notes
0
Completed successfully.
Other than 0
Terminated due to a failure.
When issuing error messages by using the clprexec command, the message reception
monitor resources for which executing an action when an error occurs is specified in
EXPRESSCLUSTER server must be registered and started.
The command version is output to the standard output when the command is
executed.
The command checks whether the character string specified for the --script option
includes "\", "/" or ".." because a relative path must not be specified.(This is because
a relative path cannot be specified.)
The server that has the IP address specified for the -h option must satisfy the
following conditions:
= EXPRESSCLUSTER X3.0 or later must be installed.
= EXPRESSCLUSTER must be running.
= mrw must be set up and running.
Examples
Example 1: This example shows how to issue a request to execute the script
(script1.bat) on EXPRESSCLUSTER server 1 (10.0.0.1):
# clprexec --script script1.bat -h 10.0.0.1
Example 2: This example shows how to issue an error message to
EXPRESSCLUSTER server 1 (10.0.0.1):
* mrw1 set, category: earthquake, keyword: scale3
This example shows how to specify a message reception monitor resource name:
# clprexec --notice mrw1 -h 10.0.0.1 -w 30 -o
/tmp/clprexec/clprexec.log
- This example shows how to specify the category and keyword specified for the
message reception monitor resource:
# clprexec --notice -h 10.0.0.1 -k earthquake.scale3 -w
30 -o /tmp/clprexec/clprexec.log
Example 3: This example shows how to issue a request to change the monitor
status of mrw1 to EXPRESSCLUSTER server 1 (10.0.0.1):
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
104
Requesting processing to cluster servers (clprexec command)
* mrw1 set, category: earthquake, keyword: scale3
- This example shows how to specify a message reception monitor resource
name:
# clprexec --clear mrw1 -h 10.0.0.1
- This example shows how to specify the category and keyword specified for the
message reception monitor resource:
# clprexec --clear -h 10.0.0.1 -k earthquake.scale3
Error Messages
Message
Cause/solution
Success
Invalid option.
Could not connect to the data transfer servers.
Check if the servers have started up.
Check the command argument.
Check whether the specified IP address is correct
and whether the server that has the IP address is
running.
Check whether the specified IP address is correct
and whether the server that has the IP address is
running.
Check whether the processing is complete on the
server that has the specified IP address.
This command might already be running.
Could not connect to all data transfer server.
Command timeout.
All servers are busy. Check if this command is
already run.
Group(%s) is offline.
Group that specified resource(%s) belongs to is
offline.
Specified script(%s) does not exist.
Specified resource(%s) is not exist.
Specified resource(Category:%s, Keyword:%s)
is not exist.
Specified group(%s) does not exist.
This server is not permitted to execute clprexec.
%s failed in execute.
Check the processing result on the server that
received the request.
Check the group status.
Check if the specified script exist.
Check the resource name or monitor resource
name.
Check the resource name or monitor resource
name.
Check the group name.
Check whether the IP address of the server that
executes the command is registered in the list of
client IP addresses that are not allowed to
connect to the WebManager.
Check the status of the EXPRESSCLUSTER
server that received the request.
Section II Command Reference
105
Chapter 2 EXPRESSCLUSTER X SingleServerSafe command reference
Controlling reboot count (clpregctrl command)
clpregctrl
Controls reboot count limitation.
Command line:
clpregctrl --get
clpregctrl -g
clpregctrl --clear -t type -r registry
clpregctrl -c -t type -r registry
Description
Displays or initializes the reboot count on a server.
Option
-g, --get
Displays reboot count information.
-c, --clear
Initializes reboot count.
-t type
Specifies the type to initialize the reboot count. The type that can
be specified is rc or rm
-r registry
Specifies the registry name. The registry name that can be
specified is haltcount.
0
Completed successfully.
1
Privilege for execution is invalid.
2
Duplicated activation
3
The option is invalid.
4
The configuration data is invalid.
10 to 17
Internal error
20 to 22
Obtaining reboot count information has failed.
90
Allocating memory has failed.
Return Value
Notes
This command must be executed by a user with the administrator privilege.
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
106
Controlling reboot count (clpregctrl command)
Examples
Display of reboot count information
# clpregctrl –g
******************************
------------------------type
: rc
registry : haltcount
comment : halt count
kind
: int
value
: 0
default
: 0
------------------------type
: rm
registry : haltcount
comment : halt count
kind
: int
value
: 3
default
: 0
******************************
success.(code:0)
#
The reboot count is initialized in the following examples.
Example 1: When initializing the count of reboots caused by a group resource
error:
# clpregctrl -c -t rc -r haltcount
success.(code:0)
#
Example 2: When initializing the count of reboots caused by a monitor resource
error:
# clpregctrl -c -t rm -r haltcount
success.(code:0)
#
Error Messages
Message
Cause/solution
Command succeeded.
The command ran successfully.
Log in as Administrator.
You are not authorized to run this
command. Run this command as a user
with Administrator privileges.
The command is already executed.
The command is already running.
Invalid option.
Specify a valid option.
Internal error. Check if memory or OS
resources are sufficient.
Not enough memory space or OS
resource.
Section II Command Reference
107
Chapter 2 EXPRESSCLUSTER X SingleServerSafe command reference
Estimating the amount of resource usage
(clpprer command)
Estimates the future value from changes in the resource usage amount
written to the input file and outputs the result to a file. It can also be used
to check the result of threshold judgment for estimated data.
clpprer
Command line:
clpprer –i <inputfile > -o <outputfile > [-p <number >] [-t <number
> [-l]]
Description
Estimates the future value from the tendency of the given resource use amount data.
Option
-i <inputfile>
The clpprer command specifies the resource data for
which a future value is to be obtained.
-o <outputfile>
Specifies the name of the file to which the estimate
result is output.
Specifies the number of estimate data items. If
omitted, 30 items of estimate data are obtained.
Specifies the threshold to be compared with the
estimate data.
Valid only when the threshold is set with the -t
option.Judges the status to be an error when the data
value is less than the threshold.
-p <number>
-t <number>
-l
Return Value
0
Normal end without threshold judgment
1
Error occurrence
2
As a result of threshold judgment, the input data is
determined to have exceeded the threshold.
3
As a result of threshold judgment, the estimate data
is determined to have exceeded the threshold.
4
As a result of threshold judgment, the data is
determined to have not exceeded the threshold.
5
If the number of data items to be analyzed is less
than the recommended number of data items to be
analyzed (120), the input data is determined to have
exceeded the threshold as a result of threshold
judgment.
6
If the number of data items to be analyzed is less
than the recommended number of data items to be
analyzed (120), the estimate data is determined to
have exceeded the threshold as a result of threshold
judgment.
7
If the number of data items to be analyzed is less
than the recommended number of data items to be
analyzed (120), the data is determined to have not
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
108
Estimating the amount of resource usage (clpprer command)
exceeded the threshold as a result of threshold
judgment.
Notes
This command can be used only when the license for the system monitor
resource (System Resource Agent) is registered. (If the license is
registered, you do not need to configure system monitor resources for the
cluster configuration.)
The maximum number of input data items of the resource data file
specified with the -i option is 500. A certain number of input data items
are required to estimate the amount of resource usage. However, if the
number of input data items is large, it takes a considerable amount of time
to perform the analysis. So, it is recommended that the number of input
data items be restricted to about 120. Moreover, the maximum number of
output data items that can be specified in option -p is 500.
If the time data for the input file is not arranged in ascending order, the
estimate will not be appropriate. In the input file, therefore, set the time
data arranged in ascending order.
Input file
The input file format is explained below. You need to have an input file,
written in the following format, for the resource usage amount for which
you want to estimate a result.
The input file format is CSV. One piece of data is coded in the form of
date and time, numeric value.
Moreover, the data and time format is YYYY/MM/DD hh:mm:ss.
File example
2012/06/14 10:00:00,10.0
2012/06/14 10:01:00,10.5
2012/06/14 10:02:00,11.0
Examples
The estimation of the future value is explained using a simple example.
When an error is detected in the input data:
If the latest value of the input data exceeds the threshold, an error is
assumed and a return value of 2 is returned. If the number of input data
items is less than the recommended value (=120), a return value of 5 is
returned.
Section II Command Reference
109
Chapter 2 EXPRESSCLUSTER X SingleServerSafe command reference
Threshold
Input data
Estimate data
Figure: Error detection in the input data
When an error is detected in the estimate data:
If the estimate data exceeds the threshold, an error is assumed and a return
value of 3 is returned. If the number of input data items is less than the
recommended value (=120), a return value of 6 is returned.
Threshold
Input data
Estimate data
Figure: Error detection in the estimate data
When no threshold error is detected:
If neither the input data nor the estimate data exceeds the threshold, a
return value of 4 is returned. If the number of input data items is less than
the recommended value (=120), a return value of 7 is returned.
Threshold
Input data
Estimate data
Figure: When no threshold error is detected
When the -l option is used:
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
110
Estimating the amount of resource usage (clpprer command)
If the -l option is used, an error is assumed when the data is less than the
threshold.
Threshold
Input data
Estimate data
Figure: Use of the -l option
Examples
If you use a file written in the specified format and run the clpprer
command, you can output the estimate result to a file and check it.
nput file test.csv
2012/06/14 10:00:00,10.0
2012/06/14 10:01:00,10.5
2012/06/14 10:02:00,11.0
# clpprer –i test.csv –o result.csv
Output result result.csv
2012/06/14 10:03:00,11.5
2012/06/14 10:04:00,12.0
2012/06/14 10:05:00,12.5
2012/06/14 10:06:00,13.0
2012/06/14 10:07:00,13.5
:
If you set a threshold for option, you can check the result of threshold
judgment for estimate data at the command prompt.
# clpprer –i test.csv –o result.csv –t 12.5
Execution result
Detect over threshold. datetime = 2012/06/14
10:06:00, data = 13.00, threshold = 12.5
Section II Command Reference
111
Chapter 2 EXPRESSCLUSTER X SingleServerSafe command reference
Error Messages
Message
Causes/Solution
Normal state.
As a result of threshold judgment, no data
exceeding the threshold is detected.
Detect over threshold. datetime = %s, data
= %s, threshold = %s
As a result of threshold judgment, data
exceeding the threshold is detected.
Detect under threshold. datetime = %s, data
= %s, threshold = %s
As a result of threshold judgment with the -l
option, data less than the threshold is detected.
License is nothing.
The license for the valid System Resource
Agent is not registered. Check to see the
license.
Inputfile is none.
The specified input data file does not exist.
Inputfile length error.
The path for the specified input data file is too
long. Specify no more than 1023 bytes.
Output directory does not exist.
The directory specified with the output file does
not exist. Check whether the specified directory
exists.
Outputfile length error.
The path for the specified output file is too long.
Specify no more than 1023 bytes.
Invalid number of -p.
The value specified in the -p option is invalid.
Invalid number of -t.
The value specified in the -t option is invalid.
Not analyze under threshold(not set -t) .
The -t option is not specified. When using the
-I option, also specify the -t option.
File open error [%s]. errno = %s
The file failed to open. The amount of memory
or OS resources may be insufficient. Check for
any insufficiency.
Inputfile is invalid. cols = %s
The number of input data items is not correct.
Set the number of input data items to 2 or
more.
Inputfile is invalid. rows = %s
The input data format is incorrect. One line
needs to be divided into two rows.
Invalid date format. [expected YYYY/MM/DD
HH:MM:SS]
The date of the input data is not of the correct
format. Check to see the data.
Invalid date format. Not sorted in ascending
order.
Input data is not arranged in ascending order of
date and time. Check the data.
File read error.
An invalid value is set in the input data. Check
the data.
Too large number of data [%s]. Max number of
data is %s.
The number of input data items exceeds the
maximum value (500). Reduce the number of
data items.
Input number of data is smaller than
recommendable number.
Internal error.
The number of input data items is less than the
recommended number of data items to be
analyzed (120).
* Data is analyzed even if the recommended
number of data items to be analyzed is small.
An internal error has occurred.
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
112
Checking the process health
Checking the process health
command)
clphealthchk
(clphealthchk command)
(clphealthchk
Checks the process health.
Command line.
clphealthchk [ -t pm | -t rc | -t rm | -t nm | -h]
Note: This command must be run on the server whose process health is to be checked because
this command checks the process health of a single server.
Description
This command checks the process health of a single server.
Option
None
Checks the health of all of pm, rc, rm, and nm.
-t pm
Checks the health of pm.
-t rc
Checks the health of rc.
-t rm
Checks the health of rm.
-t nm
Checks the health of nm.
-h
Displays the usage.
0
Normal termination.
1
Privilege for execution is invalid.
2
Duplicated activation.
3
Initialization error.
4
The option is invalid.
10
The process stall monitoring function has not been
enabled.
11
The cluster is not activated (waiting for the cluster to start
or the cluster has been stopped.)
12
The cluster daemon is suspended.
Return Value
100
255
There is a process whose health information has not been
updated within a certain period.
If the -t option is specified, the health information of the
specified process is not updated within a certain period.
Other internal error.
Section II Command Reference
113
Chapter 2 EXPRESSCLUSTER X SingleServerSafe command reference
Example 1: When the processes are healthy
Examples
# clphealthchk
pm OK
rc OK
rm OK
nm OK
Example 2: When clprc is stalled
# clphealthchk
pm OK
rc NG
rm OK
nm OK
# clphealthchk –t rc
rc NG
Example 3: When the cluster has been stopped
# clphealthchk
The cluster has been stopped
Remarks
If the cluster has been stopped or suspended, the process is also stopped.
Notes
Run this command as a user with Administrator privileges.
Error Messages
Message
Cause/Solution
Log in as Administrator.
Log in as a user with Administrator privileges.
Initialization error. Check if memory or OS
resources are sufficient.
Invalid option.
The function of process stall monitor is
disabled.
The cluster has been stopped.
The cluster has been suspended.
This command is already run.
Internal error. Check if memory or OS
resources are sufficient.
Check to see if the memory or OS resource is
sufficient.
Specify a valid option.
The process stall monitoring function has not
been enabled.
The cluster has been stopped.
The cluster has been suspended.
The command has already been started.
Check to see if the memory or OS resource is
sufficient.
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
114
Section III
Release Notes
This section describes the restrictions on EXPRESSCLUSTER X SingleServerSafe, as well as the known
problems and how to prevent them.
•
•
Chapter 3
Chapter 4
Notes and restrictions
Error messages
115
Chapter 3
Notes and restrictions
This chapter provides cautions on using EXPRESSCLUSTER X SingleServerSafe, as well as the known
problems and how to prevent them.
This chapter covers:
•
•
After the system is put into operation ············································································ 118
WebManager ········································································································ 122
117
Chapter 3 Notes and restrictions
After the system is put into operation
This section provides notes on situations you might encounter after starting to operate
EXPRESSCLUSTER.
Restrictions during recovery operation
Do not perform the following operations by using the WebManager or command line while
recovery processing is changing (reactivation  last operation), if a group resource (an
application resource, service resource, or other resource) is specified as a recovery target and
when a monitor resource detects an error.

Stopping/suspending the cluster

Starting or stopping a group
If you perform the above-mentioned operations while recovery caused by detection of an error by
a monitor resource is in progress, other group resources of the group with an error may not stop.
However, you can perform them when the final action is completed.
Executable format files and script files not described in the
command reference
The installation directory contains executable files and script files that are not described in
Chapter 3, “EXPRESSCLUSTER command reference” in the Reference Guide. Do not execute
these files by using any program other than EXPRESSCLUSTER X SingleServerSafe.
Any problems caused by not using EXPRESSCLUSTER will not be supported.
EXPRESSCLUSTER Disk Agent service
The EXPRESSCLUSTER Disk Agent service is not used for EXPRESSCLUSTER X
SingleServerSafe. Do not start this service.
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
118
After the system is put into operation
Issues with User Account Control (UAC) in Windows Server 2008
environment
In Windows Server 2008 or later environment, User Account Control (UAC) is enabled by
default. When UAC is enabled, there are following issues.
Startup Program
If you log on a server with any account other than built-in Administrator account, following
programs are not allowed to execute. Also, following window is displayed.
Even if following programs are not executed, there is no effect on clustering functions.
clpaltui.exe
This is an icon showed in the task bar that indicate of cluster status. It is one of functions
of EXPRESSCLUSTER Alert Service. For more detail, please refer to Chapter 9, “Alert
Service” of Reference Guide.
clphookstdn.exe
When you initiate shutdown from [Start] of the task bar, this program shows the display
to notify you that you should shutdown the server with WebManager or
EXPRESSCLUSTER commands.
Even if you turn off UAC, above programs are not executed automatically when you log on.
Monitor Resource
Following resource has issues with UAC.
Oracle Monitor Resource
For the Oracle monitor resource, if you select OS Authentication for Authentication
Method and then set any user other than those in the Administrators group as the
monitor user, the Oracle monitoring processing will fail.
When you set OS Authentication in Authentication Method, the user to be set in
Monitor User must belong to the Administrators group.
Compatible Command
Following command has issue with UAC.
armload.exe
Section III Release Notes
119
Chapter 3 Notes and restrictions
If you use this command with /U option and any account other than built-in
Administrator, the command will fail to execute the application or service that set as
argument of it.
Screen display of application resource / script resource in the
Windows Server 2008 / 2012 environment
Because the processes started from the application resource or script resource of
EXPRESSCLUSTER are executed in session 0, when you start a process having GUI, the
Interactive services dialog detection pop-up menu is displayed in Windows Server 2008 / 2012.
Unless you select Show me the message, GUI is not displayed.
Environment in which the network interface card (NIC) is
duplicated
In an environment in which the NIC is duplicated, NIC initialization at OS startup may take some
time. If the cluster starts before the NIC is initialized, the starting of the kernel mode LAN
heartbeat resource (lankhb) may fail. In such cases, the kernel mode LAN heartbeat resource
cannot be restored to its normal status even if NIC initialization is completed. To restore the
kernel mode LAN heartbeat resource, you must first suspend the cluster and then resume it.
In that environment, we recommend to delay startup of the cluster by following setting or
command.
Network Initialization Complete Wait Time Setting
You can configure this setting in [Timeout] tab of [Cluster Properties]. This setting will be
enabled on all cluster servers. If NIC initialization is completed within timeout, the cluster
service starts up.
ARMDELAY command (armdelay.exe)
You must execute this command on each cluster server. The cluster service starts up after
the time that you set with the command from OS startup.
For more details of above setting and command, please refer to the Reference Guide.
EXPRESSCLUSTER service login account
The EXPRESSCLUSTER service login account is set in Local System Account. If this account
setting is changed, EXPRESSCLUSTER might not properly operate as a cluster.
Monitoring the EXPRESSCLUSTER resident process
The EXPRESSCLUSTER resident process can be monitored by using software monitoring
processes. However, recovery actions such as restarting a process when the process abnormally
terminated must not be executed.
JVM monitor resources
When restarting the monitoring-target Java VM, you must first suspend JVM monitor resources
or stop the cluster.
When changing the JVM monitor resource settings, you must suspend and resume the cluster.
JVM monitor resources do not support a delay warning for monitor resources.
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
120
After the system is put into operation
System monitor resources
To change a setting, the cluster must be suspended.
System monitor resources do not support a delay warning for monitor resources.
If the date or time setting on the OS is changed while a system monitor resource is operating, that
system monitor resource may fail to operate normally.
If you have changed the date or time setting on the OS, suspend and then resume the cluster.
Up to 26 disks that can be monitored by the disk resource monitor function at the same time.
Display of the Interactive services dialog detection pop-up menu in
a Windows Server 2008 / 2012 environment
To allow the Interactive services dialog detection pop-up menu to be displayed by setting the
Allow to Interact with Desktop of the application resource or script resource in a Windows
Server 2008 or Windows Server 2012 environment, the “Interactive Service Detection” service
must have been started.
In Windows Server 2012, the startup of the “Interactive Service Detection” service with its
default settings is invalid. Follow the procedure below to validate the service.
Reference site :
http://msdn.microsoft.com/en-us/library/windows/desktop/ms683502(v=vs.85).aspx
→ Using an Interactive Service
Section III Release Notes
121
Chapter 3 Notes and restrictions
WebManager

Information displayed by the WebManager does not always reflect the latest status. To
acquire the latest information, click the Reload icon on the toolbar or Reload in the Tool
menu.

If a server fails while the WebManager is acquiring information, the information acquisition
fails, which may result in the failure to show some objects.
Wait for the next automatic update, or click the Reload icon on the toolbar or Reload in the
Tool menu to reacquire the latest information.

Logs cannot be collected from multiple WebManagers simultaneously.

If you work on the WebManager when no connectivity is established, it may take a while to
regain control.

If you move the cursor out of the browser while the mouse pointer is a wristwatch or
hourglass, the pointer might change back to an arrow.

If a proxy server is used, configure the proxy server so that the port number of the
WebManager can be relayed.

When a reverse proxy server is used, the WebManager does not run normally.

When you update EXPRESSCLUSTER X SingleServerSafe, close the browser. Next, clear
the Java cache, and then restart the browser.

If the client PC to connect to WebManager uses Java Runtime Environment (JRE) 7 Update
25 or later, and cannot be connected to the Internet, it may take time to start WebManager.
This can be avoided by setting Execute Certificate Revocation Check to Not Check on
Detailed Settings on the Java Control Panel. For details of how to set it, check the Java
website.

Closing the Web browser (by clicking Exit from the menu), the dialog box to confirm to
save is displayed.
When you continue to edit, click the Cancel button.
Note:
This dialog box is not displayed if JavaScript is disabled.
EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
122
Chapter 4
Error messages
This chapter provides information on
EXPRESSCLUSTER X SingleServerSafe.
error
messages
you
might
encounter
when
operating
This chapter covers:
•
Messages reported by event log and alert········································································ 124
123
Chapter 4 Error messages
Messages reported by event log and alert
The messages that are output to event logs and alerts are the same as those of
EXPRESSCLUSTER X. For details of these messages, see the Reference Guide for
EXPRESSCLUSTER X.
The messages specific to EXPRESSCLUSTER X SingleServerSafe are as follows.
sss
Error
20005
sss
Info
20006
sss
Error
20007
sss
Info
20008
sss
Error
20009
sss
Error
20010
sss
Info
20012
Userlog
Error
20004
Eventlog
Event Type
sss
Alert
Module Type
Event
ID
Message
Explanation
Solution
Failed to get the
system drive letter.
The system drive
letter could not be
acquired.
The system may not
be able to operate
properly.

Failed to get the
server name.
The server name
could not be
acquired.
The system may not
be able to operate
properly.

The server name has
been updated.
The server name has
been updated.



Failed to update the
configuration file.
The configuration file
could not be
updated.
Check the
configuration data.


The configuration file
has been updated.
The configuration file
has been updated.


The content of the
configuration file is
invalid.
The content of the
configuration file is
invalid.
Check the
configuration data.

Failed to start %1
service.
The %1 service
could not be started.
The system may not
be able to operate
properly.
%1 service has been
started.
The %1 service has
been started.




EXPRESSCLUSTER X SingleServerSafe 3.3 for Windows Operation Guide
124
Messages reported by event log and alert
Error
sss
Info
sss
Userlog
Info
20013
Eventlog
Event Type
sss
Alert
Module Type
Event
ID
%1 service has been
stopped.
The %1 service has
been stopped.


20014
The redundant
module of the LAN
board has been
started.
The redundant
module of the LAN
board has been
started.
Memory or OS
resources may not
be sufficient. Check
them.

20015
Failed to start the
redundant module of
the LAN board.
The redundant
module of the LAN
board could not be
started.



An error was
detected in LAN
board %1.
An error was
detected in LAN
board %1.
Check whether the
settings of the
standby LAN board
are correct.


Changing LAN
board %1 to LAN
board %2.
LAN board %1 will
now be switched to
LAN board %2.



The operation of
LAN board %1 failed.
The operation of
LAN board %1 failed.



ncctl
20101
ncctl
20102
ncctl
Error
Solution
caution
Explanation
Error
Message
20103
Section III Release Notes
125
Appendix
•
Appendix A Index
127
Appendix A Index
A
Adjusting time-out temporarily, 80
Alert view fields, 48
Alert view operations, 49
Applying configuration data, 55, 74
B
Backing up cluster configuration data, 55, 74
Backing up configuration data, 78
EXPRESSCLUSTER Disk Agent service, 116
J
JVM monitor resources, 118
M
Main window of the WebManager, 18
Manually stopping and starting the
WebManager, 50
Modifying the log level and size, 83
C
O
Changing the screen layout on the WebManager,
26
Changing the WebManager operation mode, 21
Checking alerts using the WebManager, 48
Checking the cluster status by the WebManger
List view, 39
Checking the status of each object, 15, 20, 30
Checking the status of individual server in the
WebManager list view, 47
Checking the status of the whole monitor in the
WebManager list view, 47
Checking the time information, 26
Checking the whole status of the server in the
WebManager list view, 46
checkingthe process health, 55, 111
Collecting information on emergency OS
shutdown, 73
Collecting logs, 69
Collecting logs by specifying a type, 70
Collecting logs by using the WebManager, 23
Confirming the license from the WebManager, 29
Controlling CPU frequency, 99
Controlling group resources, 97
Controlling monitor resources, 55, 93
Controlling reboot count, 104
Operating groups, 66
Operating the cluster from the command line, 56
Operating the service, 61
Operation services on the WebManager, 28
Operations that can be executed from the
WebManager, 30
Output paths of log files, 72
Outputting messages, 91
D
Display of interactive serivces dialog detection
popup menu, 119
Displaying information by using the
WebManager list view, 39
Displaying the cluster status, 58
E
Estimating the amount of resource usage, 106
Executable files, 116
Executing Integrated WebMnager from the
WebMnager, 28
EXPRESSCLUSTER commands, 56
R
Requesting processing to cluster servers, 101
Restrictions during recovery operation, 116
S
Script files, 116
Searching for an alert by using the WebManager,
22
Setting limitations on the connection and
operation of the WebManager, 51
Shutting down the server, 65
Specifying a event log type to collect, 72
Starting the WebManager, 16, 17
T
Types of usage limitations, 51
U
Updating the WebManager information, 25
W
WebManager, 16, 120
When you do not want to use the WebManager,
50
Windows of the WebManager, 18
129