DEFINITY Enterprise Communications Server Release 7
Maintenance for R7r
555-230-126 Issue 4
June 1999
Maintenance Object Repair Procedures
9-238ATM-SGRP (ATM Signaling Group)
9
f. Error Type 1793: failure of the Layer 2 Query Test for the primary signaling
channel.
■Excessive AAL - The AAL layer is experiencing an excessive
number of errors in trying to reconstruc t Service Data Unit (SDUs).
Possible causes:
— Something may b e wrong with the ATM switch.
— The communic ation paths on the other side of the ATM
switch may be noisy.
— The sending node might not be healthy. It could also be a
problem with cong estion on the ATM switch.
g. Error Type 2305: the Remote Layer 3 Query Test (#637) failed. A specific
message was sent to the far-end switc h, and it did not resp ond within the
allotted time.
1. Investigate elements of the ATM D-channel(s) (ATM-DCH) for both
this switch and the Far-end switc h.
If Test #637 fails twice in a row, the B-channels are alarmed and mad e
unavailable for outgoing calls (although inc oming calls are still acc epted).
When Test #637 succeeds and the Far-end switch start s responding
properly, the ATM Trunk (B-channels) are placed back into norm al
operation and their alarms retired .
h. Error Type 3585: A SERV or SERV ACK ISDN D-channel message has
been received by a no n-US-type interface (country option other than 1 on
the DS1 administration form). However, these messages are used only for
duplex NFAS signaling, which is supported by country protocol 1.
Thus, there may be a mismatch in administration between the local and
far-end switches.
1. Consult with the customer’s network provid er to determine whether
the D-channel is set up correc tly on the far-end switch.
i. Error Type 3840-3928: These error types are used to report certain error
messages received b y the ATM-SGRP Signaling Group for one of its
associated B-channels. The Aux Data field is the port number of the
B-channel from which the messag e was received.
The error code generated eq uals 3840+
x
, where
x
is a Cause Value
defined by the ISDN PRI Specification. Note that there is no Test to Clear
Value for these error types; selected ISDN cause values are p laced in the
log when they are received, b ut no direct action or alarming is performed
solely in response to receiving them. They provide added data that may
prove useful when tracking d own obscure networking and routing
problems. Table 9-102 provides more information about this range o f Error
Codes: