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.

Communication Manager Maintenance Object Repair Procedures<br />

This test verifies the connectivity of a BRI port across the TDM Bus. It aborts if calls associated<br />

with the port are in progress. Failure of this test indicates an on-board fault associated with the<br />

port hardware on the circuit pack.<br />

This looparound test runs the following individual tests on the two B-Channels (B1 and B2)<br />

associated with the port:<br />

● Looparound test across the TDM Bus for B1.<br />

● Conference Circuit test for B1.<br />

● Looparound test across the TDM Bus for B2.<br />

● Conference Circuit test for B2.<br />

The tests are run in the above order. If one test fails, the remaining tests in the sequence are not<br />

executed and an error code is returned at that point.<br />

This test runs on BRI-PORT (ISDN-BRI Port) and TBRI-PT (ISDN Trunk-Side BRI Port).<br />

Table 509: BRI Port Local TDM Looparound Test (#619) 1 of 3<br />

Error<br />

Code<br />

Test<br />

Result<br />

Description / Recommendation<br />

1000 ABORT The system resources required to run this test are not available. The port<br />

may be busy with a valid call.<br />

1. Enter display port location to determine the station extension<br />

or trunk group/member number of the port.<br />

2. Enter status bri-port location to determine the service state<br />

of the port. If the port is in use, wait until the port is idle before<br />

retesting.<br />

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

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

1002 ABORT The system could not allocate time slots for the test. The system may be<br />

under heavy traffic conditions, or it may have time slots out-of-service<br />

due to TDM-BUS errors. A system is considered under heavy traffic<br />

when the Call Processing Occupancy is greater than 50% or when the<br />

System Management and the Call Processing Occupancies together<br />

exceed 65%.<br />

1. Enter status health to view the occupancy measurements.<br />

2. Enter display errors and resolve any TDM-BUS (TDM Bus)<br />

errors.<br />

3. If the system has no TDM-BUS errors and is not handling heavy<br />

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

1752 Maintenance <strong>Alarms</strong> for <strong>Avaya</strong> Communication Manager, Media Gateways and <strong>Server</strong>s<br />

1 of 3

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

Saved successfully!

Ooh no, something went wrong!