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.

Link Status Test (#601)<br />

Link Status Test (#601)<br />

This <strong>test</strong> determines the state of the call-control signaling link for the TN799 CLAN-BD (Control<br />

LAN Circuit Pack) <strong>and</strong> VAL-BD (Voice announcements over LAN Circuit Pack). If the signaling<br />

link is physically connected, the <strong>test</strong> sends a <strong>test</strong> frame over the link <strong>and</strong> checks for a response.<br />

The <strong>test</strong> passes only if both the signaling link is connected <strong>and</strong> the <strong>test</strong> frame is successfully<br />

transmitted.<br />

A failure may indicate a problem with:<br />

● this circuit pack<br />

● the packet bus<br />

● the Packet Interface circuit pack<br />

Table 410: Link Status Test (#601) 1 of 2<br />

Error<br />

Code<br />

Test<br />

Result<br />

Description / Recommendation<br />

1125 ABORT RSCL link or circuit pack not in service.<br />

1. Release the circuit pack with release board location.<br />

2. Repeat the <strong>test</strong>.<br />

3. Escalate if the problem persists.<br />

2012 ABORT Could not allocate the necessary system resources to run this <strong>test</strong>.<br />

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

2100 ABORT Internal system <strong>error</strong>.<br />

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

2. If the problem persists, escalate the problem.<br />

2 FAIL The RSCL control link is disconnected.<br />

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

2. If the <strong>test</strong> continues to fail, run the Packet Interface <strong>test</strong> (#598) with<br />

<strong>test</strong> board location to determine if the problem is due to the<br />

circuit pack.<br />

3. If the Packet Interface <strong>test</strong> (#598) fails, see Packet Interface Test<br />

(#598) for repair procedures.<br />

4. If the Packet Interface <strong>test</strong> (#598) passes, refer to PKT-BUS<br />

(Packet Bus) repair procedures.<br />

1 of 2<br />

Issue 5 May 2009 1391

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

Saved successfully!

Ooh no, something went wrong!