Maintenance Manual

1 Maintenance Precautions and Basic Operations 1-1 ......................................
1.1 Maintenance Precautions 1-1 .......................................................................

1.1.1 Laser 1-1 ..............................................................................................
1.1.2 Electrical Safety 1-3 .............................................................................
1.1.3 Board Mechanical Safety 1-4 ...............................................................
1.1.4 Network Management System Maintenance 1-5 .................................
1.1.5 Modifying Traffic Configuration 1-5 ......................................................
1.2 Basic Operations 1-6 ....................................................................................
1.2.1 Swapping Fiber Jumper 1-6 .................................................................
1.2.2 Swapping Board 1-6 .............................................................................
1.2.3 Resetting SCC Unit 1-9 ........................................................................
1.2.4 Testing Trunk Cable with Multimeter 1-9 .............................................
1.2.5 Loopback Operation 1-9 .......................................................................
1.2.6 Bit Error Test 1-14 ..................................................................................
1.2.7 Cable Tag Description 1-15 ...................................................................
1.2.8 Receiving/transmitting Optical Power Test 1-18 ....................................
1.2.9 Preparation of the Ethernet Cable of NMS Computer 1-19 ....................
2 Routine Maintenance 2-1 ....................................................................................
2.1 Maintenance Overview 2-1 ...........................................................................
2.1.1 Maintenance Objective 2-1 ..................................................................
2.1.2 Classification of Maintenance 2-1 ........................................................
2.1.3 Basic Principles for Routine Maintenance 2-2 .....................................
2.1.4 Maintenance Capability of OptiX Metro 500 Equipment 2-2 ................
2.2 Routine Maintenance Items of Equipment 2-4 .............................................
2.2.1 Observing Indicators 2-5 ......................................................................
2.2.2 Checking Equipment Temperature 2-5 ................................................
2.2.3 Service Check -- Bit Error Test 2-6 ......................................................
2.3 Routine Maintenance Items of NMS 2-7 .......................................................
3 Principle for Generation of Alarm and Performance Event 3-1 ......................
3.1 Overview of SDH Alarm and Performance Event 3-1 ...................................
3.1.1 Terminology Agreement 3-3 .................................................................
3.1.2 Two Common Alarms 3-3 ....................................................................
3.2 Generation and Detection of Alarm and Performance Event in
Signal Flow of Higher Order Part 3-4 .................................................................
3.2.1 Downlink Signal Flow 3-5 .....................................................................
3.2.2 Uplink Signal Flow 3-8 .........................................................................
3.3 Generation of Alarm and Performance in Signal Flow of Lower
Order Part 3-10 .....................................................................................................
3.3.1 Downlink Signal Flow 3-11 .....................................................................
3.3.2 Uplink Signal Flow 3-12 .........................................................................
3.4 SDH Alarm Suppression 3-14 ........................................................................
3.5 Generation and Detection of SDH Performance Event 3-16 ..........................
3.5.1 Bit Error 3-16 ..........................................................................................
3.5.2 Pointer Justification 3-19 ........................................................................
3.6 Application of Locating a Fault According to Signal Flow 3-22 .......................
3.6.1 Bit Error 3-22 ..........................................................................................
3.6.2 Alarm 3-23 ..............................................................................................
3.6.3 Summary 3-24 ........................................................................................
3.6.4 Method of Analyzing Alarms and Faults 3-24 ........................................
4 Alarm and Performance Event Handling 4-1 ....................................................
Alarm Handing 4-1 ..............................................................................................
AU_AIS 4-2 .........................................................................................................
AU_LOP 4-3 .......................................................................................................
B1_EXC 4-4 ........................................................................................................
B1_SD 4-5 ..........................................................................................................
B2_EXC 4-6 ........................................................................................................
B2_SD 4-7 ..........................................................................................................
B3_EXC 4-8 ........................................................................................................
B3_SD 4-9 ..........................................................................................................
BIP_EXC 4-10 ......................................................................................................
BIP_SD 4-11 .........................................................................................................
BUS_LOC 4-12 .....................................................................................................
DOWN_E1_AIS 4-13 ............................................................................................
E1_LOS 4-14 ........................................................................................................
FAN_FAIL 4-15 .....................................................................................................
HP_LOM 4-16 .......................................................................................................
HP_RDI 4-17 ........................................................................................................
HP_REI 4-18 ........................................................................................................
HP_SLM 4-19 .......................................................................................................
HP_TIM 4-20 ........................................................................................................
HP_UNEQ 4-21 ....................................................................................................
J0_MM 4-22 ..........................................................................................................
LOOP_ALM 4-23 ..................................................................................................
LP_RDI 4-24 .........................................................................................................
LP_REI 4-25 .........................................................................................................
LP_RFI 4-26 .........................................................................................................
LP_R_FIFO 4-27 ..................................................................................................
LP_SIZE_ERR 4-28 .............................................................................................
LP_SLM 4-29 ........................................................................................................
LP_T_FIFO 4-30 ...................................................................................................
LP_TIM 4-31 .........................................................................................................
LP_UNEQ 4-32 .....................................................................................................
LTI 4-33 ................................................................................................................
MS_AIS 4-34 ........................................................................................................
MS_RDI 4-35 ........................................................................................................
MS_REI 4-36 ........................................................................................................
NESTATE_INSTALL 4-37 ....................................................................................
POWER_FAIL 4-38 ..............................................................................................
PS 4-39 .................................................................................................................
PWR_MAJ_ALM 4-40 ..........................................................................................
R_LOF 4-41 ..........................................................................................................
R_LOS 4-42 ..........................................................................................................
R_OOF 4-43 .........................................................................................................
RP_LOC 4-44 .......................................................................................................
SYN_BAD 4-45 .....................................................................................................
SYNC_C_LOS 4-46 ..............................................................................................
T_ALOS 4-47 ........................................................................................................
T_LOC 4-48 ..........................................................................................................
T_LOS 4-49 ..........................................................................................................
T_LOTC 4-50 ........................................................................................................
TU_AIS 4-51 .........................................................................................................
TU_LOP 4-52 .......................................................................................................
W_R_FAILURE 4-53 ............................................................................................
WRG_BD_TYPE 4-54 ..........................................................................................
Performance Events of SDH Service 4-55 ...........................................................
AUPJCHIGH 4-58 .................................................................................................
AUPJCLOW 4-59 .................................................................................................
TUNPJC 4-60 .......................................................................................................
TUPPJC 4-61 .......................................................................................................
HPBBE 4-62 .........................................................................................................
HPCSES 4-63 .......................................................................................................
HPES 4-64 ............................................................................................................
HPFEBBE 4-65 .....................................................................................................
HPFEES 4-66 .......................................................................................................
HPFESES 4-67 .....................................................................................................
HPSES 4-68 .........................................................................................................
HPUAS 4-69 .........................................................................................................
LPBBE 4-70 ..........................................................................................................
LPCSES 4-71 .......................................................................................................
LPES 4-72 ............................................................................................................
LPFEBBE 4-73 .....................................................................................................
LPFECSES 4-74 ...................................................................................................
LPFEES 4-75 ........................................................................................................
LPFESES 4-76 .....................................................................................................
LPSES 4-77 ..........................................................................................................
LPUAS 4-78 ..........................................................................................................
MSBBE 4-79 .........................................................................................................
MSCSES 4-80 ......................................................................................................
MSES 4-81 ...........................................................................................................
MSFEBBE 4-82 ....................................................................................................
MSFECSES 4-83 ..................................................................................................
MSFEES 4-84 .......................................................................................................
MSFESES 4-85 ....................................................................................................
MSSES 4-86 .........................................................................................................
MSUAS 4-87 .........................................................................................................
RSBBE 4-88 .........................................................................................................
RSCSES 4-89 .......................................................................................................
RSES 4-90 ............................................................................................................
RSOFS 4-91 .........................................................................................................
RSOOF 4-92 .........................................................................................................
RSSES 4-93 .........................................................................................................
RSUAS 4-94 .........................................................................................................
5 Basic Thoughts and Methods for Fault Locating 5-1 ......................................
5.1 Requirements for Maintenance Staff 5-1 ......................................................
5.1.1 Professional Skills 5-1 ..........................................................................
5.1.2 Aware of Network Layout 5-3 ...............................................................
5.1.3 Collecting and Storing On-site Data 5-3 ...............................................
5.2 Basic Principles of Fault Locating 5-4 ..........................................................
5.2.1 External First, then Transmission 5-4 ..................................................
5.2.2 Network First, then NE 5-4 ...................................................................
5.2.3 High-speed Section First, then Low-speed One 5-4 ............................
5.2.4 Higher Order Alarms First, then Lower Order Alarms 5-4 ....................
5.3 Common Methods of Fault Locating 5-5 ......................................................
5.3.1 Alarm and Performance Analysis 5-6 ...................................................
5.3.2 Loopback 5-9 .......................................................................................
5.3.3 Replacement 5-15 ..................................................................................
5.3.4 Configuration Data Analysis 5-16 ...........................................................
5.3.5 Configuration Modification 5-17 .............................................................
5.3.6 Meter Test 5-18 ......................................................................................
5.3.7 Experience 5-18 .....................................................................................
5.3.8 Comparison of Fault Locating Methods 5-19 .........................................
5.4 Some Classified Fauts & their Troubleshooting 5-20 .....................................
5.4.1 External Faults Handling 5-20 ................................................................
5.4.2 Localizing Fault to a Single Station 5-22 ................................................
5.4.3 Localizing Fault to the Boards 5-23 ........................................................
5.5 Conact Huawei for Assistance 5-24 ...............................................................
5.6 Obtaining the Latest Technical Documentation 5-25 ......................................
A Abbreviations A-1 ...............................................................................................

HUAWEI

OptiX Metro 500 Ultra Compact
STM-1 Multi-Service Transmission Platform
Maintenance Manual
V100R001

OptiX Metro 500 Ultra Compact STM-1
Multi-Service Transmission Platform
Maintenance Manual

Manual Version T2-040386-20030425-C-1.10
Product Version V100R001
BOM 31030386

Huawei Technologies Co., Ltd. provides customers with comprehensive technical support
and service. Please feel free to contact our local office, customer care center or company
headquarters.

Huawei Technologies Co., Ltd.
Address: Administration Building, Huawei Technologies Co., Ltd.,
Bantian, Longgang District, Shenzhen, P. R. China
Postal Code: 518129
Website: http://www.huawei.com
Email: support@huawei.com

Copyright 2003 Huawei Technologies Co., Ltd.

All Rights Reserved
No part of this manual may be reproduced or transmitted in any form or by any
means without prior written consent of Huawei Technologies Co., Ltd.
Trademarks
, HUAWEI, C&C08, EAST8000, HONET, , ViewPoint, INtess, ETS, DMC,
TELLIN, InfoLink, Netkey, Quidway, SYNLOCK, Radium, M900/M1800,
TELESIGHT, Quidview, Musa, Airbridge, Tellwin, Inmedia, VRP, DOPRA, iTELLIN,
HUAWEI OptiX, C&C08 iNET, NETENGINE, OptiX, SoftX, iSite, U-SYS, iMUSE,
OpenEye, Lansway, SmartAX are trademarks of Huawei Technologies Co., Ltd.
All other trademarks mentioned in this manual are the property of their respective
holders.

Notice
The information in this manual is subject to change without notice. Every effort has
been made in the preparation of this manual to ensure accuracy of the contents, but
all statements, information, and recommendations in this manual do not constitute
the warranty of any kind, express or implied.

OptiX Metro 500 MM

1 About This Manual

Release Notes
This document is for OptiX Metro 500 Ultra Compact STM-1 Multi-service Optical
Transmission Platform, Version V100R001.
Related Documentation
The documentation portfolio is divided into:
Documentation for the optical network products
Documentation for the network management (NM) systems
The documentation package for an optical network product is shipped with the
product, and the documentation package for an NM system is shipped with the NM
system. The table below lists the documentation for the products.

About This Manual OptiX Metro 500 MM

Documentation shipped with the product
Document Usage
OptiX Metro 500 Ultra Compact STM-1 Multi-service
Optical Transmission Platform Technical Manual
Introduces the functionality, structure, performance,
specifications, and theory of the product.
Optical Transmission Platform Hardware Description
Manual
Introduces the hardware of the product, including
cabinet, subrack, power, fan, board, and a variety of
interfaces.
Optical Transmission Platform Installation Manual
Guides the on-site installation of the product and
provides the information of the structural parts.
Optical Transmission Platform Maintenance Manual
Guides the analysis and troubleshooting of common
faults.

Documentation shipped with the NM system
Document Volume Usage
OptiX iManager T2000 Integration Network
Management System for Transmission
Network(Sub-Network Level) Technical
Manual

Introduces the position, software and
hardware structure, functionality features,
networking mode and performance
specifications of the T2000, appended with
standards that the T2000 complies with,
abbreviations, tables of functions and alarm
& performance.
Configuration OptiX iManager T2000 Integration Network
Network(Sub-Network Level) Operation
Manual
Management &
Maintenance
Introduces the operation tasks of T2000,
including provisioning, maintenance, and
task management.
Network(Sub-Network Level) Installation
Manual

Introduces the installation procedures of the
T2000 under the UNIX and Windows 2000
platform, and the installation procedures of
T2000-LCT. The installation of the Solaris 8
operating environment is described as well.
Network(Sub-Network Level) Electronic
Documentation (CD)

Contains all the above manuals in CD
format, readable with Acrobat Reader.


Organization
The document has the following organization:
Chapter Description
Chapter 1 Maintenance
Precautions and Basic
Operations
Describes maintenance precautions and basic
operations which maintenance personnel should
master for the OptiX Metro 500 maintenance.
Chapter 2 Routine
Maintenance
Describes maintenance objective and methods in
routine maintenance of the OptiX Metro 500.
Chapter 3 Principle for
Generation of Alarm and
Performance Event
Details the generation principles of various alarms and
performance events and their relations. This chapter is
the basis for you to apply alarm and performance
analysis in troubleshooting.
Chapter 4 Alarm and
Performance Event Handling
Lists common alarms. You can find common alarms,
causes, and treatments in this chapter.
Chapter 5 Basic Thoughts and
Methods for Fault Locating
Describes the operation of troubleshooting and the
common methods used in respective procedures.
Meanwhile, it emphasizes the thought for the
troubleshooting locating the fault to a single station.
Appendix A Abbreviations Lists the full names of all the abbreviations in this
manual

Intended Audience
This document is for:
Network administrator
Maintenance engineer
Provisioning engineer


Conventions
The following conventions are used throughout this publication.
Symbol Description

Means reader be careful. In this situation, you might do something that
could result in equipment damage or loss of data.

Means reader be careful. The equipment is static-sensitive.

Means reader be careful. In this situation, the high voltage could result in
harm to yourself or others.

Means reader be careful. In this situation, the strong laser beam could
result in harm to yourself or others.

Means reader take note. Notes contain helpful suggestions or useful
background information.

Release Upgrade Description
Release Release upgrade description
T2-040386-20030425-C-1.10 This document is the first release.

OptiX Metro 500 MM

i

Contents
1 Maintenance Precautions and Basic Operations
1.1 Maintenance Precautions 1-1
1.1.1 Laser 1-1
1.1.2 Electrical Safety 1-3
1.1.3 Board Mechanical Safety 1-4
1.1.4 Network Management System Maintenance 1-5
1.1.5 Modifying Traffic Configuration 1-5
1.2 Basic Operations 1-6
1.2.1 Swapping Fiber Jumper 1-6
1.2.2 Swapping Board 1-6
1.2.3 Resetting SCC Unit 1-9
1.2.4 Testing Trunk Cable with Multimeter 1-9
1.2.5 Loopback Operation 1-9
1.2.6 Bit Error Test 1-14
1.2.7 Cable Tag Description 1-15
1.2.8 Receiving/transmitting Optical Power Test 1-18
1.2.9 Preparation of the Ethernet Cable of NMS
Computer 1-19

2 Routine Maintenance
2.1 Maintenance Overview 2-1
2.1.1 Maintenance Objective 2-1
2.1.2 Classification of Maintenance 2-1
2.1.3 Basic Principles for Routine Maintenance 2-2
2.1.4 Maintenance Capability of OptiX Metro 500
Equipment 2-2
2.2 Routine Maintenance Items of Equipment 2-4
2.2.1 Observing Indicators 2-5
2.2.2 Checking Equipment Temperature 2-5
2.2.3 Service Check -- Bit Error Test 2-6

OptiX Metro 500 MM

ii

Contents
2.3 Routine Maintenance Items of NMS 2-7

3 Principle for Generation of Alarm and Performance Event
3.1 Overview of SDH Alarm and Performance Event 3-1
3.1.1 Terminology Agreement 3-3
3.1.2 Two Common Alarms 3-3
3.2 Generation and Detection of Alarm and Performance
Event in Signal Flow of Higher Order Part 3-4
3.2.1 Downlink Signal Flow 3-5
3.2.2 Uplink Signal Flow 3-8
3.3 Generation of Alarm and Performance in Signal Flow of
Lower Order Part 3-10
3.3.1 Downlink Signal Flow 3-11
3.3.2 Uplink Signal Flow 3-12
3.4 SDH Alarm Suppression 3-14
3.5 Generation and Detection of SDH Performance Event 3-16
3.5.1 Bit Error 3-16
3.5.2 Pointer Justification 3-19
3.6 Application of Locating a Fault According to Signal Flow 3-22
3.6.1 Bit Error 3-22
3.6.2 Alarm 3-23
3.6.3 Summary 3-24
3.6.4 Method of Analyzing Alarms and Faults 3-24

4 Alarm and Performance Event Handling
Alarm Handing 4-1
AU_AIS 4-2
AU_LOP 4-3
B1_EXC 4-4
B1_SD 4-5

OptiX Metro 500 MM

iii

Contents
B2_EXC 4-6
B2_SD 4-7
B3_EXC 4-8
B3_SD 4-9
BIP_EXC 4-10
BIP_SD 4-11
BUS_LOC 4-12
DOWN_E1_AIS 4-13
E1_LOS 4-14
FAN_FAIL 4-15
HP_LOM 4-16
HP_RDI 4-17
HP_REI 4-18
HP_SLM 4-19
HP_TIM 4-20
HP_UNEQ 4-21
J0_MM 4-22
LOOP_ALM 4-23
LP_RDI 4-24
LP_REI 4-25
LP_RFI 4-26
LP_R_FIFO 4-27
LP_SIZE_ERR 4-28
LP_SLM 4-29
LP_T_FIFO 4-30
LP_TIM 4-31
LP_UNEQ 4-32
LTI 4-33
MS_AIS 4-34
MS_RDI 4-35
MS_REI 4-36
NESTATE_INSTALL 4-37
POWER_FAIL 4-38

OptiX Metro 500 MM

iv

Contents
PS 4-39
PWR_MAJ_ALM 4-40
R_LOF 4-41
R_LOS 4-42
R_OOF 4-43
RP_LOC 4-44
SYN_BAD 4-45
SYNC_C_LOS 4-46
T_ALOS 4-47
T_LOC 4-48
T_LOS 4-49
T_LOTC 4-50
TU_AIS 4-51
TU_LOP 4-52
W_R_FAILURE 4-53
WRG_BD_TYPE 4-54
Performance Events of SDH Service 4-55
AUPJCHIGH 4-57
AUPJCLOW 4-58
TUNPJC 4-59
TUPPJC 4-60
HPBBE 4-61
HPCSES 4-62
HPES 4-63
HPFEBBE 4-64
HPFEES 4-65
HPFESES 4-66
HPSES 4-67
HPUAS 4-68
LPBBE 4-69
LPCSES 4-70
LPES 4-71
LPFEBBE 4-72

OptiX Metro 500 MM

v

Contents
LPFECSES 4-73
LPFEES 4-74
LPFESES 4-75
LPSES 4-76
LPUAS 4-77
MSBBE 4-78
MSCSES 4-79
MSES 4-80
MSFEBBE 4-81
MSFECSES 4-82
MSFEES 4-83
MSFESES 4-84
MSSES 4-85
MSUAS 4-86
RSBBE 4-87
RSCSES 4-88
RSES 4-89
RSOFS 4-90
RSOOF 4-91
RSSES 4-92
RSUAS 4-93

5 Basic Thoughts and Methods for Fault Locating
5.1 Requirements for Maintenance Staff 5-1
5.1.1 Professional Skills 5-1
5.1.2 Aware of Network Layout 5-3
5.1.3 Collecting and Storing On-site Data 5-3
5.2 Basic Principles of Fault Locating 5-4
5.2.1 External First, then Transmission 5-4
5.2.2 Network First, then NE 5-4
5.2.3 High-speed Section First, then Low-speed One 5-4

OptiX Metro 500 MM

vi

Contents
5.2.4 Higher Order Alarms First, then Lower Order
Alarms 5-4
5.3 Common Methods of Fault Locating 5-5
5.3.1 Alarm and Performance Analysis 5-6
5.3.2 Loopback 5-9
5.3.3 Replacement 5-15
5.3.4 Configuration Data Analysis 5-16
5.3.5 Configuration Modification 5-17
5.3.6 Meter Test 5-18
5.3.7 Experience 5-18
5.3.8 Comparison of Fault Locating Methods 5-19
5.4 Some Classified Fauts & their Troubleshooting 5-20
5.4.1 External Faults Handling 5-20
5.4.2 Localizing Fault to a Single Station 5-22
5.4.3 Localizing Fault to the Boards 5-23
5.5 Conact Huawei for Assistance 5-24
5.6 Obtaining the Latest Technical Documentation 5-25

A Abbreviations
A

OptiX Metro 500 MM

1-1

1 Maintenance Precautions and
Basic Operations

1.1 Maintenance Precautions
To ensure the safety of the maintenance personnel and that of the equipment, some
basic rules must be followed before equipment maintenance.
1.1.1 Laser
Warning:
The laser emitted by the optical interface board is invisible infrared ray, which may
cause permanent damage to human eyes.

When operating the optical connectors of the fiber jumper and optical interface board,
please wear a pair of protective glasses that can filter infrared ray to avoid the
damage to your eyes. It is forbidden to directly stare into the laser aperture and fiber
connectors on the optical interface boards without protective glasses.
The protective glasses should be prepared by the user instead of the transmission
equipment supplier.

Maintenance Precautions and Basic Operations OptiX Metro 500 MM

1-2

1. Handling of optical interface of optical interface board and fiber jumper
connector
The unused optical interface and unused optical connector should be covered with
optical caps. For the optical interface in use, when it is necessary to pull off the fiber
jumper from it, please cover the optical interface and the fiber connector with optical
caps.
In this way, it will
Prevent the invisible laser ray from irradiating human eyes.
Protect the optical interfaces or fiber jumpers from dust, and so as not to
enhance the loss.
2. Cleaning of the optical interface and fiber connector
The fiber connectors and the optical fiber interfaces must be cleaned with special
cleaning tools and materials. These tools and material are available from the
manufacturers of optical fiber/optical cables. Always use special cleaning tools and
materials to clean the high-power laser interfaces. For low-power laser interfaces,
pure anhydrous alcohol can be used if special cleaning tools and materials are not
available.
Before cleaning the optical interface, please first pull off optical fiber on the board
and then pull out the optical interface board. It is recommended that this work should
be done or supervised by the engineers of the customer service center of Technical
Support Department of Huawei to avoid damage to the optical interface board due to
misoperation.
Warning:
It is strictly forbidden to use any cleaning tools and materials that cannot be proved
suitable for cleaning the optical fiber connectors and the optical fiber interfaces!
Using unqualified tools and materials will damage optical fiber connectors and
optical interfaces.

3. Precautions for the loopback of the optical interface
During the hardware loopback test of the optical interface with fiber jumpers, an
attenuator must be used to avoid the extra strong receiving optical power from
saturating or even damaging the optical receiving module.


1-3

1.1.2 Electrical Safety
1. ESD precautions
Before the maintenance on the equipment, ESD measures must be taken as the
stipulations in this section, to avoid damaging the equipment.
In the cases of body movements, clothes friction, the friction between the shoes and
ground, and plastics held in the hand, human body generates static electromagnetic
field and would keep it for a long time. Before touching the equipment, holding
boards, PCBs, IC chips and so on, you must wear the ESD wrist strap and ground
the other end of the ESD wrist strap properly, lest the static electricity of the human
body should damage the static-sensitive components. Refer to Figure 1-1.

Figure 1-1 Wearing an ESD wrist strap

Note:
The static electricity produced by the human body can damage the static-sensitive
components on the board, such as large scale integrated circuit.


1-4

2. Precautions for board electrical safety
The board should be kept in the ESD bag when it is not used. Wear an ESD
wrist and make sure the wrist is well grounded before taking the board.
Moisture-proof treatment of the board
Note:
As to the OptiX Metro 500, only SP2D board in extended slot can be plug-in.

Please pay attention to the impact of environmental temperature and humidity on the
storage of the backup boards. Desiccant should be placed inside the ESD protection
bag to absorb the moisture in the bag and keep the bag dry.
When the board encapsulated in the ESD protection bag is taken from a cool, dry
place to a hot, humid place, wait for at least 30 minutes before opening it. Otherwise,
the moisture will condense on the surface of the board, which may damage the
elements.
3. Precautions for power supply maintenance
Never install and remove the equipment power supply with the power on.
Never connect or disconnect the equipment power cable with power on.
At the moment when the power cable touches the conductor, electric sparks
or arcs will be produced, which can cause fire or injury to the personnel.
Before cable is connected, you must make sure whether cable and cable
label are in compliance with the practical installation.
1.1.3 Board Mechanical Safety
Avoid shocks during the transportation of boards, which may result in damage
to the boards.
When replacing a board, swap the board with care and strictly follow the
instructions.


1-5

1.1.4 Network Management System
Maintenance
Do not quit the network management system when its software is working
normally. Although quitting the network management system will not interrupt
the service on the network, it will disable the NMS to monitor the equipment
during the shutdown period and jeopardize the continuity of the equipment
monitoring.
Never run any software irrelevant to equipment maintenance on the computer.
Never play game on the NMS computer. Never copy file or software which
has not been anti-virus scanned to NMS computer. Remove viruses regularly
with the latest virus killer software, lest any computer virus infects and
damage the NMS.
1.1.5 Modifying Traffic Configuration
Don't use the NMS to groom the service configuration during the traffic peak.
Because once there is a fault, there will be great effect. Choose the hour of minimum
traffics, such as the nighttime, to perform service grooming.


1-6

1.2 Basic Operations
1.2.1 Swapping Fiber Jumper
The OptiX Metro 500 uses two types of interfaces: SC/PC and FC/PC, as shown in
Figure 1-2.

Figure 1-2 SC/PC fiber jumper

Please use special tool (such as fiber extractor) to pull off SC/PC fiber jumper. When
inserting the SC/PC fiber jumper, align the connector of the SC/PC fiber jumper with
the optical interface on the board, and push it until it clicks into place.
1.2.2 Swapping Board
1. Method of inserting the board
First know each part of the board, as shown in Figure 1-3:
Front panel
Printed Circuit
Board
Ejector lever
Captive screw
DB78

Figure 1-3 ach part of the board


1-7

Method of inserting the board is as the following:
(1) Wear an ESD wrist and ensure that the other end of the wrist is well
grounded.
(2) To insert the board, first push the board gently along the slide to the bottom
of the board position In the event, the board is under floating insertion.
(3) Make sure that the connector of the board aligns with the backplane socket
and the guide pin of the backplane aligns with the guide sleeve of the board.
Then push the board front panel with proper force until it is basically
inserted. If you feel some resistance, please do not insert the board forcedly,
instead, you should adjust the board position and then try again.
(4) When the board connector is completely matched with backplane socket
(connector and socket can be observed), press the upper and lower ejector
levers of the front panels inward till the board is inserted completely, then
tighten the captive screws.
Note:
1. Forcibly inserting the board in an improper position will do permanent damage to
the equipment.
2. Float inserting the board means that the board is already in the slot but the board
connector and motherboard socket are not connected yet; actually, the board is still
in not-inserted status.
3. Please remove the fiber (cable) from the front panel of the board before swapping
the board. It is forbidden to swap the board with the fiber (cable) on it.

See Figure 1-4.


1-8

SP2D

Figure 1-4 Inserting the board

2. Method of pulling out the board
The operation of pulling out the board is shown in Figure 1-5:
SP2D

Figure 1-5 Pulling out the board


1-9

1.2.3 Resetting SCC Unit
You can reset the SCC Unit through the NMS.
In addition, there is a reset button RST on the front panel of the ISU board. You can
reset the SCC Unit by pressing the RST button.
Neither hard reset nor soft reset of the SCC Unit will affect the service unless.
However, when the SCC Unit is in the reset state, the NMS communication will be
interrupted temporarily until the SCC unit enters the normal running state again.
Note:
The board reset is a dangerous operation, it shall not be done unless in special
conditions. If it is really necessary to reset a board, please ask the engineer of
Huawei for acknowledgement before you do it.

1.2.4 Testing Trunk Cable with Multimeter
During construction and maintenance, coaxial trunk cable should be tested
frequently to judge whether the cable has dry point, open solder point and short
circuit, and whether the connection position of trunk cable at the DDF is correct. This
is usually mentioned as wire-matching. Operations of the wire-matching are as
follow:
Short-circuit the signal core and shielding layer at one end of coaxial cable (with a
shorting stub or a pair of tweezers), and use a multi-meter to test the resistance
between the signal core and shielding layer at the other end. The resistance should
be 0. Then break off the short circuit and use the multi-meter to test at the other
end. The resistance should be infinite. These two tests show that the tested ends are
the two ends of the same cable, and this cable is normal. Otherwise, it shows there
is broken point in the cable, there might be dry joint, open solder joint and short
circuit at the cable connection point, or these two ends are not the two ends of the
same cable.
1.2.5 Loopback Operation
The meanings of inloop/outloop of SDH and PDH interfaces are described in the
following:
1. Loop back of SDH interface
(1) Hardware loop back of the SDH interface
From the viewpoint of signal flow direction, hardware loop back is generally inloop,


1-10

therefore, we call it as hardware self-loop as well. The hardware loopback of optical
interface means to connect the OUT and IN optical ports of optical interface board
with a fiber jumper, so as to accomplish signal loopback. There are two hardware
self-loop modes: board self-loop and cross self-loop.
The board self-loop is defined as connecting the IN to OUT optical ports on the
same optical interface board with a fiber jumper. The cross self-loop is defined as
connecting the OUT port of west optical interface board to the IN port of east optical
interface board, or the OUT port of east optical interface board and the IN port of
west optical interface board with a fiber jumper.
Note:
An attenuator should be added during hardware self-loop of the optical interface.

(2) Software loopback of SDH interface
The software loopback of SDH interface refers to the VC-4 loopback setting in the
NMS, which is subdivided into inloop and outloop as well.
(3) Application of VC-4 loopback
To locate such faults as service interruption and bit error, the simplest and most
effective method is the loopback section-by-section, i.e., locate the fault to a single
station or a section of the optical fiber via VC-4 loopback from near to far or from
far to near. The sequence of fault location using VC-4 loopback is shown in
Figure 1-6:


1-11

Station C
OptiX
Metro 500
2Mbit/s port
e
w
e
w
e
STM-1
STM-1
BER tester
1
2
3
4
5
6
Station B
Station A
OptiX
Metro 500
OptiX
Metro 500

Figure 1-6 Application of VC-4 loopback

Assume Station A is the central office in Figure 1-6, and now the 2Mbit/s service
between Stations A and C are interrupted. The steps of locating fault using VC-4
loopback are as follow:
(1) First, connect BER tester to the 2Mbit/s port where service is interrupted
and then start to test, as illustrated in Step in Figure 1-6.
(2) Find the VC-4 the 2M service is located. Through the NMS, perform inloop
to the VC-4 of the east optical board (e in the diagram) of Station A, as
illustrated in Step in Figure 1-6. If the BER tester indicates that the
service resumes, it can be judged that there is no fault with Station A. Then
go to next step.
(3) Through the NMS, cancel the inloop of the VC-4 of the east optical board of
Station A. Then perform outloop to the VC-4 of the west optical board (w in
the diagram) of Station B, as illustrated in Step in Figure 1-6. If the BER


1-12

tester indicates that the service is blocked after loopback, it indicates that
the fault is basically with the optical fiber between Stations A and B. If the
BER tester still indicates that the service is normal, please go to the next
step.
(4) Cancel the outloop of the VC-4 of the west optical board of Station B. Then,
continue to perform inloop to the VC-4 of the east optical interface board of
Station B, as illustrated in Step in Figure 1-6. If the service is blocked
after loopback, it indicates the fault is with Station B. If the service is still
normal after loopback, please go to the next step.
(5) Cancel the inloop of the VC4 of the east optical board at Station B, perform
outloop to the VC4 of the west optical board of Station C, as illustrated in
Step in Figure 1-6. If the service is blocked after loopback, it shows that
the fault is with the fiber between Stations B and C. If the service is normal,
the fault is with Station C.
(6) Cancel the outloop of the VC4 of the west optical board of Station C. Next,
perform inloop to the corresponding 2Mbit/s TU interface of Station C
instead of VC-4 loopback. Then, the fault can be judged either at Station C
or at the trunk cable or at the exchange. The inloop of TU interface is
illustrated in Step in Figure 1-6.
Review the steps of , , , , , and , the loopback idea from near end to
far end is very clear.
Note:
1) Since the VC-4 loopback is aimed at the whole VC-4, all services in the VC-4 will
be affected.
2) No matter whether the bit rate on the optical path is STM-1 or STM-4, if VC-4
loopback is performed on the first VC4 of the optical path, ECC communication may
be affected and then the downstream NEs cannot be logged on. Use the function
with care!
3) The VC-4 loopback must be cancelled after test! (Set to No loopback)

2. Loopback of PDH interface
(1) Hardware loopback of PDH interface
Hardware loopback of PDH interface is to connect the receive ports with the
transmitter ports by cables.


1-13

(2) Software loopback of PDH interface
The software loopback of PDH interface is to set inloop or outloop for PDH interface
via the NMS.
Whether a certain 2Mbit/s path in its entirety is normal can be tested through
loopback of PDH interfaces and outloop test in combination with BER tester.
For specific operation, please refer to the Operation Manual of the corresponding
NMS.
(3) Application of outloop and inloop
If any alarm occurs in some 2Mbit/s paths, or traffics of the switching system are
interrupted, the general troubleshooting methods are to perform outloop and inloop
on both ports of corresponding 2Mbit/s path. At the same time we should perform
loopback at the DDF to locate the fault, as illustrated in Figure 1-7.
OptiX Metro 500
OptiX Metro 500
A Office B Office
RX
RX TX
TX
Swithing
DDF
swithing
DDF
RX
TX
RX TX
RX TX
RX TX
RX TX
RX TX
1
2
4
3
outloop inloop

Figure 1-7 Outloop and inloop application of the PDH interface

In Figure 1-7, suppose that Office A is the central office and the exchange room
reports that there is a 2Mbit/s service interruption between Office A and Office B.
Then, the sequence of the PDH tributary interface loopback is as follows:
(1) First, at the DDF of Office A, perform loopback to the exchange side with a
self-loop cable and observe the trunk status of the exchange, as shown in
Step in Figure 1-7. If the trunk status of the exchange is abnormal, it
indicates the problem is between the exchange and the DDF. If the trunk
status of the exchange is normal, go to the next step.
(2) Cancel the self-loop cable from the DDF to the exchange. Then, through the
NMS, perform outloop to the corresponding 2Mbit/s interface of the OptiX
Metro 500 at Office A, and observe the trunk status of the exchange at
Office A or connect a BER tester to the DDF for test, as shown in Step in
Figure 1-7. If the trunk status of the exchange is abnormal, it indicates the


1-14

problem is with the tributary board of the OptiX Metro 500 at Office A or the
cable between the OptiX equipment and the DDF. If the trunk state is
normal, please go to the next step.
(3) Through the NMS, cancel the outloop to the corresponding 2Mbit/s interface
of the OptiX Metro 500 at Office A. Perform inloop on the corresponding
2Mbit/s path port of the OptiX Metro 500 at Office B. And observe the trunk
status of the exchange at Office A or the status of BER tester, as illustrated
in Step in Figure 1-7. If the trunk status of the exchange is still abnormal,
all of the tributary board, cross-connect board, line board in OptiX
equipments both at Office A and Office B may be faulty, as well as optical
fibers, because service passes through all these sections. If the trunk status
of the exchange is normal, please go to the next step.
(4) Cancel the inloop to the corresponding 2Mbit/s interface of the OptiX Metro
500 at Office B. Then, at the DDF of Office B, use a self-loop cable to
perform loopback towards Office A and observe the trunk status of the
exchange at Office A or the status of the BER tester. If the trunk status of
the exchange is still abnormal, it can be affirmed that the problem may exist
on the cable between OptiX equipment and the DDF or on the tributary unit
of OptiX equipment at Office B. If the trunk status of the exchange is normal,
the problem exists between the exchange and the DDF at Office B.
1.2.6 Bit Error Test
When performing bit error test with the BER tester, the service access point, such as
E1 and STM-1 interface, is generally taken as the test point. There are two test
modes available: on-line test or off-line test.
1. On-line test method
First, select a service channel in use (E1 or STM-1) and find the port on the DDF
corresponding to this channel. Then, connect one end of the test cable with the
on-line test connector of the port on the DDF and the other end with the on-line test
interface of the BER tester. In normal cases, there should be no bit error in 24 hours.
For the setting of the BER tester, please refer to its usage instructions. Note that the
meter is set to on-line test at the event.
2. Off-line test method
This is a commonly used bit error test method. First select a service channel (E1 or
STM-1), connect the TX and RX ports of BER tester with the RX and RTX PDH/SDH
interfaces of this service channel in this station respectively, then perform inloop to


1-15

the PDH/SDH interface of the opposite station (e.g., perform hardware self-loop at
the DDF), and test the bit error. For the BER tester usage, please refer to its usage
instructions. Under normal conditions there should be no bit error.
The block diagram of bit error test connection is shown in Figure 1-8:
OptiX Metro
500
OptiX Metro
500
BER tester
Tributary
inloop

Figure 1-8 Bit error test

Note:
The test meter should be grounded properly. It is suggested that other electric
appliances not be switched on/off in the test course.

1.2.7 Cable Tag Description
To ensure correct optical fiber connection and facilitate future maintenance, both
ends of the fiber jumper should be marked with tags. Depending on the connectivity
of the transmission equipment, the tags of fiber jumpers can be prepared in two
different ways. One kind of tags is used for inter-station connection of the
transmission equipment, where tags are pasted on fiber jumpers at the transmission
equipment side. The other kind of tags is used for intra-station connection of the
transmission equipment, where tags are pasted on both ends of fiber jumpers. It
should be noted that the tag content on both ends of the same fiber should be the
same.
In case of the inter-station connection of transmission equipment, the tags bear the
contents as shown in Table 1-1.


1-16

Table 1-1 Content of tag on inter-station fiber
Tag content Meaning Remarks
I: receive optical interface of local
station;
O: transmit optical interface of
local station

A: opposite station name

B: slot number of opposite station Physical slot number of
opposite station.
I/O--A--B--C
C: optical interface number of
opposite station
For a multiple-
optical-interface board, the
optical interfaces are
numbered 1~8 top to
bottom and left to right.

Figure 1-9 shows a typical fiber jumper tag in the inter-station connection.
Optical fiber
35.3mm
36.1mm
Optical fiber

Figure 1-9 Tag on fiber jumper transferred via the ODF

The content of the tag on the intra-station fiber jumper is shown in Table 1-2:


1-17

Table 1-2 Content of tag on intra-station fiber
Tag content Meaning Remarks
O: optical TX interface;
I: optical RX interface.

MN-O: rack number;
B: NE position

O/I-MN-O-B-C-D
C: board position number;
D: optical interface
number.
For a multiple- optical-interface
board, the optical interfaces are
numbered 1~8 top to bottom
and left to right.
O: optical TX interface;
I: optical RX interface.

MN-O: rack number;
B: NE position.

TO:
OUT/IN-MN-O-B-C-D
C: board position number;
D: optical interface
number.
For a multiple- optical-interface
board, the optical interfaces are
numbered 1~8, top to bottom
and left to right.

Figure 1-10 shows a typical tag of fiber jumper when the transmission equipment is
connected directly with fiber jumper.
Optical fiber
O p t i c a l f i b e r
35.3mm
36.1mm
T O :

Figure 1-10 Preparation of fiber jumper tag with transmission equipment connected
directly with fiber jumper


1-18

1.2.8 Receiving/transmitting Optical Power Test
1. Transmitting optical power test
As shown in Figure 1-11, the transmitting optical power is measured in the following
steps:
(1) Set the receiving optical wavelength of optical power meter to be the same
as the tested optical wavelength.
(2) Connect the testing fiber jumper to the OUT interface of the tested optical
interface board.
(3) Connect the other end of this fiber jumper to the test input interface of the
optical power meter, wait till the receiving optical power is stable, read the
optical power value, i.e., the transmitting optical power of this optical
interface board.
Note:
(1) To do this test, you have to keep the fiber connector clean and well connected,
and also keep the ring flange of the board front panel well connected and clean.
(2) Test the attenuation of fiber jumper in advance;
(3) Different fiber jumpers should be used for single-mode and multi-mode optical
interfaces.
(4) To test fiber jumper, the fiber jumper with FC/PC (round) or SC/PC (square)
connector should be selected according to the interface type.
(5) Optical power meter should work under the mode of Root Mean Square.

OUT
Optical power meter
Display
Control panel
Optical interface board
Test port
Fiber jumper
Power supply

Figure 1-11 Diagram of transmitting optical power test


1-19

2. Receiving optical power test
The receiving optical power test is shown in Figure 1-12. The test operations are as
follows:
(1) Set the receiving optical wavelength of optical power meter to be the same
as the tested optical wavelength.
(2) In this station, select the fiber jumper connected to the transmit optical
interface (OUT) of the adjacent station. (Under normal conditions, this fiber
jumper is connected to the receive optical interface of the optical interface
board in this station).
Connect this fiber jumper to the input interface of the optical power meter, wait till the
receiving optical power is stable, read the optical power value, i.e., the actual
receiving optical power of this optical interface board.
OUT
Optical power meter
Display
Control panel Test port
Fiber
jumper
ODF
Optical cable
ODF
Fiber
jumper
Power supply
Local station
Abjacent station

Figure 1-12 Diagram of receiving optical power test

The precautions are the same as those of transmitting optical power test.
1.2.9 Preparation of the Ethernet Cable of NMS
Computer
To connect NMS computer with gateway NE via Ethernet cable, you can use
cross-connection cable and straight-through cable. The cross-connection cable is
used for direct connection between the NMS computer and the gateway NE while
straight-through cable is used for connection between the NMS computer and the
gateway NE through a hub. The two differ from each other in the connectivity of the
cores of the cable.
Both these network cables use the RJ-45 connector, as shown in Figure 1-13:


1-20

PIN #1
PIN #8

Figure 1-13 RJ-45 connector

The correspondence between core colors of both ends of the straight-through cable
is as follows;
Table 1-3 Connection of the straight-through cable
Connector at the head
8-core, category 5
twisted pair
Connector at the end
Pin 1 White (orange) Pin 1
Pin 2 Orange Pin 2
Pin 3 White (green) Pin 3
Pin 4 Blue Pin 4
Pin 5 White (blue) Pin 5
Pin 6 Green Pin 6
Pin 7 White (brown) Pin 7
Pin 8 Brown Pin 8

The connection of the cross-connection cable is shown in Table 1-4.


1-21

Table 1-4 Connection of the cross-connection cable
Connector at the head
8-core, category 5
twisted pair
Connector at the end
Pin 1 White (orange) Pin 3
Pin 2 Orange Pin 6
Pin 3 White (green) Pin 1
Pin 4 Blue Pin 4
Pin 5 White (blue) Pin 5
Pin 6 Green Pin 2
Pin 7 White (brown) Pin 7
Pin 8 Brown Pin 8

OptiX Metro 500 MM

2-1

2 Routine Maintenance

2.1 Maintenance Overview
2.1.1 Maintenance Objective
The reliable operation of the system in different running environments largely
depends on efficient daily maintenance. To timely find out and solve the problem is
the objective of routine maintenance.
This chapter describes the content of routine maintenance of the OptiX Metro 500
equipment and the operation procedures. It provides the user with basic methods
and reference in determining the local office maintenance plan.
2.1.2 Classification of Maintenance
According to the maintenance cycle the maintenance is classified into the following
types:
1. Emergency maintenance
Emergency maintenance refers to the maintenance executed due to transmission
equipment fault and network adjustment, such as the maintenance conducted in
case of subscriber complaint for faults, equipment damage, or line faults.
Furthermore, the problems detected and recorded in daily routine maintenance are
also sources of the emergency maintenance.

Routine Maintenance OptiX Metro 500 MM

2-2

2. Daily routine maintenance
Daily routine maintenance refers to those maintenance items you should perform
everyday. It can help maintenance personnel learn the equipment operation
condition at any time so as to find and solve the problems in time. If a fault is
detected in daily maintenance, please record its specific physical location,
phenomena and process for timely fault removal.
3. Periodical routine maintenance
Periodical routine maintenance refers to the maintenance performed periodically.
Through it, maintenance personnel can get the long-term running status of the
equipment
The periodical routine maintenance falls into quarterly maintenance and yearly
maintenance.
2.1.3 Basic Principles for Routine Maintenance
The basic principle of routine maintenance is to find and solve problems in time.
Qualified maintenance personnel should be able to locate and eliminate equipment
failure quickly in case any problem occurs. What is more important, he should be
able to find and clear hidden troubles in time through routine maintenance, so as to
enable equipment to run stably for a long period of time. Excellent and effective
maintenance of the equipment would reduce the fault rate and increase the service
life of equipment.
If the maintenance personnel can detect any fault presymptom in time during routine
maintenance before the fault occurs and nip it in the bud, the troubleshooting mess
and economic losses caused by service interruption can be avoided. Moreover, the
damage to the equipment caused by the fault degradation can be prevented, the
maintenance costs can saved, the board replacement rate can reduced and the life
span of the equipment can be prolonged. All these requires the maintenance
personnel have not only profound knowledge and rich experience, but also sharp
eyes to look into details.
2.1.4 Maintenance Capability of OptiX Metro
500 Equipment
The OptiX Metro 500 equipment is designed to take into account the users
requirements for maintenance with respect to both hardware and software. The
OptiX Metro 500 equipment can provide powerful maintenance capability, which
includes the following:
1. In daily maintenance
(1) Dynamically monitoring the operation conditions and Qos of the equipment


2-3

in the network through the NM system.
(2) Assisting the maintenance personnel in monitoring the equipment operation
through the equipment indicator.
2. In troubleshooting
(1) Providing automatic service protection in case of abnormal service
interruption.
(2) Dynamically monitoring the fault of the equipment as a whole through the
NM system.
(3) Providing a variety of loopback testing functions.


2-4

2.2 Routine Maintenance Items of
Equipment
Table 2-1 lists the routine maintenance items, which are applicable to the
maintenance personnel for all equipment facilities.
Table 2-1 Routine maintenance items and maintenance cycle of the OptiX transmission
equipment
Maintenance test item Maintenance Type Cycle
Check the equipment temperature Equipment maintenance Daily
Log in NMS as a lower-level user NMS maintenance Daily
Check the NE and board state NMS maintenance Daily
Check alarm NMS maintenance Daily
Monitor performance event NMS maintenance Daily
Check protection switching NMS Maintenance Daily
Query log record NMS Maintenance Daily
Check ECC route NMS maintenance Daily
Check equipment environmental variables NMS maintenance Daily
Check NE time NMS Maintenance Daily
Query board configuration NMS Maintenance Daily
Check the fan periodically Equipment maintenance 2 weeks
Check service -- bit error test Equipment maintenance 1 month
Check the start and shutdown of NMS NMS maintenance 1 month
Modify login password of NMS user
periodically
NMS maintenance 1 month
Backup and dump NMS database NMS maintenance 1 month
Maintain NMS computer NMS maintenance 1 month
Test remote maintenance function NMS maintenance 1 month


2-5

2.2.1 Observing Indicators
There are four indicators on the front panel of the OptiX Metro 500,as showed in
Table 2-2.
Table 2-2 indicators
silkscreen Description remarks
RUN Running indicator Off : OptiX Metro 500 is not powered
Flash per 0.5 second : waiting for loading
software
Quick Flash : loading software
Slow flash : running normally
CRT critical alarm
indicator
Off :no critical alarm
On :critical alarm
MAJ Major alarm
indicator
Off : no major alarm
On : major alarm
los Optical interface
indicator

2.2.2 Checking Equipment Temperature
The operating temperature requirements for the equipment are shown in Table 2-3:
Table 2-3 Temperature requirements for the equipment
Operational Condition Temperature (C)
long-term operating conditions 0C~45C
Safe working condition -5C~50C

Safe operating condition means that the successive operating time does not exceed
72 hours and the accumulated time every year does not exceed 15 days.
Touch the board front panel with your hand to detect the board temperature.
Equipment temperature should be checked once a day.


2-6

2.2.3 Service Check -- Bit Error Test
This is one of tests on the long-term stabile operation and working performance of
the transmission system. In routine maintenance, periodical spot test should be
performed to the service channel on condition that the currently running services are
not interrupted, so as to judge whether the performance of all the service channels is
normal.
Approach 1: if there exist configured but not used service channels between two
stations, we can test the unused service channels to check the quality of the service
channels between the two stations;
Approach 2: if the configured service channels are all used between two stations, we
can temporarily disconnect the service channel used for protection to make bit error
test when the service is comparatively light, and judge the quality of the service
channel between two stations based on this test.
Approach 3: if the above two approaches are not available, we can monitor the
quality of the service channel through the performance and alarms reported by the
NMS.
Generally, for the selected service channel, bit error test is carried out by means of
setting inloop on the 155Mbit/s electrical interface board at the remote station, and
testing bit error with a meter in this station. The test period is 24 hours, the test result
should be zero.
Please note that the bit error detector should be in good grounding during the test.
To avoid interference, make every effort not to turn on/off other electric appliances
during the test.
Bit error test should be performed once a month. After the test is completed, the
inloop setting of the electrical interface board must be canceled.
Note:
The test meter should be grounded properly. It is suggested that other electric
appliances not be switched on/off in the test course.
During the test process, when performing loopback to the service channel of the
electrical interface board, first consider to perform hardware loopback to the external
DDF of the equipment. If the test result is abnormal (such as a great amount of bit
errors), perform loopback in the wiring area of the subrack instead.
If the fault remains after the hardware loopback, perform board software loopback to
the service channel of the electrical interface board. Note that after the test is
completed, be sue to cancel the loopback setting of the electrical interface board.


2-7

2.3 Routine Maintenance Items of
NMS
The OptiX iManager NMS is an important tool used in equipment routine
maintenance. To ensure safe and reliable operation of the equipment, maintenance
personnel in the NMS station should check the equipment via the NMS daily.
For detailed NMS operations, please refer to OptiX iManager T2000 Integration
Network Management System for Transmission Network (Sub-Network Level)
Operation Manual.
Prompt:
OptiX iManager T2000 is a network management system for transmission
equipment NE, and it is oriented to management at the sub-network level. Its
operating platform is Windows 2000 or Unix.

OptiX Metro 500 MM

3-1

3 Principle for Generation of
Alarm and Performance Event

This chapter covers principle for the generation of alarm and performance event of
SDH service and its application in troubleshooting.
3.1 Overview of SDH Alarm and
Performance Event
There are abundant overhead bytes in SDH frame structure, including regenerator
section overhead, multiplex section overhead, and path overhead. These overhead
bytes carry alarm and performance event information, thus enabling SDH system a
strong ability of on-line alarm and error monitoring. An understanding of the
generation and monitoring modes of the alarm information allows you to locate the
failure rapidly. The SDH alarm signal flow is shown in Figure 3-1.

Principle for Generation of Alarm and Performance Event OptiX Metro 500 MM

3-2

T1512780-93/d02
SPI RST (Note 1) MST MSA HPOM HUG HPC HPT HPA LPOM LUG LPC LPT LPA
Physical
Section
Regenerator
Section
Multiplex Section Higher Order Path Lower Order Path
Unused
LPC output/
LP-UNEQ
LOF
RS-BIP
Error (B1)
Regeneratedsignal
passed through
HP-UNEQ
HP-TIM
HP-SLM
HP-BIP Error (B3)
HP-FEBE
HP-FERF
HP-FERF
HP-FEBE
LOS
MS-AIS
MS-Exc. Error (B2)
MS-BIP Error (B2)
MS-FERF
MS-FERF
AU-AIS
AU-LOP
HP-LOM/TU-LOP
LP-UNEQ
LP-TIM
LP-SLM
LP-BIP Error (B3/V5)
LP-FEBE
LP-FERF
LP-FERF
LP-FEBE
AU-AIS
TU-AIS
TU-AIS
HO Path signal passed through
HOVC with POH and unspeci fied payload
HO unequipped signal
LO Path signal passed through
LOVC wi th POH and unspecified payload
LO unequipped signal
Unused
HPC output/
HQ-UNEQ
1
1
1
1
1
1
1
1
1
Detection
Generation
Insertion of all-ones (AIS) signal
AlarmIndication Signal
Far End Block Error
Far End Receive Failure
Loss Of Frame
Loss Of Multiframe
Loss Of Pointer
Loss Of Signal
Signal Label Mismatch
Trace Identifier Mismatch
Unequipped signal per Recommendation G.709
1
AIS
FEBE
FERF
LOF
LOM
LOP
LOS
SLM
TIM
UNEQ
1.Thiscolumn representsthedegenerateconnection function present in aregenerator.
NOTES
2.The insertion of al l-ones(AIS) andFERFon certain defectsmay be opti onal.
This figureshowstheseoptionsasdashed l ines. SeeRecommendation G.783.
FIGURE 2-2/G.782
SDHmaintenancesignal interaction

Figure 3-1 SDH alarm signal flow


3-3

3.1.1 Terminology Agreement
In order to describe the positions where common alarms and performance events
are generated and the generation modes, it is better to describe these common
alarms and performance events in detail along the signal flow. Signal flow, here, will
be classified into downlink and uplink signal flows according to the signal flow
directions.
The so-called downlink signal flow refers to the signal direction from the SDH
interface, to the cross-connect unit, and then to the PDH interface.
On the contrary, the uplink signal flow refers to the signal direction from the PDH
interface, to cross-connect unit, and then to the SDH interface.
3.1.2 Two Common Alarms
AIS alarm (i.e. all "1"s alarm) inserts the all "1"s signal to the lower level circuits,
indicating that the signal is unavailable. Common AIS signals include MS-AIS,
AU-AIS, TU-AIS.
RDI (remote receive defect indication) alarm: is the alarm transferred back to the
home station from the opposite station after the opposite station has tested alarms of
LOS (loss of signal), AIS and TIM (trace identifier mismatch). Common RDI alarms
include MS-RDI, HP-RDI and LP-RDI.
Note:
The alarm detected may be caused by the opposite station or due to other causes.
For example, R-LOS alarm is caused by broken fiber, and HP-LOM (higher order
path loss of multiframe) alarm at the home station is caused by the failed
cross-connect unit at the opposite station.


3-4

3.2 Generation and Detection of
Alarm and Performance Event in
Signal Flow of Higher Order Part
The fault locating principle is "line first, then tributary; high level first, then low level".
Since the alarm and performance data generated in the higher order part will cause
the report of the lower order alarm and performance events. We shall first focus on
the alarm, performance information generated between the SDH interface and the
cross-connect unit during maintenance. The signal flow chart of this route is
illustrated in Figure 3-2.
"1"
LOS
STM-1
optical
interface
B1
BI Err.
K2
AIS
MS-AIS
k2
MS-RDI
B2
M1
Frame synchronizer
and RS overhead
processor
MS overhead
processor
C2
AU-AIS
AU-LOP
J1
HP-UNEQ
HP-TIM
B3
B3 Err.
G1
G1
HP-REI
HP-RDI
MS-REI
H4
C2
HP-LOM
HP-SLM
B2-Err.
Downlink signal flow
Pointer processor and HP
overhead processor
AIS
A1, A2
LOF
Signal transfer point
Alarm termination point
(Report to SCC unit) (Insert down all "1"s signal)
H1,H2
H1,H2
"1"
"1"
Alarm report or return
(RST) (MST) (MSA, HPT)
Cross-connect unit

Figure 3-2 Flowchart of alarm signals generated between the SDH interface and the cross-connect unit

Note:
According to the processing positions of various overhead bytes in the STM-1 frame
structure, we divide the overhead bytes into four modules: regenerator section
overhead, multiplex section overhead, and higher order path overhead and the
pointer. If the first two modules have problems, generally all the higher order paths
will be affected, while the problem occurs in the overhead bytes of the last module
will only affect a certain higher order paths. Therefore, we can usually deduce the
influencing factor of the problem, and how to select the paths during the test.


3-5

We'll describe the signal flow and processing of each overhead byte module by
module in the following.
3.2.1 Downlink Signal Flow
1. Frame synchronizer and regenerator section overhead processor
Regenerator section overheads that will be mainly processed in this section are:
framing byte (A1, A2), regenerator section trace byte (J0), error checking byte (B1).
The alarm signal flow is as follows:
(1) When the STM-1 optical signal from the optical line enters the optical
receiving module, first, it is recovered into electrical signal after
optical/electrical conversion (O/E conversion) and then sent into frame
synchronizer and scrambler for processing. In this process, the O/E module
monitors this signal. If it is found that there is no light in the input signal,
optical power excessively low or high and code type of the input signal
mismatch, R-LOS (loss of signal) alarm will be reported.
Prompt:
No light usually occurs in the case that the fiber is broken, the optical transmitting
module at the opposite station fails or the optical receiving module at the home
station fails. The cause of excessively low optical power may be too much fiber
attenuation or poor contact of the optical joint, etc. Over high optical power refers to
the received optical power overload. If this happens, check whether the optical
attenuator is damaged, or the transmission distance of the optical board is suitable,
etc. The code type mismatch usually occurs when the signal rate between upstream
station and downstream station is inconsistent, or failed STG unit at upstream station
will cause data transmission disorder, etc. At this moment it is necessary to check
whether the optical board at upstream station is matched or the STG unit and
cross-connect unit are in normal operation, etc.
R-LOS alarm has no relation with overhead bytes, and it is only related to the quality
of input signal.

After R-LOS alarm occurs, only when optical receiving module at the home station
has continuously tested two correct patterns of code type, and meanwhile it has not
tested any new R-LOS alarm, can SDH equipment quit from R-LOS status and enter
normal status.
In case R-LOS alarm occurs, the system will insert all "1"s signal to the lower level
circuits.
(2) After frame synchronizer has received STM-1 signal sent from the


3-6

optical/electrical conversion module, it captures A1, A2 framing bytes in the
signal. Meanwhile it extracts line reference synchronous timing source from
the signal and sends it to the STG unit for clock locking.
Normally, the A1 value is F6H, and the A2 value is 28H. If incorrect A1 and A2 values
are detected in five successive frames, R-OOF (out of frame) alarm will be reported.
If R-OOF alarm lasts for more than 3 ms, it will report loss of frame alarm R-LOF and
insert all "1"s signal. In case of R-LOF alarm, if the frame alignment state lasts for
more than 1 ms, that means the equipment has resumed to normal.
J0 byte is used to confirm that both ends of the regenerator section are in continuous
connecting state. It requires that J0 bytes at receive end and transmit end be fully
matched. If they are not matched, the equipment will report J0-MM trace identifier
mismatch alarm.
Scrambler is mainly engaged in unscrambling the bytes in the STM-1 signals except
for the A1, A2 and J0 bytes.
(3) The regenerator section overhead processor extracts and processes other
regenerator section overhead bytes in the STM-1 signal. Among all the
bytes, B1 byte is of utmost importance.
If the B1 byte recovered from STM-1 signal is not in compliance with BIP-8
computing result of the preceding STM-1 frame, it will report B1 error. If the number
of B1 bit errors exceeds the threshold 10
-3
, the B1-OVER alarm will be reported.
When ten serious errored seconds (SES, i.e. the errored blocks reach to 30% in one
second) in regenerator section appear consecutively, it is considered that
RSUATEVENT (regenerator section unavailable time event) occurs.
At the same time, in this section these bytes, such as F1, D1~D3 and E1, which
have nothing to do with alarm will be sent to the SCC unit and OHP unit.
2. Multiplex section overhead processor
Multiplex overhead bytes that are related to alarm and performance and will be
processed in this part include: automatic protection switching channels (K1, K2),
BIP-24 (B2), multiplex section remote error indication (M1). The signal flow is as
follows:
(1) Multiplex section overhead processor extracts multiplex section overhead
bytes in STM-1 signal for processing and completes SF and SD detection. It
sends D4~D12, S1 and E2 to the SCC unit and overhead unit, meanwhile
realizes the shared multiplex section protection (MSP) function by the
cooperation of the SCC unit, cross-connect unit and K1, K2 bytes.
If the b6-b8 of K2 byte is detected as 111, the MS-AIS alarm will be reported and all
1s signal will be inserted.If the b6-b8 of K2 byte is detected as 110, the MS-RDI
alarm will be reported.
(2) If the B2 byte recovered from the STM-1 signal is not consistent with the


3-7

computing result of BIP-24 in the lastly received STM-1 frame (All bits
expect for the regenerator section overhead), then the processor reports the
B2 bit error.
Whether to report MS-REI is determined by M1 bytes. MS-REI transfers the number
of error interleaved block detected by B2 byte.
If B2 bit error exceeds the threshold 10
-6
, B2-SD alarm will be generated. If the B2 bit
error exceeds the threshold 10
-3
, B2-OVER alarm will be reported. In multiplex
section protection mode, the B2-SD and B2-OVER alarms will give rise to the
multiplex section protection switching.
When B2 byte detects SES consecutively for 10 seconds (errored block reaches
30% in one second), it is considered as an MSUATEVENT (multiplex section
unavailable time event).
3. Pointer processor and higher order path overhead processor.
This part processes higher order pointer justification and higher order path overhead.
Bytes related to pointer justification are H1, H2 and H3, and those related to alarm
and error are path trace byte (J1), signal label byte (C2), path BIP-8 (B3), path status
byte (G1), position indicator byte (H4).
Their alarm flows are as follows:
(1) The pointer processor interprets and justifies the pointer on the basis of H1,
H2 bytes of each AU-4, completes frequency and phase calibration and
tolerates phase jitter and wander in the network. At the same time, it locates
each VC-4 and sends it to corresponding higher order path overhead
processor. If H1 and H2 bytes of AU pointer are detected to be all "1"s,
AU-AIS (administrative unit-alarm indication signal) alarm will be reported
and all "1"s signal will be inserted. If the indicator values of H1 and H2 are
illegal (not in the normal range of 0~782) and receives illegal pointers
consecutively in eight frames, then it will report AU-LOP (administrative
unit-loss of pointer) alarm and insert all "1"s signal.
In case AU pointer positive justification occurs, the number of the PJCHIGH of the
MSA increases by 1. In case AU pointer negative justification occurs, the number of
the PJCLOW of MSA increases by 1.
(2) Higher order path overhead processor processes higher order path
overhead (HPOH) bytes received in N VC-4s. The processing mode for
each byte is as follows.
If J1 byte value detected is not the same as the preset, HP-TIM alarm will be
reported and all "1"s signal will be inserted.
If C2 byte is detected as 00, Higher Order Path- Unequipped (HP-UNEQ) alarm will
be reported and all "1"s signal will be inserted. When C2 byte detected is different


3-8

from the preset, Higher Order path - Signal Label Mismatch (HP-SLM ) alarm will be
reported and all "1"s signal will be inserted.
If B3 byte recovered from HPOH is not in compliance with BIP-8 computing result of
VC-4 signal of the preceding frame, B3 bit error will be reported.
In OptiX STM-1 (N<=4) lower order SDH interface unit, when extracting TU-12 signal
from VC-4, H4 byte is required to indicate which frame of the current multiframe the
current TU-12 is in. When H4 byte is tested as illegal, then Higher Order Path- Loss
of Multiframe (HP-LOM ) alarm will be reported, and all "1"s signal and normal H4
byte will be inserted.
If the b5 of G1 byte is detected as 1, HP-RDI alarm will be reported. Whether to
report HP-REI alarm depends on the value of G1 (b1-b4). If the value of G1 (b1-b4)
is 1~8, HP-REI alarm will be reported.
When B3 has detected SES consecutively for ten seconds (errored block reaches
30% in one second), it is considered as an HVCUATEVENT (higher order virtual
container unavailable time event).
Other overhead bytes F3, K3, N1 are reserved for future use.
(3) Finally, N STM-1 payload processed in the above way is sent to the
cross-connect unit for cross connection of higher order path and lower order
path.
3.2.2 Uplink Signal Flow
The extraction and termination of overhead bytes are completed in the downlink
signal flow of higher order part, and the generation of initial value for overhead byte
and the return of alarm signal to the opposite station are completed in the uplink
signal flow of higher order part.
1. Pointer processor and higher order path overhead processor.
(1) N STM-1 payload signals from the cross-connect unit is firstly sent to higher
order path overhead processor.
(2) The higher order path overhead processor generates N higher order path
overhead bytes, which are sent to pointer processor together with N
payload. Along the uplink direction, the setting function of higher order path
overhead bytes (including J1, C2, B3, G1, F2, F3 and N1) can be
completed.
If AU-AIS, AU-LOP, HP-UNEQ or HP-LOM (HP-TIM and HP-SLM optional) alarms
are detected in downlink signal flow, set the b5 of G1 byte to 1 and HP-RDI alarm
will be returned to the remote. If B3 bit errors are tested in the downlink signal, set
the b1-b4 of G1 byte to a corresponding bit error value (ranging 1~8) according to
the error value tested, and HP-REI alarm will be returned to the remote end.


3-9

H4 byte will not be processed in the uplink direction.
(3) Pointer processor generates N AU-4 pointers, adapts VC-4 into AU-4,
among which AU-4 pointer is represented by H1 and H2 bytes, then N
AU-4s are multiplexed into STM-1 signal by multiplexing processor and sent
to multiplex section overhead processor.
2. Multiplex section overhead processor
Multiplex section overhead processor sets MSOH bytes (including K1, K2, D4-D12,
S1, M1, E2 and B2) for the received STM-1 signal.
If R-LOS, R-LOF or MS-AIS alarms are detected in the downlink signal flow, the
b6-b8 of K2 byte will be set to 110 and MS-RDI will be returned to the remote.
If B2 bit errors are tested in the downlink signal flow, MS-REI alarm will be returned
to the remote via the M1 byte..
3. Frame synchronizer and regenerator section overhead processor
(1) Regenerator section overhead processor sets overhead bytes in
regenerator section (including A1, A2, J0, E1, F1, D1-D3 and B1), and send
a complete STM-1 electrical signal to frame synchronizer and scrambler.
(2) Frame synchronizer and scrambler scrambles STM-1 electrical signals
(except for A1, A2, J0), then STM-1 electrical signal is converted into STM-1
optical signal by the E/O module and sent out of the optical interface.


3-10

3.3 Generation of Alarm and
Performance in Signal Flow of
Lower Order Part
The following will describe the processing of the signal flow between PDH interface
and the cross-connect unit, and the generation of alarms by taking 2Mbit/s service
as an example. The alarm signal flow is as shown in Figure 3-3.
HPA , LPT
Signal flow
Signal transfer point
Alarm termination point
(Report to the SCC unit)
(Insert down all "1"s signal)
V5
V5
LP-UNEQ
J2
V1, V2
V1, V2
H4
LP-TIM
TU-LOP
TU-AIS
HP-LOM
LP-RDI
V5
BIP-2
LP-REI
T-ALOS
All "1''s
LPA PPI
V5
V5
LP-TFIFO
LP-RFIFO
Alarm report or return
E1-AIS
E1-AIS
E1 interface
LP-SLM
Cross-connect
board
All "1''s

Figure 3-3 Flow chart of the generation of alarm signals between the 2M PDH interface and the cross-connect unit

In view of different characteristics of processing the overhead bytes in each part, the
lower order part is divided into several functional modules in the above diagram.
They are higher order path adapter (HPA), lower order path terminal (LPT), lower
order path adapter (LPA) and asynchronous physical interface in sequence. In the
following, we will take these functional modules as index to introduce alarm signal
flow.


3-11

3.3.1 Downlink Signal Flow
1. Higher order path adaptation (HPA) and lower order path terminal (LPT)
This part is the core of lower order part, because most of the lower order overhead
bytes are processed here, including lower order path pointer indicator bytes (V1, V2,
V3), V5 byte, and path trace byte (J2).
(1) VC-4 signal from the cross-connect unit is sent to HPA.
(2) HPA demaps the VC-4 into VC-12. Pointers of all VC-12s are decoded, so
as to provide, between the VC-4 and the VC-12, the frame offset
information in byte.
When node clock at TU-12 assembler is different from local reference clock, this
process needs continuous pointer justification. Positive TU pointer justification
(LPPPJE) and negative TU pointer justification (LPNPJE) will be tested in downlink
signal flow. The TU pointer justification count threshold-crossing (The threshold is
adjustable) is expressed in a group of alarms HPADCROSSTR. HPADCROSSTR
includes HPADPJCHIGHCX15 (TU pointer positive justification count
threshold-crossing for 15 minutes), HPADPJCHIGHCX24 (TU pointer positive
justification count threshold-crossing for 24 hours), HPADPJCLOWCX15 (TU pointer
negative justification count threshold-crossing for 15 minutes) and
HPADPJCLOWCX24 (TU pointer negative justification count threshold-crossing for
24 hours).
If incorrect H4 multiframe byte sequence is detected in the downlink, then the
HP-LOM alarm is reported.
If V1 and V2 are detected to be all 1s, TU-AIS alarm will be reported. If the values
of V1 and V2 are tested illegal, TU-LOP alarm will be reported. If either of these two
alarms occur, all "1"s signal will be inserted down to the next function block.
In addition, if TU-AIS alarm is received, AIS signal will be inserted in the downward
data, and LP-RDI will be returned. To return LP-RDI is to set the b8 of V5 byte to "1".
(3) The VC-12 signal flow is sent to the LPT unit for the V5 byte processing.
Composition of timeslot structure of V5 byte is as shown in Figure 3-4.
b1 b2 b3 b4 b5 b6 b7 b8
BIP-2 error check
V5 byte
Inconsistent:LPBBE 1:LP-REI Unused
Signal label
000:LP-UNEQ 1:LP-RDI

Figure 3-4 The structure of V5 byte

Detect the b5-b7 of V5 byte in the downlink signal flow, and report them as signal
labels. If they are 000, it means that lower order paths are not equipped (LP-UNEQ),


3-12

and insert AIS signal into the lower level circuit. If signal labels mismatch, LP-SLM
will be reported and AIS signal will be inserted to the lower level circuit.
Path RDI information in the b8 of V5 byte will be terminated, and REI will be
reported.
Detect error monitoring bits of the b1 and b2 of V5 byte and calculate BIP-2 for
VC-12. BIP-2 value calculated for the current frame will be compared with the b1
and b2 of V5 byte recovered from the next frame. LPBBE will be reported if they are
inconsistent. Meanwhile the b3 of V5 byte is recovered, and if it is "1", it means that
the remote has BIP-2 bit error and will report it as LPFEBBE. The b4 of V5 byte is
not used.
When BIP-2 finds ten consecutive SESs (errored block reaches 30% in one second)
appears continuously during the test, it is considered as an LVCUATEVENT (lower
order virtual container unavailable time event).
(4) At the same time, the lower order path trace identifier J2 will be recovered
and it tests whether the value of J2 byte received is equal to the expected
value. If they are not equal, lower order path trace identifier mismatch alarm
(LP-TIM) will be reported.
2. Lower order path adaptation (LPA) and asynchronous physical interface
(PPI)
(1) C-12 data processed in the above way are sent to LPA. Subscriber data
stream and the related clock reference signals are recovered from the
container simultaneously, and sent to PPI as data and timing reference.
(2) The data and clock, after being processed by LPA, are sent to PPI, forming
a 2048kbit/s signal.
3.3.2 Uplink Signal Flow
1. Lower order path adaptation (LPA) and Plesiochronous physical
interface (PPI)
(1) When E1 electrical signal enters PPI and after clock extraction and dada
regeneration, it is sent to mapping and de-mapping processor, meanwhile
jitter suppression will be performed.
PPI checks and terminates the T-ALOS alarm. When it tests T-ALOS alarm, it will
insert all "1"s signals in the upper level circuit.
(2) LPA completes the data adaptation
If it receives E1-AIS, it will report E1-AIS alarm. T-ALOS alarm can cause E1-AIS
alarm, but in case T-ALOS alarm occurs, E1-AIS alarm will be suppressed.


3-13

If the deviation of uplink data rate is too great, it will result in FIFO overflow at the
transmit end of lower order path, thus LP-TFIFO will be reported.
2. Higher order path adaptation (HPA) and lower order path terminal (LPT)
(1) LPT allows the POH to be inserted in the C-12 to constitute the VC-12.
LPT inserts "signal label" in the b5-b7 of V5 byte, calculate BIP-2 for the previous
multiframe data and set the result to the b1 and b2 of V5 byte in the frame. If it is
tested in downlink signal flow that the downlink data has "path terminal error", the b3
of V5 byte will be set to "1" in the next frame and return LP-PEI.
(2) HPA adapts VC-12 into TU-12, then maps it into higher order VC-4, and
sends it to the cross-connect unit. The frame offset in byte between the
VC-12 and the VC-4 is expressed in a TU-12 pointer. Each frame defines
one of V1, V2, V3, and V4 bytes, and every four frames compose a
multiframe, and, the H4 byte that is used to determine the value of V byte is
also generated here.


3-14

3.4 SDH Alarm Suppression
Through the above analysis of various common alarms in the alarm signal flow, we
find that the alarms are associated with each other. Some alarms trigger other
alarms. In particular, higher order alarms often generate lower order alarms.
Here is a simple example. If R-LOS is generated on the optical board due to optical
path fault, AIS is inserted into the downstream circuit, i.e., the overhead bytes are all
"1"s. It triggers a series of alarms, such as R_LOF, R_OOF, and MS-AIS etc. The
generation of these alarms is natural, but it is not practical for the maintenance
personnel. As the upstream node fails, it is not necessary to talk about the
downstream nodes.
In addition, the downstream alarms triggered increase the amount of data reported
and the workload of the NMS and the SCC if they are all reported simultaneously
networkwide. They also increase the complexity of the problem for the user.
To avoid it, alarm suppression comes into picture to suppress the alarms that are not
necessary to report.
The following explains how the suppression of the main alarms is done, as shown in
Figure 3-5.
R-LOS R-LOF
B2-EXC MS-AIS
AU-LOP
AU-AIS HP-UNEQ HP-TIM HP-SLM
TU-AIS

Figure 3-5 Suppression tree of main alarms

The higher level alarm on the tail side of the arrow will suppress the lower level
alarms on the head side of the arrow. In this way, we can locate the higher level
alarm when a fault occurs.


3-15

Prompt:
Note that performance event data at different levels cannot be suppressed, though
alarms at different levels may be suppressed. For example, when B1 bit error occurs,
the system will not act to generate B2 bit error. B2 bit error is generated based on
the computing of data within its working scope.


3-16

3.5 Generation and Detection of
SDH Performance Event
The performance of an SDH network includes bit error performance, jitter
performance, wander performance, and availability indices. They are important for
the transmission QoS of the SDH network.
3.5.1 Bit Error
1. Generation mechanism
The SDH system adopts bit interleaved parity (BIP) to detect bit error, i.e., BIP is
done on the BIP matrix of the regenerator section, multiplex section, higher order
path, and lower order path with the B1, B2, B3 and V5 bytes.
The B1 byte is allocated for the regenerator section error monitoring function. This
function shall be a Bit Interleaved Parity 8 (BIP-8) code using even parity. The
working mechanism for the B1 byte is as follows:
At the transmit end the BIP-8 is computed over all bits of the previous STM-1 frame
after scrambling and the result is placed in the B1 byte of the current frame before
scrambling. At the receive end the BIP-8 is computed over all bits of the current
STM-(N-1) frame before descrambling and the result is compared with the value of
B1 byte of the next STM-1 frame after descrambling. If the two values are different,
conduct exclusive-OR operation on them. The number of "1"s in the result is the
number of errored blocks in the STM-1 frame during transmission.
The B2 byte is allocated for multiplex section error monitoring function and its
mechanism is similar to that of B1 byte. This function shall be a Bit Interleaved Parity
N 24 code (BIP-N 24) using even parity. The B1 byte monitors the errors
occurring in the whole STM-1 frame during transmission. One STM-1 frame has one
B1 byte. The B2 byte monitors the errors occurring in every STM-1 frame of the
STM-1 frame. There are N 3 B2 bytes in an STM-1 frame, namely, three B2 bytes
for one STM-1 frame. The mechanism for the B2 byte monitoring is that at the
transmit end the BIP-24 is computed over all bits of the previous STM-1 frame
except for the RSOH and the result is placed in B2 bytes of the current frame before
scrambling. At the receive end the BIP-24 is computed over all bits of the current
frame STM-1 after descrambling except for the RSOH and conducts exclusive-OR
operation between the parity result and B2 bytes in the next frame after
descrambling. The number of "1"s in the result of the exclusive-OR operation is the
number of errored blocks occurring in this STM-1 frame within the STM-1 frame
during transmission. This method can at most monitor 24 errored blocks.
The B3 byte is allocated for monitoring the bit error performance of VC-4 within the
STM-1 frame during transmission, i.e., monitoring the error performance of
140Mbit/s signal within the STM-1 frame. Its monitoring mechanism is similar to that


3-17

of the B1 and B2 bytes except that it is used to process BIP-8 parity for the VC-4
signal.
The V5 byte provides the functions of error checking, signal label and path status of
the VC-12 path. Bits 1- 2 convey the BIP-2. If the receive end monitors errored
blocks through BIP-2 and will display the errored blocks as performance events. Bit
3 of the V5 byte returns lower order path remote error indication (LP-REI) to the
transmit end and LP-REI will be displayed as performance event in the transmit end.
2. Error detection and report
Figure 3-6 shows the error detection relation and location.
V5
B1
B2
B3
RST MST RST MST HPT HPT LPT LPT

Figure 3-6 Error detection relation and location

In Figure 3-6 RST is regenerator section terminal, MST is multiplex section terminal,
HPT is higher order path terminal, and LPT is lower order terminal. The B1, B2, B3
and V5 bytes are allocated to monitor them respectively. Figure 3-6 shows that
errors occurring in lower order path will not be detected in higher order path,
multiplex section and regenerator section. If errors occur in regenerator section, they
will occur to multiplex section, higher order path and lower order path as well.
Generally higher order bit errors will trigger lower order errors. If there is B1
error, B2 ,B3 and V5 errors will usually be generated. If V5 bit error occurs, B3,
B2 and B1 bit errors do not necessarily occur.
When it detects errors, the SDH system reports error performance or alarm and
notifies the remote end through overhead bytes about error detection
3. Terms
Errored block (EB) is a block in which one or more bits are in error.
Background block error (BBE) is an errored block not occurring as part of an SES.
Far-end background block error (FEBBE) is a BBE event detected at the far-end.
Errored second (ES) is a one second period with one or more errored blocks or at
least one defect.
Far-end errored second (FEES) is an ES event detected at the far-end.


3-18

Severely errored second (SES) is a one-second period which contains 30% errored
blocks or at least one serious disturbance period (SDP). Here, the SDP is a period of
at least four consecutive blocks or 1ms (taking the longer one) where the error ratios
of all the consecutive blocks are 10
-2
or loss of signal occurs.
Far-end severely errored second (FESES) is a SES event detected at the far-end.
Consecutive severely errored seconds (CSES) are that the SES events
consecutively occur, but last for no more than 10 seconds.
Far-end consecutive severely errored seconds (ECSES) is a CSES event detected
at the far-end.
Unavailable second (UAS) is a period of unavailable time begins at the onset of ten
consecutive SES events. These ten seconds are considered to be part of
unavailable time.
4. Relationship with alarms
The SDH system reports error performance or alarm event to the home station and
returns error detection information to the remote station via overhead bytes. Based
on these performance and alarm events from the home station and remote station,
we can locate faulty section of the path or locate the direction where errors occur.
Table 3-1 lists the performance and alarm events related with errors.
Table 3-1 Monitor positions and functions of alarm and performance events for bit error threshold crossing
Item Performance event Alarm event
Performance events
both detected and
reported by the
home station
Performance events
detected by the
remote station, while
reported by the
home station
Alarm events reported
by the home station
when it detects error
threshold-crossing
Alarm events reported by the
home station when the
remote station detects error
threshold-crossing
Regenerat
or section
RSBBE - B1_OVER -
Multiplex
section
MSBBE MSFEBBE B2_OVER MS_REI
Higher
order path
HPBBE HPFEBBE HPCROSSTR HP_REI
Lower
order path
LPBBE LPFEBBE LPCROSSTR LP_REI

(1) If the B1 byte recovered from STM-1 signal is not consistent with BIP-8
computing result of the previous STM-1 frame, B1 bit error will be reported.
(2) If the B2 byte recovered from the STM-1 signal does not consist with the
result of BIP-24 computing over all bits expect for the regenerator section
overhead in the previous STM-1 frame, B2 bit error will be reported.


3-19

(3) If the B3 byte recovered from HPOH is not in compliance with BIP-8
computing result of VC-4 signal of the previous frame, B3 bit error will be
reported.
(4) If B1, B2 and B3 bit errors exceed 10
-6
, such alarms as B1_SD, B2_SD,
B3_SD will occur. If B1, B2 and B3 bit errors exceed 10
-3
, such alarms as
B1_OVER, B2_OVER and B3_OVER will occur.
When B1 detects ten SES events in regenerator section appear consecutively , it is
considered as an RSUATEVENT (regenerator section unavailable time event).
When B2 detects the SES consecutively for 10 seconds, it is considered as a
MSUATEVENT (multiplex section unavailable time event) .
When B3 tests the SES consecutively for 10 seconds, it is considered that
HVCUATEVENT (higher order virtual container unavailable time event) happen.
3.5.2 Pointer Justification
Pointer justification is a phenomenon especially for the SDH network. The occurring
of pointer justification indicates that there exists the NE out of synchronization in the
SDH network
Payload pointer in the SDH can be classified into administrative unit pointer
(AU_PTR) and tributary unit pointer (TU_PTR), and so pointer justification falls into
administrative unit pointer justification and tributary unit pointer justification.
1. Generation mechanism of AU pointer justification
In the AU-4 frame as shown in Figure 3-7, several bytes in specific locations (the first
nine bytes in the four row) are used to record the location of the starting point of data
information (to represent the data information phase). These bytes are called
pointer.Here, H1 and H2 are pointers, and three H3s are negative pointer justification
opportunities.
AU- 4 PTR
9 row
Y Byte: 1001SS11 (S Unspecified )
1* Byte:
11111111
10
270column
1 9
H1 Y Y H2 1* 1* H3 H3 H3
VC-4

Figure 3-7 AU pointer location and content

When the network is synchronous, the pointer is used to make phase alignment
among synchronous signals. If the SDH NEs work in the same clock, the signals


3-20

sent from various NEs to a certain NE have the same clock frequency, it is
unnecessary to make rate adjustment. In the transient point of view, it may be either
a little faster or slower, and so the phase alignment is needed.
When the network is out of synchronization, different NEs will work with phase
difference, and the pointer is used for frequency justification. The pointer justification
can also be used to tolerate the frequency jitter and wander of the network.
If the frame rate of the VC is different from that of the AUG, information will be stuffed
in the H3 bytes of AU pointer area or idle bytes stuffed with pseudo-random
information will be inserted to decrease or increase the frame rate of the VC.
Meanwhile the pointer value will be incremented or decremented to raise or drop the
frame rate of the VC. Thus, the pointer positive justification and negative justification
are generated as shown in Table 3-2.
Table 3-2 Pointer justification state
Byte numbering and content of the fourth row in the STM-1 frame State
name 7 8 9 10 11 12
Rate relation
Pointer
zero
justification
H3 H3 H3 Information Information Information Information
rate =
container rate
Pointer
positive
justification
H3 H3 H3 Stuffing Stuffing Stuffing Information
rate <
container rate
Pointer
negative
justification
Information Information Information Information Information Information Information
rate >
container rate

All the NEs in the SDH network are normally well synchronized, the pointer
justification seldom occurs. Actual monitoring on the pointer justification performance
of the network proves that AU pointer justification seldom occur and TU pointer
justification is also few.
It is difficult to guarantee all the NEs are well synchronized in all the time during the
long-term network running. If one or several NEs is out of synchronization, and even
if this situation lasts for a very short time, a great amount of pointer justifications will
occur. Pointer positive or negative justification consecutively appear to adjust phase
forward or backward to realize frequency justification.
2. Generation mechanism of TU pointer justification
The causes of TU pointer justification are as follows:
(1) Transformed from the AU pointer justification
TU pointer justification cannot appear when E1 signal is adapted into VC-12, then
into STM-1. If there is frequency offset between E1 signal of the switch and SDH
clock, adapt it to realize synchronization. So the TU pointer justification detected on
the tributary unit are generally transformed from the AU pointer justification. The TU


3-21

pointer justification happens during the demultiplexing.
(2) The system clock is not consistent with the receiving clock, and TU pointer
justification will be generated during the demultiplexing.
(3) When the service passes through the upstream NE which has pointer
justification, TU pointer justification will appear at the home station during
the demultiplexing.
3. Detection and reporting of the pointer justification
There are two modes of detection and reporting of AU pointer justification: remote
detection and home detection.
[Remote detection]
In this mode the AU pointer justification generated at the home station is transferred
to the remote station via H1 and H2 bytes. The remote station realizes the reporting
of the AU pointer justification by interpreting of H1 and H2 bytes. So in this mode, if
the remote station reports AU pointer justification event, it indicates that home station
has pointer justification. Here, the remote station refers to the downstream station
along the clock tracing direction.
[Home detection]
In this mode the AU pointer justification generated at home station is detected and
reported at the home station. So, if the home station reports AU pointer justification
event, it indicates that the home station has pointer justification.
In SDH system the AU pointer justification events of a majority of optical boards are
detected and reported by interpreting H1 and H2 bytes. That is, remote detection
mode is generally adopted.
The TU pointer justification reported on the tributary unit is a interpretation of
transforming AU pointer justification into TU pointer justification. Since the
transformation of AU pointer justification into TU pointer justification may happen at
the upstream station, it does not necessarily indicate that the home station has
pointer justification if the tributary unit reports pointer justification events.
Generally, AU pointer justification is generated at the upstream station, while
detected and reported at the downstream station. TU pointer justification is
generated at the station where AU pointer justification is transformed into the TU
pointer, and detected and reported at the tributary unit of the station where the
service is terminated.


3-22

3.6 Application of Locating a Fault
According to Signal Flow
Through the above study we are clear about the alarm signal flow, and we lay a
theoretical foundation for practical application. It is our ultimate goal to guide practice
with theory in promptly locating and removing the faults according to the signal flow
principles. The following describes two typical cases and we hope they help in our
troubleshooting.
3.6.1 Bit Error
(1) Networking diagram
Figure 3-8 shows a certain networking diagram.
A B C
W
E W W

Figure 3-8 Networking diagram in analysis of error problem

It is a chain network formed by three OptiX Metro 500 NEs at the rate of 155M bit/s.
Station A is a gateway station. There is 2Mbit/s service among the stations in
distributed service mode.
(2) Fault phenomena
Query the tested performance data from the NMS. It is found at station A that the
services between Stations A and B, between Stations A and C have a large amount
of LPBBE in the tributary, and a great deal of HPBBE, MSBBE in the westbound line.
Check Station B, and find a great number of HPFEBBE, MSFEBBE in the
eastbound line, and the service between Stations A and C has a majority of
LPFEBBE in the tributary, but the services between Stations B and C is normal.
Check Station C, and find that the service between Stations C and A has a number
of LPFEBBE only in the tributary.
(3) Fault analysis
According to the principle of " station first, board second", locate the faulty NE first.
There are bit errors between Stations A and B, between Stations A and C, and no bit
error between Stations B and C. According to this we can judge that the fault lies
between Stations A and B. Because all services with errors pass this section of route.
But is the problem in Station A or B, or in the optical path? We have to analyze
performance data.
First, we analyze the performance data in the line according to the principle of
"higher level first, lower level second, and line first, tributary second".


3-23

From the signal flow knowledge mentioned above, we may know that there are three
types of bit error monitoring overhead bytes B1, B2, B3 in the line. B1 byte monitors
the route between regenerator sections of two stations; B2 byte monitors the route
between the multiplex sections of the two stations; B3 byte monitors only the route
between higher order paths of the two stations. Obviously, the route monitored by B3
byte covers that monitored by B2 and B1 bytes, and the route monitored by B2 byte
covers that monitored by B1 byte.
As seen from the on-site data, there are only B2 and B3 bit errors. This means that
the route between the regenerator sections of the two stations is sound, thus
excluding the possibility of the optical path fault. If there are B2 bit error, there may
be a failure on the route between the multiplex sections of the two stations. In terms
of the contents of bit error data, Station A has BBE, and Station B has FEBBE. It
shows that the bit errors in the signal are tested at Station A, but it does not mean
that the problem must be in Station A as the bit errors are all tested in downlink
signal flow. Therefore, the bit errors tested in Station A may come either from the
receive end of the home station or from the transmit end of remote station B.
Now, we may troubleshoot station one by one. First self-loop the westbound optical
line of Station A and find that the errors of this station disappear, then the problem is
not in this station. Replace the westbound optical board S16 of Station B, and find
that the bit errors of the whole network disappear, then the problem is solved.
Tips:
In the analysis of the above problem, according to the coverage relation of routes
tested by B1, B2 and B3 bytes, we take such an assumption as B1 bit error would
cause B2 and B3 bit errors, and B2 bit error would cause B3 bit error.
But, in fact, this regularity is not absolute. Though the routes tested by B1, B2 and
B3 bytes have coverage relation, the contents tested by the three bytes respectively
don't have coverage relation. B1 byte detects all bytes of STM-1 frame, but B2 byte
only detects all bytes except regenerator section overhead and B3 byte only detects
all bits of VC-3 and VC-4 of each path. Hence, if the overhead bytes get bit errors,
the inclusion relation among the three will be broken off. For example, if errors tested
in regenerator section overhead byte B1 cannot be tested by B2 and B3 bytes.
However, in actual maintenance it is seldom to find that the errors only occur in the
overhead byte. We can make use of the route coverage relation of B1, B2 and B3
bytes to locate the failure as a rule of thumb.

3.6.2 Alarm
The thought of troubleshooting according to the alarm is similar to that of
troubleshooting according to the performance parameters. The only difference is that
bit error problem is simple in variety, while alarm problem is rather complicated.
Many kinds of alarms are often mixed together which brings difficulty in
troubleshooting. If we consider alarms comprehensively according to their


3-24

generation mechanism in signal flow, common problems can be solved. The
following describes a simple example.
3.6.3 Summary
Taking the advantage of generation locations of various alarms in the alarm signal
flow, you can narrow down the problem area step by step, thus achieving rapid fault
locating. Therefore, it is essential for professional maintenance personnel to grasp
the corresponding principles of the alarm and performance signal flow.
3.6.4 Method of Analyzing Alarms and Faults
1. For TU_AIS and TU_LOP alarms
Generally speaking, service will be interrupted when these two alarms occur. The
main causes for these two alarms include incorrect cross-connect configuration, the
cross-connect board fault or optical fiber fault. You can first check the optical fiber if it
is fast or if critical alarms take place on the line board. If you can remove the alarms
by handling the optical fiber, the problem is solved. If everything is normal with the
line board, then you need to check the configuration data of the cross-connect board,
including the timeslot configuration and traffic direction configuration.
2. For ETH_LOS alarm
In case that ETH_LOS alarm occurs, check whether the twisted-pair cables of the
home station are connected well, whether the equipment connected with the home
station via Ethernet interface operates normally, and connection point is sound. This
kind of faults is generally caused by the interface or cable. If the interface and cable
are in normal state, it is required to test whether the board works normally with
certain instrument.

OptiX Metro 500 MM

4-1

4 Alarm and Performance Event
Handling

Alarm Handing
In the maintenance of OptiX Metro 500 equipment many alarms need to be dealt
with, and an effective analysis of alarms is the key to solve the problem. To find out
the source of the problem, find the causes of the alarms first. Then use effective
methods to remove them.
The following describes the causes and treatments of the alarms generated in the
OptiX transmission equipment as a reference for maintenance.
Note:
1. Alarm level is the default one.
2. In terms of alarm generation and treatment, the alarms are classified into
equipment alarm, communication alarm, Qos alarm, processing alarm, environment
alarm and security alarm.
Note:
If it is necessary to replace the line unit, time unit, cross unit, scc unit of the OptiX
Metro 500, please replace the OptiX Metro 500.

4

Alarm and Performance Event Handling OptiX Metro 500 MM

4-2

AU_AIS
Item Description
Alarm name AU_AIS
Full name AU alarm indication signal
Alarm level Major
Alarm type Communication alarm
Alarm board SL1S/SL1D
Alarm indication Alarm indicator flashes twice every other seond.
Causes (1) MS_AIS, R_LOS and R_LOF alarms trigger AU_AIS alarm in the corresponding VC_4
path;
(2) The service configuration is incorrect;
(3) The opposite station sends AU_AIS alarm;
(4) Fault occurs to the transmitting part of the opposite station;
(5) Fault occurs to the receiving part of the home station.

Treatments (1) MS_AIS, R_LOS and R_LOF alarms of the home station trigger AU_AIS alarm in the
corresponding VC-4 path.
(2) The corresponding VC4 path does not receive service it should receive, resulting in
AU-AIS alarm on the corresponding path. In this case, TU-AIS alarm will occur on the
corresponding TU. At this time, check whether the station where AU-AIS alarm occurs and
its interworking station are normal and check whether the timeslot configuration of
intermediate station is wrong.
(3) Replace the corresponding cross-connect board and line board of the opposite station.
(4) Replace the line board and cross-connect board at the home station.

Remarks


4-3

AU_LOP
Item Description
Alarm name AU_LOP
Full name AU Loss of Pointer
Alarm level Major
Alarm indication Alarm indicator flashes twice every other second.
Causes (1) Fault occurs to the transmitting part of the opposite station;
(2) Service configuration of the opposite station is wrong.
(3) Bit errors received by the home station are excessive.

Treatments (1) Check whether service configurations of the opposite station and home station are
correct. If not, reconfigure the service.
(2) Generally, 155M optical interface board has no such failure. If it has, it is very possible
that the 155M optical interface board is not correctly configured. And if 622M and 2.5G
optical interface boards receive AU-LOP alarm, check the STG board of the opposite
station for normal operation and whether the cross-connect board has detected the clock.
(3) If it is 140M service, check whether the service is correctly accessed.
(4) Replace the corresponding cross-connect board and line board at the opposite station
in turn and locate the fault.
(5) Replace the line board and the cross-connect board at the home station.

Remarks


4-4

B1_EXC
Item Description
Alarm name B1_EXC
Full name Regenerator section (B1) excessive errors
Alarm level Minor
Alarm type QoS alarm
Alarm indication Alarm indicator flashes once every other second
Causes (1) Receiving signal is greatly attenuated.
(3) The optical fiber connector is dirty or the connector is not appropriate;

Treatments (1) Check whether the receiving optical power is normal. If too low, check whether optical
cable is intact and the optical fiber connector is clean, and then check whether the
launched optical power of the opposite optical board is normal.
(2) Loop back the home station, if bit errors disappear, the opposite optical board fails,
replace it. If bit errors increase, the home optical board fails, replace it.
(3) Check whether the operating temperature is too high.
(4) If there is no problem as mentioned above, replace the failed board.

Remarks Looping back the optical board will negatively influence the service.


4-5

B1_SD
Item Description
Alarm name B1_SD
Full name Regenerator section(B1) signal degraded
Alarm level Minor
Alarm indication Alarm indicator flashes once every other second.

Treatments (1) Clean the optical fiber connector and check the receiving/transmitting optical power of
the two terminal stations to determine whether there exists broken fiber or the attenuation of
optical path is too much;
(2) Check whether the clock trace setting of the entire network is correct;
(3) Perform self-loop for two terminal stations respectively to locate the faulty board and
replace it.

Remarks


4-6

B2_EXC
Item Description
Alarm name B2_EXC
Full name Multiplex section (B2) excessive errors
Alarm level Major
(4) Fault occurs to the receiving part of the home station;
(5) It is caused by B1 bit error.

Treatments (1) If B1 bit errors also appear, clear B1 bit error first.
(2) If there are only B2 bit errors, the fault is usually with the optical interface board, replace
it;
(3) Check if the operating temperature of equipment is too high.

Remarks


4-7

B2_SD
Item Description
Alarm name B2_SD
Full name Multiplex section (B2) signal degraded
Alarm level Minor
(2) The optical fiber connector is not clean or the optical connector is not appropriate;

replace it.

Remarks


4-8

B3_EXC
Item Description
Alarm name B3_EXC
Full name Higher order path (B3) excessive errors
Alarm level Major
(2) The optical fiber connector or optical connector is not appropriate;
(5) It is caused by B1, B2 bit errors.

Treatments (1) If B1 and B2 bit errors also appear, clear B1 and B2 bit errors first.
(2) If there are only B3 bit errors, the fault is usually with the optical interface board, replace
it;
(3) Check if the operating temperature of equipment is too high.

Remarks


4-9

B3_SD
Item Description
Alarm name B3_SD
Full name Higher order path (B3) signal degraded
Alarm level Minor

replace it.

Remarks


4-10

BIP_EXC
Item Description
Alarm name BIP_EXC
Full name BIP excessive errors
Alarm level Minor
Alarm board PL1S/PL1D/SP2D
Alarm indication Alarm indicator flashes twice every other second
Causes (1) B2 bit errors are excessive.

Treatments

Remarks


4-11

BIP_SD
Item Description
Alarm name BIP_SD
Full name BIP signal degraded
Alarm level Minor
Causes (1) B2 bit errors are excessive.

Treatments (1) Reset or swap the board;
(2) Replace the faulty board.

Remarks


4-12

BUS_LOC
Item Description
Alarm name BUS_LOC
Full name Bus dropping loss of clock
Alarm level Major
Alarm type Equipment alarm
Alarm indication Alarm indicator flashes twice every other second
Causes (1) The service configuration is incorrect;
(2) Fault occurs to the STG board.

Treatments (1) Check whether service configuration is correct;
(2) Check whether the STG board is in the position, whether the running and alarm
indicators are normal;
(3) Swap the STG board or replace it

Remarks


4-13

DOWN_E1_AIS
Item Description
Alarm name DOWN_E1_AIS
Full name 2M down signal alarm indication
Alarm level Minor
Causes (1) The 2M down signals are all 1s.

Treatments (1) It may be caused by higher order alarms, remove them.
(2) Replace the tributary board. If the alarm is ineffective yet, replace the cross-connect
board.

Remarks


4-14

E1_LOS
Item Description
Alarm name E1_LOS
Full name 2M line loss of signal
Alarm level Minor
Causes (1) The 2M interface cable is faulty;
(2) 2M service is not accessed.

Treatments (1) Loop back the related path at equipment interface part. If the alarm remains, check
whether the contact with the electrical interface board is good, or replace the board;
(2) If the alarm disappears, then the fault is not with the transmission equipment. Perform
loopback on the DDF to check whether there exists problem on the cable. If the alarm
disappears, loop back the switch on the DDF to determine whether the fault exists on the
switch.

Remarks


4-15

FAN_FAIL
Item Description
Alarm name FAN_FAIL
Full name Fan failed
Alarm level Major
Alarm board SCC
Causes (1) The fan is not turned on.
(2) The fan is faulty.

Treatments (1) Check whether the power switch on the fan subrack is turned on.
(2) Check whether the cable connection from the fan subrack to main subrack is intact.
(3) Check whether the fan operates normally.

Remarks


4-16

HP_LOM
Item Description
Alarm name HP_LOM
Full name Higher order path loss of multiframe
Alarm level Major
Alarm indication The alarm indicator flashes twice every other second.
(2) H4 byte is lost or incorrect.

Treatments (1) This alarm is possibly caused by problems at the opposite station. The common cause
is that the opposite cross-connect board fails or the transmitting/receiving of C2 byte is
mismatched.
(2) Check the service configuration of the opposite station and home station first. If it is
configured incorrectly, modify it and re-send the configuration.
(3) Check the bus selection on the opposite board for correctness, and T-LOS alarm, and
the cross-connect board and line board for failure. Check the opposite station through
self-loop of the optical path for hardware failure. If it is determined that the opposite station
fails, replace the cross-connect board and line board in sequence and check the subrack of
the opposite station.
(4) Check whether the home station fails through self-loop of the optical path. Replace the
faulty board.

Remarks


4-17

HP_RDI
Item Description
Alarm name HP_RDI
Full name Higher order path remote defect indication
Alarm level Minor
Causes (1) Opposite station receives AU_AIS/AU_LOP alarm signals.
(2) Fault occurs to the receiving part of the opposite station.
(3) Fault occurs to the transmitting part of the home station.

Treatments (1) When this alarm occurs, check whether the equipment has higher order alarm according
to the flow chart of alarm. If it has the alarm, analyze the cause.
(2) Check the corresponding path of the line board at the opposite station for AU-AIS and
AU-LOP alarms. If it has the alarm, process it. After processing, HP-RDI alarm should
disappear.
(3) If the opposite station has no alarm or after the corresponding alarm stops, HP-RDL
alarm still continues, it can be decided that the board fails, and replace the board.

Remarks


4-18

HP_REI
Item Description
Alarm name HP_REI
Full name Higher order path remote error indication
Alarm level Prompt
Alarm indication Alarm indicator does not flash
Causes (1) The opposite station receives B3 bit errors.

Treatments (1) Check whether the opposite station has B3 bit errors. If yes, and at the same time alarms
B1 and B2 occur, it is usually due to excessive line attenuation or optical interface board
failure. The localization method is the same as that when R-LOS occurs.
(2) If only a few B3 bit errors appear at the remote, generally, it is not caused by optical path
failure, while it is often the problem of the equipment itself. It is necessary to check whether
the cross-connect board and tributary board on the opposite equipment are normal.
(3) Check whether the cross-connect board and tributary board at the home station are
normal.
(4) Check whether the equipment is well grounded or there is a great interference source
near the equipment.

Remarks


4-19

HP_SLM
Item Description
Alarm name HP_SLM
Full name Higher order path signal identification mismatch
Alarm level Minor
Causes (1) Signal labels that the home station should receive and the opposite station should
transmit are not configured consistently.
(2) The service configuration is incorrect.

Treatments

Remarks


4-20

HP_TIM
Item Description
Alarm name HP_TIM
Full name Higher order path trace identifier mismatch
Alarm level Minor
Causes (1) Path trace bytes that the home station should receive and the opposite station should
transmit are configured inconsistently.

Treatments (1) Check whether the corresponding higher order path trace byte configuration on the line
board of the opposite station is the same as that on the home station. If the configurations
are different, modify and re-send them. If the configurations are identical, it can be decided
that the board fails. Replace the board.
(2) Check the service configurations of the opposite station and home station. If the
configurations are wrong, modify and re-send them.

Remarks


4-21

HP_UNEQ
Item Description
Alarm name HP_UNEQ
Full name Higher order path unequipped
Alarm level Minor
Causes (1) C2 byte is 0.

Treatments (1) Check whether the C2 byte is correctly configured. If it wrongly configured, modify and
re-send the configuration. If it is correctly configured, it can be determined that the board
fails. Replace the board.

Remarks


4-22

J0_MM
Item Description
Alarm name J0_MM
Full name Trace identifier mismatch
Alarm level Minor
Causes (1) J0 byte mismatch.

Treatments (1) From the NMS, check the J0 byte configurations of the two stations to which alarms
occurs; if they are inconsistent, reconfigure J0 byte to Huawei SBS;
(2) Perform hardware self-loop for the corresponding boards of two stations respectively,
and replace the board in which the alarm remains with a new one.

Remarks


4-23

LOOP_ALM
Item Description
Alarm name LOOP_ALM
Full name Loop alarm
Alarm level Minor
Alarm board PL1D/PL1S/SP2D
Alarm indication Alarm board flashes once every other second.
Causes (1) Line board are set to inloop or outloop.

Treatments (1) Set the line board to non-loopback.

Remarks


4-24

LP_RDI
Item Description
Alarm name LP_RDI
Full name Lower order path remote defect indication
Alarm level Minor
Causes (1) The opposite station receives TU_AIS/TU_LOP alarm signals;
(2) The receiving part of the opposite station fails.
(3) The transmitting part of the home station fails.

Treatments (1) Check if the corresponding path of the tributary board of the opposite station has TU-AIS
and TU-LOP alarms. If it has the alarms, process them. After the processing, LP-RDL alarm
should disappear.
(2) If the opposite station has no alarm or LP-RDL alarm still exists after other alarms
disappear, it shows that the board fails. Replace the faulty board.

Remarks


4-25

LP_REI
Item Description
Alarm name LP_REI
Full name Lower order path remote error indication
Alarm level Minor
Causes (1) Errors with lower order path receiving of the opposite station

Treatments (1) Check and treat the alarms of the opposite station;

Remarks


4-26

LP_RFI
Item Description
Alarm name LP_RFI
Full name Lower order path remote failure indication
Alarm level Minor
Causes (1) The lower order path receiving of the opposite station fails.

Treatments (1) Check and treat the alarms of the opposite station;
(2) Typically there also exists some problem on the transmitting signal of the tributary
board of the home station that reports alarms. Replace the tributary board.

Remarks


4-27

LP_R_FIFO
Item Description
Alarm name LP_R_FIFO
Full name FIFO overflow on the receiving side of the lower order path
Alarm level Minor
Causes (1) The service configuration is incorrect.

Treatments (1) Check the serviceconfiguration. After correcting the mistake, re-send the configuration.

Remarks


4-28

LP_SIZE_ERR
Item Description
Alarm name LP_SIZE_ERR
Full name TU structure error
Alarm level Minor
Causes (1) The mapping structure configuration is wrong.

Treatments (1) Check and treat the alarms of the opposite tributary board;
(2) Replace the tributary board of the home station.
(3) Replace the tributary board of the opposite station.

Remarks


4-29

LP_SLM
Item Description
Alarm name LP_SLM
Full name Lower order path signal label mismatch
Alarm level Minor
Alarm indication Alarm board flashes once every other second
Causes (1) Lower order path signal labels of the home station and opposite station are not
configured consistently;

Treatments (1) Check whether the signal label byte configuration of the corresponding lower order path
on the tributary board of the opposite station is the same as that of the home station. If the
configurations are different, modify and re-send them. If the configurations are identical, it
can be decided that the board fails. Replace the board.

Remarks


4-30

LP_T_FIFO
Item Description
Alarm name LP_T_FIFO
Full name FIFO overflow on the transmission side of the lower order path
Alarm level Minor
Causes (1) The frequency deviation of PDH input signal is too big.

Treatments (1) Check whether the input PDH signal frequency deviation falls into the frequency
deviation range required for the equipment.

Remarks


4-31

LP_TIM
Item Description
Alarm name LP_TIM
Full name Lower order path tracking identification mismatch
Alarm level Minor
Causes (1) Lower order path trace bytes the home station should receive and the opposite station
should transmit are configured inconsistently.

Treatments (1) Check whether the corresponding lower order path trace byte configuration of the
tributary board of the opposite station is the same as that of the home station. If the
configurations are different, modify and re-send them. If the configurations are identical, it
can be decided that the board fails. Replace the board.

Remarks


4-32

LP_UNEQ
Item Description
Alarm name LP_UNEQ
Full name Lower order path unequipped
Alarm level Minor
Causes (1) No 2M service access.

Treatments (1) Check the service configurations of the opposite station and home station. If the
(2) Check whether the attribute configurations of the tributary boards of both stations are
correct.

Remarks


4-33

LTI
Item Description
Alarm name LTI
Full name Loss of timing input
Alarm level Major
Alarm board STG
Causes In non-S1 byte mode:
(1) Optical fiber is broken (if tracing line clock source).
(2) External source clock stops inputting (if tracing external clock source).
(3) The synchronous source is configured as unrecoverable.
(4) The synchronous clock source traced is blocked.
(5) The synchronous clock source is wrongly configured.
In S1 byte mode:
(1) Broken fiber occurs;
(2) Enter the free-run mode.
(3) The synchronous source is incorrectly configured.
Treatments (1) Check whether the synchronous clock source is configured to trace nonexistent clock
source. If the configuration is incorrect, modify and re-send it.
(2) If the configuration is correct, check whether the traced synchronous source is normal. If
not, eliminate the corresponding failure to make it normal. If it is configured as tracing line
clock and there is signal loss alarm on the line, eliminate the signal loss alarm first. If tracing
external clock, check whether the external clock is normal and whether the external clock
line is in good contact.
(3) If the traced synchronous source is normal, it can be decided that the board fails.
Replace the board.

Remarks


4-34

MS_AIS
Item Description
Alarm name MS_AIS
Full name Multiplex section alarm indication signal
Alarm level Major
Causes (1) The opposite station sends MS-AIS signal;
(2) The STG board of the opposite station fails.
(3) The receiving part of the home station fails.

Treatments (1) Check whether the line board of the opposite station fails. Reset or replace the board to
check whether the alarm disappears.
(2) Check the line board of the home station. Reset or replace the board to check whether
the alarm disappears.

Remarks


4-35

MS_RDI
Item Description
Alarm name MS_RDI
Full name Multiplex section remote defect indication
Alarm level Minor
Causes (1) The opposite station receives R_LOS/R_LOF/MS_AIS signals.

Treatments (1) Check whether there are R-LOS, R-LOF and MS-AIS alarms on the line board of the
opposite station. If there are, remove them. Then the MS-RDI alarm at the home station
should disappear.
(2) If there is no alarm or MS-RDI alarm still exists after the corresponding alarms
disappear, it can be decided that the board is failed. Replace it.
(3) Fiber cut seldom happens, because this alarm can only occur when the transmitting
fiber is broken, while the receiving fiber of the home station is intact. If the
transmitting/receiving fibers are all broken, MS-RDI alarm can not be returned to the home
station. The key is to check the fiber connection at the home station and opposite station
(ODF side, optical interface board side).

Remarks


4-36

MS_REI
Item Description
Alarm name MS_REI
Full name Multiplex section remote error indication
Alarm level Prompt
Alarm indication Alarm indicator does not flash.
Causes (1) The opposite station receives B2 bit errors.

Treatments (1) Self-loop the corresponding optical interface board of the home station and check
whether the bit errors in MS-REI performance event at the home station is still increasing.
Then use this as a basis to decide the problem lies with the transmitting part of the home
terminal or the receiving part of the opposite station.
(2) If the bit errors do not increase, it shows that the receiving part of the opposite board
fails. Replace the board.
(3) If the bit errors keep on increasing, it shows that the transmitting part of the board at the
home station fails. Replace the board.

Remarks When the service has been loaded, self-loop of optical path is prohibited.


4-37

NESTATE_INSTALL
Item Description
Alarm name NESTATE_INSTALL
Full name NEstate install
Alarm level Critical
Alarm type Processing alarm
Alarm board SCC
Alarm indication Alarm indicator flashes three times every other second.
Causes (1) NE is in installation state.

Treatments (1) Check the configuration data. After modification, re-send the configuration.

Remarks


4-38

POWER_FAIL
Item Description
Alarm name POWER_FAIL
Full name Power failure
Alarm level Major
Alarm board SCC
Causes (1) The power switch of the power board is not turned on.
(2) The power board fails.
(3) The STG board is faulty or not in position;
(4) The battery is low or faulty

Treatments (1) Check whether the power switch of the power board is turned on. If not, turn it on.
(2) Check whether the STG board is in position and if it is running normally.
(3) Check whether the output of power board is normal. If not, replace the failed board.

Remarks


4-39

PS
Item Description
Alarm name PS
Full name Protection switching happened indication
Alarm level Major
Causes (1) Protection switching occurs;
(2) Board parameters are set incorrectly.

Treatments PS alarm on the tributary board
(1) In path protection ring, when PS alarm occurs on the tributary board, check whether
there are alarms such as R-LOS, R-LOF, and excessive bit errors which initiate
protection switching. If there are such alarms, treat them first.
(2) In chain network or multiplex section protection ring, when there is PS alarm on the
tributary board, check whether the tributary board is configured as non-protection correctly.
PS alarm on the cross-connect board
(1) In multiplex section protection ring, when PS alarm appears on the cross-connect
board, check whether there are alarms such as R-LOS, R-LOF, excessive bit errors which
generate protection switching. If there are such alarms, remove them first.
(2) If the service is interrupted due to switching, restart after the multiplex section protection
protocol of the whole network has stopped.
(3) If there is no alarm which results in switching, check whether protection switching
protocol of each NE is correct and whether it is correctly started.

Remarks


4-40

PWR_MAJ_ALM
Item Description
Alarm name PWR_MAJ_ALM
Full name Serious under/over-voltage
Alarm type Environment alarm
Alarm board SCC
Alarm indication Alarm indicator flashes three times every other second.
Causes (1) The input voltage is abnormal.

Treatments (1) Check whether the input voltage of the power supply where the alarm occurs is normal;
(2) Check whether the wiring between connection post and the power supply box is normal.

Remarks


4-41

R_LOF
Item Description
Alarm name R_LOF
Full name Receive loss of frame
Alarm indication Alarm indicator flashes three times every other second
Causes (1) The receiving signal is greatly attenuated.
(2) The transmitting signal of the opposite station has no frame structure.
(3) Fault occurs in the receiving direction of this board.

Treatments (1) If there is R-LOS, generally, it is due to broken fiber, too much fiber attenuation, board
failure etc.
(2) Check whether the fiber is intact.
(3) Check whether the connector of the fiber is in good contact and clean the connector of
the fiber.
(4) If the board is faulty, replace it.

Remarks


4-42

R_LOS
Item Description
Alarm name R_LOS
Full name Receive loss of signal
Causes (1) Broken fiber occurs;
(2) The line is greatly attenuated or optical power is overloaded.
(3) The transmitting part of the opposite station fails, and the line transmission is invalid.
(4) The cross-connect board of the opposite station is faulty or not in position;
(5) The STG board of the opposite station fails.

Treatments (1) Generally, it is due to broken fiber, too much fiber attenuation, board failure, etc.
(2) Check whether the optical cable is intact and the optical connector is in good contact.
Clean the optical cable connector.
(3) If the receiving optical power is overloaded, add an attenuator.

Remarks


4-43

R_OOF
Item Description
Alarm name R_OOF
Full name Receive out of frame
Causes (1) The receiving signal is greatly attenuated.
(2) Bit errors are excessive during the transmission.
(4) Fault occurs to the receiving direction of the home station.

Treatments (1) Generally, it is due to broken fiber, too much fiber attenuation, board failure, etc.
(2) Check whether the optical cable is intact and the optical connector is in good contact.
Clean the optical cable connector.
(3) If the receiving optical power is overloaded, add an attenuator.

Remarks


4-44

RP_LOC
Item Description
Alarm name RP_LOC
Full name Receiving phase-locked ring loss of clock
Alarm level Major
(2) The board is faulty.

Treatments (1) Check the service configuration; after modification, re-send it;
(2) Reset or swap the board;

Remarks


4-45

SYN_BAD
Item Description
Alarm name SYN_BAD
Full name Synchronous source deteriorated
Alarm level Minor
Alarm board STG
Causes (1) The index quality of synchronous source traced degrades.

Treatments (1) Check and process the bit errors and pointer justification performance events occurring
in the direction of clock source traced.
(2) When setting clock trace, do not form clock tracing loop.

Remarks


4-46

SYNC_C_LOS
Item Description
Alarm name SYNC_C_LOS
Full name Synchronous source level loss
Alarm level Major
Alarm board STG
Causes In non-S1 byte mode:
High level clock source is unavailable:
(1) Optical fiber is broken (if tracing line clock source).
(2) External source clock stops inputting (if tracing external clock source)
In S1 byte mode:
(1) S1 byte switching occurs at the home station.
(2) External clock (BITS) input has changed.

Treatments (1) Reset the priority level of clock source.
(2) If tracing line clock source, check whether there is R-LOS alarm and treat it.
(3) If tracing tributary clock source, check whether there is T-ALOS alarm and treat it.
(4) If tracing external clock, check whether the external clock source operates normally.

Remarks


4-47

T_ALOS
Item Description
Alarm name T_ALOS
Full name 2M interface loss of analog signal
Alarm level Major
Causes (1) 2M service is not accessed.
(2) The output port of 2M interface at the DDF is disconnected or loosened.
(3) The input port of 2M interface at the home station is disconnected or loosened.
(4) The board is faulty
(5) Cable fault.
(6) Exchange resetting.
Treatments Gradually pinpoint the alarm area on the link-by-link self-loop basis to locate the alarm
point.
(1) Confirm the board position and path number where the alarm is generated via the NMS.
(2) Self-loop the path on 2M interface board. If the alarm still does not disappear after
self-loop, check whether the interface board is in good contact. If the contact is good,
replace 2M tributary board.
(3) If the alarm disappears after performing self-loop on the interface board, it can be
determined that the transmission equipment does not fail. On the DDF, loop back the
transmission equipment and confirm whether the problem is with the cable between the
DDF and transmission equipment. If the alarm does not disappear after self-loop, surely the
connector of the DDF and the connection cable between the DDF and interface board have
problems.
(4) If the alarm disappears after performing self-loop at the DDF, loop back the exchange
equipment on the DDF and determine whether the problem exists between the DDF and
the exchange or the problem lies with the exchange itself.

Remarks


4-48

T_LOC
Item Description
Alarm name T_LOC
Full name Transmit loss of clock
Alarm level Major
Causes (1) The cross-connect board is faulty or not in position;
(2) The STG board is faulty or not in position.

Treatments (1) Check whether the cross-connect board and STG board are in position and working
normally;
(2) Reset or swap the cross-connect board and STG board;
(3) Replace the cross-connect board and STG board.

Remarks


4-49

T_LOS
Item Description
Alarm name T_LOS
Full name Transmit loss of signal
Alarm level Major
Causes (1) The service configuration is incorrect.

Treatments (1) Check the service configuration for correctness. After modification, re-send it;
(2) Reset or swap the board;

Remarks


4-50

T_LOTC
Item Description
Alarm name T_LOTC
Full name 2M interface loss of transmit clock
Alarm level Minor
Causes (1) The board is faulty

Treatments (1) Reset or swap the board;

Remarks


4-51

TU_AIS
Item Description
Alarm name TU_AIS
Full name TU alarm indication
Alarm level Major
(2) The corresponding path of the opposite station fails.
(3) It is caused by higher order alarms such as R-LOS.
(4) Fault occurs to the cross-connect board.

Treatments (1) Check whether there is higher order alarm such as R-LOS. If there are such alarms,
eliminate them.
(2) Check whether service configuration is correct.
(3) If it is caused by failures of cross-connect board and tributary board, replace the failed
board.

Remarks


4-52

TU_LOP
Item Description
Alarm name TU_LOP
Full name TU loss of pointer
Alarm level TU loss of pointer
Alarm level Major
Causes (1) The interface between tributary board and cross-connect board fails.

Treatments (1) Check whether the configurations of cross-connect board and tributary board are correct.
If not, modify and re-download them.
(2) Check whether there are bent pins on the backplane at both end stations by means of
self-loop method. Replace the board positions of the corresponding tributary board and
cross-connect board in sequence.

Remarks


4-53

W_R_FAILURE
Item Description
Alarm name W_R_FAILURE
Full name Reading or writing single chip register failed
Alarm level Major
Alarm board SL1S/SL1D/PL1S/PL1D/SP2D
Causes (1) The board is faulty;
(2) Fault occurs to the STG board.

Treatments (1) Replace the corresponding board;
(2) Replace the STG board of the home NE.

Remarks


4-54

WRG_BD_TYPE
Item Description
Alarm name WRG_BD_TYPE
Full name Wrong inserted board type
Alarm level Major
Alarm board SCC
Causes (1) The incorrect board is plugged in;
(2) The board configuration is incorrect.

Treatments (1) Check whether the configured board type is consistent with the actual one;
(2) Check whether the type of the board software is matched with the hardware.

Remarks


4-55

Performance Events of SDH Service
The performance events of the SDH service can be classified into three types:
pointer justification, bit error and equipment function, as shown in Table 4-1,
Table 4-2 respectively.
Table 4-1 List of pointer justification performance events
Abbreviation Detailed information Board supported
AUPJCHIGH AU positive pointer justification
count
AUPJCLOW AU negative pointer justification
count
SL1D/SL1S
TUNPJC TU negative pointer justification
count
TUPPJC TU positive pointer justification
count
SP2D/PL1D/PL1S


4-56

Table 4-2 List of bit error performance events
HPBBE Higher order path background block
error
HPCSES Higher order path consecutive severely
errored second
HPES Higher order path errored second
HPFEBBE Higher order path far-end background
block error
HPFEES Higher order path far-end errored
second
HPFESES Higher order path far-end severely
errored second
HPSES Higher order path severely errored
second
HPUAS Higher order path unavailable second
SL1D/SL1S
LPBBE Lower order path background block
error
LPCSES Lower order path consecutive severely
errored second
LPES Lower order path errored second
LPFEBBE Lower order path far-end background
block error
PL1D/PL1S/SP2D
LPFECSES Lower order path far-end consecutive
severely errored second
LPFEES Lower order path far-end errored
second
LPFESES Lower order path far-end severely
errored second
LPSES Lower order path severely errored
second
LPUAS Lower order path unavailable second
PL1D/PL1S/SP2D
MSBBE Multiplex section background block
error
MSCSES Multiplex section consecutive severely
errored second
SL1D/SL1S


4-57

MSES Multiplex section errored second
MSFEBBE Multiplex section far-end background
block error
MSFECSES Multiplex section consecutive severely
errored second
MSFEES Multiplex section far-end errored
second
MSFESES Multiplex section far-end severely
errored second
MSSES Multiplex section severely errored
second
MSUAS Multiplex section unavailable second
SL1D/SL1S
RSBBE Regeneration section background block
error
RSCSES Regeneration section consecutive
severely errored second
RSES Regeneration section errored second
RSOFS Regeneration section out-of-frame
second
RSOOF Regeneration section out-of-frame
count
RSSES Regeneration section severely errored
second
RSUAS Regeneration section unavailable
second
SL1D/SL1S


4-58

AUPJCHIGH
Item Description
Performance
event name
AUPJCHIGH
Full name Administrative Unit Pointer Justification Count HIGH
Board supported SL1D/SL1S
Causes The fundamental reason of the AU pointer justification is that the clocks of the NEs in the SDH
network are not synchronous.
(1) Performance deterioration of the external clock.
(2) Misconnection of optical fibers causes mutual tracing.
(3) Performance deterioration of equipment due to extra-high equipment temperature
(4) Clock configuration error;
(5) The clock quality is deteriorated because the SSM clock protection is not started.
(6) The clock ID is not configured, so the loss of the master clock source leads to pointer
justification in the whole network.
(7) Performance deterioration of the line board
(8) Performance deterioration of the clock board

Treatments (1) Check whether there is any clock alarm, such as SYN_BAD, LTI, S1_SYN_CHANGE,
EXT_SYN_LOS, etc. Please handle these alarms first.
(2) In the case of the networkwide pointer justification, please check whether the clock
configuration is correct, including the clock ID, SSM protocol, clock tracing level, etc.
(3) In the case of non-networkwide pointer justification, please check whether the equipment
environment temperature is normal, whether the line board performance is normal and replace
the faulty board.

Remarks


4-59

AUPJCLOW
Item Description
Performance
event name.
AUPJCLOW
Full name Administrative Unit Pointer Justification Count LOW
Causes The fundamental reason of the AU pointer justification is that the clocks of the NEs in the SDH
network are not synchronous.
(1) Performance deterioration of the external clock.
(2) Misconnection of optical fibers causes mutual tracing
(3) Performance deterioration of equipment due to extra-high equipment temperature
(4) Clock configuration error
(5) The clock quality is deteriorated because the SSM clock protection is not started.
(6) The clock ID is not configured, so the loss of the master clock source leads to the pointer
justification in the whole network.
(7) Performance deterioration of the line board
(8) Performance deterioration of the clock board.

Treatments (1) Check whether there is any clock alarm, such as SYN_BAD, LTI, S1_SYN_CHANGE,
EXT_SYN_LOS, etc.. Please handle these alarms first.
(2) In the case of the networkwide pointer justification, please check whether the clock
configuration is correct, including the clock ID, SSM protocol, clock tracing level, etc.
(3) In the case of the networkwide pointer justification, please check whether the equipment
environment temperature is normal, whether the line board performance is normal and replace
the faulty board.

Remarks


4-60

TUNPJC
Item Description
Performance
event name.
TUNPJC
Full name TU Negative Pointer Jitter Count
Board supported SP2D/PL1D/PL1S
Generation
principle
The reason of the AU pointer justification is that the AU pointer justification is transformed into
the TU pointer justification during the demultiplexing. The TU pointer justification is generated
on the cross-connect unit but reported on the tributary board.
Causes (1) The AU pointer justification occurs in the network.
(2) Cross-connect board fault.
(3) Tributary board fault.

Treatments (1) Handle the AU pointer justification.

Remarks


4-61

TUPPJC
Item Description
Performance
event name.
TUPPJC
Full name TU Positive Pointer Jitter Count
Causes The reason of the AU pointer justification is that the AU pointer justification is transformed into
the TU pointer justification during the demultiplexing. The TU pointer justification is generated
on the cross-connect board but reported on the tributary board.
(1) The AU pointer justification occurs in the network.
(2) Cross-connect board fault

Treatments (1) Handle the AU pointer justification first.

Remarks


4-62

HPBBE
Item Description
Performance
event name.
HPBBE
Full name HP Background Block Error
Causes The higher order bit error refers to the error generated when detecting B3 byte. The
background block error is the block in which one or more bits are in error during transmission.
(1) External environment interference;
(2) Fault of the switching equipment interconnected with the SDH equipment;
(3) Signal cable fault;
(4) Line board fault;
(6) Timing board fault

Treatments (1) If this performance event is independently reported, it is most likely due to external factors.
Please check whether there is any electromagnetic interference upon the equipment, whether
the operating temperature of the equipment is normal and whether the equipment is well
grounded.
(2) If the performance event is reported accompanying alarm, regeneration section and
multiplex section bit error report, please remove other alarms and performance events
according to the priority.

Remarks The performance event priority is: regeneration section bit error, multiplex section bit error,
higher order path bit error and lower order path bit error.


4-63

HPCSES
Item Description
Performance
event name.
HPCSES
Full name HP Consecutive Severely Errored Second
Causes The higher order path bit error refers to the error generated when detecting B3 byte. The
severely errored second is the one-second period which contains 30% errored blocks.
Generally, the consecutive severely errored second will be accompanied with the B3_OVER
alarm, and possibly the service will be interrupted.
Treatments (1) Check whether there is any electromagnetic interference upon the equipment, whether the
operating temperature of the equipment is normal and whether the equipment is well
grounded.
(2) If the performance event is reported accompanying the reporting of alarm, regeneration
section and multiplex section bit errors, please remove other alarms and performance events
(3) Check whether the interconnected switching equipment is normal.
(4) Check whether the optical power is normal;

Remarks
The performance event priority is: regeneration section bit error, multiplex section bit error,


4-64

HPES
Item Description
Performance event
name.
HPES
Full name HP Errored Second

errored second is a one second period with one or more errored blocks or at least one
defect.

Treatments (1) If this performance event is independently reported, it is most likely due to external
factors. Please check whether there is any electromagnetic interference upon the
equipment, whether the operating temperature of the equipment is normal and whether the
equipment is well grounded.
(2) If the performance event is reported accompanying the reporting of the alarm,
regeneration section and multiplex section bit errors, please remove other alarms and
performance events according to the priority.

Remarks


4-65

HPFEBBE
Item Description
Performance event
name.
HPFEBBE
Full name HP Far-End Background Block Error
background block error is the block in which one or more bits are in error during
transmission. The far-end background block error refers to the error detected at the far-end.


Remarks


4-66

HPFEES
Item Description
Performance event
name.
HPFEES
Full name HP Far-End Errored Second
defect. The far-end errored second means the bit error detected at the far-end.

equipment factors. Please check whether there is any electromagnetic interference upon
the equipment, whether the operating temperature of the equipment is normal and whether
the equipment is well grounded.
(2) If the performance event is reported accompanying the alarm, regeneration section and
multiplex section bit errors, please remove other alarms and performance events according
to the priority.



4-67

HPFESES
Item Description
Performance
event name.
HPFESES
Full name HP Far-End Severely Errored Second
severely errored second is the one-second period which contains 30% errored blocks. The
far-end bit error refers to the error detected at the far-end.

grounded.
(2) If the performance event is reported accompanying the reporting of the alarm, regeneration
(4) Check whether the receiving optical power is normal;



4-68

HPSES
Item Description
Performance event
name.
HPSES
Full name HP Severely Errored Second

Treatments (1) Check whether there is any electromagnetic interference upon the equipment, whether
grounded.



4-69

HPUAS
Item Description
Performance event
name.
HPUAS
Full name HP Unavailable Second
unavailable second is a period of unavailable time begins at the onset of ten consecutive
severely errored seconds. In this case the service is interrupted and the corresponding
alarm is generated until the fault is removed.
grounded.



4-70

LPBBE
Item Description
Performance event
name.
LPBBE
Full name LP Background Block Error
Causes The lower order bit error refers to the error generated when detecting V5 byte. The
transmission.




4-71

LPCSES
Item Description
Performance event
name.
LPCSES
Full name LP Consecutive Severely Errored Second
Causes The lower order path bit error refers to the error generated when detecting V5 byte. The
(7) Tributary board fault
grounded.
(2) If the performance event is reported accompanying the reporting of the alarm, and
regeneration section, multiplex section and higher order path bit errors, please remove other
alarms and performance events according to the priority.



4-72

LPES
Item Description
Performance event
name.
LPES
Full name LP Errored Second
defect.




4-73

LPFEBBE
Item Description
Performance
event name.
LPFEBBE
Full name LP Far-End Background Block Error
background block error is the block in which one or more bits are in error during transmission.
The far-end background block error refers to the error detected at the far-end.

grounded.



4-74

LPFECSES
Item Description
Performance event
name.
LPFECSES
Full name LP Far-End Consecutive Severely Errored Second
The far-end bit error refers to the error detected at the far-end.

grounded.
(2) If the performance event is reported accompanying the reporting of the alarm and



4-75

LPFEES
Item Description
Performance
event name.
LPFEES
Full name LP Far-End Errored Second
errored second is a one second period with one or more errored blocks or at least one defect.

grounded.
(2) If the performance event is reported accompanying the reporting if the alarm, regeneration



4-76

LPFESES
Item Description
Performance event
name.
LPFESES
Full name LP Far-End Severely Errored Second

grounded.
regeneration section, multiplex section and higher order path bit errors, please remove
other alarms and performance events according to the priority.



4-77

LPSES
Item Description
Performance event
name.
LPSES
Full name LP Severely Errored Second

grounded.



4-78

LPUAS
Item Description
Performance
event name.
LPUAS
Full name LP Unavailable Second
Causes The lower order path bit error is the error generated when detecting V5 byte. The unavailable
second is a period of unavailable time begins at the onset of ten consecutive severely errored
seconds. In this case the service is interrupted and the corresponding alarm is generated until
the fault is removed.

grounded.



4-79

MSBBE
Item Description
Performance event
name.
MSBBE
Full name MS Background Block Error
Causes The multiplex section bit error refers to the error generated when detecting B2 byte. The
transmission.
(2) Fiber performance fault;

regeneration section bit error, please remove other alarms and performance events
(4) Replace the faulty unit with a new one.



4-80

MSCSES
Item Description
Performance event
name.
MSCSES
Full name MS Consecutive Severely Errored Second
Generally, the consecutive severely errored second will be accompanied by the B2_OVER
alarm, and the service may be interrupted.

grounded.
regeneration section bit errors, please remove other alarms and performance event
(4) Check whether the clock configuration is correct.



4-81

MSES
Item Description
Performance event
name.
MSES
Full name MS Errored Second
defect.

equipment factors. Please check whether there is any electromagnetic interference upon the
regeneration section bit errors, please remove other alarms and performance events



4-82

MSFEBBE
Item Description
Performance event
name.
MSFEBBE
Full name MS Far-End Background Block Error
transmission. The far-end background block error refers to the error detected at the far-end.

regeneration section bit error, please remove other alarms and performance events



4-83

MSFECSES
Item Description
Performance event
name.
MSFECSES
Full name MS Far-End Consecutive Severely Errored Second
alarm, and the service may be interrupted. The far-end bit error refers to the error detected
at the far-end.

grounded.



4-84

MSFEES
Item Description
Performance event
name.
MSFEES
Full name MS Far-End Errored Second
defect. The far-end bit error refers to the error detected at the far-end.




4-85

MSFESES
Item Description
Performance event
name.
MSFESES
Full name MS Far-End Severely Errored Second
alarm, and the service may be interrupted. The far-end bit error refers to the error detected
at the far-end.

grounded.



4-86

MSSES
Item Description
Performance event
name.
MSSES
Full name MS Severely Errored Second

grounded.
(2) If the performance event is associated alarm and regeneration section bit error report,
please solve other alarms and performance event according to the priority.



4-87

MSUAS
Item Description
Performance event
name.
MSUAS
Full name MS Unavailable Second
unavailable second is a period of unavailable time begins at the onset of ten consecutive
severely errored seconds. In this case the service is interrupted and the corresponding
alarm is generated until the fault is removed.

grounded.



4-88

RSBBE
Item Description
Performance event
name
RSBBE
Full name RS Background Block Error
Causes The regeneration section bit error refers to error generated when detecting B1 byte. The
transmission.




4-89

RSCSES
Item Description
Performance event
name.
RSCSES
Full name RS Consecutive Severely Errored Second
Causes The regeneration section bit error refers to the error generated when detecting B1 byte. The
alarm, and the service may be interrupted.

grounded.



4-90

RSES
Item Description
Performance event
name.
RSES
Full name RS Errored Second
defect.




4-91

RSOFS
Item Description
Performance event
name.
RSOFS
Full name RS Out-of-Frame Second
Out-of-Frame (OOF) means the loss of the frame alignment byte and the OOF second refers
to the second in which at least one OOF occurs. After lasting 3ms, the OOF will become the
Loss of Frame (LOF).




4-92

RSOOF
Item Description
Performance event
name.
RSOOF
Full name RS Out of Frame
OOF refers to the loss of the frame alignment byte and the count of the OOF refers to the
occurrence times of the OOF. After lasting 3ms, the OOF will become the LOF.


Remarks


4-93

RSSES
Item Description
Performance event
name.
RSSES
Full name RS Severely Errored Second
Causes The regeneration section bit error refers to the error generated when detecting B1 byte.
The severely errored second is the one-second period which contains 30% errored
blocks.

grounded.



4-94

RSUAS
Item Description
Performance event
name.
RSUAS
Full name RS Unavailable Second
Causes The regeneration section bit error refers to the error generated when detecting B1 byte.
The unavailable second is a period of unavailable time begins at the onset of ten
consecutive severely errored seconds. In this case the service is interrupted and the
corresponding alarm is generated until the fault is removed.

grounded.


OptiX Metro 500 MM

5-1

5 Basic Thoughts and Methods for
Fault Locating

This chapter describes the basic thoughts and methods for fault locating.
5.1 Requirements for Maintenance
Staff
In telecommunication the service interruption means revenue loss. This put much
pressure on maintenance staff to locate faults quickly and clear them as soon as
possible. The following are some important tips for maintenance personnel.
5.1.1 Professional Skills
1. Be familiar with SDH fundamentals
2. Be familiar with alarm generation mechanism and signal flow in
transmission system
For details, refer to chapter 4.
5

Basic Thoughts and Methods for Fault Locating OptiX Metro 500 MM

5-2

3. Be familiar with common alarms
(1) SDH line alarms
R_LOS
R_LOF
R_OOF
AU_AIS
AU_LOP
MS_AIS
MS_RDI
B1_EXC
B2_EXC
(2) PDH tributary alarms
HP_LOM
HP_SLM
HP_TIM
HP_UNEQ
TU_AIS
TU_LOP
T_ALOS
T_DLOS
P_LOS
EXT_LOS
UP_E1_AIS
LP_RDI
LP_SLM
LP_TIM
LP_UNEQ
B3_EXC
(3) Protection switching alarms
PS


5-3

(4) Clock alarms
LTI
SYNC_C_LOS
SYN_BAD
(5) Equipment alarms
POWER_FAIL
FAN_FAIL
BD_STATUS
4. Be expert in transmission equipment handling
For details, refer to NMS Operation Manual.
5. Be familiar with the basic maintenance instruments and tools
A maintenance personnel should know how to operate various maintenance
instruments, including 2M BER tester, optical power meter, SDH analyzer,
oscilloscope, multimeter, etc. For the usage, see their respective user manuals.
5.1.2 Aware of Network Layout
Maintenance personnel should have the complete knowledge of his office network,
power supply, power cable layouts, ODF cabling, DDF cabling, boards type &
version and the equipment location in the equipment room. He should maintain the
inventory list and make sure that important components always have spares.
5.1.3 Collecting and Storing On-site Data
Before fault processing, maintenance personnel should first collect and store the
on-site data. It is a very important task. The detailed on-site data is very useful in
finding the fault reason. The main data to be collected and stored includes the
system alarm & performance data, the configuration & running states of respective
NEs and boards, operation log of the NMS, etc. In addition, maintenance personnel
should make operation log and record manually, respective operation procedures
during troubleshooting. These log reports with complete fault analysis can be used
as reference cases for future problems.


5-4

5.2 Basic Principles of Fault Locating
During fault locating of transmission equipment, locate the fault in a single station
precisely.
The general principles of troubleshooting can be summarized as: "external first,
then transmission; network first, then NE; high-speed section first, then
low-speed section; and higher order first, then lower order".
5.2.1 External First, then Transmission
During fault localization, first confirm that external conditions are normal, e.g. line
optical fiber is correct or there should be no power failure or switching equipment
fault, etc.
5.2.2 Network First, then NE
First analyze the fault in the protocol of the network, then precisely locate the fault to
an NE.
5.2.3 High-speed Section First, then Low-speed
One
From the alarm signal flow, we can see that the alarms of the high-speed signals
usually cause those of the low-speed signals. Therefore, when you locat faults, first
clear the faults of the high-speed section.
5.2.4 Higher Order Alarms First, then Lower
Order Alarms
Always handle critical alarms first, so that the service can be maintained. Then go for
major and minor alarm removal, respectively.


5-5

5.3 Common Methods of Fault
Locating
The common methods and general procedures of fault locating of the OptiX Metro
500 can be summarized as firstly analysis, secondly loopback and then board
replacement.
That is, when the fault occurs, first determine the possible faulty points by analyzing
the alarm events, performance data and signal flow. Then locate the fault on the
particular NE by looping back station by station. Finally, clear the fault by replacing
faulty board.
To assist the maintenance personnel, the following are some methods to locate a
fault in an optical transmission network.


5-6

Table 5-1 Common faults handling
Methods Application Features
Alarm and performance
analysis
Universal 1. Evaluate the whole network situation.
2. Can locate the faulty point preliminarily based
on the collected data
3. Cause no negative effect on normal services
4. Depend on the NMS
Loopback Locate the fault to a single station
or board
1. Independent of alarm and performance event
analysis
2. Rapid and effective
3. May affect the ECC and normal services
Replacement Locate the fault to a board or
isolate external faults
1. Convenient
2. Require spare parts/equipment
3. Applied with other methods
Configuration data
analysis
Locate the fault to a single station
or board
1. Can find the fault cause
2. Fault locating time is longer
Configuration
modification
Locate the fault to a board 1. Have a high risk
Meter test Isolate external faults and resolve
interconnectivity problem
1. A general method, with high accuracy
2. Have certain requirements for the meters
3. Applied with other methods
Experience Special cases 1. Fast fault handling
2. High probability of mistake
3. Need experience accumulation

5.3.1 Alarm and Performance Analysis
In SDH frame, there are abundant overhead bytes, which carry system alarms and
performance information. Therefore, a number of alarm and performance events will
be generated, when the SDH system fails
Alarm and performance data analysis is used to get accurate and timely overall fault


5-7

information. The fault information either can be obtained by data queries from the
NMS or from the board & cabinet indicators flashing. Both methods have
advantages and disadvantages, which are discussed in the following section.
1. Alarm and performance query through the NMS
The NMS monitors and manages the running states of the transmission equipment.
The fault information acquired through the NMS is comprehensive. The fault
information is also accurate. Through the obtained information, one can know the
alarm category, alarm history, etc.
Aided with graphic display, maintenance personnel can quickly locate the fault
on its occurrence. However, this method fully depends on the normal
operations of computer, software and communication. Once any one is faulty,
the capability of obtaining fault information in this way will be greatly
decreased, and even lost completely.
For further understanding, consider a chain network, as illustrated in Figure 5-1. The
NMS computer is attached with NE 1.
w w w w e e
NE1
NE2 NE3 NE4
NMS

Figure 5-1 The OptiX Metro 500 chain network

Suppose E1 service between NE 1 and NE 4 is interrupted. NE 4 cannot be
accessed from NE 1. Meanwhile, there are MS_RDI and HP_RDI alarms at
eastbound optical board of NE 3. Also, LP_RDI alarm is displayed corresponding to
the service between NE 1 and NE 4.
After analyzing the alarms, it is observed that the signals from NE 3 have not been
correctly received at NE 4, while NE 3 can correctly receive the signals from NE 4.
The potential problems may be:
Disturbance in NE3 signal transmission.
Broken optical fiber or connectors.
Disturbance in NE 4 signal receiver.


5-8

Note:
When obtaining the alarm or performance information via the NMS, ensure that all
NEs are set correctly. Otherwise, the alarm and performance information may be
incorrect or some time even nothing is received.
During the maintenance, special attention should be paid to setting the NE time at
current time. Otherwise, the NE will work at the default time, which is not the current
time.

2. Obtaining the alarm information through the equipment indicators to
locate faults
There are various running and alarm indicators with different colors and flashing
times, in the OptiX Metro 500 system. On/Off and flashing states of these indicators,
indicate the status or possible alarms in particular equipment.
Table 5-2 indicators
Silkscreen Description Remarks
RUN Running indicator Dark : OptiX Metro 500 is not powered
Flash per 0.5 second : waiting for loading
software
Quick Flash : loading software
Slow flash : running normally
CRT critical alarm
indicator
Dark :no critical alarm
Light :critical alarm
MAJ Major alarm
indicator
Dark : no major alarm
Light : major alarm
los Optical interface
indicator

3. Comparison between above two methods
From the above descriptions, it is obvious that either method has its advantages and
disadvantages. Through the NMS, one can know the overall running status of the
equipment. He can also conveniently locate the fault of specific equipment.
Through indicators, one can have direct access to the equipment. It is helpful in
on-site maintenance.


5-9

In practice, both methods are supporting each other and used during fault locating.
In case of serious faults, NMS and on-site maintenance staff cooperate and work
jointly to resume the system in minimum outage time.
The comparison between these two methods is shown in Table 5-3.
Table 5-3 A comparison between maintenance through the NMS and through board
indicators
Item
Network management
system
Indicator
Main user NMS maintenance personnel Equipment maintenance
personnel
Function Central source Assist NMS staff
Alarm information Entire network alarms and
performance
Only local NE alarms and
status
Alarm history Available Unavailable
Alarm Time Determined Can not be known
Performance event Determined Can not be known
Computer, software,
and communication
Fully dependent Independent

4. Limitation of alarm and performance analysis
Sometimes service and the fault information is complicated, a number of alarms and
performance events will be generated if the faults occur. This may cause difficulty for
maintenance personnel to perform analysis.
5.3.2 Loopback
Loopback is the most popular and most effective method to locate faults in an SDH
transmission network. The most significant feature of this method is, there is no
need of thorough data and performance analysis. This saves time in debugging
faults and reduces the outage time.
Warning:
Loopback affects the normal traffic. It is recommended only when there is complete
failure of services or during off-peak hours.

A user cans loopback the system either by software or through hardware.


5-10

Compared with software loopback, hardware loopback is more reliable.
However, hardware loopback always needs on-site physical presence. In
addition, the overload of the receiving optical power should be considered
during the operation.
Software loopback is easier but less reliable than hardware loopback. For
example, during single station testing, an optical boards normal running can
not be determined through software loopback (inloop on the optical port). The
optical board is tested by hardware loopback (optical fiber jumper is
connected with transmitter and receiver of the optical board).
1. Provisions of software loopback in the OptiX Metro 500
Provisions of software loopbacks at different levels, with respect to boards are
enlisted in Table 5-4. Here note that, all kind of software loopbacks are given by the
NMS.
Table 5-4 Software loopback offered by the OptiX Metro 500
Board involved Loopback options Loopback level Application
Tributary board Inloop/ outloop Loopback at path level Separates switching faults from
transmission faults. Roughly determines
the tributary board failure. Not necessary
to modify service configuration.
Line board Inloop/ outloop Loopback at VC-4
level or whole STM-N
level
Locates single station faults. Roughly
determines the line board failure. No need
to modify service configuration.
Cross-connect
board
Line loopback,
tributary loop-back
Loopback at service
path level
Determines whether line or tributary side is
faulty in a specific faulty station.
Requires much professional knowledge,
and service configuration needs to be
modified.

The line and tributary board loopbacks are widely used because they can locate a
fault to a single station and can roughly determine if a line or tributary board is faulty.
So the maintenance personnel are required to be skilled in it.


5-11

Warning:
Some line boards in the OptiX transmission system support the VC-4-level software
loopback. And some support the software loopback only at STM-N level.
During loopback of the whole STM-N in a remote station, the ECC communication
may be interrupted. Also, it may be interrupted if looping back the first VC-4. So, be
cautious during this operation.
Remember ECC is responsible for the communication between NMS and NE. Once
it is interrupted, the loopback only can be cleared only from the remote station to
recover the ECC communication. This delays the troubleshooting and prolongs the
outage time.
In a chain network, the NMS has only a single path to access an NE, i.e. no backup
path available. However, in a ring network, NMS can access an NE from two
available paths. If one ECC fails, NMS can access the NE from other ECC.
Therefore, be careful during software loopback of the line board in a chain network.
However, in a ring network there is no problem in performing software loopback for
the line board. Note that, a ring network is considered to be a chain network, if
optical fiber is broken between any two NEs of the ring.

Note:
Figure 5-2 shows how the software loop-back affects the ECC communication. In
this figure, NE 2 and NE 3 are the remote stations for the NMS. If westbound (W)
board of NE2 is looped-back, the ECC between NE 2 and NE 1 will be interrupted,
and the NMS will lose the control on NE 2, i.e. the remaining network is also out of
access. If eastbound (E) board of NE2 is looped-back, the ECC will not be
interrupted and NE2 will be still accessible.

W
E W E W
NE1 X X
NE2
NE3
NMS

Figure 5-2 Effect on the ECC communication caused by the software loopback

The cross-connect board loopback can be used to determine whether the fault of the


5-12

station occurs at the line side, or the tributary side, or the cross-connect side. The
failure side of line board can be also determined by this loopback. However, the
cross-connect board loopback is seldom used due to its complications.
Tips:
The simplest way to perform cross-connect board loopback is to configure a
loopback for a line or tributary board via the NMS. For service recovery, first make
service backup prior to performing loopback.

2. Procedures
Before loopback, one should determine about path and timeslot, which will be
looped-back. Also make sure, which kind of loopback will be used, i.e. inloop or
outloop?
Following steps are recommended during software loopback:
Step 1: Select service path for loopback.
From collected alarm and performance data select faulty service path as an object.
Tips:
Usually services failed simultaneously, are related to each other. Thus, once one of
them is recovered, others are also recovered subsequently. In addition, the principle
of simplified sampling makes the fault analysis and handling easy. Especially, it is
more effective in case the faulty service is very complicated.

The process of simplifying the sampling of service path for loopback is:
(1) Select one of the faulty stations.
(2) Select one of the faulty service paths of the selected station. Since self-loop
of the first VC-4 affects the ECC, dont select the first VC-4 for loopback.
(3) First analyze the service in one direction of the selected service path.
Step 2: Draw the complete loopback path
Draw the complete loopback path, in which all the NEs in between are clearly
showed. Mark the source and sink of this service, VC-4 number and timeslots it
occupied.
Step 3: Now loopback each section, step-by-step until faulty NE is located.
Step 4: Locate the faulty board


5-13

After locating the faulty NE, further locate the possible faulty boards by looping-back
the line, tributary or cross-connect boards. Confirm the faulty board by applying other
test methods. Finally, replace the faulty board.
3. Example
Let us use Figure 5-1 again. Figure 5-1 shows a chain network with four OptiX Metro
500 NEs. Figure 5-3 is the timeslot allocation of these NEs.
NE1
1
VC-4
E
NE
Time
slot
W
NE2
t1:1-16
1-16
t2:1-16
E W
17-32
E W
t1:1-16
33-48
E W
t1:1-16
t1:1-16
t3:1-16
NE3 NE4
2
VC-4
3
VC-4
4
VC-4

Figure 5-3 Timeslot allocation diagram

In the figure above, there are four VC-4s available. The network uses the service of
two VC-4s. t1, t2, and t3 represent the 2M tributary board in slots 1, 2, and 3 in NE 1.
The number 1-16 along with tributary board number (e.g. t1) represents the 2M
number. The numbers above the transverse lines indicate the timeslot number of the
VC-4 occupied. For example, consider NE 1 and third transverse line, t3: 1-16
shows 2M paths 1-16 of the tributary board in slot 3 of NE 1. The 33-48 indicates,
the timeslots occupied by the second VC-4. The service distribution from this
diagram is:
(1) The 2M paths 1-16 of the tributary board in slot 1 of NE 1 are connected
with 2M paths 1-16 of the tributary board in slot 1 of NE 2. The timeslots
1-16 of the first VC-4 carry the service between them.
with 2M paths 1-16 of the tributary board in slot 1 of NE3. The timeslots
17-32 of the second VC-4 carry the service between them.
with 2M paths 1-16 of the tributary board in slot 1 of NE4. The timeslots
33-48 of the second VC-4 carry the service between them.


5-14

Suppose NE 1 could not communicate with any other NE. Let us apply our recently
discussed loopback to handle this fault:
Step 1: Select the interrupted service for analysis
(1) Services between NE 1 and NEs 2, 3, and 4 are interrupted. Select the
service of NE 3 for analysis.
(2) There are 16 interrupted services in NE 3. Select the first 2M service of the
t1 tributary board for analysis.
(3) First analyze the service from NE 1 to NE 3.
Step 2: Draw a complete path from NE 1 to NE 3 including intermediate stations.
From the timeslot allocation diagram, we can see that the source of the selected
interrupted service is t2:1 of NE 1, i.e. the first 2M path of the second tributary board.
It occupies the 17th 2M timeslot of the second VC-4, and takes NE 2 as the
intermediate station. The sink of the service is t1: 1 of NE 3. Thus, the service path
diagram will be as shown in Figure 5-4.
NMS
NE1
w2:17 w2:17 w2:17 e2:17
t2:1 t1:1
NE2 NE3

Figure 5-4 Loopback path from NE 1 to NE 3

Step 3: Perform loopback section by section to locate the faulty NE.
According to Figure 5-4, connect a 2M BER tester to the first 2M path of the second
tributary board of NE 1.
Tips:
If you are familiar with the alarm signal flow, you can also determine the service from
alarm status. Generally, when the service is recovered many alarms will vanish.
When service interruption happens many alarms will occur.

Then, perform the following operations in turn (note that you must cancel previous
loopback before starting the next):
Inloop the second VC-4 of the westbound optical board of NE 1. Observe the
2M BER tester reading. If the reading is normal, then the fault is not in NE 1
and move to the next step. Otherwise, the fault is in NE 1.
Remove the inloop, and make outloop for the second VC-4 of the westbound
optical board in NE 2. Observe the 2M BER tester reading. If the reading is


5-15

normal, then the fault is not in fibers between NE 1 and NE 2 and move to the
next step. Otherwise, the fault is in this section.
Remove the outloop and make inloop from the second VC-4 of the eastbound
optical board of NE 2. Observe the 2M BER tester reading. If the reading is
normal then the fault is not in NE 2 and move to the next step. Otherwise, the
fault is in NE 2.
Remove the inloop from NE 2 and make outloop from the second VC-4 of the
westbound optical board of NE 3. Observe the 2M BER tester reading. If the reading
is normal, then fibers between NE 2 and NE 3 are normal and the fault must be in
NE 3. Otherwise, the fault is in this section.
Tips:
When there are many NEs in a chain network, the dichotomy can be adopted for
loopback, so as to locate the fault quickly. That is, perform the loopback on one NE
located in the middle of the network first, thus locating the faulty point to the first half
or the second half of the network.

4. Summary
From above discussion we realize that, loopback does not require much time in
alarm and performance analysis, and through it one can locate the faulty NE or
board quickly. However, path loopback temporarily interrupts the normal service,
which is not affordable in a live network. Therefore, as a general rule, loopback is
used only when service is interrupted or major faults occur. Remember again, when
the first VC-4 path of the line is looped back, the ECC communication among NEs
may be affected.
5.3.3 Replacement
1. Overview
In this method, an abnormal article is replaced with normal article. If the problem
persists, then it means that particular article is not faulty and there may be some
other problems. Here, the article might be a section of fiber, a board, a flange or an
attenuator.
2. Application
Replacement method is applicable in handling the problems of external equipment,
such as optical fiber, flange, accessed SDH equipment, and power supply
equipment, etc. It is also used to remove the problem in the board or module in the
single station.


5-16

3. Example
Let us go back to our favorite Figure 5-1. This time, consider the service between
NE 3 and NE 4 is interrupted completely. The doubt is, optical fibers between the
transmit end of NE 3 and the receive end of NE 4 are abnormal. Interchange the
receiving and transmitting fibers between them. After the interchange, if the R_LOS
alarm is generated at the receive end of the eastbound optical board of NE 3, it
means optical fibers are faulty. However, if the fault still persists, then the optical
board is faulty.
To confirm the faulty board, apply this method again and replace the eastbound
board of NE 3 with the new one.
If the alarm still persists, then replace the westbound board of NE 4 with a new one.
This time the alarm should be removed.
Similarly, if there is T_ALOS alarm on 2M path of the tributary board. The
possibilities are that the external switch or trunk cable is faulty. Interchange this path
with a normal one. After the interchange, if the T_ALOS alarm has been shifted, it
indicates the external trunk cable or the external switch is faulty and the transmission
equipment is normal. If the T_ALOS alarm persists, then there should be fault in
transmission network, either in the board or in the connector, etc.
By applying this method, we can also solve other problems such as power supply
and grounding.
4. Summary
This method requires the least skill. It is easy for the maintenance personnel to
grasp, and thus it is very practical. However, this method requires spare parts. Also
extra care is required during its application. For example, wrong handling of the
board or component during replacement, may cause the damages and lead to
another fault.
5.3.4 Configuration Data Analysis
1. Overview
Some times sudden change in ambient conditions or improper operations, may
change or damage the configuration data (e.g. NE and board data) of the equipment.
This can affect the services. In this case, after locating the fault to a single station,
we can further locate the fault by analyzing the configuration data
2. Application
Locate the fault by querying and analyzing the current configuration data of the
equipment. The configuration data includes: logical system and its attributes, node
parameters of the multiplex section, path loopback setting of the line and tributary
boards, protection attributes of the tributary path, path trace byte, etc.


5-17

If the path protection of a tributary board does not work, we should check if the
protection at the tributary level is enabled.
Any improper operation from the NMS can be verified from the operation log.
3. Summary
This method is applicable to the further analysis of a known faulty station. It can help
in finding the original causes of a fault. However, this is a time-consuming method.
This method requires much expertise and knowledge in the field of optical
transmission. Of course, product knowledge is essential.
5.3.5 Configuration Modification
1. Overview
In this method, we modify the timeslot configuration, slot configuration, board
parameter configuration, and so on. It is applied to remove problems which are
caused by configuration errors in a known faulty station. In addition, the typical
application of this method is to eliminate the problem of pointer justification.
2. Application
If there is doubt that some paths of a certain tributary board become faulty, or a
certain tributary board may be wrong, we can clear this doubt by modifying timeslot
configuration. In this way, we can shift this payload to other tributary board or paths.
Similarly, we can shift the traffic over one VC-4 to another. If a certain slot becomes
faulty, then we can change the slot configuration. Moreover, loopback of the
cross-connect board is also considered one of the applications of this method.
During the upgrade or expansion, if you doubt the new configuration is not correct,
you can re-load the original configuration for confirmation.
However, we notice that modifying the timeslot configuration is not helpful in locating
the faulty point or board (e.g. a line board, cross-connect board or backplane). In this
case, apply the replacement method to further locate the fault. Therefore, this
method is applicable to the preliminary fault locating when there is no spare board
available. Also, other service paths or slots shall be used to resume the service
temporarily.
To solve the pointer justification problem by modifying configuration, modify the
tracing direction and reference source of the clock.
3. Summary
This method is not convenient and efficient for the maintenance personnel. It is
usually used to resume the service temporarily when there is no spare board
available for replacement, or used to handle the pointer justification problem. In
addition, before you apply this method, save the original configuration. Meanwhile,


5-18

record carefully the steps executed, to facilitate the fault locating.
Note:
For the multiplex section protection ring, modifying the service configuration in
switching may pause the multiplex section protocol, which will interrupt the services.

5.3.6 Meter Test
1. Overview
This method is usually applied to clear the external problems or to locate the
interconnectivity problems.
2. Application
If there is doubt that power supply is abnormal, then use a multimeter to measure
the input voltages. If you suspect that the poor interconnectivity between the
transmission equipment and other equipment is due to the grounding, then use
multimeter to measure the voltage between the shielding layer of coaxial ports of the
transmitter and receiver of the interconnection path. If the voltage value exceeds
0.5V, then there is some problem with grounding. If you doubt that the poor
interconnectivity is due to the incorrect signal, you can use appropriate analyzers to
observe whether the frame signals are normal, whether the overhead bytes are
normal, and whether there is any alarms.
3. Summary
This method provides highly accurate results. However, this method rather depends
on meters and professional knowledge.
5.3.7 Experience
1. Overview
Some time a running board enters in abnormal state because of transient power
supply behavior, low voltage or strong external electromagnetic interference, etc.
Service and ECC communication interruption, might be or might not be
accompanied with corresponding alarms. The configuration data might also be
correct. In this case, the fault can be cleared and the normal service can be resumed
in time by board reset or board swapping. Sometimes give power reset to the
subrack or re-send the system configurations.


5-19

2. Summary
The main disadvantage of this method is uncertainty, because the problem is not
fully known and there is probability that the alarm persists after board or even power
reset. This method is not recommended.
5.3.8 Comparison of Fault Locating Methods
Table 5-5shows the comparison between these methods. In practice, the
maintenance personnel usually need to apply more than one method to locate and
clear the faults.
Table 5-5 Comparison between various fault locating methods
Methods Application Features
Skills
requirement
Configuration
data analysis
Locate the fault to a board Can find out the causes of fault. Need
more time for fault locating.
Highest
Alarm and
performance
analysis
Universal Evaluate the situation as a whole. Can
foresee latent dangers of equipment. Do
not affect services
High
Configuration
modification
Locate the faulty point to the
board. Can solve the pointer
justification problem.
Operation is complicated. May affect
services
More
Meter test Isolate external faults. Solve the
problem of poor
interconnection.
Accurate. Require meters. More
Loopback Locate the fault to a single
station or isolate external faults
Independent of analysis of alarms and
performance events. May affect ECC
and normal service
Less
Replacement Locate the fault to a single
station or isolate external faults
Simple, but need spares Low
Experience Special cases Simple Least


5-20

5.4 Some Classified Fauts & their
Troubleshooting
The troubleshooting procedures of transmission equipment are basically the same. It
does not matter which type of the fault it is. That is, first start from the external
equipment, then locate the faulty station. After that, localize the fault to the board or
component for the final solution.
5.4.1 External Faults Handling
Before locating faults of the transmission equipment, first eliminate the external faults
like, grounding, optical fibers, trunk cables, external switch, power failure, etc.
1. Troubleshooting of external switch fault
Method 1: Self-loop the switch trunk interface. If the switch trunk board is abnormal
after self-looping the trunk interface, it can be determined that the switch fails.
Otherwise, something is wrong with the transmission equipment.
Method 2: Loopback the accessed 2M/34M/140M service path of transmission
equipment as shown in Figure 5-5. If alarm indications disappear from the tributary
unit, it means that the transmission equipment is normal. That is, external switch is
abnormal. Ask the concerned switch staff to assist you in the fault removal.
SDH NE
Switch
Meter
Line
Tributary
A B
Tributary
SDH NE

Figure 5-5 Looping back the PDH interface

Select a faulty service path in station A and attach a BER tester with it.. Loopback
the corresponding path of the tributary board of NE B. This loopback will isolate the
external switch. Check the BER tester reading, if the reading is normal, it means the
service is normal and transmission equipment is ok. If the BER tester shows some
errors, then it means the fault is in transmission equipment. Check carefully the
tributary and line boards according to the above-described methods.


5-21

2. Troubleshooting of optical fiber fault
When there is R_LOS alarm displayed in the NMS and the red indicator of the line
board flashes 3 times per second, it simply means communication path is
interrupted and something wrong with either board or optical fiber happens. To
further determine whether the problem lies in the board or in the optical fiber, the
following methods are used.
Method 1: Use the OTDR to check the optical fiber continuity. By analyzing the line
attenuation curve displayed on the analyzer, we can approximate the optical fiber
breaking point. If there is no such point, it means optical fiber is perfect.
Method 2: Measure the transmitting and receiving optical power of the optical board
at the both ends of the optical fiber. Compare these values, if the transmitting optical
power of opposite end optical board is normal while the receiving optical power of
this end is abnormal, then the optical fiber is faulty. If the transmitting optical power of
the optical board is very low, then the optical board is faulty.
Method 3: Check the transmitting optical power. If it is normal, then it means the fault
is after this point. Now hardware loopback the board, by connecting transmit port
and receive port of the board with fiber jumper. Make sure that, an attenuator is
attached in between, to avoid any optical power overload. If the alarm indicator of
the board is still flashing, then the board is faulty. Otherwise, similarly check the
corresponding opposite board. If both boards are right, then there must be problem
in optical fiber.
Method 4: Use the replacement method. Use a piece of normal fiber to replace that
suspected to be faulty to judge whether the problem is with optical fiber.
As to ADM stations in a ring network, the eastbound optical board of this station
should be connected to the westbound optical board of the next station, and the
connection of other stations shall follow this rule. As to ADM stations in a chain
network, the connection of the optical fibers should be made according to a specified
direction. The eastbound optical board of this station should be connected to the
westbound optical board of the next station. When the optical fibers are connected
improperly, a great amount of pointer justification events will be generated. For
further localization the following methods can be adopted.
Method 1: Judge the fiber connection by drawing out fibers, shutting down the laser,
etc. Note that this method will negatively affect the service.
Method 2: fulfill the judgement by inserting the MS_RDI alarm via the NMS. This
method will not affect the service, and is recommended.
Method 3: modify the trace byte J1 of the higher order path via the NMS. Modifying
the trace byte may negatively affect the service. Be cautious of doing it.
The above mentioned three methods fulfill the analysis by observing whether the
corresponding optical board of the adjacent station reports the correct alarms. For
the method 1, the R_LOS alarm shall be reported when the corresponding optical
board of the adjacent station cannot receive optical signals. For the method 2, the
corresponding optical board of the adjacent station shall report the MS_RDI alarm.
For the method 3, the HP_TIM alarm shall be reported by the corresponding optical


5-22

board of the adjacent station. If you can not find the appropriate alarms reported
from the corresponding optical board of the adjacent station, but another optical
board in the adjacent station reports the alarm, then that usually means the fiber
mis-connection.
3. Troubleshooting of trunk cable fault
Before looping-back the switch, let us remember the troubleshooting of external
switch fault. We decide that transmission equipment is normal and after checking,
the switching staff claims that switch equipment is also normal. Then what can be
the possibility? Sure, the media between transmission and switch equipment is faulty,
i.e. trunk cable or DDF connections. In case of cable blocking or poor-connection, an
alarm can be observed on the corresponding path of the tributary board. In this case,
you can use wire-matching method to determine whether the cable is connected
properly. Also, to confirm the fault, interchange the trunk cables and observe the
behavior. If the alarm is shifted along the trunk cable, it indicates that the fault is in
trunk cable.
4. Troubleshooting of power supply fault
If an NE is not accessible and the R_LOS alarm is reported from the related optical
board, then the power supply of this station may fail. If this station makes a sudden
shift from normal operation to abnormal state, such as failure of path switching or
multiplex section switching, abnormality of some boards, service interruption,
abnormal login, etc., then concentrate on its power. Check if the power supply
voltage of the transmission equipment is too low, or if there is instantaneous voltage
fluctuation.
5. Troubleshooting of grounding fault
If the equipment is struck by lightning or can not be interconnected you need to
check whether the grounding is correct. First check if the grounding is in line with the
standards, if any equipment is not grounded together, and if the grounding of
equipment in the same room is consistent. Then use meters to measure grounding
resistance and voltage difference between working ground and protection ground,
and check if they are within the range allowed.
5.4.2 Localizing Fault to a Single Station
In fault handling, the most important step is localizing fault to a single station. For this,
the popular method is loopback. That is, perform either inloop or outloop to check
the faulty NE, station by station. The other efficient method is, alarm and
performance analysis. Generally, with the combination of these two methods, one
can easily you localize fault to a single station.


5-23

5.4.3 Localizing Fault to the Boards
Once faulty NE is recognized, then replacement method is used to further localize
the fault to the board or unit. In addition, the configuration modification, configuration
data analysis, and experience methods are also are commonly used during
debugging. Further fault locating will be introduced in the next chapter, which deals
with the troubleshooting of various common faults. Table 5-6 shows procedures and
common methods of troubleshooting.
Table 5-6 Troubleshooting procedures and methods
Procedures Methods Additional measures
Removing external
faults
Replacement, meter
test, and loopback
Alarm and performance analysis
Localizing fault to a
single station
Loopback Alarm and performance analysis
Localizing fault to the
boards
Replacement Alarm and performance analysis,
configuration modification,
checking configuration data, and
experience


5-24

5.5 Conact Huawei for Assistance
During routine maintenance or fault handling, if you encounter problems that are
hard to handle, contact the customer service center or technical support office of
Huawei. Meanwhile, make the trouble report for Huawei engineer, with the following
information:
Detailed name of the faulty spot
Name and phone number of the contact person
Name and phone number of the contact person on site
Exact time when faults happen
Equipment type and network type
Fault level and expected settlement time
Measures taken and results after faults


5-25

5.6 Obtaining the Latest Technical
Documentation
You can directly get the latest technical documentation from the technical support
web site http://support.huawei.com. Here you can get online information and
assistance.

OptiX Metro 500 MM

A-1

A Abbreviations

Abbreviations Full name
ADM Add/Drop Multiplexer
AIS Alarm Indication Signal
APS Automatic Protection Switching
ATM Asynchronous Transfer Mode
AU Administrative Unit
AU-AIS Administrative Unit - Alarm Indication Signal
AU-LOP Administrative Unit Loss of Pointer
AUG Administrative Unit Group
AUNPJC AU Negative Pointer Justification
AUPPJC AU Positive Pointer Justification
AUP Administration Unit Pointer
BBE Background Block Error
BIP Bit Interleaved Parity
BITS Building Integrated Timing Supply
DCC Data Communication Channel
DDF Digital Distribution Frame

Abbreviations OptiX Metro 500 MM

A-2

DDN Digital Data Network
DNI Dual Node Interconnection
DQDB Distributed Queue Dual Bus
DXC Digital Cross-connection
ECC Embedded Control Channel
EMC Electromagnetic Compatibility
ESD Electronic Static Discharge
FDDI Fiber Distributed Data Interface
GND Ground
GSM Global System for Mobile Communications
GTC General Timeslot Cross-connect Board
HDLC High Digital Link Control
HP-RDI Higher Order Path Remote Defect Indication
HP-REI Higher Order Path Remote Error Indication
HPA Higher Order Path Adaptation
HPC Higher Order Path Connection
HPT Higher Order Path Termination
IC Integrated Circuit
ID Identification
IP Internet Protocol
ISDN Integrated Services Digital Network
ITU-T International Telecommunication Union - Telecommunication
Standardization Sector
LED Light Emitting Diode
LOF Loss Of Frame
LOM Los Of Multiframe
LOP Loss Of Pointer
LOS Loss Of Signal
LPA Lower Order Path Adaptation


A-3

LPC Lower Order Path Connection
LP-REI Lower-order Path Error Indicator
LP-UNEQ Lower-order Path Unequipped
LPT Lower Order Path Termination
LTI Loss of Timing Input
LU Line Unit
MADM Multi Add/Drop Multiplexer
MAN Metropolitan Area Network
MCF Message Communication Function
MS Multiplex Section
MSA Multiplex Section Adaptation
MS-AIS Multiplex Section -Alarm Indication Signal
MS-RDI Multiplex Section-Remote Defect Indication
MSOH Multiplex Section Overhead
MSP Multiplex Section Protection
NE Network Element
OAM Operation Administration and Maintenance
OAM&P Operation Administration and Maintenance & Provisioning
ODF Optical Distribution Frame
OHP Overhead Processing Board
OOF Out Of Frame
PCM Pulse Code Modulation
PDH Plesiochronous Digital Hierarchy
POH Path Overhead
PP Path Protection
PPP Point-to-Point Protocol
PRC Primary Reference Clock
PS Protection Switching


A-4

RDI Remote Defect Indication
REG Regenerator
REI Remote Error Indication
RSBBE Regenerator Section Background Block Error
RSOH Regenerator Section Overhead
OptiX iManager OptiX Series Network Management System for Transmission
Network
SCC System Control & Communication
SD Signal Degrade
SDH Synchronous Digital Hierarchy
SEC SDH Equipment Clock
SEMF Synchronous Equipment Management Function
SETS Synchronous Equipment Timing Physical Interface
SLM Signal Label Mismatch
SNCP Sub-Network Connection Protection
SOH Section Overhead
SSM Synchronous Status Message
SSMB Synchronous Status Message Byte
STG Synchronous Timing Generator
STM-N Synchronous Transport Module Level N
TCP Transport Control Protocol
TDA Tone & Data Access Board
TF Transmit Failure
TIM Trace Identifier Mismatch
TM Terminal Multiplexer
TMN Telecommunications Management Network
TPS Tributary Protection Switching
TU Tributary Unit
TUG Tributary Unit Group


A-5

TUP Tributary Unit Pointer
TUPP Tributary Unit Payload Processing
UART Universal Asynchronous Receiver/Transmitter
UNEQ Unequipped
VC Virtual Container
WTR Wait-to-Restore
XC Cross-Connection

Maintenance Manual

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Maintenance Manual

Uploaded by

Copyright:

Available Formats

1 Maintenance Precautions and Basic Operations 1-1 ......................................

1.1 Maintenance Precautions 1-1 .......................................................................

You might also like