OptiX OSN 3500 Troubleshooting (V100R008)

00384241
OptiX OSN 3500 Intelligent Optical Transmission

System
V100R008
Troubleshooting
Issue 04
Date 2010-11-30
HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2010. 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 the 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 04 (2010-11-30) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
i
About This Document
Purpose
Based on various services of the OptiX OSN 3500, this document describes the troubleshooting
process, which involves background knowledge, information collection, general processing
flow, common troubleshooting methods, and case study.
Related Versions
The following table lists the product versions related to this document.
Product Name Version
OptiX OSN 3500 V100R008
iManager U2000 V100R001C00

Intended Audience
The intended audiences of this document are:
l Field maintenance engineer
l System maintenance engineer
Organization
This document consists of eight chapters and is organized as follows.
OptiX OSN 3500 Intelligent Optical Transmission System
Troubleshooting About This Document
iii
Chapter Description
General Model and Methods of Fault Locating This chapter describes the
operation of troubleshooting and
the common methods used in
respective procedures.
Fault Handling Flow This chapter describes the fault
handling flow and how to
recover service when the service
is interrupted.
3 Emergency Handling Flow These chapters describe the
methods and procedures for
troubleshooting, and provide
typical cases.
4 Troubleshooting Service Interruption
5 Troubleshooting Bit Errors
6 Troubleshooting the Pointer Justification
Troubleshooting Equipment Interconnection Faults
8 Troubleshooting Multiplex Section Protection
Switching Faults
9 Troubleshooting SNCP Switching Faults
10 Troubleshooting Clock Protection Switching Fault
11 Troubleshooting Tributary Protection Switching
Fault
12 Troubleshooting ECC Faults
13 Troubleshooting Orderwire Fault
14 Ethernet Troubleshooting
15 Handling of ATM/IMA Faults
16 Remote Maintenance Guide This chapter describes the
remote maintenance.
Glossary This chapter lists the terms used
in this document.

Conventions
Symbol Conventions
The following symbols may be found in this document. They are defined as follows.
About This Document
Troubleshooting
iv Huawei Proprietary and Confidential
Issue 04 (2010-11-30)
Symbol Description
DANGER
Indicates a hazard with a high level of risk which, if not
avoided, will result in death or serious injury.
WARNING
Indicates a hazard with a medium or low level of risk which,
if not avoided, could result in minor or moderate injury.
CAUTION
Indicates a potentially hazardous situation that, if not
avoided, could cause equipment damage, data loss, and
performance degradation, or unexpected results.
TIP
Indicates a tip that may help you solve a problem or save
your time.
NOTE
Provides additional information to emphasize or
supplement important points of the main text.

General Conventions
Convention Description
Times New Roman Normal paragraphs are in Times New Roman.
Boldface Names of files, directories, folders, and users are in boldface. For
example, log in as user root.
Italic Book titles are in italics.
Courier New Terminal display is in Courier New.

Command Conventions
Boldface The keywords of a command line are in boldface.
Italic Command arguments are in italic.
[ ] Items (keywords or arguments) in square brackets [ ] are
optional.
{ x | y | ... } Alternative items are grouped in braces and separated by
vertical bars. One is selected.
[ x | y | ... ] Optional alternative items are grouped in square brackets
and separated by vertical bars. One or none is selected.
{ x | y | ... } * Alternative items are grouped in braces and separated by
vertical bars. A minimum of one or a maximum of all can
be selected.
v

GUI Conventions
Boldface Buttons, menus, parameters, tabs, window, and dialog titles are in
boldface. For example, click OK.
> Multi-level menus are in boldface and separated by the ">" signs. For
example, choose File > Create > Folder.

Keyboard Operation
Format Description
Key Press the key. For example, press Enter and press Tab.
Key 1+Key 2 Press the keys concurrently. For example, pressingCtrl+Alt+A means the
three keys should be pressed concurrently.
Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A means the two keys
should be pressed in turn.

Mouse Operation
Action Description
Click Select and release the primary mouse button without moving the pointer.
Double-click Press the primary mouse button twice continuously and quickly without
moving the pointer.
Drag Press and hold the primary mouse button and move the pointer to a certain
position.

Update History
Updates between document issues are cumulative. Therefore, the latest issue contains all updates
made to previous issues.
Updates in Issue 04 (2010-11-30) Based on Product Version V100R008
This document is the fourth issue for V100R008. Compared with the third issue, this issue
contains the following updates:
l Section "Software Package Loading" is deleted.
About This Document
Troubleshooting
vi Huawei Proprietary and Confidential
Issue 04 (2010-11-30)
l Section "Package Diffusion" is deleted.
l Section "Hot Fix" is deleted.
This document is the third issue for V100R008. Compared with the second issue, this issue
contains the following update:
l The document structure is changed, and the troubleshooting information is provided by
scenario.
This document is the second issue for V100R008. Compared with the first issue, this issue
contains the following updates:
l The N2EGS4A boards are added.
l Section "Querying Working Temperature" is added.
l Section "Control of Power Consumption" is added.
l Section "Replacing Pluggable Optical Modules on Site" is added.
l Known issues are resolved.
This document is the first issue for V100R008. Compared with V100R007, this issue contains
the following updates:
l The related descriptions of new boards are added.
vii
Contents
About This Document...................................................................................................................iii
1 General Model and Methods of Fault Locating...................................................................1-1
1.1 Requirements for the Maintenance personnel.................................................................................................1-2
1.1.1 Professional Skills..................................................................................................................................1-2
1.1.2 Network Layout......................................................................................................................................1-3
1.1.3 Collecting and Storing On-site Data...................................................................................................... 1-4
1.2 Basic Principle of Locating Faults..................................................................................................................1-4
1.3 Common Methods of Locating Faults.............................................................................................................1-4
1.3.1 Alarm and Performance Event Analysis................................................................................................1-6
1.3.2 Loopback................................................................................................................................................1-8
1.3.3 Replacement.........................................................................................................................................1-11
1.3.4 Configuration Data Analysis................................................................................................................1-12
1.3.5 Configuration Modification..................................................................................................................1-12
1.3.6 PRBS Test............................................................................................................................................1-13
1.3.7 Meter Test............................................................................................................................................1-17
1.3.8 Comparison of Methods for Locating Faults.......................................................................................1-17
1.4 Some Classified Faults and Their Troubleshooting......................................................................................1-18
1.4.1 Handling External Faults .....................................................................................................................1-19
1.4.2 Locating the Fault to a Specific NE.....................................................................................................1-21
1.4.3 Locating a Fault to a Specific Board and Rectifying the Fault............................................................1-22
1.5 Terminology..................................................................................................................................................1-22
2 Fault Handling Flow..................................................................................................................2-1
2.1 General Flow...................................................................................................................................................2-2
2.1.1 Flow Chart..............................................................................................................................................2-2
2.1.2 Flow Description....................................................................................................................................2-3
2.2 Emergency Handling Flow..............................................................................................................................2-4
2.2.1 Flow Chart..............................................................................................................................................2-4
2.2.2 Flow Description....................................................................................................................................2-6
2.2.3 Information Collection and Record........................................................................................................2-7
2.2.4 Report and Technical Support................................................................................................................2-8
3 Emergency Handling Flow.......................................................................................................3-1
3.1 Flow Chart.......................................................................................................................................................3-3
Troubleshooting Contents
ix
3.2 Flow Description.............................................................................................................................................3-3
3.3 Troubleshooting Service Interruption.............................................................................................................3-5
3.4 Troubleshooting Multiplex Section Protection Switching Faults...................................................................3-6
3.5 Troubleshooting SNCP Switching Faults.......................................................................................................3-6
3.6 Troubleshooting Equipment Level Protection Switching Faults....................................................................3-6
3.7 Information Collection and Record.................................................................................................................3-6
3.8 Report and Technical Support.........................................................................................................................3-6
4 Troubleshooting Service Interruption...................................................................................4-1
4.1 Background Knowledge..................................................................................................................................4-2
4.1.1 Classification of Signal Flow.................................................................................................................4-2
4.1.2 Service Signal Flow...............................................................................................................................4-2
4.1.3 Alarm Signal Flow.................................................................................................................................4-4
4.1.4 Clock Signal Flow..................................................................................................................................4-4
4.2 Common Fault Causes....................................................................................................................................4-4
4.3 Fault Locating Flow........................................................................................................................................4-5
4.4 Methods of Fault Locating..............................................................................................................................4-8
4.4.1 Handling of Power Failure.....................................................................................................................4-8
4.4.2 Troubleshooting for Grounding.............................................................................................................4-9
4.4.3 Handling of Environment Abnormality...............................................................................................4-10
4.4.4 Handling of Abnormalities of Fiber, Cable, and Connector................................................................4-10
4.4.5 Checking Configuration Data...............................................................................................................4-11
4.4.6 Checking Misoperation .......................................................................................................................4-12
4.4.7 Checking Consistency of Board Models..............................................................................................4-12
4.4.8 Handling Hardware Faults of Equipment.............................................................................................4-12
4.5 Cases on Service Interruption.......................................................................................................................4-13
5 Troubleshooting Bit Errors.......................................................................................................5-1
5.2 Common Causes..............................................................................................................................................5-2
5.4 Methods for Fault Locating.............................................................................................................................5-5
5.4.1 Checking Optical Power.........................................................................................................................5-6
5.4.2 Checking Power Cable...........................................................................................................................5-6
5.4.3 Checking External Interference..............................................................................................................5-7
5.4.4 Checking the Grounding........................................................................................................................5-7
5.4.5 Checking Ambient Temperature............................................................................................................5-8
5.4.6 Equipment Causes..................................................................................................................................5-8
5.4.7 Checking Clock Configuration...............................................................................................................5-9
5.5 Cases on Bit Errors..........................................................................................................................................5-9
6 Troubleshooting the Pointer Justification.............................................................................6-1
6.1.1 Mechanism of Pointer Justification........................................................................................................6-2
Contents
Troubleshooting
x Huawei Proprietary and Confidential
Issue 04 (2010-11-30)
6.1.2 Detection Report of Pointer Justification...............................................................................................6-3
6.1.3 Performance Events of Pointer Justification..........................................................................................6-3
6.2 Common Causes..............................................................................................................................................6-4
6.4 Methods of Fault Locating..............................................................................................................................6-7
6.4.1 Checking Clock Configuration Data......................................................................................................6-8
6.4.2 Checking Ambient Temperature............................................................................................................6-9
6.4.3 Checking Synchronization of Interconnection Equipment.................................................................... 6-9
6.4.4 Checking Connection of Optical Fibers.................................................................................................6-9
6.4.5 Checking Quality of External Clock......................................................................................................6-9
6.4.6 Checking NE Hardware Faults.............................................................................................................6-10
6.5 Cases on Pointer Justification.......................................................................................................................6-10
7 Troubleshooting Equipment Interconnection Faults..........................................................7-1
7.1.1 Grounding...............................................................................................................................................7-2
7.1.2 Higher Order Path Overhead Bytes C2 and J1.......................................................................................7-3
7.1.3 Processing Mode of C2 and J1...............................................................................................................7-5
7.1.4 Arrangement of VC-12 Timeslots in a VC-4.........................................................................................7-6
7.1.5 Interconnection Between the Broadcast Data Interface of the OptiX Equipment and Other Equipment
.........................................................................................................................................................................7-9
7.2 Common Fault Causes..................................................................................................................................7-10
7.3 Methods of Locating Faults...........................................................................................................................7-11
7.3.1 Common Methods for Locating Faults................................................................................................7-11
7.3.2 Procedures............................................................................................................................................7-12
7.4 Locating and Handling Faults.......................................................................................................................7-18
7.4.1 Checking Service Configuration..........................................................................................................7-18
7.4.2 Checking Physical Connection.............................................................................................................7-19
7.4.3 Checking the Optical Power.................................................................................................................7-19
7.4.4 Checking the Grounding......................................................................................................................7-19
7.4.5 Checking Cable Distance and Signal Attenuation...............................................................................7-20
7.4.6 Checking the Structure of an Interconnected Signal............................................................................7-20
7.4.7 Checking Clock Synchronization of the Network................................................................................7-21
7.4.8 Replacing Boards as Required.............................................................................................................7-22
7.5 Cases on Equipment Interconnection............................................................................................................7-22
8 Troubleshooting Multiplex Section Protection Switching Faults....................................8-1
8.1.1 Multiplex Section Protection Classification and Protection Principles................................................. 8-2
8.1.2 Standards to Follow................................................................................................................................8-4
8.1.3 Realization of MSP Switching...............................................................................................................8-4
8.1.4 State Transition of the APS controller................................................................................................... 8-5
8.1.5 MSP Switching Condition and Priority..................................................................................................8-8
8.1.6 K Byte..................................................................................................................................................8-11
xi
8.2 Common Faults and Causes..........................................................................................................................8-13
8.3 Fault Locating Flow......................................................................................................................................8-13
8.4 Cases on Multiplex Section Protection.........................................................................................................8-16
9 Troubleshooting SNCP Switching Faults.............................................................................9-1
9.1.1 SNCP Principle......................................................................................................................................9-2
9.1.2 Boards Involved in SNCP Switching.....................................................................................................9-3
9.1.3 SNCP Trigger Conditions......................................................................................................................9-4
9.1.4 SNCP Service Configuration.................................................................................................................9-4
9.2 Common Faults and Causes............................................................................................................................9-5
9.4 Cases on SNCP................................................................................................................................................9-7
10 Troubleshooting Clock Protection Switching Fault........................................................10-1
10.1 Background Knowledge..............................................................................................................................10-2
10.1.1 Clock Quality.....................................................................................................................................10-2
10.1.2 SSM Transmission Mode...................................................................................................................10-3
10.1.3 Principle of Clock Protection.............................................................................................................10-3
10.1.4 Configuration of Clock Protection Switching....................................................................................10-4
10.1.5 Boards Involved in Clock Protection Switching................................................................................10-5
10.2 Common Faults and Causes........................................................................................................................10-6
10.3 Fault Locating Flow....................................................................................................................................10-6
10.4 Cases on Clock Protection...........................................................................................................................10-8
11 Troubleshooting Tributary Protection Switching Fault.................................................11-1
11.1.1 TPS of the OptiX OSN 3500..............................................................................................................11-2
11.1.2 Working Principle..............................................................................................................................11-6
11.4 Cases on TPS Protection.............................................................................................................................11-9
12 Troubleshooting ECC Faults................................................................................................12-1
12.1.1 Communication Between NM and NEs.............................................................................................12-2
12.1.2 ECC Signal Flow................................................................................................................................12-3
12.1.3 ECC Routing......................................................................................................................................12-3
12.1.4 ID and IP............................................................................................................................................12-4
12.1.5 Manual Settings of Connection List and Routing Table...................................................................12-4
12.1.6 ECC Routing Planning.......................................................................................................................12-5
12.4 Case of ECC................................................................................................................................................12-8
13 Troubleshooting Orderwire Fault.......................................................................................13-1
Contents
Troubleshooting
xii Huawei Proprietary and Confidential
Issue 04 (2010-11-30)
13.1.1 Setting Principles for the Orderwire Phone........................................................................................13-2
13.1.2 Network-Wide Conference Call and Subnet Conference Call...........................................................13-3
13.1.3 Calling Waiting Time.........................................................................................................................13-3
13.4 Cases on Orderwire.....................................................................................................................................13-6
14 Ethernet Troubleshooting.....................................................................................................14-1
14.1.1 Ethernet Service Features...................................................................................................................14-2
14.1.2 Ethernet Service Classification..........................................................................................................14-3
14.2 Common Fault Causes................................................................................................................................14-4
14.3.1 Fault Locating Flow...........................................................................................................................14-5
14.3.2 Fault Locating Flow...........................................................................................................................14-8
14.4 Cases on the Ethernet Faults.....................................................................................................................14-10
15 Handling of ATM/IMA Faults.............................................................................................15-1
15.1.1 IMA Functions and Interconnection..................................................................................................15-2
15.2 Common Causes..........................................................................................................................................15-4
15.4 Cases on ATM and IMA.............................................................................................................................15-7
16 Remote Maintenance Guide................................................................................................16-1
16.1 Introduce......................................................................................................................................................16-2
16.2 Enabling a Remote Maintenance User........................................................................................................16-2
16.3 Establishing Remote Maintenance..............................................................................................................16-3
A Glossary.....................................................................................................................................A-1
A.1 Numerics........................................................................................................................................................A-3
A.2 A....................................................................................................................................................................A-3
A.3 B....................................................................................................................................................................A-5
A.4 C....................................................................................................................................................................A-6
A.5 D....................................................................................................................................................................A-9
A.6 E...................................................................................................................................................................A-10
A.7 F...................................................................................................................................................................A-12
A.8 G..................................................................................................................................................................A-14
A.9 H..................................................................................................................................................................A-14
A.10 I..................................................................................................................................................................A-15
A.11 J..................................................................................................................................................................A-16
A.12 L.................................................................................................................................................................A-16
A.13 M................................................................................................................................................................A-18
A.14 N................................................................................................................................................................A-19
xiii
A.15 O................................................................................................................................................................A-20
A.16 P.................................................................................................................................................................A-21
A.17 Q................................................................................................................................................................A-23
A.18 R................................................................................................................................................................A-23
A.19 S.................................................................................................................................................................A-25
A.20 T.................................................................................................................................................................A-28
A.21 U................................................................................................................................................................A-29
A.22 V................................................................................................................................................................A-30
A.23 W...............................................................................................................................................................A-30
Contents
Troubleshooting
xiv Huawei Proprietary and Confidential
Issue 04 (2010-11-30)
Figures
Figure 1-1 Chain network.....................................................................................................................................1-6
Figure 1-2 Signal flow of PRBS test for lower order services...........................................................................1-14
Figure 1-3 PRBS test for lower order services in tributary direction.................................................................1-14
Figure 1-4 PRBS test for lower order services in cross-connect direction.........................................................1-15
Figure 1-5 Signal flow of PRBS test for higher order services (initiated by a cross-connect board)................1-15
Figure 1-6 RPBS test for higher order services in line direction (initiated by a cross-connect board)..............1-16
Figure 1-7 PRBS test for higher order services in line direction (initiated by a line board)..............................1-16
Figure 1-8 Loopback on the electrical interface.................................................................................................1-19
Figure 2-1 General flow for troubleshooting faults..............................................................................................2-3
Figure 2-2 Emergency flow for troubleshooting faults........................................................................................2-5
Figure 3-1 Emergency handling flow...................................................................................................................3-3
Figure 4-1 Block diagram of the OptiX OSN 3500 hardware structure...............................................................4-3
Figure 4-2 Handling flowchart of service interruption ........................................................................................4-6
Figure 5-1 Networking diagram...........................................................................................................................5-2
Figure 5-2 Handling flowchart of service bit error..............................................................................................5-4
Figure 6-1 Generation of AU pointer...................................................................................................................6-2
Figure 6-2 Generation of TU pointer...................................................................................................................6-3
Figure 6-3 Handling flowchart of service interruption pointer justification........................................................6-6
Figure 7-1 Overhead pass-through and overhead termination.............................................................................7-6
Figure 7-2 Flow of troubleshooting a fault in the SDH line interconnection.....................................................7-13
Figure 7-3 Flow of troubleshooting a fault in the PDH tributary interconnection.............................................7-14
Figure 7-4 Flow of troubleshooting a fault in the auxiliary interface interconnection......................................7-15
Figure 7-5 Attaching a BER tester to test the SDH interconnection..................................................................7-17
Figure 7-6 Attaching a BER tester to test the PDH interconnection..................................................................7-17
Figure 7-7 2 Mbit/s signal interconnection........................................................................................................7-19
Figure 8-1 Two-fiber bidirectional multiplex section shared protection ring......................................................8-3
Figure 8-2 Multiplex section module (NM side)..................................................................................................8-4
Figure 8-3 Relations between multiplex section switching algorithm and NE side or board side.......................8-5
Figure 8-4 Process of APS controller state transition..........................................................................................8-6
Figure 8-5 Bit arrangement for K1 byte of linear MSP......................................................................................8-12
Figure 8-6 Bit arrangement for K2 byte of linear MSP......................................................................................8-12
Figure 8-7 Bit arrangement for K1 byte of MSP ring........................................................................................8-12
Figure 8-8 Bit arrangement for K2 byte of MSP ring........................................................................................8-12
Troubleshooting Figures
xv
Figure 8-9 Handling flowchart of multiplex section faults................................................................................8-14
Figure 9-1 Boards involved in SNCP switching..................................................................................................9-3
Figure 9-2 Handling flowchart of SNCP switching fault ....................................................................................9-6
Figure 10-1 Clock tracing direction in SDH synchronization network..............................................................10-4
Figure 10-2 Handling flowchart of clock protection switching fault.................................................................10-7
Figure 11-1 Protection mode of E1/T1 processing board.................................................................................. 11-2
Figure 11-2 Protection mode of E3/T3 processing board (1).............................................................................11-3
Figure 11-3 Protection mode of E3/T3 processing board (2).............................................................................11-3
Figure 11-4 Protection mode of E4 processing board........................................................................................11-4
Figure 11-5 Protection mode of STM-1(e) processing board............................................................................ 11-4
Figure 11-6 Protection mode of Ethernet board.................................................................................................11-5
Figure 11-7 Protection mode of DDN board......................................................................................................11-5
Figure 11-8 TPS protection for hybrid services.................................................................................................11-6
Figure 11-9 Handling flowchart of TPS faults...................................................................................................11-8
Figure 12-1 ECC in ring network.......................................................................................................................12-3
Figure 12-2 Handling flowchart of ECC fault ...................................................................................................12-6
Figure 13-1 Handling flowchart of orderwire faults ......................................................................................... 13-5
Figure 14-1 Ethernet frame structure................................................................................................................. 14-3
Figure 14-2 Interface of Ethernet faults locating............................................................................................... 14-5
Figure 14-3 Handling flowchart of Ethernet network fault in the case of service interruption......................... 14-6
Figure 14-4 Handling flowchart of Ethernet network fault in the case of service degradation......................... 14-9
Figure 15-1 Basic IMA functions.......................................................................................................................15-2
Figure 15-2 IMA service networking.................................................................................................................15-3
Figure 15-3 Handling flowchart of IMA interconnection faults........................................................................15-6
Figure 16-1 Connection for remote maintenance...............................................................................................16-2
Figures
Troubleshooting
xvi Huawei Proprietary and Confidential
Issue 04 (2010-11-30)
Tables
Table 1-1 Locating and clearing complicated faults ............................................................................................1-5
Table 1-2 Comparison of the methods of using the NMS and observing equipment indicators .........................1-8
Table 1-3 Software loopback provided by the OptiX series products..................................................................1-9
Table 1-4 Comparison of the methods for locating faults..................................................................................1-17
Table 1-5 Troubleshooting procedures and methods.........................................................................................1-22
Table 1-6 Terminology.......................................................................................................................................1-22
Table 2-1 Equipment alarms of the .....................................................................................................................2-6
Table 3-1 OptiX OSN Equipment alarms.............................................................................................................3-4
Table 4-1 Common causes of service interruption...............................................................................................4-4
Table 5-1 The common causes of bit errors.........................................................................................................5-2
Table 6-1 Performance events of pointer justifications........................................................................................6-4
Table 6-2 Common causes for the pointer justifications......................................................................................6-4
Table 7-1 C2 byte coding.....................................................................................................................................7-4
Table 7-2 Path numbering....................................................................................................................................7-7
Table 7-3 Interface pin assignment......................................................................................................................7-9
Table 7-4 Common causes of equipment interconnection faults........................................................................7-11
Table 7-5 Alarms relevant to EI faults and possible causes...............................................................................7-16
Table 8-1 APS controller states............................................................................................................................8-5
Table 8-2 Process of APS controller state transition............................................................................................8-6
Table 8-3 MSP switching modes..........................................................................................................................8-9
Table 8-4 LMSP switching priorities...................................................................................................................8-9
Table 8-5 RMSP switching priorities.................................................................................................................8-10
Table 8-6 Common causes of MSP switching fault...........................................................................................8-13
Table 9-1 Comparison between SNCP and MSP.................................................................................................9-2
Table 9-2 SNCP trigger conditions......................................................................................................................9-4
Table 9-3 Causes of the SNCP switching faults...................................................................................................9-5
Table 10-1 SSM codes........................................................................................................................................10-2
Table 10-2 Causes of common faults.................................................................................................................10-6
Table 11-1 Board Supporting Protection............................................................................................................11-6
Table 11-2 Common causes for TPS switching fault.........................................................................................11-7
Table 12-1 Common causes of ECC faults........................................................................................................12-5
Table 13-1 Configuration requirements of network orderwire...........................................................................13-2
Table 13-2 Common causes of the orderwire faults...........................................................................................13-4
Troubleshooting Tables
xvii
Table 14-1 Common causes for service interruption..........................................................................................14-4
Table 14-2 Common causes for service degradation..........................................................................................14-4
Table 15-1 Common causes of IMA interconnection faults...............................................................................15-4
Tables
Troubleshooting
xviii Huawei Proprietary and Confidential
Issue 04 (2010-11-30)
1 General Model and Methods of Fault
Locating
About This Chapter
This chapter describes the basic thoughts and methods of locating faults.
1.1 Requirements for the Maintenance personnel
To locate and rectify faults speedily, the maintenance personnel must meet the requirements for
service skills and operational regulations.
1.2 Basic Principle of Locating Faults
This section describes the basic principles to be followed in the process of locating faults.
1.3 Common Methods of Locating Faults
The common methods of locating faults in the OptiX series equipment are fault analysis,
loopback, and board replacement.
1.4 Some Classified Faults and Their Troubleshooting
The procedures for troubleshooting the equipment are basically the same irrespective of the fault
type.
1.5 Terminology
There are some terms that you need to know about before maintaining the equipment.
Troubleshooting 1 General Model and Methods of Fault Locating
1-1
1.1 Requirements for the Maintenance personnel
To locate and rectify faults speedily, the maintenance personnel must meet the requirements for
service skills and operational regulations.
1.1.1 Professional Skills
Maintenance personnel should acquire some professional knowledge and skills before
troubleshooting.
1.1.2 Network Layout
To locate faults, maintenance personnel should be acquainted with the networking information.
1.1.3 Collecting and Storing On-site Data
In the process of locating faults, the on-site data should be collected and stored.
1.1.1 Professional Skills
Maintenance personnel should acquire some professional knowledge and skills before
troubleshooting.
l Be familiar with SDH Fundamentals.
l Be familiar with alarm generating mechanism and signal flow in the transmission system.
For details, refer to the Alarms and Performance Events Reference.
l Be familiar with common alarms.
Line alarms
R_LOS
R_LOF
R_OOF
AU_AIS
AU_LOP
MS_AIS
MS_RDI
B1_EXC
B2_EXC
B3_EXC
HP_LOM
HP_SLM
HP_TIM
HP_UNEQ
ETH_LOS
Link_ERR
ALM_GFP_dLFD
VCAT_LOA
Tributary alarms
1 General Model and Methods of Fault Locating
Troubleshooting
1-2 Huawei Proprietary and Confidential
Issue 04 (2010-11-30)
TU_AIS
TU_LOP
T_ALOS
UP_E1AIS
DN_E1AIS
LP_RDI
LP_SLM
LP_TIM
LP_UNEQ
BIP_EXC
Protection switching alarms
APS_INDI
TPS_ALM
PS
Clock alarms
LTI
SYNC_C_LOS
SYN_BAD
Equipment alarms
POWER_ABNORMAL
BD_STATUS
HARD_BAD
TEMP_ALARM
l Equipment and NM Operations
For details, refer to the NM system operation manual and online Help.
l Basic Transmission Meters
Meters used during the maintenance of the Optical Network equipment include the 2 Mbit/s
BER tester, optical power meter, SDH analyzer, oscilloscope, and multi-meter. For their usage,
refer to the corresponding user manuals.
Visiting Huawei Web Sites Regularly
You can visit the web sites of Huawei to obtain the related documentation.
l http://www.huawei.com
l http://support.huawei.com
1.1.2 Network Layout
To locate faults, maintenance personnel should be acquainted with the networking information.
l Networking
l Service configuration
1-3
l Operating conditions of the equipment
l Engineering documents and maintenance of engineering documents
1.1.3 Collecting and Storing On-site Data
In the process of locating faults, the on-site data should be collected and stored.
l Alarms and performance events of the equipment
l Configuration data of NEs and boards
l Operation status of NEs and boards
l Operation log of the network management system (NMS)
1.2 Basic Principle of Locating Faults
This section describes the basic principles to be followed in the process of locating faults.
The key principle of locating faults is: locate the fault in a single station precisely.
The general principles of troubleshooting can be summarized as follows:
External first, then transmission; network first, then NE; high-speed section first, then
low-speed section; higher level alarms first, then lower level alarms. The basic principles
of locating faults are as follows:
l External first, then transmission
When you locate faults, first ensure that the external conditions are normal. For example, the
line optical fiber should be working normally, there should be no power failure, and there should
be no fault on the switching equipment.
l Network first, then NE
When you locate faults, first try to precisely locate in which station the fault lies.
l High-speed section first, then low-speed section
The alarm signal flow shows that the alarms of high-speed signals usually cause alarms of low-
speed signals. Hence, clear faults in the high-speed section first.
l High-level alarms first, then low-level alarms
First handle high-level alarms, such as critical alarms and major alarms. Then handle low-level
alarms, such as minor alarms and warnings.
1.3 Common Methods of Locating Faults
The common methods of locating faults in the OptiX series equipment are fault analysis,
loopback, and board replacement.
When a fault occurs, first determine the possible faulty points by analyzing the alarm events,
performance data and signal flow. Then locate the fault to a particular NE and finally to a
particular board by looping back station by station. Finally, clear the fault by replacing the faulty
board.
To locate and remove complicated faults, refer to Table 1-1.
Troubleshooting
Issue 04 (2010-11-30)
Table 1-1 Locating and clearing complicated faults
Method Application Characteristic
Alarm and
performance
analysis
Universal l Evaluates the entire network situation
to preliminarily locate the point where
the fault occurs.
l Causes no negative effect to the
services.
l Depends on the NMS.
Loopback Isolates external faults and
locates the fault to a specific
NE or board.
l Is independent of alarm and
performance event analysis.
l Is rapid.
Replacement Locates the fault to a specific
board or isolates external
faults.
l Is simple.
l Requires spare parts.
l Needs to be used together with other
methods.
Configuration
data analysis
Locates the fault to a specific
NE or board.
l Finds the cause for a fault.
l Takes longer time to locate a fault.
Configuration
modification
Locates the fault to a board. l Is highly risky.
Meter test Isolates external faults and
resolves interconnectivity
problems.
l Is a general method with high
accuracy.
l Has specific requirements for the
meters.
l Needs to be used together with other
methods.

1.3.1 Alarm and Performance Event Analysis
Analyzing alarms and performances is a method used to locate faults.
1.3.2 Loopback
Loopback is the most popular and effective method to locate faults in an OptiX series equipment.
1.3.3 Replacement
Replacement is a method used to determine and locate faults.
1.3.4 Configuration Data Analysis
Analyzing the configuration data is a method used to determine and locate faults.
1.3.5 Configuration Modification
Configuration modification is a method used to determine and locate faults.
1.3.6 PRBS Test
The PRBS test is a method used to determine and locate faults.
1.3.7 Meter Test
1-5
This method is used to locate a fault.
1.3.8 Comparison of Methods for Locating Faults
This section describes the methods commonly used to locate faults and their characteristics.
1.3.1 Alarm and Performance Event Analysis
Analyzing alarms and performances is a method used to locate faults.
In an SDH frame, there are abundant overhead bytes that carry system alarms and performance
data. Hence, failure of the SDH system results in a large number of alarms and performance
events. After analyzing the alarms and performance events, you may infer the type and position
of the fault.
To obtain alarms and performance events, do as follows:
l Query the current or history alarms and performance events on the NMS.
l Learn the operation status of the equipment through the RUN and ALARM indicators on
the cabinet and the boards.
Querying Alarms Using the NMS
The features of locating a fault by using the NMS are as follows:
l Comprehensive: You can obtain the fault information of the entire network.
l Accurate: You can obtain current alarms, alarm generation time, and history alarms of the
equipment. In addition, you can obtain the specific values of the performance events.
l Complex: In case of too many alarms and performance events, analysis becomes difficult.
l Dependent: Locating faults is totally dependant on the normal functioning of the computer,
software, and communication equipment. Hence, if one of the three is faulty, the capability
of locating faults is reduced or even lost.
Consider a chain network as an example, where the NM computer is connected to NE1. See
Figure 1-1.
Figure 1-1 Chain network
NE1 NE2 NE3 NE4
NM
W E W E W W

Fault symptom:
If the E1 service between NE1 and NE4 is disrupted, NE4 cannot be accessed from NE1.
In addition, the MS_RDI and HP_RDI alarms occur at the east line board of NE3, and an LP_RDI
alarm occurs in the E1 path to which the service between NE1 and NE4 corresponds.
Fault analysis:
Troubleshooting
Issue 04 (2010-11-30)
After analysis of the alarms, you may find that signals from NE3 are not correctly received at
NE4, but NE3 can correctly receive the signals from NE4.
The possible causes are as follows:
l There is a problem with the signal transmission of the east optical board at NE3.
l The optical fiber or connectors are faulty.
l Faults occur to the signal receiving of the line board at NE4.
Fault locating:
To locate the fault, you can change the configuration or manually insert an alarm on the NMS.
For example, if the fibers between NE2 and NE3 are suspected to be reversely connected (the
east line board of NE2 is connected to the east line board of NE3) as shown in Figure 1-1, we
can use the NMS to manually insert an HP_RDI alarm at the east line board of NE2. Then, check
the alarm on NE3.
l If the west line board of NE3 reports an HP_RDI alarm, the east transmit end of NE2 is
connected to the west receive end of NE3. This indicates that the fiber connection is correct.
l If the east line board of NE3 reports an HP_RDI alarm, the east transmit end of NE2 is
connected to the east receive end of NE3. This indicates that the fiber connection is reversed
and needs to be corrected.
CAUTION
When you query alarms or performance events by using the NMS, ensure that the time of all
NEs is synchronous with the time of the NMS. Otherwise, the reported information of alarms
or performance events may be incorrect.
During maintenance, make sure that the current time of the NE is synchronous with the time of
the NMS after you re-issue configurations to the NE. Otherwise, the NE works at the default
time, which is not the current time.
Observing Equipment Indicators
The OptiX series equipment has running and alarm indicators, in different colors. The indicators
indicate the running status of the equipment or the severities of existing alarms.
For details, refer to the System Hardware Description.
Comparison of the Two Methods
Both the methods have their advantages. Hence, use both methods when locating a fault.
The NM maintenance personnel and the equipment maintenance personnel must participate in
troubleshooting. Generally, the NM maintenance personnel superintend the activity and the on-
site maintenance personnel cooperate.
Refer to Table 1-2 to learn about the two methods.
1-7
Table 1-2 Comparison of the methods of using the NMS and observing equipment indicators
Item NMS Indicator
Main user NM maintenance personnel Equipment maintenance
personnel
Role Primary Assistant
Alarm information Entire network, large amount, and
precise
Local NE, few, and fuzzy
History alarms Available Unavailable
Alarm time Seen Unknown
Performance events Seen Unknown
Computer, software,
and communication
Fully dependent Independent

Limitation of Alarm and Performance Event Analysis
l If the networking topology, service, and fault data are complicated, a large number of alarms
and performance events may occur when a fault occurs. In this case, it is difficult for the
maintenance personnel to locate the fault.
l When some faults occur, no obvious alarm or performance event may be reported or
detected. In this case, alarm and performance event analysis does not help.
1.3.2 Loopback
Loopback is the most popular and effective method to locate faults in an OptiX series equipment.
Overview
The most significant feature of this method is that there is no need of thorough data and
performance analysis. Hence, the equipment maintenance personnel are expected to be familiar
with this method.
CAUTION
Loopback may affect the normal service. Perform this operation during off-peak hours.
There are software loopback and hardware loopback, which have their own advantages and
disadvantages as follows:
l Compared with software loopback, hardware loopback is more reliable. Hardware
loopback, however, requires on-site operation. In addition, the overload of the received
optical power must be considered during the operation.
l Compared with hardware loopback, software loopback is simpler but locates a broader
range of faults and indicates a rough position. For example, during a single NE test, if a
software inloop is performed on an optical port and the service is normal, it does not
Troubleshooting
Issue 04 (2010-11-30)
necessarily mean that the line board is normal. But if a selfloop is performed on the optical
port by using a fiber jumper and the service is normal, it means that the line board is normal.
Software Loopback Provided by the OptiX Series Equipment
For the operations and application of the software loopback provided by the OptiX series
equipment, refer to Table 1-3.
Table 1-3 Software loopback provided by the OptiX series products
Board That
Supports
Software
Loopback
Tool Software
Loopback Type
Loopback
Level
Application
Tributary
board
NMS Inloop/Outloop Loopback at
the path level
l Separates switching
faults from transmission
faults.
l Determines the tributary
board failure roughly.
l The service
configuration need not
be modified.
Line board NMS Inloop/Outloop Loopback at
the VC-4
level,
loopback by
the optical
interface
l Locates the fault to a
particular station.
l Determines the line
board failure.
l The service
configuration need not
be modified.
Cross-
connect and
timing board
NMS Line loopback/
Tributary
loopback
Loopback at
the service
channel level
l Determines whether the
fault occurs on the line
side or on the tributary
side of the board when
the fault is located to a
particular station.
l Requires that the service
configuration is
modified. Thus, the
operator must be
qualified.

By performing a loopback operations on the tributary board and the line board, you can locate
a fault to a specific NE and can check whether the board is faulty. This method is widely applied.
The maintenance personnel are required to master it.
You can perform a loopback on the cross-connect and timing board to check whether the board
fault occurs on the line side, tributary side, or in the cross-connection, and then to locate the fault
1-9
to the line board on one side. The loopback operations on the cross-connect and timing board
are complex, and thus are used in few cases.
NOTE
The simplest method to implement a loopback on the cross-connect and timing board is to configure a line
board or tributary board with a loopback service by using the NMS.
Back up the existing services so that the services can be restored after the loopback.
Application
Before carrying out a loopback operation, determine the path and timeslot, the loopback position,
and the type of loopback to be used (inloop or outloop).
NOTE
Differences between outloop and inloop: To check whether the interface module of a board or an external
cable is normal, set the loopback to outloop. To check whether the cross-connect unit or a service channel
is normal, set the loopback to inloop.
To perform a loopback operation, do as follows:
Procedure
Step 1 By means of consultation, observation and test, select a faulty service channel on which the
loopback will be performed. Use the following simplified procedure to sample a service channel
for the loopback:
l Select a faulty NE.
l At the NE, select a faulty service channel.
NOTE
Since self-loop of the first VC-4 may affect the ECC communication, do not select the first VC-4 for
loopback.
l Analyze the service in one direction of the selected service channel.
Step 2 Draw the path diagram of the selected service in one direction. Mark the source and sink of the
service, the NEs through which the service passes, and the VC-4 path and the timeslot the service
occupies.
Step 3 Perform loopback section by section and station by station according to the service trail until
the faulty NE is located.
Step 4 After locating the faulty NE, further locate the possible faulty board by looping back the line,
tributary or cross-connect boards. Confirm the faulty board by applying other test methods.
Finally, replace the faulty board.
TIP
Services that fail at the same time are often related to each other. Hence, the services gradually recover
one after the other.
In addition simplified sampling makes the fault analysis and locating easier, especially if the fault is very
complicated.
----End
Example
Refer to chapter 14 "Regular Operations for Troubleshooting" in the Troubleshooting.
Troubleshooting
Issue 04 (2010-11-30)
Summary
You can perform loopback to quickly locate a fault to a station or even to a board without
spending excessive time on analyzing the alarm or performance events. The operations are
simple and can be easily mastered by the maintenance personnel.
If any other services are normal in the loopback path, however, the loopback method may cause
transient service interruption. Thus, you can adopt the loopback method to handle a fault only
in the case of a critical accident. For example, the services are interrupted.
1.3.3 Replacement
Replacement is a method used to determine and locate faults.
Overview
With this method, replace a suspected faulty object with a normal one to check whether the
suspected one is faulty. The object may be a section of fiber, a device or a board.
Application
Replacement is applicable when you handle problems of the external equipment, such as an
optical fiber, trunk cable, switch, and power supply equipment.
In addition, the replacement method is also used to remove the problem in the board at a single
NE.
Example
Consider Figure 1-1 as an example.
If the optical fibers between the transmit end of NE3 and the receive end of NE4 are suspected
to be faulty, exchange the receive and transmit fibers between the two NEs.
If the R_LOS alarm occurs at the receive end of the east line board of NE3, it indicates that the
optical fibers are faulty. If the fault persists, the line board is faulty. Then, replace the east line
board on NE 3 and the west optical interface board on NE4 to check whether the line board is
faulty.
If there is a T_ALOS alarm on the 2 Mbit/s path of the tributary board and the alarm is suspected
to be caused by the external switch or external trunk cable, interchange the path with a normal
one.
After the replacement, if the T_ALOS alarm shifts, it indicates that the external trunk cable or
the external switch is faulty.
If the T_ALOS alarm persists, there may be a problem with the transmission.
Using this method, you can also solve problems related to power supply and grounding.
Summary
This method is practical and is easy for the maintenance personnel to understand.
This method, however, requires spare parts. Extra care is required during its application.
Improper handling of the board or component during the replacement may cause damage and
even result in a new fault.
1-11
1.3.4 Configuration Data Analysis
Analyzing the configuration data is a method used to determine and locate faults.
Overview
Sudden change in ambient conditions or improper operations may change or damage the
configuration data, for example, NE and board data of the equipment.
This can affect the service. In this case, after locating the fault at a single NE, further analyze
the configuration data to locate the fault.
Application
Locate the fault by querying and analyzing the current configuration data of the equipment.
The configuration data includes the following items:
l Node parameters of the multiplex section
l Path loopback setting for the line and tributary boards
l Tributary path protection attributes
l Path trace byte
For example, if the SNCP protection of a certain tributary board does not work, query whether
the path attribute of the tributary board is set to "protection".
You can view the operation log on the NM to check whether any improper operation on the NM
is performed.
Summary
This method is applicable to further analysis of a known faulty NE and helps to find the root
cause of a fault. This method, however, takes a long time and requires expertise in the field of
optical transmission and essential product knowledge.
1.3.5 Configuration Modification
Configuration modification is a method used to determine and locate faults.
Overview
Use this method to modify the timeslot configuration, slot configuration, and board parameter
configuration. This method also removes problems caused by configuration errors in a known
faulty NE.
In addition, this method is used to troubleshoot pointer justifications.
Application
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.
If a certain slot is suspected to be faulty, change the slot configuration.
If a VC-4 is suspected to be faulty, shift the traffic to another VC-4.
Troubleshooting
Issue 04 (2010-11-30)
During the upgrade or expansion, if you are unsure about the new configuration, you can re-load
the original configuration for confirmation.
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.
To modify the configuration in case of pointer justification, modify the tracing direction and the
reference source of the clock.
Summary
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.
CAUTION
In the MSP ring, modifying the service configuration during switching may stop the multiplex
section protocol. This may interrupt the service.
1.3.6 PRBS Test
The PRBS test is a method used to determine and locate faults.
Overview
A Pseudo-Random Binary Sequence (PRBS) module functions as a meter and can receive the
non-framed services sent from the module itself. With the application of the module, you do not
need other special meters in the process of deployment or fault locating. It is typically used for
network self-check and maintenance.
The NEs, which are provided with the PRBS function, can be regarded as a meter and are used
to analyze service channels of an individual NE or the entire network to check whether there are
any faults.
Application
The PRBS test method has two types: PRBS test for lower order services and PRBS test for
higher order services.
After the PRBS function is activated, perform loopback at the proper spots. Then, you can
conduct the test in cross-connection, tributary, or line direction. Determine the working state of
the tested service channels based on whether there is any bit error.
l PRBS test for lower order services: a PRBS module is integrated into a tributary board. See
Figure 1-2.
1-13
Figure 1-2 Signal flow of PRBS test for lower order services

Tributary board Cross-connect board
RX OUT
IN
Line board
Return route of PRBS test in tributary direction
PRBS
module
TX
Return route of PRBS test in cross-connect direction

The PRBS test is initiated by the tributary board and can be conducted in two directions.
l In the electric interface direction: The PRBS is looped back by way of cables or other NEs.
In this way, the PRBS module can determine whether the interfaces in transmission
direction of the tributary board function normally. The board sends the fixed PRBS to the
Tx interface of the tributary, and the Rx interface receives the transmitted PRBS. See Figure
1-3.
Figure 1-3 PRBS test for lower order services in tributary direction
Tributary board
PRBS
generator
PRBS
receiver
Cable
TX
RX

l In the cross-connect direction: The PRBS is returned from the lower order cross-connect
chip by way of he higher order cross-connect chip, or is groomed to other tributary or line
board by way of the lower order cross-connect chip and looped back from the board. After
the PRBS arrives at the cross-connect board, it is sent back to the tributary board that
initiates the PRBS test for the test result verification. In this way, you can check whether
the higher order, lower order cross-connect chips, and the service channels of other line or
tributary boards are normal. As shown in Figure 1-4, the board sends the fixed PRBS to a
service channel in the cross-connect direction and the transmitted PRBS is received in the
downlink direction of this channel.
Troubleshooting
Issue 04 (2010-11-30)
Figure 1-4 PRBS test for lower order services in cross-connect direction
Tributary
board
PRBS
generator
PRBS
receiver
Cross-connect
board
OUT
IN
Line board
Inloop at the local line board
Hardware loopback at the local optical interfaces
Line board at the
opposite station

Outloop at opposite optical interfaces
Local NE

l PRBS test for higher order services: A PRBS module is integrated into a line or cross-
connect board. See Figure 1-5, Figure 1-6, and Figure 1-7.
Figure 1-5 Signal flow of PRBS test for higher order services (initiated by a cross-connect board)
OUT
IN
Line board
Return route of PRBS test in line direction
Cross-connect board
PRBS module

l Conducting the PRBS test by using a higher order cross-connect chip:
The PRBS is sent to a line board. Loopback is performed at the optical interfaces of the line
board. The PRBS returns to the cross-connect board by way of the line board. The higher order
cross-connect chip verifies the received PRBS to determine whether the line and higher order
cross-connect channels are in normal conditions. See Figure 1-6.
1-15
Figure 1-6 RPBS test for higher order services in line direction (initiated by a cross-connect
board)
OUT
IN
Line board
Inloop at the local line board
Line board at the
opposite station

Outloop at the opposite optical interfaces
Local NE
Cross-connect
board
PRBS
generator
PRBS
receiver

l Conducting the PRBS test by using a line board:
The PRBS test for higher order services is used to check whether a higher order service channel
functions normally. In the optical interface direction, the PRBS is looped back by way of optical
fibers or other NEs. In this way, the PRBS test module can determine whether the service
channels in transmission are normal. See Figure 1-7.
Figure 1-7 PRBS test for higher order services in line direction (initiated by a line board)
OUT
IN
Line board

Outloop at opposite optical interfaces
Line board at the
opposite station
PRBS
generator
PRBS
receiver

Troubleshooting
Issue 04 (2010-11-30)
Summary
The PRBS test for lower order services, conducted by tributary boards, is used to monitor the
lower order service channels of all the boards in a system. The PRBS test for higher order
services, performed by cross-connect or line boards, can only monitor STM-1 channels.
1.3.7 Meter Test
This method is used to locate a fault.
Overview
This method is used to clear the external faults or to locate the problem related to interconnection.
Application
l To check whether the voltage of the power supply is too high or too low, use a multimeter
to measure the input voltage.
l To check whether the poor interconnection between the equipment and other equipment is
due to the grounding, use a multimeter to measure the voltage between the shielding layer
of the coaxial ports of the transmitter and receiver of the interconnecting path. If the voltage
is more than 0.5 V, it indicates that the grounding is improper.
l To check whether the poor interconnection is caused by a wrong signal, use proper
analyzers to check whether the frame signals and the overhead bytes are normal, and
whether there are any abnormal alarms.
Summary
This method provides accurate results, but it depends on the accuracy of the meters and the
professional knowledge of the personnel.
1.3.8 Comparison of Methods for Locating Faults
This section describes the methods commonly used to locate faults and their characteristics.
Table 1-4 is a comparison of different methods used to locate faults. In normal cases, the
maintenance personnel need to use more than one method to locate and clear faults.
Table 1-4 Comparison of the methods for locating faults
Method Application Characteristic Skill
Requireme
nt
Configuration
data analysis
Locates the fault to a
board.
l Helps find out the causes of
the faults.
l Requires a long time for
fault locating.
Highest
1-17
Method Application Characteristic Skill
Requireme
nt
Alarm and
performance
analysis
Universal l Evaluates the situation as a
whole.
l Foresees latent dangers of
the equipment.
l Does not affect services.
High
Configuration
modification
l Locates the fault to a
board.
l Can solve the pointer
justification
problem.
Operations are complex. Higher
Meter test l Isolates external
faults.
l Solves the problem
of poor
interconnection.
l Is accurate.
l Requires meters.
Higher
Loopback Locates the fault to a
single NE or isolate
external faults.
l Does not require the analysis
of alarms and performance
events.
l Is rapid.
l May affect ECC and normal
services.
Higher
Replacement Locates the fault to a
single NE or isolate
external faults.
Is simple, but requires spares
parts.
Low

1.4 Some Classified Faults and Their Troubleshooting
The procedures for troubleshooting the equipment are basically the same irrespective of the fault
type.
First troubleshoot the external problems of the equipment, and then locate the faulty station.
After that, locate the fault to a specific board, and then clear the fault.
1.4.1 Handling External Faults
Before you locate a fault of the equipment, first clear the external faults related to the grounding,
optical fibers, trunk cables, external switches, and power.
1.4.2 Locating the Fault to a Specific NE
The key to troubleshooting is to locate the fault to a specific NE as much as possible.
1.4.3 Locating a Fault to a Specific Board and Rectifying the Fault
Once a faulty NE is located, use the replacement method to further narrow down the location of
the fault to a specific board or unit.
Troubleshooting
Issue 04 (2010-11-30)
1.4.1 Handling External Faults
Before you locate a fault of the equipment, first clear the external faults related to the grounding,
optical fibers, trunk cables, external switches, and power.
Isolating an Equipment Problem from a Switch Problem
Method 1:
Perform a selfloop on the switch trunk interface. After the selfloop of the trunk interface, if the
switch trunk board is faulty, it indicates failure of the switch. Otherwise, the equipment or the
trunk cable is faulty.
Method 2:
Perform a loopback at the electrical interface to test the 2 Mbit/s, 34 Mbit/s, or 140 Mbit/s service
channel of the equipment to check whether the switch is faulty.
Perform a loopback at the electrical interface. For details, see Figure 1-8.
Figure 1-8 Loopback on the electrical interface
RX
TX
OptiX equipment
RX TX
SDH analyzer/BER tester
OUT
IN
RX
TX
SDH unit
Cross-connect
unit
PDH unit
OptiX equipment
OUT
IN
NE1 NE2
Switch
RX TX
PDH unit
Cross-connect
unit
SDH unit

Select a faulty service channel in NE2 and attach a BER tester to it. Perform an inloop on the
related path of the tributary board of NE1. This loopback isolates the external switch.
Check the BER tester. If the reading is normal, it indicates that the service is normal and the
equipment is working normally. In this situation, the fault may occur on the switch or trunk
cable.
If the BER tester shows errors, the equipment may be faulty.
Troubleshooting Optical Fiber Faults
When an R_LOS alarm is generated, it indicates that either the line board or the optical fiber is
faulty.
To locate the fault further, use the following methods:
Method 1:
Use the optical time-domain reflectometer (OTDR) to check the optical fiber continuity.
1-19
Analyze the line attenuation curve displayed on the analyzer to check whether any fiber is cut.
If a fiber cut exists, locate the fiber cut by referring to the attenuation curve. Note that a distance
of blind area exists near the OTDR.
CAUTION
As the power launched by the OTDR is strong, the line board may be damaged due to receiver
overload optical power. Hence, during a test, disconnect the fiber jumper from the line board.
Method 2:
Measure the transmitted and received optical power of the line boards at the two ends of the
optical fibers. If the transmit power of the opposite line board is normal, and the receive power
of the local end is abnormal, it indicates that the optical fiber is faulty.
If the transmit power of the line board is very low, it indicates that the line board is faulty.
Method 3:
If the transmit power of the line board is normal, perform a loopback on the board by connecting
the transmit port and the receive port of the board with a fiber jumper (avoiding overload of
optical power).
If a critical alarm occurs on the board, it indicates that the board is faulty. If there is no critical
alarm, check the opposite line board. If the alarm is cleared after the opposite board is looped
back, the optical fiber may be faulty.
Method 4:
The replacement method: Replace the faulty fiber with a normal fiber to judge if the optical fiber
is faulty.
Troubleshooting Fiber Connection Faults
In the case of ADM NEs in a ring network, the east line board of the NE must be connected to
the west line board of the next NE, and the connection of other NEs shall follow this rule.
In the case of ADM NEs in a chain network, connect the optical fibers in the specified direction.
The east line board of the NE must be connected to the west line board of the next NE.
When the optical fibers are wrongly connected, a large number of pointer justification events
can occur. To further locate faults, use the methods listed as follows:
Method 1:
Check the fiber connection by removing the fibers, or shutting down the laser. Note that
performing this method affects the service. Hence, this method is not recommended.
Method 2:
Insert the MS_RDI alarm using the NMS. This method is preferable, as the service is not affected.
Method 3:
Modify the higher order path trace byte J1 using the NMS. Modifying the trace byte may affect
the service. Hence, you need to exercise caution when using this method.
Troubleshooting
Issue 04 (2010-11-30)
The three methods mentioned above fulfill the analysis by checking whether the mapping line
board of the adjacent NE reports the correct alarms.
In method 1, the R_LOS alarm shall be reported when the mapping line board of the adjacent
NE cannot receive optical signals.
In method 2, the mapping line board of the adjacent NE shall report the MS_RDI alarm. After
the check, cancel the insertion of the MS_RDI alarm.
In method 3, the HP_TIM alarm shall be reported by the mapping line board of the adjacent NE.
If the mapping line board of the adjacent NE fails to report the expected alarm, but another line
board in the adjacent NE does report the expected alarm, it indicates that the fiber is wrongly
connected.
Troubleshooting Trunk Cable Faults
If the switch relay is found normal during the loopback performed at the switch side, and the
transmission test is also found normal during the selfloop performed in the subrack wiring area
of the equipment, it indicates that the trunk cable is faulty.
In the case of cable blocking or poor connection, a T_ALOS alarm is reported in the related path
of the tributary board. In this case, you can use the wire-matching method or exchange the trunk
cables to check the cable continuity and check whether the cable is connected properly.
Troubleshooting Power Supply Faults
If an NE is not accessible and the R_LOS alarm is reported by the related line board, the power
supply of this NE may fail.
If this NE makes a sudden shift to abnormal state, check whether the power voltage of the
equipment is too low, or whether there is transient voltage fluctuation.
Abnormal state of the NE indicates failure in the path switching or multiplex section switching,
faults in some boards, service interruption, or abnormal login.
Troubleshooting Grounding Faults
If the equipment is struck by lightning or cannot be interconnected, you should check whether
the grounding is correct.
First check whether the grounding meets the specifications. Check whether the equipment is not
grounded jointly, or whether the grounding of the equipment in the same room is consistent.
Then, use meters to measure the grounding resistance and voltage difference between the
working ground and the protection ground. Check whether they are within the allowed range.
1.4.2 Locating the Fault to a Specific NE
The key to troubleshooting is to locate the fault to a specific NE as much as possible.
The most common method of locating a fault to a specific NE is the loopback method.
Specifically, you can locate the faulty station or line board by performing an outloop or inloop
on each line board of different NEs. In addition, the alarm and performance event analysis
method is a common method of locating a fault to a specific NE. Generally, you can locate a
fault to a specific NE by using the two methods together.
1-21
1.4.3 Locating a Fault to a Specific Board and Rectifying the Fault
Once a faulty NE is located, use the replacement method to further narrow down the location of
the fault to a specific board or unit.
In addition, configuration modification and configuration data analysis are commonly used
during the troubleshooting.
Table 1-5 provides procedures and common methods of troubleshooting.
Table 1-5 Troubleshooting procedures and methods
Procedure Method Additional Measure
Removing external
faults
Replacement, meter
test, and loopback
Alarm and performance analysis
Locating the fault to a
single NE
Loopback Alarm and performance analysis
Locating the fault to a
specific board and
rectifying the fault
Replacement Alarm and performance analysis,
loopback, configuration modification, and
checking configuration data

1.5 Terminology
There are some terms that you need to know about before maintaining the equipment.
Table 1-6 lists the terms that you need to know. The understanding of these terms helps to
facilitate the troubleshooting process.
Table 1-6 Terminology
Term Meaning Legend
Upstream
station
For a receiving station, the transmitting
station and stations being passed
through are all its upstream stations. In
the figure at the right, NE1 and NE2 are
upstream stations of NE3. The service
signals can be plesiochronous digital
hierarchy (PDH) signal, synchronous
digital hierarchy (SDH) signal,
embedded control channel (ECC)
signal or orderwire signal.
Service direction
NE1 NE2 NE3

Troubleshooting
Issue 04 (2010-11-30)
Term Meaning Legend
Downstrea
m station
Contrary to an upstream site, NE2 and
NE3 are downstream stations of NE1.
Service direction
NE1 NE2 NE3

Opposite
station
An opposite station is defined based on
the service. In the figure at the right, if
NE1 is the local station, NE2 is the
opposite station of NE1 in service 1;
whereas in service 2, NE3 is the
opposite station of NE1.
Service 1
NE1 NE2 NE3
Service 2

Adjacent
station
The adjacent station is used to describe
the fiber connection. For example, NE1
is the adjacent station of NE2, NE2 is
the adjacent site of NE1 and NE3 and
NE3 is the adjacent station of NE2.
NE1 NE2 NE3

1-23
2 Fault Handling Flow
About This Chapter
In the troubleshooting process, comply with the basic principles and follow the common method.
2.1 General Flow
This section describes the general flow for troubleshooting faults.
2.2 Emergency Handling Flow
The emergency handling flow is for the case that services are interrupted when the equipment
becomes faulty. During the process, follow the fault handling flow and take other emergency
measures such as provision of backup trail to shorten the service interrupting time.
Troubleshooting 2 Fault Handling Flow
2-1
2.1 General Flow
This section describes the general flow for troubleshooting faults.
2.1.1 Flow Chart
The guidance diagram illustrates the process of fault handling.
2.1.2 Flow Description
Record the fault process in detail, including the time at which the fault occurred.
2.1.1 Flow Chart
The guidance diagram illustrates the process of fault handling.
Figure 2-1 shows the general flow for troubleshooting faults.
Troubleshooting
Issue 04 (2010-11-30)
Figure 2-1 General flow for troubleshooting faults
Start
Record fault
symptoms.
External
causes?
Is the service
restored?
End
Notify Huawei of
this fault.
Make the solution
together.
Try the solution.
Observe the running
of the service.
Is this fault
removed?
Compile the fault
handling report.
Other
handling flow
Equipment emergency
handling flow
No
Yes
No
Yes
Yes
Yes
No
No
Equipment
causes?

Record the fault process in detail, including the time at which the fault occurred.
In addition, record the operations before and after the fault, and the alarms and performance
events reported on the NMS.
2-3
Apply other handling flows for faults due to external causes. External causes include the faults
in power supply, fiber, environment in the equipment room (for example, temperature), or
terminal equipment (for example, switch).
Follow the emergency handling flow to deal with a fault caused by an equipment problem.
During emergency handling, services should be restored with the highest priority. Adjust service
routes or perform the forced switching to restore services. Besides, back up the system data.
When the problem cannot be solved on site with every effort, dial 4008302118 to get technical
support from Huawei. Cooperate with Huawei engineers to solve the problem.
After the service resumes, check the running status to make sure that the fault is removed.
Compile the relevant handling report after the fault is removed.
CAUTION
Strictly follow the operation regulations to solve equipment problems. For example, wear the
anti-static wrist strip.
2.2 Emergency Handling Flow
The emergency handling flow is for the case that services are interrupted when the equipment
becomes faulty. During the process, follow the fault handling flow and take other emergency
measures such as provision of backup trail to shorten the service interrupting time.
Before handling a fault, first migrate the services to other available routes by configuration on
the NMS.
CAUTION
Do not do the operations before learning about the cause of the fault, because improper operations
may worsen the problem.
2.2.1 Flow Chart
Introduce the emergency flow for troubleshooting faults.
When services are interrupted, handle it by following certain procedures.
2.2.3 Information Collection and Record
When removing faults, the maintenance staff must record the symptom, alarms, performance
and detailed process used to remove the faults. This ensures that the fault is located and removed.
2.2.4 Report and Technical Support
If you adopt the emergency handling flow, contact Huawei Customer Service Center as soon as
possible, regardless of whether you remove the fault or not.
2.2.1 Flow Chart
Introduce the emergency flow for troubleshooting faults.
Troubleshooting
Issue 04 (2010-11-30)
Figure 2-2 shows the emergency flow for troubleshooting faults.
Figure 2-2 Emergency flow for troubleshooting faults
Keep on locating the
fault
Emergency handling
flow
Transmission NMS
Yes
Yes
Yes
Yes
Contact Huawei
technical support
Loopback or handle the
interconnection problem
Modify the service
configuration
Cancel the setting
Yes
No
N
Yes
No
Handle the problem
of the lcoal station
Handle the fiber
problem/opposite
station problem
Handle the problem
of the lcoal station
Yes
5
No
Yes
No
No
No
No
No
Yes
Yes
Handle the problem
No
Reset/Swap/Replace
the board
Yes
No
Handle the fiber/interface/
Loopback section by
section
No
No
Yes
No
MSP handling/SNCP handling/
Equipment level protection
switching handling
Any equipment
alarm?
Protection switching
failed?
Any STM-N RS or MS
alarm?
Any higher order path
alarm?
Is there the T_ALOS
alarm?
Any lower order path
alarm?
Are there bit errors/
pointer justifications?
Service configuration
wrong?
Loopback/Unequipped
set?
Local receive optical
power abnormal?
Any line alarm after the local
station is loopbacked?
2
1
3
4
T_ALOS disappeared
after the local station is
loopbacked?
Fault cleared?
End
6
7
8
9
Yes
Handle bit errors/
pointer justifications

NOTE
In Figure 2-2, N represents steps 1, 2, 3 ......9.
2-5
When services are interrupted, handle it by following certain procedures.
Checking Equipment Alarms
Upon a service interruption, check if there are alarms listed in Table 2-1, which indicates that
the fault is in the board or equipment. Then, remove the fault first.
Table 2-1 Equipment alarms of the
Alarm Description Solution
POWER_FAIL Power supply failure Check the power box or external
power supply.
BD_STATUS Board not in position Replace the board or SCC board.
NO_BD_SOFT No board software Replace the board.
HARD_BAD Hardware fault of the board Replace the board.
SYN_BAD Clock synchronization source
deterioration
l Replace the clock board in the
NE or other NEs.
l Start the active/standby
switching on the cross-connect
and timing boards.
l Replace the external clock
source.
l Check if the clock tracing
relation forms a ring.

CAUTION
Resetting, swapping, replacing a board or re-sending the configuration data may cause a service
interruption. Try the best to shorten the duration of a service interruption. Do not worsen the
fault coverage.
After replacing the SCC board, re-issue the configuration data of the NE.
Checking the Protection Switching
Protection switching faults include network level protection switching faults (multiplex section,
SNCP) and equipment level protection switching faults.
For a network with network level protection, check if the service interruption is caused by a
protection switching failure.
For an NE with equipment level protection, if the service is interrupted after the working board
fails, check if the interruption is caused by a protection switching failure.
Troubleshooting
Issue 04 (2010-11-30)
Checking Line Faults
If alarms such as R_LOS and R_LOF or regenerator section (RS) bit errors occur on the line,
check the performance event of the laser using the NMS. Or use an optical power meter to test
if the transmit and receive optical power is within the normal range. Remove the fault on the
fiber or on the opposite end.
If the fault lies in the equipment, perform a selfloop on the equipment to locate the faulty point.
Checking Higher Order Path Alarms
If the HP_TIM or HP_SLM alarm occurs, check the J1 andC2 bytes of the higher order path
corresponding to the line board in the upstream station. If the configuration differs with that of
this station, modify the configuration and re-send it again.
In OptiX series products, the HP_TIM alarm does not affect services.
Checking the Tributary Alarm T_ALOS
The T_ALOS alarm indicates faults in the fiber, terminal equipment (for example, switch) or
the tributary board of the local station. Loopback section by section or use meters to locate the
fault.
Checking the Tributary Alarm TU_AIS
The TU_AIS alarm indicates a line fault, external problem or switching exception. Solve the
higher level alarms before handling the TU_AIS alarm.
After locating the faulty point by loopback, you can try to recover the service through enabling
network level protection (path protection, SNCP or MSP) or equipment level protection (cross-
connect, clock active/standby switching or TPS). Avoid worsening the fault coverage when
recovering services through switching.
Checking the Bit Error and Pointer
Upon bit error problems, the line board should be checked before the tributary board. The bit
error on the line relates to the optical power, optical board type, and optical board fault. If the
bit error occurs only on the tributary board, the fault can be located by loopback.
For the pointer problem, check the clock configuration in the network.
Checking the Configuration Data
Check the service configuration section by section along the route.
Checking Loopback and Path Unequipped
Check if loopback or path unequipped is set on the service route.
2.2.3 Information Collection and Record
2-7
2.2.4 Report and Technical Support
Huawei Customer Service Center 24-hour hot line: 4008302118.
In case of a major fault, contact Huawei for support.
Send the faulty board to Huawei for maintenance and apply for a spare board based on the
contract.
Troubleshooting
Issue 04 (2010-11-30)
3 Emergency Handling Flow
About This Chapter
In the case of service interruption, emergency measures should be taken.
The emergency handling flow is performed in case the services are interrupted when the
equipment becomes faulty. During the process, follow the fault handling flow and take other
emergency measures such as provision of backup trail to shorten the service interrupting time.
Before handling a fault, first migrate the services to other available routes by configuration on
the T2000.
CAUTION
Do not perform the operations before learning about the cause of the fault, because improper
operations may aggravate the problem.
3.1 Flow Chart
The emergency handling flow chart shows the procedure for troubleshooting the OptiX OSN
equipment in case of emergency.
3.2 Flow Description
This section describes the procedure for troubleshooting in case of emergency.
3.3 Troubleshooting Service Interruption
When services are interrupted on the equipment, locate the fault and clear it according to the
fault causes.
3.4 Troubleshooting Multiplex Section Protection Switching Faults
In a network with MSP, check whether the service interruption is caused by an MSP switching
failure. Locate and clear the fault according to the fault symptom.
3.5 Troubleshooting SNCP Switching Faults
In a network with SNCP, check whether the service interruption is caused by an SNCP switching
3.6 Troubleshooting Equipment Level Protection Switching Faults
Troubleshooting 3 Emergency Handling Flow
3-1
On an NE with equipment level protection, if services are interrupted after the working board
becomes faulty, check whether the service interruption is caused by a protection switching
failure. Locate and clear the fault according to the fault symptom. This section illustrates how
to troubleshoot a TPS fault.
3.7 Information Collection and Record
3.8 Report and Technical Support
Troubleshooting
Issue 04 (2010-11-30)
3.1 Flow Chart
The emergency handling flow chart shows the procedure for troubleshooting the OptiX OSN
equipment in case of emergency.
Figure 3-1 shows the fault handling procedure.
Figure 3-1 Emergency handling flow
Keep on
locating
Service interruption
handing
Is there any equipment
type alarm?
Is there any higher
order path alarm?
Is there any lower order
path alarm?
Does the service route set with
loopback or unloading?
Yes
Yes
Yes
Yes
End
Contact Huawei
for help
Loopback or handle the
Modify the service
configuration
Cancel the setting
Yes
No
N
Is the service
configuration wrong?
Is there any line alarm after self-
looping the local station?
Yes
No
Handle the problem
of the local station
Handle the problem of the
fiber or the opposite
station
Handle the problem of
the local station
Is there any bit error or
pointer justification?
Yes
9
8
6
4
1
No
Yes
No
No
N
o
No
No
Yes
Is fault
removed?
Is there any line
alarm
?
Does the protection
switching fail?
Yes Handle the
problem
2
No
Reset/swap/replace
board
Yes
No
Handle the fiber/interface/
Loopback section by section
to locate and remove the fault
Does the T_ALOS alarm
disappear after self-looping the
local station?
Is there T_ALOS
alarm?
Handle bit error or pointer
justification
No
No
Yes
7
5
3
Is the receiving optica
power at the local station
abnormal?
No
Yes
MSP handling SNCP protection
switching handling Equipment
level protection switching
handling
Yes
T2000

3.2 Flow Description
This section describes the procedure for troubleshooting in case of emergency.
3-3
Check Equipment Alarms
After service interruption, check whether there are alarms listed in Table 3-1, which indicate
that the board or equipment is faulty. Then, first remove the fault.
Table 3-1 OptiX OSN Equipment alarms
Alarm Description Solution
POWER_FAIL Power supply failure Check the power box or external
power supply.
FAN_FAIL Fan failure that may cause
abnormal equipment
temperature
Check the fan switch or replace the
fan.
BD_STATUS Board is not in position. Replace the board or GSCC board.
NO_BD_SOFT The board has no software. Replace the board.
HARD_BAD Hardware fault of board Replace the board.
W_R_FAIL Hardware fault of board Replace the board.
NESTATE_INSTA
LL
The NE is in installation status. Re-send the configuration.
SYN_BAD Clock synchronization source
deterioration.
l Replace the clock board in the
NE or other NEs.
l Enable active/standby
switching.
l Replace the external clock
source.

CAUTION
l Resetting, swapping and replacing board or re-sending the configuration data may cause
service interruption. Try the best to shorten the duration of service interruption. Do not
worsen the fault in operation.
l After replacing GSCC, re-send the configuration data of the NE.
Check Protection Switching
The protection switching includes network level protection switching (multiplex section, SNCP)
and equipment level protection switching (cross-connect, clock board active/standby protection,
TPS).
In the case of a network with network level protection, check whether the service interruption
is caused by protection switching failure.
In the case of an NE with equipment level protection, if the service is interrupted after the working
board fails, check whether it is caused by the protection switching failure.
Troubleshooting
Issue 04 (2010-11-30)
Check Line Fault
If alarms R_LOS, R_LOF or the regenerator section bit error occur on line, check the laser
performance event on NM. Alternatively, use an optical power meter to test whether the optical
power is within the normal range, and then remove the fault on fiber or on the opposite end
accordingly.
If the equipment is faulty, self-loop the equipment to locate the faulty point.
Check Higher Order Path Alarm
If alarms HP_TIM and HP_SLM occur, you should check the J1 and C2 bytes of the higher
order path corresponding to the line board in the upstream station. If the configuration is different
from that of this station, modify the configuration and re-send it. In OptiX series products, the
HP_TIM does not affect services.
Check Tributary Alarm T_ALOS
The T_ALOS alarm indicates faults in fiber, terminal equipment (for example switch) or the
tributary board of this station. The fault can be located by using a meter test or by using loopback,
section by section.
Check Tributary Alarm TU_AIS
The TU_AIS alarm indicates line fault, external problem or switching exception. Handle the
higher level alarms before handling TU_AIS alarm.
After locating the faulty point by loopback, you can try to recover the service by enabling
network level protection (path protection, SNCP or MSP) or equipment level protection (cross-
connect, clock active/standby switching or TPS). Avoid causing further problems when you
recover services through switching.
Check Bit Error and Pointer
In the case of bit error problems, first check the line board and then check the tributary board.
The bit error on line is related to the optical power, optical board type and the fault of the optical
board. If the bit error only occurs on the tributary board, the fault can be located by loopback.
For the pointer problem, you should check network-wide clock configuration.
Check Service Configuration
Check the service configuration section by section along the route.
Check Loopback and Path Loading
Check whether loopback or path unequipped is set on the service route.
3.3 Troubleshooting Service Interruption
When services are interrupted on the equipment, locate the fault and clear it according to the
fault causes.
For the troubleshooting flow of service interruption, see 4.3 Fault Locating Flow.
3-5
3.4 Troubleshooting Multiplex Section Protection
Switching Faults
In a network with MSP, check whether the service interruption is caused by an MSP switching
For the troubleshooting flow of an MSP switching fault, see 8.3 Fault Locating Flow.
3.5 Troubleshooting SNCP Switching Faults
In a network with SNCP, check whether the service interruption is caused by an SNCP switching
For the troubleshooting flow of an SNCP switching fault, see 9.3 Fault Locating Flow.
3.6 Troubleshooting Equipment Level Protection Switching
Faults
On an NE with equipment level protection, if services are interrupted after the working board
becomes faulty, check whether the service interruption is caused by a protection switching
failure. Locate and clear the fault according to the fault symptom. This section illustrates how
to troubleshoot a TPS fault.
For the troubleshooting flow of a TPS fault, see 11.3 Fault Locating Flow.
3.7 Information Collection and Record
3.8 Report and Technical Support
Huawei Customer Service Center 24-hour hot line: 4008302118.
In case of a major fault, contact Huawei for support.
Send the faulty board to Huawei for maintenance and apply for a spare board based on the
contract.
Troubleshooting
Issue 04 (2010-11-30)
About This Chapter
The service interruption problem can be solved by using basic methods and measures.
4.1 Background Knowledge
This section describes the basic knowledge of signal flow.
4.2 Common Fault Causes
The common causes of fault include external causes, incorrect data configuration, equipment
hardware, bit error, pointer justification, equipment interconnection, and protection switching.
4.3 Fault Locating Flow
This section describes the procedures for locating the faults in the case of service interruption.
4.4 Methods of Fault Locating
Equipment faults may occur due to several types of causes.
4.5 Cases on Service Interruption
This section provides the case analysis of service interruption.
Troubleshooting 4 Troubleshooting Service Interruption
4-1
This section describes the basic knowledge of signal flow.
4.1.1 Classification of Signal Flow
This section describes the different types of signal flow running on the OptiX OSN equipment.
4.1.2 Service Signal Flow
The signal flow that relates to service interruption includes the service signal flow.
4.1.3 Alarm Signal Flow
Alarm signal flow can be used to locate faults that occur on the OptiX OSN equipment.
4.1.4 Clock Signal Flow
The clock information can be extracted from the clock signal flow.
4.1.1 Classification of Signal Flow
This section describes the different types of signal flow running on the OptiX OSN equipment.
l Service signal flow
l Alarm signal flow
l Clock signal flow
l ECC signal flow
l Orderwire signal flow
The flows related to service interruption are service signal flow, alarm signal flow, and clock
signal flow.
4.1.2 Service Signal Flow
The signal flow that relates to service interruption includes the service signal flow.
Service Signal Flow Inside an NE
The hardware structure of the OptiX OSN 3500 is shown in Figure 4-1.
Troubleshooting
Issue 04 (2010-11-30)
Figure 4-1 Block diagram of the OptiX OSN 3500 hardware structure
System control &
communications
processing unit
(GSCC)
SLOT 29
SDH cross-connect and
synchronous timing
units
(EXCSA/GXCSA/UXCSA/
UXCSB/SXCSA/SXCSB/
IXCSA/IXCSB)
SLOT 1
SLOT 2
SLOT 3
SLOT 11
SLOT 20
SLOT 21
SLOT 22
Auxiliary
interface unit
(AUX)
Power unit
(PIU)
Interface
board
Processing
board
SLOT 19
SLOT 4 SLOT 23
SLOT 24
SLOT 5 SLOT 25
SLOT 26
SLOT 6
SLOT 7
SLOT 8
SLOT 13
SLOT14
SLOT 15
SLOT 34
SLOT 33
SLOT 30
SLOT 32
SLOT 31
SLOT 12
SLOT 36
SLOT 35
Processing
board
Interface
board
SLOT 16
SLOT 17
Bus Unit
(board)
Active/
backup

Traffic signals in an NE are processed by the service processing board (such as line board and
tributary board) and the cross-connect board through the bus on the backplane.
The signal flow is as follows: signals are accessed at the line board and tributary board and form
VC-4 after overhead processing or mapping. Then, they are transmitted to the cross-connect
board. After cross-connection, the signals will be output to the line board and tributary board.
The connection between the line board and cross-connect board and that between the tributary
board and cross-connected board are realized by bus.
For the flow and processing procedures of service signals inside the line board, tributary board,
and cross-connect board, refer to the OptiX OSN 3500 Intelligent Optical Transmission System
Hardware Description.
Signal Flow Between NEs
The signal flows in the case of normal condition and switching vary according to the network
types. Refer to the OptiX OSN 3500 Intelligent Optical Transmission System Planning
Guidelines.
Major Methods for Changing Signal Flow
l Switching
l Configuration modification
4-3
l Loopback
4.1.3 Alarm Signal Flow
Alarm signal flow can be used to locate faults that occur on the OptiX OSN equipment.
There are many overhead bytes in an SDH frame, including regenerator section overhead bytes,
multiplex section overhead bytes, and path overhead bytes. These overhead bytes carry alarm
and performance event data, which provides a strong capability of in-service alarm and bit error
monitoring to an SDH system.
An understanding of the generation and monitoring modes of alarms helps you quickly locate
the failure. For details, refer to the OptiX OSN 3500 Intelligent Optical Transmission System
Alarms and Performance Events Reference.
4.1.4 Clock Signal Flow
The clock information can be extracted from the clock signal flow.
The clock signal flow is divided into clock extraction signal flow and clock distribution signal
flow. The direction of the clock extraction signal flow is from the tributary board, line board,
external clock source to the cross-connect and timing board. The direction of the clock
distribution signal flow is from the cross-connect and timing board to the tributary board, line
board and external clock.
The tributary and line slots of the OptiX OSN 3500 subrack are equipped with a clock bus that
is connected to the slot for the cross-connect and timing board. The line boards and tributary
boards use the bus to extract clock signals and send them to the clock unit. The clock unit
generates a system clock signal based on the clock source signal. The system timing signal is
distributed to various boards by the cross-connect and timing board.
The common causes of fault include external causes, incorrect data configuration, equipment
hardware, bit error, pointer justification, equipment interconnection, and protection switching.
Common causes of service interruption are shown in Table 4-1.
Table 4-1 Common causes of service interruption
Fault type Causes Treatments
External causes Abnormal power supply See 4
Troubleshooting
Service Interruption
Optical fibers, cables, and connectors are
faulty
Switch or other equipment is faulty
Environment (temperature, and humidity)
abnormal
Grounding abnormal, and lightning strike
Troubleshooting
Issue 04 (2010-11-30)
Fault type Causes Treatments
Data configuration Configuration error See 4
Troubleshooting
Mis-operation
Software problem during running
Equipment
hardware
Board failure or performance deterioration See 4
Troubleshooting
Bit error Excessive bit errors See 5
Troubleshooting Bit
Errors
Pointer
Justification
Excessive pointer justification See 6
Troubleshooting the
Pointer Justification
Equipment
interconnection
Configuration error or interconnecting
equipment mismatch
See Troubleshooting
Equipment
Interconnection Faults
Protection
switching
Protection switching function abnormal See 8
Troubleshooting
Multiplex Section
Protection Switching
Faults, 9
Troubleshooting
SNCP Switching
Faults, 10
Troubleshooting
Clock Protection
Switching Fault and
11 Troubleshooting
Tributary Protection
Switching Fault

This section describes the procedures for locating the faults in the case of service interruption.
Fault Handling Flow
Figure 4-2 shows the procedures for handling the fault in the case of service interruption.
4-5
Figure 4-2 Handling flowchart of service interruption
Go to the next step
Troubleshooting for
service interruption
Is there any equipment
alarm?
Is there any overhead byte
alarm, such HP_TIM/
HP_SLM?
Is there any TU_AIS/
LP_RDI alarm?
Is loopback/service
unload set?
End
Contact Huawei for
technical support
Handle problems of
equipment interconnection
Modify service
configuration
Cancel settings
Yes
No
N
Is the service
configuration wrong?
Does the line alarm
disappear after the loopback
for this station?
Handle problems of optical
fibers/opposite end station
Handle problems of
this station
Is there any bit error/pointer
justification?
9
8
6
4
1
Is the fault cleared?
Is there any line
alarm?
Does protection
switching fail?
Handle problems of
protection switching
2
Reset/draw/insert/
replace boards
Solve problems of fiber
cables/interfaces/
opposite end equipment
Perform loopbacks section
by section to locate and
eliminate faults
Does the T_ALOS alarm
disappear after the
loopback for this station?
Is there any T_ALOS
alarm?
Handle bit error/pointer
justification
7
5
3
Is the receiving optical
power of this station
abnormal?
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes Yes
Yes
Yes
No
No
No
No
No
No
No
No
No
No
No
No
Handle problems
of this station
Handle problems of
opposite end equipment
U2000

Procedure
Step 1 Cause 1: The NEs have B1 and B2 bit errors.
In the case of service interruption, check for the following alarms first:
Troubleshooting
Issue 04 (2010-11-30)
l POWER_FAIL
l NE_POWER_OVER
l POWER_ABNORMAL
l FAN_FAIL
l BD_STATUS
l NO_BD_SOFT
These alarms indicate a fault in the equipment or board. Clear the fault first.
Step 2 Cause 2: The protection switching fails.
In the case of protection networking, check whether service interruption is caused by a failure
in protection switching . The phenomena of protection switching failure are usually as follows:
l In the case of an SNCP protection networking, there is no switching event reported at the
faulty station.
l In the case of a multiplex section protection (MSP) networking, one or more NEs report no
switching event, or any of the NEs report APS_FAIL alarm.
For more information about service interruption caused by protection switching failures, refer
to the 8 Troubleshooting Multiplex Section Protection Switching Faults, 9 Troubleshooting
SNCP Switching Faults, 10 Troubleshooting Clock Protection Switching Fault, and 11
Troubleshooting Tributary Protection Switching Fault.
Step 3 Cause 3: Line alarms are reported. These line alarms include R_LOS, R_LOF, R_OOF,
AU_AIS, AU_LOP, MS_AIS, MS_RDI, B1_EXC, B2_EXC, HP_LOM, HP_SLM, HP_TIM,
and HP_UNEQ.
Handle the reported alarm according to the alarm type.
Step 4 Cause 4: The T_ALOS alarm is reported.
Step 5 Cause 5: The TU_AIS alarm or the LP_RDI alarm is reported.
Step 6 Cause 6: Bit errors or pointer justification occurs.
For more information about service interruption caused by bit errors or pointer justification,
refer to the Troubleshooting Bit Errors and the Troubleshooting the Pointer Justification.
Step 7 Cause 7: The service is incorrectly configured.
Query items include data configuration of the network, NE and NM. If the service is incorrectly
configured, modify the service configuration.
Step 8 Cause 8: Loopback is set or the service is set as unloaded.
If the tributary board or the line board is set with loopback, the service is interrupted. In this
case, the software or hardware loopback can be cleared on the NM or the equipment.
If the service is set as unloaded on the NM, the service is also interrupted. In this case, Service
unloaded can be changed to Service loaded on the NM.
----End
4-7
Equipment faults may occur due to several types of causes.
4.4.1 Handling of Power Failure
This section describes how to handle a power failure based on the common causes of the power
failure.
4.4.2 Troubleshooting for Grounding
This section describes how to handle a grounding failure based on the common causes of the
grounding failure.
4.4.3 Handling of Environment Abnormality
This section describes how to handle an environment abnormality based on the common causes
of the environment abnormality.
4.4.4 Handling of Abnormalities of Fiber, Cable, and Connector
This section describes how to handle a fiber failure, cable failure, and a connector failure based
on the common causes of the fiber failure, cable failure, and connector failure.
4.4.5 Checking Configuration Data
During the fault location and rectification, the configuration data should be checked.
4.4.6 Checking Misoperation
Human misoperation may result in service interruption.
4.4.7 Checking Consistency of Board Models
After the replacement, models of the new board and original board should be consistent.
4.4.8 Handling Hardware Faults of Equipment
If the fault is a hardware fault, replace the faulty board with a new one.
4.4.1 Handling of Power Failure
This section describes how to handle a power failure based on the common causes of the power
failure.
Common Causes
l The power consumption of the NE exceeds the threshold value.
l External power supply fails or has high fluctuation.
l Power supply fuse is damaged.
l Fuse capacity of power terminal is very small.
l Short circuit of power supply.
l Zero line and live line of AC power supply are wrongly connected.
l Power cable connectors are loose or poorly connected.
l PIU board fails.
Troubleshooting
Issue 04 (2010-11-30)
WARNING
All the services at the local NE may be interrupted if you turn off the power switch on the PIU
power board.
Procedure
Step 1 On the U2000, check whether the NE_POWER_OVER alarm, indicating that the power
consumption of the NE exceeds the threshold value, exists. When the alarm exists, refer to the
OptiX OSN 3500 Intelligent Optical Transmission System Alarm and Performance Event
Reference to handle the alarm.
Step 2 On the U2000, check whether the POWER_ABNORMAL alarm, indicating that the power
supply is invalid, exists. When the alarm exists, refer to the OptiX OSN 3500 Intelligent Optical
Transmission System Alarm and Performance Event Reference to handle the alarm.
Step 3 When the equipment is in operation, measure the voltage of the power distribution unit. Check
whether the voltage is within the permitted range. If it is not within the range, the service
interruption may occur due to power failure. In this case, locate the faulty point.
Step 4 Switch off the power switch on the PIU board. Measure the voltage of the connector terminal
of the power distribution unit. Check whether the voltage is within the permitted range. If it is
not within the range, the external power supply or the cables may be faulty. Otherwise, the PIU
board may fail.
Step 5 If the fault is located on the PIU power board, replace the faulty board.
Step 6 If the fault is located outside the board, you require help from power supply engineers.
----End
4.4.2 Troubleshooting for Grounding
This section describes how to handle a grounding failure based on the common causes of the
grounding failure.
Common Causes
l PGND and BGND are poorly grounded. The grounding resistance is more than 10 ohms.
l The difference between BGND and PGND is more than 0.5 V.
l PGND and BGND share the same ground with the AC zero line.
l The PGNDs of two interconnection equipments are not jointly grounded.
l The audio and trunk cables are poorly grounded.
Procedure
Step 1 Check whether the grounding bar in the equipment room is properly grounded.
Step 2 Check whether the cabinet connects properly with the grounding bar.
Step 3 Check the connection of the front door and the side panel of the cabinet.
Step 4 Check whether the subrack connects properly with the cabinet.
4-9
Step 5 Check whether the signal cable is properly grounded.
Step 6 Check whether the DDF and ODF are properly grounded.
Step 7 Check whether the equipment are properly grounded.
Step 8 Check whether the interconnection equipment are jointly grounded.
You can use meters to measure whether the grounding resistance of BGND and PGND meets
the requirements. You can also check whether the pulse shape of the interconnection signal is
distorted or not.
----End
4.4.3 Handling of Environment Abnormality
This section describes how to handle an environment abnormality based on the common causes
of the environment abnormality.
Common Causes
l The ambient temperature and humidity do not comply the specifications for the normal
running of the equipment in a long time.
l A strong external interference source exists.
l There are rodents in the equipment room.
Procedure
Step 1 Check whether the ambient temperature and humidity meet the requirements.
The specifications are listed as follows:
l Temperature: 0C to 45C
l Relative humidity: 10% to 90%
Step 2 Check whether there is a temperature threshold-crossing alarm, such as TEMP_EXC or
TEMP_ALARM. Check whether the air filter is blocked and whether the fan functions properly.
Step 3 Check whether there are strong interference sources around the equipment. In the case of service
interruption due to environment abnormality, there are usually bit errors or pointer justifications.
You can locate the faults based on these errors or pointer justifications.
Step 4 Check whether there are rodents, such as mice in the equipment room. Check whether the rodent
resistant net is installed properly.
----End
4.4.4 Handling of Abnormalities of Fiber, Cable, and Connector
This section describes how to handle a fiber failure, cable failure, and a connector failure based
on the common causes of the fiber failure, cable failure, and connector failure.
Common Causes
l Cables are broken or wrongly spliced.
l Attenuation of cable and flange is very high.
Troubleshooting
Issue 04 (2010-11-30)
l The cable connector is loose.
l Power cables are wrongly connected.
l The interface board is wrongly connected.
Procedure
Step 1 On the U2000, check whether alarms, such as R_LOS, R_LOF, T_ALOS, P_LOS or
IN_PWR_ABN, are triggered when the fiber, cable, or connector is abnormal. When these
alarms exist, refer to the OptiX OSN 3500 Intelligent Optical Transmission System Alarms
Reference to handle these alarms.
Step 2 Check whether optical fibers and power cables are broken.
Step 3 Check whether optical fibers are wrongly spliced.
Step 4 Check whether connectors are loose.
Step 5 Check whether the bending radius of the optical fiber is not less than 60 mm.
WARNING
Do not stare at the optical interface and the tail fiber connector. Otherwise, the infrared light
from the optical interface may cause permanent eye damage.
WARNING
When you remove the fiber jumper from an optical interface, make sure that the corresponding
optical connector is pulled off. Otherwise, it may cause service interruption.
Test cables and fibers by using loopback, or by using OTDR or optical power meter. You can
also use the multimeter to check the cable connection through wire matching.
Use the optical power meter to measure the receiving optical power, and compare it with the
value recorded during the engineering installation. If the optical power is very low, use the special
cleaning material to clean the connector of the fiber jumper. Then, measure the optical power
again, and if it is still less than the minimum sensitivity, clean the optical connectors of the ODF.
You can also make sure that the bending curve of optical fibers is within the range permitted.
----End
4.4.5 Checking Configuration Data
During the fault location and rectification, the configuration data should be checked.
Check whether the data is correctly configured. Especially, check the configuration data when
the services are interrupted during the equipment installation, commissioning and upgrade.
The query items include data configuration of the network, NE and U2000.
4-11
4.4.6 Checking Misoperation
Human misoperation may result in service interruption.
Misoperation
Human misoperation refers to the following operations on the available services.
l Configure hardware or software loopback.
l Configure services as unloaded.
NOTE
If no services are available on a path of the tributary board, configure the services on the tributary board
as unloaded to suppress the reporting of related alarms.
The purpose to set "service unloaded" is to avoid the interference to normal maintenance from useless
alarms, which may disturb the alert for the alarms of the path where services are available.
Procedure
Step 1 Check whether the loopback is configured on the tributary or line. If the loopback is configured,
the LOOP_ALM alarm, indicating the loopback, can be queried on the U2000. In this case,
release the software or hardware loopback on the U2000 or equipment.
Step 2 Check whether "service unloaded" is configured on the U2000. If "service unloaded" is
configured, the alarm indicating that the path is unloaded, such as LP_UNEQ, can be queried
on the U2000. In this case, modify "service unloaded" to "service loaded".
----End
4.4.7 Checking Consistency of Board Models
After the replacement, models of the new board and original board should be consistent.
Procedure
Step 1 Check whether the model of the replaced or added board during the upgrade or expansion is
consistent with that of the original board. Especially, in the case of the cross-connect and timing
boards with the active and standby relation, the active and standby boards should of the same
model. If the board models are inconsistent, the WRG_BD_TYPE alarm, indicating that the
board type of the inserted board is incorrect, can be queried on the U2000.
Step 2 According to the actual situation, check whether the setting of the DIP switch and jumper is
correct.
NOTE
A replacement relation between different types of boards with the same name is available. For details,
consult technical support engineers of Huawei.
----End
4.4.8 Handling Hardware Faults of Equipment
If the fault is a hardware fault, replace the faulty board with a new one.
Common alarms indicating hardware faults are listed as follows:
Troubleshooting
Issue 04 (2010-11-30)
l HARD_BAD
l COMMUN_FAIL
l HSC_UNAVAIL
l BD_STATUS
l BUS_ERR
l CHIP_FAIL
l PLL_FAIL
l TR_LOC
l T_LOSEX
For handling of the preceding alarms, refer to the Alarms and Performance Events Reference.
Locate the faulty station by analyzing the alarms, indicators or using the loopback. Then, replace
the faulty board to rectify the fault.
4.5 Cases on Service Interruption
This section provides the case analysis of service interruption.
Related cases:
None.
4-13
About This Chapter
Bit errors have a negative impact on the service quality and should be handled in time.
Understanding bit errors helps to locate and troubleshoot the faults related to bit errors.
5.2 Common Causes
Bit errors occur mainly due to the following reasons: external causes, equipment causes, and
incorrect data configuration.
This section describes the procedures for locating bit errors.
5.4 Methods for Fault Locating
You can locate and handle bit errors based on the common causes that result in bit errors.
5.5 Cases on Bit Errors
This section provides the case analysis of bit errors.
Troubleshooting 5 Troubleshooting Bit Errors
5-1
Understanding bit errors helps to locate and troubleshoot the faults related to bit errors.
Generally, higher order bit errors are accompanied with lower order bit errors. For example, if
there is a B1 bit error, there are also B2, B3 and BIP bit errors. Lower order bit errors, however,
are not necessarily accompanied with higher order bit errors. If there is a BIP bit error, there
may be no B3, B2 or B1 bit error.
Because the higher order bit errors can lead to the lower order bit errors, the higher order bit
errors should be handled first for clearing bit errors.
Figure 5-1 shows an example of chain networking. If the optical fiber attenuation between NE2
and NE3 is very high, the optical path bit errors are generated. The line board connected to NE2
and NE3 detects the B1 and B2 bit errors. In addition, all the higher order and lower order paths
that pass this optical path also detect bit errors. If only a 2 M tributary board (such as PQ1) of
NE1 fails, the BIP bit error can be detected only in the corresponding 2 M path. There are no
bit errors in optical paths and higher order paths.
Figure 5-1 Networking diagram
NE1 NE2 NE3 NE4
U2000
W W E W E W

5.2 Common Causes
Bit errors occur mainly due to the following reasons: external causes, equipment causes, and
Table 5-1 shows the common causes of bit errors.
Table 5-1 The common causes of bit errors
Fault Types Causes
External causes Very low or very high receiving optical power along with excessive
dispersion
Deteriorated cable performance
Environment problem very high equipment temperature)
Poor grounding
External interference
Troubleshooting
Issue 04 (2010-11-30)
Fault Types Causes
Equipment causes Faults in the line board, clock board, cross-connect board and tributary
board
Faulty fan
Data configuration
causes
Incorrect clock configuration

This section describes the procedures for locating bit errors.
Fault Handling Flow
Figure 5-2 shows the procedures for handling the fault in the case of bit error.
5-3
Figure 5-2 Handling flowchart of service bit error
Go to the next step
If all the NEs have B1
and B2 bit errors ?
If V5 bit error only ?
End
Contact Huawei for
technical support
Handle fault of the optical
board/cross-connect board/
backplane of the opposite NE
Exclude the grounding fault
Exclude equipment
interconnection fault
Yes
No
N
If bit errors in this NE after
hardware loopback of the
optical interface ?
Exclude the faults of the
optical board/cross-connect
board/backplane of this NE
Exclude the faults of the
optical fibers/optical
interfaces/optical boards
If bit errors found during the
test while not found in
performance events?
4
1
Is the fault
cleared ?
If only this NE has B1
and B2 bit errors ?
Exclude the problems of
the clock tracing and the
cross-connect unit
Exclude the problems
of the environment and
the fan
Handle board problems of
this NE or previous NE
Handle board problems of this
NE or all the upstream NE
If extra-high equipment
temperature or if external
interference ?
Exclude this station fault
5
2
Is optical power
abnormal ?
Yes
Yes
Yes
Yes Yes
Yes
No
No
No
No
No
No
Trouble shooting
for bit error
If B3 bit error only ?
3
Yes
No
If anything wrong with the
DDF/cables/line boards/tributary
boards/backplane of this NE ?
If anything wrong
with grounding ?
Yes
No
No
Yes
No
Yes
U2000

Procedure
Step 1 Cause 1: The NEs have B1 and B2 bit errors
Troubleshooting
Issue 04 (2010-11-30)
1. Check for external causes. Eliminate the external causes such as extra-high equipment
temperature and external interference. For more information, refer to the 5.4.5 Checking
Ambient Temperature and 5.4.3 Checking External Interference.
2. Check the clock unite configuration. If there is incorrect configuration, re-configure the
clock.
WARNING
l The NE can trace the external clock BITS, line clock, tributary clock and internal clock. To
implement clock protection, at least two clock tracing sources are to be set.
l Usually, the tributary clock is not used as the reference clock of the clock subnet.
l Avoid timing loops when configuring clock sources.
Step 2 Cause 2: Only this NE has bit errors.
1. Check whether the optical power is normal. Refer to the 5.4.1 Checking Optical Power
to eliminate the faults of the optical fibers and optical interfaces on this NE and the opposite
NE.
2. Check the bit errors by the loopback mechanism. Eliminate the faults of the optical fibers
and optical interfaces on this NE and the opposite NE.
Step 3 Cause 3: The NE has B3 bit errors and reports the B3_EXC, B3_SD, and HP_REI alarms.
Step 4 Cause 4: The NE has BIP bit errors and reports the BIP_EXC and LP_REI alarms.
Step 5 Cause 5: Bit errors are found during instrument tests but not found in performance events.
1. Check whether there is any problem with the DDF, cables, line boards, tributary boards,
and backplane of this NE. Eliminate the faults if any.
2. Check whether there is any grounding problems. For more information, refer to the
Checking the Grounding.
3. Check whether the opposite equipment is faulty or not.
----End
5.4 Methods for Fault Locating
You can locate and handle bit errors based on the common causes that result in bit errors.
5.4.1 Checking Optical Power
Abnormal optical power is a common cause that results in bit errors.
5.4.2 Checking Power Cable
In the case of the services transmitted over cables, a cable failure is the common problem that
causes bit errors.
5.4.3 Checking External Interference
External electromagnetic interference may cause bit errors.
5-5
5.4.4 Checking the Grounding
Improper grounding may cause bit errors.
5.4.5 Checking Ambient Temperature
The ambient temperature in the equipment room must comply with the requirements. If the
temperature is very high or very low, it may cause bit errors.
5.4.6 Equipment Causes
If the external causes are excluded, you need to check whether the bit errors are caused by the
equipment itself.
5.4.7 Checking Clock Configuration
Incorrect clock configuration may also cause bit errors and pointer justifications.
5.4.1 Checking Optical Power
Abnormal optical power is a common cause that results in bit errors.
Common Fault Causes
Abnormal optical power of the line board is a common cause for bit errors. If the optical power
is very high or very low, it will cause abnormality of the optical module in receiving optical
signals and also cause bit errors B1, B2, B3 or BIP . Therefore, when the equipment reports a
large number of bit errors of various types, first test whether the receiving optical power of this
station is normal . In the case of indexes of optical interfaces, refer to the OptiX OSN
3500Intelligent Optical Transmission System Product Description.
Procedure
l Troubleshooting:
1. Check whether the line board matches with the transmission distance. If it does not
match, replace with a proper one.
2. If there is no proper line board, add an optical attenuator at the receiving end.
l For over-low optical power:
1. Check the transmitting optical power of the opposite station, and replace the faulty
line board.
2. Check whether the interfaces of the ODF, attenuator, flange and optical processing
board are connected well.
3. Check whether the interfaces of the ODF, attenuator, flange and optical processing
board are clean.
4. Check whether the bending radius of the optical fiber is not less than 60 mm.
5. Check the line board of the local station to see whether the receiver sensitivity matches
with the transmission distance. Replace with a proper line board.
----End
5.4.2 Checking Power Cable
In the case of the services transmitted over cables, a cable failure is the common problem that
causes bit errors.
Troubleshooting
Issue 04 (2010-11-30)
Common Fault Causes
When the power cables connected to the transmission equipment deteriorate, bit errors may
occur. Check whether the power cables connected to the equipment are correct. Prevent the
power cables from open solder point, dry point and poor contact.
When interconnecting the OptiX OSN 3500 with other equipment, check whether the
interconnection cables are normal when the interconnection equipment report bit errors.
Procedure
Step 1 Check whether the cable of the equipment is aging or whether the cladding surface falls off.
Step 2 Check whether the connection points of the cable are properly connected.
Step 3 Check whether the cable of the interconnection equipment is aging or the cladding surface falls
off.
----End
5.4.3 Checking External Interference
External electromagnetic interference may cause bit errors.
Common Fault Causes from External Interference
l Electromagnetic interference caused by the external electronic equipment.
l Electromagnetic interference caused by the power supply equipment.
l Electromagnetic interference caused by the lightning and high-voltage power transmission
line.
Locating and Handling Faults Caused by External Interference
Procedure
Step 1 Check whether any electromagnetic interference is caused by the external electronic equipment,
such as the power switch, fan, air conditioner, and radio generator in the transmission equipment
room.
Step 2 Check whether any electromagnetic interference (such as surge voltage or working frequency
interference) is caused by the power supply equipment.
Step 3 Check whether any electromagnetic interference is caused by the lightning and high-voltage
power transmission line.
----End
Improper grounding may cause bit errors.
Common Fault Causes
l PGND and BGND are poorly grounded and the grounding resistance is more than 10 ohms.
5-7
l The potential difference between BGND and PGND is more than 0.5 V.
l PGND, BGND share ground with AC zero line.
l The PGNDs of two interconnection equipments are not jointly grounded.
l The audio and trunk cables are poorly grounded.
Procedure
Step 1 Check whether the grounding bar in the equipment room is well grounded.
Step 2 Check whether the transmission equipment cabinet connects well with the grounding bar.
Step 3 Check the connection of the front door and side panel of the cabinet.
Step 4 Check whether the subrack connects well with the cabinet.
Step 5 Check whether the signal cable is well grounded.
Step 6 Check whether the DDF and ODF are well grounded.
Step 7 Check whether the NM equipment and various power consumption equipments are well
grounded.
Step 8 Check whether the interconnection equipment is jointly grounded.
----End
The ambient temperature in the equipment room must comply with the requirements. If the
temperature is very high or very low, it may cause bit errors.
Procedure
Step 1 Check whether the subrack fan is faulty.
Step 2 Check the equipment ventilation to prevent dust from accumulating on the air filter of the subrack
fan.
Step 3 Check whether the air conditioner in the equipment room works normally.
----End
5.4.6 Equipment Causes
If the external causes are excluded, you need to check whether the bit errors are caused by the
equipment itself.
Bit errors are usually generated when the following boards of the OptiX OSN 3500 fail.
l Optical (electrical) processing board
l Clock unit
l Cross-connect unit
l Tributary board
l Fan
After the equipment reports bit errors, analyze the features of the bit errors step by step to locate
the fault to a single station. Loopback method can be adopted to locate faults that occur on a
Troubleshooting
Issue 04 (2010-11-30)
board of a certain station. Then, use the replacement method to reset or replace the board that is
found to be faulty.
Deterioration of Processing Board
If there are bit errors of B1, B2 and B3 on the line, the clock board or the optical (electrical)
processing board may be faulty. First, check whether alarms are generated on the processing
board. If the bit errors of B1, B2 and B3 are reported only on the line board, the line board may
fail.
The deterioration of the optical (electrical) processing board usually refers to the deterioration
of one or more VC-4 paths of this processing board. In this case, the opposite station connected
to these VC-4s reports bit errors. When locating this kind of bit error, note the features of the
bit error report. If bit errors always occur to certain VC-4s, and if these VC-4s are transmitted
from a certain optical (electrical) processing board, check whether this board is faulty.
Deterioration of Clock Board
Bit errors caused by the clock board usually have the following characteristics:
l The station and the downstream station report many pointer justification events.
l The line board of this station reports B1 and B2 bit errors.
l The line board of the adjacent station connected to this station reports B1 and B2 bit errors.
l The tributary board of this station reports path bit errors.
l The path bit errors pass through this station, and are terminated and reported at the tributary
board of the downstream station.
Deterioration of Cross-Connect Unit
Bit errors caused by the cross-connect unit have the same characteristics as those of the clock
unit. The bit errors generated by the cross-connect unit always appear in certain VC-4s or
VC-12s.
Deterioration of Tributary Board
If there are lower order services at this station, the lower order bit error (BIP) is usually reported
when the tributary board fails. Therefore, if only-lower order bit errors are reported over the
network, the cross-connect unit or the tributary board may fail.
5.4.7 Checking Clock Configuration
Incorrect clock configuration may also cause bit errors and pointer justifications.
Incorrect configuration of the clock board may also cause bit errors and pointer justifications.
If the external factors are excluded, check whether the clock configuration is correct.
5.5 Cases on Bit Errors
This section provides the case analysis of bit errors.
Related cases:
5-9
None.
Troubleshooting
Issue 04 (2010-11-30)
About This Chapter
A pointer justification event means that some NEs are not completely synchronized in the SDH
network. If only a pointer justification event occurs, the services are not affected. To enhance
the transmission network stability, however, you need to find out the causes and eliminate the
pointer justification event.
The pointer justification is a specific phenomenon of the SDH network. When pointer
justification appears, it indicates that there are non-synchronized NEs in the SDH network.
6.2 Common Causes
Pointer justifications are usually generated due to external causes, equipment causes, and
The clock out-of-synchronization is the primary cause of pointer justification. Locate faults
mainly by handling problems related to the clocks. The fault should be located based on the
service direction, clock tracing direction, detection report location of pointer justification and
the generation location of pointer justification.
You can locate and handle faults based on the common causes that result in pointer justification.
6.5 Cases on Pointer Justification
This section provides the case analysis of pointer justification.
Troubleshooting 6 Troubleshooting the Pointer Justification
6-1
The pointer justification is a specific phenomenon of the SDH network. When pointer
justification appears, it indicates that there are non-synchronized NEs in the SDH network.
By handling the pointer justification in time, clocks of respective NEs can be synchronous in
the SDH network. Thus, the signal quality of the transmission can be ensured.
6.1.1 Mechanism of Pointer Justification
Pointer justifications occur when the clocks between the NEs are not fully synchronized.
6.1.2 Detection Report of Pointer Justification
The location where AU pointers are generated and reported is different from that of TU pointers.
6.1.3 Performance Events of Pointer Justification
When a pointer justification occurs, the associated performance events are reported.
6.1.1 Mechanism of Pointer Justification
Pointer justifications occur when the clocks between the NEs are not fully synchronized.
In an SDH network, there are two kinds of pointers: administrative unit pointer (AU-PTR) and
tributary unit pointer (TU-PTR). There are two corresponding pointer justifications, AU pointer
justification and TU pointer justification. The generation mechanism of these two kinds of
pointer justification is mostly the same. For details, see Chapter 1 "Generation of Alarm and
Performance" of the OptiX OSN 3500 Intelligent Optical Transmission System Alarms and
Performance Events Reference.
Generation Mechanism of AU Pointer Justification
See Figure 6-1, the E1 service between NE1 and NE6 passes through the intermediate NEs at
the VC-4 level. NE1 is the clock source, and the other NEs trace the clock signal of NE1
westwards. If the clocks of NEs 2 and 3 are not synchronous, the east optical board of NE2 and
the west optical board of NE3 generate the AU pointer justifications. These justifications may
cause the west optical boards of NEs 1, 4, 5 and 6 to generate pointer justifications.
l If the clock of NE2 runs faster than that of NE3, the east optical board of NE2 executes the
AU positive pointer justification. At the same time, the west optical board of NE3 executes
the AU negative pointer justification.
l If the clock of NE2 runs slower than that of NE3, the east optical board of NE2 executes
the AU negative pointer justification. At the same time, the west optical board of NE3
executes the AU positive pointer justification.
Figure 6-1 Generation of AU pointer
NE1 NE2 NE3 NE4
U2000
W W E W E W E E W
NE5 NE6
W
E1 E1
Troubleshooting
Issue 04 (2010-11-30)

Generation Mechanism of TU Pointer Justification
For the TU pointer, the TU pointer justification does not occur in the period of adapting the E1
signals into the VC-12s until including the VC-12s to the STM-1 signal. If there is frequency
offset between the E1 signal and the SDH clock, the E1 signal and the SDH clock can be
synchronized by adaptation.
See Figure 6-2. The E1 services are inserted in to NE1. Parts of the services are dropped on
NE2. Another part of the services passes through NE2 and is dropped on NE3. If the clocks of
NE1 and NE2 are not synchronous, the AU pointer justification occurs in the west boards of
NEs 1 and 2, and are then transformed into the TU pointer justification of NEs 1 and 2. The AU
pointer justification of the west optical board of NE2 generates the AU pointer justifications
occurring in the west optical board of NE3. The AU pointer justifications generated in the west
optical boards of NEs 2 and 3 are directly transformed into the TU pointer justifications of NE3.
Therefore, the TU pointer justifications are reported in NEs 1, 2 and 3.
Figure 6-2 Generation of TU pointer
NE1 NE2 NE3
U2000
W W W E
E1 E1 E1

6.1.2 Detection Report of Pointer Justification
The location where AU pointers are generated and reported is different from that of TU pointers.
When a local station generates an AU pointer justification, it neither detect nor report the AU
pointer justification. Instead, this station transmits the pointer justification information to the
remote station through the H1 and H2 bytes. The remote station will report the event of the AU
pointer justification by interpreting the H1 and H2 bytes. Therefore, in remote detection mode,
if the remote station reports the AU pointer justification event, it means that the pointer
justification is generated in the local station.
Take Figure 6-1 for example, the clocks of NE2 and NE3 are not synchronous, but neither the
east optical board of NE2 and nor the west optical board of NE3 may detect or report the AU
pointer justification performance event. The pointer justification, generated in the west optical
board of NE3, is detected and reported in the west optical board of NE4. The pointer justification,
generated in the east optical board of NE2, is detected and reported in the west optical board of
NE1.
6.1.3 Performance Events of Pointer Justification
When a pointer justification occurs, the associated performance events are reported.
6-3
Table 6-1 shows the performance events of the pointer justification supported by the OptiX
OSN 3500
Table 6-1 Performance events of pointer justifications
Acronym Detailed Information
AUPJCHIGH AU positive pointer justification count
AUPJCLOW AU negative pointer justification count
AUPJCNEW AU new pointer justification count
TUPJCHIGH TU positive pointer justification count
TUPJCLOW TU negative pointer justification count
TUPJCNEW TU new pointer justification count

6.2 Common Causes
Pointer justifications are usually generated due to external causes, equipment causes, and
Table 6-2 shows the common causes of pointer justification. They can be classified into external
causes, data configuration causes, and equipment causes. One cause or a combination of causes
may cause the pointer justification. Analyze the pointer justification one by one with related
fault locating methods based on actual situations.
Table 6-2 Common causes for the pointer justifications
Category Causes
External causes External clock signal degrade, for example, the external clock signal
provided by the equipment, such as building integrated timing supply
system (BITS).
Misconnection of optical fibers, thus leading to mutual tracing of two NEs.
Very high equipment temperature due to fans not being cleaned for a very
long time or the fans failed or the air conditioner in the equipment room
failed).
Unreasonable planning of the clock network (for example, the clock
tracing link is too long).
Data
configuration
causes
Multiple independent clock sources are configured in the same SDH
network.
Wrong configuration of the clock source level, thus leading to mutual
tracing of two NEs.
Troubleshooting
Issue 04 (2010-11-30)
Category Causes
The synchronization status message (SSM) protection function is not
correctly enabled. The function that should be enabled is not enabled. The
function that has been enabled is not correctly set.
Equipment
causes
Clock board failure or performance deterioration
Line board failure or performance deterioration
Cross-connect board failure or performance deterioration

The clock out-of-synchronization is the primary cause of pointer justification. Locate faults
mainly by handling problems related to the clocks. The fault should be located based on the
service direction, clock tracing direction, detection report location of pointer justification and
the generation location of pointer justification.
Fault Handling Flow
Figure 6-3 shows the procedures for handling the fault in the case of pointer justification.
6-5
Figure 6-3 Handling flowchart of service interruption pointer justification
If extra-high
temperature?
If the timing unit faulty?
Trouble shooting of
Pointer justification
If incorrect clock
configuration?
If the external clock
degraded?
If the NE clock
degraded?
Go to the next step
4
7
End
Contact Huawei for
technical support
Leave only one clock
synchronization source
Handle the fan fault
Correct the connection
of optical fibers
Use a clock source with
better clock quality
Replace the cross-connect
board
Yes
No
Handle the alarm
Handle extra-high
ambient temperature
If more than two clock
synchronization sources at
the same time?
Correctly configure
the clock
Replace the line board If the line board faulty ?
Replace the cross-connect
board
If the cross-connect
unit faulty ?
N
Handle the out-of-
synchronization
If any other alarm in
the network ?
Handle the out-of-
synchronization between
two upstream NE of this NE
Handle the out-of-
synchronization between the
previous NE and this NE
If optical fibers mis-
connected?
If the first station has the
AU pointer justification ?
If the fan fault ?
1
3
5
a
b
No
Yes
Yes
Yes
Yes
Yes
No
No
No
No
No
No
No
No
Yes
Yes
Yes
Yes
Yes
No
Yes
Yes
No
No
Yes
No
Yes
No
If the clock of the
interconnection equipment
out of synchronization ?
If equipment
interconnection involved ?
6
8
2
If the pointer
justification removed?
U2000
a: The first station refers to the station that first reports the pointer justification in the service direction, which
is the same as the clock direction, that is, in the clock tracing direction.
b: The first station has no AU pointer justification, that is, it only has the TU pointer justification. You should
handle the problem of TU pointer justification.

Troubleshooting
Issue 04 (2010-11-30)
Procedure
Step 1 Cause 1: Pointer justification is triggered by clock-related alarms.
The alarms related to pointer justification are listed as follows:
l SYN_BAD
l LTI
l SYNC_C_LOS
l EXT_SYNC_LOS
After the alarms are cleared, the pointer justification clears normally.
Step 2 Cause 2: The clock of the interconnected equipment is out of synchronization. For details, refer
to the 6.4.3 Checking Synchronization of Interconnection Equipment.
Step 3 Cause 3: The station reports the pointer justification performance events.
l If the first station has the AU pointer justification, You should handle the out-of
synchronization between two upstream NE of this NE.
l If the first station has the TU pointer justification, You should handle the out-of
synchronization between the previous NE and this NE.
Step 4 Cause 4: The clock is incorrectly configured.
For more information about pointer justification caused by incorrect clock configuration, refer
to the 6.4.1 Checking Clock Configuration Data.
Step 5 Cause 5: The operating temperature of the equipment is too high.
For more information about pointer justification caused by extra-high equipment temperature,
refer to the 6.4.2 Checking Ambient Temperature.
Step 6 Cause 6: The optical fibers are incorrectly connected.
For more information about pointer justification caused by fiber mis-connection, refer to the
6.4.4 Checking Connection of Optical Fibers.
Step 7 Cause 7: The performance of the external clock degrades.
For more information about pointer justification caused by external clock degradation, refer to
the 6.4.5 Checking Quality of External Clock.
Step 8 Cause 8: The performance of the NE clock degrades.
For more information about pointer justification caused by NE clock degradation, refer to the
6.4.6 Checking NE Hardware Faults.
----End
You can locate and handle faults based on the common causes that result in pointer justification.
6.4.1 Checking Clock Configuration Data
Incorrect clock configuration can result in clock out-of-synchronization. Follow these steps to
ensure the correctness of the configuration data and to locate the faults.
6-7
If the working temperature of the transmission equipment is extremely high, a pointer
justification event may occur. For this reason, after locating faults to a station, you need to check
the ambient temperature of the NE.
6.4.3 Checking Synchronization of Interconnection Equipment
During the interconnection between different types of equipment or between equipment from
different vendors, you need to check whether the clocks of the interconnecting equipment are
synchronized.
6.4.4 Checking Connection of Optical Fibers
In some network protection modes (such as path protection ring), services continue to be normal
even if the optical fiber is wrongly connected in the east and west directions. However, the clocks
trace each other, and thus pointer justifications may be generated.
6.4.5 Checking Quality of External Clock
The low precision of external clock sources may also generate pointer justifications.
6.4.6 Checking NE Hardware Faults
After eliminating the external causes, check whether the board of the NE where the pointer
justification is generated fails.
6.4.1 Checking Clock Configuration Data
Incorrect clock configuration can result in clock out-of-synchronization. Follow these steps to
ensure the correctness of the configuration data and to locate the faults.
Procedure
Step 1 Check whether the network is configured with more than two clock sources that result in pointer
justification.
Step 2 Check whether the traced clock source has a low precision. For example, the precision of the
access switch clock is low or there are too many tracing stations.
Step 3 Check whether the clock protection subnet is not set. After the main clock is lost (or fiber cut),
the non-protection of the clock causes the pointer justification.
Step 4 Check whether the level of the clock source is incorrectly set. After the clock protection
switching, clocks begin to trace each other, which results in the pointer justification.
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 station, which causes all the NEs in this clock subnet to be in
the free-run mode. Thus, the pointer justification is generated.
Step 6 Check whether the SSM clock protection is enabled. The clock quality deterioration and failed
protection switching can generate the pointer justification.
Step 7 When the SSM clock protection is not enabled, the SSM quality output is set as "Disable". Hence,
the clock quality transmitted to other NEs is not in use. The SSM will be automatically enabled
after some NE is started again. After the NE detects that the quality of all the line clock sources
is unusable, it will begin to trace the internal clock. At the same time, it will enter the free-run
mode, thus generating the pointer justification.
----End
Troubleshooting
Issue 04 (2010-11-30)
If the working temperature of the transmission equipment is extremely high, a pointer
justification event may occur. For this reason, after locating faults to a station, you need to check
the ambient temperature of the NE.
Procedure
Step 1 Check the subrack fan.
Step 2 Check whether the air filter is blocked with dust.
Step 3 Check whether the air-conditioner in the equipment room works normally.
----End
6.4.3 Checking Synchronization of Interconnection Equipment
different vendors, you need to check whether the clocks of the interconnecting equipment are
synchronized.
The network-wide clock out-of-synchronization does not definitely indicate a problem of the
transmission equipment itself. This problem may be due to improper planning of the network-
wide clock synchronization. For example, the interconnecting equipment traces a clock reference
source, whereas the transmission equipment traces another, thus resulting in a certain deviation
between the clocks of the two networks.
different vendors, first check whether the clocks of the interconnection equipment are
synchronized. Set the SDH equipment to use the same clock source with other equipment.
Otherwise, the pointer justification can also be generated.
NOTE
When the SDH is interconnected with other equipment, such as router, ATM equipment, switch, or
microwave equipment, pointer justifications may occur due to clock out-of-synchronization.
Pointer justifications generated during the equipment interconnection can be ignored if they do not affect
services. If it is necessary to eliminate the pointer justification, the clock source should be planned uniformly
for the interconnection equipment.
6.4.4 Checking Connection of Optical Fibers
In some network protection modes (such as path protection ring), services continue to be normal
even if the optical fiber is wrongly connected in the east and west directions. However, the clocks
trace each other, and thus pointer justifications may be generated.
Insert the MS_RDI alarm through the NM for the NE of which the optical fiber may be wrongly
connected, or query the ECC route. By using this operation, determine whether the optical fiber
is wrongly connected. If the optical fiber is misconnected, the pointer justification disappears
after correcting the connection.
6.4.5 Checking Quality of External Clock
The low precision of external clock sources may also generate pointer justifications.
6-9
Generally, check the quality of the external clock source by modifying the configuration of the
clock source.
Sometimes, the low precision of the external clock source traced by the SDH equipment may
generate network-wide pointer justifications. The switching of the upper level clock source of
the external BITS may also generate pointer justifications on the SDH equipment.
Quality factors of the external clock source, which can cause pointer justifications in the NE,
include the following:
l The precision of the clock source is low.
l The external clock source is unavailable.
l Power cables of the external clock deteriorate.
6.4.6 Checking NE Hardware Faults
After eliminating the external causes, check whether the board of the NE where the pointer
justification is generated fails.
Major factors that affect the NE clock quality include the following:
l The clock board fails or its performance deteriorates.
l The line board fails or its performance deteriorates.
l The cross-connect board fails or its performance deteriorates.
In this case, the major method of locating faults is to modify the clock configuration. First,
change the tracing direction of the clock. Then, analyze the fault and locate it to a specific board
of the NE based on the generation and disappearance of the pointer justification. Finally, replace
the board according to the actual situation, thus eliminating the pointer justification.
NOTE
Faults related to the clock boards and line boards are common. After eliminating the faults of the line boards
and clock boards, we should consider whether the cross-connect board fails. This is because the clock
generated by the clock board through phase-lock is first transmitted to the cross-connect board. After that,
it is distributed to the line board or the tributary board through the cross-connect board.
6.5 Cases on Pointer Justification
This section provides the case analysis of pointer justification.
Related cases:
None.
Troubleshooting
Issue 04 (2010-11-30)
7 Troubleshooting Equipment
Interconnection Faults
About This Chapter
To handle faults in equipment interconnection, you need to follow the basic methods and
procedures.
Equipment interconnection (EI) refers to the interconnection between the OptiX series
equipment and other sets of equipment.
Either the external or the equipment causes can result in the interconnection faults.
7.3 Methods of Locating Faults
This section describes common methods of locating and removing an equipment interconnection
fault.
7.4 Locating and Handling Faults
This section describes how to locate an EI fault and provides the troubleshooting procedures.
7.5 Cases on Equipment Interconnection
This section provides the case analysis of equipment interconnection.
Troubleshooting 7 Troubleshooting Equipment Interconnection Faults
7-1
Equipment interconnection (EI) refers to the interconnection between the OptiX series
equipment and other sets of equipment.
Other sets of equipment include the following:
l SPC switch
l PDH equipment
l SDH equipment
The interconnection signals include the following:
l PDH signals
l SDH signals
l Ethernet signals
7.1.1 Grounding
The equipment must be properly grounded to ensure that the system can work normally.
7.1.2 Higher Order Path Overhead Bytes C2 and J1
The main higher order path overheads relevant to EI are C2 and J1.
7.1.3 Processing Mode of C2 and J1
The bytes C2 and J1 are handled differently by the equipment of different types. When the
received values of the C2 and J1 bytes are different from the expected ones, their impact on
services varies according to the equipment type.
7.1.4 Arrangement of VC-12 Timeslots in a VC-4
There are two methods of numbering the tributary locations: sequential numbering (also called
path timeslot numbering) and interleaved numbering (also called line timeslot numbering).
7.1.5 Interconnection Between the Broadcast Data Interface of the OptiX Equipment and Other
Equipment
The OptiX series equipment supports the broadcast data interfaceasynchronous RS-232/
RS-422 serial interface. The OptiX equipment is connected to the data terminal equipment
through this interface. Point-to-point and point-to-multipoint transmission modes are available.
7.1.1 Grounding
The equipment must be properly grounded to ensure that the system can work normally.
Good grounding of the equipment has the following advantages:
l Ensures lightning protection, surge protection, and shockproof function.
l Resists possible electromagnetic interference.
l Avoids electromagnetic leaking in the transmission equipment.
According to relevant specifications, the grounding resistance value of the equipment is
recommended to be less than 10 ohms. The less the grounding resistance is, the better.
Bad grounding of the equipment directly affects the long-term stability of the operation of the
equipment and the service interconnection.
7 Troubleshooting Equipment Interconnection Faults
Troubleshooting
Issue 04 (2010-11-30)
Grounding of the Equipment Room
NOTE
The PGND refers to the protection ground, and the BGND refers to the battery ground (also called the
working ground).
Ensure joint grounding in the equipment room.
For an NE without joint grounding, test the grounding of the equipment before you install the
hardware.
l Before you switch on the power of the equipment, test the resistance between the two
grounding bars BGND and PGND. It should be 0 ohms.
l After you switch on the power of the equipment, check the voltage between the BGND and
PGND of the power distribution unit stud. The voltage should be 0 V.
Grounding of the DDF
If the equipment is connected to other equipment through the DDF, make sure that you connect
the DDF to the PGND.
Grounding of the 75-Ohm Coaxial Port
For grounding the external conductor (the shielding layer) of a 75-ohm unbalanced coaxial port,
connect the transmit and receive ends to the PGND or suspend the receive end. Certain
transmission equipment from other vendors connect the receive end and the transmit end to the
BGND.
Use a multimeter to check the voltage between the shielding layer of the coaxial port and the
PGND of the equipment. This helps in determining how the shielding layer of the coaxial port
is grounded.
During a signal connection, if the shielding layer is poorly grounded, the potential difference
and the AC interference between BGND and PGND affect the wave shape. This causes failure
in the interconnection.
Grounding of the 120-Ohm Port
For the 2 Mbit/s service of a 120-ohm balanced port, transmission is achieved through twisted-
pair cables in the differential mode. As a result, interconnection failure due to poor grounding
seldom occurs.
7.1.2 Higher Order Path Overhead Bytes C2 and J1
The main higher order path overheads relevant to EI are C2 and J1.
Signal Label Byte: C2
The C2 byte is used to indicate the structure of the higher order virtual container VC-3/VC-4/
VC-4-Xc and payload property.
The VC-3 has only one information structure which consists of C-3 plus POH and can load
34.368 Mbit/s tributary signals.
The VC-4 can be formed in the following two manners:
7-3
l Add path overhead (POH) to the C-4.
l Multiplex three TUG3s and then add POH.
The VC-4 composed of C-4 contains 139.264 Mbit/s tributary signals.
The VC-4 composed of three TUG3s consists of the following signals:
l 3x34.368 Mbit/s tributary signals when the TUG-3 is composed of VC-3s
l 63x2.048 Mbit/s tributary signals when the TUG-3 is composed of seven TUG-2s
The VC-4 can carry other types of signals also, such as the ATM or new service signals.
In ITU-T G.707, the C2 byte is defined as follows. Refer to Table 7-1.
Table 7-1 C2 byte coding
C2 Byte (Hex Code) Interpretation
00 Unequipped or supervisory-unequipped
01 Equipped - non-specific
02 TUG structure
03 Locked TU-n
04 34.368 Mbit/s or 44.736 Mbit/s
05 Mapping structure under development
12 Asynchronous mapping of 139.264 Mbit/s signal into C-4
13 ATM mapping
14 MAN (DQDB) mapping
15 FDDI mapping
16 HDLC frame signal mapping
17 SDL mapping with the SDH self-synchronization
scrambler (for further study)
18 HDLC/LAP-S frame signal mapping
19 SDL mapping with the reset setting scrambler (for further
study)
1A 10 Gbit/s Ethernet frame mapping (for further study)
1B Flexible mapping of the topological data link (for further
study)
CF Reserved
E1 - FC Reserved for national use
FE O.181 specific mapping
FF VC-AIS
Troubleshooting
Issue 04 (2010-11-30)

Path Trace Byte: J1
The J1 byte is used to repeatedly transmit a higher order path access point identifier (APID).
With this byte, you can make sure whether the path is correctly connected to the intended transmit
end by verifying the APID at the path receive end.
7.1.3 Processing Mode of C2 and J1
The bytes C2 and J1 are handled differently by the equipment of different types. When the
received values of the C2 and J1 bytes are different from the expected ones, their impact on
services varies according to the equipment type.
In the case of line interconnection, if the settings of the J1 and C2 byte are different at the two
ends, the trace identifier mismatch (HP_TIM) alarm or signal label mismatch (HP_SLM) alarm
is reported.
When the HP_TIM alarm or the HP_SLM alarm occurs, if the equipment inserts the AIS alarm,
services are interrupted, causing failure in interconnection.
When the J1 and C2 bytes are enabled, the line board on the OptiX series equipment does not
insert the AIS alarm if it detects that the received J1 and C2 bytes are different from the expected
values,.
The HP_TIM alarm or the HP_SLM alarm does not affect services and you can suppress the
alarm. To clear the HP_TIM alarm or the HP_SLM alarm, set the J1 and C2 bytes at the both
ends to the same values.
NOTE
When the J0 byte is enabled, the J0_MM alarm occurs on the interconnected equipment if the received J0
byte in the regenerator section overhead is different from the expected value. The AIS alarm, however, is
not inserted in normal cases.
The higher order path overhead can be processed using the pass-through mode or the termination
mode. The overhead pass-through and termination modes are described as follows:
l Pass-through: The equipment directly sends the received higher order path overheads to
the next NE. The local NE only detects the overhead bytes, but does not change the values
of the overhead bytes.
l Termination: The equipment labels the received higher order path overhead with their
default values and sends them out. The values of the overhead bytes to be sent to the opposite
NE are regenerated values or default values.
NOTE
Overhead detection: The equipment extracts the higher order path overheads and takes corresponding
actions or reports corresponding alarms based on the extracted value. Overhead detection does not change
the value of the higher order path overheads.
For overhead pass-through and overhead termination, see Figure 7-1.
7-5
Figure 7-1 Overhead pass-through and overhead termination
Line board
Overhead detection
A Overhead pass-through
Higher order
path overhead
Higher order
path overhead
B Overhead termination
Higher order path
overhead
Line board
Overhead detection
Higher order
path overhead

The overhead bytes can be set only in the mode of overhead termination. In other modes, the
default value of the overhead byte cannot be modified.
If the overhead is set to be terminated, ensure that the J1 and C2 bytes of the interconnected
equipment are the same.
The J1 and C2 bytes of the interface board can be modified on the NMS.
The overhead processing mode of the OptiX series equipment defaults to pass-through. The
mode needs not to be set separately for the equipment that is interconnected with the SDH
equipment in normal case. The equipment is not affected in the switching state.
7.1.4 Arrangement of VC-12 Timeslots in a VC-4
There are two methods of numbering the tributary locations: sequential numbering (also called
path timeslot numbering) and interleaved numbering (also called line timeslot numbering).
ITU-T recommends the following modes to multiplex E1 signals into a VC-4:
l Three TU-12s are multiplexed into one TUG-2.
l Seven TUG-2s are multiplexed into one TUG-3.
l Three TUG-3s are multiplexed into one VC-4.
The multiplexing structure of E1 signals is 3-7-3.
As the multiplexing is implemented in the byte interleaving mode, the 63 VC-12s in one VC-4
are not arranged in sequence.
The difference between the sequence number of the first VC-12 and that of the immediately next
VC-12 is 21.
When equipment of different vendors is interconnected, and if the locations of tributary signals
in the VC-4 are inconsistent, services are unavailable after the interconnection.
There are two methods of numbering the tributary locations: sequential numbering and
interleaved numbering. Refer to Table 7-2.
NOTE
By default, Huawei equipment applies the sequential numbering mode.
Troubleshooting
Issue 04 (2010-11-30)
Table 7-2 Path numbering
TUG-3 TUG-2 TU-12 Sequential
Numbering
Interleaved
Numbering
1 1 1 1 1
1 1 2 22 2
1 1 3 43 3
1 2 1 4 4
1 2 2 25 5
1 2 3 46 6
1 3 1 7 7
1 3 2 28 8
1 3 3 49 9
1 4 1 10 10
1 4 2 31 11
1 4 3 52 12
1 5 1 13 13
1 5 2 34 14
1 5 3 55 15
1 6 1 16 16
1 6 2 37 17
1 6 3 58 18
1 7 1 19 19
1 7 2 40 20
1 7 3 61 21
2 1 1 2 22
2 1 2 23 23
2 1 3 44 24
2 2 1 5 25
2 2 2 26 26
2 2 3 47 27
2 3 1 8 28
2 3 2 29 29
7-7
Numbering
Interleaved
Numbering
2 3 3 50 30
2 4 1 11 31
2 4 2 32 32
2 4 3 53 33
2 5 1 14 34
2 5 2 35 35
2 5 3 56 36
2 6 1 17 37
2 6 2 38 38
2 6 3 59 39
2 7 1 20 40
2 7 2 41 41
2 7 3 62 42
3 1 1 3 43
3 1 2 24 44
3 1 3 45 45
3 2 1 6 46
3 2 2 27 47
3 2 3 48 48
3 3 1 9 49
3 3 2 30 50
3 3 3 51 51
3 4 1 12 52
3 4 2 33 53
3 4 3 54 54
3 5 1 15 55
3 5 2 36 56
3 5 3 57 57
3 6 1 18 58
Troubleshooting
Issue 04 (2010-11-30)
Numbering
Interleaved
Numbering
3 6 2 39 59
3 6 3 60 60
3 7 1 21 61
3 7 2 42 62
3 7 3 63 63

Use the following formula to calculate the sequence numbers of the VC-12s in the timeslot
numbering mode:
VC-12 sequence number (sequential numbering mode) = TUG-3 number + (TUG-2 number -
1) x 3 + (TU-12 number - 1) x 21
Use the following formula to calculate the sequence numbers of the VC-12s in the line numbering
mode:
VC-12 sequence number (sequential numbering mode) = (TUG-3 number 1) x 21 + (TUG-2
number - 1) x 3 + TU-12 number
7.1.5 Interconnection Between the Broadcast Data Interface of the
OptiX Equipment and Other Equipment
RS-422 serial interface. The OptiX equipment is connected to the data terminal equipment
through this interface. Point-to-point and point-to-multipoint transmission modes are available.
RS-422 serial interface.
The RS-232 interface complies with ITU-T V.24/V.28.
The RS-422 interface complies with ITU-T V.11.
The broadcast data interface can realize full-duplex communications of universal asynchronous
receiver/transmitter (UART).
The OptiX equipment is connected to the data terminal equipment through this interface. Point-
to-point and point-to-multipoint transmission modes are available.
The serial interfaces are defined in Table 7-3.
Table 7-3 Interface pin assignment
Pin Signal Description
1 RS-422T+ Positive terminal of RS-422 transmitted data
difference
7-9
Pin Signal Description
2 RS-422T- Negative terminal of RS-422 transmitted data
difference
3 RS-422R+ Positive terminal of RS-422 received data
difference
4 RS-232RX RS-232 received data
5 GND Signal ground
6 RS-422R- Negative terminal of RS-422 received data
difference
7 - Undefined
8 RS-232TX RS-232 transmitted data

The RS-232 interface of the interconnected equipment can be interconnected to the serial
interface of the OptiX series equipment when the following requirements are met:
l The interface must be of the RS-232 level.
l The maximum rate is 19.2 kbit/s.
l When no data is sent, the port must be of the RS-232 high level (about 9 V).
l When using software for operation, only one slave station sends data to the master station
at one moment.
l The maximum cable distance is 15 meters.
The RS-422 interface of the interconnected equipment can be interconnected to the serial
interface of the OptiX series equipment when the following requirements are met:
l The interface must be of the RS-422 level.
l The maximum rate is 19.2 kbit/s.
l When using software for operation, only one slave station sends data to the master station
at one moment.
l The maximum cable distance is 1000 meters.
Either the external or the equipment causes can result in the interconnection faults.
Common EI fault symptoms are as follows:
l The interconnected services are unavailable.
l The services activated are abnormal (for example, the voice service is not clear and
disconnection often occurs during network access).
Table 7-4 lists common causes of equipment interconnection faults.
Troubleshooting
Issue 04 (2010-11-30)
Table 7-4 Common causes of equipment interconnection faults
Cause Type Cause
External
cause
The equipment is not jointly grounded or is poorly grounded.
Fibers or cables are wrongly connected.
Fibers or cables do not match (for example, single-mode fibers are used
together with multi-mode fibers, or 120-ohm cables are used together with
75-ohm cables).
The interconnected signal is too much attenuated or is not compliant with the
specifications.
Service configuration for the interconnected equipment is incorrect.
Equipment
cause
Overhead bytes in the SDH frame of the interconnected equipment are not
defined the same (such as C2, J1, J0, H1, H2, H3).
Performance indexes of the interconnected equipment fail to meet the
requirements.
Clocks of the interconnected equipment are not synchronized.
Types of interconnected optical/electrical interface boards do not match.
Models of the interconnection signals are different.
A fault occurs on the board.

7.3 Methods of Locating Faults
This section describes common methods of locating and removing an equipment interconnection
fault.
7.3.1 Common Methods for Locating Faults
This section describes the methods used to locate the interconnection faults.
7.3.2 Procedures
This section describes the normal procedure for locating an equipment interconnection fault.
7.3.1 Common Methods for Locating Faults
This section describes the methods used to locate the interconnection faults.
The common methods are as follows:
l Alarm and performance analysis
l Meter test
l Configuration modification
l Loopback
7-11
7.3.2 Procedures
This section describes the normal procedure for locating an equipment interconnection fault.
Context
Based on the signal types, the equipment interconnection may be one of the following:
l SDH line interconnection
l PDH tributary interconnection
l Auxiliary interface interconnection, such as the serial interface
Figure 7-2 shows the flow of troubleshooting a fault in the SDH line interconnection.
Figure 7-3 shows the flow of troubleshooting a fault in the PDH tributary interconnection.
Figure 7-4 shows the flow of troubleshooting a fault in the auxiliary interface interconnection.
Troubleshooting
Issue 04 (2010-11-30)
Figure 7-2 Flow of troubleshooting a fault in the SDH line interconnection
Go to the next
step.
Troubleshooting SDH
line interconnection
Transmission NMS
Yes
Yes
Yes
Yes
Yes
No
N
4
No
No
No
Yes
Yes
No
No
No
Yes
No
If the service tested
abnormal with a
meter?
Any line alarm like
R_LOS?
Is there the HP_TIM/
HP_SLM alarm?
Is there the HP_RDI
alarm?
Any bit errors/PJs?
Any wrong
configuration or any
VC-4 loopback?
Clocks out-of-sync.?
2
1
3
Fault cleared?
End
5
6
7
Abnormal fiber/cable
connection?
Yes
No
Replace the optical fiber
or optical interface
board.
Clean the optical
interface or replace the
board.
Unify the overhead
bytes or signal types.
Unify signal types or
interface modes.
Handle bit errors/PJs.
Modify/Unify the clock
source.
Contact Huawei
technical support.
Handle OptiX equipment
problems
Handle fiber/cable
connection problems.
Abnormal optical
power?
Types of optical interface
boards/fibers mismatch?
Yes
Yes
No
No
Handle problems of the
interconnected
equipment.
Bit errors/PJs persist
after an selfloop?
Handle problems of
opposite equipment or
cables.
Yes
No
Modify the configuration/
cancel the loopback.
NOTE
In Figure 7-2, N represents steps 1, 2, 3, , 7.

7-13
Figure 7-3 Flow of troubleshooting a fault in the PDH tributary interconnection
Go to the next
step.
Troubleshooting PDH
tributary
interconnection
Transmission NMS
Yes
Yes
Yes
No
Yes
No
N
4
No
No
Yes
Yes
No
No
No
Yes
No
If the service
tested abnormal
with a meter?
Any line alarm like
T_ALOS?
Is there the T_DLOS
alarm?
Any wrong
configuration
or any tributary
loopback?
Any cable problem
or opposite equipment
problem?
Equipment poorly
grounded?
Do the indexes of
interconnected equipment
meet the requirements?
2
1
3
Fault cleared?
End
5
6
7
Abnormal fiber/cable
connection?
Yes
No
Adjust the interconnected
cable or replace the board.
Reset the interface or
board.
Replace or correctly set the
interconnected board to make
signals consistent.
Modify the configuration/
cancel the loopback.
Handle problems of
cables or opposite
equipment.
Handle equipment index
problems.
Contact Huawei
technical support.
Handle OptiX equipment
problems.
Handle fiber/cable
connection problems.
Does the impedance
mismatch?
Signal
overattenuated?
Yes
Yes
No
No
Handle grounding
problems.
Handle grounding
problems.
Clocks out-of-sync.?
8
Modify/Unify the clock
source.
No
Yes
Yes
NOTE

Troubleshooting
Issue 04 (2010-11-30)
Figure 7-4 Flow of troubleshooting a fault in the auxiliary interface interconnection
Go to the next
step.
Troubleshooting
auxiliary interface
interconnection
Transmission NMS
Yes
No
Yes
Yes
Yes
No
N
4
No
No
Yes
No
No
Yes
No
Any line alarm like
R_LOS?
Interconnection
service with bit errors?
Does the interconnection
signal meet auxiliary interface
requirements?
Wrong configuration?
Wrong interface
connection?
Any cable problem
or opposite equipment
problem?
Interface properties
wrongly set?
2
1
3
Fault cleared?
End
5
6
7
Modify configuration or replace
the interconnected board.
Re-configure the service.
Correctly connect the
interface.
Reset interface
properties.
Contact Huawei
technical support.
Remove other faults and then
auxiliary interface faults.
Check/Replace the
interconnected cable or board.
Handle problems of cables or
opposite equipment.
Is the AUX board
faulty?
8
Replace the AUX board.
No
Yes
Is the SCC board
faulty?
No
9
Yes
Replace the SCC board.
Yes
No
Yes
NOTE

Checking and Analyzing Alarms and Bit Errors
When an EI fault occurs, check the alarms. Locate the fault by analyzing the alarms.Table 7-5
lists some of the alarms reported when an EI fault occurs, and the possible causes.
7-15
Table 7-5 Alarms relevant to EI faults and possible causes
Alarm Name Possible Cause
R_LOS, R_LOF l Fiber/cable connection fault
l Abnormal optical power
l Mismatch in types of optical interface boards or optical fibers
l Board fault
l Loss of clock
AU_LOP The signal types or interface modes of the interconnected equipment are
inconsistent.
For example, the overhead or pointer bytes are not defined the same.
AU_AIS l Errors in service configuration
l Faults in fiber/cable connection
l Board fault
J0_MM The J0 bytes of the interconnected equipment are not the same.
If the AIS alarm is not inserted, normal services are not affected.
HP_TIM The J1 bytes of the interconnected equipment are not the same.
HP_SLM The C2 bytes of the interconnected equipment are not the same.
HP_RDI The signal types or interface modes of the interconnected equipment are
inconsistent.
T_ALOS l Cable connection fault
l Impedance mismatch
l Signal overattenuated

After the EI, if the activated service is abnormal, for example, noise or slip in the speech, or the
speech being interrupted, query and analyze bit errors to locate the fault.
Use the NMS to query the performance events of all boards or paths to check the performance
quality of the path. If bit errors are detected, it indicates that the OptiX series equipment is faulty.
For the methods of clearing bit errors, refer to Chapter 5 "Troubleshooting Bit Errors."
When you use a meter for testing, and if you detect bit errors in the equipment interconnected
to the OptiX series equipment, or in the interconnected circuits, it indicates that one of the
following has occurred:
l A fault in the interconnected cables and connectors
l Clocks of the interconnected equipment not synchronized
l A fault in the opposite equipment
Troubleshooting
Issue 04 (2010-11-30)
Attaching a Meter to Test Services and Separating Fault Points
If a fault occurs in the interconnection, check if the OptiX series equipment is faulty.
Use the loopback method to locate the fault.
Attach a BER tester for a test at the SDH line side. See Figure 7-5.
Figure 7-5 Attaching a BER tester to test the SDH interconnection
OUT
IN
RX
TX
SDH analyzer/
BER tester
OUT
IN
SDH unit Cross-connect unit
OUT
IN
TX
RX
PDH unit SDH unit Cross-connect unit SDH unit

Attach a BER tester for a test at the PDH tributary side. See Figure 7-6.
Figure 7-6 Attaching a BER tester to test the PDH interconnection
TX
RX
TX RX
SDH analyzer/
BER tester
OUT
IN
SDH unit Cross-connect unit
OUT
IN
TX
RX
PDH unit PDH unit Cross-connect unit SDH unit

Procedure
Step 1 Select a service path. Connect the receive and transmit ends of the BER tester or SDH analyzer
to the PDH or SDH interface of the service path at the local NE.
Step 2 Perform an inloop at the PDH or SDH interface of the opposite NE. Set the BER tester to test
services.
Step 3 If the service is received by the tester and no bit errors occur within 24 hours, it indicates that
the OptiX series equipment is operating normally.
----End
7-17
7.4 Locating and Handling Faults
This section describes how to locate an EI fault and provides the troubleshooting procedures.
7.4.1 Checking Service Configuration
Incorrect service configurations may cause interconnection faults.
7.4.2 Checking Physical Connection
The incorrect connection of optical fibers and cables may also cause interconnection faults.
7.4.3 Checking the Optical Power
For line interconnection at the optical interface, check if the optical power is within the normal
range. Measure the optical power of the interconnected equipment.
For the interconnection of electrical interfaces, check the grounding and joint grounding of
equipment and cables of both the interfaces.
7.4.5 Checking Cable Distance and Signal Attenuation
If the trunk cable distance is too long, service interconnection may fail. For example, the service
is blocked or the activated service is often interrupted.
7.4.6 Checking the Structure of an Interconnected Signal
In the case of interconnection with SDH signals, check the interconnecting equipment at both
ends in terms of timeslot arrangement, overheads, pointers, and compatibility of protection
networking.
7.4.7 Checking Clock Synchronization of the Network
After the EI, ensure that the clocks in the SDH transmission network and the interconnected
network are synchronous.
7.4.8 Replacing Boards as Required
To locate a fault to a specific board, confirm this fault by replacing boards.
7.4.1 Checking Service Configuration
Incorrect service configurations may cause interconnection faults.
Analyze the configuration data of the interconnected equipment, including the following
parameters:
l Physical equipment parameters
l Logical equipment parameters
l Tributary board parameters
l Clock parameters
l Multiplex section switchover parameters
Analyze the data and modify the incorrect data to make sure that the configured data is correct.
In addition, if loopback is set for the tributary or line, services will be unavailable. Using the
NMS, you can check and release the loopback.
Troubleshooting
Issue 04 (2010-11-30)
7.4.2 Checking Physical Connection
The incorrect connection of optical fibers and cables may also cause interconnection faults.
Check if the cables and optical fibers between the interconnected equipment are properly
connected and avoid any open solder joint, dry joint and poor contact in the cables, and especially
cable misconnection.
Check the connection of the cables and fibers.
Ensure that there are no open solder joints, dry joints, poor contact, and wrong connections.
NOTE
Figure 7-7 illustrates a wrong cable connection. The switched 2 Mbit/s port A is connected to the 2 Mbit/
s port B of the transmission equipment, and the switched 2 Mbit/s port B to the 2 Mbit/s port A of the
transmission equipment. In this case, no T_ALOS alarm is reported. The occurrence of the alarm depends
on the signal input at the receive port. In this case, it is irrelevant whether the signal is correct or not.
Figure 7-7 2 Mbit/s signal interconnection
Switch
A
Transmission
B
A
B
A
Switch
B
A
B
Correct connection Misconnection
2M port
Transmission
2M port 2M port 2M port

7.4.3 Checking the Optical Power
For line interconnection at the optical interface, check if the optical power is within the normal
range. Measure the optical power of the interconnected equipment.
Make sure that the optical power meets the requirements mentioned in the engineering
documents and product manuals.
For details, refer to the Product Description.
Make sure that the interface boards at both ends match in terms of the optical module, receiver
sensitivity, and launched power.
Make sure that the jitter and frequency offset of the interface meet the specifications mentioned
in the manual.
Make sure that the fiber types at both ends match. For example, the single-mode fiber cannot be
used together with the multi-mode fiber.
For the interconnection of electrical interfaces, check the grounding and joint grounding of
equipment and cables of both the interfaces.
Use a meter to test if the grounding resistance of BGND and PGND meets the requirements.
The grounding resistance of DDF should also meet the required specifications.
7-19
Check if the shielding layers of the 75-ohm coaxial interfaces of both sets of equipment are
grounded in the same way. Also, check if they are properly grounded.
To clear a grounding fault, the best way is to use an oscilloscope to check if the wave shape of
an interconnected signal is distorted. Or you can use a multimeter to test. Disconnect all the
signal cables. Using a multimeter, measure the level between the shielding layers of the coaxial
cables at the receive and transmit ends of the OptiX series equipment. Repeat the method to
measure the level at the receive and transmit ends of the interconnected equipment.
The potential difference must be less than 20 mV. If it is higher, check if the difference is caused
by a fault in the service interconnection.
7.4.5 Checking Cable Distance and Signal Attenuation
If the trunk cable distance is too long, service interconnection may fail. For example, the service
is blocked or the activated service is often interrupted.
The maximum transmission distance of a 75-ohm 2 Mbit/s trunk signal should be 300 m, and
that of a 75-ohm 34 M/45 M trunk signal should be 140 m (equalization is needed).
If the transmission distance of the trunk signal exceeds the specified limit, it distorts the wave
shape of the interface. This may be because of the following reasons:
l Impedance mismatch
l Interference
l Poor reliability
Services are interrupted more frequently when they are interfered greatly.
Using a meter, check if the wave shape of an interconnected signal is deformed or distorted.
7.4.6 Checking the Structure of an Interconnected Signal
In the case of interconnection with SDH signals, check the interconnecting equipment at both
ends in terms of timeslot arrangement, overheads, pointers, and compatibility of protection
networking.
Timeslot Arrangement
In SDH signal interconnection, check the sequence of the timeslots that corresponds to the
tributary board path in the VC-4 mapping structure.
Overhead and Pointer
In SDH signal interconnection, check if the overheads and pointers of the interconnected
equipment are the same, including J0, J1, C2, H1, and H2.
In case there is a mismatch of signal structures, alarms such as J0_MM, HP_TIM, HP_SLM,
AU_LOP and HP_RDI are reported to indicate an interconnection failure.
If the overhead bytes are not the same, the overhead for the equipment of a party must be
redefined.
The definitions of the J0, J1 and C2 bytes of the OptiX series equipment can be modified using
the NMS. The H1 and H2 bytes, however, cannot be modified.
Troubleshooting
Issue 04 (2010-11-30)
Interconnection During Protection Networking
As the MSP functions of the transmission equipment from different vendors are incompatible,
it is not possible to interconnect the equipment of different vendors.
Independent of protection protocols, the SNCP functions of the equipment from different
vendors are compatible with each other.
7.4.7 Checking Clock Synchronization of the Network
After the EI, ensure that the clocks in the SDH transmission network and the interconnected
network are synchronous.
If the clocks are not synchronous, fault phenomena are different in the SDH line interconnection
and PDH tributary interconnection.
Clock Synchronization in the SDH Line Interconnection
The clock synchronization in the network can be reflected by pointer justification performance
events.
If a large number of pointer justification events occur, or a bit error alarm is raised, the OptiX
series equipment can be faulty.
Refer to Chapter 6 "Troubleshooting Pointer Justifications" to clear the fault and then take other
measures.
If the equipment operates normally, check if the clock processing performance of the
interconnected equipment is normal.
Clock Synchronization in the PDH Tributary Interconnection
In case the clocks are not synchronized when the OptiX series equipment is interconnected to
other equipment in the PDH tributary, no alarm and performance events occur in the OptiX
equipment. But, slip or service intermittence can occur in the PDH equipment.
Handling Clock Out-of-Synchronization
When the clocks in a network are not synchronized, it may not be caused by the transmission
equipment; instead it may be due to improper planning.
For example, the switch equipment traces one clock whereas the transmission equipment traces
another. As a result, there is an offset between the two clocks.
In this case, first make sure that the clocks within the transmission network of the OptiX series
equipment are synchronous. If the fault persists, adjust the scheme of the clock synchronization
to synchronize the clocks in the entire network.
For example, enable the switch and the OptiX series equipment to trace the BITS clock signal
with high precision. In this way, transmission performance is improved.
In the transmission network, the NE at the central station has a built-in reference clock so that
it can be traced by other NEs.
As a result, the specified requirements for synchronization are met and the majority of the switch
and mobile equipment can be interconnected.
The common solution is to modify the configuration.
7-21
NOTE
Pay attention to the differences between the clock signal transmission by the PDH equipment and by the
SDH equipment. The multiplexing structure of the PDH equipment is designed as the bit-interleaving mode,
which hardly damages the transmitted clock signals. But the SDH equipment is designed with the pointer
justification technique, jitter and wander are unavoidably introduced to the transmitted clock signals, thus
resulting in phase difference. As a result, the clock signals transmitted through the 2M path of the SDH
equipment are theoretically inferior to those transmitted through the PDH equipment. Hence, it is
recommended that you do not transmit 2M clock signals through the tributary interface of the OptiX series
equipment but transmit them through the clock input/output port of the equipment.
7.4.8 Replacing Boards as Required
To locate a fault to a specific board, confirm this fault by replacing boards.
Perform a loopback for each section to locate the fault. Once the fault is located on a board,
replace that board.
7.5 Cases on Equipment Interconnection
This section provides the case analysis of equipment interconnection.
Related cases:
l MC-B5 Interconnection with SONET Equipment Fails
l MC-B12 SEP1 Board Keeps Reporting AU_AIS Alarm
l MC-B17 As Multi-mode Port Uses Single-Mode Fibers, Interconnection Fails
Troubleshooting
Issue 04 (2010-11-30)
8 Troubleshooting Multiplex Section
Protection Switching Faults
About This Chapter
To handle the MSP switching faults, you need to understand the basic principle of MSP, common
causes of the MSP switching faults, and the troubleshooting methods.
The multiplex section protection (MSP) is an important way to realize the self-healing function
of the SDH transmission network.
8.2 Common Faults and Causes
The protection switching faults may occur due to external causes, incorrect data configuration,
or equipment causes.
This section describes the procedures for locating multiplex section faults.
8.4 Cases on Multiplex Section Protection
This section provides the case analysis of multiplex section protection.
Troubleshooting
8 Troubleshooting Multiplex Section Protection Switching
Faults
8-1
The multiplex section protection (MSP) is an important way to realize the self-healing function
of the SDH transmission network.
NOTE
This chapter considers the MS ring as an example to show how to troubleshoot MSP switching.
8.1.1 Multiplex Section Protection Classification and Protection Principles
The MSP can be classified into linear MSP and MSP ring, depending on the network topology.
8.1.2 Standards to Follow
The OptiX OSN 3500 complies with ITU-T Recommendations G.782/ G.783/ G.803/ G.841
about SDH protection switching.
8.1.3 Realization of MSP Switching
The MSP switching of the OptiX OSN 3500 is realized through a multiplex section module.
8.1.4 State Transition of the APS controller
The APS controller has five states and the migration of one state to another is controlled by
protocols.
8.1.5 MSP Switching Condition and Priority
MSP switching can be automatically triggered or be triggered by external switching requests.
8.1.6 K Byte
The K1 and K2 bytes, located in the MS overhead, are mainly used to transfer information during
switching.
8.1.1 Multiplex Section Protection Classification and Protection
Principles
The MSP can be classified into linear MSP and MSP ring, depending on the network topology.
The linear MSP can be classified into the following two types:
l Linear multiplex section (MS) 1+1 protection
l Linear multiplex section (MS) 1:N protection
The MSP ring can be classified into the following three types:
l Two-fiber bidirectional MSP ring
l Two-fiber unidirectional MSP ring
l Four-fiber bidirectional MSP ring
The commonest two-fiber bidirectional MSP ring is described in the following section.
Principle of Two-Fiber Bidirectional MSP Ring
For the protection switching process of a two-fiber bidirectional MSP ring, see Figure 8-1.
Faults
Troubleshooting
Issue 04 (2010-11-30)
Figure 8-1 Two-fiber bidirectional multiplex section shared protection ring
CA
CA CA
CA AC
AC AC
AC
S1/P2 S1/P2
S2/P1 S2/P1
A A
C C
D D
B B
S2/P1 S2/P1
S1/P2 S1/P2
(a) (b)
Switching

In the two-fiber bidirectional MSP ring, half of the optical fiber capacity in each direction is
allocated to working channels, and the other half is allocated to protection channels. In normal
situations, traffic signals from node A to node C are transmitted clockwise along fiber S1/P2,
and those from node C to node A are transmitted counter-clockwise along fiber S2/P1, as shown
in Figure 8-1 (a).
When the two fibers between node B and node C are cut off at the same time, as shown in Figure
8-1 (b), the selector of these two nodes connects fiber S1/P2 to fiber S2/P1. At node B, the traffic
signal timeslots, which enter the ring from node A and are sent along fiber S1/P2, are switched
to protection timeslots over fiber S2/P1 and then transmitted to node C. At node C, the traffic
signal timeslots, which enter the ring from node C and are sent along fiber S2/P1, are switched
to protection timeslots over fiber S1/P2 and then transmitted to node A.
In a two-fiber bidirectional ring, the working timeslots and protection timeslots are transmitted
over the same optical fiber in the respective directions. That is, an optical fiber transmits both
working signals and protection signals. Any fault in a receiver, transmitter, optical cable or node,
affects both the working channel and protection channel at the same time.
Features of Two-Fiber Bidirectional MSP Ring
The maximum service capacity with protection that is available in a ring is K x STM-N/2 (K
indicates the number of nodes on the ring). For the evenly distributed services between nodes,
the transmission capacity can be greatly increased, however, this kind of ring has no obvious
advantages for the centralized services.
For an STM-64 two-fiber bidirectional MSP ring, the first and second VC-4s are working
channels, and the third and fourth VC-4s are protection channels.
For an STM-16 two-fiber bidirectional MSP ring, the first through the eighth VC-4s are working
channels, and the ninth through the sixteenth ones are protection channels.
Four bits of K1 and K2 bytes are used to represent node numbers, so maximum number of nodes
in this ring is 16. Note that an REG does not occupy any node number.
For a ring without extra traffic, in the case that no request for a bridge is made earlier and the
fiber is shorter than 1200 km, the switching completion time should be less than 50 ms.
Switching Process
In a two-fiber bidirectional MSP, half of the optical fiber capacity is allocated to the working
channels, and the other half is allocated to the protection channels. The protection channels of
Troubleshooting
Faults
8-3
one optical fiber are used to protect the working channels of the other. Also, they both can be
used to transmit extra traffic. In the case of switching, extra traffic is discarded. As it is dual-
ended switching, that is, the nodes at both ends of the fault point are switched, a certain protocol
is needed. The K1 and K2 bytes in MS overhead are employed to transport the APS protocol.
Consequently, this kind of switching takes a longer time than path switching and has high
requirements for hardware and software of the equipment.
To prevent frequent switching due to line instability, the switching is not immediately restored
after the working channel is restored to normal. It is restored only after a certain period of time
elapses. This period of time, called wait-to-restore (WTR), is usually 512 minutes.
8.1.2 Standards to Follow
The OptiX OSN 3500 complies with ITU-T Recommendations G.782/ G.783/ G.803/ G.841
about SDH protection switching.
8.1.3 Realization of MSP Switching
The MSP switching of the OptiX OSN 3500 is realized through a multiplex section module.
The structure and the interface relations of this module are shown in Figure 8-2.
Figure 8-2 Multiplex section module (NM side)
Command Alarm Performance
Multiplex switching
algorithm
Board
M
u
l
t
i
p
l
e
x

s
e
c
t
i
o
n

m
o
d
u
l
e
Multiplex section
module at NE side
Multiplex section module
at board side

Figure 8-3 shows the relations between the multiplex section switching algorithm and the NE
side or board side.
Faults
Troubleshooting
Issue 04 (2010-11-30)
Figure 8-3 Relations between multiplex section switching algorithm and NE side or board side
NMS
APS Controller
state transition
of multiplex
section
algorithm
judgment
Line board
Start/stop
Parameter
setting
State/event
query
Set switching
mode
SD/SF
reporting
Transceive
K bytes
Cross-
connect
board
Perform
protection
switching
Event
record

In case a fault occurs on the line, the line board detects the signal degrade (SD) condition or the
signal fail (SF) condition, and then reports this condition to the cross-connect board. The cross-
connect board generates K byte according to automatic protection switching (APS) protocol and
send it through the line board. The line boards of other nodes receive K byte and report it to the
cross-connect board. The cross-connect board implements the APS protocol. Finally, the cross-
connect board specifies the switching status of each node according to the protocol, and perform
service switching.
The SF includes R_LOS, R_LOF, MS_AIS and B2_EXC. The SD includes B2_SD. The line
board monitors bit errors over the line through the B2_EXC and B2_SD alarms.
l When the bit error rate exceeds the B2 threshold-crossing value (10
-3
, by default), the
B2_EXC alarm is reported.
l When the bit error rate exceeds the B2 degrade threshold value (10
-6
, by default), the B2_SD
alarm is reported.
The function of SD starting multiplex section switching is disabled in the default state of the NE
software.
The automatic protection switch controller (APS Controller) can be started and shut down
through the NM. It can be started automatically, usually two minutes later, after configuration.
8.1.4 State Transition of the APS controller
The APS controller has five states and the migration of one state to another is controlled by
protocols.
The five types of APS controller states are shown in Table 8-1.
Table 8-1 APS controller states
State Indication
Protocol stop STOP
Protocol normal IDLE
Switching SWITCH
Troubleshooting
Faults
8-5
State Indication
Pass-through PASS
Wait to restore WTR

The protocol functions control the state transition according to the communication quality
information detected by the line board and the received K byte or external commands.
For the process of APS controller state transition, see Figure 8-4 and Table 8-2.
Figure 8-4 Process of APS controller state transition
PASS
IDLE STOP SWITCH
NOTE
The IDLE, SWITCH, and PASS states can directly migrated to the STOP state.

Table 8-2 Process of APS controller state transition
Proces
s No.
Transition
Condition
Common Problem Event Process
1 Receive a
command to
start the
protocol.
l The XCS resets.
l Re-send the
configuration data.
l Send a command of
protocol startup
through the NM.
The process of
re-starting the
protocol at a
station when
the protocol of
each station is
normal.
Omitted
2 Receive a
command to
stop the
protocol
Command to stop the
protocol is sent. The
cross-connect board
and clock board are not
in position.
The process of
protocol
stopping.
Omitted
Faults
Troubleshooting
Issue 04 (2010-11-30)
Proces
s No.
Transition
Condition
3 Receive the
non-request
code from
the short
path.
Fault recovery The MS
switching
alarm on the
MS ring is
cleared.
l Receive the non-
request code from
the short path.
l Cancel the K byte
pass-through.
l Send the non-
request codes to
both sides; the
protocol is restored
to normal.
4 Receive a
command of
confirming
bridge
switching
among other
stations.
Faults occur at other
stations.
The MS
switching
alarm occurs at
other stations.
l After receiving the
request for bridge
switching, perform
K byte pass-
through.
l After receiving the
acknowledgement
of bridge
switching, perform
service pass-
through.
5 Receive a
request for
bridge
restoration
from the
short path.
Fault recovery The MS
switching
alarm is
cleared on the
MS ring.
l After detecting the
disappearance of
SF or SD, send the
request for bridge
switching to the
long path and short
path.
l After receiving a
request for bridge
switching
restoration from the
short path, enter the
WTR state.
l After the wait-to-
restore time
expires, enter the
IDLE state.
Troubleshooting
Faults
8-7
Proces
s No.
Transition
Condition
6 Receive a
request for
bridge
switching or
a
confirmation
of bridge
switching
from the
long path.
Detect the SF or SD.
Receive an external
forced switching
command.
The MS
switching
alarm occurs at
other stations.
SF or SD, enter the
suspended
switching state SA.
l After receiving a
bridge switching
request or bridge
switching
confirmation, enter
the switching state.
7 Receive a
request for
long-path
bridge
switching
from the
non-local
node in the
currently
switched
side.
The process in which
the whole ring starts
the protocols in turn.
The process of
protocol
startup of
nodes on the
switched side.
Omitted
8 Receive a
request for
bridge
switching or
a
confirmation
for bridge
switching
from the
long path.
Detect the SF or SD
signal on one side of
the pass-through
station.
After cutting
off the optical
fiber on the
other side of
the switched
station, the
station
connected to
this optical
fiber changes
from the PASS
state to S state.
SF or SD signal,
send the request for
long-path and
short-path
switching. Then,
start a T1 timer, and
enter the SA.
l After receiving a
request for bridge
switching or
confirmation of
bridge switching
from the long path,
enter the switching
state. Then,
command the
cross-connect
board to switch the
page over.

8.1.5 MSP Switching Condition and Priority
MSP switching can be automatically triggered or be triggered by external switching requests.
Automatic MSP switching is triggered by SF and SD. In the case of the MSP switching is
triggered by external switching requests, external switching command is issued to make the
Faults
Troubleshooting
Issue 04 (2010-11-30)
status of the multiplex section changed. External switching requests are mainly related to the
lockout of protection, forced switching, manual switching, exercise switching and clear.
You can use the U2000 to perform forced switching and manual switching, lockout of protection
and exercise switching.
Table 8-3 describes various MSP switching modes.
Table 8-3 MSP switching modes
Mode Description
Forced
switching
Forced switching means switching the service forcibly from the working
channel to protection channel, regardless of the condition of the protection
channel. The forced switching ignores the status of the protection channel
unless the non-protection channel complies with the bridging request of a
higher priority. After the forced switching, the system is always be in the
switching state, and is not be switched back to the working channel unless
there is a manual interference.
Manual
switching
Manual switching means switching the service from the working channel to
protection channel. If the protection channel is normal, the switching occurs.
If it fails or is in service for a switching of higher priority, the manual
switching does not occur.
Lockout of
protection
No service, including normal service and extra service, is allowed to be
switched from the working channel to the protection channel. If the service
has been switched to the protection channel, the command forces it back to
the working channel even if the working channel is abnormal. Therefore, the
command may interrupt services. Hence be careful when executing it.
Exercise
switching
It is used to test whether the switching protocol works normally. Actually,
no switching occurs and the service is not affected.

For MSP, the following switching requests can bring a status change of the multiplex section.
Table 8-4 and Table 8-5 lists the MSP switching (or preemption) priorities.
Table 8-4 LMSP switching priorities
Priority Switching
Request
Description Trigger Condition
1 LPS_LP Lockout switching Lockout command issued on
the U2000, or SF detected in
the protection path
2 LPS_FS Forced switching Forced switching command
issued on the U2000
3 LPS_SF_H High priority path
invalid
SF of high priority detected
in the path
4 LPS_SF_L Low priority path
invalid
SF of low priority detected
in the path
Troubleshooting
Faults
8-9
Priority Switching
Request
5 LPS_SD_H High priority path
degraded
SD of high priority detected
in the path
6 LPS_SD_L Low priority path
degraded
SD of low priority detected
in the path
7 LPS_MS Manual switching Manual switching command
issued on the U2000
8 LPS_WTR WTR of the
switching
State request during the
switching
9 LPS_EXER Exercise switching Exercise switching
command issued on the
U2000
10 LPS_RR Reverse request Reverse request returned to
the received switching K
byte
12 LPS_DNR No restoration Switching request of
clearing the SF or SD in the
1+1 non-revertive mode
13 LPS_NR No request -

Table 8-5 RMSP switching priorities
No. Switching
Request
1 LP_S(SF_P) Lockout of Protection
- Span
An external command, or
signal failure on the
protection channel of a four-
fiber ring
2 FS_S Forced Switching to
Protection - Span
An external command
3 FS_R Forced Switching to
Protection - Ring
An external command
4 SF_S Signal Failure - Span Signal failure on a span of
the four-fiber ring working
channel
5 SF_R Signal Failure - Ring Signal failure on the
working channel of a four-
fiber or two-fiber ring
Faults
Troubleshooting
Issue 04 (2010-11-30)
No. Switching
Request
6 SD_P Signal Degrade -
Protection
Signal degrade on the
protection channel of a four-
7 SD_S Signal Degrade -
Span
Signal degrade on a span of
the four-fiber ring working
channel
8 SD_R Signal Degrade -
Ring
Signal degrade on the
working channel of a four-
9 MS_S Manual Switching to
Protection - Span
An external command
10 MS_R Manual Switching to
Protection - Ring
An external command
11 WTR Wait-to-Restore Status request between NEs
during the switching
12 EXER_S Exerciser - Span An external command
13 EXER_R Exerciser - Ring An external command
14 RR_S Reverse Request -
Span
A reverse request during the
switching
15 RR_R Reverse Request -
Ring
A reverse request during the
switching
16 NR No Request -

NOTE
When a reconstruction protocol is used for the MSP, the ring forced switching (SF_P) has a higher priority
than the protection channel failure (SD_P), and the manual ring switching (MS_R) and exercise switching
(EXER_R) has a higher priority than the protection channel failure (SF_P) and protection channel degrade
(SD_P) in the same section of a four-fiber MSP ring.
8.1.6 K Byte
The K1 and K2 bytes, located in the MS overhead, are mainly used to transfer information during
switching.
The following descriptions of the K1 and K2 bytes are only related to what we need in the MS
maintenance. For a detailed description, refer to ITU-T G.841.
K Byte of the Linear MSP
Bits 1 - 4 transmit the bridge request code, and bits 5 8 transmit the channel request code.
The bit arrangement for the K1 byte is shown in Figure 8-5.
Troubleshooting
Faults
8-11
Figure 8-5 Bit arrangement for K1 byte of linear MSP
b1 b2 b3 b4 b5 b6 b7 b8
Bridge request code
Channel request code

Channel request code (bits 5 8):
l 0: protection channel
l 1-14: working channel (1 for 1+1 mode)
l 15: extra service channel (for 1:N mode only)
Figure 8-6 Bit arrangement for K2 byte of linear MSP
b1 b2 b3 b4 b5 b6 b7 b8
Bridge channel code
Status 1+1/1:N
mode

K Byte of the Ring MSP
Bits 1 4 transmit the bridge request code, and bits 5 8 transmit the ID of the destination node
of the request code.
Figure 8-7 Bit arrangement for K1 byte of MSP ring
b1 b2 b3 b4 b5 b6 b7 b8
Bridge request code
Destination node identification

Destination node identification (bits 5 8):
As only four bits are available, the maximum number of NEs in an MSP ring is 16.
Figure 8-8 Bit arrangement for K2 byte of MSP ring
b1 b2 b3 b4 b5 b6 b7 b8
Source node identification Status Long/short
Faults
Troubleshooting
Issue 04 (2010-11-30)

The protection switching faults may occur due to external causes, incorrect data configuration,
or equipment causes.
A protection switching fault refers to the following:
l A fault caused by some unknown causes when the whole network is in the normal state.
l When the protection switching should be performed, the entire network is not in the
protection switching state or the protection switching state is incorrect.
l All or parts of services in a network are interrupted after the network is in the protection
switching state.
For common fault phenomena of MSP switching, see Table 8-6. The fault causes can be
classified into external cause, data configuration cause and equipment fault cause. The MSP
switching fault may be caused by one of these phenomena or by combination of them. Hence,
it is necessary to analyze the fault phenomena one by one with the basic fault locating methods
according to the actual situation.
Table 8-6 Common causes of MSP switching fault
Fault type Fault cause
External causes Optical fiber misconnection
Abnormal switching protocol
Manual insertion of MS_AIS, MS_RDI alarms
Data
configuration
causes
Incorrect service configuration in whole network
Incorrect multiplex section parameter configuration
Equipment
causes
Line board fault
Cross-connect board fault
Backplane fault

This section describes the procedures for locating multiplex section faults.
Fault Handling Flow
Figure 8-9 shows the procedures for handling the fault in the case of multiplex section faults.
Troubleshooting
Faults
8-13
Figure 8-9 Handling flowchart of multiplex section faults
MSP switching
fault handing
If the networkwide
switching protocol
state normal?
If the parameter
configuration incorrect?
If the protocol manually
halted/forced switch/alarm
insertion?
If the parameters lost?
If the hardware
faulty?
If the fault
removed?
Go to the next step
Yes
No
No
Yes
Yes
1
2
3
6
End
Contact Huawei for
technical support
Remove the
cross-connect
board fault
Configure the
parameters
Eliminate
personal factors
Yes
Yes
Swap or replace
the line board
If the line board faulty?
Yes
Yes
Yes
Replace the
backplane
If the backplane faulty?
N
Incorrect parameter
configurations
If the cross-connect
board not switched yet?
Yes
Locate the fault
section by section
according to an
interrupted trail
After equipment restart, if the
switching protocol normal ?
Yes
4
Turn to Service
Interruption Fault
Handling
If power supply
abnormal?
5
Eliminate the
power-supply fault
Yes
No
No
No
No
No
No
No
No
U2000

Procedure
Step 1 Cause 1: The protection switching protocol normally started with protection switching failed.
Faults
Troubleshooting
Issue 04 (2010-11-30)
Checking multiplex section protocol is a indispensable step to determine the fault. Query the
current status of each NE through the NM. If two adjacent NEs in the network are in "Switching
(S)", whereas the other NEs are in "Pass-through (P)", it indicates that the APS protocol is
normally started.
Although each NE is normal and the APS is started normally, the services are interrupted. In
this case, restart the protocol through the NM. After that, if the problem persists, check the board
according to a general method of fault handling.
Step 2 Cause 2: The protection switching protocol abnormal with protection switching failed.
In the case of APS protocol abnormality, there are generally two types of fault phenomena.
l The APS protocol cannot be started/stopped normally.
l Statuses of some or all of the NEs are abnormal.
The abnormal APS protocol may cause K byte pass-through and reporting of the problem, thus
causing the protection switching failure. If this occurs, check if the multiplex section parameters
of respective NEs are configured correctly and if some of them are lost. Check the optical board
and the cross-connect board in case of the normal parameter setting.
l For the revertive linear MSP, usually, set the WTR time to 600 seconds.
l For the MSP ring, pay attention to the following in parameter setting:
Counter-clockwise direction, active ring direction: The counter-clockwise direction is the
active ring direction. The left slot of the adjacent optical board on the NE is called west,
whereas the right slot is called east. In the counterclockwise networking, it is required to
connect the east optical boards of respective nodes in a ring to the west optical boards of
the downstream station, and connect the west optical boards of respective nodes to the
east optical boards of the upstream station.
Setting multiplex section ring parameters: These parameters include multiplex section
node number and WTR time. They must be set correctly, otherwise multiplex section
switching may fail.
Multiplex section node number: The multiplex section node number in a ring is 16. It is
recommended that the number starts from "0" and then increments along the active ring
NE by NE.
WTR: Usually, it is set to 600 seconds.
To locate faults, collect and analyze the K byte event records, and then find out the reasons
of the failed switching.
Step 3 Cause 3: The protocol manually halted/forced switch/alarm insertion?
1. Check whether the APS protocol is disabled due to improper operation, whether the forced
switching is incorrectly set, and whether the R_LOS, MS_AIS alarms are inserted due to
wrong operation. Eliminate human factors.
Step 4 Cause 4: After the equipment is restarted, the switching protocol is normal, but the protection
switching fails.
Refer to the 4 Troubleshooting Service Interruption for troubleshooting.
Step 5 Cause 5: The power supply of the equipment is abnormal.
1. Eliminate the faults of the power supply and storage battery.
Step 6 Cause 6: The hardware is faulty.
Troubleshooting
Faults
8-15
1. Check whether the line board is working normally. If no, replace the line board.
2. Check whether the backplane is working normally. If no, replace the backplane.
----End
8.4 Cases on Multiplex Section Protection
This section provides the case analysis of multiplex section protection.
Related cases:
None.
Faults
Troubleshooting
Issue 04 (2010-11-30)
About This Chapter
To handle the SNCP switching faults, you need to understand the basic principle of SNCP,
common causes of the SNCP switching faults, and the troubleshooting methods.
SNCP stands for subnet connection protection and is used to protect services among subnets.
The SNCP switching faults may be caused by external causes, incorrect data configuration, or
equipment causes.
Analysis of the SNCP switching faults should be carried out network-wide and it should comply
with the standard procedure. In troubleshooting, check whether the related NEs can correctly
receive related switching messages and whether they can execute the switching commands.
9.4 Cases on SNCP
This section provide the case analysis of SNCP.
Troubleshooting 9 Troubleshooting SNCP Switching Faults
9-1
SNCP stands for subnet connection protection and is used to protect services among subnets.
The SNCP is mainly used in the ring-with-chain network to protect services between the chain
and the ring.
9.1.1 SNCP Principle
The principle of the SNCP is "dual fed and selective receiving". That is, the receive end selects
the signal that has better quality from the two service sources that are sent from the transmit end.
9.1.2 Boards Involved in SNCP Switching
The boards involved in the SNCP switching include line board, cross-connect board and GSCC
board.
9.1.3 SNCP Trigger Conditions
The SNCP switching is triggered only in certain conditions.
9.1.4 SNCP Service Configuration
The SNCP is typically used in the ring-with-chain network. When configuring protection, you
must comply with the basic principles.
9.1.1 SNCP Principle
The principle of the SNCP is "dual fed and selective receiving". That is, the receive end selects
the signal that has better quality from the two service sources that are sent from the transmit end.
The signal selection of SNCP is performed on the cross-connect board. Table 9-1 compares
SNCP with MSP.
Table 9-1 Comparison between SNCP and MSP
SNCP MSP
Intended for the services between
subnetworks, applicable to the protection
of both end-to-end path and a part of the
protection path
Protects the services passing (or multiplex
section) fails, also called line protection.
Able to protect parts of the paths Protects the path based on the multiplex section
level
Dedicated protection mechanism Shared or dedicated protection mechanism
Applicable to various network topologies,
no limitation on the number of nodes in the
ring
It is only applicable to the ring topology and line
topology, the number of nodes in the ring is not
more than 16, and the number of nodes in the
line is not more than 14.
Permanent bridge at the transmit end and
switching at the receive end
Bridging and switching are performed upon
activation Head end/tail end means the bridging
node and switching node at the same time.
Single-ended switching Ring switching
Troubleshooting
Issue 04 (2010-11-30)
SNCP MSP
Able to form the DNI (Dual Node
Interconnection) protection structure
through SNCP
Unable to form the DNI protection structure
through MSP only
No need of the APS protocol, high
reliability
Needs the APS protocol in the network, low
reliability
Switch time is related to the service and the
network structure.
Switch time is less than 50ms, independent of
the service
Usually monitors the path overhead Monitors the multiplex section overhead

9.1.2 Boards Involved in SNCP Switching
The boards involved in the SNCP switching include line board, cross-connect board and GSCC
board.
Figure 9-1 shows the relations of the three boards.
Figure 9-1 Boards involved in SNCP switching
Cross-connect board
Line
board
Line
board
GSCC
Data report/
issue
Intra-board data
communication
Working source
Protection
source
Working sink
Intra-board data
communication

The line board monitors the SNCP service and reports the service state to the GSCC board. It
provides the real-time report to the GSCC board when the service state changes.
The cross-connect board collects the state information of the SNCP service, and completes the
service source switching based on the command sent by the GSCC board. At the same time, it
reports the collected SNCP service state changes to the GSCC board and completes the SNCP
service judgment, service route analysis and SNCP data generation.
9-3
9.1.3 SNCP Trigger Conditions
The SNCP switching is triggered only in certain conditions.
When the OptiX OSN 3500 receives alarms listed in Table 9-2, SNCP switching is triggered.
Table 9-2 SNCP trigger conditions
Switching
Condition
Related Alarm
Conditions for
higher order
SNCP
SF: R_LOS, R_LOF, R_LOC, MS_AIS, B2_EXC, AU_AIS, AU_LOP
SD: B3_EXC, B3_SD, HP_TIM, HP_UNEQ
Conditions for
lower order
SNCP
SF: HP_LOM, TU_AIS, TU_LOP
SD: BIP_EXC, BIP_SD, B3_EXC_VC3, B3_SD_VC3
The service
processing board
where the higher
order monitoring
points operate is
offline.
Signal Failure (SF) arises at all the higher order monitoring points on the
offline board.

9.1.4 SNCP Service Configuration
The SNCP is typically used in the ring-with-chain network. When configuring protection, you
must comply with the basic principles.
The SNCP is usually used in the ring-with-chain network. The node where the ring intersects
the chain adopts the following configuration rules to protect the services between the NEs in the
ring and chain.
l When configuring the SNCP protection service, the dual-fed feature of SNCP starts
functioning. The side where the service is configured is the working trail, whereas the other
side is the protection trail.
l The service added/dropped or passing through at the intersection node cannot be protected
through SNCP. In this case, the corresponding protection mode for the ring should be
configured.
l When the SNCP is configured in the MS, that is, on the intersected node, the switching
time delay must be configured. Otherwise, the switching occurs again, and the services are
interrupted for several times.
l When the SNCP is configured in the MS, or the configuration of the SNCP involves an
intersecting node, HP_UNEQ must be configured as the switching condition. Otherwise,
in the case of selectively receiving, the SNCP service is not switched to the protection path
and the service is interrupted.
Troubleshooting
Issue 04 (2010-11-30)
The SNCP switching faults may be caused by external causes, incorrect data configuration, or
equipment causes.
The SNCP switching fault refers to the network that is not in the protection switching state when
the switching occurs, or when all or parts of the service in the network are interrupted.
Table 9-3 shows the common SNCP switching faults and related causes, including the external
causes, data configuration causes and transmission equipment causes.
Table 9-3 Causes of the SNCP switching faults
Fault types Fault causes
External causes Wrong fiber connection
SNCP not supported by the board of this version
Mis-operation by the maintenance personnel
Data configuration
causes
Incorrect setting of the SNCP switching triggering conditions
Incorrect setting of the SNCP switching attributes for the node where
the ring intersects the chain
Incorrect configuration of the SNCP services at the source/sink stations
Incorrect configuration of the SNCP services at relevant pass-through
stations
Equipment causes Abnormal operation of the cross-connect board
Abnormal operation of the line board

Analysis of the SNCP switching faults should be carried out network-wide and it should comply
with the standard procedure. In troubleshooting, check whether the related NEs can correctly
receive related switching messages and whether they can execute the switching commands.
Fault Handling Flow
Figure 9-2 shows the procedures for handling the fault in the case of SNCP switching fault.
9-5
Figure 9-2 Handling flowchart of SNCP switching fault
Restore the fiber and cut
off that in the other
direction, to turn the ring
into bidirectional link
Trouble shooting
for SNCP switching
End
Connect Huawei for
technical support
Go to the next step N
If the fault
removed?
1
2
3
4
5
a
If the SCNP ring
complete?
If the interrupted service
not switched over yet?
Analysis alarm and
Performance, judge the fault
positon of SNCP ring
Cut off the fiber in one direcition, to
turn the ring into the bidirectioinal link
If the service restores
to normal?
loopback section by
section to locate the fault
to the single station
If fiber
mis-connection?
Connect the optical
fiber again
Correct the SNCP
switching startup
conditions
Correct SNCP
switching attributes
Correct SNCP services
in the source/sink stations
Correct SNCP services in the
relevant pass-through stations
Replace the
SCC board
Replace the cross-
connection board
Replace the
line board
If incorrect SNCP
service configuration
If SNCP switching
startup condition
configuration incorrect
If SNCP switching attributes
configuration incorrect
If SNCP switching services
configuration at source/sink stations
incorrect
If the trigger information
of protection switching
not received yet?
If SNCP services in the
relevant pass-through
stations incorrect
If the boards
abnormal?
If the SCC board
abnormal?
If the cross-connection
board abnormal?
If the line board
abnormal?
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
No
No
No
No
No
No
No
No
No No
No
No
No
No No
U2000

Procedure
Step 1 Cause 1: The SNCP ring is not complete when the fault occurs.
1. Loop back section by section to locate the fault to the single station
Step 2 Cause 2: The fibers are incorrectly connected at the faulty station.
NOTE
The SNCP adopts the "dual fed and selective receiving" protection mechanism. Therefore, under normal
operating conditions, wrong fiber connection does not affect service transmitting or receiving. When the
SNCP switching occurs, however, the SNCP service will be switched to the protection trail, and inverse
fiber connection affects the service. Therefore, fiber connection should be checked at the faulty station.
Troubleshooting
Issue 04 (2010-11-30)
1. Connect the optical fibers again.
Step 3 Cause 3: The SNCP service configuration is incorrect at the faulty station.
1. Whether the triggering conditions are correctly set and if the alarms that may trigger SNCP
switching are received.
2. Whether the protection attributes of SNCP are correctly configured at the ring or chain
intersection station.
3. Whether the protection attributes are correctly configured at the source or sink stations
according to respective network structures.
4. Whether pass-through is configured at related intermediate stations.
Step 4 Cause 4: The faulty station does not receive the trigger information of protection switching.
1. Check whether the SNCP services. are correctly configured at relevant pass-through
stations. If no, correct the SNCP service configuration at the pass-through stations.
Step 5 Cause 5: The boards are not working normally.
1. Check whether the SCC board is working normally. If no, replace the SCC board.
2. Check whether the cross-connect board is working normally. If no, replace the cross-
connect board.
----End
9.4 Cases on SNCP
This section provide the case analysis of SNCP.
Related cases:
None.
9-7
10 Troubleshooting Clock Protection
Switching Fault
About This Chapter
To handle a fault that occurs in clock protection switching, you need to know the basic principles
of protecting a clock, and the common causes that occur in a fault. In addition, you need to know
the method for locating and handling a fault.
To understand clock protection switching, you need to know the clock quality, SSM transmission
mode, clock protection principle, and relevant board and parameter setting.
To analyze the clock protection switching faults, you need to understand their causes.
The analysis of the faults of clock protection switching should be performed network-wide.
10.4 Cases on Clock Protection
This section provides the case analysis of clock protection.
Troubleshooting 10 Troubleshooting Clock Protection Switching Fault
10-1
To understand clock protection switching, you need to know the clock quality, SSM transmission
mode, clock protection principle, and relevant board and parameter setting.
10.1.1 Clock Quality
The synchronous status message (SSM) is a group of codes that represent the clock quality grade
in the synchronization network.
10.1.2 SSM Transmission Mode
When the SSM is transmitted in a transport network and in the BITS equipment, different
transmission modes are used.
10.1.3 Principle of Clock Protection
To understand clock protection, you need to learn the clock tracing direction and the automatic
protection switching (APS).
10.1.4 Configuration of Clock Protection Switching
To enable the clock automatic protection switching, configure some parameters.
10.1.5 Boards Involved in Clock Protection Switching
The clock protection switching needs to start the protocol. It involves the line board, cross-
connect clock board and SCC board to carry out different functions.
10.1.1 Clock Quality
The synchronous status message (SSM) is a group of codes that represent the clock quality grade
in the synchronization network.
The ITU-T uses four bits to define the synchronization status message byte (SSMB). Table
10-1 shows the ITU-T-defined SSM codes that represent the quality grades of 16 synchronization
sources. SSMB = 2 corresponds to the highest grade, whereas SSMB = f corresponds to the
lowest grade.
Table 10-1 SSM codes
S1(b5-b8) SDH Synchronization Quality Grade Description
0000 Quality unknown (existing sync. network)
0001 Reserved
0010 Rec. G.811 clock signal (PRC, cesium clock)
0011 Reserved
0100 Rec. G.812 transit office clock signal (SSU-A, rubidium clock)
0101 Reserved
0110 Reserved
0111 Reserved
1000 Rec. G.812 local office clock signal (SSU-B, rubidium or crystal clock)
Troubleshooting
Issue 04 (2010-11-30)
S1(b5-b8) SDH Synchronization Quality Grade Description
1001 Reserved
1010 Reserved
1011 Synchronous equipment timing source (SETS) signal (SEC, crystal clock)
1100 Reserved
1101 Reserved
1110 Reserved
1111 Not used for synchronization

NOTE
Note that the SSMB and the S1 byte are different in concept. The SSMB is a group of message codes that
represent the clock quality grade (see the preceding table). The S1 byte is a byte in the SDH section
overhead, and its less significant four bits are the SSMB.
10.1.2 SSM Transmission Mode
When the SSM is transmitted in a transport network and in the BITS equipment, different
transmission modes are used.
In an SDH transmission network, the SSM is transmitted through the less significant four bits
(b5b8) of the S1 byte in the SDH section overhead. In the BITS equipment, the SSM is
transmitted through a certain bit of the first timeslot (TS0) in the 2 Mbit/s clock signal. Therefore,
the 2 MHz clock signal cannot carry SSM.
10.1.3 Principle of Clock Protection
To understand clock protection, you need to learn the clock tracing direction and the automatic
protection switching (APS).
Clock Tracing Direction in an SDH Synchronization Network
In the SDH network, each NE is finally synchronized with the primary reference source by
following a certain synchronization trail, thus achieving the network-wide synchronization. As
shown in Figure 10-1, the clocks of all NEs are synchronized to a primary reference, that is, the
active building integrated timing supply (BITS).
Usually, there is more than one synchronization trail for an NE. As shown in Figure 10-1, NE4
can select to trace either the west clock or the east clock. These two sources are traceable to the
same primary reference.
10-3
Figure 10-1 Clock tracing direction in SDH synchronization network
NE2
NE1
NE3
NE4
NE5
NE6
NE
Clock reference source
Clock tracing direction
Active
BITS
Standby
BITS
Active
BITS

Clock APS
In a synchronization network, it is essential to maintain synchronization among the NEs. To
prevent the network-wide out-of-synchronization being caused by the failure of one
synchronization trail, the automatic protection switching of the synchronization clock is
required.
Take NE4 in the preceding figure as an example. If the west clock is lost, NE4 can switch to
trace the east clock instead.
After the automatic protection switching, the new clock source may derive from the same
primary reference source as the previous one (for example, the active BITS) or from a primary
reference of low quality (for example, the standby BITS).
10.1.4 Configuration of Clock Protection Switching
To enable the clock automatic protection switching, configure some parameters.
Clock Source
According to the clock source list used by the current NE, complete the configuration, such as
priority levels, recovery parameters, switching conditions, and switching state of the clock
source.
Troubleshooting
Issue 04 (2010-11-30)
Clock Subnet
Pay attention to the following aspects when configuring the clock subnet.
l The NEs tracing the same clock need to be arranged into the same subnet.
l The division principle of the clock subnet is that the clock tracing chain is not too long (not
more than seven NEs), and the aim is to prevent clock degrade.
l The NEs based on synchronization status message (SSM) clock protection must be arranged
in one clock protection subnet. Otherwise, SSM will not be activated at the left of the NEs
outside of the clock protection subnet, which may cause wrong clock tracing switching.
Synchronization Status Message Byte
If there is an external clock source and the signal is 2 Mbit/s, it is necessary to configure the
synchronization status message byte.
The SSM is represented by SA4, SA5, SA6, SA7 or SA8, and is transmitted through a bit of the
first timeslot (TS0) in the 2 Mbit/s clock signal.
Enable Clock Protection Protocol
Start the clock protection protocol of the GSCC board and make sure that the clock board is in
the SSM mode (that is, detect SSM).
The process to start the clock protection protocol is as follows:
When the clock protection protocol is enabled, the GSCC board will automatically send a
command to the clock board and allow it to enter the SSM mode. When the clock protection
protocol is disabled, the GSCC board will order the clock board to exit from the SSM mode.
Select Enable SSM to enable the protocol and S1 byte at the same time on NM.
10.1.5 Boards Involved in Clock Protection Switching
The clock protection switching needs to start the protocol. It involves the line board, cross-
connect clock board and SCC board to carry out different functions.
In the course of clock protection switching, boards of different types perform different functions.
l Line board
It is used for the insertion and extraction of the S1 byte. The line board inserts the S1 byte sent
by the SCC board into the section overhead and extracts the S1 byte from the section overhead
and sends it to the SCC board for further processing.
l Cross-connect and timing board
It completes the extraction of the SSM from the external clock and the clock source switching.
l SCC board
In the OptiX OSN 3500 system, the SCC board processes the clock protection protocol. The
SCC board, after receiving the SSMs from the line board, and cross-connect and timing board,
determines the clock source that the cross-connect and timing board should trace according to
the protocol and sends a command to the cross-connect and timing board for switching. At the
same time, the SCC board sends the SSMs of the current clock source to all the remaining line
boards.
10-5
To analyze the clock protection switching faults, you need to understand their causes.
Common faults are as follows:
l Unreasonable allocation of network-wide clock sources. As a result, two or more master
clocks appear and a large amount of pointer justifications occur in the relevant NEs.
l Although the clock protection switching protocol is normally started, the protection
switching fails, resulting in pointer justification and service interruption.
l Clock protection switching protocol is abnormal. It leads to the failure of protection
switching, pointer justification and service interruption.
Table 10-2 shows phenomena and causes of common faults. There are three types of faults:
external, data configuration, and hardware.
Table 10-2 Causes of common faults
Fault types Fault causes
External causes Wrong fiber connection which causes traced clock source error
Relevant clock information is not provided by the clock signals in the
external clock source.
Data
configuration
causes
The clock protection protocol is not started normally.
Incorrect settings of the NE traced clock source priority
Incorrect recovery parameter configuration of the clock source
Equipment
causes
Abnormal operation of the EXCS/GXCS/UXCSA/SXCSA board, line
board, and GSCC board

The analysis of the faults of clock protection switching should be performed network-wide.
Fault Handling Flow
The sequence for locating faults are as follows:
1. Check whether the configuration of the clock tracing mode in each NE is correct.
2. Check whether the protection switching protocol is normally started.
3. Check whether the clock signals of the external clock source of the corresponding NE are
correctly output.
Figure 10-2 shows the procedures for handling the fault in the case of clock protection switching
fault.
Troubleshooting
Issue 04 (2010-11-30)
Figure 10-2 Handling flowchart of clock protection switching fault
Fault handling
of clock protection
switching
If false configuration
of external clock source?
If false clock tracing mode?
Change the network-wide
clock tracing mode
2
4
If false configuration of
network-wide clock protections
witching protocol
If relevant NEs added
into the subnet?
Add the relevant NEs
into the clock protection
subnet
3
If abnormal startup of relevant NE
clock protection switching
protocols?
Start the clock protection
switching protocols
of the relevant NEs
If no clock signals outputed
from relevant NE's external
clock sources?
Debug the external
clock source to ensure
the normal signal output
If no SSMB carried by
the external clock sources?
Manually configure
the relevant SSMB
Configure the sa
byte again
If the sa byte incorrectly
set in external clock sources?
If the optical fiber connection
direction matched with the
clock tracing mode?
Connect the optical fiber
between NES again
Yes
Contact Huawei for
technical support
If faulty board?
5
If faulty line board?
Replace line
board
If faulty EXCS/GXCS
board?
Replace XCS
board
If faulty SCC board?
Replace SCC
board
Go to the
next step
N
If the fault
removed?
End
No
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
No
Yes
Yes
No
Yes
No
Yes
No
Yes
No
No
Yes
1
U2000

Procedure
Step 1 Cause 1: The optical fiber connection mode between the NEs does not match the clock tracing
mode.
For the clock protection, the direction of each NE clock source must match the fiber connection
direction of the NE. And the eastbound and westbound optical fibers must be correctly
connected. This matching must be checked first in the case of a clock protection failure.
10-7
1. Connect the optical fibers between the NEs again.
Step 2 Cause 2: The clock tracing mode of the NEs is incorrect.
When the clock protection switching fails, you need to check whether the clock priority is
correctly configured to the NEs in the network. Because the network-wide clock configuration
mode is involved in clock protection switching, during troubleshooting, check the clock tracing
configuration of each NE on the basis of the clock switching protocol and check whether there
is clock mutual tracing caused by wrong priority configuration.
1. Change the network-wide clock tracing mode.
Step 3 Cause 3: The network-wide clock protection switching protocol is incorrectly set.
1. Check whether relevant NEs have been added into the clock protection subnet. If no, add
them into the clock protection subnet.
2. Check whether relevant NE clock protection switching protocols are started normally. If
no, start the clock protection switching protocols of the relevant NEs.
Step 4 Cause 4: The external clock sources of the relevant NEs are incorrectly set.
1. Check whether the external clock sources of the relevant NEs output any clock signals. If
no, debug the external clock sources to ensure the normal output of clock signals.
2. Check whether the external clock sources of the relevant NEs carry any SSMB information.
If no, manually configure the relevant SSMB information.
3. Check whether the sa byte is correctly set in the external clock sources of the relevant NEs.
If no, set the sa byte again.
Step 5 Cause 5: The boards are not working normally.
1. Check wether the clock board is working normally. If no, replace the clock board.
3. Check wether the SCC board is working normally. If no, replace the SCC board.
----End
10.4 Cases on Clock Protection
This section provides the case analysis of clock protection.
Related cases:
None.
Troubleshooting
Issue 04 (2010-11-30)
11 Troubleshooting Tributary Protection
Switching Fault
About This Chapter
To handle a TPS protection switching fault, you need to know the basic principles of TPS
protection, and the common causes that result in a fault. In addition, you need to know the method
for locating and handling a fault.
The TPS is a protection function provided by the equipment. The TPS function is implemented
to protect other tributary processing boards on the basis of a standby tributary processing board.
The TPS switching faults may occur due to external causes, incorrect data configuration, and
equipment causes.
This section describes the procedures for locating TPS faults.
11.4 Cases on TPS Protection
This section provides the case analysis of TPS protection.
Troubleshooting 11 Troubleshooting Tributary Protection Switching Fault
11-1
The TPS is a protection function provided by the equipment. The TPS function is implemented
to protect other tributary processing boards on the basis of a standby tributary processing board.
11.1.1 TPS of the OptiX OSN 3500
Tributary protection switching (TPS) is intended to protect several (N) tributary processing
boards through a standby tributary processing board.
11.1.2 Working Principle
It introduces the working principle of TPS.
11.1.1 TPS of the OptiX OSN 3500
Tributary protection switching (TPS) is intended to protect several (N) tributary processing
boards through a standby tributary processing board.
l It supports one group of 1:N (N8) TPS for E1/T1 services in the main subrack and the
extended subrack.
l It supports two groups of 1:N (N3) TPS for E3/T3 services in the main subrack and the
extended subrack.
l It supports two groups of 1:N (N3) TPS for E4/STM-1(e) services in the main subrack.
l It supports two groups of 1:1 TPS for Ethernet services in the main subrack.
l It supports one group of 1:N (N8) TPS for DDN services in the main subrack.
l It supports the coexistence of three types of TPS protection groups.
The protection modes of the electrical processing board are shown in Figure 11-1, Figure
11-2, Figure 11-3, Figure 11-4, Figure 11-5, Figure 11-6, Figure 11-7, and Figure 11-8.
NOTE
In the following figures, "W" indicates working board and "P" protection board.
Figure 11-1 Protection mode of E1/T1 processing board
S
2
7
S
1
9
S
2
0
S
2
1
S
2
2
S
2
3
S
2
4
S
2
5
S
2
6
S
3
7
S
2
9
S
3
0
S
3
1
S
3
2
S
3
3
S
3
4
S
3
6
S
3
5
S
2
8
S
1
S
2
S
3
S
4
S
5
S
6
S
7
S
8
S
9
S
1
0
S
1
1
S
1
2
S
1
3
S
1
4
FAN FAN FAN
S
1
5
S
1
6
S
1
7
S
1
8
P
I
U
P
I
U
G
X
C
S
A
G
X
C
S
A
G
S
C
C
G
S
C
C
P
Q
1
/
P
Q
M

(
W
)
P
Q
1
/
P
Q
M

(
P
)
A
U
X
P
Q
1
/
P
Q
M

(
W
)
P
Q
1
/
P
Q
M

(
W
)
P
Q
1
/
P
Q
M

(
W
)
P
Q
1
/
P
Q
M

(
W
)
P
Q
1
/
P
Q
M

(
W
)
P
Q
1
/
P
Q
M

(
W
)
P
Q
1
/
P
Q
M

(
W
)
D
7
5
S
/
D
1
2
S
D
7
5
S
/
D
1
2
S
D
7
5
S
/
D
1
2
S
D
7
5
S
/
D
1
2
S
D
7
5
S
/
D
1
2
S
D
7
5
S
/
D
1
2
S
D
7
5
S
/
D
1
2
S
D
7
5
S
/
D
1
2
S
D
7
5
S
/
D
1
2
S
D
7
5
S
/
D
1
2
S
D
7
5
S
/
D
1
2
S
D
7
5
S
/
D
1
2
S
D
7
5
S
/
D
1
2
S
D
7
5
S
/
D
1
2
S
D
7
5
S
/
D
1
2
S
D
7
5
S
/
D
1
2
S

11 Troubleshooting Tributary Protection Switching Fault
Troubleshooting
Issue 04 (2010-11-30)
Figure 11-2 Protection mode of E3/T3 processing board (1)
S
2
7
S
1
9
S
2
0
S
2
1
S
2
2
S
2
3
S
2
4
S
2
5
S
2
6
S
3
7
S
2
9
S
3
0
S
3
1
S
3
2
S
3
3
S
3
4
S
3
6
S
3
5
S
2
8
S
1
S
2
S
3
S
4
S
5
S
6
S
7
S
8
S
9
S
1
0
S
1
1
S
1
2
S
1
3
S
1
4
FAN FAN FAN
S
1
5
S
1
6
S
1
7
S
1
8
P
I
U
P
I
U
G
X
C
S
A
G
X
C
S
A
G
S
C
C
G
S
C
C
P
D
3
/
P
L
3

(
P
)
A
U
X
P
D
3
/
P
L
3

(
W
)
P
D
3
/
P
L
3

(
W
)
P
D
3
/
P
L
3

(
W
)
P
D
3
/
P
L
3

(
W
)
P
D
3
/
P
L
3

(
W
)
P
D
3
/
P
L
3

(
W
)
P
D
3
/
P
L
3

(
P
)
T
S
B
8
T
S
B
8
D
3
4
S
/
C
3
4
S
D
3
4
S
/
C
3
4
S
D
3
4
S
/
C
3
4
S
D
3
4
S
/
C
3
4
S
D
3
4
S
/
C
3
4
S
D
3
4
S
/
C
3
4
S

Figure 11-3 Protection mode of E3/T3 processing board (2)
S
2
7
S
1
9
S
2
0
S
2
1
S
2
2
S
2
3
S
2
4
S
2
5
S
2
6
S
3
7
S
2
9
S
3
0
S
3
1
S
3
2
S
3
3
S
3
4
S
3
6
S
3
5
S
2
8
S
1
S
2
S
3
S
4
S
5
S
6
S
7
S
8
S
9
S
1
0
S
1
1
S
1
2
S
1
3
S
1
4
FAN FAN FAN
S
1
5
S
1
6
S
1
7
S
1
8
P
I
U
P
I
U
G
X
C
S
A
G
X
C
S
A
G
S
C
C
G
S
C
C
P
Q
3

(
P
)
A
U
X
P
Q
3

(
W
)
P
Q
3

(
W
)
P
Q
3

(
W
)
P
Q
3

(
W
)
P
Q
3

(
W
)
P
Q
3

(
W
)
P
Q
3

(
P
)
T
S
B
8
T
S
B
8
D
3
4
S
D
3
4
S
D
3
4
S
D
3
4
S
D
3
4
S
D
3
4
S
T
S
B
8
T
S
B
8
D
3
4
S
D
3
4
S
D
3
4
S
D
3
4
S
D
3
4
S
D
3
4
S

NOTE
When the PQ3 is used as a protection board, two TSB8 boards must be used.
11-3
Figure 11-4 Protection mode of E4 processing board
S
2
7
S
1
9
S
2
0
S
2
1
S
2
2
S
2
3
S
2
4
S
2
5
S
2
6
S
3
7
S
2
9
S
3
0
S
3
1
S
3
2
S
3
3
S
3
4
S
3
6
S
3
5
S
2
8
S
1
S
2
S
3
S
4
S
5
S
6
S
7
S
8
S
9
S
1
0
S
1
1
S
1
2
S
1
3
S
1
4
FAN FAN FAN
S
1
5
S
1
6
S
1
7
S
1
8
P
I
U
P
I
U
G
X
C
S
A
G
X
C
S
A
G
S
C
C
G
S
C
C
S
P
Q
4
(
P
)
A
U
X
S
P
Q
4

(
W
)
S
P
Q
4

(
W
)
S
P
Q
4

(
W
)
S
P
Q
4

(
W
)
S
P
Q
4

(
W
)
S
P
Q
4

(
W
)
S
P
Q
4

(
P
)
T
S
B
8
M
U
0
4
M
U
0
4
M
U
0
4
M
U
0
4
M
U
0
4
M
U
0
4
T
S
B
8

Figure 11-5 Protection mode of STM-1(e) processing board
S
2
7
S
1
9
S
2
0
S
2
1
S
2
2
S
2
3
S
2
4
S
2
5
S
2
6
S
3
7
S
2
9
S
3
0
S
3
1
S
3
2
S
3
3
S
3
4
S
3
6
S
3
5
S
2
8
S
1
S
2
S
3
S
4
S
5
S
6
S
7
S
8
S
9
S
1
0
S
1
1
S
1
2
S
1
3
S
1
4
FAN FAN FAN
S
1
5
S
1
6
S
1
7
S
1
8
P
I
U
P
I
U
G
X
C
S
A
G
X
C
S
A
G
S
C
C
G
S
C
C
S
E
P
(
P
)
A
U
X
S
E
P
(
W
)
S
E
P
(
W
)
S
E
P
(
W
)
S
E
P

(
W
)
S
E
P

(
P
)
T
S
B
8
E
U
0
8
E
U
0
8
E
U
0
8
E
U
0
8
T
S
B
8
E
U
0
8
E
U
0
8
S
E
P
(
W
)
S
E
P
(
W
)

Troubleshooting
Issue 04 (2010-11-30)
Figure 11-6 Protection mode of Ethernet board
S
2
7
S
1
9
S
2
0
S
2
1
S
2
2
S
2
3
S
2
4
S
2
5
S
2
6
S
3
7
S
2
9
S
3
0
S
3
1
S
3
2
S
3
3
S
3
4
S
3
6
S
3
5
S
2
8
S
1
S
2
S
3
S
4
S
5
S
6
S
7
S
8
S
9
S
1
0
S
1
1
S
1
2
S
1
3
S
1
4
FAN FAN FAN
S
1
5
S
1
6
S
1
7
S
1
8
P
I
U
P
I
U
G
X
C
S
A
G
X
C
S
A
G
S
C
C
G
S
C
C
E
F
S
0
(
P
)
A
U
X
E
F
S
0

(
W
)
E
F
S
0

(
W
)
E
F
S
0
(
P
)
T
S
B
8
E
T
S
8
E
T
S
8
T
S
B
8

Figure 11-7 Protection mode of DDN board
S
2
7
S
1
9
S
2
0
S
2
1
S
2
2
S
2
3
S
2
4
S
2
5
S
2
6
S
3
7
S
2
9
S
3
0
S
3
1
S
3
2
S
3
3
S
3
4
S
3
6
S
3
5
S
2
8
S
1
S
2
S
3
S
4
S
5
S
6
S
7
S
8
S
9
S
1
0
S
1
1
S
1
2
S
1
3
S
1
4
FAN FAN FAN
S
1
5
S
1
6
S
1
7
S
1
8
P
I
U
P
I
U
G
X
C
S
A
G
X
C
S
A
G
S
C
C
G
S
C
C
D
X
1

(
W
)
D
X
1
(
P
)
A
U
X
D
M
1
2
D
X
1

(
W
)
D
X
1

(
W
)
D
X
1

(
W
)
D
X
1

(
W
)
D
X
1

(
W
)
D
X
1

(
W
)
D
X
1

(
W
)
D
M
1
2
D
M
1
2
D
M
1
2
D
M
1
2
D
M
1
2
D
M
1
2
D
M
1
2
D
M
1
2
D
M
1
2
D
M
1
2
D
M
1
2
D
M
1
2
D
M
1
2
D
M
1
2
D
M
1
2

11-5
Figure 11-8 TPS protection for hybrid services
S
2
7
S
1
9
S
2
0
S
2
1
S
2
2
S
2
3
S
2
4
S
2
5
S
2
6
S
3
7
S
2
9
S
3
0
S
3
1
S
3
2
S
3
3
S
3
4
S
3
6
S
3
5
S
2
8
S
1
S
2
S
3
S
4
S
5
S
6
S
7
S
8
S
9
S
1
0
S
1
1
S
1
2
S
1
3
S
1
4
FAN FAN FAN
S
1
5
S
1
6
S
1
7
S
1
8
P
I
U
P
I
U
E
X
C
S
A
E
X
C
S
A
G
S
C
C
G
S
C
C
P
D
3
/
P
L
3

(
P
)
P
Q
1
/
P
Q
M

(
P
)
A
U
X
P
D
3
/
P
L
3

(
W
)
P
Q
1
/
P
Q
M

(
W
)
P
Q
1
/
P
Q
M

(
W
)
S
E
P
1

(
W
)
S
E
P
1

(
P
)
T
S
B
8
D
3
4
S
/
C
3
4
S
D
7
5
S
/
D
1
2
S
D
7
5
S
/
D
1
2
S
D
7
5
S
/
D
1
2
S
D
7
5
S
/
D
1
2
S
E
U
0
8
E
U
0
8
E
U
0
8
T
S
B
8
S
E
P
1

(
W
)
S
E
P
1

(
W
)

Table 11-1 lists the boards that support the TPS.
Table 11-1 Board Supporting Protection
Service Type Boards
E1/T1 N1PQ1, N1PQM, N2PQ1
E3/T3 N1PD3, N1PL3, N2PQ3, N2PD3, N2PL3
E4 N1SPQ4, N2SPQ4
STM-1(e) N1SEP
Ethernet N2EFS0, N4EFS0
DDN N1DX1
NOTE
N2PQ1 cannot support T1 service.

11.1.2 Working Principle
It introduces the working principle of TPS.
For the working principle of TPS, refer to the OptiX OSN 3500 Intelligent Optical
Transmission System Hardware Description. The TPS principle is covered in the introduction
to the protection configuration of each board.
The TPS switching faults may occur due to external causes, incorrect data configuration, and
equipment causes.
Troubleshooting
Issue 04 (2010-11-30)
The fault of TPS switching refers to the equipment that does not enter the protection switching
status when the switching occurs or when services are interrupted after the protection switching.
Table 11-2 shows the common faults and causes of TPS switching. The causes include external
causes, data configuration and equipment fault.
Table 11-2 Common causes for TPS switching fault
Fault type Cause
External causes Protection board fails.
The TSB8 board is in poor contact.
Data configuration The protection parameter is set incorrectly.
Equipment causes The GSCC unit fails.
Cross-connect board fails.
The TSB8 board fails.
The PIU unit fails.

This section describes the procedures for locating TPS faults.
Fault Handling Flow
Figure 11-9 shows the procedures for handling the fault in the case of TPS faults.
11-7
Figure 11-9 Handling flowchart of TPS faults.
TPS troubleshooting
Switching of TSB4/
TSB8 board activated?
NM cofiguration
incorrect?
Hardware fault?
Fault removed?
Continue next
condition
Yes
No
1
2
3
End
Contac Technical
Support, Huawei
Replace Protection
processing board
Re-configure NM
paramenters
SCC board fault?
TSB4/TSB8 fault?
N
Protection Processing
board correct?
TSB4/TSB8
board loosend?
Put TSB4/TSB8
board in place
No
Cross-connect
board fault?
Unplug/Plug/Replace
TSB4/TSB8 board
Unplug/Plug/Replace
cross-connect board
Unplug/Plug/
Replace SCC board
PIU fault?
Unplug/Plug/Replace
PIU board
No
No
Yes
Yes
Yes
No
No
No
No
No
No
Yes
Yes
Yes
Yes
Yes
Yes
U2000

Procedure
Step 1 Cause 1: Exceptions occur in the TSB4/TSB8 board switching.
1. Check whether the protection board is working normally. Whether TPS occurs or not can
be checked through the indicators on the protection board when TPS is not started the ACT
indicator on the protection board is off, whereas that on the working board is on. After
switching, the ACT indicator on the working board where switching is performed is off,
whereas that on the protection board is on. If the protection board is not working normally,
replace the protection board.
2. Check whether the TSB4/TSB8 boards are well inserted. If no, re-insert the boards and
ensure that they are tightly inserted.
Step 2 Cause 2: The NM is incorrectly configured.
1. Make sure that the TPS function is enabled.
Step 3 Cause 3: The hardware is faulty.
Troubleshooting
Issue 04 (2010-11-30)
1. Check whether the SCC board is working normally. If no, replace the SCC board.
2. Check whether the cross-connect board is working normally. If no, replace the cross-
connect board.
3. Check whether the TSB4 or TSB8 board is working normally. If no, replace the TSB4 board
or the TSB8 board.
4. Check whether the PIU board is working normally. If no, replace the PIU board.
----End
11.4 Cases on TPS Protection
This section provides the case analysis of TPS protection.
Related cases:
None.
11-9
About This Chapter
This chapter describes the common causes of ECC faults, and the methods of locating and
handling ECC faults.
The embedded control channel (ECC) is used for SDH NE communication, the transmission of
the telecommunications management network (TMN) information, and the management (by the
NM) of the non-gateway network elements (non-GNEs).
Common ECC faults may occur due to external causes, human factors, or equipment causes.
This section describes the procedures for locating ECC faults according to based on the basic
principle of fault handling.
12.4 Case of ECC
Analysis of cases related to ECC.
Troubleshooting 12 Troubleshooting ECC Faults
12-1
The embedded control channel (ECC) is used for SDH NE communication, the transmission of
the telecommunications management network (TMN) information, and the management (by the
NM) of the non-gateway network elements (non-GNEs).
The physical ECC channel includes the data communication channel (DCC) byte, serial port,
and network port (the latter two are used for ECC extension). The DCC bytes are the D1D12
bytes in the section overhead (SOH). The OptiX OSN products usually use D1D3 bytes. The
OptiX OSN products can select any one group from the three groups of bytes: D1D3, D4D12,
D7D9), that is, the regenerator section DCC. With the rate of 192 kbit/s, it is used for OAM
information exchange among NEs.
If two SDH NEs are connected with optical fiber, the TMN information is transmitted through
the regenerator section bytes D1D3 in the section overhead. If they are not connected with
optical fiber, this transmission is carried out through the extended ECC. That is, these two NEs
are connected through a network port or serial port for TMN information transmission.
12.1.1 Communication Between NM and NEs
The communication between NM and NEs includes the information exchange between NM and
the gateway NEs, and the ECC communication between the gateway NEs and the non-gateway
NEs.
12.1.2 ECC Signal Flow
The ECC signal flow is independent of the service signal flow.
12.1.3 ECC Routing
The ECC route has two types: short trail and long trail.
12.1.4 ID and IP
The ID consists of the NE ID and the extended ID. The NE ID is used for the ECC communication
between NEs, whereas the extended ID is introduced to prevent any two subnets from sharing
the same ID. The IP address is used for the communication between the gateway NEs and the
NM and set only for the gateway NEs.
12.1.5 Manual Settings of Connection List and Routing Table
The communication between NEs can be completed by a manually set connection list and routing
table, which is a substitute for auto routing.
12.1.6 ECC Routing Planning
ECC routing planning can be defined as a reasonable limitation on the number of NEs managed
by a GNE.
12.1.1 Communication Between NM and NEs
The communication between NM and NEs includes the information exchange between NM and
the gateway NEs, and the ECC communication between the gateway NEs and the non-gateway
NEs.
The NM communicates with non-GNEs as follows. First, the NM and the GNE communicate
with each other through TCP/IP, and then the GNE and non-GNEs communicate with each other
through the ECC channels. In other words, the NM can communicate with non-GNEs.
Troubleshooting
Issue 04 (2010-11-30)
12.1.2 ECC Signal Flow
The ECC signal flow is independent of the service signal flow.
For the OptiX OSN 3500, when the GSCC unit is not in position, the DCC bytes of each paired
slot (such as slot 5 and slot 14) can pass through each other. In ADM configuration, slot 5 and
slot 14 form the west and east of an ADM.
NOTE
For more details of the paired slots, refer to OptiX OSN 3500 Intelligent Transmission System Product
Description.
12.1.3 ECC Routing
The ECC route has two types: short trail and long trail.
Features of ECC Routing
l In the case of normal routing, the NM logs in to the non-GNE over the short trail through
the GNE. The long trail is used when the short trail is abnormal. If both trails are abnormal,
the login fails.
l The ECC is established by means of dual transmission at the transmitting end and single
selection at the receiving end. The selection principle is "create the route on the basis of
the shortest trail". The shortest trail is not the actual geographical distance, but the logical
distance in the routing table, that is, the number of stations.
ECC Routing in Ring Network
Figure 12-1 shows that NE1 is the GNE connected to the NM. The NM may log in to NE4 in
the 1 to 4 direction (the short trail) or the 1 to 2 to 3 to 4 direction (the long trail). In a ring
network, the NM logs in to NE4 through the long trail if the short trail fails. You should frequently
check the ECC routing through the NM. If the ECC routing goes through the long trail, detect
the cause and remove the fault.
Figure 12-1 ECC in ring network
NE2
NE1
NE3
NE4
U2000

12-3
12.1.4 ID and IP
The ID consists of the NE ID and the extended ID. The NE ID is used for the ECC communication
between NEs, whereas the extended ID is introduced to prevent any two subnets from sharing
the same ID. The IP address is used for the communication between the gateway NEs and the
NM and set only for the gateway NEs.
NE ID
Each NE must have one independent ID, and the ECC communication between the NEs is
performed by identifying the ID. The NM identifies different NEs with IDs in the interface or
database, by using the keyword to indicate each NE.
Extended ID
Extended ID is used to realize centralized management of various subnets, which are
independent before, through one NM. Since they have the same ID, there may be errors in setting
up an ECC routing table and the NM may fail to manage them when various subnets are
connected to form a large network. Hence, NEs with the same ID must be first configured with
different extended IDs. The extended ID (that is, the subnet number of the NE) can be set and
queried in the NM.
IP Address of GNE
Because the IP address is intended for the communications between the GNE and the NM, it is
useful when the TCP/IP communication is performed. That is, only the GNE needs the IP
address. The IP address is not the only parameter to identify the NE.
In essence, the ID is independent of the IP. They can be set independently. The low 16 bits of
the default IP address is the ID of the NE. For instance, if the ID is 1, the IP address is 129.9.0.1
by default. If the IP address is set manually, it is no longer influenced by any change to the ID.
After this IP address is cancelled, the IP varies according to the ID.
CAUTION
Only the GNE needs to be set with an IP address (no IP for any non-GNE). After setting the IP,
it is necessary to record it in a file. If you forget the IP address, log in to the NE with the original
IP through a non-GNE and regain the IP address through the NM.
12.1.5 Manual Settings of Connection List and Routing Table
The communication between NEs can be completed by a manually set connection list and routing
table, which is a substitute for auto routing.
Automatic routing is the routing relationship that is automatically established between NEs
according to the protocol. It cannot be deleted or changed. Manual routing is the routing
relationship set manually between NEs (including routing distance and level). After being set,
manual routing will replace the original automatic routing to realize communications between
NEs.
Troubleshooting
Issue 04 (2010-11-30)
Manual routing can be added or deleted in the U2000. The manually set connection list and
routing table are intended for ECC creation when the routing is unidirectional. Improper manual
routing will affect the communications among NEs. . You need to pay attention before using it.
For adding and deleting manual routing, refer to the Online Help of the U2000.
12.1.6 ECC Routing Planning
ECC routing planning can be defined as a reasonable limitation on the number of NEs managed
by a GNE.
If the network connection is made through the ECC, the more the number of NEs that exist, the
more complicated is the ECC routing. Improper ECC routing planning will lead to ECC
communications problem if the network is abnormal.
It is recommended that the number of NEs under one GNE should not be more than 50 for the
OptiX OSN 3500 networking.
Common ECC faults may occur due to external causes, human factors, or equipment causes.
Fault Description
The common ECC faults include NE login failure of the NM, low login speed, discontinuous
connection, and incorrect ECC routing.
Causes
Table 12-1 shows the common causes of ECC faults.
Table 12-1 Common causes of ECC faults
Fault cause Fault type
External causes Faults in peripheral devices, such as network cable, network card, NM
computer, hub, and router
Optical fiber performance is degraded.
Human factors Improper ECC routing planning
Incorrect IP address setting
Repeated use of NE ID
No NE is added into the system management domain.
Manual routing is set.
Equipment
causes
The GSCC board fault
Optical interface board fault

12-5
This section describes the procedures for locating ECC faults according to based on the basic
principle of fault handling.
Fault Handling Flow
The basic principle is "external first, transmission next; network first, NE next; high-speed first,
low-speed next; higher-level first, lower-level next".
Figure 12-2 shows the procedures for handling the fault in the case of ECC fault.
Figure 12-2 Handling flowchart of ECC fault
ECC fault
handling
Yes
1
If the external causes?
External fault
handling
If the personnel factors?
No
If improper ECC
route planning?
2
If the optical board
faulty
Replace the optical
interface board
If the SCC board
faulty?
Replace the
SCC board
3
Add the NE into the
system management
domain
If the NE not added into the
management domain yet?
Delete the
manual route
If manual route set?
Plan the ECC
route again
If incorrect IP address
configuration?
Set the correct
IP again
If the repeated NE ID?
Reallocate
the NE ID
If the fault
removed?
Go to the
next step
End
Contact Huawei for
technical support
N
4
Yes
No
No
Yes
Yes
No
No
No
No
Yes
Yes
Yes
Yes
No
Yes
No
No
Yes
U2000

Troubleshooting
Issue 04 (2010-11-30)
Procedure
Step 1 Cause 1: Rectify problems caused by external factors, such as faults in a network cable, network
card, NM computer, hub, and router.
Faults in peripheral devices, such as network cable, network card, NM computer, hub, and router,
disable the NM from logging into any of the NEs.
Step 2 Cause 2: The ECC routing planning is improperly planned; The IP address of the gateway NEs
and the IP address of the NM computer are not in the same network section.
Eliminate human factors.
l Improper ECC routing planning may result in low speed of the NM and the phenomenon that
several NEs suddenly turn gray and are then restored to normal again later. During
networking testing, ECC routing planning should be done properly. It should be planned
again if ECC communications is abnormal due to improper ECC routing planning.
l If the IP addresses of the GNE and the NM computer are not in the same network section,
the NM computer cannot log in to any of the NEs. Set the IP addresses again to remove the
fault.
l The mistakes made in the settings for equipment installation and commissioning or upgrade
and expansion, may also cause ECC problems. For example, the ID of a newly-added NE is
the same as that of an existing NE.
l Pay special attention to the setting of the system management domain. Make sure that the
NE that cannot be logged in to has been added to the system management domain.
l Check if manual routing exists. ECC communications fault may occur in the case of fiber-
cut if manual routing exists.
Step 3 Cause 3: The GSCC board is faulty.
Check if the indicators on the GSCC board are normal. If the red indicator is on, it indicates that
the GSCC board hardware is faulty. In this case, replace the GSCC board. For details, refer to
the Replacing the GSCC Board.
CAUTION
After replacing the GSCC board, resend the configuration data to this NE, because the data is
kept in the GSCC board.
Step 4 Cause 4: The optical interface board is faulty.
If handling the GSCC board does not help, check the optical interface board. For details, refer
to the Replacing SDH Interface Boards.
CAUTION
If handling the GSCC board does not help, check the optical interface board.
----End
12-7
12.4 Case of ECC
Analysis of cases related to ECC.
Relevant cases:
None.
Troubleshooting
Issue 04 (2010-11-30)
About This Chapter
This section describes the common causes of orderwire faults, and the methods of locating and
handling orderwire faults.
This section describes the basic knowledge required for handling an orderwire fault, for example,
the principles of setting orderwire phones, the functions of subnet conference calls and
networkwide conference calls, and the basic concept of call waiting time.
The orderwire faults may occur due to human factors and equipment faults.
This section describes the procedures for locating orderwire faults.
13.4 Cases on Orderwire
This section provides the case analysis of orderwire.
Troubleshooting 13 Troubleshooting Orderwire Fault
13-1
This section describes the basic knowledge required for handling an orderwire fault, for example,
the principles of setting orderwire phones, the functions of subnet conference calls and
networkwide conference calls, and the basic concept of call waiting time.
13.1.1 Setting Principles for the Orderwire Phone
When setting the orderwire, you need to comply with some principles.
13.1.2 Network-Wide Conference Call and Subnet Conference Call
Conference calls include subnet conference calls and network-wide conference calls to meet
requirements for large-scale networking.
13.1.3 Calling Waiting Time
The call waiting time refers to the waiting time after the local station dials the number of the
caller.
13.1.1 Setting Principles for the Orderwire Phone
When setting the orderwire, you need to comply with some principles.
Table 13-1 shows the setting principles for the orderwire phone.
Table 13-1 Configuration requirements of network orderwire
No. Orderwire configuration requirement
1 The orderwire signaling in the network must be the same or must be
compatible with other networks.
2 The orderwire phone number of each node is of the same length. It is
recommended that you use a four digit number.
3 It is recommended that you set the orderwire phone number as a subnet
number (one digit) + user number (three digits).
4 The number of conference calls in a network should be the same and can be
more than the orderwire number. It is recommended that you use number
9999.
5 It is suggested to set the subnet conference call number as subnet number
(one or two digit) + 999 (three or two digits).
6 No repetition of orderwire number in a network is allowed, except the
number of conference call.
7 The dialing mode of orderwire phone at each node is dual-tone multi-
frequency.
8 The call waiting time of each node should be consistent. Five seconds for
nodes less than 30 and nine seconds for nodes more than 30.
9 The increase of orderwire number and that of the node ID must be consistent.
Troubleshooting
Issue 04 (2010-11-30)
No. Orderwire configuration requirement
10 If there is a howler tone in the orderwire loop, disconnect the loop to solve
the problem. In a network that only contains the OptiX OSN 3500 or in a
hybrid network that contains the OptiX OSN 3500 and the OptiX OSN
2500, the loop can be disconnected automatically. When the equipment
interworks with the OptiX 2500+, the loop needs to be disconnected
manually.
11 When orderwire interworking is required where there is no optical path
connection, orderwire outgoing subnet connection can be made to realize it.
In this case, use Voice 1 or Voice 2 as the audio interface, and use Serial 3
or Serial 4 as the data interface.

13.1.2 Network-Wide Conference Call and Subnet Conference Call
Conference calls include subnet conference calls and network-wide conference calls to meet
requirements for large-scale networking.
The network-wide conference call function: A network-wide conference call refers to a network-
wide group call. That is, when the convener dials the conference call number, phones in the
network will ring and send ring-back tone, and all the phones enter the communication status.
The subnet conference call function: The subnet conference call function refers to a group call
within subnets with the same subnet number and connected through optical paths. In this case,
subnets refer to physical ones. They must be connected directly through physical optical paths.
Logical subnets are excluded here.
The network-wide conference call functions as a conventional telephone set, whereas the subnet
conference call is introduced to divide the "Specified area" in a super network. This specified
area is a subnet. When the route of a subnet conference call is established, the site addresses are
searched only in this subnet instead of the entire network so that the time of route setup is greatly
reduced. You must add the subnet number before the conference call number when making a
subnet conference call.
The priority of a network-wide conference call is higher than a subnet conference call. A
network-wide conference call from outside of a subnet will disable an on-going subnet
conference call.
13.1.3 Calling Waiting Time
The call waiting time refers to the waiting time after the local station dials the number of the
caller.
The relations among the call waiting time, ring-back tone, and busy tone are as follows:
l If the opposite party has been searched during the call waiting time and if the caller is
available, the ring-back tone can be heard.
l If the opposite party has been searched during the call waiting time but he is busy, the busy
tone can be heard.
l If the opposite party is not yet found during this period, the busy tone will be heard.
The call waiting time can be set from 1 to 9 seconds, and it is 5 seconds by default. It is not
required to set it to 0 seconds. If yes, the waiting time will be very long.
13-3
For complicated networking with many nodes, the call waiting time is longer. Even though the
line is free, call waiting timeout may occur and cause a call to fail. In this case, make another
call immediately, or delay the call waiting time.
The orderwire faults may occur due to human factors and equipment faults.
The common phenomena of the orderwire fault includes: the line being blocked or there are
stray noises in a conversation.
Table 13-2 shows the common causes of the orderwire faults.
Table 13-2 Common causes of the orderwire faults
Cause Fault type
Human factors The phone set is not plugged in or is plugged in a wrong position.
The phone set is set incorrectly or is not on-hook.
The orderwire is set incorrectly.
The orderwire is planned improperly.
Equipment fault There is a fault with the phone set or phone cable.
The GSCC board is faulty.
The AUX board is faulty.
The line board is faulty.

This section describes the procedures for locating orderwire faults.
Fault Handling Flow
Figure 13-1 shows the procedures for handling the fault in the case of orderwire faults.
Troubleshooting
Issue 04 (2010-11-30)
Figure 13-1 Handling flowchart of orderwire faults
Continue next
condition
Orderwire
troubleshooting
Phone connector
disconnected or
misconnected?
Orderwire setting wrong?
Incorrect phone setting?
SCC board fault?
Yes
End
Contact Technical
Support, Huawei
Resetting
phone setting
Replace SCC
board
Replace
line board
N
Line board fault?
Remove
connector fault
Change
orderwire setting
6
5
4
3
2
1
No
Orderwire
fault removed?
Replace AUX
board
AUX board fault?
No
No
No
No
No
Yes
Yes
Yes
Yes
Yes
No
Yes
U2000

Procedure
Step 1 Cause 1: The phone set is not plugged in or is plugged in a wrong position.
Reconnect the phone set. The orderwire phone line is usually connected to the PHONE interface
on the orderwire board.
Step 2 Cause 2: The phone set is incorrectly set.
Most of the orderwire problems are caused by incorrect settings of the phone set. The settings
of the phone set are as follows:
l The ringing current switch "RING" on the phone set should be set to "ON", indicating that
the phone will ring when there is an incoming call.
l Select T for the dialing mode, that is, the dual tone multi-frequency (DTMF) mode.
l An orderwire phone set should be on-hook when it is not in communication, and the
upperright red indicator in the front view of the orderwire phone set should be off. If the red
indicator is on, it indicates that the phone set is not in the on-hook state. Press the "TALK"
button in the front of a phone set to hook it up. On some occasions, the "TALK" button is
13-5
accidentally pressed by the maintenance personnel. This makes the phone set remain in the
off-hook state and the orderwire calls from other stations cannot get through.
Step 3 Cause 3: The orderwire is incorrectly set.
Check the phone numbers that are set in the entire network to ensure that the numbers are not
repeated.
Step 4 Cause 4: The ring current module is faulty.
If the phone does not ring, check if the ring current module of the GSCC board is faulty. If the
it is fault, replace it. For details, refer to the Replacing CF Cards of System Control and
Communication Board.
Step 5 Cause 5: The SCC board or the orderwire board is faulty.
Replace the SCC board or the orderwire board.
l Replace the SCC board or the orderwire board. For details, refer to the Replacing CF Cards
of System Control and Communication Board.
Step 6 Cause 6: The line board is faulty.
Replace the line board. For details, refer to the Replacing SDH Interface Boards.
----End
13.4 Cases on Orderwire
This section provides the case analysis of orderwire.
Related cases:
None.
Troubleshooting
Issue 04 (2010-11-30)
About This Chapter
This section describes the common causes of Ethernet faults, and the methods of locating and
handling Ethernet faults.
This section describes the basic features and types of Ethernet services.
Generally, an Ethernet service failure results in service interruption or service degradation.
When locating Ethernet faults, follow the principles of "performance first, alarms next; SDH
first, Ethernet next; logs first, tests next, and internal first, external next". Make good use of the
maintenance means as alarms, performance events, segment-by-segment loopback, and test
frames together with the maintenance tool such as the software tools, test instruments, and the
Ping function. Locate the Ethernet faults step by step as planned.
14.4 Cases on the Ethernet Faults
This section provides the case analysis of Ethernet faults.
Troubleshooting 14 Ethernet Troubleshooting
14-1
This section describes the basic features and types of Ethernet services.
With the development of Ethernet services, it is important to have a robust and steady network .
Therefore, the method of quickly locating the faulty point and restoring the service becomes
important in the case of an Ethernet service failure.
Before handling a fault in the Ethernet network, you must have a basic knowledge of the Ethernet
network and understand the Ethernet service features.
14.1.1 Ethernet Service Features
This section describes the Ethernet service features in terms of multiplexing mode, transmission
mode, negotiation mode, frame structure, and port working mode.
14.1.2 Ethernet Service Classification
Ethernet services can be classified into four types, namely, Ethernet private line (EPL), Ethernet
virtual private line (EVPL), Ethernet private local area network (EPLAN), and Ethernet virtual
private local area network (EVPLAN).
14.1.1 Ethernet Service Features
This section describes the Ethernet service features in terms of multiplexing mode, transmission
mode, negotiation mode, frame structure, and port working mode.
Multiplexing Mode
An Ethernet service is transmitted in the statistical multiplexing mode.
The service is variable. In addition, it occupies the bandwidth resource as required, thus sharing
the bandwidth resource.
Transmission Mode
When being transmitted, an Ethernet service adopts the encapsulation format to carry the
addressing information. Unlike an SDH service that is strictly synchronized in the whole
network, an Ethernet service is transmitted in the asynchronous transfer mode (ATM).
Negotiation Mode
An Ethernet port works in one of the following negotiation modes:
l Auto-negotiation mode: Automatically negotiates for the working mode of the
interconnected Ethernet port.
l Non-auto-negotiation mode: Manually specifies the working mode of the interconnected
Ethernet port..
Frame Structure
Figure 14-1 shows the Ethernet frame structure that is widely adopted at present.
Troubleshooting
Issue 04 (2010-11-30)
Figure 14-1 Ethernet frame structure
0806
8035
Forward
synchronization code
Frame header
character
Destination
address
Source
address
Type Frame data CRC
1 byte 6 bytes
2 bytes 4 bytes 46-1500 bytes
7 bytes
Type
0800
IP data packet
ARP request/response
RARP request/response
Fill in
6 bytes
64-1518 bytes
2 bytes 46-1500 bytes
Type
2 bytes
28 bytes 18 bytes
Type
2 bytes
28 bytes
Fill in
18 bytes

The Ethernet frame structure can be changed to some extent as required.
Port Working Mode
An Ethernet service runs in :
l Negotiation mode.
l Duplex mode: Full-duplex mode and half-duplex mode.
14.1.2 Ethernet Service Classification
Ethernet services can be classified into four types, namely, Ethernet private line (EPL), Ethernet
virtual private line (EVPL), Ethernet private local area network (EPLAN), and Ethernet virtual
private local area network (EVPLAN).
EPL Service
The EPL service is implemented through the point-to-point transparent transmission in the
Ethernet network.
EVPL Service
The VLAN ID, QinQ or MPLS tags can be used to isolate the EVPL service of different users
or the EVPL services of different departments in the same company. In this way, the data of the
same VLAN in the same link is isolated.
EPLAN Service
The EPLAN service supports layer 2 switching of Ethernet data, which is transmitted according
to its destination media access control (MAC) address. The EPLAN services can dynamically
share the bandwidth at multiple points.
14-3
EVPLAN Service
The EVPLAN service implements the multipoint-to-multipoint connection of user sites. From
the perspective of users, the EVPLAN network is a large VLAN where the services can be
converged.
Generally, an Ethernet service failure results in service interruption or service degradation.
Common causes for service interruption are shown in Table 14-1.
Table 14-1 Common causes for service interruption
No. Causes
No. Causes for Service Interruption
1 The TAG attribute (TAG/UNTAG) of the port is incorrectly set.
2 The port working mode is faulty.
3 The network cable or fiber becomes faulty.
4 The VC path binding is incorrect or inconsistent.
5 The default VLAN ID of the port is incorrectly set.
6 The Ethernet static router is faulty or lost.
7 The board hardware becomes faulty.
8 The encapsulation protocol does not match.
9 The GFP frame is out of synchronization, or the FCS_ERROR occurs in the GFP
encapsulation.
10 A large number of packets are lost.

Common causes for service degradation are shown in Table 14-2.
Table 14-2 Common causes for service degradation
No. Causes
1 The traffic is heavy, but the bandwidth is insufficient.
2 The bandwidth is sufficient, but the burst traffic is heavy.
3 If the traffic is extremely heavy, the peer equipment does not respond to the
service control policy, thus discarding packets.
4 The maximum transmission unit (MTU) value specified for the board is less than
the actual size of the packets transmitted according to the requirement.
Troubleshooting
Issue 04 (2010-11-30)
No. Causes
5 The working mode of the port does not match that of the port on the peer
equipment. Therefore, the port works in an abnormal state.
6 The network cable or fiber becomes faulty.
7 The board hardware becomes faulty.
8 A loop exists in the service, and the spanning tree protocol is not enabled.
9 Exceptions occur on the network.

When locating Ethernet faults, follow the principles of "performance first, alarms next; SDH
first, Ethernet next; logs first, tests next, and internal first, external next". Make good use of the
maintenance means as alarms, performance events, segment-by-segment loopback, and test
frames together with the maintenance tool such as the software tools, test instruments, and the
Ping function. Locate the Ethernet faults step by step as planned.
In addition, take other emergency measures (such as providing and switching to standby links)
to restore the services in the shortest time possible.
Figure 14-2 shows the interface of Ethernet fault locating.
Figure 14-2 Interface of Ethernet faults locating
VCTRUNK
attributes
Ethernet
interface
attributes
The interconnected
data communication
equipment
Cross-connection
at the SDH layer
VCTRUNK
attributes
Ethernet
interface
attributes
The interconnected
data communication
equipment
SDH Ethernet board External equipment

14.3.1 Fault Locating Flow
This section describes the procedures for locating the Ethernet faults in the case of service
interruption.
degradation.
interruption.
14-5
Fault Handling Flow
Figure 14-3 shows the procedures for handling the fault in the case of Ethernet network fault
in the case of service interruption.
Figure 14-3 Handling flowchart of Ethernet network fault in the case of service interruption
Start
Handle the faults of locally
interconnected equipment
Handle the
SDH alarms
Yes
NO
View the RMON performance
statistics, and check whether
any packets are transmitted
or received at the port
Check whether any
SDH alarms are raised
Analyze the network operation
logs to check whether any risky
operations have been performed
3
1
2
Board indicator abnormal
Handle board
faults
4
Correct the
configurations
Check whether the network
configurations are incorrect
Check if the test frames fail to
travel through the VCTRUNK
Test together with the data
communications equipment, and
ping the data communications
equipment for success
External
problems
Replace the PC or meters to check
whether the test is successful based
on the statistics of performance
events stored in the RMON memory
The data communications
equipment is faulty
Contact the technical
support engineers from
Huawei
Faults removed?
Continue to check
the next item
N
No
5
6
7
8
End
NO
NO
NO
NO
NO
NO
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Handle the faults of
remote equipment
Packets are
transmitted and
received
Check the
configuration
Yes
Packets are
transmitted but not
received
Packets are
received but not
transmitted
Packets are not
transmitted and
received
U2000

Troubleshooting
Issue 04 (2010-11-30)
Procedure
Step 1 Cause 1: The board is faulty as indicated by the STAT indicator on the board.
Check whether the STAT indicator indicates a fault on the board according to the description in
the Board Alarm Indicator. If yes, handle the fault of the board.
Step 2 Cause 2: The RMON performance analysis shows that there is abnormal performance events.
1. To handle an Ethernet fault, analyze the RMON performance on the U2000 to know
whether the service is abnormal. For details, refer to the Browsing the Current Performance
Events at the Ethernet Port.
2. View the performance events.
l If there is the performance value of the RMON module crosses the upper
threshold event, the FCS error frames exist. It indicates that the CRC error occurs.
Then, you need perform the following operations.
a. Check whether the working mode of the port matches at the two ends. The port
cannot work in the full-duplex mode at one end, but in the half-duplex mode at
another end.
b. Check whether the network cable is of poor quality.
c. Check whether the hardware of the network interface becomes faulty.
l If there is the performance value of the RMON module crosses the upper
threshold event, the DropEvent exists. It indicates the packet is lost due to the hardware
anomaly.
a. Perform a cold reset on the board.
b. If packets are still dropped, replace the board.
Step 3 Cause 3: The SDH side is faulty.
1. Query the current alarms on the U2000. For details, refer to the Querying Current Alarms
on U2000. Check where there is any alarm that may cause service interruption or
degradation.
2. Check the type of the reported alarm. If the alarm is reported on the SDH side, handle the
SDH fault accordingly.
Step 4 Causes 4 and 5: Risky operation is performed. Services are incorrectly set. Transmitting of test
frames fails.
Check and re-configure the services.
Step 5 Cause 6: Test frames cannot be transmitted over the VCTRUNK.
The possible causes and handling methods of the transmission failure are as follows:
l The test frames are carried by different modes at the two ends. Set the same carrying modes
for the interconnected equipment at both ends.
l Timeslots are not bound to the VCTRUNK interfaces for test frame enabling. Bind the
corresponding timeslots to the VCTRUNK interfaces at the two interconnected ends.
l Cross-connections are not established between the bound timeslots. Establish cross-
connections between the timeslots bound to the VCTRUNK interfaces at the two
interconnected ends.
----End
14-7
degradation.
Fault Handling Flow
Figure 14-4 shows the procedures for handling the fault in the case of Ethernet network fault
in the case of service degradation.
Troubleshooting
Issue 04 (2010-11-30)
Figure 14-4 Handling flowchart of Ethernet network fault in the case of service degradation
Start
U2000
No
1
Check whether any traffic information
is contained in the statistical data
stored in the RMON memory
Interrupt the Ethernet services
Contact the technical
support engineers from
Huawei
Whether the faults
have been removed?
Continue to check the
next item
N
End
Check whether any SDH
alarms are raised
Handle the SDH alarms
Yes
Check whether any performance
events stored in the RMON
memory, and check whether any
abnormal data exists
Timeslot collision or
fragments
Replace the ports or
boards
Check the working mode
of the ports
Analyze whether the
traffic is normal
FCS error
Excessive
unicast traffic
Excessive
broadcast traffic
Pick up packets for analysis
/ Increase the bandwidth
Check the loop
Send the test frame to check
whether it fails to be transmitted
between VCTRUNKs
Handle it as failed to send
the test frame
Whether the meter and
loopback test has been passed
2
3
4
5
6
Modify the MTU
External problems or/and failed
interconnection to the data
communications equipment
No
No
No
No
No
Yes
Yes
Yes
Yes
Yes
Yes
No

14-9
Procedure
Step 1 Cause 1: Alarms are raised on the SDH side.
1. Query the current alarms on the U2000. For details, refer to the Querying Current Alarms
on U2000. Check where there is any alarm that may cause service interruption or
degradation.
2. Check the type of the reported alarm. If the alarm is reported on the SDH side, handle the
SDH fault accordingly.
Step 2 Cause 2: There are excessive unicasts or broadcasts.
Step 3 Cause 3: Test frames cannot be transmitted over the VCTRUNK.
The possible causes and handling methods of the transmission failure are as follows:
l The test frames are carried by different modes at the two ends. Set the same carrying modes
for the interconnected equipment at both ends.
l Timeslots are not bound to the VCTRUNK interfaces for test frame enabling. Bind the
corresponding timeslots to the VCTRUNK interfaces at the two interconnected ends.
l Cross-connections are not established between the bound timeslots. Establish cross-
connections between the timeslots bound to the VCTRUNK interfaces at the two
interconnected ends.
Step 4 Cause 4: The MTU value specified for the board is less than the actual size of the packets
transmitted by the equipment
1. Find the MTU value by testing the network through a meter.
2. If the MTU value specified for the board is less than the value obtained in the test, set
another MTU value for the board.
----End
14.4 Cases on the Ethernet Faults
This section provides the case analysis of Ethernet faults.
Related cases:
None.
Troubleshooting
Issue 04 (2010-11-30)
About This Chapter
This section describes the common causes of ATM/IMA faults and the locating and handling of
such faults.
This section describes the basic knowledge of IMA.
15.2 Common Causes
This section describes the common causes of IMA interconnection faults, including external
causes and equipment causes.
This section describes the procedures for locating IMA interconnection faults.
15.4 Cases on ATM and IMA
This section provides the case analysis of ATM and IMA.
Troubleshooting 15 Handling of ATM/IMA Faults
15-1
This section describes the basic knowledge of IMA.
15.1.1 IMA Functions and Interconnection
In inverse multiplexing over ATM (IMA) mode, the transmit end inversely multiplexes ATM
cell flow in a high-rate link into multiple low-rate links, and the receive end converges the ATM
cell flow in these low-rate links to a high-rate ATM cell flow.
15.1.1 IMA Functions and Interconnection
In inverse multiplexing over ATM (IMA) mode, the transmit end inversely multiplexes ATM
cell flow in a high-rate link into multiple low-rate links, and the receive end converges the ATM
cell flow in these low-rate links to a high-rate ATM cell flow.
Functions and Principles
Figure 15-1 shows the basic IMA principles.
Figure 15-1 Basic IMA functions
IMA
group PHY
PHY
PHY
PHY
PHY
PHY
Original ATM
Cell stream
to ATM layer
Single ATM
cell stream
from ATM
layer
Physical link0#
Physical link 1#
Physical link 2#
IMA
group
Logical link

The IMA technology is mainly used to solve the problem of interconnection between high-rate
links and low-rate links. Inverse multiplexing is based on physical links instead of VPCs or
VCCs. The IMA functions are transparent to the ATM layer. In inverse multiplexing mode or
multiplexing mode, VPIs/VCIs are not used.
Application
The IMA technology is applicable when ATM cells are transmitted through an interface of the
E1 rate or other rates. The IMA technology provides a path only, and does not process service
types and ATM cells. The signals at the ATM layer and a higher layer are transparently
transmitted.
The IMA technology is used on the access layer of the wireless network to dynamically allocate
the bandwidth so as to achieve bandwidth convergence. The IMA E1 links of an BTS (NodeB)
is transparently connected to the IMA board over the SDH network. After the IMA protocol
Troubleshooting
Issue 04 (2010-11-30)
interconnection and ATM service convergence are accomplished on the IMA board, the IMA
E1 links are interconnected to the radio network controller (RNC) through the external optical
interfaces of the IMA board.
Figure 15-2 shows the IMA service networking.
Figure 15-2 IMA service networking
STM-16 two-fiber
bidirectional MSP ring
U2000
NE1
NE2
NE3
NE4
25km
35km
30km
40km
RNC
NodeB 1
NodeB 3
NodeB 2
NodeB 4

IMA Interconnection
The interconnection of the IMA groups are implemented by the state machines of the
interconnected devices. The IMA groups implement the communication between the state
machines through the IMA control protocol (ICP) cells. The operating states of the IMA groups
can be obtained by checking the state machines of the IMA groups and IMA links.
The ICP is used to transmit controlling information (such as IMA protocol version and IMA
frame length) between the communicating parties. In addition, the ICP is used in the frame
synchronization and negotiation of IMA group states at the two ends. Therefore, the ICP is
important in fault analyzing.
Attributes of IMA Groups
The basic principle of IMA interconnection is to ensure consistent configuration of the IMA
group attributes. Inconsistent IMA group attributes may result in IMA group negotiation failures.
The attributes of IMA groups are the IMA transmit frame length, IMA group configuration
mode, and IMA protocol version.
15-3
l IMA Protocol Version: The IMA protocol has two versions: IMA1.0 and IMA1.1. The
IMA groups with different IMA protocol versions cannot be interconnected to each other.
l IMA Transmit Frame Length: The IMA Transmit Frame Length parameter specifies the
length of one IMA frame transmitted by the local equipment. That is, how many ATM cells
are contained in one IMA frame. An IMA frame can contain 32, 64, 128 or 256 ATM cells.
Moreover, each IMA frame contains an IMA control protocol cell (ICP), which is used to
negotiate the IMA protocol and to transmit information. When the adopted protocol is
IMA1.0, the IMA transmit frame length can only be 128.
l IMA Group Configuration Mode:
Symmetrical Mode and Symmetrical Operation: IMA links are configured at both the
transmitting and receiving directions. Only those IMA links whose transmitting and
receiving functions are activated can transmit ATM cells.
Symmetrical Mode and Asymmetrical Operation: IMA links are configured at both the
transmitting and receiving directions. Those IMA links with activated transmitting
function can transmit ATM cells. Those IMA links with activated receiving function
can receive ATM cells.
Asymmetrical Mode and Asymmetrical Operation: IMA links are configured at either
the transmitting or the receiving direction. Those IMA links with activated transmitting
function can transmit ATM cells. Those IMA links with activated receiving function
can receive ATM cells.
15.2 Common Causes
This section describes the common causes of IMA interconnection faults, including external
causes and equipment causes.
Table 15-1 shows the common causes of IMA interconnection faults.
Table 15-1 Common causes of IMA interconnection faults
Fault Types Causes
External causes The E1 links are not connected or the
connection to the E1 links fails.
Obvious bit errors occurs in the E1 links.
Equipment causes The IMA group of the interconnected
equipment is not started.
The E1 link is not added to the IMA group of
the interconnected equipment.
The IMA frame length is inconsistent with
that of the interconnected equipment.
The IMA group configuration mode is
inconsistent with that of the interconnected
equipment.
The IMA protocol version is inconsistent
with that of the interconnected equipment.
Troubleshooting
Issue 04 (2010-11-30)
Fault Types Causes
Some E1 links in the IMA group of the
interconnected equipment become faulty.
The frame formats of the IMA links are
inconsistent.
The IMA chip is faulty.

This section describes the procedures for locating IMA interconnection faults.
Fault Handling Flow
Figure 15-3 shows the procedures for handling the faults in the case of IMA interconnection.
15-5
Figure 15-3 Handling flowchart of IMA interconnection faults
Are the IMA services
normal?
Yes
No
Are there any IMA-
related alarms?
No
Start
Are the IMA groups
normal?
No
Are the IMA links
normal?
No
Replace the IMA E1
links. Restart the IMA
groups.
Yes No
Are the IMA physical
links normal?
Yes
Yes
Are IMA groups added to
the interconnected
equipment? Are IMA links
added to the IMA
groups?
Add IMA groups to the
connected equipment. Add
IMA links to the IMA groups.
Restart the IMA groups.
Set consistent IMA group
attributes for the
interconnected equipment.
Restart the IMA groups.
Replace the board.
Is the IMA chip or
the board faulty?
Are the IMA group
attributes of the
interconnected
equipment consistent?
No
No
Yes
Yes
Yes
End
No
Yes
Contact Huawei engineers
for troubleshooting.
Other faults

Procedure
Step 1 Cause 1: Alarms related to IMA groups are reported.
1. Quety the current alarms on the U2000. For details, refer to the Querying Current Alarms
on U2000. Check whether there is any ALM_IMA_RFI,
ALM_IMA_RE_RX_UNUSABLE, ALM_IMA_RE_TX_UNUSABLE,
ALM_IMA_LIF, ALM_IMA_LODS, or ALM_IMA_LINK_LCD alarm.
2. Handle the IMA faults according to the types of the reported alarms.
3. If the alarm still persists after the implementation of relevant alarm handling measures,
check whether the cross-connection and the line path that carry the IMA links are correctly
Troubleshooting
Issue 04 (2010-11-30)
set. If not, correct the cross-connection configuration, and then check whether the alarm is
cleared.
Step 2 Cause 2: The IMA group is abnormal.
Check whether the transmit rate and receive rate of the IMA group is normal. Check whether
all the transmit links and reveive links are activated. If there is any link that is not activated,
check the status of the IMA link.
Step 3 Cause 3: The IMA link is abnormal.
1. Check the IMA links to locate the faulty direction of the faulty link. Solve the problem by
checking or replace the link.
2. Check whether the IMA attributes are consistent with those of the interconnected
equipment. Ensure that the IMA transmit frame lengths, IMA protocol versions, IMA group
configuration modes, and E1 frame formats are consistent for the equipment at both ends.
Inconsistent attribute configuration may in IMA negotiation failures. Change the attribute
configuration on one end to make it consistent with that of the other end. After changing
the IMA group attributes, reset the IMA groups at both ends of the link for re-negotiation.
NOTE
The attributes of an IMA group are usually configured as follows:
l IMA Transmit Frame Length: 128
l IMA Group Configuration Mode: Symmetrical Mode and Symmetrical Operation
l IMA Protocol Version: 1.1
l Link Frame Format: E1 CRC-4 Multiframe
----End
15.4 Cases on ATM and IMA
This section provides the case analysis of ATM and IMA.
Related cases:
None.
15-7
16 Remote Maintenance Guide
About This Chapter
Remote maintenance guide the user how to enabling the remote maintenance user and
establishing the remote maintenance.
16.1 Introduce
Summarizes how to perform the remote maintenance.
16.2 Enabling a Remote Maintenance User
A remote maintenance user is a network management user who logs in to the U2000 server on
a remote maintenance client. By default, the remote maintenance user is "Disabled". Hence,
enable the remote maintenance user before starting the remote maintenance.
16.3 Establishing Remote Maintenance
This section describes how the U2000 server establishes remote maintenance connection with
the remote terminal.
Troubleshooting 16 Remote Maintenance Guide
16-1
16.1 Introduce
Summarizes how to perform the remote maintenance.
A remote computer (remote end) can connect to the U2000 server on site (local end) through
the public switched telephone network (PSTN) or the Internet. The remote computer then can
perform in-time maintenance to the equipment.
Figure 16-1 shows a connection for remote maintenance. A modem should be installed at each
of the remote maintenance terminal and the U2000 server. The dial-up connection program
should be set. The hardware and software should be configured before the U2000 is installed.
Connection for remote maintenance
Figure 16-1 Connection for remote maintenance
Remote
maintenance
terminal
U2000
server
Modem
PSTN/
Internet
Modem
Serial port
Optical
network
Serial port

When you use the remote maintenance function to maintain the equipment, the U2000 should
perform the following operations in cooperation with the remote end.
l Enabling an remote maintenance user
l Establishing remote maintenance
16.2 Enabling a Remote Maintenance User
A remote maintenance user is a network management user who logs in to the U2000 server on
a remote maintenance client. By default, the remote maintenance user is "Disabled". Hence,
enable the remote maintenance user before starting the remote maintenance.
Troubleshooting
Issue 04 (2010-11-30)
Prerequisite
The operator must have the "NM administrator" authority or higher.
Procedure
Step 1 Choose System Management > Remote Maintenance User Management from the Main
Menu. The Remote Maintenance User Management dialog box is displayed.
Step 2 In the dialog box, set the Enable/Disable parameter to Enable. Set other attributes of the remote
maintenance user.
Step 3 Click Apply.
Step 4 Click Set Password to set the password for the remote maintenance user.
Step 5 Click OK.
----End
16.3 Establishing Remote Maintenance
This section describes how the U2000 server establishes remote maintenance connection with
the remote terminal.
Prerequisite
l The communication connection between the remote maintenance terminal and the U2000
server must have been configured.
l The remote maintenance user must have been enabled.
l The dial-up telephone number, user name and password of the U2000 server must be known
to maintenance personnel at the remote maintenance terminal.
Context
CAUTION
To ensure network security, set the Enable/Disable parameter of the remote maintenance user
to Disable after the remote maintenance.
Procedure
Step 1 On the U2000 server, query the status of the remote maintenance connection. If the remote
maintenance connection is established, go to Step 5. If not established, go to Step 2. The query
methods are listed as follows.
l If the Windows operating system is installed, right-click Network Neighbor and click the
Attribute tab to query the status of the remote maintenance connection.
l If the Sun workstation is installed, open a terminal window and run the ifconfig -a command
to query the status of the remote maintenance connection.
Troubleshooting 16 Remote Maintenance Guide
16-3
Step 2 Double-click the shortcut icon of the dial-up connection on the desktop, for example, Remote
Maintenance, to dial up.
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 in the lower right
corner to establish the connection.
NOTE
After you enter the password and press the Enter key, a line of junk characters are 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 >
Attachment > Command Prompt to display the Command Prompt window. Enter ipconfig
-a in the dialog box and query the dynamic IP address for dial-up access to network.
l If the Sun workstation is installed, display a terminal window and run the ipconfig -a
command to query dynamic IP address for dial-up access to network.
Step 6 Inform the maintenance personnel at the remote end of the queried IP address.
Step 7 The remote maintenance user dials up the U2000 server and logs in to the U2000 client. After
the login succeeds, you can perform the remote maintenance.
----End
Troubleshooting
Issue 04 (2010-11-30)
A Glossary
Terms and abbreviations are listed in an alphabetical order.
A.1 Numerics
A.2 A
A.3 B
A.4 C
A.5 D
A.6 E
A.7 F
A.8 G
A.9 H
A.10 I
A.11 J
A.12 L
A.13 M
A.14 N
A.15 O
A.16 P
A.17 Q
A.18 R
A.19 S
A.20 T
A.21 U
A.22 V
A.23 W
Troubleshooting A Glossary
A-1
A Glossary
Troubleshooting
A-2 Huawei Proprietary and Confidential
Issue 04 (2010-11-30)
A.1 Numerics
1+1 protection An architecture that has one normal traffic signal, one working SNC/trail, one protection
SNC/trail and a permanent bridge. At the source end, the normal traffic signal is
permanently bridged to both the working and protection SNC/trail. At the sink end, the
normal traffic signal is selected from the better of the two SNCs/trails. Due to the
permanent bridging, the 1+1 architecture does not allow an extra unprotected traffic
signal to be provided.
100BASE-T IEEE 802.3 Physical Layer specification for a 100 Mb/s CSMA/CD local area network.
100BASE-TX IEEE 802.3 Physical Layer specification for a 100 Mb/s CSMA/CD local area network
over two pairs of Category 5 unshielded twisted-pair (UTP) or shielded twisted-pair
(STP) wire.
10BASE-T Defined in IEEE 802.3, it is an Ethernet specification that uses the twist pair with the
maximum length of 100 meters at 10 Mbit/s for each network segment.
1:N protection A 1:N protection architecture has N normal service signals, N working SNCs/trails and
one protection SNC/trail. It may have one extra service signal.
1PPS Pulse per second, which, strictly speaking, is not a time synchronization signal. This is
because 1PPS provides only the "gauge" corresponding to the UTC second, but does not
provide the information about the day, month, or year. Therefore, 1PPS is used as the
reference for frequency synchronization. On certain occasions, 1PPS can also be used
on other interfaces for high precision timing.
3R Reshaping, Retiming, Regenerating.
A.2 A
ABR Available Bit Rate
AC Alternating Current
ACAP The Adjacent Channel Alternate Polarization (ACAP) operation provides orthogonal
polarizations between two adjacent communication channels.
Active/Standby
switching of cross-
connect board
If there are two cross-connect boards on the SDH equipment, which are in hot back-up
relation of each other, the operation reliability is improved. When both the cross-connect
boards are in position, the one inserted first is in the working status. Unplug the active
board, the standby one will run in the working status automatically. When the active
cross-connect board fails in self-test, the board is pulled out, the board power supply
fails or the board hardware operation fails, the standby cross-connect board can
automatically take the place of the active one.
add/drop multiplexer A network element that adds/drops the PDH signal or STM-x (x < N) signal to/from the
STM-N signal on the SDH transport network.
ADM See add/drop multiplexer
ADM See optical add/drop multiplexing
A-3
Administrative Unit The information structure which provides adaptation between the higher order path layer
and the multiplex section layer. It consists of an information payload (the higher order
VC) and a AU pointer which indicates the offset of the payload frame start relative to
the multiplex section frame start.
Administrative Unit
Group
One or more Administrative Units occupying fixed, defined positions in an STM payload
are termed an Administrative Unit Group (AUG).An AUG-1 consists of a homogeneous
assembly of AU-3s or an AU-4.
Administrator A user who has authority to access all the Management Domains of the EMLCore
product. He has access to the whole network and to all the management functionalities.
aging time N/A
AIS Alarm Indication Signal
Alarm A means of alerting the operator that specified abnormal condition exists.
Alarm automatic
report
When an alarm is generated on the device side, the alarm is reported to the N2000. Then,
an alarm panel prompts and the user can view the details of the alarm.
alarm cable The cable for generation of visual or audio alarms.
alarm filtering The alarms are reported to the N2000 BMS, which decides whether to display and save
the alarms according to the filtering states of the alarms. The filtered alarms are not
displayed and saved on the N2000 BMS, but still monitored.
alarm indication On the cabinet of an NE, there are four indicators in different colors indicating the current
status of the NE. When the green indicator is on, it indicates that the NE is powered on.
When the red indicator is on, it indicates that a critical alarm is generated. When the
orange indicator is on, it indicates that a major alarm is generated. When the yellow
indicator is on, it indicates that a minor alarm is generated. The ALM alarm indicator on
the front panel of a board indicates the current status of the board. (Metro)
Alarm indication signal A code sent downstream in a digital network as an indication that an upstream failure
has been detected. It is associated with multiple transport layers.
Alarm inversion For the port that has already been configured but has no service, this function can be
used to avoid generating relevant alarm information, thus preventing alarm interference.
The alarm report condition of the NE port is related to the alarm inverse mode (not
inverse, automatic recovery and manual recovery) setting of the NE and the alarm
inversion status (Enable and Disable) setting of the port. When the alarm inversion mode
of NE is set to no inversion, alarms of the port will be reported as usual no matter whatever
the inversion status of the port is. When the alarm inversion mode of the NE is set to
automatic recovery, and the alarm inversion state of the port is set to Enabled, then the
alarm of the port will be suppressed. The alarm inversion status of the port will
automatically recover to "not inverse" after the alarm ends. For the port that has already
been configured but not actually loaded with services, this function can be used to avoid
generating relevant alarm information, thus preventing alarm interference. When the
alarm inverse mode of the NE is set as "not automatic recovery", if the alarm inversion
status of the port is set as Enable, the alarm of the port will be reported.
Alarm Masking Alarms are detected and reported to the N2000 UMS, and whether the alarm information
is displayed and stored is decided by the function of alarm masking. These alarms masked
are not displayed and stored on the N2000 UMS.
Alarm Severity Alarm severity is used to identify the impact of a fault on services. According to ITU-T
recommendations, the alarm is classified into four severities: Critical, Major, Minor,
Warning.
A Glossary
Troubleshooting
Issue 04 (2010-11-30)
Alarm suppression When alarms of various levels occur at the same time, certain lower-level alarms are
suppressed by higher-level alarms, and thus will not be reported.
ALS See Automatic laser shutdown
APS See Automatic Protection Switching
asynchronous Pertaining to, being, or characteristic of something that is not dependent on timing.
Asynchronous
Transfer Mode
A data transfer technology based on cell, in which packets allocation relies on channel
demand. It supports fast packet switching to achieve efficient utilization of network
resources. The size of a cell is 53 bytes, which consist of 48-byte payload and 5-byte
header.
ATM See Asynchronous Transfer Mode
ATPC See Automatic Transmit Power Control
attenuation Reduction of signal magnitude or signal loss, usually expressed in decibels.
AU See Administrative Unit
AUG See Administrative Unit Group
auto-negotiation A mechanism that enables devices to negotiate the SPEED and MODE (duplex or half-
duplex) of an Ethernet Link.
Automatic laser
shutdown
A function that enables the shutdown of the laser when the optical interface board does
not carry services or the fiber is faulty. The automatic laser shutdown (ALS) function
shortens the working time of the laser and thus extends the service life of the laser. In
addition, the ALS prevents human injury caused by the laser beam.
Automatic Protection
Switching
Automatic Protection Switching (APS) is the capability of a transmission system to
detect a failure on a working facility and to switch to a standby facility to recover the
traffic.
Automatic Transmit
Power Control
A method of automatically adjusting the transmit power at the opposite end based on the
transmit signal detected at the receiver.
A.3 B
backplane A backplane is an electronic circuit board containing circuitry and sockets into which
additional electronic devices on other circuit boards or cards can be plugged; in a
computer, generally synonymous with or part of the motherboard.
backup A periodic operation performed on the data stored in the database for the purposes of
database recovery in case that the database is faulty. The backup also refers to data
synchronization between active and standby boards.
bandwidth A range of transmission frequencies that a transmission line or channel can carry in a
network. In fact, it is the difference between the highest and lowest frequencies the
transmission line or channel. The greater the bandwidth, the faster the data transfer rate.
BDI Backward Defect Indicator
BER See Bit Error Rate
Binding strap A component installed on two sides of the cabinet for binding various cables.
binding strap The binding strap is 12.7 mm wide, with one hook side (made of transparent
polypropylene material) and one mat side (made of black nylon material).
A-5
BIP BIP-X code is defined as a method of error monitoring. With even parity an X-bit code
is generated by the transmitting equipment 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, etc. Even parity is
generated by setting the BIP-X bits so that there is an even number of 1s in each monitored
partition of the signal. A monitored partition comprises all bits which are in the same bit
position within the X-bit sequences in the covered portion of the signal. The covered
portion includes the BIP-X.
bit error An error that occurs in some bits in the digital code stream after being received, judged,
and regenerated, thus damaging the quality of the transmitted information
Bit Error Rate Bit error rate. Ratio of received bits that contain errors. BER is an important index used
to measure the communications quality of a network.
BITS See Building Integrated Timing Supply
bound path Binding several seriel paths into a parallel path, thus improving the data throughput
capacity.
BPDU Bridge Protocol Data Unit
bridge A device that connects two or more networks and forwards packets among them. Bridges
operate at the physical network level. Bridges differs 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.
broadcast The process of sending packets from a source to multiple destinations. All the ports of
the nodes in the network can receive packets.
Broadcast A means of delivering information to all members in a network. The broadcast range is
determined by the broadcast address.
BSC Base Station Controller
BSS Base Station Subsystem
Build-in WDM A function which integrates some simple WDM systems into products that belong to the
OSN series . That is, the OSN products can add or drop several wavelengths directly.
Building Integrated
Timing Supply
A building timing supply that minimizes the number of synchronization links entering
an office. Sometimes referred to as a synchronization supply unit.
BWS Backbone WDM System
A.4 C
cabling The method by which a group of insulated conductors is mechanically assembled or
twisted together.
cabling aperture A hole which is used for cable routing in the cabinet.
Cabling frame The frame which is used for cable routing over the cabinet.
cabling trough The trough which is used for cable routing in the cabinet.
A Glossary
Troubleshooting
Issue 04 (2010-11-30)
captive nut Captive nuts (or as they are more correctly named, 'tee nuts') have a range of uses but
are more commonly used in the hobby for engine fixing (securing engine mounts to the
firewall), wing fixings, and undercarriage fixing.
CAR See committed access rate
CAS Channel Associated Signaling
CBR See Constant Bit Rate
CBS Committed Burst Size
CCDP Co-Channel Dual Polarization
CCM Continuity Check Message
CDR Clock and Data Recovery
CDVT See Cell Delay Variation Tolerance
Cell Delay Variation
Tolerance
This parameter measures the tolerance level a network interface has to aggressive
sending (back-to-back or very closely spaced cells) by a connected device, and does not
apply to end-systems.
Centralized alarm
system
The system that gathers all the information about alarms into a certain terminal console.
CFM Connectivity Fault Management
Chain network One type of network that all network nodes are connected one after one to be in series.
channel A telecommunication path of a specific capacity and/or at a specific speed between two
or more locations in a network. The channel can be established through wire, radio
(microwave), fiber or a combination of the three.The amount of information transmitted
per second in a channel is the information transmission speed, expressed in bits per
second. For example, b/s (100 bit/s), kb/s (103 bit/s), Mb/s (106 bit/s), Gb/s (109 bit/s),
and Tb/s (1012 bit/s).
CIR Committed Information Rate
Circuit The circuit of the service port on the access device.
CIST Common and Internal Spanning Tree
class of service Class of service (CoS) is a technology or method used to classify services into different
categories according to the service quality.
Class of Service Class of Service is abbreviated to CoS. CoS is a rule for queuing. It classifies the packets
according to the service type field or the tag in packets, and specifies different priorities
for them. All the nodes in DiffServ domain forwards the packets according to their
priorities.
client A device that sends requests, receives responses, and obtains services from the server.
Clock Synchronization Also called frequency synchronization, clock synchronization means that the signal
frequency traces the reference frequency, but the start point need not be consistent.
Clock tracing The method to keep the time on each node being synchronized with a clock source in a
network.
CLP Cell Loss Priority
CM See Configuration Management
A-7
committed access rate A traffic control method that uses a set of rate limits to be applied to a router interface.
CAR is a configurable method by which incoming and outgoing packets can be classified
into QoS (Quality of Service) groups, and by which the input or output transmission rate
can be defined.
Concatenation A process that combines multiple virtual containers. The combined capacities can be
used a single capacity. The concatenation also keeps the integrity of bit sequence.
Configuration Data A command file for an NE which defines the configuration of the NE hardware. With
the file, the NE can coordinate with other NEs in the entire network. Configuration data
is the key factor for the normal running of the entire network.
Configuration
Management
In a network, a system for gathering current configuration information from all nodes in
a LAN.
Configure To set the basic parameters of an operation object.
congestion An extra intra-network or inter-network traffic resulting in decreasing network service
efficiency.
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.
Constant Bit Rate constant bit rate. 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.
convergence It refers to the speed and capability for a group of networking devices to run a specific
routing protocol. It functions to keep the network topology consistent.
Convergence A process in which multiple channels of low-rate signals are multiplexed into one or
several channels of required signals.
Convergence service A service that provides enhancements to an underlying service in order to provide for
the specific requirements of the convergence service user.
Conversion In the context of message handling, a transmittal event in which an MTA transforms
parts of a message content from one encoded information type to another, or alters a
probe so it appears that the described messages were so modified.
corrugated tube N/A
CoS See class of service
CoS See Class of Service
CPU Central Processing Unit
CRC See Cyclic Redundancy Check
current alarm An alarm in unrecovered and unacknowledged state, unrecovered and acknowledged
state, or recovered and unacknowledged state. Treatment measures must be taken on
these alarms.
Current Performance
Data
Performance data stored in the current register. An NE provides two types registers for
each performance parameter of the performance monitoring entity. The registers are 15-
minute register and 24-hour register, which are used to accumulate the performance data
within the current monitoring period.
A Glossary
Troubleshooting
Issue 04 (2010-11-30)
Cyclic Redundancy
Check
A procedure used in checking 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 transmission and includes it in the packet that it
sends to the receiving device. The receiving device repeats the same calculation after
transmission. If both devices obtain the same result, it is assumed that the transmission
was error free. The procedure is known as a redundancy check because each transmission
includes not only data but extra (redundant) error-checking values. Communications
protocols such as XMODEM and Kermit use cyclical redundancy checking.
A.5 D
DC Direct Current
DCC Data Communication Channel
DCD Data Carrier Detect
DCE Data Circuit-terminal Equipment
DCN Data Communication Network
DDF See Digital Distribution Frame
DDN Digital Data Network
Defect A limited interruption in the ability of an item to perform a required function.
demultiplexing To separate from a common input into several outputs. Demultiplexing occurs at many
levels. Hardware demultiplexes signals from a transmission line based on time or carrier
frequency to allow multiple, simultaneous transmissions across a single physical cable.
Device set It is an aggregate of multiple managed equipments. Device set facilitates the authority
management on devices in the management domain of the U2000. If some operation
authorities over one device set are assigned to a user (user group), these operation
authorities over all devices of the device set are assigned to the user (user group), thus
eliminating the need to set the operation authorities over these devices respectively. It is
suggested to design device set according to such criteria as geographical region, network
level, device type, etc.
differentiated services
code point
Values for a 6-bit field defined for the IPv4 and IPv6 packet headers that enhance class
of service (CoS) distinctions in routers.
Differentiated Services
Code Point
Differentiated Services CodePoint. A marker in the header of each IP packet using bits
0-6 in the DS field. Routers provide differentiated classes of services to various service
streams/flows based on this marker. In other words, routers select corresponding PHB
according to the DSCP value.
DiffServ Differentiated Services
Digital Distribution
Frame
Digital Distribution Frame. A frame which is used to transfer cables.
A-9
digital signal A signal in which information is represented by a limited number of discrete statesfor
example, high and low voltagesrather than by fluctuating levels in a continuous stream,
as in an analog signal. In the pulse code modulation (PCM) technology, the 8 kHz
sampling frequency is used and a byte contains 8 bits in length. Therefore, a digital signal
is also referred to as a byte-based code stream. Digital signals, with simple structures
and broad bandwidth, are easy to shape or regenerate, and are not easily affected by
external interference.
Distributed Link
Aggregation Group
The distributed link aggregation group (DLAG) is a board-level port protection
technology used to detect unidirectional fiber cuts and to negotiate with the opposite end.
In the case of a link down failure on a port or a hardware failure on a board, the services
can automatically be switched to the slave board, thus realizing 1+1 protection for the
inter-board ports.
DLAG See Distributed Link Aggregation Group
DNI See Dual Node Interconnection
domain A logical subscriber group based on which the subscriber rights are controlled.
DQDB Distributed Queue Dual Bus
DSCP See differentiated services code point
DSCP See Differentiated Services Code Point
DSL Digital Subscriber Line
DSLAM Digital Subscriber Line Access Multiplexer
DSR Data Set Ready
DTE Data Terminal Equipments
DTR Data Terminal Ready
Dual Node
Interconnection
DNI provides an alternative physical interconnection point, between the rings, in case
of an interconnection failure scenario.
DVB-ASI Digital Video Broadcast- Asynchronous Serial Interface
DVMRP Distance Vector Multicast Routing Protocol
DWDM Dense Wavelength Division Multiplexing
A.6 E
E-AGGR Ethernet-Aggregation
E-LAN Ethernet LAN
E-LAN A L2VPN service type that is provided for the user Ethernet in different domains over
the PSN network. For the user Ethernet, the entire PSN network serves as a Layer 2
switch.
E-Line Ethernet line. An point-to-point private service type that is provided for the user Ethernet
in different domains.
Ear bracket A component on the side of the subrack. It is used to install the subrack into a cabinet.
ECC See Embedded Control Channel
A Glossary
Troubleshooting
Issue 04 (2010-11-30)
EFM Ethernet in the First Mile
ElectroStatic Discharge A sudden flow of electric current through a material that is normally an insulator.
Embedded Control
Channel
An ECC provides a logical operations channel between SDH NEs, utilizing a data
communications channel (DCC) as its physical layer.
EMS Element Management System
encapsulation The technique used by layered protocols to add header information and possibly tail
information to the protocol data unit.
Enterprise System
Connection
A path protocol which connects the host with various control units in a storage system.
It is a serial bit stream transmission protocol. The transmission rate is 200 Mbit/s.
Entity A part, device, subsystem, functional unit, equipment or system that can be individually
considered. For ETH-OAM, an OAM entity generally refers to a specified system or
subsystem that supports the OAM protocol. For example, a Huawei Ethernet service
processing board is an OAM entity.
EoD Ethernet Over Dual Domains
EPL See Ethernet Private Line
EPLAN Ethernet Private LAN Service
ESCON See Enterprise System Connection
ESD See ElectroStatic Discharge
ESD jack Electrostatic discharge jack. A hole in the cabinet or shelf, which connect the shelf or
cabinet to the insertion of ESD wrist strap.
Ethernet A technology complemented in LAN. It adopts Carrier Sense Multiple Access/Collision
Detection. The speed of an Ethernet interface can be 10 Mbit/s, 100 Mbit/s, 1000 Mbit/
s or 10000 Mbit/s. The Ethernet network features high reliability and easy maintaining..
Ethernet Alarm Group The Ethernet alarm group periodically obtain the statistics value to compare with the
configured threshold. If the value exceeds the threshold, an event is reported.
Ethernet Private LAN Both a LAN service and a private service. Transport bandwidth is never shared between
different customers.
Ethernet Private Line A point-to-point interconnection between two UNIs without SDH bandwidth sharing.
Transport bandwidth is never shared between different customers.
ethernet virtual private
line service
An Ethernet service type, which carries Ethernet characteristic information over shared
bandwidth, point-to-point connections, provided by SDH, PDH, ATM, or MPLS server
layer networks.
ETSI European Telecommunications Standards Institute
EVPL See ethernet virtual private line service
Exercise Switching An operation to check if the protection switching protocol functions normally. The
protection switching is not really performed.
Exerciser - Ring This command exercises ring protection switching of the requested channel without
completing the actual bridge and switch. The command is issued and the responses are
checked, but no working traffic is affected.
Extended ID The number of the subnet that an NE belongs to, for identifying different network
segments in a WAN. The extended ID and ID form the physical ID of the NE.
A-11
extra traffic The traffic that is carried over the protection channels when that capacity is not used for
the protection of working traffic. Extra traffic is not protected.
A.7 F
Failure If the fault persists long enough to consider the ability of an item with a required function
to be terminated. The item may be considered as having failed; a fault has now been
detected.
Fairness For any link specified in a ring network, if the data packets transmitted by the source
node are constrained by the fairness algorithm, the source node is provided with certain
bandwidth capacities. This feature of RPR is called fairness.
fairness algorithm An algorithm designed to ensure the fair sharing of bandwidth among stations in the case
of congestion or overloading.
fault An accidental condition that causes a functinal unit to fail to perform its required
function.
FC Fiber Channel
FD See frequency diversity
FDDI See fiber distributed data interface
FDI Forward Defect Indicator
FE Fast Ethernet
feature code Code(s) used to select/activate a service feature (e.g. forwarding, using two or three digit
codes preceded by * or 11 or #, and which may precede subsequent digit selection).
FEC See forwarding equivalence class
FEC See Forward Error Correction
fiber A kind of fiber used for connections between the subrack and the ODF, and for
connections between subracks or inside a subrack.
Fiber Connect. A new generation connection protocol which connects the host with various control units.
It carries single byte command protocol through the physical path of fiber channel, and
provides higher rate and better performance than ESCON.
Fiber Connector A device installed at the end of a fiber, optical source or receive unit. It is used to couple
the optical wave to the fiber when connected to another device of the same type. A
connector can either connect two fiber ends or connect a fiber end and a optical source
(or a detector).
fiber distributed data
interface
A standard developed by the American National Standards Institute (ANSI) for high-
speed fiber-optic local area networks (LANs). FDDI provides specifications for
transmission rates of 100 megabits (100 million bits) per second on networks based on
the token ring network.
A Glossary
Troubleshooting
Issue 04 (2010-11-30)
fiber/cable Fiber & Cable is the general name of optical fiber and cable. It refers to the physical
entities that connect the transmission equipment, carry transmission objects (user
information and network management information) and perform transmission function
in the transmission network. The optical fiber transmits optical signal, while the cable
transmits electrical signal. The fiber/cable between NEs represents the optical fiber
connection or cable connection between NEs. The fiber/cable between SDH NEs
represents the connection relation between NEs. At this time, the fiber/cable is of optical
fiber type.
FICON See Fiber Connect
FIFO First In First Out
Flow An aggregation of packets that have the same characteristics. On the T2000 or NE
software, flow is a group of classification rules. On boards, it is a group of packets that
have the same quality of service (QoS) operation. At present, two flows are supported:
port flow and port+VLAN flow. Port flow is based on port ID and port+VLAN flow is
based on port ID and VLAN ID. The two flows cannot coexist in the same port.
Forced switch This function forces the service to switch from the working channel to the protection
channel, with the service not to be restored automatically. This switch occurs regardless
of the state of the protection channels or boards, unless the protection channels or boards
are satisfying a higher priority bridge request.
Forward Error
Correction
A bit error correction technology that adds the correction information to the payload at
the transmit end. Based on the correction information, the bit errors generated during
transmission are corrected at the receive end.
forwarding equivalence
class
A term used in Multiprotocol Label Switching (MPLS) to describe a set of packets with
similar or identical characteristics which may be forwarded the same way; that is, they
may be bound to the same MPLS label.
FPGA Field Programmable Gate Array
frame A frame, starting with a header, is a string of bytes with a specified length. Frame length
is represented by the sampling circle or the total number of bytes sampled during a circle.
A header comprises one or a number of bytes with pre-specified values. In other words,
a header is a code segment that reflects the distribution (diagram) of the elements pre-
specified by the sending and receiving parties.
Free-run mode An operating condition of a clock, the output signal of which is strongly influenced by
the oscillating element and not controlled by servo phase-locking techniques. In this
mode the clock has never had a network reference input, or the clock has lost external
reference and has no access to stored data, that could be acquired from a previously
connected external reference. Free-run begins when the clock output no longer reflects
the influence of a connected external reference, or transition from it. Free-run terminates
when the clock output has achieved lock to an external reference.
frequency diversity A diversity scheme that enables two or more microwave frequencies with a certain
frequency interval are used to transmit/receive the same signal and selection is then
performed between the two signals to ease the impact of fading.
FTP File Transfer Protocol
Full duplex The system that can transmit information in both directions on a communication link.On
the communication link, both parties can send and receive data at the same time.
A-13
A.8 G
Gain The ratio between the optical power from the input optical interface of the optical
amplifier and the optical power from the output optical interface of the jumper fiber,
which expressed in dB.
Gateway IP When an NE accesses a remote network management system or NE, a router can be used
to enable the TCP/IP communication. In this case, the IP address of the router is the
gateway IP. Only the gateway NE requires the IP address. The IP address itself cannot
identify the uniqueness of an NE. The same IP addresses may exist in different TCP/IP
networks. An NE may have multiple IP addresses, for example, one IP address of the
network and one IP address of the Ethernet port.
Gateway Network
Element
Gateway NE refers to the NE that communicates with the NMS via Ethernet or serial
port line. The non-gateway NE communicates with the gateway NE via ECC and
communicates with the NMS via the gateway NE. The gateway NE is a communication
route that the U2000 must pass through when managing the entire network. The
communication status between the gateway NE and the U2000 can be:(1) Normal: The
current communication is efficient; (2) Connecting: The destination gateway responds,
and the communication is interrupted but is being connected; (3) Disconnected: The
destination gateway does not respond (Maybe the network cable is disconnected or not
within the same network segment), and the communication is unreachable or the gateway
is disabled manually.
GE Gigabit Ethernet
GFP Generic Framing Procedure
GFP GFP is a framing and encapsulated method which can be applied to any data type. It has
been standardized by ITU-T SG15.
GNE See Gateway Network Element
GPS Global Positioning System
GSM Global System for Mobile Communications
GTS Generic Traffic Shaping
GUI Graphic User Interface
A.9 H
half-duplex An operation mode of the Ethernet port. In half-duplex mode, a port can only send or
receive data at a time.
handle A component of the panel. It is used to insert or remove boards and RTMs in and out of
slots.
Hardware loopback A connection mode in which a fiber jumper is used to connect the input optical interface
to the output optical interface of a board to achieve signal loopback.
HDLC High level Data Link Control
HEC Header Error Control
History alarm The confirmed alarms that have been saved in the memory and other external memories.
A Glossary
Troubleshooting
Issue 04 (2010-11-30)
History Performance
Data
The performance data that is stored in the history register or that is autoreported and
stored in the NMS.
HP Higher Order Path
HPT Higher Order Path Termination
A.10 I
IC Integrated Circuit
IDU Indoor Unit
IEEE Institute of Electrical and Electronics Engineers
IETF Internet Engineering Task Force
IF Intermediate Frequency
IGMP See Internet Group Management Protocol
IGMP Snooping IGMP proxy means that in some network topologies, the device does not set up the
multicast routes, but to learn the information about the accessed multicast group members
and forward it to the upstream multicast router. The upstream multicast router sets up
the multicast routes.
IMA frame The IMA frame is used as the unit of control in the IMA protocol. It is a logical frame
defined as M consecutive cells, numbered 0 to M-l, transmitted on each of the N links
in an IMA group.
Input jitter tolerance The maximum amplitude of sinusoidal jitter at a given jitter frequency, which, when
modulating the signal at an equipment input port, results in no more than two errored
seconds cumulative, where these errored seconds are integrated over successive 30
second measurement intervals.
Intelligent power
adjusting
The factors such as fiber cut, degradation of equipment, and removal of connectors may
result in the loss of the optical power signals. The function of intelligent power adjusting
(IPA) enables the ROP laser and booster amplifier (BA) of a section to be shut down
automatically. In this way, the maintainers, their eyes in particular, can be protected for
the exposed optical fibers when they are performing the repairs.
Interface board area The area for the interface boards on the subrack.
Internal cable The cables and optical fibers which are used for interconnecting electrical interfaces and
optical interfaces within the cabinet.
Internet Group
Management Protocol
The protocol for managing the membership of Internet Protocol multicast groups among
the TCP/IP protocols. It is used by IP hosts and adjacent multicast routers to establish
and maintain multicast group memberships.
IP Internet Protocol
IP address In the TCP/IP protocol, it is used to uniquely identify the 32-bit address of the
communication port, An IP address consists of a network ID and a unique host ID. An
IP address consists of the decimal values of its eight bytes, separated with periods; for
example,192.168.7.27.
IP over DCC The IP Over DCC follows TCP/IP telecommunications standards and controls the remote
NEs through the Internet. The IP Over DCC means that the IP over DCC uses overhead
DCC byte (the default is D1-D3) for communication.
A-15
IPA See Intelligent power adjusting
IS-IS Intermedia System-Intermedia System
ISDN Integrated Services Digital Network
ISO International Standard Organization
ISP Internet Service Provider
IST Internal Spanning Tree
ITU-T International Telecommunication Union Telecommunication Standardization
A.11 J
Jitter Short waveform variations caused by vibration, voltage fluctuations, and control system
instability.
jitter tolerance Jitter tolerance is defined as the peak-to-peak amplitude of sinusoidal jitter applied on
the input ATM-PON signal that causes a 1 dB optical power penalty at the optical
equipment.
A.12 L
label A mark on a cable, a subrack, or a cabinet for identification.
Label A short identifier that is of fixed length and local significance. A label is used to uniquely
identify the FEC to which a packet belongs. A label does not contain topology
information. It is carried in the header of a packet and does not contain topology
information.
LACP See Link Aggregation Control Protocol
LAG See link aggregation group
LAN Local Area Network
LAPS Link Access Procedure-SDH
Laser A component that generates directional optical waves of narrow wavelengths. The laser
light has better coherence than ordinary light. The fiber system takes the semi-conductor
laser as the light source.
Layer A concept used to allow the transport network functionality to be described hierarchically
as successive levels; each layer being solely concerned with the generation and transfer
of its characteristic information.
layer 2 switch A data forwarding method. In LAN, a network bridge or 802.3 Ethernet switch transmits
and distributes packet data based on the MAC address. Since the MAC address is the
second layer of the OSI model, this data forwarding method is called layer 2 switch.
LB See Loopback
LBM Loopback Message
LBR Loopback Reply
LC Lucent Connector
A Glossary
Troubleshooting
Issue 04 (2010-11-30)
LCAS See Link Capacity Adjustment Scheme
LCD Liquid Crystal Display
LCT See Local craft terminal
License A permission that the vendor provides for the user with a specific function, capacity, and
durability of a product. A license can be a file or a serial number. Usually the license
consists of encrypted codes, and the operation authority varies with different level of
license.
Link In the topology view, a link is used to identify the physical or logical connection between
two topological nodes.
Link Aggregation
Control Protocol
Link Aggregation Control Protocol (LACP) is part of an IEEE specification (802.3ad)
that allows you to bundle several physical ports to form a single logical channel. LACP
allows a switch to negotiate an automatic bundle by sending LACP packets to the peer.
link aggregation group 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
The Link Capacity Adjustment Scheme (LCAS) is designed to allow the dynamic
provisioning of bandwidth, using VCAT, to meet customer requirements.
LLC Logical Link Control
Local craft terminal A single layer network management scheme that manages a transmission network
consisting of a maximum of five NEs. In this way, the comprehensive management of
the multi-service transmission network is achieved. Normally, the cross-over network
cables and serial port cables are used to connect the local craft terminal (LCT) to an NE.
Then, the LCT can configure and maintain a single NE.
Locked switching When the switching condition is satisfied, this function disables the service from being
switched from the working channel to the protection channel. When the service has been
switched, the function enables the service to be restored from the protection channel to
the working channel.
LOF Loss of frame
LOM Loss Of Multiframe
Loopback A troubleshooting technique that returns a transmitted signal to its source so that the
signal or message can be analyzed for errors.
LOS Loss Of Signal
Lower Threshold When the performance event count value is smaller than a certain value, a threshold-
crossing event occurs. The value is the lower threshold.
LP Lower Order Path
LPT Link State Pass Through
LSP Label Switched Path
LSR Label Switching Router
LT Link Trace
A-17
A.13 M
MA See Maintenance Association
MAC Medium Access Control
Maintenance
Association
That portion of a Service Instance, preferably all of it or as much as possible, the
connectivity of which is maintained by CFM. It is also a full mesh of Maintenance
Entities.
Maintenance Domain The network or the part of the network for which faults in connectivity are to be managed,
belonging to a single administration. The boundary of a Maintenance Domain is defined
by a set DSAPs, each of which may become a point of connectivity to a Service Instance.
MAN See Metropolitan Area Network
Manual switching A protection switching. When the protection path is normal and there is no request of a
higher level switching, the service is manually switched from the working path to the
protection path, to test whether the network still has the protection capability.
Mapping A procedure by which tributaries are adapted into virtual containers at the boundary of
an SDH network.
Marking-off template A quadrate cardboard with four holes. It is used to mark the positions of the installation
holes for the cabinet.
MBS Maximum Burst Size
MCF Message Communication Function
MCR Minimum Cell Rate
MD See Maintenance Domain
Mean launched power The average power of a pseudo-random data sequence coupled into the fibre by the
transmitter.
MEP Maintenance End Point
Metropolitan Area
Network
A metropolitan area network (MAN) is a network that interconnects users with computer
resources in a geographic area or region larger than that covered by even a large local
area network (LAN) but smaller than the area covered by a wide area network (WAN).
The term is applied to the interconnection of networks in a city into a single larger
network (which may then also offer efficient connection to a wide area network). It is
also used to mean the interconnection of several local area networks by bridging them
with backbone lines. The latter usage is also sometimes referred to as a campus network.
MIB Management Information Base
MIP Maintenance Intermediate Point
MODEM MOdulator-DEModulator
MP Maintenance Point
MPID Maintenance Point Identification
MPLS See Multi-Protocol Label Switch
MS Multiplex Section
MSA Multiplex Section Adaptation
A Glossary
Troubleshooting
Issue 04 (2010-11-30)
MSOH See Multiplex Section Overhead
MSP See multiplex section protection
MST Multiplex Section Termination
MSTI Multiple Spanning Tree Instance
MSTP See Multi-service transmission platform
MSTP See Multiple spanning tree protocol
MTIE Maximum Time Interval Error
MTU Maximum Transmission Unit
Multi-Protocol Label
Switch
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. It improves the cost performance and expandability of
networks, and is beneficial to routing.
Multi-service
transmission platform
It is based on the SDH platform, capable of accessing, processing and transmitting TDM
services, ATM services, and Ethernet services, and providing unified management of
these services.
Multicast A process of transmitting packets of data 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.
Multiple spanning tree
protocol
The MSTP 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.
Multiplex Section
Overhead
The overhead that comprises rows 5 to 9 of the SOH of the STM-N signal. See SOH
definition.
multiplex section
protection
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.
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.
A.14 N
N+1 protection A radio link protection system composed of N working channels and one protection
channel.
NE See network element
NE Explorer The main operation interface, of the U2000, which is used to manage the OptiX
equipment. In the NE Explorer, the user can configure, manage and maintain the NE,
boards, and ports on a per-NE basis.
A-19
network element A network element (NE) contains both the hardware and the software running on it. One
NE is at least equipped with one system control board which manages and monitors the
entire network element. The NE software runs on the system control board.
network node interface The interface at a network node which is used to interconnect with another network node.
network segment Network Segment means any discrete part of the Network.
NLP Normal Link Pulse
NMS Network Management System
NNI See network node interface
NPC Network Parameter Control
nrt-VBR Non Real-Time Variable Bit Rate
NRZ Non Return to Zero code
NSAP Network Service Access Point
NTP Network Time Protocol
A.15 O
OA See Optical Amplifier
OADM Optical Add/Drop Multiplexer
OAM Operations, Administration and Maintenance
OAM auto-discovery In the case of OAM auto-discovery, two interconnected ports, enabled with the Ethernet
in the First Mile OAM (EFM OAM) function, negotiate to determine whether the mutual
EFM OAM configuration match with each other by sending and responding to the OAM
protocol data unit (OAMPDU). If the mutual EFM OAM configuration match, the two
ports enter the EFM OAM handshake phase. In the handshake phase, the two ports
regularly send the OAMPDU to maintain the neighborhood relation.
OCP See Optical Channel Protection
ODF See Optical Distribution Frame
ODU Outdoor Unit
OFS Out-of-frame Second
OHA Overhead Access Function
OLT Optical Line Terminal
Online Help The capability of many programs and operating systems to display advice or instructions
for using their features when so requested by the user.
ONU Optical Network Unit
OOF Out of Frame
optical add/drop
multiplexing
A process that adds the optical signals of various wavelengths to one channel and drop
the optical signals of various wavelengths from one channel.
Optical Amplifier Devices or subsystems in which optical signals can be amplified by means of the
stimulated emission taking place in a suitable active medium.
A Glossary
Troubleshooting
Issue 04 (2010-11-30)
Optical attenuator A passive device that increases the attenuation in a fiber link. It is used to ensure that the
optical power of the signals received at the receive end is not extremely high. It is
available in two types: fixed attenuator and variable attenuator.
Optical Channel
Protection
In an optical transmission link that contains multiple wavelengths, when a certain
wavelength goes faulty, the services at the wavelength can be protected if the optical
channel protection is configured.
Optical Connector A component normally attached to an optical cable or piece of apparatus for the purpose
of providing frequent optical interconnection/disconnection of optical fibers or cables.
Optical Distribution
Frame
A frame which is used to transfer and spool fibers.
Optical Interface A component that connects several transmit or receive units.
Optical Time Domain
Reflectometer
A device that sends a very short pulse of light down a fiber optic communication system
and measures the time history of the pulse reflection.
orderwire A channel that provides voice communication between operation engineers or
maintenance engineers of different stations.
OSI Open Systems Interconnection
OSN Optical Switch Node
OSPF Open Shortest Path First
OTDR See Optical Time Domain Reflectometer
OTU Optical Transponder Unit. A device or subsystem that converts the accessed client signals
into the G.694.1/G.694.2-compliant WDM wavelength.
Output optical power The ranger of optical energy level of output signals.
Overhead Extra bits in a digital stream used to carry information besides traffic signals. Orderwire,
for example, would be considered overhead information.
A.16 P
Paired slots Two slots of which the overheads can be passed through by using the bus on the
backplane. When the SCC unit is faulty or offline, the overheads can be passed through
between the paired slots by using the directly connected overhead bus. When two SDH
boards form an MSP ring, the boards need to be inserted in paired slots so that the K
bytes can be passed through.
pass through When services are passed through, it indicates that transmission equipment does not
process the service received and only detects the signal quality.
Path A performance resource object defined in the network management system. The left end
of a path is a device node whose port needs to be specified and the right end of a path is
a certain IP address which can be configured by the user. By defining a path in the
network management system, a user can test the performance of a network path between
a device port and an IP address. The tested performance may be the path delay, packet
loss ratio or other aspects.
path protection Path protection is a special case of fixed partitioning sub-path protection technique where
every primary path is partitioned into only one sub-path (i.e., h = D, diameter of the
network).
A-21
PBS Peak Burst Size
PC Personal Computer
PCM Pulse Code Modulation
PCR Peak Cell Rate
PDH See Plesiochronous Digital Hierarchy
PE Provider Edge. A PE is the name of the device or set of devices at the edge of the provider
network with the functionality that is needed to interface with the customer.
Performance register Performance register is the memory space for performance event counts, including 15-
min current performance register, 24-hour current performance register, 15-min history
performance register, 24-hour history performance register, UAT register and CSES
register. The object of performance event monitoring is the board functional module, so
every board functional module has a performance register. A performance register is
used to count the performance events taking place within a period of operation time, so
as to evaluate the quality of operation from the angle of statistics.
performance threshold The performance threshold is a limit for generating an alarm for a selected entity. When
the measurement data satisfies the preset alarm threshold or exceeds the preset grads,
the PM subsystem generates a performance alarm.
Performance threshold Performance events usually have upper and lower thresholds. When the performance
event count value exceeds the upper threshold, a performance threshold-crossing event
is generated; when the performance event count value is below the upper threshold for
a period of time, the performance threshold-crossing event is ended. In this way,
performance jitter caused by some sudden events can be shielded. A few performance
events only have one threshold, which is the special case that upper threshold and lower
threshold are equal.
Permanent Virtual
Connection
Traditional ATM Permanent Virtual Connection that is established/released upon a
request initiated by a management request procedure (that is all nodes supporting the
connections need to be instructed by the network management).
PGND Protection Ground
PIM-SM Protocol Independent Multicast-Sparse Mode
PIR Peak Information Rate
plesiochronous Qualifying two time-varying phenomena, time-scales, or signals in which corresponding
significant instants occur at the same rate, any variations in rate being constrained within
specified limits. Note: Corresponding significant instants are separated by time intervals
having durations which may vary without limit.
Plesiochronous Digital
Hierarchy
The Plesiochronous Digital Hierarchy (PDH) is a technology used in
telecommunications networks to transport large quantities of data over digital transport
equipment such as fibre optic and microwave radio systems.
PLL Phase-Locked Loop
Pointer An indicator whose value defines the frame offset of a virtual container with respect to
the frame reference of the transport entity on which it is supported.
POS Packet Over SDH
Power box A direct current power distribution box at the upper part of a cabinet, which supplies
power for the subracks in the cabinet.
A Glossary
Troubleshooting
Issue 04 (2010-11-30)
PPP Point-to-Point Protocol
PRBS See Pseudo-Random Binary Sequence
PRC Primary Reference Clock
Primitive In the hierarchy of signaling system No.7, when the upper layer applies for services from
the lower layer or the lower layer transmits services to the upper layer, the data is
exchanged between the user and the service provider. In this case, the data transmitted
between adjacent layers is called primitive.
Private Line The line, such as the subscriber cable and trunk cable, which are hired by the
telecommunication carrier and are used to meet the special requirement of the user. The
line is also called hired line. Generally, the switch device is not contained.
protection grounding A cable which connects the equipment and the protection grounding bar. Usually, the
cable is yellow and green.
Protection path A specific path that is part of a protection group and is labeled protection.
Protection service A specific service that is part of a protection group and is labelled protection.
Protection subnet In the NMS, the protection subnet becomes a concept of network level other than
multiplex section rings or path protection rings. The protection sub-network involves
NEs and fibre cable connections.
Protection View The user interface, of the network management system, which is used to manage
protection in the network.
PS Packet Switched
PSD Power Spectral Density
Pseudo-Random
Binary Sequence
A sequence that is random in a sense that the value of an element is independent of the
values of any of the other elements, similar to real random sequences.
PVC See Permanent Virtual Connection
PW Pseudo Wire
PW Pseudo wire. A mechanism that bears the simulated services between PEs on the PSN
(Packet Switched Network).
A.17 Q
QoS See Quality of Service
Quality of Service Quality of Service, which determines the satisfaction of a subscriber for a service. QoS
is influenced by the following factors applicable to all services: service operability,
service accessibility, service maintainability, and service integrity.
A.18 R
Rapid Spanning Tree
Protocol
An evolution of the Spanning Tree Protocol, providing for faster spanning tree
convergence after a topology change. The RSTP protocol is backward compatible with
the STP protocol.
RDI Remote Defect Indication
A-23
Receiver Sensitivity Receiver sensitivity is defined as the minimum acceptable value of average received
power at point R to achieve a 1 x 10-10 BER.
Reference clock A reference clock is usually of high stability , accuracy and autonomy and it's frequency
can be compared with other clock as a benchmark.
REG A piece of equipment or device that regenerates electrical signals.
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.
Regenerator section
overhead
The regenerator section overhead comprises rows 1 to 3 of the SOH of the STM-N signal.
Remote optical
pumping amplifier
(ROPA)
An remote optical amplifier sub-system designed for applications where power supply
and monitoring systems are unavailable. The ROPA subsystem is a power compensation
solution to the ultra-long distance long hop (LHP) transmission.
Resilient Packet Ring A network topology being developed as a new standard for fiber optic rings.
RF Radio Frequency
RFA Request For Announcement
RFI Request for Information
ring network A ring network is a network topology in which each node connects to exactly two other
nodes, forming a circular pathway for signals.
RNC Radio Network Controller
route A route is the path that network traffic takes from its source to its destination. In a TCP/
IP network, each IP packet is routed independently. Routes can change dynamically.
router Links a local network to a remote network. For example, your company's network
probably uses a router to connect to the Internet. Can be used to connect a LAN to a
LAN, a WAN to a WAN, or a LAN to the Internet.
RP Rendezvous Point
RPR See Resilient Packet Ring
RS232 In the asynchronous transfer mode and there is no hand-shaking signal. It can
communicate with RS232 and RS422 of other stations in point-to-point mode and the
transmission is transparent. Its highest speed is 19.2kbit/s.
RS422 The specification that defines the electrical characteristics of balanced voltage digital
interface circuits. The interface can change to RS232 via the hardware jumper and others
are the same as RS232.
RSTP See Rapid Spanning Tree Protocol
RTN Radio Transmission Node
RX Receiver
A Glossary
Troubleshooting
Issue 04 (2010-11-30)
A.19 S
S1 byte In an SDH network, each network element traces step by step to the same clock reference
source through a specific clock synchronization path, thus realizing the synchronization
of the whole network. If a clock reference source traced by the NE is lost, the clock of
this NE will trace another clock reference source of lower level. To implement protection
switching of clocks in the whole network, the NE must learn about the clock quality
information of the clock reference source it traces. Therefore, ITU-T defines S1 byte to
transmit the network synchronization status information. It uses the lower four bits of
the multiplex section overhead S1 byte to indicate 16 types of synchronization quality
grades. The specific coding information is shown in the following table. Auto protection
switching of clocks in the synchronous network can be implemented by using S1 byte
and following the certain switching protocol.
SAN Storage Area Network
SC Square Connector
SCR Sustainable Cell Rate
SD See space diversity
SD See Signal Degrade
SDH See Synchronous Digital Hierarchy
SDP Serious Disturbance Period
SEC SDH Equipment Clock
Section The portion of a SONET transmission facility, including terminating points, between (i)
a terminal network element and a regenerator or (ii) two regenerators. A terminating
point is the point after signal regeneration at which performance monitoring is (or may
be) done.
Self-healing Self-healing is the establishment of a replacement connection by network without the
NMC function. When a connection failure occurs, the replacement connection is found
by the network elements and rerouted depending on network resources available at that
time.
Serial port extended
ECC
The ECC channel realized by means of serial port.
server A network device that provides services to network users by managing shared resources,
often used in the context of a client-server architecture for a LAN.
Service protection A measure that ensures that the services can be received at the receive end.
SES Severely Errored Second
SETS Synchronous Equipment Timing Source
settings Parameters of a system or operation that can be selected by the user.
SF See Signal Fail
SF See SF
SF Signal Fail. A signal that indicates the associated data has failed in the sense that a near-
end defect condition (non-degrade defect) is active.
A-25
SFP See Small Form-Factor Pluggable
SHDSL Single-line High speed Digital Subscriber Line
Side Mode Suppression
Ratio
The Side Mode Suppression Ratio (SMSR) is the ratio of the largest peak of the total
source spectrum to the second largest peak.
signal cable Common signal cables cover the E1cable, network cable, and other non-subscriber signal
cable.
Signal Degrade SD is a signal indicating the associated data has degraded in the sense that a degraded
defect (e.g., dDEG) condition is active.
Signal Fail SF is a signal indicating the associated data has failed in the sense that a near-end defect
condition (not being the degraded defect) is active.
Simple Network
Management Protocol
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.
slide rail Angle-bars on which shelves and chassis may slide and be supported within a cabinet or
shelf.
Small Form-Factor
Pluggable
A specification for a new generation of optical modular transceivers.
SMSR See Side Mode Suppression Ratio
SNC SubNetwork Connection
SNCMP See Subnetwork connection multipath protection
SNCP See SubNetwork Connection Protection
SNCP node Set the SNC node on the protection sub-network to support sub-network connection
protection that spans protection sub-networks. The SNCP node of the ring sub-network
can support electric circuit dually feed and selectively receive a timeslot out of the ring,
thus implementing sub-network connection protection. The SNCP node is generally set
on the node on the line board with the path protection type of the dual fed and selectively
received.
SNCTP See Subnetwork Connection Tunnel Protection
SNMP See Simple Network Management Protocol
SNR Signal Noise Ratio
space diversity A protection mode. The main and standby radios are set up in Hot Standby mode, but
are connected to their own antennas. Both antennas, separated by a specific distance, are
receiving the signal transmitted from the online radio at the other end of the lin
Spanning Tree Protocol Spanning Tree Protocol. STP is a protocol that is used in the LAN to remove the loop.
STP applies to the redundant network to block some undesirable redundant paths through
certain algorithms and prune a loop network into a loop-free tree network.
SPI Synchronous Physical Interface
SSM See Synchronization Status Message
A Glossary
Troubleshooting
Issue 04 (2010-11-30)
SSU Synchronization Supply Unit
Statistical multiplexing A multiplexing technique whereby information from multiple logical channels can be
transmitted across a single physical channel. It dynamically allocates bandwidth only to
active input channels, to make better use of available bandwidth and allow more devices
to be connected than with other multiplexing techniques. Compare with TDM.
STM-4 SDH Transport Module -4
STP See Spanning Tree Protocol
Sub-network number It is used to differentiate the different network sections in the sub-network conference.
Actually it is the first several digits (one or two) of the user phone number. An orderwire
phone number is composed of the sub-network number and the user number.
subnet A logical entity in the transmission network, which comprises a group of network
management objects. A subnet can contain NEs and other subnets.
subnet mask The technique used by the IP protocol to determine which network segment packets are
destined for. The subnet mask is a binary pattern that is stored in the client machine,
server or router and is matched with the IP address.
Subnetwork connection
multipath protection
The only difference is that SNCP is of 1+1 protection and SNCMP is of N+1 protection.
That is, several backup channels protect one active channel in SNCMP.
SubNetwork
Connection Protection
A working subnetwork connection is replaced by a protection subnetwork connection if
the working subnetwork connection fails, or if its performance falls below a required
level.
Subnetwork
Connection Tunnel
Protection
SNCTP provides a VC-4 level channel protection. When the working channel is faulty,
the services of the entire VC-4 path can be switched over to the protection channel.
Support A part used to support and fix a cabinet on the antistatic floor
Suppression state An attribute set to determine whether an NE monitors the alarm. Under suppression
status, NE will not monitor the corresponding alarm conditions and the alarm will not
occur even when the alarm conditions are met.
SVC Switching Virtual Connection
Switching priority There may be the case that several protected boards need to be switched; thus the tributary
board switching priority should be set. If the switching priority of each board is set the
same, the tributary board that fails later cannot be switched. The board with higher
priority can preempt the switching of that with lower priority.
Switching restoration
time
It refers to the period of time between the start of detecting and the moment when the
line is switched back to the original status after protection switching occurs in the MSP
sub-network.
Synchronization Status
Message
A message that is used to transmit the quality levels of timing signals on the synchronous
timing link. Through this message, the node clocks of the SDH network and the
synchronization network can aquire upper stream clock information, and the two perform
operations on the corresponding clocks, such as tracing, switchover, or converting hold),
and then forward the synchronization information of this node to down stream.
A-27
Synchronous Digital
Hierarchy
SDH is a transmission scheme that follows ITU-T G.707, G.708, and G.709. It 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. It interleaves the bytes of low-speed signals to multiplex the signals to high-speed
counterparts, and the line coding of scrambling is only used only for signals. SDH is
suitable for the fiber communication system with high speed and a large capacity since
it uses synchronous multiplexing and flexible mapping structure.
Synchronous source A clock providing timing services to connected network elements. This would include
clocks conforming to Recommendations G.811, G.812 and G.813.
A.20 T
T2000 The T2000 is a subnet management system (SNMS). In the telecommunication
management network architecture, the T2000 is located between the NE level and
network level, which can support all NE level functions and part of the network level
management functions. See also NM.
T2000 LCT A lite version of T2000. It is an element level management system for the optical
transmission network. It can manage SDH, DWDM and Metro optical transmission
equipment. See also LCT.
Tandem Connection
Monitor
In the SDH transport hierarchy, the TCM is located between the AU/TU management
layer and HP/LP layer. It uses the N1/N2 byte of POH overhead to monitor the quality
of the transport channels on a transmission section (TCM section).
TCM See Tandem Connection Monitor
TCP/IP See Transmission Control Protocol/Internet Protocol
TCP/IP Transmission Control Protocol/Internet Protocol
TDM Time Division Multiplexing
tie wrap N/A
TIM Trace Identifier Mismatch
Time Slot Continuously repeating interval of time or a time period in which two devices are able
to interconnect.
Time Synchronization Also called the moment synchronization, time synchronization means that the
synchronization of the absolute time, which requires that the starting time of the signals
keeps consistent with the UTC time.
TM Terminal Multiplexer
TMN Telecommunications Management Network
ToS See Type of Service
TPS See Tributary Protection Switch
Trail management
function
A network level management function of the network management system. Through trail
management, you can configure end-to-end services, view graphic interface and visual
routes of a trail, query detailed information of a trail, filter, search and locate a trail
quickly, manage and maintain trails in a centralized manner, manage alarms and
performance data by trail, and print a trail report.
A Glossary
Troubleshooting
Issue 04 (2010-11-30)
Transceiver A transmitter and receiver housed together in a single unit and having some circuits in
common, often for portable or mobile use.
Transmission Control
Protocol/Internet
Protocol
Common name for the suite of protocols developed to support the construction of
worldwide internetworks.
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.
Tray A component that can be installed in the cabinet for holding chassis or other devices.
Tributary loopback A fault can be located for each service path by performing loopback to each path of the
tributary board. There are three kinds of loopback modes. 1. No loopback: It is the normal
status. No loopback is needed when the equipment runs efficiently; 2. Outloop: When
arriving at the line board after passing the input port in the local NE, the input signal is
directly looped back to the service output end; 3. Inloop: The input signal is returned
along the original trail from the tributary board of the target NE.
Tributary Protection
Switch
Tributary protection switching, a function provided by the equipment, is intended to
protect N tributary processing boards through a standby tributary processing board.
Tributary unit An information structure which provides adaptation between the lower order path layer
and the higher order path layer. It consists of an information payload (the lower order
VC) and a TU pointer which indicates the offset of the payload frame start relative to
the higher order VC frame start.
Tributary Unit Group One or more Tributary Units, occupying fixed, defined positions in a higher order VC-
n payload is termed a Tributary Unit Group (TUG). TUGs are defined in such a way that
mixed capacity payloads made up of different size Tributary Units can be constructed
to increase flexibility of the transport network
TTL Time To Live
TU Tributary Unit
TUG See Tributary Unit Group
Type of Service A field in an IP packet (IP datagram) that is used for quality of service (QoS). The TOS
field is 8 bits, broken into five sub-fields.
A.21 U
UART Universal Asynchronous Receiver/Transmitter
UAS Unavailable Second
UBR Unspecified Bit Rate
underfloor cabling The cables connected cabinets and other devices are routed underfloor.
UNI See User Network Interface
Unprotected Pertaining to the transmission of the services that are not protected, the services cannot
be switched to the protection channel if the working channel is faulty or the service is
interrupted, because protection mechanism is not configured.
Unprotected sub-
network
It refers to a sub-network without any protection mechanism. The purpose of such
configuration is to provide the basic data of trail protection for the subsequent trail
management.
A-29
Upload An operation to report some or all configuration data of an NE to the T2000. The
configuration data then covers the configuration data stored at the T2000 side.
Upper threshold The critical value that can induce unexpected events if exceeded.
UPS Uninterruptible Power Supply
Upward cabling Cables or fibers connect the rack with other equipment from the top of the cabinet.
User A client user of the NMS. The user name and password uniquely identifies the operation
rights of a user in the NMS.
User Network Interface The interface between a network and the user of network services.
UTC Universal Time Coordinated
A.22 V
VB Virtual Bridge
VBR Variable Bit Rate
VC See Virtual concatenation
VCG Virtual Concatenation Group
VCI Virtual Channel Identifier
Virtual concatenation N/A
Virtual Container A Virtual Container is the information structure used to support path layer connections
in the SDH. It consists of information payload and path Overhead (POH) information
fields organized in a block frame structure which repeats every 125 or 500 s.
Virtual local area
network
A subset of the active topology of a Bridged Local Area Network. Associated with each
VLAN is a VLAN Identifier (VID).
Virtual Private
Network
The extension of a private network that encompasses encapsulated, encrypted, and
authenticated links across shared or public networks. VPN connections can provide
remote access and routed connections to private networks over the Internet.
VLAN See Virtual local area network
VP Virtual Path
VPI Virtual Path Identifier
VPN See Virtual Private Network
A.23 W
Wait to Restore Time A period of time that must elapse before a - from a fault recovered - trail/connection can
be used again to transport the normal traffic signal and/or to select the normal traffic
signal from.
Wait-to-Restore A period of time that must elapse from a recovered fault before an LSP/span can be used
again to transport the normal traffic and/or to select the normal traffic from.
WAN Wide Area Network
A Glossary
Troubleshooting
Issue 04 (2010-11-30)
Wander The long-term variations of the significant instants of a digital signal from their ideal
position in time (where long-term implies that these variations are of frequency less than
10Hz).
washer A washer is a thin flat ring of metal or rubber which is placed over a bolt before the nut
is screwed on.
Wavelength Division
Multiplexing
Wavelength Division Multiplexing. WDM technology utilizes the characteristics of
broad bandwidth and low attenuation of single mode optical fibre, uses multiple
wavelengths as carriers, and allows multiple channels to transmit simultaneously in a
single fibre.
Wavelength protection
group
The wavelength protection group is important to describe the wavelength protection
structure. Its function is similar to that of the protection subnet in the SDH NE. The
wavelength path protection can only work with the correct configuration of the
wavelength protection group.
WDM See Wavelength Division Multiplexing
WFQ Weighted Fair Queuing
Winding pipe A tool for fiber routing, which acts as the corrugated pipe.
Working path The channels allocated to transport the normal traffic.
WRED Weighted Random Early Detection
WTR See Wait-to-Restore
WTR See Wait to Restore Time
A-31

OptiX OSN 3500 Troubleshooting (V100R008)

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

OptiX OSN 3500 Troubleshooting (V100R008)

Caricato da

Copyright:

Formati disponibili

00384241

OptiX OSN 3500 Intelligent Optical Transmission

Hardware loopback at the local optical interfaces

Potrebbero piacerti anche