Server Alarms - Avaya Support

Table 11: ENV Alarms 4 of 14
Event
ID
Alarm
Level
Alarm Text, Cause/Description, Recommendation
ENV (Environment)
8 MAJ “3.3 Voltage reached Critical High. Value = x.y” — Motherboard's nominal
+3.3 voltage reached a critically high level.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the Temperature/Voltage diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
9 MIN “+5 voltage reached Warning Low” — Motherboard's nominal +5 voltage
reached a warning low level.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the Temperature/Voltage diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
10 MAJ “5 Voltage reached Critical Low. Value = x.y” — Motherboard's nominal +5
voltage reached a critically low level.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the Temperature/Voltage diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
4 of 14
Communication Manager Release 5.0 Issue 4 January 2008 65