09.12.2012 Views

Server Alarms - Avaya Support

Server Alarms - Avaya Support

Server Alarms - Avaya Support

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.

Table 11: ENV <strong>Alarms</strong> 2 of 14<br />

Event<br />

ID<br />

Alarm<br />

Level<br />

Alarm Text, Cause/Description, Recommendation<br />

ENV (Environment)<br />

3 WRN “Temperature reached Warning High. Value = xx0C” — Motherboard's<br />

temperature reached a warning high.<br />

1. See if the alarmed condition is still present, either from the:<br />

- Web interface, by selecting the Temperature/Voltage diagnostic<br />

- Linux command line, by entering environment<br />

2. If not, manually clear the alarm, either from the:<br />

- Web interface, by selecting <strong>Alarms</strong> and Notification, the<br />

appropriate alarm, and Clear<br />

- Linux command line, by entering almclear -n #id<br />

4 MAJ “Temperature reached Critical High. Value = xx0C” — Motherboard's<br />

temperature reached a critically high level.<br />

1. Look for any obstructions blocking the server’s fans.<br />

2. Check for any fan alarms, and clear those alarms.<br />

3. Shut down and restart the system.<br />

4. See if the alarmed condition is still present, either from the:<br />

- Web interface, by selecting the Temperature/Voltage diagnostic<br />

- Linux command line, by entering environment<br />

5. If not, manually clear the alarm, either from the:<br />

- Web interface, by selecting <strong>Alarms</strong> and Notification, the<br />

appropriate alarm, and Clear.<br />

- Linux command line, by entering almclear -n #id<br />

2 of 14<br />

Communication Manager Release 5.0 Issue 4 January 2008 63

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

Saved successfully!

Ooh no, something went wrong!