maintenance and trouble clearing - alarmspecs.comebay.alarmspecs.com/flm150adm/150480p.pdf ·...

FLM 150 ADMPractice FJTU-320-515-480

MAINTENANCE AND TROUBLE CLEARING

ISSUE 9, MAY 1999

FUJITSU NETWORK COMMUNICATIONS, INC.

FNC and FNC Customer Use Only

The contents of this document are subject to change without notice. Neither this document, nor any portion thereof, is to be disclosed, reproduced, or distributed in any form without the express written permission of FNC. Information contained in this document is FNC Proprietary and is for use by FNC authorized recipients only.

FLEXR and FLEXR

Plus

are registered trademarks of Fujitsu Network Communications, Inc. (FNC).

FASTLANE and NETSMART are trademarks of FNC.

UNIX is a registered trademark of UNIX System Laboratories, Inc.

NMA and CLEI are trademarks of Bell Communications Research, Inc.

Proprietary Rights Notice

All other products or services mentioned in this document are identified by the trademarks, service marks, or product names as designated by the companies who market those products or services or own those marks. Inquiries concerning such products, services, or marks should be made directly to those companies.

Unpublished work and only distributed under restriction.

Copyright

Fujitsu Network Communications, Inc. All Rights Reserved.

Issue 9, May 1999 FNC and FNC Customer Use Only

Maintenance and Trouble ClearingFJTU-320-515-480

Document Change Notice

This section lists the reason, location, and description of practice changes. When the changes are extensive, a general statement giving the nature of the revisions is provided.

Reason for Document Change:

FLM 150 ADM Product Release 14S

Location of Change Description of Change

Throughout Improved wording and formatting.

FASTLANE I™ information removed and references made to new FASTLANE practices.

Section 3 New condition code added associated with 14S features.

Section 4 New optical unit (HC1A and MC6A) information added.

FNC and FNC Customer Use Only

Plug-In Unit Warnings

Many plug-in units are stamped with anti-electrostatic markings (see figures at left) and require special handling and storage. The following precautions should be strictly observed to avoid damage from electrostatic discharge (ESD).

• When handling plug-in units for installation, removal, or option setting, always wear a wrist strap, with a minimum 1-megohm resistance, that is connected to safety ground.

• Hold only the edges of the plug-in units. Do not touch the integrated circuit (IC) leads or the circuitry.

• Transport and store the plug-in units in the ESD protective bags that the units were shipped in. Always fold the open end of the bag and secure it with ESD tape.

• Return the units to Fujitsu in ESD protective bags. Use the original shipping containers when possible.

All plug-in units should be seated with a slow, firm motion. Many critical units have longer power connector pins to minimize power surges during installation. A slow insertion method ensures that the plug-in units are not damaged.

Fiber Warnings

Danger: Invisible laser radiation. Avoid direct exposure to the beam. Never look into the end of a fiber, fiber cord, or fiber pigtail. Permanent eye damage or blindness can occur quickly when laser radiation is present. The label on the left is attached to laser-emitting and receiving units as a reminder. Use of controls, adjustments, or procedures other than those specified may result in hazardous laser radiation exposure from a fiber-optic pigtail.

Danger: Never handle exposed fiber with your bare hands or touch it to your body. Fiber fragments can enter the skin and are difficult to detect and remove.

Installation Restriction

Systems shall be installed only in restricted access areas (for example, dedicated equipment rooms or equipment closets) in accordance with Articles 110-16, 110-17, and 110-18 of the National Electrical Code, ANSI/NFPA 70.

Anti-electrostatic Markings

ATTENTIONOBSERVE PRECAUTIONS

FOR HANDLING

ELECTROSTATIC

SENSITIVE

DEVICE

DANGER

Invisible laser radiation from

connectors when

uncoupled AVOID DIRECT

EXPOSURE TO BEAM

Laser Radiation Label

Important

Observe all warnings in the text or on equipment labels regarding high-voltage or high-temperature conditions. The following warnings and figures apply to most Fujitsu products.


Table of Contents

Page

1 Maintaining Equipment

1.1 Alarm/Status Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.1-1

1.2 Message Parameter Interpretation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.1-6

1.3 Maintenance Philosophy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.1-14

1.4 Alarm and Status Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.1-15

1.5 Trouble Analysis Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.1-16

1.6 Repairing Defective Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.1-17

1.7 Front and Rear Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.1-18

2 Plug-In Unit Front-Panel Devices

2.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.2-1

2.2 LED Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.2-2

3 Responding to Alarms and Conditions

3.1 Condition Code Responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-1

3.2 Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-4

3.3 ACTLPBKF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-5

3.4 ACTLPBKT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-6

3.5 AIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-6

3.6 AL1PLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-8

3.7 APSB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-8

3.8 B1ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-9

3.9 B2ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-9

3.10 B3ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-10

3.11 BERSDL and BERSFL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-10

3.12 BERSDP and BERSFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-12

3.13 BIP2ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-13

3.14 CANVAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-13

3.15 CLEI-FLT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-13

3.16 CLEI-LBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-13



Page

3.17 CLEI-TEMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-14

3.18 CPY Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-14

3.19 CTNEQPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-15

3.20 DCCFAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-15

3.21 ECRESTART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-17

3.22 FALLBK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-17

3.23 FE Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-17

3.24 FEAIS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-18

3.25 FEFLT-COM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-18

3.26 FEFLT-T1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-18

3.27 FEFLT-T1M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-19

3.28 FEFLT-T1S. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-19

3.29 FEFLT-T3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-19

3.30 FEISD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-20

3.31 FELOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-20

3.32 FEOOF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-20

3.33 FILECONFIG–ACT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-21

3.34 FILECONFIG–STBY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-21

3.35 FRCDSW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-21

3.36 HMIA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-22

3.37 INIT-SYS-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-22

3.38 INTFAIL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-22

3.39 IPNOTREACH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-22

3.40 IPREACHABLE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-23

3.41 ISD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-23

3.42 ISOPLS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-23

3.43 LOCKIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-24

3.44 LOCKOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-24

3.45 LOF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-25

3.46 LOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-27

3.47 LOP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-27

3.48 LOS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-28

3.49 MAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-30



Page

3.50 MANSW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-30

3.51 MISMOUNT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-31

3.52 MSGCHG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-32

3.53 PDI-n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-32

3.54 PINGTIMEOUT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-33

3.55 PLM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-33

3.56 RAI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-34

3.57 RFI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-34

3.58 RFI-CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-36

3.59 RFI-PLD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-36

3.60 RFI-SRV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-36

3.61 RMVD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-37

3.62 SVM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-37

3.63 SYNCD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-38

3.64 SYSRES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-38

3.65 T-FE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-38

3.66 T-LBCN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-39

3.67 T-PSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-39

3.68 TARPECHO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-40

3.69 TARPERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-40

3.70 Threshold Violations-Line. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-41

3.71 Threshold Violations–Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-43

3.72 Threshold Violations-Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-45

3.73 TMGOUTPSW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-46

3.74 TMGOUTSSW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-46

3.75 TMGSW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-47

3.76 TRCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-47

3.77 UNEQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-48

3.78 WKSWBK. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-48

3.79 WKSWPR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.3-49



Page

4 Replacing Units

4.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.4-1

4.2 Replacing the Power (PW1A) Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.4-1

4.3 Replacing the Microprocessor (MP1A) Unit. . . . . . . . . . . . . . . . . . . . . . . . 480.4-5

4.4 Replacing the Time-Slot Assignment (TS1A) Unit . . . . . . . . . . . . . . . . . 480.4-10

4.5 Replacing the Alarm (AW1A) Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.4-14

4.6 Replacing the Supervisory (SV1A) Unit. . . . . . . . . . . . . . . . . . . . . . . . . . 480.4-18

4.7 Replacing the Middle-Speed Mux/Demux/Transmux (MC1A) Unit . . . . 480.4-25

4.8 Replacing the Low-Speed Switch (LS1A-D1) Unit . . . . . . . . . . . . . . . . . 480.4-34

4.9 Replacing the Embedded Operation Channel (EC1A) Unit . . . . . . . . . . 480.4-37

4.10 Replacing the High-Speed Switch Control (HS1A) Unit . . . . . . . . . . . . . 480.4-41

4.11 Replacing the OC-12 Optical Channel (HC1A-6Lx1) Units . . . . . . . . . . 480.4-45

4.12 Replacing the OC-3 Optical Channel (HC1A and MC6A) Units. . . . . . . 480.4-49

4.13 Replacing the STS-1 Electrical Channel (HC1A-STS1) Unit . . . . . . . . . 480.4-59

4.14 Replacing the Timing Control Access (TCA) Unit . . . . . . . . . . . . . . . . . . 480.4-62

4.15 Replacing the Low-Speed Channel–DS1(LC1A-D1xx) Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.4-65

4.16 Replacing the Low-Speed Channel–OVTG(LC1A-F6xx) Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.4-68

5 Miscellaneous Procedures

5.1 Handling Fiber Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.5-1

5.2 Cleaning, Connecting, and Disconnecting the Optical Connectors . . . . . 480.5-6

5.3 Measuring Optical Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.5-9

5.4 Verifying External Clock and Clock Connections . . . . . . . . . . . . . . . . . . 480.5-15

5.5 Correcting the T1 or T3 Framing Format . . . . . . . . . . . . . . . . . . . . . . . . 480.5-17

5.6 Correcting Unidirectional or Bidirectional Switch Provisioning . . . . . . 480.5-21

5.7 Placing an SDCC In Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.5-24

5.8 Correcting a Mismounted Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.5-27

Appendix A. Trouble Analysis Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480.A-1



1.1: Alarm/Status Identification

1 Maintaining Equipment

1.1 Alarm/Status Identification

1.1.1 Summary

This procedure describes the identification of conditions that cause visible or audible alarms. Once the technician is alerted to a condition by visible or audible alarms, he can use alarm and status messages retrieved through the operations support system (OSS) or craft interface to assist in isolating the cause of the condition.

Fujitsu recommends that all FLM equipment be connected to form operation and maintenance networks. These networks should be continuously monitored by an interface device such as FLEXR® or the Network Monitoring and Analysis (NMA™) system.

Fujitsu also recommends that operations and maintenance personnel keep records of all alarm and status indications and the steps taken to clear them. A sample of the type of document that can be used with the FLM 150 ADM is contained in Appendix A, Trouble Analysis Log.

1.1.2 Procedure

Step 1 Determine the location (near- or far-end) and severity of the condition and record this information in the trouble log.

a. Check the NE ACT and FE ACT LEDs on the AW1A unit. NE ACT indicates a near-end alarm while FE ACT is lit for a far-end alarm. Treat near-end conditions first. If FE ACT is indicated, the number shown on the MP1A unit display identifies the remote node whose alarm/status conditions are displayed on the AW1A unit.

b. If there is a near-end alarm (NE ACT LED on AW1A is on), then the display on the MP1A unit should be a decimal point. If a number without a decimal is being displayed, the status lights on the AW1A are showing the status for that remote node. Press the FE SEL button to check the next subscribed node. Continue this process until the decimal appears in the display. This will verify the NE ACT indication on the AW1A unit.

Issue 9, May 1999 FNC and FNC Customer Use Only Vol. ll, Page 480.1-1

1.1: Alarm/Status IdentificationMaintenance and Trouble ClearingFJTU-320-515-480

c. Use the FE SEL button to step through all the subscribed nodes. Check for alarm lights on the AW1A at each node.

d. Record the alarm severity displayed on the AW1A unit (CR, MJ, MN) in the trouble log.

e. If the FE ACT LED is lit, read the identity of the far-end node on the EQPT NO. display and record the alarm severity displayed on the AW1A unit for that node in the trouble log. Repeat this process by using the FE SEL button to step through each subscribed node.

f. Address near-end conditions first, then work on other alarms in the order of their severity.

Step 2 Log on the node from which the alarm condition is originating.

Step 3 Retrieve all current alarms using TL1 or FLEXR. Record them in the trouble log.

TL1 FLEXR 7.71

Press CTRL + X (ACS LED lights on the SV1A unit).

Press CTRL + X (Welcome screen).

Press 3 for TL1.

ACT-USER:TID:UID:CTAG::PID;

TID = FUJITSU

UID = ROOT

PID = ROOT

Session

Logon

Click OK (Port Set-Up).

Enter System ID: FUJITSU

Enter User Name: ROOT

Enter Password: ROOT

Click OK.

Repeat for other TIDs.

TL1 FLEXR 7.71

RTRV-ALM-ALL:TID:CTAG; Click once in the Alarm window.

Exit.



Step 4 If more information is desired, retrieve the standing conditions using TL1 or FLEXR. Record them in the trouble log.

Step 5 Problems caused by intermittent failure conditions may not show up in the alarm retrieval. To view the complete recent history of a node, retrieve all or a portion of the autonomous output (AO) buffer. Up to 500 of the most recent messages are stored there. The AO buffer is a valuable information source for nodes not continuously monitored (that is, not logged on) by the craft interface or OSS. When no craft interface or OSS is logged on a node, autonomous messages are sent only to the AO buffer. (Before Release 10 of the FLM 150 ADM, autonomous messages were neither generated nor stored if no one was logged on the node.)

TL1 FLEXR 7.71

RTRV-COND-ALL:TID::CTAG; Status/Control

Shelf Condition

Retrieve Shelf Condition

Click Exit to close the shelf condition log report.

TL1 FLEXR 7.71

RTRV-AO:TID:AIDs:CTAG:::KEYWORD=DOMAIN;

AID Values: 1 through 500, null = all

KEYWORD = DOMAIN:

ATAGSEQ = 6-digit numbers (can use &, &&)

MSGTYPE = ALM/EVT/PM/DBCHG

ORDER = INCR/DECR

(Defaults in bold)

Note: With Release 10, knowledge of ATAGSEQ is not required. With the ORDER keyword, set to “increment” or “decrement” and using ranging (& and &&), any group of messages can be retrieved.

Example: To retrieve the 20 most recent messages of all types, starting with the newest, use the following:

RTRV-AO:TID:1&&20:CTAG:::ORDER=DECR;

Status/Control

Auto Report Control

Retrieve Autonomous Output

Select the Aid Range or ATAGSEQ.

Enter the applicable data.

Click OK.



Step 6 Determine which current alarm has the greatest service effect. List that alarm in the first available section of the Alarm Clearing Procedures portion of the trouble log.

Critical (service-affecting) alarms should be cleared first, followed by any other service-affecting alarms. Then any remaining major (non–service-affecting [NSA]) alarms, followed by any minor alarms, should be cleared.

Step 7 If using the LEDs, refer to Section 2, Plug-In Unit Front-Panel Devices, for additional information to interpret the LED indications. If appropriate, use the listed Related Condition Codes in the Alarm and Status Descriptions table and go to Section 3, Responding to Alarms and Conditions, to find the probable causes and suggested corrective actions. List the probable causes in the trouble log.

Step 8 If using the alarm and/or AO log messages, use the condition type, such as AIS (alarm indication signal) or LOS (loss of signal), and the AID (access identifier) type and go to Section 3, Responding to Alarms and Conditions, to find the probable causes and suggested corrective actions. List the probable causes in the trouble log.

Step 9 Use the procedures recommended in Section 3, Responding to Alarms and Conditions, to correct the trouble condition. Did the alarm or status condition clear?

Step 10 Retrieve all current conditions.

If Yes: If No:

Record the time in the Time Cleared column of your form and continue with Step 10.

Call Fujitsu at 1-800-USE-FTAC (1-800-873-3822).

TL1 FLEXR 7.71

RTRV-ALM-ALL:TID::CTAG; Click once in the Alarm window.

Exit.



Step 11 Have all alarm conditions in the system cleared?

Step 12 Compare the current alarms to those listed in the trouble log. List the time in the Time Cleared column next to any conditions that have cleared, and add any additional alarm/status conditions to the list. Then repeat from Step 6.

You have completed this procedure.

If Yes: If No:

Go to Step 12. Call Fujitsu at 1-800-USE-FTAC (1-800-873-3822).


1.2: Message Parameter InterpretationMaintenance and Trouble ClearingFJTU-320-515-480

1.2 Message Parameter Interpretation

This section provides explanations of message fields or parameters for alarms, transient or standing conditions, and example messages.

Note: The RTRV-AO report format is identical to the autonomous report REPT format except for the termination indicator.

1.2.1 Interpreting Messages

Autonomous messages are reported by the FLM 150 ADM to the craft terminal and/or the OSS computer display. They are embedded in the equipment firmware and have the REPT prefix. The REPT messages are automatically displayed when an event is triggered, provided the condition is not provisioned as NR (no report) or its message category is not currently inhibited.

1.2.2 Message Retrieval

To retrieve alarm or condition messages, send the following commands:

• Alarm events—RTRV-ALM-ALL, RTRV-ALM-ENV, RTRV-COND-ALL

• Standing conditions—RTRV-COND-ALL

• Performance monitoring (PM) data—RTRV-PM-AIDTYPE

• All current and historical messages, including transient conditions and database change reports—RTRV-AO

• The report may be limited to specific message categories (ALM, EVT, PM, DBCHG) and specific sequences.



1.2.3 Report Formats

Alarm Report Format

Report alarm (REPT ALM) messages are generated by the system to report the occurrence of an alarm event. Each event causes a separate message. The only conditions that appear in a REPT ALM message are those with provisioned notification codes of CR, MJ, or MN. (Note that housekeeping [environmental] alarm reports use a different format, which is shown in the next section.)

The format for an autonomous alarm report (real time) or an alarm report retrieved at a later time using RTRV-AO and an example follow.

TID DATE TIMEALMCDE ATAG REPT ALM AIDTYPE “AID:NTFCNCDE,CONDTYPE, SRVEFF,,,LOCN,DIRN,,,:\”COND DESCR\””

Example: FUJITSU 95-12-23 20:43:44 *C 000003 REPT ALM EQPT "TS1A-W:CR,RMVD,SA,,,NEND,NA,,,: \"Unit is removed\""

The RTRV-AO command retrieves an alarm from the AO buffer, which will indicate the time at which it was generated. If the operator wants to know if the condition still exists, the RTRV-ALM-ALL or RTRV-COND-ALL command can be used, which will result in a real-time report.

The format for a report retrieved using RTRV-ALM-ALL or RTRV-COND-ALL and an example follow.

"AID,AIDTYPE:NTFCNCDE,CONDTYPE,SRVEFF,,,LOCN,DIRN,:\"CONDDESCR\""

Example: "MC1A-4-W,EQPT:CR,RMVD,SA,,,NEND,NA,:\"Unit is removed\""



Environmental Report Format

Report alarm environment (REPT ALM ENV) reports are generated to report an environmental (housekeeping) alarm event. The format for a environmental report retrieved using RTRV-AO and an example follow.

TID DATE TIMEA ALMCDE ATAG REPT ALM ENV “AID:NTFCNCDE,ALMTYPE,,,\"ALMMSG\""

Example: FUJITSU 95-11-15 20:10:10 A 000010 REPT ALM ENV "1:MJ, AIRCOND,,,\"Air Conditioning Failure\""

The format for an environmental report retrieved using RTRV-ALM-ENV and an example follow.

“AID:NTFCNCDE,ALMTYPE,,,\”ALMMSG\””

Example: “1:MJ,AIRCOND,,,\”Air Conditioning Failure\””



Event Report Format

Report event (REPT EVT) messages are generated by the network element (NE) to report an event that has been assigned a notification code of NA (not alarmed). Each nonalarmed event that is reported will generate a separate autonomous message. The only REPT EVT messages for SWDL (software download) concern Transient Conditions.

The following format and example are for an event report retrieved using RTRV-AO.

TID DATE TIMEA ATAG REPT EVT AIDTYPE AID:CONDTYPE,CONDEFF,,,LOCN,DIRN,:,,\"CONDDESCR\"

Example: FUJITSU 93-02-22 06:10:01 A 000100 REPT EVT T3 3:ACTLPBKT,CL,,,NEND,NA,:,,\ "Terminal loopback in active position\"

The following format and example are for an event report retrieved using RTRV-ALM-ALL or RTRV-COND-ALL.

"AID,AIDTYPE:NTFCNCDE,CONDTYPE,SRVEFF,,,LOCN,DIRN,:\"CONDDESCR\""

Example: "MC1A-4-W,EQPT:CR,RMVD,SA,,,NEND,NA,:\"Unit is removed\""



Performance Monitoring Report Format

The following format and example are for a PM report retrieved using RTRV-AO.

TID DATE TIMEA ATAG REPT PM AIDTYPE “AID:MONTYPE,MONVAL,,LOCN,DIRN,TMPER, MONDAT,MONTM”

Example: FUJITSU 95-09-20 12:15:02 A 102 REPT PM EC1 "1-1:CVL,73,,NEND,TRMT,15-MIN, 06-30,10-15"

The following format and example are for a PM report retrieved using RTRV-PM-ALL.

“AID,AIDTYPE:MONTYPE,MONVAL,,LOCN,DIRN,TMPER,MONDAT,MONTM,INDEX”

Example: “1-1,EC1:CVL,73,NEND,TRMT,1-DAY,06-30,00-00,1"

Database Change Report Format

The following format and example are for a database change report retrieved using RTRV-AO.

TID DATE TIME A ATAG REPT DBCHG "UPDATE MANAGEMENT BLOCK:COMMAND CODE: AIDs:DATA BLOCK"

Where Update Management Block: Source = CTAGData Block: Parameters that were changed

Example: FUJITSU 96-1-12 17:50:45 A 000100 REPT DBCHG "SOURCE=ALAN:ED-T1:3-1-1&&3-1-4:SINH=Y,AISSD=Y"



1.2.4 Report Parameters

Table 1-1 defines each of the report parameters.

Table 1-1: Autonomous and Retrieved Report Parameters

Parameter Definition

AID The values in the Access Identifier field identify the exact address of the equipment or the facility (channel) reporting the status. For environment alarms, the valid AID values are 1 through 16. For REPT EVT FILE, FILESPEC is the AID and ALMTYPE.

AIDTYPE The value in the Access Identifier Type field specifies whether AID applies to equipment, common equipment, or one of the traffic or data channels. An example AIDTYPE is OC3/OC12 = Optical Carrier-Level 3/12 Facility.

ALMCDE Alarm Code identifies alarm severity. The following are the possible alarm codes. Note that the letter A is an ALMCDE used to identify events; that is, transient and standing conditions and subsequent alarm messages indicating that an alarm code has cleared.

*C—Critical alarm

**—Major alarm

*—Minor alarm

A—Autonomous message (reserved for event messages and cleared alarm messages)

ALMMSG Alarm Message is the text message associated with the environmental alarm. ALMMSG texts have a maximum length of 40 characters and appear within a pair of escaped quotes (\”).

ALMTYPE Alarm Type is the alarm type associated with the environmental scan point. ALMTYPEs are limited to 10 ASCII characters.

ATAG The Autonomous Message Tag is used to correlate autonomous messages caused by a common trouble. The system assigns each autonomous message an ATAG. It is a number limited to a maximum of six characters.

COMMON CODE Common Code identifies the TL1 command used to change the database.

CONDDESCR The Condition Descriptions is a detailed text description of the alarm that caused this notification. This field is limited to 64 characters enclosed within escaped quotes (\”). CPY-FILE uses x % COMPLETE for REPT EVT FILE.



CONDEFF Condition Effect indicates if the reported event results in a standing condition, a transient condition, or the clearing of a previously reported standing condition. The valid values for CONDEFF are as follows:

• SC—standing condition raised

• CL—standing condition cleared

• TC—transient condition

CONDTYPE The Condition Type is the alarm, transient condition, or standing condition that generated the message. An example value is CPY-FILE-PRTL for REPT EVT FILE.

DATA BLOCK Data Block identifies any parameter modified in a TL1 command that affects the provisioning database (i.e., ED-AIDTYPE command).

DIRN Direction of the signal on which the condition was detected:

TRMT—Transmit, toward the highest speed output

RCV—Receive, from the highest speed input

NA—Not applicable, direction not relevant

KEYWORD = DOMAIN Provisioned parameter and its possible values. The keyword is the optioned parameter. The domain is the list of possible settings for the chosen keyword.

LOCN Location where the condition was detected: NEND (near end) or FEND (far end). The only valid value for Release 10 and earlier is NEND (near end of the system; that is, the NE reporting the condition).

MONDAT Monitoring Date is the date of the beginning of the storage register period specified in TMPER. The format is mm:dd. If TMPER is 1-DAY, MONTM is null.

MONTM Monitoring Time is the beginning time of the day of the storage register period specified in TMPER. The format is hh:mm (allowed values for min are 0, 15, 30, or 45). If TMPER is 1-DAY, MONTM is null.

MONTYPE Monitoring Type is the type of the parameter being monitored.

MONVAL Monitoring Value is the measured value of a monitored parameter. This data is presented in the form of numeric counts or rates. Valid values for MONVAL are restricted to decimal numerals. A null value means that no MONVAL is associated with this event or that the reported event is not a PM event.

Table 1-1: Autonomous and Retrieved Report Parameters (cont’d)




NTFCNCDE Notification Code (factory default value). The value in this field indicates the provisioned severity level of the condition being reported. The values for NTFCNCDE are given as follows:

• CR = Critical, reported using REPT ALM

• MJ = Major, reported using REPT ALM

• MN = Minor, reported using REPT ALM.

• NA = Not Alarmed, reported using REPT EVT

• NR = Not Reported when the event occurs, but the information is available using RTRV-COND-ALL or RTRV-AO

• CL = Cleared, not a provisionable value; is used only to identify the message that indicates a previously reported alarm has cleared

REPT TYPE Four types of autonomous messages can be reported by the system:

• REPT ALM—Report Alarm

• REPT EVT—Report Event

• REPT PM—Report Performance Monitoring

• REPT DBCHG—Report Database Change

SRVEFF The Service-effecting value is SA for service-affecting or NSA for non-service-affecting.

THLEV The Threshold Level identifies the magnitude of monitored parameter that, when crossed, will generate a threshold crossing message.

TID The Target Identifier is a unique name given to each NE when it is installed. This name identifies the particular NE to which each command is directed. Each TID is composed of a minimum of 7 and a maximum of 20 alphanumeric characters.

TMPER Time Period is the accumulation time period for the PM information. Valid TMPER values are 1-DAY and 15-MIN. A null value means that no TMPER is associated with this event or that the reported event is not a PM event.

UPDATE MANAGEMENT BLOCK Identifies the CTAG (Correlation Tag) of the TL1 command that modified the database.

Table 1-1: Autonomous and Retrieved Report Parameters (cont’d)



1.3: Maintenance PhilosophyMaintenance and Trouble ClearingFJTU-320-515-480

1.3 Maintenance Philosophy

The FLM 150 ADM multiplexes a maximum of 84 DS1 or three DS3 electrical signals into a SONET (Synchronous Optical Network) OC-3 optical signal. During normal operation, the system should require no maintenance on the part of the technician. However, if equipment or lines fail, self-diagnostic features identify the faulty system unit or line.

This practice lists the procedures used to maintain and troubleshoot the FLM 150 ADM.


1.4: Alarm and Status MessagesMaintenance and Trouble ClearingFJTU-320-515-480

1.4 Alarm and Status Messages

The FLM 150 ADM provides built-in test features to monitor both internal circuitry and input/output facilities. These features are described in Table 1-2.

In addition to the above features, any abnormal or trouble condition triggers alarm and status messages that are automatically reported to an interface device (such as a craft interface, OSS, or NMA) logged on the affected system. If no interface device is logged on when an alarm is generated, the messages can be retrieved by logging on the system and retrieving all or part of the AO buffer.

For FLM 150 ADM systems using Release 9.1 or earlier system operations software, no autonomous messages are displayed or stored in the AO buffer if there is no logon to the craft or OSS interfaces.

With Release 10 and later for the FLM 150 ADM, all autonomous messages are stored in the AO buffer, regardless of the logon status of the craft and OSS interfaces. The AO buffer has a capacity of 500 messages. It is a first-in, first-out (FIFO) buffer.

Current alarms can also be retrieved using the retrieve alarm TL1 command or using the FLEXR™ alarm window.

Section 3, in this practice, lists the possible alarm and status conditions for the FLM 150 ADM system, along with the probable causes and suggested corrective actions.

The system reports critical, major, and minor alarms.

• Office alarms announce trouble occurring at both near-end (NE) and far-end (FE) locations.

• Self-diagnostic features identify failures of faulty units or lines through the FAIL or LINE LED on each unit. The status is indicated by the NE ACT, FE ACT, or ABN LEDs on the AW1A unit or the LINE LED on the related channel unit.

Table 1-2: Built-In Test Features

Feature Purpose

• Redundant channel units

• Synchronization units

• Switching units

• Power supplies

Support critical data paths within the system

• Relays to office alarm systems

• Status LEDs on unit front panels

Provide maintenance personnel with visual and audible information


1.5: Trouble Analysis ProceduresMaintenance and Trouble ClearingFJTU-320-515-480

1.5 Trouble Analysis Procedures

1.5.1 General

When alarm indications are received, retrieve the alarms from the NEs using FLEXR or TL1 messages. By using the retrieved condition type, resolve troubles in the order of severity. Refer to Section 3, Responding to Alarms and Conditions, for trouble-clearing information.

In regard to clearing troubles, the following assumptions are made:

• All FLM 150 ADM shelves in the network are properly equipped.

• Multiple trouble indications may have a single cause.

• Only one failure exists for the indication.

The local FLM 150 ADM displays the equipment number of any remote alarm source on a 7-segment indicator on the front panel of the MP1A unit.

The local AW1A unit provides critical (CR), major (MJ), minor (MN), and abnormal (ABN) alarm indications on the front panel for both the local and the remote site.

Section 4 , in this practice, lists the precedures for replacing the plug-in units. If the alarm does not clear after you install the replacement unit, return the original plug-in unit to operation.

1.5.2 Alarm Message Flooding

In ring configurations, a serious event, such as a fiber cut, may flood the autonomous message system with path-switch event reports, even though it does not affect traffic. These messages are insignificant compared to the LOS alarm that is also reported. With Release 10 and later system software, path-switch event messages can be inhibited to prevent this flooding.


1.6: Repairing Defective UnitsMaintenance and Trouble ClearingFJTU-320-515-480

1.6 Repairing Defective Units

Fujitsu does not recommend field repair of defective units. Equipment failures should be corrected by replacing the defective unit with a working spare. Return defective units to a Fujitsu field service office.

Units under warranty will be repaired or replaced with new or refurbished units and returned. Equipment out of warranty will be evaluated to determine the repair cost and date of delivery. The field service office will then notify you concerning the cost and delivery date and will request authorization to proceed with repairs. Fujitsu also offers a fixed-price repair and exchange service. Information about the defective units can be furnished by mail or telephone. In any correspondence, include the following information:

• The unit part number and serial number

• A brief description of failure symptoms

• The original purchase order number covering the unit

• The return shipping address

• The shipping mode preference

• The invoice

• The name and telephone number of the person to contact for further information

Ensure that the units you return are properly packaged to prevent damage. Fujitsu is not liable for damage incurred during shipment.


1.7: Front and Rear ViewsMaintenance and Trouble ClearingFJTU-320-515-480

1.7 Front and Rear Views

Figure 1-1 is a front view of the FLM 150 ADM shelf showing the plug-in units and their associated equipment slots.

FC9612SVL4

SV1A-TL4

TERM

FAIL

LINE

ACS

FC9612MP31

MP1A-V3

FAIL

FESEL

CPURESET

HG1 MODE

FC96162SAM1

HS1A-AD1

FAIL

LINE

FORCE

AUTO

MNL

FORCE

AUTO

MNL

HG 2 MODE

FAIL/ON PTCT

FC9612LSD1

LS1A-D1HC1A-3MR1

FAIL/SVCLINE

FAIL/SVCLINE

FC9612TSB1 FC9612TSB1

TS1A-BSC TS1A-BSC

PW1A PW1AAW1A 3-W 3-P 3

LS1A4-W 4-P 4

LS1A5-W 5-P 5

LS1A1-W 1-P 2-W 2-P

MC1A MC1A MC1A HC1A

TCA TCA 3-1 3-2 3-3 3-4 3-5 3-6 3-7 3-P 4-1 4-2 4-3 4-4 4-5 4-6 4-7 4-P 5-1 5-2 5-3 5-4 5-5 5-6 5-7 5-P

LC1A

WTS1A

PTS1A

HS1A MP1A SV1A

FLM 150 ADM

LC1A-D1

FC

9612

LD11FAIL/

SVCE

LINE

EC1A

FAIL/ON PTCT

LS1A-D1

FAIL/ON PTCT

LS1A-D1MC1A-MDM1

FC9612MDM1

FAILSVCLINE

FC9612LSD1 FC9612LSD1

MC1A-MDM1

FAILSVCLINE

FC9612MDM1

MC1A-MDM1

FAILSVCLINE

FC9612MDM1

MC1A-MDM1

FAILSVCLINE

FC9612MDM1

MC1A-MDM1

FAILSVCLINE

MC1A-MDM1

FAILSVCLINE

AW1A-BSC

FC9612AWB1

ACO

LAMPTEST

CR

MJ

MN

ABN

NE ACT

FE ACT

LC1A-D1

FC

9612

LD11FAIL/

SVCE

LINE

LC1A-D1

FC

9612

LD11FAIL/

SVCE

LINE

LC1A-D1

FC

9612

LD11FAIL/

SVCE

LINE

LC1A-D1

FC

9612

LD11FAIL/

SVCE

LINE

LC1A-D1

FC

9612

LD11FAIL/

SVCE

LINE

LC1A-D1

FC

9612

LD11FAIL/

SVCE

LINE

LC1A-D1F

C96

12LD

11FAIL/SVCE

LINE

LC1A-D1

FC

9612

LD11FAIL/

SVCE

LINE

LC1A-D1

FC

9612

LD11FAIL/

SVCE

LINE

LC1A-D1

FC

9612

LD11FAIL/

SVCE

LINE

LC1A-D1

FC

9612

LD11FAIL/

SVCE

LINE

LC1A-D1

FC

9612

LD11FAIL/

SVCE

LINE

LC1A-D1

FC

9612

LD11FAIL/

SVCE

LINE

LC1A-D1

FC

9612

LD11FAIL/

SVCE

LINE

LC1A-D1

FC

9612

LD11FAIL/

SVCE

LINE

LC1A-D1

FC

9612

LD11FAIL/

SVCE

LINE

LC1A-D1

FC

9612

LD11FAIL/

SVCE

LINE

LC1A-D1

FC

9612

LD11FAIL/

SVCE

LINE

LC1A-D1

FC

9612

LD11FAIL/

SVCE

LINE

LC1A-D1

FC

9612

LD11FAIL/

SVCE

LINE

LC1A-D1

FC

9612

LD11FAIL/

SVCE

LINE

LC1A-D1

FC

9612

LD11FAIL/

SVCE

LINE

LC1A-D1

FC

9612

LD11FAIL/

SVCE

LINE

FC9616TCA1 FC9616TCA1

FAIL/SVCE

LINE

FAIL/SVCE

LINE

TC

A

TC

A

PWR

FC9612PW11

+5.4V-5.6V

SG

MAIN

G

PW1A

PWR ON

ON

OFF

PWR

PWR

FC9612PW11

+5.4V-5.6V

SG

MAIN

G

PW1A

PWR ON

ON

OFF

PWR

FC9612H3M1

FAIL

LINE

SEND

RCV

ON LINE

DA

NG

ER

HC1A-3MR1

FC9612H3M1

FAIL

LINE

SEND

RCV

ON LINE

DA

NG

ER

F9612MDM1 F9612MDM1

o200

77.4

ESDFG

Figure 1-1: FLM 150 ADM Shelf Front View


1.7: Front and Rear ViewsMaintenance and Trouble ClearingFJTU-320-515-480

Figure 1-2 is a rear view of the FLM 150 ADM shelf backplane showing cable connectors and terminals.

S OUT CN21 S OUT CN20 S OUT CN19

R IN CN24 R IN CN23 R IN CN22

CH3 CH2 CH1

MODEMCN11

ALMCN1

MAIN A

MAIN B

GA

GB

OHACN2

SECONDCN3

PRIMCN4

OSS1CN9

OW/E2A1CN7

STS-1GP1

CN17 CN15 CN13

DS-1S INGP5

DS-1S INGP4

DS-1S INGP3

DS-1R OUTGP5

DS-1R OUTGP4

DS-1R OUTGP3

EXT CLKH.K.1CN6

OW

CN12

PWR

CN18 CN16 CN14

H.K.2CN5

S OUT CN27 S OUT CN26 S OUT CN25

R IN CN30 R IN CN29 R IN CN28

CH3 CH2 CH1STS-1GP2

OW/E2A2CN8

T

R

S IN CN33 S IN CN32 S IN CN31

R OUT CN36 R OUT CN35 R OUT CN34

GP5 GP4 GP3

STS-1/DS3

OSS2

CN10

FG

d243

2.4

Figure 1-2: FLM 150 ADM Shelf Rear View


This page intentionally left blank.


2.1: Overview

2 Plug-In Unit Front-Panel Devices

2.1 Overview

2.1.1 Introduction

This section lists the condition types shown by the LEDs on the plug-in units. Tables 2-1 through 2-19 show the LED indications for the FLM 150 ADM shelf (with the exception of LEDs relating to FASTLANE ™plug-in units). For simplicity, the LED colors caused by the lamp test function are not presented in the table. In general, for 1-color LEDs, the lamp test color is the same as shown for the LED function. For 2-color LEDs, the lamp test color is yellow.

For LED information relating to FASTLANE plug-in unit LED information, refer to the FASTLANE I practice, FJTU-320-515-110, and FASTLANE II practice, FJTU-320-515-111.

2.1.2 Other Resources

To perform related trouble-clearing tasks, refer to the following sections in this practice:

• To replace a unit: Refer to Section 4, in this practice, or the Table of Contents, located in the front of this practice, to select the appropriate unit replacement procedure.

• To retrieve a condition message: Refer to Section 1.1, Alarm/Status Identification, to retrieve and interpret alarms, transient conditions, and standing conditions.

• To interpret message parameters: Refer to Section 1.2, Message Parameter Interpretation, for information on understanding and interpreting condition messages.

• To respond to an alarm or condition: Refer to Section 3, Responding to Alarms and Conditions. Find the condition message (listed in alphabetical order) and perform the corrective action indicated.

• Unit Descriptions: Refer to the Unit Descriptions practice, FJTU-320-515-000, to select the appropriate unit description.


2.2: LED DescriptionsMaintenance and Trouble ClearingFJTU-320-515-480

2.2 LED Descriptions

Table 2-1: AW1A LED Descriptions

LED Color Meaning

Note: The LEDs on these units are also used to indicate alarm information at other sites. Verify that the local shelf is the source of the alarm by checking that the NE ACT LED is lit red and the FE ACT LED is off. To select the local shelf, repeatedly press the FE SEL button on the MP1A unit until a decimal shows in the EQPT NO. window.

CR Red A critical (service-affecting) alarm exists on or has been detected by the local network element.

Off Normal operation.

MJ Red A major (service-affecting) alarm exists on or has been detected by the local network element.


MN Yellow A minor (non–service-affecting) alarm exists on or has been detected by the local network element.


ABN Yellow An abnormal condition, such as a forced switch.


PMN

(AW1-ENH only)

Red Housekeeping 1 alarm is on (HK1).


NE ACT Red (Near-end activity) The failure LEDs displayed on the AW1A front panel refer to alarms reported by the local shelf.


FE ACT Red (Far-end activity)= The failure LEDs displayed on the AW1A front panel refer to alarms reported by the shelf with the ID number indicated by the EQPT. NO. (7-segment LED) display on the MP1A unit.


ACO Green Pressing the ACO (alarm cutoff) button turns off the visual and audible office alarms.


CALL

(AW1A-ENH only)

Green Lights green for 90 seconds when this station is called by another station.




Table 2-2: EC1A LED Descriptions

LED Color Meaning

FAIL Red An internal failure.

Blinking red Unit MISMOUNT: the system is configured for a different mode, or the mounted unit is not intended for use in the current configuration.

Off Normal operation (in service).

LINE Red An incoming data communications channel (DCC) signal failure.


Table 2-3: HC1A-3xxx LED Descriptions

LED Color Meaning

FAIL Red An internal failure or an incoming signal failure (such as an LOS or LOF).


LINE Red The incoming signal has degraded or failed. A service-affecting alarm (such as BERSDP or BERSFP) exists on both drops.

Yellow A non–service-affecting failure, such as an AIS or RFI (remote failure indication), has been detected.


SEND Green The unit is transmitting.

Off Standby or out of service.

RCV Green The unit is receiving.




Table 2-4: HC1A-6Lx1 LED Descriptions

LED Color Meaning

FAIL Red An internal failure or an incoming signal failure (such as an LOS or LOF) or interconnect cables may be disconnected.




Yellow A non–service-affecting failure, such as an AIS or RFI, has been detected.


SEND Green The unit is transmitting.


RCV Green The unit is receiving.


Table 2-5: HC1A-STS1 LED Descriptions

LED Color Meaning

FAIL/SVCE Red An internal failure.


Green Normal operation (in service).


LINE 1/2/3 Red The incoming signal has degraded or failed. A service-affecting alarm (such as a BERSDP or BERSFP) exists on both drops.

Yellow A non–service-affecting failure, such as an AIS or RFI, has been detected.

Green Normal operation (in service), TRMT (transmit) and RCV (receive).



Table 2-6: HS1A-AD1/-AD2 LED Descriptions

LED Color Meaning

FAIL Red An internal failure.



LINE Red An automatic protection switching (APS) byte failure (APSB), channel mismatch (APSCM), or DCC failure (DCCFAIL).


HG1 Mode

FORCE Green A forced switch has been performed.

AUTO Green Automatic switching is in effect (normal operation).

MNL Green A manual switch has been performed.

HG2 Mode

FORCE Green A forced switch has been performed.

AUTO Green Automatic switching is in effect (normal operation).

MNL Green A manual switch has been performed.



Table 2-7: LC1A-D1/-D1E/-D1E2 LED Descriptions

LED Color Meaning

FAIL/SVCE Red An internal failure, or the internal clock or building integrated timing supply (BITS) output is down.




LINE Red The incoming signal has degraded or failed. A service-affecting alarm (such as a bipolar violation [BPV] within a DS1, or an LOS, LOF, or bit error rate [BER] exists.

Yellow One or more non–service-affecting path-level conditions exist. Possible conditions include an AIS within the virtual tributary (VT) path, or an unequipped code (UNEQ).


Table 2-8: LC1A-F6/-F6C1/-F6T1 LED Descriptions

LED Color Meaning

FAIL/SVCE Red An internal failure, or the internal clock or BITS output is down.




Table 2-9: LS1A-D1 LED Descriptions

LED Color Meaning

FAIL/ON PTCT Red An internal failure

Green Switched to protect

Off Normal operation (in service)



Table 2-10: MC1A-D3/-D3A2 LED Descriptions

LED Color Meaning





LINE Red The incoming signal has degraded or failed. A service-affecting alarm, such as a BERSDP or BERSFP, exists on both drops.

Yellow One or more non–service-affecting path-level conditions exist. Possible conditions include a BERSDP, BERSFP, AIS, RFI, or UNEQ (unequipped).


Table 2-11: MC1A-MDM1 LED Descriptions

LED Color Meaning





LINE Red An incoming AIS, an LOS on the DS1 clock inputs, or a loss of pointer (LOP) on the STS-1.

Yellow An AIS or RFI has been detected on the incoming line.




Table 2-12: MC1A-STS1/-ST1P LED Descriptions

LED Color Meaning





LINE Red The incoming signal has degraded or failed. A service-affecting alarm, such as a BERSDP or BERSFP, exists on both drops.

Yellow One or more non–service-affecting path-level conditions exist. Possible conditions include a BERSDP, BERSFP, AIS, RFI, or UNEQ (unequipped).


Table 2-13: MC6A LED Descriptions

LED Color Meaning

FAIL Red An internal failure, or an incoming signal failure, such as an LOS or LOF.




Yellow One or more non–service-affecting path-level conditions exist. Possible conditions include a BERSDP, BERSFP, AIS, or RFI (remote failure indication).


SEND Green The unit is transmitting normally.


RCV Green The unit is receiving normally.




Table 2-14: MP1A LED Descriptions

LED Color Meaning

FAIL Red An internal failure of the central processing unit (CPU).



EQPT. NO. Red 7-segment LED readout

If a numeral, indicates the ID number of the selected far-end shelf. If a decimal point, indicates the local shelf.

Table 2-15: PW1A LED Descriptions

LED Color Meaning

PWR Red A tripped circuit breaker, or a unit failure

Green Normal operation (in service)

Off No power to the unit

Table 2-16: SV1A LED Descriptions

LED Color Meaning

FAIL Red An internal microprocessor failure.



LINE Red An incoming line failure.


ACS Green The SV1A has been accessed by a craft interface terminal or modem.

Off Turns off after approximately 30 minutes of no electrical signal.

SWDL

(SV1A-TDL1 only)

Green CPY-MEM in progress, software download scheduled for activation; or activation without CANC-VALTM.



Table 2-17: TCA LED Descriptions

LED Color Meaning



Off Indicates standby or out of service.

LINE Red The incoming signal has degraded or failed. A service-affecting alarm (such as an AIS, LOS, or LOF) exists on both drops.


Table 2-18: TCA–ENH LED Descriptions

LED Color Meaning

FAIL/SVCE Red Unit failure

Green Normal (in service)

Yellow AW1A unit TST button pressed

LINE Red Line failure

Green Normal (in service)



Table 2-19: TS1A LED Descriptions

LED Color Meaning


Blinking red Unit MISMOUNT: the system is configured for a different mode, or the mismounted unit is not used in this configuration.



LINE Red The incoming signal has degraded or failed. A service-affecting alarm (such as an AIS or RFI) exists on both drops.

Yellow One or more non–service-affecting path-level conditions exist. Possible conditions include an AIS or RFI (remote failure indication).




3.1: Condition Code Responses

3 Responding to Alarms and Conditions

3.1 Condition Code Responses

3.1.1 Summary

Use this section to respond to conditions reported by the FLM 150 ADM system (with the exception of FASTLANE ™applications). When the condition code indicates an alarm event, this section provides trouble-clearing information. Transient and standing conditions are also indicated by condition codes and in some cases are associated with an alarm condition. General information about the condition codes is presented. This is followed by suggested procedural steps in clearing troubles. The majority of this section consists of the FLM 150 ADM alarm and status message condition codes, which are presented in alphabetical order. Each is accompanied by a table that provides the following:

• Access identifier (AID) type

• Direction of signal on which trouble (or trouble indicator) appears

• Probable cause(s)

• Suggested corrective action(s)

For some condition types, such as the bit error rate (BER) condition types, additional information before the table explains how to interpret the FLEXR® or TL1 message.

Note: Although all condition types reflect near-end messages, the source of a problem may be at a remote location or in near-end tributary equipment.

For responding to alarms and conditions relating to FASTLANE applications, refer to the FASTLANE I practice, FJTU-320-515-110, and FASTLANE II practice, FJTU-320-515-111.


3.1: Condition Code ResponsesMaintenance and Trouble ClearingFJTU-320-515-480

3.1.2 Condition Code Types

There are three types of conditions that are reported by the FLM 150 ADM—alarm conditions, transient conditions, and standing conditions. These conditions are defined as follows:

• Alarm conditions trigger autonomous messages to notify maintenance and operational personnel of failure or fault conditions that require immediate response. Autonomous alarm condition messages carry an ALMEVT label. In addition, office alarms alert local maintenance personnel with audible and visible indications that an alarm condition exists. Alarm conditions can also be reported to a remote operations support system (OSS). Alarm messages can also be retrieved via the craft terminal with the RTRV-ALM-ALL command or from FLEXR by clicking in the Alarm Summary window.

• Transient condition messages provide a record of events that are momentary. These may or may not be associated with an alarm event. Autonomous transient condition messages carry an EVTTC label. The two categories are:

- Notification of threshold crossings of performance monitoring (PM) parameters

- Notification of switches between working and protection equipment.

• Standing conditions result from a manual operation, such as a manual switch, loopback, mismounted cards, or the use of the internal test signal capability of the network element (NE). The condition remains present until the manual action that created the condition is released. Many standing conditions are accompanied by the alarm condition MAN, which stays active until the manual switch, loopback, or signal injection is released. Standing conditions trigger autonomous messages that carry an EVTSC label. A standing condition message can be retrieved with the RTRV-COND-ALL command.


3.1: Condition Code ResponsesMaintenance and Trouble ClearingFJTU-320-515-480

3.1.3 Other Resources

For trouble-clearing task details, refer to the following sections:

• To replace a unit: Refer to Section 4, in this practice, or the Table of Contents, located in the front of this practice, to select the appropriate unit replacement procedure.

• To retrieve a condition message: Refer to Section 1.1, Alarm/Status Identification, to retrieve and interpret alarms, transient conditions, and standing conditions.

• To interpret a message: Refer to Section 1.2, Message Parameter Interpretation, for information on understanding and interpreting condition messages.

• To interpret LED display: Refer to Section 2, Plug-In Unit Front-Panel Devices, to interpret the codes shown by the LEDs on the plug-in units.


3.2: ProcedureMaintenance and Trouble ClearingFJTU-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).


3.3: ACTLPBKFMaintenance and Trouble ClearingFJTU-320-515-480

3.3 ACTLPBKF

The NE reporting the condition has a loopback control operated to provide a near-end facility loopback for testing at the same site.

Table 3-1: ACTLPBFK (Facility Loopback Activated)—Standing Condition

AID Type Direction Probable Cause Suggested Corrective Action

EC1 NA OPR-LPBK-EC1 has been executed.

• Verify that the facility testing is complete.

• Execute the RLS-LPBK command.

OC3 NA OPR-LPBK-OC3 has been executed.



OVTG NA OPR-LPBK-OVTG has been executed.



T1 NA OPR-LPBK-T1 has been executed.







3.4: ACTLPBKTMaintenance and Trouble ClearingFJTU-320-515-480

3.4 ACTLPBKT

The NE reporting the condition has a loopback control operated to provide a terminal loopback that loops the selected channel back to the far end for testing at that site.

3.5 AIS

Table 3-2: ACTLPBKT (Terminal Loopback Activated)—Standing Condition


EC1 NA OPR-LPBK-EC1 has been executed.



OC3 NA OPR-LPBK-OC3 has been executed.



OVTG NA OPR-LPBK-OVTG has been executed.









Table 3-3: AIS (Alarm Indication Signal)—Alarm Event


EC1 TRMT/RCV The locally received middle-speed (TRMT) or high-speed (RCV) STS-1 signal contains an AIS. This indicates a remote failure.

• Retrieve the alarms at upstream sites.

• Clear any upstream service-affecting alarms.

OC3

OC12

TRMT/RCV The locally received OC-3/OC-12 signal contains an AIS. This indicates a remote failure.

Retrieve the alarms at the upstream site. There should be an OC-3/OC-12 LOS or other service-affecting alarm reported at the upstream site.

Issue 9, May 1999 FNC and FNC Customer Use Only Vol. ll, 0.3-6

3.5: AISMaintenance and Trouble ClearingFJTU-320-515-480

OVTG The locally received optical virtual tributary group (OVTG) signal contains an AIS. This indicates a remote failure.

Retrieve the alarms at the remote FLM 6 site.

STS1 The STS signal demultiplexed from the OC-3 contains an AIS. This AIS can result from an upstream failure along the STS path. Possible failures include OC-3 failures (such as an LOS) and T3 input failures (such as a T3 LOS).

• Check for an upstream OC-3/OC-12 signal failure.

• Check for a service-affecting alarm where the tributary signal enters the far end of the ring.

• Verify that the HC1A or MC1A unit is in service and has not failed.

• Check for deleted STS-1 cross-connects.

T1 NA A failure on the input side of the building integrated timing supply (BITS) timing source.

A DS1 far-end NE (such as a channel bank) has lost its downstream input and has inserted an AIS.

• Refer to the timing source vendor documentation for procedures to isolate and repair the failure.

• Retrieve the alarms from the upstream sites.

TRMT

(LC1A-D1 or LC1A-D1E unit installed)

TRMT/RCV


TRMT

(Transmux unit installed)

T2 TRMT TRMT: The DS2 input contains an AIS.

Check for alarms on the upstream asynchronous equipment.

T3 TRMT/RCV TRMT: The DS3 input contains an AIS.

RCV: An upstream failure.

Check for alarms on the upstream asynchronous equipment.

VT1 RCV The virtual tributary (VT) signal demultiplexed from the OC-3 contains an AIS.

• Check for OC-3/OC-12 signal failure.

• Verify that the HC1A or MC1A unit is in service and has not failed.

• Check for a deleted VT cross-connect.

Table 3-3: AIS (Alarm Indication Signal)—Alarm Event (cont’d)


DN

616

3

TRMT

OC-3/OC-12

ADDEDSIGNAL

150 ADMd6

164

RCV

OC-3/OC-12

DROPPEDSIGNAL

150 ADM


3.6: AL1PLSMaintenance and Trouble ClearingFJTU-320-515-480

3.6 AL1PLS

3.7 APSB

Table 3-4: AL1PLS (All-Ones Pulse Generated)—Standing Condition


T1 NA The internal all-ones test signal has been connected to the external clock output port (T1) for test purposes.

Check to see if testing is complete before disconnecting the test signal.

T3 RCV The internal all-ones test signal has been connected to the DS3 channel (T3) for test purposes.


Table 3-5: APSB (Automatic Protection Switching Byte Failure)—Alarm Event


OC3 TRMT/RCV An automatic protection switching (APS) channel byte failure. The APS bytes (K1/K2) are in an invalid state.

• Check for OC-3 near- and far-end optical channel unit failures.

• Check for failure indicators in the HS1A-AD1 unit. To replace the unit, refer to Section 4.10, Replacing the High-Speed Switch Control (HS1A) Unit.


3.8: B1ERRMaintenance and Trouble ClearingFJTU-320-515-480

3.8 B1ERR

3.9 B2ERR

Table 3-6: B1ERR (Error Data Generated)—Standing Condition


OC-3 TRMT/RCV CONN-TSTSIG-OC3 has been executed.


• Execute the DISC-TSTSIG-OC3 command.

OC-12 CONN-TSTSIG-OC12 has been executed.



Table 3-7: B2ERR (B2 Error Data Generated)—Standing Condition


EC1/HC TRMT/RCV CONN-TSTSIG-EC1 has been executed.


• Execute the DISC-TSTSIG-EC1 command.

OC3 TRMT/RCV CONN-TSTSIG-OC3 has been executed.



OC12 CONN-TSTSIG-OC12 has been executed.



DN

616

3

TRMT

OC-3/OC-12

ADDEDSIGNAL

150 ADM

DN

616

3

TRMT

OC-3/OC-12

ADDEDSIGNAL

150 ADM


3.10: B3ERRMaintenance and Trouble ClearingFJTU-320-515-480

3.10 B3ERR

3.11 BERSDL and BERSFL

Table 3-8: B3ERR (B3 Error Data Generated)—Standing Condition


STS1 TRMT/RCV CONN-TSTSIG-STS1 has been executed.


• Execute the DISC-TSTSIG-STS1 command.

Table 3-9: BERSDL and BERSFL (Bit Error Rate Signal Degrade/Fail-Line)—Alarm Event


OC3 TRMT/RCV • The OC-3 receive power has fallen below or exceeded the specified limits. May be accompanied by an OC-3 LOS alarm.

• A fiber problem.

• A connector in the OC-3 optical link is dirty.

• The far-end transmitter is creating bit errors.

• Points of large optical reflection exist along the OC-3 link.

• Verify the local receive and upstream transmit levels. Clean the optical connectors.

• Verify good optical connections to the local and far-end OC-3 units and at the Lightwave Distribution Frame (LDF) panels along the link (see Section 5.1, Handling Fiber Cables, and Section 5.2, Cleaning, Connecting, and Disconnecting the Optical Connectors.)

• Replace the far-end OC-3 channel unit. Refer to Section 4.12, Replacing the OC-3 Optical Channel (HC1A and MC6A) Units, and Section 4.16, Replacing the Low-Speed Channel–OVTG (LC1A-F6xx) Unit.

OVTG The incoming OVTG signal has fallen below or exceeded the specified limits. May be accompanied by an OVTG LOS alarm.

• Check the remote FLM 6 for OVTG unit removal or failure.

• Verify the local receive optical levels, and the upstream transmit levels. Clean the optical connectors.

• Check the fiber link and perform trouble analysis procedures as necessary.

T1 TRMT • The DS1 input has exceeded its provisioned BER threshold.

• A DS1 far-end NE (such as a channel bank) failure.

• A DS1 cable failure.

• Verify the cable connections at both sites.

• Perform DS1 source trouble analysis.

• Replace the DS1 cable.

DN

616

3

TRMT

OC-3/OC-12

ADDEDSIGNAL

150 ADM


3.11: BERSDL and BERSFLMaintenance and Trouble ClearingFJTU-320-515-480

These BERSDL and BERSFL alarm messages indicate line-level problems that may only exist between line terminating equipment (LTE). Figure 3-1 shows how to determine exactly where the line BER problem is located. Notes 1 and 2 (below the figure and referenced within the circles) give examples of how to determine problem locations.

Node A

ADM REGEN

Node B Node C Node DOC-n

Link A Link B Link C

12

d6

19

8

Line Section Section

Line

DS3

ADM

DS3

OC-nOC-n

ADM

Figure 3-1: Line BER Causes

Note 1: If a line BER problem is detected here, the bit errors may be caused by a fiber problem on Link A or a bad transmitter at Node B.

Note 2: If a line BER problem is detected here, the bit errors may be caused by a fiber problem on Link B or Link C, a bad plug-in unit at the REGEN site, or a bad transmitter at Node C or Node D. If Node C is actually line terminating and not a true REGEN, the bit errors are caused by problems on Link B only.


3.12: BERSDP and BERSFPMaintenance and Trouble ClearingFJTU-320-515-480

3.12 BERSDP and BERSFP

These BERSDP and BERSFP alarm messages indicate path-level problems. Refer to Figure 3-2 for help in finding the problem.

Table 3-10: BERSDP and BERSFP (Bit Error Rate Signal Degrade/Fail-Path)—Alarm Event


STS-1

VT-1

• The STS signal demultiplexed and dropped from the OC-3/OC-12 has exceeded its signal degrade threshold.

• The BER is detected at a drop port, but the problem could be caused by a plug-in unit along the Sychronous Optical Network (SONET) path.

• Examine the network for other path BER problems and retrieve PM data to find a possible common source of the bit errors.

• If a tributary channel unit is a possible source of the bit errors, perform a manual protection switch to the protection unit. If the BER alarm clears, replace the original Working unit. Refer to Section 4, in this practice, or the Table of Contents, located in the front of this practice, to select the appropriate unit replacement procedure.

• If the trouble can be isolated to an original HC1A unit, replace the unit. Refer to Section 4.12, Replacing the OC-3 Optical Channel (HC1A and MC6A) Units, and Section 4.16, Replacing the Low-Speed Channel–OVTG (LC1A-F6xx) Unit.

Caution: Replacing an HC1A unit will cause hits on previously working traffic. Perform this step only after careful fault isolation.

d616

4

RCV

OC-3/OC-12

DROPPEDSIGNAL

150 ADM

Node A

ADM REGEN

Node B Node C Node DOC-n

Link A Link B Link C

1d

61

99

.1

DS3 DS3

PathOrigination

Path

ADM ADM

OC-nOC-n

Figure 3-2: Path BER Causes

Note 1: If an STS path BER problem is detected here, the bit errors are not caused by a problem on any of the fiber links. The bit errors may be caused by a plug-in unit at the source or destination.


3.13: BIP2ERRMaintenance and Trouble ClearingFJTU-320-515-480

3.13 BIP2ERR

3.14 CANVAL

3.15 CLEI-FLT

3.16 CLEI-LBC

Table 3-11: BIP2ERR (BIP2 Error Data Generated)—Standing Condition


VT1 TRMT CONN-TSTSIG-VT1 has been executed.


• Execute the DISC-TSTSIG-VT1 command.

Table 3-12: CANVAL (CANC-VALTM Command Acceptable)—Transient Condition


COM NA NE can now accept cancel validation timer for software download (SWDL).

Send CANC-VALTM command to NE if new software version is accepted by technician.

Table 3-13: CLEI-FLT (Plug-In Failure)—Alarm Event


EQPT NA The plug-in unit has failed. Refer to Section 4, in this practice, or the Table of Contents, located in the front of this practice, to select the appropriate unit replacement procedure.

Table 3-14: CLEI-LBC (Laser Bias Current Alarm)—Standing Condition


EQPT NA The laser diode mounted in the LC1A card may be bad.

Refer to Section 4, in this practice, or the Table of Contents, located in the front of this practice, to select the appropriate unit replacement procedure.


3.17: CLEI-TEMPMaintenance and Trouble ClearingFJTU-320-515-480

3.17 CLEI-TEMP

3.18 CPY Conditions

The following are the definitions of the CPY conditions:

• CPY-FILE-PRTL (Copy file status is partial.)

• CPY-FILE-FAIL (Copy file status is failed.)

• CPY-FILE-COMPL (Copy file status is complete.)

• CPY-MEM-FAIL (Copy memory status is failed.)

• CPY-MEM-COMPL (Copy memory status is complete.)

Table 3-15: CLEI-TEMP (Laser Temperature Increased)—Standing Condition


EQPT NA • The temperature of the laser transmitter has exceeded a preset threshold.

• The ambient air temperature is too high.

• The thermoelectric cooling unit in the laser transmitter has failed.

• Check site ambient temperature and/or cooling system.

• Check shelf airflow for obstructions.

• Replace optical transmitter unit.

Table 3-16: CPY Conditions (CPY-FILE-PRTL, CPY-FILE-FAIL, CPY-MEM-FAIL)—Transient Conditions


FILE NA Attempted to copy file or memory when another copy file/memory is still active.

Check the SWDL lead on the SV1A-TDL1 unit. Wait until the LED is off (or until COMPL MSG is received) before attempting CPY-FILE or CPY-MEM.


3.19: CTNEQPTMaintenance and Trouble ClearingFJTU-320-515-480

3.19 CTNEQPT

3.20 DCCFAIL

Table 3-17: CTNEQPT (Ribbon Cable Disconnect)—Alarm Event


EQPT NA The circuit between the two HC1A-6Lx1 units has failed.

• Verify good connections between the HC1A-6Lx1 units (refer to Section 5.1, Handling Fiber Cables, and Section 5.2, Cleaning, Connecting, and Disconnecting the Optical Connectors).

• Replace the ribbon cable between the HC1A-6Lx1 units.

Table 3-18: DCCFAIL (Data Communications Connect Failure)—Alarm Event

AIDType Direction Probable Cause Suggested Corrective Action

EC1 TRMT/RCV The Section Data Communications Channel (SDCC) on the incoming EC-1 line from the tributary has failed.

• Verify that the tributary STS-1 source has not failed. If an EC-1 LOS alarm exists, clear that trouble first.

• Verify that the coax cable is connected securely.

• At both the local and upstream sites, verify that the SDCC is provisioned as In Service.

• Verify that the SDCC parameters for this site and the upstream site are identical.

• Verify that the MC1A-STS1 unit is in service and has not failed. Refer to Section 4.13, Replacing the STS-1 Electrical Channel (HC1A-STS1) Unit.

• Verify that the HC1A unit is in service and has not failed. Refer to Section 4.12, Replacing the OC-3 Optical Channel (HC1A and MC6A) Units, and Section 4.16, Replacing the Low-Speed Channel–OVTG (LC1A-F6xx) Unit.

• Verify that the HC1A unit has the correct issue number to ensure firmware compatibility.

• Verify that the SDCC has been initialized.


3.20: DCCFAILMaintenance and Trouble ClearingFJTU-320-515-480

OC3 TRMT/RCV The OC-3 SDCC has failed.


• At both the local and upstream sites, check for OC-3 optical channel unit failure/removal alarms. Refer to Section 4.12, Replacing the OC-3 Optical Channel (HC1A and MC6A) Units, and Section 4.16, Replacing the Low-Speed Channel–OVTG (LC1A-F6xx) Unit.

• At both the local and upstream sites, verify that the SDCC is provisioned In Service and initialized. Refer to Section 5.8, Correcting a Mismounted Unit, for procedures. (Use INIT-OSSI for SWDL units.)


• Verify that the local and upstream optical units have the correct issue numbers to ensure firmware compatibility.

OC12 The OC-12 Section Data Communications Channel (SDCC) has failed


• At both the local and upstream sites, check for OC-12 optical channel unit failure/removal alarms. Refer to Section 4.11, Replacing the OC-12 Optical Channel (HC1A-6Lx1) Units, and Section 4.16, Replacing the Low-Speed Channel–OVTG (LC1A-F6xx) Unit.

• At both the local and upstream sites, verify that the SDCC is provisioned In Service and initialized. Refer to Section 5.8, Correcting a Mismounted Unit, for procedures. (Use INIT-OSSI for SWDL units.)


• Verify that the local and upstream optical units have the correct issue numbers to ensure firmware compatibility.

OVTG The low-speed OVTG Section Data Communications Channel (SDCC) has failed.


• At both local and upstream sites, verify that no LC1A-F6 unit has failed or been removed.Refer to Section 4.12, Replacing the OC-3 Optical Channel (HC1A and MC6A) Units; Section 4.11, Replacing the OC-12 Optical Channel (HC1A-6Lx1) Units; and Section 4.16, Replacing the Low-Speed Channel–OVTG (LC1A-F6xx) Unit.

• At both the local and upstream sites, verify that the SDCC is provisioned as In Service and initialized. Refer to Section 5.8, Correcting a Mismounted Unit, for procedures.

Table 3-18: DCCFAIL (Data Communications Connect Failure)—Alarm Event (cont’d)

AIDType Direction Probable Cause Suggested Corrective Action

d616

4

RCV

OC-3/OC-12

DROPPEDSIGNAL

150 ADM

DN

61

63

TRMT

OC-3/OC-12

ADDEDSIGNAL

150 ADM


3.21: ECRESTARTMaintenance and Trouble ClearingFJTU-320-515-480

3.21 ECRESTART

3.22 FALLBK

3.23 FE Alarms

The following are the definitions for the FE Alarms:

• FECR (Far-End NE Critical alarm)

• FEENV (Far-End NE Environmental alarm)

• FEMJ (Far-End NE Major alarm)

• FEMN (Far-End NE Minor alarm)

Table 3-19: ECRESTART (EC Software Restart)—Transient Condition


EQPT NA The EC software has been restarted. No corrective action required.

Table 3-20: FALLBK (Fullback)—Transient Condition


COM NA System software reverting (fall back). No corrective action required.

Table 3-21: FE Alarms (FECR, FEENV, FEMJ, FEMN)—Alarm Events


OVTG NA A far-end alarm has occurred at the remote FLM 6 site.

Retrieve alarms at the remote FLM 6 site and clear these troubles.


3.24: FEAISMaintenance and Trouble ClearingFJTU-320-515-480

3.24 FEAIS

3.25 FEFLT-COM

3.26 FEFLT-T1

Table 3-22: FEAIS (Far-End Alarm Indication Signal)—Alarm Event


T3 Alarm indication signal detected from FEAC DL. (far-end alarm and control data link).

Retrieve the alarm and clear the trouble.

Table 3-23: FEFLT-COM (Far-End Common Equipment Failure)—Alarm Event


T3 Common equipment failure detected from the FEAC DL.


Table 3-24: FEFLT-T1 (Far-End DS1 Equipment Failure)—Alarm Event


T3 DS1 equipment failure detected from FEAC DL.


DN

61

63

TRMT

OC-3/OC-12

ADDEDSIGNAL

150 ADM

DN

61

63

TRMT

OC-3/OC-12

ADDEDSIGNAL

150 ADM

DN

61

63

TRMT

OC-3/OC-12

ADDEDSIGNAL

150 ADM


3.27: FEFLT-T1MMaintenance and Trouble ClearingFJTU-320-515-480

3.27 FEFLT-T1M

3.28 FEFLT-T1S

3.29 FEFLT-T3

Table 3-25: FEFLT-T1M (Far-End Multiple DS1 Loss of Signal)—Alarm Event


T3 Multiple DS1 loss of signal detected from FEAC DL.


Table 3-26: FEFLT-T1S (Far-End Single DS1 Loss of Signal)—Alarm Event


T3 Single DS1 loss of signal detected from FEAC DL.


Table 3-27: FEFLT-T3 (Far End DS3 Equipment Failure)—Alarm Event


T3 DS3 equipment failure detected from FEAC DL.


DN

61

63

TRMT

OC-3/OC-12

ADDEDSIGNAL

150 ADM

DN

61

63

TRMT

OC-3/OC-12

ADDEDSIGNAL

150 ADM

DN

61

63

TRMT

OC-3/OC-12

ADDEDSIGNAL

150 ADM


3.30: FEISDMaintenance and Trouble ClearingFJTU-320-515-480

3.30 FEISD

3.31 FELOS

3.32 FEOOF

Table 3-28: FEISD (Far-End DS3 Idle Signal)—Alarm Event


T3 DS3 idle signal detected from FEAC DL.


Table 3-29: FELOS (Far-End Loss of Signal)—Alarm Event


T3 Loss of signal detected from FEAC DL.


Table 3-30: FEOOF (Far-End Out of Frame)—Alarm Event


T3 Out of frame detected from FEAC DL.


DN

61

63

TRMT

OC-3/OC-12

ADDEDSIGNAL

150 ADM

DN

61

63

TRMT

OC-3/OC-12

ADDEDSIGNAL

150 ADM

DN

61

63

TRMT

OC-3/OC-12

ADDEDSIGNAL

150 ADM


3.33: FILECONFIG–ACTMaintenance and Trouble ClearingFJTU-320-515-480

3.33 FILECONFIG–ACT

3.34 FILECONFIG–STBY

3.35 FRCDSW

Table 3-31: FILECONFIG–ACT (File Configuration-Active)—Alarm Event


COM NA A mismatch failure of the file configuration among active nonvolatile memories (NVMs).

• Make sure the program files are correct. This condition could occur when the NE is powered up if the existing program files are incorrect.

Table 3-32: FILECONFIG–STBY (File Configuration-Standby)—Transient Condition


COM NA A mismatch failure of the file configuration among standby NVMs.

Verify that all program files for the new generic issue are installed in the Standby NVM and that the correct configuration file is present in the Standby NVM. After updating the files, the INIT-SYS will be allowed.

Note: With this condition, the NE will not allow the new generic issue to be started. The system will remain at the previous software version until another INIT-SYS is completed, after corrective action.

Table 3-33: FRCDSW (Forced Switch)—Standing Condition


OC3

OC12

OVTG

VT1

STS1

NA A manual (forced) switch to either Working or Protect is in effect. No automatic switching can occur until the forced switch is released.

• Check to see if there is a valid reason to maintain the forced switch condition.

• If appropriate, release the forced switch.

COM

(If SYNCMSG =Y)

NA A manual (forced) switch of the clock source.

• Check to see if there is a valid reason to maintain the forced switch condition.

• If appropriate, release the forced switch.


3.36: HMIAMaintenance and Trouble ClearingFJTU-320-515-480

3.36 HMIA

3.37 INIT-SYS-FAIL

3.38 INTFAIL

3.39 IPNOTREACH

Table 3-34: HMIA (Hardware Mismatch Alarm Indication)—Transient Condition


EQPT NA Maladjusted to EC1A hardware, mismatch alarm indication.

Correct the connection.

Table 3-35: INIT-SYS-FAIL (Initialization System Failure)—Transient Condition


COM NA Initialization failure-card removed or failed Replace card.

Table 3-36: INTFAIL (Interconnection Fail)—Alarm Event


EQPT NA MC1A misconnected or unit failure

• Correct the connection.

• Replace the MC1A unit.

Table 3-37: IPNOTREACH (IP = xxx.xxx.xxx.xxx Not Reachable)—Transient Condition


COM NA No IP connection to destination node or improper IP provisioning

Verify LCN physical connection from source to destination node. Verify IP provisioning at destination node.


3.40: IPREACHABLEMaintenance and Trouble ClearingFJTU-320-515-480

3.40 IPREACHABLE

3.41 ISD

3.42 ISOPLS

Table 3-38: IPREACHABLE (IP = xxx.xxx.xxx.xxx Reachable)—Transient Condition


COM NA IP address was reached successfully.

NA

Table 3-39: ISD (Idle Signal Detected)—Alarm Event


T3 DS3 idle signal detected Check for alarms on the upstream asynchronous equipment.

Table 3-40: ISOPLS (Isolation Pulse Generated)—Standing Condition


T1 NA The internal isolation pulse test signal has been connected to the external clock output port (T1) for test purposes.


T3 The internal isolation pulse test signal has been connected to DS3 channel (T3) for test purposes.


EC1 TMT/RCV The internal isolation pulse test signal has been connected to the electronic channel.


DN

61

63

TRMT

OC-3/OC-12

ADDEDSIGNAL

150 ADM

d6

16

4

RCV

OC-3/OC-12

DROPPEDSIGNAL

150 ADM


3.43: LOCKINMaintenance and Trouble ClearingFJTU-320-515-480

3.43 LOCKIN

3.44 LOCKOUT

Table 3-41: LOCKIN—Alarm Event


OC3

OVTG

NA Lockin has occurred on the high-speed OC-3 group. Some intermittent failure has caused more than four APS events within 10 minutes.

This indication should be accompanied by other OC-3 OVTG alarms listed in this section.

• Check the local receive and upstream transmit optical levels to verify that no optical unit has failed or been removed.

• Clean the optical connectors. (See Section 5.1, Handling Fiber Cables, and Section 5.2, Cleaning, Connecting, and Disconnecting the Optical Connectors).

• Lockin prevents continued switching under intermittent failures that affect both the working and protection lines. If lockin is not desired, it can be disabled by setting LIN=N for the OC-3 group by using the following TL1 command:

ED-FFP-OC3:TID:AID:CTAG:::LIN=N;

The FLEXR GT 1.1 steps are as follows:

Provisioning

System

Set System Lockin (select unit)

Switch Lockin =Y, N

Table 3-42: LOCKOUT—Standing Condition


OC3

OVTG

NA Manual lockout has been applied on the OC-3 group to prevent any automatic switching.

• Check to see if there is a valid reason to maintain the lockout condition.

• If appropriate, release the lockout.


3.45: LOFMaintenance and Trouble ClearingFJTU-320-515-480

3.45 LOF

Table 3-43: LOF (Loss of Frame)—Alarm Event

AID Type Direction Probable

Cause Suggested Corrective Action

EC1 TRMT/RCV A framing problem on the incoming STS-1 signal

• Inspect all aspects of the STS-1 link.

• Check the remote sites for unit removal or failure. Refer to Section 4, Replacing Units, for the appropriate unit replacement procedures.

• Verify that the coax cable is installed and connected securely.

OC3 TRMT/RCV A framing problem on the incoming OC-3 signal

• Check local receive and upstream transmit levels.

• Verify the local receive optical levels, as well as the upstream transmit optical levels. Clean the optical connectors.

• Check the upstream ADM for optical channel unit failure/removal.

• Verify good optical connections to the local and far-end OC-3 units and at the Lightwave Distribution Frame (LDF) panels along the link (refer to Section 5.1, Handling Fiber Cables, and Section 5.2, Cleaning, Connecting, and Disconnecting the Optical Connectors).

• Clean the optical connectors (refer Section 5.1, Handling Fiber Cables, and Section 5.2, Cleaning, Connecting, and Disconnecting the Optical Connectors).

• Verify cross-connects match on the upstream and downstream nodes.

OC12 A framing problem with the OC-12 signal

• Check local receive and upstream transmit levels.

• Verify the local receive optical levels and upstream transmit optical levels. Clean the optical connectors.


• Verify good optical connections to the local and far-end OC-12 units and at the LDF panels along the link (refer to Section 5.1, Handling Fiber Cables, and Section 5.2, Cleaning, Connecting, and Disconnecting the Optical Connectors).

• Clean the optical connectors (refer to Section 5.1, Handling Fiber Cables, and Section 5.2, Cleaning, Connecting, and Disconnecting the Optical Connectors).

d6

16

4

RCV

OC-3/OC-12

DROPPEDSIGNAL

150 ADM


3.45: LOFMaintenance and Trouble ClearingFJTU-320-515-480

OVTG A framing problem on the incoming low-speed OVTG signal

• Check the OVTG link.

• Check the remote FLM 6 for OVTG unit removal or failure. Refer to Section 4, in this practice, or the Table of Contents, located in the front of this practice, to select the appropriate unit replacement procedure.

• Verify the local receive and upstream transmit optical levels. Refer to Section 5.3, Measuring Optical Power, to measure the local receive and upstream transmit levels.

• Clean the optical connectors (refer to Section 5.1, Handling Fiber Cables, and Section 5.2, Cleaning, Connecting, and Disconnecting the Optical Connectors).


T1 NA A failure within the timing source (the BITS clock)

Refer to the timing source vendor documentation for procedures to isolate and repair failure.

TRMT


A failure within a DS1 far-end NE (such as a channel bank), or the ADM is provisioned for a framed DS1 and is receiving an unframed DS1

• If the expected DS1 is framed, perform far-end site trouble analysis procedures.

• If the expected DS1 is unframed, reprovision the facility.

• Check Section 5.5, Correcting the T1 or T3 Framing Format, to verify the T1 or T3 framing.

TRMT/RCV

(LC1A-D1E2 unit installed)

T2 TRMT A failure within the DS2 far-end NE, or the ADM is provisioned for a framed DS2 and is receiving an unframed DS2

• If the expected DS2 is framed, initiate trouble analysis procedures for the far-end site.

• If the expected DS2 is unframed, reprovision the facility for FMT=UNFR.

T3 TRMT/RCV A failure within the DS3 far-end NE, or the ADM is provisioned for a framed DS3 and is receiving an unframed DS3

• If the expected DS3 is framed, initiate trouble analysis procedures for the far-end site.

• If the expected DS3 is unframed, reprovision the facility for FMT=UNFR.

• Check Section 5.5, Correcting the T1 or T3 Framing Format, to verify the T1 or T3 framing.

Table 3-43: LOF (Loss of Frame)—Alarm Event (cont’d)

AID Type Direction Probable

Cause Suggested Corrective Action

DN

61

63

TRMT

OC-3/OC-12

ADDEDSIGNAL

150 ADM


3.46: LOMMaintenance and Trouble ClearingFJTU-320-515-480

3.46 LOM

3.47 LOP

Table 3-44: LOM (Loss of Message)—Transient Condition


SYNCIN NA A loss of synchronization message is detected.

• Verify that synchronous status messaging is properly configured.

• Make sure a TCA-ENH unit is installed.

• Check the upstream ADM for optical channel unit failure or removal.

• Check the fiber link and repair or replace as required.

Table 3-45: LOP (Loss of Pointer)—Alarm Condition


EC1 TRMT/RCV An STS-1 loss of pointer on the EC-1 tributary interface

• Verify that the actual cross-connect entered for this facility is an STS-1 cross-connect.

• Verify that all upstream cross-connect levels are set to STS-1.

• Refer to the Turn-Up and Operation practice, FJTU-320-515-270, Section 6.2, Adding or Changing Time-Slot Assignments in UPSR Applications, and Section 2, for the appropriate ring turn-up procedure.

OC3 TRMT/RCV A loss of pointer in the tributary OC-3 signal




OC12 A loss of pointer in the tributary OC-12 signal




d6

16

4

RCV

OC-3/OC-12

DROPPEDSIGNAL

150 ADM


3.48: LOSMaintenance and Trouble ClearingFJTU-320-515-480

3.48 LOS

STS1 TRMT/RCV An STS-1 loss of pointer; indicates that a timing failure has occurred upstream

Verify the timing source at the upstream sites.

OVTG TRMT An OVTG loss of pointer, which indicates a timing failure at the source FLM 6

Verify the timing source at the FLM 6 site.

Table 3-46: LOS (Loss of Signal)—Alarm Event


EC1 TRMT/RCV A loss of signal on an EC-1 interface input

• Check for an STS-1 source near- or far-end removal failure.

• Verify that the coax cable is installed and connected securely.

OC3 TRMT/RCV An OC-3 loss of signal



• Verify the local receive and remote transmit optical levels.

• Verify optical connections to the local and far-endOC-3/OC-12 units and at the Lightwave Distribution Frame (LDF) panels along the link. See Section 5.1, Handling Fiber Cables, and Section 5.2, Cleaning, Connecting, and Disconnecting the Optical Connectors.

Table 3-45: LOP (Loss of Pointer)—Alarm Condition (cont’d)



3.48: LOSMaintenance and Trouble ClearingFJTU-320-515-480

OC12 An OC-12 loss of signal



• Verify the local receive and remote transmit optical levels.

• Verify good optical connections to the local and far-end OC-3 units and at the LDF panels along the link. See Section 5.1, Handling Fiber Cables, and Section 5.2, Cleaning, Connecting, and Disconnecting the Optical Connectors.

OVTG An OVTG loss of signal

• Check the remote FLM 6 for OVTG unit removal.

• Refer to Section 5.3, Measuring Optical Power, to measure the local receive and remote transmit levels.

• Clean the optical connectors. See Section 5.1, Handling Fiber Cables, and Section 5.2, Cleaning, Connecting, and Disconnecting the Optical Connectors.


T1 NA A loss of signal caused by a timing supply failure or a DS1 cable failure

• Check the DS1 clock signal cable connections.

• Refer to the timing source vendor documentation for procedures to isolate and repair the failure.

TRMT

(LC1A-D1, LC1A-D1E, or LC1A-D1E2 unit installed)

A loss of signal caused by a timing supply failure or a DS1 cable failure

Perform far-end site trouble analysis.

T3 TRMT A loss of signal caused by a DS3 NE failure on an incoming DS3

• Verify that the cable connections between the DSX-3 and NE are secure.

• Initiate trouble analysis procedures for the DSX-3 or asynchronous equipment site.

• Replace the DS3 cable.

Table 3-46: LOS (Loss of Signal)—Alarm Event (cont’d)


d6

16

4

RCV

OC-3/OC-12

DROPPEDSIGNAL

150 ADMD

N 6

16

3

TRMT

OC-3/OC-12

ADDEDSIGNAL

150 ADM


3.49: MANMaintenance and Trouble ClearingFJTU-320-515-480

3.49 MAN

3.50 MANSW

The Working/Protect entity has been switched to the Protect/Working entity, based on the fault-free operating status of the switched-to entity.

Table 3-47: MAN (Manually Caused Abnormal Condition)—Alarm Event


COM NA The system is in an operator-caused abnormal condition (forced or lockin protection switching, or loopback).

Corrective action is not necessarily required. The manual condition will automatically clear when the operator removes the forced switch, loopback, or lockin condition.

Table 3-48: MANSW (Manual Switch of Working/Protect to Protect/Working)—Standing Condition


COM NA OPR-PROTNSW-COM: TID:AIDs:CTAG::MAN; has been executed for testing or maintenance reasons.

• Verify that the cause of operating the forced switch no longer exists or that authorization to release the manual switch is secured.

• Execute the RLS-PROTNSW-COM command.

EQPT NA OPR-PROTNSW-EQPT: TID:AIDs:CTAG::MAN; has been executed for testing or maintenance reasons.


• Execute the RLS-PROTNSW-EQPT command.

OC-3 NA OPR-PROTNSW-OC3: TID:AIDs:CTAG::MAN; has been executed for testing or maintenance reasons.


• Execute the RLS-PROTNSW-OC3 command.

OVTG NA OPR-PROTNSW-OVTG: TID:AIDs:CTAG::MAN; has been executed for testing or maintenance reasons.


• Execute the RLS-PROTNSW-OVTG command.


3.51: MISMOUNTMaintenance and Trouble ClearingFJTU-320-515-480

3.51 MISMOUNT

STS1 NA OPR-PROTNSW-STS1: TID:AIDs:CTAG::MAN; has been executed for testing or maintenance reasons.


• Execute the RLS-PROTNSW-STS1 command.

SYNCIN TMG, TMOUTP, TMGPUTS

OPR-SYNCNSW :TID:AID:CTAG::MAN; has been executed for testing or maintenance reasons.


• Execute the RLS-SYNCSW command.

VT1 NA OPR-PROTNSW-VT1: TID:AIDs:CTAG::MAN; has been executed for testing or maintenance reasons.


• Execute the RLS-PROTNSW-VT1 command.

Table 3-49: MISMOUNT (Remote Alarm Indication)—Standing Condition


EQPT NA The unit in the slot specified is mismounted. The plug-in unit does not match the provisioning for the slot.

• Verify that the correct card type is installed.

• Check the slot provisioning and correct if necessary.

Table 3-48: MANSW (Manual Switch of Working/Protect to Protect/Working)—Standing Condition (cont’d)



3.52: MSGCHGMaintenance and Trouble ClearingFJTU-320-515-480

3.52 MSGCHG

These messages indicate a change in the quality level of the synchronous status message:

• MSGCHGRES-PRS/-STU/-ST2/-ST3/-SIC/-ST4/-DUS/-FAIL/-NA

• MSGCHGPRS-STU/-ST2/-ST3/-SIC/-ST4/-DUS/-RES/-FAIL/-NA

• MSGCHGSTU-PRS/-ST3/-ST3/-SIC/-ST4/-DUS/-RES/-FAIL/-NA

• MSGCHGST2-PRS/-STU/-ST3/-SIC/-ST4/-DUS/-RES/-FAIL/-NA

• MSGCHGST3-PRS/-STU/-ST2/-SIC/-ST4/-DUS/-RES/-FAIL/-NA

• MSGCHGSIC-PRS/-STU/-ST2/-ST3/-ST4/-DUS/-RES/-FAIL/-NA

• MSGCHGST4-PRS/-STU/-ST2/-ST3/-SIC/-DUS/-RES/-FAIL/-NA

• MSGCHGDUS-PRS/-STU/-ST2/-ST3/-SIC/-ST4/-RES/-FAIL/-NA

• MSGCHGFAIL-PRS/-STU/-ST2/-ST3/-SIC/-ST4/-DUS/-RES/-NA

• MSGCHGNA-PRS/-STU/-ST2/-ST3/-SIC/-ST4/-DUS/-RES/-FAIL

3.53 PDI-n

Table 3-50: MSGCHG (Synchronization Status Message Change)—Transient Condition


SYNCIN NA Synchronization message degrade or upgrade is detected.

• Replace the TCA-ENH unit.


• Check the fiber-optic path and perform trouble analysis as needed.

Table 3-51: PDI-n (Payload Defect Indication code n received [n = 1~27, ALL])—Alarm Condition


STS1 RCV Five consecutive identical PDI codes are received within 5 ms.

Provision the NE, by selecting PDISD = Y, so that path switching is accomplished.


3.54: PINGTIMEOUTMaintenance and Trouble ClearingFJTU-320-515-480

3.54 PINGTIMEOUT

3.55 PLM

Table 3-52: PINGTIMEOUT (Ping Request Timed Out)—Transient Condition


COM NA No IP connection to destination node or improper IP provisioning

Verify LCN physical connection from source to destination node. Verify IP provisioning at destination node.

Table 3-53: PLM (Payload Label Mismatch)—Alarm Event


STS1

VT

Incoming payload label does not match expected payload label.

• The provisioning of the near-end expected cross-connects does not agree with the provisioning of far-end payload label. Correct the provisioning that is in error. Do not change expected trace based only on the basis of the incoming trace value. This would defeat the purpose of this feature.

• If a cross-connect error is suspected in a ring configuration, manually switch the channel to the other direction. If the PLM clears, check the cross-connects in the suspect direction.

d6

16

4

RCV

OC-3/OC-12

DROPPEDSIGNAL

150 ADM


3.56: RAIMaintenance and Trouble ClearingFJTU-320-515-480

3.56 RAI

3.57 RFI

This condition type indicates a remote failure. This alarm has replaced the FERF and YEL alarms.

Table 3-54: RAI (Remote Alarm Indication)—Alarm Event


T2 The tributary equipment has detected a defective incoming DS2 (AIS, LOF, or LOS) and toggles the x-bit on its outgoing DS2. The toggled x-bit is detected by the local NE, which triggers the RAI alarm.

• Verify that the connections from the NE to the tributary equipment are mechanically secure.

• Check the outgoing DS2 signal from the NE to the tributary equipment for the presence of AIS or framing problems.

• Check for AIS, LOS, and LOF at the NE where this DS2 originated.

T3 The tributary equipment has detected a defective incoming DS3 (AIS, LOF, or LOS) and toggles the x-bit on its outgoing DS3. The toggled x-bit is detected by the local NE, which triggers the RAI alarm.

The alarm may also be generated if the ED-T3, XPOL keyword, is not provisioned.

• Verify that the connections from the NE to the tributary equipment are mechanically secure.

• Check the outgoing DS3 signal from the NE to the tributary equipment for the presence of AIS or framing problems.

• Check for AIS, LOS, and LOF at the NE where this DS3 originated.

• Verify that the ED-T3, XPOL keyword, is properly provisioned.

Table 3-55: RFI (Remote Failure Indication)—Alarm Event


EC1 RFI detected on an incoming tributary EC-1 signal. A problem exists on the EC-1 signal that the local ADM is sending toward the FLM 6 equipment.

• Verify that the outgoing EC-1 coax cable is installed and connected securely. Perform trouble analysis procedures as necessary.

• Switch the traffic to the standby MC1A-STS1 unit. If the RFI clears, replace the suspect unit. Switch the new unit on line and make sure the RFI does not reappear.

• Check the incoming tributary EC-1 interface unit.

DN

616

3

TRMT

OC-3/OC-12

ADDEDSIGNAL

150 ADM

DN

616

3

TRMT

OC-3/OC-12

ADDEDSIGNAL

150 ADM

DN

61

63

TRMT

OC-3/OC-12

ADDEDSIGNAL

150 ADM


3.57: RFIMaintenance and Trouble ClearingFJTU-320-515-480

OC3 TRMT/RCV • TRMT: RFI detected on the signal received from the tributary ADM. The local OC-3 transmit unit may be sending a bad optical signal to the FLM 6.

• RCV: RFI detected on the signal received from the far end. The local OC-3 transmit unit may be sending a bad signal to the far end.

• Check the output of the local optical transmit unit for level degradation or dirty optical connectors. Refer to Section 5.3, Measuring Optical Power, to measure the local receive and upstream transmit levels. In this practice, refer to Section 5.1, Handling Fiber Cables, and Section 5.2, Cleaning, Connecting, and Disconnecting the Optical Connectors, to clean the optical connectors.

• Verify that the outgoing fiber link for OC-3 is installed and connected securely.

• Retrieve the alarms from the tributary FLM 6 (TRMT) or the far end (RCV) to determine the faults detected there. The receive unit at the FLM 6 or at the far end could have failed.

OC12 RFI detected on the signal received from the far end. The local OC-12 transmit unit may be sending a bad signal to the far end.

• Verify that the outgoing fiber link for OC-12 is installed and connected securely.

• Retrieve the alarms from the tributary FLM 6 (TRMT) or the far end (RCV) to determine the faults detected there. The receive unit at the FLM 6 or at the far end could have failed.

OVTG TRMT RFI detected on the OVTG signal received from the tributary ADM. The local transmit unit may be sending a bad OVTG signal to the tributary FLM 6.

• Check the output of the local optical transmit unit for level degradation or dirty optical connectors. Refer to Section 5.3, Measuring Optical Power, to measure the local receive and upstream transmit levels. In this practice, refer to Section 5.1, Handling Fiber Cables, and Section 5.2, Cleaning, Connecting, and Disconnecting the Optical Connectors, to clean the optical connectors.


• Retrieve the alarms from the tributary FLM 6 to determine the faults detected there. The receive unit at the tributary FLM 6 could have failed.

Table 3-55: RFI (Remote Failure Indication)—Alarm Event (cont’d)


d6

16

4

RCV

OC-3/OC-12

DROPPEDSIGNAL

150 ADM


3.58: RFI-CONMaintenance and Trouble ClearingFJTU-320-515-480

3.58 RFI-CON

3.59 RFI-PLD

3.60 RFI-SRV

Table 3-56: RFI-CON (Remote Failure Indicator-Connectivity)—Alarm Event


STS1 RFI-connectivity defect received

Verify that connections are secure.

Table 3-57: RFI-PLD (Remote Failure Indicator-Payload Defect)—Alarm Event


STS1 RFI-payload defect received Retrieve alarms and correct.

Table 3-58: RFI-SRV (Remote Failure Indicator-Server)—Alarm Event


STS1

VT1

RFI-server defect received Retrieve alarms and correct.

d6

16

4RCV

OC-3/OC-12

DROPPEDSIGNAL

150 ADMd

61

64

RCV

OC-3/OC-12

DROPPEDSIGNAL

150 ADM

d6

16

4

RCV

OC-3/OC-12

DROPPEDSIGNAL

150 ADM


3.61: RMVDMaintenance and Trouble ClearingFJTU-320-515-480

3.61 RMVD

3.62 SVM

Table 3-59: RMVD (Plug-In Unit Removed)—Alarm Event


EQPT NA The plug-in unit is not properly seated, or it is removed.

• Reseat the unit or replace it.

• If a plug-in unit is not required in the slot generating the alarm, the alarm can be cleared by deleting the equipment (slot).

Table 3-60: SVM (Software Version Mismatch)—Standing Condition


EQPT NA NE is equipped with a combination of different software files or the software files are unreadable.

Examples:

• One or more file versions do not match the ones listed in the configuration file.

• Software versions in one or more CPU(s) are unreadable.

Plug-in units that contain mismatched or unreadable software files display a flashing red FAIL LED when SVM occurs. The NE generates an alarm to the office alarm interfaces, OS/DCC, and craft interfaces. Correct for the SVM condition is available in the following retrieve commands:

• CPU in SVM condition—RTRV-ALM-ALL-RTRV-COND-ALL

• Expected file version—READ-CONFIG

• Observed file version—RTRV-FILE-NVM

Refer to FJTU-320-515-270, Section 7, Reports, for evaluating compatibility in terms of SVM and system release numbers for software download systems.

When the SVM condition is corrected, the NE deactivates the flashing red LED and office alarms and generates a clear message to the OS/DCC/craft interfaces.


3.63: SYNCDMaintenance and Trouble ClearingFJTU-320-515-480

3.63 SYNCD

3.64 SYSRES

3.65 T-FE

Table 3-61: SYNCD (Synchronization Message Degradation)—Alarm Event


SYNCIN NA Synchronization message degradation is detected.

• Replace the TCA-ENH unit.



Table 3-62: SYSRES (System Restart)—Transient Condition


COM NA The system was restarted. Monitor system to determine reason for restart not initiated by technician.

Table 3-63: T-FE (Threshold Violation)—Transient Condition


OVTG NA A threshold violation occurred on the far-end NE.

Retrieve PM from far-end NE to determine cause of errors.


3.66: T-LBCNMaintenance and Trouble ClearingFJTU-320-515-480

3.66 T-LBCN

T-LBCN is reported when transmitter laser bias current exceeds the threshold level.

3.67 T-PSC

PSC is the count of the number of protection switches for each OC-3 line.

Table 3-64: T-LBCN (Threshold Violation for Normalized Laser Bias Current)—Transient Condition


EQPT RCV • Laser approaching end of useful life

• Faulty optical transmitter unit

• Improperly set threshold

• Replace the optical transmitter unit.

• Verify the proper threshold levels with local standards. The allowable threshold values are 0.5 to 2.0. Factory default = 1.5.

• A threshold set too low causes a premature indication that a laser is nearing the end of its useful life.

Table 3-65: T-PSC (Threshold Violation for Protection Switch Count)—Transient Condition


OC3

OVTG

NA • Intermittent digital errors

• Loss of DS3, EC-1, or optical signal

• Faulty MC1A plug-in unit

• Faulty optical transmitter unit, or optical receiver unit

• Improperly set threshold

• The FLM 150 ADM provides a lockin function to prevent successive switching of the unit and line caused by intermittent digital errors. Lockin occurs automatically if the unit switches four times in a 15-minute period. It will remain in that state for 24 hours or until the lockin function is disabled through provisioning. Not coincidentally, the default threshold for 15-minute time periods is four switches. If all four switches occur in the same quarter-hour PM period, a threshold crossing will accompany the lockin.

• See LOS.

• Replace the faulty MC1A or optical unit as required.

• See also APSB.

• Refer to TL1 Commands practice FJTU-320-515-274, Section 5, Performance Monitoring Parameters, for the minimum, maximum, and default parameters.


3.68: TARPECHOMaintenance and Trouble ClearingFJTU-320-515-480

3.68 TARPECHO

TID and network address collection time period completed.

3.69 TARPERR

A TID address resolution protocol (TARP) error or a NET unreachable error.

a TID expected behavior = 7 to 20 ASCII characters—Deviation = TID is none or 40 hex characters.NET expected behavior = 40 hex characters—Deviation = NET address is none or 7 to 20 ASCII characters.

a TID expected behavior = 7 to 20 ASCII characters—Deviation = TID is none.NET expected behavior = 40 Hex characters—Deviation = NET address is none.

Table 3-66: TARPECHO (Tarp Echo Function)—Transient Condition

AID Type Direction Probable Causea Suggested Corrective Action

COM NA OPR-TEF response None required

Table 3-67: TARPERR (TARP Error)—Transient Condition

AID Type Direction Probable Causea Suggested Corrective Action

COM NA • Unknown NET used during CPY-FILE

• Unknown NET or TID used during OPR-TEF

• Unknown error TID when any command is sent

• Make sure the TID is correct.

• If the TID is correct, increase timer values RT1 and RT2 for Type 1 and Type 2 response time-outs. When left at default values, the TARPEER will be returned approximately 90 seconds after the command is initiated.


3.70: Threshold Violations-LineMaintenance and Trouble ClearingFJTU-320-515-480

3.70 Threshold Violations-Line

The following are the definitions for the line threshold violations:

• CVL: Coding Violation count–Line

• ESL: Errored Second count–Line

• SEFSL: Severely Errored Framing Second count–Line

• SESL: Severely Errored Second count–Line

• UASL: Unavailable Second count–Line

Table 3-68: Threshold Violations-Line (T-CVL, T-ESL, T-SESL, T-UASL)—Transient Conditions

AID Type and MONTYPE Direction Probable Cause Suggested Corrective Action

T1

CVL

ESL

SESL

(clock and LC1A-D1E or LC1A-D1E2 unit installed)

NA Faulty or missing external clock input signal

• Check for problems with external timing source.

• Check for bad clock-input cable.

T3

CVL

ESL

SESL

OC3 and EC1

CVL

ESL

SESL

UASL

OVTG

ESL

SESL

UASL

CVL

SEFSL

OC12

UASL

TRMT • The signal input to the shelf contains an AIS.

• Faulty input cable.

• Faulty signal from subscriber.

• Faulty MC1A plug-in unit.

• Improperly set threshold.

• Inspect and clear alarms from the upstream asynchronous equipment for an AIS indication.

• Verify the proper cable connection between the FLM 150 ADM and the DSX.

• Test subscriber input signal parameters.

• Replace the suspect MC1A unit if the PM register count stops incrementing when the standby unit is on line.

• Verify the proper threshold levels through local standards. Refer to TL1 Commands practice FJTU-320-515-274, Section 5, Performance Monitoring Parameters, for the minimum, maximum, and default parameters.


3.70: Threshold Violations-LineMaintenance and Trouble ClearingFJTU-320-515-480

OC3

CVL

ESL

SESL

UASL

RCV/TRMT

• Incoming interface signal at far end has a problem.

• High-speed unit problems at intermediate sites.

• Optical path problems between far end and near end.


• Check the far end for incoming (TRMT) T3 alarms or threshold crossings or PM register counts (see above).

• Check for alarm conditions at the far end and at all intermediate sites.

• High-speed unit and fiber problems are not the likely cause if only one channel is reporting threshold crossings.


OC12

CVL

ESL

SESL

RCV • Incoming interface signal at far end has a problem.








OC12

UASL

TRMT • Incoming interface signal at far end has a problem.








Table 3-68: Threshold Violations-Line (T-CVL, T-ESL, T-SESL, T-UASL)—Transient Conditions (cont’d)

AID Type and MONTYPE Direction Probable Cause Suggested Corrective Action


3.71: Threshold Violations–PathMaintenance and Trouble ClearingFJTU-320-515-480

3.71 Threshold Violations–Path• CVP: Coding Violation count–Path

• ESP: Errored Second count–Path

• SESP: Severely Errored Second count–Path

• UASP: Unavailable Second count–Path

• SASP: Each SASP register stores the count of 1-second intervals containing one or more SEF defects or one or more AIS defects for a specific DS3 path

Table 3-69: Threshold Violations-Path (T-CVP, T-ESP, T-SESP, T-UASP, T-SASP)—Transient Conditions

AID TypeMONTYPE Direction Probable Cause Suggested Corrective Action

T3

CVP

ESP

SESP

UASP

SASP

T3U

CVP

ESP

SESP

UASP

SASP

T1

SASP

TRMT • The signal input to the shelf contains an AIS.

• Faulty input cable.

• Faulty signal from subscriber.



• Inspect and clear alarms from the upstream asynchronous equipment for an AIS indication.

• Verify proper cable connection between FLM 150 ADM and DSX.

• Test subscriber input signal parameters.

• Replace the suspect MC1A unit if the PM register count stops incrementing when the other (standby) unit is on line.

• Verify proper threshold levels with local standards. Refer to TL1 Commands practice FJTU-320-515-274, Section 5, Performance Monitoring Parameters, for the minimum, maximum, and default parameters.


3.71: Threshold Violations–PathMaintenance and Trouble ClearingFJTU-320-515-480

T3

CVP

ESP

SESP

UASP

SASP

STS1, T1, and VT1

CVP

ESP

SESP

UASP

SASP

(clock and LC1A-D1E or LC1A--D1E2 installed)

RCV • Incoming interface signal at far end has a problem.







• Replace the suspect MC1A unit if the PM register count stops incrementing when the other (standby) unit is on line.

Table 3-69: Threshold Violations-Path (T-CVP, T-ESP, T-SESP, T-UASP, T-SASP)—Transient Conditions (cont’d)



3.72: Threshold Violations-SectionMaintenance and Trouble ClearingFJTU-320-515-480

3.72 Threshold Violations-Section

The following are the definitions for the section threshold violations:

• CVS: Coding Violation count–Section

• ESS: Errored Second count–Section

• SESS: Severely Errored Second count–Section

• SEFSS: Severely Errored Framing Second count–Section

Table 3-70: Threshold Violations-Section (T-CVS, T-ESS, T-SESS, T-SEFSS)—Transient Conditions


OC3

CVS

ESS

SESS

SEFSS

TRMT • The optical tributary input to the shelf contains an AIS.


• Faulty MC1A optical plug-in unit.


• Inspect and clear alarms from the upstream tributary equipment for an AIS indication.

• Check and clean all fiber-optic connectors in the optic path between the tributary equipment and the FLM 150 ADM shelf.

• Check optical output level at tributary transmitter.

• Check optical receive level at input to FLM 150 ADM shelf.

• Replace the suspect MC1A unit if the PM register count stops incrementing when the other (standby) optical unit is on line.


OC3 and OC12

CVS

ESS

SESS

SEFSS

RCV • The optical input to the shelf contains an AIS.

• Optical path problems between upstream node and near end.

• Faulty HC6A optical plug-in unit.


• Check for alarm conditions at the upstream node.

• Check optical output level at upstream transmitter.

• Check the optical receive level at input to local FLM 150 ADM shelf.

• Replace the suspect HC1A unit if the PM register count stops incrementing when the other (standby) optical unit is on line.



3.73: TMGOUTPSWMaintenance and Trouble ClearingFJTU-320-515-480

3.73 TMGOUTPSW

TMGOUTPSWPRS/STU/ST2/ST3/SIC/ST4/RES/FAIL/NA

3.74 TMGOUTSSW

TMGOUTSSWPRS/STU/ST2/ST3/SIC/ST4/RES/FAIL/NA

Table 3-71: TMGOUPSW (Primary DS1 Timing Reference Output Switch)—Transient Condition


SYNCIN NA A derived DS1 primary timing reference switch is detected.

• The TCA-ENH unit is defective.



Table 3-72: TMGOUTSSW (Secondary DS1 Timing Reference Output Switch)—Transient Condition


SYNCIN NA A derived DS1 secondary timing reference switch is detected.



• Check the fiber optic-path and perform trouble analysis as needed.


3.75: TMGSWMaintenance and Trouble ClearingFJTU-320-515-480

3.75 TMGSW

These messages indicate a switch in the timing reference:

TMGSW/PRS/STU/ST2/ST3/SIC/ST4/RES/FAIL/NA

3.76 TRCM

Table 3-73: TMGSW (Timing Reference Switch)—Transient Condition


SYNCIN NA A system timing reference is detected.




Table 3-74: TRCM (Path Trace Mismatch)—Transient Condition


STS1 TRMT/RCV Incoming path trace label does not match expected path trace label.

• The provisioning of the near-end expected path trace does not agree with the provisioning of the far-end path trace. Correct the provisioning that is in error. Do not change expected trace based only on the basis of the incoming trace value. This would defeat the purpose of this feature.

• If the path trace value provisioned at the far end is identical to the provisioned expected trace at the near end, a mismatch indicates a cross-connect error somewhere in the path.

• If a cross-connect error is suspected in a ring configuration, manually switch the channel to the other direction. If the TRCM clears, check the cross-connects in the suspect direction.


3.77: UNEQMaintenance and Trouble ClearingFJTU-320-515-480

3.77 UNEQ

3.78 WKSWBK

Condition code that reports the switching from the Protect unit back to the Working unit in the FLM 150 ADM.

Table 3-75: UNEQ (Unequipped Code Signal Label Received)—Alarm Event


STS1 TRMT/RCV This alarm occurs in path switched rings only. It is detected as the signal is dropped:

• An STS-1 cross-connect has been deleted either at the local node or at an upstream node. A deleted cross-connect anywhere along the SONET path could cause this alarm.

• The upstream tributary facility where the signal is added to the ring has been deleted.

• Retrieve the cross-connects along the SONET path for this circuit. Enter any cross-connect that is missing. The alarm will clear when all needed cross-connects have been entered.

• If no circuit is to be carried on the facility reporting the alarm, the alarm can be cleared by setting PSWOPT = N for the STS drop reporting the alarm.

• Retrieve the facility state where the circuit is added to the ring. Enter the facility if it is out of service (OOS).

VT1 RCV

Table 3-76: WKSWBK (Working Facility/Equipment Switched Back to Working)—Transient Condition


EQPT

OC3

OVTG

STS1

VT1

NA • The restoration of signal to Working unit after an LOS or degraded condition

• Working unit plugged in after it had been removed

• Faulty Working unit repaired

No action required. The FLM 150 ADM has two modes of protective switching, revertive and nonrevertive. In nonrevertive switching, switching is performed manually. In revertive switching, switching will occur after normal conditions have been restored to the Working unit.


3.79: WKSWPRMaintenance and Trouble ClearingFJTU-320-515-480

3.79 WKSWPR

Condition code that reports the switching from the Working unit to the Protect unit in the FLM 150 ADM.

Table 3-77: WKSWPR (Working Facility/Equipment Switched to Protection)—Transient Condition


EQPT

OC3

OVTG

STS1

VT1

NA • LOS or degraded signal input of the Working unit

• Faulty Working unit

• Working unit removed from chassis

• Has Working unit been removed? If not, signal analysis should be performed to verify condition of circuit.

• If signal is present and not degraded, replace faulty Working unit.

• Replace unit.



4.1: Overview

4 Replacing Units

4.1 Overview

This section list s the procedures required to replace the FLM 150 ADM plug-in units (with the exception of units and cards used in FASTLANE applications).

For information relating to replacing FASTLANE ™units and cards, refer to the FASTLANE I practice, FJTU-320-515-110, and FASTLANE II practice, FJTU-320-515-111.

4.2 Replacing the Power (PW1A) Unit

4.2.1 Overview

This procedure lists the steps required to replace a failed PW1A Power Unit.

Refer to Section 2, Plug-In Unit Front-Panel Devices, in this practice for descriptions of LEDs associated with each plug-in unit, and other front-panel devices.

WARNING:During unit replacement, seat all plug-in units with a slow, but firm motion. Do not push them quickly into the slot. Many critical units have longer power connector pins to minimize power surges during unit replacement. A slow insertion method will ensure that plug-in units are not damaged.

WARNING:Wear an electrostatic discharge wrist strap with a minimum resistance of 1 megohm when handling FLM units to prevent damage to the units. Before using the wrist strap, check for opens, shorts and minimum resistance value. If the strap does not pass these checks, do not use it.


4.2: Replacing the Power (PW1A) UnitMaintenance and Trouble ClearingFJTU-320-515-480

4.2.2 Procedure

Step 1 Turn off the power switch.

Note: The PW1A unit has no hardware option settings.

Step 2 If you have a known-good PW1A unit, use it to replace the original unit, or locate another unit and inspect it for damage, debris, and foreign objects. Install the unit. Refer to Figure 4-1 and turn on the power switch. Is the PWR LED green?

Step 3 Check the fuse on the Fuse and Alarm Panel. Is the fuse good?

Step 4 Replace the fuse on the Fuse and Alarm Panel. Is the PWR LED on the PW1A unit green? Does the power switch remain in the ON position?

Step 5 Connect the DMM (digital multimeter) leads to the MAIN and G test jacks on the unit. Is the MAIN reading between –42 and –56 V dc?

If Yes: If No:

Go to Step 5. • If the PWR LED is not lit, go to Step 3.

• If the PWR LED is red, call the Fujitsu Technical Assistance Center at 1-800-USE-FTAC (1-800-873-3822) for assistance.

If Yes: If No:

Go to Step 2, unit is bad. Go to Step 4.

If Yes: If Any No:

Go to Step 5. Call the Fujitsu Technical Assistance Center at 1-800-USE-FTAC (1-800-873-3822) for assistance.

If Yes: If No:

Go to Step 8. Go to Step 6.



Step 6 Repeat trouble analysis procedures (See Section 2, Plug-In Unit Front-Panel Devices). Is the PWR LED green?

Step 7 Connect the DMM leads to the MAIN and G test jacks on the unit. Is the MAIN reading between –42 and –56 V dc?

Step 8 Connect the DMM leads to the +5.4V and SG test jacks and to the –5.6V and SG test jacks. Is the reading for the +5.4V test jack between +5.02 and +6.21 V and for the –5.6V test jack between –5.21 and –6.44 V?

Note: The Hardware Data Record form is provided in Appendix A of the Plug-In Unit Installation practice, FJTU-320-515-220.


If Yes: If No:


If Yes: If No:


If Yes: If No:

Complete your fault-reporting documentation.

Call the Fujitsu Technical Assistance Center at 1-800-USE-FTAC (1-800-873-3822) for assistance.



PWR

FC9612PW11

+5.4V-5.6V

SG

MAIN

G

PW1A

ON

ON

OFF

PW

d5

03

1.2

Figure 4-1: PW1A Unit Front Panel


4.3: Replacing the Microprocessor (MP1A) UnitMaintenance and Trouble ClearingFJTU-320-515-480

4.3 Replacing the Microprocessor (MP1A) Unit

4.3.1 Overview

This procedure lists the steps required to replace a failed MP1A Microprocessor unit.

Refer to Section 2, Plug-In Unit Front-Panel Devices, in this practice for descriptions of LEDs associated with each plug-in unit and other front-panel devices.

Refer to the Application Engineering practice, FJTU-320-515-120, Appendix C, Hardware Options, for descriptions of plug-in unit hardware option settings.

Refer to the Unit Descriptions practice, FJTU-320-515-000, for hardware option default settings.





4.3.2 Procedure

Step 1 If you have a known-good MP1A unit, use it to replace the original unit or locate another unit and inspect it for damage, debris, and foreign objects. Verify that you have the correct type of MP1A unit for your application:

• MP1A supports DS1 tributary interfaces. Refer to Figure 4-2.

• MP1A-V2 supports all tributaries. Refer to Figure 4-3.

• MP1A-ADL supports software download, all tributaries, OC-12, and enhanced TSA units. Refer to Figure 4-3.

• MP1A-V3 supports all tributaries, OC-12, and enhanced TSA units. Refer to Figure 4-4.

• MP1A-R11 supports all tributaries, OC-12, and enhanced TSA units. Refer to Figure 4-4.

Step 2 Set the option switch on the new unit to the same position used on the removed MP1A unit.

Step 3 Replace the original MP1A unit. Is the FAIL LED off?

Note: Wait 5 minutes before proceeding. This allows the database memory to upload from the SV1A unit to the MP1A unit.

Step 4 Press the CPU RESET button. Wait for system reset. Is the alarm cleared?



If Yes: If No:

You have completed this procedure. Go to Step 4.

If Yes: If No:





MP1A

FC9612MPB1

FAIL

91234

0

567 8

9123

4

0

5 6

78

E.N. (1-9)

d2

42

7.5

EQPT NO.

FESEL

CPURESET

Figure 4-2: MP1A Unit Front Panel and Hardware Option Locations



d6

29

9.1

EQPT NO.

(1-9)

91

2 3 4

0

5678

91

2 3 4

0

5678

FC9612MP21

MP1A-V2

FAIL

FESEL

EQPT. NO.

CPURESET

Figure 4-3: MP1A-V2/-ADL Unit Front Panel and Hardware Option Locations



MP1A-V3

FC9612MP31

d5

64

6.2

FAIL

9123

4

0

5 6

78

91234

0

5678

E.N. (1–9)

EQPT NO.

FESEL

CPURESET

Figure 4-4: MP1A-V3/-R11 Unit Front Panel and Hardware Option Locations


4.4: Replacing the Time-Slot Assignment (TS1A)Unit


4.4 Replacing the Time-Slot Assignment (TS1A) Unit

4.4.1 Overview

This procedure lists the steps required to replace a failed TS1A Time-Slot Assignment unit.







4.4.2 Procedure

Step 1 If you have a known-good unit, use it to replace the original unit, or locate another unit and inspect it for damage, debris, and foreign objects. Verify that you have the correct type of TS1A unit for your application:

• TSIA-BSC (Figure 4-5)

• TS1A-ENH (Figure 4-6)

• TS1A-ENH2 (Figure 4-7)

Note: The TS1A-ENH unit requires the use of MP1A-V3/-ADL and SV1A-TL4/-TDL1 cards. The TS1A-ENH2 requires the use of the MP1A-ADL and SV1A-TDL1 cards.

Note: The TS1A unit has no hardware option settings.

Step 2 Replace the original unit. Is the LINE LED off and the FAIL/SVCE LED green?

Step 3 Check the signal of the MC1A and TS1A units at the remote terminal. Are the FAIL/SVCE LEDs green?

Step 4 At the remote terminal, replace the MC1A or the TS1A with a known-good unit, if you have one, or with another unit. Is the LINE LED on the TS1A unit off and the FAIL/SVCE LED green?

If Yes: If No:



Go to Step 3.

If Yes: If No:


If Yes: If No:



Go to Step 5.




Step 5 Repeat trouble analysis procedures (refer to Section 3, Responding to Alarms and Conditions). Is the LINE LED off and the FAIL/SVCE LED green on the local TSA unit?



If Yes: If No:

Complete your fault-reporting documentation. Call the Fujitsu Technical Assistance Center at 1-800-USE-FTAC (1-800-873-3822) for assistance.

TS1A

FC9612TSB1

d231

1.2

FAILSVCE

LINE

Figure 4-5: TS1A-BSC Unit Front Panel




TS1A-ENH

FC9612TSE1

d565

6.2

FAIL/SVCE

LINE

Figure 4-6: TS1A-ENH Unit Front Panel

TS1A-ENH2

FC9612TSE2

d710

3

FAIL/SVCE

LINE

Figure 4-7: TS1A-ENH2 Unit Front Panel


4.5: Replacing the Alarm (AW1A) UnitsMaintenance and Trouble ClearingFJTU-320-515-480

4.5 Replacing the Alarm (AW1A) Units

4.5.1 Overview

This procedure lists the steps required to replace a failed AW1A Alarm and Orderwire unit.




Note: The strap options should all be set the same for each type of alarm (i.e., all MJ or all CR).





4.5.2 Procedure

Step 1 If you have a known-good unit, use it to replace the failed AW1A unit, or locate another unit and inspect it for damage, debris, and foreign objects. Verify that you have the correct type of AW1A unit for your application:

• AWIA-BSC (Figure 4-8)

• AW1A-ENH (Figure 4-9)

Step 2 Set the option switches to the same positions used on the removed unit.

Step 3 Install the new unit. Does the original problem clear?

Step 4 If the alarm does not clear, repeat trouble analysis procedures (see Section 3, Responding to Alarms and Conditions). Does the original problem clear?



If Yes: If No:



Go to Step 4.

If Yes: If No:





AW1A-BSC

FC9612AWB1

ACO

LAMPTEST

CR

MJ

MN

ABN

NE ACT

FE ACT

PWR FAIL ALM

VMJ VCR

AMJ ACR

LEDMJ

LEDCR

d242

4.2

Figure 4-8: AW1A-BSC Unit Front Panel and Hardware Option Locations



CR

AW1A-ENH

MJ

MN

PMN

ABN

ACO

LAMPTEST

CALL

PH

ON

E

FC9612AWE1

FE ACT

NE ACT

VMJ

AMJ

LEDMJ

VCR

ACR

LEDCR

PWR FAIL ALM

DIS EN

CMN

DN

36

89

.1

Figure 4-9: AW1A-ENH Unit Front Panel and Hardware Option Locations


4.6: Replacing the Supervisory (SV1A) UnitMaintenance and Trouble ClearingFJTU-320-515-480

4.6 Replacing the Supervisory (SV1A) Unit

4.6.1 Overview

This procedure lists the steps required to replace a failed SV1A Supervisory unit.








4.6.2 Procedure

Step 1 If you have a known-good unit, use it to replace the SV1A unit, or locate another unit and inspect it for damage, debris, and foreign objects. Verify that you have the correct type of SV1A unit for your application:

• SV1A-TL1 with the MP1A supports TL1/FLEXR® interfaces and low-speed DS1 facility types only. Refer to Figure 4-10.

• SV1A-TL2 with the MP1A-V2 supports TL1/FLEXR interfaces and all middle-speed and low-speed options. Refer to Figure 4-11.

• SV1A-TL3 with the MP1A-V2 (Issue 06) supports TL1, FLEXR, and Menu Mode interfaces and all middle-speed and low-speed options. Refer to Figure 4-11.

• SV1A-TL4 with MP1A-V3 supports TL1/FLEXR, and all middle-speed and low-speed options, as well as supporting the OC-12 high-speed interface and the TS1A-ENH unit. Refer to Figure 4-11.

• SV1A-R11 with MP1A-R11 supports TL1/FLEXR, and all middle-speed and low-speed options, as well as supporting the OC-12 high-speed interface and the TS1A-ENH unit. Refer to Figure 4-11.

• SV1A-TDL1 supports all middle-speed, low-speed, and high-speed options and the TS1A-ENH/-ENH2, EC1A-DL1/-DL2, and transmux units. Refer to Figure 4-12.

• SV1A-TB with the MP1A-V2 supports TL1, FLEXR, and telemetry byte-oriented serial (TBOS) protocol interfaces and all middle-speed and low-speed options. Refer to Figure 4-13.

Step 2 Set the option switches to the same positions as those used on the removed unit.

Note: The SV1A-TB does not have option switches.

Step 3 Replace the original unit. Is the FAIL LED on the SV1A unit off?

If Yes: If No:



Go to Step 4.



Step 4 If the FAIL LED is still on, repeat trouble analysis procedures (see Section 3, Responding to Alarms and Conditions). Does the FAIL LED go off?



If Yes: If No:





SV1A-TL1

FC9612SVL1

DN

24

28

.1

FAIL

ACS

TERM

LINE

OS

SB

-B

Figure 4-10: SV1A-TL1 Unit Front Panel and Hardware Option Locations



SV1A-TL2

FC9612SVL2

DN

41

49

.1

FAIL

ACS

TERM

LINE

SELECTOSS CLOCK

B-B

OP

EN

12

OSS

Figure 4-11: SV1A-TL2/-TL3/-TL4/- R11 Unit Front Panel and Hardware Option Locations



B-BOSS

-OP

EN

-

1

2

ON

OF

F

FC9612SVD1

SV1A-TDL1

d6

97

2

TERM

FAIL

ACS

B-B

LINE

OSS

-OP

EN

-

SWDL

1

2

ON

OF

F

Figure 4-12: SV1A-TDL1 Unit Front Panel and Hardware Option Locations



SV1A-TB

FC9612SVB1

DN

41

48

.1

FAIL

ACS

TERM

LINE

Figure 4-13: SV1A-TB Unit Front Panel


4.7: Replacing the Middle-Speed Mux/Demux/Transmux (MC1A) Unit


4.7 Replacing the Middle-Speed Mux/Demux/Transmux (MC1A) Unit

4.7.1 Overview

This procedure lists the steps required to replace a failed MC1A Middle-Speed Channel Mux/Demux/Transmux unit.









4.7.2 Procedure

Step 1 If you have a known-good MC1A unit, use it to replace the original unit, or locate another unit and inspect it for damage, debris, and foreign objects. Verify that you have the correct type of MC1A unit for your application:

• MC1A-D3 (Figure 4-14)

• MC1A-D3A2 (Figure 4-15)

• MC1A-STS1 (Figure 4-16)

• MC1A-ST1P (Figure 4-17)

• MC1A-TMD3 (Figure 4-18)

• MC1A-TME1 (Figure 4-19)

• MC1A-MDM1 (Figure 4-20)

Note: The MC1A-TMD3/-TME‘1/-MDM1 units do not have hardware option settings.

Step 2 Set the option switches to the same positions as those used on the removed unit.

Step 3 Insert the replacement unit. Is the LINE LED off and the FAIL/SVCE LED green?

Step 4 Check the indicators of the MC1A unit at the remote terminal. Is the FAIL/SVCE LED on the MC1A or TS1A unit red?

If Yes: If No:



Go to Step 4.

If Yes: If No:





Step 5 Repeat trouble analysis procedures (see Section 2, Plug-In Unit Front-Panel Devices). Is the LINE LED off and the FAIL/SVCE LED on the local MC1A unit green?

Step 6 Replace the MC1A or TS1A unit at the remote terminal. Is the LINE LED on the MC1A unit off and the FAIL/SVCE LED green?



If Yes: If No:




If Yes: If No:






CableLength(feet)

LBO-SETTING

0 - 100

100 - 225

225 - 325

325 - 450 THR THR

SET THR

THR SET

SET SET

1 2

d4

56

1.3

SET

THR

21

1 2

FC

9612

MD

31M

C1A

-D3

FAIL/SVCE LINE

Figure 4-14: MC1A-D3 Unit Front Panel and Hardware Option Locations




FC9612MDA1

MC1A-D3A2

FAIL/SVCE

CableLength(feet)

LBO-SETTING

0 - 100

100 - 225

225 - 325

325 - 450 THR THR

SET THR

THR SET

SET SET

1 2

DN

58

13

.3

LINE

2

SETTHR

1

LBO

Figure 4-15: MC1A-D3A2 Unit Front Panel and Hardware Option Locations




d7

60

3

SET

THR

21CableLength(feet)

LBO SETTING

0–100

100–225

225–325

325–450 THR THR

SET THR

THR SET

SET SET

1 2

SET

THR

21

FC

9612

MS

T1

MC

1A-S

TS

1

FAIL/SVCE LINE

Figure 4-16: MC1A-STS1 Unit Front Panel and Hardware Option Locations




d7

60

4

SET

THR

21CableLength(feet)

LBO SETTING

0–100

100–225

225–325

325–450 THR THR

SET THR

THR SET

SET SET

1 2

SET

THR

21

FC

9612

MS

T2

MC

1A-S

T1P

FAIL/SVCE LINE

Figure 4-17: MC1A-ST1P Unit Front Panel and Hardware Option Locations




MC1A-TMD3

FC9612TMD3

FAIL/SVCELINE

d7

10

0

Figure 4-18: MC1A-TMD3 Unit Front Panel

MC1A-TME1

FC9612TME1

FAIL/SVCE

LINE

d7

09

9

Figure 4-19: MC1A-TME1 Unit Front Panel




MC1A-MDM1

FC9612MDM1

FAIL/SVCELINE

d2

30

8.4

Figure 4-20: MC1A-MDM1 Unit Front Panel


4.8: Replacing the Low-Speed Switch (LS1A-D1)Unit


4.8 Replacing the Low-Speed Switch (LS1A-D1) Unit

4.8.1 Overview

This procedure lists the steps required to replace a failed LS1A-D1 Low-Speed Switch unit.


Note: LS1A units are not required for middle-speed groups using DS3, STS-1, or OC-3 cards, or in groups not requiring protect units in the low-speed section of the FLM 150 ADM.






4.8.2 Procedure

Step 1 If you have a known-good unit, use it to replace the failed LS1A-D1 unit, or locate another unit and inspect it for damage, debris, and foreign objects. Refer to Figure 4-21.

Note: The LS1A unit has no hardware option settings.

Step 2 Replace the original unit. Is the FAIL LED off?

Step 3 Repeat the trouble analysis procedures (see Section 2, Plug-In Unit Front-Panel Devices). Is the FAIL LED off?



If Yes: If No:



Go to Step 3.

If Yes: If No:






LS1A-D1

FC9612LSD1

d2

30

4.4

/ON PTCT

FAIL

Figure 4-21: LS1A-D1 Unit Front Panel


4.9: Replacing the Embedded Operation Channel(EC1A) Unit


4.9 Replacing the Embedded Operation Channel (EC1A) Unit

4.9.1 Overview

This procedure lists the steps required to replace a failed EC1A Embedded Operation Channel unit.


Note: EC1A units are required only when F6, STS-1 or OC-3 units are used in Groups 4 or 5 of the FLM 150 ADM. The EC1A is not required for DS1 applications.






4.9.2 Procedure

Step 1 If you have a known-good unit, use it to replace the original unit, or locate another unit and inspect it for damage, debris, and foreign objects. Verify that you have the correct version for your application:

• EC1A supports Section Data Communication Channel (SDCC) for OC-3, STS-1E, and OVTG tributaries. Refer to Figure 4-22

• EC1A-DL1 supports SDCC for all Synchronous Optical Network (SONET) tributaries. Refer to Figure 4-23.

• EC1A-DL2 supports SDCC for all SONET tributaries and FASTLANE applications. Refer to Figure 4-24.

• EC1A-V2 supports SDCC for all SONET tributaries synchronization status messaging. Refer to Figure 4-25.

Note: The EC1A unit has no hardware option settings.

Step 2 Replace the original unit. Are the FAIL and LINE LEDs off?

Step 3 Repeat trouble analysis procedures (refer to Section 3, Responding to Alarms and Conditions). Are the FAIL and LINE LEDs off?



If Yes: If No:



Go to Step 3.

If Yes: If No:





EC1A

FC9612EC11

DN

41

54

FAIL

LINE

Figure 4-22: EC1A Unit Front Panel

EC1A-DL1

FC9612EC11

d6

211

.1

FAIL

LINE

Figure 4-23: EC1A-DL1 Unit Front Panel




EC1A-DL2

FC9612ECD2

d6

91

7

FAIL

LINE

Figure 4-24: EC1A-DL2 Unit Front Panel

EC1A-V2

FC9612EC12

d7

60

8

FAIL

LINE

Figure 4-25: EC1A-V2 Unit Front Panel


4.10: Replacing the High-Speed Switch Control(HS1A) Unit


4.10 Replacing the High-Speed Switch Control (HS1A) Unit

4.10.1 Overview

This procedure lists the steps required to install a failed HS1A High-Speed Switch Control unit.


Refer to the Unit Descriptions practice, FJTU 320-515-000, for hardware option default settings.







4.10.2 Procedure

Step 1 If you have a known-good HS1A-AD1/AD2 unit, use it to replace the original unit, or locate another unit and inspect it for damage, debris, and foreign objects. Verify that you have the correct version for your application:

• The HS1A-AD1 unit is used for all FLM 150 ADM systems. This unit does not support orderwire and DCC operations in nodes adjacent to a regenerator site.

• The HS1A-AD2 unit is a fully compatible replacement for the HS1A-AD1 and provides orderwire protection and DCC operations for FLM 150 ADM systems adjacent to regenerator sites and also supports synchronization messaging.

Refer to Figure 4-26 for a view of the HS1A-AD1/-AD2 unit.

Step 2 Set the option switches to the same positions used on the removed unit.

Step 3 Install the new unit. Is the FAIL LED off?

Step 4 Check the status of the SV1A unit at the remote terminal. Is the FAIL LED on the remote SV1A unit off?

Step 5 Replace the SV1A unit at the remote terminal. Are the LINE and FAIL LEDs on the local HS1A-AD1 unit off?

If Yes: If No:



Go to Step 4.

If Yes: If No:


If Yes: If No:







Step 6 Repeat trouble analysis procedures (see Section 2, Plug-In Unit Front-Panel Devices). Is the FAIL LED off?



If Yes: If No:





HS1A-AD1

FC9612SAM1

d634

0.2

FAIL

LINE

AUTO

FORCE

MNL

HG1 MODE

HG2 MODE

AUTO

FORCE

MNL

Setting TBOS F1 SET RESTR MASTER/SLAVE

Open 1 All 1sNo datalinkrestoration

Slave

Closed 2 All 0s Restoredata link

Master

a

aAll nodes in a given ring should be set to the same direction.

F1 SET

RESTR

MASTER SLAVE12

34

OP

EN

2 1 TBOS

SW1

F1 SET

RESTR

MASTER SLAVE12

34

OP

EN

2 1 TBOS

SW1

ON

OF

F

ON

OF

F

Figure 4-26: HS1A-AD1/-AD2 Unit Front Panel and Hardware Option Locations


4.11: Replacing the OC-12 Optical Channel(HC1A-6Lx1) Units


4.11 Replacing the OC-12 Optical Channel (HC1A-6Lx1) Units

4.11.1 Overview

This procedure lists the steps required to replace the failed HC1A-6Lx1 OC-12 Optical unit.


Review this procedure before attempting to replace the HC1A-6Lx1 optical plug-in units. In addition, refer to Section 5.1, Handling Fiber Cables, Section 5.2, Cleaning, Connecting, and Disconnecting the Optical Connectors, and Section 5.3, Measuring Optical Power, located in this practice, to avoid damaging equipment.



DANGER:Never look into the end of a fiber-optic cable, fiber cord, fiber pigtail, or fiber. If laser light is present, you can suffer permanent eye damage or blindness. Even brief exposure causes damage very quickly.




4.11.2 Procedure

Step 1 Remove the front cover from the optical cable tray located on the top front of the shelf.

Note: Each unit occupies both the Working and Protect high-speed slot for the respective group (high-speed Group 1 or 2). When both units are in place, a pair of interconnect ribbon cables must be disconnected between them before the unit(s) can be removed.

Step 2 Disconnect the interconnect ribbon cable between CN4 of the Group 1 unit and CN3 of the Group 2 unit. Refer to Figures 4-27 and 4-28.

Step 3 Disconnect the interconnect ribbon cable between CN3 of the Group 1 unit and CN4 of the Group 2 unit. Refer to Figures 4-27 and 4-28.

Step 4 Disconnect the fiber cables.

Step 5 Remove the original HC1A-6Lx1 unit(s).

Step 6 If you have a known-good unit, use it to replace the failed optical HC1A-6Lx1 unit(s), or locate another unit and inspect it for damage, debris, and foreign objects.

Note: The HC1A-6Lx1 unit has no hardware option settings.

Step 7 Reinstall the interconnect cable between CN3 of the Group 1 unit and CN4 of the Group 2 unit. Refer to Figures 4-27 and 4-28.

Step 8 Reinstall the interconnect cable between CN4 of the Group 1 unit and CN3 of the Group 2 unit. Refer to Figures 4-27 and 4-28.

Step 9 Reconnect the fibers and insert the new unit(s). Are the LINE and FAIL LEDs on the optical unit off?

If Yes: If No:



Go to Step 10.




Step 10 Repeat trouble analysis procedures (see Section 2, Plug-In Unit Front-Panel Devices). Are the LINE and FAIL LEDs off?



If Yes: If No:



DN

56

48

.1

OPT IN

OPT OUT

FAIL

SEND

LINE

RCV

ON LINE

CN4 CN3

RCV SENDTHRU

DANGERInvisible laserradiation from

connectorswhen uncoupledAVOID DIRECT

EXPOSURETO BEAM

HC1A-6LX1

FC

9612

_ _

_ _

Figure 4-27: HC1A-L6x1 Unit Front Panel and Side View




FAIL

SEND

LINE

RCV

ON LINE

CN4 CN3

RCV SENDTHRU



EXPOSURETO BEAM

HC1A-6LX1

FC

9612

_ _

_ _

FAIL

SEND

LINE

RCV

ON LINE

CN4 CN3

RCV SENDTHRU



EXPOSURETO BEAM

HC1A-6LX1

FC

9612

_ _

_ _

d6

40

5

Figure 4-28: Interface Cables Between the Group 1 and Group 2 Units


4.12: Replacing the OC-3 Optical Channel (HC1Aand MC6A) Units


4.12 Replacing the OC-3 Optical Channel (HC1A and MC6A) Units

4.12.1 Overview

This procedure lists the steps required to replace failed the HC1A and MC6A OC-3 Optical units.




Review this procedure before attempting to replace the HC1A and MC6A optical plug-in units. In addition, refer to Section 5.1, Handling Fiber Cables; Section 5.2, Cleaning, Connecting, and Disconnecting the Optical Connectors; and Section 5.3, Measuring Optical Power, located in this practice, to avoid damaging equipment.







Refer to Figures 4-29 and 4-30 while performing the following procedures. Please note that the both upper and lower card levers should be extended, as shown in Figure 4-29, when installing or removing the optical unit.

The secondary latch, located at the bottom of the optical unit as shown in Figure 4-30, is also visible when viewing the optical unit from the side.

d5

02

7.2

Removal Instruction Label

OpticalConnector

Covers

Figure 4-29: Removing the Optical Unit




d622

6.1

SECONDARYLATCH

Figure 4-30: The Secondary Latch at the Bottom of the Optical Unit




4.12.2 Procedure—Removing the Optical Unit

Step 1 Using both hands, squeeze the lever lock tabs toward the levers and rotate the top and bottom extractor levers. Slide the unit out until the secondary latch engages (a little less than half way out of the slot).

Step 2 Disconnect the optical fibers. Refer to Section 5.1, Handling Fiber Cables.

Step 3 If needed, install necessary optical connector cover on the fiber jumper.

Step 4 Lift the metal spring of the secondary latch and pull the unit out.

Step 5 Are there more optical channel units (HC1A and MC6A) to be removed from the shelf?

If Yes: If No:

Repeat procedure from Step 1 of Removing the Optical Channel Unit.





4.12.3 Procedure—Installing the Optical Unit

Procedure

Step 1 Get an HC1A or MC6A unit and verify that you have the correct version for your application:

• HC1A-3xxx (Figure 4-31)

• MC6A-3xxx (Figure 4-32)

• MC6A-31xx (Figure 4-33)

• MC6A-31xL/-31xM Issue 2, MC6A-31xS Issue 2 and later, and MC6A-31xA (Figure 4-34)

• MC6A-31xL, Issue 3 (Figure 4-35)

• MC6A-31xM, Issue 3 (Figure 4-36)

Step 2 Inspect the HC1A or MC6A for damage, debris, and foreign objects.

Step 3 Go to Step 4 if replacing the MC6A-31xL/-31xM/-31xS /-31xA, OC-3 plug-in units. If the NE is not configured this way, go to Step 5.

Step 4 Ensure that the hardware option switches are set the same on the new MC6A-31xL/-31xM/-31xS /-31xA plug-in units as on the units being replaced. If the unit that is to be replaced has an MR/LR switch option, this should not be changed from factory default. Refer to the FLM 150 ADM Unit Descriptions practice, FJTU-320-515-000, for a detailed description of the hardware option switches and default settings used on these units.

Note: The SONET/SDH switch should not be set to SDH when the these units are used in the FLM 150 ADM system.

Step 5 Carefully slide the HC1A or MC6A unit into the appropriate HC1A or MC6A slot until the secondary latch engages (a little more than halfway into the slot).

Step 6 Connect optical fibers. Refer to are to be connected at the time of installation, Section 5.1, Handling Fiber Cables.




Step 7 Make sure the extractor levers are open. Slowly press the unit into the mounting slot. Gently close the top and bottom extractor levers with both hands to seat the unit into the backplane. Are the LINE and FAIL LEDs on the optical unit off?

Step 8 Repeat trouble analysis procedures. Refer to Section 2, Plug-In Unit Front-Panel Devices. Are the LINE and FAIL LEDs on the optical unit off?



If Yes: If No:



Go to Step 8.

If Yes: If No:


HC1A-3xxx

FC9612H3xx

DN

60

02

FAIL

LINE

SEND

RCV

ON LINE

DA

NG

ER

Figure 4-31: Typical HC1A-3xxx Unit Front Panel




FC

9616

3MR

1

MC6A-3MR1

FAIL

SEND

LINE

OD

3-00

06

RCV

ON LINE

DA

NG

ER

Figure 4-32: Typical MC6A-3xxx Unit Front Panel

FC9616xx31

MC6A-31xx

FAIL

LINE

SEND

RCV

ON LINE

DA

NG

ER

d5

63

5.4

Figure 4-33: Typical MC6A-31xx Unit Front Panel




OC3 I/F MODE

SDHSONET OP

EN

12

m06

58

FC9616LRx1

MC6A-31xS

FAIL

LINE

SEND

RCV

ON LINE

DA

NG

ER

Optical Connector

OC3 I/F MODE

SDHSONET OP

EN

12

Figure 4-34: MC6A-31xL/-31xM (Issue 2), MC6A-31xS (Issue 2 and Later), and MC6A-31xA UnitHardware Option Locations




m06

60

FC9616LRx1

MC6A-31xL

FAIL

LINE

SEND

RCV

ON LINE

DA

NG

EROptical Connector

OC

3 I/F

MO

DE

SD

HS

ON

ET

OPEN

1 2

LRM

R

OC3 I/FMODE

SDHSONET OP

EN

12 LRMR

Figure 4-35: MC6A-31xL (Issue 3) Unit Front Panel and Hardware Option Locations




m06

59

FC9616MRx1

MC6A-31xM

FAIL

LINE

SEND

RCV

ON LINE

DA

NG

EROptical Connector

OC

3 I/F

MO

DE

SD

HS

ON

ET

OPEN

1 2

LRM

RSDHSONET O

PE

N

12 LRMR

OC3 I/FMODE

Figure 4-36: MC6A-31xM (Issue 3) Unit Front Panel and Hardware Option Locations


4.13: Replacing the STS-1 Electrical Channel(HC1A-STS1) Unit


4.13 Replacing the STS-1 Electrical Channel (HC1A-STS1) Unit

4.13.1 Overview

This procedure lists the steps required to replace a failed HC1A-STS1 Electrical Channel unit.









4.13.2 Procedure

Step 1 If you have a known-good HC1A-STS1 unit, use it to replace the original unit, or locate another unit and inspect if for damage, debris, and foreign objects. Figure 4-37 shows the HC1A-STS1 unit front panel and hardware option locations.

Step 2 Set the option switches on the new unit to the same positions used on the removed unit.

Step 3 Insert the replacement unit by carefully sliding the HC1A unit into the appropriate HC1A slot until the connectors meet. Make sure the extractor levers are open. Slowly press the unit into the mounting slot. Gently close the top and bottom extractor levers with both hands to seat the unit into the backplane. Is the LINE LED off and the FAIL/SVCE LED green?

Step 4 Check the incoming signal at the DSX-1/DSX-3/STS-1 bay. Is the signal present and error-free at the DSX?

Step 5 Repeat trouble analysis procedures. Refer to Section 2, Plug-In Unit Front-Panel Devices. Is the LINE LED off and the FAIL/SVCE LED green?



If Yes: If No:



Go to Step 4.

If Yes: If No:

Go to Step 5. The source of the problem is not the FLM 150 ADM.


If Yes: If No:





o200

72.2

CableLength(feet)

LBO-SETTING

0 - 100

100 - 225

225 - 325

325 - 450 THR THR

SET THR

THR SET

SET SET

1 2

0 1 0 0 2 0

FC

9612

HS

T1

HC

1A-S

TS

1

FAIL/SVCE

LINE

12

30 1 0 0 2 0

0 1 0 0 2 0

LBOCH1

LBOCH2

LBOCH3

SET

THR

0 1 0 0 2 0

SET

THR

0 1 0 0 2 0

SET

THR

0 1 0 0 2 0

LBOCH1

LBOCH2

LBOCH3

Note: These switches are represented on the back of thecabinet board, and the right and left sides are reversed.

Figure 4-37: HC1A-STS1 Unit Front Panel and Hardware Option Locations


4.14: Replacing the Timing Control Access (TCA)Unit


4.14 Replacing the Timing Control Access (TCA) Unit

4.14.1 Overview

This procedure lists the steps required to replace a failed TCA or TCA-ENH Timing Control and Access units.


Refer to the Unit Descriptions practice, FJTU320-515-000, for hardware option default settings.







4.14.2 Procedure

Step 1 If you have a known-good unit, use it to replace the failed TCA unit, or locate another unit and inspect it for damage, debris, and foreign objects. Refer to Figure 4-38.


Note: The TCA-ENH unit does not have the ALM switch.

Step 3 Install the replacement unit. Is the LINE LED off and the FAIL/SVCE LED on the TCA unit green?

Step 4 Repeat trouble analysis procedures (refer to Section 3, Responding to Alarms and Conditions). Is the LINE LED off and the FAIL/SVCE LED on the TCA unit green?



If Yes: If No:



Go to Step 4.

If Yes: If No:







TC

A

FC9616TCA

d6

00

3.2

FAIL/SVCE

LINE

LBOSET

ON OFF

5

4

3

2

1

–O

PE

N–

OO

FA

LM

AC

TV

T

INH

BO

PE

N2

1

Cable Length(feet)

Segment 1 Segment 2 Segment 3 Segment 4 Segment 5

0 - 173

173-346

346-519

ON

OFF

OFF

ON

OFF

OFF

OFF

ON

OFF

OFF

ON

OFF

OFF

OFF

ON

Cable Length(feet)


0 - 250

250 - 500

500-750

ON

OFF

OFF

ON

OFF

OFF

OFF

ON

OFF

OFF

ON

OFF

OFF

OFF

ON

Note: This table is imprinted on the back of the unit.

TCA LBO SETTINGS - 26 AWG

TCA LBO SETTINGS - 22 AWG

Figure 4-38: TCA/TCA-ENH Unit Front Panel and Hardware Option Locations


4.15: Replacing the Low-Speed Channel–DS1(LC1A-D1xx) Unit


4.15 Replacing the Low-Speed Channel–DS1(LC1A-D1xx) Unit

4.15.1 Overview

This procedure lists the steps required to replace a failed LC1A-D1/-D1E/-D1E2 Low-Speed unit.

Refer to the Application Engineering practice, FJTU-320-515-120, Section C, Hardware Options, for descriptions of plug-in unit hardware option settings.








4.15.2 Procedure

Step 1 If you have a known-good LC1A unit, use it to replace the original unit, or locate another unit and inspect if for damage, debris, and foreign objects. Figure 4-39 shows the front panel and hardware option locations for the LC1A-D1 and LC1A-D1E units.

Note: The line buildout (LBO) settings for the LC1A-D1E2 unit are software provisioned.


Step 3 Install the replacement LC1A unit. Is the LINE LED off and the FAIL/SVCE LED green?

Step 4 Check the incoming signal at the DSX-1/DSX-3/STS-1 bay. Is the signal present and error-free at the DSX?

Step 5 Repeat trouble analysis procedures. Refer to Section 2, Plug-In Unit Front-Panel Devices. Is the LINE LED off and the FAIL/SVCE LED green?



If Yes: If No:



Go to Step 4.

If Yes: If No:

Go to Step 5. The source of the problem is not the FLM 150 ADM.


If Yes: If No:





LC1A-D1

FC

9612

LD11

d242

2.5

FAIL/SVCE

LINE

LCIA-D1 LBO SETTINGS-22 AWG

Cable Length(feet)


0–250

250–500

500–750

ON

OFF

OFF

ON

OFF

OFF

OFF

ON

OFF

OFF

ON

OFF

OFF

OFF

ON

(CH 4)

(CH 3)

(CH 2)

(CH 1)

Note: This table is imprinted on the back of the unit

LCIA-D1 LBO SETTINGS-26 AWG

Cable Length(feet)


0–173

173–346

346–519

ON

OFF

OFF

ON

OFF

OFF

OFF

ON

OFF

OFF

ON

OFF

OFF

OFF

ON

1 2 3 4 5

OPEN

1 2 3 4 5

OPEN

1 2 3 4 5

OPEN

1 2 3 4 5

OPEN

1 2 3 4 5

OPEN

1 2 3 4 5

OPEN

1 2 3 4 5

OPEN

1 2 3 4 5

OPEN

ON

OFF

ON

OFF

ON

OFF

ON

OFF

Figure 4-39: LC1A-D1/-D1E Unit Front Panel and Hardware Option Locations


4.16: Replacing the Low-Speed Channel–OVTG(LC1A-F6xx) Unit


4.16 Replacing the Low-Speed Channel–OVTG(LC1A-F6xx) Unit

4.16.1 Overview

This procedure lists the steps required to replace a failed LC1A-F6, LC1A-F6C1, or LC1A-F6T1 Low-speed channel unit.


Review this procedure before attempting to replace the LC1A-F6, LC1A-F6C1, or LC1A-F6T1 plug-in unit. In addition, refer to Section 5.1, Handling Fiber Cables; Section 5.2, Cleaning, Connecting, and Disconnecting the Optical Connectors; and Section 5.3, Measuring Optical Power, located in this practice, to avoid damaging equipment.







4.16.2 Procedure

Step 1 Remove the front cover from the optical cable tray located on the top front of the shelf.

Step 2 Disconnect the fiber cables from the original LC1A-F6, LC1A-F6C1, or LC1A-F6T1 unit and store them in the fiber tray under the shelf.

Step 3 If you have a known-good LC1A-F6, LC1A-F6C1, or LC1A-F6T1 unit, use it to replace the original unit, or locate another unit and inspect it for damage, debris, and foreign objects. Refer to Figure 4-40.

Note: These units have no hardware option settings.

Step 4 Remove the fiber cables from the fiber tray and reconnect the fibers to the unit.

Step 5 Make sure the extractor lever is open and slowly press the unit into the mounting slot. Gently close the extractor lever to seat the unit into the backplane connector. Is the LINE LED off or yellow and the FAIL/ SVCE LED off or green?

Step 6 Repeat the trouble analysis procedures. Is the LINE LED off or yellow and the FAIL/ SVCE LED off or green?



If Yes: If No:



Go to Step 6.

If Yes: If No:



Call the Fujitsu Technical Assistance Center at 1-800-.




FAIL/SVCE

LINE FC

9612

LF61

LC1A-F6

d4

38

5.4

IN

OU

T

IN

OUT

OUT

IN

Figure 4-40: LC1A-F6 Unit Face and Side View



5.1: Handling Fiber Cables

5 Miscellaneous Procedures

5.1 Handling Fiber Cables

5.1.1 Overview

This section lists the precautionary measures that must be followed when handling optical fibers and optical components.

DANGER:Never look into the end of a fiber optic cable, fiber cord, fiber pigtail, or fiber. If laser light is present, you can suffer permanent eye damage or blindness. Even brief exposure causes damage very quickly.

DANGER:Never handle exposed fiber with bare hands or touch it to your body. A fiber fragment could enter the skin and be very difficult to detect and remove.

Figure 5-1 shows the label that is attached to laser-emitting devices as a reminder.

DANGERInvisible LaserRadiation From

Connectors WhenUncoupled

AVOID DIRECTEXPOSURE TO BEAM.

DANGERRayonnement a laser

quand ouvert.EVITER L'EXPOSITIONDIRECTE AU RAYON.

Figure 5-1: Laser Radiation Caution


5.1: Handling Fiber CablesMaintenance and Trouble ClearingFJTU-320-515-480

5.1.2 Fiber Handling Guidelines

Step 1 Protective caps are provided with the optical cord connectors.(Figure 5-2). When optical cords are not going to be used for a long time, put the protective caps back on the optical connectors and seal the cords in a vinyl bag.

Step 2 Do not expose the optical cords to direct sunlight. The recommended storage temperature is –10° to +60°C (14° to 140°F), and the maximum recommended relative humidity is 90 percent.

Step 3 Never apply excessive force to the connector by pulling, bending, or twisting the cord when the coupling nut is tightened (Figure 5-3).

PROTECTIVECAP

OD

2-00

21-9

3

Figure 5-2: Protective Cap

CONNECTORTENSILE STRENGTH:10 kg (22 lbs.) OR LESS

OPTICAL FIBER CORDTENSILE STRENGTH:20 kg (44 lbs.) OR LESS

OD

2-00

22-9

3

Figure 5-3: Tension Limit



Step 4 Do not pull the cord when the connector is attached to the optical plug-in unit or optical adapter of the lightwave distribution frame (LDF) (Figure 5-4).

Step 5 Take precautions not to place sharp bends in the cord. This may occur in attempting to route the cord around an obstruction. Remove the obstruction or find a different route for the cord (see Figure 5-5).

OD

2-00

23-9

3

Figure 5-4: Fiber Cord Pulling

OD

2-0

02

4-9

3

Figure 5-5: Fiber Cord Bending to Clear an Obstruction



Step 6 Do not bend the cord to a radius of less than 50 mm (Figure 5-6).

Step 7 Do not twist the cord more than 360 degrees per meter of length (Figure 5-7).

R 50 mm(2 in.)

OD

2-00

25-9

3

Figure 5-6: Fiber Cord Maximum Bending Radius

OD

2-00

26-9

3

Figure 5-7: Twisting the Fiber Cord



Step 8 Do not drop or step on the cord and do not subject it to excessive vibration (Figure 5-8).


OD

2-0

02

7-9

3

Figure 5-8: Fiber Cord Vibration and Shock Damage


5.2: Cleaning, Connecting, and Disconnectingthe Optical Connectors


5.2 Cleaning, Connecting, and Disconnecting the Optical Connectors

5.2.1 Overview

This procedure discusses the procedure for cleaning, connecting, and disconnecting the optical connectors.

DANGER:Never look into the end of a fiber optic cable, fiber cord, fiber pigtail, or fiber. If laser light is present, you can suffer permanent eye damage or blindness. Even brief exposure causes damage very quickly.

The following tools are required:

• Pure alcohol (more than 90 percent purity)

• A can of compressed air

• A cotton swab




5.2.2 Cleaning the Connectors

Clean the fiber end surface if you are using the connector for the first time. In addition, clean the surface every time you disconnect the connector.

Step 1 Inspect the optical fiber cords and connectors for damage.

Step 2 Clean the connectors by wiping the fiber end surface with a cotton swab soaked in alcohol (Figure 5-9).

Step 3 After cleaning them, use compressed air to remove any remaining alcohol (Figure 5-10).


COTTON SWAB

FIBER END SURFACEOPTICAL FIBER CONNECTOR

o200

30.2

Figure 5-9: Cleaning the Fiber End Surface

AIR NOZZLE o200

31.2

Figure 5-10: Air Drying




5.2.3 Connecting the Fiber Cable

Step 1 Insert the fiber cord into the plug-in unit, adapter, distribution frame, or attenuator. For slotted connector types, make sure that the tab on the connector is lined up with the slot on the receptacle.

Step 2 Tighten the coupling nut until it is “finger tight.” Do not turn the connector body or twist the fiber cord (Figure 5-11).


5.2.4 Disconnecting the Fiber Cable

Step 1 Loosen the coupling nut completely. Do not twist the fiber cord (Figure 5-12).

Step 2 Remove the connector body.

Step 3 Put a protective cap on the connector.


o200

28.2

CW

OPTICAL FIBERCORD

COUPLING NUTCONNECTOR BODY

Figure 5-11: Connection Method

CCW

o200

29.2

OPTICAL FIBERCORD

COUPLING NUTCONNECTOR BODY

Figure 5-12: Disconnection Method


5.3: Measuring Optical PowerMaintenance and Trouble ClearingFJTU-320-515-480

5.3 Measuring Optical Power

5.3.1 Measuring Optical Output Power

This section provides detailed instructions for measuring optical output power at the HC1A-3xxx and MC6A-3xxx units in the FLM 150 ADM. The channel to be measured must not be carrying traffic before this procedure is begun. Once the measurement is complete, record the information on the data record provided in the Plug-In Installation practice, FJTU-320-515-220, Appendix A.

Measurement Setup

Figure 5-13 shows the power meter setup to be used throughout the procedure.

OPTICALPOWER METER

OPTICAL SENSOR

d162

6 .5

T IN OPTICAL LINE

ON LINE

FAIL

SEND

LINE

HC1A-3MR1

FC961M3M1

ON LINE

FAIL

SEND

LINE

HC1A-3MR1

FC961M3M1

ON LINE

FAIL

SEND

LINE

HC1A-3MR1

FC961M3M1

ON LINE

FAIL

SEND

LINE

HC1A-3MR1

FC961M3M1

DA

NG

ER

DA

NG

ER

DA

NG

ER

DA

NG

ER

Figure 5-13: FLM 150 ADM Optical Output Power Measurement



Before You Start

• Make sure all connectors are cleaned before measuring. Optical connector performance can be affected by dust.

• Before you begin measuring, verify that the channel to be measured is not carrying traffic.

• Make sure the following required equipment is available: Optical Power Meter with Sensor (Ando AQ-1135E/AQ-1965 or equivalent) and Optical Fiber Test Cord (Fujitsu H660-5381-U920 SM, PC/PC or equivalent) with the same type connectors used by power meter and optical units.

DANGER:Never look into the end of a fiber pigtail or a fiber cable. Permanent eye damage or blindness can occur very quickly if laser light is present.

Procedure

Step 1 Disconnect the optical fiber cord from the transmitter side of the HC1A/MC6A unit.

Step 2 Attach the protective cap to the optical fiber cord. (If no fiber cord is connected, remove the protective cap from the unit and keep the protective cap in the storage box on the shelf for future use.)

Step 3 Clean the optical connector on the HC1A/MC6A unit.

Step 4 Set the range on the optical power meter (see Figure 5-13) to match the expected power level as shown below:

• MR units = –15.0 to –8.0 dBm

• LR units = –5.0 to 0.0 dBm

Step 5 Clean the connectors on the optical fiber test cord.

Step 6 Connect one end of the optical fiber test cord to the sending side of the HC1A/MC6A unit optical connector and the other end to the optical sensor used with the optical power meter (see Figure 5-13).

Step 7 Plug the unit into the shelf.

Step 8 Record the optical power meter reading.



Step 9 If the output optical power requirements shown in Step 4 are met, continue with Step 11. If the requirements are not met, perform the following substeps until the output power meets the specifications outlined above.

a. Clean optical connectors on the HC1A/MC6A units, fiber test cords, and test equipment and repeat Steps 6 through 8.

b. Replace the optical fiber cords and repeat Steps 6 through 8.

a. Replace the HC1A/MC6A units and repeat Steps 3 through 8.

Step 10 Remove the plug-in units.

Step 11 Disconnect the optical fiber test cords from the HC1A/MC6A units.

Step 12 Reconnect the optical fiber cords (part of the optical transmission line).

Step 13 Reinstall the removed units.




5.3.2 Measuring Optical Input Power

This section provides detailed instructions for measuring optical input power at the HC1A-3xRx units. When measuring optical input power, check the HC1A-3xRx units for correct optical output power using the procedure in Section 5.3.1, Measuring Optical Output Power. Once the measurement is complete, you can record the information on the data record provided in the Plug-In Installation practice, FJTU-320-515-220, Appendix A.

Measurement Setup

Figure 5-14 shows the power meter setup to be used throughout the procedure.

OPTICAL POWER METER

OPTICAL SENSOR

m09

24

R IN OPTICAL LINE

ON LINE

FAIL

SEND

LINE

HC1A-3MR1

FC961M3M1

ON LINE

FAIL

SEND

LINE

HC1A-3MR1

FC961M3M1

ON LINE

FAIL

SEND

LINE

HC1A-3MR1

FC961M3M1

ON LINE

FAIL

SEND

LINE

HC1A-3MR1

FC961M3M1

DA

NG

ER

DA

NG

ER

DA

NG

ER

DA

NG

ER

Figure 5-14: FLM 150 ADM Optical Receiving Power Measurement



Before You Start

• Check for correct optical output using the procedure in Section 5.3.1, Measuring Optical Output Power.

• Clean all optical connectors.

• Make sure the channel to be measured is out of service.

• Make sure you have the Optical Power Meter with Sensor (Ando AQ-1135E/AQ-1965 or AGNT).

DANGER:Never look into the end of a fiber optic cable, fiber cord, fiber pigtail, or fiber. Permanent eye damage or blindness can occur very quickly if laser light is present.

Procedure

Step 1 Remove the HC1A-MC6A unit.

Step 2 Disconnect the optical fiber cord from the receive side of the unit.

Step 3 Attach the protective cap to the unit. The cap should remain in place during measurement.

Step 4 Clean the end surface of the optical fiber cord.

Step 5 Connect one end of the optical receive fiber cord to the optical attenuator (see Figure 5-14).

Step 6 Ensure that the HC1A/MC6A unit at the distant end is connected to the transmission line and is transmitting an optical signal.

Step 7 Record the optical power meter reading. Required optical parameters are as follows:

• MR units = Minimum –28 dBm

• LR units = Minimum –34 dBm



Step 8 If the optical input power is more than –8 dBm, insert a 10- or 15-dB fixed attenuator between the lightwave distribution frame (LDF) and the optical fiber input cord. Select the amount of attenuation so that input power is between –8 and –28 dBm.

Note: The following are the suggested fixed optical attenuators:– 10-dB attenuator: H72M-2032-L002– 15-dB attenuator: H72M-2032-L004

Note: If the optical receiving power is between –3 and –8 dBm, a 10-dB attenuator should be inserted. If it is more than –3 dBm, a 15 -dB attenuator should be used.

Step 9 If optical input power is less than –28 dBm on the MR units, or less than –34 dBm on the LR units, perform the following steps one at a time until required input power is measured.

Step 10 Disconnect transmission path fiber from power meter; then reconnect the fiber to the power meter. (A slight alignment change may affect the reading.)

a. Clean optical connectors on both the fiber cord and test equipment. Repeat Steps 4 through 7.

b. Test (or replace, if required) HC1A/MC6A units at the opposite terminal. Repeat Steps 4 through 7.

Step 11 When the power reading is correct, disconnect optical power and reconnect the fiber optic cord to the HC1A/MC6A unit.

Step 12 Reinstall the unit.



5.4: Verifying External Clock and ClockConnections


5.4 Verifying External Clock and Clock Connections

5.4.1 Summary

This procedure lists the steps required to check external clock connections, and to check the external clock signal source for the FLM 150ADM. Table 5-1 describes the connectors.

5.4.2 Procedure

Step 1 If an external clock source is being used, verify that the D-Sub connectors are installed on the appropriate primary and secondary clock cables (see Figures 5-15 and 5-16).

Step 2 Connect the cables to the EXT CLK PRIM (CN14) and EXT CLK SECOND (CN13), respectively. Refer to the Shelf Installation practice, FJTU-320-515-200, Section 2, Backplane Connection Procedures, for connector locations.

Step 3 To retrieve any existing external clock source alarms, go to one of the following practices:

• If using TL1 Commands, go to the TL1 Commands practice, FJTU-320-515-274, RTRV Commands, and check for any alarms on the clock source.

• If using FLEXR®, go to the Fujitsu FLEXR Manual, FJTU-320-900-FLX, and check for any alarms on the clock source.


Table 5-1: Connectors for External Clock Cables

Connector Function Description Connector Type

Wire Gauge

CN14 EXTERNAL CLOCK

(Primary)

Input of primary external clock for interface unit in the synchronous network

Output of reference clock from Optical Synchronous Network

9-pin D-Sub No. 22 AWG

CN13 EXTERNALCLOCK

(Secondary)

Input of secondary external clock for interface unit in the synchronous network. Output of reference clock from Optical Synchronous Network

9-pin D-Sub Mo. 22 AWG


5.4: Verifying External Clock and ClockConnections


9

5

8

4

7

3

6

2

1

P-ECLK IN (T)

NC

NC

P-ECLK OUT (T)

P-ECLK OUT (R)

SG

NC

FG

W/G

G/W

EU9 PIN M D-SUB

OD

2-00

87-9

4

CN 4

P

P-ECLK IN (R)

PW/BL

BL/W

DRAIN

DRAIN

Figure 5-15: External Clock (Primary) Connector Pin-Out

9

5

8

4

7

3

6

2

1

S-ECLK IN (T)

NC

NC

S-ECLK OUT (T)

S-ECLK OUT (R)

SG

NC

FG

W/G

G/W

EU9 PIN M D-SUB

OD

2-00

88-9

4

CN 3

P

S-ECLK IN (R)

PW/BL

BL/W

DRAIN

DRAIN

Figure 5-16: External Clock (Secondary) Connector Pin-Out


5.5: Correcting the T1 or T3 Framing FormatMaintenance and Trouble ClearingFJTU-320-515-480

5.5 Correcting the T1 or T3 Framing Format

5.5.1 Overview

This procedure describes the retrieval and editing of the provisioning to verify that the T1 or T3 framing format matches the signal format. Note that the engineering work order provides the appropriate provisioning.

This task can be performed using any of the following procedures presented below: FLEXR or TL1.

5.5.2 FLEXR Procedure

Step 1 Retrieve the T1 or T3 format.

a. From the Provisioning menu, choose Facility, then choose Set Facility.

b. Click the unit, then click the shelf edge. A dialog box opens.

c. Click Retrieve to show the current format setting. The possible settings are shown in the following table.

Is the facility provisioned correctly?

T1(Only if Group is configured for D1E)

T3

UNFR (unframed) ASYNC (asynchronous)

SF (superframe) UNFR (unframed)

ESF (extended superframe) —

DLC16 —

If Yes: If No:

Click Close.


Go to Step 2.



Step 2 Edit the T1 or T3 format.

a. Select the desired option.

b. Click OK.

c. Click Retrieve to verify that the command was successful.

d. Click Close. Is the framing correct?

If Yes: If No:

You have completed this procedure. Call the Fujitsu Technical Assistance Center at 1-800-USE-FTAC (1-800-873-3822) for assistance.



5.5.3 TL1 Procedure

Note: Verify that you receive a completed (COMPLD) response to each command before going to the next step.

Step 1 Retrieve the T1 or T3 format by using one of the following TL1 commands.

RTRV-T1:TID:AID:CTAG;

RTRV-T3:TID:AID:CTAG;

The FMT keyword and the applicable domain show the framing format. The possible settings are shown in the following table.


Keyword T1 Domain(Only if Group is configured for D1E)

T3 Domain

FMT UNFR (unframed) ASYNC (asynchronous)



DLC16 —

If Yes: If No:


Go to Step 2.



Step 2 Edit the T1 or T3 format by using one of the following TL1 commands.

ED-T1:TID:AID:CTAG:::KEYWORD=DOMAIN;

ED-T3:TID:AID:CTAG:::KEYWORD=DOMAIN;

The possible settings are shown in the following table.

Is the framing correct?

Keyword T1 Domain(Only if Group is configured for D1E)

T3 Domain

FMT UNFR (unframed) ASYNC (asynchronous)



DLC16 —

If Yes: If No:



5.6: Correcting Unidirectional or BidirectionalSwitch Provisioning


5.6 Correcting Unidirectional or Bidirectional Switch Provisioning

5.6.1 Overview

This procedure lists the steps required to correct the provisioning for the protection switching for a fiber-optic group. Note that the engineering work order provides the appropriate provisioning.

This task can be performed using any of the following procedures presented below: FLEXR or TL1.


Step 1 Retrieve the direction.

a. From the Provisioning menu, choose System then choose Set Switch Lock-In.

b. Click the unit and then click on any nonselectable unit. A dialog box opens.

c. Click Retrieve to show the current setting. The possible directional settings are UNI (unidirectional) or BI (bidirectional). Is the facility provisioned correctly?

If Yes: If No:

Click Close.


Go to Step 2.




Step 2 Edit the Direction.

a. Select the desired option.

b. Click OK.

c. Click Retrieve to verify that the command was successful.

d. Click Close. Is the Direction correct?

5.6.3 TL1 Procedure


Step 1 Retrieve the DIRN by using one of the following TL1 commands.

RTRV-FFP-OC3:TID:AID:CTAG;

The DIRN keyword and the applicable domain show the current provisioning. The possible settings are shown in the following table.


If Yes: If No:


Keyword Domain

DIRN UNI (unidirectional)

BI (bidirectional)

If Yes: If No:


Go to Step 2.




Step 2 Edit the DIRN by using the following TL1 command.

ED-FFP-OC3:TID:AID:CTAG:::KEYWORD=DOMAIN;

The possible settings are shown in the table below.

Is the Direction correct?

Keyword Domain

DIRN UNI (unidirectional)

BI (bidirectional)

If Yes: If No:



5.7: Placing an SDCC In ServiceMaintenance and Trouble ClearingFJTU-320-515-480

5.7 Placing an SDCC In Service

5.7.1 Overview

This procedure lists the steps required to place the Section Data Communications Channel (SDCC) in service.

This task can be performed using FLEXR or TL1.

Note: The EDIT-SDCC command only provisions the channel. The INIT-SDCC command is required to make it active.


Step 1 Retrieve the SDCC status.

a. From the Provisioning menu, choose Section DCC then choose SDCC Service State. The Service State dialog box opens.

b. Select an Access ID.

c. Click Retrieve to show the current SDCC setting. The possible settings are In Service or Out of Service. Is the channel in service?

If Yes: If No:

Click Cancel to close the dialog box.


Go to Step 2.



Step 2 Edit the SDCC status.

a. Select In Service.

b. Click OK.

c. Click Initialize.

d. Click Retrieve to verify that the command was successful.

e. Click Cancel to close the dialog box. Is the channel in service?

5.7.3 TL1 Procedure


Step 1 Retrieve the SDCC status by using the following TL1 command.

RTRV-SDCC:TID:AIDs:CTAG;

The possible settings are IS (In Service) and OOS (Out of Service). Is the channel in service?

Step 2 Edit the SDCC status by using the following TL1 command.

ED-SDCC:TID:AIDs:CTAG::::IS;

If Yes: If No:



If Yes: If No:


Go to Step 2.



Step 3 Place the SDCC in service by using the following TL1 command.

For tributary AIDs—

INIT-SDCC:TID:ALL:CTAG;

For high-speed AIDs—

Three-layer protocol: INIT-SDCC:TID:ALL:CTAG;

Seven-layer OSI protocol: INIT-OSSI:TID:ALL:CTAG;

Is the channel in service?

If Yes: If No:



5.8: Correcting a Mismounted UnitMaintenance and Trouble ClearingFJTU-320-515-480

5.8 Correcting a Mismounted Unit

5.8.1 Overview

A mismounted unit is indicated by a blinking red FAIL LED that denotes either of the following troubles:

• The slot is configured for a different type of unit.

• The mounted unit is not used in this configuration.

No alarm is generated by a mismounted unit.

To correct a mismounted unit, use the appropriate procedure presented below: FLEXR or TL1.


Step 1 Should the unit have been installed in another slot?

Step 2 Should a different unit have been installed in the slot?

If Yes: If No:

Move the unit to the correct slot.


Go to Step 2.

If Yes: If No:

Replace the incorrect unit with a correct unit.


Go to Step 3 to retrieve the current provisioning.



Step 3 Retrieve the Group Configuration to show how the slot is provisioned.

a. From the Provisioning menu, choose System, then choose Set Group Configuration. A dialog box opens.

b. Select Group Configuration.

c. Click Retrieve to show the current settings. The following configurations are possible:

- Groups 1 and 2—OC3, EC1, or OC12

- Group 3—D1, D3, EC1, or D1E

- Groups 4 and 5—D1, D3, EC1, D1E, OC3, F6-4WP, F6-7W, LAN, or D3U

Is the group provisioned correctly?

WARNING:The following action has the potential for dropping traffic if not done correctly!

Step 4 Delete any cross-connects that exist to/from the group.

a. From the Provisioning menu, choose Add/Drop.

b. Select Disconnect and the type of circuit to disconnect (1-Way, 2-Way, or Broadcast).

c. Click on each end of the circuit to be disconnected and repeat for each cross-connected circuit.

d. Click Send and check the resulting Confirmation box to verify that only connections to the appropriate Group are slated for disconnection. If accurate, click OK to make the disconnections.

e. Click on Close.

If Yes: If No:

Click Close.

Call the Technical Assistance Center at 1-800-USE-FTAC (1-800-873-3822) for assistance.

Go to Step 4.

Click Close.



Step 5 If any of the facilities in the applicable group are in service, place them out of service.

a. From the Provisioning menu, choose Service State, then choose Change Facility State.

b. Click the applicable units, then click on any nonselectable unit. A dialog box opens.

c. Select the appropriate Channel IDs. If low-speed units were selected, the dialog box shows Channel IDs. If high-speed units were selected, the dialog box does not show Channel IDs.

d. Select OOS Memory Admin.

e. Click OK.

f. Click Close or Cancel.

Step 6 Place the equipment slots for the group out of service.

a. From the Provisioning menu, choose Service State, then choose Change Equipment State.

b. Click the applicable units, then click on any nonselectable unit. A dialog box opens.

c. Select Out of Service (MA).

d. Click OK.

Step 7 Change the Group Configuration.

a. From the Provisioning menu, choose System then choose Set Group Configuration. The system dialog box opens.

b. Select Group Configuration.

c. Select the appropriate facility type for the group being modified.



Step 8 Has the mismount cleared?

Step 9 Place the equipment slots back in service.

a. From the Provisioning menu, choose Service State, then choose Change Equipment State.

b. Click the unit, then click on any nonselectable unit. A dialog box opens.

c. Select In Service.

d. Click OK.

Step 10 Place the facilities back in service.

a. From the Provisioning menu, choose Service State, then choose Change Facility State.

b. Click the unit, then click on any nonselectable unit. A dialog box opens.

c. Select the appropriate Channel IDs.

d. Select In Service.

e. Click OK.

f. Click Retrieve to verify that the command was completed.

g. Click Close or Cancel.

Step 11 Were any cross-connects deleted in Step 4 that must be reconnected?

If Yes: If No:


If Yes: If No:

Go to Step 12. You have completed this procedure.



Step 12 Restore the cross-connects that were removed in Step 4.

a. From the Provisioning menu, choose Add/Drop.

b. Select Connect and the type of circuit to connect (1-Way, 2-Way, or Broadcast).

c. Click on each end of the circuit to be connected and repeat for each circuit.

d. Click Send and check the resulting Confirmation box to verify that only connections to the appropriate Group are slated for connection. If accurate, click OK to make the connections.

e. Click on Close.

f. You have completed this procedure.

5.8.3 TL1 Procedure


Step 1 Should the unit have been installed in another slot?

Step 2 Should another unit have been installed in the slot as the slot was provisioned?

If Yes: If No:

Move the unit to the correct slot.


Go to Step 2.

If Yes: If No:

Replace the incorrect unit with a correct unit.


Go to Step 3.



Step 3 Retrieve the Group Configuration to show how the slot is provisioned.

RTRV-SYS:TID::CTAG;

Is the group provisioned correctly?

WARNING:The following action has the potential for dropping traffic if not done correctly!

Step 4 Delete any cross-connects that exist to/from the group. Repeat as necessary.

DLT-CRS-AIDTYPE:TID:from,to:CTAG::CCT;

where the AIDTYPE = VT1 or STS1 and CCT = 1WAY or 2WAY.

WARNING:Do not use CCT=1WAYBD with a DLT-CRS command, Your may inadvertently drop the “continue” portion of a “Drop and Continue” circuit. Use 1WAY instead.

Step 5 If any of the facilities in the applicable group are in service, place them out of service.

DLT-AIDTYPE:TID:AID:CTAG;

where the AIDTYPE = T1, T3, OC12, OC3, OVTG, EC1, ATMVC, LMP, LBP, or T3U.

Step 6 Place the equipment slots for the group out of service starting with the lower speed unit and progressing to the higher speed units.

DLT-EQPT:TID:AID:CTAG;

Step 7 Change the Group Configuration by using the following command.

ED-SYS:TID::CTAG:::CONFx-y

where x = appropriate group number and y = unit type.

If Yes: If No:


Go to Step 4.



Step 8 Has the mismount cleared?

Step 9 Place the equipment slots back in service starting with the higher speed unit and progressing to the lower speed units.

ENT-EQPT:TID:AID:CTAG;

Step 10 Place the facilities back in service.

ENT-AIDTYPE:TID:AID:CTAG;

where the AIDTYPE = T1, T3, OC12, OC3, OVTG, EC1, ATMVC, LMP, LBP, or EQPT.

Step 11 Were any cross-connects deleted in Step 4 that must be reconnected?

Step 12 Restore the cross-connects deleted in Step 4. Repeat as necessary.

ENT-CRS-AIDTYPE:TID:from,to:CTAG::CCT;

where the AIDTYPE = VT1 or STS1 and CCT = 1WAY or 2WAY.


If Yes: If No:


If Yes: If No:

Go to Step 12. You have completed this procedure.



1: Trouble Analysis Log FormsAppendix A

Appendix A Trouble Analysis Log

1 Trouble Analysis Log Forms

Date:

Time:

System Generating Trouble Indication::

Current Alarm and Status Conditions Time Cleared

Issue 9, May 1999 FNC and FNC Customer Use Only Vol. ll, Page 480.A-1

1: Trouble Analysis Log FormsAppendix A

PRELIMINARY–Monday, May 17, 1999 8:06 am


Alarm Clearing Procedures

Alarm

Probable Cause

Procedures Performed

Time Alarm Cleared


Alarm

Probable Cause


Time Alarm Cleared


Alarm

Probable Cause


Time Alarm Cleared


Alarm

Probable Cause


Time Alarm Cleared


Alarm

Probable Cause


Time Alarm Cleared

Issue 9, May 1999 FNC and FNC Customer Use Only Vol. ll, Page 480.A-2

maintenance and trouble clearing - alarmspecs.comebay.alarmspecs.com/flm150adm/150480p.pdf ·...

Documents