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.

d. Error Type 23: the circuit pack has been logically administered but not physically installed.<br />

The alarm should clear when the circuit pact is installed.<br />

If the circuit pack is already installed:<br />

1. Run <strong>test</strong> board location long <strong>and</strong> look at any <strong>test</strong> failures or Error Codes<br />

generated.<br />

2. If the <strong>test</strong> does not clear <strong>error</strong> 23, then execute reset board location <strong>and</strong> run the<br />

long <strong>test</strong> again.<br />

If the reset/<strong>test</strong> does not clear <strong>error</strong> 23, replace the circuit pack.<br />

e. Error Type 125: wrong circuit pack has been physically inserted into a slot administered for<br />

an RC circuit pack.<br />

f. Error Type 130: an RC circuit pack has been physically inserted into a slot for which it has<br />

not been administered<br />

g. Error Type 257: transient communication problems between the switch <strong>and</strong> this circuit<br />

pack. Execute <strong>test</strong> board location <strong>and</strong> refer to the repair procedures for the Control<br />

Chel Looparound Test (#52).<br />

h. Error Type 513: This <strong>error</strong> indicates an on-board hardware failure. The system will<br />

continuously <strong>test</strong> the circuit pack <strong>and</strong> report the results approximately every 10 minutes. If<br />

the hardware problem is resolved, the alarm should clear in approximately 30 minutes. If the<br />

alarm does NOT clear in 30 minutes, then the circuit pack should be replaced.<br />

i. Error Type 769: this <strong>error</strong> can be ignored, but look for other <strong>error</strong>s on this circuit pack.<br />

j. Error Type 1025: this <strong>error</strong> is not service-affecting, <strong>and</strong> no action is required<br />

k. Error Type 1281: Execute <strong>test</strong> board location <strong>and</strong> refer to the repair procedures for<br />

RC NPE Allocation Test (#1336)<br />

l. Error Type 1537: this <strong>error</strong> occurs when an excessive number of up-link messages have<br />

been received by the circuit pack. Switch software will take the circuit pack out of service<br />

<strong>and</strong> alarm the circuit pack. Switch software will periodically (every 15 minutes) put the circuit<br />

pack back in service. If the problem still exists, the circuit pack will again be taken out of<br />

service. If the circuit pack does not exhibit the problem for a certain amount of time, the<br />

alarm will be resolved <strong>and</strong> the circuit pack will be left in service.<br />

m. .Error Type 1793: this <strong>error</strong> occurs if the RC detects a DECT protocol <strong>error</strong>.<br />

n. .Error Type 2049: Execute <strong>test</strong> board location <strong>and</strong> refer to the repair procedures for<br />

RC NPE Port Loop Test (#1316)<br />

o. .Error Type 2305: this <strong>error</strong> indicates a firmware checksum <strong>error</strong>.<br />

p. .Error Type 2561: this <strong>error</strong> indicates a firmware upgrade operations <strong>error</strong>.<br />

q. Error Type 2817: Execute <strong>test</strong> board location <strong>and</strong> refer to the repair procedures for<br />

RC Hardware Translation Audit (#1317) .<br />

r. Error Type 3073: this <strong>error</strong> indicates loss of SYSCLOCK.<br />

s. Error Type 3329: this <strong>error</strong> indicates loss of HSCLOCK.<br />

800 Maintenance Alarms for Communication Manager, Media Gateways <strong>and</strong> Servers

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

Saved successfully!

Ooh no, something went wrong!