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 />

250<br />

Notes Run this command as a user with Administrator privileges.<br />

Example of a<br />

command<br />

entry<br />

For the name of a server <strong>for</strong> the -h option, specify the name of a server in<br />

the cluster that allows name resolution.<br />

When you suspend the cluster, the <strong>ExpressCluster</strong> service should be<br />

activated in all servers in the cluster. When the --<strong>for</strong>ce option is used, the<br />

cluster is <strong>for</strong>cefully suspended even if there is any stopped server in the<br />

cluster.<br />

When you start up or resume the cluster, access the servers in the cluster<br />

in the order below, and use one of the paths that allowed successful<br />

access.<br />

1. via the IP address on the interconnect LAN<br />

2. via the IP address on the public LAN<br />

3. via the IP address whose name was resolved by the server name in<br />

the cluster configuration data<br />

When you resume the cluster, use the clpstat command to see there is no<br />

activated server in the cluster.<br />

Example 1: Activating the <strong>ExpressCluster</strong> service in the local server<br />

# clpcl –s<br />

Command succeeded<br />

Example 2: Activating the <strong>ExpressCluster</strong> service in server1 from<br />

server0<br />

# clpcl -s -h server1<br />

Start server1 : Command succeeded.<br />

If a server name is specified, the display after running the command<br />

should look similar to above.<br />

Start server_name : Execution result<br />

Example 3: Activating the <strong>ExpressCluster</strong> service in all servers<br />

# clpcl -s -a<br />

Start server0 : Command succeeded.<br />

Start server1 : Per<strong>for</strong>med startup processing to the<br />

active cluster service.<br />

When all the servers are activated, the display after running the command<br />

should look similar to above.<br />

Start server_name : Execution result<br />

Example 4: Stopping the <strong>ExpressCluster</strong> service in all servers<br />

# clpcl -t -a<br />

Stop server0 : Command succeeded.<br />

Stop server1 : Command succeeded.<br />

When all the servers are stopped, the display after running the command<br />

should look similar to above. Stop server_name : Execution result.<br />

When the stopping process fails, the display may be different from the<br />

example above depending on the process.<br />

Wait <strong>for</strong> the stopping of all servers of the <strong>ExpressCluster</strong> service.<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!