Demand test descriptions and error codes - Avaya Support

IPMEDPRO (TN2302 IP Media Processor)
● Have the IPMEDPRO IP address administered (change node-names ip)
● Be enabled (change ip-interface)
● Be physically inserted into the correct slot.
A TN2302 differs from most circuit packs in that inserting the circuit pack into the switch is
not enough to make the board usable. It must also be administered.
d. Error Type 125: the wrong circuit pack is inserted in the slot where this circuit pack is
logically administered. Do one of the following:
● Remove the wrong circuit pack and insert the logically administered circuit pack.
● Re-administer this slot to match the circuit pack inserted (change circuit-pack).
e. Error Type 257: failure of the Control Chel Looparound Test (#52). See Control Chel
Looparound Test (#52) for more information.
f. Error Type 513: transient hardware device problems on the board. These include an
external RAM failure, internal RAM failure, ROM checksum failure, message corruption,
and program logic inconsistency. If the board detects only one of these hardware problems
it may be alarmed. The error will disappear when none of these faults are detected for 10
minutes. There are no associated tests for these inline errors. If they continue to happen,
the circuit pack should be replaced.
g. Error Type 769: failed attempts to verify IP network connectivity between a specified IP
Media Processor and other IP Media Processor/s in the system. See Short IP 2-Way
Transmission Test (#1505) for Short IP 2-way transmission test failures and Long IP 2-Way
Transmission Test (#1506) for Long IP 2-way transmission test failures.
h. Error Type 770: DSP overallocation error. Since this error causes the DSP audit to run, the
condition is cleared and no action is necessary. No alarms are generated.
i. Error Type 1025: Field Programmable Gate Array (FPGA) failure associated with a the
FPGA device located on the TN2302. Communication Manager will take the resources
associated with every DSP out of service and attempt to reset the FPGA. For the repair
procedure, see MP Diagnostic Test (#1406)
j. Error Type 1281: TSI failures. There are potentially 2 different TSI failures that can occur:
one is a TSI DSP failure, and the other is a TSI FPGA failure. The switch will take the
resources associated with every DSP out of service and attempt to reset the TSI. For the
repair procedure, see MP Diagnostic Test (#1406).
k. Error Type 1538: this error indicates hyperactivity on the board. Hyperactivity means the
circuit pack is sending too many uplink messages to switch software. The circuit pack will be
taken out of service. See (v) for Error Type 3999.
l. Error Type 1793: no electrical signal is detected on the Ethernet cable. Either the Ethernet
cable is unplugged or there is a problem with a connection to the network interface.
m. Error Type 2049: the processor hardware is failing. The PPC provides the Angel
functionality as well as the UDP/IP interface. An attempt is made to reset the board
automatically. For the repair procedure, see MP Diagnostic Test (#1406). If the reset fails,
the board is probably bad and should be replaced.
Issue 5 May 2009 515