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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Module<br />

Type<br />

Event<br />

Type<br />

Event<br />

ID<br />

rc Error 1460<br />

rc Error 1461<br />

rc Error 1462<br />

rc Error 1463<br />

rc Error 1464<br />

rm In<strong>for</strong>mation 1501<br />

rm In<strong>for</strong>mation 1502<br />

rm In<strong>for</strong>mation 1503<br />

rm Warning 1504<br />

rm Warning 1505<br />

rm Warning 1506<br />

rm Error 1507<br />

rm Error 1508<br />

rm Error 1509<br />

rm In<strong>for</strong>mation 1510<br />

Section III Maintenance in<strong>for</strong>mation<br />

Messages Description Solution<br />

CPU frequency control<br />

cannot be used.<br />

Failed to set the CPU<br />

frequency to high.<br />

Failed to set the CPU<br />

frequency to low.<br />

Failed to set the CPU<br />

frequency to %1.<br />

Failed to switch the CPU<br />

frequency setting to<br />

automatic control by<br />

cluster.<br />

Monitor %1 has been<br />

started.<br />

Monitor %1 has been<br />

stopped.<br />

Monitor %1 does not<br />

monitor in this server.<br />

Monitor %1 is in the<br />

warning status.<br />

(%2 : %3)<br />

The number of monitor<br />

resources reached the<br />

maximum number.<br />

(registered<br />

resource: %1)<br />

Configuration of %1 is<br />

invalid. (%2 : %3)<br />

Failed to start<br />

monitor %1.<br />

Failed to stop<br />

monitor %1.<br />

Monitor %1 detected an<br />

error. (%2 : %3)<br />

Monitor %1 is not<br />

monitored.<br />

CPU frequency control<br />

cannot be used.<br />

Setting the CPU<br />

frequency to high has<br />

failed.<br />

Setting the CPU<br />

frequency to low has<br />

failed.<br />

Setting the CPU<br />

frequency has failed.<br />

Switching the CPU<br />

frequency setting to<br />

automatic control by<br />

cluster has failed.<br />

Messages reported by event log and alert<br />

Alert<br />

Event log<br />

User log<br />

805<br />

Report Manager<br />

setting Alive<br />

Mail report<br />

Check BIOS settings and<br />

kernel settings.<br />

Check BIOS settings and<br />

kernel settings. Check if the<br />

● ● ● ●<br />

cluster service is started.<br />

Check if the configuration is<br />

set so that CPU frequency<br />

control is used.<br />

Check BIOS settings and<br />

kernel settings. Check if the<br />

● ● ● ●<br />

cluster service is started.<br />

Check if the configuration is<br />

set so that CPU frequency<br />

control is used.<br />

Check BIOS settings and<br />

kernel settings. Check if the<br />

● ● ● ●<br />

cluster service is started.<br />

Check if the configuration is<br />

set so that CPU frequency<br />

control is used.<br />

Check if the cluster service is<br />

● ● ● ●<br />

started. Check if the<br />

configuration is set so that<br />

CPU frequency control is used.<br />

● ● ● ●<br />

Monitor start - ● ● ●<br />

Monitor stop - ● ● ●<br />

Not target server - ● ● ●<br />

Monitor warn Check the cause of Warning. ● ● ● ●<br />

invalid number of<br />

monitor resource<br />

invalid monitor resource<br />

monitor starting failed<br />

monitor stopping failed<br />

monitor failed<br />

Check the cluster configuration<br />

data.<br />

Check the cluster configuration<br />

data.<br />

The system may not be able to<br />

operate properly.<br />

The system may not be able to<br />

operate properly.<br />

Check the cause <strong>for</strong> monitor<br />

error.<br />

not monitored - ● ● ●<br />

● ● ● ●<br />

● ● ● ●<br />

● ● ● ● ●<br />

● ● ● ●<br />

● ● ● ● ●<br />

rm In<strong>for</strong>mation<br />

Monitor resource has not unregistered monitor<br />

1511<br />

been registered. resource<br />

- ● ● ●<br />

rm In<strong>for</strong>mation<br />

%1 was stopped <strong>for</strong><br />

1512<br />

failure in monitor %2.<br />

relation stop - ● ● ●<br />

rm In<strong>for</strong>mation<br />

%1 was restarted <strong>for</strong><br />

1513<br />

failure in monitor %2.<br />

relation restart - ● ● ●<br />

rm In<strong>for</strong>mation<br />

%1 was failed over <strong>for</strong><br />

1514<br />

failure in monitor %2.<br />

There was a request to<br />

relation group failover - ● ● ●<br />

rm In<strong>for</strong>mation 1515 stop cluster <strong>for</strong> failure in<br />

monitor %1.<br />

cluster stop - ● ● ●

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

Saved successfully!

Ooh no, something went wrong!