09.12.2012 Views

Server Alarms - Avaya Support

Server Alarms - Avaya Support

Server Alarms - 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.

Table 516: Signaling Link Status Test (#626) 2 of 2<br />

Error<br />

Code<br />

Test<br />

Result<br />

Description / Recommendation<br />

Signaling Link Status Test (#626)<br />

1187 ABORT The circuit pack, port, or station may have been busied out by command.<br />

1. Look in the Error Log for Error Type 18 (busied out) for ASAI-BD,<br />

ASAI-PT, ASAI-EPT, BRI-BD, BRI-PORT, or BRI-SET.<br />

2. If this Error Type is present for ASAI-EPT or BRI-SET only, enter<br />

release station extension and run the test again.<br />

3. If this Error Type is present for ASAI-PT and ASAI-EPT or BRI-PORT<br />

and BRI-SET, use release port location and run the test<br />

again.<br />

4. If this Error Type is present for ASAI-BD, ASAI-PT, and ASAI-EPT or<br />

BRI-BD, BRI-PORT, and BRI-SET, enter release board<br />

location and run the test again.<br />

2012 ABORT Internal system error.<br />

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

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

2. If the test continues to abort, escalate the problem.<br />

1113 FAIL The signaling link is not “bound” to the adjunct or endpoint.<br />

For BRI endpoints supporting MIM initialization, this error indicates<br />

that the endpoint has not been bound to a signaling link (that is, SPID<br />

initialization has not been completed). Since the signaling link<br />

associated with the endpoint is not identified until SPID initialization<br />

completes, this error does not imply that the signaling link is<br />

connected or disconnected at Layer 2 nor does it provide the status<br />

of TEI assignment for the endpoint.<br />

For ASAI adjuncts and BRI endpoints not supporting MIM<br />

initialization, this error indicates that the link is disconnected at Layer<br />

2. Since the signaling link associated with the endpoint has been<br />

identified via administration, the link is only “unbound” from the<br />

endpoint when it is disconnected.<br />

1. Enter status bri-port location and see the associated<br />

procedures in BRI-PORT (ISDN-BRI Port).<br />

PASS The signaling link is connected at Layer 2 and “bound” to the BRI endpoint<br />

or ASAI adjunct.<br />

2 of 2<br />

Communication Manager Release 5.0 Issue 4 January 2008 1765

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

Saved successfully!

Ooh no, something went wrong!