Demand test descriptions and error codes - Avaya Support

Table 183: MG-BRI Error Log Entries 2 of 2
Error Type Aux
Data
Associated Test Alarm
Level
3842 (i) 46095 Receive FIFO
Overflow
3843 (j) 46097 Bad LAN
Translation RAM
On/Off
Board
MG-BRI (BRI Trunk Media Module)
Notes:
a. Error Type 0: run the short test sequence first. If every test passes, run the long test
sequence. Refer to each test’s description, and follow its procedures.
b. Error Type 1: the media module stopped functioning or is physically removed from the
system. This alarm is logged approximately 11 minutes after removing the media module
and/or the SAKI Sanity Test (#53) fails. If the media module is not in the system, insert a
media module in the same slot as the error indicates. See note (f).
c. Error Type 257: there are transient communication problems between the switch and this
media module. Execute the test board location command and refer to the repair
procedures for the Control Chel Looparound Test (#52).
d. Error Type 513: on-board hardware failure. Aux data values correspond to the following
detected errors:
Aux Value Detected Error
4352 External RAM error
4353 Internal RAM error
4355 ROM checksum error
4357 Message Corruption error
Recommended Action
2 of 2
Reset the media module with the busyout board location and reset board
location commands. When reset, the media module executes a set of tests to detect the
presence of any of the faults listed above. Detection of one of these errors during
initialization causes the media module to lock-up and appear insane to the system.
e. Error Type 769: the media module detects a program logic error. No action is required.
However, this error can lead to other errors against this media module.
f. Error Type 1291: the BRI Media Module detected a parity error while accessing its dynamic
RAM which stores the board’s translation information and downloadable application
firmware. Maintenance software resets the media module.
Issue 5 May 2009 633