Lucent Technologies MERLIN LEGEND Release 5.0 Maintenance And Troubleshooting Manual page 39

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