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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

This <strong>test</strong> runs on M/T-DIG (Maintenance/Test Digital Port).<br />

Table 397: Digital Port Sanity Test (#565) 1 of 3<br />

Error<br />

Code<br />

Test<br />

Result<br />

Description / Recommendation<br />

Digital Port Sanity Test (#565)<br />

1000 ABORT One of the digital ports is busy with background maintenance.<br />

1. Either wait for the port to become idle, or busyout both Maintenance/<br />

Test digital ports on the Maintenance/Test circuit pack with busyout<br />

port location (02) <strong>and</strong> busyout port location (03).<br />

2. If the ports were busied out, release them with release port<br />

location (02) <strong>and</strong> release port location (03).<br />

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

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

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

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

to TDM-BUS <strong>error</strong>s. A system is considered under heavy traffic when the<br />

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

Management <strong>and</strong> the Call Processing Occupancies together exceed 65%.<br />

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

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

<strong>error</strong>s.<br />

3. If the system has no TDM-BUS <strong>error</strong>s <strong>and</strong> is not h<strong>and</strong>ling heavy<br />

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

1004 ABORT The port was seized by a valid ISDN-PRI <strong>test</strong> call.<br />

1. Enter list isdnpri-<strong>test</strong>call to determine which call is using<br />

the port from the M/T Port column. Wait for the <strong>test</strong> call to complete<br />

as indicated in the Start Time <strong>and</strong> Duration fields, or abort the <strong>test</strong><br />

call with clear isdnpri-<strong>test</strong>call grp#/mem#, where grp#/<br />

mem# is determined from the B-Chel field of<br />

list isdnpri-<strong>test</strong>call.<br />

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

1 of 3<br />

Issue 5 May 2009 1365

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

Saved successfully!

Ooh no, something went wrong!