09.12.2012 Views

Server Alarms - Avaya Support

Server Alarms - Avaya Support

Server Alarms - Avaya Support

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Communication Manager Maintenance Object Repair Procedures<br />

Table 325: Descriptions and Recommendations for Error Types 3842-3942 8 of 9<br />

Error<br />

Code<br />

3942<br />

(cont’d)<br />

Description/Recommendation<br />

3. To interpret the receipt of Cause Value 102 from the far-end, look at a trace/<br />

protocol capture of the messaging taking place, and find the last message<br />

received from the far-end before Cause Value 102 is received. The timer that<br />

expired is most likely the Layer 3 timer associated with that last message. If<br />

Communication Manager generated a message in between those two events<br />

that should have stopped the timer, the cause might be:<br />

a. The far-end never saw the message because the message was corrupted<br />

in transmission by noise on the D-Channel. Check for any type of T1/E1<br />

facility errors.<br />

b. The far-end is experiencing a high traffic condition and did not have the<br />

processing time to parse the sent message before the timer expired.<br />

c. Even though the message was seen to be generated in an internal<br />

Communication Manager trace, the message was never transmitted out<br />

onto the D-Channel. Perform an external protocol capture on the<br />

D-Channel to confirm the transmission of the suspect message.<br />

4. If Communication Manager did not respond to the receipt of the last<br />

message from the far-end, then Communication Manager internal hardware<br />

and software become suspect, and troubleshooting the problem must<br />

proceed from that point.<br />

5. Communication Manager administration that can contribute to seeing timer<br />

expiry errors:<br />

a. Trunk group form: Incoming call handling table. If the Per call CPN/BN<br />

field is incorrectly populated in comparison to how the CO is programmed<br />

to send CPN or BN, it causes Communication Manager to send a<br />

FACILITY message to the CO requesting CPN/BN information and the CO<br />

will never respond. Communication Manager will log many timer expiry<br />

errors against the signaling group (Error Type 1, Aux Data 13).<br />

b. DS1 form: Protocol version: If Communication Manager is running custom<br />

protocol (protocol version A) and is connected to a Nortel DMS central<br />

office running custom protocol, Communication Manager will log timer<br />

expiry errors against the signaling group for DISCONNECT problems<br />

(Error Type 1, Aux Data 4) during high traffic conditions.<br />

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

8 of 9

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

Saved successfully!

Ooh no, something went wrong!