Demand test descriptions and error codes - Avaya Support

ISDN-PLK (ISDN-PRI Signaling Link Port)
b. Error Type 18: The D-Chel is demand busied out by command. No calls can be made over
this D-Chel.
c. Error Type 130: the circuit pack or media module has been removed or has been insane for
more than 11 minutes. To clear the error, reinsert or replace the circuit pack or media
module.
d. Error Type 1537: Link error. This error occurs when the port receives an invalid frame over
the D-Chel. This error normally indicates an off-board problem usually related to
transmission errors on the DS1 facility. Enter list measurements ds1-log for the
UDS1 TN464 circuit pack or DS1 Media Module where the D-chel resides. If the UDS1 or
MG-DS1 is reporting errors, the DS1 facility has experienced transmission problems that
could have caused the ISDN-PLK to report a Link Error.
If the UDS1 or MG-DS1 is not reporting errors, execute the long test sequence for the
D-Chel. Investigate any errors. If there are none, execute a long test sequence for the
UDS1 circuit pack (UDS1-BD) or DS1 Media Module (MG-DS1). Investigate any errors.
If no errors could be found by testing, the Link Error is probably not affecting service.
However, if this Link Error continues to be logged, follow normal escalation procedures.
e. Error Type 1793: UDS1 Interface circuit pack or DS1 Interface Media Module is out of
service. Look for and resolve UDS1-BD or MG-DS1 errors in the Hardware Error Log.
f. Error Type 3585: transmit FIFO Overflow error. The circuit pack is having problems
transmitting data to the packet bus, thus affecting the conveyance of signaling information
over the D-Chel. Specifically, this error occurs when the packet bus transmit buffers
overflow. This condition probably indicates a hardware problem.
The actual alarming level will depend on the options chosen via the set options
command. ISDN-PRI Signaling Link port alarms are treated as Station alarms, and their
default alarming option is to downgrade every alarm to Warning. The value shown in the
preceding table indicates the normal, unfiltered case (option “y” on the set options
screen).
g. Error Type 3841: Bad DLCI error. This error occurs when a LAPD frame is received across
the DS1 facility that contains a DLCI that does not have a valid entry in the on-board
translation memory. This error normally indicates an off-board problem usually related to a
broken endpoint or a state mismatch between a remote endpoint and the local
call-processing software. Maintenance will not start any testing or generate any alarms in
response to this error.
h. Error Type 3842: Receive FIFO Overflow error. This error occurs when the circuit pack or
media module detects an overflow of its receive buffers. If it occurs frequently, it may
indicate a LAPD parameter mismatch between the two endpoints of a packet-switched
connection. LAPD should be able to recover from this problem, but it may degrade the
performance of the LAN bus. Maintenance will not start any testing or generate any alarms
in response to this error.
i. Error Type 3843: The Signaling Port LAN Loopback test (#939) failed. Run the long test
sequence and note the results of the Signaling Port LAN Loopback Test (#939).
Issue 5 May 2009 547