Cause
Server could not read translations. Usually, indicates a failure loading translations, but can also infrequently occur on a running system.
Duplicated servers: The servers spontaneously interchanged.
S8300: The server rebooted.
Proposed Solution
Procedure
- Check the integrity of the translation files xln1 and xln2 in /etc/opt/defty, and verify that they are of non-zero length.
- From the /etc/opt/defty directory, enter the Linux command cksum xln1 xln2 to verify that the checksums of the files are identical.
- Duplicated servers: Copy the translation files from the backup or the other server.
- S8300: Copy the translation files from the backup.
- If Steps 1 to 3 do not help, load the system with null translations.
- If the system does not start, go to the Avaya Support website at http://support.avaya.com to open a service request.
- After the error is resolved, manually clear the alarm:
- From the Web interface, select Current Alarms and the appropriate alarm, and click Clear.
- From the Linux command line, enter almclear -n #id.