Server Alarms - Avaya Support

Table 10: DUP Alarms 2 of 4
Event
ID
1
(cont’d)
Alarm
Level
Alarm Text, Cause/Description, Recommendation
DUP (Duplication Manager)
MAJ If not: 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
by selecting Interchange Servers
b. Busy out the standby server by selecting Busy Server
c. Release the standby server by selecting Release Server
6. If the problem persists, 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.
8. Using the Linux Command Line Interface: Check the physical fiber
connectivity at each server.
9. Enter logv -t ts to verify the alarm by accessing the trace log.
10. Examine the trace-log query’s output for one of these messages:
“glbi: couldn't open Dup Card, errno=. ndm exiting”
“glbi: mmap failed, errno=. ndm exiting”
“Haven't heard from active dupmgr. Dup fiber link down.”
“san_check_rsp() FAILED: Dup Fiber link down.”
11. Enter server and check if the dup link is both “up” and “refreshed”.
12. If so, manually clear the alarm by entering almclear -n #id
If not: Since the following commands cause a brief service outage,
they should only be executed at the customer’s convenience:
a. Enter server -if and select the force option to force a server
interchange and make the suspected server standby.
b. Enter server -b to busy out the standby server.
c. Enter server -r to release the standby server.
13. If the problem persists, try:
a. Replacing the fiber between the two servers
b. Rebooting the standby server
14. If the problem still persists, escalate for a probable server
replacement.
2 of 4
Communication Manager Release 5.0 Issue 4 January 2008 59