Lucent DDM-2000 OC-3 User And Service Manual page 603

TAD-100
363-206-285 Trouble Clearing:
Issue 2, February 2000 Page 1 of 4
Maintenance Philosophy
Overview
The maintenance philosophy for TARP Release 13 and 15 is built on gathering
system information at two levels. The first is through an Operation System or
Graphical User Interface [TL1 (X.25), ITM-SNC, CPro-2000, etc.]. Trouble indications
obtained from these interfaces are analyzed at the operations center and trouble
reports issued. For more information on TL1 interfaces, see 824-102-151 Operations
System Engineering Guide (OSEG). For ITM-SNC, see 107-564-288, ITM-SNC
System Administration Guide , and 107-564-270, ITM-SNC User Guide . For
CPro-2000, see 190-523-xxx (release dependent), Cpro-2000 User Manual .
Operations center personnel can use the OSEG and the rtrv-alm: Report
Descriptions in the Commands and Reports section of Volume 1 of this User/Service
manual to assess the severity and meaning of alarm messages received at the
operations interface. After analyzing the reports, center personnel may dispatch
someone to the site indicating a local alarm condition. The trouble clearing
procedures in this manual assume that troubles have been isolated to a particular
node and are being used by technicians that have been dispatched to the site.
The second level of maintenance is a local visual inspection of the user panel and
circuit pack LEDs, then using a CIT interface to retrieve detailed alarm reports.
Trouble Analysis Procedures
The trouble analysis procedures in this document involve replacing faulty circuit packs
and obtaining performance reports and/or alarm and status reports for analysis to
determine proper system operation and/or trouble. After determining the alarm level
(Critical, Major, Minor, etc.) or trouble indication, the technician accesses the proper
trouble analysis procedure (TAP) from Trouble Clearing: IXL-001. If the trouble
cannot be corrected or identified using these procedures, the procedures direct the
technician to obtain assistance because no more step-action procedural data is
known for the specific trouble.
DDM-2000 OC-3 M
ULTIPLEXER