OptiX OSN 8800 6800 3800 Troubleshooting (V100R007)

OptiX OSN 8800/6800/3800
V100R007C00
Troubleshooting
Issue 05
Date 2013-11-30
HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2013. 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 purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
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, express or implied.

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
Issue 05 (2013-11-30) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
i
About This Document
Related Versions
The following table lists the product versions related to this document.
Product Name Version
OptiX OSN 8800 V100R007C00
iManager U2000 V100R006C02
iManager U2000 Web LCT V100R006C02

Intended Audience
The intended audiences of this document are:
l Field maintenance engineers
l Network monitoring engineers
l System maintenance engineers
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Indicates an imminently hazardous situation which, if not
avoided, will result in death or serious injury.
Indicates a potentially hazardous situation which, if not
avoided, could result in death or serious injury.
OptiX OSN 8800/6800/3800
Troubleshooting About This Document
ii
Symbol Description
avoided, may result in minor or moderate injury.
avoided, could result in equipment damage, data loss,
performance deterioration, or unanticipated results.
NOTICE is used to address practices not related to personal
injury.
Calls attention to important information, best practices and
tips.
NOTE is used to address information not related to personal
injury, equipment damage, and environment deterioration.

GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Convention Description
Boldface Buttons, menus, parameters, tabs, window, and dialog titles
are in boldface. For example, click OK.
> Multi-level menus are in boldface and separated by the ">"
signs. For example, choose File > Create > Folder.

Change History
Updates between document issues are cumulative. Therefore, the latest document issue contains
all updates made in previous issues.
Updates in Issue 05 (2013-11-30) Based on Product Version
V100R007C00
This issue is the fifth official release for V100R007C00. Compared with Issue 04, some bugs in
the manual are fixed.
OptiX OSN 8800/6800/3800
iii
V100R007C00
This issue is the forth official release for V100R007C00. Compared with Issue 03, updating of
the following content.
Update Description
Basic Concepts
and Methods of
Fault Locating
Updated "Test Frame": optimized application 2 of ethernet test frame.
Fault Location
Using TP-Assist
Updated the procedure of "Performing Intelligent Service Fault
Diagnosis for Ethernet Services".

V100R007C00
This issue is the third official release for V100R007C00. Compared with Issue 02 (2012-09-30),
updating of SPC200 is added. This issue has the following updates.
Update Description
Whole manual l Deleted "Description" in the Chapter "General Fault Handling Flow"
l Deleted "Information Collecting and Recording" "Technical
Support" "Latest Technical Documentation Obtaining" in the Chapter
"Fault Handling Flow"
l Deleted "Basic Rules for Locating Faults" in the Chapter "Basic
Concepts and Methods of Fault Locating".
l Deleted "Configuration Data Analysis" in the Chapter "Common
Methods of Locating Faults"
l Deleted "Related Information" in the Chapter "Rectifying Bit Errors"
l Deleted "Failure of Ringing of the Orderwire Phone Set upon
Incoming Calls Though the Calls Can Be Answered" in the Chapter
"Rectifying Orderwire Problems"
l "Frequent Resetting of the SCC Board" has been moved from "17
ECC Problems" to "10 NE Offline Problems".
l Added "Rectifying Coherent Board Faults".
Common
Methods of
Locating Fault
Updated "Test Frame", added 100G OTU board.

OptiX OSN 8800/6800/3800
iv
V100R007C00
This issue is the second official release for V100R007C00. Only the issue number is updated.
V100R007C00
First release for version V100R007C00. Compared with version V100R006C03, this issue has
the following updates.
Update Description
3.1 Common
Fault Isolation
Methods
Section "One-Click Data Collection" is added.
4 Fault Location
Using TP-Assist
Section "Fault Location Using TP-Assist" is added.
15 Packet
Service
Problems
Section "Rectifying Packet Service Problems" is added.
16 Ethernet
Problems
l Section "Common LAG Faults" is added.
l Section "Common MSTP Faults" is added.
17 ECC
Problems
l Section "FAQs for HWECC" is added.
l Section "Troubleshooting for Inband DCN" is added.

V100R006C03
The update of contents is described as follows:
Update Description
3.1 Common Fault Isolation
Methods
l 3.1.6 PRBS Test: Updated PRBS networking
applications.
l 3.1.8 Test Frame: Added the 40G service type and
the supported board.
l Added "One-Click Data Collection".
OptiX OSN 8800/6800/3800
v
Update Description
12 Automatic Switching
Failures
12.5 ODUk SNCP Protection: Updated the solution of
troubleshooting.
17 ECC Problems Added "FAQs for HWECC".

V100R006C03
Update Description
3.1 Common Fault Isolation
Methods
Section "Port Mirroring Analysis" is added.
Common fault diagnosis methods are optimized.
10.1 Unreachability of One NE
by the U2000
Causes and diagnosis methods for the fault are modified.
12.12 DLAG Protection Changed "Automatic Switching Failure of DLAG
Protection (OTN)" to "Automatic Switching Failure of
DLAG Protection".
13.10 DLAG Protection Changed "Automatic Reverting Failure of DLAG
Protection (OTN)" to "Automatic Reverting Failure of
DLAG Protection".
Automatic Switching Failure of
DLAG Protection(OCS)
Automatic Reverting Failure of
DLAG Protection(OCS)
Section are deleted.
14.4 IPA End Failure in a
Raman System
Causes and diagnosis methods for the fault are added.

V100R006C03
Some bugs in the manual are fixed.
OptiX OSN 8800/6800/3800
vi
V100R006C01
V100R006C01
V100R006C00
V100R006C00
Update Description
12.16 Inter-
Subrack
Communication
Protection
Section "Automatic Switching Failure of Inter-Subrack Communication
Protection" is added.

V100R005C00
This issue is the first official release for OptiX OSN 8800/6800/3800 V100R005C00. In this
release, the manuals for OptiX OSN 8800 V100R002C02, OptiX OSN 6800 V100R004C04,
and OptiX OSN 3800 V100R004C04 are combined into one manual. Compared with the
combined manual, this issue has the following updates.
OptiX OSN 8800/6800/3800
vii
Update Description
Entire manual This manual provides descriptions according to product series OptiX
OSN 8800, OptiX OSN 6800, and OptiX OSN 3800. Any difference
between the products is described in the manual.
11 Board Offline
Problems
Section "Rectifying Board Offline Problems" is added.
16 Ethernet
Problems
Section "Service Interruption" is deleted.
OptiX OSN 8800/6800/3800
viii
Contents
About This Document.....................................................................................................................ii
1 Overview.........................................................................................................................................1
1.1 Safety Precautions..........................................................................................................................................................2
1.1.1 Laser............................................................................................................................................................................2
1.1.2 Short Circuit................................................................................................................................................................4
1.1.3 ESD..............................................................................................................................................................................4
1.1.4 Working on Equipment with Power Applied..............................................................................................................6
1.1.5 Alarm and Safety Symbols..........................................................................................................................................6
1.2 Instruments and Tools....................................................................................................................................................7
1.3 Maintenance Personnel Qualifications...........................................................................................................................8
2 Troubleshooting Workflow.........................................................................................................9
2.1 General Troubleshooting..............................................................................................................................................10
2.1.1 Workflow...................................................................................................................................................................10
2.2 Emergency Troubleshooting.........................................................................................................................................12
2.2.1 Workflow...................................................................................................................................................................12
2.2.2 Description.................................................................................................................................................................15
3 Fault Isolation Basics..................................................................................................................22
3.1 Common Fault Isolation Methods................................................................................................................................24
3.1.1 Service Signal Flow Analysis....................................................................................................................................24
3.1.2 Alarm and Performance Analysis..............................................................................................................................26
3.1.3 Fault Analysis Using Test Instruments......................................................................................................................29
3.1.4 Loopback...................................................................................................................................................................31
3.1.5 Replacement..............................................................................................................................................................32
3.1.6 PRBS Test..................................................................................................................................................................33
3.1.7 Configuration Modification.......................................................................................................................................35
3.1.8 Test Frame.................................................................................................................................................................36
3.1.9 RMON Performance Analysis...................................................................................................................................41
3.1.10 Port Mirroring Analysis...........................................................................................................................................43
3.1.11 One-Click Data Collection......................................................................................................................................46
4 Fault Location Using TP-Assist.................................................................................................49
4.1 Fault Location Using IP Ping.......................................................................................................................................50
OptiX OSN 8800/6800/3800
Troubleshooting Contents
ix
4.2 E-LAN Service Loopback Detection............................................................................................................................52
4.3 Performing Intelligent Service Fault Diagnosis for Ethernet Services.........................................................................54
5 Service Interruptions..................................................................................................................56
5.1 Interruption of All Services..........................................................................................................................................58
5.2 Single-Channel Service Interruption on the Client Side..............................................................................................60
5.3 Single-Channel Service Interruption on the WDM Side..............................................................................................61
5.4 Service Interruption Caused by Human Misoperation.................................................................................................63
5.5 Service Interruptions Caused by Power Supply Failures.............................................................................................64
5.6 Service Interruptions Due to Grounding Fault.............................................................................................................66
5.7 Service Interruptions Due to Unfavorable Environmental Conditions.........................................................................67
5.8 Service Interruptions Due to Faulty Optical Fibers, Cables, or Connectors................................................................71
5.9 Service Interruptions Due to Inconsistency of Board Types or Board Settings...........................................................74
5.10 Service Interruptions on the VCTRUNK Port............................................................................................................75
5.11 Service Interruptions on a Single Ethernet Port.........................................................................................................77
5.12 Service Interruptions on All Ethernet Ports................................................................................................................79
5.13 Service Interruption Cases..........................................................................................................................................81
6 Transient Service Interruptions................................................................................................83
6.1 Transient Interruption of Main Path Services...............................................................................................................84
6.2 Transient Interruption of Single-Channel Services......................................................................................................85
6.3 Transient Service Interruptions on a Single VCTRUNK Port.....................................................................................87
6.4 Transient Service Interruptions on a Single Ethernet Port...........................................................................................93
6.5 Transient Service Interruptions Due to Protocol Related Causes.................................................................................97
6.6 Transient Interruption Cases.......................................................................................................................................100
7 Optical Power Abnormity........................................................................................................102
7.1 Abnormal Decline of the Optical Power....................................................................................................................103
7.2 Optical Power Abnormity Cases................................................................................................................................104
8 Bit Errors......................................................................................................................................106
8.1 Multi-Channel Bit Errors............................................................................................................................................107
8.2 Single-Channel Bit Errors..........................................................................................................................................109
8.3 Bit Errors Due to Unfavorable Environmental Conditions........................................................................................111
8.4 Bit Errors Due to Device Faults.................................................................................................................................115
8.5 Bit Error Cases............................................................................................................................................................117
9 A Fault in Pointer Justification...............................................................................................118
9.1 Pointer Justification Due to Incorrect Clock Configuration.......................................................................................119
9.2 Pointer Justification Due to Over-High Temperature and Humidity..........................................................................120
9.3 Pointer Justification Due to Over-Low Precision of the External Clock Source.......................................................121
10 NE Offline Problems..............................................................................................................123
10.1 Unreachability of One NE by the U2000.................................................................................................................124
10.2 Unreachability of All NEs in a Subnet by the U2000..............................................................................................125
OptiX OSN 8800/6800/3800
x
10.3 Frequent Unreachability of an NE by the U2000.....................................................................................................127
10.4 The System Control Board Is Frequently Reset.......................................................................................................128
10.5 NE Offline Cases......................................................................................................................................................129
11 Board Offline Problems......................................................................................................... 130
11.1 A Board Is Offline....................................................................................................................................................131
11.2 Multiple Boards Are Offline.....................................................................................................................................131
12 Automatic Switching Failures...............................................................................................133
12.1 Optical Line Protection.............................................................................................................................................136
12.2 Intra-Board 1+1 Protection.......................................................................................................................................138
12.3 Client-side 1+1 Protection........................................................................................................................................141
12.4 SW SNCP Protection................................................................................................................................................143
12.5 ODUk SNCP Protection...........................................................................................................................................145
12.6 VLAN SNCP Protection...........................................................................................................................................149
12.7 Tributary SNCP Protection.......................................................................................................................................151
12.8 Automatic Switching Failure of DBPS Protection...................................................................................................155
12.9 Board 1+1 Protection................................................................................................................................................156
12.10 Ethernet Ring Protection........................................................................................................................................157
12.11 MS SNCP Protection..............................................................................................................................................159
12.12 DLAG Protection....................................................................................................................................................162
12.13 Board-Level Protection...........................................................................................................................................163
12.14 ODUk SPRing Protection.......................................................................................................................................165
12.15 Optical Wavelength Shared Protection...................................................................................................................168
12.16 Inter-Subrack Communication Protection..............................................................................................................171
12.17 Linear Multiplex Section Protection.......................................................................................................................171
12.18 MSP Ring...............................................................................................................................................................174
12.19 Transoceanic MSP Ring.........................................................................................................................................176
12.20 SNCP......................................................................................................................................................................178
12.21 SNCTP....................................................................................................................................................................180
12.22 Protection Cases.....................................................................................................................................................182
13 Automatic Reverting Failures............................................................................................... 184
13.1 Optical Line Protection.............................................................................................................................................187
13.2 Intra-Board 1+1 Protection.......................................................................................................................................189
13.3 Client-side 1+1 Protection........................................................................................................................................191
13.4 SW SNCP Protection................................................................................................................................................193
13.5 ODUk SNCP Protection...........................................................................................................................................195
13.6 VLAN SNCP Protection...........................................................................................................................................197
13.7 Tributary SNCP Protection.......................................................................................................................................200
13.8 Ethernet Ring Protection..........................................................................................................................................202
13.9 MS SNCP Protection................................................................................................................................................203
13.10 DLAG Protection....................................................................................................................................................205
OptiX OSN 8800/6800/3800
xi
13.11 ODUk SPRing Protection.......................................................................................................................................207
13.12 Optical Wavelength Shared Protection...................................................................................................................209
13.13 Linear Multiplex Section Protection.......................................................................................................................211
13.14 MSP Ring...............................................................................................................................................................212
13.15 Transoceanic Ring MS Protection..........................................................................................................................213
13.16 SNCP......................................................................................................................................................................214
13.17 SNCTP....................................................................................................................................................................215
13.18 Protection Cases.....................................................................................................................................................216
14 Optical Power Management Problems................................................................................219
14.1 IPA Start Failure.......................................................................................................................................................220
14.2 IPA End Failure........................................................................................................................................................222
14.3 IPA Start Failure in a Raman System.......................................................................................................................224
14.4 IPA End Failure in a Raman System........................................................................................................................228
14.5 ALC Start Failure.....................................................................................................................................................232
14.6 APE Exceptions........................................................................................................................................................234
14.7 Handling Anomalies in the OPA Function...............................................................................................................237
14.8 Optical Power Management Cases...........................................................................................................................237
14.8.1 Automatic Power Equilibrium (APE)....................................................................................................................238
14.8.2 Automatic Level Control (ALC)...........................................................................................................................238
14.8.3 Intelligent Power Adjustment (IPA)......................................................................................................................238
14.8.4 Intelligent Power Adjustment (IPA) of Raman System........................................................................................238
15 Packet Service Problems........................................................................................................240
15.1 Handling MPLS Tunnel Faults.................................................................................................................................241
15.2 Handling PW Faults..................................................................................................................................................242
15.3 Native Ethernet Service Troubleshooting.................................................................................................................243
15.4 PWE3 Ethernet Service Troubleshooting.................................................................................................................245
15.5 Tunnel APS Troubleshooting...................................................................................................................................247
16 Ethernet Problems...................................................................................................................250
16.1 Service Degradation.................................................................................................................................................251
16.2 LCAS Startup Failure...............................................................................................................................................252
16.3 LPT Switching Failure..............................................................................................................................................255
16.4 LB Test Failure.........................................................................................................................................................255
16.5 Test Frames Unavailability.......................................................................................................................................259
16.6 Common LAG faults................................................................................................................................................259
16.7 Common MSTP faults..............................................................................................................................................262
16.8 Ethernet Service Cases.............................................................................................................................................265
17 ECC Problems...........................................................................................................................266
17.1 ECC Communication Interruption............................................................................................................................267
17.2 Intermittent ECC Communication............................................................................................................................268
17.3 HWECC FAQ...........................................................................................................................................................269
OptiX OSN 8800/6800/3800
xii
17.4 Troubleshooting for Inband DCN.............................................................................................................................270
17.5 ECC Cases................................................................................................................................................................273
18 Clock Problems........................................................................................................................275
18.1 Failure of NodeBs to Trace Clock Signals...............................................................................................................276
18.2 Synchronization Failure of the Physical-Layer Clock..............................................................................................277
19 Orderwire Problems................................................................................................................280
19.1 Orderwire Failure.....................................................................................................................................................281
19.2 A Called Phone Set Cannot Exit the Conference Call State.....................................................................................282
19.3 Orderwire Cases.......................................................................................................................................................283
20 Coherent Board Faults............................................................................................................284
21 Interconnection Faults............................................................................................................287
21.1 Failure in Intercommunication with the Data Equipment........................................................................................288
21.2 Failure in Intercommunication with the SDH Equipment........................................................................................289
21.3 WDM and other OTN Equipment Interconnection Failures....................................................................................291
21.4 Equipment Interconnection Cases............................................................................................................................292
A Remote Maintenance Guide...................................................................................................294
A.1 Overview....................................................................................................................................................................295
A.2 Enabling Remote Maintenance User.........................................................................................................................295
A.3 Creating Remote Maintenance..................................................................................................................................296
B Glossary......................................................................................................................................298
OptiX OSN 8800/6800/3800
xiii
1 Overview
About This Chapter
This topic describes safety precautions, introduces essential instruments and tools, and outlines
maintenance personnel training requirements necessary for troubleshooting.
1.1 Safety Precautions
This section describes the safety operation guidelines. It contains personal safety guidelines and
equipment operating guidelines. These guidelines must be strictly followed to avoid any injury
to human body or damage to equipment during equipment operation.
1.2 Instruments and Tools
This topic introduces the essential instruments and tools necessary for troubleshooting.
1.3 Maintenance Personnel Qualifications
To quickly and accurately locate and resolve a fault in the optical transport system, maintenance
personnel must have sufficient background knowledge and service skills and be familiar with
the network and the equipment used. This topic outlines the skills and knowledge that
maintenance personnel require for troubleshooting the OptiX OSN equipment.
OptiX OSN 8800/6800/3800
Troubleshooting 1 Overview
1
1.1 Safety Precautions
This section describes the safety operation guidelines. It contains personal safety guidelines and
equipment operating guidelines. These guidelines must be strictly followed to avoid any injury
to human body or damage to equipment during equipment operation.
1.1.1 Laser
When you install and maintain equipment, follow the safety precautions described below to help
prevent personal injury or equipment damage. The laser complies with IEC60825.
The safety precautions of lasers consist of two parts:
l Personal injury
l Equipment damage
Personal Injury
DANGER
Laser beams from the optical ports on boards or from the fiber connectors cause eye damage.
Do not look directly at the optical ports or fiber connectors during the installation and
maintenance of boards or fibers. Do not shine laser beams into the eyes of other workers.
DANGER
To prevent eye damage in the case of an optical port that is in use, use protective caps to cover
the optical interface and the fiber connector after you remove the fiber from the optical interface.
DANGER
The optical power of the LINE interface on the Raman amplifier board is very high. Shut down
the pump laser before you insert or remove fiber connectors on the Raman amplifier board to
help prevent personal injury that is caused by high optical power.
OptiX OSN 8800/6800/3800
2
Equipment Damage
CAUTION
Use protective caps to cover unused optical ports and fiber connectors so that they do not gather
dust.
CAUTION
When performing a hardware loopback test on optical ports using a fiber, add an optical
attenuator to prevent damage to the equipment because of the high power of the laser beam. Add
the attenuator at the receive optical port on a board that supports optical attenuators.
CAUTION
When you use the optical time domain reflectometer (OTDR), disconnect the fiber between the
opposite station and the board to prevent damage to the receive optical module because of high
optical power.
CAUTION
Exercise caution when you remove or insert a board that is connected with fibers.
OptiX OSN 8800/6800/3800
3
CAUTION
The optical power of the Raman amplifier board is very high. Observe the following precautions
when using the Raman amplifier board to prevent damage to the equipment.
l Do not use fiber connectors within 020 km. The fibers at every joint point must be spliced.
l The single-point additional loss within 010 km must be smaller than 0.1 dB (G.652) or
0.2 dB (G.655) and the single-point return loss must not be smaller than 40 dB.
l The single-point additional loss within 1020 km must be smaller than 0.2 dB (G.652) or
0.4 dB (G.655) and the single-point return loss must not be smaller than 40 dB.
l Fiber connections must be complete before you enable the lasers on the Raman amplifier
board. Make sure that the fiber connectors are clean. Otherwise, the fiber connectors might
be damaged when you insert or remove the fiber connectors.
l The optical power of the LINE interface on the Raman amplifier board is very high. The
LSH/APC optical connectors must be used in the fiber that is connected to the LINE
interface.
l For the Raman amplifier board with backward pump, the strong pump light enters the fiber
through the input end (LINE) instead of the output end (SYS). Do not add boards or non-
fiber devices, such as attenuators or fiber jumpers, at the input end.
l The bent radius of the fiber that is connected to the LINE interface on the Raman amplifier
board must be larger than 30 mm to prevent the fiber from being burned.
1.1.2 Short Circuit
Exercise caution where you place metallic tools so that you do not cause a short circuit in any
equipment.
CAUTION
Do not place tools, such as screwdrivers, on the air baffle.
CAUTION
Ensure that screws do not fall off into the subrack or chassis.
1.1.3 ESD
During installation and maintenance, follow ESD procedures to prevent equipment damage:
l Always wear an ESD wrist strap during the operation.
l Check that the equipment is securely grounded.
OptiX OSN 8800/6800/3800
4
CAUTION
Wear a well-grounded ESD wrist strap whenever you touch equipment or boards. Make sure
that the wrist strap touches your skin. Insert the ESD strap connector into the ESD socket of the
equipment.
For information about how to wear an ESD wrist strap, see Figure 1-1.
Figure 1-1 Wearing an ESD wrist strap

NOTE
Insert the connector of the ESD strap into the equipment port. For details, see the Quick Installation Guide.
When you are following ESD procedures, take the following precautions:
l Check the validity and functionality of the wrist strap. Its resistance value must be between
0.75 mega ohm to 10 mega ohm. If the wrist strap validity period (usually two years) has
expired, or if the resistance value fails to meet requirements, replace it with a wrist strap
that provides the required resistance value.
l Do not touch a board with your clothing. Clothing generates static electricity that is not
protected by the wrist strap.
l Wear an ESD wrist strap and place the board on an ESD pad when you replace boards or
chips. Use ESD tweezers or extraction tools to replace chips. Do not touch chips, circuits,
or pins with your bare hands.
l Keep the boards and other ESD-sensitive parts you are installing in ESD bags. Place the
removed boards and components on an ESD pad or ESD material. Do not use non-antistatic
materials such as white foams, common plastic bags, or paper bags to pack boards, and do
not let these materials touch the boards.
l Wear an ESD wrist strap when operating the ports of boards because they are also ESD-
sensitive. Discharge the static electricity of cables and protective sleeves before you connect
them to the ports.
OptiX OSN 8800/6800/3800
5
l Keep packing materials (such as, ESD boxes and bags) available in the equipment room
for packing boards in the future.
ESD complies with IEC Publication 1000, EN 55022, EN 55024, IEC 61000 and GR-1089-
CORE.
1.1.4 Working on Equipment with Power Applied
When you perform operations on the equipment when power is applied, ensure that you take the
safety precautions to prevent personal injury or equipment damage.
DANGER
Do not install or disassemble equipment when power is applied.
1.1.5 Alarm and Safety Symbols
During equipment installation and maintenance, observe the precautions indicated by the alarm
and safety symbols to help prevent personal injury or equipment damage.
Table 1-1 describes the alarm and safety symbols on the WDM equipment.
Table 1-1 Symbols on the WDM equipment
Symbol Describes
ESD protection symbol.
You must wear an ESD wrist strap or glove to avoid
damage caused by electrostatic discharge to boards.
HAZARDLEVEL 1MINVISIBLE
LASERRADIATION
DONOT VIEWDIRECTLYWITH
NON-ATTENUATINGOPTICAL
INSTRUMENTS
CAUTION
Laser level symbol.
Indicates the laser level and warns that laser beams
can cause injuries to eyes.
Grounding symbol.
Indicates the position of the grounding point.
Regular cleaning symbol.
Warns you to regularly clean the air filter.
OptiX OSN 8800/6800/3800
6
Symbol Describes
Fan warning symbol.
Warns you not to touch the fan blade until the fan
stops moving.

1.2 Instruments and Tools
This topic introduces the essential instruments and tools necessary for troubleshooting.
Table 1-2 lists the instruments and tools used for troubleshooting.
Table 1-2 Instruments and tools used for troubleshooting
Name Usage
Optical power meter
Fiber patch cord
Tests the optical power of optical ports.
Attenuator Attenuates the receive optical power.
Optical spectrum analyzer Tests the system index.
Optical time-domain
reflectometer
Detects optical cable faults.
Adjustment pin Adjusts mechanical variable optical attenuators (VOAs).
Fiberscope Checks whether the optical fiber end faces are clean.
ESD wrist strip Protects sensitive components against static generated by the
human body.
ESD bag Safely stores static-sensitive components.
ESD uniform Protects sensitive components against static generated by the
human body.
Phillips screwdriver Tightens and loosens screws on boards.
Cassette cleaner Cleans optical fiber end faces.
Dust-free cloth Cleans optical fiber heads.
Special cleaning solvent
(Isopropyl alcohol is
preferred to propyl alcohol)
Cleans optical fibers and flanges.
Special compressed gas Cleans boards and optical ports.
U2000 Software used to configure and issue commands to boards
Web LCT Software used to configure and issue commands to boards
OptiX OSN 8800/6800/3800
7
Name Usage
Label Labels the replacement pigtails.
Fiber binding strap Binds the replacement pigtails.

1.3 Maintenance Personnel Qualifications
To quickly and accurately locate and resolve a fault in the optical transport system, maintenance
personnel must have sufficient background knowledge and service skills and be familiar with
the network and the equipment used. This topic outlines the skills and knowledge that
maintenance personnel require for troubleshooting the OptiX OSN equipment.
Background Knowledge
l WDM fundamentals
l The WDM system alarm generation mechanism
l Troubleshooting methods for common alarms
Basic Operations
l Basic transmission equipment operations
l Basic network management system (NMS) operations
For basic NMS operations, refer to the OptiX iManager U2000 Operator Guide or the on-line
help.
Common Test Instruments
Commonly needed transmission system test instruments include optical power meter, SDH/
SONET tester, SmartBits tester, optical spectrum analyzer, OTDR and communication signal
analyzer. Refer to the respective operator guide for more information.
Network Layout
The network layout of the project
The service configuration, wavelength assignment, optical distribution frame (ODF), fiber
routing, board version, and equipment layout in each office.
The current equipment running status in local office
The relevant engineering files and documents (which need to be updated periodically)
On-Site Data Collection
This process includes periodic data collection both when the equipment is running normally and
when faults occur. Before handling the fault, maintenance personnel should first collect and
store the on-site data. For more information about data collection, refer to "3.1.11 One-Click
Data Collection".
OptiX OSN 8800/6800/3800
8
2 Troubleshooting Workflow
About This Chapter
This topic describes the troubleshooting process, information collection, and how to obtain
additional technical support and the latest technical documentation.
2.1 General Troubleshooting
This topic describes how to handle general faults.
2.2 Emergency Troubleshooting
This topic describes how to handle emergencies.
OptiX OSN 8800/6800/3800
Troubleshooting 2 Troubleshooting Workflow
9
2.1 General Troubleshooting
2.1.1 Workflow
The following figure describes how to handle general faults.
OptiX OSN 8800/6800/3800
10
Figure 2-1 General troubleshooting flowchart
Start
Collect and record
information
External causes? Other handling process
Analyze and locate fault
Fault cleared?
Feed back to Huawei
Work out solutions
together
Try to solve
Observe the running
equipment
Fault cleared?
Summary and fill out
report
End
Service recovery?
Yes
Yes
No
No
No
No
Yes
Yes
OptiX OSN 8800/6800/3800
11

Fault Information Collection
The following information needs to be recorded:
l Fault occurrence time
l Operations performed before and after the occurrence of the fault
Additionally, other important data, such as alarm information and performance events on the
U2000, also needs to be saved.
External Faults
Handle faults caused by any of the following external factors:
l Power failure
l Optical cable fault
l Environment variable (for example, telecommunications room temperature)
l Terminal equipment
Technical Support
Contact Huawei Customer Service Center (CSC) for assistance locating and resolving any issues
beyond the scope of this document.
You can also contact the technical support personnel in Huawei's local representative office in
either of the following ways:
l Hotline: 4008302118
l E-mail: support@huawei.com
Observation and Confirmation
After services are restored, observe services for 24 consecutive hours to confirm that the fault
has been resolved.
Troubleshooting Reports
After the fault is resolved, fill in the related troubleshooting report in a timely manner and
summarize how the fault was handled.
2.2 Emergency Troubleshooting
This topic describes how to handle emergencies.
2.2.1 Workflow
This topic describes emergency handling workflow.
The emergency handling flow refers to the fault handling flow when the service of the equipment
is interrupted due to external faults (such as power supply fault or fiber cut), misoperations, or
OptiX OSN 8800/6800/3800
12
software/hardware faults of the equipment. In the case of the OptiX WDM optical transmission
equipment, in addition to clearing the fault according to the troubleshooting flow, take other
emergency measures (such as providing standby channels) or ask for help in time to reduce the
service interruption duration. The emergency troubleshooting process refers to the
troubleshooting process when services on the equipment are interrupted due to external faults,
such as a power failure or damaged fiber cables, incorrect operations, or software/hardware faults
of the equipment. For the OptiX WDM optical transmission equipment, in addition to clearing
the fault according to the troubleshooting process, take other emergency measures, such as
providing standby channels, or ask for help in time to reduce the duration of service interruption.
CAUTION
When handling service interruptions or other emergencies, note the following points:
l Restore services as soon as possible. If a backup channel is available, switch services to the
backup channel.
l Analyze the fault symptoms first, find the causes, and handle the fault.
l When you fail to resolve a fault, contact Huawei technical support to troubleshoot the fault
and minimize the duration of service interruption.
l During the handling process, record and save the original fault data.
OptiX OSN 8800/6800/3800
13
Figure 2-2 Emergency troubleshooting flowchart 1
Start, a fault is reported
Yes
No
Yes
No
Yes
Have spare resources?
Yes
The
R_LOS/R_LOF/MUT_L
OS/IN_PWR-
LOW/PWR_HIGH/NE-
unreachable alarm
exists?
Locate the faulty
section along the signal
flow and confirm
whether the NE is
unreachable
The power
supply/optical cable
is faulty?
Yes
Yes
No
Check the
SCC/OA/MUX/DEMUX
board on site
All channels are
abnormal?
No
Handle
the
external
fault
The fault is cleared, end
Cancel the abnormal operation,
end
Query the bit error
performance and check
whether all channels have
excessive bit
errors
Yes
No
The BUS_ERR
alarm exists?
Yes
No
The
OTU_LOF/OTU_LOM/
ODU_LOF/ODU_LOM/
ODUk_PM_SSF/ODUk
_PM_BDI alarm
exists?
Yes
Yes
No
Replace the faulty
board
Yes
Check the bit error
performance and locate
the channel with
excessive bit errors
The system
OSNR/nonlinearity/fiber
jumper between the OTU
and MUX/DEMUX board
is faulty?
Handle the fiber
jumper/optical cable
fault
No
Check the
OTU/MUX/DEMUX board
Replace the faulty board
Yes
The fault is a system
fault, go to
The fault is a cross-
connect fault, go to
The fault is an
OTN/electrical layer
fault, go to
The fault is a single-
channel fault, go to
The fault is a multi-
channel fault, go to
Check alarms with the NMS 1
Adjust the affected services
to the backup resources, go
to 1
2
3
4
5
6
No
An abnormal operation
is performed?

OptiX OSN 8800/6800/3800
14
Figure 2-3 Emergency handling flow chart 2
a
The system OSNR or
nonlinearity is improper or
the fiber jumper/optical
cable is faulty?
No
Yes
Check the
OA/MUX/DEMUX
board at the
local/opposite end
Replace the faulty
board
Handle the fiber
jumper/optical cable
fault
The cross-connection
configuration is correct?
No
Yes
Modify the cross-
connection
configuration
Replace the faulty
tributary/line/cross-
connect board
The fiber
connections between
OTU/tributary/line
boards at the
local/opposite end
are normal?
No
Yes
Handle the fiber connection
fault
The
TD/TF/LSR_WILL_DI
alarm exists on the
OTU/line board at the
local end?
Yes
Replace the faulty
board at the local end
No
The
LSR_WILL_DIE/OUT_PWR_HIGH/
OUT_PWR/LOW alarm exists on
the OTU/line board at the opposite
end?
Replace the faulty
board at the opposite
end

the transmit and receive
optical power values are
abnormal?
Yes
boards at both the transmit
and receive ends
Compare the current
optical power of the OA/
MUX/DEMUX board with
the history normal value
No
The
OA/MUX/DEMUX
board is faulty?
Compare the current optical power of the
OTU/tributary/line board of the faulty
channel with the history normal value
The
OTU/tributary/line
board is faulty?
Replace the internal fiber
between the OTU and
MUX/DEMUX boards
Replace the faulty
board
Handle the fiber
jumper/optical cable fault
No
No
Yes Yes
Handle the fiber
jumper/optical cable fault
No
Replace the faulty board
Yes
Cross-connection fault
OTN/electrical
layer fault
Single-channel fault
Multi-channel fault
System fault 2 3
4
5
6
a: The fiber connection faults include the
inconsistency between the logical fiber
connection and the physical fiber connection,
and the physical fiber connection faults.
a
Both
faulty?
The
OA/MUX/DEMUX
are

2.2.2 Description
This topic describes the emergency troubleshooting process.
OptiX OSN 8800/6800/3800
15
Checking for Incorrect Operations
Check for incorrect operations performed on the equipment, such as loopback or manual laser
shutdown. If there are any, cancel them as required.
Restoring Services as Soon as Possible
When a fault occurs in the WDM system, services are interrupted. If a backup channel is
available, switch the services to the backup channel to restore the services as soon as possible
before you begin troubleshooting the fault.
Handling Alarms
l If an R_LOS, R_LOF, MUT_LOS, IN_PWR_HIGH, IN_PWR_LOW, or NE-unreachable
alarm is reported, check and analyze the alarm.
When such an alarm occurs, if the power supply or optical cable is faulty, handle these
faults first.
Determine whether the fault is a multi-channel or single-channel issue based on the the
range of services affected, and handle it accordingly.
If multiple channels are faulty, check the transmit/receive optical power and compare
the current optical power of the optical amplifier (OA)/multiplexer (MUX)/
demultiplexer (DEMUX) board with the historical normal value. Check the network
section by section to determine whether the line, pigtail, or OA/MUX/DEMUX board
is faulty. Then handle the line/pigtail fault or replace the board accordingly.
If only one channel is faulty, compare the current optical power of the optical
transponder unit (OTU)/tributary/line board on the faulty channel with the historical
normal value to determine whether the board or intra-board fiber connection is faulty.
Then replace the faulty board or change the internal fiber connections accordingly.
l If no R_LOS, R_LOF, MUT_LOS, IN_PWR_HIGH, IN_PWR_LOW, or NE-unreachable
alarm is reported, check the bit error rate (BER) performance or optical power performance
for any of the following problems.
If all channels have excessive bit errors, a system fault has occurred. Check the network
section by section along the signal flow to determine whether the system OSNR and
nonlinearity are correct and whether the pigtail/optical cable is faulty. If the system
OSNR and nonlinearity are incorrect and the pigtail/optical cable is faulty, handle the
pigtail/optical cable fault. If the pigtail/optical cable is functioning normally, the OA/
MUX/DEMUX board is faulty and should be replaced.
If the fault is not a system fault and the BUS_ERR alarm is reported, the fault is a cross-
connection fault. If the cross-connection configuration is incorrect, modify it to resolve
the fault. If it is correct, the tributary/line/cross-connect board is faulty and should be
replaced.
If the OTU_LOF/OTU_LOM/ODU_LOF/ODU_LOM/ODUk_PM_SSF/
ODUk_PM_BDI alarm is reported, the OTN/electrical layer is faulty. Check whether
the fiber connections between OTU boards, tributary boards, or line boards at the local
and opposite ends are faulty. If any of these is faulty, handle the fiber connection faults,
including the inconsistency between logical and physical fiber connections and physical
fiber connection faults.
If a TD/TF/LSR_WILL_DIE alarm is reported by an OTU/line board, the board is faulty
and should be replaced.
OptiX OSN 8800/6800/3800
16
TIP
As shown in the flowchart, optical-layer faults and fiber connection faults cause OTN alarms.
Therefore, these faults must be handled first. After these faults are cleared, OTN alarms will typically
clear also.
If you isolate the fault to a specific board, replace the board.
Table 2-1 lists common alarms and their causes for the OA, MUX, DEMUX or OTU/tributary/
line board.
Table 2-1 Common alarms and their causes
Board Type Alarm
a
Possible Cause Action
OA board MUT_LOS Power-related alarm
Possible cause:
The received signals are
abnormal.
Check whether the optical
power of the upstream
optical path and station is
normal.
PUM_BCM_A
LM
PUM_COOL_
EXC
Temperature-related alarm
Possible causes are as
follows:
l The fan is powered off.
l The ambient
temperature is too high
or too low.
l The board is faulty.
l Power on the fan.
l Adjust the ambient
temperature.
l Replace the faulty
board.
Optical
Multiplexer/
Demultiplexe
r Board
MUT_LOS Power-related alarm
Possible cause:
abnormal.
normal.
MODULE_CO
OLCUR_OVE
R,
MODULE_TE
MP_OVER
Temperature-related alarm.
follows:
l The ambient
temperature is too high.
l Power on the fan.
temperature.
board.
OTU/
tributary/line
board
R_LOS,
IN_PWR_LO
W,
IN_PWR_HIG
H
Power-related alarm
Possible cause:
abnormal.
normal.
OptiX OSN 8800/6800/3800
17
Board Type Alarm
a
Possible Cause Action
R_LOF,
B1_EXC,
B1_SD,
B2_EXC,
B2_SD
Power-related alarm
Possible cause:
abnormal.
If the module in the receive
end is faulty, these alarms
will also occur.
l Check whether the
optical power of the
upstream optical path
and station is normal.
l Check whether the
optical power of the
receive end is normal.
TF, TD,
OUT_PWR_L
OW,
OUT_PWR_HI
GH
Mainly related to the
transmit unit of the board. If
the optical module on the
board is pluggable, check
the module.
Check whether the
pluggable optical module
or the board is faulty.
LSR_COOL_A
LM,
LSR_WILL_DI
E
Temperature-related alarm
follows:
l The ambient
temperature is too high.
l The pluggable optical
module is faulty.
l Power on the fan.
temperature.
module.
board.

NOTE
a: Common alarms are listed by board type in the table. Alarms for different boards of the same type may
differ slightly.
In addition, there are various running and alarm indicators with different colors on the equipment.
The On/Off and flashing states of these indicators indicate the current running state or possible
alarm of the equipment. Such indication helps you analyze the cause of the fault and accordingly
handle the alarm. Refer to the Indicators.
OptiX OSN 8800/6800/3800
18
CAUTION
If you observe only the alarm indicators on the top of the cabinet, minor equipment alarms may
be missed (in the case of minor alarms, the alarm indicators on the top of the cabinet do not light
up, whereas the alarm indicators on the board do). In most cases, a minor alarm indicates a
potential fault at the local or opposite end. Such alarms cannot be neglected.
Equipment indicators indicate only the current operating status of the equipment, not the faults
that have already occurred and been cleared.
The indicator status that corresponds to a specific alarm category can be redefined on the U2000,
and certain alarm types can even be suppressed.
The board alarm indicator reports the alarm with the highest severity level detected by the board.
Isolating and Resolving External Faults
Before locating a fault in the system, identify and resolve external faults, including optical cable
or fiber faults, client equipment faults, and power failures.
l Troubleshooting a client equipment fault
To troubleshoot a fault on client equipment, use either of the following methods:
Method 1: Connect a bit error meter between the receive port and transmit port of the
OTU/tributary board and perform a bit error test. Use a pigtail to short-circuit the
transmit port of the corresponding OTU/tributary board at the opposite station to the
receive port of the corresponding OTU/tributary board. Check for bit errors for 24 hours.
If no bit error is detected, the fault is occurring on the client side.
CAUTION
Before short-circuiting the transmit port of the corresponding OTU/tributary board at
the opposite station to the receive port of the corresponding OTU/tributary board,
determine whether to add an optical attenuator to the receive optical port on the OTU/
tributary board. The appropriate optical attenuator is determined based on the optical
power specification on the transmit port of the OTU/tributary board. Otherwise, optical
power overload might damage the OTU/tributary board.
Method 2: For an OTU/tributary board that supports B1 bit error detection, compare
whether the RSES performance value of the OTU/tributary board at the local station is
the same as that at the opposite station. If they are the same, the system has no new bit
errors and is operating normally, which indicates that the fault is located on the client
side.
Method 3: If users check client equipment on site, they can perform a self-loop (an
optical attenuator is required) on the receive and transmit optical ports of the client
equipment to check the alarms on the equipment. If alarms persist or the bit error meter
still detects bit errors, the fault is occurring on the client side.
l Troubleshooting an optical cable fault
To troubleshoot an optical cable fault, use any of the following methods:
OptiX OSN 8800/6800/3800
19
Method 1: Test the input optical power of the local station and the output optical power
of the upstream station. If the difference between the two values (that is, the attenuation)
is less than the designated value, the optical cable is functioning normally; otherwise,
the optical cable is faulty.
Method 2: Check whether optical cable parameters such as the type and length meet the
design requirements. If not, the optical cable is faulty.
Method 3: If the optical cable meets design requirements, check whether the optical
cable connector is properly attached. Ensure that the connection is normal.
Method 4: Switch system services to the backup optical cable. If the alarm is cleared,
the optical cable is faulty.
Method 5: Use an OTDR to measure the optical power and determine whether the optical
cable is faulty. If the reflectance of the tested optical fiber core is less than 27 dB and
the attenuation of the fiber core is less than the designated value, the optical cable is
functioning normally. Otherwise, the optical cable is faulty. Note that the OTDR has a
blind spot within a short distance (smaller than 5 km), in which the test results are
inaccurate.
CAUTION
When you use the OTDR, separate the optical fiber from the equipment. Otherwise, the intense
OTDR light might damage the equipment.
l Troubleshooting a power supply fault
If you cannot log in to a station and all boards connected to the station report alarms indicating
input signal loss, the power supply of this station might be faulty. This causes a power failure
at this station and triggers the alarm. If this station suddenly enters an abnormal operating status,
the optical power of the station will suddenly decrease, some boards will operate abnormally,
services will be interrupted, and abnormal login will occur. Check whether the power supply
voltage of the transmission equipment is or a low-frequency transient voltage surge occurred.
l Troubleshooting a grounding fault
If the equipment is struck by lightning or cannot be interconnected, check the grounding. Check
whether the equipment is grounded in compliance with the specifications, whether any
equipment is disconnected from the public ground bar, and whether all types of equipment in
the same telecommunications room are grounded similarly. Then use an earth resistance tester
to test whether the grounding resistance and the potential between working and protection
grounds are within the permitted range.
Isolating and Resolving Optical Fiber or Board Faults
To troubleshoot an optical fiber or board fault, use any of the following methods:
l Method 1: Measure the input optical power of the board reporting the alarm and the output
optical power of the corresponding board at the opposite station.
If the transmit optical power of the corresponding board at the opposite station is normal
and the difference between the receive optical power of the board at the local station
OptiX OSN 8800/6800/3800
20
and the transmit optical power of the corresponding board at the opposite station is
greater than the designed value, the optical fiber is faulty.
If the transmit optical power of the corresponding board at the opposite station is too
low, the pluggable optical module on the board is faulty or the board is faulty.
l Method 2: Connect the board and optical meter using a new pigtail and measure the transmit
optical power of the board.
If the measured optical power is normal, the original optical fiber is faulty.
If the measured optical power is still too low, the pluggable optical module on the board
is faulty or the board is faulty.
OptiX OSN 8800/6800/3800
21
3 Fault Isolation Basics
About This Chapter
This topic describes the basic concepts and methods used to locate faults.
The key to locating faults is to pinpoint a fault to a single station.
The general fault isolation rules are as follows:
l Locate external faults first, followed by internal faults.
l Locate network faults first, followed by NE faults.
l Locate high-severity alarms first, followed by low-severity alarms.
l Locate multi-channel signal alarms first, followed by single-channel signal alarms.
l Locate bidirectional signal alarms first, followed by unidirectional signal alarms.
l Locate public alarms first, followed by individual alarms.
Locate External Faults First, Followed by Internal Faults
Before locating a fault, confirm that external conditions are normal. For example, no faults are
occurring in optical cables and fibers, client equipment, or power supply.
Locate Network Faults First, Followed by NE Faults
When a fault occurs on the transmission equipment, multiple stations, rather than a single station,
may be reporting alarms. Fault analysis is required to quickly and accurately determine the
station at which the fault occurs.
Locate High-severity Alarms First, Followed by Low-severity Alarms
First analyze high-severity alarms, including critical and major alarms. Then analyze low-
severity alarms, such as minor alarms and warnings.
OptiX OSN 8800/6800/3800
Troubleshooting 3 Fault Isolation Basics
22
Locate Multi-channel Signal Alarms First, Followed by Single-channel Signal
Alarms
When analyzing alarms, determine whether multiple channels are faulty or only a single channel
is faulty. If multiple channels are faulty, locate the fault to the multiplex section (MS). After the
fault of the MS is resolved, the single-channel alarm will be subsequently cleared.
Locate Bidirectional Signal Alarms first, Followed by Unidirectional Signal Alarms
When analyzing alarms, if alarms are present in both the local receive and opposite transmit
directions, check for similar faults in the opposite receive and local transmit directions. If alarms
are being reported in both directions, analyze and handle them first.
Locate Public Alarms First, Followed by Individual Alarms
When analyzing alarms, check whether they are public or individual alarms and determine the
scope of their impact. That is, determine whether one or more boards are reporting the alarms.
For a board with multiple optical ports, determine whether one, multiple, or all optical ports
have bit errors.
3.1 Common Fault Isolation Methods
This topic provides common fault isolation methods.
OptiX OSN 8800/6800/3800
23
3.1 Common Fault Isolation Methods
This topic provides common fault isolation methods.
Common methods for locating hardware faults can be briefly summarized as "First analyze, then
perform a loopback, and finally replace the board."
When a fault occurs, first analyze the signal flow, alarms, and performance event data to
determine the possible faulty station or optical section. Then measure the optical power section
by section, analyze the optical spectrum, and perform a loopback to isolate the fault to a specific
board. If the fault persists, replace the board or optical fiber.
3.1.1 Service Signal Flow Analysis
A common method for isolating faults is to check for faults along the signal flow, station by
station. This method allows you to quickly determine where the fault is occurring.
The following example describes service signal flow analysis.
Application 1: Each Station Uses Tributary and Line Boards
l Fault description:
Figure 3-1 shows the networking structure of this example. A channel of client services
from station A to station B is interrupted, and the client equipment at station B is either not
receiving optical signals or is receiving a large number of bit errors.
Figure 3-1 Signal flow analysis: Each station uses tributary and line boards
MUX OA OA DEMUX
MUX
DEMUX OA OA
Station A
Client
equipment
Station B
Client
equipment
Line
board
Tributary
board
Tributary
board
Line
board
Signal Flow Fault Point
NOTE
The U2000 provides the service signal flow interface. For details on how to view the service signal
flow using the GUIs, see "Viewing the Signal Flow Diagram for a WDM Trail" in the Online
Help.

l Fault analysis:
As shown in the preceding figure, the service signal flow of the client equipment at station
B is: client equipment at station A the tributary board at station A the cross-connect
board at station A the line board at station A MUX at station A OA at station A
OA at station B DEMUX at station B the line board at station B the cross-
connect board at station B the tributary board at station B client equipment at station
B.
Possible causes are as follows:
OptiX OSN 8800/6800/3800
24
The transmit unit of station A is faulty.
The optical path (including the optical fibers and fiber connectors) is faulty.
The receive unit of station B is faulty.
1. Analyze the alarms and performance of the tributary board at station A. If the client-
side port of this tributary board receives no optical signal or its receive optical power
is too low, the fault location can be refined to the transmit end of the client equipment
at station A, the pigtail from the client equipment to the tributary board, or the client-
side receive module of the tributary board.
2. If the client-side input optical power of the tributary board at station A is normal,
check whether the cross-connection configuration is correct. If it is correct, locate the
corresponding line board based on the cross-connection. Then, check the alarms and
performance events of the tributary and line boards at station B for BUS_ERR alarms.
If BUS_ERR alarms are reported, the fault may be occurring on the tributary, cross-
connect, or line board. If needed, you can change the configuration or replace the
related boards.
3. If no BUS_ERR alarms are reported, check whether the output optical power of the
line board is normal. If the optical power is abnormal, the fault is occurring on the line
board.
4. The remaining steps are similar to the fault analysis steps of a tributary/line integrated
board.
Application 2: Each Station Uses the OTU board
l Fault description:
Figure 3-2 shows the networking structure. A channel of client services from station A to
station B are interrupted, and the client equipment at station B receives no optical signals
or receives a large number of bit errors.
Figure 3-2 Each Station Uses the OTU board in Application 2
OTU
MUX OA
OA DEMUX OTU
MUX
DEMUX OA OA
Client
equipment
Client
equipment
Station A Station B
NOTE
The U2000 provides the service signal flow interface. For information on how to view the service
signal flow in GUIs, see "Viewing the Signal Flow Diagram for a WDM Trail" in the Online Help.

l Fault analysis:
The Client equipment at station B receives no optical signals or receives a large number of
bit errors. As shown in Figure 3-2, the service signal flow of the Client equipment at station
B is: Client equipment at station A OTU at station A MUX at station A OA at
OptiX OSN 8800/6800/3800
25
station A OA at station B DEMUX at station B OTU at station B Client
equipment at station B. Possible causes are as follows:
The transmit unit of station A is faulty.
The optical path (including the fibers and fiber connectors) is faulty.
The receive unit of station B is faulty.
1. Analyze the alarms and performance of the OTU at station A. If the client-side
interface of this OTU receives no optical signal or its received optical power is too
low, locate the fault to the transmit end of the Client equipment at station A, the fiber
jumper from the client equipment to the OTU, or the client side receiver module of
the OTU.
2. If the input optical power of the OTU at station A is normal, check whether its output
optical power is normal. If not, locate the fault to this OTU.
3. If the output optical power of the OTU at station A is also normal, observe whether
the optical power of the MUX at station A sharply changes. If there are many
wavelengths at station A, the loss of one of them does not results in a great change to
the optical power. Therefore, feed the signals at the MON port of the MUX to the
MCA board and query for any loss-of-wavelength alarm.
4. The key components on the MUX are passive; therefore, the MUX is not likely to be
damaged. When the MCA detects the loss of a wavelength, the most possible fault
point is between the fiber jumper from the OTU to the MUX.
5. The OA provides a function of input and output optical power detection. If the OA is
faulty, multiple wavelengths are affected. As a result, the possibility is rather low that
the OA board is faulty.
6. At station B, analyze the signal flow in this order: OA at station B DEMUX at
station B OTU at station B Client equipment at station B. The method to analyze
the signal flow at station B is similar to that of station A.
3.1.2 Alarm and Performance Analysis
When a fault occurs in the system, it is usually accompanied by a large number of alarms and
abnormal performance events. By analyzing this information, you can approximate the type and
location of the fault.
To review the alarms and performance events, do as follows:
l Query the current or historical alarms and performance events on the U2000.
l Review the running status or the severities of the alarms using the indicators on the open
rack and the boards.
The U2000 fault isolation capabilities can be affected by system faults, and are classified as
follows:
l Comprehensive: You are able to obtain fault information for the entire network.
l Accurate: You are able to obtain the current alarms, alarm generation time, and historical
alarms of the equipment. In addition, you are able to obtain the specific values of the
performance events.
l Complex: In some cases, a significantly high number of alarms and performance events
can make analysis very difficult.
OptiX OSN 8800/6800/3800
26
l Dependent: Fault isolation is entirely dependent on the normal operations of the computer,
software, and communication equipment. If any of these are faulty, fault isolation
capabilities may be limited or entirely lost.
CAUTION
l Before querying the performance data on the U2000, enable performance monitoring on the
U2000. Otherwise, the performance data will not be reported to the U2000.
l Before querying the alarm or performance data on the U2000, ensure that the running time
of each NE is correctly set. Otherwise, the alarm and performance data will be incorrect or
not reported to the U2000.
l During maintenance, after re-issuing the configuration to a NE, set the NE time to the current
time. Otherwise, the NE will operate at the incorrect default time.
The generation, detection, and transmission of an alarm varies with the OTU type and the type
of signals that the OTU receives. Alarm signal flow analysis allows you to quickly determine
where the fault is occurring.
Application 1: Alarm Signal Flow for a Non-convergence OTU Board to Process
SDH-compliant Signals
An R_LOS alarm generated by the OTU board at the local station is used as an example to
describe the alarm signal flow analysis when a non-convergent OTU board processes SONET/
SDH standard signals, as shown in Figure 3-3.
Figure 3-3 Alarm and performance analysis: A Non-convergence OTU board processes SDH-
compliant signals
OTU
MUX OA
OA DEMUX OTU
MUX
DEMUX OA OA
Client
equipment
Client
equipment
Station A Station B
NOTE
The automatic laser shutdown (ALS) function of the OTU board shown in the figure is disabled.

OptiX OSN 8800/6800/3800
27
Figure 3-4 Alarm and performance analysis: fault isolation
R_LOS
R_LOS
REM_SF R_LOF
Station B Client device
Client-side WDM-side WDM-side Client-side Client-device
Station A
xxx Detects and reports the xxx alarm.
Alarm processing

As shown in Figure 3-4, the client side of the OTU board at station A receives R_LOS signals.
The WDM side of this OTU board reports an R_LOS alarm and sends the fault information to
station B. The client side of the OTU board at station B reports the REM_SF alarm and sends
the fault information to the downstream client device. The client device then reports an
R_LOF alarm.
If the client-side OTU board at station A reports the R_LOS alarm to the U2000, the client-side
equipment at station B reports the R_LOF alarm. In this case, the input signals on the client side
of the OTU board at station A are abnormal. Therefore, if the input signals on the client side of
the OTU board at station A are abnormal, the client device is normal and the local device is
faulty.
Application 2: Alarm Signal Flow for a Non-convergence OTU Board to Process
OTN-compliant Signals
In this example, a non-convergence OTU board is used to describe how to locate a fault using
alarm signal flow analysis after an OTU2_LOF alarm is generated when the board is processing
OTN services. For other alarms, the fault analysis is similar. In Figure 3-5, ODU2 services are
transmitted on the line, and the optical fiber between station A and station B degrades.
Figure 3-5 Alarm and performance analysis: A non-convergence OTU board processes OTN-
compliant signals
OTU
OTM
OTU
OTM
OTU-E
OTM OTM
Client
equipment
Station A
OTU-W
Client
equipment
Station B Station C
NOTE
The ALS function of the OTU board shown in this figure is disabled.

OptiX OSN 8800/6800/3800
28
Figure 3-6 Alarm and performance analysis: fault isolation
Station B
OTUk_LOF/
OTUk_LOM/
OTUk_AIS
WDM-side WDM-side WDM-side
SF
Station A
SF: SF event detecting Alarm processing
xxx Detects and reports the xxx alarm or performance event
OTUk_LOF/
OTUk_LOM/
OTUk_AIS
ODUk_PM_AIS
OTUk_BDI
Station C
ODUk_PM_BDI
WDM-side
OTU-W OTU-E

As shown in Figure 3-6, when the optical fiber between station A and station B degrades, an
OTU2_LOF alarm is detected on the WDM side of the OTU-W at station B. After being
processed at station B, the OTU2_LOF alarm is transmitted to stations A and C. (If the optical
fiber is severely degraded, either an LOF or LOM alarm is generated. In this example, an LOF
alarm is generated.) At station C, an ODU2_PM_AIS alarm is detected on the WDM side of the
OTU board. After being processed at station C, the ODU2_PM_AIS alarm is transparently
transmitted to station B and then to station A. Then, station A reports OTU2_BDI and
ODU2_PM_BDI alarms.
If the WDM side of the OTU board at station A reports the OTU2_BDI and ODU2_PM_BDI
alarms to the U2000, the WDM side of the OTU-W board at station B reports the OTU2_LOF
alarm, and the WDM side of the OTU board at station C reports the ODU2_PM_AIS alarm. In
this case, the input signals on the WDM side of the OTU board at station B are abnormal. Further
analysis can be performed to determine whether the fault is caused by degraded optical fibers.
3.1.3 Fault Analysis Using Test Instruments
This method is used to resolve external transmission equipment problems or interconnection
problems. The test instruments must be available on site and maintenance personnel must have
been properly trained.
Overview
The most commonly used test instruments for the WDM system include the optical power meter,
optical spectrum analyzer, SDH/SONET tester, SmartBits tester, communication signal analyzer
and multimeter. Among these tools, the optical power meter and optical spectrum analyzer are
most often used.
OptiX OSN 8800/6800/3800
29
Application
l Optical power meter
The optical power of each point can be obtained from the U2000 performance data.
However, to get a precise reading for a specific point, you must measure the optical power
at that point using an optical power meter.
CAUTION
When the output optical power of the MUX boards, the input optical power of the DEMUX
boards, or the input and output optical power of the OA boards are abnormal, all services
are interrupted if the line is disconnected for testing. Therefore, do not disconnect the line
to test the optical power of the main-path signal unless absolutely necessary.
You can test the output optical power on the MON port of various boards. Use this tested
value and the ratio of the tested value to the optical power of the main-path signal to
calculate the optical power of the main-path signal.
l Optical spectrum analyzer
Use an optical spectrum analyzer to test the optical spectrum of the output signal on the
MON port of the board. Read from the spectrum analyzer the optical power, OSNR, central
wavelength and analyze the gain flatness of the OA. Compare this data with the original
data and check whether there is a significant performance deterioration (for the original
data, refer to the engineering documentation). Verify the following items:
Per-channel optical power is normal and the gain flatness is normal.
OSNR meets the design requirements.
Deviation of the central wavelength is lower than the specification.
NOTE
The main-path optical spectrum on the MON ports of boards can be tested online. If all the services
carried on the main path are affected, analyze the optical spectrum of the OA boards. If only one
service channel on the main path is affected, analyze the optical spectrum of the MUX and DEMUX
boards.
l SDH/SONET tester, SmartBits tester, and communication signal analyzer
If it is suspected that the poor interconnection is caused by signal error, use these analyzers
to check whether the frame signals and overhead bytes are normal, and check whether there
are any abnormal alarms.
l Multimeter
If it is suspected that the power supply is too high or too low, use a multimeter to measure
the input voltage.
If it is suspected that the poor interconnection is caused by improper grounding, use a
multimeter to measure the voltage between the shield layers of the coaxial ports at the
transmit and receive ends of interconnected channels. If the voltage is more than 0.5 V, the
grounding is improper.
OptiX OSN 8800/6800/3800
30
3.1.4 Loopback
The loopback method is the most common and effective method to locate a fault in a transport
network. The key feature of this method is that it does not require in-depth analysis of alarm and
performance information. Maintenance engineers should be familiar with this method.
There are software loopbacks and hardware loopbacks, which have the following advantages
and disadvantages:
l A hardware loopback is performed on a physical port (optical port) using an optical fiber.
Compared with the software loopback, the hardware loopback is more reliable. The
hardware loopback, however, requires on-site operations. In addition, a receive optical
power overload must be avoided when performing a hardware loopback.
l Compared with the hardware loopback, the software loopback is simpler but cannot locate
a fault as accurately. For example, during a single station test, if a software inloop is
performed on an optical port and the service is normal, the line board may not necessarily
be normal. However, if a selfloop is performed on the same optical port using a pigtail and
the service is normal, line board is normal.
For loopback configurations, refer to Performing Software Loopback and Performing Hardware
Loopback.
CAUTION
When performing a loopback on the optical path of the multiplex section, ensure that the OSNR
and dispersion meet the OTU requirements.
This method affects service quality. Therefore, it is generally used in deployment commissioning
or fault location in situations where services have been interrupted.
If the protection scheme has been configured, loopback is not recommended. Otherwise,
protection switching may fail. If a loopback is required, lock the protected services on the current
channel before performing the loopback, and unlock the services after the loopback is completed.
Application
The loopback method is applicable when the approximate range of the fault is known. The fault
is located by applying the loopback method on a section by section basis. This method clears
board and line faults. Figure 3-7 provides an example of fault isolation using the loopback
method.
Figure 3-7 Loopback method: fault isolation
Client
equipment
OTU MUX OA OA DEMUX OTU
MUX
DEMUX OA OA
Station A (OTM)
Inloop on
client side
Client
equipment
Station B (OTM)
OptiX OSN 8800/6800/3800
31

In Figure 3-7, the client side of the OTU at station A reports an R_LOS alarm whereas the
WDM side at station A reports no alarm. The WDM side and client sides of the OTU board at
station B report no alarms whereas the client equipment at station B reports an R_LOF alarm.
Perform an inloop on the client side of the OTU board at station A as shown in Figure 3-7.
l If the alarms at both stations A and B are cleared, the OTU board at station A is receiving
no signal from the client equipment at station A. The fault is occurring on the client
equipment at station A or the optical fiber from the client equipment at station A to the
OTU board at station A.
l If the alarms at stations A and B persist, the fault is occurring on the OTU board at station
A.
NOTE
l The faulty point can be identified quickly using the analysis method described in the "Alarm and
Performance Analysis" and analyzing the fault based on the alarm signal flow.
l If the system is capable of automatically releasing a loopback, the automatic loopback release period
can be changed or entirely disabled on the U2000. By default, the automatic loopback release period
is five minutes.
3.1.5 Replacement
In this method, a component suspected to be malfunctioning is replaced with a functional
component, in order to locate and resolve the fault. The component might be a section of pigtail,
a board, a flange, or an attenuator.
Application
The replacement method is used to resolve problems on external equipment, such as optical
fibers, flanges, client equipment, and power supply equipment. It is also used to handle faults
on boards or modules at a single station. Figure 3-8 and Figure 3-9 provide two examples.
The advantage of the replacement method is that the fault can be located within a small range,
and is a relatively simple procedure for maintenance personnel to perform. This method requires
that spare components be available. In addition, the operator must exercise caution when
performing operations. For example, when a board is being inserted or removed, careless
operations that could damage board components should be avoided.
Figure 3-8 Interchanging pigtails: fault isolation
Client
equipment
A
OTU
B

As shown in Figure 3-8, when the OTU or tributary board reports an R_LOS alarm on the client
side but the receive module of the client equipment reports no alarm, swap pigtails A and B. If
the R_LOS alarm persists, the transmit module of the client side or the receive module of the
OptiX OSN 8800/6800/3800
32
OTU or tributary board is faulty. If the R_LOS alarm is cleared but the client equipment reports
an R_LOS alarm, pigtail A is faulty.
CAUTION
Before performing the test, disable the automatic laser shutdown (ALS) function of the lasers
on the OTU or tributary board and the client equipment.
Figure 3-9 Replacing the board: fault isolation
Client
equipment
Original
OTU
MUX OA OA DEMUX OTU
MUX
DEMUX OA OA
Station A (OTM)
Fiber jumper connected to the original OTU
Fiber jumper connected to the replacement OTU
Replacement
OTU
Client
equipment
Station B (OTM)

As shown in Figure 3-9, when the OTU or tributary board reports an R_LOS alarm but the
receive module of the client equipment reports no alarm, replace the original OTU or tributary
board with a backup OTU board. Observe the alarms on the OTU board and client equipment.
If the alarm is cleared after the replacement, the original OTU board is faulty and needs to be
repaired. The following procedures can be used to narrow down the possible cause of the OTU
failure:
l If it is suspected that one of the tributary board channels or some a tributary board is faulty,
change the timeslot configuration to switch services to another channel or tributary board.
l If it is suspected that a slot is faulty, change the slot configuration.
l If it is suspected that a VC-4 channel is faulty, switch the time slot to another VC-4 channel.
3.1.6 PRBS Test
If no commissioning instruments are available in the network maintenance phase or on a new
network where no services are deployed, you can perform a self-transmit and self-receive test
using the pseudo random bit sequence (PRBS) function to check whether links on each section
are normal by performing loopbacks section by section.
Figure 3-10 shows a PRBS application. A local board with the PRBS test function sends PRBS
codes and analyzes the PRBS codes looped back from the peer end. By comparing the
loopbacked PRBS codes with the PRBS codes that should be received according to the
theoretical calculation, the local board determines whether equipment and the transmission line
are normal.
OptiX OSN 8800/6800/3800
33
Figure 3-10 PRBS application
PRBS is enabled on the auxiliary boards
Site A Site B
Tester
board
WDM
network
Inloop on
WDM side
Outloop on
WDM side
Inloop on
client side
Near-end
auxiliary
board
Far-end
auxiliary
board
Sends PRBS codes

CAUTION
l When a PRBS test is in progress, only query operations can be performed, no configurations
can be delivered to involved boards, the involved boards cannot carry any services, and the
original services on the boards will be interrupted.
l The LTX board does not support a PRBS test on multiple optical ports at the same time.
NOTE
l The PRBS test function is targeted for use during deployment and fault location. After deployment and
fault location, users must set PRBS Test Status to Disabled.
l PRBS codes vary according to the client-side service types. Therefore, to perform a client-side PRBS
test, users must ensure that the client-side service types for the tester board and auxiliary board are the
same.
The PRBS test is applicable to two networking modes, as provided in Table 3-1.
For a network, a client-side PRBS test covers a larger area than a WDM-side PRBS test, as
illustrated in Table 3-1. If a board on which a PRBS test has been started does not receive the
PRBS test signals that the board has sent, the board reports a PRBS_LSS alarm.
For information about how to complete PRBS configurations, see Configuring PRBS Test on
the Meter Board in Commissioning Guide.
For the boards that support the PRBS function, refer to Basic Functions of OTUs, OTN Tributary
Boards, OTN Line Boards and Packet Service Boards in Hardware Description.
OptiX OSN 8800/6800/3800
34
Table 3-1 PRBS applications
Test Mode Service Type Networking Diagram
Client-side
PRBS test
OTN signals/SDH
services
WDM network
Tester
board
Loopback on the WDM side/fiber loopback
TX RX
RX TX
OUT
IN
IN
OUT
TX
RX
WDM
side
Client
side
WDM
side
Client
side
Client
side
Remote
auxiliary
board
Near
auxiliary
board
Loopback on the client side/fiber loopback
2
3
4
1
Start PRBS test 1
2 3 4
WDM-side
PRBS test
N/A
Loopback on the WDM side/fiber loopback
WDM network
IN
OUT
OUT
IN
Tester
board
WDM
side
WDM
side
Remote
auxiliary
board
2
1
1
2
Start PRBS test
Tester board: generates PRBS test signals and monitors the loopbacked PRBS test signals
from the remote board. By comparing the transmitted and received PRBS test signals, the
board determines whether the current link and equipment are normal.
Auxiliary board: connects a tester board and the network under test and transparently transmits
the PRBS test signals. On the auxiliary boards at the near end, PRBS Test Status need to be
set to Enabled, only when client-side services are other than OTN services.
When a tributary or line board is used as a tester or auxiliary board, cross-connections need
to be configured to form a service path.

3.1.7 Configuration Modification
This method also removes problems caused by configuration errors in a known faulty NE. In
addition, this method is used to troubleshoot pointer justifications. Use this method to modify
the timeslot configuration, slot configuration, and board parameter configuration.
This method is used to resume the service temporarily when no spare board is available for the
replacement, or is used in handling the problem of pointer justification. The maintenance
personnel may not find this method convenient. In addition, save the original configuration
before you use this method. Record the steps used to locate the fault.
l If some path of a tributary board or some tributary board is suspected to be faulty, modify
the timeslot configuration to shift the payload to other path or tributary board.
l If a certain slot is suspected to be faulty, change the slot configuration.
l If a VC-4 is suspected to be faulty, shift the traffic to another VC-4.
l During the upgrade or expansion, if you are unsure about the new configuration, you can
re-load the original configuration for confirmation.
OptiX OSN 8800/6800/3800
35
l To modify the configuration in case of pointer justification, modify the tracing direction
and the reference source of the clock.
Modifying the timeslot configuration, however, does not help to locate the faulty point or faulty
board, for example, a line board, tributary board, cross-connect board or backplane. In this case,
use the replacement method or the loopback method to further locate the fault. This method is
applicable in the preliminary process of locating faults when spare boards are not available.
Other service channels or slots are used to resume the service temporarily.
3.1.8 Test Frame
A test frame is a data packet to test connectivity of networks carrying Ethernet services.
If a test meter or instrument is unavailable on site, the board receiving Ethernet services can be
used to send test frames. Test frames help operators commission services and locate faults during
network deployment or maintenance.
NOTE
The test frame function complies with the internal standard of Huawei.
When a test frames is in progress, only query operations can be performed, no configurations can be
delivered to involved boards, the involved boards cannot carry any services, and the original services on
the boards will be interrupted.
Application
A network can be into divided into access networks and a transmission network. On the access
networks, boards on OptiX OTN products are interconnected with client-side devices; on the
transmission network, boards on OptiX OTN products are interconnected with each other on the
WDM side.
Figure 3-11 and Figure 3-12 shows how to use test frames to assess the connectivity of network
links.
For OptiX OTN products, Ethernet boards with the test frame function send test frames in either
of the following modes: GFP test frame and Ethernet test frame.
l GFP test frame: send test frames using GFP management frame for GE and 10GE service.
The local NE compares the number of test frames transmitted with the number of response
frames received by the local board to detect network connectivity.
l Ethernet test frame: directly send test frames at MAC layer of 40GE and 100GE service.
The local NE compares the number of test frames transmitted with the number of test frames
received by the local board to detect network connectivity.
OptiX OSN 8800/6800/3800
36
Figure 3-11 Application 1 of GFP test frames
MAC
Internal Logical
Port
Board B
MAC
Internal Logical
Port
Board A
Test Frame
Transmission Network
Router
Router
Access Network Access Network
NE1 NE2
1
The internal logical ports of
Board A transmit a test
frame to the internal logical
ports of Board B.
NE1 counts the number of
transmitted test frames and received
test frames on Board A.
NE1 enables the user to determine
the quality of the service network.
OptiX OTN Product
3
2
Response Frame
After receiving the test
frame on Board B, Board B
transmits back a response
frame.

OptiX OSN 8800/6800/3800
37
Figure 3-12 Application 2 of Ethernet test frame
Router
Router
Access Network
NE1 NE2
1
The client-side port on board A
generates an Ethernet test frame and
encapsulates it into an OTN signal.
Then the OTN signal carrying the test
frame is sent to board B.
OptiX OTN product
2
Access Network
MAC
Board B
Upward
OTN signal carrying
an Ethernet test frame
Board A
MAC OTN
Test frame
OTN
NE1 counts the number of transmitted
test frames and received frames on
board A.
NE1 enables the user to determine the
quality of the service network.
OptiX OSN 8800/6800/3800
38
OTN signal carrying an
Ethernet test frame
Router Router
Access Network
NE1 NE2
1 The client-side port on
board A transmits an
Ethernet test frame to
the client-side port of
board B.
OptiX OTN product
3
Access Network
A A
Board A
MAC OTN
Board B
OTN MAC OTN
Board C
MAC
Downward
Test
frame
2
After receving the Ethernet test
frame, board B encapsulates it into
an OTN signal and transmits the
signal to board C.
NE1 counts the number of transmitted
test frames and received frames on
board A.
NE1 enables the user to determine the
quality of the service network.
NOTE
l Upward: The client-side port on board A generates an Ethernet test frame and send it to the WDM-side on
board B.
l Downward: The client-side port on board A generates an Ethernet test frame, send it to the WDM-side on
board C by the client-side port on board B.

l Application 1 of GFP test frames: In Figure 3-11, three counters monitor test frames
response frames. The first monitors the number of test frames transmitted by board A in
step 1, the second is the number of response frames transmitted by board B in step 2, and
the third is number of test frames received by board A in step 3. Based on service flows, if
the number of test frames transmitted by board A is equal to that of response frames received
by board A, the transmission link is normal. If the two numbers are different, packet loss
is occurring along the transmission link, indicating a fault on the link.
l Application 2 of ethernet test frames (for 40GE/100GE service): In Figure 3-12, two
counters monitor test frames response frames. The first monitors the number of test frames
transmitted by board A in step 1, the second is number of test frames received by board A
in step 2. Based on service flows, if the number of test frames transmitted by board A is
equal to that of test frames received by board A, the transmission link is normal. If the two
numbers are different, packet loss is occurring along the transmission link, indicating a
fault on the link.
For test frame configurations, refer to Configuring Test Frames in the Supporting Tasks.
Availability
Table 3-2 lists the boards that support the test frame function on OptiX OTN products.
OptiX OSN 8800/6800/3800
39
Table 3-2 Boards that support the test frame function on OptiX OTN products
Service Type Board Type with the Test Frame Function
OTU Board Tributary Board
FE
a
TN12LDM, TN11LDMD,
TN11LDMS, TN11LEM24,
TN11LOA, TN13LQM,
TN12LQMD, TN12LQMS
TN11TBE, TN54TEM28,
TN11TOM, TN52TOM,
TN12TQM
GE
b
TN11L4G, TN11LDGD,
TN11LDGS, TN12LDM,
TN11LDMD, TN11LDMS,
TN11LEM24, TN11LOA,
TN11LOG, TN12LOG,
TN11LOM, TN12LOM,
TN11LQG, TN13LQM,
TN12LQMD, TN12LQMS
TN11TBE, TN11TDG,
TN54TEM28, TN54THA,
TN54TOA, TN54TOG,
TN11TOM, TN52TOM,
TN12TQM
10GE LAN
c
TN11LEM24, TN11LEX4 TN11TBE, TN11TDX, TN12TDX,
TN52TDX, TN53TDX,
TN54TEM28, TN55TOX,
TN11TQX, TN52TQX, TN53TQX,
TN55TQX
40GE N/A TN54TSXL
100GE
TN12LSC
d
N/A
a: For FE service, the board supports the test frame function only when the serviec is mapping
with GFP-F.
b: For GE service, the board supports the test frame function only when the serviec is mapping
with GFP-T.
c: For 10GE LAN service, the board supports the test frame function only when Port Mapping
(WDM Interface) is set to MAC Transparent Mapping (10.7 G) or MAC Transparent
Mapping (10.7 G) support 1588.
d: The TN12LSC only support downward ethernet test frame.

When using the test frame function, take the following precautions:
l For OTU boards, except for TOM boards with tributary-line mode, test frames are
independent of electrical cross-connections. The receive board can receive test frames if
the transmission link between the transmit and receive boards is connective.
l When electrical cross-connections function from a tributary board to the WDM-side port
on an OTU board with the test frame, the OTU board processes GFP management frames.
Therefore, the tributary board cannot send or receive test frames.
OptiX OSN 8800/6800/3800
40
3.1.9 RMON Performance Analysis
When Ethernet service is interrupted or degraded, remote monitoring (RMON) can be enabled
on the U2000along with Ethernet OAM, loopback, and ping functions to locate faults causing
service interruption or degradation.
RMON is used to transmit monitoring data between different network segments.
Various performance statistics and Ethernet port data need to be managed. RMON is a standard
monitoring specification that enables various network monitors and console systems to exchange
network-monitoring data and create port-statistics reports. To meet different network
requirements, RMON provides flexible detection modes and control mechanisms. RMON also
provides error diagnosis, planning, and performance event monitoring of the entire network.
Purposes of RMON performance management are as follows:
l To save all statistical data at the agent end even when NEs cannot be reached by the manager
l To save historical data for fault diagnosis
l To detect errors and report performance events to the U2000
l To provide detailed port data to the U2000
l To support multiple management stations
RMON features are implemented through the following modules:
l Ethernet statistics group: Queries the current real-time statistical data of Ethernet ports.
The following performance items are supported: different packet lengths, overall
performance, errors and collisions, and FC performance.
l Ethernet historical group: Queries statistical data on Ethernet ports over a historical
sampling period. The Ethernet history group supports the same performance items as the
Ethernet statistics group.
For details, refer to Performance Event List of RMON Function in the Alarms and Performance
Events Reference.
Application
This topic uses Ethernet convergence service as an example to describe how to locate data service
faults using the RMON function. As shown in Figure 3-13, there is an Ethernet service from
station A to station C. Ethernet boards 1, 2, and 3 are used on stations A, B, and D, respectively.
Figure 3-14 shows the service connections. The data service from Router 1 to Router 2 is
abnormal. In this example, the service from Router 1 to Router 2 is interrupted.
OptiX OSN 8800/6800/3800
41
Figure 3-13 Ethernet convergence service
iManager U2000
A
B
C
D
Router 1
Router 2 Router 3
Ethernet
Board 1
Ethernet
Board 2
Ethernet
Board 3

Figure 3-14 Service Connections
Router 1
Router 2
VCTRUNK1
VCTRUNK2
VCTRUNK1
VCTRUNK1
Router 3
PORT1
PORT1
PORT1
Board 1
Board 2
Board 3

The RMON function is enabled to remotely monitor the service between stations C and A. To
check the service performance of the Ethernet service board at the transmit end (station A) you
can query the RMON performance of the corresponding Ethernet service board at station C.
When service is interrupted or signals are degraded, diagnose the fault as follows:
1. Set the RMON performance monitoring parameters for the Ethernet port, including the
monitored objects (ports on the Ethernet board) and the monitoring period of the
performance event.
OptiX OSN 8800/6800/3800
42
2. View the historical group performance and statistical group performance of the Ethernet
ports, and query the performance of PORT1 on Ethernet boards 1, 2, and 3 for a specific
period.
3. Analyze RMON performance and check whether the data is normal.
l When the PAUSE frame is found in the statistics report of the monitored port, use the
ping function to check whether the fault is occurring on the link between Huawei
equipment and the interconnected data communication equipment.
l If the FCS error, collision, or fragment is found in the statistics report of the monitored
port, refer to the procedure of handling the "the RMON performance value is above the
upper limit performance"event.
l If the problem is related to the maximum transmission unit (MTU), for example, the
set maximum transmission unit (MTU) is smaller than expected, change it.
4. Check whether the sum of the traffic on PORT1 of Ethernet boards 2 and 3 is equal to the
traffic on PORT1 of Ethernet board 1.
l If the sum of the traffic on PORT1 of Ethernet boards 2 and 3 is equal to the traffic on
PORT1 of Ethernet board 1, the fault may be located at the interconnection point
between Huawei equipment and the customer equipment instead of on Ethernet boards
1, 2, and 3. Use the ping function to check the link between Huawei equipment and the
non-Huawei equipment.
l If the sum of the traffic on PORT1 of Ethernet boards 2 and 3 is not equal to the traffic
on PORT1 of Ethernet board 1, the fault is occurring on Ethernet board 1, 2, or 3. Check
whether the traffic on PORT1 on Ethernet board 1, 2, or 3 is equal to the sum of the
traffic on the corresponding VCTRUNK ports to locate the specific board where the
fault (congestion or signal degradation) is occurring.
5. Use the ping function to check whether the fault occurs on the link between Huawei
equipment and the interconnected data communication equipment.
For RMON configurations, refer to Configuring the RMON in the Supporting Tasks.
3.1.10 Port Mirroring Analysis
To monitor and analyze the Ethernet packets at a port, you can enable the port mirroring function
so that the received or transmitted packets on the port are duplicated to another Ethernet port to
which the Ethernet tester is connected. Then, you can monitor and analyze the packets.
Application
You can configure port mirroring to perform packet monitoring, daily maintenance and in-
service commissioning. Port mirroring has the following features:
l Port mirroring applies to online fault diagnosis. It mirrors the traffic from one or more ports
to another port, and then an analyzer is used for fault diagnosis.
l After port mirroring is used, traffic can be monitored in real time using an analyzer.
Port mirroring implements fault diagnosis by mirroring and analyzing port data and without
affecting services. This method, which takes a long time and demands high maintenance skills,
is generally used by experienced maintenance personnel.
OptiX OSN 8800/6800/3800
43
Figure 3-15 Schematic diagram of Ethernet port mirroring
Mirroring
port
Ethernet processing unit
Monitoring
port
Ethernet tester Duplication
NE
To monitor the data in different directions, port mirroring can be performed in the ingress
direction and in the egress direction.
l In the ingress direction
Also in the upstream direction. The equipment duplicates the packets received from the
mirroring port to the observing port, and then transmits the packets from the observing port
to the Ethernet tester.
l In the egress direction
Also in the downstream direction. The equipment duplicates the packets transmitted by the
mirroring port to the observing port, and then transmits the packets from the observing port
to the Ethernet tester.
NOTE
No services can be configured on an observing port.
For LEX4, LEM24, TBE, and TEM28 boards, you can set Mirrored Upstream Port or Mirrored
DownstreamPort, but cannot set them at the same time.
For packet boards such as EG16, WX2, and PND2, pay attention to the following points:
l The port where LAG protection groups are configured, can be configured as the source mirroring port but
cannot as an observing port.
l Setting tags on an observing port does not affect the receiving or transmission of mirroring packets.
l On the same physical port, you can configure upstream or downstream mirroring services.

For port mirroring configurations, see Configuring Port Mirroring in Supporting Tasks.
Availability
Table 3-3 lists the boards that support the port mirroring function.
Table 3-3 Boards that support the port mirroring for the OptiX OTN products
Board Type Equipment
TBE, L4G OptiX OSN 6800
OptiX OSN 3800
LEX4, LEM24 OptiX OSN 6800
OptiX OSN 8800
EG16, EX2, PND2 OptiX OSN 8800

OptiX OSN 8800/6800/3800
44
Related Information
For TBE, L4G, LEX4, LEM24, TEM28:
Table 3-4 Parameters
Field Value Description
Board For example: 5-L4G Selects a board for port mirroring.
Mirror Listener Port For example: PORT4 l After the mirroring function of the
port is configured, you can
monitor all the mirrored ports by
analyzing the packets at the
mirroring port only. As a result,
you can easily manage the ports.
l Mirrored Port indicates the port
that sends the packets copied from
Mirrored Upstream Port and
Mirrored Downstream Port.
l Mirrored Port cannot be set to a
port that carries any service.
Uplink Listened Port For example: PORT3 Sets the uplink listened port.
Mirrored Upstream Port can be a
PORT or a VCTRUNK. As a PORT,
the port copies the packets that it
receives; as a VCTRUNK, the port
copies the packets that it transmits.
Mirrored Port sends the packets
copied from Mirrored Upstream
Port.
Downlink Listened
Port
For example: PORT5 Sets the downlink listened port.
Mirrored Downstream Port can be
a PORT or a VCTRUNK. As a PORT,
the port copies the packets that it
transmits; as a VCTRUNK, the port
copies the packets that it receives.
Mirrored Port sends the packets
copied from Mirrored Downstream
Port.
Mirrored Upstream Port and Mirrored Downstream Port indicate the ports that copy
packets for Mirrored Port.
The transmit direction and receive direction mentioned in this section are related to the local
NE.

For EG16, EX2, PND2:
OptiX OSN 8800/6800/3800
45
Table 3-5 Parameters
Field Value Description
Mirror ID - Indicates the mirroring ID. The
system automatically assigns
mirroring IDs if the Automatically
Assign check box is selected.
Mirror Name - Indicates the name of a mirroring
service.
Direction INGRESS, EGRESS
Default: INGRESS
Indicates the direction for observing a
mirroring service.
Mirror Source Function
Point
For example: Shelf0
(subrack)-2-54EX2-1
(PORT-1)
Indicates the source mirroring port.
Mirror Observation
Point
For example: Shelf0
(subrack)-12-54EX2-1
(PORT-1)
Indicates the observing port.

3.1.11 One-Click Data Collection
One-click data collection is generally used in the event of equipment failure to collect the fault
and performance data of the equipment.
For any problems that prove complex for technicians to identify or resolve, contact Huawei
technical support and report the relevant equipment data. As shown in Table 3-6, the equipment
data to be collected includes the version information, electronic labels, basic configurations,
service configurations, current and historical alarm and performance event data, equipment
running logs, operation logs, security logs, and equipment running status.
Table 3-6 Description of fault data types
N
o.
Type Description
1 NGWDM_
Board_Data
Collects the version information about NEs and boards, board dump
information, service performance parameters and alarms, and chip
register information on boards.
2 40G_Modul
e_Basic_Dat
a
Collects the performance status and key component parameters of the
40G optical and electrical modules installed on the boards on the current
NE. Such data includes the module input and output optical power
specifications, service status, alarms, and key component parameters.
OptiX OSN 8800/6800/3800
46
N
o.
Type Description
3 NGWDM_
Basic_Data
Collects the basic configuration information and electromechanical
information about the current NE. The basic configuration information
includes information about the active/standby boards, memory partition
and usage, file system, alarms, performance, and databases. The
electromechanical information includes the temperature alarm thresholds
of the system control boards and other boards, NE power consumption,
and NE power-saving status.
4 NGWDM_
Clock_Data
Collects time and clock information to check the tracing status of the
current NE. Such information includes the IEEE 1588-related alarms,
external time sources, line time sources, line time source tracing jitter,
synchronization clock alarms, and lost external clock sources.
5 NGWDM_
Communica
tions_Data
Collects the communication information to check the communication
status between NEs. Such information includes the NE IDs, NE routes,
communication ports, and orderwire configurations.
6 NGWDM_
Configure_
Data
Collects the electromechanical and configuration information about the
current NE. Such information includes the power supply and fan status,
interface board (EFI and ATE) status, and online status of the physical
boards.
7 NGWDM_E
lectric_Data
Collects the electrical-layer service configuration information about the
current NE. Such information includes the OTN overhead configurations
on service boards, management information about Ethernet ports, and
basic SDH configurations.
8 NGWDM_P
rotected_Da
ta
Collects the cross-connection and protection configurations on the
current NE. Such configurations include the intra-board protection, inter-
board protection, client-side protection, optical line protection, and
electrical cross-connections.
9 NGWDM_L
ight_Data
Collects the optical-layer configurations of the current NE. Such
configurations include the logical fiber connections, optical cross-
connections, automatic level control (ALC), intelligent power adjustment
(IPA), automatic power equilibrium (APE), and windows media unit
(WMU).
1
0
NGWDM_P
atch_Data
Collects the package loading data of the current NE. Such data includes
the package loading alarms, status, logs, and patch loading and operating
data.
1
1
NGWDM_
BlackBox_
Data
Collects board black box data in the log files from the platform in file
transfer protocol (SFTP) mode.
1
2
OTN_Ason
_Data
Collects data about ASON services, TE links, current alarms, historical
alarms, and boards. Such data must be collected when an ODUk service
in the OTN ASON domain is faulty (for example, service rerouting fails
or service interruption alarms are generated), or an ODUk ASON link is
faulty.
OptiX OSN 8800/6800/3800
47
N
o.
Type Description
1
3
WDM_Aso
n_Data
alarms, and boards. Such data must be collected when an OCh service in
the WDM ASON domain is faulty (for example, service rerouting fails
or service interruption alarms are generated), or an OCh/OMS ASON
link is faulty.
1
4
SDH_Ason_
Data
alarms, and boards. Such data must be collected when an SDH service in
the SDH ASON domain is faulty (for example, service rerouting fails or
service interruption alarms are generated), or an SDH ASON link is
faulty.
1
5
Collect_HIS
I_Chip_Dat
a
Collects the alarms of the boards that support the HISI chip on the current
NE.
1
6
SYS Collects information about management modules in one-click mode.
1
7
ALM Collects current and historical alarms in one-click mode.
1
8
ASON Collects information about ASON services in one-click mode.
1
9
TDM Collects data about the time division multiplexing (TDM) feature in one-
click mode.
2
0
WDM Collects data about the wavelength division multiplexing (WDM) feature
in one-click mode.
2
1
Data Collects information about service configuration modules in one-click
mode.
2
2
DBMS Collects data in the database in one-click mode.
2
3
PER Collects the current and historical performance data in one-click mode.

For data collection configurations, refer to Collecting Fault Data in the Supporting Tasks.
OptiX OSN 8800/6800/3800
48
4 Fault Location Using TP-Assist
About This Chapter
Fault location using the Transport Packet Assist (TP-Assist) simplifies operation and
maintenance (O&M) of packet services and improves O&M efficiency.
4.1 Fault Location Using IP Ping
You can use the cross-product IP ping function to quickly locate the fault that occurs on a hybrid
network containing transport network equipment and wireless network equipment.
4.2 E-LAN Service Loopback Detection
E-LAN services are broadcast on the related VLAN. If packet loopbacks occur, a broadcast
storm occurs. The E-LAN service loopback detection function is provided to detect and disable
the looped back service in time. The function helps prevent network congestion.
4.3 Performing Intelligent Service Fault Diagnosis for Ethernet Services
This section describes how to intelligently diagnose faults of Ethernet services based on service
paths.
OptiX OSN 8800/6800/3800
Troubleshooting 4 Fault Location Using TP-Assist
49
4.1 Fault Location Using IP Ping
You can use the cross-product IP ping function to quickly locate the fault that occurs on a hybrid
network containing transport network equipment and wireless network equipment.
The IP ping function is classified into near-end IP ping and far-end IP ping functions.
l Near-end IP ping
The wireless network equipment sends IP ping packets to a user-to-network interface (UNI)
on near-end transport network equipment. The transport network equipment responds to
the IP ping packets. The near-end IP ping function is generally used to check whether a
fault occurs on wireless network equipment. For example, the NodeB sends IP ping packets
to the UNI on NE1, as shown in Figure 4-1.
l Far-end IP ping
The wireless network equipment sends IP ping packets to a UNI on far-end transport
network equipment. The transport network equipment responds to the IP ping packets. The
far-end IP ping function is generally used to check whether a fault occurs on the transport
network. For example, the NodeB sends IP ping packets to the UNI port on NE2, as shown
in Figure 4-1.
Figure 4-1 Application of the IP ping functions
NodeB
RNC
Far-end IP Ping
Near-end IP Ping
Near-end IP Ping
Far-end IP Ping
NE1 NE2
PSN
Router

NOTE
Switches and routers support both strict mode and non-strict mode.
l In strict mode, switches and routers learn MAC addresses only upon receiving ARP responses.
l In non-strict mode, switches and routers learn MAC addresses upon receiving ARP request packets.
OptiX OSN equipment enabled with the IP ping function does not send ARP responses. If switches or
routers use the strict mode, IP ping will fail. Therefore, if the IP ping function is initiated by a switch or
router, use the non-restrict mode for the switch or router.
When the IP ping function is initiated at a PC that is directly connected to an NE, the packets sent by the
PC do not carry VLAN tags. To test a service with VLAN tags on the NE, set the tag attribute of the service
port to Access or Hybrid, and set the default VLAN ID of the port the same as the service VLAN ID.
The following describes how to configure the near-end IP ping function and far-end IP ping
function using a NodeB as the initiator of the IP ping function.
OptiX OSN 8800/6800/3800
50
Table 4-1 Mapping between port encapsulation modes and TPIDs in IP Ping packets
Encapsulation mode of the
Port
TPID in IP Ping Packets
Null 0x8100
802.1Q 0x8100
QinQ 0x8100 and NE-level TPID (0x88a8 by default)

Near-End IP Ping
Step 1 Right-click NE1 in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 In the NE Explorer, click NE1 and choose Configuration > Packet Configuration > IP Ping
Test.
Step 3 Set Enable, VLAN ID, VLAN Priority, IP Address, IP Mask, Next Hop IP Address, and
Next Hop IP Mask for the target UNI.
NOTE
l The IP address of the UNI must be on the same network segment with the IP address of the NodeB, to
ensure that the near-end IP ping function can operate properly.
l The next hop IP address of the UNI is the IP address of the port connecting straightly with the NodeB.
Step 4 Click Apply.
----End
Far-End IP Ping
Step 2 In the NE Explorer, click NE1 and choose Configuration > Packet Configuration > IP Ping
Test.
Step 3 Click Add and set the proxy IP address in the Proxy IP Address List area.
NOTE
In far-end IP ping tests, the configured proxy IP address ensures that IP ping packets are forwarded through
the proxy IP address.
Step 4 Click Apply.
Step 5 Set Enable, VLAN ID, VLAN Priority, IP Address, and IP Mask for a UNI of NE2 by
referring to the configuration steps applicable to NE1.
OptiX OSN 8800/6800/3800
51
NOTE
l The UNI IP address configured on NE2 must be the same as the proxy IP address configured on NE1.
l Before using the far-end IP ping function, ensure that the IP ping function has been enabled on both
the near-end port and far-end port.
----End
4.2 E-LAN Service Loopback Detection
E-LAN services are broadcast on the related VLAN. If packet loopbacks occur, a broadcast
storm occurs. The E-LAN service loopback detection function is provided to detect and disable
the looped back service in time. The function helps prevent network congestion.
Application Scenario
The E-LAN service loopback detection function applies to the following native Ethernet
services:
l IEEE 802.1d bridge-based E-LAN services
l IEEE 802.1q bridge-based E-LAN services
l IEEE 802.1ad bridge-based E-LAN services
Context
l As shown in Figure 4-2, E-LAN services are configured for the network. A UNI on NE1
initiates a loopback detection packet on the specified VLAN. The loopback detection packet
takes the same path as forwarded service packets.
l If the UNI receives a loopback detection packet whose destination MAC address is the
same as the source MAC address of the loopback detection packet sent by the UNI, a
loopback occurs. You can use the automatic disabling function to disable loopback services.
If the UNI does not receive a loopback detection packet within the specified duration, a
service loopback does not occur. The duration ranges from 3s to 10s and the default value
is 3s.
NOTE
The automatic disabling function disables only the looped back service. The UNI remains operational.
Therefore, disabling of the looped back service does not affect other services provided by the UNI.
l You can perform E-LAN service loopback detection for a maximum of 20 VLANs at a
time. You can perform two consecutive loopback detection operations for a VLAN at an
interval of 10 or more seconds.
OptiX OSN 8800/6800/3800
52
Figure 4-2 Application of E-LAN service loopback detection
Loopback
detection
packet
NE1
NE2
NE3
PSN

Procedure
Step 2 In the NE Explorer, click NE1 and choose Configuration > Packet Configuration > Ethernet
Service Management > E-LAN Service.
Step 3 Select the target E-LAN service and click the Loopback tab.
Step 4 Click UNI and set the port that initiates the loopback packet.
NOTE
This task uses a UNI as an example. The port varies according to services.
Step 5 Click Start.
Step 6 Set Vlans/CVLAN, Packet Timeout Period, and Disable Service When Loopback is
Detected. Then click Start.
Step 7 Check the loopback detection results.
Step 8 Optional: If the loopback services does occur, disable the looped back service in time to help
prevent network congestion.
OptiX OSN 8800/6800/3800
53
1. Choose NE Explore. In the NE Explorer choose Configuration > Packet
Configuration > Ethernet Service Management > E-LAN Service > Loopback, Click
Service Status List.
2. In the Service Status List box, choose the loopback service, set Service Status as
Disable,then click Enable.
----End
4.3 Performing Intelligent Service Fault Diagnosis for
Ethernet Services
This section describes how to intelligently diagnose faults of Ethernet services based on service
paths.
Prerequisites
You must be an NM user with NE administrator authority or higher.
End-to-end Ethernet services have been deployed.
Procedure
Step 1 Search for services.
1
3
The service path to which the specified port
and VLAN ID reside is displayed.
4
Search for nodes in a VLAN
domain based on the port and
VLAN ID specified by a user.
Networking diagram of the domain
is displayed.
2
Step 2 Select a service to be diagnosed by specifying a service port.
OptiX OSN 8800/6800/3800
54
5
6 7
Detect a specified service.
8
Step 3 Diagnose the service and display the result.
Test result about received packets
on ports is displayed.
Test result about transmitted
packets on ports is displayed.
Alarms that affect services are
displayed.
12
Service information is
displayed.
9
Test result and progress are
displayed.
11
10
13
Step 4 Optional: You can also diagnose the PWE3 services as follow:
1. Choose Service > PWE3 Service > Manage PWE3 Service from the main menu.
2. In the dialog box that is displayed, set filter vaule. Click Filter to check PWE3 services.
3. Select the PWE3 service to be deployed, right-click the PWE3 services, and choose
Diagnose Service from the shortcut menu.
----End
OptiX OSN 8800/6800/3800
55
5 Service Interruptions
About This Chapter
Many factors can cause service interruptions, such as bit errors, line interruption, decrease of
optical power, failed interconnection of equipment.
5.1 Interruption of All Services
This section introduces the analysis and handling of faults that result in service interruptions on
an NE.
5.2 Single-Channel Service Interruption on the Client Side
This section introduces the analysis and handling of faults that result in an interruption of one
client-side service on an NE.
5.3 Single-Channel Service Interruption on the WDM Side
WDM-side service on an NE.
5.4 Service Interruption Caused by Human Misoperation
an NE because of misoperations.
5.5 Service Interruptions Caused by Power Supply Failures
This topic describes the symptoms, impact, and possible causes of a service interruption caused
by a power supply failure. In addition, this topic describes the required tools, precautions, and
procedures for rectifying the fault.
5.6 Service Interruptions Due to Grounding Fault
by a grounding fault. In addition, this topic describes the required tools, precautions, and
5.7 Service Interruptions Due to Unfavorable Environmental Conditions
by unfavorable environmental conditions. In addition, this topic describes the required tools,
precautions, and procedures for rectifying the fault.
5.8 Service Interruptions Due to Faulty Optical Fibers, Cables, or Connectors
OptiX OSN 8800/6800/3800
Troubleshooting 5 Service Interruptions
56
by faulty fibers, cables, and or connectors. In addition, this topic describes the required tools,
5.9 Service Interruptions Due to Inconsistency of Board Types or Board Settings
by inconsistent board types or board settings when the board is replaced or added. In addition,
this topic describes the required tools, precautions, and procedures for rectifying the fault.
5.10 Service Interruptions on the VCTRUNK Port
This topic describes the symptoms, impact on the system, and possible causes of a service
interruption on the VCTRUNK port. In addition, this topic describes the required tools,
5.11 Service Interruptions on a Single Ethernet Port
This topic describes the symptoms, impact, and possible causes of a service interruption on a
single Ethernet port. In addition, this topic describes the required tools, precautions, and
5.12 Service Interruptions on All Ethernet Ports
This topic describes the symptoms, impact, and possible causes of a service interruption on all
Ethernet ports of an Ethernet board. In addition, this topic describes the required tools,
5.13 Service Interruption Cases
This section lists cases related to Service Interruption.
OptiX OSN 8800/6800/3800
57
5.1 Interruption of All Services
an NE.
Symptom
The OA (Station B) reports MUT_LOS alarm and all OTUs (Station B) report alarm R_LOS, ,
OTUk_LOF, OTUk_LOM alarm. All services are interrupted.
Networking configuration example is shown in Figure 5-1.
Figure 5-1 Networking configuration example of interruption of all services
Client
equipment
OTU MUX OA
DEMUX
Station A (OTM)
FIU OTU
MUX
OA DEMUX FIU
OSC OSC
Client
equipment
Station B (OTM)

Impact on System
All services are interrupted.
Possible Causes
l Cause 1: The fiber is cut off.
l Cause 2: The optical power is abnormal.
l Cause 3: The optical amplifying board or the optical cable is faulty.
l Cause 4: The demultiplexing/multiplexing board at station A or B is faulty.
l Cause 5: The ring fiber adapter from the equipment to the ODF is damaged.
Tools, Equipment and Materials
U2000, Optical power meter, cassette cleaner, optical time-domain reflectometer, ring fiber
adapter
Procedure
l Cause 1: The system provides an OSC board, the optical amplifier board reports a
MUT_LOS alarm, and the optical supervisory board reports a OSC_LOS alarm. In this
case, suspect that the optical cable is cut off.
OptiX OSN 8800/6800/3800
58
1. Check the fiber jumper between the optical distribution frame (ODF) and WDM
equipment. If the fiber jumper is dirty, clean the fiber jumper; if it is faulty, replace
the fiber jumper.
2. If the fiber jumper is good, the optical cable is faulty. Clear the fault.
l Cause 2: The system provides an OSC board, the optical amplifier board reports a
MUT_LOS alarm, and the OSC board reports no OSC_LOS alarm. It indicates that the
optical power is abnormal.
1. Check the fiber jumper between the FIU and optical amplifier board. If the fiber jumper
is dirty, clean the fiber jumper.
2. Check the optical power change of the OSC. If the received optical power of the OSC
declines, check whether the attenuation of the optical cable is excessive. If yes, the
optical cable is faulty. Clear the fault.
3. If the optical cable between station A and B is good, query the optical power on the
U2000 at station A.
If the input optical power of the optical amplifier board at station A is normal but
the output optical power is too low, replace the optical amplifier board at station
A.
If the input optical power of the optical amplifier board at station A declines and
thus results in a low output optical power, check the upstream against the service
signal flow to locate the fault.
4. If the optical cables of the faulty station B are good, check whether the input optical
power of the optical amplifier board is normal. If yes, and the output optical power is
too low, replace the board.
l Cause 3: The system provides no OSC board, and the optical amplifier board reports a
MUT_LOS alarm. It indicates that the optical amplifying board or the optical cable is faulty.
1. Refer to Testing Optical Power by Using an Optical Power Meter. Check whether the
input optical power of the optical amplifier board at station B is normal. If yes, replace
the optical amplifier board at station B.
input and output optical power of the optical amplifier board at station A is normal.
If the input optical power is normal but the output optical power declines, replace the
optical amplifier board at station A.
3. Check the fiber jumper between the ODF and WDM equipment. If the fiber jumper
is dirty, clean it; if it is faulty, replace it.
4. If the fiber jumper is good, the optical cable is faulty. Clear the fault.
l Cause 4: The MUX/DEMUX board at station A or B is faulty.
1. Query failure alarms of the MUX/DEMUX board at station A or B. If alarms are found,
replace the faulty board.
NOTE
Before you replace the M40V or D40V board, record the attenuation of the internal VOA of
each channel.
1. Check the ring fiber adapter between the ODF and WDM equipment. If the ring fiber
adapter is faulty, replace it.
----End
OptiX OSN 8800/6800/3800
59
5.2 Single-Channel Service Interruption on the Client Side
client-side service on an NE.
Symptom
The client-side RX interface of the OTU or tributary board reports alarms such as R_LOS,
R_LOF, OTUk_LOF at station A, and the client-side service is interrupted.
Figure 5-2 Networking configuration example of interruption of client-side services
Client
equipment
OTU1 OTU1
Station A (OTM)
OTUn
MUX
DEMUX
OA
OTUn
MUX
DEMUX
OA
Client
equipment
Station B (OTM)

Impact on System
Single channel service is interrupted on the client side.
Possible Causes
l Cause 1: The output optical power of the client equipment that is interconnected to the
OTU board is abnormal.
l Cause 2: The fiber jumper between the OTU board and client equipment is faulty.
l Cause 3: The optical interfaces of the OTU board are dirty.
l Cause 4: The OTU board is faulty.
l Cause 5: The client equipment is faulty.
l Cause 6: The service type, wavelength and mode that configured on the board 1 are different
from those of the client equipment, and therefore services are interrupted.
U2000, Optical power meter, Cassette cleaner, Optical fiber, Compressed gas
Procedure
l Cause 1: The output optical power of the client equipment that is interconnected to the
OTU board is abnormal.
OptiX OSN 8800/6800/3800
60
output optical power of the client equipment is normal. If not, remove the fault of the
client equipment.
l Cause 2: The fiber jumper between the OTU board and client equipment is faulty.
1. If the output optical power of the client equipment is normal, check whether the input
optical power of the OTU board is normal. If not, clean the fiber jumper or replace
the fiber jumper.
l Cause 3: The optical interfaces of the OTU board are dirty.
1. If the optical interfaces of the OTU board are dirty, blow them with compressed gas
to clean them.
l Cause 4: The OTU board is faulty.
1. If the input optical power of the OTU board is normal, but the system reports an alarm
indicating that the optical power is abnormal or an alarm related to the optical module,
replace the client-side optical module on the OTU board.
2. If the fault still exists, replace the board.
l Cause 5: The client equipment is faulty.
1. Remove the fault of the client equipment.
l Cause 6: The service type, wavelength and mode that configured on the board 1 are different
from those of the client equipment, and therefore services are interrupted.
1. Query and set the client service type, wavelength and mode of the board 1. Make sure
that the service type, wavelength and mode of the board 1 board are the same as those
of the client equipment.
NOTE
For GE service, query and set the auto-negotiation modes of the boards. Make sure that the auto-
negotiation modes are the same.
----End
5.3 Single-Channel Service Interruption on the WDM Side
WDM-side service on an NE.
Symptom
The WDM-side IN interface of the OTU, or tributary board and line board reports alarms such
as R_LOS, R_LOF, R_OOF and OTUk_LOF, and one channel of services is interrupted.
OptiX OSN 8800/6800/3800
61
Figure 5-3 Networking configuration example of interruption of one channel of services
OTU
MUX OA
OA DEMUX OTU
MUX
DEMUX OA OA
Client
equipment
Client
equipment
Signal Flow
Station A Station B

Impact on System
One channel of the WDM-side services of an NE is interrupted.
Possible Causes
l Cause 1: The OTU, or tributary board and line board in the opposite station (station A) is
faulty or the fiber jumper in the opposite station between the OTU board and MUX is dirty.
l Cause 2: The fiber jumper between the DEMUX and OTU, or tributary board and line board
is dirty or faulty.
l Cause 3: The loopback testing on the OTU, or tributary board and line board in the local
station and the optical power of OTU, or tributary board and line board is normal. In this
case, the FEC mode of the OTU, or tributary board and line board in the local station and
the opposite station might be inconsistent.
l Cause 4: The interconnection services type, wavelength and mode do not match.
l Cause 5: The OTU, or tributary board and line board at the local station (station B) is faulty.
l Cause 6: New service wavelengths are added to the network and the new service
wavelengths conflict with existing service wavelengths.
Procedure
l Cause 1: The OTU, or tributary board and line board in the opposite station (station A) is
faulty or the fiber jumper in the opposite station between the OTU, or tributary board and
line board and MUX is dirty.
1. Check whether the input optical power on the client side and the output optical power
on the WDM side of the OTU, or tributary board and line board in the opposite station
are normal. If either optical power is abnormal, replace the corresponding board.
2. Check the input optical power of the optical amplifier board in the opposite station
(station A) to determine whether the fiber jumper between the OTU, or tributary board
and line board and MUX is dirty or faulty. If the fiber jumper is dirty, clean the fiber
jumper; if it is faulty, replace the fiber jumper.
OptiX OSN 8800/6800/3800
62
l Cause 2: The fiber jumper between the DEMUX and OTU, or tributary board and line board
is dirty or faulty.
1. Check whether the input optical power of the OTU, or tributary board and line board
is normal. If not, clean or replace the fiber jumper between the DEMUX and OTU, or
tributary board and line board.
l Cause 3: The loopback testing on the OTU, or tributary board and line board in the local
station and the optical power of OTU, or tributary board and line board is normal. In this
case, the FEC mode of the OTU, or tributary board and line board in the local station and
the opposite station might be inconsistent.
1. Refer to Querying the FEC Type to query the FEC states of the two interconnected
boards on the U2000. If the two modes differ, enable the FEC to ensure mode
matching.
l Cause 4: The interconnection services type, wavelength and mode do not match.
1. Check and ensure that the interconnection services type, wavelength and mode match.
NOTE
If the services on the WDM side do not match, there is only LOOP_ALM alarm reported in
the loopback operation, but there will be OTUk_LOF or R_LOF if the loopback operation is
canceled.
l Cause 5: The OTU, or tributary board and line board at station B is faulty.
1. Check whether the input optical power of the OTU, or tributary board and line board
is normal. If yes, the OTU, or tributary board and line board in the local station is
faulty. Replace the pluggable optical module or Replace the board.
l Cause 6: New service wavelengths are added to the network and the new service
wavelengths conflict with existing service wavelengths.
1. Check whether new services are added to the network. If new services are added,
check whether the new service wavelengths conflict with the existing service
wavelengths. Then, change the new service wavelengths so that they do not conflict
with the existing service wavelengths.
----End
5.4 Service Interruption Caused by Human Misoperation
an NE because of misoperations.
Symptom
Human misoperation results in service interruptions.
Impact on System
The services carried on the OTU, or tributary board and line board are interrupted.
OptiX OSN 8800/6800/3800
63
Possible Causes
l Cause 1: When you disable the FEC function of an OTU, or tributary board and line board,
the equipment does not report any alarm, whereas the OTN services borne by the equipment
are interrupted.
l Cause 2: The FEC mode of any OTU, or tributary board and line board is manually changed,
causing the services to be interrupted.
l Cause 3: Hardware loopback or software loopback is set manually.
U2000
Procedure
l Cause 1: When you disable the FEC function of an OTU, or tributary board and line board,
the equipment will not report any alarm, but the OTN services are interrupted.
1. Querying the FEC Mode, the equipment does not report any alarm when you enable
or disable the FEC function of the OTU, or tributary board and line board. The engineer
must pay attention to this during maintenance. Make sure to enable the FEC function
in application.
l Cause 2: The FEC mode of any OTU, or tributary board and line board is manually changed,
causing the services to be interrupted.
1. Check whether the FEC modes of the two interconnected boards are different.
l Cause 3: Hardware loopback or software loopback is set manually.
1. Check whether hardware loopback is set. If yes, release the hardware loopback.
2. On the U2000, check whether software loopback is set on the service channel
manually. If yes, release the software loopback.
----End
5.5 Service Interruptions Caused by Power Supply Failures
by a power supply failure. In addition, this topic describes the required tools, precautions, and
Symptom
A large number of boards on the device of a certain site are reset simultaneously and the services
are interrupted.
Impact on System
Power supply failures may cause service interruptions.
Possible Causes
l Cause 1: The power supply of the board fails.
OptiX OSN 8800/6800/3800
64
l Cause 2: The power cable connectors are not connected properly.
l Cause 3: The external power supply is off or the power fluctuates abnormally.
l Cause 4: The power board of the device is faulty.
l Cause 5: The DC PDU is faulty.
Tools, Equipment, and Materials
U2000, Multimeter, Screwdriver
Procedure
l Cause 1: The power supply of the board is faulty. As a result, services are interrupted.
1. Query the current alarms on the U2000.
If... Then...
The NE reports the
POWER_ABNORMAL,
POWER_FAIL alarm
Proceed to the next step.
The NE does not report the
POWER_ABNORMAL,
POWER_FAIL alarm
Check whether the fault is due to other
causes.

NOTE
Only SDH boards support POWER_ABNORMAL alarm.
2. Handle the POWER_ABNORMAL, POWER_FAIL alarm.
3. Check whether services recover. If the services do not recover, check whether the fault
is due to other causes.
l Cause 2: The power cable connectors are not connected properly. As a result, services are
interrupted.
1. Check the connections of the power cables on the external power supply module, DC
PDU, and power board of the device.
If... Then...
The power cable connectors are not
connected properly
Fasten the power cable connectors by
using a screwdriver or replace the power
cable connectors, and proceed to the
next step.
Power cable connectors are connected
properly and the contact is good
causes.

l Cause 3: The external power supply is off or the power fluctuates abnormally. As a result,
services are interrupted.
OptiX OSN 8800/6800/3800
65
1. Switch off the DC PDU. Connect the positive pole of the multimeter to the NEG(-)
terminal of the DC PDU and the negative pole of the multimeter to the RTN(+)
terminal. Measure the voltage between the RTN(+) and NEG(-) terminals and check
whether the voltage meets the requirement. For details about voltage requirements,
refer to the Hardware Description.
If... Then...
The voltage between the RTN and -48V
DC terminals does not meet the
requirements
The voltage between the RTN and -48V
DC terminals meets the requirements
causes.

2. Contact the power supply engineers to rectify the fault of the external power supply.
l Cause 4: The power board of the device is faulty. As a result, services are interrupted.
1. Replace the power board of the device.
l Cause 5: The DC PDU is faulty. Abnormality of the power supply system causes the board
reset.
1. Replace the DC PDU.
----End
5.6 Service Interruptions Due to Grounding Fault
by a grounding fault. In addition, this topic describes the required tools, precautions, and
Symptom
are interrupted.
Impact on System
The grounding fault causes service interruptions.
Possible Causes
l Cause 1: The PGND and BGND grounding is poor, and the grounding resistance is higher
than 10 ohms or the potential difference between BGND and PGND is higher than 0.5 V.
l Cause 2: The PGND and BGND share the same grounding with the AC neutral wire.
OptiX OSN 8800/6800/3800
66
l Cause 3: The PGND of the interconnected device is not joint grounding.
NOTE
PGND means protection ground and BGND means power ground (also called working ground).
Multimeter, Screwdriver
NOTE
Use the multimeter to check whether the grounding resistance of the BGND and PGND meet the
requirements. Or, you can use a proper meter to check whether the waveform of the interconnected signal
is distorted.
Procedure
l Cause 1-3: The device grounding is improper. As a result, services are interrupted.
1. Check whether the ground bar in the telecommunications room is properly grounded.
If the grounding is proper, proceed to the next step; otherwise, ground the ground bar
properly.
2. Check whether the contact between the cabinet of the transmission device and the
ground bar in the telecommunications room is good. If the contact is good, proceed
to the next step; otherwise, ground the cabinet of the transmission device properly.
3. Check whether the contact between the cabinet and the front door/side cover of the
cabinet is good. If the contact is good, proceed to the next step; otherwise, ground the
front door/side cover of the cabinet properly.
4. Check whether the contact between the subrack and the cabinet is good. If the contact
is good, proceed to the next step; otherwise, ground the subrack properly.
5. Check whether the DDF and ODF are properly grounded. If the DDF and ODF are
properly grounded, proceed to the next step; otherwise, ground the DDF and ODF
properly.
6. Check whether the NMS device and various power consumption devices are properly
grounded. If these devices are properly grounded, proceed to the next step; otherwise,
ground these devices properly.
7. Check whether the grounding of the interconnection devices is joint grounding.
----End
5.7 Service Interruptions Due to Unfavorable
Environmental Conditions
by unfavorable environmental conditions. In addition, this topic describes the required tools,
Symptom
are interrupted.
OptiX OSN 8800/6800/3800
67
Impact on System
Unfavorable environmental conditions can cause a service interruption.
Possible Causes
l Cause 1: The temperature and humidity of the environment have caused equipment damage.
l Cause 2: A strong external interference source exists.
l Cause 3: Rodent animals damage equipment.
U2000, Thermometer, Humidiometer
Procedure
l Cause 1: The temperature and humidity of the environment have caused equipment damage.
As a result, services are interrupted.
1. Check whether the temperature and humidity of the environment meet the
requirements.
The detailed requirements are as follows:
Temperature: 0C to 45 C (32F to 113F)
Relative humidity: 10% to 90%
If... Then...
The temperature and humidity of the
environment do not meet the
requirements
Check and adjust the air conditioner in
the telecommunications room to make
sure that the temperature and humidity
of the telecommunications room are in
the proper range. Check whether
services recover. If the services do not
recover, check whether the fault is due
to other causes.
environment meet the requirements

2. Check the current alarms on the U2000.
If... Then...
The NE reports the temperature
threshold-crossing alarms
TEMP_OVER
The NE does not report the temperature
TEMP_OVER
causes.

OptiX OSN 8800/6800/3800
68
3. Handle the TEMP_OVER alarms.
l Cause 2: A strong external interference source exists. As a result, services are interrupted.
1. Check whether there is a transformer, high-voltage transmission line, or high-current
device near the device.
If... Then...
There is an AC transformer within 20 m
(65.6 ft.) of the device or high-voltage
transmission line within 50 m (164.1 ft.)
of the device
The interference should meet the
requirements of related standards. When
necessary, shielding or isolation
measures should be taken to protect the
device. Check whether services recover.
If the services do not recover, proceed to
the next step.
There is no AC transformer within 20 m
of the device

2. Check whether there is a high-power broadcasting transmitter near the device.
If... Then...
There is a high-power broadcasting
transmitter within 500 m (1640.5 ft.) of
the device
the next step.
There is no high-power broadcasting
the device

3. Check whether there is a mobile communication transmitter near the device.
If... Then...
There is a mobile communication
transmitter near the device
the next step.
OptiX OSN 8800/6800/3800
69
If... Then...
There is no mobile communication

4. Check whether a hand-held mobile communication device is in use near the device.
If... Then...
A hand-held mobile communication
device is in use near the device
Switch off the hand-held mobile
communication device. Check whether
to other causes.
No hand-held mobile communication
causes.

l Cause 3: Rodent animals damage equipment. As a result, services are interrupted.
1. Check whether there are rodent animals or their excrement inside the cabinet.
If... Then...
There are rodent animals or their
excrement inside the cabinet
Remove the rodent animals and their
excrement, replace any broken cable,
and install a rodent-proof mesh in the
cabinet. Check whether services
recover. If the services do not recover,
check whether the fault is due to other
causes.
There are no rodent animals or their
excrement inside the cabinet
causes.

----End
Related Information
Table 5-1 lists the requirement for the electromagnetic interference.
Table 5-1 Requirements of the electromagnetic interference
Electromagnetic Environment Electromagnetic
Environment Parameter
Low-frequency magnetic
field
Frequency (Hz) 50 to 20000
Ampl. A/m (rms) 10 to 0.025
OptiX OSN 8800/6800/3800
70
Amplitude-modulated
radio-frequency electrical
field
Frequency (MHz) 0.009 to 1000
Ampl. V/m (rms) 3
Impulse-modulated radio-
frequency electrical field
Frequency (GHz) 1 to 20
Ampl. (V/m (peak)) 3

5.8 Service Interruptions Due to Faulty Optical Fibers,
Cables, or Connectors
by faulty fibers, cables, and or connectors. In addition, this topic describes the required tools,
Symptom
Services of a certain site are interrupted.
Impact on System
Faulty fibers, cables, or connectors can cause a service interruption.
Possible Causes
l Cause 1: The fibers are broken.
l Cause 2: Attenuation of the fibers and the fiber adapter is too high.
l Cause 3: The cable connectors are connected improperly or incorrectly, or are not
connected.
U2000, Optical time-domain reflectometer (OTDR), Optical power meter
Precautions
DANGER
l Avoid direct eye exposure to laser beams launched from the optical interface and the fiber
jumper connector.
l When removing fibers from the optical interface, make sure that the proper optical fiber is
removed; otherwise, it may cause service interruption to a larger area.
OptiX OSN 8800/6800/3800
71
Procedure
l Query alarms on the U2000 and clear the alarms according to the reported information.
If... Then...
The NE reports the R_LOS, R_LOF or
IN_PWR_LOW alarm
Proceed to the next substep.
The NE does not report the R_LOS,
R_LOF or IN_PWR_LOW alarm
causes.

2. Handle the R_LOS, R_LOF or IN_PWR_LOW alarm.
l Cause 1: The fibers are broken. As a result, services are interrupted.
1. Use the OTDR meter to test the fibers. According to the line attenuation curve
displayed by the meter, determine whether the fibers are broken and the detailed
position of the broken fibers. For how to use the OTDR meter, see the Operation
Guide of the OTDR meter.
If... Then...
The fibers are detected as broken Replace the fibers. Check whether
to other causes.
The fibers are not detected as broken Check whether the fault is due to other
causes.

l Cause 2: Attenuation of the fibers and the fiber adapter is too high. As a result, services are
interrupted.
1. Measure the transmit optical power of the board in the upstream station and the receive
optical power of the board in downstream station.
If... Then...
The transmit optical power of the board
in the upstream station is abnormal
Replace the board.
The receive optical power of the board
in downstream station is abnormal

2. The difference between the transmit optical power of the board in the upstream station
and the receive optical power of the board in downstream station is the actual optical
power attenuation of the line. Compare the actual optical power attenuation of the line
with the designed value. If the actual attenuation is higher than the designed value,
locate and rectify the fault as follows.
OptiX OSN 8800/6800/3800
72
Check whether the bending radius of the fibers is equal to or larger than
standard. If the bending radius of the fibers is less than standard, re-route the
fibers and make sure that the bending radius is equal to or larger than standard.
Check whether there are many fiber connectors on the line and whether the
connectors are connected properly. If the connectors are connected improperly,
fasten the connectors with the optical modules.
Check whether there are aerial fibers on the line, which is easy to be affected by
the weather. If there are aerial fibers on the line, provide necessary protection to
the aerial fibers.
Check whether the fiber type and attenuation factor of the line are consistent with
the designed ones. If the fiber type and attenuation factor of the line are inconsistent
with the designed ones, replace the fiber.
Check whether the fiber connectors of the line are dirty. For details, see the
information about checking the fiber connectors. Clean the fiber connectors.
l Cause 3: The connection between the cable and the connector is loose, the cable connectors
are connected incorrectly, or the cable connectors are not connected. As a result, services
are interrupted.
1. Check the cables connection on the board in the downstream station.
If... Then...
The connection between the cable and
the connector is loose
Connect the cables properly. Check
whether services recover. If the services
do not recover, proceed to the next
substep.
The connection of the cable and the
connectors is good

2. Check whether the connections of the cables to the board in the downstream station
are correct.
If... Then...
Connections of the cables to the board in
the downstream station are incorrect
Connect the cables correctly. Check
do not recover, check whether the fault
Connections of the cables to the board in
the downstream station are correct
causes.

----End
OptiX OSN 8800/6800/3800
73
Related Information
Table 5-2 Minimum bending radius for fibers
Fiber Type Minimum Bending Radius
G.652D 30 mm
Multi-mode fiber (A1B) 30 mm
G.657A2 10 mm
G.657B3 8 mm
Note: When fibers are connected to CRPC boards, the bending radius of the fibers must be
greater than or equal to 50 mm to ensure expected transmission performance.

5.9 Service Interruptions Due to Inconsistency of Board
Types or Board Settings
by inconsistent board types or board settings when the board is replaced or added. In addition,
this topic describes the required tools, precautions, and procedures for rectifying the fault.
Symptom
During a capacity expansion at a site, after a board is replaced or added, services are interrupted.
Impact on System
Inconsistency of board types causes service interruption.
Possible Causes
l Cause 1: The board types are inconsistent.
U2000
Procedure
l Cause 1: The board types are inconsistent. As a result, services are interrupted.
If... Then...
The NE reports the
WRG_BD_TYPEalarm
OptiX OSN 8800/6800/3800
74
If... Then...
WRG_BD_TYPE alarm
causes.

2. Handle the WRG_BD_TYPE alarm.
----End
Related Information
For any capacity expansion, the type of the board to be replaced or added must be consistent
with that of the original board. Especially, when replacing or adding the cross-connect boards
with the active and standby relation, make sure that the types of the active and standby boards
are the same.
NOTE
A list of compatible boards is available. For details, consult technical support engineers of Huawei.
5.10 Service Interruptions on the VCTRUNK Port
This topic describes the symptoms, impact on the system, and possible causes of a service
interruption on the VCTRUNK port. In addition, this topic describes the required tools,
Symptom
The receive end of the Ethernet board reports the ALM_GFP_dLFD or VCAT_LOA alarm,
indicating that the services are interrupted.
Impact on System
The services in the VCG that reports the alarms are interrupted.
Possible Causes
l Cause 1: The board fails to frame the GFP frame. As a result, services are interrupted.
l Cause 2: During the service data transmission, if the alignment delay of the virtual
concatenation is excessively long, a data frame cannot be formed. Accordingly, it causes
the packet loss and even service interruptions.
l Cause 3: The number of timeslots bound with the VCTRUNK at the downstream station
is inconsistent with the number of timeslots bound with the VCTRUNK at the upstream
station. As a result, services are interrupted.
U2000
OptiX OSN 8800/6800/3800
75
Procedure
l Cause 1: The board fails to frame the GFP frame. As a result, services are interrupted
If... Then...
The NE reports the ALM_GFP_dLFD
alarm
ALM_GFP_dLFD alarm
causes.

2. Handle the ALM_GFP_dLFD alarm.
l Cause 2: During the service data transmission, if the alignment delay of the virtual
concatenation is excessively long, a data frame cannot be formed. Accordingly, it causes
the packet loss and even service interruptions.
If... Then...
The NE reports the VCAT_LOA alarm Proceed to the next substep.
VCAT_LOA alarm
causes.

2. Handle the VCAT_LOA alarm.
l Cause 3: The number of timeslots bound with the VCTRUNK at the downstream station
is inconsistent with the number of timeslots bound with the VCTRUNK at the upstream
station. As a result, services are interrupted.
1. On the U2000, query whether the LCAS function of the VCTRUNK port is enabled.
If... Then...
The LCAS function of the VCTRUNK
port is enabled
causes.
The LCAS function of the VCTRUNK
port is disabled
Enable the LCAS function, and then
check whether services recover. If the
services do not recover, check whether
the fault is due to other causes.

----End
OptiX OSN 8800/6800/3800
76
5.11 Service Interruptions on a Single Ethernet Port
This topic describes the symptoms, impact, and possible causes of a service interruption on a
single Ethernet port. In addition, this topic describes the required tools, precautions, and
Symptom
The service on a single Ethernet port of an Ethernet board is interrupted.
Impact on System
The service on a single Ethernet port is interrupted.
Possible Causes
l Cause 1: The configuration is incorrect.
l Cause 2: The fibers, network cables, or optical/electrical modules are faulty.
l Cause 3: The optical module does not match the optical port.
l Cause 4: The board port is faulty.
U2000
Procedure
l Cause 1: The configuration is incorrect. As a result, services are interrupted.
1. On the U2000, query the configuration on the board.
If... Then...
The configuration is incorrect Re-configure the service. Check
whether the service recovers. If the
service does not recover, proceed to the
next step.
The configuration is correct Proceed to the next step.

2. On the U2000, query whether the board port is configured with loopback.
If... Then...
The board port is configured with a
loopback
Release the loopback. Check whether
services recover. If the service does not
recover, proceed to the next step.
The board port is not configured with a
loopback
OptiX OSN 8800/6800/3800
77

3. On the U2000, query the attributes of the port.
If... Then...
The attributes of the port are incorrect Set the attributes of the port again,
including the tag attributes and whether
to enable the port. Check whether
The attributes of the port are correct Proceed to the next step.

4. On the U2000, check whether the working mode of the local port is consistent with
the working mode of the opposite port.
If... Then...
The working mode of the local port is
inconsistent with that of the opposite
port
Set the local port to the same working
mode as the opposite port. Check
consistent with that of the opposite port
causes.

l Cause 2: The fibers, network cables, or optical/electrical modules are faulty. As a result,
services are interrupted.
If... Then...
The NE reports the LINK_ERR alarms Handle the LINK_ERR alarms. Check
LINK_ERR alarms
causes.

l Cause 3: The optical module does not match the optical port. As a result, services are
interrupted.
OptiX OSN 8800/6800/3800
78
If... Then...
The NE reports the
LASER_MODULE_MISMATCH
alarm that indicates the mismatch of the
optical module
Handle the LASER_MODULE_MIS-
MATCH alarm.
Check whether services recover. If the
LASER_MODULE_MISMATCH
alarm that indicates the mismatch of the
optical module
causes.

l Cause 4: The board port is faulty. As a result, services are interrupted.
1. On the U2000, query the data of the Ethernet port on the Ethernet board by using the
remote monitoring (RMON) function.
If... Then...
The Ethernet port receives data, but does
not transmit data
Replace the board. Check whether
to other causes.
The Ethernet port receives and also
transmits data
causes.

----End
5.12 Service Interruptions on All Ethernet Ports
This topic describes the symptoms, impact, and possible causes of a service interruption on all
Ethernet ports of an Ethernet board. In addition, this topic describes the required tools,
Symptom
Services on all Ethernet ports of an Ethernet board are interrupted.
Impact on System
Services on all Ethernet ports are interrupted.
Possible Causes
l Cause 1: The board is offline.
l Cause 2: The configuration is incorrect.
l Cause 3: The ports of the board are faulty.
OptiX OSN 8800/6800/3800
79
U2000
Procedure
l Cause 1: The board is offline. As a result, services are interrupted.
If... Then...
The NE reports the BD_STATUS alarm Handle the BD_STATUS alarm. Check
BD_STATUS alarm
causes.

l Cause 2: The configuration is incorrect. As a result, services are interrupted.
1. On the U2000, query the configuration on the board.
If... Then...
The configuration is incorrect Re-configure the service. Check
whether services recover. If the service
does not recover, proceed to the next
step.
The configuration is correct Proceed to the next substep.

2. On the U2000, query whether the board port is configured with loopback.
If... Then...
The board port is configured with a
loopback
Release the loopback. Check whether
The board port is not configured with a
loopback

3. On the U2000, query the tag attributes of the port on the board.
If... Then...
The attributes of the port are incorrect Re-configure the attributes of the port,
such as the tag attributes and whether to
enable the port. Check whether services
proceed to the next substep.
OptiX OSN 8800/6800/3800
80
If... Then...
The attributes of the port are correct Proceed to the next substep.

4. On the U2000, check whether the working mode of the local port is consistent with
that of the opposite port.
If... Then...
inconsistent with that of the opposite
port
Set the local port to the same working
mode as the opposite port. Check
consistent with that of the opposite port
causes.

l Cause 3: The ports of the board are faulty. As a result, services are interrupted.
1. On the U2000, query the data of the Ethernet ports by using the remote monitoring
(RMON) function.
If... Then...
The Ethernet ports receive data, but do
not transmit data
Replace the board. Check whether
to other causes.
The Ethernet ports receive and transmit
data
causes.

----End
5.13 Service Interruption Cases
This section lists cases related to Service Interruption.
NOTE
The following cases are related to the OptiX WDM product series.
Related Cases:
l MC-A1 The OTU_LOF Alarm is Reporting on the OTU at the Downstream Station
l MC-A4 The LOG Board Fails to Interwork With the FDG Board on the Client Sides. The
LOG board reports the R_LOS alarm on the client side. The FDG board reports the
LINK_STATUS alarm.
l MC-A8 The TN11OAU101 at the Transmit End Reports the MUT_LOS Alarm
l MC-A15 The Downstream Optical Amplifier Board Does Not Report MUT_LOS
OptiX OSN 8800/6800/3800
81
l MC-A24 Low Optical Power on the Client Side of the OTU Board Leads to R_LOS Alarm
on the Board
l MC-A38 The Service Is Interrupted After the Protection Is Triggered
l MC-A45 During the deployment of Raman, the OPU board reports MUT_LOS
l MC-A52 Faults of End Face of the Fiber Connector Cannot Be Identified
l MC-A67 The GE Port on the Client Side Reports LINK_DOWN Alarm
l MC-A69 Shutdown of the RPC Laser Interrupts SDH-Layer Services in a DWDM Network
l MC-A114 LSX Board to which the 10GE LAN service is input reports the OTU_LOF
alarm due to inconsistent settings of the client-side mode
l MC-A117 Analysis and Handling of the ALM_DATA_RLOS and ALM_DATA_TLOS
Alarms Reported by the LBE
l MC-A118 An R_OOF Alarm Occurs When the LWC Interconnects with Third-Party
Equipment
l MC-A147 Services Are Unavailable Due to Inappropriate FEC Configuration on the 40G
Regeneration Boards, The System Reports An OTU_LOF Alarm
l MC-A188 The LDGF2 Board on the OptiX OSN 1800 Reports an OTU1_LOF Alarm
l MC-A200 Fiber Faults Result in Service Interruption, The TDX Board Reports
ODU1_PM_SSF Alarms
l MC-A206 Service Provisioning Fails on an LHP Network, The OTU2_LOF Alarm Is
Reported
l MC-A207 Inaccurate System Commissioning Causes Poor System Performance
l MC-A208 40G Service Provisioning Fails On a Network, The OTU_LOF And
DCM_INSUFF Alarms Are Reported
l MC-A211 OTUk_LOF Alarm Is Reported Due to Mismatched Mapping Modes of the LSX
Boards in the Case of 10GE LAN Services
l MC-A215 Incorrect Configuration of an Added Wavelength During Expansion Results in
Service Interruption of Another Normal Wavelength on an OTU Board, The Corresponding
OTU Board Reports OTU2_LOF Alarm
l MC-A219 EPL Service Is Interrupted Due to Mismatched Service Modes of the L4G
Boards, Sites Report The R_LOF, ODU5G_PM_AIS, OTU5G_LOF And LINK_ERR
Alarms
l MC-A227 Services Cannot Be Provisioned and The LWX2 Boards Report The R_LOC
Alarm Due to Incorrect Service Rates on LWX2 Board of OptiX OSN 1800
l MC-A234 Services Are Interrupted After an Upgrade due to Improper Database
Restoration Operations on the OptiX OSN 6800
l MC-A248 Network Services Are Interrupted After the Equipment Restarts Because the
Wavelengths Conflict After the Wavelength Configurations Are Modified
OptiX OSN 8800/6800/3800
82
6 Transient Service Interruptions
About This Chapter
Transient service interruption refers to the transient loss of signal at the millisecond level during
transmission.
6.1 Transient Interruption of Main Path Services
This section describes the transient interruption of services in the main optical path in terms of
the symptom, impact on the system, possible causes, and handling procedure, as well as the
necessary tools for fault handling and the precautions that should be taken during fault handling.
6.2 Transient Interruption of Single-Channel Services
This section describes the transient interruption of services in a single channel in terms of the
symptom, impact on the system, possible causes, and handling procedure, as well as the
6.3 Transient Service Interruptions on a Single VCTRUNK Port
This topic describes the symptoms, impact, and possible causes of transient service interruptions
on a single VCTRUNK port. In addition, this topic describes the required tools, precautions, and
6.4 Transient Service Interruptions on a Single Ethernet Port
on a single Ethernet port. In addition, this topic describes the required tools, precautions, and
6.5 Transient Service Interruptions Due to Protocol Related Causes
due to protocol-related causes. In addition, this topic describes the required tools, precautions,
and procedures for rectifying the fault.
6.6 Transient Interruption Cases
This section lists cases related to Transient Interruption.
OptiX OSN 8800/6800/3800
Troubleshooting 6 Transient Service Interruptions
83
6.1 Transient Interruption of Main Path Services
This section describes the transient interruption of services in the main optical path in terms of
the symptom, impact on the system, possible causes, and handling procedure, as well as the
Symptom
The OTU, or tributary board and line boards at station B may report the R_LOS, R_LOF,
OTUk_LOF, OTUk_LOM alarms on WDM side, and the alarms clear in a short time. All
services at station B are transiently interrupted.
Figure 6-1 shows an example of the network configuration in this case.
Figure 6-1 Example of the network configuration where all services are transiently interrupted
Client
OTU MUX OA
DEMUX
FIU OTU
MUX
OA DEMUX
Station B (OTM)
FIU
OSC OSC
Station A (OTM)
Client

Impact on System
Services are interrupted for milliseconds at station B.
Possible Causes
l Cause 1: The optical cable or fiber jumper in the multiplexing part is faulty.
l Cause 2: The equipment temperature is too high.
l Cause 3: The optical amplifier board is faulty.
l Cause 4: The FIU board is faulty.
U2000, Cassette cleaner, Fiber jumpers
Procedure
l Cause 1: The optical cable or fiber jumper in the multiplexing part is faulty.
1. Check the fiber jumper in the multiplexing part. If it is loose, secure it; if it is dirty,
clean it; if it is faulty, replace the fiber jumper.
OptiX OSN 8800/6800/3800
84
NOTE
The fiber jumpers in the multiplexing part are the fiber jumpers between:
l The equipment and ODF
l The OA and FIU
l The OA and MUX/DEMUX
l ODFs
l TDC and RDC of the OAU
2. Clear the fault of the optical cable.
If the fault is located in a section of optical line, check:
Whether there are multiple fiber connectors in this section of optical line and
whether they are in good connection
Whether there are aerial optical cables, which are liable to be damaged by the
weather
Whether the type and attenuation coefficient of the optical fiber in this section is
correct
NOTE
The optical line fault is the usual cause which results in a transient interruption. Usually, the
transient interruption caused by a line fault affects all channels (including the OSC). The optical
line fault can be caused by a fiber cut or excessive attenuation.
However, the fiber cut cannot cause a transient interruption. When you have a line fault, find
the cause of excessive attenuation of the fiber and then remove the fault.
1. Check whether the performance data of NE contain alarms such as TEMP_OVER. If
yes, the operating temperature of the board is too high. Check the environmental
conditions of the telecommunications room. Clean the air filter.
2. Check whether the fan tray assembly works normally. If not, replace the fan tray
assembly.
l Cause 3: The optical power fluctuates by the fault of the optical amplifier board.
1. In the case of the DWDM application, on the U2000, query the historical performance
data of optical power of OA board. Check the input and output optical power of the
optical amplifier board. If the input optical power is normal but the output optical
power does not reach the standard output optical power, replace the board.
l Cause 4: The FIU board is faulty.
1. In the case of the DWDM application, replace the FIU board. If the fault clears,
determine that the FIU board is faulty.
----End
6.2 Transient Interruption of Single-Channel Services
This section describes the transient interruption of services in a single channel in terms of the
symptom, impact on the system, possible causes, and handling procedure, as well as the
OptiX OSN 8800/6800/3800
85
Symptom
The IN interface on the WDM side of OTU1 at station C reports the R_LOS, R_LOF, R_OOF,
IN_PWR_LOW, and OTUk_LOF alarms, and the alarms clear in a short time. The services in
a single channel of station C are transiently interrupted.
Figure 6-2 Example of the network configuration where the services in a single channel are
transiently interrupted
Client
OTU1
OTU1
DEMUX
OTM OTM
OTU2
MUX
DEMUX
OA
OTU2
MUX
DEMUX
OA
Client
Station A Station C

Impact on System
Services are interrupted for milliseconds on one channel at station C.
Possible Causes
l Cause 1: The services are configured with protection. When a fault in the working channel
triggers protection switching, the switching times out or occurs frequently.
l Cause 2: The fiber jumper between the MUX/DEMUX and OTU1 is faulty.
l Cause 3: The OTU1 board at station A is faulty.
l Cause 4: The equipment temperature is extremely high.
U2000, Cassette cleaner, Fiber jumpers
Procedure
l Cause 1: The services are configured with protection. When a fault in the working channel
triggers protection switching, the switching times out or occurs frequently.
1. On the U2000, query the historical data of alarms. Check whether the protection
switching alarm exists (the equipment reports a PS alarm when protection switching
occurs). Handle the related protection switching alarm.
l Cause 2: The fiber jumper between the MUX/DEMUX and OTU1 is faulty.
1. Check the fiber jumper. If it is loose, secure it; if it is dirty, clean it; if it is faulty,
replace the fiber jumper.
l Cause 3: The OTU1 board at station A is faulty.
OptiX OSN 8800/6800/3800
86
1. Query on the U2000 the historical performance data of the output optical power of
OTU1 at station A. If the data contains a performance event showing a drastic decline
of output optical power of OTU1 at station A, then OTU1 at station A is faulty. Replace
OTU1 at station A.
l Cause 4: The equipment temperature is extremely high. When the equipment temperature
is extremely high, the wavelength of the single channel deviates and the services are
interrupted.
1. On the U2000, query the historical data of alarms. If alarms such as TEMP_OVER
exists, determine that the operating temperature of the board is extremely high. Check
and lower the temperature in the telecommunications room. Clean the air filter.
2. Check whether the fan tray assembly works normally. If not, replace the fan tray
assembly.
----End
6.3 Transient Service Interruptions on a Single VCTRUNK
Port
on a single VCTRUNK port. In addition, this topic describes the required tools, precautions, and
Symptom
l Symptom 1: The ALM_GFP_dLFD alarm jitter occurs on a single VCTRUNK port of an
Ethernet board, and services recover after a period of interruption.
l Symptom 2: The channel bound to a single VCTRUNK port on an Ethernet board
transiently reports the SDH-related alarms, such as the HP_UNEQ, HP_LOM, and
VCAT_LOA. Services are transiently interrupted.
l Symptom 3: The channel bound to a single VCTRUNK port on an Ethernet board
transiently reports the LCAS_TLCT and LCAS_TLCR bandwidth loss alarms. Services
are transiently interrupted.
Impact on System
The services in the VCG that reports the alarms are interrupted transiently.
Possible Causes
l For symptom 1, the possible causes are as follows:
Cause 1: The fibers on the line side are faulty and recover within a short period.
Cause 2: Bit errors exist on the line.
Cause 1: The configuration of the SDH service is changed manually.
Cause 2: Channel binding is added or deleted on the opposite device manually.
Cause 3: The VCTRUNK port uses multiple lines and the delay of a certain line is too
long.
OptiX OSN 8800/6800/3800
87
Cause 1: The line is faulty and then recovers. As a result, the channel changes to the
WTR state.
U2000, Optical power meter
Procedure
Step 1 For symptom 1: The ALM_GFP_dLFD alarm jitter occurs on a single VCTRUNK port of an
1. Cause 1: The fibers on the line side are faulty and recover within a short period.
a. Query the historical line alarms on the U2000.
If... Then...
The line from the VCTRUNK port of the
local device to the VCTRUNK port of
the opposite device generates the
R_LOS alarm
The line is faulty. Replace the optical
module and the fibers. Check whether
the opposite device does not generate the
R_LOS alarm

b. Check whether the fibers or the line boards are removed and reinserted manually.
If... Then...
The fibers or the line boards are removed
and reinserted manually
Make sure that the fibers or the line
boards is not removed and reinserted
manually. Check whether services
proceed to the next step.
The fibers or the line boards are not
removed and reinserted manually

c. According to the transmission distance, check whether the optical module type is
correct.
OptiX OSN 8800/6800/3800
88
If... Then...
The optical module type is incorrect See the Hardware Description and
Parts Replacement to select a correct
optical module and replace the optical
module on the device with the correct
one. Check whether services recover. If
the services do not recover, proceed to
the next step.
The optical module type is correct Proceed to the next step.

d. Check whether the fibers are faulty.
If... Then...
The fibers are faulty Replace the faulty fibers. Check whether
The fibers are normal Check whether the fault is due to other
causes.

2. Cause 2: Bit errors exist on the line.
a. Query the historical alarms on the U2000.
If... Then...
the opposite device generates the bit
error alarms B3_EXC, B3_SD,
BIP_EXC, or BIP_SD
See the Alarms and Performance Events
Reference to handle the bit error alarm.
bit error alarms B3_EXC, B3_SD,
BIP_EXC, or BIP_SD
causes.

Step 2 For symptom 2: The channel bound to a single VCTRUNK port on an Ethernet board transiently
reports the SDH-related alarms, such as the HP_UNEQ, TU_LOP, HP_LOM, and VCAT_LOA.
Services are transiently interrupted.
1. Cause 1: The configuration of the SDH service is changed manually.
a. On the U2000, query the historical alarms of the VCTRUNK ports of the local and
the opposite devices.
OptiX OSN 8800/6800/3800
89
If... Then...
The VCTRUNK ports of the local and
the opposite devices generate the
alarms, such as the HP_UNEQ and
HP_LOM
Only the VCTRUNK port of the local
device generates the alarms, such as the
HP_UNEQ and HP_LOM
Proceed to Cause 2.

b. Query the operation log on the U2000.
If... Then...
The SDH cross-connection has been
deleted or set up manually
Make sure that the SDH cross-
connection is not manually deleted and
set up again. Check whether services
causes.
The SDH cross-connection has not been
deleted or set up manually
causes.

2. Cause 2: Channel binding is added or deleted on the opposite device manually.
a. On the U2000, query the historical alarms of the VCTRUNK ports of the local and
the opposite devices.
If... Then...
The VCTRUNK ports of the local and
the opposite devices generate the
alarms, such as the HP_UNEQ and
HP_LOM
Proceed to Cause 1.
Only the VCTRUNK port of the local
device generates the alarms, such as the
HP_UNEQ and HP_LOM

If... Then...
Channel binding of the device has been
added or deleted manually
Make sure that channel binding is not
added or deleted on the opposite device
causes.
OptiX OSN 8800/6800/3800
90
If... Then...
Channel binding of the device has not
been added or deleted manually
causes.

3. Cause 3: The VCTRUNK port uses multiple lines and the delay of a certain line is too long.
a. On the U2000, query the historical alarms of the VCTRUNK port of the local device.
If... Then...
The VCTRUNK port of the local device
generates the VCAT_LOA alarm
The VCTRUNK port of the local device
does not generate the VCAT_LOA
alarm
causes.

If... Then...
The SDH cross-connection and channel
binding have been deleted or set up
manually
Make sure that the SDH cross-
connection and channel binding is not
deleted or set up manually. Check
do not recover, proceed to the next step.
The SDH cross-connection and channel
binding have not been deleted or set up
manually

c. Query the historical line alarms on the U2000.
If... Then...
R_LOS alarm
R_LOS alarm

d. Measure the hold-off time of each route.
OptiX OSN 8800/6800/3800
91
If... Then...
The delay of each route is rather long Optimize the network to reduce the
delay of each route. Check whether
to other causes.
The delay of each route is normal Check whether the fault is due to other
causes.

Step 3 For symptom 3: The channel bound to a single VCTRUNK port on an Ethernet board transiently
reports the LCAS_TLCT and LCAS_TLCR bandwidth loss alarms. Services are transiently
interrupted.
1. Cause 1: The line is faulty and then recovers. As a result, the channel changes to the WTR
state.
a. On the U2000, query the historical alarms of the channel used by the VCTRUNK port
of the local device.
If... Then...
The LCAS_TLCT or LCAS_TLCR
alarm is generated
The LCAS_TLCT or LCAS_TLCR
alarm is not generated
causes.

b. Query the historical line alarms on the U2000.
If... Then...
R_LOS alarm
R_LOS alarm

c. Check the configuration of the LCAS parameters on the U2000.
If... Then...
The delay is set short It is recommended that you set the WTR
time to the default 300s and the delay to
the default 2s.
The delay are set properly Contact the Huawei engineers.
OptiX OSN 8800/6800/3800
92

NOTE
l When the network is stable, the WTR time should not be set too long; otherwise, the
interruption time of the services after the restoration of the network is long. If the channel
does not need to enter the WTR time, the WTR time can be set to 0s.
l The delay should not be set too short; otherwise, when the network is unstable, the channel
changes to the WTR state frequently. As a result, services are interrupted. It is
recommended that you set the delay to 2s.
----End
Related Information
None
6.4 Transient Service Interruptions on a Single Ethernet Port
on a single Ethernet port. In addition, this topic describes the required tools, precautions, and
Symptom
l Symptom 1: The LINK_ERR alarm jitter occurs on a single Ethernet port of an Ethernet
board that works in auto-negotiation mode, and services recover after a period of
interruption.
l Symptom 2: The ETH_CFM_LOC alarm jitter occurs on a single Ethernet port of an
Impact on System
Services on the Ethernet port are transiently interrupted.
Possible Causes
Cause 1: Optical fibers in the transmit direction of the local Ethernet port are faulty and
recover within a short period.
Cause 2: The port interconnected to the Ethernet port switches between the auto-
negotiation mode and the fixed mode continuously.
Cause 3: The board is faulty.
Cause 1: Optical fibers in the receive direction of the Ethernet port are faulty and recover
within a short period.
Cause 2: The port interconnected to the Ethernet port is disabled or enabled within a
short period.
Cause 3: The board is faulty.
OptiX OSN 8800/6800/3800
93
U2000, Optical power meter
Procedure
l For symptom 1: The LINK_ERR alarm jitter occurs on a single Ethernet port of an Ethernet
board that works in auto-negotiation mode, and services recover after a period of
interruption.
1. Cause 1: Optical fibers in the transmit direction of thelocal Ethernet port are faulty
and recover within a short period.
a. Query the historical alarms of the port of the interconnected device on the
U2000.
If... Then...
The ETH_CFM_LOC alarm exists Indicates that the fibers in the transmit
direction of the local Ethernet port
have been broken. As a result, the
negotiation fails at the local end and
the LINK_ERR alarm is reported
accordingly. In this case, services are
transiently interrupted. Check
whether services recover. If the
services do not recover, proceed to the
next step.
The ETH_CFM_LOC alarm does not
exist

Query the historical alarms of the interconnected port of the device on the
U2000.
If... Then...
The fibers or the line boards are

c. According to the transmission distance, check whether the optical module types
are correct.
OptiX OSN 8800/6800/3800
94
If... Then...
The optical module type is incorrect Select a correct optical module and
replace the optical module on the
device with the correct one. Check
next step.

If... Then...
The fibers are faulty Replace the faulty fibers. Check
next step.
causes.

2. Cause 2: The port interconnected to the Ethernet port switches between the auto-
negotiation mode and the fixed mode continuously.
a. Query the operation log on the U2000.
If... Then...
The working mode of the
interconnected port is changed
manually
Indicates that the service transient
interruption is caused by the
mismatch of the working mode. Make
sure that the operation mode of the
interconnected port is not changed
causes.
The working mode of the
interconnected port is not changed
manually
causes.

3. Cause 3: The board is faulty.
a. Replace the board.
b. Check whether services recover. If the services do not recover, check whether
l For symptom 2: The ETH_CFM_LOC alarm jitter occurs on a single Ethernet port of the
Ethernet board, and the services recover after a period of interruption.
OptiX OSN 8800/6800/3800
95
1. Cause 1: Optical fibers in the receive direction of the Ethernet port are faulty and
recover within a short period.
a. Query the historical alarms of the Ethernet port on the U2000.
If... Then...
The ETH_CFM_LOC alarm exists Indicates that the fibers in the receive
direction of the local Ethernet port
have been broken. Proceed to the next
step.
The ETH_CFM_LOC alarm does not
exist
causes.

Query the historical alarms of the interconnected port of the device on the
U2000.
If... Then...
The fibers or the line boards are

c. According to the transmission distance, check whether the optical module types
are correct.
If... Then...
The optical module type is incorrect Select a correct optical module and
replace the optical module on the
device with the correct one. Check
next step.

If... Then...
The fibers are faulty Replace the faulty fibers. Check
next step.
OptiX OSN 8800/6800/3800
96
If... Then...
causes.

2. Cause 2: The port interconnected to the Ethernet port is disabled or enabled.
If... Then...
The port interconnected to the
Ethernet port is disable or enabled
manually
Make sure that these ports are not
enabled or disabled manually. Check
services do not recover, check
whether the fault is due to other
causes.
The port interconnected to the
Ethernet port is not disable or enabled
manually
causes.

3. Cause 3: The board is faulty.
a. Replace the board.
b. Check whether services recover. If the services do not recover, check whether
----End
Related Information
None
6.5 Transient Service Interruptions Due to Protocol Related
Causes
due to protocol-related causes. In addition, this topic describes the required tools, precautions,
and procedures for rectifying the fault.
Symptom
l Symptom 1: The Rapid Spanning Tree Protocol (RSTP) is enabled, but the status of the
protocol jitters and the services are transiently interrupted.
l Symptom 2: The Link Aggregation Control Protocol (LACP) is enabled, but the status of
the protocol jitters and the services are transiently interrupted.
Impact on System
The services are transiently interrupted.
OptiX OSN 8800/6800/3800
97
Possible Causes
Cause 1: The network topology is changed and the RSTP protocol reconstructs the
network topology.
Cause 2: The RSTP protocol is reset.
Cause 3: The RSTP protocol packets are lost. As a result, the status of the protocol
jitters.
Cause 1: The NE reports the LAG_PORT_FAIL alarm and the services are transiently
interrupted.
Cause 2: The LACP protocol is reset and the services are transiently interrupted.
U2000
Procedure
l For symptom 1: The RSTP protocol has been enabled, but the state of the protocol jitters
and the services are transiently interrupted.
1. Cause 1: The network topology is changed and the RSTP protocol reconstructs the
network topology.
a. Check whether the network topology is changed manually.
If... Then...
The network topology is changed
manually
The transient service interruption is
caused by the reconstruction of the
network topology implemented by
the RSTP protocol.
The network topology is not changed
manually

b. Query the historical alarms on the U2000.
If... Then...
The service interruption alarms are
reported, such as the
ETH_CFM_LOC and
LINK_ERRLINK-ERR alarms of the
Ethernet port and the UNEQ and
TU_LOP alarms on the SDH side
After the link is faulty, the services
are transiently interrupted due to the
reconstruction of the network
topology by the RSTP protocol.
OptiX OSN 8800/6800/3800
98
If... Then...
The service interruption alarms are
not reported, such as the
ETH_CFM_LOC and
LINK_ERRLINK-ERR alarms of the
Ethernet port and the UNEQ and
TU_LOP alarms on the SDH side
causes.

2. Cause 2: The RSTP protocol is reset.
If... Then...
Before the services are interrupted,
the RSTP protocol has been reset or
the board has been warm reset
manually
The service interruption is caused by
the reset of the RSTP protocol.
the RSTP protocol has not been reset
or the board has been warm reset
manually
causes.

NOTE
After the board is warm reset, the RSTP protocol is restarted automatically.
3. Cause 3: The RSTP protocol packets are lost. As a result, the status of the protocol
jitters.
a. Check the traffic flow of the services, and then check whether the QoS function
is enabled according to the service configuration.
If... Then...
The QoS function is enabled and the
bandwidth is insufficient
The state jitter of the RSTP protocol
is caused by the loss of the RSTP
protocol packets.
The QoS is not enabled Check whether the fault is due to other
causes.

NOTE
Generally, the priority of the protocol packets is higher than the priority of the service
packets. If the QoS function is enabled, the priority of the service packets may be higher
than that of the protocol packets. In this case, the protocol packets may be discarded when
the bandwidth is insufficient.
l For symptom 2: The LACP protocol has been enabled, but the state of the protocol jitters
and the services are transiently interrupted.
OptiX OSN 8800/6800/3800
99
1. Cause 1: The NE reports the LAG_PORT_FAIL alarm and the services are transiently
interrupted.
a. Check the current alarms on the U2000.
If... Then...
The NE reports the
LAG_PORT_FAIL alarm
Handle the LAG_PORT_FAIL
alarm. Check whether services
causes.
LAG_PORT_FAIL alarm
causes.

2. Cause 2: The LACP protocol is reset and the services are transiently interrupted.
If... Then...
the LACP protocol has been reset or
the board has been warm reset
manually
The service interruption is caused by
the reset of the LACP protocol.
the LACP protocol has not been reset
or the board has been warm reset
manually
causes.

NOTE
After the board is warm reset, the LACP protocol is restarted automatically.
----End
Related Information
None
6.6 Transient Interruption Cases
This section lists cases related to Transient Interruption.
NOTE
Related Cases:
OptiX OSN 8800/6800/3800
100
l MC-A5 The LQG Board Reports the ALM_DATA_RLOS and ALM_DATA_TLOS
Alarms Transiently
l MC-A6 The LDG Board Keeps Reporting the ALM_DATA_TLOS and
ALM_DATA_RLOS Alarms Transiently
l MC-A36 The OTU in the OptiX BWS 1600G Reports IN_PWR_LOW Alarm
OptiX OSN 8800/6800/3800
101
7 Optical Power Abnormity
About This Chapter
Correct optical power is critical to the performance of the WDM system. If the input optical
power is too high or too low, the system will generate bit errors, or even interrupt services.
7.1 Abnormal Decline of the Optical Power
This section introduces the analysis and handling of the fault of drastic optical power decline.
7.2 Optical Power Abnormity Cases
This section lists cases related to Optical Power Abnormity.
OptiX OSN 8800/6800/3800
Troubleshooting 7 Optical Power Abnormity
102
7.1 Abnormal Decline of the Optical Power
This section introduces the analysis and handling of the fault of drastic optical power decline.
Symptom
The optical power of all OTUs in the local station sharply declines, and the optical signal-to-
noise ratio (OSNR) is lower than the OSNR tolerance of the OTU.
NOTE
Lower OSNR is caused by lower receiving optical power.
Figure 7-1 Networking configuration example of drastic decline of optical power
To OTUs
and client
equipment
MUX OA
DEMUX
Station A (OTM)
FIU
MUX
OA DEMUX FIU
To OTUs
and client
equipment
Station B (OTM)

Impact on System
A large number of bit errors occur in the services and the services are transiently interrupted
frequently.
Possible Causes
l Cause 1: Any fiber jumper in the multiplexing part, or an optical cable degrades or is
physically damaged.
l Cause 2: The gain of the optical amplifier board in the upstream station or downstream
station declines.
U2000, Optical power meter, Cassette cleaner, Ring fiber adapter
Procedure
l Cause 1: Any fiber jumper in the multiplexing part, or an optical cable degrades or is
physically damaged. Hence, the attenuation of the fiber increases and the received optical
power declines. As a result, the OSNR decreases.
OptiX OSN 8800/6800/3800
103
1. Refer to Checking Fiber Jumpers by Using an Optical Power Meter. Check whether
the fiber jumper in the multiplexing part is faulty. If yes, replace the fiber jumper.
2. Remove the fault of the optical cable.
NOTE
l The OA and FIU
l ODFs
l Cause 2: The gain of the optical amplifier board in the upstream station or downstream
station declines.
1. Check whether the gain of the optical amplifier board is abnormal. If yes, replace the
board.
----End
7.2 Optical Power Abnormity Cases
This section lists cases related to Optical Power Abnormity.
NOTE
Related Cases:
l MD-A13 Bit Error Alarm (BEFFEC_EXC) Is Generated When Optical Power Gets Close
to the Threshold
l MC-A15 The Downstream Optical Amplifier Board Does Not Report MUT_LOS
l MC-A19 Use Power Monitoring To Process Problems on IN_PWR_LOW Alarm
l MC-A24 Low Optical Power on the Client Side of the OTU Board Leads to R_LOS Alarm
on the Board
l MC-A35 LWM Output Optical Power Is Unstable upon Forced Light Generation
l MC-A36 The OTU in the OptiX BWS 1600G Reports IN_PWR_LOW Alarm
l MC-A43 Too High Insertion Loss Between TDC and RDC of the E3OAUC01C
l MC-A45 During the deployment of Raman, the OPU board reports MUT_LOS
l MC-A52 Faults of End Face of the Fiber Connector Cannot Be Identified
l MC-A54 After the Lasers of the Raman Amplifier Are Disabled, the Optical Power Is
Abnormal
l MC-A62 The Minimum Optical Power of the SC2 Is Detected As -35 dBm
l MC-A66 The Received Optical Power of Downstream Stations Is not Flat and Some
Wavelengths Report the IN_PWR_LOW Alarm
l MC-A68 OTU Boards Report the IN_PWR_LOW Alarm Due to Wavelength Wander
OptiX OSN 8800/6800/3800
104
l MC-A90 The Incorrect Configuration of DWC Leads To Abnormal Optical Power and
Service Interruption, the WDM Side of the LBE Reports the IN_PWR_HIGH and
OTU_LOF Alarms Abruptly
l MC-A93 The Input Optical Power of the OTU Board Is Abnormal Due to a Fault of the
OPU Board
l MC-A101 The Wavelength Is Unstable or Changed Due to Optical Power Variation
l MC-A126 VA4 Board Reports R_LOS When the Receiver Power Is Below -23 dBm Even
If the Attenuation Is Decreased
l MC-A169 T2000 Reports Errors After the Standard Optical Power of Single Wavelength
Is Set to 7 dBm with ALC in Power Reference Mode
l MC-A174 Excessive PDL of Fiber Results in Slow Changes of the Received Optical Power
on an OTU Board
l MC-A182 Receive Optical Power Is Excessively Low Because of the End Face Problem
of the Fiber Jumper, the OAU Board Reports the MUT_LOS Alarm
l MC-A186 Inconsistency of Fiber Jumper Model and Fiber Connector Type of a Board
Causes Low Receive Optical Power, The Connected OAU Board At The Downstream
Station Reports MUT_LOS And R_LOS Alarms
l MC-A194 A Malfunctioning VA1 Board Causes Abnormal Optical Power, The NS2
Boards Reports IN_PWR_HIGH Alarms For Three Times
l MC-A196 The Insertion Loss of the FIU Board on OptiX OSN 6800 Is High Because the
Fiber and Fiber Connector Are Not Securely Connected
l MC-A198 Optical Power Can Be Detected at the IN and OUT Ports of the FIU Board
Because of Incorrect Connections of Fiber Patch Cords
l MC-A201 Frequent Fiber Cut Results in High Line Attenuation and the IN_PWR_LOW
Alarm Reported by the OTU Board
l MC-A203 System of Few Wavelengths Fails to Function
l MC-A239 Inappropriate Line Optical Power Adjustment Causes Deteriorated 40G
Performance
l MC-A242 Excessively High Incident Optical Power Results in Poor Performance of OTU
Boards
l MC-A244 The Insertion Loss of a Board Is Abnormal
OptiX OSN 8800/6800/3800
105
8 Bit Errors
About This Chapter
Bit errors refer to the errors that occur in transmitted bit stream. Bit errors are usually represented
by bit. In the SDH/SONET frame structure, bytes for monitoring bit errors include B1, B2, M1,
B3, and G1. However, in DWDM equipment, the OTU only provides non-intrusive monitoring
on B1. In the OTN frame structure, for the DWDM equipment, the OTU provides bit errors
monitoring on BIP8 bytes of SM, PM and TCM section.
8.1 Multi-Channel Bit Errors
This section introduces the analysis and handling of bit errors on multiple channels.
8.2 Single-Channel Bit Errors
This section introduces the analysis and handling of bit errors on one channel.
8.3 Bit Errors Due to Unfavorable Environmental Conditions
This topic describes the symptoms, impact, and possible causes of bit errors due to unfavorable
environmental conditions. In addition, this topic describes the required tools, precautions, and
8.4 Bit Errors Due to Device Faults
This topic describes the symptoms, impact, and possible causes of bit errors due to device faults.
In addition, this topic describes the required tools, precautions, and procedures for rectifying the
fault.
8.5 Bit Error Cases
This section lists cases related to Bit Errors.
OptiX OSN 8800/6800/3800
Troubleshooting 8 Bit Errors
106
8.1 Multi-Channel Bit Errors
This section introduces the analysis and handling of bit errors on multiple channels.
Symptom
The optical power is normal but a large number of bit errors occur in services on multiple
channels.
The OTU, or tributary board and line board reports alarms such as OTUk_EXC, OTUk_DEG,
BEFFEC_EXC, B1_EXC, and B1_SD.
Figure 8-1 Networking configuration example of multi-channel bit errors
To OTUs
and client
equipment
MUX OA
DEMUX
Station A (OTM)
FIU
MUX
OA DEMUX FIU
To OTUs
and client
equipment
Station B (OTM)

Impact on System
A large number of bit errors occur in services on multiple channels.
Possible Causes
l Cause 1: The attenuation of the optical cable or that of the fiber jumper in the multiplexing
part is too large.
l Cause 3: The configuration of the dispersion compensation module (DCM) is improper.
l Cause 4: The optical power of the main path is faulty.
l Cause 5: The non-linearity of the optical fiber. Bit errors can be caused by the non-linearity
of the optical power but not often.
l Cause 7: The PMD exceeds the permitted range.
CAUTION
Multi-channel bit errors might be caused by the improper commissioning of the optical power
of the system, please check the optical power of system.
OptiX OSN 8800/6800/3800
107
U2000, Optical power meter, Cassette cleaner, Ring fiber adapter
Procedure
l Cause 1: The attenuation of the optical cable or that of the fiber jumper in the multiplexing
part is too large.
1. Refer to Checking Fiber Jumpers by Using an Optical Power Meter. Check whether
the fiber jumper in the multiplexing part is faulty. If yes, replace the fiber jumper.
2. Remove the fault of the optical cable.
NOTE
l The OA and FIU
l ODFs
1. Check whether the NE generates alarms such as TEMP_OVER. If yes, check the
environmental conditions of the telecommunications room. Clean the air filter.
l Cause 3: The configuration of the dispersion compensation module (DCM) is improper.
1. Check optical cable parameters such as the type and actual length of the optical cable.
Check the configuration of the DCM. After that, adjust the compensation distance of
the DCM to a value that matches the actual length of the optical cable.
l Cause 4: The optical power of the main-path is abnormal.
1. Check the input and output optical power of boards between MUX of the transfer
station and the DEMUX of the receive station. If the input optical power is normal
but the output optical power does not reach the standard output optical power, replace
the board.
l Cause 5: The non-linearity of the optical fiber. Bit errors can be caused by the non-linearity
of the optical power but not often.
1. Decrease or increase the optical power, to judge whether bit errors are caused by the
non-linearity of the optical fiber.
Increasing optical power causes bit errors to increase.
Decreasing optical power causes bit errors to decrease.
2. Increase the value of attenuator.
NOTE
Perform this procedure only after all other possible causes have been checked.
1. Check the ring fiber adapter between the ODF and WDM equipment. If the ring fiber
adapter is faulty, replace it.
l Cause 7: The PMD exceeds the permitted range.
OptiX OSN 8800/6800/3800
108
1. Test the PMD of optical fibers in all spans to obtain the PMD values. Resplice the
splicing points of optical fibers with very large PMD and resplice the splicing points
with large attenuation. The attenuation of optical fibers will improve.
2. The PMD values of several spans are larger than the recommended value in the system
design. It is recommended that the fiber core be replaced to ensure that the total PMD
value of optical fibers between electrical regenerators of all channels is smaller than
the system design. In this manner, the system can work stably in the long run and the
system instability caused by large PMD can be resolved radically.
NOTE
The 40G services require a smaller PMD. When the accumulated PMD exceeds the threshold, a large
OSNR penalty will be introduced, deteriorating the system performance. In a short period of time, high
PMD leads to the generation of the BEFFEC_EXC alarm for some wavelengths and irregular changes to
the receive-end system performance.
----End
8.2 Single-Channel Bit Errors
This section introduces the analysis and handling of bit errors on one channel.
Symptom
The OTU, or tributary board and line board reports alarms such as OTUk_EXC, OTUk_DEG,
BEFFEC_EXC, B1_EXC, and B1_SD.
Figure 8-2 Networking configuration example of single-channel bit errors
Client
equipment
OTU1 OTU1
Station A (OTM)
OTUn
MUX
DEMUX
OA
OTUn
MUX
DEMUX
OA
Client
equipment
Station B (OTM)

Impact on System
A large number of bit errors occur in one channel and the services are transiently interrupted.
Possible Causes
l Cause 1: The input optical power of the OTU, or tributary board and line board on the
WDM side is abnormal.
l Cause 2: The fiber jumper between the MUX and ODF is aged or bent. Hence, the
attenuation of the fiber jumper is too large.
OptiX OSN 8800/6800/3800
109
l Cause 4: The FEC modes of the two interconnected boards might be different.
l Cause 5: The optical interfaces of the OTU, or tributary board and line boards are dirty.
l Cause 6: The OTU, or tributary board and line board is faulty.
Procedure
l Cause 1: The input optical power of the OTU, or tributary board and line board on the
WDM side is abnormal.
1. Checking fiber jumpers by using an optical power meter. Check whether the input
optical power of the OTU, or tributary board and line board is too low. If yes, clean
the fiber.
l Cause 2: The fiber jumper between the OTU, or tributary board and line board, MUX/
DMUX or the fiber jumper between the MUX and ODF is aged or bent. Hence, the
attenuation of the fiber jumper is too large.
1. Replace the fiber jumper.
1. Check whether the NE contains alarms such as TEMP_OVER. If yes, the operating
temperature of the board is too high. Check the environmental conditions of the
telecommunications room. Clean the air filter.
l Cause 4: The FEC modes of the two interconnected boards might be different.
1. Query the FEC mode of the two interconnected boards on the U2000. If the two modes
differ, re-set the FEC Working state and ensure state matching.
l Cause 5: The optical interfaces of the OTU, or tributary board and line board board are
dirty.
1. If the optical interfaces of the OTU, or tributary board and line board board are dirty,
blow them with compressed gas to clean them.
l Cause 6: The OTU, or tributary board and line board is faulty.
1. If the fiber jumper, input optical power and operating temperature are normal, and the
FEC modes of the OTU, or tributary board and line boards are matching, replace the
OTU, or tributary board and line board at receive end. If the bit errors disappear, it
indicates that the OTU, or tributary board and line board at receive end is faulty.
2. If the OTU, or tributary board and line board at receive end is normal, replace the
OTU, or tributary board and line board at transmit end. If the bit errors disappear, it
indicates that the OTU, or tributary board and line board at transmit end is faulty.
----End
OptiX OSN 8800/6800/3800
110
8.3 Bit Errors Due to Unfavorable Environmental
Conditions
This topic describes the symptoms, impact, and possible causes of bit errors due to unfavorable
environmental conditions. In addition, this topic describes the required tools, precautions, and
Symptom
The telecommunications room of a certain site does not meet the environmental requirements
of a device. The device reports bit errors.
Impact on System
Unfavorable environmental conditions may cause bit errors in services.
Possible Causes
l Cause 1: The temperature and humidity of the environment do not meet the environmental
requirements of a device.
l Cause 2: A strong external interference source exists.
l Cause 3: The grounding is improper.
l Cause 4: The cable is faulty.
U2000, Thermometer, Humidiometer
Procedure
l Cause 1: The temperature and humidity of the environment do not meet the requirements
of long term running of the device. As a result, bit errors are generated.
1. Check whether the temperature and humidity of the environment meet the
requirements.
Temperature: 0C to +45 C (32F to 113F)
Relative humidity: 10% to 90%
OptiX OSN 8800/6800/3800
111
If... Then...
environment do not meet the
requirements
Check and adjust the air conditioner in
the telecommunications room to make
sure that the temperature and humidity
of the telecommunications room are in
the proper range. Check whether the bit
errors persist. If the bit errors persist,
causes.

If... Then...
The NE reports the temperature
Handle the temperature threshold-
crossin alarms. Check whether the bit
errors persist. If the bit errors persist,
causes.
causes.

l Cause 2: A strong external interference source exists. As a result, bit errors are generated.
1. Check whether there is a transformer, high-voltage transmission line, or high-current
device near the device.
If... Then...
There is an AC transformer within 20 m
of the device
device. Check whether the bit errors
persist. If the bit errors persist, check
whether the fault is due to other causes.
There is no AC transformer within 20 m
of the device

2. Check whether there is a high-power broadcasting transmitter near the device.
OptiX OSN 8800/6800/3800
112
If... Then...
There is a high-power broadcasting
the device
There is not a high-power broadcasting
the device

3. Check whether there is a mobile communication transmitter near the device.
If... Then...
There is a mobile communication
There is not a mobile communication

4. Check whether a hand-held mobile communication device is in use near the device.
If... Then...
A hand-held mobile communication
Switch off the hand-held mobile
communication device. Check whether
the bit errors persist. If the bit errors
persist, check whether the fault is due to
other causes.
No hand-held mobile communication
causes.

l Cause 3: The grounding is improper.
1. Check whether the ground bar in the telecommunications room is properly connected.
If yes, proceed to the next step. If not, connect the ground bar properly.
2. Check whether the ground bar is properly connected with the cabinet of the
transmission equipment. If yes, proceed to the next step. If not, connect the ground
bar properly.
OptiX OSN 8800/6800/3800
113
3. Check whether the front door and side panel of the cabinet are properly connected to
the cabinet. If yes, proceed to the next step. If not, connect the front door and side
panel to the cabinet properly.
4. Check whether the subrack is connected to the cabinet properly. If yes, proceed to the
next step. If not, connect the subrack to the cabinet properly.
5. Check whether the DDF and ODF are properly grounded. If yes, proceed to the next
step. If not, ground the DDF and ODF properly.
6. Check whether the NMS devices and all power-consumption devices are properly
grounded. If yes, proceed to the next step. If not, ground the devices properly.
7. Check whether the interconnected equipment is jointly grounded.
l Cause 4: The cable is faulty.
1. Test the transmit optical power of the board at the opposite end and the receive optical
power of the board at the local end.
2. The difference between the transmit optical power and the receive optical power is
the actual loss of optical power on the line. If the difference varies much with the
design value of the line attenuation, locate and clear the fault using the following steps.
Check whether the bending radius of fibers is equal to or larger than standard. If
the bending radius is smaller than standard, route the fiber again.
Check whether the multiple fiber connectors are correctly connected on the line.
If certain connectors are badly connected, push the connectors into the optical
module and ensure that the connectors are caught tightly.
Check whether there are aerial optical fiber cables on the line. If yes, provide
external protection to the cables because they are easily affected by the weather.
Check the optical fiber type and the attenuation coefficient of the line. Ensure that
the type and attenuation coefficient are consistent with the design document. If
they are inconsistent with the design document, replace the fiber.
Check whether the fiber connectors are dirty. If the fiber connectors are dirty, clean
them immediately.
3. Check whether services recover. If not, proceed to other causes.
----End
Related Information
Table 8-1 lists the requirement for the electromagnetic interference.
Table 8-1 Requirements of the electromagnetic interference
Low-frequency magnetic
field
Frequency (Hz) 50 to 20000
Ampl. A/m (rms) 10 to 0.025
Amplitude-modulated
radio-frequency electrical
field
Frequency (MHz) 0.009 to 1000
Ampl. V/m (rms) 3
OptiX OSN 8800/6800/3800
114
Impulse-modulated radio-
frequency electrical field
Frequency (GHz) 1 to 20
Ampl. (V/m (peak)) 3

Table 8-2 Minimum bending radius for fibers
Fiber Type Minimum Bending Radius
G.652D 30 mm
Multi-mode fiber (A1B) 30 mm
G.657A2 10 mm
G.657B3 8 mm
Note: When fibers are connected to CRPC boards, the bending radius of the fibers must be
greater than or equal to 50 mm to ensure expected transmission performance.

8.4 Bit Errors Due to Device Faults
This topic describes the symptoms, impact, and possible causes of bit errors due to device faults.
In addition, this topic describes the required tools, precautions, and procedures for rectifying the
fault.
Symptom
Large amounts of regeneration section bit errors and multiplex section bit errors are generated
on the line.
Impact on System
Device faults cause bit errors.
Possible Causes
l Cause 1: The clock unit is faulty.
l Cause 2: The cross-connect unit is faulty.
l Cause 3: The line board is faulty.
U2000
OptiX OSN 8800/6800/3800
115
Procedure
Step 1 Cause 1: The clock unit is faulty. As a result, bit errors are generated.
1. Check the configuration of the clock on the NE.
If... Then...
The configuration of the clock on the NE
is incorrect
Re-configure the clock on the NE. Check
whether the bit errors persist. If the bit
errors persist, proceed to the next step.
is correct

2. Check the configuration of the clock on the network.
If... Then...
is incorrect
Re-configure the clock on the NE. Check
whether the bit errors persist. If the bit
errors persist, proceed to the next step.
is correct

3. The clock unit is faulty.
a. Replace the faulty board.
b. Check whether services recover. If the services do not recover, check whether the fault
Step 2 Cause 2: The cross-connect unit is faulty. As a result, bit errors are generated.
1. Replace the faulty board.
2. Check whether services recover. If the services do not recover, check whether the fault is
due to other causes.
Step 3 Cause 3: The line board is faulty. As a result, bit errors are generated.
----End
Related Information
After the device reports bit errors, you need to analyze the features of the bit errors to locate the
fault to a single site.
You can use the loopback method to locate faults to a board of a certain site, and then use the
replacement method to reset or replace the doubted board.
OptiX OSN 8800/6800/3800
116
8.5 Bit Error Cases
This section lists cases related to Bit Errors.
NOTE
Related Cases:
l MD-A13 Bit Error Alarm (BEFFEC_EXC) Is Generated When Optical Power Gets Close
to the Threshold
l MC-A16 The R_LOF and R_OOF Alarms Are Reported in the 24-Hour Bit Error Test
Because the Line Fiber Loss Is Very Large
l MC-A31 Wrong Calculation for Dispersion in One DWDM Project
l MC-A40 Over Compensation Causes Very High Bit Error Rate of the Short Waves After
Correction and the SM_BIP8_OVER and SM_BIP8_SD Alarms Are Transiently Reported
on the Board
l MC-A44 Bit Errors Generated in the Services, the Meter Reports the HP_RDI and ERROR
Alarms
l MC-A55 Improper DCM Distribution Causes Abnormal Service and Bit Error Alarm
BEFFEC_EXC Is Detected on the Newly-added LWFS Board
l MC-A63 MSBBE Bit Errors and OTU_LOF Alarm Occur in a DWDM 10G Network Due
to the Incorrect PMD
l MC-A88 The OTU Board Reports the B1_EXC Alarm, And There Are the Difference in
BER Reported by the OTU Board and Test Instrument
Equipment
l MC-A124 Determine the Factors That Affect the OSNR By Using the ANT30 Tester
l MC-A199 An OTU Board Reports Bit Errors Due to High Fiber Reflection
l MC-A202 Mixing Compensation of DCMs Results in the Inconsistency of Channel
Performance
l MC-A205 WDM-Side Pre-FEC BER Changes Drastically
l MC-A240 Isolated Bit Errors Are Found in the Long-Term Bit Error Testing of a 40G
System
OptiX OSN 8800/6800/3800
117
9 A Fault in Pointer Justification
About This Chapter
The scenario is applicable to only the OptiX OSN 8800. This topic describes the common
methods and measures that can be adopted to rectify a fault in pointer justification.
9.1 Pointer Justification Due to Incorrect Clock Configuration
This topic describes the symptoms, impact, and possible causes of the pointer justification due
to the incorrect clock configuration. In addition, this topic describes the required tools,
9.2 Pointer Justification Due to Over-High Temperature and Humidity
to over-high temperature and humidity. In addition, this topic describes the required tools,
9.3 Pointer Justification Due to Over-Low Precision of the External Clock Source
to the over-low clock source precision. In addition, this topic describes the required tools,
OptiX OSN 8800/6800/3800
Troubleshooting 9 A Fault in Pointer Justification
118
9.1 Pointer Justification Due to Incorrect Clock
Configuration
to the incorrect clock configuration. In addition, this topic describes the required tools,
Symptom
After the fibers of a network are broken, services of respective NEs are switched normally. The
AU and TU pointer justifications, however, occur on the line, and this is accompanied by bit
errors. The pointer justification frequency and the bit error rate increase with time.
Impact on System
Incorrect clock configuration causes pointer justification.
Possible Causes
l Cause 1: The clock configuration is incorrect.
U2000
Procedure
Step 1 Cause 1: Incorrect clock configuration causes pointer justification.
1. Check whether the transmit network traces two or more clock sources and whether the
clock sources trace each other, which results in the pointer justification. If the configuration
is correct, proceed to the next step.
2. Check whether the precision of the traced clock source is low or there are too many tracing
sites. If the configuration is correct, proceed to the next step.
NOTE
Provide clock compensation for long clock chain: the number of G.812 slave clocks in a transmission
link should not be more than 10; the number of G.813 clocks between two G.812 slave clocks should
not be more than 20; the number of G.813 clocks between the G.811 and G.812 slave clocks should
not be more than 20; the number of G.813 slave clocks should not be more than 60.
3. Check whether the clock protection subnet is not configured. After the main clock is lost
(or the fiber is broken), the non-protection of the clock causes the pointer justification. If
the configuration is correct, proceed to the next step.
4. Check whether the priority configuration of the clock source is correct. After the clock
protection switching, clocks begin to trace each other, which results in the pointer
justification. If the configuration is correct, proceed to the next step.
5. Check whether the internal clock source of the main clock NE is configured with the clock
source ID. After the clock source of a higher level is lost, the NE enters the free-run mode.
Other NEs will not synchronize to the central site. As a result, all NEs in this clock subnet
OptiX OSN 8800/6800/3800
119
are in the free-run mode. Thus the pointer justification occurs accordingly. If the
configuration is correct, proceed to the next step.
6. Check whether the SSM clock protection is enabled. When the clock quality deteriorates,
the protection switching cannot be executed, thus causing the pointer justification. If the
configuration is correct, proceed to the next step.
7. When the settings of the SSM mode on the network are different, the NE with the SSM
mode enabled cannot extract the line clock of other NEs. In this case, the NE enters the
free-run mode, thus causing the pointer justification.
----End
Related Information
None
9.2 Pointer Justification Due to Over-High Temperature and
Humidity
to over-high temperature and humidity. In addition, this topic describes the required tools,
Symptom
The telecommunications room of a certain site does not meet the requirements of device running,
and the AU and TU pointer justifications occur on the line.
Impact on System
Over-high temperature and humidity cause pointer justification.
Possible Causes
l Cause 1: The temperature and humidity of the environment do not meet the requirements
of long term running of the device.
U2000, Thermometer
Procedure
Step 1 Cause 1: The temperature and humidity of the environment do not meet the requirements of long
term running of the device. As a result, the pointer justification occurs.
1. Check whether the temperature and humidity of the environment meet the requirements.
l Temperature: 0C to +45 C
l Relative humidity: 10% to 90%
OptiX OSN 8800/6800/3800
120
If... Then...
environment do not meet the requirements
Check and adjust the air conditioner in the
telecommunications room to make sure
that the temperature and humidity of the
telecommunications room are in the proper
range. Check whether the pointer
justification persists. If the pointer
justification persists, check whether the
fault is due to other causes.

If... Then...
The NE reports the temperature threshold-
crossing alarms TEMP_OVER
See the Alarms and Performance Events
Reference to handle the TEMP_OVER
alarms. Check whether the pointer
justification persists. If the pointer
justification persists, check whether the
threshold-crossing alarms TEMP_OVER
Contact Huawei engineers.

----End
Related Information
None
9.3 Pointer Justification Due to Over-Low Precision of the
External Clock Source
to the over-low clock source precision. In addition, this topic describes the required tools,
Symptom
After the network operates for a certain period, AU pointer justification and TU pointer
justification occur on a large scale on the network.
Impact on System
Over-low precision of the external clock source causes pointer justification.
OptiX OSN 8800/6800/3800
121
Possible Causes
l Cause 1: The precision of the external clock source is over-low.
U2000
Procedure
Step 1 Cause 1: Over-low precision of the external clock source causes pointer justification.
1. Check the external clock source. It is found that the central site traces the clock source of
the switch or other clock sources with lower levels.
2. Change the clock tracing of the central site into internal free-run mode. Observe the clock
tracing for 24 hours and it is found that the fault of pointer justification is rectified.
3. Introduce the clock with a higher level to solve the problem thoroughly.
----End
Related Information
The SDH device has high requirements on the external clock source, the external clock source
must meet at least the requirements in the G.813 of SDH synchronization quality level. If the
precision of the external clock source is over-low or the clock quality deteriorates, pointer
justification occurs on the entire network.
OptiX OSN 8800/6800/3800
122
10 NE Offline Problems
About This Chapter
When the communication between an NE and the U2000 fails, this NE cannot be reached by the
U2000.
10.1 Unreachability of One NE by the U2000
This section describes the possible causes and handling methods when one NE is unreachable
by the U2000.
10.2 Unreachability of All NEs in a Subnet by the U2000
This section describes the possible causes and handling methods when all NEs in a subnet are
unreachable by the U2000.
10.3 Frequent Unreachability of an NE by the U2000
This section describes the possible causes and handling methods when an NE is frequently
10.4 The System Control Board Is Frequently Reset
This topic describes the possible causes and handling methods when the system control board
is frequently reset, which is caused by an ECC communication overload.
10.5 NE Offline Cases
This section lists cases related to NE Offline.
OptiX OSN 8800/6800/3800
Troubleshooting 10 NE Offline Problems
123
10.1 Unreachability of One NE by the U2000
This section describes the possible causes and handling methods when one NE is unreachable
by the U2000.
Symptom
One NE at a station is unreachable by the U2000, whereas the other NEs at this station are
reachable. The NE_COMMU_BREAK and NE_NOT_LOGIN alarms are reported on the
U2000.
The services on the NE are not interrupted.
Impact on System
The NE is unreachable by the U2000.
Possible Causes
l Cause 1: The network cable is disconnected or loose. For example, between the NE and
the HUB, between the GNE and the computer where the NMS server is installed, between
the GNE and non-GNEs, between the master and slave subrack of an NE.
l Cause 2: The NE Attributes of the NE is changed by mistake, such as the IP address, ID,
Gateway Type, User Name or Password
l Cause 3: The system control board on the NE is faulty.
l Cause 4: ECC communication is interrupted.
l Cause 5: The NE(non-first gateway NE) encounters system control board active/standby
switching.
l Cause 6: Coherent and non-coherent boards are interconnected.
U2000, Web LCT, cable tester
Procedure
l Cause 1: The network cable is disconnected or loose. For example, between the NE and
the HUB, between the GNE and the computer where the NMS server is installed, between
the GNE and non-GNEs, between the master and slave subrack of an NE.
1. Determine if the network cable connection between the NE and the HUB is loose. If
the network cable connection is loose, secure it.
2. Check whether network cables are correctly connected between the GNE and the
computer where the NMS server is installed, between the GNE and non-GNEs,
between the master and slave subrack of an NE.
3. Use a cable tester to test the network cable and the network port. If the network cable
is faulty, replace it.
OptiX OSN 8800/6800/3800
124
4. If the network cable is good, replace the interface, to which the network cable is
connected to the HUB. If the problem clears, the interface of the HUB may be
damaged.
5. If the network cable and the HUB is good, the interface board (such as EFI, EFI1,
EFI2, or AUX) is faulty, replace it.
l Cause 2: The NE Attributes of the NE is changed by mistake, such as the IP address, ID,
Gateway Type, User Name or Password.
1. Log in to the NE on the Web LCT and restore the initial IP address , ID, gateway type,
NE user or password of the NE according to the record.
l Cause 3: The system control board on the NE is faulty.
1. Log in to the NE on the Web LCT. If you fail to log in, the system control board is
faulty. Reset the board. If the problem persists, replacing the SCC board.
l Cause 4: ECC communication is interrupted.
1. A maximum of 16 users can simultaneously log in to an NE. If the number of users
reaches the upper limit, other users are not permitted to log in to the NE. For the method
of handling the interruption of ECC communication, see 17.1 ECC Communication
Interruption.
l Cause 5: The NE(non-first gateway NE) encounters system control board active/standby
switching.
1. No handling is required. Communication between the NE and U2000 will be restored
after the system control board active/standby switching.
1. The DCN bytes are defined differently for coherent and non-coherent services, so the
two types of services cannot be interconnected. If DCN channels are unavailable,
check whether the interconnected boards are coherent boards.
----End
10.2 Unreachability of All NEs in a Subnet by the U2000
This section describes the possible causes and handling methods when all NEs in a subnet are
Symptom
All NEs in a subnet are unreachable by the U2000. The NE_COMMU_BREAK,
NE_NOT_LOGIN, and GNE_CONNECT_FAIL alarms are reported on the U2000.
Impact on System
The NEs are unreachable by the U2000 in the subnet.
Possible Causes
l Cause 1: The gateway NE is faulty.
l Cause 2: The network cable between the gateway NE and the HUB is disconnected or the
interface to the HUB is damaged.
OptiX OSN 8800/6800/3800
125
l Cause 3: The IP address of the gateway NE is changed.
l Cause 4: The optical cable is faulty.
l Cause 5: The gateway NE encounters the system control board active/standby switching if
only one gateway NE is provided. The primary gateway NE encounters the system control
board active/standby switching if the primary and secondary gateway NEs are provided.
U2000, Web LCT, Cable tester
Procedure
l Cause 1: The gateway NE is faulty. No backup gateway NE is configured for the subnet.
1. Determine if the power supply of the gateway NE is faulty. If yes, clear the fault of
the power supply.
2. Log in to the gateway NE on the Web LCT. If you fail to log in, the system control
board is faulty. replacing the SCC board.
l Cause 2: The network cable between the gateway NE and the HUB is faulty.
1. Determine if the network cable connection between the gateway NE and the HUB is
loose. If the network cable connection is loose, secure it.
2. Use a cable tester to test whether the network cable is good. If the network cable is
faulty, replace it.
3. If the network cable is good, replace the interface to the HUB. If the problem clears,
the HUB is damaged.
l Cause 3: The IP address of the gateway NE is changed.
1. Log in to the NE on the Web LCT and restore the initial IP address of the gateway
NE according to the record.
l Cause 4: The optical cable is faulty.
1. When the optical cable is cut off in the main optical path, the NEs in the subnet become
unreachable by the U2000. At the same time, a large number of alarms and
performance events occur in the main optical path. Hence, the normal operation of
services is affected. In this case, the optical cable is faulty.
l Cause 5: The gateway NE encounters the system control board active/standby switching if
only one gateway NE is provided. The primary gateway NE encounters system the control
board active/standby switching if the primary and secondary gateway NEs are provided.
1. No handling is required. Communication between the gateway NE and U2000 will be
restored after the system control board active/standby switching.
----End
Solution
To prevent all NEs in a subnet from becoming unreachable by the U2000 when the gateway NE
fails, configure a backup gateway NE for the NEs in the subnet.
OptiX OSN 8800/6800/3800
126
10.3 Frequent Unreachability of an NE by the U2000
This section describes the possible causes and handling methods when an NE is frequently
Symptom
An NE frequently becomes unreachable by the U2000. The NE_COMMU_BREAK,
NE_NOT_LOGIN, and GNE_CONNECT_FAIL alarms are reported on the U2000.
Impact on System
The NE is unreachable by the U2000.
Possible Causes
l Cause 1: The IP address of the NE conflicts with that of another NE.
l Cause 2: The ECC communication is intermittent.
l Cause 3: The load of ECC communication is extremely heavy.
l Cause 4: Another NE user with the same account as that of the current NE user in the
network has logged in to the NE.
l Cause 5: When ESC and OSC coexist between station A and B, the system preferentially
selects the ESC for communication. Bit errors leads to the unstable link and the ESC
communication fails. The switching between ESC and OSC occurs frequently because the
route of ESC is shorter than the route of OSC.
l Cause 6: The scale of the DCN subnetwork is extremely large.
U2000
Procedure
l Cause 1: The IP address of the NE conflicts with that of another NE.
1. Determine if the IP addresses of the other devices (such as routers and servers) that
are newly configured in the network are the same as the IP address of the frequently
unreachable NE. Make sure that the IP address of the NE is unique.
l Cause 2: The ECC communication is intermittent.
1. For the method of handling the intermittent ECC communication, see 17.2
Intermittent ECC Communication.
l Cause 3: The load of ECC communication is extremely heavy.
1. For the method of handling the extremely heavy load of ECC communication, see
10.4 The System Control Board Is Frequently Reset.
l Cause 4: Another NE user with the same account as that of the current NE user in the
network has logged in to the NE. As a result, the NE becomes unreachable, and the
NE_NOT_LOGIN alarm is frequently reported on the U2000.
OptiX OSN 8800/6800/3800
127
1. Plan and manage the users that can log in to the NE. For the information on NE user
management, see "Creating an NE User".
l Cause 5: When ESC and OSC coexist between station A and B, the system preferentially
selects the ESC for communication. Bit errors leads to the unstable link and the ESC
communication fails. The switching between ESC and OSC occurs frequently. The NEs at
station B are frequently unreachable by the U2000.
1. Disable the ESC communication between station A and B on the U2000, keep the
OSC communication.
In NE Explorer, select the NE.
Select Communication > DCC Management from Function Tree.
In DCC Rate Configuration, select the board. Double click the parameter area of
Enabled/Disabled.
Choose Disabled in the drop list.
Click Apply.
2. Rectify the bit errors on the link, for details refer to 8 Bit Errors.
3. Enable the ESC communication between station A and B after the link becomes stable.
l Cause 6: The scale of the DCN subnetwork is extremely large.
1. Due to the inherent limitations of the DCC protocol, there is a limit on the number of
NEs (physical NEs with unique IDs) in a network even though there are sufficient
GNEs. If the number of NEs in a network exceeds the limit, the network must be
divided into multiple DCN subnets. The details refer to DCN Networking Capability.
NOTE
Each GNE can connect to a maximum of 50 non-GNEs, regardless of the protocol. If there are more
than 50 non-NEs for one GNE, another GNE must be added.
----End
10.4 The System Control Board Is Frequently Reset
This topic describes the possible causes and handling methods when the system control board
is frequently reset, which is caused by an ECC communication overload.
Symptom
Due to an ECC communication overload, the system control board is frequently reset and the
U2000 is frequently unable to reach the NE.
System Impact
The U2000 cannot reach the NE.
Possible Causes
l Cause 1: The ECC communication load is extremely heavy.
WEB LCT, cable tester
OptiX OSN 8800/6800/3800
128
Procedure
l Cause 1: The ECC communication load is extremely heavy. The scale of the ECC network
is extremely large and the inter-NE ECC communication load exceeds the maximum
processing capability of the NEs in the network. As a result, the system control board
frequently resets.
1. Check the scale of the ECC network. The number of NEs in the network cannot exceed
100. If there are more than 100 NEs in the network, divide the network into subnets.
Create a data communication network (DCN) management channel for each subnet
so the subnets are independent of each other.
2. Check the per-NE scale. When multiple pieces of equipment are connected by using
a HUB or are cascaded inter subracks, the extended ECC function of the network
interfaces of the equipment is used for communication. If not more than four pieces
of equipment are connected by using one HUB, the automatic extended ECC function
can be enabled. If more than four pieces of equipment are connected by using one
HUB, the manual extended ECC function is recommended for communication to
prevent ECC storms. For details on how to set the manual extended ECC function,
refer to "Configuring Extended ECC in Specified Mode".
----End
10.5 NE Offline Cases
This section lists cases related to NE Offline.
NOTE
Related Cases:
l MC-A20 The T2000 Cannot Log in to the Remote GNE Connected by the Router
l MC-A22 NE ESC Communication Interrupted Because of the Closure of the OTU Laser
l MC-A64 Many BD_STATUS Alarms Occur Due to the ECC Storm
l MC-A83 The OptiX OSN 6800 Is Not Reachable When the NE IP Is Modified
l MC-A110 Question About the Extended ECC of WDM NEs
l MC-A113 Communication Between the WDM Equipment And the DCN Network Fails
After a Hub Is Connected To the DCN Network
l MC-A135 The Communication Between the NE and the T2000 Stops Because the NE
Software Cannot Switch the ECC from an OSC Board to an OTU Board Automatically
l MC-A181 An NE Is Frequently Unreachable to the NMS Due to Insufficient Processing
Capacity of a Router
l MC-A212 Secondary GNE Becomes Unavailable After a Change of the Maximum Number
of Route Hops of an NE
l MC-A213 Internal Communication of an NE Is Abnormal And Many Boards Report
Transiently BD_STATUS or COMMUN_FAIL Alarms Due to Conflicted Subrack IDs
OptiX OSN 8800/6800/3800
129
11 Board Offline Problems
About This Chapter
This section describes how to troubleshoot offline boards.
11.1 A Board Is Offline
This section describes the possible causes and handling methods of a board that is offline on the
U2000.
11.2 Multiple Boards Are Offline
This section describes the possible causes and handling methods when multiple boards are offline
on the U2000.
OptiX OSN 8800/6800/3800
Troubleshooting 11 Board Offline Problems
130
11.1 A Board Is Offline
This section describes the possible causes and handling methods of a board that is offline on the
U2000.
Fault Description
The board is offline and unavailable on the U2000 while the other boards are online.
The board reports the BD_STATUS alarm.
Impact on the System
The boards cannot be managed or communicated with.
Possible Causes
l Cause 1: The slot that houses the board is faulty.
l Cause 2: The board is faulty.
U2000
Procedure
l Cause 1: The slot that houses the board is faulty.
1. Reseat the board to check whether the fault is removed.
2. If the fault persists, change the slot that houses the board.
l Cause 2: The board is faulty.
----End
11.2 Multiple Boards Are Offline
This section describes the possible causes and handling methods when multiple boards are offline
on the U2000.
Fault Description
Multiple or all boards are offline and unavailable on the U2000.
Multiple or all boards on the NE report the BD_STATUS alarms.
The boards cannot be managed or communicated with.
OptiX OSN 8800/6800/3800
131
Possible Causes
l Cause 1: The NE is unreachable.
l Cause 2: The network cable between the master and slave subracks is faulty.
l Cause 3: The backplane is faulty.
U2000
Procedure
l Cause 1: The NE is unreachable.
1. If the U2000 reports NE_COMMU_BREAK or NE_NOT_LOGIN alarm, the NE is
likely unreachable. For details, see 10.1 Unreachability of One NE by the U2000.
l Cause 2: The network cable between the master and slave subracks is faulty.
1. Check whether the network cable between the master and slave subracks is damaged
or loose and remove the fault accordingly.
l Cause 3: The backplane is faulty.
1. Replace the subrack.
----End
OptiX OSN 8800/6800/3800
132
12 Automatic Switching Failures
About This Chapter
This topic describes how to handle services that fail to be automatically switched to the protection
channel when the working channel works abnormally.
For information on the protection schemes supported by the OptiX OSN 8800, OptiX OSN 6800,
and OptiX OSN 3800, see the Feature Description"Feature Overview".
12.1 Optical Line Protection
This topic describes how to resolve switchover issues when optical line protection fails to
automatically switch services to the protection channel.
12.2 Intra-Board 1+1 Protection
This topic describes how to resolve switchover issues when intra-board 1+1 protection fails to
12.3 Client-side 1+1 Protection
This topic describes how to resolve switchover issues when client 1+1 protection fails to
12.4 SW SNCP Protection
This section describes the handling methods for services with SW SNCP protection that fail to
automatically switch to the protection channel when the working channel works abnormally.
12.5 ODUk SNCP Protection
This topic describes how to resolve switchover issues when ODUk SNCP protection fails to
12.6 VLAN SNCP Protection
This section describes the handling methods for services with VLAN SNCP protection that fail
to automatically switch to the protection channel when the working channel works abnormally.
12.7 Tributary SNCP Protection
This topic describes how to resolve switchover issues when tributary SNCP protection fails to
12.8 Automatic Switching Failure of DBPS Protection
This section describes the handling methods for services with DBPS protection that fail to
OptiX OSN 8800/6800/3800
Troubleshooting 12 Automatic Switching Failures
133
12.9 Board 1+1 Protection
This topic describes how to resolve switchover issues when board-level protection fails to
automatically switch services to the protection channel. Board-level protection refers to an
equipment-level protection scheme, which includes M:N protection for the cross-connect board
and 1+1 protection for the system control board.
12.10 Ethernet Ring Protection
This section describes the symptoms, impact, and possible causes of the protection switching
failure of Ethernet ring protection. In addition, this section describes the required tools,
12.11 MS SNCP Protection
This section describes the handling methods for services with MS SNCP protection that fail to
12.12 DLAG Protection
This section describes the handling methods for services with DLAG protection that fail to
12.13 Board-Level Protection
This section describes the handling methods for services with board-level protection that fail to
12.14 ODUk SPRing Protection
This section describes the handling methods for services with ODUk SPRing protection that fail
12.15 Optical Wavelength Shared Protection
This section describes the handling methods for services with optical wavelength shared
protection that fail to automatically switch to the protection channel when the working channel
works abnormally.
12.16 Inter-Subrack Communication Protection
This topic describes how to resolve switchover issues when inter-subrack communication
protection fails to automatically switch services to the standby route when communication
between master and slave subracks is interrupted.
12.17 Linear Multiplex Section Protection
This section describes the handling methods for services with linear multiplex section protection
that fail to automatically switch to the protection channel when the working channel works
abnormally.
12.18 MSP Ring
This section describes the handling methods for services with MSP ring protection that fail to
12.19 Transoceanic MSP Ring
This section describes the handling methods for services with transoceanic MSP ring protection
abnormally.
12.20 SNCP
This section describes the handling methods for services with SNCP protection that fail to
12.21 SNCTP
OptiX OSN 8800/6800/3800
134
This section describes the handling methods for services with tributary SNCTP protection that
fail to automatically switch to the protection channel when the working channel works
abnormally.
12.22 Protection Cases
This section lists cases related to Protection.
OptiX OSN 8800/6800/3800
135
Symptom
In normal operation of a network, the working channel has generated triggering conditions for
protection switching, but services cannot be automatically switched to the protection channel.
In this case, the services are interrupted.
l During normal network operations, conditions that trigger protection switching occur on
the working channel, but services do not automatically switch to the protection channel. In
this case, the services are interrupted.
l The optical line protection (OLP) board may report an OLP_PS or OLP_STA_INDI alarm.
Possible Causes
l Cause 1: The protection group parameters are incorrectly configured.
l Cause 2: Locked or forced switching commands have been manually issued.
l Cause 3: The optical fibers are improperly connected to the corresponding boards.
l Cause 4: The protection channel is working abnormally.
Troubleshooting Workflow
The following figure illustrates the optical line protection automatic switching failure
troubleshooting process.
OptiX OSN 8800/6800/3800
136
Figure 12-1 Optical line protection automatic switching failure troubleshooting flowchart
Yes
No No
Yes
No
Do the parameter
values comply with the
specificatsions?
Yes
Yes No
No
Yes
No
Start
Modify the
parameters.
Is a locked or
forced switching command
manually issued?
Are the fiber
connections on the
board correct?
Does the
protection channel work
normally?
Clear the locked or
forced switching
command.
Modify the fiber
connections.
Handle the faults on the
working and
protection channels.
the protection channel.
Resolve the faults on
the working
channel.
Contact Huawei
engineers.
End
Are the
services switched
to the protection
channel?
Yes
Are the
services switched
to the protection
channel?
Yes
No
Are the
services switched
to the protection
channel?
Yes
No
Are the
services switched
to the protection
channel?
Forcibly switch the
services to

U2000
Procedure
1. In the NE Explorer, click the NE and choose Configuration > Port Protection from
the Function Tree.
2. In the Port Protection window, click Query to query all protection group parameter
values. In the Operation Result dialog box, click Close.
OptiX OSN 8800/6800/3800
137
3. Compare these values against those specified in "Dependency and Limitation" and
"Parameters" to ensure that the parameters are configured correctly.
1. In the Port Protection window, click Query to check the Switching Status parameter
of the protection group.
2. If Switching Status is Locked or Force to Working Channel, click Function and
choose Clear to clear the locked or forced switching commands.
1. Check whether the optical fibers are properly connected to optical ports 1 (RI1/TO1)
and 2 (RI2/TO2) on the OLP boards located at the two stations next to the failure point.
For details, refer to "Principles".
1. In the Port Protection interface, click Query to check the Protection Channel
Status parameter of the protection group.
2. If Protection Channel Status is SF, check whether MUT_LOS and
POWER_DIFF_OVER alarms are being reported on the corresponding boards on the
protection channel, clear the alarms.
NOTE
If Protection Channel Status is SF, faults have occurred on both the working and protection
channels.
----End
Solution
If the preceding measures are not successful in switching the services to the protection channel,
and Protection Channel Status is displayed as Normal, you need to perform a forced switching
to switch the services to the protection channel, which eventually restores the services.
For more information regarding how to handle faults that occur in the working channel, clean
the Alarms and Performance Events in the NE. If necessary, contact Huawei engineers to resolve
the problem.
Symptom
l When the OLP board initiates intra-board 1+1 protection, the OLP board may report an
INTRA_OTU_PS or INTRA_OTU_STA_INDI alarm.
OptiX OSN 8800/6800/3800
138
l When the intra-board 1+1 protection is realized by dual fed and selective receiving OTU,
the OTU board may report the INTRA_OTU_PS alarm or INTRA_OTU_STA_INDI
alarm.
Possible Causes
l The protection group parameters are incorrectly configured.
l Locked or forced switching commands have been manually issued.
l The optical fibers are improperly connected to the corresponding boards.
l The protection channel is working abnormally.
Troubleshooting Flow
The following figure illustrates the intra-board 1+1 protection automatic switching failure
Figure 12-2 Intra-board 1+1 protection automatic switching failure troubleshooting flowchart
Yes
No No
Yes
No
Do the parameter
specificatsions?
Yes
Yes No
No
Yes
No
Start
Modify the
parameters.
Is a locked or
manually issued?
Are the fiber
connections on the
board correct?
Does the
normally?
Clear the locked or
forced switching
command.
Modify the fiber
connections.
working and
Resolve the faults on
the working
channel.
Contact Huawei
engineers.
End
Are the
services switched
to the protection
channel?
Yes
Are the
services switched
to the protection
channel?
Yes
No
Are the
services switched
to the protection
channel?
Yes
No
Are the
services switched
to the protection
channel?
Forcibly switch the
services to
OptiX OSN 8800/6800/3800
139

U2000
Procedure
the Function Tree.
1. For 2.5G OTU boards, check whether the optical fibers are properly connected to the
optical ports for working and protection channels on the OTU, or tributary or line
boards located at the two stations next to the failure point. For 5G, 10G, and 40G
OTU, or tributary or line boards, check whether the optical fibers are properly
connected to the optical ports for working and protection channels on the OLP or DCP
boards located at the two stations next to the failure point. For details, refer to
"Principles".
NOTE
OptiX OSN 3800/6800 supports 5G OTU.
1. In the Port Protection window, click Query to query the Protection Channel
2. If Protection Channel Status is SD or SF, check whether R_LOS, R_LOF, R_LOC,
OTUk_LOF, OTUk_LOM, OTUk_AIS, ODUk_PM_AIS, ODUk_PM_OCI,
ODUk_PM_LCK, ODUk_LOFLOM, B1_EXC, ODUk_PM_DEG,
ODUk_PM_EXC, POWER_DIFF_OVER, IN_PWR_HIGH and IN_PWR_LOW
alarms are being reported on the corresponding boards on the protection channel.
NOTE
If Protection Channel Status is SD, SF, faults have occurred on both the working and protection
channels.
----End
OptiX OSN 8800/6800/3800
140
Solution
the problem.
Symptom
l The DCP or OLP board may report a CLIENT_PORT_PS or CLIENT_PORT_STA_INDI
alarm.
l When you use the SCS board to configure the protection, the OTU or tributary board may
report the CLIENT_PORT_PS alarm or CLIENT_PORT_STA_INDI alarm.
Possible Causes
l The protection group parameters are incorrectly configured.
l The optical fibers are improperly connected to the corresponding boards.
l The protection channel is working abnormally.
The following figure illustrates the client 1+1 protection automatic switching failure
OptiX OSN 8800/6800/3800
141
Figure 12-3 Client 1+1 protection automatic switching failure troubleshooting flowchart
No Yes
Yes
No
Yes
Yes
Yes
No
Modify the
parameters.
Do the
parameter values comply
with the specifications?
Start
Are the
services switched to
the protection
channel?
Handle the faults on
the working and
Is Protection
Channel Status
Normal?
Forcibly switch the
services to the
protection channel.
the working channel.
Contact Huawei
engineers.
End
Yes
No
Are the
the protection
channel?
No
Are the
the protection
channel?
Is a locked or
manually issued?
Clear the locked or
forced switching
command.
Are the fiber
connections on the
board correct?
No
Modify the fiber
connections.
Yes
Are the
services switched
to the protection
channel?
No No
Yes

U2000
Procedure
the Function Tree.
OptiX OSN 8800/6800/3800
142
"Parameters" to ensure that the parameters are configured properly.
1. Ensure that the optical fibers are properly connected to the optical ports for the working
and protection channels.
1. In the Port Protection window, click Query to query the Protection Channel
2. If Protection Channel Status is SD or SF, check whether the alarms listed in the
trigger conditions are being reported on the corresponding boards on the protection
channel, clear the alarms.
NOTE
If Protection Channel Status is SD or SF, faults have occurred on both the working and protection
channels.
----End
Solution
the problem.
This section describes the handling methods for services with SW SNCP protection that fail to
Fault Description
The OTU board may report SW_SNCP_STA_INDI alarm.
Possible Causes
The possible causes of the automatic switching failure are as follows:
OptiX OSN 8800/6800/3800
143
l The parameters of the protection group are improperly configured.
l Locked or forced switching is not released.
l The electrical cross-connections are configured incorrectly.
l The protection channel works abnormally.
Fault Handling Flow
Figure 12-4 Fault handling flow when automatic switching by SW SNCP protection fails
No Yes
Yes
No
No
Yes Yes
No
Yes
No
No
Yes
Modify the
parameters.
Do the parameter
specifications?
Start
Are the
the protection
channel?
Are the
configurations of electrical
cross-connections
correct?
Dose the protection
channel work
abnormally?
End
Modify the
configurations of
electrical cross-
connections.
working channel.
Contact Huawei
engineers.
Are the
the protection
channel?
Yes
No
Are the
the protection
channel?
Yes
No
Are the
the protection
channel?
Is a locked or
manually issued?
Clear the locked or
forced switching
command.

U2000
Procedure
l Cause 1: The parameters of the protection group are improperly configured.
OptiX OSN 8800/6800/3800
144
1. Select the NE in the NE Explorer, and choose Configuration > WDM Service
Management from the Function Tree. Click the SNCP Service Control tab.
2. Click Query in the SNCP Service Control interface, to query the values of all
parameters of the protection group. Click Close in the Operation Result dialog box.
3. Compare the values against the principles and requirements specified in Dependency
and Limitation and Parameters in the Feature Description to ensure that the parameters
are configured properly.
l Cause 2: Locked or forced switching is not released.
1. In the SNCP Service Control interface, click Query to check the Status parameter
2. If Status is displayed as Lockout or Forced (from protection to working) switching
state, select the protection group and right-click it. Choose Clear from the shortcut
menu to clear the locked or forced switching configuration.
l Cause 3: The electrical cross-connections are configured incorrectly.
Management from the Function Tree.
2. Click Query on the bottom of the WDM Cross-Connection Configuration interface
to check the created cross-connections.
3. According to the network design, ensure the source and sink ports of the dual fed
cross-connections that are configured on the source end are correct.
l Cause 4: The protection channel works abnormally.
1. In the SNCP Service Control interface, click Query to query the Channel Status
parameter of the protection cross-connection.
2. If Channel Status is displayed as SD, SF, check whether the following alarms of
trigger conditions exist on the relevant boards on the protection channel. For the
method of handling the alarms, see the Alarms and Performance Events Reference.
NOTE
If the Channel Status parameter of the protection cross-connection is displayed as SD, SF, it
is indicated that faults have occurred in both the working and protection channels.
----End
Solution
the problem.
OptiX OSN 8800/6800/3800
145
Symptom
Tributary, line or PID board may report an ODU_SNCP_STA_INDI alarm.
Possible Causes
l Cause 1: The SNCP Type is inappropriate for the service scenario.
l Cause 4: The electrical cross-connections are incorrectly configured.
The following figure illustrates the ODUk SNCP protection automatic switching failure
OptiX OSN 8800/6800/3800
146
Figure 12-5 ODUk SNCP protection automatic switching failure troubleshooting flowchart
No Yes
Yes
No
No
Yes
Yes
No
Yes
No
No Yes
Yes
No
No
Yes
Change the SNCP Type
Is the SNCP Type
consistent with that
required in the service
scenario?
Start
Are the
services switched
to the protection
channel?
Do the parameter values
comply with the
specifications?
Is
a locked or forced
switching command
manually issued?
Are
the configurations
of electrical cross-
connections correct?
Does
the protection
channel work
abnormally?
End
Modify the parameters.
Clear the locked or
forced switching
command.
Modify the
configurations of
electrical cross-
connections.
the working and
working channel.
Contact Huawei
engineers.
Are the
services switched
to the protection
channel?
Are the
services switched
to the protection
channel?
Yes
No
Are the
services switched
to the protection
channel?
Yes
No
Are the
services switched
to the protection
channel?

U2000
Procedure
1. In the NE Explorer, click the NE and choose Configuration > WDM Service
Management from the Function Tree. Then click the SNCP Service Control tab.
2. In the SNCP Service Control window, click Query to query the Protection Type of
the protection group. In the Operation Result dialog box, click Close.
OptiX OSN 8800/6800/3800
147
3. Refer to "Dependency and Limitation" and "Parameters" to check whether the
Protection Type of the protection group is appropriate for the service scenario.
1. In the SNCP Service Control window, click Query to query all protection group
parameter values.
l Cause 3: Locked switching or forced switching commands have been manually issued.
1. In the SNCP Service Control window, click Query to query the Channel Status
2. If Channel Status is SD or SF, check whether the alarms listed in Trigger Conditions
are being reported on the corresponding boards on the protection channel, clear the
alarms.
NOTE
If the Channel Status parameter of the protection cross-connection is SD or SF, faults have occurred
on both the working and protection channels.
1. Forcibly switch services to the protection channel, which will eventually restores
services.
2. Replace the faulty line board.
----End
Solution
Before the working channel is restored from a failure (for example, the faulty board has not yet
been replaced), services on the protection channel may run without protection for a long time.
To avoid a second failure on the network, you are advised to convert an idle and unprotected
service to the SNCP service for protection. For details, refer to "Converting a Normal WDM
Service to an SNCP Service." After the working channel is restored, convert the SNCP service
OptiX OSN 8800/6800/3800
148
back to an unprotected service. For details, refer to "Converting an SNCP Service to a Normal
WDM Service."
the problem.
This section describes the handling methods for services with VLAN SNCP protection that fail
Fault Description
L4G, TBE, LEM24, LEX4 board of OptiX OSN 6800/OptiX OSN 3800 may report
VLAN_SNCP_PS.
LEM24, LEX4 board of OptiX OSN 8800 may report VLAN_SNCP_PS.
Possible Causes
l Locked or forced switching is not released.
OptiX OSN 8800/6800/3800
149
Fault Handling Flow
Figure 12-6 Fault handling flow when automatic switching by VLAN SNCP protection fails
No Yes
Yes
No
No
Yes Yes
No
Yes
No
Yes
No
Modify the
parameters.
Does the parameter
specifications?
Start
Are the
the protection
channel?
Are the
configurations of electrical
cross-connections
correct?
Is Protection
Channel Status
Normal?
End
Modify the
configurations of
electrical cross-
connections.
the working and
Forcibly switch the
services to the
protection channel.
working channel.
Contact Huawei
engineers.
Are the
the protection
channel?
Yes
No
Are the
the protection
channel?
Yes
No
Are the
the protection
channel?
Is a locked or
manually issued?
Clear the locked or
forced switching
command.

U2000
Procedure
1. Select the desired Ethernet board in the NE Explorer, and choose Configuration >
Ethernet Service > Ethernet Line Service from the Function Tree.
OptiX OSN 8800/6800/3800
150
2. Click Query in the VLAN SNCP Service Management tab to query the values of
all parameters of the protection group.
and Limitation and Parameters in the Feature Description to ensure that the parameters
are configured properly.
l Cause 2: Locked or forced switching is not released.
1. In the VLAN SNCP Service Management interface, click Set/Query Switching and
select Query Switching Status to query the Channel Status parameter of the
protection group.
2. If Channel Status for the protection channel is displayed as Lockout State or Forced
(Standby to Active) Switching State, right-click the protection group, and then
choose Clear from the shortcut menu, to clear the locked or forced switching
configuration.
select Query Switching Status to check the Link Status parameter of the protection
service.
2. If Link Status is displayed as SF, check whether the following alarms exist on the
relevant boards on the protection channel: R_LOS, R_LOF, R_OOF, OTU5G_LOF,
OTU5G_AIS, OTU5G_LOM. For the method of handling the alarms, see the Alarms
and Performance Events Reference.
NOTE
If the Link Status parameter of the protection service is displayed as SF, it is indicated that
faults have occurred in both the working and protection channels.
----End
Solution
the problem.
OptiX OSN 8800/6800/3800
151
Symptom
Tributary, line or PID board may report an ODU_SNCP_PS alarm or ODU_SNCP_STA_INDI
alarm.
Possible Causes
l Cause 4: The electrical cross-connections are incorrectly configured.
The following figure illustrates the tributary SNCP protection automatic switching failure
OptiX OSN 8800/6800/3800
152
Figure 12-7 Tributary SNCP protection automatic switching failure troubleshooting flowchart
No Yes
Yes
No
No
Yes
Yes
No
Yes
Yes
No
No
No Yes
Yes
No
Yes
No
Change the
SNCP Type

Is the SNCP Type
consistent with that
required in the service
scenario?
Start
Are the
services switched
to the protection
channel?
Do
the parameter
specifications?
Are
the configurations
of electrical cross-
connections correct?
End

Modify the
configurations of
electrical cross-
connections.
the working and
working channel.
Contact Huawei
engineers.
Are the
services switched
to the protection
channel?
Are the
services switched
to the protection
channel?
Are the
services switched
to the protection
channel?
Is a locked or
manually issued?
Clear the locked or
forced switching
command.
Yes
No
Are the
services switched
to the protection
channel?
normally?
Does the

U2000
Procedure
the protection group.
OptiX OSN 8800/6800/3800
153
1. In the SNCP Service Control window, click Query to query all protection group
parameter values.
l Cause 3: Locked switching or forced switching commands have been manually issued.
are being reported on the corresponding boards on the protection channel, clear the
alarms.
NOTE
If the Channel Status parameter of the protection cross-connection is SD or SF, faults have occurred
on both the working and protection channels.
----End
Solution
the problem.
NOTE
If the section overhead status changes, protection switching may be triggered.
OptiX OSN 8800/6800/3800
154
12.8 Automatic Switching Failure of DBPS Protection
This section describes the handling methods for services with DBPS protection that fail to
Fault Description
TBE board may report DBPS_ABNORMAL alarm.
Possible Causes
l There is alarm to be solved.
Fault Handling Flow
Fault handling flow in the case that services cannot be switched back to the protection channel
in the DBPS protection, see Figure 12-8.
Figure 12-8 Fault handling flow when automatic switching by DBPS protection fails
Yes
No
No
Does the parameter
value comply with the
specifications?
Yes
Yes No
No
Start
Modify the
parameters.
Are the alarms
cleared?
Clear the alarms.
Contact Huawei
engineers.
End
Are the
services switched
to the protection
channel?
Yes
Are the
services switched
to the protection
channel?

OptiX OSN 8800/6800/3800
155
U2000
Procedure
1. In the NE Explorer, select the NE and then choose Configuration > Distributed
Board-Level Protection from the Function Tree.
2. In the right pane, click Query to obtain the current information about the created
DBPS.
3. Compare the values against the principles and requirements specified in Dependencies
and Limitations and Parameters in the Feature Description to check and ensure that
the parameters are configured properly.
l Cause 2: There is alarm to be solved.
1. Check if there is the DBPS_ABNORMAL, LINK_ERR, R_LOS, R_LOF,
HARD_BAD, PORT_MODULE_OFFLINE alarms.
2. Solve the alarms. For details, refer to the Alarms and Performance Events
Reference.
----End
Solution
the problem.
12.9 Board 1+1 Protection
This topic describes how to resolve switchover issues when board-level protection fails to
automatically switch services to the protection channel. Board-level protection refers to an
equipment-level protection scheme, which includes M:N protection for the cross-connect board
and 1+1 protection for the system control board.
Background Information
The OptiX OSN 3800 supports 1+1 protection for only SCC boards.
The OptiX OSN 6800 supports 1+1 protection for only cross-connect boards and SCC boards.
Symptom
During normal network operations, conditions that trigger protection switching occur on the
equipment, but services do not automatically switch to the standby board.
OptiX OSN 8800/6800/3800
156
l If 1+1 protection for the system control board fails to be automatically switched, the
U2000 cannot reach the equipment. The services on the equipment, however, are
unaffected.
l If the protection switching of the cross-connect boards or clock boards fails, the services
on the equipment are interrupted.
Possible Causes
l Cause 1: No standby board is configured.
l Cause 2: The standby board is faulty.
U2000
Procedure
l Cause 1: No standby board is configured.
1. Configure a standby board.
l Cause 2: The standby board is faulty.
1. Replace the faulty standby board.
----End
Solution
After configuring a standby board or replacing the faulty standby board, replace the faulty active
board to restore services.
NOTE
To replace a board with active/standby protection, use a board of the same type.
This section describes the symptoms, impact, and possible causes of the protection switching
failure of Ethernet ring protection. In addition, this section describes the required tools,
Fault Description
When the network operates normally, the working channel has generated the conditions of
triggering the protection switching, but the services cannot be automatically switched to the
protection channel. In this case, the services are interrupted.
If there is more than one RPL owner node on the ring, the system reports the
MULTI_RPL_OWNER alarm.
An ERPS failure interrupts services.
OptiX OSN 8800/6800/3800
157
Possible Causes
l Cause 1: The configuration of the protection group parameters is incorrect.
l Cause 3: The fiber connections on the board are incorrect.
l Cause 4: The hardware is faulty.
U2000
Procedure
l Cause 1: The configuration of the protection group parameters is incorrect. As a result, the
protection switching fails.
1. Review the configuration of the protection group parameters on the U2000.
If... Then...
The configuration of the protection
group parameters is incorrect
Re-configure the protection group
parameters. Determine if the services
are restored. If the services are not
restored, determine if the fault is due to
other causes.
The configuration of the protection
group parameters is correct
Determine if the fault is due to other
causes.

1. Determine if the following alarms exist on the relevant boards: AU_LOP, MS_AIS,
AU_AIS, B3_EXC, R_LOS, and LINK_ERR. For the method of handling the alarms,
see the Alarms and Performance Events Reference.
l Cause 3: The fiber connections on the board are incorrect. As a result, the protection
switching fails.
1. See the protection principles to determine if the fiber connections at the faulty point
are correct.
If... Then...
The fiber connections are incorrect Reconnect the fibers. Determine if the
recover, determine if the fault is due to
other causes.
The fiber connections are correct Determine if the fault is due to other
causes.

l Cause 4: The hardware is faulty. As a result, the protection switching fails.
1. See the Parts Replacement to replace the faulty board.
OptiX OSN 8800/6800/3800
158
2. Determine if the services are restored. If the services are not restored, determine if the
----End
Solution
If the preceding measures are not successful in switching the services to the working channel,
contact Huawei engineers to resolve the problem.
This section describes the handling methods for services with MS SNCP protection that fail to
Fault Description
The OTU board may report MS_SNCP_PS alarm or MS_SNCP_STA_INDI alarm.
Possible Causes
l The related boards work abnormally.
l Locked switching or forced switching is not released.
OptiX OSN 8800/6800/3800
159
Fault Handling Flow
Figure 12-9 Fault handling flow when automatic switching by MS SNCP protection fails
No Yes
Yes
No
No
Yes Yes
No
Yes
Yes No
No
Yes
No
Modify the
parameters.
Do the parameter
values comply with
the specifications?
Start
Are services
switched to the
protection channel?
Are the configurations of
electrical cross-connections
correct?
Does the protection
channel work
normally?
End
Modify the
configurations of
electrical cross-
connections.
protection channel.
Contact Huawei
engineers.
Are services
switched to the
protection
channel?
Are services
switched to the
protection channel?
No Yes
Yes
No
Replace the
board.
Does the
corresponding
board work
normally?
Are services
switched to the
protection channel?
Is a locked or forced
switching command
manually issued?
Clear the locked or
forced switching
command.
Yes
No
Are services
switched to the
protection channel?

U2000
Procedure
l Cause 1: The related boards work abnormally.
1. Allocate the board which works abnormally.
2. Replace the board. For details refer to Parts Replacement.
OptiX OSN 8800/6800/3800
160
Management from the Function Tree. Click SNCP Service Control tab.
2. Click Query in the SNCP Service Control interface, to query the values of all
parameters of the protection group.
and Limitation and Parameters in the OptiX OSN 6800/3800 Feature Description to
check and ensure that the parameters are configured properly.
l Cause 3: Locked switching or forced switching is not released.
1. In the SNCP Service Control interface, click Query to query the Status parameter
state, right-click the protection group, and then choose Clear from the shortcut menu,
to clear the locked or forced switching configuration.
to query the created cross-connections.
3. According to the network design, check if source and sink ports of the dual fed cross-
connections that are configured on the source end are correct.
2. If Channel Status is displayed as SD, SF, check whether the following alarms exist
on the relevant boards on the protection channel: R_LOF, R_LOS, R_LOC,
ODUk_PM_LCK, ODUk_LOFLOM, REM_SF, B1_EXC, ODUk_PM_EXC,
OTUk_EXC, REM_SD. For the method of handling the alarms, see the Alarms and
Performance Events Reference.
NOTE
If the Channel Status parameter of the protection cross-connection is displayed as SD, SF, it
is indicated that faults have occurred in both the working and protection channels.
----End
Solution
the problem.
OptiX OSN 8800/6800/3800
161
This section describes the handling methods for services with DLAG protection that fail to
Fault Description
The board may report DLAG_PROTECT_FAIL alarm.
Possible Causes
l There is alarm which needs to be cleared.
Fault Handling Flow
Figure 12-10 Fault handling flow when automatic switching by DLAG protection fails
Yes No
No
Do the parameter
specifications?
Yes
Yes No
No
Start
Modify the
parameters.
Are the alarms cleared? Clear the alarms.
Contact Huawei
engineers.
End
Are the
services switched
to the protection
channel?
Yes
Are the
services switched
to the protection
channel?

U2000
OptiX OSN 8800/6800/3800
162
Procedure
1. In the NE Explorer, select the NE and then choose Configuration > Ethernet
Distributed Link Aggregation Management from the Function Tree.
2. In the right pane, click Query to obtain the current information about the created
DLAG.
3. For DLAG Protection(EOO/EOW), compare the values against the principles and
requirements specified in Parameters in the OptiX OSN 8800 Feature Description to
ensure that the parameters are configured properly.
4. For DLAG Protection(EOS), compare the values against the principles and
requirements specified in Dependency and Limitation and Parameters in the OptiX
OSN 8800 Feature Description to check and ensure that the parameters are configured
properly.
5. For DLAG Protection(EOS), compare the values against the principles and
requirements specified in Dependency and Limitation and Parameters in the OptiX
OSN 6800/3800 Feature Description to ensure that the parameters are configured
properly.
l Cause 2: There is alarm which needs to be cleared.
1. On the U2000, determine if there is DLAG_PROTECT_FAIL or other alarms on the
protection channel.
2. Clear the alarms. For more information, refer to the Alarms and Performance Events
Reference.
----End
Solution
the problem.
12.13 Board-Level Protection
This section describes the handling methods for services with board-level protection that fail to
Fault Description
Possible Causes
OptiX OSN 8800/6800/3800
163
l Forced switching is not released.
l The protection board works abnormally.
Fault Handling Flow
Figure 12-11 Fault handling flow when automatic switching by board-level protection fails
No Yes
Yes
No
Yes
No
Yes
No
Modify parameters
Does the parameter
value comply with the
specification?
Start
Are the
the protection
board?
Is a forced
switching command
issued?
Is Protection Board
Status displayed as
Available?
Clear the
forced switching
command
Clear the faults in the
working and protection
boards
Perform forced
switching
Clear the faults in the
working board
Contact Huawei
engineers
End
Yes
No
Are the
the protection
board?
Yes
No
Are the
the protection
board?

U2000
Procedure
1. Select the NE in the NE Explorer, and choose Configuration > Board-Level
Protection from the Function Tree.
OptiX OSN 8800/6800/3800
164
2. Click Query in the interface, to query the values of all parameters of the protection
group.
and Limitation and Parameters in the OptiX OSN 6800/3800 Feature Description to
ensure that the parameters are configured properly.
l Cause 2: Forced switching is not released.
1. In the window, click Query to check the Switching Status parameter of the protection
group.
2. If Switching Status is displayed as Forced Switch Request, right-click the protection
group, and then choose Clear from the shortcut menu to clear the locked switching
or forced switching configuration.
l Cause 3: The protection board works abnormally.
1. In the window, click Query to check the Protection Board Availability parameter
2. If Protection Board Availability is displayed as Unusable, determine if the following
alarms exist on the relevant boards on the channels: HARD_BAD, BD_STATUS,
PORT_MODULE_OFFLINE, R_LOS, R_LOF. For more information, refer to the
Alarms and Performance Events Reference.
----End
Solution
If the problem persists after the above steps are performed and Protection Board
Availability is Available, choose Forced Switching to Protection to perform a forced
switching on the protection group. Then, the services are switched to the protection board and
the services recover.
For more information regarding how to handle faults that have occurred on the working board,
refer to the Alarms and Performance Events Reference. If necessary, contact Huawei engineers
to resolve the problems.
This section describes the handling methods for services with ODUk SPRing protection that fail
Fault Description
The NEs at both ends of the channel where the switching occurs may report the ODUKSP_PS
alarm or ODUKSP_STA_INDI alarm.
Possible Causes
OptiX OSN 8800/6800/3800
165
l The SD Switching is set to Disabled.
l The protection protocol is not started.
l The fibers are improperly connected to the corresponding boards.
Fault Handling Flow
Figure 12-12 Fault handling flow when automatic switching by ODUk SPRing protection fails
No Yes
Yes
No
No Yes
Yes No
Yes Yes
No
Yes
No
Yes Yes
No No
Yes
No
Start
Are the
the protection
channel?
working and
Perform manual
switching or forced
switching.
working channel.
Contact Huawei
engineers.
Are the
the protection
channel?
Are the
the protection
channel?
Are the
the protection
channel?
End
No
Yes
No
Are the
the protection
channel?
No
Yes
No
Are the
the protection
channel?
Is a locked or
manually issued?
Clear the locked
or forced switching
command.
Does
the protection channel
work normally?
Are the fiber
connections on the board
correct?
Modify the fiber
connections.
Is the protection
protocol started?
Start the protection
protocol.
values comply with
the specifications?
Do
the parameter
Modify the
parameters.
Is SD Switching set
to Disabled?
Modify the parameter.
OptiX OSN 8800/6800/3800
166

U2000
Procedure
1. In the Channel Mapping Relation interface, click Query to query the Channel
Status parameter of the protection channel.
on the relevant boards on the protection channel: R_LOS, R_LOC, HARD_BAD,
OTUk_LOF, OTUk_LOM, OTUk_AIS, ODUk_LOFLOM, ODUk_TCMn_OCI,
ODUk_TCMn_LCK, ODUk_TCMn_AIS, OTUk_EXC, ODUk_TCM6_DEG,
ODUk_TCM6_EXC. For the method of handling the alarms, see the Alarms and
1. In the ODUk SPRing interface, click Query to query the Switching Request-East
or Switching Request-West parameter of the protection group.
2. If Switching Request-West or Switching Request-East is displayed as Locked or
Forced Switching - Ring, right-click the protection group, and then choose Clear
from the shortcut menu, to clear the locked or forced switching configuration.
1. Select the NE in the NE Explorer, and choose Configuration > ODUk SPRing from
the Function Tree.
2. Click Query in the interface, to query the values of all parameters of the protection
group.
3. Check whether Span ID has been set correctly.
For example, if services are added/dropped at sites A and B and site B is east to site
A, then the span ID for the west working unit of site B must be the same as the span
ID for the east working unit of site A.
the other parameters are configured properly.
l Cause 4: SD Switching has been set to Disabled.
1. Click Query to query the SD Switching parameter of the protection group.
If SD Switching has been set to Disabled, services cannot be switched to the
protection channel when an OTUk_EXC, ODUk_TCM6_DEG, or
ODUk_TCM6_EXC alarm is generated on the working channel.
2. Set SD Switching to Enabled.
l Cause 5: The protection protocol is not started.
1. Click Query to query the Switching Request-East or Switching Request-West
parameter of the protection group.
OptiX OSN 8800/6800/3800
167
If the protection protocol has not started, Switching Request-East or Switching
Request-West is displayed as Unknown.
2. Select the protection group and click Start Protocol.
l Cause 6: The fibers are improperly connected to the corresponding boards.
1. Refer to the protection principle in Principles. Check if the fiber connections are
correct on the optical interfaces of the east and west working channels and protection
channels of the line boards at the stations on the two ends.
----End
Solution
protection that fail to automatically switch to the protection channel when the working channel
works abnormally.
Fault Description
DCP board may report OWSP_PS alarm or OWSP_STA_INDI alarm.
Possible Causes
l The protection protocol is not started.
l The fibers are improperly connected to the corresponding boards.
OptiX OSN 8800/6800/3800
168
Fault Handling Flow
Figure 12-13 Fault handling flow when automatic switching by OWSP protection fails
No
Yes
Yes
No
Yes
No
Yes
No
No Yes
Yes
No
No Yes
Yes No
Modify the
parameters.
Do
the parameter
specifications?
Start
Are the
the protection
channel?
Is the protection protocol
started?
Are
the fiber connections
on the board correct?
Are the
the protection
channel?
Are the
the protection
channel?
End
Start the protection
protocol.
Modify the fiber
connections.
working and
Perform a manual
or forced switching.
working channel.
Contact Huawei
engineers.
Yes
No
Are the
the protection
channel?
Yes
No
Are the
the protection
channel?
Is a locked or
manually issued?
Clear the locked or
forced switching
command.
Does
the protection channel
work normally?

U2000
OptiX OSN 8800/6800/3800
169
Procedure
1. Select the NE in the NE Explorer, and choose Configuration > Optical Wavelength
Shared Protection from the Function Tree. Click OWSP Protection tab.
2. Click Query in the OWSP Protection interface, to query the values of all parameters
the parameters are configured properly.
l Cause 2: The protection protocol is not started.
1. In the OWSP Protection interface, select the protection group and click Start
Protocol.
1. In the OWSP Protection interface, click Query to query the Switching Request-
East or Switching Request-West parameter of the protection group.
2. If Switching Request-East or Switching Request-West is displayed as Locked or
Forced Switching - Ring, right-click the protection group, and then choose Clear
from the shortcut menu, to clear the locked or forced switching configuration.
l Cause 4: The fibers are improperly connected to the corresponding boards.
1. Refer to the protection principle in Principles. Check if the fiber connections are
correct on the optical interfaces of the east and west working channels and protection
channels of the DCP boards at the stations on the two ends.
1. In the OWSP Protection interface, click Query to query the Channel Status
parameter of the protection channel.
on the relevant boards on the protection channel: MUT_LOS, R_LOS, R_LOC,
R_LOF, OTUk_LOF, OTUk_LOM, OTUk_AIS, ODUk_PM_AIS,
ODUk_PM_OCI, ODUk_PM_LCK, OTUk_TIM, ODUk_PM_TIM,
ODUk_LOFLOM, IN_PWR_HIGH, IN_PWR_LOW, B1_EXC, ODUk_PM_DEG,
ODUk_PM_EXC, OTUk_DEG, OTUk_EXC. For the method of handling the alarms,
see the Alarms and Performance Events Reference.
NOTE
If the Channel Status parameter of the protection channel is displayed as SD, SF, it is indicated
that faults have occurred in both the working and protection channels.
----End
Solution
the problem.
OptiX OSN 8800/6800/3800
170
12.16 Inter-Subrack Communication Protection
This topic describes how to resolve switchover issues when inter-subrack communication
protection fails to automatically switch services to the standby route when communication
between master and slave subracks is interrupted.
The OptiX OSN 8800 and 6800 support protection for inter-subrack communication.
Symptom
During normal network operations, the communication between master and slave subracks is
interrupted, and services do not automatically switch to the standby route.
System Impact
When inter-subrack communication protection fails to automatically switch, the U2000 cannot
reach the slave subracks. The services on the equipment, however, are unaffected.
Possible Causes
l Cause 1: The protection network cable is loosely connected or is malfunctioning.
U2000
Procedure
l Cause 1: The protection network cable is loosely connected or is malfunctioning.
1. Securely attach the protection network cable.
2. Replace the protection network cable.
----End
abnormally.
Fault Description
SCC board may report APS_FAIL alarm.
OptiX OSN 8800/6800/3800
171
Possible Causes
l Cause 1: The protocol fails to start and the protection switching fails.
l Cause 2: The protection switching protocol is abnormal. The protocol status is not idle.
l Cause 3: The protocol is stopped manually or a forced switching is performed manually.
As a result, the protection switching fails.
l Cause 4: The power supply of the device is faulty.
U2000
Procedure
Step 1 Cause 1: The protocol fails to start and the protection switching fails.
1. In the NE Explorer, click the desired NE and choose Configuration > Linear MS from
the Function Tree.
2. In Linear MS interface, click Stop Protocol. Click Close in the Operation Result dialog
box.
3. Click Start Protocol to re-enable the protocol. Click Close in the Operation Result dialog
box.
4. Check whether the hardware is faulty. If the hardware is faulty, go to cause 5.
Step 2 Cause 2: The protection switching protocol is abnormal. The protocol status is not idle.
1. Check the settings of linear MS parameters on the U2000.
If... Then...
The settings of the linear MS parameters
are incorrect
Set the parameters of the multiplex section
to proper values. Check whether services
causes.
The configuration of the linear MS
parameters is correct

2. The optional switching conditions are not configured.
If... Then...
The optional switching conditions are not
configured.
Configure B2_SD as an optional switching
conditions. For the details, see the Feature
Description.
The working channel is configured with
optional switching conditions.

OptiX OSN 8800/6800/3800
172
3. The protection channel works abnormally.
If... Then...
Check whether the following alarms exist
on the relevant boards:
R_LOS, R_L0F, R_LOC, MS_AIS,
B2_EXC, B2_SD
For the method of handling the alarms, see
the Alarms and Performance Events
Reference.
No alarms, proceed to the next substep.

4. Re-enable the protocol, check whether services recover. If the services do not recover,
Step 3 Cause 3: The protocol is stopped manually or a forced switching is performed manually. As a
result, the protection switching fails.
1. Check the protocol controller state on the U2000.
If... Then...
The state of the protocol controller is
Protocol Stopped
Restart the protocol controller. Check
whether services recover. If the services do
not recover, check whether the fault is due
to other causes.
Protocol Started

2. Check the protection group switching state on the U2000.
If... Then...
The switching state of the protection group
is Lockout or Switching
Clear protection switching. Check whether
recover, check whether the fault is due to
other causes.
is Normal
causes.

Step 4 Cause 4: The power supply of the device is faulty. As a result, the protection switching fails.
1. Refer to 5.5 Service Interruptions Caused by Power Supply Failures to rectify the fault.
Step 5 Cause 5: The hardware is faulty. As a result, the protection switching fails.
----End
Related Information
None
OptiX OSN 8800/6800/3800
173
12.18 MSP Ring
This section describes the handling methods for services with MSP ring protection that fail to
Fault Description
When the network operates normally, the working channel generates the triggering conditions
for protection switching, but the services cannot be automatically switched to the protection
channel. In this case, the services are interrupted.
SCC board may report APS_FAIL alarm.
Possible Causes
l Cause 3: The protocol is stopped manually or the forced switching is performed manually.
U2000
Procedure
1. In the NE Explorer, click the desired NE and choose Configuration > Ring MS from the
Function Tree.
2. In Ring MS interface, click Stop Protocol. Click Close in the Operation Result dialog
box.
box.
1. Check the settings of the ring MS parameters on the U2000.
OptiX OSN 8800/6800/3800
174
If... Then...
The settings of the ring MS parameters are
incorrect
Set the parameters of the ring MS to proper
values. Check whether services recover. If
the services do not recover, check whether
The configuration of the ring MS

If... Then...
configured.
Description.

If... Then...
B2_EXC, B2_SD
Reference.

Step 3 Cause 3: The protocol is stopped manually or the forced switching is performed manually. As
a result, the protection switching fails.
If... Then...
Protocol Stopped
to other causes.
Protocol Started

OptiX OSN 8800/6800/3800
175
If... Then...
is Lockout or Forced Switching
other causes.
is Normal
causes.

----End
Related Information
None
12.19 Transoceanic MSP Ring
This section describes the handling methods for services with transoceanic MSP ring protection
abnormally.
Fault Description
Possible Causes
l Cause 3: The protocol is stopped manually, the forced switching is performed manually.
U2000
OptiX OSN 8800/6800/3800
176
Procedure
1. In the NE Explorer, click the desired NE and choose Configuration > Ring MS from the
Function Tree.
2. In Ring MS interface, click Stop Protocol. Click Close in the Operation Result dialog
box.
box.
4. Check whether services recover. If the services do not recover, proceed to the next substep.
1. Check the settings of the transoceanic MSP ring parameters on the U2000.
If... Then...
The settings of the transoceanic MSP ring
parameters are incorrect
Set the parameters of the multiplex section
to proper values.
For the details about the parameters, refer
to Feature Description.
Check whether services recover.
If the services do not recover, check
The configuration of the transoceanic MSP
ring parameters is correct

NOTE
Transoceanic protocol must be configured on all NEs.
If... Then...
configured.
Description.

If... Then...
B2_EXC, B2_SD
Reference.
OptiX OSN 8800/6800/3800
177

Step 3 Cause 3: The protocol is stopped manually, the forced switching is performed manually. As a
result, the protection switching fails.
If... Then...
Protocol Stopped
to other causes.
Protocol Started

If... Then...
is Lockout or Forced Switching
other causes.
is Normal
causes.

----End
Related Information
None
12.20 SNCP
This section describes the handling methods for services with SNCP protection that fail to
OptiX OSN 8800/6800/3800
178
Fault Description
Possible Causes
U2000
Procedure
Step 1 Cause 1: The configuration of the protection group parameters is incorrect. As a result, the
1. Check the configuration of the protection group parameters on the U2000.
If... Then...
The configuration of the protection group
parameters is incorrect
See the Feature Description to re-
configure the protection group parameters.
services do not recover, check whether the

If... Then...
configured
Configure HP_UNEQ, B3_SD, HP_TIM
as the optional switching conditions. For
the details, see the Feature Description.
The optional switching conditions are
configured
causes.

Step 2 Cause 2: The protection channel works abnormally.
OptiX OSN 8800/6800/3800
179
If... Then...
Check whether the following alarms exist on
the relevant boards:
B2_EXC, B2_SD
For the method of handling the alarms, see the
No alarms Check whether the fault is due to other causes.

Step 3 Cause 3: Locked switching or forced switching is not released.
1. Choose the NE in NE Explorer.
2. Choose Configuration > SNCP Service Control from the Function Tree.
3. In the SNCP Service Control interface, click Query. Click Close in the Operation
Result dialog box.
4. Choose the protection group, and then click Function. Choose Clear from the shortcut
menu, to clear the locked switching or forced switching configuration.
Step 4 Cause 4: The fiber connections on the board are incorrect. As a result, the protection switching
fails.
1. See the protection principles to check whether the fiber connections at the faulty point are
correct. For details of the protection principles, see the Production Description.
If... Then...
The fiber connections are incorrect Reconnect the fibers. Check whether
other causes.
The fiber connections are correct Check whether the fault is due to other
causes.

----End
Related Information
None
12.21 SNCTP
This section describes the handling methods for services with tributary SNCTP protection that
fail to automatically switch to the protection channel when the working channel works
abnormally.
OptiX OSN 8800/6800/3800
180
Fault Description
Possible Causes
U2000
Procedure
Step 1 Cause 1: The configuration of the protection group parameters is incorrect. As a result, the
1. Check the configuration of the protection group parameters on the U2000.
If... Then...
parameters is incorrect
See the Feature Description to re-
configure the protection group parameters.
services do not recover, check whether the

If... Then...
configured
Configure HP_UNEQ, B3_SD, HP_TIM
as the optional switching conditions. For
the details, see the Feature Description.
The optional switching conditions are
configured
causes.

Step 2 Cause 2: The protection channel works abnormally.
OptiX OSN 8800/6800/3800
181
If... Then...
Check whether the following alarms exist on
the relevant boards:
B2_EXC, B2_SD
For the method of handling the alarms, see the
No alarms Check whether the fault is due to other causes.

Step 3 Cause 3: Locked switching or forced switching is not released.
1. Choose the NE in NE Explorer.
2. Choose Configuration > SNCTP from the Function Tree.
3. In the SNCTP interface, click Query Switching Status.
4. Right-click the protection group, and then choose Clear from the shortcut menu, to clear
the locked switching or forced switching configuration.
Step 4 Cause 4: The fiber connections on the board are incorrect. As a result, the protection switching
fails.
1. See the protection principles to check whether the fiber connections at the faulty point are
correct. For details of the protection principles, see the Production Description.
If... Then...
The fiber connections are incorrect Reconnect the fibers. Check whether
other causes.
The fiber connections are correct Check whether the fault is due to other
causes.

----End
NOTE
Related Cases:
Alarms Transiently
OptiX OSN 8800/6800/3800
182
l MC-A23 When the OTU Board Accesses Light, the Laser at Output End is Disabled
l MC-A25 The System Indicates that the Channel Number Is Illegal
l MC-A41 Unsuccessful 1: N Protection Subnet Search
l MC-A91 Creation of Intra-Board Wavelength Protection on the LDG Fails
l MC-A94 The WXCP Protection Configured for the LOG Board Is Invalid
l MC-A98 The Protection Switching Times Out Severely
l MC-A127 WXCP Protection Cannot Be Implemented Due To Wrong Configuration of the
LQG Boards
l MC-A133 In a WDM System with 1:N Optical Channel Protection, the R_LOF Alarm Is
Reported in the Receive Direction on the Client Side When the Laser on the LWC1 Board
in the Protection Channel Is Open
l MC-A139 Automatic Switching Is Caused by the Incorrect Service Configuration of ODUk
SPRing Protection
l MC-A150 How Signals Are Selected When the DCP Board Is Used
l MC-A151 OWSP Protection Switching Fails Due to Incorrect Connection of Fiber Jumpers
On The DCP Boards, DCP Boards Report The MUT_LOS Alarms And TDG Board Reports
The OPU1_PLM Alarm
l MC-A155 Using the LDMD Board to Configure Intra-Board 1+1 Protection Fails Due to
the System Limit and the System Displays "The optical port number exceeds the limit"
l MC-A157 An OptiX OSN 6800 Network Cannot Be Reverted Back to the Working
Channel After Being Restored from an ODUk SNCP Protection Switching, The Board
Reports The ODU_SNCP_PS Alarm
l MC-A159 Services Are Interrupted After the Protection Hold-Off Time Is Set to 10s During
Configuration of Client-Side 1+1 Protection on the OptiX OSN 6800, The System Reports
The R_LOS Alarm
l MC-A161 The NS2 and TDG Boards Report the BUS_ERR Alarms at the Same Time After
ODUk SNCP Protection Is Configured Because The SCC Board Is Faulty
l MC-A171 How to Configure Two TMX Boards in a Client-Side 1+1 Protection Group
Through an SCS Board
l MC-A176 Loss of the Data About an Inter-Subrack Wavelength Protection Group Results
from a Change of an NE ID
l MC-A177 What Is the Difference Between the EOLP Board and the OLP Board
l MC-A220 SNCP Protection Switching Fails Due to Incorrect Fiber Connections
l MC-A228 Intra-Board 1+1 Protection Switching Fails on the OptiX OSN 1800 After a
Change of the NE ID
l MC-A229 Switching Fails Due to Incorrect SNCP Protection Mode on the WDM
Equipment
l MC-A232 The ODUk SNCP Protection Is Abnormal due to Incorrect Fiber Connections
l MC-A233 The LOM Board Fails to Carry Two FC400 Services due to Port Specification
Limitations When Inter-Subrack 1+1 Protection or Client 1+1 Protection Is Configured
l MC-A252 Switching of ODUk SNCP Protection Fails
OptiX OSN 8800/6800/3800
183
13 Automatic Reverting Failures
About This Chapter
This topic describes how to resolve switchover issues when services fail to automatically switch
back to the working channel even after the working channel has resumed normal operation.
For information on the protection schemes supported by the OptiX OSN 8800, OptiX OSN 6800,
and OptiX OSN 3800, see the Feature Description"Feature Overview".
automatically switch services back to the working channel even after the working channel has
resumed normal operations.
This section describes the handling methods for services with SW SNCP protection that cannot
automatically switch back to the working channel even after the working channel resumes
normal operation and the revertive mode is properly configured.
This section describes the handling methods for services with VLAN SNCP protection that
cannot automatically switch back to the working channel even after the working channel resumes
OptiX OSN 8800/6800/3800
Troubleshooting 13 Automatic Reverting Failures
184
This section describes the handling methods in the case that services cannot be switched back
to the working channel after the working channel resumes normal operation even though the
revertive mode is configured.
This section describes the handling methods for services with MS SNCP protection that cannot
This section describes the handling methods for services with DLAG protection that cannot
This section describes the handling methods for services with ODUk SPRing protection that
protection that cannot automatically switch back to the working channel even after the working
channel resumes normal operation and the revertive mode is properly configured.
that cannot automatically switch back to the working channel even after the working channel
resumes normal operation and the revertive mode is properly configured.
13.14 MSP Ring
This section describes the handling methods for services with MSP ring protection that cannot
13.15 Transoceanic Ring MS Protection
This section describes the handling methods for services with transoceanic ring MS protection
13.16 SNCP
This section describes the handling methods for services with SNCP protection that cannot
13.17 SNCTP
This section describes the handling methods for services with SNCTP protection that cannot
OptiX OSN 8800/6800/3800
185
OptiX OSN 8800/6800/3800
186
Symptom
In normal operation of a network, services are switched to the protection channel after the
working channel generates the protection triggering conditions. When the working channel
resumes normal operation, the services cannot be automatically switched back to the working
channel.
The OLP board may be reporting an OLP_PS or OLP_STA_INDI alarm.
Possible Causes
l Cause 1: The value of the Revertive Mode parameter of the protection group has been set
to Non-Revertive
l Cause 2: The working channel works abnormally or failure has not been resolved.
l Cause 4: When the working channel is restored, service are restored to the working channel
after the time specified by WTR Time elapses.
The following figure illustrates the optical line protection automatic reverting failure
OptiX OSN 8800/6800/3800
187
Figure 13-1 Optical line protection automatic reverting failure troubleshooting flowchart
No Yes
Yes No
No
Yes Yes
No
Yes
Yes No
No
Yes
Yes No
No
Set
to Revertive.
Is
Revertive Mode set to
Revertive?
Start
End
Does the working
channel work normally?
Does the time exceed
WTR Time?
working channel.
Wait for a period
longer than
Contact Huawei
engineers.
Are the
the working
channel?
Are the
the working
channel
?
Are the
the working
channel?
Are the
the working
channel ?
switching command
manually issued?
Clear the locked, or
forced switching
command.
Revertive Mode
WTR Time.

U2000
Procedure
to Non-Revertive.
the Function Tree.
2. In the Port Protection window, select one protection group and click Modify to
change Revertive Mode to Revertive.
l Cause 2: The working channel is working abnormally.
1. In the Port Protection window, click Query to query the Working Channel
OptiX OSN 8800/6800/3800
188
2. If Working Channel Status is not Normal, check whether MUT_LOS and
POWER_DIFF_OVER alarms are being reported on the corresponding boards on the
working channel, clear the alarms.
1. In the Port Protection interface, click Query to check the Switching Status
2. If Switching Status is displayed as Lock or Force to Protection Channel, right-click
the protection group, and then choose Clear from the shortcut menu to clear the
switching configuration.
l Cause 4: When the working channel is restored, services are restored to the working channel
1. In the Port Protection window, click Query to check the WTR Time.
2. If service fails to be restored to the working channel after the time specified by WTR
Time elapses, check whether the working channel is normal.
----End
Solution
Symptom
channel.
When the intra-board 1+1 protection is achieved using the OLP board, the OLP board reports
an INTRA_OTU_PS or INTRA_OTU_STA_INDI alarm.
When the intra-board 1+1 protection is realized by dual fed and selective receiving OTU, the
OTU board may report the INTRA_OTU_PS alarm or INTRA_OTU_STA_INDI alarm.
Possible Causes
to Non-Revertive. In the case of the intra-board 1+1 protection configured using an OLP
or DCP board, when the Detection Channel is configured, the Revertive Mode parameter
must be set to Non-Revertive. This is not considered as one of the possible causes when
the protection cannot be restored automatically.
OptiX OSN 8800/6800/3800
189
l Cause 3: Locked, or forced switching commands have been manually issued.
The following figure illustrates the intra-board 1+1 protection automatic reverting failure
Figure 13-2 Intra-board 1+1 protection automatic reverting failure troubleshooting flowchart
No Yes
Yes No
No
Yes Yes
No
Yes
Yes No
No
Yes
Yes No
No
Set
to Revertive.
Is
Revertive?
Start
End
Does the working
WTR Time?
working channel.
Wait for a period
longer than
Contact Huawei
engineers.
Are the
the working
channel?
Are the
the working
channel
?
Are the
the working
channel?
Are the
the working
channel ?
switching command
manually issued?
forced switching
command.
Revertive Mode
WTR Time.

U2000
Procedure
to Non-Revertive.
OptiX OSN 8800/6800/3800
190
the Function Tree.
NOTE
In the case of intra-board 1+1 protection configured using an OLP or DCP board, when the
Monitoring Channel is configured, Revertive Mode can only be set to Non-Revertive.
1. In the Port Protection interface, click Query to query the Working Channel
2. If Working Channel Status is not Normal, check whether R_LOS, R_LOF, R_LOC,
ODUk_PM_LCK, ODUk_LOFLOM, B1_EXC, ODUk_PM_DEG,
ODUk_PM_EXC, POWER_DIFF_OVER, IN_PWR_HIGH and IN_PWR_LOW
alarms are being reported on the corresponding boards on the working channel, clear
the alarms.
l Cause 3: Forced switching commands have been manually issued.
----End
Solution
Symptom
channel.
OptiX OSN 8800/6800/3800
191
l The DCP or OLP board may be reporting a CLIENT_PORT_PS or
CLIENT_PORT_STA_INDI alarm.
l When you use the SCS board to configure the protection, the OTU or tributary board may
report the CLIENT_PORT_PS alarm or CLIENT_PORT_STA_INDI alarm.
Possible Causes
l The value of the Revertive Mode parameter of the protection group has been set to Non-
Revertive.
l The working channel works abnormally or failure has not been resolved.
The following figure illustrates the client 1+1 protection automatic reverting failure
Figure 13-3 Client 1+1 protection automatic reverting failure troubleshooting flowchart
No Yes
Yes No
No
Yes Yes
No
Yes
Yes No
No
Yes
Yes No
No
Set
to Revertive.
Is
Revertive?
Start
End
Does the working
WTR Time?
working channel.
Wait for a period
longer than
Contact Huawei
engineers.
Are the
the working
channel?
Are the
the working
channel
?
Are the
the working
channel?
Are the
the working
channel ?
switching command
manually issued?
forced switching
command.
Revertive Mode
WTR Time.
OptiX OSN 8800/6800/3800
192

U2000
Procedure
to Non-Revertive.
the Function Tree.
1. In the Port Protection window, click Query to query the Working Channel
2. If Working Channel Status is not Normal, check whether the alarms listed in the
trigger conditions are being reported on the relevant boards on the working channel,
clear the alarms.
----End
Solution
This section describes the handling methods for services with SW SNCP protection that cannot
Fault Description
OptiX OSN 8800/6800/3800
193
channel.
OTU board may report SW_SNCP_PS alarm or SW_SNCP_STA_INDI alarm.
Possible Causes
The possible causes of the automatic reverting failure are as follows:
Revertive.
l Locked, or forced switching is not released.
Fault Handling Flow
Figure 13-4 Fault handling flow when automatic switching back to the working channel by SW
SNCP protection fails
No Yes
Yes No
No
Yes Yes
No
Yes
Yes No
No
Yes
Yes No
No
Set
to Revertive.
Is
Revertive?
Start
End
Does the working
WTR Time?
working channel.
Wait for a period
longer than
Contact Huawei
engineers.
Are the
the working
channel?
Are the
the working
channel
?
Are the
the working
channel?
Are the
the working
channel ?
switching command
manually issued?
forced switching
command.
Revertive Mode
WTR Time.

OptiX OSN 8800/6800/3800
194
U2000
Procedure
to Non-Revertive.
Management from the Function Tree. Click the SNCP Service Control tab.
2. On the SNCP Service Control interface, select the desired protection group. Double-
click the Revertive Mode field, and then change Non-Revertive to Revertive.
parameter of the working cross-connection.
2. If Channel Status is not displayed as Normal, check whether the following alarms
of trigger conditions exist on the relevant boards on the working channel. For the
method of handling the alarms, see the Alarms and Performance Events Reference.
l Cause 3: Locked, or forced switching is not released.
2. If Status is displayed as Lockout or Forced (from working to protection) switching
state, choose the protection group. Click Function and then choose Clear from the
shortcut menu to clear the switching configuration.
1. In the SNCP Service Control interface, click Query to check the WTR Time
(mm:ss).
----End
Solution
Symptom
channel.
OptiX OSN 8800/6800/3800
195
Tributary, line or PID board may report an ODU_SNCP_PS alarm or ODU_SNCP_STA_INDI
alarm.
Possible Causes
to Non-Revertive.
The following figure illustrates the ODUk SNCP protection automatic reverting failure
Figure 13-5 ODUk SNCP protection automatic reverting failure troubleshooting flowchart
Wait for a moment
longer than
Yes
Yes No
No
Yes
Yes No
No
Yes Yes
No
No
No
Yes Yes
No
Yes
Yes No
No
Change the SNCP
Type of the protection
group.
Is the SNCP Type
consistent with that required in
the service scenario?
Start
Are the
the working
channel?
Is
Revertive?
the working channel work
abnormally?
WTR time?
working channel.
Contact Huawei
engineers.
End
Are the
the working
channel?
Are the
the working
channel?
Are the
the working
channel?
Are the
the working
channel?
Is a forced,
or locked switching command
manually issued?
Clear the
forced, or locked
switching command.
Set
Revertive Mode
to Revertive.
Does
WTR Time.
OptiX OSN 8800/6800/3800
196

U2000
Procedure
the protection group. In the Operation Result dialog box, click Close.
to Non-Revertive.
1. In the SNCP Service Control window, select the desired protection group. Double-
2. If Channel Status is not Normal, check whether the alarms listed in Trigger
Conditions are being reported on the corresponding boards on the working channel,
clear the alarms.
1. In the SNCP Service Control window, click Query to check the WTR Time.
----End
Solution
This section describes the handling methods for services with VLAN SNCP protection that
OptiX OSN 8800/6800/3800
197
Fault Description
channel.
L4G, TBE, LEM24, LEX4 board of OptiX OSN 6800/OptiX OSN 3800 may report
VLAN_SNCP_PS.
LEM24, LEX4 board of OptiX OSN 8800 may report VLAN_SNCP_PS.
Possible Causes
Revertive.
l Manual, locked or forced switching is not released.
OptiX OSN 8800/6800/3800
198
Fault Handling Flow
Figure 13-6 Fault handling flow when automatic switching back to the working channel by
VLAN SNCP protection fails
No Yes
Yes No
No
Yes Yes
No
Yes
Yes No
No
Yes
Yes No
No
Set
to Revertive.
Is
Revertive?
Start
End
Does the working
WTR Time?
working channel.
Wait for a period
longer than
Contact Huawei
engineers.
Are the
the working
channel?
Are the
the working
channel
?
Are the
the working
channel?
Are the
the working
channel ?
switching command
manually issued?
forced switching
command.
Revertive Mode
WTR Time.

U2000
Procedure
to Non-Revertive.
1. Select the desired Ethernet board in the NE Explorer, and choose Configuration >
Ethernet Service > Ethernet Line Service from the Function Tree. Click the VLAN
SNCP Service Management tab.
OptiX OSN 8800/6800/3800
199
2. On the VLAN SNCP Service Management interface, select the desired protection
group. Double-click the Revertive Mode field, and then change Non-Revertive to
Revertive.
1. In the VLAN SNCP Service Management interface, click Query to check the Link
Status parameter of the working service.
2. If Link Status is not displayed as Normal, check whether the following alarms exist
on the relevant boards on the working channel: R_LOF, R_LOS, R_OOF,
OTUk_LOF, OTUk_LOM, OTUk_AIS. For the method of handling the alarms, see
the Alarms and Performance Events Reference.
l Cause 3: Manual, locked or forced switching is not released.
select Query Switching Status to check the Current Status parameter of the
protection group.
2. If Current Status is displayed as Manual (Active to Standby) Switching State,
Forced (Active to Standby) Switching State or Lockout State, click Set/Query
Switching. Then choose Clear from the shortcut menu, to clear the manual, locked
or forced switching configuration.
1. In the VLAN SNCP Service Management interface, click Query to check the WTR
Time (s).
----End
Solution
Symptom
channel.
Tributary, line may report an ODU_SNCP_PS alarm or ODU_SNCP_STA_INDI alarm.
Possible Causes
OptiX OSN 8800/6800/3800
200
to Non-Revertive.
Fault Handling Flow
The following figure illustrates the tributary SNCP protection automatic reverting failure
Figure 13-7 Tributary SNCP protection automatic reverting failure troubleshooting flowchart
Wait for a period
longer than
Yes
Yes
No
No
Yes
Yes
No
No
Yes Yes
No
No
No
Yes Yes
No
Yes
Yes
No
No
Change the SNCP
Type of the protection
group.
the SNCP Type
consistent with that required
in the service
scenario?
Start
Are the
the working
channel?
Is
Revertive Mode
set to
Revertive ?
the working channel work
abnormally?
WTR Time?
working channel.
Contact Huawei
engineers.
End
Are the
the working
channel?
Are the
the working
channel?
Are the
the working
channel?
Are the
the working
channel?
Clear the
forced, or locked
switching command.
Set
Revertive Mode
to Revertive.
Is
Does
WTR Time.
Is a forced
or locked switching command
manually issued?

U2000
OptiX OSN 8800/6800/3800
201
Procedure
2. In the SNCP Service Control window, click Query to query Protection Type of the
protection group. In the Operation Result dialog box, click Close.
3. Refer to "Dependency and Limitation" and "Parameters" to check whether Protection
Type of the protection group is appropriate for the service scenario.
to Non-Revertive.
1. In the SNCP Service Control window, select the desired protection group. Double-
1. In the SNCP Service Control window, click Query to check the Channel Status
are being reported on the corresponding boards on the working channel, clear the
alarms.
1. In the SNCP Service Control window, click Query to check WTR Time.
----End
Solution
This section describes the handling methods in the case that services cannot be switched back
to the working channel after the working channel resumes normal operation even though the
revertive mode is configured.
Fault Description
In the normal operation of the network, the services are switched to the protection channel after
the working channel generates the protection triggering conditions. When the working channel
resumes the normal operation, the services cannot be automatically switched back to the working
channel.
OptiX OSN 8800/6800/3800
202
Possible Causes
The possible causes of the automatic revertive failure are as follows:
l Cause 1: The working channel works abnormally.
l Cause 2: When the working channel is recovered, the working channel recovery time does
not exceed the specified WTR Time (min).
l Cause 3: The control VLAN channel on an ERPS-enabled Ethernet ring is faulty.
U2000
Procedure
l Cause 1: The working channel works abnormally.
1. If there are alarms on the working channel, clear the alarms. For the method of handling
the alarms, see Alarms and Events Handling.
not exceed the specified WTR Time (min).
1. Select an Ethernet board in NE Explorer.
2. Choose Configuration > Ethernet Protection > ERPS Management.
3. In the ERPS Management interface, click Query to check WTR Time (min).
l Cause 3: The control VLAN channel on an ERPS-enabled Ethernet ring is faulty.
1. Check whether the Ethernet ring has a control VLAN channel. If no, create a control
VLAN channel for the Ethernet ring.
----End
Solution
This section describes the handling methods for services with MS SNCP protection that cannot
Fault Description
channel.
SCC board may report MS_SNCP_PS alarm or MS_SNCP_STA_INDI alarm.
OptiX OSN 8800/6800/3800
203
Possible Causes
Revertive.
Fault Handling Flow
Services cannot be switched back to the working channel in the MS SNCP protection see Figure
13-8.
Figure 13-8 Fault handling flow when automatic switching back to the working channel by MS
SNCP protection fails
No Yes
Yes No
No
Yes Yes
No
Yes
Yes No
No
Yes
Yes No
No
Manually switch the
services to the
protection channel.
Is Revertive Mode
set to Revertive ?
Start
End
Is Working Channel
Status Normal?
working channel.
Wait for a period
longer than
Contact Huawei
engineers.
Are the
the working
channel?
Are the
the working
channel?
Are the
the working
channel?
Are the
the working
channel?
Is a forced
or locked switching
command manually
issued?
Clear the
forced, or locked
switching command.
WTR Time.
WTR Time?

U2000
OptiX OSN 8800/6800/3800
204
Procedure
to Non-Revertive.
Management from the Function Tree. Click SNCP Service Control tab.
2. On the SNCP Service Control interface, select the desired protection group. Double-
2. If Channel Status is displayed as SD, SF check whether the following alarms exist
on the relevant boards: R_LOF, R_LOS, R_LOC, OTUk_LOF, OTUk_LOM,
OTUk_AIS, ODUk_PM_AIS, ODUk_PM_OCI, ODUk_PM_LCK,
ODUk_LOFLOM, REM_SF, B1_EXC, ODUk_PM_EXC, OTUk_EXC, REM_SD.
For the method of handling the alarms, see the Alarms and Performance Events
Reference.
1. In the SNCP Service Control interface, click Query to query the Status parameter
state , click Function, and then choose Clear from the shortcut menu, to clear the
manual, locked or forced switching configuration.
1. In the SNCP Service Control interface, click Query to query the WTR Time
(mm:ss).
----End
Solution
This section describes the handling methods for services with DLAG protection that cannot
Fault Description
channel.
OptiX OSN 8800/6800/3800
205
Possible Causes
Revertive.
Fault Handling Flow
DLAG protection fails
Set Revertive
Mode to Revertive.
No Yes
Yes No
No Yes
Yes No
Start
End
Does the working
Are the
the working
channel?
Contact Huawei
engineers.
Is
the protection
Are the
the working
channel?
working channel.
revertive?

U2000
Procedure
to Non-Revertive
1. Select the NE in the NE Explorer and then choose Configuration > Ethernet
Distributed Link Aggregation Management.
2. Click Query. Double-click Revertive Mode parameter and choose Revertive from
the drop-down list.
1. Resolve the problems with the working channel. Determine if the following alarms
exist on the relevant boards: HARD_BAD, PORT_MODULE_OFFLINE,
LINK_ERR, R_LOS, R_LOF. For more information regarding how to clear the
alarms, see the Alarms and Performance Events Reference.
----End
OptiX OSN 8800/6800/3800
206
Solution
This section describes the handling methods for services with ODUk SPRing protection that
Fault Description
channel.
The NEs at both ends of the channel where the switching occurs may report the ODUKSP_PS
alarm or ODUKSP_STA_INDI alarm.
Possible Causes
l Manual switching, locked switching or forced switching is not released.
OptiX OSN 8800/6800/3800
207
Fault Handling Flow
ODUk SPRing protection fails
No Yes
Yes No
No
Yes Yes
No
Yes
Yes No
No
Start
End
Does
the time exceed
working channel.
Wait for a period
longer than
Contact Huawei
engineers.
Are the
the working
channel?
Are the
the working
channel?
Are the
the working
channel?
Is a forced, or
locked switching
command manually
issued?
Clear the forced, or
locked switching
command.
Does
the working channel
work normally?
WTR Time?
WTR Time.

U2000
Procedure
1. Select the NE in the NE Explorer, and choose Configuration > ODUk SPRing from
the Function Tree.
2. In the Channel Mapping Relation interface, click Query to query the Channel
Status parameter of the working channel.
on the relevant boards on the working channel: R_LOS, R_LOC, HARD_BAD,
OTUk_LOF, OTUk_LOM, OTUk_AIS, ODUk_LOFLOM, ODUk_TCMn_OCI,
ODUk_TCMn_LCK, ODUk_TCMn_AIS, OTUk_EXC, ODUk_TCM6_DEG,
ODUk_TCM6_EXC. For the method of handling the alarms, see the Alarms and
1. In the ODUk SPRing interface, click Query to query the Switching Request-East
or Switching Request-West parameter of the protection group.
OptiX OSN 8800/6800/3800
208
2. If Switching Request-East or Switching Request-West is displayed as Forced
Switching-Ring, or Locked, right-click the protection group, and then choose
Clear from the shortcut menu, to clear the manual, locked or force switching
configuration.
1. In the ODUk SPRing window, click Query to view the WTR Time(mm:ss) value.
During the WTR time, the value of Switching Request-East or Switching Request-
West parameter should be WTR - Ring Switching. After the WTR time elapses, the
protection switching will automatically take place.
----End
Solution
protection that cannot automatically switch back to the working channel even after the working
channel resumes normal operation and the revertive mode is properly configured.
Fault Description
channel.
DCP board may report OWSP_PS alarm or OWSP_STA_INDI alarm.
Possible Causes
OptiX OSN 8800/6800/3800
209
Fault Handling Flow
OWSP protection fails
No Yes
Yes
No
No
Yes Yes
No
Yes
Yes
No
No
working channel.
Start
Are the
the working
channel?
Is a forced
switching command
manually issued?
Are the
the working
channel?
Are the
the working
channel?
End
Clear the
forced switching
command.
Wait for a period
longer than
Contact Huawei
engineers.
Does
the working channel
work normally?
WTR Time?
WTR Time.

U2000
Procedure
1. Select the NE in the NE Explorer, and choose Configuration > Optical Wavelength
Shared Protection from the Function Tree. Click OWSP Protection tab.
2. In the Channel interface, click Query to query the Channel Status parameter of the
working channel.
on the relevant boards on the working channel: MUT_LOS, R_LOS, R_LOC, R_LOF,
ODUk_PM_LCK, OTUk_TIM, ODUk_PM_TIM, ODUk_LOFLOM,
IN_PWR_HIGH, IN_PWR_LOW, B1_EXC, ODUk_PM_DEG, ODUk_PM_EXC,
OTUk_DEG, OTUk_EXC. For the method of handling the alarms, see the Alarms
1. In the OWSP Protection interface, click Query to query the Switching Request-
East or Switching Request-West parameter of the protection group.
OptiX OSN 8800/6800/3800
210
2. If Switching Request-East or Switching Request-West is displayed as Forced
Switching-Ring, or Locked, right-click the protection group, and then choose
Clear from the shortcut menu, to clear the manual, locked or force switching
configuration.
1. In the OWSP Protection interface, click Query to query the WTR Time (s).
----End
Solution
Fault Description
channel.
Possible Causes
Revertive.
l When the working channel is recovered, the working channel recovery time does not exceed
the specified WTR Time (s).
U2000
Procedure
to Non-Revertive.
1. In the NE Explorer, click the desired NE and choose Configuration > Linear MS
from the Function Tree.
OptiX OSN 8800/6800/3800
211
2. In the Linear MS interface, select one protection group and double click Revertive
Mode parameter area. Choose Revertive from drop-down list.
1. Check whether the following alarms exist on the relevant boards on the working
channel: R_LOS, R_LOF, R_LOC, MS_AIS, B2_EXC, B2_SD. For the method of
handling the alarms, see the Alarms and Performance Events Reference.
1. Click Query in Linear MS interface and choose Query Switching Status.
2. If Switching Status-West is Switching or Lockout, right click the protection group
and choose Clear.
not exceed the specified WTR Time (s).
1. In the Linear MS interface, click Query and choose Query Protection Group to
check WTR Time (s).
----End
Solution
13.14 MSP Ring
This section describes the handling methods for services with MSP ring protection that cannot
Fault Description
channel.
Possible Causes
U2000
OptiX OSN 8800/6800/3800
212
Procedure
1. In the NE Explorer, click the desired NE and choose Configuration > Ring MS from
the Function Tree.
2. Click Query in Ring MS interface and choose Query Switching Status.
3. If Switching Status is Forced switching or Lockout, right click the protection group
and choose Clear.
1. In the Ring MS interface, click Query and choose Query Protection Group to check
WTR Time (s).
----End
Solution
13.15 Transoceanic Ring MS Protection
This section describes the handling methods for services with transoceanic ring MS protection
Fault Description
channel.
Possible Causes
U2000
OptiX OSN 8800/6800/3800
213
Procedure
l Cause 2: Manual switching, locked switching or forced switching is not released.
1. In the NE Explorer, click the desired NE and choose Configuration > Ring MS from
the Function Tree.
2. Click Query in Ring MS interface and choose Query Switching Status.
and choose Clear.
1. In the Ring MS interface, click Query and choose Query Protection Group to check
WTR Time (s).
----End
Solution
13.16 SNCP
This section describes the handling methods for services with SNCP protection that cannot
Fault Description
channel.
Possible Causes
Revertive.
OptiX OSN 8800/6800/3800
214
U2000
Procedure
to Non-Revertive.
1. In the NE Explorer, click the desired NE and choose Configuration > SNCP Service
Control from the Function Tree.
2. In the SNCP Service Control interface, select one protection group and double click
Revertive Mode parameter area. Choose Revertive from drop-down list.
channel: R_LOS, R_LOF, MS_AIS, AU_AIS, AU_LOP, HP_LOM, B2_EXC,
B3_SD, B3_EXC, HP_TIM, HP_UNEQ. For the method of handling the alarms, see
l Cause 3: Forced switching is not released.
1. Click Query in the SNCP Service Control interface.
2. Click Close in the Operation Result dialog box.
3. If Current Status is Forced switching to Protection, Manual switching to
Protection or Lockout, click Function and choose Clear.
1. In the SNCP Service Control interface, click Query.
2. Click Close in the Operation Result dialog box.
3. Check WTR Time (s).
----End
Solution
13.17 SNCTP
This section describes the handling methods for services with SNCTP protection that cannot
Fault Description
channel.
OptiX OSN 8800/6800/3800
215
Possible Causes
Revertive.
U2000
Procedure
to Non-Revertive.
1. In the NE Explorer, click the desired NE and choose Configuration > SNCTP from
the Function Tree.
2. In the SNCTP interface, select one protection group and double click Revertive
Mode parameter area. Choose Revertive from drop-down list.
channel: R_LOS, R_LOF, MS_AIS, AU_AIS, AU_LOP, HP_LOM, B2_EXC,
B3_SD, B3_EXC, HP_TIM, HP_UNEQ. For the method of handling the alarms, see
l Cause 3: Manual switching, locked switching or forced switching is not released.
1. Click Query Switching Status in SNCTP interface.
and choose Clear.
1. In the SNCTP interface, click Query Protection Group to check WTR Time (s).
----End
Solution
NOTE
OptiX OSN 8800/6800/3800
216
Related Cases:
Alarms Transiently
l MC-A23 When the OTU Board Accesses Light, the Laser at Output End is Disabled
l MC-A25 The System Indicates that the Channel Number Is Illegal
l MC-A41 Unsuccessful 1: N Protection Subnet Search
l MC-A91 Creation of Intra-Board Wavelength Protection on the LDG Fails
l MC-A94 The WXCP Protection Configured for the LOG Board Is Invalid
l MC-A98 The Protection Switching Times Out Severely
l MC-A127 WXCP Protection Cannot Be Implemented Due To Wrong Configuration of the
LQG Boards
l MC-A133 In a WDM System with 1:N Optical Channel Protection, the R_LOF Alarm Is
Reported in the Receive Direction on the Client Side When the Laser on the LWC1 Board
in the Protection Channel Is Open
l MC-A139 Automatic Switching Is Caused by the Incorrect Service Configuration of ODUk
SPRing Protection
l MC-A150 How Signals Are Selected When the DCP Board Is Used
l MC-A151 OWSP Protection Switching Fails Due to Incorrect Connection of Fiber Jumpers
On The DCP Boards, DCP Boards Report The MUT_LOS Alarms And TDG Board Reports
The OPU1_PLM Alarm
l MC-A155 Using the LDMD Board to Configure Intra-Board 1+1 Protection Fails Due to
the System Limit and the System Displays "The optical port number exceeds the limit"
l MC-A157 An OptiX OSN 6800 Network Cannot Be Reverted Back to the Working
Channel After Being Restored from an ODUk SNCP Protection Switching, The Board
Reports The ODU_SNCP_PS Alarm
l MC-A159 Services Are Interrupted After the Protection Hold-Off Time Is Set to 10s During
Configuration of Client-Side 1+1 Protection on the OptiX OSN 6800, The System Reports
The R_LOS Alarm
l MC-A161 The NS2 and TDG Boards Report the BUS_ERR Alarms at the Same Time After
ODUk SNCP Protection Is Configured Because The SCC Board Is Faulty
l MC-A171 How to Configure Two TMX Boards in a Client-Side 1+1 Protection Group
Through an SCS Board
l MC-A176 Loss of the Data About an Inter-Subrack Wavelength Protection Group Results
from a Change of an NE ID
l MC-A177 What Is the Difference Between the EOLP Board and the OLP Board
l MC-A220 SNCP Protection Switching Fails Due to Incorrect Fiber Connections
l MC-A228 Intra-Board 1+1 Protection Switching Fails on the OptiX OSN 1800 After a
Change of the NE ID
l MC-A229 Switching Fails Due to Incorrect SNCP Protection Mode on the WDM
Equipment
l MC-A232 The ODUk SNCP Protection Is Abnormal due to Incorrect Fiber Connections
OptiX OSN 8800/6800/3800
217
l MC-A233 The LOM Board Fails to Carry Two FC400 Services due to Port Specification
Limitations When Inter-Subrack 1+1 Protection or Client 1+1 Protection Is Configured
l MC-A252 Switching of ODUk SNCP Protection Fails
OptiX OSN 8800/6800/3800
218
14 Optical Power Management Problems
About This Chapter
This topic describes how to troubleshoot optical power management problems.
14.1 IPA Start Failure
This topic describes how to troubleshoot the IPA function when it fails to start.
14.2 IPA End Failure
This topic describes how to troubleshoot the IPA function when it fails to end.
14.3 IPA Start Failure in a Raman System
This topic describes how to troubleshoot the IPA function when it fails to start in a Raman
system.
14.4 IPA End Failure in a Raman System
This topic describes how to troubleshoot the IPA function when it fails to end in a Raman system.
14.5 ALC Start Failure
This topic describes how to troubleshoot the ALC function when it fails to start after the line
attenuation changes when DCN communication between NEs is working normal and there are
no fiber cuts along the line.
14.6 APE Exceptions
When the communication between NEs is working normally and there are no fiber cuts along
the line, the U2000 reports an optical power equilibrium event and then starts APE adjustment.
However, APE does not function and the adjustment fails. This topic describes how to handle
such an exception in the APE function.
14.7 Handling Anomalies in the OPA Function
This section describes fault handling when the OPA function fails to calculate the VOA of the
optical-layer boards after the optical cross-connections are configured.
14.8 Optical Power Management Cases
This section lists cases related to Optical Power Management.
OptiX OSN 8800/6800/3800
Troubleshooting 14 Optical Power Management Problems
219
14.1 IPA Start Failure
This topic describes how to troubleshoot the IPA function when it fails to start.
Symptom
During normal network operations, when a fiber cut occurs, and the intelligent power adjustment
(IPA) function may fail to start. As a result, the OAs at both ends of the optical fiber fail to
automatically shut down the lasers on the output optical ports.
Possible Causes
l Cause 1: The IPA function is disabled.
l Cause 2: The fault is resolved before the time specified by Start Hold-off Time elapses.
l Cause 3: The IPA protection group is configured with auxiliary detection boards. When a
fiber cut occurs, some of the auxiliary detection boards do not report any alarm.
l Cause 4: The IPA protection group is configured with auxiliary detection boards. However,
the auxiliary detection board ports are incorrectly set.
Figure 14-1 illustrates the IPA start failure troubleshooting process.
OptiX OSN 8800/6800/3800
220
Figure 14-1 IPA start failure troubleshooting flowchart
No Yes
Yes
No
Yes
Yes No
No
Yes
Yes No
No
Yes
Yes No
No
Set IPA Status to Enabled.
Is IPA Status set to
Enabled?
Start
Is IPA started?
Is the fault resolved
before the time specified
by Start Hold-off Time
elapses?
Are auxiliary detection
board ports set correctly?
Wait for a period longer
than Start Hold-off Time.
Check the fiber
connections of the OA
board.
Re-set the
auxiliary detection board
ports.
Contact Huawei
engineers.
End
Is IPA started?
Are the line services
restored?
Is IPA started?
Do all the auxiliary detection
boards report IPA-triggering
alarms?

U2000
Procedure
1. In the NE Explorer, select the NE and choose Configuration > IPA Management.
Click Query to check the IPA Status of IPA.
2. If IPA Status is set to Disabled, change it to Enabled. Click Apply.
3. Query the IPA Status of the NE at the opposite end. Ensure that the IPA function of
the NEs at the two ends of the line is set to Enabled.
In case of a fiber cut, the IPA function is enabled only after the start hold-off time expires.
1. In the IPA Management window, click Set Start Delay. In the dialog box that is
displayed, click Query to query the Start Hold-off Time.
OptiX OSN 8800/6800/3800
221
2. Check whether the fault is resolved before the time specified by Start Hold-off
Time elapses.
1. Check whether each auxiliary detection board is reporting IPA-triggering alarms, such
as R_LOS, R_LOF, and OSC_RDI. If some of the auxiliary detection boards are not
reporting such alarms, check whether the fiber connection between the OA board and
the FIU, and that between the FIU and the auxiliary detection board, comply with the
engineering design.
1. Check whether the auxiliary detection board ports are receiving optical signals from
the same direction as the detection board ports. If they are not receiving optical ports,
re-set the auxiliary detection board ports.
----End
Solution
If the problem persists after you take the preceding measures, handle the alarms and faults of
the NE, and contact Huawei technical support for resolving the IPA start failure.
14.2 IPA End Failure
This topic describes how to troubleshoot the IPA function when it fails to end.
Symptom
During normal network operations, when a fiber cut occurs, the IPA function starts. The lasers
on the output optical ports of the OAs at the upstream station of the optical fiber are automatically
shut down. After the optical fiber is restored, the IPA function does not automatically turn the
lasers on the output optical ports back on. As a result, the output optical power of the OAs is not
restored.
Possible Causes
l Cause 1: When the IPA protection group is not configured with any detection board and
is configured with only auxiliary detection boards, all the auxiliary detection boards are
reporting IPA-triggering alarms.
l Cause 2: One or more of IPA function parameters are incorrectly set.
Figure 14-2 illustrates the IPA end failure troubleshooting process.
OptiX OSN 8800/6800/3800
222
Figure 14-2 IPA end failure troubleshooting flowchart
No Yes
Yes
No
Yes
Yes No
No
Yes
Yes
No
Handle the fiber connection
errors or board faults on the
auxiliary detection boards.
Do all the auxiliary
detection boards report
IPA-triggering alarms?
Start
Are the services
restored?
Do the parameter values
comply with the
specifications?
Are the srivices
recovered?
Query NE alarms and
handle other faults.
Contact Huawei
engineers.
End
Are the services
restored?
Set IPA Status to
Disanabled to disable the
IPA function.

U2000
Procedure
l Cause 1: When the IPA protection group is not configured with any detection board and
is configured with only auxiliary detection boards, all the auxiliary detection boards are
as R_LOS, R_LOF, and OSC_RDI. If any of these alarms is being reported, check
the fiber connection of each auxiliary detection board.
2. If the fiber connection of each auxiliary detection board is normal, check whether one
of the auxiliary detection boards is faulty.
l Cause 2: One or more of IPA function parameters are incorrectly set.
1. In the NE Explorer, click the NE and choose Configuration > IPA Management.
2. In the IPA Management window, click Query and check whether the IPA parameters
are correctly set. For more information about how to set each parameter, refer to
"Dependency and Limitation" and "Parameters".
OptiX OSN 8800/6800/3800
223
NOTE
l Check whether the Off Period, On Period, and Start Test Duration values of the two
jointly used IPA pairs are the same.
l Check whether the On Period value of the two IPA pairs is the same as the recommended
value calculated based on the number of intermediate stations.
----End
Solution
If the problem persists after you take the preceding measures, disable the IPA function by setting
the IPA Status in the IPA Management window to Disabled. In the WDM interface window
of the corresponding board, confirm that Laser Status of the transmit optical port of Laser
Control Board is set to On.
Check whether the services are restored. If services are not restored, query the alarms of the NE
and clear the alarms and faults of the NE. If the services are still not restored, contact Huawei
technical support for resolving the IPA end failure.
14.3 IPA Start Failure in a Raman System
This topic describes how to troubleshoot the IPA function when it fails to start in a Raman
system.
Symptom
During normal network operations, when a fiber cut occurs, the IPA function fails to start. As a
result, the OAs at both ends of the optical fiber fail to automatically shut down the lasers on the
output optical ports.
Possible Causes
l The IPA function is disabled.
l The fault is resolved before the time specified by Start Hold-off Time elapses.
l The communication between the case-shape Raman pump amplifier unit for C-band
(CRPC) frame and the subrack is faulty.
l The preset power threshold of the detection board is too low.
l The preset power threshold of the Raman board is too low.
l The IPA protection group is configured with auxiliary detection boards. When a fiber cut
occurs, some of the auxiliary detection boards do not report any alarm.
l The IPA protection group is configured with auxiliary detection boards. However, the
auxiliary detection board ports are incorrectly set.
l IPA parameters are incorrectly set.
CAUTION
Ensure that the optical fibers are properly connected and the configuration is correct.
OptiX OSN 8800/6800/3800
224
NOTE
When the RAU1 or RAU2 board functions as the Raman amplifier,
l The TN14FIU and OSC boards function as the auxiliary detection boards to implement IPA, you do
not need to configure the detection board. In this case, IPA Detection Board Threshold cannot be
set.
l It does not support fiber-break detection and therefore the Raman Board Threshold cannot be set.
Figure 14-3 illustrates the IPA start failure in a Raman system troubleshooting process.
OptiX OSN 8800/6800/3800
225
Figure 14-3 IPA start failure in a Raman system troubleshooting flowchart
Is IPA Status set to
Enabled?
Is the fault resolved before
the time specified by Start
Hold-off Time elapses?
No Yes
Yes No
Yes
Yes No
No
Yes
Yes No
No
Yes
Yes No
No
Yes
Yes
No
No
Yes
Yes No
No
Yes
Yes No
No
Start
Is IPA started?
Do all auxiliary detection
boards report IPA-triggering
alarms?
Are all auxiliary
detection board ports
set correctly?
Do the parameter
specifications?
Wait for a period longer
than Start Hold-off Time.
Check the connectors and
replace the network cables.
Re-calculate and
change the threshold.
Contact Huawei
engineers.
End
Yes
No
?
Re-calculate and
?
Is the receive optical power
of the detection board lower
than the threshold?
Yes
Is the communication
between CRPC frame and
the master subrack normal?
Set IPA Status to
Enabled.
Is IPA started?
Is IPA started?
Is IPA started?
Is IPA started?
Are the line services
restored?
Is IPA started?
Is IPA started?
Re-set the auxiliary
detection board ports.
Check the fiber connections
of the OA board.
of the Raman board lower
than the threshold?

OptiX OSN 8800/6800/3800
226
U2000
Procedure
Then click Query to query IPA Status.
2. If IPA Status is set to Disabled, change it to Enabled and click Apply.
3. Query IPA Status of the opposite NE. Ensure that IPA Status of the NEs at both ends
of the line is set to Enabled.
After the fiber cut occurs, the IPA function is enabled only after the start hold-off time
elapses.
1. In the IPA Management window, click Set Start Delay. In the dialog box that is
displayed, click Query to query the Start Hold-off Time.
2. Check whether the fault is resolved before the time specified by Start Hold-off
Time elapses.
l Cause 3: The communication between the CRPC frame and the subrack is faulty.
1. On the U2000, check whether the CRPC board status is normal.
2. If the query fails, check whether the connectors and network cables are properly
installed.
l Cause 4: The preset optical value of the detection board threshold is too low.
1. Test the actual receive optical power of the detection board, and compare the test result
with the value of the IPA parameter IPA Detection Board Threshold.
2. If the actual receive optical power is higher than the value of Raman Board
Threshold, recalculate the Raman Board Threshold value and change it to a value
higher than the actual receive optical power of the detection board.
NOTE
For the Raman Board Threshold calculation method, refer to "Parameters".
3. If the actual receive optical power is higher than the value of IPA Detection Board
Threshold, recalculate the IPA Detection Board Threshold value and change it to
a value higher than the actual receive optical power of the detection board.
NOTE
For the IPA Detection Board Threshold calculation method, refer to "Parameters".
l Cause 5: The preset value of the Raman board threshold is too low.
1. Test the actual receive optical power of the Raman board, and compare the test result
with the IPA parameter Raman Board Threshold.
2. If the actual receive optical power is lower than the Raman board threshold, recalculate
the Raman board threshold and change it to a value lower than the actual receive
optical power.
NOTE
OptiX OSN 8800/6800/3800
227
as R_LOS, R_LOF, and OSC_RDI. If some of the auxiliary detection boards are not
reporting such alarms, check whether the fiber connection between the OA board and
the FIU, and that between FIU and the auxiliary detection board, comply with the
engineering design.
1. Check the auxiliary detection board ports are receiving optical signals from the same
direction as the detection board ports. If they are not receiving optical signals, re-set
the auxiliary detection board ports.
l Cause 8: IPA parameters are incorrectly set.
1. In the IPA Management window, click Query and check whether IPA parameters
are correctly set. For more information about how to set each parameter, refer to
NOTE
Main IPA parameters include Detection Board, Laser Control Board, IPA Detection Board
Threshold, Raman Board Threshold, and Raman Board Alarm Reporting.
----End
Solution
If the problem persists after you take the preceding measures, clear the alarms and faults of the
NE. Contact Huawei technical support for resolving the IPA function failure.
14.4 IPA End Failure in a Raman System
This topic describes how to troubleshoot the IPA function when it fails to end in a Raman system.
Symptom
During normal network operations, when a fiber cut occurs, the IPA function starts. The lasers
on the output optical ports of the OAs at both ends of the optical fiber are automatically shut
down. After the optical fiber is restored, the IPA function does not automatically turn \the lasers
on the output optical ports back on. As a result, the output optical power of the OAs is not
restored.
Possible Causes
l When the IPA protection group is not configured with a Detection Board and is configured
with only auxiliary detection boards, all the auxiliary detection boards are reporting IPA-
triggering alarms.
l The preset value of the Raman board threshold is too high.
l The preset value of the detection board threshold is too high.
l IPA parameters are incorrectly set.
OptiX OSN 8800/6800/3800
228
l The lasers on the local and remote Raman boards are not turned on manually within the
time specified by On Period or Start Test Duration.
NOTE
When the RAU1 or RAU2 board functions as the Raman amplifier,
l The TN14FIU and OSC boards function as the auxiliary detection boards to implement IPA, you do
not need to configure the detection board. In this case, IPA Detection Board Threshold (dBm)
cannot be set.
l It does not support fiber-break detection and therefore the Raman Board Threshold (dBm) cannot
be set.
Figure 14-4 illustrates the IPA function failure in a Raman system troubleshooting process.
OptiX OSN 8800/6800/3800
229
Figure 14-4 IPA function failure in a Raman system troubleshooting flowchart
Yes Yes
No
No
Yes
Yes No
No
Yes
No
No Yes
Yes
No
Start
Are the services
restored?
End
Modify the
parameters.
Query NE alarms and
handle other faults.
Contact Huawei
engineers.
No Yes
Yes
No
Re-calculate and change
the threshold.
of the detection board
higher than the threshold?
Handle the fiber
connection errors or
board faults on the
auxiliary detection
boards.
Are the services
restored?
Are the services
restored?
Re-calculate and
Set IPA Status
to Disabled to disable
the IPA function.
Are the services
restored?
Do all auxiliary
detection boards
report IPA-triggering
alarms?
of the Raman board higher
than the threshold?
Do the other parameter
specifications?
Are the services
restored?
Yes
Yes No
No
Are the lasers
manually turned on
within the specified
time?
Are the services
restored?
Manually turn on the
lasers within the
specified time.

U2000
OptiX OSN 8800/6800/3800
230
Procedure
l Cause 1: When the IPA protection group is not configured with a Detection Board and is
configured with only auxiliary detection boards, all the auxiliary detection boards are
as R_LOS, R_LOF, and OSC_RDI. If some of the auxiliary detection boards are
reporting such alarms, check the fiber connection of each auxiliary detection board.
2. If the fiber connection of each auxiliary detection board is normal, check whether one
of the auxiliary detection boards is faulty.
l Cause 2: The preset value of the Raman board threshold is too high.
1. Test the actual receive optical power of the Raman board, and compare the test result
with the IPA parameter Raman Board Threshold.
2. If the actual receive optical power is lower than the Raman board threshold, recalculate
the Raman board threshold and change it to a value lower than the actual receive
optical power.
NOTE
l Cause 3: The preset value of the detection board threshold is too high.
1. Test the actual receive optical power of the detection board, and compare the test result
with the IPA parameter IPA Detection Board Threshold.
2. If the actual receive optical power is lower than the detection board threshold,
recalculate the detection board threshold and change it to a value lower than the actual
receive optical power.
NOTE
For the IPA Detection Board Threshold calculation method, refer to "Parameters".
l Cause 4: IPA parameters are incorrectly set.
2. In the IPA Management window, click Query to check whether IPA parameters are
correctly set. For more information about how to set each parameter, refer to
NOTE
Do the follows to check the parameters:
l Check whether the Off Period, On Period and Start Test Duration values of the two
jointly used IPA pairs are the same.
l Check whether the value of On Period value of the two IPA pairs is the same as the
recommended value calculated based on the number of intermediate stations.
l Cause 5: The lasers on the local and remote Raman boards are not turned on manually
within the time specified by On Period or Start Test Duration.
1. Check whether the On Period and Start Test Duration values of the two IPA pairs
is the same as the recommended value calculated based on the number of intermediate
stations.
2. Manually turn on the lasers on the local and remote Raman boards within the specified
time.
OptiX OSN 8800/6800/3800
231
NOTE
This operation applies only to the scenario where lasers need to be manually opened after Laser
Restart Mode is set to Manual.
If the CRPC03 and ROP board are involved in the IPA function, the laser on the CRPC03 and ROP
board need to be manually opened.
----End
Solution
If the problem persists after you take the preceding measures, set the IPA Status in the IPA
Management window to Disabled to disable the IPA function. In the WDM Interface window
of the corresponding board, confirm that the Laser Status of the transmit optical interface of
the laser control board is set to On.
Check whether the services are restored. If services have not been restored, query the alarms of
the NE and clear the alarms and faults of the NE. If the services are still not restored, contact
Huawei technical support for resolving the IPA function failure.
14.5 ALC Start Failure
This topic describes how to troubleshoot the ALC function when it fails to start after the line
attenuation changes when DCN communication between NEs is working normal and there are
no fiber cuts along the line.
Symptom
During normal operations of an ALC-enabled network, the attenuation of a line section changes
and the ALC function does not start. As a result, all OAs at each downstream station cannot
make adjustments. This affects the system OSNR and service transmission.
Possible Causes
l Cause 1: The ALC Automatic Regulation Switch is set to Disabled.
l Cause 2: ALC stops abnormally due to other external causes. ALC nodes report the event
indicating that ALC has ended unexpectedly.
l Cause 3: MUT_LOS or BD_STATUS alarms are being reported on the related board.
l Cause 4: ALC parameters are configured incorrectly. Therefore, the consistency check
fails.
Figure 14-5 illustrates the ALC function failure troubleshooting process.
OptiX OSN 8800/6800/3800
232
Figure 14-5 ALC function failure troubleshooting flowchart
No Yes
Yes No
Yes
No
Yes Yes
No
Yes
Yes No
No
No
Start
Start ALC. Is ALC started?
Does any node report
the event indicating that
ALC has ended
unexpectedly?
Is the consistency check
successful?
Is ALC started?
Is ALC started?
Clear the alarm.
Check and modify
ALC parameter values.
Contact Huawei
engineers.
End
Is Automatic
Regulation Switch
set to Enabled ?
Is the
MUT_LOS or BD_STATUS
alarm being reported?

U2000
Procedure
l Cause 1: The ALC Automatic Regulation Switch is set to Disabled.
1. Choose Configuration > WDM ALC Management from the Main Menu. In the
WDM ALC Management window that is displayed, click NG WDM Single Station
Configuration tab.
2. In the left-hand NE list, select the desired NE. Check whether the Automatic
Regulation Switch is set to Disabled. If it is disabled, enable ALC. For more
information, refer to "Starting Automatic Link Adjustment".
l Cause 2: ALC stops abnormally due to other external causes. ALC nodes report the event
indicating that ALC has ended unexpectedly.
1. On the left of the WDM ALC Management window, query the ALC events reported.
Check whether there are events indicating that the ALC has ended unexpectedly. If
the ALC has ended unexpectedly, identify the reason.
l Cause 3: MUT_LOS or BD_STATUS alarms are being reported on the related board.
OptiX OSN 8800/6800/3800
233
1. Check whether MUT_LOS or BD_STATUS alarms are being reported on the ALC-
related OA and VOA boards at the station. If either of these alarms is being reported,
clear the alarm.
l Cause 4: ALC parameters are configured incorrectly. Therefore, the consistency check
fails.
1. Perform a consistency check of the ALC links. For more information, refer to
"Performing Consistency Check of ALC Links". If the consistency check fails, check
whether the ALC parameters of each ALC node are configured correctly. For details
on how to set each parameter, refer to "Dependency and Limitation and "Parameters".
----End
Solution
If the problem persists after you take the preceding measures, query NE alarms and clear the
alarms and faults on the NE. Contact Huawei technical support for resolving ALC function
faults.
14.6 APE Exceptions
When the communication between NEs is working normally and there are no fiber cuts along
the line, the U2000 reports an optical power equilibrium event and then starts APE adjustment.
However, APE does not function and the adjustment fails. This topic describes how to handle
such an exception in the APE function.
The OptiX OSN 3800 does not support the APE function.
Fault Description
During normal operations on an APE-enabled network, the U2000 reports an optical power
equilibrium event and then starts APE adjustment. However, the system fails to automatically
adjust the optical power at the transmit end of each channel or report an event indicating that
APE has ended unexpectedly. In this case, the equilibrium of the receive-end optical power and
OSNR cannot be ensured.
NOTE
If a fiber cut occurs along the line or communication is abnormal, handle the network faults.
NOTE
If the U2000 reports both an ALC event and an optical power equilibrium event, start the ALC function.
If the optical power equilibrium event persists after the adjustment is completed, start the APE function.
Possible Causes
l Cause 1: APE parameters are configured incorrectly.
l Cause 2: The Optical Interface Attenuation Ratio of the APE power regulation unit has
reached a critical point and can no longer be adjusted. As a result, the adjustment cannot
be started.
OptiX OSN 8800/6800/3800
234
l Cause 3: Limited APE adjustment is performed and further adjustment is required.
l Cause 4: The Standard Power Offset settings are insufficient to meet the requirements of
the live network.
Figure 14-6 illustrates the APE function exception troubleshooting process.
Figure 14-6 APE function exception troubleshooting flowchart
No Yes
Yes
No
Yes
Yes No
No
Yes
Yes
No
Are alarms being reported
on the regulation and
monitoring units?
Are there alarms on the
regulating and monitoring
units?
Start
Is optical power
adjusted?
Do the APE parameter
specifications?
Restart APE.
Re-calibrate the value of
Standard Power Offset.
End
Is there any margin in
Optical Interface
Attenuation Ratio of the
APE regulation unit?
Is the difference between
ActualPower Offset and Standard
Power Offset lower than the
threshold?
No
Audust the optical power
budget of the line.
Is optical power
adjusted?
Is optical power
adjusted?
Is optical power
adjusted?
Contact Huawei engineers.
Is optical power
adjusted?
No
No
No
Yes
Yes
Yes

U2000
OptiX OSN 8800/6800/3800
235
Procedure
l Cause 1: APE parameters are configured incorrectly.
1. In the NE Explorer, select the desired NE and choose Configuration > Optical Power
Equilibrium from the Function Tree.
2. Click Query to check whether APE parameters are configured correctly. For more
information about how to set each parameter, refer to "Dependency and Limitation
and Parameters".
NOTE
Main APE parameters include Power Monitoring Unit, Odd Wavelength Power Regulation
Unit, Even Wavelength Power Regulation Unit, and Monitoring Flag of the related
wavelength.
l Cause 2: The Optical Interface Attenuation Ratio of the APE power regulation unit has
reached a critical point and can no longer be adjusted. As a result, the adjustment cannot
be started.
1. In the NE Explorer, select the desired power regulation unit and choose
Configuration > WDM Interface to query the Optical Interface Attenuation
Ratio board parameter.
2. Check whether the Optical Interface Attenuation Ratio of each optical port where
the APE monitoring wavelength is located has reached the critical value and there is
no margin for adjustment.
3. If the Optical Interface Attenuation Ratio value has reached this point, adjust the
optical attenuation of the regulation unit at the upstream station, thereby decreasing
the optical attenuation required by the local station.
l Cause 3: Insufficient APE adjustment has occurred and further adjustment is required.
1. In the NE Explorer, select the desired NE and choose Configuration > Optical Power
Equilibrium from the Function Tree.
2. Query the Actual Power Offset and Standard Power Offset of the APE monitoring
wavelength and the Power Unbalance Threshold.
3. If the maximum difference between Actual Power Offset and Standard Power
Offset in all monitoring wavelengths is less than 7 dB and Power Unbalance
Threshold uses the default value (1.5), start the APE function again.
4. If the maximum difference between Actual Power Offset and Standard Power
Offset in all monitoring wavelengths is greater than 7 dB and Power Unbalance
Threshold uses the default value (1.5), increase the value of Power Unbalance
Threshold and start the APE function again.
NOTE
The Power Unbalance Threshold ranges from 0.5 dBm to 3 dBm.
5. If the APE function starts successfully, set Power Unbalance Threshold to the
original value.
l Cause 4: The Standard Power Offset settings are insufficient to meet the requirements of
the live network.
1. Re-design the optical power budget and re-calibrate the Standard Power Offset.
----End
OptiX OSN 8800/6800/3800
236
Solution
If the problem persists after you take the preceding measures, contact Huawei technical support
for resolving the APE function faults.
14.7 Handling Anomalies in the OPA Function
This section describes fault handling when the OPA function fails to calculate the VOA of the
optical-layer boards after the optical cross-connections are configured.
Fault Description
After the optical cross-connections in automatic mode are configured, the optical path is
unavailable.
Possible Causes
l Cause 1: The rated optical power of the OA board is set incorrectly, and thus the NE reports
the OPA_FAIL_INDI alarm.
l Cause 2: The optical power budget is insufficient, and thus the NE reports the
OPA_FAIL_INDI alarm.
U2000
Procedure
l Cause 1: The rated optical power of the OA board is set incorrectly, and thus the NE reports
the OPA_FAIL_INDI alarm.
1. In Explorer, choose the desired OA board.
2. In Function Tree on the left side, choose Configuration > WDM Interface and then
select Advanced Attributes.
3. Double-click the Rated Optical Power (dBm) fields of the input and output
interfaces, and modify the values.
l Cause 2: The optical power budget is insufficient, and thus the NE reports the
OPA_FAIL_INDI alarm.
1. Adjust the system optical power budget, which is insufficient.
----End
Solution
After the above steps are performed, contact Huawei engineers to remove the faults in the OPA
function.
14.8 Optical Power Management Cases
This section lists cases related to Optical Power Management.
OptiX OSN 8800/6800/3800
237
14.8.1 Automatic Power Equilibrium (APE)
Case analysis related to Automatic Power Equilibrium (APE) cases.
NOTE
The following cases are the cases relevant to the OptiX WDM product series.
Related Cases:
l MC-A8 The TN11OAU101 at the Transmit End Reports the MUT_LOS Alarm
14.8.2 Automatic Level Control (ALC)
Case analysis related to Automatic Level Control cases.
NOTE
Related Cases:
l MC-A77 Improper Configuration of Protocol Channels Results in a Failure of the ALC to
Start
l MC-A81 The Created ALC Link on OptiX OSN 6800 Cannot Be Automatically Adjusted
l MC-A121 The T2000 Reports a Failure In Querying the ALC Link Status Because Of Too
Many NEs On the Link
l MC-A169 T2000 Reports Errors After the Standard Optical Power of Single Wavelength
Is Set to 7 dBm with ALC in Power Reference Mode
14.8.3 Intelligent Power Adjustment (IPA)
Case analysis related to Intelligent Power Adjustment cases.
NOTE
Related Cases:
l MC-A78 When the IPA Is Set or Deleted, the OAU Alarm Threshold Changes Due to
Version Features
l MC-A116 Failure in Configuring the SC2 as an Auxiliary Detection Board in the IPA
Protection Group
l MC-A175 How to Clear the LASER_HAZARD_WARNING Alarms Reported on Certain
OBU and OAU Boards After an Upgrade of Software
14.8.4 Intelligent Power Adjustment (IPA) of Raman System
Case analysis related to Intelligent Power Adjustment (IPA) of Raman System cases.
NOTE
Related Cases:
OptiX OSN 8800/6800/3800
238
l MC-A116 Failure in Configuring the SC2 as an Auxiliary Detection Board in the IPA
Protection Group
OptiX OSN 8800/6800/3800
239
15 Packet Service Problems
About This Chapter
This topic describes the symptoms, impact, and possible causes of MPLS tunnel faults such as
creation failures or service interruptions. In addition, this topic describes the required tools,
15.1 Handling MPLS Tunnel Faults
This section describes the MPLS tunnel faults such as the creation failure or service interruption
in terms of the symptoms, impact on the system, possible causes, tools required for
troubleshooting, troubleshooting procedure, and precautions that should be taken during the
troubleshooting.
15.2 Handling PW Faults
This section describes the PW faults such as the creation failure or service interruption in terms
of the symptoms, impact on the system, possible causes, tools required for troubleshooting,
troubleshooting procedure, and precautions that should be taken during the troubleshooting.
15.3 Native Ethernet Service Troubleshooting
The Ethernet services based on the packet mode are transmitted over a packet switched network.
The faults of native Ethernet services include service interruption and service degradation.
15.4 PWE3 Ethernet Service Troubleshooting
This topic describes how to troubleshoot PWE3 Ethernet service interruption or packet loss in
terms of the symptoms, impact on the system, possible causes, tools required for troubleshooting,
15.5 Tunnel APS Troubleshooting
This topic describes the symptom of common faults when the Tunnel APS function is enabled
and the solution to the relevant fault.
OptiX OSN 8800/6800/3800
Troubleshooting 15 Packet Service Problems
240
15.1 Handling MPLS Tunnel Faults
This section describes the MPLS tunnel faults such as the creation failure or service interruption
in terms of the symptoms, impact on the system, possible causes, tools required for
troubleshooting, troubleshooting procedure, and precautions that should be taken during the
troubleshooting.
Symptoms
Symptom 1: Creating the tunnel fails, and thus the service is unavailable.
Symptom 2: The tunnel is faulty, and thus the service is interrupted.
Symptom 3: The protection switching fails, and thus the service is interrupted.
If the tunnel is faulty, the service carried by this tunnel on the network is affected, but the services
carried by other tunnels are normal.
Possible Causes
Cause 1: Creating the tunnel fails.
Cause 1: The routing fails.
Cause 2: The physical link where the tunnel resides is faulty.
Cause 1: The protection switching fails.
Tools, Instruments, and Materials
l U2000
Procedure
Step 1 For symptom 1: Creating the tunnel fails, and thus the service is unavailable.
1. Cause 1: Creating the cross-connection fails.
a. Check whether different NEs on the network use the same network segment. If
different NEs use the same network segment, change the IP address of the port.
b. Check whether the tunnel is configured with the incompatible protection feature. For
details, see the Release Notes.
Step 2 For symptom 2: The tunnel is faulty, and thus the service is interrupted.
1. Cause 1: The routing fails.
OptiX OSN 8800/6800/3800
241
a. According to the network planning, check whether the parameters of the ports such
as the IP address of the port at the two ends of the tunnel are correctly set. Correct the
parameter settings, and then create the tunnel again.
b. Check whether there is a complete and reachable link between the NEs where the
source and sink nodes of the tunnel reside. If the link does not exist, repair the
incomplete or faulty part of the link.
2. Cause 2: The physical link where the tunnel resides is faulty.
a. Check whether the HARD_BAD or ETH_LOS alarm indicating that the physical link
used by the tunnel is faulty exists in the system. If any alarm exists, take priority to
handle it.
b. Enable the tunnel OAM function. Then, check and handle the following alarms that
exist in the system, MPLS_TUNNEL_LOCV, MPLS_TUNNEL_SD and
MPLS_TUNNEL_SF.
c. Check whether anomalies such as board faults or NE resetting exist on the opposite
equipment If yes, rectify the anomalies.
Step 3 For symptom 3: The protection switching fails, and thus the service is interrupted.
1. Cause 1: The protection switching fails.
a. The MPLS tunnel APS protection switching fails. For details, see Feature
Description.
----End
Related Information
None
15.2 Handling PW Faults
This section describes the PW faults such as the creation failure or service interruption in terms
of the symptoms, impact on the system, possible causes, tools required for troubleshooting,
Symptoms
Symptoms 1: Creating the PW fails, and thus the service is unavailable.
Symptoms 2: The PW is faulty, and thus the service is interrupted, or packet loss or bit errors
occur in the service.
If a PW is faulty, the service carried in the PW is affected, but the services carried by other PWs
are normal.
Possible Causes
Cause 1: Creating the PW cross-connection fails.
OptiX OSN 8800/6800/3800
242
Cause 1: The physical link is faulty.
Cause 2: The tunnel where the PW resides is faulty.
Cause 3: The protection switching fails.
Cause 4: The equipment is faulty.
l U2000
Procedure
Step 1 For symptom 1: Creating the PW fails, and thus the service is unavailable.
1. Cause 1: Creating the PW cross-connection fails.
a. Check whether the number of PWs reaches the upper limit of the NE or that of the
board. If yes, make a plan again or delete redundant PWs.
b. Check whether the label of PW is existent. If yes, modify the label of PW.
Step 2 For symptom 2: The PW is faulty, and thus the service is interrupted, or packet loss or bit
errors occur in the service.
1. Cause 1: The physical link is faulty.
a. Check whether the physical link between the source and sink nodes of the PW are
normal, and whether the R_LOS, or ETH_LOS alarm exists in the system.
b. If the alarm exists, take priority to handle the ETH_LOS alarm.
2. Cause 2: The tunnel where the PW resides is faulty.
a. For details on the tunnel faults, see 15.1 Handling MPLS Tunnel Faults.
3. Cause 3: The protection switching fails.
a. The PW APS protection switching fails.
4. Cause 4: The equipment is faulty.
a. Check whether anomalies such as board faults or NE resetting exist on the opposite
equipment. If yes, rectify the anomalies.
----End
Related Information
None
15.3 Native Ethernet Service Troubleshooting
The Ethernet services based on the packet mode are transmitted over a packet switched network.
The faults of native Ethernet services include service interruption and service degradation.
Symptom
Symptom 1: Ethernet services are interrupted.
OptiX OSN 8800/6800/3800
243
Symptom 2: Ethernet services are degraded. For example, they have great delays, packet loss,
or incorrect packets.
Impact on System
Ethernet services are interrupted or degraded.
Possible Causes
l Cause 1: Services are incorrectly configured or parameter settings at local equipment are
inconsistent with those at its interconnected equipment. Parameter settings include settings
for loopbacks on Ethernet ports, loopbacks on transmission lines, enabling statuses/
working modes of Ethernet ports, and flow control for Ethernet ports.
l Cause 2: The local/interconnected equipment is faulty or bit errors occur on lines.
l Cause 3: The network cable is faulty.
l Cause 4: The external electromagnetic interference is severe.
U2000 and test instruments
Procedure
Step 1 Troubleshoot an Ethernet service fault.
1. Cause 1: Services are incorrectly configured or parameter settings at local equipment
are inconsistent with those at its interconnected equipment. Parameter settings
include settings for loopbacks on Ethernet ports, loopbacks on transmission lines,
enabling statuses/working modes of Ethernet ports, and flow control for Ethernet
ports.
a. Check whether a loopback is configured for an Ethernet port or a transmission line.
If misoperations cause a port/line loopback, correct the settings. If no loopback is
configured, go to the next step.
b. Check whether Ethernet port settings regarding enabling status, working mode, and
flow control at local equipment are consistent with those at its interconnected
equipment. If inconsistent, correct the settings; if consistent, go to the next step.
c. Check whether the Ethernet protocol and Ethernet service configurations (especially
the attributes of the Ethernet port) are correct.
Step 2 Troubleshoot an abnormal RMON performance event.
1. Cause 1: Services are incorrectly configured or parameter settings at local equipment
are inconsistent with those at its interconnected equipment. Parameter settings
include settings for loopbacks on Ethernet ports, loopbacks on transmission lines,
enabling statuses/working modes of Ethernet ports, and flow control for Ethernet
ports.
a. Check whether working rate settings and working mode settings at local equipment
are consistent with those at its interconnected equipment.
2. Cause 2: The local/interconnected equipment is faulty or bit errors occur on lines.
OptiX OSN 8800/6800/3800
244
a. Query the real-time performance measurement statistics of the Ethernet port with
reference to Feature Description.
b. Change the Ethernet port that receives services. If the RMON performance statistics
of the new port do not contain FCS errors, the hardware of the original port is faulty;
otherwise, the network port of the interconnected equipment may be faulty. To check
it out, go to the next step.
3. Cause 3: The network cable is faulty.
a. Check the network cable. If the network cable is not qualified, replace it with a new
one.
NOTE
When an Ethernet port works in auto-negotiation mode, its interconnected port must not work
in full duplex mode.
4. Cause 4: The external electromagnetic interference is severe.
a. Reduce external electromagnetic interference.
----End
Related Information
None.
15.4 PWE3 Ethernet Service Troubleshooting
This topic describes how to troubleshoot PWE3 Ethernet service interruption or packet loss in
terms of the symptoms, impact on the system, possible causes, tools required for troubleshooting,
Symptoms
Symptom 1: The PWE3 Ethernet service is interrupted.
Symptom 2: The PWE3 Ethernet service loses packets or has errored packets.
PWE3 Ethernet service interruption, PWE3 packet loss, or errored PWE3 packets may impact
the services that the equipment receives.
Possible Causes
Cause 1: The board hardware is faulty, the board temperature is above the upper
threshold, or the communication between boards fails. As a result, the board cannot
work properly.
Cause 2: The PWE3 Ethernet port is misconnected and the port negotiation fails.
Cause 3: Loopback is configured for the port.
Cause 4: Dynamically learning the entries in the ARP table fails.
OptiX OSN 8800/6800/3800
245
Cause 5: The service configuration is incorrect.
Cause 1: The signals on the receive side are lost.
Cause 2: The configured traffic limit is excessively low at the port and configurations
of the source and sink ports are inconsistent.
l U2000
Procedure
Step 1 For symptom 1: The PWE3 Ethernet service is interrupted.
1. Cause 1: The board hardware is faulty, the board temperature is above the upper
threshold, or the communication between boards fails. As a result, the board cannot
work properly.
a. Query the current alarms of the system to check for the HARD_BAD or
COMMUN_FAIL alarm and the board that reports the alarm.
b. Handle the HARD_BAD or COMMUN_FAIL alarm. For details, refer to the Alarms
and Performance Events Reference manual.
2. Cause 2: The PWE3 Ethernet port is misconnected and the port negotiation fails.
a. Check for the ETH_LOS alarm of the system and handle the ETH_LOS alarm.
3. Cause 3: Loopback is configured for the port.
a. Check for the LOOP_ALM alarm of the system and handle the LOOP_ALM alarm.
b. Check for the ETH_EFM_LOOPBACK alarm of the system and handle the
ETH_EFM_LOOPBACK alarm.
4. Cause 4: Dynamically learning the entries in the ARP table fails.
a. Check whether the ARP table contains the mapping relationship between the opposite
IP address and the opposite MAC address. If the ARP table does not contain the
mapping relationship, it indicates that the entries in the ARP table fail to be
dynamically learned.
b. Configure the static ARP table.
5. Cause 5: The service configuration is incorrect.
a. See the Configuration Guide to re-configure the services.
Step 2 For symptom 2: The PWE3 Ethernet service loses packets or has errored packets.
1. Cause 1: The signals on the receive side are lost.
a. Check for the ETH_LOS alarm of the system and handle the ETH_LOS alarm.
b. Check for the LSR_NO_FITED, LSR_WILL_DIE, or LASER_MOD_ERR alarm of
the system and handle the LSR_NO_FITED, LSR_WILL_DIE, or
LASER_MOD_ERR alarm.
2. Cause 2: The configured traffic limit is excessively low at the port and configurations
of the source and sink ports are inconsistent.
OptiX OSN 8800/6800/3800
246
a. Check for the FLOW_OVER alarm of the system and handle the FLOW_OVER
alarm.
----End
Related Information
None
15.5 Tunnel APS Troubleshooting
This topic describes the symptom of common faults when the Tunnel APS function is enabled
and the solution to the relevant fault.
Symptom
When the network works normally, a condition that triggers the protection switching occurs on
the working tunnel. The services, however, fail to be automatically switched from the working
tunnel to the protection tunnel. Consequently, the services are interrupted. The symptoms are as
follows:
l The switching duration exceeds the specified value.
l The MPLS Tunnel APS protection group is configured incorrectly. Thus the protection
tunnel cannot receive the APS frame. In this case, the protection fails and the following
alarms may be reported.
ETH_APS_PATH_MISMATCH
ETH_APS_TYPE_MISMATCH
ETH_APS_LOST
ETH_APS_SWITCH_FAIL
l The protection tunnel is faulty and fails to provide protection. In this case, the following
alarms may be reported.
MPLS_TUNNEL_LOCV
MPLS_TUNNEL_UNEXPMEG
MPLS_TUNNEL_UNEXPMEP
MPLS_TUNNEL_SD
MPLS_TUNNEL_SF
MPLS_TUNNEL_AIS
MPLS_TUNNEL_RDI
TUNNEL_APS_DEGRADED
Possible Causes
l Cause 1: The fibers or cables on the protection tunnel are connected incorrectly.
l Cause 2: The OAM parameters of the working tunnel and protection tunnel are set
incorrectly.
OptiX OSN 8800/6800/3800
247
l Cause 3: The parameter values of the APS protection group at the two ends are different
from each other.
l Cause 4: The MPLS Tunnel APS protocol is disabled.
Flow Chart
Figure 15-1 shows the flow chart for rectifying a fault when the MPLS Tunnel APS function is
enabled.
Figure 15-1 Flow chart for rectifying a fault when the MPLS Tunnel APS function is enabled
No
Conact the technical support
engineers of Huawei.
End
Yes
See the Alarms and
Performance Events
Reference to clear the alarm.
Can the APS be
performed normally?
No
Yes
Are the fibers or cables
connected correctly?
Reconnect the fibers or
cables.
No
Can the APS be
performed normally?
Yes
Yes
No
Are the OAM parameters of the
working and protection
tunnels set correctly?
Yes
Start
Are the parameter values of the
APS the same at the two ends?
Set the parameters for the
APS at the two ends
correctly.
Yes
Can the APS be
performed normally?
Yes
No
No
Is the MPLS APS protocol
enabled?
Enable the MPLS APS
protocol.
Yes
Can the APS be
performed normally?
Yes
No
No
Set the working and
protection tunnels correctly.
Can the APS be
performed normally?
No
Yes
No
Does any alarm related to
the APS occur?

OptiX OSN 8800/6800/3800
248
Procedure
l Cause 1: The fibers or cables on the protection tunnel are connected incorrectly.
1. Reconnect the fibers or cables to each port and ensure that the fibers or cables are
connected correctly.
l Cause 2: The working tunnel and protection tunnel are set incorrectly.
1. In the Main Topology, right-click the NE that you want to configure and choose NE
Explorer from the shortcut menu.
2. Choose Configuration > Packet Configuration > MPLS Management > Unicast
Tunnel Management in the Function Tree.
3. Click the OAM Parameters tab, select the tunnel that realizes the MPLS Tunnel APS
function. Then, set Detection Packet Period (ms) to 3.3.
l Cause 3: The parameter values of the APS protection group at the two ends are different
from each other.
2. Choose Configuration > Packet Configuration > APS Protection Management in
the Function Tree.
3. Click Query to query whether the settings of the APS protection group are the same.
If the settings of the APS protection group are different from each other, set the
protection tunnel in the APS protection group to the same value as the working tunnel.
l Cause 4: The MPLS Tunnel APS protocol is disabled.
2. Choose Configuration > Packet Configuration > APS Protection Management in
the Function Tree.
3. Set Protocol Status to Enabled, and then click Apply.
4. In the Operation Result dialog box that is displayed, click Close.
l If the preceding operations are performed but the alarm related to the MPLS Tunnel APS
function persists, clear the alarm. If the fault persists, contact Huawei technical support
engineers for the solution.
----End
OptiX OSN 8800/6800/3800
249
16 Ethernet Problems
About This Chapter
This topic describes how to troubleshoot Ethernet problems.
16.1 Service Degradation
This topic describes how to handle Ethernet service degradation.
16.2 LCAS Startup Failure
Learning the common fault symptom and the fault handling flow helps you to locate and rectify
the common faults quickly.
16.3 LPT Switching Failure
This topic describes how to handle LPT switching failure.
16.4 LB Test Failure
If the LB test fails, troubleshoot the failure according to the troubleshooting flow.
16.5 Test Frames Unavailability
This topic describes the possible causes and handling methods when the test frames are
unavailable.
16.6 Common LAG faults
Following a certain troubleshooting flow facilitates your fault locating and rectification.
16.7 Common MSTP faults
Following a certain troubleshooting flow can facilitate fault locating and rectification.
16.8 Ethernet Service Cases
Case analysis related to Ethernet Service cases.
OptiX OSN 8800/6800/3800
Troubleshooting 16 Ethernet Problems
250
16.1 Service Degradation
This topic describes how to handle Ethernet service degradation.
Symptom
Services are degraded.
System Impact
Services are affected.
Possible Causes
l Cause 1: The bandwidth is insufficient for heavy traffic or the bandwidth is sufficient but
the burst traffic is excessive.
l Cause 2: There is a fault at the physical layer.
U2000
Figure 16-1 illustrates the Ethernet service degradation troubleshooting process.
OptiX OSN 8800/6800/3800
251
Figure 16-1 Ethernet service degradation troubleshooting flowchart
No
Yes
Yes
No
No
Yes Yes
No
Yes Yes
No No
Yes
Yes
No
No
Check for RMON
performance events of the
NE and handle them.
The bandwidth is insufficient for
heavy traffic or the bandwidth is
insufficient but the burst traffic is
excessive.
When the traffic is extremely
heavy, the opposite equipment
does not respond.
The setting of a port attribute of
the local equipment is different
from that of the opposite
equipment.
Enable the flow control
function for the equipment
at both ends.
Start
Is there a fault at the
physical layer?
Contact Huawei
engineers.
Check for alarms and
handle them.
Modify the
mismatched setting.
Are services
restored?
Are services
restored?
Are services
restored?
Are services
restored?
End

Procedure
l Cause 1: The bandwidth is insufficient for heavy traffic or the bandwidth is sufficient but
the burst traffic is excessive.
1. Check for RMON performance events of the corresponding NE and handle them. For
information about how to handle RMON performance events, refer to the Alarms and
l Cause 2: There is a fault at the physical layer.
1. Check for alarms. If an ETH_8B10B_ERR alarm is being reported, handle this alarm.
----End
16.2 LCAS Startup Failure
Learning the common fault symptom and the fault handling flow helps you to locate and rectify
the common faults quickly.
Fault Symptom
The common fault phenomena are as follows:
OptiX OSN 8800/6800/3800
252
l The source and sink ends fail to transmit control information. Hence, the negotiation
between the two ends is incorrect and the LCAS function fails to be enabled.
l If the bound path of the data board is configured before the SDH services from the data
board to the line board are configured, the LCAS function may fail to start immediately.
Possible Causes
The possible causes are as follows:
l The configuration timeslots of SDH services at the source and sink ends are not consistent.
l The timeslots actually bound to the data boards at the source and sink ends are abnormal
or lost.
l The LCAS function at the source and sink ends is not enabled.
l Excessive bit errors cause the failure of control information transmission between the
source and sink ends.
U2000
Flow for Handling Faults
If the LCAS function fails to successfully start, see Figure 16-2.
Figure 16-2 Flowchart for handling LCAS faults
No
Yes
No
Yes
Start
Yes
Yes
No
No
See the Alarms and
Performance Events
Reference handle the alarms
Yes
Yes
No
No
No
Contact Huawei
engineers for handling
End
No LCAS_FOPR or
LCAS_FOPT alarm is
reported
Reconfigure the timeslots of
SDH services at the
source and sink ends
No
Yes
No
The LCAS
function starts
successfully
Yes
The timeslots configured
at the source and sink
ends are correct and
consistent
The timeslots actually
bound to the data boards at
the source and sink ends
are normal or are not lost
The LCAS function is
enabled at the source and
sink ends
Reconfigure the timeslots
bound to the data boards at
the source and sink ends
The LCAS
function starts
successfully
The LCAS
function starts
successfully
The LCAS function
starts successfully
Enable the LCAS function
at the source and sink
ends
OptiX OSN 8800/6800/3800
253

Procedure
l Cause 1: The timeslots configured at the source and sink ends are not consistent.
1. Right-click the relevant NE icon in the Main Topology, and then choose NE
Explorer.
2. Choose Configuration > SDH Service Configuration from the Function Tree.
3. Select the SDH service that is configured between the source and sink ends in the pane
on the right side.
4. Click the Deactivate button in the lower right corner.
5. In the Confirm dialog box that is displayed, click OK.
6. Right-click the SDH service that is configured between the source and sink ends, and
then choose Modify.
7. In the Modify SDH Service dialog box that is displayed, verify that the service level
and timeslots configured for the source and sink ends are consistent.
l Cause 2: The timeslots actually bound to the data boards at the source and sink ends are
abnormal or lost.
Explorer.
2. Select the relevant data board in the Object Tree, and then choose Configuration >
Ethernet Interface Management > Ethernet Interface from the Function Tree in
the left pane.
3. Select Internal Port and click the Bound path tab.
4. Ensure that the activation status of the configured bound path in the bound path list is
"active".
5. Select the configured bound path, and then click the Configuration button in the lower
right corner in the pane on the right side.
6. In the Bound Path Configuration dialog box that is displayed, re-configure
Available Resources and Available Timeslots.
l Cause 3: The LCAS function is not enabled at the source and sink ends at the same time.
Explorer.
2. Select the relevant data board in the Object Tree, and then choose Configuration >
Ethernet Interface Management > Ethernet Interface from the Function Tree
3. Select Internal Port and click the LCAS tab.
4. Find the relevant port, double-click on the column Enabling LCAS of which is set to
Disabled, and finally set Enabling LCAS to Enabled.
5. Click the Apply button in the lower right corner.
6. In the Operation Result dialog box that is displayed, click Close.
l Cause 4: Excessive bit errors cause the failure of control information transmission between
the source and sink ends.
NOTE
You can check whether the control information transmission between the source and sink ends fails
due to excessive bit errors by querying the alarm information on the NMS.
OptiX OSN 8800/6800/3800
254
1. Right-click the relevant NE icon in the Main Topology, and then choose Browse
Current Alarms.
2. Check whether the VCAT_LOA alarm is contained in the alarm list.
3. See the Alarms and Performance Events Reference to troubleshoot the virtual
concatenation delay and excessive bit errors.
----End
16.3 LPT Switching Failure
This topic describes how to handle LPT switching failure.
Symptom
Services are interrupted.
Possible Causes
l Cause 1: The LPT function is disabled.
l Cause 2: The LPT bearer modes of all the NEs between the service access point and
intermediate network are inconsistent.
U2000
Procedure
Step 1 Cause 1: The LPT function is disabled.
1. In the NE Explorer, select the desired board and choose Configuration > Ethernet
Interface Management > LPT Management from the Function Tree.
2. Click Query and the Operation Result dialog box is displayed.
3. Check the LPT field of the board and ensure that the LPT function is enabled. Then click
Close.
Step 2 Cause 2: The LPT bearer modes of all the NEs between the service access point and intermediate
network are inconsistent.
1. In the NE Explorer, select the desired board and choose Configuration > Ethernet
Interface Management > LPT Management from the Function Tree.
2. Click Query and the Operation Result dialog box is displayed.
3. Check the Bearer Mode field of the board and ensure that the bearer modes of all nodes
are consistent. Then click Close.
----End
16.4 LB Test Failure
If the LB test fails, troubleshoot the failure according to the troubleshooting flow.
OptiX OSN 8800/6800/3800
255
Fault Symptom
Common fault phenomena are listed as follows.
l LB test failure
Possible Causes
Possible causes of the LB test failure are listed as follows.
l The external physical port where the maintenance point resides is not enabled.
l Values of Port Type of the ports where the sink and source maintenance points reside are
inconsistent.
l When values of Port Type of the ports where the sink and source maintenance points reside
are UNI or PE, the TAG flags are inconsistent.
l The VLAN ID of the maintenance points is inconsistent with the VLAN ID of the service.
l The level of the source maintenance point is inconsistent with the level of the sink
maintenance point.
l MEPs or MIPs of a higher level exist between the source and sink maintenance points.
l The Ethernet service is a unidirectional service.
l The Ethernet service is interrupted.
OptiX OSN 8800/6800/3800
256
Figure 16-3 Troubleshooting flow for the LB test failure
Yes
No
Start
Enable the external
physical port of the
MP
No
No
Is LB test
successful
Is LB test
successful
Yes
Yes
Yes
Refer to the
Troubleshooting for
the handling
Is LB test
successful
Yes
Ethernet service is
interrupted
End
No
No
Yes
Are TAG flags
consistent
No Yes
Is LB test
successful
Make the TAG flags
consistent
Yes
No
No
No
Yes
Is LB test
successful
Make the VLAN ID
consistent
No
No
No
Yes
Is LB test
successful
Make levels of the
source and sink MP
consistent
No
Yes
No
Yes
Is LB test
successful
Degrade the level of
the MEPs or MIPs
Yes
Is the Ethernet service
bidirectional
No
No
Yes
Is LB test
successful
Configure the service
as a bidirectional
Ethernet service
No
Contact Huawei
engineers
1
2
3
No
Port type of the port where the MP resides may be improperly configured
1
2 MP attributes may be improperly configured
3 The Ethernet service may be interrupted
Is
the external
physical port of the MP
enabled
of the source and sink MPs
Are the
types of the ports
consistent
sink MPs consistent
Make the types of the
ports of the source and
and or PE
Port type
of the ports of the
source sink MPs is UNI
Are the
VLAN IDs of the
MPs and the service
consistent
Are
levels of the source
and sink MP consistent
source and sink
Are
there MEPs or MIPs
of a higher level between the
MPs

Procedure
Step 1 Cause 1: The external physical port where the maintenance point resides is not enabled.
1. In the Main View, right-click the required NE icon and choose NE Explorer from the
shortcut menu.
2. In the Object Tree, select the required Ethernet service processing board. Choose
Configuration > Ethernet Interface Management > Ethernet Interface from the
Function Tree. Click .
OptiX OSN 8800/6800/3800
257
3. Select External Port.
4. Click the Basic Attributes tab. Check whether Enabled/Disabled of the port where the
maintenance point resides is Enabled.
Step 2 Cause 2: Values of Port Type of the ports where the sink and source maintenance points reside
are inconsistent.
1. Select External Port or Internal Port.
2. Click the Network Attributes tab. Check whether the values of Port Type of the ports are
consistent.
Step 3 Cause 3: When values of Port Type of the ports where the sink and source maintenance points
reside are UNI or PE, the TAG flags are inconsistent.
1. Click the TAG Attribute tab. Check whether the values of TAG of the ports are consistent.
NOTE
The TAG parameter is valid only when the value of Port Type is UNI or PE.
Step 4 Cause 4: The VLAN ID of the maintenance points is inconsistent with the VLAN ID of the
service.
Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function
Tree. Click .
2. Click Query to check whether the VLAN ID of the maintenance points is consistent with
the VLAN ID of the service.
Step 5 Cause 5: The level of the source maintenance point is inconsistent with the level of the sink
maintenance point.
1. Click Query to check whether the level of the source maintenance point is inconsistent
with the level of the sink maintenance point.
Step 6 Cause 6: MEPs or MIPs of a higher level exist between the source and sink maintenance points.
1. Click Query to check whether any MEP or MIP of a higher level exists between the source
and sink maintenance points.
Step 7 Cause 7: The Ethernet service is a unidirectional service.
Configuration > Ethernet Service from the Function Tree.
2. Select Ethernet Line Service or Ethernet LAN Service. Then, click .
3. Click Query to check whether the Ethernet service is a unidirectional service.
NOTE
The LB test is based on bidirectional Ethernet services.
Step 8 Cause 8: The Ethernet service is interrupted.
1. Check and handle the Ethernet service fault according to the Troubleshooting.
----End
OptiX OSN 8800/6800/3800
258
16.5 Test Frames Unavailability
This topic describes the possible causes and handling methods when the test frames are
unavailable.
Symptom
The test frame cannot function normally.
System Impact
None.
Possible Cause
l Cause 1: The timeslots in the cross-connection services of the interconnected ends are
inconsistent.
l Cause 2: The bearing modes of the VC trunk ports at the two interconnected ends are
inconsistent.
l Cause 3: The logic port on which the function of test frame is enabled is not bound with
timeslots.
U2000
Procedure
l Cause 1: The timeslots in the cross-connection services of the interconnected ends are
inconsistent.
1. Check whether the timeslots in the cross-connection services of the interconnected
ends are consistent. If they are inconsistent, set them to the same.
l Cause 2: The bearing modes of the VC trunk ports at the two interconnected ends are
inconsistent.
1. Check whether the bearing modes of the VC trunk ports at the two interconnected
ends are consistent. If they are inconsistent, set them to the same.
l Cause 3: The logic port on which the function of test frame is enabled is not bound with
timeslots.
1. Check whether the logic port on which the function of test frame is enabled is bound
with timeslots.
----End
16.6 Common LAG faults
OptiX OSN 8800/6800/3800
259
Symptom
The common LAG faults are as follows:
l The member ports become unavailable, because the LAG is faulty. As a result, the services
are interrupted.
l Certain packets are discarded, because the member ports in the LAG become unavailable.
Possible Causes
l The NEs at both ends of the LAG are configured incorrectly.
l The member ports in the LAG work in half-duplex mode.
l Loopbacks are performed on the member ports in the LAG.
l The member ports in the LAG are disconnected.
Flow Chart
NOTE
This topic describes the process for rectifying a LAG fault when the LAG function is enabled in TDM
mode. This topic also provides a reference for you to rectify a LAG fault because the process for rectifying
a LAG fault when the LAG function is enabled in packet mode is similar.
OptiX OSN 8800/6800/3800
260
Figure 16-4 Flow chart for rectifying a LAG fault
The
LAG_FAIL
alarm occurs?
End
Start
Handle the
alarm
The
configurations of
both NEs at both
ends are
incorrect?
The port works
in half-duplex
mode?
Modify the
configurations of
both NEs
Modify the working
mode of the port to
full-duplex
Release the
loopback at the port
Rectify the connection
fault at the port to
clear the alarm
The fault is
rectified?
Contact Huawei
technical support
engineers to handle the
fault
The
LOOP_ALM or
ETH_EFM_LOOPBACK
alarm occurs?
The ETH_LOS or
ETH_LINK_DOWN
alarm occurs?
Yes
Yes
Yes
Yes
Yes
Yes
No
No
No
No
No

OptiX OSN 8800/6800/3800
261
Procedure
Step 1 Cause 1: The NEs at both ends of the LAG are configured incorrectly.
1. On the U2000, check whether the LAG_DOWN or LAG_MEMBER_DOWN alarm is
reported.
2. If yes, see the Alarms and Performance Events Reference to clear the alarm. Then, check
whether the fault is rectified.
Step 2 Cause 2: The member ports in the LAG work in half-duplex mode.
1. Check whether the member ports in the LAG work in half-duplex mode.
2. If yes, change the working mode to full-duplex and ensure that the ports on the local and
opposite NEs work in the same mode.
Step 3 Cause 3: Loopbacks are performed on the member ports in the LAG.
1. Check whether the LOOP_ALM or ETH_EFM_LOOPBACK alarm is reported on the
member ports in the LAG.
2. If yes, release the loopback status to clear the LOOP_ALM or ETH_EFM_LOOPBACK
alarm.
Step 4 Cause 4: The member ports in the LAG are disconnected.
1. Check whether the ETH_LOS or ETH_LINK_DOWN alarm is reported on the member
ports in the LAG.
2. If yes, clear the alarm. Then, check whether the fault is rectified.
Step 5 If the fault persists, contact the technical support engineers of Huawei.
----End
16.7 Common MSTP faults
Following a certain troubleshooting flow can facilitate fault locating and rectification.
Context
Figure 16-5 shows the flow for rectifying a fault that occurs when the MSTP function is used.
OptiX OSN 8800/6800/3800
262
Figure 16-5 Troubleshooting flowchart
Start
End
Check the information in the
MAC address tables of all the
equipment on the network
Check the parameter
configurations of the bridge
Check the parameter
configurations of the
Ethernet port
Check the configurations of
the MSTP function for the
other equipment
Check the VLAN
configuration of the network

Procedure
Step 1 Check the information in the MAC address tables of all the equipment on the network.
1. Check the information in the MAC address tables of all the equipment on the network. If
a MAC address corresponds to several ports, loops may exist. In this case, cancel any
loopbacks.
Step 2 Check the parameter configurations of the bridge.
If a fault occurs when the MSTP function is used, check whether the parameter configurations
of the MSTP bridge are incorrect. If this is the case, modify the parameter configurations to
rectify the fault.
1. Check whether the MSTP function is disabled. If this is the case, enable it.
2. Check whether the equipment works in MSTP mode or STP mode.
The OptiX OSN equipment supports the MSTP protocol, which is compatible with the STP
and RSTP protocols.
3. Check whether the priorities are correctly set for the equipment.
Modify the priorities of the bridges so that one bridge is selected as the root bridge. If the
priorities of the bridges are set incorrectly, the root bridge is incorrectly selected.
OptiX OSN 8800/6800/3800
263
4. Check whether the values of the Hello Time, Forward Delay, and Max Age parameters
are set correctly.
l If the Hello Time parameter is set to an extremely large value, the change in network
topology may be responded in a delayed manner. If the Hello Time parameter is set to
an extremely small value, the configuration message is frequently transmitted, and thus
more CPU and network resources are consumed.
l If the Forward Delay parameter is set to an extremely large value, the spanning tree
converges slowly. If the Forward Delay parameter is set to an extremely small value,
temporary loops may exist when the network topology changes.
l If the Max Age parameter is set to an extremely large value, the fault on the link fails
to be detected. If the Max Age parameter is set to an extremely small value, the switch
incorrectly considers that a fault occurs on the link in the case of network congestion,
and thus the spanning tree is frequently computed.
NOTE
It is recommended that the three parameters take the default values.
Step 3 Check the parameter configurations of the Ethernet port.
If a fault occurs when the MSTP function is used, check whether the parameter configurations
of the Ethernet port are incorrect. If this is the case, modify the parameter configurations to
rectify the fault.
1. Check whether the MSTP function is enabled for the Ethernet port.
2. Check whether the setting of the point-to-point link status for the Ethernet port is consistent
with the actual point-to-point link status.
If the Ethernet port is set as a point-to-point link port whereas the actual situation is
inconsistent, temporary loops may exist when the network topology changes.
Step 4 Check the configurations of the MSTP function for the other equipment.
If a fault occurs when the MSTP function is used, check the configurations of the MSTP function
for the other equipment on the network. The MSTP protocol should be enabled for all the
equipment on the network (at least on one ring). Otherwise, the equipment on the network fails
to be informed of the network topology by exchanging the messages, and thus the learning of
the spanning tree fails.
1. Check whether the root bridge of the entire network is correctly selected.
In general cases, you can set the intermediate LanSwitch as the root bridge by modifying
the priorities of bridges. If the intermediate LanSwitch is not set as the root bridge, the
traffic on the entire network is not balanced. In addition, certain services become
unavailable.
2. Check whether the bridge parameters and port parameters of all the equipment are set
correctly. In general cases, the Hello Time, Forward Delay, and Max Age parameters
take the parameters values of the root bridge.
Step 5 Check the VLAN configuration of the network.
If a fault occurs when the MSTP function is used, check whether the VLAN configuration of
the network is correct. Mainly check whether the service is unavailable due to the blocking of
the Ethernet port.
----End
OptiX OSN 8800/6800/3800
264
16.8 Ethernet Service Cases
Case analysis related to Ethernet Service cases.
NOTE
Related Cases:
LINK_STATUS alarm.
Alarms Transiently
l MC-A17 The LQG Reports ALM_DATA_RLOS and ALM_DATA_TLOS Alarms
l MC-A30 LDG Board of Metro 6100 Equipment Reports the INBADOCTS_OVER Alarm
l MC-A96 Packet Loss Occurs in Ethernet Service Testing of the L4G Board
l MC-A158 How to Use the Ethernet Test Frames on the OptiX OSN 6800
l MC-A219 EPL Service Is Interrupted Due to Mismatched Service Modes of the L4G
Boards, Sites Report The R_LOF, ODU5G_PM_AIS, OTU5G_LOF And LINK_ERR
Alarms
OptiX OSN 8800/6800/3800
265
17 ECC Problems
About This Chapter
In a WDM system, communication between the U2000 and non-gateway NEs is established
with the U2000 first communicating with the gateway NE over TCP/IP. Then the gateway NE
communicates with non-gateway NEs through the embedded control channel (ECC) to complete
the communication channel.
17.1 ECC Communication Interruption
This topic describes how to handle ECC interruption.
17.2 Intermittent ECC Communication
This topic describes how to handle intermittent ECC communication.
17.3 HWECC FAQ
This topic provides answers to frequently asked questions about the HWECC solution.
17.4 Troubleshooting for Inband DCN
A troubleshooting flow facilitates fault locating and rectification.
17.5 ECC Cases
Case analysis related to ECC cases.
OptiX OSN 8800/6800/3800
Troubleshooting 17 ECC Problems
266
17.1 ECC Communication Interruption
This topic describes how to handle ECC interruption.
Symptom
The services on the main optical path are normal, but ECC communication is interrupted and
the NE cannot be reached by the U2000.
System Impact
Possible Causes
l Cause 1: The ID of the NE is a duplicate of another NE.
l Cause 2: The pigtail connected to the OSC board is faulty.
l Cause 3: The system control board is faulty.
l Cause 4: The OSC board is faulty.
l Cause 5: The OTU or tributary or line board is faulty.
WEB LCT, optical power meter
Procedure
l Cause 1: The ID of the NE is a duplicate of another NE.
1. Log in to the NE on the WEB LCT and modify the NE ID of the NE according to the
record.
l Cause 2: The pigtail connected to the OSC board is faulty.
1. Check the pigtail connected to the OSC board on the first faulty NE along the signal
flow. If the pigtail is loose, secure it; if it is dirty, clean it; if it is faulty, replace it.
2. Ensure that the pigtail is properly connected to the OSC board on the faulty NE.
NOTE
During deployment commissioning, the pigtail might be incorrectly connected because the FIU
board and the OSC board have many ports marked with similar names. During commissioning,
to prevent incorrect pigtail connections in one direction of the OSC board, you can connect an
optical attenuator between the currently unused RM and TM optical ports in the other direction
of the OSC board to form a self-loop.
l Cause 3: The system control board is faulty.
1. Reset the system control board on the faulty NE along the signal flow, and then check
whether you can log in to the NE.
2. If you cannot log in to the NE, remove the system control board on the faulty NE so
the ECC signals pass through the backplane. Then check whether the downstream NE
OptiX OSN 8800/6800/3800
267
is restored. If the downstream NE is restored, the system control board is faulty.
Replace the system control board.
l Cause 4: The OSC board is faulty.
1. Replace the OSC board on the first faulty NE along the signal flow, and check whether
the network is restored. If the network is restored, the OSC board is faulty. Replace
the OSC board.
l Cause 5: The OTU or tributary or line board is faulty.
1. Replace the OTU, or tributary or line board on the first faulty NE along the signal
flow, and check whether the network is restored. If the network is restored, the OTU,
or tributary or line board is faulty. Replace the OTU, or tributary or line board.
1. The DCN bytes are defined differently for coherent and non-coherent services, so the
----End
17.2 Intermittent ECC Communication
This topic describes how to handle intermittent ECC communication.
Symptom
The ECC communication is intermittent, and the U2000 is frequently unable to reach the NE.
System Impact
Possible Causes
l Cause 1: Clock tracing is set incorrectly.
l Cause 2: There are bit errors on the signal transmission.
WEB LCT
Procedure
l Cause 1: Clock tracing is set incorrectly.
1. Set clock tracing to the correct source. For details on how to set the correct clock
tracing, see "Synchronization".
OptiX OSN 8800/6800/3800
268
NOTE
All equipment on the network must trace the same clock source. In the case of WDM equipment,
the internal clock source of a specific NE should be given the highest priority, and the other
NEs trace the internal clock source of this NE. (In the case of chain networking, the internal
clock source of a terminal NE rather than an intermediate NE should be set as the clock source
so it can be traced network-wide.)
l Cause 2: There are bit errors on the signal transmission.
1. Refer to rectifying bit errors.
----End
17.3 HWECC FAQ
This topic provides answers to frequently asked questions about the HWECC solution.
Q: Why does the U2000 always fail to log in to an NE?
A: Common causes include:
l Communication between the U2000 and the GNE is faulty.
To locate the fault, run the ping or tracert command on the U2000 server.
l The ECC route between the GNE and a non-GNE is faulty.
To locate the fault, check the ECC route between the GNE and the non-GNE.
l NE IDs conflict.
Q: Why does the U2000 frequently fail to log in to NEs?
l The U2000 is faulty.
In this case, the U2000 fails to log in to all NEs.
l The IP addresses of GNEs conflict.
In this case, the U2000 fails to log in to all NEs on a DCN subnet.
l The scale of a DCN subnet is excessively large.
In this case, the U2000 fails to log in to NEs that access multiple data communications
channels (DCCs).
Q: Why does the system control board board on the GNE or the NE that uses the extended
ECC frequently reset?
l Unknown equipment is connected to the LAN to which the NE is connected, resulting in
a conflict between the NE and the equipment.
l A loop (especially between the Ethernet NM port and NE cascading port) occurs in the
LAN to which the NE is connected, resulting in a network storm.
Q: What are the hazards of a DCN subnet of excessively large scale?
A: Main hazards include:
l The stability of the ECC route is poor, the convergence time is long, and ECC route flapping
can occur.
OptiX OSN 8800/6800/3800
269
l Remote loading occurs slowly.
l Alarms reported to the U2000 are lost.
l The U2000 cannot log in to certain NEs.
l The system control boards of certain NEs reset unexpectedly.
Q: Why are NEs prone to be unreachable by the U2000 due to bit errors during deployment
and expansion?
A:
If the OSC and ESC functions are used together, bit errors are often generated during deployment
and expansion because services transmitted along with ESC information are being
commissioned. Once bit errors are generated, the network frequently switches between the OSC
and ESC channels, and consequently NEs on the network become unreachable by the U2000,
leading to NE configuration and management failures. To prevent this problem, disable the ESC
function during deployment and expansion, and enable it again when deployment and expansion
are complete.
17.4 Troubleshooting for Inband DCN
Symptom
The common faults regarding the inband DCN are as follows:
l The communication between the U2000 and NEs is interrupted, and the NE icons on the
U2000 become unavailable.
l No response is returned after a command is issued on the U2000. If no response is returned
more than 2 minutes later, the communication between the U2000 and an NE is interrupted.
l Part of the query result on the U2000 is missing.
Impact on System
l After the communication between an NE and the U2000 is interrupted, the NEs that
communicate with the U2000 through the NE also become unreachable, if they cannot
connect to the U2000 by other methods. The other NEs, however, are not affected.
Possible Causes
l Cause 1: The physical link between the faulty NE and the U2000 is disconnected.
l Cause 2: The ports on the faulty NE are not enabled with the inband DCN function.
l Cause 3: The DCN VLAN IDs of the NEs at both ends are not the same.
l Cause 4: The ports connecting the local and opposite NEs use different protocols.
l Cause 5: The faulty NE fails to obtain DCN packets due to loss of received signals or very
low receive optical power.
l Cause 6: A board is faulty.
l Cause 7: No response is returned for inband DCN packets, because the SCC board on the
faulty NE is being reset or active/standby protection switching occurs on another board.
OptiX OSN 8800/6800/3800
270
l Cause 8: The bandwidth of the inband DCN channel is very low or other services preempt
the bandwidth for the inband DCN channel.
NOTE
When handling a fault regarding the inband DCN, do as follows:
l If communication between NEs and the U2000 is interrupted, rectify the fault on the gateway NE
prior to the fault on the non-gateway NE.
l If the communication between NEs and the U2000 is normal, rectify the fault on the non-gateway
NE prior to the fault on the gateway NE. This method ensures that the unaffected NEs can keep
communicating with the U2000 during the troubleshooting process.
U2000
OptiX OSN 8800/6800/3800
271
Figure 17-1 Flow chart for handling an inband DCN fault
Contact Huawei technical
support engineers.
No
Yes
Enable the port
on the DCN.
Reconnect the
Ethernet cable or
fiber.
Yes
Replace the board.
Clear the alarm
related to the optical
power, fiber, or cable.
Yes
Yes
Yes
Wait until the SCC
board is reset.
Increase the bandwidth of the
DCN path or degrade the
priority of other services.
The bandwidth
of the DCN path
is very low.
The SCC board is
being reset.
Yes
Yes
Start
No
No response is
returned for the
command on the
U2000.
Is the information
queried on the
U2000 lost?
No
Is the physical link
disconnected?
Is the received
signal lost?
No
No
Is the board
faulty?
No
The communication
between the U2000 and
the NE is interrupted.
Yes
Is the fault
rectified?
End
Check whether the
NE icon is dimmed.
Is the port on the
DCN disabled?

Procedure
Step 1 Cause 1: The physical link between the faulty NE and the U2000 is disconnected.
1. Check whether the Ethernet cable or fiber of the faulty NE is disconnected from the port.
If yes, reconnect it.
Step 2 Cause 2: The ports on the faulty NE are not enabled with the inband DCN function.
1. Check whether the DCN function is enabled by default for the port that is connected to the
fiber. If not, connect the fiber to a port with the DCN function enabled by default.
OptiX OSN 8800/6800/3800
272
2. Check whether the inband DCN function is enabled for the ports at both ends of the link.
If not, enable DCN access function for the ports.
Step 3 Cause 3: The DCN VLAN IDs of the NEs at both ends are not the same.
1. Check whether the DCN VLAN ID of the local NE is the same as that of the opposite NE.
If not, change the DCN VLAN ID of the local NE to the DCN VLAN ID of the opposite
NE.
Step 4 Cause 4: The ports connecting the local and opposite NEs use different protocols.
1. Check whether the port on the local NE uses the same protocol as the port on the opposite
NE. If not, change the protocol to ensure that the ports connecting the local and opposite
NEs use the same protocol.
Step 5 Cause 5: The faulty NE fails to obtain DCN packets due to loss of received signals or very low
receive optical power.
1. Check whether alarms, such as ETH_LOS, ETH_LINK_DOWN, or IN_PWR_LOW, are
reported on the board that is configured with the inband DCN channel. If yes, see the Alarms
and Performance Events Reference to clear these alarms.
Step 6 Cause 6: A board is faulty.
1. Check whether the HARD_BAD alarm is reported on the board that is configured with the
inband DCN channel. If yes, see the Alarms and Performance Events Reference to clear
the alarm.
Step 7 Cause 7: No response is returned for inband DCN packets, because the SCC board on the faulty
NE is being reset or active/standby protection switching occurs on another board.
1. Check whether the PROG indicator on the system control and communication (SCC) board
is blinking green. If yes, the SCC board is being reset. When the PROG indicator is steady
green, the reset of the SCC board is completed. Then, the NE is automatically reconnected
to the DCN.
2. If no response is returned for DCN packets, check whether active/standby protection
switching occurs on another board, which results in rerouting of DCN packets.
3. If active/standby protection switching occurs on a board, the NE automatically responds
to DCN packets after rerouting of DCN packets is completed.
Step 8 Cause 8: The bandwidth of the inband DCN channel is very low or other services preempt the
bandwidth for the inband DCN channel.
1. If the number of services that are configured for the port exceeds the specified value, part
of the query result may be missing. To resolve the problem, increase the bandwidth of the
inband DCN channel properly. For details, see Setting the VLAN ID and Bandwidth Used
by the Inband DCN.
Step 9 If the fault persists, contact Huawei to handle the fault.
----End
17.5 ECC Cases
Case analysis related to ECC cases.
NOTE
OptiX OSN 8800/6800/3800
273
Related Cases:
l MC-A22 NE ESC Communication Interrupted Because of the Closure of the OTU Laser
l MC-A64 Many BD_STATUS Alarms Occur Due to the ECC Storm
l MC-A81 The Created ALC Link on OptiX OSN 6800 Cannot Be Automatically Adjusted
l MC-A110 Question About the Extended ECC of WDM NEs
l MC-A113 Communication Between the WDM Equipment And the DCN Network Fails
After a Hub Is Connected To the DCN Network
l MC-A135 The Communication Between the NE and the T2000 Stops Because the NE
Software Cannot Switch the ECC from an OSC Board to an OTU Board Automatically
l MC-A181 An NE Is Frequently Unreachable to the NMS Due to Insufficient Processing
Capacity of a Router
l MC-A247 NE Configuration Data Cannot Be Uploaded
OptiX OSN 8800/6800/3800
274
18 Clock Problems
About This Chapter
This section describes the possible causes of the synchronization failure in the clock, and the
troubleshooting procedure.
18.1 Failure of NodeBs to Trace Clock Signals
When a fiber on the path for transmitting IEEE 1588v2 clock signals is faulty, compensate for
the delay after rectifying the fault. Otherwise, the downstream NodeBs cannot trace the clock
signals.
18.2 Synchronization Failure of the Physical-Layer Clock
This section describes the possible causes of the synchronization failure in the physical-layer
clock, and the troubleshooting procedure.
OptiX OSN 8800/6800/3800
Troubleshooting 18 Clock Problems
275
18.1 Failure of NodeBs to Trace Clock Signals
When a fiber on the path for transmitting IEEE 1588v2 clock signals is faulty, compensate for
the delay after rectifying the fault. Otherwise, the downstream NodeBs cannot trace the clock
signals.
Symptom
After a fiber fault is rectified, the delay is not compensated. As a result, the downstream NodeBs
cannot trace the clock signals.
Impact on System
If protection is configured, the IEEE 1588v2 clock signals are switched from the working path
to the protection path. If no protection is configured, the IEEE 1588v2 clock signals are
interrupted and the downstream NodeBs cannot perform clock synchronization.
U2000 and time testing meter
Fault Handling on a Ring Network Configured with Protection
As shown in the following figure, the fiber between NE2 and NE3 on the working path is faulty.
IEEE 1588v2 clock signals are switched to protection path NE1NE4NE3.
Figure 18-1 Networking diagram of the ring network configured with protection
NE2 NE1
NE3
NodeB
Convergence
layer
NE4
BITS NodeB OptiX OSN equipment
BITS
OptiX PTN
equipment
: IEEE 1588v2 working path
: IEEE 1588v2 protection path
East
West
West
East
East
East
West
West
NE5
Compensate for the delay on the faulty fiber as follows:
OptiX OSN 8800/6800/3800
276
1. Delete the west IEEE 1588v2 port on NE3 so that the clock signals will not be immediately
switched to the working path after the fiber between NE2 and NE3 is repaired.
2. Repair the faulty fiber between NE2 and NE3.
3. Check whether the time precision on NE3 and that on NE4 satisfy requirements. For the
time precision requirements, see Requirements on Clock Synchronization. If the time
precision requirements are not satisfied, the path between NE3 and NE4 is faulty. When
this occurs, remove the fault on the path.
4. Create the west IEEE 1588v2 port that is deleted in step 1 to switch the IEEE 1588v2 clock
signals to working path NE1NE2NE3.
5. Record the time precision on NE2 and that on NE3. Then calibrate the original compensated
delay on NE2 and that on NE3 according to the time precision on NE2 and the time precision
on NE3. For the delay compensation method, see Testing Delay Compensation.
6. Ensure that the time precision on NE2 and that on NE3 satisfy requirements.
7. Verify that the status of all PTP clock ports is normal.
Fault Handling on a Chain Network Configured with Protection
On a chain network configured with protection, IEEE 1588v2 clock signals are switched to the
protection path after a fiber on the working path is faulty. Use the same method as that used on
a ring network configured with protection to compensate for the delay on the faulty fiber.
Fault Handling on a Network Not Configured with Protection
On a network not configured with protection, the downstream NodeBs cannot perform clock
synchronization after a fiber on the working path is faulty. After the faulty fiber is repaired,
compensate for the delay on the faulty fiber by performing 5 to 7 described in the scenario of a
ring network configured with protection.
18.2 Synchronization Failure of the Physical-Layer Clock
This section describes the possible causes of the synchronization failure in the physical-layer
clock, and the troubleshooting procedure.
Symptom
In the case of a clock processing failure, the EXT_TIME_LOC, SYNC_C_LOS,
S1_SYN_CHANGE, LTI, SYN_BAD, EXT_SYNC_LOS, or CLK_NO_TRACE_MODE
alarm occurs.
When you clear the alarm reported by the equipment, the fault is rectified.
Impact on System
When the clock source of the network is lost or degrades, the services that trace the clock source
are affected. In this case, pointer justification occurs and BER increases.
Possible Causes
l Cause 1: In the priority table, the synchronous time source for the service board is lost.
OptiX OSN 8800/6800/3800
277
l Cause 2: The synchronous clock source is lost and the clock of the NE is in an abnormal
state.
l Cause 3: In SSM mode, the clock source is switched and the clock source traced by the NE
is also switched.
l Cause 4: The signals of the synchronous clock source are degraded.
l Cause 5: The external clock source is lost.
l Cause 6: The clock enters the non-tracing working mode.
U2000
Procedure
l Cause 1: In the priority table, the synchronous time source for the service board is lost.
1. Check for the SYNC_C_LOS alarm of the STG board on U2000. For details, refer to
"Querying the Current Alarms and Performance Events of a Component on the
U2000" in Supporting Tasks.
2. If the SYNC_C_LOS alarm occurs, handle the alarm according to the Alarms and
l Cause 2: The synchronous clock source is lost and the clock of the NE is in an abnormal
state.
1. Check for the LTI alarm of the STG board on U2000. For details, refer to "Querying
the Current Alarms and Performance Events of a Component on the U2000" in
Supporting Tasks.
2. If the LTI alarm occurs, handle the alarm according to the Alarms and Performance
Events Reference.
l Cause 3: In SSM mode, the clock source is switched and the clock source traced by the NE
is also switched.
1. Check for the S1_SYN_CHANGE alarm of the STG board on U2000. For details,
refer to "Querying the Current Alarms and Performance Events of a Component on
the U2000" in Supporting Tasks.
2. If the S1_SYN_CHANGE alarm occurs, handle the alarm according to the Alarms
l Cause 4: The signals of the synchronous clock source are degraded.
1. Check for the SYN_BAD alarm of the STG board on U2000. For details, refer to
"Querying the Current Alarms and Performance Events of a Component on the
2. If the SYN_BAD alarm occurs, handle the alarm according to the Alarms and
l Cause 5: The external clock source is lost.
1. Check for the EXT_SYNC_LOS alarm of the STG board on U2000. For details, refer
to "Querying the Current Alarms and Performance Events of a Component on the
2. If the EXT_SYNC_LOS alarm occurs, handle the alarm according to the Alarms and
OptiX OSN 8800/6800/3800
278
l Cause 6: The clock enters the non-tracing working mode.
1. Check for the CLK_NO_TRACE_MODE alarm of the STG board on U2000. For
details, refer to "Querying the Current Alarms and Performance Events of a
Component on the U2000" in Supporting Tasks.
2. If the CLK_NO_TRACE_MODE alarm occurs, handle the alarm according to the
----End
OptiX OSN 8800/6800/3800
279
19 Orderwire Problems
About This Chapter
This topic describes how to handle orderwire problems.
19.1 Orderwire Failure
This topic describes the possible causes and troubleshooting methods for orderwire failures that
occur when the services on the main optical path are working normally.
19.2 A Called Phone Set Cannot Exit the Conference Call State
This topic describes the possible cause and troubleshooting method when a called phone set in
a conference call fails to exit the conference call state.
19.3 Orderwire Cases
Case analysis related to Orderwire cases.
OptiX OSN 8800/6800/3800
Troubleshooting 19 Orderwire Problems
280
19.1 Orderwire Failure
This topic describes the possible causes and troubleshooting methods for orderwire failures that
occur when the services on the main optical path are working normally.
Symptom
The services on the main optical path from station A to station C are normal, but the orderwire
is unavailable.
Figure 19-1 Network configuration in the case of an orderwire failure
Station A Station C Station B
OTM
OLA
OTM

System Impact
The services are not affected.
Possible Causes
l Cause 1: The parameters are incorrectly configured.
l Cause 2: The setting of the phone set is incorrect.
l Cause 3: The phone set or phone line is faulty.
l Cause 4: The fiber connection of the SC2 board at station B is incorrect.
l Cause 5: The system control board at station B is faulty.
U2000
Procedure
l Cause 1: The parameters are incorrectly configured.
1. On the U2000, check the phone numbers of stations A and C. Ensure that each phone
number is correctly set to a unique value. For details, refer to "Configuring Orderwire".
OptiX OSN 8800/6800/3800
281
2. On the U2000, check the setting of the OSC boards at stations A, B, and C. Set
orderwire bytes to pass through each station; otherwise, the orderwire of station A and
that of station C are unavailable.
3. On the U2000, check the clock tracing settings of stations A and C. For details on how
to set the correct clock tracing, see "Setting the Priority List of Clock Sources" or
"Setting IEEE 1588v2" in the Configuration Guide.
l Cause 2: The setting of the phone set is incorrect.
1. Check the port to which the phone set is connected and ensure that the interface is
correctly selected.
NOTE
Generally, the orderwire phone line is inserted on the "PHONE1" port of the subrack.
2. Check whether the ringing current switch RING on the phone set is set to ON
(indicating that the phone rings when there is an incoming call).
3. Check whether the dialing mode switch is set to T (indicating the dual-tone
multifrequency (DTMF) dialing mode).
4. Check whether the called orderwire phone is on hook. If the red indicator in the upper
right corner on the front panel of the phone set is unlit, the phone set is on hook. If the
red indicator is lit, the phone set is not on hook. Press the "TALK" button on the front
panel of the phone set to hook it up.
l Cause 3: The phone set or phone line is faulty.
1. Install a normal phone set at stations A and C and test the calling function of the phone
set. If the function is available, the original phone set is faulty.
2. Replace the phone line between the phone set and the equipment at stations A and C,
and test the calling function. If the function is available, the phone line is faulty.
l Cause 4: The fiber connection of the SC2 board at station B is incorrect.
1. Along the signal flow, check the pigtail connected to the SC2 board at station B. Ensure
that the connection is correct.
l Cause 5: The system control board at station B is faulty.
1. Remove the system control board at station B to make orderwire bytes pass through
station B. If the orderwire becomes available, the system control board is faulty.
Replace the system control board.
----End
19.2 A Called Phone Set Cannot Exit the Conference Call
State
This topic describes the possible cause and troubleshooting method when a called phone set in
a conference call fails to exit the conference call state.
Symptom
A called phone set in a conference call fails to exit the conference call state. That is, the called
phone set is still in the conference call state after being connected and then disconnected.
OptiX OSN 8800/6800/3800
282
System Impact
The called phone set fails to exit the conference call state, and the orderwire is unavailable.
Possible Causes
l Cause 1: During the conference call, the calling orderwire board of a certain phone set is
reset either due to an external cause or because the phone set was connected when
communication on the supervisory channel failed.
None
Procedure
l Cause 1: During the conference call, the calling orderwire board of a certain phone set is
reset either due to an external cause or because the phone set was connected when
communication on the supervisory channel failed.
1. Leave the phone set in the connected state for two hours. The phone set will return to
the idle state two hours later.
2. Use an idle phone set to initiate a conference call. Then, connect this phone set, causing
all phone sets in orderwire communication with this phone set to exit the conference
call state.
----End
19.3 Orderwire Cases
Case analysis related to Orderwire cases.
NOTE
Related Cases:
l MC-A42 A Fault of the PMU for the OptiX BWS 1600G Results In an Orderwire Ringing
Failure
l MC-A163 How To Quickly Re-obtain the IP Address Of a Device At a Station After the
IP Address Of the Device Is Changed
l MC-A187 How to Change the IP Address of the OptiX OSN 1800 to the Default One
l MC-A223 When a Self-Made Network Cable Is Used, the OptiX OSN 6800 Reports the
COMMUN_FAIL Alarm
l MC-A224 The Network Cable at the COM Port on the EFI Board of the OptiX OSN 6800
Subrack Is Incorrectly Connected. Consequently, All the Boards on the OptiX OSN 6800
Subrack Report the COMMUN_FAIL Alarms
OptiX OSN 8800/6800/3800
283
20 Coherent Board Faults
This section describes how to troubleshoot coherent board faults in terms of the symptoms,
impact on the system, possible causes, tools required for troubleshooting, troubleshooting
procedure, and precautions that should be taken during the troubleshooting.
Symptoms
l Symptom 1: The pre-FEC BER is high, services are unavailable, or the wavelength of the
received service is incorrect.
l Symptom 2: DCN communication is interrupted and some NEs are unreachable by the
NMS.
On the NEs unreachable by the NMS, bit errors are generated in the services, or the services are
interrupted.
Possible Causes
l For symptom 1:
Cause 1: The receive wavelength is incorrectly configured.
Cause 2: The FEC type of the board is incorrectly set.
l For symptom 2:
Cause 1: Coherent and non-coherent boards are interconnected.
l U2000
Procedure
Step 1 For symptom 1:
1. Cause 1: The receive wavelength is incorrectly configured.
a. Check whether the receive wavelength has been configured for the coherent board. If
not, the system automatically associates the receive and transmit wavelengths when
OptiX OSN 8800/6800/3800
Troubleshooting 20 Coherent Board Faults
284
receiving coherent wavelengths. In other words, the local transmit wavelength is
consistent with the remote transmit wavelength expected to be received.
b. If the receive wavelength has been configured for the board, the configured
wavelength takes effect and there is no automatic association between the receive and
transmit wavelengths. Check whether the receive wavelengths configured for
interconnected boards are consistent with the planned ones.
c. In the following scenario, the user must set the receive wavelength for the coherent
board. In the figures, there are four nodes: A, B1, B2, and C. Nodes B1 and B2 use
the TN11LTX board in relay mode, wavelength 1 is used between node A and nodes
B1/B2, and wavelength 2 is used between node C and nodes B1/B2. Normally, the
receive wavelength and transmit wavelength of node B1 are 1 and 2 respectively, and
those of node B2 are 2 and 1 respectively. If no receive wavelength is configured for
the 11LTX boards of nodes B1 and B2, the receive and transmit wavelengths of nodes
B1 and B2 will be consistent at each node.
1
A
B1
11LTX
2
B2
11LTX
C
2 1
2. Cause 2: The FEC type of the board is incorrectly set.
a. On the U2000, check whether the board supports the preset FEC type. Currently,
coherent boards support HFEC only. If the board does not support the preset FEC
type, set the FEC type as HFEC.
Step 2 For symptom 2:
1. Cause 1: Coherent and non-coherent boards are interconnected.
a. The DCN bytes are defined differently for coherent and non-coherent services, so the
----End
Related Information
Coherent boards are heavy and their components are sensitive, so special package materials are
required and boards must be packaged in strict compliance with the instructions. During
deployment, keep the removed package materials in case of return for repair in future. If boards
OptiX OSN 8800/6800/3800
285
are improperly packaged, they will be easily damaged during transportation, installation, and
return for repair, resulting in unnecessary loss.
Storing Package Materials: Package materials must be free of water and must be handled with
care. They can be stacked.
CAUTION
A board must be put into a foam box with the front panel towards a correct direction. Otherwise,
connectors and optical modules on the board maybe seriously damaged by the stress of the foam
box.
OptiX OSN 8800/6800/3800
286
21 Interconnection Faults
About This Chapter
This topic describes the possible causes and troubleshooting methods for WDM and OTN
equipment interconnection failures.
21.1 Failure in Intercommunication with the Data Equipment
This section describes the possible causes and handling methods of the failure in
intercommunication of the WDM equipment with the data equipment.
21.2 Failure in Intercommunication with the SDH Equipment
intercommunication of the WDM equipment with the SDH equipment.
21.3 WDM and other OTN Equipment Interconnection Failures
21.4 Equipment Interconnection Cases
Case analysis related to Equipment Interconnection cases.
OptiX OSN 8800/6800/3800
Troubleshooting 21 Interconnection Faults
287
21.1 Failure in Intercommunication with the Data
Equipment
intercommunication of the WDM equipment with the data equipment.
Symptom
After a piece of WDM equipment is interconnected to a piece of data equipment, the two pieces
of equipment fail to communicate with each other and the equipment might report the R_LOS,
LINK_ERR and R_OOF alarms.
Impact on System
The two pieces of interconnected equipment fail to communicate with each other.
Possible Causes
l Cause 1: The line between the WDM equipment and the data equipment is faulty.
l Cause 2: The parameter configuration of interconnected board of the WDM equipment on
the client side is incorrect.
l Cause 3: Either or both of the interconnected boards is/are faulty.
U2000, optical power meter
Procedure
Step 1 Cause 1: The line between the WDM equipment and the data equipment is faulty. In this case,
interconnected board of the WDM equipment may report the R_LOS, LINK_ERR alarms on
the client side.
1. Check whether the optical modules of the interconnected boards are of the same type. If
they are of the same type, check whether the supported transmission distance of the optical
modules is equal or longer than the actual distance away from the client side. The single-
mode optical module and the multimode optical module cannot be used together.
2. Check whether the fibers of the interconnected boards match each other. The single-mode
fiber and the multimode fiber cannot be used together.
NOTE
Generally, the multimode fiber is nacarat-colored, and the single-mode fiber is yellow.
3. Check whether any fiber is inserted in an incorrect interface according to the fiber labels.
If any fiber is inserted in an incorrect interface, the equipment might not generate the
R_LOS alarm but generates a large number of performance events against anomalies. In
this case, insert the fiber in the correct interface.
OptiX OSN 8800/6800/3800
288
4. Use an optical power meter to test the interconnect fiber jumper. If the fiber jumper is
abnormal, replace the fiber jumper. If the fiber jumper is good, check whether the optical
cable is faulty.
Step 2 Cause 2: The parameter configuration of interconnected board of the WDM equipment on the
client side is incorrect. In this case, interconnected board of the WDM equipment may report
R_LOS, LINK_ERR alarms on the client side.
1. In the case of the OTU board that can access various service data, check whether the service
type settings of the OTU board are different from those of the data equipment.
l On the interconnected board of the WDM equipment, query and set the client service
type of the board. Make sure that the service type of the WDM equipment is the same
as the interconnected data equipment.
2. Check whether the auto-negotiation modes of the optical interfaces on the interconnected
boards are different from each other.
l Querying and Setting the Working Mode of the Ethernet Port. Make sure that the auto-
negotiation modes are the same.
3. The Maximum Package Length of the optical interfaces on the interconnected boards are
different from each other.
l Log in to the U2000. In the NE Explorer interface, select the interconnected board.
l In Function Tree on the left side, choose Configuration > WDM Interface.
l Select Advanced Attributes, and click Query. Make sure that the Maximum Package
Length of the optical interfaces on the interconnected boards are same.
4. Check whether any interconnected interface is looped back.
l Select Basic Attributes, and click Query. Check whether the optical interface on the
client side of each board is looped back. If yes, double-click the Loopback field. In the
drop-down list, select Non-Loopback and click Apply.
Step 3 Cause 3: Either or both of the interconnected boards is/are faulty.
1. At the optical interface on the client side of the interconnected board in the WDM
equipment, use the optical power meter to test the optical power. If the optical power is
abnormal, replace the board.
2. At the optical interface of the interconnected board in the data equipment, use the optical
power meter to test the optical power. If the optical power is abnormal, replace the board.
----End
21.2 Failure in Intercommunication with the SDH
Equipment
intercommunication of the WDM equipment with the SDH equipment.
OptiX OSN 8800/6800/3800
289
Symptom
After a piece of WDM equipment is interconnected to a piece of SDH equipment, the two pieces
of equipment fail to communicate with each other and the equipment might report the R_LOS,
R_LOF, and R_OOF alarms.
If the equipment reports the B1_EXC, B1_SD, B2_EXC, and B2_SD alarms, it indicates that
bit errors occur in the one of the two pieces of interconnected equipment. For details on how to
clear the fault, see Single-Channel Bit Errors.
Impact on System
The communication between the interconnected equipment is unavailable.
Possible Causes
l Cause 1: The line between the WDM equipment and the SDH equipment is faulty.
l Cause 2: The parameter configuration of interconnected board of the WDM equipment on
the client side is incorrect.
l Cause 3: Either or both of the interconnected boards is/are faulty.
Procedure
Step 1 Cause 1: The line between the WDM equipment and the SDH equipment is faulty. In this case,
interconnected board of the WDM equipment may report the R_LOS and R_LOF alarms on the
client side.
2. Check whether the fibers of the interconnected boards match each other. The single-mode
fiber and the multimode fiber cannot be used together.
NOTE
Generally, the multimode fiber is nacarat-colored, and the single-mode fiber is yellow.
3. Check whether any fiber is inserted in an incorrect interface according to the fiber labels.
If any fiber is inserted in an incorrect interface, the equipment might not generate the
R_LOS alarm but generates a large number of performance events against anomalies. In
this case, insert the fiber in the correct interface.
4. Use an optical power meter to test the interconnect fiber jumper. If the fiber jumper is
abnormal, replace the fiber jumper. If the fiber jumper is good, check whether the optical
cable is faulty.
Step 2 Cause 2: The parameter configuration of interconnected board of the WDM equipment on the
client side is incorrect. In this case, interconnected board of the WDM equipment may report
R_OOF alarm on client side.
1. Check whether the service types of the interconnected boards mismatch each other.
OptiX OSN 8800/6800/3800
290
l On the interconnected board of the WDM equipment, query and set the client service
type of the board. Make sure that the service type of the WDM equipment is the same
as the interconnected SDH equipment.
2. Check whether any interconnected interface is looped back.
l Select Basic Attributes, and click Query. Check whether the optical interface on the
client side of each board is looped back. If yes, double-click the Loopback field. In the
drop-down list, select Non-Loopback and click Apply.
Step 3 Cause 3: Either or both of the interconnected boards is/are faulty.
1. At the optical interface on the client side of the interconnected board in the WDM
equipment, use the optical power meter to test the optical power. If the optical power is
abnormal, replace the board.
2. At the optical interface of the interconnected board in the SDH equipment, use the optical
power meter to test the optical power. If the optical power is abnormal, replace the board.
----End
21.3 WDM and other OTN Equipment Interconnection
Failures
Symptom
After local WDM equipment is interconnected with other OTN equipment, the two devices fail
to communicate with each other and the U2000 may report R_LOS, OTUk_LOF, and
OTUk_LOM alarms.
System Impact
Interconnected devices are unable to communicate with each other.
Possible Causes
l Cause 1: The line between the local WDM equipment and the other OTN equipment is
faulty.
l Cause 2: The client-side configuration for the interconnected board on the WDM equipment
is incorrect.
l Cause 3: One or both of the interconnected boards is/are faulty.
OptiX OSN 8800/6800/3800
291
Procedure
Step 1 Cause 1: The line between the local WDM equipment and the other OTN equipment is faulty.
In this case, the interconnected board on the WDM equipment may report the R_LOS alarm on
the client side.
2. Check whether the optical fibers of the interconnected boards match each other. The single-
mode optical fiber and the multimode optical fiber cannot be used together.
NOTE
Generally, the multimode optical fiber is nacarat, and the single-mode fiber is yellow.
3. Check whether any optical fiber is installed on an incorrect port according to the optical
fiber labels. If any optical fiber is installed on an incorrect port, the R_LOS alarm might
not be generated but a large number of performance events against anomalies may be
generated on the equipment. In this case, install the optical fiber on the correct port.
4. Use an optical power meter to test the pigtail interconnected with the equipment. If the
pigtail is abnormal, replace it. If it is normal, check whether the optical cable is faulty.
Step 2 Cause 2: The client-side configuration for the ports on the interconnected board of the WDM
equipment is incorrect. In this case, the interconnected board on the WDM equipment may report
the OTUk_LOF and OTUk_LOM alarms on the client side.
1. Check whether the service types, FEC mode, working modes, board mode of the
interconnected boards are inconsistent.
l Query and set the client service type of the interconnected board of the WDM
equipment. Ensure that the service type of the WDM equipment is the same as that of
the interconnected OTN equipment.
2. Check whether a loop is occurring on any interconnected port.
l Log in to the U2000. In NE Explorer, select the interconnected NE.
l Choose Configuration > WDM Interface from the Function Tree.
l On the Basic Attributes tab, click Query to check whether a loopback is enabled on
any optical port on the client side of each board. If a loopback is enabled, double-click
the Loopback field. In the drop-down list, select Non-Loopback and click Apply.
Step 3 Cause 3: One or both of the interconnected boards is/are faulty.
1. Use the optical power meter to test the optical power of the client-side optical port on the
interconnected board of the WDM equipment. If the optical power is abnormal, replace the
board.
2. Use the optical power meter to test the optical power of the optical port on the
interconnected board of the OTN equipment. If the optical power is abnormal, replace the
board.
----End
21.4 Equipment Interconnection Cases
Case analysis related to Equipment Interconnection cases.
OptiX OSN 8800/6800/3800
292
NOTE
Related Cases:
LINK_STATUS alarm.
Alarms Transiently
l MC-A11 The SSE3LWF Board Reports the OTU_LOF Alarm When Interworking with
the SSE1TMR
l MC-A17 The LQG Reports ALM_DATA_RLOS and ALM_DATA_TLOS Alarms
l MC-A21 An Interconnection Failure between the WDM and SDH Equipment
l MC-A30 LDG Board of Metro 6100 Equipment Reports the INBADOCTS_OVER Alarm
l MC-A44 Bit Errors Generated in the Services, the Meter Reports the HP_RDI and ERROR
Alarms
l MC-A49 An Incorrect Setting of CRC Results in an Interconnection Failure
l MC-A67 The GE Port on the Client Side Reports LINK_DOWN Alarm
l MC-A74 The FDG Reports the T_DATA_LOST and R_DATA_LOST Alarms
l MC-A75 Bandwidth Decreases and Service Rate Becomes Lower Due to Improper Setting
l MC-A84 Maximal Packet Length Setting of the OptiX OSN 6800 Causes the Abnormal
Service
Equipment
l MC-A153 It Is Recommended to Enable the Auto-Negotiation Working Mode at a GE Port
When the LPT Function Is Enabled, Or The Services Are Interrupted And The System
Reports The R_LOS Alarms
l MC-A154 The N2SLQ16 Board Interconnected with the TQS Board Reports an R_LOS
Alarm Because The TQS Board Emits White Lights When the Input Optical Power Is
Normal
l MC-A156 An SDH Board on the SDH Equipment Reports an R_LOF Alarm When the
SDH Board Is Interconnected with a Tributary Board on the OptiX OSN 6800
l MC-A185 Incorrect Client-Side Service Type Causes Failure of Interconnection With a
Router
l MC-A249 The OTN Equipment Fails to Transparently Transmit Ethernet Clock Signals
OptiX OSN 8800/6800/3800
293
A Remote Maintenance Guide
This topic describes remote maintenance.
A.1 Overview
This topic provides remote maintenance overview.
A.2 Enabling Remote Maintenance User
This section introduces how to enable remote maintenance user.
A.3 Creating Remote Maintenance
This section introduces how to create remote maintenance between the U2000 service end and
the remote maintenance terminal.
OptiX OSN 8800/6800/3800
Troubleshooting A Remote Maintenance Guide
294
A.1 Overview
This topic provides remote maintenance overview.
The Huawei optical transmission equipment series supports remote maintenance. A remote
computer (remote end) can connect to an on-site U2000 server (local end) through a public
switched telephone network (PSTN) or through the Internet. The remote computer then can
perform maintenance to the equipment.
Figure A-1 is a networking diagram illustrating remote maintenance. A modem is installed at
the remote maintenance terminal and on the U2000 server, and dial-up programs are installed
at each end. These operations are performed during the U2000 installation.
Figure A-1 Remote maintenance networking diagram
PSTN/
Internet
Modem
Modem
Remote
maintenance
ternimal
serial
port
serial
port
U2000
Server
WDM
network

During remote maintenance, the U2000 server needs to cooperate with the remote end to perform
the following operations:
l Enable the remote maintenance user.
l Establish the remote maintenance connection.
A.2 Enabling Remote Maintenance User
This section introduces how to enable remote maintenance user.
Prerequisites
You must be an NM user with "Network administrator" authority or higher.
OptiX OSN 8800/6800/3800
295
Context
A remote maintenance user is the NM user who logs in to the U2000 server to maintain the
equipment. Remote maintenance users are in Disable status by default. You need to enable it
before you start the remote maintenance.
Procedure
Step 1 In the Main Menu choose System > Remote Maintenance User Management to display the
Remote Maintenance User Management dialog box.
Step 2 Set the Disable/Enable to be Enable. Set the other attributes of the remote user.
Step 3 Click Apply.
Step 4 Click OK to confirm the settings.
----End
A.3 Creating Remote Maintenance
This section introduces how to create remote maintenance between the U2000 service end and
the remote maintenance terminal.
Prerequisites
The communication connection between the remote maintenance terminal and the U2000 server
must have been configured.
The remote maintenance user must have been enabled.
The user name and password of the U2000 server must be known to maintenance personnel at
the remote maintenance end.
Procedure
Step 1 On the U2000 server, query the connection status for remote maintenance. If the remote
maintenance connection is normal, go to step 5. If not, go to step 2.
The query methods are listed as follows.
l If the Windows operating system is installed, right-click My Network Places and select
Properties to query the connection status for remote maintenance.
l If the Solaris or Linux operating system is installed, open a terminal window and run the
ifconfig -a command to query the connection status for remote maintenance.
Step 2 Double-click the shortcut icon, which is created for dial-up connection, on the desktop, such as
Remote Maintenance to perform dial-up connection.
Step 3 Enter the user name (ppp_user) and password in the displayed dialog box.
Step 4 Enter the user name and password. Press the Enter key and click the D button at the right bottom
corner to establish the connection.
OptiX OSN 8800/6800/3800
296
NOTE
After you enter the password and press the Enter key, a line of illegal characters is displayed. This is normal.
Step 5 Query the IP address for dial-up access to network.
l If the Windows operating system is installed, choose Start > All Programs > Accessories
> Command Prompt. Enter ipconfig in the dialog box and query the dynamic IP address
for dial-up access to network.
l If the Solaris or Linux operating system is installed, display a terminal window and run the
ifconfig -a command to query dynamic IP address for dial-up access to network.
NOTE
The address for dial-up access is IP address. If the dial-up connection of the server is disconnected, re-dial
to get a new IP address.
Step 6 Inform the maintenance personnel at the remote end of the queried IP address.
Step 7 Establish the dial-up connection between the remote maintenance personnel and the U2000
server. Log in to the U2000 client. After the login succeeds, you can perform the remote
maintenance.
CAUTION
To ensure network security, set the remote maintenance user to Disabled after the remote
maintenance.
----End
OptiX OSN 8800/6800/3800
297
B Glossary
Numerics
1+1 backup A backup method in which two components mirror each other. If the active component
goes down, the standby component takes over services from the active component to
ensure that the system service is not interrupted.
1000BASE-T An Ethernet specification that uses the twisted pair cable with the transmission speed as
1000 Mbit/s and the transmission distance as 100 meters.
3R reshaping, retiming, regenerating
A
AC alternating current
ACL See access control list.
ADM add/drop multiplexer
ADSL See asymmetric digital subscriber line.
AGC automatic gain control
AIS alarm indication signal
ALC link A piece of end-to-end configuration information, which exists in the equipment (single
station) as an ALC link node. Through the ALC function of each node, it fulfills optical
power control on the line that contains the link.
ALS See automatic laser shutdown.
ANSI See American National Standards Institute.
APE See automatic power equilibrium.
APS automatic protection switching
ASE amplified spontaneous emission
ASIC See application-specific integrated circuit.
ATM asynchronous transfer mode
OptiX OSN 8800/6800/3800
Troubleshooting B Glossary
298
American National
Standards Institute
(ANSI)
An organization that defines U.S standards for the information processing industry.
access control list
(ACL)
A list of entities, together with their access rights, which are authorized to access a
resource.
active/standby
switchover
A troubleshooting technology. When an active device becomes faulty, services and
control functions are automatically switched over to the standby device to ensure the
normal running of the services and functions.
alarm cable A cable used to transmit visual or audio alarms.
alarm cascading The method of cascading alarm signals from several subracks or cabinets.
alarm output Node or other signals that are sent by an alarm controller to peripheral devices when an
alarm is reported.
alarm suppression A method to suppress alarms for the alarm management purpose. Alarms that are
suppressed are no longer reported from NEs.
application-specific
integrated circuit
(ASIC)
A special type of chip that starts out as a nonspecific collection of logic gates. Late in
the manufacturing process, a layer is added to connect the gates for a specific function.
By changing the pattern of connections, the manufacturer can make the chip suitable for
many needs.
asymmetric digital
subscriber line (ADSL)
A technology for transmitting digital information at a high bandwidth on existing phone
lines to homes and businesses. Unlike regular dialup phone service, ADSL provides
continuously-available, "always on" connection. ADSL is asymmetric in that it uses most
of the channel to transmit downstream to the user and only a small part to receive
information from the user. ADSL simultaneously accommodates analog (voice)
information on the same line. ADSL is generally offered at downstream data rates from
512 kbit/s to about 6 Mbit/s.
attenuation Reduction of signal magnitude or signal loss, usually expressed in decibels.
attenuator A device used to increase the attenuation of an Optical Fiber Link. Generally used to
ensure that the signal at the receive end is not too strong.
automatic laser
shutdown (ALS)
A technique (procedure) to automatically shutdown the output power of laser transmitters
and optical amplifiers to avoid exposure to hazardous levels.
automatic power
equilibrium (APE)
A function to automatically equalize channel optical power at the transmitter end,
ensuring a required optical power flatness and OSNR at the receiver end.
B
B/S browser/server
BBER background block error ratio
BC boundary clock
BDI See backward defect indication.
BGP Border Gateway Protocol
BIOS See basic input/output system.
BIP See bit interleaved parity.
OptiX OSN 8800/6800/3800
299
BIP-8 See bit interleaved parity-8.
BITS See building integrated timing supply.
BOM bill of materials
BPDU See bridge protocol data unit.
BPSK See binary phase shift keying.
BRAS See broadband remote access server.
backbone network A network that forms the central interconnection for a connected network. The
communication backbone for a country is WAN. The backbone network is an important
architectural element for building enterprise networks. It provides a path for the exchange
of information between different LANs or subnetworks. A backbone can tie together
diverse networks in the same building, in different buildings in a campus environment,
or over wide areas. Generally, the backbone network's capacity is greater than the
networks connected to it.
backplane An electronic circuit board containing circuits and sockets into which additional
electronic devices on other circuit boards or cards can be plugged.
backward defect
indication (BDI)
A function that the sink node of a LSP, when detecting a defect, uses to inform the
upstream end of the LSP of a downstream defect along the return path.
bandwidth A range of transmission frequencies a transmission line or channel can carry in a network.
In fact, the bandwidth is the difference between the highest and lowest frequencies in
the transmission line or channel. The greater the bandwidth, the faster the data transfer
rate.
basic input/output
system (BIOS)
Firmware stored on the computer motherboard that contains basic input/output control
programs, power-on self test (POST) programs, bootstraps, and system setting
information. The BIOS provides hardware setting and control functions for the computer.
binary phase shift
keying (BPSK)
2-phase modulation for carrier based on binary baseband signal. In this modulation mode,
the binary character 0 represents phase 0 of the carrier, and character 1 represents the
phase 180. The phase of character 0 is 0, and the phase of character 1 needs to be
specified. This is an absolute phase shift mode that uses different phases to represent
digital information.
bit The smallest unit of information handled by a hardware component. One bit expresses
a 1 or a 0 in a binary numeral, or a true or a false logical condition, and is represented
physically by an element such as a high or low voltage at one point in a circuit or a small
spot on a disk magnetized one way or the other. A single bit conveys little information
a human would consider meaningful. A group of eight bits, however, makes up a byte,
which can be used to represent many types of information, such as a letter of the alphabet,
a decimal digit, or other character.
bit interleaved parity
(BIP)
A method of error monitoring. With even parity, the transmitting equipment generates
an X-bit code over a specified portion of the signal in such a manner that the first bit of
the code provides even parity over the first bit of all X-bit sequences in the covered
portion of the signal, the second bit provides even parity over the second bit of all X-bit
sequences within the specified portion, and so forth. Even parity is generated by setting
the BIP-X bits so that an even number of 1s exist in each monitored partition of the
signal. A monitored partition comprises all bits in the same bit position within the X-bit
sequences in the covered portion of the signal. The covered portion includes the BIP-X.
OptiX OSN 8800/6800/3800
300
bit interleaved parity-8
(BIP-8)
Consists of a parity byte calculated bit-wise across a large number of bytes in a
transmission transport frame. Divide a frame is into several blocks with 8 bits (one byte)
in a parity unit and then arrange the blocks in matrix. Compute the number of "1" or "0"
over each column. Then fill a 1 in the corresponding bit for the result if the number is
odd, otherwise fill a 0.
bit/s See bits per second.
bits per second (bit/s) A rate at which the individual bits are transmitted through a communication link or
circuit. Its unit can be bit/s, kbit/s, and Mbit/s.
bridge A device that connects two or more networks and forwards packets among them. Bridges
operate at the physical network level. Bridges differ from repeaters because bridges store
and forward complete packets, while repeaters forward all electrical signals. Bridges
differ from routers because bridges use physical addresses, while routers use IP
addresses.
bridge protocol data
unit (BPDU)
Data messages exchanged across switches within an extended LAN that uses a spanning
tree protocol (STP) topology. BPDU packets contain information on ports, addresses,
priorities, and costs, and they ensure that the data reaches its intended destination. BPDU
messages are exchanged across bridges to detect loops in a network topology. These
loops are then removed by shutting down selected bridge interfaces and placing
redundant switch ports in a backup, or blocked, state.
broadband remote
access server (BRAS)
A new type of access gateway for broadband networks. As a bridge between backbone
networks and broadband access networks, BRAS provides methods for fundamental
access and manages the broadband access network. It is deployed at the edge of network
to provide broadband access services, convergence, and forwarding of multiple services,
meeting the demands for transmission capacity and bandwidth utilization of different
users. BRAS is a core device for the broadband users' access to a broadband network.
broadcast A means of delivering information to all members in a network. The broadcast range is
determined by the broadcast address.
broadcast address A network address in computer networking that allows information to be sent to all nodes
on a network, rather than to a specific network host.
building integrated
timing supply (BITS)
In the situation of multiple synchronous nodes or communication devices, one can use
a device to set up a clock system on the hinge of telecom network to connect the
synchronous network as a whole, and provide satisfactory synchronous base signals to
the building integrated device. This device is called BITS.
bus A path or channel for signal transmission. The typical case is that, the bus is an electrical
connection that connects one or more conductors. All devices that are connected to a
bus, can receive all transmission contents simultaneously.
byte A unit of computer information equal to eight bits.
C
CAR committed access rate
CBR See constant bit rate.
CE See customer edge.
CES See circuit emulation service.
OptiX OSN 8800/6800/3800
301
CPRI See common public radio interface.
CPU See central processing unit.
CRC See cyclic redundancy check.
CSF Client Signal Fail
CSMA/CD See carrier sense multiple access with collision detection.
CV connectivity verification
CWDM See coarse wavelength division multiplexing.
cabinet Free-standing and self-supporting enclosure for housing electrical and/or electronic
equipment. It is usually fitted with doors and/or side panels which may or may not be
removable.
carrier sense multiple
access with collision
detection (CSMA/CD)
Carrier sense multiple access with collision detection (CSMA/CD) is a computer
networking access method in which:
l A carrier sensing scheme is used.
l A transmitting data station that detects another signal while transmitting a frame,
stops transmitting that frame, transmits a jam signal, and then waits for a random
time interval before trying to send that frame again.
central processing unit
(CPU)
The computational and control unit of a computer. The CPU is the device that interprets
and executes instructions. The CPU has the ability to fetch, decode, and execute
instructions and to transfer information to and from other resources over the computer's
main data-transfer path, the bus.
chain network One type of network that all network nodes are connected one after one to be in series.
circuit emulation
service (CES)
A function with which the E1/T1 data can be transmitted through ATM networks. At the
transmission end, the interface module packs timeslot data into ATM cells. These ATM
cells are sent to the reception end through the ATM network. At the reception end, the
interface module re-assigns the data in these ATM cells to E1/T1 timeslots. The CES
technology guarantees that the data in E1/T1 timeslots can be recovered to the original
sequence at the reception end.
client trail A lower level trail in a structure where trails of different levels have an inclusion relation.
For example, a trail of a certain level contains multiple trails of lower levels.
clock source A device that provides standard time for the NTP configuration.
clock synchronization A process of synchronizing clocks, in which the signal frequency traces the reference
frequency, but the start points do not need to be consistent. This process is (also known
as frequency synchronization).
clock tracing The method of keeping the time on each node synchronized with a clock source in the
network.
coarse wavelength
division multiplexing
(CWDM)
A signal transmission technology that multiplexes widely-spaced optical channels into
the same fiber. CWDM spaces wavelengths at a distance of several nm. CWDM does
not support optical amplifiers and is applied in short-distance chain networking.
collection A process of prompting a customer to pay outstanding bills.
OptiX OSN 8800/6800/3800
302
common public radio
interface (CPRI)
A common standard of the key internal interface between the REC and the RE of the
wireless base station. This standard was established by Huawei, Ericsson, NEC, Siemens,
and Nortel in June 2003. It aims at standardizing the baseband and RF interface. The
CPRI has a set of mature standards, which advance the standard and equipment. The
major feature of the CPRI is that baseband is separated from RF to reduce the cost of
engineering, equipment room, and equipment.
configuration data A command file defining hardware configurations of an NE. With this file, an NE can
collaborate with other NEs in a network. Therefore, configuration data is the key factor
that determines the operation of an entire network.
connection point A reference point where the output of a trail termination source or a connection is bound
to the input of another connection, or where the output of a connection is bound to the
input of a trail termination sink or another connection. The connection point is
characterized by the information which passes across it. A bidirectional connection point
is formed by the association of a contradirectional pair.
consistency check A function that is used to check the consistency of service data and resource data between
two softswitches that have the dual homing relation. This ensures the consistency of
service data and resource data between the softswitches.
constant bit rate (CBR) A kind of service categories defined by the ATM forum. CBR transfers cells based on
the constant bandwidth. It is applicable to service connections that depend on precise
clocking to ensure undistorted transmission.
control VLAN A VLAN that transmits only protocol packets.
convergence layer A "bridge" between the access layer and the core layer. The convergence layer provides
the convergence and forwarding functions for the access layer. It processes all the traffic
from the access layer devices, and provides the uplinks to the core layer. Compared with
the access layer, the convergence layer devices should have higher performance, fewer
interfaces and higher switching rate. In the real network, the convergence layer refers to
the network between UPEs and PE-AGGs.
cross-connection The connection of channels between the tributary board and the line board, or between
line boards inside the NE. Network services are realized through the cross-connections
of NEs.
customer edge (CE) A part of the BGP/MPLS IP VPN model that provides interfaces for directly connecting
to the Service Provider (SP) network. A CE can be a router, switch, or host.
cyclic redundancy
check (CRC)
A procedure used to check for errors in data transmission. CRC error checking uses a
complex calculation to generate a number based on the data transmitted. The sending
device performs the calculation before performing the transmission and includes the
generated number in the packet it sends to the receiving device. The receiving device
then repeats the same calculation. If both devices obtain the same result, the transmission
is considered to be error free. This procedure is known as a redundancy check because
each transmission includes not only data but extra (redundant) error-checking values.
D
DAPI destination access point identifier
DBPS distributed board protect system
DC direct current
OptiX OSN 8800/6800/3800
303
DC-C See DC-return common (with ground).
DC-I See DC-return isolate (with ground).
DC-return common
(with ground) (DC-C)
A power system, in which the BGND of the DC return conductor is short-circuited with
the PGND on the output side of the power supply cabinet and also on the line between
the output of the power supply cabinet and the electric equipment.
DC-return isolate (with
ground) (DC-I)
A power system, in which the BGND of the DC return conductor is short-circuited with
the PGND on the output side of the power supply cabinet and is isolated from the PGND
on the line between the output of the power supply cabinet and the electric equipment.
DCC See data communications channel.
DCM See dispersion compensation module.
DCN See data communication network.
DGD differential group delay
DLAG See distributed link aggregation group.
DRDB dynamic random database
DRZ differential phase return to zero
DSLAM See digital subscriber line access multiplexer.
DSP See digital signal processor.
DVB-ASI digital video broadcast-asynchronous serial interface
DWDM See dense wavelength division multiplexing.
data communication
network (DCN)
A communication network used in a TMN or between TMNs to support the data
communication function.
data communications
channel (DCC)
The data channel that uses the D1-D12 bytes in the overhead of an STM-N signal to
transmit information on the operation, management, maintenance, and provisioning
(OAM&P) between NEs. The DCC channel composed of bytes D1-D3 is referred to as
the 192 kbit/s DCC-R channel. The other DCC channel composed of bytes D4-D12 is
referred to as the 576 kbit/s DCC-M channel.
dense wavelength
division multiplexing
(DWDM)
The technology that utilizes the characteristics of broad bandwidth and low attenuation
of single mode optical fiber, employs multiple wavelengths with specific frequency
spacing as carriers, and allows multiple channels to transmit simultaneously in the same
fiber.
digital signal processor
(DSP)
A microprocessor designed specifically for digital signal processing, generally in real
time.
digital subscriber line
access multiplexer
(DSLAM)
A network device, usually situated in the main office of a telephone company, that
receives signals from multiple customer Digital Subscriber Line (DSL) connections and
uses multiplexing techniques to put these signals on a high-speed backbone line.
discrete service The cross-connection that exists on an NE but cannot form trails on the network
management system.
dispersion
compensation module
(DCM)
A type of module that contains dispersion compensation fibers to compensate for the
dispersion of the transmitting fiber.
OptiX OSN 8800/6800/3800
304
distributed link
aggregation group
(DLAG)
A board-level port protection technology that detects unidirectional fiber cuts and
negotiates with the opposite port. In the case of a link down failure on a port or hardware
failure on a board, services are automatically switched to the slave board, thereby
achieving 1+1 protection for the inter-board ports.
dual feed and selective
receiving
A channel used to transmit monitoring data on an optical transmission network. The
monitoring data is transmitted on the data communications channel as part of the
overhead of the service signal.
dual-ended switching A protection method in which switching is performed at both ends of a protected entity,
such as a connection or path, even if a unidirectional failure occurs.
E
E-LAN See Ethernet local area network.
E-Line See Ethernet line.
E1 An European standard for high-speed data transmission at 2.048 Mbit/s. It provides
thirty-two 64 kbit/s channels. A time division multiplexing frame is divided in to 32
timeslots numbered from 0 to 31. Timeslot 0 is reserved for frame synchronization, and
timeslot 16 is reserved for signaling transmission. The rest 30 timeslots are use as speech
channels. Each timeslot sends or receives an 8-bit data per second. Each frame sends or
receives 256-bit data per second. 8000 frames will be sent or received per second.
Therefore the line data rate is 2.048 Mbit/s.
EAPE enhanced automatic power pre-equilibrium
ECC See embedded control channel.
EDFA See erbium-doped fiber amplifier.
EEPROM See electrically erasable programable read-only memory.
EMI See electromagnetic interference.
EPL See Ethernet private line.
EPLAN See Ethernet private LAN service.
EPLD See erasable programmable logical device.
EPON See Ethernet passive optical network.
ERPS Ethernet ring protection switching
ES edge server
ESC See electric supervisory channel.
ESCON See enterprise system connection.
ESD electrostatic discharge
ESN See equipment serial number.
ETS European Telecommunication Standards
ETSI See European Telecommunications Standards Institute.
EVOA electrical variable optical attenuator
EVPL See Ethernet virtual private line.
OptiX OSN 8800/6800/3800
305
EVPLAN See Ethernet virtual private LAN service.
EXP See experimental bits.
Ethernet A LAN technology that uses the carrier sense multiple access with collision detection
(CSMA/CD) media access control method. The Ethernet network is highly reliable and
easy to maintain. The speed of an Ethernet interface can be 10 Mbit/s, 100 Mbit/s, 1000
Mbit/s, or 10,000 Mbit/s.
Ethernet line (E-Line) A type of Ethernet service that is based on a point-to-point EVC (Ethernet virtual
connection).
Ethernet local area
network (E-LAN)
A type of Ethernet service that is based on a multipoint-to-multipoint EVC (Ethernet
virtual connection).
Ethernet passive
optical network
(EPON)
A passive optical network based on Ethernet. It is a new generation broadband access
technology that uses a point-to-multipoint structure and passive fiber transmission. It
supports upstream/downstream symmetrical rates of 1.25 Gbit/s and a reach distance of
up to 20 km. In the downstream direction, the bandwidth is shared based on encrypted
broadcast transmission for different users. In the upstream direction, the bandwidth is
shared based on TDM. EPON meets the requirements for high bandwidth.
Ethernet private LAN
service (EPLAN)
A type of Ethernet service provided by SDH, PDH, ATM, or MPLS server layer
networks. This service is carried over dedicated bandwidth between multipoint-to-
multipoint connections.
Ethernet private line
(EPL)
networks. This service is carried over dedicated bandwidth between point-to-point
connections.
Ethernet virtual
private LAN service
(EVPLAN)
networks. This service is carried over shared bandwidth between multipoint-to-
multipoint connections.
Ethernet virtual
private line (EVPL)
networks. This service is carried over shared bandwidth between point-to-point
connections.
European
Telecommunications
Standards Institute
(ETSI)
A standards-setting body in Europe. Also the standards body responsible for GSM.
eDQPSK enhanced differential quadrature phase shift keying
eSFP enhanced small form-factor pluggable
egress The egress LER. The group is transferred along the LSP consisting of a series of LSRs
after the group is labeled.
electric supervisory
channel (ESC)
A technology that implements communication among all the nodes and transmission of
monitoring data in an optical transmission network. The monitoring data of ESC is
introduced into DCC service overhead and is transmitted with service signals.
electrically erasable
programable read-only
memory (EEPROM)
A type of EPROM that can be erased with an electrical signal. It is useful for stable
storage for long periods without electricity while still allowing reprograming. EEPROMs
contain less memory than RAM, take longer to reprogram, and can be reprogramed only
a limited number of times before wearing out.
OptiX OSN 8800/6800/3800
306
electromagnetic
interference (EMI)
Any electromagnetic disturbance that interrupts, obstructs, or otherwise degrades or
limits the performance of electronics/electrical equipment.
embedded control
channel (ECC)
A logical channel that uses a data communications channel (DCC) as its physical layer
to enable the transmission of operation, administration, and maintenance (OAM)
information between NEs.
encapsulation A technology for layered protocols, in which a lower-level protocol accepts a message
from a higher-level protocol and places it in the data portion of the lower-level frame.
Protocol A's packets have complete header information, and are carried by protocol B
as data. Packets that encapsulate protocol A have a B header, an A header, followed by
the information that protocol A is carrying. Note that A could equal to B, as in IP inside
IP.
encryption A function used to transform data so as to hide its information content to prevent it's
unauthorized use.
enterprise system
connection (ESCON)
A path protocol that connects the host to various control units in a storage system.
Enterprise system connection is a serial bit stream transmission protocol that operates a
rate of 200 Mbit/s.
equalization A method of avoiding selective fading of frequencies. Equalization can compensate for
the changes of amplitude frequency caused by frequency selective fading.
equipment serial
number (ESN)
A string of characters that identify a piece of equipment and ensures correct allocation
of a license file to the specified equipment. It is also called "equipment fingerprint".
erasable
programmable logical
device (EPLD)
A logical array device which can be used to implement the required functions by
programming the array. In addition, a user can modify and program the array repeatedly
until the program meets the requirement.
erbium-doped fiber
amplifier (EDFA)
An optical device that amplifies optical signals. This device uses a short optical fiber
doped with the rare-earth element, Erbium. The signal to be amplified and a pump laser
are multiplexed into the doped fiber, and the signal is amplified by interacting with
doping ions. When the amplifier passes an external light source pump, it amplifies the
optical signals in a specific wavelength range.
experimental bits
(EXP)
A field in the MPLS packet header, three bits long. This field is always used to identify
the CoS of the MPLS packet.
extended ID The number of the subnet to which an NE belongs, used to identify different network
segments in a wide area network (WAN). Together, the ID and extended ID form the
physical ID of the NE.
eye pattern An oscilloscope display in which a digital data signal from a receiver is repetitively
sampled and applied to the vertical input, while the data rate is used to trigger the
horizontal sweep. It is so called because, for several types of coding, the pattern looks
like a series of eyes between a pair of rails.
F
FC See Fibre Channel.
FCS free cooling system
FDB See forwarding database.
FDDI See fiber distributed data interface.
OptiX OSN 8800/6800/3800
307
FE fast Ethernet
FEC See forward error correction.
FICON See Fiber Connect.
FOADM fixed optical add/drop multiplexer
FPGA See field programmable gate array.
FTP File Transfer Protocol
Fiber Connect
(FICON)
A new generation connection protocol that connects the host to various control units. It
carries a single byte command protocol through the physical path of fiber channel, and
provides a higher transmission rate and better performance than ESCON.
Fibre Channel (FC) A high-speed transport technology used to build SANs. FC is primarily used for
transporting SCSI traffic from servers to disk arrays, but it can also be used on networks
carrying ATM and IP traffic. FC supports single-mode and multi-mode fiber
connections, and can run on twisted-pair copper wires and coaxial cables. FC provides
both connection-oriented and connectionless services.
fault alarm A type of alarm caused by hardware and/or software faults, for example, board failure,
or by the exception that occurs in major functions. After handling, a fault alarm can be
cleared, upon which the NE reports a recovery alarm. Fault alarms are of higher severity
than event alarms.
fiber distributed data
interface (FDDI)
A standard developed by the American National Standards Institute (ANSI) for high-
speed fiber-optic LANs. FDDI provides specifications for transmission rates of 100
megabits per second on token ring networks.
field programmable
gate array (FPGA)
A semi-customized circuit that is used in the Application Specific Integrated Circuit
(ASIC) field and developed based on programmable components. FPGA remedies many
of the deficiencies of customized circuits, and allows the use of many more gate arrays.
forced switching The action of switching traffic signals between a working channel and protection
channel. The switching occurs even if the channel to which traffic is being switched is
faulty or an equal or higher priority switching command is in effect.
forward error
correction (FEC)
A bit error correction technology that adds correction information to the payload at the
transmit end. Based on the correction information, the bit errors generated during
transmission can be corrected at the receive end.
forwarding database
(FDB)
A type of database that Includes entries for guiding multicast data forwarding. There are
Layer 2 FDB and Layer 3 FDB. The Layer 2 FDB refers to the MAC table, which provides
information about the MAC address and outbound interface and guides Layer 2
forwarding. The Layer 3 FDB refers to the ARP table, which provides information about
the IP address and outbound interface and guides Layer 3 forwarding.
G
GCC general communication channel
GE Gigabit Ethernet
GFP See Generic Framing Procedure.
GMP Group Map Protocol
GMPLS generalized multiprotocol label switching
OptiX OSN 8800/6800/3800
308
GNE See gateway network element.
GPON gigabit-capable passive optical network
GPS See Global Positioning System.
Generic Framing
Procedure (GFP)
A framing and encapsulated method that can be applied to any data type. GFP is defined
by ITU-T G.7041.
Global Positioning
System (GPS)
A global navigation satellite system that provides reliable positioning, navigation, and
timing services to users worldwide.
gain The difference between the optical power from the input optical interface of the optical
amplifier and the optical power from the output optical interface of the jumper fiber,
which expressed in dB.
gateway A device that connects two network segments using different protocols. It is used to
translate the data in the two network segments.
gateway network
element (GNE)
An NE that serves as a gateway for other NEs to communicate with a network
management system.
H
HD-SDI high definition serial digital interface
HSDPA See High Speed Downlink Packet Access.
High Speed Downlink
Packet Access
(HSDPA)
A modulating-demodulating algorithm put forward in 3GPP R5 to meet the requirement
for asymmetric uplink and downlink transmission of data services. It enables the
maximum downlink data service rate to reach 14.4 Mbit/s without changing the
WCDMA network topology.
handle A component of the panel. It is used to insert or remove boards in and out of slots.
hardware loopback A connection mode in which a fiber jumper is used to connect the input optical interface
of a board to the output optical interface of the board to achieve signal loopback.
hop A network connection between two distant nodes. For Internet operation a hop represents
a small step on the route from one main computer to another.
hot patch A patch that is used to repair a deficiency in the software or add a new feature to a program
without restarting the software and interrupting the service. For the equipment using the
built-in system, a hot patch can be loaded, activated, confirmed, deactivated, deleted, or
queried.
I
IANA See Internet Assigned Numbers Authority.
IC See integrated circuit.
ICMP See Internet Control Message Protocol.
IEEE See Institute of Electrical and Electronics Engineers.
IETF Internet Engineering Task Force
IGMP See Internet Group Management Protocol.
IMA See inverse multiplexing over ATM.
OptiX OSN 8800/6800/3800
309
IP Internet Protocol
IP subnet A special submap used to identify an IP network segment. It is displayed as the submap
icon in the topological view.
IPA See intelligent power adjustment.
IPv4 See Internet Protocol version 4.
IPv6 See Internet Protocol version 6.
IS-IS See Intermediate System to Intermediate System.
ISDN integrated services digital network
ISO International Organization for Standardization
ITU-T International Telecommunication Union-Telecommunication Standardization Sector
Institute of Electrical
and Electronics
Engineers (IEEE)
A professional association of electrical and electronics engineers based in the United
States, but with membership from numerous other countries. The IEEE focuses on
electrical, electronics, and computer engineering, and produces many important
technology standards.
Intermediate System to
Intermediate System
(IS-IS)
A protocol used by network devices (routers) to determine the best way to forward
datagram or packets through a packet-based network.
Internet Assigned
Numbers Authority
(IANA)
A department operated by the IAB. IANA delegates authority for IP address-space
allocation and domain-name assignment to the NIC and other organizations. IANA also
maintains a database of assigned protocol identifiers used in the TCP/IP suite, including
autonomous system numbers.
Internet Control
Message Protocol
(ICMP)
A network layer protocol that provides message control and error reporting between a
host server and an Internet gateway.
Internet Group
Management Protocol
(IGMP)
One of the TCP/IP protocols for managing the membership of Internet Protocol multicast
groups. It is used by IP hosts and adjacent multicast routers to establish and maintain
multicast group memberships.
Internet Protocol
version 4 (IPv4)
The current version of the Internet Protocol (IP). IPv4 utilizes a 32bit address which is
assigned to hosts. An address belongs to one of five classes (A, B, C, D, or E) and is
written as 4 octets separated by periods and may range from 0.0.0.0 through to
255.255.255.255. Each IPv4 address consists of a network number, an optional
subnetwork number, and a host number. The network and subnetwork numbers together
are used for routing, and the host number is used to address an individual host within the
network or subnetwork.
Internet Protocol
version 6 (IPv6)
An update version of IPv4, which is designed by the Internet Engineering Task Force
(IETF) and is also called IP Next Generation (IPng). It is a new version of the Internet
Protocol. The difference between IPv6 and IPv4 is that an IPv4 address has 32 bits while
an IPv6 address has 128 bits.
indicator Description of a performance feature collected from the managed devices by the
performance collector.
integrated circuit (IC) A combination of inseparable associated circuit elements that are formed in place and
interconnected on or within a single base material to perform a microcircuit function.
OptiX OSN 8800/6800/3800
310
intelligent power
adjustment (IPA)
A technology that reduces the optical power of all the amplifiers in an adjacent
regeneration section in the upstream to a safe level if the system detects the loss of optical
signals on the link. IPA helps ensure that maintenance engineers are not injured by the
laser escaping from a broken fiber or a connector that is not plugged in properly.
intersecting ring More than two public nodes between two ring networks. The network is more complex
if there are many intersecting nodes. Most devices support that two rings are intersected
at two nodes.
inverse multiplexing
over ATM (IMA)
A technique that involves inverse multiplexing and de-multiplexing of ATM cells in a
cyclical fashion among links grouped to form a higher bandwidth logical link whose rate
is approximately the sum of the link rates.
J
jitter The measure of short waveform variations caused by vibration, voltage fluctuations, and
control system instability.
jumper A connection wire for connecting two pins.
L
L2 switching The switching based on the data link layer.
L2VPN Layer 2 virtual private network
L3VPN Layer 3 virtual private network
LACP See Link Aggregation Control Protocol.
LAG See link aggregation group.
LAN See local area network.
LAPD link access procedure on the D channel
LB See loopback.
LC Lucent connector
LCAS See link capacity adjustment scheme.
LCT local craft terminal
LDP Label Distribution Protocol
LED See light emitting diode.
LMP link management protocol
LOS See loss of signal.
LP logical port
LPT link-state pass through
LSP See label switched path.
LSR See label switching router.
LTC loss of tandem connection
OptiX OSN 8800/6800/3800
311
Layer 2 switching A data forwarding method. In a LAN, a network bridge or 802.3 Ethernet switch
transmits and distributes packet data based on the MAC address. Since the MAC address
is at the second layer of the OSI model, this data forwarding method is called Layer 2
switching.
Link Aggregation
Control Protocol
(LACP)
A dynamic link aggregation protocol that improves the transmission speed and
reliability. The two ends of the link send LACP packets to inform each other of their
parameters and form a logical aggregation link. After the aggregation link is formed,
LACP maintains the link status in real time and dynamically adjusts the ports on the
aggregation link upon detecting the failure of a physical port.
label A short identifier that is of fixed length and local significance. It is used to uniquely
identify the FEC to which a packet belongs. It does not contain topology information. It
is carried in the header of a packet and does not contain topology information.
label switched path
(LSP)
A sequence of hops (R0...Rn) in which a packet travels from R0 to Rn through label
switching mechanisms. A label-switched path can be chosen dynamically, based on
common routing mechanisms or through configuration.
label switching router
(LSR)
Basic element of an MPLS network. All LSRs support the MPLS protocol. The LSR is
composed of two parts: control unit and forwarding unit. The former is responsible for
allocating the label, selecting the route, creating the label forwarding table, creating and
removing the label switch path; the latter forwards the labels according to groups
received in the label forwarding table.
light emitting diode
(LED)
A display and lighting technology used in almost every electrical and electronic product
on the market, from a tiny on/off light to digital readouts, flashlights, traffic lights, and
perimeter lighting. LEDs are also used as the light source in multimode fibers, optical
mice, and laser printers.
linear MSP linear multiplex section protection
link aggregation group
(LAG)
An aggregation that allows one or more links to be aggregated together to form a link
aggregation group so that a MAC client can treat the link aggregation group as if it were
a single link.
link capacity
adjustment scheme
(LCAS)
LCAS in the virtual concatenation source and sink adaptation functions provides a
control mechanism to hitless increase or decrease the capacity of a link to meet the
bandwidth needs of the application. It also provides a means of removing member links
that have experienced failure. The LCAS assumes that in cases of capacity initiation,
increases or decreases, the construction or destruction of the end-to-end path is the
responsibility of the network and element management systems.
link group According to some principles, links are divided into the set in the logical term. A set of
links is called the link group. The division makes management more convenient.
link status The running status of a link, which can be Up, Down, backup, or unknown.
loading A process of importing information from the storage device to the memory to facilitate
processing (when the information is data) or execution (when the information is
program).
local area network
(LAN)
A network formed by the computers and workstations within the coverage of a few square
kilometers or within a single building, featuring high speed and low error rate. Current
LANs are generally based on switched Ethernet or Wi-Fi technology and run at 1,000
Mbit/s (that is, 1 Gbit/s).
OptiX OSN 8800/6800/3800
312
loopback (LB) A troubleshooting technique that returns a transmitted signal to its source so that the
signal or message can be analyzed for errors. The loopback can be a inloop or outloop.
loopback test Self-test of chips, including internal and external loopback. Loopback test is used to test
whether interfaces work normally.
loss of signal (LOS) No transitions occurring in the received signal.
M
MAC mandatory access control
MAC address A link layer address or physical address. It is six bytes long.
MADM multiple add/drop multiplexer
MCA multi-channel spectrum analyzer unit
MD5 See message digest algorithm 5.
MFAS See multiframe alignment signal.
MIP maintenance association intermediate point
MPLS See Multiprotocol Label Switching.
MPLS TE multiprotocol label switching traffic engineering
MPLS VPN See multiprotocol label switching virtual private network.
MPLS-TP See MultiProtocol Label Switching Transport Profile.
MS multiplex section
MSOH multiplex section overhead
MSP See multiplex section protection.
MSTP See Multiple Spanning Tree Protocol.
MTU See maximum transmission unit.
MUX See multiplexer.
MultiProtocol Label
Switching Transport
Profile (MPLS-TP)
An extension to MPLS in terms of forwarding, OAM, reliability, NMS and control plane
protocol standardized by IETF to provide sufficient transport functionality.
Multiple Spanning
Tree Protocol (MSTP)
A protocol that can be used in a loop network. Using an algorithm, the MSTP blocks
redundant paths so that the loop network can be trimmed as a tree network. In this case,
the proliferation and endless cycling of packets is avoided in the loop network. The
protocol that introduces the mapping between VLANs and multiple spanning trees. This
solves the problem that data cannot be normally forwarded in a VLAN because in STP/
RSTP, only one spanning tree corresponds to all the VLANs.
Multiprotocol Label
Switching (MPLS)
A technology that uses short tags of fixed length to encapsulate packets in different link
layers, and provides connection-oriented switching for the network layer on the basis of
IP routing and control protocols.
OptiX OSN 8800/6800/3800
313
main topology A basic component of a human-machine interface. It is the default client interface of the
NMS and intuitively displays the structure of a network, NEs on the network, subnets in
the network as well as the NE communication and running status, reflecting the overall
network running status.
management node A management node consists of multiple document security management(DSM) servers
(four at most) in an area. Management nodes are created so that the DSM management
center can synchronize the department and account information of areas from each node
and then deliver all information to all nodes, thus realizing across-system authorization
and roaming access of security documents.
maximum transmission
unit (MTU)
The largest packet of data that can be transmitted on a network. MTU size varies,
depending on the network576 bytes on X.25 networks, for example, 1500 bytes on
Ethernet, and 17,914 bytes on 16 Mbit/s token ring. Responsibility for determining the
size of the MTU lies with the link layer of the network. When packets are transmitted
across networks, the path MTU, or PMTU, represents the smallest packet size (the one
that all networks can transmit without breaking up the packet) among the networks
involved.
member A basic element for forming a dimension according to the hierarchy of each level. Each
member represents a data element in a dimension. For example, January 1997 is a typical
member of the time dimension.
message digest
algorithm 5 (MD5)
A hash function that is used in a variety of security applications to check message
integrity. MD5 processes a variable-length message into a fixed-length output of 128
bits. It breaks up an input message into 512-bit blocks (sixteen 32-bit little-endian
integers). After a series of processing, the output consists of four 32-bit words, which
are then cascaded into a 128-bit hash number.
monitoring A method that an inspector uses to inspect a service agent. By monitoring a service agent,
an inspector can check each detailed operation performed by the service agent during
the conversation and operate the GUI used by the service agent. The inspector helps the
service agent to provide better service.
mounting ear A piece of angle plate on a rack. The mounting ear has holes that can be used to fix
network elements or components.
multicast A process of transmitting data packets from one source to many destinations. The
destination address of the multicast packet uses Class D address, that is, the IP address
ranges from 224.0.0.0 to 239.255.255.255. Each multicast address represents a multicast
group rather than a host.
multiframe alignment
signal (MFAS)
A distinctive signal inserted into every multiframe or once into every n multiframes,
always occupying the same relative position within the multiframe, and used to establish
and maintain multiframe alignment.
multiplex section
protection (MSP)
A function, which is performed to provide capability for switching a signal between and
including two multiplex section termination (MST) functions, from a "working" to a
"protection" channel.
multiplexer (MUX) Equipment that combines a number of tributary channels onto a fewer number of
aggregate bearer channels, the relationship between the tributary and aggregate channels
being fixed.
OptiX OSN 8800/6800/3800
314
multiplexing A procedure by which multiple lower order path layer signals are adapted into a higher
order path or the multiple higher order path layer signals are adapted into a multiplex
section.
multiprotocol label
switching virtual
private network
(MPLS VPN)
An Internet Protocol (IP) virtual private network (VPN) based on the multiprotocol label
switching (MPLS) technology. It applies the MPLS technology for network routers and
switches, simplifies the routing mode of core routers, and combines traditional routing
technology and label switching technology. It can be used to construct the broadband
Intranet and Extranet to meet various service requirements.
N
NE Explorer The main operation interface of the NMS, which is used to manage the
telecommunication equipment. In the NE Explorer, a user can query, manage, and
maintain NEs, boards, and ports.
NE ID An ID that indicates a managed device in the network. In the network, each NE has a
unique NE ID.
NE Panel A graphical user interface, of the network management system, which displays subracks,
boards, and ports on an NE. On the NE Panel, the user can complete most of the
configuration, management and maintenance functions for an NE.
NNI network node interface
NRZ non-return to zero
NSAP See network service access point.
NTP Network Time Protocol
network layer Layer 3 of the seven-layer OSI model of computer networking. The network layer
provides routing and addressing so that two terminal systems are interconnected. In
addition, the network layer provides congestion control and traffic control. In the TCP/
IP protocol suite, the functions of the network layer are specified and implemented by
IP protocols. Therefore, the network layer is also called IP layer.
network service A service that needs to be enabled at the network layer and maintained as a basic service.
network service access
point (NSAP)
A network address defined by ISO, at which the OSI Network Service is made available
to a Network service user by the Network service provider.
network storm A phenomenon that occurs during data communication. To be specific, mass broadcast
packets are transmitted in a short time; the network is congested; transmission quality
and availability of the network decrease rapidly. The network storm is caused by network
connection or configuration problems.
O
O&M operation and maintenance
OA optical amplifier
OADM See optical add/drop multiplexer.
OAM See operation, administration and maintenance.
OAMS Optical fiber line Automatic Monitoring System
OptiX OSN 8800/6800/3800
315
OAU See optical amplifier unit.
OC ordinary clock
OC-3 optical carrier level 3
OCP optical channel protection
OCS optical core switching
OCh optical channel with full functionality
OD optical demultiplexing
ODB optical duobinary
ODF optical distribution frame
ODUk optical channel data unit - k
OEQ optical equalizer
OLA optical line amplifier
OLP See optical line protection.
OM optical multiplexing
OMS optical multiplexing section
ONT See optical network terminal.
ONU See optical network unit.
OPA optical power adjust
OPU See optical channel payload unit.
OPUk optical channel payload unit - k
OSC See optical supervisory channel.
OSI open systems interconnection
OSN optical switch node
OSNR See optical signal-to-noise ratio.
OSPF See Open Shortest Path First.
OTM optical terminal multiplexer
OTN optical transport network
OTS See optical transmission section.
OTU See optical transponder unit.
OTUk optical channel transport unit - k
OWSP optical wavelength shared protection
Open Shortest Path
First (OSPF)
A link-state, hierarchical interior gateway protocol (IGP) for network routing that uses
cost as its routing metric. A link state database is constructed of the network topology,
which is identical on all routers in the area.
OptiX OSN 8800/6800/3800
316
operation,
administration and
maintenance (OAM)
A set of network management functions that cover fault detection, notification, location,
and repair.
optical add/drop
multiplexer (OADM)
A device that can be used to add the optical signals of various wavelengths to one channel
and drop the optical signals of various wavelengths from one channel.
optical amplifier unit
(OAU)
A board that is mainly responsible for amplifying optical signals. The OAU can be used
in both the transmitting direction and the receiving direction.
optical channel payload
unit (OPU)
A protection architecture that allows one wavelength to provide protection for multiple
services between different stations, saving wavelength resources and lowering costs.
optical interface A component that connects several transmit or receive units.
optical line protection
(OLP)
A mechanism that protects line signals using the dual feeding and selective receiving
principle, featuring single-ended switching.
optical network
terminal (ONT)
A device that terminates the fiber optical network at the customer premises.
optical network unit
(ONU)
A form of Access Node that converts optical signals transmitted via fiber to electrical
signals that can be transmitted via coaxial cable or twisted pair copper wiring to
individual subscribers.
optical signal-to-noise
ratio (OSNR)
The ratio of signal power to noise power in a transmission link. OSNR is the most
important index for measuring the performance of a DWDM system.
optical supervisory
channel (OSC)
A technology that uses specific optical wavelengths to realize communication among
nodes in optical transmission network and transmit the monitoring data in a certain
channel.
optical switch A passive component possessing two or more ports that selectively transmits, redirects,
or blocks optical power in an optical fiber transmission line.
optical transmission
section (OTS)
A section in the logical structure of an optical transport network (OTN). The OTS allows
the network operator to perform monitoring and maintenance tasks between NEs.
optical transponder
unit (OTU)
A device or subsystem that converts accessed client signals into a G.694.1/G.694.2-
compliant WDM wavelength.
orderwire A channel that provides voice communication between operation engineers or
maintenance engineers of different stations.
P
P2MP point-to-multipoint
P2P See point-to-point service.
PC personal computer
PCB See printed circuit board.
PCN product change notice
PDH See plesiochronous digital hierarchy.
PDL See polarization-dependent loss.
PDU See power distribution unit.
OptiX OSN 8800/6800/3800
317
PE See provider edge.
PGND cable A cable which connects the equipment and the protection grounding bar. Usually, one
half of the cable is yellow, whereas the other half is green.
PHB See per-hop behavior.
PID photonics integrated device
PIN See personal identification number.
PM performance monitoring
PMD polarization mode dispersion
PMU power monitoring unit
POS See packet over SDH/SONET.
POTS See plain old telephone service.
PPP Point-to-Point Protocol
PRBS See pseudo random binary sequence.
PSI payload structure identifier
PSN See packet switched network.
PT payload type
PTN packet transport network
PTP Precision Time Protocol
PVC permanent virtual channel
PW See pseudo wire.
PWE3 See pseudo wire emulation edge-to-edge.
packet loss The discarding of data packets in a network when a device is overloaded and cannot
accept any incoming data at a given moment.
packet over SDH/
SONET (POS)
A MAN and WAN technology that provides point-to-point data connections. The POS
interface uses SDH/SONET as the physical layer protocol, and supports the transport of
packet data (such as IP packets) in MAN and WAN.
packet switched
network (PSN)
A telecommunications network that works in packet switching mode.
packet switching A network technology in which information is transmitted by means of exchanging
packets and the bandwidth of a channel can be shared by multiple connections.
paired slots Two slots of which the overheads can be passed through by using the bus on the
backplane.
per-hop behavior
(PHB)
IETF Diff-Serv workgroup defines forwarding behaviors of network nodes as per-hop
behaviors (PHB), such as, traffic scheduling and policing. A device in the network should
select the proper PHB behaviors, based on the value of DSCP. At present, the IETF
defines four types of PHB. They are class selector (CS), expedited forwarding (EF),
assured forwarding (AF), and best-effort (BE).
personal identification
number (PIN)
A code used by a mobile user in conjunction with a SIM card to complete a call.
OptiX OSN 8800/6800/3800
318
phase The relative position in time within a single period of a signal.
physical layer Layer 1 in the Open System Interconnection (OSI) architecture; the layer that provides
services to transmit bits or groups of bits over a transmission link between open systems
and which entails electrical, mechanical and handshaking.
physical link The link between two physical network elements (NEs). When the user creates NEs or
refreshes the device status, the system automatically creates the physical link according
to the topology structure information on the device. The remark information of a physical
link can be modified, but the physical link cannot be deleted.
plain old telephone
service (POTS)
The basic telephone service provided through the traditional cabling such as twisted pair
cables.
plesiochronous digital
hierarchy (PDH)
A multiplexing scheme of bit stuffing and byte interleaving. It multiplexes the minimum
rate 64 kit/s into rates of 2 Mbit/s, 34 Mbit/s, 140 Mbit/s, and 565 Mbit/s.
point-to-point service
(P2P)
A service between two terminal users. In P2P services, senders and recipients are
terminal users.
polarization-dependent
loss (PDL)
A measure of the peak-to-peak insertion loss or gain variation caused by a component
when stimulated by all possible polarization states. PDL is specified in dB.
policy A set of rules that are applied when the conditions for triggering an event are met.
port priority The priority that is used when a port attaches tags to Layer 2 packets. Packets received
on ports with higher priorities are forwarded preferentially.
power box A direct current power distribution box at the upper part of a cabinet, which supplies
power for the subracks in the cabinet.
power distribution unit
(PDU)
A unit that performs AC or DC power distribution.
power module The module that converts the external power input into the power supply for internal
use. Power modules are classified into AC power modules and DC power modules.
power on To start up a computer; to begin a cold boot procedure; to turn on the power
printed circuit board
(PCB)
A board used to mechanically support and electrically connect electronic components
using conductive pathways, tracks, or traces, etched from copper sheets laminated onto
a non-conductive substrate.
private line A line, such as a subscriber cable and trunk cable, which are leased by the
telecommunication carrier and are used to meet the special user requirements.
protection path A path in a protection group that transports services when a fault occurs on the working
path.
protection service A specific service that is part of a protection group and is labeled protection.
provider edge (PE) A device that is located in the backbone network of the MPLS VPN structure. A PE is
responsible for managing VPN users, establishing LSPs between PEs, and exchanging
routing information between sites of the same VPN. A PE performs the mapping and
forwarding of packets between the private network and the public channel. A PE can be
a UPE, an SPE, or an NPE.
pseudo random binary
sequence (PRBS)
A sequence that is random in the sense that the value of each element is independent of
the values of any of the other elements, similar to a real random sequence.
OptiX OSN 8800/6800/3800
319
pseudo wire (PW) An emulated connection between two PEs for transmitting frames. The PW is established
and maintained by PEs through signaling protocols. The status information of a PW is
maintained by the two end PEs of a PW.
pseudo wire emulation
edge-to-edge (PWE3)
An end-to-end Layer 2 transmission technology. It emulates the essential attributes of a
telecommunication service such as ATM, FR or Ethernet in a packet switched network
(PSN). PWE3 also emulates the essential attributes of low speed time division
multiplexing (TDM) circuit and SONET/SDH. The simulation approximates to the real
situation.
pulse A variation above or below a normal level and a given duration in electrical energy.
Q
QinQ A layer 2 tunnel protocol based on IEEE 802.1Q encapsulation. It add a public VLAN
tag to a frame with a private VLAN tag to allow the frame with double VLAN tags to
be transmitted over the service provider's backbone network based on the public VLAN
tag. This provides a layer 2 VPN tunnel for customers and enables transparent
transmission of packets over private VLANs.
QoS See quality of service.
quality of service (QoS) A commonly-used performance indicator of a telecommunication system or channel.
Depending on the specific system and service, it may relate to jitter, delay, packet loss
ratio, bit error ratio, and signal-to-noise ratio. It functions to measure the quality of the
transmission system and the effectiveness of the services, as well as the capability of a
service provider to meet the demands of users.
R
RADIUS See Remote Authentication Dial In User Service.
RADIUS
authentication
An authentication mode in which the BRAS sends the user name and the password to
the RADIUS server by using the RADIUS protocol. The RADIUS server authenticates
the user, and then returns the result to the BRAS.
RB See radio bearer.
RDI remote defect indication
RFC See Request For Comments.
RJ registered jack
RMON See remote monitor.
ROADM reconfigurable optical add/drop multiplexer
RSTP See Rapid Spanning Tree Protocol.
RSVP See Resource Reservation Protocol.
RTN radio transmission node
RZ return to zero
Rapid Spanning Tree
Protocol (RSTP)
An evolution of the Spanning Tree Protocol (STP) that provides faster spanning tree
convergence after a topology change. The RSTP protocol is backward compatible with
the STP protocol.
OptiX OSN 8800/6800/3800
320
Remote Authentication
Dial In User Service
(RADIUS)
A security service that authenticates and authorizes dial-up users and is a centralized
access control mechanism. RADIUS uses the User Datagram Protocol (UDP) as its
transmission protocol to ensure real-time quality. RADIUS also supports the
retransmission and multi-server mechanisms to ensure good reliability.
Request For Comments
(RFC)
A document in which a standard, a protocol, or other information pertaining to the
operation of the Internet is published. The RFC is actually issued, under the control of
the IAB, after discussion and serves as the standard. RFCs can be obtained from sources
such as InterNIC.
Resource Reservation
Protocol (RSVP)
A protocol that reserves resources on every node along a path. RSVP is designed for an
integrated services Internet.
radio bearer (RB) The service provided by the Layer 2 for the transfer of user data between UE (User
Equipment) and UTRAN (UMTS Terrestrial Radio Access Network).
reboot To start the system again. Programs or data will be reloaded to all boards.
receiver sensitivity The minimum acceptable value of mean received power at point Rn (a reference point
at an input to a receiver optical connector) to achieve a 1x10-12 BER when the FEC is
enabled.
regeneration The process of receiving and reconstructing a digital signal so that the amplitudes,
waveforms and timing of its signal elements are constrained within specified limits.
remote monitor
(RMON)
A widely used network management standard defined by the IETF, and it enhances the
MIB II standard greatly. It is mainly used to monitor the data traffic over a network
segment or the entire network. RMON is completely based on the SNMP architecture,
including the NMS and the Agent running on each network device.
report A tool that displays data in a specific format to intuitively present service information.
resistance The ability to impede (resist) the flow of electric current. With the exception of
superconductors, all substances have a greater or lesser degree of resistance. Substances
with very low resistance, such as metals, conduct electricity well and are called
conductors. Substances with very high resistance, such as glass and rubber, conduct
electricity poorly and are called nonconductors or insulators.
response A message that is returned to the requester to notify the requester of the status of the
request packet.
router A device on the network layer that selects routes in the network. The router selects the
optimal route according to the destination address of the received packet through a
network and forwards the packet to the next router. The last router is responsible for
sending the packet to the destination host. Can be used to connect a LAN to a LAN, a
WAN to a WAN, or a LAN to the Internet.
routing The determination of a path that a data unit (frame, packet, message) traverses from
source to destination.
routing table A table that stores and updates the locations (addresses) of network devices. Routers
regularly share routing table information to be up to date. A router relies on the
destination address and on the information in the table that gives the possible routes--in
hops or in number of jumps--between itself, intervening routers, and the destination.
Routing tables are updated frequently as new information is available.
OptiX OSN 8800/6800/3800
321
rule Rules define automatic management services or applications. Rules include triggering
conditions and execution logic. Triggering conditions refer to the conditions for
executing a rule and execution logic refers to a set of actions executed based on the rule.
S
S-VLAN service virtual local area network
SAN storage area network
SAPI source access point identifier
SD See signal degrade.
SD-SDI See standard definition-serial digital interface signal.
SDH See synchronous digital hierarchy.
SDI See serial digital interface.
SES severely errored second
SESR severely errored second ratio
SETS SDH equipment timing source
SF See signal fail.
SFP small form-factor pluggable
SFTP See Secure File Transfer Protocol.
SHDSL See single-pair high-speed digital subscriber line.
SLA See service level agreement.
SLM signaling link management
SM section monitoring
SMF See single-mode fiber.
SNC subnetwork connection
SNCP subnetwork connection protection
SNCTP subnetwork connection tunnel protection
SNMP See Simple Network Management Protocol.
SONET See synchronous optical network.
SPC soft permanent connection
SRG See shared risk group.
SRLG shared risk link group
SSL See Secure Sockets Layer.
SSM See Synchronization Status Message.
STI service trigger information
STM synchronous transfer mode
STM-1 See Synchronous Transport Module level 1.
OptiX OSN 8800/6800/3800
322
STM-16 Synchronous Transport Module level 16
STM-4 Synchronous Transport Module level 4
STM-N Synchronous Transport Module level N
STP Spanning Tree Protocol
STS synchronous transport signal
Secure File Transfer
Protocol (SFTP)
A network protocol designed to provide secure file transfer over SSH.
Secure Sockets Layer
(SSL)
A security protocol that works at a socket level. This layer exists between the TCP layer
and the application layer to encrypt/decode data and authenticate concerned entities.
Simple Network
Management Protocol
(SNMP)
A network management protocol of TCP/IP. It enables remote users to view and modify
the management information of a network element. This protocol ensures the
transmission of management information between any two points. The polling
mechanism is adopted to provide basic function sets. According to SNMP, agents, which
can be hardware as well as software, can monitor the activities of various devices on the
network and report these activities to the network console workstation. Control
information about each device is maintained by a management information block.
Synchronization Status
Message (SSM)
A message that carries the quality levels of timing signals on a synchronous timing link.
SSM messages provide upstream clock information to nodes on an SDH network or
synchronization network.
Synchronous
Transport Module level
1 (STM-1)
Synchronous transfer mode at 155 Mbit/s.
security Protection of a computer system and its data from harm or loss. A major focus of
computer security, especially on systems accessed by many people or through
communication lines, is preventing system access by unauthorized individuals.
serial digital interface
(SDI)
An interface that transmits data in a single channel in sequence.
serial port An input/output location (channel) that sends and receives data to and from a computer's
CPU or a communications device one bit at a time. Serial ports are used for serial data
communication and as interfaces with some peripheral devices, such as mice and printers.
service data The user and/or network information required for the normal functioning of services.
service level The level of service quality of an evaluated party in a specified period, determined by
an evaluating party.
service level agreement
(SLA)
A service agreement between a customer and a service provider. SLA specifies the
service level for a customer. The customer can be a user organization (source domain)
or another differentiated services domain (upstream domain). An SLA may include
traffic conditioning rules which constitute a traffic conditioning agreement as a whole
or partially.
service protection A measure that ensures that services can be received at the receive end.
shared risk group
(SRG)
A group of resources that share a common risk component whose failure can cause the
failure of all the resources in the group.
OptiX OSN 8800/6800/3800
323
signal degrade (SD) A signal indicating that associated data has degraded in the sense that a degraded defect
condition is active.
signal fail (SF) A signal indicating that associated data has failed in the sense that a near-end defect
condition (non-degrade defect) is active.
single-ended switching A protection mechanism that takes switching action only at the affected end of the
protected entity in the case of a unidirectional failure.
single-mode fiber
(SMF)
A type of optical fiber through which only one type of optical signal with a fixed wave
length can travel at a time. The inner diameter of the single-mode fiber is less than 10
microns. This type of fiber can transmit data over a long distance.
single-pair high-speed
digital subscriber line
(SHDSL)
A symmetric digital subscriber line technology developed from HDSL, SDSL, and
HDSL2, which is defined in ITU-T G.991.2. The SHDSL port is connected to the user
terminal through the plain telephone subscriber line and uses trellis coded pulse
amplitude modulation (TC-PAM) technology to transmit high-speed data and provide
the broadband access service.
smooth upgrade Process of upgrading the system files without service interruption
span The physical reach between two pieces of WDM equipment.
standard definition-
serial digital interface
signal (SD-SDI)
Standard definition video signal transported by serial digital interface.
subnet A type of smaller networks that form a larger network according to a rule, for example,
according to different districts. This facilitates the management of the large network.
synchronous digital
hierarchy (SDH)
A transmission scheme that follows ITU-T G.707, G.708, and G.709. SDH defines the
transmission features of digital signals, such as frame structure, multiplexing mode,
transmission rate level, and interface code. SDH is an important part of ISDN and B-
ISDN.
synchronous optical
network (SONET)
A high-speed network that provides a standard interface for communications carriers to
connect networks based on fiber optical cable. SONET is designed to handle multiple
data types (voice, video, and so on). It transmits at a base rate of 51.84 Mbit/s, but
multiples of this base rate go as high as 2.488 Gbit/s.
T
TCM tandem connection monitor
TCP See Transmission Control Protocol.
TCP/IP Transmission Control Protocol/Internet Protocol
TD transmit degrade
TDC tunable dispersion compensator
TDM See time division multiplexing.
TF transport format
TFTP See Trivial File Transfer Protocol.
TIM trail trace identifier mismatch
TL1 Transaction Language 1
OptiX OSN 8800/6800/3800
324
TM See terminal multiplexer.
TMN See telecommunications management network.
TSC test system controller
TTI trail trace identifier
TX transmit
Transmission Control
Protocol (TCP)
The protocol within TCP/IP that governs the breakup of data messages into packets to
be sent using Internet Protocol (IP), and the reassembly and verification of the complete
messages from packets received by IP. A connection-oriented, reliable protocol (reliable
in the sense of ensuring error-free delivery), TCP corresponds to the transport layer in
the ISO/OSI reference model.
Trivial File Transfer
Protocol (TFTP)
A small and simple alternative to FTP for transferring files. TFTP is intended for
applications that do not need complex interactions between the client and server. TFTP
restricts operations to simple file transfers and does not provide authentication.
tangent ring A concept borrowed from geometry. Two tangent rings have a common node between
them. The common node often leads to single-point failures.
telecommunications
management network
(TMN)
A protocol model defined by ITU-T for managing open systems in a communications
network. TMN manages the planning, provisioning, installation, and OAM of
equipment, networks, and services.
terminal multiplexer
(TM)
A device used at a network terminal either to multiplex multiple channels of low rate
signals into one channel of high rate signals, or to demultiplex one channel of high rate
signals into multiple channels of low rate signals.
threshold A limitation on an amount, scale, or level. Changes will occur when a threshold is
reached.
time division
multiplexing (TDM)
A multiplexing technology. TDM divides the sampling cycle of a channel into time slots
(TSn, n=0, 1, 2, 3), and the sampling value codes of multiple signals engross time slots
in a certain order, forming multiple multiplexing digital signals to be transmitted over
one channel.
tolerance Permissible degree of variation from a pre-set standard.
topology view A basic component for the man-machine interface. The topology view directly displays
the networking of a network as well as the alarm and communication status of each
network element and subnet. The topology view reflects the basic running conditions of
the network.
transmission delay The period from the time when a site starts to transmit a data frame to the time when the
site finishes the data frame transmission. It consists of the transmission latency and the
equipment forwarding latency.
transparent
transmission
A process during which the signaling protocol or data is not processed in the content but
encapsulated in the format for the processing of the next phase.
tunnel A channel on the packet switching network that transmits service traffic between PEs.
In VPN, a tunnel is an information transmission channel between two entities. The tunnel
ensures secure and transparent transmission of VPN information. In most cases, a tunnel
is an MPLS tunnel.
U
OptiX OSN 8800/6800/3800
325
UAT See unavailable time event.
UNI See user-to-network interface.
UPI user payload identifier
UPM uninterruptible power module
unavailable time event
(UAT)
An event that is reported when the monitored object generates 10 consecutive severely
errored seconds.
unicast The process of sending data from a source to a single recipient.
unprotected Pertaining to the transmission of services that are not protected. Unprotected services
cannot be switched to the protection channel if the working channel is faulty or the service
is interrupted, because protection is not configured.
user-to-network
interface (UNI)
The interface between user equipment and private or public network equipment (for
example, ATM switches).
V
V-UNI See virtual user-network interface.
VB virtual bridge
VBR See variable bit rate.
VC See virtual container.
VCPLM virtual concatenation payload mismatch
VCTRUNK A virtual concatenation group applied in data service mapping, also called the internal
port of a data service processing board.
VDSL2 See very-high-speed digital subscriber line 2.
VLAN virtual local area network
VOA variable optical attenuator
VPLS See virtual private LAN service.
VPN virtual private network
VPWS See virtual private wire service.
VRRP See Virtual Router Redundancy Protocol.
VSI See virtual switching instance.
Virtual Router
Redundancy Protocol
(VRRP)
A protocol designed for multicast or broadcast LANs such as an Ethernet. A group of
routers (including an active router and several backup routers) in a LAN is regarded as
a virtual router, which is called a backup group. The virtual router has its own IP address.
The host in the network communicates with other networks through this virtual router.
If the active router in the backup group fails, one of the backup routers in this backup
group becomes active and provides routing service for the host in the network.
variable bit rate (VBR) One of the traffic classes used by ATM (Asynchronous Transfer Mode). Unlike a
permanent CBR (Constant Bit Rate) channel, a VBR data stream varies in bandwidth
and is better suited to non real time transfers than to real-time streams such as voice calls.
OptiX OSN 8800/6800/3800
326
very-high-speed digital
subscriber line 2
(VDSL2)
An extension of the VDSL technology, which complies with ITU G.993.2, supports
multiple spectrum profiles and encapsulation modes, and provides short-distance and
high-speed access solutions to the next-generation FTTx access service.
view The topological view that is presented in some rules. Customize the view according to
requirements of every product and organize the data in the view displayed by the topology
module. By default, the platform provides the physical view. The topology view can be
planned according to the domain, maintenance relationship and so on.
virtual container (VC) An information structure used to support path layer connections in the SDH. A VC
consists of a payload and path overhead (POH), which are organized in a block frame
structure that repeats every 125 s or 500 s.
virtual private LAN
service (VPLS)
A type of point-to-multipoint L2VPN service provided over the public network. VPLS
enables geographically isolated user sites to communicate with each other through the
MAN/WAN as if they are on the same LAN.
virtual private wire
service (VPWS)
A technology that bears Layer 2 services. VPWS emulates services such as ATM, FR,
Ethernet, low-speed TDM circuit, and SONET/SDH in a PSN.
virtual switching
instance (VSI)
An instance through which the physical access links of VPLS can be mapped to the
virtual links. Each VSI provides independent VPLS service. VSI has Ethernet bridge
function and can terminate PW.
virtual user-network
interface (V-UNI)
A virtual user-network interface, works as an action point to perform service
classification and traffic control in HQoS.
W
WAN wide area network
WDM wavelength division multiplexing
WLAN See wireless local area network.
WSS wavelength selective switching
Web LCT The local maintenance terminal of a transport network, which is located at the NE
management layer of the transport network.
wireless local area
network (WLAN)
A hybrid of the computer network and the wireless communication technology. It uses
wireless multiple address channels as transmission media and carriers out data interaction
through electromagnetic wave to implement the functions of the traditional LAN.
working service A specific service that is part of a protection group and is labeled working.
X
XCS cross-connect and synchronous timing board
Y
OptiX OSN 8800/6800/3800
327
Y.1731 The OAM protocol introduced by the ITU-T. Besides the contents defined by
IEEE802.1ag, ITU-T Recommendation Y.173 also defines the following combined
OAM messages: Alarm Indication Signal (AIS), Remote Defect Indication (RDI),
Locked Signal (LCK), Test Signal, Automatic Protection Switching (APS), Maintenance
Communication Channel (MCC), Experimental (EXP), and Vendor Specific (VSP) for
fault management and performance monitoring, such as frame loss measurement (LM),
and delay measurement (DM).
OptiX OSN 8800/6800/3800
328

OptiX OSN 8800 6800 3800 Troubleshooting (V100R007)

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

OptiX OSN 8800 6800 3800 Troubleshooting (V100R007)

Încărcat de

Drepturi de autor:

Formate disponibile

OptiX OSN 8800/6800/3800

S-ar putea să vă placă și