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.

EXP-INTF (Expansion Interface Circuit Pack)<br />

2. If the alarm is not resolved within the next 15 minutes, replace the EI circuit pack<br />

reporting the alarm.<br />

3. If the alarm is not resolved within the next 15 minutes, replace the connected EI circuit<br />

pack, SNI circuit pack, or DS1 converter circuit pack.<br />

t. Error Type 3841: the EI has reported a loss of lock with the backplane system clock.<br />

u. Error Type 3842: the <strong>test</strong> that queries the EI for the state of the lock to the system clock has<br />

failed. A loss of lock condition is present.<br />

v. The counter associated with Error Types 3841 <strong>and</strong> 3842 is cleared when the query for the<br />

state of the clock-to-system-clock passes. Once the alarm is raised, this <strong>test</strong> is run every<br />

five minutes. However, the <strong>test</strong> is not part of any sequence that can be run on dem<strong>and</strong>. See<br />

previous Note p for the repair procedure.<br />

w. Error Type 10001: the EI circuit pack dropped one control message to the PN. This<br />

condition may have been observed as a call that did not complete correctly. No action is<br />

required.<br />

<strong>Dem<strong>and</strong></strong> <strong>test</strong> <strong>descriptions</strong> <strong>and</strong> <strong>error</strong> <strong>codes</strong><br />

Investigate <strong>test</strong>s in the order presented. By clearing <strong>error</strong>s associated with the first <strong>test</strong>, <strong>error</strong>s<br />

generated from other <strong>test</strong>s may also be cleared. Click on the link to see the full description of<br />

the <strong>test</strong>, <strong>error</strong> <strong>codes</strong>, <strong>and</strong> recommended actions.<br />

When <strong>test</strong>ing EI circuit packs to investigate problems, <strong>test</strong>s should always be run on both circuit<br />

packs on the associated fiber link, whether the circuit packs are both EI circuit packs, or one is a<br />

SNI circuit pack. This will provide a better indication of where a problem is located.<br />

When <strong>test</strong>ing of the EI is not possible, (for example, when the PN is down), see the Expansion<br />

Interface Manual Loopback Procedure.<br />

Order of Investigation Short Test<br />

Sequence<br />

Long Test<br />

Sequence<br />

D/ND 1<br />

Expansion Interface Fiber Out-of-Frame Query Test (#238) X X ND<br />

Expansion Interface Lightwave Transceiver Looparound Test<br />

(#242)<br />

X D<br />

Expansion Interface Control Chel Test (#316) X X ND<br />

Expansion Interface Neighbor Query Test (#237) X X ND<br />

Expansion Interface Local Looparound (#240) X X ND<br />

Expansion Interface 2-Way Transmission Test (#241) X X ND<br />

Expansion Interface Packet Interface Test (#589) X X ND<br />

The following <strong>test</strong> is executed as part of the reset board comm<strong>and</strong><br />

Expansion Interface Reset Test (#336) D<br />

Issue 5 May 2009 449

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

Saved successfully!

Ooh no, something went wrong!