09.12.2012 Views

Server Alarms - Avaya Support

Server Alarms - Avaya Support

Server Alarms - Avaya Support

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Communication Manager Maintenance Object Repair Procedures<br />

are working properly. If the test fails, it is immediately run a second time. If the test 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 and the IP<br />

Media Resource 320. If this error 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) and the IP Address Update Test (#1371).<br />

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

up analysis testing and rerun the test. 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 and attempts to reset the<br />

Ethernet hardware. There are several failure conditions that can cause this error. 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 />

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

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

Saved successfully!

Ooh no, something went wrong!