Filter
Top Products
IPMEDPRO (TN2602AP IP Media Resource 320)
Issue 1 June 2005 1385
m. Error Type 2561: the ping test has failed. The diagnostics that are run by this failure start
up analysis testing and rerun the test. Testing will continue until the problem is cleared.
n. Error Type 2817: Ethernet hardware failure on the TN2602AP IP Media Resource. The
switch takes resources associated with every DSP out of service and attempts to reset the
Ethernet hardware. There are several error conditions that can be sent up in the error
message for this problem. They will all be treated as the same failure by switch software.
For the repair procedure, see associated Test #1405.
o. Error Type 3073: there is a problem with the Aggregator Hardware on the TN2602.
p. Error Type 3329: duplicate IP address detected. Administration of the TN2602AP contains
an IP address that is a duplicate of an existing network IP address. The board accepted the
address, but there might be problems in the network that could cause problems with calls
on the TN2602.
q. Error Type 3585: The administered NIC interface options (auto-negotiate, speed, and
duplex) do not match the TN2602AP administration. On the change ip-interface form,
if auto is y, set speed to 100 and duplex to full. Submit the form.
r. Error Type 3841: Aux Data = None: Inconsistent downlink message. The board was sent a
message it did not understand. These errors are not service affecting. No action is required.
s. Error Type 3841: Aux Data = 4283: The RTCP monitor server is not connected. There is a
network problem between the monitor server and the media server or the RTCP monitor
server is mis-administered. Use the Avaya Communication Manager administration
command change system-parameters ip-options to verify administration of RTCP
monitor server parameters.
t. Error Type 3999: the circuit pack sent a large number of control channel messages to the
switch within a short period of time.
● If Error Type 1538 is also present, then the circuit pack was taken out of service due to
hyperactivity.
● If Error Type 1538 is not present, then the circuit pack has not been taken out of service,
but it has generated 50 percent of the messages necessary to be considered
hyperactive. This may be completely normal during heavy traffic periods. However, if this
error type is logged when the circuit pack is being lightly used, it may indicate a problem
with the circuit pack or the equipment attached to it.