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 />

Table 381: Conference Circuit Test (#7) 5 of 7<br />

Error<br />

Code<br />

Test<br />

Result<br />

Description / Recommendation<br />

1020 ABORT The test did not run due to either a previously existing error on the<br />

specific port or a more general circuit pack error.<br />

1. Examine the Error Log for existing errors against this port or the<br />

circuit pack and attempt to diagnose and resolve the previously<br />

existing error.<br />

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

1412 ABORT This test does not run on media modules or media gateways. Ignore.<br />

2000 ABORT Response from the test was not received within the time allowed.<br />

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

2053 ABORT At least one of the following errors is found on the DS1 circuit pack:<br />

● 1281 – Loss of signal<br />

● 1793 – Blue alarm<br />

● 2049 – Red alarm<br />

● 2305 – Yellow alarm<br />

● 1537 – Hyperactivity<br />

Look for these Error Types in the error log, and follow the procedures<br />

given in the DS1-BD (DS1 Interface Circuit Pack) or UDS1-BD (UDS1<br />

Interface Circuit Pack) maintenance documentation for the listed Error<br />

Types.<br />

2100 ABORT System resources required to run this test are not available.<br />

1. Resolve any TONE-PT (Tone Generator) errors.<br />

2. If there are no TONE-PT errors in the error log, retry the test at<br />

1-minute intervals for a maximum of 5 times.<br />

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

5 of 7

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

Saved successfully!

Ooh no, something went wrong!