Huawei Optical Network Maintenance Reference NA-20110812-C

Huawei Optical Network
Maintenance Reference_NAWDM
Issue
01
Date
2011-08-10
CONFIDENTIAL
Huawei Technologies Co., Ltd.
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service.
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. 2011. 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 trademarks 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 all statements, information, and
recommendations in this document do not constitute a warranty of any kind, expressed or implied.
Acknowledgement
This document is prepared and reviewed by the WDM R&D Maintenance Team, Information Development
Dept, Customer Support Dept, and Technical Support Dept together.
Editor:
Jiang Yi, Bai Zhongqiang, Li Qingsong, Wu Siyong, Zhang Xiaohua, Zhou Yuxing
Others:
WDM R&D Maintenance Team: Bao Yuliang, Cai Yaqing, Chen Gang, Deng Jingliang, Gong Xiongbin,
Huang Jianfei, Hu Kewei, Hu Xi, Jin Xiaoming, Liu Gang, Liu Yan, Lu Jun, Xu Cheng, Yuan Bin, Zhang
Meng, Zhuang Chenjian, Wang Yunpeng
Information Development Dept: Zheng Fan, Pei Xin
Technical Support Dept: Dou Yongtan, Xie Bing
Customer Support Dept: Zhang Junguang, Fu Ming, Yu Ding
Quality Assurance Dept: Zhang Enhua
Special acknowledgements to Jin Yuzhi, Mu Jianhong, Feng Zhigang, Wu Gang, and Niu Shouchang
Huawei Optical Network Maintenance Reference_NA- WDM
Contents
1 Overview......................................................................................................................................... 7
2 SOP for Routine Maintenance of WDM Products.................................................................. 8
2.1 Overview .......................................................................................................................................................... 8
2.2 SOP .................................................................................................................................................................. 9
3 Guidelines for Identifying WDM Faults................................................................................ 16

3.1 Preparations for Fault Identification............................................................................................................... 16
3.2 Basic Rules for Fault Identification................................................................................................................ 17
3.3 Methods of Fault Identification ...................................................................................................................... 18
3.3.1 Signal Flow Analysis ............................................................................................................................ 19
3.3.2 Alarm and Performance Event Analysis ............................................................................................... 19
3.3.3 Loopback .............................................................................................................................................. 20
3.3.4 Replacement.......................................................................................................................................... 21
3.3.5 Configuration Data Analysis ................................................................................................................. 22
3.3.6 Testing with Instruments ....................................................................................................................... 22
3.3.7 Experience-Based Analysis ................................................................................................................... 23
3.3.8 RMON Performance Analysis .............................................................................................................. 23
4 Guide to Emergency Fault Handling ...................................................................................... 24

4.1 General Fault Handling Process ..................................................................................................................... 25
4.2 Process Description ........................................................................................................................................ 26
4.3 Preparations .................................................................................................................................................... 26
4.3.1 Routine Maintenance Operations .......................................................................................................... 26
4.3.2 Engineering Information ....................................................................................................................... 27
4.3.3 Requirements for Maintenance Personnel............................................................................................. 27
4.3.4 Collection and Saving of Field Data ..................................................................................................... 28
4.3.5 Tools and Meters ................................................................................................................................... 28
4.4 Emergency Handling Process ......................................................................................................................... 29
4.4.1 Emergency Handling Process for Rectifying Service Interruption ....................................................... 30
4.5 Sub-process for Rectifying Faults Related to Abnormal Optical Power ........................................................ 34
4.5.1 Flow Chart 1 ......................................................................................................................................... 35
4.5.2 Flow Chart 2 ......................................................................................................................................... 36
4.5.3 Process Description ............................................................................................................................... 37
4.6 Sub-process for Rectifying Faults Related to Bit Errors ................................................................................ 37
Issue 01 (2011-08-10)
Huawei Proprietary and Confidential
Page 3 of 95

4.6.1 Flow Chart ............................................................................................................................................ 39
4.6.2 Process Description ............................................................................................................................... 39
4.7 Fault Locating by Performing Loopbacks ...................................................................................................... 41
4.8 Rectifying Interruption of Client-Side Services ............................................................................................. 47
4.8.1 Rectifying Interruption of Services Without Protection ........................................................................ 47
4.8.2 Rectifying Interruption of Services with Protection.............................................................................. 49
4.9 Rectifying Interruption of the Service on a Subwavelength (ODUk) ............................................................ 50
4.9.1 Rectifying Interruption of Services Without Protection ........................................................................ 50
4.9.2 Rectifying Interruption of Services with Protection.............................................................................. 50
4.10 Rectifying Interruption of the Service on a Single Wavelength ................................................................... 51
4.10.1 Rectifying Interruption of Services Without Protection ...................................................................... 51
4.10.2 Rectifying Interruption of Services with Protection............................................................................ 53
4.11 Rectifying Interruption of Services on Multiple Wavelengths ..................................................................... 53
4.11.1 Rectifying Interruption of Services Without Protection ...................................................................... 54
4.11.2 Rectifying Interruption of Services with Protection ............................................................................ 55
4.12 Manually Restoring Services........................................................................................................................ 56
4.13 Service Interruption Caused by Misoperations ............................................................................................ 57
5 Identifying Faults in Interconnection Between WDM and Other Products ................... 60

5.1 Design Constraints for Interconnecting WDM Products and Routers ............................................................ 60
5.1.1 Standard Compliance ............................................................................................................................ 60
5.1.2 Checking Configuration for Interconnecting WDM Products and Other Products on a Network with
Protection ....................................................................................................................................................... 61
5.1.3 Checking Configuration for Interconnecting WDM Products and Other Products on a Network
Without Protection ......................................................................................................................................... 62
5.2 Common Methods for Identifying Interconnection Faults ............................................................................. 63
6 Appendix I: WDM Alarm Signal Flow ................................................................................... 64

6.1 Background Knowledge ................................................................................................................................. 65
6.2 Non-Convergent OTU Processing Standard SONET/SDH Signals ............................................................... 65
6.3 Non-Convergent OTU Processing OTN Standard Signals ............................................................................. 69
6.4 Convergent OTU Processing SONET/SDH Standard Signals ....................................................................... 73
6.5 Convergent OTU Processing OTN Standard Signals ..................................................................................... 76
6.6 Regenerating OTU ......................................................................................................................................... 79
6.7 Alarm Signal Processing of the OTU with the Cross-Connect Function ....................................................... 81
6.8 OTU Processing GE Signals .......................................................................................................................... 82
6.9 Optical-Layer Alarm Signal Processing on OTN ........................................................................................... 84
7 Appendix II: OTN Protection ................................................................................................... 89

7.1 Client-Side 1+1 Protection (OTU 1+1) .......................................................................................................... 90
7.2 Optical Line Protection (OLP) ....................................................................................................................... 90
7.3 ODUk SNCP (OTN 1+1 Channel Protection) ................................................................................................ 91
8 Appendix III: Wavelength and Frequency Allocation Table ............................................. 94
Issue 01 (2011-08-10)
Page 4 of 95
Figures
Figure 4-1 General fault handling process .......................................................................................................... 25
Figure 4-2 Emergency handling process for rectifying service interruption ....................................................... 30
Figure 4-3 Sub-process 1 for rectifying faults related to abnormal optical power .............................................. 35
Figure 4-4 Sub-process 2 for rectifying faults related to abnormal optical power .............................................. 36
Figure 4-5 Sub-process for rectifying faults related to bit errors......................................................................... 39
Figure 4-6 Loopback diagram when tributary and line boards are interconnected at the sites on two ends ........ 42
Figure 4-7 Loopback diagram when two tributary-line boards are interconnected at the sites at the ends ......... 46
Figure 6-1 Alarm signal flow 1 when non-convergent OTU processes SONET/SDH standard signals ............. 66
Figure 6-2 Alarm signal flow 2 when non-convergent OTU processes SONET/SDH standard signals ............. 68
Figure 6-3 Alarm signal flow 1 when non-convergent OTU processes OTN standard signals ........................... 70
Figure 6-4 Alarm signal flow 2 when non-convergent OTU processes OTN standard signals ........................... 72
Figure 6-5 Alarm signal flow 1 when convergent OTU processes SONET/SDH standard signals ..................... 74
Figure 6-6 Alarm signal flow 2 when convergent OTU processes SONET/SDH standard signals ..................... 75
Figure 6-7 Alarm signal flow 1 when convergent OTU processes OTN standard signals .................................. 77
Figure 6-8 Alarm signal flow 2 when convergent OTU processes OTN standard signals .................................. 78
Figure 6-9 Alarm signal flow of the regenerating OTU ...................................................................................... 80
Figure 6-10 OTU unit with the cross-connect function in straight-through mode .............................................. 81
Figure 6-11 OTU unit with the cross-connect function in cross-connect mode .................................................. 82
Figure 6-12 Alarm signal flow 1 when the OTU processes GE signals .............................................................. 83
Figure 6-13 Scenario I ......................................................................................................................................... 84
Figure 6-14 Scenario II........................................................................................................................................ 85
Figure 6-15 Scenario III ...................................................................................................................................... 86
Issue 01 (2011-08-10)
Page 5 of 95
Tables
Table 4-1 Required tools and meters for handling a fault .................................................................................... 28
Table 7-1 Trigger conditions of ODUk SNCP protection .................................................................................... 92
Table 8-1 Wavelength and frequency allocation table (OptiX OSN 6800A and OptiX OSN 8800) .................... 94
Issue 01 (2011-08-10)
Page 6 of 95
Overview
This maintenance collection provides guidelines to assist maintenance personnel with

operating and maintaining WDM equipment.
SOP for Routine Maintenance of WDM Products

This chapter describes the items and operations necessary for routine maintenance of
WDM products. By performing standard operations during routine maintenance, a
maintenance engineer can discover and remove potential network problems, therefore
avoiding risks to equipment and ensuring stable and secure network operations.
Guidelines for Identifying WDM Faults

This chapter describes the major approaches applicable to identifying faults on WDM
products. These approaches therefore help maintenance personnel understand how to
identify and troubleshoot faults.
Guide to Emergency Fault Handling

This chapter describes the restoration measures that can be taken in case of emergencies,
such as service interruption to restore the normal state of equipment.
Identifying Faults in Interconnection Between WDM and Other Products

This chapter describes the methods of identifying common faults in interconnection
between WDM products and other products.
Appendix I: WDM Alarm Signal Flow

This chapter describes how alarms are generated, detected, and transferred when OTU
boards receive signals of various types. By verifying the alarms, a maintenance engineer
can identify the cause of a fault.
Appendix II: OTN Protection

This chapter describes how to configure common protection and how protection is
implemented.
Appendix III: Wavelength and Frequency Allocation Table

This chapter provides the wavelength and frequency allocation table.
Issue 01 (2011-08-10)
Page 7 of 95
SOP for Routine Maintenance of WDM

Products
Objective
By performing standard operations during routine maintenance, a maintenance engineer can
discover and remove potential network problems, therefore avoiding risks to equipment and
ensuring stable and secure network operations.
Intended Audience
System maintenance personnel
Application Scenario
Equipment maintenance personnel perform operations and maintenance actions included in
the maintenance SOP during routine maintenance periods and at a recommended frequency.
2.1 Overview
Description of maintenance SOP: The maintenance SOP for WDM products provides
standard procedures for maintaining WDM products by project. It focuses on "what to
do" during and "how to do" the routine maintenance of WDM products on a network.
Orientation of maintenance SOP: By performing standard operations during routine

maintenance periods, a maintenance engineer can identify and remove potential network
problems, therefore avoiding risks to equipment and ensuring the network is stable and
securely operating.
Issue 01 (2011-08-10)
Page 8 of 95
2.2 SOP
Item
Subitem
Frequency
Implementation Method
Priority
Preparations
Collecting
network
information
Monthly
Obtain network information and update changes

to the documentation as they occur.
Minor
Checking
version
mapping
information
Monthly
Preparing
maintenance
tools
Monthly
Issue 01 (2011-08-10)
1.
Update the network design PPT

documents, MDS engineering documents,
and wavelength allocation diagrams, and
obtain accurate distance and fibers types
used on the lines between two sites,
dispersion coefficient, and OSNR.
2.
Obtain special network configurations, for

example, protection types and special
functions such as IPA, ALC, and APE.
3.
Identify equipment that is connected to

third-party equipment. Pay attention to
special configurations and compatibility
requirements for interconnection. For
details, see section 5: Identifying Faults in
Interconnection Between WDM and Other
Products of Huawei Optical Network
Maintenance Reference - WDM.
4.
Obtain engineering design documents,

including slot layouts, fiber connection
diagrams, mappings between site names,
IDs and IP addresses, telecommunications
room cabling diagram, telecommunications
room layouts, and port allocations on the
ODF.
5.
Obtain the NMS managed objects (MOs)

and scripts.
6.
Obtain the historical preventive

maintenance inspection (PMI) information
of sites.
7.
Obtain the manufacturer information of

boards on the entire network from the
NMS.
1.
Collect the version information (patch

version information included) of all NEs,
the NMS, and tools.
2.
Check whether the site version is

customized, and make upgrade plans based
on the results.
Contact Huawei engineers to prepare

maintenance tools, such as the NMS, PMI tools,
fault collection tools, and the DC tool.
Major
Minor
Page 9 of 95
Item
Equipment
status check
Subitem
Frequency
Priority
Applying for
maintenance
accounts
Monthly
Apply for account names and passwords for

maintenance, including the user names and
passwords for logging in to the NMS and
remotely accessing the VPN.
Major
Preparing
instruction
documents
Monthly
Obtain the Release Notes for the required

versions, product manuals including Hardware
Description, Commissioning Guide, and
Troubleshooting, and Operation Manuals of the
related tools.
Major
Checking the
inventory of
spare parts
Quarterly
Collect information about existing boards on a

live network and contact Huawei engineers to
check on the spare parts of these existing boards
by using the spare part PTO model.
Minor
Checking for
alarms
Daily
1.
Verify automatic alarm reporting is

properly configured per NE. Set alarm
suppression for specific alarms.
Critical
2.
Check NE alarms and ensure that no

unexpected critical alarm exists.
3.
Clear all alarms on the live network. If an

alarm cannot be cleared, determine the
cause and discuss resolution.
1.
Verify that performance monitoring is

enabled on the equipment.
2.
Check the transmit and receive optical

power of OTU boards, line boards, and
tributary boards, ensuring that they are
within the permitted range.
3.
Check performance of OTU boards, line

boards, and tributary boards. For 10G or
lower-rate boards, ensure that the bit error
rate (FEC-BEF-COR-ER) is 10E-5 or
lower; for 40G boards, ensure that the
FEC-BEF-COR-ER is 10E-4 or lower.
Ensure that there are no bit errors
generated after error correction. In
addition, check the current and historical
15-minute/24-hour performance data of the
WDM sides of the boards and ensure that
there are no uncorrectable frames.
4.
Check service data and ensure that there

are no abnormal RMON performance
events.
Checking
equipment
performance
Issue 01 (2011-08-10)
Daily
Critical
Page 10 of 95
Item
Subitem
Frequency
Priority
Checking
ambient
environment
Daily
1.
Check the ambient temperature inside the

telecommunications room and the
equipment operating temperature; ensure
that they are within the permitted ranges.
Major
2.
Ensure that the equipment surface and

telecommunications rooms are tidy and
clean.
3.
Ensure that there are no signs of rodents or

insects, such as rat holes and biological
waste.
1.
Check the working status of each service

protection group and the working and
protection channels of each group. Check
for unexpected protection switching. If a
signal fail (SF) occurs, identify the cause
and correct it.
2.
Check the protection status of boards,

including the active and standby
cross-connect boards, power supply
boards, clock boards, and SCC. Ensure that
they are working properly.
1.
Ensure service types, line rates (standard

mode or speedup mode), and FEC modes
(AFEC or STDFEC) on the working and
protection channels are the same.
2.
For SNCP protection, the SNCP type must

be set to SNC/N when services traverse
regeneration boards.
Checking
protection
group status
Daily
Major
Checking
service types
and rates on
the working
and
protection
channels
Quarterly
Checking the
manufacturer
information
of boards on
the entire
network
Monthly
Export the manufacturer information of all

boards on the network from the NMS when
applying for spare parts or statistics collection.
Major
Periodically
cleaning the
air filter
Every two
weeks
Clean the air filter with water and dry it with a

cloth. If necessary, use a blow dryer to ensure
no moisture exists before installing.
Major
Periodically
replacing the
air filter
Every six
months
Replace the air filter.
Major
Issue 01 (2011-08-10)
Major
Page 11 of 95
Item
Subitem
Frequency
Priority
System
security
check
Checking
optical power
of OA boards
Daily
1.
Periodically export the 24-hour

performance values from the NMS.
Major
2.
Check the 24-hour optical power of optical

amplifier (OA) boards when the number of
wavelengths remains constant. Ensure the
change in the optical power is within 1
dBm and the difference between the actual
optical power of the OA boards and the
theoretically calculated optical power is
equal to or less than 2 dBm.
3.
Check the optical power of OA boards and

adjust the optical power according to the
nominal optical power. For example, the
output optical power of a single
wavelength in a 40-channel system is +4
dBm and that in an 80-channel system is
+1 dBm.
Checking NE
data
consistency
Issue 01 (2011-08-10)
Monthly
Choose all NEs in Configuration Data

Management List on the NMS to check
consistency of all NE data in a one-click
manner. If the data stored on the NMS and the
data stored on the NEs are inconsistent,
determine which is incorrect based on actual
requirements. If the data on the NMS is
incorrect, upload the NE data to the NMS; if the
data on the NEs is incorrect, contact Huawei
engineers.
Major
Page 12 of 95
Item
Subitem
Frequency
Priority
Backing up
data and
checking the
backup data
Daily
1.
Ensure that the automatic backup function

is enabled for the databases.
Minor
2.
Check the protection mode of the

databases.
Use a PMI tool and perform the check item

(Check the current mode of a database).
Ensure the databases are not in protection
mode. A normal value should be returned
using the tool.
Or run TL1 commands. The highlighted part

in the following information should be
Normal.
>RTRV-DBMS-MODE:::C
RTRV-DBMS-MODE:::C;
DNVTCO56HT10319 1990-01-01 13:08:58
M
C COMPLD
"NORMAL,0"
Alarm
analysis and
processing
Identifying
alarm
severities
Clearing
alarms
Issue 01 (2011-08-10)
Daily
Daily
3.
Ensure the equipment data has been

periodically backed up to the NMS server
or client. Contact Huawei engineers to
check the database data on the live network
by using the UpgradeKit and verify no
database exception occurs. To obtain the
UpgradeKit, visit
http://support.huawei.com.
1.
Sort the critical and major alarms based on

the principles: critical and major alarms
must be cleared prior to minor alarms and
alarms on line boards must be cleared prior
to alarms on tributary boards.
2.
Place a high priority on clearing alarms

that concern customers.
1.
Confirm the identified alarms one by one.

If an alarm is generated at an idle port, it is
recommended that you suppress after
receiving confirmation from customers.
2.
Devise a solution for persistent alarms and

assist customers with clearing all such
alarms.
3.
Clear all alarms on the live network. If an

alarm cannot be cleared, identify the cause.
Critical
Critical
Page 13 of 95
Item
Equipment
load
assessment
Analysis of
special
functions
Subitem
Frequency
Priority
Analyzing
historical
alarm
summary
Weekly
Analyze the equipment historical alarms.

Identify the causes of the historical critical
alarms and verify they are cleared to prevent
alarms caused by inappropriate equipment
operations.
Major
Checking the
quantity of
OptiX OSN
6800A/8800
subracks on a
live network
Quarterly
1.
When both OptiX OSN 6800A and OptiX

OSN 8800 subracks are deployed, the
OptiX OSN 8800 subrack must be the
master subrack.
Minor
2.
Ensure the quantity of master and slave

OptiX OSN 6800A/8800 subracks satisfies
the design requirements. For the quantity
requirements of subracks, see the
description of the master and slave
subracks in the corresponding Product
Description.
Checking the
IP Over DCC
protocol
Quarterly
1.
A GNE can connect to a maximum of 50

non-GNEs (50 non-GNEs are
recommended). If a GNE connects to more
than 60 non-GNEs, another GNE must be
used. (The non-GNEs in this contest refer
to equivalent NEs.)
2.
When the IP over DCC protocol is used, a

maximum of 250 NEs can be configured
on a DCN subnet.
3.
A GNE and its non-GNEs must have the

same OSPF settings, including Area, Hello
Timer, and Dead Timer.
Checking the
IPA function
Issue 01 (2011-08-10)
Monthly
If an IPA pair and Raman boards are configured

on an NE, check the following items:
1.
The Raman boards must be configured in

the IPA pair.
2.
The optical power of a Raman board must

be within the range of -60 dBm to 0 dBm.
3.
The optical power of the detection board in

the IPA pair must be within the range of
-35.0 dBm to -14.0 dBm.
Minor
Major
Page 14 of 95
Item
Subitem
Frequency
Priority
Checking the
ALC function
Monthly
1.
For a node that adds or drops a

wavelength, it is recommended to
configure the optical amplifier unit in the
receive direction as the detection node and
the optical amplifier unit in the transmit
direction as the reference unit.
Major
2.
Information about ALC nodes must be

recorded in TIDIPMAP tables. (Each NE
maintains a table, which records the TIDs
of reachable NEs in the network and
provides the IP address mapping
relationships.)
3.
Update the ALC status on the NMS and

ensure that no error is reported.
1.
Ensure the physical fiber connections and

logical fiber connections are consistent.
2.
Verify if an IN-PWR-HIGH or
IN-PWR-LOW alarm is reported on the
WMU board. If yes, ensure that the IN port
on the WMU board is properly connected.
3.
Verify the configuration of the WMU pair

is consistent with the configuration of
physical fiber connections. Verify the
IN1/IN2 port on the WMU board is
connected to the MON port on the
corresponding OA board. Otherwise,
wavelength wander occurs on all the OTU
boards.
4.
Verify if a WAVELEN-OVER alarm

indicating wavelength wander is reported.
If yes, ensure the fiber is properly
connected.
Checking the
WMU
function
PMI
Monthly
Major
Checking the
integrity of
the E2E path
information
Quarterly
Verify all E2E paths can be found in the NMS.

If an E2E path cannot be found, check the
integrity of the path.
Minor
Performing
PMIs
Monthly
Perform PMIs using the associated tools and

select preventive maintenance items based on
equipment types.
Major
Issue 01 (2011-08-10)
Page 15 of 95
Guidelines for Identifying WDM Faults
Objective
This chapter provides guidelines to identify faults in a WDM optical transmission system.
These approaches help maintenance personnel understand how to identify a fault according to
fault symptoms.
Intended Audience
Equipment maintenance personnel need to identify a fault in equipment.
3.1 Preparations for Fault Identification

Equipment maintenance personnel must make the following preparations for fault
identification:
Issue 01 (2011-08-10)
Master the following professional skills:
Basic working principles of a WDM system
Cause of a WDM system alarm and the process of generating an alarm signal flow
Handling of common alarms
Basic operations on common instruments
Attain familiarity with the following engineering network information:
Network topology
Service configuration
Equipment operating status
Engineering documents
Collect fault data in the field and properly save the data:
Page 16 of 95
3.2 Basic Rules for Fault Identification
Issue 01 (2011-08-10)
Page 17 of 95
3.3 Methods of Fault Identification
Common methods for fault identification have their own features. The following table lists
comparisons between these fault identification methods. Using multiple fault identification
methods helps to quickly identify network faults. In practice, maintenance personnel usually
need to apply more than one method to locate faults and clear them.
Method
Application Scope
Feature
Signal flow analysis
General
Comprehensive understanding of the entire network
Predicting potential equipment hazards
Comprehensive understanding of the entire network
Predicting potential equipment hazards
No impact on normal services
Easy to use
Independent of alarms and performance events

analysis
May affect NE communication and services
To identify a board with a

fault or to exclude an
external fault
Simple
Requiring spare parts
To identify a board with a

fault
Identifying the fault cause
Requiring long time
Alarm and
performance event
analysis
General
Loopback
To identify a site with a fault

or to exclude an external
fault
Replacement
Configuration data
analysis
Issue 01 (2011-08-10)
Page 18 of 95
Method
Application Scope
Feature
Testing with
instruments
To exclude an external fault

or to resolve an
interconnection problem
Persuasive
Requiring instruments
Experience-based
analysis
Applicable to special cases
Simple operations
RMON
performance
analysis
Applicable to data services

only
Routine statistics
Analysis of service performance and alarms on

Ethernet boards
3.3.1 Signal Flow Analysis

Analyzing the service signal flow helps to quickly identify a fault.
3.3.2 Alarm and Performance Event Analysis
Issue 01 (2011-08-10)
Page 19 of 95
Complete information
Fault information about networkwide equipment,instead of a single station or board
Detailed information
Active alarms and history alarms of equipment, and alarm generation time
Specific statistics on performance events
Priority principle
Handle Optical-layer LOS,electrical- layer OTU-LOF,protection switching,and board-level
(BUS-ERR,EQPT-NSA,COMM-FAIL)
Applicable for NM maintenance personnel to troubleshoot faults
Analysis of alarms and performance events, and alarm signal flows helps quickly identify a fault.
3.3.3 Loopback
Issue 01 (2011-08-10)
Page 20 of 95
3.3.4 Replacement
Possible causes on equipment outside the transmission
system are excluded.
After a single station with the fault is identified, it is suspected
that a board or accessory at the station is faulty.
When you use the method of replacement, you replace a

suspected malfunctioning component with a normal component.
Replaceable components include cables, fibers, fiber adapters,
power supplies, boards, and equipment.
Issue 01 (2011-08-10)
Page 21 of 95
3.3.5 Configuration Data Analysis
3.3.6 Testing with Instruments
Issue 01 (2011-08-10)
Page 22 of 95
3.3.7 Experience-Based Analysis
3.3.8 RMON Performance Analysis
Issue 01 (2011-08-10)
Page 23 of 95
Guide to Emergency Fault Handling
Objective
This chapter describes how to restore services that have been affected due to emergency
situations, such as a service interruption on WDM equipment in an optical transport system. It
provides guidelines to assist maintenance personnel in restoring normal equipment operation.
Intended Audience
When critical problems occur, such as a service interruption, equipment maintenance
personnel can identify faults quickly based on the guidelines provided in this chapter. For a
service interruption in a WDM system due to an external fault, (such as a power failure or
fiber cut), misoperation, or a software/hardware fault, maintenance personnel can quickly
identify the fault or ask for assistance in a timely manner according to the emergency
handling process described in section 4.4 and then restore services.
Preventive Measures
To stabilize the operation of a WDM optical transport system and minimize potential critical
problems, perform routine maintenance in compliance with the SOP for Routine Maintenance
of WDM Products.
Issue 01 (2011-08-10)
Page 24 of 95
4.1 General Fault Handling Process

Figure 4-1 General fault handling process
Start
Record fault
symptom
An external
cause?
Yes
Rectify the
external fault
No
Analyze and locate the
fault
Fault is
rectified?
Yes
No
Contact Huawei technical
support engineers
Work out
solutions together
Try to rectify the
fault
No
Services are
restored?
Yes
Observe the running
status of the equipment
No
Fault is
rectified?
Yes
Prepare a fault
handling report
End
Issue 01 (2011-08-10)
Page 25 of 95
When handing critical problems, such as a service interruption, exercise the following
precautions:
Restore services as soon as possible.
Analyze the fault symptom, and then handle the fault after identifying the cause. When the
cause is unknown, avoid performing random operations, which may lead to more severe
problems.
When a fault cannot be resolved, contact Huawei engineers for technical support.
Coordinate with Huawei engineers to handle the fault, so as to minimize the service
interruption duration.
Record the operations performed during fault handling, and save the original data related
to the fault.
4.2 Process Description
Record important details of a fault, such as the fault start time and the operations
performed before and after the fault occurred. In addition, save alarms and performance
events on the T2000 NA/U2000.
If a fault is caused by an external factor, such as a power failure, an optical cable fault,
an environmental change in the telecommunications room, or a terminal equipment issue,
handle the fault based on the usual practiced company procedures.
If a fault is caused by the equipment, the information in this chapter will help with
handling such faults. During fault handling, strictly comply with the operation rules to
perform operations on equipment. For example, wear an ESD wrist strap.
When a fault cannot be resolved, contact Huawei engineers for technical support and
coordinate with Huawei engineers to resolve the fault.
After services are restored, observe the service running status to confirm the fault has
been resolved.
Complete the handling report after troubleshooting.
4.3 Preparations
To ensure a fault can be identified and resolved quickly, prepare the following:
Routine maintenance operations
Engineering information
Maintenance personnel with sufficient professional skills and knowledge
Spare parts, tools, and meters
4.3.1 Routine Maintenance Operations

During routine network maintenance, perform the following operations to identify and
remove potential network problems or to help locate a fault quickly:
Issue 01 (2011-08-10)
Collecting network information
Page 26 of 95
Checking alarms
Checking the status of protection groups
Checking optical power
Backing up data and checking the backup data
Checking optical power of optical amplifier boards (evaluating load)
For details on the operation guide and requirements for each routine maintenance item, see the
SOP for Routine Maintenance of WDM Products.
4.3.2 Engineering Information

To ensure a fault can be identified and resolved quickly, collect the following engineering
information:
Fiber connection diagram

The diagram must include the mapping relationship between NE names and NE IP
addresses with the gateway NEs being marked.
Slot layout
Network topology diagram

The slot layout of each board on service trails must be clear. Obtain the service trail
information immediately when a fault occurs.
Engineering configuration diagram
Channel allocation diagram
Diagram of protection service trails

Determine whether the working route or protection route is currently in use. For services
on overlapped rings, determine the service that is selectively received. Ensure the
configurations, (such as service type and service rate) on the working and protection
channels in a protection group are the same.
24-hour and 15-minute performance data on the NMS
Fault information
Record the specific time when services are affected, and collect the alarms and
performance events generated at that time.
Detailed operation records

Record the operations, such as service scheduling, during fault locating and handling.
Field data
According to the alarm information, collect the upstream and downstream boards
information by using the fault collection tool for WDM equipment.
The diagrams must be updated in case of network expansion or optimization.
4.3.3 Requirements for Maintenance Personnel

Professional Skills
Familiar with fundamentals of the DWDM system.
Familiar with alarm signal flows and the alarm generation mechanism in the WDM
transport system.
Familiar with common alarm troubleshooting.
Issue 01 (2011-08-10)
Page 27 of 95
Familiar with basic operations on common meters for transmission equipment.

The common meters for transmission equipment include an optical power meter, optical spectrum
analyzer, oscilloscope, and multimeter. For the use of these meters, see the related manuals for each
meter.
Visit http://support.huawei.com regularly to obtain and learn about the product-related

materials.
Expertise in Basic Operations
Operations on various WDM products in the optical transport system.
Operations on various application servers.
Operations on the NMS for the transmission equipment.
Familiarity with Network Layout of the Optical Transport System
Familiar with common network types of the WDM optical transport system.
Familiar with the network layout at the site under maintenance.
Familiar with the running status of the equipment at the site under maintenance.
4.3.4 Collection and Saving of Field Data

Collect and save the field data periodically during normal equipment operation and when a
fault occurs. Maintenance personnel must collect and save the field data before handling a
fault.
According to the alarm information, maintenance personnel can collect the upstream and
downstream boards information by using the fault collection tool for WDM equipment.
4.3.5 Tools and Meters

Table 4-1lists the required tools and meters for handling a fault.
Table 4-1 Required tools and meters for handling a fault
Tool
Usage
Optical power meter
Measures optical power.
Fiber jumper
Replaces a faulty fiber patch cord.
Fiber binding strap
Binds the faulty fiber patch cord after replacement.
Ethernet cable
Connects NEs or a LAN.
Optical spectrum analyzer
Displays the spectrum of an optical line.
Multimeter
Measures electrical parameters.
ESD wrist strap
Prevents electrostatic discharges from damaging

electrostatic-sensitive components.
ESD bag
Protects electrostatic-sensitive parts.
ESD cloth
Prevents electrostatic discharges from damaging

electrostatic-sensitive components.
Issue 01 (2011-08-10)
Page 28 of 95
Tool
Usage
Phillips screwdriver
Tightens or loosens screws on equipment.
Label paper
Identifies equipment or cables.
4.4 Emergency Handling Process

Take emergency measures when services are interrupted.
The emergency handling process is applied when services are interrupted. In addition to
following the emergency handling process, take other emergency measures, such as providing
standby trails, to minimize service interruption time.
Do not perform any operation before identifying the cause. Otherwise, any inappropriate
operation may cause more severe fault issues.
Issue 01 (2011-08-10)
Page 29 of 95
4.4.1 Emergency Handling Process for Rectifying Service

Interruption
Flowchart
Figure 4-2 Emergency handling process for rectifying service interruption
Start
A fault is reported
Yes
A misoperation is
performed?
Cancel the misoperation.

End
No
A backup resource is
available?
Switch the services to the

backup resource and
proceed to step 1
Yes
No
1
The NE is unreachable to the
NMS?
Yes
Yes
The power supply/optical
cable is faulty?
No
No
Determine the impact scope of the

service interruption based on the fault
symptom and reported alarms
Services on multiple
wavelengths are interrupted?
Check the SCC/OA/

MUX/DEMUX board
on site
Yes
Handle the
external fault
Locate the faulty point according to

the process for rectifying
interruption of services on multiple
wavelengths
No
The service on a single
wavelength is interrupted?
Yes
Locate the faulty point according

to the process for rectifying
interruption of the service on a
single wavelength
No
Services carried at the
electrical-layer ODUk are
interrupted?
Yes

interruption of the ODUk services
Yes

interruption of the GE, Any, or
other client-side services
No
Client-side services
are interrupted?
No
Replace the faulty
board/module

support engineers and work out
solutions together
No
Services are restored?

Yes
The fault is rectified.
End
Issue 01 (2011-08-10)
Page 30 of 95
Checking for Misoperation

Verify if a misoperation, such as a loopback or manual laser shutdown, is performed on
equipment before a fault occurred. If you determine it is the result of a misoperation, correct
it.
Restoring Services as Soon as Possible

When a fault occurs in the system, the services in the system are interrupted. If a backup
resource is available, switch the services to the backup resource to restore the services as soon
as possible before you handle the fault.
Identifying and Resolving External Faults

Before locating a fault in the system, remove possible external equipment faults. Possible
external equipment faults include faults of optical cables and fibers, faults of client equipment,
and power failures.
Removing a client equipment fault

To locate a client equipment fault, use any of the following methods:
Method 1: Connect a bit error meter between the Rx input port on the OTU/tributary
board at the local site and the Tx output port on the OTU/tributary board to perform a
bit error test. Use a fiber patch cord to loop the Tx output port of OTU/tributary board
(interconnected with the OTU/tributary at the local site) at the opposite site to the Rx
input port on the OTU/tributary board. If no bit error is detected, the client equipment
is faulty.
Method 2: If the OTU/tributary boards support the B1 error detection function,

compare and determine whether the RS-ES performance value of the OTU/tributary
board at the local site is the same as that of the OTU/tributary board at the opposite
site. If the two values are the same, no new bit error is generated in the system and
the system is operating properly. In this case, locate the fault on the client equipment.
Method 3: If a customer checks the client equipment, the customer can perform a
self-loop (add a proper optical attenuator before performing the self-loop) between
the transmit and receive optical ports on the client equipment and check for alarms on
the equipment. If alarms persist or the bit error meter still detects bit errors, the client
equipment is faulty.
Removing an optical cable fault

When the optical power decreases sharply, an alarm indicating loss of signals is reported
on a board. When this occurs, determine whether the board or optical cable is faulty. To
locate optical cable faults, use any of the following methods:
Issue 01 (2011-08-10)
Method 1: Measure the input optical power at the local site and the output optical
power at the upstream site. If the difference between the two values is less than the
design value, the optical cable is normal. If the difference is greater than the design
value, the optical cable is faulty.
Method 2: Verify optical cable parameters, such as the type and length, satisfy the
design requirements. If not, the optical cable is faulty.
Method 3: Switch the services to a backup fiber cable. If the alarm is removed, the
optical cable is faulty.
Method 4: Use an optical time domain reflectometer (OTDR) to measure the optical
power and determine whether the optical cable is faulty. If the reflectance of the
tested fiber core in the optical cable is less than 27 dB and the attenuation of this fiber
core is less than the designed value, the optical cable is normal. Otherwise, the optical
Page 31 of 95
cable is faulty. Note that the OTDR has a blind area that can produce inaccurate test
results.
When using the OTDR, separate the optical fiber from the equipment. Otherwise, intensive
light of the OTDR may damage the equipment.
Removing a power supply fault

If you cannot log in to a site and the downstream boards report alarms indicating loss of
input signals, the power supply of this site may be faulty. If this site starts working
abnormally, the optical power of this site suddenly decreases, some boards operate
abnormally, services are interrupted, or abnormal login occurs, check whether the power
supply voltage of the transmission equipment is excessively low or a transient low
voltage previously occurred.
Removing a grounding fault

If the equipment is struck by lightning or cannot be interconnected, check the following:
-verify the equipment grounding complies with the specifications; verify if any
equipment is isolated or not properly grounded and all equipment in the
telecommunications room are grounded using the same practices. You can also use a
meter to verify the grounding resistance and voltage difference between the working
ground and protection ground fall within the allowed ranges.
Determining Service Impact Scope

Fault locating and handling methods vary with the impact scope of service interruption.
Determine the fault impact scope based on the fault symptoms, and then locate and handle a
fault according to the scenario based on the fault impact scope. For details, see sections 4.7
through 4.10 .
Identifying and Resolving a Fiber or Board Fault

To identify a fiber or board fault, use any of the following methods:
Issue 01 (2011-08-10)
Method 1: Measure the input optical power of the board in alarm and the output optical
power of the corresponding board at the opposite site.
If the output optical power of the corresponding board at the opposite site is normal
and if the difference between the input optical power of the board at the local site and
the output optical power of the corresponding board at the opposite site is greater
than the design value, the fiber is faulty.
If the output optical power of the corresponding board at the opposite site is low, the
board is faulty or its input optical power is abnormal.
Method 2: Replace the fiber patch cord of the board whose optical power is abnormal
with a new fiber patch cord.
If the output optical power of the board is within the normal range after replacement,
the fiber is faulty.
If the output optical power of the board is still low after replacement, the board is
faulty.
Page 32 of 95
Analyzing Service Signal Flows

When a fault occurs, first analyze the service signal flow. Locating a fault in a WDM system
by performing site by site checks along a signal flow is a common method. With such a
method, you can quickly locate the point where the fault occurs.
Handling Abnormal Alarms

When a fault occurs in a system, it is generally accompanied with alarms and performance
events. Identify, handle, and clear the alarms reported on the NMS.
When multiple alarms are reported, handle these alarms according to the following principles:
Sort the critical and major alarms immediately based on the principles of "critical and
major alarms followed by minor alarms" and "alarms on line boards followed by alarms
on tributary boards".
Handle and clear alarms according to the following priorities (from high to low):
optical-layer LOS, electrical-layer OTU-LOF protection-related alarms, and board-level
alarms (BUS-ERR, EQPT-NSA, and COMM-FAIL).
If a LOS, LOS-MUT, IN-PWR-LOW, or IN-PWR-HIGH alarm is reported, handle the alarm

according to the sub-process for rectifying faults related to abnormal optical power. If an
alarm of another type is reported, such as an alarm indicating a board not inserted, abnormal
bias current, or abnormal cooling current, you can reset, reinstall, or replace the board.
For details on the alarm description and handling, see the Alarms and Performance Events
Reference.
In addition to the alarms and performance events reported on the NMS, you can also view the
alarm indicators and running status indicators on the equipment in the field to help locate a
fault. The on/off and blinking states of these indicators show the current running status or
possible alarms on the equipment. By viewing the indicators, you can predetermine the fault
cause and handle the fault accordingly. For a description of the indicators of cabinets,
subracks, and boards, see "Indicators" in the Hardware Description for the product.
When a fault occurs, take preliminary actions to locate the faulty point, such as analyzing the service
signal flow, alarms, performance events, and performance data.
Then measure the optical power section by section along the signal flow and analyze the optical
spectrum. Check whether any optical jumper or cable is faulty. If the optical jumpers or cables are good,
the board is faulty.
Finally, resolve the fault by resetting (warm or cold) the board, replacing it, or replacing the optical fiber
of the board.
Handling a Fault According to Experience

Sometimes, an operating board becomes abnormal because of a transient abnormal power
supply, low voltage, or strong external electromagnetic interference. When this occurs, service
communication interruption may be accompanied with alarms. If the configuration data of
each board is complete, experience has shown that in such a case, you can resolve the fault
and restore services by resetting or reinstalling the board, performing a restart on the single
site from a power failure or re-loading the configuration.
Issue 01 (2011-08-10)
Page 33 of 95
4.5 Sub-process for Rectifying Faults Related to Abnormal

Optical Power
Abnormal optical power may result in system bit errors or laser shut-down. Faults occur when
the optical power is excessively high or low. Generally, a LOS, LOS-MUT, IN-PWR-LOW,
IN-PWR-HIGH, OUT-PWR-HIGH or OUT-PWR-LOW alarm is reported.
When service interruption is accompanied with bit errors in the regenerator section (RS) or a
large amount of error corrections in the performance data, you can query the optical power
performance events of the OTU and optical amplifier boards, or measure the output and input
optical power by using the optical power meter. Then verify the optical power is within the
normal range of a board and determine if the fault is caused by a power failure on the opposite
NE or abnormal attenuation of the optical cable.
Compare the obtained data with the optical power data before the fault occurs to verify the current
optical power is normal. The data before the fault occurs can be the historical optical power performance
data or data in the regularly updated documentation.
If the equipment is faulty, you can locate the faulty point by performing a loopback (note the
attenuation change when performing the loopback). Then replace the faulty OTU or optical
amplifier board.
Issue 01 (2011-08-10)
Page 34 of 95
4.5.1 Flow Chart 1

Figure 4-3 Sub-process 1 for rectifying faults related to abnormal optical power
Handle a fault
related to abnormal
optical power
The LOS-MUT alarm is

reported or the LOS/LOF
alarm is reported on multiple
wavelengths?
Yes
Go to
subprocess 2
NMS of the
transmission
network
No
Measure the receive
optical power at the Rx
Yes port on the board by using Yes
an optical power meter.
Check whether the optical
power is normal.
An OTU board on a
wavelength reports the
LOS/LOF alarm on the
client side ?
Perform a loopback by
connecting the Tx port of the
OTU board to the Rx port through
an attenuator.The alarm is
cleared?
Rectify the fault in the

fiber between the the
client equipment OTU
and client equipment or
the fault on
No
No
No
Yes
Replace the
board
The OTU board reports the
IN-POWER-HIGH/INPOWER-LOW alarm on the
client side ?
Rectify the fault in the fiber

between the OTU and client
equipment or the fault on the
client equipment
Yes
No

IN-POWER-HIGH/INPOWER-LOW alarm on the
WDM side ?
Compare the optical power

changes on the demultiplexer
board and those on the OTU
board Determine that the intra site fibers are faulty?
Yes
No
Rectify the intra - site fiber

connection fault between the
demultiplexer board and the
OTU board
Yes
No
Replace the corresponding

OTU board
LOS/LOF alarm on the
WDM side ?
Yes
Measure the receive optical

power at the IN port on the
board by using an optical power
meter. The optical power is
normal?
Yes
Perform a loopback by
connecting the OUT port of the
OTU board to the IN port through
an attenuator.The alarm
is cleared?
No
Replace the corresponding

OTU board
Yes
No
Compare the optical power
changes on the multiplexer
board.those on the optical amplifier
board , and those on the OTU
board . Determine that the intra side fibers are faulty?
Yes
Rectify the intra - site fiber

connection fault according to
the signal flow
No
The settings , such as FEC
mode and service rate , on the
OTU are inconsistent with those
on the interconnected OUT?
Yes
Adjust settings, such as FEC

mode and service rate , on the
OTU board to ensure that the
settings are consistent with
those on the upstream OTU
board
No
support engineers and work
out solutions together
No
The fault related to

optical power is
removed?
Yes
End
Issue 01 (2011-08-10)
Page 35 of 95
4.5.2 Flow Chart 2

Figure 4-4 Sub-process 2 for rectifying faults related to abnormal optical power
Handle a fault related to
abnormal optical power
The LOS/LOF alarm is

reported only on a single
wavelengths?
Yes
Proceed to
subprocess 1
NMS of the
transmission
network
No
Yes
Cutover occurs on the

line?
Rectify the attenuation

fault caused by cutover
No

reported at site A?
No
Yes
Compare the current and
history input optical power performance
values for the optical amplifier board at
the receive end at station A.
The values are normal?
Yes

history output optical power performance
values for the optical amplifier board at
the receive end at station A.
No
Rectify the fault on the

optical amplifier board at
the receive end or the fault
related to fiber connections
at the TDC and RDC ports
on the OAU board
Yes
history input optical power performance
values for the demultiplexer board at
station A.
No
Yes
Rectify the fault related to

fiber on the demultiplexer
board or the fault related
to fiber connections
between the demultiplexer
board and the
corresponding OTU
boards
Rectify the fault related to

fiber connections between the
optical amplifier board and the
demultiplexer board

reported on the optical
amplifier board at the receive
end at site A?
Yes
The optical power

at the IN port on the
OSC board is normal?
Yes
Rectify the attenuation

fault in the fibers
connected to the optical
amplifer board at the site
Yes
No
The optical power

at the IN port on the FIU
board is normal?
Yes
Replace the FIU board
No
The optical power at the
OUT port on the FIU
board at the upstream
site B according to the
signal flow
Yes
Rectify the fault related

to the line ODF and
attenation of the optical
cable
No
Rectify the fault related to optical
power at site B according to the
signal flow and the reported
performance events

reported on the
demultiplexer board at
site A?
Proceed to 1
Contact Huawei
technical support
engineers and work out
solutions together
Yes
Proceed
to
No
No
The fault related to

optical power is
removed?
Yes
End
Issue 01 (2011-08-10)
Page 36 of 95
4.5.3 Process Description
If the LOS-MUT alarm and the LOS alarm are reported on multiple boards, a fault
occurs on multiple wavelengths. In this case, identify the fault in the multiplexed signals.
If only one board reports the LOS, IN-PWR-LOW, or IN-PWR-HIGH alarm, a fault
occurs on a single wavelength. In this case, identify the fault within a single site.
You can identify the specific board reporting the alarm on the NMS. If the LOS-MUT
alarm is reported, then all services are interrupted. When this occurs, test the input
optical power of the optical amplifier board, demultiplexer board, and FIU board at the
site. If the input optical power of the FIU board is abnormal, identify the fault in
interconnection between the board and the ODF or the optical cable. If the input optical
power of the FIU board functions properly, identify the fault in the intra-site fibers.
You can identify the specific board reporting the alarm on the NMS. If the LOS or LOF
alarm is reported, then the service is interrupted. When this occurs, test the input optical
power at the corresponding port. If the optical power is abnormal, identify the fault in the
fiber connected to the port. If the optical power is normal, perform a physical fiber
loopback on the port by adding an attenuator of 10 dB. Then, verify the alarm is cleared.
If the alarm is cleared, the board at the local end is normal and you can identify the fault
on the upstream equipment. If the alarm persists, the board at the local end may be
damaged and you need to replace the board.
When an OTU board that a wavelength traverses reports the LOS or LOF alarm, the
upstream or downstream board that the wavelength traverses reports the LOF alarm.
For details on the alarm signal flows, see "Alarm Signal Flow" in the Alarms and
Performance Events Reference.
When a board reports a LOF alarm, verify the input optical power of the board is
excessively high or low. If the optical power is normal, verify the settings on the
board, such as FEC mode and service rate, are consistent with the interconnected
board.
When an OTU board that a wavelength traverses reports the IN-PWR-LOW or

IN-PWR-HIGH alarm, bit errors and pre-FEC bit errors are generally accompanied.
However, the service is usually not interrupted. In this case, you can query the input
optical power threshold of the OTU board.
Run the following command to query the input optical power threshold:
RTRV-ALMTH-<MOD2>:[<TID>]:<AID>:<CTAG>[:::ALMTHTYPE=<ALMTHTYPE>];
<MOD2>: WDM, OC, OCH, OSC, PL
<AID>: Indicates the access ID. The format is FAC-<SHELF>-<SLOT>-<PORT>.
<ALMTHTYPE>: Indicates the type of the alarm threshold.
OPR: input optical power (unit: 1 dBm)
OPT: output optical power (unit: 1 dBm).
Query the current input optical power of the local OTU board, the current output optical power of the
upstream OTU board, and their 15-minute/24-hour performance values. By comparing these values, you
can identify the fault within the site
4.6 Sub-process for Rectifying Faults Related to Bit Errors

The bit error faults are handled according to the sequence of the boards along the signal flow.
Bit errors are associated with optical power, fiber nonlinearity, abnormal reflection of the fiber,
and faults on optical boards (such as the wavelength conversion board and optical amplifier
board). If bit errors are generated on a single wavelength, the bit errors are irrelevant to the
Issue 01 (2011-08-10)
Page 37 of 95
line where the multiplexed signals traverse. Similarly, if bit errors are generated on all
wavelengths, the bit errors are irrelevant to a single wavelength. When bit errors are generated
on a single wavelength, locate the fault through replacement. If the optical power and OSNR
are at the critical points of the system, faults may occur on certain wavelengths.
NOTE
The OTU board used on WDM equipment supports detection of B1 bit errors as follows: The board
calculates B1 bit errors in signals whose wavelength needs to be converted and displays the result
through the RS-BBE performance item.
Issue 01 (2011-08-10)
Page 38 of 95
4.6.1 Flow Chart

Figure 4-5 Sub-process for rectifying faults related to bit errors
Start handling bit errors
NMS of the transmission network
Cutover is performed on
the line ?
The fault
occurs after
the cutover ?
Yes
Yes
Clean
the fiber patch cords
involved in the cutover Rectify the
connection of fiber jumpers and
possible fiber adapter faults . After
that , bit errors disappear ?
Yes
No
No
No
Check whether the fiber length and types
after the cutover are consistent with those
before the cutover . Handle problems of
under - compensation of dispersion .
Bit errors are

generated on a single
wavelength ?
Check whether the TF,

LCC-HIGH, or LSR-EOL alarm is
reported on the OTU on the
wavelength ?
Yes
No
Yes
Replace the OTU that

reports the alarms .
No
Alarms indicating optical

power abnormity are reported
on multiple wavelengths ?
Rectify abnormal optical power

according to the Rectifying Optical
Power Abnormity Flow 1 .
Yes
Rectify abnormal optical power

according to
Rectifying Optical
Power Abnormity Flow 2.
No
The fault is not caused by
nonlinearity of the fiber ?
Increase the input optical power of the

amplifier at the transmit end by 3 dB.
No
Yes
No
Along the
reverse signal flow
direction , find the first station
where bit errors are generated .
OSNR of each wavelength is normal
through the MON port on the
amplifier board at the receive
end ?
No
Bit errors
increase ?
Compare
the current and history
performance values of the input optical
power of the amplifier . The difference
is in normal range ?
Yes
Yes
Bit errors result from fiber

nonlinearity . In this case , locate
the fiber nonlinearity by
segment . Configure an
attenuator before the
associated fiber to ensure that
single - wavelength incident
power is lower than + 5 dBm.
No
Rectify optical power

abnormity according to
Rectifying Optical Power
Abnormity Flow 2.
Yes
Replace this amplifier .
The customer checks whether
line fiber deteriorates or abnormal
reflection occurs on the fiber .
Assist customers to handle

problems associated with line
fiber .

support engineers for support
and co - work out solutions to
resolve the problem .
No
Bit errors are

rectified ?
Yes
The fault is rectified .
End
4.6.2 Process Description
Issue 01 (2011-08-10)
Rectifying a bit error fault associated with a cutover
Page 39 of 95
If bit errors are generated after a line cutover, resolve the bit error fault associated with
the cutover.
If services on a line are migrated to another optical cable, items such as fiber types,
length, and configurations for the DCM module may result in over-compensation or
under-compensation of dispersion. Dispersion itself, however, does not result in OSNR
changes. The dispersion fault is generally caused by incorrect configuration of the DCM
type. For example, a 100 km DCM module is used where a 20 km DCM module is
required, or a G.652 fiber is used where a G.655 fiber is required. Another cause of the
dispersion fault is the configuration of incorrect directions of the DCM modules. For
example, DCM modules in the east and west directions are configured in reverse. If the
previous causes are excluded and the bit error fault persists, a possible reason may be
that the dispersion of the customer fiber is inconsistent with the dispersion in the design
file.
The 2.5G OTU board has high dispersion tolerance. Therefore, no dispersion
compensation is required for transmission over 640 km without using an electrical
regenerator.
When a 2.5G OTU board works with a 10G OTU board, because dispersion tolerance
of the 10G OTU board is far lower than the 2.5G OTU board, impacts caused by
dispersion must be considered when expanding 10G services on a network with
single-wavelength rate at 2.5 Gbit/s.
Rectifying a bit error fault associated with optical power

If changes in the input or output optical power of the OTU board exceed the normal
range, bit errors may be associated with optical power. In this case, handle the fault
according to the sub-process for rectifying faults related to abnormal optical power. In
fact, most of bit error faults result from abnormal optical power. Once bit errors are
generated on a network, query the optical power performance of the relevant channel
before handling the fault.
Rectifying a bit error fault associated with fiber nonlinearity

The possibility of bit errors caused by fiber nonlinearity is unlikely. Therefore, ignore
this possibility during the fault rectification. If the fiber nonlinearity is severe, bit errors
are generated on each channel randomly. In this case, locate the nonlinearity fault by
increasing and decreasing optical power at the transmit end. If the bit errors at the
receive end increase or decrease with the increasing or decreasing of the optical power at
the transmit end, the fault is caused by the nonlinearity issue. In this case, handle the
fault by decreasing the optical power at the transmit end.
Rectifying a bit error fault associated with abnormal alarms

If the OTU board on the channel where bit errors are generated reports an alarm, such as
LSR-EOL, or LCC-HIGH, replace the OTU board.
Issue 01 (2011-08-10)
Additional information on bit error fault locating
If bit errors are generated at the client-side port on the OTU board but not on the
WDM-side port on the OTU board, perform a client-side facility loopback and verify
bit errors disappear. If bit errors persist, the fault is associated with the OTU board. In
this case, replace the OTU board. If bit errors disappear, replace the fiber between the
OTU board and client equipment. If bit errors disappear after the fiber is replaced, the
fault is caused by the inner faults of the fiber. If bit errors persist, locate the fault to
the client equipment.
If bit errors are generated on both the WDM-side equipment and client equipment,
find the OTU board where bit errors are first generated. Assume the OTU board is
located at site A. Verify the input and output optical power of the OTU board are
within the normal range. If they are abnormal, check the line attenuation between the
Page 40 of 95
OTU board and client equipment. If the input and output optical power of the OTU
board within the normal range, locate the faults to the client equipment.
If the OTU board on the channel where bit errors are generated is a regeneration
board at site A, interchange the two OTU boards for both two directions of the
channel at site A. After the two OTU boards are interchanged, if the direction of bit
errors is reversed, the OTU board where bit errors are generated is faulty. In this case,
replace the faulty OTU board. If the direction of bit errors is the same, replace the
OTU board on the channel at the upstream site.
If the bit errors persist after the OTU board where bit errors are generated is replaced,
the fault is caused by the line fiber. In this case, ask the customer to test the line by
using an OTDR. Verify if the fiber deteriorates or abnormal reflection occurs on the
fiber, and rectify the fault accordingly.
If the bit error fault persists, contact Huawei technical support engineers.
4.7 Fault Locating by Performing Loopbacks

Performing a loopback is the most common and effective method for locating a fault. The
most significant feature of this method is that it does not require thorough analysis on alarms
and performance data. Equipment maintenance personnel must be familiar with this method.
Loopbacks are classified into software loopbacks and hardware loopbacks. Software
loopbacks are further classified into facility loopbacks and terminal loopbacks. For more
information about the definition and operations of loopbacks, see the Supporting Tasks.
Once a service interruption occurs, the loopback method helps fault locating and rectification.
This section describes fault locating by using the loopback method based on the following
two fault scenarios.
Issue 01 (2011-08-10)
Page 41 of 95
Scenario 1: Tributary and Lines Boards Are Interconnected at the Sites on Two
Ends
Figure 4-6 Loopback diagram when tributary and line boards are interconnected at the sites on
two ends
Station A
Client
equipment
Tributary
board
8 7
Station B
Crossconnect
board
6
5 4
3
Fiber hardware loopback
X: Loopback No.
X Board software loopback

configured on the NMS
X:Loopback No.
Crossconnect
board
Line
board
Line
board
3
2
Tributary
board
2
Client
equipment
1
Detection point No.

Upstream services
(Services from station A to station B)
Downstream services
(Services from station B to station A)
In this scenario, perform loopbacks based on the following main principle: Perform loopbacks
starting from the client-side port on the tributary board at site B in the receive direction.
Check for alarms at each detection point along the service flow direction. According to the
position and sequence that alarms are reported, perform loopbacks to locate the fault.
Detection point 1: Alarms are reported at the client-side port on the tributary board at site
B. Perform a loopback using the following procedure:
Step 1 Perform a loopback on the client equipment at site B by using a fiber (loopback 1 as shown in
the preceding diagram). If the client equipment receives abnormal services after the loopback,
the client equipment is faulty; otherwise, proceed to the next step.
Step 2 Configure a terminal loopback at the client-side port on the tributary board at site B (loopback
2 as shown in the preceding diagram). If the client equipment receives abnormal services after
the loopback, verify the client-side optical module on the tributary board at site B is pluggable.
If the module is pluggable, replace the client-side optical module. If the client equipment still
receives abnormal services after the module is replaced, then replace the tributary board at site
B. If the module is fixed and not pluggable, replace the tributary board at site B.
----End
Detection point 2: The BUS-ERR alarm is reported at the port (near the cross-connect
board) of the line board at site B. In this case, perform a loopback as follows:
Step 1 Configure a loopback of services from the cross-connect board to the tributary board at site B
(loopback 3 as shown in the preceding diagram). If upstream services are running normally
after the loopback, the tributary board at site B is faulty. In this case, replace the faulty board.
If the upstream services are still running abnormally after the loopback, proceed to the next
step.
Issue 01 (2011-08-10)
Page 42 of 95
Step 2 Perform switching between active and standby cross-connect boards at site B if there is a
standby cross-connect board. If the upstream services are running normally after switching,
the active cross-connect board is faulty. In this case, replace the faulty cross-connect board. If
the upstream services are still running abnormally, the tributary board at site B is faulty. In
this case, replace the faulty tributary board.
NOTE
Switching active and standby cross-connect boards can only restore the interrupted services, but not
clear the BUS-ERR alarm.
In addition, it may interrupt services that are running normally on the boards. Exercise caution when you
perform this operation.
----End
Detection point 3: Alarms are reported at the WDM-side port on the line board at site A.
In this case, perform a loopback as follows:
Step 1 Verify if any similar alarm is reported at the WDM-side ports of the service boards that are
involved in the same line. If a similar alarm is reported, the line is faulty. In this case, rectify
the faulty line before clearing the alarm. If no similar alarm is reported on the service board in
the line, proceed to the next step.
Step 2 Perform a hardware loopback at the client-side port on the line board at site B by using a fiber
(loopback 5 as shown in the preceding diagram). If the upstream services are running
normally and the faulty line is rectified after the loopback, the line board at site A is faulty. If
the optical module at the WDM-side port on the faulty line board is pluggable, replace the
module to check if it is faulty. If services are not restored after the module is replaced, replace
the line board at site A. If services are not restored after the line board at site A is replaced,
proceed to the next step.
Step 3 Configure a facility loopback at the WDM-side port on the line board at site B (loopback 4 as
shown in the preceding diagram). If the upstream services are still running abnormally after
the facility loopback, the line board at site B is faulty. If the WDM-side optical module on the
line board at site B is pluggable, replace the module. If the upstream services are not restored
after the optical module is replaced, then replace the line board at site B. If the module is
fixed to the line board, replace the line board at site B.
----End
Detection point 4: The ODU-LOF/ODU-LOM alarm is reported at the port

(cross-connect side) of the tributary board at site A. In this case, perform a loopback as
follows:
Step 1 Configure a loopback of services from the cross-connect board to the line board at site A
normally after the loopback, the tributary board at site A is faulty. In this case, replace the
faulty board. If the upstream services are still running abnormally after the loopback, proceed
to the next step.
Step 2 Perform a hardware loopback on the line board at site B by using a fiber (loopback 5 as
shown in the preceding diagram). If the upstream services are running normally and the faulty
line is rectified after the loopback, the line board at site A is faulty. If the WDM-side optical
module on the line board at site A is pluggable, replace the module. If the upstream services
are still running abnormally after the module is replaced, then replace the line board at site A.
If the upstream services are running normally after the board is replaced, proceed to the next
step.
Issue 01 (2011-08-10)
Page 43 of 95
the loopback, the line board at site B is faulty. If the WDM-side optical module on the line
board at site B is pluggable, replace the module. If the upstream services are not restored after
the module is replaced, then replace the line board at site B. If the module is fixed to the line
board, replace the line board at site B.
----End
Detection point 4: The BUS-ERR alarm is reported at the port (near the cross-connect
board) of the tributary board at site A. In this case, perform a loopback as follows:
normally after the loopback, the tributary board at site A is faulty. In this case, replace the
faulty board. If the upstream services are still running abnormally after the loopback, proceed
to the next step.
Step 2 Perform switching between active and standby cross-connect boards at site A if there is a
standby cross-connect board. If the upstream services are running normally after switching,
the cross-connect board (the active cross-connect board before switching) is faulty. In this
case, replace the faulty cross-connect board. If the upstream services are still running
abnormally after switching, the line board at site A is faulty. In this case, replace the faulty
line board at site A.
NOTE
Switching of active standby cross-connect boards can only restore the interrupted services. Switching
cannot clear the BUS-ERR alarm.
Switching may interrupt services that are running normally on the boards. Exercise caution when you
perform this operation.
----End
Detection point 4: Alarms (other than the BUS-ERR, ODU-LOF, ODU-LOM alarms) are
reported at the XCS-side port on the tributary board at site A. In this case, perform a
loopback as follows:
(loopback 6 as shown in the preceding diagram). If the upstream services are restored after the
loopback, the tributary board at site A is faulty. In this case, replace the faulty board. If the
upstream services are still running abnormally after the loopback, proceed to the next step.
Step 2 Configure a loopback of services from the cross-connect board to the tributary board at site B
(loopback 3 as shown in the preceding diagram). If the upstream services are still running
abnormally after the loopback, the tributary board at site B is faulty. In this case, replace the
faulty board. If the upstream services are restored after the loopback, proceed to the next step.
Step 3 Perform a hardware loopback on the line board at site B by using a fiber (loopback 5 as
shown in the preceding diagram). If the upstream services are running normally after the
loopback and the line fault is rectified, it indicates that the line board at site A is faulty. If the
WDM-side optical module on the line board at site A is pluggable, replace the module. If the
upstream services are still running abnormally after the module is replaced, then replace the
line board at site A. If the upstream services are running normally after the board is replaced,
Issue 01 (2011-08-10)
Page 44 of 95
the loopback, the line board at site B is faulty. If the WDM-side optical module on the line
board at site B is pluggable, replace the module. If the upstream services are still running
abnormally after the module is replaced, then replace the line board at site B. If the module is
fixed to the line board, replace the line board at site B.
----End
Detection point 5: Services are running abnormally on the client equipment at site A. In
this case, perform a loopback as follows:
Step 1 Perform a hardware loopback at the client-side port on the tributary board at site A by using a
fiber (loopback 8 as shown in the preceding diagram). If the upstream services are restored
after the loopback, the client equipment at site A is faulty. If the upstream services are still
running abnormally after the loopback, proceed to the next step.
Step 2 Configure a facility loopback at the client-side port on the tributary board at site A (loopback
7 as shown in the preceding diagram). If the upstream services are not restored after the
loopback, the tributary board at site A is faulty. If the WDM-side optical module on the
tributary board at site A is pluggable, replace the module. If the upstream services are not
restored after the module is replaced, then replace the tributary board at site A. If the module
is fixed to the tributary board, replace the board. If the module is fixed, replace the tributary
board at site A.
WARNING
When performing a loopback on a board by using a fiber, ensure that the incident optical
power of the board is within the normal range.
Before replacing a board, you can perform a cold reset on the board.
For upstream service faults (from site A to site B), locate the faults in the same way.
----End
Issue 01 (2011-08-10)
Page 45 of 95
Scenario 2: Tributary-Line Boards Are Interconnected at the Sites at the Ends

Figure 4-7 Loopback diagram when two tributary-line boards are interconnected at the sites at the
ends
Station A
Station B
Tributaryline board
Tributaryline board
Client
equipment
Client
equipment
6
3
4
2
Fiber hardware loopback
X: Loopback No.
X Board software loopback

configured on the NMS
X:Loopback No.
Detection point No.

Upstream services
(Services from station A to station B)
Downstream services
(Services from station B to station A)
In this scenario, perform loopbacks based on the following main principle: Perform loopbacks
starting from the client-side port on the board at site B in the receive direction. Check for
alarms at each detection point along the service flow direction. Detection point 1: Alarms are
reported at the client-side port on the board at site B. In this case, perform a loopback as
follows:
Step 1 Perform a hardware loopback on the board at site B by using a fiber (loopback 1 as shown in
the preceding diagram). If the client equipment receives abnormal services after the loopback,
the client equipment is faulty. If the client equipment receives normal services after the
loopback, go to the next step.
Step 2 Configure a terminal loopback at the client-side port on the board at site B (loopback 2 as
shown in the preceding diagram). If the client equipment receives abnormal services after the
loopback, the board at site B is faulty. If the client-side optical module on the board at site B
is pluggable, replace the module. If the client equipment still receives abnormal services after
the module is replaced, then replace the OTU board at site B. If the client-side optical module
is fixed and not pluggable, replace the OTU board at site B.
----End
Detection point 2: Alarms are reported at the WDM-side port on the board at site A. In
Step 1 On the line where the board is located, check whether any similar alarm is reported at the
WDM-side ports of service boards. If there is a similar alarm reported at the WDM-side port
of a service board in the line, the line is faulty. In this case, remove the line fault before
resolving the problem associated with the alarms. If there is no other similar alarm reported
on service boards in the line, go the next step.
Issue 01 (2011-08-10)
Page 46 of 95
Step 2 Perform a hardware loopback at the client-side port on the board at site B by using a fiber
normally after the loopback and the line fault is rectified, the OTU board at site A is faulty. If
the WDM-side optical module on the OTU board is pluggable, replace the module. If the
upstream services are not restored after the module is replaced, then replace the OTU board at
site A. If services are not restored after the OTU board at site A is replaced, proceed to the
next step.
Step 3 Configure a facility loopback at the WDM-side port on the board at site B (loopback 3 as
the loopback, the board at site B is faulty. If the WDM-side optical module on the board at
site B is pluggable, replace the module. If the upstream services are still running abnormally
after the module is replaced, then replace the board at site B. If the module is fixed to the
board, replace the board at site B.
----End
Detection point 3: Services are running abnormally on the client equipment at site A. In
Step 1 Perform a hardware loopback at the client-side port on the board at site A by using a fiber
(loopback 6 as shown in the preceding diagram). If the upstream services are restored after the
loopback, it indicates that the client equipment at site A is faulty. If the upstream services are
still running abnormally after the loopback, proceed to the next step.
Step 2 Configure a facility loopback at the client-side port on the board at site A (loopback 5 as
shown in the preceding diagram). If the upstream services are not restored after the loopback,
board at site A is faulty. If the WDM-side optical module on the board is pluggable, replace
the module. If the upstream services are not restored after the module is replaced, then replace
the board at site A. If the module is fixed and not pluggable, replace the board at site A.
WARNING
1. When performing a loopback on a board by using a fiber, ensure that the incident optical
power of the board is within the normal range.
2. Before replacing a board, you can perform a cold reset on the board.
3. For faults of the upstream services (from site A to site B), locate the faults in the same way.
----End
4.8 Rectifying Interruption of Client-Side Services

4.8.1 Rectifying Interruption of Services Without Protection
Fault Scenario
If client-side services are interrupted, the following alarms may be reported at the client-side
port on the local or opposite board.
Issue 01 (2011-08-10)
Page 47 of 95
In a GE service scenario, the following alarms may be reported:
Client-side port on the local board: the LOS alarm
Client-side port on the opposite board: the REMC-SF alarm
Client-side port: the LINK-ERR alarm
Client-side port: the CV-ETH alarm
Client-side port: the LOSYNC alarm
In a 10GE-LAN service scenario, the following alarms may be reported:
Client-side port on the board (such as the TN12LSX board) configured with 10GE
services in the flow control mode: the LOCAL-FAULT alarm or REMOTE-FAULT
alarm
In a 10GE-WAN or STM64 or 0C-192 or STM256 service scenario, the following alarms

may be reported:
Client-side port: the LOF alarm
In an FC1200 service scenario, the following alarms may be reported:
Client-side port: the LOSYNC alarm
In an Any service scenario, the following alarms may be reported:
Client-side port: the RATE-OVER alarm
No alarm reported upon service interruption
Impact Scope and Severity

Client-side services are interrupted.
Cause Analysis and Restoration Measures

When alarms are reported at the client-side port, clear the alarms based on the service signal
flow by referring to the Alarms and Performance Events Reference.
If services are still interrupted after the alarms are cleared or no alarm is reported at the
client-side port, rectify the fault using the following procedure:
Step 1 Check the alarm downgrade settings of the board or NE. If the alarms are downgraded, cancel
the downgrade and then handle the alarms.
Step 2 If the fault persists, contact Huawei technical support engineers.
----End
Issue 01 (2011-08-10)
Page 48 of 95
4.8.2 Rectifying Interruption of Services with Protection

Fault Scenario
Client-side services on WDM equipment are interrupted. These services are under protection,
which may be the client-side 1+1 or SW SNCP protection.

Client-side services are interrupted.

Step 1 Check if configurations of the working and protection channels at the two ends are consistent.
If the configurations are inconsistent, modify them. If the services are not restored, proceed to
the next step.
Step 2 Check the protection group status and determine if services on the working or protection
channel in the protection group are forced to or are locked on the abnormal channel. If
services on the working or protection channel in the protection group are forced to or are
locked on the abnormal channel, cancel the forced or locked switching and check if the
services are restored. If the services are not restored, proceed to the next step.
Step 3 Check the protection group status. If the working or protection channel in the protection group
is a normal channel, forcibly switch the services in the protection group at the two ends over
to the normal working or protection channel and check if the services are restored. If the
services are not restored, proceed to the next step.
Step 4 Forcibly switch the services in the protection group at the two ends over to the working
channel and check if the services are restored. If the services are not restored, proceed to the
next step.
Step 5 Forcibly switch the services in the protection group at the two ends over to the protection
next step.
Step 6 If the services still cannot be restored after the preceding steps are performed, forcibly switch
the services in the protection group at the two ends over to the working channel by referring
to methods for restoring services without protection.
Step 7 After the services are temporarily restored, contact Huawei technical support engineers to
identify and rectify the fault.
----End
Issue 01 (2011-08-10)
Page 49 of 95
4.9 Rectifying Interruption of the Service on a

Subwavelength (ODUk)
Fault Scenario
When services carried by ODUk on the line are interrupted, the following alarms may be
reported at the WDM-side port on the local or opposite board.
Local board: the LOS, OTU-LOF, OTU-LOM, ODU-LOFLOM, ODU-AIS, ODU-OCI

or ODU-LCK alarm
Opposite board: the OTU-BDI or ODU-BDI alarm

Services carried by ODUk on the line are interrupted.

When alarms are reported at the WDM-side port, clear the alarms based on the service signal
flow by referring to the Alarms and Performance Events Reference.
client-side port, rectify the fault using the following procedure:
Step 1 Check the alarm downgrade settings of the board or NE. If the alarms are downgraded, cancel
the downgrade and then handle the alarms.
Step 2 If the alarms cannot be cleared, identify the fault by referring to 4.7 "Fault Locating by
Performing Loopbacks."
Step 3 If the fault still cannot be rectified after the preceding steps are performed, contact Huawei
technical support engineers.
----End

Fault Scenario
Services, configured with ODUk SNCP protection and carried by ODUk on the line, are
interrupted.

Services carried by ODUk on the line are interrupted.
Issue 01 (2011-08-10)
Page 50 of 95

If the configurations are inconsistent, modify them. If services are not restored after
modification, proceed to the next step.
Step 3 Check the protection group status. If the working or protection channel is normal, forcibly
switch the services in the protection group at the two ends over to the normal working or
protection channel to check if the services are restored. If the services are not restored,
next step.
next step.
Step 6 If services still cannot be restored, forcibly switch the services in the protection group at the
two ends over to the working channel and then restore the services on the working channel by
referring to methods for restoring services without protection.
----End
4.10 Rectifying Interruption of the Service on a Single

Wavelength
Fault Scenario
If services on a single wavelength are interrupted, the following alarms may be reported at the
WDM-side port on the local or opposite board.
The following alarms may be reported at the WDM-side port on the local or opposite board:
The LOS or OTU-LOF alarm
The OTU-LOF, OTU-LOM, or OTU-DEG alarm
The ODU-OCI or ODU-DEG alarm
The IN-PWR-HIGH or IN-PWR-LOW alarm
No alarm may be reported when services on a single wavelength are interrupted.
Issue 01 (2011-08-10)
Page 51 of 95

Services carried by a single wavelength are interrupted.

If alarms are reported at the WDM-side port, remove emergent alarms that affect services
based on the service signal flow by referring to the Alarms and Performance Events
Reference.
WDM-side port, rectify the fault using the following procedure:
Step 1 Check the alarm masking settings for boards or NEs. If the above mentioned alarms are
masked, cancel alarm masking and clear the alarms.
Step 2 Query the current performance and 15-minute/24-hour historical performance of the OTU
board at the receive end by running commands or by using the NMS. Check if the optical
power of the single wavelength at the receive end is normal.
Step 3 If the optical power of the single wavelength at the receive end is abnormal, query the current
performance and the 15m/24h historical performance of the OTU board at the transmit end.
Check if the optical power of the single wavelength at the transmit end is normal.
Step 4 If the optical power at the receive or transmit end is abnormal, rectify the abnormal optical
power by referring to 4.5 "Sub-process for Rectifying Faults Related to Abnormal Optical
Power."
Step 5 If services are still interrupted, check the configuration parameters of the OTU boards at the
local and opposite ends. If the configuration parameters are inconsistent, re-configure the
configuration parameters.
1.
Verify FEC types on the OTU board at the two ends are consistent. Verify the FEC
self-sensing function is enabled on the OTU board that supports FEC self-sensing. The
OTU board can be the TN12ND2 or TN52ND2 board.
2.
For the OTU board that supports the settings of the OTN line rates, verify the line rates
at the two ends match.
3.
For the board that supports the settings of service modes at ports, verify service modes at
the two ends match. The board can be the ND2 or NQ2 board.
4.
For a 40G board, verify the receive wavelength is consistent with the transmit
wavelength.
5.
For an L4G board, verify the working modes on the line side of the board at the two ends
are consistent.
6.
If services are still not restored, proceed to the next step.
Step 6 If alarms cannot be cleared and services are still interrupted, locate the fault point by referring
to 4.7 "Fault Locating by Performing Loopbacks."
Step 7 If the fault still cannot be rectified after the preceding steps are performed, contact Huawei
technical support engineers.
----End
Issue 01 (2011-08-10)
Page 52 of 95

Fault Scenario
Services, configured with intra-board 1+1 protection and carried on a single wavelength, are
interrupted.

Services carried by a single wavelength are interrupted.

If the configurations are inconsistent, modify them. If services are not restored after
modification, proceed to the next step.
Step 3 Check the protection group status. If the working or protection channel is normal, forcibly
switch the services in the protection group at the two ends over to the normal working or
protection channel to check if the services are restored. If the services are not restored,
next step.
next step.
Step 6 If services still cannot be restored, forcibly switch the services in the protection group at the
two ends over to the working channel and then restore the services on the working channel by
referring to methods for restoring services without protection.
----End
4.11 Rectifying Interruption of Services on Multiple

Wavelengths
Interruption of services on multiple wavelengths includes interruption of services on some
wavelengths and interruption of services on all wavelengths.
Issue 01 (2011-08-10)
Page 53 of 95

Fault Scenario
If services on multiple wavelengths are interrupted, the following alarms may be reported on
the board.
Optical amplifier board: the LOS-MUT, SUM-INPWR-HIGH, SUM-INPWR-LOW,

PRE-INPWR-HIGH, PRE-INPWR-LOW alarm
OTU board with multiple wavelengths: the LOS, OTU-LOF, IN-PWR-LOW, or

IN-PWR-HIGH alarm
Optical supervisory channel board: the LOS alarm
D40 or D40V board: the LOS-MUT, SUM-INPWR-HIGH, SUM-INPWR-LOW alarm
FIU board: the LOS-MUT alarm

Services on multiple wavelengths are interrupted.
Check the boards along the reverse signal flow direction
As shown in the preceding figure, check each board along the reverse signal flow direction
using the following procedure to identify the faulty boards or faulty lines.
Step 1 If the LOS, IN-PWR-HIGH, or IN-PWR-LOW alarm is reported on multiple OTU boards, the
input optical power performance value and historical performance value change. Check if the
input optical power of the demultiplexer board before the OTU board changes, compared with
the historical performance value. If the input optical power of the demultiplexer board does
not change, check the fiber patch cord between the demultiplexer board and the OTU board. If
the fiber patch cord is abnormal, replace it. If the fiber patch cord is normal, the demultiplexer
board is faulty and needs to be replaced. If the demultiplexer board functions properly,
Step 2 Check if the input optical power of the demultiplexer board changes. If it changes, check if
the input and output optical power of the upstream optical amplifier boards changes. If the
output optical power of the optical amplifier boards is stable, remove or replace the fiber
patch cords between the optical amplifier board and the demultiplexer board. If the output
Issue 01 (2011-08-10)
Page 54 of 95
optical power of the optical amplifier board changes but the input optical power is stable,
check if gain is set on the optical amplifier board and if the laser is shut down. If the optical
amplifier board is an OAU board, also check if insertion loss between the TDC and RDC
ports changes. If no exception is found, the optical amplifier board is faulty and needs to be
replaced. If the optical amplifier board functions properly, proceed to the next step.
Step 3 Check if the input optical power of the optical amplifier board changes. If it changes, check if
the input and output optical power of the FIU board changes. If the output optical power of
the FIU board is stable, remove or replace the fiber patch cords between the optical amplifier
board and the FIU board. If the output optical power of the FIU board changes, check the
input optical power of the FIU board. If it is stable, the FIU board is faulty and needs to be
replaced. If the FIU board functions properly, proceed to the next step.
Step 4 Check if the input optical power of the FIU board changes. If it changes, check if the output
optical power of the upstream FIU boards changes. If the output optical power of the
upstream FIU boards is stable, check if the line attenuation between the two FIU boards
changes. If the line attenuation between the two FIU boards does not change, proceed to the
next step.
Step 5 If the output optical power of the upstream FIU boards changes, continue to check the
upstream sites by referring to the preceding steps. When checking the upstream sites, you
need to comply with the following principles:
Check the reported power of the FIU board, optical amplifier board, and multiplexer
board along the reverse signal flow direction.
Locate the specific point where the optical power changes according to the optical power
change point.
If the optical power change is caused by a board, replace the board. If a fiber patch cord
is faulty, remove or replace it.
Step 6 If an attenuation board is configured on the line, check if the attenuation board is set. If the
actual attenuation of the attenuation board is inconsistent with the set value, replace the
attenuation board. If the fault still cannot be rectified after the preceding steps are performed,
contact Huawei technical support engineers.
----End

Fault Scenario
If services configured with optical line 1+1 protection and carried on multiple wavelengths
are interrupted, the following alarms may be reported on the board.
Optical amplifier board: the LOS-MUT, SUM-INPWR-HIGH, SUM-INPWR-LOW,

PRE-INPWR-HIGH, PRE-INPWR-LOW alarm
OTU board with multiple wavelengths: the LOS, OTU-LOF, IN-PWR-LOW, or

IN-PWR-HIGH alarm
Optical supervisory channel board: the LOS alarm
D40 or D40V board: the LOS-MUT, SUM-INPWR-HIGH, SUM-INPWR-LOW alarm
FIU board: the LOS-MUT alarm
OLP board: the LOS-MUT or OPR-DIFF-OVER alarm
Issue 01 (2011-08-10)
Page 55 of 95

Services on multiple wavelengths are interrupted.

Usually, the fact that the working and protection channels are interrupted simultaneously
results in the interruption of services (with protection) on multiple wavelengths. In this case,
restore services using the following procedure:
channel in the protection group are on the normal channel. If services on the working or
protection channel in the protection group are on the normal channel, forcibly switch services
over to the normal channel and check if the services are restored. If the services are not
restored, proceed to the next step.
Step 2 Forcibly switch the services in the protection group at the receive end over to the working
next step.
Step 3 Forcibly switch the services in the protection group at the receive end over to the protection
next step.
Step 4 If services still are not restored, forcibly switch the services in the protection group at the
receive end over to the working channel by referring to methods for restoring services without
protection.
NOTE
Before identifying the power change point, check the input optical power of the OLP board. If the input
optical power of the OLP board does not change while the output optical power changes, replace the
OLP board.
----End
4.12 Manually Restoring Services

Fault Scenario
After the optical cable interruption fault is rectified and the optical cables are restored, the
services carried by the WDM equipment cannot be automatically restored.

All services are interrupted.

Step 1 First exclude external faults, board faults, and abnormal optical power according to the
emergent handling procedure in the WDM system and the fault handling guide to service
interruption.
Issue 01 (2011-08-10)
Page 56 of 95
Step 2 If the interrupted services are configured with extension intra-board 1+1 protection, the
IN-PWR-HIGH alarm is reported at the WDM-side optical port on the OTU board, and the
OPR-DIFF-OVER alarm is reported on the OLP board, perform the following measures. If
the optical power on the working channel is high, forcibly switch the services in the
protection group over to the protection channel; if the optical power at the optical port on the
protection channel is high, lock and switch the services in the protection group over to the
working channel and adjust the excessively high optical power value to a normal one. After
that, clear the external switching command of the protection group.
Step 3 If the interrupted services are GE services, you need to wait for about two minutes after the
optical cables are restored because re-enabling the protocol takes time. GE services can be
restored only after the protocol is re-enabled.
Step 4 Check if the laser on the optical amplifier board is shut down. If the laser is shut down,
resolve the fault using the following procedure:
Manually enable the laser.
In a system configured with IPA in automatic restart mode, IPA automatically enables the
laser several minutes after IPA is enabled.
In a system configured with IPA in manual restart mode, IPA can automatically enable
the laser only after IPA is manually re-started.
Step 5 Check if the laser of the Raman optical amplifier board is shut down or the gain of the pump
is insufficient. If the laser is shut down or the gain of the pump is insufficient, resolve the
fault using the following procedure:
In a system configured with the Raman optical amplifier board, check whether the laser
on the Raman optical amplifier board is enabled after the optical fibers are restored. If
the laser is shut down, the laser can be enabled only when IPA is enabled.
Check if the on-off gain of the Raman optical amplifier board satisfies specification
requirements. If it does not satisfy the index requirements, adjust the on-off gain by
referring to the Commissioning Guide.
----End
4.13 Service Interruption Caused by Misoperations

Fault Scenario
Manual misoperations result in service interruption.

Services carried by the OTU board are interrupted.

The possible causes of service interruptions and the restoration measures are as follows:
Issue 01 (2011-08-10)
Cause 1: Services are not configured with protection but are mistakenly configured with
1+1 optical channel protection. In this mode, the mistakenly configured 1+1 optical
channel protection results in service interruption on the OTU board in the slot of the
protection channel.
Page 57 of 95
Measures: Delete the mistakenly configured protection.
Cause 2: The FEC on the OTU board is disabled and no alarm is reported.
Measures: Ensure that the FEC is enabled during maintenance because no alarm is
reported whenever the FEC on the OTU board is enabled or not.
Cause 3: The FEC mode on the OTU board is changed manually.

Measures: Check the FEC modes on the interconnected OTU boards to check if they are
consistent. If the FEC modes are not consistent, change them.
Cause 4: Hardware loopback and software loopback are set manually.

Measures: Check if hardware loopback is manually set to the service channel. If it is
configured, release it.
Check if software loopback is manually set to the service channel by using the NMS. If it
is configured, release it.
Cause 5: The protection types are incorrectly configured. The ODUk SNCP protection
requires an SNC/N scenario but is mistakenly configured with an SNC/I scenario. When
services pass through the REG, the ODUk SNCP protection cannot be switched to the
correct protection but optical fibers are interrupted. As a result, services are interrupted.
Measures: Switch the SNC/I protection group to the SNC/N protection group. For
detailed information, refer to the Changing the SNCI Services to the SNCN Services by
Using the NMS.
Cause 6: For services with protection, the optical fibers on the protection channel are
incorrectly connected and thereby services on the working channel are interrupted. When
services are switched to the protection channel, they are interrupted.
Measures: Perform a protection switching test to check all physical and logical fiber
connections on the protection channel in the protection group with interrupted services.
Then correct the optical fiber connections on the protection channel.
Cause 7: For services with protection, protection configurations are incorrect and thereby
cross-connection routing on the working channel is incorrect. As a result, when services
are switched to the protection channel after services are interrupted on the working
channel, they are interrupted.
Measures: Perform a protection switching test to check configurations of the protection
group with interrupted services. Then configure a correct protection group.
Cause 8: For services with protection, cross-connections on the protection channel are
mistakenly deleted by a user. When services on the working channel are switched to the
protection channel after service interruption, they are interrupted.
Measures: Perform a protection switching test to check the cross-connection
configurations of the protection group with interrupted services. Then restore the deleted
cross-connections.
Cause 9: The logical intra-board fiber connections on the NE are inconsistent with the
actual fiber connections. If a WMU board is configured and the wavelength locking is
enabled, the wavelength locking may be mistakenly adjusted, and services are thereby
interrupted.
Measures: Check if the physical and logical fiber connections on a live network are
consistent and correct any incorrect connections.
Cause 10: The RMU9 board supports any wavelength. If the RMU9 board receives
wavelengths of the same size, the board cannot detect the wavelengths and services that
pass through on the wavelength are interrupted.
Measures: Check if the add wavelengths conflict with the original pass-through
wavelengths. If conflicts are noticed, groom the add wavelengths to other idle
wavelengths.
Issue 01 (2011-08-10)
Page 58 of 95
Cause 11: If the protection group is in forced or locked state, the protection group cannot
be switched normally during service cutover or when a fiber fault occurs. As a result,
services are interrupted.
Measures: Check the status of the protection group on the live network periodically and
release the abnormal status of the protection group.
Issue 01 (2011-08-10)
Page 59 of 95
Identifying Faults in Interconnection

Between WDM and Other Products
Objective
As networks are converging, WDM products need to be interconnected with routers, MSTP
products, and PTN products provided by other suppliers. This chapter sorts out the common
methods for troubleshooting faults in interconnection. These methods will help maintenance
personnel quickly identify faults.
Intended Audience
When WDM products are interconnected with other types of products, take into account the
requirements for interconnection design, and verify and set relevant parameters based on
recommended interconnection configurations. When a fault occurs, identify the fault
according to the guidelines.
5.1 Design Constraints for Interconnecting WDM Products

and Routers
5.1.1 Standard Compliance
The WDM products are the OptiX OSN series products, which comply with ITU-T
G.709.
Protection switching on WDM products complies with the following standards:
Issue 01 (2011-08-10)
ITU-T Recommendation G.774 Synchronous Digital Hierarchy (SDH) management

information model for the network element view
ITU-T Recommendation G.798 (Characteristics of optical transport network

hierarchy equipment functional blocks)
ITU-T Recommendation G.841 Types and characteristics of SDH network protection

architectures
Page 60 of 95
ITU-T Recommendation G.808.1 (The generic functional models, characteristics and

processes associated with various linear protection schemes for connection-oriented
layer networks)
Ethernet ports on routers and WDM products comply with IEEE 802.3.
SDH ports on routers and WDM products comply with ITU-T G.707.
5.1.2 Checking Configuration for Interconnecting WDM Products

and Other Products on a Network with Protection
No.
Check Item
Recommended
Configuration
Cause
Probable
Consequence of
Nonconformance
Hold-off time of
ports on a router
When there is no
embedded protection,
the hold-off time must
be set for the router. It is
recommended to set the
hold-off time to 200 ms.
Protection switching on
WDM products results in
the down state of physical
ports on the router and
services are damaged.
When there is embedded

protection on WDM
products, the hold-off
time for the router can
be extended. Extend
hold-off time by 50 ms
for every extra level of
protection.
Before protection
switching on a WDM
product is complete,
services are interrupted
for a short period. If the
hold-off time is not set
for the router, service
interruption results in
the down state of ports
on the router.
When there is no
embedded protection, do
not set the hold-off time
for protection switching
on WDM products. That
is, retain the default
hold-off time (0).
WDM products may fail

to complete protection
switching in time.
Setting the hold-off time
avoids this problem.
Multiple levels of
protection may result in
excessively long
protection switching
time.
When there is embedded

protection, extend the
hold-off time by 50 ms
for every extra level of
external protection.
Auto-negotiation modes
of interconnected ports
must be consistent.
It is recommended to set
interconnected ports to
auto-negotiation mode.
In the scenario where a

router is interconnected
with a WDM product, if
auto-negotiation is
enabled at one port (A)
but is disabled at the
interconnected port (B),
port B can be up but port
A is unstable. That is,
port A may be up or
down, depending on the
chip.
Protection switching on
WDM products results in
the down state of
physical ports on the
router and services are
damaged. To restore the
services, perform a
loopback at the port on
the router and then
release the loopback.
Hold-off time for

protection
switching on
WDM products
Auto-negotiation
mode
Issue 01 (2011-08-10)
Page 61 of 95
No.
Check Item
Recommended
Configuration
Cause
Probable
Consequence of
Nonconformance
Clock mode
the clock mode to
master-master mode.
This avoids a clock loop.

A clock loop results in
service interruption.
Services are interrupted.
5.1.3 Checking Configuration for Interconnecting WDM Products

and Other Products on a Network Without Protection
No.
Check Item
Recommended
Configuration
Cause
Probable
Consequence of
Nonconformance
Hold-off time of
ports on a router
the hold-off time to 0 ms.
In case of a link fault,

the router can detect it in
time and start service
protection on the router
layer such as FRR.
Excessive hold-off time

may result in a delay in
restoring services.
Auto-negotiation
mode
Auto-negotiation modes
of interconnected ports
must be consistent.
interconnected ports to
auto-negotiation mode.
In the scenario where a

router is interconnected
with a WDM product, if
auto-negotiation is
enabled at one port (A)
but is disabled at the
interconnected port (B),
port B can be up but port
A is unstable. That is,
port A may be up or
down, depending on the
chip.
The physical port is

down. To recover the
port, perform loopback at
the port and then release
the loopback.
This avoids a clock loop.

A clock loop results in
service interruption.
Services are interrupted.
Clock mode
Issue 01 (2011-08-10)
Do not set the clock mode

to "slave" for both
interconnected ports.
Page 62 of 95
5.2 Common Methods for Identifying Interconnection

Faults
Alarm Analysis
Analyze alarms at different equipment levels according to the time sequence to identify the
fault point.
Sort alarm information along the link to identify the fault point.
Section-by-Section Loopbacks
Service
PTN
MSTP
Router
WDM
OTU
WDM
OTU
PTN
MSTP
Service
Router
Start from the first NE to set outloops along the link. This helps quickly identify the equipment with the fault.
Set inloops and outloops along the link. This helps identify the board with the fault.
Issue 01 (2011-08-10)
Page 63 of 95
Appendix I: WDM Alarm Signal Flow
Objective
This chapter describes the seven types of scenarios associated with the alarm signal flow, SF,
SD, and basic concepts in the alarm signal flow diagram. It also describes the generation,
detection, and transmission of alarms when the OTU receives different types of signals.
Information in this chapter helps engineers determine the cause of an alarm reported when a
fault occurs.
Intended Audience
For a WDM product, the detection and transmission of alarms vary according to the type of
signals received by the OTU. The OTU is classified into the following types:
Non-convergent OTU
It refers to an OTU that converts one channel of client service signals.
Convergent OTU
It refers to an OTU that converges and converts multiple channels of client service
signals.
Regenerating OTU
It refers to an OTU that regenerates the corresponding service signals at an intermediate
site.
According to the type of the OTU and the type of the signals accessed by the OTU, the
following seven situations are defined in this section:
Non-convergent OTU processing standard SDH signals

This section describes the alarm signal flow when the non-convergent OTU processes
standard SDH signals.
Non-convergent OTU processing standard OTN signals

standard OTN signals.
Convergent OTU processing standard SDH signals

This section describes the alarm signal flow when the convergent OTU processes
standard SDH signals.
Issue 01 (2011-08-10)
Page 64 of 95
Convergent OTU processing standard OTN signals

standard OTN signals.
Regenerating OTU
This section describes the alarm signal flow of the regenerating OTU.
OTU with the cross-connect function

This section describes the alarm signal flow of an OTU with the cross-connect function.
OTU processing GE signals

This section describes the alarm signal flow when the OTU processes GE signals.
6.1 Background Knowledge

SF and SD
SF is a signal failure event, and SD is a signal degrade event. The SF and SD events are
trigger conditions of protection switching. Whether the SD event is used as a trigger condition,
however, can be set by users.
The SF and SD events are marked in the alarm signal flow diagrams in this section. These
events are generated when the equipment configured with network protection detects a certain
alarm. If the equipment is not configured with the network protection, the SF and SD events
are not detected or reported.
Concepts
The following concepts are used in the diagrams in this section:
WDM side: It is the WDM side of the OTU.
Client side: it is the client side of the OTU. On the client side, the services from a client
device are accessed.
Middle part: It is the middle part between the WDM side and the client side. It is a
virtual concept, and therefore is not displayed on the U2000. This concept is introduced
to describe the alarm detection mechanism.
N#1: It indicates channel 1 at optical interface N on the OTU. For example, the
client-side optical interfaces of the LQMD unit are numbered 3, 4, 5, and 6, and the
WDM-side optical interface of the LQMD unit is numbered 1. Then, 3#1 indicates
channel 1 at client-side optical interface 3.
1#N: It indicates channel N at WDM-side optical interface 1 on the OTU. For example,
1#3 indicates channel 3 at WDM-side optical interface 1.
6.2 Non-Convergent OTU Processing Standard

SONET/SDH Signals
SONET/SDH standard signals.
Issue 01 (2011-08-10)
Page 65 of 95
Figure 6-1 and Figure 6-2 describe the alarm signal flow when the non-convergent OTU
processes SONET/SDH standard signals.
The ALS function of the OTU shown in the figures in this section is not enabled.
Figure 6-1 Alarm signal flow 1 when non-convergent OTU processes SONET/SDH standard
signals
Station A
Client-side
LOS
LOF
AIS-L
B1 errors
B1 errors
Station B
WDM-side
WDM-side
Client device
Client-side
Client-device
LOS
REMC-SF
LOF
LOF
REMC-SF
LOF
AIS-L
REMC-SF
AIS-L
SF-S
REMC-SD
B1 errors
SD-S
B1 errors
PM BIP errors
SD
ODU-DEG/
ODU-EXC
SM BIP errors
SD
OTU-DEG/
OTU-EXC
OTU-AIS
Errors
Errors
SF
OTU-AIS
LOF
OTU-BDI&ODU-BDI
SF:SF event detecting

xxx
SD:SD event detecting
Alarm processing
Detects and reports the xxx alarm.
This section describes the alarm signal flow by analyzing how the OTU unit processes the
LOS alarm and PM BIP errors. The alarm signal flow of other alarms is similar.
LOS
The client side of the OTU at station A receives LOS signals. The LOS signals are
processed on the WDM side of the OTU and then are sent to station B. The client side of
the OTU at station B detects the REMC-SF alarm. The alarm is then sent to the
Issue 01 (2011-08-10)
Page 66 of 95
downstream client device of station B, and the OTU reports the LOF alarm to the client
device.
PM BIP errors
The OTU unit at station B detects PM BIP errors on the WDM side. Then, the
ODU-DEG or ODU-EXC alarm is generated. The number of errors detected determines
which of the two alarms is generated. The errors are sent to the downstream client device.
The alarm cannot be sent to the downstream station unless the PM BIP errors are
generated because of faults on the local station. The error-dependent alarm is detected in
the client device.
An SD event is generated on the WDM side of the OTU at station B, and protection
switching is triggered.
Issue 01 (2011-08-10)
Page 67 of 95
Figure 6-2 Alarm signal flow 2 when non-convergent OTU processes SONET/SDH standard
signals
Station A
Client-side
Station B
WDM-side
WDM-side
Client-side
Client device
Client-device
SF
OTU-LOM
MFAS frame discontinuous
The SF event is generated when the

TIM follow-up response is Enabled.
PM TTI byte mismatch
ODU-TIM
ODU-BDI
LOF
SM TTI byte mismatch
OTU-TIM
LOF
OTU-BDI
ODU-BDI
ODU-BDI
OTU-BDI
OTU-BDI
Excessive bit errors before FEC
BEFFEC-EXC
OTU-LOF
SF
OTU-LOF
LOF
ODU-BDI&OTU-BDI
ODU-AIS/
ODU-OCI/
ODU-LCK
SF
ODU-AIS/
ODU-OCI/
ODU-LCK
LOF
ODU-BDI
SF
LOS
LOS
LOF
ODU-BDI&OTU-BDI
SF : SF event detecting
Alarm processing
xxx
xxx
Detects and reports the xxx alarm when the TIM follow-up response is Enabled.
OTU-BDI and OTU-LOF alarms. The alarm signal flow of other alarms is similar.
OTU-BDI
The WDM side of the OTU at station B detects the OTU-BDI alarm that is sent from
upstream station A. The alarm is not sent to the downstream station.
Issue 01 (2011-08-10)
OTU-LOF
Page 68 of 95
The WDM side of the OTU at station B detects the OTU-LOF alarm. Then, the OTU
sends the ODU-BDI and OTU-BDI alarms to the WDM side of upstream station A. In
addition, the alarm is sent to the client side of station B. After the alarm is processed on
the client side, the LOF alarm is detected in the client device.
An SF event is generated on the WDM side of the OTU at station B, which triggers protection
switching.
6.3 Non-Convergent OTU Processing OTN Standard

Signals
This section describes the alarm signal flow when the non-convergent OTU processes OTN
standard signals.
Figure 6-3 and Figure 6-4 describe the alarm signal flow when the non-convergent OTU
processes OTN standard signals.
Issue 01 (2011-08-10)
Page 69 of 95
Figure 6-3 Alarm signal flow 1 when non-convergent OTU processes OTN standard signals
Station A
Client-side
Station B
WDM-side
WDM-side
LOS
SF
ODU-AIS
PM BIP errors
ODU-DEG/
ODU-EXC
SD
ODU-DEG/
ODU-EXC
SM BIP errors
OTU-DEG/
OTU-EXC
LOS
Client device
Client-side
Client-device
ODU-AIS
PM BIP errors
SD
PM BIP errors
SM BIP errors
OTU-LOF
ODU-DEG/
ODU-EXC
PM BIP errors
SD
OTU-DEG/
OTU-EXC
OTU-LOF
SF
ODU-AIS
ODU-AIS
OTU-AIS
SF
ODU-AIS
ODU-AIS
OTU-BDI&ODU-BDI
OTU-AIS
OTU-BDI&ODU-BDI
OTU-LOF/
OTU-AIS
SF
OTU-LOF/
OTU-AIS
ODU-AIS
OTU-BDI&ODU-BDI

xxx
Alarm processing
LOS and OTU-LOF alarms. The alarm signal flow of other alarms is similar.
LOS
The client side of the OTU at station A receives LOS signals. The LOS signals are
processed on the WDM side of the OTU and then are sent to station B. The WDM side
of the OTU at station B detects the ODU-AIS alarm and then an SF event is generated.
Issue 01 (2011-08-10)
Page 70 of 95
The event triggers protection switching. The alarm is sent to the downstream client
device where the ODU-AIS alarm is detected.
The OTU-LOF signals are accessed on the WDM side.

The WDM side of the OTU at station B detects the OTU-LOF alarm. The OTU sends the
OTU-BDI alarm to the WDM side of station A. In addition, the alarm is sent to the client
side of station B. After the alarm is processed on the client side, the ODU-AIS alarm is
detected in the client device.
An SF event is generated on the WDM side of the OTU at station B, and protection
The OTU-LOF signals are accessed on the client side.

After receiving OTU-LOF signals on the client side, the OTU at station A sends the
OTU-BDI alarm to the upstream client device. In addition, the OTU-LOF alarm is
processed on the WDM side of the OTU and then is sent to station B. The WDM side of
the OTU at station B detects the ODU-AIS alarm, and then an SF event is generated. The
event triggers protection switching. The alarm is sent to the downstream client device
where the ODU-AIS alarm is detected.
Issue 01 (2011-08-10)
Page 71 of 95
Figure 6-4 Alarm signal flow 2 when non-convergent OTU processes OTN standard signals
Station A
Station B
Client-side
WDM-side
WDM-side

OTU-TIM
Client-side
SM TTI byte
mismatch
Client-device
SF
ODU-AIS
OTU-BDI
Client device
ODU-AIS
OTU-TIM
ODU-AIS
OTU-BDI
OTU-BDI
OTU-BDI
OTU-BDI
OTU-BDI
Transparent transmission of all PM signals

ODU-AIS/
ODU-LCK/
ODU-OCI
ODU-AIS/
ODU-LCK/
ODU-OCI
ODU-AIS/
ODU-LCK/
ODU-OCI
ODU-AIS/
ODU-LCK/
ODU-OCI
SF
LOS
LOS
ODU-AIS
ODU-BDI&OTU-BDI
Alarm processing
xxx
xxx
OTU-TIM
When the OTU receives the OTU-TIM alarm on the client side or on the WDM side, the
OTU sends the OTU-BDI alarm to the upstream station.
OTU-BDI
The OTU detects the OTU-BDI alarm that is sent from the upstream station. This alarm
is not sent to the downstream station.
ODU-TIM/ODU-BDI
The OTU transparently transmits all PM alarms.
ODU-AIS/ODU-LCK/ODU-OCI
The client side of the OTU at station A receives ODU-AIS, ODU-LCK, or ODU-OCI
signals. The signals are not processed or reported at the local station. After the signals
are sent to station B, the WDM side of the OTU at station B detects the ODU-AIS,
ODU-LCK, or ODU-OCI alarm. Then, an SF event is generated. The event triggers
Issue 01 (2011-08-10)
Page 72 of 95
protection switching. The alarm is sent to the downstream client device where the
ODU-AIS, ODU-LCK, or ODU-OCI alarm is detected.
LOS
The WDM side of the OTU at station B detects the LOS alarm. The OTU sends
ODU-BDI and OTU-BDI alarms to the WDM side of upstream station A. In addition, the
alarm is sent to the client side of station B. After the alarm is processed on the client side,
the ODU-AIS alarm is detected in the client device.
6.4 Convergent OTU Processing SONET/SDH Standard

Signals
Figure 6-5 and Figure 6-6 describe the alarm signal flow when the convergent OTU processes
In Figure 6-5, N#1 indicates channel 1 at optical interface N on the OTU unit. For example, the
client-side optical interfaces of the LQG unit are numbered 3, 4, 5 and 6, and the WDM-side optical
interface of the LQG unit is numbered 1. Therefore, 3#1 indicates channel 1 at optical interface 3 on
the client side. 1#N indicates channel N at optical interface 1 on the WDM side of the OTU unit. For
example, 1#3 indicates channel 3 at optical interface 1 on the WDM side.
The middle part of the OTU unit is between the WDM side and the client side. It is a virtual concept,
and therefore is not displayed on the U2000. This concept is introduced to describe the alarm
detection mechanism. In the middle part of the convergent OTU, the optical interface number and
channel number of signals are re-allocated.
The ALS function of the OTU shown in the figures in this section is not enabled.
Issue 01 (2011-08-10)
Page 73 of 95
Figure 6-5 Alarm signal flow 1 when convergent OTU processes SONET/SDH standard signals
Station A
Client-side
LOS
Station B
Middle
WDM-side
WDM-side
Middle
Client device
Client-side
Client-device
N#1 LOS
N#1 REMC-SF
N#1 LOF
LOS
N#1 LOS
N#1 REMC-SF
N#1 LOF
LOS
N#1 LOS
N#1 REMC-SF
N#1 LOF
LOS
N#1 LOS
N#1 REMC-SF
N#1 LOF
N#1 LOS
N#1 REMC-SF
N#1 LOF
N#1 LOF
N#1 REMC-SF
N#1 LOF
N#1 REMC-SF
N#1 LOF
LOS
LOF
LOC
N#1 LOC
SD
1#N BIT errors
Errors
N#1 A
1#N A
N#1 B
1#N B
N#1 C
1#N C
N#1 D
1#N D
Errors N#1 errors
A
B
C
ABCD are the others of the SONET/SDH alarms

xxx
Alarm processing
This section describes the alarm signal flow through an example in which four client-side
services are accessed on the convergent OTU.
Four channels of LOS signals are accessed on the client side.

The OTU at station A receives four channels of LOS signals on the client side. After
being processed in the middle part of the OTU at station A, the alarm signals are sent to
station B. After being processed on the WDM side of the OTU at station B, the
REMC-SF alarm is generated on the client side of station B. The LOF alarm is detected
in the client device.
One channel of LOS signals is accessed on the client side.

The OTU at station A receives one channel of LOS signals on the client side, for
example, channel 1 at optical interface 3. After being processed in the middle part and on
the WDM side of the OTU at station A and the WDM side of station B, the alarm signals
are sent to the downstream station. The LOF alarm for channel 3 at optical interface 1 is
generated in the middle part of station B, and the REMC-SF alarm of channel 1 at optical
interface 3 is generated on the client side. The LOF alarm is detected in the client device.
Non-LOS alarms are accessed on the client side.

The signal flow of the LOF or the LOC is similar to that of the LOS.
Issue 01 (2011-08-10)
Page 74 of 95
When any other alarms are accessed, the same alarm is reported at each detection point
in the system.
Figure 6-6 Alarm signal flow 2 when convergent OTU processes SONET/SDH standard signals
Station A
Client-side
Client device
Station B
Middle
WDM-side
WDM-side
Middle
Client-side
Client-device
LOF
LOS
LOF
SF
LOS
LOF
ODU-BDI&OTU-BDI
LOF
LOF
SF
OTU-LOF/
OTU-AIS OTU-LOF/
OTU-AIS
LOF
LOF
ODU-BDI&OTU-BDI
LOF
LOF
SF
ODU-AIS/
ODU-LCK/ ODU-AIS/
ODU-OCI ODU-LCK/
ODU-OCI
LOF
LOF
ODU-BDI
LOF
Errors
PM BIP
errors
SD
Errors
ODU-DEG/
ODU-EXC
Errors
Errors
Errors
SM BIP
errors
SD
Errors
OTU-DEG/
OTU-EXC
Errors
Errors

xxx
Alarm processing
LOS, OTU-LOF, OTU-AIS, ODU-AIS, ODU-OCI, or ODU-LCK exist on the WDM

side.
The WDM side of the OTU at station B receives and processes the alarm signals. The
OTU sends the ODU-BDI or OTU-BDI alarm to the WDM side of upstream station A. In
the client side, the LOF alarm is detected in the client device.
Issue 01 (2011-08-10)
Page 75 of 95
Bit error alarms exist on the WDM side.

The WDM side of the OTU at station B receives and processes the bit error alarm signals.
The alarm is sent to the client side of downstream station B. The error-dependent alarm
is detected in the client device.
6.5 Convergent OTU Processing OTN Standard Signals

This section describes the alarm signal flow when the convergent OTU processes OTN
standard signals.
Figure 6-7 and Figure 6-8 describe the alarm signal flow when the convergent OTU processes
OTN standard signals.
In Figure 6-7, N#1 indicates channel 1 at optical interface N on the OTU unit. For example, the
client-side optical interfaces of the LQG unit are numbered 3, 4, 5 and 6, and the WDM-side optical
interface of the LQG unit is numbered 1. Therefore, 3#1 indicates channel 1 at optical interface 3 on the
client side. 1#N indicates channel N at optical interface 1 on the WDM side of the OTU unit. For
example, 1#3 indicates channel 3 at optical interface 1 on the WDM side.
The middle part of the OTU unit is the middle part between the WDM side and the client side. It is a
virtual concept, and therefore is not displayed on the U2000. This concept is introduced to describe the
alarm detection mechanism. In the middle part of the convergent OTU, the optical interface number and
channel number of signals are re-allocated.
Non-Intrusive Monitoring of the boards shown in the figures in this section is enabled.
Issue 01 (2011-08-10)
Page 76 of 95
Figure 6-7 Alarm signal flow 1 when convergent OTU processes OTN standard signals
Station B
Station A
Client-side
Middle
WDM-side
WDM-side
Middle
LOS
1#N ODU-AIS
N#1 LOS
1#N ODU-AIS
N#1 LOS
1#N ODU-AIS
N#1 LOS
1#N ODU-AIS
N#1 LOS
1#N ODU-AIS
N#1 LOS
1#N ODU-AIS
N#1 OTU-LOF
1#N ODU-AIS
LOS
N#1 REMC-SF
N#1 ODU-AIS
N#1 REMC-SF
N#1 ODU-AIS
N#1 REMC-SF
N#1 ODU-AIS
N#1 REMC-SF
N#1 ODU-AIS
N#1 REMC-SF
N#1 ODU-AIS
N#1 REMC-SF
N#1 ODU-AIS
N#1 REMC-SF
N#1 ODU-AIS
SF
Inserts OTU-BDI back

LOS
SF

LOS
SF
SF
LOS
OTU-LOM
SF

OTU-LOF
ODU-AIS
Client-device
SF
N#1 LOS
Client device
Client-side
SF
SD
N#1 ODU-AIS
1#N ODU-AIS
1#N ODU-AIS
N#1 A
1#N A
1#N A
N#1 B
1#N B
1#N B
N#1 C
1#N C
1#N C
A
B
C
SD
BIT errors
N#1 BIT errors

xxx
1#N BIT errors

Alarm processing
N#1 BIT errors
ABC are the others of the OTN alarms
Four channels of LOS signals are accessed on the client side.

The OTU at station A receives four channels of LOS signals on the client side. After
being processed in the middle part and on the WDM side of the OTU at station A, the
alarm signals are sent to station B. The ODU-AIS alarm for the corresponding channel is
generated in the middle part of station B, and the REMC-SF alarm is reported on the
client side. The ODU-AIS alarm is detected in the client device.
An SF event is generated in each channel of the OTU at station B, and protection
One channel of LOS, OTU-LOM, or OTU-LOF signals is accessed on the client side.
The OTU at station A receives one channel of LOS, OTU-LOM, or OTU-LOF signals on
the client side, for example, channel 1 at optical interface 3. After being processed in the
middle part and on the WDM side of the OTU at station A and the WDM side of station
B, the alarm signals are sent to the downstream station. The ODU-AIS alarm for channel
Issue 01 (2011-08-10)
Page 77 of 95
3 at optical interface 1 is generated in the middle part of station B, and the REMC-SF
alarm for channel 1 at optical interface 3 is reported on the client side. The ODU-AIS
alarm is detected in the client device.
An SF event is generated in the corresponding channel in the middle part of the OTU at
station B, and protection switching is triggered.
All the alarms, except the LOS, OTU-LOM, and OTU-LOF, are accessed on the client
side.
When any other alarms are accessed, the same alarm is reported at each detection point
in the system.
Figure 6-8 Alarm signal flow 2 when convergent OTU processes OTN standard signals
Station A
Client-side
Middle
Client device
Station B
WDM-side
WDM-side
Middle
Client-side
Client-device
ODU-AIS
ODU-AIS
SF
LOS
LOS
ODU-AIS
ODU-AIS
ODU-BDI&OTU-BDI
ODU-AIS
OTU-LOF/
OTU-AIS
SF
ODU-AIS
OTU-LOF/
OTU-AIS
ODU-AIS
ODU-BDI&OTU-BDI
ODU-AIS
ODU-AIS
ODU-AIS/
ODU-LCK/
ODU-OCI
SF
ODU-AIS
ODU-AIS/
ODU-LCK/
ODU-OCI
ODU-AIS
ODU-BDI
ODU-AIS
Errors
SD
PM BIP errors
Errors
ODU-DEG/
ODU-EXC
Errors
Errors
Errors
SD
SM BIP errors
Errors
OTU-DEG/
OTU-EXC
Errors
Errors

xxx
Issue 01 (2011-08-10)
Alarm processing
Page 78 of 95
LOS, OTU-LOF, OTU-AIS, ODU-AIS, ODU-OCI, or ODU-LCK exist on the WDM

side.
The WDM side of the OTU at station B receives and processes the alarm signals. The
OTU sends the ODU-BDI or OTU-BDI alarm to the WDM side of upstream station A. In
the client side, the ODU-AIS alarm is detected in the client device.
Bit error alarms exist on the WDM side.

The WDM side of the OTU at station B receives and processes the bit error alarm signals.
The alarm is sent to the client side of downstream station B. The error-dependent alarm
is detected in the client device.
6.6 Regenerating OTU

This section describes the alarm signal flow of the regenerating OTU.
Figure 6-9 shows the alarm signal flow of the regenerating OTU.
Issue 01 (2011-08-10)
Page 79 of 95
Figure 6-9 Alarm signal flow of the regenerating OTU

Station A
Station B(REG)
WDM-side
WDM-side1
MFAS frame discontinuous

PM TTI byte mismatch
WDM-side2
Station C
WDM-side
OTU-LOM
ODU-TIM
ODU-TIM
OTU-TIM
ODU-AIS
OTU-BDI
ODU-BDI
OTU-BDI
OTU-LOF
ODU-BDI
ODU-BDI
OTU-BDI
OTU-LOF
ODU-AIS
ODU-AIS/
ODU-OCI/
ODU-LCK
ODU-AIS/
ODU-OCI/
ODU-LCK
PM BIP errors
ODU-DEG/
ODU-EXC
ODU-DEG/
ODU-EXC
SM BIP errors
OTU-DEG/
OTU-EXC
OTU-BDI
ODU-AIS/
ODU-OCI/
ODU-LCK
Excessive bit errors before FEC
LOS
xxx
xxx
BEFFEC-EXC
LOS
ODU-AIS

For a regenerating OTU, all alarms in the SM section are terminated at the local station and
are not sent to the downstream station. Exceptions are OTU-LOF/OTU-TIM alarms, which
Issue 01 (2011-08-10)
Page 80 of 95
are inserted with an ODU-AIS alarm to the downstream station. Other alarms are sent to the
downstream station and are reported on the WDM side of the OTU, except for LOS alarms
which are inserted with an ODU-AIS alarm to the downstream station.
6.7 Alarm Signal Processing of the OTU with the

Cross-Connect Function
An OTU with the cross-connect function supports service transmission in straight-through
mode or cross-connect mode. The processing of alarm signals in one mode is different from
that in the other. This section describes the alarm signal flow of an OTU with the
cross-connect function.
I. Straight-Through Mode
Figure 6-10 shows the unidirectional signal flow in straight-through mode.
The optical interface number and channel number shown in Figure 6-10 are displayed on the U2000.
Figure 6-10 OTU unit with the cross-connect function in straight-through mode
A
3#1(RX1)
4#1(RX2)
5#1(RX3)
6#1(RX4)
B
1#3
1#4 1(OUT)
1#5
1#3
1(IN) 1#4
1#5
1#6
1#6
3#1(TX1)
4#1(TX2)
5#1(TX3)
6#1(TX4)
As shown in Figure 6-10, the four channels of optical signals accessed from RX1-RX4 on unit
A at the upstream station are sent to channels 3-6 that correspond to the OUT port in
straight-through mode. One channel of optical signals that is input from the IN port on unit B
at the downstream station is demultiplexed into four channels of optical signals, which are
then sent to TX1-TX4.
Therefore, in straight-through mode, the REMC-SF and REMC-SD alarms at the downstream
station indicate that the signals at the corresponding port on the client side at the upstream
station fail or bit errors at this port exceed the threshold. For example, when the services in
channel 1 at optical interface 3 on unit A at the upstream station fail, channel 1 at optical
interface 3 on unit B at the downstream station reports the REMC-SF alarm.
II. Cross-Connect Mode

Cross-connect mode is classified into intra-unit cross-connections and inter-unit
cross-connections.
Intra-unit cross-connections
In Figure 6-11, the cross-connection from RX2 (channel 1 at optical interface 4) on unit
A to OUT (channel 3 at optical interface 1) on unit A is defined as the intra-unit
cross-connection.
Issue 01 (2011-08-10)
Inter-unit cross-connections
Page 81 of 95
In Figure 6-11, the cross-connection from RX1 (channel 1 at optical interface 3) on unit
C to OUT (channel 6 at optical interface 1) on unit A is defined as the inter-unit
cross-connection. The inter-unit cross-connection is achieved by using the backplane.
Figure 6-11 shows the unidirectional signal flow diagram in cross-connect mode.
Figure 6-11 OTU unit with the cross-connect function in cross-connect mode
A
3#1(RX1)
B
1#3
1#4 1(OUT)
1#5
4#1(RX2)
5#1(RX3)
6#1(RX4)
1#3
1(IN) 1#4
1#5
1#6
3#1(RX1)
1#6
3#1(TX1)
4#1(TX2)
5#1(TX3)
6#1(TX4)
1#3
1#4
1#5
4#1(RX2)
5#1(RX3)
6#1(RX4)
1#6
C
In Figure 6-11, the following cross-connections are created:
An intra-unit cross-connection from RX2 (channel 1 at optical interface 4) on unit A to

OUT (channel 3 at optical interface 1) on unit A
An inter-unit cross-connection from RX1 (channel 1 at optical interface 3) on unit C to

OUT (channel 6 at optical interface 1) on unit A
The signals received from RX2 (channel 1 at optical interface 4) on unit A at the upstream
station are sent to IN (channel 3 at optical interface 1) on unit B at the downstream station.
The signals received from RX1 (channel 1 at optical interface 3) on unit C at the upstream
station are sent to IN (channel 6 at optical interface 1) on unit B at the downstream station.
Optical interfaces and channels related to REMC-SF and REMC-SD alarms in cross-connect
mode are different from those in straight-through mode. For example, if the services in
channel 1 at optical interface 4 on unit A at the upstream station fail, unit B at the downstream
station reports the REMC-SF alarm in channel 1 at optical interface 3; if the services in
channel 1 at optical interface 3 on unit C at the upstream station fail, unit B at the downstream
station reports the REMC-SF alarm in channel 1 at optical interface 6.
Therefore, when a unit reports the REMC-SF or REMC-SD alarm, query the
cross-connections of the unit at the upstream station to locate the alarm signal source. After
that, check whether the client signals in the channel at the corresponding optical interface are
in normal state. For example, check whether the optical power, fibers and optical modules
function properly. If not, take appropriate maintenance measures.
6.8 OTU Processing GE Signals

This section describes the alarm signal flow when the OTU unit processes Ethernet service
signals.
Issue 01 (2011-08-10)
Page 82 of 95
The GE services are encapsulated into OTN signals after they are accessed on the client side
of the OTU on an Ethernet network.
Figure 6-12 show the signal flow when the GE services are encapsulated into OTN signals.
The ALS function of the OTU shown in Figure 6-12 is not enabled.
Figure 6-12 Alarm signal flow 1 when the OTU processes GE signals
Station A
Client-side
Client device
Station B
Middle
WDM-side
WDM-side
Client-side
Middle
Client-device
Scenario 1: The client sides are in the non-negotiation mode.

LOS
LOS
REMC-SF
LINK-ERR
LINK-ERR
LINK-ERR
REMC-SF
None
Scenario 2: The client sides are in the auto-negotiation mode.

LOS
REMC-SF
LINK-ERR
LOS
LPT=Enable
LINK-ERR
LINK-ERR
None
LINK-ERR
LPT=Disable
Errors
PM BIP8 errors
LINK-ERR
None
Errors
Errors
LINK-ERR
Errors
SD
ODU-DEG/ODUEXC
Errors
PM remote BER
performance events
SD
OTU-DEG/
OTU-EXC
SM BIP8 errors
OTUk remote BER

performance events
LOS
Errors
SF
LOS
LINK-ERR
OTU-BDI&
ODU-BDI
OTU-AIS/
OTU-LOF/
OTU-LOM
OTU-BDI&
ODU-BDI
ODU-AIS/ODUOCI/ODU-LCK
SF
OTU-AIS/
OTU-LOF/
OTU-LOM
LINK-ERR
SF
LINK-ERR
ODU-AIS/ODUOCI/ODU-LCK
ODU-BDI
SF: SF event detecting

xxx
SD: SD event detecting
Alarm processing
Detects and reports the xxx alarm or performance event
This section describes the alarm signal flow when the OTU processes the LOS and
LINK-ERR alarms. The signal flow for processing other alarms is similar.
LOS
The client sides of the OTUs at stations A and B work in non-auto-negotiation mode. The
LOS alarm signal is received on the client side of an OTU at station A. The alarm signal
is sent to station B after it is processed on the WDM side of the OTU. In this case, the
Issue 01 (2011-08-10)
Page 83 of 95
REMC-SF alarm is generated on the client side of the OTU at station B, and the client
equipment at station B reports the LINK-ERR alarm.
The client sides of the OTUs at stations A and B work in auto-negotiation mode. The
LOS alarm signal is received on the client side of an OTU at station A. The alarm signal
is sent to station B after it is processed on the WDM side of the OTU. In this case, the
REMC-SF and LINK-ERR alarms are generated on the client side of the OTU at station
B, and the client equipment at station B reports the LINK-ERR alarm.
LINK-ERR
The client sides of the OTUs at stations A and B work in non-auto-negotiation mode. The
client signals at station A contain LINK-ERR alarms, and these client signals are
transmitted transparently from station A to the WDM side of the OTU at station B.
The client sides of the OTUs at stations A and B work in auto-negotiation mode. For Ethernet
units that support the LPT function, when the LPT enabling status is set to Disable, the
LINK-ERR is not generated on the client side of the OTU at station B; when the LPT
enabling status is set to Enable, the LINK-ERR alarm is generated on the client side of the
OTU at station B.
6.9 Optical-Layer Alarm Signal Processing on OTN

This section describes how an OTU board processes optical-layer alarm signals and how the
alarm signals flow.
Certain alarms are specific to the OCh, OMS, or OTS optical layer. This section describes the
association relationship between the optical-layer alarms generated by each NE.
This section describes the alarm association relationships in three network scenarios, as
shown in Figure 6-13, Figure 6-14, and Figure 6-15.
Figure 6-13 Scenario I
OTU
OTU
OTU
OM
OTU
OTU
OD
FIU
FIU
OA
OD
Line-side ODF
SC1
Line-side ODF
Client-side equipment
OTU
OA
OA
OTU
OTU
SC1
OTU
OA
OM
OTU
OTU
OTU
Station A
Station B
In this scenario, stations A and B are both OTM stations.

The OTS, OMS, and OCh trails are between adjacent nodes.
Issue 01 (2011-08-10)
Page 84 of 95
For the following faults, alarms that may be generated at each station are as follows:
The fiber from station A to station B is cut.

The FIU board at station B reports the OTS-LOS alarm and the FIU board at station A
reports the OTS-BDI alarm.
At station A, the optical amplifier unit in direction A-to-B is faulty.

The FIU board at station B reports the OTS-LOS-P alarm and the FIU board at station A
reports the OTS-BDI-P alarm.
At station A, the optical amplifier in direction A-to-B loses input light.

The FIU board at station A inserts the OTS-PMI signal and the FIU board at station B
does not report the OTS-LOS-P alarm.
At station A, the fiber in direction SC1-to-FIU is cut.

The FIU board at station B reports the OTS-LOS-O alarm and the FIU board at station A
reports the OTS-BDI-O alarm.
The configuration of the TTI to be received at station B is inconsistent with the TTI
transmitted by station A.
The FIU board at station B reports the OTS-TIM alarm and the FIU board at station A
The optical multiplexer (OM) unit at station A is faulty.

The optical demultiplexer (OD) unit at station B reports the OMS-LOS-P alarm and the
OM unit at station A reports the OMS-BDI-P alarm.
The OTU board at station A is faulty.

The OTU board at station B reports the OCh-LOS-P alarm.
Figure 6-14 Scenario II

OTU
OTU
OA
OTU
OD
OA
FIU
SC2
OA
West line-side
OTU
FI
U
ODF
SC1
Line-side ODF
OTU
OA
FIU
FIU
Line-side ODF
East line-side ODF
OM
OTU
OD
OTU
OTU
SC1
OA
OTU
OM
OA
OTU
OTU
OTU
Station A
Station B
Station C
In this scenario, stations A and C are both OTM stations, and station B is an OLA station.
Station OLA only amplifies signals and terminates the OTS layer. The OMS and OCh trails
are between station A and station C.

The FIU board at station B reports the OTS-LOS alarm and the OD unit at station C
reports the OMS-FDI alarm. The FIU board and OM unit at station A report the
OTS-BDI alarm and OMS-BDI alarm, respectively.
Issue 01 (2011-08-10)
Page 85 of 95
The FIU board at station B reports the OTS-LOS-P alarm. The OD unit at station C
reports the OMS-FDI-P alarm. The FIU board and OM unit at station A report the
OTS-BDI-P alarm and OMS-BDI-P alarm, respectively.


The FIU board at station B reports the OTS-LOS-O alarm. The OD unit at station C
reports the OMS-FDI-O alarm. The FIU board and OM unit at station A report the
OTS-BDI-O alarm and OMS-BDI-O alarm, respectively.
The FIU board at station B reports the OTS-TIM alarm. The OD unit at station C reports
the OMS-FDI alarm. The FIU board and OM unit at station A report the OTS-BDI alarm
and OMS-BDI alarm, respectively.
The OM unit at station A is faulty.

The OD unit at station C reports the OMS-LOS-P alarm and the OM unit at station A
reports the OMS-BDI-P alarm.

The OTU board at station B reports the OCh-LOS-P alarm.
Figure 6-15 Scenario III

West clientside
OOO
T T T
U U U
OTU
East clientside
O O OO
T T T T
U U U U
O
T
U
OTU
OTU
OM
OD
OA
OD
WSD9
OA
RMU9
OA
OA
OM
O
T
U
OTU
OA
FIU
SC2
WSD9
OA
OO OO O
T T T T T
U U UU U
FIU
OTU
OTU
SC1
OA
OD
West clientside
Station A
RMU9
OD
ODF
Line-side
ODF
line-side
East
OTU
West line-side ODF
OTU
FI
U
FI
U
Line-side ODF
SC1
OTU
OA
OM
OTU
OM
OTU
OO
T T
UU
OTU
East clientside
Station B
Station C
In this scenario, stations A and C are both OTM stations, and station B is an ROADM station.
In this scenario, station B adds and drops certain wavelengths. That is, certain wavelengths
are between stations A and B, or stations B and C, while other wavelengths are between
stations A and C. Therefore, certain OCh trails are between stations A and B, or B and C, and
other OCh trails are between stations A and C.
Issue 01 (2011-08-10)
Page 86 of 95

The FIU board at station B reports the OTS-LOS alarm and the FIU board at station A
reports the OTS-BDI alarm. Station C reports the OCh-FDI alarm (for wavelengths
between stations A and C).

The FIU board at station B reports the OTS-LOS-P alarm and the FIU board at station A
reports the OTS-BDI-P alarm. Station C reports the OCh-FDI-P or OCh-SSF-P alarm
(for wavelengths between stations A and C).


The FIU board at station B reports the OTS-LOS-O alarm and the FIU board at station A
reports the OTS-BDI-O alarm. Station C reports the OCh-FDI-O alarm (for wavelengths
The FIU board at station B reports the OTS-TIM alarm and the FIU board at station A
reports the OTS-BDI alarm. Station C reports the OCh-FDI alarm (for wavelengths
The OM unit at station A is faulty.

The OD unit at station B reports the OMS-LOS-P alarm and the OM unit at station A
reports the OMS-BDI-P alarm. Station C reports the OCh-FDI-P alarm (for wavelengths

The OTU board at station B reports the OCh-LOS-P alarm (for wavelengths between
stations A and B). The OTU board at station C reports the OCh-LOS-P alarm (for
wavelengths between stations A and C).
The fiber from station B to station C is cut.

The FIU board at station C reports the OTS-LOS alarm and the FIU board at station B
At station B, the optical amplifier unit in direction B-to-C is faulty.

The FIU board at station C reports the OTS-LOS-P alarm and the FIU board at station B
reports the OTS-BDI-P alarm.
At station B, the optical amplifier in direction B-to-C loses input light.

The FIU board at station B inserts the OTS-PMI signal and the FIU board at station C
At station B, the fiber in direction SC1-to-FIU is cut.

The FIU board at station C reports the OTS-LOS-O alarm and the FIU board at station B
reports the OTS-BDI-O alarm.
The configuration of the TTI to be received at station C is inconsistent with the TTI
transmitted by station B.
The FIU board at station C reports the OTS-TIM alarm and the FIU board at station B
The OM unit at station B is faulty.

The OD unit at station C reports the OMS-LOS-P alarm and the OM unit at station B
reports the OMS-BDI-P alarm.
Issue 01 (2011-08-10)
Page 87 of 95
The OTU board at station B is faulty.

The OTU board at station C reports the OCh-LOS-P alarm (for wavelengths from station
B to station C).
Issue 01 (2011-08-10)
Page 88 of 95
Appendix II: OTN Protection
Objective
This chapter describes how to configure common protection and how protection is
implemented.
Intended Audience
Understanding how protection switching is triggered or implemented helps to correctly
configure common protection on WDM products.
Issue 01 (2011-08-10)
Page 89 of 95
7.1 Client-Side 1+1 Protection (OTU 1+1)

TI1
TO11
RI11
RO1
TO21
RI21
SCS TO12
RI12
TI2
TO22
RI22
RO2
OM
OTU1
OD
FIU
OTU1
FIU
RI11
TO11
RO1
TI1
OD
OM
RI21
TO21
OM
OD
RI12
TO12
OTU2
FIU
FIU
OD
Working signal flow
OTU2
OM
SCS
RI22
TO22
RO2
TI2
Protection signal flow
A DCM is embedded in a board.The boards on the working and

protection channels preset dispersion compensation according to
channel status to ensure protection switching time of less than 50 ms.
Client-side 1+1 protection is costly but easy to configure. Currently, all
suppliers in the industry support client-side 1+1 protection.
7.2 Optical Line Protection (OLP)
Issue 01 (2011-08-10)
Page 90 of 95
7.3 ODUk SNCP (OTN 1+1 Channel Protection)
Switching Reversion Process
Issue 01 (2011-08-10)
Page 91 of 95
Switching Trigger Condition
Table 7-1 Trigger conditions of ODUk SNCP protection

Default SF Trigger Condition
SD Trigger Condition
Alarm
conditions
common to
SNC/I,
SNC/N, and
SNC/S
LOS, LOC, OTU-LOF, OTU-LOM, OTU-AIS, ODU-AIS,

ODU-LCK, ODU-OCI, OTU-TIM, ODU- TIM,
ODU-TCM-TIM
OTU-DEG, OTU-EXC,
ODU-DEG, ODU-EXC
Configuration
requirement
for SNC/I
For SNC/I, there are no requirements on OTN overhead settings.
Alarm
conditions
exclusive to
SNC/S
ODU-TCM-OCI, ODU-TCM-LCK, ODU-TCM-AIS
OTU-TIM, ODU-TIM, and ODU-TCM-TIM are functional only when TIM subsequent
response is enabled for the NS2 and ND2 boards under protection.
ODU-TCM-DEG,
ODU-TCM-EXC
ODU-TCM-OCI, ODU-TCM-LCK, and ODU-TCM-AIS are functional only when the

protection layer is TCM and the sink TCM mode of a channel at relevant optical interfaces
with protection is transparent transmission.
ODU-TCM-LTC is functional only when the protection layer is TCMn and LTC subsequent
response is enabled for the TCMn section of ODU1 on the NS2 and ND2 boards under
protection.
Configuration
requirement
for SNC/S
To configure SNC/S, set the sink mode of TCM overheads at the layer of a channel to
"operation mode" and enable the sink, when setting OTN overheads for the source NS2 and
ND2 boards.
Alarm
conditions
exclusive to
ODU-LOFLOM, ODU-TCM-OCI,
ODU-TCM-LCK, ODU-TCM-AIS,
ODU-TCM-LTC
Issue 01 (2011-08-10)
ODU-TCM-DEG, ODU-TCM-EXC
Page 92 of 95
Default SF Trigger Condition

SNC/N
SD Trigger Condition
ODU-PM-AIS, ODU-PM-LCK, ODU-PM-OCI, ODU-PM-DEG, and ODU-PM-EXC are

functional only when non-intrusive monitoring is enabled for the PM layer of an OTU board
under protection.
ODU-TCM-OCI, ODU-TCM-LCK, and ODU-TCM-AIS are functional only when the
protection layer is TCM and the sink TCM mode of a channel at relevant optical interfaces
with protection is transparent transmission.
ODU-TCM-LTC is functional only when the protection layer is TCMn and LTC subsequent
response is enabled for the TCMn section of ODU1 on the NS2 and ND2 boards under
protection.
Configuration
requirement
for SNC/N
To configure protection at the PM layer, enable non-intrusive monitoring for the PM

overheads in a channel at the source NS2 and ND2 boards.
To configure protection at the TCM layer, set the sink mode of TCM overheads on a channel
to transparent transmission, and enable the sink and non-intrusive monitoring when setting
TCM overheads for the source NS2 and ND2 boards.
Issue 01 (2011-08-10)
Page 93 of 95
Appendix III: Wavelength and Frequency

Allocation Table
Table 8-1 Wavelength and frequency allocation table (OptiX OSN 6800A and OptiX OSN 8800)
No
Central
Frequency
(THz)
Central
Wavelength
(nm)
No.
Central
Frequency
(THz)
Central
Wavelength
(nm)
196.05
1529.163
41
194.05
1544.924
196
1529.553
42
194
1545.322
195.95
1529.944
43
193.95
1545.72
195.9
1530.334
44
193.9
1546.119
195.85
1530.725
45
193.85
1546.518
195.8
1531.116
46
193.8
1546.917
195.75
1531.507
47
193.75
1547.316
195.7
1531.898
48
193.7
1547.715
195.65
1532.29
49
193.65
1548.115
10
195.6
1532.681
50
193.6
1548.515
11
195.55
1533.073
51
193.55
1548.915
12
195.5
1533.465
52
193.5
1549.315
13
195.45
1533.858
53
193.45
1549.715
14
195.4
1534.25
54
193.4
1550.116
15
195.35
1534.643
55
193.35
1550.517
16
195.3
1535.036
56
193.3
1550.918
17
195.25
1535.429
57
193.25
1551.319
18
195.2
1535.822
58
193.2
1551.721
Issue 01 (2011-08-10)
Page 94 of 95
No
Central
Frequency
(THz)
Central
Wavelength
(nm)
No.
Central
Frequency
(THz)
Central
Wavelength
(nm)
19
195.15
1536.216
59
193.15
1552.122
20
195.1
1536.609
60
193.1
1552.524
21
195.05
1537.003
61
193.05
1552.926
22
195
1537.397
62
193
1553.329
23
194.95
1537.792
63
192.95
1553.731
24
194.9
1538.186
64
192.9
1554.134
25
194.85
1538.581
65
192.85
1554.537
26
194.8
1538.976
66
192.8
1554.94
27
194.75
1539.371
67
192.75
1555.343
28
194.7
1539.766
68
192.7
1555.747
29
194.65
1540.162
69
192.65
1556.151
30
194.6
1540.557
70
192.6
1556.555
31
194.55
1540.953
71
192.55
1556.959
32
194.5
1541.349
72
192.5
1557.363
33
194.45
1541.746
73
192.45
1557.768
34
194.4
1542.142
74
192.4
1558.173
35
194.35
1542.539
75
192.35
1558.578
36
194.3
1542.936
76
192.3
1558.983
37
194.25
1543.333
77
192.25
1559.389
38
194.2
1543.73
78
192.2
1559.794
39
194.15
1544.128
79
192.15
1560.2
40
194.1
1544.526
80
192.1
1560.606
Issue 01 (2011-08-10)
Page 95 of 95

Huawei Optical Network Maintenance Reference NA-20110812-C

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Huawei Optical Network Maintenance Reference NA-20110812-C

Transféré par

Droits d'auteur :

Formats disponibles

Huawei Optical Network

Huawei Technologies Co., Ltd.

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Copyright Huawei Technologies Co., Ltd. 2011. All rights reserved.

Trademarks and Permissions

Huawei Optical Network Maintenance Reference_NA- WDM

3 Guidelines for Identifying WDM Faults................................................................................ 16

4 Guide to Emergency Fault Handling ...................................................................................... 24

Huawei Proprietary and Confidential

Huawei Optical Network Maintenance Reference_NA- WDM

5 Identifying Faults in Interconnection Between WDM and Other Products ................... 60

6 Appendix I: WDM Alarm Signal Flow ................................................................................... 64

7 Appendix II: OTN Protection ................................................................................................... 89

8 Appendix III: Wavelength and Frequency Allocation Table ............................................. 94

Huawei Proprietary and Confidential

Huawei Optical Network Maintenance Reference_NA- WDM

Huawei Proprietary and Confidential

Huawei Optical Network Maintenance Reference_NA- WDM

Huawei Proprietary and Confidential

Huawei Optical Network Maintenance Reference_NA- WDM

This maintenance collection provides guidelines to assist maintenance personnel with

SOP for Routine Maintenance of WDM Products

Guidelines for Identifying WDM Faults

Guide to Emergency Fault Handling

Identifying Faults in Interconnection Between WDM and Other Products

Appendix I: WDM Alarm Signal Flow

Appendix II: OTN Protection

Appendix III: Wavelength and Frequency Allocation Table

Huawei Proprietary and Confidential

Huawei Optical Network Maintenance Reference_NA- WDM

SOP for Routine Maintenance of WDM

Orientation of maintenance SOP: By performing standard operations during routine

Huawei Proprietary and Confidential

Huawei Optical Network Maintenance Reference_NA- WDM

Obtain network information and update changes

Update the network design PPT

Obtain special network configurations, for

Identify equipment that is connected to

Obtain engineering design documents,

Obtain the NMS managed objects (MOs)

Obtain the historical preventive

Obtain the manufacturer information of

Collect the version information (patch

Check whether the site version is

Contact Huawei engineers to prepare

Huawei Proprietary and Confidential

Huawei Optical Network Maintenance Reference_NA- WDM

Apply for account names and passwords for

Obtain the Release Notes for the required

Collect information about existing boards on a

Verify automatic alarm reporting is

Check NE alarms and ensure that no

Clear all alarms on the live network. If an

Verify that performance monitoring is

Check the transmit and receive optical

Check performance of OTU boards, line

Check service data and ensure that there

Huawei Proprietary and Confidential

Huawei Optical Network Maintenance Reference_NA- WDM

Check the ambient temperature inside the

Ensure that the equipment surface and

Ensure that there are no signs of rodents or

Check the working status of each service