19.12.2012 Views

Demand test descriptions and error codes - Avaya Support

Demand test descriptions and error codes - Avaya Support

Demand test descriptions and error codes - Avaya Support

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

PKT-INT (Packet Interface)<br />

l. Error Type 2049: LAPD Received Buffer Overflow <strong>error</strong>. The Packet Interface‘s packet bus<br />

receive buffer overflowed. For more information, refer to the repair procedures of Packet<br />

Interface Read <strong>and</strong> Clear Counters (#887).<br />

m. Error Type 2305: parity failure was detected by the packet bus interface. The Packet<br />

Interface received packets with parity <strong>error</strong>s from the packet bus.<br />

1. Check for <strong>error</strong>s logged against the packet bus <strong>and</strong> Maintenance/ Test circuit pack.<br />

Refer to repair procedures to clear those <strong>error</strong>s first.<br />

2. Check every other circuit pack connected to the packet bus in the same cabinet.<br />

Packet bus failures may be caused by a faulty circuit pack connected to the backplane<br />

or bent pins on the back plane.<br />

3. If the problem still exists, use <strong>test</strong> packet-interface, <strong>and</strong> follow repair<br />

procedures described for Packet Interface Read <strong>and</strong> Clear Counters (#887).<br />

n. Error Type 2561: Active-St<strong>and</strong>by Peer Link <strong>test</strong> failure indicating a possible failure of the:<br />

● Active IPSI’s Packet Interface<br />

● St<strong>and</strong>by IPSI’s Packet Interface<br />

If the number of <strong>error</strong>s exceeds a defined threshold, a Minor alarm is raised. For more<br />

information, refer to the repair procedures of Active-St<strong>and</strong>by Peer Link Test (#888).<br />

o. Error Type 2817: St<strong>and</strong>by Packet Interface Translation RAM failure. A MINOR alarm is<br />

raised when there are 1 to 5 bad locations <strong>and</strong> a MAJOR alarm is raised when there are 5<br />

or more bad locations. Use <strong>test</strong> packet-interface, <strong>and</strong> follow repair procedures<br />

described for Packet Interface Read <strong>and</strong> Clear Counters (#887).<br />

p. Error Types 3074, 3073, <strong>and</strong> 3072: PKT-INT Transmit Buffer Overflow, the number of<br />

transmit buffers required by software exceeded the number available. Error Type 3074 is<br />

generated when the PKINT sends an inline hardware <strong>error</strong> to maintenance software,<br />

indicating transmit buffer overflow. As part of the background recovery action for this <strong>error</strong>,<br />

maintenance software automatically runs the Packet Interface Maintenance Looparound<br />

Test (#886). If that <strong>test</strong> fails, maintenance software generates Error Types 3073 <strong>and</strong> 3072,<br />

<strong>and</strong> it requests a system WARM restart. If, after the WARM restart, transmit buffer overflow<br />

<strong>error</strong>s continue to be reported, maintenance software generates Error Code 100 <strong>and</strong> it<br />

resets the PKT-INT. These <strong>error</strong>s may be the result of system overload due to a problem<br />

with communication between the PKT-INT <strong>and</strong> the PNs.<br />

1. Check for <strong>error</strong>s logged against the Expansion Interface circuit pack, the Switch Node<br />

Interface circuit pack, Packet Gateway circuit pack, the Packet Data Line circuit packs<br />

associated with the System Ports, BRI Line circuit packs <strong>and</strong> BRI endpoints, <strong>and</strong> the<br />

Universal DS1 circuit packs supporting PRI service. Clear <strong>error</strong>s against those<br />

components first.<br />

2. Use <strong>test</strong> packet-interface short against the Packet Interface associated with<br />

the <strong>error</strong>. If the Packet Interface Maintenance Looparound Test (#886) passes, the<br />

alarm will clear. If the <strong>test</strong> fails, repeat the <strong>test</strong> 5 times.<br />

3. If it continues to fail, follow normal escalation procedures.<br />

Issue 5 May 2009 741

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

Saved successfully!

Ooh no, something went wrong!