27.02.2013 Views

ExpressCluster X 2.0 for Windows Reference Guide - Nec

ExpressCluster X 2.0 for Windows Reference Guide - Nec

ExpressCluster X 2.0 for Windows Reference Guide - Nec

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 4 <strong>ExpressCluster</strong> command reference<br />

324<br />

Notes This command must be executed by a user with the administrator<br />

privilege.<br />

This command cannot be executed when the <strong>ExpressCluster</strong> Transaction<br />

service is not operating on the server with the IP address specified by -h.<br />

Examples<br />

When WebManager connection restriction is conducted by the client IP<br />

address on this target server, it is required that connection to the address<br />

of the server to execute the command is permitted.<br />

It is required that <strong>ExpressCluster</strong> <strong>for</strong> <strong>Windows</strong> of internal version 10.02 or<br />

later, or <strong>ExpressCluster</strong> <strong>for</strong> Linux of internal version <strong>2.0</strong>.2_1 or later is set<br />

up in the server which executes this command and the server with the IP<br />

address specified by -h.<br />

Example 1: When per<strong>for</strong>ming a failover on the group having the appli1<br />

resource of another cluster<br />

# clptrnreq –t GRP_FAILOVER –h 10.0.0.1,10.0.0.2 –r appli1<br />

GRP_FAILOVER 10.0.0.1: Success<br />

GRP_FAILOVER 10.0.0.2: Group that specified resource (appli1)<br />

belongs is offline.<br />

Example 2: When executing the scrpit1.bat script by the server with IP<br />

address 10.0.0.1<br />

# clptrnreq –t EXEC_SCRIPT –h 10.0.0.1 –s script1.bat<br />

EXEC_SCRIPT 10.0.0.1: Success<br />

Error messages<br />

Message Cause/solution<br />

Log in as Administrator. Log in as a user with Administrator privileges.<br />

Invalid option.<br />

The command line option is invalid. Specify the<br />

correct option.<br />

All servers are busy. Check if this command is<br />

already run.<br />

This command may be run already. Check it.<br />

Internal error. Check if memory or OS resources<br />

are sufficient.<br />

Check if the memory or OS resource is sufficient.<br />

Command timeout The cause may be heavy load on OS and so on.<br />

Check this.<br />

Failed to obtain the list of nodes.<br />

Specify a valid server name in the cluster.<br />

Failed to obtain the list of nodes.<br />

Specify a valid IP address.<br />

Could not connect to all data transfer server.<br />

Check if the server has started up.<br />

Could not connect to all IP addresses specified.<br />

Check the IP addresses and the status of the<br />

target server.<br />

Could not connect to the data transfer server.<br />

Check if the server has started up.<br />

Could not connect to the IP address specified.<br />

Check the IP address and the status of the target<br />

server.<br />

GRP_FAILOVER IP: Group that specified<br />

resource (resouce_name) belongs to is offline.<br />

Failover process is not per<strong>for</strong>med because the<br />

group to which the specified resource belongs is<br />

not started on the target server.<br />

EXEC_SCRIPT IP: Specified script ( script_file )<br />

does not exist.<br />

The script does not exist on the specified server.<br />

Check it.<br />

<strong>ExpressCluster</strong> X <strong>2.0</strong> <strong>for</strong> <strong>Windows</strong> <strong>Reference</strong> <strong>Guide</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!