maintenance and trouble clearing - launch 3 telecom · 2014-08-04 · issue 7, may 1999 fnc and fnc...
TRANSCRIPT
T
FLM 2400 ADMPractice FJTU-320-560-480
ask Oriented Practice(TOP)
TEDD-Document-3.0
FUJITSU NETWORK COMMUNICATIONS, INC.FJTU-320-XXX-XXX
ISSUE 7, MAY 1999
MAINTENANCE AND TROUBLE CLEARING
Unpublished work and only distributed under restriction. Copyright © Fujitsu Network Communications, Inc. All Rights Reserved.
Proprietary Rights Notice
FACTR, FLEXR, and FLEXR Plus are registered trademarks of Fujitsu Network Communications, Inc. (FNC).Portions of FLEXR Plus are copyrighted by Illustra Information Technologies, Inc.
FASTLANE, FLASH, FLASHWAVE, NETSMART, and SPEEDPORT are trademarks of FNC.
All other products or services mentioned in this document are identified by the trademarks, service marks, or product names as designated by the companies that market those products or services or own those marks. Inquiries concerning such products, services, or marks should be made directly to those companies.
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 Confidential and is for use by FNC authorized recipients only.
FNC and FNC Customer Use Only
Maintenance and Trouble ClearingFJTU-320-560-480
This notice lists the reasons for, location of, and a description of practice changes. When the changes are extensive, a general statement giving the nature of the revisions is provided.
Document Change Notice Issue
Location of Change Description of Change
Reason For Document Change: Release 14.2
Section 4 Added condition tables for IPNOTREACH, IPREACHABLE, and PINGTIMEOUT.
Section 6 Added information about new issue of the MC6A unit to sections 6.18 and 6.28.
Issue 7, May 1999 FNC and FNC Customer Use Only
Maintenance and Trouble ClearingFJTU-320-560-480
FNC and FNC Customer Use Only
This page intentionally left blank.
Anti-electrostatic Markings
ATTENTION
DANGER
Invisible laser radiation from
connectors when
uncoupled AVOID DIRECT
EXPOSURE TO BEAM
Laser Radiation Label
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.
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.
OBSERVE PRECAUTIONS
FOR HANDLING
ELECTROSTATIC
SENSITIVE
DEVICE
FNC and FNC Customer Use Only
Maintenance and Trouble ClearingFJTU-320-560-480
Task Index List
Task Index List
Page
CHAPTERS
1 Maintaining Equipment
1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
1.2 Reason for Reissue. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
1.3 Alarm/Status Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
1.4 Message Parameter Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
1.5 Maintenance Philosophy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
1.6 Repairing Defective Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15
2 LED Indications
2.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
3 Error Codes
3.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
3.2 Error Code Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
3.3 Equipage Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
3.4 Input Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
3.5 Privilege Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
3.6 Status Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
4 Responding to Alarms and Conditions
4.1 Condition Code Responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.2 Response Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
4.3 Condition Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
5 Unit and Connector Locations
5.1 High-Speed and Tributary Shelf Front and Back Views. . . . . . . . . . . . . . . . . 5-1
Issue 7, May 1999 FNC and FNC Customer Use Only i
Page
Task Index List Maintenance and Trouble ClearingFJTU-320-560-480
6 Replacing Units
6.1 Removing and Installing Optical Channel Units . . . . . . . . . . . . . . . . . . . . . . 6-1
6.2 Removing and Installing Electrical Plug-In Units . . . . . . . . . . . . . . . . . . . . . 6-5
6.3 Replacing and Maintaining the Fan Shelf Filter. . . . . . . . . . . . . . . . . . . . . . . 6-9
6.4 Replacing Power (PW2H-HS) Unit in the HS Shelf . . . . . . . . . . . . . . . . . . . 6-11
6.5 Replacing the Microprocessor (MP2H-xxx) Unit in the HS Shelf. . . . . . . . . 6-14
6.6 Replacing Supervisory (SV2H-T11/-T12/-B1/-DL/-DLB) Unit in the HS Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18
6.7 Replacing the High-Speed Switch (HS2H-xxxx) Unit in the HS Shelf. . . . . 6-23
6.8 Replacing the Alarm and Orderwire Alarm (AW2H-A1/-A2) Unit in the HS Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-31
6.9 Replacing the High-Speed Multiplexer (HM2H-xx) Unit in the HS Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-34
6.10 Replacing the High-Speed Transmit Channel (HT2H-xxxx) Unit in the HS Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-42
6.11 Replacing High-Speed Receive Channel (HR2H-xxxx) Unit in the HS Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-45
6.12 Replacing Power Unit (PW1A/PW1A-TRIB) Unit in the HD TRIB Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-48
6.13 Replacing Microprocessor (MP2T-T11/-T12/-DL) Unit in the HD TRIB Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-51
6.14 Replacing Middle-Speed Switch for DS3/STS-1 (MS2T-D31) Unit in the HD TRIB Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-53
6.15 Replacing High-Speed Switch (HS2T-xxxx) Unit in the HD TRIB Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-55
6.16 Replacing High-Speed Channel (HC2T-MDL/-C12L) Unit in the HD TRIB Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-61
6.17 Replacing Optical Middle-Speed Interface (MC6A-2Lxx) Unit in the HD TRIB Shelf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-65
6.18 Replacing Optical Middle-Speed Interface (MC6A-31xx) Unit in the HD TRIB Shelf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-67
6.19 Replacing Middle-Speed Channel Clock Distribution (MC6A-2THR) Unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-72
6.20 Replacing Middle-Speed Channel OC-3 Bridge (MC6A-3BRD) Unit in the HD TRIB Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-74
6.21 Replacing DS3/EC-1 Interface (MC6A-D3/-D3E2/-ST1E/-ST1P) Unit in the HD TRIB Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-77
ii FNC and FNC Customer Use Only Issue 7, May 1999
Page
Maintenance and Trouble ClearingFJTU-320-560-480
Task Index List
6.22 Replacing Power (PW6A) Unit in the FLM 600 ADM TRIB Shelf . . . . . . . . 6-82
6.23 Replacing Microprocessor (MP6A-24G/-24DL) Unit in the FLM 600 ADM TRIB Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-86
6.24 Replacing Supervisory Interface (SV6A-24G/-TDL1) Unit in the FLM 600 ADM TRIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-89
6.25 Replacing Alarm and Orderwire (AW6A-BSC/-ENH) Unit in the FLM 600 ADM TRIB Shelf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-92
6.26 Replacing High-Speed Switch (HS6A-AD1/-AD2) Unit in the FLM 600 ADM TRIB Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-95
6.27 Replacing Middle-Speed Optical Switch Control (MS6A-OPT/-OPT2) Unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-97
6.28 Replacing Optical Channel (HC6A-xxxx/MC6A-xxxx) Unit in the FLM 600 ADM TRIB Shelf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-99
6.29 Replacing HS Electrical Interface (HC6A-6EL1/-6EL2) Units in the FLM 600 ADM TRIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-104
6.30 Replacing Electrical Channel (MC6A-D3/-D3A2/-STS1/-ST1E/-ST1P) Unit in the FLM 600 ADM TRIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-108
6.31 Replacing Timing Control Access (TCA/TCA-ENH) Unit in the FLM 600 ADM TRIB Shelf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-116
6.32 Replacing Embedded Channel (EC6A-24G/-DL1) Unit in the FLM 600 ADM TRIB Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-120
7 General Procedures
7.1 Handling the Fiber Cables Correctly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
7.2 Cleaning the Optical Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
7.3 Connect/Disconnect Optical Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10
7.4 Measuring the Optical Transmit Unit Output Power . . . . . . . . . . . . . . . . . . 7-15
7.5 Measuring the Optical Receive Unit Input Power. . . . . . . . . . . . . . . . . . . . . 7-19
7.6 Verifying the External Clock and Connections . . . . . . . . . . . . . . . . . . . . . . . 7-23
7.7 Verifying the T3 Framing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-25
7.8 Changing Unidirectional/Bidirectional Switching. . . . . . . . . . . . . . . . . . . . . 7-26
7.9 Changing the SDCC Service State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-28
7.10 Removing and Installing Front Covers on the HS and HD TRIB Shelves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-30
Issue 7, May 1999 FNC and FNC Customer Use Only iii
Page
Task Index List Maintenance and Trouble ClearingFJTU-320-560-480
APPENDIXES
A Trouble Analysis Log
B Recommended Test Equipment
B.1 Test and Turn-Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
B.2 Fiber Breaks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
B.3 General Maintenance and Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
iv FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
Chapter 1: Maintaining Equipment
CHAPTER 1
1 Maintaining Equipment
1.1 Overview
This practice provides information and procedures used for the FLM 2400 ADM system maintenance and trouble clearing. The following topics are included.
• Section 1 provides a procedure to identify alarm and status conditions, and definitions of message parameters, maintenance philosophy, and plug-in unit repair.
• Section 2 lists the LED indicators and gives their meanings.
• Section 3 lists the error codes that are returned when a command cannot be completed and possible causes and suggested corrective actions for each.
• Section 4 lists all alarm/status conditions and possible causes and suggested corrective actions for each.
• Section 5 provides front and rear views of the system to show connector and unit locations.
• Section 6 provides procedures for plug-in unit replacement.
• Section 7 covers general procedures such as optic fiber handling and cleaning, optic power measurements, and provisioning changes related to trouble clearing.
• Appendix A provides a Trouble Analysis Log form.
• Appendix B provides diagrams of the equipment and facility service state models.
Issue 7, May 1999 FNC and FNC Customer Use Only Page 1-1
1.2: Reason for Reissue Maintenance and Trouble ClearingFJTU-320-560-480
1.2 Reason for Reissue
This practice has been revised to add the MP2H-DLB and SV2H-DLB unit. Minor reformatting and corrections were included for consistency.
Page 1-2 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
1.3: Alarm/Status Identification
1.3 Alarm/Status Identification
1.3.1 Summary
This procedure provides the steps to identify alarms conditions indicated by the FLM 2400 ADM. Once the technician receives a visible or audible alarm, alarm and status messages retrieved through the operations support system (OSS) or craft interface help isolate the cause of the trouble.
Note: Fujitsu recommends that all FLM 2400 ADM equipment be connected to form operation and maintenance networks. These networks should be connected to an interface device (craft interface, OSS, Network Monitoring and Administration (NMA), etc.) at all times. This procedure assumes that an interface device is connected to the network and operating correctly.
Note: Fujitsu recommends that operations and maintenance personnel keep records of all alarm and trouble indications and of the steps taken to clear them.
1.3.2 Procedure
Step 1 Determine if the alarm condition is located at the near- or far-end equipment.
a. Ensure that the MP2H unit is displaying a decimal point (.) which indicates that the alarm display on the AW2H unit shows a near-end (this shelf) condition. If necessary, momentarily press the FE SEL button on the MP2H unit until the decimal appears in the display. This should coincide with the NE ACT indication on the AW2H unit.
b. Check the NE ACT and FE ACT LEDs on the AW2H unit. The NE ACT LED is lit for a near-end alarm, while the FE ACT LED is lit for a far-end alarm. Treat near-end conditions first. If the FE ACT LED is lit, the number shown on the MP2H unit display identifies the remote shelf that has the alarm/status conditions displayed by the AW2H unit.
c. Record the alarm severity displayed on the AW2H unit (Critical [CR], Major [MJ], Minor [MN]) in the trouble log.
d. If the FE ACT LED is lit, read the identity of the far-end node on the EQPT NO. display. Record the alarm severity displayed on the AW2H unit for that node in the trouble log. If necessary, repeat this procedure for each remote node addressee using the FE SEL function.
Issue 7, May 1999 FNC and FNC Customer Use Only Page 1-3
1.3: Alarm/Status Identification Maintenance and Trouble ClearingFJTU-320-560-480
Step 2 Log on the system that is originating the alarm.
Step 3 Retrieve all current alarms. Record them in the trouble log.
Step 4 If more information is desired, retrieve the standing conditions. Record them in the trouble log.
TL1 FLEXR 7.61
Press CTRL + X (The ACS LED lights on the SV2H 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 setup)
Type System ID: FUJITSU
Type user name: ROOT
Type password: ROOT
Click OK
Note: Repeat for other TIDs.
TL1 FLEXR 7.61
RTRV-ALM-ALL:TID::CTAG; Click once in the Alarm window
Exit
TL1 FLEXR 7.61
RTRV-COND-ALL:TID::CTAG; > Status/Control
> Shelf Condition
> Retrieve Shelf Condition
Click Exit to close the Shelf Condition Log report
Page 1-4 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
1.3: Alarm/Status Identification
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, which stores up to 500 of the most recent messages. 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.)
Step 6 Determine which current alarm has the greatest service effect. List that alarm in the first available section of the Trouble Analysis Log shown in Appendix A of this practice.
Step 7 Clear Critical (service-affecting) alarms first, followed by any other service-affecting alarms. Then clear any remaining Major (non–service-affecting [NSA]) alarms, followed by any Minor alarms.
Step 8 Use the following information to help isolate the causes of alarms:
a. Go to Section 4, Responding to Alarms and Conditions, to find the probable causes and suggested corrective actions. List the probable causes in the trouble log.
b. If using the LEDs, refer to Section 2, LED Indications, for additional information to interpret the LED indications.
c. Check the Trouble Analysis Log, shown in Appendix A of this practice, to determine if a similar condition has occurred. Consider resolving the current alarm in the same manner.
TL1 FLEXR 7.61
RTRV-AO:TID:AIDs:CTAG:::KEYWORD=DOMAIN;
AID Values
1~500
null (500)
KEYWORD = DOMAIN
ATAGSEQ = 0~999999 (may use &, &&)
MSGTYPE = ALM/EVT/PM/DBCHG
ORDER = INCR/DECR
(Defaults shown in bold)
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 Access ID Range or ATAGSEQ
Type the applicable data
Click OK to exit
Issue 7, May 1999 FNC and FNC Customer Use Only Page 1-5
1.3: Alarm/Status Identification Maintenance and Trouble ClearingFJTU-320-560-480
Step 9 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 4, Responding to Alarms and Conditions, to find the probable causes and suggested corrective actions. List the probable causes in the trouble log.
Step 10 Use the procedures recommended in Section 4, Responding to Alarms and Conditions, to correct the trouble condition. Did the alarm or status condition clear?
Step 11 Retrieve all current alarms.
Step 12 Have all alarm conditions in the system cleared?
Step 13 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. Repeat Steps 6 through 13.
You have completed this task.
If yes: If no:
Record the time in the Time Cleared column of your form and continue with Step 11.
Call Fujitsu at 1-800-USE-FTAC (1-800-873-3822).
TL1 FLEXR 7.61
RTRV-ALM-ALL:TID::CTAG; Click once in the Alarm window
Exit
If yes: If no:
You have completed this procedure. Call Fujitsu at 1-800-USE-FTAC (1-800-873-3822).
Page 1-6 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
1.4: Message Parameter Definitions
1.4 Message Parameter Definitions
This section provides definitions of message fields or parameters for alarms, transient conditions, 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.4.1 Interpreting Messages
Autonomous messages are reported by the FLM 2400 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 whenever an event is triggered, provided the condition is not provisioned as NR (no report) or its message category is not currently inhibited.
1.4.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 can be limited to specific message categories (ALM, EVT, PM, DBCHG) and specific sequences.
1.4.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 following format and example are for a report retrieved using RTRV-AO.
TID DATE TIMEALMCDE ATAG REPT ALM AIDTYPE “AID:NTFCNCDE,CONDTYPE, SRVEFF,,,LOCN,DIRN,,,:\”COND DESCR\””
Issue 7, May 1999 FNC and FNC Customer Use Only Page 1-7
1.4: Message Parameter Definitions Maintenance and Trouble ClearingFJTU-320-560-480
Example: FUJITSU 95-12-23 20:43:44 *C 000003 REPT ALM EQPT "TS1A-W:CR,RMVD,SA,,,NEND,NA,,,: \"Unit is removed\""
The format for a report retrieved using RTRV-ALM-ALL or RTRV-COND-ALL is shown below, followed by an example.
"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 of a report retrieved using RTRV-AO is as follows.
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 following format and example are for a report retrieved using RTRV-ALM-ENV.
“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 non-alarmed event that is reported will generate a separate autonomous message. The only REPT EVT messages for software download (SWDL) concern transient conditions.
The following shows the format and an example message for an event report retrieved using RTRV-AO.
Page 1-8 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
1.4: Message Parameter Definitions
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 format for a report retrieved using RTRV-ALM-ALL or RTRV-COND-ALL is shown below, followed by an example.
"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 message are for a performance monitoring 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 message 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 report are for a database change report retrieved using RTRV-AO.
Issue 7, May 1999 FNC and FNC Customer Use Only Page 1-9
1.4: Message Parameter Definitions Maintenance and Trouble ClearingFJTU-320-560-480
TID DATE TIME A ATAG REPT DBCHG "UPDATE MANAGEMENT BLOCK:COMMAND CODE: AIDs:DATA BLOCK"
UPDATE MANAGEMENT BLOCK: SOURCE=CTAGDATA BLOCK: PARAMETERS
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.4.4 Report Parameters
Table 1-1 lists and defines each of the report parameters.
Table 1-1: Autonomous and Retrieved Report Parameters
Parameter Definition
AID Access identifier identifies 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 Access identifier type specifies whether AID applies to equipment, com, 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. The 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. The ALMTYPEs are limited to 10 ASCII characters.
ATAG 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.
Page 1-10 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
1.4: Message Parameter Definitions
CONDDESCR Condition description is 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 Condition type is the alarm, transient condition, or standing condition that generated the message. An example valid value is CPY-FILE-PRTL for REPT EVT FILE.
CTAG Correlation Tag is used to correlate user input requests and system output responses. CTAG is one to six alphanumeric characters.
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 (time period). The format for month of the year ranges (1 to 12) and the day of the month (1 to 31); for example, 0-30. The TMPER is 1-DAY, MONTM null.
MONTM Monitoring time is the beginning time of the day of the storage register period specified in TMPER. The format for MONTM is the hour of day (0 to 23) and the minute of the hour (0, 15, 30, and 45); for example, 0-30. If TMPER is 1-DAY, MONTM is null.
MONTYPE Monitoring type is the type of the parameter being reported.
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.)
Parameter Definition
Issue 7, May 1999 FNC and FNC Customer Use Only Page 1-11
1.4: Message Parameter Definitions Maintenance and Trouble ClearingFJTU-320-560-480
NTFCNCDE Notification code (factory default value) 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. CL is only used to identify the message that indicates that a previously reported alarm has cleared.
REPT TYPE Four types of autonomous messages can be reported by the system, as shown below:
REPT ALM—Report alarm
REPT EVT—Report event
REPT PM—Report performance monitoring
REPT DBCHG—Report database change.
SID Source identifier is a unique name given to each system when it is installed in the network. This name identifies the particular NE that is the source of the message.
SRVEFF Service effect; SA is for service affecting; NSA for non-service affecting.
THLEV Identifies the magnitude of monitored parameter that when crossed will generate a threshold crossing message.
TID Target identifier is a unique name given to each system when it is installed in the network. 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 MANAGEMENTBLOCK
Identifies the CTAG (correlation tag) of the TL1 command that modified the database.
VLDTY Validity of PM interval: TRUE or FALSE.
Table 1-1: Autonomous and Retrieved Report Parameters (Cont.)
Parameter Definition
Page 1-12 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
1.5: Maintenance Philosophy
1.5 Maintenance Philosophy
1.5.1 General
During normal operation, the FLM 2400 ADM is designed to require virtually no maintenance intervention on your part. Under equipment or line failure conditions, the self-diagnostic features of the FLM 2400 ADM quickly identify the faulty unit or line in the system. This practice describes the procedures that should be used to maintain and troubleshoot the FLM 2400 ADM. The practice is organized in the task-oriented practice (TOP) format so that trouble-clearing procedures can be quickly identified and implemented.
1.5.2 Periodic Maintenance Requirements
The FLM 2400 ADM requires periodic replacement of the fan unit filter (Section 6.3, Replacing and Maintaining the Fan Shelf Filter). This maintenance does not affect customer traffic or interfere with normal equipment operation.
1.5.3 Alarm and Status
The FLM 2400 ADM system provides built-in test features to monitor both internal circuitry and input/output facilities. Redundant channel units, synchronization units, switching units, and power supplies support critical data paths within the system. Relays to office alarm systems and status indicators on module front panels provide maintenance personnel with visual and audible information. In addition, any abnormal or trouble condition triggers appropriate alarm and status messages. These messages are automatically reported to any interface device (craft interface, OSS, NMA) that is currently logged on the affected system. These messages can be retrieved by logging on to the system and performing an alarm retrieval command.
The FLM 2400 ADM also provides Critical (CR), Major (MJ), and Minor (MN) alarms to the office. When troubles occur, they trigger near end (NE) office alarms. The self-diagnostic feature of the FLM 2400 ADM identifies any failure of the faulty unit or line system. These failures are indicated by the FAIL, FAIL/SVCE, or LINE LED located on each unit.
Section 2, LED Indications, lists the condition types depicted by the LED indications on the plug-in units.
Issue 7, May 1999 FNC and FNC Customer Use Only Page 1-13
1.5: Maintenance Philosophy Maintenance and Trouble ClearingFJTU-320-560-480
1.5.4 Trouble Analysis Procedures
The incidence of hardware malfunction in a computerized multiplexer is normally very low. This is especially true of a fully protected FLM 2400 ADM system. When alarm indications are received, you must first identify the specific shelf originating the alarm and retrieve all current alarm and status messages. The following assumptions are made in this practice:
• All FLM 2400 ADM Shelves in a network are properly equipped.
• Multiple trouble indications may have a single cause.
• Only a single failure exists.
Section 4.2, Response Procedure, provides trouble-clearing information. After you have retrieved the alarm message, this document enables you to isolate the fault and take corrective action.
Occasionally, trouble clearing requires replacing plug-in units. The sections in this practice show you how to replace the units. If the alarm does not clear after the replacement unit is installed, the original plug-in unit should be returned to operation.
Page 1-14 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
1.6: Repairing Defective Units
1.6 Repairing Defective Units
Field repair of defective units is not recommended. Equipment failures should be corrected by replacing the defective unit with a working spare. Defective units should be sent to a Fujitsu field service office. Units under warranty will be repaired and returned or replaced with new or refurbished units. Equipment out of warranty will be evaluated to determine the repair cost and date of delivery. The customer will then be notified and a request will be made for authorization to proceed with repairs. Fujitsu also offers a fixed-priced repair and exchange service. Information about the defective units can be furnished informally by either mail or telephone. In any correspondence, include the following information:
• Unit part number and serial number
• Brief description of failure symptoms
• Original purchase order number covering the unit
• Return shipping address
• Preference in shipping mode
• Invoice
• Name and phone number of person to be contacted for further information
Returned units should be properly packed to prevent damage during shipment. Fujitsu is not liable for damage encountered during shipment.
Issue 7, May 1999 FNC and FNC Customer Use Only Page 1-15
1.6: Repairing Defective Units Maintenance and Trouble ClearingFJTU-320-560-480
Page 1-16 FNC and FNC Customer Use Only Issue 7, May 1999
This page intentionally left blank.
Maintenance and Trouble ClearingFJTU-320-560-480
Chapter 2: LED Indications
CHAPTER 2
2 LED Indications
2.1 Overview
This document lists alarm and status descriptions shown by the LEDs on the plug-in units. Tables 2-1 through 2-21 show the LED indications for the following shelves:
• The FLM 2400 ADM High-Speed (HS) Shelf
• The FLM 2400 ADM High-Density Tributary (HD TRIB) Shelf.
Note: Alarm and status information for the FLM 600 ADM Tributary Shelf is located in Section 2, Plug-in Unit Front-Panel Devices, in the Maintenance and Trouble Clearing practice, FJTU-320-545-480, of the FLM 600 ADM documentation.
To perform related trouble-clearing tasks, refer to the following documents in this practice:
• To retrieve an alarm—Refer to Section 1.4.2, Message Retrieval, to retrieve and interpret fault data.
• To clear troubles—Find the alarm message, listed in alphabetical order in the Task Index List of this practice, and perform the corrective action indicated.
• To replace a unit—Refer to the Task Index List to select the appropriate unit replacement procedure.
Table 2-1: AW2H-A1/-A2/ LED Descriptions
LED Color Meaning
CR Red A critical (service-affecting) alarm exists on or has been detected by the local network element (NE).
Off Normal operation (in service).
MJ Red A major (service-affecting) alarm exists on or has been detected by the local NE.
Off Normal operation (in service).
Issue 7, May 1999 FNC and FNC Customer Use Only Page 2-1
Chapter 2: Overview Maintenance and Trouble ClearingFJTU-320-560-480
MN Yellow A minor (non–service-affecting) alarm exists on or has been detected by the local NE.
Off Normal operation (in service).
ABN Yellow An abnormal condition, such as a forced switch or loopback, has been initiated by a user.
Off Normal operation (in service).
ACO Green An alarm cutoff has been activated.
CALL
(AW2H-A2)
(AW6A-ENH)
Green Lights green for 90 seconds when this station is called by another station.
Table 2-2: Fan Shelf LED Descriptions
LED Color Meaning
PWR Red An internal failure. Refer to the Plug-In Unit Installation practice, FJTU-320-560-220, Section 7, Fan Installation Procedures.
Green Normal operation (in service).
Off No power to the shelf.
FAN ON Green The Fan Shelf equipment is turned on.
Off No power to the shelf.
FAIL Red An internal failure or a fuse has blown. If the Fan Shelf has failed, refer to the Plug-In Unit Installation practice, FJTU-320-560-220, Section 7.1, Installing Fan Unit in the Fan Shelf.
Yellow Diode temperature problem.
Off Normal operation (in service).
Table 2-1: AW2H-A1/-A2/ LED Descriptions (Cont.)
LED Color Meaning
Page 2-2 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
Chapter 2: Overview
Table 2-3: HC2T-C12L/-MDL LED Descriptions
LED Color Meaning
FAIL/SVCE Red An internal failure. Refer to Section 6.16, Replacing High-Speed Channel (HC2T-MDL/-C12L) Unit in the HD TRIB Shelf.
Blinking red Unit mismount; the system is configured for a different mode or the mounted unit is not used in this configuration.
Green Normal operation (in service).
Off Out of service.
LINE Red A loss of pointer has been detected on an incoming line.
Off Normal operation (in service).
Table 2-4: HM2H-A1/-A2/-A3/-B1/-C1 LED Descriptions
LED Color Meaning
FAIL/SVCE Red An internal failure, a blown fuse, or the internal clock or building integrated timing supply (BITS) output is down. Refer to Section 6.9, Replacing the High-Speed Multiplexer (HM2H-xx) Unit in the HS Shelf.
Blinking red Unit mismount; the system is configured for a different mode or the mounted unit is not used in this configuration.
Green Normal operation (in service).
Off Standby or out of service.
LINE Red An incoming alarm indication signal (AIS) or loss of signal (LOS) on the DS1 clock inputs(HM2H-A1/-B1 only).
Yellow An incoming path AIS condition has been detected (HM2H-B1 only).
Off Normal operation (in service).
Issue 7, May 1999 FNC and FNC Customer Use Only Page 2-3
Chapter 2: Overview Maintenance and Trouble ClearingFJTU-320-560-480
Table 2-5: HR2H-xxxx LED Descriptions
LED Color Meaning
FAIL/SVCE Red An internal failure, or a blown fuse. Refer to Section 6.11, Replacing High-Speed Receive Channel (HR2H-xxxx) Unit in the HS Shelf.
Blinking red Unit mismount; the system is configured for a different mode or the mounted unit is not used in this configuration.
Green Normal operation (in service).
Off Standby or out of service.
LINE Red An OC-48 signal has degraded or failed.
Yellow Indicates an AIS or remote failure indication (RFI).
Off Normal operation (in service).
Table 2-6: HS2H-ADM1/-A2DL/-U1 LED Descriptions
LED Color Meaning
FAIL Red An internal failure. Refer to Section 6.7, Replacing the High-Speed Switch (HS2H-xxxx) Unit in the HS Shelf.
Blinking red Unit mismount; the system is configured for a different mode or the mounted unit is not used in this configuration.
Off Normal operation (in service).
LINE Red An incoming line failure.
Off Normal operation (in service).
FORCE Green Forced manual control or a forced manual switch has been performed.
Off Normal operation (in service).
AUTO Green Automatic switching is in effect (normal operation).
Off Normal operation (in service).
MNL Green Manual control, a manual switch has been performed.
Off Normal operation (in service).
Page 2-4 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
Chapter 2: Overview
Table 2-7: HS2H-B1/-B1DL LED Descriptions
LED Color Meaning
FAIL Red An internal failure. Refer to Section 6.7, Replacing the High-Speed Switch (HS2H-xxxx) Unit in the HS Shelf.
Blinking red Unit mismount; the system is configured for a different mode or the mounted unit is not used in this configuration.
Off Normal operation (in service).
LINE Red An incoming line failure (automatic protection switching [APS]). Node ID mismatch, Auto-Provisioning.
Off Normal operation (in service).
RINGST Yellow A switch (MANUAL or AUTOMATIC and FORCED) has been performed at this node.
Off This LED will be turned OFF when a switch has been dropped or lockout of protection has been cleared.
AUTO Green Automatic switching is in effect (normal operation). The node is in the IDLE or PASS-THRU state.
Off FRCD (forced) or MAN (manual) mode.
MANU Green A manual switch has been performed.
Off AUTO or FRCD mode.
FRCE Green A forced switch has been performed.
Off AUTO or MAN mode.
Table 2-8: HS2H-REG/-RNG/-RNG2 LED Descriptions
LED Color Meaning
FAIL Red An internal failure. Refer to Section 6.7, Replacing the High-Speed Switch (HS2H-xxxx) Unit in the HS Shelf.
Blinking red Unit mismount; the system is configured for a different mode or the mounted unit is not used in this configuration.
Off Normal operation (in service).
Issue 7, May 1999 FNC and FNC Customer Use Only Page 2-5
Chapter 2: Overview Maintenance and Trouble ClearingFJTU-320-560-480
Table 2-9: HS2T-C3/-C3DL/-C3D2/-S1/-SDL/-SDL2 LED Descriptions
LED Color Meaning
FAIL Red An internal failure. Refer to Section 6.15, Replacing High-Speed Switch (HS2T-xxxx) Unit in the HD TRIB Shelf.
Blinking red Unit mismount; the system is configured for a different mode or the mounted unit is not used in this configuration.
Off Normal operation (in service).
LINE Red A section data communications channel (SDCC) failure on the incoming line.
Off Normal operation (in service).
Table 2-10: HS2T-D3 LED Descriptions
LED Color Meaning
FAIL Blinking red Unit mismount; the system is configured for a different mode or the mounted unit is not used in this configuration.
Off Normal operation (in service).
Table 2-11: HT2H-xxxx LED Descriptions
LED Color Meaning
FAIL/SVCE Red An internal failure. Refer to Section 6.10, Replacing the High-Speed Transmit Channel (HT2H-xxxx) Unit in the HS Shelf.
Blinking red Unit mismount; the system is configured for a different mode or the mounted unit is not used in this configuration.
Green Normal operation (in service).
Yellow LD CUR, LD TEMP ALM are detected.
Off Standby or Out of Service.
Page 2-6 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
Chapter 2: Overview
Table 2-12: MC6A-2Lxx/-31xx LED Descriptions
LED Color Meaning
FAIL Red An internal failure.
Refer to Section 6.17, Replacing Optical Middle-Speed Interface (MC6A-2Lxx) Unit in the HD TRIB Shelf.
Refer to Section 6.18, Replacing Optical Middle-Speed Interface (MC6A-31xx) Unit in the HD TRIB Shelf.
Blinking red Unit mismount; the system is configured for a different mode or the mounted unit is not used in this configuration.
Off Normal operation (in service).
LINE Red The incoming OC-3 or OC-12 signal has degraded or failed (such as an LOS, OOF [out of frame], BERSDP [bit error rate signal degrade-path], or BERSFP [bit error rate signal failure-path]) on one path.
Yellow One or multiple path level conditions exist. Possible conditions include a BERSDP, BERSFP, AIS, RDI, or unequipped code (UNEQ).
Off Normal operation (in service).
SEND Green The unit is transmitting and operating normally.
Off The unit is on standby or is Out of Service.
RCV Green The unit is receiving and operating normally.
Off The unit is on standby or is Out of Service.
Table 2-13: MC6A-2THR LED Descriptions
LED Color Meaning
FAIL Red An internal failure. Refer to Section 6.19, Replacing Middle-Speed Channel Clock Distribution (MC6A-2THR) Unit.
Blinking red Unit mismount; the system is configured for a different mode or the mounted unit is not used in this configuration.
Off Normal operation (in service).
Issue 7, May 1999 FNC and FNC Customer Use Only Page 2-7
Chapter 2: Overview Maintenance and Trouble ClearingFJTU-320-560-480
Table 2-14: MC6A-3BRD LED Descriptions
LED Color Meaning
FAIL/SVCE Red An internal failure. Refer to Section 6.20, Replacing Middle-Speed Channel OC-3 Bridge (MC6A-3BRD) Unit in the HD TRIB Shelf.
Blinking red Unit mismount; the system is configured for a different mode or the mounted unit is not used in this configuration.
Green Normal operation (in service).
Off Standby or Out of Service.
Table 2-15: MC6A-D3E/-D3E2 LED Descriptions
LED Color Meaning
FAIL/SVCE Red An internal failure. Refer to Section 6.21, Replacing DS3/EC-1 Interface (MC6A-D3/ -D3E2/-ST1E/-ST1P) Unit in the HD TRIB Shelf.
Blinking red Unit mismount; the system is configured for a different mode or the mounted unit is not used in this configuration.
Green Normal operation (in service).
Off Standby or Out of Service.
LINE 1/ 2/ 3 Red An incoming line 1/2/3 failure, or a service-affecting alarm (such as an LOS, OOF, BERSDP, or BERSFP) on both received STS-1 drops.
Yellow A non–service-affecting AIS signal or RFI (MC6A-D3 and MC6A-D3A), or an AIS, RFI, BERSDP, BERSFP, or UNEQ (MC6A-D3A2 and MC6A-D3E2) has been received on a high-speed -H1 or -H2.
Off Normal operation (in service).
Page 2-8 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
Chapter 2: Overview
Table 2-16: MC6A-ST1E/-ST1P LED Descriptions
LED Color Meaning
FAIL/SVCE Red An internal failure. Refer to Section 6.21, Replacing DS3/EC-1 Interface (MC6A-D3/ -D3E2/-ST1E/-ST1P) Unit in the HD TRIB Shelf.
Blinking red Unit mismount; the system is configured for a different mode or the mounted unit is not used in this configuration.
Green Normal operation (in service).
Off Standby or out of service.
LINE 1/2/3 Red An incoming line 1/2/3 failure or a service-affecting alarm (such as an LOS, LOF [loss of frame], and LOP [loss of path]) on both received STS-1 drops.
Yellow One or multiple STS-1 path level conditions exist, such as AIS, RFI, or UNEQ.
Off Normal operation (in service).
Table 2-17: MP2H-B1/-DL/-DLB/-DLS/-SLV/-T11/-T12 LED Descriptions
LED Color Meaning
FAIL Red An internal central processing unit (CPU) failure. Refer to Section 1.4.2, Message Retrieval, and Section 6.5, Replacing the Microprocessor (MP2H-xxx) Unit in the HS Shelf.
Blinking red Unit mismount; the system is configured for a different mode or the mounted unit is not used in this configuration.
Off Normal operation (in service).
Table 2-18: MP2T-DL/-T11/-T12 LED Descriptions
LED Color Meaning
FAIL Red An internal CPU failure. Refer to Section 6.13, Replacing Microprocessor (MP2T-T11/-T12/-DL) Unit in the HD TRIB Shelf.
Blinking red Unit mismount; the system is configured for a different mode or the mounted unit is not used in this configuration.
Off Normal operation (in service).
Issue 7, May 1999 FNC and FNC Customer Use Only Page 2-9
Chapter 2: Overview Maintenance and Trouble ClearingFJTU-320-560-480
Table 2-19: PW1A, PW1A-TRIB LED Descriptions
LED Color Meaning
PWR Red A tripped circuit breaker or a unit failure. Refer to Section 6.12, Replacing Power Unit (PW1A/PW1A-TRIB) Unit in the HD TRIB Shelf.
Green Normal operation (in service).
Off No power to the unit.
Table 2-20: PW2H-HS LED Descriptions
LED Color Meaning
PWR Red A fuse is blown or a unit failure. Refer to Section 4.2, Response Procedure, and Section 6.4, Replacing Power (PW2H-HS) Unit in the HS Shelf.
Green Normal operation (in service).
Off No power to the unit.
Table 2-21: SV2H-B1/-DL/-DLB/-T11/-T12 LED Descriptions
LED Color Meaning
FAIL Red An internal microprocessor failure. Refer to Section 6.6, Replacing Supervisory (SV2H-T11/-T12/-B1/-DL/-DLB) Unit in the HS Shelf.
Blinking red Unit mismount; the system is configured for a different mode or the mounted unit is not used in this configuration.
Off Normal operation (in service).
LINE Red An incoming OC-48 data communications channel (DCC) failure.
Off Normal operation (in service).
ACS Green The SV2H has been accessed by a local craft interface terminal.
Off Turns off after approximately 30 minutes of no electrical signal.
Page 2-10 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
Chapter 3: Error Codes
CHAPTER 3
3 Error Codes
3.1 Overview
The failure of a TL1 command causes an error code to be returned to the user’s terminal. This section describes the TL1 error codes that apply to the FLM 2400 ADM. Below each error code is a table containing one or more s, listed alphabetically. Corresponding s are provided in the right-hand column.
3.2 Error Code Categories
Error codes fall in one of the following categories:
• Equipage error codes
• Input error codes
• Privilege error codes
• Status error codes.
The following alphabetical listing of TL1 error codes within each category includes the definition, s, and s.
Issue 7, May 1999 FNC and FNC Customer Use Only Page 3-1
3.3: Equipage Error Codes Maintenance and Trouble ClearingFJTU-320-560-480
3.3 Equipage Error Codes
Tables 3-1 through 3-6 describe equipage error code messages.
Table 3-1: ENAD (Equipage, Not Equipped with Audit Capability)
Probable Cause Suggested Corrective Action
A. The TL1 command was sent while the network element (NE) was undergoing a processor reset.
A. Wait until the reset process is complete, then retry the command. With Release 9.0 or later systems, the NE will generate an autonomous message to indicate that the reset is complete.
Table 3-2: ENDS (Equipage, Not Equipped with Duplex Switching)
Probable Cause Suggested Corrective Action
A. The unit controlling the switching function is not installed.
A. Verify that the units are installed and in service.
B. An OPR-PROTNSW-OCn command was attempted during a central processing unit (CPU) failure.
B. Verify that the unit is properly installed.
Table 3-3: ENEQ (Equipage, Not Equipped)
Probable Cause Suggested Corrective Action
A. The TL1 command to the initial HK (housekeeping) controls or the alarm cutoff (ACO) was entered but the units were not installed.
A. Verify that the units are installed.
B. The TL1 command to operate loopbacks or test signals was entered, but the associated interface card, such as OC-3 or T3, was not installed.
B. Verify that the appropriate interface card is installed and in service.
Table 3-4: ENEX (Equipage, Not Equipped with Exercise Capability)
Probable Cause Suggested Corrective Action
A. The user has attempted to enter a cross-connect on an NE that has been configured as a terminal with no cross-connect capability.
A. Verify that the network has been configured as a terminal with cross-connect capability.
Page 3-2 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
3.3: Equipage Error Codes
Table 3-5: ENMD (Equipage, Not Equipped with Memory Device)
Probable Cause Suggested Corrective Action
A. The TL1 command was sent while the NE was undergoing a processor reset.
A. Wait until the reset process is complete, then retry the command.
B. The NE microprocessor unit (MPU) has been removed or is not functioning properly.
B1. Verify that the MPU is installed in the add/drop multiplexer (ADM). If any unit is missing, insert the correct unit and retry the command. Be careful to check for firmware compatibility any time an MPU is installed.
B2. If the units were installed, verify that no equipment failure alarms have been reported on any of these units. Clear alarms if necessary, then retry the command.
Table 3-6: ENSI (Equipage, Not Equipped for Setting Specified Information)
Probable Cause Suggested Corrective Action
A. The command and the access identifier (AID) are valid, but the keyword or domain that has been entered in the command is not valid.
A1. Verify that the keyword used in the TL1 command does not contain a typographical error and is a valid keyword for the command being attempted. The keyword is the third field after the CTAG (correlation tag).
A2. Verify that the domain used in the TL1 command does not contain a typographical error and is a valid domain for the intended keyword. The domain is the fourth field after the CTAG.
Issue 7, May 1999 FNC and FNC Customer Use Only Page 3-3
3.4: Input Error Codes Maintenance and Trouble ClearingFJTU-320-560-480
3.4 Input Error Codes
Tables 3-7 through 3-14 describe input error code messages.
Table 3-7: IDNV (Input, Data Not Valid)
Probable Cause Suggested Corrective Action
A. An item in one of the data fields is not appropriate for the TL1 command used. The data fields are the fields that occur after the CTAG.
A. Verify that the entered data items are valid for the command and are entered in the correct fields.
Table 3-8: IDRG (Input, Data Range Error)
Probable Cause Suggested Corrective Action
A. The KEYWORD=DOMAIN parameter contains invalid data.
A. Verify that the input data is of the proper type and range.
Table 3-9: IIAC (Input, Invalid Access Identifier)
Probable Cause Suggested Corrective Action
A. The AID used in the TL1 message is not valid. A1. Verify that the syntax of the AID is correct.
A2. Verify that the AIDTYPE specified in the TL1 command is actually the AIDTYPE that should be used with this command. For example, an error code of IIAC might be returned if the user attempts to send a command to a T3 facility while specifying an OC-3 AID.
B. The command is attempting to delete (place Out of Service) a facility or equipment slot that is not permitted to be delete
B. Verify that both the command and the application to ensure that the requested command applies.
Table 3-10: IICT (Input, Invalid Correlation Tag)
Probable Cause Suggested Corrective Action
A. The correlation tag (CTAG) has been omitted. A. A CTAG is required for every TL1 command. Retry the command with a CTAG.
B. The CTAG contains too many characters. B. Retry the command with a CTAG of six characters or less.
Page 3-4 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
3.4: Input Error Codes
Table 3-11: IIFM (Input, Invalid Data Format)
Probable Cause Suggested Corrective Action
A. The data typed into the parameter field was the improper format.
A. Verify the syntax of the TL1 command, while paying special attention to the parameter field.
Table 3-12: ICNV (Input, Command Not Valid)
Probable Cause Suggested Corrective Action
A. The first field of the attempted TL1 command is not a valid TL1 command.
A. Verify that the command has the proper syntax and retry the command.
B. The attempted TL1 command is not valid for the particular NE configuration.
B. Verify that the command is valid for the particular NE configuration.
Table 3-13: INUP (Input, Non-Null Unimplemented Parameter)
Probable Cause Suggested Corrective Action
A. The data typed in the parameter field is the correct syntax, but the parameter is not valid for the entered TL1 command.
A. Verify the parameter fields of the TL1 command.
Table 3-14: ISCH (Input, Syntax Invalid Character)
Probable Cause Suggested Corrective Action
A. The parameter field contains invalid data; for example, attempting to use the (“) character for the new TID (target identifier) in the SET-SID command.
A. Verify that the parameter fields contain valid input data.
Issue 7, May 1999 FNC and FNC Customer Use Only Page 3-5
3.5: Privilege Error Codes Maintenance and Trouble ClearingFJTU-320-560-480
3.5 Privilege Error Codes
Tables 3-15 through 3-17 describe privilege error code messages.
Table 3-15: PICC (Privilege, Invalid Command Code)
Probable Cause Suggested Corrective Action
A. The user’s security level did not allow access to the command that was typed; for example, a user with UPC=1 attempted to perform an ED-SYS command.
A. Verify that the user’s security level (UPC [user privilege code]) supports access to the command being attempted.
Table 3-16: PIMF (Privilege, Invalid Memory File)
Probable Cause Suggested Corrective Action
A. Either the ED-SECU-USER or the RTRV-SECU-USER command specified a private identifier (PID) that does not match the current PID being used. In other words, the typed PID does not match the PID that you are currently being logged on with.
A. Retry the command using the correct PID.
Table 3-17: PIUI (Privilege, Illegal User Identify)
Probable Cause Suggested Corrective Action
A. The user identifier (UID) specified by the CANC-USER does not match the UID being used.
A. Retry the command using the correct UID.
B. The UID specified in the ENT-SECU-USER command already exists.
B. Retry the command using a unique UID.
C. The UID specified in either the ED-SECU-USER or the DLT-SECU-USER does not exist.
C. Retry the command using a UID that exists in the ADM.
Page 3-6 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
3.6: Status Error Codes
3.6 Status Error Codes
Tables 3-18 through 3-24 describe status error code messages.
Table 3-18: SAAL (Status, Already Allowed)
Probable Cause Suggested Corrective Action
A. This error code will appear when an allow message, such as the following, is attempted when the reporting is already allowed:
• ALW-MSG-ALL
• ALW-DBREPT-ALL
• ALW-MSG-PSWREPT
• ALW-PMREPT-<AIDTYPE>
A1. Verify that the intended command is being sent. For example, if the intent is to allow the reporting of all autonomous messages, verify that the ALW-MSG-ALL command was sent.
A2. If the intended command was sent, the error code implies that the intended reporting capability is already allowed. For Release 9.0 or later systems, an RTRV-MSG-<AIDTYPE> command can be sent to verify whether or not the performance monitoring (PM) reporting capability for a specific AID has been allowed.
Table 3-19: SAIN (Status, Already Inhibited)
Probable Cause Suggested Corrective Action
A. This error code will appear when an inhibit message, such as the following, is attempted when the reporting is already inhibited:
• INH-MSG-ALL
• INH-DBREPT-ALL
• INH-MSG-PSWREPT
• INH-PMREPT-<AIDTYPE>
A1. Verify that the intended command is being sent. For example, if the intent is to inhibit the reporting of all autonomous messages, verify that the INH-MSG-ALL command was sent.
A2. If the intended command was sent, the error code implies that the intended reporting capability is already inhibited. For Release 9.0 or later systems, an RTRV-MSG-<AIDTYPE> command can be sent to verify whether or not the PM reporting capability for a specific AID has been inhibited.
Table 3-20: SAOP (Status, Already Operated)
Probable Cause Suggested Corrective Action
A. The requested operation, such as the following, has already been completed:
• OPR-LPBK
• CONN-TSTSIG
• OPR-EXT-CONT
• OPR-PROTNSW
A. None. The requested command has already been completed.
Issue 7, May 1999 FNC and FNC Customer Use Only Page 3-7
3.6: Status Error Codes Maintenance and Trouble ClearingFJTU-320-560-480
Table 3-21: SARB (Status, All Resources Busy)
Probable Cause Suggested Corrective Action
A1. This code is generated because the NE is still busy executing the previous TL1 command; for example, single commands that delete a range of many tributary facilities often require several seconds to execute. The execution of these commands may still be continuing after the NE issues the COMPLD response back to the user.
A2. The TL1 command has been sent while the NE is undergoing a processor reset.
A. Wait a few minutes and retry the command.
Table 3-22: SARL (Status, Already Released)
Probable Cause Suggested Corrective Action
A. The requested operation, such as the following, has already been released:
• RLS-LPBK
• DISC-TSTSIG
• RLS-EXT-CONT
• RLS-PROTNSW
A. None. The requested command has already been completed.
Table 3-23: SNVS (Status, Not in Valid State)
Probable Cause Suggested Corrective Action
A1. The command attempted to do one of the following:
A2. Place an equipment slot or facility in service when the equipment or facility was already in service.
A. Retrieve the state of the equipment slot or facility to verify that the facility is in the In-Service state. If the equipment slot or facility is already in the in service state, the command does not need to be retried.
B. Place an equipment slot or facility into the maintenance state (OOS-MT) when the equipment or facility was already in that state.
B. Retrieve the state of the facility to verify that the facility is in the OOS-MT state. If the facility is already in the OOS-MT state, the command does not need to be retried.
C. Place a facility into the Out-of-Service state (OOS-MA) directly from the maintenance state (OOS-MT).
C. Retrieve the state of the facility to determine the facility state. If the slot or facility is in the OOS-MT state, the facility must first be placed in service and then placed in the OOS-MA state.
D. Place a facility In Service when the equipment is not In Service.
D. Verify the facility equipment slot is In Service.
Page 3-8 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
3.6: Status Error Codes
E. Delete a tributary channel unit without first deleting the facilities that the tributary channel unit carried.
E1. After checking the engineering work order, delete the facilities that are found on the card.
E2. Deleting facilities will cause any service carried by those facilities to be lost.
E3. Facilities can be deleted without first deleting the cross-connects for the circuit.
F. Enter a cross-connect of a particular signal type when the cross-connect levels of the NE were provisioned differently. For example, if the user provisions the high-speed time slots to be STS-3c and then attempts to enter STS-1 cross-connects to these time slots, the command will be denied.
F. Verify that the time slot assignment (TSA) level has been set appropriately. Verify that the attempted cross-connect was intended to go to the high-speed time slots specified in the command. Verify that the correct AIDTYPE was used in the ENT-CRS-<AIDTYPE> command.
G. Attempt to delete a one-way pass-through cross-connection when the drop cross-connect to the end point (circuit destination) has not been deleted. This applies to dual-node ring interconnections.
G. Delete the drop cross-connect at the secondary node before deleting the one-way pass-through at the primary node.
Table 3-24: SSRD (Status, Switch Request Denied)
Probable Cause Suggested Corrective Action
A. A manual switch was attempted, but the equipment or facility being switched to is either not present or switching to the facility or equipment would cause a service disruption.
A1. Retrieve the conditions on the NE to verify that no service-affecting conditions exist on the facility or equipment to which the switch is desired. These conditions must be cleared before a manual software switch will be accepted. If the switch must take place regardless of the service impact, retry the command and specify a forced switch rather than a manual switch.
A2. For a facility switch, verify that all necessary parameters associated with that unit have been correctly provisioned.
A3. For an equipment switch, verify that the unit to be switched to is installed and placed in service and that all necessary parameters associated with that unit have been correctly provisioned.
B. The AID specified in the command should be the “switch from” AID; that is, the AID of the active facility or equipment—the facility or equipment that is currently carrying the traffic. If the AID specified is not the AID of the active facility or equipment, the command will be denied.
B1. Verify which equipment slot or facility is actively carrying the traffic. If the desired equipment or facility is already carrying the traffic, the command need not be sent.
B2. Verify the AID to be used and reattempt the command.
Table 3-23: SNVS (Status, Not in Valid State)
Probable Cause Suggested Corrective Action
Issue 7, May 1999 FNC and FNC Customer Use Only Page 3-9
3.6: Status Error Codes Maintenance and Trouble ClearingFJTU-320-560-480
C. For 1:1 or 1+1 equipment, if a previous switch from the current standby equipment was never released, the switch request is denied.
C. Perform an RLS-PROTNSW command on the standby equipment; then retry the OPR-PROTNSW command on the active equipment.
Table 3-24: SSRD (Status, Switch Request Denied)
Probable Cause Suggested Corrective Action
Page 3-10 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
Chapter 4: Responding to Alarms andConditions
CHAPTER 4
4 Responding to Alarms and Conditions
4.1 Condition Code Responses
4.1.1 Summary
Use this section to respond to conditions reported by the FLM 2400 ADM system. 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 for clearing troubles. The majority of this section consists of the FLM 2400 ADM alarm and status message condition codes, which are presented in alphabetical order. Each is accompanied by a table that provides the following:
• AID type
• Direction of signal on which trouble (or trouble indicator) appears
• Probable cause
• Suggested corrective action.
For some condition types, such as the BER condition types, additional information before the table explains how to interpret the FLEXR® flexible user interface software or TL1 message. Note that although all condition types reflect near-end messages, the source of a problem can be at a remote location or in near-end tributary equipment.
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-1
4.1: Condition Code Responses Maintenance and Trouble ClearingFJTU-320-560-480
4.1.2 Condition Code Types
Three types of conditions are reported: alarm events, transient conditions, and standing conditions. These conditions are defined as follows:
• Alarm events trigger autonomous messages to notify maintenance and operational personnel of failure or fault conditions that require an immediate response. Autonomous alarm event messages carry an ALMEVT label. Office alarms alert local maintenance personnel with audible and visible indications that an alarm event exists. Alarm events can also be reported to a remote operations support system (OSS). Alarms messages can be retrieved by 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 following are the two categories:
– 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 event 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.
4.1.3 Other Resources
To perform related trouble-clearing tasks, refer to the following sections in this practice:
• To replace a unit: Refer to the Task Index List to select the appropriate unit replacement procedure.
• To retrieve a condition message: Refer to Section 1.3, Alarm/Status Identification, to retrieve and interpret alarms, transient conditions, and standing conditions.
• To interpret a message: Refer to Section 1.5, Maintenance Philosophy, for information on understanding and interpreting condition messages.
• To interpret LED indications: Refer to Section 2, LED Indications, to interpret the condition types shown by the LEDs on the plug-in units.
Page 4-2 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.2: Response Procedure
4.2 Response Procedure
The following steps for clearing a trouble are presented only as an example. It is impossible to provide a single approach to trouble clearing when a wide variety of trouble situations may exist. Certainly, local trouble-clearing procedures take precedence.
Step 1 Examine the autonomous messages associated with the condition changes that are in question.
a. If a printer output of these messages is available, use that.
b. If a printer output of these messages is not available, log on the nodes 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 events 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.
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.
d. Alarm indication signal (AIS) and other maintenance signal conditions that are normally not the cause of the trouble are not focused on until the more serious problems are cleared.
e. 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 table in the following pages for information on probable causes and suggested corrective actions.
Step 3 If problems persist after a reasonable effort, call Fujitsu technical support at 1-800-USE-FTAC (1-800-873-3822).
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-3
4.2: Response Procedure Maintenance and Trouble ClearingFJTU-320-560-480
Problem locations, probable causes, and corrective actions are listed in Tables 4-1 through 4-218. The AID Type column is to guide the user to the correct row based on the AID type found in the 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).
You have completed this task.
Page 4-4 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3 Condition Tables
4.3.1 3BRDn-W/P-m
Table 4-1 suggests corrective action for a 3BRDn-W/P-m High-Density Tributary Shelf Bridge Cable Failure (3BRDn-W/P-m) Alarm Event.
To understand what the 3BRD condition type indicates, read the following and note Figures 4-1 and 4-2. Then go to the table that follows for probable causes of the alarm and corrective actions. This condition type is indicated with variables to help explain where the problem is located.
The letter n after 3BRD indicates which High-Density Tributary (HD TRIB) Shelf generated the alarm; n=1, 2, 3, or 4, as follows:
• If n=1, the problem is in Trib shelf 1.
• If n=2, the problem is in Trib shelf 2.
• If n=3, the problem is in Trib shelf 3.
• If n=4, the problem is in Trib shelf 4.
In the condition type above, the W/P indicates that the problem could be with a Working (W) or Protection (P) unit; for example, the problem could be 3BRD1-W-1 or 3BRD1-P-1.
Table 4-1: 3BRDn-W/P-m (High-Density Tributary Shelf Bridge Cable Failure)—Alarm Event
AID Type Direction Probable Cause Suggested Corrective Action
COM NA Trouble exists on the bridge cable connection between the MC6A-3BRD and the HC2T-MDL. See the complete explanation for exactly where the trouble is located.
• Verify that the bridge cable is properly connected to the HC2T-MDL unit. See Section 6.16 in this practice.
• Verify that the bridge cable is properly connected to the MC6A-3BRD unit. See Section 6.20 in this practice.
• If no bridge cable connection is desired, deactivate alarming for any bridge cable connection that is not equipped.
• Replace bridge cable.
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-5
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
The m at the end of the condition type shows which group of HC2T units are involved in the faulty connection, either the left or right group; m=1 or 2, as follows.
• If m=1, the HC2T units on the left half of the shelf are involved in the faulty connection.
• If m=2, the HC2T units on the right half of the shelf are involved in the faulty connection.
In any HD TRIB Shelf, which is designated here as shelf 3BRDn, the trouble could then be located in the following locations:
• 3BRDn-W-1
• 3BRDn-W-2
• 3BRDn-P-1
• 3BRDn-P-2.
If the condition type is either W-1 (Working) or P-1 (Protection), the trouble is on the FC9608CAB1 bridge cable between the Working MC6A-3BRD and the Working HC2T-MDL on the left side of the HD TRIB shelf, or between the protection MC6A-3BRD and the Protection HC2T-MDL on the right half of the HD TRIB Shelf. Figures 4-1 and 4-2 show the four locations in each shelf where the trouble can be located.
Page 4-6 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
Figure 4-1: Trouble Location for the 3BRDn-P-1/2 Condition Type
3BRDn-W-1
3BRDn-W-2 d609
9.2
P
PW1A-TRIB
PW1A-TRIB
MP2T-T12
21 21
The problem is in this bridge cable connection.
HS2T-C3
HC2T-MDL
2
MC6A-3XXX
1 2
MC6A-3BRD
1
MC6A-3BRD
P
MC6A-3XXX
MC6A-3XXX
MC6A-3XXX
HC2T-MDL
MC6A-3XXX
MC6A-3XXX
HC2T-MDL
HS2T-C3
W
MC6A-3XXX
21
MC6A-3XXX
W W
HC2T-MDL
P
P
PW1A-TRIB
PW1A-TRIB
MP2T-T12
21 21
The problem is in this bridge cable connection.
HS2T-C3
HC2T-MDL
2
MC6A-3XXX
1 2
MC6A-3BRD
1
MC6A-3BRD
P
MC6A-3XXX
MC6A-3XXX
MC6A-3XXX
HC2T-MDL
MC6A-3XXX
MC6A-3XXX
HC2T-MDL
HS2T-C3
W
MC6A-3XXX
21
MC6A-3XXX
W W
HC2T-MDL
P
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-7
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
Figure 4-2: Trouble Location for the 3BRDn-P-1/2 Condition Type
3BRDn-P-1
3BRDn-P-2
d610
0.1
P
PW1A-TRIB
PW1A-TRIB
MP2T-T12
21 21
The problem is in this bridge cable connection.
HS2T-C3
HC2T-MDL
2
MC6A-3xxx
1 2
MC6A-3BRD
1
MC6A-3BRD
P
MC6A-3xxx
MC6A-3xxx
MC6A-3xxx
HC2T-MDL
MC6A-3xxx
MC6A-3xxx
HC2T-MDL
HS2T-C3
W
MC6A-3xxx
21
MC6A-3xxx
W W
HC2T-MDL
P
P
PW1A-TRIB
PW1A-TRIB
MP2T-T12
21 21
The problem is in this bridge cable connection.
HS2T-C3
HC2T-MDL
2
MC6A-3xxx
1 2
MC6A-3BRD
1
MC6A-3BRD
P
MC6A-3xxx
MC6A-3xxx
MC6A-3xxx
HC2T-MDL
MC6A-3xxx
MC6A-3xxx
HC2T-MDL
HS2T-C3
W
MC6A-3xxx
21
MC6A-3xxx
W W
HC2T-MDL
P
Page 4-8 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.2 ACTLPBKF
The network element is provisioned to provide a facility loopback for testing purposes. Table 4-2 suggests corrective action for a Facility Loopback in Active Position (ACTLPBKF) Standing Condition. Table 4-3 lists Condition Parameters for ACTLPBKF.
Table 4-2: ACTLPBKF (Facility Loopback in Active Position)—Standing Condition
AID Type Probable Cause Suggested Corrective Action
EC1 A loopback on an EC-1 facility is in place. • Verify that the facility testing is complete.
• Release the loopback.
OC3 A loopback on an OC-3 facility is in place. • Verify that the facility testing is complete.
• Release the loopback.
T3 A loopback on a T3 facility is in place. • Verify that the facility testing is complete.
• Release the loopback.
Table 4-3: ACTLPBKF Condition Parameters
AID Type
Default Notification
CodeLocation Direction Service Affecting/
Non-Service Affecting
EC1 MN NEND NA NSA
OC3 MN NEND NA NSA
T3 MN NEND NA NSA
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-9
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.3 ACTLPBKT
The NE is provisioned to provide a terminal loopback for testing purposes. Table 4-4 suggests corrective action for a Terminal Loopback in Active Position (ACTLPBKT) Standing Condition. Table 4-5 lists Condition Parameters for ACTLPBKT.
Table 4-4: ACTLPBKT (Terminal Loopback in Active Position)—Standing Condition
AID Type Probable Cause Suggested Corrective Action
EC1 A loopback on an EC-1 facility is in place. • Verify that the facility testing is complete.
• Release the loopback.
OC3 A loopback on an OC-3 facility is in place. • Verify that the facility testing is complete.
• Release the loopback.
T3 A loopback on a T3 facility is in place. • Verify that the facility testing is complete.
• Release the loopback.
Table 4-5: ACTLPBKT Condition Parameters
AID Type
Default Notification
CodeLocation Direction Service Affecting/
Non-Service Affecting
EC1 MN NEND NA NSA
OC3 MN NEND NA NSA
T3 MN NEND NA NSA
Page 4-10 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.4 ACTOW
Table 4-6 suggests corrective action for a Orderwire Line Active (ACTOW) Standing Condition. Table 4-7 lists Condition Parameters for ACTOW.
Table 4-6: ACTOW (Orderwire Line Active)—Standing Condition
AID Type Probable Cause Suggested Corrective Action
OC48 External orderwire communication channel(s) have been activated by command.
• Verify that the orderwire communication channels are no longer needed.
• Deactivate the orderwire channel.
Table 4-7: ACTOW Condition Parameters
AID Type
Default Notification Code Location Direction Service Affecting/
Non-Service Affecting
OC48 MN NEND NSAD
N 6
103
TRMT
OC-48
ADDEDSIGNAL
2400 ADMHS & TRIBs
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-11
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.5 AIS
Table 4-8 suggests corrective action for an Alarm Indication Signal (AIS) Alarm Event. Table 4-9 lists Condition Parameters for AIS.
Table 4-8: AIS (Alarm Indication Signal)—Alarm Event
AID Type Probable Cause Suggested Corrective Action
EC1 The input signal on an EC-1 tributary interface contains an AIS.
• Retrieve the alarms at upstream sites.
• Clear any upstream service-affecting alarms.
OC3 OC12
The locally received tributary OC-3/OC-12 signal contains an AIS. This indicates a remote OC-3/OC-12 level failure.
• Retrieve the alarms at upstream sites.
OC48 The locally received OC-48 signal contains an OC-48 AIS. This signal indicates a remote OC-48 level failure at the upstream site.
• Check the alarms at the upstream sites. There should be an OC-48 LOS or other service-affecting alarm reported on the upstream equipment.
STS1
STS3C
STS12C
The STS signal demultiplexed from the OC-48 contains an AIS. This AIS signal can result from an upstream failure along the STS path. Examples of possible failures include the following:
• OC-48 failures, such as an LOS.
• T3 input failures, such as a T3 LOS.
If no other network alarms exist, this alarm is probably caused by a bad 78-Mb/s cable connection.
• Check for an upstream OC-48 signal failure.
• Check for a service-affecting alarm where the tributary signal enters the far end of the ring. Clear these alarms.
• Verify the connection on the tributary units, beginning with the HC2T-MDL (see the Plug-In Unit practice, FJTU-320-560-220, Section 8.11, Installing High-Speed Channel (HC2T-MDL/-C12L) Unit in the HD TRIB Shelf). Then continue with other units, referring to the Task Index List of the FJTU-320-560-220 practice to locate the applicable section.
• Verify the good condition of the 78-Mb/s cables along the path.
T1 A failure on the input side of the timing source (i.e., the building integrated timing supply [BITS] clock).
• Refer to the timing source vendor documentation for procedures to isolate and repair failure.
T3 TRMT—The DS3 input to the tributary shelf contains an AIS.
RCV—A T3 AIS is generated in path switched ring systems if an STS AIS is received on both drop paths.
• Inspect and clear alarms from the upstream asynchronous equipment.
Page 4-12 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
Table 4-9: AIS Condition Parameters
AID Type
Default Notification Code Location Direction Service Affecting/
Non-Service Affecting
EC1 CR NEND SA
OC3 CR/MN NEND TRMT SA/NSA
OC12 CR/MN NEND TRMT SA/NSA
OC48 CR/MN NEND SA/NSA
STS1 CR/MN NEND RCV SA/NSA
STS3C CR/MN NEND RCV SA/NSA
STS12C CR/MN NEND RCV SA/NSA
T1 CR/MN NEND NA SA/NSA
T3 CR NEND TRMT
RCV
SA
DN
610
3
TRMT
OC-48
ADDEDSIGNAL
2400 ADMHS & TRIBs
DN
610
4
RCV
DROPPEDSIGNAL
OC-48
2400 ADMHS & TRIBs
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-13
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.6 AL1PLS
Table 4-10 suggests corrective action for an All-Ones Pulse Generated (AL1PLS) Standing Condition. Table 4-11 lists Condition Parameters for AL1PLS.
Table 4-10: AL1PLS (All-Ones Pulse Generated)—Standing Condition
AID Type Probable Cause Suggested Corrective Action
EC1 An EC-1 test signal has been generated by command.
• Verify that the facility testing is complete.
• Disable the EC-1 test signal.
T1 A T1 test signal has been generated by command.
• Verify that the facility testing is complete.
• Disable the T1 test signal.
T3 A T3 test signal has been generated by command.
• Verify that the facility testing is complete.
• Disable the T3 test signal.
Table 4-11: AL1PLS Condition Parameters
AID Type
Default Notification Code Location Direction Service Affecting/
Non-Service Affecting
EC1 MN NEND NSA
T1 MN NEND NA NSA
T3 MN NEND RCV NSA
DN
610
4
RCV
DROPPEDSIGNAL
OC-48
2400 ADMHS & TRIBs
Page 4-14 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.7 APSAM
Table 4-12 suggests corrective action for an Automatic Protection Switching Architecture Match Failure (APSAM) Standing Condition. Table 4-13 lists Condition Parameters for APSAM.
Table 4-12: APSAM (Automatic Protection Switching Architecture Match Failure)—Standing Condition
AID Type Probable Cause Suggested Corrective Action
OC3
OC12
Local and remote NEs do not have the same protection setting.
• Fujitsu NEs do not support 1:N protection mode. The NE must be provisioned for 1+1 mode. The APSAM is reported via the K2 byte (bit 5). Bit 5=0 for 1+1, and bit 5=1 for 1+N.
• If remote node is not a Fujitsu node, it must be set for 1+1 mode.
• Replace faulty HS2T or MS6A as required. Refer to Sections 6.15 and 6.27 respectively.
Faulty HS2T or MS6A unit.
OC48 Local and remote Network Elements do not have the same protection setting.
• Fujitsu NEs do not support 1:N protection mode. The NE must be provisioned for 1+1 Mode. APSAM is reported via the K2 byte (bit 5). Bit 5=0 for 1+1, and Bit 5=1 for 1+N.
• If remote node is not a Fujitsu node, it must be set for 1+1 mode.
• Replace faulty HS2H as required. Refer to Section 6.7.Faulty HS2H unit.
Table 4-13: APSAM Condition Parameters
AID Type
Default Notification
CodeLocation Direction Service Affecting/
Non-Service Affecting
OC3 MN NEND NSA
OC12 MN NEND TRMT NSA
OC48 MN NEND NSA
DN
610
3
TRMT
OC-48
ADDEDSIGNAL
2400 ADMHS & TRIBs
DN
610
4
RCV
DROPPEDSIGNAL
OC-48
2400 ADMHS & TRIBs
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-15
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.8 APSB
The NE is provisioned to provide a terminal loopback for testing purposes. Table 4-14 suggests corrective action for an Automatic Protection Switching Byte Failure (APSB) Alarm Event. Table 4-15 lists Condition Parameters for APSB.
Table 4-14: APSB (Automatic Protection Switching Byte Failure)—Alarm Event
AID Type Probable Cause Suggested Corrective Action
OC3 OC12
An automatic protection switching (APS) channel byte failure. The APS bytes (K1/K2) are in an invalid state.
• Check for OC-3/OC-12 optical channel unit failures.
• Check for failure indicators in the HS2T-C3 unit. If this unit has failed, replace it and return the defective unit to Fujitsu. Refer to Section 6.15, Replacing High-Speed Switch (HS2T-xxxx) Unit in the HD TRIB Shelf, for unit replacement procedures.
• Check for failures in the far-end OC-3/OC-12 optical channel unit.
OC48 An APS channel byte failure. The APS bytes (K1/K2) are in an invalid state.
• Check for OC-48 (transmit and receive) optical channel unit failures. Refer to the Plug-In Unit Installation practice, FJTU-320-560-220, Section 6.7, Installing High-Speed Transmit Channel (HT2H) Unit in the HS Shelf, and Section 6.8, Installing High-Speed Receive Channel (HR2H) Unit in the HS Shelf, and Sections 6.10 and 6.11 in this practice for information on replacing the units.
• Check for failures in the HS2H unit. If this unit has failed, replace it, and return the defective unit to Fujitsu. Refer to Section 6.7, Replacing the High-Speed Switch (HS2H-xxxx) Unit in the HS Shelf, for unit replacement procedures.
• Check for failures in the far-end OC-48 transmitter.
Page 4-16 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
Table 4-15: APSB Condition Parameters
AID Type
Default Notification Code Location Direction Service Affecting/
Non-Service Affecting
OC3 MN NEND NSA
OC12 MN NEND TRMT NSA
OC48 MN NEND NSA
DN
610
3
TRMT
OC-48
ADDEDSIGNAL
2400 ADMHS & TRIBs
DN
610
4
RCV
DROPPEDSIGNAL
OC-48
2400 ADMHS & TRIBs
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-17
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.9 APSCM
The NE is provisioned to provide a terminal loopback for testing purposes. Table 4-16 suggests corrective action for an Automatic Protection Switching Channel Mismatch (APSCM) Alarm Event. Table 4-17 lists Condition Parameters for APSCM.
Table 4-16: APSCM (Automatic Protection Switching Channel Mismatch)—Alarm Event
AID Type Probable Cause Suggested Corrective Action
OC3 OC12
An APS channel mismatch, which applies only to a bidirectional APS. The local add/drop multiplexer (ADM) is not receiving the K1/K2 values that it is expecting.
• Verify proper provisioning of unidirectional versus bidirectional switching at both the local and upstream sites. Both the local and remote sites must be provisioned identically. Unidirectional is the default setting. Refer to Section 7.8, Changing Unidirectional/Bidirectional Switching.
• Check for local or remote OC-3/OC-12 optical channel unit failure. Refer to Section 1.4.2, Message Retrieval.
OC48 An APS channel mismatch, which applies only to a bidirectional APS. The local ADM is not receiving the K1/K2 values that it is expecting.
This alarm applies only to 1+1 terminal and 1+1 linear ADM systems.
• Verify proper provisioning of unidirectional versus bidirectional switching at both the local and upstream sites. Both the local and remote sites must be provisioned identically. Unidirectional is the default setting. Refer to Section 7.8.
• Check for local or remote OC-48 optical transmitter failure. Section 6.10, Replacing the High-Speed Transmit Channel (HT2H-xxxx) Unit in the HS Shelf.
Page 4-18 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
Table 4-17: APSCM Condition Parameters
AID Type
Default Notification Code Location Direction Service Affecting/
Non-Service Affecting
OC3 MN NEND NSA
OC12 MN NEND TRMT NSA
OC48 MN NEND NSA
DN
610
3
TRMT
OC-48
ADDEDSIGNAL
2400 ADMHS & TRIBs
DN
610
4
RCV
DROPPEDSIGNAL
OC-48
2400 ADMHS & TRIBs
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-19
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.10 APSDM
The NE is provisioned to provide a terminal loopback for testing purposes. Table 4-18 suggests corrective action for an Automatic Protection Switching Direction Match Failure (APSDM) Standing Condition. Table 4-19 lists Condition Parameters for APSDM.
Table 4-18: APSDM (Automatic Protection Switching Direction Match Failure)—Standing Condition
AID Type Probable Cause Suggested Corrective Action
OC3 OC12
Local and remote NEs do not have same unidirectional/bidirectional mode settings.
• Perform the RTRV-FFP command to confirm switching modes. Switch modes are reported via the K2 byte (bits 6-8); UNI=100, BI=101.
• Retrieve the optical facility protection group to confirm switching nodes.
• After identifying switch mode, set local and remote nodes to the same setting.
• If this does not resolve problem, replace faulty HS2T or MS6A as required. Refer to Section 6.15 and 6.27 respectively.
Faulty HS2T or MS6A unit.
OC48 Local and remote NEs do not have same unidirectional/bidirectional mode settings.
• Perform the RTRV-FFP command to confirm switching modes. Switch modes are reported via the K2 byte (bits 6-8); UNI=100, BI=101.
• Retrieve the optical facility protection group to confirm switching nodes.
• After identifying switch mode, set local and remote nodes to the same setting.
• If this does not resolve problem, replace faulty HS2H as required. Refer to Section 6.7.
Faulty HS2H unit.
Page 4-20 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
Note: OC-48 AID type does not apply to the FLM 2400 ADM bidirectional line-switched ring (BLSR) configuration.
Table 4-19: APSDM Condition Parameters
AID Type
Default Notification
CodeLocation Direction Service Affecting/
Non-Service Affecting
OC3 MN NEND NSA
OC12 MN NEND TRMT NSA
OC48 MN NEND NSA
DN
610
3
TRMT
OC-48
ADDEDSIGNAL
2400 ADMHS & TRIBs
DN
610
4
RCV
DROPPEDSIGNAL
OC-48
2400 ADMHS & TRIBs
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-21
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.11 AUTOPROVERR
The NE is provisioned to provide a terminal loopback for testing purposes. Table 4-20 suggests corrective action for an Auto Provisioning Error (AUTOPROVERR) Alarm Event. Table 4-21 lists Condition Parameters for AUTOPROVERR.
Note: AUTOPROVERR is used only with the FLM 2400 ADM BLSR configuration.
Table 4-20: AUTOPROVERR (Auto Provisioning Error)—Alarm Event
AID Type Probable Cause Suggested Corrective Action
COM A signal failure has occurred on the ring, and the user adds new cross-connect data by command. When the unit attempts to autoprovision the squelch tables, they cannot be updated, triggering the AUTOPROVERR alarm.
• Clear the signal failure and the AUTOPROVERR alarm will clear.
• If the AUTOPROVERR does not clear, then initialize the topology.
Table 4-21: AUTOPROVERR Condition Parameters
AID Type Default Notification Code Location Direction Service Affecting/Non-Service Affecting
COM MN NEND NA NSA
Page 4-22 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.12 B1ERR
A test signal has been generated by command.
The NE is provisioned to provide a terminal loopback for testing purposes. Table 4-22 suggests corrective action for a B1 Error Data Generated (B1ERR) Standing Condition. Table 4-23 lists Condition Parameters for B1ERR.
Table 4-22: B1ERR (B1 Error Data Generated)—Standing Condition
AID Type Probable Cause Suggested Corrective Action
OC3 OC-3 test signal is enabled. • Verify that the facility testing is complete.
• Disable the OC-3 test signal.
OC12 OC-12 test signal is enabled. • Verify that the facility testing is complete.
• Disable the OC-12 test signal.
OC48 OC-48 test signal is enabled. • Verify that the facility testing is complete.
• Disable the OC-48 test signal.
Table 4-23: B1ERR Condition Parameters
AID Type
Default Notification Code Location Direction Service Affecting/
Non-Service Affecting
OC3 MN NEND NSA
OC12 MN NEND RCV NSA
OC48 MN NEND NSA
DN
610
4
RCV
DROPPEDSIGNAL
OC-48
2400 ADMHS & TRIBs
DN
610
3
TRMT
OC-48
ADDEDSIGNAL
2400 ADMHS & TRIBs
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-23
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.13 B2ERR
The NE is provisioned to provide a terminal loopback for testing purposes. Table 4-24 suggests corrective action for a B2 Error Data Generated (B2ERR) Standing Condition. Table 4-25 lists Condition Parameters for B2ERR.
Table 4-24: B2ERR (B2 Error Data Generated)—Standing Condition
AID Type Probable Cause Suggested Corrective Action
EC1 An EC-1 test signal has been generated by command.
• Verify that the facility testing is complete.
• Disable EC-1 test signal.
OC3 An OC-3 test signal has been generated by command.
• Verify that the facility testing is complete.
• Disable OC-3 test signal.
OC12 An OC-12 test signal has been generated by command.
• Verify that the facility testing is complete.
• Disable OC-12 test signal.
OC48 An OC-48 test signal has been generated by command.
• Verify that the facility testing is complete.
• Disable OC-48 test signal.
Table 4-25: B2ERR Condition Parameter
AID Type
Default Notification
CodeLocation Direction Service Affecting/
Non-Service Affecting
EC1 MN NEND NSA
OC3 MN NEND NSA
OC12 MN NEND RCV NSA
OC48 MN NEND TRMT NSA
DN
610
4
RCV
DROPPEDSIGNAL
OC-48
2400 ADMHS & TRIBs
DN
610
4
RCV
DROPPEDSIGNAL
OC-48
2400 ADMHS & TRIBs
Page 4-24 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.14 B3ERR
The NE is provisioned to provide a terminal loopback for testing purposes. Table 4-26 suggests corrective action for a B3 Error Data Generated (B3ERR) Standing Condition. Table 4-27 lists Condition Parameters for B3ERR.
Table 4-26: B3ERR (B3 Error Data Generated)—Standing Condition
AID Type Probable Cause Suggested Corrective Action
STS1 An STS-1 test signal has been generated by command.
• Verify that the facility testing is complete.
• Disable STS-1 test signal.
Table 4-27: B3ERR Condition Parameters
AID Type
Default Notification Code Location Direction Service Affecting/
Non-Service Affecting
STS1 MN NEND NSAD
N 6
103
TRMT
OC-48
ADDEDSIGNAL
2400 ADMHS & TRIBs
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-25
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.15 BERSDL and BERSFL
The BER condition types show two different types of problems: line (L) problems and path (P) problems. In both cases, the signal has either degraded (D) or has failed (F). Figures 4-3 and 4-4 show where the problem is located and the probable cause.
The NE is provisioned to provide a terminal loopback for testing purposes. Table 4-28 suggests corrective action for a Bit Error Rate Signal Degrade/Fail–Line (BERSDL/BERSFL) Alarm Event. Table 4-29 lists Condition Parameters for BERSDL and BERSFL.
Table 4-28: BERSDL and BERSFL (Bit Error Rate Signal Degrade/Fail–Line)—Alarm Event
AID Type Probable Cause Suggested Corrective Action
OC3 OC12
The OC-3/OC-12 receive power has fallen below or exceeded the specified threshold limits.
A connector in the optical link is dirty.
A plug-in unit hardware problem in an OC-12 Regenerator could cause OC-12 line BER problems.
• Verify the local receive optical levels and the upstream transmit levels. Clean the optical connectors. Refer to Sections 7.1 through 7.5.
• Verify good optical connections to the local and far-end (FEND) OC-3/OC-12 units and at the lightwave distribution frame (LDF) panels along the link. Refer to Sections 7.1 through 7.5.
• Replace the far-end OC-3 or OC-12 channel unit and return the defective unit to Fujitsu. In this practice, refer to the Task Index List (Section 6, Replacing Units) to locate the applicable instructions for unit replacement.
OC48 The OC-48 receive power has fallen below or exceeded the specified threshold limits.
A connector in the OC-48 optical link is dirty.
The far-end transmitter is creating bit errors.
Points of large optical reflection exist along the OC-48 link.
An HM2H, HR2H, or HT2H plug-in unit problem at an FLM 2400 ADM (Regenerator) site could cause OC-48 line BER problems.
• Verify the local receive optical levels, and the upstream transmit levels. Clean the optical connectors. Refer to Sections 7.1 through 7.5.
• Verify good optical connections to the local and far-end OC-48 units, and at the LDF panels along the link. Refer to Sections 7.1 through 7.5.
• The presence of large reflection points along the link can cause bit errors. If the trouble cannot be cleared by cleaning the connectors, examine the link by using an optical time domain reflectometer (OTDR) for reflections larger than –27 dBm.
• Replace near-end OC-48 receiver and return the defective unit to Fujitsu. Refer to Section 6.11, Replacing High-Speed Receive Channel (HR2H-xxxx) Unit in the HS Shelf, for replacement procedures.
• Replace the far-end OC-48 transmitter and return the defective unit to Fujitsu. Refer to Section 6.10, Replacing the High-Speed Transmit Channel (HT2H-xxxx) Unit in the HS Shelf, for replacement procedures.
Page 4-26 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
These messages indicate a line-level problem, which can only exist between line-terminating equipment (LTE). Figure 4-3 shows how to determine exactly where the line BER problem is located. The notes shown in the figure give examples of how to determine problem locations.
Table 4-29: BERSDL and BERSFL Condition Parameters
AID Type
Default Notification
CodeLocation Direction Service Affecting/
Non-Service Affecting
OC3 CR/MN NEND SA/NSA
OC12 CR/MN NEND TRMT SA/NSA
OC48 CR/MN NEND SA/NSA
DN
610
3
TRMT
OC-48
ADDEDSIGNAL
2400 ADMHS & TRIBs
DN
610
4
RCV
DROPPEDSIGNAL
OC-48
2400 ADMHS & TRIBs
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-27
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
Note 1: If an OC-48 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 an OC-48 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.
Figure 4-3: Line BER Causes
Node A
HS HS
REGEN
Node B Node C Node D
HS
OC-48 OC-48 OC-48
Link A Link B Link C
12
d610
1.1TRIB TRIB
DS3
TRIB
DS3
Line Section Section
Line
Page 4-28 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.16 BERSDP and BERSFP
These messages indicate a path-level problem. Figure 4-4 and the note in the figure show how to detect exactly where the problem lies.
Table 4-30 suggests corrective action for a Bit Error Rate Signal Degrade/Fail—Path (BERSDP/BERSFP) Alarm Event. Table 4-31 lists Condition Parameters for BERSDP and BERSFP.
Note: BERSDP and BERSFP do not apply to the FLM 2400 ADM BLSR configuration.
CAUTION:
Replacing an HM2H unit will cause hits on previously unerrored traffic. Perform this step only after careful fault isolation.
Note: 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 on the source or destination tributary shelves or a multplexer unit anywhere along the path, or a 78-Mb/s cable problem may exist between the BER detection point on the channel unit and the path origination point.
Figure 4-4: Path Bit Error Rate Causes
Node A
HS
TRIB
HS
TRIB
REGEN
Node B Node C Node D
HS
TRIB
OC-48 OC-48 OC-48
Link A Link B Link C
1
d610
2.1
DS3 DS3
PathOrigination
Path
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-29
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
Table 4-30: BERSDP and BERSFP (Bit Error Rate Signal Degrade/Fail—Path)—Alarm Event
AID Type Probable Cause Suggested Corrective Action
STS1 STS3C STS12C
The STS signal demultiplexed and dropped from the OC-48 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 or 78-Mb/s cable problems along the SONET path.
• Examine the network for other path BER problems and retrieve performance monitoring (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 defective Working unit and return the defective unit to Fujitsu.
• Verify good 78-Mb/s and bridge cable connections along the path. Begin by checking the tributary shelf side of the connections. Refer to the Plug-In Unit Installation practice, FJTU-320-560-220, Section 8.8, Installing High-Speed Switch (HS2T-D3/-S1/ -SDL/-SDL2) Unit in the HD TRIB Shelf and Section 8.10, Installing Middle-Speed Channel Clock Distribution (MC6A-2THR) Unit.
• If the trouble can be isolated to an HM2H unit, replace the unit and return the defective unit to Fujitsu. Refer to Section 6.9, Replacing the High-Speed Multiplexer (HM2H-xx) Unit in the HS Shelf.
Table 4-31: BERSDP and BERSFP Condition Parameters
AID Type
Default Notification Code Location Direction Service Affecting/
Non-Service Affecting
STS1 CR/MN NEND SA/NSA
STS3C CR/MN NEND RCV SA/NSA
STS12C CR/MN NEND RCV SA/NSA
DN
610
4
RCV
DROPPEDSIGNAL
OC-48
2400 ADMHS & TRIBs
Page 4-30 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.17 CANVAL
Table 4-32 suggests corrective action for a CANC-VALTM Command Acceptable (CANVAL) Transient Condition. Table 4-33 lists Condition Parameters for CANVAL.
Table 4-32: CANVAL (CANC-VALTM Command Acceptable)—Transient Condition
AID Type Probable Cause Suggested Corrective Action
COM The NE can now accept cancel validation timer for software download (SWDL).
• Send CANC-VALTM command to NE if new software version is accepted by the technician.
Table 4-33: CANVAL Condition Parameters
AID Type Location Direction Service Affecting/
Non-Service Affecting
COM NEND NA NSA
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-31
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.18 CLEI-FLT
Table 4-34 suggests corrective action for a Plug-In Failure (CLEI-FLT) Alarm Event. Table 4-35 lists Condition Parameters for CLEI-FLT.
Table 4-34: CLEI-FLT (Plug-In Failure)—Alarm Event
AID Type Probable Cause Suggested Corrective Action
EQPT The plug-in unit has failed. • In this practice, refer to the Task Index List to locate the procedure for replacing the failed unit.
• Replace the unit and return the defective unit to Fujitsu.
Table 4-35: CLEI-FLT Condition Parameters
AID Type
Default Notification
CodeLocation Direction Service Affecting/
Non-Service Affecting
EQPT CR/MN NEND NA SA/NSA
Page 4-32 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.19 CLEI-LBC
Table 4-36 suggests corrective action for a Excessive Laser Transmitter Bias Current (CLEI-LBC) Alarm Event. Table 4-37 lists Condition Parameters for CLEI-LBC.
Table 4-36: CLEI-LBC (Excessive Laser Transmitter Bias Current)—Alarm Event
AID Type Probable Cause Suggested Corrective Action
EQPT A laser bias current alarm. Abnormal laser bias current has been detected. This alarm can only occur on units with an optical transmitter.
• In this practice, refer to the Task Index List to locate the procedure for replacing the failed unit.
• Replace the unit and return the defective unit to Fujitsu.
Table 4-37: CLEI-LBC Condition Parameters
AID Type
Default Notification Code Location Direction Service Affecting/
Non-Service Affecting
EQPT MN NEND NA NSA
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-33
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.20 CLEI-TEMP
Table 4-38 suggests corrective action for a Excessive Laser Transmit Temperature (CLEI-TEMP) Alarm Event. Table 4-39 lists Condition Parameters for CLEI-TEMP.
Table 4-38: CLEI-TEMP (Excessive Laser Transmit Temperature)—Alarm Event
AID Type Probable Cause Suggested Corrective Action
EQPT The laser temperature has increased. This condition type applies only to units with optical transmitters.
• In this practice, refer to the Task Index List to locate the procedure for replacing the failed unit.
• Replace the unit and return the defective unit to Fujitsu.
Table 4-39: CLEI-TEMP Condition Parameters
AID Type
Default Notification
CodeLocation Direction Service Affecting/
Non-Service Affecting
EQPT MN NEND NA NSA
Page 4-34 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.21 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 4-40 suggests corrective action for CPY Conditions (CPY-FILE-PRTL, CPY-FILE-FAIL, CPY-MEM-FAIL) Transient Condition. Table 4-41 lists Condition Parameters for CPY Conditions.
Table 4-40: CPY Conditions (CPY-FILE-PRTL, CPY-FILE-FAIL, CPY-MEM-FAIL)—Transient Condition
AID Type Probable Cause Suggested Corrective Action
FILE Attempted to copy file or memory when another copy file/memory is still active.
• Check SWDL LED on SV2H-DL/-DLB unit.
• Wait until LED is extinguished (or until COMPL MSG is received) before attempting to copy file/memory.
Table 4-41: CPY Condition Parameters
AID Type
Default Notification
Code Location Direction Service Affecting/
Non-Service Affecting
FILE NA NA NA NSA
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-35
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.22 CTNCLKDISTP and CTNCLKDISTS
• CTNCLKDISTP (Primary clock distribution cable is removed.)
• CTNCLKDISTS (Secondary clock distribution cable is removed.)
Table 4-42 suggests corrective action for a Linear ADM Clock Distribution Cable Failure (CTNCLKDISTP/CTNCLKDISTS) Alarm Event. Table 4-43 lists Condition Parameters for CTNCLKDISTP and CTNCLKDISTS.
Note: CTNCLKDISTP and CTNCLKDISTS apply only to the FLM 2400 ADM linear configuration.
Table 4-42: CTNCLKDISTP and CTNCLKDISTS (Linear ADM Clock Distribution Cable Failure)—Alarm Event
AID Type Probable Cause Suggested Corrective Action
COM The primary or secondary clock distribution cable between the linear ADM High-Speed Shelves has failed or has been removed.
• Verify the connection between the HS Shelves. Refer to Section 7.6, Verifying the External Clock and Connections, and the Shelf Installation practice, FJTU-320-560-200, Section 2.4, Connecting External Clock Cables (HS Shelf).
Table 4-43: CTNCLKDISTP and CTNCLKDISTS Condition Parameters
AID Type Default Notification Code Location Direction Service Affecting/
Non-Service Affecting
COM MN NEND NA NSA
Page 4-36 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.23 CTNEQPT1 Through CTNEQPT4 or CTNEQPT1S Through CTNEQPT4S
Table 4-44 suggests corrective action for a 78-Mb/s Cable Connection Failure (CTNEQPT1 through CTNEQPT4 or CTNEQPT1S through CTNEQPT4S) Alarm Event. Table 4-45 lists Condition Parameters for CTNEQPT.
Note: CTNEQPTnS applies only to the FLM 2400 ADM linear configuration.
These messages indicate a 78-Mb/s cable connection failure. The number at the end of the condition type shows where the problem is located:
• Number 1 indicates 600 ADM TRIB Shelf 1, HD TRIB with OC-3, or quadrant 3 if the shelf is an HD TRIB Shelf.
• Number 2 indicates 600 ADM TRIB Shelf 2, HD TRIB with OC-3, or quadrant 4 if the shelf is an HD TRIB Shelf.
Table 4-44: CTNEQPT1 Through CTNEQPT4 or CTNEQPT1SThrough CTNEQPT4S (78-Mb/s Cable Connection Failure)—Alarm Event
AID Type Probable Cause Suggested Corrective Action
EQPT A circuit failure has occurred on the 78-Mb/s cable connecting the HS Shelf with a tributary shelf, or the cable is not connected.
• Verify the cable connection. Begin by checking the connection on the tributary plug-in that terminated the cable.
• Check to see if the tributary plug-in that terminates the cable has failed or been removed. If a unit must be replaced, see the applicable procedure in Section 6, Replacing Units.
• Activate the bridge cable connection.
The HD TRIB Shelf HC2T-C12L unit has failed or been removed.
The HD TRIB Shelf MC6A-3BRD unit has failed or been removed.
The 600 ADM TRIB Shelf HC6A-6ELX has failed or been removed.
Both tributary shelf power supplies have failed.
If OC-3 HD TRIB Shelves are used, this alarm will be generated if the bridge cable connection has not been activated.
Table 4-45: CTNEQPT Condition Parameters
AID Type
Default Notification Code Location Direction Service Affecting/
Non-Service Affecting
EQPT CR/MN NEND NA SA/NSA
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-37
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
• Number 3 indicates 600 ADM TRIB Shelf 3, HD TRIB with OC-3, or quadrant 5 if the shelf is an HD TRIB Shelf.
• Number 4 indicates 600 ADM TRIB Shelf 4, HD TRIB with OC-3, or quadrant 6 if the shelf is an HD TRIB Shelf.
The S at the end of the condition type means that the shelf is connected to the slave HS Shelf in a linear ADM.
Page 4-38 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.24 CTNHSCONF
Table 4-46 suggests corrective action for a Linear ADM High-Speed Shelf Mismatch (CTNHSCONF) Alarm Event. Table 4-47 lists Condition Parameters for CTNHSCONF.
Table 4-46: CTNHSCONF (Linear ADM High-Speed Shelf Mismatch)—Alarm Event
AID Type Probable Cause Suggested Corrective Action
COM A failure has occurred because of a mismatch between the master and slave in an FLM 2400 ADM linear configuration.
Poor INT cable connection.
Incorrect MP2H unit placed in either shelf.
• Check the INT cable connection between the HS Shelves. Refer to the Shelf Installation practice, FJTU-320-560-200, Section 2.5, Connecting the Internal Cables from the High-Speed Shelf to the Tributary Shelves.
• Verify that the master shelf contains an MP2H-T12 unit and that the slave shelf contains an MP2H-SLV unit. If either of these units needs to be replaced, see Section 6.5, Replacing the Microprocessor (MP2H-xxx) Unit in the HS Shelf.
Table 4-47: CTNHSCONF Condition Parameters
AID Type
Default Notification
CodeLocation Direction Service Affecting/
Non-Service Affecting
COM CR NEND NA SA
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-39
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.25 CTNOHBCOM1 and CTNOHBCOM2
• CTNOHBCOM1 (Cable is removed for overhead communication 1.)
• CTNOHBCOM2 (Cable is removed for overhead communication 2.)
Table 4-48 suggests corrective action for a Linear ADM Master and Slave Shelf Interconnection Problem (CTNOHBCOM1/CTNOHBCOM2) Alarm Event. Table 4-49 lists Condition Parameters for CTNOHBCOM1 and CTNOHBCOM2.
Note: CTNOHBCOM1/2 applies only to the FLM 2400 ADM linear configuration.
Table 4-48: CTNOHBCOM1 and CTNOHBCOM2 (Linear ADM Master and Slave Shelf Interconnection Problem)—Alarm Event
AID Type Probable Cause Suggested Corrective Action
COM The INT LINK 2 or SW/SVC cable between the master and slave HS Shelves has failed or been removed.
• Verify that the cables are connected properly. Refer to the Shelf Installation practice, FJTU-320-560-200, Section 4.2, Connecting the Master and Slave HS Shelves for Linear ADM.
Table 4-49: CTNOHBCOM1 and CTNOHBCOM2 Condition Parameters
AID Type
Default Notification
CodeLocation Direction Service Affecting/
Non-Service Affecting
COM MN NEND NA NSA
Page 4-40 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.26 CTNTRIBCONF1 Through CTNTRIBCONF4
• CTNTRIBCONF1 (Mismatch failure of tributary configuration 1.)
• CTNTRIBCONF2 (Mismatch failure of tributary configuration 2.)
• CTNTRIBCONF3 (Mismatch failure of tributary configuration 3.)
• CTNTRIBCONF4 (Mismatch failure of tributary configuration 4.)
Table 4-50 suggests corrective action for a Tributary Shelf Configuration Mismatch (CTNTRIBCONF) Alarm Event. Table 4-51 lists Condition Parameters for CTNTRIBCONF.
Table 4-50: CTNTRIBCONF1 Through CTNTRIBCONF4 (Tributary Shelf Configuration Mismatch)—Alarm Event
AID Type Probable Cause Suggested Corrective Action
COM The INT cable(s) are not connected in accordance with the 78-Mb/s cable connection.
• Verify that the 78-Mb/s cables are connected to the intended shelf. For the HD TRIB Shelf, refer to the Plug-In Unit Installation practice, FJTU-320-560-220, Sections 6.6, 8.11, and 8.7. For the 600 TRIB Shelf, refer to FLM 600 ADM documentation set.
• Verify that the INT cables are connected to the intended shelf. Refer to the Shelf Installation practice, FJTU-320-560-200, Section 2.5, Connecting the Internal Cables from the High-Speed Shelf to the Tributary Shelves.
• Verify current revision and firmware compatibility being used in the MP2H and MP2T units. Call 1-800-USE-FTAC for assistance in determining current revision.
Table 4-51: CTNTRIBCONF Condition Parameters
AID Type
Default Notification
CodeLocation Direction Service Affecting/
Non-Service Affecting
COM CR NEND NA SA
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-41
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.27 DCCFAIL
Table 4-52 suggests corrective action for a Section Data Communications Channel Failure (DCCFAIL) Alarm Event. Table 4-53 lists Condition Parameters for DCCFAIL.
Table 4-52: DCCFAIL (Section Data Communications Channel Failure)—Alarm Event
AID Type Probable Cause Suggested Corrective Action
EC1 The section data communications channel (SDCC) on the incoming EC-1 line to the tributary has failed.
May also be caused by incompatible supervisory (SV) units and firmware.
• Verify that the far-end STS-1 source has not failed. If an EC-1 LOS alarm exists, clear that trouble first (see Section 4.3.55).Verify that the coax cable is installed on the correct channel.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 EC6A-24G or the HS2T-S1 unit is in service and has not failed. Refer to Section 6.15, Replacing High-Speed Switch (HS2T-xxxx) Unit in the HD TRIB Shelf, and Section 6.32, Replacing Embedded Channel (EC6A-24G/ -DL1) Unit in the FLM 600 ADM TRIB Shelf.
• Verify that the EC6A-24G or HS2T-S1 unit has the correct issue number to ensure firmware compatibility. Refer to the Application Engineering practice, FJTU-320-560-120, Section 5, Hardware/Firmware Compatibility, or call Fujitsu for technical assistance at 1-800-USE-FTAC (1-800-873-3822).
Page 4-42 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
OC3OC12
The OC-3 SDCC has failed.
Note: May also be caused by incompatible SV units and firmware.
• Check for a fiber cut and OC-3/OC-12 LOS alarms (see Section 4.3.55).
• At both the local and upstream sites, check for OC-3/OC-12 optical channel unit failure/removal alarms, <CLEI>-FLT (Section 4.3.18), and RMVD (Section 4.3.72) respectively.
• 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 EC6A-24G or HS2T-C3 unit is in service and has not failed. Refer to Section 6.15, Replacing High-Speed Switch (HS2T-xxxx) Unit in the HD TRIB Shelf, and Section 6.32, Replacing Embedded Channel (EC6A-24G/ -DL1) Unit in the FLM 600 ADM TRIB Shelf for replacement procedures.
• Verify that the option setting switch on the HS2T-C3 is set for OC-3/OC-12.
• Verify that the local and upstream EC6A-24G or HS2T-C3 unit has the correct issue number to ensure firmware compatibility. Refer to the Application Engineering practice, FJTU-320-560-120, Section 5, Hardware/Firmware Compatibility, or call Fujitsu for technical assistance at 1-800-USE-FTAC (1-800-873-3822).
OC48 The OC-48 SDCC has failed.
Note: May also be caused by incompatible SV units and firmware.
• Check for a fiber cut and OC-48 LOS alarms (see Section 4.3.55).
• At both the local and upstream sites, check for OC-48 optical channel unit failure/removal alarms. Refer to Sections 7.1 through 7.5 for information on checking the optical levels; and to Sections 6.10 and 6.11 in this practice for information on replacing the units.
• 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 local or upstream HS2H unit is in service and has not failed. Refer to Section 6.7, Replacing the High-Speed Switch (HS2H-xxxx) Unit in the HS Shelf.
• Verify that the local and upstream HS2H units have the correct issue number to ensure firmware compatibility. Refer to the Application Engineering practice, FJTU-320-560-120, Section 5, Hardware/Firmware Compatibility, or call Fujitsu for technical assistance at 1-800-USE-FTAC (1-800-873-3822).
Table 4-52: DCCFAIL (Section Data Communications Channel Failure)—Alarm Event (Cont.)
AID Type Probable Cause Suggested Corrective Action
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-43
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
Table 4-53: DCCFAIL Condition Parameters
AID Type
Default Notification
CodeLocation Direction Service Affecting/
Non-Service Affecting
EC1 MN NEND NA NSA
OC3 MN NEND NA NSA
OC12 MN NEND NA NSA
OC48 MN NEND NA NSA
Page 4-44 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.28 DEFKBYTE
Table 4-54 suggests corrective action for a Default K Byte Defect (DEFKBYTE) Alarm Event. Table 4-55 lists Condition Parameters for DEFKBYTE.
Note: DEFKBYTE is used only with the FLM 2400 ADM BLSR configuration.
Table 4-54: DEFKBYTE (Default K Byte Defect)—Alarm Event
AID Type Probable Cause Suggested Corrective Action
OC48 There is a topology mismatch on the ring, or the ring topology has not been initialized.
Note: May also result when some node on the ring is not capable of performing protection switching.
• Once the ring has been completely turned up, initialize the ring topology on any idle node in the ring. Refer to the corrective actions under the SWTOSWITCHED condition, Section 4.3.91, for the procedure to bring the node back to the idle state.
• Reseat or replace the malfunctioning unit(s).
Table 4-55: DEFKBYTE Condition Parameters
AID Type
Default Notification Code Location Direction Service Affecting/
Non-Service Affecting
OC48 MN NEND NSA
DN
610
4
RCV
DROPPEDSIGNAL
OC-48
2400 ADMHS & TRIBs
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-45
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.29 DEFKBYTE–PTHR
Table 4-56 suggests corrective action for a Default K Byte Defect–Pass-Through State (DEFKBYTE-PTHR) Standing Condition. Table 4-57 lists Condition Parameters for DEFKBYTE-PTHR.
Note: DEFKBYTE-PTHR is used only with the FLM 2400 ADM BLSR configuration.
Table 4-56: DEFKBYTE–PTHR (Default K Byte Defect–Pass-Through State)—Standing Condition
AID Type Probable Cause Suggested Corrective Action
OC48 (Same as for DEFKBYTE, but reported by a node in the pass-through state.)
There is a topology mismatch on the ring, or the ring topology has not been initialized.
Note: May also result when some node on the ring is not capable of performing protection switching.
(Same as for DEFKBYTE, but for a node in the pass-through state.)
• Once the ring has been completely turned up, initialize the ring topology on any idle node in the ring. Refer to the corrective actions under the SWTOSWITCHED condition, Section 4.3.91, for the procedure to bring the node back to the idle state.
• Reseat or replace the malfunctioning unit(s).
Table 4-57: DEFKBYTE-PTHR Condition Parameters
AID Type
Default Notification
CodeLocation Direction Service Affecting/
Non-Service Affecting
OC48 MN NEND NSA
DN
610
4
RCV
DROPPEDSIGNAL
OC-48
2400 ADMHS & TRIBs
Page 4-46 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.30 ECBOOT
Table 4-58 suggests corrective action for a Complete EC Software Booting (ECBOOT) Transient Condition. Table 4-59 lists Condition Parameters for ECBOOT.
Table 4-58: ECBOOT (Complete EC Software Booting)—Transient Condition
AID Type Probable Cause Suggested Corrective Action
EQPT EC software booting has been completed • No corrective action required
Table 4-59: ECBOOT Condition Parameters
AID Type Location Direction Service Affecting/
Non-Service Affecting
EQPT NEND NA NSA
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-47
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.31 ECRESTART
Table 4-60 suggests corrective action for an EC Software restart (ECRESTART) Transient Condition. Table 4-61 lists Condition Parameters for ECRESTART.
Table 4-60: ECRESTART (EC Software restart)—Transient Condition
AID Type Probable Cause Suggested Corrective Action
EQPT The EC software has been restarted • No corrective action required.
Table 4-61: ECRESTART Condition Parameters
AID Type Location Direction Service Affecting/
Non-Service Affecting
EQPT NEND NA NSA
Page 4-48 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.32 EXERFAIL
Table 4-62 suggests corrective action for an Exerciser failure (EXERFAIL) Transient Condition. Table 4-63 lists Condition Parameters for EXERFAIL.
Table 4-62: EXERFAIL (Exerciser failure)—Transient Condition
AID Type Probable Cause Suggested Corrective Action
OC48 Failure of unit HS2H, HT2H, or HR2H at one of the NEs, either NEND, FEND or at an NE in between.
• Determine the location of the failing NE by conducting a manual switch exerciser using the TL1 command OPR-PROTNSW-OC48. Refer to TL1 Commands in practice FJTU-320-560-274, Section 16.6, Operate Protection Switch for more detailed information. Begin the procedure by performing the manual switch at a closer NE, then at the next farthest NE, and at each NE thereafter until the failing NE is determined.
OC48 One of the provisioning parameters, such as node identification, has been entered incorrectly.
• Check provisioning and correct if necessary.
Table 4-63: EXERFAIL Condition Parameters
AID Type Location Direction Service Affecting/
Non-Service Affecting
OC48 NEND NA NSA
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-49
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.33 EXERPASS
Table 4-64 suggests corrective action for an Exerciser pass (EXERPASS) Transient Condition. Table 4-65 lists Condition Parameters for EXERPASS.
Table 4-64: EXERPASS (Exerciser pass)—Transient Condition
AID Type Probable Cause Suggested Corrective Action
OC48 Exerciser pass • No corrective action required.
Table 4-65: EXERPASS Condition Parameters
AID Type Location Direction Service Affecting/
Non-Service Affecting
OC48 NEND NA NSA
Page 4-50 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.34 FALLBACK
Table 4-66 suggests corrective action for System Software Reverting (FALLBACK) Transient Condition. Table 4-67 lists Condition Parameters for FALLBACK.
Table 4-66: FALLBACK (System Software Reverting)—Transient Condition
AID Type Probable Cause Suggested Corrective Action
COM System software reverting(fallback)
• No corrective action required.
Table 4-67: FALLBACK Condition Parameters
AID Type Location Direction Service Affecting/
Non-Service Affecting
COM NEND NA NSA
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-51
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.35 FILECONFIG–ACT
Table 4-68 suggests corrective action for a Mismatch Failure of File Configuration among Active Banks (FILECONFIG–ACT) Alarm Event. Table 4-69 lists Condition Parameters for FILECONFIG–ACT.
Table 4-68: FILECONFIG–ACT (Mismatch Failure of File Configuration Among Active Banks)—Alarm Event
AID Type Probable Cause Suggested Corrective Action
COM A mismatch failure of the file configuration among active banks.
• Download latest release to all NE units and switch to new load. Refer to the FLEXR SWDL User Guide, practice FJTU-320-920-100.
Table 4-69: FILECONFIG–ACT Condition Parameters
AID Type
Notification Code (Default) Location Direction Service Affecting/
Non-Service Affecting
COM MN NEND NA NSA
Page 4-52 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.36 FILECONFIG-STBY
Table 4-70 suggests corrective action for a Mismatch Failure of File Configuration among Standby Banks (FILECONFIG–STBY) Alarm Event. Table 4-71 lists Condition Parameters for FILECONFIG–STBY.
Table 4-70: FILECONFIG–STBY (Mismatch Failure of File Configuration Among Standby Banks)—Transient Condition
AID Type Probable Cause Suggested Corrective Action
COM A mismatch failure of the file configuration among standby banks.
• Verify all standby files with generic issue.
• Download latest release to the standby nonvolatile memory (NVM) of all NE units.
Table 4-71: FILECONFIG–STBY Condition Parameters
Aid Type Location Direction Service Affecting/
Non-Service Affecting
COM NEND NA NSA
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-53
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.37 FRCDSW
The Working/Protect entity has been switched to the Protect/Working entity, regardless of the fault operating status of the switched-to entity.
Table 4-72 suggests corrective action for a Forced Switch of Working/Protect to Protect/Working (FRCDSW) Standing Condition. Table 4-73 lists Condition Parameters for FRCDSW.
Table 4-72: FRCDSW (Forced Switch of Working/Protect to Protect/Working)—Standing Condition
AID Type Probable Cause Suggested Corrective Action
OC3 Protection switch for OC-3 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 forced switch is secured.
• Release the OC-3 protection switch.
OC12 Protection switch for OC-12 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 forced switch is secured.
• Release the OC-12 protection switch.
OC48 Protection switch for OC-48 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 forced switch is secured.
• Release the OC-48 protection switch.
STS1 Protection switch for STS-1 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 forced switch is secured.
• Release the STS-1 protection switch.
STS3C Protection switch for STS-3c 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 forced switch is secured.
• Release the STS-3c protection switch.
STS12C Protection switch for STS-12c 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 forced switch is secured.
• Release the STS-12c protection switch.
Page 4-54 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
Table 4-73: FRCDSW Condition Parameters
AID Type
Default Notifica
tion Code
Location Direction Service Affecting/Non-Service Affecting
COM MN NEND TMGTMGOUTPTMGOUTS
NA
OC3 MN NENDFEND
NA NSA
OC12 MN NENDFEND
NA NSA
OC48 MN NENDFEND
NA NSA
STS1 N NEND NA NSA
STS3C MN NEND NA NSA
STS12C MN NEND NA NSA
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-55
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.38 IMPAPS
Table 4-74 suggests corrective action for a Improper APS Codes Defect (IMPAPS) Alarm Event. Table 4-75 lists Condition Parameters for IMPAPS.
Note: IMPAPS is used only with the FLM 2400 ADM BLSR configuration.
Table 4-74: IMPAPS (Improper APS Codes Defect)—Alarm Event
AID Type Probable Cause Suggested Corrective Action
OC48 The HS2H unit has detected that the automatic protection switching codes are improper.
Note: May also occur if a node is mishandling an extra traffic indicator. This is a provisioning problem on the STS-1 channels 25 through 48.
• Reseat the HS2H-B1 unit at the near-end node and at the upstream node. If reseating the units does not clear the problem, replace the HS2H-B1 units. Refer to Section 6.7, Replacing the High-Speed Switch (HS2H-xxxx) Unit in the HS Shelf.
• Be sure that the STS channels 25 through 48 have been properly provisioned.
Table 4-75: IMPAPS Condition Parameters
AID Type
Default Notification
CodeLocation Direction Service Affecting/
Non-Service Affecting
OC48 MN NEND NSA
DN
610
4
RCV
DROPPEDSIGNAL
OC-48
2400 ADMHS & TRIBs
Page 4-56 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.39 IMPAPS–PTHR
Table 4-76 suggests corrective action for an Improper APS Codes Defect–Pass Through State (IMPAPS–PTHR) Standing Condition. Table 4-77 lists Condition Parameters for IMPAPS–PTHR.
Note: IMPAPS-PTHR is used only with the FLM 2400 ADM BLSR configuration.
Table 4-76: IMPAPS–PTHR (Improper APS Codes Defect–Pass Through State)—Standing Condition
AID Type Probable Cause Suggested Corrective Action
OC48 (Same as for IMPAPS, but reported by a node in the pass-through state.)
The HS2H unit has detected that the automatic protection switching codes are improper.
Note: May also occur if a node is mishandling an extra traffic indicator. This is a provisioning problem on the STS-1 channels 25 through 48.
(Same as for IMPAPS, but for a node in the pass-through state.)
• Reseat the HS2H-B1 unit at the near-end node and at the upstream node. If reseating the units does not clear the problem, replace the HS2H-B1 units. Refer to Section 6.7, Replacing the High-Speed Switch (HS2H-xxxx) Unit in the HS Shelf.
• Be sure that the STS channels 25 through 48 have been properly provisioned.
Table 4-77: IMPAPS–PTHR Condition Parameters
AID Type
Default Notification
CodeLocation Direction Service Affecting/
Non-Service Affecting
OC48 MN NEND NSA
DN
610
4
RCV
DROPPEDSIGNAL
OC-48
2400 ADMHS & TRIBs
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-57
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.40 INCONAPS
Table 4-78 suggests corrective action for an Inconsistent APS Codes Defect (INCONAPS) Alarm Event. Table 4-79 lists Condition Parameters for INCONAPS.
Note: INCONAPS is used only with the FLM 2400 ADM BLSR configuration.
Table 4-78: INCONAPS (Inconsistent APS Codes Defect)—Alarm Event
AID Type Probable Cause Suggested Corrective Action
OC48 The HS2H unit has detected that the automatic protection switching codes are inconsistent.
Note: May also be related to a loss-of-frame (LOF) alarm event.
• Verify the local receive optical levels and the upstream transmit optical levels. Clean the optical connectors. Refer to Sections 7.1 through 7.5.
• Reseat the HS2H-B1 unit at the near-end node and at the upstream node. If reseating the units does not clear the problem, replace the HS2H-B1 units. Refer to Section 6.7, Replacing the High-Speed Switch (HS2H-xxxx) Unit in the HS Shelf.
• Clear the LOF alarm (see Section 4.3.50).
Table 4-79: INCONAPS Condition Parameters
AID Type
Default Notification Code Location Direction Service Affecting/
Non-Service Affecting
OC48 MN NEND NSA
DN
610
4
RCV
DROPPEDSIGNAL
OC-48
2400 ADMHS & TRIBs
Page 4-58 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.41 INCONAPS-PTHR
Table 4-80 suggests corrective action for an Inconsistent APS Codes Defect–Pass-Through State (INCONAPS-PTHR) standing condition. Table 4-81 lists condition parameters for INCONAPS-PTHR.
Note: INCONAPS-PTHR is used only with the FLM 2400 ADM BLSR configuration.
Table 4-80: INCONAPS-PTHR (Inconsistent APS Codes Defect-Pass-Through State)—Standing Condition
AID Type Probable Cause Suggested Corrective Action
OC48 (Same as for INCONAPS, but reported by a node in the pass-through state.)
The HS2H unit has detected that the automatic protection switching codes are inconsistent.
Note: May also be related to an LOF alarm event.
(Same as for INCOAPS, but for a node in the pass-through state.)
• Verify the local receive optical levels and the upstream transmit optical levels. Clean the optical connectors. Refer to Sections 7.1 through 7.5.
• Reseat the HS2H-B1 unit at the near-end node and at the upstream node. If reseating the units does not clear the problem, replace the HS2H-B1 units. Refer to Section 6.7, Replacing the High-Speed Switch (HS2H-xxxx) Unit in the HS Shelf.
• Clear the LOF alarm. (See Section 4.3.50.)
Table 4-81: INCONAPS–PTHR Condition Parameters
AID Type
Default Notification
CodeLocation Direction Service Affecting/
Non-Service Affecting
OC48 MN NEND NSA
DN
610
4
RCV
DROPPEDSIGNAL
OC-48
2400 ADMHS & TRIBs
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-59
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.42 INIT-SYS-FAIL
Table 4-82 suggests corrective action for an Initialization Failure—Card removed or failed (INIT-SYS-FAIL) transient condition. Table 4-83 lists condition parameters for INIT-SYS-FAIL.
4.3.43 IPNOTREACH
Table 4-84 suggests corrective action for an IP Not Reachable condition.
4.3.44 IPREACHABLE
Table 4-85 suggests corrective action for an IP Reachable Condition.
Table 4-82: INIT-SYS-FAIL (Initialization Failure—Card Removed or Failed)—Transient Condition
AID Type Probable Cause Suggested Corrective Action
COM Initialization failure card removed or failed. Replace card.
Table 4-83: INIT–SYS–FAIL Condition Parameters
AID Type Location Direction Service Affecting/
Non-Service Affecting
NA NEND NA NSA
Table 4-84: IPNOTREACH (IP = xxx.xxx.xxx.xxx Not Reachable)—Transient Condition
AID Type Direction Probable Cause Suggested Corrective Action
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 4-85: IPREACHABLE (IP = xxx.xxx.xxx.xxx Reachable)—Transient Condition
AID Type Direction Probable Cause Suggested Corrective Action
COM NA IP address was reached successfully. NA
Page 4-60 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.45 ISOPLS
Table 4-86 suggests corrective action for an Isolation Pulse Generated (ISOPLS) Standing Condition. Table 4-87 lists Condition Parameters for ISOPLS.
Note: ISOPLS is used only with the FLM 2400 ADM BLSR configuration.
Table 4-86: ISOPLS (Isolation Pulse Generated)—Standing Condition
AID Type Probable Cause Suggested Corrective Action
EC1 An EC-1 test signal has been generated by command.
• Verify that the facility testing is complete.
• Disconnect the EC-1 test signal.
T1 A T1 test signal has been generated by command.
• Verify that the facility testing is complete.
• Disconnect the T1 test signal.
T3 A T3 test signal has been generated by command.
• Verify that the facility testing is complete.
• Disconnect the T3 test signal.
Table 4-87: ISOPLS Condition Parameters
AID Type
Default Notification Code Location Direction Service Affecting/
Non-Service Affecting
EC1 MN NEND NSA
T1 MN NEND NA NSA
T3 MN NEND NSA
DN
610
4
RCV
DROPPEDSIGNAL
OC-48
2400 ADMHS & TRIBs
DN
610
4
RCV
DROPPEDSIGNAL
OC-48
2400 ADMHS & TRIBs
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-61
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.46 LOCKIN
Table 4-88 suggests corrective action for a Lockin (LOCKIN) Alarm Event. Table 4-89 lists Condition Parameters for LOCKIN.
Note: LOCKIN does not apply to the FLM 2400 ADM BLSR configuration.
If the problem that caused the alarm has cleared, LOCKIN will remain in effect for 24 hours. To reset, set LIN=N, then set back to LIN=Y.
Table 4-88: LOCKIN (Lockin)—Alarm Event
AID Type Probable Cause Suggested Corrective Action
OC3OC12
Lockin has occurred on a tributary OC-3/OC-12 group. Some intermittent failure has caused more than four APS events within 10 minutes. This indication should be accompanied by other OC-3/OC-12 level alarms listed elsewhere in this practice (Sections 4.3.1 through 4.3.113).
• Retrieve the other OC-3/OC-12 level alarms and clear these troubles; refer to appropriate sections as listed in the Task Index List.
OC48 Lockin has occurred on the OC-48 group. Some intermittent failure has caused more than four APS events within 10 minutes. This indication should be accompanied by other OC-48 level alarms listed elsewhere in this practice (Sections 4.3.1 through 4.3.113).
This alarm occurs in 1+1 terminal and 1+1 linear ADM systems only.
• Retrieve the other OC-48 level alarms and clear these troubles; refer to appropriate sections as listed in the Task Index List.
Table 4-89: LOCKIN Condition Parameters
AID Type
Default Notification
CodeLocation Direction Service Affecting/
Non-Service Affecting
OC3 MN NEND NA NSA
OC12 MN NEND NA NSA
OC48 MN NEND NA NSA
Page 4-62 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.47 LOCKOUT
The Protection entity has been made unavailable to the Working entity, or vice versa, for protection switching.
Table 4-90 suggests corrective action for a Lock Out of Protection/Working (LOCKOUT) Standing Condition. Table 4-91 lists Condition Parameters for LOCKOUT.
Table 4-90: LOCKOUT (Lock Out of Protection/Working)—Standing Condition
AID Type Probable Cause Suggested Corrective Action
OC3 A protection switch for OC-3 (manually executed) has occurred for testing or maintenance reasons.
• Verify that the cause of operating the forced switch no longer exists or that authorization to release the lockout is secured.
• Release the protection switch.
OC12 A protection switch for OC-12 (manually executed) has occurred for testing or maintenance reasons.
• Verify that the cause of operating the forced switch no longer exists or that authorization to release the lockout is secured.
• Release the protection switch.
OC48 A protection switch for OC-48 (manually executed) has occurred for testing or maintenance reasons.
• Verify that the cause of operating the forced switch no longer exists or that authorization to release the lockout is secured.
• Release the protection switch.
Note: Not applicable to BLSR.
For BLSR, see Section 4.3.48, LOCKOUTP, or Section 4.3.49, LOCKOUTW, as applicable.
Table 4-91: LOCKOUT Condition Parameters
AID Type
Default Notification
CodeLocation Direction Service Affecting/
Non-Service Affecting
OC3 MN NEND
FEND
NA NSA
OC12 MN NEND
FEND
NA NSA
OC48 MN NEND
FEND
NA NSA(not applicable to BLSR)
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-63
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.48 LOCKOUTP
A lockout of Protection has been manually entered to disable ring protection switching on all spans.
Table 4-92 suggests corrective action for a Lock Out Protection (LOCKOUTP) Standing Condition. Table 4-93 lists Condition Parameters for LOCKOUTP.
Note: LOCKOUTP is used only with the FLM 2400 ADM BLSR configuration.
Table 4-92: LOCKOUTP (Lock Out Protection)—Standing Condition
AID Type Probable Cause Suggested Corrective Action
OC48 A lockout of protection switch for OC-48 (manually executed) has occurred for testing or maintenance reasons.
• Release the manually initiated lockout of protection switch to clear the standing condition. Direct the release command to the same node that processed the original lockout of protection command.
Table 4-93: LOCKOUTP Condition
AID Type
Default Notification Code Location Direction Service Affecting/
Non-Service Affecting
OC48 MN NEND
FEND
NA NSA
Page 4-64 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.49 LOCKOUTW
A lockout of Working has been manually entered to disable ring protection switching on a specific span.
Table 4-94 suggests corrective action for a Lock Out Working (LOCKOUTW) Standing Condition. Table 4-95 lists Condition Parameters for LOCKOUTW.
Note: LOCKOUTW is used only with the FLM 2400 ADM BLSR configuration.
Table 4-94: LOCKOUTW (Lock Out Working)—Standing Condition
AID Type Probable Cause Suggested Corrective Action
OC48 A lockout of working protection switch for OC-48 (manually executed) has occurred for testing or maintenance reasons.
• Release the manually initiated lockout of working protection switch to clear the standing condition. Direct the release command to the same node that processed the original lockout of working command.
Table 4-95: LOCKOUTW Condition Parameters
AID Type
Default Notification Code Location Direction Service Affecting/
Non-Service Affecting
OC48 MN NEND
FEND
NA NSA
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-65
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.50 LOF
Table 4-96 suggests corrective action for a Loss of Frame (LOF) Alarm Event. Table 4-97 lists Condition Parameters for LOF.
Table 4-96: LOF (Loss of Frame)—Alarm Event
AID Type Probable Cause Suggested Corrective Action
EC1 This indicates a framing problem on the incoming tributary STS-1 signal.
An STS-1 circuit is looped back at both ends of the path.
• Inspect all facilities related to the STS-1 link.
• Check the remote sites for STS-1 removal/failure alarms, RMVD (Section 4.3.72), and <CLEI>-FLT (Section 4.3.18) respectively.
• Check that the coax cable is installed on the correct channel.
• Switch to Protection unit. If problem clears, replace defective unit.
• If looped back at both ends of the path, release the loopbacks.
OC3OC12
A framing problem on the incoming OC-3/OC-12 signal.
An OC-3 circuit is looped back at both ends of the path.
• Inspect all facilities related to the OC-3/OC-12 link.
• Verify the local receive optical levels, and the upstream transmit optical levels. Clean the optical connectors. Refer to Sections 7.1 through 7.5.
• Check the upstream ADM for optical channel unit failure/removal, <CLEI>-FLT (Section 4.3.18), and RMVD (Section 4.3.72) respectively.
• Verify good optical connections to the local and far-end OC-3/-12 units and at the lightwave distribution frame (LDF) panels along the link.
• If looped back at both ends of the path, release the loopbacks.
OC48 A framing problem on the incoming OC-48 signal.
• Inspect all facilities related to the OC-48 link.
• Verify the local receive optical levels, and the upstream transmit optical levels. Clean the optical connectors. Refer to Sections 7.1 through 7.5.
• Check the upstream ADM for optical channel unit failure/removal alarms, <CLEI>-FLT (Section 4.3.18), and RMVD (Section 4.3.72) respectively.
• Verify good optical connections to the local and far-end OC-48 units and at the LDF panels along the link.
T1 A failure within the timing source (i.e., the building integrated timing supply (BITS) clock).
• Refer to the timing source vendor documentation for procedures to isolate and repair failure.
Page 4-66 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
T3 A failure within the DS3 far-end NE.
• If the expected DS3 is framed, initiate trouble analysis procedures for the far-end site (refer to the applicable alarm-clearing procedures in Section 4.2, Response Procedure).
• If the expected DS3 is unframed, provision the T3 facility for FMT=UNFR. See Section 7.7, Verifying the T3 Framing, for additional information.
• If looped back at both ends of the path, release the loopbacks.
The ADM is provisioned for a framed DS3 and is receiving an unframed DS3.
A DS3 circuit is looped back at both ends of the path.
Table 4-97: LOF Condition Parameters
AID Type
Default Notification
CodeLocation Direction Service Affecting/
Non-Service Affecting
EC1 CR NEND SA
OC3 CR/MN NEND TRMT SA/NSA
OC12 CR/MN NEND TRMT SA/NSA
OC48 CR/MN NEND SA/NSA
T1 CR/MN NEND NA SA/NSA
T3 CR NEND TRMT
RCV
SA
Table 4-96: LOF (Loss of Frame)—Alarm Event (Cont.)
AID Type Probable Cause Suggested Corrective Action
DN
610
3
TRMT
OC-48
ADDEDSIGNAL
2400 ADMHS & TRIBs
DN
610
4
RCV
DROPPEDSIGNAL
OC-48
2400 ADMHS & TRIBs
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-67
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.51 LOM
Table 4-98 suggests corrective action for a Loss of Synchronization Message (LOM) Alarm Event. Table 4-99 lists Condition Parameters for LOM.
Table 4-98: LOM (Loss of Synchronization Message)—Alarm Event
AID Type Probable Cause Suggested Corrective Action
SYNCIN A loss of synchronization message is detected.
• Verify that synchronous status messaging is properly configured.
• Make sure a HM2H unit is installed.
• Check the upstream ADM for optical channel unit failure or removal.
• A break occurred in the fiber-optic cable.
Table 4-99: LOM Condition Parameters
AID Type
Default Notification
CodeLocation Direction Service Affecting/
Non-Service Affecting
SYNCIN MN NEND NA NSA
Page 4-68 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.52 LOP
Table 4-100 suggests corrective action for a Loss of Pointer (LOP) Alarm Event. Table 4-101 lists Condition Parameters for LOP.
Table 4-100: LOP (Loss of Pointer)—Alarm Event
AID Type Probable Cause Suggested Corrective Action
EC1 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-560-272, Section 4, Time Slot Assignments/Cross-Connects.
OC3 OC12
A loss of pointer in the tributary OC-3/OC-12 signal.
• 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-560-272, Section 4, Time Slot Assignments/Cross-Connects.
OC48 A loss of pointer in the OC-48 line. The OC-48 line and the STS-1 are reporting a loss of pointer.
• Verify that the cross-connect level for this channel has been set to STS-1 at all upstream sites along the path.
• Verify that the entered drop cross-connect is an STS-1 cross-connect.
• Refer to the Turn-Up and Operation practice, FJTU-320-560-272, Section 4, Time Slot Assignments/Cross-Connects.
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-69
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
Table 4-101: LOP Condition Parameters
AID Type
Default Notification
CodeLocation Direction Service Affecting/
Non-Service Affecting
EC1 CR NEND SA
OC3 CR/MN NEND TRMT SA/NSA
OC12 CR/MN NEND TRMT SA/NSA
OC48 CR/MN NEND SA/NSA
DN
610
3
TRMT
OC-48
ADDEDSIGNAL
2400 ADMHS & TRIBs
DN
610
4
RCV
DROPPEDSIGNAL
OC-48
2400 ADMHS & TRIBs
Page 4-70 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.53 LOP3C
Table 4-102 suggests corrective action for a Loss of Pointer–STS-3c (LOP3C) Alarm Event. Table 4-103 lists Condition Parameters for LOP3C.
Table 4-102: LOP3C (Loss of Pointer–STS-3c)—Alarm Event
AID Type Probable Cause Suggested Corrective Action
OC3OC12
A loss of pointer in the tributary OC-3/OC-12 signal.
• Verify that the actual cross-connect entered for this facility is an STS-3c cross-connect.
• Refer to the Turn-Up and Operation practice, FJTU-320-560-272, Section 4, Time Slot Assignments/Cross-Connects.
• Verify that all upstream cross-connect levels are set to STS-3c.
OC48 This indicates a loss of pointer in the OC-48 line. The OC-48 line and the STS-3c are reporting a loss of pointer.
• Verify that the cross-connect level for this channel has been set to STS-3c at all upstream sites along the path.
• Refer to the Turn-Up and Operation practice, FJTU-320-560-272, Section 4, Time Slot Assignments/Cross-Connects.
• Verify that the drop cross-connect entered is an STS-3c cross-connect.
Table 4-103: LOP3C Condition Parameters
AID Type
Default Notification Code Location Direction Service Affecting/
Non-Service Affecting
OC3 CR/MN NEND SA/NSA
OC12 CR/MN NEND TRMT SA/NSA
OC48 CR/MN NEND SA/NSA
DN
610
3
TRMT
OC-48
ADDEDSIGNAL
2400 ADMHS & TRIBs
DN
610
4
RCV
DROPPEDSIGNAL
OC-48
2400 ADMHS & TRIBs
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-71
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.54 LOP12C
Table 4-104 suggests corrective action for a Loss of Pointer–STS-12c (LOP12C) Alarm Event. Table 4-105 lists Condition Parameters for LOP12C.
Table 4-104: LOP12C (Loss of Pointer–STS-12c)—Alarm Event
AID Type Probable Cause Suggested Corrective Action
OC12 A loss of pointer in the tributary OC-12 signal.
• Verify that the actual cross-connect entered is an STS-12c cross-connect.
• Verify that all cross-connect levels are set to STS-12c.
• Refer to the Turn-Up and Operation practice, FJTU-320-560-272, Section 4, Time Slot Assignments/Cross-Connects.
OC48 A loss of pointer in the OC-48 line. The OC-48 line and the STS-12c are reporting a loss of pointer.
• Verify that the cross-connect level for this channel has been set to STS-12c at all upstream sites along the path.
• Verify that the drop cross-connect entered is an STS-12c cross-connect.
• Refer to the Turn-Up and Operation practice, FJTU-320-560-272, Section 4, Time Slot Assignments/Cross-Connects.
Table 4-105: LOP12C Condition Parameters
AID Type
Default Notification Code Location Direction Service Affecting/
Non-Service Affecting
OC12 CR/MN NEND SA/NSA
OC48 CR/MN NEND SA/NSA
DN
610
3
TRMT
OC-48
ADDEDSIGNAL
2400 ADMHS & TRIBs
DN
610
4
RCV
DROPPEDSIGNAL
OC-48
2400 ADMHS & TRIBs
Page 4-72 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.55 LOS
Table 4-106 suggests corrective action for a Loss of Signal–STS-12c (LOS) Alarm Event. Table 4-107 lists Condition Parameters for LOS.
Table 4-106: LOS (Loss of Signal)—Alarm Event
AID Type Probable Cause Suggested Corrective Action
EC1 A loss of signal on an EC-1 interface input.
• Check for an STS-1 source NE failure/removal, <CLEI>-FLT (Section 4.3.18), and RMVD (Section 4.3.72) respectively.
• Check that the coax cable is installed on the correct channel.
OC3 OC12
An OC-3/OC-12 tributary loss of signal.
• Check the upstream ADM for optical channel unit failure/removal, <CLEI>-FLT (Section 4.3.18), and RMVD (Section 4.3.72) respectively.
• Check for a fiber cut.
• Verify the receive optical levels.
• Verify good optical connections to the local and far-end OC-3/OC-12 units and at the lightwave distribution frame (LDF) panels along the link. Refer to Sections 7.1 through 7.5.
OC48 An OC-48 tributary loss of signal.
• Check the upstream ADM for optical channel unit failure/removal, <CLEI>-FLT (Section 4.3.18), and RMVD (Section 4.3.72), respectively. If the unit is not operating per specification and must be replaced, refer to Section 6.10, Replacing the High-Speed Transmit Channel (HT2H-xxxx) Unit in the HS Shelf, and Section 6.11, Replacing High-Speed Receive Channel (HR2H-xxxx) Unit in the HS Shelf in this practice.
• Check for a fiber cut.
• Verify the receive optical levels. Refer to Sections 7.1 through 7.5.
• Verify good optical connections to the local and far-end OC-3 or OC-12 units and at the LDF panels along the link. Refer to Sections 7.1 through 7.5.
T1 A loss of signal caused by a timing supply failure or a DS1 cable failure.
• Refer to Section 7.6, Verifying the External Clock and Connections (in this practice), and to the Shelf Installation practice, FJTU-320-560-200, Section 2.4, Connecting External Clock Cables (HS Shelf), and Section 2.15, Connecting the DS1 Out Synchronization Cables (HD Tributary Shelf).
• Refer to the timing source vendor documentation.
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-73
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
T3 A loss of signal caused by a DS3 NE failure on an incoming DS3.
• Verify that the cable connections between the DS-X and NE are secure.
• Initiate trouble analysis procedures for the DS-X or asynchronous equipment site.
• If the signal leaving the far-end site is “good,” replace the DS3 cable.
• Switch to protection unit. If problem clears, replace the defective unit. Refer to the Task Index List to find the appropriate section.
Table 4-107: LOS Condition Parameters
AID Type
Default Notification
CodeLocation Direction Service Affecting/
Non-Service Affecting
EC1 CR NEND SA
OC3 CR/MN NEND TRMT SA/NSA
OC12 CR/MN NEND TRMT SA/NSA
OC48 CR/MN NEND SA/NSA
T1 CR/MN NEND NA SA/NSA
T3 CR NEND TRMT SA
Table 4-106: LOS (Loss of Signal)—Alarm Event (Cont.)
AID Type Probable Cause Suggested Corrective Action
DN
610
3
TRMT
OC-48
ADDEDSIGNAL
2400 ADMHS & TRIBs
DN
610
4
RCV
DROPPEDSIGNAL
OC-48
2400 ADMHS & TRIBs
Page 4-74 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.56 LSQL
Table 4-108 suggests corrective action for a Persistent Line Squelching (LSQL) Standing Condition. Table 4-109 lists Condition Parameters for LSQL.
Note: LSQL is used only with the FLM 2400 ADM BLSR configuration.
Table 4-108: LSQL (Persistent Line Squelching)—Standing Condition
AID Type Probable Cause Suggested Corrective Action
OC48 An STS path on the reporting OC-48 line has been squelched to avoid a misconnection.
The STS path squelch occurs when the source or destination node for that path becomes isolated by:
• Multiple line failures
• A line failure and a conflicting forced switch command
• A source or destination nodal failure
• More than one forced switch active on the ring.
• Retrieve the OC-48 line conditions that may have caused a source or destination node to become isolated.Refer to the corrective actions for clearing those conditions. Refer to the Task Index List of this practice to locate the specific condition(s).
Table 4-109: LSQL Condition Parameters
AID Type
Default Notification Code Location Direction Service Affecting/
Non-Service Affecting
OC48 MN NEND NSA
DN
610
3
TRMT
OC-48
ADDEDSIGNAL
2400 ADMHS & TRIBs
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-75
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.57 MAN
Table 4-110 suggests corrective action for a Manually Caused Abnormal Condition (MAN) Alarm Event. Table 4-111 lists Condition Parameters for MAN.
Table 4-110: MAN (Manually Caused Abnormal Condition)—Alarm Event
AID Type Probable Cause Suggested Corrective Action
COM The system is in an operator-caused abnormal condition (manual, forced, or lockout protection switching, or loopback).
• Corrective action is not necessarily required. The Manual condition will automatically clear when the manual switch, forced switch, loopback, or lockout condition is removed by the operator.
Table 4-111: MAN Condition Parameters
AID Type
Default Notification Code Location Direction Service Affecting/
Non-Service Affecting
COM MN NEND NA NSA
Page 4-76 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.58 MANSW (Working/Protect)
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 4-112 suggests corrective action for a Manual Switch of Working/Protect to Protect/Working (MANSW) Standing Condition. Table 4-113 lists Condition Parameters for MANSW (Working/Protect).
Table 4-112: MANSW (Working/Protect) (Manual Switch of Working/Protect to Protect/Working)—Standing Condition
AID Type Probable Cause Suggested Corrective Action
EQPT The Equipment Protection Switch 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.
• Release the Protection Switch.
OC3 The OC-3 Protection Switch 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.
• Release the Protection Switch.
OC12 The OC-12 Protection Switch 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.
• Release the Protection Switch.
OC48 The OC-48 Protection Switch 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.
• Release the Protection Switch.
STS1 The STS-1 Protection Switch 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.
• Release the Protection Switch.
STS3C The STS-3c Protection Switch 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.
• Release the Protection Switch.
STS12C The STS-12c Protection Switch 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.
• Release the Protection Switch.
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-77
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
Table 4-113: MANSW Condition Parameters
AID Type
Default Notification
CodeLocation Direction Service Affecting/
Non-Service Affecting
COM MN NEND TMG
TMGOUTP
TMGOUTS
NSA
EQPT MN NEND NA NSA
OC3 MN NEND
FEND
NA NSA
OC12 MN NEND
FEND
NA NSA
OC48 MN NEND
FEND
NA NSA
STS1 MN NEND NA NSA
STS3C MN NEND NA NSA
STS12C MN NEND NA NSA
Page 4-78 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.59 MANSW (Clock)
Table 4-114 suggests corrective action for a Manual Switch for Clock Source (MANSW) Standing Condition. Table 4-115 lists Condition Parameters for MANSW (Clock).
Table 4-114: MANSW (Clock) (Manual Switch for Clock Source)—Standing Condition
AID Type Probable Cause Suggested Corrective Action
COM The synchronization clock source has been manually switched from the default to an alternate source 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.
• Release the synchronous switch.
Table 4-115: MANSW (Clock) Condition Parameters
AID Type Default Notification Code Location Direction Service Affecting/
Non-Service Affecting
COM MN NEND TMG
TMGOUTP
TMGOUTS
NSA
EQPT MN NEND NA NSA
OC3 MN NEND
FEND
NA NSA
OC12 MN NEND
FEND
NA NSA
OC48 MN NEND
FEND
NA NSA
STS1 MN NEND NA NSA
STS3C MN NEND NA NSA
STS12C MN NEND NA NSA
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-79
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.60 MISMATAPS
Table 4-114 suggests corrective action for a Node ID Mismatch Defect (MISMATAPS) Alarm Event. Table 4-115 lists Condition Parameters for MISMATAPS.
Note: MISMATAPS is used only with the FLM 2400 ADM BLSR configuration.
Table 4-116: MISMATAPS (Node ID Mismatch Defect)—Alarm Event
AID Type Probable Cause Suggested Corrective Action
OC48 The source node ID is not adjacent to the destination node ID.
May also be caused if a source or destination node ID contains a value which has not been provisioned into the ring map.
• Initialize topology.
Table 4-117: MISMATAPS Condition Parameters
AID Type
Default Notification
CodeLocation Direction Service Affecting/
Non-Service Affecting
OC48 MN NEND NSA
DN
610
4
RCV
DROPPEDSIGNAL
OC-48
2400 ADMHS & TRIBs
Page 4-80 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.61 MISMOUNT
The Network Element does not recognize the Circuit Card in a given slot.
Table 4-118 suggests corrective action for a Mismounted Unit (MISMOUNT) Standing Condition. Table 4-119 lists Condition Parameters for MISMOUNT.
Table 4-118: MISMOUNT (Unit Is Mismounted)—Standing Condition
AID Type Probable Cause Suggested Corrective Action
EQPT Circuit card is not fully installed in its slot.
Installed circuit card is not the correct card for that slot.
• Refer to the Plug-In and Unit Installation practice, FJTU-320-560-220,Section 2.5, Removing and Installing Optical, Multiplexer/Demultiplexer, and Electrical Interface Units , for circuit card installation procedure.
• Verify that the correct slot has been chosen for installing the card.
• Verify that the correct card for the slot has been chosen.
• Verify that the correct card has been designated in the Engineering Order.
Table 4-119: MISMOUNT Condition Parameters
AID Type
Default Notification
CodeLocation Direction Service Affecting/
Non-Service Affecting
EQPT MN NEND NA NSA
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-81
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.62 MSGCHG
These messages indicate a change in quality level of the synchronous status message. Table 4-120 defines the synchronization status messaging quality levels.
Example: MSGCHGRES-STU indicates a change in the synchronization quality level from RES to STU.
• MSGCHGRES-PRS/-STU/-ST2/-ST3/-SIC/-ST4/-DUS/-FAIL/-NA
• MSGCHGPRS-STU/-ST2/-ST3/-SIC/-ST4/-DUS/-RES/-FAIL/-NA
• MSGCHGSTU-PRS/-ST2/-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.
Table 4-120: Synchronization Status Messaging Quality Level Values
Acronym Description Quality Level
PRS PRS Traceable 1
STU Synchronized–Traceability Unknown 2
ST2 Traceable Stratum 2 Holdover 3
ST3 Traceable Stratum 3 Holdover 4
SICa
a The acronym SIC has been changed to SMC in GR-253-CORE Issue 2 but the quality level and values remain the same.
Traceable SONET Clock Self-Timed 5
ST4 Traceable Stratum 4 Free-Run 6
DUS Don’t Use for Sync 7
RES Reserved for Network Synchronization Use User Assigns
Page 4-82 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
Table 4-121 suggests corrective action for a Synchronization Quality Level Change (MSGCHG) Transient Condition. Table 4-122 lists Condition Parameters for MSGCHG.
Table 4-121: MSGCHG (Synchronization Quality Level Change)—Transient Condition
AID Type Probable Cause Suggested Corrective Action
SYNCIN Synchronization message degrade or upgrade is detected.
• The HM2H unit is defective.
• Check the upstream ADM for optical channel unit failure or removal.
• A break occurred in the fiber-optic cable.
Table 4-122: MSGCHG Condition Parameter
AID Type Location Direction Service Affecting/
Non-Service Affecting
SYNCIN NEND NA NSA
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-83
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.63 PCASQL
Table 4-123 suggests corrective action for a Squelched PCA Channel (PCASQL) Standing Condition. Table 4-124 lists Condition Parameters for PCASQL.
Note: PCASQL is used only with the FLM 2400 ADM BLSR configuration.
Table 4-123: PCASQL (PCA Channel Is Squelched)—Standing Condition
AID Type Probable Cause Suggested Corrective Action
COM Extra traffic carried on Protection channel(s) has been squelched due to a protection switch.
• Clear the protection switch.
Table 4-124: PCASQL Condition Parameters
AID Type
Default Notification Code Location Direction Service Affecting/
Non-Service Affecting
COM MN NEND NA NSA
Page 4-84 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.64 PDI-ALL
Table 4-125 suggests corrective action for a Payload Defect Indication (PDI) alarm event. Table 4-126 lists condition parameters for PDI-ALL.
Table 4-125: PDI Code—Alarm Event
AID Type Probable Cause Suggested Corrective Action
STS3C Five consecutive identical PDI codes are received within 5 ms.
Provision the NE by selecting PDISD = Y, so that path switching is accomplished.
Table 4-126: PDI-ALL Condition Parameters
AID Type
Default Notification Code Location Direction Service Affecting/
Non-Service Affecting
STS3C CR/MN NEND RCV SA/NSA
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-85
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.65 PDI-n
Table 4-127 suggests corrective action for a Payload Defect Indication (PDI) alarm event-Code n Received (n = 1~27, ALL). Table 4-128 lists condition parameters for PDI-n.
4.3.66 PINGTIMEOUT
Table 4-129 suggests corrective action for an IP Reachable Condition.
Table 4-127: PDI Code n Received (n = 1~27, ALL)—Alarm Event
AID Type Probable Cause Suggested Corrective Action
STS1 Five consecutive identical PDI codes are received within 5 ms.
Provision the NE by selecting PDISD = Y, so that path switching is accomplished.
Table 4-128: PDI-n Condition Parameters
AID Type
Default Notification
CodeLocation Direction Service Affecting/
Non-Service Affecting
STS1 CR/MN NEND RCV SA/NSA
Table 4-129: PINGTIMEOUT (Ping Request Times Out)—Transient Condition
AID Type Direction Probable Cause Suggested Corrective Action
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.
Page 4-86 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.67 PLM
Table 4-130 suggests corrective action for a Payload Label Mismatch (PLM) Alarm Event. Table 4-131 lists Condition Parameters for PLM.
Table 4-130: PLM (Payload Label Mismatch)—Alarm Event
AID Type Probable Cause Suggested Corrective Action
STS1 Signal label within the C2 byte in the received STS-1 does not match the expected NE signal label.
Provision the NE at the receiving end (EC-1 and OC-3 interface) by setting the following:
• Set expected payload (EXPSLB) by (ED-SYS-STS-1/STS-3)
• Enable PLM by selecting PLMOPT = Y.
Table 4-131: PLM Condition Parameters
AID Type
Default Notification
CodeLocation Direction Service Affecting/
Non-Service Affecting
STS1 CR/MN NEND RCV SA/NSA
STS3C CR/MN NEND RCV SA/NSA
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-87
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.68 RAI
Table 4-132 suggests corrective action for a Remote Alarm Indication (RAI) Alarm Event. Table 4-133 lists Condition Parameters for RAI.
Table 4-132: RAI (Remote Alarm Indication)—Alarm Event
AID Type Probable Cause Suggested Corrective Action
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.
• 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.
Table 4-133: RAI Condition Parameters
AID Type
Default Notification
CodeLocation Direction
Service Affecting/Non-Service Affecting
T3 CR NEND SA
DN
610
3
TRMT
OC-48
ADDEDSIGNAL
2400 ADMHS & TRIBs
Page 4-88 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.69 RESETCOMPL
This message is generated at the conclusion of a central processing unit (CPU) reset.
Table 4-134 suggests corrective action for a Initial/Reset Process Is Complete (RESETCOMPL) Transient Condition. Table 4-135 lists Condition Parameters for RESETCOMPL.
Table 4-134: RESETCOMPL (Initial/Reset Process Is Complete)—Transient Condition
AID Type Probable Cause Suggested Corrective Action
COM This message generated at the conclusion of a CPU reset.
• No action required.
Table 4-135: RESETCOMPL Condition Parameters
AID Type Location Direction Service Affecting/
Non-Service Affecting
COM NEND NA NSA
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-89
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.70 RFI
This condition type indicates a remote failure indication. This alarm has replaced FERF and YEL.
Table 4-136 suggests corrective action for a Remote Failure Indication (RFI) Alarm Event. Table 4-137 lists Condition Parameters for RFI.
Table 4-136: RFI (Remote Failure Indication)—Alarm Event
AID Type Probable Cause Suggested Corrective Action
EC1 The locally received STS-1 signal contains an RFI.
• Check for MC6A-ST1E unit failure/removal alarms, <CLEI>-FLT (Section 4.3.18) and RMVD (Section 4.3.72) respectively. If the unit requires replacement, refer to Section 6.21, Replacing DS3/EC-1 Interface (MC6A-D3/ -D3E2/-ST1E/-ST1P) Unit in the HD TRIB Shelf.
• Verify that the coax cable is installed on the correct channel.
The local MC6A-ST1E is sending a bad STS-1 to the remote ADM.
OC3OC12
The locally received tributary OC-3/OC-12 signal contains an RFI.
• Verify the output of the local optical channel unit for level degradation/dirty optical connectors. Clean the optical connectors. Refer to Sections 7.1 through 7.5.
• Query the far-end ADM to determine the defects found.
• Based on the condition type(s) retrieved at the far end, refer to the Task Index List for condition type troubleshooting.
The local OC-3/OC-12 channel unit is sending a bad OC-3/OC-12 signal to the remote ADM.
The far-end OC-3/OC-12 unit has failed.
OC48 The locally received tributary OC-48 signal contains an OC-48 RFI.
• Check the output of the local optical channel unit for level degradation/dirty optical connectors. Clean the optical connectors. Refer to Sections 7.1 through 7.5.
• Query the far-end ADM to determine the defects found.
• Based on the condition type(s) retrieved at the far end, refer to the Task Index List for condition type troubleshooting.
The local OC-48 channel unit is sending a bad OC-48 signal to the remote ADM.
The far-end OC-48 receiver has failed.
STS1 The STS-1 signal demultiplexed from the OC-48 contains an STS-1 RFI.
• Query the far-end ADM to determine the defects found.
• Based on the condition type(s) retrieved at the far end, refer to the Task Index List for condition type troubleshooting.
The far-end ADM has detected STS-1 defects coming from the local site.
Page 4-90 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
Table 4-137: RFI Condition Parameters
AID Type
Default Notification Code Location Direction Service Affecting/
Non-Service Affecting
EC1 CR NEND SA
OC3 CR/MN NEND TRMT SA/NSA
OC12 CR/MN NEND TRMT SA/NSA
OC48 CR/MN NEND SA/NSA
DN
610
3
TRMT
OC-48
ADDEDSIGNAL
2400 ADMHS & TRIBs
DN
610
4
RCV
DROPPEDSIGNAL
OC-48
2400 ADMHS & TRIBs
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-91
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.71 RFI-SRV
Table 4-138 suggests corrective action for a Remote Failure Indication—Server Defect Received (RFI-SRV) Alarm Event. Table 4-139 lists Condition Parameters for RFI-SRV.
Table 4-138: RFI-SRV (RFI-Server Defect Received)—Alarm Event
AID Type Probable Cause Suggested Corrective Action
STS1 RFI-server defect received. • Retrieve alarms and correct.
Table 4-139: RFI-SRV Condition Parameters
AID Type
Default Notification Code Location Direction Service Affecting/
Non-Service Affecting
STS1 CR NEND RCV SA
Page 4-92 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.72 RMVD
Table 4-140 suggests corrective action for a Plug-in Unit Removed (RMVD) Alarm Event. Table 4-141 lists Condition Parameters for RMVD.
Table 4-140: RMVD (Plug-in Unit Removed)—Alarm Event
AID Type Probable Cause Suggested Corrective Action
EQPT 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 4-141: RMVD Condition Parameters
AID Type
Default Notification Code Location Direction Service Affecting/
Non-Service Affecting
EQPT CR/MN NEND NA SA/NSA
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-93
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.73 SQLTM-1/-2
Table 4-142 suggests corrective action for a Squelch Table Mismatch–High-Speed Group 1 and Group 2 (SQLTM-1/-2) Alarm Event. Table 4-143 lists Condition Parameters for SQLTM-1/-2.
Note: SQLTM-1/2 is used only with the FLM 2400 ADM BLSR configuration.
Table 4-142: SQLTM-1/-2 (Squelch Table Mismatch–High-Speed Group 1 and Group 2)—Alarm Event
AID Type Probable Cause Suggested Corrective Action
COM This alarm is raised as a circuit is being added to or deleted from a bidirectional line-switched ring (BLSR).
• If the circuit is being added: This alarm will clear after the circuit has been completely built into the ring by adding all the necessary cross-connections.
• If the circuit is being deleted: This alarm will clear after the circuit has been completely removed from the ring by deleting all the necessary cross-connections.
• Be sure that STS channels 1 through 24 have been properly provisioned.
• Clear the signal failure and then initialize topology.
If the alarm is SQLTM-1, this means that the circuit assigned to the high-speed facility Group 1 (carried by HR2H-1 and HT2H-2) has not been cross-connected at the other downstream nodes.
If the alarm is SQLTM-2, this means that the circuit assigned to the high-speed facility Group 1 (carried by HR2H-2 and HT2H-1) has not been cross-connected at the other downstream nodes.
May also be caused by incomplete provisioning of the STS-1 channels.
May be caused by a signal failure followed by a command to initialize topology.
Table 4-143: SQLTM–1/-2 Condition Parameters
AID Type
Default Notification
CodeLocation Direction Service Affecting/
Non-Service Affecting
COM MN NEND NA NSA
Page 4-94 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.74 SSAIS
Table 4-144 suggests corrective action for an Alarm Indication Signal Detected–Service Selector (SSAIS) Alarm Event. Table 4-145 lists Condition Parameters for SSAIS.
Table 4-144: SSAIS (Alarm Indication Signal Detected–Service Selector)—Alarm Event
AID Type Probable Cause Suggested Corrective Action
STS1 STS3C STS12C
The STS signal demultiplexed from the OC-48 contains an AIS. This AIS signal resulted from an upstream failure along the STS path that passed through the Service Selector. The Service Selector is located upstream from the logged-on NE. Examples of possible failures include the following:
• OC-48 failures, such as an LOS
• T3 input failures, such as a T3 LOS.
If no other network alarms exist, this alarm is probably caused by a bad 78-Mb/s cable connection at the Add site.
• Check for an upstream OC-48 signal failure.
• Check for a service-affecting alarm where the tributary signal enters the far end of the network. Clear these alarms. (Refer to Task Index List for applicable alarms.)
• At the Add site, first verify the connection on the tributary units, such as the HC2T-MDL. Refer to the Shelf Installation practice, FJTU-320-560-200, Task Index List, to locate the applicable section.
• Verify the good condition of the 78-Mb/s cables along the path.
STS1 STS3C STS12C
The STS signal demultiplexed from the OC-48 contains an AIS. This AIS signal resulted from a downstream failure along the STS path that passed through the Service Selector. The Service Selector is located downstream from the logged-on NE. Examples of possible failures include the following:
• OC-48 failures, such as an LOS
• T3 input failures, such as a T3 LOS.
If no other network alarms exist, this alarm is probably caused by a bad 78-Mb/s cable connection at the add site.
• Check for a downstream OC-48 signal failure.
• Check for a service-affecting alarm where the tributary signal exits the far end of the network. Clear these alarms. (Refer to Task Index List for applicable alarms.)
• At the add site, first verify the connection on the tributary units, such as the HC2T-MDL. Refer to the Shelf Installation practice, FJTU-320-560-200, Task Index List, to locate the applicable section.
• Verify the good condition of the 78-Mb/s cables along the path.
Table 4-145: SSAIS Condition Parameters
AID Type
Default Notification
CodeLocation Direction Service Affecting/
Non-Service Affecting
STS1 CR/MN NEND RCVTRMT
SA/NSA
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-95
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
Note: SSAIS is used only with the FLM 2400 ADM BLSR configuration.
STS3C CR/MN NEND RCVTRMT
SA/NSA
STS12C CR/MN NEND RCVTRMT
SA/NSA
Table 4-145: SSAIS Condition Parameters
AID Type
Default Notification
CodeLocation Direction Service Affecting/
Non-Service Affecting
Page 4-96 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.75 SSFRCDSW
The active path has been manually switched from the path selected by the Service Selector to the nonselected path, regardless of the fault operating status of the switched-to path.
Table 4-146 suggests corrective action for a Forced Switch–Service Selector (SSFRCDSW) Standing Condition. Table 4-147 lists Condition Parameters for SSFRCDSW.
Note: SSFRCDSW is used only with the FLM 2400 ADM BLSR configuration.
Table 4-146: SSFRCDSW (Forced Switch–Service Selector)—Standing Condition
AID Type Probable Cause Suggested Corrective Action
STS1STS3CSTS12C
Forced protection switch for STS-1/STS-3c/STS-12c 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 forced switch is secured.
• Release the protection switch.
Table 4-147: SSFRCDSW Condition Parameters
AID Type
Default Notification Code Location Direction Service Affecting/
Non-Service Affecting
STS1 MN NEND NA NSA
STS3C MN NEND NA NSA
STS12C MN NEND NA NSA
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-97
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.76 SSSWINS
The insertion path is one of two path segments between the drop-and-continue point on one BLSR ring and the Service Selector point on the other BLSR ring.The insertion path is the path that carries the signal directly from the drop-and-continue point to the Service Selector point.
Table 4-148 suggests corrective action for a Service Selector Switched to Insertion Path (SSSWINS) Transient Condition. Table 4-149 lists Condition Parameters for SSSWINS.
Note: SSWINS is used only with the FLM 2400 ADM BLSR configuration.
Table 4-148: SSSWINS (Service Selector Switched to Insertion Path)—Transient Condition
AID Type Probable Cause Suggested Corrective Action
STS1 STS3C STS12C
The Service Selector has detected a degradation in the active through path relative to the insertion path.
There may be trouble in the through path between the drop-and-continue point and the Service Selector point.
• Verify that there are no alarms present on the through path.
• Monitor the through path for PM threshold-crossing events.
Table 4-149: SSSWINS Condition Parameters
AID Type Location Direction Service Affecting/
Non-Service Affecting
STS1 NEND NA NSA
STS3C NEND NA NSA
STS12C NEND NA NSA
Page 4-98 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.77 SSSWTHR
The through path is one of two path segments between the drop-and-continue point on one BLSR ring and the Service Selector point on the other BLSR ring.The through path is the path that carries the signal sent from the drop-and-continue point through intermediate nodes on each ring and then on to the Service Selector point.
Table 4-150 suggests corrective action for a Service Selector Switched to Through Path (SSSWTHR) Transient Condition. Table 4-151 lists Condition Parameters for SSSWTHR.
Note: SSWTHR is used only with the FLM 2400 ADM BLSR configuration.
Table 4-150: SSSWTHR (Service Selector Switched to Through Path)—Transient Condition
AID Type Direction Probable Cause Suggested Corrective Action
STS1STS3CSTS12C
NA The Service Selector has detected a degradation in the active insertion path relative to the through path.
There may be trouble in the insertion path between the drop-and-continue point and the Service Selector point.
• Verify no alarms on the insertion path.
• Monitor the insertion path for PM threshold-crossing events.
Table 4-151: SSSWTHR Condition Parameters
AID Type Location Direction Service Affecting/
Non-Service Affecting
STS1 NEND NA NSA
STS3C NEND NA NSA
STS12C NEND NA NSA
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-99
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.78 SSUNEQ
Table 4-152 suggests corrective action for an Unequipped Code Received–Service Selector (SSUNEQ) Alarm Event. Table 4-153 lists Condition Parameters for SSUNEQ.
Note: SSUNEQ is used only with the FLM 2400 ADM BLSR configuration.
Table 4-152: SSUNEQ (Unequipped Code Received–Service Selector)—Alarm Event
AID Type Probable Cause Suggested Corrective Action
STS1 STS3C STS12C
This alarm occurs in bidirectional line switched rings (BLSRs) only. The Service Selector has detected an unequipped facility.
An STS-1/-3c/-12c cross-connect has been deleted at an upstream node. A deleted cross-connect upstream from the Service Selector, 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-connect 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.
• Retrieve the facility state where the circuit is added to the ring. Enter the facility if it is out-of-service (OOS).
Table 4-153: SSUNEQ Condition Parameters
AID Type
Default Notification Code Location Direction Service Affecting/
Non-Service Affecting
STS1 CR/MN NEND SA/NSA
STS3C CR/MN NEND RCV SA/NSA
STS12C CR/MN NEND RCV SA/NSA
DN
610
4
RCV
DROPPEDSIGNAL
OC-48
2400 ADMHS & TRIBs
Page 4-100 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.79 SVM
This feature is provided as a safeguard in maintaining the integrity of the NE provisioning database during NE maintenance. Software version mismatch (SVM) informs the user if different versions of software are simultaneously present in the NE.
Table 4-154 suggests corrective action for a Software Version Mismatch (SVM) Alarm Event. Table 4-155 lists Condition Parameters for SVM.
Table 4-154: SVM (Software Version Mismatch)—Alarm Event
AID Type Probable Cause Suggested Corrective Action
EQPT A mismatch failure of the file configuration among active banks.
• Download latest release to all NE units and switch to new load. Refer to the FLEXR SWDL User Guide, practice FJTU-320-920-100. If there are any problems, call Fujitsu for technical assistance at:1-800-USE-FTAC (1-800-873-3822).
Table 4-155: SVM Condition Parameters
AID Type
Default Notification
CodeLocation Direction Service Affecting/
Non-Service Affecting
EQPT CR NEND NA NSA
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-101
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.80 SWTOHO
Holdover (HO) is a function of a node clock that has lost its controlling input. The NE uses stored data acquired while in operation to control its output, allowing normal conditions to be simulated. Once the controlling input is restored, holdover terminates.
• SWTOIDLE—Node switching state switched to idle (FLM 2400 ADM BLSR only)
• SWTOINT1&INT2—Synchronization switch to internal clock 1 and internal clock 2
• SWTOINT1&PRI2—Synchronization switch to internal clock 1 and primary timing 2
• SWTOISOLATE—Node switching state switched to isolate (FLM 2400 ADM BLSR only)
• SWTOPASSTHRU—Node switching state switched to pass through (FLM 2400 ADM BLSR only)
• SWTOPRI1&PRI2—Synchronization switch to primary timing 1 and primary timing 2
• SWTOPRI1&INT2—Synchronization switch to primary timing 1 and internal clock 2
• SWTOSWITCHED—Node switching state changed to switched (FLM 2400 ADM BLSR only)
Note: SWTOINT1 (or 2) and SWTOPRI1 (or 2) pertain only to the FLM 2400 ADM Regenerator configuration.
Page 4-102 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
Table 4-156 suggests corrective action for a Synchronization Switch to Holdover (SWTOHO) Transient Condition. Table 4-157 lists Condition Parameters for SWTOHO.
Table 4-156: SWTOHO (Synchronization Switch to Holdover)—Transient Condition
AID Type Probable Cause Suggested Corrective Action
COM Loss of primary and secondary timing references.
• Verify proper building integrated timing supply (BITS) clock output.
• Check signal path from the NE to the BITS clock source.
• Refer to timing source vendor document.
• Replace HM2H plug-in unit. Refer to Section 6.9, Replacing the High-Speed Multiplexer (HM2H-xx) Unit in the HS Shelf.
For line timing:
• Check for fiber cut.
• Verify the receive optical levels. Clean optical connectors (refer to Sections 7.1 through 7.5.
• Verify good optical connections to the local and far-end units and at the lightwave distribution frame (LDF) panels along the link (refer to Sections 7.1 through 7.5).
• Replace HR2H plug-in unit. Refer to Section 6.11, Replacing High-Speed Receive Channel (HR2H-xxxx) Unit in the HS Shelf.
• Replace HM2H plug-in unit. Refer to Section 6.9, Replacing the High-Speed Multiplexer (HM2H-xx) Unit in the HS Shelf.
• Replace far-end HT2H plug-in unit. Refer to Section 6.10, Replacing the High-Speed Transmit Channel (HT2H-xxxx) Unit in the HS Shelf.
Excessive framing errors (line timing).
Damaged optical lines.
Improper optical levels.
Dirty optical connections.
Faulty HR2H plug-in unit.
Faulty HM2H plug-in unit.
Faulty HT2H plug-in unit at far end.
Table 4-157: SWTOHO Condition Parameters
AID Type Location Direction Service Affecting/
Non-Service Affecting
COM NEND NA NSA
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-103
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.81 SWTOIDLE
Table 4-158 suggests corrective action for a Node Switching State Switch to IDLE (SWTOIDLE) Transient Condition.
Table 4-158: SWTOIDLE (Node Switching State Switch to IDLE)—Transient Condition
AID Type Direction Probable Cause Suggested Corrective Action
COM NA This autonomous message is generated when the node switches to the Idle state from either the Pass-Through, Isolated or Switched state. The node enters the Idle state in response to the release of a manual or forced protection switch, or after the OC-48 line condition has been cleared.
• No action required. The Idle state is the normal state of operation for the BLSR.
Page 4-104 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.82 SWTOINT
A condition in which a node has lost its primary and secondary timing sources. Switch to internal clock is a default function of all NE types.
Table 4-159 suggests corrective action for a Synchronization Switch to Internal Clock (SWTOINT) Transient Condition.
Table 4-159: SWTOINT (Synchronization Switch to Internal Clock)—Transient Condition
AID Type Direction Probable Cause Suggested Corrective Action
COM NA Loss of primary and secondary timing references.
• Verify proper building integrated timing supply (BITS) clock output.
• Check signal path from the NE to the BITS clock source.
• Refer to timing source vendor document.
• Replace HM2H plug-in unit. Refer to Section 6.9, Replacing the High-Speed Multiplexer (HM2H-xx) Unit in the HS Shelf.
For line timing:
• Check for fiber cut.
• Verify the receive optical levels. Clean optical connectors (refer to Sections 7.1 through 7.5).
• Verify good optical connections to the local and far-end units and at the lightwave distribution frame (LDF) panels along the link (refer to Sections 7.1 through 7.5).
• Replace HR2H plug-in unit. Refer to Section 6.11, Replacing High-Speed Receive Channel (HR2H-xxxx) Unit in the HS Shelf.
• Replace HM2H plug-in unit. Refer to Section 6.9, Replacing the High-Speed Multiplexer (HM2H-xx) Unit in the HS Shelf.
• Replace far-end HT2H plug-in unit. Refer to Section 6.10, Replacing the High-Speed Transmit Channel (HT2H-xxxx) Unit in the HS Shelf.
Excessive framing errors (line timing).
Damaged optical lines.
Improper optical levels.
Dirty optical connections.
Faulty HR2H plug-in unit.
Faulty HM2H plug-in unit.
Faulty HT2H plug-in unit at far end.
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-105
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.83 SWTOINT1&INT2
SWTOINT1&INT2 is performed by the FLM 2400 ADM Regenerator NE. The Regenerator uses line timing (PRI1 and PRI2). For the Regenerator to switch to INT1 and INT2, either one of the PRI reference sources would already be in a failed state (for example, SWTOINTn&PRIn). And when the other PRI reference failed, the NE would switch to INT1&INT2 timing clocks.
Table 4-160 suggests corrective action for a Synchronization Switch to Internal Clock 1 and Internal Clock 2 (SWTOINT1&INT2) Transient Condition.
Table 4-160: SWTOINT1&INT2 (Synchronization Switch to Internal Clock 1 and Internal Clock 2)—Transient Condition
AID Type Direction Probable Cause Suggested Corrective Action
COM NA Excessive framing errors (line timing).
• Check for fiber cut.
• Verify the receive optical levels. Clean optical connectors (refer to Sections 7.1 through 7.5).
• Verify good optical connections to the local and far-end units and at the lightwave distribution frame (LDF) panels along the link (refer to Sections 7.1 through 7.5).
• Replace HR2H plug-in unit. Refer to Section 6.11, Replacing High-Speed Receive Channel (HR2H-xxxx) Unit in the HS Shelf.
• Replace HM2H plug-in unit, local end. Refer to Section 6.9, Replacing the High-Speed Multiplexer (HM2H-xx) Unit in the HS Shelf.
• Replace HT2H plug-in unit, far end. Refer to Section 6.10, Replacing the High-Speed Transmit Channel (HT2H-xxxx) Unit in the HS Shelf.
Damaged optical lines.
Improper optical levels.
Dirty optical connections.
Faulty HR2H plug-in unit.
Faulty HM2H plug-in unit at local end.
Faulty HT2H plug-in unit at far end.
Page 4-106 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.84 SWTOINT1&PRI2
SWTOINT1&PRI2 is performed by the FLM 2400 ADM Regenerator NE. The Regenerator uses line timing (PRI1 and PRI2). This transient condition occurs if the PRI1 reference source fails.
Table 4-160 suggests corrective action for a Synchronization Switch to Internal Clock 1 and Internal Clock 2 (SWTOINT1&INT2) Transient Condition.
Table 4-161: SWTOINT1&PRI2 (Synchronization Switch To Internal Clock 1and Primary Timing 2)—Transient Condition
AID Type Direction Probable Cause Suggested Corrective Action
COM NA Excessive framing errors (line timing).
• Check for fiber cut.
• Verify the receive optical levels. Clean optical connectors. (Refer to Sections 7.1 through 7.5.)
• Verify good optical connections to the local and far-end units and at the lightwave distribution frame (LDF) panels along the link. (Refer to Sections 7.1 through 7.5.)
• Replace HR2H plug-in unit. Refer to Section 6.11, Replacing High-Speed Receive Channel (HR2H-xxxx) Unit in the HS Shelf.
• Replace HM2H plug-in unit, far end. Refer to Section 6.9, Replacing the High-Speed Multiplexer (HM2H-xx) Unit in the HS Shelf.
• Replace HT2H plug-in unit, local end. Refer to Section 6.10, Replacing the High-Speed Transmit Channel (HT2H-xxxx) Unit in the HS Shelf.
Damaged optical lines.
Improper optical levels.
Dirty optical connections.
Faulty HR2H plug-in unit.
Faulty HT2H plug-in units at far end.
Faulty HM2H plug-in unit at local end.
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-107
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.85 SWTOISOLATE
Table 4-162 suggests corrective action for a Synchronization Switch to Internal Clock 1 and Internal Clock 2 (SWTOINT1&INT2) Transient Condition.
Table 4-162: SWTOISOLATE (Node Switching State Switch to Isolate)—Transient Condition
AID Type Direction Probable Cause Suggested Corrective Action
COM NA This autonomous message is generated when a node switches to the Isolate state. The node enters the Isolate state in response to a forced protection switch on both sides of the node, or after OC-48 line conditions have been declared on both sides of the node.
• If forced protection switches have caused the node to enter the Isolate state, release the protection switches as described in Section 4.3.37, FRCDSW. Direct the release command to the node that accepted the protection switch command.
• If OC-48 line conditions have caused the node to enter the Isolate state, retrieve the OC-48 alarm from the NE and refer to the trouble-clearing procedure for that alarm (see the Task Index List for a list of alarm events).
Page 4-108 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.86 SWTOPASSTHRU
Table 4-163 suggests corrective action for a Node Switching State Switch to PASSTHRU (SWTOPASSTHRU) Transient Condition.
Table 4-163: SWTOPASSTHRU (Node Switching State Switch to PASSTHRU)—Transient Condition
AID Type Direction Probable Cause Suggested Corrective Action
COM NA This autonomous message is generated when a node switches from the Idle or Isolate state to the Pass-Through state. The node enters the Pass-Through state in response to a manual or forced protection switch elsewhere on the ring, or in response to OC-48 line conditions elsewhere on the ring.
• If a manual or forced protection switch has caused the node to enter the Pass-Through state, release the protection switch as described in Section 4.3.58, MANSW (Working/Protect), or Section 4.3.37, FRCDSW, as applicable. Direct the release command to the node that accepted the protection switch command.
• If an OC-48 line condition has caused the node to enter the Pass-Through state, retrieve the OC-48 alarm from the NE adjacent to the failure, and refer to the trouble-clearing procedure for that alarm. (See the Task Index List for a list of alarm events.)
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-109
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.87 SWTOPRI
A condition in which the NE was previously using the internal clock or secondary as the timing reference. This condition is the result of a revertive switch back to primary.
Table 4-164 suggests corrective action for a Switch to Primary Timing (SWTOPRI) Transient Condition.
Table 4-164: SWTOPRI (Switch to Primary Timing)—Transient Condition
AID Type Direction Probable Cause Suggested Corrective Action
COM NA Primary reference source returned.
• No action required.
Page 4-110 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.88 SWTOPRI1&INT2
SWTOPRI1&INT2 is performed by the FLM 2400 ADM Regenerator NE. The Regenerator uses line timing (PRI1 and PRI2). This transient condition occurs when the PRI2 reference source fails.
Table 4-165 suggests corrective action for a Synchronization Switch to Primary Timing 1 and Internal Clock 2 (SWTOPRI1&INT2) Transient Condition.
Table 4-165: SWTOPRI1&INT2 (Synchronization Switch to Primary Timing 1and Internal Clock 2)—Transient Condition
AID Type Direction Probable Cause Suggested Corrective Action
COM NA Excessive framing errors (line timing).
• Check for fiber cut.
• Verify the receive optical levels. Clean optical connectors. (Refer to Sections 7.1 through 7.5.)
• Verify good optical connections to the local and far-end units and at the Lightwave Distribution Frame (LDF) panels along the link. (Refer to Sections 7.1 through 7.5.)
• Replace HR2H plug-in unit. Refer to Section 6.11, Replacing High-Speed Receive Channel (HR2H-xxxx) Unit in the HS Shelf.
• Replace HM2H plug-in unit, local end. Refer to Section 6.9, Replacing the High-Speed Multiplexer (HM2H-xx) Unit in the HS Shelf.
• Replace HT2H plug-in unit, far end. Refer to Section 6.10, Replacing the High-Speed Transmit Channel (HT2H-xxxx) Unit in the HS Shelf.
Damaged optical lines.
Improper optical levels.
Dirty optical connections.
Faulty HR2H plug-in unit.
Faulty HM2H plug-in unit, local end.
Fault HT2H Plug-in units at far end.
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-111
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.89 SWTOPRI1&PRI2
SWTOPRI1&PRI2 is performed by the FLM 2400 ADM Regenerator NE. The Regenerator uses line timing (PRI1 and PRI2). This transient condition occurs when the Regenerator was previously using Internal clocks 1 and 2 as the timing reference. This switch occurs when the node is provisioned for revertive switching.
Table 4-166 suggests corrective action for a Synchronization Switch to Primary Timing 1/2 (SWTOPRI1&PRI2) Transient Condition.
Table 4-166: SWTOPRI1&PRI2 (Synchronization Switch to Primary Timing 1/2)—Transient Condition
AID Type Direction Probable Cause Suggested Corrective Action
COM NA Primary reference sources returned.
• No action required.
Page 4-112 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.90 SWTOSEC
A condition in which the primary reference source has failed.
Table 4-167 suggests corrective action for a Switch to Secondary Timing (SWTOSEC) Transient Condition.
Table 4-167: SWTOSEC (Switch to Secondary Timing)—Transient Condition
AID Type Direction Probable Cause Suggested Corrective Action
COM NA Loss of building integrated timing supply (BITS) clock.
• Verify proper BITS clock output.
• Check signal path from the NE to the BITS clock source.
• Refer to timing source vendor document.
For line timing:
• Check for fiber cut.
• Verify the receive optical levels. Clean optical connectors. (Refer to Sections 7.1 through 7.5.)
• Verify good optical connections to the local and far-end units and at the lightwave distribution frame (LDF) panels along the link. (Refer to Sections 7.1 through 7.5.)
• Replace HR2H plug-in unit. Refer to Section 6.11, Replacing High-Speed Receive Channel (HR2H-xxxx) Unit in the HS Shelf.
• Replace HM2H plug-in unit. Refer to Section 6.9, Replacing the High-Speed Multiplexer (HM2H-xx) Unit in the HS Shelf.
• Replace far-end HT2H plug-in unit. Refer to Section 6.10, Replacing the High-Speed Transmit Channel (HT2H-xxxx) Unit in the HS Shelf.
Excessive framing errors (line timing).
Damaged optical lines.
Improper optical levels.
Dirty optical connections.
Faulty HR2H plug-in unit.
Faulty HM2H plug-in unit.
Faulty HT2H plug-in unit at far end.
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-113
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.91 SWTOSWITCHED
Table 4-168 suggests corrective action for a Node Switching State to Switched (SWTOSWITCHED) Transient Condition.
Table 4-168: SWTOSWITCHED (Node Switching State to Switched)—Transient Condition
AID Type Direction Probable Cause Suggested Corrective Action
COM NA This autonomous message is generated when a node switches to the Switched state from either the Idle or Pass-Through state. The node enters the Switched state in response to either:
• A manual or forced protection switch
or
• In response to OC-48 line conditions on a span adjacent to the node.
• If a manual or forced protection switch has caused the node to enter the Switched state, release the protection switch as described in Section 4.3.58, MANSW (Working/Protect), or Section 4.3.37, FRCDSW, as applicable. Direct the release command to the node that accepted the protection switch command.
• If an OC-48 line condition has caused the node to enter the Switched state, retrieve the OC-48 alarm from the NE, and refer to the trouble-clearing procedure for that alarm (see the Task Index List for a list of alarm events).
Page 4-114 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.92 SYNCD
Table 4-169 suggests corrective action for a Degradation of Synchronization Message (SYNCD) Alarm Event. Table 4-170 lists Condition Parameters for SYNCD.
Table 4-169: SYNCD (Degradation of Synchronization Message)—Alarm Event
AID Type Probable Cause Suggested Corrective Action
SYNCIN Synchronization message degradation is detected.
• The HM2H unit is defective.
• Check the upstream ADM for optical channel unit failure or removal.
• A break occurred in the fiber cable.
Table 4-170: SYNCD Condition Parameters
AID Type
Default Notification Code Location Direction Service Affecting/
Non-Service Affecting
SYNCIN MN NEND NA NSA
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-115
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.93 SYSRES
Table 4-171 suggests corrective action for a System Restart (SYSRES) Transient Condition. Table 4-172 lists Condition Parameters for SYSRES.
Table 4-171: SYSRES (System Restart)—Transient Condition
AID Type Probable Cause Suggested Corrective Action
COM The system was restarted. • Monitor system to determine reason for restart not initiated by the technician.
Table 4-172: SYSRES Condition Parameters
AID Type Location Direction Service Affecting/
Non-Service Affecting
COM NEND NA NA
Page 4-116 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.94 T-CVL, -CVP, -CVS
The performance monitor (PM) detects and reports transient conditions of the line, path, and section layers of the network.
Table 4-173 suggests corrective action for a Threshold Violation for Coding Violation Count–Line, Path, or Section (T-CVL, -CVP, -CVS) Transient Condition. Table 4-174 lists Condition Parameters for T-CVL. Table 4-175 lists Condition Parameters for T-CVP. Table 4-176 lists Condition Parameters for T-CVS.
Table 4-173: T-CVL, -CVP, -CVS (Threshold Violation for Coding Violation Count–Line, Path, or Section)—Transient Condition
AID Type Probable Cause Suggested Corrective Action
EC1 OC3 OC12 T3
STS1 STS3C STS12C OC48 T3
T1
Improper threshold setting.
For signal loss:
• Verify cable connections between FLM 2400 ADM and timing source (for T1 errors) or the DSX (for DS3 errors).
• Refer to Section 7.6, Verifying the External Clock and Connections, in this practice, and to the Shelf Installation practice, FJTU-320-560-200, Section 2.4, Connecting External Clock Cables (HS Shelf).
• Refer to timing source vendor document.
For CV errors:
• Identify the node originating the event message. The originating node is identified by the Target Identifier (TID) portion of the Condition Report.
• Verify threshold level settings with local standards. The Systems Operations practice, FJTU-320-560-272, Section 5.4, Performance Monitoring Parameters, provides the minimum, maximum, and default threshold levels.
• Retrieve current unit status with the RTRV-PM-(AID type) command. Record the date and time of the most recent event. After a one-minute period, perform the retrieval again. If the error count has incremented, then the problem exists at the current time.
• Refer to Sections 7.1 through 7.5 in this practice and follow troubleshooting procedures. Check connections for any error-causing conditions. If trouble persists, call Fujitsu for technical assistance at 1-800-USE-FTAC (1-800-873-3822).
• Refer to the previous step. If no increase in error count occurred after the reported error event, the unit should be monitored for possible future events.
Note: The 15-MIN register resets to zero at the end of the time interval limit. After reset, data may not be present. Additional retrievals are necessary to accurately determine unit status.
• Test the inputs of the unit in question to determine if the error is caused from an incoming signal. Incoming signals will be either line, path, section, or DS3 (from subscriber). If the incoming signal is error-free, switch MC6A working unit with MC6A protection unit. Monitor unit status. If problem clears, replace faulty MC6A unit.
Faulty data signal from subscriber.
Faulty local MC6A plug-in unit.
Faulty MC6A plug-in unit from downstream FLM 150, 600 or 2400 ADM.
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-117
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
Table 4-174: T-CVL Condition Parameters
AID Type Location Direction Service Affecting/
Non-Service Affecting
EC1 NEND TRMT NSA
T1 NEND NA NSA
T3 NEND TRMT NSA
OC3 NEND
FENDaTRMT NSA
OC12 NEND
FENDbTRMT NSA
OC48 NEND
FEND
RCV NSA
a FEND PM is supported only when an STS-3c signal is used.b FEND PM is supported only when an STS-12c signal is used (HD TRIB only).
Table 4-175: T-CVP Condition Parameters
AID Type Location Direction Service Affecting/
Non-Service Affecting
STS1 NEND
FEND
RCV NSA
STS3C NEND RCV NSA
STS12C NEND RCV NSA
T1 NEND NA NSA
T3 NEND RCV
TRMT
NSA
Table 4-176: T-CVS Condition Parameters
AID Type Location Direction Service Affecting/Non-Service Affecting
OC3 NEND TRMT NSA
OC12 NEND TRMT NSA
OC48 NEND RCV NSA
Page 4-118 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
CAUTION:
Switching between Working and Protection units is service affecting. Before switching, assess the potential impact on subscriber circuits.
The performance monitoring parameter T-CVx reports threshold violations of bit interleave parity (BIP) errors for each of the three network layers and the DS3 line. The BIP errors are collected in the following bytes of the STS-1 protocol header:
• B1-Section layer
• B2-Line layer
• B3-Path layer.
The CV counter is incremented for each BIP error detected; therefore, each BIP-8 byte can detect up to eight CVs per STS frame. For DS3 CVP errors, the CV counter is incremented for each DS3 frame in which a P-bit parity error is detected. For DS3 CVL error, a count of bipolar violations (BPVs) plus the count of excessive zeroes (EXZ) (three or more consecutive zeroes) occur.
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-119
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.95 T-ESL, -ESP, -ESS
Threshold violation for errored second count is a PM parameter that reports threshold violations of the errored second line, path, and section. Errored second count is a one-second interval in which at least one line, path, or section CV (BIP) error, severely errored framing (SEF), loss of signal (LOS), loss of pointer (LOP), or alarm indication signal (AIS) defect occurs. Performance monitoring also reports one or more CVs (P-bit parity error), one or more SEF or AIS defects on the DS3 path, BPVs, one or more excessive zeroes, or LOS on the DS3 line.
CAUTION:
Switching between Working and Protection units is service affecting. Before switching, assess the potential impact on subscriber circuits.
Page 4-120 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
Table 4-177 suggests corrective action for an Errored Second Count–Line, Path, or Section (T-ESL, -ESP, -ESS) Transient Condition. Table 4-178 lists Condition Parameters for T-ESL. Table 4-179 lists Condition Parameters for T-ESP. Table 4-180 lists Condition Parameters for T-ESS.
Table 4-177: T-ESL, -ESP, -ESS (Threshold Violation for Errored Second Count–Line, Path, or Section)—Transient Condition
AID Type Probable Cause Suggested Corrective Action
EC1 OC3 OC12 T3
OC48
STS1 STS3C
STS12C
T3
T1
Improperly set threshold.
MC6A unit.
Signal errors:
• For LOS, refer to Section 4.3.55.
• For LOF, refer to Section 4.3.50.
• For AIS, refer to Section 4.3.5.
• For T-SEFSS, refer to Section 4.3.100.
For CV (BIP) errors:
• Identify the node originating the event message. The originating node is identified by the Target Identifier (TID) portion of the Condition Report.
• Verify threshold level settings with local standards. Refer to the System Operations practice, FJTU-320-560-272. Section 5.4, Performance Monitoring Parameters, provides minimum, maximum, and default threshold levels for ESx.
• Retrieve current unit status with the RTRV-PM-(AID type) command. Record the date and time of the most recent event. After a one-minute period, perform the retrieval again. If the error count has incremented, then the problem exists at the current time.
• Refer to Sections 7.1 through 7.5 in this practice and follow troubleshooting procedures. Check connections for any error-causing conditions. If trouble persists, call Fujitsu for technical assistance at1-800-USE-FTAC (1-800-873-3822).
• In the previous step, if no increase in error count occurred after the reported error event, the unit should be monitored for possible future events.
Note: The 15-MIN register resets to zero at the end of the time interval limit. After reset, data may not be present. Additional retrievals are necessary to accurately determine unit status.
• Test the inputs of the unit in question to determine if the error is caused from an incoming signal. Incoming signals will be either line, path, section, or DS3 (from subscriber). If the incoming signal is error-free, switch MC6A Working unit with MC6A Protection unit. Monitor unit status. If problem clears, replace faulty MC6A unit.
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-121
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
Table 4-178: T-ESL Condition Parameters
AID Type Location Direction Service Affecting/
Non-Service Affecting
EC1 NEND TRMT NSA
T1 NEND NA NSA
T3 NEND TRMT NSA
OC3 NEND
FEND
TRMT NSA
OC12 NEND
FEND
TRMT NSA
OC48 NEND
FEND
RCV NSA
Table 4-179: T-ESP Condition Parameters
AID Type Location Direction Service Affecting/
Non-Service Affecting
STS1 NEND
FEND
RCV NSA
STS3C NEND RCV NSA
STS12C NEND RCV NSA
T1 NEND NA NA
T3 NEND RCV
TRMT
NSA
Table 4-180: T-ESS Condition Parameters
AID Type Location Direction Service Affecting/
Non-Service Affecting
OC3 NEND TRMT NSA
OC12 NEND TRMT NSA
OC48 NEND RCV NSA
Page 4-122 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.96 T-LBCN
The PM parameter detects errors at the physical layer. T-LBCN is reported when laser bias current from the transmitter falls outside threshold levels.
Table 4-181 suggests corrective action for a Threshold Violation for Normalized Laser Bias Current (T-LBCN) Transient Condition. Table 4-182 lists Condition Parameters for T-LBCN.
Table 4-181: T-LBCN (Threshold Violation for Normalized Laser Bias Current)—Transient Condition
AID Type Probable Cause Suggested Corrective Action
EQPT Improperly set threshold. • Verify proper threshold levels with local standards. Refer to the System Operations practice, FJTU-320-560-272, Section 5.4, Performance Monitoring Parameters, for minimum, maximum, and defaults parameters.
• Monitor laser bias current levels for fluctuations. Bias levels may change due to aging components.
• Replace the HT2H plug-in unit. Refer to Section 6.10, Replacing the High-Speed Transmit Channel (HT2H-xxxx) Unit in the HS Shelf.
Faulty HT2H plug-in unit.
Table 4-182: T-LBCN Condition Parameters
AID Type Location Direction Service Affecting/
Non-Service Affecting
EQPT NEND NSA
DN
610
4
RCV
DROPPEDSIGNAL
OC-48
2400 ADMHS & TRIBs
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-123
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.97 T-LPTN
The PM parameter detects errors at the physical layer. T-LPTN is reported when light power intensity of the transmitter output falls outside threshold levels.
Table 4-183 suggests corrective action for a Threshold Violation for Normalized Light Power Intensity (T-LPTN) Transient Condition. Table 4-184 lists Condition Parameters for T-LPTN.
Table 4-183: T-LPTN (Threshold Violation for Normalized Light Power Intensity)—Transient Condition
AID Type Probable Cause Suggested Corrective Action
EQPT Improperly set threshold. • Verify proper threshold levels with local standards. Refer to the System Operations practice, FJTU-320-560-272, Section 5.4, Performance Monitoring Parameters, for minimum, maximum, and defaults parameters.
• Repair fiber connection. Refer to Sections 7.1 through 7.5.
• Replace the HT2H plug-in unit. Refer to Section 6.10, Replacing the High-Speed Transmit Channel (HT2H-xxxx) Unit in the HS Shelf.
Poor optical connection.
Fiber cut.
Faulty HT2H plug-in unit.
Table 4-184: T-LPTN Condition Parameters
AID Type Location Direction Service Affecting/
Non-Service Affecting
EQPT NEND NSA
DN
610
4
RCV
DROPPEDSIGNAL
OC-48
2400 ADMHS & TRIBs
Page 4-124 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.98 T-PSC
T-PSC is the count of the number of protection switches per Working (W) and Protection (P) line. On the HD TRIB Shelf, incoming DS3 or EC-1 groups are protected at a 1:4 ratio. When an MC6A fails or is removed, the MS2T unit selects the affected backplane signals and reroutes them to the Protection MC6A unit. OC-3, OC-12, and OC-48 are protected on a 1:1 basis for either bidirectional or unidirectional switching. For bidirectional switching, if a failure occurs on the receiving line of the local shelf, the receiving line and sending line will be switched to protection, along with the remote shelf. For Unidirectional switching, only the receive signal is switched. Automatic protection Switching bytes in the SONET overhead (bytes K1 and K2) control the autonomous switching function.
Table 4-185 suggests corrective action for a Threshold Violation for Protection Switch Count (T-PSC) Transient Condition. Table 4-186 lists Condition Parameters for T-PSC.
Table 4-185: T-PSC (Threshold Violation for Protection Switch Count)—Transient Condition
AID Type Probable Cause Suggested Corrective Action
OC3OC12OC48
Improperly set threshold. • Verify proper threshold levels with local standards. Refer to the System Operations practice, FJTU-320-560-272, Section 5.4, Performance Monitoring Parameters, for minimum, maximum, and defaults parameters.
• The FLM 2400 ADM provides a lock-in function to prevent successive switching of the unit and the line caused by intermittent digital errors. Lockin is autonomous, and will occur if the unit switches four times in a 15-minute period, and will remain in that state for 24 hours or until the function is disabled through provisioning.
• Refer to Section 4.3.55, alarm event.
• Replace faulty MC6A, HT2H, or HR2H as required (refer to Sections 6.30, 6.10 and 6.11 respectively).
• Refer to Section 4.3.8, APSB, alarm event.
Intermittent digital errors.
Loss of DS3, EC-1, or optical signal.
Faulty MC6A plug-in unit.
Faulty HT2H transmit unit, or HR2H receive unit.
Table 4-186: T-PSC Condition Parameters
AID Type Location Direction Service Affecting/
Non-Service Affecting
OC3 NEND NA NSA
OC12 NEND NA NSA
OC48 NEND NA NSA
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-125
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.99 T-SASP
The PM parameter detects a threshold crossing of one-second intervals containing one or more SEF defects or one or more AIS defects for DS3 paths.
Table 4-187 suggests corrective action for a Threshold Violation for SEF/AIS Second Count–Path (T-SASP) Transient Condition. Table 4-188 lists Condition Parameters for T-SASP.
Table 4-187: T-SASP (Threshold Violation for SEF/AIS Second Count–Path)—Transient Condition
AID Type Probable Cause Suggested Corrective Action
T3 Improperly set threshold. • Verify proper threshold levels with local standards. Refer to the System Operations practice, FJTU-320-560-272, Section 5.4, Performance Monitoring Parameters, for minimum, maximum, and defaults parameters.
• Inspect and clear alarms from the upstream asynchronous equipment for an AIS indication. See Section 4.3.5.
• Verify proper cable connection between FLM 2400 ADM and DSX.
• Test subscriber input signal parameters.
• Replace faulty MC6A unit. See Section 6.30, Replacing Electrical Channel (MC6A-D3/-D3A2/-STS1/-ST1E/-ST1P) Unit in the FLM 600 ADM TRIB.
TRMT: The DS3 input to the tributary shelf contains an AIS.
Faulty cable.
Faulty signal from subscriber.
Faulty MC6A plug-in unit.
Table 4-188: T-SASP Condition Parameters
AID Type Location Direction Service Affecting/
Non-Service Affecting
T1 NEND NA NSA
T3 NEND NSA
DN
610
3
TRMT
OC-48
ADDEDSIGNAL
2400 ADMHS & TRIBs
Page 4-126 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.100 T-SEFSS
A threshold crossing of the PM parameter detects a one-second interval in which one or more severely errored framing (SEF) defects occur. If more than one SEF defect occurs during a single timing interval (one second), only one SEFSS event is counted.
Table 4-189 suggests corrective action for a Threshold Violation for Severely Errored Framing Second–Section (T-SEFSS) Transient Condition. Table 4-190 lists Condition Parameters for T-SEFSS.
Table 4-189: T-SEFSS (Threshold Violation for Severely Errored Framing Second–Section)—Transient Condition
AID Type Probable Cause Suggested Corrective Action
OC3OC12OC48
Improperly set threshold. • Verify proper threshold levels with local standards. Refer to the System Operations practice, FJTU-320-560-272, Section 5.4, Performance Monitoring Parameters, for minimum, maximum, and defaults parameters.
• Inspect all aspects of the OC-3/OC-12/OC-48 link as required.
• Verify the local receive optical levels, and the upstream transmit optical levels. Clean the optical connectors. Refer to Sections 7.1 through 7.5.
• Check the upstream or downstream ADMs for optical channel unit failure/removal. Refer to <CLEI>-FLT (Section 4.3.18) and RMVD (Section 4.3.72) respectively.
• Replace faulty HT2H or HR2H as needed. See Sections 6.10 and 6.11 respectively.
Improper optical levels.
Dirty or faulty fiber-optic connection.
Damaged fiber-optic cable.
OC-3—Faulty HT2H unit in upstream FLM 150 ADM or HR2H unit in local FLM 2400 ADM.
OC-12—Faulty HT2H unit in upstream FLM 600 ADM; faulty HR2H unit in local FLM 2400 ADM.
OC-48—Faulty HT2H unit in downstream FLM 2400 ADM; faulty HR2H unit in local FLM 2400 ADM.
Table 4-190: T-SEFSS Condition Parameters
AID Type Location Direction Service Affecting/
Non-Service Affecting
OC3 NEND TRMT NSA
OC12 NEND TRMT NSA
OC48 NEND RCV NSA
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-127
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.101 T-SESL, -SESP, or -SESS
Threshold Violation for Severely Errored Second Count—Line, Path, or Section
• Transient condition
T-SES- is a PM parameter that reports threshold violations of the severely errored secondline, path, or section. T-SES- is identical to T-ES-; however, a predefined number of CV (BIP-8) errors must occur before the performance monitor reports this condition. These values are:
• T-SESL = 2500 errors for OC-3; 10,000 for OC-12; and 40,300 for OC-48. For DS3 line, the number of errors is three.
• T-SESP = 2500 errors for OC-3; 8800 for OC-12; and 23,100 for OC-48. For DS3 path, the number of errors is 44.
• T-SESS = 2400 errors for STS-1 and STS-3c.
Refer to T-ESS Section 4.3.95 for problem resolution.
Table 4-191 lists Condition Parameters for T-SESL. Table 4-192 lists Condition Parameters for T-SESP. Table 4-193 lists Condition Parameters for T-SESS.
Table 4-191: T-SESL Condition Parameters
AID Type Location Direction Service Affecting/
Non-Service Affecting
EC1 NEND TRMT NSA
T1 NEND NA NSA
T3 NEND TRMT NSA
OC3 NEND
FEND
TRMT NSA
OC12 NEND
FEND
TRMT NSA
OC48 NEND
FEND
RCV NSA
Page 4-128 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
Table 4-192: T-SESP Condition Parameters
AID Type Location Direction Service Affecting/
Non-Service Affecting
STS1 NEND
FEND
RCV NSA
STS3C NEND RCV NSA
STS12C NEND RCV NSA
T1 NEND NA NA
T3 NEND RCV
TRMT
NSA
Table 4-193: T-SESS Condition Parameters
AID Type Location Direction Service Affecting/
Non-Service Affecting
OC3 NEND TRMT NSA
OC12 NEND TRMT NSA
OC48 NEND RCV NSA
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-129
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.102 T-UASL
The duration in seconds for which the line is unavailable. The UASL counter starts counting after 10 continuous SESL seconds. It counts continuously until 10 consecutive SESL-free seconds have elapsed.
Table 4-194 suggests corrective action for a Threshold Violation for Unavailable Second Count–Line (T-UASL) Transient Condition. Table 4-195 lists Condition Parameters for T-UASL.
Table 4-194: T-UASL (Threshold Violation for Unavailable Second Count–Line)—Transient Condition
AID Type Probable Cause Suggested Corrective Action
EC1 OC3 OC12 OC48
Faulty cable. • Resolve problem using LOS procedures, Section 4.3.55.
Cut fiber.
Faulty HT2H or HR2H unit.
Table 4-195: T-UASL Condition Parameters
AID Type Location Direction Service Affecting/
Non-Service Affecting
EC1 NEND TRMT NSA
OC3 NEND
FEND
TRMT NSA
OC12 NEND
FEND
TRMT NSA
OC48 NEND
FEND
RCV NSA
Page 4-130 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.103 T-UASP
The duration in seconds for which the path is unavailable. The UASP counter starts counting after 10 continuous SESP seconds. It counts continuously until 10 consecutive SESP-free seconds have elapsed.
Table 4-196 suggests corrective action for a Threshold Violation for Unavailable Second Count–Path (T-UASP) Transient Condition. Table 4-197 lists Condition Parameters for T-UASP.
Table 4-196: T-UASP (Threshold Violation for Unavailable Second Count–Path)—Transient Condition
AID Type Probable Cause Suggested Corrective Action
STS1 STS3C STS12C
T3
Faulty cable. • Resolve problem using LOS procedures Section 4.3.55.
Faulty DS3 signal from subscriber.
Faulty MC6A unit.
Table 4-197: T-UASP Condition Parameters
AID Type Location Direction Service Affecting/
Non-Service Affecting
STS1 NEND
FEND
RCV NSA
STS3C NEND RCV NSA
STS12C NEND RCV NSA
T1 NEND NA NA
T3 NEND RCV
TRMT
NSA
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-131
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.104 TARPECHO
Table 4-198 suggests corrective action for a TARP Echo Autonomous Response (TARPECHO) Transient Condition. Table 4-199 lists Condition Parameters for TARPECHO.
Table 4-198: TARPECHO (TARP Echo Autonomous Response)—Transient Condition
AID Type Probable Cause Suggested Corrective Action
COM OPR-TEF response. • No action required.
Table 4-199: TARPECHO Condition Parameters
AIDType Location Direction Service Affecting/
Non-Service Affecting
COM NEND NA NA
Page 4-132 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.105 TARPEER
Table 4-200 suggests corrective action for a TID or NET Unreachable Error (TARPEER) Transient Condition. Table 4-201 lists Condition Parameters for TARPEER.
Table 4-200: TARPEER (A TID or NET Unreachable Error)—Transient Condition
AID Type Probable Cause Suggested Corrective Action
COM Unknown network entity title (NET) used during CPY-FILE.
• Check for correct NET if executing CPY-FILE.
• Check for correct NET or TID if executing OPR-TEF.
Unknown NET or TID used during OPR-TEF.
Table 4-201: TARPEER Condition Parameters
AID Type Location Direction Service Affecting/
Non-Service Affecting
COM NEND NA NA
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-133
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.106 TMGOUTPSW
• TMGOUTPSWPRS/STU/ST2/ST3/SIC/ST4/RES/FAIL/NA
Table 4-202 suggests corrective action for a Derived Primary Reference Switch (TMGOUTPSW) Transient Condition. Table 4-203 lists Condition Parameters for TMGOUTPSW.
Table 4-202: TMGOUTPSW (Derived Primary Reference Switch)—Transient Condition
AID Type Probable Cause Suggested Corrective Action
SYNCIN A derived DS1 primary timing reference switch is detected.
• The HM2H unit is defective.
• Check the upstream ADM for optical channel unit failure or removal.
• A break occurred in the fiber-optic cable.
Table 4-203: TMGOUTPSW Condition Parameters
AID Type Location Direction Service Affecting/Non-Service Affecting
SYNCIN NEND NA NSA
Page 4-134 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.107 TMGOUTSSW
• TMGOUTSSWPRS/STU/ST2/ST3/SIC/ST4/RES/FAIL/NA
Table 4-204 lists quality level values for Synchronization Status Messaging. Table 4-205 suggests corrective action for a Derived Secondary Reference Switch (TMGOUTSSW) Transient Condition. Table 4-206 lists Condition Parameters for TMGOUTSSW.
Table 4-204: Synchronization Status Messaging Quality Level Values
Acronym Description Quality Level
PRS PRS Traceable 1
STU Synchronized–Traceability Unknown 2
ST2 Traceable Stratum 2 Holdover 3
ST3 Traceable Stratum 3 Holdover 4
SICa
a The acronym SIC has been changed to SMC in GR-253-CORE Issue 2 but the quality level and values remain the same.
Traceable SONET Clock Self-Timed 5
ST4 Traceable Stratum 4 Free-Run 6
DUS Don’t Use for Sync 7
RES Reserved for Network Synchronization Use User Assigns
Table 4-205: TMGOUTSSW (Derived Secondary Reference Switch)—Transient Condition
AID Type Probable Cause Suggested Corrective Action
SYNCIN A derived DS1 secondary timing reference switch is detected.
• The HM2H unit is defective.
• Check the upstream ADM for optical channel unit failure or removal.
• A break occurred in the fiber-optic cable.
Table 4-206: TMGOUTSSW Condition Parameters
AID Type Location Direction Service Affecting/
Non-Service Affecting
SYNCIN NEND NA NSA
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-135
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.108 TMGSW
• TMGSWPRS/STU/ST2/ST3/SIC/ST4/RES/FAIL/NA
Table 4-207 suggests corrective action for an NE Reference Switch (TMGSW) Transient Condition. Table 4-208 lists Condition Parameters for TMGSW.
Table 4-207: TMGSW (NE Reference Switch)—Transient Condition
AID Type Probable Cause Suggested Corrective Action
SYNCIN A system timing reference is detected.
• The HM2H unit is defective.
• Check the upstream ADM for optical channel unit failure or removal.
• A break occurred in the fiber-optic cable.
Table 4-208: TMGSW Condition Parameters
AID Type Location Direction Service Affecting/Non-Service Affecting
SYNCIN NEND NA NSA
Page 4-136 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.109 TPLGYM
Table 4-209 suggests corrective action for a Topology Mismatch (TPLGYM) Alarm Event. Table 4-210 lists Condition Parameters for TPLGYM.
Note: TPLGYM is used only with the FLM 2400 ADM BLSR configuration.
Table 4-209: TPLGYM (Topology Mismatch)—Alarm Event
AID Type Probable Cause Suggested Corrective Action
COM A node ID is missing.
Note: There are duplicated node IDs in the topology table. This may occur, for example, when adding nodes to the ring.
• Enter an ID in the node that declared the alarm. The ID must be between 0 and 15 (inclusive) and must be unique from the IDs of other nodes in the ring. If the ring has been completely turned up, initialize the ring topology after entering the node ID.
• Retrieve the node IDs from all the nodes in the ring and change one of the duplicate IDs to a new unique ID number between 0 and 15 (inclusive). If the ring has been completely turned up, initialize the ring topology after entering the node ID.
Table 4-210: TPLGYM Condition Parameters
AID Type
Default Notification
CodeLocation Direction Service Affecting/
Non-Service Affecting
COM MN NEND NA NSA
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-137
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.110 TRCM
There is a discontinuity in the signal path.
Table 4-211 suggests corrective action for a Path Trace Mismatch (TRCM) Standing Condition. Table 4-212 lists Condition Parameters for TRCM.
Table 4-211: TRCM (Path Trace Mismatch)—Standing Condition
AID Type Probable Cause Suggested Corrective Action
STS1 Cross-connect(s) have not been provisioned correctly.
• Retrieve and reconcile the existing cross-connects conditions with requirements (refer to local documentation for cross-connect mapping).
• Provision the correct cross-connects.
Table 4-212: TRCM Condition Parameters
AID Type
Default Notification
CodeLocation Direction Service Affecting/
Non-Service Affecting
STS1 MN NEND NSA
DN
610
4
RCV
DROPPEDSIGNAL
OC-48
2400 ADMHS & TRIBs
Page 4-138 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.111 UNEQ
Table 4-213 suggests corrective action for an Unequipped Code Signal Label Received (UNEQ) Alarm Event. Table 4-214 lists Condition Parameters for UNEQ.
Table 4-213: UNEQ (Unequipped Code Signal Label Received)—Alarm Event
AID Type Probable Cause Suggested Corrective Action
STS1STS3CSTS12C
This alarm occurs in path-switched rings only. It is detected as the signal is dropped.
• 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).
• This option works only with MC6A-D3E2. If MC6A-D3E is used, turn this option off. Refer to the Turn-Up and Operation practice, FJTU-320-560-270, Section 3.1.2, Changing Facility State, Table 3-1.
An STS-1/-3c/-12c 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.
Table 4-214: UNEQ Condition Parameters
AID Type
Default Notification Code Location Direction Service Affecting/
Non-Service Affecting
STS1 CR/MN NEND SA/NSA
STS3C CR/MN NEND RCV SA/NSA
STS12C CR/MN NEND RVC SA/NSA
DN
610
4
RCV
DROPPEDSIGNAL
OC-48
2400 ADMHS & TRIBs
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-139
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
4.3.112 WKSWBK
WKSWBK is a PM parameter reporting the switching of the protection unit to the working unit in the FLM 2400 ADM.
Table 4-215 suggests corrective action for a Working Facility/Equipment Switched Back to Working (WKSWBK) Transient Condition. Table 4-216 lists Condition Parameters for WKSWBK.
Table 4-215: WKSWBK (Working Facility/Equipment Switched Back to Working)—Transient Condition
AID Type Probable Cause Suggested Corrective Action
EQPTOC3OC12OC48STS1
STS3CSTS12C
The restoration of signal to Working unit after an LOS or degraded condition.
• No action required. The FLM 2400 ADM has two modes of protective switching, revertive and nonrevertive. In nonrevertive switching, switching is performed manually. In revertive, switching occurs after normal conditions have been restored to the working unit.
Working unit plugged in after it had been removed.
Faulty Working unit repaired.
Table 4-216: WKSWBK Condition Parameters
AID Type AID Location Direction Service Affecting/
Non-Service Affecting
EQPT EQPT NEND NA NSA
OC3 OC3 GP NEND NA NSA
OC12 OC12 GP NEND NA NSA
OC48 OC48 GP NEND NA NSA
STS1 STS1 EWSTS1 LG
NEND NA NSA
STS3C STS3C EW
STS3C LG
NEND NA NSA
STS12C STS12C EW
STS12C LG
NEND NA NSA
Page 4-140 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
4.3: Condition Tables
4.3.113 WKSWPR
WKSWPR is a PM parameter reporting the switching of the Working unit to the Protection unit in the FLM 2400 ADM.
Table 4-217 suggests corrective action for a Working Facility/Equipment Switched Back to Protection (WKSWPR) Transient Condition. Table 4-218 lists Condition Parameters for WKSWPR.
Table 4-217: WKSWPR (Working Facility/Equipment Switched Back to Protection)—Transient Condition
AID Type Probable Cause Suggested Corrective Action
EQPTOC3OC12OC48STS1
STS3CSTS12C
LOS or degraded signal input of the Working unit.
• Has the 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. Refer to Task Index List to find the appropriate unit.
Faulty Working unit.
Working unit removed from chassis.
Table 4-218: WKSWPR Condition Parameters
AID Type Location Direction Service Affecting/
Non-Service Affecting
EQPT NEND NA NSA
OC3 NEND NA NSA
OC12 NEND NA NSA
OC48 NEND NA NSA
STS1 NEND NA NSA
STS3C NEND NA NSA
STS12C NEND NA NSA
Issue 7, May 1999 FNC and FNC Customer Use Only Page 4-141
4.3: Condition Tables Maintenance and Trouble ClearingFJTU-320-560-480
This page intentionally left blank.
Page 4-142 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
Chapter 5: Unit and Connector Locations
CHAPTER 5
5 Unit and Connector Locations
5.1 High-Speed and Tributary Shelf Front and Back Views
5.1.1 Summary
Figures 5-1, 5-2, and 5-3 show rear views of the FLM 2400 ADM High-Speed shelf, the High-Density Tributary (HD TRIB) Shelf, and the FLM 600 ADM TRIB shelf respectively. These illustrations can be used to assist you in locating connectors. Figures 5-4, 5-5, and 5-6 show typical front views of these FLM shelves.
Figure 5-1: FLM 2400 ADM HS Shelf Rear View
c401
83.2
OW/E2A2 OW/E2A1INT
LINK 1
CN20 CN18 CN19SYNC2EXT CLKSECOND
OHA 1 SVC 2 SVC 1OSS2
SYNC1EXT CLK
PRIM
CN25 CN23 CN22
INT 5 INT 4 INT 2 SW/SCV H.K.1 H.K.2 ALM
CN17 CN16 CN14 CN24
CN12
CN11
CN10
CN8
CN15 CN13 CN21 CN9CN3
SV1
CN4
SV2
INT3 INT1 INT LINK2 OSS1
CN5CN6 CN1
MAIN A
MAIN B
GA
GB
CN7 CN2
MODEM
FG
PWR
Issue 7, May 1999 FNC and FNC Customer Use Only Page 5-1
Chapter 5: High-Speed and Tributary Shelf Front and Back Views
Maintenance and Trouble ClearingFJTU-320-560-480
Figure 5-2: FLM 2400 ADM TRIB Shelf Rear View
Figure 5-3: FLM 600 ADM TRIB Shelf Rear View
INT HS
LINK 2
DS1OUTSECOND
DS1OUTPRIM
CN51
CN53CN52
LINK 1 CN50 CN49
PWRTRM
MAINA
MAINB
GA
FG
GP4/GP6 GP3/GP5
S IN
CH23 CH21 CH19 CH17 CH15 CH13 CH11 CH9 CH7 CH5 CH3 CH1
CN11 CN9 CN7 CN5 CN3 CN1CN35 CN33 CN31 CN29 CN27 CN25
CH10 CH8 CH6 CH4CH24 CH22 CH20 CH18 CH16 CH14 CH12 CH2
CN10 CN8 CN6 CN4CN36 CN34 CN32 CN30 CN28 CN26 CN12 CN2
CH23 CH21 CH19 CH17 CH15 CH13 CH11 CH9 CH7 CH5 CH3 CH1
CN47 CN45 CN43 CN41 CN39 CN37 CN23 CN21 CN19 CN17 CN15 CN13
CH10 CH8 CH6 CH4CH24 CH22 CH20 CH18 CH16 CH14 CH12 CH2
CN22 CN20 CN18 CN16CN48 CN46 CN44 CN42 CN40 CN38 CN24 CN14
S IN
R OUT R OUT
GP4/GP6 GP3/GP5
o401
48.1
GB
G B
CN7 CN6 CN4 CN2
OW/E2A2
OW/E2A1 H.K.1 OHA1
MAIN A
MAIN B
G A
MODEM2.4GINF ALM H.K.2 OHA2
d592
7.2CN10 CN9 CN8 CN5 CN3 CN1
GP3R OUT S IN R OUT S IN R OUT S IN R OUT S IN
OSS2SECOND PRIM
CN13CN12 CN11
EXT CLK
PWR
FG
GP6 GP5 GP4
CH1 CH1 CH1 CH1
CH2 CH2 CH2 CH2
CH3 CH3 CH3 CH3
OSS1CN37 CN25 CN34 CN22 CN31 CN19 CN28 CN16
CN36 CN24 CN33 CN21 CN30 CN18 CN27 CN15
CN35 CN23 CN32 CN20 CN29 CN17 CN26 CN14
Page 5-2 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
Chapter 5: High-Speed and Tributary Shelf Frontand Back Views
Figure 5-4: FLM 2400 ADM HS Shelf Front View
Figure 5-5: Typical FLM 2400 ADM HD TRIB Shelf Front View
FUSE2.0A
FC9607HRXX
HR2H-XXXX
FAIL/SVCE
LINE
FC9607HMA1
FUSE2.0A
HM2H-C1
ATTENTION
Push the lever of the unit lower part to remove the coaxunit as shown in the figure
FUSE2.0A
FC9607HTXX
HT2H-XXXX
FUSE2.0A
FC9607HRXX
HR2H-XXXX
FC9607HMA1
FUSE2.0A
HM2H-C1
FC9607HTXX
HT2H-XXXX
o400
01.1
2
FUSE2.0A
PW2H-HS
PWR
FC
9607
PW
H1
+5.0VSGMAING
LAMPTST
FC9607AWA2
AW2H-A2
CR
MJMN
ABN
SV2H-DL
FAIL
LINE
ACS
FC9607SVD2
TERM
FC9607MPD2
FAIL
CPURESET
MP2H-DLB
FC9607HSN2
FAIL
HS2H-U1
ATTENTION
Push the lever of the unit lower part to remove the coaxunit as shown in the figure
PW2H AW2H SV2H MP2H HS2H1
HR2H1
HM2H1
HT2H2
HR2H2
HM2H2
HT2H
ATTENTION
ESDOBSERVE PRECAUTIONS
FOR HANDLINGFLM 2400 HS
DANGERInvisible laserradiation from
connectorswhen uncoupledAVOID DIRECT
EXPOSURETO BEAM
DANGERInvisible laserradiation from
connectorswhen uncoupledAVOID DIRECT
EXPOSURETO BEAM
DANGERInvisible laserradiation from
connectorswhen uncoupledAVOID DIRECT
EXPOSURETO BEAM
DANGERInvisible laserradiation from
connectorswhen uncoupledAVOID DIRECT
EXPOSURETO BEAM
ACO
SWDL
PHONE
FUSE2.0A
FAIL/SVCE
LINE
FAIL/SVCE
FAIL/SVCE
LINE
FAIL/SVCE
LINE
FAIL/SVCE
CALL
o400
02.6
PWR
+5.4V
-5.6V
SG
MAIN
G
ON
OFF
PWR
FC9608PW11
PW
1A-T
RIB
USE ONLY INFLM 2400 ADM HD
FC
9608
MS
D3
FAIL/ON PTCT
MS2T-D31
FC
9608
MP
D2
MP2T-DL
FAIL
CPURESET
FAIL/SVCE
1
2
3
LINE
MC6A-D3E
FC
9616
MD
32
FAIL/SVCE
1
2
3
LINE
MC6A-D3E
FC
9616
MD
32
LINE
FC
9608
HC
M1
FAIL/SVCE
HC2T-MDL
FAIL/SVCE
1
2
3
LINE
MC6A-D3E
FC
9616
MD
32
FAIL/SVCE
1
2
3
LINE
MC6A-D3E
FC
9616
MD
32
FAIL/SVCE
1
2
3
LINE
MC6A-D3E
FC
9616
MD
32
FAIL/SVCE
1
2
3
LINE
MC6A-D3E
FC
9616
MD
32
FAIL
FC
9608
HS
D3
HS2T-D3
LINE
FC
9608
HC
M1
FAIL/SVCE
HC2T-MDL
FAIL/SVCE
1
2
3
LINE
MC6A-D3E
FC
9616
MD
32
LINE
FC
9608
HC
M1
FAIL/SVCE
HC2T-MDL
FAIL/SVCE
1
2
3
LINE
MC6A-D3E
FC
9616
MD
32
FAIL/SVCE
1
2
3
LINE
MC6A-D3E
FC
9616
MD
32
LINE
FC
9608
HC
M1
FAIL/SVCE
HC2T-MDL
FAIL/SVCE
1
2
3
LINE
MC6A-D3E
FC
9616
MD
32
FC
9608
MS
D3
FAIL/ON PTCT
MS2T-D31
FAIL
FC
9608
HS
D3
HS2T-D3
FLM 2400 HD TRIB
1PW1A
2PW1A MP2T
1
MC6A2
MC6A1
HC2T3
MC6A4
MC6A2
HC2TP
MC6A MS2T HS2T1
MC6A2
MC6A1
HC2T3
MC6A4
MC6A2
HC2TP
MC6A MS2T HS2T
ATTENTION
ESDOBSERVE PRECAUTIONS
FOR HANDLING
ESDFG
PWR
+5.4V
-5.6V
SG
MAIN
G
ON
OFF
PWR
FC9608PW11
PW
1A-T
RIB
USE ONLY INFLM 2400 ADM HD
Issue 7, May 1999 FNC and FNC Customer Use Only Page 5-3
Chapter 5: High-Speed and Tributary Shelf Front and Back Views
Maintenance and Trouble ClearingFJTU-320-560-480
Figure 5-6: FLM 600 ADM TRIB Shelf Front View
FC
9616
ST
15M
C6A
-ST
1P
FAIL/SVCE
1
2
3
LINE
FC
9616
ST
15M
C6A
-ST
1P
FAIL/SVCE
1
2
3
LINE
FC9616LRx1
MC6A-31xL
FAIL
LINE
SEND
RCV
ON LINE
DA
NG
ER
FC9616LRx1
MC6A-31xL
FAIL
LINE
SEND
RCV
ON LINE
DA
NG
ER
FC9616LRx1
MC6A-31xL
FAIL
LINE
SEND
RCV
ON LINE
DA
NG
ER
EC6A
FC9616EC62
LINE
EC
6A-2
4G
FAIL
3-W 3-P 4-W 4-P 5-W 5-P 6-P6-WMC6A
1PW6A
2PW6A AW6A SV6A MP6A HS6A
2 W P 1-W 1-P 2-W 2-P
FLM 600 ADM TRIBESDFG
ATTENTION
ESDOBSERVE PRECAUTIONS
FOR HANDLING
FC9616MPG1
MP6A-24G
FAIL
CPURESET
FC9616SVG1
SV6A-24G
d520
0.10
FAIL/SVCE
12
3
LINE
FC9616MDA1
MC6A-D3A2
FAIL/SVCE
12
3
LINE
FC9616MDA1
MC6A-D3A2
PW6A
FC9616PW61
PWR ON
PWR
+5.4V
-5.6V
SG
MAIN
G
PW6A
FC9616PW61
PWR ON
PWR
+5.4V
-5.6V
SG
MAIN
G
FAIL/SVCE
LINE
HC6A-6EL2
FC9616H6E2
ATTENTION
PUSH THE LEVER OFUNIT LOWER PART TOREMOVE THE COAXUNIT AS SHOWN INTHE FIGURE
FAIL/SVCE
LINE
HC6A-6EL2
FC9616H6E2
ATTENTION
PUSH THE LEVER OFUNIT LOWER PART TOREMOVE THE COAXUNIT AS SHOWN INTHE FIGURE
3 4 5 16
EC6A
LINE
EC
6A-2
4G
FAIL
FC9616EC62 FC9616TCE1
FAIL/SVCE
LINE
TCA-ENH
FC9616TCE1
FAIL/SVCE
LINE
TCA-ENH
MS
6A-O
PT
2
FC9616MS62
FAIL
LINE
MS
6A-O
PT
2FC9616MS62
FAIL
LINEM
S6A
-OP
T2
FC9616MS62
FAIL
LINE
HG1 MODE
FC9616SAM2
HS6A-AD2
FAIL
LINE
FORCE
AUTO
MNL
FORCE
AUTO
MNL
HG 2 MODE
FC9616AWE1
AW6A-ENH
LAMPTST
CALL
PHONE
ACO
CRMJMN
ABN
NEACTFEACT
PMN
FC9616LRx1
MC6A-31xL
FAIL
LINE
SEND
RCV
ON LINE
DA
NG
ER
Page 5-4 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
Chapter 6: Replacing Units
CHAPTER 6
6 Replacing Units
6.1 Removing and Installing Optical Channel Units
6.1.1 Summary
This procedure describes the steps to remove and install the Optical, Multiplexer/Demultiplexer, and Electrical Interface units in the High-Speed (HS), High-Density Tributary (HD TRIB), and FLM 600 ADM TRIB Shelves. Refer to Table 6-1 for a list of these modules and the associated practice/section, which gives the detailed steps of the installation.
Table 6-1: Optical and Electrical Interface Units
Module Practice Section
HT2H-xxxx FJTU-320-560-480 Section 6.10
HR2H-xxxx FJTU-320-560-480 Section 6.11
HM2H-Ax FJTU-320-560-480 Section 6.9
HC2T-MDL/C12L FJTU-320-560-480 Section 6.16
MC6A-3BRD FJTU-320-560-480 Section 6.20
MC6A-2Lxx FJTU-320-560-480 Section 6.17
MC6A-31xx FJTU-320-560-480 Section 6.18
HC6A-xxxx/MC6A-xxxx FJTU-320-560-480 Section 6.28
HC6A-6EL1/6EL2 FJTU-320-545-220
(600 ADM)
DLP-220-028
HC6A-6Lxx FJTU-320-545-220
(600 ADM)
DLP-220-014
MC6A-3xxx FJTU-320-545-220
(600 ADM)
DLP-220-014
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-1
6.1: Removing and Installing Optical Channel Units
Maintenance and Trouble ClearingFJTU-320-560-480
DANGER:
NEVER look into the end of a fiber cord, fiber pigtail, or a fiber cable. PERMANENT EYE DAMAGE or BLINDNESS can occur VERY QUICKLY if laser light is present.
CAUTION:
To prevent possible damage to the units, an electrostatic discharge (ESD) wrist strap with a minimum resistance of 1 megohm should be worn when handling FLM units. Before using the strap, check for opens, shorts, and minimum resistance value. If the strap does not pass these checks, it should not be used.
WARNING:
To avoid damage to a fiber cord or fiber pigtail, read Section 7.1, Handling the Fiber Cables Correctly, and Section 7.3, Connect/Disconnect Optical Cables.
6.1.2 Removing the Plug-In Unit
Refer to Figures 6-1 and 6-2 while performing the following steps.
Step 1 If the unit has been seated in the shelf, pull the top and bottom extractor levers with both hands and slide the unit out until the secondary latch engages (a little more than halfway out of the slot).
Step 2 Disconnect the optical fiber cords if they are connected to the optical unit, or the 78-Mb/s cables if they are connected to the Multiplexer/Demultiplexer or the Electrical Interface units. Refer to Section 7.3, Connect/Disconnect Optical Cables.
Step 3 If needed, install necessary optical connector covers on the fiber jumper. Refer to this practice, Section 7.1, Handling the Fiber Cables Correctly.
Step 4 Lift the metal spring of the secondary latch and pull the unit out.
You have completed this task.
6.1.3 Installing the Plug-In Unit
Step 1 Inspect the unit to be installed for possible damage.
Page 6-2 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.1: Removing and Installing Optical ChannelUnits
Step 2 If required, set strap options. Refer to the appropriate section.
Step 3 Slide the unit into the appropriate slot until the secondary latch engages (a little more than halfway into the slot).
Step 4 Connect the optical fiber cords or electrical cables. Refer to the appropriate section.
Figure 6-1: Removing and Installing the Unit
d123
3.5
Removal Instruction Label
Bottom Extractor Lever
Top Extractor Lever
SecondaryLatch
Optical FiberConnections
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-3
6.1: Removing and Installing Optical Channel Units
Maintenance and Trouble ClearingFJTU-320-560-480
Step 5 Seat the unit by pulling the top and bottom extractor levers with both hands and pressing the unit into the mounting slot with a slow, firm movement until the unit rests securely in place.
You have completed this task.
Figure 6-2: The Secondary Latch at the Bottom of the Unit
d622
6.1
SECONDARYLATCH
Page 6-4 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.2: Removing and Installing Electrical Plug-InUnits
6.2 Removing and Installing Electrical Plug-In Units
6.2.1 Summary
This procedure describes steps to remove and replace electrical plug-in units except Optical Units HR2H, HT2H, HM2H, HC2T, MC6A-3BRD, MC6A-31xx/2Lxx, MC6A-3xxx, and HC6A-6ELx, or other electrical units with cables attached.
CAUTION:
To prevent possible damage to the units, an electrostatic discharge (ESD) wrist strap with a minimum resistance of 1 megohm should be worn when handling FLM units. Before using the strap, check for opens, shorts, and minimum resistance value. If the strap does not pass these checks, it should not be used.
WARNING:
During replacement, all plug-in units should be seated with a slow but firm motion. Many critical units have long power connector pins to minimize power surge during unit replacement.
6.2.2 Procedure
Step 1 Review this procedure before removing or inserting any plug-in unit.
a. Wear a wrist strap that is connected to ground.
b. Hold the plug-in units by the edges only.
c. Do not touch the IC leads or circuitry.
d. Transport and store the units in special ESD protective bags.
You have completed this task.
e. Return the units to Fujitsu Network Communications, Inc. Service Center.
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-5
6.2: Removing and Installing Electrical Plug-In Units
Maintenance and Trouble ClearingFJTU-320-560-480
Removing the Plug-In Unit
Step 1 Locate the plug-in unit to be replaced.
Step 2 Gently pull open the top and bottom extractor levers until plug-in unit is free from the rear connector. Refer to Figure 6-3.
Step 3 Carefully remove the plug-in unit from the mounting shelf.
You have completed this task.
Installing the Plug-In Unit
Step 1 If required, set strap options on the unit according to each plug-in unit’s installation.
Figure 6-3: Removing the Plug-In Unit d5
078.
2
Rotate the card levers whilepressing the locking tabs on the endof each lever toward the lever.
1. Gently apply additional pressureuntil card levers pop-out.
2. Grasp both upper and lower cardlevers with thumbs and forefingers.Slowly pull unit out of shelf.
3.
Page 6-6 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.2: Removing and Installing Electrical Plug-InUnits
Step 2 Slide the replacement unit into the correct mounting slot. Refer to the Plug-In Unit Installation practice, FJTU-320-560-220, Section 2.2, Viewing the Shelf Layouts.
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-7
6.2: Removing and Installing Electrical Plug-In Units
Maintenance and Trouble ClearingFJTU-320-560-480
Step 3 Make sure the extractor levers are open and slowly press the unit into the mounting slot. Carefully close the top and bottom extractor levers to seat the unit in the backplane connector. Refer to Figure 6-4.
You have completed this task.
Figure 6-4: Installing the Plug-In Unit
DN
507
7.1
Place thumbs and forefingers oncard levers. Check that card leversare fully extended toward you.
1. Grasp both levers with thumbs andforefingers. Position unit in card slotand gently push unit into shelf.
2. Apply additional pressure on leversuntil lock lever locks into stopper.
3.
Lock Lever
Main Body of Card Lever
Unit
Stopper
DN
523
3
Page 6-8 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.3: Replacing and Maintaining the Fan ShelfFilter
6.3 Replacing and Maintaining the Fan Shelf Filter
6.3.1 Summary
Fujitsu recommends replacing the fan filter used on the FLM 2400 ADM at least every 6 months. This filter should be replaced more frequently if the equipment is installed in an abnormally dusty environment or in a location with a large amount of foot traffic. Refer to Figure 6-5 in this procedure.
Note: If the Fan unit has failed, refer to the Plug-In Unit Installation practice, FJTU-320-560-220, Section 7.1, Installing Fan Unit in the Fan Shelf.
6.3.2 Procedure
Step 1 Remove the fuses to turn the fan off before changing the air filter.
Step 2 Locate a new replacement filter (PN H15B-0201-C293) and have it available at the Fan Shelf being serviced.
Figure 6-5: Fan Shelf Filter Installation
FAN UNIT ASSEMBLY
FAN/FILTER SHELF
FILTER COVERTHUMBSCREW
d770
0
FILTER ASSEMBLY
FAN ASSEMBLY COVER
FAN COVERTHUMBSCREW
FLTR
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-9
6.3: Replacing and Maintaining the Fan Shelf Filter
Maintenance and Trouble ClearingFJTU-320-560-480
Step 3 Loosen the two thumbscrews on either side of the filter cover.
Step 4 Remove the filter faceplate.
Step 5 Pull out the filter and discard it.
Note: This filter cannot be cleaned and reused.
Step 6 Insert the new filter until flush with the shelf.
Step 7 Install the filter faceplate.
Step 8 Tighten the two thumbscrews on either side of the filter cover.
Step 9 Replace the fuses to turn the fan on.
Step 10 Update the servicing schedule in accordance with local procedures.
You have completed this task.
Page 6-10 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.4: Replacing Power (PW2H-HS) Unit in the HSShelf
6.4 Replacing Power (PW2H-HS) Unit in the HS Shelf
CAUTION:
An electrostatic discharge (ESD) wrist strap with a minimum resistance of 1 megohm should be worn when handling FLM units to prevent possible damage to the units. Before using the strap, check for opens, shorts, and minimum resistance value. If the strap does not pass these checks, it should not be used.
6.4.1 Procedure
Refer to Section 6.2, Removing and Installing Electrical Plug-In Units, before performing this procedure.
Step 1 Check the fuse in the PW2H-HS unit. Is the fuse good?
Step 2 Check the distribution panel fuse. Is it good?
Step 3 Replace the fuse. Does the new fuse operate correctly?
Step 4 Check the power at the distribution panel. Is it acceptable?
Step 5 Check the power at the backplane. Is it acceptable?
If yes: If no:
Go to Step 2. Go to Step 3.
If yes: If no:
Go to Step 4. Go to Step 3.
If yes: If no:
Go to Step 11. Go to Step 4.
If yes: If no:
Go to Step 5. Go to Step 6.
If yes: If no:
Go to Step 8. Go to Step 6.
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-11
6.4: Replacing Power (PW2H-HS) Unit in the HS Shelf
Maintenance and Trouble ClearingFJTU-320-560-480
Step 6 Correct the problem with the wiring or power levels.
Step 7 Check the LED on the PW2H-HS unit. Is the green light on?
Step 8 Have you already replaced the PW2H-HS unit once?
Step 9 Get a replacement PW2H-HS unit and inspect it for possible damage and debris. Figure 6-6 is a view of the PW2H-HS unit front panel. Remove the fuse from the new unit.
Note: No option settings exist on the PW2H-HS unit.
Step 10 Remove the old PW2H-HS unit from the PW2H slot, and replace it with the new PW2H-HS unit. Reinstall the fuse on the new unit.
Step 11 Check the LED on the PW2H-HS unit. Is the green light on?
Step 12 Check the voltage on the PW2H-HS unit. Is the voltage acceptable?
Step 13 If required, record the new unit serial number and issue level on a copy of the data record form in the Plug-In Unit Installation practice (FJTU-320-560-220), Appendix A, Data Record Forms. Complete other fault-reporting documentation as necessary.
You have completed this task.
If yes: If no:
Go to Step 12. Go to Step 1.
If yes: If no:
Stop. Call Fujitsu for technical assistance at 1-800-USE-FTAC (1-800-873-3822).
Go to Step 9.
If yes: If no:
Go to Step 12. Go to Step 12.
If yes: If no:
Go to Step 13. Go to Step 4.
Page 6-12 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.4: Replacing Power (PW2H-HS) Unit in the HSShelf
Figure 6-6: PW2H-HS Front Panel
FUSE2.0A
DN
273
5.1
PW2H-HS
PWR
FC
9607
PW
H1
+5.0V
SG
MAIN
G
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-13
6.5: Replacing the Microprocessor (MP2H-xxx) Unit in the HS Shelf
Maintenance and Trouble ClearingFJTU-320-560-480
6.5 Replacing the Microprocessor (MP2H-xxx) Unit in the HS Shelf
CAUTION:
An electrostatic discharge (ESD) wrist strap with a minimum resistance of 1 megohm should be worn when handling FLM units to prevent possible damage to the units. Before using the strap, check for opens, shorts, and minimum resistance value. If the strap does not pass these checks, it should not be used.
6.5.1 Procedure
CAUTION:
When replacing an MP2H unit, ensure that the replacement unit matches the type of unit being removed. Insertion of the wrong unit type could interrupt traffic.
Step 1 Get a replacement MP2H unit and inspect it for possible damage and debris. Figure 6-7 is a view of the MP2H-T11 unit; Figure 6-8 is a view of the MP2H-DL/-DLB/-DLS units; and Figure 6-9 is a view of the MP2H-T12/-SLV/-B1 units.
Step 2 Remove the failed unit.
Step 3 For the MP2H-T11/-DL/-DLB/-DLS unit, set the MASTER/SLAVE option switch to the same position as the removed MP2H unit. The option switch on the MP2H-DL/-DLB/-DLS unit is preset at the factory. The unit is set to master (MP2H-DL/-DLB) or slave (MP2H-DLS).
Note: The MP2H-T12, MP2H-SLV, and MP2H-B1 units do not have option settings. The MP2H units must be placed in their appropriate slots.
Step 4 Install the replacement unit in the MP2H slot and wait 5 minutes for a reset to occur. After 5 minutes, is the FAIL LED on the MP2H unit on?
Step 5 Push the CPU RESET button on the MP2H.
If yes: If no:
Go to Step 5. Go to Step 7.
Page 6-14 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.5: Replacing the Microprocessor (MP2H-xxx)Unit in the HS Shelf
Step 6 Is the FAIL LED on the MP2H unit lit?
Step 7 If required, record the new unit serial number and issue level on a copy of the data record form in the Plug-In Unit Installation practice (FJTU-320-560-220), Appendix A, Data Record Forms. Complete other fault-reporting documentation as necessary.
You have completed this task.
If yes: If no:
Multiple troubles exist and trouble analysis must be repeated. Refer to Section 4.2, Response Procedure. After the trouble is resolved, go to Step 7
Go to Step 7.
Figure 6-7: MP2H-T11 Switch Location
d529
8.2
MASTER
SLAVE
FC9607MPT1
MP2H-T11
FAIL
CPURESET
1 2
—OPEN—
1 2
—OPEN—
= Depressed (factory default).
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-15
6.5: Replacing the Microprocessor (MP2H-xxx) Unit in the HS Shelf
Maintenance and Trouble ClearingFJTU-320-560-480
Figure 6-8: MP2H-DL/-DLB/-DLS Switch Location
d657
3.3
SW 1
OP
EN
SLAVEMASTER
SW 1
—O
PE
N—
SLAVEMASTER 1
2
21
FAIL
FC9607MPD1
MP2H-DL
CPURESET
= Depressed (factory default)
Page 6-16 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.5: Replacing the Microprocessor (MP2H-xxx)Unit in the HS Shelf
Figure 6-9: MP2H Front Panels
FC9607MPT3
MP2H-T12
FAIL
CPURESET
DN
512
6
DN
516
2.1
FC9607MPS1
MP2H-SLV
FAIL
CPURESET
d586
1.2
FC9607MPB1
MP2H-B1
FAIL
CPURESET
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-17
6.6: Replacing Supervisory (SV2H-T11/-T12/-B1/-DL/-DLB) Unit in the HS Shelf
Maintenance and Trouble ClearingFJTU-320-560-480
6.6 Replacing Supervisory (SV2H-T11/-T12/-B1/-DL/-DLB) Unit in the HS Shelf
CAUTION:
An electrostatic discharge (ESD) wrist strap with a minimum resistance of 1 megohm should be worn when handling FLM units to prevent possible damage to the units. Before using the strap, check for opens, shorts, and minimum resistance value. If the strap does not pass these checks, it should not be used.
6.6.1 Procedure
CAUTION:
When replacing an SV2H unit, ensure that the replacement unit matches the type of unit being removed. Insertion of the wrong unit type could interrupt traffic.
Step 1 Get a replacement SV2H unit and inspect it for possible damage and debris.
Note: SV2H-T11 supports TL1/FLEXR interfaces and does not support TSA x 48.
Note: SV2H-T12, -DL, and -DLB support TL1/FLEXR interfaces and all tributary facility types. They also support the HM2H-A1 unit (TSA x 48).
Note: SV2H-B1, -DL, and -DLB support TL1/FLEXR interfaces and all tributary facility types. They also support the HM2H-B1 and HM2H-C1 units (TSA 24 x 24 x 48).
Step 2 Remove the failed unit.
Step 3 Set all option switches to the same position as the removed SV2H unit. Figure 6-10 shows the switch locations and settings, and a view of the SV2H-T11 unit front panel. Figure 6-11 shows switch locations and settings, and a view of the SV2H-T12 unit front panel. Figure 6-12 shows switch locations and settings and a view of the SV2H-B1 unit front panel. Figure 6-13 shows switch locations and settings, and a view of the SV2H-DL/-DLB unit front panel.
Page 6-18 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.6: Replacing Supervisory (SV2H-T11/-T12/-B1/-DL/-DLB) Unit in the HS Shelf
Step 4 Install the replacement SV2H unit into the SV2H slot. Is the FAIL LED on the SV2H unit lighted red?
Step 5 If required, record the new unit serial number and issue level on a copy of the data record form in the Plug-In Unit Installation practice (FJTU-320-560-220), Appendix A, Data Record Forms. Complete other fault-reporting documentation as necessary.
You have completed this task.
If yes: If no:
Multiple troubles exist and trouble analysis must be repeated. Refer to Section 4.2, Response Procedure. After the trouble is resolved, go to Step 5.
Go to Step 5.
Figure 6-10: SV2H-T11 Switch Locations and Front Panel
d529
3.6
—OPEN—
= Depressed (factory default)
OS
S
-OPEN-
B-B
ON
OFF
1 2 3 4 5
FAILLINEACS
FC9607SVT1
TERM
SV2H-T11
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-19
6.6: Replacing Supervisory (SV2H-T11/-T12/-B1/-DL/-DLB) Unit in the HS Shelf
Maintenance and Trouble ClearingFJTU-320-560-480
Figure 6-11: SV2H-T12 Switch Locations and Front Panel
= Depressed (factory default)
-OPEN-
B-B
OS
S
OT
HE
RS
LNR
21
d529
4.6
FAILLINEACS
FC9607SVT4
TERM
SV2H-T12
-OPEN-
B-B
OS
S
OT
HE
RS
LNR
21
Page 6-20 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.6: Replacing Supervisory (SV2H-T11/-T12/-B1/-DL/-DLB) Unit in the HS Shelf
Figure 6-12: SV2H-B1 Switch Locations and Front Panel
d595
0.3
FAILLINEACS
FC9607SVB1
TERM
SV2H-B1
—OPEN—
1 2
SW 1
B-B
OS
S
OT
HE
RS
LNR
SW 1
B-B
OS
S
OT
HE
RS
LNR
= Depressed (factory default)
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-21
6.6: Replacing Supervisory (SV2H-T11/-T12/-B1/-DL/-DLB) Unit in the HS Shelf
Maintenance and Trouble ClearingFJTU-320-560-480
Figure 6-13: SV2H-DL/-DLB Front Panel
d657
1.3
B-B
OS
S
OT
HE
RS
LIN
EA
R
OT
HE
RS
1:N
LIN
EA
R
FAILLINEACS
FC9607SVD1
TERM
SV2H-DL
SWDL
= Depressed (factory default)
B-B
OS
S
OT
HE
RS
LIN
EA
R
OT
HE
RS
1:N
LIN
EA
R
-OPEN-
4321
Page 6-22 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.7: Replacing the High-Speed Switch(HS2H-xxxx) Unit in the HS Shelf
6.7 Replacing the High-Speed Switch (HS2H-xxxx) Unit in the HS Shelf
CAUTION:
An electrostatic discharge (ESD) wrist strap with a minimum resistance of 1 megohm should be worn when handling FLM units to prevent possible damage to the units. Before using the strap, heck for opens, shorts, and minimum resistance value. If the strap does not pass these checks, it should not be used.
6.7.1 Procedure
Step 1 When alarm trouble indicates, get a replacement HS2H unit.
Step 2 Remove the failed unit.
Step 3 Verify that you have the correct HS2H unit for your configuration and inspect it for damage or debris. Refer to the following figures for verification.
• Figure 6-14 shows the HS2H-ADM1 unit front panel.
• Figure 6-15 shows the HS2H-A1DL unit front panel.
• Figure 6-16 shows the HS2H-A2DL unit front panel.
• Figure 6-17 shows the HS2H-B1/-B1DL units front panel.
• Figure 6-18 shows the HS2H-U1 unit front panel.
• Figure 6-19 shows the HS2H-LTE1 unit front panel.
• Figure 6-20 shows a typical HS2H-REG/-RNG/-RNG2 units front panel.
Step 4 If the unit to be replaced is an HS2H-ADM1/-A1DL/-A2DL unit, set all option switches to the same position as the failed HS2H-ADM1/-A1DL/-A2DL. See Figure 6-14 for a view of the option settings for the HS2H-ADM1, HS2H-A1DL, and HS2H-A2DL units. The other HS2H units do not have option switches.
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-23
6.7: Replacing the High-Speed Switch (HS2H-xxxx) Unit in the HS Shelf
Maintenance and Trouble ClearingFJTU-320-560-480
Step 5 Install the replacement HS2H unit in the HS2H slot. Is the FAIL LED on the HS2H unit lighted red?
Step 6 If required, record the new unit serial number and issue level on a copy of the data record form in the Plug-In Unit Installation practice (FJTU-320-560-220), Appendix A, Data Record Forms. Complete other fault-reporting documentation as necessary.
You have completed this task.
If yes: If no:
Multiple troubles exist and trouble analysis must be repeated. Refer to Section 4.2, Response Procedure. After the trouble is resolved, go to Step 6.
Go to Step 6.
Figure 6-14: HS2H-ADM1/-A1DL /-A2DL Unit Option Settings and HS2H-ADM1 Front Panel
d 57
75.2
FAILLINE
FC9607HSA1
HS2H-ADM1
SW MODE
FORCE
MNL
AUTO
= Depressed (factory default)
MASTER
OP
EN
12
SLAVE
MASTER
OP
EN
12
SLAVE
Page 6-24 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.7: Replacing the High-Speed Switch(HS2H-xxxx) Unit in the HS Shelf
Figure 6-15: HS2H-A1DL Front Panel
d658
3
FC9607HSA4
HS2H-A1DL
FAIL
LINE
FORCE
AUTO
MNL
SW MODE
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-25
6.7: Replacing the High-Speed Switch (HS2H-xxxx) Unit in the HS Shelf
Maintenance and Trouble ClearingFJTU-320-560-480
Figure 6-16: HS2H-A2DL Unit Front Panel
d754
5
FC9607HSA7
HS2H-A2DL
FAIL
LINE
FORCE
AUTO
MNL
SW MODE
Page 6-26 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.7: Replacing the High-Speed Switch(HS2H-xxxx) Unit in the HS Shelf
Figure 6-17: HS2H-B1/-B1DL Front Panel
d585
9.4
FC9607HSB2
FAIL
LINE
RINGST
FRCE
AUTOMNL
HS2H-B1DL
SW MODE
FC9607HSB1
FAIL
LINE
RINGST
FRCE
AUTO
MNL
HS2H-B1
SW MODE
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-27
6.7: Replacing the High-Speed Switch (HS2H-xxxx) Unit in the HS Shelf
Maintenance and Trouble ClearingFJTU-320-560-480
Figure 6-18: HS2H-U1 Unit Front Panel
d754
4
FC9607HSU1
HS2H-U1
FAIL
LINE
FORCE
AUTO
MNL
SW MODE
Page 6-28 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.7: Replacing the High-Speed Switch(HS2H-xxxx) Unit in the HS Shelf
Figure 6-19: HS2H-LTE1 Front Panel
d577
6.1
FC9607HSL1
SW MODE
MNL
FAIL
HS2H-LTE1
LINE
FORCE
AUTO
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-29
6.7: Replacing the High-Speed Switch (HS2H-xxxx) Unit in the HS Shelf
Maintenance and Trouble ClearingFJTU-320-560-480
Figure 6-20: Typical HS2H-REG/-RNG-/-RNG2 Front Panel
o403
40.1
FC9607HSR1
HS2H-REG
FAIL
FC9607HSN1
FAIL
HS2H-RNG
OD
14-0
328
FC9607HSN2
FAIL
HS2H-RNG2
OD
14-0
341
Page 6-30 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.8: Replacing the Alarm and Orderwire Alarm(AW2H-A1/-A2) Unit in the HS Shelf
6.8 Replacing the Alarm and Orderwire Alarm (AW2H-A1/-A2) Unit in the HS Shelf
CAUTION:
An electrostatic discharge (ESD) wrist strap with a minimum resistance of 1 megohm should be worn when handling FLM units to prevent possible damage to the units. Before using the strap, check for opens, shorts, and minimum resistance value. If the strap does not pass these checks, it should not be used.
6.8.1 Procedure
Step 1 When alarm trouble indicates, get a replacement AW2H unit, verify that you have the correct unit for your configuration, and inspect it for possible damage and debris.
Step 2 Remove the failed unit.
Step 3 Set all option switches to the same position as on the removed AW2H unit. Refer to Figure 6-21 for the option locations and settings and a front-panel view of the AW2H-A1 unit. Refer to Figure 6-22 for the option locations and settings and a front-panel view of the AW2H-A2 unit.
Step 4 Install the replacement AW2H unit in the AW2H slot.
Step 5 Did the alarm clear?
If yes: If no:
Go to Step 6. Multiple troubles exist and trouble analysis must be repeated. Refer to Section 4.2, Response Procedure. After the trouble is resolved, go to Step 6.
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-31
6.8: Replacing the Alarm and Orderwire Alarm (AW2H-A1/-A2) Unit in the HS Shelf
Maintenance and Trouble ClearingFJTU-320-560-480
Step 6 If required, record the new unit serial number and issue level on a copy of the data record form in the Plug-In Unit Installation practice (FJTU-320-560-220), Appendix A, Data Record Forms. Complete other fault-reporting documentation as necessary.
Figure 6-21: AW2H-A1 Unit Option Location and Front Paneld5
299.
4
PWR FAIL ALM
PWR FAIL ALM
PWR FAIL ALM
PWR FAIL ALM
AMJ ACR
AMJ ACR
VMJ VCR
VMJ VCR
SLAVE MASTER
SLAVE MASTER
VF CUT
THR1 2
Default Settings
TM7PWR FAIL ALM
LED MJ LED CR
CRMJMN
FC9607AWA1
AW2H-A1
ABN
ACO
LAMPTST
PWR FAIL ALM
LED MJ LED CR
PWR FAIL ALM
PWR FAIL ALM
PWR FAIL ALM
PWR FAIL ALM
AMJ ACR
AMJ ACR
VMJ VCR
VMJ VCR
SLAVE MASTER
SLAVE MASTER
VF CUT
THR1 2
Page 6-32 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.8: Replacing the Alarm and Orderwire Alarm(AW2H-A1/-A2) Unit in the HS Shelf
You have completed this task.
Figure 6-22: AW2H-A2 Unit Option Location and Front Panel
d530
1.6
SLA
VE
MA
ST
ER
PWR FAIL ALM
ACR AMJ
VCR VMJ
LED CR LED MJ
THRU CUT
Default Settings
SLA
VE
MA
ST
ER
PWR FAIL ALM
ACR AMJ
VCR VMJ
LED CR LED MJ
Default Settings
CMNDIS
CMNENTHRU CUT
CMNDIS
CMNEN
CRMJMN
FC9607AWA
AW2H-A2
ABN
ACO
LAMPTST
CALL
PHONE
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-33
6.9: Replacing the High-Speed Multiplexer (HM2H-xx) Unit in the HS Shelf
Maintenance and Trouble ClearingFJTU-320-560-480
6.9 Replacing the High-Speed Multiplexer (HM2H-xx) Unit in the HS Shelf
CAUTION:
An electrostatic discharge (ESD) wrist strap with a minimum resistance of 1 megohm should be worn when handling FLM units to prevent possible damage to the units. Before using the strap, check for opens, shorts, and minimum resistance value. If the strap does not pass these checks, it should not be used.
Step 1 When alarm trouble clearing indicates a new unit is needed, get a replacement HM2H unit and inspect it for possible damage and debris. Verify that you have the correct type HM2H unit for your configuration.
Step 2 Disconnect the 78-Mb/s cable (Refer to the Plug-In Unit Installation practice, FJTU-320-560-220, Section 6.6, Installing High-Speed Multiplexer (HM2H) Unit in the HS Shelf) and remove the failed HM2H unit (Section 6.1, Removing and Installing Optical Channel Units, in this practice).
Step 3 Set all option switches to the same positions as on the removed unit. Refer to the following figures:
• Figure 6-23 for the view of the option switches on the HM2H-A1/-A2/-B1/-C1 units
• Figure 6-24 for the view of the HM2H-A1/-A2 front panels
• Figure 6-25 for the front-panel view of the newer version of the HM2H-A3 unit
• Figure 6-26 for the option locations, settings, and a front-panel view of the previous version of the HM2H-A3 unit
• Figure 6-27 for the front-panel view of the HM2H-B1 unit
• Figure 6-28 for the front-panel view of the HM2H-C1 unit.
Step 4 Set the option switch on the HM2H-A3 to REG. This option only exists on some older versions of the card (Figure 6-26).
Step 5 Connect the 78-Mb/s cable (FJTU-320-560-220, Section 6.6) and install the new HM2H unit (Section 6.1 in this practice) in the HM2H slot.
Page 6-34 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.9: Replacing the High-Speed Multiplexer(HM2H-xx) Unit in the HS Shelf
Step 6 Is the FAIL/SVC LED on the new unit lighted red?
If yes: If no:
Multiple troubles exist and trouble analysis must be repeated. Refer to Section 4.2, Response Procedure. After the trouble is resolved, go to Step 7.
Go to Step 7.
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-35
6.9: Replacing the High-Speed Multiplexer (HM2H-xx) Unit in the HS Shelf
Maintenance and Trouble ClearingFJTU-320-560-480
Step 7 If required, record the new unit serial number and issue level on a copy of the data record form in the Plug-In Unit Installation practice (FJTU-320-560-220), Appendix A, Data Record Forms. Complete other fault-reporting documentation as necessary.
Figure 6-23: HM2H-A1/A2/B1/-C1 Unit Option Switches
HM2H-A1/-B1/-C1 HM2H-A2
LBO
SE
TSW1
GP4 CN6
GP3 CN5
GP2 CN4
GP1 CN3
d521
5.17O
PE
N
12
34
5
OFF ON
GP4 CN6
GP3 CN5
GP2 CN4
GP1 CN3
CABLELENGTH
0-250 FT250-500 FT500-750 FT
LBO SETTING
1 2 3 4 5
ONOFFOFF
ONOFFOFF
OFFONOFF
OFFONOFF
OFFOFFON
Note: This table is imprintedon the back of the unit
Note: Switches are underdaughter board
OPEN
12345
OF
FO
N
OPEN
12345
OF
FO
N
OP
EN
12
34
5
OFF ON
Page 6-36 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.9: Replacing the High-Speed Multiplexer(HM2H-xx) Unit in the HS Shelf
Figure 6-24: HM2H-A1 and A2 Unit Front Panels
d516
1.1
FUSE3.2A
FC9607HMA1
HM2H-A1
ATTENTION
Push the lever ofthe unit lower part toremove the coaxunit as shown inthe figure.
FAIL/SVCELINE
d284
1.5
FUSE2.0A
FC9607HMA2
HM2H-A2
ATTENTION
Push the lever ofthe unit lower part toremove the coaxunit as shown inthe figure.
FAIL/SVCELINE
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-37
6.9: Replacing the High-Speed Multiplexer (HM2H-xx) Unit in the HS Shelf
Maintenance and Trouble ClearingFJTU-320-560-480
Figure 6-25: Newer Version of HM2H-A3
OD
14-0
066
FUSE1.0A
FC9607HMA3
HM2H-A3
FAIL/SVCE
ATTENTION
Push the lever ofthe unit lower part toremove the coaxunit as shown inthe figure
Page 6-38 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.9: Replacing the High-Speed Multiplexer(HM2H-xx) Unit in the HS Shelf
Figure 6-26: Option Switch of Previous Version of HM2H-A3
REG
CN
100
LTE-P
CQ
14-0
246-
92
FUSE1.0A
FC9607HMA3
HM2H-A3
FAIL/SVCE
ATTENTION
Push the lever ofthe unit lower part toremove the coaxunit as shown inthe figure
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-39
6.9: Replacing the High-Speed Multiplexer (HM2H-xx) Unit in the HS Shelf
Maintenance and Trouble ClearingFJTU-320-560-480
Figure 6-27: HM2H-B1 Front Panel
d585
6.5
FC9607HMB1
HM2H-B1
ATTENTION
Push the lever ofthe unit lower part toremove the coaxunit as shown inthe figure.
FUSE2.0A
FAIL/SVC
LINE
Page 6-40 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.9: Replacing the High-Speed Multiplexer(HM2H-xx) Unit in the HS Shelf
You have completed this task.
Figure 6-28: HM2H-C1 Front Panel
d754
7.1
FC9607HMC1
HM2H-C1
ATTENTION
Push the lever ofthe unit lower part toremove the coaxunit as shown inthe figure.
FUSE2.0A
FAIL/SVC
LINE
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-41
6.10: Replacing the High-Speed Transmit Channel (HT2H-xxxx) Unit in the HS Shelf
Maintenance and Trouble ClearingFJTU-320-560-480
6.10 Replacing the High-Speed Transmit Channel (HT2H-xxxx) Unit in the HS Shelf
CAUTION:
An electrostatic discharge (ESD) wrist strap with a minimum resistance of 1 megohm should be worn when handling FLM units to prevent possible damage to the units. Before using the strap, check for opens, shorts, and minimum resistance value. If the strap does not pass these checks, it should not be used.
6.10.1 Procedure
Step 1 When an alarm indicates a new HT2H unit is needed, get a replacement and inspect it for possible damage and debris. Refer to Figure 6-29 for a view of the front panel. Verify that you have the correct type HT2H unit for the application (refer to Table 6-2).
Step 2 Remove the failed unit. Refer to Section 6.1, Removing and Installing Optical Channel Units.
Step 3 On the new replacement unit, remove the protective cap and clean the optical connections. Refer to Section 7.2, Cleaning the Optical Connectors.
Table 6-2: HT2H-xxxx Family Name and Part Number
Family Name (HT2H-xxxx) Part Number (FC9607xxxx)
-LR1B HTL1
-LR1H HTL3
-LR2B HTL2
-LR2H HTL4
-LR1S HTL5
-LR2S HTL7
-L1BC HTL6
-L2BC HTL8
-L1BD HTD1
-L2BD HTD2
Page 6-42 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.10: Replacing the High-Speed TransmitChannel (HT2H-xxxx) Unit in the HS Shelf
Step 4 Install the HT2H unit into the HT2H slot. Refer to Section 6.1, Removing and Installing Optical Channel Units.
Step 5 Measure optical transmit level. Refer to Section 7.4, Measuring the Optical Transmit Unit Output Power.
Step 6 Connect the optical fiber to the unit. Refer to Section 7.3, Connect/Disconnect Optical Cables, and to Section 6.1.
Step 7 Plug the HT2H unit into the HT2H slot. Refer to Section 6.1 in this practice.
Step 8 Is the FAIL/SVCE LED green?
Step 9 Check the HR2H unit at the remote terminal. Are the FAIL and LINE LED off?
Step 10 Replace the HR2H unit at the remote terminal. Refer to Section 6.11. Is the FAIL/SVCE LED green on the local HT2H unit?
Step 11 Is the FAIL/SVCE LED green on the local HT2H unit?
Step 12 If required, record the new unit serial number and issue level on a copy of the data record form in the Plug-In Unit Installation practice (FJTU-320-560-220), Appendix A, Data Record Forms. Complete other fault-reporting documentation as necessary.
If yes: If no:
Go to Step 12. Go to Step 9.
If yes: If no:
Go to Step 11. Go to Step 10.
If yes: If no:
Go to Step 12. Trouble analysis must be repeated. Refer to Section 4.2, Response Procedure. After the trouble is resolved, go to Step 12.
If yes: If no:
Go to Step 12. Call Fujitsu for technical assistance at 1-800-USE-FTAC (1-800-873-3822).
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-43
6.10: Replacing the High-Speed Transmit Channel (HT2H-xxxx) Unit in the HS Shelf
Maintenance and Trouble ClearingFJTU-320-560-480
Step 13 If required by local procedures, run test traffic to ensure that the replacement unit is working properly.
You have completed this task.
Figure 6-29: HT2H-xxxx Front Panel
FAIL/SVCE
FUSE2.0A
FC9607HTXX
HT2H-XXXX
o4-0
326.
1
DANGERInvisible laserradiation from
connectorswhen uncoupledAVOID DIRECT
EXPOSURETO BEAM
Page 6-44 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.11: Replacing High-Speed Receive Channel(HR2H-xxxx) Unit in the HS Shelf
6.11 Replacing High-Speed Receive Channel (HR2H-xxxx) Unit in the HS Shelf
CAUTION:
An electrostatic discharge (ESD) wrist strap with a minimum resistance of 1 megohm should be worn when handling FLM units to prevent possible damage to the units. Before using the strap, check for opens, shorts, and minimum resistance value. If the strap does not pass these checks, it should not be used.
Step 1 When an alarm indicates a new HR2H unit is needed, get a replacement and inspect it for possible damage and debris. Refer to Figure 6-30 for a view of a typical HR2H unit. Verify that you have the correct type of HR2H unit for your application (refer to Table 6-3).
Step 2 Remove the failed unit. Refer to Section 6.1, Removing and Installing Optical Channel Units of this practice.
Step 3 On the new replacement unit, remove the protective cap and clean the optical connections. Refer to Section 7.2, Cleaning the Optical Connectors, of this practice.
Step 4 Install the HR2H unit into the HR2H slot. Refer to Section 6.1.
Table 6-3: HR2H-xxxx Family Name and Part Number
Family Name (HR2H-xxxx) Part Number (FC9607xxxx)
-LR1B HRL1
-LR1H HRL3
-LR2B HRL2
-LR2H HRL4
-LR1S HRL5
-LR2S HRL7
-L1BC HRL6
-L2BC HRL8
-L1BD HRD1
-L2BD HRD2
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-45
6.11: Replacing High-Speed Receive Channel (HR2H-xxxx) Unit in the HS Shelf
Maintenance and Trouble ClearingFJTU-320-560-480
Step 5 Measure optical receive levels. Refer to Section 7.5, Measuring the Optical Receive Unit Input Power.
Step 6 Connect the optical fiber to the unit. Refer to Section 7.3, Connect/Disconnect Optical Cables, and to Section 6.1.
Step 7 Plug the HR2H unit into the HR2H slot. Refer to Section 6.1.
Step 8 Are the FAIL and LINE LEDs off?
Step 9 Check the HT2H unit at the remote terminal. Is the FAIL LED off?
Step 10 Replace the HT2H unit at the remote terminal. Are the FAIL and LINE LEDs off on the local HR2H unit?
Step 11 If required, record the new unit serial number and issue level on a copy of the data record form in the Plug-In Unit Installation practice (FJTU-320-560-220), Appendix A, Data Record Forms. Complete other fault-reporting documentation as necessary.
If yes: If no:
Go to Step 11. Go to Step 9.
If yes: If no:
Further trouble analysis is required. Call Fujitsu for technical assistance at 1-800-USE-FTAC (1-800-873-3822).
Go to Step 10.
If yes: If no:
Go to Step 11. Further trouble analysis is required. Refer to Section 4.2, Response Procedure. After the trouble is resolved, go to Step 11
Page 6-46 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.11: Replacing High-Speed Receive Channel(HR2H-xxxx) Unit in the HS Shelf
Step 12 If required by local procedures, run test traffic to ensure that the replacement unit is working properly.
You have completed this task.
Figure 6-30: Typical HR2H-xxxx Front Panel
DANGERInvisible laserradiation fromconnectors
when uncoupledAVOID DIRECT
EXPOSURETO BEAM
c402
36.1
FUSE2.0A
FC9607HRXX
HR2H-XXXX
FAIL/SVCELINE
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-47
6.12: Replacing Power Unit (PW1A/PW1A-TRIB) Unit in the HD TRIB Shelf
Maintenance and Trouble ClearingFJTU-320-560-480
6.12 Replacing Power Unit (PW1A/PW1A-TRIB) Unit in the HD TRIB Shelf
CAUTION:
An electrostatic discharge (ESD) wrist strap with a minimum resistance of 1 megohm should be worn when handling FLM units to prevent possible damage to the units. Before using the strap, check for opens, shorts, and minimum resistance value. If the strap does not pass these checks, it should not be used.
Note: Do not mix the PW1A units and the PW1A-TRIB units in the same shelf.
Note: The PW1A does not support OC-3 or OC-12 interfaces in the High-Density Tributary (HD TRIB) Shelf. If either of these interfaces are found on the shelf, PW1A-TRIB units must be used. The PW1A-TRIB units will work with all HD TRIB configurations.
Step 1 Get a replacement PW1A or PW1A-TRIB unit and inspect for possible damage and debris. Refer to Figure 6-31 for a view of the front panels.
Step 2 Remove the failed PW1A/PW1A-TRIB unit.
Step 3 Verify that the power switch on the replacement PW1A/PW1A-TRIB unit is turned OFF.
Step 4 Install the PW1A/PW1A-TRIB unit in the vacant PW1A slot and turn the power switch to the ON position.
Step 5 Is the green PWR LED on the PW1A/PW1A-TRIB unit lighted?
Step 6 Check the wiring of the power supply terminal. Is the wiring correct?
Step 7 Repair the wiring.
Step 8 Turn the power switch to the ON position.
If yes: If no:
Go to Step 10. Turn the power switch on the PW1A/PW1A-TRIB unit OFF, and continue with Step 6.
If yes: If no:
Go to Step 8. Go to Step 7.
Page 6-48 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.12: Replacing Power Unit (PW1A/PW1A-TRIB)Unit in the HD TRIB Shelf
Step 9 Is the green PWR LED on the PW1A/PW1A-TRIB unit lighted?
Step 10 Connect the leads of a digital multimeter (DMM) to the MAIN and G test jacks on the front of the unit (see Figure 6-31 for the front-panel view). Record the test results in Table 6-4.
Step 11 Check the main voltage. Is it acceptable?
Step 12 Turn the power switch on the PW1A/PW1A-TRIB to the OFF position.
Step 13 Check the wiring of the power supply terminal. Is the wiring connected properly?
Step 14 Turn the power switch to the ON position. Remeasure the main voltage and then proceed to Step 15.
Step 15 Connect the DMM test leads to the SG (+5.4 V and –5.6 V) test jacks on the front panel of the unit to check that the secondary voltage is within standards (Figure 6-31). Record the test results in Figure 6-4.
Step 16 Did all the voltage readings satisfy the specifications shown in Figure 6-4?
If yes: If no:
Go to Step 10. Call Fujitsu for technical assistance at 1-800-USE-FTAC (1-800-873-3822).
If yes: If no:
Go to Step 15. Continue with Step 12.
Turn power switch to the ON position.
Go to Step 15.
Connect wiring properly, or repair wiring according to local procedures.
If yes: If no:
Disconnect the DMM test leads and go to Step 17.
Call Fujitsu for technical assistance at 1-800-USE-FTAC (1-800-873-3822).
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-49
6.12: Replacing Power Unit (PW1A/PW1A-TRIB) Unit in the HD TRIB Shelf
Maintenance and Trouble ClearingFJTU-320-560-480
Step 17 If required, record the new unit serial number and issue level on a copy of the data record form in the Plug-In Unit Installation practice (FJTU-320-560-220), Appendix A, Data Record Forms. Complete other fault-reporting documentation as necessary.
You have completed this task.
Table 6-4: PWR1 Power Voltage
Terminal No Load (V dc) Unit 1 Test Result (V dc) Unit 2 Test Result (V dc)
MAIN –40 to –56.7
+5.4V +5.02 to +6.21
–5.6V –5.15 to –6.44
Figure 6-31: PW1A and PW1A-TRIB Unit Front Panels
PWR
+5.4V
-5.6V
SG
MAIN
G
ON
OFF
PWR
FC9612PW11
PW1A
DN
277
2.1
PWR
+5.4V
-5.6V
SG
MAIN
G
ON
OFF
PWR
FC9608PW11
PW
1A-T
RIB
OD
14-0
311.
1
USE ONLY INFLM 2400 ADM HD
Page 6-50 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.13: Replacing Microprocessor (MP2T-T11/-T12/-DL) Unit in the HD TRIB Shelf
6.13 Replacing Microprocessor (MP2T-T11/-T12/-DL) Unit in the HD TRIB Shelf
CAUTION:
An electrostatic discharge (ESD) wrist strap with a minimum resistance of 1 megohm should be worn when handling FLM units to prevent possible damage to the units. Before using the strap, check for opens, shorts, and minimum resistance value. If the strap does not pass these checks, it should not be used.
6.13.1 Procedure
CAUTION:
When replacing an MP2T unit, ensure that the replacement unit matches the type of unit being removed. Insertion of the wrong unit type could interrupt traffic.
Step 1 Remove the failed unit.
Step 2 Get a replacement MP2T and inspect it for possible damage and debris. Refer to Figure 6-32 for a view of the MP2T-T11/-T12/-DL unit front panels.
Step 3 Install the replacement MP2T unit in the MP2T slot. Is the FAIL LED on MP2T lighted red?
Step 4 Push the CPU RESET button on the MP2T unit and wait for the system to reset.
Step 5 Is the FAIL LED on MP2T lighted red?
If yes: If no:
Go to Step 4. Go to Step 6.
If yes: If no:
Trouble analysis must be repeated. Refer to Section 4.2, Response Procedure. After the trouble is resolved, go to Step 6.
Go to Step 6.
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-51
6.13: Replacing Microprocessor (MP2T-T11/-T12/-DL) Unit in the HD TRIB Shelf
Maintenance and Trouble ClearingFJTU-320-560-480
Step 6 If required, record the new unit serial number and issue level on a copy of the data record form in the Plug-In Unit Installation practice (FJTU-320-560-220), Appendix A, Data Record Forms. Complete other fault-reporting documentation as necessary.
You have completed this task.
Figure 6-32: MP2T-T11/-T12/-DL Front Panels
FC
9608
MP
D2
MP2T-DL
FAIL
CPURESET
d657
8
FC
9608
MP
T1
MP2T-T11
FAIL
d277
5.2
CPURESET
FC
9608
MP
T2
MP2T-T12
FAIL
CPURESET
d514
9.2
Page 6-52 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.14: Replacing Middle-Speed Switch for DS3/STS-1 (MS2T-D31) Unit in the HD TRIB Shelf
6.14 Replacing Middle-Speed Switch for DS3/STS-1 (MS2T-D31) Unit in the HD TRIB Shelf
CAUTION:
An electrostatic discharge (ESD) wrist strap with a minimum resistance of 1 megohm should be worn when handling FLM units to prevent possible damage to the units. Before using the strap, check for opens, shorts, and minimum resistance value. If the strap does not pass these checks, it should not be used.
6.14.1 Procedure
Step 1 Get a replacement MS2T-D31 and inspect it for possible damage and debris. Refer to Figure 6-33 for a view of the MS2T-D31 unit front panels.
Step 2 Remove the failed MS2T-D31.
Step 3 Install the replacement MS2T-D31 in the MS2T slot.
Step 4 Is the FAIL/ON PTCT LED lighted red?
If yes: If no:
Multiple troubles exist, and trouble analysis should be repeated. Refer to Section 4.2, Response Procedure. After the trouble is resolved, go to Step 5.
Go to Step 5.
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-53
6.14: Replacing Middle-Speed Switch for DS3/STS-1 (MS2T-D31) Unit in the HD TRIB Shelf
Maintenance and Trouble ClearingFJTU-320-560-480
Step 5 If required, record the new unit serial number and issue level on a copy of the data record form in the Plug-In Unit Installation practice (FJTU-320-560-220), Appendix A, Data Record Forms. Complete other fault-reporting documentation as necessary.
You have completed this task.
Figure 6-33: MS2T-D31 Front Panel
FAILON PTCT
FC9608MSD3
MS2T-D31
OD
4-00
42
Page 6-54 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.15: Replacing High-Speed Switch (HS2T-xxxx)Unit in the HD TRIB Shelf
6.15 Replacing High-Speed Switch (HS2T-xxxx) Unit in the HD TRIB Shelf
CAUTION:
An electrostatic discharge (ESD) wrist strap with a minimum resistance of 1 megohm should be worn when handling FLM units to prevent possible damage to the units. Before using the strap, check for opens, shorts, and minimum resistance value. If the strap does not pass these checks, it should not be used.
6.15.1 Procedure
Step 1 Get a replacement HS2T-xxxx unit and inspect it for possible damage and debris.
Step 2 Remove the failed HS2T-xxxx unit from the shelf.
Step 3 Install the replacement HS2T-xxxx unit into the HS2T slot. Refer to the following figures:
• Figure 6-34 for a view of the HS2T-C3 front panel and option switches on both the HS2T-C3 and HS2T-C3DL units
• Figure 6-35 for a view of the HS2T-C3DL front panel
• Figure 6-36 for a view of the HS2T-C3D2 front panel
• Figure 6-37 for a view of the HS2T-D3 front panel
• Figure 6-38 for a view of the HS2T-S1/-SDL/-SDL2 front panels.
Step 4 If you are replacing an HS2T-C3/-C3DL unit, make sure the option switches on the new unit have been set to match the settings on the old unit. Figure 6-34 shows option settings and a view of the HS2T-C3 front panel. Figure 6-35 shows a view of the HS2T-C3DL front panel.
Step 5 Is the FAIL LED on the HS2T-xxxx unit lighted red?
If yes: If no:
Multiple troubles exist, and trouble analysis should be repeated. Refer to Section 4.2, Response Procedure. After the trouble is resolved, go to Step 6.
Go to Step 6.
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-55
6.15: Replacing High-Speed Switch (HS2T-xxxx) Unit in the HD TRIB Shelf
Maintenance and Trouble ClearingFJTU-320-560-480
Step 6 If required, record the new unit serial number and issue level on a copy of the data record form in the Plug-In Unit Installation practice (FJTU-320-560-220), Appendix A, Data Record Forms. Complete other fault-reporting documentation as necessary.
Figure 6-34: HS2T-C3 Front Panel and HS2T-C3/-C3DL Option Switches
d563
7.4
TH
RU
HS
TR
IB
1 2
OPEN
CU
T
OC12
OC3
1 2
OPEN
LIN
E 1
LIN
E 2
OF
FO
N
OC12
OC3
TH
RU
HS
TR
IB
1 2
OPEN
CU
T
FC
9608
HS
C3
FAIL
LINE
HS2T-C3
1 2
OPEN
LIN
E 1
LIN
E 2
OF
FO
N
Page 6-56 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.15: Replacing High-Speed Switch (HS2T-xxxx)Unit in the HD TRIB Shelf
Figure 6-35: HS2T-C3DL Front Panel
d658
4
FC
9608
HS
C4
HS2T-C3DL
FAIL
LINE
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-57
6.15: Replacing High-Speed Switch (HS2T-xxxx) Unit in the HD TRIB Shelf
Maintenance and Trouble ClearingFJTU-320-560-480
Figure 6-36: HS2T-C3D2 Front Panel
d756
2
FC
9608
HS
C6
HS2T-C3D2
FAIL
LINE
Page 6-58 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.15: Replacing High-Speed Switch (HS2T-xxxx)Unit in the HD TRIB Shelf
Figure 6-37: HS2T-D3 Front Panel
FAIL
FC9608HSD3
HS2T-D3C
Q14
-027
1-92
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-59
6.15: Replacing High-Speed Switch (HS2T-xxxx) Unit in the HD TRIB Shelf
Maintenance and Trouble ClearingFJTU-320-560-480
You have completed this task.
Figure 6-38: HS2T-S1/-SDL/-SDL2 Front Panelso4
0312
.2
FAIL
FC
9608
HS
S2
HS2T-SDL
LINE
FAIL
FC
9608
HS
S4
HS2T-SDL2
LINE
FAIL
FC
9608
HS
S1
HS2T-S1
LINE
Page 6-60 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.16: Replacing High-Speed Channel(HC2T-MDL/-C12L) Unit in the HD TRIB Shelf
6.16 Replacing High-Speed Channel (HC2T-MDL/-C12L) Unit in the HD TRIB Shelf
CAUTION:
An electrostatic discharge (ESD) wrist strap with a minimum resistance of 1 megohm should be worn when handling FLM units to prevent possible damage to the units. Before using the strap, check for opens, shorts, and minimum resistance value. If the strap does not pass these checks, it should not be used.
6.16.1 Procedure
Step 1 Get a replacement HC2T-MDL/-C12L unit and inspect it for possible damage and debris. Verify that you have the correct HC2T-MDL/-C12L unit to use in the HD TRIB Shelf.
Step 2 Disconnect the bridge cable from the HC2T-MDL unit if the OC-3 configuration is being used. Refer to the Plug-In Unit Installation practice, FJTU-320-560-220, Section 8.11, Installing High-Speed Channel (HC2T-MDL/-C12L) Unit in the HD TRIB Shelf.
Step 3 Disconnect the 78-Mb/s cable from the HC2T-MDL/C12L unit. Refer to the Plug-In Unit Installation practice, FJTU-320-560-220, Section 8.11.
Step 4 Remove the failed unit.
Step 5 Set the option switches to the same positions as on the removed HC2T-MDL/-C12L unit. Figure 6-39 shows option settings and a view of the HC2T-MDL unit front panel. Figure 6-40 shows option settings and a view of the HC2T-C12L unit front panel.
Step 6 Connect the 78-Mb/s cable to the HC2T-MDL/-C12L unit. Refer to the Plug-In Unit Installation practice, FJTU-320-560-220, Section 8.11.
Note: If the HC2T-MDL unit is being used in an OC-3 configuration, connect the bridge cable.
Step 7 Install the HC2T-MDL/-C12L unit in the HC2T slot.
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-61
6.16: Replacing High-Speed Channel (HC2T-MDL/-C12L) Unit in the HD TRIB Shelf
Maintenance and Trouble ClearingFJTU-320-560-480
Step 8 Is the FAIL/SVC LED green?
Step 9 Is the LINE LED off?
If yes: If no:
Go to Step 9. Repeat Steps 1 through 7 if this is the first time the unit has been replaced. If this is the second time the unit has been replaced, call Fujitsu for technical assistance at 1-800-USE-FTAC (800-873-3822).
If yes: If no:
If local procedures allow, switch to the new unit to verify operation, then go to Step 10
Call Fujitsu for technical assistance at 1-800-USE-FTAC (800-873-3822).
Page 6-62 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.16: Replacing High-Speed Channel(HC2T-MDL/-C12L) Unit in the HD TRIB Shelf
Step 10 If required, record the new unit serial number and issue level on a copy of the data record form in the Plug-In Unit Installation practice (FJTU-320-560-220), Appendix A, Data Record Forms. Complete other fault-reporting documentation as necessary.
Figure 6-39: HC2T-MDL Unit Front Panel and Hardware Option Switch Locations
ON
OFF
LBO SET
1 2 3 4
OPEN
5
FAIL/SVCELINE
FC
9608
HC
M1
HC2T-MDL
ON
OFF
LBO SET
1 2 3 4
OPEN
5
CABLELENGTH
0-250 FT250-500 FT500-750 FT
LBO SETTING
1 2 3 4 5
ONOFFOFF
ONOFFOFF
OFFONOFF
OFFONOFF
OFFOFFON
Note: This table is imprinted on the back of the unit
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-63
6.16: Replacing High-Speed Channel (HC2T-MDL/-C12L) Unit in the HD TRIB Shelf
Maintenance and Trouble ClearingFJTU-320-560-480
You have completed this task.
Figure 6-40: HC2T-C12L Unit Front Panel and Hardware Option Switch Locations
d5
63
9.7
OFF
ON
Note: This table is imprinted on theback of the unit.
OPEN
LBO SET
1 2 3 4 5
FAIL/SVCE
LINE
FC
9608
HC
21
HC2T-C12L
OFF
ON
OPEN
LBO SET
1 2 3 4 5
FUJITSU
CABLELENGTH
0-250 FT250-500 FT500-750 FT
LBO SETTING
1 2 3 4 5
ONOFFOFF
ONOFFOFF
OFFONOFF
OFFONOFF
OFFOFFON
Page 6-64 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.17: Replacing Optical Middle-Speed Interface(MC6A-2Lxx) Unit in the HD TRIB Shelf
6.17 Replacing Optical Middle-Speed Interface (MC6A-2Lxx) Unit in the HD TRIB Shelf
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.
CAUTION:
An electrostatic discharge (ESD) wrist strap with a minimum resistance of 1 megohm should be worn when handling FLM units to prevent possible damage to the units. Before using the strap, check for opens, shorts, and minimum resistance value. If the strap does not pass these checks, it should not be used.
CAUTION:
To avoid damage to a fiber optic-cable or fiber pigtail, or fiber, read handling notes in accordance with Section 7.1, Handling the Fiber Cables Correctly.
6.17.1 Procedure
Step 1 Remove the front cover from the optical cable tray located on the top front of the shelf.
Step 2 Perform the unit removal procedure described in Section 6.1, Removing and Installing Optical Channel Units.
Step 3 Get a replacement MC6A-2Lxx unit and inspect it for possible damage and debris. Refer to Figure 6-41 for a view of the front panel.
Note: No hardware option settings exist on the MC6A-2Lxx.
Step 4 Clean the optical cables and make the connections (refer to Section 7.3, Connect/Disconnect Optical Cables).
Step 5 Measure input/output power for the unit. Refer to Section 7.4, Measuring the Optical Transmit Unit Output Power, and Section 7.5, Measuring the Optical Receive Unit Input Power.
Step 6 Replace the front cover on the optical tray.
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-65
6.17: Replacing Optical Middle-Speed Interface (MC6A-2Lxx) Unit in the HD TRIB Shelf
Maintenance and Trouble ClearingFJTU-320-560-480
Step 7 If required, record the new unit serial number and issue level on a copy of the data record form in the Plug-In Unit Installation practice (FJTU-320-560-220), Appendix A, Data Record Forms. Complete other fault-reporting documentation as necessary.
Step 8 If required by local procedures, run test traffic to ensure that the replacement unit is working properly.
You have completed this task.
Figure 6-41: MC6A-2Lxx Unit Front Panel
FC9608XXXX
MC6A-2XXX
FAIL
LINE
SEND
RCV
DANGER
DN
563
8
ONLINE
Page 6-66 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.18: Replacing Optical Middle-Speed Interface(MC6A-31xx) Unit in the HD TRIB Shelf
6.18 Replacing Optical Middle-Speed Interface (MC6A-31xx) Unit in the HD TRIB Shelf
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.
CAUTION:
An electrostatic discharge (ESD) wrist strap with a minimum resistance of 1 megohm should be worn when handling FLM units to prevent possible damage to the units. Before using the strap, check for opens, shorts, and minimum resistance value. If the strap does not pass these checks, it should not be used.
CAUTION:
To avoid damage to a fiber-optic cable or fiber pigtail, or fiber, read handling notes in accordance with Section 7.1, Handling the Fiber Cables Correctly.
6.18.1 Procedure
Step 1 Remove the front cover from the optical cable tray located on the top front of the shelf.
Step 2 Perform the unit removal procedure described in Section 6.1, Removing and Installing Optical Channel Units.
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-67
6.18: Replacing Optical Middle-Speed Interface (MC6A-31xx) Unit in the HD TRIB Shelf
Maintenance and Trouble ClearingFJTU-320-560-480
Step 3 Get a replacement MC6A-31xx unit and inspect it for possible damage and debris. Refer to the following figures:
• Figure 6-42 for a view of a typical MC6A-31xx front panel.
Note: This unit does not have hardware option settings.
• Figure 6-43 for a view of the MC6A-31xL/-31xM (Issue 2) and the MC6A-31xS (Issue 2 and later) front panel and hardware option switch locations.
• Figure 6-44 for a view of the MC6A-31xA front panel and hardware option switch locations.
• Figure 6-45 for a view of the MC6A-31xL (Issue 3) front panel and hardware option switch location.
• Figure 6-46 for a view of the MC6A-31xM (Issue 3) front panel and hardware option switch location.
Note: The MC6A-31xA is the unit that uses multimode fiber. The other 31xx units use single-mode fibers.
Step 4 Set all option switches on the replacement MC6A unit to the same position as on the removed MC6A unit. For option switch locations, refer to Figures 6-43 through 6-46. If the unit being replaced has an MR/LR switch option, ensure the switch is set to the factory default setting. Refer to the FLM 2400 ADM Unit Descriptions practice, FJTU-320-515-000, for a detailed description of the hardware option switches and default settings for these units.
Step 5 Clean the optical cables and make the connections (refer to Section 7.3, Connect/Disconnect Optical Cables).
Step 6 Measure input/output power for the unit. Refer to Section 7.4, Measuring the Optical Transmit Unit Output Power, and Section 7.5, Measuring the Optical Receive Unit Input Power.
Step 7 Replace the front cover on the optical tray.
Step 8 If required, record the new unit serial number and issue level on a copy of the data record form in the Plug-In Unit Installation practice (FJTU-320-560-220), Appendix A, Data Record Forms. Complete other fault-reporting documentation as necessary.
Page 6-68 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.18: Replacing Optical Middle-Speed Interface(MC6A-31xx) Unit in the HD TRIB Shelf
Step 9 If required by local procedures, run test traffic to ensure that the replacement unit is working properly.
Figure 6-42: Typical MC6A-31xx Unit Front Panel
FC9616xx31
MC6A-31xx
FAIL
LINE
SEND
RCV
ON LINE
DA
NG
ER
d563
5.4
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-69
6.18: Replacing Optical Middle-Speed Interface (MC6A-31xx) Unit in the HD TRIB Shelf
Maintenance and Trouble ClearingFJTU-320-560-480
Figure 6-43: MC6A-31xL/-31xM (Issue 2) and MC6A-31xS (Issue 2 and later) Unit Front Panel and Hardware Option Switch Locations
OC3 I/F MODE
SDHSONET OP
EN
12
d733
9.1
FC9616LRx1
MC6A-31xL
FAIL
LINE
SEND
RCV
ON LINE
DA
NG
ER
Optical Connector
OC3 I/F MODE
SDHSONET OP
EN
12
Page 6-70 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.18: Replacing Optical Middle-Speed Interface(MC6A-31xx) Unit in the HD TRIB Shelf
Figure 6-44: MC6A-31xA Unit Front Panel and Hardware Option Switch Locations
OC3 I/F MODE
SDHSONET OP
EN
12
d758
1
FC9616MMx1
MC6A-31xA
FAIL
LINE
SEND
RCV
ON LINE
DA
NG
ER
Optical Connector
OC3 I/F MODE
SDHSONET OP
EN
12
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-71
6.18: Replacing Optical Middle-Speed Interface (MC6A-31xx) Unit in the HD TRIB Shelf
Maintenance and Trouble ClearingFJTU-320-560-480
Figure 6-45: MC6A-31xL (Issue 3) Unit Front Panel and Hardware Option Switch Locationsm
0660
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
LR
MR
OC3 I/FMODE
SDHSONET OP
EN
12 LRMR
Page 6-72 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.18: Replacing Optical Middle-Speed Interface(MC6A-31xx) Unit in the HD TRIB Shelf
You have completed this task.
Figure 6-46: MC6A-31xM (Issue 3) Unit Front Panel and Hardware Option Switch Locationsm
0659
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
LR
MR
SDHSONET OP
EN
12 LRMR
OC3 I/FMODE
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-73
6.19: Replacing Middle-Speed Channel Clock Distribution (MC6A-2THR) Unit
Maintenance and Trouble ClearingFJTU-320-560-480
6.19 Replacing Middle-Speed Channel Clock Distribution (MC6A-2THR) Unit
CAUTION:
An electrostatic discharge (ESD) wrist strap with a minimum resistance of 1 megohm should be worn when handling FLM units to prevent possible damage to the units. Before using the strap, check for opens, shorts, and minimum resistance value. If the strap does not pass these checks, it should not be used.
6.19.1 Procedure
Step 1 Get a replacement MC6A-2THR and inspect it for possible damage and debris. Refer to Figure 6-47 for a view of the front panel.
Step 2 Remove the failed MC6A-2THR unit.
Step 3 Install the replacement MC6A-2THR in the MC6A slot. Is the FAIL LED on MC6A lighted red?
If yes: If no:
Trouble and analysis must be repeated. Refer to Section 4.2, Response Procedure. After the trouble is resolved, go to Step 4.
Go to Step 4.
Page 6-74 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.19: Replacing Middle-Speed Channel ClockDistribution (MC6A-2THR) Unit
Step 4 If required, record the new unit serial number and issue level on a copy of the data record form in the Plug-In Unit Installation practice (FJTU-320-560-220), Appendix A, Data Record Forms. Complete other fault-reporting documentation as necessary.
You have completed this task.
Figure 6-47: MC6A-2THR Unit Front Panel
FC
9608
MT
H1
MC6A-2THR
DN
564
0
FAIL
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-75
6.20: Replacing Middle-Speed Channel OC-3 Bridge (MC6A-3BRD) Unit in the HD TRIB Shelf
Maintenance and Trouble ClearingFJTU-320-560-480
6.20 Replacing Middle-Speed Channel OC-3 Bridge (MC6A-3BRD) Unit in the HD TRIB Shelf
CAUTION:
An electrostatic discharge (ESD) wrist strap with a minimum resistance of 1 megohm should be worn when handling FLM units to prevent possible damage to the units. Before using the strap, check for opens, shorts, and minimum resistance value. If the strap does not pass these checks, it should not be used.
6.20.1 Procedure
Step 1 Get a replacement MC6A-3BRD unit and inspect it for possible damage and debris.
Step 2 Remove the failed MC6A-3BRD unit from the shelf until the secondary latch engages. Refer to Section 6.1, Removing and Installing Optical Channel Units.
Step 3 Open the connector cover plate by loosening the thumbscrew at the top and letting the cover swing down. Refer to Figure 6-48.
Step 4 Disconnect the 8x78-Mb/s FC9607CAB4 cable from the High-Speed (HS) Shelf by removing the cable connector from connector CN2 that is located just above the cover hinge. To disconnect it, spread the two tabs to unlock the connector. Then finish disengaging the connection by gripping and pulling the cable connector, not the cable.
Step 5 Disconnect the Group 1 FC9608CAB1 cable from connector CN4 (the upper of the two stacked connectors; that is, the one away from the printed-circuit board). To disconnect it, spread the two tabs to unlock the connector. Then finish disengaging the connection by gripping and pulling the cable connector, not the cable.
Step 6 Remove the Group 2 FC9608CAB1 cable connector from connector CN3 (the lower of the two stacked connectors; that is, the one next to the printed-circuit board). To disconnect it, spread the two tabs to unlock the connector. Then finish disengaging the connection by gripping and pulling the cable connector, not the cable.
Page 6-76 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.20: Replacing Middle-Speed Channel OC-3Bridge (MC6A-3BRD) Unit in the HD TRIB Shelf
Step 7 If the opposite ends of the above three cables are not already disconnected from the HC2T-MDL (FC9608HCM1) and the HS Shelf units (HM2H-Ax, FC9607HMA1/2), refer to the Plug-In Unit Installation practice, FJTU-320-560-220, Section 8.7, Installing Middle-Speed Channel OC-3 Bridge (MC6A-3BRD) in the HD TRIB Shelf, for instructions.
Step 8 Finish removing the unit from the shelf.
Step 9 Install the replacement unit in the appropriate slot on the HD TRIB Shelf until the secondary latch engages.
Step 10 Insert the Group 2 FC9608CAB1 cable connector into connector CN3 (the lower of the two stacked connectors; that is, the one next to the printed-circuit board).
Step 11 Install the Group 1 FC9608CAB1 cable into CN4 (the upper of the two stacked connectors; that is, the one away from the printed-circuit board).
Step 12 Install the 8x78-Mb/s FC9607CAB4 cable from the HS Shelf by inserting the cable connector into connector CN2 that is located just above the cover hinge.
Step 13 If the opposite ends of the above three cables are not already connected to the HC2T-MDL (FC9608HCM1), refer to the Plug-In Unit Installation practice, FJTU-320-560-220, Section 8.11, Installing High-Speed Channel (HC2T-MDL/-C12L) Unit in the HD TRIB Shelf. For the HS Shelf units (HM2H-Ax, FC9607HMA1/2), refer to FJTU-320-560-220, Section 6.6, Installing High-Speed Multiplexer (HM2H) Unit in the HS Shelf for instructions.
Step 14 Dress the three cables to lie side by side as they exit the front of the unit.
Step 15 Close the connector cover plate and secure it with the thumbscrew.
Step 16 Carefully seat the unit.
Step 17 If required, record the new unit serial number and issue level on a copy of the data record form in the Plug-In Unit Installation practice (FJTU-320-560-220), Appendix A, Data Record Forms. Complete other fault-reporting documentation as necessary.
You have completed this task.
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-77
6.20: Replacing Middle-Speed Channel OC-3 Bridge (MC6A-3BRD) Unit in the HD TRIB Shelf
Maintenance and Trouble ClearingFJTU-320-560-480
Figure 6-48: MC6A-3BRD Unit and Cable Connectors
d620
0.2
FC9608BR31
CN2
CN3 -(For cable connectionto HC2T Group 2 - W slot)
CN4 -(For cable connectionto HC2T Group 1 - W slot)
MC
6A
-3B
RD
FAIL/
SVCE
Page 6-78 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.21: Replacing DS3/EC-1 Interface (MC6A-D3/-D3E2/-ST1E/-ST1P) Unit in the HD TRIB Shelf
6.21 Replacing DS3/EC-1 Interface (MC6A-D3/ -D3E2/-ST1E/-ST1P) Unit in the HD TRIB Shelf
CAUTION:
An electrostatic discharge (ESD) wrist strap with a minimum resistance of 1 megohm should be worn when handling FLM units to prevent possible damage to the units. Before using the strap, check for opens, shorts, and minimum resistance value. If the strap does not pass these checks, it should not be used.
6.21.1 Procedure
Step 1 Obtain a replacement MC6A-D3E/-D3E2/-ST1E/-ST1P unit, and inspect it for possible damage and debris.
Step 2 Remove the failed unit.
Step 3 Set all option switches on the replacement unit to the same position as the removed unit. Refer to the following figures:
• Figure 6-49 for the front panel and hardware option switch locations for the MC6A-D3E/D3E2 unit
• Figure 6-50 for the front panel and hardware option switch for the MC6A-ST1E unit
• Figure 6-51 for the front panel and hardware option switch for the MC6A-ST1P unit.
Step 4 Install the replacement unit. Is the LINE LED off and the FAIL/SVCE LED green?
Step 5 Check the incoming DSX-3/STSX-1 signal at the DSX-3/STSX-1 bay. Is the signal present at the bay?
If yes: If no:
Go to Step 7. Go to Step 5.
If yes: If no:
Go to Step 6. The trouble is not with the FLM 2400 ADM. Refer to Section 4.2, Response Procedure, then go to Step 7.
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-79
6.21: Replacing DS3/EC-1 Interface (MC6A-D3/ -D3E2/-ST1E/-ST1P) Unit in the HD TRIB Shelf
Maintenance and Trouble ClearingFJTU-320-560-480
Step 6 Repeat the trouble and analysis procedures (see Section 4.2, Response Procedure in this practice). Is the LINE LED off and the FAIL/SVCE LED green?
If yes: If no:
Go to Step 7. Call Fujitsu for technical assistance at 1-800-USE-FTAC (1-800-873-3822).
Page 6-80 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.21: Replacing DS3/EC-1 Interface (MC6A-D3/-D3E2/-ST1E/-ST1P) Unit in the HD TRIB Shelf
Step 7 If required, record the new unit serial number and issue level on a copy of the data record form in the Plug-In Unit Installation practice (FJTU-320-560-220), Appendix A, Data Record Forms. Complete other fault-reporting documentation as necessary.
Figure 6-49: MC6A-D3E/D3E2 Unit and Front Panel and Hardware Option Locationsd5
303.
8
= Depressed (factory default)
SETTHR
SETTHR
SETTHR
1 2
LBO
CH
1
1 2
LBO
CH
2
1 2
LBO
CH
3
1 2
LBO
CH
1
1 2
LBO
CH
2
1 2
LBO
CH
3
FC
9608
MD
33
MC6A-D3E2
US
E O
NLY
IN
FL
M 2
400
AD
M H
D
FAIL/SVCE
1
2
3
LINE
Note: This table is imprinted on theback of the unit.
CABLELENGTH
LBO SETTINGS
0-100 FT
100-225 FT
325-450 FT THR THR
THR SET
SET SET
1 2
225-325 FT SET THR
SETTHR
SETTHR
SETTHR
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-81
6.21: Replacing DS3/EC-1 Interface (MC6A-D3/ -D3E2/-ST1E/-ST1P) Unit in the HD TRIB Shelf
Maintenance and Trouble ClearingFJTU-320-560-480
Figure 6-50: MC6A-ST1E Unit and Front Panel and Hardware Option Location
FC
9616
ST
14M
C6A
-ST
1E
FAIL/SVCE
1
2
3
LINE
d734
4
CableLength(feet)
LBO-SETTING
0 - 100
100 - 225
225 - 325
325 - 450 THR THR
SET THR
THR SET
SET SET
1 2LBO
CH
1LB
OC
H2
LBO
CH
3
21
21
21
THR
SET
THR
SET
THR
SET
Page 6-82 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.21: Replacing DS3/EC-1 Interface (MC6A-D3/-D3E2/-ST1E/-ST1P) Unit in the HD TRIB Shelf
You have completed this task.
Figure 6-51: MC6A-ST1P Unit and Front Panel and Hardware Option Location
FC
9616
ST
15M
C6A
-ST
1P
FAIL/SVCE
1
2
3
LINE
d734
5
CableLength(feet)
LBO-SETTING
0 - 100
100 - 225
225 - 325
325 - 450 THR THR
SET THR
THR SET
SET SET
1 2LBO
CH
1LB
OC
H2
LBO
CH
3
21
21
21
THR
SET
THR
SET
THR
SET
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-83
6.22: Replacing Power (PW6A) Unit in the FLM 600 ADM TRIB Shelf
Maintenance and Trouble ClearingFJTU-320-560-480
6.22 Replacing Power (PW6A) Unit in the FLM 600 ADM TRIB Shelf
CAUTION:
An electrostatic discharge (ESD) wrist strap with a minimum resistance of 1 megohm should be worn when handling FLM units to prevent possible damage to the units. Before using the strap, check for opens, shorts, and minimum resistance value. If the strap does not pass these checks, it should not be used.
6.22.1 Procedure
Step 1 Get a replacement PW6A unit and inspect for possible damage and debris. Refer to Figure 6-53 for a view of the front panel of the PW6A unit and the digital multimeter.
Step 2 Is the power switch turned to the OFF position on the new PW6A?
Step 3 Install the replacement PW6A unit in the PW6A slot and turn the power switch to the ON position.
Step 4 Is the red PWR LED on the PW6A unit lighted?
Step 5 Is the wiring of the power terminal correct? See Figure 6-52.
Step 6 Remove the PW6A and repair the wiring.
Step 7 Install the removed PW6A unit in the PW6A slot and turn the power switch to the ON position.
If yes: If no:
Proceed to Step 3. Turn the switch to the OFF position and proceed with Step 3.
If yes: If no:
Turn the power switch on the PW6A to the OFF position, remove the unit, and then continue with Step 5.
Ensure that the PWR LED is lighted green, then go to Step 14.
If yes: If no:
Then proceed to Step 9. Then continue to Step 6.
Page 6-84 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.22: Replacing Power (PW6A) Unit in the FLM600 ADM TRIB Shelf
Step 8 Is the PWR LED on the PW6A unit lighted red?
Step 9 Connect the leads of the digital multimeter (DMM) to the MAIN and G jack on the front of the PW6A unit. Refer to Figure 6-53 for a view of the DMM.
Step 10 Is the indicated voltage on the DMM between –42 V dc and –56 V dc?
Note: A faulty power source or power wiring in the facility shelf caused the alarm.
Step 11 Disconnect the leads of DMM and repair the power source or wiring to clear conditions that caused the alarm to activate. Go to Step 7.
Step 12 If the PWR LED on the PW6A is still lighted red, multiple troubles exist and trouble analysis must be repeated. Refer to Section 4.2, Response Procedure. After the trouble analysis has been completed, go to Step 13.
Step 13 Is the PWR LED on the PW6A still lighted red?
If yes: If no:
Turn the power switch on the PW6A to the OFF position. Go to Step 9.
Ensure that the PWR LED is lighted green, then go to Step 14.
If yes: If no:
Go to Step 12. Go to Step 11.
If yes: If no:
Call Fujitsu for technical assistance at 1-800-USE-FTAC (1-800-873-3822).
Go to Step 14.
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-85
6.22: Replacing Power (PW6A) Unit in the FLM 600 ADM TRIB Shelf
Maintenance and Trouble ClearingFJTU-320-560-480
Step 14 If required, record the new unit serial number and issue level on a copy of the data record form in the Plug-In Unit Installation practice (FJTU-320-560-220), Appendix A, Data Record Forms. Complete other fault-reporting documentation as necessary.
Figure 6-52: Power Terminal Connector
CN10
OD
2-00
32
CN9 CN1CN3CN5CN8
CN2CN4CN6CN7
MODEM2.4GINF OSS1OHA2H.K.2ALM
OHA1H.K.1OW/E2A1
OW/E2A2
MAIN A
MAIN B
FG
G B
G A
PWR
Page 6-86 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.22: Replacing Power (PW6A) Unit in the FLM600 ADM TRIB Shelf
You have completed this task.
Figure 6-53: PW6A Unit Front Panel and Digital Multimeter
PW6A
PWR
FC9616PW61
+5.4V
-5.6V
SG
MAIN
G
PWRON
d245
8.3
DIGITAL MULTIMETER
VDC
VΩ COM AMP
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-87
6.23: Replacing Microprocessor (MP6A-24G/-24DL) Unit in the FLM 600 ADM TRIB Shelf
Maintenance and Trouble ClearingFJTU-320-560-480
6.23 Replacing Microprocessor (MP6A-24G/-24DL) Unit in the FLM 600 ADM TRIB Shelf
CAUTION:
An electrostatic discharge (ESD) wrist strap with a minimum resistance of 1 megohm should be worn when handling FLM units to prevent possible damage to the units. Before using the strap, check for opens, shorts, and minimum resistance value. If the strap does not pass these checks, it should not be used.
6.23.1 Procedure
CAUTION:
When replacing an MP6A unit, ensure that the replacement unit matches the type of unit being removed. Insertion of the wrong unit type could interrupt traffic.
Step 1 Get a replacement MP6A-24G/-24DL unit and inspect it for possible damage and debris. Refer to Figure 6-54 for a view of the MP6A-24G front panel. See Figure 6-55 for a view of the MP6A-24DL front panel and option switches.
Step 2 Remove the failed MP6A-24G/-24DL unit.
Step 3 For the MP6A-24DL unit, set the option switches to the same positions as on the removed unit. Refer to Figure 6-55 for a view of option settings.
Step 4 Install the replacement MP6A unit into the MP6A slot. Wait 5 minutes for a reset to occur.
Step 5 After waiting 5 minutes: Is the FAIL LED on MP6A lighted red?
Step 6 Push the CPU RESET button on the MP6A unit. Is the FAIL LED on MP6A lighted red?
If yes: If no:
Go to Step 6. Go to Step 7.
If yes: If no:
Trouble and analysis procedure must be repeated. Refer to Section 4.2, Response Procedure. After the trouble is resolved, go to Step 7.
Go to Step 7.
Page 6-88 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.23: Replacing Microprocessor (MP6A-24G/-24DL) Unit in the FLM 600 ADM TRIB Shelf
Step 7 If required, record the new unit serial number and issue level on a copy of the data record form in the Plug-In Unit Installation practice (FJTU-320-560-220), Appendix A, Data Record Forms. Complete other fault-reporting documentation as necessary.
Figure 6-54: MP6A-24G Front Panel
MP6A-24G
CPURESET
FAIL
FC9616MPG1
w05
03.1
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-89
6.23: Replacing Microprocessor (MP6A-24G/-24DL) Unit in the FLM 600 ADM TRIB Shelf
Maintenance and Trouble ClearingFJTU-320-560-480
You have completed this task.
Figure 6-55: MP6A-24DL Unit Front Panel and Option Switches
d676
2
FC9616MPD2
MP6A-24DL
FAIL
FESEL
CPURESET
EQPT. NO.
3 4
5
91
2
0
678
91
2 3 4
0 5678
EQPT NO.
(1-9)600
600
TR
IB
-OPEN-
600/
600
TR
IBS
ELE
CT
= Depressed (factory default).
600
600
TR
IB
-OPEN-
Page 6-90 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.24: Replacing Supervisory Interface(SV6A-24G/-TDL1) Unit in the FLM 600 ADM TRIB
6.24 Replacing Supervisory Interface (SV6A-24G/-TDL1) Unit in the FLM 600 ADM TRIB
CAUTION:
An electrostatic discharge (ESD) wrist strap with a minimum resistance of 1 megohm should be worn when handling FLM units to prevent possible damage to the units. Before using the strap, check for opens, shorts, and minimum resistance value. If the strap does not pass these checks, it should not be used.
6.24.1 Procedure
CAUTION:
When replacing an SV6A unit, ensure that the replacement unit matches the type of unit being removed. Insertion of the wrong unit type could interrupt traffic.
Step 1 Get a replacement SV6A-24G or SV6A-TDL1 and inspect it for possible damage and debris. Refer to Figure 6-56 for a view of the SV6A-24G front panel. See Figure 6-57 for a view of the front panel and option switches for the SV6A-TDL1 unit.
Note: The SV6A-24G unit used for the software download (SWDL) platform must be Issue 3 or later.
Note: The SV6A-TDL1 unit used for SWDL platform must be Issue 4 or later.
Step 2 Remove the failed unit.
Step 3 For SV6A-TDL1 set all of the option switches to the same position as on the removed unit. Refer to Figure 6-57 for a view of the option switches.
Step 4 Install the replacement SV6A-24G or SV6A-TDL1 in the SV6A slot. For the SV6A-TDL1 unit, wait 5 minutes for a reset to occur.
Step 5 (For the SV6A-TDL1 unit, it is necessary to wait 5 minutes for a reset to occur.) Did the alarm clear?
If yes: If no:
Go to Step 6. Call Fujitsu for technical assistance at 1-800-USE-FTAC (1-800-873-3822).
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-91
6.24: Replacing Supervisory Interface (SV6A-24G/-TDL1) Unit in the FLM 600 ADM TRIB
Maintenance and Trouble ClearingFJTU-320-560-480
Step 6 If required, record the new unit serial number and issue level on a copy of the data record form in the Plug-In Unit Installation practice (FJTU-320-560-220), Appendix A, Data Record Forms. Complete other fault-reporting documentation as necessary.
Figure 6-56: SV6A-24G Unit Front Panel
SV6A-24G
FC9616SVG1
w05
02
Page 6-92 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.24: Replacing Supervisory Interface(SV6A-24G/-TDL1) Unit in the FLM 600 ADM TRIB
You have completed this task.
Figure 6-57: SV6A-TDL1 Front Panel and Option Switches
FC9616SVD1
SV6A-TDL1
TERM
FAIL
ACS
B-B
LINE
OSS
-OP
EN
-
SELECTOSS CLOCK
600
600
TR
IB
-OPEN-
600/
600
TR
IBS
ELE
CT
SWDL
d594
1.2
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-93
6.25: Replacing Alarm and Orderwire (AW6A-BSC/-ENH) Unit in the FLM 600 ADM TRIB Shelf
Maintenance and Trouble ClearingFJTU-320-560-480
6.25 Replacing Alarm and Orderwire (AW6A-BSC/-ENH) Unit in the FLM 600 ADM TRIB Shelf
CAUTION:
An electrostatic discharge (ESD) wrist strap with a minimum resistance of 1 megohm should be worn when handling FLM units to prevent possible damage to the units. Before using the strap, check for opens, shorts, and minimum resistance value. If the strap does not pass these checks, it should not be used.
6.25.1 Procedure
Step 1 Get a replacement AW6A unit and inspect it for possible damage and debris.
Step 2 Remove the failed unit.
Step 3 Set the option switches to the same position as on the removed AW6A. Refer to Figure 6-58 for option switch locations and settings and a front-panel view of the AW6A-ENH unit. Refer to Figure 6-59 for option switch locations and settings and a front-panel view of the AW6A-BSC unit.
Step 4 Install the replacement AW6A unit into the AW6A slot.
Step 5 Did the alarm clear?
If yes: If no:
Go to Step 6. Call Fujitsu for technical assistance at 1-800-USE-FTAC (1-800-873-3822).
Page 6-94 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.25: Replacing Alarm and Orderwire (AW6A-BSC/-ENH) Unit in the FLM 600 ADM TRIB Shelf
Step 6 If required, record the new unit serial number and issue level on a copy of the data record form in the Plug-In Unit Installation practice (FJTU-320-560-220), Appendix A, Data Record Forms. Complete other fault-reporting documentation as necessary.
Figure 6-58: AW6A-ENH Unit Option Settings and Front-Panel Indications
2.4G
600M
VMJ
AMJ
VCR
ACR
PWR FAIL ALM CMN EN
CMN DIS
d368
6.5LED
MJLEDCR
CMN EN
CMN DIS
= Depressed (factory default).
= Strap (factory default).
1 2
2.4G
600M
1 2
VMJ
AMJ
VCR
ACR
PWR FAIL ALM
LEDMJ
LEDCR
FC9616AWE1
AW6A-ENH
LAMPTST
CALL
PHONE
ACO
CRMJMN
ABN
NEACTFEACT
PMN
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-95
6.25: Replacing Alarm and Orderwire (AW6A-BSC/-ENH) Unit in the FLM 600 ADM TRIB Shelf
Maintenance and Trouble ClearingFJTU-320-560-480
You have completed this task.
Figure 6-59: AW6A-BSC Unit Option and Front-Panel Indications
FC9616AWB1
ACO
AW6A-BSC
CRMJ
MNABN
LAMPTST
NEACTFEACT
d625
1.1600 M
2.4 G
FAIL ALM
VMJ VCR
AMJ ACR
LED MJ LED CR
1 2
PWR
CN1
CN3
CN2
CN4
FAIL ALM
VMJ VCR
AMJ ACR
LED MJ LED CR
PWR
CN1
CN3
CN2
CN4
600 M
2.4 G
1 2
Page 6-96 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.26: Replacing High-Speed Switch (HS6A-AD1/-AD2) Unit in the FLM 600 ADM TRIB Shelf
6.26 Replacing High-Speed Switch (HS6A-AD1/-AD2) Unit in the FLM 600 ADM TRIB Shelf
CAUTION:
An electrostatic discharge (ESD) wrist strap with a minimum resistance of 1 megohm should be worn when handling FLM units to prevent possible damage to the units. Before using the strap, check for opens, shorts, and minimum resistance value. If the strap does not pass these checks, it should not be used.
6.26.1 Procedure
Step 1 Obtain a replacement HS6A-AD1/AD2 and inspect it for possible damage and debris.
Step 2 Remove the failed unit.
Step 3 Set all option switches to the same position as on the removed HS6A unit and install the replacement HS6A unit in the HS6A slot. Refer to Figure 6-60 for a view of the HS6A unit front panel and option switch locations and settings.
Step 4 Is the LINE LED off and the FAIL LED green?
Step 5 If required, record the new unit serial number and issue level on a copy of the data record form in the Plug-In Unit Installation practice (FJTU-320-560-220), Appendix A, Data Record Forms. Complete other fault-reporting documentation as necessary.
You have completed this task.
If yes: If no:
Go to Step 5. Trouble analysis must be repeated. Refer to Section 4.2, Response Procedure. After the trouble is resolved, go to Step 5.
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-97
6.26: Replacing High-Speed Switch (HS6A-AD1/-AD2) Unit in the FLM 600 ADM TRIB Shelf
Maintenance and Trouble ClearingFJTU-320-560-480
Figure 6-60: HS6A-AD1/-AD2 Option Settings and Front-Panel Indications
DN
239
3.2
F1 SET
RESTR
MASTER SLAVE
HG1 MODE
FC9616SAM1
HS6A-AD1
FAIL
LINE
FORCE
AUTO
MNL
FORCE
AUTO
MNL
HG 2 MODE
12
34
OP
EN
1 TBOS2
Page 6-98 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.27: Replacing Middle-Speed Optical SwitchControl (MS6A-OPT/-OPT2) Unit
6.27 Replacing Middle-Speed Optical Switch Control (MS6A-OPT/-OPT2) Unit
CAUTION:
An electrostatic discharge (ESD) wrist strap with a minimum resistance of 1 megohm should be worn when handling FLM units to prevent possible damage to the units. Before using the strap, check for opens, shorts, and minimum resistance value. If the strap does not pass these checks, it should not be used.
6.27.1 Procedure
Step 1 Get a replacement MS6A-OPT/-OPT2 unit and inspect it for possible damage and debris. Refer to Figure 6-61 for a view of the front panels.
Step 2 Remove the failed unit.
Step 3 Install the replacement MS6A-OPT/-OPT2 unit in the MS6A slot.
Step 4 Is the FAIL LED off?
Step 5 Is the LINE LED off?
If yes: If no:
Go to Step 5. Multiple problems exist, and trouble analysis must be repeated. Refer to Section 4.2, Response Procedure. After the trouble is resolved, go to Step 5.
If yes: If no:
Go to Step 6. Call Fujitsu for technical assistance at 1-800-USE-FTAC (1-800-873-3822).
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-99
6.27: Replacing Middle-Speed Optical Switch Control (MS6A-OPT/-OPT2) Unit
Maintenance and Trouble ClearingFJTU-320-560-480
Step 6 If required, record the new unit serial number and issue level on a copy of the data record form in the Plug-In Unit Installation practice (FJTU-320-560-220), Appendix A, Data Record Forms. Complete other fault-reporting documentation as necessary.
You have completed this task.
Figure 6-61: MS6A-OPT/-OPT2 Unit Front Panels
MS
6A-O
PT
DN
405
4
FC9616MS61
FAIL
LINE
d690
4MS
6A-O
PT
2
FC9616MS62
FAIL
LINE
Page 6-100 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.28: Replacing Optical Channel (HC6A-xxxx/MC6A-xxxx) Unit in the FLM 600 ADM TRIB Shelf
6.28 Replacing Optical Channel (HC6A-xxxx/MC6A-xxxx) Unit in the FLM 600 ADM TRIB Shelf
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.
CAUTION:
To avoid damage to a fiber-optic cable, fiber pigtail, or fiber, read handling notes in accordance with Section 7.1, Handling the Fiber Cables Correctly, and Section 7.2, Cleaning the Optical Connectors.
CAUTION:
An electrostatic discharge (ESD) wrist strap with a minimum resistance of 1 megohm should be worn when handling FLM units to prevent possible damage to the units. Before using the strap, check for opens, shorts, and minimum resistance value. If the strap does not pass these checks, it should not be used.
6.28.1 Procedure
Step 1 Remove the front cover from the optical cable tray located on the top front of the shelf.
Step 2 Remove the failed optical HC6A/MC6A unit. Refer to Section 6.1, Removing and Installing Optical Channel Units.
Step 3 Get a replacement HC6A/MC6A unit and inspect for possible damage and debris. If replacing the MC6A-31xL/-31xM/-31xS unit, set the hardware option switches to the same settings as the failed unit. If the unit being replaced has an MR/LR switch option, ensure the switch is set to the factory default setting. Refer to the FLM 2400 ADM Unit Descriptions practice, FJTU-320-515-000, for a detailed description of the hardware option switches and default settings for these units.Refer to the following figures:
• Figure 6-62 for a view of a typical HC6A unit front panel
• Figure 6-63 for a view of the MC6A-31xx unit front panel
• Figure 6-64 for a view of the MC6A-31xL/-31xM (Issue 2), MC6A-31xS (Issue 2 and later), and MC6A-31xA unit front panels and hardware option switch locations.
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-101
6.28: Replacing Optical Channel (HC6A-xxxx/MC6A-xxxx) Unit in the FLM 600 ADM TRIB Shelf
Maintenance and Trouble ClearingFJTU-320-560-480
• Figure 6-65 for a view of the MC6A-31xL (Issue 3) unit front panels and hardware option switch locations.
• Figure 6-66 for a view of the MC6A-31xM (Issue 3) unit front panels and hardware option switch locations.
Step 4 Install the replacement HC6A/MC6A unit and reconnect the fibers. Refer to Section 7.1, Handling the Fiber Cables Correctly and Section 7.2, Cleaning the Optical Connectors, and Section 7.3, Connect/Disconnect Optical Cables.
Step 5 Measure input/output power for the unit. Refer to Section 7.4, Measuring the Optical Transmit Unit Output Power, and Section 7.5, Measuring the Optical Receive Unit Input Power.
Step 6 Is the LINE LED off and the FAIL LED green on the HC6A/MC6A unit?
Step 7 If required, record the new unit serial number and issue level on a copy of the data record form in the Plug-In Unit Installation practice (FJTU-320-560-220), Appendix A, Data Record Forms. Complete other fault-reporting documentation as necessary.
If yes: If no:
Go to Step 7. Multiple troubles exist, and trouble analysis must be repeated. Refer to Section 4.2, Response Procedure. After the trouble is resolved, go to Step 7.
Page 6-102 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.28: Replacing Optical Channel (HC6A-xxxx/MC6A-xxxx) Unit in the FLM 600 ADM TRIB Shelf
Step 8 If required by local procedures, run test traffic to ensure that the replacement unit is working properly.
Figure 6-62: Typical Optical Channel HC6A Unit Front Panel
d220
8.4
HC6A-6LR1
FC9616H6L1
DANGERInvisible laserradiation fromconnectors
when uncoupledAVOID DIRECT
EXPOSURETO BEAM
LINE
SEND
RCV
ONLINE
FAIL
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-103
6.28: Replacing Optical Channel (HC6A-xxxx/MC6A-xxxx) Unit in the FLM 600 ADM TRIB Shelf
Maintenance and Trouble ClearingFJTU-320-560-480
Figure 6-63: Typical Optical Channel MC6A-31xx Unit Front Panel
FC9616xx31
MC6A-31xx
FAIL
LINE
SEND
RCV
ON LINED
AN
GE
R
d563
5.4
Page 6-104 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.28: Replacing Optical Channel (HC6A-xxxx/MC6A-xxxx) Unit in the FLM 600 ADM TRIB Shelf
Figure 6-64: MC6A-31xL/-31xM/-31xS Unit Front Panel and Hardware Option Switch Locations
OC3 I/F MODE
SDHSONET OP
EN
12
d733
9.1
FC9616LRx1
MC6A-31xL
FAIL
LINE
SEND
RCV
ON LINE
DA
NG
ER
Optical Connector
OC3 I/F MODE
SDHSONET OP
EN
12
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-105
6.28: Replacing Optical Channel (HC6A-xxxx/MC6A-xxxx) Unit in the FLM 600 ADM TRIB Shelf
Maintenance and Trouble ClearingFJTU-320-560-480
Figure 6-65: MC6A-31xL (Issue 3) Unit Front Panel and Hardware Option Switch 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
LR
MR
OC3 I/FMODE
SDHSONET OP
EN
12 LRMR
Page 6-106 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.28: Replacing Optical Channel (HC6A-xxxx/MC6A-xxxx) Unit in the FLM 600 ADM TRIB Shelf
You have completed this task.
Figure 6-66: MC6A-31xM (Issue 3) Unit Front Panel and Hardware Option Switch 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
LR
MR
SDHSONET OP
EN
12 LRMR
OC3 I/FMODE
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-107
6.29: Replacing HS Electrical Interface (HC6A-6EL1/-6EL2) Units in the FLM 600 ADM TRIB
Maintenance and Trouble ClearingFJTU-320-560-480
6.29 Replacing HS Electrical Interface (HC6A-6EL1/-6EL2) Units in the FLM 600 ADM TRIB
This procedure is used for replacing the High-Speed Electrical Interface units (HC6A-6EL1/-6EL2). These units are used in the FLM 600 ADM TRIB Shelf and are required for interfacing with each high-speed group in the FLM 2400 ADM.
6.29.1 Procedure
Refer to Section 6.1, Removing and Installing Optical Channel Units, of this practice while performing this procedure.
Step 1 Remove the cover from the shelf.
Step 2 Get a replacement HC6A-6EL1 or HC6A-6EL2 unit and inspect for possible damage and debris. Use local platform compatibility information to verify that the Issue number of the replacement unit indicates full compatibility with the operational platform of the system. Refer to Figure 6-67 for front-panel and side views of the HC6A-6EL1 unit. See Figure 6-68 for front-panel and side views of the HC6A-6EL2 unit.
CAUTION:
The replacement unit must have the correct Issue number based on the operating system revision status of the network element. Traffic-affecting features of the system may not be supported by an incompatible issue of a unit.
Step 3 Remove the failed unit. Refer to Section 6.1, Removing and Installing Optical Channel Units, of this practice.
Step 4 Disconnect the 78-Mb/s cable(s) by referring to the following documentation in the FLM 2400 ADM for cabling and slot information:
• FJTU-320-560-200, DLP-200-055 for linear systems
• FJTU-320-560-200, DLP-200-056 for terminal systems
• FJTU-320-560-200, DLP 200-057 for unidirectional path-switched ring (UPSR) systems.
Step 5 Install the HC6A-6ELx unit. Refer to Section 6.1, Removing and Installing Optical Channel Units, of this practice.
Page 6-108 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.29: Replacing HS Electrical Interface (HC6A-6EL1/-6EL2) Units in the FLM 600 ADM TRIB
Step 6 Is the FAIL/SVCE LED on the HC6A-6ELx unit lighted red?
Step 7 Is the LINE LED lighted red?
Step 8 Is the LINE LED lighted red?
If yes: If no:
Call 1-800-USE-FTAC for technical assistance.
Go to Step 7.
If yes: If no:
There is a cable failure. Go to Step 4; refer to the FLM 2400 ADM documentation that is mentioned to correct the cabling problem, then go to Step 8.
Go to Step 9.
If yes: If no:
Call 1-800-USE-FTAC for technical assistance. Go to Step 9.
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-109
6.29: Replacing HS Electrical Interface (HC6A-6EL1/-6EL2) Units in the FLM 600 ADM TRIB
Maintenance and Trouble ClearingFJTU-320-560-480
Step 9 If required, record the new unit serial number and issue level on a copy of the data record form in the Plug-In Unit Installation practice (FJTU-320-560-220), Appendix A, Data Record Forms. Complete other fault-reporting documentation as necessary.
Figure 6-67: HC6A-6EL1 Unit Front Panel and Side View
FAIL/SVCELINE
HC6A-6EL1
FC9616H6E1
d522
1.1
ATTENTION
PUSH THE LEVER OFUNIT LOWER PART TOREMOVE THE COAXUNIT AS SHOWN INTHE FIGURE
CN3
Page 6-110 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.29: Replacing HS Electrical Interface (HC6A-6EL1/-6EL2) Units in the FLM 600 ADM TRIB
You have completed this task.
Figure 6-68: HC6A-6EL2 Unit Front Panel and Side View
DN
522
2
CN 4
CN 3
FAIL/SVCELINE
HC6A-6EL2
FC9616H6E2
ATTENTION
PUSH THE LEVER OFUNIT LOWER PART TOREMOVE THE COAXUNIT AS SHOWN INTHE FIGURE
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-111
6.30: Replacing Electrical Channel (MC6A-D3/-D3A2/-STS1/-ST1E/-ST1P) Unit in the FLM 600 ADM TRIB
Maintenance and Trouble ClearingFJTU-320-560-480
6.30 Replacing Electrical Channel (MC6A-D3/-D3A2/-STS1/-ST1E/-ST1P) Unit in the FLM 600 ADM TRIB
CAUTION:
An electrostatic discharge (ESD) wrist strap with a minimum resistance of 1 megohm should be worn when handling FLM units to prevent possible damage to the units. Before using, check for opens, shorts, and minimum resistance value. If the strap does not pass these checks, it should not be used.
6.30.1 Procedure
Step 1 Get a replacement MC6A unit and inspect it for possible damage and debris. Verify that you have the correct STS-1 or DS-3 unit to use in the 600 ADM Tributary shelf.
Step 2 Remove the failed unit.
Step 3 Set all of the option switches to the same position as on the removed MC6A unit. Refer to the following figures:
• Figure 6-69 for view of the MC6A-D3 front panel and hardware option switch locations
• Figure 6-70 for view of the MC6A-D3A2 front panel and hardware option switch locations
• Figure 6-71 for view of the MC6A-STS1 front panel and hardware option switch locations
• Figure 6-72 for view of the MC6A-ST1E front panel and hardware option switch locations
• Figure 6-73 for view of the MC6A-ST1P front panel and hardware option switch locations.
Step 4 Install the new MC6A unit.
Page 6-112 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.30: Replacing Electrical Channel (MC6A-D3/-D3A2/-STS1/-ST1E/-ST1P) Unit in the FLM 600
ADM TRIB
Step 5 Is the FAIL/SVC LED green?
Step 6 Are the LINE LEDs off?
Step 7 Monitor the associated incoming DSX-3/STSX-1 signal at the DSX-3/STS-X-1 bay. Is the signal present at the bay?
Step 8 Monitor the incoming signal at the associated S IN CH 1-12 connectors (CN 14 through CN 25) on rear of the shelf. Is the signal good?
Step 9 Did the alarm clear?
If yes: If no:
Go to Step 6. Repeat Step 1 through Step 4 if this is the first time the unit has been replaced.If this is the second time the unit has been replaced, call Fujitsu for technical assistanceat 1-800-USE-FTAC (800-873-3822).
If yes: If no:
Go to Step 9. Go to Step 7.
If yes: If no:
Go to Step 8. The problem is not in the FLM 2400 equipment. Go to Step 11.
If yes: If no:
Repeat Steps 1 through 4 if this is the first time the unit has been replaced.
If this is the second time the unit has been replaced, call Fujitsu for technical assistanceat 1-800-USE-FTAC (800-873-3822).
Repair the wiring between the DSX3/STS-1 bay and the connector. Repeat Steps 6 through 8.
If yes: If no:
If local procedures allow, switch to the new unit to verify operation, then go to Step 11.
Call Fujitsu for technical assistance at 1-800-USE-FTAC (1-800-873-3822).
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-113
6.30: Replacing Electrical Channel (MC6A-D3/-D3A2/-STS1/-ST1E/-ST1P) Unit in the FLM 600 ADM TRIB
Maintenance and Trouble ClearingFJTU-320-560-480
Step 10 Press the alarm cutoff (ACO) button on the AW6A.
Note: Audible alarm is cleared and the ACO LED on the AW6A is lighted green.
Step 11 If required, record the new unit serial number and issue level on a copy of the data record form in the Plug-In Unit Installation practice (FJTU-320-560-220), Appendix A, Data Record Forms. Complete other fault-reporting documentation as necessary.
You have completed this task.
Page 6-114 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.30: Replacing Electrical Channel (MC6A-D3/-D3A2/-STS1/-ST1E/-ST1P) Unit in the FLM 600
ADM TRIB
Figure 6-69: MC6A-D3 Unit Front Panel and Hardware Option Locations
FC
9616
MD
31M
C6A
-D3
FAIL/SVCE
1
2
3
LINE
DN
593
5.1
CableLength(feet)
LBO-SETTING
0 - 100
100 - 225
225 - 325
325 - 450 THR THR
SET THR
THR SET
SET SET
1 2LBO
CH
1LB
OC
H2
LBO
CH
3
21
21
21
THR
SET
THR
SET
THR
SET
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-115
6.30: Replacing Electrical Channel (MC6A-D3/-D3A2/-STS1/-ST1E/-ST1P) Unit in the FLM 600 ADM TRIB
Maintenance and Trouble ClearingFJTU-320-560-480
Figure 6-70: MC6A-D3/D3A2 Unit Front Panel and Hardware Option Locations
FC9616MDA1
MC6A-D3A2
FAIL/SVCE
1
2
3
LINE
DN
593
7.1
CableLength(feet)
LBO-SETTING
0 - 100
100 - 225
225 - 325
325 - 450 THR THR
SET THR
THR SET
SET SET
1 2LBO
CH
1LB
OC
H2
LBO
CH
3
21
21
21
THR
SET
THR
SET
THR
SET
Page 6-116 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.30: Replacing Electrical Channel (MC6A-D3/-D3A2/-STS1/-ST1E/-ST1P) Unit in the FLM 600
ADM TRIB
TH
SE
TH
SE
TH
SE
Figure 6-71: MC6A-STS1 Unit Front Panel and Hardware Option Locations
FC
9616
MS
T1
MC
6A-S
TS
1
FAIL/SVCE
1
2
3
LINE
DN
593
9.1
CableLength(feet)
LBO-SETTING
0 - 100
100 - 225
225 - 325
325 - 450 THR THR
SET THR
THR SET
SET SET
1 2LBO
CH
1LB
OC
H2
LBO
CH
3
21
21
21
R
T
R
T
R
T
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-117
6.30: Replacing Electrical Channel (MC6A-D3/-D3A2/-STS1/-ST1E/-ST1P) Unit in the FLM 600 ADM TRIB
Maintenance and Trouble ClearingFJTU-320-560-480
Figure 6-72: MC6A-ST1E Unit Front Panel and Hardware Option Locations
FC
9616
ST
14M
C6A
-ST
1E
FAIL/SVCE
1
2
3
LINE
d734
4
CableLength(feet)
LBO-SETTING
0 - 100
100 - 225
225 - 325
325 - 450 THR THR
SET THR
THR SET
SET SET
1 2LBO
CH
1LB
OC
H2
LBO
CH
3
21
21
21
THR
SET
THR
SET
THR
SET
Page 6-118 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.30: Replacing Electrical Channel (MC6A-D3/-D3A2/-STS1/-ST1E/-ST1P) Unit in the FLM 600
ADM TRIB
Figure 6-73: MC6A-ST1P Unit Front Panel and Hardware Option Locations
FC
9616
ST
15M
C6A
-ST
1P
FAIL/SVCE
1
2
3
LINE
d734
5
CableLength(feet)
LBO-SETTING
0 - 100
100 - 225
225 - 325
325 - 450 THR THR
SET THR
THR SET
SET SET
1 2LBO
CH
1LB
OC
H2
LBO
CH
3
21
21
21
THR
SET
THR
SET
THR
SET
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-119
6.31: Replacing Timing Control Access (TCA/TCA-ENH) Unit in the FLM 600 ADM TRIB Shelf
Maintenance and Trouble ClearingFJTU-320-560-480
6.31 Replacing Timing Control Access (TCA/TCA-ENH) Unit in the FLM 600 ADM TRIB Shelf
CAUTION:
An electrostatic discharge (ESD) wrist strap with a minimum resistance of 1 megohm should be worn when handling FLM units to prevent possible damage to the units. Before using the strap, check for opens, shorts, and minimum resistance value. If the strap does not pass these checks, it should not be used.
6.31.1 Procedure
Step 1 Get a replacement TCA/TCA-ENH unit and inspect it for possible damage and debris. Verify that you have the correct TCA unit to use in the FLM 600 ADM Shelf.
Step 2 Remove the failed unit.
Step 3 Set all of the option switches to the same position as the removed TCA/TCA-ENH unit. Refer to the following figures:
• Figure 6-74 for a view of the TCA front panel and hardware option switch locations
• Figure 6-75 for a view of the TCA-ENH front panel and hardware option switch locations.
Step 4 Install the new TCA/TCA-ENH unit.
Step 5 Is the FAIL/SVCE LED green?
If yes: If no:
Go to Step 6. Repeat Steps 1 through 5 if this is the first time the unit has been replaced.If this is the second time the unit has been replaced, call Fujitsu for technical assistance at 1-800-USE-FTAC (800-873-3822).
Page 6-120 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.31: Replacing Timing Control Access (TCA/TCA-ENH) Unit in the FLM 600 ADM TRIB Shelf
Step 6 Is the LINE LED off?
Step 7 Monitor the BITS clock signal at the DSX. Is the signal good?
Step 8 Monitor the BITS clock signal at the inputs to the FLM 600 ADM TRIB shelf (CN 11 and CN 12). Is the signal good?
Step 9 Did the alarm clear?
Step 10 If required, record the new unit serial number and issue level on a copy of the data record form in the Plug-In Unit Installation practice (FJTU-320-560-220), Appendix A, Data Record Forms. Complete other fault-reporting documentation as necessary.
You have completed this task.
If yes: If no:
Go to Step 9. Go to Step 7.
If yes: If no:
Go to Step 8. The problem is not in the FLM 2400 ADM equipment. Go to Step 10.
If yes: If no:
Repeat Steps 1 through 5 if this is the first time the unit has been replaced.If this is the second time the unit has been replaced, call Fujitsu for technical assistance at 1-800-USE-FTAC (800-873-3822).
Repair the wiring between the DSX and the FLM 600 ADM TRIB shelf and repeat Steps 6 through 8.
If yes: If no:
If local procedures allow, switch to the new unit to verify operation, then go to Step 10.
Call Fujitsu for technical assistance at 1-800-USE -FTAC (1-800-873-3822).
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-121
6.31: Replacing Timing Control Access (TCA/TCA-ENH) Unit in the FLM 600 ADM TRIB Shelf
Maintenance and Trouble ClearingFJTU-320-560-480
Figure 6-74: TCA Unit Front Panel and Hardware Option LocationsT
CA
FC9616MS61
FAIL/SVCELINE
d239
5.5
LBOSET
12
34
5
OO
F A
LMA
CT
VT
INH
B
LBO- SETTINGSCABLE
LENGTH 1 2 3 4 5
0 - 250 FT
250 - 500 FT
500-750 FT
ON
OFF
OFF
ON
OFF
OFF
OFF
ON
OFF
OFF
ON
OFF
OFF
OFF
ON
12
OP
EN
OP
EN
Note: This table is on the back of the unit.(Where: OFF = OPEN)
Page 6-122 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.31: Replacing Timing Control Access (TCA/TCA-ENH) Unit in the FLM 600 ADM TRIB Shelf
Figure 6-75: TCA-ENH Unit Front-Panel Option and Hardware Option Locations
d691
1
LBOSET
12
34
5 LBO SETTINGSCable Length
(ft) 1 2 3 4 5
0–250 FT
250–500 FT
500–750 FT
ON
OFF
OFF
ON
OFF
OFF
OFF
ON
OFF
OFF
ON
OFF
OFF
OFF
ON
OP
EN
ON OFF
FC9616TCE1
FAIL/SVCELINE
TCA-ENH
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-123
6.32: Replacing Embedded Channel (EC6A-24G/ -DL1) Unit in the FLM 600 ADM TRIB Shelf
Maintenance and Trouble ClearingFJTU-320-560-480
6.32 Replacing Embedded Channel (EC6A-24G/ -DL1) Unit in the FLM 600 ADM TRIB Shelf
CAUTION:
An electrostatic discharge (ESD) wrist strap with a minimum resistance of 1 megohm should be worn when handling FLM units to prevent possible damage to the units. Before using the strap, check for opens, shorts, and minimum resistance value. If the strap does not pass these checks, it should not be used.
6.32.1 Procedure
Step 1 Get a replacement EC6A-24G or EC6A-DL1 unit and inspect it for possible damage and debris. Verify that you have the correct EC6A unit to use in the FLM 600 ADM Shelf. Refer to Figure 6-76 for a view of the EC6A-24G front panel. See Figure 6-77 for a view of the front panel and option switches for the EC6A-DL1 unit.
Step 2 Remove the failed unit.
Step 3 For the EC6A-DL1 unit, set the option switches to the same positions as on the removed unit. Refer to Figure 6-77 for a view of option switches.
Step 4 Install the new EC6A-24G or EC6A-DL1 unit. For the EC6A-DL1 unit, wait 5 minutes for a reset to occur after installation.
Step 5 (For the EC6A-DL1, wait 5 minutes for a reset to occur after installation.) Is the FAIL LED off?
If yes: If no:
Go to Step 6. Repeat Steps 1 through 5 if this is the first time the unit has been replaced.
If this is the second time the unit has been replaced, call Fujitsu for technical assistance at 1-800-USE-FTAC (800-873-3822).
Page 6-124 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
6.32: Replacing Embedded Channel (EC6A-24G/ -DL1) Unit in the FLM 600 ADM TRIB Shelf
Step 6 Is the LINE LED off?
Step 7 Is section data communications channel (SDCC) required?
Step 8 After the provisioning is complete, is the LINE LED off?
Step 9 Verify that the far-end equipment SDCC is In Service.
Step 10 Is the LINE LED off?
Step 11 Did the alarm clear?
If yes: If no:
If local procedures allow, switch to the new unit to verify operation, then go to Step 12
Go to Step 7.
If yes: If no:
Go to Step 9. Provision SDCC to out-of-service (OOS).
If yes: If no:
If local procedures allow, switch to the new unit to verify operation, then go to Step 12
Call Fujitsu for technical assistance at 1-800-USE-FTAC (800-873-3822).
If yes: If no:
Go to Step 11. Repeat Steps 1 through 5, if this is the first time the unit has been replaced.
If this is the second time the unit has been replaced, call Fujitsu for technical assistance at1-800-USE-FTAC (800-873-3822).
If yes: If no:
If local procedures allow, switch to the new unit to verify operation, then go to Step 12
Call Fujitsu for technical assistance at 1-800-USE -FTAC (1-800-873-3822).
Issue 7, May 1999 FNC and FNC Customer Use Only Page 6-125
6.32: Replacing Embedded Channel (EC6A-24G/ -DL1) Unit in the FLM 600 ADM TRIB Shelf
Maintenance and Trouble ClearingFJTU-320-560-480
Step 12 If required, record the new unit serial number and issue level on a copy of the data record form in the Plug-In Unit Installation practice (FJTU-320-560-220), Appendix A, Data Record Forms. Complete other fault-reporting documentation as necessary.
You have completed this task.
Figure 6-76: EC6A-24G Unit Front Panel
Figure 6-77: EC6A-DL1 Front Panel and Option Switches
EC
6A
FC9616EC61
FAIL
d599
4
LINE
600 600TRIB
600600TRIB
EC
6A-D
L1
FC9616ECD1
FAIL
LINE
DN
594
7
Page 6-126 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
Chapter 7: General Procedures
CHAPTER 7
7 General Procedures
7.1 Handling the Fiber Cables Correctly
7.1.1 Summary
This procedure lists precautionary measures that must be followed when dealing with optical fibers and optical components.
DANGER:
This equipment contains a high-powered optical laser device that operates at an extremely high transmission rate. NEVER look into the end of a fiber cord, fiber pigtail, or a fiber. Permanent eye damage or blindness can occur very quickly if the laser light is present. The label shown in Figure 7-1 is attached to laser-emitting devices as a reminder.
DANGER:
NEVER handle exposed fiber with bare hands or touch it to your body. Follow local safety precautions regarding fiber. A fiber fragment could enter the skin and be very difficult to detect and remove.
Figure 7-1: Laser Radiation Caution Mark
danger
Invisible laserradiation from
connectorswhen
uncoupledAVOID DIRECT
EXPOSURETO BEAM
Issue 7, May 1999 FNC and FNC Customer Use Only Page 7-1
7.1: Handling the Fiber Cables Correctly Maintenance and Trouble ClearingFJTU-320-560-480
7.1.2 Procedure
Storage
Observe the following admonishments.
WARNING:
All optical connectors are shipped with covers installed. If covers are always used when fibers are not connected, and protective covers are always stored in a clean container, then the need for cleaning can be minimized.
Improper cleaning can contaminate a connector that is not contaminated. Common contaminants in dust are microscopic particles of carbon and silicon. These particles are very hard and can crush optical fiber. A connector contaminated with microscopic silicon or carbon particles can destroy multiple connectors by crushing the fiber. For example: If a fiber optic cable connector is contaminated with microscopic carbon or silicon particles, several module connectors could be crushed by the contaminates connector. The modules would have to be returned for repair (replacement of the optical pigtail.)
WARNING:
Protective caps are provided with the optical connectors of the fiber-optic cable (Figure 7-2). When fiber-optic cables are not used for a long period, put the protective caps back on the optical connectors and seal the fiber-optic cables in a vinyl bag.
When a fiber-optic cable is disconnected, install a protective cap on both the cable connector and the equipment connector unless the connector will be reconnected in the following step.
Figure 7-2: Protective Cap
PROTECTIVECAP
OD
2-00
21-9
3
Page 7-2 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
7.1: Handling the Fiber Cables Correctly
WARNING:
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%.
Handling
Observe the following admonishments.
WARNING:
Do not drop or subject the fiber connector and fiber-optic cable to excessive vibration. Never apply excessive force to the connector by pulling, bending, or twisting the cord when the coupling nut is tightened (Figure 7-3).
WARNING:
Do not pull the fiber-optic cable in the direction indicated in Figure 7-4 when the connector is attached to an optical plug-in unit or an optical adapter of the lightwave distribution frame (LDF).
WARNING:
Be careful not to create sharp bends in the fiber-optic cable. (Figure 7-5). This may occur in attempting to route the fiber-optic cable around an obstruction. Remove the obstruction or find a different route for the fiber-optic cable.
Figure 7-3: Tension Limit
CONNECTORTENSILE STRENGTH:10 kg (22 lbs.) OR LESS
OPTICAL FIBER CORDTENSILE STRENGTH:20 kg (44 lbs.) OR LESS
OD
2-00
22-9
3
Issue 7, May 1999 FNC and FNC Customer Use Only Page 7-3
7.1: Handling the Fiber Cables Correctly Maintenance and Trouble ClearingFJTU-320-560-480
WARNING:
Do not bend the fiber-optic cable to a radius of less than 50 mm (Figure 7-6).
WARNING:
Do not twist the fiber-optic cable more than 360 degrees per meter of length (Figure 7-7).
WARNING:
Do not step on the connector or fiber-optic cable (Figure 7-8).
Figure 7-4: Fiber Cord Pulling
Figure 7-5: Fiber Cord Bending and Obstruction
OD
2-00
23-9
3O
D2-
0024
-93
Page 7-4 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
7.1: Handling the Fiber Cables Correctly
Figure 7-6: Fiber Cord Minimum Bending Radius
Figure 7-7: Twisting the Fiber Cord
R 50 mm(2 in.)
OD
2-00
25-9
3
OD
2-00
26-9
3
Issue 7, May 1999 FNC and FNC Customer Use Only Page 7-5
7.1: Handling the Fiber Cables Correctly Maintenance and Trouble ClearingFJTU-320-560-480
Figure 7-8: Fiber Cord Vibration and Shock Damage
OD
2-00
27-9
3
Page 7-6 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
7.2: Cleaning the Optical Connectors
7.2 Cleaning the Optical Connectors
7.2.1 Summary
This procedure discusses the steps for cleaning optical fiber cables and connectors.
Tools Required
• Pure alcohol (more than 95 percent purity)
• Compressor-supplied air or a can of compressed gas with a nozzle (as defined by local procedures)
• Lint-free cotton swabs (designed for cleaning optical connectors)
Note: Clean the fiber cord end surface when using the connector for first time. Also, clean the surface when it is dirty, or approximately every 100 disconnections.
DANGER:
This equipment contains high-power optical laser devices that operate at an extremely high transmission rate. Follow local safety precautions regarding fiber-optic cables. Never look into the end of a fiber-optic cable. Permanent eye damage or blindness can occur very quickly if the laser light is present.
DANGER:
Never handle exposed fiber with bare hands or touch it to your body. Follow local safety precautions regarding fiber. A fiber fragment could enter the skin and be very difficult to detect and remove.
Issue 7, May 1999 FNC and FNC Customer Use Only Page 7-7
7.2: Cleaning the Optical Connectors Maintenance and Trouble ClearingFJTU-320-560-480
WARNING:
All optical connectors are shipped with covers installed. If covers are always used when fibers are not connected, and protective covers are always stored in a clean container, then the need for cleaning can be minimized.
Improper cleaning can contaminate a connector that is not contaminated. Common contaminants in dust are microscopic particles of carbon and silicon. These particles are very hard and can crush optical fiber. A connector contaminated with microscopic silicon or carbon particles can destroy multiple connectors by crushing the fiber. For example: If a fiber optic cable connector is contaminated with microscopic carbon or silicon particles, several module connectors could be crushed by the contaminates connector. The modules would have to be returned for repair (replacement of the optical pigtail.)
7.2.2 Procedure
WARNING:
Use only alcohol with a purity of more than 95 percent to clean optical connectors. Many store-bought alcohols are mixtures of less than 95 percent purity and can seriously contaminate connectors. Do not leave containers of alcohol open because they can quickly absorb water vapor from the air. If alcohol with a purity of less than 95 percent is used, a thin film of water can be left on the connector, thus causing the connector to have a high loss and an unacceptable dispersion.
Use only the compressed gas systems specified in the local procedures when using a blower to clean or dry connectors.
Use only lint-free swabs specially designed for cleaning optical connectors. Never use ordinary cotton swabs because lint from these swabs will contaminate the connector.
Step 1 Read the general information for fiber-optic cable handling (refer to Section 7.1, Handling the Fiber Cables Correctly).
Step 2 Wipe the fiber-end surface with a cotton swab soaked in alcohol (Figure 7-9).
Step 3 After cleaning, use a blower to remove any remaining alcohol (Figure 7-10).
You have completed this task.
Page 7-8 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
7.2: Cleaning the Optical Connectors
Figure 7-9: Cleaning the Fiber-End Surface
Figure 7-10: Blower Cleaning
COTTON SWAB
FIBER END SURFACEOPTICAL FIBER CONNECTOR
o200
30.2
AIR NOZZLE o200
31.2
Issue 7, May 1999 FNC and FNC Customer Use Only Page 7-9
7.3: Connect/Disconnect Optical Cables Maintenance and Trouble ClearingFJTU-320-560-480
7.3 Connect/Disconnect Optical Cables
7.3.1 Summary
This procedure discusses the precautions that must be taken to preserve the integrity of optical connectors and cables during connection and disconnection. Separate procedures are provided for the following connector types:
• FC and ST
• SC
DANGER:
This equipment contains high-power optical laser devices that operate at an extremely high transmission rate. Follow local safety precautions regarding fiber-optic cables. Never look into the end of a fiber-optic cable. Permanent eye damage or blindness can occur very quickly if the laser light is present.
DANGER:
Never handle exposed fiber with bare hands or touch it to your body. Follow local safety precautions regarding fiber. A fiber fragment could enter the skin and be very difficult to detect and remove.
WARNING:
All optical connectors are shipped with covers installed. If covers are always used when fibers are not connected, and protective covers are always stored in a clean container, then the need for cleaning can be minimized.
Improper cleaning can contaminate a connector that is not contaminated. Common contaminants in dust are microscopic particles of carbon and silicon. These particles are very hard and can crush optical fiber. A connector contaminated with microscopic silicon or carbon particles can destroy multiple connectors by crushing the fiber. For example: If a fiber optic cable connector is contaminated with microscopic carbon or silicon particles, several module connectors could be crushed by the contaminates connector. The modules would have to be returned for repair (replacement of the optical pigtail.)
Page 7-10 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
7.3: Connect/Disconnect Optical Cables
WARNING:
Use only alcohol with a purity of more than 95 percent to clean optical connectors. Many store-bought alcohols are mixtures of less than 95 percent purity and can seriously contaminate connectors. Do not leave containers of alcohol open because they can quickly absorb water vapor from the air. If alcohol with a purity of less than 95 percent is used, a thin film of water can be left on the connector, thus causing the connector to have a high loss and an unacceptable dispersion.
Use only the compressed gas systems specified in the local procedures when using a blower to clean or dry connectors.
Use only lint-free swabs specially designed for cleaning optical connectors. Never use ordinary cotton swabs because lint from these swabs will contaminate the connector.
7.3.2 FC and ST Connector Procedures
Preparation
Step 1 If necessary, remove the protective cover from the connector.
Step 2 Verify that there are no serious defects in the fiber-optic cables and connectors.
Step 3 Clean the fiber-end surface with a cotton swab soaked in alcohol (refer to Section 7.2, Cleaning the Optical Connectors).
You have completed this task.
Connection Procedure
Step 1 While holding the connector body, insert the connector in the axial direction over the receptacle of the optical connector located on the plug-in unit, adapter, distribution frame, or attenuator. (See Figure 7-11.)
Note: For slotted connector types, make sure the tab on the connector is lined up with the slot on the receptacle.
Issue 7, May 1999 FNC and FNC Customer Use Only Page 7-11
7.3: Connect/Disconnect Optical Cables Maintenance and Trouble ClearingFJTU-320-560-480
Step 2 After insertion, tighten the coupling nut until it is “finger tight.” Do not turn the connector body or twist the fiber-optic cable. (Figure 7-11.)
You have completed this task.
Disconnect Procedure
Step 1 Loosen the coupling nut completely (Figure 7-12). Do not allow the fiber-optic cable to be twisted.
Step 2 Pull the connector body in the axial direction. Do not pull or bend the fiber-optic cable (Figure 7-12).
Step 3 Put a protective cap on the connector.
You have completed this task.
Figure 7-11: Insertion Method (FC Connector Shown)
Figure 7-12: Disconnection Method (FC Connector Shown)
o200
28.2
CW
OPTICAL FIBERCORD
COUPLING NUTCONNECTOR BODY
CCW
o200
29.2
OPTICAL FIBERCORD
COUPLING NUTCONNECTOR BODY
Page 7-12 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
7.3: Connect/Disconnect Optical Cables
7.3.3 SC Connector Procedures
The SC connectors are available in both single and double configurations.
Preparation
Step 1 Remove the protective cover from the connector.
Step 2 Verify that there are no serious defects in the fiber-optic cables and connectors.
Step 3 Clean the fiber-end surface(s) with a cotton swab soaked in alcohol (refer to Section 7.2, Cleaning the Optical Connectors).
You have completed this task.
Connection Procedure
Step 1 While holding the connector body, insert the connector in the axial direction into the receptacle of the optical connector located on the plug-in unit, adapter, distribution frame, or attenuator. Make sure the tab on the connector is lined up with the notch on the receptacle. (See Figure 7-13.)
Step 2 Press the connector into the receptacle until a positive snap-fit connection is made. Do not turn the connector body or twist the fiber-optic cable.
You have completed this task.
Figure 7-13: Insertion Method for SC Connectors
d724
9
Issue 7, May 1999 FNC and FNC Customer Use Only Page 7-13
7.3: Connect/Disconnect Optical Cables Maintenance and Trouble ClearingFJTU-320-560-480
Disconnect Procedure
Step 1 Grasp the connector body and pull the connector straight out of the receptacle until the snap-fit connection is released. Do not pull on the fiber and do not allow the fiber-optic cable to be twisted. (See Figure 7-14.)
Step 2 Put a protective cap on the connector.
You have completed this task.
Figure 7-14: Disconnection Method for SC Connectors
d724
8
Page 7-14 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
7.4: Measuring the Optical Transmit Unit OutputPower
7.4 Measuring the Optical Transmit Unit Output Power
7.4.1 Summary
This procedure lists the steps required to measure the optical output power of the units in the FLM 2400 ADM. The channel to be measured must not be actively carrying traffic when this procedure is started. When the measurements are finished, record them in the data record shown in the Application Engineering practice, FJTU-320-560-220, Appendix A, and save them for later use.
DANGER:
This equipment contains high-power optical laser devices that operate at an extremely high transmission rate. Follow local safety precautions regarding fiber-optic cables. Never look into the end of a fiber-optic cable. Permanent eye damage or blindness can occur very quickly if laser light is present.
DANGER:
Never handle exposed fiber with bare hands or touch it to your body. Follow local safety precautions regarding fiber. A fiber fragment could enter the skin and be very difficult to detect and remove.
CAUTION:
Unplugging one of these units may be traffic-affecting. Please make sure traffic is not dependent on the unit before unplugging it.
CAUTION:
Since optical connector performance is affected by dust, all connectors should be cleaned before performing measurements. Keep the ends of fiber-optic cables covered when the cables are not in use. Refer to Sections 7.1, 7.2, and 7.3 for information on fiber handling and cleaning.
WARNING:
To avoid damage to a fiber cord or fiber pigtail, read Section 7.1, Handling the Fiber Cables Correctly, and Section 7.3, Connect/Disconnect Optical Cables, for connection and disconnection procedures.
Issue 7, May 1999 FNC and FNC Customer Use Only Page 7-15
7.4: Measuring the Optical Transmit Unit Output Power
Maintenance and Trouble ClearingFJTU-320-560-480
Test Equipment Required
• Optical power meter with sensor
• Ando AQ-1135E/AQ-1965 or its equivalent
• Optical fiber test cord (Fujitsu H660-5381-U920, SM, PC/PC)
7.4.2 Procedure
Step 1 Disconnect the optical fiber cord from the optical output of the unit (Section 7.3, Connect/Disconnect Optical Cables). Attach a protective cap to the optical fiber cord. If no fiber cord is connected, remove the protective cap from the optical unit. Keep the protective cap in a storage box on a shelf for future use.
Step 2 Clean the optical connector on the optical output of the unit (Section 7.2).
Step 3 Set up the optical power meter as shown in Figure 7-15. Set the meter to read approximately 0 dBm.
Figure 7-15: FLM 2400 ADM Optical Output Power Measurement
HM
2H-X
X
OPTICAL POWER METER
OPTICAL SENSORC
Q4-
0043
HM
2H-X
X
HT2H-XXXX
HR
2H-X
XX
X
Page 7-16 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
7.4: Measuring the Optical Transmit Unit OutputPower
Step 4 Connect one end of the optical fiber test cord to the optical output connector of the unit and the other end to the sensor used with the optical power meter (Figure 7-15).
Step 5 Record the optical power meter reading. The requirements are shown in Table 7-1.
Step 6 If the output optical power requirement is not met, perform the following substeps, one at a time, until the output power requirements are met.
a. Clean the optical connectors on the unit under test, the fiber-optic cable, and the test equipment. Repeat Steps 2 and 3.
b. Replace the fiber-optic cable and repeat Steps 2, 3, and 4.
c. Replace the optical unit and repeat Steps 2, 3, and 4.
d. Replace the optical power meter and repeat Steps 2, 3, and 4.
e. Replace the optical unit.
Step 7 Disconnect fiber-optic test cable from optical output of the unit (Section 7.3).
Table 7-1: Optical Power Meter Reading
Unit Minimum Maximum Measured
HT2H-LR1x –0.6 dBm +6.0 dBm
HT2H-LR2x –2.6 dBm +4.0 dBm
HC6A-xxxx –3.0 dBm +2.0 dBm
MC6A-31Mx –15.0 dBm –8.0 dBm
MC6A-3Mxx –15.0 dBm –8.0 dBm
MC6A-31Lx –5.0 dBm 0.0 dBm
MC6A-3Lxx –5.0 dBm 0.0 dBm
MC6A-31Sx –15.0 dBm –8.0 dBm
MC6A-3Sxx –15.0 dBm –8.0 dBm
Issue 7, May 1999 FNC and FNC Customer Use Only Page 7-17
7.4: Measuring the Optical Transmit Unit Output Power
Maintenance and Trouble ClearingFJTU-320-560-480
Step 8 Reconnect fiber-optic cable (part of optical transmission line) and reinstall the unit.
You have completed this task.
Page 7-18 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
7.5: Measuring the Optical Receive Unit InputPower
7.5 Measuring the Optical Receive Unit Input Power
7.5.1 Summary
This procedure lists the steps required to measure the optical input power. These steps can be followed for each optical channel after the optical unit has been checked for correct optical output by following the procedure described in Section 7.4, Measuring the Optical Transmit Unit Output Power. The channel to be measured must not be actively carrying traffic when this procedure is started. When the measurements are finished, record them in the data record shown in the Application Engineering practice, FJTU-320-560-220, Appendix A, and save for later use.
DANGER:
This equipment contains high-power optical laser devices that operate at an extremely high transmission rate. Follow local safety precautions regarding fiber-optic cables. Never look into the end of a fiber-optic cable. Permanent eye damage or blindness can occur very quickly if the laser light is present.
WARNING:
To avoid damage to a fiber cord or fiber pigtail, read Section 7.1, Handling the Fiber Cables Correctly, and Section 7.3, Connect/Disconnect Optical Cables, for connection and disconnection procedures.
Note: Because optical connector performance is affected by dust, all connectors should be cleaned as described in Section 7.2, Cleaning the Optical Connectors, before taking measurements.
Test Equipment Required
• Optical power meter with sensor
• Ando AQ-1135E/AQ-1965 or its equivalent
7.5.2 Procedure
Step 1 Have the optical cables been completely connected per Section 7.3?
If yes: If no:
Go to Step 2. Go to Step 3.
Issue 7, May 1999 FNC and FNC Customer Use Only Page 7-19
7.5: Measuring the Optical Receive Unit Input Power
Maintenance and Trouble ClearingFJTU-320-560-480
Step 2 Release the top and bottom latches and slide the optical unit out until it reaches the secondary latch. Disconnect the optical fiber cord from the unit (Section 7.3). Put a protective cap on the optical unit during measurement.
Step 3 Clean the end surface of the optical fiber cord (Section 7.2).
Step 4 Set up the optical power meter to read in the –10 to –30 dBm range. See Figure 7-16.
Step 5 Connect the end of the optical fiber cord to the optical sensor (Figure 7-16).
Step 6 Ensure that the optical unit at the distant end is connected to the transmission line and transmitting an optical signal. Record the optical power meter reading. Refer to Table 7-2 for minimum and maximum values for optical signals.
Figure 7-16: FLM 2400 ADM Optical Input Power Measurement
HM
2H-X
X
HT
2H-X
XX
X
HM
2H-X
X
OPTICAL POWER METER
OPTICAL SENSOR
CQ
4-00
44
HR2H-XXXX
HT
2H-X
XX
X
R IN OPTICAL LINE
Page 7-20 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
7.5: Measuring the Optical Receive Unit InputPower
Step 7 If the optical input power exceeds the maximum requirement (where –10 dBm is more than –11 dBm), insert a fixed attenuator between the LDF and the optical fiber input cord. Select the amount of attenuation so that the input power is between the required maximum and minimum values. The suggested fixed optical attenuators are as follows:
• 10-dB attenuator: H72M-2032-L002
• 15-dB attenuator: H722M-2032-L004.
Step 8 If the optical input power is less than the required minimum value (where –30 dBm is less than –27 dBm), perform the following substeps one at a time until required input power is measured.
a. Clean the optical connectors on both the fiber cord and the test equipment. Repeat Steps 5 and 6.
b. Remove any attenuators between the remote transmitter and the fiber jumper at the receiver.
c. Using a known good test fiber cord, measure the optical power at the corresponding LDF connector. If the level is at least one dB higher than the minimum required at the optical unit input, clean both ends of the fiber between the LDF and the optical unit. If this does not solve the problem, replace the fiber.
Table 7-2: Minimum and Maximum Values for Optical Signals
Unit Minimum Maximum Measured
HR2H-LR1x: –27.0 dBm –13.0 dBm
HR2H-LR2x: –27.8 dBm –13.0 dBm
HR2H-LR1B –25.6 dBm –11.0 dBm
HR2H-LR2B –25.6 dBm –11.0 dBm
HC6A-xxxx –28.0 dBm –8.0 dBm
MC6A-31Mx –28.0 dBm –8.0 dBm
MC6A-3Mxx –34.0 dBm –10.0 dBm
MC6A-31Lx –34.0 dBm –10.0 dBm
MC6A-3Lxx –34.0 dBm –10.0 dBm
MC6A-31Sx –23.0 dBm –8.0 dBm
MC6A-3Sxx –23.0 dBm –8.0 dBm
Issue 7, May 1999 FNC and FNC Customer Use Only Page 7-21
7.5: Measuring the Optical Receive Unit Input Power
Maintenance and Trouble ClearingFJTU-320-560-480
d. Test, or replace if required, the optical unit at the opposite terminal. Repeat Steps 5 and 6.
e. Ensure that the span loss budget is within specifications.
Step 9 When the power reading is correct, disconnect optical power meter and reconnect the optical fiber cord to optical unit (Section 7.3).
Step 10 Carefully reseat the optical unit.
You have completed this task.
Page 7-22 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
7.6: Verifying the External Clock andConnections
7.6 Verifying the External Clock and Connections
7.6.1 Summary
This procedure gives the steps required to check the external clock connections and to verify the external clock signal source for the FLM 2400 ADM. Table 7-3 describes the connectors.
7.6.2 Procedure
Step 1 If an external clock source is being used, verify that the D-Sub connectors are terminated on the appropriate primary and secondary clock cables. Refer to Figure 7-17 for the external clock (primary) connector pinout, and Figure 7-18 for the external clock (secondary) connector pinout.
Step 2 Connect the cables to the EXT CLK PRIM (CN1) and EXT CLK SECOND (CN2) respectively.
Step 3 To retrieve any existing external clock source alarms, refer to one of the following practices:
• Using TL1 commands, refer to the TL1 Commands practice FJTU-320-560-274, Section 21, and check for any alarms on the clock source.
• For the FLEXR® flexible user interface software alarm retrieval, refer to FLEXR, FJTU-320-900-FLX, Section 6, and check for any alarms on the clock source.
You have completed this task.
Table 7-3: Connectors for External Clock Cables
Connector External Clocks Function Connector Type
CN1 Primary Input of primary external clock
Output of reference clock
D-Sub 9-pin
CN2 Secondary Input of secondary external clock
Output of reference clock
D-Sub 9-pin
Issue 7, May 1999 FNC and FNC Customer Use Only Page 7-23
7.6: Verifying the External Clock and Connections
Maintenance and Trouble ClearingFJTU-320-560-480
Figure 7-17: External Clock (Primary) Connector Pinout
Figure 7-18: External Clock (Secondary) Connector Pinout
9
5
8
4
7
3
6
2
1
DS1 IN (T)
DS1 IN (R)
NC
NC
DS1 OUT (T)
DS1 OUT (R)
SG
NC
FG
CN1
P
P
o408
8.3
61
5
FG
NCNC
NC
9 DS1 IN (T)
DS1 OUT (T)
SG
DS1 IN (R)
DS1 OUT (R)
CN1
9
5
8
4
7
3
6
2
1
DS1 IN (T)
DS1 IN (R)
NC
NC
SG
NC
FG
CN2
P
P
o400
89.3
61
5
FG
NCNC
NC
9 DS1 IN (T)
DS1 OUT (T)
SG
DS1 IN (R)
DS1 OUT (R)
CN2
DS1 OUT (R)
DS1 OUT (T)
Page 7-24 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
7.7: Verifying the T3 Framing
7.7 Verifying the T3 Framing
7.7.1 Summary
This procedure describes how to verify the framing on a T3 carrier and, if necessary, change the format. Before performing this procedure, use local procedures/documents to determine the appropriate provisioning for this facility.
CAUTION:
Verify that you have received a completed (COMPLD) response to each command before going to the next step.
7.7.2 Procedure
Step 1 Retrieve the current framing parameter:
Step 2 Examine the response for FMT: T3=ASYNC or UNFR.
Step 3 If the framing is incorrect, edit the parameter:
You have completed this task.
TL1 FLEXR 7.61
RTRV-T3:TID:AID:CTAG; > Provisioning
> Facility
> Set Facility
Select the unit
Click on Retrieve
TL1 FLEXR 7.61
ED-T3:TID:AID:CTAG:::KEYWORD=DOMAIN;
KEYWORD = DOMAIN
FMT = ASYNC /UNFR
Default shown in bold)
Select the parameters
Click on OK
Issue 7, May 1999 FNC and FNC Customer Use Only Page 7-25
7.8: Changing Unidirectional/Bidirectional Switching
Maintenance and Trouble ClearingFJTU-320-560-480
7.8 Changing Unidirectional/Bidirectional Switching
7.8.1 Summary
This procedure describes how to retrieve and edit the current protection switching settings for a fiber-optic group. Before performing this procedure, use local procedures/documents to determine the appropriate provisioning for this facility protection group.
CAUTION:
Verify that you have received a completed (COMPLD) response to each command before going to the next step.
7.8.2 Summary
Step 1 Retrieve the current protection switch setting:
Step 2 Check the response for the current switch setup.
TL1 FLEXR 7.61
RTRV-FFP-OC48:TID:AID:CTAG;
RTRV-FFP-OC12:TID:AID:CTAG;
RTRV-FFP-OC3:TID:AID:CTAG;
> Provisioning
> System
> Set switch Lock-In
> Retrieve
Page 7-26 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
7.8: Changing Unidirectional/BidirectionalSwitching
Step 3 If the UNI/BI direction does not match the far end, change to make it consistent with the correct provisioning for this facility:
Note: Neither unidirectional nor bidirectional line switching is done for OC-48 signals in the path-switched ring (2400PSR) or regenerator (2400REG) applications.
You have completed this task.
TL1 FLEXR 7.61
ED-FFP-OC48:TID:AID:CTAG:::KEYWORD=DOMAIN;
ED-FFP-OC12:TID:AID:CTAG:::KEYWORD=DOMAIN;
ED-FFP-OC3:TID:AID:CTAG:::KEYWORD=DOMAIN;
KEYWORD = DOMAIN
DIRN = BI/UNI
(Default shown in bold)
> Provisioning
> System
> Set switch Lock-In
Issue 7, May 1999 FNC and FNC Customer Use Only Page 7-27
7.9: Changing the SDCC Service State Maintenance and Trouble ClearingFJTU-320-560-480
7.9 Changing the SDCC Service State
7.9.1 Summary
This procedure changes the section data communications channel (SDCC) service state. Note that the command only provisions the channel. The INIT-SDCC command is required to activate any changes. If the turn-up procedures are followed, as documented in the Turn-Up and Operation practice, FJTU-320-560-270, the SDCCs should automatically be placed In Service correctly for most applications.
For example, when turning up a 1+1 point-to-point system with no Regenerator sites, one SDCC is automatically provided over the working OC-48 facility. This SDCC switches with the OC-48 line. If the point-to-point terminals are provisioned to use a Regenerator between terminals, two SDCC channels are provided over the OC-48 facilities to provide SDCC connectivity to the Regenerator site(s).
CAUTION:
Verify that you have received a completed (COMPLD) response to each command before going to the next step.
7.9.2 Procedure
Step 1 Retrieve the current status of the channel:
Step 2 If the channel is not in the desired service state, go to Step 3. Otherwise, stop.
TL1 FLEXR 7.61
RTRV-SDCC:TID:AID:CTAG;
AID=1,2,3/4/5/6 - 1/2/3/4
> Provisioning
> Section DCC
> SDCC Service State
Select AID
Retrieve
Page 7-28 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
7.9: Changing the SDCC Service State
Step 3 Enter the desired SDCC service state:
Step 4 Activate the SDCC state changes.
You have completed this task.
TL1 FLEXR 7.61
ED-SDCC:TID:AID:CTAG::::PST;
Enter the required parameters.
PST: IS/OOS
where:
IS—In Service
OOS—Out of Service
Select the parameters:
AIDs Service State
OK
TL1 FLEXR 7.61
INIT-SDCC:TID:AID:CTAG; Initialize.
Issue 7, May 1999 FNC and FNC Customer Use Only Page 7-29
7.10: Removing and Installing Front Covers on the HS and HD TRIB Shelves
Maintenance and Trouble ClearingFJTU-320-560-480
7.10 Removing and Installing Front Covers on the HS and HD TRIB Shelves
7.10.1 Summary
This procedure describes the steps to remove and install electromagnetic interference (EMI) protective covers on the HS and HD TRIB. To remove and install the protective cover and heat shield on the 600 TRIB shelf, refer to the FLM 600 ADM documentation set.
CAUTION:
To prevent possible damage to the units, an electrostatic discharge (ESD) wrist strap with a minimum resistance of 1 megohm should be worn when handling FLM units. Before using the strap, check for opens, shorts, and minimum resistance value. If the strap does not pass these checks, it should not be used.
7.10.2 Procedure
Removing the Shelf Cover
Step 1 Grasp the shelf cover with both hands. Be sure your thumbs are on the front of the shelf cover and your middle fingers are on the side release buttons. Refer to Figure 7-19.
Step 2 Push on the heat shield cover with your thumbs while simultaneously pressing the release buttons on the side of the cover. You should hear a click and feel the side latches release.
Step 3 Allow the cover to hinge downward as shown in Figure 7-20.
Note: The cover will open only to a 30 degree angle.
Step 4 Pull the cover towards you while lifting it off the two hinge clips located at the bottom of the shelf, as shown in Figure 7-21.
Step 5 Place the shelf cover in a safe place until you are ready to reinstall it.
You have completed this task.
Page 7-30 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
7.10: Removing and Installing Front Covers onthe HS and HD TRIB Shelves
Figure 7-19: Grasp the Shelf Cover
Figure 7-20: Pull Down the Shelf Cover
DN
330
5D
N 3
306
Issue 7, May 1999 FNC and FNC Customer Use Only Page 7-31
7.10: Removing and Installing Front Covers on the HS and HD TRIB Shelves
Maintenance and Trouble ClearingFJTU-320-560-480
Installing the Shelf Cover
Step 1 Grasp the shelf front cover with both hands and place it so that the two hinge clips, located at the bottom of the shelf, fit into the slots at the bottom of the shelf cover as shown in Figure 7-22.
Figure 7-21: Remove the Shelf Cover
Figure 7-22: Align the Shelf Hinge Clips to the Shelf Cover Slots
DN
330
7
d620
2
Page 7-32 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
7.10: Removing and Installing Front Covers onthe HS and HD TRIB Shelves
Step 2 Pivot the shelf cover up into the closed position and press on the upper portion of the shelf cover until you hear the two side latches click as shown in Figure 7-23.
You have completed this task.
Figure 7-23: Reinstall the Shelf Cover
d620
3
Issue 7, May 1999 FNC and FNC Customer Use Only Page 7-33
7.10: Removing and Installing Front Covers on the HS and HD TRIB Shelves
Maintenance and Trouble ClearingFJTU-320-560-480
Page 7-34 FNC and FNC Customer Use Only Issue 7, May 1999
This page intentionally left blank.
Maintenance and Trouble ClearingFJTU-320-560-480
Appendix A: Trouble Analysis Log
APPENDIX A
A Trouble Analysis Log
Date Time System Generating Trouble Indication
Current Alarm and Status Conditions Time Cleared
Issue 7, May 1999 FNC and FNC Customer Use Only Page A-1
Appendix A: Trouble Analysis Log Maintenance and Trouble ClearingFJTU-320-560-480
Alarm Clearing Procedures
Alarm
Probable Cause
Procedures Performed
Time Alarm Cleared
Alarm Clearing Procedures
Alarm
Probable Cause
Procedures Performed
Time Alarm Cleared
Alarm Clearing Procedures
Alarm
Probable Cause
Procedures Performed
Time Alarm Cleared
Alarm Clearing Procedures
Alarm
Probable Cause
Procedures Performed
Time Alarm Cleared
Alarm Clearing Procedures
Alarm
Probable Cause
Procedures Performed
Time Alarm Cleared
Page A-2 FNC and FNC Customer Use Only Issue 7, May 1999
Maintenance and Trouble ClearingFJTU-320-560-480
Appendix B: Recommended Test Equipment
APPENDIX B
B Recommended Test Equipment
B.1 Test and Turn-Up
B.1.1 Optical Time Domain Reflectometer
• Base Unit (Fibertech 462L)
• Dual Laser (Fibertech 462-5)
• Source Connector (Fibertech 462-AP)
• DS1/DS3 Test Set (T-Berd Series 300)
• Base Unit (310)
• DS1 Drop (305-1)
• Demux DS3 (305-7)
• Terminal Printer (PR-40A)
• SONET Drop (310-4A)
• DS3 Jitter (310-5)
• SONET Receiver (310-14R)
• SONET Transmitter (310-14T)
• Software Upgrade (T-Berd 310)
B.1.2 Cables and Adapters
• PC Notebook, Dell 386SX (FNC PN 50-020-075)
• Modem, Hayes 2400-Baud (FNC PN 08-011-232)
• Bag, PC Notebook (FNC PN 58-010-642)
Issue 7, May 1999 FNC and FNC Customer Use Only Page B-1
B.2: Fiber Breaks Maintenance and Trouble ClearingFJTU-320-560-480
B.2 Fiber Breaks
B.2.1 Optical Time Domain Reflectometer
• Base Unit (Fibertech 462L)
• Dual Laser (Fibertech 462-5)
• Source Connector (Fibertech 462-AP)
B.3 General Maintenance and Troubleshooting
B.3.1 DS1/Berd Series 300)
• Base Unit (310)
• DS1 Drop (305-1)
• Demux DS3 (305-7)
• Terminal Printer (PR-40A)
• SONET Drop (310-4A)
• DS3 Jitter (310-5)
• SONET Receiver (310-14R)
• SONET Transmitter (310-14T)
• Software Upgrade (T-Berd 310)
B.3.2 Cables and Adapters
• PC Notebook, Dell 386SX (FNC PN 50-020-075)
• Modem, Hayes 2400-Baud (FNC PN 08-011-232)
• Bag, PC Notebook (FNC PN 58-010-642)
End of Practice
Page B-2 FNC and FNC Customer Use Only Issue 7, May 1999
User Comments
We appreciate your suggestions. Use the form below to rate the document and comment on any specific area.
Please describe the item that needs improvement or correction and the suggested change.
Section and page number: ______________________________________
____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
If you would like a reply, please give us your name, address, and fax number:
________________________________________________________________________________________________________
Category Excellent Good Fair Poor
Ease of use
Clarity
Completeness
Accuracy
Appearance
Figures
Examples
Overall satisfaction
Maintenance and Trouble ClearingFJTU-320-560-480
Issue 7, May 1999 FNC and FNC Customer Use Only
Fujitsu Network Communications, Inc., Technical Publications, 2801 Telecom Parkway, Richardson, TX 75082-9983;fax no.: (972) 479-3804; e-mail address: [email protected] Issue