Demand test descriptions and error codes - Avaya Support

● Be physically inserted into the correct slot
If the circuit pack has an entry on the circuit pack screen and any of the other conditions
are not met, a MINOR alarm is logged. To resolve the error:
● Make sure every condition for administration is met, and that a functioning Media
Processor is inserted in the correct slot.
● Completely remove the IP Media Resource 320 from the system:
a. Remove the administered IP-Interface associated with the circuit pack.
b. Physically remove the circuit pack from the slot.
b. Error Type 18: The TN2602AP was busied out by a busyout board location.
● Release the circuit pack (release board location).
c. Error Type 23: The IP Media Resource 320 is not completely administered. To be fully
administered, a TN2602AP must:
● Have an entry in the circuit plan (change circuit-pack)
● Have an administered IP address (change node-names ip)
● Be enabled (change ip-interface)
● Be physically inserted into the correct slot.
A TN2602AP 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 test (#52). See Control Chel Looparound Test
(#52) for the repair procedures.
f. Error Type 513: transient hardware device problems on the board. They include an
external RAM failure, internal RAM failure, ROM checksum failure, message corruption,
and program logic inconsistency. There are no associated tests for these errors; if they
continue to happen, an alarm will occur.
g. Error Type 769: failed attempts to verify IP network connectivity between a specified
TN2602AP and other IP Media Processors in the system. See Short IP 2-Way Transmission
Test (#1505) for Test #1505 failures and Long IP 2-Way Transmission Test (#1506) Test for
#1506 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: a module on the board failed. Aux Data values between 16641 and 16895
indicate a critical problem. See Board Health Query Test (#1652).
522 Maintenance Alarms for Communication Manager, Media Gateways and Servers