A high-priority process caused the active Arbiter to hang for at least 4.1 seconds causing an interchange. Each Arbiter then realized that the other had assumed the active role. An automatic resolution process must leave the newly active server active, while the other server backs down to the standby role.
Every Inter-arbiter link is down or misconfigured.
Proposed Solution 1
Procedure
To check server status, see Verifying the server status.
If one server is active and the other is standby, 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 .
If the problem persists, go to the Avaya Support website at http://support.avaya.com to open a service request.
Proposed Solution 2
Procedure
To check server status, see Verifying the server status.
Check for problems with an Ethernet interface:
From the Web interface, select the Execute Ping diagnostic.
From the Linux command line, enter pingall -a.
Check both sides of each failed link, and make necessary repairs.
If the links are okay but the problem persists, go to the Avaya Support website at http://support.avaya.com to open a service request.
