Considerations - Avaya MERLIN MAGIX Maintenance And Troubleshooting Manual

Maintenance and Troubleshooting

Considerations

Before running a module test, make sure the following system components are working:
I
– Power supply
– Processor
– Maintenance Console (4424LD+ or MLX-20L console)
Before running a module test, backup system programming to a floppy disk or memory card.
I
See "Backup" in the Programming Basics section of this guide to backup to floppy disk, or
Appendix D, Backing up with a Memory Card to backup to a memory card.
To run tests on the TDL module connected to the 4424LD+ console, or on the MLX module
I
connected to the MLX-20L console, you must run the test from the PC, not from the console.
Before running a module test, busy-out or reset the modules. Busy-Out is the best method, but
I
it will not work if any line or extension is on a stable call. See Busy-Out and Reset.
When beginning the Board Controller Test or the Internal Loopback Module Test, choose to
I
run it once or repetitively.
You can interrupt any module test by selecting Exit .
I
A module test can fail for one of the following reasons:
I
– 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
I
after running the test.
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
MERLIN MAGIX Releases 1.0 or 1.1. An 008 MLX module must be used to provide
extension jacks with Releases 1.0 or 1.1.
If any of the module tests fail and replacing the module does not clear the trouble, then either
I
several modules may be faulty or the connector on the carrier may be faulty.
Module Test Process
6-2
6