Maintenance Cases (V100R004C04 - 01)

OptiX OSN 6800 Intelligent Optical Transport Platform/OptiX OSN
3800 Compact Intelligent Optical Transport Platform

V100R004C04
Maintenance Cases
Issue 01
Date 2009-08-10
Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For any
assistance, please contact our local office or company headquarters.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Copyright © Huawei Technologies Co., Ltd. 2009. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are the property of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but the statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Proprietary and Confidential

OptiX OSN 6800 Intelligent Optical Transport Platform/
OptiX OSN 3800 Compact Intelligent Optical Transport
Platform
Maintenance Cases Contents
Contents
About This Document.....................................................................................................................1

1 Classified by Products...............................................................................................................1-1
1.1 OptiX BWS 1600G.........................................................................................................................................1-2
1.2 OptiX Metro 6100...........................................................................................................................................1-4
1.3 OptiX Metro 6040...........................................................................................................................................1-5
1.4 OptiX OSN 6800.............................................................................................................................................1-5
2 Classified by Faults....................................................................................................................2-1
2.1 Service Interruption Cases..............................................................................................................................2-2
2.2 Transient Interruption Cases...........................................................................................................................2-2
2.3 Optical Power Abnormity Cases.....................................................................................................................2-2
2.4 Bit Errors Cases...............................................................................................................................................2-3
2.5 NE Offline Cases.............................................................................................................................................2-3
2.6 Other Cases.....................................................................................................................................................2-4
3 Classified by Alarms.................................................................................................................3-1
3.1 BEFFEC_EXC................................................................................................................................................3-2
3.2 IN_PWR_LOW...............................................................................................................................................3-2
3.3 LINK_ERR......................................................................................................................................................3-2
3.4 POWER_FAIL................................................................................................................................................3-2
3.5 R_LOF.............................................................................................................................................................3-3
3.6 R_LOS.............................................................................................................................................................3-3
3.7 R_SLIP............................................................................................................................................................3-3
3.8 R_OOF............................................................................................................................................................3-4
3.9 TF....................................................................................................................................................................3-4
3.10 OTU_LOF.....................................................................................................................................................3-4
3.11 Other Cases...................................................................................................................................................3-4
4 Classified by Functions and Features....................................................................................4-1

4.1 Ethernet Service Cases....................................................................................................................................4-2
4.2 Protection Cases..............................................................................................................................................4-2
4.3 Optical Power Management Cases..................................................................................................................4-2
4.4 ECC Cases.......................................................................................................................................................4-3
4.5 Orderwire Cases..............................................................................................................................................4-3
4.6 Equipment Interconnection Cases...................................................................................................................4-3
Issue 01 (2009-08-10) Huawei Proprietary and Confidential i

Platform
Contents Maintenance Cases
4.7 Other Cases.....................................................................................................................................................4-4
5 MC-A1 to MC-A108....................................................................................................................5-1
5.1 MC-A1 The OTU_LOF Alarm is Reporting on the OTU at the Downstream Station...................................5-8
5.2 MC-A2 The E1V40 Board Reports the POWER_FAIL and MODULE_TEMP_OVER Alarms..................5-9
5.3 MC-A3 The FDG Board Reports the ALM_DATA_RLOS Alarm in the Early Morning.............................5-9
5.4 MC-A4 The LOG Board Fails to Interwork With the FDG Board on the Client Sides................................5-10
5.5 MC-A5 The LQG Board Reports the ALM_DATA_RLOS and ALM_DATA_TLOS Alarms Transiently
.............................................................................................................................................................................5-12
5.6 MC-A6 The LDG Board Keeps Reporting the ALM_DATA_TLOS and ALM_DATA_RLOS Alarms
Transiently...........................................................................................................................................................5-13
5.7 MC-A7 The R_SLIP Alarm Is Generated Because of Improper Fiber Connections on the OSC Board.....5-14
5.8 MC-A8 The TN11OAU101 at the Transmit End Reports the MUT_LOS Alarm........................................5-15
5.9 MC-A11 The SSE3LWF Board Reports the OTU_LOF Alarm When Interworking with the SSE1TMR
.............................................................................................................................................................................5-16
5.10 MC-A12 Certain Boards Report the TF Alarm Transiently.......................................................................5-17
5.11 MD-A13 Bit Error Alarm Is Generated When Optical Power Gets Close to the Threshold......................5-18
5.12 MC-A14 The LWF Board Reports R_LOS................................................................................................5-19
5.13 MC-A15 The Downstream Optical Amplifier Board Does Not Report R_LOS........................................5-21
5.14 MC-A16 LOF/OOF Is Reported in the 24-Hour Bit Error Test Because the Line Fiber Loss Is Very Large
.............................................................................................................................................................................5-22
5.15 MC-A17 The LQG Reports ALM_DATA_RLOS and ALM_DATA_TLOS Alarms...............................5-23
5.16 MC-A18 TTL Was Abnormal.....................................................................................................................5-24
5.17 MC-A19 Use Power Monitoring To Process Problems On Wavelength Division.....................................5-25
5.18 MC-A20 The T2000 Cannot Log in to the Remote GNE Connected by the Router..................................5-27
5.19 MC-A21 An Interconnection Failure between the WDM and SDH Equipment........................................5-28
5.20 MC-A22 NE ESC Communication Interrupted Because of the Closure of the OTU Laser.......................5-29
5.21 MC-A23 When the OTU Board Accesses Light, the Laser at Output End is Disabled..............................5-30
5.22 MC-A24 Low Optical Power on the Client Side of the OTU Board Leads to R_LOS Alarm on the Board
.............................................................................................................................................................................5-31
5.23 MC-A25 The System Indicates that the Channel Number Is Illegal...........................................................5-32
5.24 MC-A26 The Centralized Power Distribution Cabinet Endures Power Failure.........................................5-33
5.25 MC-A27 Should the Nominal Gain of the OAU1 Board Be Re-set?.........................................................5-35
5.26 MC-A28 The LSX Board Reports the OTUk_LOF Alarm.........................................................................5-36
5.27 MC-A29 On the OptiX OSN 6800, End-to-end GE Services Cannot Be Created.....................................5-37
5.28 MC-A30 LDG Board of Metro 6100 Equipment Reports the INBADOCTS_OVER Alarm....................5-38
5.29 MC-A31 Wrong Calculation for Dispersion in One DWDM Project.........................................................5-39
5.30 MC-A32 When OptiX BWS 1600G SCC Board Is Replaced with the SCE, TC2 Board Reports BD_STATUS
Alarm...................................................................................................................................................................5-40
5.31 MC-A33 Remotely Checking the Correctness of the DCM Installation....................................................5-41
5.32 MC-A34 The Subrack Alarm Cannot be Uploaded to the Alarm Indicator in the Cabinet........................5-42
5.33 MC-A35 LWM Output Optical Power Is Unstable upon Forced Light Generation...................................5-43
5.34 MC-A36 The OTU in the OptiX BWS 1600G Reports IN_PWR_LOW Alarm........................................5-44
5.35 MC-A37 The LWFS in the OptiX BWS 1600G Transiently Reports FEC_LOF Alarm...........................5-46
5.36 MC-A38 The Service Is Interrupted After the Protection Is Triggered......................................................5-47
ii Huawei Proprietary and Confidential Issue 01 (2009-08-10)

Platform
Maintenance Cases Contents
5.37 MC-A39 There Are Errors in the Setting of the Meter ONT-30.................................................................5-48
5.38 MC-A40 Over Compensation Causes Very High Bit Error Rate of the Short Waves After Correction....5-49
5.39 MC-A41 Unsuccessful 1: N Protection Subnet Search...............................................................................5-51
5.40 MC-A42 A Fault of the PMU for the OptiX BWS 1600G Results In an Orderwire Ringing Failure........5-52
5.41 MC-A43 Too High Insertion Loss Between TDC and RDC of the E3OAUC01C.....................................5-53
5.42 MC-A44 Bit Errors Generated in the Services............................................................................................5-54
5.43 MC-A45 During the deployment of Raman, the OPU board reports MUT_LOS......................................5-55
5.44 MC-A46 POWERALM Alarm in OptiX BWS 1600G Caused by Switching off the Upper Subrack.......5-56
5.45 MC-A47 The CRC4_CROSSTR Alarm Is Generated Because of Low Fiber Quality..............................5-56
5.46 MC-A48 The T2000 Cannot Search the Wavelength Trail........................................................................5-57
5.47 MC-A49 An Incorrect Setting of CRC Results in an Interconnection Failure...........................................5-58
5.48 MC-A50 Measure the PMD of an Optical Cable to Determine the Quality of the Optical Cable..............5-60
5.49 MC-A52 Faults of End Face of the Fiber Connector Cannot Be Identified................................................5-60
5.50 MC-A53 OptiX BWS 1600G Cannot Be Deleted on the T2000................................................................5-62
5.51 MC-A54 After the Lasers of the Raman Amplifier Are Disabled, the Optical Power Is Abnormal..........5-63
5.52 MC-A55 Improper DCM Distribution Causes Abnormal Service..............................................................5-64
5.53 MC-A56 LWF Board Reports OTU_LOF Alarm.......................................................................................5-65
5.54 MC-A57 How to Clear OTU Alarms Because of Unused Ports.................................................................5-67
5.55 MC-A59 Mismatch of SC2 Models Causes Frequent Reporting of the CRC4_CROSSTR Alarm...........5-68
5.56 MC-A62 The Minimum Optical Power of the SC2 Is Detected As -35 dBm............................................5-69
5.57 MC-A63 Bit Errors Occur in a DWDM 10G Network Due to the Uncorrect PMD...................................5-70
5.58 MC-A64 Many BD_STATUS Alarms Occur Due to the ECC Storm........................................................5-71
5.59 MC-A65 The Gain of the RPC Board Cannot Exceed 10 dB Due to Excessively High Attenuation of Flange
.............................................................................................................................................................................5-72
5.60 MC-A66 The Received Optical Power of Downstream Stations Is not Flat...............................................5-74
5.61 MC-A67 The GE Port on the Client Side Reports LINK_DOWN Alarm..................................................5-75
5.62 MC-A68 OTU Boards Report the IN_PWR_LOW Alarm Due to Wavelength Wander...........................5-76
5.63 MC-A69 Shutdown of the RPC Laser Interrupts SDH-Layer Services in a DWDM Network..................5-77
5.64 MC-A71 Excessive Attenuation Results in That the Gain of the E3OAU Cannot Be Set.........................5-78
5.65 MC-A72 The OTU_LOF Alarm Reported in the LWC1 Due to Wrong Regenerator Board.....................5-78
5.66 MC-A74 The FDG Reports the T_DATA_LOST and R_DATA_LOST Alarms......................................5-79
5.67 MC-A75 Bandwidth Decreases and Service Rate Becomes Lower Due to Improper Setting....................5-80
5.68 MC-A76 The PMU Cannot Work Normally...............................................................................................5-81
5.69 MC-A77 Improper Configuration of Protocol Channels Results in a Failure of the ALC to Start.............5-82
5.70 MC-A78 When the IPA Is Set or Deleted, the OAU Alarm Threshold Changes Due to Version Features
.............................................................................................................................................................................5-83
5.71 MC-A79 The MCA Board Reports an Execution Failure...........................................................................5-84
5.72 MC-A80 Intermittent BEFFEC_EXC Alarm at IN/OUT optical interfaces on LWF board......................5-85
5.73 MC-A81 The ALC Cannot Run..................................................................................................................5-86
5.74 MC-A82 Analysis of the POWER_FAIL Alarm on the OptiX OSN 6800 and Solution...........................5-87
5.75 MC-A83 The OptiX OSN 6800 Is Not Reachable When the NE IP Is Modified.......................................5-88
5.76 MC-A84 Maximal packet length setting of the OptiX OSN 6800 Causes the Abnormal Service.............5-89
5.77 MC-A85 SWDL_CHGMNG_NOMATCH Alarm Is Reported.................................................................5-90
Issue 01 (2009-08-10) Huawei Proprietary and Confidential iii

Platform
Contents Maintenance Cases
5.78 MC-A86 Inserting, Removing, and Resetting Operations Affect NG WDM Products..............................5-91
5.79 MC-A87 SWDL_CHGMNG_NOMATCH Alarm Is Reported.................................................................5-94
5.80 MC-A88 Difference in BER Reported by the OTU Board and Test Instrument........................................5-96
5.81 MC-A89 Two Different Power Supplies for the OptiX Metro 6100..........................................................5-97
5.82 MC-A90 The Incorrect Configuration of DWC Leads To Abnormal Optical Power and Service Interruption
.............................................................................................................................................................................5-98
5.83 MC-A91 Creation of Intra-Board Wavelength Protection on the LDG Fails.............................................5-99
5.84 MC-A92 How to Handle the J0_MM Alarm on the LWM.......................................................................5-100
5.85 MC-A93: The Input Optical Power of the OTU Board Is Abnormal Due to a Fault of the OPU Board..5-101
5.86 MC-A94: The WXCP Protection Configured for the LOG Board Is Invalid...........................................5-102
5.87 MC-A95: The SC2 Board Reports the CRC4_CROSSTR Alarm............................................................5-103
5.88 MC-A96: Packet Loss Occurs in Ethernet Service Testing of the L4G Board.........................................5-104
5.89 MC-A97: The Optical Amplifier Reports the IN_PWR_HIGH Alarm Because of Optical Power Reflection
...........................................................................................................................................................................5-105
5.90 MC-A98: The Protection Switching Times Out Severely........................................................................5-105
5.91 MC-A99: The PMU Reports the THUNDERALM Alarm.......................................................................5-107
5.92 MC-A100: The FDG Board Reports the R_DATA_LOST Alarm in the Early Morning........................5-108
5.93 MC-A101: The Wavelength Is Unstable or Changed Due to Optical Power Variation...........................5-109
5.94 MC-A102: The LBE, LDG and LQG Boards Report the LINK_ERR or LINK_STATUS Alarm..........5-109
5.95 MC-A103: How to Configure the Dual Feed and Selective Receiving Boards........................................5-111
5.96 MC-A104: No Optical Power Is Output on the WDM Side Due to Incorrect Configuration...................5-112
5.97 MC-A105: Line Reflection Leads to Inaccurate BER Detection of the SSC6LWX Board......................5-112
5.98 MC-A106: OptiX Metro 6100 Reports the PWR_MAJ_ALM Alarm.....................................................5-115
5.99 MC-A107: The Cross-Connection Function of the Subrack Fails............................................................5-116
5.100 MC-A108: How to Select Test Meters on Site When Testing OTU Boards of the Data Type..............5-117
A Glossary..................................................................................................................................... A-1
B Acronyms and Abbreviations.................................................................................................B-1
iv Huawei Proprietary and Confidential Issue 01 (2009-08-10)

Platform
Maintenance Cases Figures
Figures
Figure 5-1 Networking diagram.......................................................................................................................5-113

Figure 5-2 Working pinciple of the SSC6LWX board.....................................................................................5-114
Figure 5-3 Main signal eye patterns when the secondary reflection interference does not exist and exists....5-115
Issue 01 (2009-08-10) Huawei Proprietary and Confidential v

Platform
Maintenance Cases Tables
Tables
Table 5-1 PMD coefficient relation....................................................................................................................5-71

Table 5-2 Affection of plugging & unplugging and resetting operations of the SCC .......................................5-92
Table 5-3 Bit error thresholds for the STM-16 service......................................................................................5-97
Issue 01 (2009-08-10) Huawei Proprietary and Confidential vii

Platform
Maintenance Cases About This Document
About This Document
Purpose
This document lists 100 cases of actual project maintenance and provides four entries of case
classification: classified by products, classified by faults, classified by alarms, and classified by
functions and features. You can find the desired cases quickly with a proper entry of
classification.
Intended Audience
The intended audiences of this document are:
l Field Maintenance Engineer

l Network Monitoring Engineer
l System maintenance engineer
Organization
This document consists of following chapters and is organized as follows.
Chapter Description
1 Classified by Products When the entry of classification by products is selected,

the cases of faults of the OptiX BWS 1600G, OptiX Metro
6100, OptiX Metro 6040, and OptiX OSN 6800 are listed
separately.
2 Classified by Faults When the entry of classification by faults is selected, the

cases of service interruption, cases of transient service
interruption, cases of abnormal optical power, cases of bit
errors, and cases of communication interruption between
an NE and the T2000, are listed separately.
3 Classified by Alarms When the entry of classification by alarms is selected, the

cases of faults indicated by 30 common alarms such as
R_LOS are listed separately.
Issue 01 (2009-08-10) Huawei Proprietary and Confidential 1

Platform
About This Document Maintenance Cases
Chapter Description
4 Classified by Functions and When the entry of classification by functions and features
Features is selected, the cases of Ethernet services, cases of
protection, cases of optical power management, cases of
error checking and correction (ECC), and cases of
orderwire, and cases of equipment interconnection, are
listed separately.
5 MC-A1 to MC-A108 Lists all the cases, that is, case 1 to case 108.
A Glossary Lists the glossary mentioned in this document.
B Acronyms and Lists the abbreviations and acronyms mentioned in this

Abbreviations document.
Conventions
Symbol Conventions
The following symbols may be found in this document. They are defined as follows.
Symbol Description
Indicates a hazard with a high level of risk which, if not

avoided, will result in death or serious injury.
DANGER
Indicates a hazard with a medium or low level of risk which,

if not avoided, could result in minor or moderate injury.
WARNING
Indicates a potentially hazardous situation that, if not

avoided, could cause equipment damage, data loss, and
CAUTION
performance degradation, or unexpected results.
TIP Indicates a tip that may help you solve a problem or save
your time.
NOTE Provides additional information to emphasize or

supplement important points of the main text.
General Conventions
Convention Description
Times New Roman Normal paragraphs are in Times New Roman.
Boldface Names of files, directories, folders, and users are in boldface. For
example, log in as user root.
2 Huawei Proprietary and Confidential Issue 01 (2009-08-10)

Platform
Maintenance Cases About This Document
Italic Book titles are in italics.

Courier New Terminal display is in Courier New.
Command Conventions
Boldface The keywords of a command line are in boldface.
Italic Command arguments are in italic.
[] Items (keywords or arguments) in square brackets [ ] are

optional.
{ x | y | ... } Alternative items are grouped in braces and separated by

vertical bars. One is selected.
[ x | y | ... ] Optional alternative items are grouped in square brackets

and separated by vertical bars. One or none is selected.
{ x | y | ... } * Alternative items are grouped in braces and separated by

vertical bars. A minimum of one or a maximum of all can
be selected.
GUI Conventions
Boldface Buttons, menus, parameters, tabs, window, and dialog titles are in
boldface. For example, click OK.
> Multi-level menus are in boldface and separated by the ">" signs. For
example, choose File > Create > Folder.
Keyboard Operation
Format Description
Key Press the key. For example, press Enter and press Tab.
Key 1+Key 2 Press the keys concurrently. For example, pressingCtrl+Alt+A means the
three keys should be pressed concurrently.
Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A means the two keys
should be pressed in turn.
Issue 01 (2009-08-10) Huawei Proprietary and Confidential 3

Platform
About This Document Maintenance Cases
Mouse Operation
Action Description
Click Select and release the primary mouse button without moving the pointer.
Double-click Press the primary mouse button twice continuously and quickly without
moving the pointer.
Drag Press and hold the primary mouse button and move the pointer to a certain
position.
Update History
Updates in Issue 01 (2009-08-10) Based on Product Version V100R004C04
Some bugs in former version are fixed in this version.

This document is the second release.
Add 53 cases of actual project maintenance.

Add 47 cases of actual project maintenance.


This document is the first release.
4 Huawei Proprietary and Confidential Issue 01 (2009-08-10)

Platform
Maintenance Cases 1 Classified by Products
1 Classified by Products
About This Chapter
1.1 OptiX BWS 1600G

Case analysis related to OptiX BWS 1600G.
1.2 OptiX Metro 6100
Case analysis related to OptiX Metro 6100.
1.4 OptiX OSN 6800
Case analysis related to OptiX OSN 6800.
Issue 01 (2009-08-10) Huawei Proprietary and Confidential 1-1

Platform
1 Classified by Products Maintenance Cases
1.1 OptiX BWS 1600G

Case analysis related to OptiX BWS 1600G.
Related Cases:
l 5.1 MC-A1 The OTU_LOF Alarm is Reporting on the OTU at the Downstream
Station
l 5.2 MC-A2 The E1V40 Board Reports the POWER_FAIL and
MODULE_TEMP_OVER Alarms
l 5.4 MC-A4 The LOG Board Fails to Interwork With the FDG Board on the Client
Sides.
l 5.7 MC-A7 The R_SLIP Alarm Is Generated Because of Improper Fiber Connections
on the OSC Board
l 5.9 MC-A11 The SSE3LWF Board Reports the OTU_LOF Alarm When
Interworking with the SSE1TMR
l 5.10 MC-A12 Certain Boards Report the TF Alarm Transiently
l 5.11 MD-A13 Bit Error Alarm Is Generated When Optical Power Gets Close to the
Threshold
l 5.12 MC-A14 The LWF Board Reports R_LOS
l 5.14 MC-A16 LOF/OOF Is Reported in the 24-Hour Bit Error Test Because the Line
Fiber Loss Is Very Large
l 5.16 MC-A18 TTL Was Abnormal
l 5.19 MC-A21 An Interconnection Failure between the WDM and SDH Equipment
l 5.21 MC-A23 When the OTU Board Accesses Light, the Laser at Output End is
Disabled
l 5.22 MC-A24 Low Optical Power on the Client Side of the OTU Board Leads to
R_LOS Alarm on the Board
l 5.30 MC-A32 When OptiX BWS 1600G SCC Board Is Replaced with the SCE, TC2
Board Reports BD_STATUS Alarm
l 5.31 MC-A33 Remotely Checking the Correctness of the DCM Installation
l 5.32 MC-A34 The Subrack Alarm Cannot be Uploaded to the Alarm Indicator in the
Cabinet
l 5.33 MC-A35 LWM Output Optical Power Is Unstable upon Forced Light Generation
l 5.34 MC-A36 The OTU in the OptiX BWS 1600G Reports IN_PWR_LOW Alarm
l 5.35 MC-A37 The LWFS in the OptiX BWS 1600G Transiently Reports FEC_LOF
Alarm
l 5.36 MC-A38 The Service Is Interrupted After the Protection Is Triggered
l 5.37 MC-A39 There Are Errors in the Setting of the Meter ONT-30
l 5.38 MC-A40 Over Compensation Causes Very High Bit Error Rate of the Short
Waves After Correction
l 5.39 MC-A41 Unsuccessful 1: N Protection Subnet Search
l 5.40 MC-A42 A Fault of the PMU for the OptiX BWS 1600G Results In an Orderwire
Ringing Failure
1-2 Huawei Proprietary and Confidential Issue 01 (2009-08-10)

Platform
l 5.41 MC-A43 Too High Insertion Loss Between TDC and RDC of the E3OAUC01C
l 5.42 MC-A44 Bit Errors Generated in the Services
l 5.43 MC-A45 During the deployment of Raman, the OPU board reports MUT_LOS
l 5.44 MC-A46 POWERALM Alarm in OptiX BWS 1600G Caused by Switching off
the Upper Subrack
l 5.45 MC-A47 The CRC4_CROSSTR Alarm Is Generated Because of Low Fiber
Quality
l 5.46 MC-A48 The T2000 Cannot Search the Wavelength Trail
l 5.47 MC-A49 An Incorrect Setting of CRC Results in an Interconnection Failure
l 5.48 MC-A50 Measure the PMD of an Optical Cable to Determine the Quality of the
Optical Cable
l 5.49 MC-A52 Faults of End Face of the Fiber Connector Cannot Be Identified
l 5.50 MC-A53 OptiX BWS 1600G Cannot Be Deleted on the T2000
l 5.51 MC-A54 After the Lasers of the Raman Amplifier Are Disabled, the Optical
Power Is Abnormal
l 5.52 MC-A55 Improper DCM Distribution Causes Abnormal Service
l 5.53 MC-A56 LWF Board Reports OTU_LOF Alarm
l 5.54 MC-A57 How to Clear OTU Alarms Because of Unused Ports
l 5.55 MC-A59 Mismatch of SC2 Models Causes Frequent Reporting of the
CRC4_CROSSTR Alarm
l 5.56 MC-A62 The Minimum Optical Power of the SC2 Is Detected As -35 dBm
l 5.57 MC-A63 Bit Errors Occur in a DWDM 10G Network Due to the Uncorrect PMD
l 5.58 MC-A64 Many BD_STATUS Alarms Occur Due to the ECC Storm
l 5.59 MC-A65 The Gain of the RPC Board Cannot Exceed 10 dB Due to Excessively
High Attenuation of Flange
l 5.60 MC-A66 The Received Optical Power of Downstream Stations Is not Flat
l 5.61 MC-A67 The GE Port on the Client Side Reports LINK_DOWN Alarm
l 5.62 MC-A68 OTU Boards Report the IN_PWR_LOW Alarm Due to Wavelength
Wander
l 5.63 MC-A69 Shutdown of the RPC Laser Interrupts SDH-Layer Services in a
DWDM Network
l 5.64 MC-A71 Excessive Attenuation Results in That the Gain of the E3OAU Cannot
Be Set
l 5.65 MC-A72 The OTU_LOF Alarm Reported in the LWC1 Due to Wrong
Regenerator Board
l 5.66 MC-A74 The FDG Reports the T_DATA_LOST and R_DATA_LOST Alarms
l 5.67 MC-A75 Bandwidth Decreases and Service Rate Becomes Lower Due to
Improper Setting
l 5.68 MC-A76 The PMU Cannot Work Normally
l 5.69 MC-A77 Improper Configuration of Protocol Channels Results in a Failure of
the ALC to Start

Platform
l 5.70 MC-A78 When the IPA Is Set or Deleted, the OAU Alarm Threshold Changes
Due to Version Features
l 5.71 MC-A79 The MCA Board Reports an Execution Failure
l 5.72 MC-A80 Intermittent BEFFEC_EXC Alarm at IN/OUT optical interfaces on
LWF board

Related Cases:
l 5.3 MC-A3 The FDG Board Reports the ALM_DATA_RLOS Alarm in the Early
Morning
Sides.
l 5.5 MC-A5 The LQG Board Reports the ALM_DATA_RLOS and
ALM_DATA_TLOS Alarms Transiently
l 5.6 MC-A6 The LDG Board Keeps Reporting the ALM_DATA_TLOS and
ALM_DATA_RLOS Alarms Transiently
l 5.13 MC-A15 The Downstream Optical Amplifier Board Does Not Report R_LOS
l 5.15 MC-A17 The LQG Reports ALM_DATA_RLOS and ALM_DATA_TLOS
Alarms
l 5.17 MC-A19 Use Power Monitoring To Process Problems On Wavelength Division
l 5.18 MC-A20 The T2000 Cannot Log in to the Remote GNE Connected by the Router
l 5.20 MC-A22 NE ESC Communication Interrupted Because of the Closure of the
OTU Laser
l 5.28 MC-A30 LDG Board of Metro 6100 Equipment Reports the
INBADOCTS_OVER Alarm
l 5.29 MC-A31 Wrong Calculation for Dispersion in One DWDM Project
l 5.80 MC-A88 Difference in BER Reported by the OTU Board and Test Instrument
l 5.81 MC-A89 Two Different Power Supplies for the OptiX Metro 6100
l 5.82 MC-A90 The Incorrect Configuration of DWC Leads To Abnormal Optical
Power and Service Interruption
l 5.83 MC-A91 Creation of Intra-Board Wavelength Protection on the LDG Fails
l 5.84 MC-A92 How to Handle the J0_MM Alarm on the LWM
l 5.85 MC-A93: The Input Optical Power of the OTU Board Is Abnormal Due to a Fault
of the OPU Board
l 5.86 MC-A94: The WXCP Protection Configured for the LOG Board Is Invalid
l 5.87 MC-A95: The SC2 Board Reports the CRC4_CROSSTR Alarm
l 5.88 MC-A96: Packet Loss Occurs in Ethernet Service Testing of the L4G Board
l 5.89 MC-A97: The Optical Amplifier Reports the IN_PWR_HIGH Alarm Because of
Optical Power Reflection
l 5.90 MC-A98: The Protection Switching Times Out Severely

Platform
l 5.91 MC-A99: The PMU Reports the THUNDERALM Alarm

l 5.92 MC-A100: The FDG Board Reports the R_DATA_LOST Alarm in the Early
Morning
l 5.93 MC-A101: The Wavelength Is Unstable or Changed Due to Optical Power
Variation
l 5.94 MC-A102: The LBE, LDG and LQG Boards Report the LINK_ERR or
LINK_STATUS Alarm
l 5.95 MC-A103: How to Configure the Dual Feed and Selective Receiving Boards
l 5.96 MC-A104: No Optical Power Is Output on the WDM Side Due to Incorrect
Configuration
l 5.97 MC-A105: Line Reflection Leads to Inaccurate BER Detection of the SSC6LWX
Board
l 5.98 MC-A106: OptiX Metro 6100 Reports the PWR_MAJ_ALM Alarm
l 5.99 MC-A107: The Cross-Connection Function of the Subrack Fails
l 5.100 MC-A108: How to Select Test Meters on Site When Testing OTU Boards of the
Data Type

Related Cases:
1.4 OptiX OSN 6800

Case analysis related to OptiX OSN 6800.
Related Cases:
l 5.8 MC-A8 The TN11OAU101 at the Transmit End Reports the MUT_LOS Alarm
l 5.23 MC-A25 The System Indicates that the Channel Number Is Illegal
l 5.24 MC-A26 The Centralized Power Distribution Cabinet Endures Power Failure
l 5.25 MC-A27 Should the Nominal Gain of the OAU1 Board Be Re-set?
l 5.26 MC-A28 The LSX Board Reports the OTUk_LOF Alarm
l 5.27 MC-A29 On the OptiX OSN 6800, End-to-end GE Services Cannot Be Created
l 5.73 MC-A81 The ALC Cannot Run
l 5.74 MC-A82 Analysis of the POWER_FAIL Alarm on the OptiX OSN 6800 and
Solution
l 5.75 MC-A83 The OptiX OSN 6800 Is Not Reachable When the NE IP Is Modified
l 5.76 MC-A84 Maximal packet length setting of the OptiX OSN 6800 Causes the
Abnormal Service
l 5.77 MC-A85 SWDL_CHGMNG_NOMATCH Alarm Is Reported

Platform
l 5.78 MC-A86 Inserting, Removing, and Resetting Operations Affect NG WDM

Products

Platform
Maintenance Cases 2 Classified by Faults
2 Classified by Faults
About This Chapter
2.1 Service Interruption Cases

Case analysis related to Service Interruption cases.
2.2 Transient Interruption Cases
Case analysis related to Transient Interruption cases.
2.3 Optical Power Abnormity Cases
Case analysis related to Optical Power Abnormity cases.
2.4 Bit Errors Cases
Case analysis related to Bit Errors cases.
2.5 NE Offline Cases
Case analysis related to NE Offline cases.
2.6 Other Cases
Case analysis related to other cases.

Platform
2 Classified by Faults Maintenance Cases
2.1 Service Interruption Cases

Case analysis related to Service Interruption cases.
NOTE
The following cases are the cases relevant to the OptiX WDM product series.
Related Cases:
Station
Sides.
DWDM Network
2.2 Transient Interruption Cases

Case analysis related to Transient Interruption cases.
NOTE
Related Cases:
2.3 Optical Power Abnormity Cases

Case analysis related to Optical Power Abnormity cases.
NOTE
Related Cases:
Threshold

Platform
Power Is Abnormal
Wander
of the OPU Board
Variation
2.4 Bit Errors Cases

Case analysis related to Bit Errors cases.
NOTE
Related Cases:
Threshold
2.5 NE Offline Cases

Case analysis related to NE Offline cases.

Platform
NOTE
Related Cases:
OTU Laser
2.6 Other Cases

NOTE
Related Cases:
Station
Morning
Sides.
on the OSC Board
Alarms
Disabled

Platform

Cabinet
Alarm
Ringing Failure
the Upper Subrack
Quality
Optical Cable
CRC4_CROSSTR Alarm
Improper Setting
the ALC to Start
LWF board
Solution

Platform
Abnormal Service
Products
Morning
LINK_STATUS Alarm
Configuration
Board
Data Type

Platform
Maintenance Cases 3 Classified by Alarms
3 Classified by Alarms
About This Chapter
3.1 BEFFEC_EXC
Case analysis related to BEFFEC_EXC.
3.2 IN_PWR_LOW
Case analysis related to IN_PWR_LOW.
3.3 LINK_ERR
Case analysis related to LINK_ERR.
3.4 POWER_FAIL
Case analysis related to POWER_FAIL.
3.5 R_LOF
Case analysis related to R_LOF.
3.6 R_LOS
Case analysis related to R_LOS.
3.7 R_SLIP
Case analysis related to R_SLIP.
3.8 R_OOF
Case analysis related to R_OOF.
3.9 TF
Case analysis related to TF.
3.10 OTU_LOF
Case analysis related to OTU_LOF.
3.11 Other Cases
Case analysis related to Other cases.

Platform
3 Classified by Alarms Maintenance Cases
3.1 BEFFEC_EXC
Case analysis related to BEFFEC_EXC.
NOTE
Related Cases:
Threshold
LWF board
3.2 IN_PWR_LOW
Case analysis related to IN_PWR_LOW.
NOTE
Related Cases:
Wander
3.3 LINK_ERR
Case analysis related to LINK_ERR.
NOTE
Related Cases:
Sides.
LINK_STATUS Alarm
3.4 POWER_FAIL
Case analysis related to POWER_FAIL.
NOTE

Platform
Related Cases:
Solution
3.5 R_LOF
Case analysis related to R_LOF.
NOTE
Related Cases:
Configuration
3.6 R_LOS
Case analysis related to R_LOS.
NOTE
Related Cases:
Station
Sides.
3.7 R_SLIP
Case analysis related to R_SLIP.
NOTE

Platform
Related Cases:
on the OSC Board
3.8 R_OOF
Case analysis related to R_OOF.
NOTE
Related Cases:
3.9 TF
Case analysis related to TF.
NOTE
Related Cases:
3.10 OTU_LOF
Case analysis related to OTU_LOF.
NOTE
Related Cases:
Station
Regenerator Board
3.11 Other Cases

Case analysis related to Other cases.

Platform
NOTE
Related Cases:
Morning
Alarms
OTU Laser
Disabled
Cabinet
Alarm
Ringing Failure
the Upper Subrack

Platform

Quality
Optical Cable
Power Is Abnormal
CRC4_CROSSTR Alarm
DWDM Network
Be Set
Improper Setting
the ALC to Start
Abnormal Service
Products

Platform
of the OPU Board
Morning
Variation
Board
Data Type

Platform
Maintenance Cases 4 Classified by Functions and Features
4 Classified by Functions and Features
About This Chapter
4.1 Ethernet Service Cases

Case analysis related to Ethernet Service cases.
4.2 Protection Cases
Case analysis related to Protection cases.
4.3 Optical Power Management Cases
Case analysis related to Optical Power Management cases.
4.4 ECC Cases
Case analysis related to ECC cases.
4.5 Orderwire Cases
Case analysis related to Orderwire cases.
4.6 Equipment Interconnection Cases
Case analysis related to Equipment Interconnection cases.
4.7 Other Cases

Platform
4 Classified by Functions and Features Maintenance Cases
4.1 Ethernet Service Cases

Case analysis related to Ethernet Service cases.
NOTE
Related Cases:
Morning
Sides.
Alarms
4.2 Protection Cases

Case analysis related to Protection cases.
NOTE
Related Cases:
Disabled
4.3 Optical Power Management Cases

Case analysis related to Optical Power Management cases.

Platform
NOTE
Related Cases:
the ALC to Start
4.4 ECC Cases

Case analysis related to ECC cases.
NOTE
Related Cases:
OTU Laser
4.5 Orderwire Cases

Case analysis related to Orderwire cases.
NOTE
Related Cases:
Ringing Failure
4.6 Equipment Interconnection Cases

Case analysis related to Equipment Interconnection cases.
NOTE
Related Cases:
Morning
Sides.

Platform

Alarms
Improper Setting
Abnormal Service
4.7 Other Cases

NOTE
Related Cases:
Station
on the OSC Board
Threshold

Platform
Cabinet
Alarm
the Upper Subrack
Quality
Optical Cable
Power Is Abnormal
CRC4_CROSSTR Alarm

Platform
Wander
DWDM Network
Be Set
Regenerator Board
LWF board
Solution
Products
of the OPU Board
Morning
Variation
LINK_STATUS Alarm
Configuration
Board

Platform
Data Type

Platform
Maintenance Cases 5 MC-A1 to MC-A108
5 MC-A1 to MC-A108
About This Chapter
5.1 MC-A1 The OTU_LOF Alarm is Reporting on the OTU at the Downstream Station
The TF alarm on the OTU at the upstream station results in the OTU_LOF alarm on the OTU
at the downstream station.
5.2 MC-A2 The E1V40 Board Reports the POWER_FAIL and MODULE_TEMP_OVER
Alarms
The E1V40 board reports the POWER_FAIL and MODULE_TEMP_OVER alarms when the
primary power supply module is faulty.
5.3 MC-A3 The FDG Board Reports the ALM_DATA_RLOS Alarm in the Early Morning
The FDG board reports the ALM_DATA_RLOS alarm in the early morning when the traffic
volume is light.
5.4 MC-A4 The LOG Board Fails to Interwork With the FDG Board on the Client Sides.
The LOG board fails to interwork with the FDG board on the client sides because the loss in the
fiber jumper is extremely large.
5.5 MC-A5 The LQG Board Reports the ALM_DATA_RLOS and ALM_DATA_TLOS Alarms
Transiently
The LQG board reports the ALM_DATA_RLOS and ALM_DATA_TLOS alarms transiently
because the channel does not carry services.
5.6 MC-A6 The LDG Board Keeps Reporting the ALM_DATA_TLOS and
The LDG board keeps reporting the ALM_DATA_TLOS and ALM_DATA_RLOS alarms
transiently.
5.7 MC-A7 The R_SLIP Alarm Is Generated Because of Improper Fiber Connections on the
OSC Board
The R_SLIP alarm is generated because of improper fiber connections on the OSC board.
5.8 MC-A8 The TN11OAU101 at the Transmit End Reports the MUT_LOS Alarm
The TN11OAU101 at the transmit end reports the MUT_LOS alarm because the optical
attenuation of the M40V board is not adjusted.
5.9 MC-A11 The SSE3LWF Board Reports the OTU_LOF Alarm When Interworking with the
SSE1TMR

Platform
5 MC-A1 to MC-A108 Maintenance Cases
The SSE3LWF board reports the OTU_LOF alarm when interworking with the SSE1TMR.
5.10 MC-A12 Certain Boards Report the TF Alarm Transiently
Certain boards report the TF alarm transiently because the FAN speed is low and the board
temperature reaches 60 degrees centigrade.
5.11 MD-A13 Bit Error Alarm Is Generated When Optical Power Gets Close to the Threshold
Bit error alarm is generated when optical power gets close to the threshold.
5.12 MC-A14 The LWF Board Reports R_LOS
The LWF board reports R_LOS because the incorrect fiber type leads to dispersion over-
compensation.
5.13 MC-A15 The Downstream Optical Amplifier Board Does Not Report R_LOS
The downstream optical amplifier board does not report R_LOS when the service between the
upstream optical amplifier board and the FIU board is interrupted.
5.14 MC-A16 LOF/OOF Is Reported in the 24-Hour Bit Error Test Because the Line Fiber Loss
Is Very Large
LOF/OOF is reported in the 24-hour bit error test because the line fiber loss is very large.
5.15 MC-A17 The LQG Reports ALM_DATA_RLOS and ALM_DATA_TLOS Alarms
The LQG reports ALM_DATA_RLOS and ALM_DATA_TLOS alarms in the corresponding
channel because of wavelength mismatch.
5.16 MC-A18 TTL Was Abnormal
TTL was abnormal.
5.17 MC-A19 Use Power Monitoring To Process Problems On Wavelength Division
Use power monitoring to process problems on wavelength division.
5.18 MC-A20 The T2000 Cannot Log in to the Remote GNE Connected by the Router
The T2000 cannot log in to the remote GNE connected by the router.
5.19 MC-A21 An Interconnection Failure between the WDM and SDH Equipment
Inconsistent wavelength range causes an interconnection failure between the WDM and SDH
equipment.
5.20 MC-A22 NE ESC Communication Interrupted Because of the Closure of the OTU Laser
NE ESC communication interrupted because of the closure of the OTU laser.
5.21 MC-A23 When the OTU Board Accesses Light, the Laser at Output End is Disabled
When the OTU board accesses light, the laser at output end is disabled.
5.22 MC-A24 Low Optical Power on the Client Side of the OTU Board Leads to R_LOS Alarm
on the Board
Low optical power on the client side of the OTU board leads to R_LOS alarm on the board.
5.23 MC-A25 The System Indicates that the Channel Number Is Illegal
In the case of the deployment of the OptiX OSN 6800, the system indicates that the channel
number is illegal when the electrical cross-connect services are configured on the TQM board.
5.24 MC-A26 The Centralized Power Distribution Cabinet Endures Power Failure
The external power cables of the DC power distribution box in the OSN 6800 are connected
incorrectly. When one channel in the centralized power distribution cabinet endures a failure,
power failure occurs in two subracks.
5.25 MC-A27 Should the Nominal Gain of the OAU1 Board Be Re-set?
Should the nominal gain of the OAU1 board in the OSN 6800 be re-set after the type of the
DCM between TDC and RDC is changed?

Platform
5.26 MC-A28 The LSX Board Reports the OTUk_LOF Alarm

OptiX OSN 6800, When accessing 10GE LAN services, the LSX board reports the OTUk_LOF
alarm because of the inconsistency in the settings of WDM-side rate.
5.27 MC-A29 On the OptiX OSN 6800, End-to-end GE Services Cannot Be Created
On the OptiX OSN 6800, end-to-end GE services cannot be created.
5.28 MC-A30 LDG Board of Metro 6100 Equipment Reports the INBADOCTS_OVER Alarm
LDG board of Metro 6100 equipment reports the INBADOCTS_OVER alarm.
5.29 MC-A31 Wrong Calculation for Dispersion in One DWDM Project
Wrong calculation for dispersion in OptiX Metro 6100, which leads to B1, B2 and B3 errors. In
addition, the R_LOF alarm is detected on SDH analyzer sometimes.
5.30 MC-A32 When OptiX BWS 1600G SCC Board Is Replaced with the SCE, TC2 Board
Reports BD_STATUS Alarm
When OptiX BWS 1600G SCC board is replaced with the SCE, TC2 board reports BD_STATUS
alarm.
5.31 MC-A33 Remotely Checking the Correctness of the DCM Installation
Remotely checking the correctness of the DCM installation.
5.32 MC-A34 The Subrack Alarm Cannot be Uploaded to the Alarm Indicator in the Cabinet
OptiX BWS 1600G PMU board being down; subrack alarm cannot be uploaded to the alarm
indicator in the cabinet.
5.33 MC-A35 LWM Output Optical Power Is Unstable upon Forced Light Generation
LWM output optical power is unstable upon forced light generation.
5.34 MC-A36 The OTU in the OptiX BWS 1600G Reports IN_PWR_LOW Alarm
The OTU in the OptiX BWS 1600G reports IN_PWR_LOW alarm.
5.35 MC-A37 The LWFS in the OptiX BWS 1600G Transiently Reports FEC_LOF Alarm
OptiX BWS 1600G, the LWFS in the OptiX BWS 1600G transiently reports FEC_LOF alarm.
5.36 MC-A38 The Service Is Interrupted After the Protection Is Triggered
The service in the working channel is interrupted after the inter-board wavelength protection is
triggered, because the 1+1 inter-board protection is mistakenly configured on the OptiX BWS
1600G.
5.37 MC-A39 There Are Errors in the Setting of the Meter ONT-30
There are errors in the setting of the Meter ONT-30, Which causes optical signal-to-noise ratio
test failure.
5.38 MC-A40 Over Compensation Causes Very High Bit Error Rate of the Short Waves After
Correction
Over compensation causes very high bit error rate of the short waves after correction.
5.39 MC-A41 Unsuccessful 1: N Protection Subnet Search
Unsuccessful 1: N protection subnet search.
5.40 MC-A42 A Fault of the PMU for the OptiX BWS 1600G Results In an Orderwire Ringing
Failure
A fault of the PMU for the OptiX BWS 1600G results in an orderwire ringing failure.
5.41 MC-A43 Too High Insertion Loss Between TDC and RDC of the E3OAUC01C
For OptiX BWS 1600G, too high insertion loss between TDC and RDC of the E3OAUC01C
causes the failure of gain setting.
5.42 MC-A44 Bit Errors Generated in the Services

Platform
Bit errors generated in the services when the LWFS board of the OptiX BWS 1600G interworks
with the router of company A.
5.43 MC-A45 During the deployment of Raman, the OPU board reports MUT_LOS
During the deployment of Raman, the OPU board reports MUT_LOS
5.44 MC-A46 POWERALM Alarm in OptiX BWS 1600G Caused by Switching off the Upper
Subrack
POWERALM alarm in OptiX BWS 1600G caused by switching off the upper subrack.
5.45 MC-A47 The CRC4_CROSSTR Alarm Is Generated Because of Low Fiber Quality
The CRC4_CROSSTR is generated because of low fiber quality.
5.46 MC-A48 The T2000 Cannot Search the Wavelength Trail
The T2000 cannot search the wavelength trail because engineers did not create the OAU fiber
connections between TDC and RDC.
5.47 MC-A49 An Incorrect Setting of CRC Results in an Interconnection Failure
The port of the router from company S is set to the SONET mode. An incorrect setting of CRC
results in an interconnection failure.
5.48 MC-A50 Measure the PMD of an Optical Cable to Determine the Quality of the Optical
Cable
Measure the PMD of an optical cable to determine the quality of the optical cable.
5.49 MC-A52 Faults of End Face of the Fiber Connector Cannot Be Identified
Faults of end face of the fiber connector cannot be identified by using an optical power meter.
5.50 MC-A53 OptiX BWS 1600G Cannot Be Deleted on the T2000
The fiber connections are not deleted completely. Therefore, the WDM equipment on the T2000
is unable to be deleted.
5.51 MC-A54 After the Lasers of the Raman Amplifier Are Disabled, the Optical Power Is
Abnormal
After the lasers of the Raman amplifier are disabled, the optical power is abnormal.
5.52 MC-A55 Improper DCM Distribution Causes Abnormal Service
Improper DCM distribution causes abnormal service of the OptiX BWS 1600G equipment after
the upgrade.
5.53 MC-A56 LWF Board Reports OTU_LOF Alarm
LWF board reports OTU_LOF alarm.
5.54 MC-A57 How to Clear OTU Alarms Because of Unused Ports
How to clear OTU alarms because of unused ports.
5.55 MC-A59 Mismatch of SC2 Models Causes Frequent Reporting of the CRC4_CROSSTR
Alarm
The OptiX BWS 1600G system frequently reports the CRC4_CROSSTR alarm because of the
mismatch of SC2 models.
5.56 MC-A62 The Minimum Optical Power of the SC2 Is Detected As -35 dBm
Because the fibers or the fiber jumpers are in fault, the minimum optical power of the SC2 is
detected as -35 dBm.
5.57 MC-A63 Bit Errors Occur in a DWDM 10G Network Due to the Uncorrect PMD
The bit errors occur in a DWDM 10G network due to the uncorrect PMD.
5.58 MC-A64 Many BD_STATUS Alarms Occur Due to the ECC Storm
Many BD_STATUS alarms occur due to the ECC storm.

Platform
5.59 MC-A65 The Gain of the RPC Board Cannot Exceed 10 dB Due to Excessively High
Attenuation of Flange
The gain of the RPC board cannot exceed 10 dB due to excessively high attenuation of flange.
5.60 MC-A66 The Received Optical Power of Downstream Stations Is not Flat
The received optical power of downstream stations is not flat because the designed pass-through
wavelengths are not connected.
5.61 MC-A67 The GE Port on the Client Side Reports LINK_DOWN Alarm
Due to the auto negotiation, the GE port reports LINK_DOWN alarm when FDG connects to a
GE port of Cisco 12410 router on the client side.
5.62 MC-A68 OTU Boards Report the IN_PWR_LOW Alarm Due to Wavelength Wander
The wavelength wander of an OTU board causes the downstream OTU boards to report the
IN_PWR_LOW alarm.
5.63 MC-A69 Shutdown of the RPC Laser Interrupts SDH-Layer Services in a DWDM Network
The shutdown of the RPC laser interrupts SDH-layer services in a DWDM network.
5.64 MC-A71 Excessive Attenuation Results in That the Gain of the E3OAU Cannot Be Set
The excessive attenuation between the TDC and RDC ports results in that the gain of the E3OAU
cannot be set.
5.65 MC-A72 The OTU_LOF Alarm Reported in the LWC1 Due to Wrong Regenerator Board
The OTU_LOF alarm reported in the LWC1 is caused by the Wrong Regenerator Board in the
BWS1600G.
5.66 MC-A74 The FDG Reports the T_DATA_LOST and R_DATA_LOST Alarms
The FDG reports the T_DATA_LOST and R_DATA_LOST alarms because of the fault
configuration of the client GE interface.
5.67 MC-A75 Bandwidth Decreases and Service Rate Becomes Lower Due to Improper Setting
The improper setting of the interconnected FC switch results in that the bandwidth of the LOG
board decreases and the service rate becomes lower.
5.68 MC-A76 The PMU Cannot Work Normally
The PMU cannot work normally because the communication setting of the PMU is improper.
5.69 MC-A77 Improper Configuration of Protocol Channels Results in a Failure of the ALC to
Start
The improper configuration of protocol channels results in a failure of the ALC to start.
5.70 MC-A78 When the IPA Is Set or Deleted, the OAU Alarm Threshold Changes Due to
Version Features
When the IPA is set or deleted, the OAU alarm threshold changes due to version features.
5.71 MC-A79 The MCA Board Reports an Execution Failure
The MCA board reports an execution failure if the wavelength is not set to the monitor status.
5.72 MC-A80 Intermittent BEFFEC_EXC Alarm at IN/OUT optical interfaces on LWF board
The intermittent BEFFEC_EXC alarm is reported at IN/OUT optical interfaces on the LWF
board housed in slot 10 of one surack NE.
5.73 MC-A81 The ALC Cannot Run
The ALC cannot run.
5.74 MC-A82 Analysis of the POWER_FAIL Alarm on the OptiX OSN 6800 and Solution
The SCC board reports the POWER_FAIL alarm due to a battery failure.
5.75 MC-A83 The OptiX OSN 6800 Is Not Reachable When the NE IP Is Modified

Platform
The OptiX OSN 6800 is not reachable when the NE IP is modified.

5.76 MC-A84 Maximal packet length setting of the OptiX OSN 6800 Causes the Abnormal
Service
The LQMD board of the OptiX OSN 6800 connects to the router C4507 of C company. The
ordinary ADSL service is fine but the enterprise ADSL service has anomalies.
5.77 MC-A85 SWDL_CHGMNG_NOMATCH Alarm Is Reported
The SCC board in the slave subrack of OptiX OSN 6800 is identical with the NE software
version. After power-on, the SWDL_CHGMNG_NOMATCH alarm is reported
5.78 MC-A86 Inserting, Removing, and Resetting Operations Affect NG WDM Products
How do inserting, removing, and resetting operations affect the NE software version and
configuration of NG WDM products.
5.79 MC-A87 SWDL_CHGMNG_NOMATCH Alarm Is Reported
Though the SCC of the OptiX OSN 3800 and OptiX OSN 6800 is not replaced, an alarm
(SWDL_CHGMNG_NOMATCH) is reported, indicating replacement of the SCC.
5.80 MC-A88 Difference in BER Reported by the OTU Board and Test Instrument
Difference test instrument cause difference in BER reported by the OTU board and test
instrument.
5.81 MC-A89 Two Different Power Supplies for the OptiX Metro 6100
Two different power supplies can be provided by the OptiX Metro 6100.
5.82 MC-A90 The Incorrect Configuration of DWC Leads To Abnormal Optical Power and
Service Interruption
The incorrect configuration of DWC leads to abnormal optical power and service interruption.
5.83 MC-A91 Creation of Intra-Board Wavelength Protection on the LDG Fails
The creation of intra-board wavelength protection on the LDG fails due to the configured
attributes of the board.
5.84 MC-A92 How to Handle the J0_MM Alarm on the LWM
How to handle the J0_MM alarm on the LWM.
5.85 MC-A93: The Input Optical Power of the OTU Board Is Abnormal Due to a Fault of the
OPU Board
The input optical power of the OTU board is abnormal due to a fault of the OPU board.
5.86 MC-A94: The WXCP Protection Configured for the LOG Board Is Invalid
The WXCP protection configured for the LOG board is invalid due to the configured attributes
of the board.
5.87 MC-A95: The SC2 Board Reports the CRC4_CROSSTR Alarm
The SC2 board reports the CRC4_CROSSTR alarm due to the board faulty.
5.88 MC-A96: Packet Loss Occurs in Ethernet Service Testing of the L4G Board
The packet loss occurs in Ethernet service testing of the L4G board due to the different equipment
and meters.
5.89 MC-A97: The Optical Amplifier Reports the IN_PWR_HIGH Alarm Because of Optical
Power Reflection
The optical amplifier reports the IN_PWR_HIGH alarm because of optical power reflection.
5.90 MC-A98: The Protection Switching Times Out Severely
The protection switching time is out severely in the event of wavelength protection between the
SCS boards of the OptiX Metro 6100 because of the wrong test method.

Platform
5.91 MC-A99: The PMU Reports the THUNDERALM Alarm

The PMU reports the THUNDERALM alarm.
5.92 MC-A100: The FDG Board Reports the R_DATA_LOST Alarm in the Early Morning
The FDG board reports the R_DATA_LOST alarm in the early morning because the traffic
volume is light.
5.93 MC-A101: The Wavelength Is Unstable or Changed Due to Optical Power Variation
The wavelength is unstable or changed due to optical power variation.
5.94 MC-A102: The LBE, LDG and LQG Boards Report the LINK_ERR or LINK_STATUS
Alarm
The LBE, LDG and LQG boards report the LINK_ERR or LINK_STATUS alarm.
5.95 MC-A103: How to Configure the Dual Feed and Selective Receiving Boards
How to configure the dual feed and selective receiving boards in the case of a unidirectional
WDM link.
5.96 MC-A104: No Optical Power Is Output on the WDM Side Due to Incorrect Configuration
No optical power is output on the WDM side of the LWM board due to incorrect configuration
of the SFP module on the client side.
5.97 MC-A105: Line Reflection Leads to Inaccurate BER Detection of the SSC6LWX Board
The line reflection leads to the inaccurate BER detection of the SSC6LWX board.
5.98 MC-A106: OptiX Metro 6100 Reports the PWR_MAJ_ALM Alarm
When supplied with both -48 V and -60 V power, the OptiX Metro 6100 reports the
PWR_MAJ_ALM alarm.
5.99 MC-A107: The Cross-Connection Function of the Subrack Fails
The cross-connection function between two LOG or ELOGS boards on the left and right sides
of the subrack fails because the hardware bus is restricted.
5.100 MC-A108: How to Select Test Meters on Site When Testing OTU Boards of the Data
Type
How to select test meters on site when testing OTU boards of the data type.

Platform
5.1 MC-A1 The OTU_LOF Alarm is Reporting on the OTU

at the Downstream Station
The TF alarm on the OTU at the upstream station results in the OTU_LOF alarm on the OTU
at the downstream station.
Product
OptiX BWS 1600G
Fault Type
OTU_LOF
R_LOS
Symptom
In a network consisting of the OptiX BWS 1600G systems, the signal flow at stations is as
follows: A→B→C→D. A, C, and D are OTM stations and B is an OLA station. The LWFS
board is configured at stations A and D. The TMRS board is configured at station C.
An LWFS board at station A reports the TF alarm and the transmit optical power on the WDM
side decreases by 10 dB approximately. The corresponding TMRS board at station C reports the
OTU_LOF alarm on the WDM side. The transmit optical power of the TMRS is -60 dBm. The
corresponding LWFS at station D reports the R_LOS alarm.
Cause Analysis
l The TMRS board at station C is faulty.
l The LWFS board at station A is faulty.
Procedure
Step 1 Replace the TMRS at station C. The problem persists and the transmit optical power of the
TMRS remains -60 dBm.
Step 2 Replace the LWFS at station A. Then, the problem is solved.
----End
Reference Information
None.

Platform
5.2 MC-A2 The E1V40 Board Reports the POWER_FAIL and

The E1V40 board reports the POWER_FAIL and MODULE_TEMP_OVER alarms when the
primary power supply module is faulty.
Product
OptiX BWS 1600G
Fault Type
POWER_FAIL
MODULE_TEMP_OVER
Symptom
The E1V40 at an OEQ station reports the POWER_FAIL and MODULE_TEMP_OVER alarms
when the input/output optical power and the services are normal.
Cause Analysis
l The power supply module is faulty.
l The board is faulty and thus the board misreports the alarm.
Procedure
Step 1 Perform a warm reset on the board. The alarms persist.
Step 2 Remove the V40 and insert it into another slot. The alarms persist.
Step 3 The V40 has backup power supply. When the primary power supply is faulty, the board remains
in the normal working state and the services are not affected. There are, however, potential
problems. Hence, replace the board.
Step 4 After the board is replace, the alarms are cleared and the problem is solved.
----End
None.
5.3 MC-A3 The FDG Board Reports the ALM_DATA_RLOS

Alarm in the Early Morning
The FDG board reports the ALM_DATA_RLOS alarm in the early morning when the traffic
volume is light.

Platform
Product
OptiX Metro 6100
Fault Type
ALM_DATA_RLOS
Ethernet Service
Equipment Interconnection
Symptom
The FDG board in the OptiX Metro 6100 keeps reporting the ALM_DATA_RLOS alarm in the
early morning. The line and the data equipment connecting to the FDG board, however, are
normal.
Cause Analysis
The FDG board detects the services every five seconds. If the FDG does not receive data packets
during the detection, the FDG reports the ALM_DATA_RLOS alarm. The alarm does not mean
that the services are not available. No alarm is generated in the line during the daytime and the
services are normal. The alarm is generated only in the early morning. Hence, the alarm is related
to the truth that the traffic volume is light. In the early morning, no data packets are transmitted
normally when the FDG detects the services. Hence, the ALM_DATA_RLOS alarm is reported.
Procedure
Step 1 Suppress the alarm after making sure that the services are normal.
----End
The data boards, such as LDG, also have the similar problem. Solve the problem in a similar
way.
5.4 MC-A4 The LOG Board Fails to Interwork With the FDG
Board on the Client Sides.
The LOG board fails to interwork with the FDG board on the client sides because the loss in the
fiber jumper is extremely large.
Product
OptiX Metro 6100
OptiX BWS 1600G
Fault Type

Platform
R_LOS
LINK_ERR
LINK_STATUS
Ethernet Service
Symptom
There are two carriers. One carrier uses the OptiX Metro 6100 and the other carrier uses the
OptiX BWS 1600G. The LOG board in the OptiX Metro 6100 needs to interwork with the FDG
board in the OptiX BWS 1600G on the client sides. The two NEs are in the same equipment
room. After the two boards are connected by using fibers, the two boards become abnormal and
the interworking fails. The LOG board reports the R_LOS alarm on the client side. The input
optical power is -60 dBm and the optical power meter indicates that there is input light.
Cause Analysis
l The service configuration on the LOG board is incorrect.
l The input or output optical power of the LOG board is abnormal.
l There are errors in the fiber connections or the loss in the fiber jumper is extremely large.
Procedure
Step 1 Query the auto-negotiation mode of the LOG and FDG boards. The two boards are in the non-
autonegotiation mode.
Step 2 Query the cross-connections on the LOG. The board is configured with eight pairs of pass-
through cross-connections.
Step 3 Query the type of the service that is configured on the client side of the LOG. The service type
is GE.
Step 4 Query the performance data of the LOG. The input optical power on the client side is -60 dBm.
Step 5 Use an optical power meter to measure the input optical power again. The measured value is -19
dBm.
Step 6 Check the fiber connections. It is found that a section of fiber jumper is abnormal. Replace the
fiber jumper and increase the input optical power on the client side of the LOG to -9 dBm. Then,
the alarm is cleared and the interworking is successful.
----End
l The receiver sensitivity of the client-side optical module of the LOG is -19 dBm. When the
optical power is smaller than -19 dBm, the board is unable to detect the light and thus reports
the R_LOS alarm.
l It is recommended that you choose the non-autonegotiation mode for the interconnected
ports unless otherwise specified.

Platform
l If the client-side optical interfaces of two LOG boards need to be interconnected, use the
GE ADM feature to enable the service pass-through by using the inter-board cross-
connections.
5.5 MC-A5 The LQG Board Reports the ALM_DATA_RLOS

and ALM_DATA_TLOS Alarms Transiently
The LQG board reports the ALM_DATA_RLOS and ALM_DATA_TLOS alarms transiently
because the channel does not carry services.
Product
OptiX Metro 6100
Fault Type
Transient Interruption
ALM_DATA_RLOS
ALM_DATA_TLOS
Ethernet Service
Protection
Symptom
The working and protection LQG boards are configured with the WXCP protection to enable
the channel protection. The transmit end of the working path on the WDM side is #151-11-
LQG-1 (#151 is the name of the NE, 11 is the slot of the board, LQG is the name of the board,
and 1 is the optical interface of the board) and the receive end is #161-2-LQG-1. The transmit
end of the protection path is #151-10-LQG-1. Then, the services in the protection path pass
through #150, #157, #158, and #160 NEs and arrive at #161-3-LQG-1. Two GE services
(#151-11-LQG-3/4←→#161-2-LQG-3/4) are configured. The fourth optical interfaces on the
working and protection LQG boards at #151 and #161 NEs keep reports the
ALM_DATA_RLOS and ALM_DATA_TLOS transiently.
Cause Analysis
The ALM_DATA_RLOS alarm indicates that no service is accessed. The ALM_DATA_TLOS
alarm indicates that the corresponding channel on the WDM side does not carry services. The
ALM_DATA_RLOS alarm is generated at the opposite station when no actual service is
accessed at the local station. The channel, however, is actually carry services according to the
feedback from the customer. The LQG-4 and the Alcatel router are checked for the interworking
problems. Then, use the ping command to substitute the services. The ALM_DATA_RLOS and
ALM_DATA_TLOS alarms are no longer reported at the fourth optical interfaces on the working
and protection LQGs at #151 and #161 NEs. It indicates that the channel is connected physically
but does not carry actual services. Hence, the fourth optical interfaces on the working and
protection LQG boards at #151 and #161 NEs keep reports the ALM_DATA_RLOS and
ALM_DATA_TLOS transiently.

Platform
Procedure
Step 1 Suppress the alarms.
----End
None.
5.6 MC-A6 The LDG Board Keeps Reporting the

ALM_DATA_TLOS and ALM_DATA_RLOS Alarms
Transiently
The LDG board keeps reporting the ALM_DATA_TLOS and ALM_DATA_RLOS alarms
transiently.
Product
OptiX Metro 6100
OptiX Metro 6040
Fault Type
ALM_DATA_TLOS
ALM_DATA_RLOS
Ethernet Service
Symptom
In a new project, the OptiX Metro 6100 and OptiX Metro 6040 are used to form a point-to-point
network. The NEs connect to data equipment by using the LDG and LWX boards. Many LDG
boards keep reporting the ALM_DATA_TLOS and ALM_DATA_RLOS alarms transiently.
No anomaly, however, is found in the data test and the phone test. The LWX board is normal.
Cause Analysis
Co-operation problem between the router and the board
Procedure
Step 1 When no service is configured, the router sends the ARP packets periodically. The LDG board
reports the ALM_DATA_TLOS and ALM_DATA_RLOS alarms transiently after the LDG
detects the ARP packets. The alarms are the warnings that are reported by the data board. You

Platform
can suppress these two alarms. If the alarms are not suppressed, the alarms clear automatically
after the service is configured on the boards.
----End
None.
5.7 MC-A7 The R_SLIP Alarm Is Generated Because of

Improper Fiber Connections on the OSC Board
The R_SLIP alarm is generated because of improper fiber connections on the OSC board.
Product
OptiX BWS 1600G
Fault Type
R_SLIP
Symptom
A backbone network uses the OptiX BWS 1600G. The network construction is divided into two
phases. In the first phase, the following four stations are constructed to form a chain network:
station A (OTM), station B (OTM1, OTM2), station C (OTM1, OTM2), and station D (OTM).
In the second phase, the following three stations are constructed to form a chain network: station
C (OTM3), station E (OLA), and station F (OTM). After the first phase is complete, the network
operates normally and no abnormal alarms and performance events are reported. After the second
phase is complete, the OSC boards at stations C, E, and F report the R_SLIP alarm transiently.
The R_SLIP alarm can be found only in the history alarms.
Cause Analysis
The R_SLIP alarm indicates that the slip is received. The possible causes are as follows:
l The clock synchronization is lost.

l The attenuation in the optical path is extremely large.
l The receive optical power is overloaded.
Procedure
Step 1 Check the alarms in the network. There are no alarms such as R_LOS or R_LOF. During the
commissioning, the receive optical power and transmit optical power of the OSC are normal.
The R_SLIP alarm, however, persists. Hence, the alarm is not related to the optical power.
Step 2 Check the working clock source of the SCC board at each station. It is found that there are two
clock sources in the network. One clock source is station A and the other is station F. The clock
priorities of the two stations are local,0xff,0xff.

Platform
Step 3 Change the clock priority of station F to clk6,local,0xff. In this case, the clock priorities of all
stations except for station A are clk6,local,0xff. The R_SLIP alarm, however, persists at stations
C, E, and F. This indicates that the clock of stations C, E, and F is not synchronous with the
clock of station A.
Step 4 Check the fiber connections. It is found that port 1 of the SC2 board in the OTM3 subrack at
station C is connected to port 2 of the SC2 board at station E, and port 1 of the SC2 board at
station E is connected to the SC1 board at station C. By default, the board sends the clock in line
1 (that is, port 1 of the SC2) back to the SCC board. Hence, the clock at stations E and F traces
each other and station C traces station E. Then, the slip occurs.
Step 5 According to the fiber connection rules of the BWS 1600G, port 1 of the OSC should be
connected to the upstream NE and port 2 to the downstream NE. Hence, the fiber connections
at stations C and E are improper.
Step 6 You can correct the fiber connections to solve this problem. The distance between the two
stations, however, is very long. Hence, it is impossible to correct the fiber connections. Modify
the configuration of the clock that is sent back to the SCC at stations C and E. Make sure that
the SC2 boards at stations C and E sends the east clock back to the SCC. Then, observe the
network for a period of time. The R_SLIP alarm is cleared.
----End
l In the DWDM network, clock is the key factor that ensures the synchronous communication
between the SC1/SC2 and the SCC. There is only one clock source at the source end in the
entire network. The communication between the OSC board at other stations and the SCC
must be synchronous with the clock at the source end. Otherwise, the R_SLIP alarm is
generated.
l During the networking commissioning, port 1 of the OSC is connected to the upstream NE
and port 2 is connected to the downstream NE normally. By default, the OSC sends the
line clock at port 1 to the SCC. In a certain situation, when port 2 of the OSC is connected
to the upstream NE and port 1 is connected to the downstream NE, you need to configure
the east clock as the clock that is sent back to the SCC manually. It is recommended,
however, that you do not change the clock source that the OSC sends back the the SCC.
5.8 MC-A8 The TN11OAU101 at the Transmit End Reports

the MUT_LOS Alarm
The TN11OAU101 at the transmit end reports the MUT_LOS alarm because the optical
attenuation of the M40V board is not adjusted.
Product
OptiX OSN 6800
Fault Type
MUT_LOS
Optical Power Management

Platform
Symptom
At the ROADM station consisting of the OptiX OSN 6800 V1R2, the signal flow in the
wavelength add direction is as follows: L4G->M40V->WSM9->OAU->FIU. After the internal
logical fiber connections are complete at the NE, create the single-station optical cross-
connections and select the automatic optical power adjustment function. Then, the T2000
prompts that the creation is successful. The OAU board, however, reports the MUT_LOS alarm.
No alarm is generated on other boards.
Cause Analysis
The OPA supports only the WSD9, WSM9, RMU9, and ROAM boards. In the case of other
boards supporting the setting of attenuation (VA1/M40V/D40V), the OPA does not set the
attenuation. Thus, you need to set the attenuation. During the calculation, OPA regards the
attenuation as zero (0) and the changes in the attenuation of the boards does not trigger the re-
adjustment by the OPA.
By default, the VA1, M40V, and D40V take the maximum attenuation for each channel. Hence,
when the OPA function is started, the light from the L4G does not enter the OAU after passing
the M40V because the attenuator of the M40V is not adjusted.
Procedure
Step 1 Adjust the M40V on the T2000 and set the attenuation value of the corresponding channel to 0
dB. Then, the MUT_LOS alarm is cleared.
----End
In certain scenarios, the attenuation of certain channels of the M40V, D40V, VA1, and VA4
boards needs to be set manually. At the station that is configured with the M40V, D40V, VA1,
or VA4, set the attenuation value of the optical channel of the board manually to ensure the
availability of the optical channel. This is very important for the ASON feature to trigger
rerouting in the WDM network.
5.9 MC-A11 The SSE3LWF Board Reports the OTU_LOF

Alarm When Interworking with the SSE1TMR
The SSE3LWF board reports the OTU_LOF alarm when interworking with the SSE1TMR.
Product
OptiX BWS 1600G
Fault Type
OTU_LOF

Platform
Symptom
L T L
W M W
F R F
A B C
The SSE1TMR board at station B is forced to emit light during the commissioning. Then, the
SSE3LWF board at station C reports the OTU_LOF alarm. Perform an inloop on the WDM side
of the SSE3LWF at station C. The services are normal. The adjacent channels are also normal.
In addition, it is ensured that the alarm is not caused by dispersion problem. The OTU_LOF
alarm persists.
Cause Analysis
The SSE1TMR supports AFEC and FEC encoding/decoding modes and the FEC auto-adaptation
function. The board selects the FEC encoding/decoding mode automatically according to the
FEC mode of the input signals. No manual setting is required.
When the SSE1TMR reports R_LOS and is forced to emit light, note that the FEC mode when
the board inserts ODU_AIS is the FEC mode that the board tries to perform adaptation at the
last time. If the FEC mode of the TMR is not the same as the FEC mode of the downstream
LWF, the LWF reports the OTU_LOF alarm. If the FEC mode of the TMR is the same as the
FEC mode of the downstream LWF, the downstream LWF reports the ODU_AIS alarm.
Procedure
Step 1 Enable the WDM-side laser of the SSE3LWF at station A and make sure that the input optical
power of the SSE1TMR is normal. The SSE1TMR automatically selects the proper FEC mode.
Then, the OTU_LOF on the downstream board is cleared.
----End
None.
5.10 MC-A12 Certain Boards Report the TF Alarm

Transiently
Certain boards report the TF alarm transiently because the FAN speed is low and the board
temperature reaches 60 degrees centigrade.
Product
OptiX BWS 1600G

Platform
Fault Type
TF
Symptom
The LWF board in the BWS 1600G reports the TF alarm transiently. Reseat the board and the
alarm is cleared. The alarm, however, is generated again several days later. Query the board
performance by using the T2000. It is found that the temperature of slots 1, 2, 11, and 12 is
extremely high and reaches 60 degrees centigrade. Then, check the fan status. The fan is working
normally. Check the PMU performance. The ambient temperature is 35 degrees centigrade.
Cause Analysis
l The NE temperature is very high because the ambient temperature is extremely high.
l The laser of the board is aged.
l The fan speed is very low and thus the temperature in certain areas in the NE is very high.
Procedure
Step 1 Measure the ambient temperature. The ambient temperature is 25 degrees centigrade, which is
normal.
Step 2 Measure the NE temperature. The temperature in the two sides of the NE is very high and the
temperature in the middle area is normal.
Step 3 Check the fan speed. It is found that the air distribution on the right and left sides is inadequate.
Step 4 Replace the fan board. The board temperature becomes normal and the TF alarm is cleared.
----End
None.
5.11 MD-A13 Bit Error Alarm Is Generated When Optical

Power Gets Close to the Threshold
Bit error alarm is generated when optical power gets close to the threshold.
Product
OptiX BWS 1600G
Fault Type
Bit Errors
Optical Power Abnormity
BEFFEC_EXC

Platform
Symptom
Station A and B form an OTM with station C functioning as an OLA in between. The BWS
1600G is used at each station and the LWF is used as the OTU board.
The LWF at station A in slot 3 keeps reports the BEFFEC_EXC alarm transiently. Query the
WDM performance of the board. It is found that there are a lot of FEC correction events (the
number of corrected bytes is larger than 100 thousand).
Cause Analysis
l The optical power is abnormal.
l The fiber connector is dirty or is connected improperly.
l The dispersion is too high, or signal-to-noise ratio is too low.
Procedure
Step 1 The board reports the alarm indicating that excessive bit errors are detected. Query the optical
power of the board. The input optical power on the WDM side is -6.9 dBm, which is within the
normal range.
Step 2 Perform the following steps to rectify the possible fiber faults. Check the fiber jumpers and clean
the fiber connectors at stations A and B. There is no obvious change in the performance and the
alarm persists.
Step 3 Query the performance of other LWF boards at station A. There are FEC correction events in
the three LWF boards in slots 4-6 and the BER before FEC correction is very high.
Step 4 Query the optical power of all boards at station A. The input optical power on the WDM side
of every LWF board is about -7 dBm (slightly higher than -7 dBm). Query the threshold of the
input optical power at the IN interface of the board by using the T2000. The threshold is -2.0
dBm. According the the optical power adjustment principle (plus 3 minus 5), the input optical
power must be 5 dBm smaller than the receiver overload. The input optical power of the OTU
at station A is close to the threshold but not reach the value that triggers an optical power alarm.
The bit errors may be generated because the optical power is slightly high.
Step 5 The optical power of every board is slightly high. In this case, you can adjust the optical power
by decreasing the gain of the OAU board. Query the gain of the OAU at station A. The gain is
close to the lower limit. Decrease the gain of the OAU at station C by using the T2000. Then,
query the optical power of every LWF at station A. The input optical power at the IN interface
is about -9 dBm. Observe the performance. The number of error correction events decrease
dramatically and the LWF in slot 3 does not report the alarm any more.
----End
The OAU supports the gain adjustment by software, which can be set by using the T2000. The
operation is very easy.
5.12 MC-A14 The LWF Board Reports R_LOS

The LWF board reports R_LOS because the incorrect fiber type leads to dispersion over-
compensation.

Platform
Product
OptiX BWS 1600G
Fault Type
R_LOS
Symptom
In a national backbone WDM network, the OptiX BWS 1600G is used. A, B, C, and D are the
OTM, OLA, OADM, and OTM stations respectively. The distance between A, B, C, and D is
more than 100 km. The 120 km dispersion compensation module (DCM) is added between C
and D. A 100 km DCM is configured at the transmit end and a 20 km is configured at the receive
end. The OTU boards that are configured at stations A, C, and D are the LWM, LWF, and LQG.
The OTU is forced to emit light. After the system commissioning is complete, the LWF boards
at stations A, C, and D report R_LOS on the WDM side.
Cause Analysis
l The per-channel optical power is very low or no light is received.
l The multiplexer/demultiplexer device is faulty, which causes wavelength drop.
l The LWF board is faulty.
l The OSNR does not meet the design requirements.
l There is problem in the dispersion.
Procedure
Step 1 The LWF boards at stations A, C, and D report R_LOS. Hence, the cause cannot lie in a certain
board. Use an optical power meter to measure the optical power at the IN interface of every
LWM board. The optical power is about -8 dBm, which meets the requirement. Hence, the
problem is not caused by the LWF, D40, M40, or MR2.
Step 2 In the same system, the problem does not occur on the LWM and LQG at 2.5 Gbit/s. Because
the board at 10 Gbit/s has different OSNR and dispersion requirements from the board at 2.5
Gbit/s, the problem must be caused by a dispersion problem.
Step 3 Remove the 20 km DCM at the receive end at station D. The alarm persists. Then, remove the
100 km DCM at the transmit end at station D, the alarm that is reported at station C changes to
R_LOF. Remove the DCM at station C, the alarms on the corresponding LWFs at stations A
and D change to R_LOF. Hence, the problem lies in the dispersion. Remove the 100 km DCM
and the R_LOF alarm persists. The dispersion to be compensated that is obtained during the
design phase cannot be more than 100 km. Check the fibers that are used on site. The G.655
fibers are used. The G.652 fibers, however, are used during the design phase. Hence, replace the
fibers between station A and station D. Then, the R_LOS on the WDM side of the LWF is cleared
and the problem is solved.
----End
None.

Platform
5.13 MC-A15 The Downstream Optical Amplifier Board

Does Not Report R_LOS
upstream optical amplifier board and the FIU board is interrupted.
Product
OptiX Metro 6100
Fault Type
R_LOS
Symptom
upstream optical amplifier board and the FIU board is interrupted because of fiber jumper failure.
Cause Analysis
OA OA
F F
I I
S U U S
C C
2 2
The transmit optical power of the SC2 ranges from 0 dBm to -4 dBm. The threshold for the
downstream optical amplifier board to report R_LOS is -35 dBm. Assume that the transmit
optical power of the upstream SC2 is -2 dBm. When the loss on the line side is no less than 19.5
dB (35-2-1.5-12, where 1.5 is the insertion loss of the FIU and 12 is the isolation of the FIU),
the downstream optical amplifier board reports the R_LOS alarm.
When the WDM equipment is used in a MAN, the line loss is normally smaller than 19.5 dB.
In this case, the downstream optical amplifier board does not report the R_LOS alarm when
there is a fiber cut between the upstream optical amplifier board and the FIU.
Procedure
Step 1 Check the output optical power of the upstream optical amplifier board. The output optical power
is within the normal range.
Step 2 Check the input optical power of the upstream FIU. The input optical power is very low. This
indicates that the fiber between the optical amplifier board and the FIU is faulty.

Platform
Step 3 Replace the fiber between the upstream optical amplifier board and the FIU. Then, the services
become normal.
----End
None.
5.14 MC-A16 LOF/OOF Is Reported in the 24-Hour Bit Error

Test Because the Line Fiber Loss Is Very Large
LOF/OOF is reported in the 24-hour bit error test because the line fiber loss is very large.
Product
OptiX BWS 1600G
Fault Type
Bit Error
R_LOF
R_OOF
B1_SD
Symptom
In the OptiX BWS 1600G that is newly deployed, a meter is used to perform the 24-hour bit
error test after the system commissioning is complete. Then, the OTU boards of the 14
wavelengths at stations A and B report R_LOF and R_OOF at the IN interface on the WDM
side and the RX interface on the client side at the same time. In addition, the B1_SD alarm is
reported.
Cause Analysis
There are faults in the line. For example, the fiber loss is very high or the fiber jumper between
the equipment and the ODF is faulty.
Procedure
Step 1 Check the loss of the line fiber. The line loss between stations A and B is normal. Hence, the
problem is not caused by high fiber loss.
Step 2 On the ODF at station A, measure the optical power of the signals from station B. Then, check
whether the loss of the two fiber jumpers between the ODF and the equipment is normal on the
equipment side of station A. The loss of the two fiber jumpers (50 m) is almost the same.
Step 3 On the ODF at station B, measure the optical power of the signals from station A. Then, check
whether the loss of the two fiber jumpers between the ODF and the equipment is normal on the
equipment side of station B. The loss of the two fiber jumpers (50 m) is different. The loss of

Platform
one fiber jumper is smaller than 0.5 dB and the loss of the other fiber jumper reaches 2.3 dB.
Hence, the bit errors are generated because the loss of the fiber jumper is very high.
Step 4 Replace and re-route the two fiber jumpers at station B. Connect a meter to perform the 24-hour
bit error test again. No bit error is generated.
----End
l When routing the fiber jumpers, make sure that the fiber jumpers are not bent so that the
fiber jumpers will not be damaged.
l Note the loss of the tested line during the system commissioning, including the loss of the
fiber jumper between the ODF and the equipment. This prevents the possible problems
caused by the loss.
5.15 MC-A17 The LQG Reports ALM_DATA_RLOS and

ALM_DATA_TLOS Alarms
The LQG reports ALM_DATA_RLOS and ALM_DATA_TLOS alarms in the corresponding
channel because of wavelength mismatch.
Product
OptiX Metro 6100
Fault Type
ALM_DATA_RLOS
ALM_DATA_TLOS
Ethernet Service
Symptom
In a network, the LQG is used to access the client-side services. After the data equipment is
connected, ALM_DATA_RLOS and ALM_DATA_TLOS alarms are reported in the
corresponding channel and the data service is unavailable.
Cause Analysis
l The service configuration of the board is incorrect.
l The fiber jumper is connected improperly or the optical power is abnormal.
l The data equipment does not send data services.
l The interconnected wavelengths mismatch.
Procedure
Step 1 Check the service configuration of the board and the cross-connections. No error is found.

Platform
Step 2 Check the fiber jumper connections. No error is found. The measured optical power is -18 dBm,
which is within the normal range.
Step 3 The data equipment sends data services normally and the self-loop indicates that the data
equipment is normal. Hence, the problem does not lie in the data equipment.
Step 4 Check the wavelengths. The transmit data wavelength on the client side of the LQG is 1310 nm
and the transmit data wavelength of the data equipment is 1550 nm. The wavelengths mismatch
and thus the services are unavailable. Then, the board reports the alarms.
Step 5 Replace the transmit optical module of the data equipment and make sure that the wavelength
is the same as the wavelength of the WDM equipment. Then, the alarm is cleared and the services
are normal.
----End
None.
5.16 MC-A18 TTL Was Abnormal

TTL was abnormal.
Product
OptiX BWS 1600G
Fault Type
Other
Symptom
During the test of X Ethernet ring network consisting of DWDM equipment, it is found that the
ITL value keeps changing, which should be constant and remain at 5 ms, as shown below:
TTL = 5ms
TTL = 113ms
TTL = 223ms
Cause Analysis
l The signals at the remote station is excessively weak.
l The fiber is faulty.
Procedure
Step 1 Clean all the fibers at this station, reconfigure the EPL services, and/or replace the Ethernet
cable. It is found there is little effect.
Step 2 This problem may be caused by excessively weak signals at the remote station. In this case,
make a call to the NOC (the NMS operation center) and ask them to check the optical power at

Platform
the remote station and check whether there are bit errors at the remote station. After confirmation,
it is found that the power at the remote station is excessively low and bit errors in the data exceeds
the permissible range. Thus, it is determined that the attenuation on the line is caused by the
fibers at the remote station.
Step 3 Replace the fibers, the optical power at the remote station is recovered, and the ITL at the remote
station becomes normal, that is, it remains at 5 ms.
----End
Whenever you test a DWDM system, bring the fiber cleansing tool, fiber jumpers, and optical
power meter with you.
Pay attention to the optical power, BER, system performance, and the like system indexes. Power
decrease and bit errors are related to each other. For example, if the power does not meet the
specified requirement, bit errors will be generated; if the fiber jumpers are of poor quality, signal
degrade and a large number of bit errors will occur.
5.17 MC-A19 Use Power Monitoring To Process Problems

On Wavelength Division
Use power monitoring to process problems on wavelength division.
Product
OptiX Metro 6100
Fault Type
IN_PWR_LOW
Symptom
In a network consisting of the OptiX Metro 6100, five stations form a link. Station 1 and 5 are
the service convergence point and configured as the OTM stations. Other stations are configured
as OADM stations and each of them has two GE services with station 1 and 5 respectively. The
LDG is used as the OTU and the LDG uses the PIN laser. For the timeslot, see the file in the
attachment. (Note: 1:1-LDG indicates the LDG is in Slot 1 of the subrack at station 1.)
Station1 Station2 Station3 Station4 Station5
1:1-LDG 2:9-LDG 2:9-LDG 5:1-LDG

192.10THz
1:2-LDG 3:9-LDG 3:9-LDG 5:2-LDG

192.50THz
1:3-LDG 4:9-LDG 4:9-LDG 5:3-LDG

192.90THz

Platform
Cause Analysis
One day both 2-D:9-LDG and 3-D:9-LDG report IN_PWR_LOW alarm. The IN_PWR_LOW
alarm indicates that the input power is too low and the alarm is reported through the LDG-och-1
port (WDM-side port). On the T2000, query the power of the two boards. The current input
power of the 2:9-LDG-och-1 is -19.2 dBm and that of the 3:9-LDG-och-1 is -20.2 dBm, which
are below the receiver sensitivity of the PIN laser (-18 dBm). Thus, the alarm occurs. Compare
the queried power value with the values recorded during maintenance, and it is found that the
power of each wavelength has degraded by 5-6 dB.
Analyze the services against the timeslot diagram. It is found that the routing shared by the two
services is between stations 3 and 5. Thus, you can locate the problem in the section between
stations 3 and 5.
Procedure
Step 1 Query the optical power of the 4:9-LDG-och-1 and compare it with the original value as
recorded. You can find there is little change. Query the optical power of the 1:3-LDG-och-1 and
find it is -17.5 dBm, whereas the original value is -12.4 dBm. The optical power of the 1:3-LDG-
och-1 has degraded by 5.1dB, but no alarm is generated though it is below the receiver sensitivity.
Thus, the failure can be located to the section specified by the routing shared by the three services;
that is, the section between station 3 and station 4. In addition, query the power of the other
direction, and find the power is similar to the original value as recorded in the initial maintenance.
At this stage, you can determine that the problem is located in the direction where station 3
receives services from station 4. Moreover, the problem lies in the optical path shared by all
wavelengths.
Step 2 Check with the maintenance personnel at station 3 and station 4 over the phone to find whether
the fiber jumpers or equipment is moved. It is confirmed that the ODF and the relevant documents
at station 4 are available at about 9 o'clock. Then, the maintenance personnel at station 4 check
the ODF and find that the fiber responsible for transmitting the service from station 4 to station
3 is bent, which is then restored to the normal condition. At this stage, it is found that optical
power is recovered.
----End
l The processing of the fault occurred in the WDM equipment also should comply with the
principle for processing the common failures; that is, locate the failure to a single station
according to the signal flow.
l The processing of the failure occurred in the WDM equipment, however, has its unique
features. In the case of one-channel 2.5 Gbit/s, regardless of the dispersion, the essential
cause for the problem is the optical power. Especially when the MCA is not configured,
the optical power is the primary index for us to know the network operation status. The
T2000 provide a good monitoring method for us, so we must make full use of it.
l During the maintenance of WDM equipment, recording the power of each reference point
of the equipment is very important. We must do well in recording the power values once
the project is completed. Firstly, keep the project completion documents. Secondly, during
the maintenance, though the power differs slightly at different stages, record the variation
in time; if the power differs greatly, you must deal with the problems in a timely manner.
In this way, you can ensure that the equipment operates with proper power. The detailed
maintenance documents of the power are helpful to resolve the problem in the shortest time.

Platform
l Familiarize yourself with the equipment performance and the T2000. For example, the
LDG has four pairs of optical interfaces, which are called IN1/OUT1 (WDM-side 1), IN2/
OUT2 (WDM-side 2), RX1/TX1 (client-side 1), and RX2/TX2 (client-side 2). On the
T2000, however, they are called LDG-och-1, LDG-och-2, LDG-och-CTL-3, and LDG-
och-CTL-4, respectively.
5.18 MC-A20 The T2000 Cannot Log in to the Remote GNE

Connected by the Router
The T2000 cannot log in to the remote GNE connected by the router.
Product
OptiX Metro 6100
Fault Type
NE Offline
Symptom
The OptiX Metro 6100 equipment forms a ring network. The remote T2000 connects to the GNE
through the router. It is found that the T2000 cannot communicate with the GNE. Thus, the
T2000 fails to manage the entire network.
Cause Analysis
When users cannot log in to the GNE on the T2000 or through the command line, it is possibly
because:
l Wrong IP address, subnet mask and gateway setting.
l Ethernet cable problem or poor communication quality.
l Fault of the SCC.
Procedure
Step 1 Check the communication setting of the T2000, router, and GNE to check whether they are
properly connected. If so, the possibility that the connection is configured improperly is
excluded.
Step 2 Replace the Ethernet cable, but the problem persists. In addition, confirm that the contact of the
router and HUB interface is in good condition, so you can exclude the possibility that the Ethernet
cable is faulty.
Step 3 Connect a PC to the local GNE interface. In this case, users can log in to the equipment
successfully. Therefore, the SCC is normal.
Step 4 Finally, it is found that the GNE and T2000 are located in two different sections. To realize the
communication between the GEN and the T2000, static routes must be configured, refer to
Configuration Guide. At this stage, users can log into the GEN through the T2000 and thus the
T2000 can manage the entire network.
----End

Platform
When the GNE in the network consisting of the Metro 6100 equipment and the T2000 are located
in different sections, you need to configure the static route. Otherwise, communication between
the GNE and the T2000 will fail.
5.19 MC-A21 An Interconnection Failure between the WDM

and SDH Equipment
Inconsistent wavelength range causes an interconnection failure between the WDM and SDH
equipment.
Product
OptiX BWS 1600G
Fault Type
R_LOF
Symptom
Before cutover(services run on the 320G normally)
TWC RWC
S16 BA2 S16
RWC TWC
Station A Station B Station C
After cutover(services run on the 1600G normally) R_LOS is reported
S16 LWC LWC BA2 S16
Station A Station B Station C
Patch cord External cable
As shown in the figure, cut over the SDH service from the OptiX BWS 320G to the OptiX BWS
1600G. After cutover is completed, the received optical power of the SL16 board in the SDH
equipment is normal, but the SL16 reports R_LOF.

Platform
Cause Analysis
l Connect the fiber to the OptiX BWS 320G equipment. As a result, services are recovered
normally. Test the optical power on each node. All values are normal.
l Browse the OTU board parameters of two kinds of equipment. View the RWC front panel
of the OptiX BWS 320G. The board is the 72RWC04. The English name STM-16 Receiving
Wavelength Conversion Board (RxAPD/Tx1550nm, SC) indicates that the transmit
wavelength on the client side of the board is 1550 nm. The LWC client side of the 1600G
is S-16.1 and the transmit wavelength is 1310 nm.
l The wavelength of the BA2 ranges from 1530 nm to 1565 nm; namely, the wavelength
window is 1550 nm. Therefore, the BA2 amplifies the transmit light (1550 nm) of the TWC
for the 320G and services are normal. However, the BA2 cannot amplify the transmit light
(1310nm) of the LWC for the 1600G, but can amplify the noise at 1550 nm. At station C,
the SL16 detects the noise at 1550 nm. Though the noise optical power is normal, the SL16
reports R_LOF.
Procedure
Step 1 Replace the LWC with the client side module L-16.2 (L16.2 transmits light at 1550 nm).
----End
None.
5.20 MC-A22 NE ESC Communication Interrupted Because

of the Closure of the OTU Laser
NE ESC communication interrupted because of the closure of the OTU laser.
Product
OptiX Metro 6100
OptiX BWS 1600G
Fault Type
NE Offline
ECC
Symptom
NE ESC communication interrupted.
Cause Analysis
The OptiX Metro 6100 and OptiX BWS 1600G support two types of supervisory channel: optical
supervisory channel (OSC) and electrical supervisory channel (ESC). The ESC is transmitted
by any OTU. The difference between the OSC and the ESC is that the OSC is transmitted by a

Platform
dedicated supervisory channel board but the ESC is transmitted by the DCC byte or subcarrier
module of the OTU.
when the ESC is used for communication, in the case that only the OTUs are used for connection
of two NEs, when the ALS function is enabled or the lasers on the OTUs are turned off forcibly,
the communication on the remote NE is interrupted, and users cannot log into the NE.
Procedure
Step 1 An engineer must go to the station and turn on the lasers on the OTUs to restore the
communication.
----End
It is not recommended to use the ESC when two NEs are connected through the OTUs.
If the ESC is used for communication, engineers must turn on the lasers of the OTUs forcibly
and it is recommended to set Automatic Laser Shutdown to Disabled(Automatic Laser
Shutdown for some OTU boards is set to Enabled by default).
5.21 MC-A23 When the OTU Board Accesses Light, the Laser
at Output End is Disabled
When the OTU board accesses light, the laser at output end is disabled.
Product
OptiX BWS 1600G
Fault Type
Protection
Symptom
During the TMX test in the OptiX BWS 1600G, it is found that no light is transmitted at the
transmit end on the client side of the TMX board after the fiber on the WDM side of IN port is
removed. After a meter is connected to the WDM side, the client-side laser on the TMX board
cannot be enabled automatically (the automatic laser shutdown (ALS) function is enabled). In
this case, you have to disable the ALS function, enable the client-side laser manually, and then
enable the ALS function. Then, the situation becomes normal. That is, the client-side laser is
enabled automatically after a meter is connected to the WDM side of the TMX board.
Cause Analysis
None.

Platform
Procedure
Step 1 When the problem occurs, make sure that there is no LOS alarm on the OTU board (note that
the alarm may be suppressed). If there is the LOS alarm and the automatic laser shutdown (ALS)
function is enabled, the laser at the output end is disabled.
Step 2 Check whether the SCC issues a command to disable the laser or not. If yes, the ALS function
cannot take effect, unless the SCC issues a command to enable the laser.
Step 3 Check whether the SCS protection is configured or not. If yes, the SCC disables the laser of one
board to duplicate the service. In this case, the ALS function cannot take effect.
----End
If there is service on the SCS, do not enable the laser that is disabled by the SCC. Otherwise,
the service is interrupted, unless the fiber from the OTU to the SCS is removed.
5.22 MC-A24 Low Optical Power on the Client Side of the

OTU Board Leads to R_LOS Alarm on the Board
Low optical power on the client side of the OTU board leads to R_LOS alarm on the board.
Product
OptiX BWS 1600G
Fault Type
R_LOS
R_LOF
Symptom
The networking is as follows: E(SDH)------>A(OTM)--->B(OLA)--->C(OLA)--->D
(OTM)------>F(SDH). A-B-C-D is a WDM link. A and D are OTM stations and are connected
to the SDH equipment E and F respectively.
E-SDH A-OTM B-OLA C-OLA D-OTM F-SDH
On station A, the RX interface of the client side of the board LWC-192.2THz reports R_LOS.
At the same time, the optical board SL26 on station F reports R_LOF, and IN interface of the
WDM side of the board LWC-192.2THz on station D reports R_LOF. The LWC board is 2.5G-
SSEM4LWC01-PDS and is forced to emit light.

Platform
Cause Analysis
l The fiber jumper is not connected or not properly inserted.
l The LWC board fails.
l The fiber jumper is faulty.
Procedure
Step 1 Query the received optical power of the RX interface on the LWC on the station A by using the
T2000. The power is -60.0 dBm and no light is received. The received optical power of the SDH
board on station E is normal. The cause may be that the RX interface of the LWC board on
station A or the OUT interface of the SDH optical board on station E is not connected with a
fiber jumper.
Step 2 Conduct inloop at the client side of the LWC board on station A. The SDH optical board on
station E reports the R_LOS alarm. Conduct outloop. The alarm is cleared. This indicates that
the SDH optical board on station E receives signals from station A normally, and the RX interface
of the LWC board on station A or the OUT interface of the SDH optical board on station E is
connected with a fiber jumper. If the fiber jumper is not connected, the loopback cannot be
successful.
Step 3 Conduct outloop at the client side of the LWC board on station D. The SDH optical board on
station E reports R_LOS. Conduct inloop. The alarm of the SDH optical board on station E is
cleared. This indicates that the WDM chain A—B—C—D is normal.
Step 4 Conduct inloop at the client side of the LWC board on station A. The R_LOF of the SDH optical
board on station F is cleared. Conduct outloop. The SDH optical board of station F reports
R_LOF. This indicates that the service from station A to station F is normal.
Step 5 Check the fiber jumpers on site. All the fiber jumpers are connected. Test the optical power of
the RX interface on the LWC board. The power is -24.5 dBm which is far lower than the receiver
sensitivity (-18.0 dBm) of the client side of the LWC in short distance transmission. When the
optical power is lower than the threshold, R_LOS is raised. After checking the fiber jumper
connections section by section, it is found that the jumper in the ODF frame is not properly
inserted. After the fiber jumper is properly inserted, the problem is resolved.
----End
When installing the fibers into the ODF frame, insert the jumper connectors properly into the
socket. Then, such problem can be avoided.
5.23 MC-A25 The System Indicates that the Channel

Number Is Illegal
In the case of the deployment of the OptiX OSN 6800, the system indicates that the channel
number is illegal when the electrical cross-connect services are configured on the TQM board.
Product
OptiX OSN 6800

Platform
Fault Type
Protection
Symptom
In an IP MAN network that is newly deployed, the OptiX OSN 6800 is used and the TQM and
NS2 boards are configured. Networking: There are five stations in this project. The five stations
are located in the same city, forming a 10Gbit/s ring network. The ODU1 SNCP protection is
configured.
During the configuration of electrical cross-connect services for GE services, the system
indicates that the channel number is illegal.
Cause Analysis
When there is an indication for this problem, check whether the input parameters are correct and
whether the cross-connect type matches the service type of the board.
Procedure
Step 1 Check if the channel number consists of illegal characters. After checking, we found that the
number consists of legal digit characters.
Step 2 Check if the LP port corresponding to the channel number does not exist. After checking we
found that the LP port (port 1) exists.
Step 3 Check if each LP port corresponds to a certain type of services by default. On the NE Explorer
in T2000, select the TQM board and choose Configuration > WDM Interfaces. Click
Advanced Attributes on the displayed dialog box and check the service type for each LP port.
It is found that each LP port corresponds to STM-4 services by default. Then, change the service
type to GE service. Configure the electrical cross-connections again and the problem is not
revisited.
----End
When configuring the electrical cross-connect service, we should pay attention to the fact that
the LP port corresponds to a certain service type by default.
5.24 MC-A26 The Centralized Power Distribution Cabinet

Endures Power Failure
The external power cables of the DC power distribution box in the OSN 6800 are connected
incorrectly. When one channel in the centralized power distribution cabinet endures a failure,
power failure occurs in two subracks.
Product
OptiX OSN 6800

Platform
Fault Type
Other
Symptom
In a OptiX OSN 6800 cabinet, there are four subracks. The DC power distribution box of the
cabinet provides four power supplies.
After hardware installation, perform a power switch test in the working and protection power
supplies: First perform a power switch test in the DC power distribution box first. Shut down
the four working switches in area A of the DC power distribution box. The four switches are the
working power supply switches of the four subracks. In this case, the power supply to subracks
is normal. Turn on the four switches in area A and shut down the four switches in area B. The
four switches in area B are the protection power supply switches of the four subracks. In this
case, the power supply to subracks is normal.
Then, perform a power switch test in the working and protection power supplies in the centralized
power distribution cabinet. Turn on the two protection power supply switches and shut down
the two working power supply switches. In this case, the two lower subracks endure a power
failure. Turn on the two working power supply switches and shut down the two protection power
supply switches. In this case, the two upper subracks endure a power failure.
Cause Analysis
The DC power distribution box of the OptiX OSN 6800 cabinet provides four power supplies.
For the four inputs, area A and area B are of mutual backup. Each area accesses two external
inputs. The two external inputs in area A are the working power supplies. RTN1(+) and NEG1
(-) provide the working power supply (working 1) for the two lower subracks. RTN2(+) and
NEG2(-) provide the working power supply (working 2) for the two upper subracks. The two
external inputs in area B are the protection power supplies. RTN1(+) and NEG1(-) provide the
protection power supply (protection 1) for the two lower subracks. RTN2(+) and NEG2(-)
provide the protection power supply (protection 2) for the two upper subracks.
After the on-site fault locating, it is found that the hardware engineer introduced a reverse
connection mistake in the two -48V external power cables of working 2 and protection 1.
Terminals in area A are connected to the external input power cables of working 1 and protection
1 and terminals in area B are connected to the external input power cables of working 2 and
protection 2. In this case, working 1 and working 2 provide power supplies to the two lower
subracks at the same time. Protection 1 and protection 2 provide power supplies to the two upper
subracks. Hence, this problem occurs.
Procedure
Step 1 Re-connect the two -48V power cables of working 2 and protection 1 in the reverse way.
----End
l Precautions for connecting external power cables in the OSN 6800 are as follows: The DC
power distribution box of the OSN 6800 is different from that of old products. When each
input is 63A , four power inputs are required. The cable connections are as follows: The
two inputs in area A are the working power supplies. RTN1(+) and NEG1(-) provide the
working power supply (working 1) for the two lower subracks. RTN2(+) and NEG2(-)

Platform
provide the working power supply (working 2) for the two upper subracks. The two inputs
in area B are the protection power supplies. RTN1(+) and NEG1(-) provide the protection
power supply (protection 1) for the two lower subracks. RTN2(+) and NEG2(-) provide
the protection power supply (protection 2) for the two upper subracks.
l After the equipment is powered on, two working/protection power failure tests must be
performed to determine if there is any fault in the cable connections. 1. Perform a power
failure test in the DC power distribution box. 2. Perform a power failure test in the
centralized power distribution cabinet. After the two tests, we can ensure that there will not
be power failure faults in the equipment room and the subracks.
5.25 MC-A27 Should the Nominal Gain of the OAU1 Board

Be Re-set?
Should the nominal gain of the OAU1 board in the OSN 6800 be re-set after the type of the
DCM between TDC and RDC is changed?
Product
OptiX OSN 6800
Fault Type
VOA_ADJUST_FAIL
Symptom
In a OptiX OSN 6800 40-channel project, the TN11OAU101 (gain ranges from 20 dB to 31 dB
and the per-channel standard output optical power is +4 dBm) is used. In the initial stage, no
DCM is configured between optical interface TDC and RDC of the OAU1. The nominal gain
of the OAU1 is set to 20 dB on the T2000 and the per-channel input/output optical power is -16
dBm/+4 dBm. In later stages, a DCM(B) (it compensates for 40 km dispersion and the insertion
loss is 5 dB) is added between TDC and RDC of the OAU1 because of dispersion issues. In this
case, engineers are wondering if the nominal gain of the OAU1 should be re-set on the T2000,
so that the per-channel output optical power of the board remains +4 dBm? Or the OAU1 adjusts
the gain automatically to ensure that the per-channel output optical power remains +4 dBm?
Cause Analysis
None.
Procedure
Step 1 Check if the DCM insertion loss meets the requirement before replacing the DCM.
Step 2 Allowable DCM insertion loss = Gain of the OAU1 - Nominal gain (the setting on the T2000)
If the insertion loss between TDC and RDC is very large and exceeds the adjustment range of
the OAU1, the OAU1 reports the VOA_ADJUST_FAIL, which is a minor alarm. In this case,
check if the fiber insertion loss is very large. If it is very large, remove the fiber faults.
Step 3 If the DCM insertion loss meets the requirements and the fiber faults are removed, engineers do
not need to re-set the nominal gain on the T2000. The OAU1 adopts the automatic gain control
(AGC) mode. The OAU1 monitors the output and input optical power in real time, so that the

Platform
gain (the difference between the input and output optical power) of the OAU1 keeps the same
as the value set on the T2000. Whether TDC and RDC interfaces are connected directly through
a fiber jumper or a DCM is added between them, the per-channel input/output optical power is
always -16 dBm/+4 dBm and the gain remains 20 dB.
----End
None.
5.26 MC-A28 The LSX Board Reports the OTUk_LOF Alarm

OptiX OSN 6800, When accessing 10GE LAN services, the LSX board reports the OTUk_LOF
alarm because of the inconsistency in the settings of WDM-side rate.
Product
OptiX OSN 6800
Fault Type
OTUk_LOF
Ethernet Service
Symptom
In a OptiX OSN 6800 project, the LSX board is used to access 10GE LAN services. While the
receive optical power is normal, the board reports the OTUk_LOF alarm on the WDM side and
thus the services are interrupted.
Cause Analysis
When the TN11LSX board accesses 10GE LAN services, three mapping modes are available
on the client side:
l Bit Transparent Mapping (11.1G)

l Bit Transparent Mapping (10.7G)
l MAC Transparent Mapping (10.7G)
The TN12LSX board do not support the third mode. When the TN12LSX accesses 10GE LAN
services, two mapping modes are available on the client side:
l Bit Transparent Mapping (11.1G) (OTU2v Signals)

l Bit Transparent Mapping (10.7G) (OTU2 Signals)
The difference in the modes of the OTUs at the transmit and receive ends brings service
interruption.

Platform
Procedure
Step 1 On the T2000, query the client-side setting of the LSX boards on the two ends. The setting of
one LSX is Bit Transparent Mapping (11.1G) and that of the other LSX is Bit Transparent
Mapping ( 10.7G ). The modes of the two LSX boards are different. Hence, the OTUk_LOF
alarm is generated. Change the modes of the two LSX boards to Bit Transparent Mapping
( 10.7G ) on the T2000. Then, the alarm clears and the services are recovered.
----End
When the LSX boards in the OptiX OSN 6800 are used to access 10GE LAN services, make
sure that the client-side mode of the boards are the same. Otherwise, the services are interrupted.
In the case of the TN11LSX, if the mapping modes of the LSX boards at the two ends are in the
combination of 1+2 or 1+3 (in different rates), the OTUk_LOF alarm is reported. If the mapping
modes are in the combination of 2+3 (in the same rates), the BEFFEC_EXC alarm is reported.
5.27 MC-A29 On the OptiX OSN 6800, End-to-end GE

Services Cannot Be Created
On the OptiX OSN 6800, end-to-end GE services cannot be created.
Product
OptiX OSN 6800
Fault Type
Other
Symptom
The OptiX OSN 6800 V100R003 system is used in a new site. In the ROADM network
comprising the WSD9 and RMU9, the L4G is used. After fiber connections are created, OTS
and OMS routes are found. Create GE services by using the end-to-end trail function on the
T2000V200R006C01. Firstly, create OCh service trails end to end by using the WDM trails.
The system should automatically complete the optical cross-connection configuration. It,
however, cannot continue to create end-to-end GE services.
Cause Analysis
In the ROADM network comprising the WSD9 and RMU9, after we created OCh trails, only
the OCh trails on optical layer are created. The electrical-layer service trails of the ODU 5G and
OTU 5G , however, are not created. Currently, the ODU 5G and OTU 5G can be discovered
only through searching. Client GE services must be created on OCh optical-layer trails and the
electrical-layer service trails of the ODU 5G and OTU 5G . For the relation between trails on
each layer, refer to the attachment.

Platform
Client
ODUk
OTUk
OCh
OMS
OTS OTS OTS
Procedure
Step 1 After OCh trails are created, use the WDM trail searching function. The electrical-layer service
trails of the ODU 5G and OTU 5G are discovered after the searching. Then, use the WDM trail
function to create client GE services. In this case, the system automatically completes the
electrical cross-connection configuration.
----End
The end-to-end grooming is a very important section in WDM service management. The T2000
supports the creation of end-to-end services on the network layer. After the user specifies the
source and sink of a service, the T2000 is able to generate a client trail after it searches out the
service trail. The creation of WDM trails effectively simplifies the service configuration process
and guarantees the correctness of the operation. In addition, the service grooming and allocation
in deployment or capacity expansion are more flexible. When you create end-to-end services on
the T2000, search the trails after you create OCh trails. Then, configure client services.
5.28 MC-A30 LDG Board of Metro 6100 Equipment Reports

the INBADOCTS_OVER Alarm
LDG board of Metro 6100 equipment reports the INBADOCTS_OVER alarm.
Product
OptiX Metro 6100
Fault Type
INBADOCTS_OVER
Ethernet Service
Symptom
In one DWDM network, the Metro 6100 equipment is configured with the LDG board that is
interconnection with client-side datacom equipment and transmits the GE service , but during

Platform
the running status, the LDG in some site reports the INBADOCTS_OVER alarm. The alarm is
reported continually for several minutes.
Cause Analysis
The INBADOCTS_OVER indicates that the LDG has received the damaged IP service packet.
The following lists the possible causes:
l The input optical power of the LDG board is abnormal.
l Client-side datacom equipment sent the wrong IP packet.
l The GE port on the LDG board is faulty.
l The length of the IP packet applied for exceeds the maximum length of a packet configured
for the LDG port.
Procedure
Step 1 Test the LDG port input power and it is found that the power is normal.
Step 2 Use Smartbits to test the LDG board for 24 hours, and no bit errors are detected, which indicates
that the problem may be caused by the datacom equipment.
Step 3 Confirm with datacom engineers and it is found that the IP packet from datacom port is longer
than the default packet length value of the LDG port (1552 byte ). In NE Explorer of the T2000,
select the LDG board. Then, choose Configuration > WDM Interface to change the value of
Maximum Packet Length to 1552 bytes, or change it to the maximum value. And the
INBADOCTS_OVER alarm is not reported any more.
----End
Reference Imformation
None.
5.29 MC-A31 Wrong Calculation for Dispersion in One

DWDM Project
Wrong calculation for dispersion in OptiX Metro 6100, which leads to B1, B2 and B3 errors. In
addition, the R_LOF alarm is detected on SDH analyzer sometimes.
Product
OptiX Metro 6100
Fault Type
Bit Errors
R_LOF
Symptom
One OptiX Metro 6100 project consists of two OTM stations, five OLA stations, and two OADM
stations. The network transmits two STM-16 services and two GE services. In the case of the

Platform
STM-16 services, two pairs of LWX boards are used for transmission; in the case of the GE
services, one pair of LDG boards are used for transmission.
After the hardware installation and software commissioning, it is found that the performance of
the STM-16 services is very poor, in which a great deal of B1, B2, and B3 errors are detected.
In addition, the R_LOF alarm is detected on SDH analyzer sometimes.
Cause Analysis
Try to reduce the transmission distance by moving the LWX boards into other proper stations.
Then, we found the STM-16 services were normal.
Check the real dispersion and find that that the dispersion of the customer's optical cable does
not comply with the international standard for the dispersion. In this case, the dispersion is 8400
ps/nm instead of 7000 ps/nm, whereas the connection is made by 330 km G.652 fiber and 225
km G.655 fiber. In quotation, it describes as follows: two "SS-LWX(S/M,Rx1PIN, I-16,7200ps/
nm)" boards used for one station, and two "SS-LWX (S/L,Rx1APD,L-16.2,12800ps/nm)"
boards used for the remote station. The dispersion tolerance of LWX board at the first station is
insufficient and cannot meet the transmission requirement (8400 ps/nm).
Procedure
Step 1 Connect the SDH analyzer to the LWX board at one station and created the hardware loop on
the client side of the LWX at the remote station . In the case of the locale loop, the STM16 is
normal. in the case of the software loop or hardware loop in remote station, the STM16 services
is abnormal. On the T2000, no alarm on the LWX boards is reported, but on the SDH analyzer
a lot of B1, B2 and B3 errors are detected. Furthermore, sometimes the LOF is detected on the
SDH analyzer. After the SDH analyzer is set to send STM-4 services, it is found that the STM-4
services are normal.
Step 2 Replace the LWX boards at the first station with the LWX boards with 12800 ps/nm dispersion
tolerance.
----End
Not every time the features of the optical fiber comply with the international standards. In the
system, sometimes aging fibers with poor performance are used. Thus, before the design, collect
the information of all the fibers that are used in the existing system. When necessary, consult
with customers for the right information about the optical cables.
5.30 MC-A32 When OptiX BWS 1600G SCC Board Is

Replaced with the SCE, TC2 Board Reports BD_STATUS
Alarm
When OptiX BWS 1600G SCC board is replaced with the SCE, TC2 board reports BD_STATUS
alarm.
Product
OptiX BWS 1600G

Platform
Fault Type
BD_STATUS
Symptom
In the OptiX BWS 1600G V100R001 (OptiX BWS 1600G-III), NE software version is
5.08.01.31. It is found that the TC2 board in slot 6 reports the BD_STATUS alarm. At the
beginning, it is suspected that the board or slot is faulty. After they are replaced, the problem
persists.
It is found that an SCE board is inserted in slot 7 of the same subrack. When we asked the
equipment room maintenance personnel, it was told that the previous SCC board is faulty;
therefore an SCE spare board is used to replace the faulty SCC board.
Cause Analysis
The SCE board is a simplified version of the SCC. It has no orderwire module and cannot monitor
the TC1/TC2 board.
Procedure
Step 1 Replace the TC2 board, the problem persists.
Step 2 Remove the TC2 board in slot 6 and insert it into slot 8. The problem persists.
Step 3 Replace the SCE board with an new SCC board. The problem is resolved.
----End
Compared with the SCC board, the SCE board does not provide the orderwire function, and
cannot monitor the SC1/SC2/TC1/TC2 board. Therefore, observe the preceding differences
when replacing the SCC board with the SCE board.
5.31 MC-A33 Remotely Checking the Correctness of the

DCM Installation
Remotely checking the correctness of the DCM installation.
Product
OptiX BWS 1600G
Fault Type
Other
Symptom
In the hardware installation of the OptiX BWS 1600G, because of the mis-operation of engineers,
the DCM at some sites may be installed incorrectly. For example, the two directions of a DCM

Platform
in an OLA site are: from east to west, C1 (20 km) and from west to east, C3 (60 km). If the two
directions are installed incorrectly, the service cannot be provisioned smoothly. Hence, we need
to check whether the two directions are installed in the reverse manner.
Cause Analysis
It is time-consuming to check the correctness of the DCM installation on site. We can remotely
check the OAU optical power to determine whether DCM is installed correctly. The OAU
provides the detection and report of optical power at five points on the board. Optical interface
3, corresponding to optical interface RDC, detects the input optical power in the middle of the
board; Optical interface 5, corresponding to optical interface TDC, detects the output optical
power in the middle of the board.
Because DCM is installed between TDC and RDC of the OAU, the difference in optical power
between interface 5 and interface 3 is the DCM insertion loss. Because the DCM insertion loss
is basically fixed, one knows what DCM model is installed according to the insertion loss.
Procedure
Step 1 Query the east-to-west OAU optical power and the difference in optical power between interface
5 and interface 3 is calculated to be 1.6 dB.
Step 2 Query the west-to-east OAU optical power and the difference in optical power between interface
5 and interface 3 is calculated to be 5.3 dB.
Step 3 This shows that the east-to-west is DCM (C1) and the west-to-east is DCM (C3). The two DCMs
are installed correctly. There is no need to conduct on-site operations.
----End
l The engineers must be trained before performing hardware installation. The engineers are
required to install the hardware according to the cabinet fiber wiring diagram in the
engineering design. Observe the label on the fiber jumper that is threaded to the DCM frame
from the subrack. Note that the DCM model is indicated on the label.
l If a problem occurs during the hardware installation, do not rush to the site. Consider
whether the equipment can be remotely checked.
l If the problem can be remotely resolved, use the remote method. If remote troubleshooting
is impossible, the engineer has to go to the site to resolve the problem.
5.32 MC-A34 The Subrack Alarm Cannot be Uploaded to the

Alarm Indicator in the Cabinet
OptiX BWS 1600G PMU board being down; subrack alarm cannot be uploaded to the alarm
indicator in the cabinet.

Platform
Product
OptiX BWS 1600G
Fault Type
Other
Symptom
At the NE commissioning in a project, no matter what alarms are generated in the subrack, the
alarm indicators at the top of the cabinet are not on. However, if the Test switch is opened, the
visual and audible alarm in the cabinet is normal.
Cause Analysis
l The alarm connector in the subrack may be loosened.
l The connector of the alarm cable to the power box may be loosened.
l The PMU board is faulty.
Procedure
Step 1 Check the connectors of the alarm cable in the subrack and to the power box. They are well
installed.
Step 2 Replace the PMU board with the one in another cabinet and the alarms can be reported normally,
whereas the alarms in the other cabinet cannot. The PMU board is faulty.
Step 3 Replace the faulty PMU board.
----End
l The problem can be resolved simply by replacing the board.
l If you are familiar with the alarm flow, this case study is a good reference for such rare
faults in the PMU.
5.33 MC-A35 LWM Output Optical Power Is Unstable upon

Forced Light Generation
LWM output optical power is unstable upon forced light generation.
Product
OptiX BWS 1600G
Fault Type

Platform
Symptom
When there is no input light to the LWM board, the board is forced to emit light for system
commissioning. Then, it is found that the output power of the light fluctuates at about 1 dB.
There is no such problem in the OTUs in other type such as the LWF.
Cause Analysis
The LWM processes signals in a way that is different from other OTUs. The LWM does not
process the signals. When the engineer forces the LWM to emit light, optical signals are random.
There may be multiple continuous "0"s or "1"s in an optical signal.. In this case, the optical
power fluctuates significantly at 10 dB.
The LWF, however, processes the input signals. Even when there is no input signal, the light
that is emitted by the LWF is scrambled. Therefore the output power is stable.
Procedure
Step 1 It is normal.
----End
l When a board is forced to emit light, the fluctuation in the output optical power varies with
the board type because different types of boards have different mechanisms to process
signals.
l At the commissioning stage, use instruments and meters.
l This problem does not mean the equipment is not stable.
5.34 MC-A36 The OTU in the OptiX BWS 1600G Reports

IN_PWR_LOW Alarm
The OTU in the OptiX BWS 1600G reports IN_PWR_LOW alarm.
Product
OptiX BWS 1600G
Fault Type
IN_PWR_LOW

Platform
Symptom
Station 2
Station 3
Station 1
Station 4
Station 6
Station 5
Six OptiX BWS1600G systems form a ring network. One day, some OTUs on stations 2, 3, and
4 report the IN_PWR_LOW alarms and some report LOS or LOF transiently.
Cause Analysis
l The optical power is very low.
l This attenuation is very high.
l The OTU is faulty.
Procedure
Step 1 Check the optical power on each station through the T2000. The optical power received on every
station that reports the alarm is within the range, but the common thing is that the optical power
is close to the lower limit.
Step 2 Check the add/drop wavelength operations on stations 1 to 4. The OTUs that report alarms are
in the same direction, that is, 1-2-3-4. The optical power of the OTUs of the opposite direction
that drop wavelengths is good.
Step 3 The transmitting optical power of the WBA2 on station 1 is 7.8 dBm and the related receive
optical power of the WBA on station 2 is -14.6 dBm. The attenuation is 22.4 dB and the actual
distance between the two stations is only 40 km. This attenuation is very high.
Step 4 Adjust the optical power of each optical interface. The attenuation of a section of the fiber jumper
on station 2 is very large. So the fiber jumper is replaced. The alarms on some OTUs on the
downstream stations are cleared. The alarm on the LDG on station 3 persists.
Step 5 Test the incoming optical fiber of the LDG. The value is the same as that displayed on the T2000.
A 10 dB optical attenuator is used. Then remove the optical attenuator and connect the board
back. The optical power recovers normal and the alarm is cleared.
----End

Platform
The reason is that the incoming optical power is not adjusted to the best value, but to the value
within the lower limit during a project test. Thus when a point of the system changes slightly,
many OTUs report alarms.
5.35 MC-A37 The LWFS in the OptiX BWS 1600G

Transiently Reports FEC_LOF Alarm
OptiX BWS 1600G, the LWFS in the OptiX BWS 1600G transiently reports FEC_LOF alarm.
Product
OptiX BWS 1600G
Fault Type
FEC_LOF
SM_BDI
Symptom
Station A and station B are the OptiX BWS 1600G, they perform the point-to-point chain
network. In the middle are three OLAs. The LWFS on site B (196.00 THz) transiently reports
FEC_LOF and station A reports SM_BDI.
Cause Analysis
l SM_BDI is the remote alarm information of the OTU. station B receives FEC_LOF and
then reports it.
l Other LWFSs are normal. So the line is not faulty.
l The transmit part of station A or the receive part of station B is faulty.
Procedure
Step 1 The optical power and signal-to-noise ratio are normal. So the line is not faulty.
Step 2 Perform a self-loop between stations A and B on the WDM side. Site A reports FEC_LOF.
Step 3 Replace the LWFS on station A and the problem is resolved.
----End
None.

Platform
5.36 MC-A38 The Service Is Interrupted After the Protection

Is Triggered
The service in the working channel is interrupted after the inter-board wavelength protection is
triggered, because the 1+1 inter-board protection is mistakenly configured on the OptiX BWS
1600G.
Product
OptiX BWS 1600G
Fault Type
Protection
Symptom
There are alarms on the SDH equipment interconnected to the DWDM network, but the client-
side services are configured with the 1+1 inter-board protection and are not interrupted. After
checking the entire network, it is found that there is no output power on the client side of the
LWC1 board in slot 5 of the OptiX BWS 1600G, and the laser on the client side is shut down.
In addition, reseating the board cannot solve this problem. After the LWC1 board in slot 5 is
moved to another subrack of the local station, the laser on the client side of the LWC1 resumed
normal operation.
Cause Analysis
After checking the entire network and analyzing the symptom, the cause for this problem is that
the inter-board wavelength protection is mistakenly configured on the LWC1 boards in slot 5
and slot 6. On the existing network, the LWC1 boards in slot 5 and slot 6, however, are considered
as two independent boards to carry separate services. When the customer adjusts the optical
path, the inter-board wavelength protection is triggered. In this case, the client-side laser on the
LWC1 board in slot 5 (the working board) is shut down. As configured, the protection switching
mode is configured to the non-revertive mode. Therefore, although the fault that occurs on the
LWC1 board in slot 5 is eliminated, the service in the channel cannot be restored, and thus the
service is interrupted.
Procedure
Step 1 After checking the entire network on site, the inter-board wavelength protection is deleted. This
eliminates potential faults.
----End
None.

Platform
5.37 MC-A39 There Are Errors in the Setting of the Meter

ONT-30
There are errors in the setting of the Meter ONT-30, Which causes optical signal-to-noise ratio
test failure.
Pruduct
OptiX BWS 1600G
Fault Type
Other
Symptom
There are four wavelengths added, dropped or transmitted transparently on station A. The four
wavelengths are equalized before entering the FIU. When meter ONT-30 is used to test the RC
and OUT interfaces on the FIU board, it is found that the difference of optical signal-to-noise
ratio (OSNR) between the four wavelengths reaches about 6 or 7 dB after they pass through the
FIU, while the optical power does not change. Remove the fiber from the RM interface on the
FIU, the OSNR becomes flat.
Cause Analysis
Before the four wavelengths are received by the FIU, the optical power and OSNR are even.
The difference between the OSNR before a supervisory channel is used and the OSNR after a
supervisory is used is 6-7 dB. Therefore, the possible causes are as follows:
l The FIU board has poor performance. As a result, the supervisory channel affects the OSNR
of the service channel.
l The output signal of the SC2 board is of poor quality. As a result, the OSNR of the service
channel is affected.
l There are errors in the setting of the Meter ONT-30.
Procedure
Step 1 The FIU is a pure optical device. The possibility that the FIU is faulty is slight. When the RC
and RM interfaces of the FIU are connected in another direction, the problem persists. That is,
the supervisory channel still affects the OSNR of the service channel. Hence, the FIU is not
faulty.
Step 2 Interchange the TM1 and TM2 interfaces of the SC2, and the problem changes. The signals from
the TM1 interface can affect the OSNR while those from the TM2 interface cannot. Hence, the
SC2 might be faulty. However, after the TM1 interface is tested, it is found that each index of
TM1 interface is compliant with the standard. The evaluation on the optical power shows that
the TM1 interface cannot cause a difference of 6 or 7 dB between the service channels. The
problem cannot be caused by the SC2. Hence, the problem may lie in the setting of the meter.
Step 3 Meter ONT-30 performs always automatic scanning and is never manually set. It seems
impossible for the meter to have any problem. However, after compare the parameter of the

Platform
meter when the OSNR is flat with that when the OSNR is not flat, it is found that the parameter
setting of OSNR DISTANCE changes from 50 GHz to 175 GHz. This might be the problem
cause. Set the parameter to 50 GHz manually and perform the test again. The problem is cleared.
That is, the OSNR of each service channel from the FIU is flat. Why does the parameter change?
Compare the output of TM1 and TM2 interfaces. It is found that there is a spurious wavelength
with the optical power of -39 dBm in the output of TM1 interface. There is no such spurious
wavelength in the output of TM2 interface. In this case, the output side mode suppression ratio
of the TM1 interface is compliant with the standard, but the spurious wavelength has lower SNR.
This causes the change of OSNR DISTANCE.
----End
Meters used in a WDM equipment test becomes more intelligent. However, you should be
cautious of the parameter setting, because automatic scanning is not always reliable.
5.38 MC-A40 Over Compensation Causes Very High Bit

Error Rate of the Short Waves After Correction
Over compensation causes very high bit error rate of the short waves after correction.
Product
OptiX BWS 1600G
Fault Type
Bit Errors
SM_BIP8_OVER
SM_BIP8_SD
Symptom
B A A A A A
v D
OBU03 OBU03
OBU03 OAU01 OAU01 OAU01 OAU01 OAU01 OAU01
40 40
25Km 89.44Km 87.19Km 73.25Km 67.34Km 73.54Km 40.60Km
D 11.23dB 25.60dB 25.66dB 24.03dB 20.25dB 21.69dB 15.88dB v
OBU03 OAU01
OAU01 OAU01 OAU01 OAU01 OAU01 OAU01 OBU03
40 40
A A A A A Ｂ
A B C D E F G H
M 40-Channel Multiplexing Unit

40 OAU** Optical Amplifier Unit A B DCM
A G.652 Fiber
D OBU** Optical Booster Unit G.655 Fiber

40-Channel Demultiplexing Unit
40
V
40 40-Channel Multiplexing Unit with VOA
In some networks consisting of the OptiX BWS 1600G equipment, 1-22 channels (192.1 THz
used for the first channel) or 80 channels (196.05 THz) are configured. The OSNR of the system
is greater than 20 dB (the nominal OSNR is 18 dB), and the E2LWF is used as the OTU board
(AFEC). The bit error rate before correction of the networks configured with 1-22 channels is

Platform
very low (less than 10e-9), but the bit error rate before correction of the networks configured
with 80 channels is very high (about 10e-4). Check the OTU alarm information and it is found
that the SM_BIP8_OVER and SM_BIP8_SD alarms are transiently reported.
Cause Analysis
When the dispersion is over compensated, the frame structure of the short wave signals is
damaged. As a result, the bit error rate is very high before the correction.
Procedure
Step 1 Check the performance and alarm of the OTU in the 80th channel at stations A and H. It is found
that the SM_BIP8_OVER and SM_BIP8_SD alarms are transiently reported. The optical power
on the WDM side is between -6 dBm and -10 dBm. The bit error rate is very high before the
correction, which is about 10e-4. As the performance of other channels is good, this problem
may be related to the 80th channel rather than the line.
Step 2 Test single equipment indexes of stations A and H, such as the central wavelength and the output
jitter. The indexes are within the normal range.
Step 3 Check the OSNR of the 80th channel and find it is greater than 20 dB, which is better than the
nominal OSNR (18 dB). Thus, the possibility that the OSNR causes the problem is excluded.
Step 4 Clean the corresponding optical interfaces on the OTU (OUT interface that connects to the V40,
and the IN interface that connects to the D40), the problem persists. Replace the jumper, the
problem still persists.
Step 5 Use the first channel at station H to receive the signals from the 80th channel at station A. The
bit error rate of the first channel before correction is still about 10e-4, that is, the error correction
performance is not improved. Therefore, the receive end of the OTU in the 80th channel at station
H proves to be normal. Similarly, use the first channel at station A to receive the signals from
the 80th channel at station H; the error correction performance is not improved. Therefore, the
receive end of the OTU in the 80th channel at station A proves to be normal, too.
Step 6 Attach a test meter to the OTUs of stations A and H, respectively. Create a loopback on the
WDM side, and connect the test meter to the client side. The test results indicate that the OTU
is normal.
Step 7 To further verify the board performance, apply new boards at stations A and H. The problem
persists after the new boards are added. Thus, failure of the boards can be excluded.
Step 8 After the failure of the boards and stations are excluded, the system OSNR also proves to be
normal. Provide feedbacks of the networking materials and the field data to finds that the
dispersion of the original design is over compensated.
Step 9 In the direction where signals of station A are transmitted to station H, remove the DCMs of
stations F, G and H. The correction performance of the 80th channel at the receive end of station
H is gradually improved. After the dispersion over 60 km transmission is deleted, the BER before
correction of the 80th channel at the receive end at station H is 0. At this stage, check other
channels and find the correction performance does not degrade.
Step 10 Follow the same way as described in step 9 to remove the DCMs at stations A, B and C along
the direction where signals of station H are transmitted to station A. The correction performance
of the 80th channel at the receive end of station A is also improved.
----End

Platform
This solution breaks the traditional thought of troubleshooting. Traditional troubleshooting
thinks that degrade of the single-channel performance is independent of the DCM module and
improper configuration of the DCM affects all the channels rather than single channel. Thus, in
troubleshooting, after the failure of jumpers, optical power, OSNR and board is excluded, the
system should be checked.
5.39 MC-A41 Unsuccessful 1: N Protection Subnet Search

Unsuccessful 1: N protection subnet search.
Product
OptiX BWS 1600G
Fault Type
Protection
Symptom
Use one OCP and two LWF boards to form the OTU 1:N protection. After the physical fiber is
connected, the protection group is configured on the two stations, respectively. But search of
the WDM protection subnet on the T2000 always fails.
Cause Analysis
l On the T2000, the search of WDM protection subnetwork is based on the WDM path, and
the WDM path on the T2000 is based on the fiber connection on the T2000. Therefore,
after the physical fiber connection is completed, the fiber connection between the OCP and
OTU should be created on the T2000. After that, search the WDM path. Then, search of
WDM SNCP according to the WDM path will be successful.
Procedure
Step 1 First create the fiber connection between the OCP and LWF on the T2000, and then search the
WDM path. It is found that search of the WDM path fails.
Step 2 After an inspection, it is found that the transmit frequency and the receive frequency of the
protection LWF board are different. Under this situation, though the service can be available,
path search on the WDM side will fail.
Step 3 Replace the LWF board at the opposite end to ensure the transmit frequency and the receive
frequency is consistent. Search the WDM path again. At this stage, the search of the WDM path
and SNCP is successful.
----End
l The transmit frequency and receive frequency of the OTU board that used for OCP
protection must be consistent.

Platform
l Fiber connection between the OCP and OTU should be created on the T2000.
l Search the WDM path before searching the SNCP.
5.40 MC-A42 A Fault of the PMU for the OptiX BWS 1600G
Results In an Orderwire Ringing Failure
A fault of the PMU for the OptiX BWS 1600G results in an orderwire ringing failure.
Product
OptiX BWS 1600G
Fault Type
Orderwire
Symptom
During the system commissioning for the OptiX BWS 1600G, the orderwire from the local
station to remote station can get through and the ringing is normal. However, the orderwire from
the remote station to local station can get through, but the ring does not work. It is indicated only
by SCC indicator.
Cause Analysis
l Improper orderwire settings.
l Fault of the orderwire telephone.
l PMU fault.
l SCC fault.
Procedure
Step 1 As the orderwire can get through bidirectionally, the possibility that the orderwire is improperly
configured is excluded.
Step 2 Replace the orderwire with other orderwire that functions well in other subrack to perform a
test. The problem persists.
Step 3 Reset the PMU board. The problem persists.
Step 4 Replace the SCC board, after the replacement, the fault persists.
Step 5 Replace the PMU and then perform an orderwire test. The fault is deleted.
----End
In the case of troubleshooting the orderwire fault on the OptiX BWS 1600G, if the orderwire is
configured properly and no alarm is reported, it is probably caused by the PMU board.

Platform
5.41 MC-A43 Too High Insertion Loss Between TDC and

RDC of the E3OAUC01C
For OptiX BWS 1600G, too high insertion loss between TDC and RDC of the E3OAUC01C
causes the failure of gain setting.
Product
OptiX BWS 1600G
Fault Type
Symptom
The receive end of an OTM station uses the E3OAUC01. The line attenuation is about 24 dB.
Eight wavelengths of services are provided. The input optical power of the OAU is -10.2 dBm.
On the T2000, query the gain and find it is 19.6 dB and the output optical power is 9.4 dBm.
The nominal output optical power should be 13 dBm. We tried to set the gain on the T2000 to
increase the output optical power but failed, as indicated by the T2000.
Cause Analysis
OAU boards support setting the gain on the T2000.
Procedure
Step 1 The performance values of the OAU are queried as follows: The input optical power at port 1
(IN) is -10.2 dBm, the output optical power at port 2(PAOUT) is 9.7 dBm, the input optical
power at port 3(BAIN) is -6.7 dBm and the output optical power at port 4(OUT) is 9.4 dBm.
Step 2 Query the performance values of the OAU at other stations. The input optical power at port 3
(BAIN) is positive, which is probably the cause of the problem.
Step 3 During inspection, it is found that the TDC/RDC directly connects to the DCM (D). In general,
the insertion loss of the DCM (D) is 5 dB to 6 dB. Obviously, the insertion loss is too high.
Step 4 Check the fiber connector of the DCM. The connector is inserted loosely. After the connector
is tightly inserted, check the input optical power at port 3(BAIN). The value changes to 2.3 dBm.
Step 5 Readjust the gain of the OAU on the T2000. The output optical power at port 4(OUT) reaches
13 dBm. The setting is successful.
----End
For the E2 series boards, a built-in tunable optical amplifier is used to increase the output optical
power. However, for the E3OAUC01, the gain is set to increase the output optical power. If the
gain of the OAU cannot be set, check whether the insertion loss between the TDC and RDC is

Platform
too high. For the OAUC01, the maximum insertion loss between the TDC and RDC is 13 dB.
For the range of insertion loss of other boards, refer to Product Description.
5.42 MC-A44 Bit Errors Generated in the Services

Bit errors generated in the services when the LWFS board of the OptiX BWS 1600G interworks
with the router of company A.
Product
OptiX BWS 1600G
Fault Type
Bit Errors
HP_RDI
ERROR
Symptom
Stations A and B are equipped with the WDM equipment and the specific OTU board is the
LWFS. Connect the MP1570A meter to the LWFS board at station A; connect the LWFS at
station B to the router of company A. Check whether the receive optical power and transmit
optical power of the OTU at stations A and B are normal and whether the performance is normal.
If everything is normal, perform a 24-hour bit error test. Later the MP1570A meter reports the
HP_RDI and ERROR alarms.
Cause Analysis
l Improper setting of the test meter.
l Fault of the intermediate pass-through stations.
l Fault of the router of company A.
Procedure
Step 1 Check the settings of the test meter. No anomaly is found, so the meter is normal.
Step 2 Check the performance of each intermediate pass-through station. No anomaly is found.
Step 3 Check the router of company A. The status of the router port is in-loop. Release the in-loop of
the router. As a result, the alarm on the test meter clears and the fault is deleted.
----End
None.

Platform
5.43 MC-A45 During the deployment of Raman, the OPU

board reports MUT_LOS
During the deployment of Raman, the OPU board reports MUT_LOS
Product
OptiX BWS 1600G
Fault Type
MUT_LOS
Symptom
The RPC is used at the station. The fibers of the customer are in poor quality, but customers
cannot reconstruct the lines. Hence, commissioning should be first performed. After all fiber
jumpers are connected, the OPU at the receive end reports the MUT_LOS alarm, and no optical
power can be received.
Cause Analysis
The fibers are in poor quality or the fiber from RPC to ODF is damaged.
Procedure
Step 1 The remote station uses the HBA board. The transmit optical power is 22.9 dBm. According to
the whole-line loss (the optical power is -45.58 dBm during the test of the optical source), the
receive optical power at the local station should be around -22.68 dBm. However, the optical
power meter shows that the value on the SYS port of the RPC is -40.45 dBm.
Step 2 Test the optical power on the ODF. Remove the flange on the fiber. The optical power meter
shows the value is above -37 dBm. After the fiber connector is cleaned by the fiber cleansing
tool, test the power again and it is around -31 dBm. However, the nominal input optical power
at wavelength 40 of the E3OPU should be -24 dBm.
Step 3 Use a fiber microscope to check the connector from RPC to ODF. The central core of the fiber
is not damaged, but outer part of the solid round is obviously damaged. As a result, the receive
light is not centralized, thus the received optical power is affected.
Step 4 Replace this part of the fiber and query the optical power on the T2000. The receive optical
power of the OPU is -25 dBm, which meets the demand.
----End

Platform
l Raman has stringent requirements on the fiber line. When Raman amplifiers are used, fiber
jumpers are easily damaged. Thus, pay more attention to the fibers during routine
maintenance.
l Even the central core of the fiber is not damaged, the damage to the outer part also affects
receiving of the optical power.
5.44 MC-A46 POWERALM Alarm in OptiX BWS 1600G

Caused by Switching off the Upper Subrack
POWERALM alarm in OptiX BWS 1600G caused by switching off the upper subrack.
Product
OptiX BWS 1600G
Fault Type
POWERALM
Symptom
During the initial acceptance of the OptiX BWS 1600G, the power box of some stations reports
the POWERALM alarm, which is critical alarm.
Cause Analysis
In practical application, some stations need not be configured with the upper subrack. Thus, the
power switch of the upper subrack is turned off.
Procedure
Step 1 After we turn on the power switch of the upper subrack, the alarm clears.
----End
None.
5.45 MC-A47 The CRC4_CROSSTR Alarm Is Generated

Because of Low Fiber Quality
The CRC4_CROSSTR is generated because of low fiber quality.
Product
OptiX BWS 1600G

Platform
Fault Type
CRC4_CROSSTR
Symptom
After checking the equipment at the station, the maintenance personnel finds that the
CRC4_CROSSTR alarm is generated on the board in slot 6 (SC2).
Cause Analysis
None.
Procedure
Step 1 The receive optical power is -31 dBm, which is within the normal range. In addition, the receiver
sensitivity of the SC2 board is -48 dBm.
Step 2 After the fiber jumper between the FIU and SC2 boards is replaced, the alarm persists. This
indicates that the fiber jumper is normal.
Step 3 On the SC2, move the fiber jumper from optical interface 1 to optical interface 2. The
CRC4_CROSSTR alarm at optical interface clears but it is generated at optical interface 2. This
indicates that the optical interfaces on the SC2 are normal.
Step 4 After the existing SC2 board is replaced with a new SC2 board, the alarm persists. This indicates
that the SC2 board at the local station is normal.
Step 5 After the existing SC2 board at the opposite station is replaced with a new SC2 board, the alarm
persists. This indicates that the SC2 board at the opposite station is normal.
Step 6 Therefore, it is determined that the alarm is caused by the fiber problem at the opposite station.
After the fiber at the opposite station is repaired, the alarm clears and the fault is rectified.
----End
After the OTDR is used for problem troubleshooting, it is found that the alarm is caused by the
fiber problem at the opposite station.
5.46 MC-A48 The T2000 Cannot Search the Wavelength

Trail
The T2000 cannot search the wavelength trail because engineers did not create the OAU fiber
connections between TDC and RDC.
Product
OptiX BWS 1600G
Fault Type
Other

Platform
Symptom
The T2000 supports the end-to-end management of wavelengths. However, engineers cannot
search out the OCH trail after fiber connections are created. The T2000 can search out OTS and
OMS trails.
Cause Analysis
l The T2000 license does not support this function.
l There are errors in the fiber connections.
Procedure
Step 1 Confirm on site that the T2000 license supports searching wavelength trails and OTS and OMS
trails can be searched out successfully. The license supports the wavelength trail management.
Step 2 Check the fiber connections: OTU board--M40/D40--amplifier board--FIU board. No problem
is found, and the optical interfaces on the OTU connected to the M40/D40 are normal.
Step 3 Engineer finds that the OAU board is used in the OTM. There are RDC and TDC interfaces on
the OAU. The two interfaces are used for connecting the DCM. If DCM is not used, the two
interfaces must be connected by a fiber. Engineer creates the fiber connection between TDC and
RDC and then searches the WDM trail on the T2000. Then, the wavelength trail (OCH trail) is
searched out.
----End
To point-to-point OTM, We need to create fiber connections in the following way: OTU--M40--
amplifier board--FIU---------FIU--amplifier board D40--OTU. In addition, the fiber linkage in
the reverse direction is consistent with the fiber linkage in the forward direction.
5.47 MC-A49 An Incorrect Setting of CRC Results in an

Interconnection Failure
The port of the router from company S is set to the SONET mode. An incorrect setting of CRC
results in an interconnection failure.
Product
OptiX BWS 1600G
Fault Type

Platform
Symptom
A X B1B2 C
Router Router
A<=>X<=>B1B2<=>C makes a WDM chain network. A, B1, B2 C and X are the WDM
equipment. A service is dropped from the fourth 2.5G interface on the E1OCU at A to the fourth
2.5G interface at C. A and C connect to the router from Company S. B1B2 is a site. Two OCUs
are connected in a back-to-back manner (connect each interface of the OCU with a fiber to pass
through services). X indicates the pass-through WDM optical amplifier sites in the middle.
The port of the router from Company S keeps reporting AIS. The state of the port is DOWN all
the time.
Cause Analysis
Interconnection problem.
Procedure
Step 1 Enable an optical interface outloop at sites A and C respectively. The router from Company S
works and its state is UP. In addition, a loopback signal is received. But if you enable an optical
interface outloop at B1 and B2, the port of the router does not work all the time.
Step 2 Enable a hardware loopback from site C to site A, but the port of the router does not work.
Assume that the port of the router from Company S is faulty. Through checking, it is found that
the port of the router from Company S is set to the SONET mode, but that of Huawei is set to
the SDH mode. Thus two settings conflict. After two settings are changed to be the same, the
port of the router still does not work. On the other hand, if you enable an optical interface outloop
at B1 and B2, the port of the router works. In addition, if you enable a hardware loopback from
site C to site A, the port of the router also works.
Step 3 Enable a loopback in the WDM equipment, and the port of the router works. The failure does
not lie in the WDM. Through checking, the length of the checking code at router A of Company
S is 32 digits and that at C is 16 digits. If the length is changed to be the same, the router works
normally.
----End
As interconnection is involved and the 155M service is enabled with a default setting of the
Cisco router, the same method is adopted to enable the 2.5G service. However, the method is

Platform
unavailable. In addition, the checking mode of ports of different routers from Company S is
inconsistent. (High- and low-end routers also have the problem).
5.48 MC-A50 Measure the PMD of an Optical Cable to

Determine the Quality of the Optical Cable
Measure the PMD of an optical cable to determine the quality of the optical cable.
Product
OptiX BWS 1600G
Fault Type
Other
Symptom
After obtaining the PMD value of an optical cable by using a test instrument (for example,
FTP-400), the Customer does not know how to assess the quality of the optical cable based on
the PMD value.
Cause Analysis
None.
Procedure
Step 1 The most of PMD of the fiber is less than 0.1 ps/km^, and one or two is less than 0.2 ps/km^.
This is compliant with the new standard of ITU (as stated in ITU-T G.652D and G.655C that
PMD should be less than 0.2 ps/km^). The limited distance of 10 Gbit/s Single-Channel PMD
exceeds 3000 km, and the limited distance of 40 Gbit/s Single-Channel PMD exceeds 80 km.
Note: ^ means evolution; PMD Delay indicates average differential group delay (DGD); the
PMD coefficient equals average DGD divided by the square root of fiber length. (numerator is
average DGD, denominator is the square root of fiber length)
----End
None.
5.49 MC-A52 Faults of End Face of the Fiber Connector

Cannot Be Identified
Faults of end face of the fiber connector cannot be identified by using an optical power meter.
Product
OptiX BWS 1600G

Platform
Fault Type
R_LOS
Symptom
The receive side of the OptiX BWS 1600G is configured with the RPC and OPU. A user
incorrectly removes other FC connector on the ODF. Then the OPU in the OptiX BWS 1600G
reports the LOS alarm.
Through checking, a field engineer confirms that the receive optical power of the OPU is lower
than -32 dBm. Combining the maintenance process, the engineer judges that the fiber from the
RPC to ODF is faulty. So the engineer performs the following operations: disable the RPC,
replace the fiber from the RPC to ODF, and clean the connector. After the RPC board is opened,
however, the LOS alarm persists on the OPU board.
The field engineer disables the RPC and then checks the fault with an optical power meter. The
receive optical power of the remote fiber on the ODF is -17 dBm. The value is normal. The
output optical power of the RPC (the laser is disabled) is only -35 dBm. However, the fiber from
the RPC to ODF has already been replaced. In addition, the fiber from the FIU to the optical
power meter is a new fiber. Hence, the fault reason is unknown.
Cause Analysis
l The optical power on the ODF is -17 dBm, but the output power of the RPC (if the laser is
disabled) is -35 dBm. Therefore the failure is between the ODF and FIU. In the previous
operations, only the fiber between the ODF and RPC is replaced. The connector of the
remote fiber of the ODF may be faulty.
l The output optical power is normal when it is tested through an optical power meter. As
the area of the optical device in the optical power meter is big, the emission angle is great.
Even if the tested connector is burnt, most output lights can be emitted in the optical device.
But when two connectors interconnect with each other, the situation changes. The same
light aperture of the opposite end connector is about only 8 um (single-mode), and two
connectors are touched closely. Therefore, the defect or dirt on any one connector will result
in reflection or absorption between the two. Finally, the insertion loss of the connector is
added.
l Hence, the optical power meter is unable to test whether the fiber connector connecting the
optical power meter is good or bad. To test the insertion loss of the connector, you need
connect another standard fiber to the connector and then test by using an optical power
meter.
Procedure
Step 1 After the remote fiber of the ODF is replaced, the attenuation turns to be normal. Use a magnifier
to check the fiber removed from the ODF. The connector is already burnt.
----End

Platform
l When you use an optical power meter to test the output optical power, you are not sure
whether the fiber connector connecting the optical power meter is good or bad.
l If the connector on the ODF in front of the RPC is burnt, replace the fiber on both sides of
the ODF.
5.50 MC-A53 OptiX BWS 1600G Cannot Be Deleted on the

T2000
The fiber connections are not deleted completely. Therefore, the WDM equipment on the T2000
is unable to be deleted.
Product
OptiX BWS 1600G
Fault Type
Other
Symptom
When the OLA is upgraded to the OADM in the OptiX BWS 1600G equipment, the Optical NE
type need be changed from OLA to OADM on the T2000. This need to delete the fiber
connections of the previous OLA.
After the fiber connections between the original OLA and the upstream/downstream NEs
(including the fiber connections between all optical amplifier units and between all optical
channel supervisory units) are deleted on the T2000, and then delete the OptiX BWS 1600G
equipment on the T2000, the system prompts "The board port is use, error:74505" error
information. Hence, the delete operation fails; however, all the fiber connections have been
deleted.
Cause Analysis
l The system misreports the error.
l In this equipment, another fiber connection is not deleted.
Procedure
Step 1 In the fiber management interface on the T2000, check each fiber connection of the equipment.
Some fiber connections between the TDC and RDC ports of the OAU on the NE are found not
deleted. After you delete the fiber connections, the equipment can be successfully deleted and
the fault is cleared.
----End
None.

Platform
5.51 MC-A54 After the Lasers of the Raman Amplifier Are

Disabled, the Optical Power Is Abnormal
After the lasers of the Raman amplifier are disabled, the optical power is abnormal.
Product
OptiX BWS 1600G
Fault Type
Symptom
At an OADM site, a channel of signals from an upstream site (this site has only one channel)
enters into the E3OAUC01 and the E3OAUC01 amplifies the signals. Finally, the signals are
dropped from MR2-DROP1 (the wavelength operates in 192.1 THz at 10 Gbit/s). Use an optical
power meter to test the optical power at the OUT interface of the E3OAUC01. The value is 4
dBm (the gain of the OAU is set to the maximum value: 33 dB). Connect the optical power meter
to the MR2-DROP1 interface and adjust the variable optical attenuator between the OAU03 and
MR2. The optical power is equal to or less than -12 dBm. Remove the variable optical attenuator
between the OAU03 and MR2. The optical power at the MR2-DROP1 interface is only -12 dBm.
Cause Analysis
Possible causes are as follows:
l The MR2 board is faulty.

l There are errors in the commissioning of the E3OAUC01 board.
Procedure
Step 1 This problem persists after the MR2 board is replaced. Hence, this problem is not caused by a
faulty MR2 board.
Step 2 Use an optical spectrum analyzer to measure the optical power. The optical power at the OTU
optical interface (192.1 THz) of the E3OAUC01 is –11 dBm and the optical power at the IN
optical interface is –29 dBm. Calculate the actual gain of the wavelength through the OAU. The
actual gain is –11 - (–29), that is, 18 dBm. The measured gain, however, is +4 – (–29), that is,
33 dBm, which is the maximum gain of the OAU. This indicates that the output optical power
at the OTU optical interface of the E3OAUC01 includes noise power, which is +4 – (–11), that
is, 15 dBm. These noise lights are generated by the pump light of the OAU. Two DCM modules
(80 km) are added between the TDC and RDC of the OAU. The intermediate insertion loss is
about 15 dB. In this configuration, the actual maximum gain of the OAU is 33 - 15, that is, 18
dB. According to the parameters of the E3OAUC01, the gain ranges from 20 dB to 33 dB. The
current gain, however, is not within the range. In this case, the noise lights may be amplified
abnormally. Hence, when gain is set to 33 dB, the lights with the optical power of 33 - 18 (that
is, 15 dB) are output as noise lights. Then, the output optical power of the OAU is relatively
low.

Platform
Step 3 Increase the input optical power of the E3OAUC01. This site is configured with an RPC. The
laser of the RPC may be disabled.
----End
Result
Enable the laser of the RPC. Then, the input optical power of the E3OAUC01 is increased and
thus this problem is solved.
l In the event of a small count of adding wavelengths, use an optical spectrum analyzer,
rather than an optical power meter to test the optical power. The optical power meter cannot
test the optical power accurately.
l The range of the insertion loss of the E3OAUC01 is 0-13 dB. Consider the insertion loss
of the DCM when you configure a DCM between the TDC and RDC. The maximum
insertion loss is 13-2 = 11 dB (2 dB is a fixed attenuation of the VOA of the E3OAU).
Otherwise, the actual gain is beyond the range and the noise optical power in the optical
output power is large.
l An RPC has two lasers. Enable both to amplify signals.
5.52 MC-A55 Improper DCM Distribution Causes

Abnormal Service
Improper DCM distribution causes abnormal service of the OptiX BWS 1600G equipment after
the upgrade.
Product
OptiX BWS 1600G
Fault Type
Bit Errors
BEFFEC_EXC
Symptom
For some WDM OptiX BWS 1600G equipment, it is configured as an OLA (B) at the initial
stage and is upgraded to an OADM. A service is added/dropped on the equipment. The LWFC
board is used as an OTU board and the fiber type is G.652.
55Km 80Km 84Km 137Km

A-OTM B-OLA C-OLA D-OLA E-OTM
Before Upgrade
55Km 80Km 84Km 137Km

A-OTM B-OADM C-OLA D-OLA E-OTM
After Upgrade

Platform
Four services are added between stations A and E. Before the upgrade, the performance of the
OTU boards on the two stations is normal. After the upgrade, bit error alarm BEFFEC_EXC is
detected on the newly-added LWFS board on station B that receives signals from station A. The
bit error rate is 10E-6, the board performance is not good but the received optical power of the
OTU board is normal. At the same time, the performance of the OTU boards on station A that
receives signals from station B is not good. The received optical power of each OTU board is
normal. This phenomenon seems abnormal.
Cause Analysis
l It is caused by the line optical power.
l It is caused by the dispersion compensation.
After reading the original engineering files, we found that the DCM configuration between
stations A and E is as follows: There is no DCM between stations A and B. Stations B and C
are configured with a DCM (C) respectively; stations C and D are configured with a DCM (C)
+ DCM(D) respectively; stations D and E are configured with a DCM (C) + DCM(D)
respectively. The total length of the line is 356 kilometers and the dispersion compensation
covers 340 kilometers. In principle, the compensation is enough. But the distribution of the DCM
is improper. From station C to station D, it is over compensated, and from station A to station
B, it is seriously under compensation. This may be the cause. Hence, the DCM distribution
should be adjusted.
Procedure
Step 1 Remove the DCM (C) between stations C and D to the stations A and B on site. Then, the bit
error alarm between stations A and B is cleared. The bit error of the OTU boards on stations A
and B is "0" before the correction. The performance of each board is very good. The problem is
resolved.
----End
When setting the DCM, consider the future hardware upgrade, for example, the budget
dispersion.
5.53 MC-A56 LWF Board Reports OTU_LOF Alarm

LWF board reports OTU_LOF alarm.
Product
OptiX BWS 1600G
Fault Type
OTU_LOF
SM_BDI

Platform
Symptom
On the link consisting of the OptiX BWS 1600G equipment, there are four stations. Station A
and station D are OTM stations; station B and station C are REG stations.
Stations A and D are configured with one LWF(E3LWF01) board; stations B and C are
configured with two TMR boards. The LWF board at station A reports the OTU_LOF alarm.
Station A Station B Station C Station D

O
SM_BDI SM_BDI I SM_BDI
OTU_LOF U N
T TMR TMR
LWF LWF
TMR TMR O
I U
N No Alarm No Alarm T
OTM REG REG OTM

Fault TMR
Query alarms of other stations and find all the TMR boards report the SM_BDI alarm along the
direction where signals are transmitted from station A to station D, whereas no alarm is reported
on the TMR at the receive end of station A. In addition, the LWF board at station D also reports
the SM_BDI alarm.
Cause Analysis
The main cause is probably that the TMR board at station B located in the receive direction of
station A is faulty.
Procedure
Step 1 Exclude the possibility that fibers are improperly connected.
Step 2 Replace the LWF boards on the two OTM stations. The alarms, however, persist.
Step 3 Swap the transmit TMR with receive TMR at station B, as shown in the following figure. It is
found that the OTU_LOF alarm is reported on station D, and the SM_BID alarm occurred on
one TMR at station C clears but the other TMR at station C has the SM_BID alarm. At this stage,
it is indicated that the TMR at station B is probably faulty. Replace the faulty TMR at station
B, and the alarms clear.
TMR Exchange
Fault TMR
Station A Station B Station C Station D
O
No Alarm No Alarm I OTU_LOF
OTU_LOF U N
T TMR TMR
LWF LWF
TMR TMR O
I U
N SM_BDI SM_BDI T
OTM REG REG OTM
Step 4 If the alarms persist after the above three steps, you need to swap over the TMR boards at station
C to locate the fault.
----End

Platform
l The OTU_LOF alarm is generated when the attenuation is excessively high or the frame
loss occurs in the optical signals.
l If the attenuation proves to be normal, it is confirmed that unframed signals are detected
at the opposite station or the board is faulty.
l The reason for the TMR board reports the SM_BDI alarm is that the opposite station has
receive alarm signals. In this case, one of the TMR boards at station B is probably faulty.
Locate the faulty by swapping the two TMR boards at station B.
5.54 MC-A57 How to Clear OTU Alarms Because of Unused

Ports
How to clear OTU alarms because of unused ports.
Product
OptiX BWS 1600G
Fault Type
ODU_AIS
SM_BDI
MS_AIS
Symptom
Usually in a DWDM system, some client-side ports on the OTU board are not used by customers.
If the ports are enabled, relevant alarms, such as the ODU_AIS , SM_BDI , and MS_AIS, will
be reported to the T2000. These alarms will confuse customers or maintenance personnel that
services are abnormal.
Cause Analysis
If the T2000 detects that a client-side or WDM-side port is set to USED, the T2000 will report
the alarms.
Procedure
Step 1 Right-click the NE and then choose NE Explorer from the shortcut menu.
Step 2 Select the OTU.
Step 3 In the Function Tree, choose Configuration > WDM Interface > General Attribute.
Step 4 Set the Channel Use Status parameter to Unused.
Step 5 Click Apply.
Step 6 Browse the alarms to check whether the alarms clear.
----End

Platform
It is useful to know the status of the client-side ports on the OTU: used or unused. This is helpful
for alarm analysis and troubleshooting. This operation cannot be performed without customer's
permission and supervision.
5.55 MC-A59 Mismatch of SC2 Models Causes Frequent

Reporting of the CRC4_CROSSTR Alarm
The OptiX BWS 1600G system frequently reports the CRC4_CROSSTR alarm because of the
mismatch of SC2 models.
Product
OptiX BWS 1600G
Fault Type
Others
Symptom
In a WDM ring network of the OptiX BWS 1600G NEs, the SC2 board on one NE frequently
reports the CRC4_CROSSTR alarm. As a result, this NE and downstream NEs that communicate
with this NE through ECC become frequently unreachable to the T2000.
Cause Analysis
The model of the SC2 board on the opposite NE does not match that on the local NE.
As the distance between the two NEs is more than 120 km, the local NE uses the SSE1SC2 board
whose launched optical power is as high as is 10 dBm. The SC2 on the opposite NE is the SC2
board with the common optical power, that is, -4 dBm. The CRC4_CROSSTR alarm is reported
on the local NE because the optical power received from the opposite NE is excessively low.
As the RPC board is used, which causes noise, the optical power is -30 dB, which is far higher
than the board sensitivity. As a result, the ECC communication has an exception.
Procedure
Step 1 Check the received optical power on the local NE, which is -30 dBm. Such optical power or
more for the SC2 is normal. When the received optical power is more than -48 dBm (sensitivity),
the board can work normally.
Step 2 Perform an outloop on the local SC2. The alarm is cleared. The fault persists even after the SC2
is replaced at the local station.
Step 3 The launched optical power of the opposite SC2 is -4 dBm and attenuation on the line is 50 dB.
The received optical power of the local SC2 should be -54 dBm, but is actually -30 dBm.
Step 4 An RPC is used on this fiber cable. The Raman amplifier amplifies the supervisory channel to
a little extent, but causes noise. The FIU at the receive end, however, just splits the light but does
not filter wavelengths. As a result, the SC2 receives much noise.

Platform
Step 5 The SC207 board is used on the opposite NE. When the SC207 is replaced with the SC209 with
high launched optical power, this fault is rectified.
----End
None.
5.56 MC-A62 The Minimum Optical Power of the SC2 Is

Detected As -35 dBm
Because the fibers or the fiber jumpers are in fault, the minimum optical power of the SC2 is
detected as -35 dBm.
Product
OptiX BWS 1600G
Fault Type
Optical power abnormity
Symptom
A WDM chain with the OptiX BWS 1600G NEs is deployed in an office. The line attenuation
between site A and site B is about 30 dB. One day, the received optical power of the two sites
decreases by 8 dB and the OSNR also decreases. The optical power of the supervisory channel,
however, remains unchanged, which is -35 dBm.
Cause Analysis
As the optical power of the supervisory channel remains unchanged, the cause does not lie in
the fiber cable or out-frame ODF, but in the span between the in-frame FIU and OAU of the two
sites.
Procedure
Step 1 Test the optical power of MON interfaces of the OBU and FIU boards for transmitting signals
to the opposite end at the two sites.
Step 2 The optical power difference of the two MON interfaces is as slight as not more than 1 dB. It
can be concluded that the no problem exists between the OBU at the transmit end and the RC
port of the FIU, and no problem exists on the OUT interface of the FIU. The detected optical
power of MON interfaces is 1% of the optical power of the OUT interface. If the OUT interface
is faulty, the receiving of the SC2 at the opposite end is affected.
Step 3 The previous analysis shows that the problem lies in the receive port of the FIU or the fiber from
the FIU to OAU. There is low possibility that the two stations have the same fault. In addition,
for further test, the optical path must be disconnected. To locate the problem for once, re-
compose the fault locating scheme.

Platform
Step 4 The cable problem can be excluded if the detected optical power of the SC2 is consistent with
the actual optical power. The received optical power of the SC2 for receiving signals from the
opposite end is tested after suspicion. The actual value is -35 dBm. If the transmitted optical
power of the SC2 is -4.2 dBm, it is concluded that the attenuation of the supervisory channel is
around 40 dB and the attenuation of the service channel is around 38 dB.
Step 5 It can be concluded that cables and the fiber jumper between the FIU and ODF of the two stations
are faulty. Then, test cables and the ODF with the cooperation of users. Locate and rectify the
fault.
----End
None.
5.57 MC-A63 Bit Errors Occur in a DWDM 10G Network

Due to the Uncorrect PMD
The bit errors occur in a DWDM 10G network due to the uncorrect PMD.
Product
OptiX BWS 1600G
Fault Type
OTU_LOF
Bit error
Symptom
After the fiber of the OTM site (node CLS1 to node CLS2) is replaced, the MSBBE bit errors
and OTU_LOF alarm occur on the OTM site.
Cause Analysis
The bit errors occur in the network due to the uncorrect PMD.
Procedure
Step 1 The optical power is measured and adjusted to the reference value. After the adjustment, bit
errors and the alarm are cleared. Half an hour later, the bit errors and alarm occur again.
Step 2 Add or remove the DCM to extend the distance from 5 km to 10 km. Then, the bit errors and
alarm are cleared. One hour later, the bit errors and alarm occur again.
Step 3 Then, the customer checks the features of the new fiber (chromatic dispersion and polarization
mode dispersion). The check shows that the chromatic dispersion (CD) in the fiber is normal
but the polarization mode dispersion (PMD) is excessively high. The problem is solved when
the customer replaces the fiber.
----End

Platform
PMD coefficient relation is given in Table 5-1.
Table 5-1 PMD coefficient relation
Bit Rate(Gbit/s) Max PMD(ps) PMD Coefficient (ps.km)

a a
2.5 40 < 2.0
10 10 (with no FECb) < 0.5
40 2.5 < 0.125
a: Standards suggest a value for 10 Gbit/s only. Values at other data rates are nonetheless
accepted by the industry.
b: Most long-haul instruments perform forward error correction (FEC).
5.58 MC-A64 Many BD_STATUS Alarms Occur Due to the

ECC Storm
Many BD_STATUS alarms occur due to the ECC storm.
Product
OptiX BWS 1600G
Fault Type
NE offline
ECC Storm
BD_STATUS
Symptom
In a network of the OptiX BWS 1600G, many NEs becomes unreachable to the T2000. The NE
icons become grayed and then normal. In this process, each board reports the BD_STATUS
alarm. This problem occurs several times a week, and lasts for one to two hours each time.
NOTE
Recently, many NEs are expanded by adding boards or subracks. The new boards are all the LBE and
TMX.
Cause Analysis
l Conflict of IDs causes the BD_STATUS alarm and NEs to be unreachable.

Platform
l In a complex network, there may be more than one route available for inter-network
communication due to application of the OSC, ESC, and extended ECC. As a result, the
ECC data overflows to cause incorrect IDs and incorrect ECC routes.
l When an OptiX BWS 1600G NE is added, the DCN is configured improperly.
Procedure
Step 1 Extract the log file of an OptiX BWS 1600G NE and check the ECC route. Many ECC routes
are found, the number of which exceeds the number of NEs, that is, 20. When a new ID is created
on the T2000, the T2000 prompts that the ID exceeds the range.
Step 2 Check the OptiX BWS 1600G subrack. The extended ECC and ECC are found enabled. As
planned, the extended ECC communication of the gateway NE at site OTM is to be disabled.
Then, the communication over the ECC route between gateway NEs are terminated. Many NEs,
however, are connected now. In this way, the ECC communication is terminated for most NEs
in the network.
The previous analysis shows that the problem may be due to an ECC storm.
Step 3 Disable all the extended ECC communication and most ESC communication on the OptiX BWS
1600G. Observation for weeks shows that the problem does not occur.
Step 4 It is suspected that the ID conflict causes the BD_STATUS alarm when new boards are
configured. Finally, check on the subrack shows that the SCC is reset frequently in the case of
the BD_STATUS alarm. Now, the alarm is cleared.
An ECC storm causes the SCC to be so busy (confirmed by reset log) that it fails to respond to
the signals of in-service boards. Then, the BD_STATUS alarm occurs.
----End
None.
5.59 MC-A65 The Gain of the RPC Board Cannot Exceed 10

dB Due to Excessively High Attenuation of Flange
The gain of the RPC board cannot exceed 10 dB due to excessively high attenuation of flange.
Product
OptiX BWS 1600G
Fault Type
Other
Symptom
The OptiX BWS 1600G runs in a chain network (A-B-C-D). The RPC board is used between
sites B and C to extend the transmission distance. One day, a fiber cut occurs between stations
B and C. After the fiber is repaired, the optical power received by station C from station B is

Platform
excessively low. As a result, services cannot be provided between the two stations and the gain
of the RPC does not meet the requirement. It is suspected that the problem lies in the RPC board,
which may be faulty. Prepare a standby RPC and tail fibers to handle the problem on site.
Cause Analysis
l The fiber cable is faulty.
l The tail fiber and flange are faulty.
l The RPC board is faulty.
Procedure
Step 1 The laser must be disabled before the operation. When connections are completed, enable the
laser. Disable the laser before operating the tail fiber.
Step 2 Double-click the ONE icon on the Main Topology. The NE Panel tab is displayed. Right click
the NE icon and select NE Explorer. In the NE Explorer, select RPC board and choose
Configuration > WDM Interface from the Function Tree. Select the By Board/Port
(Channel) radio button. Select Channel from the drop-down list. Double-click Laser Status
field and select Close.
Step 3 Test the line by using an OTDR. The test shows that the fiber cable is normal. Then, connect
the fiber and measure the receive end with an optical power meter. The optical power at the
receive interface of the RPC board is measured as -29 dBm.
Step 4 According to the technical specification of the RPC, the optical power of the RPC should range
from -25 dBm to 3 dBm. Then, it is suspected that this problem is caused excessively low input
optical power of the RPC.
Step 5 The normal RPC can achieve a gain higher than 10 dB regardless of how much the received
optical power is. Therefore, the excessively low optical power does not cause the problem.
Step 6 The Raman amplifier of the RPC board has two pump lasers and works normally only when the
two pump lasers are normal. When enabled, the two pump lasers should output the same optical
power in a certain range (higher than 23.5 dBm). Then, the gain of the RPC board is in the normal
range. Query of the 15-minute performance shows the following information:
1 15m 2007-3-10 10:15:26 pumpoopcur 1 1 24
1 15m 2007-3-10 10:15:26 pumpoopcur 1 2 24
The two pump lasers are enabled and output 24 dBm optical power. The Raman amplifier does
not cause this problem.
Step 7 When the E2000 tail fiber exclusive for the RPC is replaced, the problem persists. The fiber
cable, fiber, and board are all fine. Only the connector is not replaced.
Step 8 Replace the flange between the tail fiber and the fiber cable. Then, the fault is rectified.
----End
None.

Platform
5.60 MC-A66 The Received Optical Power of Downstream

Stations Is not Flat
The received optical power of downstream stations is not flat because the designed pass-through
wavelengths are not connected.
Product
OptiX BWS 1600G
Fault Type
IN_PWR_LOW
Symptom
The result of commissioning the OptiX BWS 1600G system at station A shows that the three
LWC1 boards use the 21st wavelength, 23rd wavelength, and 40th wavelength. When the fibers
are properly connected, the optical amplifier board is adjusted to the nominal value. The LWC1
boards that use the 21st wavelength and the 40th wavelength report the IN_PWR_LOW alarm.
Cause Analysis
l The tail fiber or optical attenuator is faulty.
l The transmit part of the opposite end or the receive part of the local end is faulty.
Procedure
Step 1 Remove the tail fiber of the D40 and then measure the launched optical power of each optical
interface of the D40. The launched optical power of the LWC1 boards that use the 21st
wavelength and the 40th wavelength is about 5 dB different from that of the LWC1 board that
uses the 23rd wavelength. Check on the upstream station shows that the upstream 2*OTM station
B has only one OTU (LWC1 board using the 23rd wavelength) and only the LWC1 board of
No.1 OTM is connected to the LWC1 board of No.2 OTM on the client site. Further check on
the upstream OTM station C shows that station C has three LWC1 boards, just like the local
station.
Step 2 According to the design document, the 21st and 40th wavelengths are to pass through station B
but they are not connected. To connect the two wavelengths, connect the interface on D40 at
station OTM1 for the two interfaces to the mapping interface on M40 of station OTM2.
Step 3 When the alarm is cleared, check the input optical power of the three local LWC1 boards. The
optical power flatness meets the requirement.
----End
None.

Platform
5.61 MC-A67 The GE Port on the Client Side Reports

LINK_DOWN Alarm
Due to the auto negotiation, the GE port reports LINK_DOWN alarm when FDG connects to a
GE port of Cisco 12410 router on the client side.
Product
OptiX BWS 1600G
Fault Type
Service interruption
Symptom
In one DWDM network, two type of GE services are transmitted over wavelengths, which are
generated by the FDG board. When the FDG connects to Cisco Router 12410, the GE port on
the router reports LINK_DOWN alarm.
Cause Analysis
This problem occurs because the FDG board is improperly connected to the client-side device
or the fiber between them is damaged. If auto-negotiation function is required when the FDG
connects to the client-side device, this problem also occurs.
Procedure
Step 1 Check the fiber that connects the client-side port on the FDG to the router.
Step 2 Check the input optical power on the T2000. The input optical power is found normal.
Step 3 Use the optical power meter to check the output optical power of the client-side device. The
output optical power is found normal.
Step 4 If Cisco router still reports LINK_DOWN. Perform the following setting:
1. In the NE Explorer, select the desired FDG board and choose Configuration > WDM
Interface from the Function Tree.
2. Select By Board/Port(Channel).
3. Select Channel from the drop-down list.
4. Adjust the Auto Negotiation as Enabled in the Basic Attributes tab and click Apply.
Step 5 Confirm that the port on Cisco router reports LINK_UP.
----End
None.

Platform
5.62 MC-A68 OTU Boards Report the IN_PWR_LOW Alarm

Due to Wavelength Wander
The wavelength wander of an OTU board causes the downstream OTU boards to report the
IN_PWR_LOW alarm.
Product
OptiX BWS 1600G
Fault Type
IN_PWR_LOW
Symptom
The OptiX BWS 1600G is networked in the chain mode: OTM----OTM (A)----OTM (B) ----
OTM, that is, multiple OTM stations form a ring of 7 channels (one is standby). One day, the
IN interface of the 18th-channel LWC board at station B reports the IN_PWR_LOW alarm.
Cause Analysis
l The LWC board of station B is faulty or a fault in the fiber from the D40 to LWC causes
excessively high attenuation.
l The launched optical power of the opposite station A is abnormal. As a result, the local
received optical power is abnormal.
l Other boards are faulty, for example, the M40 at the transmit end or the D40 at the receive
end is faulty. Because these two boards are passive optical components, they are less likely
to be faulty.
l Other causes.
Check the optical power of the equipment level by level from the downstream to the upstream
according to the signal flow for fault locating.
Procedure
Step 1 Measure the input optical power of the D40 and LWC at station B. Excessively low optical
power causes the OTU board to report the alarm.
Step 2 Scan the wavelengths of the D40 and OAU at station B with a multi-wavelength meter. The 18th
wavelength is absent.
Step 3 The wavelength ranges of the LWC and M40 at station A are in consistent. The 18th wavelength
is not input to the M40. Measure optical interface 23 of the M40 at station A. the input optical
power is measured as -2 dBm (normal).
Step 4 Scan the wavelengths of the M40 board at station A. The 18th wavelength is still absent. Use
the optical power meter to measure the optical power, which is found normal.

Platform
Step 5 Directly scan the wavelengths of the OUT interface of the 18th-wavelength LWC board. The
root cause of the fault is finally located. The scanning result shows that the optical power of the
18th wavelength is -2 dBm (normal value) and the wavelength is 1547.468 nm. The standard
wavelength, however, is 1546.92 nm. The wavelength wander is up to 0.5 nm. In the WDM
system, the wavelength wander range of the OTU board should be not more than 0.15 nm.
Step 6 Temporarily solve the problem by using the standby wavelength between the two stations. Apply
for a new 18th-wavelength LWC board and replace the faulty LWC board.
----End
None.
5.63 MC-A69 Shutdown of the RPC Laser Interrupts SDH-

Layer Services in a DWDM Network
The shutdown of the RPC laser interrupts SDH-layer services in a DWDM network.
Product
OptiX BWS 1600G
Fault Type
Service interruption
Symptom
In a DWDM network, there is one MSP ring with four nodes. To perform certain operations, the
customer shuts down the RPC laser between two nodes. As a result, services between these two
nodes are interrupted, though the MSP is configured. When the RPC laser is enabled, the services
are restored.
Cause Analysis
When the RPC laser is shutdown, signals are still received but not amplified by RPC. There is
no SF event (for example, R_LOS) on related OTU or optical boards. In this case, if the SD flag
is set as disabled, the MSP protection switching does not function and the services are
interrupted.
Procedure
Step 1 Check on the MSP parameters shows that the SD flag is not selected. Shutdown of the RPC
degrades the signals but does not cause a signal failure. Therefore, the MSP protection switching
is not triggered. When the SD flag is enabled, shutdown of the RPC successfully triggers the
MSP switching.
----End

Platform
None.
5.64 MC-A71 Excessive Attenuation Results in That the

Gain of the E3OAU Cannot Be Set
The excessive attenuation between the TDC and RDC ports results in that the gain of the E3OAU
cannot be set.
Product
OptiX BWS 1600G
Fault Type
Optical amplifier board
Symptom
In a new project, during network commissioning, the gain of the E3OAU board at a station needs
to be enhanced. The gain value should be within the range and can be adjusted. The gain,
however, cannot be set no matter through the network management system (NMS) or the
command line.
Cause Analysis
According to the query, the output power at the TDC port of the E3OAU board is 10.5 dBm and
the input power at the RDC port is -9.5 dBm. The attenuation between the TDC and RDC ports
is 20 dB. Therefore, the gain of the board reaches the maximum and cannot be adjusted.
The reason is that the attenuation between the TDC and RDC ports is excessive.
Procedure
Step 1 The on-site engineers remove the tail fiber from the DCM module between the TDC and RDC,
reconnect the OAU, and then re-query the gain. The re-query shows that the attenuation between
the TDC and RDC decreases to about 8 dB. Through the network management system, the gain
of the board can be set normally. The fault is ratified.
----End
None.
5.65 MC-A72 The OTU_LOF Alarm Reported in the LWC1

Due to Wrong Regenerator Board
The OTU_LOF alarm reported in the LWC1 is caused by the Wrong Regenerator Board in the
BWS1600G.

Platform
Product
OptiX BWS 1600G
Fault Type
OTU_LOF
Optical transponder board
Symptom
The engineers are doing a test with 4 different wavelength (192.1THz, 192.2THz , 192.3THz
and 192.4THz) in a network. The wavelength_1 and wavelength_2 are using LWC1 board and
wavelength_3 and wavelength_4 are using LWC board. In the REG station, four TRC boards
are used to be the signal regeneratation.
The wavelength_3 and wavelength_4 are OK. But the wavelength_1 and wavelength_2 are
alarming OTU_LOF.
Cause Analysis
The LWC1 is a tunable board and a TRC can not be used as the regenerator board of the LWC1
in the regeneration station. In this station, you should use a TRC1 board with the tunable function.
Procedure
Step 1 If the LWC is used, the regenerator board should be a TRC.
Step 2 If the LWC1 is used, the regenerator board should be a TRC1.
----End
None.
5.66 MC-A74 The FDG Reports the T_DATA_LOST and

R_DATA_LOST Alarms
The FDG reports the T_DATA_LOST and R_DATA_LOST alarms because of the fault
configuration of the client GE interface.
Product
OptiX BWS 1600G
Fault Type
Equipment interconnection
T_DATA_LOST
R_DATA_LOST

Platform
Symptom
In a DWDM network, a new wavelength is configured on the FDG boards. When the customer
connects the GE routers, the FDG boards report the T_DATA_LOST and R_DATA_LOST
alarms.
The T_DATA_LOST and R_DATA_LOST alarms do not affect services. When the customer
runs a ping command to test the trail connectivity and the packets are lost.
Cause Analysis
The T_DATA_LOST alarm is client-side transmitting data lost. The board regularly checks the
Ethernet performance event "Good Octets Transmitted" and compares the number with the
number of last time. The alarm occurs when the two numbers are the same, which indicating
that the board does not transmit any data.
The R_DATA_LOST alarm is client-side receiving data lost. The board regularly checks the
Ethernet performance event "Good Octets Received" and compares the number with the number
of last time. The alarm occurs when the two numbers are the same, which indicating that the
board does not receive any data.
The T_DATA_LOST and R_DATA_LOST alarms indicate that the FDG receives no packets
in a period.
When customer runs the ping command, packets cannot be sent continuously. As a result, the
FDG receives no packets in this short period and thus reports the T_DATA_LOST and
R_DATA_LOST alarms.
Procedure
Step 1 If no packets are lost when the customer runs the ping command, it indicates that the link is fine.
Step 2 To clear T_DATA_LOST and R_DATA_LOST alarms, check the KEEP ALIVE parameter of
one router. If the parameter is enabled, the router continuously sends small packets to inform
the remote equipment that the link is up.
Step 3 This function should be enabled on the FDG clients to avoid the T_DATA_LOST and
R_DATA_LOST alarms.
----End
None.
5.67 MC-A75 Bandwidth Decreases and Service Rate

Becomes Lower Due to Improper Setting
The improper setting of the interconnected FC switch results in that the bandwidth of the LOG
board decreases and the service rate becomes lower.
Product
OptiX BWS 1600G

Platform
Fault Type
Other
Symptom
The FC service on the LOG board slows down and no operation is performed on the LOG
previously.
Cause Analysis
The service on the LOG board slows down. The engineer checks the alarms and performance
events of the LOG board, and finds no exception. Therefore, the LOG may be probably normal.
The engineer checks the data on the interconnected FC switch with the customer and finds the
history data is over the normal performance value, which indicates that the bandwidth on the
transmit side of the switch is insufficient. This why the data slows down. Therefore, the cause
lies in the setting of the switch.
Procedure
Step 1 Theoretical analysis on the relation between the FC service bandwidth and packet length shows
that sufficient bandwidth is available only on the following conditions if the distance from the
site is 75 km:
1. The BBC of the FC switch should be greater than 64.
2. The frame size of the FC switch should be greater than 2000.
Step 2 In fact, the customer has changed the frame size of the switch to 1000, which leads to this
problem. The frame size of the interconnected switch is changed to 2048.
Step 3 This problem is solved.
----End
None.
5.68 MC-A76 The PMU Cannot Work Normally

The PMU cannot work normally because the communication setting of the PMU is improper.
Product
OptiX BWS 1600G
Fault Type
Other

Platform
Symptom
During deployment of a remote pump project, the PMU on the SS07PBS cannot work normally
and the green indicator and the red indicator blink quickly. In addition, the PMU cannot be
searched out through the T2000 or Navigator.
Cause Analysis
Observation on NEs A, B, C, and D shows that this symptom occurs on every site and the PMU
is not in position.
Each site with the PMU out of position has a remote pump system and the ROP is in the lower
subrack of the cabinet.
Communication setting of the PMU may be improper. By default, the PMU communicates with
the lower subrack. In this case, the lower subrack with the ROP, however, has no communication
interface. The DIP switches should be set so that the PMU communicates with the middle
subrack.
Procedure
Step 1 Under the control of DIP switches 1 and 2, the PMU communicates with the WDM subracks.
1. When the DIP switch is set to ON(0) ON(0), the PMU communicates with the upper
subrack.
2. When the DIP switch is set to ON(0) OFF(1), the PMU communicates with the middle
subrack.
3. When the DIP switch is set to OFF(1) ON(0), the PMU communicates with the lower
subrack.
4. When the DIP switch is set to OFF(1) OFF(1), it makes no sense.
Step 2 According to the previous settings, the DIP switch is set to (0, 1).
Step 3 After installation, the problem is solved.
----End
None.
5.69 MC-A77 Improper Configuration of Protocol Channels

Results in a Failure of the ALC to Start
The improper configuration of protocol channels results in a failure of the ALC to start.
Product
OptiX BWS 1600G
Fault Type
Optical power management

Platform
Symptom
The network topology is OTM1--OADM--OTM2. The ordinary ALC mode (wave detection
mode) need be configured in this network. At the initial stage of configuration, only the forward
ALC (OTM1->OADM->OTM2) is configured, and the MCA board is configured at the OTM2
site. The OSC units are configured as follows: SC1 for OTM1, SC2 for OADM, and SC1 for
OTM2. The protocol channel is configured as follows: SC1 of OTM1 as east, SC2-1 of OADM
as west, SC2-2 of OADM as east, and SC1 of OTM2 as west. After other ALC configuration is
complete, the ALC function is supposed to start. In this case, the system, however, prompts that
the ALC of the OADM site is querying reference. A period later, the ALC still cannot start.
Cause Analysis
Check on all ALC-related configurations on the NMS shows no exception.
Then, all NE data is re-loaded and ALC is re-configured. The ALC, however, still cannot start
and the NMS prompts the same message. Therefore, the data and configurations are correct.
Then, the fiber connection direction of the OSC may be inconsistent with the configured protocol
channel.
Querying of the engineering document shows that the actual OSC connection of the OADM site
is SC2-1 for OTM2, and SC2-2 for OTM1.
Procedure
Step 1 Change the protocol channel configuration of the OAMD site for consistency with the actual
configuration.
Step 2 Then start the ALC. The ALC starts normally.
----End
None.
5.70 MC-A78 When the IPA Is Set or Deleted, the OAU

Alarm Threshold Changes Due to Version Features
When the IPA is set or deleted, the OAU alarm threshold changes due to version features.
Product
OptiX BWS 1600G
Fault Type
Optical power management
Symptom
After the IPA service pair is created, the customer finds that the LOS alarm threshold of the
OAU after RPC changes from -40 dBm to -15 dBm. After the configuration of the IPA pair is

Platform
deleted, the LOS alarm threshold of the OAU does not change back to -40 dBm but change to
-28 dBm. After the OAU is warm reset, the threshold changes back to -40 dBm.
Cause Analysis
In the case of certain WDM versions, the alarm threshold of the OAU is modifiable. In this case,
the customer manually changes the default alarm threshold from -28 dBm to -40 dBm. Now,
Huawei WDM products have a feature that enables the alarm threshold of OAU to change back
to default value of the system instead of changing to the value set by the customer after the IPA
is deleted. When the OAU is reset, the threshold changes to the value set by the customer.
Procedure
Step 1 Reset the OAU to restore threshold value previously set.
----End
None.
5.71 MC-A79 The MCA Board Reports an Execution Failure

The MCA board reports an execution failure if the wavelength is not set to the monitor status.
Product
OptiX BWS 1600G
Fault Type
Other
Symptom
To analyze the OSNR, a user sets the MCA board but mistakenly sets a wrong wavelength to
the monitor status. As this wavelength is received from the opposite end, wavelength 192.3 nm
of port 1 need be set to the monitor status. Instead, the user mistakenly sets wavelength 192.3
nm of port 2 of the MAC card to the monitor status. During the analysis on the laser spectrum,
the MCA board prompts execution failure.
Cause Analysis
A wrong port is selected for monitoring.
Procedure
Step 1 Set the right port and wavelength received from the opposite end to the monitor status.
Step 2 The problem is solved.
----End

Platform
None.
5.72 MC-A80 Intermittent BEFFEC_EXC Alarm at IN/OUT

optical interfaces on LWF board
The intermittent BEFFEC_EXC alarm is reported at IN/OUT optical interfaces on the LWF
board housed in slot 10 of one surack NE.
Product
OptiX BWS 1600G
Fault Type
Other
BEFFEC_EXC
Symptom
The intermittent BEFFEC_EXC alarms are reported at the IN/OUT optical interfaces on the
LWF board housed in slot 10 of one surack NE.
Initial operations:
l Check connection.
l Replace MR2 board in slot 8, which is connected with the IN optical interface of LWF
board.
l Still alarm at NMS.
Expected operations from vendor:
l Clear the Problem

l Provide User Guide (faulty description and problem handling)
l Provide Maintenance Manual Books
Cause Analysis
The LWF board has the FEC function of correcting bit errors generated in the transmission over
DWDM equipment. If the number of bit errors is beyond FEC correction ability, the number of
uncorrectable bit errors and alarms is reported.
Then, initialize the current performance data and observe the NMS after a certain period. The
NMS shows that the channels that report bit errors and number of bit errors are not stable.
If bit errors occur in one direction, it indicates that the fault is related to unidirectional optical
fibers or boards. In this case, only the local station has bit errors. This means that the fault happens
only in one direction.

Platform
Procedure
Step 1 Query performance events
Step 2 After 15m performance, bit errors occur in local station for the signals that are received from
the opposite station and pass through 5 OLA stations. The channels that report bit errors and
number of bit errors are not stable.
Step 3 No bit error occurs on the signals sent from the opposite station to the local station.
Step 4 Conclusion: Bit errors occur in one direction.
Step 5 Check optical power.
1. Check the optical power of the amplifier at each station on the NMS. The optical power is
identical with the value specified during engineering commissioning.
2. Check optical power of the LWF at the local station on the NMS. The optical power is
identical with the value specified during engineering commissioning.
Step 6 Adjust optical power:
1. Adjust the optical power. With OSNR guaranteed, increase the input optical power of the
optical fiber with bit errors. Observe the variation of the number of bit errors on the NMS.
It shows the number of bit errors increases with the optical power. Reduce the input optical
power of the fiber. It shows that the number of bit errors decreases with the optical power.
Step 7 Check the transmit power of the LWF board in slot 10 in the local station, which the transmission
direction is from the opposite station to the local station. Trace step by step each site the OAU
receiving power and transmit go to the local station also power gain. Make sure the power receive
and power transmit adjust equally or difference is not significant.
Step 8 The launched optical power of the upstream station is excessively high about +15 dBm and the
OAU gain +28 dB.
Step 9 The bit errors are caused by the non-linearity of optical fiber. Reduce the input optical power in
the local station and bit error problem is solved.
----End
None.
5.73 MC-A81 The ALC Cannot Run

The ALC cannot run.
Product
OptiX OSN 6800
Fault Type
ALC
ECC Status
Optical Power Management

Platform
Symptom
The ALC feature is configured on the OptiX OSN 6800 NEs (A with OBU and B with OAU).
The ALC, however, does not function to automatically adjust the link. A is the gateway NE.
Cause Analysis
Related documents only mention that the ECC channel is required and available on the SC1/
SC2 board, which, however, is not configured on site. The R&D personnel confirms that the
OptiX OSN 6800 supports ALC through ESC.
Check on the ECC routes of A and B shows B cannot be logged into sometimes.
Procedure
Step 1 In this case, the ECC link may be not stable. Then, a pair of OTU boards are added on A and B
and are connected through fibers. Then, the ECC is fine for a long time and the ALC functions.
----End
The OptiX OSN 6800 supports ALC through ESC and the ALC requires stable ECC status.
This case can be applied to the OptiX Metro 6100 V100R008 and OptiX BWS 1600G V100R006
or above.
5.74 MC-A82 Analysis of the POWER_FAIL Alarm on the

OptiX OSN 6800 and Solution
The SCC board reports the POWER_FAIL alarm due to a battery failure.
Product
OptiX OSN 6800
Fault Type
POWER_FAIL
Symptom
During commissioning of the OptiX OSN 6800 in a pilot project, the SCC board reports the
POWER_FAIL alarm.
Alarm Parameters (hex): 0x05 0xff 0xff 0xff 0xff
Cause Analysis
The OptiX OSN 6800 is new equipment and several OptiX OSN 6800 NEs have this alarm. It
is suspected that the power module is faulty.

Platform
After cutting off the power of the OptiX OSN 6800 then power on, the equipment time and date
information is lost and changes to the initial time and date, that is 1990-01-01 00:00:00. Then,
the battery on the SCC may be faulty.
Procedure
Step 1 Remove the SCC board and check the jumper that controls the battery. This jumper is found in
an incorrect state.
Step 2 Change the state of the jumper so that the battery works.
Step 3 Insert the SCC. The POWER_FAIL alarm is cleared.
Step 4 Reset the date and time.
Step 5 Reset the equipment and the time and date information is not lost. The problem is solved.
----End
The jumper is to be set before delivery, the setting on sit is not required to be fixed normally.
5.75 MC-A83 The OptiX OSN 6800 Is Not Reachable When

the NE IP Is Modified
The OptiX OSN 6800 is not reachable when the NE IP is modified.
Product
OptiX OSN 6800
Fault Type
NE Offline
Symptom
The NM_ETH port of an NE is directly connected to the PC through a network cable. No anomaly
occurs before the NE IP is modified. After the NE IP is modified, the PC cannot reach the NE.
This anomaly occurs on two sites.
Cause Analysis
This problem may lies in the NE or PC. The physical connection between them, however, is
fine. Then, it is suspected that the anomaly lies in the IP communication or SCC board.
The R&D confirms that the SCC board is fine. Then, checking on the PC shows that the PC has
three IP addresses, 129.9.0.200, 192.169.0.200, and 10.1.68.200. This may be the cause why the
anomaly occurs.

Platform
Procedure
Step 1 Refresh the network connection of computer
1. On the PC, right-click Network Neighborhood and choose Properties.
2. Double-click Local Area Connection for the connection.
3. Choose Support and click Repair. When the repair is complete, record the IP address.
Step 2 Configure only one IP address.
1. Choose Control Panel in Start menu, and then double-click Network Connection.
2. Right-click which the network connection to be set in Network Connection field, and then
choose Properties from the short cut menu.
3. In the Components checked are used by this connection field, click Internet Protocol
(TCP/IP), and then click Properties.
4. In the Internet Protocol (TCP/IP) field, click General tab. Click Advenced.
5. In the Advanced TCP/IP Setting field, click IP Setting tab, delete all the IP address except
the one recorded.
Step 3 After the configuration, the PC can reach the NE. The problem is solved.
----End
None.
5.76 MC-A84 Maximal packet length setting of the OptiX

OSN 6800 Causes the Abnormal Service
ordinary ADSL service is fine but the enterprise ADSL service has anomalies.
Product
OptiX OSN 6800
Fault Type
Symptom
ordinary ADSL service is fine but the enterprise ADSL service has anomalies. The enterprise
user fails to access the Internet.
Cause Analysis
Comparison between the ordinary ADSL service and enterprise ADSL service shows that the
enterprise ADSL service has an extra user tag. Normally, the maximal packet length setting of
enterprise ADSL service is not the same as that of the ordinary ADSL service.

Platform
Procedure
Step 1 The maximal packet length of the OptiX OSN 6800 is 1518. The problem is solved when the
maximum packet length is changed to 9600.
----End
The level of the enterprise ADSL service is higher than that of the ordinary ADSL service.
5.77 MC-A85 SWDL_CHGMNG_NOMATCH Alarm Is

Reported
The SCC board in the slave subrack of OptiX OSN 6800 is identical with the NE software
version. After power-on, the SWDL_CHGMNG_NOMATCH alarm is reported
Product
OptiX OSN 6800
Fault Type
SWDL_CHGMNG_NOMATCH
Symptom
A OptiX OSN 6800 NE contains two subracks in a network. The master subrack houses two
SCC boards. One is active and the other is standby. The software package on the active SCC
board is correct and complete. The SCC board of the slave subrack is replaced with a new SCC
board, whose software package version is the same as the current NE software version. After
power-on, the SCC reports an SWDL_CHGMNG_NOMATCH alarm. In this process, no SCC
board of the master subrack is inserted or removed.
Cause Analysis
Regarding the function of software package auto-match, the SCC board has a software package
version description file different from that of other board.
Regarding the software package auto-match function of the NG WDM products, the SCC board
of the slave subrack is considered as an ordinary board. Therefore, the SCC unit of the slave
subrack should have a board version description file in addition to the software package version
description file. The new SCC board, however, provides only the software package version
description file. The corresponding board software description file is generated only after the
board is considered as an SCC board of the slave subrack, or has undergone a package loading
process or a package auto-match process.
After the NE is powered on, the new SCC board replaced in the slave subrack lacks a board
version description file. As a result, the slave subrack is considered as inconsistent with the
version of the NE software and thus the SWDL_CHGMNG_NOMATCH (replace SCC) alarm
is reported.

Platform
Procedure
Step 1 Check whether the version of the software package for the SCC board is correct and make sure
that the board version description file has been provided.
Step 2 Load the correct software package successfully. The problem is solved.
----End
None.
5.78 MC-A86 Inserting, Removing, and Resetting

Operations Affect NG WDM Products
How do inserting, removing, and resetting operations affect the NE software version and
configuration of NG WDM products.
Product
OptiX OSN 6800
Fault Type
MSSW_DIFFERENT
SWDL_CHGMNG_NOMATCH
CFGDATA_OUTRANGE
Symptom
The OptiX OSN 6800 V100R004C01 version or before and the OptiX OSN 3800 V100R004C01
version or before use the software upgrade with the Toolkit.
The OptiX OSN 6800 and OptiX OSN 3800 automatically matches the master and slave subracks
and software packages on them, and reacts differently to the operations on the SCC of the original
WDM products such as insertion, removal, and reset.
Loading software package: All files that need to be stored on the NE are bundled into a package
(including NE software, board software, INI file, FPGA file, and extended BIOS). This package
is sent to the active SCC and copied to the standby SCC and other boards. Finally, the NE
software, board software, and FPGA file start running to upgrade the NE.
Automatic software package matching: When the new inserted standby SCC board working
normally, the active SCC checks the matching state according to the information sent from the
standby SCC. If the software package is mismatched, the active SCC copies a new software
package to the standby SCC, and activate the new software package on the standby SCC. This
can ensure the consistency of the software on the active SCC and standby SCC.
For details on the symptom, see Table 5-2.

Platform
Cause Analysis
Relevant alarms:
When the software package version is inconsistent between the active and standby SCCs, the
SCC reports the alarm indicating software mismatch (MSSW_DIFFERENT).
If the new software mismatches the software of any board after the single SCC is replaced, the
"replace SCC" alarm is reported (SWDL_CHGMNG_NOMATCH). This alarm can be cleared
by loading the package through the Toolkit.
If the configuration data between the new SCC and the original SCC is different, the
CFGDATA_OUTRANGE alarm is reported.
Procedure
Step 1 For details on how to handle the effect caused by inserting, removing, and resetting operations
on the SCC, see Table 5-2.
----End
Table 5-2 Affection of plugging & unplugging and resetting operations of the SCC
SCC Maintenance Phenomenon Possible Alarm Recommended
Type Operation Handling
Single Remove and Configuration CFGDATA_OU Use the Toolkit to

SCC in insert the original data on the SCCs TRANGE deliver the
master SCC is not consistent. backup
subrack configuration
data of the SCC.
A board of the - The board gets

same version is into service
inserted when the normally.
SCC is out of
position
(including the
SCC in the slave
subrack)
A board of a SWDL_CHGMN Use the ToolKit

different version G_NOMATCH to load the
is inserted when package
the SCC is out of correctly.
position
(including the
SCC in the slave
subrack)

Platform

Replace SCC Replace the SCC If the -

with one of the configuration
same software data between the
version. new SCC and
original SCC is
different, the
"CFGDATA_OU
TRANGE" alarm
is reported. If the
configuration
data is the same,
the alarm is not
reported.
Replace the SCC SWDL_CHGMN Use the ToolKit

with one of a G_NOMATCH to load the
different software package
version. correctly.
Dual SCC Remove and The active SCC MSSW_DIFFER Wait until the NE
master in insert the active and standby SCC ENT software matches
subrack SCC. are switched. The the software
state of the NE package
software is automatically.
inconsistent with
the state of the
standby SCC.
When the SCC is
of the same
software version,
there is no effect.
When the SCC is
of a different
software version,
automatic
package loading
is performed to
match the current
NE software
version, and an
alarm is reported
during the
matching period.

Platform

Remove and When the SCC is MSSW_DIFFER Wait until the NE

insert the standby of the same ENT software matches
SCC. software version, the software
there is no effect. package
When the SCC is automatically.
of a different
software version,
automatic
package loading
is performed to
match the current
NE software
version, and an
alarm is reported
during the
matching period.
SCC in Remove and The slave subrack - -

slave insert the original is not reachable to
subrack SCC. the T2000.
Replace the SCC. When the new - -

SCC is of the
same software
version as the
original SCC,
there is no effect.
When the new - -

SCC is of a
different software
version from the
original SCC,
automatic
package loading
is performed to
match the current
NE software
version.
5.79 MC-A87 SWDL_CHGMNG_NOMATCH Alarm Is

Reported
Though the SCC of the OptiX OSN 3800 and OptiX OSN 6800 is not replaced, an alarm
(SWDL_CHGMNG_NOMATCH) is reported, indicating replacement of the SCC.

Platform
Product
OptiX OSN 6800
OptiX OSN 3800
Fault Type
SWDL_CHGMNG_NOMATCH
Auto Match
Symptom
An OptiX OSN 6800 NE contains two subracks. The master subrack houses an active SCC and
a standby SCC. The software package on the active SCC is correct and complete. A new OTU
board is inserted, whose software version is different from the software version of the SCC. The
NE software cannot match the software package automatically.
The SWDL_CHGMNG_NOMATCH alarm is reported. In this process, no SCC in the master
subrack is removed, inserted, switched, or replaced.
Cause Analysis
The SWDL_CHGMNG_NOMATCH alarm means SCC board changed alarm. The system re-
checks whether the board software of each board matches the NE software after the NE starts
up upon a power failure, the SCC unit is replaced, or a cold reset is performed on the SCC unit.
The alarm occurs when the board software of a board mismatches the NE software. It indicates
that the board software mismatches the NE software.
The software package is automatically matched in two stages:
In the startup process, the SCC only detects the board version, but does not start auto-match of
the software package. After the SCC starts up, the SCC checks whether the board supports
package loading. If yes, the SCC checks whether the software version of the board is consistent
with the NE software version. This interaction process starts from the startup of the NE software
and continues until the SCC changes from the pending stability state to the normal state.
The auto-match of the software package starts only after the NE state changes to normal. At this
time, if no alarm related to package loading is reported (that is, the alarm that begins with
SWDL_), the SCC matches the board software automatically. In the case of the board whose
software version is different from that of the NE software, the SCC delivers the board software
stored on the SCC, and activates the software.
If any alarm related to package loading is raised on the NE software, however, the SCC does
not perform auto-match of software, but reports SWDL_CHGMNG_NOMATCH alarm.
NOTE
The board here means any board except the active SCC of the master subrack, including the standby SCC
of the master subrack and the SCC of the slave subrack.
Procedure
Step 1 Use the correct software package to perform package loading successfully. If the SCC has a
version identical with the software version of most boards (except one or two boards) in the

Platform
software package, the loading process is quick, and the board with loaded software package is
reset.
----End
None.
5.80 MC-A88 Difference in BER Reported by the OTU Board

and Test Instrument
Difference test instrument cause difference in BER reported by the OTU board and test
instrument.
Product
OptiX Metro 6100
Fault Type
Bit error
B1_EXC
Symptom
When the test instrument inserts bit error at a certain rate, the OTU board reports an alarm
indicating that the higher order bit errors crosses the threshold (B1_EXC alarm). The bit errors
inserted by the test instrument deviate from the bit errors reported by the OTU by 10E2 to the
maximum.
The bit errors inserted by the test instrument deviate from the bit errors reported by the OTU.
Cause Analysis
This problem occurs because the test instrument and OTU adopt different standards. The former
adopts the B1 error block rate, which is the ratio of error blocks to all errors in a certain time
period with bit errors. In this case, the error block rate is 8000*8/10E10=6.4*10E-6 (for example:
STM-64). The latter adopts the BER, which is the ratio of bit errors to all bit errors in a certain
time period, The BER read on the test instrument is the higher order BER of the OTU.
For example, the rate of the STM-16 service is 2.5 Gbit/s and the SDH equipment sends bits at
a rate of 8000 frame/sec. In the case of 1.0E-3, the BER is computed as follows:
l Theoretical value: All data packets have bit errors. BER = Rate x Time x 8 bit = 8000 frame/
sec x 0.01 sec x 8 bit = 640
l Value test by equipment: The BER is verified in real time. When a bit has even bit errors,
the verification value is correct. For example,
– Two transmitted bytes: (a: 10101010; b: 10101011)
– These two byte at receive end are: (a: 10101001; b: 10101000)

Platform
At the receive end, the verification value is correct. Therefore, the value read on the test
instrument should be less than the theoretical value and should be 300.
l Set the value of the OTU to raise the alarm: According to the value read on the test
instrument and the value computed on the OTU board, set the alarm threshold to 300.
l Set the value of the OTU to clear the alarm: According to the value read on the test
instrument and the value computed on the OTU board, set the alarm threshold to 260.
Table 5-3 lists the bit error thresholds for the STM-16 service.
Table 5-3 Bit error thresholds for the STM-16 service
B1 Test Theoreti Value Value Value of Value of

Time cal Value Tested Tested OTU Set OTU Set
by by 37718 to Raise to Clear
ANT20 the the
Alarm Alarm
1.0E -3 10ms 640 300 N/A 300 260
1.0E -4 100ms 6,400 N/A 2,500 1,800
1.0E -5 1s 24,883 17,300 24,883 17,250 2,500
1.0E -6 10s 24,883 24,000 24,883 23,950 2,500
1.0E -7 100s 24,883 24,800 24,883 24,750 2,500
1.0E -8 1000s 24,883 24,883 24,883 24,800 2,500
1.0E -9 10000s 24,883 24,883 24,883 24,800 2,500
Procedure
Step 1 None.
----End
None.
5.81 MC-A89 Two Different Power Supplies for the OptiX

Metro 6100
Two different power supplies can be provided by the OptiX Metro 6100.
Product
OptiX Metro 6100

Platform
Fault Type
PWR_MAJ_ALM
Symptom
A customer wants to install OptiX Metro 6100 subrack into the cabinet. The following two power
supplies are available in the equipment room:
l input power 1: -48 V DC
l input power 2: -60 V DC
No power supply alarm should be reported.
Cause Analysis
The equipment reports the PWR_MAJ_ALM alarm when the input voltage is excessively high
or excessively low.
The subrack can access both the -60 V and -48 V power supplies. On the T2000, you can select
one of them according to the input voltage level.
Procedure
Step 1 The customer can select the input voltage level according to the actual voltage level.
Step 2 The customer can suppress the PWR_MAJ_ALM alarm.
----End
None.
5.82 MC-A90 The Incorrect Configuration of DWC Leads To

Abnormal Optical Power and Service Interruption
The incorrect configuration of DWC leads to abnormal optical power and service interruption.
Product
OptiX Metro 6100
Fault Type
IN_PWR_HIGH
OTU_LOF
Symptom
The Metro6100V1R6 (ROADM) adopts the DWC board. A 10G link (FJQ:3-1-8 <-> NAD:
2-3-5) composed of LBE works normally (21st wavelength), but reports the IN_PWR_HIGH

Platform
and OTU_LOF alarms abruptly at the WDM side of the LBE of FJQ. The FEC error correction
performance is "1", and the service is abnormal.
Cause Analysis
The receiving optical power increases abruptly. With past experience in handling faults similar
to the DWC problem, we cut off the laser to discern the correctness of the link. After cutting off
the laser of the NAD:2-3-5 LBE, we find that the receiving optical power at the WDM side of
the FJQ 3-1-8 LBE does not change, which is abnormal (normally, the R_LOS alarm should
occur). By checking the configuration, we find that the blocking state of the 21st wavelength of
the 1-1 DWC at the NAD site is set incorrectly (It should be set as Block/Add wavelength, but
is actually set as Pass through). Consequently, the pass-through signals and the local V40
wavelength adding signals are multiplexed concurrently. Thus the peer optical power is
abnormal and the service is interrupted.
Procedure
Step 1 By analyzing the NAD (3-2-5)-->FJQ (3-1-8), we find that the receiving optical power at the
WDM side of the LBE of FJQ is +3 dB, which is abnormal. After the laser of the NAD is cut
off, the receiving optical power of FJQ is still +3 dB, which is abnormal.
Step 2 By checking the DWC configuration of the FJQ, RAK-C, RAQ and NAD sites sequentially, we
find that the blocking state of the 21st wavelength of the 1-1 DWC at the NAD site is set
incorrectly (it should be set as Block/Add wavelength, but is actually set as Pass through).
Consequently, the pass-through signals and the local V40 wavelength adding signals are
multiplexed concurrently. Thus the peer optical power is abnormal and the service is interrupted.
Step 3 After we change the DWC configuration, the optical power of FJQ returns to normal, the alarm
disappears, and the FEC error correction performance value is 0.
----End
None.
5.83 MC-A91 Creation of Intra-Board Wavelength

Protection on the LDG Fails
The creation of intra-board wavelength protection on the LDG fails due to the configured
attributes of the board.
Product
OptiX Metro 6100
Fault Type
Protection
Symptom
Housed in the OptiX Metro 6100 subrack, the LDG has 2 WDM interfaces (IN1/OUT1 and IN2/
OUT2). An attempt is made to create the intra-board wavelength protection on the LDG by using

Platform
the T2000-LCT (version V200R003C01B01h). In Configuration/Wawelength Protection

Group, IN1/OUT1 of the LDG cannot be selected as the working channel and IN2/OUT2 of
the LDG as the protection channel.
Cause Analysis
The creation of intra-board wavelength protection on the LDG fails due to the incorrect Board
Receiving/Transmitting Attributes attributes of the board.
Even though the board dually feeds and selectively receives signals, this information is not
automatically displayed.
Procedure
Step 1 Select the LDG board and choose Board in Configuration/WDM Interface for query the LDG.
Step 2 Board Receiving/Transmitting Attributes displays the information according to the board
type. Then, intra-board wavelength protection can be normally configured on the LDG.
Step 3 The problem is resolved.
----End
None.
5.84 MC-A92 How to Handle the J0_MM Alarm on the LWM

How to handle the J0_MM alarm on the LWM.
Product
OptiX Metro 6100
Fault Type
JO_MM
Symptom
The ANT20 analyzer is used to test an STM-16 link with two LWM boards. One LWM connects
to the analyzer and the other is looped back. The traffic is normal but the LWM reports the
J0_MM alarm. Check on the J0 transmitted by analyzer shows that the J0 byte was set to 11.
Check on LWM -> Configuration/WDM Overhead Management/SDH Overhead shows
that J0 to be transmitted and J0 to be received (displayed in hex) are both 11.
Cause Analysis
Verify the SDH overhead in text mode not just in hexadecimal format.

Platform
Procedure
Step 1 Check on the J0 trace identifier on analyzer shows that the test is in process.
Step 2 Checked on the SDH overhead of the LWM (displayed in text) shows that the J0 received is
indeed "text", but the J0 to be received is blank.
Step 3 The J0 to be received (displayed in text) is changed to be tested and the alarm is cleared.
----End
None.
5.85 MC-A93: The Input Optical Power of the OTU Board Is

Abnormal Due to a Fault of the OPU Board
The input optical power of the OTU board is abnormal due to a fault of the OPU board.
Product
OptiX Metro 6100
Fault Category
Amplifier unit
Symptom
In a single-channel ring network, the input optical power of an OTU board drops from 0 dBm
to -7 dBm, -15 dBm, or -62 dBm.
This ring network bears the SDH service and is configured with the multiplex section protection
(MSP).
Cause Analysis
The launched optical power of the opposite OTU is abnormal, or the line amplifier unit is faulty.
Procedure
Step 1 By checking whether there are abnormal alarms against the input optical power of the opposite
OTU board, you can find that the parameters of the opposite OTU board are proved normal.
This indicates that the launched optical power of the opposite OTU is normal.
Step 2 The input and output optical power of the opposite amplifier board are also checked normal.
Step 3 The input and output optical power of the local amplifier board, however, are checked abnormal.
The input optical power of the local amplifier board is constant, whereas the output optical power
of the local amplifier board is abnormal. This indicates that the local amplifier board is faulty.

Platform
Step 4 After you replace the local amplifier board, the system is restored.
----End
l When you find that the output optical power of the local OTU is abnormal, check the
following items:
– Input and output optical power of the opposite OTU board
– Input and output optical power of the opposite amplifier board
– Input and output optical power of the local amplifier board
l If the anomaly of optical power occurs at random, perform the following steps:
– Check whether any fiber jumper is loose or bent.
– Clean the fibers and connectors.
– Perform an optical time domain reflectometer (OTDR) test under the customer's
consent.
5.86 MC-A94: The WXCP Protection Configured for the

LOG Board Is Invalid
of the board.
Product
OptiX Metro 6100
Fault Category
Protection
Symptom
The LOG board is configured with the correct WXCP protection.
During a protection switching test, services are interrupted because there is no protection channel
to which the services can be switched; however, no alarms are reported to the T2000.
Check whether the protection configuration is correct.
If you delete the protection group and then configure a new one, the fault persists.
Cause Analysis
of the board.
Procedure
Step 1 Check the LOG board of the protection group.

Platform
1. In the NE Explorer, select the LOG board to be checked.

2. Select Configuration > WDM Interface from the Function Tree.
3. Click the Advanced Attributes tab.
4. Check whether the Max Packet Length is 9800.
Step 2 In this case, set the value of this parameter to 1511.
Step 3 Because the value of the parameter cannot be changed, set the LOG board.
Step 4 After the LOG board is reset, the value of the parameter is displayed as 9800.
Step 5 Test whether the fault is cleared. If the fault is cleared, the WXCP protection becomes valid.
----End
None.
5.87 MC-A95: The SC2 Board Reports the CRC4_CROSSTR

Alarm
The SC2 board reports the CRC4_CROSSTR alarm due to the board faulty.
Product
OptiX Metro 6100
Fault Category
OSC
CRC4_CROSSTR
Symptom
The SC2 board in the OptiX Metro 6100 reports the CRC4_CROSSTR alarm.
Cause Analysis
The main causes may be the abnormal received optical power and the fault in the fiber or optical
connectors.
Procedure
Step 1 The received optical power of the SC2 board is normal (The receiver sensitivity of the SC2 board
is -48V.), whereas the SC2 board reports the alarm.
Step 2 The fault persists even when the fibers and connectors at the RM1 interface of the SC2 board
are cleaned.

Platform
Step 3 Replace the SC2 board, and the fault is cleared. This indicates that the RM1 interface of the SC2
board is faulty.
----End
None.
5.88 MC-A96: Packet Loss Occurs in Ethernet Service

Testing of the L4G Board
The packet loss occurs in Ethernet service testing of the L4G board due to the different equipment
and meters.
Product
OptiX Metro 6100
Fault Type
Ethernet service
Symptom
In a test of EPL and VLAN networking by using the L4G board, the Smartbits meter is used to
transmit complete bandwidth signals that are looped back on the client side at the remote end.
During the test, a packet loss ratio of 0.001% is found. If the EPL networking is set up without
the VLAN networking, no packets are lost on site.
Cause Analysis
In the EPL networking, exact synchronization of Ethernet networking can hardly be realized
and a frequency deviation tolerance of +/-100 ppm is permitted. Hence, different equipment and
meters trace different clock sources. If the inner oscillation frequency of the transmit unit is
quicker than that of the receive unit, packet loss occurs.
Procedure
Step 1 None.
----End
None.

Platform
5.89 MC-A97: The Optical Amplifier Reports the

IN_PWR_HIGH Alarm Because of Optical Power
Reflection
The optical amplifier reports the IN_PWR_HIGH alarm because of optical power reflection.
Product
OptiX Metro 6100
Fault Type
IN_PWR_HIGH
Symptom
A metropolitan area ring network composed of the OptiX Metro 6040 bears single wavelengths.
After the local commissioning of all sites, if you shut down all the optical amplifiers such as the
OPU and OBU, the IN_PWR_HIGH alarm is reported. In this case, if you power on some of
the amplifiers, the optical power of the network is restored.
Cause Analysis
This problem is caused by optical refection of the amplifiers.
The sites of the network are OADM sites. That is, services pass through between the MI and
MO optical interfaces on the MR2 boards of all the sites. If the pass-through wavelengths of the
network are not blocked, optical power reflection of the amplifiers occur.
Procedure
Step 1 To solve this problem, the pass-through wavelengths between the MI and MO optical interfaces
on the MR2 boards of the network must be blocked. If a wavelength bearing no services passes
through the MR2 boards of all the sites, this wavelength must also be blocked. You can also add
a electrically variable optical attenuator to the link between the MI and MO optical interfaces
of each site, and set the attenuation of each electrically variable optical attenuator to the
maximum value until more pass-through wavelengths are loaded.
Step 2 This method is used to avoid repeated amplification of noise.
----End
None.
5.90 MC-A98: The Protection Switching Times Out Severely

The protection switching time is out severely in the event of wavelength protection between the
SCS boards of the OptiX Metro 6100 because of the wrong test method.

Platform
Product
OptiX Metro 6100
Fault Type
Protection
Symptom
In the test of inter-board wavelength protection of the SCS board, the test result is severely
beyond the standard. The minimum switching time is over 1000 ms and the maximum switching
time even reaches up to 3000 ms. The standard switching time should be less than 50 ms. As a
result, the test result is far from the required switching time.
The test meter used on site is the ANT-20SE.
The test procedure is as follows: 1. Perform a hard loopback between the IN and OUT optical
interfaces of the LQS board by using a fiber, and connect the TI1 and RO1 optical interfaces of
the SCS board to the test instrument. 2. Configure inter-board wavelength protection by using
the T2000. 3. After completing the configuration, test the inter-board wavelength protection by
using the tester. No alarm is found and the optical path is normal. 4. Disconnect the fibers on
the client-side optical receiving interfaces of the active and standby LQS boards. The protection
switching can be completed but times out severely.
Cause Analysis
The trigger condition of the wavelength protection switching is an anomaly of service receiving
on the WDM side. Hence, the correct test moth is to remove the fiber on the WDM side of the
LQS board. During the test, however, the client-side receive fiber of the LQS board is removed.
Hence, the switching process is as follows:
l Remove the client-side receiving fiber of the LQS board.
l The LQS board shuts down the WDM-side laser according to the ALS function in about 2
seconds.
l The system detects that there is no optical input on the WDM-side optical interface of the
LQS board. Hence, the board reports the SF event.
l The protection group switches over to the protection path.
Hence, the actual test time includes the switching time and the time taken for the ALS to close
the laser. As a result, the switching times out severely.
Procedure
Step 1 The test method is changed to perform by disconnecting the WDM-side fiber, the switching time
is normal.
Step 2 The test is past after the test method is changed to perform by disconnecting the WDM-side
fiber.
----End
None.

Platform
5.91 MC-A99: The PMU Reports the THUNDERALM Alarm

The PMU reports the THUNDERALM alarm.
Product
OptiX Metro 6100
Fault Type
Others
Symptom
The PMU of the OptiX Metro 6100 equipment reports the THUNDERALM alarm.
Cause Analysis
The fuse for a protection indicator on the DPFU is blown out. According to the definition of the
parameters of the alarm, the format of the alarm is as the following:
l PARA1 PARA2 PARA3 PARA4 PARA5
l 0x** 0xff 0xff 0xff 0xff
The definition of the PARA1 is as the following:

l 0x11: indicates that the level-1 lightning protection indicator for the DPFU in channel 1 is
unlit.
unlit.
unlit.
unlit.
In the normal configuration, current is input from channel A of the DPFU in channel 1 and
channel B of the DPFU in channel 2.
The level-1 lightning protection indicator is unlit is equivalent to that fuse 14 is blown out.
Likewise, the level-2 lightning protection indicator is unlit is equivalent to that fuse 5 is blown
out.
Each lightning protection alarm level corresponds to a specific fuse class for alarm analysis and
troubleshooting.
Procedure
Step 1 Test the lightning protection fuses for the DPFU.

Platform
Step 2 When you install the fuses, unscrew the four screws on the DPFU. The lightning protection fuses
F14 and F5 are the two fuses correspond to the alarm indication. In the case of blow-out of a
fuse, a backup fuse is available on the DPFU.
----End
None.
5.92 MC-A100: The FDG Board Reports the R_DATA_LOST

Alarm in the Early Morning
The FDG board reports the R_DATA_LOST alarm in the early morning because the traffic
volume is light.
Product
OptiX Metro 6100
Fault Type
R_DATA_LOST
Symptom
The FDG board in the Metro 6100 keeps reporting the R_DATA_LOST alarm in the early
morning. The line and the data equipment connecting to the FDG board, however, are normal.
Cause Analysis
The FDG board detects the services every five seconds. If the FDG does not receive data packets
during the detection, the FDG reports the R_DATA_LOST alarm. The alarm does not mean that
the services are not available. No alarm is generated in the line during day and the services are
normal. The alarm is generated only in the early morning. Hence, the alarm is related to the truth
that the traffic volume is light. In the early morning, no data packets are transmitted normally
when the FDG detects the services. Hence, the R_DATA_LOST alarm is reported.
Procedure
Step 1 Suppress the alarm on the NM after making sure that the services are normal.
----End
The data boards, such as the LDG, also have the similar problem. Solve the problem in a similar
way.

Platform
5.93 MC-A101: The Wavelength Is Unstable or Changed Due

to Optical Power Variation
The wavelength is unstable or changed due to optical power variation.
Product
OptiX Metro 6100
Fault Type
Optical power abnormal
Problem Description
As time goes by, the optical power of a board changes because of temperature variation or system
aging. The original wavelength may be unstable or changed.
Cause Analysis
Temperature has slight impact on the optical power. Hence, the optical power of a new board is
almost the same as that of the old board. The only slight difference is that the optical power at
a port on the WDM side is 0.5 dB (in the case of a low temperature) or 1 dB (in the case of the
normal temperature) lower than that on the client side of the board.
If the board adopts the SFP module, the optical power at a port on the client side drops by 3 dB
under the normal temperature.
Procedure
Step 1 The optical power at a port on the WDM side is 0.5 dB (in the case of a low temperature) or 1
dB (in the case of the normal temperature) lower than that on the client side of the board.
Step 2 If the board adopts the SFP module, the optical power at a port on the client side drops by 3 dB
under the normal temperature.
----End
None.
5.94 MC-A102: The LBE, LDG and LQG Boards Report the
LINK_ERR or LINK_STATUS Alarm
The LBE, LDG and LQG boards report the LINK_ERR or LINK_STATUS alarm.
Product
OptiX Metro 6100

Platform
Fault Type
Symptom
The LBE, LDG or LQG board reports the LINK_ERR or LINK_STATUS alarm.
Cause Analysis
The causes for the alarms must be ascertained before the correct solutions can be found.
Procedure
Step 1 The trigger conditions for the LBE or LBES board to generate the LINK_ERR alarm are as
follows:
1. The receive sequence (at the physical coding sublayer (PCS)) at the peer or local end is
incorrect.
2. The bit error ratio is extremely high.
3. The synchronization frame is lost.
4. Bit synchronization is lost.
5. Signals are lost.
Step 2 The trigger conditions for the LOG board to generate the LINK_ERR alarm are as follows:
2. When auto-negotiation is enabled, the LINK_ERR alarm is reported if the auto-negotiation
fails.
3. When LPT is enabled, the board reports the LINK_ERR alarm if the service network is
faulty or the peer board reports LINK_ERR.
Step 3 The trigger conditions for the LDG board to generate the LINK_STATUS alarm are as follows:
2. When auto-negotiation is enabled, the LINK_STATUS alarm is reported if the auto-
negotiation fails.
3. When LPT is enabled, the board reports the LINK_STATUS alarm if the service network
is faulty or the peer board reports LINK_STATUS. When the optical interface on the client
side is inlooped, neither LINK_ERR nor LINK_STATUS is reported.
Step 4 When no light is received on the client side, LINK_ERR or LINK_STATUS is suppressed
because the R_LOS alarm is reported. If the client-side link is normal but no packet is sent or
received, only ALM_DATA_RLOS or ALM_DATA_TLOS is reported.
----End
None.

Platform
5.95 MC-A103: How to Configure the Dual Feed and

Selective Receiving Boards
How to configure the dual feed and selective receiving boards in the case of a unidirectional
WDM link.
Product
OptiX Metro 6100
Fault Type
Optical Transponder Unit
Symptom
The LDG board that supports the dual fed and selective receiving is used as the service board.
This case also applies to the OTU board hat supports the dual fed and selective receiving.
When the link is not configured with protection and the fiber signal flow is not created on the
T2000, the T2000 display that the WDM-side optical interfaces adopt two separated routes.
Cause Analysis
In the case of the board that supports the dual fed and selective receiving, if the physical fibers
are not connected and the logic fibers are not created on the T2000, the system cannot identify
whether the link is configured with protection.
To make the system report the correct WDM-side optical interface information (that is, the link
does not adopt the intra-board 1+1 protection) of the LDG board, the use status of the unused
WDM-side optical interfaces must be set to Unused.
Procedure
Step 1 In the NE Explorer, select the desired board, and choose the Configuration > WDM
Interface.
Step 2 In Basic Attributes, select the Path Used Status field, and set the use status of the WDM-side
optical interfaces to Unused.
----End
None.

Platform
5.96 MC-A104: No Optical Power Is Output on the WDM

Side Due to Incorrect Configuration
No optical power is output on the WDM side of the LWM board due to incorrect configuration
of the SFP module on the client side.
Product
OptiX Metro 6100
Fault Type
R_LOF
R_LOC
TP_LOC
Others
Symptom
In a network, the LWM board accesses the STM-16 service on the client side but does not output
optical power on the WDM side. In addition, the client side of the LWM board reports the R_LOF
or R_LOC alarm, and thus the WDM side of the board reports the TP_LOC alarm.
Cause Analysis
The SFP module on the client side of the board is of SCP6801-H1-BNE and supports rates that
are only lower than 155.52 Mbit/s. This SFP module does not comply with the specifications of
the LWM board. Hence, this problem results from the incorrect configuration of the SFP module
type.
Procedure
Step 1 Replace the SFP module of the correct type on the client side to clear the fault.
----End
None.
5.97 MC-A105: Line Reflection Leads to Inaccurate BER

Detection of the SSC6LWX Board
The line reflection leads to the inaccurate BER detection of the SSC6LWX board.

Platform
Product
OptiX Metro 6100
Fault Type
Symptom
As shown in Figure 5-1, when an intensive reflection exists on the line, the SDH instrument
reports bit errors. When the performance event reporting of the LWX board along the signal
flow is queried, however, the first bit error reporting point is found on the RX port of the
downstream board 2 instead of on the IN port of board 1. Alternatively, the IN port of board 1
has only a few bit errors, whereas plenty of bit errors appear on the RX port of board 2. Such a
phenomenon in which the first bit error reporting point is on the second receiving side in the
downstream instead of on the first receiving side is called "beating an ox on the other side of a
mountain". The phenomenon, caused by line reflection, directly impacts the fault analysis and
troubleshooting and misleads the fault locating on site. By now, the problem has occurred in
two sites.
The LWX board reports the B1_EXC alarm.
Figure 5-1 Networking diagram
Cause Analysis
As shown in Figure 5-2, the LWX is a wavelength conversion board of any rate ranging from
32 Mbit/s to 2.5 Gbit/s. The board implements performance monitoring through bypass
detection. That is, it divides the received signals into two parts. One part is sent to the
performance monitoring module for bit error statistics, and the other part is sent to the
downstream chip for output after being processed by the board. Because the performance
monitoring path is independent of the signal output path, it is possible that the receiving side of
the board is normal but bit errors occur after board processing. Because the LWX is an access
board of any rate ranging from 32 Mbit/s to 2.5 Gbit/s, no phase-locked loop circuit exists inside
the board. Nevertheless, the performance monitoring module is implemented by the FPGA.
Depending on the service type monitored, the board is loaded with a specific logic file. A phase-
locked loop (that is, access at a fixed rate) exists inside every implemented circuit. Hence, the
two parts of signals differ in performance. Generally, this difference is ignorable. If no bit error
occurs in performance monitoring, the signals received by the board on this point can be regarded

Platform
normal; however, when the multipath interference (MPI) effect is triggered by an intensive
reflection point on the line, the BER detection of the board may be inaccurate (inaccurate BER
reporting of the board is the only reflection-caused problem found during the three years of
application of the LWX board).
Figure 5-2 Working pinciple of the SSC6LWX board
To locate the preceding LWX bit error problem, the normal location method is preferred to check
the optical power, OSNR, and dispersion of the system, which are found normal. Then, the
software and hardware of the board are checked to ensure that the board is normal (these are the
items that should be inspected first, and are the most easily discernible causes for the problem).
After the foregoing factors are precluded, if the LWX still reports bit errors, the upstream line
might be faulty. An OTDR is used to measure the line and check whether any intensive reflection
event occurs, that is, whether intensive reflection point exists on the line (according to the China
national standard, the reflection must be less than -27 dB). After the reflection point is found,
the problem can be cleared by cleaning the fiber, replacing the connector, or splicing the fiber
connector.
Because the interference light and signal light caused by reflection are in the same direction and
at the same frequency, and impose little impact on the power of the main signal light, the problem
is unable to be discerned by measuring the optical power of signals or the OSNR with the optical
power meter or spectrum analyzer.
Procedure
Step 1 Use the OTDR instrument to measure the line and observe whether intensive reflection events
occur on the instrument, and detect the reflection problem on the line.
Step 2 A research shows that the MIP effect greatly impacts the probability distribution of the "1" codes
in the system. Based on the special optical power distribution generated by secondary reflection
interference on the "1" codes of the signal light, the statistic function of the eye pattern tester
can be used to test the optical power distribution diagram (histogram) of the "1" codes in the eye
pattern. In this way, the existence of the secondary reflection interference can be discerned
effectively.
----End

Platform
Figure 5-3 shows the main signal eye patterns. Figure (a) shows the eye pattern when the
secondary reflection interference does not exist; figure (b) shows the eye pattern when the
secondary reflection interference exists.
Figure 5-3 Main signal eye patterns when the secondary reflection interference does not exist
and exists
5.98 MC-A106: OptiX Metro 6100 Reports the

PWR_MAJ_ALM Alarm
When supplied with both -48 V and -60 V power, the OptiX Metro 6100 reports the
PWR_MAJ_ALM alarm.
Product
OptiX Metro 6100
Fault Type
PWR_MAJ_ALM
Symptom
When supplied with -48 V and -60 V respectively, two DPFUs of the OptiX Metro 6100 report
the PWR_MAJ_ALM alarm.
Cause Analysis
The two DPFUs of the OptiX Metro 6100 can be respectively supplied with two power supplies
of different voltages between -38.4 V DC and -72 V DC. Hence, the two DPFUs can be supplied
with -48 V and -60 V respectively. When both these two power supplies are normal, all current
flows through the -60 V DPFU (namely, the -48 V DPFU does not function). The -48 V DPFU
takes over the function to supply power only when the -60 V DPFU is faulty. This switching
process is seamless and takes no time.

Platform
When the two DPFUs are respectively supplied with two power supplies of different voltages,
the monitoring voltage level can be set to -48 V or -60 V though the operating voltage is -60 V.
The alarm thresholds of monitoring voltage vary with the monitoring voltage level. If the
monitoring voltage level is set to -60 V, the lower threshold of the voltage alarm is -51 V and
the upper threshold is -71 V by default. That is, when both the two input voltages are between
-51 V and -71 V, no voltage alarm occurs. If the voltage level is set to -48 V, the lower threshold
of the voltage alarm is -41 V and the upper threshold is -60 V by default. That is, when both the
two input voltages are between -41 V and -60 V, no voltage alarm occurs. When either of the
two input voltages crosses the threshold, the PWR_MAJ_ALM alarm is reported.
Procedure
Step 1 The result being detected shows that the voltage level set on site is -48 V and the thresholds of
the voltage alarm are the default values; therefore, the two DPFUs allow an input voltage range
between -41 V and -60 V. The input voltages might deviate to some extent; therefore, when the
voltage of the -60 V DPFU deviates up to a value that crosses the upper threshold, the overvoltage
alarm is reported.
Step 2 After the upper threshold of voltage alarm is changed to -65 V, the overvoltage alarm clears.
----End
When supplied with two power supplies of different voltages, the OptiX Metro 6100 reports an
overvoltage alarm.
To clear this alarm, you can change the thresholds of the alarm. When setting the thresholds,
consider the stabilities of the input voltages. If the input voltages are of large amplitudes, the
alarm is likely to persist.
When supplied with -48 V and -60 V respectively, two DPFUs of the OptiX Metro 6040 reports
an overvoltage alarm by default. To clear this alarm, use either of the following two methods.
l Suppress the PWR_MAJ_ALM alarm.

l Set the voltage level to -60 V so that the OptiX Metro 6040 does not detect the input voltages
and does not report the overvoltage alarm.
5.99 MC-A107: The Cross-Connection Function of the

Subrack Fails
The cross-connection function between two LOG or ELOGS boards on the left and right sides
of the subrack fails because the hardware bus is restricted.
Product
OptiX Metro 6100
Fault Type
Others

Platform
Symptom
The cross-connection function between two LOG boards on the left and right sides of the subrack
fails. Relevant documentation, however, shows that the LOG board supports the function.
Cause Analysis
The hardware bus is restricted. The backplane of the OptiX Metro 6100 V100R006 subrack
consists of two parts, that is, slots IU1-IU6 and slots IU8-IU13. The two LOG or ELOGS boards
can be configured with the inter-board GE service cross-connection and the WXCP protection
if the two boards are both installed in slots IU1 and IU3 or IU8 and IU10.
The ELOG or ELOGS board supports the inter-board GE service cross-connection across cross-
connect planes.
l The combination of two ELOG or ELOGS boards in the same cross-connect plane (in slots
IU1-IU6 or slots IU8-IU13) supports the cross-connection of a maximum of eight pairs of
GE services.
l The combination of two ELOG or ELOGS boards in two paired slots (IU1 and IU8, IU2
and IU9, IU3 and IU10, IU4 and IU11, IU5 and IU12, or IU6 and IU13) also supports the
cross-connection of a maximum of eight pairs of GE services.
Procedure
Step 1 None.
----End
None.
5.100 MC-A108: How to Select Test Meters on Site When

Testing OTU Boards of the Data Type
How to select test meters on site when testing OTU boards of the data type.
Product
OptiX Metro 6100
Fault Type
Symptom
The OTU boards of the data type used in a project are the SSC6LOG01M01, SSC6LDGD01M12,
SSC8LBE01M01, and SSC6FCETD04. The meters available on site are as follows:
l SmartBits Main Chassis model SMB600B

Platform
l SmartBits Main Chassis model SMB600 (with option SWF1201A, SWF1212A)

l SmartBits Main Chassis model SMB600 (with option SWF1201A)
l SmartMetrics 10 Gbps Ethernet XFP, 1 Port MSA Module model XFP3730A
l 10/100/1000 Mbps and Gigabit Ethernet Fiber, 2-port, SmartMetrics XD Module model
LAN3320A
l 10/100/1000 Mbps and Gigabit Ethernet Fiber, 2-port, TeraMetrics XD Module model
LAN3321A
l 10/100/1000 Mbps and Gigabit Ethernet Fiber, 4-port, SmartMetrics XD Module model
LAN3324A
l SmartMetrics Gigabit Ethernet Module model LAN3201B
l SMART Optical Level Attenuator, 1260 nm to 1650 nm model OLA-55 (2280/01)
On site, which one or two test meters should be selected to test all the OTU boards of the data
type?
Cause Analysis
According to the types of OTU boards used on site, services that need to be configured and
activated in the project include GE, 10GE, and FC100/200. The meter SmartBits Main Chassis
model SMB600B can be used to test these three types of services. The test card varies with the
service type.
All the services in the project can be tested with the meter SmartBits Main Chassis model
SMB600B.
l In the case of the GE service, use the test card LAN3320A.

– 1x SmartBits Main Chassis model SMB600B
– 1x 10/100/1000Mbps and Gigabit Ethernet Fiber, 2-port, SmartMetrics XD Module
model LAN3320A
l In the case of the 10GE service, use the test card XFP-3730A.
– 1x SmartMetrics 10 Gbps Ethernet XFP, 1 Port MSA Module model XFP3730A
l In the case of the FC100/200 service, use the test card FBC3602.
– 1x FBC3602
Procedure
Step 1 None.
----End
None.

Platform
Maintenance Cases A Glossary
A Glossary
A
Alarm A visible or an audible indication to notify the person concerned that a failure or an
emergency has occurred. See also Event.
Auto negotiation When the auto negotiation mode is enabled on the telecommunication equipment, the
equipment sets its working mode and rate through negotiation based on the mode and
rate of the opposite equipment.
B
Bit Error Rate The ratio of the errored bit count to the transmitted bit count in a certain period of time.
In the digital communication system, bit error rate is the ratio of the errored bit count to
the received bit count in a typical period of time.
C
Channel The trail on the channel layer.
Configure To set the basic parameters of an operation object.
Connection A "transport entity" which consists of an associated pair of "unidirectional connections"
capable of simultaneously transferring information in opposite directions between their
respective inputs and outputs.
D
DCM Dispersion Compensation Module. A module, which contains dispersion compensation
fibers to compensate for the positive dispersion of transmitting fiber.
E
Ethernet A data link level protocol comprising the OSI model's bottom two layers. It is a broadcast
networking technology that can use several different physical media, including twisted
pair cable and coaxial cable. Ethernet usually uses CSMA/CD. TCP/IP is commonly
used with Ethernet networks.
Issue 01 (2009-08-10) Huawei Proprietary and Confidential A-1

Platform
A Glossary Maintenance Cases
F
Fault A fault is the inability of a function to perform a required action. This does not include
an inability due to preventive maintenance, lack of external resources, or planned actions.
Fiber jumper The fiber which is used to connect the subrack with the ODF, subrack or connect the
board interfaces.
Flow An aggregation of packets that have the same characteristics. On the T2000 or NE
software, flow is a group of classification rules. On boards, it is a group of packets that
have the same quality of service (QoS) operation. At present, two flows are supported:
port flow and port+VLAN flow. Port flow is based on port ID and port+VLAN flow is
based on port ID and VLAN ID. The two flows cannot coexist in the same port.
Frame A cyclic set of consecutive time slots in which the relative position of each time slot can
be identified.
G
Gain The ratio between the optical power from the input optical interface of the optical
amplifier and the optical power from the output optical interface of the jumper fiber,
which expressed in dB.
GE ADM The technology can optimize GE service transport over WDM for Metro network. It
owns the capability of GE service convergence and grooming and benefits to use the
network resource more effectively.
H
Hardware loopback Hardware selfloop refers to the process where a fiber jumper is used to connect the input
optical interface to the output optical interface of a board to achieve signal loopback.
J
Jitter The short-term non-cumulative variations of the significant instants of a digital signal
from their ideal positions in time.
L
Laser The device that generates the directional light covering a narrow range of wavelengths.
Laser light is more coherent than ordinary light. Semiconductor diode lasers are the used
light source in fiber-optic system.
Layer A concept used to allow the transport network functionality to be described hierarchically
as successive levels; each layer being solely concerned with the generation and transfer
of its characteristic information.
M
MAN Metropolitan Area Network. A network where the computer resources in a geographic
region are connected. The coverage of a MAN is larger than the coverage of a local area
network (LAN) but smaller than the coverage of a wide area network (WAN).
A-2 Huawei Proprietary and Confidential Issue 01 (2009-08-10)

Platform
Maintenance Cases A Glossary
N
NE A network unit, including the hardware and software. Normally a network unit has at
least one SCC board, which manages and monitors the entire network unit. NE software
runs on the SCC board.
O
ODF Optical Distribution Frame. A frame which is used to transfer and spool fibers.
Optical spectrum An instrument that scans the spectrum to record power, measures the value of loss
analyzer insertion and tests the performance of the wavelength and optical signal noise ratio
(OSNR) of each channel.
Orderwire The link that provides voice communication between stations for operators or
maintenance engineers.
OSC Optical Supervisory Channel. A technology realizes communication among nodes in
optical transmission network and transmits the monitoring data in a certain channel (the
wavelength of the working channel for it is 1510 nm and that of the corresponding
protection one is 1625 nm).
P
Pass-Through A mode in which the transmission equipment directly forwards the received services to
the next station and the local station only detects the signal quality.
Power box A direct current power distribution box at the upper part of a cabinet, which supplies
power for the subracks in the cabinet.
R
Receiver sensitivity Receiver sensitivity is defined as the minimum acceptable value of average received
power at point R to achieve a 1 x 10-12 BER.
REG A piece of equipment or device that regenerates electrical signals.
Ring network One type of network that all network nodes are connected one after one to be a cycle.
Route The path a trail takes.
S
Side mode suppression The ratio of the largest peak of the total source spectrum to the second largest peak.
ratio
T
T2000 A network management system that Huawei provides to manage transmission networks.
The T2000 is located between the NE level and the network level in the
telecommunication management network structure. That is, the T2000 is a subnetwork
management system. The T2000 provides all management functions at the NE layer and
some of the management functions at the network layer.
Issue 01 (2009-08-10) Huawei Proprietary and Confidential A-3

Platform
A Glossary Maintenance Cases
Trail A type of transport entity, mainly engaged in transferring signal from the input of the
trail source to the output of the trail sink, and monitoring the integrality of the transferred
signal.
U
Upper subrack The subrack close to the top of the cabinet when a cabinet contains several subracks.
User The user of the T2000 client, and the user and password define the corresponding
authority of operation and management of the T2000.
Y
Wander In telecommunication, wander are long-term random variations of the significant instants
of a digital signal from their ideal positions.
A-4 Huawei Proprietary and Confidential Issue 01 (2009-08-10)

Platform
Maintenance Cases B Acronyms and Abbreviations
B Acronyms and Abbreviations
ADM Add and Drop Multiplexer
AFEC Advanced Forward Error Correction
AGC Automatic Gain Control
AIS Alarm Indication Signal
ALS Automatic Laser Shutdown
ARP Address Resolution Protocol
ASON Automatic Switched Optical Network
BDI Backward Defect Indication
CRC Cyclical Redundancy Check
DCC Data Communication Channel
DCM Dispersion Compensation Module
DWDM Dense Wavelength Division Multiplexer
ECC Embedded Control Channel
Issue 01 (2009-08-10) Huawei Proprietary and Confidential B-1

Platform
B Acronyms and Abbreviations Maintenance Cases
FC Fiber Channel
FEC Forward error correction
GE Gigabit Ethernet
HP Higher Order Path
ID Identity
IEEE Institute of Electrical and Electronic Engineers
IP Internet Protocol
ITU-T International Telecommunication Union-Telecommunication

Sector
LAN Local Area Network
LOF Loss Of Frame
LOS Loss Of Signal
MS Multiplex Section
NE Network Element
OADM Optical Add/Drop Multiplexer
B-2 Huawei Proprietary and Confidential Issue 01 (2009-08-10)

Platform
Maintenance Cases B Acronyms and Abbreviations
ODF Optical Distribution Frame
OEQ Optical Equalizer
OLA Optical Line Amplifier
OMS Optical multiplex section
OOF Out Of Frame
OPU Optical Channel Payload Unit
OSC Optical Supervisory Channel
OSI Open Systems Interconnection
OSN Optical Switch Node
OSNR Optical Signal-to-noise Ratio
OTDR Optical Time-Domain Reflectometer
OTM Optical Transport Module
OTU Optical Transponder Unit
PIN Positive Intrinsic Negative
PMD Polarization Mode Dispersion
QoS Quality of Service
RDI Remote Defect Indication
ROADM Reconfigurable Optical Add/drop Multiplexer
SC Switched Connection
SCC System Control & Communication
SD Signal Degrade
SDH Synchronous Digital Hierarchy
SLIP Serial Line Internet Protocol
Issue 01 (2009-08-10) Huawei Proprietary and Confidential B-3

Platform
B Acronyms and Abbreviations Maintenance Cases
SM Section Monitoring
SONET Synchronous Optical Network
TTL Transistor-Transistor Logic
VLAN Virtual Local Area Network
VOA Variable Optical Attenuator
WDM Wavelength Division Multiplex
WXCP Wavelength Cross-Connection Protection
B-4 Huawei Proprietary and Confidential Issue 01 (2009-08-10)


Maintenance Cases (V100R004C04 - 01)

Uploaded by

Copyright:

Available Formats

You might also like

Maintenance Cases (V100R004C04 - 01)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Maintenance Cases (V100R004C04 - 01)

Uploaded by

Copyright:

Available Formats

OptiX OSN 6800 Intelligent Optical Transport Platform/OptiX OSN

3800 Compact Intelligent Optical Transport Platform

Huawei Proprietary and Confidential

Huawei Technologies Co., Ltd.

Copyright © Huawei Technologies Co., Ltd. 2009. All rights reserved.

Trademarks and Permissions

Huawei Proprietary and Confidential

About This Document.....................................................................................................................1

4 Classified by Functions and Features....................................................................................4-1

Issue 01 (2009-08-10) Huawei Proprietary and Confidential i

4.7 Other Cases.....................................................................................................................................................4-4

ii Huawei Proprietary and Confidential Issue 01 (2009-08-10)

Issue 01 (2009-08-10) Huawei Proprietary and Confidential iii

iv Huawei Proprietary and Confidential Issue 01 (2009-08-10)

Figure 5-1 Networking diagram.......................................................................................................................5-113

Issue 01 (2009-08-10) Huawei Proprietary and Confidential v

Table 5-1 PMD coefficient relation....................................................................................................................5-71

Issue 01 (2009-08-10) Huawei Proprietary and Confidential vii

About This Document

l Field Maintenance Engineer

1 Classified by Products When the entry of classification by products is selected,

2 Classified by Faults When the entry of classification by faults is selected, the

3 Classified by Alarms When the entry of classification by alarms is selected, the

Issue 01 (2009-08-10) Huawei Proprietary and Confidential 1

A Glossary Lists the glossary mentioned in this document.

B Acronyms and Lists the abbreviations and acronyms mentioned in this

Indicates a hazard with a high level of risk which, if not

Indicates a hazard with a medium or low level of risk which,

Indicates a potentially hazardous situation that, if not

NOTE Provides additional information to emphasize or

Times New Roman Normal paragraphs are in Times New Roman.

2 Huawei Proprietary and Confidential Issue 01 (2009-08-10)

Italic Book titles are in italics.

Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italic.

[] Items (keywords or arguments) in square brackets [ ] are

{ x | y | ... } Alternative items are grouped in braces and separated by

[ x | y | ... ] Optional alternative items are grouped in square brackets

{ x | y | ... } * Alternative items are grouped in braces and separated by

Issue 01 (2009-08-10) Huawei Proprietary and Confidential 3

Updates in Issue 02 (2009-07-20) Based on Product Version V100R004C03

Updates in Issue 01 (2009-05-20) Based on Product Version V100R004C03

Updates in Issue 02 (2009-03-25) Based on Product Version V100R004C02

Updates in Issue 01 (2008-12-31) Based on Product Version V100R004C02

4 Huawei Proprietary and Confidential Issue 01 (2009-08-10)

About This Chapter

1.1 OptiX BWS 1600G

Issue 01 (2009-08-10) Huawei Proprietary and Confidential 1-1

1.1 OptiX BWS 1600G

1-2 Huawei Proprietary and Confidential Issue 01 (2009-08-10)

Issue 01 (2009-08-10) Huawei Proprietary and Confidential 1-3

1.2 OptiX Metro 6100

1-4 Huawei Proprietary and Confidential Issue 01 (2009-08-10)

l 5.91 MC-A99: The PMU Reports the THUNDERALM Alarm

1.3 OptiX Metro 6040

1.4 OptiX OSN 6800

Issue 01 (2009-08-10) Huawei Proprietary and Confidential 1-5

l 5.78 MC-A86 Inserting, Removing, and Resetting Operations Affect NG WDM