00425665-IDU 610620 Maintenance Guide (V100R002 - 02) PDF

OptiX RTN 600 Radio Transmission System
V100R002
IDU 610/620 Maintenance Guide
Issue
02
Date
2008-6-20
Part Number
00425665
Huawei Proprietary and Confidential

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

Address:
Huawei Industrial Base

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

No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

and other Huawei trademarks are the property of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but the statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.


Contents
Contents
About This Document.....................................................................................................................1
1 Safety Precautions......................................................................................................................1-1
2 Routine Maintenance Guide....................................................................................................2-1
2.1 Routine Maintenance Items.............................................................................................................................2-2
2.1.1 Web LCTBased Routine Maintenance Items.......................................................................................2-2
2.1.2 T2000-Based Routine Maintenance Items.............................................................................................2-3
2.1.3 Field Maintenance Items for Indoor Equipment....................................................................................2-3
2.1.4 Field Maintenance Items for Outdoor Equipment..................................................................................2-4
2.2 Guide to Web LCTBased Routine Maintenance...........................................................................................2-4
2.2.1 Checking the Status of NEs and Boards.................................................................................................2-4
2.2.2 Browsing the Current Alarms................................................................................................................2-5
2.2.3 Browsing the History Alarms.................................................................................................................2-6
2.2.4 Browsing the Abnormal Events.............................................................................................................2-7
2.2.5 Browsing the Current Performance Events of the SDH/PDH................................................................2-7
2.2.6 Browsing the History Performance Events of the SDH/PDH................................................................2-8
2.2.7 Testing the IF 1+1 Switching.................................................................................................................2-9
2.2.8 Testing the IF N+1 Switching..............................................................................................................2-10
2.2.9 Testing the Two-Fiber Bidirectional MSP Ring Switching.................................................................2-11
2.3 Guide to T2000-Based Routine Maintenance...............................................................................................2-12
2.3.1 Checking the Status of NEs and Boards...............................................................................................2-12
2.3.2 Browsing the Current Alarms..............................................................................................................2-13
2.3.3 Browsing the History Alarms...............................................................................................................2-14
2.3.4 Browsing the Abnormal Events...........................................................................................................2-15
2.3.5 Browsing the Current Performance Events of the SDH/PDH..............................................................2-15
2.3.6 Browsing the History Performance Events of the SDH/PDH..............................................................2-16
2.3.7 Testing the IF 1+1 Switching...............................................................................................................2-17
2.3.8 Testing the IF N+1 Switching..............................................................................................................2-18
2.3.9 Testing the Two-Fiber Bidirectional MSP Ring Switching.................................................................2-19
2.4 Guide to Field IDU Maintenance..................................................................................................................2-20
2.4.1 Cleaning the Air Filter..........................................................................................................................2-20
2.4.2 Testing the Orderwire Phone................................................................................................................2-21
2.4.3 Checking the Equipment Room...........................................................................................................2-22
Issue 02 (2008-6-20)

Contents

2.5 Guide to Field Maintenance of Outdoor Equipment.....................................................................................2-22

2.5.1 Checking the ODU...............................................................................................................................2-22
2.5.2 Checking the Hybrid Coupler..............................................................................................................2-23
2.5.3 Checking the Antenna..........................................................................................................................2-24
2.5.4 Checking IF Cables..............................................................................................................................2-24
3 Emergency Maintenance Guide..............................................................................................3-1

3.1 Definition of Emergency.................................................................................................................................3-2
3.2 Purposes of Emergence Maintenance..............................................................................................................3-2
3.3 Procedure of Emergency Maintenance............................................................................................................3-2
4 Troubleshooting Guide.............................................................................................................4-1
4.1 General Fault Locating Procedures.................................................................................................................4-2
4.2 Troubleshooting Service Interruptions............................................................................................................4-4
4.3 Troubleshooting Microwave Links.................................................................................................................4-8
4.4 Troubleshooting Bit Errors............................................................................................................................4-15
4.5 Troubleshooting Pointer Justifications..........................................................................................................4-20
4.6 Troubleshooting the Interconnection with the SDH Equipment...................................................................4-24
4.7 Troubleshooting the Interconnection with the PDH Equipment...................................................................4-28
4.8 Troubleshooting Ethernet Service Faults......................................................................................................4-30
4.9 Troubleshooting the Orderwire.....................................................................................................................4-36
5 Common Maintenance Operation Guide..............................................................................5-1

5.1 Loopback.........................................................................................................................................................5-3
5.1.1 Setting Loopback for the SDH Optical Interface Board........................................................................5-3
5.1.2 Setting Loopback for the SDH Electrical Interface Board.....................................................................5-5
5.1.3 Setting Loopback of the PDH Interface BoardSetting the Tributary Loopback....................................5-7
5.1.4 Setting Loopback on the IF Board.........................................................................................................5-8
5.1.5 Setting Loopback of the Ethernet Service Processing Board...............................................................5-11
5.1.6 Setting Loopback of the ODU..............................................................................................................5-13
5.2 Resetting........................................................................................................................................................5-14
5.2.1 Cold Resetting......................................................................................................................................5-14
5.2.2 Warm Resetting....................................................................................................................................5-15
5.2.3 SCC Resetting......................................................................................................................................5-15
5.3 PRBS Test.....................................................................................................................................................5-16
5.4 Using the Ethernet Test Frames....................................................................................................................5-18
5.5 Setting the State of the ODU Transmitter.....................................................................................................5-19
5.6 Setting the State of the Laser.........................................................................................................................5-20
5.7 Setting the Automatic Release Function.......................................................................................................5-21
5.8 Part Replacement...........................................................................................................................................5-21
5.8.1 Removing a Board................................................................................................................................5-22
5.8.2 Inserting a Board..................................................................................................................................5-23
5.8.3 Replacing the SDH Optical Interface Board........................................................................................5-24
5.8.4 Replacing the SDH Electrical Interface Board.....................................................................................5-25
ii

Issue 02 (2008-6-20)

Contents
5.8.5 Replacing the PDH Interface Board.....................................................................................................5-26

5.8.6 Replacing the Ethernet Service Processing Board...............................................................................5-27
5.8.7 Replacing the IF Board........................................................................................................................5-28
5.8.8 Replacing the PXC Board....................................................................................................................5-29
5.8.9 Replacing the SCC Board....................................................................................................................5-30
5.8.10 Replacing the Fan Board....................................................................................................................5-31
5.8.11 Replacing the ODU............................................................................................................................5-33
5.9 Cleaning Fiber Connectors and Adapters......................................................................................................5-34
5.9.1 Cleaning Fiber Connectors Using Cartridge Cleaners.........................................................................5-34
5.9.2 Cleaning Fiber Connectors Using Lens Tissue....................................................................................5-36
5.9.3 Cleaning Fiber Adapters Using Optical Cleaning Sticks.....................................................................5-37
A Alarm Reference.......................................................................................................................A-1
A.1 Alarm List......................................................................................................................................................A-1
A.2 Alarms and Corrective procedures..............................................................................................................A-10
A.2.1 A_LOC...............................................................................................................................................A-10
A.2.2 APS_MANUAL_STOP.....................................................................................................................A-11
A.2.3 ALM_GFP_dCSF...............................................................................................................................A-12
A.2.4 ALM_GFP_dLFD..............................................................................................................................A-13
A.2.5 ALM_RTC_FAIL...............................................................................................................................A-14
A.2.6 APS_FAIL..........................................................................................................................................A-15
A.2.7 APS_INDI..........................................................................................................................................A-16
A.2.8 AU_AIS..............................................................................................................................................A-17
A.2.9 AU_LOP.............................................................................................................................................A-19
A.2.10 B1_EXC...........................................................................................................................................A-20
A.2.11 B1_SD..............................................................................................................................................A-21
A.2.12 B2_EXC...........................................................................................................................................A-22
A.2.13 B2_SD..............................................................................................................................................A-23
A.2.14 B3_EXC...........................................................................................................................................A-24
A.2.15 B3_EXC_VC3..................................................................................................................................A-25
A.2.16 B3_SD..............................................................................................................................................A-26
A.2.17 B3_SD_VC3.....................................................................................................................................A-27
A.2.18 BD_NOT_INSTALLED..................................................................................................................A-28
A.2.19 BD_STATUS...................................................................................................................................A-29
A.2.20 BIP_EXC..........................................................................................................................................A-32
A.2.21 BIP_SD.............................................................................................................................................A-33
A.2.22 BOOTROM_BAD............................................................................................................................A-33
A.2.23 C2_VCAIS.......................................................................................................................................A-35
A.2.24 CONFIG_NOSUPPORT..................................................................................................................A-35
A.2.25 DBMS_ERROR...............................................................................................................................A-37
A.2.26 DBMS_PROTECT_MODE.............................................................................................................A-39
A.2.27 DN_E1_AIS.....................................................................................................................................A-40
A.2.28 E1_LOC............................................................................................................................................A-41
Issue 02 (2008-6-20)

iii
Contents

A.2.29 E1_LOS............................................................................................................................................A-42
A.2.30 ESN_FAILED..................................................................................................................................A-43
A.2.31 ESN_INVALID................................................................................................................................A-44
A.2.32 ETH_LOS.........................................................................................................................................A-45
A.2.33 EXT_SYNC_LOS............................................................................................................................A-46
A.2.34 F1PORT_FAILED...........................................................................................................................A-47
A.2.35 FAN_FAIL.......................................................................................................................................A-48
A.2.36 FCS_ERR.........................................................................................................................................A-49
A.2.37 HARD_BAD....................................................................................................................................A-51
A.2.38 HP_CROSSTR.................................................................................................................................A-53
A.2.39 HP_LOM..........................................................................................................................................A-54
A.2.40 HP_RDI............................................................................................................................................A-55
A.2.41 HP_REI.............................................................................................................................................A-56
A.2.42 HP_SLM...........................................................................................................................................A-57
A.2.43 HP_TIM............................................................................................................................................A-59
A.2.44 HP_UNEQ........................................................................................................................................A-60
A.2.45 HPAD_CROSSTR...........................................................................................................................A-61
A.2.46 HSB_INDI........................................................................................................................................A-62
A.2.47 HSM_INDI.......................................................................................................................................A-63
A.2.48 IF_CABLE_OPEN...........................................................................................................................A-64
A.2.49 IF_INPWR_ABN.............................................................................................................................A-65
A.2.50 IF_MODE_UNSUPPORTED..........................................................................................................A-67
A.2.51 IN_PWR_HIGH...............................................................................................................................A-67
A.2.52 IN_PWR_LOW................................................................................................................................A-69
A.2.53 J0_MM.............................................................................................................................................A-70
A.2.54 K1_K2_M.........................................................................................................................................A-71
A.2.55 K2_M................................................................................................................................................A-72
A.2.56 LASER_CLOSED............................................................................................................................A-74
A.2.57 LASER_MOD_ERR_EX.................................................................................................................A-75
A.2.58 LCAS_FOPR....................................................................................................................................A-76
A.2.59 LCAS_FOPT....................................................................................................................................A-77
A.2.60 LCAS_PLCR....................................................................................................................................A-79
A.2.61 LCAS_PLCT....................................................................................................................................A-80
A.2.62 LCAS_TLCR....................................................................................................................................A-81
A.2.63 LCAS_TLCT....................................................................................................................................A-83
A.2.64 LCS_LIMITED................................................................................................................................A-84
A.2.65 LICENSE_LOST..............................................................................................................................A-85
A.2.66 LICENSE_ERR................................................................................................................................A-86
A.2.67 LINK_ERR.......................................................................................................................................A-87
A.2.68 LOOP_ALM.....................................................................................................................................A-88
A.2.69 LPS_UNI_BI_M...............................................................................................................................A-90
A.2.70 LP_CROSSTR..................................................................................................................................A-91
iv

Issue 02 (2008-6-20)

Contents
A.2.71 LP_R_FIFO......................................................................................................................................A-92
A.2.72 LP_RDI.............................................................................................................................................A-93
A.2.73 LP_RDI_VC12.................................................................................................................................A-94
A.2.74 LP_RDI_VC3...................................................................................................................................A-95
A.2.75 LP_REI.............................................................................................................................................A-96
A.2.76 LP_REI_VC12.................................................................................................................................A-97
A.2.77 LP_REI_VC3...................................................................................................................................A-97
A.2.78 LP_RFI.............................................................................................................................................A-98
A.2.79 LP_SIZE_ERR.................................................................................................................................A-99
A.2.80 LP_SLM.........................................................................................................................................A-100
A.2.81 LP_SLM_VC12..............................................................................................................................A-101
A.2.82 LP_SLM_VC3................................................................................................................................A-102
A.2.83 LP_T_FIFO....................................................................................................................................A-103
A.2.84 LP_TIM..........................................................................................................................................A-104
A.2.85 LP_TIM_VC12...............................................................................................................................A-105
A.2.86 LP_TIM_VC3.................................................................................................................................A-106
A.2.87 LP_UNEQ......................................................................................................................................A-107
A.2.88 LP_UNEQ_VC12...........................................................................................................................A-108
A.2.89 LP_UNEQ_VC3.............................................................................................................................A-109
A.2.90 LSR_NO_FITED............................................................................................................................A-111
A.2.91 LSR_WILL_DIE............................................................................................................................A-111
A.2.92 LTI..................................................................................................................................................A-112
A.2.93 MOD_TYPE_MISMATCH...........................................................................................................A-114
A.2.94 MS_AIS..........................................................................................................................................A-115
A.2.95 MS_CROSSTR...............................................................................................................................A-116
A.2.96 MS_RDI.........................................................................................................................................A-117
A.2.97 MS_REI..........................................................................................................................................A-118
A.2.98 MSAD_CROSSTR.........................................................................................................................A-119
A.2.99 MSSW_DIFFERENT.....................................................................................................................A-120
A.2.100 MW_FECUNCOR.......................................................................................................................A-121
A.2.101 MW_LIM.....................................................................................................................................A-122
A.2.102 MW_LOF.....................................................................................................................................A-124
A.2.103 MW_RDI......................................................................................................................................A-125
A.2.104 NESF_LOST................................................................................................................................A-126
A.2.105 NESTATE_INSTALL..................................................................................................................A-127
A.2.106 NO_BD_SOFT.............................................................................................................................A-128
A.2.107 NP1_MANUAL_STOP................................................................................................................A-129
A.2.108 NP1_SW_FAIL............................................................................................................................A-130
A.2.109 NP1_SW_INDI.............................................................................................................................A-131
A.2.110 OPM_FAIL...................................................................................................................................A-132
A.2.111 PORT_MODULE_OFFLINE......................................................................................................A-133
A.2.112 POWER_ALM.............................................................................................................................A-134
Issue 02 (2008-6-20)

Contents

A.2.113 POWER_FAIL.............................................................................................................................A-135
A.2.114 P_AIS...........................................................................................................................................A-136
A.2.115 P_LOS..........................................................................................................................................A-137
A.2.116 PS..................................................................................................................................................A-138
A.2.117 R_F_RST......................................................................................................................................A-139
A.2.118 R_LOC.........................................................................................................................................A-140
A.2.119 R_LOF..........................................................................................................................................A-142
A.2.120 R_LOS..........................................................................................................................................A-143
A.2.121 R_S_ERR.....................................................................................................................................A-145
A.2.122 RADIO_MUTE............................................................................................................................A-146
A.2.123 RADIO_RSL_HIGH....................................................................................................................A-148
A.2.124 RADIO_RSL_LOW.....................................................................................................................A-149
A.2.125 RADIO_TSL_HIGH....................................................................................................................A-151
A.2.126 RADIO_TSL_LOW.....................................................................................................................A-151
A.2.127 RELAY_ALARM........................................................................................................................A-152
A.2.128 RP_LOC.......................................................................................................................................A-153
A.2.129 RS_CROSSTR.............................................................................................................................A-154
A.2.130 S1_SYN_CHANGE.....................................................................................................................A-155
A.2.131 SYN_BAD....................................................................................................................................A-156
A.2.132 SYNC_C_LOS.............................................................................................................................A-157
A.2.133 T_ALOS.......................................................................................................................................A-158
A.2.134 T_F_RST......................................................................................................................................A-159
A.2.135 T_FIFO_E.....................................................................................................................................A-160
A.2.136 T_LOC..........................................................................................................................................A-161
A.2.137 T_LOS..........................................................................................................................................A-163
A.2.138 TEMP_ALARM...........................................................................................................................A-164
A.2.139 TU_AIS........................................................................................................................................A-165
A.2.140 TU_AIS_VC12.............................................................................................................................A-167
A.2.141 TU_AIS_VC3...............................................................................................................................A-168
A.2.142 TU_LOP.......................................................................................................................................A-170
A.2.143 TU_LOP_VC12............................................................................................................................A-171
A.2.144 TU_LOP_VC3..............................................................................................................................A-172
A.2.145 UP_E1_AIS..................................................................................................................................A-173
A.2.146 VCAT_LOA.................................................................................................................................A-175
A.2.147 VCAT_LOM_VC12.....................................................................................................................A-176
A.2.148 VCAT_LOM_VC3.......................................................................................................................A-177
A.2.149 VCAT_SQM_VC12.....................................................................................................................A-178
A.2.150 VCAT_SQM_VC3.......................................................................................................................A-179
A.2.151 VOLT_LOS..................................................................................................................................A-181
A.2.152 WRG_BD_TYPE.........................................................................................................................A-183
A.2.153 WRG_DEV_TYPE.......................................................................................................................A-184
A.2.154 WS_LOS.......................................................................................................................................A-184
vi

Issue 02 (2008-6-20)

Contents
A.2.155 W_R_Failure................................................................................................................................A-186
A.2.156 XCP_INDI....................................................................................................................................A-186
A.2.157 XPIC_LOS...................................................................................................................................A-187
B Performance Event Reference.................................................................................................B-1

B.1 Performance Event List..................................................................................................................................B-1
B.1.1 SDH /PDH Performance Event List.....................................................................................................B-1
B.1.2 Microwave Performance Events...........................................................................................................B-4
B.1.3 Other Performance Events....................................................................................................................B-5
B.2 Performance Events and Corrective Procedures............................................................................................B-6
B.2.1 AUPJCHIGH, AUPJCLOW, and AUPJCNEW...................................................................................B-6
B.2.2 TUPJCHIGH, TUPJCLOW, and TUPJCNEW....................................................................................B-7
B.2.3 RSBBE, RSES, RSSES, RSCSES, and RSUAS..................................................................................B-8
B.2.4 RSOOF and RSOFS..............................................................................................................................B-9
B.2.5 MSBBE, MSES, MSSES, MSCSES, and MSUAS............................................................................B-10
B.2.6 MSFEBBE, MSFEES, MSFESES, MSFECSES, and MSFEUAS.....................................................B-11
B.2.7 HPBBE, HPES, HPSES, HPCSES, and HPUAS...............................................................................B-12
B.2.8 HPFEBBE, HPFEES, HPFESES, HPFECSES, and HPFEUAS........................................................B-14
B.2.9 VC3BBE, VC3ES, VC3SES, VC3CSES, and VC3UAS...................................................................B-15
B.2.10 VC3FEBBE, VC3FEES, VC3FESES, VC3FECSES, VC3FEUAS.................................................B-16
B.2.11 LPBBE, LPES, LPSES, LPCSES, and LPUAS................................................................................B-17
B.2.12 LPFEBBE, LPFEES, LPFESES, LPFECSES and LPFEUAS.........................................................B-18
B.2.13 E3_LCV_SDH, E3_LES_SDH, and E3_LSES_SDH......................................................................B-19
B.2.14 T3_LCV_SDH, T3_LES_SDH, and T3_LSES_SDH......................................................................B-20
B.2.15 TSLMAX, TSLMIN, and TSLCUR.................................................................................................B-21
B.2.16 RSLMAX, RSLMIN and RSLCUR.................................................................................................B-22
B.2.17 FEC_BEF_COR_ER, FEC_COR_BYTE_CNT...............................................................................B-22
B.2.18 TPLMAX, TPLMIN, and TPLCUR.................................................................................................B-23
B.2.19 RPLMAX, RPLMIN, and RPLCUR................................................................................................B-24
B.2.20 BDTMPMAX, BDTMPMIN, and BDTMPCUR.............................................................................B-24
B.2.21 OSPITMPMAX, OSPITMPMIN, and OSPITMPCUR....................................................................B-25
C Alarm Management.................................................................................................................C-1
C.1 NE Alarm Management.................................................................................................................................C-1
C.2 Board Alarm Management.............................................................................................................................C-1
C.2.1 Setting the Alarm Level........................................................................................................................C-1
C.2.2 Alarm Suppression................................................................................................................................C-1
C.2.3 Alarm Auto-Report...............................................................................................................................C-1
C.2.4 Alarm Reversion...................................................................................................................................C-2
C.2.5 Setting Bit Error Alarm Threshold.......................................................................................................C-2
C.2.6 AIS Insertion.........................................................................................................................................C-3
C.2.7 UNEQ Insertion....................................................................................................................................C-4
D Performance Event Management..........................................................................................D-1

Issue 02 (2008-6-20)

vii
Contents

D.1 NE Performance Event Management............................................................................................................D-1

D.2 Board Performance Event Management........................................................................................................D-1
E Alarm Suppression Relation...................................................................................................E-1

F Glossary.......................................................................................................................................F-1
G Acronyms and Abbreviations...............................................................................................G-1
Index.................................................................................................................................................i-1
viii

Issue 02 (2008-6-20)

Figures
Figures
Figure 1-1 Wearing an ESD wrist strap............................................................................................................... 1-3
Figure 3-1 Main procedure of emergency maintenance.......................................................................................3-3
Figure 3-2 Procedure of on-site fault handling.....................................................................................................3-6
Figure 4-1 General fault locating procedures.......................................................................................................4-3
Figure 4-2 Flow of handling service interruptions...............................................................................................4-5
Figure 4-3 Procedure of on-site fault handling.....................................................................................................4-7
Figure 4-4 Flow of handling microwave link faults...........................................................................................4-11
Figure 4-5 Flow of handling bit errors...............................................................................................................4-18
Figure 4-6 Flow of handling pointer justifications.............................................................................................4-22
Figure 4-7 Flow of troubleshooting the interconnection with the SDH equipment...........................................4-26
Figure 4-8 Flow of troubleshooting the interconnection with the PDH equipment...........................................4-29
Figure 4-9 Flow of handling Ethernet service faults..........................................................................................4-32
Figure 4-10 Flow of handling RMON abnormal performance events...............................................................4-35
Figure 4-11 Flow of handling orderwire faults..................................................................................................4-37
Figure 5-1 Optical interface inloop......................................................................................................................5-3
Figure 5-2 Optical interface outloop....................................................................................................................5-4
Figure 5-3 VC-4 path outloop..............................................................................................................................5-4
Figure 5-4 VC-4 path inloop................................................................................................................................5-4
Figure 5-5 Electrical interface inloop ..................................................................................................................5-5
Figure 5-6 Electrical interface outloop.................................................................................................................5-6
Figure 5-7 VC-4 path outloop .............................................................................................................................5-6
Figure 5-8 Tributary outloop................................................................................................................................5-7
Figure 5-9 Tributary inloop..................................................................................................................................5-7
Figure 5-10 Tributary outloop..............................................................................................................................5-8
Figure 5-11 IF port inloop....................................................................................................................................5-9
Figure 5-12 IF port outloop..................................................................................................................................5-9
Figure 5-13 Port inloop........................................................................................................................................ 5-9
Figure 5-14 Port outloop....................................................................................................................................5-10
Figure 5-15 VC-4 path inloop............................................................................................................................5-10
Figure 5-16 inloop over an Ethernet port...........................................................................................................5-11
Figure 5-17 VC-3 path inloop ...........................................................................................................................5-12
Figure 5-18 VC-3 path outloop .........................................................................................................................5-12
Figure 5-19 RF inloopback.................................................................................................................................5-13
Issue 02 (2008-6-20)

ix

Figures
Figure 5-20 PRBS test in the tributary direction................................................................................................5-16

Figure 5-21 PRBS test in the cross-connect direction........................................................................................5-17
Figure 5-22 Ethernet test frames between Ethernet boards................................................................................5-19
Figure 5-23 Removing a board (1).....................................................................................................................5-22
Figure 5-24 Removing a board (2) ....................................................................................................................5-22
Figure 5-25 Removing a board (3).....................................................................................................................5-23
Figure 5-26 Inserting a board (1).......................................................................................................................5-23
Figure 5-29 Remove the portable memory card.................................................................................................5-31
Figure 5-30 Pulling out the fan tray assembly...................................................................................................5-32
Figure 5-31 Removing the fan board.................................................................................................................5-32
Figure 5-32 CLETOP cassette cleaner...............................................................................................................5-35
Figure 5-33 Dragging the fiber tip slightly on one cleaning area.......................................................................5-35
Figure 5-34 Dragging the fiber tip slightly on the other cleaning area..............................................................5-36
Figure 5-35 Cleaning the fiber with the lens tissue ...........................................................................................5-37

Issue 02 (2008-6-20)

Tables
Tables
Table 2-1 Web LCTbased routine maintenance items....................................................................................... 2-2
Table 2-2 T2000-based routine maintenance items..............................................................................................2-3
Table 2-3 Field maintenance items for indoor equipment....................................................................................2-4
Table 2-4 Field maintenance items for outdoor equipment..................................................................................2-4
Table 3-1 Description of the main procedure of emergency maintenance...........................................................3-4
Table 3-2 Sheet for on-site operations..................................................................................................................3-4
Table 3-3 Procedure of on-site fault handling......................................................................................................3-7
Table 4-1 Flow description...................................................................................................................................4-4
Table 4-2 Flow description...................................................................................................................................4-5
Table 4-3 Causes of microwave link faults..........................................................................................................4-9
Table 4-4 Flow description.................................................................................................................................4-12
Table 4-5 Causes of bit errors.............................................................................................................................4-16
Table 4-10 Flow description...............................................................................................................................4-33
Table 5-1 Part replacement description .............................................................................................................5-21
Table A-1 Alarm list............................................................................................................................................A-1
Table B-1 Pointer justification performance event list........................................................................................B-1
Table B-2 Regenerator section error performance event list...............................................................................B-1
Table B-3 Multiplex section error performance event list...................................................................................B-2
Table B-4 Higher order path error performance event list...................................................................................B-2
Table B-5 VC-3 path bit error performance event list.........................................................................................B-3
Table B-6 Lower order path error performance event list...................................................................................B-3
Table B-7 Line side code violation performance event list.................................................................................B-4
Table B-8 Microwave power performance events...............................................................................................B-4
Table B-9 FEC performance events.....................................................................................................................B-5
Table B-10 Optical power performance events...................................................................................................B-5
Table B-11 Board temperature performance events............................................................................................B-5
Table B-12 Laser core temperature performance events.....................................................................................B-5
Issue 02 (2008-6-20)

xi
Tables

Table C-1 Setting of the bit error alarm threshold...............................................................................................C-3
Table C-2 Setting of AIS insertion......................................................................................................................C-3
Table C-3 Setting of UNEQ insertion.................................................................................................................C-4
Table D-1 Board performance event management function................................................................................D-1
Table E-1 Suppression relation between intra-board alarms...............................................................................E-1
Table E-2 Suppression relation between inter-board alarms...............................................................................E-2
xii

Issue 02 (2008-6-20)

About This Document
About This Document
Purpose
This document is a maintenance guide of the OptiX RTN 600based IDU 610/620. It also
contains details of alarms and performance events for reference purpose.
Related Versions
The following table lists the product versions related to this document.
Product Name
Version
OptiX RTN 600
V100R002
OptiX iManager T2000
V200R006C03
Intended Audience
This document is intended for the maintenance engineers of the OptiX RTN 600. Before reading
this document, you need to:
l
Know microwave communication basics.
Know the basics of the OptiX RTN 600 product.
Organization
This document is organized as follows.
Issue 02 (2008-6-20)


About This Document
Chapter
Content
1 Safety
Precautions
Describes parts of the safety precautions. Read and follow these safety
precautions before installing, commissioning, and maintaining the
OptiX RTN 600.
2 Routine
Maintenance Guide
Describes maintenance items and operation procedures for routine

maintenance of the OptiX RTN 600.
3 Emergency
Maintenance Guide
Describes operation procedures for emergency maintenance of the

OptiX RTN 600.
4 Troubleshooting
Guide
Describes the causes of common faults and troubleshooting

procedures of the OptiX RTN 600.
5 Common
Maintenance
Operation Guide
Describes common maintenance operations of the OptiX RTN 600.
A Alarm Reference
Describes all the possible alarms and clearing procedures of the OptiX
RTN 600.
B Performance
Event Reference
Describes all the performance events and clearing procedures of the

OptiX RTN 600.
C Alarm
Management
Describes the alarm management function of the OptiX RTN 600.
D Performance
Event Management
Describes the performance management function of the OptiX RTN

600.
E Alarm
Suppression
Relation
Describes the alarm suppression relation of the OptiX RTN 600.
F Glossary
Lists the terms used in this document.
G Acronyms and
Abbreviations
Lists the acronyms and abbreviations used in this document.
Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol
Description
Indicates a hazard with a high level of risk, which if not
avoided, will result in death or serious injury.

Issue 02 (2008-6-20)

Symbol
About This Document
Description
Indicates a hazard with a medium or low level of risk, which
if not avoided, could result in minor or moderate injury.
Indicates a potentially hazardous situation, which if not
avoided, could result in equipment damage, data loss,
performance degradation, or unexpected results.
Indicates a tip that may help you solve a problem or save time.
Provides additional information to emphasize or supplement
important points of the main text.
General Conventions
The general conventions that may be found in this document are defined as follows.
Convention
Description
Times New Roman
Normal paragraphs are in Times New Roman.
Boldface
Names of files, directories, folders, and users are in

boldface. For example, log in as user root.
Italic
Book titles are in italics.
Courier New
Examples of information displayed on the screen are in

Courier New.
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Convention
Description
Boldface
Buttons, menus, parameters, tabs, windows, and dialog titles are in

boldface. For example, click OK.
>
Multi-level menus are in boldface and separated by the ">" signs. For
example, choose File > Create > Folder.
Mouse Operation
The mouse operations that may be found in this document are defined as follows.
Issue 02 (2008-6-20)


About This Document
Action
Description
Click
Select and release the primary mouse button without moving the pointer.
Double-click
Press the primary mouse button twice continuously and quickly without
moving the pointer.
Drag
Press and hold the primary mouse button and move the pointer to a certain
position.
Update History
Updates between document versions are cumulative. Therefore, the latest document version
contains all updates made to previous versions.
Updates in Issue 02 (2008-06-20)

Known defects are modified as required.
Updates in Issue 01 (2008-05-20)

Initial release.

Issue 02 (2008-6-20)

1 Safety Precautions
Safety Precautions
This section describes parts of the safety precautions. Read and follow these safety precautions
before installing, commissioning, and maintaining the OptiX RTN 600.
CAUTION
Before performing any operation, go through the instructions and precautions carefully to
minimize the possibility of accidents. The Caution, Warning and Danger items in other
documents do not cover all the safety precautions that must be followed. They are only
supplements to the safety precautions for operations as a whole. The personnel in charge of the
installation and maintenance must be trained to learn the proper operating methods and all safety
precautions. Only the trained and qualified personnel can install or maintain the device.
When operating the device, abide by the local safety regulations. The precautions listed in this
chapter are in compliance with the local safety regulations.
When operating the Huawei device, follow the full precautions and special safety instructions
from Huawei.
The personnel in charge of installation and maintenance must understand the basics of the safety
operations. Only trained and qualified personnel can install or maintain the device.
High Voltage
DANGER
Issue 02 (2008-6-20)
The high voltage power supply supplies power for the device operation. Direct or indirect
contact (through damp objects) with high voltage and AC mains supply may result in fatal
accident.
Non-standard and improper high voltage operations can result in fire and electric shock.
Therefore, you must abide by the local rules and regulations when bridging and wiring AC
cables through a certain area. The personnel who perform high voltage operations must be
qualified for performing high voltage and AC operations.

1-1

l
Do not wear conducting articles, such as watches, chains, bracelets and rings while
performing high voltage operations.
Switch off the power supply immediately if you find water in the rack or if the rack is damp.
Make sure that the device is kept away from water when being operated in a damp
environment.
Power Cable
DANGER
l
Do not install or remove a live line. Transient contact between the core of the power cable
and the conductor might generate electric arc or spark, which can cause fire or damage to the
human body.
During high voltage and AC operations, special tools must be used instead of common tools.
Before installing or removing the power cable, turn off the power switch.
Before connecting the power cable, make sure that the power cable and label conform to
the requirements of the actual installation.
Thunderstorm
DANGER
High voltage and AC operations, or operations on a steel tower and a mast on a thunderstorm
day are prohibited.
On a thunderstorm day, the electromagnetic field generated in the thunderstorm area may cause
damage to electronic parts. To prevent the device from being damaged by lightning, use proper
grounding.
Electrostatic Discharge
CAUTION
The static electricity generated by the human body can damage the electrostatic sensitive
components on the circuit board, such as the large-scale integrated circuit (LIC).
Electrostatic discharge (ESD) is caused by body movement, friction between shoes and floor,
friction between clothes, and contact with plastic objects. ESD remains in the human body for
a long time.
Before touching the device or holding the boards, circuit boards, or ASICs, wear a grounded
ESD wrist strap. It can prevent the sensitive components from being damaged by the static
electricity in the human body.
1-2

Issue 02 (2008-6-20)

Figure 1-1 Wearing an ESD wrist strap
Microwave
WARNING
Strong radio frequency can harm the human body.
Do not stay too close to the antenna in the emitting direction of the antenna when the microwave
communication equipment is working. Before installing or maintaining an antenna in a steel
tower or a mast with a large number of transmitter antennas, the operator should coordinate all
parties concerned to shut down the transmitter antennas.
Laser
WARNING
Laser radiation can cause injury to your eyes.
When handling optical fibers, do not stand close to or look into the optical fiber outlet directly
with naked eyes.
High Temperature
WARNING
When the ambient temperature is higher than 55, the surface temperature of the IDU boards
may exceed 70. In this case, wear protective gloves before touching the IDU boards.
Issue 02 (2008-6-20)

1-3

Working at Heights
WARNING
When working at heights, prevent objects from falling down.
Working at high altitude shall comply with the following requirements:
l
Only trained personnel can work at high altitudes.
The operating machines and tools should be carried and handled safely to prevent them
from falling.
Safety measures, such as wearing a helmet and a safety belt, should be taken.
In cold areas, warm clothes must be worn before performing any high-altitude operation.
Appliances used for lifting objects must be checked and ensured to be intact before
performing any high-altitude operation.
Hoisting Heavy Objects
DANGER
During hoisting heavy objects, do not stand or walk under the boom or the objects.
Sharp Objects
WARNING
When carrying the device with hands, wear protection gloves to avoid injuries caused by sharp
objects.
IF Cable
WARNING
Before installing or removing the IF cable, turn off the ODU-PWR power switch on the IF board.
1-4

Issue 02 (2008-6-20)

Installing and Removing Boards
CAUTION
l
When inserting a board, handle it gently to avoid distorting the pins on the backplane.
Insert the board along the slot guide. Do not allow the board interfaces to come in contact
with that of another board as this can cause short-circuit or can damage the board.
When holding a board in hand, do not touch the board circuit, components, connectors, or
the connection slots.
Bundling Signal Cables
CAUTION
Bundle the signal cables separately from the strong current cables or high voltage cables. The
space between two adjacent ties must be at least 150 mm.
Issue 02 (2008-6-20)

1-5

2 Routine Maintenance Guide
Routine Maintenance Guide
About This Chapter

The aim of routine maintenance is to find and remove hidden fault causes in time before the
equipment becomes faulty and services are affected. Simply, nip in the bud.
2.1 Routine Maintenance Items
Routine maintenance items are classified into four categories: routine maintenance items carried
out through the Web LCT, routine maintenance items carried out through the T2000, field
maintenance items for indoor equipment, and field maintenance items for outdoor equipment.
2.2 Guide to Web LCTBased Routine Maintenance
This topic describes the guide to the routine maintenance items that are carried out though the
Web LCT.
2.3 Guide to T2000-Based Routine Maintenance
T2000.
2.4 Guide to Field IDU Maintenance
This guide describes how to carry out routine maintenance for the IDU and the equipment room
where the IDU is installed.
2.5 Guide to Field Maintenance of Outdoor Equipment
This guide describes how to carry out routine maintenance on site for outdoor equipment.
Issue 02 (2008-6-20)

2-1

2.1 Routine Maintenance Items

Routine maintenance items are classified into four categories: routine maintenance items carried
out through the Web LCT, routine maintenance items carried out through the T2000, field
maintenance items for indoor equipment, and field maintenance items for outdoor equipment.
2.1.1 Web LCTBased Routine Maintenance Items

This topic describes the routine maintenance items that can be carried out through the Web LCT.
Table 2-1 Web LCTbased routine maintenance items
Maintenance Item
Recommen
ded Cycle
Remarks
2.2.1 Checking the Status of NEs and

Boards
Every day
2.2.2 Browsing the Current Alarms
Every day
2.2.3 Browsing the History Alarms
Every day
2.2.5 Browsing the Current Performance

Events of the SDH/PDH
Every day
2.2.6 Browsing the History Performance

Every day
2.2.4 Browsing the Abnormal Events
Every day
2.2.7 Testing the IF 1+1 Switching
Half a year
Applies only to the

equipment that is configured
in 1+1 protection mode.
During the 1+1 protection
switching (< 500 ms),
protection services are
interrupted. Hence, you are
recommended to carry out 1
+1 protection switching
when the traffic is light.
2-2
2.2.8 Testing the IF N+1 Switching
Half a year
Applies only to the

in N+1 protection mode.
2.2.9 Testing the Two-Fiber Bidirectional

MSP Ring Switching
Half a year
Applies only to the

in two-fiber bidirectional
MSP.

Issue 02 (2008-6-20)

2.1.2 T2000-Based Routine Maintenance Items

This topic describes the routine maintenance items that can be carried out through the T2000.
Table 2-2 T2000-based routine maintenance items
Maintenance Item
Recommen
ded Cycle
Remarks
2.3.1 Checking the Status of NEs and

Boards
Every day
Every day
Every day
2.3.5 Browsing the Current Performance

Every day
2.3.6 Browsing the History Performance

Every day
Every day
Half a year
Applies only to the

in 1+1 protection mode.
During the 1+1 protection
switching (< 500 ms),
protection services are
interrupted. Hence, you are
recommended to carry out 1
+1 protection switching
when the traffic is light.
Half a year
Applies only to the

in N+1 protection mode.
2.3.9 Testing the Two-Fiber Bidirectional

MSP Ring Switching
Half a year
Applies only to the

in two-fiber bidirectional
MSP.
2.1.3 Field Maintenance Items for Indoor Equipment

Carry out these field maintenance items in the equipment room where the IDU is installed.
Issue 02 (2008-6-20)

2-3

Table 2-3 Field maintenance items for indoor equipment

Maintenance Item
Recommended
Cycle
Remarks
2.4.1 Cleaning the

Air Filter
Two months
Only for the IDU 620a
2.4.2 Testing the

Orderwire Phone
Two months
Only for the case that the equipment is

equipped with the orderwire phone
2.4.3 Checking the

Equipment Room
Two months
Only for the case that the equipment is

installed indoors
NOTE
a: If the IDU 620 is installed in an outdoor dust-proof cabinet, the IDU is not installed with an air filter.
2.1.4 Field Maintenance Items for Outdoor Equipment

Carry out these field maintenance items at places where the ODU, hybrid coupler, antenna, and
other outdoor equipment are installed.
Table 2-4 Field maintenance items for outdoor equipment
Maintenance Item
Recommended
Cycle
Remarks
2.5.1 Checking the

ODU
Half year
2.5.2 Checking the

Hybrid Coupler
Half year
Carry out a complete check after a level-8

hurricane, an earthquake, or other exceptional
circumstances.
2.5.3 Checking the

Antenna
Half year
2.5.4 Checking IF
Cables
Half year
2.2 Guide to Web LCTBased Routine Maintenance

Web LCT.
2.2.1 Checking the Status of NEs and Boards

This topic describes how to check the status of an NE or a board through the Web LCT. By
obtaining the status of the NE or board, you can detect faults in time.
2-4

Issue 02 (2008-6-20)

Prerequisite
l
The Web LCT is in normal communication with the NE.
The NE user has the authority of monitor level or higher.
Tools, Instruments, and Materials

Web LCT
Procedure
Step 1 Log in to the Web LCT, open the NE List window, and check the Communication Status
column of a specific NE.
The Communication Status column should be Normal.
Step 2 If the Login Status column of a specific NE is Not Logged In, log in to the NE.
1.
Right-click the NE, and choose NE Login from the shortcut menu.
The system displays the NE Login dialog box.
2.
Specify User Name and Password.

l
The user name is lct by default.
The password for user lct is password by default.

NOTE
User lct has the authority of system level.
The Login Status column switches to Logged In.

Step 3 Click NE Explorer.
Step 4 Check NE STATE above the slot layout.
NE STATE should be Running.
Step 5 Check the running status of the boards by referring to the legend description.
If a board is running normally, it should be green.
----End

Periodically browsing alarms helps you to find and rectify a fault in a timely manner.
Prerequisite
l

Web LCT
Issue 02 (2008-6-20)

2-5

Procedure
Step 1 Select an NE from the Object Tree in the NE Explorer, and click the
icon in the toolbar.
Step 2 Browse the displayed alarms.

Step 3 Select the newly generated alarms, and record the details of them.
Step 4 If there are newly generated alarms after the last maintenance, notify the troubleshooting
personnel for alarm clearing in time.
For details about how to handle alarms, refer to A Alarm Reference.
----End
Related Information
A current alarm is an alarm that is not cleared.

Periodically browsing alarms helps you to find and rectify a fault in a timely manner.
Prerequisite
l

Web LCT
Procedure
Step 1 Select an NE from the Object Tree in the NE Explorer, and click the
icon in the toolbar.
Step 2 Select the Browse History Alarm tab.

Step 3 Click Filter.
The Filter dialog box is displayed.
Step 4 After specify Start Time and End Time, click Filter.
The start time should be the time when the last history alarm browsing operation was performed,
and the end time should be the current time.
Step 5 Browse the displayed history alarms.
Step 6 Click Save As.
The system displays the text file that lists the history alarms. You can save the text file as required.
----End
Related Information
A history alarm is an alarm that has been cleared. An NE stores a maximum of 1,000 history
alarms.
2-6

Issue 02 (2008-6-20)


Periodically browsing abnormal events helps you to find abnormalities in the equipment in a
timely manner.
Prerequisite
l

Web LCT
Procedure
Step 1 Select an NE from the NE Explorer, and choose Alarm > Browse Abnormal Events from the
Function Tree.
TIP
Alternatively, you can select an NE and then click the

Events tab page.
icon to switch to the Browse Abnormal

Step 3 Click Select All, and then click OK.
Step 4 Browse the displayed abnormal events.
Step 5 Optional: Click Save As.
The system displays the text file that lists the abnormal events. You can save the text file as
required.
----End
Related Information
An abnormal event is an abnormality that arises in the system at a particular time rather than
persists for a period. Being different from alarms, an abnormal event has only occurrence time,
with clearance time not provided.
2.2.5 Browsing the Current Performance Events of the SDH/PDH

Periodically browsing the performance events helps you to check the long-term running status
of the equipment. Hence, the latent hazards can be detected and cleared in time.
Prerequisite
Issue 02 (2008-6-20)
The performance monitoring function must be enabled.

2-7


Web LCT
Procedure
Step 1 Select a specific board from the NE Explorer, and choose Performance > Current
Performance from the Function Tree.
Step 2 Select All in Monitored Object Filter Condition.
Step 3 Select 15-Minute after Monitor Period.
Step 4 Select all the available performance events in Count, and select Display Continuous Severely
Errored Second in Display Options.
Step 5 Click Apply.
Step 6 Browse the displayed performance events.
In normal situations, no bit error performance events should be displayed, and the number of
pointer justification events should be less than six per day.
Step 7 Select all the available performance events in Gauge, and select Current Value and Maximum/
Minimum Value in Display Options.
Step 8 Click Apply.
Step 9 Browse the displayed performance events.
Compared with the history records, the gauge indicators, such as board temperature, do not
change drastically.
Step 10 Select 24-Hour after Monitor Period.
Step 11 Repeat Step 4 through Step 9 to query the current performance events in a period of 24 hours.
----End
Related Information
The counter of current performance events measures all the performance events that arise
between the start time of the monitoring period and the current time.
2.2.6 Browsing the History Performance Events of the SDH/PDH

Periodically browsing the performance events helps you to check the long-term running status
of the equipment. Hence, the latent hazards can be detected and cleared in time.
Prerequisite
l

Web LCT
2-8

Issue 02 (2008-6-20)

Procedure
Step 1 Select a specific board from the NE Explorer, and choose Performance > History
Performance from the Function Tree.
Step 4 Specify the start time and end time of a specific time span. The time span starts from the time
when the last history performance event browsing operation was performed to the current time.
Step 5 Select all the available performance events in Count, and select Display Continuous Severely
Errored Second in Display Options.
Step 6 Click Query to browse the history performance events.
Step 7 Click Save As.
The system displays the text file that lists the history performance events. You can save the text
file as required.
Step 8 Select all the available performance events in Gauge, and select Current Value and Maximum/
Minimum Value in Display Options.
Step 10 Click Save As to save the performance events.
The system displays the text file that lists the history performance events. You can save the text
file as required.
Step 11 Select 24-Hour after Monitor Period.
Step 12 Repeat Step 4 through Step 10 to query the history performance events in a period of 24 hours.
----End
Related Information
A history performance event is a performance event of which the monitor period ends in the
past. For history performance events, an NE has only six 24-hour registers and sixteen 15-minute
registers for each performance indicator. Therefore, only the six most recent non-zero 24-hour
performance events and the sixteen most-recent non-zero 15-minute performance events can be
obtained from the NE.

Periodically testing the IF 1+1 switching helps you to check whether the equipment can be
normally switched.
Prerequisite
l
The NE user has the authority of maintenance level or higher.

Web LCT
Issue 02 (2008-6-20)

2-9

Precautions
l
The IF 1+1 switching performed manually is a HSB switching. During the 1+1 protection
switching (< 500 ms), protection services are interrupted. Hence, you are recommended to
carry out 1+1 protection switching when the traffic is light.
Before you perform the switching, ensure that the standby equipment is working properly.
If the switching fails, contact Huawei engineers for further assistance.
Procedure
Step 1 Select an NE from the NE Explorer, and choose Configuration > Link Configuration from
the Function Tree.
Step 2 Select the IF 1+1 Protection tab.
Step 3 In Protection Group, select the protection group that is to be switched over.
Step 4 In Slot Mapping Relation, right-click the IF board, and choose Manual Switch to
Protection from the shortcut menu.
Step 5 Click OK to begin the protection switching.
Step 6 Click Query to check the protection switching status.
After the switching is complete, the Switching Status of Device of the working board should
be Manual Switching.
Step 7 After the equipment runs properly for a period, query the current alarms and performance events.
There should be no new alarms or performance events.
Step 8 Repeat Step 1 through Step 3.
Step 9 In Slot Mapping Relation, right-click the IF board, and choose Clear from the shortcut menu.
Step 10 Click OK to restore the protection switching.
the Switching Status of Device of the working board should be Normal.
----End

Periodically testing the IF N+1 switching helps you to check whether the equipment can be
normally switched over.
Prerequisite
l

Web LCT
2-10

Issue 02 (2008-6-20)

Precautions
l
This task helps to check whether an NE implements the N+1 protocol properly and is
designed only for test. Therefore, the service is not switched over.
Procedure
the Function Tree.
Step 2 Select N+1 Protection tab.
Step 3 In Slot Mapping Relation, right-click a working unit, and choose Exercise switching from the
shortcut menu.
The system displays a prompt message indicating that the switching command is issued
successfully.
Step 4 Click OK.
The status of the working unit should be Exercise switching.
Step 7 In Slot Mapping Relation, right-click the protection unit or a working unit, and choose Clear
from the shortcut menu.
Step 8 Click OK.
The status of the working unit should be normal.
----End
2.2.9 Testing the Two-Fiber Bidirectional MSP Ring Switching

Periodically testing the two-fiber bidirectional MSP ring switching helps you to check whether
the equipment can be switched normally.
Prerequisite
l

Web LCT
Precautions
l
Issue 02 (2008-6-20)
This task helps to check whether an NE implements the MSP protocol properly and is
2-11


l
Procedure
Step 1 Select an NE from the Object Tree in the NE Explorer, and choose Configuration > Ring
MSP from the Function Tree.
Step 3 In Slot Mapping Relation, right-click East Line, and choose Exercise switching from the
shortcut menu.
Step 4 Click OK to query the status of protection switching. The Switching Status of the east line
board should be Excise ring switching.
Step 5 Right-click the selected line, and choose Clear excise ring switching from the shortcut menu.
board should be Normal.
Step 7 In Slot Mapping Relation, right-click West Line of the protection group selected in Step 2,
and choose Excise ring switching from the shortcut menu.
----End
2.3 Guide to T2000-Based Routine Maintenance

T2000.
2.3.1 Checking the Status of NEs and Boards

This topic describes how to check the status of an NE or a board through the T2000. By obtaining
the status of the NE or board, you can detect faults in time.
Prerequisite
l
The T2000 is in normal communication with the NE.

T2000
Procedure
Step 1 Log in to the T2000 system, and check the color of the NE icon.
TIP
In the toolbar of the main view, click the

icon, and select the Legend tab in the displayed window.
By moving the vertical scrolling bar, you can view all the status legends of the NE.
2-12

Issue 02 (2008-6-20)

The NE icon should be green. In other cases, you can infer as follows:
l
If the NE icon is gray, you can infer that the NE loses communication with the T2000.
If the NE icon is blue, you can infer that the NE status is unknown.
If the NE icon is red, you can infer that a critical alarm is generated.
If the NE icon is orange, you can infer that a major alarm is generated.
If the NE icon is yellow, you can infer that a minor alarm is generated.
If the NE icon is purple, you can infer that a warning is generated.
Step 2 Double-click the NE.

The slot layout is displayed.
Step 3 Check NE STATE above the slot layout.
NE STATE should be Running.
Step 4 Click the
icon.
The system displays the legend description.

Step 5 Check the running status of the boards by referring to the legend description.
If a board is running normally, it should be green.
----End

Periodically browsing the current alarms helps you to find and rectify a fault in a timely manner.
Prerequisite
l

T2000
Procedure
Step 1 On the T2000, choose Fault > Browse Current Alarms from the main menu.
Step 2 Select one or multiple NEs from the left pane, and click
All the alarms of the selected NE or NEs are displayed in Browse Current Alarms.
Step 3 Select Auto Refresh.
Step 5 Select the newly generated alarms, record the details of them, and click OK.
Step 6 Notify the fault handling personnel of the alarms in a timely manner.
Issue 02 (2008-6-20)

2-13

For details about how to handle alarms, refer to Alarm Reference.

----End
Related Information
A current alarm is an alarm that is not cleared.
You can browse the network-wide alarms based on alarm severity by clicking the alarm
indicators in the upper right corner.
l
You can click
(red) to browse the network-wide critical alarms.
You can click
(orange) to browse the network-wide major alarms.
You can click
(yellow) to browse the network-wide minor alarms.
NOTE
The number to the right side of each indicator indicates the number of network-wide alarms of the specific
severity.
If a square frame is displayed around an alarm indicator, you can infer that there are unacknowledged alarms.

Periodically browsing the history alarms helps you to find and rectify a fault in a timely manner.
Prerequisite

T2000
Procedure
Step 1 On the T2000, choose Fault > History Alarm Browse from the main menu.
.
All the history alarms of the selected NE or NEs are displayed in History Alarm Browse.
Step 4 After specify Start Time and End Time, click Filter.
The start time should be the time when the last history alarm browsing operation was performed,
and the end time should be the current time.
Step 6 Click Save as to the history alarms as required.
----End
2-14

Issue 02 (2008-6-20)

Related Information
A history alarm is an alarm that has been cleared.

Periodically browsing abnormal events helps you to find abnormalities in the equipment in a
timely manner.
Prerequisite
l

T2000
Procedure
Step 1 On the T2000, choose Fault > Browse Abnormal Events from the main menu.
.
All the abnormal events of the selected NE or NEs are displayed in Browse Abnormal
Events.
Step 3 Browse the abnormal events.
Step 4 Optional: Click Save as to save the abnormal events as required.
----End
Related Information
An abnormal event is an abnormality that arises in the system at a particular time rather than
persists for a period. Being different from alarms, an abnormal event has only occurrence time,
with clearance time not provided.
2.3.5 Browsing the Current Performance Events of the SDH/PDH

Browsing the current performance events helps you to check the long-term running status of the
equipment. Hence, the latent hazards can be cleared in time.
Prerequisite
l

T2000
Issue 02 (2008-6-20)

2-15

Procedure
Step 1 On the T2000, choose Performance > Browse SDH Performance from the main menu, and
than select Current Performance Data.

Step 4 Select 15-Minute in the Monitor Period field.
Step 5 Select Count, select Select All in the displayed tab page, and select Consecutive Severely
Errored Seconds in the right pane.
Step 6 Click Query to browse the current performance events.
In normal situations, no bit error performance events should be displayed, and the number of
pointer justification events should be less than six per day.
Step 7 Select Gauge , select Select All in the displayed tab page, and select Current Value and
Maximum/Minimum Value in the right pane.
Step 8 Click Query to browse the current performance events.
Compared with the history records, the gauge indicators, such as board temperature, do not
change drastically.
Step 9 Re-define the time span by setting Monitor Period to 24-Hour, and leave other fields
unchanged.
Step 10 Repeat Step 5 through Step 8 to query the performance events in a period of 24 hours.
----End
Related Information
The counter of current performance events measures all the performance events that arise
between the start time of the monitoring period and the current time.
2.3.6 Browsing the History Performance Events of the SDH/PDH

Browsing the history performance events helps you to check the long-term running status of the
equipment. Hence, the latent hazards can be cleared in time.
Prerequisite
l

T2000
Procedure
Step 1 On the T2000, choose Performance > Browse SDH Performance from the main menu, and
than select the History Performance Data tab.
2-16

Issue 02 (2008-6-20)


Step 5 Specify the start time and end time of a specific time span.
The time span starts from the time when the last history performance event browsing operation
was performed to the current time.
Step 6 Specify Data Source.
NOTE
If this is the first browsing operation, you should select Query from NE and Save to Database. Otherwise,
you should select Query from T2000. In this case, the history performance databases of the T2000 and
NE are synchronized.
Step 7 Select the Count tab page, and then select Select All.
Step 9 Click Save as to save the history performance events as required.
Step 10 Select Gauge, select Select All in the displayed tab page, and select Current Value and
Maximum/Minimum Value in the right pane.
Step 12 Click Save as to save the history performance events.
Step 13 Select 24-Hour in the Monitor Period field.
Step 14 Repeat Step 5 through Step 12 to browse the history performance events in a period of 24 hours.
----End
Related Information
For history performance events, an NE has only six 24-hour registers and sixteen 15-minute
registers for each performance indicator. Therefore, only the six most recent non-zero 24-hour
performance events and the sixteen most-recent non-zero 15-minute performance events can be
obtained from the NE. The T2000, however, automatically stores the history data reported by
NEs. Therefore, you can obtain the performance data generated in the last months.

Periodically testing the IF 1+1 switching helps you to check whether the equipment can be
normally switched.
Prerequisite
l

T2000
Issue 02 (2008-6-20)

2-17

Precautions
l
The IF 1+1 switching performed manually is a HSB switching. During the 1+1 protection
switching (< 500 ms), protection services are interrupted. Hence, you are recommended to
carry out 1+1 protection switching when the traffic is light.
Procedure
the Function Tree.
Step 2 Select the IF 1+1 Protection tab.
Step 4 In Slot Mapping Relation, right-click the IF board, and choose Manual Switch to
Protection from the shortcut menu.
Step 5 Click OK to begin the protection switching.
After the switching is complete, the Switching Status of Device of the working board should
be Manual Switching.
Step 9 In Slot Mapping Relation, right-click the IF board, and choose Clear from the shortcut menu.
Step 10 Click OK to restore the protection switching.
the Switching Status of Device of the working board should be Normal.
----End

Periodically testing the IF N+1 switching helps you to check whether the equipment can be
normally switched over.
Prerequisite
l

T2000
2-18

Issue 02 (2008-6-20)

Precautions
l
This task helps to check whether an NE implements the N+1 protocol properly and is
Procedure
the Function Tree.
Step 2 Select N+1 Protection tab.
Step 3 In Slot Mapping Relation, right-click a working unit, and choose Exercise switching from the
shortcut menu.
The system displays a prompt message indicating that the switching command is issued
successfully.
Step 4 Click OK.
The status of the working unit should be Exercise switching.
Step 7 In Slot Mapping Relation, right-click the protection unit or a working unit, and choose Clear
from the shortcut menu.
Step 8 Click OK.
The status of the working unit should be normal.
----End
2.3.9 Testing the Two-Fiber Bidirectional MSP Ring Switching

Periodically testing the two-fiber bidirectional MSP ring switching helps you to check whether
the equipment can be switched normally.
Prerequisite
l

T2000
Precautions
l
Issue 02 (2008-6-20)
This task helps to check whether an NE implements the MSP protocol properly and is
2-19


l
Procedure
Step 1 Select an NE from the Object Tree in the NE Explorer, and choose Configuration > Ring
MSP from the Function Tree.
Step 3 In Slot Mapping Relation, right-click East Line, and choose Exercise switching from the
shortcut menu.
board should be Excise ring switching.
Step 5 Right-click the selected line, and choose Clear excise ring switching from the shortcut menu.
board should be Normal.
Step 7 In Slot Mapping Relation, right-click West Line of the protection group selected in Step 2,
and choose Excise ring switching from the shortcut menu.
----End
2.4 Guide to Field IDU Maintenance

This guide describes how to carry out routine maintenance for the IDU and the equipment room
where the IDU is installed.
2.4.1 Cleaning the Air Filter

Periodically checking the air filter ensures that the air intake path of the fans is not blocked and
thus avoids over-high board temperature caused by degraded heat dissipation.
Prerequisite
None.

An air blower or a clean brush
Procedure
Step 1 Loosen the captive screws on the panel of the fan box.
Step 2 Move the cables away from the front of the panel of the fan box.
Step 3 Draw out the air filter at the left side.
2-20

Issue 02 (2008-6-20)

Step 4 Use an air blower or a clean brush to clean the air filter.
Step 5 After the cleaning, insert the air filter back to its original position.
Step 6 Tighten the screws on the panel of the fan box.
----End
2.4.2 Testing the Orderwire Phone

Periodically testing the orderwire phone helps you to check whether the orderwire facilities are
in good conditions and helps you to judge the quality of transmission links through the voice
quality.
Prerequisite
l
The NE has been correctly installed with an orderwire phone.
The orderwire data has been correctly configured.

None.
Procedure
Step 1 Check the status of the orderwire phone.
The orderwire phone should meet the following requirements:
l
The ringing switch is set to position ON.
The dialing mode switch is set to position T, which indicates the dual tone multi-frequency
mode.
Step 2 Make orderwire calls.

1.
Hook-off the orderwire phone and press the "TALK" button.

The red indicator on the front of phone set should be lit and you can hear the dialing prompt
tone.
2.
Make orderwire calls to other NEs.

The calls should be normal and the voice should be clear.
Step 3 Receive orderwire calls.

Issue 02 (2008-6-20)

2-21

1.
The maintenance personnel of other NEs make calls to the orderwire phone.
The phone should ring.
2.
Hook-off the phone, press the "TALK" button, and have a conversation.
The red indicator on the front of phone set should be lit. The call should be normal and the
voice should be clear.
----End
2.4.3 Checking the Equipment Room

Periodically checking the equipment room not only ensures that the equipment can operate
normally in appropriate temperature and humidity conditions, but also reduces the fault rate, and
increases the service life of the equipment.
Prerequisite
None.

None.
Procedure
Step 1 Record the reading of the thermometer in the equipment room.
The normal temperature should be between 5C and +45C.
Step 2 Record the reading of the humidity meter in the equipment room.
The normal humidity should be between 5% and 95%.
Step 3 Check whether the equipment room meets the disaster protection requirements.
Ensure the following points:
l
There should be portable foam fire extinguishers in the equipment room. The fire
extinguishers should be in their service life.
There should be no rain leakage or water penetration in the equipment room.
There should be no mice or insects in the equipment room.
Step 4 Clean the equipment room.

Ensure that there is no dust on the cabinets, on the equipment shells, in the equipment, on the
desks, or on the floor. The equipment should be tidy.
----End
2.5 Guide to Field Maintenance of Outdoor Equipment

This guide describes how to carry out routine maintenance on site for outdoor equipment.
2.5.1 Checking the ODU

Periodically checking the ODU helps you to find faults and hidden troubles of the ODU in a
timely manner.
2-22

Issue 02 (2008-6-20)

Prerequisite
None.

None.
Procedure
Step 1 Ensure that the ODU is located within the protected area of the lightning arrester.
For plain areas, the lightning arrester protects the area that is located within an angle of 45 under
it. For mountainous areas and the areas where lightning frequently occurs, the lightning arrester
protects the area that is located within an angle of 30 under it.
Step 2 Ensure that the ODU is reliably fixed on the antenna.
Step 3 Ensure that the ODU is not damaged.
Step 4 Ensure that the interface between the ODU and the antenna is waterproof.
Step 5 Ensure that the protection grounding cable of the ODU is firmly and reliably grounded.
----End
2.5.2 Checking the Hybrid Coupler

Periodically checking a hybrid coupler helps you to find faults and hidden troubles of the coupler
in a timely manner.
Prerequisite
None.

None.
Procedure
Step 1 Ensure that the coupler is located within the protected area of the lightning arrester.
Step 2 Ensure that the coupler is reliably fixed on the antenna.
Step 3 Ensure that the coupler is not damaged.
Step 4 Ensure that the interface between the coupler and the antenna is waterproof.
Step 5 Ensure that the interface between the coupler and the ODU is waterproof.
----End
Issue 02 (2008-6-20)

2-23

2.5.3 Checking the Antenna

Periodically checking an antenna helps you to find faults and hidden troubles of the antenna in
a timely manner.
Prerequisite
None.

None.
Procedure
Step 1 Ensure that the antenna is located within the protected area of the lightning arrester.
Step 2 Ensure that the antenna is reliably fixed on the mast.
Step 3 Ensure that the antenna radome is not damaged.
Step 4 Ensure that there is no accumulated water in the antenna.
Step 5 Check whether the fastening bolts on the antenna are loose. Check whether the antenna slants
from the original position. Ensure that the azimuth angle and the elevation angle of the antenna
meet the design requirements.
Step 6 In the case of split mounting, ensure that the installation parts (ODU adapter, antenna adapter,
and flexible waveguide) are installed firmly, and that the connectors are fastened.
----End
2.5.4 Checking IF Cables

Periodically checking the IF cables helps you to find faults and hidden troubles of the cables in
a timely manner.
Prerequisite
None.

None.
Procedure
Step 1 Check the appearance of cables.
2-24
There should be no bent or twisted cable.
There should be no bare copper wire.

Issue 02 (2008-6-20)

l
The bending radius of the cable should be greater than 30 cm.
Step 2 Check the cable connectors.

l
The cable connector should be reliably connected to the ODU.
The cable connector should be waterproof.
Step 3 Check the grounding of the cables.

l
The grounding clip should be waterproof.
The grounding cable should be routed from top downwards. The angle between the grounding
cable and the IF cable should not be more than 15 degrees.
----End
Issue 02 (2008-6-20)

2-25

3 Emergency Maintenance Guide
Emergency Maintenance Guide
About This Chapter

Emergency maintenance is performed when emergencies arise or possible emergencies owing
to natural disasters may arise during the operation of the equipment.
3.1 Definition of Emergency
For the microwave equipment, an emergency situation is depicted as a situation where the
microwave services are interrupted.
3.2 Purposes of Emergence Maintenance
Being different from troubleshooting, which aims at locating and rectifying the faults, emergency
maintenance is performed to recover the normal operation of a system or a device rapidly.
3.3 Procedure of Emergency Maintenance
The procedure of emergency maintenance consists of a main procedure and a sub-procedure that
handles faults on site.
Issue 02 (2008-6-20)

3-1

3.1 Definition of Emergency

For the microwave equipment, an emergency situation is depicted as a situation where the
microwave services are interrupted.
3.2 Purposes of Emergence Maintenance

Being different from troubleshooting, which aims at locating and rectifying the faults, emergency
maintenance is performed to recover the normal operation of a system or a device rapidly.
3.3 Procedure of Emergency Maintenance

The procedure of emergency maintenance consists of a main procedure and a sub-procedure that
handles faults on site.
NOTE
In the case of emergency events, the customers in China can contact our 24-hour technical support center at
400-830-2118, and the customers in areas outside China can contact the local Huawei offices.
3-2

Issue 02 (2008-6-20)

Main Procedure of Emergency Maintenance

Figure 3-1 Main procedure of emergency maintenance
Start
1
Maloperation?
Yes
Cancel the operation
No
2
Service interrupted by
external causes?
Yes
Contact related
departments to handle
the problem
No
3
Query NE status and alarms

by using the T2000
4
NE access successful
and alarms cleared?
Yes
Handle the alarm
No
Rectify the fault on site
Go to the next step
5
Check the fault handling
result
No
Service restored?
Yes
End
Issue 02 (2008-6-20)

3-3

Table 3-1 Description of the main procedure of emergency maintenance

Comment
No.
Description
The common maloperations are as follows:

l
Modifying the data configurations
Performing loopback operations
Shutting down the laser
Muting the ODU
Changing boards/cables
Loading software
Faults owing to external causes, such as faults of the power supply, cables,
environment, and terminal equipment (such as switching devices).
If you want to perform integrated network management by using the Web

LCT, you can see 2.2.1 Checking the Status of NEs and Boards and 2.2.2
Browsing the Current Alarms for details.
If you want to perform integrated network management by using the T2000,

you can see 2.3.1 Checking the Status of NEs and Boards and 2.3.2
Browsing the Current Alarms for details.
The following alarms can be cleared through the

NM:APS_MANUAL_STOP, ALM_GFP_dLFD, APS_FAIL,
BD_NOT_INSTALLED, DBMS_ERROR, ESN_INVALID, FCS_ERR,
HP_TIM, HP_UNEQ, J0_MM, LOOP_ALM, LPS_UNI_BI_M,
LP_SIZE_ERR, LP_SLM, LP_SLM_VC12, LP_SLM_VC3, LP_TIM,
LP_TIM_VC12, LP_TIM_VC3, LP_UNEQ, LP_UNEQ_VC12,
LP_UNEQ_VC3, MSSW_DIFFERENT, NESF_LOST,
NESTATE_INSTALL, NO_BD_SOFT, RADIO_MUTE,
WRG_BD_TYPE, and WRG_DEV_TYPE.
After the fault is handled, proceed as follows:

1. Check the alarms, and ensure that the system is running smoothly.
2. Arrange personnel to watch and guard the system during the peak service
hours, and be sure to solve the problems promptly, if any.
3. Fill in the sheet for on-site operations, record the fault symptoms and
handling results, and then send them to Huawei. Table 3-2 shows the sheet
for on-site operations.
Table 3-2 Sheet for on-site operations

Maintained on: year month day
Actual Step
3-4
; maintained by:
Step in the Whole

Procedure
Handling Result

Remarks
Issue 02 (2008-6-20)

Maintained on: year month day

Actual Step
Issue 02 (2008-6-20)
; maintained by:
Step in the Whole

Procedure
Handling Result

Remarks
3-5

Procedure of On-Site Fault Handling

Figure 3-2 Procedure of on-site fault handling
Start
Obvious
equipemnt
damage?
Yes
Repair or replace the

equipment
No
PWR indicator of
PXC lights?
2
No
Handle the power

input alarm
Yes
Browse alarms
by using the
Web LCT
3
Equipment
alarm?
Yes
Handle the alarm
No
4
Line alarm?
Yes
Handle the alarm
No
5
High order
path alarm?
Yes
Handle the alarm
No
6
Low order
path alarm?
Yes
Handle the alarm
No
SDH/PDH
interconnection
fault?
Yes
7
Handle the fault
No
Ethernet
service fault?
No
Locate fault by using
section-by-section
loopback
Yes
8
Handle the fault
Go to the next step
No
Service restored?
Yes
End
3-6

Issue 02 (2008-6-20)

Table 3-3 Procedure of on-site fault handling

Comment
No.
Description
The handling procedure is as follows:

1. Check whether the air circuit breaker for the input power is off. If the air
circuit breaker is automatically turned off, identify the cause (such as short
circuits or insufficient fuse capacity), and handle the fault accordingly.
2. Check the power cables, especially the power connectors, and replace the
power cables or re-make power connectors if required.
3. Check the voltage and polarization of the input power. If the voltage or
polarization of the input power does not meet the requirements, contact the
power engineers and handle the fault.
NOTE
For detailed specifications of the fuse capacity and input power, refer to section
"Powering On the Equipment" in the OptiX RTN 600 Radio Transmission System IDU
610/620 Commissioning Guide.

1. Refer to the OptiX RTN 600 Radio Transmission System IDU 610/620
Commissioning Guide and access the Web LCT.
2. Refer to the OptiX RTN 600 Radio Transmission System IDU 610/620
Configuration Guide and log in to the NEs.
3. Refer to 2.2.2 Browsing the Current Alarms, and browse the current
alarms.
NOTE
If you fail to log in to a created NE, ensure that the operations you performed are correct,
and then identify and rectify the fault according to the indicators of the PXC and SCC.
For details about the indicators, refer to the OptiX RTN 600 Radio Transmission System
IDU 610/620 Hardware Description.
Issue 02 (2008-6-20)
Pay special attention to the following alarms:

l
HARD_BAD
POWER_ALM
FAN_FAIL
BD_STATUS
SYN_BAD
NESF_LOST
TEMP_ALARM
RADIO_RSL_HIGH
RADIO_RSL_LOW
RADIO_TSL_HIGH
RADIO_TSL_LOW
IF_INPWR_ABN
IF_CABLE_OPEN
VOLT_LOS

3-7

Comment
No.
Description
3-8
MW_LIM
MW_LOF
R_LOS
R_LOF
R_LOC
MS_AIS
AU_AIS
AU_LOP
B1_EXC
B2_EXC

l
HP_LOM
B3_EXC
HP_UNEQ

l
TU_AIS
TU_LOP
BIP_EXC
P_LOS
LP_UNEQ
T_ALOS
E1_LOC
See 4.6 Troubleshooting the Interconnection with the SDH Equipment or

4.7 Troubleshooting the Interconnection with the PDH Equipment.
See 4.8 Troubleshooting Ethernet Service Faults.

Issue 02 (2008-6-20)

4 Troubleshooting Guide
Troubleshooting Guide
About This Chapter

This guide describes the general troubleshooting procedures for the OptiX RTN 600 and provides
troubleshooting methods for common faults.
4.1 General Fault Locating Procedures
When handling a fault, make a detailed record of the fault phenomenon. Contact Huawei
engineers to report problems and obtain technical support.
4.2 Troubleshooting Service Interruptions
When services cannot be transmitted due to an equipment failure or link failure, the services are
interrupted.
4.3 Troubleshooting Microwave Links
When an NE reports MW_LOF or MW_FECUNCOR due to failure or performance degrade of
a microwave link, there is a microwave link fault.
4.4 Troubleshooting Bit Errors
When an NE reports an alarm or performance event on the regenerator section (RS), multiplex
section (MS), higher order path (HP), or lower order path (LP), there are bit errors in services.
4.5 Troubleshooting Pointer Justifications
When an NE reports a large amount of justification events of the administrative unit (AU) pointer
or the tributary unit (TU) pointer, there are pointer justification faults.
4.6 Troubleshooting the Interconnection with the SDH Equipment
In the case that the OptiX RTN 600 is interconnected with the SDH equipment, if the SDH
service cannot be transmitted between the equipment sets, there is an interconnection fault.
4.7 Troubleshooting the Interconnection with the PDH Equipment
In the case that the OptiX RTN 600 is interconnected with the PDH equipment, if the PDH
4.8 Troubleshooting Ethernet Service Faults
An Ethernet service fault might be Ethernet service interruption or Ethernet service degradation.
4.9 Troubleshooting the Orderwire
If orderwire calls cannot get through when services are normal, there is an orderwire fault.
Issue 02 (2008-6-20)

4-1

4.1 General Fault Locating Procedures

When handling a fault, make a detailed record of the fault phenomenon. Contact Huawei
engineers to report problems and obtain technical support.
4-2

Issue 02 (2008-6-20)

Figure 4-1 General fault locating procedures

Start
1
Record the fault phenomenon
Caused by external factors?
Yes
Other handling procedures
No
Analyze fault causes and locate
the fault
Is the fault cleared?

4
Yes
No
Report to Huawei
Make a solution together
Attempt to clear the fault
No
Is the service restored?

Yes
Observe the operating
No

Yes
Fill in the fault handling report
End
Issue 02 (2008-6-20)

4-3

Table 4-1 Flow description

Note
Description
When recording the fault phenomenon, make a true and detailed record of the
entire process of the fault. Record the exact time when the fault occurs, and
the operations done before and after the occurrence of the fault. Save the
alarms, performance events, and other important information.
Faults that are caused by external factors include power failures, fiber faults,
environmental faults, and terminal equipment (like switching equipment)
faults.
If the fault is caused by the equipment, refer to 4.2 Troubleshooting Service

Interruptions.
Contact Huawei engineers to report problems and obtain technical support.
4.2 Troubleshooting Service Interruptions

When services cannot be transmitted due to an equipment failure or link failure, the services are
interrupted.
Fault Causes
l
There are maloperations.

The data is wrongly modified. A board/cable is looped back or replaced.
The protection switching fails.
The transmission NE or link is faulty.
There is an interconnection fault.

If the transmission equipment and connections are working normally, check if there is a
fault in the interconnection between the transmission equipment and the switching
equipment.
Fault Locating Methods

1.
Check out the operations done before the service interruption.
2.
Analyze alarms.
If several NEs report alarms, analyze the alarms in the following sequence: switching failure
alarms, equipment alarms, line alarms, HP alarms, and LP alarms.
3.
Perform loopback operations section by section. Or replace components.
CAUTION
If the fault cannot be removed in a short time, first restore services. Adjust service routes or
perform a forced switching operation to restore services.
4-4

Issue 02 (2008-6-20)

Fault Locating Procedures

Figure 4-2 Flow of handling service interruptions
Start
1
Maloperation?
Yes
No
2
Service interrupted
by external causes?
Yes
Contact related
departments to handle
the problem
No
3
Query NE status and alarms

by using the T2000
4
NE access successful
and alarms cleared?
Yes
Handle the alarm
No
No
Rectify the fault on site
Go to the next step
Service restored?
Yes
End
Issue 02 (2008-6-20)
Note
Description
Operations that may cause a service interruption are as follows:

l
Modifying the data configuration
Performing loopback operations
Shutting down the laser
Muting the ODU
Replacing boards/cables

4-5

4-6
Note
Description
Faults owing to external causes, such as faults of the power supply, cables,
environment, and terminal equipment (such as switching devices).
The following alarms can be cleared through the

T2000:APS_MANUAL_STOP, ALM_GFP_dLFD, APS_FAIL,
BD_NOT_INSTALLED, DBMS_ERROR, ESN_INVALID, FCS_ERR,
HP_TIM, HP_UNEQ, J0_MM, LOOP_ALM, LPS_UNI_BI_M,
LP_SIZE_ERR, LP_SLM, LP_SLM_VC12, LP_SLM_VC3, LP_TIM,
LP_TIM_VC12, LP_TIM_VC3, LP_UNEQ, LP_UNEQ_VC12,
LP_UNEQ_VC3, MSSW_DIFFERENT, NESF_LOST,
NESTATE_INSTALL, NO_BD_SOFT, RADIO_MUTE,
WRG_BD_TYPE, and WRG_DEV_TYPE.
Pay special attention to:

l
MW_LIM
MW_LOF
R_LOS
R_LOF
MS_AIS
AU_AIS
AU_LOP
B1_EXC
B2_EXC

Issue 02 (2008-6-20)

Figure 4-3 Procedure of on-site fault handling

Start
Obvious
equipemnt
damage?
Yes
Repair or replace the

equipment
No
PWR indicator of
PXC lights?
2
No
Handle the power

input alarm
Yes
Browse alarms
by using the
Web LCT
3
Equipment
alarm?
Yes
Handle the alarm
No
4
Line alarm?
Yes
Handle the alarm
No
5
High order
path alarm?
Yes
Handle the alarm
No
6
Low order
path alarm?
Yes
Handle the alarm
No
SDH/PDH
interconnection
fault?
Yes
7
Handle the fault
No
Ethernet
service fault?
No
Locate fault by using
section-by-section
loopback
Yes
8
Handle the fault
Go to the next step
No
Service restored?
Yes
End
Issue 02 (2008-6-20)

4-7

Experience and Summary

Carry out routine maintenance to reduce the probability that the equipment becomes faulty. Solve
the problems before the services are affected.
4.3 Troubleshooting Microwave Links

When an NE reports MW_LOF or MW_FECUNCOR due to failure or performance degrade of
a microwave link, there is a microwave link fault.
The key to locate a microwave link fault is to check whether the transmit power and the receive
power are abnormal, and to check whether there is external interference.
In the following two cases, the transmit power is abnormal. The first case is that the transmit
power exceeds the range that the ODU supports. The second case is that the difference between
the transmit power and the set value is more than 2 dB when the ATPC is disabled. The relevant
alarms and performance events are as follows:
l
RADIO_TSL_HIGH
RADIO_TSL_LOW
TSL_CUR
TSL_MAX
TSL_MIN
NOTE
For the range of the transmit power, refer to the OptiX RTN 600 Radio Transmission System Product
Description.
In the following two cases, the RSL is abnormal. The first case is that the RSL always fails to
reach the ideal value, which should be greater than the RSL in free space minus 6 dB. If the RSL
in free space is unknown, you can take the RSL designed in network planning as the lower
threshold of the ideal value. The second case is that the receive power is lower than the receiver
sensitivity or higher than the free space receive power due to fading. The relevant alarms and
performance events are as follows:
l
RADIO_RSL_HIGH
RADIO_RSL_LOW
RSL_CUR
RSL_MAX
RSL_MIN
NOTE
For the receiver sensitivity, refer to the OptiX RTN 600 Radio Transmission System Product Description.
Generally, external interference is classified into co-channel interference and adjacent channel
interference.
4-8
Co-channel interference is crosstalk from two different radio transmitters reusing the same
frequency channel. Therefore, the entire spectrum may be impaired.
Adjacent channel interference is signal impairment to one frequency due to presence of

another signal on a nearby frequency. Therefore, a part of the spectrum is impaired.
Issue 02 (2008-6-20)

Because interference is closely related to the frequency in use, the microwave link may be faulty
in one direction.
Fault Causes
Table 4-3 Causes of microwave link faults
Fault
Common Fault Causes
The transmit power is

abnormal.
The ODU is faulty.
The receive power is always

lower than the ideal value.
The antenna direction is not properly adjusted.
The antennas have different polarization directions.
There is a mountain or obstacle in the transmit direction.
The performance of the feeder degrades.
The receive power is

abnormal due to slow upfading.
There is an external interference.

abnormal due to slow downfading.
The fading margin is not enough.

abnormal due to fast fading.
The multipath fading is severe.
The microwave link is faulty

in one direction.
There is external interference.
NOTE
Depending on the received level, there is up-fading and down-fading.

l
Up-fading
The received level is higher than the value after free space fading. The difference can be 10-odd decibels.
Down-fading
The received level is lower than the value after free space fading. The difference can be tens of decibels.
Depending on the fading time, there is fast fading and slow fading.
l
Fast fading
The fading duration time ranges from several milliseconds to tens of seconds.
Slow fading
The fading duration time ranges from tens of seconds to several hours.
Because fast fading and slow fading are imposed by the propagation paths, the microwave link may be faulty
in both directions.

1.
Issue 02 (2008-6-20)
Check whether the ODU is mute, powered off, or looped back. Check whether the data
configuration is correct.
4-9
4-10

2.
Check whether the ODU and the IF board are faulty.
3.
If the transmit power is abnormal, replace the ODU.
4.
If the receive power is abnormal, check out the possible causes based on the fading type.
5.
If the microwave link is faulty in only one direction, check whether there is interference
before you proceed.
6.
If the transmit/receive power is normal, perform loopback operations.

Issue 02 (2008-6-20)


Figure 4-4 Flow of handling microwave link faults
Start
Is there a wrong
operation?
Yes
No
2
Is there an ODU or IF
board related fault?
Yes
No
No
Handle the alarm
Normal transmit power?
Handle the fault
Yes
The receive power
always lower than the
ideal value?
Yes
4
Handle the fault
No
Abnormal receive
Yes
power caused by slow upfading?
5
Handle the fault
No
6
Abnormal receive
power caused by slow
down-fading?
Yes
Handle the fault
No
7
Abnormal receive
power caused by fast
fading?
Yes
Handle the fault
No
8
Microwave link
fault in one
direction?
Yes
Handle the fault
No
9
Perform loopback operations
Go to the next step
No

Yes
End
Issue 02 (2008-6-20)

4-11


Note
Description
Check the following points:
Check whether the ODU is powered off.
Check whether the ODU is muted.
Check whether the IF board is looped back.
Check whether the data configuration at the transmit side is consistent with
that at the receive side.
Check whether the data configuration matches the type of the ODU and
the hybrid coupler.

l
HARD_BAD
TEMP_ALARM
IF_INPWR_ABN
RADIO_MUTE
RADIO_TSL_HIGH
RADIO_TSL_LOW
RADIO_RSL_HIGH
IF_CABLE_OPEN
Replace the ODU.
Follow the steps below:

1. Check the installation of the antenna. Check whether the azimuth angle of
the antenna meets the requirement.
2. Check the antenna direction. Check whether the received signal is from the
main lobe.
If the antenna direction does not meet the requirement, adjust the antenna
in a wide range.
3. Check whether the setting of the polarization direction of the antenna is
correct. Adjust wrong polarization direction.
4. Check whether the antenna gain at both the transmit and receive sides meets
the indexes. Replace unqualified antennas.
5. Check whether there is a mountain or obstacle in the transmit direction.
4-12

Issue 02 (2008-6-20)

Note
Description
1. Check whether there is co-channel interference.

1. Mute the opposite ODU.
2. Check the RSL at the local end. If the RSL exceeds 90 dBm, you can
infer that there is co-channel interference that may impair the long-term
availability and performance of the system.
2. Use a spectrum analyzer to analyze the interference source.
3. Contact the spectrum management department to clear the interference
spectrum or change plans to reduce the interference.
Issue 02 (2008-6-20)
Contact the network planning department to make the following changes:

l
Increase the installation height of the antenna.
Reduce the transmission distance.
Increase the antenna gain.
Increase the transmit power.
Contact the network planning department to make the following changes:

l
Adjust the position of the antenna to block the reflected wave or make the
reflection point fall on the ground that has a small reflection coefficient,
thus reducing the multipath fading.
Adjust the RF configuration to make the links in the 1+1 SD configuration.
For the links in the 1+1 SD configuration, adjust the height difference
between two antennas to make the receive power of one antenna much
stronger than that of another.
Increase the fading margin.

4-13

Note
Description

1. Check whether there is co-channel interference.
2. Check the RSL at the local end. If the RSL exceeds 90 dBm, you can
infer that there is co-channel interference that may impair the long-term
availability and performance of the system.
2. Check whether there is adjacent channel interference.
2. Adjust the microwave working mode at the local end and use the
minimum channel spacing.
3. Decrease the received frequency at the local end by a half of the channel
spacing.
4. Test and record the RSL.
5. Increase the received frequency at the local end, with a step length of
0.5 MHz or 1 MHz, and record the RSL accordingly until the received
frequency is equal to the original received frequency plus a half of the
channel spacing.
6. Compare the recorded RSLs, and check whether the RSL in a certain
spectrum is abnormal if the received frequency is within the permitted
range.
3. Use a spectrum analyzer to analyze the interference source.
4. Contact the spectrum management department to clear the interference
spectrum or change plans to reduce the interference.
1. Loop back the IF ports.

If the fault is not cleared after the loopback, replace the IF board.
2. Check whether the IF cable is soggy, broken or pressed. Replace the
unqualified cable.
3. Check whether the cable connector is made in accordance with
specifications. Remake unqualified ones.
4. Replace the ODU.
If the fault is cleared after the replacement, the original ODU is faulty.
5. Replace the IF cable.
If the fault is cleared after the replacement, the original IF cable is faulty.
4-14
During a commissioning process, make sure that the antenna direction is correctly adjusted
to avoid possible incipient faults.
Periodically collect the change data of the transmit power and receive power, and analyze
the change data to remove incipient faults in time.

Issue 02 (2008-6-20)

4.4 Troubleshooting Bit Errors

When an NE reports an alarm or performance event on the regenerator section (RS), multiplex
section (MS), higher order path (HP), or lower order path (LP), there are bit errors in services.
The line board detects RS bit errors by the RS overhead byte B1. Related alarms and performance
events are listed below:
l
B1_EXC
B1_SD
RS_CROSSTR
RSBBE
RSES
RSSES
RSCSES
RSUAS
NOTE
When the IF board works in the PDH mode, the above RS bit error alarms and performance events may also be
reported. Such alarms and performance events are detected by the B1 that is defined in the PDH microwave
frame.
The line board detects MS bit errors by the MS overhead byte B2. Related alarms and
performance events are listed below:
l
B2_EXC
B2_SD
MS_CROSSTR
MSBBE
MSES
MSSES
MSCSES
MSUAS
The line board detects HP bit errors by the HP overhead byte B3. Related alarms and performance
events are listed below:
Issue 02 (2008-6-20)
B3_EXC
B3_SD
HP_CROSSTR
HPBBE
HPES
HPSES
HPCSES
HPUAS
4-15

LP bit errors are detected by PDH service processing boards or Ethernet service processing
boards using the VC-3 overhead byte B3 or VC-12 overhead byte V5. Related alarms and
performance events are listed below:
l
B2_EXC
B2_SD
B3_EXC_VC3_
B3_SD_VC3
BIP_EXC
BIP_SD
LP_CROSSTR
VC3BBE
VC3ES
VC3SES
VC3CSES
VC3UAS
LPBBE
LPES
LPSES
LPCSES
LPUAS
Fault Causes
Table 4-5 Causes of bit errors
Fault Type
Common Cause
There are some RS bit errors.
The line is faulty.
For the optical fiber line, the optical power is abnormal,

the fiber performance degrades, or the fiber connector
is not clean.
For the STM-1 cable line, the cable performance

degrades, the cable is not properly grounded, or the cable
connector is not in good contact.
For the microwave line, check whether there is an

MW_FECUNCOR alarm or an HSB_INDI alarm.
The line board is faulty.
The clock unit is faulty.
The quality of the clock over the network degrades.

When the quality of the clock over the network degrades,
there will be a pointer justification event.
4-16

Issue 02 (2008-6-20)

Fault Type
Common Cause
There is no RS bit error, but

there are MS bit errors or HP
bit errors.
The quality of the clock over the network degrades.
There are only LP bit errors.
When the quality of the clock over the network degrades,

there will be a pointer justification event.
l
The working temperature of the line board is excessively

high.
There is power surge or an external interference source, or

the equipment is not properly grounded.
The PDH service processing board or the Ethernet service

processing board is faulty.
The cross-connect unit is faulty.
The working temperature of the PDH service processing

board or the Ethernet service processing board is
excessively high.
The working temperature of the cross-connect unit is

excessively high.
There is power surge or an external interference source, or

the equipment is not properly grounded.
Issue 02 (2008-6-20)
1.
Analyze the equipment alarms and performance events that are related to bit errors.
2.
When there are many types of alarms and performance events, first analyze RS bit errors,
then MS bit errors, HP bit errors, and finally LP bit errors.
3.
When multiple paths have bit errors, first check whether the overlapping part is faulty.
4.
When the fault is not located after you analyze the alarms and performance events, perform
loopback operations section by section.
5.
For a possibly degraded component, replace it with a new one.

4-17


Figure 4-5 Flow of handling bit errors
Start
2
1
Is there an
equipment alarm?
Yes
Handle the alarm
No
Is there a pointer
justification event?
Yes
Handle the pointer

justification event
SDH optical
interface board
No
3
Handle the RS bit error of the
SDH optical interface board
4
Is there an
RS bit error alarm or a
performance
event?
Yes
If the
alarming
board is
IF board Handle the RS bit error of the

IF board
STM-1 electrical
interface board
No
Is there an
MS/HP alarm or a
performance
event?
5
Handle the RS bit error of the
STM-1 electrical interface
board
6
Yes
No
Handle the MS/HP bit error
Is there an LP alarm?
Yes
Handle the LP bit error
No
Go to the next
step
No
Perform loopback operations

section by section
Yes
End
4-18
Note
Description

l
TEMP_ALARM
SYN_BAD
HARD_BAD

Issue 02 (2008-6-20)

Note
Description
Refer to 4.5 Troubleshooting Pointer Justifications.

1. Make an exchange between the Tx fiber core and the Rx fiber core at both
ends of the path. If bit errors change after the exchange, the fiber is faulty.
Otherwise, the equipment at the two ends is faulty.
2. In the case that the fiber is faulty, check whether the fiber between the
equipment and the ODF and the section of the fiber that is led out of the
equipment room are pressed. Also check whether the fiber connector is
clean.
3. In the case that the equipment at the two ends is faulty, use a fiber jumper
to loop back the optical ports. After the loopback, if the fault is not cleared,
the line board is most likely faulty.
4. For the case that the equipment at the two ends is faulty, to locate the fault,
you can also replace the board or make an exchange between the board and
another board of the same type that is working normally. If the alarm
changes after the exchange, the board is faulty.

1. Check whether there is an MW_FECUNCOR alarm or an HSB_INDI
alarm.
2. If yes, refer to 4.3 Troubleshooting Microwave Links.
3. If no, replace the IF board.

1. Make an exchange between the Tx cable and the Rx cable at both ends of
the path. If bit errors change after the exchange, the cable is faulty.
Otherwise, the equipment at the two ends is faulty.
2. In the case that the cable is faulty, check the cable connector. Also check
whether the cable is properly grounded and if the cable is broken.
3. In the case that the equipment at the two ends is faulty, use a cable to loop
back the electrical ports. After the loopback, if the fault is not cleared, the
line board is most likely faulty.
4. For the case that the equipment at the two ends is faulty, to locate the fault,
you can also replace the board or make an exchange between the board and
another board of the same type that is working normally. If the alarm
changes after the exchange, the board is faulty.

1. Loop back the alarming line board.
If the fault is not cleared, replace the line board.
If the fault is cleared, replace the line board at the transmit side.
2. If the fault is still not cleared, check whether there is power surge or an
external interference source, or if the equipment is not properly grounded
(primarily for the SDH electrical interface board).
Issue 02 (2008-6-20)

4-19

Note
Description

1. Based on how the service paths that have bit errors overlap each other,
replace the PDH service processing board or the Ethernet service
processing board or the cross-connect board.
2. If the fault is not cleared, check whether there is power surge or an external
interference source, or if the equipment is properly grounded.

l
Take it as a routine job to check bit error performance events and handle them in time.
To locate a fault, primarily use the method of analyzing alarms and performance events.
Take the loopback method and the replacement method as a supplement.
4.5 Troubleshooting Pointer Justifications

When an NE reports a large amount of justification events of the administrative unit (AU) pointer
or the tributary unit (TU) pointer, there are pointer justification faults.
When the position of the first byte of the VC-4 in the AU-4 payload changes, the AU pointer
makes a justification accordingly. The performance events of the AU pointer justification are as
follows:
l
AUPJCHIGH
AUPJCLOW
AUPJCNEW
NOTE
The AU pointer justification is generated at an upstream NE but is detected and reported at a downstream NE.
When the service is configured to be at the VC-12 level, apply the re-framing process to terminate
the AU pointer justification. The terminating method is to transform the AU pointer justification
into the TU pointer justification. The performance events of the TU pointer justification are as
follows:
l
TUPJCHIGH
TUPJCLOW
TUPJCNEW
NOTE
The TU pointer justification is generated at the NE where the AU pointer is transformed into the TU pointer,
but is detected and reported by the tributary board of the NE where services are terminated.
Fault Causes
4-20
The clock sources or the clock source levels are wrongly configured. As a result, there are
two clock sources in the same network or mutual clock tracing occurs.
The optical fibers links are wrongly connected. As a result, mutual clock tracing occurs.
Issue 02 (2008-6-20)

The quality of the clock source degrades. The clock unit is faulty. Or there are other clock
related faults.
The tributary board is faulty (only for the TU pointer justification).

When there are both AU pointer justifications and TU pointer justifications in a service path,
first handle AU pointer justifications and then TU pointer justifications.
Fault Types
AU pointer justifications
1. Analyze and clear clock alarms.

2. Correct wrong data configurations and wrong fiber
connections.
3. Change the clock and service configurations to find the
stations whose clock is asynchronous with the entire
network.
4. Replace the components whose performance is possibly
poor or degraded to locate a fault.
TU pointer justifications
1. Analyze and clear clock alarms.

2. Correct wrong data configurations and wrong fiber
connections.
3. Change the clock and service configurations to find the
stations whose clock is asynchronous with the entire
network.
4. Replace the components whose performance is possibly
poor or degraded to locate a fault.
Issue 02 (2008-6-20)

4-21


Figure 4-6 Flow of handling pointer justifications
Start
1 Is there a clock related

alarm?
2
Yes
Handle the alarm
No
Check the clock
configuration
Yes
Wrong configuration?
Modify the data

configuration
No
Check the fiber connection
Wrongly connected?
Yes
Re-connect the fiber
No
4
Find the NE whose clock is
out of synchronization
Is there an AU pointer Yes

No
Is there a TU pointer
6
Yes
Locate the faulty board
Find the NE whose clock is

out of synchronization
No
Go to the next step
Find the faulty board
No
Yes
End
4-22

Issue 02 (2008-6-20)


Note
Description
TEMP_ALARM
SYN_BAD
HARD_BAD
LTI
SYNC_C_LOS
S1_SYN_CHANGE
EXT_SYNC_LOS

l
Check whether there are two clock reference sources in the entire network.
Check whether mutual clock tracing occurs.
Query ECC routes to check if the fibers are correctly connected. Check the fiber
connection in the east and west directions of the NE that reports the pointer
justification event.

1. Find a VC-4 channel that reports an AU pointer justification event.
2. Along the service source direction of the VC-4 channel, find the source NE of
the entire VC-4 service (not the source NE of a timeslot in the VC-4).
3. Set the clock of the source NE to free-run. Set other NEs to trace the clock of
the source NE along the direction of the VC-4 service.
4. Along the clock tracing direction, find the line board that is the first to report
the AU pointer justification of the VC-4 channel.
The clock of the remote NE to which the line board is connected is
asynchronous with the reference clock. Hence, the line board in the remote NE
that receives the clock signal, the line board that sends the clock signal to the
remote NE, and the clock unit of the remote NE, may be faulty.
5. Set the clock of the sink NE of the VC-4 service to free-run. Set other NEs to
trace the clock of the sink NE along the direction of the VC-4 service.
6. Along the clock tracing direction, find the line board that is the first to report
the AU pointer justification of the VC-4 channel.
The clock of the remote NE to which the line board is connected is
asynchronous with the reference clock. Hence, the line board in the remote NE
that receives the clock signal, the line board that sends the clock signal to the
remote NE, and the clock unit of the remote NE, may be faulty.
7. Compare the results and find out the common points.
Issue 02 (2008-6-20)
Replace the possibly faulty boards.

4-23

Note
Description

1. Modify the service configuration to make the NE where the clock reference
source is as the central NE. Other NEs has the E1 service of the central NE.
2. Along the clock tracing direction, find the NE that is the first to report the TU
pointer justification.
The clock of the NE is asynchronous with the reference clock. Hence, the line
board in the NE that receives the clock signal, the line board that sends the
clock signal to the NE, and the clock unit of the NE, may be faulty.
3. Modify the configuration data to make all NEs trace the clock in another
direction.
4. Along the clock tracing direction, find the NE that is the first to report the TU
pointer justification.
The clock of the NE is asynchronous with the reference clock. Hence, the line
board in the NE that receives the clock signal, the line board that sends the
clock signal to the NE, and the clock unit of the NE, may be faulty.
5. Compare the results and find out the common points.
NOTE
This method is also applicable in locating an AU pointer justification event.
Replace the possibly faulty boards. For a TU pointer justification, check the line
board, the clock board, and the tributary board.

In a well synchronized network, there are few pointer justifications (less than six per day). Hence,
monitoring the pointer of an SDH transmission system is an effective way to check the
synchronization of the system.
4.6 Troubleshooting the Interconnection with the SDH

Equipment
In the case that the OptiX RTN 600 is interconnected with the SDH equipment, if the SDH
Fault Causes
l
The VC-12 numbering method of OptiX equipment is different from that of some vendors'
equipment.
The OptiX equipment applies the timeslot numbering method. The numbering formula is:
VC-12 number = TUG-3 number + (TUG-2 number - 1) x 3 + (TU-12 number - 1) x 21.
This method is also called ordering method.
Some equipment applies the line numbering method. The numbering formula is: VC-12
number = (TUG-3 number - 1) x 21 + (TUG-2 number - 1) x 3 + TU-12 number. This
method is also called interval method.
4-24

Issue 02 (2008-6-20)

The overhead bytes at the two sides are inconsistent.
The indexes of SDH interfaces do not meet requirements.
The equipment is not properly grounded (only for the STM-1 electrical interface).
NOTE
When the interconnected equipment is the ATM or Ethernet equipment, the common cause for the
interconnection fault is that the service is not set to the VC-4 pass-through service. As a result, the overheads
are processed in the terminating mode instead of the pass-through mode.

Analyze the fault phenomenon and alarms. Check the possible fault causes one by one.
Issue 02 (2008-6-20)

4-25


Figure 4-7 Flow of troubleshooting the interconnection with the SDH equipment
Start
Is the
interconnected equipment Yes
the ATM/IP equipment?
Set the interconnection

service to be the VC-4 passthrough service
No
Query the VC-12 numbering
method of the interconnected
equipment
Is the
numbering mode the
line numbering?
Yes
Modify the data configuration.

Use the line numbering
method to set the VC-12
No
1
Is there an overhead
setting related alarm?
Yes
No
Is the interface the
STM-1 electrical
interface?
3
Handle the alarm
2
Yes
Check the grounding
No
Test the indexes of interfaces
Do the interfaces meet

relevant standards?
Yes
No
Handle the faults of the

interconnected equipment
Go to the next
step
Handle the faults of the local
equipment
No

Yes
End
4-26

Issue 02 (2008-6-20)


Note
Description
J0_MM
HP_TIM
LP_TIM
LP_TIM_VC12
LP_TIM_VC3
HP_SLM
LP_SLM
LP_SLM_VC12
LP_SLM_VC3

l
Check if all the equipment and the DDF in the equipment room are jointly
grounded.
Check if the shielding layer of the coaxial cable connector on the DDF is
connected to the protection ground.
Check if the shielding layers of coaxial cables are grounded in the same
way.
NOTE
Disconnect all the signal cables between the interconnecting equipment. Use a
multimeter to measure the level between the shielding layers of the coaxial cables at the
receive and transmit ends of the SDH equipment. Also measure the level between the
shielding layers of the coaxial cables at the receive and transmit ends of the opposite
equipment. If the potential difference is large (about 0.5 V), the fault may be caused by
the grounding.
Common indexes of the optical interfaces:

l
Mean launched optical power
Extinction ratio
Operating wavelength of the laser
Receiver sensitivity
Overload optical power
Permitted frequency deviation of the input interface
Output jitter
Jitter and wander tolerance
Common indexes of the electrical interfaces:
Issue 02 (2008-6-20)
Permitted frequency deviation of the input interface
Allowed attenuation of the input interface
Input jitter and wander tolerance
Output jitter

4-27


To clear any interconnection fault, it is a must to have a sound knowledge of the characteristics
of the interfaces of the interconnected equipment.
4.7 Troubleshooting the Interconnection with the PDH

Equipment
In the case that the OptiX RTN 600 is interconnected with the PDH equipment, if the PDH
Fault Causes
l
There is an impedance mismatch between interfaces.
The equipment is not properly grounded.
The cable performance degrades.
The indexes of PDH interfaces do not meet requirements.

Analyze the fault phenomenon and alarms. Check the possible fault causes one by one.
4-28

Issue 02 (2008-6-20)


Figure 4-8 Flow of troubleshooting the interconnection with the PDH equipment
Start
1
Check the impedance of
the interfaces
Is there an
Yes
impedance mismatch?
No
Is the cable the
coaxial cable?
3
Replace the cable or the

tributary board
2
Yes
Check the grounding
No
Check the cables
Is in good conditions?
No
Adjust the cables
Yes
Test the indexes of
interfaces
Do the interfaces
meet standards?
Yes
No

Go to the next
step
No

Yes

local equipment
End
Issue 02 (2008-6-20)

4-29


Note
Description
Check whether the typeinterface impedance of the tributary board matches

the type of the cable.

l
Check whether all the equipment and the DDF in the equipment room are
jointly grounded.
Check whether the shielding layer of the coaxial cable connector on the
DDF is connected to the protection ground.
Check whether the shielding layers of coaxial cables are grounded in the
same way.
NOTE
Disconnect all the signal cables between the interconnecting equipment. Use a
multimeter to measure the level between the shielding layers of the coaxial cables at the
receive and transmit ends of the PDH equipment. Also measure the level between the
shielding layers of the coaxial cables at the receive and transmit ends of the opposite
equipment. If the potential difference is large (about 0.5 V), the fault may be caused by
the grounding.

l
Check whether the wires of the cable are correctly connected.
Check whether the cable is too long (for example, longer than 50 meters).
Check whether the cable is broken or pressed.
Check whether the cable signal is interfered (for example, when the trunk
cable is bound with the power cable, the cable signal is interfered by the
power signal).
Check the following indexes:

l
Input jitter tolerance
Permitted input frequency deviation
Input reflection attenuation
Output jitter
Output frequency deviation
Output waveform

Grounding problems are the most common reasons that cause an interconnection failure when
the OptiX RTN 600 is interconnected with the PDH equipment.
4.8 Troubleshooting Ethernet Service Faults

An Ethernet service fault might be Ethernet service interruption or Ethernet service degradation.
Ethernet service interruption indicates that the Ethernet service is completely interrupted.
Ethernet service degradation indicates that the Ethernet service is abnormal. For example, the
4-30

Issue 02 (2008-6-20)

network speed is low, the equipment delay is long, loss of packets occurs, or incorrect packets
exist in the received or transmitted data.
Fault Causes
l
Human factors are as follows:
An Ethernet board loopback or a transmission line loopback occurs.
The settings of parameters of an Ethernet port such as port enabled, working mode, and
flow control are different from those of its interconnected equipment.
The configuration of the encapsulation/mapping protocol or the LCAS protocol is

different from that of the opposite equipment.
The VCTRUNK-bound timeslot is different from that of the opposite equipment.
The service configuration is incorrect.
Equipment faults are as follows:
The line board is faulty or has bit errors.
The interconnected equipment is faulty.
The network cable is faulty.
The external electromagnetic interference is severe.
Issue 02 (2008-6-20)
1.
Clear the human factors such as a loopback and data configuration error.
2.
Locate the fault cause according to the equipment alarm.
3.
Locate the fault cause according to the RMON performance event and alarm.

4-31


Figure 4-9 Flow of handling Ethernet service faults
Start
1
Incorrect operation?
Yes
Roll back this operation.
No
2
Equipment
or line alarm?
Yes
Handle the alarm.
No
3
Ethernet interface
alarm?
Yes
Handle the alarm.
No
4
Ethernet protocol
alarm?
Yes
Handle the alarm.
No
5
Abnormal RMON
performance?
Troubleshoot according to
the flow of handling the
RMON performance event.
Yes
No
Fault of the
opposite equipment?
Yes
Troubleshoot faults of the

opposite equipment.
No
Troubleshoot equipment
faults by performing
loopbacks section by
section or replacing boards.
Proceed
with the
next step.
No
Are faults
cleared?
Yes
End
4-32

Issue 02 (2008-6-20)


Note
Description
Whether a loopback is set for the Ethernet board
Whether a loopback is set for the transmission line
Whether the settings of parameters of an Ethernet port such as port enabled,

working mode, and flow control are the same as those of its interconnected
equipment
Whether the configuration of the encapsulation/mapping protocol or the

LCAS protocol is the same as that of the opposite equipment
Whether the VCTRUNK-bound timeslot is the same as that of the opposite

equipment
Whether the service configuration in correct, especially the VLAN tag

related port attributes and network attributes and the parameters of the
VLAN filtering table
Check the following equipment alarms:

l
POWER_ALM
FAN_FAIL
HARD_BAD
BD_STATUS
SYN_BAD
NESF_LOST
TEMP_ALARM
RADIO_RSL_HIGH
RADIO_RSL_LOW
RADIO_TSL_HIGH
RADIO_TSL_LOW
IF_INPWR_ABN
Check the following line alarms:
Issue 02 (2008-6-20)
MW_LIM
MW_LOF
R_LOS
R_LOF
MS_AIS
AU_AIS
AU_LOP
B1_EXC
B2_EXC

4-33

Note
Description
Check the following:
4-34
ETH_LOS
ALM_GFP_dCSF
Check the following:

l
ALM_GFP_dLFD
FCS_ERR
LCAS_PLCT
LCAS_TLCT
LCAS_PLCR
LCAS_TLCR
LCAS_FOPT
LCAS_FOPR
For RMON performance events, refer to OptiX RTN 600 Radio Transmission
System Feature Description.

Issue 02 (2008-6-20)

Figure 4-10 Flow of handling RMON abnormal performance events

Start
1
Analyze the RMON
performance.
Collisions or
fragements?
Yes
2
Check the working
mode of a port.
No
FCS errors?
Yes
3
Handle the fault.
No
PAUSE frame?
Yes
Handle the flow

control problem or
add bandwidths.
No
Excessive
broadcast
packets?
Yes
5
Handle the fault.
No
Test with a meter.
Pass the test?
Yes
Troubleshoot faults of
the opposite equipment.
No
6
MTU setting
errors?
Yes
Modify the MTU value.
No
Troubleshoot equipment
faults by performing
loopbacks section by
section or replacing boards.
Proceed
with the
next step.
No
Are faults
cleared?
Yes
End
Issue 02 (2008-6-20)
Note
Description
Refer to OptiX RTN 600 Radio Transmission System Feature Description.

4-35

Note
Description

l
Whether the port operating rate of this equipment is the same as that of its
Whether the duplex/half-duplex mode of ports on this equipment is the

same as that on its interconnected equipment
Do not set one port to auto-negotiation and the opposite port to full-duplex.
Check the Ethernet cable. If the Ethernet cable is not qualified, replace it
with a new one.
Access the Ethernet services by using another Ethernet port. If the new port
does not report the "FCS error " of RMON performance, you can infer that
the hardware of the previous port is faulty. Otherwise, you can infer that
the hardware of the Ethernet port at the opposite side is faulty.
Whether the flow control mode of this equipment is the same as that of its
Whether the Ethernet service volume is larger that the configured

VCTRUNK bandwidth
Identify the causes of generating excessive broadcast packets, such as

loopback over the Ethernet port or incorrect setting of the VB filtering table,
and handle the problem accordingly. If the fault lies in the opposite equipment,
you can reduce the number of broadcast packets by setting a broadcast packet
suppression threshold for the Ethernet port.
The Maximum Transmission Unit (MTU) of a network can be tested by a test

meter. The maximum frame length that is set for a port must be longer than
this maximum network MTU.

Learn the features, working mode, and configured protocols of interfaces on Ethernet equipment,
which is a must to troubleshoot Ethernet faults.
4.9 Troubleshooting the Orderwire

If orderwire calls cannot get through when services are normal, there is an orderwire fault.
Fault Causes
4-36
The phone set is incorrectly set.
The phone line is wrongly connected.
The orderwire is incorrectly configured.
The SCC board is faulty.

Issue 02 (2008-6-20)


l
Check if the phone set is correctly set, if the phone line is correctly connected, and if the
orderwire is correctly configured.
Replace the possibly faulty board to check it out.

Figure 4-11 Flow of handling orderwire faults
Start
1
Check the phone setting
Is the phone
correctly set?
No
Modify the phone setting
Yes
Is the phone line
correctly connected?
No
Re-connect the phone line
Yes
2
Check the orderwire
configuration
Is the configuration
correct?
No
Modify the configuration
Yes
3
Replace the possibly faulty
board
Go to the next
step
No

Yes
End
Issue 02 (2008-6-20)

4-37


Note
Description

l
Check if the ring current switch "RING" on the phone set is set to "ON".
Check if the dialing mode switch is set to "T", that is, the dual tone multifrequency mode.
An orderwire phone set should be on-hook when it is not in communication,

and the upper-right red indicator in the front view of the orderwire phone
set should be off.
If the red indicator is on, it indicates that the phone set is in the off-hook
state. Press the "TALK" button in the front of phone set to hook it up. In
some occasions the "TALK" button is pressed by the maintenance
personnel due to carelessness. This makes the phone set stay in the offhook state all the time and the orderwire call from other NEs cannot get
through.

l
Check if all orderwire phone numbers in a subnet are of the same length.
Check if all orderwire phone numbers in a subnet are unique.
Check if the overhead bytes of all NEs in a subnet are the same.
Check if the orderwire port is correctly set.
Replace the SCC board and the line board that extracts the orderwire byte to
locate the faulty board.

It is necessary to periodically check the orderwire phone set.
4-38

Issue 02 (2008-6-20)

5 Common Maintenance Operation Guide
Common Maintenance Operation Guide
About This Chapter

This topic describes the operations of loopback, part replacement, and fiber connector and
adapter cleaning that are commonly used in maintenance.
5.1 Loopback
Loopback is process in which a signal is sent to the device under test which then returns the
signal to the originator.
5.2 Resetting
Resetting is an important method for handling software faults. The OptiX RTN 600 supports
cold resetting, warm resetting, and SCC resetting.
5.3 PRBS Test
The PRBS test is an important method for network self-check and network maintenance. In the
absence of a dedicated test tool, you can perform a PRBS test by using the embedded test system
on the PDH interface board.
5.4 Using the Ethernet Test Frames
By using the Ethernet test frames in the OptiX RTN 600, you can check the connectivity of the
VCTRUNK.
5.5 Setting the State of the ODU Transmitter
In the OptiX RTN 600, the state of the ODU transmitter can be mute or unmute. When the
transmitter of the ODU is unmute, the ODU transmits and receives microwave signals. When
the transmitter is mute, the ODU only receives signals.
5.6 Setting the State of the Laser
The laser on the port of the optical interface board transmits optical signals only when the laser
is open. You can open or close the laser through the NM.
5.7 Setting the Automatic Release Function
An NE can automatically release the loopback operation or enable the laser after a default period
of five minutes. You can custom the related settings through the NM.
5.8 Part Replacement
Part replacement is a method frequently used to locate faults. The replacement operation varies
with the part types.
Issue 02 (2008-6-20)

5-1

5.9 Cleaning Fiber Connectors and Adapters

The optical connecting components are easily contaminated in the maintenance. The minute dust
particles that can be seen only in the microscope can also affect the quality of optical signals. In
this case, it downgrades the system performance. Hence, clean the fiber connectors or adapters
that are terminated in a timely manner.
5-2

Issue 02 (2008-6-20)

5.1 Loopback
Loopback is process in which a signal is sent to the device under test which then returns the
signal to the originator.
Loopback is a very important test method. Based on the implementing methods, loopbacks can
be classified into:
l
Hardware loopback
Hardware loopback is a loopback implemented by changing the physical connections.
Software loopback
Hardware loopback is a loopback implemented through software design.
In the OptiX RTN 600, the SDH optical interface board, SDH electrical interface board, PDH
interface board, IF board, Ethernet service processing board, and ODU support loopback.
5.1.1 Setting Loopback for the SDH Optical Interface Board

The optical interface board (SL1/SD1/SL4) of the OptiX RTN 600 supports optical interface
outloops and VC-4 path outloops. The SL4 also supports VC-4 path inloops.
Prerequisite
l
The Web LCT has a normal communication with the NE.
Context
Optical interface inloop is a process where the SDH signal is looped back at the overhead
processing unit towards the backplane.
Figure 5-1 Optical interface inloop
Backplane
SDH optical
interface board
SDH
Optical interface outloop is a process where the SDH signal is looped back at the overhead
processing unit towards the remote equipment.
Issue 02 (2008-6-20)

5-3

Figure 5-2 Optical interface outloop

SDH optical
interface board
Backplane
SDH
VC-4 path outloop is a process where the VC-4 signal is looped back at the logic processing unit
towards the remote equipment.
Figure 5-3 VC-4 path outloop
SDH optical
interface board
Backplane
VC-4
VC-4 path inloop is a process where the VC-4 signal is looped back at the logic processing unit
towards the backplane.
Figure 5-4 VC-4 path inloop
Backplane
SDH optical
board
VC-4
Precaution
CAUTION
5-4
Loopback may interrupt the services on the port or the path for which the loopback is
performed.
A software loopback may be automatically released within a period (five minutes by default).
For details, refer to 5.7 Setting the Automatic Release Function.

Issue 02 (2008-6-20)

Procedure
Step 1 Select SDH optical interface board in the object tree.
Step 2 In the function tree, choose Configuration > SDH Interface.
Step 3 Select By Function, and select the loopback mode in the drop-down list.
To Perform ...
Select ...
Optical interface loopback
Optical (Electrical) Interface Loopback
VC-4 path loopback
VC4 Loopback
Step 4 Set the loopback status of the port as required.

Step 5 Click Apply.
The system displays a prompt dialog box for confirmation.
Step 6 Click OK.
----End
5.1.2 Setting Loopback for the SDH Electrical Interface Board

The electrical interface board of the OptiX RTN 600 supports the inloop/outloop of the electrical
interface and the outloop of the VC-4 path.
Prerequisite
l
The NE user has the "maintenance level" authority or higher.
Context
For the inloop of the electrical interface, an SDH signal is looped back at the coding/decoding
unit of the board to the backplane.
Figure 5-5 Electrical interface inloop
Backplane
SDH electrical
interface board
SDH
For the outloop of the electrical interface, an SDH signal is looped back at the coding/decoding
unit of the board to the remote equipment.
Issue 02 (2008-6-20)

5-5

Figure 5-6 Electrical interface outloop

SDH electrical
interface board
Backplane
SDH
For the outloop of the VC-4 path, a VC-4 signal is looped back at the logic processing unit of
the board to the remote equipment.
SDH electrical
interface board
Backplane
VC-4
Precaution
CAUTION
l
Loopback can interrupt the services on the port or the path for which the loopback is
performed.
Procedure
Step 1 Select an SDH electrical interface board from the NE Explorer.
Step 2 Choose Configuration > SDH Interface from the Function Tree.
Step 3 Select By Function, and select a loopback mode from the drop-down list.
To Perform ...
Select ...
Electrical interface loopback
VC-4 path loopback
VC4 Loopback
Step 4 Set the loopback status of the port or path as required.

5-6

Issue 02 (2008-6-20)

Step 5 Click Apply.

A prompt dialog box for confirmation is displayed.
Step 6 click OK.
----End
5.1.3 Setting Loopback of the PDH Interface BoardSetting the

Tributary Loopback
The PDH interface board supports the tributary inloop/outloop.
Prerequisite
l
The NE user has the "maintenance level" authority or higher.
Context
For the tributary outloop, a PDH signal is looped back at the coding/decoding unit of the board
to the remote equipment.
Figure 5-8 Tributary outloop
Backplane PDH interface board

PDH
Context
For the tributary inloop, a PDH signal is looped back at the coding/decoding unit of the board
to the backplane.
Figure 5-9 Tributary inloop
Backplane
PDH interface board

PDH
For the tributary outloop, a PDH signal is looped back at the coding/decoding unit of the board
to the remote equipment.
Issue 02 (2008-6-20)

5-7

Figure 5-10 Tributary outloop
Backplane PDH interface board

PDH
Precaution
CAUTION
Loopback can interrupt the services on the port or the path for which the loopback is performed.
Procedure
Step 1 Select a PDH interface board from the Object Tree.
Step 2 Choose Configuration > Interface from the Function Tree.
Step 3 Select By Function, and select Tributary Loopback in the drop-down list.
Step 4 Set the loopback status of the path as required.
Step 5 Click Apply.
Step 6 Click OK.
----End
5.1.4 Setting Loopback on the IF Board

Loopbacks on the IF board are classified into IF port loopbacks, port loopbacks, and VC-4 path
loopbacks. The IF1A/IF1B supports IF port inloops/outloops and VC-4 path inloops. The IF0A/
IF0B supports IF port inloops/outloops and port inloops/outloops. The IFX supports port inloops/
outloops and VC-4 path inloops.
Prerequisite
l
Context
IF port inloop is a process where the IF signal is looped back at the modem unit of the board
towards the backplane.
5-8

Issue 02 (2008-6-20)

Figure 5-11 IF port inloop
IF board
Backplane
IF signal
IF port outloop is a process where the IF signal is looped back at the modem unit of the board
IF port outloop is a process where the IF signal is looped back at the modem unit of the board
Figure 5-12 IF port outloop
Backplane
IF board
IF signal
Port inloop is a process where the microwave signal is loopbacked at the MUX/DEMUX unit
of the board towards the backplane.
Figure 5-13 Port inloop
Backplane
IF board
Microwave
baseband signal
Port outloop is a process where the microwave signal is loopbacked at the MUX/DEMUX unit
of the board towards the remote equipment.
Issue 02 (2008-6-20)

5-9

Figure 5-14 Port outloop

Backplane
IF board
Microwave
baseband
signal
VC-4 path inloop is a process where the VC-4 signal is looped back at the logic processing unit
of the board towards the backplane.
Backplane
IF board
VC-4 signal
Precaution
CAUTION
l
Loopback may interrupt the services on the port or in the path where the loopback operation
is conducted.
Procedure
Step 1 Select an IF board from the Object Tree in the NE Explorer.
Step 2 Choose the menus from the Function Tree.
To Perform ...
Choose ...
IF port loopback
Configuration > IF Interface
Port loopback
Configuration > Digital Interface
VC-4 path loopback
Configuration > Digital Interface
Step 3 Select By Function, and then select the loopback mode in the drop-down list.
5-10

Issue 02 (2008-6-20)

To Perform ...
Choose ...
IF port loopback
IF Port Loopback
Port loopback
VC-4 path loopback
VC4 Loopback

Step 5 Click Apply.
Step 6 Click OK.
----End
5.1.5 Setting Loopback of the Ethernet Service Processing Board

The Ethernet service processing board of the OptiX RTN 600 supports Ethernet port inloops (at
the MAC Layer and PHY layer) and VC-3 path inloops and outloops.
Prerequisite
l
Context
A MAC layer inloop is an inloop where the service processing module loops back the Ethernet
physical signals towards the backplane direction through the MAC layer. A PHY layer internal
inloop is an inloop where the interface module loops back the Ethernet frame signals towards
the backplane direction through the PHY layer.
Figure 5-16 inloop over an Ethernet port
Backplane
Ethernet service
processing board
MAC
PHY
VC-3 path inloop is an inloop where the logic processing unit of a board loops back the signals
in a specific VC-3 path towards the backplane direction.
Issue 02 (2008-6-20)

5-11


Ethernet service
processing board
Backplane
VC-3 signal
VC-3 path inloop is an inloop where the logic processing unit of a board loops back the signals
in a specific VC-3 path towards the remote equipment.
Backplane
Ethernet service
processing board
VC-3 signal
Precautions
CAUTION
l
A loopback operation may interrupt the services on the port or in the path where the loopback
is conducted.
A loopback in a VC-3 path may be automatically released within a period (five minutes by
default). For details, refer to 5.7 Setting the Automatic Release Function.
Procedure
Step 1 Select an Ethernet processing board from the Object Tree in the NE Explorer.
Step 2 Choose the menus from the Function Tree.
To Perform...
Choose...
Loopback over PHY Layer, Configuration > Ethernet Interface Management >
Ethernet Interface.
Loopback over MAC Layer, Configuration > Ethernet Interface Management >
Ethernet Interface.
Loopback in the VC-3 path
Configuration > SDH Interface.
Step 3 Select the loopback type.

5-12

Issue 02 (2008-6-20)

To Perform...
Choose...
Loopback over PHY Layer,
PHY Loopback
Loopback over MAC Layer,
MAC Loopback
Loopback in the VC-3 path
VC3 Loopback
Step 4 Set the loopback status of the port or path as required.

Step 5 Click Apply.
Step 6 Click OK.
----End
5.1.6 Setting Loopback of the ODU

In the OptiX RTN 600, the ODU supports RF port inloops.
Prerequisite
l
Context
An RF inloop is an inloop where the Diplexer of the ODU loops back the RF signals towards
the IF board direction.
Figure 5-19 RF inloopback
IF board
ODU
RF signal
Issue 02 (2008-6-20)

5-13

Precautions
CAUTION
Because the loopback over an IF port may cause serious accidents, familiarize yourself with the
following precautions when performing loopback operations:
l
During the loopback, the services on the related IF port are interrupted.
During the loopback, the IF board can handle only the services in the first four VC-12s (IF1A/
IF1B/IFX) or the services on the first five E1 ports.
During the loopback, the NE may interfere with the nearby radio communication equipment
of which the receive or transmit frequency is lower than the lowest transmit frequency of the
ODU.
During the loopback, do not modify the IF port- or ODU-related parameters. For the system
that is provided with 1+1 protection, do not modify the IF port- or ODU-related parameters
for the working and protection channels.
Some types of ODUs do not support loopback over the RF port.
Procedure
Step 1 Select an ODU from the NE Explorer.
Step 2 Choose Configuration > ODU Interface from the Function Tree.
Step 3 Select By Function, and select RF Loopback from the drop-down list.
Step 5 Click Apply.
Step 6 Click OK.
----End
5.2 Resetting
Resetting is an important method for handling software faults. The OptiX RTN 600 supports
cold resetting, warm resetting, and SCC resetting.
5.2.1 Cold Resetting

Cold resetting is a process where the board software is reset and the board is re-initiated. Except
that the board software of the EMS6 is independently located, the software modules of all other
boards are located in the SCC. During the board initialization, the FPGA, if any, is re-loaded.
Prerequisite
l
5-14

Issue 02 (2008-6-20)

l
Precautions
CAUTION
Being similar to the procedure of removing and inserting a board, cold resetting causes service
interruption.
Procedure
Step 1 In the slot layout of the T2000, right-click the board to be cold reset.
Step 2 Choose Cold Reset in the popup menu.
The system displays the Operation success dialog box.
Step 3 Click Close.
----End
5.2.2 Warm Resetting

Warm resetting is a process where the board software is reset but the board is not re-initiated.
Except that the board software of the EMS6 is independently located, the software modules of
all other boards are located in the SCC.
Prerequisite
l
Precautions
During the warm resetting, the running services are not affected.
Procedure
Step 1 In the slot layout of the T2000, right-click the board to be reset.
Step 2 Choose Warm Resetting in the popup menu.
The system displays the Operation succeeded dialog box.
Step 3 Click Close.
----End
5.2.3 SCC Resetting

SCC resetting is a process in which all the software modules on the SCC are reset, the SCC is
re-initiated.
Issue 02 (2008-6-20)

5-15

Prerequisite
l
Precautions
During the resetting, protection switching and NMS operations are unavailable although the
running services are not affected.
Procedure
Step 1 In the slot layout of the T2000, right-click the SCC to be reset.
Step 2 Choose SCC Reset in the popup menu.
The system displays the following prompt dialog box: Resetting the SCC board may result
in lost communication. Are you sure to continue?
Step 3 Click OK.
The system displays the Operation succeeded dialog box.
Step 4 Click Close.
----End
5.3 PRBS Test

The PRBS test is an important method for network self-check and network maintenance. In the
absence of a dedicated test tool, you can perform a PRBS test by using the embedded test system
on the PDH interface board.
Prerequisite
l
Context
The PRBS test in the tributary direction can be used to check the connection between the PDH
interface board and the DDF, as shown in Figure 5-20.
Figure 5-20 PRBS test in the tributary direction
DDF frame
PDH interface board

PRBS
Transmitter
1
PRBS
Recevicer
1
5-16
Inloop at the DDF frame

Issue 02 (2008-6-20)

The PRBS test in the cross-connect direction can be used to check the connection between the
PDH interface board and the remote NE, as shown in Figure 5-21.
Figure 5-21 PRBS test in the cross-connect direction
a) IF board working as line board
PDH interface
board
Cross-connect
board
IF board
IF board
OUT
PRBS
Transmitter
2
PRBS
IN
Receiver
Local NE
1
VC4 inloop or
port inloop
IF port inloop
Remote NE
3
IF port outloop
b) SDH optical/electrical board working as line board

PDH interface
board
Cross-connect
board
SDH optical/
electrical board
SDH optical/
electrical board
OUT
PRBS
Transmitter
2
1
PRBS
3
IN
Receiver
Local NE
1
VC4 inloop
Port inloop
Remote NE
3
Port outloop
Precautions
CAUTION
l
During the PRBS test, the services in the tested path are interrupted.
The PRBS test can only be conducted in one path and in one direction.
Procedure
Step 1 Set the loopback. For details, refer to Figure 5-20 and Figure 5-21.
Step 2 Select an PDH board from the Object Tree in the NE Explorer.
Issue 02 (2008-6-20)

5-17

Step 3 Choose Configuration > PRBS Test from the Function Tree.
The PRBS Test tab page is displayed.
Step 4 Select the port to be tested.
Step 5 Specify Direction, Duration, and Measured in Time.
NOTE
The PRBS test supports three time units: one second, 10 minutes, and one hour.
A maximum of 255 test cycles is permissible for the PRBS test.
Step 6 Optional: Select Accumulating Mode.

Step 7 Click Start the test.
The system displays the following prompt dialog box: The operation may interrupt the
service. Are you sure to continue?
Step 8 Click OK.
Step 9 When Progress in the PRBS Test tab page is displayed as 100%, click Query to check the test
result.
NOTE
The result of a PRBS test can be normal, error, or invalid.

l
Normal: Indicates that the path is working properly. The number of PRBSs should be zero, and the
curve should be green.
Error: Indicates that the path has errors. The number of total PRBSs should be greater than zero, and
the curve should be red.
Invalid: Indicates that no bit is received. The curve should be yellow.
----End
5.4 Using the Ethernet Test Frames

By using the Ethernet test frames in the OptiX RTN 600, you can check the connectivity of the
VCTRUNK.
Prerequisite
l
The service traffic is encapsulated or mapped by using the GFP method.
Context
For test purposes, the Ethernet board sends, at an interval of about one second, one specific GFP
management frame or one specific Ethernet frame to the peer Ethernet board, which then returns
with a response frame. Upon receiving the response frame, the Ethernet board at the local end
can judge the connectivity of the VCTRUNK in between.
5-18

Issue 02 (2008-6-20)

Figure 5-22 Ethernet test frames between Ethernet boards

Test frame
Local
Ethernet
board
Response frame
Remote
Ethernet
board
Precautions
CAUTION
Never use the test frames when the network traffic is heavy.
Procedure
Step 1 Select an Ethernet board from the NE Explorer.
Step 2 Choose Configuration > Ethernet Maintenance > Ethernet Test from the Function Tree.
The Ethernet Test tab page is displayed.
Step 3 Select the port to be tested, click Clear Counters and chooseClear All Counters from the dropdown list.
Step 4 Specify Send Mode and Frames to Send.
NOTE
Huawei recommends that you choose "Burst mode", and a maximum of 10 frames can be transmitted each
time.
Step 5 Click Apply.

Step 6 When Status changes to Finished Sending, click Query.
Step 7 Check Counter of Frames Sent and Counter of Received Response of Test Frame.
Test frames are used to check the network connectivity. If some of the test frames are lost but
no alarm is reported on the SDH side, you can infer that the network connectivity is in good
condition. If all the test frames are lost, you can infer that network disconnection arises.
----End
Related Information
If you choose the "Continue" mode, the local port transmits test frames continuously until the
test is disabled.
5.5 Setting the State of the ODU Transmitter

In the OptiX RTN 600, the state of the ODU transmitter can be mute or unmute. When the
transmitter of the ODU is unmute, the ODU transmits and receives microwave signals. When
the transmitter is mute, the ODU only receives signals.
Issue 02 (2008-6-20)

5-19

Prerequisite
l
Context
When the transmitter of the ODU is unmute, the actual transmit power of the ODU takes the
preset value if the ATPC is disabled. The actual transmit power of the ODU, however, is a little
bit different from the preset value if the ATPC is enabled.
Procedure
Step 1 Select an NE from the NE Explorer.
Step 2 Choose Configuration > Link Configuration from the Function Tree.
Step 3 Select the IF/ODU Configuration tab.
Step 4 Click the slot icon of the ODU, and specify TX Status.
Step 5 Click Apply.
----End
5.6 Setting the State of the Laser

The laser on the port of the optical interface board transmits optical signals only when the laser
is open. You can open or close the laser through the NM.
Prerequisite
l
Procedure
Step 1 Select an SDH optical interface board from the NE Explorer.
Step 2 Choose Configuration > SDH Interface from the Function Tree, and then select the SDH
Interface tab.
Step 3 Select By Function.
Step 4 Select Laser Switch from the drop-down list.
Step 5 Select a port, and set Laser Switch.
Step 6 Click Apply.
----End
5-20

Issue 02 (2008-6-20)

5.7 Setting the Automatic Release Function

An NE can automatically release the loopback operation or enable the laser after a default period
of five minutes. You can custom the related settings through the NM.
Prerequisite
l
Precautions
NOTE
The PDH interface board does not support the loopback and automatic release functions.
Procedure
Step 1 Select an NE from the Object Tree in the NE Explorer.
Step 2 Choose Configuration > Automatic Disabling of NE Function from the Function Tree.
Step 3 Specify Auto Disabling and Auto Disabling Time (min).
Step 4 Click Apply.
----End
5.8 Part Replacement

Part replacement is a method frequently used to locate faults. The replacement operation varies
with the part types.
Table 5-1 Part replacement description
Issue 02 (2008-6-20)
Part Name
Operation
SD1, SL1, SL4
5.8.3 Replacing the SDH Optical Interface Board
SLE and SDE
5.8.4 Replacing the SDH Electrical Interface Board
PO1, PH1, PD1, and PL3
5.8.5 Replacing the PDH Interface Board
EFT4 and EMS6
5.8.7 Replacing the IF Board
IF1A, IF1B, IFX, IF0A, and

IF0B
PXC
5.8.8 Replacing the PXC Board
SCC
5.8.9 Replacing the SCC Board
FAN
5.8.10 Replacing the Fan Board

5-21

Part Name
Operation
ODU
5.8.11 Replacing the ODU
5.8.1 Removing a Board

Procedure
Step 1 Insert one end of the ESD wrist strap into the ESD connector on the cabinet. Wear the ESD wrist
strap.
Step 2 If the board is connected with cables, remove the cables after marking them.
Step 3 Loosen screws on the panel of the board.
Figure 5-23 Removing a board (1)
Step 4 Hold the left and right ejector levers with hands. Push them outwards to disengage the board
from the backplane.
Step 5 Pull out the board gently along the guide rail in the slot. At this time, the board is in a parallel
manner.
5-22

Issue 02 (2008-6-20)

CAUTION
Slowly remove the board, to avoid that the components on the boards are collided.
Step 6 Put the board removed into the antistatic box or bag.
----End
5.8.2 Inserting a Board

Procedure
Step 1 Insert one end of the ESD wrist strap into the ESD connector on the cabinet. Wear the ESD wrist
strap.
Step 2 Hold the ejector levers with hands on the panel. Push them outwards and make the angle between
the ejector lever and the panel be 45 degrees or so.
Step 3 Push the board gently along the slot guide rail until the board cannot slide further.
Figure 5-26 Inserting a board (1)
Issue 02 (2008-6-20)

5-23

CAUTION
Slowly insert the board, to avoid that the components on the boards are collided.
Step 4 Press the two ejector levers inward with force.
Step 5 Tighten screws on the panel.

Step 6 If the board is connected to cables originally, connect the cables based on the label marked on
them.
----End
5.8.3 Replacing the SDH Optical Interface Board

When the SDH optical interface board is replaced, the service of the board without any protection
is interrupted.
Prerequisite
5-24
Know the impact of board replacement.
Know the specific position of the board to be replaced.
Know the service protection and protection channels of the board to be replaced.
Issue 02 (2008-6-20)

l
Make sure that the spare SDH optical interface board is at hand and that the version and
type of the spare board are consistent with those of the board to be replaced.
NOTE
You can identify the type of a board through the board feature code in the bar code on the ejector lever.

l
Antistatic wrist strap
Screwdriver
Web LCT or T2000
Procedure
Step 1 Query the current alarm of the board using the Web LCT or T2000, and record the result.
Step 2 When the service of the board to be replaced is the working service configured with the SNCP,
use the Web LCT or T2000 to perform the forced switching of the service.
Step 3 Refer to 5.8.1 Removing a Board, and remove the board.
Step 4 Make sure the version and SFP type of the spare board are consistent with those of the board to
be replaced.
Step 5 Refer to 5.8.2 Inserting a Board, and insert the spare board.
Step 6 When the board is working, observe the indicators.
The STAT indicator should light on as green.
Step 7 If the SNCP forced switching was performed for the service, use the Web LCT or T2000 to
cancel it.
Step 8 Query the current alarm of the board using the Web LCT or T2000.
There should be no newly added alarms.
----End
5.8.4 Replacing the SDH Electrical Interface Board

When the SDH electrical interface board is replaced, the service of the board without any
protection is interrupted.
Prerequisite
l
The spare SDH electrical interface board is at hand, and is of the same version as the board
to be replaced.

l
Issue 02 (2008-6-20)

5-25

l
Screwdriver
Web LCT or T2000

Procedure
Step 4 Make sure the version of the spare board is consistent with that of the board to be replaced.
cancel it.
----End
5.8.5 Replacing the PDH Interface Board

When the PDH interface board is replaced, the services of the board are interrupted.
Prerequisite
l
Make sure that the spare PDH interface board is at hand and that the version and type of it
are consistent with the board to be replaced.
NOTE
The E1 interface boards PO1 and PH1 both have two types: A and B. The A type is of 75-ohm interface
impedance, and the B type 120-ohm. Identify them by the bar code on the board ejector lever.

l
Screwdriver
Web LCT or T2000
Procedure
5-26

Issue 02 (2008-6-20)

Step 3 Make sure the version and type of the spare board are consistent with those of the board to be
replaced.
----End
5.8.6 Replacing the Ethernet Service Processing Board

When the Ethernet service processing board is replaced, the services on this board are
interrupted.
Prerequisite
l
The backup part for the Ethernet service processing board must be available on site. The
version of the backup part must be the same as those of the board to be replaced. For the
EMS6 board, the type of the backup part must also be the same as those of the board to be
replaced.
NOTE
You can identify the type of a board through the board feature code in the bar code on the ejector lever.

l
Screwdriver
Web LCT or T2000
Procedure
Step 3 Check whether the version and type of the backup part are the same as those of the board to be
replaced.
----End
Issue 02 (2008-6-20)

5-27


If the IF board is not configured with 1+1 protection and the services of the board are not
configured with any protection, the services on the board are interrupted during board
replacement. If the IF board is configured with XPIC, the XPIC-related services are also affected.
Prerequisite
l
Make clear the configuration of the board 1+1 protection.
Make sure that the spare IF board is at hand and that the version and type of it are consistent
with those of the board to be replaced.

l
Screwdriver
Web LCT or T2000
Procedure
Step 2 When the board to be replaced is the working board configured with the 1+1 protection, use the
Web LCT or T2000 to perform the forced switching of the board.
After the successful switching, perform the step 4.
Step 4 Turn off the ODU-PWR switch of the IF board to be replaced.
Step 6 Make sure the version and type of the spare IF board are consistent with those of the board to
be replaced.
Step 7 Make sure that the ODU-PWR switch on the spare IF board is in the off position.
Step 10 Turn on the ODU-PWR switch of the IF board.
cancel it.
Step 12 If the 1+1 protection forced switching of the board was performed, use the Web LCT or T2000
to cancel it.
5-28

Issue 02 (2008-6-20)

Step 14 After you replace the IF1A/IF1B board, you should re-load and re-activate the FPGA file by
referring to the upgrade guide if the new board reports a NO_BD_SOFT alarm.
----End
5.8.8 Replacing the PXC Board

If the PXC board is not configured with the 1+1 backup, all services of the system are interrupted
during this process.
Prerequisite
l
Make clear the configuration of the board 1+1 protection.
Make sure that the spare PXC board is at hand and that the version is consistent with that
of the board to be replaced.

l
Screwdriver
Web LCT or T2000
Precaution
When the PXC is configured with 1+1 protection and only one-channel power is accessed, it is
recommended to provide one-channel -48 V/-60 V power for the standby PXC board
temporarily. After the board is replaced, stop providing power for the standby board. This can
ensure that the equipment does not power off during the PXC replacement.
Procedure
Step 2 When the board to be replaced is the active board configured with the 1+1 protection, perform
the active and standby switching using the Web LCT or T2000.
1.
Select an NE from the NE Explorer, and choose Configuration > Board 1+1 Protection
from the Function Tree.
2.
Select a PXC protection group.
3.
Click Working/Protection Switching.
4.
Click OK to begin the protection switching.
Step 3 Turn off the SYS-PWR switch of the PXC board to be replaced.
Step 4 Turn off the switch of the power that provides power for the PXC board to be replaced.
Issue 02 (2008-6-20)

5-29

Step 5 Make sure that the version and type of the spare board are consistent with those of the board to
be replaced.
Step 6 Turn on the switch of the power that provides power for the PXC board.
Step 7 Turn on the SYS-PWR switch of the PXC board.
Step 8 If the switching is performed before the replacement, perform a switchover operation on the
Web LCT or T2000 to make the working board be the active board, not the standby board.
1.
Select an NE from the NE Explorer, and choose Configuration > Board 1+1 Protection
from the Function Tree.
2.
Select a PXC protection group.
3.
Click Working/Protection Switching.
4.
Click OK to begin the protection switching.
----End
5.8.9 Replacing the SCC Board

During this process, any NM operation and switching cannot be performed.
Prerequisite
l
Make sure that the spare SCC is at hand and that the version of it is consistent with that of
the board to be replaced.

l
Screwdriver
Web LCT or T2000
Procedure
Step 2 Press the RST button on the SCC front panel.
During the reset of the SCC board, the PROG indicator is on, off, flashing, and off sequentially.
Step 3 When the PROG indicator is operating, Refer to section 3.2.1 Removing a Board, remove the
board.
Step 4 Make sure the version and the jumper settings of the spare board are consistent with those of the
board to be replaced.
Step 5 Remove the board to be replaced and portable memory card of the spare board.
1.
5-30
Wear the ESD wrist strap.

Issue 02 (2008-6-20)

2.
Remove the screws on the portable memory card and pull the connector of the memory
card out from the socket of the dual edge connector on the SCC board.
Figure 5-29 Remove the portable memory card
Step 6 Install the portable memory card of the board to be replaced onto the spare board.
The STAT and PROG indicators should be lit green.
----End
5.8.10 Replacing the Fan Board

As the IDU can not perform the air cooling during the process, replace the fan board quickly.
Prerequisite
Make sure that the spare fan board is at hand and that the version of it is consistent with that of
the board to be replaced.

l
Screwdriver
Web LCT or T2000
Procedure
Issue 02 (2008-6-20)

5-31

Step 2 Loosen the captive screws on the panel of the fan tray assembly.
Step 3 Move cables away from the front panel of the fan tray assembly.
Step 4 Pull out the fan tray assembly.
Figure 5-30 Pulling out the fan tray assembly
NOTE
If the IDU is installed in a dust-proof environment, there is no air filter.
Step 5 Remove the fan board gently and horizontally along the guide rail.
Figure 5-31 Removing the fan board
WARNING
Before the fan stops, do not touch the blades.
Step 6 Make sure the version of the spare board is consistent with that of the board to be replaced.
Step 7 Insert the spare board steadily along the guide rail.
Step 8 Install the panel of the fan tray assembly to the original position.
Step 9 Tighten the captive screws on the panel.
Step 10 Observe the indicator on the panel.
5-32

Issue 02 (2008-6-20)

The FAN indicator should be lit green.

----End
5.8.11 Replacing the ODU

When the ODU is not configured with 1+1 protection, the service transmitted by the ODU is
interrupted during the process.
Prerequisite
l
The influence of replacing the ODU must be acknowledged.
The specific location of the ODU to be replaced must be specified.
Spare ODU must be available on site, and the spare part must be the same as those to be
replaced in version and type

l
Web LCT or T2000
Silicon
Waterproof adhesive tape
Torque spanner
Precautions
Before you replace an ODU installed on the coupler, power off the ODU to be replaced, but do
not power off or mute the other ODU. Otherwise, the services may be affected. The interface of
the coupler ejects little RF radiation, and thus meets the safety standards for microwave radiation.
Procedure
Step 1 Query the current alarm of the ODU using the Web LCT or T2000, and record the result.
Step 2 Turn off the ODU-PWR switch on the panel of the IF board.
Step 3 Disconnect the IF cable and grounding cable of the ODU.
Step 4 Loosen the four latches of the ODU and disconnect the ODU from the antenna or the hybrid
coupler.
Step 5 Make sure the type of the spare ODU is consistent with that of the ODU to be replaced.
Step 6 Install the ODU.
Issue 02 (2008-6-20)
1.
Remove the protective cap on the antenna interface of the ODU.
2.
Wearing gloves, dispense appropriate amount of lubricant on the sealing packing ring.

5-33

CAUTION
Do not dispense the lubricant on the front panel of the feeder. Otherwise, it may affect the
signal transmission.
3.
Align the antenna interface of the ODU with the feeder and then insert it to the feeder.
Make sure that the four hooks are engaged with the latches of the ODU.
CAUTION
When inserting, make sure that the arrow direction stenciled on the ODU is consistent with
the polarity direction of the antenna or the hybrid coupler.
4.
Lock the four latches in a diagonal order.
Step 7 Connect the grounding cable and IF cable to the ODU.

Step 8 Carry out the waterproof processing for the IF interface of the ODU.
Step 9 Turn on the ODU-PWR switch on the panel of the IF board.
Step 10 When the ODU is working, observe the indicators of the IF board: ODU and LINK.
The indicators ODU and LINK should both light on as green.
Step 11 Query the current alarm of the ODU using the Web LCT or T2000
----End
5.9 Cleaning Fiber Connectors and Adapters

The optical connecting components are easily contaminated in the maintenance. The minute dust
particles that can be seen only in the microscope can also affect the quality of optical signals. In
this case, it downgrades the system performance. Hence, clean the fiber connectors or adapters
that are terminated in a timely manner.
5.9.1 Cleaning Fiber Connectors Using Cartridge Cleaners

When there are special cartridge cleaners (such as the CLETOP cassette cleaner), use them for
cleaning the fiber connectors.
Prerequisite
l
Disconnect both ends of the fiber. Make sure there is no laser light present on the fiber
connector.
Inspect the fiber connector with a fiber microscope to make sure that the fiber connector
is contaminated.

Cartridge cleaner
5-34

Issue 02 (2008-6-20)

Procedure
Step 1 Press down and hold the lever, and the shutter slides back and expose a new cleaning area.
Figure 5-32 CLETOP cassette cleaner
Step 2 Position the fiber tip slightly against the cleaning area and drag the fiber tip slightly in the
downward direction.
Figure 5-33 Dragging the fiber tip slightly on one cleaning area
Step 3 Do it again on the other cleaning area in the same direction as the step 2.
Issue 02 (2008-6-20)

5-35

Figure 5-34 Dragging the fiber tip slightly on the other cleaning area
Step 4 Release the lever to close the cleaning area.

----End
5.9.2 Cleaning Fiber Connectors Using Lens Tissue

When there is no cartridge cleaners, use the lens tissue for cleaning fiber connectors.
Prerequisite
l
Disconnect both ends of the fiber to be inspected. Make sure there is no laser light present
on the fiber connector.
Inspect the fiber connector with a fiber microscope to make sure that the fiber connector
is contaminated.

l
Clean solvent
Non-woven lens tissue
Special compressed gas

NOTE
5-36
Using the isoamylol as the clean solvent is preferred, and the propyl can also be used. Do not use alcohol
or formalin.
The fiber cleaning tissue or lint-free wipes can replace the non-woven lens tissue.
The special cleaning roll can replace the special compressed gas.

Issue 02 (2008-6-20)

Procedure
Step 1 Place a small amount of cleaning solvent on the lens tissue.
Step 2 Drag the fiber tip slightly on the lens tissue.
Figure 5-35 Cleaning the fiber with the lens tissue
Step 3 Repeat step 2 several times on the areas of the lens tissue that have not been used.
Step 4 Using compressed gas, blow off the fiber tip.
When using compressed gas:
l
First spray it into the air as the initial spray of condensation can contain some sediment.
Keep the injector nozzle as close as possible to the connector surface without touching it.
----End
5.9.3 Cleaning Fiber Adapters Using Optical Cleaning Sticks

Clean fiber adapters with optical cleaning sticks. This part describes the method of cleaning fiber
adapters on the optical interface board. The method of cleaning fiber adapters on the optical
attenuators and flanges is the same.
Prerequisite
Issue 02 (2008-6-20)
Before you clean the fiber adapter, be sure to remove the optical fiber and shut down the
laser. For details about how to shut down a laser, refer to 5.6 Setting the State of the
Laser.
Inspect the fiber adapter with a fiber microscope to make sure that the fiber adapter is
contaminated.

5-37


l
Optical cleaning sticks
Clean solvent
Special compressed gas

NOTE
For the SC and FC optical interface, use the cleaning stick with a diameter of 2.5 mm, for the LC optical
interface, use the cleaning stick with a diameter of 1.25 mm.
The medical cotton or long fiber cotton can replace the optical cleaning stick.
Using the isoamylol as the clean solvent is preferred, and the propyl can also be used. Do not use alcohol
or formalin.
The special cleaning roll can replace the special compressed gas.
Procedure
Step 1 Place a small amount of cleaning solvent on the optical cleaning stick.
Step 2 Hold the stick straight out from the adapter and turn the stick clockwise four to five times.
Ensure that there is direct contact between the stick tip and fiber tip so that the solvent can clean
the adapter tip.
Step 3 Using compressed gas, blow off the fiber tip.
When using compressed gas:
l
First spray it into the air as the initial spray of condensation can contain some sediment.
Keep the injector nozzle as close as possible to the connector surface without touching it.
----End
5-38

Issue 02 (2008-6-20)

A Alarm Reference
Alarm Reference
A.1 Alarm List

The following table lists all the possible alarms generated by the OptiX RTN 600 in alphabetical
order.
Table A-1 Alarm list
Issue 02 (2008-6-20)
Alarm Name
Description
Alarm
Severit
y
Source Board
A_LOC
Add to bus - loss of clock
Major
PO1, PH1, PD1, and

PL3
APS_MANUAL_S
TOP
MSP protocol is stopped

manually
Major
SCC
ALM_GFP_dCSF
GFP loss of client signal
Critical
EFT4 and EMS6
ALM_GFP_dLFD
GFP loss of frame delineation
Major
EFT4 and EMS6
ALM_RTC_FAIL
RTC time fail alarm
Major
SCC
APS_FAIL
APS protection switching failed
Major
SCC
APS_INDI
APS state indication alarm
Major
SCC
AU_AIS
AU alarm indication
Major
SD1, SL1, SDE,

SLE, IF1A, IF1B,
IFX, and SL4
AU_LOP
AU loss of pointer
Major
SD1, SL1, SDE,

SLE, IF1A, IF1B,
IFX, and SL4

A-1

A Alarm Reference
A-2
Alarm Name
Description
Alarm
Severit
y
Source Board
B1_EXC
Regenerator section (B1)

excessive errors
Minor
SD1, SL1, SDE,

SLE, IF1A, IF1B,
IF0A, IF0B, IFX, and
SL4
B1_SD
Regenerator section (B1) signal

degraded
Minor
SD1, SL1, SDE,

SLE, IF1A, IF1B,
SL4
B2_EXC
Multiplex section (B2) excessive

errors
Major
SD1, SL1, SDE,

SLE, IF1A, IF1B,
IFX, and SL4
B2_SD
Multiplex section (B2) signal

degraded
Minor
SD1, SL1, SDE,

SLE, IF1A, IF1B,
IFX, and SL4
B3_EXC
Higher order path (B3) excessive

errors
Major
SD1, SL1, SDE,

SLE, IF1A, IF1B,
IFX, SL4, and PL3
B3_EXC_VC3
B3_EXC_VC3
Major
EFT4 and EMS6
B3_SD
Higher order path (B3) signal

degraded
Minor
SD1, SL1, SDE,

SLE, IF1A, IF1B,
IFX, SL4, and PL3
B3_SD_VC3
B3_SD_VC3
Minor
EFT4 and EMS6
BD_NOT_INSTAL
LED
Slot not installed with the

corresponding logical board
Minor
SCC
BD_STATUS
Board not in position
Major
SD1, SL1, SDE,

SLE, IF1A, IF1B,
PO1, PH1, EFT4,
PXC, ODU, FAN,
EOW, IF0A, IF0B,
IFX, PD1, and SL4
BIP_EXC
BIP excessive errors
Minor
PO1, PH1, EFT4,

EMS6, IF0A, IF0B,
IFX, and PD1
BIP_SD
BIP signal degraded
Minor
PO1, PH1, EFT4,

EMS6, IF0A, IF0B,
and PD1
BOOTROM_BAD
BOOTROM data check fails
Major
SCC
CONFIG_NOSUP
PORT
Configuration not supported
Major
ODU

Issue 02 (2008-6-20)

Issue 02 (2008-6-20)
A Alarm Reference
Alarm Name
Description
Alarm
Severit
y
Source Board
DBMS_ERROR
Database error
Major
SCC
DBMS_PROTECT
_MODE
Database in protection mode
Critical
SCC
DN_E1_AIS
2M down signal alarm indication
Minor
PO1, PH1, and PD1
E1_LOC
Loss of E1 clock
Major
PO1, PH1, and PD1
E1_LOS
2M line loss of signal
Minor
PO1, PH1, and PD1
ESN_FAILED
ESN failed
Major
SCC
ESN_INVALID
ESN invalid
Major
SCC
ETH_LOS
Ethernet receive loss of input

signal
Critical
EFT4 and EMS6
F1PORT_FAILED
Synchronous data port failure
Minor
SCC
EXT_SYNC_LOS
Loss of external synchronous

source
Critical
SCC
FAN_FAIL
Fan failed
Major
FAN
FCS_ERR
FCS check error
Critical
EFT4 and EMS6
HARD_BAD
Hardware error
Critical
SD1, SL1, SDE,

SLE, IF1A, IF1B,
PO1, PH1, EFT4,
PXC, SCC, ODU,
EMS6, IF0A, IF0B,
IFX, PD1, and SL4
HP_CROSSTR
Higher order path performance

over threshold
Minor
SD1, SL1, SDE,

SLE, IF1A, IF1B,
IFX, SL4
HP_LOM
Higher order path loss of

multiframe
Major
SD1, SL1, SDE,

SLE, IF1A, IF1B,
IFX, and SL4
HP_RDI
Higher order path remote defect

indication
Minor
SD1, SL1, SDE,

SLE, IF1A, IF1B,
IFX, and SL4
HP_REI
Higher order path remote error

indication
Warning
SD1, SL1, SDE,

SLE, IF1A, IF1B,
IFX, and SL4
HP_SLM
Higher order path signal label

mismatch
Minor
SD1, SL1, SDE,

SLE, IF1A, IF1B,
IFX, and SL4

A-3

A Alarm Reference
A-4
Alarm Name
Description
Alarm
Severit
y
Source Board
HP_TIM
Higher order path trace identifier

mismatch
Minor
SD1, SL1, SDE,

SLE, IF1A, IF1B,
IFX, and SL4
HP_UNEQ
Higher order path unequipped
Minor
SD1, SL1, SDE,

SLE, IF1A, IF1B,
IFX, and SL4
HPAD_CROSSTR
Higher order path adaptation

performance over threshold
Minor
PO1, PH1, and PD1
HSB_INDI
Microwave equipment HSB

switching indication
Major
SCC
HSM_INDI
Microwave channels HSM

switching indication
Major
SCC
IF_CABLE_OPEN
IF cable disconnected
Major
IF1A, IF1B, IF0A,

IF0B, and IFX
IF_INPWR_ABN
Abnormal input IF power of the

ODU
Major
ODU
IN_PWR_HIGH
Input power too high
Critical
SD1, SL1
IF_MODE_UNSU
PPORTED
Preset IF working mode not

supported
Major
IF1A, IF1B
IN_PWR_LOW
Input power too low
Critical
SD1, SL1, and SL4
J0_MM
Trace identifier mismatch
Minor
SD1, SL1, SDE,

SLE, IF1A, IF1B,
and SL4
K1_K2_M
K1K2 mismatch
Minor
SCC
K2_M
K2 mismatch
Minor
SCC
LASER_CLOSED
Laser closed alarm
Major
SD1, SL1, and SL4
LASER_MOD_ER
R_EX
Pluggable optical module on the

board mismatches the optical
interface
Major
SD1, SL1, and SL4
LCAS_FOPR
Failure of protocol receive
Major
EFT4 and EMS6
LCAS_FOPT
Failure of protocol transmit
Major
EFT4 and EMS6
LCAS_PLCR
Partial loss of capacity receive
Minor
EFT4 and EMS6
LCAS_PLCT
Partial loss of capacity transmit
Minor
EFT4 and EMS6
LCAS_TLCR
Total loss of capacity receive
Major
EFT4 and EMS6
LCAS_TLCT
Total loss of capacity receive
Major
EFT4 and EMS6

Issue 02 (2008-6-20)

Issue 02 (2008-6-20)
A Alarm Reference
Alarm Name
Description
Alarm
Severit
y
Source Board
LCS_LIMITED
Capacity of the configured

services crosses the limit defined
in the license file
Major
SCC
LICENSE_LOST
License file lost
Major
SCC
LICENSE_ERR
License file verification fails
Major
SCC
LCS_LIMITED
Capacity of the configured

services crosses the limit defined
in the license file
Major
SCC
LCS_LOST
License file lost
Major
SCC
LINK_ERR
Data link failure
Critical
EMS6
LPS_UNI_BI_M
Alarm of mismatch in
unidirectional operation and
bidirectional operation in linear
MSP
Minor
SCC
LOOP_ALM
Path loopback
Minor
SD1, SL1, SDE,

SLE, IF1A, IF1B,
PO1, PH1,
EFT4,EMS6, ODU,
IF0A, IF0B, IFX,
PD1, and SL4
LP_CROSSTR
Lower order path performance

parameter over threshold
Minor
PO1, PH1, and PD1
LP_R_FIFO
FIFO overflow on the receiving

side of the lower order path
Minor
PO1, PH1, PD1, and

PL3
LP_RDI
Lower order path remote defect

indication
Minor
PO1, PH1, IF0A,

IF0B, PD1, and PL3
LP_RDI_VC12
VC-12 lower order path remote

defect indication
Minor
EFT4 and EMS6
LP_RDI_VC3

defect indication
Minor
EFT4 and EMS6
LP_REI
Lower order path remote error

indication
Minor
PO1, PH1, IF0A,

IF0B, PD1, and PL3
LP_REI_VC12

receiving failure indication
Minor
EFT4 and EMS6
LP_REI_VC3

receiving failure indication
Minor
EFT4 and EMS6

A-5

A Alarm Reference
A-6
Alarm Name
Description
Alarm
Severit
y
Source Board
LP_RFI
Lower order path remote failure

indication
Minor
PO1, PH1, and PD1
LP_SIZE_ERR
TU structure error
Minor
PO1, PH1, and PD1
LP_SLM
Lower order path signal label

mismatch
Minor
PO1, PH1, PD1, and

PL3
LP_SLM_VC12
VC-12 lower order path signal

flag mismatch
Minor
EFT4 and EMS6
LP_SLM_VC3
VC-3 lower order path signal flag

mismatch
Minor
EFT4 and EMS6
LP_T_FIFO
FIFO overflow on the

transmission side of the lower
order path
Minor
PO1, PH1, PD1, and

PL3
LP_TIM
Lower order path trace identifier

mismatch
Minor
PO1, PH1, PD1, and

PL3
LP_TIM_VC12
VC-12 lower order path trace

identifier mismatch
Minor
EFT4 and EMS6
LP_TIM_VC3
VC-3 lower order path trace

identifier mismatch
Minor
EFT4 and EMS6
LP_UNEQ
Lower order path unequipped
Minor
PO1, PH1, IF0A,

IF0B, PD1, and PL3
LP_UNEQ_VC12

unequipped
Minor
EFT4 and EMS6
LP_UNEQ_VC3

unequipped
Minor
EFT4 and EMS6
LSR_NO_FITED
Laser not installed
Critical
SD1, SL1, and SL4
LSR_WILL_DIE
Laser to expire
Critical
SL4
LTI
Loss of timing input
Major
SCC
MOD_TYPE_MIS
MATCH
Peer modules mismatch
Critical
EMS6
MS_AIS
Multiplex section alarm

indication
Major
SD1, SL1, SDE,

SLE, IF1A, IF1B,
IFX, and SL4
MS_CROSSTR
Multiplex section performance

over threshold
Minor
SD1, SL1, SDE,

SLE, IF1A, IF1B,
and SL4

Issue 02 (2008-6-20)

Issue 02 (2008-6-20)
A Alarm Reference
Alarm Name
Description
Alarm
Severit
y
Source Board
MS_RDI
Multiplex section remote defect

indication
Minor
SD1, SL1, SDE,

SLE, IF1A, IF1B,
IFX, SL4
MS_REI
Multiplex section remote error

indication
Warning
SD1, SL1, SDE,

SLE, IF1A, IF1B,
IFX, and SL4
MSAD_CROSSTR
Multiplex section adaptation

performance over threshold
Minor
SD1, SL1, SDE,

SLE, IF1A, IF1B,
IFX, and SL4
MSSW_DIFFERE
NT
Master and slave software

different alarm
Major
SCC
MW_FECUNCOR
Microwave FEC uncorrectable
Minor
IF1A and IF1B
MW_LIM
Microwave link identifier

mismatch
Major
IF1A, IF1B, IF0A,

IF0B, and IFX
MW_LOF
Loss of microwave frame
Critical
IF1A, IF1B, IF0A,

IF0B, and IFX
MW_RDI
Microwave link remote defect

indication
Minor
IF1A and IF1B
NESF_LOST
Loss of NE software
Critical
SCC
NESTATE_INSTA
LL
NE in install state
Critical
SCC
NO_BD_SOFT
Software file corrupted or

missing
Critical
SD1, SL1, SDE,

SLE, IF1A, IF1B,
PXC, IF0A, IF0B,
IFX, SL4, and EMS6
NP1_MANUAL_S
TOP
N+1 protection protocol

manually disabled
Minor
SCC
NP1_SW_FAIL
N+1 protection switching failed
Major
SCC
NP1_SW_INDI
N+1 protection switching

indicator
Major
SCC
OPM_FAIL
Output optical power failed
Major
SL4
PORT_MODULE_
OFFLINE
Port not in position
Major
EMS6
POWER_ALM
Power module alarm
Major
IF1A, IF1B, PXC,

SCC, FAN
POWER_FAIL
Board power failed
Major
ODU

A-7

A Alarm Reference
A-8
Alarm Name
Description
Alarm
Severit
y
Source Board
P_AIS
PDH interface signal alarm
Major
PL3
P_LOS
Signal lost over the PDH

interface
Major
PL3
PS
Protection switch indication
Major
PO1, PH1, and PD1
R_F_RST
Receiving FIFO reset
Minor
PO1, PH1, and PD1
R_LOC
Receive loss of clock
Critical
SD1, SL1, SDE,

SLE, IF1A, IF1B,
SL4
R_LOF
Receive loss of frame
Critical
SD1, SL1, SDE,

SLE, IF1A, IF1B,
SL4
R_LOS
Receive loss of signal
Critical
SD1, SL1, SDE,

SLE, IF1A, IF1B,
IFX, IF0A, IF0B, and
SL4
R_S_ERR
Received signal error
Critical
PO1, PH1, and PD1
RADIO_MUTE
Radio transmission mute
Warning
ODU
RADIO_RSL_HIG
H
Radio receive signal level too

high
Critical
ODU
RADIO_RSL_LO
W
Radio receive signal level too low
Critical
ODU
RADIO_TSL_HIG
H
Radio transmission signal level

too high
Critical
ODU
RADIO_TSL_LO
W
Radio transmission signal level

too low
Critical
ODU
RELAY_ALARM
Relay alarm
Critical
EOW
RP_LOC
Loss of receiving phaselock ring

clock
Major
PO1, PH1, and PD1
RS_CROSSTR
Regenerator section performance

over threshold
Minor
SD1, SL1, SDE,

SLE, IF1A, IF1B,
IFX, and SL4
S1_SYN_CHANG
E
Reference source change in

S1_Mode
Major
SCC
SYN_BAD
Synchronous source degraded
Minor
PXC

Issue 02 (2008-6-20)

Issue 02 (2008-6-20)
A Alarm Reference
Alarm Name
Description
Alarm
Severit
y
Source Board
SYNC_C_LOS
Synchronous source level loss
Warning
SCC
T_ALOS
E1 interface loss of analog signal
Major
PO1, PH1, and PD1
T_F_RST
Transmission FIFO reset
Minor
PO1, PH1, and PD1
T_FIFO_E
Transmission FIFO overflow
Minor
PO1, PH1
T_LOC
Transmit loss of clock
Major
SD1, SL1, SDE,

SLE, and SL4
T_LOS
Transmit loss of signal
Major
SD1, SL1, SDE,

SLE, and SL4
TEMP_ALARM
Temperature over threshold
Minor
IF1A, IF1B, EFT4,

PXC, SCC, EMS6,
IF0A, IF0B, and IFX
TU_AIS
TU alarm indication
Major
PO1, PH1, IF0A,

IF0B, PD1, and PL3
TU_AIS_VC12
VC-12 tributary unit alarm

indication
Major
EFT4 and EMS6
TU_AIS_VC3
VC-3 tributary unit alarm

indication
Major
EFT4 and EMS6
TU_LOP
TU loss of pointer
Major
PO1, PH1, IF0A,

IF0B, PD1, and PL3
TU_LOP_VC12
VC-12 tributary unit loss of

pointer
Major
EFT4 and EMS6
TU_LOP_VC3
VC-3 tributary unit loss of

pointer
Major
EFT4 and EMS6
UP_E1_AIS
2M up signal alarm indication
Minor
PO1, PH1, and PD1
VCAT_LOA
Virtual concatenation delay

crosses the threshold
Critical
EFT4 and EMS6
VCAT_LOM_VC1
2
The multiframe indication of

members in VC-12 virtual
concatenation mismatches
Major
EFT4 and EMS6
VCAT_LOM_VC3
The multiframe indication of

Major
EFT4 and EMS6
VCAT_SQM_VC1
2
The serial number indication of

Major
EFT4 and EMS6

A-9

A Alarm Reference
Alarm Name
Description
Alarm
Severit
y
Source Board
VCAT_SQM_VC3
The serial number indication of

Major
EFT4 and EMS6
VOLT_LOS
Loss of voltage
Major
PXC, IF1A, IF1B,

IF0A, IF0B, and IFX
WRG_BD_TYPE
Wrong board type
Major
SCC
WRG_DEV_TYPE
Wrong device type
Critical
SCC
WS_LOS
Wayside interface loss of signal
Major
PXC
W_R_FAILURE
Read and write board chip

register failed
Major
EMS6
XCP_INDI
XCS protection switching

indication
Major
SCC
XPIC_LOS
XPIC signal lost
Critical
IFX
A.2 Alarms and Corrective procedures

This topic describes all the possible alarms of the OptiX RTN 600 and how to handle these
alarms.
A.2.1 A_LOC
Description
The A_LOC is an alarm indicating that the clock signal is lost in the adding bus.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
A-10

Issue 02 (2008-6-20)

Name
Meaning
Parameter 1
The value is always 0x01.
A Alarm Reference
Parameters 23 Indicate the ID of the path that reports the alarm. For example, 0x00 0x01
indicates that the alarm is reported by path 1.
Impact on System
The board services are interrupted.
Possible Causes
The board is faulty.
Handling Procedure
Replace the faulty board.
----End
Related Information
None.
A.2.2 APS_MANUAL_STOP
Description
The APS_MANUAL_STOP is an alarm indicating that the MSP protocol is manually disabled.
Attribute
Alarm Severity
Alarm Type
Minor
Processing alarm
Parameters
table.
Name
Meaning
Parameter 1 Indicates the type of a protection group.
Issue 02 (2008-6-20)
0x01 indicates a linear MSP group.
0x02 indicates a ring MSP group.

A-11

A Alarm Reference
Name
Meaning
Parameter 2 Indicates the ID of the protection group that reports the alarm. For example, 0x01
indicates that the alarm is reported by protection group 1.
Impact on System
When the APS_MANUAL_STOP alarm arises, the MSP or the switching might fail.
Possible Causes
The MSP protocol is manually disabled.
Handling Procedure
Enable the MSP protocol.
----End
Related Information
None.
A.2.3 ALM_GFP_dCSF
Description
The ALM_GFP_dCSF is an alarm indicating that the generic framing procedure (GFP) customer
signal is lost. This alarm is reported if a board detects that a GFP customer signal management
frame is received from the remote station.
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Parameters 23 Indicate the ID of the VCTRUNK that reports the alarm. For example, 0x00
0x01 indicates that the alarm is reported by VCTRUNK 1.
A-12

Issue 02 (2008-6-20)

A Alarm Reference
Impact on System
The services are interrupted.
Possible Causes
The related Ethernet port on the remote board is not well connected.
Handling Procedure
Handle the alarm occurred to the remote board.
----End
Related Information
None.
A.2.4 ALM_GFP_dLFD
Description
The ALM_GFP_dLFD is an alarm indicating that the GFP frame is out of frame. This alarm is
reported if a board detects that the GFP frame is out of frame.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
Issue 02 (2008-6-20)

A-13

A Alarm Reference
Possible Causes
l
The source and the sink VCTRUNKs are configured with different paths or timeslots.
Errors exist on a link or the link is faulty.
Handling Procedure
Step 1 Check whether the VCTRUNK at the local end and the VCTRUNK at the remote end are
configured with the same number of physical paths and timeslots.
If ...
Then ...
No,
Correct the configuration.
Yes,
Go to the next step.
Step 2 Check whether a failure or bit errors occur in the line that services pass.
If ...
Then ...
Yes,
Rectify the fault.
No,
Step 3 Replace the board that reports the ALM_GFP_dLFD alarm.

----End
Related Information
None.
A.2.5 ALM_RTC_FAIL
Description
The ALM_RTC_FAIL is an alarm indicating that the real time clock (RTC) of the equipment
fails.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
None.
A-14

Issue 02 (2008-6-20)

A Alarm Reference
Impact on System
None.
Possible Causes
The RTC of the SCC board is faulty.
Handling Procedure
Step 1 Reset the SCC board.
If ...
Then ...
The ALM_RTC_FAIL alarm disappears after

the resetting,
Reset the NE clock, and complete the

alarm handling.
The alarm persists,
Step 2 Replace the SCC board.

----End
Related Information
None.
A.2.6 APS_FAIL
Description
The APS_FAIL is an alarm indicating that the MSP switching fails.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
table.
Issue 02 (2008-6-20)

A-15

A Alarm Reference
Name
Meaning

l
Parameter 2 Indicates the ID of the protection group that reports the APS_FAIL alarm. For
example, 0x01 indicates that the alarm is reported by protection group 1.
Impact on System
The services cannot be switched. If the current paths are not available, the services are
interrupted.
Possible Causes
l
The parameters of the MSP are incorrectly configured.
The parameters of the MSP are lost.
Handling Procedure
Step 1 Check whether the parameters of the MSP are correctly configured.
If ...
Then ...
No,
Configure the MSP parameters correctly.
Yes,
Step 2 Check the networkwide MSP protocol, and then disable and restart the protocol manually.
If ...
Then ...
The APS_FAIL alarm disappears after the

protocol is restarted,
The fault is rectified, and the alarm handling

is complete.
The APS_FAIL alarm persists after the

Contact the technical support engineers of

Huawei.
----End
Related Information
None.
A.2.7 APS_INDI
Description
The APS_INDI is an alarm indicating that MSP protection switching is detected.
A-16

Issue 02 (2008-6-20)

A Alarm Reference
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
table.
Name
Meaning

l
Parameter 2 Indicates the ID of the protection group that reports the APS_INDI alarm. For
Impact on System
During the MSP switching (within 50 ms), the services are interrupted. After the MSP switching
is complete, the services are restored to normal. During the MSP switching, the extra services
are interrupted.
Possible Causes
MSP switching occurs to the services.
Handling Procedure
Locate the causes of the switching and take appropriate measures.
NOTE
After the non-revertive 1+1 linear MSP switching occurs, the APS_INDI alarm is generated. When the
working path is restored to normal, the services are not automatically switched to the working path and the
APS_INDI alarm persists. In this case, you need to switch the services from the protection path to the
working path manually. After the switching is successful, the APS_INDI alarm is cleared.
----End
Related Information
None.
A.2.8 AU_AIS
Issue 02 (2008-6-20)

A-17

A Alarm Reference
Description
The AU_AIS is an alarm indicating AU alarms. This alarm is reported if the AU pointers of
three consecutive frames are detected to be all "1"s.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Indicates the ID of the line port that reports the alarm. For example, 0x01
indicates the alarm is reported by port 1 of the related board.
Parameters 23 Indicate the ID of the AU-4 path that reports the alarm. For example, 0x00
0x01 indicates the alarm is reported by AU-4 path 1 in the SDH signal.
Impact on System
Services in AU-4 paths are interrupted. If the services are configured with protection, protection
switching may be triggered.
Possible Causes
l
The AU_AIS alarm is inserted at the remote station.
The transmit unit of the remote station is faulty.
The receive unit of the local station is faulty.
Handling Procedure
Step 1 Based on the alarm parameters, locate the AU-4 path that reports the alarm.
Step 2 Check whether the remote station has the alarms that can trigger the AU_AIS alarm.
If ...
Then ...
Yes,
Handle the alarms at the remote station first.
No,
Step 3 Replace the line board of the remote station.

A-18

Issue 02 (2008-6-20)

A Alarm Reference
If ...
Then ...
The alarm disappears after the line board is The fault is rectified, and the alarm handling
replaced,
is complete.
The alarm persists after the line board is
replaced,
Step 4 Replace the cross-connect and timing board of the remote station.
If ...
Then ...
The alarm disappears after the crossconnect and timing board is replaced,

is complete.
The alarm persists after the cross-connect

and timing board is replaced,
Step 5 Replace the board that reports the alarm.

----End
Related Information
None.
A.2.9 AU_LOP
Description
The AU_LOP is an alarm indicating that AU pointer is lost. This alarm is reported if a board
detects that the AU-PTR value of eight consecutive frames is invalid or is NDF revertive.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
indicates the alarm is reported by port 1 of the board.
0x01 indicates that the alarm is reported by AU-4 path 1 in the SDH signal.
Issue 02 (2008-6-20)

A-19

A Alarm Reference
Impact on System
Services in AU-4 paths are interrupted. If the services are configured with protection, protection
Possible Causes
l
Handling Procedure
Step 1 Based on the alarm parameters, locate the AU-4 channel that reports the alarm.
If ...
Then ...
The alarm disappears after the line board is The fault is rectified, and the alarm handling
replaced,
is complete.
The alarm persists after the line board is
replaced,
If ...
Then ...
The alarm disappears after the crossconnect and timing board is replaced,

is complete.
The alarm persists after the cross-connect

and timing board is replaced,

----End
Related Information
None.
A.2.10 B1_EXC
Description
The B1_EXC is an alarm indicating that the regenerator section (B1) has excessive errors. This
alarm is reported if a board detects that the B1 bit errors exceed the preset B1_EXC alarm
threshold (10-3 by default).
The IF boards that work in the PDH mode may also report this alarm. This alarm is detected by
the self-defined overhead bytes B1 in PDH microwave frames.
A-20

Issue 02 (2008-6-20)

A Alarm Reference
Attribute
Alarm Severity
Alarm Type
Minor
Service alarm
Parameters
table.
Name
Meaning
Parameter 1
indicates the alarm is reported by port 1 of the related board.
Parameters 23 Indicate the path ID.
Impact on System
The services on the port are interrupted.
Possible Causes
l
The line performance degrades.
Handling Procedure
For details, refer to 4.4 Troubleshooting Bit Errors.
----End
Related Information
None.
A.2.11 B1_SD
Description
The B1_SD is an alarm indicating that the regenerator section (B1) signal degrades. This alarm
is reported if a board detects that the B1 bit errors exceed the preset B1_SD alarm threshold
(10-6 by default).
The IF boards that work in the PDH mode may also report this alarm. This alarm is detected by
the self-defined overhead bytes B1 in PDH microwave frames.
Issue 02 (2008-6-20)

A-21

A Alarm Reference
Attribute
Alarm Severity
Alarm Type
Minor
Service alarm
Parameters
table.
Name
Meaning
Parameter 1
indicates that the alarm is reported by port 1 of the related board.
Impact on System
The service performance on the port degrades.
Possible Causes
l
Handling Procedure
Refer to 4.4 Troubleshooting Bit Errors.
----End
Related Information
None.
A.2.12 B2_EXC
Description
The B2_EXC is an alarm indicating that the multiplex section (B2) has excessive errors. This
alarm is reported if a board detects that the B2 bit errors exceed the preset B2_EXC alarm
threshold (10-3 by default).
A-22

Issue 02 (2008-6-20)

A Alarm Reference
Attribute
Alarm Severity
Alarm Type
Major
Service alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
The services on the port are interrupted. If the services are configured with protection, protection
Possible Causes
l
Handling Procedure
----End
Related Information
None.
A.2.13 B2_SD
Description
The B2_SD is an alarm indicating that the regenerator section (B2) signal degrades. This alarm
is reported if a board detects that the B2 bit errors exceed the preset B2_SD alarm threshold
(10-6 by default).
Issue 02 (2008-6-20)

A-23

A Alarm Reference
Attribute
Alarm Severity
Alarm Type
Minor
Service alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
The services on the interface degrade.
Possible Causes
l
Handling Procedure
----End
Related Information
None.
A.2.14 B3_EXC
Description
The B3_EXC is an alarm indicating that the higher order path (B3) has excessive errors. This
alarm is reported if a board detects the B3 bit errors exceed the preset B3_EXC alarm threshold
(10-3 by default).
A-24

Issue 02 (2008-6-20)

A Alarm Reference
Attribute
Alarm Severity
Alarm Type
Major
Service alarm
Parameters
table.
Name
Meaning
Parameter 1
0x01 indicates that the alarm is reported by AU-4 path 1.
Impact on System
The services in the path are interrupted.
Possible Causes
l
Handling Procedure
----End
Related Information
None.
A.2.15 B3_EXC_VC3
Description
The B3_EXC_VC3 is an alarm indicating that excessive B3 bit errors exist in the VC-3 path.
This alarm is reported if a board detects that the B3 bit errors cross the preset threshold of the
B3_EXC_VC3 (10-3 by default).
Issue 02 (2008-6-20)

A-25

A Alarm Reference
Attribute
Alarm Severity
Alarm Type
Major
QoS alarm
Parameters
table.
Name
Meaning
Parameter 1
indicates that the alarm is reported by VC-3 path 1.
Impact on System
A large number of bit errors exist in the services in the VC-3 path.
Possible Causes
l
Handling Procedure
----End
Related Information
None.
A.2.16 B3_SD
Description
The B3_SD is an alarm indicating that the higher order path (B3) signal degrades. This alarm is
reported if a board detects that the B3 bit errors exceed the preset B3_SD alarm threshold
(10-6 by default).
A-26

Issue 02 (2008-6-20)

A Alarm Reference
Attribute
Alarm Severity
Alarm Type
Minor
Service alarm
Parameters
table.
Name
Meaning
Parameter 1
0x01 indicates that the alarm is reported by AU-4 path 1.
Impact on System
Services in the path degrade. If the services are configured with protection, protection switching
may be triggered.
Possible Causes
l
Handling Procedure
----End
Related Information
None.
A.2.17 B3_SD_VC3
Description
The B3_SD_VC3 is an alarm indicating that the B3 bits in the VC-3 path deteriorate. This alarm
is reported if a board detects that the B3 bit errors cross the preset threshold of the B3_SD_VC3
(10-6 by default).
Issue 02 (2008-6-20)

A-27

A Alarm Reference
Attribute
Alarm Severity
Alarm Type
Minor
Service alarm
Parameters
table.
Name
Meaning
Parameter 1
indicates that the alarm is reported by VC-3 path 1.
Impact on System
The services in this VC-3 path degrade.
Possible Causes
l
Handling Procedure
----End
Related Information
None.
A.2.18 BD_NOT_INSTALLED
Description
The BD_NOT_INSTALLED is an alarm indicating that a slot is not installed with the logical
board.
A-28

Issue 02 (2008-6-20)

A Alarm Reference
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1
Indicates the slot ID.
Impact on System
The physical board installed in the slot fails to work.
Possible Causes
l
The slot is not configured with the logical board.
The physical board is installed into a wrong slot during the board replacement.
Handling Procedure
Step 1 Check whether the physical board is installed into a wrong slot.
If ...
Then ...
Yes,
Install the physical board into the correct slot.
No,
Step 2 Configure the logical board through the NMS.

----End
Related Information
None.
A.2.19 BD_STATUS
Description
The BD_STATUS is an alarm indicating that the board is not in position.
Issue 02 (2008-6-20)

A-29

A Alarm Reference
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None.
Impact on System
The board that reports the alarm fails to work.
Possible Causes
If the board that reports the alarm is in the IDU, the possible causes are as follows:
l
The board is installed in an incorrect slot.
The board and the backplane are poorly connected.
The slot is faulty.
If the board that reports the alarm is in the ODU, the possible causes are as follows:
l
The ODU is faulty.
The power supply of the ODU is switched off.
The IF cables are poorly connected.
The IF boards are faulty.
Handling Procedure
Step 1 Locate the board that reports the alarm.
If ...
Then ...
The ODU reports the alarm,
Perform Step 2 through Step 6.
The IDU reports the alarm,
Perform Step 7 through Step 11.
Step 2 Check whether the ODU is powered on.

If ...
Then ...
Yes,
No,
Power on the ODU.
Step 3 Check whether the IF cables are correctly connected.
A-30
If ...
Then ...
Yes,

Issue 02 (2008-6-20)

If ...
Then ...
No,
Connect the cables correctly.
A Alarm Reference
Step 4 Replace the ODU.

If ...
Then ...
The alarm disappears after the board is

replaced,

is complete.
The alarm persists after the board is

replaced
Step 5 Replace the IF cables.

If ...
Then ...
The alarm disappears after the cables are

replaced,

is complete.
The alarm persists after the cables are

replaced
Step 6 Replace the IF board.

Step 7 Check whether the board that reports the alarm is installed in the correct slot.
If ...
Then ...
No,
Re-install the board in the correct slot.
Yes,
Step 8 Remove and insert the board again.

If ...
Then ...

removed and inserted,

is complete.


If ...
Then ...

replaced,

is complete.

replaced,
Step 10 Install the board into another slot.

If the board reports no alarm in the new slot, you can infer that the previous slot is faulty.
Step 11 Keep the board working in the new slot, and contact the technical support engineers of Huawei.
----End
Issue 02 (2008-6-20)

A-31

A Alarm Reference
Related Information
None.
A.2.20 BIP_EXC
Description
The BIP_EXC is an alarm indicating that excessive BIP errors arise. This alarm is reported if
the BIP2 bit errors in the V5 byte exceed the preset BIP_EXC alarm threshold (10-3 by default).
Attribute
Alarm Severity
Alarm Type
Minor
Service alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
The services in the path are interrupted.
Possible Causes
l
Handling Procedure
----End
Related Information
None.
A-32

Issue 02 (2008-6-20)

A Alarm Reference
A.2.21 BIP_SD
Description
The BIP_SD is an alarm indicating that the BIP signal degrades. This alarm is reported if the
BIP2 bit errors in the V5 byte exceed the preset BIP_SD alarm threshold (10-6 by default).
Attribute
Alarm Severity
Alarm Type
Minor
Service alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
The services in the path degrade.
Possible Causes
l
Handling Procedure
----End
Related Information
None.
A.2.22 BOOTROM_BAD
Issue 02 (2008-6-20)

A-33

A Alarm Reference
Description
The BOOTROM_BAD is an alarm indicating that the BOOTROM data check fails. This alarm
is reported if the system detects that the BOOTROM data is corrupted.
Attribute
Alarm Severity
Alarm Type
Major alarm
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1
Indicates the type of BOOTROM data corruption.

l
0x01 indicates that the basic BIOS is corrupted.
0x02 indicates that the extended BIOS is corrupted.
Impact on System
This alarm indicates that errors arise in the system database processing. Some system
configuration data may be lost, and some query and setting commands may fail. Hence, some
system functions may fail.
l
If an NE is working, the BOOTROM_BAD dose not affect the system and running services.
If you hard reset the board in the case of a BOOTROM_BAD alarm, the board fails to load
the BIOS and thus fails to start.
Possible Causes
l
The basic BIOS is corrupted
The extended BIOS is corrupted
The BOOTROM database is corrupted.
Handling Procedure
Replace the board that reports the alarm.
----End
Related Information
None.
A-34

Issue 02 (2008-6-20)

A Alarm Reference
A.2.23 C2_VCAIS
Description
The C2_VCAIS is an alarm indicating that a mismatched signal label byte is received. This alarm
is reported if the C2 byte received by the board is "0xFF".
Attribute
Alarm Severity
Alarm Type
Minor alarm
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
None.
Possible Causes
The C2 byte received from the remote end is incorrectly configured.
Handling Procedure
Step 1 Based on the alarm parameters, locate the VC path that reports the alarm.
Step 2 Change C2 to be Received of the remote station based on the actual situation.
----End
Related Information
None.
A.2.24 CONFIG_NOSUPPORT
Issue 02 (2008-6-20)

A-35

A Alarm Reference
Description
The CONFIG_NOSUPPORT is an alarm indicating that the configuration is not supported. This
alarm is reported if the ODU detects that the configured parameters do not match those of the
ODU.
Attribute
Alarm Severity
Alarm Type
Major
Processing alarm
Parameters
table.
Name
Meaning
Parameter 1
Indicates the mismatched parameter.

l
0x01: Indicates the frequency configuration error.
0x02: Indicates the TR spacing configuration error.
0x03: Indicates the transmit power configuration error.
0x04: Indicates the ATPC threshold configuration error.
0x05: Indicates the bandwidth configuration error.
0x06: Indicates the modulation mode configuration error.
Impact on System
The ODU fails to work normally. If the equipment is configured with 1+1 FD protection, the
main ODU generates the CONFIG_NOSUPPORT alarm. In this case, IF 1+1 protection
Possible Causes
The type of the ODU mismatches the configured parameters.
Handling Procedure
Step 1 Determine the mismatched parameter according to the alarm parameters.
Step 2 Check whether the configured parameters meet the network planning requirements.
A-36
If ...
Then ...
Yes,
Replace the ODU with a correct one.

Issue 02 (2008-6-20)

If ...
Then ...
No,
Modify the parameters.
A Alarm Reference
----End
Related Information
None.
A.2.25 DBMS_ERROR
Description
The DBMS_ERROR is an alarm indicating that errors occur in the system database processing.
Attribute
Alarm Severity
Alarm Type
Major
Processing alarm
Parameters
table.
Issue 02 (2008-6-20)

A-37

A Alarm Reference
Name
Meaning
Parameter 1 Indicates the type of the database error.

l
0x01: Indicates that the entered parameter is illegal.
0x02: Indicates that no database file exists.
0x03: Indicates that the database storage area numbers are incorrect.
0x04: Indicates that a database overwriting occurs.
0x05: Indicates that errors occur in the header information check in the
database backup area.
0x06: Indicates that errors occur in the FAT table structure check in the
database storage area.
0x07: Indicates that errors occur in the database check in the database backup
area.
0x08: Indicates that restoring the database fails.
0x09: Indicates an invalid database ID.
0x0A: Indicates that the databases are different.
0x0B: Indicates that the data is unchecked.
0x0E: Indicates that the semaphore handle is invalid.
0x0F: Indicates that errors occur in memory applying.
0x10: Indicates that errors occur in memory releasing.
0x12: Indicates that transmitting the message packets fails.
0x13: Indicates that the start record is queried to be incorrect.
0x14: Indicates that the database is null.
0x15: Indicates that the mark is incorrectly set.
0x16: Indicates that the entered command parameters are incorrect.
0x17: Indicates that this is not a backup database.
0x18: Indicates that the database is in the protected mode.
0x19: Indicates that the configuration is not verified.
Parameter 2 Indicates the database memory area in which errors occur.

l
0x00: Indicates the database in the FDB0.
0x01: Indicates the database in the FDB1.
0x02: Indicates the database in the DRDB.
Parameter 3 Indicates the incorrect database ID.

l
0x00: Indicates the IDs of all the databases in the storage area.
0x010xff: Indicates the ID of a specific database.
Impact on System
When the DBMS_ERR alarm occurs, it indicates that errors occur in the system database
processing. The system configuration may be lost. As a result, the failure indication is returned
for some query and setting commands, and some system functions cannot work.
A-38

Issue 02 (2008-6-20)

A Alarm Reference
Possible Causes
l
The database operation fails.
The data in the database is corrupted.
The SCC board is faulty.
Handling Procedure
Step 1 SCC resets.
If ...
Then ...
The DBMS_ERROR alarm disappears after

SCC resetting,
The fault is rectified, and the alarm

handling is complete.
The DBMS_ERROR alarm persists after SCC Go to the next step.

resetting,
Step 2 Replace the boardIDU that reports the DBMS_ERROR alarm.
----End
Related Information
None.
A.2.26 DBMS_PROTECT_MODE
Description
The DBMS_PROTECT_MODE is an alarm indicating that the system database is in protection
mode.
Attribute
Alarm Severity
Alarm Type
Critical
Processing alarm
Parameters
None.
Impact on System
When the DBMS_PROTECT_MODE alarm arises, you can infer that errors occur in the system
database processing, which then may cause configuration data loss. As a result, some query and
setting commands may fail, and some system functions may become unavailable.
Possible Causes
The NE software is reset frequently.
Issue 02 (2008-6-20)

A-39

A Alarm Reference
Handling Procedure
Replace the board that reports the DBMS_PROTECT_MODE alarm.
----End
Related Information
None.
A.2.27 DN_E1_AIS
Description
The DN_E1_AIS is an alarm indicating that the 2-MHz downlink signal is abnormal. This alarm
is reported if the tributary board detects that the downlink E1 signal is all "1"s.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
The E1 signal is unavailable.
Possible Causes
l
The tributary board of the remote station transmits the E1_AIS signal.
The receive unit of the tributary board of the local station is faulty.
The cross-connect board of the local station is faulty.
Handling Procedure
Step 1 Check whether the remote station has the UP_E1_AIS or T_ALOS alarm.
A-40

Issue 02 (2008-6-20)

If ...
Then ...
Yes,
Clear the alarm.
No,
A Alarm Reference

If ...
Then ...

replaced,

is complete.

replaced,
Step 3 Replace the cross-connect and timing board of the local station.
----End
Related Information
None.
A.2.28 E1_LOC
Description
The E1_LOC is an alarm indicating that the uplink 2-MHz clock signal is lost. This alarm is
reported if the tributary board fails to extract clock signals from the input E1 signal.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1 Indicates the ID of the tributary port or path that reports the alarm. For example,
0x01 indicates that the alarm is reported by the first port 1 or path 1 of the related
board.
Impact on System
This alarm has no impact on the services.
Issue 02 (2008-6-20)

A-41

A Alarm Reference
Possible Causes
l
The waveform of the input E1 signal is abnormal.
Handling Procedure
Step 1 Check whether the remote station is faulty.
If ...
Then ...
Yes,
Rectify the fault.
No,
Step 2 Check whether there is external interference that causes abnormal E1 signal waveform.
If ...
Then ...
Yes,
The fault is rectified, and the alarm handling is complete.
No,
Contact the technical support engineers of Huawei.
Step 3 Replace the boardthat reports the alarm.

----End
Related Information
None.
A.2.29 E1_LOS
Description
The E1_LOS is an alarm indicating that the 2-MHz line signal (E1 signal) is lost. This alarm is
reported if the tributary board detects that the uplink E1 signal is all "0"s.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
A-42

Issue 02 (2008-6-20)

Name
Meaning
Parameter 1
A Alarm Reference
Impact on System
E1 services are interrupted.
Possible Causes
l
The input E1 signal is abnormal.
The tributary board of the local station is faulty.
Handling Procedure
If ...
Then ...
Yes,
Rectify the fault.
No,

----End
Related Information
None.
A.2.30 ESN_FAILED
Description
The ESN_FAILED is an alarm indicating that the electronic serial number (ESN) of the
equipment fails.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
Issue 02 (2008-6-20)

A-43

A Alarm Reference
table.
Name
Meaning
Parameter 1
Indicates the ID of the SCC board that reports the ESN_FAILED alarm.
Impact on System
None.
Possible Causes
l
Reading the equipment ESN fails.
The verification of the equipment ESN fails.
Handling Procedure
Replace the SCC board that reports the ESN_FAILED alarm.
----End
Related Information
None.
A.2.31 ESN_INVALID
Description
The ESN_INVALID is an alarm indicating that the electronic serial number (ESN) of the
equipment is invalid.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1 Indicates the ID of the SCC board that reports the ESN_INVALID alarm.
A-44

Issue 02 (2008-6-20)

A Alarm Reference
Impact on System
None.
Possible Causes
The ESN that is read from the SCC board is verified, but it cannot be identified.
Handling Procedure
Contact the technical support engineers of Huawei to upgrade the NE software.
----End
Related Information
None.
A.2.32 ETH_LOS
Description
The ETH_LOS is an alarm indicating that the Ethernet port is disconnected.
Attribute
Alarm Severity
Alarm Type
Critical alarm
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Indicates the ID of the Ethernet port that reports the alarm. For example, 0x01
indicates that the alarm is reported by Ethernet port 1 of the related board.
Parameters 23 The values are always 0x00 and 0x01, respectively.
Impact on System
The services carried over the port are interrupted.
Possible Causes
l
Issue 02 (2008-6-20)
The Ethernet cable or optical fiber connected to the port is faulty.

A-45

A Alarm Reference
l
The equipment connected to the port is faulty.
The working mode of the port does not match that of the port at the remote end.
Handling Procedure
Step 1 Check the Ethernet cable or optical fiber connected to the port.
If ...
Then ...
The Ethernet cable or optical fiber is loose Reconnect or replace the Ethernet cable or
or damaged,
optical fiber.
The connector of the optical fiber is dirty,
Clean the connector of the optical fiber.
The connector of the optical fiber is loose or Reconnect or replace the connector.
damaged,
The Ethernet cable or optical fiber is
connected properly to the port,
Step 2 Check whether the equipment connected to the port is faulty.

If ...
Then ...
Yes,
Rectify the fault.
No,
Step 3 Check whether the working modes of the ports at both ends match each other.
If ... Then ...
No,
Reset the working modes at both ends and ensure that they match each other.
Yes, Go to the next step.

Step 4 Replace the board that reports the ETH_LOS alarm.
----End
Related Information
None.
A.2.33 EXT_SYNC_LOS
Description
The EXT_SYNC_LOS is an alarm indicating that the external clock source is lost.
Attribute
A-46
Alarm Severity
Alarm Type
Critical
Equipment alarm
Issue 02 (2008-6-20)

A Alarm Reference
Parameters
table.
Name
Meaning
Parameter 1 Indicates the ID of the external clock that reports the alarm. For example, 0x01
indicates that the alarm is reported by external clock 1.
Impact on System
l
If the clock source priority table is configured with the external and internal clock sources
only, the internal clock source is traced and the clock enters the free-run mode after the
loss of the external clock source.
If the clock source priority table is configured with other valid clock sources, the loss of
the external clock source can trigger clock protection switching.
Possible Causes
The clock priority table has the external clock source, but the external clock source cannot be
detected or is unavailable.
Handling Procedure
Step 1 Check whether the clock source device at the remote end is faulty.
If ...
Then ...
Yes,
Rectify the fault.
No,
Step 2 Check whether the cable of the external clock source is normal.
If ...
Then ...
No,
Replace the cable.
Yes,
Step 3 Replace the cross-connect and timing board that connects to the clock source.
----End
Related Information
None.
A.2.34 F1PORT_FAILED
Issue 02 (2008-6-20)

A-47

A Alarm Reference
Description
The F1PORT_FAILED is an alarm indicating that the synchronous data port fails. This alarm
is reported if the synchronous data portrelated data is configured but the SCC does not provide
a synchronous data port.
Attribute
Alarm Severity
Alarm Type
Minor alarm
Communication alarm
Parameters
None.
Impact on System
The synchronous data portrelated configuration is invalid.
Possible Causes
The portable memory card located in the SCC is configured with synchronous data portrelated
data, but the SCC does not provide a synchronous data port.
Handling Procedure
Step 1 Check whether the synchronous data portrelated data is required.
If ...
Then ...
Required,
Not required,
Delete the data through the T2000.
Step 2 Replace the SCC board with an SL61 of VER.C or higher.

----End
Related Information
None.
A.2.35 FAN_FAIL
Description
The FAN_FAIL is an alarm indicating that the fan fails.
A-48

Issue 02 (2008-6-20)

A Alarm Reference
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None.
Impact on System
The heat dissipation is affected.
Possible Causes
l
Handling Procedure
Step 1 Remove and insert the fan board. Clear the dust on the fan and re-install the fan board.
If ...
Then ...


is complete.


----End
Related Information
None.
A.2.36 FCS_ERR
Description
The FCS_ERR is an alarm indicating that errors occur in the verification of the frame check
sequence (FCS). This alarm is reported if errors occur when a board performs FCS verification
for the received frames.
Attribute
Issue 02 (2008-6-20)
Alarm Severity
Alarm Type
Critical
Communication alarm
A-49

A Alarm Reference
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
When the encapsulation protocols or the encapsulation parameters at both ends of the Ethernet
service are different, the service is interrupted or bit errors arise.
Possible Causes
l
The encapsulation protocols or the encapsulation parameters at both ends of the Ethernet
service are different.
Bit errors exist in the service path.
Handling Procedure
Step 1 Check whether the encapsulation protocols at both ends of the Ethernet service are the same.
If ...
Then ...
No,
Yes,
Step 2 Check whether the encapsulation parameters at both ends of the Ethernet service are the same.
If ...
Then ...
No,
Yes,
Step 3 Check whether any bit error alarm or performance event occurs on the line boards through which
the service travels.
If ...
Then ...
Yes,
Handle the alarm or performance event.
No,
Step 4 Replace the board on which the FCS_ERR alarm occurs.

A-50

Issue 02 (2008-6-20)

A Alarm Reference
If ...
Then ...
The FCS_ERR alarm disappears after the

board is replaced,

is complete.
The FCS_ERR alarm persists after the

board is replaced,
Step 5 Replace the cross-connect board.

----End
Related Information
None.
A.2.37 HARD_BAD
Description
The HARD_BAD is an alarm indicating hardware errors.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
table.
Issue 02 (2008-6-20)

A-51

A Alarm Reference
Name
Meaning
Parameter 1 Indicates the fault cause.

l
0x01: Indicates that the power module is working abnormally.
0x02: Indicates that the board is improperly installed.
0x03: Indicates that the 38-MHz system clock 1 is abnormal.
0x04: Indicates that the 38-MHz system clock 2 is abnormal.
0x05: Indicates that the 2-MHz clock source is abnormal.
0x06: Indicates that the digital phase-locked loop is abnormal.
0x07: Indicates that the 38-MHz service clock is lost.
0x08: Indicates that the bus is abnormal.
0x09: Indicates that the TPS protection board is abnormal.
0x0A: Indicates that the primary crystal oscillator stops oscillating.
0x0B: Indicates the frequency offset of the primary crystal oscillator is

excessive.
0x0C: Indicates that the secondary crystal oscillator stops oscillating.
0x0D: Indicates that the processor (CPU/DSP/coprocessor) is faulty.
0x0E: Indicates that the storage components are faulty.
0x0F: Indicates that the programmable logic device is faulty.
0x10: Indicates that the SDH components are faulty.
0x11: Indicates that the data communication components are faulty.
0x12: Indicates that the clock components are faulty.
0x13: Indicates that the interface components are faulty.
0x14: Indicates that the power components are faulty.
0x15: Indicates other faults.
0x16: Indicates that the analog phase-locked loop is abnormal.
0x17: Indicates that the 32-MHz clock is unavailable.
Impact on System
The board that reports the alarm fails to work.
Possible Causes
A-52
The slot is faulty.

Issue 02 (2008-6-20)

A Alarm Reference
Handling Procedure
Step 1 Remove and insert the board again.
If ...
Then ...


is complete.


If ...
Then ...

replaced,

is complete.

replaced,
Step 3 Install the board that reports the alarm into another slot.
If the board reports no alarm in the new slot, you can infer that the previous slot is faulty.
Step 4 Keep the board in the new slot, and contact the technical support engineers of Huawei for
rectifying the fault.
----End
Related Information
None.
A.2.38 HP_CROSSTR
Description
The HP_CROSSTR is an alarm indicating that a performance indicator of the higher order path
crosses the related threshold. This alarm is reported if a board detects that a bit error performance
indicator of the higher order path crosses the preset threshold.
Attribute
Alarm Severity
Alarm Type
Minor
Service alarm
Parameters
table.
Issue 02 (2008-6-20)

A-53

A Alarm Reference
Name
Meaning
Parameter 1
Parameters 23 Indicate the ID of the path that reports the alarm.

Parameters 45
The two most significant bits of Parameter 4 indicate the performance

monitoring period. When the value of the two most significant is "01", the
monitoring period is 15 minutes. When the value of the two most
significant is "02", the monitoring period is 24 hours.
The six least significant bits of Parameter 4 together with Parameter 5

indicate the performance event ID.
Impact on System
The services contain a large amount of bit errors, and the services may be interrupted.
Possible Causes
A bit error performance indicator of the higher order path crosses the preset threshold.
Handling Procedure
Step 1 Check the threshold crossing records of higher order path bit error performance events to
determine the performance event that crosses the preset threshold.
Step 2 Handle the performance event accordingly.
----End
Related Information
None.
A.2.39 HP_LOM
Description
The HP_LOM is an alarm indicating that the multiframe is lost in the higher order path. This
alarm is reported if a board detects that the H4 byte mismatches the expected multiframe
sequence.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
A-54

Issue 02 (2008-6-20)

A Alarm Reference

table.
Name
Meaning
Parameter 1
Impact on System
The services in the path are interrupted. If the services are configured with protection, protection
Possible Causes
l
Handling Procedure
If ...
Then ...

replaced,

is complete.

replaced,
If ...
Then ...

replaced,

is complete.

replaced,

----End
Related Information
None.
A.2.40 HP_RDI
Issue 02 (2008-6-20)

A-55

A Alarm Reference
Description
The HP_RDI is an alarm indicating that signal reception fails at the remote end of the higher
order path. This alarm is reported if a board detects that bit 5 of the G1 byte is "1".
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
The local station is not affected. Signal reception at the remote station, however, is interrupted.
Possible Causes
The local station receives a message from the remote station, and the message indicates that
signal reception fails at the remote end of the higher order path.
Handling Procedure
Step 2 Clear the alarm in the AU-4 path of the remote station.
----End
Related Information
None.
A.2.41 HP_REI
A-56

Issue 02 (2008-6-20)

A Alarm Reference
Description
The HP_REI is an alarm indicating that an error is detected in the remote higher order path. This
alarm is reported if the board detects that the values of bit 1 through bit 4 of the G1 byte range
from "1" to "8".
Attribute
Alarm Severity
Alarm Type
Warning
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
The local station is not affected. The remote station, however, receives bit errors.
Possible Causes
The local station receives a message from the remote station, and the message indicates bit errors
over the remote higher order path.
Handling Procedure
Step 2 Handle the HP_BBE performance event in the AU-4 path of the remote station.
----End
Related Information
None.
A.2.42 HP_SLM
Issue 02 (2008-6-20)

A-57

A Alarm Reference
Description
The HP_SLM is an alarm indicating that a mismatched higher order path signal label is detected.
This alarm is reported if a board detects a mismatched C2 byte.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
None.
Possible Causes
l
The C2 byte to be received at the local station mismatches the C2 byte transmitted by the
remote station.
The data configuration is wrong.
Handling Procedure
Step 2 If the port that reports the alarm is the SDH port used to interconnect ATM/Ethernet equipment,
configure the services to be VC-4 pass-through services.
If ...
Then ...
The alarm disappears after the configurations The fault is rectified, and the alarm handling
are modified,
is complete.
The alarm persists after the configurations are Go to the next step.
modified
Step 3 Unify the service types at the local and remote stations of the AU-4 path.
----End
A-58

Issue 02 (2008-6-20)

A Alarm Reference
Related Information
None.
A.2.43 HP_TIM
Description
The HP_TIM is an alarm indicating that a mismatched higher order path trace identifier is
detected. This alarm is reported if the board detects a mismatched J1 byte.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
If the services are configured with protection and this alarm is the triggering condition, protection
Possible Causes
l
The J1 byte to be received at the local station is different from the J1 byte transmitted from
the remote station.
Data configuration at the intermediate nodes is incorrect.
Handling Procedure
Step 2 If the port that reports the alarm is the SDH port used to interconnect ATM/Ethernet equipment,
configure the services to be VC-4 pass-through services.
Issue 02 (2008-6-20)

A-59

A Alarm Reference
If ...
Then ...
The alarm disappears after the configurations The fault is rectified, and the alarm handling
are modified,
is complete.
The alarm persists after the configurations are Go to the next step.
modified,
Step 3 Set the J1 byte to be received at the local station to the disable mode. Alternatively, set the J1
byte to be received at the local station to be the same as that transmitted from the remote station.
Step 4 Check whether the cross-connections of the intermediate nodes through which the service travels
are correctly configured. If not, correct the cross-connection configuration.
----End
Related Information
None.
A.2.44 HP_UNEQ
Description
The HP_UNEQ is an alarm indicating that the higher order path is unequipped. This alarm is
reported if a board detects that the C2 byte is "0".
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
Services in the AU-4 path are unavailable. If the services are configured with protection and this
alarm is the triggering condition, protection switching may be triggered.
A-60

Issue 02 (2008-6-20)

A Alarm Reference
Possible Causes
The line port of the local station is configured with services, but the line port of the remote station
is not.
Handling Procedure
Step 2 Configure line services for the remote station.
----End
Related Information
None.
A.2.45 HPAD_CROSSTR
Description
The HPAD_CROSSTR is an alarm indicating that a higher order path adaptation performance
indicator crosses the threshold. This alarm is reported if a board detects that a TU pointer
adaptation performance indicator crosses the preset threshold.
Attribute
Alarm Severity
Alarm Type
Minor
Service alarm
Parameters
table.
Name
Meaning
Parameter 1

Parameters 45
Issue 02 (2008-6-20)
The higher two bits of Parameter 4 indicate the performance monitoring

period. When the value of the two most significant bits is "01", the
monitoring period is 15 minutes. When the value of the two most
significant bits is "02", the monitoring period is 24 hours.

indicate the ID of a performance event.

A-61

A Alarm Reference
Impact on System
Bit errors may occur to the services.
Possible Causes
A TU pointer adaptation performance indicator crosses the preset threshold.
Handling Procedure
Step 1 Check the threshold crossing records of the TU pointer adaptation performance events, and
locate the performance event that crosses the preset threshold.
Step 2 Handle the performance event that crosses the threshold.
----End
Related Information
None.
A.2.46 HSB_INDI
Description
The HSB_INDI is an alarm indicating that the microwave equipment is switched over.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1
Indicates the ID of the protection group.
Parameter 2
Indicates the slot where the working board is installed.
Impact on System
The services are interrupted during the protection switching and return to normal after the
switching is complete.
A-62

Issue 02 (2008-6-20)

A Alarm Reference
Possible Causes
1+1 HSB protection switching occurs.
Handling Procedure
Locate the cause of switching, and take appropriate measures.
----End
Related Information
None.
A.2.47 HSM_INDI
Description
The HSM_INDI is an alarm indicating that the microwave channel is switched over.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1
Indicates the ID of the protection group.
Parameter 2
Indicates the slot where the working board is installed.
Impact on System
Bit errors are not generated during channel switching. This alarm has no impact on the services.
Possible Causes
1+1 FD/SD protection switching occurs.
Handling Procedure
----End
Issue 02 (2008-6-20)

A-63

A Alarm Reference
Related Information
None.
A.2.48 IF_CABLE_OPEN
Description
The IF_CABLE_OPEN is an alarm indicating that the IF cable is disconnected.
Attribute
Alarm Severity
Alarm Type
Major alarm
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1 Indicates the ID of the IF port that reports the alarm. For example, 0x01 indicates
that the alarm is reported by IF port 1 of the related board.
Impact on System
The services carried over the IF port are interrupted.
Possible Causes
l
The IF cable is loose or faulty.
The IF port on the IF board is faulty.
The power module of the ODU is faulty.
Handling Procedure
Step 1 Check whether the connector of the IF cable is loose or whether the connector is not properly
made.
A-64
If ...
Then ...
The connector is loose,
Tighten the connector.
The connector is not properly made,
Make a new connector.
None of the above,

Issue 02 (2008-6-20)

A Alarm Reference
Step 2 Check whether the jacket of the IF cable is damaged.

If ... Then ...
Yes, Use a multimeter to test whether the IF cable conducts electricity well, and replace the
cable if it fails to conduct electricity.
No, Go to the next step.
If ...
Then ...
The alarm disappears after the IF board is

replaced,

is complete.
The alarm persists after IF board is

replaced,

----End
Related Information
None.
A.2.49 IF_INPWR_ABN
Description
The IF_INPWR_ABN is an alarm indicating that the input IF power of the ODU is abnormal.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Issue 02 (2008-6-20)
Name
Meaning
Parameter 1
0x01 indicates that the input power is too high.
0x02 indicates that the input power is too low.

A-65

A Alarm Reference
Impact on System
The services on the ODU are interrupted. If 1+1 protection is configured, 1+1 HSB switching
may be triggered.
Possible Causes
l
There is an inloop operation on the IF port.
The IF board is faulty.
The IF cables are faulty.
The ODU is faulty.
Handling Procedure
Step 1 Check whether there is an inloop operation on the IF port.
If ...
Then ...
Yes,
Cancel the loopback operation.
No,
Step 2 Check whether the IF cables are soggy, broken, or pressed.

If ...
Then ...
Yes,
Replace the IF cables.
No,
Step 3 Check whether the cable connector workmanship meets the requirement.
If ...
Then ...
No,
Make a new connector.
Yes,
Step 4 Replace the IF board connecting with the ODU that reports the alarm.
If ...
Then ...
The alarm disappears after the boardis

replaced,

is complete.

replaced,
Step 5 Replace the ODU that reports the alarm.

----End
Related Information
None.
A-66

Issue 02 (2008-6-20)

A Alarm Reference
A.2.50 IF_MODE_UNSUPPORTED
Description
The IF_MODE_UNSUPPORTED is an alarm indicating that the configured IF working mode
is not supported. This alarm is reported if the board is not loaded with the FPGA file that supports
the configured IF working mode.
Attribute
Alarm Severity
Alarm Type
Major alarm
Equipment alarm
Parameters
table.
Name
Meaning
Impact on System
The services carried over the IF port are interrupted.
Possible Causes
The board is not loaded with the FPGA file that supports the configured IF working mode.
Handling Procedure
Contact the technical support engineers of Huawei to upgrade the board software and the FPGA
file.
----End
Related Information
None.
A.2.51 IN_PWR_HIGH
Description
The IN_PWR_HIGH is an alarm indicating that the input power is too high.
Issue 02 (2008-6-20)

A-67

A Alarm Reference
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1 Indicates the ID of the optical interface that reports the alarm. For example, 0x01
indicates that the alarm is reported by optical interface 1 of the board.
Impact on System
Bit errors occur to the services of the optical interface.
Possible Causes
l
The transmit optical power of the remote station is too high.
The type of the optical module is incorrect.
Handling Procedure
Step 1 Based on the alarm parameters, locate the optical interface that reports the alarm.
Step 2 Based on the transmission distance, check whether the type of the SFP optical modules of the
receive and transmit ends is correct.
If ...
Then ...
No,
Replace the optical modules.
Yes,
Step 3 Query the performance events of the transmit optical power at the remote station.
If ...
Then ...
The transmit optical power does not meet the requirement, Replace the optical modules.
The transmit optical power meets the requirement,
Step 4 Add a proper optical attenuator to reduce the receive optical power.
----End
Related Information
None.
A-68

Issue 02 (2008-6-20)

A Alarm Reference
A.2.52 IN_PWR_LOW
Description
The IN_PWR_LOW is an alarm indicating that the input power is too low.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
table.
Name
Meaning
indicates that the alarm is reported by optical interface 1 of the related board.
Impact on System
Bit errors may occur to the services on the optical interface.
Possible Causes
l
The transmit optical power of the remote station is too low.
The fiber performance degrades.
The type of the optical module is incorrect.
Handling Procedure
Step 2 Based on the transmission distance, check whether the type of the SFP optical modules of the
receive and transmit ends is correct .
If ...
Then ...
Yes,
Replace the optical modules.
No,
Step 3 Query the performance events of the transmit optical power at the remote station.
Issue 02 (2008-6-20)

A-69

A Alarm Reference
If ...
Then ...
The transmit optical power does not meet the requirement, Replace the optical modules.
The transmit optical power meets the requirement,
Step 4 Clean the optical fiber connector.

If ...
Then ...
The alarm disappears after the connector is The fault is rectified, and the alarm handling
cleaned,
is complete.
The alarm persists after the connector is
cleaned,
Step 5 Check whether the fiber is broken or pressed.

If ...
Then ...
Yes,
Replace the fiber.
No,
Step 6 Add a proper optical amplifier to increase the receive optical power.
----End
Related Information
None.
A.2.53 J0_MM
Description
The J0_MM is an alarm indicating that a mismatched trace identifier is detected. This alarm is
reported if a board detects a mismatched J0 byte.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
A-70

Issue 02 (2008-6-20)

A Alarm Reference
Name
Meaning
Parameter 1
Impact on System
None.
Possible Causes
The J0 byte to be received by the local station mismatches the J0 byte transmitted by the remote
station.
Handling Procedure
Step 1 Based on the alarm parameters, locate the line port that reports the alarm.
Step 2 Set the J0 byte to be received at the local station to the disable mode.
----End
Related Information
None.
A.2.54 K1_K2_M
Description
The K1_K2_M is an alarm indicating that the K1 and K2 bytes are mismatched. This alarm is
reported if a board detects that the transmitted K1 byte (bits 58) contains a path ID different
from that contained in the received K2 byte.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
Issue 02 (2008-6-20)

A-71

A Alarm Reference
Name
Meaning
Parameter 1 Indicates the type of a protection group. For example, 0x01 indicates a linear
MSP group.
Parameter 2 Indicates the ID of the protection group that reports the K1_K2_M alarm. For
Impact on System
The MSP switching may be abnormal or even fail.
Possible Causes
l
The switching modes at both ends are single-ended switching and dual-ended switching,
respectively.
The equipment is faulty.
Handling Procedure
Step 1 Check whether the services are correctly configured.
If ...
Then ...
No,
Yes,
Step 2 Check whether the fiber connections are correct.

If ...
Then ...
No,
Correct the fiber connections.
Yes,
Step 3 Replace the line board at the remote station.

If ...
Then ...
The K1_K2_M alarm disappears after the

board is replaced

is complete.
The K1_K2_M alarm persists,
Step 4 Replace the board that reports the K1_K2_M alarm.

----End
Related Information
None.
A.2.55 K2_M
A-72

Issue 02 (2008-6-20)

A Alarm Reference
Description
The K2_M is an alarm indicating that a mismatched K2 byte is detected. This alarm is reported
if a board detects that the received K2 byte (bit 5) contains a protection mode different from that
of the local station.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1 Indicates the type of a protection group. For example, 0x01 indicates a linear
MSP group.
Parameter 2 Indicates the ID of the protection group that reports the K2_M alarm. For
Impact on System
The MSP switching may be abnormal or even fail.
Possible Causes
l
Two NEs on a linear MS are configured with different MSP modes, such as 1+1 and 1:N.
When the MSP switching occurs, the MSP protocol at the remote station is disabled.
The equipment is faulty.
Handling Procedure
Step 1 Check whether the two NEs on a linear MS are configured with the same MSP mode.
If ...
Then ...
No,
Yes,
Step 2 Check whether the fiber connections are correct.
Issue 02 (2008-6-20)
If ...
Then ...
No,
Correct the fiber connections.

A-73

A Alarm Reference
If ...
Then ...
Yes,
Step 3 Replace the line board at the remote station.

If ...
Then ...
The K2_M alarm disappears after the board The fault is rectified, and the alarm handling
is replaced,
is complete.
The K2_M alarm persists,
Step 4 Replace the board that reports the K2_M alarm.

----End
Related Information
None.
A.2.56 LASER_CLOSED
Description
The LASER_CLOSED is an alarm indicating that the laser is closed.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Name
Meaning
Impact on System
The optical interface fails to carry services.
Possible Causes
The laser is shut down at the local station.
A-74

Issue 02 (2008-6-20)

A Alarm Reference
Handling Procedure
Step 2 Find out why the laser is shut down, and turn it on promptly.
----End
Related Information
None.
A.2.57 LASER_MOD_ERR_EX
Description
The LASER_MOD_ERR_EX is an alarm indicating that the pluggable optical module on the
board mismatches the optical interface.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Name
Meaning
indicates that the alarm is reported by optical interface 1 of the board.
Impact on System
The services on the optical interface are interrupted.
Possible Causes
l
The rate of the optical module does not match that of the optical interface.
The optical module is faulty.
Handling Procedure
Step 1 Check whether the rate of the optical module and that of the optical interface match each other.
Issue 02 (2008-6-20)

A-75

A Alarm Reference
If ...
Then ...
No,
Replace the optical module with an appropriate one.
Yes,
Replace the optical module with a new one of the same type.
Step 2 Check whether the alarm is cleared.

If ...
Then ...
The alarm disappears after the optical

module is replaced,

is complete.
The alarm persists after the optical module Go to the next step.
is replaced,
----End
Related Information
None.
A.2.58 LCAS_FOPR
Description
The LCAS_FOPR is an alarm indicating that the link capacity adjustment scheme (LCAS)
protocol in the receive direction fails. This alarm is reported if the receive unit of the LCAS
module of a board detects an abnormal state in which the LCAS might fail to negotiate or cannot
negotiate correctly.
Attribute
Alarm Severity
Alarm Type
Major
Processing alarm
Parameters
table.
Name
Meaning
Parameter 1
A-76

Issue 02 (2008-6-20)

A Alarm Reference
Impact on System
The Ethernet service is abnormal.
Possible Causes
l
The downlink virtual concatenation group (VCG) receives repeated sequence numbers due
to incorrect configuration or bit errors on the link.
The LCAS function of the remote VCG is disabled.
The downlink VCG receives the FIXED and other LCAS control bytes simultaneously
owing to incorrect configuration or bit errors on the link.
Handling Procedure
Step 1 Check whether the LCAS enable state and the LCAS parameters are the same at both ends of
the link.
If ...
Then ...
No,
Set the LCAS protocol properly at both ends of the link.
Yes,
Step 2 Check whether the configurations of the local and remote stations are correct. That is, check
whether an VCG of the local station is connected to multiple VCGs of the remote station.
If ...
Then ...
No,
Yes,
Step 3 Check whether a fault such as failure or bit errors occurs on the service link.
If ...
Then ...
Yes,
Rectify the fault.
No,
Step 4 Disable the LCAS protocol at both the stations, and then restart the protocol.
Step 5 Replace the board that reports the LCAS_FOPR alarm.
----End
Related Information
None.
A.2.59 LCAS_FOPT
Issue 02 (2008-6-20)

A-77

A Alarm Reference
Description
The LCAS_FOPT is an alarm indicating that the LCAS protocol in the transmit direction fails.
This alarm is reported if the transmit unit of the LCAS module of a board detects an abnormal
state in which the LCAS might fail to negotiate or cannot negotiate correctly.
Attribute
Alarm Severity
Alarm Type
Major
Processing alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
The Ethernet service is abnormal.
Possible Causes
l
The LCAS protocol configuration is incorrect.
The link is faulty.
Handling Procedure
Step 1 Check whether the LCAS enable state and the LCAS parameters are the same at both ends of
the link.
If ...
Then ...
No,
Set the LCAS protocol properly at both ends of the link.
Yes,
Step 2 Check whether a fault such as failure or bit errors occurs on the service link.
A-78
If ...
Then ...
Yes,
Rectify the fault.
No,

Issue 02 (2008-6-20)

A Alarm Reference
Step 3 Disable the LCAS protocol at both ends of the link, and then restart the protocol.
If ...
Then ...
The LCAS_FOPT alarm disappears after the The fault is rectified, and the alarm handling
is complete.
The LCAS_FOPT alarm persists after the
Step 4 Replace the board that reports the LCAS_FOPT alarm.

----End
Related Information
None.
A.2.60 LCAS_PLCR
Description
The LCAS_PLCR is an alarm indicating that a part of the LCAS bandwidth in the receive
direction is lost. This alarm is reported if a board detects that the number of paths that carry the
overloads in the receive direction of the VCTRUNK with the LCAS enabled is less than the
preset number but is not zero.
Attribute
Alarm Severity
Alarm Type
Minor
Service alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
The available Ethernet service bandwidth is smaller than the configured bandwidth.
Issue 02 (2008-6-20)

A-79

A Alarm Reference
Possible Causes
l
The number of paths or timeslots that are configured for the VCTRUNK at the remote
station is different from that at the local station.
Some paths in the transmit direction of the remote station are faulty.
Some paths in the receive direction of the local station are faulty.
Handling Procedure
Step 1 Check whether the VCTRUNKs at the transmit and the receive directions at the local station are
If ...
Then ...
No,
Yes,
Step 2 Check whether any path alarm exists in the transmit direction of the remote station.
If ...
Then ...
Yes,
Handle the alarms.
No,
Step 3 Replace the board that reports the LCAS_PLCR alarm.

----End
Related Information
None.
A.2.61 LCAS_PLCT
Description
The LCAS_PLCT is an alarm indicating that all the LCAS bandwidth in the transmit direction
is lost. This alarm is reported if a board detects that the number of paths that carry the overloads
in the transmit direction of the VCTRUNK with the LCAS enabled is less than the preset number
but is not zero.
Attribute
Alarm Severity
Alarm Type
Minor
Service alarm
Parameters
A-80

Issue 02 (2008-6-20)

A Alarm Reference
table.
Name
Meaning
Parameter 1
Impact on System
The available Ethernet service bandwidth is smaller than the configured bandwidth.
Possible Causes
l
Some paths in the receive direction of the remote station are faulty.
Some paths in the transmit direction of the local station are faulty.
Handling Procedure
Step 1 Check whether the VCTRUNKs in the transmit direction of the local station and the receive
direction of the remote station are configured with the same number of physical paths and
timeslots.
If ...
Then ...
No,
Yes,
Step 2 Check whether any path alarm exists in the receive direction of the remote station.
If ...
Then ...
Yes,
Handle the alarms.
No,
Step 3 Replace the board that reports the LCAS_PLCT alarm.

----End
Related Information
None.
A.2.62 LCAS_TLCR
Issue 02 (2008-6-20)

A-81

A Alarm Reference
Description
The LCAS_TLCR is an alarm indicating that all the LCAS bandwidth in the receive direction
is lost. This alarm is reported if no path in the receive direction of the VCTRUNK with LCAS
enabled carries the overload but paths are configured to carry the overload.
Attribute
Alarm Severity
Alarm Type
Major
Service alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
The Ethernet service is interrupted.
Possible Causes
l
The paths in the transmit direction of the remote station are faulty.
The paths in the receive direction of the local station are faulty.
Handling Procedure
If ...
Then ...
No,
Yes,
A-82

Issue 02 (2008-6-20)

If ...
Then ...
Yes,
Handle the alarms.
No,
A Alarm Reference
Step 3 Replace the board that reports the LCAS_TLCR alarm.

----End
Related Information
None.
A.2.63 LCAS_TLCT
Description
The LCAS_TLCT is an alarm indicating that all the LCAS bandwidth in the transmit direction
is lost. This alarm is reported if no path in the transmit direction of the VCTRUNK with LCAS
enabled carries the overload but paths are configured to carry the overload.
Attribute
Alarm Severity
Alarm Type
Major
Service alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
The Ethernet service is interrupted.
Possible Causes
Issue 02 (2008-6-20)
The paths in the transmit direction of the remote station are faulty.
A-83

A Alarm Reference
l
The paths in the receive direction of the local station are faulty.
Handling Procedure
If ...
Then ...
No,
Yes,
If ...
Then ...
Yes,
Handle the alarms.
No,
Step 3 Replace the board that reports the LCAS_TLCT alarm.

----End
Related Information
None.
A.2.64 LCS_LIMITED
Description
The LCS_LIMITED is an alarm indicating that the capacity of the services configured for an
NE crosses the limit defined in the license file.
Attribute
Alarm Severity
Alarm Type
Major alarm
Equipment alarm
Parameters
None.
Impact on System
Changing the capacity of the microwave services through an NE does not take effect.
Possible Causes
The capacity of the configured services crosses the limit defined in the license file.
A-84

Issue 02 (2008-6-20)

A Alarm Reference
Handling Procedure
Step 1 Check whether the capacity of the microwave services is changed as required.
If ...
Then ...
Yes,
No,
Delete the unauthorized microwave cross-connections.
Step 2 Check whether the service capacity defined in the license file of the NE is in agreement with the
latest authorization terms.
If ... Then ...
No,
Contact the technical support engineers of Huawei to obtain the latest license file.
Step 3 Contact the local Huawei office to apply for the authorization of greater service capability.
----End
Related Information
The microwave service capacity of an NE is calculated based on the cross-connections on the
IF board.
A.2.65 LICENSE_LOST
Description
The LICENSE_LOST is an alarm indicating that the license file is not detected.
Attribute
Alarm Severity
Alarm Type
Major alarm
Equipment alarm
Parameters
None.
Impact on System
If no microwave service is configured, the microwave services with a default capacity of 4xE1
are configured. If microwave services are configured, there is no impact on the system except
that an alarm is reported.
Possible Causes
The license file is lost or not loaded.
Issue 02 (2008-6-20)

A-85

A Alarm Reference
Handling Procedure
Contact the technical support engineers of Huawei to reload the associated license file.
----End
Related Information
IF board.
A.2.66 LICENSE_ERR
Description
The LICENSE_ERR is an alarm indicating that license verification of a NE fails.
Attribute
Alarm Severity
Alarm Type
Major alarm
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1 Indicates the cause of verification failure.

l
0x01: Indicates that the license file is illegal.
0x02: Indicates that the license file is incorrect in file format.
0x03: Indicates that the characteristic segment (signature) verification fails.
0x04: Indicates that the equipment serial number specified in the characteristic
segment does not match the equipment.
0x05: Indicates that the trial usage of the characteristic segment expires.
0x06: Indicates that the characteristic segment is incorrect in format.
0x07: Indicates that the characteristic segment expires.
Impact on System
If no microwave service is configured, the microwave services with a default capacity of 4xE1
are configured. If microwave services are configured, there is no impact on the system except
that an alarm is reported.
A-86

Issue 02 (2008-6-20)

A Alarm Reference
Possible Causes
The verification of the license file fails.
Handling Procedure
Contact the technical support engineers of Huawei to reload the associated license file.
----End
Related Information
IF board.
A.2.67 LINK_ERR
Description
The LINK_ERR is an alarm indicating that the data link fails.
Attribute
Alarm Severity
Alarm Type
Critical alarm
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Indicates the ID of the optical interface. For example, 0x01 indicates that the
alarm is reported by optical interface 1 of the related board.
Parameters 23 Indicate the ID of the path that reports the alarm. 0x00 0x01 indicates that
the alarm is reported by path 1.
Impact on System
The services carried over the path are interrupted.
Possible Causes
Issue 02 (2008-6-20)
The optical fiber connected to the Ethernet optical interface is faulty.
The working modes of the ports at both ends do not match each other.
A-87

A Alarm Reference
l
The equipment at the local end or the remote end is faulty.
Handling Procedure
Step 1 Check whether the optical fiber connected to the Ethernet optical interface is faulty.
If ...
Then ...
Yes,
Replace the optical fiber.
No,
Step 2 Check whether the working modes of the ports at both ends match each other.
If ... Then ...
No,
Adjust the working modes of the ports and ensure that they match each other.

Step 3 Use an optical fiber to conduct a loopback test over the port that reports the alarm.
If ...
Then ...
The alarm disappears,
Replace the Ethernet board at the remote end.
The alarm persists,
Replace the Ethernet board at the local end.
----End
Related Information
None.
A.2.68 LOOP_ALM
Description
The LOOP_ALM is an alarm indicating that a path loopback arises.
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
table.
A-88

Issue 02 (2008-6-20)

A Alarm Reference
Name
Meaning
Parameter 1

Parameter 4
Indicates the type of loopback.

l
0x00: Indicates optical/electrical port inloop.
0x01: Indicates optical/electrical port outloop.
0x02: Indicates path inloop.
0x03: Indicates path outloop.
0x04: Indicates loopback at the user side.
0x05: Indicates loopback at the combination wave side.
0x06: Indicates SPI inloop.
0x07: Indicates SPI outloop.
0x08: Indicates ATM layer inloop.
0x09: Indicates ATM layer outloop.
0x0A: Indicates PHY layer inloop.
0x0B: Indicates PHY layer outloop.
0x0C: Indicates MAC layer inloop.
0x0D: Indicates MAC layer outloop.
0x0E: Indicates VC-4 timeslot inloop.
0x0F: Indicates VC-4 timeslot outloop.
0x10: Indicates VC-3 timeslot inloop.
0x11: Indicates VC-3 timeslot outloop.
0x12: Indicates VC-12 timeslot inloop.
0x13: Indicates VC-12 timeslot outloop.
0x14: Indicates IF outloop.
0x15: Indicates IF inloop.
0x16: Indicates RF inloop.
0xFF: Indicates one of the above loopback modes.
Impact on System
The loopback port or path fails to carry services.
Possible Causes
Loopback is performed at the local station.
Issue 02 (2008-6-20)

A-89

A Alarm Reference
Handling Procedure
Step 1 Based on the alarm parameters, determine the type of loopback.
Step 2 Find out the cause of loopback, and cancel the loopback.
----End
Related Information
None.
A.2.69 LPS_UNI_BI_M
Description
The LPS_UNI_BI_M is an alarm indicating that switching modes (single-ended or dual-ended)
at both ends of the linear MSP do not match each other.
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
table.
Name
Meaning
Impact on System
The system performs protection switching in single-ended mode.
Possible Causes
The LPS_UNI_BI_M alarm is generated only when the following conditions are met:
A-90
The switching modes at the local and remote stations are different.
The last three bits of the K2 byte are set to the indicated mode.
The type of the protocol is set to the restructure protocol.

Issue 02 (2008-6-20)

A Alarm Reference
Handling Procedure
Change the MSP switching modes at both ends, and ensure that they are the same.
----End
Related Information
None.
A.2.70 LP_CROSSTR
Description
The LP_CROSSTR is an alarm indicating that a lower order path performance indicator crosses
the related threshold. This alarm is reported if a board detects that a lower order path bit error
performance indicator crosses the preset threshold.
Attribute
Alarm Severity
Alarm Type
Minor
Service alarm
Parameters
table.
Name
Meaning
Parameter 1

Parameter 45
The two most significant bits of Parameter 4 indicate the performance

monitoring period. When the value of the two most significant bits is "01",
the monitoring period is 15 minutes. When the value of the two most
significant bits is "02", the monitoring period is 24 hours.

indicate the performance event ID.
Impact on System
The services contain a large amount of bit errors and the services may be interrupted.
Possible Causes
Lower order path bit error performance events exceed the preset threshold.
Issue 02 (2008-6-20)

A-91

A Alarm Reference
Handling Procedure
Step 1 Check the threshold crossing records of lower order path bit error performance events to
----End
Related Information
None.
A.2.71 LP_R_FIFO
Description
The LP_R_FIFO is an alarm indicating that the FIFO overflows on the receive side of a lower
order path.
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
Bit errors occur to the services.
Possible Causes
A-92
The clock at the local station and that at the remote station are asynchronous.
Issue 02 (2008-6-20)

A Alarm Reference
Handling Procedure
Step 1 Check whether there are TU pointer adjustment performance events at the local and remote
stations.
If ...
Then ...
Yes,
Handle the performance events.
No,

----End
Related Information
None.
A.2.72 LP_RDI
Description
The LP_RDI is an alarm indicating that the remote end fails to receive signals over the lowerorder path. This alarm is reported if the board detects that bit 8 of the V5 byte (indicating E1
interface board) is 1 or bit 5 of the G1 byte (indicating E3/T3 interface board) is 1.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
The local station is not affected, but the service reception at the remote station is interrupted.
Issue 02 (2008-6-20)

A-93

A Alarm Reference
Possible Causes
The local station receives a message from the remote station, and the message says that signal
reception in the lower-order path fails.
Handling Procedure
Handle the alarm about the lower order path of the remote station.
----End
Related Information
None.
A.2.73 LP_RDI_VC12
Description
The LP_RDI_VC12 is an alarm indicating that data reception fails at the remote end of VC-12
lower order path. This alarm is reported if a board detects that bit 8 of the V5 byte is "1".
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Parameters 23 Indicate the ID of the VC-12 path that reports the alarm. For example, 0x00
0x01 indicates that the alarm is reported by VC-12 path 1.
Impact on System
The local station is not affected. Data reception at the remote station, however, is interrupted.
Possible Causes
The local station receives a message from the remote station, and the message says that data
reception fails at the remote end of a lower order path.
A-94

Issue 02 (2008-6-20)

A Alarm Reference
Handling Procedure
Handle the fault occurred to the remote station.
----End
Related Information
None.
A.2.74 LP_RDI_VC3
Description
The LP_RDI_VC3 is an alarm indicating that data reception at the remote end of a VC-3 lower
order path fails. This alarm is reported if a board detects that bit 5 of the G1 byte is "1".
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
Possible Causes
reception fails at the remote end of a lower order path.
Handling Procedure
Handle the fault occurred to the remote station.
----End
Issue 02 (2008-6-20)

A-95

A Alarm Reference
Related Information
None.
A.2.75 LP_REI
Description
The LP_REI is an alarm indicating that there are bit errors over the lower order path of the remote
station. This alarm is reported if the board detects that bit 3 of the V5 (indicating E1 interface
board) byte is 1 or bits 14 of the G1 byte (indicating E3/T3 interface board) are 18.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
The local station is not affected, but there are bit errors in the received signals of the remote
station.
Possible Causes
The local station receives a message from the remote station, and the message says that there
are bit errors in the lower order path of the remote station.
Handling Procedure
Handle the LP_BBE performance event of the remote station.
----End
Related Information
None.
A-96

Issue 02 (2008-6-20)

A Alarm Reference
A.2.76 LP_REI_VC12
Description
The LP_REI_VC12 is an alarm indicating that there are bit errors at the remote end of a VC-12
lower order path. This alarm is reported if a board detects that bit 3 of the V5 byte is "1".
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
The local station is not affected. The remote station, however, has bit errors in the received data.
Possible Causes
are bit errors in the lower order path.
Handling Procedure
Handle the LP_BBE performance event of the remote station.
----End
Related Information
None.
A.2.77 LP_REI_VC3
Issue 02 (2008-6-20)

A-97

A Alarm Reference
Description
The LP_REI_VC3 is an alarm indicating that there are bit errors at the remote end of a VC-3
lower order path. This alarm is reported if a board detects that a bit of bits 14 of the G1 byte is
"1".
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
Bit errors exist in the service in the receive direction of the remote station.
Possible Causes
are bit errors at the remote end of a lower order path.
Handling Procedure
Handle the VC3BBE performance event.
----End
Related Information
None.
A.2.78 LP_RFI
Description
The LP_RFI is an alarm indicating that the remote end of the lower order path fails. This alarm
is reported if a board detects that bit 4 of the V5 byte is "1".
A-98

Issue 02 (2008-6-20)

A Alarm Reference
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
The local station is not affected. The remote station, however, has bit errors in the received data.
Possible Causes
The local station receives a message from the remote station, and the message says that the
remote end of the lower order path fails.
Handling Procedure
Clear the alarm in the lower order path of the remote station.
----End
Related Information
None.
A.2.79 LP_SIZE_ERR
Description
The LP_SIZE_ERR is an alarm indicating that the TU structure is wrong.
Attribute
Issue 02 (2008-6-20)
Alarm Severity
Alarm Type
Minor
Service alarm
A-99

A Alarm Reference
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
The services on the board are interrupted.
Possible Causes
l
The configuration of the mapping structure is incorrect.
The tributary board is faulty.
Handling Procedure
Step 1 Check whether the types of the add/drop services configured are consistent with the service types
that the board supports.
If ...
Then ...
The service types are inconsistent,
Modify the configuration data.
The service types are consistent,

----End
Related Information
None.
A.2.80 LP_SLM
Description
The LP_SLM is an alarm indicating that a mismatched signal label is detected in the lower order
path. This alarm is reported if the board detects a signal label mismatch between the V5 bytes
(indicating E1 interface board) or the C2 bytes (indicating E3/T3 interface board) of both ends.
A-100

Issue 02 (2008-6-20)

A Alarm Reference
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
The services in the lower order path are unavailable.
Possible Causes
The signal label contained in the V5 byte or C2 byte that is received by the local station does
not match that transmitted by the remote station.
Handling Procedure
Modify the signal label contained in the V5 byte or C2 byte at the local station or the remote
station and ensure that the signal labels at both ends match each other.
----End
Related Information
None.
A.2.81 LP_SLM_VC12
Description
The LP_SLM_VC12 is an alarm indicating that a mismatched signal label is detected in a VC-12
lower order path. This alarm is reported if a board detects a mismatched signal label in the V5
byte.
Issue 02 (2008-6-20)

A-101

A Alarm Reference
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
0x01 indicates that the alarm is reported by the first VC-12 path.
Impact on System
The service in this lower order path is unavailable.
Possible Causes
The signal label in the V5 byte to be received at the local station is different from that transmitted
from the remote station.
Handling Procedure
Modify the signal label in V5 byte to be received at the local station in consistent with that
transmitted from the remote station.
----End
Related Information
None.
A.2.82 LP_SLM_VC3
Description
The LP_SLM_VC3 is an alarm indicating that a mismatched signal label is detected in a VC-3
path. This alarm is reported if a board detects a mismatched signal label in the C2 byte.
A-102

Issue 02 (2008-6-20)

A Alarm Reference
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
The service in this lower order path is unavailable.
Possible Causes
The signal label in the C2 byte to be received at the local station is different from that at the
remote station.
Handling Procedure
Modify the signal label to be received at the local station inconsistent with that transmitted from
the remote station.
----End
Related Information
None.
A.2.83 LP_T_FIFO
Description
The LP_T_FIFO is an alarm indicating that the FIFO overflows on the transmission side of the
lower order path.
Issue 02 (2008-6-20)

A-103

A Alarm Reference
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
Possible Causes
l
The frequency offset of the input signal is too large.
Handling Procedure
Step 1 Test the frequency offset of the input signal.
If ...
Then ...
The frequency offset is too large,
Troubleshoot the remote station.
The frequency offset meets the requirement,

----End
Related Information
None.
A.2.84 LP_TIM
A-104

Issue 02 (2008-6-20)

A Alarm Reference
Description
The LP_TIM is an alarm indicating a mismatched lower-order path trace identifier is received.
This alarm is reported if the board detects a mismatch between the J1 bytes (indicating E3/T3
interface board) or the J2 bytes (indicating E1 interface board) of both ends.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
None.
Possible Causes
l
The J1 or J2 byte to be received by the local station does not match that transmitted by the
remote station..
Handling Procedure
Step 1 Set the byte mode of the J1/J2 byte to be received by the local station to the disable mode.
Alternatively, you can set the byte mode in consistent with the J1/J2 byte transmitted by the
remote station.
----End
Related Information
None.
A.2.85 LP_TIM_VC12
Issue 02 (2008-6-20)

A-105

A Alarm Reference
Description
The LP_TIM_VC12 is an alarm indicating that a mismatched VC-12 lower path trace identifier
is detected. This alarm is reported if a board detects a mismatched J2 byte in a VC-12 path.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
None.
Possible Causes
l
the remote station.
Handling Procedure
Step 1 Set the J2 byte to be received at the local station to disabled or to be the same as the J2 byte
----End
Related Information
None.
A.2.86 LP_TIM_VC3
A-106

Issue 02 (2008-6-20)

A Alarm Reference
Description
The LP_TIM_VC3 is an alarm indicating that a mismatched VC-3 lower path trace identifier is
detected. This alarm is reported if a board detects a mismatched J1 byte in a VC-3 path.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
None.
Possible Causes
l
the remote station.
Handling Procedure
Step 1 Set the J1 byte to be received at the local station to disabled or to be the same as the J1 byte
----End
Related Information
None.
A.2.87 LP_UNEQ
Issue 02 (2008-6-20)

A-107

A Alarm Reference
Description
The LP_UNEQ is an alarm indicating that the lower order path is unequipped. This alarm is
reported if a board detects that the V5 byte signal label is "0".
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
The service in this path is unavailable.
Possible Causes
The tributary path of the local station is configured with services, but that of the remote station
is not.
Handling Procedure
Configure tributary services for the remote station.
----End
Related Information
None.
A.2.88 LP_UNEQ_VC12
Description
The LP_UNEQ_VC12 is an alarm indicating that the VC-12 lower order path is unequipped.
This alarm is reported if a board detects that the signal label in the V5 byte is "0".
A-108

Issue 02 (2008-6-20)

A Alarm Reference
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
The service in the path is unavailable. If the service is configured with protection, protection
Possible Causes
Data configuration has the following errors:
l
The tributary path at the local station is configured with services but the corresponding
tributary path at the remote station is not configured with services.
The cross-connection configurations are incorrect at intermediate NEs.
Handling Procedure
Step 1 Check whether the corresponding tributary path is configured with services at the remote station.
If ...
Then ...
No,
Correctly configure the services.
Yes,
Step 2 Check whether the cross-connection configurations at intermediate NEs are correct. If not,
correct the configurations.
----End
Related Information
None.
A.2.89 LP_UNEQ_VC3
Issue 02 (2008-6-20)

A-109

A Alarm Reference
Description
The LP_UNEQ_VC3 is an alarm indicating that the VC-3 lower order path is unequipped. This
alarm is reported if a board detects that the signal label in the C2 byte is "0".
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
The service in this path is unavailable. If the service is configured with protection, protection
Possible Causes
Data configuration has the following errors:
l
The tributary path at the local station is configured with services but the corresponding
tributary path at the remote station is not configured with services.
The cross-connection configurations are incorrect at intermediate NEs.
Handling Procedure
Step 1 Check whether the corresponding tributary path is configured with services at the remote station.
If ...
Then ...
No,
Correctly configure the services.
Yes,
Step 2 Check whether the cross-connection configurations at intermediate NEs are correct. If not,
correct the configurations.
----End
A-110

Issue 02 (2008-6-20)

A Alarm Reference
Related Information
None.
A.2.90 LSR_NO_FITED
Description
The LSR_NO_FITED is an alarm indicating that the laser is not installed.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
table.
Name
Meaning
Impact on System
The optical interface fails to carry services.
Possible Causes
The laser of the local station is not installed.
Handling Procedure
Step 2 Find out why the laser is not installed, and install it promptly.
----End
Related Information
None.
A.2.91 LSR_WILL_DIE
Issue 02 (2008-6-20)

A-111

A Alarm Reference
Description
The LSR_WILL_DIE is an alarm indicating that the service life of the laser will end soon.
Attribute
Alarm Severity
Alarm Type
Critical alarm
Equipment alarm
Parameters
table.
Name
Meaning
Impact on System
The SFP optical module may not function reliably, and thus the services may be interrupted.
Possible Causes
The laser gets aged.
Handling Procedure
Step 2 Contact the technical support engineers of Huawei to replace the SFP optical module with a new
one.
----End
Related Information
None.
A.2.92 LTI
Description
The LTI is an alarm indicating that the synchronization source is lost. This alarm is reported if
all the synchronization sources are lost for the NE.
A-112

Issue 02 (2008-6-20)

A Alarm Reference
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1
0x01: Indicates that all the synchronization sources of the system clock are
lost.
0x02: Indicates that all the synchronization sources of the 2-MHz phaselocked source are lost.
Impact on System
The clock enters the free-run mode and loses synchronization with other NE clocks.
Possible Causes
l
The clock configuration is incorrect.
The clock sources in the clock source priority table fail.
Handling Procedure
Step 1 Check whether the data in the clock source priority table complies with the network planning
requirement.
If ...
Then ...
No,
Correct the configurations.
Yes,
Step 2 Based on the clock source priority table, locate the synchronization source.
Issue 02 (2008-6-20)
If ...
Then ...
The synchronization source is the external

clock,
Check whether the external clock source

and external clock cable are faulty.
The synchronization source is the line clock,
Check whether the line and line board are

faulty.
The synchronization source is the IF clock,
Check whether the microwave link, IF

cable, and IF board are faulty.

A-113

A Alarm Reference
If ...
Then ...
The synchronization source is the tributary

clock,
Check whether the tributary clock source,

relay cable, and tributary board are faulty.
----End
Related Information
None.
A.2.93 MOD_TYPE_MISMATCH
Description
The MOD_TYPE_MISMATCH is an alarm indicating that a mismatched port module is
detected.
Attribute
Alarm Severity
Alarm Type
Critical alarm
Maloperation
Parameters
table.
Name
Meaning
Parameter 1 Indicates the ID of the port that reports the alarm. For example, 0x01 indicates
that the alarm is reported by port 1 of the related board.
Impact on System
The services carried over the port are interrupted.
Possible Causes
The type defined by the customer for the SFP module is different from the actual module type.
Handling Procedure
Step 1 Based on the alarm parameters, locate the port that reports the alarm.
Step 2 Verify the type of the SFP module that connects to the port.
A-114

Issue 02 (2008-6-20)

A Alarm Reference
If ...
Then ...
The type defined for the SFP module is

correct,

Huawei to replace the SFP module with an
appropriate one.
The type defined for the SFP module is

wrong,
Step 3 Define a correct type for the SFP module.

----End
Related Information
None.
A.2.94 MS_AIS
Description
The MS_AIS is an alarm indicating multiplex section alarms. This alarm is reported if a board
detects that bit 6 to bit 8 of the K2 byte in three consecutive frames are "111".
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
The services on the line port are interrupted. If the services are configured with protection,
protection switching may be triggered.
Possible Causes
l
Issue 02 (2008-6-20)

A-115

A Alarm Reference
l
Handling Procedure
If ...
Then ...

replaced,

is complete.

replaced,
If ...
Then ...

replaced,

is complete.

replaced,

----End
Related Information
None.
A.2.95 MS_CROSSTR
Description
The MS_CROSSTR is an alarm indicating that a performance indicator of the multiplex section
crosses the threshold. This alarm is reported if a board detects that the multiplex section bit error
performance indicator crosses the preset threshold.
Attribute
Alarm Severity
Alarm Type
Minor
Service alarm
Parameters
table.
A-116

Issue 02 (2008-6-20)

A Alarm Reference
Name
Meaning
Parameter 1

Parameters 45
The two most significant bits of the parameter 4 indicates the performance
monitoring period ("01" means that the monitoring period is 15 minutes,
and "02" means that the monitoring period is 24 hours).
The parameter 5 and the six least significant bits of the parameter 4 together
Impact on System
Possible Causes
The multiplex section bit error performance indicator crosses the preset threshold.
Handling Procedure
Step 1 Check the threshold crossing records of multiplex section bit error performance events to
----End
Related Information
None.
A.2.96 MS_RDI
Description
The MS_RDI is an alarm indicating that data reception fails at the remote end of the multiplex
section. This alarm is reported if a board detects that bit 6 to bit 8 of the K2 byte are "110".
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
Issue 02 (2008-6-20)

A-117

A Alarm Reference
table.
Name
Meaning
Parameter 1
Impact on System
Possible Causes
reception fails at the remote end of the multiplex section.
Handling Procedure
Step 2 Rectify the fault occurred to the remote station.
----End
Related Information
None.
A.2.97 MS_REI
Description
The MS_REI is an alarm indicating that there are errors at the remote end of the multiplex section.
This alarm is reported if a board detects that the M1 byte is non-zero.
Attribute
Alarm Severity
Alarm Type
Warning
Service alarm
Parameters
table.
A-118

Issue 02 (2008-6-20)

A Alarm Reference
Name
Meaning
Parameter 1
Impact on System
The local station is not affected. The services received by the remote station, however, have bit
errors.
Possible Causes
are bit errors at the remote end of the multiplex section.
Handling Procedure
Step 2 Handle the MS_BBE performance event on the port.
----End
Related Information
None.
A.2.98 MSAD_CROSSTR
Description
The MSAD_CROSSTR is an alarm indicating that the adaptation performance indicator of the
multiplex section crosses the threshold. This alarm is reported if board detects that an AU pointer
adaptation performance indicator crosses the preset threshold.
Attribute
Alarm Severity
Alarm Type
Minor
Service alarm
Parameters
table.
Issue 02 (2008-6-20)

A-119

A Alarm Reference
Name
Meaning
Parameter 1

Parameters 45
The two most significant bits of parameter 4 indicates the performance

monitoring period ("01" means that the monitoring period is 15 minutes,
and "02" means that the monitoring period is 24 hours).
Parameter 5 and the six least significant bits of parameter 4 together

Impact on System
Bit errors may occur to the services.
Possible Causes
l
An AU pointer adaptation performance indicator crosses the preset threshold.
Handling Procedure
Step 1 Check the threshold crossing records of the AU pointer adaptation performance events to
----End
Related Information
None.
A.2.99 MSSW_DIFFERENT
Description
The MSSW_DIFFERENT is an alarm indicating that the master and slave software mismatches
each other. This alarm is reported if the NE detects that the master and slave software mismatches
each other.
Attribute
Alarm Severity
Alarm Type
Major
Processing alarm
Parameters
A-120

Issue 02 (2008-6-20)

A Alarm Reference

table.
Name
Meaning
Parameter 1
Indicates the file location.

l
0x01: Indicates the files in the flash.
0x02: Indicates the software that is currently running.
Parameters 23 Indicate the ID of the inconsistent file on the SCC board.

Parameters 45 Indicate the alarm cause.
l
0x04: Indicates that the file versions in the master and slave areas of an
SCC board are inconsistent.
0x08: Indicates that the file versions in the active and standby SCC boards
are inconsistent, or that the files in the corresponding directories of the
active and standby SCC boards have different names.
0x0c: Indicates that the file versions in the master and slave areas of an
SCC board are inconsistent and the file versions on the active and standby
SCC boards are also inconsistent.
Impact on System
If the working software is lost, the backup software fails to take over the running services. If no
NE software exists in the flash, the system is unable to restart upon power-off or resetting.
Possible Causes
Software loading is abnormal.
Handling Procedure
Contact the technical support engineers of Huawei for re-loading the software.
----End
Related Information
None.
A.2.100 MW_FECUNCOR
Description
The MW_FECUNCOR is an alarm indicating that the Reed Solomon (RS) encoding is
uncorrectable.
Issue 02 (2008-6-20)

A-121

A Alarm Reference
Attribute
Alarm Severity
Alarm Type
Minor
Service alarm
Parameters
table.
Name
Meaning
Parameter 1 Indicates the IF port that reports the alarm. For example, 0x01 indicates that the
alarm is reported by port 1 of the related board.
Impact on System
Bit errors occur to the services. If the system is configured with 1+1 FD/SD protection, channel
Possible Causes
l
The microwave link performance degrades.
Handling Procedure
Refer to 4.3 Troubleshooting Microwave Links.
----End
Related Information
None.
A.2.101 MW_LIM
Description
The MW_LIM is an alarm indicating that a mismatched microwave link identifier is detected.
This alarm is reported if a board detects a mismatched LINK ID in the microwave frame
overheads.
A-122

Issue 02 (2008-6-20)

A Alarm Reference
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
table.
Name
Meaning
Impact on System
The microwave link fails to carry services. If the services are configured with SNCP, protection
Possible Causes
l
The LINK ID of the local station mismatches the LINK ID of the remote station.
The receive frequency at the local end is incorrectly configured.
The direction of the antenna is incorrectly configured. As a result, the antenna receives the
microwave from other stations.
The polarization direction of the XPIC is wrong.
Handling Procedure
Step 1 Determine the IF port that reports the alarm according to alarm parameters.
Step 2 Check whether the LINK ID of the local station matches the LINK ID of the remote station.
If ...
Then ...
No,
Yes,
Step 3 Check whether the receive/transmit frequencies at the local end are consistent with those at the
remote end.
If ...
Then ...
No,
Modify the data configurations.
No,
Step 4 Check whether the XPIC configuration is correct if XPIC protection groups are provided.
Issue 02 (2008-6-20)

A-123

A Alarm Reference
If ...
Then ...
No,
Modify the data configurations.
Yes,
Step 5 Adjust the direction of the antenna.

----End
Related Information
None.
A.2.102 MW_LOF
Description
The MW_LOF is an alarm indicating that the Reed Solomon (RS) frame is lost.
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
table.
Name
Meaning
Impact on System
The services are interrupted. If the system is configured with protection, protection switching
may be triggered.
Possible Causes
A-124
The microwave link performance degrades.
The working modes of the IF units at the local and the remote stations are the same.
The working modes of the ODUs at the local and the remote stations are the same.
Issue 02 (2008-6-20)

A Alarm Reference
Handling Procedure
Refer to 4.3 Troubleshooting Microwave Links.
----End
Related Information
None.
A.2.103 MW_RDI
Description
The MW_RDI is an alarm indicating that there are defects at the remote end of the microwave
link. This alarm is reported if an IF board detects an RDI in the microwave frame overheads.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
Name
Meaning
alarm is reported by port 1 of the board.
Impact on System
If the local station is configured with reverse switching and both the active and standby boards
receive the MW_RDI alarm at the same time, the 1+1 switching may be triggered. This alarm
also indicates that service reception at the remote station may be interrupted.
Possible Causes
After detecting a service alarm that is caused by a microwave link fault, the receive station returns
a microwave link fault indication to the transmit station.
Handling Procedure
Handle the microwave alarm occurred to the remote station.
----End
Issue 02 (2008-6-20)

A-125

A Alarm Reference
Related Information
None.
A.2.104 NESF_LOST
Description
The NESF_LOST is an alarm indicating that the NE software is lost. This alarm is reported if
the SCC board detects that the NE software in the flash memory is lost.
Attribute
Alarm Severity
Alarm Type
Critical
Processing alarm
Parameters
table.
Name
Meaning
Parameter 1
Indicates the inspection object.

l
0x01: Indicates an ordinary file.
0x02: Indicates the version file of the running software.
0x03: Indicates a special inspection object.
Parameters 23 Indicate the ID of the inspection object.
Parameter 4
A-126
0x01, 0x03, and 0x05 indicate the scc.fpga, nesoft.hwx, and ne.ini in the
ofs1, respectively.
0x02, 0x04, and 0x06 indicate the scc.fpga, nesoft.hwx, and ne.ini in the
ofs2, respectively.
Indicates the alarm cause.

l
If the first bit is "1", you can infer that the file does not exist.
If the second bit is "1", you can infer that verification of the file fails.
If the third bit is "1", you can infer that the version of the file in the active
area is different from that of the file in the standby area.
If the fourth bit is "2", you can infer that the version of the file in the active
board is different from that of the file in the standby board.

Issue 02 (2008-6-20)

A Alarm Reference
Impact on System
If the NE software does not exist in the master and slave storage areas, an NE cannot be restarted
after it is powered off or reset.
Possible Causes
l
No NE software is loaded after the existing ones are erased.
Loading the NE software is unsuccessful.
The portable flash memory is not in position or is faulty.
Handling Procedure
Step 1 Check whether the alarm is caused by the loading operation.
If ... Then ...
Yes, Contact the technical support engineers of Huawei to re-load the NE software.
No,
Step 2 Re-install or replace the portable flash memory.

----End
Related Information
None.
A.2.105 NESTATE_INSTALL
Description
The NESTATE_INSTALL is an alarm indicating that the NE is in the install state.
Attribute
Alarm Severity
Alarm Type
Critical
Processing alarm
Parameters
None.
Impact on System
The NE fails to work.
Possible Causes
l
Issue 02 (2008-6-20)
The configuration data check fails.

A-127

A Alarm Reference
l
The logical cross-connect board is not configured.
Handling Procedure
Step 1 Through the NMS, check whether the logical cross-connect board is configured.
If ...
Then ...
No,
Configure the cross-connect board through the NMS.
Yes,
Step 2 Download the correct database for the NE.

----End
Related Information
None.
A.2.106 NO_BD_SOFT
Description
The NO_BD_SOFT is an alarm indicating that the board software is missing.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1
Parameters 23
Indicate the type of the lost software.

l
0x01: Indicates board software.
0x02: Indicates the active FPGA.
0x03: Indicates the standby FPGA.
Impact on System
l
A-128
If the board software is lost, the board fails to work normally.

Issue 02 (2008-6-20)

l
A Alarm Reference
If the FPGA is lost, the FPGA has no backup copy.
Possible Causes
Software loading is abnormal.
Handling Procedure
Contact the technical support engineers of Huawei to re-load the software.
----End
Related Information
None.
A.2.107 NP1_MANUAL_STOP
Description
The NP1_MANUAL_STOP is an alarm indicating that the N+1 protection protocol is manually
disabled.
Attribute
Alarm Severity
Alarm Type
Minor alarm
Processing alarm
Parameters
table.
Name
Meaning
Impact on System
The N+1 protection may fail, or the protection switching may fail.
Possible Causes
The N+1 protection protocol is manually disabled.
Issue 02 (2008-6-20)

A-129

A Alarm Reference
Handling Procedure
Enable the N+1 protection protocol.
----End
Related Information
None.
A.2.108 NP1_SW_FAIL
Description
The NP1_SW_FAIL is an alarm indicating that the N+1 protection switching fails.
Attribute
Alarm Severity
Alarm Type
Major alarm
Communication alarm
Parameters
table.
Name
Meaning
Impact on System
The services cannot be switched. If the current paths are not available, the services are
interrupted.
Possible Causes
The N+1 protection switching fails.
Handling Procedure
Step 1 Check whether the parameters of the N+1 protection are correctly configured.
A-130
If ...
Then ...
No,
Configure the parameters correctly.

Issue 02 (2008-6-20)

If ...
Then ...
Yes,
A Alarm Reference
Step 2 Check the networkwide N+1 protection protocol, and then disable and restart the protocol
manually.
If ...
Then ...
The alarm disappears after the protocol is

restarted,

is complete.
The alarm persists after the protocol is

restarted,

Huawei to handle the alarm.
----End
Related Information
None.
A.2.109 NP1_SW_INDI
Description
The NP1_SW_INDI is an alarm indicating that the N+1 protection switching is detected.
Attribute
Alarm Severity
Alarm Type
Major alarm
Communication alarm
Parameters
table.
Name
Meaning
Impact on System
During the switching (not more than 50 ms), the services are interrupted. After the switching is
complete, the services are restored to normal. During the switching, the extra services are
interrupted.
Issue 02 (2008-6-20)

A-131

A Alarm Reference
Possible Causes
The N+1 protection switching is performed.
Handling Procedure
----End
Related Information
None.
A.2.110 OPM_FAIL
Description
The OPM_FAIL is an alarm indicating that the system fails to output optical power.
Attribute
Alarm Severity
Alarm Type
Major alarm
Equipment alarm
Parameters
table.
Name
Meaning
Impact on System
The services carried over the optical interface are interrupted.
Possible Causes
The SFP optical module is faulty.
Handling Procedure
A-132

Issue 02 (2008-6-20)

A Alarm Reference
Step 2 Contact the technical support engineers of Huawei to replace the SFP optical module with an
appropriate one.
----End
Related Information
None.
A.2.111 PORT_MODULE_OFFLINE
Description
The PORT_MODULE_OFFLINE is an alarm indicating that the port is not in position.
Attribute
Alarm Severity
Alarm Type
Major alarm
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1
Indicates the ID of the port that reports the alarm.
Parameters 23
The values are always 0x00 and 0x01, respectively.
Impact on System
The services over the port are interrupted.
Possible Causes
The port is enabled, but the SFP module is not installed.
Handling Procedure
Step 1 Verify whether to access services over the port.
Issue 02 (2008-6-20)
If ...
Then ...
Yes,
No,
Disable the port.

A-133

A Alarm Reference
Step 2 Check whether the SFP module is installed.

If ... Then ...
No,
Contact the technical support engineers of Huawei to install the SFP module.

Step 3 Re-install the SFP module.
If ...
Then ...
The alarm disappears, The fault is rectified, and the alarm handling is complete.
The alarm persists,
Contact the technical support engineers of Huawei to replace the SFP

module with a new one.
----End
Related Information
None.
A.2.112 POWER_ALM
Description
The POWER_ALM is an alarm indicating that the power module is abnormal.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1 Indicates the ID of the power module that reports the alarm. For example, 0x01
indicates that the alarm is reported by the first power module of the board.
Parameter 2
A-134
0x01: Indicates under-voltage.
0x02: Indicates over-voltage.

Issue 02 (2008-6-20)

A Alarm Reference
Impact on System
Power modules of the IDU 620 are configured with protection. If only one power module reports
the POWER_ALM alarm, the system is not affected.
Possible Causes
l
The input power is abnormal.
The power module is abnormal.
Handling Procedure
Step 1 Use a multimeter to test the power voltage supplied to the chassis.
If ...
Then ...
The voltage is out of the range from 38.4 V to 72 V
Clear the alarm.
The voltage is within the range from 38.4 V to 72 V

----End
Related Information
l
For the IDU 620, the two power modules on the two PXC boards make 1+1 backup.
For the IDU 620, the two power modules on the FAN board make 1+1 backup.
A.2.113 POWER_FAIL
Description
The POWER_FAIL is an alarm indicating that the power supply fails. This alarm is reported if
the ODU detects that its power module fails.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Issue 02 (2008-6-20)

A-135

A Alarm Reference
Name
Meaning
Parameter 1 Indicates the ID of the power supply that reports the alarm. For example, 0x01
indicates that the alarm is reported by the first group of power supply of the board.
Parameter 2
Parameter 3
0x01: Indicates that the active power fails.
0x02: Indicates that the standby power fails.
0x01: Indicates over-voltage.
0x02: Indicates under-voltage.
Impact on System
The ODU fails to work normally.
Possible Causes
The ODU is faulty.
Handling Procedure
Replace the ODU that reports the alarm.
----End
Related Information
None.
A.2.114 P_AIS
Description
The P_AIS is an alarm indicating that abnormal signal reception is detected over the PDH
interface. This alarm is reported if the tributary board detects all "1"s in the up signal flow of
the PDH.
Attribute
Alarm Severity
Alarm Type
Major alarm
Communication alarm
Parameters
table.
A-136

Issue 02 (2008-6-20)

A Alarm Reference
Name
Meaning
Parameter 1
Impact on System
The signals transmitted over the PDH interface are not usable.
Possible Causes
l
The PDH equipment at the remote end transmits the AIS signal.
The tributary board at the local end fails to receive signals properly.
Handling Procedure
Step 1 Check whether the equipment at the remote end transmits the AIS signal.
If ...
Then ...
Yes,
Rectify the fault.
No,

----End
Related Information
None.
A.2.115 P_LOS
Description
The P_LOS is an alarm indicating that signals are lost over the PDH interface.
Attribute
Alarm Severity
Alarm Type
Major alarm
Communication alarm
Parameters
table.
Issue 02 (2008-6-20)

A-137

A Alarm Reference
Name
Meaning
Parameter 1
Impact on System
The PDH services are interrupted.
Possible Causes
l
The PDH services are not accessed over the interface.
The equipment at the remote end is faulty.
The trunk cable is faulty.
The board that reports the alarm is faulty.
Handling Procedure
Step 1 Check whether PDH services are accessed over the interface.
If ...
Then ...
No,
Access the PDH services or delete those unnecessary services.
Yes,
Step 2 Check whether the equipment at the remote end is faulty.

If ...
Then ...
Yes,
Rectify the fault.
No,
Step 3 Check whether the trunk cable is faulty.

If ...
Then ...
Yes,
Rectify the fault.
No,

----End
Related Information
None.
A.2.116 PS
A-138

Issue 02 (2008-6-20)

A Alarm Reference
Description
The PS is an alarm indicating that protection switching is performed.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
The services are interrupted during the protection switching (<50 ms) and return to normal after
the switching is complete.
Possible Causes
Protection switching occurs to the services.
Handling Procedure
----End
Related Information
None.
A.2.117 R_F_RST
Description
The R_F_RST is an alarm indicating that the receive FIFO is reset.
Issue 02 (2008-6-20)

A-139

A Alarm Reference
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
Possible Causes
l
Clock synchronization is lost between the local station and the remote station.
Handling Procedure
Step 1 Query whether there are TU pointer adjustment performance events at the local station or the
remote station.
If ...
Then ...
Yes,
Handle the performance events.
No,

----End
Related Information
None.
A.2.118 R_LOC
A-140

Issue 02 (2008-6-20)

A Alarm Reference
Description
The R_LOC is an alarm indicating that clock signal is not detected at the receive side. This alarm
is reported if the line board fails to extract clock signal from the line signal.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
If the system is configured with protection, protection switching may be triggered.
Possible Causes
l
Handling Procedure
Step 2 Perform port inloop at the local end.
If ...
Then ...
The alarm persists,
Replace the IDU.
Issue 02 (2008-6-20)
If ...
Then ...

replaced,

is complete.

A-141

A Alarm Reference
If ...
Then ...

replaced,
If ...
Then ...

replaced,

is complete.

replaced,
----End
Related Information
None.
A.2.119 R_LOF
Description
The R_LOF is an alarm indicating that frames are lost at the receive side. This alarm is reported
if the OOF state lasts for 3 ms.
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
may be triggered.
A-142

Issue 02 (2008-6-20)

A Alarm Reference
Possible Causes
l
Handling Procedure
Step 2 If this alarm is reported by the IF board, check whether there is an MW_FECUNCOR alarm.
If ...
Then ...
Yes,
Handle the MW_FECUNCOR alarm.
No,
Go to Step 4.
Step 3 If this alarm is reported by the optical interface board or STM-1 electrical interface board,
exchange the receive/transmit fiber jumpers or cables at the receive and the transmit ends.
If ...
Then ...
The alarm persists,
The line port of the remote station reports the R_LOF Rectify the fault in fibers/cables.
alarm,
If ...
Then ...

replaced,

is complete.

replaced,
If ...
Then ...

replaced,

is complete.

replaced,

----End
Related Information
None.
A.2.120 R_LOS
Issue 02 (2008-6-20)

A-143

A Alarm Reference
Description
The R_LOS is an alarm indicating that signal is lost at the receive side.
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
may be triggered.
Possible Causes
l
Handling Procedure
Step 2 If this alarm is reported by the IF board, check whether there is an MW_FECUNCOR alarm.
If ...
Then ...
Yes,
Handle the MW_FECUNCOR alarm.
No,
Go to Step 4.
Step 3 If this alarm is reported by the optical interface board or STM-1 electrical interface board,
exchange the receive/transmit fiber jumpers or cables at the receive and the transmit ends.
A-144
If ...
Then ...
The alarm persists,

Issue 02 (2008-6-20)

A Alarm Reference
If ...
Then ...
The line port of the remote station reports the R_LOS

alarm,
Rectify the fault in fibers/cables.
NOTE
This method applies only to the situation where only one end reports the alarm. If both ends reports the
alarm, check whether the transmission distance is too long or the cables are broken.

If ...
Then ...

replaced,

is complete.

replaced,
If ...
Then ...

replaced

is complete.

replaced

----End
Related Information
None.
A.2.121 R_S_ERR
Description
The R_S_ERR is an alarm indicating that the received signal has errors.
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
Issue 02 (2008-6-20)

A-145

A Alarm Reference
table.
Name
Meaning
Parameter 1
Impact on System
Possible Causes
l
Handling Procedure
Step 1 Check whether the tributary board supports the type of the input signal.
If ...
Then ...
No,
Modify the type of the output signal of the remote station.
Yes,
Step 2 Test the frequency offset of the input signal.

If ...
Then ...
The frequency offset of the input signal is too large,
The frequency offset of the input signal meets the

requirement,

----End
Related Information
None.
A.2.122 RADIO_MUTE
Description
The RADIO_MUTE is an alarm indicating that radio transmitter is muted.
A-146

Issue 02 (2008-6-20)

A Alarm Reference
Attribute
Alarm Severity
Alarm Type
Warning
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1
Indicates the RF port that reports the alarm.
Impact on System
The transmitter does not launch services.
Possible Causes
l
The transmitter of the local station is muted.
The data configuration of the ODU is incorrect.
The IF board is faulty, causing abnormal IF output.
Handling Procedure
Step 1 Check whether the transmitter of the ODU is muted.
If ...
Then ...
Yes,
Cancel the muting operation.
No,
Step 2 Check whether there is an CONFIG_NOSUPPORT alarm.

If ...
Then ...
Yes,
Handle the CONFIG_NOSUPPORT alarm.
No,

----End
Related Information
None.
Issue 02 (2008-6-20)

A-147

A Alarm Reference
A.2.123 RADIO_RSL_HIGH
Description
The RADIO_RSL_HIGH is an alarm indicating that the radio receive power is too high. This
alarm is reported if the detected receive power is equal to or higher than the upper threshold of
the ODU (20 dBm).
Attribute
Alarm Severity
Alarm Type
Critical
Service alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
The service transmission is affected. If the system is configured with 1+1 protection, protection
Possible Causes
l
The ODU is faulty.
There is a strong interference source nearby.
Handling Procedure
If ...
Then ...
The alarm disappears after the ODU is

replaced

is complete.
The alarm persists after the ODU is replaced Go to the next step.
Step 2 Remove the nearby strong interference source.
----End
A-148

Issue 02 (2008-6-20)

A Alarm Reference
Related Information
None.
A.2.124 RADIO_RSL_LOW
Description
The RADIO_RSL_LOW is an alarm indicating that the radio receive power is too low. This
alarm is reported if the detected receive power is equal to or below the lower threshold of the
ODU (90 dBm).
Attribute
Alarm Severity
Alarm Type
Critical
Service alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
If there is neither the MW_LOF nor the MW_FECUNCOR alarm, the services are not affected.
Possible Causes
l
The microwave link signal is too much attenuated.
The transmit power of the remote station is too low.
The ODU of the local station is faulty.
Handling Procedure
Step 1 Check whether the transmit power of the remote station is normal.
If ...
Then ...
No,
Yes,
Replace the ODU of the remote station.
Step 2 Check whether the alarm occurs frequently.

Issue 02 (2008-6-20)

A-149

A Alarm Reference
If ...
Then ...
The alarm occurs occasionally, Contact the network planning department to change the
design to increase the anti-fading performance.
The alarm occurs frequently,
Step 3 Check whether the antennas at both ends are properly adjusted.
If ...
Then ...
No,
Adjust the antenna again.
Yes,
Step 4 Check whether the polarization direction of the antenna, ODU, and hybrid coupler is correctly
set.
If ...
Then ...
No,
Correct the polarization direction.
Yes,
Step 5 Check whether the outdoor units such as antennas, combiner, ODU, and flexible waveguide are
wet, damp, or damaged.
If ...
Then ...
Yes,
Replace the unit that is wet, damp, or damaged.
No,
Step 6 Check whether the antenna gain at both the transmit and receive sides meets the requirement.
If ...
Then ...
No,
Replace the antenna.
Yes,
Step 7 Check whether there is a mountain or building in the transmit direction.

If ... Then ...
Yes, Contact the network planning department to change the design to avoid mountain or
building interference.
No, Go to the next step.
Step 8 Replace the ODU and combiner at the local end in sequence.
If ...
Then ...
The fault is rectified, and the alarm handling is complete.
The alarm persists,
Step 9 Replace the ODU and combiner at the remote end in sequence.
----End
A-150

Issue 02 (2008-6-20)

A Alarm Reference
Related Information
None.
A.2.125 RADIO_TSL_HIGH
Description
The RADIO_TSL_HIGH is an alarm indicating that the radio transmit power is too high. This
alarm is reported if the detected transmit power is higher than the upper power threshold of the
ODU.
Attribute
Alarm Severity
Alarm Type
Critical
Service alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
Possible Causes
The ODU is faulty.
Handling Procedure
Replace the ODU.
----End
Related Information
None.
A.2.126 RADIO_TSL_LOW
Issue 02 (2008-6-20)

A-151

A Alarm Reference
Description
The RADIO_TSL_LOW is an alarm indicating that the radio transmit power is too low. This
alarm is reported if the detected transmit power is below the lower power threshold of the ODU.
Attribute
Alarm Severity
Alarm Type
Critical
Service alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
Possible Causes
The ODU is faulty.
Handling Procedure
Replace the ODU.
----End
Related Information
None.
A.2.127 RELAY_ALARM
Description
The RELAY_ALARM is an alarm indicating relay errors.
A-152

Issue 02 (2008-6-20)

A Alarm Reference
Attribute
Alarm Severity
Alarm Type
Critical
Environment alarm
Parameters
table.
Name
Meaning
Parameter 1 Indicates the ID of the input alarm. For example, 0x01 indicates that the reported
external alarm is the first input alarm.
Impact on System
None.
Possible Causes
The input alarm signal reports the alarm.
Handling Procedure
Step 1 Based on the alarm parameters, locate the ID of the input alarm.
Step 2 Rectify the fault according to the meaning of the input alarm.
----End
Related Information
None.
A.2.128 RP_LOC
Description
The RP_LOC is an alarm indicating that the receiving phaselock ring clock is lost.
Attribute
Issue 02 (2008-6-20)
Alarm Severity
Alarm Type
Major
Equipment alarm
A-153

A Alarm Reference
Parameters
None.
Impact on System
The services on the board are interrupted.
Possible Causes
Handling Procedure
----End
Related Information
None.
A.2.129 RS_CROSSTR
Description
The RS_CROSSTR is an alarm indicating that a regenerator section performance indicator
crosses the threshold. This alarm is reported if board detects that a regenerator section
performance event crosses the preset threshold.
Attribute
Alarm Severity
Alarm Type
Minor
Service alarm
Parameters
table.
Name
Meaning
Parameter 1

A-154

Issue 02 (2008-6-20)

A Alarm Reference
Name
Meaning
Parameters 45
The two most significant bits of parameter 4 indicates the performance

monitoring period (01 means that the monitoring period is 15 minutes, and
02 means that the monitoring period is 24 hours).
Parameter 5 and the six least significant bits of parameter 4 together

Impact on System
Possible Causes
A regenerator section performance event crosses the preset threshold.
Handling Procedure
Step 1 Check the threshold crossing records of the regenerator section performance events to determine
the performance event that crosses the preset threshold.
----End
Related Information
None.
A.2.130 S1_SYN_CHANGE
Description
The S1_SYN_CHANGE is an alarm indicating that the clock source is switched over in S1 byte
mode.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Issue 02 (2008-6-20)

A-155

A Alarm Reference
Name
Meaning
Parameter 1
0x01: Indicates that the system clock is switched over.
0x02: Indicates that the 2-MHz phase-locked source is switched over.
Impact on System
This alarm has no impact on the system.
Possible Causes
In S1 byte mode, switching occurs to the clock source.
Handling Procedure
Find out the cause of switching, and take appropriate measures.
----End
Related Information
None.
A.2.131 SYN_BAD
Description
The SYN_BAD is an alarm indicating that the synchronization source degrades.
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
None.
Impact on System
The NE clock is unlocked.
Possible Causes
A-156
The synchronization source degrades.
The cross-connect unit is faulty.

Issue 02 (2008-6-20)

A Alarm Reference
Handling Procedure
Step 1 If the traced synchronization source is the external clock, check whether the type of the external
clock configuration is correct.
If ...
Then ...
The configuration is incorrect
The configuration is correct
Step 2 If the traced synchronization source is the external clock, check whether the remote clock source
device is faulty.
If ...
Then ...
Yes,
Rectify the fault.
No,
Step 3 If the traced synchronization source is the external clock, check whether the external clock cable
is normal.
If ...
Then ...
No,
Replace the cable.
Yes,
Perform step 5.
Step 4 If the traced synchronization source is the line clock, replace the cross-connect and timing board
of the upstream NE.
----End
Related Information
None.
A.2.132 SYNC_C_LOS
Description
The SYNC_C_LOS is an alarm indicating that the synchronization source is lost.
Attribute
Alarm Severity
Alarm Type
Warning
Equipment alarm
Parameters
Issue 02 (2008-6-20)

A-157

A Alarm Reference

table.
Name
Meaning
Parameter Two parameters indicate one lost clock source.

l
If the line clock source is lost, the first parameter indicates the slot number of
the clock source, and the second parameter indicates the port number of the
clock source.
If the external clock source is lost, "xf0, 1"indicates the external clock 1, and
"0xf0, 2" indicates the external clock 2.
Impact on System
The NE clock degrades or enters the free-run mode.
Possible Causes
The clock source is lost.
Handling Procedure
Step 1 Based on the alarm parameters, locate the lost clock source.
Step 2 Find out why the clock source is lost, and rectify the fault.
----End
Related Information
None.
A.2.133 T_ALOS
Description
The T_ALOS is an alarm indicating that the 2-Mbit/s analog signal is lost at the specific port.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
table.
A-158

Issue 02 (2008-6-20)

Name
Meaning
Parameter 1
A Alarm Reference
Impact on System
Possible Causes
l
The port does not access the 2 Mbit/s service.
The remote station is faulty.
The trunk cable is faulty.
The board that reports the alarm is faulty.
Handling Procedure
Step 1 Check whether the port that reports the alarm accesses the 2 Mbit/s service.
If ... Then ...
No,
Access the service to the port or delete the unnecessary service configuration.

If ...
Then ...
Yes,
Rectify the fault.
No,
Step 3 Check whether the trunk cable is faulty.

If ...
Then ...
Yes,
Rectify the fault.
No,

----End
Related Information
None.
A.2.134 T_F_RST
Issue 02 (2008-6-20)

A-159

A Alarm Reference
Description
The T_F_RST is an alarm indicating that the transmit FIFO is reset.
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
The service in the PDH path is interrupted.
Possible Causes
l
Handling Procedure
Step 1 Check whether the frequency offset of the input signal is too large.
If ...
Then ...
Yes,
No,

----End
Related Information
None.
A.2.135 T_FIFO_E
A-160

Issue 02 (2008-6-20)

A Alarm Reference
Description
The T_FIFO_E is an alarm indicating that the transmit FIFO overflows.
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
Possible Causes
l
Handling Procedure
Step 1 Check whether the frequency offset of the input signal is too large.
If ...
Then ...
Yes,
No,

----End
Related Information
None.
A.2.136 T_LOC
Issue 02 (2008-6-20)

A-161

A Alarm Reference
Description
The T_LOC is an alarm indicating that the clock signal is lost at the transmit side.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
The services in the AU-4 path are interrupted.
Possible Causes
l
The cross-connect and timing board is faulty.
Handling Procedure
Step 2 Replace the cross-connect and timing board.
If ...
Then ...

replaced,

is complete.

replaced,

----End
A-162

Issue 02 (2008-6-20)

A Alarm Reference
Related Information
None.
A.2.137 T_LOS
Description
The T_LOS is an alarm indicating that the input signal is lost at the transmit side.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
The services in the AU-4 path are interrupted.
Possible Causes
l
The SDH service configuration mismatches the type of the line board.
Handling Procedure
Step 1 Check the SDH service configuration.
Issue 02 (2008-6-20)
If ...
Then ...
The SDH service configuration mismatches

the type of the line board,

is complete.
The SDH service configuration is correct,

A-163

A Alarm Reference

If ...
Then ...

replaced,

is complete.

replaced,

----End
Related Information
None.
A.2.138 TEMP_ALARM
Description
The TEMP_ALARM is an alarm indicating that the temperature crosses the threshold.
Attribute
Alarm Severity
Alarm Type
Minor
Environment alarm
Parameters
table.
Name
Meaning
Parameter 1
0x01: Indicates that the temperature crosses the upper threshold.
0x02: Indicates that the temperature crosses the lower threshold.
Impact on System
The board fails to work normally.
Possible Causes
A-164
The board temperature crosses the threshold.
The temperature detecting circuit is faulty.

Issue 02 (2008-6-20)

A Alarm Reference
Handling Procedure
Step 1 If the alarm is reported by the ODU, install a sunshade to control the temperature.
Step 2 If the alarm is reported by a board of the IDU, check whether the temperature control devices,
such as air-conditioners, operate normally.
If ...
Then ...
No,
Adjust the temperature control devices.
Yes,
Step 3 If the alarm is reported by a board of the IDU and the IDU has air filters, clean the air filters.
Step 4 If the ambient temperature is normal and there is no heat-sinking problem, replace the board that
reports the alarm.
----End
Related Information
None.
A.2.139 TU_AIS
Description
The TU_AIS is an alarm indicating that the TU has errors. This alarm is reported if a board
detects that the TU path is all "1"s.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Issue 02 (2008-6-20)

A-165

A Alarm Reference
Impact on System
The services in the TU path are interrupted. If the services are configured with protection,
Possible Causes
l
The line is faulty.
Handling Procedure
Step 1 Check whether the SDH service data and the network protection data are correct.
If ...
Then ...
No,
Yes,
Step 2 Check whether a line alarm exists in the service trail.

If ...
Then ...
Yes,
No,
Step 3 Perform a loopback operation to locate the faulty station.

If ...
Then ...
The fault lies in a remote station,
Locate the faulty board by replacing boards.
The fault lies in the local station,
Step 4 Replace the line board of the local station.

If ...
Then ...

replaced,

is complete.

replaced,
A-166
If ...
Then ...

replaced,

is complete.

replaced,

Issue 02 (2008-6-20)

A Alarm Reference

----End
Related Information
None.
A.2.140 TU_AIS_VC12
Description
The TU_AIS_VC12 is an alarm indicating a VC-12 TU has errors. This alarm is reported if a
board detects that the TU pointer is "1".
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
The value is always 1.
Impact on System
The services in the VC-12 TU path are interrupted. If the services are configured with protection,
Possible Causes
l
The data configuration is incorrect.
The link is faulty.
A tributary board is faulty.
Handling Procedure
Issue 02 (2008-6-20)

A-167

A Alarm Reference
If ...
Then ...
No,
Yes,

If ...
Then ...
Yes,
Handle the alarm.
No,

If ...
Then ...
Step 4 Replace the line board at the local station.

If ...
Then ...
The TU_AIS_VC12 alarm disappears after the The fault is rectified, and the alarm
board is replaced,
The TU_AIS_VC12 alarm persists after the
board is replaced,
Step 5 Replace the cross-connect and timing board at the local station.
If ...
Then ...
The TU_AIS_VC12 alarm disappears after the The fault is rectified, and the alarm
board is replaced,
board is replaced,
Step 6 Replace the board that reports the TU_AIS_VC12 alarm.

----End
Related Information
None.
A.2.141 TU_AIS_VC3
Description
The TU_AIS_VC3 is an alarm indicating that a VC-3 TU has errors. This alarm is reported if a
board detects that the TU pointer is "1".
A-168

Issue 02 (2008-6-20)

A Alarm Reference
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
The services in the VC-3 TU path are interrupted. If the services are configured with protection,
Possible Causes
l
The link is faulty.
Handling Procedure
If ...
Then ...
No,
Yes,

If ...
Then ...
Yes,
Handle the alarm.
No,

Issue 02 (2008-6-20)

A-169

A Alarm Reference
If ...
Then ...
Step 4 Replace the line board at the local station.

If ...
Then ...
The TU_AIS_VC3 alarm disappears after the The fault is rectified, and the alarm handling
board is replaced,
is complete.
board is replaced,
If ...
Then ...
The TU_AIS_VC3 alarm disappears after the The fault is rectified, and the alarm handling
board is replaced,
is complete.
board is replaced,
Step 6 Replace the board that reports the TU_AIS_VC3 alarm.

----End
Related Information
None.
A.2.142 TU_LOP
Description
The TU_LOP is an alarm indicating that the TU pointer is lost. This alarm is reported if a board
detects that the TU-PTR value of eight consecutive frames is invalid or is NDF revertive.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
table.
A-170

Issue 02 (2008-6-20)

A Alarm Reference
Name
Meaning
Parameter 1
Impact on System
The services on the TU channel are interrupted. If the services are configured with protection,
Possible Causes
l
Handling Procedure
If ...
Then ...

replaced,

is complete.

replaced,

----End
Related Information
None.
A.2.143 TU_LOP_VC12
Description
The TU_LOP is an alarm indicating that the VC-12 TU pointer is lost. This alarm is reported if
a board detects that the VC-12 TU-PTR value of eight consecutive frames is invalid or is NDF
revertive.
Attribute
Issue 02 (2008-6-20)
Alarm Severity
Alarm Type
Major
Communication alarm
A-171

A Alarm Reference
Parameters
table.
Name
Meaning
Parameter 1
The value is always 1.
Impact on System
Possible Causes
l
Handling Procedure
If ...
Then ...
The TU_LOP_VC12 alarm disappears after

the board is replaced,

The TU_LOP_VC12 alarm persists after the

board is replaced,
Step 2 Replace the board that reports the TU_LOP_VC12 alarm.

----End
Related Information
None.
A.2.144 TU_LOP_VC3
Description
The TU_LOP is an alarm indicating that the VC-3 TU pointer is lost. This alarm is reported if
a board detects that the TU-PTR value of eight consecutive frames is invalid or is NDF revertive.
A-172

Issue 02 (2008-6-20)

A Alarm Reference
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
Possible Causes
l
Handling Procedure
If ...
Then ...
The TU_LOP_VC3 alarm disappears after the The fault is rectified, and the alarm
board is replaced,
The TU_LOP_VC3 alarm persists after the
board is replaced,
Step 2 Replace the board that reports the TU_LOP_VC3 alarm.

----End
Related Information
None.
A.2.145 UP_E1_AIS
Issue 02 (2008-6-20)

A-173

A Alarm Reference
Description
The UP_E1_AIS is an alarm indicating that the 2-MHz uplink signal has errors. This alarm is
reported if the tributary board detects that the uplink E1 signal is all "1"s.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
The E1 signals are unavailable.
Possible Causes
l
The remote station sends the AIS signal.
Handling Procedure
Step 1 Check whether the remote station sends the AIS signal.
If ...
Then ...
Yes,
No,

----End
Related Information
None.
A-174

Issue 02 (2008-6-20)

A Alarm Reference
A.2.146 VCAT_LOA
Description
The VCAT_LOA is an alarm indicating that the delay of the virtual concatenation is too long.
This alarm is reported if a board detects that the time delay of the timeslots bound to a VCTRUNK
is out of the permissible limit.
Attribute
Alarm Severity
Alarm Type
Critical
Service alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
The virtually concatenated services are interrupted.
Possible Causes
The differences between VC links are too large.
Handling Procedure
Step 1 Check whether the transmission routes for the paths that are bound to this VCTRUNK are the
same.
If ...
Then ...
No,
Adjust the routes to be the same.
Yes,
Step 2 Check whether bit errors or a line alarm exists. If yes, handle the alarm.
----End
Issue 02 (2008-6-20)

A-175

A Alarm Reference
Related Information
None.
A.2.147 VCAT_LOM_VC12
Description
The VCAT_LOM_VC12 is an alarm indicating that the virtual concatenation multiframe in the
VC-12 path is lost. This alarm is reported if a board detects that the K4 byte of the VC-12 timeslot
mismatches the expected multiframe sequence.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
This path is unavailable. If the LCAS function is disabled, the services are interrupted.
Possible Causes
l
The link configuration is incorrect.
The virtual concatenation delay time varies with each path.
Bit errors exist in the line.
Handling Procedure
Step 1 Check whether the VCTRUNKs at both ends of the path are bound with the same timeslot.
A-176
If ...
Then ...
No,
Yes,

Issue 02 (2008-6-20)

A Alarm Reference
same.
If ...
Then ...
No,
Yes,
Step 3 Check whether any bit errors or line alarm exists. If yes, handle the alarms.
----End
Related Information
None.
A.2.148 VCAT_LOM_VC3
Description
The VCAT_LOM_VC3 is an alarm indicating the virtual concatenation multiframe in the VC-3
path is lost. This alarm is reported if a board detects that the H4 byte of the VC-3 timeslot
mismatches the expected multiframe sequence.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
Possible Causes
l
Issue 02 (2008-6-20)
The link configuration is incorrect.

A-177

A Alarm Reference
l
The virtual concatenation delay is too long.
Handling Procedure
Step 1 Check whether the VCTRUNKs at both ends of the path are bound with the same timeslot.
If ...
Then ...
No,
Yes,
same.
If ...
Then ...
No,
Yes,
Step 3 Check whether bit errors or a line alarm exists. If yes, handle the alarms.
----End
Related Information
None.
A.2.149 VCAT_SQM_VC12
Description
The VCAT_SQM_VC12 is an alarm indicating that a mismatched virtual concatenation
sequence (SQ) is detected in the VC-12 path. This alarm is reported if a board detects that a
mismatched virtual concatenation (SQ).
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
table.
A-178
Name
Meaning
Parameter 1

Issue 02 (2008-6-20)

Name
A Alarm Reference
Meaning
Impact on System
Possible Causes
l
Errors exist on a link or the link is faulty.
The SQ number sent from the remote station is wrong.
Handling Procedure
Step 1 Check whether bit errors or a line alarm exists.
If ...
Then ...
Yes,
Handle the alarm.
No,
Step 2 Replace the board on which the VCAT_SQM_VC12 alarm occurs.

If ...
Then ...
The VCAT_SQM_VC12 alarm disappears after The fault is rectified, and the alarm
The VCAT_SQM_VC12 alarm persists after the Go to the next step.
board is replaced,
Step 3 Replace the corresponding board at the remote station.
If ...
Then ...
The VCAT_SQM_VC12 alarm disappears after The fault is rectified, and the alarm
The VCAT_SQM_VC12 alarm persists after the Contact the technical support engineers
board is replaced,
of Huawei.
----End
Related Information
None.
A.2.150 VCAT_SQM_VC3
Issue 02 (2008-6-20)

A-179

A Alarm Reference
Description
The VCAT_SQM_VC3 is an alarm indicating that a mismatched virtual concatenation SQ is
detected in the VC-3 path. This alarm is reported if a board detects a mismatched virtual
concatenation SQ in the VC-3 path.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Impact on System
The path is unavailable. If the LCAS function is disabled, the services are interrupted.
Possible Causes
l
Bit errors exist on a link or the link is faulty.
The SQ number sent from the remote station is wrong.
Handling Procedure
Step 1 Check whether bit errors or a line alarm exists.
If ...
Then ...
Yes,
Handle the alarm.
No,
Step 2 Replace the board on which the VCAT_SQM_VC3 alarm occurs.
A-180
If ...
Then ...
The VCAT_SQM_VC3 alarm disappears after



Issue 02 (2008-6-20)

A Alarm Reference
If ...
Then ...
The VCAT_SQM_VC3 alarm persists after the Go to the next step.

board is replaced,
Step 3 Replace the corresponding board at the remote station.
If ...
Then ...
The VCAT_SQM_VC3 alarm disappears after

End the alarm handling.
The VCAT_SQM_VC3 alarm persists after the Contact the technical support engineers
board is replaced,
of Huawei.
----End
Related Information
None.
A.2.151 VOLT_LOS
Description
The VOLT_LOS is an alarm indicating that the power is not available.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Issue 02 (2008-6-20)
Name
Meaning
Parameter 1
Indicates the type of the power that reports the alarm.

l
0x01: Indicates 48 V/+24 V power output.
0x02: Indicates 48 V/+24 V power input.
0x03: Indicates +5 V power output.
0x04: Indicates +3.3 V power output.
0x05: Indicates lightning power.

A-181

A Alarm Reference
Impact on System
If the alarm is reported by the PXC board, only one power input is available for the system.
If the alarm is reported by the IF board, the ODU connected to the IF board fails to work.
Possible Causes
l
The input power is abnormal.
The power module is abnormal.
The power switch is turned off.
Handling Procedure
Step 1 Locate the board that reports the alarm, and handle the alarm accordingly.
If ...
Then ...
The IF board reports the alarm,
Go to Step 2.
The PXC board reports the alarm,
Go to Step 3 through Step 5.
Step 2 Check the power switch of the ODU.

If ...
Then ...
The power switch is on,
Replace the IF board.
The power switch is off,
Turn on the power switch.
Step 3 Locate the type of the power supply that reports the alarm, and handle the alarm accordingly.
If ...
Then ...
The alarm is about the input power,
The alarm is about the output power,
The alarm is about the lightning power,
Check the grounding system.
Step 4 Clear the alarm about the input power.

If ...
Then ...
It is normal that there is no input power,
Mask the alarm for the board.
It is abnormal that there is no input power,
Step 5 Check the power switch.

If ...
Then ...
The power switch is on,
Contact the power engineers to rectify the fault.
The power switch is off,
Turn on the power switch.
----End
A-182

Issue 02 (2008-6-20)

A Alarm Reference
Related Information
None.
A.2.152 WRG_BD_TYPE
Description
The WRG_BD_TYPE is an alarm indicating that a board of the wrong type is detected.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1
Indicates the slot where the board is seated.
Impact on System
The board does not work.
Possible Causes
l
The type of the board installed is incorrect.
Handling Procedure
Step 1 Check whether the board type configured complies with the planning requirement.
If ...
Then ...
No,
Yes,
Step 2 Replace the board.

----End
Issue 02 (2008-6-20)

A-183

A Alarm Reference
Related Information
None.
A.2.153 WRG_DEV_TYPE
Description
The WRG_DEV_TYPE is an alarm indicating that a device of the wrong type is detected.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
None.
Impact on System
The equipment does not work.
Possible Causes
Handling Procedure
Modify the type of the equipment to be consistent with the equipment.
----End
Related Information
None.
A.2.154 WS_LOS
Description
The WS_LOS is an alarm indicating that the wayside interface signal is lost.
Attribute
A-184
Alarm Severity
Alarm Type
Major
Communication alarm
Issue 02 (2008-6-20)

A Alarm Reference
Parameters
table.
Name
Meaning
Parameter 1
Indicates the wayside service where the alarm occurs.
Impact on System
The wayside services are interrupted.
Possible Causes
l
Wayside service data has been configured, but the services are not accessed.
The remote station is faulty.
The wayside cables are faulty.
The PXC board is faulty.
Handling Procedure
Step 1 Check whether wayside service data is configured but the services are not accessed.
If ...
Then ...
Yes,
Access the services and delete the unnecessary wayside service data.
No,

If ...
Then ...
Yes,
Rectify the fault.
No,
Step 3 Check whether the wayside service cable is faulty.

If ...
Then ...
Yes,
Rectify the fault.
No,

----End
Related Information
None.
Issue 02 (2008-6-20)

A-185

A Alarm Reference
A.2.155 W_R_Failure
Description
The W_R_Failure is an alarm indicating that reading and writing the chip register fail.
Attribute
Alarm Severity
Alarm Type
Major alarm
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1
Indicates the ID of the register.
Parameters 23
The values are always 0x00 and 0x01, respectively.
Impact on System
The services carried in the path are interrupted.
Possible Causes
l
The chip register fails.
The read/write time sequence is wrong.
Handling Procedure
----End
Related Information
None.
A.2.156 XCP_INDI
Description
The XCP_INDI is an alarm indicating that the active and standby PXC boards are switched over.
A-186

Issue 02 (2008-6-20)

A Alarm Reference
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1
Indicates the slot where the working board is seated.
Impact on System
During the protection switching (< 50 ms), VC-3/VC-12 services are interrupted.
Possible Causes
Protection switching occurs to the PXC board.
Handling Procedure
Determine the cause of switching, and take appropriate measures.
----End
Related Information
None.
A.2.157 XPIC_LOS
Description
The XPIC_LOS is an alarm indicating that the XPIC compensation signals are lost.
Attribute
Alarm Severity
Alarm Type
Critical alarm
Equipment alarm
Parameters
Issue 02 (2008-6-20)

A-187

A Alarm Reference

table.
Name
Meaning
Impact on System
Bit errors arise, and the services carried over the port may be interrupted.
Possible Causes
l
The related data is incorrectly configured.
The XPIC signal cable is faulty.
The IF board is faulty.
The ODU connected to the IF board is faulty.
Handling Procedure
Step 1 Verify whether to enable the XPIC function.
If ...
Then ...
Yes,
No
Modify the configuration, and disable the XPIC function.
Step 2 Check whether the XPIC signal cable is properly connected.

If ...
Then ...
Yes,
No,
Rectify the fault.
Step 3 Replace the remote IF board connected to the XPIC signal cable.
If ...
Then ...
The alarm disappears after the IF board is The fault is rectified, and the alarm handling
replaced,
is complete.
The alarm persists after the IF board is
replaced,
Replace the ODU connected to the IF cable.
----End
Related Information
None.
A-188

Issue 02 (2008-6-20)

B Performance Event Reference
Performance Event Reference
B.1 Performance Event List

The list is categorized based on the performance event type, and includes all the events of the
OptiX RTN 600.
B.1.1 SDH /PDH Performance Event List

SDH performance events are classified into five categories: pointer justification, regenerator
section error, multiplex section error, higher order path error and lower order path error.
Table B-1 Pointer justification performance event list
Event Name
Description
Source
AUPJCHIGH
Count of positive AU pointer justification
AUPJCLOW
Count of negative AU pointer justification
AUPJCNEW
Count of new AU pointer justifications
SL1, SD1, SLE,

SDE,SL4.
IF1A, and IF1B
and IFX
TUPJCHIGH
Count of positive TU pointer justifications
TUPJCLOW
Count of negative TU pointer justifications
TUPJCNEW
Count of new TU pointer justifications
PO1 PH1,PD1
and PL3
Table B-2 Regenerator section error performance event list
Issue 02 (2008-6-20)
Event Name
Description
Source
RSBBE
Regenerator section block of background error
RSES
Regenerator section errored second
RSSES
Regenerator section severely errored second
SL1, SD1, SLE,

SDE, IF1A,
IF1B,IFX and
SL4

B-1

Event Name
Description
RSUAS
Regenerator section unavailable second
RSCSES
Regenerator section consecutive severely errored

second
RSOFS
Regenerator section out-of-frame second
RSOOF
Regenerator section out of frame
Source
Table B-3 Multiplex section error performance event list

Event Name
Description
Source
MSBBE
Multiplex section block of background error
MSES
Multiplex section errored second
MSSES
Multiplex section severely errored second
SL1, SD1, SLE,

SDE, IF1A,
IF1B,IFX and
SL4
MSCSES
Multiplex section consecutive severely errored second
MSUAS
Multiplex section unavailable second
MSFEBBE
Multiplex section far end block of background error
MSFEES
Multiplex section far end errored second
MSFESES
Multiplex section far end severely errored second
MSFECSES
Multiplex section far end consecutive severely errored

second
MSFEUAS
Multiplex section far end unavailable second
Table B-4 Higher order path error performance event list
B-2
Event Name
Description
Source
HPBBE
Higher order path block of background error
HPES
Higher order path errored second
HPSES
Higher order path severely errored second
SL1, SD1, SLE,

SDE, IF1A,
IF1B,IFX and
SL4
HPCSES
Higher order path consecutive severely errored second
HPUAS
Higher order path unavailable second
HPFEBBE
Higher order path far end block of background error
HPFEES
Higher order path far end errored second
HPFESES
Higher order path far end severely errored second

Issue 02 (2008-6-20)

Event Name
Description
Source
HPFECSES
Higher order path far end consecutive severely errored

second
HPFEUAS
Higher order path far end unavailable second
Table B-5 VC-3 path bit error performance event list

Event Name
Description
Source
VC3BBE
VC-3 background block error
EFT4,EMS6
VC3ES
VC-3 errored second
VC3SES
VC-3 severely errored

second
VC3CSES
VC-3 consecutive severely

errored second
VC3UAS
VC-3 unavailable second
VC3FEBBE
VC-3 far end block of the

background error
VC3FEES
VC-3 far end errored second
VC3FESES
VC-3 far end severely

errored second
VC3FECSES
VC-3 far end consecutive

severely errored second
VC3FEUAS
VC-3 far end unavailable

second
Table B-6 Lower order path error performance event list
Issue 02 (2008-6-20)
Event Name
Description
Source
LPBBE
Lower order path block of background error
LPES
Lower order path errored second
LPSES
Lower order path severely errored second
PO1,
PH1,PD1,PL3,
EFT4,EMS6,IF
0A and IF0B
LPCSES
Lower order path consecutive severely errored second
LPUAS
Lower order path unavailable second
LPFEBBE
Lower order path far end block of background error
LPFEES
Lower order path far end errored second

B-3

Event Name
Description
Source
LPFESES
Lower order far end severely errored second
LPFECSES
Lower order path far end consecutive severely errored

second
LPFEUAS
Lower order far end unavailable second
Table B-7 Line side code violation performance event list

Event Name
Description
Source
E3_LCV_SDH
E3 line side code violations
PL3
E3_LES_SDH
E3 line side code violation

errored second
E3_LSES_SDH
E3 line side code violation

T3_LCV_SDH
T3 line side code violations
T3_LES_SDH
T3 line side code violation

errored second
T3_LSES_SDH
T3 line side code violation

B.1.2 Microwave Performance Events

The microwave performance events are performance events of the microwave power and the
FEC.
Table B-8 Microwave power performance events
B-4
Event Name
Description
Source
TSL_MAX
Maximum value of microwave transmit signal level
ODU
TSL_MIN
Minimum value of microwave transmit signal level
TSL_CUR
Current value of microwave transmit signal level
RSL_MAX
Maximum value of microwave receive signal level
RSL_MIN
Minimum value of microwave receive signal level
RSL_CUR
Current value of microwave receive signal level

Issue 02 (2008-6-20)

Table B-9 FEC performance events

Event Name
Description
Source
FEC_BEF_COR_ER
Bit error rate before FEC correction
FEC_COR_BYTE_CNT
FEC corrected byte count
IF1A, IF1B,
IF0A, IF0B, and
IFX
B.1.3 Other Performance Events

Besides the SDH and microwave performance events, the OptiX RTN 600 also supports
performance events of the optical power and the temperature.
Table B-10 Optical power performance events
Event Name
Description
Source
TPLMAX
Maximum value of transmit optical power
TPLMIN
Minimum value of transmit optical power
SD1, SL1, SL4

and EMS6
TPLCUR
Current value of receive optical power
RPLMAX
Maximum value of received optical power
RPLMIN
Minimum value of received optical power
RPLCUR
Current value of received optical power
Table B-11 Board temperature performance events

Event Name
Description
Source
BDTMPMAX
Maximum board temperature
BDTMPMIN
Minimum board temperature
BDTMPCUR
Current board temperature
CIF1A,
IF1B,IF0A,IF0
B, PXC, EFT4,
ODU, EMS6,
and SCC
Table B-12 Laser core temperature performance events
Issue 02 (2008-6-20)
Event Name
Description
Source
OSPITMPMAX
Maximum temperature of the

laser core
EMS6
OSPITMPMIN
Minimum temperature of the

laser core

B-5

Event Name
Description
Source
OSPITMPCUR
Current temperature of the

laser core
B.2 Performance Events and Corrective Procedures

Based on the event type, this part describes all the performance events of the OptiX RTN 600
and the corrective procedures in details.
B.2.1 AUPJCHIGH, AUPJCLOW, and AUPJCNEW

Meanings of Performance Events
l
AUPJCHIGH stands for "positive AU pointer justifications".
AUPJCLOW stands for "negative AU pointer justifications".
AUPJCNEW stands for "new AU pointer justifications".
Attributes of Performance Events

Attribute
Description
Performance event cell
PPJE(AUPJCHIGH)
NPJE(AUPJCLOW)
NDF(AUPJCNEW)
Unit
Block
Impact on the System

Less than six AUPJCHIGH and AUPJCLOW events have no impact on the system. If the pointer
is justified for more than six times, or the AUPJCNEW events occur, bit errors may be
introduced.
Relevant Alarms
When the AUPJCHIGH, AUPJCLOW, and AUPJCNEW events cross the preset thresholds, the
MSAD_CROSSTR alarm may be generated.
B-6
Performance Event
Default 15-Minute
Threshold
Default 24-Hour
Threshold
AUPJCHIGH
1500
30000
AUPJCLOW
1500
30000
AUPJCNEW
1500
30000

Issue 02 (2008-6-20)

Probable Causes
The NE clock is not synchronized.
Procedure
See 4.5 Troubleshooting Pointer Justifications.
----End
B.2.2 TUPJCHIGH, TUPJCLOW, and TUPJCNEW

Performance Event Meaning
l
TUPJCHIGH stands for "Count of positive TU pointer justifications".
TUPJCLOW stands for "Count of negative TU pointer justifications".
TUPJCNEW stands for "Count of new TU pointer justifications".
Performance Event Attribute

Description
TUPPJE(TUPJCHIGH)
TUNPJE(TUPJCLOW)
TUNDF(TUPJCNEW)
Unit
Block

Less than six TUPJCHIGH and TUPJCLOW do not impact the system. If the pointer is justified
for more than six times, or if even the TUPJCNEW exists, bit errors might exist in the service.
Relevant Alarm
When the TUPJCHIGH, TUPJCLOW and TUPJCNEW cross the preset threshold, the
HPAD_CROSSTR alarm occurs.
Issue 02 (2008-6-20)
Performance Event
Default 15-Minute
Threshold
Default 24-Hour
Threshold
TUPJCHIGH
1500
30000
TUPJCLOW
1500
30000
TUPJCNEW
1500
30000

B-7

Probable Causes
The NE clock is not synchronized.
Procedure
Refer to section 4.5 Troubleshooting Pointer Justifications.
----End
B.2.3 RSBBE, RSES, RSSES, RSCSES, and RSUAS

l
RSBBE stands for "regenerator section background block error".

BBES refers to the errored blocks excluding those in the unavailable and severely errored
seconds.
RSES stands for "regenerator section errored second".

The ES is the second with one or more errored blocks.
RSSES stands for "regenerator section severely errored second".

The SES is the second in which more than 30% errored blocks or at least one severely
disturbed period (SDP) exists. The SDP is the period during which the BER of all the
consecutive blocks in a period of less than four consecutive blocks or 1ms (the longer period
is applied) is equal to or higher than 102 or the signal is lost.
RSCSES stands for "regenerator section consecutive severely errored second".

The CSES is the second in which the SES occurs in a consecutive mode and lasts for less
than 10 seconds.
RSUAS stands for "regenerator section unavailable second".

The UAS is a period of unavailable time that begins at the onset of ten CSESs. When SESs
disappear for ten consecutive seconds, the available time begins from the eleventh second,
with the previous ten seconds included.
NOTE
When the intermediate board works in the PDH mode, the performance events might also be reported. These
events are detected through the self-defining overhead byte B1 of the PDH microwave frame.

Attribute
Description
B1CNT
Unit
Block (RSBBE)
Second (RSES, RSSES, RSCSES, and
RSUAS)
B-8

Issue 02 (2008-6-20)


Too many bit errors may interrupt the service (the bit error rate should be less than 103 for the
voice service, and 106 for the data service).
Relevant Alarms
When the RSBBE, RSES, RSSES, RSCSES, and RSUAS events cross the preset threshold, the
RS_CROSSTR alarm may be generated.
Performance Event
Default 15-Minute
Threshold
Default 24-Hour
Threshold
RSBBE
1500
15000
RSES
50
100
RSSES
20
50
RSUAS
20
50
RSCSES
4 (number of consecutive SESs)
Probable Causes
The system detects the RSBBE by using the B1 byte.
Procedure
See 4.4 Troubleshooting Bit Errors.
----End
B.2.4 RSOOF and RSOFS

l
RSOOF stands for "Regenerator section out of frame".

The OOF block is the data block in which incorrect A1 and A2 bytes are detected.
RSOFS stands for "regenerator section out-of-frame second".

The OFS second is a second in which one or more OOF blocks are detected.

Description
OOF
Unit
Block (RSOOF)
Second (RSOFS)
Issue 02 (2008-6-20)

B-9


The system discards OOF data blocks. Thus, an RSOOF event is like a big error (one RSOOF
exists in a second, and the BER is not less than 1.25 x 105).
Relevant Alarms
If RSOOF is received in five consecutive frames, the equipment will enter the OOF state. If the
OOF state lasts for 3 ms, the equipment will report the R_LOF alarm. As a result, all the services
are interrupted.
Probable Causes
The system detects that the A1 and A2 bytes are incorrect.
Procedure
If the R_LOF alarms are reported at the same time, process the errors according to the alarms.
Otherwise, refer to section 4.4 Troubleshooting Bit Errors .
----End
B.2.5 MSBBE, MSES, MSSES, MSCSES, and MSUAS

l
MSBBE stands for "multiplex section background block error".

BBE refers to the errored blocks excluding those in the unavailable and severely errored
seconds.
MSES stands for "multiplex section errored second".

ES refers to the second with one or more errored blocks.
MSSES stands for "multiplex section severely errored second".

SES refers to the second in which more than 30% errored blocks or at least one SDP exists.
The SDP refers to the period in which the BER of all the consecutive blocks in a period of
less than four consecutive blocks or 1ms (the longer period is applied) is equal to or higher
than 102 or the signal is lost.
MSCSES stands for "multiplex section consecutive severely errored second".

CSES refers to the second in which the SESs occur in a consecutive mode and lasts for less
than 10 seconds.
MSUAS stands for "multiplex section unavailable second".

UAS refers to the period of unavailable time that begins at the onset of ten CSESs. When
SESs disappear for ten consecutive seconds, the available time begins from the eleventh
second, with the previous ten seconds included.
B-10
Attribute
Description
B2CNT

Issue 02 (2008-6-20)

Attribute
Description
Unit
Block (MSBBE)
Second(MSES, MSSES, MSCSES and
MSUAS)

Too many bit errors can interrupt the service (the BER should be less than 103 for the voice
service, and 106 for the data service).
Relevant Alarms
When the MSBBE, MSES, MSSES, MSCSES, and MSUAS events cross the preset thresholds,
the MS_CROSSTR alarm may be generated.
Performance Event
Default 15-Minute
Threshold
Default 24-Hour
Threshold
MSBBE
1500
15000
MSES
50
100
MSES
20
50
MSUAS
20
50
MSCSES
Probable Causes
The system detects the MSBBE according to the B2 byte.
Procedure
----End
B.2.6 MSFEBBE, MSFEES, MSFESES, MSFECSES, and MSFEUAS

l
MSFEBBE stands for "multiplex section far end background block error".
The FEBBE (far end background block error) indicates that the BBE occurs at the opposite
end.
MSFEES stands for "multiplex section far end errored second".

The FEES ( far end errored second) indicates that the ES occurs at the opposite end.
Issue 02 (2008-6-20)

B-11


l
MSFESES stands for "multiplex section far end severely errored second".
The FESES (far end severely errored second) indicates that the SES occurs at the opposite
end.
MSFECSES stands for "Multiplex section far end consecutive severely errored second".
The FESES (far end consecutive severely errored second) indicates that the CSES occurs
at the opposite end.
MSFEUAS stands for "multiplex section unavailable second".

The FEUAS (far end unavailable second) indicates that the UAS occurs at the opposite end.

Description
LFEBE
Unit
Block (MSFEBBE)
Second(MSFEES, MSFESES, MSFECSES
and MSFEUAS)

Too many bit errors can interrupt the service (the bit error rate needs to be less than 103 for the
Relevant Alarm
The MS_REI alarm occurs at the local end.
Probable Causes
The system detects the MSFEBBE by the M1 byte.
Procedure
Clear the corresponding event at the opposite end.
----End
B.2.7 HPBBE, HPES, HPSES, HPCSES, and HPUAS

l
HPBBE stands for "Higher-order path background block error".

Background block error (BBE) refers to the errored blocks excluding those in the
unavailable and severely errored seconds.
HPES stands for "higher-order path errored second".

Errored second (ES) refers to the second with one or more errored blocks.
B-12
HPSES stands for "higher-order path severely errored second".

Issue 02 (2008-6-20)

Severely errored second (SES) refers the second in which more than 30% errored blocks
or at least one severely disturbed period (SDP) exists. The SDP refers to the period in which
the BER of all the consecutive blocks in a period of less than four consecutive blocks or
1ms (the longer period is applied) is equal to or higher than 102 or the signal is lost.
l
HPCSES stands for "higher-order path consecutive severely errored second".

Consecutive severely errored second (CSES) refers to the second in which the SESs occur
in a consecutive mode and lasts for less than 10 seconds.
HPUAS stands for "higher-order path unavailable second".

Unavailable second (UAS) refers to the period of unavailable time that begins at the onset
of ten CSESs. When SESs disappear for ten consecutive seconds, the available time begins
from the eleventh second, with the previous ten seconds included.

Attribute
Description
B3CNT
Unit
Block (HPBBE)
Second (HPES, HPSES, HPCSES, and
HPUAS)

Too many bit errors may interrupt the service (the BER should be less than 103 for the voice
Relevant Alarms
When the HPBBE, HPES, HPSES, HPCSES, and HPUAS events cross the preset thresholds,
the HP_CROSSTR alarm may be generated.
Performance Event
Default 15-Minute
Threshold
Default 24-Hour
Threshold
HPBBE
1500
15000
HPES
50
100
HPSES
20
50
HPUAS
20
50
HPCSES
Probable Causes
The system detects higher order path bit errors according to the B3 byte.
Issue 02 (2008-6-20)

B-13

Procedure
----End
B.2.8 HPFEBBE, HPFEES, HPFESES, HPFECSES, and HPFEUAS

l
HPFEBBE stands for "higher order path far end background block error".
The far end background block error (FEBBE) refers to the error detected at the remote end.
HPFEES stands for "higher order path far end errored second".
The far end errored second (FEES) refers to the ES detected at the remote end.
HPFESES stands for "higher order path far end severely errored second".
The far end severely errored second (FESES) refers to the SES detected at the remote end.
HPFECSES stands for "higher order path far end consecutive severely errored second".
The far end consecutive severely errored second (FESES) refers to the CSES detected at
the remote end.
HPFEUAS stands for "higher order path unavailable second".

The far end unavailable second (UAS) refers to the UAS detected at the remote end.

Description
PFEBE
Unit
Block (HPFEBBE)
Second (HPFEES, HPFESES, HPFECSES,
and HPFEUAS)

A few bit errors cannot affect services. But if the bit errors are excessive (less than 103 for voice
services and 106 for data services), the services can be interrupted.
Relevant Alarms
The HP_REI alarm occurs at the local node at the same time.
Probable Causes
The system detects the HPFEBBE by the bit 1 to bit 4 of the G1 byte.
B-14

Issue 02 (2008-6-20)

Procedure
Clear the corresponding performance events at the opposite end.
----End
B.2.9 VC3BBE, VC3ES, VC3SES, VC3CSES, and VC3UAS

l
VC3BBE stands for "VC-3 background block error".

BBE is an errored block occurring outside the period of UAT and SES.
VC3ES stands for "VC-3 errored second".

An ES is a certain second with one or more errored blocks detected.
VC3SES stands for "VC-3 severely errored second".

An SES is a certain second which contains not less than 30% errored blocks or at least one
serious disturbance period (SDP). The SDP is a period of at least four consecutive blocks
or 1 ms (taking the longer one) where the error ratios of all the consecutive blocks are more
than or equal to 10-2 or loss of signal occurs.
VC3CSES stands for "VC-3 consecutive severely errored second".

CSES indicates that the SES events consecutively occur, but last less than 10 seconds.
VC3UAS stands for "VC-3 unavailable second".

A UAS period is counted from the first second of 10 consecutive severely errored seconds
(SESs). These ten seconds is considered to be part of the unavailable time. A new available
second period starts from the first second of ten consecutive non-SESs. These ten seconds
is considered to be part of the available time.

Description
B3CNT
Unit
Block (VC3BBE)
Second (VC3ES, VC3SES, VC3CSES,
VC3UAS)

A small number of bit errors do not affect the services. Too many bit errors, however, can
interrupt the services (the bit error rate needs to be less than 10-3 for the voice service, and
10-6 for the data service).
Related Alarm
When the VC3BBE, VC3ES, VC3SES, VC3CSES, or VC3UAS performance event crosses the
preset threshold, the LP_CROSSTR alarm can occur.
Issue 02 (2008-6-20)

B-15

Performance Event
Default 15-Minute
Threshold
Default 24-Hour
Threshold
VC3BBE
1500
15000
VC3ES
50
100
VC3SES
20
50
VC3UAS
20
50
VC3CSES
Probable Causes
The system detects the VC3BE by the B3 byte.
Procedure
Refer to section 4.4 Troubleshooting Bit Errors.
----End
B.2.10 VC3FEBBE, VC3FEES, VC3FESES, VC3FECSES, VC3FEUAS

l
VC3FEBBE stands for "VC-3 far end background block error".

A VC3FEBBE indicates that a BBE event is detected at the far end.
VC3FEES stands for "VC-3 far end errored second".

An FEES indicates that an ES event is detected at the far end.
VC3FESES stands for "VC-3 far end severely errored second".

An FESES indicates that an SES event is detected at the far end.
VC3FECSES stands for "VC-3 far end consecutive severely errored second".
An FECSES indicates that a CSES event is detected at the far end.
VC3FEUAS stands for "VC-3 far end unavailable second".

An FEUAS indicates that a UAS event is detected at the far end.

Description
VC3FEBE
Unit
Block (VC3FEBBE)
Second (VC3FEES, VC3FESES,
VC3FECSES, VC3FEUAS)
B-16

Issue 02 (2008-6-20)


A small number of bit errors do not affect the services. Too many bit errors, however, can
interrupt the services (the bit error rate needs to be less than 10-3 for the voice service, and
10-6 for the data service).
Related Alarm
At the same time, the LP_REI_VC3 alarm is reported at the local NE.
Probable Causes
The system detects the VC3FEBE by bits 14 of the G1 byte.
Procedure
Clear the corresponding performance events at the opposite NE.
----End
B.2.11 LPBBE, LPES, LPSES, LPCSES, and LPUAS

l
LPBBE stands for "lower-order path background block error".

BBE refers to the errored blocks excluding those in the unavailable and severely errored
seconds.
LPES stands for "Lower-order path errored second".

ES refers to the second with one or more errored blocks.
LPSES stands for "lower-order path severely errored second".

SES refers to the second in which more than 30% errored blocks or at least one SDP exists.
The SDP is the period during which the BER of all the consecutive blocks in a period of
less than four consecutive blocks or 1ms (the longer period is applied) is equal to or higher
than 102 or the signal is lost.
LPCSES stands for "lower order path consecutive severely errored second".
CSES refers to the second in which the SES occurs in a consecutive mode and lasts for less
than 10 seconds.
LPUAS stands for "lower order path unavailable second".

UAS refers to the period of unavailable time that begins at the onset of ten CSESs. When
SESs disappear for ten consecutive seconds, the available time begins from the eleventh
second, with the previous ten seconds included.
Issue 02 (2008-6-20)
Attribute
Description
LPBIP2CNT

B-17

Attribute
Description
Unit
Block (LPBBE)
Second (LPES, LPSES, LPCSES, and
LPUAS)

Too many bit errors may interrupt the service (the BER should be less than 103 for the voice
Relevant Alarm
When the LPBBE, LPES, LPSES, LPCSES, and LPUAS events crosses the preset thresholds,
the LP_CROSSTR alarm may be generated.
Performance Event
Default 15-Minute
Threshold
Default 24-Hour
Threshold
LPBBE
1500
15000
LPES
50
100
LPSES
20
50
LPUAS
20
50
LPCSES
Probable Causes
The system detects lower order path bit errors by using the BIP2 of the V5 byte (E1 interface
board or Ethernet board) or B3 byte (E3/T3 interface board).
Procedure
----End
B.2.12 LPFEBBE, LPFEES, LPFESES, LPFECSES and LPFEUAS

l
LPFEBBE stands for "lower order path far end background block error".
The far end background block error (FEBBE) refers to the error detected at the remote end.
LPFEES stands for "lower order path far end errored second".
The far end errored second (FEES) refers to the ES detected at the remote end.
B-18

Issue 02 (2008-6-20)

l
LPFESES stands for "lower order path far end severely errored second".
The far end severely errored second (FESES) refers to the SES detected at the opposite
end.
LPFECSES stands for "lower order path far end consecutive severely errored second".
The far end consecutive severely errored second (FESES) refers to the CSES detected at
the remote end.
LPFEUAS stands for "lower order path unavailable second".

The far end unavailable second (UAS) refers to the UAS detected at the remote end.

Description
LPFEBE
Unit
Block (LPFEBBE)
Second (LPFEES, LPFESES, LPFECSES,
and LPFEUAS)

Too many bit errors can interrupt the service (the bit error rate needs to be less than 103 for the
Relevant Alarm
If the performance event occurs on the tributary board, the LP_REI alarm is generated at the
local NE at the same time. If the performance event occurs on the Ethernet board, the
LP_REI_VC12 alarm is generated at the local NE at the same time
Probable Causes
The system detects lower order path bit errors by using bit 3 of the V5 byte (E1 interface board
or Ethernet board) or bit 1 through bit 4 of the G1 byte (E3/T3 interface board).
Procedure
Clear the corresponding event at the opposite end.
----End
B.2.13 E3_LCV_SDH, E3_LES_SDH, and E3_LSES_SDH

Issue 02 (2008-6-20)
E3_LCV_SDH stands for "E3 line side code violations".
E3_LES_SDH stands for "E3 line side code violation errored seconds".
E3_LSES_SDH stands for "E3 line side code violation severely errored seconds".
B-19


Attribute
Description
DS3_BPV_CNT
Unit
Block

Bit errors may be produced.
Probable Causes
There are interference signals on the transmission lines.
Procedure
Step 1 Check whether services are accessed at the signal reception end.
If ...
Then ...
No,
Re-access the services.
Yes,
Step 2 Check whether the equipment is properly grounded.

If ... Then ...
No, Ground the equipment properly, and thus eliminate the interference produced by
inappropriate grounding.
Step 3 Check whether the connectors of the transmission lines are properly made.
If ...
Then ...
No,
Make new connectors.
Yes,
Eliminate the external interference.
----End
B.2.14 T3_LCV_SDH, T3_LES_SDH, and T3_LSES_SDH

B-20
T3_LCV_SDH stands for "T3 line side code violations".
T3_LES_SDH stands for "T3 line side code violation errored seconds".
T3_LSES_SDH stands for "T3 line side code violation severely errored seconds".
Issue 02 (2008-6-20)


Attribute
Description
DS3_BPV_CNT
Unit
Block

Bit errors may be produced.
Probable Causes
There are interference signals on the transmission lines.
Procedure
Step 1 Check whether services are accessed at the signal reception end.
If ...
Then ...
No,
Re-access the services.
Yes,
Step 2 Check whether the equipment is properly grounded.

If ... Then ...
No, Ground the equipment properly, and thus eliminate the interference produced by
inappropriate grounding.
Step 3 Check whether the connectors of the transmission lines are properly made.
If ...
Then ...
No,
Make new connectors.
Yes,
Eliminate the external interference.
----End
B.2.15 TSLMAX, TSLMIN, and TSLCUR

Issue 02 (2008-6-20)
TSLMAX stands for "maximum value of microwave transmit signal level".
TSLMIN stands for "minimum value of microwave transmit signal level".
TSLCUR stands for "current value of microwave transmit signal level".

B-21


Description
TSL
Unit
0.1 dBm

When the microwave transmit power is too low or too high, the receive power at the opposite
station will be too low or too high. Moreover, bit errors might occur and services might be
interrupted.
Relevant Alarm
If the transmit power crosses the threshold, the RADIO_TSL_HIGH or
RADIO_TSL_LOW alarm can occur.
B.2.16 RSLMAX, RSLMIN and RSLCUR

l
RSLMAX stands for "Maximum value of microwave receive signal level".
RSLMIN stands for "Maximum value of microwave receive signal level".
RSLCUR "Current value of microwave receive power".

Description
RSL
Unit
0.1 dBm

When the microwave receive power is overly low or overly high, bit errors might occur and the
service might be interrupted.
Relevant Alarm
If the receive power crosses the threshold, the RADIO_RSL_HIGH or RADIO_RSL_LOW
alarm occurs.
B.2.17 FEC_BEF_COR_ER, FEC_COR_BYTE_CNT

B-22

Issue 02 (2008-6-20)


l
FEC_BEF_COR_ER stands for "FEC bit error rate before correcting the errors".
This event indicates the impact of the external environment on the transmission.
FEC_COR_BYTE_CNT stands for "FEC corrected byte count".

This event indicates the impact of the FEC.

Description
FECBEFCORER
Unit
None (FEC_BEF_COR_ER)
Byte (FEC_COR_BYTE_CNT)

If the FEC_BEF_COR_ER is too high, there will be residual bit errors in services after the FEC.
Relevant Alarms
If any byte cannot be troubleshooted, the MW_FECUNCOR alarm occurs.
B.2.18 TPLMAX, TPLMIN, and TPLCUR

l
TPLMAX stands for "Maximum value of output optical power".
TPLMIN stands for "Minimum value of output optical power".
TPLCUR stands for "Current value of output optical power".

Description
OPM
Unit
0.1 dBm

In the normal case, the receive optical power is 3 dB higher than the receiver sensitivity, and 5
dB lower than the overload power.
If the transmit power is overly low or high, the receive optical power might be overly low or
high at the opposite end. Thus, bit errors might occur and even the service might be interrupted.
Issue 02 (2008-6-20)

B-23

Relevant Alarms
l
If the receive optical power at the opposite end is lower than the receiver sensitivity, the
IN_PWR_LOW alarm can occur.
If the receive optical power at the opposite end is higher than the overload power, the
IN_PWR_HIGH alarm can occur.
B.2.19 RPLMAX, RPLMIN, and RPLCUR

l
RPLMAX stands for "maximum received power of the optical port laser".
RPLMIN stands for "minimum received power of the optical port laser".
RPLCUR stands for "approximate received power of the optical port laser".

Description
IPM
Unit
dBm

In the normal case, the received power is 3 dB higher than the receiver sensitivity, and 5 dB
lower than the overload power.
When the receive optical power is excessively low or high, bit errors might occur and the service
might be interrupted.
Relevant Alarms
l
If the receive optical power is lower than the receiver sensitivity, the IN_PWR_LOW
alarm can occur.
If the receive optical power is higher than the receiver sensitivity, the IN_PWR_HIGH
alarm can occur.
B.2.20 BDTMPMAX, BDTMPMIN, and BDTMPCUR

B-24
BDTMPMAX stands for "Maximum board temperature".
BDTMPMIN stands for "Minimum board temperature".
BDTMPCUR stands for "Current board temperature".

Issue 02 (2008-6-20)


Description
None
Unit
0.1C

Excessively high or low board temperature might cause faults such as degradation of the board
working performance and bit errors.
Relevant Alarm
If the board temperature crosses the threshold, the TEMP_ALARM alarm occurs.
B.2.21 OSPITMPMAX, OSPITMPMIN, and OSPITMPCUR

l
OSPITMPMAX stands for "maximum temperature of the laser core".
OSPITMPMIN stands for "minimum temperature of the laser core".
OSPITMPCUR stands for "current temperature of the laser core".

Description
TMP
Unit
0.1C

If the temperature of the laser core is excessively high or low, the performance of the laser
deteriorates and other faults may arise.
Relevant Alarms
None.
Issue 02 (2008-6-20)

B-25

C Alarm Management
Alarm Management
C.1 NE Alarm Management

Once set by a user, the NE alarm management function is valid for all boards on the NE.
For the OptiX RTN 600, the NE alarm management function includes the following aspects:
l
Set the alarm storage mode.
Set the alarm delay.
Set the alarm reversion mode.
For details of this function, refer to related manuals or online helps of the OptiX iManager
products.
C.2 Board Alarm Management

The board alarm management function is valid only for the boards on which a user configures
this function.
C.2.1 Setting the Alarm Level

Alarms are categorized into critical, major, minor, and warning according to their severities.
This function is supported by all boards.
C.2.2 Alarm Suppression

The board detects only the alarms of which Alarm Monitoring is set to Yes. For the alarms not
to be monitored, the maintenance personnel can set alarm suppression.
This function is supported for all boards.
C.2.3 Alarm Auto-Report

If Alarm Auto-Report is set to Reported, all the detected alarms are reported to the NM system
in a timely manner. If Alarm Auto-Report is set to Not Report, the alarms are reported only
Issue 02 (2008-6-20)

C-1

C Alarm Management
upon query. The maintenance personnel can change the setting as required through the NM
system.
The alarm auto-report function is supported by all boards.
C.2.4 Alarm Reversion

For ports that are not configured with services, some alarms might be reported. To filter alarms
that need no attention, set the alarms to be reversed. In this way, the alarm status for this port
turns the opposite to the actual case. That is, the status is displayed to be normal when an alarm
actually exists.
Three modes exist for alarm reversion: non-revertive, automatic reversion, and manual
reversion.
l
Non-Revertive
In this mode, the alarms are monitored by default and alarm reversion cannot be enabled
for a port.
Automatic reversion
In this mode, alarm reversion can be enabled for a port. The port does not report the alarms
for which alarm reversion is enabled. When the current alarm is cleared, the alarm reversion
automatically changes into the disabled status. That is, it changes to the non-revertive mode.
Then, the status of alarm reporting for the port becomes the same as the actual status.
Manual reversion
In this mode, alarm reversion can be enabled for a port, whether any alarms exist on the
port or not. After alarm reversion is enabled, the status of alarm reporting becomes the same
as the actual status.
Observe the following cautions when setting alarm reversion:

l
Alarm reversion does not change the actual status of alarms on the board, as well as the
indication status of the alarm indicators.
Alarm reversion is performed on the SCC. The alarm data is the same on the NE and the
NM system, which is the status after the alarm reversion. If queried directly from a board,
however, the actual alarm status is returned.
Alarm reversion is set on the basis of the ports. And it is supported for each port of the
SD1, SL1, SDE, SLE, SL4, IF1A, IF1B, IFX, IF0A, IF0B, PH1, PO1, PD1, PL3, EFT4,
and EMS6.
C.2.5 Setting Bit Error Alarm Threshold

When the number of alarms detected by a board crosses a specific number, the board generates
a bit error alarm. This specific number is the bit error alarm threshold, and the setting of this
threshold is supported by all the bit error threshold-crossing and degrading alarms on the OptiX
RTN 600.
C-2

Issue 02 (2008-6-20)

C Alarm Management
Table C-1 Setting of the bit error alarm threshold

Alarm Name
Default Alarm Threshold
Board Supporting This

Function
B1_EXC
10-3
B1_SD
10-6
SD1, SL1, SDE, SLE, IF1A,

IF1B, IF0A, IF0B, IFX, and
SL4
B2_EXC
10-3
B2_SD
10-6
B3_EXC
10-3
B3_SD
10-6
BIP_EXC
10-3
BIP_SD
10-6
B3_EXC_VC3
10-3
B3_SD_VC3
10-6

IF1B, IFX, and SL4
IF1B, IFX, SL4, and PL3
PO1, PH1, EFT4, EMS6,
IF0A, IF0B, IFX, and PD1
EFT4 and EMS6
C.2.6 AIS Insertion

AIS insertion can be set for some alarms on a board. When the board detects the alarms, it inserts
all ones into the lower level service to indicate the remote end that the service is unavailable.
Table C-2 Setting of AIS insertion
Triggering Condition
Default Value

Function
B1_EXC
Enabled

IF1B, IFX and SL4
Disabled
IF0A and IF0B
Disabled

IF1B and IFX
Enabled
SL4
B2_EXC
Disabled
HP_LOM
Enabled

IF1B, IFX and SL4
HP_TIM
Disabled
HP_SLM
Disabled
HP_UNEQ
Disabled
B2_SD
Issue 02 (2008-6-20)

C-3

C Alarm Management
Default Value

Function
B3_EXC
Enabled
B3_SD
Disabled

IF1B, IFX, PL3 and SL4
B1_SD
Disabled

IF1B, IFX, IF0A, IF0B and
SL4
LP_TIM
Disabled
PO1, PH1, PD1 and PL3
LP_UNEQ
Disabled
LP_SLM
Disabled
T_ALOS
Enabled
BIP_EXC
Disabled
BIP_SD
Disabled
P_LOS
Enabled
PL3
NOTE
When the SD1/SL1/SDE/SLE/IF1A/IF1B board detects the R_LOS, R_LOF, MS_AIS, AU_AIS and
AU_LOP, it inserts the AIS in a forceful manner.
C.2.7 UNEQ Insertion

When the board detects that the service path is not in use or that the LOS alarm exists, it inserts
all zeros to the service signal to notify the remote end that this signal is unavailable.
Table C-3 Setting of UNEQ insertion
C-4
Default Value

Function
The T_ALOS alarm exists.
Disabled
PO1, PH1, PD1 and PL3
The service path is not in use.
Disabled
P_LOS
Disabled

PL3
Issue 02 (2008-6-20)

D Performance Event Management
Performance Event Management
D.1 NE Performance Event Management

The NE performance event management function set by users is applicable to all the boards on
the NE.
The NE performance event management function of the OptiX RTN 600 includes:
l
Setting NE performance event monitoring
Setting the start/end time of performance events
Enabling/Disabling the reporting of the UAT event
For details of these function, refer to the manuals or online Help of the NM system.
D.2 Board Performance Event Management

The performance event management function is only applicable to the board that the user has
set this function on.
Table D-1 Board performance event management function
Issue 02 (2008-6-20)
Function
Board Supporting This Function
Setting 15-minute/24-hour
performance monitoring
SD1, SL1, SDE, SLE, SL4, IFX, IF0A, IF0B, IF1A,

IF1B, PO1, PH1, PD1, EFT4, EMS6, PXC, SCC, and
ODU
Setting 15-minute/24-hour
performance event auto-reporting
SD1, SL1, SDE, SLE,SL4, IFX, IF0A, IF0B, IF1A,

IF1B, PO1, PH1, PD1, EFT4, EMS6, PXC, SCC, and
ODU
Setting performance thresholds
SD1, SL1, SDE, SL4, IFX, IF0A, IF0B, SLE, IF1A,

IF1B, PO1, PH1, PD1, PL3, EFT4, EMS6, and ODU
Resetting the performance register

IF1B, PO1, PH1, PD1, EFT4, EMS6 and ODU

D-1

D Performance Event Management
D-2
Function
Board Supporting This Function
Generating performance threshold

crossing alarms
SD1, SL1, SDE, SLE, SL4M, IFX, IF0A, IF0B, IF1A,

IF1B, PO1, PH1, PD1, PL3, EFT4, EMS6 and ODU
Monitoring UAT events

IF1B, PO1, PH1, PD1, PL3, EFT4, EMS6 and ODU
Monitoring CSES performance

events

IF1B, PO1, PH1, PD1, PL3, EFT4 and EMS6

Issue 02 (2008-6-20)

E Alarm Suppression Relation
Alarm Suppression Relation
Table E-1 Suppression relation between intra-board alarms
Issue 02 (2008-6-20)
Alarm
Identifier
Suppressed Alarm Identifier
MW_LOF
R_LOS, R_LOF, R_LOC, MW_FECUNCOR, MW_RDI, MW_LIM
R_LOS,
R_LOC
R_LOF, J0_MM, B1_EXC, B1_SD , MS_AIS, MS_RDI, B2_EXC,

B2_SD, MS_REI, AU_AIS, AU_LOP, HP_TIM, HP_UNEQ,
HP_SLM, HP_RDI, B3_EXC, B3_SD, HP_LOM, HP_REI,
MW_RDI, MW_LIM
R_LOF
J0_MM, B1_EXC, B1_SD, MS_AIS, MS_RDI, B2_EXC, B2_SD,

MS_REI, AU_AIS, AU_LOP, HP_TIM, HP_UNEQ, HP_SLM,
HP_RDI, B3_EXC, B3_SD, HP_LOM, HP_REI , MW_RDI,
MW_LIM
MS_AIS
B2_SD, MS_REI, MS_RDI AU_AIS, AU_LOP, HP_TIM,

HP_UNEQ, HP_SLM, HP_RDI, B3_EXC, B3_SD, HP_LOM,
HP_REI
MS_RDI
MS_REI
AU_AIS,
AU_LOP
B3_EXC, B3_SD, HP_TIM, HP_SLM, HP_UNEQ, HP_RDI,

HP_LOM, HP_REI
HP_TIMa
HP_LOM, B3_EXC, B3_SD
HP_SLMa
HP_LOM
LP_UNEQ
LP_TIM, LP_RDI,LP_SLM
LP_TIM
LP_RDI
HP_RDI
HP_REI
B1_EXC
B1_SD
B2_EXC
B2_SD

E-1

E Alarm Suppression Relation
Alarm
Identifier
B3_EXC
B3_SD
TU_AIS
P_AIS, LP_TIM, LP_SIZE_ERR, LP_UNEQ, LP_RDI, LP_REI,

LP_RFI, LP_R_FIFO, BIP_EXC, BIP_SD, LP_SLM, B3_EXC,
B3_SD, C2_VCAIS
TU_LOP
TU_AIS, LP_TIM, LP_SIZE_ERR, LP_UNEQ, LP_RDI, LP_REI,

LP_RFI, LP_R_FIFO, BIP_EXC, BIP_SD, LP_SLM, B3_EXC,
B3_SD, C2_VCAIS
T_ALOS
E1_LOS, UP_E1_AIS
E1_LOS
UP_E1_AIS
BIP_EXC
BIP_SD
P_LOS
A_LOC, P_AIS
C2_VCAIS
LP_SLM
NOTE
a: The alarm suppression relation works only when the AIS insertion function is enabled. The alarm
suppression relation is invalid in other cases.
Table E-2 Suppression relation between inter-board alarms
E-2
Alarm Identifier
R_LOS, R_LOC, MS_AIS, AU_AIS,

AU_LOP
TU_AIS
MW_LOF, MW_LIM
TU_AIS

Issue 02 (2008-6-20)

F Glossary
F
1+1 protection
Glossary
A microwave link protection system composed of one working channel

and one protection channel. Two ODUs and two IF boards are used at
each end of a microwave link.
A
ATPC
Automatic Transmit Power Control. A method of adjusting the transmit

power based on fading of the transmit signal detected at the receiver.
B
Bit error
An error occurs to some bits in the digital code stream after being
received, judged, and regenerated, thus damaging the quality of the
transmitted information.
F
FD
Frequency Diversity. Two or more microwave frequencies with certain

frequency space are used to transmit/receive the same signal and
selection is then performed between the two signals to ease the impact
of fading.
I
IDU
Indoor Unit. The indoor unit implements accessing, multiplexing/

demultiplexing, and IF processing for services.
IF
Intermediate Frequency. IF is the transitional frequency between the

frequencies of a modulated signal and an RF signal.
Issue 02 (2008-6-20)

F-1

F Glossary
Line board
A board that processes the services carried on line. As the OptiX RTN
600 involves SDH fiber line, STM-1 cable line, and microwave line, the
line boards include SDH optical interface board, STM-1 electrical
interface board, and IF board.
N
NE
Network Element. An NE contains both the hardware and the software

running on it. One NE is at least equipped with one SCC board which
manages and monitors the entire network element. NE software runs on
the SCC board.
O
ODU
Outdoor Unit. The outdoor unit implements frequency conversion and

amplification for RF signals.
Orderwire
Orderwire is able to provide voice communication for operators or

maintenance engineers at different workstation.
P
PDH
Plesiosynchronous Digital Hierarchy. A multiplexing scheme of bit

stuffing and byte interleaving. It multiplexes the minimum rate 64 kit/s
into the 2 Mbit/s, 34 Mbit/s, 140 Mbit/s and 565 Mbit/s rates.
S
SD
Space Diversity. Two or more antennas separated by a specific distance

transmit/receive the same signal and selection is then performed between
the two signals to ease the impact of fading. Currently, only receive SD
is used.
SDH
Synchronous Digital Hierarchy. A hierarchical set of digital transport

structures, standardized for the transport of suitably adapted payloads
over physical transmission networks.
F-2
T2000
A subnet management system (SNMS). In the telecommunication

management network architecture, the T2000 is located between the NE
level and network level, which can supports all NE level functions and
part of the network level management functions.
Trail
A type of transport entity, mainly engaged in transferring signal from the

input of the trail source to the output of the trail sink, and monitoring the
integrality of the transferred signal.

Issue 02 (2008-6-20)

F Glossary
V
VC
Virtual Container. The information structure used to support path layer

connections in the SDH. It consists of information payload, and path
overhead (POH) information fields organized in a block frame structure
which repeats every 125 or 500 microseconds.
W
Web LCT
Issue 02 (2008-6-20)
Web LCT is located in the NE management layer of a transmission

network. It performs management for a single NE.

F-3

G Acronyms and Abbreviations
Acronyms and Abbreviations
A
AIS
Alarm Indication Signal
APS
Automatic Protection Switching
ASIC
Application Specific Integrated Circuit
ATM
Asynchronous Transfer Mode
ATPC
Automatic Transmit Power Control
AU
Administrative Unit
AU-4
Administrative Unit -4
B
BBE
Background Block Error
BER
Bit Error Rate
BIOS
Basic Input Output System
BIP
Bit-Interleaved Parity
C
CPU
Central Processing Unit
D
DDF
Digital Distribution Frame
E
ECC
Issue 02 (2008-6-20)
Embedded Control Channel

G-1

ESN
Electronic Serial Number
F
FCS
Frame Check Sequence
FD
Frequency Diversity
FEC
Forward Error Correction
FIFO
First In First Out
FPGA
Field Programmable Gate Array
G
GFP
Generic Framing Procedure
H
HP
Higher Order Path
HSB
Hot Standby
HSM
Hitless Switch Mode
I
IDU
Indoor Unit
IE
Internet Explorer
IF
Intermediate Frequency
L
LCAS
Link Capacity Adjustment Scheme
LCT
Generation-Local Craft Terminal
LOS
Loss Of Signal
LP
Lower Order Path
G-2
MAC
Medium Access Control
MODEM
MOdulator-DEModulator
MS
Multiplex Section

Issue 02 (2008-6-20)

MSP
Multiplex Section Protection
MTU
Maximum Transmission Unit
O
ODU
Outdoor Unit
P
PDH
Plesiochronous Digital Hierarchy
PRBS
Pseudo-random binary sequence
Q
QPSK
Quadrature Phase Shift Keying
R
RDI
Remote Defect Indication
REI
Remote Error Indication
RMON
Remote Monitoring
RS
Regenerator Section
RSL
Received Signal Level
RTC
Real-time Clock
RTN
Radio Transmission Node
S
SD
Space Diversity
SDH
Synchronous Digital Hierarchy
SES
Severely Errored Seconds
SFP
Small Form-Factor Pluggable
SNCP
Sub-Network Connection Protection
STM-1
SDH Transport Module -1
T
TU
Issue 02 (2008-6-20)
Tributary Unit

G-3

U
UAS
Unavailable Seconds
UAT
Unavailable Time
UNI
user-network interface
V
VB
Virtual Bridge
VC
Virtual Container
VC-12
Virtual Container -12
VC-3
VC-4
VC12
VC3
VC4
VCG
Virtual Concatenation Group
VLAN
Virtual LAN
W
WS
Wayside
X
XPIC
G-4
Cross-polarization interference cancellation

Issue 02 (2008-6-20)

Index
Index
A
A_LOC, A-10
alarm, A-1
AIS insertion, C-3
auto-report, C-2
bit error threshold, C-2
corrective procedure, A-10
level, C-1
list, A-1
management function, board level, C-1
management function, NE level, C-1
reversion, C-2
suppression, C-1
suppression relation, E-1
UNEQ insertion, C-4
alarm management, C-1
ALM_GFP_dCSF, A-12
ALM_GFP_dLFD, A-13
ALM_RTC_FAIL, A-14
APS_FAIL, A-15
APS_INDI, A-16
APS_MANUAL_STOP, A-11
AU_AIS, A-17
AU_LOP, A-19
AUPJCHIGH, B-6
AUPJCLOW, B-6
AUPJCNEW, B-6
automatic release
loopback operation, 5-21
shut down the laser, 5-21
B
B1_EXC, A-20
B1_SD, A-21
B2_EXC, A-22
B2_SD, A-23
B3_EXC, A-24
B3_EXC_VC3, A-25
B3_SD, A-26
B3_SD_VC3, A-27
BD_NOT_INSTALLED, A-28
BD_STATUS, A-29
Issue 02 (2008-6-20)
BDTMPCUR, B-24
BDTMPMAX, B-24
BDTMPMIN, B-24
BIP_EXC, A-32
BIP_SD, A-33
board
inserting, 5-23
removing, 5-22
BOOTROM_BAD, A-33
C
C2_VCAIS, A-35
cleaning fiber adapters, 5-37
cleaning fiber connectors
using cartridge cleaners, 5-34
using lens tissue, 5-36
CONFIG_NOSUPPORT, A-35
D
DBMS_ERROR, A-37
DBMS_PROTECT_MODE, A-39
DN_E1_AIS, A-40
E
E1_LOC, A-41
E1_LOS, A-42
E3_LCV_SDH, B-19
E3_LES_SDH, B-19
E3_LSES_SDH, B-19
emergency maintenance, 3-1
ESN_FAILED, A-43
ESN_INVALID, A-44
ETH_LOS, A-45
Ethernet board
Ethernet test frame, 5-18
Ethernet service processing board, 5-11
EXT_SYNC_LOS, A-46
F
F1PORT_FAILED, A-47

i-1

Index
FAN_FAIL, A-48
FCS_ERR, A-49
FEC_BEF_COR_ER, B-22
FEC_COR_BYTE_CNT, B-22
K1_K2_M, A-71
K2_M, A-72
LICENSE_LOST, A-85
LINK_ERR, A-87
LOOP_ALM, A-88
loopback
, 5-8
IF board, 5-8
IF port, 5-8
PDH interface board, 5-7
SDH electrical interface board, 5-5
SDH optical interface board, 5-3
loopback operation, 5-11, 5-13
LP_CROSSTR, A-91
LP_R_FIFO, A-92
LP_RDI, A-93
LP_RDI_VC12, A-94
LP_RDI_VC3, A-95
LP_REI, A-96
LP_REI_VC12, A-97
LP_REI_VC3, A-97
LP_RFI, A-98
LP_SIZE_ERR, A-99
LP_SLM, A-100
LP_SLM_VC12, A-101
LP_SLM_VC3, A-102
LP_T_FIFO, A-103
LP_TIM, A-104
LP_TIM_VC12, A-105
LP_TIM_VC3, A-106
LP_UNEQ, A-107
LP_UNEQ_VC12, A-108
LP_UNEQ_VC3, A-109
LPBBE, B-17
LPCSES, B-17
LPES, B-17
LPFEBBE, B-18
LPFECSES, B-18
LPFEES, B-18
LPFESES, B-18
LPFEUAS, B-18
LPS_UNI_BI_M, A-90
LPSES, B-17
LPUAS, B-17
LSR_NO_FITED, A-111
LSR_WILL_DIE, A-111
LTI, A-112
LASER_CLOSED, A-74
LASER_MOD_ERR_EX, A-75
LCAS_FOPR, A-76
LCAS_FOPT, A-77
LCAS_PLCR, A-79
LCAS_PLCT, A-80
LCAS_TLCR, A-81
LCAS_TLCT, A-83
LCS_LIMITED, A-84
LICENSE_ERR, A-86
MOD_TYPE_MISMATCH, A-114
MS_AIS, A-115
MS_CROSSTR, A-116
MS_RDI, A-117
MS_REI, A-118
MSAD_CROSSTR, A-119
MSBBE, B-10
MSCSES, B-10
MSES, B-10
MSFEBBE, B-11
H
HARD_BAD, A-51
HP_CROSSTR, A-53
HP_LOM, A-54
HP_RDI, A-55
HP_REI, A-56
HP_SLM, A-57
HP_TIM, A-59
HP_UNEQ, A-60
HPAD_CROSSTR, A-61
HPBBE, B-12
HPCSES, B-12
HPES, B-12
HPFEBBE, B-14
HPFECSES, B-14
HPFEES, B-14
HPFESES, B-14
HPFEUAS, B-14
HPSES, B-12
HPUAS, B-12
HSB_INDI, A-62
HSM_INDI, A-63
I
IF_CABLE_OPEN, A-64
IF_INPWR_ABN, A-65
IF_MODE_UNSUPPORTED, A-67
IN_PWR_HIGH, A-67
IN_PWR_LOW, A-69
J
J0_MM, A-70
i-2

Issue 02 (2008-6-20)

MSFECSES, B-11
MSFEES, B-11
MSFESES, B-11
MSFEUAS, B-11
MSSES, B-10
MSSW_DIFFERENT, A-120
MSUAS, B-10
MW_FECUNCOR, A-121
MW_LIM, A-122
MW_LOF, A-124
MW_RDI, A-125
N
NESF_LOST, A-126
NESTATE_INSTALL, A-127
NO_BD_SOFT, A-128
NP1_MANUAL_STOP, A-129
NP1_SW_FAIL, A-130
NP1_SW_INDI, A-131
O
ODU, 5-13
OPM_FAIL, A-132
OSPITMPCUR, B-25
OSPITMPMAX, B-25
OSPITMPMIN, B-25
P
P_AIS, A-136
P_LOS, A-137
part replacement, 5-21
performance event, B-1
corrective procedure, B-6
list, B-1
management function, board level, D-1
management function, NE level, D-1
performance event management, D-1
PORT_MODULE_OFFLINE, A-133
POWER_ALM, A-134
POWER_FAIL, A-135
PRBS test, 5-16
PS, A-138
R
R_F_RST, A-139
R_LOC, A-140
R_LOF, A-142
R_LOS, A-143
R_S_ERR, A-145
RADIO_MUTE, A-146
RADIO_RSL_HIGH, A-148
RADIO_RSL_LOW, A-149
RADIO_TSL_HIGH, A-151
RADIO_TSL_LOW, A-151
Issue 02 (2008-6-20)
Index
RELAY_ALARM, A-152
replace
IF board, 5-28
replacing
Ethernet service processing board, 5-27
FAN, 5-31
ODU, 5-33
PDH interface board, 5-26
PXC board, 5-29
SCC board, 5-30
SDH electrical interface board, 5-25
SDH optical interface board, 5-24
resetting
cold resetting, 5-14
SCC resetting, 5-15
warm resetting, 5-15
routine maintenance
abnormal event, 2-15
browse abnormal event, 2-7
browse current alarm, 2-5, 2-13
browse current performance event of SDH/PDH,
2-7, 2-15
browse history alarm, 2-14
browse history performance event of SDH/PDH,
2-8, 2-16
check IF cable, 2-24
check status of NE and board, 2-4, 2-12
check the antenna, 2-24
check the equipment room, 2-22
check the hybrid coupler, 2-23
check the ODU, 2-23
cleaning the air filter, 2-20
history alarm, 2-6
maintenance items, 2-2
test IF 1+1 switching, 2-9, 2-17
test IF N+1 switching, 2-10, 2-18
test the orderwire phone, 2-21
two-fiber bidirectional MSP ring switching, 2-11,
2-19
RP_LOC, A-153
RPLCUR, B-24
RPLMAX, B-24
RPLMIN, B-24
RS_CROSSTR, A-154
RSBBE, B-8
RSCSES, B-8
RSES, B-8
RSLCUR, B-22
RSLMAX, B-22
RSLMIN, B-22
RSOFS, B-9
RSOOF, B-9
RSSES, B-8
RSUAS, B-8
S
S1_SYN_CHANGE, A-155
i-3

Index
setting
open/close laser, 5-20
state of the ODU transmitter, 5-20
SYN_BAD, A-156
SYNC_C_LOS, A-157
VCAT_LOM_VC3, A-177
VCAT_SQM_VC12, A-178
VCAT_SQM_VC3, A-179
VOLT_LOS, A-181
T
T3_LCV_SDH, B-20
T3_LES_SDH, B-20
T3_LSES_SDH, B-20
T_ALOS, A-158
T_F_RST, A-159
T_FIFO_E, A-160
T_LOC, A-161
T_LOS, A-163
TEMP_ALARM, A-164
TPLCUR, B-23
TPLMAX, B-23
TPLMIN, B-23
troubleshooting
bit error, 4-15
general fault locating procedure, 4-2
interconnection with the PDH equipment, 4-28
interconnection with the SDH equipment, 4-24
orderwire, 4-36
pointer justification, 4-20
service interruption, 4-4
TSLCUR, B-21
TSLMAX, B-21
TSLMIN, B-21
TU_AIS, A-165
TU_AIS_VC12, A-167
TU_AIS_VC3, A-168
TU_LOP, A-170, A-172
TU_LOP_VC12, A-171
TUPJCHIGH, B-7
TUPJCLOW, B-7
TUPJCNEW, B-7
W_R_Failure, A-186
WRG_BD_TYPE, A-183
WRG_DEV_TYPE, A-184
WS_LOS, A-184
X
XCP_INDI, A-186
XPIC_LOS, A-187
U
UP_E1_AIS, A-173
V
VC3BBE, B-15
VC3CSES, B-15
VC3ES, B-15
VC3FEBBE, B-16
VC3FECSES, B-16
VC3FEES, B-16
VC3FESES, B-16
VC3FEUAS, B-16
VC3SES, B-15
VC3UAS, B-15
VCAT_LOA, A-175
VCAT_LOM_VC12, A-176
i-4

Issue 02 (2008-6-20)

00425665-IDU 610620 Maintenance Guide (V100R002 - 02) PDF

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

00425665-IDU 610620 Maintenance Guide (V100R002 - 02) PDF

Transféré par

Droits d'auteur :

Formats disponibles

OptiX RTN 600 Radio Transmission System

IDU 610/620 Maintenance Guide

Huawei Proprietary and Confidential

Huawei Technologies Co., Ltd.

Huawei Industrial Base

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

Trademarks and Permissions

Huawei Proprietary and Confidential

OptiX RTN 600 Radio Transmission System

Huawei Proprietary and Confidential

OptiX RTN 600 Radio Transmission System

2.5 Guide to Field Maintenance of Outdoor Equipment.....................................................................................2-22

3 Emergency Maintenance Guide..............................................................................................3-1

5 Common Maintenance Operation Guide..............................................................................5-1

Huawei Proprietary and Confidential

OptiX RTN 600 Radio Transmission System

5.8.5 Replacing the PDH Interface Board.....................................................................................................5-26

Huawei Proprietary and Confidential

OptiX RTN 600 Radio Transmission System

Huawei Proprietary and Confidential

OptiX RTN 600 Radio Transmission System

Huawei Proprietary and Confidential

OptiX RTN 600 Radio Transmission System

Huawei Proprietary and Confidential

OptiX RTN 600 Radio Transmission System

B Performance Event Reference.................................................................................................B-1

D Performance Event Management..........................................................................................D-1

Huawei Proprietary and Confidential

OptiX RTN 600 Radio Transmission System

D.1 NE Performance Event Management............................................................................................................D-1

E Alarm Suppression Relation...................................................................................................E-1

Huawei Proprietary and Confidential

OptiX RTN 600 Radio Transmission System

Huawei Proprietary and Confidential

OptiX RTN 600 Radio Transmission System

Figure 5-20 PRBS test in the tributary direction................................................................................................5-16

Huawei Proprietary and Confidential

OptiX RTN 600 Radio Transmission System

Huawei Proprietary and Confidential

OptiX RTN 600 Radio Transmission System

Huawei Proprietary and Confidential

OptiX RTN 600 Radio Transmission System

About This Document

About This Document

OptiX RTN 600

OptiX iManager T2000

Know microwave communication basics.

Know the basics of the OptiX RTN 600 product.

Huawei Proprietary and Confidential

OptiX RTN 600 Radio Transmission System

About This Document

Describes maintenance items and operation procedures for routine

Describes operation procedures for emergency maintenance of the

Describes the causes of common faults and troubleshooting

Describes common maintenance operations of the OptiX RTN 600.

Describes all the performance events and clearing procedures of the

Describes the alarm management function of the OptiX RTN 600.

Describes the performance management function of the OptiX RTN

Describes the alarm suppression relation of the OptiX RTN 600.

Lists the terms used in this document.

Lists the acronyms and abbreviations used in this document.

Huawei Proprietary and Confidential

OptiX RTN 600 Radio Transmission System