Avaya 03-300430 User Manual

Page of 2574
Server Alarms
48 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
 
13
(cont’d)
MIN
2. From the Linux command line, enter start -a to restart the standby 
server.
3. Prevent any future misuse of the stop command.
4. Manually clear the alarm on the active server, either from the:
- Web interface, by selecting Alarms and Notification, the 
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
Either the:
The alternate side is hung (ARB Event 8 is not being generated)
Two or more Interarbiter links are down (ARB Event 8 is also being 
generated)
Therefore, if the servers interchanged (the previously active server 
backed down to standby), use the following procedure:
5. Check for problems with an Ethernet interface, either from the:
- Web interface, by selecting the Execute Pingall diagnostic
- Linux command line, by entering pingall -a
Check both sides of each failed link, and make any necessary repairs.
a. If the Ethernet interfaces are OK, see if the standby server is 
busied-out, either from the:
- Web interface, by selecting View Summary Status
- Linux command line, by entering server
b. If so, release the standby server, either from the:
- Web interface, by selecting Release Server
- Linux command line, by entering server -r
If not, check for related alarms to troubleshoot the standby.
6. 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
7. If the problem persists, escalate the problem.
Table 8: ARB Alarms in Media Server  (continued)
Event
ID
Alarm 
Level
Alarm Text, Cause/Description, Recommendation
 11 of 12