Filter
Top Products
Server Alarms
58 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
1
(cont’d)
MAJ If not and at the customer’s convenience:
Since the following commands cause a brief service outage, they should
only be executed at the customer’s convenience.
a. Force a server interchange to make the suspected server standby,
either from the Linux command line, by entering server -if.
b. Busy out the standby server from the Linux command line, by
entering server -b.
c. Reboot the standby server, either from the:
- Web interface, by selecting Release Server
- Linux command line, by entering server -r
6. If the problem persists, you can try:
a. Replacing the fiber between the two servers
b. Rebooting the standby server
7. If the problem continues to persist, escalate for a probable server
replacement.
2 MAJ “Duplication link down” — One server’s Duplication Manager cannot
communicate with the other server’s Duplication Manager.
1. Access the trace log, either from the:
- Web interface, by:
a. Selecting the View System Logs diagnostic and Logmanager
Debug trace
b. Specifying the Event Range for the appropriate time frame
c. Matching the “dup” pattern
- Linux command line, by entering logv -t ts
2. Examine the trace-log query’s output for one of these messages:
“mainlp: get_addrs returned ***. Could not get IP address for other
server.
Verify name and address in servers.conf. ndm exiting.”
“san_check_msg() sync_msg failed: DUPLINK DOWN.”
Table 14: DUP Alarms in Media Server (continued)
Event
ID
Alarm
Level
Alarm Text, Cause/Description, Recommendation
2 of 3