Server Alarms - Avaya Support

Server Alarms
Table 10: DUP Alarms 3 of 4
Event
ID
Alarm
Level
Alarm Text, Cause/Description, Recommendation
2 MAJ “Duplication link down” — One server’s Duplication Manager cannot
communicate with the other server’s Duplication Manager.
Follow steps 1 - 5 if using the Web Interface. Follow steps 6 - 10 if using
the Linux Command Line Interface.
1. Using the Web Interface: Access the trace log 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 “ndm” or "DUPLICATION" pattern
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.”
3. Check if the dup link is “up” from the Web interface’s Server section by
selecting View Summary Status
4. If so, manually clear the alarm by selecting Alarms and Notification,
the appropriate alarm, and Clear
If not, check the duplication interface’s Ethernet connectivity by
selecting the Execute Pingall diagnostic
5. If pingall passes, check the other server’s applications by selecting
View Process Status
60 Maintenance Alarms for Avaya Communication Manager, Media Gateways and Servers
3 of 4