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.

FIBER-LK (Fiber Link)<br />

c. Error Type 18: the fiber link has been busied out via busyout fiber-link F P. To<br />

resolve this <strong>error</strong>, use release fiber-link F P to release the fiber link.<br />

d. Error Type 257: problem with the circuit path to the neighbor. See Repair procedures.<br />

e. Error Type 513: problem with the packet path to the neighbor. See Repair procedures.<br />

f. Error Type 769: problem with the control path from the neighbor. See Repair procedures.<br />

g. Error Type 1025: problem with the circuit path from the neighbor. See Repair procedures.<br />

h. Error Type 1281: problem with the packet path from the neighbor. See Repair procedures.<br />

Repair procedures<br />

For Note b <strong>and</strong> Notes d through h, perform the following steps:<br />

1. Perform the Fiber link fault isolation in Chapter 4: General troubleshooting in Maintenance<br />

Procedures for <strong>Avaya</strong> Aura Communication Manager, Media Gateways <strong>and</strong> Servers<br />

(03-300432).<br />

2. Enter display <strong>error</strong>s <strong>and</strong> if any of the listed slip <strong>error</strong>s exist, follow the associated<br />

repair procedures in SYNC (Port Network Synchronization) for slip <strong>error</strong>s.<br />

Table 119: Error Log Entries for Slip Errors<br />

Circuit Pack Name Error Log Name Number of Slips<br />

DS1 Interface DS1-BD 3073 to 3160<br />

Expansion Interface EXP-INTF 2305<br />

SNI SNI-BD 1537<br />

Tone-Clock TDM-CLK 1025<br />

UDS1 Interface UDS1-BD 3073 to 3160<br />

Issue 5 May 2009 465

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

Saved successfully!

Ooh no, something went wrong!