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.

Table 462: Active-St<strong>and</strong>by Peer Link Test (#888) 3 of 3<br />

Error<br />

Code<br />

Test<br />

Result<br />

NO<br />

BOARD<br />

Description / Recommendation<br />

Packet Interface Reset Test (#889)<br />

Packet Interface Reset Test (#889)<br />

The IPSI circuit pack’s Packet Interface module is assigned but is not<br />

detected as physically present.<br />

1. If the IPSI circuit pack is present, replace it.<br />

2. If not, insert a TN2312AP IPSI circuit pack in the assigned slot, <strong>and</strong><br />

rerun the <strong>test</strong>.<br />

3 of 3<br />

The reset action initializes the Packet Interface firmware on the IPSI circuit pack <strong>and</strong> runs a<br />

comprehensive set of diagnostic <strong>test</strong>s.<br />

The dem<strong>and</strong> reset action aborts if the specified IPSI circuit pack’s Packet Interface module is in<br />

the active in-service state.<br />

An IPSI circuit pack’s Packet Interface module is put in the out-of-service state automatically if it<br />

resets 3 times by background maintenance within the last 15 minutes, independent of the<br />

results of the reset action.<br />

If the Packet Interface module is on the st<strong>and</strong>by IPSI (S8700-series Fiber-PNC: <strong>and</strong> this is a highor<br />

critical-reliability system), the dem<strong>and</strong> reset action runs, independent of the service state.<br />

This <strong>test</strong> runs on PKT-INT (Packet Interface).<br />

Table 463: Packet Interface Reset Test (#889) 1 of 3<br />

Error<br />

Code<br />

Test<br />

Result<br />

Description / Recommendation<br />

1334 ABORT The Packet Interface modules’s comm<strong>and</strong> queue is full. This should be<br />

a temporary condition caused by a high rate of comm<strong>and</strong>s being sent to<br />

a Packet Interface module. Continued operation with a full comm<strong>and</strong><br />

queue causes a system WARM restart that could escalate to more<br />

severe restart levels.<br />

1. Retry the comm<strong>and</strong> at 10 second intervals up to 5 times.<br />

1 of 3<br />

Issue 5 May 2009 1539

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

Saved successfully!

Ooh no, something went wrong!