Avaya 03-300430 User Manual

7

MAJ

“Arbiter in invalid/unknown state” — Memory corruption or bad code/build

1. Verify that the server’s state is “Corrupt!”, either from the:

- Web interface’s Server section, by selecting View Summary 

- Linux command line, by entering server

2. Compare the suspected arbiter with the one in /root2 — using 

the Linux commands:

(This command shows the arbiter’s version string.)

[This command runs a cyclical redundancy check (CRC) against 
the arbiter, and then shows both the CRC’s output value and the 
number of bytes in the arbiter file.]

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.

 2 of 12