Server Alarms - Avaya Support

Table 5: ARB Alarms 7 of 10
Event
ID
9
(cont’d)
Alarm
Level
Alarm Text, Cause/Description, Recommendation
ARB (Arbiter)
WRN After the interchange, the newly active server’s health should be
significantly better than the standby server’s. See the SOH values "bb" and
"cc" as defined above. The server with the larger "bb" value is generally
considered more healthy. If there is a tie, the server with the larger "cc"
value is more healthy. If the newly active server’s health is significantly
better than the standby server’s, troubleshoot the standby server.
If the newly active server’s health is not significantly better:
1. 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
2. If the problem recurs, escalate the problem.
11 WRN “Cannot create receive socket;” “Cannot create transmit socket;” “Cannot
bind receive socket;” “Cannot (re)bind send socket”
Since the Arbiter continuously attempts to create or bind the socket, the
problem may resolve itself. Once resolved, the Arbiter can send and
receive across every Interarbiter link (no subsequent error messages in
the trace log).
1. Examine the alarm log to distinguish between a:
Bind or create problem
Send or receive socket problem
by accessing either the:
- Web interface, by:
a. Selecting Alarms and Notification and the appropriate alarm
b. Selecting the View System Logs diagnostic
c. Selecting the Logmanager Debug trace
d. Specifying the Event Range for the appropriate time frame
e. Matching the “cannot create” pattern
- Linux command line, by entering almdisplay -v
7 of 10
Communication Manager Release 5.0 Issue 4 January 2008 47