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.

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

IPMEDPRO board. If this <strong>error</strong> occurs, an attempt will be made to download the IP address<br />

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

Update Test (#1371).<br />

o. Error Type 2561: the ping <strong>test</strong> has failed. See MP Diagnostic Test (#1406).<br />

p. Error Type 2817: Ethernet hardware failure on the TN2302 circuit pack. The switch will take<br />

resources associated with every DSP out of service <strong>and</strong> then attempt to reset the Ethernet<br />

hardware. There are several <strong>error</strong> conditions that can cause this problem. They will all be<br />

treated as the same failure by switch software. See MP Diagnostic Test (#1406).<br />

q. Error Type 3073: circuit board reset failed. The switch will take resources associated with<br />

every DSP out of service <strong>and</strong> then attempt to reset the board, as the failure of a Scotch is<br />

severe enough to warrant a board reset. After the reset, a query is made again for the<br />

health of the SCOTCH devices to verify whether they are working properly or not. If they are<br />

working properly, the alarm <strong>and</strong> <strong>error</strong> counters are cleared. If they are not working properly,<br />

the alarm will continue, every DSP will be left out of service, <strong>and</strong> maintenance diagnostics<br />

will stop. If the board continues to fail with this Error Type, replace the TN2302.<br />

r. Error Type 3329: an IP address update (Test #1371) was sent to the circuit pack, which<br />

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

addresses can cause problems with calls on the IPMEDPRO circuit pack. It is not possible<br />

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

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

s. Error Type 3585: The NIC parameters on the board do not match those in administration.<br />

Aux Data = 1: The speed is set for auto-negotiate in administration. The board is reporting<br />

half-duplex. See the repair procedures for Verify NIC Options Test (#1511).<br />

Aux Data = 2: The board is reporting different options than what is administered. Software<br />

tried to correct the options, but the board did not accept the option update. See the repair<br />

procedures for Verify NIC Options Test (#1511).<br />

t. Error Type 3841: Aux Data = None: Inconsistent downlink message. The board was sent a<br />

message it did not underst<strong>and</strong>. These <strong>error</strong>s are not service affecting. No action is required.<br />

u. Error Type 3841: Aux Data = 4283: The RTCP monitor server is not connected.<br />

There is a network problem between the monitor server <strong>and</strong> the server or the RTCP monitor<br />

server is mis-administered. Use the change system-parameters ip-options<br />

comm<strong>and</strong> to verify administration of RTCP monitor server parameters.<br />

v. Error Type 3999: the circuit pack sent a large number of control chel messages to the<br />

switch within a short period of time.<br />

● If Error Type 1538 is also present, the circuit pack was taken out of service due to<br />

hyperactivity.<br />

516 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!