MG-ANA error log entries and recommended actions

Last Updated : Aug 25, 2020 |
Table 1: MG-ANA Error Log Entries

Error type

Aux data

Associated test

Alarm level

On/Off board

Command to resolve the error

0

0

Any

Any

Any

test board location

1

0

Board removed or SAKI Sanity Failure (#53)

MIN

ON

18

0

busyout board location

WRN

OFF

release board location

23

0

WRN

OFF

125

MIN

ON

257

65535

Control Channel Looparound Test (#52)

MIN

ON

test board location r 20

513

Any

Angel Background Error

MIN

ON

test board location

769

Program Logic Failure

1025

4363

NPE Audit Test (#50)

1281

Ringing Application Test (#51)

1538

Any

Hyperactive Angel

WRN MIN

ON

3840

Any

Inconsistent Downlink Message
Notes:

  1. Error type 0: Run the short test sequence first. If every test passes, run the long test sequence. Refer to each appropriate test’s description, and follow its recommended procedures.

  2. Error type 1: The media module stopped functioning or has been physically removed from the system. The alarm is logged approximately 11 minutes after removal of the board or failure of the SAKI Sanity Test (#53). Check for the physical presence of the media module in the slot indicated by the alarm. If the board is absent, insert one of the proper type. If the media module is present and its red LED is lit, see LED alarms without Alarm Log entry or with Error Type 1 in LED Descriptions for Avaya Aura® Communication Manager Hardware Components.

  3. Error type 18: The media module has been busied out. Release the media module using release board location long.

  4. Error type 23: The media module has been logically administered but not physically installed. The alarm should clear when the media module is installed.

    If the media module is already installed:

    1. Run test board location long and look at any test failures or Error Codes generated.

    2. If the test does not clear error 23, then execute reset board location and run the long test again.

    3. If the reset/test does not clear error 23, replace the media module.

  5. Error type 125: The media module that is physically installed in the slot does not match the type that is administered for that slot. Do one of the following:

    • Remove the incorrect media module and replace it with one of the type that is administered for that slot.

    • Use change media-module to re-administer the slot so that it matches the board that is installed, then enter reset board location.

  6. Error type 257: Transient communication problems between the switch and this media module. Execute test board location and refer to the repair procedures for the Control Channel Looparound Test 52.

  7. Error type 513: There is an on-board hardware failure. The system will continuously test the media module and report the results approximately every 10 minutes. If the hardware problem is resolved, the alarm will clear in approximately 30 minutes. If the alarm does NOT clear in 30 minutes, then the media module should be replaced.

  8. Error type 769: This error can be ignored, but look for other errors on this media module.

  9. Error type 1025: This error is not service-affecting and no action is required.

  10. Error type 1281: This error is not service-affecting and no action is required.

  11. Error type 1538: The hyperactive media module is out-of-service and may exhibit one or more of the following symptoms:

    1. The tests such as Test #51 and/or Test #220 are aborting with Error Code 2000.

    2. The tests run on the ports of this media module are returning NO-BOARD.

    3. A busyout/release of the media module has no effect on test results.

    4. A list configuration command shows that the media module and ports are properly installed.

    If this error happens again within 15 minutes, replace the media module.

  12. Error type 3840: This error is not service-affecting and no action is required.