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.

Maintenance <strong>Dem<strong>and</strong></strong> Tests<br />

Table 403: Expansion Interface Packet Interface Test (#589) 4 of 5<br />

Error<br />

Code<br />

Test<br />

Result<br />

Description / Recommendation<br />

1421 ABORT This abort code appears only when the EI circuit pack addressed in the<br />

<strong>test</strong> comm<strong>and</strong> is one that terminates a fiber link between two PNs in a<br />

direct connect system. It indicates that the <strong>test</strong> failed, but that this <strong>test</strong><br />

was run on the PN EI board that is: a) in the same PN as the board under<br />

<strong>test</strong> b) on the active PNC (if duplicated) c) terminates the fiber from the<br />

PN. The EI <strong>test</strong>ed is probably not at fault.<br />

1. Enter display alarms <strong>and</strong> follow the EXP-INTF repair<br />

procedures for any alarms against the PN EI that is:<br />

a. In the same PN as the board just <strong>test</strong>ed<br />

b. On the active PNC<br />

c. Terminates the fiber link from the PN<br />

2. If there are no alarms logged against that EI, run Test #589 on it <strong>and</strong><br />

follow procedures for this <strong>test</strong>.<br />

3. Run this <strong>test</strong> again.<br />

1422 ABORT This abort code is valid <strong>and</strong> will only appear when the EI circuit pack<br />

under <strong>test</strong> resides in a PN of a system with a Center Stage Switch<br />

configuration. It means that the <strong>test</strong> failed, but that this <strong>test</strong> was then run<br />

on the PN EI on the same PNC as the EI under <strong>test</strong> <strong>and</strong> that <strong>test</strong> failed.<br />

This means that the EI originally <strong>test</strong>ed is probably not at fault.<br />

1. Resolve any alarms that are logged against the PN EI that is on the<br />

same PNC as the EI under <strong>test</strong>.<br />

2. If there are no alarms logged against the PN EI, run Test #589<br />

against the PN EI <strong>and</strong> follow procedures for this <strong>test</strong>.<br />

3. Run this <strong>test</strong> again.<br />

2000 ABORT Response to the <strong>test</strong> was not received within the allowed time.<br />

1. Retry the comm<strong>and</strong> at 1-minute intervals up to 3 times.<br />

2060 ABORT The link on the packet bus being used to perform the <strong>test</strong> has failed.<br />

1. Retry the comm<strong>and</strong> at 1-minute intervals up to 3 times.<br />

2. If the <strong>test</strong> continues to abort, enter display <strong>error</strong>s <strong>and</strong> resolve<br />

any PKT-INT <strong>error</strong>s.<br />

1380 Maintenance Alarms for Communication Manager, Media Gateways <strong>and</strong> Servers<br />

4 of 5

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

Saved successfully!

Ooh no, something went wrong!