Maintenance Guide

OptiX RTN 600 Radio Transmission System V100R001
Maintenance Guide
Issue Date Part Number
06 2007-12-30 31501908
Huawei Technologies Proprietary
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For any assistance, please contact our local office or company headquarters.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China http://www.huawei.com support@huawei.com
Website: Email:
Copyright 2007 Huawei Technologies Co., Ltd. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

and other Huawei trademarks are the property of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but the statements, information, and recommendations in this document do not constitute a warranty of any kind, express or implied.
OptiX RTN 600 Radio Transmission System Maintenance Guide
Contents
Contents
About This Document.....................................................................................................................1 1 Routine Maintenance Guide....................................................................................................1-1
1.1 Routine Maintenance Items.............................................................................................................................1-2 1.1.1 Routine Maintenance Items Carried out on an NM System...................................................................1-2 1.1.2 Field Maintenance Items for Indoor Equipment....................................................................................1-2 1.1.3 Field Maintenance Items for Outdoor Equipment..................................................................................1-3 1.2 Guide to Routine Maintenance on an NM System..........................................................................................1-3 1.2.1 Browsing Alarms....................................................................................................................................1-3 1.2.2 Browsing Abnormal Events...................................................................................................................1-4 1.2.3 Browsing Performance Events...............................................................................................................1-4 1.2.4 Testing the IF 1+1 Switching.................................................................................................................1-5 1.3 Guide to Field IDU Maintenance....................................................................................................................1-6 1.3.1 Cleaning the Air Filter............................................................................................................................1-6 1.3.2 Testing the Orderwire Phone..................................................................................................................1-7 1.3.3 Checking the Equipment Room.............................................................................................................1-8 1.4 Guide to Field Maintenance of Outdoor Equipment.......................................................................................1-8 1.4.1 Checking the ODU.................................................................................................................................1-8 1.4.2 Checking the Hybrid Coupler................................................................................................................1-9 1.4.3 Checking the Antenna..........................................................................................................................1-10 1.4.4 Checking IF Cables..............................................................................................................................1-10
2 Troubleshooting Guide.............................................................................................................2-1
2.1 General Fault Locating Procedures.................................................................................................................2-2 2.2 Troubleshooting Service Interruptions............................................................................................................2-4 2.3 Troubleshooting Microwave Links.................................................................................................................2-7 2.4 Troubleshooting Bit Errors............................................................................................................................2-12 2.5 Troubleshooting Pointer Justifications..........................................................................................................2-18 2.6 Troubleshooting the Interconnection with the SDH Equipment...................................................................2-22 2.7 Troubleshooting the Interconnection with the PDH Equipment...................................................................2-26 2.8 Troubleshooting Ethernet Service Faults......................................................................................................2-28 2.9 Troubleshooting the Orderwire.....................................................................................................................2-34
3 Common Maintenance Operation Guide..............................................................................3-1

3.1 Loopback.........................................................................................................................................................3-2 Issue 06 (2007-12-30) Huawei Technologies Proprietary i
Contents
OptiX RTN 600 Radio Transmission System Maintenance Guide 3.1.1 Setting Loopback for the SDH Optical Interface Board........................................................................3-2 3.1.2 Setting Loopback for the SDH Electrical Interface Board.....................................................................3-3 3.1.3 Setting Loopback of the PDH Interface Board......................................................................................3-5 3.1.4 Setting Loopback for the IF Board.........................................................................................................3-6 3.1.5 Setting Loopback for Ethernet Service Processing Boards....................................................................3-8
3.2 Part Replacement...........................................................................................................................................3-10 3.2.1 Removing a Board................................................................................................................................3-10 3.2.2 Inserting a Board..................................................................................................................................3-12 3.2.3 Replacing the SDH Optical Interface Board........................................................................................3-13 3.2.4 Replacing the SDH Electrical Interface Board.....................................................................................3-14 3.2.5 Replacing the PDH Interface Board.....................................................................................................3-15 3.2.6 Replacing the Ethernet Service Processing Board...............................................................................3-16 3.2.7 Replacing the IF Board........................................................................................................................3-16 3.2.8 Replacing the PXC board.....................................................................................................................3-17 3.2.9 Replacing the SCC Board....................................................................................................................3-18 3.2.10 Replacing the Fan Board....................................................................................................................3-20 3.2.11 Replacing the ODU............................................................................................................................3-21 3.3 Cleaning Fiber Connectors and Adapters......................................................................................................3-23 3.3.1 Cleaning Fiber Connectors Using Cartridge Cleaners.........................................................................3-23 3.3.2 Cleaning Fiber Connectors Using Lens Tissue....................................................................................3-25 3.3.3 Cleaning Fiber Adapters Using Optical Cleaning Sticks.....................................................................3-26
A Alarm Reference.......................................................................................................................A-1
A.1 Alarm List......................................................................................................................................................A-1 A.2 Alarms and Corrective procedures................................................................................................................A-8 A.2.1 A_LOC.................................................................................................................................................A-8 A.2.2 APS_MANU_STOP.............................................................................................................................A-9 A.2.3 ALM_GFP_dCSF...............................................................................................................................A-10 A.2.4 ALM_GFP_dLFD..............................................................................................................................A-11 A.2.5 ALM_RTC_FAIL...............................................................................................................................A-12 A.2.6 APS_FAIL..........................................................................................................................................A-13 A.2.7 APS_INDI..........................................................................................................................................A-15 A.2.8 AU_AIS..............................................................................................................................................A-16 A.2.9 AU_LOP.............................................................................................................................................A-17 A.2.10 B1_EXC...........................................................................................................................................A-18 A.2.11 B1_SD..............................................................................................................................................A-19 A.2.12 B2_EXC...........................................................................................................................................A-20 A.2.13 B2_SD..............................................................................................................................................A-21 A.2.14 B3_EXC...........................................................................................................................................A-22 A.2.15 B3_EXC_VC3..................................................................................................................................A-23 A.2.16 B3_SD..............................................................................................................................................A-24 A.2.17 B3_SD_VC3.....................................................................................................................................A-25 A.2.18 BD_NOT_INSTALLED..................................................................................................................A-26 ii Huawei Technologies Proprietary Issue 06 (2007-12-30)
Contents
A.2.19 BD_STATUS...................................................................................................................................A-27 A.2.20 BIP_EXC..........................................................................................................................................A-30 A.2.21 BIP_SD.............................................................................................................................................A-31 A.2.22 CONFIG_NOSUPPORT..................................................................................................................A-32 A.2.23 DBMS_ERROR...............................................................................................................................A-33 A.2.24 DBMS_PROTECT_MODE.............................................................................................................A-35 A.2.25 DN_E1_AIS.....................................................................................................................................A-36 A.2.26 E1_LOC............................................................................................................................................A-37 A.2.27 E1_LOS............................................................................................................................................A-38 A.2.28 ESN_FAILED..................................................................................................................................A-39 A.2.29 ESN_INVALID................................................................................................................................A-40 A.2.30 ETH_LOS.........................................................................................................................................A-41 A.2.31 EXT_SYNC_LOS............................................................................................................................A-42 A.2.32 FAN_FAIL.......................................................................................................................................A-43 A.2.33 FCS_ERR.........................................................................................................................................A-44 A.2.34 HARD_BAD....................................................................................................................................A-46 A.2.35 HP_CROSSTR.................................................................................................................................A-48 A.2.36 HP_LOM..........................................................................................................................................A-49 A.2.37 HP_RDI............................................................................................................................................A-50 A.2.38 HP_REI.............................................................................................................................................A-51 A.2.39 HP_SLM...........................................................................................................................................A-52 A.2.40 HP_TIM............................................................................................................................................A-54 A.2.41 HP_UNEQ........................................................................................................................................A-55 A.2.42 HPAD_CROSSTR...........................................................................................................................A-56 A.2.43 HSB_INDI........................................................................................................................................A-57 A.2.44 HSM_INDI.......................................................................................................................................A-58 A.2.45 IF_INPWR_ABN.............................................................................................................................A-59 A.2.46 IN_PWR_HIGH...............................................................................................................................A-61 A.2.47 IN_PWR_LOW................................................................................................................................A-62 A.2.48 J0_MM.............................................................................................................................................A-63 A.2.49 K1_K2_M.........................................................................................................................................A-64 A.2.50 K2_M................................................................................................................................................A-66 A.2.51 LASER_CLOSED............................................................................................................................A-67 A.2.52 LASER_MOD_ERR_EX.................................................................................................................A-68 A.2.53 LCAS_FOPR....................................................................................................................................A-69 A.2.54 LCAS_FOPT....................................................................................................................................A-71 A.2.55 LCAS_PLCR....................................................................................................................................A-72 A.2.56 LCAS_PLCT....................................................................................................................................A-73 A.2.57 LCAS_TLCR....................................................................................................................................A-75 A.2.58 LCAS_TLCT....................................................................................................................................A-76 A.2.59 LOOP_ALM.....................................................................................................................................A-77 A.2.60 LPS_UNI_BI_M...............................................................................................................................A-79 Issue 06 (2007-12-30) Huawei Technologies Proprietary iii
Contents
OptiX RTN 600 Radio Transmission System Maintenance Guide A.2.61 LP_CROSSTR..................................................................................................................................A-80 A.2.62 LP_R_FIFO......................................................................................................................................A-81 A.2.63 LP_RDI.............................................................................................................................................A-82 A.2.64 LP_RDI_VC12.................................................................................................................................A-83 A.2.65 LP_RDI_VC3...................................................................................................................................A-84 A.2.66 LP_REI.............................................................................................................................................A-85 A.2.67 LP_REI_VC12.................................................................................................................................A-86 A.2.68 LP_REI_VC3...................................................................................................................................A-86 A.2.69 LP_RFI.............................................................................................................................................A-87 A.2.70 LP_SIZE_ERR.................................................................................................................................A-88 A.2.71 LP_SLM...........................................................................................................................................A-89 A.2.72 LP_SLM_VC12................................................................................................................................A-90 A.2.73 LP_SLM_VC3..................................................................................................................................A-91 A.2.74 LP_T_FIFO......................................................................................................................................A-92 A.2.75 LP_TIM............................................................................................................................................A-93 A.2.76 LP_TIM_VC12.................................................................................................................................A-94 A.2.77 LP_TIM_VC3...................................................................................................................................A-95 A.2.78 LP_UNEQ........................................................................................................................................A-96 A.2.79 LP_UNEQ_VC12.............................................................................................................................A-97 A.2.80 LP_UNEQ_VC3...............................................................................................................................A-98 A.2.81 LSR_NO_FITED............................................................................................................................A-100 A.2.82 LTI..................................................................................................................................................A-100 A.2.83 MS_AIS..........................................................................................................................................A-102 A.2.84 MS_CROSSTR...............................................................................................................................A-103 A.2.85 MS_RDI.........................................................................................................................................A-104 A.2.86 MS_REI..........................................................................................................................................A-105 A.2.87 MSAD_CROSSTR.........................................................................................................................A-106 A.2.88 MSSW_DIFFERENT.....................................................................................................................A-107 A.2.89 MW_FECUNCOR.........................................................................................................................A-108 A.2.90 MW_LIM.......................................................................................................................................A-109 A.2.91 MW_LOF.......................................................................................................................................A-111 A.2.92 MW_RDI........................................................................................................................................A-111 A.2.93 NESF_LOST..................................................................................................................................A-112 A.2.94 NESTATE_INSTALL....................................................................................................................A-114 A.2.95 NO_BD_SOFT...............................................................................................................................A-115 A.2.96 POWER_ALM...............................................................................................................................A-116 A.2.97 POWER_FAIL...............................................................................................................................A-117 A.2.98 PS....................................................................................................................................................A-118 A.2.99 R_F_RST........................................................................................................................................A-119 A.2.100 R_LOC.........................................................................................................................................A-120 A.2.101 R_LOF..........................................................................................................................................A-121 A.2.102 R_LOS..........................................................................................................................................A-123
iv
Issue 06 (2007-12-30)
Contents
A.2.103 R_S_ERR.....................................................................................................................................A-125 A.2.104 RADIO_MUTE............................................................................................................................A-126 A.2.105 RADIO_RSL_HIGH....................................................................................................................A-127 A.2.106 RADIO_RSL_LOW.....................................................................................................................A-128 A.2.107 RADIO_TSL_HIGH....................................................................................................................A-130 A.2.108 RADIO_TSL_LOW.....................................................................................................................A-131 A.2.109 RELAY_ALARM........................................................................................................................A-132 A.2.110 RP_LOC.......................................................................................................................................A-132 A.2.111 RS_CROSSTR.............................................................................................................................A-133 A.2.112 S1_SYN_CHANGE.....................................................................................................................A-134 A.2.113 SYN_BAD....................................................................................................................................A-135 A.2.114 SYNC_C_LOS.............................................................................................................................A-136 A.2.115 T_ALOS.......................................................................................................................................A-137 A.2.116 T_F_RST......................................................................................................................................A-139 A.2.117 T_FIFO_E.....................................................................................................................................A-140 A.2.118 T_LOC..........................................................................................................................................A-141 A.2.119 T_LOS..........................................................................................................................................A-142 A.2.120 TEMP_ALARM...........................................................................................................................A-143 A.2.121 TU_AIS........................................................................................................................................A-145 A.2.122 TU_AIS_VC12.............................................................................................................................A-146 A.2.123 TU_AIS_VC3...............................................................................................................................A-148 A.2.124 TU_LOP.......................................................................................................................................A-150 A.2.125 TU_LOP_VC12............................................................................................................................A-151 A.2.126 TU_LOP_VC3..............................................................................................................................A-152 A.2.127 UP_E1_AIS..................................................................................................................................A-153 A.2.128 VCAT_LOA.................................................................................................................................A-154 A.2.129 VCAT_LOM_VC12.....................................................................................................................A-155 A.2.130 VCAT_LOM_VC3.......................................................................................................................A-157 A.2.131 VCAT_SQM_VC12.....................................................................................................................A-158 A.2.132 VCAT_SQM_VC3.......................................................................................................................A-159 A.2.133 VOLT_LOS..................................................................................................................................A-160 A.2.134 WRG_BD_TYPE.........................................................................................................................A-162 A.2.135 WRG_DEV_TYPE.......................................................................................................................A-163 A.2.136 WS_LOS.......................................................................................................................................A-164 A.2.137 XCP_INDI....................................................................................................................................A-165
B Performance Event Reference.................................................................................................B-1

B.1 Performance Event List..................................................................................................................................B-1 B.1.1 SDH Performance Event List................................................................................................................B-1 B.1.2 Microwave Performance Event List.....................................................................................................B-4 B.1.3 Other Performance Event List..............................................................................................................B-4 B.2 Performance Events and Corrective Procedures............................................................................................B-5 B.2.1 AUPJCHIGH, AUPJCLOW and AUPJCNEW....................................................................................B-5 Issue 06 (2007-12-30) Huawei Technologies Proprietary v
Contents
OptiX RTN 600 Radio Transmission System Maintenance Guide B.2.2 TUPJCHIGH, TUPJCLOW and TUPJCNEW.....................................................................................B-6 B.2.3 RSBBE, RSES, RSSES, RSCSES and RSUAS...................................................................................B-7 B.2.4 RSOOF and RSOFS..............................................................................................................................B-8 B.2.5 MSBBE, MSES, MSSES, MSCSES and MSUAS...............................................................................B-9 B.2.6 MSFEBBE, MSFEES, MSFESES, MSFECSES and MSFEUAS......................................................B-10 B.2.7 HPBBE, HPES, HPSES, HPCSES and HPUAS................................................................................B-11 B.2.8 HPFEBBE, HPFEES, HPFESES, HPFECSES and HPFEUAS.........................................................B-12 B.2.9 VC3BBE, VC3ES, VC3SES, VC3CSES, VC3UAS..........................................................................B-13 B.2.10 VC3FEBBE, VC3FEES, VC3FESES, VC3FECSES, VC3FEUAS.................................................B-14 B.2.11 LPBBE, LPES, LPSES, LPCSES and LPUAS.................................................................................B-15 B.2.12 LPFEBBE, LPFEES, LPFESES, LPFECSES and LPFEUAS.........................................................B-16 B.2.13 TSLMAX, TSLMIN and TSLCUR..................................................................................................B-17 B.2.14 RSLMAX, RSLMIN and RSLCUR.................................................................................................B-18 B.2.15 FEC_BEF_COR_ER, FEC_COR_BYTE_CNT...............................................................................B-18 B.2.16 TPLMAX, TPLMIN and TPLCUR..................................................................................................B-19 B.2.17 RPLMAX, RPLMIN and RPLCUR.................................................................................................B-19 B.2.18 BDTMPMAX, BDTMPMIN and BDTMPCUR..............................................................................B-20
C Ethernet RMON Performance List........................................................................................C-1 D Alarm Management.................................................................................................................D-1

D.1 NE Alarm Management.................................................................................................................................D-1 D.2 Board Alarm Management............................................................................................................................D-1 D.2.1 Setting the Alarm Level........................................................................................................................D-1 D.2.2 Alarm Suppression...............................................................................................................................D-1 D.2.3 Alarm Auto-Report...............................................................................................................................D-1 D.2.4 Alarm Reversion...................................................................................................................................D-2 D.2.5 Setting Bit Error Alarm Threshold.......................................................................................................D-2 D.2.6 AIS Insertion........................................................................................................................................D-3 D.2.7 UNEQ Insertion....................................................................................................................................D-4
E Performance Event Management...........................................................................................E-1

E.1 NE Performance Event Management.............................................................................................................E-1 E.2 Board Performance Event Management.........................................................................................................E-1
F Alarm Suppression Relation...................................................................................................F-1 G Glossary..................................................................................................................................... G-1 H Acronyms and Abbreviations...............................................................................................H-1 Index.................................................................................................................................................i-1
vi
Issue 06 (2007-12-30)
Figures
Figures
Figure 1 Wearing an ESD wrist strap......................................................................................................................6 Figure 2-1 General fault locating procedures.......................................................................................................2-3 Figure 2-2 Flow of handling service interruptions...............................................................................................2-5 Figure 2-3 Flow of handling microwave link faults...........................................................................................2-10 Figure 2-4 Flow of handling bit errors...............................................................................................................2-16 Figure 2-5 Flow of handling pointer justifications.............................................................................................2-20 Figure 2-6 Flow of troubleshooting the interconnection with the SDH equipment...........................................2-24 Figure 2-7 Flow of troubleshooting the interconnection with the PDH equipment...........................................2-27 Figure 2-8 Flow of handling Ethernet service faults..........................................................................................2-30 Figure 2-9 Flow of handling RMON abnormal performance events.................................................................2-33 Figure 2-10 Flow of handling orderwire faults..................................................................................................2-35 Figure 3-1 Optical interface inloop......................................................................................................................3-2 Figure 3-2 Optical interface outloop....................................................................................................................3-2 Figure 3-3 VC-4 path outloop..............................................................................................................................3-3 Figure 3-4 Electrical interface inloop ..................................................................................................................3-4 Figure 3-5 Electrical interface outloop.................................................................................................................3-4 Figure 3-6 VC-4 path outloop .............................................................................................................................3-4 Figure 3-7 Tributary inloop..................................................................................................................................3-5 Figure 3-8 Tributary outloop................................................................................................................................3-6 Figure 3-9 IF port inloop......................................................................................................................................3-7 Figure 3-10 IF port outloop..................................................................................................................................3-7 Figure 3-11 VC-4 path inloop..............................................................................................................................3-7 Figure 3-12 Inloop of an Ethernet port.................................................................................................................3-8 Figure 3-13 Inloop of a VC-3 path ......................................................................................................................3-9 Figure 3-14 Outloop of a VC-3 path ...................................................................................................................3-9 Figure 3-15 Removing a board (1).....................................................................................................................3-11 Figure 3-16 Removing a board (2) ....................................................................................................................3-11 Figure 3-17 Removing a board (3).....................................................................................................................3-11 Figure 3-18 Inserting a board (1).......................................................................................................................3-12 Figure 3-19 Inserting a board (2).......................................................................................................................3-13 Figure 3-20 Inserting a board (3).......................................................................................................................3-13 Figure 3-21 Remove the portable memory card.................................................................................................3-19 Figure 3-22 Pulling out the fan tray assembly...................................................................................................3-20 Issue 06 (2007-12-30) Huawei Technologies Proprietary vii
Figures
OptiX RTN 600 Radio Transmission System Maintenance Guide Figure 3-23 Removing the fan board.................................................................................................................3-21
Figure 3-24 CLETOP cassette cleaner...............................................................................................................3-23 Figure 3-25 Dragging the fiber tip slightly on one cleaning area.......................................................................3-24 Figure 3-26 Dragging the fiber tip slightly on the other cleaning area..............................................................3-24 Figure 3-27 Cleaning the fiber with the lens tissue ...........................................................................................3-25
viii
Issue 06 (2007-12-30)
Tables
Tables
Table 1-1 Routine maintenance items carried out on an NM system...................................................................1-2 Table 1-2 Field maintenance items for indoor equipment....................................................................................1-2 Table 1-3 Field maintenance items for outdoor equipment..................................................................................1-3 Table 2-1 Flow description...................................................................................................................................2-4 Table 2-2 Flow description...................................................................................................................................2-6 Table 2-3 Causes of microwave link faults..........................................................................................................2-8 Table 2-4 Flow description.................................................................................................................................2-11 Table 2-5 Causes of bit errors.............................................................................................................................2-14 Table 2-6 Flow description.................................................................................................................................2-16 Table 2-7 Flow description.................................................................................................................................2-21 Table 2-8 Flow description.................................................................................................................................2-25 Table 2-9 Flow description.................................................................................................................................2-28 Table 2-10 Flow description...............................................................................................................................2-31 Table 2-11 Flow description...............................................................................................................................2-33 Table 2-12 Flow description...............................................................................................................................2-36 Table 3-1 Part replacement description..............................................................................................................3-10 Table A-1 Alarm List...........................................................................................................................................A-1 Table B-1 Pointer justification performance event list........................................................................................B-1 Table B-2 Regenerator section error performance event list...............................................................................B-1 Table B-3 Multiplex section error performance event list...................................................................................B-2 Table B-4 Higher order path error performance event list...................................................................................B-2 Table B-5 VC-3 path bit error performance event list.........................................................................................B-3 Table B-6 Lower order path error performance event list...................................................................................B-3 Table B-7 Microwave power performance event list...........................................................................................B-4 Table B-8 FEC performance event .....................................................................................................................B-4 Table B-9 Optical power performance event list.................................................................................................B-4 Table B-10 Board temperature performance event list........................................................................................B-5 Table C-1 Ethernet RMON performance event list.............................................................................................C-1 Table C-2 Ethernet RMON performance list.......................................................................................................C-2 Table D-1 Setting of the bit error alarm threshold..............................................................................................D-2 Table D-2 Setting of AIS insertion......................................................................................................................D-3 Table D-3 Setting of UNEQ insertion.................................................................................................................D-4 Table E-1 Board performance event management function................................................................................E-1 Issue 06 (2007-12-30) Huawei Technologies Proprietary ix
Tables
OptiX RTN 600 Radio Transmission System Maintenance Guide Table F-1 Alarm suppression relation..................................................................................................................F-1
Issue 06 (2007-12-30)
About This Document
About This Document
Purpose
This document is an operation guide on routine maintenance and troubleshooting provided for maintenance engineers. 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 OptiX RTN 600 OptiX iManager T2000 Version V100R001 V200R005C01
Intended Audience
This document is intended for the maintenance engineers of the OptiX RTN 600. Before reading this document, you need to:
l l
Know microwave communication basics. Know the basics of the OptiX RTN 600 product.
Organization
This document is organized as follows.
Issue 06 (2007-12-30)
About This Document
Title Chapter 1 Routine Maintenance Guide 2 Troubleshooting Guide 3 Common Maintenance Operation Guide A Alarm Reference B Performance Event Reference C Ethernet RMON Performance List D Alarm Management E Performance Event Management F Alarm Suppression Relation G Glossary H Acronyms and Abbreviations
Content Describes maintenance items and operation procedures for routine maintenance of the OptiX RTN 600. Describes the causes of common faults and troubleshooting procedures of the OptiX RTN 600. Describes common maintenance operations of the OptiX RTN 600.
Describes all the possible alarms and clearing procedures of the OptiX RTN 600. Describes all the performance events and clearing procedures of the OptiX RTN 600. Describes the ethernet RMON performance of the OptiX RTN 600. Describes the alarm management function of the OptiX RTN 600. Describes the performance management function of the OptiX RTN 600. Describes the alarm suppression relation of the OptiX RTN 600.
Lists the terms used in this document. Lists the acronyms and abbreviations used in this document.
Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows. Symbol Description
DANGER
Indicates a hazard with a high level of risk that, 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.
WARNING
2
Issue 06 (2007-12-30)
About This Document
Symbol
Description
CAUTION
NOTE
Indicates a potentially hazardous situation that, if not avoided, could cause equipment damage, data loss, and performance degradation, or unexpected results. Provides additional information to emphasize or supplement important points of the main text. Indicates a tip that may help you solve a problem or save your time.
TIP
General Conventions
Convention Times New Roman Boldface Italic Courier New Description Normal paragraphs are in Times New Roman. Names of files, directories, folders, and users are in boldface. For example, log in as user root. Book titles are in italics. Terminal display is in Courier New.
GUI Conventions
Convention Boldface > Description Buttons, menus, parameters, tabs, window, and dialog titles are in boldface. For example, click OK. Multi-level menus are in boldface and separated by the > signs. For example, choose File > Create > Folder.
Mouse Operation
Action Click Double-click Drag Description Select and release the primary mouse button without moving the pointer. Press the primary mouse button twice continuously and quickly without moving the pointer. Press and hold the primary mouse button and move the pointer to a certain position.
Issue 06 (2007-12-30)
About This Document
Safety Precautions
This section describes parts of the safety precautions. Read and follow these safety precautions before installing and maintaining the OptiX RTN 600.
CAUTION
Before performing any operation, go through the instructions and precautions carefully to minimize the possibility of accidents. The Caution, Warning and Danger items in other documents do not cover all the safety precautions that must be followed. They are only supplements to the safety precautions for operations as a whole. The personnel in charge of the installation and maintenance must be trained to learn the proper operating methods and all safety precautions. Only the trained and qualified personnel can install or maintain the device. When operating the device, abide by the local safety regulations. The precautions listed in this chapter are in compliance with the local safety regulations. When operating the Huawei device, follow the full precautions and special safety instructions from Huawei. The personnel in charge of installation and maintenance must understand the basics of the safety operations. Only trained and qualified personnel can install or maintain the device.
High Voltage
DANGER
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. 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.
Do not wear conducting articles, such as watches, chains, bracelets and rings while performing high voltage operations. Switch off the power supply immediately if you find water in the rack or if the rack is damp. Make sure that the device is kept away from water when being operated in a damp environment.
l l
Issue 06 (2007-12-30)
About This Document
Power Cable
DANGER
l
Do not install or remove a live line. Transient contact between the core of the power cable and the conductor might generate electric arc or spark, which can cause fire or damage to the human body. During high voltage and AC operations, special tools must be used instead of common tools.
l l
Before installing or removing the power cable, turn off the power switch. Before connecting the power cable, make sure that the power cable and label conform to the requirements of the actual installation.
Thunderstorm
DANGER
High voltage and AC operations, or operations on a steel tower and a mast on a thunderstorm day are prohibited. On a thunderstorm day, the electromagnetic field generated in the thunderstorm area may cause damage to electronic parts. To prevent the device from being damaged by lightning, use proper grounding.
Electrostatic Discharge
CAUTION
The static electricity generated by the human body can damage the electrostatic sensitive components on the circuit board, such as the large-scale integrated circuit (LIC). Electrostatic discharge (ESD) is caused by body movement, friction between shoes and floor, friction between clothes, and contact with plastic objects. ESD remains in the human body for a long time. Before touching the device or holding the boards, circuit boards, or ASICs, wear a grounded ESD wrist strap. It can prevent the sensitive components from being damaged by the static electricity in the human body.
Issue 06 (2007-12-30)
About This Document
Figure 1 Wearing an ESD wrist strap
Microwave
WARNING
Strong radio frequency can harm the human body. Do not stay too close to the antenna in the emitting direction of the antenna when the microwave communication equipment is working. Before installing or maintaining an antenna in a steel tower or a mast with a large number of transmitter antennas, the operator should coordinate all parties concerned to shut down the transmitter antennas.
Laser
WARNING
Laser radiation can cause injury to your eyes. When handling optical fibers, do not stand close to or look into the optical fiber outlet directly with naked eyes.
High Temperature
WARNING
When the ambient temperature is higher than 55, the surface temperature of the IDU boards may exceed 70. In this case, wear protective gloves before touching the IDU boards.
6 Huawei Technologies Proprietary Issue 06 (2007-12-30)
About This Document
Working at Heights
WARNING
When working at heights, prevent objects from falling down. Working at high altitude shall comply with the following requirements:
l l
Only trained personnel can work at high altitudes. The operating machines and tools should be carried and handled safely to prevent them from falling. Safety measures, such as wearing a helmet and a safety belt, should be taken. In cold areas, warm clothes must be worn before performing any high-altitude operation. Appliances used for lifting objects must be checked and ensured to be intact before performing any high-altitude operation.
l l l
Hoisting Heavy Objects
DANGER
During hoisting heavy objects, do not stand or walk under the boom or the objects.
Sharp Objects
WARNING
When carrying the device with hands, wear protection gloves to avoid injuries caused by sharp objects.
IF Cable
WARNING
Before installing or removing the IF cable, turn off the ODU-PWR power switch on the IF board.
Issue 06 (2007-12-30)
About This Document
Installing and Removing Boards
CAUTION
l l
When inserting a board, handle it gently to avoid distorting the pins on the backplane. Insert the board along the slot guide. Do not allow the board interfaces to come in contact with that of another board as this can cause short-circuit or can damage the board. When holding a board in hand, do not touch the board circuit, components, connectors, or the connection slots.
Bundling Signal Cables
CAUTION
Bundle the signal cables separately from the strong current cables or high voltage cables. The space between two adjacent ties must be at least 150 mm.
Update History
Updates between document versions are cumulative. Therefore, the latest document version contains all updates made to previous versions.
Updates in Issue 06 (2007-12-30)

Sixth Release. Precautions for replacing an ODU are added in 3.2.11 Replacing the ODU.

Fifith Release. Bugs found in the previous version are fixed.

Fourth release. Description of new features of the product is added, including:
l l
Supporting the EFT4 Ethernet transparent transmission board Supporting linear MSP

Third release.
8 Huawei Technologies Proprietary Issue 06 (2007-12-30)
About This Document
Bugs found in the previous version are fixed.

Second release. Bugs found in the previous version are fixed.

Initial release.
Issue 06 (2007-12-30)
1 Routine Maintenance Guide
1
About This Chapter
Routine Maintenance Guide
The aim of routine maintenance is to find and remove hidden fault causes in time before the equipment becomes faulty and services are affected. Simply, nip in the bud. 1.1 Routine Maintenance Items Routine maintenance items are classified into three categories, routine maintenance items carried out on an NM system, field maintenance items for indoor equipment, and field maintenance items for outdoor equipment. 1.2 Guide to Routine Maintenance on an NM System This guide provides operation methods for routine maintenance on a Web LCT. For the methods using a T2000, refer to the T2000 online help. 1.3 Guide to Field IDU Maintenance This guide describes how to carry out routine maintenance for the IDU and the equipment room where the IDU is installed. 1.4 Guide to Field Maintenance of Outdoor Equipment This guide describes how to carry out routine maintenance on site for outdoor equipment.
Issue 06 (2007-12-30)
1-1
1.1 Routine Maintenance Items

Routine maintenance items are classified into three categories, routine maintenance items carried out on an NM system, field maintenance items for indoor equipment, and field maintenance items for outdoor equipment.
1.1.1 Routine Maintenance Items Carried out on an NM System

When NEs are managed by the T2000 or the Web LCT in a centralized manner, carry out the maintenance items in the equipment room where the NM system is. When NEs are not managed in a centralized manner, carry out the maintenance items on site using the Web LCT. Table 1-1 Routine maintenance items carried out on an NM system Maintenance Item Browsing Alarms Browsing Abnormal Events Browsing Performance Events Testing the 1+1 Switching Recommend ed Cycle One week One week Refer To 1.2.1 Browsing Alarms 1.2.2 Browsing Abnormal Events 1.2.3 Browsing Performance Events 1.2.4 Testing the IF 1+1 Switching Remarks -
One week
Half year
Only for the case that the equipment applies the 1+1 configuration Within the 1+1 HSB switching time (< 500 ms), protection services will be interrupted. Hence, carry out a 1+1 HSB switching operation at the time when the traffic volume is small.
1.1.2 Field Maintenance Items for Indoor Equipment

Carry out these field maintenance items in the equipment room where the IDU is installed. Table 1-2 Field maintenance items for indoor equipment Maintenance Item Cleaning the Air Filter
1-2
Recommended Cycle Two months
Refer To 1.3.1 Cleaning the Air Filter
Remarks Only for the IDU 620a
Issue 06 (2007-12-30)
Maintenance Item Testing the Orderwire Phone Checking the Equipment Room
Recommended Cycle Two months
Refer To 1.3.2 Testing the Orderwire Phone 1.3.3 Checking the Equipment Room
Remarks Only for the case that the equipment is equipped with the orderwire phone Only for the case that the equipment is installed indoors
Two months
NOTE
a: When the IDU 620 is installed in an outdoor dust-proof cabinet or the IDU is not installed with an air filter, there is no need to clean the air filter.
1.1.3 Field Maintenance Items for Outdoor Equipment

Carry out these field maintenance items at places where the ODU, hybrid coupler, antenna, and other outdoor equipment are installed. Table 1-3 Field maintenance items for outdoor equipment Maintenance Item Checking the ODU Checking the Hybrid Coupler Checking the Antenna Checking IF Cables Recommended Cycle Half year Half year Refer To 1.4.1 Checking the ODU 1.4.2 Checking the Hybrid Coupler 1.4.3 Checking the Antenna 1.4.4 Checking IF Cables Remarks Carry out a complete check after a level-8 hurricane, an earthquake, or other exceptional circumstances.
Half year Half year
1.2 Guide to Routine Maintenance on an NM System

This guide provides operation methods for routine maintenance on a Web LCT. For the methods using a T2000, refer to the T2000 online help.
1.2.1 Browsing Alarms

Periodically browsing alarms helps you find and remove a fault in time.
Issue 06 (2007-12-30)
1-3
Prerequisite
l l
The Web LCT has a normal communication with the NE. The NE user has the "monitor level" authority or higher.
Tools and Instruments

Web LCT
Procedure
Step 1 Select the NE from the object tree in the NE Explorer. Click Step 2 Check the Auto Refresh check box. Step 3 Browse the displayed alarms. Step 4 If there are newly generated alarms after the last maintenance, notify the fault clearing personnel in a timely manner. For alarm clearing methods, refer to A Alarm Reference. Step 5 Optional: Click Save as, Save the current alarms to a file. ----End on the toolbar.
1.2.2 Browsing Abnormal Events

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

Web LCT
Procedure
Step 1 Select the NE from the object tree in the NE Explorer. Choose Alarm > Browse Abnormal Events from the function tree. Step 2 Check the Prompt New Event Occurs check box. Step 3 Browse the displayed abnormal events. Step 4 Optional: Click Save as, Save the current abnormal events to a file. ----End
1.2.3 Browsing Performance Events

Periodically browsing performance events helps you know the change of the performance of the equipment in time and find incipient faults at the initial phase of a performance degrade.
1-4 Huawei Technologies Proprietary Issue 06 (2007-12-30)
Prerequisite
l l

Web LCT
Procedure
Step 1 Select the board whose performance events you want to query from the object tree in the NE Explorer. Choose Performance > Current Performance from the function tree. Step 2 Set the options for querying performance events. Set as follows:
l l l l l
Set the Monitor Object Filter Condition to All. Set the Monitor Period Settings to 24-Hour. In the Count, select all available performance events. In the Gauge, select all available performance events. In the Options, select only Maximum/Minimum Value.
Step 3 Click Query. Step 4 Browse the displayed performance events. In normal situations, there should be no bit error performance events. The number of pointer justification events should be less than six per day. For the gauge performance events like board temperature, there should be no obvious change when compared with the record values. Step 5 Optional: Click Save as, Save the current performance events to a file. Step 6 Repeat Step 1 to Step 5 to browse the performance events of other boards. ----End
1.2.4 Testing the IF 1+1 Switching

Periodically testing the IF 1+1 switching helps you verify whether the equipment can be normally switched over.
Prerequisite
l l
The Web LCT has a normal communication with the NE. The NE user has the "maintenance level" authority or higher.

Web LCT
Precautions
l
As the manual switching mode is used to carry out the IF 1+1 switching and all manual switching operations belong to the equipment switching (HSB switching), protection
Huawei Technologies Proprietary 1-5
Issue 06 (2007-12-30)
services will be interrupted within the switching time (<1 s). Hence, carry out a switching operation at the time when the traffic volume is small.
l
Before a switching operation, make sure that the standby equipment is in normal conditions. If a switching operation fails, contact Huawei engineers in time.
Procedure
Step 1 Select the NE from the object tree in the NE Explorer. Choose Configuration > IF 1+1 Protection from the function tree. Step 2 In the Slot Mapping Relation dialog box, select the IF board and right-click. In the displayed menu, click Manual to Standby. Step 3 After the equipment operates normally for a period of time, query the alarms and performance events of services. There should be no new alarm or performance event. Step 4 Repeat Step 1. Step 5 In the Slot Mapping Relation dialog box, select the IF board and right-click. In the displayed menu, click Clear. Step 6 After the equipment operates normally for a period of time, query the alarms and performance events of services. There should be no new alarm or performance event. ----End
1.3 Guide to Field IDU Maintenance

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

Periodically checking the air filter ensures that the air intake path of fans is not blocked to avoid too high board temperature due to degraded heat sink of fans.
Prerequisite
None.

An air blower or a clean brush
Procedure
Step 1 Loosen the captive screws on the panel of the fan box. Step 2 Move the cables away from the front of the panel of the fan box. Step 3 Draw out the air filter at the left side.
Step 4 Use an air blower or a clean brush to clean the air filter. Step 5 After the cleaning, insert the air filter back to its original position. Step 6 Tighten the screws on the panel of the fan box. ----End
1.3.2 Testing the Orderwire Phone

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

None.
Procedure
Step 1 Check the status of the orderwire phone. The orderwire phone should meet the following requirements.
l l
The ring current switch "RING" is set to "ON". The dialing mode switch is set to "T", that is, the dual tone multi-frequency mode.
Step 2 Make orderwire calls. 1. Hook-off the orderwire phone and press the "TALK" button. The red indicator on the front of phone set should be lit and you can hear the dialing prompt tone. 2. Make orderwire calls to other NEs. The calls should be normal and the voice should be clear. Step 3 Receive orderwire calls. 1.
Issue 06 (2007-12-30)
The maintenance personnel of other NEs make calls to the orderwire phone.
The phone should ring. 2. Hook-off the phone, press the "TALK" button, and have a conversation. The red indicator on the front of phone set should be lit. The call should be normal and the voice should be clear. ----End
1.3.3 Checking the Equipment Room

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

None.
Procedure
Step 1 Record the thermometer reading in the equipment room. The normal temperature should be between -5 and 45. Step 2 Record the reading of the humidity meter in the equipment room. The normal humidity should be between 5% and 95%. Step 3 Check if the equipment room meets the disaster protection requirements. Ensure the following points:
l
There should be portable foam fire extinguishers in the equipment room. The fire extinguishers should be in their service life. There should be no rain leakage or water penetration in the equipment room. There should be no mice or insects in the equipment room.
l l
Step 4 Clean the equipment room. Ensure that there is no dust on the cabinets, on the equipment shells, in the equipment, on the desks, or on the floor. The equipment should be tidy. ----End
1.4 Guide to Field Maintenance of Outdoor Equipment

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

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

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

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

None.
Procedure
Step 1 Ensure that the coupler is within the protected area of the lightning arrester. For plain areas, the lightning arrester protects the area that is located within an angle of 45 under it. For mountainous areas and the areas where lightning frequently occurs, the lightning arrester protects the area that is located within an angle of 30 under it. Step 2 Ensure that the coupler is reliably fixed on the antenna. Step 3 Ensure that the coupler is not damaged. Step 4 Ensure that the interface between the coupler and the antenna is waterproof. Step 5 Ensure that the interface between the coupler and the ODU is waterproof. ----End
Issue 06 (2007-12-30) Huawei Technologies Proprietary 1-9
1.4.3 Checking the Antenna

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

None.
Procedure
Step 1 Ensure that the antenna is within the protected area of the lightning arrester. For plain areas, the lightning arrester protects the area that is located within an angle of 45 under it. For mountainous areas and the areas where lightning frequently occurs, the lightning arrester protects the area that is located within an angle of 30 under it. Step 2 Ensure that the antenna is reliably fixed on the mast. Step 3 Ensure that the antenna radome is not damaged. Step 4 Ensure that there is no accumulated water in the antenna. Step 5 Check if the fastening bolts on the antenna are loose. Check if the antenna slants from the original position. Ensure that the azimuth angle and the elevation angle of the antenna meet the planned requirements. Step 6 In the case of split mounting, ensure that the installation parts (ODU adapter, antenna adapter, and flexible waveguide) are installed firmly, and that the connectors are fastened. ----End
1.4.4 Checking IF Cables

Periodically checking IF cables helps you find faults and hidden troubles of the cables in time.
Prerequisite
None.

None.
Procedure
Step 1 Check the appearance of cables.
l l l
There should be no bent or twisted cable. There should be no bare copper wire. The bending radius of the cable should be more than 30 cm.
Huawei Technologies Proprietary Issue 06 (2007-12-30)
1-10
Step 2 Check the cable connectors.

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

l l
The grounding clip should be waterproof. The grounding cable should be routed from top downwards. The angle between the grounding cable and the IF cable should not be more than 15 degrees.
----End
Issue 06 (2007-12-30)
1-11
2 Troubleshooting Guide
2
About This Chapter
Troubleshooting Guide
This guide describes the general troubleshooting procedures for the OptiX RTN 600 and provides troubleshooting methods for common faults. 2.1 General Fault Locating Procedures When handling a fault, make a detailed record of the fault phenomenon. Contact Huawei engineers to report problems and obtain technical support. 2.2 Troubleshooting Service Interruptions When services cannot be transmitted due to an equipment failure or link failure, the services are interrupted. 2.3 Troubleshooting Microwave Links When an NE reports MW_LOF or MW_FECUNCOR due to failure or performance degrade of a microwave link, there is a microwave link fault. 2.4 Troubleshooting Bit Errors When an NE reports an alarm or performance event on the regenerator section (RS), multiplex section (MS), higher order path (HP), or lower order path (LP), there are bit errors in services. 2.5 Troubleshooting Pointer Justifications When an NE reports a large amount of justification events of the administrative unit (AU) pointer or the tributary unit (TU) pointer, there are pointer justification faults. 2.6 Troubleshooting the Interconnection with the SDH Equipment In the case that the OptiX RTN 600 is interconnected with the SDH equipment, if the SDH service cannot be transmitted between the equipment sets, there is an interconnection fault. 2.7 Troubleshooting the Interconnection with the PDH Equipment In the case that the OptiX RTN 600 is interconnected with the PDH equipment, if the PDH service cannot be transmitted between the equipment sets, there is an interconnection fault. 2.8 Troubleshooting Ethernet Service Faults An Ethernet service fault might be Ethernet service interruption or Ethernet service degradation. 2.9 Troubleshooting the Orderwire If orderwire calls cannot get through when services are normal, there is an orderwire fault.
2.1 General Fault Locating Procedures

When handling a fault, make a detailed record of the fault phenomenon. Contact Huawei engineers to report problems and obtain technical support.
2-2
Issue 06 (2007-12-30)
Figure 2-1 General fault locating procedures

Start 1 Record the fault phenomenon
Caused by external factors? No
Yes
Other handling procedures
Analyze fault causes and locate the fault
Is the fault cleared? 4 No Report to Huawei
Yes
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
Issue 06 (2007-12-30)
2-3
Table 2-1 Flow description Note Description When recording the fault phenomenon, make a true and detailed record of the entire process of the fault. Record the exact time when the fault occurs, and the operations done before and after the occurrence of the fault. Save the alarms, performance events, and other important information. Faults that are caused by external factors include power failures, fiber faults, environmental faults, and terminal equipment (like switching equipment) faults. If the fault is caused by the equipment, refer to 2.2 Troubleshooting Service Interruptions. Contact Huawei engineers to report problems and obtain technical support.
2.2 Troubleshooting Service Interruptions

When services cannot be transmitted due to an equipment failure or link failure, the services are interrupted.
Fault Causes
l
There are misoperations. The data is wrongly modified. A board/cable is looped back or replaced. The protection switching fails. The transmission NE or link is faulty. There is an interconnection fault. If the transmission equipment and connections are working normally, check if there is a fault in the interconnection between the transmission equipment and the switching equipment.
l l l
Fault Locating Methods

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

Figure 2-2 Flow of handling service interruptions
Start 1 Check out the operations done before the service interruption Is there a wrong operation? No Are service paths protected? No 3 Is there an equipment alarm? Yes Handle the alarm Yes Yes 2 Handle switching failure Cancel the operation
No 4 Is there a line alarm? No 5 Is there an HP alarm? No 6 Is there an LP alarm?
Yes
Handle the alarm
Yes
Handle the alarm
Yes
Handle the alarm 7
Are Ethernet services interrupted? No Is there an interconnection fault? No Yes
Handle the Ethernet services fault
8 Handle the interconnection fault No
Go to the next step Perform loopback operations section by section
Is the fault cleared? Yes End
Issue 06 (2007-12-30)
2-5
Table 2-2 Flow description Note 1 Description Operations that may cause a service interruption are as follows:
l l l l l
Modifying the data configuration Performing loopback operations Shutting down the laser Silencing the ODU Replacing boards/cables
Follow the steps below: 1. Check if there are the protection switching alarms such as HSB_INDI, HSM_INDI, or PS, APS_INDI, or SNCP switching abnormities. If there are no relevant protection switching alarms, anomalies, or APS_FAIL, it indicates that the switching fails. 2. Check if the configuration data of the protection is correct. 3. Check if the status of the standby path is normal.
Pay special attention to:

l l l l l l l l l l l l
POWER_ALM FAN_FAIL HARD_BAD BD_STATUS SYN_BAD NESF_LOST TEMP_ALARM RADIO_RSL_HIGH RADIO_RSL_LOW RADIO_TSL_HIGH RADIO_TSL_LOW IF_INPWR_ABN
2-6
Issue 06 (2007-12-30)
Note 4
Description Pay special attention to:

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

l l l
HP_LOM B3_EXC HP_UNEQ

l l l l l
TU_AIS TU_LOP BIP_EXC T_ALOS LP_UNEQ
Refer to section 2.8 Troubleshooting Ethernet Service Faults. Refer to section 2.6 Troubleshooting the Interconnection with the SDH Equipment or section 2.7 Troubleshooting the Interconnection with the PDH Equipment.
Experience and Summary

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

When an NE reports MW_LOF or MW_FECUNCOR due to failure or performance degrade of a microwave link, there is a microwave link fault. The key to locate a microwave link fault is to check if the transmit power and the receive power are abnormal. 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 l l l l
RADIO_TSL_HIGH RADIO_TSL_LOW TSL_CUR TSL_MAX TSL_MIN

NOTE
For the range of the transmit power, refer to the OptiX RTN 600 Radio Transmission System Product Description.
In the following two cases, the receive power is abnormal. The first case is that the receive power always fails to reach the ideal value (free space receive power > theoretical value - 6 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 l l l l
RADIO_RSL_HIGH RADIO_RSL_LOW RSL_CUR RSL_MAX RSL_MIN

NOTE
For the receiver sensitivity, refer to the OptiX RTN 600 Radio Transmission System Product Description.
Fault Causes
Table 2-3 Causes of microwave link faults Fault The transmit power is abnormal. The receive power is always lower than the ideal value. Common Fault Causes The ODU is faulty.
l l l l
The antenna direction is not properly adjusted. The antennas have different polarization directions. There is a mountain or obstacle in the transmit direction. The performance of the feeder degrades.
The receive power is abnormal due to slow upfading. The receive power is abnormal due to slow downfading. The receive power is abnormal due to fast fading.
2-8
There is an external interference.
The fading margin is not enough.
The multipath fading is severe.
Issue 06 (2007-12-30)
NOTE
Depending on the received level, there is up-fading and down-fading.

l
Up-fading The received level is higher than the value after free space fading. The difference can be 10-odd decibels.
Down-fading The received level is lower than the value after free space fading. The difference can be tens of decibels.
Depending on the fading time, there is fast fading and slow fading.
l
Fast fading The fading duration time ranges from several milliseconds to tens of seconds. Slow fading The fading duration time ranges from tens of seconds to several hours.

1. 2. 3. 4. 5. Check if the ODU is silenced, powered off, or looped back. Check if the data configuration is correct. Check if the ODU and the IF board are faulty. If the transmit power is abnormal, replace the ODU. If the receive power is abnormal, check out the possible causes based on the fading type. If the transmit/receive power is normal, perform loopback operations.
Issue 06 (2007-12-30)
2-9

Figure 2-3 Flow of handling microwave link faults
Start
Yes Is there a wrong operation? No Cancel the operation
Is there an ODU or IF board related fault? No
Yes
Handle the alarm
No Normal transmit power? Yes The receive power always lower than the ideal value? No Yes
3 Handle the fault
4 Handle the fault
5 Abnormal receive Yes power caused by slow upfading? No 6 Abnormal receive power caused by slow down-fading? No 7 Abnormal receive power caused by fast fading? 8 No Perform loopback operations Go to the next step No Is the fault cleared? Yes End Yes Handle the fault Yes Handle the fault Handle the fault
2-10
Issue 06 (2007-12-30)
Table 2-4 Flow description Note Description Check the following points:
l l l l
Check if the ODU is powered off. Check if the ODU is silenced. Check if the IF board is looped back. Check if the data configuration at the transmit side is consistent with that at the receive side. Check if the data configuration matches the type of the ODU and the hybrid coupler.

l l l l l l l
HARD_BAD TEMP_ALARM IF_INPWR_ABN RADIO_MUTE RADIO_TSL_HIGH RADIO_TSL_LOW RADIO_RSL_HIGH
Replace the ODU. Follow the steps below: 1. Check the installation of the antenna. Check if the azimuth angle of the antenna meets the requirement. 2. Check the antenna direction. Check if 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 if the setting of the polarization direction of the antenna is correct. Adjust wrong polarization direction. 4. Check if the antenna gain at both the transmit and receive sides meets the indexes. Replace unqualified antennas. 5. Check if there is a mountain or obstacle in the transmit direction.
Follow the steps below: 1. Use a spectrum analyzer to analyze the interference source. 2. Contact the spectrum management department to clear the interference spectrum. Or change plans to reduce the interference.
Issue 06 (2007-12-30)
2-11
Note
Description Contact the network planning department to make the following changes:
l l l l
Increase the installation height of the antenna. Reduce the transmission distance. Increase the antenna gain. Increase the transmit power.
Contact the network planning department to make the following changes:

l
Adjust the position of the antenna to block the reflected wave or make the reflection point fall on the ground that has a small reflection coefficient, thus reducing the multipath fading. Adjust the RF configuration to make the links in the 1+1 SD configuration. For the links in the 1+1 SD configuration, adjust the height difference between two antennas to make the receive power of one antenna much stronger than that of another. Increase the fading margin.
l l
Follow the steps below: 1. Loop back the IF ports. If the fault is not cleared after the loopback, replace the IF board. 2. Check if the IF cable is soggy, broken or pressed. Replace the unqualified cable. 3. Check if the cable connector is made in accordance with specifications. Remake unqualified ones. 4. Replace the ODU. If the fault is cleared after the replacement, the original ODU is faulty. 5. Replace the IF cable. If the fault is cleared after the replacement, the original IF cable is faulty.

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

When an NE reports an alarm or performance event on the regenerator section (RS), multiplex section (MS), higher order path (HP), or lower order path (LP), there are bit errors in services. The line board detects RS bit errors by the RS overhead byte B1. Related alarms and performance events are listed below:
2-12
Issue 06 (2007-12-30)

l l l l l l l l
B1_EXC B1_SD RS_CROSSTR RSBBE RSES RSSES RSCSES RSUAS

NOTE
When the IF board works in the PDH mode, the above RS bit error alarms and performance events may also be reported. Such alarms and performance events are detected by the B1 that is defined in the PDH microwave frame.
The line board detects MS bit errors by the MS overhead byte B2. Related alarms and performance events are listed below:
l l l l l l l l
B2_EXC B2_SD MS_CROSSTR MSBBE MSES MSSES MSCSES MSUAS
The line board detects HP bit errors by the HP overhead byte B3. Related alarms and performance events are listed below:
l l l l l l l l
B3_EXC B3_SD HP_CROSSTR HPBBE HPES HPSES HPCSES 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 l l l
B3_EXC_VC3_ B3_SD_VC3 BIP_EXC BIP_SD

Issue 06 (2007-12-30)
l l l l l l l l l l l
LP_CROSSTR VC3BBE VC3ES VC3SES VC3CSES VC3UAS LPBBE LPES LPSES LPCSES LPUAS
Fault Causes
Table 2-5 Causes of bit errors Fault Types There are some RS bit errors. Common Causes
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 microwave line, check if there is an MW_FECUNCOR alarm or an HSB_INDI alarm.
l l l
The line board is faulty. The clock unit is faulty. The quality of the clock over the network degrades. When the quality of the clock over the network degrades, there will be a pointer justification event.
There is no RS bit error, but there are MS bit errors or HP bit errors.
l l
The line board is faulty. The quality of the clock over the network degrades. When the quality of the clock over the network degrades, there will be a pointer justification event.
The working temperature of the line board is excessively high. There is power surge or an external interference source, or the equipment is not properly grounded.
2-14
Issue 06 (2007-12-30)
Fault Types There are only LP bit errors.
Common Causes
l
The PDH service processing board or the Ethernet service processing board is faulty. The cross-connect unit is faulty. The working temperature of the PDH service processing board or the Ethernet service processing board is excessively high. The working temperature of the cross-connect unit is excessively high. There is power surge or an external interference source, or the equipment is not properly grounded.
l l

1. 2. 3. 4. 5. Analyze the equipment alarms and performance events that are related to bit errors. 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. When multiple paths have bit errors, first check if the overlapping part is faulty. When the fault is not located after you analyze the alarms and performance events, perform loopback operations section by section. For a possibly degraded component, replace it with a new one.
Issue 06 (2007-12-30)
2-15

Figure 2-4 Flow of handling bit errors
Start
2 1 Is there an equipment alarm? No Is there a pointer justification event? Yes Handle the pointer justification event SDH optical interface board 3 Handle the RS bit error of the SDH optical interface board 4 Is there an RS bit error alarm or a performance event? No Yes If the alarming board is IF board Handle the RS bit error of the IF board 5 Handle the RS bit error of the STM-1 electrical interface board 6 Yes Handle the MS/HP bit error Yes Handle the alarm
No
STM-1 electrical interface board
Is there an MS/HP alarm or a performance event? No Is there an LP alarm? No
7 Yes Handle the LP bit error
Go to the next step Perform loopback operations section by section
No
Is the fault cleared?
Yes End
Table 2-6 Flow description Note Description Pay special attention to:
l l l
TEMP_ALARM SYN_BAD HARD_BAD

Issue 06 (2007-12-30)
2-16
Note
Description Refer to section 2.5 Troubleshooting Pointer Justifications. Follow the steps below: 1. Make an exchange between the Tx fiber core and the Rx fiber core at both ends of the path. If bit errors change after the exchange, the fiber is faulty. Otherwise, the equipment at the two ends is faulty. 2. In the case that the fiber is faulty, check if the fiber between the equipment and the ODF and the section of the fiber that is led out of the equipment room are pressed. Also check if the fiber connector is clean. 3. In the case that the equipment at the two ends is faulty, use a fiber jumper to loop back the optical ports. After the loopback, if the fault is not cleared, the line board is most likely faulty. 4. For the case that the equipment at the two ends is faulty, to locate the fault, you can also replace the board or make an exchange between the board and another board of the same type that is working normally. If the alarm changes after the exchange, the board is faulty.
Follow the steps below: 1. Check if there is an MW_FECUNCOR alarm or an HSB_INDI alarm. 2. If yes, refer to section 2.3 Troubleshooting Microwave Links. 3. If no, replace the IF board.
Follow the steps below: 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 if the cable is properly grounded and if the cable is broken. 3. In the case that the equipment at the two ends is faulty, use a cable to loop back the electrical ports. After the loopback, if the fault is not cleared, the line board is most likely faulty. 4. For the case that the equipment at the two ends is faulty, to locate the fault, you can also replace the board or make an exchange between the board and another board of the same type that is working normally. If the alarm changes after the exchange, the board is faulty.
Follow the steps below: 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 if there is power surge or an external interference source, or if the equipment is not properly grounded (primarily for the SDH electrical interface board).
Issue 06 (2007-12-30)
2-17
Note
Description Follow the steps below: 1. Based on how the service paths that have bit errors overlap each other, replace the PDH service processing board or the Ethernet service processing board or the crocss-connect board. 2. If the fault is not cleared, check if there is power surge or an external interference source, or if the equipment is properly grounded.

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

When an NE reports a large amount of justification events of the administrative unit (AU) pointer or the tributary unit (TU) pointer, there are pointer justification faults. When the position of the first byte of the VC-4 in the AU-4 payload changes, the AU pointer makes a justification accordingly. The performance events of the AU pointer justification are as follows:
l l l
AUPJCHIGH AUPJCLOW AUPJCNEW

NOTE
The AU pointer justification is generated at an upstream NE but is detected and reported at a downstream NE.
When the service is configured to be at the VC-12 level, apply the re-framing process to terminate the AU pointer justification. The terminating method is to transform the AU pointer justification into the TU pointer justification. The performance events of the TU pointer justification are as follows:
l l l
TUPJCHIGH TUPJCLOW TUPJCNEW

NOTE
The TU pointer justification is generated at the NE where the AU pointer is transformed into the TU pointer, but is detected and reported by the tributary board of the NE where services are terminated.
Fault Causes
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. The optical fibers links are wrongly connected. As a result, mutual clock tracing occurs.
2-18

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

When there are both AU pointer justifications and TU pointer justifications in a service path, first handle AU pointer justifications and then TU pointer justifications. Fault Types AU pointer justifications Fault Locating Methods 1. Analyze and clear clock alarms. 2. Correct wrong data configurations and wrong fiber connections. 3. Change the clock and service configurations to find the stations whose clock is asynchronous with the entire network. 4. Replace the components whose performance is possibly poor or degraded to locate a fault. TU pointer justifications 1. Analyze and clear clock alarms. 2. Correct wrong data configurations and wrong fiber connections. 3. Change the clock and service configurations to find the stations whose clock is asynchronous with the entire network. 4. Replace the components whose performance is possibly poor or degraded to locate a fault.
Issue 06 (2007-12-30)
2-19

Figure 2-5 Flow of handling pointer justifications
Start
1 Is there a clock related alarm? 2 No Check the clock configuration
Yes
Handle the alarm
Wrong configuration? No
Yes
Modify the data configuration
Check the fiber connection
Wrongly connected?
Yes Re-connect the fiber
No 4 Is there an AU pointer Yes justification event? No Is there a TU pointer justification event? No Go to the next step Yes Find the NE whose clock is out of synchronization 5 Locate the faulty board
6 Find the NE whose clock is out of synchronization
7 Find the faulty board
No
Is the fault cleared?
Yes End
2-20
Issue 06 (2007-12-30)
l l l l l l l
TEMP_ALARM SYN_BAD HARD_BAD LTI SYNC_C_LOS S1_SYN_CHANGE EXT_SYNC_LOS
Check the following points:

l l
Check if there are two clock reference sources in the entire network. Check if mutual clock tracing occurs.
Query ECC routes to check if the fibers are correctly connected. Check the fiber connection in the east and west directions of the NE that reports the pointer justification event. Follow the steps below: 1. Find a VC-4 channel that reports an AU pointer justification event. 2. Along the service source direction of the VC-4 channel, find the source NE of the entire VC-4 service (not the source NE of a timeslot in the VC-4). 3. Set the clock of the source NE to free-run. Set other NEs to trace the clock of the source NE along the direction of the VC-4 service. 4. Along the clock tracing direction, find the line board that is the first to report the AU pointer justification of the VC-4 channel. The clock of the remote NE to which the line board is connected is asynchronous with the reference clock. Hence, the line board in the remote NE that receives the clock signal, the line board that sends the clock signal to the remote NE, and the clock unit of the remote NE, may be faulty. 5. Set the clock of the sink NE of the VC-4 service to free-run. Set other NEs to trace the clock of the sink NE along the direction of the VC-4 service. 6. Along the clock tracing direction, find the line board that is the first to report the AU pointer justification of the VC-4 channel. The clock of the remote NE to which the line board is connected is asynchronous with the reference clock. Hence, the line board in the remote NE that receives the clock signal, the line board that sends the clock signal to the remote NE, and the clock unit of the remote NE, may be faulty. 7. Compare the results and find out the common points.
Replace the possibly faulty boards.
Issue 06 (2007-12-30)
2-21
Note
Description Follow the steps below: 1. Modify the service configuration to make the NE where the clock reference source is as the central NE. Other NEs has the E1 service of the central NE. 2. Along the clock tracing direction, find the NE that is the first to report the TU pointer justification. The clock of the NE is asynchronous with the reference clock. Hence, the line board in the NE that receives the clock signal, the line board that sends the clock signal to the NE, and the clock unit of the NE, may be faulty. 3. Modify the configuration data to make all NEs trace the clock in another direction. 4. Along the clock tracing direction, find the NE that is the first to report the TU pointer justification. The clock of the NE is asynchronous with the reference clock. Hence, the line board in the NE that receives the clock signal, the line board that sends the clock signal to the NE, and the clock unit of the NE, may be faulty. 5. Compare the results and find out the common points.
NOTE This method is also applicable in locating an AU pointer justification event.
Replace the possibly faulty boards. For a TU pointer justification, check the line board, the clock board, and the tributary board.

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

In the case that the OptiX RTN 600 is interconnected with the SDH equipment, if the SDH service cannot be transmitted between the equipment sets, there is an interconnection fault.
Fault Causes
l
The VC-12 numbering method of Huawei equipment is different from that of some vendors' equipment. The OptiX equipment applies the timeslot numbering method. The numbering formula is: VC-12 number = TUG-3 number + (TUG-2 number - 1) x 3 + (TU-12 number - 1) x 21 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
l l
The overhead bytes at the two sides are inconsistent. The indexes of SDH interfaces do not meet requirements.
2-22

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.
Issue 06 (2007-12-30)
2-23

Figure 2-6 Flow of troubleshooting the interconnection with the SDH equipment
Start
Is the interconnected equipment the ATM/IP equipment? No Query the VC-12 numbering method of the interconnected equipment
Yes
Set the interconnection service to be the VC-4 pass-through service
Is the numbering mode the line numbering? No 1 Is there an overhead setting related alarm? No
Yes
Modify the data configuration. Use the line numbering method to set the VC-12
Yes
Handle the alarm
2 Yes Check the grounding
Is the interface the STM1 electrical interface? 3 No Test the indexes of interfaces
Do the interfaces meet relevant standards?
No
Handle the faults of the interconnected equipment
Yes
Go to the next step Handle the faults of the local equipment
No
Is the fault cleared? Yes
End
2-24
Issue 06 (2007-12-30)
l l l l l l l l l
J0_MM HP_TIM LP_TIM LP_TIM_VC12 LP_TIM_VC3 HP_SLM LP_SLM LP_SLM_VC12 LP_SLM_VC3

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

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

l l l l
Issue 06 (2007-12-30)
2-25

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

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

Analyze the fault phenomenon and alarms. Check the possible fault causes one by one.
2-26
Issue 06 (2007-12-30)

Figure 2-7 Flow of troubleshooting the interconnection with the PDH equipment
Start 1 Check the impedance of the interfaces
Is there an Yes impedance mismatch? No Is the cable the coaxial cable? 3 No Check the cables Yes
Replace the cable or the tributary board 2 Check the grounding
Is in good conditions? 4 Yes Test the indexes of interfaces
No
Adjust the cables
Do the interfaces meet standards? Yes
No
Handle the faults of the interconnected equipment Go to the next step No Is the fault cleared? Yes Handle the faults of the local equipment End
Issue 06 (2007-12-30)
2-27
Table 2-9 Flow description Note Description Check if the type of the tributary board matches the type of the cable. Check the following points:
l
Check if all the equipment and the DDF in the equipment room are jointly grounded. Check if the shielding layer of the coaxial cable connector on the DDF is connected to the protection ground. Check if the shielding layers of coaxial cables are grounded in the same way.
NOTE Disconnect all the signal cables between the interconnecting equipment. Use a multimeter to measure the level between the shielding layers of the coaxial cables at the receive and transmit ends of the 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 l l l
Check if the wires of the cable are correctly connected. Check if the cable is too long (for example, longer than 50 meters). Check if the cable is broken or pressed. Check if the cable signal is interfered (for example, when the trunk cable is bound with the power cable, the cable signal is interfered by the power signal).
Check the following indexes:

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

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

An Ethernet service fault might be Ethernet service interruption or Ethernet service degradation. Ethernet service interruption indicates that the Ethernet service is completely interrupted. Ethernet service degradation indicates that the Ethernet service is abnormal. For example, the
network speed is low, the equipment delay is long, loss of packets occurs, or incorrect packets exist in the received or transmitted data.
Fault Causes
l
Human factors are as follows:

An Ethernet board loopback or a transmission line loopback occurs. The settings of parameters of an Ethernet port such as port enabled, working mode, and flow control are different from those of its interconnected equipment. The configuration of the encapsulation/mapping protocol or the LCAS protocol is different from that of the opposite equipment. The VCTRUNK-bound timeslot is different from that of the opposite equipment.
l l l l l
Equipment faults are as follows: The line board is faulty or has bit errors. The interconnected equipment is faulty. The network cable is faulty. The external electromagnetic interference is severe.

1. 2. 3. Clear the human factors such as a loopback and data configuration error. Locate the fault cause according to the equipment alarm. Locate the fault cause according to the RMON performance event and alarm.
Issue 06 (2007-12-30)
2-29

Figure 2-8 Flow of handling Ethernet service faults
Start
1 Incorrect operation? No 2 Equipment or line alarm? No 3 Ethernet interface alarm? No 4 Ethernet protocol alarm? No 5 Collisions or fragements? No Fault of the opposite equipment? No
Yes
Roll back this operation.
Yes
Handle the alarm.
Yes
Handle the alarm.
Yes
Handle the alarm.
Yes
Troubleshoot according to the flow of handling the RMON performance event.
Yes
Troubleshoot faults of the opposite equipment.
Troubleshoot equipment faults by performing loopbacks section by section or replacing boards.
Proceed with the next step.
No
Are faults cleared? Yes End
2-30
Issue 06 (2007-12-30)
l l l
Whether a loopback is set for the Ethernet board Whether a loopback is set for the transmission line Whether the settings of parameters of an Ethernet port such as port enabled, working mode, and flow control are the same as those of its interconnected equipment Whether the configuration of the encapsulation/mapping protocol or the LCAS protocol is the same as that of the opposite equipment Whether the VCTRUNK-bound timeslot is the same as that of the opposite equipment
Check the following equipment alarms:

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

l l l l l l l l l
Check the following:

l l
ETH_LOS ALM_GFP_dCSF
Issue 06 (2007-12-30)
2-31
Note
Description Check the following:

l l l l l l l l
ALM_GFP_dLFD FCS_ERR LCAS_PLCT LCAS_TLCT LCAS_PLCR LCAS_TLCR LCAS_FOPT LCAS_FOPR
For RMON performance events, refer to C Ethernet RMON Performance List.
2-32
Issue 06 (2007-12-30)
Figure 2-9 Flow of handling RMON abnormal performance events

Start 1 Analyze the RMON performance.
FCS errors? No
Yes
2 Troubleshoot bit errors on the line.
Collisions or fragements? No PAUSE frame? No Test with a meter.
Yes
3 Check the working mode of a port.
Yes
Handle the flow control problem or add bandwidths.
Pass the test? No 5 MTU setting errors? No Troubleshoot equipment faults by performing loopbacks section by section or replacing boards.
Yes
Troubleshoot faults of the opposite equipment.
Yes Modify the MTU value.
Proceed with the next step.
No
Are faults cleared? Yes
End
Table 2-11 Flow description Note Description Refer to C Ethernet RMON Performance List. Refer to section 2.4 Troubleshooting Bit Errors.
Issue 06 (2007-12-30)
2-33
Note
Description Check the following points:

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

l
Whether the flow control mode of this equipment is the same as that of its interconnected equipment Whether the Ethernet service volume is larger that the configured VCTRUNK bandwidth
The Maximum Transmission Unit (MTU) of a network can be tested by a test meter. The maximum frame length that is set for a port must be longer than this maximum network MTU.

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

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

l
Check if the phone set is correctly set, if the phone line is correctly connected, and if the orderwire is correctly configured. Replace a possibly faulty board to check it out.
2-34
Issue 06 (2007-12-30)

Figure 2-10 Flow of handling orderwire faults
Start 1 Check the phone setting
Is the phone correctly set? Yes Is the phone line correctly connected? Yes 2 Check the orderwire configuration
No
Modify the phone setting
No
Re-connect the phone line
Is the configuration correct? Yes 3 Replace the possibly faulty board
No
Modify the configuration
Go to the next step
No
Is the fault cleared? Yes
End
Issue 06 (2007-12-30)
2-35
l l
Check if the ring current switch "RING" on the phone set is set to "ON". Check if the dialing mode switch is set to "T", that is, the dual tone multifrequency mode. An orderwire phone set should be on-hook when it is not in communication, and the upper-right red indicator in the front view of the orderwire phone set should be off. If the red indicator is on, it indicates that the phone set is in the off-hook state. Press the "TALK" button in the front of phone set to hook it up. In some occasions the "TALK" button is pressed by the maintenance personnel due to carelessness. This makes the phone set stay in the offhook state all the time and the orderwire call from other NEs cannot get through.

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

It is necessary to periodically check the orderwire phone set.
2-36
Issue 06 (2007-12-30)
3 Common Maintenance Operation Guide
Common Maintenance Operation Guide
About This Chapter

This part details operations of loopback, part replacement and fiber connector and adapter cleaning that are commonly used in maintenance. 3.1 Loopback Loopback is a most important method to locate faults. In the OptiX RTN 600, the SDH optical interface board, SDH electrical interface board, PDH interface board, IF board and Ethernet service processing board support the loopback. 3.2 Part Replacement Part replacement is a method frequently used to locate faults. The replacement operation varies with the part types. 3.3 Cleaning Fiber Connectors and Adapters The optical connecting components are easily contaminated in the maintenance. The minute dust particles that can be seen only in the microscope can also affect the quality of optical signals. In this case, it downgrades the system performance. Hence, clean the fiber connectors or adapters that are terminated in a timely manner.
Issue 06 (2007-12-30)
3-1
3.1 Loopback
Loopback is a most important method to locate faults. In the OptiX RTN 600, the SDH optical interface board, SDH electrical interface board, PDH interface board, IF board and Ethernet service processing board support the loopback.
3.1.1 Setting Loopback for the SDH Optical Interface Board

The optical interface board of the OptiX RTN 600 supports the outloop of the optical interface and the VC-4 path.
Prerequisite
l l
Context
For the inloop of the optical interface, an SDH signal is looped back at the overhead processing unit to the backplane. Figure 3-1 Optical interface inloop
SDH optical interface board SDH
Backplane
For the outloop of the optical interface, an SDH signal is looped back at the overhead processing unit to the remote equipment. Figure 3-2 Optical interface outloop
Backplane SDH optical interface board SDH
For the outloop of the VC-4 path, a VC-4 signal is looped back at the logic processing unit to the remote equipment.
Figure 3-3 VC-4 path outloop

Backplane SDH optical interface board VC-4
Precaution
CAUTION
Loopback can interrupt the services on the port or the path for which the loopback is performed.
Procedure
Step 1 Select SDH optical interface board in the object tree. Step 2 In the function tree, choose Configuration > SDH Interface. Step 3 Select By Function, and select the loopback mode in the drop-down list. To Perform ... Optical interface loopback VC-4 path loopback Select ... Optical (Electrical) Interface Loopback VC4 Loopback
Step 4 Set the loopback status of the port as needed. Step 5 Click Application. ----End
3.1.2 Setting Loopback for the SDH Electrical Interface Board

The electrical interface board of the OptiX RTN 600 supports the inloop/outloop of the electrical interface and the outloop of the VC-4 path.
Prerequisite
l l
Issue 06 (2007-12-30)
Context
For the inloop of the electrical interface, an SDH signal is looped back at the coding/decoding unit of the board to the backplane. Figure 3-4 Electrical interface inloop
SDH electrical interface board SDH
Backplane
For the outloop of the electrical interface, an SDH signal is looped back at the coding/decoding unit of the board to the remote equipment. Figure 3-5 Electrical interface outloop
Backplane SDH electrical interface board SDH
For the outloop of the VC-4 path, a VC-4 signal is looped back at the logic processing unit of the board to the remote equipment. Figure 3-6 VC-4 path outloop
Backplane SDH electrical interface board VC-4
3-4
Issue 06 (2007-12-30)
Precaution
CAUTION
Procedure
Step 1 Select SDH electrical interface board in the object tree. Step 2 In the function tree, choose Configuration > SDH Interface. Step 3 Select By Function, and in the drop-down list select the loopback mode. To Perform ... Electrical interface loopback VC-4 path loopback Select ... Optical (Electrical) Interface Loopback VC4 Loopback
Step 4 Set the loopback status of the port or path as needed. Step 5 Click Application. ----End
3.1.3 Setting Loopback of the PDH Interface Board

The PDH interface board of the OptiX RTN 600 supports the inloop/outloop of the tributary.
Prerequisite
l l
Context
For the tributary inloop, a PDH signal is looped back at the coding/decoding unit of the board to the backplane. Figure 3-7 Tributary inloop
Backplane
PDH interface board PDH
Issue 06 (2007-12-30)
3-5
For the tributary outloop, a PDH signal is looped back at the coding/decoding unit of the board to the remote equipment. Figure 3-8 Tributary outloop
Backplane PDH interface board PDH
Precaution
CAUTION
Procedure
Step 1 Select PDH interface board in the object tree. Step 2 In the function tree, choose Configuration > Interface. Step 3 Select By Function, and in the drop-down list select Tributary Loopback. Step 4 Set the loopback status of the path as needed. Step 5 Click Application. ----End
3.1.4 Setting Loopback for the IF Board

The IF board of the OptiX RTN 600 supports the inloop/outloop of the IF ports, and the inloop of the VC-4 path.
Prerequisite
l l
Context
For the inloop of the IF port, an IF signal is looped back at the modem unit of the board to the backplane.
Figure 3-9 IF port inloop
Backplane IF signal
IF board
For the outloop of the IF port, an IF signal is looped back at the modem unit of the board to the remote equipment. Figure 3-10 IF port outloop
Backplane
IF board IF signal
For the inloop of the VC-4 path, a VC-4 signal is looped back at the logic processing unit of the board to the backplane. Figure 3-11 VC-4 path inloop
Backplane
IF board
VC-4 signal
Precaution
CAUTION
Issue 06 (2007-12-30)
3-7
Procedure
Step 1 Select IF board in the object tree. Step 2 Select the corresponding menu in the function tree. To Perform ... IF port loopback VC-4 path loopback Choose ... Configuration > IF Interface Configuration > Digital Interface
Step 3 Select By Function, and then select the loopback mode in the drop-down list. To Perform ... IF port loopback VC-4 path loopback Choose ... IF Port Loopback VC4 Loopback
Step 4 Set the loopback status of the port as needed. Step 5 Click Application. ----End
3.1.5 Setting Loopback for Ethernet Service Processing Boards

Ethernet service processing boards of the OptiX RTN 600 support inloop of Ethernet ports (MAC layer and PHY layer), and inlooop/outloop of VC-3 paths.
Prerequisite
l l
The communication between the Web LCT and the NE must be normal. The NE user must have authority of "maintenance level" or higher.
Context
The MAC inloop of an Ethernet port indicates that the service processing module loops back Ethernet physical signals towards the backplane direction at the PHY layer. The PHY inloop of an Ethernet port indicates that the service processing module loops back Ethernet framed signals towards the backplane direction at the MAC layer. Figure 3-12 Inloop of an Ethernet port
Backplane Ethernet service processing board
MAC
PHY
3-8
Issue 06 (2007-12-30)
The inloop of a VC-3 path indicates that the board logic processing unit loops back the service in a certain VC-3 path towards the backplane direction. Figure 3-13 Inloop of a VC-3 path
Backplane VC-3 signal Ethernet service processing board
The outloop of a VC-3 path indicates that the board logic processing unit loops back the service in a certain VC-3 path towards the opposite equipment. Figure 3-14 Outloop of a VC-3 path
Backplane Ethernet service processing board VC-3 signal
Precaution
CAUTION
Procedure
Step 1 Select the EFT4 board from Object Tree. Step 2 Select the corresponding menu in Function Tree. To Perform... Ethernet port loopback (MAC layer or PHY layer) VC-3 path loopback Step 3 Select the port or the path type. Choose... Configuration > Ethernet Interface Management > Ethernet Interface Configuration > SDH Interface
Issue 06 (2007-12-30)
3-9
To Perform... Ethernet port loopback (MAC layer or PHY layer) VC-3 path loopback Step 4 Set the loopback status of the port or path as required. Step 5 Click Application. ----End
Choose... External port VC-3 path
3.2 Part Replacement

Part replacement is a method frequently used to locate faults. The replacement operation varies with the part types. Table 3-1 Part replacement description Part Name SD1, SL1 SLE, SDE PO1, PH1 EFT4 IF1A, IF1B PXC SCC FAN ODU Operation Replace the SDH optical interface board Replace the SDH electrical interface board Replace the PDH interface board Replacing the Ethernet Service Processing Board Replace the IF board Replace the PXC board Replace the SCC board Replace the FAN board Replace the ODU Reference 3.2.3 Replacing the SDH Optical Interface Board 3.2.4 Replacing the SDH Electrical Interface Board 3.2.5 Replacing the PDH Interface Board 3.2.6 Replacing the Ethernet Service Processing Board 3.2.7 Replacing the IF Board 3.2.8 Replacing the PXC board 3.2.9 Replacing the SCC Board 3.2.10 Replacing the Fan Board 3.2.11 Replacing the ODU
3.2.1 Removing a Board

Procedure
Step 1 Insert one end of the ESD wrist strap into the ESD connector on the cabinet. Wear the ESD wrist strap. Step 2 If the board is connected with cables, remove the cables after marking them. Step 3 Loosen screws on the panel of the board.
Figure 3-15 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. Figure 3-16 Removing a board (2)
Step 5 Pull out the board gently along the guide rail in the slot. At this time, the board is in a parallel manner. Figure 3-17 Removing a board (3)
Issue 06 (2007-12-30)
3-11
CAUTION
Slowly remove the board, to avoid that the components on the boards are collided. Step 6 Put the board removed into the antistatic box or bag. ----End
3.2.2 Inserting a Board

Procedure
Step 1 Insert one end of the ESD wrist strap into the ESD connector on the cabinet. Wear the ESD wrist strap. Step 2 Hold the ejector levers with hands on the panel. Push them outwards and make the angle between the ejector lever and the panel be 45 degrees or so. Step 3 Push the board gently along the slot guide rail until the board cannot slide further. Figure 3-18 Inserting a board (1)
CAUTION
Slowly insert the board, to avoid that the components on the boards are collided. Step 4 Press the two ejector levers inward with force.
3-12
Issue 06 (2007-12-30)
Figure 3-19 Inserting a board (2)
Step 5 Tighten screws on the panel. Figure 3-20 Inserting a board (3)
Step 6 If the board is connected to cables originally, connect the cables based on the label marked on them. ----End
3.2.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 l l l
Know the impact of board replacement. Know the specific position of the board to be replaced. Know the service protection and protection channels of the board to be replaced. Make sure that the spare SDH optical interface board is at hand and that the version and Small Form-Factor Pluggable (SFP) optical module type of the spare board are consistent with those of the board to be replaced.
Issue 06 (2007-12-30)
3-13

NOTE
The SL1/SD1 board is available in four types:

l l l l
The board of type 01 is equipped with the Ie-1 SFP optical module. The board of type 02 is equipped with the S-1.1 SFP optical module. The board of type 03 is equipped with the L-1.1 SFP optical module. The board of type 04 is equipped with the L-1.2 SFP optical module.
You can identify the type of a board through the bar code on the ejector lever.
Tools and Test Equipment

Web LCT or T2000
Procedure
Step 1 Query the current alarm of the board using the Web LCT or T2000, and record the result. Step 2 When the service of the board to be replaced is the working service configured with the SNCP, use the Web LCT or T2000 to perform the forced switching of the service. Step 3 Refer to 3.2.1 Removing a Board, remove the board. . Step 4 Make sure the version and SFP type of the spare board are consistent with those of the board to be replaced. Step 5 Refer to 3.2.2 Inserting a Board, insert the spare board. Step 6 When the board is working, observe the indicators. The STAT indicator should light on as green. Step 7 If the SNCP forced switching was performed for the service, use the Web LCT or T2000 to cancel it. Step 8 Query the current alarm of the board using the Web LCT or T2000. There should be no newly added alarms. ----End
3.2.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 l l l
Know the impact of board replacement. Know the specific position of the board to be replaced. Know the service protection and protection channels of the board to be replaced. The spare SDH electrical interface board is at hand, and is of the same version withe the board to be replaced.

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

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

Web LCT or T2000
Procedure
Step 1 Query the current alarm of the board using the Web LCT or T2000, and record the result. Step 2 Refer to 3.2.1 Removing a Board, remove the board. . Step 3 Make sure the version and type of the spare board are consistent with those of the board to be replaced. Step 4 Refer to 3.2.2 Inserting a Board, insert the spare board. Step 5 When the board is working, observe the indicators.
The STAT indicator should light on as green. Step 6 Query the current alarm of the board using the Web LCT or T2000. There should be no newly added alarms. ----End
3.2.6 Replacing the Ethernet Service Processing Board

When the Ethernet service processing board is replaced, the services on this board are interrupted.
Prerequisite
l l l l
Know the impact of board replacement. Know the specific position of the board to be replaced. Know the service protection and protection channels of the board to be replaced. The backup part for the Ethernet service processing board must be available on site. The version and type of the backup part must be the same as those of the board to be replaced.

Web LCT or T2000
Procedure
Step 1 Query the current alarm of the board using the Web LCT or T2000, and record the result. Step 2 Refer to 3.2.1 Removing a Board, remove the board. . Step 3 Check whether the version and type of the backup part are the same as those of the board to be replaced. Step 4 Refer to 3.2.2 Inserting a Board, insert the spare board. Step 5 When the board is working, observe the indicators. The STAT indicator should light on as green. Step 6 Query the current alarm of the board using the Web LCT or T2000. There should be no newly added alarms. ----End
3.2.7 Replacing the IF Board

When the IF board is not configured with the 1+1 protection and the services of the board are not configured with any protection, these services are interrupted during this process.
Prerequisite
l l l
Know the impact of board replacement. Know the specific position of the board to be replaced. Make clear the configuration of the board 1+1 protection.
3-16

l l
Know the service protection and protection channels of the board to be replaced. Make sure that the spare IF board is at hand and that the version and type of it are consistent with those of the board to be replaced.

Web LCT or T2000
Procedure
Step 1 Query the current alarm of the board using the Web LCT or T2000, and record the result. Step 2 When the board to be replaced is the working board configured with the 1+1 protection, use the Web LCT or T2000 to perform the forced switching of the board. After the successful switching, perform the step 4. Step 3 When the service of the board to be replaced is the working service configured with the SNCP, use the Web LCT or T2000 to perform the forced switching of the service. Step 4 Turn off the ODU-PWR switch of the IF board to be replaced. Step 5 Refer to 3.2.1 Removing a Board, remove the board. . Step 6 Make sure the version and type of the spare IF board are consistent with those of the board to be replaced. Step 7 Make sure that the ODU-PWR switch on the spare IF board is in the off position. Step 8 Refer to 3.2.2 Inserting a Board, insert the spare board. Step 9 When the board is working, observe the indicators. The STAT indicator should light on as green. Step 10 Turn on the ODU-PWR switch of the IF board. Step 11 If the SNCP forced switching was performed for the service, use the Web LCT or T2000 to cancel it. Step 12 If the 1+1 protection forced switching of the board was performed, use the Web LCT or T2000 to cancel it. Step 13 Query the current alarm of the board using the Web LCT or T2000. There should be no newly added alarms. ----End
3.2.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 l l
Know the impact of board replacement. Know the specific position of the board to be replaced. Make clear the configuration of the board 1+1 protection.
Issue 06 (2007-12-30)

l
Make sure that the spare PXC board is at hand and that the version is consistent with that of the board to be replaced.

Web LCT or T2000
Precaution
When the PXC is configured with 1+1 protection and only one-channel power is accessed, it is recommended to provide one-channel -48 V/-60 V power for the standby PXC board temporarily. After the board is replaced, stop providing power for the standby board. This can ensure that the equipment does not power off during the PXC replacement.
Procedure
Step 1 Query the current alarm of the board using the Web LCT or T2000, and record the result. Step 2 When the board to be replaced is the active board configured with the 1+1 protection, perform the active and standby switching using the Web LCT or T2000. 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 5 Refer to 3.2.1 Removing a Board, remove the board. . Step 6 Make sure that the version and type of the spare board are consistent with those of the board to be replaced. Step 7 Refer to 3.2.2 Inserting a Board, insert the spare board. 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. Step 10 When the board is working, observe the indicators. The STAT indicator should light on as green. Step 11 If the switching is performed before the replacement, perform a switchover operation on the Web LCT or T2000 to make the working board be the active board, not the standby board. Step 12 Query the current alarm of the board using the Web LCT or T2000. There should be no newly added alarms. ----End
3.2.9 Replacing the SCC Board

During this process, any NM operation and switching cannot be performed.
Prerequisite
l l
Know the impact of board replacement. Know the specific position of the board to be replaced.
3-18

l
Make sure that the spare SCC is at hand and that the version of it is consistent with that of the board to be replaced.

l l
Screwdriver Web LCT or T2000
Procedure
Step 1 Query the current alarm of the board using the Web LCT or T2000, and record the result. Step 2 Press the RST button on the SCC front panel. During the reset of the SCC board, the PROG indicator is on, off, flashing, and off sequentially. Step 3 When the PROG indicator is operating, Refer to section 3.2.1 Removing a Board, remove the board. Step 4 Make sure the version and the jumper settings of the spare board are consistent with those of the board to be replaced. Step 5 Remove the board to be replaced and portable memory card of the spare board. 1. 2. Wear the ESD wrist strap. Remove the screws on the portable memory card and pull the connector of the memory card out from the socket of the dual edge connector on the SCC board. Figure 3-21 Remove the portable memory card
Step 6 Install the portable memory card of the board to be replaced onto the spare board. Step 7 Refer to 3.2.2 Inserting a Board, insert the spare board. Step 8 When the board is working, observe the indicators. The STAT and PROG indicators should light on as green. Step 9 Query the current alarm of the board using the Web LCT or T2000.
There should be no newly added alarms. ----End
3.2.10 Replacing the Fan Board

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

Web LCT or T2000
Procedure
Step 1 Query the current alarm of the board using the Web LCT or T2000, and record the result. Step 2 Loosen the captive screws on the panel of the fan tray assembly. Step 3 Move cables away from the front panel of the fan tray assembly. Step 4 Pull out the fan tray assembly. Figure 3-22 Pulling out the fan tray assembly
NOTE
If the IDU is installed in a dust-proof environment, there is no air filter.
Step 5 Remove the fan board gently and horizontally along the guide rail.
3-20
Issue 06 (2007-12-30)
Figure 3-23 Removing the fan board
WARNING
Before the fan stops, do not touch the blades. Step 6 Make sure the version of the spare board is consistent with that of the board to be replaced. Step 7 Insert the spare board steadily along the guide rail. Step 8 Install the panel of the fan tray assembly to the original position. Step 9 Tighten the captive screws on the panel. Step 10 Observe the indicator on the panel. The FAN indicator should light on as green. Step 11 Query the current alarm of the board using the Web LCT or T2000. There should be no newly added alarms. ----End
3.2.11 Replacing the ODU

When the ODU is not configured with 1+1 protection, the service transmitted by the ODU is interrupted during the process.
Prerequisite
l l l
Know the impact of ODU replacement. Know the specific position of the ODU to be replaced and the IF board connected to it. Make sure that the spare ODU is at hand and that the type of it is consistent with that of the ODU to be replaced.

l l l
Web LCT or T2000 Silicon Waterproof adhesive tape

Issue 06 (2007-12-30)
Precautions
Before you replace an ODU installed on the coupler, power off the ODU to be replaced, but do not power off or mute the other ODU. Otherwise, the services may be affected. The interface of the coupler ejects little RF radiation, and thus meets the safety standards for microwave radiation.
Procedure
Step 1 Query the current alarm of the ODU using the Web LCT or T2000, and record the result. Step 2 Turn off the ODU-PWR switch on the panel of the IF board. Step 3 Disconnect the IF cable and grounding cable of the ODU. Step 4 Loosen the four latches of the ODU and disconnect the ODU from the antenna or the hybrid coupler. Step 5 Make sure the type of the spare ODU is consistent with that of the ODU to be replaced. Step 6 Install the ODU. 1. 2. Remove the protective cap on the antenna interface of the ODU. Wearing gloves, dispense appropriate amount of lubricant on the sealing packing ring.
CAUTION
Do not dispense the lubricant on the front panel of the feeder. Otherwise, it may affect the signal transmission. 3. Align the antenna interface of the ODU with the feeder and then insert it to the feeder. Make sure that the four hooks are engaged with the latches of the ODU.
CAUTION
When inserting, make sure that the arrow direction stencilled on the ODU is consistent with the polarity direction of the antenna or the hybrid coupler. 4. Lock the four latches in a diagonal order.
Step 7 Connect the grounding cable and IF cable to the ODU. Step 8 Carry out the waterproof processing for the IF interface of the ODU. Step 9 Turn on the ODU-PWR switch on the panel of the IF board. Step 10 When the ODU is working, observe the indicators of the IF board: ODU and LINK. The indicators ODU and LINK should both light on as green. Step 11 Query the current alarm of the ODU using the Web LCT or T2000 There should be no newly added alarms. ----End
3.3 Cleaning Fiber Connectors and Adapters

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

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

Cartridge cleaner
Procedure
Step 1 Press down and hold the lever, and the shutter slides back and expose a new cleaning area. Figure 3-24 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 3-25 Dragging the fiber tip slightly on one cleaning area
Step 3 Do it again on the other cleaning area in the same direction as the step 2. Figure 3-26 Dragging the fiber tip slightly on the other cleaning area
Step 4 Release the lever to close the cleaning area. ----End

3.3.2 Cleaning Fiber Connectors Using Lens Tissue

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

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

NOTE
l l l
Using the isoamylol as the clean solvent is preferred, and the propyl can also be used. Do not use alcohol or formalin. The fiber cleaning tissue or lint-free wipes can replace the non-woven lens tissue. The special cleaning roll can replace the special compressed gas.
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 3-27 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 l
First spray it into the air as the initial spray of condensation can contain some sediment. Keep the injector nozzle as close as possible to the connector surface without touching it.
----End
3.3.3 Cleaning Fiber Adapters Using Optical Cleaning Sticks

Clean fiber adapters with optical cleaning sticks. This part describes the method of cleaning fiber adapters on the optical interface board. The method of cleaning fiber adapters on the optical attenuators and flanges is the same.
Prerequisite
l
Remove the optical fiber interface board. Make sure there is no laser light present on the fiber adapter. Inspect the fiber adapter with a fiber microscope to make sure that the fiber adapter is contaminated.

l l l
Optical cleaning sticks Clean solvent Special compressed gas

NOTE
l l l 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. The medical cotton or long fiber cotton can replace the optical cleaning stick. Using the isoamylol as the clean solvent is preferred, and the propyl can also be used. Do not use alcohol or formalin. The special cleaning roll can replace the special compressed gas.
Procedure
Step 1 Place a small amount of cleaning solvent on the optical cleaning stick. Step 2 Hold the stick straight out from the adapter and turn the stick clockwise four to five times. Ensure that there is direct contact between the stick tip and fiber tip so that the solvent can clean the adapter tip. Step 3 Using compressed gas, blow off the fiber tip. When using compressed gas:
l l
First spray it into the air as the initial spray of condensation can contain some sediment. Keep the injector nozzle as close as possible to the connector surface without touching it.
----End
A Alarm Reference
A
A.1 Alarm List
Table A-1 Alarm List Alarm Name A_LOC ALM_APS_MANU_ STOP ALM_GFP_dCSF ALM_GFP_dLFD ALM_RTC_FAIL APS_FAIL APS_INDI AU_AIS Description Add to bus - loss of clock
Alarm Reference
The following table lists all the possible alarms generated by the OptiX RTN 600 in alphabetical order.
Alarm Severity Major Major Critical Major Major Major Major Major
Source Board PO1PH1 SCC EFT4 EFT4 SCC SCC SCC SD1, SL1, SDE, SLE, IF1A, IF1B SD1, SL1, SDE, SLE, IF1A, IF1B SD1, SL1, SDE, SLE, IF1A, IF1B
MSP protocol is stopped manually GFP Loss of Client Signal GFP loss of frame delineation RTC time fail alarm APS protection switching failed APS state indication alarm AU alarm indication
AU_LOP
AU loss of pointer
Major
B1_EXC
Regenerator section (B1) excessive errors
Minor
Issue 06 (2007-12-30)
A-1
A Alarm Reference
Alarm Name B1_SD
Description Regenerator section (B1) signal degraded Multiplex section (B2) excessive errors Multiplex section (B2) signal degraded Higher order path (B3) excessive errors B3_EXC_VC3 Higher order path (B3) signal degraded B3_SD_VC3 Slot not installed with the corresponding logical board Board not in position
Alarm Severity Minor
Source Board SD1, SL1, SDE, SLE, IF1A, IF1B SD1, SL1, SDE, SLE, IF1A, IF1B SD1, SL1, SDE, SLE, IF1A, IF1B SD1, SL1, SDE, SLE, IF1A, IF1B EFT4 SD1, SL1, SDE, SLE, IF1A, IF1B EFT4 SCC SD1, SL1, SDE, SLE, IF1A, IF1B, PO1, PH1, EFT4, PXC, ODU, FAN, EOW PO1, PH1, EFT4 PO1, PH1, EFT4 ODU SCC SCC PO1, PH1 PO1, PH1
B2_EXC
Major
B2_SD
Minor
B3_EXC
Major
B3_EXC_VC3 B3_SD
Major Minor
B3_SD_VC3 BD_NOT_INSTALL ED BD_STATUS
Minor Minor Major
BIP_EXC BIP_SD CONFIG_NOSUPP ORT DBMS_ERROR DBMS_PROTECT_ MODE DN_E1_AIS E1_LOC
BIP excessive errors BIP signal degraded Configuration not supported Database error Database in protection mode 2M down signal alarm indication Loss of E1 clock
Minor Minor Major Major Critical Minor Major
A-2
Issue 06 (2007-12-30)
A Alarm Reference
Alarm Name E1_LOS ESN_FAILED ESN_INVALID ETH_LOS EXT_SYNC_LOS FAN_FAIL FCS_ERR HARD_BAD
Description 2M line loss of signal ESN failed ESN invalid Ethernet receive loss of input signal Loss of external synchronous source Fan failed FCS check error Hardware error
Alarm Severity Minor Major Major Critical Critical Major Critical Critical
Source Board PO1, PH1 SCC SCC EFT4 SCC FAN EFT4 SD1, SL1, SDE, SLE, IF1A, IF1B, PO1, PH1, EFT4, PXC, SCC, ODU SD1, SL1, SDE, SLE, IF1A, IF1B SD1, SL1, SDE, SLE, IF1A, IF1B SD1, SL1, SDE, SLE, IF1A, IF1B SD1, SL1, SDE, SLE, IF1A, IF1B SD1, SL1, SDE, SLE, IF1A, IF1B SD1, SL1, SDE, SLE, IF1A, IF1B SD1, SL1, SDE, SLE, IF1A, IF1B PO1, PH1
HP_CROSSTR
Higher order path performance over threshold Higher order path loss of multiframe
Minor
HP_LOM
Major
HP_RDI
Higher order path remote defect indication Higher order path remote error indication Higher order path signal label mismatch Higher order path trace identifier mismatch Higher order path unequipped
Minor
HP_REI
Warning
HP_SLM
Minor
HP_TIM
Minor
HP_UNEQ
Minor
HPAD_CROSSTR
Higher order path adaptation performance over threshold
Minor
Issue 06 (2007-12-30)
A-3
A Alarm Reference
Alarm Name HSB_INDI HSM_INDI IF_INPWR_ABN IN_PWR_HIGH IN_PWR_LOW J0_MM
Description Microwave equipment HSB switching indication Microwave channels HSM switching indication Abnormal input IF power of the ODU Input power too high Input power too low Trace identifier mismatch
Alarm Severity Major Major Major Critical Critical Minor
Source Board SCC SCC ODU SD1, SL1 SD1, SL1 SD1, SL1, SDE, SLE, IF1A, IF1B SCC SCC SD1, SL1 SD1, SL1
K1_K2_M K2_M LASER_CLOSED LASER_MOD_ERR _EX LCAS_FOPR LCAS_FOPT LCAS_PLCR LCAS_PLCT LCAS_TLCR LCAS_TLCT LPS_UNI_BI_M
K1K2 mismatch K2 mismatch Laser closed alarm Pluggable optical module on the board mismatches the optical interface Failure of protocol receive Failure of protocol transmit Partial loss of capacity receive Partial loss of capacity transmit Total loss of capacity receive Total loss of capacity receive Alarm of mismatch in unidirectional operation and bidirectional operation in linear MSP Path loopback
Minor Minor Major Major
Major Major Minor Minor Major Major Minor
EFT4 EFT4 EFT4 EFT4 EFT4 EFT4 SCC
LOOP_ALM
Minor
SD1, SL1, SDE, SLE, IF1A, IF1B, PO1, PH1, EFT4, ODU PO1, PH1 PO1, PH1
LP_CROSSTR LP_R_FIFO
Lower order path performance parameter over threshold FIFO overflow on the receiving side of the lower order path
Minor Minor
A-4
Issue 06 (2007-12-30)
A Alarm Reference
Alarm Name LP_RDI LP_RDI_VC12 LP_RDI_VC3 LP_REI LP_REI_VC12 LP_REI_VC3 LP_RFI LP_SIZE_ERR LP_SLM LP_SLM_VC12 LP_SLM_VC3 LP_T_FIFO LP_TIM LP_TIM_VC12 LP_TIM_VC3 LP_UNEQ LP_UNEQ_VC12 LP_UNEQ_VC3 LSR_NO_FITED LTI
Description Lower order path remote defect indication VC-12 lower order path remote defect indication VC-3 lower order path remote defect indication Lower order path remote error indication VC-12 lower order path remote receiving failure indication VC-3 lower order path remote receiving failure indication Lower order path remote failure indication TU structure error Lower order path signal label mismatch VC-12 lower order path signal flag mismatch VC-3 lower order path signal flag mismatch FIFO overflow on the transmission side of the lower order path Lower order path trace identifier mismatch VC-12 lower order path trace identifier mismatch VC-3 lower order path trace identifier mismatch Lower order path unequipped VC-12 lower order path signal unequipped VC-3 lower order path signal unequipped Laser not installed Loss of timing input
Alarm Severity Minor Minor Minor Minor Minor Minor Minor Minor Minor Minor Minor Minor Minor Minor Minor Minor Minor Minor Critical Major
Source Board PO1, PH1 EFT4 EFT4 PO1, PH1 EFT4 EFT4 PO1, PH1 PO1, PH1 PO1, PH1 EFT4 EFT4 PO1, PH1 PO1, PH1 EFT4 EFT4 PO1, PH1 EFT4 EFT4 SD1, SL1 SCC
Issue 06 (2007-12-30)
A-5
A Alarm Reference
Alarm Name MS_AIS
Description Multiplex section alarm indication
Alarm Severity Major
Source Board SD1, SL1, SDE, SLE, IF1A, IF1B SD1, SL1, SDE, SLE, IF1A, IF1B SD1, SL1, SDE, SLE, IF1A, IF1B SD1, SL1, SDE, SLE, IF1A, IF1B SD1, SL1, SDE, SLE, IF1A, IF1B SCC IF1A, IF1B IF1A, IF1B IF1A, IF1B IF1A, IF1B SCC SCC SD1, SL1, SDE, SLE, IF1A, IF1B, PXC IF1A, IF1B, PXC, SCC, FAN ODU PO1, PH1 PO1, PH1 SD1, SL1, SDE, SLE, IF1A, IF1B
MS_CROSSTR
Multiplex section performance over threshold Multiplex section remote defect indication Multiplex section remote error indication Multiplex section adaptation performance over threshold Master and slave software different alarm Microwave FEC uncorrectable Microwave link identifier mismatch Loss of RS frame Microwave link remote defect indication Loss of NE software NE in install state Software file corrupted or missing
Minor
MS_RDI
Minor
MS_REI
Warning
MSAD_CROSSTR
Minor
MSSW_DIFFEREN T MW_FECUNCOR MW_LIM MW_LOF MW_RDI NESF_LOST NESTATE_INSTAL L NO_BD_SOFT
Major Minor Major Critical Minor Critical Critical Critical
POWER_ALM
Power module alarm
Major
POWER_FAIL PS R_F_RST R_LOC
Board power failed Protection switch indication Receiving FIFO reset Receive loss of clock
Major Major Minor Major
A-6
Issue 06 (2007-12-30)
A Alarm Reference
Alarm Name R_LOF
Description Receive loss of frame
Alarm Severity Critical
Source Board SD1, SL1, SDE, SLE, IF1A, IF1B SD1, SL1, SDE, SLE, IF1A, IF1B PO1, PH1 ODU ODU ODU ODU ODU EOW PO1, PH1 SD1, SL1, SDE, SLE, IF1A, IF1B SCC PXC SCC PO1, PH1 PO1, PH1 PO1, PH1 SD1, SL1, SDE, SLE SD1, SL1, SDE, SLE IF1A, IF1B, EFT4, PXC, SCC PO1, PH1
A-7
R_LOS
Receive loss of signal
Critical
R_S_ERR RADIO_MUTE RADIO_RSL_HIGH RADIO_RSL_LOW RADIO_TSL_HIGH RADIO_TSL_LOW RELAY_ALARM RP_LOC RS_CROSSTR
Received signal error Radio transmission mute Radio receive signal level too high Radio receive signal level too low Radio transmission signal level too high Radio transmission signal level too low Relay alarm Loss of receiving phaselock ring clock Regenerator section performance over threshold Reference source change in S1_Mode Synchronous source degraded Synchronous source level loss E1 interface loss of analog signal Transmission FIFO reset Transmission FIFO overflow Transmit loss of clock Transmit loss of signal Temperature over threshold
Critical Warning Critical Critical Critical Critical Critical Major Minor
S1_SYN_CHANGE SYN_BAD SYNC_C_LOS T_ALOS T_F_RST T_FIFO_E T_LOC T_LOS TEMP_ALARM
Major Minor Warning Major Minor Minor Major Major Minor
TU_AIS
Issue 06 (2007-12-30)
TU alarm indication
Major
A Alarm Reference
Alarm Name TU_AIS_VC12 TU_AIS_VC3 TU_LOP TU_LOP_VC12 TU_LOP_VC3 UP_E1_AIS VCAT_LOA VCAT_LOM_VC12
Description VC-12 tributary unit alarm indication VC-3 tributary unit alarm indication TU loss of pointer VC-12 tributary unit loss of pointer VC-3 tributary unit loss of pointer 2M up signal alarm indication Virtual concatenation delay exceeds the threshold The multiframe indication of members in VC-12 virtual concatenation mismatches The multiframe indication of members in VC-3 virtual concatenation mismatches The serial number indication of members in VC-12 virtual concatenation mismatches The serial number indication of members in VC-3 virtual concatenation mismatches Loss of voltage Wrong board type Wrong device type Wayside interface loss of signal XCS protection switching indication
Alarm Severity Major Major Major Major Major Minor Critical Major
Source Board EFT4 EFT4 PO1, PH1 EFT4 EFT4 PO1, PH1 EFT4 EFT4
VCAT_LOM_VC3
Major
EFT4
VCAT_SQM_VC12
Major
EFT4
VCAT_SQM_VC3
Major
EFT4
VOLT_LOS WRG_BD_TYPE WRG_DEV_TYPE WS_LOS XCP_INDI
Major Major Critical Major Major
PXC, IF1A, IF1B SCC SCC PXC SCC
A.2 Alarms and Corrective procedures

This section describes all the possible alarms of the OptiX RTN 600 and how to clear these alarms.
A.2.1 A_LOC
A-8
Issue 06 (2007-12-30)
A Alarm Reference
Description
The A_LOC alarm indicates "add to bus - loss of clock".
Attribute
Alarm Severity Major Alarm Type 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 Parameter 1 Meaning The value is always 0x01.
Parameter 23 Indicates the number of the path that reports the alarm. For example, "0x00 0x01" indicates that the alarm is reported by the first path.
Impact on System
The board services are interrupted.
Possible Causes
The board is faulty.
Handling Procedure
Replace the faulty board. ----End
Related Information
None.
A.2.2 APS_MANU_STOP
Description
The APS_MANU_STOP alarm indicates that the MS protocol is manually disabled.
Issue 06 (2007-12-30) Huawei Technologies Proprietary A-9
A Alarm Reference
Attribute
Alarm Severity Minor Alarm Type Processing 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 Indicates the type of a protection group. For example, "0x01" indicates a linear MSP group. Parameter 2 Indicates the number of the protection group that reports the alarm. For example, "0x01" indicates that the alarm is reported by the first protection group.
Impact on System
When the APS_MANU_STOP occurs, the MSP or the switching might fail.
Possible Causes
The MS protocol is manually disabled.
Handling Procedure
Enable the MS protocol. ----End
Related Information
None.
A.2.3 ALM_GFP_dCSF
Description
The ALM_GFP_dCSF alarm indicates that the generic framing procedure (GFP) customer signal is lost. If a board detects the GFP customer signal management frame that is transmitted from the opposite station, this board reports the ALM_GFP_dCSF alarm.
A-10
Issue 06 (2007-12-30)
A Alarm Reference
Attribute
Alarm Severity Critical Alarm Type Communication alarm
Parameters
Parameters 23 Indicates the number of the VCTRUNK that reports the alarm. For example, "0x00 0x01" indicates that the alarm is reported by the first VCTRUNK.
Impact on System
The services are interrupted.
Possible Causes
The connection of the corresponding Ethernet port on the opposite board is faulty.
Handling Procedure
Handle the alarm on the opposite board. ----End
Related Information
None.
A.2.4 ALM_GFP_dLFD
Description
The ALM_GFP_dLFD is an alarm indicating that the GFP frame is out of frame. When a board detects that the GFP frame is out of frame, this board reports the ALM_GFP_dLFD alarm.
Attribute
Alarm Severity Major
Issue 06 (2007-12-30)
Alarm Type Communication alarm

Huawei Technologies Proprietary A-11
A Alarm Reference
Parameters
Impact on System
Possible Causes
l
The source and the sink VCTRUNKs are configured with different numbers of paths or timeslots. Errors exist on a link or the link is faulty.
Handling Procedure
Step 1 Check whether the VCTRUNKs at the transmit and the receive directions at the local station are configured with the same number of physical paths and timeslots. If ... Not Yes Then ... Correct the configuration. Go to the next step.
Step 2 Check whether a failure or bit errors occur in the line that services pass. If ... Yes Not Then ... Remove the fault. Go to the next step.
Step 3 Replace the board that reports the ALM_GFP_dLFD alarm. ----End
Related Information
None.
A.2.5 ALM_RTC_FAIL
A-12 Huawei Technologies Proprietary Issue 06 (2007-12-30)
A Alarm Reference
Description
The ALM_RTC_FAIL alarm indicates that the real time clock (RTC) of the equipment fails.
Attribute
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. None.
Impact on System
None.
Possible Causes
The RTC of the SCC board is faulty.
Handling Procedure
Step 1 Reset the SCC board. If ... The ALM_RTC_FAIL alarm is cleared after the SCC board resets No alarm exists Step 2 Replace the SCC board. ----End Then ... Reset the NE clock to end the ALM_RTC_FAIL alarm. Go to the next step.
Related Information
None.
A.2.6 APS_FAIL
Description
The APS_FAIL alarm indicates that the MSP switching fails.
A Alarm Reference
Attribute
Alarm Severity Major Alarm Type Communication alarm
Parameters
Parameter 1 Indicates the type of a protection group. For example, "0x01" indicates a linear MSP group. Parameter 2 Indicates the number of the protection group that reports the APS_FAIL alarm. For example, "0x01" indicates that the alarm is reported by the first protection group.
Impact on System
The services cannot be switched. If the current paths cannot be used, the services are interrupted.
Possible Causes
l l
Parameters of the MSP are incorrectly configured. Parameters of the MSP are lost.
Handling Procedure
Step 1 Check whether the MSP parameters of the node on which the APS_FAIL occurs are correctly configured. If ... Not Yes Then ... Correct the configuration. Go to the next step.
Step 2 Check whether the networkwide MS protocol is normal. If not, manually disable and restart the protocol. If ... Then ...
The APS_FAIL alarm is cleared after the protocol is restarted End the alarm handling. The APS_FAIL alarm persists after the protocol is restarted Contact Huawei engineers. ----End
A Alarm Reference
Related Information
None.
A.2.7 APS_INDI
Description
The APS_INDI is an indication alarm of the MSP switching.
Attribute
Parameters
Parameter 1 Indicates the type of a protection group. For example, "0x01" indicates a linear MSP group. Parameter 2 Indicates the number of the protection group that reports the APS_INDI alarm. For example, "0x01" indicates that the alarm is reported by the first protection group.
Impact on System
During the MSP switching (within 50 ms), the services are interrupted. After the MSP switching completes, the services are restored to normal.
Possible Causes
An MSP switching occurs to the services.
Handling Procedure
Detect the switching causes and take measures accordingly.
NOTE
After a non-revertive 1+1 linear MSP switching occurs, the APS_INDI alarm is generated. When the optical channels are restored to normal, the services are not automatically switched to the working path and the APS_INDI alarm persists. In this case, manually switch the services from the protection path to the working path. After the switching succeeds, the APS_INDI alarm is cleared.
----End
A Alarm Reference
Related Information
None.
A.2.8 AU_AIS
Description
The AU_AIS alarm indicates "AU alarm indication". When the AU pointers of three consecutive frames are detected to be all "1"s, this alarm is reported.
Attribute
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 Parameter 1 Meaning Indicates the number of the line port that reports the alarm. For example, "0x01" indicates the alarm is reported by the first port of the board.
Parameter 23 Indicates the number of the AU-4 path that reports the alarm. For example, "0x00 0x01" indicates the alarm is reported by the first AU-4 path in the SDH signal.
Impact on System
Services on AU-4 paths are interrupted. If the services are configured with protection, the protection switching can be triggered.
Possible Causes
l l l
The AU_AIS alarm is inserted at the opposite station. The transmit unit of the opposite station is faulty. The receive unit of the local station is faulty.
Handling Procedure
Step 1 Locate the AU-4 channel that reports the alarm according to alarm parameters. Step 2 Query if the opposite station has the alarms that can trigger the AU_AIS alarm.
A Alarm Reference
If ...
Then ...
The opposite station has the alarms that can Handle the alarms at the opposite station first. trigger the AU_AIS alarm The opposite station has no alarms that can Go to the next step. trigger the AU_AIS alarm Step 3 Replace the line board of the opposite station. If ... Then ...
The alarm disappears after the line board The fault is cleared and the troubleshooting is is replaced complete. The alarm persists after the line board is Go to the next step. replaced Step 4 Replace the cross-connect and timing board of the opposite station. If ... The alarm disappears after the crossconnect and timing board is replaced Then ... The fault is cleared and the troubleshooting is complete.
The alarm persists after the cross-connect Go to the next step. and timing board is replaced Step 5 Replace the board that reports the alarm. ----End
Related Information
None.
A.2.9 AU_LOP
Description
The AU_LOP alarm indicates "AU loss of pointer". When the board detects the AU-PTR value of eight consecutive frames is invalid or is NDF revertive, this alarm is reported.
Attribute
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,
A Alarm Reference
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the number of the line port that reports the alarm. For example, "0x01" indicates the alarm is reported by the first port of the board.
Impact on System
Services on AU-4 paths are interrupted. If the services are configured with protection, the protection switching can be triggered.
Possible Causes
l l
The transmit unit of the opposite station is faulty. The receive unit of the local station is faulty.
Handling Procedure
Step 1 Locate the AU-4 channel that reports the alarm according to alarm parameters. Step 2 Replace the line board of the opposite station. If ... Then ...
The alarm disappears after the line board The fault is cleared and the troubleshooting is is replaced complete. The alarm persists after the line board is Go to the next step. replaced Step 3 Replace the cross-connect and timing board of the opposite station. If ... The alarm disappears after the crossconnect and timing board is replaced Then ... The fault is cleared and the troubleshooting is complete.
The alarm persists after the cross-connect Go to the next step. and timing board is replaced Step 4 Replace the board that reports the alarm. ----End
Related Information
None.
A.2.10 B1_EXC
A Alarm Reference
Description
The B1_EXC alarm indicates "regenerator section (B1) excessive errors". When the board detects the B1 bit errors exceed the preset B1_EXC alarm threshold (10-3 by default), this alarm is reported. The IF boards that work in the PDH mode may also report this alarm. This alarm is detected by the self-defined overhead bytes B1 in PDH microwave frames.
Attribute
Alarm Severity Minor Alarm Type Service alarm
Parameters
Parameter 23 Indicates the path number.
Impact on System
The services on the port are interrupted.
Possible Causes
l l l
The line performance degrades. The transmit unit of the opposite station is faulty. The receive unit of the local station is faulty.
Handling Procedure
Refer to section 2.4 Troubleshooting Bit Errors. ----End
Related Information
None.
A.2.11 B1_SD
A Alarm Reference
Description
The B1_SD alarm indicates "regenerator section (B1) signal degraded". When the board detects the B1 bit errors exceed the preset B1_SD alarm threshold (10-6 by default), this alarm is reported. The IF boards that work in the PDH mode may also report this alarm. This alarm is detected by the self-defined overhead bytes B1 in PDH microwave frames.
Attribute
Parameters
Impact on System
The service performance on the port degrades.
Possible Causes
l l l
Handling Procedure
Related Information
None.
A.2.12 B2_EXC
A Alarm Reference
Description
The B2_EXC alarm indicates "multiplex section (B2) excessive errors". When the board detects the B2 bit errors exceed the preset B2_EXC alarm threshold (10-3 by default), this alarm is reported.
Attribute
Alarm Severity Major Alarm Type Service alarm
Parameters
Impact on System
The services on the port are interrupted. If the services are configured with protection, the protection switching can be triggered.
Possible Causes
l l l
Handling Procedure
Related Information
None.
A.2.13 B2_SD
A Alarm Reference
Description
The B2_SD alarm indicates "regenerator section (B2) signal degraded". When the board detects the B2 bit errors exceed the preset B2_SD alarm threshold (10-6 by default), this alarm is reported.
Attribute
Parameters
Impact on System
The services on the interface degrade.
Possible Causes
l l l
Handling Procedure
Related Information
None.
A.2.14 B3_EXC
A-22
Issue 06 (2007-12-30)
A Alarm Reference
Description
The B3_EXC alarm indicates "higher order path (B3) excessive errors". When the board detects the B3 bit errors exceed the preset B3_EXC alarm threshold (10-3 by default), this alarm is reported.
Attribute
Parameters
Parameter 23 Indicates the number of the AU-4 path that reports the alarm. For example, "0x00 0x01" indicates the alarm is reported by the first AU-4 path.
Impact on System
The services on the path are interrupted.
Possible Causes
l l l
Handling Procedure
Related Information
None.
A.2.15 B3_EXC_VC3
A Alarm Reference
Description
The B3_EXC_VC3 alarm indicates that excessive B3 bit errors exist in the VC-3 path. When a board detects that the B3 bit errors cross the preset threshold of the B3_EXC_VC3 (10-3 by default), this board reports the alarm.
Attribute
Alarm Severity Major Alarm Type QoS alarm
Parameters
Parameters 23 Indicates the number of the path that reports the alarm. For example, "0x00 0x01" indicates that the alarm is reported by the first VC-3 path.
Impact on System
A large number of bit errors exist in the services in the VC-3 path.
Possible Causes
l l l
The line performance degrades. The transmit part at the opposite station is faulty. The receive part of the local station is faulty.
Handling Procedure
Related Information
None.
A.2.16 B3_SD
A Alarm Reference
Description
The B3_SD alarm indicates "higher order path (B3) signal degraded". When the board detects the B3 bit errors exceed the preset B3_SD alarm threshold (10-6 by default), this alarm is reported.
Attribute
Parameters
Parameter 23 Indicates the number of the AU-4 path that reports the alarm. For example, "0x00 0x01" indicates the alarm is reported by the first AU-4 path.
Impact on System
Services on the channel degrade. If the services are configured with protection, the protection switching can be triggered.
Possible Causes
l l l
Handling Procedure
Related Information
None.
A.2.17 B3_SD_VC3
A Alarm Reference
Description
The B3_SD_VC3 alarm indicates that B3 bit errors in the VC-3 path deteriorate. When a board detects that the B3 bit errors cross the preset threshold of the B3_SD_VC3 (10-6 by default), this board reports the alarm.
Attribute
Parameters
Parameters 23 Indicates the number of the path that reports the alarm. For example, "0x00 0x01" indicates that the alarm is reported by the first VC-3 path.
Impact on System
The services in this VC-3 path degrade.
Possible Causes
l l l
The line performance degrades. The transmit part at the opposite station is faulty. The receive part of the local station is faulty.
Handling Procedure
Related Information
None.
A.2.18 BD_NOT_INSTALLED
A Alarm Reference
Description
The BD_NOT_INSTALLED alarm indicates that a slot is not installed with the corresponding logical board.
Attribute
Alarm Severity Minor Alarm Type 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 Parameter 1 Meaning Indicates the slot number.
Impact on System
The physical board in this slot cannot work.
Possible Causes
l l
The corresponding slot is not configured with the logical board. The corresponding physical board is inserted in a wrong slot when this board is used to replace the original board.
Handling Procedure
Step 1 Check whether the corresponding physical board is inserted in a wrong slot. If ... Yes Not Then ... Insert the corresponding physical board in the correct slot. Go to the next step.
Step 2 Configure the logical board in the slot layout figure on the NMS. ----End
Related Information
None.
A.2.19 BD_STATUS
A Alarm Reference
Description
The BD_STATUS alarm indicates "board not in position".
Attribute
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. None.
Impact on System
The board that reports the alarm cannot operate.
Possible Causes
If the board that reports the alarm is in the IDU, the possible causes are as follows:
l l l l
The board is faulty. The board is installed in an incorrect slot. The board and the backplane are poorly connected. The slot is faulty.
If the board that reports the alarm is in the ODU, the possible causes are as follows:
l l l l
The ODU is faulty. The power supply of the ODU is switched off. The IF cables are poorly connected. The IF boards are faulty.
Handling Procedure
Step 1 Perform alarm clearing according to the type of the board that reports the alarm. If ... The board that reports the alarm is in the ODU The board that reports the alarm is in the IDU Step 2 Check if the power supply of the ODU is switched on.
Then ... Perform Step 2 to Step 6. Perform Step 7 to Step 11.
A Alarm Reference
If ... The switch is turned on The switch is turned off Step 3 Check if the IF cables are correctly connected. If ... The cables are correctly connected The cables are incorrectly connected Step 4 Replace the ODU. If ... The alarm disappears after the board is replaced The alarm persists after the board is replaced Step 5 Replace the IF cables. If ...
Then ... Go to the next step. Turn on the switch.
Then ... Go to the next step. Reconnect the cables correctly.
Then ... The fault is cleared and the troubleshooting is complete. Go to the next step.
Then ...
The alarm disappears after the cables are The fault is cleared and the troubleshooting is replaced complete. The alarm persists after the cables are replaced Step 6 Replace the IF board. Step 7 Check if the board that reports the alarm is installed in the correct slot. If ... If the board that reports the alarm is installed in an incorrect slot Then ... Re-install the board in the correct slot. Go to the next step.
The board that reports the alarm is installed in the Go to the next step. correct slot Step 8 Remove and insert the board again. If ... The alarm disappears after the board is removed and inserted The alarm persists after the board is removed and inserted Step 9 Replace the board that reports the alarm. Then ... The fault is cleared and the troubleshooting is complete. Go to the next step.
Issue 06 (2007-12-30)
A-29
A Alarm Reference
If ... The alarm disappears after the board is replaced The alarm persists after the board is replaced
Step 10 Install the board that reports the alarm into another slot. If the board reports no alarm in the new slot, it indicates that the previous slot is faulty. Step 11 Keep the board working in the new slot, and contact technical support engineers of Huawei. ----End
Related Information
None.
A.2.20 BIP_EXC
Description
The BIP_EXC alarm indicates "BIP excessive errors". When the BIP2 bit errors in the V5 byte are detected over the preset BIP_EXC alarm threshold (10-3 by default), this alarm is reported.
Attribute
Parameters
Impact on System
The services on the path are interrupted.
A Alarm Reference
Possible Causes
l l l
Handling Procedure
Related Information
None.
A.2.21 BIP_SD
Description
The BIP_SD alarm indicates "BIP signal degraded". When the BIP2 bit errors in the V5 byte are detected over the preset BIP_SD alarm threshold (10-6 by default), this alarm is reported.
Attribute
Parameters
Impact on System
The services on the path degrade.
Possible Causes
l
The line performance degrades.

Issue 06 (2007-12-30)
A Alarm Reference
l l
Handling Procedure
Related Information
None.
A.2.22 CONFIG_NOSUPPORT
Description
The CONFIG_NOSUPPORT alarm indicates "configuration not supported". When the ODU detects the configured parameters mismatch these of the ODU, this alarm is reported.
Attribute
Alarm Severity Major Alarm Type Processing 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 Parameter 1 Meaning Indicates the unmatched parameter.
l l l l l l
"0x01" indicates the frequency configuration error. "0x02" indicates the TR spacing configuration error. "0x03" indicates the transmit power configuration error. "0x04" indicates the ATPC threshold configuration error. "0x05" indicates the bandwidth configuration error. "0x06" indicates the modulation mode configuration error.
Impact on System
The ODU cannot work normally. If the equipment is configured with 1+1 FD protection, the main ODU generates the CONFIG_NOSUPPORT alarm. In this case, an IF 1+1 protection switching occurs.
A Alarm Reference
Possible Causes
The type of the ODU mismatches the configured parameters.
Handling Procedure
Step 1 Determine the unmatched parameter according to the alarm parameters. Step 2 Check if the parameters comply with the requirement of the network planning. If ... The parameters comply with the requirements of the network planning The parameters do not comply with the requirements of the network planning ----End Then ... Replace the ODU of the correct type. Modify the parameters.
Related Information
None.
A.2.23 DBMS_ERROR
Description
The DBMS_ERROR alarm indicates that errors occur in the processing of the system database.
Attribute
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.
Issue 06 (2007-12-30)
A-33
A Alarm Reference
Name
Meaning
l l l l l
Parameter 1 Indicates the type of the database error. 0x01: Indicates that the entered parameter is illegal. 0x02: Indicates that no database file exists. 0x03: Indicates that the database storage area numbers are incorrect. 0x04: Indicates that a database overwriting occurs. 0x05: Indicates that errors occur in the header information check in the database backup area. 0x06: Indicates that errors occur in the FAT table structure check in the database storage area. 0x07: Indicates that errors occur in the database check in the database backup area. 0x08: Indicates that restoring the database fails. 0x09: Indicates an invalid database ID. 0x0A: Indicates that the databases are different. 0x0B: Indicates that the data is unchecked. 0x0E: Indicates that the semaphore handle is invalid. 0x0F: Indicates that errors occur in memory applying. 0x10: Indicates that errors occur in memory releasing. 0x12: Indicates that transmitting the message packets fails. 0x13: Indicates that the start record is queried to be incorrect. 0x14: The database is null. 0x15: Indicates that the mark is incorrectly set. 0x16: Indicates that the entered command parameters are incorrect. 0x17: Indicates that this is not a backup database. 0x18: Indicates that the database is in the protected mode. 0x19: Indicates that the configuration is not verified.
l l l l l l l l l l l l l l l
Parameter 2 Indicates the database memory area in which errors occur.

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

l l
0x00: Indicates the IDs of all the databases in the storage area. 0x010xff: Indicates the ID of a specific database.
Impact on System
When the DBMS_ERR alarm occurs, it indicates that errors occur in the system database processing. The system configuration may be lost. As a result, the failure indication is returned for some query and setting commands, and some system functions cannot work.
A Alarm Reference
Possible Causes
l l l
The database operation fails. The data in the database is damaged. The SCC board is faulty.
Handling Procedure
Step 1 Reset the SCC board. If ... Then ...
The DBMS_ERROR alarm is cleared after the SCC board resets End the alarm handling. The DBMS_ERROR alarm persists after the SCC board resets Go to the next step. Step 2 Replace the board that reports the DBMS_ERROR alarm. ----End
Related Information
None.
A.2.24 DBMS_PROTECT_MODE
Description
The DBMS_PROTECT_MODE alarm indicates that the system database is in the protected mode.
Attribute
Alarm Severity Critical Alarm Type Processing alarm
Parameters
None.
Impact on System
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 some query and setting commands, and some system functions cannot work.
Possible Causes
The NE software resets frequently.
A Alarm Reference
Handling Procedure
Replace the board that reports the DBMS_PROTECT_MODE alarm. ----End
Related Information
None.
A.2.25 DN_E1_AIS
Description
The DN_E1_AIS alarm "2M down signal alarm indication". When the tributary board detects the downlink E1 signal is all "1"s, this alarm is reported.
Attribute
Parameters
Impact on System
The E1 signals are unavailable.
Possible Causes
l l l
The tributary board of the opposite station has transmitted the E1_AIS signal. The receive unit of the tributary board of the local station is faulty. The cross-connect board of the local station is faulty.
Handling Procedure
Step 1 Check if the opposite equipment has the UP_E1_AIS or T_ALOS alarm.
A Alarm Reference
If ... There is the UP_E1_AIS alarm There is no UP_E1_AIS alarm Step 2 Replace the board that reports the alarm. If ... The alarm disappears after the board is replaced The alarm persists after the board is replaced Then ...
Then ... Clear the alarm. Go to the next step.
The fault is cleared and the troubleshooting is complete. Go to the next step.
Step 3 Replace the cross-connect and timing board of the local station. ----End
Related Information
None.
A.2.26 E1_LOC
Description
The E1_LOC alarm indicates "loss of E1 clock". When the tributary board cannot extract the clock from the E1 signal, this alarm is reported.
Attribute
Parameters
Parameter 1 Indicates the number of the tributary interface/path that reports the alarm. For example, "0x01" indicates the alarm is reported by the first interface/path of the board.
Impact on System
This alarm has no impact on the services.
A Alarm Reference
Possible Causes
l l
The input E1 signal waveform is abnormal. The receive unit of the tributary board of the local station is faulty.
Handling Procedure
Step 1 Check if the opposite equipment is faulty. If ... The opposite equipment is faulty The opposite equipment is not faulty Then ... Clear the fault. Go to the next step.
Step 2 Check if there is external interference that causes abnormal E1 signal waveform. If ... There is external interference Then ... The fault is cleared and the troubleshooting is complete.
There is no external interference Contact technical support engineers of Huawei. Step 3 Replace the board that reports the alarm. ----End
Related Information
None.
A.2.27 E1_LOS
Description
The E1_LOS alarm indicates "2M line loss of signal". When the tributary board detects the uplink E1 signal is all "0"s, this alarm is reported.
Attribute
Alarm Severity Minor Alarm Type Communication alarm
Parameters
A Alarm Reference
Name Parameter 1
Meaning The value is always 0x01.
Impact on System
E1 services are interrupted.
Possible Causes
l l
The input E1 signal is abnormal. The tributary board of the local station is faulty.
Handling Procedure
Step 1 Check if the opposite equipment is faulty. If ... The opposite equipment is faulty The opposite equipment is not faulty Step 2 Replace the board that reports the alarm. ----End Then ... Clear the fault. Go to the next step.
Related Information
None.
A.2.28 ESN_FAILED
Description
The ESN_FAILED alarm indicates that the electronic serial number (ESN) of the equipment fails.
Attribute
Parameters
A Alarm Reference
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Name Meaning
Parameter 1 Indicates the number of the SCC board that reports the ESN_FAILED alarm.
Impact on System
None.
Possible Causes
l l
Reading the equipment ESN fails. Errors occur in the verification of the read equipment ESN.
Handling Procedure
Replace the SCC board that reports the ESN_FAILED alarm. ----End
Related Information
None.
A.2.29 ESN_INVALID
Description
The ESN_INVALID alarm indicates that the electronic serial number (ESN) of the equipment is invalid.
Attribute
Parameters
Parameter 1 Indicates the number of the SCC board that reports the ESN_INVALID alarm.
A Alarm Reference
Impact on System
None.
Possible Causes
Verification of the ESN that is read from the SCC board is normal, but the ESN cannot be identified.
Handling Procedure
Contact Huawei engineers to upgrade the NE software. ----End
Related Information
None.
A.2.30 ETH_LOS
Description
The ETH_LOS is an alarm indicating loss of network port connection on the data board.
Attribute
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 Parameter 1 Meaning Indicates the number of the port that reports the alarm. For example, "0x01" indicates that the alarm is reported by the first Ethernet port of this board.
Parameters 23 The value is always 0x00 0x01.
Impact on System
The services of the port that reports the ETH_LOS alarm are interrupted.
A Alarm Reference
Possible Causes
l l l
The network cable connection at the port where the ETH_LOS alarm occurs is faulty. The equipment that interconnects with the port where the ETH_LOS alarm occurs is faulty. The working mode of the port where the ETH_LOS alarm occurs is different from that of the interconnected equipment.
Handling Procedure
Step 1 Check whether the network cable that is connected to the port where the ETH_LOS alarm occurs is loose or damaged. If ... Yes Not Then ... Reconnect or replace the network cable. Go to the next step.
Step 2 Check whether the equipment that interconnects with the port where the ETH_LOS alarm occurs is faulty. If ... Yes Not Then ... Remove the fault of the interconnected equipment. Go to the next step.
Step 3 Check whether the working mode of the port where the ETH_LOS alarm occurs is the same as that of the interconnected equipment. If ... Not Yes Then ... Correct the configuration of the port working modes. Go to the next step.
Step 4 Replace the board on which the ETH_LOS alarm occurs. ----End
Related Information
None.
A.2.31 EXT_SYNC_LOS
Description
The EXT_SYNC_LOS alarm indicates "loss of external synchronous source".
Attribute
A-42 Huawei Technologies Proprietary
Alarm Type Equipment alarm

Issue 06 (2007-12-30)
A Alarm Reference
Parameters
Parameter 1 Indicates the number of the external clock that reports the alarm. For example, "0x01" indicates the alarm is reported by the first external clock.
Impact on System
l
If the clock source priority table is configured with the external and internal clock sources only, the internal clock source is traced and the clock enters the free-run mode after the loss of the external clock source. If the clock source priority table is configured with other valid clock sources, the loss of the external clock source can trigger clock protection switching.
Possible Causes
The clock priority table has the external clock source, but the external clock source cannot be detected or is unavailable.
Handling Procedure
Step 1 Check if the opposite clock source device is faulty. If ... The opposite equipment is faulty The opposite equipment is not faulty Step 2 Check if the external clock cable is normal. If ... The cables are abnormal The cables are normal Then ... Replace the cables. Go to the next step. Then ... Clear the fault. Go to the next step.
Step 3 Replace the cross-connect and timing board that connects the clock source reporting the alarm. ----End
Related Information
None.
A.2.32 FAN_FAIL
A Alarm Reference
Description
The FAN_FAIL alarm indicates "fan failed".
Attribute
Parameters
None.
Impact on System
The system heat dissipation is affected.
Possible Causes
l l
The board is faulty. The board and the backplane are poorly connected.
Handling Procedure
Step 1 Remove and insert the fan board. Clear the dust on the fan and re-install the fan board. If ... The alarm disappears after the board is removed and inserted The alarm persists after the board is removed and inserted Step 2 Replace the board that reports the alarm. ----End Then ... The fault is cleared and the troubleshooting is complete. Go to the next step.
Related Information
None.
A.2.33 FCS_ERR
Description
The FCS_ERR alarm indicates that errors occur in the verification of the frame check sequence (FCS). If errors occur when a board performs the FCS verification of the received frames, this board reports the FCS_ERR alarm.
A Alarm Reference
Attribute
Parameters
Parameters 23 Indicates the number of the path that reports the alarm. For example, "0x00 0x01" indicates that the alarm is reported by the first path.
Impact on System
When the encapsulation protocol or the encapsulation parameter of the Ethernet service source is different from that of the Ethernet service sink, the service is interrupted or bit errors exist in the service.
Possible Causes
l
The encapsulation protocol or the encapsulation parameter of the Ethernet service source is different from that of the Ethernet service sink. Bit errors exist in the service path.
Handling Procedure
Step 1 Check whether the encapsulation protocol of the Ethernet service source is the same as that of the Ethernet service sink. If ... Not Yes Then ... Correct the configuration. Go to the next step.
Step 2 Check whether the encapsulation parameter of the Ethernet service source is the same as that of the Ethernet service sink. If ... Not Yes Then ... Correct the configuration. Go to the next step.
Step 3 Check whether any bit error alarm or performance event occurs on the line boards through which the service travels.
A Alarm Reference
If ... Yes No
Then ... Handle the alarm or performance event. Go to the next step.
Step 4 Replace the board on which the FCS_ERR alarm occurs. If ... The FCS_ERR alarm is cleared after the board is replaced The FCS_ERR alarm persists after the board is replaced Step 5 Replace the cross-connect board. ----End Then ... The fault is removed. End the alarm handling. Go to the next step.
Related Information
None.
A.2.34 HARD_BAD
Description
The HARD_BAD alarm indicates "hardware error".
Attribute
Alarm Severity Critical Alarm Type Equipment alarm
Parameters
A-46
Issue 06 (2007-12-30)
A Alarm Reference
Name
Meaning
l l l l l l l l l l l
Parameter 1 Indicates the fault cause. "0x01" indicates the power module is working abnormally. "0x02" indicates the board is improperly installed. "0x03" indicates the 38M system clock 1 is abnormal. "0x04" indicates the 38M system clock 2 is abnormal. "0x05" indicates the 2M clock source is abnormal. "0x06" indicates the digital phased-locked loop is abnormal. "0x07" indicates the 38M service clock is lost. "0x08" indicates the bus is abnormal. "0x09" indicates the TPS protection board is abnormal. "0x0A" indicates the primary crystal oscillator stops oscillating. "0x0B" indicates the frequency offset of the primary crystal oscillator is excessive. "0x0C" indicates the secondary crystal oscillator stops oscillating. "0x0D" indicates the processor (CPU/DSP/coprocessor) is faulty. "0x0E" indicates the storage components are faulty. "0x0F" indicates the programmable logic device is faulty. "0x10" indicates the SDH components are faulty. "0x11" indicates the data communication components are faulty. "0x12" indicates the clock components are faulty. "0x13" indicates the interface components are faulty. "0x14" indicates the power components are faulty. "0x15" indicates other faults. "0x16" indicates the analog phase-locked loop is abnormal. "0x17" indicates the 32M clock is unavailable. "0x18" indicates the 66M clock is unavailable. "0x19" indicates the 25M clock is unavailable.
l l l l l l l l l l l l l l
Impact on System
The board that reports the alarm cannot operate.
Possible Causes
l l l
The board is faulty. The board and the backplane are poorly connected. The slot is faulty.
Issue 06 (2007-12-30)
A-47
A Alarm Reference
Handling Procedure
Step 1 Remove and insert the board again. If ... The alarm disappears after the board is removed and inserted The alarm persists after the board is removed and inserted Step 2 Replace the board that reports the alarm. If ... The alarm disappears after the board is replaced The alarm persists after the board is replaced Then ... The fault is cleared and the troubleshooting is complete. Go to the next step. Then ... The fault is cleared and the troubleshooting is complete. Go to the next step.
Step 3 Install the board that reports the alarm into another slot. If the board reports no alarm in the new slot, it indicates that the previous slot is faulty. Step 4 Keep the board working in the new slot, and contact technical support engineers of Huawei. ----End
Related Information
None.
A.2.35 HP_CROSSTR
Description
The HP_CROSSTR alarm indicates "higher order path performance over threshold". When the board detects higher order path bit error performance events exceed the preset threshold, this alarm is reported.
Attribute
Parameters
A Alarm Reference
Name Parameter 1
Meaning Indicates the number of the line port that reports the alarm. For example, "0x01" indicates the alarm is reported by first port of the board.
Parameter 23 Indicates the number of the path that reports the alarm. Parameter 45
l
The higher two bits of Parameter 4 indicate the performance monitoring period. When the value of the higher two bits is "01", the monitoring period is 15 minutes. When the value of the higher two bits is "02", the monitoring period is 24 hours. The lower six bits of Parameter 4 together with Parameter 5 indicate the performance event ID.
Impact on System
The services contain a large amount of bit errors and the services may be interrupted.
Possible Causes
Higher order path bit error performance events exceed the preset threshold.
Handling Procedure
Step 1 View the threshold crossing record of higher order path bit error performance events to determine the performance event that exceeds the preset threshold. Step 2 Handle the performance event that exceeds the threshold. ----End
Related Information
None.
A.2.36 HP_LOM
Description
The HP_LOM alarm indicates "higher order path loss of multiframe". When the board detects the H4 byte and the expected multiframe sequence mismatch, this alarm is reported.
Attribute
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
A Alarm Reference
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 Parameter 1 Meaning Indicates the number of the line port that reports the alarm. For example, "0x01" indicates the alarm is reported by first port of the board.
Impact on System
The services on the channel are interrupted. If the services are configured with protection, the protection switching can be triggered.
Possible Causes
l l
Handling Procedure
Step 1 Replace the line board of the opposite station. If ... The alarm disappears after the board is replaced The alarm persists after the board is replaced Then ... The fault is cleared and the troubleshooting is complete. Go to the next step.
Step 2 Replace the cross-connect and timing board of the opposite station. If ... The alarm disappears after the board is replaced The alarm persists after the board is replaced Step 3 Replace the board that reports the alarm. ----End Then ... The fault is cleared and the troubleshooting is complete. Go to the next step.
Related Information
None.
A.2.37 HP_RDI
A Alarm Reference
Description
The HP_RDI alarm indicates "higher order path remote defect indication". When the board detects bit 5 of the G1 byte is "1", this alarm is reported.
Attribute
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 Parameter 1 Meaning Indicates the number of the line port that reports the alarm. For example, "0x01" indicates the alarm is reported by first port of the board.
Impact on System
This alarm does not affect the local station. It indicates that the receiving services of the opposite station are interrupted.
Possible Causes
The local station detects an alarm from the opposite station, indicating remote higher order path defect.
Handling Procedure
Step 1 Determine the AU-4 path that reports the alarm according to alarm parameters. Step 2 Clear the alarm on the AU-4 path of the opposite station. ----End
Related Information
None.
A.2.38 HP_REI
A Alarm Reference
Description
The HP_REI alarm indicates "higher order path remote error indication". When the board detects bit 1 to bit 4 of the G1 byte is "1" to "8", this alarm is reported.
Attribute
Alarm Severity Warning Alarm Type Communication alarm
Parameters
Impact on System
The alarm does not affect the local station. It only indicates that the services received by the opposite station have bit errors.
Possible Causes
The local station detects an alarm from the opposite station, indicating remote higher order path bit errors.
Handling Procedure
Step 1 Determine the AU-4 path that reports the alarm according to alarm parameters. Step 2 Handle the HP_BBE performance event on the AU-4 path of the opposite station. ----End
Related Information
None.
A.2.39 HP_SLM
A Alarm Reference
Description
The HP_SLM alarm indicates "higher order path signal label mismatch". When the board detects the C2 byte mismatch, this alarm is reported.
Attribute
Parameters
Impact on System
None.
Possible Causes
l
The C2 byte to be received by the local station mismatches the C2 byte transmitted by the opposite station. The data configuration is wrong.
Handling Procedure
Step 1 Determine the AU-4 path that reports the alarm according to alarm parameters. Step 2 If the port that reports the alarm is the SDH port used to interconnect ATM/Ethernet equipment, configure the services to be VC-4 pass-through services. If ... The alarm disappears after the configurations are modified The alarm still persists after the configurations are modified
Issue 06 (2007-12-30)
A-53
A Alarm Reference
Step 3 Unify the service types at the source and sink stations of the AU-4 channel. ----End
Related Information
None.
A.2.40 HP_TIM
Description
The HP_TIM alarm indicates "higher order path trace identifier mismatch". When the board detects the J1 byte mismatch, this alarm is reported.
Attribute
Parameters
Impact on System
If the services are configured with protection and this alarm is the triggering condition, the protection switching can be triggered.
Possible Causes
l
The J1 byte to be received at the local station is different from the J1 byte transmitted from the opposite station. Data configuration at the intermediate nodes is incorrect.
A-54
Issue 06 (2007-12-30)
A Alarm Reference
Handling Procedure
Step 1 Determine the AU-4 path that reports the alarm according to alarm parameters. Step 2 If the port that reports the alarm is the SDH port used to interconnect ATM/Ethernet equipment, configure the services to be VC-4 pass-through services. If ... The alarm disappears after the configurations are modified The alarm still persists after the configurations are modified Then ... The fault is cleared and the troubleshooting is complete. Go to the next step.
Step 3 Set the J1 byte to be received of the local station to the disable mode. Alternatively, set the J1 byte to be received at the local station to be the same as that transmitted from the opposite station. Step 4 Check whether the cross-connections of the intermediate nodes through which the service travels are correctly configured. If not, correct the cross-connection configuration. ----End
Related Information
None.
A.2.41 HP_UNEQ
Description
The HP_UNEQ alarm indicates "higher order path unequipped". When the board detects the C2 byte is "0", this alarm is reported.
Attribute
Parameters
Issue 06 (2007-12-30)
A Alarm Reference
Name
Meaning
Impact on System
Services on the AU-4 path are unavailable. If the services are configured with protection and this alarm is the triggering condition, the protection switching can be triggered.
Possible Causes
The line port of the local station is configured with services, but the line port of the opposite station is not.
Handling Procedure
Step 1 Determine the AU-4 path that reports the alarm according to alarm parameters. Step 2 Configure line services for the opposite station. ----End
Related Information
None.
A.2.42 HPAD_CROSSTR
Description
The HPAD_CROSSTR alarm indicates "higher order path adaptation performance over threshold". When the board detects the TU pointer adaptation performance events over the preset threshold, this alarm is reported.
Attribute
Parameters
A Alarm Reference
Name Parameter 1
l
Impact on System
Bit errors may occur to the services.
Possible Causes
The TU pointer adaptation performance events exceed the preset threshold.
Handling Procedure
Step 1 View the threshold crossing record of the TU pointer adaptation performance events, and determine the performance event that exceeds the preset threshold. Step 2 Handle the performance event that exceeds the threshold. ----End
Related Information
None.
A.2.43 HSB_INDI
Description
The HSB_INDI alarm indicates "microwave equipment HSB switching indication".
Attribute
Parameters
A Alarm Reference
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Name Parameter 1 Parameter 2 Meaning Indicates the protection group number. Indicates the slot where the working board is seated.
Impact on System
The services are interrupted during the protection switching and return to normal after the switching is complete.
Possible Causes
1+1 HSB protection switching occurs.
Handling Procedure
Determine the cause for switching and perform relevant operations. ----End
Related Information
None.
A.2.44 HSM_INDI
Description
The HSM_INDI alarm indicates "microwave channels HSM switching indication".
Attribute
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 Parameter 1
A-58
Meaning Indicates the protection group number.

A Alarm Reference
Name Parameter 2
Meaning Indicates the slot where the working board is seated.
Impact on System
Bit errors cannot be generated during channel switching. This alarm has no impact on the services.
Possible Causes
1+1 FD/SD protection switching occurs.
Handling Procedure
Related Information
None.
A.2.45 IF_INPWR_ABN
Description
The IF_INPWR_ABN alarm indicates "abnormal input IF power of the ODU".
Attribute
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 Parameter 1 Meaning
l l
"0x01" indicates input power is too high. "0x02" indicates input power is too low.
Issue 06 (2007-12-30)
A-59
A Alarm Reference
Impact on System
The services on the ODU are interrupted. If 1+1 protection is configured, 1+1 HSB switching can be triggered.
Possible Causes
l l l l
There is an inloop operation on the IF port. The IF boards are faulty. The IF cables are faulty. The ODU is faulty.
Handling Procedure
Step 1 Check the loopback status of the IF port. If ... There is an inloop operation on the IF port The IF port is not looped back Step 2 Check if the IF cables are soggy, broken, or pressed. If ... The IF cables are soggy, broken, or pressed The IF cables are not soggy, broken, or pressed Then ... Replace the IF cables. Go to the next step. Then ... Cancel the loopback operation. Go to the next step.
Step 3 Check if the cable connector workmanship meets the requirement. If ... It does not meet the requirement It meets the requirement Then ... Remade connectors. Go to the next step.
Step 4 Replace the IF board connecting with the ODU that reports the alarm. If ... The alarm disappears after the board is replaced The alarm persists after the board is replaced Step 5 Replace the ODU that reports the alarm. ----End Then ... The fault is cleared and the troubleshooting is complete. Go to the next step.
Related Information
None.
A Alarm Reference
A.2.46 IN_PWR_HIGH
Description
The IN_PWR_HIGH alarm indicates "input power too high".
Attribute
Parameters
Parameter 1 Indicates the number of the optical interface that reports the alarm. For example, "0x01" indicates the alarm is reported by the first optical interface of the board.
Impact on System
Bit errors occur to the services of the optical interface.
Possible Causes
l l
The transmit optical power of the opposite station is too high. The type of the optical module is incorrect.
Handling Procedure
Step 1 Determine the optical interface that reports the alarm according to alarm parameters. Step 2 Check if the type of the SFP optical modules of the receive and transmit ends is correct according to transmission distance. If ... The type is incorrect The type is correct Then ... Replace the optical modules. Go to the next step.
Step 3 Query the performance events of the transmit optical power at the opposite station. If ... Then ...
The transmit optical power does not meet the requirement Replace the optical modules.
A Alarm Reference
If ... The transmit optical power meets the requirement
Then ... Go to the next step.
Step 4 Add a proper optical attenuator to reduce the receive optical power. ----End
Related Information
None.
A.2.47 IN_PWR_LOW
Description
The IN_PWR_LOW alarm indicates "input power too low".
Attribute
Parameters
Impact on System
Bit errors may occur to the services on the optical interface.
Possible Causes
l l l
The transmit optical power of the opposite station is too low. The fiber performance degrades. The type of the optical module is incorrect.
Handling Procedure
Step 1 Determine the optical interface that reports the alarm according to alarm parameters.
A Alarm Reference
Step 2 Check if the type of the SFP optical modules of the receive and transmit ends is correct according to transmission distance. If ... The type is incorrect The type is correct Then ... Replace the optical modules. Go to the next step.
Step 3 Query the performance events of the transmit optical power at the opposite station. If ... Then ...
The transmit optical power does not meet the requirement Replace the optical modules. The transmit optical power meets the requirement Step 4 Clean the optical fiber connector. If ... Then ... Go to the next step.
The alarm disappears after the connector The fault is cleared and the troubleshooting is is cleaned complete. The alarm still persists after the connector is cleaned Step 5 Check if the fiber is broken or pressed. If ... The fiber is broken or pressed The fiber is not broken or pressed Then ... Replace the fiber. Go to the next step. Go to the next step.
Step 6 Add a proper optical amplifier to increase the receive optical power. ----End
Related Information
None.
A.2.48 J0_MM
Description
The J0_MM alarm indicates "trace identifier mismatch". When the board detects the J0 byte mismatch, this alarm is reported.
Attribute
Issue 06 (2007-12-30)
Alarm Type Communication alarm

A Alarm Reference
Parameters
Impact on System
None.
Possible Causes
The J0 byte to be received by the local station mismatches the J0 byte transmitted by the opposite station.
Handling Procedure
Step 1 Determine the line port that reports the alarm according to alarm parameters. Step 2 Set the J0 byte to be received of the local station to the disable mode. ----End
Related Information
None.
A.2.49 K1_K2_M
Description
The K1_K2_M is an indication alarm of mismatch of the K1 and K2 bytes. If a board detects that the transmitted K1 byte (bits 58) indicates a path number different from that the received K2 byte indicates, this board reports the K1_K2_M alarm.
Attribute
Parameters
A Alarm Reference
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 Indicates the type of a protection group. For example, "0x01" indicates the linear MSP. Parameter 2 Indicates the number of the protection group that reports the K1_K2_M alarm. For example, "0x01" indicates that the alarm is reported by the first protection group.
Impact on System
When the K1_K2_M occurs, the MSP switching might be incorrect or even fail.
Possible Causes
l
The switching modes of the service source and sink are single-ended switching and dualended switching, respectively. The equipment is faulty.
Handling Procedure
Step 1 Check whether the services are correctly configured. If ... Not Yes Then ... Correct the configuration. Go to the next step.
Step 2 Check whether the fiber connections are correct. If ... Not Yes Then ... Correct the fiber connections. Go to the next step.
Step 3 Replace the line board at the opposite station. If ... The K1_K2_M alarm is cleared after the board is replaced The K1_K2_M persists Then ... The fault is removed. End the alarm handling. Go to the next step.
Step 4 Replace the board that reports the K1_K2_M alarm. ----End
Related Information
None.
A Alarm Reference
A.2.50 K2_M
Description
The K2_M is an indication alarm of mismatch of the K2 byte. When a board detects that the received K2 byte (bit 5) indicates a protection mode different from that of the local NE, this board reports the K2_M alarm.
Attribute
Parameters
Parameter 1 Indicates the type of a protection group. For example, "0x01" indicates the linear MSP. Parameter 2 Indicates the number of the protection group that reports the K2_M alarm. For example, "0x01" indicates that the alarm is reported by the first protection group.
Impact on System
When the K2_M occurs, the MSP switching might be incorrect or even fail.
Possible Causes
l l l
Two NEs on a linear MS are configured with different MSP modes (1+1 or 1:N). When the MSP switching occurs, the protocol at the opposite station is disabled. The equipment is faulty.
Handling Procedure
Step 1 Check whether two terminal NEs on a linear MS are configured with the same MSP mode (1+1 or 1:N). If ... Not Yes Then ... Correct the configuration. Go to the next step.
Step 2 Check whether the fiber connections are correct.

A Alarm Reference
If ... Not Yes
Then ... Correct the fiber connections. Go to the next step.
Step 3 Replace the line board at the opposite station. If ... Then ...
The K2_M alarm is cleared after the board The fault is removed. End the alarm handling. is replaced The K2_M persists Step 4 Replace the board that reports the K2_M alarm. ----End Go to the next step.
Related Information
None.
A.2.51 LASER_CLOSED
Description
The LASER_CLOSED alarm indicates "laser closed alarm".
Attribute
Parameters
Impact on System
The optical interface cannot carry services.
A Alarm Reference
Possible Causes
The laser is shut down at the local station.
Handling Procedure
Step 1 Determine the optical interface that reports the alarm according to alarm parameters. Step 2 Find out why the laser is shut down and turn it on in a timely manner. ----End
Related Information
None.
A.2.52 LASER_MOD_ERR_EX
Description
The LASER_MOD_ERR_EX alarm indicates the pluggable optical module on the board mismatches the optical interface.
Attribute
Parameters
Impact on System
The services on the optical interface where the alarm occurs are interrupted.
Possible Causes
l
The optical module installed on the optical interface does not match the optical interface rate. The optical module is faulty.
A-68

l
A Alarm Reference
Handling Procedure
Step 1 Check if the optical module installed on the optical interface matches the optical interface rate. If ... Then ...
The optical module installed on the optical Replace the optical module with one that interface does not match the optical matches the optical interface rate. interface rate The optical module installed on the optical Replace the optical module with a new one of interface matches the optical interface rate the same type. Step 2 Check if the alarm is cleared. If ... The alarm disappears after the optical module is replaced The alarm persists after the optical module is replaced Step 3 Replace the reporting board. ----End Then ... The fault is cleared and the troubleshooting is complete. Go to the next step.
Related Information
None.
A.2.53 LCAS_FOPR
Description
The LCAS_FOPR alarm indicates that the link capacity adjustment scheme (LCAS) protocol in the receive direction fails. When the receive part of the LCAS module of a board detects an abnormal state in which the LCAS might fail to negotiate or cannot correctly negotiate, this board reports the LCAS_FOPR alarm.
Attribute
Parameters
A Alarm Reference
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Name Parameter 1 Meaning The value is always 0x01.
Impact on System
The Ethernet service is abnormal.
Possible Causes
l
The downlink virtual concatenation group (VCG) receives repeated sequence numbers due to incorrect configuration or bit errors in the link. The LCAS function of the opposite VCG is disabled. The downlink VCG simultaneously receives the FIXED and other LCAS control bytes due to incorrect configuration or bit errors in the link.
l l
Handling Procedure
Step 1 Check whether the LCAS enable state and the LCAS parameters are the same at near and far ends. If ... Not Yes Then ... Correctly enable the LCAS protocol at the local and the opposite NEs. Go to the next step.
Step 2 Check whether configurations of the local and opposite NEs are correct. That is, check whether an VCG at one NE is connected to multiple VCGs at the opposite NE. If ... The configuration is incorrect The configuration is correct Then ... Correct the configuration. Go to the next step.
Step 3 Check whether a fault such as failure or bit errors occurs in the service link. If ... Yes Not Then ... Remove the fault. Go to the next step.
Step 4 Disable the LCAS protocol at both the NEs, and then restart the protocol. Step 5 Replace the board that reports the LCAS_FOPR alarm. ----End
A Alarm Reference
Related Information
None.
A.2.54 LCAS_FOPT
Description
The LCAS_FOPT alarm indicates that the the LCAS protocol in the transmit direction fails. When the transmit part of the LCAS module of a board detects an abnormal state in which the LCAS might fail to negotiate or cannot correctly negotiate, this board reports the LCAS_FOPT alarm.
Attribute
Parameters
Impact on System
The Ethernet service is abnormal.
Possible Causes
l l
The LCAS protocol configuration is incorrect. The link is faulty.
Handling Procedure
Step 1 Check whether the LCAS enable state and the LCAS parameters are the same at both ends of the link. If ... Not
Issue 06 (2007-12-30)
Then ... Correctly enable the LCAS protocol at both ends of the link.
A Alarm Reference
If ... Yes
Step 2 Check whether a fault such as failure or bit errors occurs in the service link. If ... Yes Not Then ... Remove the fault. Go to the next step.
Step 3 Disable the LCAS protocol at both ends of the link, and then restart the protocol. If ... Then ...
The LCAS_FOPT alarm is cleared after the protocol is restarted End the alarm handling. The LCAS_FOPT alarm persists after the protocol is restarted Go to the next step. Step 4 Replace the board that reports the LCAS_FOPT alarm. ----End
Related Information
None.
A.2.55 LCAS_PLCR
Description
The LCAS_PLCR alarm indicates that part of the LCAS bandwidth in the receive direction is lost. 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 but is not zero, this board report the LCAS_PLCR alarm.
Attribute
Parameters
A-72

A Alarm Reference
Name
Meaning
Impact on System
The available Ethernet service bandwidth is smaller than the configured bandwidth.
Possible Causes
l
The number of paths or timeslots that are configured for the VCTRUNK at the opposite NE is different from that at the local NE. Some paths in the transmit direction of the opposite NE are faulty. Some paths in the receive direction of the local NE are faulty.
l l
Handling Procedure
Step 2 Check whether any path alarm exists in the transmit direction of the opposite NE. If ... Yes Not Then ... Handle the alarms. Go to the next step.
Step 3 Replace the board that reports the LCAS_PLCR alarm. ----End
Related Information
None.
A.2.56 LCAS_PLCT
Description
The LCAS_PLCT alarm indicates that all the LCAS bandwidth in the transmit direction is lost. 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 but is not zero, this board report the LCAS_PLCT alarm.
A Alarm Reference
Attribute
Parameters
Impact on System
The available Ethernet service bandwidth is smaller than the configured bandwidth.
Possible Causes
l
The number of paths or timeslots that are configured for the VCTRUNK at the opposite NE is different from that at the local NE. Some paths in the receive direction of the opposite NE are faulty. Some paths in the transmit direction of the local NE are faulty.
l l
Handling Procedure
Step 1 Check whether the VCTRUNKs at the transmit direction at the local NE and the receive directions at the opposite NE are configured with the same number of physical paths and timeslots. If ... Not Yes Then ... Correct the configuration. Go to the next step.
Step 2 Check whether any path alarm exists in the receive direction of the opposite NE. If ... Yes Not Then ... Handle the alarms. Go to the next step.
Step 3 Replace the board that reports the LCAS_PLCT alarm. ----End
A Alarm Reference
Related Information
None.
A.2.57 LCAS_TLCR
Description
The LCAS_TLCR alarm indicates that all the bandwidth in the LCAS receiving direction is lost. If zero path in the receive direction of the VCTRUNK with LCAS enabled carries the overload but more than zero path is configured to carry the overload, the LCAS_TLCR alarm is reported.
Attribute
Parameters
Impact on System
The Ethernet service is interrupted.
Possible Causes
l
The number of paths or timeslots that are configured for the VCTRUNK at the opposite NE is different from that at the local NE. The paths in the transmit direction of the opposite NE are faulty. The paths in the receive direction of the local NE are faulty.
l l
Handling Procedure
Step 1 Check whether the VCTRUNKs at the transmit and the receive directions at the local station are configured with the same number of physical paths and timeslots.
A Alarm Reference
If ... Not Yes
Then ... Correct the configuration. Go to the next step.
Step 3 Replace the board that reports the LCAS_TLCR alarm. ----End
Related Information
None.
A.2.58 LCAS_TLCT
Description
The LCAS_TLCT alarm indicates that all the LCAS bandwidth in the transmit direction is lost. If zero path in the transmit direction of the VCTRUNK with LCAS enabled carries the overload but more than zero path is configured to carry the overload, the LCAS_TLCT alarm is reported.
Attribute
Parameters
Impact on System
The Ethernet service is interrupted.
A Alarm Reference
Possible Causes
l
The number of paths or timeslots that are configured for the VCTRUNK at the opposite NE is different from that at the local NE. The paths in the transmit direction of the opposite NE are faulty. The paths in the receive direction of the local NE are faulty.
l l
Handling Procedure
Step 3 Replace the board that reports the LCAS_TLCT alarm. ----End
Related Information
None.
A.2.59 LOOP_ALM
Description
The LOOP_ALM alarm indicates "path loopback".
Attribute
Parameters
A Alarm Reference
Name Parameter 1
Parameter 23 Indicates the number of the path that reports the alarm. Parameter 4 Indicates the type of loopback.
l l l l l l l l l l l l l l l l l l l l l l l l
"0x00" indicates optical/electrical port inloop. "0x01" indicates optical/electrical port outloop. "0x02" indicates path inloop. "0x03" indicates path outloop. "0x04" indicates loopback at the user side. "0x05" indicates loopback at the microwave combination side. "0x06" indicates SPI inloop. "0x07" indicates SPI outloop. "0x08" indicates ATM layer inloop. "0x09" indicates ATM layer outloop. "0x0A" indicates PHY layer inloop. "0x0B" indicates PHY layer outloop. "0x0C" indicates MAC layer inloop. "0x0D" indicates MAC layer outloop. "0x0E" indicates VC-4 timeslot inloop. "0x0F" indicates VC-4 timeslot outloop. "0x10" indicates VC-3 timeslot inloop. "0x11" indicates VC-3 timeslot outloop. "0x12" indicates VC-12 timeslot inloop. "0x13" indicates VC-12 timeslot outloop. "0x14" indicates IF outloop. "0x15" indicates IF inloop. "0x16" indicates RF inloop. "0xFF" indicates one of the above loopback modes.
Impact on System
The loopback port/path cannot carry services.
Possible Causes
Loopback is performed at the local station.
A-78
Issue 06 (2007-12-30)
A Alarm Reference
Handling Procedure
Step 1 Determine the type of loopback according to alarm parameters. Step 2 Find out why the loopback is performed and cancel the loopback. ----End
Related Information
None.
A.2.60 LPS_UNI_BI_M
Description
The LPS_UNI_BI_M alarm indicates that the single-ended/dual-ended mode of the linear MSP mismatches.
Attribute
Parameters
Parameter 1 Indicates the number of the protection group that reports the alarm. For example, "0x01" indicates that the alarm is reported by the first protection group.
Impact on System
The system performs the switching in the single-ended mode.
Possible Causes
The LPS_UNI_BI_M alarm occurs under the following conditions:
l
The switching modes (single-ended or dual-ended) at the local and opposite NEs are different. The last three bits of the K2 byte are set to the indicated mode. The type of the protocol is set to the restructure protocol.
l l
Issue 06 (2007-12-30)
A Alarm Reference
Handling Procedure
Change the MSP switching mode. Set the linear MSP switching modes at the local and the opposite NEs to be the same. ----End
Related Information
None.
A.2.61 LP_CROSSTR
Description
The LP_CROSSTR alarm indicates "lower order path performance parameter over threshold". When the board detects the lower order path bit error performance events over the preset threshold, this alarm is reported.
Attribute
Parameters
l
Impact on System
A Alarm Reference
Possible Causes
Lower order path bit error performance events exceed the preset threshold.
Handling Procedure
Step 1 View the threshold crossing record of lower order path bit error performance events to determine the performance event that exceeds the preset threshold. Step 2 Handle the performance event that exceeds the threshold. ----End
Related Information
None.
A.2.62 LP_R_FIFO
Description
The LP_R_FIFO alarm indicates "FIFO overflow on the receiving side of the lower order path".
Attribute
Parameters
Impact on System
Bit errors occur to the services.
Possible Causes
l l
The board is faulty. The clock at the local station and that at the opposite station are asynchronous.
Issue 06 (2007-12-30)
A Alarm Reference
Handling Procedure
Step 1 Query if there are TU pointer adjustment performance events at the local and opposition stations. If ... There are TU pointer adjustment performance events Then ... Handle the performance events.
There are no TU pointer adjustment performance events Go to the next step. Step 2 Replace the board that reports the alarm. ----End
Related Information
None.
A.2.63 LP_RDI
Description
The LP_RDI alarm indicates "lower order path remote defect indication". When the board detects bit 8 of the V5 byte is "1", this alarm is reported.
Attribute
Parameters
Impact on System
A Alarm Reference
Possible Causes
The local station detects an alarm from the opposite station, indicating remote lower order path defect.
Handling Procedure
Clear the alarm on the lower order path of the opposite station. ----End
Related Information
None.
A.2.64 LP_RDI_VC12
Description
The LP_RDI_VC12 alarm is an VC-12 level path remote defect indication. If a board detects that bit 8 of the V5 byte is 1, this board reports this alarm.
Attribute
Parameters
Parameters 23 Indicates the number of the VC-12 path that reports the alarm. For example, "0x00 0x01" indicates that the alarm is reported by the first VC-12 path.
Impact on System
Possible Causes
The local NE detects the return message from the opposite NE that indicates the service in a lower order path fails to be received at the opposite NE.
A Alarm Reference
Handling Procedure
Handle the lower order path alarm at the opposite NE. ----End
Related Information
None.
A.2.65 LP_RDI_VC3
Description
The LP_RDI_VC3 alarm is an VC-3 level path remote defect indication. If a board detects that bit 5 of the G1 byte is 1, this board reports this alarm.
Attribute
Parameters
Impact on System
Possible Causes
The local NE detects the return message from the opposite NE that indicates the service in a lower order path fails to be received at the opposite NE.
Handling Procedure
Handle the lower order path alarm at the opposite NE. ----End
A Alarm Reference
Related Information
None.
A.2.66 LP_REI
Description
The LP_REI alarm indicates "lower order path remote error indication". When the board detects bit 3 of the V5 byte is "1", this alarm is reported.
Attribute
Parameters
Impact on System
This alarm does not affect the local station. It indicates that the receiving services of the opposite station have bit errors.
Possible Causes
The local station detects an alarm from the opposite station, indicating remote lower order path bit errors.
Handling Procedure
Handle the LP_BBE performance event of the opposite station. ----End
Related Information
None.
A Alarm Reference
A.2.67 LP_REI_VC12
Description
LP_REI_VC12 alarm is a VC-12 level path remote error indication. If a board detects that bit 3 of the V5 byte is "1", this alarm is reported.
Attribute
Parameters
Impact on System
Possible Causes
The local station detects an alarm from the opposite station, indicating remote lower order path bit errors.
Handling Procedure
Handle the LP_BBE performance event of the opposite station. ----End
Related Information
None.
A.2.68 LP_REI_VC3
A Alarm Reference
Description
The LP_REI_VC3 alarm is a VC-3 level path remote error indication. If a board detects that any bit of bits 14 of the G1 byte is 1, this board reports this alarm.
Attribute
Parameters
Impact on System
Bit errors exist in the service in the receive direction of the opposite NE.
Possible Causes
The local NE detects the return message from the opposite NE indicating that bit errors exist in a lower order path at the opposite NE.
Handling Procedure
Handle the VC3BBE performance event. ----End
Related Information
None.
A.2.69 LP_RFI
Description
The LP_RFI alarm indicates "lower order path remote failure indication". When the board detects bit 4 of the V5 byte is "1", this alarm is reported.
A Alarm Reference
Attribute
Parameters
Impact on System
Possible Causes
The local station detects an alarm from the opposite station, indicating remote lower order path failure.
Handling Procedure
Clear the alarm on the lower order path of the opposite station. ----End
Related Information
None.
A.2.70 LP_SIZE_ERR
Description
The LP_SIZE_ERR alarm indicates "TU structure error".
Attribute
Alarm Type Service alarm

Issue 06 (2007-12-30)
A Alarm Reference
Parameters
Impact on System
The services on the board are interrupted.
Possible Causes
l l
The mapping structure configuration is incorrect. The tributary board is faulty.
Handling Procedure
Step 1 Check if the types of the add/drop services configured are consistent with the service types that the board supports. If ... The service types are inconsistent The service types are consistent Step 2 Replace the board that reports the alarm. ----End Then ... Modify the configuration data. Go to the next step.
Related Information
None.
A.2.71 LP_SLM
Description
The LP_SLM alarm indicates "lower order path signal label mismatch". When the board detects the V5 byte signal label mismatch, this alarm is reported.
Issue 06 (2007-12-30)
A-89
A Alarm Reference
Attribute
Parameters
Impact on System
The service in this lower order path is unavailable.
Possible Causes
The V5 byte signal label to be received by the local station mismatches that transmitted by the opposite station.
Handling Procedure
Modify the V5 byte signal label to be received of the local station or that transmitted by the opposite station to make the signal labels of the two stations identical. ----End
Related Information
None.
A.2.72 LP_SLM_VC12
Description
The LP_SLM_VC12 alarm indicates that the signal identifier of a VC-12 path mismatches. If a board detects a V5 signal mismatch, this board reports the LP_SLM_VC12 alarm.
A-90
Issue 06 (2007-12-30)
A Alarm Reference
Attribute
Parameters
Impact on System
Possible Causes
The signal identifier in the V5 byte to be received at the local NE is different from that transmitted from the opposite NE.
Handling Procedure
Modify the signal identifier in V5 byte to be received at the local NE and that transmitted from the opposite NE to be the same. ----End
Related Information
None.
A.2.73 LP_SLM_VC3
Description
The LP_SLM_VC3 alarm indicates that the signal identifier of a VC-3 path mismatches. If a board detects this mismatch, this board reports the LP_SLM_VC3 alarm.
Issue 06 (2007-12-30)
A-91
A Alarm Reference
Attribute
Parameters
Impact on System
Possible Causes
The signal identifier in the C2 byte to be received at the local NE is different from that at the opposite NE.
Handling Procedure
Modify the signal identifier to be received at the local NE and that transmitted from the opposite NE to be the same. ----End
Related Information
None.
A.2.74 LP_T_FIFO
Description
The LP_T_FIFO alarm indicates "FIFO overflow on the transmission side of the lower order path".
A-92
Issue 06 (2007-12-30)
A Alarm Reference
Attribute
Parameters
Impact on System
Possible Causes
l l
The board is faulty. The frequency offset of the input signal is excessive.
Handling Procedure
Step 1 Test the frequency offset of the input signal. If ... The frequency offset is excessive Then ... Troubleshoot the opposite station equipment.
The frequency offset meets the requirement Go to the next step. Step 2 Replace the board that reports the alarm. ----End
Related Information
None.
A.2.75 LP_TIM
Description
The LP_TIM alarm indicates "lower order path trace identifier mismatch". When the board detects the J2 byte mismatch, this alarm is reported.
A Alarm Reference
Attribute
Parameters
Impact on System
None.
Possible Causes
l
Handling Procedure
Step 1 Set the J2 byte to be received of the local station to the disable mode. Alternatively, set the J1 byte to be received at the local station to be the same as that transmitted from the opposite station. Step 2 Check whether the cross-connections of the intermediate nodes through which the service travels are correctly configured. If not, correct the cross-connection configuration. ----End
Related Information
None.
A.2.76 LP_TIM_VC12
Description
The LP_TIM_VC12 alarm indicates that the VC-12 lower path trace identifier mismatches. If a board detects the mismatch of the J2 byte in a VC-12 path, this board reports the LP_TIM_VC12.
A Alarm Reference
Attribute
Parameters
Impact on System
None.
Possible Causes
l
Handling Procedure
Step 1 Set the J2 byte to be received at the local NE to disabled or to be the same as the J2 byte transmitted from the opposite NE. Step 2 Check whether the cross-connections of the intermediate nodes through which the service travels are correctly configured. If not, correct the cross-connection configuration. ----End
Related Information
None.
A.2.77 LP_TIM_VC3
Description
The LP_TIM_VC3 alarm indicates that the VC-3 lower path trace identifier mismatches. If a board detects the mismatch of the J1 byte in a VC-3 path, this board reports the LP_TIM_VC3.
A Alarm Reference
Attribute
Parameters
Impact on System
None.
Possible Causes
l
Handling Procedure
Step 1 Set the J1 byte to be received at the local NE to disabled or to be the same as the J1 byte transmitted from the opposite NE. Step 2 Check whether the cross-connections of the intermediate nodes through which the service travels are correctly configured. If not, correct the cross-connection configuration. ----End
Related Information
None.
A.2.78 LP_UNEQ
Description
The LP_UNEQ alarm indicates "lower order path unequipped". When the board detects the V5 byte signal label is "0", this alarm is reported.
A Alarm Reference
Attribute
Parameters
Impact on System
The service on this path is unavailable.
Possible Causes
The tributary path of the local station is configured with services, but that of the opposite station is not.
Handling Procedure
Configure tributary services for the opposite station. ----End
Related Information
None.
A.2.79 LP_UNEQ_VC12
Description
The LP_UNEQ_VC12 alarm indicates that the VC-12 lower order path is unequipped. If a board detects that the signal identifier in the V5 byte is 0, this board reports the LP_UNEQ_VC12 alarm.
Issue 06 (2007-12-30)
A-97
A Alarm Reference
Attribute
Parameters
Impact on System
The service on this path is unavailable. If the service is configured with a protection, a switching is triggered.
Possible Causes
Data configuration errors are as follows:
l
The tributary path at the local NE is configured with services while the corresponding tributary path at the opposite NE is not configured with services. The cross-connection configurations are incorrect at intermediate NEs.
Handling Procedure
Step 1 Check whether the corresponding tributary path is configured with services at the opposite NE. If ... Not Yes Then ... Correctly configure the services. Go to the next step.
Step 2 Check whether the cross-connection configurations at intermediate NEs are correct. If not, correct the configurations. ----End
Related Information
None.
A.2.80 LP_UNEQ_VC3
A Alarm Reference
Description
The LP_UNEQ_VC3 alarm indicates that the VC-3 lower order path is unequipped. If a board detects that the signal identifier in the C2 byte is 0, this board reports the LP_UNEQ_VC3 alarm.
Attribute
Parameters
Impact on System
The service on this path is unavailable. If the service is configured with a protection, a switching is triggered.
Possible Causes
Data configuration errors are as follows:
l
The tributary path at the local NE is configured with services while the corresponding tributary path at the opposite NE is not configured with services. The cross-connection configurations are incorrect at intermediate NEs.
Handling Procedure
Step 1 Check whether the corresponding tributary path is configured with services at the opposite NE. If ... Not Yes Then ... Correctly configure the services. Go to the next step.
Step 2 Check whether the cross-connection configurations at intermediate NEs are correct. If not, correct the configurations. ----End
A Alarm Reference
Related Information
None.
A.2.81 LSR_NO_FITED
Description
The LSR_NO_FITED alarm indicates "laser not installed".
Attribute
Parameters
Impact on System
The optical interface cannot carry services.
Possible Causes
The laser of the local station is not installed.
Handling Procedure
Step 1 Determine the optical interface that reports the alarm according to alarm parameters. Step 2 Find out why the laser is not installed and install it in a timely manner. ----End
Related Information
None.
A.2.82 LTI
A Alarm Reference
Description
The LTI alarm indicates "loss of timing input". When all the synchronous sources are lost for the NE, this alarm is reported.
Attribute
Parameters
l l
"0x01" indicates all the synchronous sources of the system clock are lost. "0x02" indicates all the synchronous sources of the 2M phase-locked source.
Impact on System
The clock enters the free-run mode and cannot be synchronous with other NE clocks.
Possible Causes
l l
The clock configuration is incorrect. The clock sources in the clock source priority table fail.
Handling Procedure
Step 1 Check if the data in the clock source priority table complies with the network planning. If ... The configurations are incorrect The configurations are correct Then ... Modify the configurations. Go to the next step.
Step 2 Determine the synchronous source according to the clock source priority table. If ... Then ...
The synchronous source is the external clock Check if the external clock source and external clock cable are faulty. The synchronous source is the line clock The synchronous source is the IF clock Check if the line and line board are faulty. Check if the microwave link, IF cable and IF board are faulty.
A-101
Issue 06 (2007-12-30)
A Alarm Reference
If ... The synchronous source is the tributary clock ----End
Then ... Check if the tributary clock source, relay cable and tributary board is faulty.
Related Information
None.
A.2.83 MS_AIS
Description
The MS_AIS alarm indicates "multiplex section alarm indication". When the board detects bit 6 to bit 8 of the K2 byte in three consecutive frames are "111", this alarm is reported.
Attribute
Parameters
Impact on System
The services on the line port are interrupted. If the services are configured with protection, the protection switching can be triggered.
Possible Causes
l l
A-102
Issue 06 (2007-12-30)
A Alarm Reference
Handling Procedure
Related Information
None.
A.2.84 MS_CROSSTR
Description
The MS_CROSSTR alarm indicates "multiplex section performance over threshold". When the board detects the multiplex section bit error performance events over the preset threshold, this alarm is reported.
Attribute
Parameters
A Alarm Reference
Name Parameter 1
l
The two most significant bits of the parameter 4 indicates the performance monitoring period (01 means that the monitoring period is 15 minutes and 02 means that the monitoring period is 24 hours). The parameter 5 and the six least significant bits of the parameter 4 together indicate the ID of a performance event.
Impact on System
Possible Causes
The multiplex section bit error performance events exceed the preset threshold.
Handling Procedure
Step 1 View the threshold crossing record of multiplex section bit error performance events to determine the performance event that exceeds the preset threshold. Step 2 Handle the performance event that exceeds the threshold. ----End
Related Information
None.
A.2.85 MS_RDI
Description
The MS_RDI alarm indicates "multiplex section remote defect indication". When the board detects bit 6 to bit 8 of the K2 byte are "110", this alarm is reported.
Attribute
Parameters
A Alarm Reference
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the number of the line port that reports the alarm. For example, "0x01" indicates the alarm is reported by first port of the board.
Impact on System
Possible Causes
The local station detects an alarm from the opposite station, indicating remote multiplex section receiving failure.
Handling Procedure
Step 1 Determine the line port that reports the alarm according to alarm parameters. Step 2 Clear the alarm on the multiplex section of the opposite station. ----End
Related Information
None.
A.2.86 MS_REI
Description
The MS_REI alarm indicates "multiplex section remote error indication". When the board detects the M1 byte is non-zero, this alarm is reported.
Attribute
Alarm Severity Warning Alarm Type Service alarm
Parameters
A Alarm Reference
Name Parameter 1
Impact on System
The alarm does not affect the local station. It only indicates that the services received by the opposite station have bit errors.
Possible Causes
The local station detects an alarm from the opposite station, indicating remote multiplex section bit errors.
Handling Procedure
Step 1 Determine the line port that reports the alarm according to alarm parameters. Step 2 Handle the MS_BBE performance event on the port. ----End
Related Information
None.
A.2.87 MSAD_CROSSTR
Description
The MSAD_CROSSTR alarm indicates "multiplex section adaptation performance over threshold". When the board detects AU pointer adaptation performance events over the preset threshold, this alarm is reported.
Attribute
Parameters
A Alarm Reference
Name Parameter 1
l
Impact on System
Bit errors may occur to the services.
Possible Causes
l
AU pointer adaptation performance events exceed the preset threshold.
Handling Procedure
Step 1 View the threshold crossing record of AU pointer adaptation performance events to determine the performance event that exceeds the preset threshold. Step 2 Handle the performance event that exceeds the threshold. ----End
Related Information
None.
A.2.88 MSSW_DIFFERENT
Description
The MSSW_DIFFERENT alarm indicates "master and slave software different alarm". When the SCC board detects the software set 1 and set 2 mismatch, this alarm is reported.
Attribute
Parameters
A Alarm Reference
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the file location.
l l
0x01: Indicates the files in the flash. 0x02: Indicates the software that is currently running.
Parameter 23 Indicates the number of the inconsistent file on the SCC board. Parameter 45 Indicates the alarm cause.
l
0x04: Indicates that the file versions in the active and standby areas of an SCC board are inconsistent. 0x08: Indicates that the file versions on the active and standby SCC boards are inconsistent, or that the files in the corresponding directories of the active and standby SCC boards have different names. 0x0c: Indicates that the file versions in the active and standby areas of an SCC board are inconsistent and the file versions on the active and standby SCC boards are also inconsistent.
Impact on System
If the working software is lost, the backup software cannot take over.
l
If the NE software versions on the active and standby SCC boards are inconsistent, the active/standby switching will be affected. If no NE software exists in the flash, the system will be unable to restart after a power-off or reset.
Possible Causes
Software loading is abnormal.
Handling Procedure
Contact technical engineers of Huawei and re-load the software. ----End
Related Information
None.
A.2.89 MW_FECUNCOR
Description
The MW_FECUNCOR alarm indicates "microwave FEC uncorrectable".
A Alarm Reference
Attribute
Parameters
Parameter 1 Indicates the IF port that reports the alarm. For example, "0x01" indicates the alarm is reported by the first port of the board.
Impact on System
Bit errors occur to the services. If the system is configured with 1+1 FD/SD protection, the channel protection switching can be triggered.
Possible Causes
l l l
The microwave link performance degrades. The transmit unit of the opposite station is faulty. The receive unit of the local station is faulty.
Handling Procedure
Refer to section 2.3 Troubleshooting Microwave Links. ----End
Related Information
None.
A.2.90 MW_LIM
Description
The MW_LIM alarm indicates "microwave link identifier mismatch". When the board detects the LINK ID mismatch in microwave frame overheads, this alarm is reported.
Issue 06 (2007-12-30)
A-109
A Alarm Reference
Attribute
Parameters
Impact on System
The microwave link cannot carry services. If the services are configured with SNCP, the protection switching can be triggered.
Possible Causes
l
The LINK ID to be received by the local station mismatches the LINK ID transmitted by the opposite station. The direction of the antenna is incorrectly configured. As a result, the antenna receives the microwave from other stations.
Handling Procedure
Step 1 Determine the IF port that reports the alarm according to alarm parameters. Step 2 Check if the LINK ID to be received by the local station mismatches the LINK ID transmitted by the opposite station. If ... The LINK ID to be received by the local station mismatches the LINK ID transmitted by the opposite station Then ... Modify the data configuration.
The LINK ID to be received by the local station matches Go to the next step. the LINK ID transmitted by the opposite station Step 3 Adjust the direction of the antenna. ----End
Related Information
None.
A Alarm Reference
A.2.91 MW_LOF
Description
The MW_LOF alarm indicates "loss of Reed Solomon (RS) frame".
Attribute
Parameters
Impact on System
The services are interrupted. If the system is configured with protection, the protection switching can be triggered.
Possible Causes
l l l l l
The microwave link performance degrades. The transmit unit of the opposite station is faulty. The receive unit of the local station is faulty. The working modes of the IF units at the local and the opposite NEs are the same. The working modes of the ODUs at the local and the opposite NEs are the same.
Handling Procedure
Refer to section 2.3 Troubleshooting Microwave Links. ----End
Related Information
None.
A.2.92 MW_RDI
A Alarm Reference
Description
The MW_RDI alarm indicates "microwave link remote defect indication". When the IF board detects the RDI in microwave frame overheads, this alarm is reported.
Attribute
Parameters
Impact on System
If the local station is configured with reverse switching and both the active and standby boards receive the MW_RDI alarm at the same time, the 1+1 switching can be triggered. In addition, this alarm also indicates the receive services of the opposite station are interrupted.
Possible Causes
After detecting a service alarm that is caused by a microwave link fault, the receive station returns a microwave link fault indication to the transmit station.
Handling Procedure
Clear the microwave alarm on the opposite station. ----End
Related Information
None.
A.2.93 NESF_LOST
Description
The NESF_LOST alarm indicates "loss of NE software". When the SCC board detects that the NE software in the flash memory is lost, this alarm is reported.
A Alarm Reference
Attribute
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 Parameter 1 Meaning Indicates an inspection object.
l l l
"0x01" indicates an ordinary file. "0x02" indicates the version of the running software. "0x03" indicates a special inspection object.
Parameter 23 Indicates the ID of the inspection object.

l
"0x01", "0x03", and "0x05" respectively indicate the scc.fpga, nesoft.hwx, and ne.ini in the ofs1. "0x02", "0x04", and "0x06" respectively indicate the scc.fpga, nesoft.hwx, and ne.ini in the ofs2.
Parameter 4
Indicates the alarm cause.

l l l
If the first bit is 1, it means that the file does not exist. If the second bit is 1, it means that verification of the file fails. If the third bit is 1, it means that the version of the file in the active area is different from that of the file in the standby area. If the fourth bit is 2, it means that the version of the file in the active board is different from that of the file in the standby board.
Impact on System
If the NE software does not exist in the working and the protection storage areas, an NE cannot be restarted after it is powered off or reset.
Possible Causes
l l l
No NE software is loaded after already existing ones are erased. Loading the NE software is unsuccessful. The portable flash memory is not in position or is faulty.
Issue 06 (2007-12-30)
A-113
A Alarm Reference
Handling Procedure
Step 1 Check if the alarm is caused by the loading operation. If ... The alarm is caused by the loading operation The alarm is not caused by the loading operation Step 2 Re-install or replace the portable flash memory. ----End Then ... Contact technical engineers of Huawei and reload the NE software. Go to the next step.
Related Information
None.
A.2.94 NESTATE_INSTALL
Description
The NESTATE_INSTALL alarm indicates "NE in install state".
Attribute
Parameters
None.
Impact on System
The NE fails to work.
Possible Causes
l l
The configuration data check fails, which results in the NE in the installation state. The logical cross-connect board is not configured.
Handling Procedure
Step 1 The NE downloads the databases with correct configuration. Step 2 Check whether the logical cross-connect board is configured in the slot layout figure on the NMS.
A Alarm Reference
If ... Not Yes ----End
Then ... Configure the cross-connect board in the slot layout. Go to the next step.
Related Information
None.
A.2.95 NO_BD_SOFT
Description
The NO_BD_SOFT alarm indicates "software file corrupted or missing".
Attribute
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 Parameter 1 Parameter 23 Meaning The value is always 0x01. Indicates the type of the lost software.
l l l
"0x01" indicates board software. "0x02" indicates the active FPGA. "0x03" indicates the standby FPGA.
Impact on System
l l
If the board software is lost, the board fails to work normally. If the FPGA is lost, the FPGA has no backup.
Possible Causes
Software loading is abnormal.
A Alarm Reference
Handling Procedure
Contact technical engineers of Huawei and re-load the software. ----End
Related Information
None.
A.2.96 POWER_ALM
Description
The POWER_ALM alarm indicates "power module alarm".
Attribute
Parameters
Parameter 1 Indicates the number of the power module that reports the alarm. For example, "0x01" indicates the alarm is reported by the first power module of the board. Parameter 2
l l
"0x01" indicates under-voltage. "0x02" indicates over-voltage.
Impact on System
Power modules are configured with protection. If only one power module reports the POWER_ALM alarm, the system cannot be affected.
Possible Causes
l l
The input power is abnormal. The power module is abnormal.
Handling Procedure
Step 1 Use a multimeter to test the power voltage supplied to the chassis.
A Alarm Reference
If ... The voltage exceeds the range of -38.4 V to -72 V The voltage is within the range of -38.4 V to -72 V Step 2 Replace the board that reports the alarm. ----End
Then ... Clear the alarm. Go to the next step.
Related Information
l
For the IDU 610, the power module on the PXC board and that on the SCC board are configured into the 1+1 standby protection group. For the IDU 620, the two power modules on the two PXC boards and that on the SCC board are configured into the 2+1 standby protection group. For the IDU 620, the two power modules on the FAN board are configured into the 1+1 standby protection group.
A.2.97 POWER_FAIL
Description
The POWER_FAIL alarm indicates "power failure". When the ODU detects the ODU power module failure, this alarm is reported.
Attribute
Parameters
Parameter 1 Indicates the number of the power supply that reports the alarm. For example, "0x01" indicates the alarm is reported by the first group power supply of the board. Parameter 2
l l
"0x01" indicates the active power failure. "0x02" indicates the standby power failure. "0x01" indicates over-voltage. "0x02" indicates under-voltage.
Parameter 3
l l
Issue 06 (2007-12-30)
A Alarm Reference
Impact on System
The ODU fails to work normally.
Possible Causes
The ODU is faulty.
Handling Procedure
Replace the ODU that reports the alarm. ----End
Related Information
None.
A.2.98 PS
Description
The PS alarm indicates "protection switch indication".
Attribute
Parameters
Impact on System
The services are interrupted during the protection switching (<50 ms) and return to normal after the switching is complete.
Possible Causes
Protection switching occurs to the services.
A Alarm Reference
Handling Procedure
Related Information
None.
A.2.99 R_F_RST
Description
The R_F_RST alarm indicates "receiving FIFO reset".
Attribute
Parameters
Impact on System
Possible Causes
l l
The board is faulty. The local station clock is asynchronous with the opposite station clock.
Handling Procedure
Step 1 Query if there are TU pointer adjustment performance events at the local station or the opposite station.
A Alarm Reference
If ...
Then ...
There are TU pointer adjustment performance events at Handle the performance events. the local station or the opposite station There are no TU pointer adjustment performance events Go to the next step. at the local station or the opposite station Step 2 Replace the board that reports the alarm. ----End
Related Information
None.
A.2.100 R_LOC
Description
The R_LOC alarm indicates "receive loss of clock". When the line board cannot extract the clock from the line signal, this alarm is reported.
Attribute
Parameters
Impact on System
If the system is configured with protection, the protection switching can be triggered.
Possible Causes
l l
A-120
A Alarm Reference
Handling Procedure
Step 1 Determine the line port that reports the alarm according to alarm parameters. Step 2 Replace the line board of the opposite station. If ... The alarm disappears after the board is replaced The alarm persists after the board is replaced Then ... The fault is cleared and the troubleshooting is complete. Go to the next step.
Related Information
None.
A.2.101 R_LOF
Description
The R_LOF alarm indicates "receive loss of frame". When the OOF state lasts for 3 ms, this alarm is reported.
Attribute
Parameters
A Alarm Reference
Name Parameter 1
Impact on System
Possible Causes
l l l
The transmit unit of the opposite station is faulty. The receive unit of the local station is faulty. The line performance degrades.
Handling Procedure
Step 1 Determine the line port that reports the alarm according to alarm parameters. Step 2 If this alarm is reported by the IF board, check if there is the MW_FECUNCOR alarm. If ... There is the MW_FECUNCOR alarm There is no MW_FECUNCOR alarm Then ... Clear the MW_FECUNCOR alarm first. Go to Step 4.
Step 3 If this alarm is reported by the optical interface board or STM-1 electrical interface board, exchange the receive/transmit fiber jumpers or cables at the receive and the transmit ends. If ... The alarm still persists after the operation The line port of the opposite station reports the R_LOF alarm Step 4 Replace the line board of the opposite station. If ... The alarm disappears after the board is replaced The alarm persists after the board is replaced Then ... The fault is cleared and the troubleshooting is complete. Go to the next step. Then ... Go to the next step. Clear the fault in fibers/cables.
Step 5 Replace the cross-connect and timing board of the opposite station. If ... The alarm disappears after the board is replaced
Then ... The fault is cleared and the troubleshooting is complete.

Issue 06 (2007-12-30)
A Alarm Reference
If ... The alarm persists after the board is replaced Step 6 Replace the board that reports the alarm. ----End
Related Information
None.
A.2.102 R_LOS
Description
The R_LOS alarm indicates "receive loss of signal".
Attribute
Parameters
Impact on System
Possible Causes
l l l
The transmit unit of the opposite station is faulty. The receive unit of the local station is faulty. The line performance degrades.
Issue 06 (2007-12-30)
A Alarm Reference
Handling Procedure
Step 1 Determine the line port that reports the alarm according to alarm parameters. Step 2 If this alarm is reported by the IF board, check if the data configuration at the receive and the transmit ends is consistent. If ... The data configuration is inconsistent The data configuration is consistent Then ... Modify the data configuration. Go to the next step.
Step 3 If this alarm is reported by the IF board, check if there is the MW_FECUNCOR alarm. If ... There is the MW_FECUNCOR alarm There is no MW_FECUNCOR alarm Then ... Clear the MW_FECUNCOR alarm first. Go to Step 5.
Step 4 If this alarm is reported by the optical interface board or STM-1 electrical interface board, exchange the receive/transmit fiber jumpers or cables at the receive and the transmit ends. If ... The alarm still persists after the operation The line port of the opposite station reports the R_LOS alarm Then ... Go to the next step. Clear the fault in fibers/cables.
NOTE
This method only applies to the situation where only one end reports the alarm. If both ends reports the alarm, check if the transmission distance is too long or the cables are broken.
Step 6 Replace the cross-connect and timing board of the opposite station. If ... The alarm disappears after the board is replaced The alarm persists after the board is replaced Step 7 Replace the board that reports the alarm. ----End
A Alarm Reference
Related Information
None.
A.2.103 R_S_ERR
Description
The R_S_ERR alarm indicates "received signal error".
Attribute
Parameters
Impact on System
Possible Causes
l l
Handling Procedure
Step 1 Check if the tributary board supports the type of the input signal. If ... The tributary board does not support the type of the input signal Then ... Modify the type of the output signal of the opposite station.
The tributary board supports the type of the Go to the next step. input signal
A Alarm Reference
Step 2 Test the frequency offset of the input signal. If ... The frequency offset of the input signal is excessive The frequency offset of the input signal meets the requirement Step 3 Replace the board that reports the alarm. ----End Then ... Troubleshoot the opposite station equipment. Go to the next step.
Related Information
None.
A.2.104 RADIO_MUTE
Description
The RADIO_MUTE alarm indicates "radio transmission mute".
Attribute
Alarm Severity Warning Alarm Type 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 Parameter 1 Meaning Indicates the RF port that reports the alarm.
Impact on System
The transmitter does not launch services.
Possible Causes
l l l
The transmitter of the local station is muted. The data configuration of the ODU is incorrect. The IF board is faulty, causing abnormal IF output.
A-126
A Alarm Reference
Handling Procedure
Step 1 Check if the transmitter of the ODU that reports the alarm is muted. If ... The transmitter is muted The transmitter is not muted Then ... Cancel the muting operation. Go to the next step.
Step 2 Check if there is the CONFIG_NOSUPPORT alarm. If ... There is the CONFIG_NOSUPPORT alarm Then ... Clear the CONFIG_NOSUPPORT alarm first.
There is no CONFIG_NOSUPPORT alarm Go to the next step. Step 3 Replace the IF board. ----End
Related Information
None.
A.2.105 RADIO_RSL_HIGH
Description
The RADIO_RSL_HIGH alarm indicates "radio receive signal level too high". When the receive power is detected higher than the upper threshold of the ODU receive power (-20 dBm), this alarm is reported.
Attribute
Alarm Severity Critical Alarm Type Service alarm
Parameters
Issue 06 (2007-12-30)
Meaning Indicates the RF port that reports the alarm.

A Alarm Reference
Impact on System
The service transmission is affected. If the system is configured with 1+1 protection, the protection switching can be triggered.
Possible Causes
l l
The ODU is faulty. There is a strong interference source nearby.
Handling Procedure
Step 1 Replace the ODU. If ... The alarm disappears after the ODU is replaced The alarm persists after the ODU is replaced Then ... The fault is cleared and the troubleshooting is complete. Go to the next step.
Step 2 Remove the nearby strong interference source. ----End
Related Information
None.
A.2.106 RADIO_RSL_LOW
Description
The RADIO_RSL_LOW alarm indicates "radio receive signal level too low". When the receive power is detected below the lower threshold of the ODU receive power (-90 dBm), this alarm is reported.
Attribute
Parameters
A Alarm Reference
Name Parameter 1
Meaning Indicates the RF port that reports the alarm.
Impact on System
If there is neither the MW_LOF nor MW_FECUNCOR alarm, the services cannot be affected.
Possible Causes
l l l
The microwave link signal is too much attenuated. The transmit power of the opposite station is too low. The ODU of the local station is faulty.
Handling Procedure
Step 1 Check if the alarm persists. If ... Then ...
The alarm sometimes occurs Contact the network planning department to change the design to increase the anti-fading performance. The alarm persists Go to the next step.
Step 2 Check if the transmit power of the opposite station is normal. If ... The transmit power is abnormal The transmit power is normal Step 3 Check if the antenna is properly adjusted. If ... The antenna is not properly adjusted The antenna is properly adjusted Then ... Adjust the antenna again. Go to the next step. Then ... Go to the next step. Replace the ODU of the opposite station.
Step 4 Check if the polarization direction of the antenna is correctly set. If ... The polarization direction is wrongly set The polarization direction is correctly set Then ... Correct the polarization direction. Go to the next step.
Step 5 Check if the antenna gain at both the transmit and receive sides meets the indexes. If ... The gain does not meet the indexes The gain meets the indexes
Issue 06 (2007-12-30)
Then ... Replace the antenna. Go to the next step.

A-129
A Alarm Reference
Step 6 Check if there is a mountain or building in the transmit direction. If ... There is a mountain or building in the transmit direction There is no mountain or building in the transmit direction Step 7 Replace the ODU of the local station. ----End Then ... Contact the network planning department to change the design to avoid the mountain or building. Go to the next step.
Related Information
None.
A.2.107 RADIO_TSL_HIGH
Description
The RADIO_TSL_HIGH alarm indicates "radio transmission signal level too high". When the transmit power is detected higher than the upper power threshold of the ODU, this alarm is reported.
Attribute
Parameters
Impact on System
Possible Causes
The ODU is faulty.
A Alarm Reference
Handling Procedure
Replace the ODU. ----End
Related Information
None.
A.2.108 RADIO_TSL_LOW
Description
The RADIO_TSL_LOW alarm indicates "radio transmission signal level too low". When the receive power is detected below the lower power threshold of the ODU, this alarm is reported.
Attribute
Parameters
Impact on System
Possible Causes
The ODU is faulty.
Handling Procedure
Replace the ODU. ----End
Related Information
None.
A Alarm Reference
A.2.109 RELAY_ALARM
Description
The RELAY_ALARM alarm indicates "relay alarm".
Attribute
Alarm Severity Critical Alarm Type Environment alarm
Parameters
Parameter 1 Indicates the number of the input alarm. For example, "0x01" indicates the reported external alarm is the first input alarm.
Impact on System
None.
Possible Causes
The input alarm signal reports the alarm.
Handling Procedure
Step 1 Determine the number of the input alarm according to alarm parameters. Step 2 Clear the fault according to the meaning of the input alarm. ----End
Related Information
None.
A.2.110 RP_LOC
Description
The RP_LOC alarm indicates "loss of receiving phaselock ring clock".
A Alarm Reference
Attribute
Parameters
Impact on System
The services on the board are interrupted.
Possible Causes
Handling Procedure
Replace the board that reports the alarm. ----End
Related Information
None.
A.2.111 RS_CROSSTR
Description
The RS_CROSSTR alarm indicates "regenerator section performance over threshold". When the board detects the regenerator section performance events over the preset threshold, this alarm is reported.
Attribute
Issue 06 (2007-12-30)

A Alarm Reference
Parameters
l
Impact on System
Possible Causes
The regenerator section performance events exceed the preset threshold.
Handling Procedure
Step 1 View the threshold crossing record of regenerator section performance events to determine the performance event that exceeds the preset threshold. Step 2 Handle the performance event that exceeds the threshold. ----End
Related Information
None.
A.2.112 S1_SYN_CHANGE
Description
The S1_SYN_CHANGE alarm indicates "reference source change in S1_Mode".
A-134
Issue 06 (2007-12-30)
A Alarm Reference
Attribute
Parameters
l l
"0x01" indicates switching of the system clock. "0x02" indicates switching of 2M phase-locked source.
Impact on System
This alarm has no impact on the system.
Possible Causes
In the S1 byte mode, switching occurs to the clock source.
Handling Procedure
Related Information
None.
A.2.113 SYN_BAD
Description
The SYN_BAD alarm indicates "synchronous source degraded".
Attribute
Issue 06 (2007-12-30)
Alarm Type Equipment alarm

A Alarm Reference
Parameters
None.
Impact on System
The NE clock is unlocked.
Possible Causes
l l
The synchronous source degraded. The cross-connect unit is faulty.
Handling Procedure
Step 1 If the traced synchronous source is the external clock, check if the type of the external clock configuration is correct. If ... The configuration is incorrect The configuration is correct Then ... Modify the data configuration. Go to the next step.
Step 2 If the traced synchronous source is the external clock, check if the opposite clock source device is faulty. If ... The opposite equipment is faulty The opposite equipment is not faulty Then ... Clear the fault. Go to the next step.
Step 3 If the traced synchronous source is the external clock, check if the external clock cable is normal. If ... The cables are abnormal The cables are normal Then ... Replace the cables. Perform step 5.
Step 4 If the traced synchronous source is the line clock, replace the cross-connect and timing board of the upstream NE. Step 5 Replace the board that reports the alarm. ----End
Related Information
None.
A.2.114 SYNC_C_LOS
A Alarm Reference
Description
The SYNC_C_LOS alarm indicates "synchronous source level loss".
Attribute
Alarm Severity Warning Alarm Type Equipment alarm
Parameters
l
Parameter Every two parameters indicates one lost clock source. If the line clock source is lost, the first parameter indicates the slot number of the clock source, and the second parameter indicates the port number of the clock source. If the external clock source is lost, 0xf0, "1" indicates the external clock 1, 0xf0, "2" indicates the external clock 2.
Impact on System
The NE clock degrades or enters the free-run mode.
Possible Causes
The clock source is lost.
Handling Procedure
Step 1 Determine the lost clock source according to alarm parameters. Step 2 Find out why the clock source is lost and clear the fault. ----End
Related Information
None.
A.2.115 T_ALOS
Description
The T_ALOS alarm indicates "E1 interface loss of analog signal".
A Alarm Reference
Attribute
Parameters
Impact on System
Possible Causes
l l l l
The port does not access the 2 Mbit/s service. The opposite equipment is faulty. The trunk cable is faulty. The board that reports the alarm is faulty.
Handling Procedure
Step 1 Check if the port that reports the alarm accesses the 2 Mbit/s service. If ... The port does not access the 2 Mbit/s service The port accesses the 2 Mbit/s service Step 2 Check if the opposite equipment is faulty. If ... The opposite equipment is faulty The opposite equipment is not faulty Step 3 Check if the trunk cable is faulty.
Then ... Access the service to the port or delete the unwanted service configuration. Go to the next step.
Then ... Clear the fault. Go to the next step.
A Alarm Reference
If ... The opposite equipment is faulty The opposite equipment is not faulty Step 4 Replace the board that reports the alarm. ----End
Then ... Clear the fault. Go to the next step.
Related Information
None.
A.2.116 T_F_RST
Description
The T_F_RST alarm indicates "transmission FIFO reset".
Attribute
Parameters
Impact on System
The services on the PDH channel are interrupted.
Possible Causes
l l
Issue 06 (2007-12-30)
A Alarm Reference
Handling Procedure
Related Information
None.
A.2.117 T_FIFO_E
Description
The T_FIFO_E alarm indicates "transmission FIFO overflow".
Attribute
Parameters
Impact on System
Possible Causes
l l
A-140
A Alarm Reference
Handling Procedure
Related Information
None.
A.2.118 T_LOC
Description
The T_LOC alarm indicates "transmit loss of clock".
Attribute
Parameters
Impact on System
The services on the AU-4 path are interrupted.
A Alarm Reference
Possible Causes
l l
The cross-connect and timing board is faulty. The line board is faulty.
Handling Procedure
Step 1 Determine the AU-4 path that reports the alarm according to alarm parameters. Step 2 Replace the cross-connect and timing board. If ... The alarm disappears after the board is replaced The alarm persists after the board is replaced Step 3 Replace the board that reports the alarm. ----End Then ... The fault is cleared and the troubleshooting is complete. Go to the next step.
Related Information
None.
A.2.119 T_LOS
Description
The T_LOS alarm indicates "transmit loss of signal".
Attribute
Parameters
A-142
A Alarm Reference
Name
Meaning
Impact on System
The services on the AU-4 path are interrupted.
Possible Causes
l l l
The SDH service configuration mismatches the type of the line board. The cross-connect and timing board is faulty. The line board is faulty.
Handling Procedure
Step 1 Check the SDH service configuration. If ... The SDH service configuration mismatches the type of the line board The SDH service configuration is correct Step 2 Replace the cross-connect and timing board. If ... The alarm disappears after the board is replaced The alarm persists after the board is replaced Step 3 Replace the board that reports the alarm. ----End Then ... The fault is cleared and the troubleshooting is complete. Go to the next step. Then ... The fault is cleared and the troubleshooting is complete. Go to the next step.
Related Information
None.
A.2.120 TEMP_ALARM
Description
The TEMP_ALARM alarm indicates "temperature over threshold".
A Alarm Reference
Attribute
Alarm Severity Minor Alarm Type Environment alarm
Parameters
l l
"0x01" indicates temperature over the upper threshold. "0x02" indicates temperature below the lower threshold.
Impact on System
The board cannot work normally.
Possible Causes
The board temperature exceeds the threshold.
l l
The board temperature exceeds the threshold. The temperature detecting circuit is faulty.
Handling Procedure
Step 1 If the alarm is reported by the ODU, install a sunshade to control the temperature. Step 2 If the alarm is reported by a board of the IDU, check if the temperature control devices, such as air-conditioners, operate normally. If ... The temperature control devices operate abnormally The temperature control devices operate normally Then ... Adjust the temperature control devices. Go to the next step.
Step 3 If the alarm is reported by a board of the IDU and the IDU has air filters, clean the air filters. Step 4 If the ambient temperature is normal and there is no heat-sinking problem, replace the board that reports the alarm. ----End
A Alarm Reference
Related Information
None.
A.2.121 TU_AIS
Description
The TU_AIS alarm indicates "TU alarm indication". When the board detects the TU path with all "1" signals, this alarm is reported.
Attribute
Parameters
Impact on System
The services on the TU path are interrupted. If the services are configured with protection, the protection switching can be triggered.
Possible Causes
l l l l
The data configuration is wrong. The line is faulty. The cross-connect and timing board is faulty. The tributary board is faulty.
Handling Procedure
Step 1 Check if the SDH service data and the network protection data are correct. If ... The data are incorrect
Issue 06 (2007-12-30)
Then ... Modify the data configuration.

A Alarm Reference
If ... The data are correct
Step 2 Check if there are line alarms on the service route. If ... There are line alarms There are no line alarms Then ... Modify the data configuration. Go to the next step.
Step 3 Locate the faulty station using the loopback method. If ... The fault lies in a remote station The fault lies in the local station Step 4 Replace the line board of the local station. If ... The alarm disappears after the board is replaced The alarm persists after the board is replaced Step 5 Replace the cross-connect and timing board. If ... The alarm disappears after the board is replaced The alarm persists after the board is replaced Step 6 Replace the board that reports the alarm. ----End Then ... The fault is cleared and the troubleshooting is complete. Go to the next step. Then ... The fault is cleared and the troubleshooting is complete. Go to the next step. Then ... Locate the faulty board by replacing boards. Go to the next step.
Related Information
None.
A.2.122 TU_AIS_VC12
Description
The TU_AIS_VC12 is an indication alarm of a VC-12 TU alarm. If a board detects that the TU pointer is 1, this board reports the TU_AIS_VC12 alarm.
A Alarm Reference
Attribute
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 Parameter 1 Meaning The value is always 1.
Impact on System
The services on this VC-12 TU path are interrupted. If the services are configured with a protection, a switching is triggered.
Possible Causes
l l l l
The data configuration is incorrect. The link is faulty. The cross-connect and timing board is faulty. A tributary board is faulty.
Handling Procedure
Step 1 Check whether the SDH service data and the network protection data are correct. If ... Not Yes Then ... Correct the configuration. Go to the next step.
Step 2 Check whether any line alarm exists in the service trail. If ... Yes Not Then ... Handle the alarms. Go to the next step.
Step 3 Perform a loopback to locate the faulty point.

A Alarm Reference
If ... The fault exists on another NE The fault exists on the local NE Step 4 Replace the line board at the local NE. If ...
Then ... Replace boards to locate the faulty board. Go to the next step.
Then ... The fault is removed. End the alarm handling. Go to the next step.
The TU_AIS_VC12 alarm clears after the board is replaced The TU_AIS_VC12 alarm persists after the board is replaced
Step 5 Replace the cross-connect and timing board at the local NE. If ... The TU_AIS_VC12 alarm clears after the board is replaced The TU_AIS_VC12 alarm persists after the board is replaced Then ... The fault is removed. End the alarm handling. Go to the next step.
Step 6 Replace the board that reports the TU_AIS_VC12 alarm. ----End
Related Information
None.
A.2.123 TU_AIS_VC3
Description
The TU_AIS_VC3 is an indication alarm of VC-3 TU alarm. If a board detects that the TU pointer is 1, this board reports the TU_AIS_VC3 alarm.
Attribute
Parameters
A Alarm Reference
Name Parameter 1
Impact on System
The services on this VC-3 TU path are interrupted. If the services are configured with a protection, a switching is triggered.
Possible Causes
l l l l
The data configuration is incorrect. The link is faulty. The cross-connect and timing board is faulty. A tributary board is faulty.
Handling Procedure
Step 1 Check whether the SDH service data and the network protection data are correct. If ... Not Yes Then ... Correct the configuration. Go to the next step.
Step 2 Check whether any line alarm exists in the service trail. If ... Yes Not Then ... Handle the alarms. Go to the next step.
Step 3 Perform a loopback to locate the faulty point. If ... The fault exists on another NE The fault exists on the local NE Step 4 Replace the line board at the local NE. If ... The TU_AIS_VC3 alarm is cleared after the board is replaced The TU_AIS_VC3 alarm persists after the board is replaced Then ... The fault is removed. End the alarm handling. Go to the next step. Then ... Replace boards to locate the faulty board. Go to the next step.
Step 5 Replace the cross-connect and timing board at the local NE.
A Alarm Reference
If ... The TU_AIS_VC3 alarm is cleared after the board is replaced The TU_AIS_VC3 alarm persists after the board is replaced
Then ... The fault is removed. End the alarm handling. Go to the next step.
Step 6 Replace the board that reports the TU_AIS_VC3 alarm. ----End
Related Information
None.
A.2.124 TU_LOP
Description
The TU_LOP alarm indicates "TU loss of pointer". When the board detects the TU-PTR value of eight consecutive frames is invalid or is NDF revertive, this alarm is reported.
Attribute
Parameters
Impact on System
The services on the TU channel are interrupted. If the services are configured with protection, the protection switching can be triggered.
Possible Causes
l
The cross-connect and timing board is faulty.

A-150

l
A Alarm Reference
The tributary board is faulty.
Handling Procedure
Step 1 Replace the cross-connect and timing board. If ... The alarm disappears after the board is replaced The alarm persists after the board is replaced Step 2 Replace the board that reports the alarm. ----End Then ... The fault is cleared and the troubleshooting is complete. Go to the next step.
Related Information
None.
A.2.125 TU_LOP_VC12
Description
The TU_LOP alarm indicates that the VC-12 TU pointer is lost. If a board detects that the VC-12 TU-PTR value of eight consecutive frames is invalid or is NDF revertive, this board reports the TU_LOP_VC12 alarm.
Attribute
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 Parameter 1 Meaning The value is always 1.
Issue 06 (2007-12-30)
A-151
A Alarm Reference
Impact on System
The services in the TU path are interrupted. If the services are configured with a protection, a switching is triggered.
Possible Causes
l l
The cross-connect and timing board is faulty. A tributary board is faulty.
Handling Procedure
Step 1 Replace the cross-connect and timing board at the local NE. If ... Then ...
The TU_LOP_VC12 alarm is cleared after the The fault is removed. End the alarm board is replaced handling. The TU_LOP_VC12 alarm persists after the board is replaced Go to the next step.
Step 2 Replace the board that reports the TU_LOP_VC12 alarm. ----End
Related Information
None.
A.2.126 TU_LOP_VC3
Description
The TU_LOP alarm indicates that the VC-3 TU pointer is lost. If a board detects that the TUPTR value of eight consecutive frames is invalid or is NDF revertive, this board reports the TU_LOP_VC3 alarm.
Attribute
Parameters
A Alarm Reference
Name Parameter 1
Impact on System
The services in the TU path are interrupted. If the services are configured with a protection, a switching is triggered.
Possible Causes
l l
The cross-connect and timing board is faulty. A tributary board is faulty.
Handling Procedure
Step 1 Replace the cross-connect and timing board at the local NE. If ... Then ...
The TU_LOP_VC3 alarm is cleared after the The fault is removed. End the alarm board is replaced handling. The TU_LOP_VC3 alarm persists after the board is replaced Go to the next step.
Step 2 Replace the board that reports the TU_LOP_VC3 alarm. ----End
Related Information
None.
A.2.127 UP_E1_AIS
Description
The UP_E1_AIS alarm indicates "2M up signal alarm indication". When the tributary board detects the up E1 signal is all "1"s, this alarm is reported.
Attribute
Parameters
A Alarm Reference
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 Parameter 1 Meaning The value is always 0x01.
Impact on System
The E1 signals are unavailable.
Possible Causes
l l
The opposite equipment sends the E1_AIS signal. The receive unit of the tributary board of the local station is faulty.
Handling Procedure
Step 1 Check if the opposite equipment sends the E1_AIS signal. If ... The opposite equipment sends the E1_AIS signal Then ... Troubleshoot the opposite equipment.
The opposite equipment does not send the E1_AIS Go to the next step. signal Step 2 Replace the board that reports the alarm. ----End
Related Information
None.
A.2.128 VCAT_LOA
Description
The VCAT_LOA alarm indicates that the delay of the virtual concatenation is overly long. When a board detects that the delay time of the timeslots bound to a VCTRUNK exceeds the time allowed by the virtual concatenation delay, this board reports the VCAT_LOA alarm.
Attribute

Issue 06 (2007-12-30)
A Alarm Reference
Parameters
Impact on System
The virtually concatenated services are interrupted.
Possible Causes
The differences between each VC link are too large.
Handling Procedure
Step 1 Check whether the transmission routes for the paths that are bound to this VCTRUNK are the same. If ... The paths have different transmission routes. The paths have the same transmission route with each other Then ... Adjust the routes to be the same. Go to the next step.
Step 2 Check whether any bit errors or line alarm exists. If yes, handle the alarms. ----End
Related Information
None.
A.2.129 VCAT_LOM_VC12
Description
The VCAT_LOM_VC12 is an alarm indicating the loss of the virtual concatenation multiframe in the VC-12 path. When a board detects that the K4 byte of the VC-12 timeslot mismatches with the expected multiframe sequence, this board reports the VCAT_LOM_VC12 alarm.
Issue 06 (2007-12-30)
A-155
A Alarm Reference
Attribute
Parameters
Impact on System
This path is unavailable. If the LCAS function is disabled, the services are interrupted.
Possible Causes
l l l
The link configuration is incorrect. The virtual concatenation delay time varies with each path. Bit errors exist in the line.
Handling Procedure
Step 1 Check whether the VCTRUNKs at both ends of this path are bound with the same timeslot. If ... Not Yes Then ... Correct the configuration. Go to the next step.
Step 2 Check whether the transmission routes for the paths that are bound to this VCTRUNK are the same. If ... Not Yes Then ... Adjust the routes to be the same. Go to the next step.
A Alarm Reference
Related Information
None.
A.2.130 VCAT_LOM_VC3
Description
The VCAT_LOM_VC3 is an alarm indicating the loss of the virtual concatenation multiframe in the VC-3 path. When a board detects that the H4 byte of the VC-3 timeslot mismatches with the expected multiframe sequence, this board reports the VCAT_LOM_VC3 alarm.
Attribute
Parameters
Impact on System
Possible Causes
l l
The link configuration is incorrect. The virtual concatenation delay is overly long.
Handling Procedure
Step 1 Check whether the VCTRUNKs at both ends of this path are bound with the same timeslot. If ... Not Yes
Issue 06 (2007-12-30)
Then ... Correct the configuration. Go to the next step.

A Alarm Reference
Step 2 Check whether the transmission routes for the paths that are bound to this VCTRUNK are the same. If ... Not Yes Then ... Adjust the routes to be the same. Go to the next step.
Related Information
None.
A.2.131 VCAT_SQM_VC12
Description
The VCAT_SQM_VC12 alarm indicates the sequence (SQ) mismatch of the virtual concatenation in the VC-12 path. When a board detects that the SQ number of the virtual concatenation mismatches, this board reports the VCAT_SQM_VC12 alarm.
Attribute
Parameters
Impact on System
Possible Causes
l
Errors exist on a link or the link is faulty.

A-158

l
A Alarm Reference
The SQ number sent from the opposite NE is wrong.
Handling Procedure
Step 1 Check whether bit errors or a line alarm exists. If ... Bit errors or a line alarm exists No bit errors or line alarm exists Then ... Handle the relevant alarms. Go to the next step.
Step 2 Replace the board on which the VCAT_SQM_VC12 alarm occurs. If ... Then ...
The VCAT_SQM_VC12 alarm clears after the board is replaced End the alarm handling. The VCAT_SQM_VC12 alarm persists after the board is replaced Step 3 Replace the corresponding board at the opposite NE. If ... The VCAT_SQM_VC12 alarm clears after the board is replaced The VCAT_SQM_VC12 alarm clears after the board is replaced ----End Then ... End the alarm handling. Contact Huawei engineers. Go to the next step.
Related Information
None.
A.2.132 VCAT_SQM_VC3
Description
The VCAT_SQM_VC3 alarm indicates the sequence (SQ) mismatch of the virtual concatenation in the VC-3 path. When a board detects that the SQ number of the virtual concatenation mismatches, this board reports the VCAT_SQM_VC3 alarm.
Attribute
Parameters
A Alarm Reference
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 Parameter 1 Meaning The value is always 0x01.
Impact on System
Possible Causes
l l
Bit errors exist on a link or the link is faulty. The SQ number sent from the opposite NE is wrong.
Handling Procedure
Step 1 Check whether bit errors or a line alarm exists. If ... Bit errors or a line alarm exists No bit errors or line alarm exists Then ... Handle the relevant alarms. Go to the next step.
Step 2 Replace the board on which the VCAT_SQM_VC3 alarm occurs. If ... Then ...
The VCAT_SQM_VC3 alarm clears after the board is replaced End the alarm handling. The VCAT_SQM_VC3 persists after the board is replaced Step 3 Replace the corresponding board at the opposite NE. If ... The VCAT_SQM_VC3 alarm clears after the board is replaced The VCAT_SQM_VC3 alarm persists after the board is replaced ----End Then ... End the alarm handling. Contact Huawei engineers. Go to the next step.
Related Information
None.
A.2.133 VOLT_LOS
A Alarm Reference
Description
The VOLT_LOS alarm indicates "loss of voltage".
Attribute
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 Parameter 1 Meaning Indicates the type of the power that reports the alarm.
l l l l l
"0x01" indicates -48 V/+24 V output alarm. "0x02" indicates -48 V/+24 V input alarm. "0x03" indicates +5 V output alarm. "0x04" indicates +3.3 V output alarm. "0x05" indicates the lightning alarm.
Impact on System
As the PXC power is faulty, the system cannot work.
Possible Causes
l l l
The input power is abnormal. The power module is normal. The power switch is not turned on.
Handling Procedure
Step 1 Start different alarm clearing procedures according to the type of the board that reports the alarm. If ... The board is an IF board The board is a PXC board Step 2 Check the power switch of the ODU.
Then ... Carry out Step 2. Carry out Step 3 to Step 5.
A Alarm Reference
If ... The power switch is turned on The power switch is not turned on
Then ... Replace the IF board. Turn on the power switch.
Step 3 Clear the alarm according to the type of the power supply that reports the alarm. If ... The alarm is reported by the input power The alarm is reported by the output power The alarm is a lightning alarm Step 4 Clear the alarm reported by the input power. If ... It is normal that there is no input power It is abnormal that there is no input power Step 5 Check the power switch. If ... The power switch is turned on Then ... Contact power engineers to handle the fault of the input power. Then ... Shield the alarm for the board. Go to the next step. Then ... Go to the next step. Replace the board that reports the alarm. Check the grounding system.
The power switch is not turned on Turn on the power switch. ----End
Related Information
None.
A.2.134 WRG_BD_TYPE
Description
The WRG_BD_TYPE alarm indicates "wrong board type".
Attribute
Parameters
A Alarm Reference
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the slot where the board whose type is wrong is seated.
Impact on System
The board is unavailable.
Possible Causes
l l
The data configuration is wrong. The type of the board installed is incorrect.
Handling Procedure
Step 1 Check if the board type configured complies with the planning. If ... The board type configured does not comply with the planning The board type configured complies with the planning Step 2 Replace the board. ----End Then ... Modify the data configuration. Go to the next step.
Related Information
None.
A.2.135 WRG_DEV_TYPE
Description
The WRG_DEV_TYPE alarm indicates "wrong device type".
Attribute
Parameters
None.
A Alarm Reference
Impact on System
The equipment is unavailable.
Possible Causes
The data configuration is incorrect.
Handling Procedure
Modify the type of the equipment to be consistent with the equipment. ----End
Related Information
None.
A.2.136 WS_LOS
Description
The WS_LOS alarm indicates "wayside interface loss of signal".
Attribute
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 Parameter 1 Meaning Indicates the wayside service where the alarm occurs.
Impact on System
The wayside services are interrupted.
Possible Causes
l l l
Wayside service data has been configured, but the services are not accessed. The opposite equipment is faulty. The wayside cables are faulty.
A-164

l
A Alarm Reference
The PXC board is faulty.
Handling Procedure
Step 1 Check if wayside service data is configured but the services are not accessed. If ... Then ...
Wayside service data is configured but the Access the services and delete unnecessary services are not accessed wayside service data. There is no above situation Go to the next step.
Step 2 Check if the opposite wayside service equipment is faulty. If ... The opposite equipment is faulty The opposite equipment is not faulty Step 3 Check if the wayside service cable is faulty. If ... The opposite equipment is faulty The opposite equipment is not faulty Step 4 Replace the board that reports the alarm. ----End Then ... Clear the fault. Go to the next step. Then ... Clear the fault. Go to the next step.
Related Information
None.
A.2.137 XCP_INDI
Description
The XCP_INDI alarm indicates "XCS protection switching indication".
Attribute
Parameters
A Alarm Reference
Name Parameter 1
Meaning Indicates the slot where the working board is seated.
Impact on System
During the protection switching (< 50 ms), VC-3/VC-12 services are interrupted.
Possible Causes
Protection switching occurs to the PXC board.
Handling Procedure
Related Information
None.
A-166
Issue 06 (2007-12-30)
B Performance Event Reference
Performance Event Reference
B.1 Performance Event List

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

SDH performance events are classified into five categories: pointer justification, regenerator section error, multiplex section error, higher order path error and lower order path error. Table B-1 Pointer justification performance event list Event Name AUPJCHIGH AUPJCLOW AUPJCNEW TUPJCHIGH TUPJCLOW TUPJCNEW Description Count of positive AU pointer justification Count of negative AU pointer justification Count of new AU pointer justifications Count of positive TU pointer justifications Count of negative TU pointer justifications Count of new TU pointer justifications PO1 and PH1 Source SL1, SD1, SLE, SDE, IF1A, and IF1B
Table B-2 Regenerator section error performance event list Event Name RSBBE RSES RSSES Description Regenerator section block of background error Regenerator section errored second Regenerator section severely errored second Source SL1, SD1, SLE, SDE, IF1A, and IF1B
Issue 06 (2007-12-30)
B-1
Event Name RSUAS RSCSES RSOFS RSOOF
Description Regenerator section unavailable second Regenerator section consecutive severely errored second Regenerator section out-of-frame second Regenerator section out of frame
Source
Table B-3 Multiplex section error performance event list Event Name MSBBE MSES MSSES MSCSES MSUAS MSFEBBE MSFEES MSFESES MSFECSES MSFEUAS Description Multiplex section block of background error Multiplex section errored second Multiplex section severely errored second Multiplex section consecutive severely errored second Multiplex section unavailable second Multiplex section far end block of background error Multiplex section far end errored second Multiplex section far end severely errored second Multiplex section far end consecutive severely errored second Multiplex section far end unavailable second Source SL1, SD1, SLE, SDE, IF1A, and IF1B
Table B-4 Higher order path error performance event list Event Name HPBBE HPES HPSES HPCSES HPUAS HPFEBBE HPFEES HPFESES
B-2
Description Higher order path block of background error Higher order path errored second Higher order path severely errored second Higher order path consecutive severely errored second Higher order path unavailable second Higher order path far end block of background error Higher order path far end errored second Higher order path far end severely errored second
Source SL1, SD1, SLE, SDE, IF1A, and IF1B
Issue 06 (2007-12-30)
Event Name HPFECSES HPFEUAS
Description Higher order path far end consecutive severely errored second Higher order path far end unavailable second
Source
Table B-5 VC-3 path bit error performance event list Event Name VC3BBE VC3ES VC3SES VC3CSES VC3UAS VC3FEBBE VC3FEES VC3FESES VC3FECSES VC3FEUAS Description VC-3 background block error VC-3 errored second VC-3 severely errored second VC-3 consecutive severely errored second VC-3 unavailable second VC-3 far end block of the background error VC-3 far end errored second VC-3 far end severely errored second VC-3 far end consecutive severely errored second VC-3 far end unavailable second Source EFT4
Table B-6 Lower order path error performance event list Event Name LPBBE LPES LPSES LPCSES LPUAS LPFEBBE LPFEES Description Lower order path block of background error Lower order path errored second Lower order path severely errored second Lower order path consecutive severely errored second Lower order path unavailable second Lower order path far end block of background error Lower order path far end errored second Source PO1, PH1, and EFT4
Issue 06 (2007-12-30)
B-3
Event Name LPFESES LPFECSES LPFEUAS
Description Lower order far end severely errored second Lower order path far end consecutive severely errored second Lower order far end unavailable second
Source
B.1.2 Microwave Performance Event List

The microwave performance events contain events of the microwave power and the FEC. Table B-7 Microwave power performance event list Event Name TSL_MAX TSL_MIN TSL_CUR RSL_MAX RSL_MIN RSL_CUR Description Maximum value of microwave transmit signal level Minimum value of microwave transmit signal level Current value of microwave transmit signal level Maximum value of microwave receive signal level Minimum value of microwave receive signal level Current value of microwave receive signal level Source ODU
Table B-8 FEC performance event Event Name FEC_BEF_COR_ER FEC_COR_BYTE_CNT Description Bit error rate before FEC correction FEC corrected byte count Source IF1A and IF1B
B.1.3 Other Performance Event List

Besides the SDH and microwave performance events, the OptiX RTN 600 also supports performance events of the optical power and the board temperature. Table B-9 Optical power performance event list Event Name TPLMAX TPLMIN
B-4
Description Maximum value of transmit optical power Minimum value of transmit optical power
Source SD1 and SL1
Issue 06 (2007-12-30)
Event Name TPLCUR RPLMAX RPLMIN RPLCUR
Description Current value of receive optical power Maximum value of received optical power Minimum value of received optical power Current value of received optical power
Source
Table B-10 Board temperature performance event list Event Name BDTMPMAX BDTMPMIN BDTMPCUR Description Maximum board temperature Minimum board temperature Current board temperature Source IF1A, IF1B, PXC, EFT4, ODU, and SCC
B.2 Performance Events and Corrective Procedures

Based on the event type, this part describes all the performance events of the OptiX RTN 600 and the corrective procedures in details.
B.2.1 AUPJCHIGH, AUPJCLOW and AUPJCNEW

Performance Event Meaning
l l l
AUPJCHIGH stands for "Count of positive AU pointer justifications". AUPJCLOW stands for "Count of negative AU pointer justifications". AUPJCNEW stands for "Count of new AU pointer justifications".
Performance Event Attribute

Performance Event Attribute Performance event cell Description PPJE(AUPJCHIGH) NPJE(AUPJCLOW) NDF(AUPJCNEW) Unit Block
Impact on the System

Less than six AUPJCHIGH and AUPJCLOW events do not impact the system. If the pointer is justified for more than six times, or if even the AUPJCNEW occurs, bit errors might exist in the service.
Issue 06 (2007-12-30) Huawei Technologies Proprietary B-5
Relevant Alarms
When the AUPJCHIGH, AUPJCLOW and AUPJCNEW cross the preset threshold, the MSAD_CROSSTR alarm might occur.
Probable Causes
The NE clock is not synchronized.
Procedure
Refer to section 2.5 Troubleshooting Pointer Justifications. ----End
B.2.2 TUPJCHIGH, TUPJCLOW and TUPJCNEW

l l l
TUPJCHIGH stands for "Count of positive TU pointer justifications". TUPJCLOW stands for "Count of negative TU pointer justifications". TUPJCNEW stands for "Count of new TU pointer justifications".

Performance Event Attribute Performance event cell Description TUPPJE(TUPJCHIGH) TUNPJE(TUPJCLOW) TUNDF(TUPJCNEW) Unit Block

Less than six TUPJCHIGH and TUPJCLOW do not impact the system. If the pointer is justified for more than six times, or if even the TUPJCNEW exists, bit errors might exist in the service.
Relevant Alarm
When the TUPJCHIGH, TUPJCLOW and TUPJCNEW cross the preset threshold, the HPAD_CROSSTR alarm occurs.
Probable Causes
The NE clock is not synchronized.
B-6
Issue 06 (2007-12-30)
Procedure
Refer to section 2.5 Troubleshooting Pointer Justifications. ----End
B.2.3 RSBBE, RSES, RSSES, RSCSES and RSUAS

l
RSBBE stands for "regenerator section background block error". The BBES are the errored blocks excluding those in the unavailable and severely errored seconds.
RSES stands for "regenerator section errored second". The ES is the second with one or more errored blocks. RSSES stands for "regenerator section severely errored second". The SES is the second in which more than 30% errored blocks or at least one severely disturbed period (SDP) exists. The SDP is the period during which the BER of all the consecutive blocks in a period of less than four consecutive blocks or 1ms (the longer period is applied) is equal to or higher than 102 or the signal is lost.
RSCSES stands for "regenerator section consecutive severely errored second". The CSES is the second in which the SES occurs in a consecutive mode and lasts for less than 10 seconds.
RSUAS stands for "regenerator section unavailable second". The UAS is a period of unavailable time that begins at the onset of ten CSESs. When SESs disappear for ten consecutive seconds, the available time begins from the eleventh second, with the previous ten seconds included.
NOTE
When the intermediate board works in the PDH mode, the performance events might also be reported. These events are detected through the self-defining overhead byte B1 of the PDH microwave frame.

Performance Event Attribute Performance event cell Unit Description B1CNT Block (RSBBE) Second(RSES, RSSES, RSCSES and RSUAS)

Too many bit errors can interrupt the service (the bit error rate needs to be less than 103 for the voice service, and 106 for the data service).
Relevant Alarm
When the RSBBE, RSES, RSSES, RSCSES and RSUAS events cross the preset threshold, the RS_CROSSTR alarm can occur.
Probable Causes
The system detects the RSBBE by the B1 byte.
Procedure
B.2.4 RSOOF and RSOFS

l
RSOOF stands for "Regenerator section out of frame". The OOF block is the data block in which incorrect A1 and A2 bytes are detected. RSOFS stands for "regenerator section out-of-frame second". The OFS second is a second in which one or more OOF blocks are detected.

Performance Event Attribute Performance event cell Unit Description OOF Block (RSOOF) Second (RSOFS)

The system discards OOF data blocks. Thus, an RSOOF event is like a big error (one RSOOF exists in a second, and the BER is not less than 1.25 x 105).
Relevant Alarms
If RSOOF is received in five consecutive frames, the equipment will enter the OOF state. If the OOF state lasts for 3 ms, the equipment will report the R_LOF alarm. As a result, all the services are interrupted.
Probable Causes
The system detects that the A1 and A2 bytes are incorrect.
B-8 Huawei Technologies Proprietary Issue 06 (2007-12-30)
Procedure
If the R_LOF alarms are reported at the same time, process the errors according to the alarms. Otherwise, refer to section 2.4 Troubleshooting Bit Errors . ----End
B.2.5 MSBBE, MSES, MSSES, MSCSES and MSUAS

l
MSBBE stands for "multiplex section background block error". The BBE is the errored blocks excluding those in the unavailable and severely errored seconds.
MSES stands for "multiplex section errored second". The ES is the second with one or more errored blocks. MSSES stands for "multiplex section severely errored second". The SES is the second in which more than 30% errored blocks or at least one severely disturbed period (SDP) exists. The SDP is the period during which the BER of all the consecutive blocks in a period of less than four consecutive blocks or 1ms (the longer period is applied) is equal to or higher than 102 or the signal is lost.
MSCSES stands for "multiplex section consecutive severely errored second". The CSES is the second in which the SESs occur in a consecutive mode and lasts for less than 10 seconds.
MSUAS stands for "multiplex section unavailable second". The UAS is a period of unavailable time that begins at the onset of ten CSESs. When SESs disappear for ten consecutive seconds, the available time begins from the eleventh second, with the previous ten seconds included.

Performance Event Attribute Performance event cell Unit Description B2CNT Block (MSBBE) Second(MSES, MSSES, MSCSES and MSUAS)

Relevant Alarm
When the MSBBE, MSES, MSSES, MSCSES and MSUAS cross the preset threshold, the MS_CROSSTR alarm can occur.
Probable Causes
The system detects the MSBBE by the B2 byte.
Procedure
B.2.6 MSFEBBE, MSFEES, MSFESES, MSFECSES and MSFEUAS

l
MSFEBBE stands for "multiplex section far end background block error". The FEBBE (far end background block error) indicates that the BBE occurs at the opposite end.
MSFEES stands for "multiplex section far end errored second". The FEES ( far end errored second) indicates that the ES occurs at the opposite end. MSFESES stands for "multiplex section far end severely errored second". The FESES (far end severely errored second) indicates that the SES occurs at the opposite end.
MSFECSES stands for "Multiplex section far end consecutive severely errored second". The FESES (far end consecutive severely errored second) indicates that the CSES occurs at the opposite end.
MSFEUAS stands for "multiplex section unavailable second". The FEUAS (far end unavailable second) indicates that the UAS occurs at the opposite end.

Performance Event Attribute Performance event cell Unit Description LFEBE Block (MSFEBBE) Second(MSFEES, MSFESES, MSFECSES and MSFEUAS)

Relevant Alarm
The MS_REI alarm occurs at the local end.
Probable Causes
The system detects the MSFEBBE by the M1 byte.
Procedure
Clear the corresponding event at the opposite end. ----End
B.2.7 HPBBE, HPES, HPSES, HPCSES and HPUAS

l
HPBBE stand for "Higher order path block of background error". BBE (background block error) the errored blocks excluding those in the unavailable and severely errored seconds.
HPES stands for "higher order path errored second". The ES (errored second) the second with one or more errored blocks. HPSES stands for "higher order path severely errored second". The SES is the second in which more than 30% errored blocks or at least one severely disturbed period (SDP) exists. The SDP is the period during which the BER of all the consecutive blocks in a period of less than four consecutive blocks or 1ms (the longer period is applied) is equal to or higher than 102 or the signal is lost.
HPCSES stands for "higher order path consecutive severely errored second". The CSES (consecutive severely errored second) is the second in which the SESs occur in a consecutive mode and lasts for less than 10 seconds.
HPUAS stands for "higher order path unavailable second". The UAS (unavailable second) is a period of unavailable time that begins at the onset of ten CSESs. When SESs disappear for ten consecutive seconds, the available time begins from the eleventh second, with the previous ten seconds included.

Performance Event Attribute Performance event cell Unit Description B3CNT Block (HPBBE) Second(HPES, HPSES, HPCSES and HPUAS)

Relevant Alarms
When the HPBBE, HPES, HPSES, HPCSES and HPUAS events cross the preset threshold, the HP_CROSSTR alarm can occur.
Probable Causes
The system detects higher order path bit errors by the B3 byte.
Procedure
B.2.8 HPFEBBE, HPFEES, HPFESES, HPFECSES and HPFEUAS

l
HPFEBBE stands for "higher order path far end background block error". The far end background block error (FEBBE) refers to the error detected at the remote end. HPFEES stands for "higher order path far end errored second". The far end errored second (FEES) refers to the ES detected at the remote end. HPFESES stands for "higher order path far end severely errored second". The far end severely errored second (FESES) refers to the SES detected at the remote end. HPFECSES stands for "higher order path far end consecutive severely errored second". The far end consecutive severely errored second (FESES) refers to the CSES detected at the remote end.
HPFEUAS stands for "higher order path unavailable second". The far end unavailable second (UAS) refers to the UAS detected at the remote end.

Performance Event Attribute Performance event cell Unit Description PFEBE Block (HPFEBBE) Second(HPFEES, HPFESES, HPFECSES and HPFEUAS)

A few bit errors cannot affect services. But if the bit errors are excessive (less than 103 for voice services and 106 for data services), the services can be interrupted.
Relevant Alarms
The HP_REI alarm occurs at the local node at the same time.
Probable Causes
The system detects the HPFEBBE by the bit 1 to bit 4 of the G1 byte.
Procedure
Clear the corresponding performance events at the opposite end. ----End
B.2.9 VC3BBE, VC3ES, VC3SES, VC3CSES, VC3UAS

l
VC3BBE stands for "VC-3 background block error". BBE is an errored block occurring outside the period of UAT and SES. VC3ES stands for "VC-3 errored second". An ES is a certain second with one or more errored blocks detected. VC3SES stands for "VC-3 severely errored second". An SES is a certain second which contains not less than 30% errored blocks or at least one serious disturbance period (SDP). The SDP is a period of at least four consecutive blocks or 1 ms (taking the longer one) where the error ratios of all the consecutive blocks are more than or equal to 10-2 or loss of signal occurs.
VC3CSES stands for "VC-3 consecutive severely errored second". CSES indicates that the SES events consecutively occur, but last less than 10 seconds. VC3UAS stands for "VC-3 unavailable second". A UAS period is counted from the first second of 10 consecutive severely errored seconds (SESs). These ten seconds is considered to be part of the unavailable time. A new available second period starts from the first second of ten consecutive non-SESs. These ten seconds is considered to be part of the available time.

Performance Event Attribute Performance event cell Unit Description B3CNT Block (VC3BBE) Second (VC3ES, VC3SES, VC3CSES, VC3UAS)
Issue 06 (2007-12-30)
B-13

A small number of bit errors do not affect the services. Too many bit errors, however, can interrupt the services (the bit error rate needs to be less than 10-3 for the voice service, and 10-6 for the data service).
Related Alarm
When the VC3BBE, VC3ES, VC3SES, VC3CSES, or VC3UAS performance event crosses the preset threshold, the LP_CROSSTR alarm can occur.
Probable Causes
The system detects the VC3BE by the B3 byte.
Procedure
B.2.10 VC3FEBBE, VC3FEES, VC3FESES, VC3FECSES, VC3FEUAS

l
VC3FEBBE stands for "VC-3 far end background block error". A VC3FEBBE indicates that a BBE event is detected at the far end. VC3FEES stands for "VC-3 far end errored second". An FEES indicates that an ES event is detected at the far end. VC3FESES stands for "VC-3 far end severely errored second". An FESES indicates that an SES event is detected at the far end. VC3FECSES stands for "VC-3 far end consecutive severely errored second". An FECSES indicates that a CSES event is detected at the far end. VC3FEUAS stands for "VC-3 far end unavailable second". An FEUAS indicates that a UAS event is detected at the far end.

Performance Event Attribute Performance event cell Unit Description VC3FEBE Block (VC3FEBBE) Second (VC3FEES, VC3FESES, VC3FECSES, VC3FEUAS)
B-14
Issue 06 (2007-12-30)

A small number of bit errors do not affect the services. Too many bit errors, however, can interrupt the services (the bit error rate needs to be less than 10-3 for the voice service, and 10-6 for the data service).
Related Alarm
At the same time, the LP_REI_VC3 alarm is reported at the local NE.
Probable Causes
The system detects the VC3FEBE by bits 14 of the G1 byte.
Procedure
Clear the corresponding performance events at the opposite NE. ----End
B.2.11 LPBBE, LPES, LPSES, LPCSES and LPUAS

l
LPBBE stands for "lower order path background block error". Background block errors (BBE) refer to the errored blocks excluding those in the unavailable and severely errored seconds.
LPES stands for "Lower order path errored second". The ES is the second with one or more errored blocks. LPSES stands for "lower order path severely errored second". The SES is the second in which more than 30% errored blocks or at least one severely disturbed period (SDP) exists. The SDP is the period during which the bit error rate of all the consecutive blocks in a period of less than four consecutive blocks or 1ms (the longer period is applied) is equal to or higher than 102 or the signal is lost.
LPCSES stands for "lower order path consecutive severely errored second". The consecutive severely errored second (CSES) is the second in which the SES occurs in a consecutive mode and lasts for less than 10 seconds.
LPUAS stands for "lower order path unavailable second". The unavailable second (UAS) is a period of unavailable time that begins at the onset of ten CSESs. When SESs disappear for ten consecutive seconds, the available time begins from the eleventh second, with the previous ten seconds included.

Performance Event Attribute Performance event cell
Issue 06 (2007-12-30)
Description LPBIP2CNT
B-15
Performance Event Attribute Unit
Description Block(LPBBE) Second(LPES, LPSES, LPCSES, LPUAS)

Too many bit errors can interrupt the service (the bit error rate needs to be less than 103 for the voice service, and 106 for the data service), the service can be interrupted.
Relevant Alarm
When the LPBBE, LPES, LPSES, LPCSES, and LPUAS events crosses the preset threshold, the LP_CROSSTR alarm can occur.
Probable Causes
The system detects the lower path bit errors by using the BIP2 of the V5 byte.
Procedure
B.2.12 LPFEBBE, LPFEES, LPFESES, LPFECSES and LPFEUAS

l
LPFEBBE stands for "lower order path far end background block error". The far end background block error (FEBBE) refers to the error detected at the remote end. LPFEES stands for "lower order path far end errored second". The far end errored second (FEES) refers to the ES detected at the remote end. LPFESES stands for "lower order path far end severely errored second". The far end severely errored second (FESES) refers to the SES detected at the opposite end.
LPFECSES stands for "lower order path far end consecutive severely errored second". The far end consecutive severely errored second (FESES) refers to the CSES detected at the remote end.
LPFEUAS stands for "lower order path unavailable second". The far end unavailable second (UAS) refers to the UAS detected at the remote end.

Performance Event Attribute Performance event cell
B-16 Huawei Technologies Proprietary
Description LPFEBE
Issue 06 (2007-12-30)
Performance Event Attribute Unit
Description Block (LPFEBBE) Second (LPFEES, LPFESES, LPFECSES, and LPFEUAS)

Relevant Alarm
If the performance event occurs on the PO1/PH1 board, the LP_REI alarm is generated at the local NE at the same time. If the performance event occurs on the EFT4 board, the LP_REI_VC12 alarm is generated at the local NE at the same time
Probable Causes
The system detects the LPFEBE by the bit 3 of the V5 byte.
Procedure
Clear the corresponding event at the opposite end. ----End
B.2.13 TSLMAX, TSLMIN and TSLCUR

l l l
TSLMAX stands for "maximum value of microwave transmit signal level". TSLMIN stands for "minimum value of microwave transmit signal level". TSLCUR stands for "current value of microwave transmit signal level".

Performance Event Attribute Performance event cell Unit Description TSL 0.1 dBm

When the microwave transmit power is too low or too high, the receive power at the opposite station will be too low or too high. Moreover, bit errors might occur and services might be interrupted.
Relevant Alarm
If the transmit power crosses the threshold, the RADIO_TSL_HIGH or RADIO_TSL_LOW alarm can occur.
B.2.14 RSLMAX, RSLMIN and RSLCUR

l l l
RSLMAX stands for "Maximum value of microwave receive signal level". RSLMIN stands for "Maximum value of microwave receive signal level". RSLCUR "Current value of microwave receive power".

Performance Event Attribute Performance event cell Unit Description RSL 0.1dBm

When the microwave receive power is overly low or overly high, bit errors might occur and the service might be interrupted.
Relevant Alarm
If the receive power crosses the threshold, the RADIO_RSL_HIGH or RADIO_RSL_LOW alarm occurs.
B.2.15 FEC_BEF_COR_ER, FEC_COR_BYTE_CNT

l
FEC_BEF_COR_ER stands for "FEC bit error rate before correcting the errors". This event indicates the impact of the external environment on the transmission. FEC_COR_BYTE_CNT stands for "FEC corrected byte count". This event indicates the impact of the FEC.

Performance Event Attribute Performance event cell Unit Description FECBEFCORER None (FEC_BEF_COR_ER) Byte (FEC_COR_BYTE_CNT)
B-18
Issue 06 (2007-12-30)

If the FEC_BEF_COR_ER is too high, there will be residual bit errors in services after the FEC.
Relevant Alarms
If any byte cannot be troubleshooted, the MW_FECUNCOR alarm occurs.
B.2.16 TPLMAX, TPLMIN and TPLCUR

l l l
TPLMAX stands for "Maximum value of output optical power". TPLMIN stands for "Minimum value of output optical power". TPLCUR stands for "Current value of output optical power".

Performance Event Attribute Performance event cell Unit Description OPM 0.1 dBm

In the normal case, the receive optical power is 3 dB higher than the receiver sensitivity, and 5 dB lower than the overload power. If the transmit power is overly low or high, the receive optical power might be overly low or high at the opposite end. Thus, bit errors might occur and even the service might be interrupted.
Relevant Alarms
l
If the receive optical power at the opposite end is lower than the receiver sensitivity, the IN_PWR_LOW alarm can occur. If the receive optical power at the opposite end is higher than the overload power, the IN_PWR_HIGH alarm can occur.
B.2.17 RPLMAX, RPLMIN and RPLCUR

l l l
RPLMAX stands for "maximum received power of the optical port laser". RPLMIN stands for "minimum received power of the optical port laser". RPLCUR stands for "approximate received power of the optical port laser".
Huawei Technologies Proprietary B-19
Issue 06 (2007-12-30)

Performance Event Attribute Performance event cell Unit Description IPM dBm

In the normal case, the received power is 3 dB higher than the receiver sensitivity, and 5 dB lower than the overload power. When the receive optical power is overly low or high, bit errors might occur and even the service might be interrupted.
Relevant Alarms
l
If the receive optical power is lower than the receiver sensitivity, the IN_PWR_LOW alarm can occur. If the receive optical power is higher than the receiver sensitivity, the IN_PWR_HIGH alarm can occur.
B.2.18 BDTMPMAX, BDTMPMIN and BDTMPCUR

l l l
BDTMPMAX stands for "Maximum board temperature". BDTMPMIN stands for "Minimum board temperature". BDTMPCUR stands for "Current board temperature".

Performance Event Attribute Performance event cell Unit Description None 0.1

Overly high or low board temperature might cause faults such as degradation of the board working performance and bit errors.
Relevant Alarm
If the board temperature crosses the threshold, the TEMP_ALARM alarm occurs.
C Ethernet RMON Performance List
C
DropEvent Fragments Jabbers InBadOcts
Ethernet RMON Performance List
Ethernet RMON performance includes relevant alarms and performance events. Table C-1 Ethernet RMON performance event list Alarm Name Description The number of loss-of-packet events exceeds the threshold. The number of undersized packets exceeds the threshold. The number of oversized packets exceeds the threshold. The number of fragment packets exceeds the threshold. The number of jabber packets exceeds the threshold. The number of bytes in the received bad packets exceeds the threshold. The number of bytes in the transmitted bad packets exceeds the threshold. The number of detected collisions exceeds the threshold. The number of packets with alignment errors exceeds the threshold. The number of packets with FCS errors exceeds the threshold. The number of collisions that are detected within one timeslot period after the transmission exceeds the threshold. The number of frames that fail to be transmitted due to consecutive collisions exceeds the threshold. The number of frames of which the transmission is delayed exceeds the threshold. The system detects that the number of the carrier errors exceeds the threshold.
UndersizePkts OversizePkts
OutBadOcts Collisions AlignmentErrors FCSErrors LateCollisions ExcessiveCollisions DeferredTransmissions CarrierSenseErrors
Issue 06 (2007-12-30)
C-1
Alarm Name OutDropEvents CRCAlignErrors
Description The system monitors that the transmitted data packets are discarded for threshold-crossing times. The number of received packets that have the normal lengths but have CRC errors or alignment errors exceeds the threshold.
Table C-2 Ethernet RMON performance list Performance Type Basic performance Performance Name Packets received (64 octets in length) (packets/second) Packets received (65127 octets in length) (packets/second) Packets received (128255 bytes in length) (packets/second) Packets received (256511 bytes in length) (packets/second) Packets received (5121023 bytes in length) (packets/second) Packets received (10241518 bytes in length) (packets/second) Multicast packets received (packets/second) Broadcast packets received (packets/second) Undersize packets received (packets/second) Oversize packets received (packets/second) Fragments (packets/second) Extended performance Packets transmitted (64 octets in length) (packets/second) Packets transmitted (65127 octets in length) (packets/second) Packets received (128255 octets in length) (packets/second) Packets received (256511 octets in length) (packets/second) Packets received (5121023 octets in length) (packets/second) Packets received (10241518 octets in length) (packets/second) Unicast packets received (packets/second) Unicast packets transmitted (packets/second) Multicast packets transmitted (packets/second) Broadcast packets transmitted (packets/second) Pause frames received (packets/second) Pause frames transmitted (packets/second)
C-2
Issue 06 (2007-12-30)
Performance Type
Performance Name Good octets received (octets/second) Good octets transmitted (octets/second) Bad octets received (octets/second) Bad octets transmitted (octets/second) FCS errors (frames/second) Packets received and transmitted (64 octets in length) (packets/ second) Packets received and transmitted (65127 octets in length) (packets/ second) Packets received and transmitted (128255 octets in length) (packets/second) Packets received and transmitted (256511 octets in length) (packets/second) Packets received and transmitted (5121023 octets in length) (packets/second) Packets received and transmitted (10241518 octets in length) (packets/second)
Issue 06 (2007-12-30)
C-3
D Alarm Management
D
D.1 NE Alarm Management
l l l
Alarm Management
Once set by a user, the NE alarm management function is valid for all boards on the NE. For the OptiX RTN 600, the NE alarm management function includes the following aspects: Set the alarm storage mode. Set the alarm delay. Set the alarm reversion mode.
For details of this function, refer to related manuals or online Helps of OptiX iManager products.
D.2 Board Alarm Management

The board alarm management function is valid only for the boards on which a user configures this function.
D.2.1 Setting the Alarm Level

Alarms are categorized into critical, major, minor, and warning according to their severities. This function is supported by all boards.
D.2.2 Alarm Suppression

The board only detects alarms for which Alarm Monitoring is set to Yes. For the alarms not to be monitored, the maintenance personnel can set alarm suppression. This function is supported for all boards.
D.2.3 Alarm Auto-Report

If Alarm Auto-Report is set to Reported, the board reports the alarm to the NM system in a timely manner when it detects any alarm. If Alarm Auto-Report is set to Not Report, the board reports the alarm only when the NM system queries NE alarms. The maintenance personnel can change the attribute on the NM system.
Issue 06 (2007-12-30) Huawei Technologies Proprietary D-1
D Alarm Management
This function is supported for all boards.
D.2.4 Alarm Reversion

For ports that are not configured with services, some alarms might be reported. To filter alarms that need no attention, set the alarms to be reversed. In this way, the alarm status for this port turns the opposite to the actual case. That is, the status is displayed to be normal when an alarm actually exists. Three modes exist for alarm reversion: non-revertive, automatic reversion, and manual reversion.
l
Non-Revertive In this mode, the alarms are monitored by default and alarm reversion cannot be enabled for a port.
Automatic reversion In this mode, alarm reversion can be enabled for a port. The port does not report the alarms for which alarm reversion is enabled. When the current alarm is cleared, the alarm reversion automatically changes into the disabled status. That is, it changes to the non-revertive mode. Then, the status of alarm reporting for the port becomes the same as the actual status.
Manual reversion In this mode, alarm reversion can be enabled for a port, whether any alarms exist on the port or not. After alarm reversion is enabled, the status of alarm reporting becomes the same as the actual status.
Observe the following cautions when setting alarm reversion:

l
Alarm reversion does not change the actual status of alarms on the board, as well as the indication status of the alarm indicators. Alarm reversion is performed on the SCC. The alarm data is the same on the NE and the NM system, which is the status after the alarm reversion. If queried directly from a board, however, the actual alarm status is returned. Alarm reversion is set on the basis of the ports. And it is supported for each port of the SD1, SL1, SDE, SLE, IF1A, IF 1B, PH1, PO1, and EFT4.
D.2.5 Setting Bit Error Alarm Threshold

When the alarms detected by a board exceed a specific number, the board generates a bit error alarm. This specific number is the bit error alarm threshold. And setting of this threshold is supported for all the bit error threshold-crossing and degrading alarms on the OptiX RTN 600. Table D-1 Setting of the bit error alarm threshold Alarm Name B1_EXC B1_SD B2_EXC
D-2
Default Alarm Threshold 10-3 10-6 10-3
Board Supporting This Function SD1, SL1, SDE, SLE, IF1A, IF1B
Issue 06 (2007-12-30)
D Alarm Management
Alarm Name B2_SD B3_EXC B3_SD BIP_EXC BIP_SD B3_EXC_VC3 B3_SD_VC3
Default Alarm Threshold 10-6 10-3 10-6 10-3 10-6 10-3 10-6
Board Supporting This Function
PO1, PH1 and EFT4
EFT4
D.2.6 AIS Insertion

AIS insertion can be set for some alarms on a board. When the board detects the alarms, it inserts all ones into the lower level service to indicate the remote end that the service is unavailable. Table D-2 Setting of AIS insertion Triggering Condition B1_EXC B2_EXC B2_SD HP_LOM B3_EXC HP_TIM HP_SLM HP_UNEQ B1_SD B3_SD LP_TIM LP_UNEQ LP_SLM T_ALOS BIP_EXC
Issue 06 (2007-12-30)
Default Value Enabled Disabled Disabled Enabled Enabled Disabled Disabled Disabled Disabled Disabled Disabled Disabled Disabled Enabled Enabled
Board Supporting This Function SD1, SL1, SDE, SLE, IF1A, IF1B
PO1 and PH1
D-3
D Alarm Management
Triggering Condition BIP_SD
Default Value Disabled
Board Supporting This Function
NOTE
When the SD1/SL1/SDE/SLE/IF1A/IF1B board detects the R_LOS, R_LOF, MS_AIS, AU_AIS and AU_LOP, it inserts the AIS in a forceful manner.
D.2.7 UNEQ Insertion

When the board detects that the service path is not in use or that the LOS alarm exists, it inserts all zeros to the service signal to indicate the opposite end that this signal is unavailable. Table D-3 Setting of UNEQ insertion Triggering Condition The T_ALOS alarm exists. The service path is not in use. Default Value Disabled Disabled Board Supporting This Function PO1, PH1
D-4
Issue 06 (2007-12-30)
E Performance Event Management
E
l l l
Performance Event Management
E.1 NE Performance Event Management

The NE performance event management function set by users is applicable to all the boards on the NE. The NE performance event management function of the OptiX RTN 600 includes: Setting NE performance event monitoring Setting the start/end time of performance events Enabling/Disabling the reporting of the UAT event
For details of these function, refer to the manuals or online Help of the NM system.
E.2 Board Performance Event Management

The performance event management function is only applicable to the board that the user has set this function on. Table E-1 Board performance event management function Function Setting 15-minute/24-hour performance monitoring Setting 15-minute/24-hour performance event auto-reporting Setting performance threshold Resetting the performance register Generating performance threshold crossing alarms
Issue 06 (2007-12-30)
Board Supporting This Function SD1, SL1, SDE, SLE, IF1A, IF1B, PO1, PH1, EFT4, PXC, SCC, and ODU SD1, SL1, SDE, SLE, IF1A, IF1B, PO1, PH1, EFT4, PXC, SCC, and ODU SD1, SL1, SDE, SLE, IF1A, IF1B, PO1, PH1, EFT4, and ODU SD1, SL1, SDE, SLE, IF1A, IF1B, PO1, PH1, EFT4, and ODU SD1, SL1, SDE, SLE, IF1A, IF1B, PO1, PH1, EFT4, and ODU
E-1
E Performance Event Management
Function Monitoring the UAT event Monitoring the CSES performance event
Board Supporting This Function SD1, SL1, SDE, SLE, IF1A, IF1B, PO1, PH1, EFT4, and ODU SD1, SL1, SDE, SLE, IF1A, IF1B, PO1, PH1, and EFT4
E-2
Issue 06 (2007-12-30)
F Alarm Suppression Relation
F
Alarm Identifier MW_LOF R_LOS, R_LOC
Alarm Suppression Relation
Table F-1 Alarm suppression relation Suppressed Alarm Identifier R_LOS, R_LOF, R_LOC, MW_FECUNCOR, MW_RDI, MW_LIM R_LOF, J0_MM, B1_EXC, B1_SD , MS_AIS, MS_RDI, B2_EXC, B2_SD, MS_REI, AU_AIS, AU_LOP, HP_TIM, HP_UNEQ, HP_SLM, HP_RDI, B3_EXC, B3_SD, HP_LOM, HP_REI, MW_RDI, MW_LIM J0_MM, B1_EXC, B1_SD, MS_AIS, MS_RDI, B2_EXC, B2_SD, MS_REI, AU_AIS, AU_LOP, HP_TIM, HP_UNEQ, HP_SLM, HP_RDI, B3_EXC, B3_SD, HP_LOM, HP_REI , MW_RDI, MW_LIM B2_SD, MS_REI, MS_RDI AU_AIS, AU_LOP, HP_TIM, HP_UNEQ, HP_SLM, HP_RDI, B3_EXC, B3_SD, HP_LOM, HP_REI MS_REI B3_EXC, B3_SD, HP_TIM, HP_SLM, HP_UNEQ, HP_RDI, HP_LOM, HP_REI HP_LOM, B3_EXC, B3_SD HP_LOM LP_TIM, LP_RDI LP_RDI HP_REI B1_SD B2_SD
R_LOF
MS_AIS
MS_RDI AU_AIS, AU_LOP HP_TIMa HP_SLMa LP_UNEQ LP_TIM HP_RDI B1_EXC B2_EXC
Issue 06 (2007-12-30)
F-1
F Alarm Suppression Relation
Alarm Identifier B3_EXC T_ALOS E1_LOS BIP_EXC TU_AIS, TU_LOP
Suppressed Alarm Identifier B3_SD E1_LOS, UP_E1_AIS UP_E1_AIS BIP_SD LP_TIM, LP_SIZE_ERR, LP_UNEQ, LP_RDI, LP_REI, LP_RFI, LP_R_FIFO, BIP_EXC, BIP_SD
NOTE
a: The alarm suppression relation works only when the AIS insertion function is enabled. The alarm suppression relation is invalid in other cases.
F-2
Issue 06 (2007-12-30)
G Glossary
G
Numerics 1+1 protection A ATPC
Glossary
A microwave link protection system composed of one working channel and one protection channel. Two ODUs and two IF boards are used at each end of a microwave link.
Automatic Transmit Power Control. A method of adjusting the transmit power based on fading of the transmit signal detected at the receiver.
E Equalization A method of avoiding selective fading of frequencies. Equalization can compensate for the changes of amplitude frequency caused by frequency selective fading.
F FD Frequency Diversity. Two or more microwave frequencies with certain frequency space are used to transmit/receive the same signal and selection is then performed between the two signals to ease the impact of fading. Forward Error Correction. A bit error correction technology that adds to the payload at the transmit end the correction information based on which the bit errors generated during transmission are corrected at the receive end.
FEC
I IDU IF Indoor Unit. The indoor unit implements accessing, multiplexing/ demultiplexing, and IF processing for services. Intermediate Frequency. IF is the transitional frequency between the frequencies of a modulated signal and an RF signal.
Issue 06 (2007-12-30)
G-1
G Glossary
IF board
A board that processes microwave services.
L Line board A board that processes the services carried on line. As the OptiX RTN 600 involves SDH fiber line, STM-1 cable line, and microwave line, the line boards include SDH optical interface board, STM-1 electrical interface board, and IF board.
N NE Network Element. An NE contains both the hardware and the software running on it. One NE is at least equipped with one SCC board which manages and monitors the entire network element. NE software runs on the SCC board.
O ODU Orderwire Outdoor Unit. The outdoor unit implements frequency conversion and amplification for RF signals. Orderwire is a channel that provides voice communications among operation engineers or maintenance engineers of different stations.
P PDH Plesiosynchronous Digital Hierarchy. A multiplexing scheme of bit stuffing and byte interleaving. It multiplexes the minimum rate 64 kit/s into the 2 Mbit/s, 34 Mbit/s, 140 Mbit/s and 565 Mbit/s rates.
S SD Space Diversity. Two or more antennas separated by a specific distance transmit/receive the same signal and selection is then performed between the two signals to ease the impact of fading. Currently, only receive SD is used. Synchronous Digital Hierarchy. A hierarchical set of digital transport structures, standardized for the transport of suitably adapted payloads over physical transmission networks.
SDH
T T2000 A subnet management system (SNMS). In the telecommunication management network architecture, the T2000 is located between the NE level and network level, which can supports all NE level functions and part of the network level management functions.
G-2
Issue 06 (2007-12-30)
G Glossary
T2100
A network level management system for the optical transmission network, and is located in the network management layer (NML) in the telecommunication management network (TMN) architecture. A board that processes tributary services.
Tributary board
V VC Virtual Container. The information structure used to support path layer connections in the SDH. It consists of information payload, and path overhead (POH) information fields organized in a block frame structure which repeats every 125 or 500 microseconds.
W Web LCT Web LCT is located in the NE management layer of an optical transmission network. It performs management for a single NE.
Issue 06 (2007-12-30)
G-3
H Acronyms and Abbreviations
H
A AIS ATM ATPC AU B BER
Acronyms and Abbreviations
Alarm Indication Signal Asynchronous Transfer Mode Automatic Transmit Power Control Administrative Unit
Bit Error Rate
C CPU Central Processing Unit
D DDF DSP Digital Distribution Frame Digital Signal Processor
E ECC ESD Embedded Control Channel Electrostatic discharge
F FD FEC
Issue 06 (2007-12-30)
Frequency Diversity Forward Error Correction

Huawei Technologies Proprietary H-1
FIFO FPGA
First In First Out Field Programmable Gate Array
G GUI Graphic User Interface
H HSB HSM Hot Standby Hitless Switch Mode
I IDU IF Indoor Unit Intermediate Frequency
L LCT Generation-Local Craft Terminal
N NE NM Network Element Network Management
O ODF ODU Optical Distribution Frame Outdoor Unit
P PDH Plesiochronous Digital Hierarchy
R RF RSL RTN Radio Frequency Received Signal Level Radio Transmission System
H-2
Issue 06 (2007-12-30)
S SD SDH SFP SNCP STM-1 Space Diversity Synchronous Digital Hierarchy Small Form-Factor Pluggable Sub-Network Connection Protection SDH Transport Module -1
V VC-12 VC-3 VC-4 Virtual Container -12 Virtual Container -3 Virtual Container -4
W WS Wayside
Issue 06 (2007-12-30)
H-3
Index
Index
A
A_LOC, A-8 alarm, A-1 AIS insertion, D-3 auto-report, D-2 bit error threshold, D-2 corrective procedure, A-8 level, D-1 list, A-1 management function, board level, D-1 management function, NE level, D-1 reversion, D-2 suppression, D-1 suppression relation, F-1 UNEQ insertion, D-4 alarm management, D-1 ALM_GFP_dCSF, A-10 ALM_GFP_dLFD, A-11 ALM_RTC_FAIL, A-12 APS_FAIL, A-13 APS_INDI, A-15 APS_MANU_STOP, A-9 AU_AIS, A-16 AU_LOP, A-17 AUPJCHIGH, B-5 AUPJCLOW, B-5 AUPJCNEW, B-5 BIP_EXC, A-30 BIP_SD, A-31 board inserting, 3-12 removing, 3-10
C
cleaning fiber adapters, 3-26 cleaning fiber connectors using cartridge cleaners, 3-23 using lens tissue, 3-25 CONFIG_NOSUPPORT, A-32
D
DBMS_ERROR, A-33 DBMS_PROTECT_MODE, A-35 DN_E1_AIS, A-36
E
E1_LOC, A-37 E1_LOS, A-38 ESN_FAILED, A-39 ESN_INVALID, A-40 ETH_LOS, A-41 EXT_SYNC_LOS, A-42
B
B1_EXC, A-18 B1_SD, A-19 B2_EXC, A-20 B2_SD, A-21 B3_EXC, A-22 B3_EXC_VC3, A-23 B3_SD, A-24 B3_SD_VC3, A-25 BD_NOT_INSTALLED, A-26 BD_STATUS, A-27 BDTMPCUR, B-20 BDTMPMAX, B-20 BDTMPMIN, B-20
Issue 06 (2007-12-30)
F
FAN_FAIL, A-43 FCS_ERR, A-44 FEC_BEF_COR_ER, B-18 FEC_COR_BYTE_CNT, B-18
H
HARD_BAD, A-46 HP_CROSSTR, A-48 HP_LOM, A-49 HP_RDI, A-50 HP_REI, A-51 HP_SLM, A-52
i-1
Index
HP_TIM, A-54 HP_UNEQ, A-55 HPAD_CROSSTR, A-56 HPBBE, B-11 HPCSES, B-11 HPES, B-11 HPFEBBE, B-12 HPFECSES, B-12 HPFEES, B-12 HPFESES, B-12 HPFEUAS, B-12 HPSES, B-11 HPUAS, B-11 HSB_INDI, A-57 HSM_INDI, A-58
I
IF_INPWR_ABN, A-59 IN_PWR_HIGH, A-61 IN_PWR_LOW, A-62
J
J0_MM, A-63
LP_SLM, A-89 LP_SLM_VC12, A-90 LP_SLM_VC3, A-91 LP_T_FIFO, A-92 LP_TIM, A-93 LP_TIM_VC12, A-94 LP_TIM_VC3, A-95 LP_UNEQ, A-96 LP_UNEQ_VC12, A-97 LP_UNEQ_VC3, A-98 LPBBE, B-15 LPCSES, B-15 LPES, B-15 LPFEBBE, B-16 LPFECSES, B-16 LPFEES, B-16 LPFESES, B-16 LPFEUAS, B-16 LPS_UNI_BI_M, A-79 LPSES, B-15 LPUAS, B-15 LSR_NO_FITED, A-100 LTI, A-100
M
MS_AIS, A-102 MS_CROSSTR, A-103 MS_RDI, A-104 MS_REI, A-105 MSAD_CROSSTR, A-106 MSBBE, B-9 MSCSES, B-9 MSES, B-9 MSFEBBE, B-10 MSFECSES, B-10 MSFEES, B-10 MSFESES, B-10 MSFEUAS, B-10 MSSES, B-9 MSSW_DIFFERENT, A-107 MSUAS, B-9 MW_FECUNCOR, A-108 MW_LIM, A-109 MW_LOF, A-111 MW_RDI, A-111
K
K1_K2_M, A-64 K2_M, A-66
L
LASER_CLOSED, A-67 LASER_MOD_ERR_EX, A-68 LCAS_FOPR, A-69 LCAS_FOPT, A-71 LCAS_PLCR, A-72 LCAS_PLCT, A-73 LCAS_TLCR, A-75 LCAS_TLCT, A-76 LOOP_ALM, A-77 loopback Ethernet service processing boards, 3-8 IF board, 3-6 PDH interface board, 3-5 SDH electrical interface board, 3-3 SDH optical interface board, 3-2 LP_CROSSTR, A-80 LP_R_FIFO, A-81 LP_RDI, A-82 LP_RDI_VC12, A-83 LP_RDI_VC3, A-84 LP_REI, A-85 LP_REI_VC12, A-86 LP_REI_VC3, A-86 LP_RFI, A-87 LP_SIZE_ERR, A-88
i-2
N
NESF_LOST, A-112 NESTATE_INSTALL, A-114 NO_BD_SOFT, A-115
P
part replacement, 3-10 performance event, B-1 corrective procedure, B-5
Issue 06 (2007-12-30)
Index
list, B-1 management function, board level, E-1 management function, NE level, E-1 performance event management, E-1 POWER_ALM, A-116 POWER_FAIL, A-117 PS, A-118
RSSES, B-7 RSUAS, B-7
S
S1_SYN_CHANGE, A-134 SYN_BAD, A-135 SYNC_C_LOS, A-136
R
R_F_RST, A-119 R_LOC, A-120 R_LOF, A-121 R_LOS, A-123 R_S_ERR, A-125 RADIO_MUTE, A-126 RADIO_RSL_HIGH, A-127 RADIO_RSL_LOW, A-128 RADIO_TSL_HIGH, A-130 RADIO_TSL_LOW, A-131 RELAY_ALARM, A-132 replacing Ethernet service processing board, 3-16 FAN, 3-20 IF board, 3-16 ODU, 3-21 PDH interface board, 3-15 PXC board, 3-17 SCC board, 3-18 SDH electrical interface board, 3-14 SDH optical interface board, 3-13 RMON performance, list, C-1 routine maintenance browsing abnormal event, 1-4 browsing alarm, 1-3 browsing performance event, 1-4 checking IF cable, 1-10 checking the antenna, 1-10 checking the equipment room, 1-8 checking the hybrid coupler, 1-9 checking the ODU, 1-8 cleaning the air filter, 1-6 maintenance items, 1-2 testing the IF 1+1 switching, 1-5 testing the orderwire phone, 1-7 RP_LOC, A-132 RPLCUR, B-19 RPLMAX, B-19 RPLMIN, B-19 RS_CROSSTR, A-133 RSBBE, B-7 RSCSES, B-7 RSES, B-7 RSLCUR, B-18 RSLMAX, B-18 RSLMIN, B-18 RSOFS, B-8 RSOOF, B-8
Issue 06 (2007-12-30)
T
T_ALOS, A-137 T_F_RST, A-139 T_FIFO_E, A-140 T_LOC, A-141 T_LOS, A-142 TEMP_ALARM, A-143 TPLCUR, B-19 TPLMAX, B-19 TPLMIN, B-19 troubleshooting bit error, 2-12 general fault locating procedure, 2-2 interconnection with the PDH equipment, 2-26 interconnection with the SDH equipment, 2-22 orderwire, 2-34 pointer justification, 2-18 service interruption, 2-4 TSLCUR, B-17 TSLMAX, B-17 TSLMIN, B-17 TU_AIS, A-145 TU_AIS_VC12, A-146 TU_AIS_VC3, A-148 TU_LOP, A-150, A-152 TU_LOP_VC12, A-151 TUPJCHIGH, B-6 TUPJCLOW, B-6 TUPJCNEW, B-6
U
UP_E1_AIS, A-153
V
VC3BBE, B-13 VC3CSES, B-13 VC3ES, B-13 VC3FEBBE, B-14 VC3FECSES, B-14 VC3FEES, B-14 VC3FESES, B-14 VC3FEUAS, B-14 VC3SES, B-13 VC3UAS, B-13 VCAT_LOA, A-154 VCAT_LOM_VC12, A-155
Huawei Technologies Proprietary i-3
Index
VCAT_LOM_VC3, A-157 VCAT_SQM_VC12, A-158 VCAT_SQM_VC3, A-159 VOLT_LOS, A-160
W
WRG_BD_TYPE, A-162 WRG_DEV_TYPE, A-163 WS_LOS, A-164
X
XCP_INDI, A-165
i-4
Issue 06 (2007-12-30)

Maintenance Guide

Uploaded by

Document Information

Original Description:

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

Uploaded by

Copyright:

Available Formats

OptiX RTN 600 Radio Transmission System V100R001

Issue Date Part Number

Huawei Technologies Proprietary

Huawei Technologies Co., Ltd.

Trademarks and Permissions

Huawei Technologies Proprietary

OptiX RTN 600 Radio Transmission System Maintenance Guide

3 Common Maintenance Operation Guide..............................................................................3-1

OptiX RTN 600 Radio Transmission System Maintenance Guide

Huawei Technologies Proprietary

OptiX RTN 600 Radio Transmission System Maintenance Guide

B Performance Event Reference.................................................................................................B-1

C Ethernet RMON Performance List........................................................................................C-1 D Alarm Management.................................................................................................................D-1

E Performance Event Management...........................................................................................E-1

Huawei Technologies Proprietary

OptiX RTN 600 Radio Transmission System Maintenance Guide

Huawei Technologies Proprietary

OptiX RTN 600 Radio Transmission System Maintenance Guide

Huawei Technologies Proprietary

OptiX RTN 600 Radio Transmission System Maintenance Guide

About This Document

About This Document

Huawei Technologies Proprietary

About This Document

OptiX RTN 600 Radio Transmission System Maintenance Guide

Huawei Technologies Proprietary

OptiX RTN 600 Radio Transmission System Maintenance Guide

About This Document

Huawei Technologies Proprietary

About This Document

OptiX RTN 600 Radio Transmission System Maintenance Guide

Huawei Technologies Proprietary

OptiX RTN 600 Radio Transmission System Maintenance Guide

About This Document

Huawei Technologies Proprietary

About This Document

OptiX RTN 600 Radio Transmission System Maintenance Guide

Figure 1 Wearing an ESD wrist strap

OptiX RTN 600 Radio Transmission System Maintenance Guide

About This Document

Hoisting Heavy Objects

Huawei Technologies Proprietary

About This Document

OptiX RTN 600 Radio Transmission System Maintenance Guide

Installing and Removing Boards

Bundling Signal Cables

Updates in Issue 06 (2007-12-30)

Updates in Issue 05 (2007-09-30)

Updates in Issue 04 (2007-07-30)

Updates in Issue 03 (2007-06-30)

OptiX RTN 600 Radio Transmission System Maintenance Guide

About This Document

Bugs found in the previous version are fixed.

Updates in Issue 02 (2007-03-30)

Updates in Issue 01 (2007-03-15)

Huawei Technologies Proprietary

OptiX RTN 600 Radio Transmission System Maintenance Guide

1 Routine Maintenance Guide

Routine Maintenance Guide

Huawei Technologies Proprietary

1 Routine Maintenance Guide

OptiX RTN 600 Radio Transmission System Maintenance Guide

1.1 Routine Maintenance Items