Lucent Technologies MERLIN LEGEND Release 6.1 Maintenance And Troubleshooting Manual page 149

MERLIN LEGEND Communications System Release 6.1
Maintenance and Troubleshooting 555-661-140
Module Problems
You can interrupt any module test by selecting
A module test can fail for one of the following reasons:
— The module being tested was not busied-out. Exit the test,
busy-out the module, and try again.
— The error messages indicate that the module is faulty.
If errors indicate that the module is faulty, record them on the module
repair tag immediately after running the test.
NOTE:
If the system does not recognize a 408 GS/LS-MLX module during
testing, check the release number of the system. The 408
GS/LS-MLX module does not work with Releases 1.0 or 1.1. An
008 MLX module must be used to provide extension jacks with
Releases 1.0 or 1.1.
To run a module test, follow the steps below.
To determine which modules are suspect, read the error logs and
review any user-reported problems.
If the error logs indicate the processor is the problem, refer to
''Processor Problems'' on page 4-12
before continuing.
Replacing a faulty processor may resolve module problems.
Busy-out or reset the module.
See ''Busy-Out and Reset'' on page 4-38
Run the internal loopback test.
See "Internal Loopback Test" on page 4–47.
as described in
Run the board controller test.
See "Board Controller Test" on page 4–53.
as described in
''Considerations'' on page
''Considerations'' on page
( on the PC).
Exit
to service the processor
for general guidelines.
If errors occur, record them
4-36.
If errors occur, record them
4-36.
Issue 1
August 1998
Page 4-37