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

Create successful ePaper yourself

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

v. Error Type 3585: The administered NIC interface options (auto-negotiate, speed, <strong>and</strong><br />

duplex) do not match the TN2602AP administration. On the change ip-interface form,<br />

if auto is y, set speed to 100 <strong>and</strong> duplex to full. Submit the form.<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 take the option update. See the repair<br />

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

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

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

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

mis-administered. Use the Communication Manager administration comm<strong>and</strong> change<br />

system-parameters ip-options to verify administration of RTCP monitor server<br />

parameters.<br />

y. Error Type 1538 <strong>and</strong> 3999: the circuit pack sent a large number of control chel messages<br />

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

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

hyperactivity.<br />

● If Error Type 1538 is not present, then the circuit pack has not been taken out of<br />

service, but it has generated 50 percent of the messages necessary to be considered<br />

hyperactive. This may be completely normal during heavy traffic periods. However, if<br />

this Error Type is logged when the circuit pack is being lightly used, it may indicate a<br />

problem with the circuit pack or the equipment attached to it.<br />

<strong>Dem<strong>and</strong></strong> <strong>test</strong> <strong>descriptions</strong> <strong>and</strong> <strong>error</strong> <strong>codes</strong><br />

Investigate <strong>test</strong>s in the order presented. By clearing <strong>error</strong>s associated with the first <strong>test</strong>, <strong>error</strong>s<br />

generated from other <strong>test</strong>s may also be cleared. Click on the link to see the full description of<br />

the <strong>test</strong>, <strong>error</strong> <strong>codes</strong>, <strong>and</strong> recommended actions.<br />

Order of Investigation Short Test<br />

Sequence<br />

Long Test<br />

Sequence<br />

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

D/ND 1<br />

Ethernet Hardware Query Test (#1405) X X ND<br />

Control Chel Looparound Test (#52) X X ND<br />

IIP Address Update Test (#1371) X X CD<br />

Verify NIC Options Test (#1511) X X CD<br />

Network Connectivity Query Test (#1383) X X ND<br />

1 of 2

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

Saved successfully!

Ooh no, something went wrong!