Demand test descriptions and error codes - Avaya Support

j. Error Type 1537: Frame overrun at packet bus interface. This condition may be caused by
an on-board fault or by faulty data received on one of the circuit pack’s external ports. If any
of the ports on this circuit pack are alarmed, refer to the repair procedures for those MOs.
Error Type 1538: Circuit packet is hyperactive; that is, it is flooding the switch with
messages sent over the control chel. The circuit pack is taken out-of-service when a
threshold number of these errors is reported to the switch. Clear the alarm with busyout
board location, reset board location, test board location long clear,
release board location. If the error recurs within 10 minutes, then replace the circuit
pack.
k. Error Type 1793, 1794, 1795, 2306: the circuit pack is having problems transmitting data to
the packet bus.
Error Type 1793: Parity errors are detected when transmitting data to the packet bus.
Error Type 1794: Overflow of packet bus transmit buffers has occurred.
Error Type 1795: Circuit pack cot find end of frame when transmitting to packet bus.
Clear the alarm via the following commands: busyout board location, reset
board location, test board location long clear, release board
location. If the error recurs within 10 minutes, then replace the circuit pack.
Error Type 2306: This error occurs when the circuit pack detects an error in a received
frame from the packet bus. These errors are most likely caused by a packet bus
problem, but may be due to a circuit pack fault. An invalid Link Access Procedure Data
(LAPD) frame error occurs if the frame contains a bad cyclical redundancy check
(CRC), is greater than the maximum length, or violates the link level protocol. When
bus parity errors are reported, the LANBIC Receive Parity Error Counter test (#595)
should be performed to determine whether the condition had cleared. See Isolating
and repairing packet-bus faults in Maintenance Procedures for Avaya Aura
Communication Manager, Media Gateways and Servers (03-300432) to determine
whether the problem is isolated to this circuit pack or is caused by packet bus faults.
l. Error Type 3330: A critical failure has been detected in the packet bus interface of the
circuit pack. This failure may be due to either a packet bus or to an on-board fault. If the
packet bus is alarmed, see PKT-BUS (Packet Bus) and Isolating and repairing packet-bus
faults in Maintenance Procedures for Avaya Aura Communication Manager, Media
Gateways and Servers (03-300432) for recommended repair procedures. The probability of
this error being related to packet bus problems increases with the number of ISDN-BRI
circuit packs displaying this error.
If the packet bus is not alarmed, reset the circuit pack with busyout board location
and reset board location. If the Circuit Pack Restart Test (#594) passes, then the
on-board circuitry is healthy. Retire the alarm with test board location long
clear. If the Circuit Pack Restart test (#594) fails, replace the circuit pack. If the problem
persists after complying with the above instructions, then follow normal escalation
procedures.
212 Maintenance Alarms for Communication Manager, Media Gateways and Servers