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 12 Troubleshooting<br />

When activating or deactivating group resources fails<br />

774<br />

If any error is detected in activation of a group resource, detailed error in<strong>for</strong>mation is logged in<br />

the alert and event log. See “Detailed in<strong>for</strong>mation in activating and deactivating group resources”<br />

and examine the logs to find the cause of the error and take appropriate action <strong>for</strong> it.<br />

When a monitor resource error occurs<br />

If a monitor resource detects any error, detailed in<strong>for</strong>mation on error is logged in the alert and<br />

event logs. See “Detailed info of monitor resource errors” and examine the logs to find the cause<br />

of the error and take appropriate action <strong>for</strong> it.<br />

When a heartbeat time-out occurs<br />

Possible causes of heartbeat time-out between servers are listed below:<br />

Cause Solution<br />

Disconnection of LAN cables Check that you can send packets with the ping<br />

command.<br />

Recovering from failure of one server<br />

If the automatic recovery mode is not set in Cluster Properties, the server that you have<br />

removed errors and restarted is in the Suspension (Isolated) status. To recover the server to the<br />

normally functioning cluster from this status, use the WebManager or the clpcl command.<br />

If the Replicator is used, data between the disks that <strong>for</strong>m a mirror set becomes inconsistent.<br />

However, by recovering the server, the mirror will be automatically rebuilt, and the data will<br />

become consistent.<br />

To recover the server by the WebManager, see “Operating a cluster by using the WebManager”<br />

of Chapter 1, “Functions of the WebManager” of Section I of this guide.<br />

To recover the server by the clpcl command, see “Operating the cluster” of Chapter 4,<br />

“<strong>ExpressCluster</strong> command reference” of Section I of this guide.<br />

Recovering from failure of both servers<br />

When Off is selected <strong>for</strong> Auto Return on the Auto Recovery tab in Cluster Properties, when<br />

all the servers shut down by failures such as a hardware failure, after starting them up, they are<br />

removed from the cluster. Recover all the servers by using the WebManager or the clpcl<br />

command.<br />

Right after recovering the servers, all the groups are stopped. Start all the groups. If the<br />

Replicator is used, the mirror will be automatically built again by starting the groups, and the<br />

data will become consistent.<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!