09.12.2012 Views

Server Alarms - Avaya Support

Server Alarms - Avaya Support

Server Alarms - Avaya Support

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Server</strong> <strong>Alarms</strong><br />

DUP (Duplication Manager)<br />

The Duplication Manager process, via coordination of the Arbiter process, runs on the servers<br />

to control data shadowing between them.<br />

At the physical and data-link layers, an Ethernet-based duplication link provides a TCP<br />

communication path between each server’s Duplication Manager to enable their control of data<br />

shadowing. This TCP/IP link provides the actual data shadowing for software duplication. For<br />

hardware duplication, there is an additional fiber optic link between the duplication memory<br />

boards that provides the data shadowing.<br />

Table 10: DUP <strong>Alarms</strong> describes the Duplication Manager’s alarms and their troubleshooting<br />

procedures.<br />

See ARB (Arbiter) and DAJ1/DAL1/DAL2 (Duplication Memory Board) for more information.<br />

Table 10: DUP <strong>Alarms</strong> 1 of 4<br />

Event<br />

ID<br />

Alarm<br />

Level<br />

Alarm Text, Cause/Description, Recommendation<br />

1 MAJ “Duplication card error” — The Duplication Manager determined that the<br />

duplication card is not functioning, but it cannot distinguish between a bad<br />

card, an unplugged card, or a bad fiber link.<br />

Follow steps 1 - 7 if using the Web Interface. Follow steps 8 - 14 if using<br />

the Linux command line interface.<br />

1. Using the Web Interface: Check the physical fiber connectivity at<br />

each server.<br />

2. Verify the alarm by accessing the trace log by:<br />

a. Selecting the View System Logs diagnostic and<br />

Logmanager Debug trace<br />

b. Specifying the Event Range for the appropriate time frame<br />

c. Matching the “dup” pattern<br />

3. Examine the trace-log query’s output for one of these messages:<br />

“glbi: couldn't open Dup Card, errno=. ndm exiting”<br />

“glbi: mmap failed, errno=. ndm exiting”<br />

“Haven't heard from active dupmgr. Dup fiber link down.”<br />

“san_check_rsp() FAILED: Dup Fiber link down.”<br />

4. See if the dup link is both “up” and “refreshed” from the Web<br />

interface’s <strong>Server</strong> section by selecting View Summary Status<br />

5. If so, manually clear the alarm by selecting <strong>Alarms</strong> and Notification,<br />

the appropriate alarm, and Clear<br />

58 Maintenance <strong>Alarms</strong> for <strong>Avaya</strong> Communication Manager, Media Gateways and <strong>Server</strong>s<br />

1 of 4

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!