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 3 Function of the Builder<br />

Delay Warning tab<br />

136<br />

Configure the settings <strong>for</strong> Delay Warning on this tab. See “Delay warning of monitor resources”<br />

in Chapter 7, “Monitor resource details” <strong>for</strong> more in<strong>for</strong>mation.<br />

Heartbeat Delay Warning (1 to 99) SuspendResume<br />

Set a percentage of heartbeat time-out at which the heartbeat delay warning is issued. If the time<br />

<strong>for</strong> the percentage passes without any heartbeat response, the warning will be produced in an<br />

alert log.<br />

Monitor Delay Warning (1 to 99) SuspendResume<br />

Set a percentage of monitor time-out at which the monitor delay warning is issued. If the time <strong>for</strong><br />

the percentage passes without any monitor response, the warning will be produced in an alert log.<br />

COM Delay Warning (1 to 99) SuspendResume<br />

Set a percentage of COM I/F delay warning. If the time <strong>for</strong> the percentage passes without any<br />

COM response, the warning will be produced in an alert log.<br />

Note:<br />

If you specify 0% <strong>for</strong> the delay warning, an alert log is shown in every heartbeat interval and<br />

monitor interval. Setting 0% allows you to see the time spent <strong>for</strong> monitoring. This will be helpful<br />

particularly in a test operation. Make sure not to set low values such as 0% in the production<br />

environment.<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!