Maintenance Guide V100R005C00 01 PDF

OptiX RTN 620 Radio Transmission System
V100R005C00
Maintenance Guide
Issue 01
Date 2009-12-30
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2009-2009. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue 01 (2009-12-30) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
OptiX RTN 620
Maintenance Guide About This Document
About This Document
Purpose
This document is a maintenance guide of the OptiX RTN 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 620 V100R005C00
iManager U2000 V100R002C00
Intended Audience
This document is intended for the maintenance engineers of the OptiX RTN 620. Before reading
this document, you need to:
l Network planning engineer

l Data configuration engineer
l System maintenance engineer
Organization
This document is organized as follows.
Issue 01 (2009-12-30) Huawei Proprietary and Confidential iii

OptiX RTN 620
About This Document Maintenance Guide
Chapter Content
1 Safety Describes parts of the safety precautions. Read and follow these safety
Precautions precautions before installing, commissioning, and maintaining the
OptiX RTN 620.
2 Guides to High- Describes the common dangerous maintenance operations.

Risk Operations
3 Routine Describes maintenance items and operation procedures for routine

Maintenance maintenance of the OptiX RTN 620.
4 Emergency Describes operation procedures for emergency maintenance of the

Maintenance OptiX RTN 620.
5 Troubleshooting Describes the causes of common faults and troubleshooting

procedures of the OptiX RTN 620.
6 Part Replacement Describes the replacement process of each board on the OptiX RTN
620.
7 Supporting Task Describes the common maintenance operations of the OptiX RTN
620 by using the NMS.
A Alarm Reference Describes all the possible alarms and clearing procedures of the OptiX
RTN 620.
B Abnormal Event Describes the important abnormal events that may occur and the
Reference corresponding troubleshooting procedures of the OptiX RTN 620.
C Performance Describes all the performance events and clearing procedures of the
Event Reference OptiX RTN 620.
D RMON Event Describes the RMON events that may occur and the corresponding
Reference troubleshooting procedures of the OptiX RTN 620.
E Alarm Describes the alarm management function of the OptiX RTN 620.
Management
F Performance Describes the performance management function of the OptiX RTN

Event Management 620.
G Alarm Describes the alarm suppression relation of the OptiX RTN 620.
Suppression
Relationship
H Glossary Lists the terms used in this document.
I Acronyms and Lists the acronyms and abbreviations used in this document.
Abbreviations
iv Huawei Proprietary and Confidential Issue 01 (2009-12-30)

OptiX RTN 620
Maintenance Guide About 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.
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.
Issue 01 (2009-12-30) Huawei Proprietary and Confidential v

OptiX RTN 620
About This Document Maintenance Guide
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.
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 01 (2009-12-30)

This document is the first release of the V100R005C00 version.
vi Huawei Proprietary and Confidential Issue 01 (2009-12-30)

OptiX RTN 620
Maintenance Guide Contents
Contents
About This Document...................................................................................................................iii

1 Safety Precautions......................................................................................................................1-1
2 Guides to High-Risk Operations............................................................................................2-1
2.1 Operation Guide to a Toggle Lever Switch.....................................................................................................2-2
2.2 Operation Guide to IF Jumpers.......................................................................................................................2-3
2.3 Operation Guide to IF Cables..........................................................................................................................2-4
2.4 Operation Guide to IF Boards.........................................................................................................................2-5
3 Routine Maintenance................................................................................................................3-1
3.1 Routine Maintenance Items.............................................................................................................................3-2
3.2 Guidelines for Routine Maintenance Items.....................................................................................................3-3
3.2.1 Checking the Status of NEs....................................................................................................................3-4
3.2.2 Browsing the Current Alarms................................................................................................................3-5
3.2.3 Browsing the History Alarms.................................................................................................................3-6
3.2.4 Browsing the Abnormal Events.............................................................................................................3-7
3.2.5 Browsing the Current Performance........................................................................................................3-7
3.2.6 Browsing the History Performance........................................................................................................3-8
3.2.7 Browsing the History Transmit Power and Receive Power...................................................................3-9
3.2.8 Testing IF 1+1 Switching.....................................................................................................................3-10
3.2.9 Testing IF N+1 Switching....................................................................................................................3-11
3.2.10 Testing Two-Fiber Bidirectional MSP Ring Switching.....................................................................3-12
3.2.11 Cleaning the Air Filter........................................................................................................................3-13
3.2.12 Checking the Equipment Room.........................................................................................................3-14
3.2.13 Checking the ODU.............................................................................................................................3-14
3.2.14 Checking the Hybrid Coupler............................................................................................................3-15
3.2.15 Checking the Antenna........................................................................................................................3-15
3.2.16 Checking the IF Cables......................................................................................................................3-16
3.2.17 Checking the LOS Condition.............................................................................................................3-17
4 Emergency Maintenance...........................................................................................................4-1
4.1 Definition of Emergency.................................................................................................................................4-2
4.2 Purposes of Emergence Maintenance..............................................................................................................4-2
4.3 Procedure of Emergency Maintenance............................................................................................................4-2
Issue 01 (2009-12-30) Huawei Proprietary and Confidential vii

OptiX RTN 620
Contents Maintenance Guide
5 Troubleshooting.........................................................................................................................5-1
5.1 General Troubleshooting Procedure................................................................................................................5-3
5.2 Troubleshooting Service Interruption.............................................................................................................5-5
5.3 Troubleshooting Radio Links........................................................................................................................5-11
5.4 Troubleshooting Bit Errors in TDM Services...............................................................................................5-19
5.5 Troubleshooting the Interconnection with the SDH Equipment...................................................................5-24
5.6 Troubleshooting the Interconnection with the PDH Equipment...................................................................5-28
5.7 Troubleshooting SDH/PDH Radio-Based Ethernet Service Faults..............................................................5-30
5.8 Troubleshooting Faults in Hybrid Radio-Based Ethernet Services..............................................................5-36
5.9 Troubleshooting Pointer Justifications..........................................................................................................5-42
5.10 Troubleshooting Orderwire Faults..............................................................................................................5-47
6 Part Replacement........................................................................................................................6-1
6.1 Removing a Board...........................................................................................................................................6-4
6.2 Inserting a Board.............................................................................................................................................6-5
6.3 Replacing the SDH Optical Interface Board...................................................................................................6-7
6.4 Replacing the SDH Electrical Interface Board................................................................................................6-8
6.5 Replacing the PDH Interface Board................................................................................................................6-9
6.6 Replacing the Ethernet Service Processing Board........................................................................................6-10
6.7 Replacing the IF Board.................................................................................................................................6-11
6.8 Replacing the PXC Board.............................................................................................................................6-13
6.9 Replacing the Storage Card...........................................................................................................................6-14
6.10 Replacing the SCC Board...........................................................................................................................6-18
6.11 Replacing the Fan Tray...............................................................................................................................6-19
6.12 Replacing an ODU......................................................................................................................................6-21
6.13 Replacing the IF Cable................................................................................................................................6-22
7 Supporting Task.........................................................................................................................7-1
7.1 Hardware Loopback........................................................................................................................................7-3
7.2 Cleaning Fiber Connectors and Adapters........................................................................................................7-3
7.2.1 Cleaning Fiber Connectors Using Cartridge Cleaners...........................................................................7-3
7.2.2 Cleaning Fiber Connectors Using Lens Tissue......................................................................................7-5
7.2.3 Cleaning Fiber Adapters Using Optical Cleaning Sticks.......................................................................7-6
7.3 Browsing Alarms, Abnormal Events, and Performance Events.....................................................................7-7
7.3.1 Checking the NE Status..........................................................................................................................7-8
7.3.2 Checking the Board Status.....................................................................................................................7-9
7.3.3 Browsing the Current Alarms................................................................................................................7-9
7.3.4 Browsing History Alarms.....................................................................................................................7-10
7.3.5 Browsing the Abnormal Events...........................................................................................................7-11
7.3.6 Browsing Current Performance Events................................................................................................7-12
7.3.7 Browsing the History Performance......................................................................................................7-13
7.3.8 Browsing the Performance Event Threshold-Crossing Records..........................................................7-14
7.4 Querying a Report.........................................................................................................................................7-15
7.4.1 Querying a Board Information Report Through the Web LCT............................................................7-15
viii Huawei Proprietary and Confidential Issue 01 (2009-12-30)

OptiX RTN 620
7.4.2 Querying a Board Manufacture Information Report............................................................................7-16

7.4.3 Querying the Status of a Radio Link....................................................................................................7-16
7.5 Software loopback.........................................................................................................................................7-17
7.5.1 Setting Loopback for the SDH Optical Interface Board......................................................................7-17
7.5.2 Setting Loopback for the SDH Electrical Interface Board...................................................................7-19
7.5.3 Setting Loopback for the Tributary Board...........................................................................................7-21
7.5.4 Setting Loopback for the IF Board.......................................................................................................7-23
7.5.5 Setting Loopback for the Ethernet Service Processing Board.............................................................7-25
7.5.6 Locating the Fault by Performing Loopbacks......................................................................................7-27
7.6 Resetting........................................................................................................................................................7-28
7.6.1 Cold Resetting......................................................................................................................................7-29
7.6.2 Warm Resetting....................................................................................................................................7-29
7.6.3 SCC Resetting......................................................................................................................................7-30
7.7 PRBS Test.....................................................................................................................................................7-30
7.7.1 PRBS Test of the Tributary Board.......................................................................................................7-31
7.7.2 PRBS Test of the IF Board...................................................................................................................7-33
7.8 Querying the License Capacity.....................................................................................................................7-34
7.9 Setting the State of a Laser............................................................................................................................7-35
7.10 Setting the ALS function.............................................................................................................................7-35
7.11 Setting the Automatic Release Function.....................................................................................................7-36
7.12 Switching PXC Boards................................................................................................................................7-36
7.13 Configuring Performance Monitoring Status of NEs..................................................................................7-37
7.14 Querying the Impedance of an E1 Channel.................................................................................................7-38
7.15 Using Ethernet Test Frames........................................................................................................................7-39
7.16 Querying the Working Status of an Ethernet Port.......................................................................................7-40
7.17 Setting the Threshold of Received Traffic Flow on an Ethernet Port.........................................................7-40
7.18 Performing Statistics for the Traffic Flow on an Ethernet Port..................................................................7-41
7.19 Performing Statistics for the Traffic Flow of Ethernet Services.................................................................7-42
A Alarm Reference.......................................................................................................................A-1
A.1 Alarm List......................................................................................................................................................A-2
A.2 Alarms and Handling Procedures................................................................................................................A-13
A.2.1 A_LOC...............................................................................................................................................A-13
A.2.2 ALM_GFP_dCSF...............................................................................................................................A-14
A.2.3 ALM_GFP_dLFD..............................................................................................................................A-15
A.2.4 AM_DOWNSHIFT............................................................................................................................A-16
A.2.5 APS_FAIL..........................................................................................................................................A-17
A.2.6 APS_INDI..........................................................................................................................................A-19
A.2.7 APS_MANUAL_STOP.....................................................................................................................A-20
A.2.8 AU_AIS..............................................................................................................................................A-21
A.2.9 AU_LOP.............................................................................................................................................A-23
A.2.10 B1_EXC...........................................................................................................................................A-24
A.2.11 B1_SD..............................................................................................................................................A-27
Issue 01 (2009-12-30) Huawei Proprietary and Confidential ix

OptiX RTN 620
A.2.12 B2_EXC...........................................................................................................................................A-30
A.2.13 B2_SD..............................................................................................................................................A-33
A.2.14 B3_EXC...........................................................................................................................................A-35
A.2.15 B3_EXC_VC3..................................................................................................................................A-38
A.2.16 B3_SD..............................................................................................................................................A-41
A.2.17 B3_SD_VC3.....................................................................................................................................A-43
A.2.18 BD_NOT_INSTALLED..................................................................................................................A-46
A.2.19 BD_STATUS...................................................................................................................................A-47
A.2.20 BIP_EXC..........................................................................................................................................A-49
A.2.21 BIP_SD.............................................................................................................................................A-50
A.2.22 BOOTROM_BAD............................................................................................................................A-52
A.2.23 C2_VCAIS.......................................................................................................................................A-53
A.2.24 CONFIG_NOSUPPORT..................................................................................................................A-54
A.2.25 DBMS_ERROR...............................................................................................................................A-56
A.2.26 DBMS_PROTECT_MODE.............................................................................................................A-58
A.2.27 DOWN_E1_AIS...............................................................................................................................A-59
A.2.28 E1_LOC............................................................................................................................................A-60
A.2.29 E1_LOS............................................................................................................................................A-61
A.2.30 ESN_INVALID................................................................................................................................A-62
A.2.31 ETH_CFM_MISMERGE.................................................................................................................A-63
A.2.32 ETH_CFM_UNEXPERI..................................................................................................................A-65
A.2.33 ETH_CFM_LOC..............................................................................................................................A-67
A.2.34 ETH_CFM_RDI...............................................................................................................................A-69
A.2.35 ETH_LOS.........................................................................................................................................A-71
A.2.36 ETHOAM_DISCOVER_FAIL........................................................................................................A-73
A.2.37 ETHOAM_RMT_CRIT_FAULT....................................................................................................A-74
A.2.38 ETHOAM_RMT_LOOP..................................................................................................................A-76
A.2.39 ETHOAM_RMT_SD.......................................................................................................................A-77
A.2.40 ETHOAM_SELF_LOOP.................................................................................................................A-78
A.2.41 ETHOAM_VCG_SELF_LOOP.......................................................................................................A-80
A.2.42 EX_ETHOAM_CC_LOS.................................................................................................................A-82
A.2.43 EX_ETHOAM_MPID_CNFLCT....................................................................................................A-84
A.2.44 EXT_SYNC_LOS............................................................................................................................A-86
A.2.45 F1PORT_FAILED...........................................................................................................................A-87
A.2.46 FAN_FAIL.......................................................................................................................................A-88
A.2.47 FCS_ERR.........................................................................................................................................A-89
A.2.48 FLOW_OVER..................................................................................................................................A-90
A.2.49 HARD_BAD....................................................................................................................................A-91
A.2.50 HP_CROSSTR.................................................................................................................................A-94
A.2.51 HP_LOM..........................................................................................................................................A-95
A.2.52 HP_RDI............................................................................................................................................A-96
A.2.53 HP_REI.............................................................................................................................................A-97
x Huawei Proprietary and Confidential Issue 01 (2009-12-30)

OptiX RTN 620
A.2.54 HP_SLM...........................................................................................................................................A-98
A.2.55 HP_TIM............................................................................................................................................A-99
A.2.56 HP_UNEQ......................................................................................................................................A-101
A.2.57 HPAD_CROSSTR.........................................................................................................................A-102
A.2.58 IF_CABLE_OPEN.........................................................................................................................A-103
A.2.59 IF_INPWR_ABN...........................................................................................................................A-104
A.2.60 IF_MODE_UNSUPPORTED........................................................................................................A-106
A.2.61 IN_PWR_HIGH.............................................................................................................................A-107
A.2.62 IN_PWR_LOW..............................................................................................................................A-109
A.2.63 J0_MM...........................................................................................................................................A-110
A.2.64 K1_K2_M.......................................................................................................................................A-111
A.2.65 K2_M..............................................................................................................................................A-113
A.2.66 LAG_PORT_FAIL.........................................................................................................................A-115
A.2.67 LAG_VC_PORT_FAIL.................................................................................................................A-117
A.2.68 LASER_CLOSED..........................................................................................................................A-119
A.2.69 LASER_MOD_ERR_EX...............................................................................................................A-120
A.2.70 LCAS_FOPR..................................................................................................................................A-121
A.2.71 LCAS_FOPT..................................................................................................................................A-123
A.2.72 LCAS_PLCR..................................................................................................................................A-124
A.2.73 LCAS_PLCT..................................................................................................................................A-126
A.2.74 LCAS_TLCR..................................................................................................................................A-127
A.2.75 LCAS_TLCT..................................................................................................................................A-129
A.2.76 LCS_LIMITED..............................................................................................................................A-130
A.2.77 LICENSE_LOST............................................................................................................................A-132
A.2.78 LICENSE_ERR..............................................................................................................................A-132
A.2.79 LINK_ERR.....................................................................................................................................A-133
A.2.80 LOOP_ALM...................................................................................................................................A-135
A.2.81 LP_CROSSTR................................................................................................................................A-137
A.2.82 LP_R_FIFO....................................................................................................................................A-138
A.2.83 LP_RDI...........................................................................................................................................A-139
A.2.84 LP_RDI_VC12...............................................................................................................................A-140
A.2.85 LP_RDI_VC3.................................................................................................................................A-141
A.2.86 LP_REI...........................................................................................................................................A-142
A.2.87 LP_REI_VC12...............................................................................................................................A-143
A.2.88 LP_REI_VC3.................................................................................................................................A-144
A.2.89 LP_RFI...........................................................................................................................................A-145
A.2.90 LP_SIZE_ERR...............................................................................................................................A-146
A.2.91 LP_SLM.........................................................................................................................................A-147
A.2.92 LP_SLM_VC12..............................................................................................................................A-148
A.2.93 LP_SLM_VC3................................................................................................................................A-149
A.2.94 LP_T_FIFO....................................................................................................................................A-150
A.2.95 LP_TIM..........................................................................................................................................A-151
Issue 01 (2009-12-30) Huawei Proprietary and Confidential xi

OptiX RTN 620
A.2.96 LP_TIM_VC12...............................................................................................................................A-152
A.2.97 LP_TIM_VC3.................................................................................................................................A-153
A.2.98 LP_UNEQ......................................................................................................................................A-154
A.2.99 LP_UNEQ_VC12...........................................................................................................................A-156
A.2.100 LP_UNEQ_VC3...........................................................................................................................A-157
A.2.101 LPS_UNI_BI_M...........................................................................................................................A-158
A.2.102 LPT_INEFFECT..........................................................................................................................A-159
A.2.103 LPT_RFI.......................................................................................................................................A-160
A.2.104 LSR_NO_FITED..........................................................................................................................A-162
A.2.105 LSR_WILL_DIE..........................................................................................................................A-163
A.2.106 LTI................................................................................................................................................A-164
A.2.107 MOD_TYPE_MISMATCH.........................................................................................................A-165
A.2.108 MS_AIS........................................................................................................................................A-167
A.2.109 MS_CROSSTR.............................................................................................................................A-168
A.2.110 MS_RDI.......................................................................................................................................A-169
A.2.111 MS_REI........................................................................................................................................A-171
A.2.112 MSAD_CROSSTR.......................................................................................................................A-172
A.2.113 MSSW_DIFFERENT...................................................................................................................A-173
A.2.114 MULTI_RPL_OWNER...............................................................................................................A-175
A.2.115 MW_BER_EXC...........................................................................................................................A-176
A.2.116 MW_BER_SD..............................................................................................................................A-177
A.2.117 MW_FEC_UNCOR.....................................................................................................................A-178
A.2.118 MW_LIM.....................................................................................................................................A-183
A.2.119 MW_LOF.....................................................................................................................................A-185
A.2.120 MW_RDI......................................................................................................................................A-190
A.2.121 NESF_LOST................................................................................................................................A-191
A.2.122 NESTATE_INSTALL..................................................................................................................A-193
A.2.123 NO_BD_SOFT.............................................................................................................................A-193
A.2.124 NP1_MANUAL_STOP................................................................................................................A-194
A.2.125 NP1_SW_FAIL............................................................................................................................A-195
A.2.126 NP1_SW_INDI.............................................................................................................................A-197
A.2.127 OPM_FAIL...................................................................................................................................A-198
A.2.128 P_AIS...........................................................................................................................................A-199
A.2.129 P_LOS..........................................................................................................................................A-200
A.2.130 PROT_CONN_ERR.....................................................................................................................A-201
A.2.131 PORT_MODULE_OFFLINE......................................................................................................A-203
A.2.132 POWER_ALM.............................................................................................................................A-205
A.2.133 PS..................................................................................................................................................A-206
A.2.134 R_F_RST......................................................................................................................................A-207
A.2.135 R_LOC.........................................................................................................................................A-208
A.2.136 R_LOF..........................................................................................................................................A-210
A.2.137 R_LOS..........................................................................................................................................A-212
xii Huawei Proprietary and Confidential Issue 01 (2009-12-30)

OptiX RTN 620
A.2.138 R_S_ERR.....................................................................................................................................A-214
A.2.139 RADIO_FADING_MARGIN_INSUFF......................................................................................A-215
A.2.140 RADIO_MUTE............................................................................................................................A-217
A.2.141 RADIO_RSL_BEYONDTH........................................................................................................A-218
A.2.142 RADIO_RSL_HIGH....................................................................................................................A-219
A.2.143 RADIO_RSL_LOW.....................................................................................................................A-220
A.2.144 RADIO_TSL_HIGH....................................................................................................................A-222
A.2.145 RADIO_TSL_LOW.....................................................................................................................A-223
A.2.146 RELAY_ALARM........................................................................................................................A-224
A.2.147 RP_LOC.......................................................................................................................................A-225
A.2.148 RPS_INDI.....................................................................................................................................A-226
A.2.149 RS_CROSSTR.............................................................................................................................A-228
A.2.150 RTC_FAIL...................................................................................................................................A-229
A.2.151 S1_SYN_CHANGE.....................................................................................................................A-230
A.2.152 SWDL_ACTIVATED_TIMEOUT..............................................................................................A-231
A.2.153 SWDL_AUTOMATCH_INH......................................................................................................A-232
A.2.154 SWDL_COMMIT_FAIL.............................................................................................................A-233
A.2.155 SWDL_CHGMNG_NOMATCH.................................................................................................A-233
A.2.156 SWDL_INPROCESS...................................................................................................................A-234
A.2.157 SWDL_NEPKGCHECK..............................................................................................................A-235
A.2.158 SWDL_PKG_NOBDSOFT..........................................................................................................A-236
A.2.159 SWDL_PKGVER_MM................................................................................................................A-237
A.2.160 SWDL_ROLLBACK_FAIL........................................................................................................A-237
A.2.161 SYN_BAD....................................................................................................................................A-238
A.2.162 SYNC_C_LOS.............................................................................................................................A-239
A.2.163 T_ALOS.......................................................................................................................................A-241
A.2.164 T_F_RST......................................................................................................................................A-242
A.2.165 T_LOC..........................................................................................................................................A-243
A.2.166 T_LOS..........................................................................................................................................A-244
A.2.167 TEMP_ALARM...........................................................................................................................A-246
A.2.168 TU_AIS........................................................................................................................................A-248
A.2.169 TU_AIS_VC12.............................................................................................................................A-250
A.2.170 TU_AIS_VC3...............................................................................................................................A-252
A.2.171 TU_LOP.......................................................................................................................................A-254
A.2.172 TU_LOP_VC12............................................................................................................................A-255
A.2.173 TU_LOP_VC3..............................................................................................................................A-257
A.2.174 UP_E1_AIS..................................................................................................................................A-259
A.2.175 VCAT_LOA.................................................................................................................................A-260
A.2.176 VCAT_LOM_VC12.....................................................................................................................A-261
A.2.177 VCAT_LOM_VC3.......................................................................................................................A-263
A.2.178 VCAT_SQM_VC12.....................................................................................................................A-265
A.2.179 VCAT_SQM_VC3.......................................................................................................................A-266
Issue 01 (2009-12-30) Huawei Proprietary and Confidential xiii

OptiX RTN 620
A.2.180 VOLT_LOS..................................................................................................................................A-267
A.2.181 W_R_Failure................................................................................................................................A-270
A.2.182 WRG_BD_TYPE.........................................................................................................................A-270
A.2.183 WRG_DEV_TYPE.......................................................................................................................A-272
A.2.184 WS_LOS.......................................................................................................................................A-272
A.2.185 XCP_INDI....................................................................................................................................A-274
A.2.186 XPIC_LOS...................................................................................................................................A-275
B Abnormal Event Reference.....................................................................................................B-1

B.1 Important Abnormal Events...........................................................................................................................B-2
B.2 Important Abnormal Events and Handling Procedures.................................................................................B-2
B.2.1 IF 1+1 Protection Switching.................................................................................................................B-3
B.2.2 N+1 Protection Switching.....................................................................................................................B-5
B.2.3 SDH SNCP Protection Switching.........................................................................................................B-7
B.2.4 Ring MS Switching...............................................................................................................................B-8
B.2.5 Linear MS Switching..........................................................................................................................B-10
B.2.6 Cross-Connect and Timing Board Switching.....................................................................................B-12
B.2.7 ERPS Protection Switching................................................................................................................B-14
B.2.8 RMON Performance Value Below the Lower Limit..........................................................................B-15
B.2.9 RMON Performance Value Above the Upper Limit..........................................................................B-16
C Performance Event Reference................................................................................................C-1

C.1 Performance Event List..................................................................................................................................C-2
C.1.1 SDH/PDH Performance Events............................................................................................................C-2
C.1.2 Microwave Performance Events...........................................................................................................C-7
C.1.3 Other Performance Events....................................................................................................................C-9
C.2 Performance Events and Handling Procedures............................................................................................C-11
C.2.1 AUPJCHIGH, AUPJCLOW, and AUPJCNEW.................................................................................C-11
C.2.2 ATPC_P_ADJUST and ATPC_N_ADJUST.....................................................................................C-12
C.2.3 TUPJCHIGH, TUPJCLOW, and TUPJCNEW..................................................................................C-12
C.2.4 RSBBE, RSES, RSSES, RSCSES, and RSUAS................................................................................C-13
C.2.5 RSOOF and RSOFS............................................................................................................................C-15
C.2.6 MSBBE, MSES, MSSES, MSCSES, and MSUAS............................................................................C-16
C.2.7 MSFEBBE, MSFEES, MSFESES, MSFECSES, and MSFEUAS.....................................................C-17
C.2.8 HPBBE, HPES, HPSES, HPCSES, and HPUAS...............................................................................C-18
C.2.9 HPFEBBE, HPFEES, HPFESES, HPFECSES, and HPFEUAS........................................................C-20
C.2.10 IF_BBE, IF_ES, IF_SES, IF_CSES, and IF_UAS...........................................................................C-21
C.2.11 VC3BBE, VC3ES, VC3SES, VC3CSES, and VC3UAS.................................................................C-22
C.2.12 VC3FEBBE, VC3FEES, VC3FESES, VC3FECSES, and VC3FEUAS..........................................C-23
C.2.13 LPBBE, LPES, LPSES, LPCSES, and LPUAS................................................................................C-24
C.2.14 LPFEBBE, LPFEES, LPFESES, LPFECSES, and LPFEUAS........................................................C-26
C.2.15 E3_LCV_SDH, E3_LES_SDH, and E3_LSES_SDH......................................................................C-27
C.2.16 T3_LCV_SDH, T3_LES_SDH, and T3_LSES_SDH......................................................................C-28
C.2.17 TSL_MAX, TSL_MIN, TSL_CUR, and TSL_AVG.......................................................................C-29
xiv Huawei Proprietary and Confidential Issue 01 (2009-12-30)

OptiX RTN 620
C.2.18 RSL_MAX, RSL_MIN, RSL_CUR, and RSL_AVG......................................................................C-29

C.2.19 RLHTT, RLLTT, TLHTT, and TLLTT............................................................................................C-30
C.2.20 ACMDOWNCNT and ACMUPCNT...............................................................................................C-30
C.2.21 FEC_BEF_COR_ER, FEC_COR_BYTE_CNT, and FEC_UNCOR_BLOCK_CNT.....................C-31
C.2.22 QPSKWS, QAMWS16, QAMWS32, QAMWS64, QAMWS128, and QAMWS256.....................C-32
C.2.23 TPLMAX, TPLMIN, and TPLCUR.................................................................................................C-33
C.2.24 RPLMAX, RPLMIN, and RPLCUR................................................................................................C-34
C.2.25 BDTMPMAX, BDTMPMIN, and BDTMPCUR.............................................................................C-34
C.2.26 OSPITMPMAX, OSPITMPMIN, and OSPITMPCUR....................................................................C-35
D RMON Event Reference.........................................................................................................D-1

D.1 List of RMON Alarm Entries........................................................................................................................D-2
D.2 List of RMON Performance Entries..............................................................................................................D-2
D.3 RMON Alarm Clearance Reference..............................................................................................................D-6
D.3.1 DropEvent.............................................................................................................................................D-6
D.3.2 UndersizePkts.......................................................................................................................................D-7
D.3.3 OversizePkts.........................................................................................................................................D-8
D.3.4 Fragments.............................................................................................................................................D-9
D.3.5 Jabbers................................................................................................................................................D-10
D.3.6 FCSErrors...........................................................................................................................................D-10
E Alarm Management..................................................................................................................E-1
E.1 NE Alarm Management..................................................................................................................................E-2
E.2 Board Alarm Management.............................................................................................................................E-2
E.2.1 Setting the Alarm Severity....................................................................................................................E-3
E.2.2 Alarm Suppression................................................................................................................................E-3
E.2.3 Alarm Auto-Report................................................................................................................................E-3
E.2.4 Alarm Reversion....................................................................................................................................E-3
E.2.5 Setting of the Bit Error Alarm Threshold..............................................................................................E-4
E.2.6 AIS Insertion.........................................................................................................................................E-4
E.2.7 UNEQ Insertion.....................................................................................................................................E-6
F Performance Event Management............................................................................................F-1

F.1 NE Performance Event Management.............................................................................................................F-2
F.2 Board Performance Event Management.........................................................................................................F-2
G Alarm Suppression Relationship.........................................................................................G-1

H Glossary.....................................................................................................................................H-1
I Acronyms and Abbreviations...................................................................................................I-1
Issue 01 (2009-12-30) Huawei Proprietary and Confidential xv

OptiX RTN 620
Maintenance Guide Figures
Figures
Figure 1-1 Wearing an ESD wrist strap...............................................................................................................1-3

Figure 2-1 Toggle lever switch............................................................................................................................2-2
Figure 4-1 Main procedure of emergency maintenance.......................................................................................4-3
Figure 4-2 Procedure of on-site fault handling.....................................................................................................4-6
Figure 5-1 General fault locating procedures.......................................................................................................5-4
Figure 5-2 Flow of handling a service interruption..............................................................................................5-6
Figure 5-3 Procedure of on-site fault handling.....................................................................................................5-8
Figure 5-4 Flow of handling radio link faults....................................................................................................5-15
Figure 5-5 Flow of handling bit errors...............................................................................................................5-22
Figure 5-6 Flow of troubleshooting the interconnection with the SDH equipment...........................................5-26
Figure 5-7 Flow of troubleshooting the interconnection with the PDH equipment...........................................5-29
Figure 5-8 Flow of handling Ethernet service faults..........................................................................................5-32
Figure 5-9 Flow of handling RMON abnormal performance events.................................................................5-35
Figure 5-10 Flow of handling an Ethernet service fault.....................................................................................5-38
Figure 5-11 Flow of handling an abnormal RMON performance event............................................................5-41
Figure 5-12 Flow of handling pointer justifications...........................................................................................5-45
Figure 5-13 Flow of handling orderwire faults..................................................................................................5-48
Figure 6-1 Removing a board (1).........................................................................................................................6-4
Figure 6-2 Removing a board (2) ........................................................................................................................6-4
Figure 6-3 Removing a board (3).........................................................................................................................6-5
Figure 6-4 Inserting a board (1)...........................................................................................................................6-5
Figure 6-7 Positions of the jumpers and storage card........................................................................................6-15
Figure 6-8 Removing a Storage Card.................................................................................................................6-17
Figure 6-9 Installing a Storage Card..................................................................................................................6-18
Figure 6-10 Removing the front panel of the fan tray........................................................................................6-20
Figure 6-11 Removing the fan tray....................................................................................................................6-20
Figure 7-1 CLETOP cassette cleaner...................................................................................................................7-4
Figure 7-2 Dragging the fiber tip slightly on one cleaning area...........................................................................7-4
Figure 7-3 Dragging the fiber tip slightly on the other cleaning area..................................................................7-5
Figure 7-4 Cleaning the fiber with the lens tissue ...............................................................................................7-6
Figure 7-5 Inloop................................................................................................................................................7-18
Issue 01 (2009-12-30) Huawei Proprietary and Confidential xvii

OptiX RTN 620
Figures Maintenance Guide
Figure 7-6 Outloop.............................................................................................................................................7-18

Figure 7-7 VC-4 path outloop............................................................................................................................7-18
Figure 7-8 VC-4 path inloop..............................................................................................................................7-19
Figure 7-9 Inloop................................................................................................................................................7-20
Figure 7-10 Outloop...........................................................................................................................................7-20
Figure 7-11 VC-4 path outloop..........................................................................................................................7-20
Figure 7-12 Inloop..............................................................................................................................................7-22
Figure 7-13 Outloop...........................................................................................................................................7-22
Figure 7-14 Inloop..............................................................................................................................................7-23
Figure 7-15 Outloop...........................................................................................................................................7-23
Figure 7-16 Inloop..............................................................................................................................................7-24
Figure 7-17 Outloop...........................................................................................................................................7-24
Figure 7-18 VC-4 path inloop............................................................................................................................7-24
Figure 7-19 Inloop..............................................................................................................................................7-26
Figure 7-20 VC-3 path inloop............................................................................................................................7-26
Figure 7-21 VC-3 path outloop..........................................................................................................................7-26
Figure 7-22 Service Trail...................................................................................................................................7-28
Figure 7-23 PRBS test in the tributary direction................................................................................................7-31
Figure 7-24 PRBS test in the cross-connect direction........................................................................................7-32
Figure 7-25 Ethernet test frames between Ethernet boards................................................................................7-39
xviii Huawei Proprietary and Confidential Issue 01 (2009-12-30)

OptiX RTN 620
Maintenance Guide Tables
Tables
Table 4-1 Description of the main procedure of emergency maintenance...........................................................4-4

Table 4-2 Sheet for on-site operations..................................................................................................................4-5
Table 4-3 Procedure of on-site fault handling......................................................................................................4-7
Table 5-1 Flow description...................................................................................................................................5-5
Table 5-2 Flow description...................................................................................................................................5-7
Table 5-3 Procedure of on-site fault handling......................................................................................................5-9
Table 5-4 Causes of radio link faults..................................................................................................................5-12
Table 5-5 Flow description.................................................................................................................................5-16
Table 5-6 Causes of bit errors.............................................................................................................................5-21
Table 5-10 Flow description...............................................................................................................................5-33
Table 6-1 Part replacement description ...............................................................................................................6-1
Table 6-2 Setting the jumpers.............................................................................................................................6-15
Table A-1 Alarm list............................................................................................................................................A-2
Table B-1 Important abnormal events.................................................................................................................B-2
Table C-1 Pointer justification performance events............................................................................................C-2
Table C-2 Regenerator section error performance events...................................................................................C-3
Table C-3 Multiplex section error performance events.......................................................................................C-3
Table C-4 Higher order path error performance events.......................................................................................C-4
Table C-5 VC-3 path error performance events..................................................................................................C-5
Table C-6 Lower order path error performance events.......................................................................................C-6
Table C-7 Line side code violation performance events.....................................................................................C-6
Table C-8 Microwave power performance events...............................................................................................C-7
Table C-9 FEC performance events....................................................................................................................C-8
Table C-10 Performance events regarding radio link bit errors..........................................................................C-8
Table C-11 ATPC performance events................................................................................................................C-9
Issue 01 (2009-12-30) Huawei Proprietary and Confidential xix

OptiX RTN 620
Tables Maintenance Guide
Table C-12 AM performance events...................................................................................................................C-9

Table C-13 Performance events regarding optical power.................................................................................C-10
Table C-14 Performance events regarding board temperature..........................................................................C-10
Table C-15 Performance events regarding temperature of a laser core.............................................................C-10
Table D-1 List of RMON alarm entries...............................................................................................................D-2
Table D-2 List of RMON performance entries....................................................................................................D-2
Table E-1 Setting of the bit error alarm threshold...............................................................................................E-4
Table E-2 Setting of the AIS insertion.................................................................................................................E-5
Table E-3 Setting of the UNEQ insertion............................................................................................................E-6
Table F-1 Board performance event management function.................................................................................F-2
Table G-1 Suppression relationship between intra-board alarms........................................................................G-1
Table G-2 Suppression relationship between inter-board alarms........................................................................G-2
xx Huawei Proprietary and Confidential Issue 01 (2009-12-30)

OptiX RTN 620
Maintenance Guide 1 Safety Precautions
1 Safety Precautions
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
l 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.
l 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.
Issue 01 (2009-12-30) Huawei Proprietary and Confidential 1-1

OptiX RTN 620
1 Safety Precautions Maintenance Guide
l Do not wear conducting articles, such as watches, chains, bracelets and rings while
performing high voltage operations.
l Switch off the power supply immediately if you find water in the rack or if the rack is damp.
l 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.
l During high voltage and AC operations, special tools must be used instead of common tools.
l Before installing or removing the power cable, turn off the power switch.
l 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 Huawei Proprietary and Confidential Issue 01 (2009-12-30)

OptiX RTN 620
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

OptiX RTN 620
1 Safety Precautions Maintenance Guide
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.
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.

l The operating machines and tools should be carried and handled safely to prevent them
from falling.
l Safety measures, such as wearing a helmet and a safety belt, should be taken.
l In cold areas, warm clothes must be worn before performing any high-altitude operation.
l 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 power switch on the IF board.

OptiX RTN 620
Installing and Removing Boards
CAUTION
l When inserting a board, handle it gently to avoid distorting the pins on the backplane.
l 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.
l 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.

OptiX RTN 620
Maintenance Guide 2 Guides to High-Risk Operations
2 Guides to High-Risk Operations
About This Chapter
This topic describes the operations that easily cause human body injuries and equipment damage
in the process of commissioning and maintenance.
2.1 Operation Guide to a Toggle Lever Switch

The ODU-PWR switch and the SYS-PWR switch are toggle lever switches. When you turn on
or turn off the toggle lever switch, perform the operations in strict compliance with the guidelines.
Otherwise, the IF board or the power board may be damaged.
2.2 Operation Guide to IF Jumpers
Before removing or installing an IF jumper, turn off the ODU-PWR switch. Otherwise, human
body injuries may be caused, and the IF board or the ODU may be damaged.
2.3 Operation Guide to IF Cables
Before removing or installing an IF cable, turn off the ODU-PWR switch. Otherwise, human
2.4 Operation Guide to IF Boards
Before removing or installing an IF board, turn off the ODU-PWR switch. Otherwise, the IF
board or the ODU may be damaged.

OptiX RTN 620
2 Guides to High-Risk Operations Maintenance Guide
2.1 Operation Guide to a Toggle Lever Switch

The ODU-PWR switch and the SYS-PWR switch are toggle lever switches. When you turn on
or turn off the toggle lever switch, perform the operations in strict compliance with the guidelines.
Otherwise, the IF board or the power board may be damaged.
Position and Description of the Toggle Lever Switch

A toggle lever switch is used on the power board or IF board to control the power supply to the
IDU or ODU. as shown in Figure 2-1.
Figure 2-1 Toggle lever switch
O:OFF
I:ON
Turning On the Toggle Lever Switch

OptiX RTN 620
1. Pull the toggle lever switch out slightly.

2. Turn it to the left.
3. Release the toggle lever switch.
Turning Off the Toggle Lever Switch
1. Pull the toggle lever switch out slightly.

2. Turn it to the right.
3. Release the toggle lever switch.
2.2 Operation Guide to IF Jumpers

Before removing or installing an IF jumper, turn off the ODU-PWR switch. Otherwise, human
Procedure
Step 1 Turn off the ODU power switch on the IF board. For details, see 2.1 Operation Guide to a
Toggle Lever Switch.

OptiX RTN 620
1 2
DANGER
Do not remove any IF jumper before the ODU is powered off!
Step 2 Remove or install an IF jumper.
----End
2.3 Operation Guide to IF Cables

Before removing or installing an IF cable, turn off the ODU-PWR switch. Otherwise, human
Procedure

OptiX RTN 620
1 2
DANGER
Do not remove any IF cable before the ODU is powered off!
Step 2 Install or remove an IF cable.
----End
2.4 Operation Guide to IF Boards

Before removing or installing an IF board, turn off the ODU-PWR switch. Otherwise, the IF
board or the ODU may be damaged.
Procedure

OptiX RTN 620
1 2 3
DANGER
Do not remove or install any IF board before the ODU is powered off!
Step 2 Disconnect the IF jumper or IF cable.

Step 3 Remove or install an IF board.
----End

OptiX RTN 620
Maintenance Guide 3 Routine Maintenance
3 Routine Maintenance
About This Chapter
The aim of routine maintenance is to detect and rectify latent faults in time before the equipment
becomes faulty and services are affected.
3.1 Routine Maintenance Items

Routine maintenance items are classified into the routine maintenance items carried out through
the network management system (NMS), field maintenance items for indoor equipment, and
field maintenance items for outdoor equipment.
3.2 Guidelines for Routine Maintenance Items
This topic describes the guidelines for each routine maintenance item.

OptiX RTN 620
3 Routine Maintenance Maintenance Guide
3.1 Routine Maintenance Items

Routine maintenance items are classified into the routine maintenance items carried out through
the network management system (NMS), field maintenance items for indoor equipment, and
field maintenance items for outdoor equipment.
Routine Maintenance Items Carried Out Through the NMS

Maintenance Item Recomm Remarks
ended
Cycle
3.2.1 Checking the Status of NEs Every day -
3.2.2 Browsing the Current Alarms Every day -
3.2.3 Browsing the History Alarms Every -

week
3.2.4 Browsing the Abnormal Events Every -

week
3.2.5 Browsing the Current Every -

Performance week
3.2.6 Browsing the History Every -

Performance week
3.2.7 Browsing the History Transmit Every -

Power and Receive Power week
3.2.8 Testing IF 1+1 Switching Half a Applies to only the equipment that is
year configured in 1+1 protection mode.
During the 1+1 protection switching
time (<500 ms), the protected services
are interrupted. Hence, it is
recommended that you perform 1+1
protection switching when the traffic
is light.
3.2.9 Testing IF N+1 Switching Half a Applies to only the equipment that is
year configured in N+1 protection mode.
3.2.10 Testing Two-Fiber Half a -

Bidirectional MSP Ring Switching year
Field Maintenance Items for Indoor Equipment

Maintenance Item Recommended Cycle Remarks
3.2.11 Cleaning the Air Every two months -

Filter

OptiX RTN 620
Maintenance Item Recommended Cycle Remarks
3.2.12 Checking the Every two months -

Equipment Room
Field Maintenance Items for Outdoor Equipment

Maintenance Item Recommended Remarks
Cycle
3.2.13 Checking the ODU Half a year Perform a

complete check
3.2.14 Checking the Hybrid Coupler Half a year after a level-8 or
3.2.15 Checking the Antenna Half a year higher-level
hurricane, an
3.2.16 Checking the IF Cables Half a year earthquake, or
other exceptional
3.2.17 Checking the LOS Condition Half a year circumstances.
3.2 Guidelines for Routine Maintenance Items

This topic describes the guidelines for each routine maintenance item.
3.2.1 Checking the Status of NEs

By checking the NE status periodically, you can detect the abnormal statuses of one or more
NEs in time.
3.2.2 Browsing the Current Alarms
A current alarm refers to an alarm that is not cleared. By browsing the current alarms periodically,
you can detect and rectify faults in time.
3.2.3 Browsing the History Alarms
A history alarm is an alarm that is cleared. Periodically browsing and storing the history alarm
information helps in locating and rectifying faults.
3.2.4 Browsing the Abnormal Events
An abnormal event refers to an exception that arises in the system at a particular time. By
browsing the abnormal events periodically, you can find the exceptions that occur in the
equipment in time.
3.2.5 Browsing the Current Performance
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. By browsing the current
performance events periodically, you can learn about the performance change of the equipment
in time. Hence, you can detect the latent hazards in time when the performance of the equipment
starts to degrade.
3.2.6 Browsing the History Performance
A history alarm is an alarm that is cleared. By browsing and saving the history performance
events periodically, you can provide fault locating information for troubleshooting.

OptiX RTN 620
3.2.7 Browsing the History Transmit Power and Receive Power

By browsing the history transmit power and receive power periodically, you can learn about the
change trend of the transmit power and receive power, which provides a reference for
troubleshooting radio links.
3.2.8 Testing IF 1+1 Switching
By testing IF 1+1 switching periodically, you can check whether the equipment is normally
switched over.
3.2.9 Testing IF N+1 Switching
By testing IF N+1 switching periodically, you can check whether the equipment is normally
switched over.
3.2.10 Testing Two-Fiber Bidirectional MSP Ring Switching
By testing two-fiber bidirectional MSP ring switching periodically, you can check whether the
equipment is normally switched over.
3.2.11 Cleaning the Air Filter
Periodically checking the air filter ensures that the air intake path of the fans is not blocked and
thus prevents excessively high board temperature caused by degraded heat dissipation.
3.2.12 Checking the Equipment Room
Periodically checking the equipment room not only ensures that the equipment can operate
normally at appropriate temperature and humidity conditions, but also reduces the fault rate, and
increases the service life of the equipment.
3.2.13 Checking the ODU
By checking an ODU periodically, you can detect faults and latent hazards of the ODU in time.
3.2.14 Checking the Hybrid Coupler
By checking a hybrid coupler periodically, you can detect faults and latent hazards of the hybrid
coupler in time.
3.2.15 Checking the Antenna
By checking an antenna periodically, you can detect faults and latent hazards of the antenna in
time.
3.2.16 Checking the IF Cables
By checking the IF cables periodically, you can detect faults and latent hazards of the IF cables
in time.
3.2.17 Checking the LOS Condition
By checking the LOS condition of the transmission link periodically, you can detect latent LOS
faults on the transmission link in time.
3.2.1 Checking the Status of NEs

By checking the NE status periodically, you can detect the abnormal statuses of one or more
NEs in time.
Prerequisite
The NE user must have the authority of NE monitor or higher.
Tools, Instruments, and Materials

Web LCT

OptiX RTN 620
Procedure
Step 1 In NE List, query Communication Status of an NE. Communication Status needs to be
Normal.
Step 2 Check Login Status of an NE. If the Login Status column of an NE is Not Logged In, log in
to the NE.
1. Select an NE, and then click NE Login.
The NE Login dialog box is displayed.
2. Enter a user name in User Name and a password in Password.
l The user name is lct by default.
l The password for the user lct is password by default.
NOTE
The user lct has the authority at the system level.

3. Click OK.
After you log in to the NE successfully, Login Status in NE List changes to Logged In.
----End

A current alarm refers to an alarm that is not cleared. By browsing the current alarms periodically,
you can detect and rectify faults in time.
Prerequisite

Web LCT
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree, and then click the icon on
the toolbar.
TIP
You can also click an alarm indicator on the toolbar to display the alarms of the specific severity.
From left to right, the alarm indicators and corresponding alarm severities are as follows:
l Red: critical alarm
l Orange: major alarm
l Yellow: minor alarm
l Purple: warning
l Light blue: abnormal event
The Browse Current Alarms tab is displayed by default.

OptiX RTN 620
Step 2 Browse the displayed alarms.
Step 3 If there are newly generated alarms after the last maintenance, select the newly generated alarms,
record the details of these newly generated alarms, and then notify the troubleshooting personnel
to clear these alarms in time.
For details about how to handle an alarm, refer to A Alarm Reference.
Step 4 Optional: Click Save As.
A text file that lists the current alarms is displayed in the IE system.
NOTE
You can save and archive the text file as required.
----End
3.2.3 Browsing the History Alarms

A history alarm is an alarm that is cleared. Periodically browsing and storing the history alarm
information helps in locating and rectifying faults.
Prerequisite

Web LCT
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree, and then click the icon on
the toolbar.
Step 2 Click the Browse History Alarms tab.
Step 3 Click Filter.

The Filter dialog box is displayed.
Step 4 Specify Rising Time and Cleared Time, and then click Filter.
The time span starts from the time when the last history alarm browsing operation was performed
to the current time.
Step 5 Browse the filtered history alarms.
Step 6 Click Save As.
A text file that lists the history alarms is displayed in the IE system.
NOTE
----End

OptiX RTN 620

An abnormal event refers to an exception that arises in the system at a particular time. By
browsing the abnormal events periodically, you can find the exceptions that occur in the
equipment in time.
Prerequisite

Web LCT
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree, and then choose Alarm >
Browse Abnormal Events from the Function Tree.
TIP
In the NE Explorer, you can also select the required NE from the Object Tree and click the icon to
navigate to the Browse Abnormal Events tab.

The Filter dialog box is displayed.
Step 3 In the Abnormal Event combo box, select Select All, and then click OK.
Step 4 Browse the displayed abnormal events.
For details on how to handle an abnormal event, see B Abnormal Event Reference.
A text file that lists the abnormal events is displayed in the IE system.
NOTE
----End
Related Information
An abnormal event refers to an exception that arises in the system at a particular time rather than
persists for a period. Being different from alarms, an abnormal event has the occurrence time
rather than the clearance time.
3.2.5 Browsing the Current Performance

between the start time of the monitoring period and the current time. By browsing the current
performance events periodically, you can learn about the performance change of the equipment
in time. Hence, you can detect the latent hazards in time when the performance of the equipment
starts to degrade.

OptiX RTN 620
Prerequisite
l The performance monitoring function of the NE must be enabled. For details about how to
enable the performance monitoring function, see 7.13 Configuring Performance
Monitoring Status of NEs.
l The NE user must have the authority of NE monitor or higher.

Web LCT
Procedure
Step 1 In the NE Explorer, select the required board, and then choose Performance > Current
Performance from the Function Tree.
Step 2 Select All in Monitored Object Filter Condition.
Step 3 Select 15-Minute next to Monitor Period.
Step 4 Select all the available performance events in Count, and select Consecutive Severely Errored
Second in Display Options.
Step 5 Click Query.
Step 6 Browse the displayed performance events.

In normal cases, no bit error performance events are displayed, and the number of pointer
justification events is 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 Query.
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 next to Monitor Period.
Step 11 Repeat Step 4 to Step 9 to query the current performance events in a period of 24 hours.
----End

A history alarm is an alarm that is cleared. By browsing and saving the history performance
events periodically, you can provide fault locating information for troubleshooting.
Prerequisite

OptiX RTN 620

Web LCT
Procedure
Step 1 In the NE Explorer, select the requried board, and then choose Performance > History
Step 4 Specify the start time and the 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.
Step 6 Click Query to browse the history performance events.
A text file that lists the history performance events is displayed in the IE system.
NOTE
NOTE
Step 12 Repeat Step 4 to Step 10 to query the history performance events in a period of 24 hours.
----End
3.2.7 Browsing the History Transmit Power and Receive Power

By browsing the history transmit power and receive power periodically, you can learn about the
change trend of the transmit power and receive power, which provides a reference for
troubleshooting radio links.

OptiX RTN 620
Prerequisite

Web LCT
Procedure
Step 1 In the NE Explorer, select the required ODU for the history transmit power and receive power
from the Object Tree, and then choose Configuration > Performance Graph Analyse from
the Function Tree.
Step 2 Specify the start time and end time of a time span.
The time span starts from the last routing maintenance time to the current time.
Step 3 Set CounterType to 15M.
Step 4 Click Drawing.

The history transmit and receive power curve of the ODU in the specified time span is displayed.
Step 5 Analyze the power curve. If the receive power fading of two adjacent points exceeds 20 dB, but
the weather does not change, contact the troubleshooting engineers.
----End
3.2.8 Testing IF 1+1 Switching

By testing IF 1+1 switching periodically, you can check whether the equipment is normally
switched over.
Prerequisite

Web LCT
Precautions
l This task carries out IF 1+1 switching in manual switching mode, which is used for
equipment switching (that is, HSB switching). During the 1+1 protection switching time
(< 500 ms), the protected services are interrupted. Hence, it is recommended that you
perform IF 1+1 protection switching when the traffic is light.
l Before you perform the switching, ensure that the standby equipment works properly. If
the switching fails, contact Huawei engineers for further assistance.

OptiX RTN 620
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree, and then choose
Configuration > Link Configuration from the Function Tree.
Step 2 Click the IF 1+1 Protection tab.
Step 3 In Protection Group, select the protection group for IF 1+1 switching.
Step 4 In Slot Mapping Relation, right-click an IF board and choose Manual Switch to from the
shortcut menu.
Step 5 Click OK to start the protection switching.
Step 6 Click Query to check the protection switching status.

After the switching is completed, Switching Status of Device in Protection Group changes to
Manual Switching, and the current board functions as the standby board.
Step 7 After the equipment works for a period of time, query the current alarms and performance events
of the service.
There should be no new alarms or bit error performance events.
Step 8 Repeat Step 1 to Step 3.
Step 9 In Slot Mapping Relation, right-click an IF board and choose Clear from the shortcut menu.
Step 10 Click OK to restore the protection switching.
Step 11 Click Query to check the protection switching status.

After the switching is completed, Switching Status of Device in Protection Group changes to
Automatic Switching.
Step 12 After the equipment runs properly for a period of time, query the current alarms and performance
events.
There should be no new alarms or performance events.
----End
3.2.9 Testing IF N+1 Switching

By testing IF N+1 switching periodically, you can check whether the equipment is normally
switched over.
Prerequisite

Web LCT
Precautions
l This task carries out IF N+1 switching in exercise switching mode to check whether an NE
can run the N+1 protocol properly. Therefore, the service is not switched over.

OptiX RTN 620
l Before you perform the switching, ensure that the standby equipment works properly. If
the switching fails, contact Huawei engineers for further assistance.
Procedure
Configuration > Link Configuration from the Function Tree.
Step 2 Click the N+1 Protection tab.
Step 3 In the Slot Mapping Relation window, right-click a working unit, and then choose Exercise
Switching from the shortcut menu.
A prompt dialog box is displayed, indicating that the command is delivered successfully.
Step 4 Click OK.
Step 5 Click Query to query the status of protection switching.

The status of the switched working unit should be Exercise Switching.
Step 7 In the Slot Mapping Relation window, right-click a protection or working unit, and then choose
Clear from the shortcut menu.
Step 8 Click OK.
Step 9 Click Query to query the status of protection switching.

The status of the switched working unit should be Normal.
----End
3.2.10 Testing Two-Fiber Bidirectional MSP Ring Switching

By testing two-fiber bidirectional MSP ring switching periodically, you can check whether the
equipment is normally switched over.
Prerequisite

Web LCT
Precautions
l This task carries out two-fiber bidirectional MSP ring switching in exercise switching mode
to check whether an NE can run the MSP protocol properly. Therefore, the service is not
switched over.
l Before you perform MSP ring switching, ensure that the standby equipment works properly.
If the switching fails, contact Huawei engineers for further assistance.

OptiX RTN 620
Procedure
Configuration > Ring MS from the Function Tree.
Step 2 In Protection Group, select the protection group for exercise switching.
Step 3 In Slot Mapping Relation, right-click East Line and choose Ring Exercise from the shortcut
menu.
Step 4 Click Query to query the protection switching status. Switching Status of the east line board
changes to Excise Ring Switching.
Step 5 Select and right-click the line direction for exercise switching and choose Clear Ring
Exercise from the shortcut menu.
Step 6 Click Query to query the protection switching status. Switching Status of the east line board
changes to Normal.
Step 7 In Slot Mapping Relation, right-click West Line of the selected protection group in Step 2 and
choose Ring Exercise from the shortcut menu.
----End
3.2.11 Cleaning the Air Filter

Periodically checking the air filter ensures that the air intake path of the fans is not blocked and
thus prevents excessively 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 Tray.
Step 2 Move the cables away from the front of the panel of the fan Tray.
Step 3 Draw out the air filter at the left side.

OptiX RTN 620
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 Tray.
----End
3.2.12 Checking the Equipment Room

Periodically checking the equipment room not only ensures that the equipment can operate
normally at 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 ranges from -5℃ to +55℃
Step 2 Record the reading of the humidity meter in the equipment room.
The normal humidity ranges from 5% to 95%.
Step 3 Check whether the equipment room meets the disaster protection requirements.
Ensure the following points:
l Certain portable foam fire extinguishers are available in the equipment room and these
extinguishers need to be within their service life.
l No rain leakage or water penetration is found in the equipment room.
l No mice or insects are found in the equipment room.
Step 4 Clean the equipment room.

Ensure that the cabinets, equipment shelves, equipment, desks, and floors are clean. The
equipment needs to be tidy.
----End
3.2.13 Checking the ODU

By checking an ODU periodically, you can detect faults and latent hazards of the ODU in time.
Prerequisite
None.

OptiX RTN 620

None.
Procedure
Step 1 Ensure that the ODU is located within the protected area of a lightning arrester.
In the case of plain areas, a lightning arrester protects an area that is located within an angle of
45° under the lightning arrester. In the case of mountainous areas and the areas where lightning
frequently occurs, a lightning arrester protects an area that is located within an angle of 30° under
the lightning arrester.
Step 2 Ensure that the ODU is fixed properly 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 grounded firmly and reliably.
----End
3.2.14 Checking the Hybrid Coupler

By checking a hybrid coupler periodically, you can detect faults and latent hazards of the hybrid
coupler in time.
Prerequisite
None.

None.
Procedure
Step 1 Ensure that the hybrid coupler is located within the protected area of the lightning arrester.
45° under the lightning arrester. In the case of mountainous areas and the areas where lightning
frequently occurs, a lightning arrester protects the area that is located within an angle of 30°
under the lightning arrester.
Step 2 Ensure that the coupler is fixed reliably 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
3.2.15 Checking the Antenna

By checking an antenna periodically, you can detect faults and latent hazards of the antenna in
time.

OptiX RTN 620
Prerequisite
None.

None.
Procedure
Step 1 Ensure that the antenna is located within the protected area of the lightning arrester.
45° under lightning arrester. In the case of mountainous areas and the areas where lightning
frequently occurs, a lightning arrester protects an area that is located within an angle of 30° under
the lightning arrester.
Step 2 Ensure that the antenna is fixed reliably 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.
Step 7 Check and ensure that the interface of the feed boom is properly sealed and waterproof.
----End
3.2.16 Checking the IF Cables

By checking the IF cables periodically, you can detect faults and latent hazards of the IF cables
in time.
Prerequisite
None.

None.
Procedure
Step 1 Check the cables.
l No cables are bent or twisted.
l No bare copper wires are found.
l The bending radius of a cable needs to greater than 30 cm.
l The IF cables are bound in accordance with IF Cable Routing and Binding Specifications
specified in the Installation Reference. The feeder clip or binding strap is not loosen.

OptiX RTN 620
Step 2 Check the cable connectors.

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

l The grounding clip needs to be waterproof.
l The grounding cable needs to be routed from top downwards. The angle between the
grounding cable and an IF cable needs to be not more than 15 degrees.
----End
3.2.17 Checking the LOS Condition

By checking the LOS condition of the transmission link periodically, you can detect latent LOS
faults on the transmission link in time.
Prerequisite
None.

Telescope
Procedure
Step 1 Use the telescope to search for the antenna at the opposite end from a location nearby the local
antenna. No buildings or maintains exist on the transmission link, which may block the LOS.
Step 2 Check whether the spanning tree in the transmission path is blocked.
Step 3 Check whether any new buildings exist in the transmission path.
----End

OptiX RTN 620
Maintenance Guide 4 Emergency Maintenance
4 Emergency Maintenance
About This Chapter
Emergency maintenance is performed when emergencies occur or possible emergencies owing

to natural factors may occur during the operation of the equipment.
4.1 Definition of Emergency

In the case of the microwave equipment, an emergency situation is where the microwave services
are interrupted.
4.2 Purposes of Emergence Maintenance
Emergency maintenance is performed to restore the normal operation of a system or a device
rapidly. This is different from troubleshooting, which helps to locate and rectify the faults.
4.3 Procedure of Emergency Maintenance
The procedure of emergency maintenance consists of a main procedure and a sub-procedure that
handles faults on site.

OptiX RTN 620
4 Emergency Maintenance Maintenance Guide
4.1 Definition of Emergency

In the case of the microwave equipment, an emergency situation is where the microwave services
are interrupted.
4.2 Purposes of Emergence Maintenance

Emergency maintenance is performed to restore the normal operation of a system or a device
rapidly. This is different from troubleshooting, which helps to locate and rectify the faults.
4.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.

OptiX RTN 620
Main Procedure of Emergency Maintenance
Figure 4-1 Main procedure of emergency maintenance
Start
1 Is there an Yes
Cancel the operation
incorrect operation?
No
Is there any backup Yes Switch the service to

transmission resource? the backup resource
No
Yes Contact the power

Is the power down
supply engineer
No
Is the service 2
Yes Troubleshoot the
configured with switching failure
protection
No
3
Is there any alarm on Yes
Clear the alarm
the NE?
No
4
Is the Ethernet Yes Troubleshoot the
service interrupted Ethernet service fault
No
Is the Yes Troubleshoot the

interconnection
interconnection fault
faulty?
No
Locate the fault by
performing loopback Proceed to the next No Is the service
step restored?
operations section by section
5 Yes
No Contact Huawei
Is the service restored?
engineers
Yes
6
Check the
troubleshooting result
End

OptiX RTN 620
Table 4-1 Description of the main procedure of emergency maintenance

Comment Description
No.
1 The common incorrect operations are as follows:

l Modifying the data configurations
l Performing loopback operations
l Shutting down the laser
l Muting the ODU
l Changing boards/cables
l Loading software
2 Check the notice issued by associated departments, and check whether there
are any external factors that may cause service faults, such as faults in the
power supply, cables, environment, and terminal equipment (such as
switching devices).
3 See 7.3.1 Checking the NE Status and 7.3.3 Browsing the Current
Alarms.
4 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.
5 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.
6 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 4-2 shows the sheet
for on-site operations.

OptiX RTN 620
Table 4-2 Sheet for on-site operations

Maintained on maintained by
Actual Step Step in the Whole Handling Result Remarks

Procedure

OptiX RTN 620
Procedure of On-Site Fault Handling
Figure 4-2 Procedure of on-site fault handling
Start
Obvious Yes
equipment Repair or replace
damage? the equipment
No
1
Is the PWR indicator No Troubleshoot the
on the PXC on? power input
2 Yes
Browse alarms
locally by using the
Web LCT
3 Yes
Equipment
Clear the alarm
alarm?
No
4 Yes
Radio link Clear the alarm
alarm?
No
5 High order Yes
Clear the alarm
path alarm?
No
6 Low order Yes
Clear the alarm
path alarm?
No
Faulty inter- 7
Yes
connection with SDH/ Clear the alarm
PDH equipment?
8
Ethernet Yes
Clear the alarm
service fault?
No
Locate the fault by
Proceed to the next No Is the service
performing loopback
operations section by step restored?
section
Yes
End

OptiX RTN 620
Table 4-3 Procedure of on-site fault handling

Comment Description
No.
1 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 the topic of
"Powering On the Equipment" in the Commissioning Guide.

1. Refer to the Commissioning Guide and Connecting the Web LCT to the
IDU.
2. Refer to the Configuration Guide and Creating NEs by Using the Search
Method.
3. Refer to Commissioning Guide, and Checking 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 IDU Hardware Description.
3 Pay special attention to the following alarms:

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

OptiX RTN 620
Comment Description
No.

l MW_LIM
l MW_LOF
l R_LOS
l R_LOF
l R_LOC
l MS_AIS
l AU_AIS
l AU_LOP
l B1_EXC
l B2_EXC

l HP_LOM
l B3_EXC
l HP_UNEQ

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

5.6 Troubleshooting the Interconnection with the PDH Equipment.
8 See 5.7 Troubleshooting SDH/PDH Radio-Based Ethernet Service

Faults or 5.8 Troubleshooting Faults in Hybrid Radio-Based Ethernet
Services.

OptiX RTN 620
Maintenance Guide 5 Troubleshooting
5 Troubleshooting
About This Chapter
This guide describes the general troubleshooting procedures for the OptiX RTN 620 and provides
troubleshooting methods for common faults.
5.1 General Troubleshooting Procedure

When handling a fault, make a detailed record of the fault phenomenon. The customers in China
can contact our 24-hour technical support center at 400-830-2118, and the customers in areas
5.2 Troubleshooting Service Interruption
The service interruption fault indicates the service transmission failure due to an equipment fault
or a link fault.
5.3 Troubleshooting Radio Links
When an NE reports MW_LOF or MW_FEC_UNCOR due to failure or performance
degradation of a radio link, there is a radio link fault.
5.4 Troubleshooting Bit Errors in TDM Services
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.
5.5 Troubleshooting the Interconnection with the SDH Equipment
In the case that the NE is interconnected with the SDH equipment, if the SDH service cannot be
transmitted between the equipment sets, there is an interconnection fault.
5.6 Troubleshooting the Interconnection with the PDH Equipment
In the case that the OptiX RTN equipment is interconnected with the PDH equipment, if the
PDH service cannot be transmitted between the equipment sets, there is an interconnection fault.
5.7 Troubleshooting SDH/PDH Radio-Based Ethernet Service Faults
EoS/EoPDH-based Ethernet services can be transmitted through SDH/PDH radio networks or
TDM networks. The associated service faults include Ethernet service interruption and Ethernet
service degradation.
5.8 Troubleshooting Faults in Hybrid Radio-Based Ethernet Services
Hybrid radio-based Ethernet services can be transmitted over Hybrid radio networks but cannot
traverse a TDM network. The associated faults include Ethernet service interruption and Ethernet

OptiX RTN 620
5 Troubleshooting Maintenance Guide
5.9 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.
5.10 Troubleshooting Orderwire Faults
If orderwire calls cannot get through when services are normal, there is an orderwire fault.

OptiX RTN 620
5.1 General Troubleshooting Procedure

When handling a fault, make a detailed record of the fault phenomenon. The customers in China
can contact our 24-hour technical support center at 400-830-2118, and the customers in areas

OptiX RTN 620
Figure 5-1 General fault locating procedures
Start
Record the fault phenomenon
2 Yes
Caused by external factors? Other handling procedures
3 No
Analyze fault causes and locate
the fault
Is the fault cleared? Yes
4 No
Report to Huawei
Make a solution together
Attempt to clear the fault
No
Is the service restored?
Yes
Observe the operating
No
Is the fault cleared?
Yes
Fill in the fault handling report
End

OptiX RTN 620
Table 5-1 Flow description

Note Description
1 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 performed
before and after the fault occurs. Save the
alarms, performance events, and other
important information.
2 Check the notice issued by associated

departments, and check whether there are any
external factors that may cause service faults,
such as faults in the power supply, cables,
environment, and terminal equipment (such
as switching devices).
3 If the fault is caused by the equipment, refer

to 5.2 Troubleshooting Service
Interruption.
4 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.
5.2 Troubleshooting Service Interruption

The service interruption fault indicates the service transmission failure due to an equipment fault
or a link fault.
Fault Causes
l The operation is improper.
If the configuration data changes, the loopback occurs, or the board/cable is replaced, the
services may be interrupted.
l The transmission NE or link is faulty.
l The interconnection is improper.
If the transmission equipment functions properly and the connection is proper, check
whether the interconnection between the transmission equipment is proper and whether the
switching equipment is faulty.
Fault Locating Methods

1. Check whether an abnormal operation causes the service interruption by performing a
loopback on the previous operations.
2. Query alarms on the centralized NMS or the NMS on the site, and then locate the fault
based on the alarm analysis.

OptiX RTN 620
If multiple nodes report the alarm, analyze the alarms reported by the nodes in the sequence
of equipment alarms, line alarms, higher order path alarms, and lower order path alarms.
3. If the fault cannot be located through the alarm analysis method, locate the fault by loopback
section by section and part replacement.
CAUTION
If the fault cannot be rectified immediately, focus on the service recovery. You can recover the
services by adjusting the service route or performing forced switching as soon as possible.
Fault Locating Procedure
Figure 5-2 Flow of handling a service interruption
Start
1
Yes
Maloperation Cancel the operation
No
2
Yes Contact related
Service interrupted
departments to
by external causes?
handle the problem
No
3
Query NE status and
alarm by using the
NMS
4
NE access Yes
successful and alarm Handle the alarm
cleared?
No
No Service
Rectify the fault on site Go to the next step
restored?
Yes
End

OptiX RTN 620

Note Description
1 The common abnormal operations are as follows:

l Modifying the data configuration
l Loopback
l Shutting down the laser
l Muting the ODU
l Replacing the board/cable.
l Loading the software
2 Check the notice issued by associated departments, and check whether there
are any external factors that may cause service faults, such as faults in the
power supply, cables, environment, and terminal equipment (such as
switching devices).
3 See 3.2.1 Checking the Status of NEs and 3.2.2 Browsing the Current
Alarms.
4 The alarms that can be cleared through the operations on the NMS are as
follows: 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.

OptiX RTN 620
Figure 5-3 Procedure of on-site fault handling
Start
Obvious Yes
equipment Repair or replace
damage? the equipment
No
1
Is the PWR indicator No Troubleshoot the
on the PXC on? power input
2 Yes
Browse alarms
locally by using the
Web LCT
3 Yes
Equipment
Clear the alarm
alarm?
No
4 Yes
Radio link Clear the alarm
alarm?
No
5 High order Yes
Clear the alarm
path alarm?
No
6 Low order Yes
Clear the alarm
path alarm?
No
Faulty inter- 7
Yes
connection with SDH/ Clear the alarm
PDH equipment?
8
Ethernet Yes
Clear the alarm
service fault?
No
Locate the fault by
Proceed to the next No Is the service
performing loopback
operations section by step restored?
section
Yes
End

OptiX RTN 620
Table 5-3 Procedure of on-site fault handling

Comment Description
No.

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 the topic of
"Powering On the Equipment" in the Commissioning Guide.

1. Refer to the Commissioning Guide and Connecting the Web LCT to the
IDU.
2. Refer to the Configuration Guide and Creating NEs by Using the Search
Method.
3. Refer to Commissioning Guide, and Checking 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 IDU Hardware Description.

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

OptiX RTN 620
Comment Description
No.

l MW_LIM
l MW_LOF
l R_LOS
l R_LOF
l R_LOC
l MS_AIS
l AU_AIS
l AU_LOP
l B1_EXC
l B2_EXC

l HP_LOM
l B3_EXC
l HP_UNEQ

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

5.6 Troubleshooting the Interconnection with the PDH Equipment.
8 See 5.7 Troubleshooting SDH/PDH Radio-Based Ethernet Service

Faults or 5.8 Troubleshooting Faults in Hybrid Radio-Based Ethernet
Services.
Experience and Summary

The maintenance personnel need to perform the regular maintenance to reduce the equipment
faulty rate. Thus, equipment faults can be discovered and rectified before they affect the services.

OptiX RTN 620
5.3 Troubleshooting Radio Links

When an NE reports MW_LOF or MW_FEC_UNCOR due to failure or performance
degradation of a radio link, there is a radio link fault.
The key to locating a radio link fault is to check whether the transmit power and the receive
power are abnormal, and to check whether there is an 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
l RADIO_TSL_LOW
l TSL_CUR
l TSL_MAX
l TSL_MIN
l TSL_AVG
NOTE
For a detailed description of the range of the transmit power, refer to the Product Description.
In the following two cases, the RSL is abnormal. The first case is that the receive power is lower
than the normal value (Normal value = Planned value - 3 dB). 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
l RADIO_RSL_LOW
l RSL_CUR
l RSL_MAX
l RSL_MIN
l RSL_AVG
NOTE
For a detailed description of the receiver sensitivity, refer to the Product Description.
Generally, external interference is classified into co-channel interference and adjacent channel
interference.
l Co-channel interference is crosstalk from two different radio transmitters reusing the same
frequency channel. Therefore, the entire spectrum may be impaired.
l 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.
Because interference is closely related to the frequency in use, the transmission over a radio link
may be faulty in one direction only.

OptiX RTN 620
Fault Causes
Table 5-4 Causes of radio link faults

Fault Common Fault Causes
The transmit power is abnormal. The ODU is faulty.
The receive power is always lower than the l The antenna direction is not properly
normal value. adjusted.
l The antennas have different polarization
directions.
l There is a mountain or building in the
transmit direction.
l The antenna is faulty or the connection
between the antenna and the ODU is
abnormal (for example, the waveguide
interface of the ODU is wet or the flexible
waveguide is not connected properly).
l The ODU is faulty.
The receive power is abnormal due to slow There is an external interference.

up-fading.
The receive power is abnormal due to slow The fading margin is not sufficient.
down-fading.
The receive power is abnormal due to fast The multipath fading is fast.
fading.
The receive power is normal, but the radio There is external interference.
link is faulty in one direction.
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.
l 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.
l Slow fading
The fading duration time ranges from tens of seconds to several hours.
Because slow down fading and fast fading are imposed by the propagation paths, the radio link may be faulty
in both directions.

OptiX RTN 620

1. Check whether the ODU is mute, powered off, or looped back. Check whether the data
configuration is correct.
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 receive power is normal but faults occur on the radio link intermittently, check
whether there is interference before you proceed.
6. If the transmit/receive power is normal, perform loopback operations.

OptiX RTN 620
Fault Locating Procedures

OptiX RTN 620
Figure 5-4 Flow of handling radio link faults
Start
1 Yes Cancel the

Incorrect operation?
operation
No
Yes
2 ODU or IF related
alarm? Clear the alarm
No
No 3
Transmit power
Rectify the fault
normal?
Ye
s
Yes 4
RSL always lower
Rectify the fault
than the normal
value?
No
Yes 5
Slow up fading
causes abnormal Rectify the fault
RSL?
No
Yes 6
Slow down fading Rectify the fault
causes abnormal
RSL?
No
Yes 7
Fast fading
causes abnormal Rectify the fault
RSL?
No
Yes 8
Radio link
faulty in one Rectify the fault
direction?
No No
Proceed to Is the fault
9 the next step rectified?
Perform loopback
operations
Yes
End

OptiX RTN 620

Note Description
1 Handle Check the following points:

incorrect l Check whether the ODU is powered off.
operations.
l Check whether the ODU is muted.
l Check whether the IF board is looped back.
l Check whether the data configuration at the transmit end is the same as the
data configuration at the receive end.
l Check whether the data configuration matches the type of the ODU and
the hybrid coupler.
2 Handle Pay special attention to:

equipment l VOLT_LOS
faults.
l CONFIG_NOSUPPORT
l HARD_BAD
l TEMP_ALARM
l IF_INPWR_ABN
l RADIO_MUTE
l RADIO_TSL_HIGH
l RADIO_TSL_LOW
l RADIO_RSL_HIGH
l IF_CABLE_OPEN
3 Handle the 6.12 Replacing an ODU

exception of
transmit
power.

OptiX RTN 620
Note Description
4 Handle the Follow the steps below:

exception 1. If the receive power decreases sharply and does not recover, check the
that the installation of the antenna. Ensure that the azimuth angle of the antenna
receive meets the requirement.
power is
smaller than Check whether the antenna is aligned properly. Check whether the received
the normal signal is from the main lobe.
value. If the antenna direction is not aligned properly, adjust the antenna in a wide
range.
2. If the difference between the receive power of the main ODU and standby
ODU at one end of the 1+1 HSB radio link is beyond the range from 0 dB
to 9 dB (in the case of an unbalanced hybrid coupler) or beyond the range
from 0 dB to 5 dB (in the case of a balanced hybrid coupler), perform 1+1
HSB switching or replace the ODUs and hybrid coupler to identify the
faulty part.
3. If the difference between the RSL at the receive end and transmit end is
larger than 10 dB, replace the ODUs to check whether the main or standby
ODU is faulty.
4. Check whether the setting of the polarization direction of the antenna is
correct. Rectify the wrong polarization direction.
5. Replace the ODUs and hybrid coupler to identify the faulty part.
6. Check whether there is a mountain or building in the transmit direction.
7. Check whether the gains of the antennas at the receive and transmit ends
comply with the specifications. Replace the antenna whose gain does not
comply with the specifications.
5 Handle the Follow the steps below:

up slow 1. Check whether there is co-channel interference.
fading fault.
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.
6 Handle the Contact the network planning department to make the following changes:
down slow l Increase the installation height of the antenna.
fading fault.
l Reduce the transmission distance.
l Increase the antenna gain.
l Increase the transmit power.

OptiX RTN 620
Note Description
7 Handle the Contact the network planning department to make the following changes:
fast fading l Adjust the position of the antenna to block the reflected wave or make the
fault. reflection point fall on the ground that has a small reflection coefficient,
thus reducing the multipath fading.
l Adjust the RF configuration to make the links in the 1+1 SD configuration.
l 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.
l Increase the fading margin, by replacing the original antennas with
antennas of a larger diameter or increasing the transmit power of the
original antennas.
8 Handle the The handling procedure is as follows:

interference 1. Check whether there is co-channel interference.
fault.
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 RF 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.

OptiX RTN 620
Note Description
9 Use the Follow the steps below:

loopback 1. Perform an inloop on the IF port.
method to
locate a fault. If the fault is not cleared after the loopback, replace the IF board.
2. Check whether the IF cable is soggy, broken or pressed. Make the
connector again.
3. Check whether the IF cable is soggy, broken, or pressed. If yes, replace
the IF board.
4. Replace the ODU.
If the fault is cleared after the replacement, the original ODU is faulty.

l During a commissioning process, make sure that the antenna direction is correctly adjusted
to prevent possible incipient faults.
l Periodically collect the change data of the transmit power and receive power, and analyze
the change data to remove incipient faults in time.
5.4 Troubleshooting Bit Errors in TDM Services

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 RS bit errors refer to the bit errors that the line processing unit or the IF board that works
in SDH mode through the B1 overhead byte in the RS overhead. The related alarms and
performance events are as follows:
l B1_EXC
l B1_SD
l RS_CROSSTR
l RSBBE
l RSES
l RSSES
l RSCSES
l 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
l B2_SD

OptiX RTN 620
l MS_CROSSTR
l MSBBE
l MSES
l MSSES
l MSCSES
l MSUAS
The line board detects HP bit errors by the HP overhead byte B3. Related alarms and performance
events are listed below:
l B3_EXC
l B3_SD
l HP_CROSSTR
l HPBBE
l HPES
l HPSES
l HPCSES
l HPUAS
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 B3_EXC_VC3_
l B3_SD_VC3
l BIP_EXC
l BIP_SD
l LP_CROSSTR
l VC3BBE
l VC3ES
l VC3SES
l VC3CSES
l VC3UAS
l LPBBE
l LPES
l LPSES
l LPCSES
l LPUAS

OptiX RTN 620
Fault Causes
Table 5-6 Causes of bit errors
Fault Type Common Cause
There are some RS bit errors. l 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 radio line, check whether there
is an MW_FEC_UNCOR alarm or an
RPS_INDI alarm.
l The line board is faulty.
l The clock unit is faulty.
l 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.
There is no RS bit error, but there are MS bit l The line board is faulty.
errors or HP bit errors. l The quality of the clock over the network
degrades.
When the quality of the clock over the
network degrades, there will be a pointer
l The working temperature of the line board
is excessively high.
There are only LP bit errors. l The PDH service processing board or the
Ethernet service processing board is faulty.
l The cross-connect unit is faulty.
l The working temperature of the PDH
service processing board or the Ethernet
service processing board is excessively
high.
l The working temperature of the cross-
connect unit is excessively high.
l There is power surge or an external
interference source, or the equipment is not
properly grounded.

OptiX RTN 620

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 part, replace it with a new one.
Figure 5-5 Flow of handling bit errors
Start
2
1
Is there an Yes
Handle the alarm
equipment alarm?
No
Is there a pointer Yes Handle the pointer

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

section by section Yes
End

OptiX RTN 620

Note Description
1 Pay special attention to:

l TEMP_ALARM
l SYN_BAD
l HARD_BAD
2 Refer to 5.9 Troubleshooting Pointer Justifications.
3 Follow the steps below:

1. Interchange 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. In addition, 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 to be faulty.
4. For the case that the equipment at the two ends is faulty, to locate the fault,
you can also replace the SDH optical interface 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_FEC_UNCOR alarm or an RPS_INDI
alarm.
2. If yes, refer to 5.3 Troubleshooting Radio Links.
3. If no, replace the IF board.

OptiX RTN 620
Note Description

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 SDH electrical interface 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).

1. Replace the PDH service processing board or Ethernet service
processing board or cross-connect board based on how the service paths
that have bit errors overlap each other.
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 Check bit error performance events and handle them routinely in time.
l To locate a fault, primarily use the method of analyzing alarms and performance events.
In addition, consider the loopback method and the replacement method.
5.5 Troubleshooting the Interconnection with the SDH

Equipment
In the case that the NE is interconnected with the SDH equipment, if the SDH service cannot be
transmitted between the equipment sets, there is an interconnection fault.
Fault Causes
l The VC-12 numbering method of the OptiX equipment is different from the numbering
method of the equipment of certain vendors.

OptiX RTN 620
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.
l The overhead bytes at the two sides are inconsistent.
l The indexes of SDH interfaces do not meet requirements.
l 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.

OptiX RTN 620
Figure 5-6 Flow of troubleshooting the interconnection with the SDH equipment
Start
Is the
Set the interconnection
interconnected equipment Yes
service to be the VC-4 pass-
the ATM/IP equipment?
through service
No
Query the VC-12 numbering
method of the interconnected
equipment
Is the Modify the data configuration.

Yes
numbering mode the Use the line numbering
line numbering? method to set the VC-12
No
1 Is there an overhead Yes

setting related alarm? Handle the alarm
No
2
Is the interface the Yes

Check the grounding
STM-1 electrical
interface?
3 No
Test the indexes of interfaces
Do the interfaces meet No Handle the faults of the

relevant standards? interconnected equipment
Yes Go to the next No

step Is the fault cleared?
Handle the faults of the local Yes

equipment
End

OptiX RTN 620

Note Description

l J0_MM
l HP_TIM
l LP_TIM
l LP_TIM_VC12
l LP_TIM_VC3
l HP_SLM
l LP_SLM
l LP_SLM_VC12
l LP_SLM_VC3
2 Check the following points:

l Check whether all the equipment and the DDF in the equipment room are
jointly grounded.
l Check whether the shielding layer of the coaxial cable connector on the
DDF is connected to the protection ground.
l 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 SDH equipment. In addition, 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.
3 Common indexes of the optical interfaces:

l Mean launched optical power
l Receiver sensitivity
l Overload optical power
l Permitted frequency deviation of the input interface
Common indexes of the electrical interfaces:
l Permitted frequency deviation of the input interface
l Allowed attenuation of the input interface

To clear any interconnection fault, you need to have a knowledge of the characteristics of the
interfaces of the interconnected equipment.

OptiX RTN 620
5.6 Troubleshooting the Interconnection with the PDH

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

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

OptiX RTN 620
Figure 5-7 Flow of troubleshooting the interconnection with the PDH equipment
Start
1
Check the impedance of
the interfaces
Is there an Yes Replace the cable or the

impedance mismatch?
tributary board
No
2
Is the cable the Yes
Check the grounding
coaxial cable?
No
3
Check the cables
No
Is in good conditions? Adjust the cables
4 Yes
Test the indexes of
interfaces
Do the interfaces No Handle the faults of the

meet standards? interconnected equipment
Yes Go to the next No

step
Yes
Handle the faults of the
local equipment
End

OptiX RTN 620
Note Description
1 Check whether the type of the tributary board

l Check whether all the equipment and the DDF in the equipment room are
jointly grounded.
l Check whether the shielding layer of the coaxial cable connector on the
DDF is connected to the protection ground.
l 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.
l Check whether the cable is broken or pressed.
l 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).
NOTE
Checking the cables involves checking the cables from the DDF to the client side and
checking the cables from the DDF to the transmission equipment side.
4 Check the following indexes:

l Input jitter tolerance
l Permitted input frequency deviation
l Output jitter
l Output frequency deviation

Grounding problems are the most common reasons that cause an interconnection failure when
the OptiX RTN 600 is interconnected with the PDH equipment.
5.7 Troubleshooting SDH/PDH Radio-Based Ethernet

Service Faults
EoS/EoPDH-based Ethernet services can be transmitted through SDH/PDH radio networks or
TDM networks. The associated service faults include Ethernet service interruption and Ethernet

OptiX RTN 620
Ethernet service interruption indicates that the Ethernet service is completely interrupted.
Ethernet service degradation indicates that the Ethernet service is abnormal. For example, the
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 The possible human factors are as follows:
– Loopback is performed on an Ethernet board, or loopback is performed on a
transmission line.
– 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.
l The equipment at the local end is faulty.
l The line board is faulty or has bit errors.
l When the AM function is enabled, the Ethernet service bandwidth decreases if a lower-
efficiency modulation mode is used.
l Certain E1 services are transmitted on the transmission lines for EoS-based Ethernet
services.
l The interconnected equipment is faulty.
l The network cable is faulty.
l External electromagnetic interference is severe.

1. Rectify the human-caused faults 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.

OptiX RTN 620
Figure 5-8 Flow of handling Ethernet service faults
Start
1
Incorrect Yes
operation?
No
2 Equipment alarm Yes

or radio link Clear the alarm
alarm?
No
3 Query the port and
Ethernet Yes
Clear the alarm service traffic and
service alarm?
analyze the fault causes
No
4
Loop formed by the Yes
Release the loop
E-LAN service
trails?
5 Rectify the fault according

Abnormal Yes to the flow of handling
RMON performance
events? abnormal RMON
performance events
No
Fault on the Yes

Troubleshoot the
opposite
equipment? opposite equipment
No
Troubleshoot the equipment
by performing loopback Proceed to No Is the fault
operations section by the next step rectified?
section by replacing boards
Yes
End

OptiX RTN 620

Note Description

l Whether a loopback is set for the Ethernet port
l Whether a loopback is set for the transmission line
l 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
l Whether the configuration of the encapsulation/mapping protocol or the
LCAS protocol is the same as that of the opposite equipment
l Whether the VCTRUNK-bound timeslot is the same as that of the opposite
equipment
l Whether the Ethernet protocol and the Ethernet service configuration
(especially the attributes of the Ethernet port) are correct.
2 Check the following equipment alarms:

l POWER_ALM
l FAN_FAIL
l HARD_BAD
l BD_STATUS
l SYN_BAD
l NESF_LOST
l TEMP_ALARM
l RADIO_RSL_HIGH
l RADIO_RSL_LOW
l RADIO_TSL_HIGH
l RADIO_TSL_LOW
l IF_INPWR_ABN
Check the following line alarms:
l MW_LIM
l MW_LOF
l R_LOS
l R_LOF
l MS_AIS
l AU_AIS
l AU_LOP
l B1_EXC
l B2_EXC

OptiX RTN 620
Note Description
3 Check the following:

l ETH_LOS
l FLOW_OVER
l ALM_GFP_dCSF
l ALM_GFP_dLFD
l FCS_ERR
l LCAS_PLCT
l LCAS_TLCT
l LCAS_PLCR
l LCAS_TLCR
l LCAS_FOPT
l LCAS_FOPR
4 Check whether loops occur in the Ethernet LAN services.

NOTE
You can check whether a loop occurs by using the self-loop test function of the EMS6.
5 For RMON performance events, refer to D RMON Event Reference.

OptiX RTN 620
Figure 5-9 Flow of handling RMON abnormal performance events
Start
1
View the statistics group
performance on an Ethernet port
2
Yes Rectify the fault of line bit
Is there any FCS error? errors
No
3
Is there any collision Yes Check the working mode
or fragment? of the port
No
4
Is there any Yes Handle the flow control
PAUSE frame? problem or increase the
bandwidth
No
5
Yes Handle the problem on
Are broadcast packets excessive broadcast
excessive? packets
No
Use a meter to perform the test
Yes
Is the test passed? Rectify the fault of the
interconnected equipment
No
6 Yes
Is it a MTU setting
Modify the MTU value
problem?
No
Proceed with No Is the fault
Rectify the equipment fault by the next step rectified?
loopback section by section or
replacing the board Yes
End

Note Description
1 View the statistics group performance on an Ethernet port to obtain the real-
time performance statistics of the Ethernet port.

OptiX RTN 620
Note Description

l Check the Ethernet cable. If the Ethernet cable is not qualified, replace it
with a new one.
l 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.

l Whether the port operating rate of this equipment is the same as that of its
l Whether the duplex/half-duplex mode of ports on this equipment is the
same as that on its interconnected equipment
l Do not set one port to auto-negotiation and the opposite port to full-duplex.

l Whether the flow control mode of this equipment is the same as that of its
l Whether the Ethernet service volume is larger that the configured
VCTRUNK bandwidth
5 Identify the causes of generating excessive broadcast packets, such as 7.5.5

Setting Loopback for the Ethernet Service Processing Board 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.
6 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.

Understand the features, working mode, and configured protocols of interfaces on Ethernet
equipment, which is required to troubleshoot Ethernet faults.
5.8 Troubleshooting Faults in Hybrid Radio-Based Ethernet

Services
Hybrid radio-based Ethernet services can be transmitted over Hybrid radio networks but cannot
traverse a TDM network. The associated faults include Ethernet service interruption and Ethernet
The Ethernet service interruption indicates that the Ethernet service is completely interrupted.
The Ethernet service degradation indicates that the Ethernet service is abnormal. For example,

OptiX RTN 620
the network access speed is low, the equipment delay is long, the packet loss occurs, or incorrect
packets exist in the received or transmitted data.
Fault Causes
l The human factors are as follows:
– An Ethernet board loopback or a transmission line loopback occurs.
– The settings of the parameters of an Ethernet port, such as the port enabling, working
mode, and flow control are different from those of the interconnected equipment.
– The configuration of the encapsulation/mapping or LCAS protocol is different from
that of the remote equipment.
– The VCTRUNK-bound timeslot is different from that of the remote equipment.
– The service configuration is incorrect.
l The local equipment is faulty.
l The line board is faulty or has bit errors.
l The modulation mode changes because of the degradation of the link performance when
the AM function is enabled.
l The interconnected equipment is faulty.
l The network cable is faulty.
l The external electromagnetic interference is severe.

1. Rectify the human-caused faults such as a loopback and a 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.

OptiX RTN 620
Fault Locating Procedure
Figure 5-10 Flow of handling an Ethernet service fault
Start
1
Incorrect Yes
operation?
No
2 Equipment alarm Yes

or radio link Clear the alarm
alarm?
No
3 Query the port and
Ethernet Yes
Clear the alarm service traffic and
service alarm?
analyze the fault causes
No
4
Loop formed by the Yes
Release the loop
E-LAN service
trails?
5 Rectify the fault according

Abnormal Yes to the flow of handling
RMON performance
events? abnormal RMON
performance events
No
Fault on the Yes

Troubleshoot the
opposite
equipment? opposite equipment
No
Troubleshoot the equipment
by performing loopback Proceed to No Is the fault
operations section by the next step rectified?
section by replacing boards
Yes
End

OptiX RTN 620
Note Description

l Whether a loopback is set for the Ethernet board
l Whether a loopback is set for the transmission line
l Whether the settings of the parameters of an Ethernet port, such as the port
enabling, working mode, and flow control are the same as those of the
l Whether the configuration of the encapsulation/mapping or LCAS protocol
is the same as that of the remote equipment
l Whether the VCTRUNK-bound timeslot is the same as that of the remote
equipment
l Whether the Ethernet protocol and the Ethernet service configuration
(especially the attributes of the Ethernet port) are correct.
2 Check the following equipment alarms:

l POWER_ALM
l FAN_FAIL
l HARD_BAD
l BD_STATUS
l SYN_BAD
l NESF_LOST
l TEMP_ALARM
l RADIO_RSL_HIGH
l RADIO_RSL_LOW
l RADIO_TSL_HIGH
l RADIO_TSL_LOW
l IF_INPWR_ABN
Check the following line alarms:
l MW_LIM
l MW_LOF
l MW_BER_EXC
l MW_BER_SD
l MW_LIM
l MW_LOF
l MW_RDI
l MW_FEC_UNCOR
3 Check the following alarms:

l ETH_LOS
l ALM_GFP_dCSF

OptiX RTN 620
Note Description
4 Check the following alarms:

l ALM_GFP_dLFD
l FCS_ERR
l LCAS_PLCT
l LCAS_TLCT
l LCAS_PLCR
l LCAS_TLCR
l LCAS_FOPT
l LCAS_FOPR
5 For RMON performance events, refer to the D RMON Event Reference.

OptiX RTN 620
Figure 5-11 Flow of handling an abnormal RMON performance event
Start
1
View the statistics group
performance on an Ethernet port
2
Yes Rectify the fault of line bit
Is there any FCS error? errors
No
3
Is there any collision Yes Check the working mode
or fragment? of the port
No
4
Is there any Yes Handle the flow control
PAUSE frame? problem or increase the
bandwidth
No
5
Yes Handle the problem on
Are broadcast packets excessive broadcast
excessive? packets
No
Use a meter to perform the test
Yes
Is the test passed? Rectify the fault of the
No
6 Yes
Is it a MTU setting
Modify the MTU value
problem?
No
Proceed with No Is the fault
Rectify the equipment fault by the next step rectified?
loopback section by section or
replacing the board Yes
End

Note Description
1 View the statistics group performance on an Ethernet port to understand the

real-time performance statistics data of the Ethernet port.

OptiX RTN 620
Note Description

l Check the network cable. If the network cable does not meet the
requirements, replace the network cable.
l Change the Ethernet port of the access services on the Ethernet board. If
the new port does not have the RMON performance of an FCS error, it
indicates that the hardware of the original port is faulty. Otherwise, the
hardware of the Ethernet port on the opposite equipment is faulty.

l Whether the port operating rate of the equipment is the same as that of the
l Whether the full-duplex/half-duplex mode of a port on the equipment is
the same as that on the interconnected equipment
l Do not set the auto-negotiation at one end and the full-duplex at the other
end.

l Whether the flow control mode of the equipment is the same as that of the
l Whether the Ethernet service volume is greater than the configured
VCTRUNK bandwidth
5 Find out of the reason of excessive broadcast packets (such as 7.5.5 Setting
Loopback for the Ethernet Service Processing Board or improper VB filter
table setting) and solve the problem. If the problem is caused by the opposite
equipment, set the threshold of broadcast packet suppression for an Ethernet
port to reduce broadcast packets.
6 Test the MTU of the network by using a test meter. The maximum frame
length that is set for a port should be longer than the MTU of the network.

Understand the features, working mode, and configured protocols of interfaces on the Ethernet
equipment, which is required to troubleshoot Ethernet faults.
5.9 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
l AUPJCLOW

OptiX RTN 620
l 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
l TUPJCLOW
l 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
l 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.
l The optical fibers links are wrongly connected. As a result, mutual clock tracing occurs.
l The quality of the clock source degrades, the clock unit is faulty, or there are other clock-
related faults.
l 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 Fault Locating Methods
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.

OptiX RTN 620
Fault Types Fault Locating Methods
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.

OptiX RTN 620
Figure 5-12 Flow of handling pointer justifications
Start
1 Is there a clock related Yes

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

Wrong configuration?
configuration
No
3
Check the fiber connection
Yes
Wrongly connected? Re-connect the fiber
No
4 5
Is there an AU pointer Yes Find the NE whose clock is
out of synchronization Locate the faulty board
justification event?
No
6 7
Is there a TU pointer Yes Find the NE whose clock is

Find the faulty board
justification event? out of synchronization
No
No
Go to the next step Is the fault cleared?
Yes
End

OptiX RTN 620

Note Description

l TEMP_ALARM
l SYN_BAD
l HARD_BAD
l LTI
l SYNC_C_LOS
l S1_SYN_CHANGE
l EXT_SYNC_LOS

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

1. Locate the VC-4 channel that reports an AU pointer justification event.
2. Along the service source direction of the VC-4 channel, locate 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.
5 Replace the possibly faulty boards.

OptiX RTN 620
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.
7 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.
5.10 Troubleshooting Orderwire Faults

If orderwire calls cannot get through when services are normal, there is an orderwire fault.
Fault Causes
l The phone set is incorrectly set.
l The phone line is connected incorrectly.
l The orderwire is incorrectly configured.
NOTE
When services are transmitted over E1 lines, the orderwire traffic needs to be transmitted in other
means, for example, through the synchronous data interface or external clock interface.
l The system control unit is faulty.
l The line unit is faulty.

OptiX RTN 620

l Check whether the phone set is correctly set, whether the phone line is correctly connected,
and whether the orderwire is correctly configured.
l Replace the possibly faulty board to locate the fault.
Figure 5-13 Flow of handling orderwire faults
Start
Check the phone setting
Is the phone No
Modify the phone setting
correctly set?
Yes
Is the phone line No

Re-connect the phone line
correctly connected?
Yes
2
Check the orderwire
configuration
Is the configuration No
Modify the configuration
correct?
3 Yes
Replace the possibly faulty
board
Go to the next No
step
Yes
End

OptiX RTN 620

Note Description

l Check whether the ring current switch "RING" on the phone set is set to
"ON".
l Check whether the dialing mode switch is set to "T", that is, the dual tone
multi-frequency mode.
l 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 front of phone set to hook it up. In certain
occasions the "TALK" button is pressed by the maintenance personnel due
to carelessness. This makes the phone set stay in the off-hook state all the
time and the orderwire call from other NEs cannot get through.

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

It is necessary to periodically check the orderwire phone set.

OptiX RTN 620
Maintenance Guide 6 Part Replacement
6 Part Replacement
About This Chapter
Part replacement is a method frequently used to locate faults. The replacement operation varies
with the part types.
Table 6-1 Part replacement description

Part Name Operation Tool
SL1, SD1, and 6.3 Replacing the SDH Optical l ESD wrist strap
SL4 Interface Board l Screwdriver
SLE and SDE 6.4 Replacing the SDH Electrical l Web LCT
Interface Board
PH1, PO1, PD1, 6.5 Replacing the PDH Interface

and PL3 Board
EFT4, EMS6, 6.6 Replacing the Ethernet

and EFP6 Service Processing Board
IF1A, IF1B, 6.7 Replacing the IF Board

IFX, IF0A,
IF0B, and IFH2
PXC 6.8 Replacing the PXC Board
SCC 6.10 Replacing the SCC Board
FAN 6.11 Replacing the Fan Tray
ODU Replacing the ODU of the l Ejector lever (torque wrench)

Waveguide Interface and 6.12 l Web LCT
Replacing an ODU
l Silicon
l Waterproof adhesive tape

OptiX RTN 620
6 Part Replacement Maintenance Guide
Part Name Operation Tool
Replacing the 6.13 Replacing the IF Cable l Multimeter

IF Cable l Ejector lever
l Electro-technical knife
l File
l Installation parts and accessories
of the connector
l IF cable
6.1 Removing a Board

Removing a board is a basic operation for replacing a board.
6.2 Inserting a Board
Inserting a board is a basic operation for replacing a board.
6.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.
6.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.
6.5 Replacing the PDH Interface Board
When the PDH interface board is replaced, the services of the board are interrupted.
6.6 Replacing the Ethernet Service Processing Board
When the Ethernet service processing board is replaced, the services on this board are
interrupted.
6.7 Replacing the IF Board
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.
6.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.
6.9 Replacing the Storage Card
When replacing the storage card, do not perform any operations on the NMS, and do not perform
switching.
6.10 Replacing the SCC Board
During this process, no NM operation and switching can be performed.
6.11 Replacing the Fan Tray
The IDU cannot perform air cooling in the process of fan tray replacement. Therefore, you need
to replace the fan board quickly.
6.12 Replacing an ODU

OptiX RTN 620
If the radio link provided by an ODU is not configured with protection and the services on the
ODU are not configured with protection, replacing the ODU interrupts the services. In addition,
the services on the radio link of the other polarization direction are affected if the radio link
provided by the ODU is configured with XPIC.
6.13 Replacing the IF Cable
The IF cable cannot transmit radio services when it is replaced.

OptiX RTN 620
6.1 Removing a Board

Removing a board is a basic operation for replacing 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 Optional: If the board is connected with cables, remove the cables after marking them.
Step 3 Loosen the screws on the panel of the board.
Figure 6-1 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.

OptiX RTN 620
CAUTION
Remove the board slowly, to prevent the components on the boards from colliding.
Step 6 Put the removed board into the antistatic box or bag.
----End
6.2 Inserting a Board

Inserting a board is a basic operation for replacing 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 so that the angle between
the ejector lever and the panel is 45 degrees or so.
Step 3 Push the board gently along the slot guide rail until the board cannot slide further.
Figure 6-4 Inserting a board (1)

OptiX RTN 620
CAUTION
Insert the board slowly, to prevent the components on the boards from colliding.
Step 4 Press the two ejector levers inward with force.
Step 5 Tighten screws on the panel.
Step 6 Optional: If the board is connected to cables originally, connect the cables based on the label
marked on them.
----End

OptiX RTN 620
6.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
l You must be aware of the impact of board replacement.
l You must know the specific position of the board to be replaced.
l You must know the service protection and protection channels of the board to be replaced.
l The spare SDH optical interface board must be at hand and that the version and type of the
spare board must be consistent with those of the board to be replaced. You can perform the
task in 7.4.2 Querying a Board Manufacture Information Report to learn the version
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 ESD wrist strap
l Screwdriver
l Web LCT
Procedure
Step 1 Use the Web LCT to query the current alarms of the board.
Step 2 Optional: If the services on the board are configured with the SNCP, ensure that the services
are switched to the protection channel.
1. Query the SNCP protection group.
2. If the port on the board functions as the current working channel, the current protection
channel is not on the board, and the state of the current protection channel is normal or SD,
perform forced switching.
Step 3 Optional: If the services on the board are configured with the linear MSP, ensure that the services
1. Query the linear MSP group.
Step 4 Optional: If the services on the board are configured with the ring MSP, ensure that the services

OptiX RTN 620
Step 5 Remove the board according to 6.1 Removing a Board.
Step 6 Check whether the version and SFP type of the spare board are the same as those of the board
to be replaced.
Step 7 Insert the spare board according to 6.2 Inserting a Board.
Step 8 After the board starts to work, observe the indicators.

The STAT indicator should be on and green.
Step 9 Query the current alarms on the board using the Web LCT.
There should be no new alarms.
Step 10 Optional: If the forced SNCP switching has been performed for the services, clear the forced
switching using the Web LCT.
Step 11 Optional: If the linear MSP switching has been performed for the services, clear the forced
Step 12 Optional: If the ring MSP switching has been performed for the services, clear the forced
----End
6.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 must be at hand and that the version and type of
the spare board must be consistent with those of the board to be replaced. You can query
the board manufacturing information to obtain the version of the board to be replaced.

l ESD wrist strap
l Screwdriver
l Web LCT
Procedure
Step 2 If the services on the board are configured with the SNCP, ensure that the services are switched
to the protection channel.

OptiX RTN 620
Step 3 If the services on the board are configured with the linear MSP, ensure that the services are
switched to the protection channel.
Step 4 If the services on the board are configured with the ring MSP, ensure that the services are
switched to the protection channel.
1. Query the ring MSP group.
Step 6 Ensure that the version of the spare board is the same as the version of the board to be replaced.

Step 11 Optional: If the linear MSP switching has been performed for the services, clear the forced
Step 12 Optional: If the ring MSP switching has been performed for the services, clear the forced
----End
6.5 Replacing the PDH Interface Board

When the PDH interface board is replaced, the services of the board are interrupted.
Prerequisite
l The spare PDH interface board must be at hand and that the version and type of the spare
board must be consistent with those of the board to be replaced. You can query the board
manufacturing information to obtain the version of the board to be replaced.

OptiX RTN 620
NOTE
l The SL61PO1, PH1, and PD1 have two types: A and B. The A type is of 75-ohm interface impedance, and
the B type is of 120-ohm interface impedance. You can identify them by the bar code on the board ejector
lever.
l The E1 interface of the SL62PO1 is RJ45. The interface impedance is 120 ohms.
l The interface impedance of the PL3 is 75 ohms only.

l ESD wrist strap
l Screwdriver
l Web LCT
Procedure
Step 3 Make sure the version and type of the spare board are consistent with those of the board to be
replaced.

----End
6.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 spare Ethernet service processing board must be at hand and that the version and type
of the spare board must be consistent with those of the board to be replaced. You can
perform the task in 7.4.2 Querying a Board Manufacture Information Report to learn
the version of the board to be replaced. In the case of the EMS6 board, the type of the spare
board also must be consistent with 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.

OptiX RTN 620

l ESD wrist strap
l Screwdriver
l Web LCT
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
6.7 Replacing the IF Board

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 You must understand the configuration of the board 1+1 protection.
l The spare IF board must be at hand and that the version and type of the spare board must
be consistent with those of the board to be replaced. You can perform the task in 7.4.2
Querying a Board Manufacture Information Report to learn the version of the board
to be replaced.

l ESD wrist strap
l Screwdriver
l Web LCT

OptiX RTN 620
Procedure
Step 2 Optional: If the services on the board are configured with the SNCP, ensure that the services
Step 3 Optional: If the services on the radio link are configured with the 1+1 protection, ensure that
the services are switched to the protection IF board.
1. Query the IF 1+1 protection group.
2. If the board functions as the current working board, and the state of the current protection
board is normal or SD, perform forced switching.
Step 4 Optional: If the services on the radio link are configured with the N+1 protection, ensure that
the services are switched to the protection IF board.
1. Query the IF N+1 protection group.
2. If the board functions as the current working board, and the state of the current protection
board is normal or SD, perform forced switching.
Step 5 Turn off the ODU-PWR switch on the front panel of the IF board to be replaced.
Step 7 Check whether the version and type of the spare board are the same as those of the board to be
replaced.
Step 8 Ensure that the ODU-PWR switch on the front panel of the spare IF board is turned off.

Step 11 Turn on the ODU-PWR switch on the front panel of the IF board.
Step 13 If the new IF board is an IF1A/IF1B board and reports the new alarm NO_BD_SOFT, load and
activate the FPGA file of the IF board again according to the upgrade guide.
Step 15 Optional: If the forced protection switching has been performed for the microwave line, clear
the forced switching using the Web LCT.
----End

OptiX RTN 620
6.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 You must understand the configuration of the board 1+1 protection.
l The spare PXC board must be at hand and that the version and type of the spare board must
be consistent with those of the board to be replaced. You can perform the task in 7.4.2
Querying a Board Manufacture Information Report to learn the version of the board
to be replaced.

l ESD wrist strap
l Screwdriver
l Web LCT
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 Optional: If the board to be replaced works in 1+1 mode and it is the main board, see 7.12
Switching PXC Boards.
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.
Step 6 Ensure that the version and type of the spare board are consistent with those of the board to be
replaced.
Step 8 Turn on the switch of the power that provides power for the PXC board.
Step 9 Turn on the SYS-PWR switch of the PXC board.

OptiX RTN 620
Step 12 Optional: If the switching is performed before the replacement, perform a switchover operation
on the Web LCT to make the working board be the active board, not the standby board.
----End
6.9 Replacing the Storage Card

When replacing the storage card, do not perform any operations on the NMS, and do not perform
switching.
Prerequisite
l You must be aware of the impact of storage card replacement.
l You must know the specific position of the storage card to be replaced.
Tools, Equipment and Materials

l ESD wrist strap
l Screwdriver
l Web LCT

OptiX RTN 620
Background Information
Figure 6-7 Positions of the jumpers and storage card
SL61SCCVER.C or SL61SCCVER.E
1
2
JUMP4
JUMP3 Jumper definition
JUMP2
JUMP1
1 2
JUMP4
JUMP3
SL61SCCVER.B JUMP2
JUMP1
9 10
JUMP1
JUMP2
JUMP3
JUMP4
1. Jumpers 2. Storage card
Table 6-2 Setting the jumpers
Jumper Setting (1: disconnected, 0: short circuit) Function
JUMP4 JUMP3 JUMP2 JUMP1
0 0 0 0 Normal
operating state.
0 0 0 1 Reserved.
0 0 1 0 Reserved.

OptiX RTN 620
0 0 1 1 Commissioning
state.
0 1 0 0 Operating state,
with the
WatchDog
disabled and
memory
undergone full
check.
0 1 0 1 BIOS holdover
state. Even if the
NE software
exists, it is not
running. The IP
address is
always
129.9.0.5. The
IP in the
parameter area
does not change
for the
convenience of
querying.
0 1 1 0 Exhibition
mode.
0 1 1 1 Data recover
state.
1 0 0 0 Reserved.
1 0 0 1 Reserved.
1 0 1 0 To erase the
system
parameter area.
1 0 1 1 To erase
database.
1 1 0 0 To erase NE
software and its
patches.
1 1 0 1 To erase
database, NE
software and its
patches.

OptiX RTN 620
1 1 1 0 To format the
file system so
that all the data
is erased.
1 1 1 1 To format the
file system so
that all the data
is erased (file
system +
extended BIOS
+ system
parameter area).
Procedure
Step 3 Set the jumpers on the SCC board to positions 0111.
Step 4 Remove the storage card from the SCC board.
1. Wear an ESD wrist strap.
2. Unscrew the storage card, and remove the plug of the storage card from the socket of the
SCC board.
Figure 6-8 Removing a Storage Card

OptiX RTN 620
Step 5 Install the spare storage card onto the SCC board.
Figure 6-9 Installing a Storage Card
Step 6 Insert the SCC board.
Step 7 When the SCC board changes to BIOS state, remove the SCC board.
NOTE
When the SCC board works in BIOS state, the PROG indicator on the front panel blinks slowly (300 ms on and
300 ms off).
Step 8 Set the jumpers on the SCC board to positions 0000 (default setting).
Step 9 Insert the SCC board.
----End
6.10 Replacing the SCC Board

During this process, no NM operation and switching can be performed.
Prerequisite
l The spare SCC board must be available and that the version and type of the spare board
must be consistent with the version and type of the board to be replaced. You can perform
the task in 7.4.2 Querying a Board Manufacture Information Report to learn the version
of the board to be replaced.

OptiX RTN 620

l ESD wrist strap
l Screwdriver
l Web LCT
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 the version
and the jumper settings of the board to be replaced.
Step 5 See 6.9 Replacing the Storage Card to remove the CF card from the original board and then
install the CF card to the spare board.
Step 7 After the board starts to work, observe the indicators on the board.
----End
6.11 Replacing the Fan Tray

The IDU cannot perform air cooling in the process of fan tray replacement. Therefore, you need
to replace the fan board quickly.
Prerequisite
The spare board must be made available, and the version and type of the spare board must be
the same as those of the board to be replaced. You can query the board manufacturing
information to learn about the version of the board to be replaced.

l ESD wrist strap
l Screwdriver
l Web LCT
Procedure

OptiX RTN 620
Step 2 Loosen the captive screws on the front panel of the fan tray.
Step 3 Move the cables away from the front panel of the fan tray.
Step 4 Remove the front panel of the fan tray.
Figure 6-10 Removing the front panel of the fan tray
NOTE
If the IDU is installed in a dustproof environment, no air filter is installed.
Step 5 Remove the fan board gently and horizontally along the guide rail.
Figure 6-11 Removing the fan tray
WARNING
Do not touch the blades until the fan has stopped rotating.
Step 6 Check and ensure that the version and type of the spare board are the same as the version and
type of the board to be replaced.
Step 7 Insert the spare fan board steadily along the guide rail.
Step 8 Install the front panel of the fan tray.

OptiX RTN 620
Step 9 Tighten the captive screws on the front panel of the fan tray.
Step 10 Observe the indicators on the front panel.

The FAN indicator should be on and green.
----End
6.12 Replacing an ODU

If the radio link provided by an ODU is not configured with protection and the services on the
ODU are not configured with protection, replacing the ODU interrupts the services. In addition,
the services on the radio link of the other polarization direction are affected if the radio link
provided by the ODU is configured with XPIC.
Prerequisite
l You must be aware of the impact of ODU replacement.
l You must know the specific positions of the ODU to be replaced and the IF board connected
to the ODU.
l The spare ODU must be available and the type must be the same as the type of the ODU
to be replaced.

l Torque wrench
l Web LCT
l Silicon
Notes
Before you replace an ODU that is 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 generates little RF radiation, thus meeting the safety standards for
electromagnetic radiation.
Procedure
Step 1 Query the current alarms on the ODU.
Step 2 Turn off the ODU-PWR switch on the front panel of the IF board.
Step 3 Remove the IF cable and the PGND cable connected to the ODU.
Step 4 Remove the ODU.

OptiX RTN 620
If... Then...
You need to remove the OptiX RTN 600 Loosen the four latches of the ODU and
ODU with a waveguide interface disconnect the ODU from the antenna, the
hybrid coupler, or ODU adapter.
You need to remove the OptiX RTN 600 Remove the ODU from the post.
ODU with a coaxial interface
You need to remove the RTN XMC ODU 1. Tighten the four M6 captive screws of the
ODU cornerwise.
2. Remove the ODU.
Step 5 Ensure that the type of the spare ODU is the same as the type of the ODU to be replaced.
Step 6 Install the ODU.
If... Then...
You need to install a new OptiX RTN 600 See the OptiX RTN 600 Quick Installation
ODU with a waveguide interface Guide to install the ODU.
You need to install a new OptiX RTN 600 See the OptiX RTN 600 Quick Installation
ODU with a coaxial interface Guide to install the ODU.
You need to install a new RTN XMC ODU See the RTN XMC ODU Quick Installation
Guide to install the ODU.
Step 7 Connect the PGND cable and the IF cable to the ODU.
Step 8 Waterproof the IF interface on the ODU.
Step 10 After the ODU starts to work, observe the ODU and LINK indicators on the front panel of the
IF board.
The two indicators should be on and green.
Step 11 Query the current alarms of the ODU.

----End
6.13 Replacing the IF Cable

The IF cable cannot transmit radio services when it is replaced.
Prerequisite
l You must be aware of the impact of IF cable replacement.
l You must know the specific positions of the IF cable to be replaced and the IF board
connected to the IF jump.

OptiX RTN 620
l In the case of the RG-8U IF cable or the 1/2-inch IF cable, an IF jumper is required to
connect the IF cable to the IDU and both ends of the IF cable should be terminated with
type-N connectors. In the case of the 5D IF cable, the IF cable is connected directly to the
IDU and the cable end connecting to the IDU should be terminated with the TNC connector
and the cable end connecting to the ODU should be terminated with the type-N connector.

l Ejector lever
l Electro-technical knife
l File
l Installation parts and accessories of the connector
l IF cable
Procedure
Step 2 Turn off the ODU-PWR switch on the front panel of the IF board.
Step 3 Disconnect the IF cable and the IF jump, and the IF cable and the ODU.
Step 4 Use a multimeter to test the cable circuit so as to determine whether to make the IF cable with
connectors again or replace the IF cable.
If... Then...
If the IF cable with connectors need be made again Make new connectors for the IF cable.
If the IF cable need be replaced Replace with a new IF cable.
Step 5 Connect the IF cable and the IF jump, and the IF cable and the ODU.
Step 6 Waterproof the connectors at the two ends of the IF cable with the waterproof adhesive tape.
Step 8 After the ODU starts to work, observe the ODU and LINK indicators on the front panel of the
IF board.
The two indicators should be on and green.
Step 9 Query the current alarms of the IDU.
----End

OptiX RTN 620
Maintenance Guide 7 Supporting Task
7 Supporting Task
About This Chapter
This topic describes the common maintenance operations.
7.1 Hardware Loopback

Hardware loopback refers to the loopback operation performed by changing the physical
connection.
7.2 Cleaning Fiber Connectors and Adapters
The optical connectors are easily contaminated in the maintenance process. The minute dust
particles that can be seen only in the microscope can also affect the quality of optical signals. In
this case, the system performance deteriorates. Hence, the fiber connectors or adapters that are
terminated need to be cleaned in time.
7.3 Browsing Alarms, Abnormal Events, and Performance Events
The Web LCT is used to browse alarms, abnormal events, and performance events at the NE
layer.
7.4 Querying a Report
You can obtain the version, manufacture, and radio link information of all the boards by querying
the corresponding report.
7.5 Software loopback
Software loopback refers to the loopback operation that is implemented by using the NMS. In
the OptiX RTN 620, the SDH optical interface board, SDH electrical interface board, PDH
interface board, IF board, Ethernet service processing board, and ODU support loopback.
7.6 Resetting
Resetting is an important method for handling software faults. The OptiX RTN 620 supports
cold resetting, warm resetting, and SCC resetting.
7.7 PRBS Test
The pseudorandom binary sequence (PRBS) test is an important method for network
maintenance and self-check.
7.8 Querying the License Capacity
You can check whether the loaded license file meets the requirements by querying the license
capacity.

OptiX RTN 620
7 Supporting Task Maintenance Guide
7.9 Setting the State of a Laser

A laser on the port of the SDH optical interface board transmits optical signals only when the
laser is turned on. You can turn a laser on or off by using the NMS.
7.10 Setting the ALS function
The SDH optical interface board supports the automatic laser shutdown (ALS) function. It can
turn off a laser when it does not carry services, the optical fiber is faulty, or the received optical
signals are lost.
7.11 Setting the Automatic Release Function
To protect the NM and NE communication from improper operations, an NE supports the
automatic release of the ODU mute, loopback, and other operations that require you to exercise
caution. The automatic release time is five minutes by default. You can set whether to enable
the automatic release function and the automatic release time using the NMS.
7.12 Switching PXC Boards
Manual PXC switching is an important maintenance operation.
7.13 Configuring Performance Monitoring Status of NEs
By default, the performance monitoring of NEs is enabled. You can disable or enable this
function manually and set the period of the performance monitoring of NEs manually.
7.14 Querying the Impedance of an E1 Channel
The impedance of an E1 channel is 75 ohms or 120 ohms, which can be queried through the
NMS but cannot be set through the NMS.
7.15 Using Ethernet Test Frames
By using the Ethernet test frames on the OptiX RTN 620, you can check the connectivity of the
VCTRUNK.
7.16 Querying the Working Status of an Ethernet Port
Through the operation, you can learn about the enable/disable state, loopback status, and the
actual working mode of an Ethernet port.
7.17 Setting the Threshold of Received Traffic Flow on an Ethernet Port
The FLOW_OVER alarm is reported when the traffic flow received on an Ethernet port exceeds
the specified threshold.
7.18 Performing Statistics for the Traffic Flow on an Ethernet Port
You can perform this operation to perform statistics for the traffic flow on an Ethernet port within
a specified period.
7.19 Performing Statistics for the Traffic Flow of Ethernet Services
You can perform this operation to perform statistics for the traffic flow of Ethernet services
within a specified period.

OptiX RTN 620
7.1 Hardware Loopback

Hardware loopback refers to the loopback operation performed by changing the physical
connection.
Hardware loopback is classified into optical cable loopback, SDH/PDH cable loopback, and
Ethernet port loopback.
l Optical cable loopback indicates that the receive and transmit optical fibers are connected
through a fiber jumper on the ODF. In certain occasions, an optical attenuator is added
based on the actual situation, to prevent the optical board from being damaged by the
excessive receive optical power.
l SDH/PDH cable loopback indicates that the receive and transmit SDH/PDH cables are
connected through a short-circuiting cable or connector on the DDF.
l Ethernet port loopback indicates that the receive and transmit service signals on one
Ethernet port are looped back through a special loopback Ethernet cable.
7.2 Cleaning Fiber Connectors and Adapters

The optical connectors are easily contaminated in the maintenance process. The minute dust
particles that can be seen only in the microscope can also affect the quality of optical signals. In
this case, the system performance deteriorates. Hence, the fiber connectors or adapters that are
terminated need to be cleaned in time.
7.2.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.
7.2.2 Cleaning Fiber Connectors Using Lens Tissue
When there is no cartridge cleaners, use the lens tissue for cleaning fiber connectors.
7.2.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.
7.2.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 that there is no laser light on the fiber
connector.
l Inspect the fiber connector with a fiber microscope to make sure that the fiber connector
is contaminated.
Tools, Equipment, and Materials

Cartridge cleaner

OptiX RTN 620
Procedure
Step 1 Press down and hold the lever, and the shutter slides back and exposes a new cleaning area.
Figure 7-1 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 7-2 Dragging the fiber tip slightly on one cleaning area

OptiX RTN 620
Step 3 Repeat the same in the other cleaning area in the same direction as Step 2.
Figure 7-3 Dragging the fiber tip slightly on the other cleaning area
Step 4 Release the lever to close the cleaning area.
----End
7.2.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.
l Inspect the fiber connector with a fiber microscope to make sure that the fiber connector
is contaminated.

l Clean solvent
l Non-woven lens tissue
l Special compressed gas

OptiX RTN 620
NOTE
l Using the isoamylol as the clean solvent is recommended, and the propyl can also be used. Do not use alcohol
or formalin.
l The fiber cleaning tissue or lint-free wipes can replace the non-woven lens tissue.
l The special cleaning roll can replace the special compressed gas.
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 7-4 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.
l Keep the injector nozzle as close as possible to the connector surface without touching it.
----End
7.2.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.

OptiX RTN 620
Prerequisite
l Before you clean the fiber adapter, ensure that you remove the optical fiber and shut down
the laser. For details about how to shut down a laser, refer to 7.9 Setting the State of a
Laser.
l Inspect the fiber adapter with a fiber microscope to ensure that the fiber adapter is
contaminated.

l Optical cleaning sticks
l Clean solvent
l Special compressed gas
NOTE
l 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.
l The medical cotton or long fiber cotton can replace the optical cleaning stick.
l Using the isoamylol as the clean solvent is preferred, and the propyl can also be used. Do not use alcohol
or formalin.
l 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.
l Keep the injector nozzle as close as possible to the connector surface without touching it.
----End
7.3 Browsing Alarms, Abnormal Events, and Performance

Events
The Web LCT is used to browse alarms, abnormal events, and performance events at the NE
layer.
7.3.1 Checking the NE Status
You can learn about the basic information such as whether the NE fails to communicate with
the NMS and whether any alarms are reported by checking the NE status.
7.3.2 Checking the Board Status
You can learn about the board status in a visual manner by checking the slot diagram.
You can find the faults that occur on the equipment by browsing current alarms.

OptiX RTN 620
7.3.4 Browsing History Alarms

You can know the faults that occur on the equipment in a past period of time by browsing history
alarms.
Periodically browsing abnormal events helps you to find abnormalities in the equipment in time.
7.3.6 Browsing Current Performance Events
Periodically browsing the performance events helps you to check the long-term running status
of the equipment.
of the equipment.
7.3.8 Browsing the Performance Event Threshold-Crossing Records
You can learn about the threshold-crossing information of the performance events of an NE by
browsing the performance event threshold-crossing records.
7.3.1 Checking the NE Status

You can learn about the basic information such as whether the NE fails to communicate with
the NMS and whether any alarms are reported by checking the NE status.
Prerequisite

Web LCT
Procedure
Step 1 In NE List, check Communication Status of the NE.
In normal cases, Communication Status is Normal.
Step 2 If Login Status of the NE is Not Logged In, log in to the NE.
1. Select the NE, and choose NE Login.
The NE Login dialog box is displayed.
2. Specify User Name and Password.
l The user name is lct by default.
l The password of user lct is password by default.
NOTE
User lct has the authority at the system level.

3. Click OK.
The Login Status column switches to Logged In.
Step 3 Click NE Explorer.
Step 4 Check NE STATE above Slot Layout.

OptiX RTN 620
In normal cases, NE STATE is Running.
----End
7.3.2 Checking the Board Status

You can learn about the board status in a visual manner by checking the slot diagram.
Prerequisite

Web LCT
Procedure
Step 1 Double-click an NE in the Main Topology. Then, the Slot Layout is displayed. The NE should
be in Running Status.
Step 2 Click the icon. Then, the legend description is displayed.

Step 3 Check the running status of the boards according to the legend description. If a board is running
normally, the board icon should be green.
----End

You can find the faults that occur on the equipment by browsing current alarms.
Prerequisite
l The communication between the Web LCT and the NE must be normal.

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

OptiX RTN 620
TIP
You can also click an alarm indicator on the toolbar to display the alarms of the specific severity.
From left to right, the alarm indicators and related alarm severities are as follows:
l Red: critical alarm
l Orange: major alarm
l Yellow: minor alarm
l Purple: warning
l Light blue: abnormal event
NOTE
The number shown by each indicator indicates the number of current network-wide alarms, which are not
cleared, of the specific severity.
The Browse Current Alarms tab is displayed by default.
Step 2 Browse the displayed alarms.
Step 3 Select the newly generated alarms, record the details of the alarms.
Step 4 Notify the troubleshooting personnel to clear the alarms in time.
----End
Related Information
A current alarm refers to an alarm that is not cleared.
7.3.4 Browsing History Alarms

You can know the faults that occur on the equipment in a past period of time by browsing history
alarms.
Prerequisite
l The Web LCT is in normal communication with the NE.

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 Click the Browse History Alarm tab.
Step 3 Click Filter. The Filter dialog box is displayed.
1. In Severity, select the alarm severity to be queried.
2. In Alarm Type, select the alarm type.
3. In Rising Time, specify the alarm generation time.

OptiX RTN 620
4. In Cleared Time, specify the alarm clearance time.

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 Optional: Click Save As. Then, the history alarms are saved and archived as a file.
----End
Related Information
A history alarm is an alarm that has been cleared. An NE stores a maximum of 1,000 history
alarms.

Periodically browsing abnormal events helps you to find abnormalities in the equipment in time.
Prerequisite

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 icon to switch to the Browse Abnormal
Events tab page.
Step 2 Click Filter. The Filter dialog box is displayed.

1. Set Level and Type.
2. In Abnormal Event, select Select All.
Step 3 Click OK.
Step 4 Browse the abnormal events.
Step 5 Optional: Click Save As. Then, the abnormal events are saved and archived as a file.
----End
Related Information
An abnormal event is an abnormality that arises in the system at a particular time and not an
abnormality that persists for a long time. Being different from alarms, an abnormal event has
only occurrence time, with clearance time not provided.

OptiX RTN 620
7.3.6 Browsing Current Performance Events

of the equipment.
Prerequisite
l The performance monitoring function must be enabled.

Web LCT
Procedure
Step 1 In the NE Explorer, select the required board from the Object Tree, and then choose
Performance > Current Performance from the Function Tree.
Step 3 Select 15-Minute in the Monitor Period field.
Step 4 Click Count, select all the performance events, and select Consecutive Severely Errored
Second in Display Options.
Step 5 Click Query.
Step 6 Browse the current performance events.

In normal cases, no bit error performance events is displayed, and the number of pointer
justification events is less than six per day.
Step 7 Click Gauge, select all the performance events, and select Current Value and Maximum/
Step 8 Click Query.
Step 9 Browse the current performance events.

Compared with the history records, the gauge indicators, such as board temperature, do not
change drastically.
Step 10 Set Monitor Period to 24-Hour.
Step 11 Repeat steps Step 4 to Step 9 query the performance events in a period of 24 hours.
----End
Related Information
between the start time of the monitoring period and the current time.

OptiX RTN 620

of the equipment.
Prerequisite

Web LCT
Procedure
Step 1 Select a specific board from the NE Explorer, and choose Performance > History
Step 3 Select 15-Minute after Monitor Period.
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 Zero Data in Display
Options.

The system displays the text file that lists the history performance events.
NOTE
You can also save the text file as required.
Step 10 Click Save As to save the performance events.

The system displays the text file that lists the history performance events.
NOTE
You can also save the text file as required.
Step 11 Select 24-Hour after Monitor Period.
Step 12 Repeat Step 4 to Step 10 to query the history performance events in a period of 24 hours.
----End

OptiX RTN 620
Related Information
The history performance event refers to a performance event whose statistics period ends in the
past. Only the performance events on the NE side can be queried using the Web LCT. Currently,
the NE can store thirty 24-hour and six hundreds and seventy-two 15-minute history performance
events related to the receive level and bit errors on the radio link; the NE can store a maximum
of six 24-hour and sixteen 15-minute other history performance events.
7.3.8 Browsing the Performance Event Threshold-Crossing Records

You can learn about the threshold-crossing information of the performance events of an NE by
browsing the performance event threshold-crossing records.
Prerequisite

Web LCT
Procedure
Step 1 In the NE Explorer, select the required board, and then choose Performance > Performance
Threshold-Crossing from the Function Tree.
The Performance Threshold-Crossing dialog box is displayed.
Step 4 Specify the start time and the 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 In Performance Event Type, select Select All.
Step 6 Optional: Specify Display Options.
Step 7 Click Query. Browsing the threshold-crossing performance events.
NOTE
Step 10 Repeat steps Step 4 to Step 8 to query the performance events in a period of 24 hours.
----End

OptiX RTN 620
7.4 Querying a Report

You can obtain the version, manufacture, and radio link information of all the boards by querying
the corresponding report.
7.4.1 Querying a Board Information Report Through the Web LCT
You can know the PCB version, logic version, and software version of each board by querying
a board information report.
7.4.2 Querying a Board Manufacture Information Report
You can know the manufacture information of each board and the SFP module by querying a
board manufacture information report.
7.4.3 Querying the Status of a Radio Link
The Web LCT supports the end-to-end management of a microwave link. You can query the
information about the two ends of a radio link in an interface.
7.4.1 Querying a Board Information Report Through the Web LCT

You can know the PCB version, logic version, and software version of each board by querying
a board information report.
Prerequisite

Web LCT
Procedure
Step 1 Select an NE from the Object Tree in the NE Explorer.
Step 2 Choose Report > Board Information Report from the Function Tree.
Step 3 All the board version information of the NE is displayed in the Board Information Report tab
page.
The text file that describes the board information is displayed on the Internet Explorer.
NOTE
You can save the text file as required.
----End
Related Information
Focus on the PCB version, logic version, and software version of each board when you query
the board information.

OptiX RTN 620
7.4.2 Querying a Board Manufacture Information Report

You can know the manufacture information of each board and the SFP module by querying a
board manufacture information report.
Prerequisite

Web LCT
Procedure
Step 2 Choose Report > Board Detail Information Report from the Function Tree.
Step 3 All the board manufacture information of the NE is displayed in the Board Detail Information
Report tab page.
The text file that describes the detailed board information is displayed on the Internet Explorer.
NOTE
You can save the text file as required.
----End
7.4.3 Querying the Status of a Radio Link

The Web LCT supports the end-to-end management of a microwave link. You can query the
information about the two ends of a radio link in an interface.
Prerequisite
l The NE user must have the authority of Maintenance Level or higher.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer, and then choose Configuration > Link
Configuration from the Function Tree.
Step 2 Click the IF/ODU Configuration tab page, right-click the corresponding IF board, and then
choose HOP Management from the shortcut menu.
Step 3 In the HOP Management Function Tree, choose Configuration > Link Configuration, and
then click the IF/ODU Configuration tab.
Step 4 Select the corresponding IF board in the IF/ODU Configuration tab page, and then click
Query.

OptiX RTN 620
The configuration information of the links at two ends is displayed.
Step 5 Check whether the configuration information of the link at one end is consistent with the
configuration information of the link at the other end and whether the configuration information
of the links at the two ends is correct.
----End
7.5 Software loopback

Software loopback refers to the loopback operation that is implemented by using the NMS. In
the OptiX RTN 620, the SDH optical interface board, SDH electrical interface board, PDH
interface board, IF board, Ethernet service processing board, and ODU support loopback.
7.5.1 Setting Loopback for the SDH Optical Interface Board

The optical interface board (SL1/SD1/SL4) supports the optical interface inloop and the VC-4
path outloop. The SL4 board also supports the VC-4 path inloop.
7.5.2 Setting Loopback for the SDH Electrical Interface Board
The electrical interface board supports the electrical interface inloop/outloop and the VC-4 path
outloop.
7.5.3 Setting Loopback for the Tributary Board
The tributary board supports the tributary inloop/outloop.
7.5.4 Setting Loopback for the IF Board
The loopbacks on the IF board are classified into IF port loopback, port loopback, and VC-4
path loopback. The IF1A/IF1B board supports the IF port inloop/outloop and VC-4 path inloop.
The IF0A/IF0B board supports the IF port inloop/outloop and port inloop/outloop. The IFX
board supports port inloop/outloop and VC-4 path inloop. The IFH2 board supports the IF port
outloop and the port inloop/outloop.
7.5.5 Setting Loopback for the Ethernet Service Processing Board
The Ethernet service processing board supports the Ethernet port inloop (at the MAC layer and
PHY layer) and VC-3 path inloop and outloop.
7.5.6 Locating the Fault by Performing Loopbacks
Loopback is a common method to locate the fault.
7.5.1 Setting Loopback for the SDH Optical Interface Board

The optical interface board (SL1/SD1/SL4) supports the optical interface inloop and the VC-4
path outloop. The SL4 board also supports the VC-4 path inloop.
Prerequisite
Context
The optical interface inloop is a process where the signals at an SDH port are looped back at the
overhead processing unit towards the backplane.

OptiX RTN 620
Figure 7-5 Inloop
SDH optical
Backplane interface board
SDH
The optical interface outloop is a process where the signals at an SDH port are looped back at
the overhead processing unit towards the remote equipment.
Figure 7-6 Outloop
SDH optical
SDH
The VC-4 path outloop is a process where the signals on a VC-4 path are looped back at the
logic processing unit towards the remote equipment.
Figure 7-7 VC-4 path outloop
SDH optical
Backplane
interface board
VC-4
The VC-4 path inloop is a process where the signals on a VC-4 path are looped back at the logic
processing unit towards the backplane.

OptiX RTN 620
Figure 7-8 VC-4 path inloop
SDH optical
Backplane
board
VC-4
Precautions
CAUTION
l The services may be interrupted at the port or on the path where the loopback is performed.
l A software loopback may be cleared automatically after some time (by default, it is cleared
within five minutes). For details, see 7.11 Setting the Automatic Release Function.
Procedure
Step 1 Select the SDH optical interface board from the Object Tree.
Step 2 Choose Configuration > SDH Interface from the Function Tree.
Step 3 Choose By Function, and select the loopback mode from the drop-down list.
To Perform Select
Optical interface loopback Optical (Electrical) Interface Loopback
VC-4 path loopback VC-4 Loopback
Step 4 Set the loopback status of the port or path according to the requirements.
Step 5 Click Apply.
The system displays a prompt dialog box for confirmation.
Step 6 Click OK.
----End
7.5.2 Setting Loopback for the SDH Electrical Interface Board

The electrical interface board supports the electrical interface inloop/outloop and the VC-4 path
outloop.
Prerequisite

OptiX RTN 620
Context
The electrical interface inloop is a process where the signals at an SDH port are looped back at
the coding/decoding unit towards the backplane.
Figure 7-9 Inloop
SDH electrical
SDH
The electrical interface outloop is a process where the signals at an SDH port are looped back
at the coding/decoding unit towards the remote equipment.
Figure 7-10 Outloop
SDH electrical
Backplane
interface board
SDH
logical processing unit towards the remote equipment.
SDH electrical
VC-4

OptiX RTN 620
Precautions
CAUTION
Procedure
Step 1 Select the SDH electrical interface board from the Object Tree.
Step 2 Choose Configuration > SDH Interface from the Function Tree.
To Perform Select
Optical interface loopback Optical (Electrical) Interface Loopback
Step 5 Click Apply.
Step 6 Click OK.
----End
7.5.3 Setting Loopback for the Tributary Board

The tributary board supports the tributary inloop/outloop.
Prerequisite
Context
The tributary inloop is a process where the signals at a PDH port are looped back at the coding/
decoding unit towards the backplane.

OptiX RTN 620
Figure 7-12 Inloop
Backplane PDH interface board
PDH
The tributary inloop is a process where the signals on a tributary path are looped back at the
PDH interface board of the local IDU towards the remote equipment.
Figure 7-13 Outloop
Backplane PDH interface board
PDH
Precautions
CAUTION
Procedure
Step 1 Select the PDH interface board from the Object Tree.
Step 2 Choose Configuration > PDH Interface from the Function Tree.
Step 3 Choose By Function, and select Tributary Loopback from the drop-down list.
Step 5 Click Apply.


OptiX RTN 620
Step 6 Click OK.

----End
7.5.4 Setting Loopback for the IF Board

The loopbacks on the IF board are classified into IF port loopback, port loopback, and VC-4
path loopback. The IF1A/IF1B board supports the IF port inloop/outloop and VC-4 path inloop.
The IF0A/IF0B board supports the IF port inloop/outloop and port inloop/outloop. The IFX
board supports port inloop/outloop and VC-4 path inloop. The IFH2 board supports the IF port
outloop and the port inloop/outloop.
Prerequisite
Context
The IF port inloop is a process where the IF signals are looped back at the modem unit towards
the backplane.
Figure 7-14 Inloop
Backplane IF board
IF signal
The IF port outloop of the IDU 620 is a process where the IF signals are looped back at the
modem unit of the board towards the remote equipment.
Figure 7-15 Outloop
Backplane IF board
IF signal
The port inloop is a process where the microwave frame baseband signals are looped back at
the MUX/DEMUX unit of the board towards the backplane.

OptiX RTN 620
Figure 7-16 Inloop
Backplane IF board
Microwave
baseband signal
The port outloop is a process where the microwave frame baseband signals are looped back at
the MUX/DEMUX unit of the board towards the remote equipment.
Figure 7-17 Outloop
Backplane IF board
Microwave
baseband
signal
The VC-4 path inloop is a process where the signals on a VC-4 path are looped back at the logical
processing unit of the board towards the backplane.
Backplane IF board
VC-4 signal

OptiX RTN 620
Precautions
CAUTION
l To perform the software loopback on the protection IF board of 1+1 HSB/FD/SD, switch the
protection IF board to the working state manually. Otherwise, the operation may fail.
l Before performing the loopback operation for the IFH2, disable the AM function at the two
ends of a link.
Procedure
Step 1 Select the IF board from the Object Tree.
Step 2 Select the corresponding menu from the Function Tree according to the loopback mode.
To Perform Choose
IF port loopback Configuration > IF Interface.
Port loopback Configuration > Digital Interface
VC-4 path loopback Configuration > Digital Interface
To Perform Choose
IF port loopback IF Port Loopback
Port loopback Optical (Electrical) Interface Loopback
Step 5 Click Apply.

Step 6 Click OK.
----End
7.5.5 Setting Loopback for the Ethernet Service Processing Board

The Ethernet service processing board supports the Ethernet port inloop (at the MAC layer and
PHY layer) and VC-3 path inloop and outloop.
Prerequisite

OptiX RTN 620
Context
The Ethernet port MAC inloop is a process where the Ethernet physical signals are looped back
at the service processing module of the board at the MAC layer toward the backplane. The
Ethernet port PHY inloop is a process where the Ethernet frame signals are looped back at the
interface module of the board at the MAC layer toward the backplane.
Figure 7-19 Inloop
Ethernet service
Backplane
processing board
MAC PHY
The VC-3 path inloop is a process where the signals on a VC-3 path are looped back at the logical
processing unit of the board towards the backplane.
Backplane Ethernet service

processing board
VC-3 signal
logical processing unit towards the remote equipment.
Ethernet service
Backplane
processing board
VC-3 signal

OptiX RTN 620
Precautions
CAUTION
Procedure
Step 1 Select the Ethernet processing board from the Object Tree.
Step 2 Select the corresponding menu from the Function Tree according to the loopback mode.
To perform Choose
PHY loopback Configuration > Ethernet Interface Management > Ethernet
Interface > External Port > Basic Attributes
MAC loopback Configuration > Ethernet Interface Management > Ethernet
Interface > External Port > Basic Attributes
VC-3 path loopback Configuration > SDH Interface
Step 3 Select the loopback mode.
To perform Select
PHY loopback PHY Loopback
MAC loopback MAC Loopback
VC-3 path loopback VC-3 loopback
Step 5 Click Apply.

Step 6 Click OK.
----End
7.5.6 Locating the Fault by Performing Loopbacks

Loopback is a common method to locate the fault.
Prerequisite

OptiX RTN 620
Service Trail
Figure 7-22 shows how to locate a fault by performing the loopback.
Figure 7-22 Service Trail

PDH Tributary PXC IF Board ODU ODU IF Board PXC SDH Interface
Board Board
NE1 NE2
PDH Tributary PXC IF Board ODU ODU IF Board PXC SDH Interface
Board
Board
NE4 NE3
Fiber
Procedure
Step 1 If the services are available on the radio links, first perform the inter-station loopback to locate
the fault on a certain hop when using the loopback method.
1. Set the outloops for the SDH optical interface boards on NE2 and NE3, and then perform
the inter-station loopback to locate the fault.
Step 2 After the fault is located to a certain radio link, perform the intra-station loopback to locate the
fault to a certain NE or board.
1. Set inloop for the IF board on the NEs at two ends of the radio link where the fault occurs,
and then locate the fault to the service receiver or the radio link.
2. If the fault is located in the service receiver, set outloop for the PDH tributary board to
locate the fault to the interface board or the cross-connect board.
3. If the radio link is faulty, replace the board to locate the fault to the IF board or the ODU.
----End
7.6 Resetting
Resetting is an important method for handling software faults. The OptiX RTN 620 supports
cold resetting, warm resetting, and SCC resetting.
7.6.1 Cold Resetting

OptiX RTN 620
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.
7.6.2 Warm Resetting
Warm resetting is a process where the board software is reset but the board is not re-initiated.
Except that the EMS6 and the EFP6 have their independent board software, the software modules
of all other boards are located in the SCC.
7.6.3 SCC Resetting
SCC resetting is a process in which all the software modules on the SCC are reset, the SCC is
re-initiated.
7.6.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
Precautions
CAUTION
Cold resetting causes service interruption because it is similar to the procedure of removing and
inserting a board.
Procedure
Step 1 In Slot Layout of the Web LCT, 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
7.6.2 Warm Resetting

Warm resetting is a process where the board software is reset but the board is not re-initiated.
Except that the EMS6 and the EFP6 have their independent board software, the software modules
of all other boards are located in the SCC.
Prerequisite

OptiX RTN 620
Precautions
During the warm resetting, the running services are not affected.
Procedure
Step 1 In the Slot Layout of the Web LCT, right-click the board to be reset.
Step 2 Choose Warm Resetting in the popup menu.
The system displays the Operation Succeed dialog box.
Step 3 Click Close.
----End
7.6.3 SCC Resetting

SCC resetting is a process in which all the software modules on the SCC are reset, the SCC is
re-initiated.
Prerequisite
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 Web LCT, right-click the SCC to be reset.
Step 2 Choose SCC Reset from the shortcut menu.
A prompt dialog box is displayed.
Step 3 Click OK.
The system displays the Operation Succeed dialog box.
Step 4 Click Close.
----End
7.7 PRBS Test

The pseudorandom binary sequence (PRBS) test is an important method for network
maintenance and self-check.
7.7.1 PRBS Test of the Tributary Board

In the absence of a special test tool, you can perform the PRBS test by using the embedded test
system on the PDH interface board.

OptiX RTN 620
7.7.2 PRBS Test of the IF Board

system on the IFH2 IF board.
7.7.1 PRBS Test of the Tributary Board

system on the PDH interface board.
Prerequisite
Context
The OptiX RTN 620 supports the PRBS test in the tributary direction and the cross-connect
direction.
The PRBS test in the tributary direction can be used to check the connection between the tributary
board and the DDF, as shown in Figure 7-23.
Figure 7-23 PRBS test in the tributary direction

DDF frame PDH interface board
PRBS
Transmitter
PRBS
Recevicer
1 Inloop at the DDF frame
The PRBS test in the cross-connect direction can be used to check the connection between the
tributary board and the remote NE, as shown in Figure 7-24.

OptiX RTN 620
Figure 7-24 PRBS test in the cross-connect direction

a) IF board working as line board
PDH interface Cross-connect

board board IF board IF board
PRBS OUT
Transmitter
1 2 3
PRBS
IN
Receiver
Local NE Remote NE
VC4 inloop or
1 2 IF port inloop 3 IF port outloop
port inloop
b) SDH optical/electrical board working as line board
PDH interface Cross-connect SDH optical/ SDH optical/

board board electrical board electrical board
PRBS OUT
Transmitter
1 2 3
PRBS
IN
Receiver
Local NE Remote NE
1 VC4 inloop 2 Port inloop 3 Port outloop
Precautions
CAUTION
l During the PRBS test, the services in the tested path are interrupted.
l The PRBS test can be performed only in one path and in one direction.
Procedure
Step 1 Set the loopback at the proper location. For details, see Figure 7-23 and Figure 7-24.
Step 2 Select an E1 interface board from the Object Tree in the NE Explorer.

OptiX RTN 620
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
l The PRBS test supports three time units: one second, 10 minutes, and one hour.
l 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 The operation may interrupt the service. Are you sure to continue? dialog box is
displayed.
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 the PRBS test can be normal, error, or invalid.

l Normal: It indicates that the path is working properly. The number of PRBSs should be zero, and the
curve should be in green.
l Error: It indicates that the path has errors. The number of PRBSs should be greater than zero, and the
curve should be in red.
l Invalid: It indicates that no bit is received. The curve should be in yellow.
----End
7.7.2 PRBS Test of the IF Board

system on the IFH2 IF board.
Prerequisite
Precautions
CAUTION
l During the PRBS test, the services in the tested path are interrupted.
l The PRBS test can be performed only in one path and in one direction.
l To perform the PRBS test for the protection IF board of the 1+1 HSB/FD/SD, you must
switch the protection IF board to the working state manually.

OptiX RTN 620
Procedure
Step 1 See 7.5.4 Setting Loopback for the IF Board to perform the inloop on the ODU.
Step 2 Select an IF board from the Object Tree in the NE Explorer.
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
l The PRBS test supports three time units: one second, 10 minutes, and one hour.
l 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 The operation may interrupt the service. Are you sure to continue? dialog box is
displayed.
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 the PRBS test can be normal, error, or invalid.

l Normal: It indicates that the path is working properly. The number of PRBSs should be zero, and the
curve should be in green.
l Error: It indicates that the path has errors. The number of PRBSs should be greater than zero, and the
curve should be in red.
l Invalid: It indicates that no bit is received. The curve should be in yellow.
----End
7.8 Querying the License Capacity

You can check whether the loaded license file meets the requirements by querying the license
capacity.
Prerequisite

Web LCT

OptiX RTN 620
Procedure
Step 2 Choose Configuration > License Management from the Function Tree.
Step 3 Click Query in the License Management tab page.
Step 4 Browse the license information that is displayed.
----End
7.9 Setting the State of a Laser

A laser on the port of the SDH optical interface board transmits optical signals only when the
laser is turned on. You can turn a laser on or off by using the NMS.
Prerequisite
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 click 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 then specify Laser Switch.
Step 6 Click Apply.
----End
7.10 Setting the ALS function

The SDH optical interface board supports the automatic laser shutdown (ALS) function. It can
turn off a laser when it does not carry services, the optical fiber is faulty, or the received optical
signals are lost.
Prerequisite
Procedure
Step 1 Select an SDH optical interface board from the Object Tree in the NE Explorer.

OptiX RTN 620
Step 2 Choose Configuration > Automatic Laser Shutdown from the Function Tree, and then click
the Laser Auto Shutdown tab.
Step 3 Select Enable for Auto Shutdown.
Step 4 Click Apply to save the settings.
----End
7.11 Setting the Automatic Release Function

To protect the NM and NE communication from improper operations, an NE supports the
automatic release of the ODU mute, loopback, and other operations that require you to exercise
caution. The automatic release time is five minutes by default. You can set whether to enable
the automatic release function and the automatic release time using the NMS.
Prerequisite
Procedure
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 to complete the settings for the automatic release function.
----End
7.12 Switching PXC Boards

Manual PXC switching is an important maintenance operation.
Prerequisite
l Two PXC boards must be configured.
l The user must have the system level authority.
Procedure
Step 1 Select an NE from the Object Tree in the NE Explorer, and then choose Configuration > Board
1+1 Protection from the Function Tree.
Step 2 Select the ID of the protection group where the PXC board resides in the Board 1+1
Protection tab page.
Step 3 Click Working/Protection Switching.

OptiX RTN 620
Step 4 Click OK to perform switching.

Step 5 Click Query.
The switching status is displayed.
----End
7.13 Configuring Performance Monitoring Status of NEs

By default, the performance monitoring of NEs is enabled. You can disable or enable this
function manually and set the period of the performance monitoring of NEs manually.
Prerequisite
The NE user must have the authority of Operation Level or higher.

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE and then choose Performance > NE Performance Monitor
Time from the Function Tree.
Step 2 Set the parameters of NE performance monitoring.
1. Select 15-Minute or 24-Hour.
2. Select Enable or Disable in Set 15-Minute Monitoring or Set 24-Hour Monitoring.
3. Set the start time and end time of the performance monitoring of NEs.
NOTE
l Set 15-Minute Monitoring and Set 24-Hour Monitoring are generally set to Enable.
l You can specify the start time of the performance monitoring function, only after selecting Enable in
the Set 15-Minute Monitoring or Set 24-Hour Monitoring area.
l You can specify the end time of the performance monitoring function, only after selecting Enable and
then selecting To in the Set 15-Minute Monitoring or Set 24-Hour Monitoring area.

OptiX RTN 620
Step 3 Click Apply.
----End
7.14 Querying the Impedance of an E1 Channel

The impedance of an E1 channel is 75 ohms or 120 ohms, which can be queried through the
NMS but cannot be set through the NMS.
Prerequisite

Web LCT
Procedure
Step 1 Select A PDH tributary board from the Object Tree in the NE Explorer.
Step 2 Choose Configuration > PDH Interface from the Function Tree.
Step 3 Select By Board/Port(Channel).
Step 4 Select Port in the list.
Step 5 Select a port, and check Port Impedance.
----End

OptiX RTN 620
7.15 Using Ethernet Test Frames

By using the Ethernet test frames on the OptiX RTN 620, you can check the connectivity of the
VCTRUNK.
Prerequisite
l The service traffic must be encapsulated or mapped through the GFP method.
Context
For test purposes, the Ethernet board transmits, at an interval of about one second, one specific
GFP management frame or Ethernet frame to the opposite Ethernet board, which then returns
with a response frame. After receiving the response frame, the local Ethernet board can determine
the connectivity of the VCTRUNK in between.
Figure 7-25 Ethernet test frames between Ethernet boards
Test frame
Local Remote
Ehernet Ehernet
board board
Response frame
Precautions
CAUTION
Do not use the test frames when the network traffic is heavy.
Procedure
Step 1 Select an Ethernet board from the Object Tree in 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 then select Clear All Counters from the
drop-down list.
Step 4 Specify Send Mode and Frames to Send.

NOTE
It is recommended that you choose "Burst mode". A maximum of 10 frames can be transmitted each time.

OptiX RTN 620
Step 5 Click Apply.

The test frames start to be received and transmitted.
Step 6 When Status changes to Finished Sending, click Query.
Step 7 View Counter of Frames Sent and Counter of Received Response of Test Frame.
Test frames are used to check the network connectivity. If certain test frames are lost but no
alarm is reported on the SDH side, you can infer that the network connectivity is in a good
condition. If no test frame is received, you can infer that network is faulty.
----End
Related Information
If you choose the "Continue" mode, the local port transmits test frames continuously after you
start the test until the mode changes to "Disable".
7.16 Querying the Working Status of an Ethernet Port

Through the operation, you can learn about the enable/disable state, loopback status, and the
actual working mode of an Ethernet port.
Prerequisite

Web LCT
Procedure
Step 1 Select an Ethernet board or IFH2 board from the Object Tree.
Step 2 Choose Configuration > Ethernet Interface Management > Ethernet Interface from the
Function Tree.
Step 3 Select External Port.
Step 4 By default, click the Basic Attributes tab page.
Step 5 Check Enabled/Disabled, Working Mode, and Port Physical Parameters of the associated
port.
----End
7.17 Setting the Threshold of Received Traffic Flow on an

Ethernet Port
The FLOW_OVER alarm is reported when the traffic flow received on an Ethernet port exceeds

OptiX RTN 620
Prerequisite

Web LCT
Context
This operation can be performed on the PORT port of the EMS6 board.
Procedure
Step 1 Select the required Ethernet board from the Object Tree.
Step 2 Choose Configuration > Ethernet Interface Management > Ethernet Interface from the
Function Tree.
Step 3 Select External Port.
Step 4 Select the Advanced Attributes tab.
Step 5 Set Zero-Flow Monitor to Enable.
Step 6 Set Flow Threshold(Mbps).
Step 7 Optional: Set Zero-Flow Monitor Interval(min).
l If this parameter takes the default value of 0, the FLOW_OVER alarm is reported whenever
the traffic flow received on the port exceeds Flow Threshold(Mbps).
l If the value of this parameter is not 0, the FLOW_OVER alarm is reported only when the
traffic flow received on the port within a period of Zero-Flow Monitor Interval(min) always
exceeds Flow Threshold(Mbps).
Step 8 Click Apply.
----End
7.18 Performing Statistics for the Traffic Flow on an Ethernet

Port
You can perform this operation to perform statistics for the traffic flow on an Ethernet port within
a specified period.
Prerequisite
l The flow monitoring function must be enabled on the associated Ethernet port. To enable
the flow monitoring function on a port, do as follows:
1. Select the required Ethernet board from the Object Tree.

OptiX RTN 620
2. Choose Performance > Ethernet Port Traffic Monitor from the Function Tree.
3. Select the Set Monitoring tab.
4. Set Monitor Status to Enabled for the Ethernet port.

Web LCT
Context
l After the flow monitoring function is enabled, the system saves the statistics about the
received traffic and transmitted traffic with an interval of 15 minutes. In normal cases, the
system stores the statistics that are collected in the last 30 days. In the system, every
measurement entry shows the average transmit rate and average receive rate within a period
of 15 minutes. You can query the statistics in the last 30 days.
l This operation can be performed on the PORT port and VCTRUNK port of the EMS6
board.
Procedure
Step 2 Choose Performance > Ethernet Port Traffic Monitor from the Function Tree.
Step 3 Select the Query traffic tab.
Step 4 Set the object to be queried, the required time, and display mode, and then click Query.
The system displays the query result in a table or in a graph.
----End
7.19 Performing Statistics for the Traffic Flow of Ethernet

Services
You can perform this operation to perform statistics for the traffic flow of Ethernet services
within a specified period.
Prerequisite
l The flow monitoring function must be enabled. To enable the flow monitoring function,
do as follows:
1. Select the required Ethernet board from the Object Tree.
2. Choose Configuration > QoS Management > Flow Management from the Function
Tree.
3. Set Monitor Status to Enabled for the traffic flow.

Web LCT

OptiX RTN 620
Context
l After the flow monitoring function is enabled, the system saves the statistics about the
received traffic and transmitted traffic with an interval of 15 minutes. In normal cases, the
system stores the statistics that are collected in the last 30 days. In the system, every
measurement entry shows the average transmit rate and average receive rate within a period
of 15 minutes. You can query the statistics in the last 30 days.
l This operation can be performed on the EMS6 board.
Procedure
Step 2 Choose Performance > Flow Traffic Monitor from the Function Tree.
Step 3 Set the object to be queried, the required time, and display mode, and then click Query.
The system displays the query result in a table or in a graph.
----End

OptiX RTN 620
Maintenance Guide A Alarm Reference
A Alarm Reference
Alarms are important indicators when exceptions occur on the equipment. This topic describes
all the possible alarms on the OptiX RTN 620 and how to handle these alarms.
A.1 Alarm List

The following table lists all the possible alarms generated by the OptiX RTN 620 in alphabetical
order.
A.2 Alarms and Handling Procedures
This topic describes all the alarms on the OptiX RTN 620 in an alphabet order and how to handle
these alarms.
Issue 01 (2009-12-30) Huawei Proprietary and Confidential A-1

OptiX RTN 620
A Alarm Reference Maintenance Guide
A.1 Alarm List

The following table lists all the possible alarms generated by the OptiX RTN 620 in alphabetical
order.
Table A-1 Alarm list

Alarm Name Description Alarm Source
Severit
y
A_LOC Loss of clock on the adding bus Major PO1, PH1, PD1, PL3
APS_MANUAL_S MSP protocol stopped manually Minor SCC

TOP
ALM_GFP_dCSF Loss of GFP client signals Critical EFT4, EMS6, EFP6
ALM_GFP_dLFD GFP frames are out of frame. Major EFT4, EMS6, EFP6
AM_DOWNSHIFT Downshift of AM modes Major IFH2
APS_FAIL The APS protection switching Major SCC

fails.
APS_INDI Indication of the APS protection Major SCC

switching
AU_AIS AU alarm indication Major SD1, SL1, SDE,

SLE, IF1A, IF1B,
IFX, SL4
AU_LOP Loss of AU pointers Major SD1, SL1, SDE,

SLE, IF1A, IF1B,
IFX, SL4
B1_EXC Excessive regenerator section Minor SD1, SL1, SDE,

(B1) errors SLE, IF1A, IF1B,
IF0A, IF0B, IFX,
SL4
B1_SD Signal degradation due to Minor SD1, SL1, SDE,

excessive regenerator section SLE, IF1A, IF1B,
(B1) errors IF0A, IF0B, IFX,
SL4
B2_EXC Excessive multiplex section (B2) Major SD1, SL1, SDE,

errors SLE, IF1A, IF1B,
IFX, SL4

excessive multiplex section (B2) SLE, IF1A, IF1B,
errors IFX, SL4
A-2 Huawei Proprietary and Confidential Issue 01 (2009-12-30)

OptiX RTN 620

Severit
y
B3_EXC Excessive higher order path (B3) Major SD1, SL1, SDE,
bit errors SLE, IF1A, IF1B,
IFX, SL4, PL3
B3_EXC_VC3 Excessive VC-3 path (B3) bit Major EFT4, EMS6

errors

excessive higher order path (B3) SLE, IF1A, IF1B,
errors IFX, SL4, PL3
B3_SD_VC3 Signal degradation due to Minor EFT4, EMS6

excessive VC-3 path (B3) bit
errors
BD_NOT_INSTAL The logical board is not added on Minor SCC

LED the NMS.
BD_STATUS Board not in position Major SD1, SL1, SDE,

SLE, IF1A, IF1B,
PO1, PH1, EFT4,
EMS6, PXC, ODU,
FAN, EOW, IF0A,
IF0B, IFX, PD1,
SL4, IFH2, EFP6
BIP_EXC Excessive BIP errors Minor PO1, PH1, EFT4,

EMS6, IF0A, IF0B,
IFX, PD1, IFH2,
EFP6
BIP_SD Signal degradation due to Minor PO1, PH1, EFT4,

excessive BIP errors EMS6, IF0A, IF0B,
PD1, IFH2, EFP6
BOOTROM_BAD BOOTROM data check fails. Major SCC
C2_VCAIS C2 byte mismatch Minor PL3
CONFIG_NOSUP Configuration is not supported. Major ODU

PORT
DBMS_ERROR Errors in the processing of system Major SCC

databases
DBMS_PROTECT System databases in protection Critical SCC

_MODE mode
DOWN_E1_AIS Alarm indication of 2 Mbit/s Minor PO1, PH1, PD1

downstream signals
E1_LOC Loss of 2M clock in upstream Major PO1, PH1, PD1

signals

OptiX RTN 620

Severit
y
E1_LOS Loss of 2 Mbit/s line signals Minor PO1, PH1, PD1
ESN_INVALID Invalid ESN Major SCC
ETH_CFM_LOC Loss of connectivity Critical EMS6, EFP6
ETH_CFM_MISM Misconnection Critical EMS6, EFP6

ERGE
ETH_CFM_RDI Failure in receiving CCM Minor EMS6, EFP6

packets at the remote end
ETH_CFM_UNEX Errored frames Critical EMS6, EFP6

PERI
ETH_LOS Loss of Ethernet port connection Critical EFT4, EMS6, IFH2,

EFP6
ETHOAM_DISCO Discovery failure detected by Minor EFT4, EMS6, EFP6

VER_FAIL point-to-point Ethernet OAM
ETHOAM_RMT_ Severe fault detected by point-to- Minor EMS6, EFP6

CRIT_FAULT point Ethernet OAM at the
remote end
ETHOAM_RMT_ Remote loopback detected by Minor EMS6, EFP6

LOOP point-to-point Ethernet OAM
ETHOAM_RMT_ Remote Ethernet performance Minor EMS6, EFP6

SD degradation detected by point-to-
point Ethernet OAM
ETHOAM_SELF_ MAC port loopback detected by Major EMS6, EFP6

LOOP point-to-point Ethernet OAM
ETHOAM_VCG_S VCTRUNK loopback detected Minor EMS6, EFP6

ELF_LOOP by point-to-point Ethernet OAM
EX_ETHOAM_CC Loss of periodical connectivity Critical EMS6, EFP6

_LOS check packets
EX_ETHOAM_M Conflict of MPIDs Major EMS6, EFP6

PID_CNFLCT
EXT_SYNC_LOS Loss of external clock sources Critical SCC
F1PORT_FAILED Failure of synchronous data Minor SCC

interfaces
FAN_FAIL Failure of fan boards Major FAN
FCS_ERR FCS errors Critical EFT4, EMS6, EFP6

OptiX RTN 620

Severit
y
FLOW_OVER Excessive data traffic received by Minor EMS6

Ethernet ports
HARD_BAD Hardware errors Critical SD1, SL1, SDE,

SLE, IF1A, IF1B,
PO1, PH1, EFT4,
PXC, SCC, ODU,
EMS6, IF0A, IF0B,
IFX, PD1, SL4,
IFH2, EFP6
HP_CROSSTR Threshold-crossing performance Minor SD1, SL1, SDE,

event of the higher order path SLE, IF1A, IF1B,
IFX, SL4
HP_LOM Loss of multi-frames in the Major SD1, SL1, SDE,

higher order path SLE, IF1A, IF1B,
IFX, SL4
HP_RDI Higher order path remote defect Minor SD1, SL1, SDE,
indication SLE, IF1A, IF1B,
IFX, SL4
HP_REI Higher order path remote error Warning SD1, SL1, SDE,
IFX, SL4
HP_SLM Higher order path signal label Minor SD1, SL1, SDE,
mismatch SLE, IF1A, IF1B,
IFX, SL4
HP_TIM High order path trace identifier Minor SD1, SL1, SDE,
mismatch SLE, IF1A, IF1B,
IFX, SL4
HP_UNEQ Unequipped higher order path Minor SD1, SL1, SDE,

SLE, IF1A, IF1B,
IFX, SL4
HPAD_CROSSTR Adaptation performance Minor PO1, PH1, PD1

threshold-crossing of the higher
order path
IF_CABLE_OPEN IF cables are disconnected. Major IF1A, IF1B, IF0A,

IF0B, IFX, IFH2
IF_INPWR_ABN Abnormal power supplied by an Major ODU

IF board to an ODU
IF_MODE_UNSU Preset IF working mode not Major IF1A, IF1B

PPORTED supported

OptiX RTN 620

Severit
y
IN_PWR_HIGH Over high input optical power Critical SD1, SL1, SL4
IN_PWR_LOW Over low input optical power Critical SD1, SL1, SL4
J0_MM Trace identifier mismatch Minor SD1, SL1, SDE,

SLE, IF1A, IF1B,
SL4
K1_K2_M K1 and K2 mismatch Minor SCC
K2_M K2 mismatch Minor SCC
LAG_PORT_FAIL A port of an LAG fails Minor EMS6, EFP6
LAG_VC_PORT_ A VCG port of an LAG fails Minor EMS6, EFP6

FAIL
LASER_CLOSED A laser is closed. Major SD1, SL1, SL4
LASER_MOD_ER The type of the pluggable optical Major SD1, SL1, SL4
R_EX module on the board does not
match the type of the optical
interface.
LCAS_FOPR LCAS protocol fails in the Major EFT4, EMS6, EFP6

receive direction.
LCAS_FOPT LCAS protocol fails in the Major EFT4, EMS6, EFP6

transmit direction
LCAS_PLCR Loss of partial bandwidth in the Minor EFT4, EMS6, EFP6

LCAS receive direction
LCAS_PLCT Loss of partial bandwidth in the Minor EFT4, EMS6, EFP6

LCAS transmit direction
LCAS_TLCR Loss of total bandwidth in the Major EFT4, EMS6, EFP6

LCAS receive direction
LCAS_TLCT Loss of total bandwidth in the Major EFT4, EMS6, EFP6

LCAS transmit direction
LCS_LIMITED The capacity of the configured Major SCC, IFH2

services exceeds the range
permitted by the license file
LICENSE_LOST The license file is not detected Major SCC, IFH2
LICENSE_ERR License file check fails Major SCC, IFH2
LINK_ERR Data link errors Critical EMS6

OptiX RTN 620

Severit
y
LPS_UNI_BI_M The switching mode is single- Minor SCC

ended at one end and dual-ended
at the other end.
LOOP_ALM A loopback occurs. Minor SD1, SL1, SDE,

SLE, IF1A, IF1B,
PO1, PH1, EFT4,
EMS6, ODU, IF0A,
IF0B, IFX, PD1,
SL4, IFH2, EFP6
LPT_INEFFECT Link state pass-through function Major EFT4, EMS6

fails.
LPT_RFI Link state pass-through function Critical EFP6, EFT4, EMS6

fails at the remote end.
LP_CROSSTR Performance threshold-crossing Minor PO1, PH1, PD1

of the lower order path
LP_R_FIFO FIFO overflow at the receive side Minor PO1, PH1, PD1, PL3
of the lower order path
LP_RDI Lower order path remote defect Minor PO1, PH1, IF0A,
indication IF0B, PD1, PL3,
IFH2
LP_RDI_VC12 Remote defect indication in the Minor EFT4, EMS6, EFP6

VC-12 lower order path
LP_RDI_VC3 Remote defect indication in the Minor EFT4, EMS6

LP_REI Lower order path remote error Minor PO1, PH1, IF0A,
indication IF0B, PD1, PL3,
IFH2
LP_REI_VC12 Remote error indication in the Minor EFT4, EMS6, EFP6

LP_REI_VC3 Remote error indication in the Minor EFT4, EMS6

LP_RFI Lower order path remote failure Minor PO1, PH1, PD1,
indication IFH2
LP_SIZE_ERR Errors of TU specifications Minor PO1, PH1, PD1
LP_SLM Lower order path signal label Minor PO1, PH1, PD1, PL3
mismatch
LP_SLM_VC12 Signal label mismatch in the Minor EFT4, EMS6, EFP6


OptiX RTN 620

Severit
y
LP_SLM_VC3 Signal label mismatch in the Minor EFT4, EMS6

LP_T_FIFO FIFO overflow at the transmit Minor PO1, PH1, PD1, PL3
side of the lower order path
LP_TIM Lower order path trace identifier Minor PO1, PH1, PD1, PL3
mismatch
LP_TIM_VC12 Lower order path trace identifier Minor EFT4, EMS6, EFP6
mismatch at VC-12 level
LP_TIM_VC3 Lower order path trace identifier Minor EFT4, EMS6

mismatch at VC-3 level
LP_UNEQ Unequipped lower order paths Minor PO1, PH1, IF0A,

IF0B, PD1, PL3,
IFH2
LP_UNEQ_VC12 Unequipped VC-12 lower order Minor EFT4, EMS6, EFP6

paths
LP_UNEQ_VC3 Unequipped VC-3 lower order Minor EFT4, EMS6

paths
LSR_NO_FITED Laser not installed Critical SD1, SL1, SL4
LSR_WILL_DIE The life of the laser is close to the Critical SL4

end.
LTI Loss of all clock sources Major SCC
MOD_TYPE_MIS Port module type mismatch Critical EMS6

MATCH
MS_AIS Multiplex section alarm Major SD1, SL1, SDE,

IFX, SL4
MS_CROSSTR Multiplex section performance Minor SD1, SL1, SDE,

threshold-crossing SLE, IF1A, IF1B,
SL4
MS_RDI Multiplex section remote defect Minor SD1, SL1, SDE,

IFX, SL4
MS_REI Multiplex section remote error Warning SD1, SL1, SDE,

IFX, SL4

OptiX RTN 620

Severit
y
MSAD_CROSSTR Multiplex section adaptation Minor SD1, SL1, SDE,

performance threshold-crossing SLE, IF1A, IF1B,
IFX, SL4
MSSW_DIFFERE The active board and the standby Major SCC

NT board have inconsistent software.
MULTI_RPL_OW The ring network has multiple Minor EMS6

NER RPL_OWNER nodes.
MW_BER_EXC Excessive errors on radio links Minor IFH2
MW_BER_SD Signal degradation due to Minor IFH2

excessive errors on radio links
MW_FEC_UNCO FEC errors are uncorrectable. Minor IF1A, IF1B, IF0A,

R IF0B, IFX, IFH2
MW_LIM Label mismatch on radio links Major IF1A, IF1B, IF0A,

IF0B, IFX, IFH2
MW_LOF Loss of microwave frames Critical IF1A, IF1B, IF0A,

IF0B, IFX, IFH2
MW_RDI Remote defect indication on Minor IF1A, IF1B, IF0A,

radio links IF0B, IFX, IFH2
NESF_LOST Loss of NE software Critical SCC
NESTATE_INSTA The NE is in the installation state. Critical SCC

LL
NO_BD_SOFT No board software exists Critical SD1, SL1, SDE,

SLE, IF1A, IF1B,
PXC, IF0A, IF0B,
IFX, SL4, EMS6,
IFH2, EFP6
NP1_MANUAL_S The N+1 protection protocol is Minor SCC

TOP stopped manually.
NP1_SW_FAIL The N+1 protection switching Major SCC

fails
NP1_SW_INDI N+1 protection switching Major SCC

indication
OPM_FAIL Output of optical power fails. Major SL4
PROT_CONN_ER The connections of the protection Major EMS6, EFP6

R pair are abnormal.
PORT_MODULE_ Port not in position Major EMS6

OFFLINE

OptiX RTN 620

Severit
y
POWER_ALM Power module alarm Major PXC, SCC, FAN
P_AIS PDH interface signal alarm Major PL3

indication
P_LOS Loss of signals at PDH interfaces Major PL3
PS Indication of the triggered Major PO1, PH1, PD1

protection switching
RADIO_FADING_ Radio fading margin is Minor ODU

MARGIN_INSUFF insufficient.
RADIO_RSL_BEY Antennas are not aligned. Minor ODU

ONDTH
R_F_RST Reset of the receive FIFO Minor PO1, PH1, PD1
R_LOC Loss of clock on the receive line Critical SD1, SL1, SDE,
side SLE, IF1A, IF1B,
IF0A, IF0B, IFX,
SL4, IFH2
R_LOF Loss of frame on the receive line Critical SD1, SL1, SDE,
IF0A, IF0B, IFX,
SL4, IFH2
R_LOS Loss of signal on the receive line Critical SD1, SL1, SDE,
IFX, IF0A, IF0B,
SL4
R_S_ERR Errors in the received signal Critical PO1, PH1, PD1
RADIO_MUTE The radio transmitter is muted. Warning ODU
RADIO_RSL_HIG Over high radio receive signal Critical ODU

H level
RADIO_RSL_LO Over low radio receive signal Critical ODU

W level
RADIO_TSL_HIG Over high radio transmit signal Critical ODU

H level
RADIO_TSL_LO Over low radio transmit signal Critical ODU

W level
RELAY_ALARM Relay alarm Critical EOW
RP_LOC Loss of the received phase- Major PO1, PH1, PD1

locked clock

OptiX RTN 620

Severit
y
RPS_INDI Indication of the radio protection Major SCC

switching
RS_CROSSTR Regenerator section performance Minor SD1, SL1, SDE,

threshold-crossing SLE, IF1A, IF1B,
IFX, SL4
RTC_FAIL The real time clock (RTC) of the Major SCC

equipment fails.
S1_SYN_CHANG Clock source switching in S1 Major SCC

E byte mode
SWDL_ACTIVAT The activation timeout of the Critical SCC

ED_TIMEOUT software package
SWDL_AUTOMA The automatic match function is Minor SCC

TCH_INH disabled
SWDL_CHGMNG The board software version and Critical SCC

_NOMATCH the running software version are
inconsistent
SWDL_COMMIT_ NE submission failure Minor SCC

FAIL
SWDL_INPROCE The NE is in the process of Minor SCC

SS package loading.
SWDL_NEPKGC Loss of files in a software Critical SCC

HECK package
SWDL_PKG_NOB Files are deleted when they are Minor SCC

DSOFT customized.
SWDL_PKGVER_ Software package version Critical SCC

MM consistency check fails.
SWDL_ROLLBAC The version rollback on an NE Minor SCC

K_FAIL fails.
SYN_BAD Synchronous source degradation Minor PXC
SYNC_C_LOS The priority of the synchronous Warning SCC

clock source is lost.
T_ALOS Loss of analog signals at 2 Mbit/ Major PO1, PH1, PD1

s interfaces
T_F_RST Reset of the transmit FIFO Minor PO1, PH1, PD1
T_LOC Loss of clock on the transmit line Major SD1, SL1, SDE,
side SLE, SL4

OptiX RTN 620

Severit
y
T_LOS Loss of signal on the transmit line Major SD1, SL1, SDE,
side SLE, SL4
TEMP_ALARM The ambient temperature of the Minor IF1A, IF1B, EFT4,

board crosses the threshold. PXC, SCC, EMS6,
IF0A, IF0B, IFX,
IFH2, EFP6, ODU
TU_AIS TU alarm indication Major PO1, PH1, IF0A,

IF0B, PD1, PL3,
IFH2
TU_AIS_VC12 TU alarm indication at VC-12 Major EFT4, EMS6, EFP6

level
TU_AIS_VC3 TU alarm indication at VC-3 Major EFT4, EMS6

level
TU_LOP Loss of TU pointers Major PO1, PH1, IF0A,

IF0B, PD1, PL3,
IFH2
TU_LOP_VC12 Loss of TU pointers at VC-12 Major EFT4, EMS6, EFP6

level
TU_LOP_VC3 Loss of TU pointers at VC-3 level Major EFT4, EMS6
UP_E1_AIS Alarm indication of 2 Mbit/s Minor PO1, PH1, PD1

upstream signals
VCAT_LOA Loss of virtual concatenation Critical EFT4, EMS6, EFP6

alignment
VCAT_LOM_VC1 Loss of multiframe of VC-12 Major EFT4, EMS6, EFP6

2 path virtual concatenation
VCAT_LOM_VC3 Loss of multiframe of VC-3 path Major EFT4, EMS6

virtual concatenation
VCAT_SQM_VC1 SQ mismatch of VC-12 path Major EFT4, EMS6, EFP6

2 virtual concatenation
VCAT_SQM_VC3 SQ mismatch of VC-3 path Major EFT4, EMS6

virtual concatenation
VOLT_LOS Loss of voltage Major PXC, IF1A, IF1B,

IF0A, IF0B, IFX,
IFH2
WRG_BD_TYPE Errors of board types Major SCC
WRG_DEV_TYPE Errors of equipment types Critical SCC

OptiX RTN 620

Severit
y
WS_LOS Loss of wayside signals at 2 Mbit/ Major PXC

s electrical interfaces
W_R_FAILURE Read and write registers of the Major EMS6, EFP6

board chip fail.
XCP_INDI The active/standby switching of Major SCC

cross-connect and timing boards
occurs.
XPIC_LOS Loss of XPIC compensation Critical IFX

signals
NOTE
All alarmed boards refer to the logical boards displayed on the NMS.
A.2 Alarms and Handling Procedures

This topic describes all the alarms on the OptiX RTN 620 in an alphabet order 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.
Name Meaning
Parameter 1 The value is always 0x01.

OptiX RTN 620
Name Meaning
Parameter 2, Parameter 3 Indicate the ID of the path that reports the alarm. For example, 0x00
0x01 indicates that the alarm is reported in path 1.
Impact on the System

When the A_LOC alarm occurs, the services carried by the alarmed board are interrupted.
Possible Causes
The board is faulty.
Procedure
Step 1 Replace the board that reports the alarm.
----End
Related Information
None.
A.2.2 ALM_GFP_dCSF
Description
The ALM_GFP_dCSF is an alarm indicating that the generic framing procedure (GFP) customer
signal is lost. This alarm occurs when a board detects that a GFP customer signal management
frame, which indicates the loss of customer signals, is received from the remote station.
Attribute
Critical Communication alarm
Parameters
table.
Name Meaning
Parameter 2, Parameter 3 Indicate the ID of the VCTRUNK that reports the alarm. For
example, 0x00 0x01 indicate that the alarm is reported by
VCTRUNK 1.

OptiX RTN 620

When the ALM_GFP_dCSF alarm occurs, the services are interrupted.
Possible Causes
The associated Ethernet port on the remote board is not well connected.
Procedure
Step 1 Handle the alarm reported by the remote board.
----End
Related Information
None.
A.2.3 ALM_GFP_dLFD
Description
The ALM_GFP_dLFD is an alarm indicating that the GFP frame is out of frame. This alarm
occurs when a board detects that the GFP frame is out of frame.
Attribute
Major Communication alarm
Parameters
table.
Name Meaning
example, 0x00 0x01 indicate that the alarm is reported by
VCTRUNK 1.

The services are interrupted.

OptiX RTN 620
Possible Causes
l Cause 1: The source and the sink VCTRUNKs are configured with different timeslots or
different numbers of paths.
l Cause 2: Errors occur on certain links or certain links are faulty.
Procedure
Step 1 Cause 1: The source and the sink VCTRUNKs are configured with different timeslots or different
numbers of paths.
(1) Check whether the sink and source VCTRUNKs are bound with the same number of
physical paths or bound with the same timeslots.
If... Then...
The sink and source VCTRUNKs are not Correct the configuration data. For details,
bound with the same number of physical see Configuring the Internal Port of the
paths or bound with the same timeslots Ethernet Board.
The sink and source VCTRUNKs are Go to Cause 2.
bound with the same number of physical
paths and bound with the same timeslots
Step 2 Cause 2: Errors occur on certain links or certain links are faulty.
(1) Check whether the links that the service travels by have errors or become faulty.
If... Then...
The links are faulty Rectify the fault.
The links are normal Replace the alarmed board. .
----End
Related Information
None.
A.2.4 AM_DOWNSHIFT
Description
The AM_DOWNSHIFT is an alarm indicating the downshift of AM modes. This alarm occurs
when the AM mode is downshifted from the highest-efficiency mode to the lower-efficiency
mode. When the AM mode is upshifted from the lower-efficiency mode to the highest-efficiency
mode, this alarm clears.
Attribute

OptiX RTN 620
Parameters
None.

When the AM_DOWNSHIFT alarm occurs, the transmission capacity is reduced.
Possible Causes
The possible cause of the AM_DOWNSHIFT alarm is the degradation of the working channels.
l Cause 1: The external factors (for example, the climate) cause the degradation of the
working channels.
l Cause 2: There are interferences around the working channels.
l Cause 3: The ODU at the transmit end has abnormal transmit power.
l Cause 4: The ODU at the receive end has abnormal receive power.
Procedure
Step 1 Cause 1: The external factors (for example, the climate) cause the degradation of the working
channels.
(1) When the external factors (for example, the climate) cause the degradation of the working
channels, the downshift of the AM mode is normal. Therefore, no measures should be taken
to handle the alarm.
Step 2 Cause 2: There are interferences around the working channels.

(1) Eliminate the interferences around the working channels.
Step 3 Cause 3: The ODU at the transmit end has abnormal transmit power.
(1) Use the NMS to check whether the transmit power of the ODU at the transmit end is normal.
For details on troubleshooting the fault at the transmit end, see Troubleshooting
Microwave Links.
Step 4 Cause 4: The ODU at the receive end has abnormal receive power.
(1) Use the NMS to check whether the transmit power of the ODU at the transmit end is normal.
For details on troubleshooting the fault at the receive end, see Troubleshooting Microwave
Links.
----End
Related Information
None.
A.2.5 APS_FAIL
Description
The APS_FAIL is an alarm indicating that the MS protection switching fails.

OptiX RTN 620
Attribute

Parameters
table.
Name Meaning
Parameter 1 Indicates the type of the protection group.
l 0x01: linear MS protection.

l 0x02: ring MS protection.
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.

The services cannot be switched. If the current paths are unavailable, the services are interrupted.
Possible Causes
l Cause 1: The parameters of the MS protection are set incorrectly.
l Cause 2: The parameter settings of the MS protection are lost.
Procedure
Step 1 Cause 1: The parameters of the MS protection are set incorrectly.
(1) Check whether the parameters of the MS protection are set correctly.
If... Then...
The connection is not correct Set the parameters correctly. For details, see
Configuring Ring MSP or Configuring Linear MSP.
The connection is correct Go to Cause 2.
Step 2 Cause 2: The parameter settings of the MS protection are lost.

(1) Check whether the network-wide MSP protocol is normal.
(2) Restart the protocol. For details, see Starting/Stopping the Ring MSP Protocol or Starting/
Stopping the Linear MSP Protocol.

OptiX RTN 620
If... Then...
The alarm clears after the protocol is End the alarm handling.
restarted
The alarm persists after the protocol is Contact Huawei technical support
restarted engineers to handle the alarm.
----End
Related Information
None.
A.2.6 APS_INDI
Description
The APS_INDI is an alarm indicating that the MS protection switching occurs.
Attribute

Parameters
table.
Name Meaning


During the switching (≤ 50 ms), the services are interrupted. After the switching is complete,
the services are restored to normal. After the switching starts and before the switching is
complete, the extra services are interrupted.

OptiX RTN 620
Possible Causes
When the APS_INDI alarm occurs, the MS protection switching occurs.
Procedure
Step 1 Query the switching status of MS protection groups according to Parameter 1 and Parameter 2.
If... Then...
Parameter 1 = 0x01 Query linear MSP groups.
Parameter 1 = 0x02 Query ring MSP groups.
Step 2 Check whether the MSP protocol is in the manual switching state, forced switching state, or
locked switching state. If yes, release the switching and check whether the alarm clears.
Step 3 Check whether the MSP protocol is in the automatic switching state. Do as follows:
(1) Handle the R_LOS, R_LOF, MS_AIS, B2_EXC, or B2_SD alarm that the equipment
reports. After the alarm clears, wait until the MSP protocol is changed from the automatic
switching state to the normal state. Then, check whether the APS_INDI alarm clears.
(2) Check whether the service board configured with the MSP protocol is faulty. If yes, replace
the faulty board and then check whether the APS_INDI alarm clears.
(3) Check whether the cross-connect board is faulty. If yes, replace the PXC board, and then
check whether the APS_INDI alarm clears.
----End
Related Information
None.
A.2.7 APS_MANUAL_STOP
Description
The APS_MANUAL_STOP is an alarm indicating that the MSP protocol is stopped manually.
Attribute
Minor Processing alarm
Parameters
table.

OptiX RTN 620
Name Meaning


When the APS_MANUAL_STOP alarm occurs, the MSP protocol may fail and the protection
switching may fail.
Possible Causes
The MSP protocol is stopped manually.
Procedure
Step 1 Determine the MSP protocol that needs to be enabled according to Parameter 1.
If... Then...
Parameter 1 = 0x01 Enable the linear MSP protocol.
Parameter 1 = 0x02 Enable the ring MSP protocol.
----End
Related Information
None.
A.2.8 AU_AIS
Description
The AU_AIS is an alarm indication of the administrative unit (AU). This alarm occurs when the
board detects the AU pointer of all 1s for three consecutive frames.
Attribute
Parameters

OptiX RTN 620

table.
Name Meaning
Parameter 1 Indicates the ID of the line port that reports the alarm. For example,
0x01 indicates that the alarm is reported by port 1 of the related
board.
Parameter 2, Parameter 3 Indicate the ID of the AU-4 path that reports the alarm. For example,
0x00 0x01 indicate that the alarm is reported by AU-4 path 1 of the
SDH signal.

When the AU_AIS alarm occurs, the service in the alarmed AU-4 path is interrupted. If the
service is configured with protection, the protection switching is also triggered.
Possible Causes
l Cause 1: The opposite site inserts the AU_AIS alarm.
l Cause 2: The transmit unit at the opposite site is faulty.
l Cause 3: The receive unit at the local site is faulty.
Procedure
Step 1 Determine the AU-4 path that reports the alarm according to the alarm parameters.
Step 2 Cause 1: The opposite NE inserts the AU_AIS alarm.
If... Then...
The alarm that triggers the AU_AIS insertion occurs Clear the alarm immediately.
No such alarms that trigger the AU_AIS insertion occur Go to Cause 2.
Step 3 Cause 2: The transmit unit at the opposite site is faulty.

(1) Replace the line board or IF board of the opposite site.
If... Then...
The alarm clears after the board is The fault is rectified. End the alarm
replaced handling.
The alarm persists after the board is Go to the next step.
replaced
(2) Replace the PXC board of the opposite site.
Step 4 Cause 3: The receive unit at the local site is faulty.

(1) Replace the alarmed board.
----End

OptiX RTN 620
Related Information
None.
A.2.9 AU_LOP
Description
The AU_LOP is an alarm indicating the loss of AU pointers. This alarm occurs when a board
detects the AU pointers of invalid values or with NDFs for eight consecutive frames.
Attribute
Parameters
table.
Name Meaning
board.
SDH signal.

When the AU_LOP alarm occurs, the service in the alarmed AU-4 path is interrupted. If the
service is configured with protection, the protection switching is also triggered.
Possible Causes
Procedure
Step 1 Determine the AU-4 path that reports the alarm according to the alarm parameters.

(1) Replace the line board or IF board of the opposite site.

OptiX RTN 620
If... Then...
replaced handling.
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 occurs when the board detects that the B1 errors exceed the preset B1_EXC alarm
threshold (10-3 by default).
An IF boards that works in the PDH mode may also report this alarm. This alarm is detected by
the self-defined overhead byte B1 in PDH microwave frames.
Attribute

Minor Service alarm
Parameters
table.
Name Meaning
board.
Parameter 2, Parameter 3 Indicate the path ID. For example, 0x00 0x01 indicate that the alarm
is reported in path 1.

OptiX RTN 620

The services on the port are interrupted.
Possible Causes
l Cause 1: The line performance degrades (if the alarm is reported by an SDH optical interface
board).
l Cause 2: The line performance degrades (if the alarm is reported by an SDH electrical
interface board).
l Cause 3: The line performance degrades (if the alarm is reported by an IF board).
l Cause 4: The network clock quality degrades.
l Cause 5: The board is faulty (if the alarm is reported by an SDH optical interface board or
SDH electrical interface board).
l Cause 6: The board is faulty (if the alarm is reported by an IF board).
Procedure
Step 1 Cause 1: The line performance degrades (if the alarm is reported by an SDH optical interface
board).
(1) Check whether the transmit power at the opposite end and the receive power at the local
end meet the specifications of the optical interfaces. For details, see Browsing Current
Performance Events.
If... Then...
The transmit power of the opposite site is Replace the SDH optical interface board
extremely low of the opposite site.
The transmit power of the opposite site is The fiber is faulty. Proceed to the next step.
normal, but the receive power of the local
site is close to the value (for example,
within ±3 dB) of receiver sensitivity
(2) Exchange the core fibers of the optical cables in the receive and transmit directions of a
channel.
If... Then...
The errors vary with the change of the The fiber is faulty. Proceed to the next step.
fibers
The errors do not vary with the change Solve the problem according to the solution
of the fibers for the problem that occurs when a board is
faulty.
(3) If the fibers are faulty, check whether the fiber jumper from the equipment to the optical
distribution frame (ODF) and the fiber that is led out from the equipment room are pressed,
and whether any fiber connector is dirty or damaged. If yes, replace the fiber jumper or
clean the fiber connector.
Step 2 Cause 2: The line performance degrades (if the alarm is reported by an SDH electrical interface
board).
(1) Exchange the electrical cables that are possibly faulty in the receive and transmit directions

OptiX RTN 620
If... Then...
The bit errors vary with the change of Go to the next step.
the cables
The bit errors do not vary with the The boards of the stations at the two ends are
change of the cables faulty. Solve the problem according to the
solution for the problem that occurs when a
board is faulty.
(2) Check whether the cable grounding, cable connectors, and cables are damaged or deformed.
If yes, replace the faulty cables.
Step 3 Cause 3: The line performance degrades (if the alarm is reported by an IF board).
(1) Check whether the MW_FEC_UNCOR alarm is generated. If yes, clear the alarm.
Step 4 Cause 4: The network clock quality degrades.

(1) Check the clock status of the alarmed NE. For details, see Querying the Clock
Synchronization Status.
If... Then...
The clock source of the local NE is In this case, the clock may become
different from the clock source of the asynchronous and B1 errors may occur.
opposite NE Reconfigure the clock source, and ensure that
the clock is synchronized on the local NE and
opposite NE.
The clock of the local NE and the clock This may cause errors and even service
of the opposite NE form a timing loop interruptions. In this case, reconfigure the
clock source and release the timing loop.
Step 5 Cause 5: The board is faulty (if the alarm is reported by an SDH optical interface board or SDH
electrical interface board).
(1) The SDH optical/electrical line board of the local NE is faulty. Loop back the optical
interfaces or electrical interfaces of the NE by using a fiber jumper or an electrical cable
If... Then...
The fault is not rectified after the optical Replace the SDH line board of the local
interfaces or electrical interfaces are site.
looped back
The fault is rectified after the optical Replace the SDH line board of the
interfaces or electrical interfaces are opposite site.
looped back
Step 6 Cause 6: The board is faulty (if the alarm is reported by an IF board).
(1) Perform an inloop for the multiplexing interface of the IF board on the local site.
If... Then...
The fault is not rectified after the optical Replace the alarmed IF board of the
interfaces are looped back local site.

OptiX RTN 620
If... Then...
The fault is rectified after the multiplexing Replace the IF board of the opposite
interface is looped back site.
----End
Related Information
Handle the errors of TDM services.
A.2.11 B1_SD
Description
The B1_SD is an alarm indicating that the regenerator section (B1) signal degrades. This alarm
occurs when the board detects that the B1 errors exceed the preset B1_SD alarm threshold
(10-6 by default) but do not reach the preset B1_EXC alarm threshold (10-3 by default).
An IF board that works in PDH mode may also report this alarm. This alarm is detected by the
self-defined overhead byte B1 in PDH microwave frames.
Attribute
Minor Service alarm
Parameters
table.
Name Meaning
Parameter 1 Indicates the ID of the port that reports the alarm. For example,
board.
Parameter 2, Parameter 3 Indicate the path ID. For example, 0x00 0x01 indicate that the alarm
is reported in path 1.

The service performance on the port degrades.
If the alarm is reported by an IF board and the equipment is configured with 1+1 FD/SD
protection, the HSM switching is triggered.

OptiX RTN 620
Possible Causes
board).
interface board).
Procedure
board).
Performance Events.
If... Then...
The transmit power of the opposite site is Go to the next step.
channel.
If... Then...
The errors vary with the change of the The fibers are faulty. Proceed to the next step.
fibers
faulty.
board).
(1) Exchange the cables that are possibly faulty in the receive and transmit directions to locate
the fault.
If... Then...

OptiX RTN 620
The bit errors vary with the change of the Go to the next step.
cables
The bit errors do not vary with the change The boards of the stations at the two ends
of the cables are faulty. Solve the problem according to
the solution for the problem that occurs
when a board is faulty.
If yes, replace the cables that are faulty.

If... Then...
opposite NE.
If... Then...
looped back
looped back
If... Then...
The fault is not rectified after the Replace the alarmed IF board of the
multiplexing interface is looped back local site.

OptiX RTN 620
If... Then...
----End
Related Information
A.2.12 B2_EXC
Description
The B2_EXC is an alarm indicating that B2 errors (in multiplex section) exceed the threshold.
This alarm occurs when the board detects that the number of B2 errors exceeds the preset
B2_EXC alarm threshold (10-3 by default).
Attribute
Major Service alarm
Parameters
table.
Name Meaning
board.
Parameter 2, Parameter 3 Indicate the path ID.

Possible Causes
board).
interface board).

OptiX RTN 620
Procedure
board).
Performance Events.
If... Then...
channel.
If... Then...
fibers
faulty.
board).
the fault.
If... Then...
cables

OptiX RTN 620

If... Then...
opposite NE.
If... Then...
interfaces or electrical interface are site.
looped back
looped back
(1) Perform an inloop for the multiplexing interface of the IF board on the local NE.
If... Then...
----End
Related Information

OptiX RTN 620
A.2.13 B2_SD
Description
The B2_SD is an alarm indicating that the signal degrades due to excessive B2 errors (in the
multiplex section). This alarm occurs when the board detects that the number of B2 errors
exceeds the preset B2_EXC alarm threshold (10-6 by default).
Attribute

Minor Service alarm
Parameters
table.
Name Meaning
board.

The service performance on the port degrades.
Possible Causes
board).
interface board).

OptiX RTN 620
Procedure
board).
Performance Events.
If... Then...
channel.
If... Then...
fibers
faulty.
board).
the fault.
If... Then...
cables

OptiX RTN 620

If... Then...
opposite NE.
If... Then...
looped back
looped back
If... Then...
----End
Related Information
A.2.14 B3_EXC

OptiX RTN 620
Description
The B3_EXC is an alarm indicating that B3 errors (in the higher order path) exceed the threshold.
This alarm occurs when the board detects that the number of B3 errors exceeds the preset
B3_EXC alarm threshold (10-3 by default).
Attribute
Major Service alarm
Parameters
table.
Name Meaning
board.
0x00 0x01 indicates that the alarm is reported by AU-4 path 1 of
the related board.

When the B3_EXC alarm occurs, the service on the path that reports the alarm is interrupted.
Possible Causes
board).
interface board).
Procedure
board).

OptiX RTN 620
Performance Events.
If... Then...
The transmit power of the opposite site is Replace the board that contains the SDH
extremely low optical interface unit on the opposite
site.
channel.
If... Then...
fibers
faulty.
board).
the fault.
If... Then...
cables
(1) Check whether the MW_FEC_UNCOR or RPS_INDI alarm is reported. If yes, clear the
alarm.

OptiX RTN 620
If... Then...
opposite NE.
If... Then...
looped back
looped back
If... Then...
----End
Related Information
A.2.15 B3_EXC_VC3
Description
The B3_EXC_VC3 is an alarm indicating that the B3 errors (in VC-3 paths) exceed the threshold.
This alarm occurs when a board detects that the number of B3 errors exceeds the preset
B3_EXC_VC3 alarm threshold (10-3 by default).

OptiX RTN 620
Attribute
Major Service alarm
Parameters
table.
Name Meaning
Parameter 2, Parameter 3 Indicate the ID of the VC-3 path that reports the alarm. For example,
0x00 0x01 indicate that the alarm is reported by VC-3 path 1.

The services carried by the alarmed path have a large number of errors.
Possible Causes
l Cause 1: Higher-level bit error alarms occur in the system.
l Cause 2: The line performance degrades (if the alarm is reported by an Ethernet optical
interface).
l Cause 3: The line performance degrades (if the alarm is reported by an Ethernet electrical
interface).
l Cause 4: The board is faulty.
Procedure
Step 1 Cause 1: Higher-level bit error alarms occur in the system.
(1) Check whether the local site or the upstream station detects the B1_EXC, B1_SD,
B2_EXC, B2_SD, B3_EXC, or B3_SD alarm. If yes, clear the higher-level alarm.
(2) Then, check whether the B3_EXC_VC3 alarm clears.
If... Then...
Yes End the alarm handling.
No Go to Cause 2 or Cause 3.
Step 2 Cause 2: The line performance degrades (if the alarm is reported by an Ethernet optical interface).
Performance Events.

OptiX RTN 620
If... Then...
The transmit power of the opposite site is Replace the Ethernet board of the
extremely low opposite site.
The transmit power of the opposite site is The fibers are faulty. Proceed to the next
normal, but the receive power of the local step.
within ±3 dB) of receiver sensitivity.
channel.
If... Then...
The errors vary with the change of the fibers Go to the next step.
The errors do not vary with the change of the fibers Ensure that the board is normal.
fiber connector. Then, check whether the alarm clears.
If... Then...
No Ensure that the board is normal.
Step 3 Cause 3: The line performance degrades (if the alarm is reported by an Ethernet electrical
interface).
(2) Then, check whether the alarm clears.
If... Then...
Step 4 Cause 4: The board is faulty.

(1) Perform an inloop on the Ethernet port that is connected to the alarmed VC-3 path.
If... Then...
The fault is not rectified after the Replace the alarmed Ethernet processing
Ethernet port is looped back board of the local site.
The fault is rectified after the Ethernet Replace the Ethernet processing board of
port is looped back the opposite site.
----End
Related Information
None.

OptiX RTN 620
A.2.16 B3_SD
Description
The B3_SD is an alarm indicating that the signal degrades due to excessive B3 errors (in the
higher order path). This alarm occurs when a board detects that the number of B3 errors exceeds
the preset B3_SD alarm threshold (10-6 by default).
Attribute
Minor Service alarm
Parameters
table.
Name Meaning
board.
related board.

The service performance on the alarmed port degrades.
Possible Causes
board).
interface board).

OptiX RTN 620
Procedure
board).
Performance Events.
If... Then...
channel.
If... Then...
fibers
faulty.
board).
the fault.
If... Then...
cables

OptiX RTN 620

If... Then...
opposite NE.
If... Then...
looped back
looped back
If... Then...
----End
Related Information
None.
A.2.17 B3_SD_VC3

OptiX RTN 620
Description
The B3_SD_VC3 is an alarm indicating that the signal degrades due to excessive B3 errors (in
VC-3 paths). This alarm occurs when the board detects that the number of B3 errors exceeds the
preset B3_SD_VC3 alarm threshold (10-6 by default).
Attribute
Minor Service alarm
Parameters
table.
Name Meaning
0x01 indicate that the alarm is reported by VC-3 path 1.

When the B3_SD_VC3 alarm occurs, the service on the path that reports the alarm degrades.
Possible Causes
l Cause 1: Higher-level bit error alarms occur in the system.
l Cause 2: The line performance degrades (if the alarm is reported by an Ethernet optical
interface).
l Cause 3: The line performance degrades (if the alarm is reported by an Ethernet electrical
interface).
Procedure
Step 1 Cause 1: Higher-level bit error alarms occur in the system.
(1) Check whether the local site or the upstream station detects the B1_EXC, B1_SD,
B2_EXC, B2_SD, B3_EXC, or B3_SD alarm. If yes, clear the higher-level alarm.
If... Then...
No Go to Cause 2 or Cause 3.

OptiX RTN 620
Step 2 Cause 2: The line performance degrades (if the alarm is reported by an Ethernet optical interface).
Performance Events.
If... Then...
The transmit power of the opposite site is Replace the Ethernet board of the
extremely low opposite site.
channel.
If... Then...
The errors vary with the change of the fibers Go to the next step.
The errors do not vary with the change of the fibers Ensure that the board is normal.
clean the fiber connector. Then, check whether the alarm clears.
If... Then...
Step 3 Cause 3: The line performance degrades (if the alarm is reported by an Ethernet electrical
interface).
If... Then...

(1) Perform an inloop on the Ethernet port that is connected to the alarmed VC-3 path.
If... Then...
The fault is not rectified after the Replace the alarmed Ethernet processing
Ethernet port is looped back board of the local site.
The fault is rectified after the Ethernet Replace the Ethernet processing board of
port is looped back the opposite site.
----End

OptiX RTN 620
Related Information
None.
A.2.18 BD_NOT_INSTALLED
Description
The BD_NOT_INSTALLED is an alarm indicating that a physical board is installed in a certain
slot, but the logical board is not added.
Attribute
Minor Equipment alarm
Parameters
table.
Name Meaning
Parameter 0, Parameter 1 Indicate the ID of the slot.

When the BD_NOT_INSTALLED alarm occurs, the physical board in this slot cannot work.
Possible Causes
l Cause 1: The logical board is not added in the corresponding logical slot.
l Cause 2: The physical board is installed incorrectly during the replacement of boards.
Procedure
Step 1 Cause 1: The logical board is not added in the corresponding logical slot.
(1) Configure the logical board.
Step 2 Cause 2: The physical board is installed incorrectly during the replacement of boards.
(1) Check whether the physical board is installed in the correct slot. If not, reinstall the physical
board in the correct slot.
----End
Related Information
None.

OptiX RTN 620
A.2.19 BD_STATUS
Description
The BD_STATUS is an alarm indicating that the board is not in position.
Attribute
Parameters
None.

The board that reports the alarm fails to work.
Possible Causes
If the alarm is reported by a board of the IDU, the possible causes are as follows:
l Cause 1 of the alarm reported by a board of the IDU: The board is installed in an incorrect
slot.
l Cause 2 of the alarm reported by a board of the IDU: The board and the backplane are not
connected properly.
l Cause 3 of the alarm reported by a board of the IDU: The slot is faulty.
l Cause 4 of the alarm reported by a board of the IDU: The board is faulty.
If the alarm is reported by the ODU, the possible causes are as follows:
l Cause 1 of the alarm reported by the ODU: Other alarms are generated.
l Cause 2 of the alarm reported by the ODU: The ODU is faulty.
Procedure
Step 1 Cause 1 of the alarm reported by a board of the IDU: The board is installed in an incorrect slot.
(1) Check whether the logical slot and the physical slot of the alarmed board are consistent.
For details, see Checking Board Status.
If... Then...
The board that reports the alarm is installed Install the board in a correct slot.
in an incorrect slot
The board that reports the alarm is installed Clear the alarm according to the solution
in a correct slot for the alarm that is generated when the
board and the backplane are not connected
properly.

OptiX RTN 620
Step 2 Cause 2 of the alarm reported by a board of the IDU: The board and the backplane are not
connected properly.
(1) Remove and insert the alarmed board. For details, see 6.1 Removing a Board and 6.2
Inserting a Board.
If... Then...
The alarm disappears after the board is The fault is rectified. End the alarm
removed and inserted handling.
The alarm persists after the board is Clear the alarm according to the solution
replaced for the alarm that is generated when the
board or the slot is faulty.
Step 3 Cause 3 of the alarm reported by a board of the IDU: The slot is faulty.
(1) Contact Huawei engineers to handle the faulty slot.
TIP
Generally, the slot becomes faulty due to broken pins or bent pins. Remove the board, and use a torch
to check whether there is any broken pin or bent pin.
(2) If an idle slot is available, insert the board in the idle slot and add the board again. Then,
the board can work normally.
Step 4 Cause 4 of the alarm reported by a board of the IDU: The board is faulty.
(1) Replace the alarmed board. For details, see 6 Part Replacement.
If... Then...
The alarm clears after the board is replaced The fault is rectified. End the alarm
handling.
The alarm persists after the board is Clear the alarm according to the solution
replaced for the alarm that is generated when the slot
is faulty.
Step 5 Cause 1 of the alarm reported by the ODU: Other alarms are generated.
(1) Query the IF board to see whether the HARD_BAD, BD_STATUS,
IF_CABLE_OPEN or VOLT_LOS alarm is generated.
If... Then...
Yes Clear these alarms first.
No Clear the alarm according to the solution

for the alarm that is generated when the
ODU is faulty.
Step 6 Cause 2 of the alarm reported by the ODU: The ODU is faulty.
(1) Replace the ODU that reports the alarm. For details, see 6.12 Replacing an ODU.
----End

OptiX RTN 620
Related Information
None.
A.2.20 BIP_EXC
Description
The BIP_EXC is an alarm indicating that BIP errors exceed the preset threshold. This alarm
occurs when a board detects that the number of BIP-2 errors (in byte V5) exceeds the preset
BIP_EXC alarm threshold (10-3 by default).
Attribute
Minor Service alarm
Parameters
table.
Name Meaning
0x01 indicate that the alarm is reported in path 1.

When the BIP_EXC alarm occurs, the service on the path that reports the alarm is interrupted.
Possible Causes
l Cause 1: The line performance degrades (if the alarm is reported by an E1 service board
or Ethernet processing board).
l Cause 3: The board is faulty (if the alarm is reported by an E1 service board or Ethernet
processing board).
Procedure
Step 1 Cause 1: The line performance degrades (if the alarm is reported by an E1 service board or
Ethernet service processing board).

OptiX RTN 620
(1) Check whether any performance degradation alarm occurs on the STM-1 path or radio link
along which the E1 service or Ethernet service travels. If yes, clear the alarm immediately.
The following are the performance degradation alarms that commonly occur on an optical
line or radio link:
B1_EXC, B1_SD, B2_EXC, B2_SD, B3_EXC, B3_SD, MW_FEC_UNCOR,

RPS_INDI, MW_BER_EXC, and MW_BER_SD.
If... Then...
Yes Handle the relevant alarms first.
(1) Check whether any performance degradation alarm occurs on the tributary board or IF
board that transmits service signals. If yes, clear the alarm immediately.
The following are the performance degradation alarms that commonly occur on the
tributary board or IF board:
BIP_EXC, BIP_SD, MW_FEC_UNCOR, RPS_INDI, MW_BER_EXC, and

MW_BER_SD.
Step 3 Cause 3: The board is faulty (if the alarm is reported by an E1 service board or Ethernet service
processing board).
(1) Replace the E1 service board or replace the Ethernet service processing board. Then,
check whether the alarm clears.
If... Then...
No Replace the PXC board.
(1) Replace the IF board. Then, check whether the alarm clears.
If... Then...
----End
Related Information
5.4 Troubleshooting Bit Errors in TDM Services.
A.2.21 BIP_SD

OptiX RTN 620
Description
The BIP_SD is an alarm indicating that the signal degrades due to excessive BIP errors. This
alarm occurs when the board detects that the number of BIP-2 errors (in byte V5) exceeds the
preset BIP_SD alarm threshold (10-6 by default).
Attribute
Minor Service alarm
Parameters
table.
Name Meaning

When the BIP_SD alarm occurs, the service on the alarmed path degrades.
Possible Causes
l Cause 1: The line performance degrades (if the alarm is reported by an E1 service board
or Ethernet service processing board).
l Cause 3: The board is faulty (if the alarm is reported by an E1 service board or Ethernet
service processing board).
Procedure
Step 1 Cause 1: The line performance degrades (if the alarm is reported by an E1 service board or
Ethernet processing board).
(1) Check whether any performance degradation alarm occurs on the STM-1 path or radio link
along which the E1 service or Ethernet service travels. If yes, clear the alarm immediately.
The following are the performance degradation alarms that commonly occur on an optical
line or radio link:
B1_EXC, B1_SD, B2_EXC, B2_SD, B3_EXC, B3_SD, MW_FEC_UNCOR,
RPS_INDI, MW_BER_EXC, and MW_BER_SD.

OptiX RTN 620
If... Then...
Yes Handle the relevant alarms first.
(1) Check whether any performance degradation alarm occurs on the tributary board or IF
board that transmits service signals. If yes, clear the alarm immediately.
The following are the performance degradation alarms that commonly occur on the
tributary board or IF board:
BIP_EXC, BIP_SD, MW_FEC_UNCOR, RPS_INDI, MW_BER_EXC, and
MW_BER_SD.
Step 3 Cause 3: The board is faulty (if the alarm is reported by an E1 service board or Ethernet service
processing board).
(1) Replace the E1 service board or replace the Ethernet service processing board. Then,
If... Then...
(1) Replace the IF board. Then, check whether the alarm clears.
If... Then...
----End
Related Information
A.2.22 BOOTROM_BAD
Description
The BOOTROM_BAD is an alarm indicating that the BOOTROM data consistency check fails.
This alarm occurs when the BOOTROM data is damaged during a periodical check by the
system.
Attribute

OptiX RTN 620
Parameters
table.
Name Meaning
Parameter 1 Indicates the type of the BOOTROM damage.
l 0x01: damage of basic BIOS
l 0x02: damage of extended BIOS
Parameter 2, Parameter 3 The values are always 0xff 0xff.

When the BOOTROM_BAD 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 certain query and setting commands, and certain system functions cannot work.
l When the NE is already started ,the BOOTROM_BAD alarm has no impacts on the system
and services.
l If the BOOTROM_BAD alarm occurs and a hard reset is performed on a board, the board
fails to load the BIOS and cannot be started.
Possible Causes
l Cause 1: The basic BIOS is damaged.
l Cause 2: The extended BIOS is damaged.
l Cause 3: The BOOTROM database is damaged.
Procedure
Step 1 Replace the SCC board.
----End
Related Information
None.
A.2.23 C2_VCAIS
Description
The C2_VCAIS is an indication of the path signal label byte (C2) alarm. This alarm occurs when
a board detects that the C2 byte is 0xff.

OptiX RTN 620
Attribute

Minor Communication alarm
Parameters
table.
Name Meaning

None.
Possible Causes
Cause 1: The transmitted C2 byte at the remote end is incorrectly set.
Procedure
Step 1 Cause 1: The transmitted C2 byte at the remote end is incorrectly set.
(1) Determine the ID of the VC path that reports the alarm according to the alarm parameter.
(2) Rectify the setting of C2 to be Sent on the remote station.
----End
Related Information
None.
A.2.24 CONFIG_NOSUPPORT
Description
The CONFIG_NOSUPPORT is an alarm indicating that the configuration is not supported. This
alarm is reported if an ODU detects that the specified parameters do not meet the requirements
of the ODU.

OptiX RTN 620
Attribute

Major Processing alarm
Parameters
table.
Name Meaning
Parameter 1 Indicates that the configuration data does not meet the specified requirement.
l 0x01: The frequency is set incorrectly.
l 0x02: The T/R spacing is set incorrectly.
l 0x03: The transmit power is set incorrectly.
l 0x04: The ATPC threshold is set incorrectly.
l 0x05: The bandwidth is set incorrectly.
l 0x06: The modulation mode is set incorrectly.

The ODU fails to work normally. If the equipment is configured with 1+1 FD protection, the
active ODU generates the CONFIG_NOSUPPORT alarm. In this case, IF 1+1 protection
switching may be triggered.
Possible Causes
Cause 1: The type and configuration parameters of the ODU do not match the requirements.
Procedure
Step 1 Cause 1: The type and configuration parameters of the ODU do not match the requirements.
(1) Determine the parameter that does not meet the requirement according to the alarm
parameter. Then, handle the fault accordingly.
If... Then...
The alarm parameter takes a value from 0x01 to 0x03 Run Step 1.2.
The alarm parameter takes a value from 0x04 to 0x06 Run Step 1.3.
(2) Check whether the parameters of the ODU interface meet the requirements of network
planning. For details, see Setting Parameters of ODU Interfaces.

OptiX RTN 620
If... Then...
Yes Replace the ODU with a correct one.
No Modify the parameters of the ODU interface.
(3) Check whether the parameters of the IF interface meet the requirements of network
planning. For details, see Configuring the IF/ODU Information of a Radio Link.
If... Then...
Yes Replace the IF board.
No Configure the IF/ODU information of radio links.
----End
Related Information
None.
A.2.25 DBMS_ERROR
Description
The DBMS_ERROR is an alarm indicating that errors occur in the processing of the system
database.
Attribute
Parameters
table.

OptiX RTN 620
Name Meaning
Parameter 1 Indicates the types of the database errors.
l 0x01: The input parameters are invalid.
l 0x02: The database files do not exist.
l 0x03: The database memory area numbers are incorrect.
l 0x04: The database overwriting occurs.
l 0x05: Errors occur in the header information check in the database backup
area.
l 0x06: Errors occur in the FAT table structure check in the database storage
area.
l 0x07: Errors occur in the database check in the database backup area.
l 0x08: Restoring the database fails.
l 0x09: The database ID is invalid.
l 0x0A: The databases are different.
l 0x0B: The data is unchecked.
l 0x0E: The semaphore handle is invalid.
l 0x0F: Errors occur in applying for memory.
l 0x10: Errors occur in releasing memory.
l 0x12: Transmitting the message capsule fails.
l 0x13: The starting and ending records of the database are incorrect.
l 0x14: The database is null.
l 0x15: The flag is incorrectly set.
l 0x16: The input command parameters are incorrect.
l 0x17: Non-backup database.
l 0x18: The database is in protection mode.
l 0x19: The configuration is not verified.
Parameter 2 Indicates the errored data storage area.

l 0x00: database in fdb0
l 0x01: database in fdb1
l 0x02: database in drdb
Parameter 3 Indicates the ID of the errored database.

l 0x00: all databases in the entire storage area.
l 0x01-0xff: ID of the errored database

When the DBMS_ERROR 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 certain query and setting commands, and certain system functions cannot work.

OptiX RTN 620
Possible Causes
l Cause 1: The database processing fails or the database is damaged.
l Cause 2: The SCC board is faulty.
Procedure
Step 1 Cause 1: The database operation fails.
(1) Reset the SCC board. For details, see Resetting the SCC board.
If... Then...
The alarm clears after the board is reset End the fault handling.
The alarm persists after the board is reset Go to Cause 2.
Step 2 Cause 2: The SCC board is faulty.

(1) Replace the alarmed SCC board.
----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
Critical Processing alarm
Parameters
None.

When the DBMS_PROTECT_MODE 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 certain query and setting commands, and certain system functions cannot work.
Possible Causes
Cause 1: The data enters the protection mode due to frequent resets of the NE software.

OptiX RTN 620
Procedure
Step 1 Cause 1: The data enters the protection mode due to frequent resets of the NE software.
(1) Replace the SCC board.
----End
Related Information
None.
A.2.27 DOWN_E1_AIS
Description
The DOWN_E1_AIS is an alarm of the 2 Mbit/s downlink signal. This alarm occurs when the
tributary board detects the 2 Mbit/s downlink signal of all 1s.
Attribute
Parameters
table.
Name Meaning
0x01 indicates that the alarm is reported in path 1.

The E1 signal is unavailable.
Possible Causes
l Cause 1: The opposite site transmits the E1_AIS alarm.
l Cause 2: The board on the local site is faulty.
Procedure
Step 1 Cause 1: The opposite site transmits the E1_AIS alarm.

OptiX RTN 620
(1) Check whether the opposite site reports the UP_E1_AIS or T_ALOS alarm.
If... Then...
The opposite site reports the UP_E1_AIS Clear the alarm immediately.
or T_ALOS alarm
The opposite site does not report the Solve the problem according to the solution
UP_E1_AIS or T_ALOS alarm for the problem that occurs when a board is
faulty.
Step 2 Cause 2: The board on the local site is faulty.

If... Then...
replaced handling.
The alarm persists after the board is Replace the PXC board of the local site.
replaced
----End
Related Information
None.
A.2.28 E1_LOC
Description
The E1_LOC is an alarm indicating that the upstream 2M clock is lost. This alarm occurs when
a tributary board fails to extract the clock from E1 signals.
Attribute
Parameters
table.
Name Meaning
Parameter 1 Indicates the ID of the tributary port (path) that reports the alarm. For example,
0x01 indicates that the alarm is reported by port (path) 1 of the tributary board.

OptiX RTN 620

When E1_LOC occurs, the service is not affected.
Possible Causes
l Cause 1: The opposite NE is faulty.
l Cause 2: The line sequence of the cable is incorrect.
l Cause 3: The receive unit of the tributary board on the local NE is faulty.
l Cause 4: The input E1 signal has an abnormal waveform.
Procedure
Step 1 Cause 1: The opposite NE is faulty.
(1) Rectify the fault on the opposite NE.
Step 2 Cause 2: The line sequence of the cable is incorrect.

(1) Redo the cable.
Step 3 Cause 3: The receive unit of the tributary board on the local NE is faulty.
(1) Replace the tributary board of the local site.
Step 4 Cause 4: The input E1 signal has an abnormal waveform.

(1) Check whether any external interference causes the abnormal waveform of the E1 signal.
If... Then...
There is external interference The fault is rectified. End the alarm handling.
There is no external interference Contact Huawei engineers.
----End
Related Information
None.
A.2.29 E1_LOS
Description
The E1_LOS is an alarm indicating the loss of E1 signals. This alarm occurs when a tributary
board detects upstream E1 signals of all 0s.
Attribute


OptiX RTN 620
Parameters
table.
Name Meaning

When E1_LOS alarm occurs, E1 services are interrupted.
Possible Causes
l Cause 1: The cable is not connected or the cable is faulty.
l Cause 2: The opposite NE is faulty.
l Cause 3: The tributary board on the local site is faulty.
Procedure
Step 1 Cause 1: The cable is not connected or the cable is faulty.
(1) Check whether the cable is connected properly.
If... Then...
The cable is not connected properly Connect the cable properly.
The cable is prepared incorrectly Redo the cable.
Step 2 Cause 2: The opposite NE is faulty.

(1) Rectify the fault on the opposite NE.
Step 3 Cause 3: The tributary board on the local site is faulty.

(1) Replace the tributary board of the local site.
----End
Related Information
None.
A.2.30 ESN_INVALID

OptiX RTN 620
Description
The ESN_INVALID is an alarm indicating that the electronic serial number (ESN) of the
equipment is invalid.
Attribute
Parameters
table.
Name Meaning
Parameter 1 Indicates the slot number of the alarmed SCC board.

None.
Possible Causes
Cause 1: Verification of the ESN that is read from the SCC board is normal, but the ESN cannot
be identified.
Procedure
Step 1 Cause 1: Verification of the ESN that is read from the SCC board is normal, but the ESN cannot
be identified.
(1) Contact Huawei technical support engineers for upgrading the software.
----End
Related Information
None.
A.2.31 ETH_CFM_MISMERGE
Description
The ETH_CFM_MISMERGE is an alarm indicating an incorrect connection. This alarm occurs
when the system receives the CCM packet whose MA ID mismatches or whose priority is lower.

OptiX RTN 620
Attribute
Parameters
table.
Name Meaning
Parameter 1, Parameter 2, Parameter 3, Indicate the ID of the port that reports the alarm.
Parameter 4 (Port)
Parameter 5, Parameter 6 (VLAN ID) Indicate the VLAN ID of the MEP.
Parameter 7 (Direction) Indicates the direction of the local MEP.
l 0x00: The port is direction insensitive.
l 0x01: The port is in the ingress direction.
l 0x02: The port is in the egress direction.
Parameter 8 (Level) Indicates the MD level of the local MEP.

l 0x00: consumer MEP level (low).
l 0x01: consumer MEP level (medium).
l 0x02: consumer MEP level (high).
l 0x03: provider MEP level (low).
l 0x04: provider MEP level (high).
l 0x05: operator MEP level (low).
l 0x06: operator MEP level (medium).
l 0x07: operator MEP level (high).
NOTE
Consumer indicates the customer, provider indicates
the supplier, and operator indicates the carrier.

The services among relevant standard MEPs may be interrupted or the data flow may be
incorrectly routed.
Possible Causes
l Cause 1: The names of the MDs and the MAs that the standard MEPs correspond to are
inconsistent.
l Cause 2: The levels of the MDs that the standard MEPs correspond to are different.

OptiX RTN 620
l Cause 3: The physical connection is incorrect.
Procedure
Step 1 Cause 1: The names of the MDs and the MAs that the standard MEPs correspond to are
inconsistent.
(1) Check whether the names of the MDs and the MAs that the standard MEPs correspond to
are the same.
If... Then...
The MD names or MA names are Re-configure the MA names and MA names
different to ensure consistency at both ends.
The MD names or MA names are the Go to Cause 2.
same at both ends
Step 2 Cause 2: The levels of the MDs that the standard MEPs correspond to are different.
(1) Check whether the MD levels of the standard MEPs are the same.
If... Then...
The MD levels are different Re-configure the MD levels to ensure
consistency at both ends.
The MD levels are the same at both ends Go to Cause 3.
Step 3 Cause 3: The physical connection is incorrect.

(1) Check the physical connection of the Ethernet service route and rectify the fault on the
physical connection if any.
----End
Related Information
None.
A.2.32 ETH_CFM_UNEXPERI
Description
The ETH_CFM_UNEXPERI is an alarm indicating the errored frame. This alarm occurs when
the system receives invalid CCM packets.
Attribute
Parameters

OptiX RTN 620

table.
Name Meaning
Parameter 4 (Port)

NOTE

l The LB and LT detection functions of IEEE 802.1ag ETH-OAM are unavailable.
l The service may become abnormal due to the loop.
Possible Causes
l Cause 1: No remote MEP is configured.
l Cause 2: The configuration of the MEPs at both ends are inconsistent. For example, the
connectivity check (CC) periods are different, and the IDs of the MEPs are in conflict.
l Cause 3: The service is looped back and the looped packet is received.
l Cause 4: A software fault occurs at the MEP at the transmit end.
Procedure
Step 1 Cause 1: No remote MEP is configured.
(1) Check whether the remote MEP is configured. If not, configure the remote MEP first.
Step 2 Cause 2: The configuration of the MEPs at both ends are inconsistent. For example, the
connectivity check (CC) periods are different, and the IDs of the MEPs are in conflict.

OptiX RTN 620
(1) Check whether the CC periods set at the MEPs are the same.
If... Then...
The CC periods are different Change the CC periods to ensure consistency at both
ends.
The CC periods are the same Go to the next step.
(2) Check whether the IDs of the MEPs in the maintenance domain are in conflict.
If... Then...
The IDs are in conflict Change the conflicting IDs.
The IDs are not in conflict Go to Cause 2.
Step 3 Cause 3: The service is looped back and the looped packet is received.
(1) Enable the loop detection function of IEEE 802.3ah ETH-OAM. Check whether any loop
exists at each IP port of the service trail. If yes, release the loop and clear the alarm.
Step 4 Cause 4: A software fault occurs at the MEP at the transmit end.
(1) Perform a warm reset on the Ethernet board where the remote MEP is located. For details,
see 7.6.2 Warm Resetting.
----End
Related Information
None.
A.2.33 ETH_CFM_LOC
Description
The ETH_CFM_LOC is an alarm indicating the loss of connectivity. This alarm occurs when
the system fails to receive CCM packets from the remote MEP in 3.5 connectivity check (CC)
periods successively.
Attribute

Parameters
table.

OptiX RTN 620
Name Meaning
Parameter 1, Parameter 2, Parameter 3, Indicate the number of the port where the alarm
Parameter 4 (Port) is reported.

NOTE
Parameter 9, Parameter 10 (RMEPID) Indicate the ID of the remote MEP.

l The LB and LT detection functions of IEEE 802.1ag ETH-OAM are unavailable.
l The services among relevant standard MEPs may be interrupted.
Possible Causes
l Cause 1: The line between the local standard MEP and the remote standard MEP is
interrupted.
l Cause 2: The Ethernet service in the maintenance association (MA) to which the local MEP
belongs is faulty.
l Cause 3: Serious congestion occurs on the network.
Procedure
Step 1 Cause 1: The line between the local standard MEP and the remote standard MEP is interrupted.
(1) Check whether the physical links (such as cables or fibers) connecting the services at the
MEPs of the two ends are correct.

OptiX RTN 620
If... Then...
The connection is not correct Re-connect the cables to rectify the faults on physical
links.
Step 2 Cause 2: The Ethernet service in the maintenance association (MA) to which the local MEP
belongs is faulty.
(1) Check whether the Ethernet service in the maintenance association (MA) to which the local
MEP belongs is configured correctly.
If... Then...
The connection is not correct Modify the configuration of the Ethernet services to
ensure consistency at both ends.
Step 3 Cause 3: Serious congestion occurs on the network.

(1) Check the utilization of bandwidth. If the bandwidth is exhausted, increase the bandwidth
or eliminate the source that transmits a large amount of invalid data.
----End
Related Information
None.
A.2.34 ETH_CFM_RDI
Description
The ETH_CFM_RDI is an alarm indicating CCM packets with RDI received from the remote
MEP. This alarm occurs when the system receives CCM packets with RDI from the remote
MEP.
Attribute

Parameters
table.

OptiX RTN 620
Name Meaning
Parameter 4 (Port)
Parameter 7 (Direction) Indicate the direction of the local MEP.

l 0x00:0x00: consumer MEP level (low).
NOTE
Parameter 9, Parameter 10 (RMEPID) Indicate the ID of the remote MEP.

l The LoopBack (LB) and LinkTrace (LT) detection functions of IEEE 802.1ag ETH-OAM
are unavailable.
l The services among relevant standard MEPs may be interrupted.
Possible Causes
l Cause 1: The remote MEP fails to receive correct CCM packets.
l Cause 2: The software is reset or another software fault occurs at the remote MEP.
Procedure
Step 1 Cause 1: The remote MEP fails to receive correct CCM packets.
(1) Determine the port that reports the alarm according to the alarm parameters.
(2) Check whether the remote MEP that is connected to the port reports the
ETH_CFM_LOC, ETH_CFM_MISMERGE, or ETH_CFM_UNEXPERI alarm.
If... Then...
Any of the preceding alarms occurs Clear the alarm at the remote end.

OptiX RTN 620
If... Then...
No such alarms occur Go to Cause 2.
Step 2 Cause 2: The software is reset or another software fault occurs at the remote MEP.
(1) Check whether the equipment at the remote MEP is reset.
If... Then...
The equipment is reset Rectify the fault and then end the alarm handling.
The alarm is not reported Perform a warm reset on the board where the remote MEP
is located. For details, see 7.6.2 Warm Resetting.
----End
Related Information
None.
A.2.35 ETH_LOS
Description
The ETH_LOS is an alarm indicating the loss of Ethernet port connection.
Attribute
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 Ethernet port 1 of the
board.
Parameter 2, Parameter 3 The values are always 0x00 0x01.

When the ETH_LOS alarm occurs, the service at the port that reports the alarm is interrupted.

OptiX RTN 620
Possible Causes
l Cause 1: The negotiation fails because the transmit port and receive port work in different
modes.
l Cause 2: The link of electrical cable or optical fiber is faulty.
l Cause 3: The equipment is faulty.
Procedure
Step 1 Cause 1: The negotiation fails because the transmit port and receive port work in different modes.
(1) Check whether the transmit port and receive port work in the same mode.
If... Then...
The transmit port and receive port work Correctly set the working modes of the
in different modes transmit port and receive port.
The transmit port and receive port work Go to Cause 2.
in the same mode
Step 2 Cause 2: The link of electrical cable or optical fiber is faulty.

(1) Check the network cable or optical fiber connected to the port that reports the alarm.
If... Then...
The network cable is loose or damaged Connect the network cable properly or
replace the damaged network cable.
The connector of the fiber jumper is dirty Clean the connector.
The connector is loosely connected or Insert the connector properly or replace the
damaged damaged fiber jumper.
The connection is normal Go to Cause 3.
Step 3 Cause 3: The equipment is faulty.

(1) Check whether any fault occurs on the equipment interconnected with the port that reports
the alarm.
If... Then...
The equipment is faulty Rectify the fault.
The equipment is normal Replace the alarmed board of the local site.
----End
Related Information
None.

OptiX RTN 620
A.2.36 ETHOAM_DISCOVER_FAIL
Description
The ETHOAM_DISCOVER_FAIL is an alarm indicating that the point-to-point Ethernet OAM
negotiation fails. This alarm occurs when the OAM function is enabled at a port of a board and
the negotiation between the port and the opposite equipment fails.
Attribute
Parameters
table.
Name Meaning
Parameter 1 Indicates the ID of the port that reports the alarm.
Parameter 4 Indicates the reason why the negotiation fails.

l 0x01: A fault occurs on the local receive link.
l 0x02: The local end fails to transmit OAM packets.
l 0x03: The OAM packets from the opposite end are not received.
l 0x04: The OAM configuration of the opposite end does not meet
the requirements of the local end.
l 0x05: The OAM configuration of the local end does not meet the
requirements of the opposite end.
l 0x06-0xFF: Other unknown reasons.

The OAM function based on IEEE802.3ah is unavailable.
Possible Causes
l Cause 1: The physical port of the local end is faulty.
l Cause 2: The P2P OAM protocol is not enabled at the opposite end.

OptiX RTN 620
l Cause 3: The OAM configuration at both ends is inconsistent.
Procedure
Step 1 Cause 1: The physical port of the local end is faulty.
(1) Check whether the physical port is faulty. Replace the alarmed board.
Step 2 Cause 2: The P2P OAM protocol is not enabled at the opposite end.
(1) Enable the P2P OAM protocol at the opposite end. For details, see Enabling the OAM
Auto-Discovery Function.
Step 3 Cause 3: The OAM configuration at both ends is inconsistent.

(1) Reconfigure the P2P OAM protocol and ensure the consistency at both ends. For details,
see Enabling the OAM Auto-Discovery Function.
----End
Related Information
None.
A.2.37 ETHOAM_RMT_CRIT_FAULT
Description
The ETHOAM_RMT_CRIT_FAULT is an alarm indicating that a critical fault occurs regarding
the point-to-point Ethernet OAM function at the remote end. This alarm occurs when a port with
the OAM function enabled receives the OAM packets that contain critical fault information from
the opposite end.
Attribute
Parameters
table.
Name Meaning

OptiX RTN 620
Name Meaning
Parameter 4 Indicates the type of the fault.

l 0x01: A link fault occurs at the port of the opposite end.
l 0x02: Irrecoverable problems such as power failure occur at the
opposite end.
l 0x03-0xFF: Other faults.

When the ETHOAM_RMT_CRIT_FAULT alarm occurs, the services on the link may be
interrupted.
Possible Causes
l Cause 1: A link fault occurs at the remote MEP.
l Cause 2: Irrecoverable problems such as power failure occur at the remote MEP.
l Cause 3: Other faults occur at the remote MEP.
Procedure
Step 1 Determine the fault type according to Parameter 4 and handle the fault accordingly.
If... Then...
The value of Parameter 4 is 0x01 Go to Cause 1.
The value of Parameter 4 is 0x03-0xFF, Go to Cause 3.
Step 2 Cause 1: A link fault occurs at the remote MEP.

(1) Handle ETH_LOS and LINK_ERR of the remote port.
Step 3 Cause 2: Irrecoverable problems such as power failure occur at the remote MEP.
(1) Handle the problems such as power failure at the remote MEP.
Step 4 Cause 3: Other faults occur at the remote MEP.
(1) Contact Huawei technical support engineers.
----End
Related Information
None.

OptiX RTN 620
A.2.38 ETHOAM_RMT_LOOP
Description
The ETHOAM_RMT_LOOP is an alarm indicating that the point-to-point Ethernet OAM
function detects a remote loopback. This alarm occurs when the local equipment initiates a
remote loopback or responds to the remote loopback initiated by the opposite equipment.
Attribute
Parameters
table.
Name Meaning
Parameter 4 l 0x01: The local equipment initiates a remote loopback.

l 0x02: The local equipment responds to the remote loopback
initiated by the opposite equipment.

When the ETHOAM_RMT_LOOP alarm occurs, the services on the link are interrupted.
Possible Causes
l Cause 1: The local end issues a loopback command and the opposite end responds to the
command.
l Cause 2: The opposite end issues a loopback command and the local end responds to the
command.
Procedure
Step 1 Check whether the loopback is initiated by the local end or by the remote end.
Step 2 Cause 1: The local end issues a loopback command and the opposite end responds to the
command.

OptiX RTN 620
(1) Determine the causes of the loopback at the local end and release the loopback.
Step 3 Cause 2: The opposite end issues a loopback command and the local end responds to the
command.
(1) Determine the causes of the loopback at the opposite end and release the loopback.
----End
Related Information
None.
A.2.39 ETHOAM_RMT_SD
Description
The ETHOAM_RMT_SD is an alarm indicating that the point-to-point Ethernet OAM function
detects signal degradation at the remote end. This alarm occurs when a port with the OAM
function enabled receives link event notification packets from the opposite end.
Attribute
Parameters
table.
Name Meaning
Parameter 4 Indicates the type of the received link event:

l 0x01: Errored frame event
l 0x02: Errored frame period event
l 0x03: Errored frame second event

When the ETHOAM_RMT_SD alarm occurs, the performance of services degrade.

OptiX RTN 620
Possible Causes
l Cause 1: The link event notification function is enabled at the opposite end.
l Cause 2: The link performance thresholds of the opposite end are inappropriate.
l Cause 3: The link performance deteriorates.
Procedure
Step 1 Cause 1: The link event notification function is enabled at the opposite end.
(1) Check whether the link event notification function is enabled at the opposite end.
If... Then...
The link event notification function is Disable the link event notification function
enabled at the opposite end at the opposite end.
The link event notification function is Go to Cause 2.
disabled at the opposite end
Step 2 Cause 2: The link performance thresholds of the opposite end are inappropriate.
(1) Check whether the link performance thresholds of the opposite end are appropriate.
If... Then...
The link performance thresholds of the Set the thresholds to appropriate values.
opposite end are inappropriate
The link performance thresholds of the Go to Cause 3.
opposite end are appropriate
Step 3 Cause 3: The link performance deteriorates.

(1) Improve the link performance at the opposite end so that the opposite end does not send
any link event packet to the local end. Then, the ETHOAM_RMT_SD alarm at the local
end clears automatically.
----End
Related Information
None.
A.2.40 ETHOAM_SELF_LOOP
Description
The ETHOAM_SELF_LOOP is an alarm indicating the loopback of the MAC port that runs the
point-to-point OAM protocol. This alarm occurs when the MAC port of a board receives the
OAM protocol packets sent by the port or the board after the loopback detection function is
enabled.

OptiX RTN 620
Attribute
Major Environmental alarms
Parameters
table.
Name Meaning
Parameter 1 Indicates the port ID.
Parameter 4 Indicates the loopback type.

l 0x01: self-loop of the port.
l 0x02: self-loop of the board.
l 0x03-0xFF: unknown types.

A network storm may occur owing to the loopback.
Possible Causes
l Cause 1: The cable connected to the port is self-looped, or the port is accessed to a LAN
that has a loopback, or a PHY/MAC loopback is manually configured at the port.
l Cause 2: Two ports of the board are connected through cables or two ports of the board are
accessed to the same LAN.
Procedure
Step 1 Determine the loopback type according to Parameter 4, and then handle the loopback
accordingly.
If... Then...
Step 2 Cause 1: The cable connected to the port is self-looped, or the port is accessed to a LAN that
has a loopback, or a PHY/MAC loopback is manually configured at the port.

OptiX RTN 620
If... Then...
The PHY/MAC loopback is manually Manually release the PHY/MAC loopback (or
configured at the port wait five minutes for the automatic release by
the NMS). Then, the self-loop is released.
A self-loop is performed at the cables of the Reconnect the cables to release the self-loop.
port
The port is accessed to a LAN with a self- Release the loopback of the LAN, or
loop disconnect the port from the LAN.
Step 3 Cause 2: Two ports of the board are connected through cables or two ports of the board are
accessed to the same LAN.
(1) Check whether two ports of the board are connected through cables or whether two ports
of the board are accessed to the same LAN.
If... Then...
The two ports are connected through Disconnect the cables to release the self-
cables loop.
The two ports are accessed to the same Disconnect a port from the LAN to release
LAN the self-loop.
----End
Related Information
None.
A.2.41 ETHOAM_VCG_SELF_LOOP
Description
The ETHOAM_VCG_SELF_LOOP is an alarm indicating that the point-to-point OAM function
detects a loopback at the VCTRUNK port. This alarm occurs when the loopback detection
function is enabled and the VCTRUNK port receives the OAM protocol packets transmitted by
the port itself or the board where the VCTRUNK port resides.
Attribute
Major Environment alarm
Parameters
table.

OptiX RTN 620
Name Meaning
Parameter 2, Parameter 3 Indicate the ID of the VCTRUNK port. Parameter 2 indicates the
most significant bit (MSB) and Parameter 3 indicates the least
significant bit (LSB).
Parameter 4 Indicates the loopback type.

l 0x01: The links connected to the port are configured into a loop.
l 0x02: The links between board ports are configured into a loop.
l 0x03-0xFF: unknown types.

When the ETHOAM_VCG_SELF_LOOP alarm occurs, a network storm may occur owing to
the loopback.
Possible Causes
l Cause 1: A loopback occurs on the lines connected to one VCTRUNK.
l Cause 2: The lines connected to two VCTRUNKs on the same board are interconnected.
Procedure
Step 1 Browse alarms on the NMS and determine the alarmed VCTRUNK according to Parameter 2.
Then, determine the loopback type according to Parameter 4.
If... Then...
Step 2 Cause 1: A loopback occurs on the lines connected to one VCTRUNK.

(1) Reconfigure the lines connected to the VCTRUNK port and ensure that the port is not self-
looped.
Step 3 Cause 2: The lines connected to two VCTRUNKs on the same board are interconnected.
(1) Reconfigure the lines connected to the VCTRUNK ports and ensure that the lines connected
to any two VCTRUNK ports on the same board are not interconnected.
----End
Related Information
None.

OptiX RTN 620
A.2.42 EX_ETHOAM_CC_LOS
Description
The EX_ETHOAM_CC_LOS is an alarm indicating the loss of periodic connectivity check
(CC) packets. This alarm occurs when the sink MEP fails to receive CC packets from the same
source MEP in a period (3.5 transmission periods of CC packets at the source MEP).
Attribute
Parameters
table.
Name Meaning
Parameter 1 Indicates the ID of the MEP that reports the alarm.
Parameter 2, Parameter 3 Indicates the number of the Ethernet port that reports the alarm.
l Port number: 0x0001-0x0000 + MAX_ETH_PORT.
l VCTRUNK port number: 0x8001-0x8000 +
MAX_ETH_VCTRUNK.
NOTE
l MAX_ETH_PORT indicates the maximum MAC port number
supported by a board.
l MAX_ETH_VCTRUNK indicates the maximum VCTRUNK port
number supported by a board.
Parameter 4, Parameter 5 Indicate the service VLAN ID.

l For a service with a VLAN tag, the VLAN ID ranges from
0x0000 to 0x0FFF.
l For a service without any VLAN tag, the VLAN ID is 0xFFFF.

OptiX RTN 620
Name Meaning
Parameter 6 Indicates the maintenance domain level.

NOTE
Consumer indicates the customer, provider indicates the supplier, and
operator indicates the carrier.
Parameter 7 Indicates the source MEP ID of CC packets.
Parameter 8 Indicates the sink MEP ID of CC packets.

NOTE
The sink MEP ID of CC packets is the ID of the MEP that reports the alarm.
Parameter 1 and Parameter 8 indicate the same information.

A unidirectional connectivity failure occurs in the Ethernet service between two MEPs.
Possible Causes
l Cause 1: The line between two MEPs is interrupted.
l Cause 2: The Ethernet services in the MA to which the alarmed MEP belongs are faulty.
l Cause 3: The services between two MEPs are congested or interrupted.
Procedure
Step 1 Cause 1: The line between two MEPs is interrupted.
(1) Check whether the physical links (such as network cables or optical fibers) that carry
services between the two MEPs are correctly connected.
If... Then...
The physical links are incorrectly Re-connect the cables to rectify the faults
connected on physical links.
The physical links are correctly connected Go to Cause 2.
Step 2 Cause 2: The Ethernet services in the MA to which the alarmed MEP belongs are faulty.
(1) Check whether the Ethernet services in the MA to which the alarmed MEP belongs are
configured correctly.

OptiX RTN 620
If... Then...
The Ethernet services are configured Change the configuration and ensure
incorrectly consistency at both ends.
The Ethernet services are configured Go to Cause 3.
correctly
Step 3 Cause 3: The services between two MEPs are congested or interrupted.
(1) Check the bandwidth utilization. If the bandwidth is exhausted, increase the bandwidth or
eliminate any source that transmits a large amount of invalid data.
----End
Related Information
None.
A.2.43 EX_ETHOAM_MPID_CNFLCT
Description
The EX_ETHOAM_MPID_CNFLCT is an alarm indicating the conflict of MPIDs. This alarm
occurs when two MEPs on one MD have the same maintenance point identity (MPID) and one
MEP receives the packets from the other MEP.
Attribute
Major Environment alarm
Parameters
table.
Name Meaning
Parameter 1 Indicates the MPID associated with the alarm.

OptiX RTN 620
Name Meaning
Parameters 2, Parameter 3 Indicate the number of the Ethernet port that reports the alarm.
l MAC port number: 0x0001-0x0000 + MAX_ETH_PORT.
l VCTRUNK port number: 0x8001-0x8000 +
MAX_ETH_VCTRUNK.
NOTE
l MAX_ETH_PORT indicates the maximum MAC port number
supported by a board.
l MAX_ETH_VCTRUNK indicates the maximum VCTRUNK port
number supported by a board.
Parameters 4, Parameter 5 Indicate the service VLAN ID.

l For a service with a VLAN tag, the VLAN ID ranges from
0x0000 to 0x0FFF.
l For a service without any VLAN tag, the VLAN ID is 0xFFFF.
Parameter 6 Indicates the maintenance domain level.

l 0x00: Consumer MEP level (high).
l 0x01: Consumer MEP level (middle).
l 0x02: Consumer MEP level (low).
l 0x03: Provider MEP level (high).
l 0x04: Provider MEP level (low).
l 0x05: Operator MEP level (high).
l 0x06: Operator MEP level (medium).
l 0x07: Operator MEP level (low).
NOTE
Consumer indicates the customer, provider indicates the supplier, and
operator indicates the carrier.
Parameter 7 Indicates the ID of the local MEP.

NOTE
The ID of the local MEP is the ID of the MEP that reports the alarm.
Parameter 1 and Parameter 7 indicate the same information.

MPIDs must be unique on a network. When the EX_ETHOAM_MPID_CNFLCT alarm occurs,
the LB and LT functions are abnormal and OAM packets are received incorrectly.
Possible Causes
Cause 1: At least two MEPs in an MD have the same MPID.

OptiX RTN 620
Procedure
Step 1 Cause 1: At least two MEPs in an MD have the same MPID.
(1) Check this alarm on the NMS. Determine the associated MPID according to Parameter 1.
(2) Query the information about the MEP. Delete the incorrect MEPs and create MEPs with
unique MPIDs.
----End
Related Information
None.
A.2.44 EXT_SYNC_LOS
Description
The EXT_SYNC_LOS is an alarm of the loss of external clock sources.
Attribute
Critical Equipment alarm
Parameters
table.
Name Meaning
Parameter 1 Indicates the ID of the lost external clock source. For example, 0x01 indicates
that external clock source 1 is lost.

l When the EXT_SYNC_LOS alarm occurs, if only the external clock source and the internal
clock source are configured in the clock source priority list, the NE traces the internal clock
source after the external clock source is lost and enters the free-run state 24 hours later.
l If another valid clock source of higher priority and good quality is configured in the clock
source priority list, however, the clock protection switching occurs.
Possible Causes
Cause 1: The external clock source is configured in the clock source priority list, but the external
clock source cannot be detected or become invalid.

OptiX RTN 620
Procedure
Step 1 Cause 1: The external clock source is configured in the clock source priority list, but the external
clock source cannot be detected or become invalid.
(1) Check whether the equipment that provides the external clock source is faulty.
If... Then...
The equipment is normal Go to the next step.
(2) Check whether the cable that connects the external clock source is normal.
If... Then...
The cable is abnormal Replace the cable.
The cable is normal Replace the PXC board.
----End
Related Information
None.
A.2.45 F1PORT_FAILED
Description
The F1PORT_FAILED is an alarm indicating that synchronous data interfaces fail. This alarm
occurs when the software configures data of synchronous data interfaces but the hardware of
the SCC board does not support the data.
Attribute
Parameters
None.

When the F1PORT_FAILED alarm occurs, the service configuration for synchronous data
interfaces is invalid.
Possible Causes
Cause 1: The pluggable storage card installed on the SCC board stores the configuration data
for synchronous data interfaces, but the hardware of the SCC board does not support any
synchronous data interface.

OptiX RTN 620
Procedure
Step 1 Cause 1: The pluggable storage card installed on the SCC board stores the configuration data
for synchronous data interfaces, but the hardware of the SCC board does not support any
synchronous data interface.
(1) Determine whether the data of synchronous data interfaces is necessary.
If... Then...
The data is necessary Go to the next step.
The data is unnecessary Delete the data of synchronous data interfaces through the
NMS.
(2) Use the SCC board of SL61 VER.C or a later version.
----End
Related Information
None.
A.2.46 FAN_FAIL
Description
The FAN_FAIL is an alarm indicating that the fan is faulty.
Attribute
Parameters
None.

When the FAN_FAIL alarm occurs, the heat dissipation of the system is affected.
Possible Causes
l Cause 1: The board and the backplane are connected incorrectly.
Procedure
Step 1 Cause 1: The board and the backplane are connected incorrectly.
(1) Remove the fan board. Clean the dust on the fan and reinsert the fan board.

OptiX RTN 620
If... Then...
The alarm persists after the board is Go to Cause 2.
removed and inserted

(1) Replace the alarmed fan board.
----End
Related Information
None.
A.2.47 FCS_ERR
Description
The FCS_ERR is an alarm indicating the errors of frame check sequence (FCS). This alarm
occurs when a board detects FCS errors in the received frames.
Attribute

Parameters
table.
Name Meaning

When the FCS_ERR alarm occurs, if the encapsulation protocols or encapsulation parameters
are inconsistent at both ends of Ethernet services, the services may have errors and even become
interrupted.

OptiX RTN 620
Possible Causes
l Cause 1: The encapsulation protocols or encapsulation parameters are inconsistent at both
ends of services.
l Cause 2: Service channels have errors.
Procedure
Step 1 Cause 1: The encapsulation protocols or encapsulation parameters are inconsistent at both ends
of services.
(1) Check whether the encapsulation protocols or encapsulation parameters are consistent at
both ends of services.
If... Then...
The protocols are inconsistent Correct the configuration data.
The protocols are consistent Go to the next step.
Step 2 Cause 2: Service channels have errors.

(1) Check whether the encapsulation parameters are consistent at both ends of services.
If... Then...
The parameters are inconsistent Correct the configuration data.
The parameters are consistent Go to the next step.
(2) Check whether any error alarm or performance event occurs on the line board that carries
the services.
If... Then...
Yes Handle the alarm or performance event.
No Go to the next step.

If... Then...
replaced handling.
The alarm persists after the board is Replace the PXC board.
replaced
----End
Related Information
None.
A.2.48 FLOW_OVER

OptiX RTN 620
Description
The FLOW_OVER is an alarm indicating that the data flow received by the Ethernet port exceeds
the threshold.
Attribute
Parameters
table.
Name Meaning
Parameter 1 Indicates the ID of the path that reports the alarm.
Parameter 2 Indicates the ID of the subboard.
Parameter 3 Indicates the port ID. For example, 0x01 indicates that the alarm is reported by
Ethernet port 1 of the board.

When the FLOW_OVER alarm occurs, the extra data may be discarded by the port.
Possible Causes
Cause 1: The opposite end transmits excessive data flow.
Procedure
Step 1 Cause 1: The opposite end transmits excessive data flow.
(1) Configure the QoS policies at the opposite end to reduce the data flow that the opposite
end transmits to the local end.
----End
Related Information
None.
A.2.49 HARD_BAD
Description
The HARD_BAD is an alarm indicating hardware errors.

OptiX RTN 620
Attribute

Parameters
table.
Name Meaning
Parameter 1 Indicates the cause of the fault.
l 0x01: The power module is working abnormally.
l 0x02: The board is installed improperly.
l 0x03: 38 MHz system clock 1 is abnormal.
l 0x04: 38 MHz system clock 2 is abnormal.
l 0x05: 2 MHz clock source is abnormal.
l 0x06: The digital phase-locked loop is abnormal.
l 0x07: The 38 MHz service clock is lost.
l 0x08: The bus is abnormal.
l 0x09: The TPS protection board is abnormal.
l 0x0A: The primary crystal oscillator stops oscillating.
l 0x0B: The frequency offset of the primary crystal oscillator is excessive.
l 0x0C: The secondary crystal oscillator stops oscillating.
l 0x0D: The processor (CPU/DSP/coprocessor) is faulty.
l 0x0E: The storage components are faulty.
l 0x0F: The programmable logic device is faulty.
l 0x10: The SDH components are faulty.
l 0x11: The data communication components are faulty.
l 0x12: The clock components are faulty.
l 0x13: The interface components are faulty.
l 0x14: The power components are faulty.
l 0x15: Another fault occurs.
l 0x16: The analog phase-locked loop is abnormal.
l 0x17: The 32 MHz clock is unavailable.

OptiX RTN 620

The board that reports the alarm fails to work. If the board is configured with 1+1 protection,
the protection switching may be triggered.
Possible Causes
l Cause 1 of the alarm reported by a board of the IDU: The board and backplane are connected
improperly.
l Cause 2 of the alarm reported by a board of the IDU: The board is faulty.
l Cause 3 of the alarm reported by a board of the IDU: The slot is faulty.
Cause of the alarm reported by a board of the ODU: The ODU is faulty.
Procedure
Step 1 Cause 1 of the alarm reported by a board of the IDU: The board and backplane are connected
improperly.
(1) Remove and insert the alarmed board. For details, see 6.1 Removing a Board and 6.2
Inserting a Board. Then, check whether the alarm clears.
If... Then...
The alarm disappears after the board is The fault is rectified. End the alarm
The alarm persists after the board is Ensure that the board is normal.
replaced
Step 2 Cause 2 of the alarm reported by a board of the IDU: The board is faulty.
(1) Replace the board that reports the alarm, and then check whether the alarm clears. For
details, see 6 Part Replacement.
If... Then...
replaced handling.
The alarm persists after the board is Ensure that the slot is normal.
replaced
Step 3 Cause 3 of the alarm reported by a board of the IDU: The slot is faulty.
(1) Contact Huawei engineers to handle the faulty slot.
TIP
The slot becomes faulty due to broken pins or bent pins. Remove the board, and use a torch to observe
whether there is any broken pin or bent pin.
(2) If an idle slot is available, insert the board in the idle slot and add the board on the NMS
again. Then, the board can work normally.
Step 4 Cause of the alarm reported by a board of the ODU: The ODU is faulty.
(1) Replace the ODU that reports the alarm. For details, see 6.12 Replacing an ODU.
----End

OptiX RTN 620
Related Information
None.
A.2.50 HP_CROSSTR
Description
The HP_CROSSTR is an alarm indicating a threshold-crossing event of the higher order path.
This alarm occurs when a board detects any threshold-crossing event of the higher order path.
Attribute
Minor Service alarm
Parameters
table.
Name Meaning
Parameter 1 Indicates the performance monitoring period.
l 0x01: 15 minutes
l 0x02: 24 hours
Parameter 2, Parameter 3 Indicate the ID of the performance event that causes the alarm.

When the HP_CROSSTR alarm occurs, a large number of errors occur in services, and services
may be interrupted.
Possible Causes
Cause 1: Higher order path errors cross the preset threshold.
Procedure
Step 1 Cause 1: Higher order path errors cross the preset threshold.
(1) Check the threshold-crossing records to find out the performance event that causes the
alarm. For details, see 7.3.8 Browsing the Performance Event Threshold-Crossing
Records.

OptiX RTN 620
(2) Handle the threshold-crossing performance event.
----End
Related Information
None.
A.2.51 HP_LOM
Description
The HP_LOM is an alarm of the loss of the higher order path multiframe. This alarm occurs
when the board detects that byte H4 is inconsistent with the expected multiframe sequence.
Attribute

Parameters
table.
Name Meaning
0x01 indicates that the alarm is reported by port 1 of the
corresponding board.
Parameter 2, Parameter 3 Indicates the ID of the AU-4 path that reports the alarm. For
example, 0x00 0x01 indicate that the alarm is reported by path 1 of
the SDH signal.

When the HP_LOM alarm occurs, the service on the path that reports the alarm is interrupted.
If the service is configured with protection, the protection switching is also triggered.
Possible Causes
l Cause 1: The transmit unit of the opposite site is faulty.
l Cause 2: The receive unit of the local site is faulty.

OptiX RTN 620
Procedure
Step 1 Cause 1: The transmit unit of the opposite site is faulty.
(1) Replace the line board or IF board of the opposite site. For details, see 6 Part
Replacement. Then, check whether the alarm clears.
If... Then...
The alarm clears The fault is rectified. End the alarm handling.
The alarm persists Replace the PXC board of the local site.
Step 2 Cause 2: The receive unit of the local site is faulty.

(1) Replace the board that reports the alarm. For details, see 6 Part Replacement.
----End
Related Information
None.
A.2.52 HP_RDI
Description
The HP_RDI is an alarm indicating a remote defect in the higher order path. This alarm occurs
when the board detects that bit 5 of byte G1 is 1.
Attribute

Parameters
table.
Name Meaning
SDH signal.

OptiX RTN 620

When the HP_RDI occurs, the service at the local site is not affected. The service received by
the opposite site, however, is interrupted.
Possible Causes
Cause 1: The local site detects the message that is returned by the opposite site and indicates the
higher order path remote receive failure.
Procedure
Step 1 Cause 1: The local site detects the message that is returned by the opposite site and indicates the
(1) Determine the AU-4 path that reports the alarm based on the alarm parameter.
(2) Clear the alarms such as HP_LOM and B3_EXC that the AU-4 path reports at the opposite
site.
----End
Related Information
None.
A.2.53 HP_REI
Description
The HP_REI is an alarm indicating the higher order path remote error. This alarm occurs when
the board detects that bits 1-4 of byte G1 take a value from 1 to 8.
Attribute
Warning Communication alarm
Parameters
table.
Name Meaning

OptiX RTN 620
Name Meaning
SDH signal.

The service at the local site is not affected. The service received by the opposite site, however,
has errors.
Possible Causes
The local site detects the message that is returned by the opposite site and indicates the higher
order path remote errors.
Procedure
Step 1 Cause: The local site detects the message that is returned by the opposite site and indicates the
(1) Determine the AU-4 path that reports the alarm based on the alarm parameter.
(2) Handle the HP_BBE performance event that the AU-4 path reports on the opposite NE.
----End
Related Information
None.
A.2.54 HP_SLM
Description
The HP_SLM is an alarm indicating signal label mismatch in the higher order path. This alarm
occurs when the board detects the C2 byte mismatch.
Attribute
Parameters
table.

OptiX RTN 620
Name Meaning
SDH signal.

None.
Possible Causes
l Cause 1: The receivable C2 byte at the local site does not match with the C2 byte transmitted
at the opposite site.
l Cause 2: Configuration data is incorrect.
Procedure
Step 1 Determine the line port and AU-4 path that report the alarm based on the alarm parameter.
Step 2 Cause 1: The receivable C2 byte at the local site does not match with the C2 byte transmitted at
the opposite site.
(1) Configure the same service type at the source and sink of the AU-4 path. For details, see
Configuring VC-4 POHs.
Step 3 Cause 2: Configuration data is incorrect.
(1) If the port that reports the alarm is the SDH port that is interconnected with the ATM/
Ethernet equipment, configure the service as VC-4 pass-through service. For details, see
Creating Cross-Connections for SNCP Services.
----End
Related Information
None.
A.2.55 HP_TIM
Description
The HP_TIM is an alarm indicating that the higher order path trace identifier is mismatched.
This alarm occurs when the board detects the J1 byte mismatch.
Attribute

OptiX RTN 620
Parameters
table.
Name Meaning
SDH signal.

If the service is configured with the protection that considers the HP_TIM alarm as a trigger
condition, the protection switching is triggered.
Possible Causes
l Cause 1: the J1 byte to be received at the local site does not match the J1 byte transmitted
at the opposite site.
Procedure
Step 1 Determine the line port and AU-4 path that report the alarm based on the alarm parameter.
Step 2 Cause 1: The J1 byte to be received at the local site does not match the J1 byte transmitted at
the opposite site.
(1) Disable the J1 byte to be received at the local site or set the J1 byte to be received at the
local site to the same as the transmitted J1 byte at the opposite site. For details, see
Configuring VC-4 POHs.
(1) If the port that reports the alarm is the SDH port that is interconnected with the ATM/
Ethernet equipment, configure the service as VC-4 pass-through service. For details, see
Creating Cross-Connections of Point-to-Point Services or Creating Cross-Connections for
SNCP Services.
If... Then...
The alarm clears after the configuration is The fault is rectified. End the alarm
changed handling.
The alarm persists after the configuration Go to the next step.
is changed
(2) Check whether the cross-connections are configured correctly at the intermediate nodes
where the service travels. If not, reconfigure the cross-connections. For details, see Creating

OptiX RTN 620
Cross-Connections of Point-to-Point Services or Creating Cross-Connections for SNCP

Services.
----End
Related Information
None.
A.2.56 HP_UNEQ
Description
The HP_UNEQ is an alarm indicating the unequipped higher order path. This alarm occurs when
the board detects that the C2 byte is 0.
Attribute
Parameters
table.
Name Meaning
SDH signal.

When the HP_UNEQ alarm occurs, the service in the AU-4 path that reports the alarm is
unavailable. If the service is configured with the protection that considers the alarm as a trigger
condition, the protection switching is triggered.
Possible Causes
l Cause 1: The line port at the local site is configured with services, but the corresponding
line port at the opposite site is not configured with services.
l Cause 2: The C2 byte on the opposite end is set to 0.

OptiX RTN 620
Procedure
Step 1 Cause 1: The line port at the local site is configured with services, but the corresponding line
port at the opposite site is not configured with services.
(1) Configure line services at the opposite site. For details, see Creating Cross-Connections of
Point-to-Point Services or Creating Cross-Connections for SNCP Services.
Step 2 Cause 2: The C2 byte at the opposite site is set to 0.

(1) Change the setting of the C2 byte. For details, see Configuring VC-4 POHs.
----End
Related Information
None.
A.2.57 HPAD_CROSSTR
Description
The HPAD_CROSSTR is an alarm indicating that the higher order path adaptation performance
crosses the threshold. This alarm occurs when a board detects that the performance event of TU
pointer justification crosses the preset threshold.
Attribute

Minor Service alarm
Parameters
table.
Name Meaning
Parameter 2, Parameter 3 Indicate the ID of the path that reports the alarm.
Parameter 4, Parameter 5 l The higher two bits of Parameter 4 indicate the performance
monitoring period (01 for 15 minutes, and 02 for 24 hours).
l The lower six bits of Parameter 4 and Parameter 5 indicate the
ID of a performance event.

OptiX RTN 620

When the HPAD_CROSSTR alarm occurs, bit errors may occur in the service.
Possible Causes
The performance event of TU pointer justification crosses the preset threshold.
Procedure
Step 1 Cause: The performance event of TU pointer justification crosses the preset threshold.
(1) Check the threshold crossing records to find out the performance event of TU pointer
justification that crosses the preset threshold. For details, see 7.3.8 Browsing the
Performance Event Threshold-Crossing Records.
----End
Related Information
None.
A.2.58 IF_CABLE_OPEN
Description
The IF_CABLE_OPEN is an alarm indicating that the IF cable is open-circuited.
Attribute
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 corresponding board.

The services on the IF port are interrupted.

OptiX RTN 620
Possible Causes
l Cause 1: The IF cable is loose or faulty.
l Cause 2: The IF port of the IF board is damaged.
l Cause 3: The power module of the ODU is faulty.
Procedure
Step 1 Cause 1: The IF cable is loose or faulty. Check whether the connector of the IF cable is loose or
whether the connector is not made properly.
(1) Check whether the connector of the IF cable is loose or whether the connector is not made
properly.
The connectors to be checked include the connector between the IF fiber jumper and the
IF board, the connector between the IF fiber jumper and the IF cable, and the connector
between the IF cable and the ODU.
If... Then...
The connector is loose Connect the connector tightly.
The connector is not made properly Make a new IF cable connector.
None of the above Go to the next step.
(2) Check whether the surface of the IF fiber jumper and the IF cable is damaged, and test the
connectivity between the IF fiber jumper and the IF cable. For details, see Testing the
connectivity between cables.
If... Then...
The cable does not meet the specified Replace the cable with a proper one.
requirement
The cable meets the specified requirement Go to Cause 2 or Cause 3.
Step 2 Cause 2: The IF port of the IF board is damaged.

(1) Replace the IF board that reports the alarm.
Step 3 Cause 3: The power module of the ODU is faulty.

(1) Replace the ODU connected to the IF board that reports the alarm.
----End
Related Information
NOTE
When rectifying the faults on the IF cable, IF port, and ODU, you must turn off the ODU before the
operation. You can turn on the ODU only after the operation is complete.
A.2.59 IF_INPWR_ABN

OptiX RTN 620
Description
The IF_INPWR_ABN is an alarm indicating that the input IF power of the ODU is abnormal.
Attribute
Parameters
table.
Name Meaning
Parameter 1 l 0x01: Indicates that the input power of the ODU is over high.
l 0x02: Indicates that the input power of the ODU is over low.

The services on the ODU are interrupted. If 1+1 protection is configured, 1+1 HSB switching
may be triggered.
Possible Causes
l Cause 1: The IF board is faulty.
l Cause 2: The IF cable is faulty.
l Cause 3: The ODU is faulty.
Procedure
Step 1 Cause 1: The IF board is faulty.
(1) Reseat the board. For details, see 6.1 Removing a Board or 6.2 Inserting a Board. Then,
If... Then...
The alarm clears End the alarm handling.
The alarm persists Go to the next step.
(2) Replace the IF board connected to the ODU that reports the alarm.
Step 2 Cause 2: The IF cable is faulty.

(1) Check whether the connector of the IF cable is loose or whether the connector is not made
properly.

OptiX RTN 620
The connectors to be checked include the connector between the IF fiber jumper and the
IF board, the connector between the IF fiber jumper and the IF cable, and the connector
between the IF cable and the ODU.
If... Then...
The connector is loose Connect the connector tightly.
The connector is not made properly Terminating the IF Cable with Connectors again.
None of the above Go to the next step.
(2) Check whether the surface of the IF fiber jumper and the IF cable is damaged or deformed,
and test the connectivity between the IF fiber jumper and the IF cable. For details, see
Testing the Connectivity of the IF Cable.
If... Then...
The cable does not meet the specified Replace the cable with a proper one.
requirement
The cable meets the specified requirement The IF board or ODU may be faulty.
Step 3 Cause 3: The ODU is faulty.

(1) Replace the ODU that reports the alarm.
----End
Related Information
The number of the logical slot for the ODU is the slot number of the IF board connected to the
ODU plus 10.
A.2.60 IF_MODE_UNSUPPORTED
Description
The IF_MODE_UNSUPPORTED is an alarm indicating that the configured IF working mode
is not supported. This alarm occurs when the board is not loaded with the FPGA file that supports
the configured IF working mode.
Attribute
Parameters
table.

OptiX RTN 620
Name Meaning
Parameter 1 Indicates the number of the FPGA file that is loaded to the board.
l 0x01: Indicates that the ID of the FPGA file loaded to the board is 250.
l 0x02: Indicates that the ID of the FPGA file loaded to the board is 002.

The services on the IF port are interrupted.
Possible Causes
The board is not loaded with the FPGA file that supports the configured IF working mode, or
the FPGA file that supports the configured IF working mode is damaged.
Procedure
Step 1 Cause 1: The board is not loaded with the FPGA file that supports the configured IF working
mode, or the FPGA file that supports the configured IF working mode is damaged.
(1) Contact Huawei engineers to upgrade the board software and the FPGA file.
----End
Related Information
None.
A.2.61 IN_PWR_HIGH
Description
The IN_PWR_HIGH is an alarm indicating that the input optical power is over high.
Attribute

Parameters
table.

OptiX RTN 620
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 corresponding
board.

The service at the optical interface that reports the alarm has errors.
Possible Causes
l Cause 1: The transmit power of the opposite site is over high.
l Cause 2: The model of the selected optical module is incorrect.
l Cause 3: The optical module at the receive end is faulty.
Procedure
Step 1 Determine the optical interface that reports the alarm based on the alarm parameter.
Step 2 Cause 1: The transmit power of the opposite site is over high.
(1) Browse current performance events, and query the performance events of the transmit
optical power on the opposite NE.
If... Then...
The transmit optical power does not meet Contact Huawei engineers to replace the
the requirement optical module.
The transmit optical power meets the Add a proper attenuator to reduce the
requirement received optical power.
Step 3 Cause 2: The model of the selected optical module is incorrect.

(1) Query the board manufacturing information report, and check whether the models of
the SFP optical modules on both ends are proper.
If... Then...
The models are incorrect Contact Huawei engineers to replace the optical module.
The models are correct Go to Cause 3.
Step 4 Cause 3: The optical module at the receive end is faulty.

(1) Use the optical power meter to test the received optical power, and check whether the
received optical power meets the requirement. If not, contact Huawei engineers to replace
the optical module.
----End
Related Information
The optical power threshold set for the IN_PWR_HIGH alarm is lower than the overload point.
SDH Interface Performance.

OptiX RTN 620
A.2.62 IN_PWR_LOW
Description
The IN_PWR_LOW is an alarm indicating that the input optical power is over low.
Attribute
Parameters
table.
Name Meaning
board.

When the IN_PWR_LOW alarm occurs, the service at the optical interface that reports the alarm
has errors.
Possible Causes
l Cause 1: The transmit power of the opposite site is over low.
l Cause 2: The model of the selected optical module is incorrect.
l Cause 3: The optical module at the receive end is faulty.
l Cause 4: The optical fiber performance degrades.
Procedure
Step 1 Determine the optical interface that reports the alarm based on the alarm parameter.
Step 2 Cause 1: The transmit power of the opposite site is over low.
(1) Browse current performance events, and query the performance events of the transmit
optical power at the opposite site.
If... Then...
The transmit optical power does not meet Contact Huawei engineers to replace the
the requirement optical module.

OptiX RTN 620
If... Then...
The transmit optical power meets the Go to Cause 2.
requirement
Step 3 Cause 2: The model of the selected optical module is incorrect.

(1) Query the board manufacturing information report, and check whether the models of
the SFP optical modules on both ends are proper.
If... Then...
The models are incorrect Contact Huawei engineers to replace the optical module.
The models are correct Go to Cause 3.
Step 4 Cause 3: The optical module at the receive end is faulty.

(1) Use the optical power meter to test the received optical power, and check whether the
received optical power meets the requirement.
If... Then...
The received optical power meets the Contact Huawei engineers to replace the
requirement optical module.
The received optical power does not meet Go to Cause 4.
the requirement
Step 5 Cause 4: The optical fiber performance degrades.

(1) Cleaning Fiber Connectors and Adapters.
If... Then...
The alarm clears after the connector is The fault is rectified. End the alarm handling.
cleaned
The alarm persists after the connector is Replace the optical fiber.
cleaned
----End
Related Information
The optical power threshold set for the IN_PWR_LOW alarm is higher than the sensitivity point.
SDH Interface Performance.
A.2.63 J0_MM
Description
The J0_MM is an alarm indicating that the trace identifier is mismatched. This alarm occurs
when the board detects a mismatch between the J0 bytes at both ends.

OptiX RTN 620
Attribute
Parameters
table.
Name Meaning

None.
Possible Causes
The J0 byte to be received at the local site does not match the J0 byte transmitted at the opposite
site.
Procedure
Step 1 Cause: The J0 byte to be received at the local site does not match the J0 byte transmitted at the
opposite site.
(1) Determine the line port that reports the alarm based on the alarm parameters.
(2) Disable the J0 byte to be received at the local site. For details, see Configuring RSOHs.
----End
Related Information
None.
A.2.64 K1_K2_M
Description
The K1_K2_M is an alarm indicating the K1/K2 byte mismatch. This alarm occurs when the
board detects that the channel numbers that are indicated by the transmitted K1 byte (bits 5-8)
and the received K2 byte (bits 1-4) are different.

OptiX RTN 620
Attribute
Parameters
table.
Name Meaning
l 0x01: Indicates linear MSP.
l 0x02: Indicates ring MSP.

When the K1_K2_M alarm occurs, the MSP protocol may fail and thus the protection switching
may fail.
Possible Causes
l Cause 1: The switching modes configured at both ends are different, that is, single-ended
switching mode at one end and dual-ended switching mode at the other end.
l Cause 2: The optical fiber connection is incorrect.
Procedure
Step 1 Cause 1: The switching modes configured at both ends are different, that is, single-ended
switching mode at one end and dual-ended switching mode at the other end.
(1) Check whether the switching modes configured at both ends are the same. For details, see
Querying the Status of Linear MSP.
If... Then...
The switching modes configured at both ends Set the switching modes to the same.
are different
The switching modes configured at both ends Go to Cause 2.
are the same
Step 2 Cause 2: The optical fiber connection is incorrect.

(1) Check whether the optical fiber connection is correct. For example, the optical fiber at the
receive or transmit port may be incorrectly connected, or disconnected.

OptiX RTN 620
If... Then...
The connection is not correct Connect the optical fiber properly.

(1) Replace the line board at the opposite site. Then, check whether the alarm clears.
If... Then...
Yes The fault is rectified. End the alarm handling.
No Replace the board that reports the alarm.
----End
Related Information
None.
A.2.65 K2_M
Description
The K2_M is an alarm indicating the K2 byte mismatch. This alarm occurs when the board
detects that the protection mode indicated by the received K2 (bit 5) is different from the
protection mode of the local NE.
Attribute

Parameters
table.
Name Meaning
l 0x01: Indicates linear MSP.
l 0x02: Indicates ring MSP.

OptiX RTN 620

When the K2_M alarm occurs, the MSP protocol may fail and thus the protection switching may
fail.
Possible Causes
l Cause 1: Two NEs of the linear MSP group are configured with different protection modes
(1+1 or 1:N).
l Cause 2: The MSP protocol is stopped when the protection switching occurs.
l Cause 3: The optical fiber connection is incorrect.
Procedure
Step 1 Cause 1: Two NEs of the linear MSP group are configured with different protection modes (1
+1 or 1:N).
(1) Check whether two NEs of the linear MSP group are configured with different protection
modes (1+1 or 1:1). For details, see Querying the Status of Linear MSP.
If... Then...
The protection modes are different Set the protection modes to the same.
The protection modes are the same Go to Cause 2.
Step 2 Cause 2: The MSP protocol is stopped on the opposite NE when the protection switching occurs.
(1) Check whether the MSP protocol is stopped on the opposite NE. For details, see Querying
the Status of Linear MSP.
If... Then...
Yes Restart the MSP protocol on the opposite NE. For details, see Starting/Stopping the
Linear MSP Protocol.
No Go to Cause 3.
Step 3 Cause 3: The optical fiber connection is incorrect.

(1) Check whether the optical fiber connection is correct. For example, the optical fiber at the
receive or transmit port may be incorrectly connected, or disconnected.
If... Then...
The connection is not correct Connect the optical fiber properly.

(1) Replace the line board at the opposite site. For details, see 6.3 Replacing the SDH Optical
Interface Board or 6.4 Replacing the SDH Electrical Interface Board. Then, check
whether the alarm clears.

OptiX RTN 620
If... Then...
Yes The fault is rectified. End the alarm handling.
No Replace the SCC board that reports the alarm. For details, see 6.10 Replacing the
SCC Board.
----End
Related Information
None.
A.2.66 LAG_PORT_FAIL
Description
The LAG_PORT_FAIL is an alarm indicating that a port in the LAG of the Ethernet fails. This
alarm occurs when a port in the LAG is unavailable.
Attribute
Parameters
table.
Name Meaning
Parameter 1 Indicates the ID of the IP port.
Parameter 4 Indicates the cause of the protection failure.

l 0x01: Indicates that the link of the port is faulty or fails.
l 0x02: Indicates that the port is in half-duplex mode.
l 0x03: Indicates that the port fails to receive LACP packets.
l 0x04: Indicates that the port detects a self-loop.
l 0x05: Indicates other unknown reasons.
Parameter 5 The value is always 0xff.

OptiX RTN 620

The port in the LAG cannot share the service load, or the port does not transmit or receive any
services.
Possible Causes
l Cause 1: The port is disabled or the link is faulty.
l Cause 2: The port is in the half-duplex mode.
l Cause 3: The port fails to receive LACP packets.
l Cause 4: The port detects a self-loop.
l Cause 5: other unknown reasons.
Procedure
Step 1 Determine the port where the alarm occurs and the alarm cause based on the alarm parameter.
If... Then...
Step 2 Cause 1: The port is disabled or the link is faulty.

(1) On the NMS, check whether the port in the LAG is enabled.
If... Then...
The port is not enabled Enable the port in the LAG group.
The port is enabled Check the link state of each port. If any link is faulty, rectify
the fault.
Step 3 Cause 2: The port is in the half-duplex mode.

(1) On the NMS, check the working mode of the port in the LAG group. If the port is in half-
duplex mode, change the working mode of the port into full-duplex.
Step 4 Cause 3: The port fails to receive the LACP packets.

(1) On the NMS, check whether the LAG group is properly configured on the opposite end.
If... Then...
The LAG group is not properly configured Reconfigure the LAG group.
The LAG group is properly configured Go to the next step.
(2) Check whether the local port and the remote port transmit the LACP packets. If the LACP
packets are not transmitted, configure the ports at both ends to ensure that the packets can
be normally transmitted.

OptiX RTN 620
Step 5 Cause 4: The port detects a self-loop.

(1) Release the self-loop of the port.
Step 6 Cause 5: other unknown reasons

(1) Contact Huawei engineers to handle the fault.
----End
Related Information
None.
A.2.67 LAG_VC_PORT_FAIL
Description
The LAG_VC_PORT_FAIL is an alarm indicating that a VCG port in the LAG fails. This alarm
occurs when the VCTRUNK is unavailable.
Attribute
Parameters
table.
Name Meaning
Parameter 2, Parameter 3 Indicate the number of the faulty VCG port in the LAG. Parameter
2 indicates the most significant bit (MSB) and Parameter 3 indicates
the least significant bit (LSB).
Parameter 4 Indicates the cause of the protection failure.

l 0x01: Indicates that the link of the port is faulty or fails.
l 0x03: Indicates that the port fails to receive the LACP packets.
l 0x04: Indicates that the links of the port are configured into a
loop.
l 0x05: Other unknown reasons.

OptiX RTN 620
Name Meaning
Parameter 5 The value is always 0xff.

The port in the LAG cannot share the service load, and the port does not transmit or receive any
services.
Possible Causes
l Cause 1: The link of the port is faulty or fails.
l Cause 2: The port fails to receive the LACP packets.
l Cause 3: The port detects a self-loop.
l Cause 4: other unknown reasons.
Procedure
Step 1 Determine the port where the alarm occurs and the alarm cause based on the alarm parameter.
If... Then...
Step 2 Cause 1: The port is disabled or the link is faulty.

(1) Check the link state of each port. If any link is faulty, rectify the fault.
Step 3 Cause 2: The port fails to receive the LACP packets.

(1) On the NMS, check whether the LAG group is properly configured on the opposite end.
If... Then...
The LAG group is not properly configured Reconfigure the LAG group.
The LAG group is properly configured Go to the next step.
(2) Check whether the local port and the remote port transmit the LACP packets. If the LACP
packets are not transmitted, configure the ports at both ends to ensure that the packets can
be normally transmitted.
Step 4 Cause 3: The port detects a self-loop.

(1) Release the self-loop of the port.
Step 5 Cause 4: other unknown reasons.

(1) Contact Huawei engineers to handle the fault.
----End

OptiX RTN 620
Related Information
None.
A.2.68 LASER_CLOSED
Description
The LASER_CLOSED is an alarm indicating that the laser is shut down. This alarm occurs when
the laser is shut down by using the NMS.
Attribute
Parameters
table.
Name Meaning
board.

The optical interface fails to carry services.
Possible Causes
Cause 1: The laser on the local NE is shut down by using the NMS.
Procedure
Step 1 Cause 1: The laser on the local NE is shut down by using the NMS.
(1) Determine the optical interface that reports the alarm based on the alarm parameter.
(2) Find out the cause of shutting down the laser and start up the laser as soon as possible.
----End
Related Information
None.

OptiX RTN 620
A.2.69 LASER_MOD_ERR_EX
Description
The LASER_MOD_ERR is an alarm indicating that the type of the pluggable optical module
on the board does not match the type of the optical interface.
Attribute

Parameters
table.
Name Meaning
board.

When the LASER_MOD_ERR_EX alarm occurs, the performance of the optical interface
degrades and serious degradation even causes service interruption.
Possible Causes
l Cause 1: The optical module installed at the optical interface does not match the rate of the
optical interface.
l Cause 2: The optical module is faulty.
Procedure
Step 1 Cause 1: The optical module installed at the optical interface does not match the rate of the
optical interface.
(1) Check whether the optical module installed at the optical interface matches the rate of the
optical interface. For details, see 7.4.2 Querying a Board Manufacture Information
Report.

OptiX RTN 620
If... Then...
The optical module does not match the Contact Huawei engineers to replace the
rate of the optical interface optical module with one that matches the
rate of the optical interface.
The optical module matches the rate of Go to Cause 2.
the optical interface
Step 2 Cause 2: The optical module is faulty.

(1) Contact Huawei engineers to replace the faulty optical module.
If... Then...
The alarm clears after the board is replaced End the alarm handling.
The alarm persists after the optical module is replaced Go to Cause 3.

(1) Replace the board that reports the alarm.
----End
Related Information
None.
A.2.70 LCAS_FOPR
Description
The LCAS_FOPR is an alarm indicating that the Link Capacity Adjustment Scheme (LCAS)
protocol in the transmit direction fails. This alarm occurs when the source end of the LCAS
module detects an abnormally that the LCAS negotiation is unavailable or incorrect.
Attribute
Parameters
table.
Name Meaning

OptiX RTN 620
Name Meaning
example, 0x00 0x01 indicate that the alarm is reported in
VCTRUNK 1.

The Ethernet service is not normal.
Possible Causes
l Cause 1: Configuration data of the LCAS protocol is incorrect.
l Cause 2: The link is faulty.
Procedure
Step 1 Cause 1: Configuration data of the LCAS protocol is incorrect.
(1) Check whether the LCAS enable state and the LCAS parameters are the same at both ends
of the link.
If... Then...
The LCAS enable state and the LCAS Properly enable the LCAS protocol at
parameters are not the same both ends.
The LCAS enable state and the LCAS Go to Cause 2.
parameters are the same
(2) Check whether the configurations of the local and opposite NEs are correct. That is, check
whether a VCG at one NE is connected to multiple VCGs at the opposite NE.
If... Then...
The configurations of the local and opposite NEs are Correct the configuration data.
incorrect
The configurations of the local and opposite NEs are Go to Cause 2.
correct
Step 2 Cause 2: The link is faulty.

(1) Check whether the link where the service travels has errors or becomes faulty.
If... Then...
The link is faulty Rectify the fault.
The link is not faulty Go to the next step.
(2) Restart the LCAS protocol at both ends. Then, check whether the alarm clears.
If... Then...

OptiX RTN 620
If... Then...
The alarm persists Replace the board that reports the alarm.
----End
Related Information
None.
A.2.71 LCAS_FOPT
Description
The LCAS_FOPT is an alarm indicating that the LCAS protocol in the transmit direction fails.
This alarm occurs 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

Parameters
table.
Name Meaning
VCTRUNK 1.

The Ethernet service is not normal.
Possible Causes
l Cause 1: Configuration data of the LCAS protocol is incorrect.
l Cause 2: The link is faulty.

OptiX RTN 620
Procedure
Step 1 Cause 1: Configuration data of the LCAS protocol is incorrect.
(1) Check whether the LCAS enable state and the LCAS parameters are the same at both ends
of the link.
If... Then...
The LCAS enable state and the LCAS Properly enable the LCAS protocol at
parameters are different both ends.
The LCAS enable state and the LCAS Go to Cause 2.
parameters are the same
(2) Check whether configurations of the local and opposite NEs are correct. That is, check
whether a VCG at one NE is connected to multiple VCGs at the opposite NE.
If... Then...
The configurations of the local and opposite NEs are Correct the configuration data.
incorrect
The configurations of the local and opposite NEs are Go to Cause 2.
correct
Step 2 Cause 2: The link is faulty.

(1) Check whether the link where the service travels has errors or become faulty.
If... Then...
The link is faulty Rectify the fault.
The link is not faulty Go to the next step.
(2) Restart the LCAS protocol at both ends. Then, check whether the alarm clears.
If... Then...
The alarm persists Replace the board that reports the alarm.
----End
Related Information
None.
A.2.72 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 occurs when 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 and is not zero.

OptiX RTN 620
Attribute
Minor Service alarm
Parameters
table.
Name Meaning
VCTRUNK 1.

The available Ethernet service bandwidth is smaller than the configured bandwidth.
Possible Causes
l Cause 1: The number of paths or timeslots that are configured for the VCTRUNK at the
remote site is different from that at the local site.
l Cause 2: Some paths in the transmit direction of the remote site are faulty.
l Cause 3: Some paths in the receive direction of the local site are faulty.
Procedure
Step 1 Cause 1: The number of paths or timeslots that are configured for the VCTRUNK at the remote
site is different from that at the local site.
(1) Check whether the VCTRUNKs at both ends are configured with the same number of
physical paths and timeslots.
If... Then...
The VCTRUNKs at both ends are Correct the configuration data. For details,
configured with a different number of see Dynamically Increasing/Decreasing the
physical paths and timeslots VCTRUNK Bandwidth.
The VCTRUNKs at both ends are Go to Cause 2.
configured with the same number of
physical paths and timeslots
Step 2 Cause 2: Some paths in the transmit direction of the remote site are faulty.
(1) Check whether any path alarm exists in the transmit direction of the remote site.

OptiX RTN 620
If... Then...
The alarm is reported Clear the alarm immediately.
No alarm is reported Go to Cause 3.
Step 3 Cause 3: Some paths in the receive direction of the local site are faulty.
----End
Related Information
None.
A.2.73 LCAS_PLCT
Description
The LCAS_PLCT is an alarm indicating that part of the LCAS bandwidth in the transmit
direction is lost. This alarm occurs when 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 and is not zero.
Attribute

Minor Service alarm
Parameters
table.
Name Meaning
VCTRUNK 1.

The available Ethernet service bandwidth is smaller than the configured bandwidth.

OptiX RTN 620
Possible Causes
l Cause 2: Some paths in the receive direction of the remote site are faulty.
l Cause 3: Some paths in the transmit direction of the local site are faulty.
Procedure
If... Then...
The sink and source VCTRUNKs are Correct the configuration data. For details,
bound with the different number of see Dynamically Increasing/Decreasing the
physical paths or bound with the VCTRUNK Bandwidth.
different timeslots
paths or bound with the same timeslots
Step 2 Cause 2: Some paths in the receive direction of the remote site are faulty.
(1) Check whether any path alarm exists in the receive direction of the remote site.
If... Then...
No alarm is reported Go to the next step.
Step 3 Cause 3: Some paths in the transmit direction of the local site are faulty.
----End
Related Information
None.
A.2.74 LCAS_TLCR
Description
The LCAS_TLCR is an alarm indicating that all the LCAS bandwidth in the receive direction
is lost. This alarm occurs when no path in the receive direction of the VCTRUNK with LCAS
enabled carries the overload but paths are configured to carry the overload.

OptiX RTN 620
Attribute
Major Service alarm
Parameters
table.
Name Meaning
VCTRUNK 1.

The Ethernet service is interrupted.
Possible Causes
l Cause 2: Some paths in the transmit direction of the remote site are faulty.
l Cause 3: Some paths in the receive direction of the local site are faulty.
Procedure
(1) Check whether the VCTRUNKs at both ends are configured with the same number of
physical paths and timeslots.
If... Then...
The VCTRUNKs at both ends are Correct the configuration data. For details,
configured with a different number of see Dynamically Increasing/Decreasing the
physical paths and timeslots VCTRUNK Bandwidth.
The VCTRUNKs at both ends are Go to Cause 2.
configured with the same number of
physical paths and timeslots
Step 2 Cause 2: Some paths in the transmit direction of the remote site are faulty.
(1) Check whether any path alarm exists in the transmit direction of the remote site.

OptiX RTN 620
If... Then...
No alarm is reported Go to Cause 3.
Step 3 Cause 3: Some paths in the receive direction of the local site are faulty.
----End
Related Information
None.
A.2.75 LCAS_TLCT
Description
The LCAS_TLCT is an alarm indicating that all the LCAS bandwidth in the transmit direction
is lost. This alarm occurs when no path in the transmit direction of the VCTRUNK with LCAS
enabled carries the overload but paths are configured to carry the overload.
Attribute

Major Service alarm
Parameters
table.
Name Meaning
VCTRUNK 1.

The Ethernet service is interrupted.

OptiX RTN 620
Possible Causes
l Cause 2: Some paths in the receive direction of the remote site are faulty.
l Cause 3: Some paths in the transmit direction of the local site are faulty.
Procedure
If... Then...
The sink and source VCTRUNKs are Correct the configuration data. For details,
bound with a different number of see Dynamically Increasing/Decreasing the
physical paths or bound with different VCTRUNK Bandwidth.
timeslots
paths or bound with the same timeslots
Step 2 Cause 2: Some paths in the receive direction of the remote site are faulty.
(1) Check whether any path alarm exists in the receive direction of the remote site.
If... Then...
No alarm is reported Go to the next step.
Step 3 Cause 3: Some paths in the transmit direction of the local site are faulty.
----End
Related Information
None.
A.2.76 LCS_LIMITED
Description
The LCS_LIMITED is an alarm indicating that the capacity of the microwave services
configured for an NE crosses the limit specified in the license file.

OptiX RTN 620
Attribute
Parameters
None.

Changing the capacity of the microwave services through an NE does not take effect.
Possible Causes
The capacity of the configured microwave services crosses the limit defined in the license file.
Procedure
Step 1 The capacity of the configured microwave services crosses the limit defined in the license file.
(1) Check whether the change in the capacity of the microwave services meet the requirement
of the NE.
If... Then...
The change in the capacity of the Go to the next step.
microwave services meet the
requirement of the NE
The change in the capacity of the Delete the unauthorized microwave cross-
microwave services does not meet the connection.
requirement of the NE
(2) Check whether the service capacity complies with the latest authorization agreement. For
details, see 7.8 Querying the License Capacity.
If... Then...
The service capacity complies with the Go to the next step.
latest authorization agreement
The service capacity does not comply with Contact Huawei engineers to load a new
the latest authorization agreement license file.
(3) Contact the local office of Huawei to apply for a license authorization of greater service
capacity.
----End
Related Information
The microwave service capacity of an NE is calculated based on the cross-connections on the
IF board.

OptiX RTN 620
A.2.77 LICENSE_LOST
Description
The LICENSE_LOST is an alarm indicating that the license file is not detected.
Attribute
Major alarm Equipment alarm
Parameters
None.

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.
Procedure
Step 1 Contact the technical support engineers of Huawei to reload the associated license file.
----End
Related Information
IF board.
A.2.78 LICENSE_ERR
Description
The LICENSE_ERR is an alarm indicating that license verification of an NE fails.
Attribute

OptiX RTN 620
Parameters
table.
Name Meaning
Parameter 1 Indicates the cause of verification failure.
l 0x01: Indicates that the license file is illegal.

l 0x02: Indicates that the license file is incorrect in file format.
l 0x03: Indicates that the characteristic segment (signature) verification fails.
l 0x04: Indicates that the equipment serial number specified in the characteristic
segment does not match the equipment.
l 0x05: Indicates that the trial usage of the characteristic segment expires.
l 0x06: Indicates that the characteristic segment is incorrect in format.
l 0x07: Indicates that the characteristic segment expires.

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
Cause 1: The verification of the license file fails.
Procedure
Step 1 Cause 1: The verification of the license file fails.
(1) Contact Huawei engineers to load a new license file.
----End
Related Information
IF board.
A.2.79 LINK_ERR
Description
The LINK_ERR is an alarm indicating that the data link fails.

OptiX RTN 620
Attribute
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
Parameter 2, Parameter 3 Indicate the ID of the path that reports the alarm. 0x00 0x01 indicate
that the alarm is reported by path 1.

The services carried over the path are interrupted.
Possible Causes
l Cause 1: The optical fiber connected to the Ethernet optical interface is faulty.
l Cause 2: The working modes of the ports at both ends are different.
l Cause 3: The equipment at the local end or the remote end is faulty.
Procedure
Step 1 Cause 1: The optical fiber connected to the Ethernet optical interface is faulty.
(1) Check whether the optical fiber connected to the Ethernet optical interface is faulty.
If... Then...
The optical fiber connected to the Ethernet optical Replace the optical fiber.
interface is faulty
The optical fiber connected to the Ethernet optical Go to Cause 2.
interface is not faulty
Step 2 Cause 2: The working modes of the ports at both ends are different.
(1) Check whether the working modes of the ports at both ends are different.
If... Then...
The working modes of the ports at both Set the working modes of the ports to the
ends are different same.

OptiX RTN 620
If... Then...
The working modes of the ports at both Go to the next step.
ends are the same
Step 3 Cause 3: The equipment at the local end or the remote end is faulty.
(1) Use an optical fiber to perform a loopback at the port that reports the alarm. For details,
see 7.1 Hardware Loopback.
If... Then...
The alarm clears 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.80 LOOP_ALM
Description
The LOOP_ALM is an alarm indicating that a loopback event occurs.
Attribute
Parameters
table.
Name Meaning

OptiX RTN 620
Name Meaning
Parameter 4 Indicates the type of loopback.
l 0x00: Indicates optical/electrical port inloop.
l 0x01: Indicates optical/electrical port outloop.
l 0x02: Indicates path inloop.
l 0x03: Indicates path outloop.
l 0x04: Indicates loopback on the user side.
l 0x05: Indicates loopback on the combination wave side.
l 0x06: Indicates SPI inloop.
l 0x07: Indicates SPI outloop.
l 0x08: Indicates ATM layer inloop.
l 0x09: Indicates ATM layer outloop.
l 0x0A: Indicates PHY layer inloop.
l 0x0B: Indicates PHY layer outloop.
l 0x0C: Indicates MAC layer inloop.
l 0x0D: Indicates MAC layer outloop.
l 0x0E: Indicates VC-4 timeslot inloop.
l 0x0F: Indicates VC-4 timeslot outloop.
l 0x10: Indicates VC-3 timeslot inloop.
l 0x11: Indicates VC-3 timeslot outloop.
l 0x12: Indicates VC-12 timeslot inloop.
l 0x13: Indicates VC-12 timeslot outloop.
l 0x14: Indicates IF outloop.
l 0x15: Indicates IF inloop.
l 0x16: Indicates RF inloop.
l 0xFF: Indicates any of the preceding loopback modes.

The loopback port or path fails to transmit services.
Possible Causes
Loopback is performed at the local site.
Procedure
Step 1 Cause: Loopback is performed at the local site.
(1) Determine the type of loopback based on the alarm parameters.
(2) Find out the cause of loopback, and set the loopback status of the port that reports the alarm
to Non-Loopback.

OptiX RTN 620
For more information about the loopback operation, see 7.5 Software loopback.
----End
Related Information
None.
A.2.81 LP_CROSSTR
Description
The LP_CROSSTR is an alarm indicating that a lower order path performance indicator crosses
the related threshold. This alarm occurs when a board detects that a lower order path bit error
performance indicator crosses the preset threshold.
Attribute

Minor Service alarm
Parameters
table.
Name Meaning

The services contain a large amount of bit errors and the services may be interrupted.
Possible Causes
Lower order path bit error performance events cross the preset threshold.

OptiX RTN 620
Procedure
Step 1 Cause: The lower order path error crosses the preset threshold.
(1) Check the threshold crossing records to find out the performance event that the lower order
path error crosses the preset threshold. For details, see 7.3.8 Browsing the Performance
Event Threshold-Crossing Records.
Step 2 Handle the threshold-crossing performance event.
----End
Related Information
None.
A.2.82 LP_R_FIFO
Description
The LP_R_FIFO is an alarm indicating that the FIFO overflows on the reception side of the
lower order path.
Attribute

Parameters
None.

Bit errors occur in the services.
Possible Causes
l Cause 1: The clocks on both sites are not synchronous.
Procedure
Step 1 Cause 1: The clocks on both sites are not synchronous.
(1) Query whether a TU pointer adaptation performance event is reported at both ends. For
details, see 7.3.6 Browsing Current Performance Events.

OptiX RTN 620
If... Then...
A TU pointer adaptation performance Handle the performance event. For details,
event is reported see C.2.3 TUPJCHIGH, TUPJCLOW,
and TUPJCNEW.
A TU pointer adaptation performance Go to Cause 2.
event is not reported

----End
Related Information
None.
A.2.83 LP_RDI
Description
The LP_RDI is an alarm indicating a remote defect in the lower order path. This alarm occurs
when the board detects that bit 8 of byte V5 is 1.
Attribute

Parameters
table.
Name Meaning

is interrupted.

OptiX RTN 620
Possible Causes
lower order path remote receive failure.
Procedure
(1) Handle the alarm of the lower order path at the remote site.
----End
Related Information
None.
A.2.84 LP_RDI_VC12
Description
The LP_RDI_VC12 is an alarm indicating that data reception fails at the remote end of VC-12
path. This alarm occurs when the board detects that bit 8 of byte V5 is 1.
Attribute
Parameters
table.
Name Meaning
Parameter 2, Parameter 3 Indicate the ID of the VC-12 path that reports the alarm. For
example, 0x00 0x01 indicate that the alarm is reported by VC-12
path 1.

is interrupted.

OptiX RTN 620
Possible Causes
Cause 1: The local site receives a message from the remote site, and the message says that data
reception fails at the remote end of a lower order path.
Procedure
Step 1 Cause 1: The local site receives a message from the remote site, and the message says that data
reception fails at the remote end of a lower order path.
----End
Related Information
None.
A.2.85 LP_RDI_VC3
Description
The LP_RDI_VC3 is an alarm indicating that data reception at the remote end of a VC-3 path
fails. This alarm occurs when the board detects that bit 5 of byte G1 is 1.
Attribute

Parameters
table.
Name Meaning

is interrupted.

OptiX RTN 620
Possible Causes
The local site receives a message from the remote site, and the message says that data reception
fails at the remote end of a lower order path.
Procedure
Step 1 Cause: The local site detects the message that is returned by the opposite site and indicates the
----End
Related Information
None.
A.2.86 LP_REI
Description
The LP_REI is an alarm indicating that there are bit errors over the lower order path of the remote
site. This alarm occurs when the board detects that bit 3 of byte V5 is 1.
Attribute

Parameters
table.
Name Meaning

The local site is not affected, but there are bit errors in the received signals of the remote site.

OptiX RTN 620
Possible Causes
Cause: The local site receives a message from the remote site, and the message says that there
are bit errors in the lower order path of the remote site.
Procedure
Step 1 Cause: The local site receives a message from the remote site, and the message says that there
are bit errors in the lower order path of the remote site.
(1) Handle the LPBBE performance event of the remote site.
----End
Related Information
None.
A.2.87 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 occurs when a board detects that bit 3 of byte V5 is 1.
Attribute

Parameters
table.
Name Meaning
path 1.

Bit errors exist in the service in the receive direction of the remote site.

OptiX RTN 620
Possible Causes
Cause: The local site receives a message from the remote site, and the message says that there
are bit errors in the lower order path.
Procedure
Step 1 Cause: The local site receives a message from the remote site, and the message says that there
are bit errors in the lower order path.
(1) Handle the LPBBE performance event of the remote site.
----End
Related Information
None.
A.2.88 LP_REI_VC3
Description
The LP_REI_VC3 is an alarm indicating that there are bit errors at the remote end of a VC-3
path. This alarm occurs when a board detects that any one of bits 1-4 of byte G1 is 1.
Attribute

Parameters
table.
Name Meaning

Bit errors exist in the service in the receive direction of the remote site.

OptiX RTN 620
Possible Causes
Cause 1: The local site receives a message from the remote site, and the message says that there
are bit errors at the remote end of a lower order path.
Procedure
Step 1 Cause 1: The local site receives a message from the remote site, and the message says that there
are bit errors at the remote end of a lower order path.
(1) Handle the VC3BBE performance event of the remote site.
----End
Related Information
None.
A.2.89 LP_RFI
Description
The LP_RFI is an alarm indicating that the remote end of the lower order path fails. This alarm
occurs when a board detects that bit 4 of byte V5 is 1.
Attribute

Parameters
table.
Name Meaning

The local site is not affected. The lower order path at the remote site, however, cannot bear
services.

OptiX RTN 620
Possible Causes
Procedure
----End
Related Information
None.
A.2.90 LP_SIZE_ERR
Description
The LP_SIZE_ERR is an alarm indicating that the size of the TU pointer is incorrect.
Attribute

Minor Service alarm
Parameters
None.

The services carried by the alarmed board are interrupted.
Possible Causes
l Cause 1: The configuration of the mapping structure at the local end or remote end is
incorrect.
l Cause 2: The tributary board is faulty.
Procedure
Step 1 Cause 1: The configuration of the mapping structure at the local end or remote end is incorrect.
(1) Check whether the types of the add/drop services configured on the board are the same
with the service types supported by the board. For details, see Querying TDM Services.

OptiX RTN 620
If... Then...
The service types are different Change the configuration data.
The service types are the same Go to Cause 2.
Step 2 Cause 2: The tributary board is faulty.

----End
Related Information
None.
A.2.91 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 when the board detects a signal label mismatch between the V5
bytes.
Attribute
Parameters
table.
Name Meaning

The services in the lower order path are unavailable.
Possible Causes
Cause 1: The signal label contained in the V5 byte that is received by the local site does not
match the signal label contained in the V5 byte that is transmitted by the remote site.

OptiX RTN 620
Procedure
Step 1 Cause 1: The signal label contained in the V5 byte that is received by the local site does not
match the signal label contained in the V5 byte that is transmitted by the remote site.
(1) Modify the signal label contained in the V5 byte that is to be received by the local site or
is to be transmitted by the remote site. Ensure that the signal labels at both ends match each
other. For details, see Configuring VC-12 POHs.
----End
Related Information
None.
A.2.92 LP_SLM_VC12
Description
The LP_SLM_VC12 is an alarm indicating that a mismatched signal label is detected in the
VC-12 path. This alarm occurs when the board detects a signal label mismatch between the V5
bytes.
Attribute
Parameters
table.
Name Meaning
path 1.

The service in this lower order path is unavailable.
Possible Causes
The signal label contained in the V5 byte that is received by the local site does not match the
signal label contained in the V5 byte that is transmitted by the remote site.

OptiX RTN 620
Procedure
Step 1 Cause: The signal label contained in the V5 byte that is received by the local site does not match
the signal label contained in the V5 byte that is transmitted by the remote site.
(1) Modify the signal label contained in the V5 byte that is to be received by the local site or
that is to be transmitted by the remote site. Ensure that the signal labels at both ends match
each other. For details, see Configuring VC-12 POHs.
----End
Related Information
None.
A.2.93 LP_SLM_VC3
Description
The LP_SLM_VC3 is an alarm indicating that a mismatched signal label is detected in the VC-3
path. This alarm occurs when the board detects a signal label mismatch between the C2 bytes.
Attribute
Parameters
table.
Name Meaning

The services in the lower order path are unavailable.
Possible Causes
Cause 1: The signal label contained in the C2 byte that is received by the local site does not
match the signal label contained in the C2 byte that is transmitted by the remote site.

OptiX RTN 620
Procedure
Step 1 Cause 1: The signal label contained in the C2 byte that is received by the local site does not
match the signal label contained in the C2 byte that is transmitted by the remote site.
(1) Modify the signal label contained in the C2 byte that is to be received by the local site or
that is to be transmitted by the remote site. Ensure that the signal labels at both ends match
each other. For details, see Configuring VC-3 POHs.
----End
Related Information
None.
A.2.94 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.
Attribute
Parameters
table.
Name Meaning
path 1.

Bit errors occur in the services.
Possible Causes
l Cause 1: The frequency offset of the input signal is very large.

OptiX RTN 620
Procedure
Step 1 Cause 1: The frequency offset of the input signal is very large.
(1) Use an SDH analyzer to check whether the frequency offset of the input signal is within
50 ppm.
If... Then...
The frequency offset is very large Troubleshoot the remote site.
The frequency offset is within 50 ppm Go to Cause 2.

----End
Related Information
None.
A.2.95 LP_TIM
Description
The LP_TIM is an alarm indicating that a mismatched trace identifier is detected in the lower
order path. This alarm occurs when the board detects a mismatch between the J2 bytes at both
ends.
Attribute
Parameters
table.
Name Meaning

None.

OptiX RTN 620
Possible Causes
l Cause 1: The J2 byte to be received by the local site does not match the J2 byte to be
transmitted by the remote site.
l Cause 2: The data configuration at the intermediate nodes is incorrect.
Procedure
Step 1 Cause 1: The J2 byte to be received by the local site does not match the J2 byte to be transmitted
by the remote site.
(1) Set the byte mode of the J2 byte to be received by the local site to the disabled mode.
Alternatively, set the J2 byte to be received by the local site to match the J2 byte to be
transmitted by the remote site. For details, see Configuring VC-12 POHs.
Step 2 Cause 2: The data configuration at the intermediate nodes is incorrect.

(1) Check whether the cross-connections of the intermediate nodes where the service travels
are configured correctly. If not, re-configure the cross-connections. For details, see
Querying TDM Services.
----End
Related Information
None.
A.2.96 LP_TIM_VC12
Description
The LP_TIM_VC12 is an alarm indicating a mismatched trace identifier is detected in the VC-12
path. This alarm occurs when the board detects a mismatch between the J2 bytes at both ends.
Attribute

Parameters
table.
Name Meaning

OptiX RTN 620
Name Meaning
path 1 of the corresponding board.

None.
Possible Causes
l Cause 1: The J2 byte to be received by the local site does not match the J2 byte to be
transmitted by the remote site.
Procedure
Step 1 Cause 1: The J2 byte to be received by the local site does not match the J2 byte to be transmitted
by the remote site.
----End
Related Information
None.
A.2.97 LP_TIM_VC3
Description
The LP_TIM_VC3 is an alarm indicating a mismatched trace identifier is detected in the VC-3
path. This alarm occurs when the board detects the J1 byte mismatch.
Attribute
Parameters

OptiX RTN 620

table.
Name Meaning
0x00 0x01 indicate that the alarm is reported by VC-3 path 1 of the

None.
Possible Causes
l Cause 1: The receivable J1 byte at the local site does not match the J1 byte transmitted at
the opposite site.
Procedure
Step 1 Cause 1: The receivable J1 byte at the local site does not match the J1 byte transmitted at the
opposite site.

----End
Related Information
None.
A.2.98 LP_UNEQ
Description
The LP_UNEQ is an alarm indicating that the lower order path is unequipped. This alarm occurs
when the board detects that the V5 byte signal label is 0.

OptiX RTN 620
Attribute
Parameters
table.
Name Meaning

The service in the path is unavailable. If the service is configured with protection, the protection
switching is also triggered.
Possible Causes
The data configuration is incorrect.
l Cause 1: The tributary path at the local site is configured with services, but the tributary
path at the remote site is not configured with services.
l Cause 2: The cross-connection configuration at the intermediate nodes is incorrect.
Procedure
Step 1 Cause 1: The tributary path at the local site is configured with services, but the tributary path at
the remote site is not configured with services.
(1) Check whether the tributary path at the remote site is configured with services. For details,
see Querying TDM Services.
If... Then...
The tributary path at the remote site is not configured with Configure services.
services
The tributary path at the remote site is configured with services Go to Cause 2.
Step 2 Cause 2: The cross-connection configuration at the intermediate nodes is incorrect.

(1) Check whether the cross-connection configuration at the intermediate nodes is correct. If
not, re-configure the cross-connections. For details, see Querying TDM Services.
----End

OptiX RTN 620
Related Information
None.
A.2.99 LP_UNEQ_VC12
Description
The LP_UNEQ_VC12 is an alarm indicating that the VC-12 path is unequipped. This alarm
occurs when the board detects that the V5 byte signal label is 0.
Attribute
Parameters
table.
Name Meaning

Possible Causes
Procedure

OptiX RTN 620
If... Then...
services

----End
Related Information
None.
A.2.100 LP_UNEQ_VC3
Description
The LP_UNEQ_VC3 is an alarm indicating that the VC-3 path is unequipped. This alarm occurs
when the board detects that the C2 byte signal label is 0.
Attribute

Parameters
table.
Name Meaning
0x00 0x01 indicate that the alarm is reported by VC-3 path 1 of the


OptiX RTN 620
Possible Causes
Procedure
If... Then...
services

----End
Related Information
None.
A.2.101 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 with each other.
Attribute
Parameters
table.

OptiX RTN 620
Name Meaning

The system performs protection switching in single-ended mode.
Possible Causes
Cause 1: The linear MSP is configured incorrectly.
The LPS_UNI_BI_M alarm is generated only when the following conditions are met:
l The switching modes (single-ended or dual-ended) at the local and remote sites are
different.
l The last three bits of the K2 byte are set to the indicated mode.
l The type of the protocol is set to a restructure protocol.
Procedure
Step 1 Cause 1: The linear MSP is configured incorrectly.
(1) Change the MSP switching modes at both ends, and ensure that they are the same. For
details, see Querying the Status of Linear MSP.
----End
Related Information
None.
A.2.102 LPT_INEFFECT
Description
The LPT_INEFFECT is an alarm indicating that the LPT function fails. This alarm occurs when
the user configures the LPT function but the board does not support the LPT function.
Attribute
Parameters

OptiX RTN 620
table.
Name Meaning
Parameter 2, Parameter 3 Indicate the port ID.

The values are always 0x00 0x01.

The services are not affected. If the board hardware is of a very early version, the board software
automatically stops the state machine of the LPT protocol, but reserves the LPT configuration.
Possible Causes
Cause 1: The board hardware is of a very early version, and the user configures the LPT function.
Procedure
Step 1 Cause 1: The board hardware is of a very early version, and the user configures the LPT function.
(1) Check whether the LPT function is required.
If... Then...
The LPT function is required Replace the board with a board of a proper version.
For details, see 6.6 Replacing the Ethernet
Service Processing Board.
The LPT function is not required Delete the configuration of the LPT function. For
details, see Configuring LPT for Point-to-Point
Services.
----End
Related Information
None.
A.2.103 LPT_RFI
Description
The LPT_RFI is an alarm indicating that the link state pass-through function fails at the remote
end. This alarm occurs when the link path through (LPT) function detects the failure of the
remote port or the LPT service network.

OptiX RTN 620
Attribute
Parameters
table.
Name Meaning
Parameter 2, Parameter 3 Indicate the port ID.

The values are always 0x00 0x01.

During the data transmission, the link is unavailable and the services are interrupted when the
LPT function detects the failure of the remote port or the service network. In addition, enabling
the link backup is triggered. If the backup link is available, the service can be restored on the
backup link.
Possible Causes
l Cause 1: The remote port fails. For example, there are alarms such as ETH_LOS,
LINK_ERR, LSR_NO_FITED, or the remote port is disabled.
l Cause 2: The LPT service network is faulty.
– The communication link is interrupted.
– There are the bit error threshold-crossing alarms BIP_EXC and B3_EXC_VC3.
– There are alarms such as TU_LOP, TU_AIS, VCAT_LOA, VCAT_LOM_VC12,
VCAT_LOM_VC3, LP_UNEQ_VC12, and LP_UNEQ_VC3.
Procedure
Step 1 Check the alarm on the NMS, determine the board that reports the alarm, and then determine
the ID of the port on the board according to Parameter 1.
Step 2 Cause 1: The remote port is faulty.

(1) Check whether the corresponding opposite ports are enabled according to the ports
indicated by the parameter.

OptiX RTN 620
If... Then...
The opposite port is not enabled Enable the opposite port.
The opposite port is enabled Go to the next step.
(2) Check whether any link fault alarm occurs on the line board.
If... Then...
Any link fault alarm occurs Handle the link fault alarms first, especially the R_LOS
and MW_LOF alarms.
No link fault alarm occurs Go to Cause 2.
Step 3 Cause 2: The LPT service network is faulty.

(1) Check whether the following alarms occur on the Ethernet boards of the MEPs at both ends.
Then, handle the alarms.
l ETH_LOS
l LINK_ERR
l LSR_NO_FITED
l BIP_EXC and B3_EXC_VC3
l TU_LOP, TU_AIS, VCAT_LOA, VCAT_LOM_VC12, VCAT_LOM_VC3,
LP_UNEQ_VC12, and LP_UNEQ_VC3
----End
Related Information
None.
A.2.104 LSR_NO_FITED
Description
The LSR_NO_FITED is an alarm indicating that the laser is not installed.
Attribute
Parameters
table.

OptiX RTN 620
Name Meaning
board.

The optical interface fails to carry services.
Possible Causes
Cause 1: The laser of the local site is not installed.
Procedure
Step 1 Cause 1: The laser of the local site is not installed.
(2) Find out why the laser is not installed, and contact Huawei engineers for the installation.
----End
Related Information
None.
A.2.105 LSR_WILL_DIE
Description
The LSR_WILL_DIE is an alarm indicating that the life of the laser is close to the end.
Attribute

Parameters
table.

OptiX RTN 620
Name Meaning
board.

The SFP optical module may not function reliably, and thus the services may be interrupted.
Possible Causes
The laser is aged.
Procedure
Step 1 Cause: The laser is aged.
(2) Contact Huawei engineers to replace the faulty SFP optical module with a new one of the
same type.
----End
Related Information
None.
A.2.106 LTI
Description
The LTI is an alarm indicating that the synchronization sources are lost. This alarm occurs when
all the synchronization sources for the NE are lost.
Attribute

Parameters
table.

OptiX RTN 620
Name Meaning
Parameter 1 l 0x01: Indicates that all the synchronization sources of the system clock are
lost.
l 0x02: Indicates that all the synchronization sources of the 2 MHz phase-locked
source are lost.

The clock enters the free-run mode and loses synchronization with other NE clocks.
Possible Causes
l Cause 1: The clock configuration is incorrect.
l Cause 2: All the clock sources in the clock source priority table fail.
Procedure
Step 1 Cause 1: The clock configuration is incorrect.
(1) Check whether the data in the clock source priority table meets the network planning
requirement. For details, see Querying the Clock Synchronization Status.
If... Then...
The configuration is incorrect Correct the configurations.
The configuration is correct Go to Cause 2.
Step 2 Cause 2: All the clock sources in the clock source priority table fail.
(1) Troubleshoot the synchronization sources based on the clock source priority table.
If... Then...
The synchronization source is the Handle the EXT_SYNC_LOS alarm.
external clock
The synchronization source is the line Handle the alarm that occurs on the line
clock board.
The synchronization source is the IF Handle the alarm that occurs on the IF board.
clock
The synchronization source is the Handle the alarm that occurs on the tributary
tributary clock board.
----End
Related Information
None.
A.2.107 MOD_TYPE_MISMATCH

OptiX RTN 620
Description
The MOD_TYPE_MISMATCH is an alarm indicating that a mismatched port module is
detected.
Attribute

Critical 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 corresponding board.

The service on the port is interrupted.
Possible Causes
The type specified by the customer for the SFP module is different from the actual module type.
Procedure
Step 1 Cause: The type specified by the customer for the SFP module is different from the actual module
type.
(1) Determine the port that reports the alarm based on the alarm parameter.
(2) Check whether the configured type of the SFP module is the same as the type of the actual
module.
If... Then...
The configured type of the SFP module is Contact Huawei engineers to install an SFP
the same as the type of the actual module module of the correct type.
The configured type of the SFP module is Change the configured type of the SFP
different from the type of the actual module.
module
----End

OptiX RTN 620
Related Information
None.
A.2.108 MS_AIS
Description
The MS_AIS is an alarm indicating multiplex section alarms. This alarm occurs when a board
detects that bits 6-8 of the K2 byte in three consecutive frames are 111.
Attribute

Parameters
table.
Name Meaning

The service on the line port is interrupted. If the service is configured with protection, the
protection switching is also triggered.
Possible Causes
Procedure
(1) Replace the line board at the opposite site based on the type of the board that reports the
alarm.

OptiX RTN 620
If... Then...
The line board reports the alarm Replace the optical-interface line board at the
opposite site.
The line board reports the alarm Replace the electrical-interface line board at the
opposite site.
The IF board reports the alarm Replace the IF board at the opposite site.
(2) Replace the board and then check whether the alarm clears.
If... Then...
The alarm clears after the board is replaced End the fault handling.
The alarm persists after the board is replaced Go to the next step.
(3) Replace the PXC board at the opposite site.
If... Then...
The alarm clears after the board is replaced End the fault handling.
The alarm persists after the board is replaced Go to Cause 2.

(1) Replace the board that reports the alarm on the local end.
If... Then...
The SDH optical-interface line board Replace the SDH optical-interface line
reports the alarm board.
The SDH electrical-interface line board Replace the SDH electrical-interface line
reports the alarm board.
The IF board reports the alarm Replace the IF board that reports the
alarm.
----End
Related Information
None.
A.2.109 MS_CROSSTR
Description
The MS_CROSSTR alarm indicates that a performance indicator of the multiplex section crosses
the threshold. This alarm occurs when a board detects that the multiplex section bit error
performance indicator crosses the preset threshold.

OptiX RTN 620
Attribute
Minor Service alarm
Parameters
table.
Name Meaning
ID of the performance event.

A large number of errors occur in the service, and the service may be interrupted.
Possible Causes
Cause 1: A multiplex section bit error performance indicator crosses the preset threshold.
Procedure
Step 1 Cause 1: A multiplex section bit error performance indicator crosses the preset threshold.
(1) Check the threshold crossing records of multiplex section bit error performance events to
find out the performance event that crosses the preset threshold. For details, see 7.3.8
Browsing the Performance Event Threshold-Crossing Records.
----End
Related Information
None.
A.2.110 MS_RDI

OptiX RTN 620
Description
The MS_RDI is an alarm indicating that data reception fails at the remote end of the multiplex
section. This alarm occurs when a board detects that bits 6-8 of the K2 byte are 110.
Attribute

Parameters
table.
Name Meaning

is interrupted.
Possible Causes
The local site receives a message from the opposite site, and the message indicates that data
reception at the remote end of the multiplex section fails.
Procedure
Step 1 The local site receives a message from the opposite site, and the message indicates that data
reception at the remote end of the multiplex section fails.
(1) Rectify the fault that occurs on the regenerator section and the multiplex section at the
opposite site.
The possible alarms are as follows:
l MS_AIS
l R_LOS
l R_LOF
l B2_EXC

OptiX RTN 620
l B2_SD
----End
Related Information
None.
A.2.111 MS_REI
Description
The MS_REI is an alarm indicating that bit errors occur on the remote end of the multiplex
section. This alarm occurs when the board detects that the M1 byte is not zero.
Attribute
Warning Service alarm
Parameters
table.
Name Meaning

has errors.
Possible Causes
Cause 1: The local site receives a message from the opposite site, and the message indicates that
bit errors occur on the remote end of the multiplex section.
Procedure
Step 1 Cause 1: The local site receives a message from the opposite site, and the message indicates that
bit errors occur on the remote end of the multiplex section.

OptiX RTN 620
(1) Handle the MS_BBE performance event on the port of the opposite site.
----End
Related Information
None.
A.2.112 MSAD_CROSSTR
Description
The MSAD_CROSSTR alarm indicates that the adaptation performance indicator of the
multiplex section crosses the threshold. This alarm occurs when a board detects that an AU
pointer adaptation performance indicator crosses the preset threshold.
Attribute
Minor Service alarm
Parameters
table.
Name Meaning
– 0x2a: AUPJCHIGH
– 0x2b: AUPJCLOW
– 0x2c: AUPJCNEW
– 0xff: not used

Bit errors may occur in the service.

OptiX RTN 620
Possible Causes
An AU pointer adaptation performance indicator crosses the preset threshold.
Procedure
Step 1 Cause: An AU pointer adaptation performance indicator crosses the preset threshold.
(1) Check the threshold crossing records of the AU pointer adaptation performance events to
find out the performance event that crosses the preset threshold. For details, see 7.3.8
Browsing the Performance Event Threshold-Crossing Records.
----End
Related Information
None.
A.2.113 MSSW_DIFFERENT
Description
The MSSW_DIFFERENT is an alarm indicating that the master and slave software areas
mismatches with each other. This alarm occurs when the NE detects that the first software system
and the second software system of the system control, cross-connect, and timing board mismatch
with each other.
Attribute

Parameters
table.
Name Meaning
Parameter 1 Indicates the location of the file.
l 0x01: Indicates the files in the flash memory
l 0x02: Indicates the software that is currently running

OptiX RTN 620
Name Meaning
Parameter 2, Parameter 3 Indicate the IDs of the inconsistent files on the system control
board.
l 0x01: FPGA of the system control board in ofs1
l 0x02: FPGA of the system control board in ofs2
l 0x03: ofs1/hwx/nesoft.hwx
l 0x04: ofs2/hwx/nesoft.hwx
l 0x05: ofs1/hwx/ne.ini
l 0x06: ofs2/hwx/ne.ini
l 0x07: ofs1/hwx/ocp.ini
l 0x08: ofs2/hwx/ocp.ini
l 0x09: ofs1/fpga/if1_002.pga
l 0x0a: ofs2/fpga/if1_002.pga
l 0x0b: ofs1/fpga/if1_250.pga
l 0x0c: ofs2/fpga/if1_250.pga
l 0x0d: ofs1/fpga/sl1d.pga
l 0x0e: ofs2/fpga/sl1d.pga
l 0x0f: ofs1/fpga/sl91ifu2.pga
l 0x10: ofs2/fpga/sl91ifu2.pga
l 0x11: ofs1/fpga/sl91ifx2.pga
l 0x12: ofs2/fpga/sl91ifx2.pga
l 0x13: ofs1/fpga/sl91aux.pga
l 0x14: ofs2/fpga/sl91aux.pga
l 0x15: ofs1/hwx/lusoft.hwx
l 0x16: ofs2/hwx/lusoft.hwx
l 0x17: ofs1/hwx/lusoft.ini
l 0x18: ofs2/hwx/lusoft.ini
l 0x19: ofs1/fpga/sl91em6t.pga
l 0x1a: ofs2/fpga/sl91em6t.pga
l 0x1b: ofs1/fpga/pvg610.pga
l 0x1c: ofs2/fpga/pvg610.pga
l 0x1d: ofs1/fpga/pvg610x.pga
l 0x1e: ofs2/fpga/pvg610x.pga

OptiX RTN 620
Name Meaning
Parameter 4, Parameter 5 Indicate the cause of the alarm.
l 0x04: The file versions in the master and slave areas of a single
system control board are inconsistent.
l 0x08: The file versions in the active and standby system control
boards are inconsistent, or that the files in the corresponding
directories of the active and standby system control boards have
different names.
l 0x0c: The file versions in the master and slave areas of a single
system control board are inconsistent and the file versions on the
active and standby system control boards are also inconsistent.

If the currently running software is lost, the backup software fails to take over. If no NE software
exists in the flash memory, the system is unable to restart after power-off or reset.
Possible Causes
Cause 1: An exception occurs during the software loading.
Procedure
Step 1 Cause 1: An exception occurs during the software loading.
(1) Contact Huawei engineers to re-load the software.
----End
Related Information
None.
A.2.114 MULTI_RPL_OWNER
Description
The MULTI_RPL_OWNER is an alarm indicating that the ring network contains several
RPL_OWNER nodes.
Attribute
Parameters

OptiX RTN 620

table.
Name Meaning
Parameter 1 Indicates the port ID.
Parameter 2, Parameter 3 Indicate the ID of the ERPS instance.

The ERPS protection fails.
Possible Causes
The associated data is configured incorrectly.
Procedure
Step 1 Cause: The associated data is configured incorrectly.
(1) Reconfigure the ERPS protection. For details, see Creating ERPS Instances.
----End
Related Information
None.
A.2.115 MW_BER_EXC
Description
The MW_BER_EXC is an alarm indicating that there are excessive bit errors on the radio link.
This alarm occurs when the bit errors on the radio link exceed the specified threshold (10-3 by
default).
Attribute
Minor Service alarm
Parameters
table.

OptiX RTN 620
Name Meaning

Possible Causes
l Cause 1: Signal attenuation on the radio link is too heavy.
Procedure
Step 1 Cause 1: Signal attenuation on the radio link is too heavy.
(1) Check whether the MW_FEC_UNCOR alarm is reported. If so, clear the alarm.

(1) Replace the IF board at the local site.

(1) Replace the IF board at the opposite site.
----End
Related Information
None.
A.2.116 MW_BER_SD
Description
The MW_BER_SD is an alarm indicating that signal deteriorates on the radio link. This alarm
occurs when the bit errors on the radio link exceed the specified threshold (10-6 by default) but
does not reach the MW_BER_EXC alarm threshold (10-3 by default).
Attribute
Minor Service alarm

OptiX RTN 620
Parameters
table.
Name Meaning

The service performance on the port deteriorates. If the equipment is configured with 1+1 FD/
SD protection, HSM channel switching may be triggered.
Possible Causes
l Cause 1: Signal attenuation on the radio link is too heavy.
Procedure
Step 1 Cause 1: Signal attenuation on the radio link is too heavy.
(1) Check whether the MW_FEC_UNCOR alarm is reported. If so, clear the alarm.

(1) Replace the IF board at the local site.

(1) Replace the IF board at the opposite site.
----End
Related Information
None.
A.2.117 MW_FEC_UNCOR
Description
The MW_FEC_UNCOR alarm indicates that microwave frames forward error correction (FEC)
encoding cannot be corrected.

OptiX RTN 620
Attribute
Minor Service alarm
Parameters
table.
Name Meaning

Bit errors occur in the services. If the equipment is configured with 1+1 FD/SD protection, HSM
channel protection switching may be triggered.
Possible Causes
l Cause 1: The receive power of the ODU is abnormal.
l Cause 4: An interference event occurs.
Procedure
Step 1 Cause 1: The receive power of the ODU is abnormal.
(1) Check whether the receive power of the ODU at the local site is normal. If yes, determine
the abnormality and take proper measures. For details, see Querying History Transmit
Power and Receive Power.

OptiX RTN 620
If... Then...
The RSL is lower than the receiver Follow the steps:

sensitivity
1. Check the installation of the antenna to ensure
that 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 the
incorrect polarization direction.
4. Check whether the antenna gain at both the
transmit and receive ends meets the
specifications. Replace the antennas that do
not meet the requirement.
5. Check whether any mountain or building
obstacle exists in the transmit direction.
If yes, contact the network planning
department for proper modification of the
planning design, hence preventing the block
of the mountain or building obstacle.
The RSL is higher than the specified RSL Slow up fading occurs. Follow the steps:
of the network. The offset value is tens of
decibles. The duration is from tens of 1. Check whether any co-channel interference
seconds to several hours occurs.
a. Mute the ODU at the opposite end. For
details, seeConfiguring the IF/ODU
Information of a Radio Link.
b. Check the RSL at the local end. For details,
seeConfiguring the IF/ODU Information of
a Radio Link. If the RSL exceeds -90 dBm,
you can infer that there is co-channel
interference that may affect the long-term
availability and errored-second
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 minimize the interference.

OptiX RTN 620
If... Then...
The RSL is lower than the specified RSL Slow down fading occurs. Generally, the radio
of the network. The offset value is tens of link may be faulty in both directions, because
decibles. The duration is from tens of slow fading is imposed by the transmission path.
seconds to several hours Contact the network planning department to
make the following changes:
l Increase the installation height of the antenna.
If the RSL is lower than or higher than Fast fading occurs. Contact the network planning
the specified RSL of the network and if department to make the following changes:
the duration is from several milliseconds
l Adjust the position of the antenna to block the
to tens of seconds
reflected wave or make the reflection point fall
on the ground that has a small reflection
coefficient, thus reducing the multipath
fading.
l Adjust the RF configuration to make the links
in the 1+1 SD configuration.
l If the links are in the 1+1 SD configuration,
adjust the height offset between two antennas
to make the receive power of one antenna
much stronger than the receive power of the
other antenna.
l Increase the fading margin.
Locate the fault by looping back the opposite site and excluding the position one by one. Follow
the steps:
(1) Perform an inloop on the IF port at the opposite end. For details, see 7.5.4 Setting Loopback
for the IF Board. Check whether the fault at the opposite end is rectified after the loopback.
If... Then...
The alarm persists Replace the IF board.
The alarm clears Go to the next step.
(2) Check whether the cable connector workmanship meets the requirement. If any cable
connector does not meet the requirement, make a new connector.
(3) Check whether the IF cable is soggy, broken, or pressed. Replace the cable that does not
meet the requirement.
If... Then...
The alarm persists Replace the ODU at the opposite site.

OptiX RTN 620
If... Then...
Locate the fault by looping back the opposite site and excluding the position one by one. Follow
the steps:
(1) Perform an inloop on the IF port at the local end. For details, see 7.5.4 Setting Loopback
for the IF Board. Check whether the fault at the opposite end is rectified after the loopback.
If... Then...
(2) Check whether the cable connector workmanship meets the requirement. If any cable
(3) Check whether the IF cable is soggy, broken, or pressed. Replace the cable that does not
meet the requirement.
If... Then...
The alarm persists Replace the ODU of the local site.
Step 4 Cause 4: An interference event occurs.

(1) Check whether any co-channel interference occurs.
a. Mute the opposite ODU.
b. Check the RSL at the local end. For details, see Configuring the IF/ODU Information
of a Radio Link. If the RSL exceeds -90 dBm, you can infer that there is co-channel
interference that may affect the long-term availability and errored-second
(2) Check whether any adjacent channel interference occurs.
b. Adjust the radio working mode at the local end and use the minimum channel spacing.
For details, see Configuring the IF/ODU Information of a Radio Link.
c. Decrease the received frequency at the local end by a half of the channel spacing. For
details, see Configuring the IF/ODU Information of a Radio Link.
d. Test and record the RSL.
e. 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.
f. 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.

OptiX RTN 620
(4) Contact the spectrum management department to clear the interference spectrum or change
plans to minimize the interference.
----End
Related Information
None.
A.2.118 MW_LIM
Description
The MW_LIM is an alarm indicating that a mismatched radio link identifier is detected. This
alarm occurs when the IF board detects that the link ID in the microwave frame overheads is
inconsistent with the specified link ID.
Attribute
Parameters
table.
Name Meaning

After reporting the MW_LIM alarm, the IF board inserts the AIS alarm to the received signals.
Then, the services on the radio link are interrupted. If the services are configured with SNCP,
the protection switching may be triggered.
Possible Causes
l Cause 1: The link ID of the local site does not match the link ID of the opposite site.
l Cause 2: The services on other radio links are received due to the incorrect configuration
of the radio link receive frequency at the local or opposite site.
l Cause 3: The antenna receives microwave signals from the other site, because the direction
of the antenna is set incorrectly.
l Cause 4: The polarization direction of the XPIC is configured incorrectly.

OptiX RTN 620
Procedure
Step 1 Determine the IF port that reports the alarm based on the alarm parameters.
Step 2 Cause 1: The link ID of the local site does not match the link ID of the opposite site.
(1) Check whether the link ID of the local site matches with the link ID of the opposite site.
For details, see Configuring the IF/ODU Information of a Radio Link. If not, set the link
IDs at both ends to the same according to the network planning.
Step 3 Cause 2: The services on other radio links are received due to the incorrect configuration of the
radio link receive frequency at the local or opposite site.
(1) Check whether the receive and transmit frequencies of the local site are consistent with the
receive and transmit frequencies of the opposite site. For details, see Configuring the IF/
ODU Information of a Radio Link. If not, set the receive and transmit frequencies of the
two sites again according to the network planning.
Step 4 Cause 3: The antenna receives microwave signals from the other sites, because the direction of
the antenna is set incorrectly.
(1) Adjust the direction of the antenna and ensure that the antennas at both ends are aligned.
Step 5 Cause 4: The polarization direction of the XPIC is configured incorrectly.
(1) If XPIC protection groups are configured, check whether the XPIC configuration is correct.
For details, see Creating an XPIC Workgroup.
a. Check whether the settings of IFX boards in polarization direction-V and
polarization direction-H meet the requirement of the network planning.
If... Then...
No Delete the XPIC workgroups that are configured incorrectly and create XPIC
workgroups again.
Yes Go to the next step.
b. Check whether Link ID-V and Link ID-H meet the requirement of the network
planning.
If... Then...
No Reset the ID of the radio link of the IFX
board according to the network planning.
For details, see Creating XPIC
Workgroups.
The link ID meets the requirement of Go to the next step.
the network planning
(2) Check and modify the IFX board and ODU, and the mapping relation between the ODU
and the antenna feed. Ensure that the IFX boards in the polarization direction V of both
ends are interconnected to each other through the radio link in the polarization direction V,
and the IFX boards in the polarization direction H of both ends are interconnected to each
other through the radio link in the polarization direction H.
----End
Related Information
The MW_LIM alarm is generated due to the inconsistency between the specified link ID and
the received link ID. When the MW_LOF alarm is generated on the link, the received link ID

OptiX RTN 620
is a random value. In this case, the link ID is invalid. The MW_LIM alarm is also suppressed
by the MW_LOF alarm.
A.2.119 MW_LOF
Description
The MW_LOF is an alarm indicating that the Reed Solomon (RS) frame is lost.
Attribute
Parameters
table.
Name Meaning

The services are interrupted. If the system is configured with protection, protection switching
may be triggered.
Possible Causes
l Cause 1: The other alarms are generated.
l Cause 2: In the case of TDM radio services, the IF working modes at the local site and the
opposite site are different. In the case of Hybrid radio services, the channel bandwidth and
modulation modes at the local site and the opposite site are different.
l Cause 3: The working frequency of the ODU at the local site is inconsistent with the
working frequency of the ODU at the opposite site.
l Cause 6: The receive power of the ODU is abnormal.
l Cause 7: An interference event occurs.
Procedure
Step 1 Cause 1: The other alarms are generated.

OptiX RTN 620
(1) Check whether any alarms are generated in the equipment at the local site. If yes, take
priority to clear them.
The relevant alarms are as follows:
l HARD_BAD
l VOLT_LOS
l IF_CABLE_OPEN
l BD_STATUS
l RADIO_RSL_LOW
l CONFIG_NOSUPPORT
l TEMP_ALARM
Step 2 Cause 2: In the case of TDM radio services, the IF working modes at the local site and the
opposite site are different. In the case of Hybrid radio services, the channel bandwidth and
modulation modes at the local site and the opposite site are different.
(1) In the case of TDM radio services, check whether the working mode of the IF board at the
local site is consistent with the working mode of the IF board at the opposite site. For details,
see Configuring the IF/ODU Information of a Radio Link. If not, reset the working mode
of the IF board according to the network planning.
In the case of Hybrid radio services, check whether the channel bandwidth and modulation
modes are the same at both ends. If not, change the channel bandwidth and modulation
modes according to the network planning. For details, see Setting the Hybrid/AM Attribute.
Step 3 Cause 3: The working frequency of the ODU at the local site is inconsistent with the working
frequency of the ODU at the opposite site.
(1) Ensure that the type of the ODU at the local site is consistent with the type of the ODU at
the opposite site.
(2) Reset the working frequency of the ODU according to the network planning. For details,
see Setting Parameters of ODU Interfaces.
Set the value of the transmit frequency of the local site the same as the value of the receive
frequency of the opposite site. Then, set the value of the receive frequency of the local site
the same as the value of the transmit frequency of the opposite site.

(1) Check whether any alarms are generated in the equipment of the local site. If yes, take
priority to clear them.
The relevant alarms are as follows:
l HARD_BAD
l BD_STATUS
l VOLT_LOS
l IF_CABLE_OPEN
l RADIO_MUTE
l RADIO_TSL_HIGH
l RADIO_TSL_LOW
l TEMP_ALARM
(2) Locate the fault by looping back the opposite site.

OptiX RTN 620
Follow the steps:

a. Perform an inloop on the IF port at the opposite end. For details, see 7.5.4 Setting
Loopback for the IF Board. Check whether the fault at the opposite end is rectified
after the loopback.
If... Then...
b. Check whether the cable connector workmanship meets the requirement. If any cable
c. Check whether the IF cable is soggy, broken, or pressed. Replace the cable that does
d. Then, check whether the alarm clears.
(1) Locate the fault by looping back the opposite site.
Follow the steps:
a. Perform an inloop on the IF port at the local end. For details, see 7.5.4 Setting
Loopback for the IF Board. Check whether the fault at the opposite end is rectified
after the loopback.
If... Then...
b. Check whether the cable connector workmanship meets the requirement. If any cable
c. Check whether the IF cable is soggy, broken, or pressed. Replace the cable that does
d. Then, check whether the alarm clears.
Step 6 Cause 6: The receive power of the ODU is abnormal.
(1) Check whether the receive power of the ODU at the local site is abnormal. If yes, determine
the abnormality and take proper measures. For details, see 7.3.7 Browsing the History
Performance.

OptiX RTN 620
If... Then...
The RSL is lower than the receiver Follow the steps:

sensitivity
1. Check the installation of the antenna to ensure
that 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 the
incorrect polarization direction.
4. Check whether the antenna gain at both the
transmit and receive ends meets the
specifications. Replace the antennas that do
5. Check whether any mountain or building
obstacle exists in the transmit direction.
If yes, contact the network planning
department for proper modification of the
planning design, hence preventing the block
of the mountain or building obstacle.
The RSL is higher than the specified RSL Slow up fading occurs. Follow the steps:
of the network. The offset value is tens of
decibles. The duration is from tens of 1. Check whether any co-channel interference
seconds to several hours occurs.
a. Mute the ODU at the opposite end. For
details, see Configuring the IF/ODU
b. Check the RSL at the local end. For details,
see Configuring the IF/ODU Information of
a Radio Link. If the RSL exceeds -90 dBm,
you can infer that there is co-channel
interference that may affect the long-term
availability and errored-second
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 minimize the interference.

OptiX RTN 620
If... Then...
The RSL is lower than the specified RSL Slow down fading occurs. Generally, the radio
of the network. The offset value is tens of link may be faulty in both directions, because
decibles. The duration is from tens of slow fading is imposed by the transmission path.
seconds to several hours Contact the network planning department to
make the following changes:
l Increase the installation height of the antenna.
If the RSL is lower than or higher than Fast fading occurs. Contact the network planning
the specified RSL of the network and if department to make the following changes:
the duration is from several milliseconds
l Adjust the position of the antenna to block the
to tens of seconds
reflected wave or make the reflection point fall
on the ground that has a small reflection
coefficient, thus reducing the multipath
fading.
l Adjust the RF configuration to make the links
in the 1+1 SD configuration.
l If the links are in the 1+1 SD configuration,
adjust the height offset between two antennas
to make the receive power of one antenna
much stronger than the receive power of the
other antenna.
l Increase the fading margin.
Step 7 Cause 7: An interference event occurs.

Follow the steps:
(1) Check whether any co-channel interference occurs.
b. Check the RSL at the local end. For details, see Configuring the IF/ODU Information
of a Radio Link. If the RSL exceeds -90 dBm, you can infer that there is co-channel
interference that may affect the long-term availability and errored-second
(2) Check whether any adjacent channel interference occurs.
b. Adjust the radio working mode at the local end and use the minimum channel spacing.
For details, see Configuring the IF/ODU Information of a Radio Link.
c. Decrease the received frequency at the local end by a half of the channel spacing. For
details, see Configuring the IF/ODU Information of a Radio Link.
d. Test and record the RSL.

OptiX RTN 620
e. 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.
f. 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 minimize the interference.
----End
Related Information
None.
A.2.120 MW_RDI
Description
The MW_RDI alarm indicates that there are defects at the remote end of a radio link. This alarm
occurs when the IF board detects an RDI in the radio frame overheads.
Attribute
Parameters
table.
Name Meaning

If the local site is configured with reverse switching, 1+1 switching on the IF board is triggered
when the working and protection boards receive the MW_RDI alarm at the same time. This
alarm also indicates that the services received at the opposite site are interrupted.
Possible Causes
After detecting a service alarm that is caused by the fault on a radio link, the receive end returns
a radio link fault indication to the transmit end.

OptiX RTN 620
Procedure
Step 1 Cause: After detecting a service alarm that is caused by the fault on a radio link, the receive end
returns a radio link fault indication to the transmit end.
(1) Clear the microwave alarms that occur at the opposite site. The possible alarms are as
follows:
l MW_LOF
l R_LOF
l R_LOC
----End
Related Information
None.
A.2.121 NESF_LOST
Description
The NESF_LOST is an alarm indicating that the NE software is lost. This alarm occurs when
the system control, cross-connect, and timing board detects that the NE software in the flash
memory is lost.
Attribute

Parameters
table.
Name Meaning
Parameter 1 Indicates the routine inspection object.
l 0x01: Indicates an ordinary file
l 0x02: Indicates the version of the running software
l 0x03: Indicates a special routine inspection object

OptiX RTN 620
Name Meaning
Parameter 2, Parameter 3 Indicate the ID of the routine inspection object.
l 0x01, 0x03, and 0x05: indicate the scc.fpga, nesoft.hwx, and

ne.ini files in ofs1, respectively.
l 0x02, 0x04, and 0x06: indicate the scc.fpga, nesoft.hwx, and
ne.ini files in ofs2, respectively.
Parameter 4 Alarm Cause
l If the first bit is 1, it indicates that the file does not exist.
l If the second bit is 1, it indicates that verification of the file fails.
l If the third bit is 1, it indicates that the version of the file in the
active area is different from the version of the file in the standby
area.
l If the fourth bit is 1, it indicates that the version of the file of the
active board is different from the version of the file in the standby
board.

If the NE software does not exist in the active and standby areas, an NE cannot be restarted after
it is powered off or reset.
Possible Causes
l Cause 1: No new NE software is loaded after the existing NE software is erased.
l Cause 2: Loading the NE software fails.
l Cause 3: The portable flash memory card is not in position or is faulty.
Procedure
Step 1 Cause 1: No new NE software is loaded after the existing NE software is erased.
Cause 2: Loading the NE software fails.
(1) Check whether the alarm is caused by the loading operation.
If... Then...
The alarm is caused by the loading Contact the Huawei engineers to re-load the
operation software.
The alarm is not caused by the loading Go to the next step.
operation
Step 2 Cause 3: The portable flash memory card is not in position or is faulty.
(1) Re-install or replace the portable flash memory card.
----End

OptiX RTN 620
Related Information
None.
A.2.122 NESTATE_INSTALL
Description
The NESTATE_INSTALL is an alarm indicating that the NE is in the install state.
Attribute
Parameters
None.

The NE fails to work.
Possible Causes
l Cause 1: The logical cross-connect board is not configured.
l Cause 2: The NE database check fails.
Procedure
Step 1 Cause 1: The logical cross-connect board is not configured.
(1) Check whether the logical cross-connect board is configured in the slot layout on the NMS.
For details, see Configuring Logical Boards.
Step 2 Cause 2: The NE database check fails.

(1) Restore the data from the backup database.
----End
Related Information
None.
A.2.123 NO_BD_SOFT
Description
The NO_BD_SOFT is an alarm indicating that the board software is lost.

OptiX RTN 620
Attribute
Parameters
table.
Name Meaning
Parameter 2, Parameter 3 Indicate the type of the lost software.
l 0x01: board software
l 0x02: active FPGA
l 0x03: standby FPGA

l If the board software is lost, the board fails to work normally.
l If the FPGA is lost, the FPGA has no backup copy.
Possible Causes
Cause 1: Software loading fails to be performed correctly.
Procedure
Step 1 Cause 1: Software loading fails to be performed correctly.
(1) Contact Huawei technical support engineers to re-load the software.
----End
Related Information
None.
A.2.124 NP1_MANUAL_STOP
Description
The NP1_MANUAL_STOP is an alarm indicating that the N+1 protection protocol is stopped
manually.

OptiX RTN 620
Attribute
Parameters
table.
Name Meaning
Parameter 1, Parameter 2 Indicate the ID of the protection group that reports the alarm. For
example, 0x01 indicates that the alarm is reported by protection
group 1.

N+1 protection may fail, or protection switching may fail.
Possible Causes
Cause 1: The N+1 protection protocol is stopped manually.
Procedure
Step 1 Cause 1: The N+1 protection protocol is stopped manually.
(1) Start the N+1 protection protocol.
----End
Related Information
None.
A.2.125 NP1_SW_FAIL
Description
The NP1_SW_FAIL is an alarm indicating that N+1 protection switching fails.
Attribute

OptiX RTN 620
Parameters
table.
Name Meaning
Parameter 1, Parameter 2 Indicate the ID of the protection group that reports the alarm. For
example, 0x01 indicates that the alarm is reported by protection
group 1.

Services cannot be switched. If the current paths are unavailable, the services are interrupted.
Possible Causes
l Cause 1: The parameters of the N+1 protection for the node that reports the alarm are set
incorrectly.
l Cause 2: The networkwide N+1 protection protocol runs abnormally.
Procedure
Step 1 Cause 1: The parameters of the N+1 protection for the node that reports the alarm are set
incorrectly.
(1) Check whether the parameters of the N+1 protection are set correctly based on the planning
information. For details, see Creating an N+1 Protection Group.
If... Then...
The parameters of the N+1 protection are set Set the parameters correctly.
incorrectly
The parameters of the N+1 protection are set correctly Go to Cause 2.
Step 2 Cause 2: The networkwide N+1 protection protocol runs abnormally.

(1) Stop and restart the protocol manually. For details, see Starting/Stopping the N+1
Protection Protocol.
If... Then...
The alarm clears after the protocol is End the alarm handling.
restarted
The alarm persists after the protocol is Contact Huawei technical support
restarted engineers to handle the alarm.
----End
Related Information
None.

OptiX RTN 620
A.2.126 NP1_SW_INDI
Description
The NP1_SW_INDI is an alarm indicating N+1 protection switching. When the N+1 protection
switching is successful, the NP1_SW_INDI alarm is reported. When the switching status is
changed to the idle status, the NP1_SW_INDI alarm clears.
Attribute

Parameters
table.
Name Meaning

During the N+1 protection switching (not more than 50 ms), the services are interrupted. After
the N+1 switching is complete, the services are restored to normal.
When the services are switched from the working path to the protection path, the extra services
in the protection path are interrupted. When the services are switched back to the working path,
the extra services in the protection path continue to be transmitted.
Possible Causes
Cause: The N+1 protection switching is performed.
Procedure
Step 1 Cause: The N+1 protection switching is performed.
(1) Find out the cause of switching and take proper measures.
l Possible external switching operations: forced switching and manual switching
l Possible causes for automatic switching: fault in the hardware of the ODU or the IF
board, MW_LOF, R_LOC, R_LOF, R_LOS, MS_AIS, and B2_EXC alarm

OptiX RTN 620
If... Then...
The switching is caused by external Clear the external switching operation. For
switching operations details, see Performing IF N+1 Protection
Switching.
The switching is automatic switching Clear the alarm that triggers the automatic
switching.
----End
Related Information
None.
A.2.127 OPM_FAIL
Description
The OPM_FAIL is an alarm indicating that the system fails to launch optical power.
Attribute

Parameters
table.
Name Meaning
board.

The services at the optical interface that reports the alarm are interrupted.
Possible Causes
Cause 1: The SFP optical module is faulty.

OptiX RTN 620
Procedure
Step 1 Cause 1: The SFP optical module is faulty.
(2) Contact Huawei technical support engineers to replace the faulty SFP optical module with
a new one of the same type.
----End
Related Information
None.
A.2.128 P_AIS
Description
The P_AIS is an alarm indication at a PDH interface. This alarm occurs when the tributary board
detects that uplink PDH signals are all 1s.
Attribute

Parameters
table.
Name Meaning

The signals at a specific PDH interface are unavailable.
Possible Causes
l Cause 1: The opposite PDH equipment transmits the AIS signal.
l Cause 2: The receive unit of the tributary board on the local equipment is faulty.

OptiX RTN 620
Procedure
Step 1 Check whether the opposite equipment transmits the AIS signal.
If... Then...
The opposite equipment transmits the AIS Rectify the fault on the opposite equipment.
signal
The opposite equipment does not transmit Go to the next step.
the AIS signal
Step 2 Replace the board that reports the alarm.
----End
Related Information
None.
A.2.129 P_LOS
Description
The P_LOS is an alarm indicating that signals at a PDH interface are lost.
Attribute

Parameters
table.
Name Meaning

PDH services are interrupted.

OptiX RTN 620
Possible Causes
l Cause 1: The port does not access PDH services.
l Cause 2: The opposite equipment is faulty.
l Cause 3: The trunk cable is faulty.
l Cause 4: The board that reports the alarm is faulty.
Procedure
Step 1 Cause 1: The port does not access PDH services.
(1) Check whether the port accesses PDH services.
If... Then...
The port does not access PDH services Enable the port to access PDH services or
delete unnecessary services.
The port accesses PDH services Go to Cause 2.
Step 2 Cause 2: The opposite equipment is faulty.

(1) Check whether the opposite equipment is faulty.
If... Then...
The equipment functions normally Go to Cause 3.
Step 3 Cause 3: The trunk cable is faulty.

(1) Check whether the trunk cable is broken or cut.
If... Then...
The trunk cable is broken or cut Rectify the corresponding fault.
The trunk cable is in normal status Go to Cause 4.
Step 4 Cause 4: The board that reports the alarm is faulty.

----End
Related Information
None.
A.2.130 PROT_CONN_ERR
Description
The PROT_CONN_ERR is an alarm indicating that an exception occurs in the connection of
the protection pair. This alarm is reported when the system detects any of the following
conditions: A cross-connection or incorrect connection exists between the protection pair

OptiX RTN 620
configured on the EMS6/EFP6 board and the IFH2 board, or the connection between the
protection pair configured on the EMS6/EFP6 board and the IFH2 board is incorrect.
Attribute

Major Service alarm
Parameters
table.
Name Meaning
Parameter 1 Indicates the ID of the optical interface that reports the alarm.
Parameter 2 Indicates the type of incorrect connection.
l 0x00: loss of the protection group connection
l 0x01: protection group mismatch
l 0x02: disabled protection group
Parameter 3, Parameter 4 Indicate the information about the opposite site.

l When the value of Parameter 2 is 0x00, the values of Parameter
3 and Parameter 4 are 0x00 0x00.
l When the value of Parameter 2 is 0x01:
Parameter 3 indicates the slot ID of the board that does not match
the protection group.
Parameter 4 indicates the ID of the port that does not match the
protection group.
l When the value of Parameter 2 is 0x02:
Parameter 3 indicates the slot ID of the connected board.
Parameter 4 indicates the ID of the port that is connected to the
port that reports the alarm.

The services that travel through the protection group are unavailable or the protection function
fails.
Possible Causes
l Cause 1: The connection between the local protection group and the opposite protection
group (IFH2) fails.

OptiX RTN 620
l Cause 2: The opposite ports connected to the ports of the local protection group are not in
the same protection group or are non-protection ports.
l Cause 3: The non-protection ports at the local site are connected to the protection ports of
the opposite site (IFH2).
Procedure
Step 1 Handle the alarm based on the value of Parameter 2.
If... Then...
The value of Parameter 2 is 0x00 See Step 2.
The value of Parameter 2 is 0x01 See Step 3 or Step 4.
The value of Parameter 2 is 0x02 Enable the ports of the local protection group.
Step 2 Cause 1: The connection between the local protection group and the opposite protection group
(IFH2) is faulty.
(1) Check whether the network cables connecting the port that reports the alarm and the two
IFH2 boards of the IF 1+1 protection are incorrectly connected or faulty.
If... Then...
The network cables are loose or not connected Connect the network cables properly.
The network cables are faulty Replace the network cables.
Step 3 Cause 2: The opposite ports connected to the ports of the local protection group are not in the
same protection group or are non-protection ports.
(1) Check whether the IFH2 board connected to the port that reports the alarm is in the mapping
IF 1+1 protection group.
If... Then...
The opposite ports are not in the same Connect the ports that are in the same
protection group protection group.
The opposite ports are non-protection Enable the ports of the opposite protection
ports group.
Step 4 Cause 3: The non-protection Ethernet ports at the local site are connected to the protection ports
of the opposite site (IFH2).
(1) Check whether the Ethernet ports at the local site are in the protection group. If not,
configure these Ethernet ports into LAGs. For details, see Creating a LAG.
----End
Related Information
None.
A.2.131 PORT_MODULE_OFFLINE

OptiX RTN 620
Description
The PORT_MODULE_OFFLINE is an alarm indicating that a port is off line.
Attribute

Parameters
table.
Name Meaning

The services at the port that reports the alarm are interrupted.
Possible Causes
The port is enabled, but the SFP module is not installed.
Procedure
Step 1 Cause: The port is enabled, but the SFP module is not installed.
(1) Check whether the port needs to access services.
If... Then...
The port needs to access services Go to the next step.
The port need not access services Disable the port.
(2) Check whether the SFP module is installed.
If... Then...
The SFP module is not installed Contact Huawei technical support engineers to install
the required SFP module.
The SFP module is installed Go to the next step.
(3) Re-install the SFP module.

OptiX RTN 620
If... Then...
The alarm clears The fault is rectified. End the alarm handling.
The alarm persists Contact Huawei technical support engineers to replace the faulty
SFP module.
----End
Related Information
None.
A.2.132 POWER_ALM
Description
The POWER_ALM is a power module alarm indication.
Attribute
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 power module 1 of the board.
Parameter 2 l 0x01: under-voltage
l 0x02: over-voltage

The power module is under protection. Therefore, if only one power module reports the
POWER_ALM alarm, the system is not affected.
Possible Causes
l Cause 1: The accessed power is abnormal.
l Cause 2: The power module is abnormal.

OptiX RTN 620
Procedure
Step 1 Cause 1: The accessed power is abnormal.
(1) Use a multimeter to test the power voltage supplied to the chassis.
If... Then...
The voltage is beyond the range of -38.4 V to -72 V Clear the alarm immediately.
The voltage is within the range of -38.4 V to -72 V Go to Cause 2.
Step 2 Cause 2: The power module is abnormal.

----End
Related Information
l In the case of the IDU 620, the power modules on the two PXC boards provide 1+1 power
supply backup for the system.
l In the case of the IDU 620, the power modules on the two FAN boards provide 1+1 power
supply backup for the fan.
A.2.133 PS
Description
The PS is a protection switching alarm indication.
Attribute

Parameters
table.
Name Meaning
Parameter 1 The value is always 1.
indicates that the alarm is reported in path 1.

OptiX RTN 620

During the switching (less than 50 ms), services are interrupted. After the switching, the services
are restored to normal.
Possible Causes
Cause: Protection switching occurs in the services.
Procedure
Step 1 Cause: Protection switching occurs in the services.
(1) Find out the cause of the switching.
(2) Cancel the manual switching command if it is carried out.
(3) Browse current alarms, and check whether the path where the switching occurs reports
alarms. If yes, handle the alarms.
----End
Related Information
None.
A.2.134 R_F_RST
Description
The R_F_RST is an alarm indicating that the receive FIFO is reset.
Attribute

Parameters
table.
Name Meaning

OptiX RTN 620

Services are interrupted.
Possible Causes
l Cause 1: The clocks at both sites are not synchronous.
l Cause 2: A certain board is faulty.
Procedure
Step 1 Cause 1: The clocks at both sites are not synchronous.
(1) Check whether a TU pointer justification performance event is reported at both sites. For
details, see 7.3.6 Browsing Current Performance Events.
If... Then...
A TU pointer justification performance Handle the performance event. For details,
event is reported see C.2.3 TUPJCHIGH, TUPJCLOW,
and TUPJCNEW.
No TU pointer justification Go to Cause 2.
performance event is reported
Step 2 Cause 2: A certain board is faulty.

----End
Related Information
None.
A.2.135 R_LOC
Description
The R_LOC is an alarm indicating that the clock is lost on the receive line side. This alarm is
reported when the line board fails to extract the clock signal from the line signal or the IF board
fails to extract the clock signal from the IF signal.
Attribute
Parameters

OptiX RTN 620
table.
Name Meaning
Parameter 2, Parameter 3 Indicate the ID of the path.

The services on the line port or the IF port are interrupted. If the system is configured with
protection, protection switching may be triggered.
Possible Causes
Procedure
(1) At the local site, perform an inloop on the port of the board that reports the alarm. For
details, see 7.5 Software loopback.
If... Then...
The alarm persists after the loopback Replace the board that reports the alarm at
the local site.
The alarm clears after the loopback Go to Cause 2.
If... Then...
replaced handling.
The alarm persists after the board is Replace the PXC board of the local site.
replaced

(1) Replace the board of the opposite site.
If... Then...
replaced handling.
The alarm persists after the board is Replace the PXC board of the opposite
replaced site.
----End

OptiX RTN 620
Related Information
None.
A.2.136 R_LOF
Description
The R_LOF is an alarm indicating that frames are lost on the receive side. This alarm is reported
when the OOF state lasts for 3 ms.
Attribute
Parameters
table.
Name Meaning
Parameter 2, Parameter 3 Indicate the ID of the path.

Services are interrupted. If the system is configured with protection, protection switching may
be triggered.
Possible Causes
l Cause 1: Certain other alarms occur (if the alarm is reported by an IF board).
l Cause 2: The line performance declines (if the alarm is reported by an SDH optical or
electrical line board).
Procedure
Step 1 Based on the alarm parameters, determine the line port that reports the alarm.
Step 2 Cause 1: Certain high-level alarms occur (if the alarm is reported by an IF board).

OptiX RTN 620
(1) Check whether the MW_FEC_UNCOR alarm is reported if the alarm is reported by an IF
board.
If... Then...
The MW_FEC_UNCOR alarm is Handle the MW_FEC_UNCOR alarm
reported immediately.
The MW_FEC_UNCOR alarm is not Go to the next step.
reported
(2) Perform an inloop on the IF port that reports the alarm.
If... Then...
The alarm clears after the inloop is Clear the alarm according to the solution
performed for the alarm that is reported when the
transmit unit of the opposite site is faulty.
The alarm persists after the inloop is Clear the alarm according to the solution
receive unit of the local site is faulty.
Step 3 Cause 2: The line performance declines (if the alarm is reported by an SDH optical or electrical
line board).
(1) Exchange the receive/transmit fiber jumpers or cables at the receive and transmit ends.
If... Then...
The alarm persists after the exchange Clear the alarm according to the solution for
the alarm that is reported when the transmit
unit of the opposite site is faulty.
The line port of the opposite site reports Rectify the fault on fibers or cables.
the R_LOF alarm

(1) Replace the line board (SDH optical/electrical line board or IF board) of the opposite site.
For details, see 6 Part Replacement.
If... Then...
replaced handling.
replaced
If... Then...
replaced handling.
The alarm persists after the board is Clear the alarm according to the solution for
replaced the alarm that is reported when the receive
unit of the local site is faulty.

OptiX RTN 620

----End
Related Information
None.
A.2.137 R_LOS
Description
In the case of SDH line boards, the R_LOS is an alarm indicating that the signals on the receive
line side are lost. In the case of IF boards, the R_LOS is an alarm indicating that the microwave
frames on the receive line side are lost.
Attribute
Parameters
table.
Name Meaning
Parameter 2, Parameter 3 Indicate the ID of the path. For example, 0x00 0x01 indicate that
the alarm is reported in path 1.

Services are interrupted. If the system is configured with protection, protection switching may
be triggered.
Possible Causes
l Cause 1: Certain other alarms occur (if the alarm is reported by an IF board).
l Cause 2: The line performance declines (if the alarm is reported by an SDH optical or
electrical line board).

OptiX RTN 620
Procedure
Step 1 Based on the alarm parameter, determine the line port that reports the alarm.
Step 2 Cause 1: Certain high-level alarms occur (if the alarm is reported by an IF board).
(1) Check whether the MW_FEC_UNCOR alarm is reported if the alarm is reported by an IF
board.
If... Then...
The MW_FEC_UNCOR alarm is Handle the MW_FEC_UNCOR alarm
reported immediately.
The MW_FEC_UNCOR alarm is not Go to the next step.
reported
(2) Perform an inloop on the IF port that reports the alarm.
If... Then...
The alarm clears after the inloop is Clear the alarm according to the solution
transmit unit of the opposite site is faulty.
The alarm persists after the inloop is Clear the alarm according to the solution
receive unit of the local site is faulty.
Step 3 Cause 2: The line performance declines (if the alarm is reported by an SDH optical or electrical
line board).
(1) Exchange the receive/transmit fiber jumpers or cables at the receive and transmit ends.
If... Then...
The alarm persists after the exchange Clear the alarm according to the solution for
the alarm that is reported when the transmit
unit of the opposite site is faulty.
The line port of the opposite site reports Rectify the fault on fibers or cables.
the R_LOF alarm

(1) Replace the line board (SDH optical/electrical line board or IF board) of the opposite site.
For details, see 6 Part Replacement.
If... Then...
replaced handling.
replaced

OptiX RTN 620
If... Then...
replaced handling.
The alarm persists after the board is Clear the alarm according to the solution for
replaced the alarm that is reported when the receive
unit of the local site is faulty.

----End
Related Information
None.
A.2.138 R_S_ERR
Description
The R_S_ERR is an alarm indicating that the received signal has errors.
Attribute
Parameters
table.
Name Meaning

Services are interrupted.
Possible Causes
l Cause 1: The frequency offset of the received signal is large.

OptiX RTN 620
Procedure
Step 1 Cause 1: The frequency offset of the received signal is large.
(1) Check whether the tributary board supports the type of the received signal.
If... Then...
The tributary board does not support Change the type of the signal transmitted
the type of the received signal from the opposite site.
The tributary board supports the type of Go to the next step.
the received signal
(2) Test the frequency offset of the received signal.
If... Then...
The frequency offset is large Troubleshoot the opposite site.
The frequency offset meets the requirement Go to Cause 2.

----End
Related Information
None.
A.2.139 RADIO_FADING_MARGIN_INSUFF
Description
The RADIO_FADING_MARGIN_INSUFF is an alarm indicating that the mean receive power
of the ODUs are lower than the threshold of the receive power (the threshold value is about the
receiver sensitivity plus 14 dB).
When the receive power of the ODUs in consecutive six hours is lower than the threshold, the
system reports the alarm. When the mean receive power of the ODUs becomes normal in three
minutes after the alarm is reported, the alarm clears.
Attribute
Parameters

OptiX RTN 620

table.
Name Meaning

If the MW_LOF or MW_FEC_UNCOR alarm is not generated, services are not affected.
Possible Causes
l Cause 1: The ODU fault at the transmit end causes abnormal transmit power.
l Cause 2: The direction of the antenna is deflected.
l Cause 3: Transmission environment changes.
l Cause 4: The fading margin in the case of rain and fog in the network planning is
insufficient.
Procedure
Step 1 Cause 1: The ODU fault at the transmit end causes abnormal transmit power.
(1) Check whether the ODU at the transmit end reports the RADIO_TSL_LOW alarm.
If... Then...
The ODU at the transmit end reports the Handle the RADIO_TSL_LOW alarm.
RADIO_TSL_LOW alarm
The ODU at the opposite end does not report the Go to Cause 2.
RADIO_TSL_LOW alarm
Step 2 Cause 2: The direction of the antenna is deflected.

(1) Check whether the direction of the antenna is deflected.
If... Then...
The direction of the antenna is deflected Adjust the direction of the antenna.
The direction of the antenna is not deflected Go to Cause 3.
Step 3 Cause 3: Transmission environment changes.

(1) Check whether the transmission environment changes. For example, check whether any
building blocks the transmission and increases the link fading significantly.
If... Then...
The transmission environment changes Contact the network planning department for
replanning the transmission trail.

OptiX RTN 620
If... Then...
The transmission environment does not Go to Cause 4.
change
Step 4 Cause 4: The fading margin in the case of rain and fog in the network planning is insufficient.
(1) If the alarm is reported frequently, contact the network planning department for increasing
the fading margin by replanning the transmission trail.
----End
Related Information
None.
A.2.140 RADIO_MUTE
Description
The RADIO_MUTE is an alarm indicating that the radio transmitter is muted.
Attribute
Warning Equipment alarm
Parameters
table.
Name Meaning
Parameter 1 Indicates the RF port that reports the alarm.

The transmitter does not transmit services.
Possible Causes
l Cause 1: Certain other alarms occur.
l Cause 2: The transmitter of the local site is muted manually.
l Cause 3: The IF board is faulty, causing abnormal IF output.
l Cause 4: The data output is abnormal because the ODU is faulty.

OptiX RTN 620
Procedure
Step 1 Cause 1: Certain other alarms occur.
(1) Check whether the CONFIG_NOSUPPORT or IF_INPWR_ABN alarm is generated. If
yes, clear the alarm immediately.
Step 2 Cause 2: The transmitter of the local site is muted manually.

(1) Check whether the transmitter of the ODU is muted. For details, see Configuring the IF/
ODU Information of a Radio Link. If yes, unmute the ODU. Then, enable the ODU to
transmit signals.
Step 3 Cause 3: The IF board is faulty, causing abnormal IF output.

(1) Replace the IF board.
Step 4 Cause 4: The data output is abnormal because the ODU is faulty.
(1) 6.12 Replacing an ODU.
----End
Related Information
The number of the logical slot for the ODU is the number of the slot for the IF board connected
to the ODU plus 10.
A.2.141 RADIO_RSL_BEYONDTH
Description
The RADIO_RSL_BEYONDTH is an alarm indicating that antennas are not aligned. When the
receivable power is set on an NE, the NE enables the antenna alignment indication function
automatically. If the actual receive power of the ODU is lower than the preset receive power
minus 3 dB, the RADIO_RSL_BEYONDTH alarm is reported. Then, if the antennas are aligned
for continuous 30 minutes, the antenna alignment indication function is disabled automatically.
Afterwards, the RADIO_RSL_BEYONDTH alarm is reported only when the
RADIO_FADING_MARGIN_INSUFF alarm is reported.
Attribute

Parameters
table.

OptiX RTN 620
Name Meaning

If the MW_LOF or MW_FEC_UNCOR alarm is not generated, services are not affected.
Possible Causes
l Cause 1: Antennas are not aligned during the equipment commissioning.
l Cause 2: The RADIO_FADING_MARGIN_INSUFF is reported when the NE is running.
Procedure
Step 1 Cause 1: Antennas are not aligned during the equipment commissioning.
(1) Align the antennas, and ensure that the actual receive power is within the range of preset
receive power +/-3 dB.
Step 2 Cause 2: The RADIO_FADING_MARGIN_INSUFF is reported when the NE is running.
(1) Handle the RADIO_FADING_MARGIN_INSUFF alarm. When the
RADIO_FADING_MARGIN_INSUFF alarm clears, the RADIO_RSL_BEYONDTH
alarm clears.
----End
Related Information
None.
A.2.142 RADIO_RSL_HIGH
Description
The RADIO_RSL_HIGH is an alarm indicating that the radio receive power is 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
Critical Service alarm
Parameters

OptiX RTN 620

table.
Name Meaning

Normal transmission of services is affected. If the system is configured with 1+1 protection,
protection switching may be triggered.
Possible Causes
l Cause 1: The local ODU is faulty.
l Cause 2: There is a strong interference source nearby.
l Cause 3: The transmit power of the opposite ODU is high.
Procedure
Step 1 Cause 1: The local ODU is faulty.
(1) Replace the ODU.
Step 2 Cause 2: There is a strong interference source nearby.

(1) Check whether any nearby signal source transmits signals whose frequency is close to the
specified range. If yes, check whether the signal source can be closed or moved. If not,
contact the network planning department for replanning the frequency.
Step 3 Cause 3: The transmit power of the opposite ODU is high.

(1) Reset the transmit power of the opposite ODU. For details, see Configuring the IF/ODU
----End
Related Information
None.
A.2.143 RADIO_RSL_LOW
Description
The RADIO_RSL_LOW is an alarm indicating that the radio receive power is low. This alarm
is reported if the detected receive power is equal to or lower than the lower threshold of the ODU
(-90 dBm).

OptiX RTN 620
Attribute
Parameters
table.
Name Meaning

If no MW_LOF or MW_FEC_UNCOR alarm is generated, services are not affected.
Possible Causes
l Cause 1: Certain other alarms occur at the opposite site.
l Cause 2: The transmit power of the opposite site is low.
l Cause 3: The local ODU is faulty.
l Cause 4: Signal attenuation on the radio link is heavy.
Procedure
Step 1 Cause 1: Certain other alarms occur at the opposite site.
Check whether any of the following alarms is generated on the equipment of the opposite site.
If yes, clear the alarm immediately.
l RADIO_MUTE
l CONFIG_NOSUPPORT
l RADIO_TSL_LOW
l BD_STATUS
Step 2 Cause 2: The transmit power of the opposite site is low.

(1) Check whether the transmit power of the opposite site is normal. For details, see
Configuring the IF/ODU Information of a Radio Link. If the transmit power is abnormal,
replace the ODU of the opposite site.
Step 3 Cause 3: The local ODU is faulty.
(1) Replace the ODU of the local site.
Step 4 Cause 4: Signal attenuation on the radio link is heavy.
(1) Browse history alarms, and check whether the RADIO_RSL_LOW alarm occurs
continuously.

OptiX RTN 620
If the alarm occurs occasionally, contact the network planning department to change the
design to improve anti-fading performance.
(2) Check whether the antennas at both ends are aligned.
If the antennas are not aligned, align the antennas again.
(3) Check whether any mountain or building obstacle exists in the transmit direction.
If yes, contact the network planning department for proper modification to the planning
design, therefore avoiding the block of the mountain or building obstacle.
(4) Check whether the polarization direction of the antenna, ODU, and hybrid coupler at both
ends is set correctly.
If not, correct the polarization direction.
(5) Check whether the outdoor units such as the antenna, hybrid coupler, ODU, and flexible
waveguide are wet, damp, or damaged.
If yes, replace the unit that is wet, damp, or damaged. For details, see 6 Part
Replacement.
(6) Check whether the antenna gain at both the transmit and receive ends meets the requirement.
If not, replace the antenna.
----End
Related Information
None.
A.2.144 RADIO_TSL_HIGH
Description
The RADIO_TSL_HIGH is an alarm indicating that the radio transmit power is high. This alarm
is reported if the detected transmit power is higher than the upper power threshold of the ODU.
Attribute
Parameters
table.
Name Meaning

OptiX RTN 620

Possible Causes
Cause 1: The ODU is faulty.
Procedure
----End
Related Information
None.
A.2.145 RADIO_TSL_LOW
Description
The RADIO_TSL_LOW is an alarm indicating that the radio transmit power is low. This alarm
is reported if the detected transmit power is less than the lower power threshold of the ODU.
Attribute
Parameters
table.
Name Meaning


OptiX RTN 620
Possible Causes
Cause 1: The ODU is faulty.
Procedure
----End
Related Information
None.
A.2.146 RELAY_ALARM
Description
The RELAY_ALARM is an alarm indicating relay errors.
Attribute
Critical Environment alarm
Parameters
table.
Name Meaning
Parameter 1 Indicates the ID of the input alarm signal. For example, 0x01 indicates that the
reported external alarm is from the first input alarm signal.

None.
Possible Causes
Cause 1: There is an input alarm signal.
Procedure
Step 1 Cause 1: There is an input alarm signal.

OptiX RTN 620
(1) Based on the alarm parameter, determine the ID of the input alarm signal.
(2) Rectify the fault according the meaning of the input alarm signal.
----End
Related Information
None.
A.2.147 RP_LOC
Description
The RP_LOC is an alarm indicating that the clock of the receive phase-locked loop is lost.
Attribute

Parameters
None.

The services on the board are interrupted.
Possible Causes
l Cause 1: The service configuration data is incorrect.
Procedure
Step 1 Cause 1: The service configuration data is incorrect.
(1) Check whether the service is correctly configured.
If... Then...
The service is configured incorrectly Reconfigure the service.
The service is configured correctly Go to Cause 2.

----End

OptiX RTN 620
Related Information
None.
A.2.148 RPS_INDI
Description
The RPS_INDI is a radio protection switching alarm indication.
Attribute

Parameters
table.
Name Meaning
Parameter 1 Indicates the ID of the protection group.
Parameter 2 Indicates the type of protection switching.
0x01: HSB protection switching
0x02: HSM protection switching

During the HSB protection switching, services are interrupted. After the HSB switching is
complete, the services are restored to normal.
During the HSM protection switching, no bit errors occur and services are not affected.
Possible Causes
l The possible causes of the HSB protection switching are as follows:
– Cause 1: An external switching event occurs.
– Cause 2: An automatic switching event occurs.
– Cause 3: A reverse switching event occurs.
l Possible cause of the HSM protection switching: At the local site, the radio link in the
receive direction is faulty.

OptiX RTN 620
Procedure
Step 1 Determine the type of the protection switching based on the alarm parameter.
Step 2 Cause 1 of HSB switching: An external switching event occurs. That is, a command is issued
on the NMS to trigger the switching.
(1) Check whether the switching is the forced switching or manual switching. For details, see
Querying the IF 1+1 Protection Status.
If... Then...
The switching is the forced switching or Find the cause and clear the switching
manual switching immediately.
The switching is not the forced Go to Cause 2 of HSB switching.
switching or manual switching
Step 3 Cause 2 of HSB switching: An automatic switching event occurs. That is, the equipment is faulty,
or the service is defective.
(1) Check whether the following faults or alarms occur. If yes, rectify the faults or clear the
alarms.
l Hardware fault on the IF board, or hardware fault on the ODU
l POWER_ALM or VOLT_LOS
l RADIO_TSL_HIGH, RADIO_TSL_LOW, or RADIO_RSL_HIGH
l IF_INPWR_ABN or CONFIG_NOSUPPORT
l R_LOC, R_LOF, R_LOS, or MW_LOF
NOTE
l If the switching is non-revertive, the services are not automatically switched back to the working
path when the working path is restored to normal, and the RPS_INDI alarm persists. In this case,
you need to manually switch the services from the protection path to the working path. The
RPS_INDI alarm clears only when the switching is successful.
l If the switching is revertive, the services are automatically switched back to the working path
when the specified wait-to-restore (WTR) time expires after the working path is restored to
normal. The RPS_INDI alarm clears only when the switching is successful.
Step 4 Cause 3 of HSB switching: A reverse switching event occurs.

(1) Check whether the active and standby IF boards report the MW_RDI alarm. If yes, clear
the MW_RDI alarm immediately.
Step 5 Cause of the HSM switching: The radio link is faulty.

(1) Check whether any alarm that triggers HSM switching is generated on the IF board in the
IF 1+1 protection group. If yes, clear the alarm immediately.
HSM switching may be triggered by any of the following alarms:
l R_LOC, R_LOF, R_LOS, or MW_LOF
l MW_FEC_UNCOR
l B1_SD or B2_SD
----End

OptiX RTN 620
Related Information
None.
A.2.149 RS_CROSSTR
Description
The RS_CROSSTR is an alarm indicating that the regenerator section performance indicator
crosses the threshold. This alarm is reported if a board detects that the regenerator section
performance event crosses the preset threshold.
Attribute
Minor Service alarm
Parameters
table.
Name Meaning

A large number of bit errors occur in services, and the services may be interrupted.
Possible Causes
Cause 1: The regenerator section bit error performance event crosses the preset threshold.
Procedure
Step 1 Cause 1: The regenerator section bit error performance event crosses the preset threshold.

OptiX RTN 620
(1) Find out the regenerator section bit error performance event that crosses the threshold. For
details, see 7.3.8 Browsing the Performance Event Threshold-Crossing Records.
(2) Handle the performance event that crosses the threshold.
----End
Related Information
None.
A.2.150 RTC_FAIL
Description
The RTC_FAIL is an alarm indicating that the real-time clock (RTC) of the equipment fails.
Attribute

Parameters
None.

None.
Possible Causes
l Cause 1: The synchronization period on the NMS is long.
l Cause 2: The RTC on the SCC board malfunctions.
Procedure
Step 1 Cause 1: The synchronization period on the NMS is long.
(1) Modify the synchronization period on the NMS to one day. For details, see Synchronizing
NE Time.
Step 2 Cause 2: The RTC on the SCC board malfunctions.

(1) Reset the SCC board.
If... Then...
The alarm clears after the board is reset Reset the NE clock and end the alarm
handling.

OptiX RTN 620
If... Then...
The alarm persists after the board is Replace the SCC board.
reset
----End
Related Information
None.
A.2.151 S1_SYN_CHANGE
Description
The S1_SYN_CHANGE is an alarm indicating that the clock source is switched in S1 byte
mode.
Attribute
Parameters
table.
Name Meaning
Parameter 1 l 0x01: The system clock is switched.
l 0x02: The 2M phase-locked loop is switched.

After the clock source is switched, the lower quality of the newly traced clock source causes
pointer justifications and some bit errors. As a result, the quality of services is affected.
Possible Causes
The original clock source is lost when the SSM protocol or extended SSM protocol is enabled.
Procedure
Step 1 Cause: The original clock source is lost when the SSM protocol or extended SSM protocol is
enabled.

OptiX RTN 620
(1) Handle the SYNC_C_LOS alarm reported by the original clock source.
----End
Related Information
None.
A.2.152 SWDL_ACTIVATED_TIMEOUT
Description
The SWDL_ACTIVATED_TIMEOUT is an alarm indicating that the commit operation is not
performed during software package loading. During simulation package diffusion, the system
reports the alarm if the commit operation is not performed within 30 minutes after activation of
the board.
Attribute

Parameters
None.

If an NE fails to perform the commit operation for a long period, the software in the two areas
of the double-area boards is inconsistent.
Possible Causes
Certain radio links are faulty. As a result, the NE involved in the simulation package diffusion
fails to receive the commit command.
Procedure
Step 1 Cause: Certain radio links are faulty. As a result, the NE involved in the simulation package
diffusion fails to receive the commit command.
(1) Check whether any radio link is faulty.
If... Then...
Certain radio links are faulty Rectify the faults on the radio links and ensure that
the links between the nodes on which the software
package is loaded are normal.

OptiX RTN 620
If... Then...
Radio links are normal Perform simulation package diffusion for the NEs
that fail to be upgraded through simulation package
diffusion.
----End
Related Information
None.
A.2.153 SWDL_AUTOMATCH_INH
Description
The SWDL_AUTOMATCH_INH is an alarm indicating that the automatic match function is
disabled. When the automatic match function of the board is disabled, the system reports the
alarm if the board cannot find out the mapping software from the software on the SCC board.
Attribute
Parameters
None.

When an NE is installed with a board whose software version is not consistent, and if the board
fails to find out the mapping software from the software on the SCC board, the software versions
of the entire NE are inconsistent. As a result, certain functions of the NE cannot run normally.
Possible Causes
The automatic match function is disabled.
Procedure
Step 1 Cause: The automatic match function is disabled.
(1) Contact Huawei technical support engineers for troubleshooting.
----End
Related Information
None.

OptiX RTN 620
A.2.154 SWDL_COMMIT_FAIL
Description
The SWDL_COMMIT_FAIL is an alarm indicating that the commit operation on an NE fails.
This alarm is reported when the commit operation fails in simulation package diffusion.
Attribute

Parameters
None.

When the SWDL_COMMIT_FAIL alarm occurs, the software versions in the two areas of the
double-area board are inconsistent.
Possible Causes
Cause 1: The loaded software package is incorrect.
Procedure
Step 1 Cause 1: The loaded software package is incorrect.
(1) Check whether the loaded software package is correct.
(2) Perform simulation package diffusion again for the NE that reports the
SWDL_COMMIT_FAIL alarm.
----End
Related Information
None.
A.2.155 SWDL_CHGMNG_NOMATCH
Description
The SWDL_CHGMNG_NOMATCH is an alarm indicating that the board software version and
the version of the running software are inconsistent. This alarm is reported when the system
detects that the software version of any online board is inconsistent with the version of the
running software after the SCC board is replaced.

OptiX RTN 620
Attribute
Parameters
None.

When the SWDL_CHGMNG_NOMATCH alarm is reported, certain functions of the NE may
be affected because the board software version is inconsistent with the version of the running
software.
Possible Causes
The software package of the SCC board does not match the software version of the board after
the SCC board is replaced. In this case, the SWDL_CHGMNG_NOMATCH alarm is reported.
Procedure
Step 1 Cause: The software package of the SCC board does not match the software version of the board
after the SCC board is replaced. In this case, the SWDL_CHGMNG_NOMATCH alarm is
reported.
(1) Perform simulation package diffusion again for the NE that reports the
SWDL_CHGMNG_NOMATCH alarm.
----End
Related Information
None.
A.2.156 SWDL_INPROCESS
Description
The SWDL_INPROCESS is an alarm indicating that the simulation package diffusion is in
process on the NE.
Attribute
Warning Processing alarm
Parameters
None.

OptiX RTN 620

When the software package is being loaded to an NE, the operations, such as modifying
configuration, uploading/downloading files, and backing up the database, are not allowed.
Possible Causes
Cause: The simulation package diffusion is being performed on the NE.
Procedure
Step 1 Cause: The simulation package diffusion is being performed on the NE.
(1) The SWDL_INPROCESS alarm clears automatically after the loading or rollback is
complete. Hence, this alarm does not require handling.
----End
Related Information
None.
A.2.157 SWDL_NEPKGCHECK
Description
The SWDL_NEPKGCHECK is an alarm indicating that a certain file of the package stored in
the flash memory of the NE is lost. During the routine inspection on the flash memory in the
double areas of the SCC board, the NE software detects that a certain file of the package in one
area is missing or cannot be verified. If the corresponding file in the other area is normal, the
NE software recovers the missing or faulty file with the normal one. This alarm is reported when
the file is found missing and cannot be recovered at the end of the routine inspection. This alarm
clears when the file is recovered in the next routine inspection.
Attribute
Parameters
None.

A certain file of the package is missing and the NE may malfunction.
Possible Causes
Cause 1: A certain file is missing and cannot be recovered.

OptiX RTN 620
Procedure
Step 1 Cause 1: A certain file is missing and cannot be recovered.
(1) Ensure that the loaded software package is correct. Perform simulation package diffusion
again for the NE that reports the SWDL_NEPKGCHECK alarm.
----End
Related Information
None.
A.2.158 SWDL_PKG_NOBDSOFT
Description
The SWDL_PKG_NOBDSOFT is an alarm indicating that certain board software is missing in
the software package. This alarm is reported when the required software is missing in the
software package during the automatic match of the board.
Attribute
Parameters
None.

The board cannot perform automatic match, because the required board software is missing in
the software package. Therefore, the board software version is inconsistent with the NE software
version, and certain functions of the NE may be affected.
Possible Causes
Cause 1: Certain board software is not loaded during software package loading.
Procedure
Step 1 Cause 1: Certain board software is not loaded during software package loading.
(1) Add the required board software to the software package, Alternatively, perform software
package loading again.
----End
Related Information
None.

OptiX RTN 620
A.2.159 SWDL_PKGVER_MM
Description
The SWDL_PKGVER_MM is an alarm indicating that the consistency check on the software
package version fails. This alarm is reported when the consistency check on the software package
version fails.
Attribute

Parameters
None.

The software version of the simulation package is inconsistent with the software version
described in the software package. As a result, certain functions of the NE may be affected.
Possible Causes
Cause 1: The software version information in the description file of the software package is
inconsistent with the actual information about the software version.
Procedure
Step 1 Cause 1: The software version information in the description file of the software package is
inconsistent with the actual information about the software version.
(1) Ensure that the loaded software package is correct. Perform simulation package diffusion
again for the NE that reports the SWDL_PKGVER_MM alarm.
----End
Related Information
None.
A.2.160 SWDL_ROLLBACK_FAIL
Description
The SWDL_ROLLBACK_FAIL is an alarm indicating that an NE rollback fails. If a board
rollback fails when the NE rollback is being performed, this alarm is reported.

OptiX RTN 620
Attribute
Parameters
None.

The board software version fails to match the NE software version, and therefore certain
functions of the NE may be affected.
Possible Causes
Cause 1: Certain board software is not loaded during software package loading.
Procedure
Step 1 Cause 1: Certain board software is not loaded during software package loading.
(1) Add the required board software to the software package, Alternatively, perform software
package loading again.
----End
Related Information
None.
A.2.161 SYN_BAD
Description
The SYN_BAD is an alarm indicating that the quality of the synchronization source declines.
Attribute
Parameters
None.

The NE clock fails to be locked.

OptiX RTN 620
Possible Causes
l Cause 1: The quality of the synchronization source declines.
l Cause 2: The cross-connect unit is faulty.
Procedure
Step 1 Cause 1: The quality of the synchronization source declines.
(1) Take different measures based on the traced synchronization source.
If... Then...
The traced synchronization source is an Perform Steps Step 1.2 to Step 1.4.
external clock
The traced synchronization source is a line Replace the PXC board of the
clock upstream NE.
(2) Check whether the configuration of the external clock is correct.
If... Then...
The configuration is incorrect Change the configuration data.
The configuration is correct Go to the next step.
(3) Check whether the opposite equipment that provides the clock source is faulty.
If... Then...
The equipment functions normally Go to the next step.
(4) Check whether the cable that is connected to the external clock source is in normal status.
If... Then...
The cable is not in normal status Replace the cable.
The cable is in normal status Go to Cause 2.
Step 2 Cause 2: The cross-connect unit is faulty.

(1) Replace the PXC board.
----End
Related Information
None.
A.2.162 SYNC_C_LOS
Description
The SYNC_C_LOS is an alarm indicating that the synchronization source is lost.

OptiX RTN 620
Attribute
Warning Equipment alarm
Parameters
table.
Name Meaning
Parameter 1, Parameter 2 Indicate one lost clock source.
l If the line clock source is lost, the first parameter indicates the
slot ID of the clock source, and the second parameter indicates
the port ID of the clock source.
l If the external clock source is lost, "0xf0, 1" indicate external
clock 1, and "0xf0, 2" indicate external clock 2.

The performance of the NE clock declines, or even the NE clock enters the free-run mode.
Possible Causes
The clock source is lost.
Procedure
Step 1 Cause: The clock source is lost.
(1) Based on the alarm parameter, determine the lost clock source.
(2) Based on the clock source priority table, determine the synchronization source
corresponding to the lost clock source.
If... Then...
The synchronization source is an Handle the EXT_SYNC_LOS alarm.
external clock
The synchronization source is a line Handle the alarm that occurs on the line
clock board.
The synchronization source is an IF Handle the alarm that occurs on the IF board.
clock
The synchronization source is a Handle the alarm that occurs on the tributary
tributary clock board.
----End

OptiX RTN 620
Related Information
None.
A.2.163 T_ALOS
Description
The T_ALOS is an alarm indicating that analog signals are lost at the 2 Mbit/s interface.
Attribute

Parameters
table.
Name Meaning

2 Mbit/s services are interrupted.
Possible Causes
l Cause 1: The interface does not access 2 Mbit/s services.
l Cause 2: The opposite equipment is faulty.
l Cause 3: The trunk cable is faulty.
l Cause 4: The board that reports the alarm is faulty.
Procedure
Step 1 Cause 1: The interface does not access 2 Mbit/s services.
(1) Check whether the interface accesses 2 Mbit/s services.

OptiX RTN 620
If... Then...
The interface does not access services Enable the port to access services or delete
unnecessary services.
The interface accesses services Go to Cause 2.
Step 2 Cause 2: The opposite equipment is faulty.

(1) Check whether the opposite equipment is faulty.
If... Then...
The equipment runs normally Go to Cause 3.
Step 3 Cause 3: The trunk cable is faulty.

(1) Check whether the trunk cable is faulty.
If... Then...
The trunk cable is faulty Rectify the fault.
The trunk cable is in normal status Go to Cause 4.
Step 4 Cause 4: The board that reports the alarm is faulty.

----End
Related Information
None.
A.2.164 T_F_RST
Description
The T_F_RST is an alarm indicating that the transmit FIFO is reset.
Attribute
Parameters
table.

OptiX RTN 620
Name Meaning

Services in the PDH path are interrupted.
Possible Causes
l Cause 1: The frequency offset of the transmitted signal is large.
Procedure
Step 1 Cause 1: The frequency offset of the transmitted signal is large.
(1) Test the frequency offset of the transmitted signal.
If... Then...
The frequency offset is large Troubleshoot the opposite site.
The frequency offset meets the requirement Go to Cause 2.

----End
Related Information
None.
A.2.165 T_LOC
Description
The T_LOC is an alarm indicating that the clock is lost on the transmit line side.
Attribute
Parameters

OptiX RTN 620

table.
Name Meaning
Parameter 2, Parameter 3 Indicates the ID of the AU-4 path that reports the alarm. For
example, 0x00 0x01 indicate that the alarm is reported by AU-4
path 1 of the SDH signal.

Services in the AU-4 path that reports the alarm are interrupted.
Possible Causes
l Cause 1: The PXC board is faulty.
l Cause 2: The line board is faulty.
Procedure
Step 1 Cause 1: The PXC board is faulty.
(1) Replace the PXC board of the local site.
If... Then...
replaced handling.
replaced
Step 2 Cause 2: The line board is faulty.

(1) Replace the board that reports the alarm. For details, see 6.3 Replacing the SDH Optical
Interface Board or 6.4 Replacing the SDH Electrical Interface Board.
----End
Related Information
None.
A.2.166 T_LOS
Description
The T_LOS is an alarm indicating that signals are lost on the transmit line side.

OptiX RTN 620
Attribute
Parameters
table.
Name Meaning
SDH signal.

Services in the AU-4 path that reports the alarm are interrupted.
Possible Causes
l Cause 1: The SDH service configuration does not match the type of the line board.
l Cause 2: The PXC board is faulty.
l Cause 3: The line board is faulty.
Procedure
Step 1 Cause 1: The SDH service configuration does not match the type of the line board.
(1) Check the SDH service configuration.
If... Then...
The SDH service configuration does not The fault is rectified. End the alarm
match the type of the line board handling.
The SDH service configuration is correct Go to Cause 2.
Step 2 Cause 2: The PXC board is faulty.

If... Then...
replaced handling.

OptiX RTN 620
If... Then...
replaced
Step 3 Cause 3: The line board is faulty.

(1) Replace the line board that reports the alarm at the local site. For details, see 6.3 Replacing
the SDH Optical Interface Board or 6.4 Replacing the SDH Electrical Interface
Board.
----End
Related Information
None.
A.2.167 TEMP_ALARM
Description
The TEMP_ALARM alarm indicates that the board temperature crosses the threshold.
Attribute
Minor Environment alarm
Parameters
table.
Name Meaning
Parameter 1 l 0x01: The temperature crosses the upper threshold.
l 0x02: The temperature crosses the lower threshold.

The board fails to work normally.
Possible Causes
l Cause 1: The board temperature crosses the threshold.
l Cause 2: The temperature detection circuit of the board is faulty.

OptiX RTN 620
Procedure
Step 1 Cause 1: The board temperature crosses the threshold.
(1) If the alarm is reported by the ODU, take appropriate measures (for example, installing a
sunshade) to control the temperature.
(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...
The temperature control devices Adjust the temperature control devices.

malfunction
The temperature control devices work Go to the next step.

normally
(3) Check whether the heat dissipation hole on the IDU is covered or blocked.
If... Then...
The heat dissipation hole is covered or Clear or remove the covering materials or
blocked obstacles.
The heat dissipation hole is not covered or Go to the next step.

blocked
(4) Clear the alarm according to the type of the IDU.
If... Then...
The IDU is not equipped with a dust filter Clear the alarm according to the solution
for the alarm that is generated when the
temperature detection circuit of a board is
faulty.
The IDU is equipped with a dust filter Go to the next step.
(5) Clean the dust filter.
If... Then...
The alarm clears after the dust filter is End the alarm handling.
cleaned
The alarm persists after the dust filter is Clear the alarm according to the solution
cleaned for the alarm that is generated when the
temperature detection circuit of a board is
faulty.
Step 2 Cause 2: The temperature detection circuit of the board is faulty.

OptiX RTN 620
(1) If the ambient temperature is normal and no heat dissipation problem exists, replace the
board that reports the alarm.
----End
Related Information
None.
A.2.168 TU_AIS
Description
The AU_AIS is an indication of TU alarms. This alarm occurs when a board detects the TU path
of all 1s.
Attribute

Parameters
table.
Name Meaning

When the TU_AIS alarm occurs, the services in the alarmed TU path are interrupted. If the
services are configured with protection, the protection switching is also triggered.
Possible Causes
l Cause 2: The line is faulty.
l Cause 3: The board at the opposite end is faulty.
l Cause 4: The board at the local end is faulty.

OptiX RTN 620
Procedure
(1) Check whether the SDH service data is correct. For details, see Creating Cross-Connections
of Point-to-Point Services.
If... Then...
The SDH service data is incorrect Change the configuration data.
The SDH service data is correct Go to Cause 2.
Step 2 Cause 2: The line is faulty.

(1) Check whether a line alarm that causes AIS insertion is reported on the service trail.
NOTE
For details about the line alarms that cause AIS insertion, see E.2.6 AIS Insertion.
If... Then...
The line alarm is reported Change the configuration data.
No line alarms are reported Go to step 3.
Step 3 Locate whether the board at the local end or at the opposite end is faulty. For details, see 7.5
Software loopback.
If... Then...
The board at the opposite end is faulty Go to Cause 3.
The board at the local end is faulty Go to Cause 4.
Step 4 Cause 3: The board at the opposite end is faulty.

(1) In this case, replace the faulty board at the opposite end.
Step 5 Cause 4: The board at the local end is faulty.
(1) Replace the line board at the local site. For details, see 6.3 Replacing the SDH Optical
If... Then...
replaced handling.
replaced
If... Then...
replaced handling.
replaced

OptiX RTN 620
If... Then...
A tributary board reports the alarm Replace the PDH interface board.
An IF board reports the alarm Replace the IF board.
----End
Related Information
None.
A.2.169 TU_AIS_VC12
Description
The TU_AIS_VC12 is an indication of TU alarms at VC-12 level. This alarm occurs when a
board detects TU pointers of all 1s.
Attribute
Parameters
table.
Name Meaning
path 1 of the related board.

When the TU_AIS_VC12 alarm occurs, the services in the alarmed VC-12 path are interrupted.
If the service is configured with protection, the protection switching is also triggered.
Possible Causes

OptiX RTN 620
Procedure
(1) See Creating Cross-Connections of Point-to-Point Services to check whether the SDH
service data is incorrect.
If... Then...

NOTE
If... Then...
No line alarms are reported Go to step 3.
Step 3 Locate whether the board at the local end or at the opposite end is faulty. For details, see 7.5.5
Setting Loopback for the Ethernet Service Processing Board.
If... Then...

(1) In this case, replace the faulty board at the opposite end.

If... Then...
replaced handling.
replaced
If... Then...
replaced handling.

OptiX RTN 620
If... Then...
The alarm persists after the board is Replace the alarmed board.
replaced
----End
Related Information
None.
A.2.170 TU_AIS_VC3
Description
The TU_AIS_VC3 is a TU alarm indication at VC-3 level. This alarm occurs when a board
detects TU pointers of all 1s.
Attribute
Parameters
table.
Name Meaning

When the TU_AIS_VC3 alarm occurs, the services in the alarmed VC-3 path are interrupted. If
the services are configured with protection, the protection switching is triggered.
Possible Causes

OptiX RTN 620
Procedure
If... Then...

NOTE
If... Then...
No line alarms are reported Go to Step 3.
Step 3 Locate whether the board at the local end or at the opposite end is faulty. For details, see 7.5.5
If... Then...

(1) Replace the faulty board at the opposite end.
(1) Replace the line board at the local end. For details, see 6.3 Replacing the SDH Optical
If... Then...
replaced handling.
replaced
If... Then...
replaced handling.
The alarm persists after the board is Replace the alarmed board.
replaced
----End

OptiX RTN 620
Related Information
None.
A.2.171 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 is an invalid pointer or NDF reversion in eight consecutive frames.
Attribute

Parameters
table.
Name Meaning

Services in the TU path that reports the alarm are interrupted. If the services are configured with
protection, protection switching is also triggered.
Possible Causes
l Cause 2: The board at the opposite site is faulty.
l Cause 3: The board at the local site is faulty.
Procedure

OptiX RTN 620
If... Then...
The SDH service data is correct Go to Step 2.
Step 2 Locate whether the board at the local site or at the opposite site is faulty. For details, see 7.5
Software loopback.
If... Then...
The board at the opposite site is faulty Go to Cause 2.
The board at the local site is faulty Go to Cause 3.
Step 3 Cause 2: The board at the opposite site is faulty.

(1) In this case, replace the faulty board at the opposite site.
Step 4 Cause 3: The board at the local site is faulty.

If... Then...
replaced handling.
replaced
If... Then...
replaced handling.
replaced
If... Then...
----End
Related Information
None.
A.2.172 TU_LOP_VC12

OptiX RTN 620
Description
The TU_LOP_VC12 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 is an invalid pointer or NDF reversion
in eight consecutive frames.
Attribute
Parameters
table.
Name Meaning
example, 0x00 0x01 indicate that the alarm is reported in VC-12

Possible Causes
Procedure
If... Then...
Step 2 Locate whether the board at the local site or at the opposite site is faulty. For details, see 7.5.5

OptiX RTN 620
If... Then...

(1) In this case, replace the faulty board at the opposite site.
If... Then...
replaced handling.
replaced
If... Then...
replaced handling.
The alarm persists after the board is Replace the board that reports the
replaced alarm.
----End
Related Information
None.
A.2.173 TU_LOP_VC3
Description
The TU_LOP_VC3 is an alarm indicating that the VC-3 TU pointer is lost. This alarm is reported
if a board detects that the VC-3 TU-PTR value is an invalid pointer or NDF reversion in eight
consecutive frames.
Attribute
Parameters

OptiX RTN 620

table.
Name Meaning
0x00 0x01 indicate that the alarm is reported in VC-3 path 1.

Possible Causes
Procedure
If... Then...
Step 2 Locate whether the board at the local site or at the opposite site is faulty. For details, see 7.5
Software loopback.
If... Then...

(1) Replace the faulty board at the opposite site.

If... Then...
replaced handling.

OptiX RTN 620
If... Then...
replaced
If... Then...
replaced handling.
replaced
If... Then...
----End
Related Information
None.
A.2.174 UP_E1_AIS
Description
The UP_E1_AIS is an alarm indication of the 2 Mbit/s uplink signal. This alarm is reported
when the tributary board detects that the 2 Mbit/s uplink signal is all 1s.
Attribute

Parameters
table.
Name Meaning

OptiX RTN 620
Name Meaning

E1 signals are unavailable.
Possible Causes
l Cause 1: The opposite equipment transmits the AIS signal.
l Cause 2: The receive unit of the tributary board at the local site is faulty.
Procedure
Step 1 Cause 1: The opposite equipment transmits the AIS signal.
(1) Check whether the opposite equipment transmits the AIS signal.
If... Then...
The opposite equipment transmits the Rectify the fault on the opposite equipment.
AIS signal
The opposite equipment does not Go to Cause 2.
transmit the AIS signal
Step 2 Cause 2: The receive unit of the tributary board at the local site is faulty.
----End
Related Information
None.
A.2.175 VCAT_LOA
Description
The VCAT_LOA is an alarm indicating alignment loss of virtual concatenations. This alarm is
reported if a board detects that the time delays between the timeslots bound to a VCTRUNK are
out of the permissible limit.
Attribute


OptiX RTN 620
Parameters
table.
Name Meaning
Parameter 2, Parameter 3 Indicates the ID of the VCTRUNK that reports the alarm. For
example, 0x00 0x01 indicate that the alarm is reported in path 1.

The virtually concatenated services are interrupted.
Possible Causes
Cause 1: The timeslots bound to a VCTRUNK travel through different physical links, so the
delays between the virtually concatenated links are long.
Procedure
Step 1 Cause 1: The timeslots bound to a VCTRUNK travel through different physical links, so the
delays between the virtually concatenated links are long.
(1) Determine the ID of the VCTRUNK path that reports the alarm based on the alarm
parameter.
(2) Check whether the transmission routes of the paths bound to a VCTRUNK are the same.
If not, adjust their routes to the same.
----End
Related Information
None.
A.2.176 VCAT_LOM_VC12
Description
The VCAT_LOM_VC12 is an alarm indicating the loss of virtual concatenation multiframes in
the VC-12 path. This alarm is reported if the board detects that the K4 byte of the VC-12 path
does not match the expected multiframe sequence.

OptiX RTN 620
Attribute
Parameters
table.
Name Meaning
path 1.

The path that reports the alarm is unavailable. If the LCAS function is disabled, services are
interrupted.
Possible Causes
l Cause 1: Bit errors occur in the line.
l Cause 2: The MFI field in the K4 byte sent from the opposite site is incorrect.
l Cause 3: The delays between virtual concatenations are long.
Procedure
Step 1 Cause 1: Bit errors occur in the line.
(1) Check whether the bit error alarm BIP_EXC or BIP_SD occurs.
If... Then...
Such an alarm occurs Handle the alarm immediately.
No alarm occurs Go to Cause 2.
Step 2 Cause 2: The MFI field in the K4 byte sent from the opposite site is incorrect.
(1) Replace the board at the opposite site. For details, see 6.6 Replacing the Ethernet Service
Processing Board.
If... Then...

OptiX RTN 620
If... Then...
The alarm persists Go to Cause 3.
Step 3 Cause 3: The delays between virtual concatenations are long.

(1) Check whether the VCAT_LOA alarm is reported in this path.
If... Then...
The VCAT_LOA alarm is reported Handle the VCAT_LOA alarm immediately.
No VCAT_LOA alarm is reported Go to Cause 2.
(2) Check whether the VCAT_LOM_VC12 alarm clears after handling the VCAT_LOA
alarm.
If... Then...
The alarm persists Replace the board that reports the alarm at the local site. For details,
see 6.6 Replacing the Ethernet Service Processing Board.
----End
Related Information
None.
A.2.177 VCAT_LOM_VC3
Description
The VCAT_LOM_VC3 is an alarm indicating the loss of virtual concatenation multiframes in
the VC-3 path. This alarm is reported if the board detects that the H4 byte of the VC-3 path does
not match the expected multiframe sequence.
Attribute
Parameters
table.
Name Meaning

OptiX RTN 620
Name Meaning

interrupted.
Possible Causes
l Cause 1: Bit errors occur in the line.
l Cause 2: The MFI field in the K4 byte sent from the opposite site is incorrect.
l Cause 3: The delays between virtual concatenations are long.
Procedure
Step 1 Cause 1: Bit errors occur in the line.
(1) Check whether the bit error alarm BIP_EXC or BIP_SD occurs.
If... Then...
Such an alarm occurs Handle the alarm immediately.
No alarm occurs Go to Cause 2.
Step 2 Cause 2: The MFI field in the K4 byte sent from the opposite site is incorrect.
(1) Replace the board at the opposite site. For details, see 6.6 Replacing the Ethernet Service
Processing Board.
If... Then...
The alarm persists Go to Cause 3.
Step 3 Cause 3: The delays between virtual concatenations are long.

(1) Check whether the VCAT_LOA alarm is reported in this path.
If... Then...
The VCAT_LOA alarm is reported Handle the VCAT_LOA alarm immediately.
No VCAT_LOA alarm is reported Go to Cause 2.
(2) Check whether the VCAT_LOM_VC3 alarm clears after handling the VCAT_LOA alarm.
If... Then...

OptiX RTN 620
If... Then...
The alarm persists Replace the board that reports the alarm at the local site. For details,
see 6.6 Replacing the Ethernet Service Processing Board.
----End
Related Information
None.
A.2.178 VCAT_SQM_VC12
Description
The VCAT_SQM_VC12 is an alarm indicating the SQ number mismatch of a virtual
concatenation in the VC-12 path. This alarm is reported if the board detects that the SQ of a
virtual concatenation does not match the expected value.
Attribute
Parameters
table.
Name Meaning
path 1.

interrupted.
Possible Causes
l Cause 1: Bit errors occur on certain links or certain links are faulty.
l Cause 2: The SQ number sent from the opposite site is incorrect.

OptiX RTN 620
Procedure
Step 1 Cause 1: Bit errors occur on certain links or certain links are faulty.
(1) Check whether bit errors or line alarms occur. Focus on the bit error alarm BIP_EXC or
BIP_SD.
If... Then...
Bit errors or line alarms occur Clear these alarms.
No bit errors or line alarms occur Go to the next step.
Step 2 Cause 2: The SQ number sent from the opposite site is incorrect.
(1) Replace the corresponding board at the opposite site.
If... Then...
The alarm clears after the board is End the alarm handling.
replaced
The alarm persists after the board is Contact Huawei technical support engineers
replaced to handle the alarm.
----End
Related Information
None.
A.2.179 VCAT_SQM_VC3
Description
The VCAT_SQM_VC3 is an alarm indicating the sequence (SQ) number mismatch of a virtual
concatenation in the VC-3 path. This alarm is reported if the board detects that the SQ of a virtual
concatenation does not match the expected value.
Attribute
Parameters
table.

OptiX RTN 620
Name Meaning

interrupted.
Possible Causes
l Cause 1: Bit errors occur on certain links or certain links are faulty.
l Cause 2: The SQ number sent from the opposite site is incorrect.
Procedure
Step 1 Cause 1: Bit errors occur on certain links or certain links are faulty.
(1) Check whether bit errors or line alarms occur. Focus on the bit error alarm BIP_EXC or
BIP_SD.
If... Then...
Bit errors or line alarms occur Clear these alarms.
No bit errors or line alarms occur Go to the next step.
Step 2 Cause 2: The SQ number sent from the opposite site is incorrect.
(1) Replace the corresponding board at the opposite site.
If... Then...
The alarm clears after the board is End the alarm handling.
replaced
The alarm persists after the board is Contact Huawei technical support engineers
replaced to handle the alarm.
----End
Related Information
None.
A.2.180 VOLT_LOS
Description
The VOLT_LOS is an alarm indicating that the power voltage is unavailable.

OptiX RTN 620
Attribute
Parameters
table.
Name Meaning
Parameter 1 Indicates the type of the power that reports the alarm.
l 0x01: -48 V/+24 V power output
l 0x02: -48 V/+24 V power input
l 0x03: +5 V power output
l 0x04: +3.3 V power output
l 0x05: lightning

l If the alarm is reported by the PXC board, the power module that reports the alarm fail to
work. If the system is not configured with a protection power module, the system fails to
work normally.
l If the alarm is reported by the IF board, the ODU connected to the IF board fails to work.
Possible Causes
l Cause 1: The output power is abnormal.
l Cause 2: The input power is abnormal.
l Cause 3: Lightning occurs.
Procedure
Step 1 Determine the type of the power supply that reports the alarm based on the alarm parameter.
Step 2 Cause 1: The output power is abnormal.
(1) Clear the alarm according to the type of the power supply that reports the alarm.
If... Then...
The alarm is reported by the PXC board Replace the PXC board that reports the
alarm.
The alarm is reported by the IF board Go to the next step.
(2) Check the power switch of the ODU.

OptiX RTN 620
If... Then...
The power switch is turned off Turn on the power switch.
The power switch is turned on Go to the next step.
(3) Check the IF fiber jumper, IF cable, or ODU section by section for a short circuit.
If... Then...
A short circuit exists Replace the short-circuited component, and then replace the IF
board that reports the alarm.
No short circuit exists Replace the IF board that reports the alarm.
CAUTION
If the alarm is caused by a short circuit, replace the short-circuited cable or ODU, and then
replace the IF board. Otherwise, the new IF board may be damaged.
Step 3 Cause 2: The input power is abnormal.

(1) Clear the alarm according to the type of the power supply that reports the alarm.
If... Then...
The alarm is reported by the IF board Replace the IF board that reports the
alarm.
The alarm is reported by the PXC board Go to the next step.
(2) Check the configuration of the input power.
NOTE
The IDU 620 can be configured with two PXC boards to provide 1+1 protection of the input power.
If... Then...
No power being supplied to the input is Suppress the alarm for the board. For details,
considered normal see E.2.2 Alarm Suppression.
No power being supplied to the input is Go to the next step.
considered abnormal
(3) Check the power switch.
If... Then...
The power switch is turned off Turn on the power switch.
The power switch is turned on Contact the engineers for power supply to rectify the
fault.
Step 4 Cause 3: Lightning occurs.

(1) Contact the engineers for power supply to check the grounding lightning facilities.
----End

OptiX RTN 620
Related Information
None.
A.2.181 W_R_Failure
Description
The W_R_FAILURE is an alarm indicating a failure of reading or writing the chip register.
Attribute
Parameters
table.
Name Meaning
Parameter 1 Indicates the ID of the register.

Services in the path that reports the alarm are interrupted.
Possible Causes
Cause 1: The chip register is faulty or the read/write time sequence is incorrect.
Procedure
Step 1 Cause 1: The chip register is faulty or the read/write time sequence is incorrect.
----End
Related Information
None.
A.2.182 WRG_BD_TYPE

OptiX RTN 620
Description
The WRG_BD_TYPE is an alarm indicating that the type of the board is incorrect.
Attribute
Parameters
table.
Name Meaning
Parameter 1 Indicates the slot ID of the board whose type is incorrect.

The board fails to work.
Possible Causes
l Cause 2: The board of an incorrect type is installed.
Procedure
(1) Check whether the board type complies with the planning requirement. For details, see
Configuring Logical Boards.
If... Then...
The board type does not meet the planning Change the configuration data.
requirement
The board type meets the planning requirement Go to Cause 2.
Step 2 Cause 2: The board of an incorrect type is installed.

(1) Replace the board of an incorrect type. For details, see 6 Part Replacement.
----End
Related Information
None.

OptiX RTN 620
A.2.183 WRG_DEV_TYPE
Description
The WRG_DEV_TYPE is an alarm indicating that the type of the equipment is incorrect.
Attribute

Parameters
None.

The equipment fails to work.
Possible Causes
Cause 1: Configuration data is incorrect.
Procedure
(1) By using the method of creating an NE, change the type of the NE so that it is consistent
with the equipment type.
----End
Related Information
None.
A.2.184 WS_LOS
Description
The WS_LOS is an alarm indicating that the signals at the 2 Mbit/s wayside interface are lost.
Attribute


OptiX RTN 620
Parameters
table.
Name Meaning
Parameter 1 Indicates the ID of the wayside service that reports the alarm. For example, 0x01
indicates that the alarm is reported by wayside service 1.

Wayside services are interrupted.
Possible Causes
l Cause 1: The data of the wayside service is configured, but the service is not accessed.
l Cause 2: The cable of the wayside service is loose or damaged.
l Cause 3: The interconnected equipment of the wayside service is faulty.
Procedure
Step 1 Cause 1: The data of the wayside service is configured, but the service is not accessed.
(1) Check the configuration planning of the wayside service.
If... Then...
The wayside service needs to be Access the relevant service.

configured
The wayside service need not be Set the wayside service of the relevant IF
configured board to the disabled status. For details, see
Setting Parameters of IF Interfaces.
Step 2 Cause 2: The cable of the wayside service is loose or damaged.

(1) Check whether the connectors at the two ends of the wayside service cable are loose. If
yes, connect the cable properly.
(2) Test the connectivity of the wayside service cable. For details, see Testing Connectivity of
Cables. If the cable is damaged, replace the cable or prepare the connectors of the cable
again.
Step 3 Cause 3: The interconnected equipment of the wayside service is faulty.

(1) Check whether the interconnected equipment of the wayside service is faulty. If yes, rectify
the fault.

OptiX RTN 620
(1) If the preceding causes are excluded, replace the PXC board that reports the alarm.
----End
Related Information
None.
A.2.185 XCP_INDI
Description
The XCP_INDI is an alarm indicating that the working and protection PXC boards are switched.
Attribute
Parameters
table.
Name Meaning
Parameter 1 Indicates the slot ID of the working board.

During the protection switching (less than 50 ms), the VC-3/VC-12 services are interrupted.
Possible Causes
Protection switching occurs on the PXC board.
Procedure
Step 1 Cause: Protection switching occurs on the PXC board.
(1) Check whether the PXC board reports alarms. For details, see 7.3.3 Browsing the Current
Alarms.
If... Then...
The PXC board reports alarms Replace the PXC board.
The PXC board does not report any alarms Go to the next step.

OptiX RTN 620
(2) Check whether the manual switching command is run. If yes, clear the manual switching.
----End
Related Information
None.
A.2.186 XPIC_LOS
Description
The XPIC_LOS is an alarm indicating that XPIC compensation signals are lost.
Attribute
Parameters
table.
Name Meaning
that the alarm is reported by IF port 1 of the corresponding board.

Bit errors may occur in the service at the port, and the service may even be interrupted.
Possible Causes
l Cause 2: The radio link is faulty.
l Cause 3: The XPIC cable is faulty.
l Cause 4: The IF board or ODU is faulty.
Procedure
(1) Check whether the XPIC function needs to be enabled. If the XPIC function need not be
enabled, see Setting Parameters of IF Interfaces and set the XPIC function to the disabled
status, and then perform a self-loop at the XPIC port on the board by using the XPIC cable.

OptiX RTN 620
Step 2 Cause 2: The radio link is faulty.

(1) Check whether the paired board that is connected to the IFX2 board through the XPIC cable
reports the MW_LOF alarm. If yes, clear the MW_LOF alarm.
Step 3 Cause 3: The XPIC cable is faulty.
(1) Check the connection of the XPIC cable.
If... Then...
The cable is connected incorrectly Connect the XPIC cable properly.
The cable is properly connected Go to the next step.
(2) Test the connectivity of the XPIC cable by using the multimeter. If the XPIC cable is
damaged, replace it.
Step 4 Cause 4: The IF board or ODU is faulty.
In the case, locate the fault by replacing the IF board or ODU.
(1) Replace the paired board of the IFX board.
The paired board of the IFX2 board refers to the other IFX2 board that is connected to the
IFX2 board that reports the alarm through the XPIC cable.
If... Then...
The alarm clears after the board is replaced End the alarm handling.

replaced
(2) Replace the ODU that is connected to the paired IFX board.
If... Then...
The alarm clears after the ODU is replaced End the alarm handling.
The alarm persists after the ODU is Replace the paired board of the IFX
replaced board.
----End
Related Information
None.

OptiX RTN 620
Maintenance Guide B Abnormal Event Reference
B Abnormal Event Reference
An abnormal event is an important indicator when a fault occurs on the equipment. This topic
describes all the possible important abnormal events of the OptiX RTN 620 and how to handle
these events.
B.1 Important Abnormal Events

Important abnormal events include protection switching events and RMON alarms.
B.2 Important Abnormal Events and Handling Procedures
This topic describes all the important abnormal performance events of the OptiX RTN 620 in
alphabetic order and how to handle these events.
Issue 01 (2009-12-30) Huawei Proprietary and Confidential B-1

OptiX RTN 620
B Abnormal Event Reference Maintenance Guide
B.1 Important Abnormal Events

Important abnormal events include protection switching events and RMON alarms.
Table B-1 Important abnormal events

Event Name Source
IF 1+1 Protection Switching IF1A, IF1B, IF0A, IF0B, IFX, and IFH2
N+1 Protection Switching SCC
SNCP Protection Switching SCC
MSP Switching SCC
Linear MSP Switching SCC
Cross-Connect and Timing Board PXC

Switching
ERPS Event EMS6
RMON Performance Value Below the EMS6, EFT4, IFH2, and EFP6
Lower Limit
RMON Performance Value Above the EMS6, EFT4, IFH2, and EFP6
Upper Limit
NOTE
All alarmed boards refer to the logical boards that are displayed on the NMS.
B.2 Important Abnormal Events and Handling Procedures

This topic describes all the important abnormal performance events of the OptiX RTN 620 in
alphabetic order and how to handle these events.
B.2.1 IF 1+1 Protection Switching

B.2.2 N+1 Protection Switching
B.2.3 SDH SNCP Protection Switching
B.2.4 Ring MS Switching
B.2.5 Linear MS Switching
B.2.6 Cross-Connect and Timing Board Switching
B.2.7 ERPS Protection Switching
B.2.8 RMON Performance Value Below the Lower Limit
B.2.9 RMON Performance Value Above the Upper Limit
B-2 Huawei Proprietary and Confidential Issue 01 (2009-12-30)

OptiX RTN 620
B.2.1 IF 1+1 Protection Switching

Description
This abnormal event indicates that 1+1 HSB, 1+1 FD, or 1+1 SD switching occurs on the
equipment.
Attribute
Severity Type
Major Service
Parameters
Name Meaning
Protection Group ID Indicates the ID of the protection group where

an IF 1+1 protection switching occurs.
Slot ID of Working Board Indicates the slot ID of the current working

board.
Current Working Board Indicates the current working board.

l 0: main board
l 1: standby board
Main Board State Indicates the current state of the main board.
l Normal
l Failed
l MW_RDI
Standby Board State Indicates the current state of the standby

board.
l Normal
l Failed
l MW_RDI

OptiX RTN 620
Name Meaning
Switching Request Type Indicates the type of an IF 1+1 protection

switching request.
l No request
l Automatic switching
l Manual switching
l Forced switching
l Lockout of switching
l Wait-to-restore
l RDI switching
Impact on System
l During HSB protection switching, the services are interrupted. After the switching is
completed, the services are restored to normal.
l During HSM protection switching, no bit errors occur and the services are not affected.
When the AM function is enabled, the protection path works in modulation mode for
ensuring capacity after HSM switching is completed. Hence, the services of lower priorities
are impaired.
Relevant Alarms
When IF 1+1 protection switching occurs, the RPS_INDI alarm is reported.
Possible Causes
l The possible causes of the HSB protection switching are as follows:
– The hardware of the ODU or IF unit at the local end is faulty.
– The working path at the local end receives the MW_RDI alarm.
– An external switching, which is triggered by the switching command that is issued from
the NMS software, occurs. The external switching includes lockout of switching, forced
switching, and manual switching.
l The possible causes of HSM protection switching are as follows:
– The radio link in the receive direction of the local end is faulty.
– An external switching, which is triggered by the switching command that is issued from
the NMS software, occurs. The external switching includes lockout of switching, forced
switching, and manual switching.
Procedure
Step 1 Rectify the fault according to the switching request type indicated by the parameter and the
description in RPS_INDI.
----End

OptiX RTN 620
B.2.2 N+1 Protection Switching

Description
This abnormal event indicates that N+1 protection switching occurs on the equipment.
Attribute
Severity Type
Major Service
Parameters
Name Meaning

an IF N+1 protection switching occurs.
Path ID Indicates the ID of the path where an IF N+1

protection switching occurs.
Switching Request Type Indicates the type of an IF N+1 protection

switching request.
l Lockout of protection channel
l Forced switching
l SF switching
l SD switching
l Manual switching
l Wait-to-restore
l Exercise
l Reverse request
l No request
N+1 Protection Group State Indicates the state of an N+1 protection

group.
l Protocol unstarted
l Idle status
l Switching status
l Protocol starting
N+1 Switching Local/Remote End Indication Indicates the local or remote switching.
l Local end
l Remote end

OptiX RTN 620
Name Meaning
N+1 Switching Cause Indicates the cause of an IF N+1 protection

switching.
l Local request
l External command
l K-byte request
l Timer expiry
Impact on System
During the N+1 protection switching time (not more than 50 ms), the services are interrupted.
After the switching is completed, the services are restored to normal. After the switching starts
and before the switching is completed, the extra services are interrupted.
NOTE
If an IF N+1 protection switching is caused by exercise switching, service signals are not switched actually
because the exercise switching is used to check whether the NE can run the N+1 protocol normally.
Relevant Alarms
When an IF N+1 protection switching occurs, the NP1_SW_INDI alarm is reported.
Possible Causes
l An external switching occurs.
– Lockout of protection channel
– Forced switching
– Manual switching
l An automatic switching occurs.
– The hardware of the IDU or IF board is faulty. Focus on checking whether the
HARD_BAD or BD_STATUS alarm is reported.
– The MW_LOF, R_LOC, R_LOF, R_LOS, MS_AIS, or B2_EXC alarm is reported
on the working path.
Procedure
Step 1 Rectify the fault according to the switching request type and the switching cause indicated by
the parameters.
If... Then...
The switching is caused by an external Find the cause of the external switching, and
switching then release the external switching
immediately.
The switching is caused by an automatic Clear the alarm that triggers the automatic
switching switching.
----End

OptiX RTN 620
B.2.3 SDH SNCP Protection Switching

Description
This abnormal event indicates that an SDH SNCP switching occurs in the service that is
configured with the SNCP scheme.
Attribute
Severity Type
Major Service
Parameters
Name Meaning
Protection Group ID Indicates the protection group ID of the

service where SNCP switching occurs.
Switching Request Indicates the type of an SNCP switching

request.
l Lockout of protection channel
l Forced switching
l Manual switching
l Signal failure
l Signal degradation
l Wait-to-restore
l No request
Current Working Path Indicates the current working path.

l Main path
l Standby path
SNCP Working Path Status Indicates the current status of the SNCP
working path.
l Normal
l SD
l SF
SNCP Protection Path Status Indicates the current status of the SNCP
protection path.
l Normal
l SD
l SF

OptiX RTN 620
Impact on System
When an SNCP switching occurs, you must find the cause. If the relevant link is faulty, recover
the link immediately. Ensure that the SNCP working and protection paths are in normal state.
Possible Causes
l The switching is triggered automatically.
– The hardware of the line board is faulty.
– The R_LOS, R_LOF, R_LOC, MS_AIS, B2_EXC, AU_LOP, AU_AIS,
HP_LOM, MW_LOF (only when the IF board functions as the line board),
MW_LIM (only when the IF board functions as the line board), B3_EXC, B3_SD,
HP_TIM (in the case of VC-4 services), HP_UNEQ (in the case of VC-4 services),
TU_AIS (in the case of VC-12 services) or TU_LOP (in the case of VC-12 services)
alarm is reported.
l The switching is triggered manually.
– Forced switching
– Manual switching
Procedure
Step 1 On the NMS, query the type of the SDH SNCP switching request.
Step 2 Rectify the fault according to the switching request type.
If... Then...
The SDH SNCP switching is triggered Rectify the fault according to the relevant
automatically alarm, and eliminate the conditions of the
automatic switching.
The SDH SNCP switching is triggered Find the cause of the manual switching, and
manually then release the manual switching
immediately.
----End
B.2.4 Ring MS Switching
Description
This abnormal event indicates that a ring MSP switching occurs on the equipment that is
configured with services.
Attribute
Severity Type
Major Service

OptiX RTN 620
Parameters
Name Meaning

a ring MSP switching occurs.
Westward Protection Switching Type Indicates the type of a ring MSP switching
Eastward Protection Switching Type request.
l Clear all
l Lock out protection channel
l Unlock protection channel
l Forced switching
l Clear forced switching
l Manual switching
l Clear manual switching
l Exercise
l Clear exercise switching
Westward Switching State Indicates the switching state.

Eastward Switching State l Protocol being started
l Idle
l Switching
l Pass-through state
Eastward Switching Flag Indicates the flag when switching occurs.

Westward Switching Flag l No switching or full pass-through is
performed for the service
l The switching or full pass-through is
performed for the service
Impact on System
l During the switching time (not more than 50 ms), the services are interrupted. After the
switching is completed, the services are restored to normal. After the switching starts and
before the switching is completed, the extra services are interrupted.
l When a ring MSP switching occurs, a fiber cut may occur or the terminal node may be
faulty. In this case, you must rectify the fault immediately.
l If a fiber cut or another fault occurs on a two-fiber ring MS, the services are interrupted.
Relevant Alarms
When a ring MSP switching occurs, the APS_INDI alarm may be reported.

OptiX RTN 620
Possible Causes
l External switching such as manual switching, forced switching, or exercise switching
occurs.
– The hardware or line is faulty. Focus on the HARD_BAD and BD_STATUS alarms.
– After the R_LOS, R_LOF, MS_AIS, B2_EXC, B2_SD, B3_EXC, B3_SD,
HP_TIM (in the case of VC-4 services), HP_UNEQ (in the case of VC-4 services),
TU_AIS (in the case of VC-3 or VC-12 services), or TU_LOP (in the case of VC-3 or
VC-12 services) alarm is reported on the working path, the MSP group changes to the
switching state, and an automatic switching alarm is reported.
Procedure
Step 1 On the NMS, query the switching type and the protection group ID.
If... Then...
switching then clear manual switching immediately.
The switching is caused by an automatic Clear the relevant alarm, and rectify the fault
switching that occurs on the hardware or line immediately.
----End
B.2.5 Linear MS Switching

Description
This abnormal event indicates that a linear MSP switching occurs on the equipment that is
configured with services.
Attribute
Severity Type
Major Service
Parameters
Name Meaning

a linear MSP switching occurs.

OptiX RTN 620
Name Meaning
Current Working Path Indicates the current working path of the

linear MS.
l Working path
l Protection path
Linear MSP Switching Request Indicates the type of a linear MSP switching
request.
l Lock out protection path
l Forced switching
l Switch upon signal failure
l Switch upon signal degradation
l Manual switching
l Wait-to-restore
l Exercise
l Reverse request
l Non-revertive request
l Not requested
Switching Status Indicates the switching state.

l Protocol not started
l Idle
l Switching
l Protocol being started
Remote/Local End Indication Indicates the remote or local end.

l No remote/local end
l Local end
l Remote end
Cause for Switching Status Change Indicates the cause of changing the switching
state.
l Local request
l External command
l K-byte request
l Timer timeout
Impact on System
l During the switching time (not more than 50 ms), the services are interrupted. After the
switching is completed, the services are restored to normal. After the switching starts and
before the switching is completed, the extra services are interrupted.

OptiX RTN 620
l When a linear MSP switching occurs, a fiber cut may occur or the terminal node may be
faulty. In this case, you must rectify the fault immediately.
Relevant Alarms
When a linear MSP switching occurs, the APS_INDI alarm may be reported.
Possible Causes
l An external switching command such as manual, forced, or excise switching command is
issued.
After the R_LOS, R_LOF, MS_AIS, B2_EXC, B2_SD, B3_EXC, B3_SD, HP_TIM (in
the case of VC-4 services), HP_UNEQ (in the case of VC-4 services), TU_AIS (in the
case of VC-3 or VC-12 services), or TU_LOP (in the case of VC-3 or VC-12 services)
alarm is reported, the MSP group changes to the switching state, and an automatic switching
alarm is reported.
l The hardware or line is faulty.
Procedure
Step 1 On the NMS, query the switching type and the protection group ID.
If... Then...
switching then clear manual switching immediately.
The switching is caused by an automatic Clear the relevant alarm, and rectify the
switching hardware or line fault immediately.
----End
B.2.6 Cross-Connect and Timing Board Switching
Description
This abnormal event indicates that the cross-connect and timing boards are switched when the
working cross-connect and timing board on the equipment that is configured with the 1+1
protection scheme is faulty.
Attribute
Severity Type
Major Service

OptiX RTN 620
Parameters
Name Meaning
Working Board ID Indicates the slot ID of the current working

board.
Protection Board ID Indicates the slot ID of the current protection

board.
Impact on System
When a fault occurs on the protection cross-connect and timing board, you must find the
switching cause. If the protection cross-connect and timing board is faulty, rectify the fault
immediately. Otherwise, the services are interrupted when a fault occurs on the current working
cross-connect and timing board.
Possible Causes
l The switching is triggered.
l The switching is triggered manually.
The hardware of a board is faulty. Focus on the BD_STATUS, VOLT_LOS and
HARD_BAD alarms reported by the original working board.
Procedure
Step 1 On the NMS, check whether the cross-connect and timing board reports a relevant alarm that is
triggered automatically.
If... Then...
The cross-connect and timing board Clear the alarm immediately according to the
reports a relevant alarm clearance method of the relevant alarm.
The cross-connect and timing board does Go to the next step.
not report a relevant alarm
Step 2 Check whether the hardware of the cross-connect and timing board is faulty.
If... Then...
The hardware of the cross-connect and Replace the cross-connect and timing board
timing board is faulty according to the descriptions in the Part
Replacement.
The hardware of the cross-connect and Clear manual switching.
timing board is not faulty
----End

OptiX RTN 620
B.2.7 ERPS Protection Switching
Description
This abnormal event indicates that Ethernet ring protection switching (ERPS) occurs on the
equipment. When the state of a ring network is changed, an ERPS event is reported by a node.
Attribute
Severity Type
Major Service
Parameters
Name Meaning
Ethernet Protection Protocol Instance ID Indicates the ID of the protection group where
an ERPS event occurs.
Switching Request Type Indicates the type of a switching request.

l 0x01: The R-APS (NR) packet is received
at the local end.
l 0x02: The R-APS (NR or RB) packet is
received at the local end.
l 0x03: WTR running
l 0x04: WTR expires
l 0x05: The R-APS (SF) packet is received
at the local end.
l 0x06: Local SF
l 0x07: Local clear SF
l 0x08: Initial request
Switching State Indicates the switching state.

l Idle
l Protection
Impact on System
During the ERPS switching time (<100 ms), the services are interrupted. After the switching is
completed, the services are restored to normal.
Relevant Alarms
None.

OptiX RTN 620
Possible Causes
l The link is faulty.
l The R-APS packet is received at the local end.
Procedure
----End
B.2.8 RMON Performance Value Below the Lower Limit

Description
This abnormal event indicates that the current RMON performance value is lower than the preset
lower limit.
Attribute
Severity Type
Major Service
Parameters
Name Meaning
Performance ID Indicates the ID of the current RMON

performance event.
Current Performance Value Indicates the value of the current RMON

performance event.
Lower Limit Indicates the lower limit of the current

RMON performance event.
Impact on System
Different abnormal performance events have different impacts on the system. For details, see
List of RMON Alarm Entries.
Relevant Alarms
Different alarms are reported when different RMON performance values are lower than the
lower limits. For details, see D.3 RMON Alarm Clearance Reference.
Possible Causes
The lower limit of a performance event is set to a non-zero value.

OptiX RTN 620
Procedure
Step 1 Set the lower limit of the performance event to zero.
----End
B.2.9 RMON Performance Value Above the Upper Limit
Description
This abnormal event indicates that the current RMON performance value is higher than the preset
upper limit.
Attribute
Severity Type
Major Service
Parameters
Name Meaning
Performance ID Indicates the ID of the current RMON

performance event.
Current Performance Value Indicates the value of the current RMON

performance event.
Upper Limit Indicates the upper limit of the current

RMON performance event.
Impact on System
Different abnormal performance events have different impacts on the system. For details, see
List of RMON Alarm Entries.
Relevant Alarms
Different alarms are reported when different RMON performance values are higher than the
upper limits. For details, see D.3 RMON Alarm Clearance Reference.
Possible Causes
When the performance values of different abnormal RMON performance events are higher than
the upper limits, the causes are different from each other. For details, see D RMON Event
Reference.

OptiX RTN 620
Procedure
Step 1 See D.3 RMON Alarm Clearance Reference to handle different abnormal performance events.
----End

OptiX RTN 620
Maintenance Guide C Performance Event Reference
C Performance Event Reference
Performance events are important indicators when the equipment performance changes. This
topic describes all the possible performance events on the OptiX RTN 620 and how to handle
these performance events.
C.1 Performance Event List

Performance events are categorized on the basis of the performance event type, and include all
the events of the OptiX RTN 620.
C.2 Performance Events and Handling Procedures
Based on the type of a performance event, this topic describes all the performance events on the
OptiX RTN 620 and how to handle these performance events.
Issue 01 (2009-12-30) Huawei Proprietary and Confidential C-1

OptiX RTN 620
C Performance Event Reference Maintenance Guide
C.1 Performance Event List

Performance events are categorized on the basis of the performance event type, and include all
the events of the OptiX RTN 620.
C.1.1 SDH/PDH Performance Events

SDH/PDH performance events are classified into five categories: pointer justification,
regenerator section error, multiplex section error, higher order path error, and lower order path
error.
C.1.2 Microwave Performance Events
Microwave performance events include the performance events regarding the microwave power,
FEC, and radio link bit errors.
C.1.3 Other Performance Events
In addition to the SDH and microwave performance events, the OptiX RTN 620 supports
performance events regarding the optical power and temperature.
C.1.1 SDH/PDH Performance Events

SDH/PDH 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 C-1 Pointer justification performance events

Event Name Description Source
AUPJCHIGH Indicates the count of SL1, SD1, SLE, SDE, SL4,

positive AU pointer IF1A, IF1B, and IFX
justifications.
AUPJCLOW Indicates the count of

negative AU pointer
justifications.
AUPJCNEW Indicates the count of new

AU pointer justifications.
TUPJCHIGH Indicates the count of PH1, PO1, PD1, and PL3

positive TU pointer
justifications.
TUPJCLOW Indicates the count of

negative TU pointer
justifications.
TUPJCNEW Indicates the count of new

TU pointer justifications.
C-2 Huawei Proprietary and Confidential Issue 01 (2009-12-30)

OptiX RTN 620
Table C-2 Regenerator section error performance events

RSBBE Indicates the regenerator SD1, SL1, SDE, SLE, IF1A,

section block of background IF1B, IFX, IF0A, IF0B, and
error. SL4
RSES Indicates the errored second

of the RS.
RSSES Indicates the severely errored

seconds of the RS.
RSUAS Indicates the unavailable

second of the RS.
RSCSES Indicates RS consecutive

severe error seconds.
RSOFS Indicates the regenerator

section out-of-frame second.
RSOOF Indicates the regenerator

section of OOF performance
seconds.
NOTE
In the case of PDH radio, regenerator section bit error performance events also exist and they are detected
according to the overheads used for detecting frame alignment and bit errors in the PDH microwave frames.
Table C-3 Multiplex section error performance events

MSBBE Indicates the background SD1, SL1, SDE, SLE, IF1A,

block error of the multiplex IF1B, IFX, and SL4
section (MS).
MSES Indicates the errored second

of the MS.
MSSES Indicates the errored second

of the MS.
MSCSES Indicates the consecutively

and severely errored seconds
of the MS.
MSUAS Indicates the unavailable

second of the MS.

OptiX RTN 620
MSFEBBE Indicates the multiplex

section far end block of
background error.
MSFEES Indicates MS far end errored

second.
MSFESES Indicates the multiplex

section far end severely
errored second.
MSFECSES Indicates the multiplex

section far end consecutive
severely errored second.
MSFEUAS Indicates the multiplex

section far end unavailable
second.
Table C-4 Higher order path error performance events

HPBBE Indicates the higher order SD1, SL1, SDE, SLE, IF1A,
path background block error. IF1B, IFX, and SL4
HPES Indicates the higher order

path errored second.
HPSES Indicates the higher order

path severely errored second.
HPCSES Indicates the higher order

path consecutive severely
errored second.
HPUAS Indicates the higher order

path unavailable second.
HPFEBBE Indicates the higher order

path far end background
block error.
HPFEES Indicates the higher order

path far end errored second.
HPFESES Indicates the higher order

path far end severely errored
second.

OptiX RTN 620
HPFECSES Indicates the higher order

path far end consecutive
HPFEUAS Indicates the higher order

path far end unavailable
second.
Table C-5 VC-3 path error performance events

VC3BBE Indicates the VC-3 EFT4

background block error.
VC3ES Indicates the VC-3 errored

second.
VC3SES Indicates the VC-3 severely

errored second.
VC3CSES Indicates the VC-3

consecutive severely errored
second.
VC3UAS Indicates the VC-3

unavailable second.
VC3FEBBE Indicates the VC-3 far end

block of the background
error.
VC3FEES Indicates the VC-3 far end

errored second.
VC3FESES Indicates the VC-3 far end

second.
VC3FECSES Indicates the VC-3 far end

second.
VC3FEUAS Indicates the VC-3 far end

unavailable second.

OptiX RTN 620
Table C-6 Lower order path error performance events

LPBBE Indicates the lower order path PO1, PH1, PD1, PL3, EFT4,
block of background error. EMS6, IF0A, IF0B, and
EFP6
LPES Indicates the lower order path
errored second.
LPSES Indicates the lower order path

LPCSES Indicates the lower order path

second.
LPUAS Indicates the lower order path

unavailable second.
LPFEBBE Indicates the lower order path

far end block of background
error.
LPFEES Indicates the lower order path

far end errored second.
LPFESES Indicates the lower order path

far end severely errored
second.
LPFECSES Indicates the Lower order

path far end consecutive
LPFEUAS Indicates the lower order far PO1, PH1, PD1, PL3, EFT4,
end unavailable second. IF0A, and IF0B
Table C-7 Line side code violation performance events

E3_LCV_SDH Indicates the E3 line side PL3

code violation count.
E3_LES_SDH Indicates the E3 line side

code violation errored
second.
E3_LSES_SDH Indicates the E3 line side

code violation severely
errored second.
T3_LCV_SDH Indicates the T3 line side

code violation count.

OptiX RTN 620
T3_LES_SDH Indicates the T3 line side

code violation errored
second.
T3_LSES_SDH Indicates the T3 line side

code violation severely
errored second.
NOTE
C.1.2 Microwave Performance Events

Microwave performance events include the performance events regarding the microwave power,
FEC, and radio link bit errors.
Table C-8 Microwave power performance events
TSL_MAX Indicates the maximum radio ODU

transmit signal level.
TSL_MIN Indicates the minimum radio

TSL_CUR Indicates the current radio

TSL_AVG Indicates the average radio

RSL_MAX Indicates the maximum radio

received signal level.
RSL_MIN Indicates the minimum radio

RSL_CUR Indicates the current radio

RSL_AVG Indicates the average radio

TLHTT Indicates the duration when

the transmit power is higher
than the upper threshold.
TLLTT Indicates the duration when

the transmit power is higher
than the lower threshold.

OptiX RTN 620
RLHTT Indicates the duration when

the receive power is lower
RLLTT Indicates the duration when

the receive power is lower
Table C-9 FEC performance events

FEC_BEF_COR_ER Indicates the BER before the IF1A, IF1B, IF0A, IF0B,
FEC is performed. IFX, and IFH2
FEC_COR_BYTE_CNT Indicates the number of bytes IF1A, IF1B, IF0A, IF0B, and
that are corrected through the IFX
FEC.
FEC_UNCOR_BLOCK_C Indicates the number of IFH2

NT frames that cannot be
corrected through the FEC.
Table C-10 Performance events regarding radio link bit errors

IF_BBE Indicates the radio link IF0A, IF0B,and IFH2

background block error.
IF_ES Indicates the radio link

errored second.
IF_SES Indicates the radio link

IF_UAS Indicates the radio link

unavailable second.
IF_CSES Indicates the radio link

consecutively severely
errored second.

OptiX RTN 620
Table C-11 ATPC performance events

ATPC_P_ADJUST Indicates the positive ATPC ODU

adjustment event.
ATPC_N_ADJUST Indicates the negative ATPC

adjustment event.
Table C-12 AM performance events

QPSKWS Indicates the working IFH2

duration of the QPSK mode.
QAMWS16 Indicates the working

duration of the 16QAM
mode.

mode.

mode.

mode.

mode.
ACMDOWNCNT Indicates the count of the

downshift of the AM scheme.
ACMUPCNT Indicates the count of the

upshift of the AM scheme.
NOTE
C.1.3 Other Performance Events

In addition to the SDH and microwave performance events, the OptiX RTN 620 supports
performance events regarding the optical power and temperature.

OptiX RTN 620
Table C-13 Performance events regarding optical power
TPLMAX Indicates the maximum SD1, SL1, SL4, and EMS6

transmit power of the optical
port on the laser.
TPLMIN Indicates the minimum

transmit power of the optical
port on the laser.
TPLCUR Indicates the current transmit

power of the optical port on
the laser.
RPLMAX Indicates the maximum

receive power of the optical
port on the laser.
RPLMIN Indicates the minimum

receive power of the optical
port on the laser.
RPLCUR Indicates the current receive

power of the optical port on
the laser.
Table C-14 Performance events regarding board temperature
BDTEMPMAX Indicates the maximum IF1A, IF1B, IFX, IF0A,

board temperature. IF0B, PXC, ODU, SCC,
EFT4, EMS6, and EFP6
BDTEMPMIN Indicates the minimum board
temperature.
BDTEMPCUR Indicates the current board

temperature.
Table C-15 Performance events regarding temperature of a laser core
OSPITMPMAX Indicates the maximum EMS6

temperature of a laser core.
OSPITMPMIN Indicates the minimum

OSPITMPCUR Indicates the current


OptiX RTN 620
NOTE
C.2 Performance Events and Handling Procedures

Based on the type of a performance event, this topic describes all the performance events on the
OptiX RTN 620 and how to handle these performance events.
C.2.1 AUPJCHIGH, AUPJCLOW, and AUPJCNEW
Description
l AUPJCHIGH indicates the count of positive AU pointer justifications.
l AUPJCLOW indicates the count of negative AU pointer justifications.
l AUPJCNEW indicates the count of new AU pointer justifications.
Attribute
Attribute Description
Performance event cell PPJE (AUPJCHIGH)

NPJE (AUPJCLOW)
NDF (AUPJCNEW)
Unit Block
Impact on System
If the number of TUPJCHIGH and TUPJCLOW events is less than six, the system is not affected.
If the pointer is justified for more than six times, or if the TUPJCNEW event is generated, bit
errors may occur in the service.
Relevant Alarms
When the number of TUPJCHIGH, TUPJCLOW, or TUPJCNEW events exceeds the specified
threshold, the MSAD_CROSSTR alarm is reported.
Performance Event Default Threshold in 15- Default Threshold in 24-

Minute Monitoring Hour Monitoring
AUPJCHIGH 1500 30000
AUPJCLOW 1500 30000
AUPJCNEW 1500 30000

OptiX RTN 620
Possible Causes
The NE clock is out-of-synchronization.
Procedure
Step 1 See 5.9 Troubleshooting Pointer Justifications.
----End
C.2.2 ATPC_P_ADJUST and ATPC_N_ADJUST
Description
l ATPC_P_ADJUST indicates the positive ATPC adjustment event.
This performance event indicates that the quality of a communications link degrades.
Therefore, you must increase the transmit power of the ODU to maintain the
communication quality.
l ATPC_N_ADJUST indicates the negative ATPC adjustment event.
This performance event indicates that the quality of a communication link becomes well
or the transmit power of the ODU is very large. Therefore, you can decrease the transmit
power of the ODU.
Attribute
Performance event cell ATPCPADJUST (ATPC_P_ADJUST) and

ATPCNADJUST (ATPC_N_ADJUST)
Unit None
Impact on System
The ATPC adjustment indicates only the stability of a communication link and it does not affect
services. When the value of the performance event is larger, more adjustments are made.
When the factors that affect a communication link, such as sudden change of the weather, do
not exist, and when the ATPC adjustment count is very large, the communication link may be
faulty. You must check the communication link to prevent it from failure.
Relevant Alarms
None.
C.2.3 TUPJCHIGH, TUPJCLOW, and TUPJCNEW
Description
l TUPJCHIGH indicates the count of positive TU pointer justifications.

OptiX RTN 620
l TUPJCLOW indicates the count of negative TU pointer justifications.

l TUPJCNEW indicates the count of new TU pointer justifications.
Attribute
Performance event cell TUPPJE (TUPJCHIGH)

TUNPJE (TUPJCLOW)
TUNDF (TUPJCNEW)
Unit Block
Impact on System
If the number of TUPJCHIGH and TUPJCLOW events is less than six, the system is not affected.
If the pointer is justified for more than six times, or if the TUPJCNEW event is generated, bit
errors may occur in the service.
Related Alarms
When the number of TUPJCHIGH, TUPJCLOW, or TUPJCNEW events exceeds the specified
threshold, the HPAD_CROSSTR alarm is reported.

TUPJCHIGH 1500 30000
TUPJCLOW 1500 30000
TUPJCNEW 1500 30000
Possible Causes
The NE clock is out-of-synchronization.
Procedure
Step 1 See 5.9 Troubleshooting Pointer Justifications.
----End
C.2.4 RSBBE, RSES, RSSES, RSCSES, and RSUAS
Description
l RSBBE indicates the regenerator section background block error.

OptiX RTN 620
A BBE refers to the errored block excluding the errored block in the unavailable and
l RSES indicates the regenerator section errored second.
An ES refers to a second in which one or more errored blocks are detected.
l RSSES indicates the regenerator section severely errored second.
An SES refers to a second in which 30% or more than 30% errored blocks exist or at least
one SDP exists. The SDP refers to a period of at least four consecutive blocks or 1 ms
(whichever longer) in which the BER of all the consecutive blocks is equal to or higher
than 10-2 or the signal is lost.
l RSCSES indicates the regenerator section consecutive severely errored second.
A CSES refers to a second in which an SES event occurs continuously for less than 10
seconds.
l RSUAS indicates the regenerator section unavailable second.
A UAS period is counted from the first second of 10 consecutive SES events. These ten
seconds are considered to be a part of the unavailable time. A new available second period
starts from the first second of ten consecutive non-SES events. These ten seconds are
considered to be a part of the available time.
NOTE
When an IF board works in PDH mode, these performance events may also be reported. These events are
detected through the self-defined overhead byte B1 in the PDH microwave frame.
Attribute
Performance event cell B1CNT
Unit Block (RSBBE)

Second (RSES, RSSES, RSCSES, and
RSUAS)
Impact on System
A small number of bit errors do not affect the services. In the case of excessive bit errors,
however, the services are interrupted. Generally, the BER is less than 10-3 in the case of voice
services, and 10-6 in the case of data services.
Relevant Alarms
When the number of RSBBE, RSES, RSSES, RSCSES, or RSUAS events exceeds the specified
threshold, the RS_CROSSTR alarm is reported.

RSBBE 1500 15000
RSES 50 100

OptiX RTN 620

RSSES 20 50
RSUAS 20 50
RSCSES 4 (number of consecutive SES events)
Possible Causes
The system detects the regenerator section bit errors through the B1 byte.
Procedure
Step 1 See 5.4 Troubleshooting Bit Errors in TDM Services.
----End
C.2.5 RSOOF and RSOFS
Description
l RSOOF indicates the regenerator section out of frame.
The out-of-frame (OOF) block refers to a data block in which incorrect A1 and A2 bytes
are detected.
l RSOFS indicates the regenerator section out-of-frame second.
The out-of-frame second (OFS) refers to a second in which one or more OOF blocks are
detected.
Attribute
Performance event cell OOF
Unit Block (RSOOF)

Second (RSOFS)
Impact on System
The system discards OOF data blocks. Thus, an RSOOF event is equivalent to a big error (if one
RSOOF exists in a second, the BER is not less than 1.25 x 10-5).
Relevant Alarms
If RSOOF is received in five consecutive frames, the equipment changes to the OOF state. If
the OOF state lasts for 3 ms, the R_LOF alarm is reported and all the services are interrupted.

OptiX RTN 620
Possible Causes
The system detects incorrect A1 and A2 bytes.
Procedure
Step 1 If the R_LOF alarm is reported, eliminate the errors according to the alarm. Otherwise, see 5.4
Troubleshooting Bit Errors in TDM Services for handling.
----End
C.2.6 MSBBE, MSES, MSSES, MSCSES, and MSUAS

Description
l MSBBE indicates the multiplex section background block error.
l MSES indicates the multiplex section errored second.
l MSSES indicates the multiplex section severely errored second.
one SDP exists. The SDP refers to a period of at least four consecutive blocks or 1 ms
(whichever longer) in which the BER of all the consecutive blocks is equal to or higher
than 10-2 or the signal is lost.
l MSCSES indicates the multiplex section consecutive severely errored second.
seconds.
l MSUAS indicates the multiplex section unavailable second.
Attribute
Unit Block (MSBBE)

Second (MSES, MSSES, MSCSES, and
MSUAS)
Impact on System

OptiX RTN 620
Relevant Alarms
When the number of MSBBE, MSES, MSSES, MSCSES, or MSUAS events exceeds the
specified threshold, the MS_CROSSTR alarm is reported.

MSBBE 1500 15000
MSES 50 100
MSES 20 50
MSUAS 20 50
MSCSES 4 (number of consecutive SES events)
Possible Causes
The system detects multiplex section bit errors through the B2 byte.
Procedure
----End
C.2.7 MSFEBBE, MSFEES, MSFESES, MSFECSES, and MSFEUAS
Description
l MSFEBBE indicates the multiplex section far end background block error.
FEBBE indicates that the BBE occurs at the opposite site.
l MSFEES indicates the multiplex section far end errored second.
An FEES indicates that an ES event is detected at the opposite site.
l MSFESES indicates the multiplex section far end severely errored second.
An FESES indicates that an SES event is detected at the opposite site.
l MSFECSES indicates the multiplex section far end consecutive severely errored second.
FECSES indicates that an CSES event occurs at the opposite site.
l MSFEUAS indicates the multiplex section far end unavailable second.
FEUAS indicates that an UAS event occurs at the opposite site.
Attribute
Performance event cell LFEBE

OptiX RTN 620
Unit Block (MSFEBBE)

Second (MSFEES, MSFESES, MSFECSES,
and MSFEUAS)
Impact on System
Relevant Alarms
The MS_REI alarm is reported at the local end.
Possible Causes
The system detects multiplex section far end bit errors through the M1 byte.
Procedure
Step 1 Clear the corresponding performance events at the opposite site.
----End
C.2.8 HPBBE, HPES, HPSES, HPCSES, and HPUAS
Description
l HPBBE indicates the higher order path background block error.
l HPES indicates the higher order path errored second.
l HPSES indicates the higher order path severely errored second.
An SES refers to a certain second in which 30% or more than 30% errored blocks are
detected or at least one serious disturbance period (SDP) exists. The SDP refers to a period
of at least four consecutive blocks or 1 ms (whichever longer) in which the BER of all the
consecutive blocks is equal to or higher than 10-2 or the signal is lost.
l HPCSES indicates the higher order path consecutive severely errored second.
seconds.
l HPUAS indicates the higher order path unavailable second.

OptiX RTN 620
Attribute
Unit Block (HPBBE)

Second (HPES, HPSES, HPCSES, and
HPUAS)
Impact on System
Relevant Alarms
When the number of HPBBE, HPES, HPSES, HPCSES, or HPUAS performance events exceeds
the specified threshold, the HP_CROSSTR alarm is reported.

HPBBE 1500 15000
HPES 50 100
HPSES 20 50
HPUAS 20 50
HPCSES 4 (number of consecutive SES events)
Possible Causes
The system detects higher order path bit errors through the B3 byte.
Procedure
----End

OptiX RTN 620
C.2.9 HPFEBBE, HPFEES, HPFESES, HPFECSES, and HPFEUAS
Description
l HPFEBBE indicates the higher order path far end background block error.
FEBBE indicates that a BBE event occurs at the opposite end.
l HPFEES indicates the higher order path far end errored second.
FEES indicates that an ES event occurs at the opposite end.
l HPFESES indicates the higher order path far end severely errored second.
FESES indicates that an SES event occurs at the opposite end.
l HPFECSES indicates the higher order path far end consecutive severely errored second.
FECSES indicates that a CSES event occurs at the opposite end.
l HPFEUAS indicates the higher order path far end unavailable second.
FEUAS indicates that a UAS event occurs at the opposite end.
Attribute
Performance event cell PFEBE
Unit Block (HPFEBBE)

Second (HPFEES, HPFESES, HPFECSES,
and HPFEUAS)
Impact on System
Relevant Alarms
The HP_REI alarm is reported at the local end.
Possible Causes
The system detects the higher order path far end bit errors through bits 1 to 4 in the G1 byte.
Procedure
Step 1 Clear the corresponding performance event at the opposite end.
----End

OptiX RTN 620
C.2.10 IF_BBE, IF_ES, IF_SES, IF_CSES, and IF_UAS
Description
l IF_BBE indicates the radio link background block error.
l IF_ES indicates the radio link errored second.
l IF_SES indicates the radio link severely errored second.
An SES refers to a certain second in which 30% or more than 30% errored blocks are
detected or at least one serious disturbance period (SDP) exists. The SDP refers to a period
of at least four consecutive blocks or 1 ms (whichever longer) in which the BER of all the
consecutive blocks is equal to or higher than 10-2 or the signal is lost.
l IF_CSES indicates the radio link consecutively severely errored second.
seconds.
l IF_UAS indicates the radio link unavailable second.
Attribute
Performance event cell IFCNT
Unit Block (IFBBE)

Second (IFES, IFSES, IFCSES, and IFUAS)
Impact on System
Relevant Alarms
In the case of the IFH2 board, the MW_BER_SD or MW_BER_EXC alarm is reported when
the BER exceeds the specified threshold.
In the case of the IF1 board, the B1_SD or B1_EXC alarm is reported when the BER exceeds

OptiX RTN 620
Possible Causes
The system detects bit errors on the radio link through the bit error detection overheads in the
overheads of a microwave frame.
Procedure
----End
C.2.11 VC3BBE, VC3ES, VC3SES, VC3CSES, and VC3UAS

Description
l VC3BBE indicates VC-3 background block error.
A BBE refers to the errored block excluding the errored block in the unavailable time and
l VC3ES indicates VC-3 errored second.
An ES refers to a certain second in which one or more errored blocks are detected.
l VC3SES indicates VC-3 severely errored second.
An SES refers to a certain second in which 30% or more errored blocks are detected or at
least one serious disturbance period (SDP) exists. The SDP refers to a period of at least
four consecutive blocks or 1 ms (whichever longer) in which the BER of all the consecutive
blocks is equal to or higher than 10-2 or the signal is lost.
l VC3CSES indicates VC-3 consecutive severely errored second.
A CSES refers to a second of the period in which an SES event occurs continuously within
10 seconds.
l VC3UAS indicates VC-3 unavailable second.
Attribute
Unit Block (VC3BBE)

Second (VC3ES, VC3SES, VC3CSES, and
VC3UAS)
Impact on System

OptiX RTN 620
Related Alarms
If the number of VC3BBE, VC3ES, VC3SES, VC3CSES, or VC3UAS performance events
exceeds the specified threshold, the LP_CROSSTR alarm is reported.

VC3BBE 1500 15000
VC3ES 50 100
VC3SES 20 50
VC3UAS 20 50
VC3CSES 4 (number of consecutive SES events)
Possible Causes
The system detects VC-3 path bit errors through the B3 byte.
Procedure
----End
C.2.12 VC3FEBBE, VC3FEES, VC3FESES, VC3FECSES, and

VC3FEUAS
Description
l VC3FEBBE indicates VC-3 far end background block error.
A VC3FEBBE indicates that a BBE event is detected at the opposite site.
l VC3FEES indicates VC-3 far end errored second.
An FEES indicates that an ES event is detected at the opposite site.
l VC3FESES indicates VC-3 far end severely errored second.
An FESES indicates that an SES event is detected at the opposite site.
l VC3FECSES indicates VC-3 far end consecutive severely errored second.
An FECSES indicates that a CSES event is detected at the opposite site.
l VC3FEUAS indicates VC-3 far end unavailable second.
An FEUAS indicates that a UAS event is detected at opposite site.
Attribute
Performance event cell VC3FEBE

OptiX RTN 620
Unit Block (VC3FEBBE)

Second (VC3FEES, VC3FESES,
VC3FECSES, and VC3FEUAS)
Impact on System
Relevant Alarms
The LP_REI_VC3 alarm is reported at the local end.
Possible Causes
The system detects the VC-3 path far end bit errors through bits 1 to 4 in the G1 byte.
Procedure
----End
C.2.13 LPBBE, LPES, LPSES, LPCSES, and LPUAS
Description
l LPBBE indicates the lower order path background block error.
l LPES indicates the lower order path errored second.
l LPSES indicates the lower order path severely errored second.
one SDP exists. The SDP is a period when loss of signal is detected or the BER of all the
consecutive blocks are greater than or equal to 10-2 in at least four consecutive blocks or 1
ms (whichever longer).
l LPCSES indicates the lower order path consecutive severely errored second.
seconds.
l LPUAS indicates the lower order path unavailable second.
An unavailable second (UAS) is counted from the first second of ten SES events, which
are considered to be part of the unavailable time. A new available second period starts from

OptiX RTN 620
the first second of ten consecutive non-SES events, which are considered to be part of the
available time.
Attribute
Performance event cell LPBIP2CNT
Unit Block (LPBBE)

Second (LPES, LPSES, LPCSES, and
LPUAS)
Impact on System
A small number of bit errors do not affect the service. In the case of excessive bit errors, however,
the services are interrupted. Generally, the BER is less than 10-3 in the case of voice services
and less than 10-6 in the case of data services.
Relevant Alarms
When the number of LPBBE, LPES, LPSES, LPCSES, or LPUAS events exceeds the specified
threshold, the LP_CROSSTR alarm is reported.

LPBBE 1500 15000
LPES 50 100
LPSES 20 50
LPUAS 20 50
LPCSES 4 (number of consecutive SES events)
Possible Causes
The system detects lower order path bit errors through the V5 byte (BIP-2 check) (in the case
of an E1 interface board or an Ethernet board) or B3 byte (in the case of an E3/T3 interface
board).
Procedure
----End

OptiX RTN 620
C.2.14 LPFEBBE, LPFEES, LPFESES, LPFECSES, and LPFEUAS

Description
l LPFEBBE indicates the lower order path far end background block error.
FEBBE indicates that the BBE occurs at the opposite site.
l LPFEES indicates the lower order path far end errored second.
FEES indicates that the ES occurs at the opposite site.
l LPFESES indicates the lower order path far end severely errored second.
FESES indicates that the SES occurs at the opposite site.
l LPFECSES indicates the lower order path far end consecutive severely errored second.
FECSES indicates that the CSES occurs at the opposite site.
l LPFEUAS indicates the lower order path far end unavailable second.
FEUAS indicates that the UAS occurs at the opposite site.
Attribute
Performance event cell LPFEBE
Unit Block (LPFEBBE)

Second (LPFEES, LPFESES, LPFECSES,
and LPFEUAS)
Impact on System
A small number of bit errors do not affect the service. In the case of excessive bit errors, however,
the services are interrupted. Generally, the BER is less than 10-3 in the case of voice services
and less than 10-6 in the case of data services.
Relevant Alarms
If a performance event is generated on a tributary board, the LP_REI alarm is generated at the
local end. If a performance event is generated on an Ethernet board, the LP_REI_VC12 alarm
is generated at the local end.
Possible Causes
The system detects lower order path bit errors through bit 3 in the V5 byte (in the case of an E1
interface board or an Ethernet board) or bits 1-4 in the G1 byte (in the case of an E3/T3 interface
board).
Procedure
----End

OptiX RTN 620
C.2.15 E3_LCV_SDH, E3_LES_SDH, and E3_LSES_SDH

Description
l E3_LCV_SDH indicates the statistics of the E3 line side codes that do not meet the relevant
requirements.
l E3_LES_SDH indicates the severely errored second of the E3 line side codes.
l E3_LSES_SDH indicates the E3 line side code violation severely errored second.
Attribute
Performance event cell DS3_BPV_CNT
Unit Block
Impact on System
Bit errors may occur in the services.
Possible Causes
Interference signals exist on the transmission lines.
Procedure
Step 1 Check whether the services gain access to the receive end.
If... Then...
No services gain access to the receive end Enable the services to gain access to the
receive end.
Certain services gain access to the receive Go to the next step.
end
Step 2 Check whether the ground cable is connected properly
If... Then...
The ground cable is connected incorrectly or Connect the ground cable correctly to
is disconnected eliminate the interference.
The connection is correct Go to the next step.
Step 3 Check whether the connectors of the transmission cables are made properly.
If... Then...
The connector is made improperly Make a new connector.
The connection is correct Eliminate the external interference signals.
----End

OptiX RTN 620
C.2.16 T3_LCV_SDH, T3_LES_SDH, and T3_LSES_SDH

Description
l T3_LCV_SDH indicates the statistics of the T3 line side codes that do not meet the relevant
requirements.
l T3_LES_SDH indicates the severely errored second of the T3 line side codes.
l T3_LSES_SDH indicates the severely errored second of the T3 line side codes.
Attribute
Performance event cell DS3_BPV_CNT
Unit Block
Impact on System
Bit errors may occur in the services.
Possible Causes
Interference signals exist on the transmission lines.
Procedure
Step 1 Check whether the services gain access to the receive end.
If... Then...
No services gain access to the receive end Enable the services to gain access to the
receive end.
Certain services gain access to the receive Go to the next step.
end
Step 2 Check whether the ground cable is connected properly
If... Then...
The ground cable is connected incorrectly or Connect the ground cable correctly to
is disconnected eliminate the interference.
The ground cable is connected correctly Go to the next step.
Step 3 Check whether the connectors of the transmission cables are made properly.
If... Then...
The connectors are made inappropriately Make new connectors.
The connections are correct Eliminate the external interference signals.
----End

OptiX RTN 620
C.2.17 TSL_MAX, TSL_MIN, TSL_CUR, and TSL_AVG
Description
l TSL_MAX indicates the maximum radio transmit signal level.
l TSL_MIN indicates the minimum radio transmit signal level.
l TSL_CUR indicates the current radio transmit signal level.
l TSL_AVG indicates the average radio transmit signal level.
Attribute
Performance event cell TSL
Unit dBm
Impact on System
When the radio transmit signal level is very low or very high, the radio received signal level at
the opposite site is very low or very high. As a result, bit errors occur and even services are
interrupted.
Related Alarms
If the radio transmit signal level is beyond the range supported by the ODU, the
RADIO_TSL_HIGH or RADIO_TSL_LOW alarm is reported.
C.2.18 RSL_MAX, RSL_MIN, RSL_CUR, and RSL_AVG
Description
l RSL_MAX indicates the maximum radio received signal level.
l RSL_MAX indicates the minimum radio received signal level.
l RSL_CUR indicates the current radio received signal level.
l RSL_AVG indicates the average radio received signal level.
Attribute
Performance event cell RSL
Unit dBm

OptiX RTN 620
Impact on System
When the radio received signal level is very low or very high, bit errors occur and even services
are interrupted.
Relevant Alarms
If the radio received signal level exceeds the specified threshold, the RADIO_RSL_HIGH or
RADIO_RSL_LOW alarm is reported.
C.2.19 RLHTT, RLLTT, TLHTT, and TLLTT
Description
l RLHTT indicates the duration when the ODU at the local end has a receive power lower
l RLLTT indicates the duration when the ODU at the local end has a receive power lower
l TLHTT indicates the duration when the ODU at the local end has a transit power higher
l TLLTT indicates the duration when the ODU at the local end has a transit power higher
Attribute
Performance event cell RLHTS, RLLTS, TLHTS, and TLLTS
Unit Second
Impact on System
None.
Relevant Alarms
None.
C.2.20 ACMDOWNCNT and ACMUPCNT
Description
l ACMDOWNCNT indicates the count of AM switching on a board from a high-efficiency
modulation scheme to a low-efficiency modulation scheme in the current performance
statistics period.
l ACMUPCNT indicates the count of AM switching on a board from a low-efficiency
modulation scheme to a high-efficiency modulation scheme in the current performance
statistics period.

OptiX RTN 620
Attribute
Performance event cell AMDOWNCNT and AMUPCNT
Unit None
Impact on System
ACMDOWNCNT and ACMUPCNT indicate only statistical values, and do not affect the
system.
Relevant Alarms
AM_DOWNSHIFT
Possible Causes
When the AM function is enabled, the modulation scheme used by the IF port on an IF board
varies according to the quality of the link. Accordingly, the system counts the performance
during the change of the modulation scheme. When a low-efficiency modulation scheme is
switched to a high-efficiency modulation scheme, an upward switching action is recorded and
one ACMUPCNT event is counted. Similarly, when a high-efficiency modulation scheme is
switched to a low-efficiency modulation scheme, a downward switching action is recorded and
one ACMDOWNCNT event is counted.
C.2.21 FEC_BEF_COR_ER, FEC_COR_BYTE_CNT, and

FEC_UNCOR_BLOCK_CNT
Description
l FEC_BEF_COR_ER indicates the BER before the FEC is performed.
This event indicates the impact of the external environment on the transmission.
l FEC_COR_BYTE_CNT indicates the number of bytes corrected through the FEC.
This event indicates the impact of the FEC.
l FEC_UNCOR_BLOCK_CN indicates the number of frames that cannot be corrected
through the FEC.
This event indicates the number of error blocks after the FEC is performed.
Attribute
Performance event cell FECBEFCORER (FEC_BEF_COR_ER),

FECUNCORBLOCKCNT
(FEC_COR_BYTE_CNT), and
FECUNCORBLOCKCNT
(FEC_UNCOR_BLOCK_CNT)

OptiX RTN 620
Unit None (FEC_BEF_COR_ER)

None (FEC_COR_BYTE_CNT)
Block (FEC_UNCOR_BLOCK_CNT)
Impact on System
If the value of FEC_BEF_COR is very high, residual bit errors are generated after the FEC is
performed.
If the value of FEC_UNCOR_BLOCK_CNT is not zero, bit errors that cannot be corrected are
generated on a radio link, and bit errors are generated in the service accordingly.
Relevant Alarms
If a byte cannot be corrected, the MW_FEC_UNCOR alarm is reported.
C.2.22 QPSKWS, QAMWS16, QAMWS32, QAMWS64,

QAMWS128, and QAMWS256
Description
l QPSKWS indicates the working duration of the QPSK mode.
l QAMWS16 indicates the working time of the 16QAM mode.
Attribute
Performance event cell QPSKWSSECOND (QPSKWS)

QAMWS16SECOND (QAMWS16)
Unit Second

OptiX RTN 620
Impact on System
When the AM function is not enabled, the performance event does not affect the system.
When the AM function is enabled, in normal cases, the seconds of the modulation mode for
ensuring capacity account for a larger percentage. In the duration set for good weather, if the
seconds of the low-efficiency modulation mode account for a larger percentage, the performance
of the radio link is abnormal.
Relevant Alarms
None.
C.2.23 TPLMAX, TPLMIN, and TPLCUR
Description
l TPLMAX indicates the maximum transmit optical power at an optical interface.
l TPLMIN indicates the minimum transmit optical power at an optical interface.
l TPLCUR indicates the current transmit optical power at an optical interface.
Attribute
Performance event cell OPM
Unit dBm
Impact on System
In normal cases, the receive optical power is 3 dB higher than the receiver sensitivity, and 5 dB
lower than the overload power.
If the transmit optical power is very low or very high, the receive optical power at the opposite
site is accordingly very low or very high. As a result, bit errors occur and even services are
interrupted.
Relevant Alarms
l If the transmit optical power at the opposite site is lower than the receiver sensitivity, the
IN_PWR_LOW is reported.
l If the receive optical power at the opposite site is higher than the overload power, the
IN_PWR_HIGH alarm is reported.
Related Concepts
SDH Interface Performance

OptiX RTN 620
C.2.24 RPLMAX, RPLMIN, and RPLCUR

Description
l RPLMAX indicates the maximum receive optical power at an optical interface.
l RPLMAX indicates the minimum receive optical power at an optical interface.
l RPLCUR indicates the current receive optical power at an optical interface.
Attribute
Performance event cell IPM
Unit dBm
Impact on System
In normal cases, the receive optical power is 3 dB higher than the receiver sensitivity, and 5 dB
lower than the overload power.
If the receive optical power is very low or very high, bit errors occur and even services are
interrupted.
Relevant Alarms
l If the receive optical power is lower than the receiver sensitivity, the IN_PWR_LOW
alarm is reported.
l If the receive optical power is higher than the overload power, the IN_PWR_HIGH alarm
is reported.
Related Concepts
SDH Interface Performance
C.2.25 BDTMPMAX, BDTMPMIN, and BDTMPCUR

Description
l BDTEMPMAX indicates the maximum temperature of a board.
l BDTEMPMIN indicates the minimum temperature of a board.
l BDTEMPCUR indicates the current temperature of a board.
Attribute
Performance event cell None.
Unit ℃

OptiX RTN 620
Impact on System
If the temperature of a board is very high or very low, the performance of the board degrades,
and bit errors or other faults occur.
Relevant Alarms
If the temperature of a board exceeds the specified threshold, the TEMP_ALARM alarm is
reported.
C.2.26 OSPITMPMAX, OSPITMPMIN, and OSPITMPCUR

Description
l OSPITMPMAX indicates the maximum temperature of a laser core.
l OSPITMPMIN indicates the minimum temperature of a laser core.
l OSPITMPCUR indicates the current temperature of a laser core.
Attribute
Performance event cell TMP
Unit ℃
Impact on System
If the temperature of a laser core is very high or very low, the performance of the laser degrades,
and bit errors or other faults occur.
Relevant Alarms
None.

OptiX RTN 620
Maintenance Guide D RMON Event Reference
D RMON Event Reference
RMON events reflect the running status of the Ethernet services. This topic describes all the
possible RMON events on the OptiX RTN 620 and how to handle these events.
D.1 List of RMON Alarm Entries

RMON alarm entries refer to the table entries in the RMON alarm group.
D.2 List of RMON Performance Entries
RMON performance entries refer to the table entries in the RMON statistics group or history
group.
D.3 RMON Alarm Clearance Reference
This topic describes the RMON events of the OptiX RTN 620 and how to handle these events.
Issue 01 (2009-12-30) Huawei Proprietary and Confidential D-1

OptiX RTN 620
D RMON Event Reference Maintenance Guide
D.1 List of RMON Alarm Entries

RMON alarm entries refer to the table entries in the RMON alarm group.
Table D-1 List of RMON alarm entries

Alarm Name Description Source
Dropevent Number of packet loss events EMS6, EFT4, IFH2, EFP6

exceeding the threshold
UndersizePkts Number of undersized packets

OversizePkts Number of oversized packets

Fragments Number of fragment packets EMS6, EFT4, EFP6

Jabbers Number of jabber packets exceeding

the threshold
FCSErrors Number of packets with FCS errors

D.2 List of RMON Performance Entries

RMON performance entries refer to the table entries in the RMON statistics group or history
group.
Table D-2 List of RMON performance entries

Category Name of a Performance Entry Source
of
Performa
nce
Entries
Basic Packets received (packets) EMS6, EFT4, IFH2, EFP6

performanc
e Packets received (64 bytes in length)
(packets)
Packets received (65-127 bytes in

length) (packets)

length) (packets)
D-2 Huawei Proprietary and Confidential Issue 01 (2009-12-30)

OptiX RTN 620

of
Performa
nce
Entries

length) (packets)

length) (packets)

length) (packets)
Bytes received (bytes)
Oversized packets received (packets)
Undersized packets received

(packets)
Multicast packets received (packets)
Broadcast packets received (packets)
Undersized error packets received IFH2, EFP6

(packets)
Oversized error packets received EMS6, EFT4, EFP6

(packets)
Packet loss events EMS6, EFT4, IFH2
Fragments received (packets) EMS6, EFT4,EFP6
Collisions (times) EMS6, EFT4
FCS and alignment error packets EFT4, EFP6

(packets)
Extended Packets transmitted (64 bytes in EMS6, EFT4, IFH2, EFP6

performanc length) (packets)
e
Packets transmitted (65-127 bytes in
length) (packets)

length) (packets)

length) (packets)
Packets transmitted (512-1023 bytes

in length) (packets)
Packets transmitted (1024-1518 bytes

in length) (packets)

OptiX RTN 620

of
Performa
nce
Entries
Packets received and transmitted (64

bytes in length) (packets)
Packets received and transmitted

(65-127 bytes in length) (packets)




Unicast packets transmitted (packets)
Pause frames received (frames)
Pause frames transmitted (frames)
FCS error frames (frames)
Oversized packets transmitted

(packets)
Packets transmitted (packets)
Bytes transmitted (bytes)
Packets received (1519 bytes to the IFH2

MTU in length) (packets)
Packets transmitted (1519 bytes to the

MTU in length) (packets)

(1519 bytes to the MTU in length)
(packets)
Transmitting packet loss events

(packets)
Unicast packets received (packets) EMS6, EFT4, EFP6
Multicast packets transmitted

(packets)

OptiX RTN 620

of
Performa
nce
Entries
Broadcast packets transmitted

(packets)
Rate of good full-frame bytes received

(bytes/second)
Rate of good full-frame bytes

transmitted (bytes/second)
Good full-frame bytes received

(bytes)
Good full-frame bytes transmitted

(bytes)
Control frames received (frame) EMS6, EFT4
Control frames transmitted (frame) EMS6, EFT4, EFP6
Alignment error frames (frame) EMS6, EFT4, EFP6
Control packets transmitted (packets) EFP6
Frames properly transmitted after only EMS6, EFT4

one collision (frame)
Frames properly transmitted after

multiple collisions (frame)
Late collisions (times)
Frames unsuccessfully transmitted

after successive collisions (frame)
Delayed frames (frame)
VCG Packets received (packets) EMS6, EFP6

performanc
e Packets transmitted (packets)
Good packets received (packets)
Good packets transmitted (packets)
Rate of good full-frame bytes received

(bytes/second)
Rate of good full-frame bytes

transmitted (bytes/second)
Octects Received(octets)
Octects Transmitted(octets)

OptiX RTN 620
NOTE
The ports of the EMS6, EFP6, EFT4, and IFH2 boards support the basic performance and the extended
performance. The VCTRUNK of the EMS6 and EFP6 board supports the VCG performance. The VCTRUNK
of the EFT4 board does not support RMON.
D.3 RMON Alarm Clearance Reference

This topic describes the RMON events of the OptiX RTN 620 and how to handle these events.
D.3.1 DropEvent
D.3.2 UndersizePkts
D.3.3 OversizePkts
D.3.4 Fragments
D.3.5 Jabbers
D.3.6 FCSErrors
D.3.1 DropEvent
Description
DropEvent indicates the number of events that packet loss occurs due to resource deficiency.
An RMON threshold-crossing event is reported when the number of packet loss events is higher
than the upper threshold or lower than the lower threshold.
Impact on System
When packet loss occurs frequently, services are affected and the system is affected seriously.
Therefore, you must rectify the fault immediately.
Possible Causes
This performance event indicates packet loss due to the full MAC buffer, FIFO overflow, flow
control, or backward pressure.
l The lower threshold is not set to a non-zero value.

l The local data board is faulty.
Procedure
Step 1 Rectify the fault according to the specific performance event.
If... Then...
The number of packet loss events is lower than the lower Change the lower threshold to 0.
threshold

OptiX RTN 620
If... Then...
The number of packet loss events is higher than the Go to the next step.
upper threshold
Step 2 Replace the board that reports an alarm at the local end. Clear the alarm according to the type
of the board.
If... Then...
The alarm is reported by an IF board See 6.7 Replacing the IF Board.
The alarm is reported by an Ethernet See 6.6 Replacing the Ethernet Service
board Processing Board.
----End
Relevant Information
All the RMON performance events are threshold-crossing events. That is, you can check whether
the count of RMON performance events in a sampling period exceeds the specified threshold.
You can set the sampling period, which is defaulted to 10 seconds.
D.3.2 UndersizePkts
Description
UndersizePkts indicates that an RMON threshold-crossing event is reported when the number
of packets that are shorter than 64 bytes and are received on the line side crosses the preset
threshold.
Impact on System
The data frames whose length is beyond the specific range are discarded. As a result, the system
services are affected.
Possible Causes
1. The length of a data frame that is received by the board is shorter than 64 bytes.
2. The hardware of a local board is faulty.
Procedure
Step 1 Check whether the opposite equipment transmits a packet that is shorter than 64 bytes.
If... Then...
The opposite equipment transmits a packet that is Rectify the fault on the opposite NE.
shorter than 64 bytes
The opposite end does not transmit a packet that is Go to the next step.
shorter than 64 bytes
of the board.

OptiX RTN 620
If... Then...
----End
l The length range of the data frames that are processed by each type of board is different.
The length of the data frames transmitted by the opposite end is within the normal range,
but it may be beyond the length range of the data frames that can be processed by the local
end.
l Undersized frames may be relevant to services. The opposite equipment may change the
length of data frames by an operation such as encapsulation. As a result, a downstream
node considers the data frames as undersized frames.
D.3.3 OversizePkts
Description
OversizePkts indicates that an RMON threshold-crossing event is reported when the number of
packets that are longer than the MTU specified for the port and are received on the line side
crosses the preset threshold.
Impact on System
If the length of a data frame received at a port is longer than the preset maximum frame length,
the data frame is discarded and thus the system services are affected.
Possible Causes
1. The length of an oversized frame configured for a board is shorter than the length of a frame
that is received by the board.
2. The hardware of the local board is faulty.
Procedure
Step 1 Check whether the opposite equipment transmits a frame that is longer than the maximum frame
of the local equipment.
If... Then...
The opposite equipment transmits a frame Notify the opposite equipment that the length
that is longer than the maximum frame of transmitted frames is changed.
length set for the local equipment
The opposite equipment does not transmit Go to the next step.
a frame that is longer than the maximum
frame length set for the local equipment
of the board.

OptiX RTN 620
If... Then...
----End
l The length range of the data frames that are processed by each type of board is different.
The length of the data frames transmitted by the opposite end is within the normal range,
but it may be beyond the length range of the data frames that can be processed by the local
end.
l Oversized frames may be relevant to services. The opposite equipment may change the
length of data frames by an operation such as encapsulation. As a result, a downstream
node considers the data frames as oversized frames.
D.3.4 Fragments
Description
Fragments indicates that an RMON threshold-crossing event is reported when the number of
received packets that are shorter than 64 bytes and have FCS or alignment errors exceeds the
specified upper threshold.
Impact on System
Data transmission is delayed or packet loss occurs.
Possible Causes
l The working modes of the ports on the equipment at both ends are different from each
other.
l The hardware of the local board is faulty.
Procedure
Step 1 Check whether the working modes of the ports on the equipment at both ends are the same.
If... Then...
The working modes are the same Go to the next step.
The working modes are different from Change the working mode of the port on the
each other local equipment to ensure that the working
modes of the ports on the equipment at both
ends are the same.
Step 2 Replace the board that reports an alarm at the local end. For details, see 6.6 Replacing the
Ethernet Service Processing Board.
----End

OptiX RTN 620
D.3.5 Jabbers
Description
Jabbers indicates that an RMON threshold-crossing event is reported when the received packets
are longer than 1518 bytes and have FCS or alignment errors.
Impact on System
Data transmission is delayed or packet loss occurs.
Possible Causes
other.
Procedure
Step 1 Check whether the working modes of the ports on the equipment at both ends are the same.
If... Then...
The working modes are the same Go to the next step.
The working modes are different from Change the working mode of the port on the
each other local equipment to ensure that the working
modes of the ports on the equipment at both
ends are the same.
----End
D.3.6 FCSErrors
Description
FCSErrors indicates that the number of Ethernet data frames that contain FCS check errors
(excluding the oversized and undersized frames) and are received by the local end exceeds the
specified threshold. FCSErrors includes FCSErrOv and FCSErrUd. FCSErrOv indicates that the
number of Ethernet data frames that contain FCS check errors is higher than the upper threshold,
and FCSErrUd indicates the number of Ethernet data frames that contain FCS check errors is
lower than the lower threshold.
Impact on System
Most boards discard the packets of FCS check errors. The system services are interrupted in the
worst case.

OptiX RTN 620
Possible Causes
other. For example, the port at one end works in half-duplex mode, and the port at the other
end works in half-duplex mode.
l The transmission line is of the poor quality and bit errors exist.
Procedure
Step 1 Rectify the fault based on the alarm parameters.
If... Then...
The FCSErrUd performance event occurs Change the lower threshold to 0.
The FCSErrOv performance event occurs Go to the next step.
Step 2 If the FCSErrOv performance event occurs, on the NMS, check whether the working modes of
the ports on the equipment at both ends are the same.
If... Then...
The ports on the equipment at both ends are Change the working modes of the ports on the
different from each other equipment at both ends to ensure that they are
the same.
The ports on the equipment at both ends are Go to the next step.
the same
----End
All the RMON performance events are threshold-crossing events. That is, you can check whether
the count of RMON performance events in a sampling period exceeds the specified threshold.
You can set the sampling period, which is defaulted to 10 seconds.

OptiX RTN 620
Maintenance Guide E Alarm Management
E Alarm Management
Alarm management of the OptiX RTN 620 is classified into NE alarm management and board
alarm management.
E.1 NE Alarm Management

The NE alarm management function set by a user is applicable to all the boards on an NE.
E.2 Board Alarm Management
The board alarm management function is valid for only a board on which a user configures this
function.
Issue 01 (2009-12-30) Huawei Proprietary and Confidential E-1

OptiX RTN 620
E Alarm Management Maintenance Guide
E.1 NE Alarm Management

The NE alarm management function set by a user is applicable to all the boards on an NE.
The NE alarm management function of the OptiX RTN 620 includes:
l Sets the method for saving an alarm.

l Sets the delay of an alarm.
l Sets the reversion mode of an alarm.
For details about these functions, see the manuals or online Help of the NMS.
E.2 Board Alarm Management

The board alarm management function is valid for only a board on which a user configures this
function.
E.2.1 Setting the Alarm Severity

Alarms are classified into four severity levels: critical, major, minor, and warning. The
maintenance personnel can change the alarm severity by using the NMS.
E.2.2 Alarm Suppression
A board detects only the alarms whose Alarm Monitoring is set to Yes. If the alarms need not
be monitored, the maintenance personnel can set alarm suppression.
E.2.3 Alarm Auto-Report
If Alarm Auto-Report is set to Reported, all the detected alarms are reported immediately to
the NMS. If Alarm Auto-Report is set to Not Report, the alarms are reported only when alarm
query is performed on the NMS. The maintenance personnel can change the setting as required
on the NMS.
E.2.4 Alarm Reversion
If a port is not configured with a service, certain alarms may be reported. To filter the alarms
that are not concerned, set these alarms to be reversed. In this manner, the alarm status at this
port is contrary to the actual status. That is, the status is displayed to be normal when an alarm
is actually reported.
E.2.5 Setting of the Bit Error Alarm Threshold
When the number of bit errors detected by a board exceeds a specified value, the board generates
a bit error alarm. This specified value 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 620.
E.2.6 AIS Insertion
AIS insertion can be set for certain alarms reported on a board. When a board detects the alarms,
it inserts all 1s into the lower level service signal to indicate the opposite end that the service
signal is unavailable.
E.2.7 UNEQ Insertion
When a board detects that the service path is not in use or that the LOS alarm is generated, the
board inserts all 0s into the service signal to notify the opposite end that the service signal is
unavailable.
E-2 Huawei Proprietary and Confidential Issue 01 (2009-12-30)

OptiX RTN 620
E.2.1 Setting the Alarm Severity

Alarms are classified into four severity levels: critical, major, minor, and warning. The
maintenance personnel can change the alarm severity by using the NMS.
This function is supported by all the boards.
E.2.2 Alarm Suppression

A board detects only the alarms whose Alarm Monitoring is set to Yes. If the alarms need not
be monitored, the maintenance personnel can set alarm suppression.
E.2.3 Alarm Auto-Report

If Alarm Auto-Report is set to Reported, all the detected alarms are reported immediately to
the NMS. If Alarm Auto-Report is set to Not Report, the alarms are reported only when alarm
query is performed on the NMS. The maintenance personnel can change the setting as required
on the NMS.
E.2.4 Alarm Reversion

If a port is not configured with a service, certain alarms may be reported. To filter the alarms
that are not concerned, set these alarms to be reversed. In this manner, the alarm status at this
port is contrary to the actual status. That is, the status is displayed to be normal when an alarm
is actually reported.
The alarm reversion function is available in three modes, namely, 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.
l Auto reversion
In this mode, alarm reversion can be enabled for a port where alarms are reported. After
alarm reversion is enabled at a port, alarms are not reported. When the current alarm is
cleared, the alarm reversion changes automatically to the disabled status. That is, the alarm
reversion changes to the non-revertive mode. Then, the alarm reporting status at the port
is the same as the actual status.
l Manual reversion
In this mode, alarm reversion can be enabled for a port regardless of whether any alarms
are reported at the port. After alarm reversion is enabled, the alarm reporting status at the
port is the same as the actual status. After alarm reversion is manually disabled, the alarm
reversion status changes to the non-revertive mode. Then, the alarm reporting status at the
port is the same as the actual status.
Pay attention to the following points when you set the alarm reversion function:
l Alarm reversion does not change the actual status of alarms on the board, as well as the
indication status of the alarm indicators.

OptiX RTN 620
l Alarm reversion is implemented by the NE software. The alarm data is the same on the NE
and the NMS, which indicates the status after the alarm reversion. If you directly query the
alarm data of a board, however, the actual alarm status is returned.
l Alarm reversion is set on the basis of a port. Alarm reversion is supported by each port of
the SD1, SL1, SDE, SLE, SL4, IF1A, IF1B, IFX, IF0A, IF0B, PH1, PO1, PD1, PL3, EFT4,
and EFP6.
E.2.5 Setting of the Bit Error Alarm Threshold

When the number of bit errors detected by a board exceeds a specified value, the board generates
a bit error alarm. This specified value 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 620.
Table E-1 Setting of the bit error alarm threshold

Alarm Name Default Alarm Threshold Applicable Board
B1_EXC 10-3 SD1, SL1, SDE, SLE, IF1A,

IF1B, IF0A, IF0B, IFX, and
B1_SD 10-6 SL4

IF1B, IFX, and SL4
B2_SD 10-6

IF1B, IFX, SL4, and PL3
B3_SD 10-6
BIP_EXC 10-3 PO1, PH1, EFT4, EMS6,

EFP6, PD1, IF0A, and IF0B
BIP_SD 10-6
B3_EXC_VC3 10-3 EFT4 and EMS6
B3_SD_VC3 10-6
MW_BER_EXC 10-3 IFH2
MW_BER_SD 10-6
E.2.6 AIS Insertion

AIS insertion can be set for certain alarms reported on a board. When a board detects the alarms,
it inserts all 1s into the lower level service signal to indicate the opposite end that the service
signal is unavailable.

OptiX RTN 620
Table E-2 Setting of the AIS insertion

Trigger Condition Default Value Applicable Board
B1_EXC Enabled SD1, SL1, SDE, SLE, IF1A,

IF1B, IFX, and SL4
Disabled IF0A and IF0B
B2_SD Disabled SD1, SL1, SDE, SLE, IF1A,

IF1B, and IFX
Enabled SL4
B2_EXC Disabled SD1, SL1, SDE, SLE, IF1A,

IF1B, IFX, and SL4
HP_LOM Enabled
HP_TIM Disabled
HP_SLM Disabled
HP_UNEQ Disabled
B3_EXC Enabled SD1, SL1, SDE, SLE, IF1A,

IF1B, IFX, PL3, and SL4
B3_SD Disabled
B1_SD Disabled SD1, SL1, SDE, SLE, IF1A,

IF1B, IFX, IF0A, IF0B, and
SL4
LP_TIM Disabled PH1, PO1, PD1, and PL3
LP_UNEQ Disabled
LP_SLM Disabled
T_ALOS Enabled
BIP_EXC Disabled
BIP_SD Disabled
P_LOS Enabled PL3
MW_BER_EXC Enabled IFH2
MW_BER_SD Forbidden

OptiX RTN 620
NOTE
l When the SD1, SL1, SDE, SLE, or SL4 board detects the R_LOS, R_LOF, MS_AIS, AU_AIS, or
AU_LOP alarm, this board forcibly inserts the AIS.
l When the IFX, IF1A, or IF1B board detects the MW_LOF, R_LOS, R_LOF, MS_AIS, AU_AIS, or
AU_LOP alarm, this board forcibly inserts the AIS.
l When the IF0A or IF0B board detects the MW_LOF, R_LOS, or R_LOF alarm, this board forcibly
inserts the AIS.
l When the IFH2 board detects the MW_BER_EXC alarm, this board forcibly inserts the AIS.
E.2.7 UNEQ Insertion

When a board detects that the service path is not in use or that the LOS alarm is generated, the
board inserts all 0s into the service signal to notify the opposite end that the service signal is
unavailable.
Table E-3 Setting of the UNEQ insertion

Trigger Condition Default Value Applicable Board
T_ALOS Disabled PH1, PO1, PD1, PL3
Service path being not in use Disabled
P_LOS Disabled PL3

OptiX RTN 620
Maintenance Guide F Performance Event Management
F Performance Event Management
Performance event management of the OptiX RTN 620 is classified into NE performance event
management and board performance event management.
F.1 NE Performance Event Management

The NE performance event management function set by a user is applicable to all the boards on
an NE.
F.2 Board Performance Event Management
The performance event management function is valid for only a board on which a user configures
this function.
Issue 01 (2009-12-30) Huawei Proprietary and Confidential F-1

OptiX RTN 620
F Performance Event Management Maintenance Guide
F.1 NE Performance Event Management

The NE performance event management function set by a user is applicable to all the boards on
an NE.
The NE performance event management function supported by OptiX RTN 620 includes:
l Sets the monitoring of NE performance events
l Sets the start/end time of performance events
l Enables/Disables the reporting of UAT events
For details about these functions, see the manuals or online Help of the NMS.
F.2 Board Performance Event Management

The performance event management function is valid for only a board on which a user configures
this function.
Table F-1 Board performance event management function

Function Applicable Board
Sets 15-minute/24-hour SD1, SL1, SDE, SLE, SL4, IFX, IF0A, IF0B, IF1A, IF1B, IFH2,
performance PO1, PH1, PD1, PL3, EFT4, EMS6, EFP6, PXC, ODU, and SCC
monitoring.
Sets 15-minute/24-hour SD1, SL1, SDE, SLE, SL4, IFX, IF0A, IF0B, IF1A, IF1B, IFH2,
performance event auto- PO1, PH1, PD1, PL3, EFT4, EMS6, EFP6, PXC, ODU, and SCC
reporting.
Sets performance SD1, SL1, SDE, SLE, SL4, IFX, IF0A, IF0B, IF1A, IF1B, IFH2,
thresholds. PO1, PH1, PD1, PL3, EFT4, EMS6, and EFP6
Resets the performance SD1, SL1, SDE, SLE, SL4, IFX, IF0A, IF0B, IF1A, IF1B, IFH2,
register. PO1, PH1, PD1, PL3, EFT4, EMS6, EFP6, and ODU
Generates performance SD1, SL1, SDE, SLE, SL4, IFX, IF0A, IF0B, IF1A, IF1B, IFH2,
threshold-crossing PO1, PH1, PD1, PL3, EFT4, EMS6, and EFP6
alarms.
Monitors UAT events. SD1, SL1, SDE, SLE, SL4, IFX, IF0A, IF0B, IF1A, IF1B, IFH2,
PO1, PH1, PD1, PL3, EFT4, EMS6, and EFP6
Monitors CSES SD1, SL1, SDE, SLE, SL4, IFX, IF0A, IF0B, IF1A, IF1B, IFH2,
performance events. PO1, PH1, PD1, PL3, EFT4, EMS6, and EFP6
F-2 Huawei Proprietary and Confidential Issue 01 (2009-12-30)

OptiX RTN 620
Maintenance Guide G Alarm Suppression Relationship
G Alarm Suppression Relationship
Table G-1 Suppression relationship between intra-board alarms

Alarm Identifier Identifier of the Suppressed Alarm
MW_LOF R_LOS, R_LOF, R_LOC,

MW_FEC_UNCOR, MW_RDI, and
MW_LIM
R_LOS and 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,
and 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, and
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, and HP_REI
MS_RDI MS_REI
AU_AIS and AU_LOP B3_EXC, B3_SD, HP_TIM, HP_SLM,

HP_UNEQ, HP_RDI, HP_LOM, and
HP_REI
HP_UNEQ HP_TIM and HP_RDI
HP_TIMa HP_SLM, HP_LOM, B3_EXC, and B3_SD
HP_TIMa HP_LOM
HP_RDI HP_REI
Issue 01 (2009-12-30) Huawei Proprietary and Confidential G-1

OptiX RTN 620
G Alarm Suppression Relationship Maintenance Guide
LP_UNEQ LP_TIM, LP_RDI, and LP_SLM
LP_TIM LP_RDI
B1_EXC B1_SD
B2_EXC B2_SD
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, and
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, and
C2_VCAIS
T_ALOS E1_LOS and UP_E1_AIS
E1_LOS UP_E1_AIS
BIP_EXC BIP_SD
P_LOS A_LOC and P_AIS
C2_VCAIS LP_SLM
NOTE
a: The alarm suppression relationship is valid only when the AIS insertion function is enabled.
Table G-2 Suppression relationship between inter-board alarms

R_LOS, R_LOC, MS_AIS, AU_AIS, and TU_AIS

AU_LOP
MW_LOF and MW_LIM TU_AIS
G-2 Huawei Proprietary and Confidential Issue 01 (2009-12-30)

OptiX RTN 620
Maintenance Guide H Glossary
H Glossary
Terms are listed in an alphabetical order.
Number
1U The standard electronics industries association (EIA) rack unit (44 mm/
1.75 in.)
1+1 protection A radio 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 radio link.
A
Adaptive A technology that is used to automatically adjust the modulation mode
modulation based on the channel quality. When the channel quality is favorable, the
equipment adopts a high-efficiency modulation mode to improve the
transmission efficiency and the spectrum utilization of the system. When
the channel quality is degraded, the equipment adopts the low-efficiency
modulation mode to improve the anti-interference capability of the link
that carries high-priority services.
Add/Drop A network element that adds/drops the PDH signal or STM-x (x < N) signal
multiplexer to/from the STM-N signal on the SDH transport network.
Adjacent A channel configuration method, which uses two adjacent channels (a
channel horizontal polarization wave and a vertical polarization wave) to transmit
alternate two signals.
polarization
Automatic A method of adjusting the transmit power based on fading of the transmit
transmit power signal detected at the receiver.
control
Issue 01 (2009-12-30) Huawei Proprietary and Confidential H-1

OptiX RTN 620
H Glossary Maintenance Guide
Co-channel A channel configuration method, which uses a horizontal polarization

dual wave and a vertical polarization wave to transmit two signals. The co-
polarization channel dual polarization is twice the transmission capacity of the single
polarization.
Cross A technology used in the case of the co-channel dual polarization (CCDP)
polarization to eliminate the cross-connect interference between two polarization
interference waves in the CCDP.
cancellation
D
DC-C A power system, in which the BGND of the DC return conductor is short-
circuited with the PGND on the output side of the power supply cabinet
and also on the line between the output of the power supply cabinet and
the electric equipment.
DC-I A power system, in which the BGND of the DC return conductor is short-
circuited with the PGND on the output side of the power supply cabinet
and is isolated from the PGND on the line between the output of the power
supply cabinet and the electric equipment.
Digital A digital modulation controls the changes in amplitude, phase, and
modulation frequency of the carrier based on the changes in the baseband digital signal.
In this manner, the information can be transmitted by the carrier.
Dual-polarized An antenna intended to radiate or receive simultaneously two independent
antenna radio waves orthogonally polarized.
E
Equalization A method of avoiding selective fading of frequencies. Equalization can
compensate for the changes of amplitude frequency caused by frequency
selective fading.
Bit error A symptom that the quality of the transmitted information is degraded
because some bits of a data stream are errored after being received,
decided, and regenerated.
Ethernet An Ethernet service type, which carries Ethernet characteristic information
private line over dedicated bandwidth, point-to-point connections, provided by SDH,
service PDH, ATM, or MPLS server layer networks.
virtual private over shared bandwidth, point-to-point connections, provided by SDH,
line service PDH, ATM, or MPLS server layer networks.
private lan over a dedocated bridge, point-to-multipoint connections, provided by
service SDH, PDH, ATM, or MPLS server layer networks.
H-2 Huawei Proprietary and Confidential Issue 01 (2009-12-30)

OptiX RTN 620

virtual private over a shared bridge, point-to-multipoint connections, provided by SDH,
lan service PDH, ATM, or MPLS server layer networks.
F
Forward error A bit error correction technology that adds the correction information to
correction the payload at the transmit end. Based on the correction information, the
bit errors generated during transmission are corrected at the receive end.
Frequency A diversity scheme that enables two or more microwave frequencies with
diversity a certain frequency interval are used to transmit/receive the same signal
and selection is then performed between the two signals to ease the impact
of fading.
G
Gateway A network element that is used for communication between the NE
network application layer and the NM application layer.
element
H
Hybrid radio The hybrid transmission of Native E1 and Native Ethernet signals. Hybrid
radio supports the AM function.
I
Indoor Unit The indoor unit of the split-structured radio equipment. It implements
accessing, multiplexing/demultiplexing, and IF processing for services.
Internet Group The protocol for managing the membership of Internet Protocol multicast
Management groups among the TCP/IP protocols. It is used by IP hosts and adjacent
Protocol multicast routers to establish and maintain multicast group memberships.
Intermediate The transitional frequency between the frequencies of a modulated signal
frequency and an RF signal.
IGMP A multicast constraint mechanism running on a layer 2 device. This
snooping protocol manages and controls the multicast group by listening to and
analyze the Internet Group Management Protocol (IGMP) packet between
hosts and layer 3 devices. In this manner, the spread of the multicast data
on layer 2 network can be prevented efficiently.

OptiX RTN 620
Layer 2 switch A data forwarding method. In LAN, a network bridge or 802.3 Ethernet
switch transmits and distributes packet data based on the MAC address.
Since the MAC address is the second layer of the OSI model, this data
forwarding method is called layer 2 switch.
LCT The local maintenance terminal of a transport network, which is located
on the NE management layer of the transport network.
Link An aggregation that allows one or more links to be aggregated together to
aggregation form a link aggregation group so that a MAC client can treat the link
group aggregation group as if it were a single link.
Trail A type of transport entity, mainly engaged in transferring signals from the
input of the trail source to the output of the trail sink, and monitoring the
integrality of the transferred signals.
M
Multiplex The function performed to provide capability for switching a signal
section between and including two MST functions, from a "working" to a
protection "protection" channel.
N
N+1 protection A microwave link protection system that employs N working channels and
one protection channel.
Network A network element (NE) contains both the hardware and the software
element running on it. One NE is at least equipped with one system control board
which manages and monitors the entire network element. The NE software
runs on the system control Unit.
Network The network management system in charge of the operation,
management administration, and maintenance of a network.
system
Non-gateway A network element whose communication with the NM application layer
network must be transferred by the gateway network element application layer.
element
O
Orderwire A channel that provides voice communication between operation
engineers or maintenance engineers of different stations.
Outdoor unit The outdoor unit of the split-structured radio equipment. It implements
frequency conversion and amplification for RF signals.

OptiX RTN 620
Plesiochronous A multiplexing scheme of bit stuffing and byte interleaving. It multiplexes

Digital the minimum rate 64 kit/s into the 2 Mbit/s, 34 Mbit/s, 140 Mbit/s, and 565
Hierarchy Mbit/s rates.
Polarization A kind of electromagnetic wave, the direction of whose electric field vector
is fixed or rotates regularly. Specifically, if the electric field vector of the
electromagnetic wave is perpendicular to the plane of horizon, this
electromagnetic wave is called vertically polarized wave; if the electric
field vector of the electromagnetic wave is parallel to the plane of horizon,
this electromagnetic wave is called horizontal polarized wave; if the tip of
the electric field vector, at a fixed point in space, describes a circle, this
electromagnetic wave is called circularly polarized wave.
Q
QinQ A layer 2 tunnel protocol based on IEEE 802.1Q encapsulation. It
encapsulates the tag of the user's private virtual local area network (VLAN)
into the tag of the public VLAN. The packet carries two layers of tags to
travel through the backbone network of the carrier. In this manner, the layer
2 virtual private network (VPN) is provided for the user.
R
Rapid An evolution of the Spanning Tree Protocol, providing for faster spanning
Spanning Tree tree convergence after a topology change. The RSTP protocol is backward
Protocol compatible with the STP protocol.
S
Single An antenna that can transmit only one channel of polarized electromagnetic
polarized waves.
antenna
Space diversity A diversity scheme that enables two or more antennas separated by a
specific distance to 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.
Spanning Tree An algorithm defined in the IEEE 802.1D. It configures the active topology
Protocol of a Bridged LAN of arbitrary topology into a single spanning tree.
Subnet A logical entity in the transmission network, which comprises a group of
network management objects. A subnet can contain NEs and other subnets.
Subnetwork A function, which allows a working subnetwork connection to be replaced
connection by a protection subnetwork connection if the working subnetwork
protection connection fails, or if its performance falls below a required level.
Synchronous A hierarchical set of synchronous digital transport, multiplexing, and
Digital cross-connect structures, which is standardized for the transport of suitably
Hierarchy adapted payloads over physical transmission networks.

OptiX RTN 620
U
U2000 A unified network management system developed by Huawei. It can
support all the NE level and network level management functions, and can
manage the transport network, access network, and MAN Ethernet in a
unified manner.
V
Virtual LAN An end-to-end logical network that can travel through several network
segments or networks by using the network management software based
on the switch LAN. The IEEE 802.1Q is the main standard for the virtual
LAN.

OptiX RTN 620
Maintenance Guide I Acronyms and Abbreviations
I Acronyms and Abbreviations
Acronyms and abbreviations are listed in alphabetical order.

A
AM Adaptive Modulation
APS Automatic Protection Switching
ARP Address Resolution Protocol
ATPC Automatic Transmit Power Control
AU Administrative Unit
B
BER Bit Error Rate
BIP Bit-Interleaved Parity
BPDU Bridge Protocol Data Unit
C
CAR Committed Access Rate
CBS Committed Burst Size
CCDP Co-Channel Dual Polarization
CGMP Cisco Group Management Protocol
CIR committed information rate
CLNP connectionless network protocol
CLNS Connectionless Network Service
CoS Class of Service
CPU Central Processing Unit
Issue 01 (2009-12-30) Huawei Proprietary and Confidential I-1

OptiX RTN 620
I Acronyms and Abbreviations Maintenance Guide
CRC cyclic redundancy check

CVLAN Customer VLAN
C-VLAN Customer VLAN
D
DC Direct Current
DCC Data Communications Channel
DCN Data Communication Network
DSCP differentiated services code point
DVMRP Distance Vector Multicast Routing Protocol
E
ECC Embedded Control Channel
EoPDH Ethernet Over PDH
EoS Ethernet Over SDH
EPL Ethernet Private Line
EPLAN Ethernet Private LAN
ERPS Ethernet Ring Protection Switching
ES-IS End System to Intermediate System
EVPL Ethernet Virtual Private Line
F
FCS Frame Check Sequence
FD Frequency Diversity
FE Fast Ethernet
FIFO First In First Out
FLP Fast Link Pulse
FTP file transfer protocol
G
GE Gigabit Ethernet
GFP Generic Framing Procedure
I-2 Huawei Proprietary and Confidential Issue 01 (2009-12-30)

OptiX RTN 620
GTS Generic Traffic Shaping

GUI Graphical User Interface
H
HDLC High level Data Link Control procedure
HSB Hot Standby
HSM Hitless Switch Mode
I
ICMP Internet Control Message Protocol
IDU Indoor Unit
IEEE Institute of Electrical and Electronics Engineers
IETF The Internet Engineering Task Force
IF Intermediate Frequency
IGMP Internet Group Management Protocol
IP Internet Protocol
IPv6 Internet Protocol version 6
IS-IS Intermediate System to Intermediate System
ISO International Standard Organization
ITU-T International Telecommunication Union - Telecommunication
Standardization Sector
IVL Independence VLAN learning
L
LAN Local Area Network
LAPD Link Access Procedure on the D channel
LAPS Link Access Procedure-SDH
LCAS Link Capacity Adjustment Scheme
LCT Generation-Local Craft Terminal
LMSP Linear Multiplex Section Protection
M
MAC Medium Access Control

OptiX RTN 620
MBS Maximum Burst Size

MDI Medium Dependent Interface
MIB Management Information Base
MPLS multiprotocol label switching
MSP Multiplex Section Protection
MTU Maximum Transmission Unit
N
NE Network Element
NLP Normal Link Pulse
NMS Network Management System
NNI Network-to-Network Interface or Network Node Interface
NSAP Network Service Access Point
O
ODU Outdoor Unit
OSI Open Systems Interconnection
OSPF Open Shortest Path First
P
PDH Plesiochronous Digital Hierarchy
PIM-DM Protocol Independent Multicast-Dense Mode
PIM-SM Protocol Independent Multicast-Sparse Mode
PPP Point-to-Point Protocol
Q
QinQ 802.1Q in 802.1Q
QoS Quality of Service
R
RF radio frequency
RFC Request For Comment

OptiX RTN 620
RIP Routing Information Protocol

RMON Remote Monitoring
RSL Received Signal Level
RSTP Rapid Spanning Tree Protocol
RTN Radio Transmission Node
S
SD Space Diversity
SDH Synchronous Digital Hierarchy
SNC SubNetwork Connection
SNCP Sub-Network Connection Protection
SNMP Simple Network Management Protocol
SNR Signal-to-Noise Ratio
STM Synchronous Transport Module
STM-1 SDH Transport Module -1
STM-1e STM-1 Electrical Interface
STM-1o STM-1 Optical Interface
STM-4 SDH Transport Module -4
STM-N SDH Transport Module -N
STP Spanning Tree Protocol
SVL Shared VLAN Learning
T
TCI Tag Control Information
TCP Transfer Control Protocol
TU Tributary Unit
U
UDP User Datagram Protocol
UNI user-network interface

OptiX RTN 620
VC Virtual Container
VC12 Virtual Container -12
VC-12 Virtual Container -12
VCG Virtual Concatenation Group
VLAN Virtual LAN
VoIP Voice over IP
VPN Virtual Private Network
W
WAN Wide Area Network
WRR Weighted Round Robin
WTR Wait to Restore Time
X
XPD Cross-Polarization Discrimination
XPIC Cross-polarization interference cancellation


Maintenance Guide V100R005C00 01 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Maintenance Guide V100R005C00 01 PDF

Uploaded by

Copyright:

Available Formats

OptiX RTN 620 Radio Transmission System

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 01 (2009-12-30) Huawei Proprietary and Confidential i

About This Document

Product Name Version

OptiX RTN 620 V100R005C00

iManager U2000 V100R002C00

l Network planning engineer

Issue 01 (2009-12-30) Huawei Proprietary and Confidential iii

2 Guides to High- Describes the common dangerous maintenance operations.

3 Routine Describes maintenance items and operation procedures for routine

4 Emergency Describes operation procedures for emergency maintenance of the

5 Troubleshooting Describes the causes of common faults and troubleshooting

F Performance Describes the performance management function of the OptiX RTN

H Glossary Lists the terms used in this document.

iv Huawei Proprietary and Confidential Issue 01 (2009-12-30)

Indicates a hazard with a high level of risk,

Indicates a hazard with a medium or low level

Indicates a potentially hazardous situation,

Indicates a tip that may help you solve a

Provides additional information to emphasize

Times New Roman Normal paragraphs are in Times New Roman.

Boldface Names of files, directories, folders, and users are in

Italic Book titles are in italics.

Issue 01 (2009-12-30) Huawei Proprietary and Confidential v

Updates in Issue 01 (2009-12-30)

vi Huawei Proprietary and Confidential Issue 01 (2009-12-30)

About This Document...................................................................................................................iii

Issue 01 (2009-12-30) Huawei Proprietary and Confidential vii

viii Huawei Proprietary and Confidential Issue 01 (2009-12-30)

7.4.2 Querying a Board Manufacture Information Report............................................................................7-16

Issue 01 (2009-12-30) Huawei Proprietary and Confidential ix

x Huawei Proprietary and Confidential Issue 01 (2009-12-30)

Issue 01 (2009-12-30) Huawei Proprietary and Confidential xi

xii Huawei Proprietary and Confidential Issue 01 (2009-12-30)

Issue 01 (2009-12-30) Huawei Proprietary and Confidential xiii

B Abnormal Event Reference.....................................................................................................B-1

C Performance Event Reference................................................................................................C-1

xiv Huawei Proprietary and Confidential Issue 01 (2009-12-30)

C.2.18 RSL_MAX, RSL_MIN, RSL_CUR, and RSL_AVG......................................................................C-29

D RMON Event Reference.........................................................................................................D-1

F Performance Event Management............................................................................................F-1

G Alarm Suppression Relationship.........................................................................................G-1

Issue 01 (2009-12-30) Huawei Proprietary and Confidential xv

Figure 1-1 Wearing an ESD wrist strap...............................................................................................................1-3

Issue 01 (2009-12-30) Huawei Proprietary and Confidential xvii

Figure 7-6 Outloop.............................................................................................................................................7-18

xviii Huawei Proprietary and Confidential Issue 01 (2009-12-30)

Table 4-1 Description of the main procedure of emergency maintenance...........................................................4-4

Issue 01 (2009-12-30) Huawei Proprietary and Confidential xix

Table C-12 AM performance events...................................................................................................................C-9

xx Huawei Proprietary and Confidential Issue 01 (2009-12-30)

Issue 01 (2009-12-30) Huawei Proprietary and Confidential 1-1

1-2 Huawei Proprietary and Confidential Issue 01 (2009-12-30)

Figure 1-1 Wearing an ESD wrist strap

Issue 01 (2009-12-30) Huawei Proprietary and Confidential 1-3

Working at high altitude shall comply with the following requirements:

l Only trained personnel can work at high altitudes.

Hoisting Heavy Objects

1-4 Huawei Proprietary and Confidential Issue 01 (2009-12-30)

Installing and Removing Boards