Instruction manual

MERLIN LEGEND Communications System Release 5.0
Maintenance and Troubleshooting
555-650-140
Issue 1
June 1997
Introduction
Page 1-21
Maintenance Strategy
Figure 1-7. Maintenance Strategy
Trouble Reports
System trouble can be reported in two ways:
■ By users
■ By system alarms (permanent errors)
User or 

Lucent Technologies-authorized
personnel reports a problem
Troubleshoot telephone

(Chapter 3)
1a
1a
1a
Discuss problem

with the source
Phone

problem
Check error logs

(Chapter 2)
2a
Problem persists
All

other

problems
Maintenance or programming

accessed just before

error(s) occurred
Check Access Log

(Chapter 2)
2c
Inconclusive
Problem gone;

verify that errors

do not recur
Can’t access error logs
Inconclusive
Check

permanent errors

in error logs

(Chapter 2)
1b
One or more alarms turn on:
Attendant Alarm LED

Processor LED

Supplemental alert

Status display
Can’t access

error logs
Errors
2b
Troubleshoot power supply

(Chapter 4)
2b
Troubleshoot processor

(Chapter 4)
2b
Troubleshoot carrier

(Chapter 4)
2b
Escalate to NSAC or
Lucent Technologies-
authorized dealer 

Escalate to NSAC or
Lucent Technologies-
authorized dealer 

9
Problem persists
Problem persists
Problem persists
Problem persists
2a
Troubleshoot errors

(Table 2-1, “Error Codes”)
Errors
Corrective action per Table 2-1
3
4
5
6
7
8
Troubleshoot power supply first (if indicated)

(Chapter 4)
Power supply OK; problem persists
Processor OK; problem persists
Modules OK; problem persists
Carrier OK; problem persists
Trunks OK; problem persists
Troubleshoot processor (if indicated)

(Chapter 4)
Troubleshoot modules

(Chapter 4)
Troubleshoot carrier

(Chapter 4)
Troubleshoot trunks

(Chapter 5)
Troubleshoot central office

(Chapter 5)
1b