Server Alarms - Avaya Support

Table 10: DUP Alarms 4 of 4
Event
ID
2
(cont’d)
Alarm
Level
Back to: Linux Server Alarms
Alarm Text, Cause/Description, Recommendation
DUP (Duplication Manager)
MAJ 6. Using the Linux Command Line Interface: Access the trace log by
entering logv -t ts
7. 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.”
8. Enter server and check if the dup link is “up”.
9. If so, manually clear the alarm by entering almclear -n #id
If not, check the duplication interface’s Ethernet connectivity by
entering pingall -d
10. If pingall passes, enter statapp and check the other server’s
applications.
3 MAJ Duplication Card Error - Double Bit SDRAM error. This alarm is usually
seen on the active server and indicates a potential problem with the
duplication card on that server.
1. If the alarm occurs multiple times, replace the duplication card.
4 MAJ Duplication Card Error - Double Frame CRC error. This alarm is usually
seen on the standby server and indicates a possible problem with the fiber
link between the servers.
1. If the alarm occurs multiple times, replace the fiber link.
2. If the alarm still occurs after replacing the fiber link, there might be a
problem with one of the duplication cards. Escalate for a probable
server replacement.
4 of 4
Communication Manager Release 5.0 Issue 4 January 2008 61