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.

4. If Test #799 passes, run the Far-End Internal Loopback Test (#797) via <strong>test</strong><br />

ds1-facility location long. If Test #797 passes, go to step 6. If the <strong>test</strong> fails,<br />

run the Near-End External Loopback Test (#799) using <strong>test</strong> ds1-facility<br />

location external-loopback at the other end of the DS1 converter complex,<br />

<strong>and</strong> repeat steps 2 <strong>and</strong> 3 for the other endpoint.<br />

If this is not a critical-reliability system <strong>and</strong> if there is only one DS1 facility, then Test<br />

#799 can only be executed at the end that is closer to the server relative to the DS1<br />

converter circuit pack at the end of the DS1 converter complex. If the <strong>test</strong> cot be<br />

executed for this reason, then replace the cables, connectors <strong>and</strong> the CSU at the other<br />

end of the DS1 converter complex.<br />

5. If the problem could not be isolated by the near-end external loopback <strong>test</strong>s, then the<br />

fault should be between CSU A <strong>and</strong> CSU B. Contact T1 Network Service to resolve<br />

the problem(*).<br />

6. 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 />

TDM-CLK, or SNC-BD <strong>error</strong>s. For TN574 boards <strong>and</strong> TN1654 boards in T1 mode,<br />

check line equalization settings as described in DS1 Converter-1 <strong>and</strong> DS1 Converter-2<br />

Line Compensation.<br />

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

EXP-INTF, <strong>and</strong> SNI-BD <strong>error</strong>s for the Fiber Endpoints. Enter display <strong>error</strong>s <strong>and</strong><br />

follow the associated repair procedures for any FIBER-LK <strong>error</strong>s for this fiber link.<br />

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

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

the DS1 converter complex.<br />

If D4 framing mode is used, an in-b<strong>and</strong> alarm signal (RFA) will be transmitted that will<br />

corrupt the transmit data on this facility.<br />

h. Error Type 1281:<br />

Aux Data None: This entry in the DS1 Facility Error Log occurs only prior to Release V5.<br />

The DS1 converter circuit pack's neighbor (the DS1 converter circuit pack at the other end<br />

of the DS1 converter complex) is unable to frame up on the signal being sent to it by this<br />

DS1 converter circuit pack on this DS1 facility. The far-end facility will be in LFA state. To<br />

isolate faults for this case, follow the repair procedure for Error Type #1025 for the other<br />

end of the DS1 facility. Note that references to the near <strong>and</strong> far ends are reversed, for<br />

example, the neighbor is now the near end. If D4 framing is used, received data will be<br />

corrupted as well as transmitted data.<br />

Aux Data 1: indicates that the facility is detecting a Remote Frame Alarm (RFA), also<br />

known as the YELLOW alarm, being sent by the remote DS1 endpoint. This Yellow alarm<br />

corresponds to the yellow F2 state documented in CCITT Recommendation I.431. If D4<br />

framing is used, received data will be corrupted in addition to transmitted data.<br />

366 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!