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.

3. If the problem still persists, replace the DS1 converter circuit pack.<br />

p. Error Type 769, Aux Data 6: A minor FOI receive <strong>error</strong> occurred that affects data received<br />

from the DS1 facility <strong>and</strong> transmitted to the fiber link. Replace the DS1 converter circuit<br />

pack.<br />

q. Error Type 769, Aux Data 7: A minor on-board hardware failure exists on the processor/<br />

control hardware on the DS1 converter circuit pack. Replace the DS1 converter circuit pack.<br />

r. Error Type 1281: For TN574 DS1 converter boards, this <strong>error</strong> indicates that the facility<br />

masks or the clock reference masks do not match between the two DS1 converter circuit<br />

packs in the DS1 converter complex.<br />

For TN1654 DS1 converter boards, this <strong>error</strong> indicates that the facility masks do not match<br />

between the two DS1 converter circuit packs in the DS1 converter complex.<br />

Alarm should clear in 15 minutes.<br />

1. If the problem persists, reset both DS1 converter circuit packs in the DS1 converter<br />

complex via reset board.<br />

2. If the problem persists, replace this DS1 converter circuit pack.<br />

3. If the problem persists, replace the DS1 converter circuit pack at the other end of the<br />

DS1 converter complex.<br />

s. Error Type 1537: The two TN574 DS1 converter circuit packs in the DS1 converter<br />

complex do not have the same firmware vintage. The TN574 DS1 converter with the older<br />

vintage should be replaced. This <strong>error</strong> does not apply to TN1654 boards.<br />

t. Error Type 1793: Fiber Loss of Frame Alignment (LFA) alarm occurred at the other end of<br />

the DS1 converter complex. The DS1 converter circuit pack at the other end of the DS1<br />

converter complex cot frame up on the signal coming into the circuit pack from the fiber.<br />

(The neighbor DS1 converter circuit pack detected the LFA <strong>and</strong> relayed this information to<br />

this DS1 converter circuit pack via the DS1 control chel.) The amber LED will flicker at a<br />

5-Hz rate (on for 0.1 second, off for 0.1 second).<br />

1. Execute list fiber-link to determine the Fiber Endpoint that is connected to the<br />

DS1 converter circuit pack. Enter display <strong>error</strong>s <strong>and</strong> follow the associated repair<br />

procedures for any EXP-INTF (Expansion Interface Circuit Pack) or SNI-BD (SNI<br />

Circuit Pack) <strong>error</strong>s for the Fiber Endpoints. Enter display <strong>error</strong>s <strong>and</strong> follow the<br />

associated repair procedures for any FIBER-LK (Fiber Link) <strong>error</strong>s for this fiber link.<br />

2. If the problem still persists, check for excessive slips <strong>and</strong> synchronization problems.<br />

Enter display <strong>error</strong>s <strong>and</strong> follow the associated repair procedures for any SYNC<br />

(Port Network Synchronization), TDM-CLK (TDM Bus Clock), <strong>and</strong> SNC-BD (Switch<br />

Node Clock Circuit Pack) <strong>error</strong>s.<br />

3. If the problem still persists, run the Far-End DS1 converter Circuit Pack Loopback <strong>test</strong><br />

(#788) on this DS1 converter circuit pack via <strong>test</strong> board location long. This<br />

<strong>test</strong> indicates if the neighbor DS1 converter circuit pack hardware is functioning. If the<br />

<strong>test</strong> fails, replace the DS1 converter circuit pack at the other end of the DS1 converter<br />

complex.<br />

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

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

Saved successfully!

Ooh no, something went wrong!