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.

IPMEDPRO (TN2602AP IP Media Resource 320)<br />

j. Error Type 1026: a module on the board failed. Aux Data values between 16385 <strong>and</strong> 16639<br />

indicate a non-critical <strong>error</strong>. See Board Health Query Test (#1652)<br />

k. Error Type 1281: certain firmware modules or components on the board failed to initialize<br />

properly. This <strong>test</strong> verifies that the embedded software (firmware) applications on the board<br />

are working properly. If the <strong>test</strong> fails, it is immediately run a second time. If the <strong>test</strong> fails a<br />

second time, an alarm is raised. See Ethernet Hardware Query Test (#1405) for more<br />

information.<br />

l. Error Type 1538: hyperactivity on the board. The circuit pack is sending too many<br />

messages to switch software. The circuit pack will be taken out of service. See (y) for Error<br />

Type 3999.<br />

m. Error Type 1793: no electrical signal is detected on the Ethernet cable. The Ethernet cable<br />

is unplugged or there is a problem with a connection to the network interface.<br />

n. Error Type 2049: There is aa problem with the packet bus. See Packet Count Query Test<br />

(#1630).<br />

o. Error Type 2305: There is an IP address inconsistency between switch software <strong>and</strong> the IP<br />

Media Resource 320. If this <strong>error</strong> occurs, an attempt will be made to download the IP<br />

address again. If the board still refuses the IP address, the board will be reset. See IP<br />

Address Update Test (#1371).<br />

p. Error Type 2306: Packet link did not come up during board initialization. See the Packet<br />

Count Query Test (#1630) <strong>and</strong> the IP Address Update Test (#1371).<br />

q. Error Type 2561: the ping <strong>test</strong> has failed. The diagnostics that are run by this failure start<br />

up analysis <strong>test</strong>ing <strong>and</strong> rerun the <strong>test</strong>. Testing will continue until the problem is cleared. For<br />

the repair procedure, see Ping Test (#1379).<br />

r. Error Type 2817: Ethernet hardware failure on the TN2602AP IP Media Resource 320. The<br />

switch takes resources associated with every DSP out of service <strong>and</strong> attempts to reset the<br />

Ethernet hardware. There are several failure conditions that can cause this <strong>error</strong>. They will<br />

all be treated as the same failure by switch software. For the repair procedure, see Ethernet<br />

Hardware Query Test (#1405).<br />

s. Error Type 3073: there is a problem with the Aggregator Hardware on the TN2602AP. See<br />

the repair procedure for Aggregator Hardware Query (#1629).<br />

t. Error Type 3329: duplicate IP address detected. Administration of the TN2602AP contains<br />

an IP address that is a duplicate of an existing network IP address. Duplicate IP addresses<br />

can cause problems with calls on the TN2602AP. It is not possible to determine where the<br />

duplicate address is located. See the repair procedure for IP Address Update Test (#1371).<br />

u. Error Type 3330: A virtual duplicate IP address was detected. Administration of the<br />

TN2602AP contains an IP address that is a duplicate of an existing network IP address.<br />

Duplicate IP addresses can cause problems with calls on the TN2602AP. Its is not possible<br />

to determine where the duplicate address is located. See the repair procedure for IP<br />

Address Update Test (#1371).<br />

Issue 5 May 2009 523

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

Saved successfully!

Ooh no, something went wrong!