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.

Monitoring errors on the connection to the shared resources (armwhshr command)<br />

Return Value<br />

How to use<br />

0 Success<br />

Section I Detailed functions of <strong>ExpressCluster</strong><br />

1 The parameter is invalid.<br />

2 Insufficient memory<br />

8 The <strong>ExpressCluster</strong> Server service has not been started.<br />

When using the ARMWHSHR command, configure the following<br />

settings.<br />

(1) Registering the user account<br />

Register the user account with an administrator right.<br />

(2) Describing the ARMWHSHR command in scripts<br />

Create a new failover group <strong>for</strong> monitoring errors on the connection<br />

to the shared name(*), and describe the ARMWHSHR command in<br />

scripts.<br />

* Setting a failover group<br />

1. Add only one server to the Servers that can run the Group by<br />

clicking the Startup Server tab on the Group Properties.<br />

For example, to monitor errors on the connection to the shared name<br />

(temp) of the server (server name: server public LAN IP address:<br />

100.100.100.1), describe the following in the start script:<br />

(Lines in the script that is run when CLP_EVENT is START)<br />

ARMLOAD watchID /U Administrator<br />

ARMWHSHR \\server\temp 100.100.100.1<br />

Describe the following in the stop script<br />

(Lines in the script that is run when CLP_EVENT is START)<br />

ARMKILL watchID<br />

351

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

Saved successfully!

Ooh no, something went wrong!