Server Alarms - Avaya Support

Server Alarms
Table 5: ARB Alarms 8 of 10
Event
ID
11
(cont’d)
Alarm
Level
Alarm Text, Cause/Description, Recommendation
WRN 2. Check for both the completeness and consistency of the servers’
hosts and servers.conf files (containing IP addresses of the
system’s configured components), either from the:
- Web interface, by selecting Configure Server
- Linux command line, by entering:
more /etc/hosts
more /etc/opt/ecs/servers.conf
The Arbiter uses port number 1332 for sockets. Enter
netstat -a | grep 1332 to see if the alarm is still active. The
output should look something like:
upd 0 0-cnb:1332 *.*
upd 0 0-cna:1332 *.*
upd 0 0-dup:1332 *.*
3. If the IP addresses agree and there are no alarms for port 1332,
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 this problem affects call processing or if the problem persists,
continue with Step 5.
If not, continue only at the customer’s convenience.
5. Escalate this problem for explicit guidance with Steps 5a through 6.
a. Enter server to verify that the suspected server is the standby.
b. If not, enter server -if to force a server interchange. Busy out
the standby server from the Linux command line, by entering
server -b.
c. Reboot the server (as the standby), either from the:
- Web interface, by selecting Shutdown This Server
- Linux command line, by entering /sbin/shutdown -r now
6. If rebooting the standby does not help or if the problem recurs,
escalate the problem to the next higher tier.
48 Maintenance Alarms for Avaya Communication Manager, Media Gateways and Servers
8 of 10