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.

Module<br />

Type<br />

Chapter 13 Error messages<br />

798<br />

Event<br />

Type<br />

Event<br />

ID<br />

nm Error 6<br />

nm Error 7<br />

nm Error 8<br />

nm Error 9<br />

nm In<strong>for</strong>mation 10<br />

nm Error 11<br />

Messages Description Solution<br />

The resource %2 of the<br />

server %1 is unknown.<br />

Network partition was<br />

detected. Shut down the<br />

server %1 to protect<br />

data.<br />

An error occurred while<br />

confirming the network<br />

partition. Shut down the<br />

server %1.<br />

An error occurred in<br />

confirming the network<br />

partition. To avoid<br />

failover on multiple<br />

servers, the server %1<br />

suspended failover.<br />

The server %1 cancelled<br />

the pending failover.<br />

Shut down the<br />

server %1. (reason:%2)<br />

Resource unknown<br />

Network partition<br />

Can not network partition<br />

resolution<br />

Failover hold<br />

Check the cluster configuration<br />

data.<br />

All heartbeat resources cannot<br />

be used. Check if an error has<br />

occurred in network adapter<br />

and the network is properly<br />

connected.<br />

Refer to the event logs and<br />

check if an error has occurred<br />

in resource.<br />

Refer to the event logs and<br />

check if an error has occurred<br />

in resource.<br />

Failover hold cancel - ● ●<br />

Server shutdown<br />

All heartbeat resources cannot<br />

be used. Check if an error has<br />

occurred in network adapter<br />

and the network is properly<br />

connected.<br />

Check the cause following the<br />

message.<br />

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

Alert<br />

Event log<br />

User log<br />

Report Manager<br />

setting Alive<br />

Mail report<br />

● ● ●<br />

● ● ● ●<br />

● ● ● ●<br />

● ● ● ●<br />

● ● ● ●<br />

nm Error 12<br />

Cluster service will be<br />

stopped. (reason:%1)<br />

The combination of the<br />

Cluster service stopping ● ● ●<br />

nm Warning 13<br />

network partition<br />

resources is invalid.<br />

(server name:%1)<br />

NP resource<br />

combination error<br />

Check the cluster configuration<br />

data.<br />

● ● ●<br />

The status of<br />

Check if an error has occurred<br />

nm Error 14 heartbeat %1 is Heartbeat abnormally in network adapter and the ● ● ● ●<br />

abnormal.<br />

The hearbeat %1 has<br />

network is properly connected.<br />

nm In<strong>for</strong>mation 15 been recovered to the<br />

normal status.<br />

Hearbeat recovered - ● ●<br />

nm Error 16<br />

The network partition %2<br />

Network partition<br />

of the server %1 has an<br />

abnormally<br />

error.<br />

The network partition %2<br />

Refer to the event logs and<br />

check if an error has occurred<br />

in resource.<br />

● ● ● ●<br />

nm In<strong>for</strong>mation 17<br />

of the server %1 has<br />

been recovered to the<br />

normal status.<br />

Network partition<br />

recovered<br />

- ● ●<br />

Failed to start the<br />

Refer to the event logs and<br />

nm Error 18 resource %1. Server Resource start failed check if an error has occurred ● ● ● ●<br />

name:%2<br />

in resource.<br />

pm In<strong>for</strong>mation 501<br />

Cluster service has been<br />

Cluster service started<br />

started properly.<br />

- ● ● ●<br />

pm In<strong>for</strong>mation 502<br />

Cluster service is<br />

shutting down.<br />

Cluster service shutting<br />

down<br />

- ● ● ●<br />

pm In<strong>for</strong>mation 503<br />

Shutdown stall monitor<br />

has been started.<br />

Shutting down stall<br />

monitor<br />

- ● ● ●<br />

pm Error 510<br />

Cluster service has<br />

already been started.<br />

Cluster service already<br />

started<br />

Check the status of cluster<br />

service.<br />

The service is not run by a<br />

● ● ● ●<br />

pm Error 511<br />

Fatal error has occurred<br />

in the cluster service.<br />

Critical error in cluster<br />

service<br />

user with required privilege or<br />

the system may not be able to<br />

operate properly.<br />

● ● ● ● ●

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

Saved successfully!

Ooh no, something went wrong!