Server Alarms - Avaya Support

Server Alarms
Table 5: ARB Alarms 2 of 10
Event
ID
Alarm
Level
Alarm Text, Cause/Description, Recommendation
7 MAJ “Arbiter in invalid/unknown state” — Memory corruption or bad code/build
1. Verify that the server’s state is “Corrupt!” by entering the following
commands on the Linux command line:
server
stop -Sf -s arbiter
start -s arbiter
server -c
If the output no longer shows "Mode: Corrupt!", then the problem has
been fixed. Otherwise, proceed to step 2.
2. Compare the suspected arbiter with the one in /root2.
Enter the following Linux command to display the arbiter’s version
string:
/opt/ecs/sbin/acpfindvers /opt/ws/arbiter
Enter the following command to run a cyclical redundancy check
(CRC) against the arbiter and display both the CRC output value
and the number of bytes in the arbiter file:
/sbin/cksum /opt/ws/arbiter
3. If the two arbiter files differ:
a. Get a fresh copy of arbiter from the CD.
b. 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. If the arbiter file is OK or the problem persists, escalate the
problem.
42 Maintenance Alarms for Avaya Communication Manager, Media Gateways and Servers
2 of 10