MG-BRI error log entries and recommended actions

Last Updated : Feb 02, 2015 |
Table 1: MG-BRI Error Log Entries

Error type

Aux data

Associated test

Alarm level

On/Off board

Command to resolve the error

0

0

Any

Any

test board location

1

Any

Sanity Failure

MIN

ON

18

Media Module is busied out

release board location

257

65535

Control Channel Looparound Test (#52)

MIN

ON

test board location r 20

513

4352 to 4357

Angel Background Errors

ON

test board location

769

4358

Program Logic Error

1291

4359

Clear Error Counters (#270)

MIN

ON

3586

MIN

OFF

3840

4096 to 4101

Inconsistent Downlink Message

3842

46095

Receive FIFO Overflow

3843

46097

Bad LAN Translation RAM

Notes:
  1. 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.

  2. 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).

  3. 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 Channel Looparound Test 52.

  4. 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

    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.

  5. 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.

  6. 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.

  7. Error type 3586: The system detected an excessive number of uplink messages from the Media Module. To prevent the faulty board from flooding the switch with data, the switch software takes the board out of service and alarms it.

    When the board is alarmed due to this error, the switch software periodically puts the board back in service and tells the Archangel to process uplink messages from the board. If the problem still exists, the software takes the media module out of service again. If the media module does not exhibit the problem for a certain time period, then maintenance software resolves the alarm and the media module is left in service.

  8. Error type 3840: The media module received an inconsistent down-link message (a bad header, port number, data, sub-qualifier, or logical link) over the Control Channel. This is a notification only, and no action is required.

  9. Error type 3842: The board is receiving data from the bus faster than it can distribute the data to its endpoints, causing the FIFO RAM buffer to overflow. This error can occur occasionally due to the statistical sizing of the buffers. If it occurs frequently, it may indicate a LAPD parameter mismatch. LAPD should recover from this problem, but it may degrade the performance of the LAN bus.

  10. Error type 3843: Bad translation RAM detected during call connection. The media module marks the location as bad and reports it. The call continues on a different port.