Server Alarms - Avaya Support

PKT-INT (Packet Interface)
m. Error Type 2305: parity failure was detected by the packet bus interface. The Packet
Interface received packets with parity errors from the packet bus.
1. Check for errors logged against the packet bus and Maintenance/ Test circuit pack. Refer
to repair procedures to clear those errors first.
2. Check every other circuit pack connected to the packet bus in the same cabinet. Packet
bus failures may be caused by a faulty circuit pack connected to the backplane or bent
pins on the back plane.
3. If the problem still exists, use test packet-interface, and follow repair procedures
described for Packet Interface Read and Clear Counters (#887).
n. Error Type 2561: Active-Standby Peer Link test failure indicating a possible failure of the:
● Active IPSI’s Packet Interface
● Standby IPSI’s Packet Interface
If the number of errors exceeds a defined threshold, a Minor alarm is raised. For more
information, refer to the repair procedures of Active-Standby Peer Link Test (#888).
o. Error Type 2817: Standby Packet Interface Translation RAM failure. A MINOR alarm is
raised when there are 1 to 5 bad locations and a MAJOR alarm is raised when there are 5
or more bad locations. Use test packet-interface, and follow repair procedures
described for Packet Interface Read and Clear Counters (#887).
p. Error Types 3074, 3073, and 3072: PKT-INT Transmit Buffer Overflow, the number of
transmit buffers required by software exceeded the number available. Error Type 3074 is
generated when the PKINT sends an inline hardware error to maintenance software,
indicating transmit buffer overflow. As part of the background recovery action for this error,
maintenance software automatically runs the Packet Interface Maintenance Looparound
Test (#886). If that test fails, maintenance software generates Error Types 3073 and 3072,
and it requests a system WARM restart. If, after the WARM restart, transmit buffer overflow
errors continue to be reported, maintenance software generates Error Code 100 and it
resets the PKT-INT. These errors may be the result of system overload due to a problem
with communication between the PKT-INT and the PNs.
1. Check for errors logged against the Expansion Interface circuit pack, the Switch Node
Interface circuit pack, Packet Gateway circuit pack, the Packet Data Line circuit packs
associated with the System Ports, BRI Line circuit packs and BRI endpoints, and the
Universal DS1 circuit packs supporting PRI service. Clear errors against those
components first.
2. Use test packet-interface short against the Packet Interface associated with
the error. If the Packet Interface Maintenance Looparound Test (#886) passes, the alarm
will clear. If the test fails, repeat the test 5 times.
3. If it continues to fail, follow normal escalation procedures.
Communication Manager Release 5.0 Issue 4 January 2008 1103