Fujitsu FLM 150 ADM, Maintenance And Trouble Clearing

Page: 46 / 198

3.2: Procedure
Issue 9, May 1999 FNC and FNC Customer Use Only Vol. ll, Page 480.3-4
Maintenance and Trouble Clearing
FJTU-320-515-480
3.2 Procedure
The following steps for trouble clearing are presented only as an example. When
necessary, local trouble-clearing procedures take precedence.
Step 1
Examine the autonomous messages associated with the condition changes that
are in question.
a. A printer output of these messages can be very helpful.
b. If a printer output of these messages is not available, log on the node(s) in
question through a craft interface. Use RTRV-COND-ALL (or the FLEXR
equivalent) to retrieve the autonomous messages associated with current
conditions. For transient conditions and alarm conditions caused by
intermittent problems, the autonomous output (AO) buffer may need to be
examined. This message buffer can store up to 500 autonomous messages in
the sequence in which they were generated. The TL1 command is
RTRV-AO.
Note: Before Release 10, if no user identifier (UID) was logged on the NE, autonomous
messages were obviously not displayed, nor were they stored in the AO buffer. With
Release 10 (and later), all autonomous messages, regardless of log-on status, are stored in
the AO buffer.
c. If several condition types are reported, make a list with the most severe
conditions at the top. Critical (CR) or service-affecting (SA) failures, such as
loss of signal (LOS) and equipment failure (FLT), should be handled first.
• Alarm indication signals (AISs) and other maintenance signal conditions
that are normally not traffic-affecting are not addressed until the more
serious problems are cleared.
• Generally, alarm conditions take precedence over transient and standing
conditions, although an undesired manual loopback (standing condition)
could be the cause of a loss of service and must be dealt with quickly.
Step 2
Find the condition type in the alarm/status message. Locate the applicable table
on the following pages for information on probable causes and suggested
corrective actions.
Step 3 If problems persist after a reasonable effort, do not hesitate to call Fujitsu
Technical Support at 1-800-USE-FTAC (1-800-873-3822).
In Tables 3-1 through 3-77, the purpose of the column labeled AID Type is to
guide the user to the correct row, based on the AID type found in first line of the
alarm/status message. It is not intended to imply literally that STS-1 is an AID
type. In fact there are several AID types for STS-1 (e.g., STS1-HG, STS1-LG,
STS1-EW).