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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Packet Interface Maintenance Looparound Test (#886)<br />

Table 460: Packet Interface Maintenance Looparound Test (#886) 2 of 3<br />

Error<br />

Code<br />

Test<br />

Result<br />

Description / Recommendation<br />

1–5 FAIL Fail Codes 1 - 4:<br />

1 = Did not receive looparound data<br />

2 = Looparound data not correct length<br />

3 = Looparound data did not match<br />

4 = Transmit buffer exhaustion<br />

Either the system could not establish a looparound link from the IPSI’s<br />

Packet Interface module back to itself, or it could not receive data that<br />

was sent on one side of the looparound link.<br />

1. Enter <strong>test</strong> packet-interface location to retry the <strong>test</strong>.<br />

If the same Error Code is observed, the system automatically<br />

attempts to reset the Packet Interface <strong>and</strong> clear the problem.<br />

2. Retry the comm<strong>and</strong>. If the <strong>test</strong> fails, replace the IPSI circuit pack<br />

that has the failing Packet Interface.<br />

3. If the <strong>test</strong> continues to fail after replacing the IPSI circuit pack,<br />

enter <strong>test</strong> packet P long.<br />

If any of the <strong>test</strong>s fail, the fault may be on the packet bus. See<br />

PKT-BUS (Packet Bus) for the recommended repair procedures.<br />

4. If the <strong>test</strong> continues to fail after the IPSI circuit pack is replaced,<br />

<strong>and</strong> with no other alarms associated with the packet bus or circuit<br />

packs connected to the packet bus, follow normal escalation<br />

procedures.<br />

2 of 3<br />

Issue 5 May 2009 1531

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

Saved successfully!

Ooh no, something went wrong!