159930386-RTN-950-Maintenance-Guide-U2000-V100R002C00-05

OptiX RTN 950 Radio Transmission SystemV100R002C00

Maintenance Guide (U2000)

Issue 05

Date 2010-07-30

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2010. All rights reserved.No part of this document may be reproduced or transmitted in any form or by any means without prior writtenconsent of Huawei Technologies Co., Ltd. Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.All other trademarks and trade names mentioned in this document are the property of their respective holders. NoticeThe purchased products, services and features are stipulated by the contract made between Huawei and thecustomer. All or part of the products, services and features described in this document may not be within thepurchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,and recommendations in this document are provided "AS IS" without warranties, guarantees or representationsof any kind, either express or implied.

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

Huawei Technologies Co., Ltd.Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

Issue 05 (2010-07-30) Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

i

http://www.huawei.com

mailto:[email protected]

About This Document

Related VersionsThe following table lists the product versions related to this document.

Product Name Version

OptiX RTN 950 V100R002C00

iManager U2000 V100R001C00

Intended AudienceThis document provides the guidelines to maintaining the OptiX RTN 950. It also describes thealarms and performance events that are required for troubleshooting during the maintenance.

This document is intended for:

l Network planning engineer

l Data configuration engineer

l System maintenance engineer

Symbol ConventionsThe symbols that may be found in this document are defined as follows.

Symbol Description

Indicates a hazard with a high level of risk,which if not avoided, will result in death orserious injury.

Indicates a hazard with a medium or low levelof risk, which if not avoided, could result inminor or moderate injury.

OptiX RTN 950Maintenance Guide (U2000) About This Document


iii

Symbol Description

Indicates a potentially hazardous situation,which if not avoided, could result inequipment damage, data loss, performancedegradation, or unexpected results.

Indicates a tip that may help you solve aproblem or save time.

Provides additional information to emphasizeor supplement important points of the maintext.

GUI ConventionsThe GUI conventions that may be found in this document are defined as follows.

Convention Description

Boldface Buttons, menus, parameters, tabs, window, and dialog titlesare in boldface. For example, click OK.

> Multi-level menus are in boldface and separated by the ">"signs. For example, choose File > Create > Folder.

Update HistoryUpdates between document issues are cumulative. Therefore, the latest document issue containsall updates made in previous issues.

Updates in Issue 05 (2010-07-30) Based on Product Version V100R002C00

This document is the fifth release for the V100R002C00 product version.

Compared with the fourth release, the updated contents are follows.

Update Description

A.3 Alarms and Handling Procedures Added the BIOS_STATUS,LASER_MOD_ERR_EX alarm.Changed the LASER_SHUT alarm to theLASER_CLOSED alarm.

About This DocumentOptiX RTN 950


iv Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 05 (2010-07-30)

Updates in Issue 04 (2010-04-20) Based on Product Version V100R002C00This document is the fourth release for the V100R002C00 product version.

Compared with the third release, the updated contents are follows.

Update Description

6.12 Replacing the SFP The description of replacing the SFP is added.

Updates in Issue 03 (2010-01-30) Based on Product Version V100R002C00This document is the third release for the V100R002C00 product version.

Compared with the second release, the updated contents are follows.

Update Description

A.2 Alarm List (Classified by LogicalBoards)

Added the alarm list of each board.

C.2 Performance Events (by LogicalBoard)

Added the performance event list of eachboard.

A.3.26 COMMUN_FAIL Added the COMMUN_FAIL alarm.

A.3.36 ETH_EFM_DF Changed the ETH_EFM_Discover alarm tothe ETH_EFM_DF alarm.

A.3.39 ETH_EFM_REMFAULT Changed the ETH_EFM_Fault alarm to theETH_EFM_REMFAULT alarm.

A.3.123 RPS_INDI Revised the possible causes and handlingprocedure of the RPS_INDI alarm.

Updates in Issue 02 (2009-10-30) Based on Product Version V100R002C00This document is the second release for the V100R002C00 product version.

Compared with the first release, the updated contents are follows.

Update Description

7 Database Backup and Restoration Added the backup and restoration of NEdatabases.

OptiX RTN 950Maintenance Guide (U2000) About This Document


v

Update Description

A Alarm Reference l Deleted the alarms POWER_FAIL andRELAY_ALARM.

l Added the alarms associated with the CFcard: CFCARD_OFFLINE,CFCARD_FAILED,CFCARD_W_R_DISABLED, andCFCARD_FULL.

l Added the alarms associated with therelay: RELAY_ALARM_CRITICAL,RELAY_ALARM_MAJOR,RELAY_ALARM_MINOR, andRELAY_ALARM_IGNORE.

l Added the LCS_MISMATCH alarmindicating the license file mismatch for theN+1 protection.

Updates in Issue 01 (2009-06-30) Based on Product Version V100R002C00This document is the first release for the V100R002C00 product version.

About This DocumentOptiX RTN 950


vi Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 05 (2010-07-30)

Contents

About This Document...................................................................................................................iii

1 Safety Precautions......................................................................................................................1-11.1 General Safety Precautions.............................................................................................................................1-21.2 Warning and Safety Symbols..........................................................................................................................1-31.3 Electrical Safety..............................................................................................................................................1-41.4 Environment of Flammable Gas.....................................................................................................................1-71.5 Storage Batteries.............................................................................................................................................1-71.6 Radiation.........................................................................................................................................................1-9

1.6.1 Safe Usage of Optical Fibers..................................................................................................................1-91.6.2 Electromagnetic Exposure....................................................................................................................1-111.6.3 Forbidden Areas...................................................................................................................................1-121.6.4 Laser.....................................................................................................................................................1-121.6.5 Microwave............................................................................................................................................1-13

1.7 Working at Heights.......................................................................................................................................1-131.7.1 Hoisting Heavy Objects.......................................................................................................................1-141.7.2 Using Ladders......................................................................................................................................1-15

1.8 Mechanical Safety.........................................................................................................................................1-171.9 Other Precautions..........................................................................................................................................1-18

2 Guides to High-Risk Operations............................................................................................2-12.1 Operation Guide to the Toggle Lever Switch.................................................................................................2-22.2 Operation Guide to the IF Jumper...................................................................................................................2-42.3 Operation Guide to the IF Cable.....................................................................................................................2-52.4 Operation Guide to the IF Board.....................................................................................................................2-6

3 Routine Maintenance................................................................................................................3-13.1 Routine Maintenance Items.............................................................................................................................3-23.2 Operation Guide to the Routine Maintenance Items.......................................................................................3-3

3.2.1 Checking the NE Status..........................................................................................................................3-43.2.2 Browsing the Current Alarms................................................................................................................3-53.2.3 Browsing the History Alarms.................................................................................................................3-63.2.4 Browsing the Abnormal Events.............................................................................................................3-73.2.5 Browsing Current Performance Events..................................................................................................3-73.2.6 Browsing the History Performance Events............................................................................................3-8

OptiX RTN 950Maintenance Guide (U2000) Contents


vii

3.2.7 Browsing the History Transmit Power and Receive Power...................................................................3-93.2.8 Testing the IF 1+1 Switching...............................................................................................................3-103.2.9 Testing the IF N+1 Switching..............................................................................................................3-113.2.10 Checking the Telecommunications Room.........................................................................................3-123.2.11 Checking the ODU.............................................................................................................................3-123.2.12 Checking the Hybrid Coupler............................................................................................................3-133.2.13 Checking the Antenna........................................................................................................................3-133.2.14 Checking the IF Cable........................................................................................................................3-143.2.15 Checking the LOS Condition.............................................................................................................3-15

4 Emergency Maintenance...........................................................................................................4-14.1 Definition of Emergency.................................................................................................................................4-24.2 Purposes of Emergency Maintenance.............................................................................................................4-24.3 Procedure of Emergency Maintenance............................................................................................................4-2

5 Troubleshooting.........................................................................................................................5-15.1 General Troubleshooting Procedure................................................................................................................5-35.2 Troubleshooting Service Interruptions............................................................................................................5-55.3 Troubleshooting the Radio Link...................................................................................................................5-105.4 Troubleshooting Bit Errors in TDM Services...............................................................................................5-185.5 Troubleshooting Pointer Justifications..........................................................................................................5-245.6 Troubleshooting the Interconnection with SDH Equipment.........................................................................5-285.7 Troubleshooting the Interconnection with PDH Equipment.........................................................................5-315.8 Troubleshooting Ethernet Service Faults......................................................................................................5-335.9 Troubleshooting Orderwire Faults................................................................................................................5-38

6 Part Replacement........................................................................................................................6-16.1 Removing a Board...........................................................................................................................................6-36.2 Inserting a Board.............................................................................................................................................6-56.3 Replacing the SDH Optical Interface Board...................................................................................................6-76.4 Replacing the PDH Interface Board................................................................................................................6-86.5 Replacing the Ethernet Interface Board..........................................................................................................6-96.6 Replacing the IF Board.................................................................................................................................6-106.7 Replacing the CF Card..................................................................................................................................6-116.8 Replacing the System Control, Switch&Clock Board..................................................................................6-136.9 Replacing the Auxiliary Board......................................................................................................................6-156.10 Replacing the Fan Tray...............................................................................................................................6-166.11 Replacing the Power Board.........................................................................................................................6-176.12 Replacing the SFP.......................................................................................................................................6-186.13 Replacing the ODU.....................................................................................................................................6-196.14 Replacing the IF Cable................................................................................................................................6-20

7 Database Backup and Restoration..........................................................................................7-17.1 NE Database....................................................................................................................................................7-27.2 Backing Up the Database Manually................................................................................................................7-3

ContentsOptiX RTN 950


viii Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 05 (2010-07-30)

7.3 Setting the Database Backup Policy................................................................................................................7-37.3.1 Setting the Default Backup Policy.........................................................................................................7-47.3.2 Setting the User-Defined Backup Policy............................................................................................... 7-47.3.3 Executing the Backup Policy of the Device...........................................................................................7-57.3.4 Suspending the Backup Policy of the Device........................................................................................ 7-6

7.4 Restoring the Database....................................................................................................................................7-6

8 Supporting Task.........................................................................................................................8-18.1 Hardware Loopback........................................................................................................................................8-38.2 Cleaning Fiber Connectors and Adapters........................................................................................................8-3

8.2.1 Cleaning Fiber Connectors by Using Cartridge Cleaners......................................................................8-38.2.2 Cleaning Fiber Connectors by Using Lens Tissue.................................................................................8-68.2.3 Cleaning Fiber Adapters by Using Optical Cleaning Sticks..................................................................8-7

8.3 Browsing Alarms, Abnormal Events, and Performance Events..................................................................... 8-88.3.1 Checking the NE Status..........................................................................................................................8-88.3.2 Checking the Board Status.....................................................................................................................8-98.3.3 Browsing Current Alarms....................................................................................................................8-108.3.4 Browsing Abnormal Events.................................................................................................................8-108.3.5 Browsing Current Performance Events................................................................................................8-118.3.6 Browsing History Alarms.....................................................................................................................8-128.3.7 Browsing History Performance Events................................................................................................8-138.3.8 Browsing the Performance Event Threshold-Crossing Records..........................................................8-13

8.4 Querying a Report.........................................................................................................................................8-148.4.1 Querying the Board Information Report .............................................................................................8-148.4.2 Querying the Board Manufacturing Information Report ....................................................................8-158.4.3 Querying the Microwave Link Information Report.............................................................................8-15

8.5 Software Loopback.......................................................................................................................................8-168.5.1 Setting Loopback for the SDH Optical Interface Board......................................................................8-168.5.2 Setting Loopback for the Tributary Board...........................................................................................8-188.5.3 Setting a Loopback for the Ethernet Interface Board...........................................................................8-208.5.4 Setting Loopback for the IF Board.......................................................................................................8-218.5.5 Locating a Fault by Performing Loopback Operations........................................................................8-24

8.6 Reset..............................................................................................................................................................8-258.6.1 Cold Reset............................................................................................................................................8-258.6.2 Warm Reset..........................................................................................................................................8-26

8.7 PRBS Test.....................................................................................................................................................8-278.7.1 Performing a PRBS Test for the Tributary Board................................................................................8-278.7.2 Performing a PRBS Test for the IF Board...........................................................................................8-29

8.8 Querying the License Capacity.....................................................................................................................8-318.9 Setting the On/Off State of the Laser............................................................................................................8-318.10 Setting the ALS Function............................................................................................................................8-328.11 Setting the Automatic Release Function.....................................................................................................8-328.12 Configuring the Performance Monitoring Status of NEs............................................................................8-33



ix

8.13 Querying the Impedance of an E1 Channel.................................................................................................8-348.14 Monitoring Ethernet Packets Through Port Mirroring................................................................................8-348.15 Querying the Attributes of an Ethernet Port................................................................................................8-368.16 Switching the System Control Unit and the Cross-Connect Unit...............................................................8-37

A Alarm Reference.......................................................................................................................A-1A.1 Alarm List (in Alphabetical Order)...............................................................................................................A-2A.2 Alarm List (Classified by Logical Boards)...................................................................................................A-9

A.2.1 CST.......................................................................................................................................................A-9A.2.2 CSH....................................................................................................................................................A-10A.2.3 IF1.......................................................................................................................................................A-11A.2.4 IFU2....................................................................................................................................................A-11A.2.5 IFX2....................................................................................................................................................A-12A.2.6 SL1D...................................................................................................................................................A-12A.2.7 EM6T..................................................................................................................................................A-12A.2.8 EM6F..................................................................................................................................................A-13A.2.9 SP3S/SP3D.........................................................................................................................................A-13A.2.10 AUX.................................................................................................................................................A-13A.2.11 PIU....................................................................................................................................................A-14A.2.12 FAN..................................................................................................................................................A-14A.2.13 ODU.................................................................................................................................................A-14

A.3 Alarms and Handling Procedures................................................................................................................A-14A.3.1 A_LOC...............................................................................................................................................A-14A.3.2 AM_DOWNSHIFT............................................................................................................................A-15A.3.3 APS_FAIL..........................................................................................................................................A-16A.3.4 APS_INDI..........................................................................................................................................A-17A.3.5 APS_MANUAL_STOP.....................................................................................................................A-19A.3.6 AU_AIS..............................................................................................................................................A-20A.3.7 AU_LOP.............................................................................................................................................A-21A.3.8 B1_EXC.............................................................................................................................................A-22A.3.9 B1_SD................................................................................................................................................A-24A.3.10 B2_EXC...........................................................................................................................................A-26A.3.11 B2_SD..............................................................................................................................................A-28A.3.12 B3_EXC...........................................................................................................................................A-31A.3.13 B3_SD..............................................................................................................................................A-33A.3.14 BD_NOT_INSTALLED..................................................................................................................A-35A.3.15 BD_STATUS...................................................................................................................................A-36A.3.16 BIOS_STATUS................................................................................................................................A-38A.3.17 BIP_EXC..........................................................................................................................................A-39A.3.18 BIP_SD.............................................................................................................................................A-40A.3.19 BOOTROM_BAD............................................................................................................................A-42A.3.20 BUS_ERR.........................................................................................................................................A-43A.3.21 CFCARD_FAILED..........................................................................................................................A-44



x Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 05 (2010-07-30)

A.3.22 CFCARD_FULL..............................................................................................................................A-45A.3.23 CFCARD_OFFLINE........................................................................................................................A-47A.3.24 CFCARD_W_R_DISABLED..........................................................................................................A-48A.3.25 CONFIG_NOSUPPORT..................................................................................................................A-49A.3.26 COMMUN_FAIL.............................................................................................................................A-50A.3.27 DBMS_ERROR...............................................................................................................................A-52A.3.28 DBMS_PROTECT_MODE.............................................................................................................A-54A.3.29 DOWN_E1_AIS...............................................................................................................................A-55A.3.30 E1_LOC............................................................................................................................................A-56A.3.31 E1_LOS............................................................................................................................................A-57A.3.32 ETH_CFM_LOC..............................................................................................................................A-58A.3.33 ETH_CFM_MISMERGE.................................................................................................................A-60A.3.34 ETH_CFM_RDI...............................................................................................................................A-62A.3.35 ETH_CFM_UNEXPERI..................................................................................................................A-64A.3.36 ETH_EFM_DF.................................................................................................................................A-66A.3.37 ETH_EFM_EVENT.........................................................................................................................A-67A.3.38 ETH_EFM_LOOPBACK.................................................................................................................A-68A.3.39 ETH_EFM_REMFAULT.................................................................................................................A-69A.3.40 ETH_LOS.........................................................................................................................................A-71A.3.41 ETHOAM_SELF_LOOP.................................................................................................................A-72A.3.42 EXT_SYNC_LOS............................................................................................................................A-74A.3.43 FAN_AGING...................................................................................................................................A-75A.3.44 FAN_FAIL.......................................................................................................................................A-75A.3.45 FLOW_OVER..................................................................................................................................A-76A.3.46 HARD_BAD....................................................................................................................................A-77A.3.47 HP_CROSSTR.................................................................................................................................A-79A.3.48 HP_LOM..........................................................................................................................................A-80A.3.49 HP_RDI............................................................................................................................................A-81A.3.50 HP_REI.............................................................................................................................................A-82A.3.51 HP_SLM...........................................................................................................................................A-83A.3.52 HP_TIM............................................................................................................................................A-84A.3.53 HP_UNEQ........................................................................................................................................A-85A.3.54 HPAD_CROSSTR...........................................................................................................................A-86A.3.55 IF_CABLE_OPEN...........................................................................................................................A-87A.3.56 IF_INPWR_ABN.............................................................................................................................A-89A.3.57 IF_MODE_UNSUPPORTED..........................................................................................................A-90A.3.58 IN_PWR_HIGH...............................................................................................................................A-91A.3.59 IN_PWR_LOW................................................................................................................................A-92A.3.60 J0_MM.............................................................................................................................................A-94A.3.61 K1_K2_M.........................................................................................................................................A-95A.3.62 K2_M................................................................................................................................................A-96A.3.63 LAG_BWMM..................................................................................................................................A-98



xi

A.3.64 LAG_DOWN...................................................................................................................................A-99A.3.65 LAG_MEMBER_DOWN..............................................................................................................A-100A.3.66 LASER_CLOSED..........................................................................................................................A-102A.3.67 LASER_MOD_ERR......................................................................................................................A-102A.3.68 LASER_MOD_ERR_EX...............................................................................................................A-104A.3.69 LCS_LIMITED..............................................................................................................................A-105A.3.70 LCS_MISMATCH.........................................................................................................................A-106A.3.71 LICENSE_LOST............................................................................................................................A-108A.3.72 LOOP_ALM...................................................................................................................................A-109A.3.73 LP_CROSSTR................................................................................................................................A-111A.3.74 LP_R_FIFO....................................................................................................................................A-112A.3.75 LP_RDI...........................................................................................................................................A-113A.3.76 LP_REI...........................................................................................................................................A-114A.3.77 LP_RFI...........................................................................................................................................A-114A.3.78 LP_SIZE_ERR...............................................................................................................................A-115A.3.79 LP_SLM.........................................................................................................................................A-116A.3.80 LP_T_FIFO....................................................................................................................................A-117A.3.81 LP_TIM..........................................................................................................................................A-118A.3.82 LP_UNEQ......................................................................................................................................A-119A.3.83 LPS_UNI_BI_M.............................................................................................................................A-120A.3.84 LSR_NO_FITED............................................................................................................................A-121A.3.85 LTI..................................................................................................................................................A-122A.3.86 MS_AIS..........................................................................................................................................A-123A.3.87 MS_CROSSTR...............................................................................................................................A-124A.3.88 MS_RDI.........................................................................................................................................A-125A.3.89 MS_REI..........................................................................................................................................A-126A.3.90 MSAD_CROSSTR.........................................................................................................................A-127A.3.91 NESOFT_MM................................................................................................................................A-128A.3.92 MULTI_RPL_OWNER.................................................................................................................A-130A.3.93 MW_BER_EXC.............................................................................................................................A-131A.3.94 MW_BER_SD................................................................................................................................A-132A.3.95 MW_FEC_UNCOR.......................................................................................................................A-133A.3.96 MW_LIM.......................................................................................................................................A-137A.3.97 MW_LOF.......................................................................................................................................A-139A.3.98 MW_RDI........................................................................................................................................A-144A.3.99 NESF_LOST..................................................................................................................................A-145A.3.100 NESTATE_INSTALL..................................................................................................................A-147A.3.101 NP1_MANUAL_STOP................................................................................................................A-148A.3.102 NP1_SW_FAIL............................................................................................................................A-149A.3.103 NP1_SW_INDI.............................................................................................................................A-150A.3.104 POWER_ALM.............................................................................................................................A-151A.3.105 POWER_ABNORMAL...............................................................................................................A-152



xii Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 05 (2010-07-30)

A.3.106 R_F_RST......................................................................................................................................A-154A.3.107 R_LOC.........................................................................................................................................A-155A.3.108 R_LOF..........................................................................................................................................A-156A.3.109 R_LOS..........................................................................................................................................A-158A.3.110 R_S_ERR.....................................................................................................................................A-159A.3.111 RADIO_FADING_MARGIN_INSUFF......................................................................................A-161A.3.112 RADIO_MUTE............................................................................................................................A-162A.3.113 RADIO_RSL_BEYONDTH........................................................................................................A-163A.3.114 RADIO_RSL_HIGH....................................................................................................................A-164A.3.115 RADIO_RSL_LOW.....................................................................................................................A-165A.3.116 RADIO_TSL_HIGH....................................................................................................................A-166A.3.117 RADIO_TSL_LOW.....................................................................................................................A-167A.3.118 RELAY_ALARM_CRITICAL....................................................................................................A-168A.3.119 RELAY_ALARM_MAJOR.........................................................................................................A-169A.3.120 RELAY_ALARM_MINOR.........................................................................................................A-170A.3.121 RELAY_ALARM_IGNORE.......................................................................................................A-171A.3.122 RP_LOC.......................................................................................................................................A-172A.3.123 RPS_INDI.....................................................................................................................................A-173A.3.124 RS_CROSSTR.............................................................................................................................A-175A.3.125 RTC_FAIL...................................................................................................................................A-176A.3.126 S1_SYN_CHANGE.....................................................................................................................A-177A.3.127 SWDL_ACTIVATED_TIMEOUT..............................................................................................A-178A.3.128 SWDL_AUTOMATCH_INH......................................................................................................A-179A.3.129 SWDL_CHGMNG_NOMATCH.................................................................................................A-179A.3.130 SWDL_COMMIT_FAIL.............................................................................................................A-180A.3.131 SWDL_INPROCESS...................................................................................................................A-181A.3.132 SWDL_NEPKGCHECK..............................................................................................................A-182A.3.133 SWDL_PKG_NOBDSOFT..........................................................................................................A-183A.3.134 SWDL_PKGVER_MM................................................................................................................A-184A.3.135 SWDL_ROLLBACK_FAIL........................................................................................................A-184A.3.136 SYNC_C_LOS.............................................................................................................................A-185A.3.137 T_ALOS.......................................................................................................................................A-186A.3.138 T_F_RST......................................................................................................................................A-187A.3.139 T_LOC..........................................................................................................................................A-188A.3.140 TEMP_ALARM...........................................................................................................................A-189A.3.141 THUNDERALM..........................................................................................................................A-191A.3.142 TU_AIS........................................................................................................................................A-191A.3.143 TU_LOP.......................................................................................................................................A-193A.3.144 UP_E1_AIS..................................................................................................................................A-194A.3.145 VOLT_LOS..................................................................................................................................A-195A.3.146 WRG_BD_TYPE.........................................................................................................................A-196A.3.147 WRG_DEV_TYPE.......................................................................................................................A-197



xiii

A.3.148 XPIC_LOS...................................................................................................................................A-198

B Abnormal Event Reference.....................................................................................................B-1B.1 Major Abnormal Performance Event List......................................................................................................B-2B.2 Abnormal Performance Events and Handling Procedures.............................................................................B-2

B.2.1 Intermediate Frequency 1+1 Protection Switching...............................................................................B-2B.2.2 N+1 Protection Switching.....................................................................................................................B-4B.2.3 SNCP Switching...................................................................................................................................B-6B.2.4 Linear MS Switching............................................................................................................................B-8B.2.5 System Control Board Switching........................................................................................................B-10B.2.6 RMON Performance Value Below the Lower Limit..........................................................................B-12B.2.7 RMON Performance Value Above the Upper Limit..........................................................................B-13

C Performance Event Reference................................................................................................C-1C.1 Performance Events (by Event Type)............................................................................................................C-2

C.1.1 SDH/PDH Performance Events............................................................................................................C-2C.1.2 Radio Performance Events....................................................................................................................C-4C.1.3 Other Performance Events....................................................................................................................C-6

C.2 Performance Events (by Logical Board)........................................................................................................C-7C.2.1 CST/CSH..............................................................................................................................................C-8C.2.2 IF1.........................................................................................................................................................C-8C.2.3 IFU2....................................................................................................................................................C-10C.2.4 IFX2....................................................................................................................................................C-12C.2.5 SL1D...................................................................................................................................................C-14C.2.6 SP3S/SP3D.........................................................................................................................................C-16C.2.7 ODU....................................................................................................................................................C-17

C.3 Performance Events and Handling Procedures............................................................................................C-18C.3.1 AMDOWNCNT and AMUPCNT......................................................................................................C-18C.3.2 ATPC_P_ADJUST and ATPC_N_ADJUST.....................................................................................C-19C.3.3 AUPJCHIGH, AUPJCLOW, and AUPJCNEW.................................................................................C-20C.3.4 BDTEMPMAX, BDTEMPMIN, and BDTEMPCUR........................................................................C-21C.3.5 FEC_BEF_COR_ER, FEC_UNCOR_BLOCK_CNT and FEC_COR_BYTE_CNT........................C-21C.3.6 HPBBE, HPES, HPSES, HPCSES, and HPUAS...............................................................................C-22C.3.7 HPFEBBE, HPFEES, HPFESES, HPFECSES, and HPFEUAS........................................................C-23C.3.8 IF_BBE, IF_ES, IF_SES, IF_CSES, and IF_UAS.............................................................................C-24C.3.9 LPBBE, LPES, LPSES, LPCSES, and LPUAS..................................................................................C-25C.3.10 LPFEBBE, LPFEES, LPFESES, LPFECSES, and LPFEUAS........................................................C-27C.3.11 MSBBE, MSES, MSSES, MSCSES, and MSUAS..........................................................................C-28C.3.12 MSFEBBE, MSFEES, MSFESES, MSFECSES, and MSFEUAS...................................................C-29C.3.13 QPSKWS, QAMWS16, QAMWS32, QAMWS64, QAMWS128, and QAMWS256.....................C-30C.3.14 RPLMAX, RPLMIN, and RPLCUR................................................................................................C-31C.3.15 RSBBE, RSES, RSSES, RSCSES, and RSUAS..............................................................................C-31C.3.16 RSL_MAX, RSL_MIN, RSL_CUR, and RSL_AVG......................................................................C-33C.3.17 RSOOF and RSOFS..........................................................................................................................C-33



xiv Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 05 (2010-07-30)

C.3.18 RLHTT, RLLTT, TLHTT, TLLTT..................................................................................................C-34C.3.19 TPLMAX, TPLMIN, and TPLCUR.................................................................................................C-35C.3.20 TSL_MAX, TSL_MIN, TSL_CUR, and TSL_AVG.......................................................................C-36C.3.21 TUPJCHIGH, TUPJCLOW, and TUPJCNEW................................................................................C-36

D RMON Event Reference.........................................................................................................D-1D.1 List of RMON Alarm Entries........................................................................................................................D-2D.2 List of RMON Performance Entries..............................................................................................................D-2D.3 RMON Events and Handling Procedures......................................................................................................D-4

D.3.1 ETHCOL.............................................................................................................................................. D-4D.3.2 ETHDROP............................................................................................................................................D-5D.3.3 ETHEXCCOL...................................................................................................................................... D-6D.3.4 ETHFCS...............................................................................................................................................D-7D.3.5 ETHFRG...............................................................................................................................................D-8D.3.6 ETHJAB...............................................................................................................................................D-9D.3.7 ETHLATECOL....................................................................................................................................D-9D.3.8 ETHOVER.........................................................................................................................................D-11D.3.9 ETHUNDER.......................................................................................................................................D-11D.3.10 RXBBAD.........................................................................................................................................D-12D.3.11 TXDEFFRM.....................................................................................................................................D-13

E Alarm Management..................................................................................................................E-1E.1 NE Alarm Management..................................................................................................................................E-2E.2 Board Alarm Management.............................................................................................................................E-2

E.2.1 Setting the Alarm Level........................................................................................................................E-3E.2.2 Alarm Suppression................................................................................................................................E-3E.2.3 Alarm Auto-Report................................................................................................................................E-3E.2.4 Alarm Reversion....................................................................................................................................E-3E.2.5 Setting of the Bit Error Alarm Threshold..............................................................................................E-4E.2.6 AIS Insertion.........................................................................................................................................E-4E.2.7 UNEQ Insertion.....................................................................................................................................E-5

F Performance Event Management............................................................................................F-1F.1 NE Performance Event Management.............................................................................................................F-2F.2 Board Performance Event Management.........................................................................................................F-2

G Alarm Suppression Relationship.........................................................................................G-1

H Glossary.....................................................................................................................................H-1H.1 0-9..................................................................................................................................................................H-2H.2 A-E................................................................................................................................................................ H-2H.3 F-J..................................................................................................................................................................H-7H.4 K-O..............................................................................................................................................................H-10H.5 P-T...............................................................................................................................................................H-12H.6 U-Z..............................................................................................................................................................H-16



xv

Figures

Figure 1-1 Wearing an ESD wrist strap...............................................................................................................1-7Figure 1-2 Slanting optical interface..................................................................................................................1-11Figure 1-3 Level optical interface......................................................................................................................1-11Figure 1-4 Hoisting heavy objects......................................................................................................................1-15Figure 1-5 Slanting a ladder...............................................................................................................................1-16Figure 1-6 Ladder top being one meter higher than the roof.............................................................................1-16Figure 2-1 Toggle lever switch............................................................................................................................2-2Figure 4-1 Main procedure of emergency maintenance.......................................................................................4-3Figure 4-2 Field troubleshooting sub-procedure..................................................................................................4-5Figure 5-1 General troubleshooting procedure.....................................................................................................5-4Figure 5-2 General procedure for troubleshooting the service interruption.........................................................5-6Figure 5-3 Field troubleshooting sub-procedure..................................................................................................5-8Figure 5-4 Procedure for troubleshooting the radio link....................................................................................5-14Figure 5-5 Procedure for troubleshooting bit errors...........................................................................................5-22Figure 5-6 Procedure for troubleshooting pointer justifications........................................................................5-26Figure 5-7 Procedure for troubleshooting the interconnection with SDH equipment........................................5-30Figure 5-8 Procedure for troubleshooting the interconnection with PDH equipment........................................5-32Figure 5-9 Procedure for troubleshooting Ethernet service faults .....................................................................5-35Figure 5-10 Procedure for troubleshooting an RMON performance event .......................................................5-37Figure 5-11 Procedure for troubleshooting orderwire faults..............................................................................5-39Figure 6-1 Removing a board (1) ........................................................................................................................6-3Figure 6-2 Removing a board (2) ........................................................................................................................6-4Figure 6-3 Removing the System control Switch&Clock board..........................................................................6-4Figure 6-4 Removing a board (3) ........................................................................................................................6-4Figure 6-5 Inserting a board (1)...........................................................................................................................6-6Figure 6-6 Inserting a board (2)...........................................................................................................................6-6Figure 6-7 Inserting a board (3)...........................................................................................................................6-7Figure 8-1 Using the CLETOP cassette cleaner...................................................................................................8-4Figure 8-2 Dragging the fiber tip slightly on one cleaning area ..........................................................................8-5Figure 8-3 Dragging the fiber tip slightly on the other cleaning area..................................................................8-5Figure 8-4 Cleaning the fiber with the lens tissue ...............................................................................................8-6Figure 8-5 Optical interface inloop....................................................................................................................8-16Figure 8-6 Optical interface outloop..................................................................................................................8-17

OptiX RTN 950Maintenance Guide (U2000) Figures


xvii

Figure 8-7 VC-4 path outloop............................................................................................................................8-17Figure 8-8 VC-4 path inloop..............................................................................................................................8-17Figure 8-9 Tributary inloop................................................................................................................................8-19Figure 8-10 Tributary outloop............................................................................................................................8-19Figure 8-11 Ethernet port inloop........................................................................................................................8-20Figure 8-12 IF port inloop..................................................................................................................................8-21Figure 8-13 IF port outloop................................................................................................................................8-22Figure 8-14 Composite port inloop....................................................................................................................8-22Figure 8-15 Composite port outloop..................................................................................................................8-22Figure 8-16 Service trail.....................................................................................................................................8-24Figure 8-17 PRBS test in the tributary direction................................................................................................8-27Figure 8-18 PRBS test in the cross-connect direction .......................................................................................8-28Figure 8-19 PRBS test of the IF board...............................................................................................................8-29Figure 8-20 Schematic diagram of Ethernet port mirroring...............................................................................8-35

FiguresOptiX RTN 950


xviii Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 05 (2010-07-30)

Tables

Table 1-1 Warning and safety symbols of the OptiX RTN 950...........................................................................1-3Table 4-1 Description of the main procedure of emergency maintenance...........................................................4-4Table 4-2 Field maintenance operation sheet.......................................................................................................4-4Table 4-3 Description of the field troubleshooting sub-procedure.......................................................................4-6Table 5-1 General troubleshooting procedure......................................................................................................5-5Table 5-2 Description of the general procedure for troubleshooting the service interruption.............................5-7Table 5-3 Description of the field troubleshooting sub-procedure.......................................................................5-9Table 5-4 Causes of radio link faults..................................................................................................................5-12Table 5-5 Description of the procedure for troubleshooting the radio link........................................................5-15Table 5-6 Causes of bit errors.............................................................................................................................5-20Table 5-7 Description of the procedure for troubleshooting bit errors...............................................................5-23Table 5-8 Description of the procedure for troubleshooting pointer justifications............................................5-27Table 5-9 Description of the procedure for troubleshooting the interconnection with SDH equipment........... 5-31Table 5-10 Description of the procedure for troubleshooting the interconnection with PDH equipment......... 5-33Table 5-11 Common faults of Ethernet services................................................................................................5-34Table 5-12 Description of the procedure for troubleshooting Ethernet service faults ...................................... 5-36Table 5-13 Description of the procedure for troubleshooting an RMON performance event ...........................5-38Table 5-14 Description of the procedure for troubleshooting orderwire faults..................................................5-40Table 6-1 Part replacement description ...............................................................................................................6-1Table A-1 Alarm list............................................................................................................................................A-2Table B-1 Major performance event list..............................................................................................................B-2Table C-1 Pointer justification performance events............................................................................................C-2Table C-2 Regenerator section error performance events...................................................................................C-2Table C-3 Multiplex section error performance events.......................................................................................C-3Table C-4 Higher order path error performance events.......................................................................................C-3Table C-5 Lower order path error performance events.......................................................................................C-4Table C-6 Radio power performance events.......................................................................................................C-4Table C-7 FEC performance events....................................................................................................................C-5Table C-8 Radio link error performance events..................................................................................................C-5Table C-9 ATPC performance events..................................................................................................................C-6Table C-10 AM performance events...................................................................................................................C-6Table C-11 Optical power performance events...................................................................................................C-6Table C-12 Board temperature performance events............................................................................................C-7

OptiX RTN 950Maintenance Guide (U2000) Tables


xix

Table C-13 Board temperature performance events............................................................................................C-8Table C-14 Pointer justification performance events..........................................................................................C-8Table C-15 Regenerator section error performance events.................................................................................C-8Table C-16 Multiplex section error performance events.....................................................................................C-9Table C-17 Higher order path error performance events.....................................................................................C-9Table C-18 FEC performance events................................................................................................................C-10Table C-19 Board temperature performance events..........................................................................................C-10Table C-20 Lower order path error performance events...................................................................................C-10Table C-21 FEC performance events................................................................................................................C-11Table C-22 Radio link error performance events..............................................................................................C-11Table C-23 AM performance events.................................................................................................................C-11Table C-24 Board temperature performance events..........................................................................................C-12Table C-25 Lower order path error performance events...................................................................................C-12Table C-26 FEC performance events................................................................................................................C-13Table C-27 Radio link error performance events..............................................................................................C-13Table C-28 AM performance events.................................................................................................................C-13Table C-29 Board temperature performance events..........................................................................................C-14Table C-30 Pointer justification performance events........................................................................................C-14Table C-31 Regenerator section error performance events...............................................................................C-14Table C-32 Multiplex section error performance events...................................................................................C-15Table C-33 Higher order path error performance events...................................................................................C-15Table C-34 Optical power performance events.................................................................................................C-16Table C-35 Board temperature performance events..........................................................................................C-16Table C-36 Pointer justification performance events........................................................................................C-16Table C-37 Lower order path error performance events...................................................................................C-17Table C-38 Radio power performance events...................................................................................................C-17Table C-39 ATPC performance events..............................................................................................................C-18Table D-1 List of RMON alarm entries...............................................................................................................D-2Table D-2 List of RMON performance entries ...................................................................................................D-3Table E-1 Setting of the bit error alarm threshold...............................................................................................E-4Table E-2 Setting of the AIS insertion.................................................................................................................E-4Table E-3 Setting of the UNEQ insertion............................................................................................................E-5Table F-1 Board performance event management function.................................................................................F-2Table G-1 Suppression relationship between intra-board alarms........................................................................G-1Table G-2 Suppression relationship between intra-board alarms........................................................................G-2

TablesOptiX RTN 950


xx Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 05 (2010-07-30)

1 Safety Precautions

About This Chapter

This topic describes the safety precautions that you must follow when installing, operating, andmaintaining Huawei devices.

1.1 General Safety PrecautionsThis topic describes essential safety precautions that instruct you in the selection of measuringand testing instruments when you install, operate, and maintain Huawei devices.

1.2 Warning and Safety SymbolsBefore using the equipment, note the following warning and safety symbols on the equipment.

1.3 Electrical SafetyThis topic describes safety precautions for high voltage, lightning strikes, high leakage current,power cables, fuses, and ESD.

1.4 Environment of Flammable GasThis topic describes safety precautions for the operating environment of a device.

1.5 Storage BatteriesThis topic describes safety precautions for operations of storage batteries.

1.6 RadiationThis topic describes safety precautions for electromagnetic exposure and lasers.

1.7 Working at HeightsThis topic describes safety precautions for working at heights.

1.8 Mechanical SafetyThis topic describes safety precautions for drilling holes, handling sharp objects, operating fans,and carrying heavy objects.

1.9 Other PrecautionsThis topic describes safety precautions for removing and inserting boards, binding signal cables,and routing cables.

OptiX RTN 950Maintenance Guide (U2000) 1 Safety Precautions


1-1

1.1 General Safety PrecautionsThis topic describes essential safety precautions that instruct you in the selection of measuringand testing instruments when you install, operate, and maintain Huawei devices.

All Safety PrecautionsTo ensure the safety of humans and a device, follow the marks on the device and all the safetyprecautions in this document when installing, operating, and maintaining a device.

The "CAUTION", "WARNING", and "DANGER" marks in this document do not cover all thesafety precautions that must be followed. They are supplements to the safety precautions.

Local Laws and RegulationsWhen operating a device, always comply with the local laws and regulations. The safetyprecautions provided in the documents are in addition/supplementary to the local laws andregulations.

Basic Installation RequirementsThe installation and maintenance personnel of Huawei devices must receive strict training andbe familiar with the proper operation methods and safety precautions before any operation.

l Only trained and qualified personnel are permitted to install, operate, and maintain a device.

l Only certified professionals are permitted to remove the safety facilities, and to troubleshootand maintain the device.

l Only the personnel authenticated or authorized by Huawei are permitted to replace orchange the device or parts of the device (including software).

l The operating personnel must immediately report the faults or errors that may cause safetyproblems to the person in charge.

Grounding RequirementsThe grounding requirements are applicable to the device that needs to be grounded.

l When installing the device, always connect the grounding facilities first. When removingthe device, always disconnect the grounding facilities last.

l Ensure that the grounding conductor is intact.

l Do not operate the device in the absence of a suitably installed grounding conductor.

l The device must be connected to the PGND permanently. Before operating the device,check the electrical connections of the device, and ensure that the device is properlygrounded.

Human Safetyl When there is a risk of a lightning strike, do not operate the fixed terminal or touch the

cables.l When there is risk of a lightning strike, unplug the AC power connector. Do not use the

fixed terminal or touch the terminal or antenna connector.

1 Safety PrecautionsOptiX RTN 950


1-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 05 (2010-07-30)

NOTEThe preceding requirements apply to wireless fixed station terminals.

l To avoid electric shocks, do not connect safety extra-low voltage (SELV) circuits totelephone-network voltage (TNV) circuits.

l Do not look into optical ports without eye protection. Otherwise, human eyes may be hurtby laser beams.

l Before operating the device, wear an ESD protective coat, ESD gloves, and an ESD wriststrap. In addition, you need to get off the conductive objects, such as jewelry and watches,to prevent electric shock and burn.

l In case of fire, escape from the building or site where the device is located and press thefire alarm bell or dial the telephone number for fire alarms. Do not enter the burning buildingagain in any situation.

Device Safetyl Before any operation, install the device firmly on the ground or other rigid objects, such as

on a wall or in a rack.l When the system is working, ensure that the ventilation hole is not blocked.

l When installing the front panel, use a tool to tighten the screws firmly, if required.

l After installing the device, clean up the packing materials.

1.2 Warning and Safety SymbolsBefore using the equipment, note the following warning and safety symbols on the equipment.

Table 1-1 lists the warning and safety symbols of the OptiX RTN 950 and their meanings.

Table 1-1 Warning and safety symbols of the OptiX RTN 950

Symbol Indication

This symbol is for anti-static protection.A notice with this symbol indicates that youshould wear an anti-static wrist strap or glovewhen you touch a board. Otherwise, you maycause damage to the board.

CLASS 1LASER

PRODUCT

LASERRADIATION

DO NOT VIEW DIRECTLYWITH OPTICALINSTRUMENTS

CLASS 1M LASERPRODUCT

This symbol is for the laser class.A notice with this symbol indicates the classof the laser. Avoid direct exposure to the laserbeams. Otherwise, it may damage you eyes orskin.



1-3

Symbol Indication

A notice with this symbol indicates where thesubrack is grounded.

ATTENTION 警告

CLEAN PERIODICALLY定期清洗

A notice with this symbol indicates that theair filter should be cleaned periodically.

严禁在风扇高速旋转时接触叶片

DON'T TOUCH THEFAN LEAVES BEFORETHEY SLOW DOWN !

This symbol is for fan safety.A notice with this symbol indicates that thefan leaves should not be touched when the fanis rotating.

1.3 Electrical SafetyThis topic describes safety precautions for high voltage, lightning strikes, high leakage current,power cables, fuses, and ESD.

High Voltage

DANGERl A high-voltage power supply provides power for device operations. Direct human contact

with the high voltage power supply or human contact through damp objects can be fatal.l Unspecified or unauthorized high voltage operations could result in fire or electric shock, or

both.

ThunderstormThe requirements apply only to wireless base stations or devices with antennas and feeders.

DANGERDo not perform operations on high voltage, AC power, towers, or backstays in stormy weatherconditions.




Issue 05 (2010-07-30)

High Leakage Current

WARNINGBefore powering on a device, ground the device. Otherwise, the safety of humans and the devicecannot be ensured.

If a high leakage current mark is labeled near the power connector of the device, you mustconnect the PGND terminal on the shell to the ground before connecting the device to an A/Cinput power supply. This is to prevent the electric shock caused by leakage current of the device.

Power Cables

DANGERDo not install or remove the power cable with a live line. Transient contact between the core ofthe power cable and the conductor may generate electric arc or spark, which may cause fire oreye injury.

l Before installing or removing power cables, you must power off the device.

l Before connecting a power cable, you must ensure that the label on the power cable iscorrect.

Device with Power On

DANGERInstalling or removing a device is prohibited if the device is on.

DANGERDo not install or remove the power cables of the equipment when it is powered on.

Short Circuits

When installing and maintaining devices, place and use the associated tools and instruments inaccordance with regulations to avoid short-circuits caused by metal objects.



1-5

CAUTIONTo avoid short-circuits when using a tool (such as a screwdriver), do not place the tool on theventilation plate of the subrack.

CAUTIONPrevent any screws from dropping into the subrack or chassis to avoid short-circuits.

Fuse

WARNINGIf the fuse on a device blows, replace the fuse with a fuse of the same type and specifications toensure safe operation of the device.

Electrostatic Discharge

CAUTIONThe static electricity generated by the human body may damage the electrostatic sensitivecomponents on the board, such as the large-scale integrated circuit (LSI).

l The human body can generate static electromagnetic fields in the following situations:physical movement, clothing friction, friction between shoes and the ground, plastics inthe hand. Such static electromagnetic effects can remain for an appreciable time.

l Before operating a device, circuit boards, or ASICs, wear an ESD wrist strap that is properlygrounded. The ESD wrist strap can prevent the electrostatic-sensitive components frombeing damaged by the static electricity in the human body.

Figure 1-1 shows the method of wearing an ESD wrist strap.




Issue 05 (2010-07-30)

Figure 1-1 Wearing an ESD wrist strap

1.4 Environment of Flammable GasThis topic describes safety precautions for the operating environment of a device.

DANGERDo not place or operate devices in an environment of flammable or explosive air or gas.

Operating an electronic device in an environment of flammable gas causes a severe hazard.

1.5 Storage BatteriesThis topic describes safety precautions for operations of storage batteries.

DANGERBefore operating a storage battery, you must read the safety precautions carefully and be familiarwith the method of connecting a storage battery.

l Incorrect operations of storage batteries cause hazards. During operation, prevent any short-circuit, and prevent the electrolyte from overflowing or leakage.

l If the electrolyte overflows, it causes potential hazards to the device. The electrolyte maycorrode metal parts and the circuit boards, and ultimately damage the circuit boards.

l A storage battery contains a great deal of energy. Misoperations may cause a short-circuit,which leads to human injuries.



1-7

Basic Precautions

To ensure safety, note the following points before installing or maintaining the storage battery:

l Use special insulation tools.

l Wear an eye protector and take effective protection measures.

l Wear rubber gloves and a protection coat to prevent the hazard caused by the overflowingelectrolyte.

l When handling the storage battery, ensure that its electrodes are upward. Leaning orreversing the storage battery is prohibited.

l Before installing or maintaining the storage battery, ensure that the storage battery isdisconnected from the power supply that charges the storage battery.

Short-Circuit

DANGERA battery short-circuit may cause human injuries. Although the voltage of an ordinary batteryis low, the instantaneous high current caused by a short-circuit emits a great deal of energy.

Avoid any short-circuit of batteries caused by metal objects. If possible, disconnect the workingbattery before performing other operations.

Hazardous Gas

CAUTIONDo not use any unsealed lead-acid storage battery. Lay a storage battery horizontally and fix itproperly to prevent the battery from emitting flammable gas, which may cause fire or deviceerosion.

Working lead-acid storage batteries emit flammable gas. Therefore, ventilation and fireproofingmeasures must be taken at the sites where lead-acid storage batteries are placed.

Battery Temperature

CAUTIONIf a battery overheats, the battery may be deformed or damaged, and the electrolyte mayoverflow.

When the temperature of the battery is higher than 60°C, you need to check whether theelectrolyte overflows. If the electrolyte overflows, take appropriate measures immediately.




Issue 05 (2010-07-30)

Battery Leakage

CAUTIONIn the event of acid overflow or spillage, neutralize the acid and clean it up appropriately.

When handling a leaky battery, protect against the possible damage caused by the acid. Whenyou find the electrolyte leaks, you can use the following substances to counteract and absorb theleaking electrolyte:

l Sodium bicarbonate (NaHCO3)

l Sodium carbonate (Na2CO3)

In the event of acid overflow or spillage, neutralize the acid and clean it up as recommended bythe battery manufacturer and any local regulations for acid disposal.

If a person contacts battery electrolyte, clean the skin that contacts the battery electrolyteimmediately by using water. In case of a severe situation, the person must be sent to a hospitalimmediately.

1.6 RadiationThis topic describes safety precautions for electromagnetic exposure and lasers.

1.6.1 Safe Usage of Optical FibersThe laser beam can cause damage to your eyes. Hence, you must exercise caution when usingoptical fibers.

1.6.2 Electromagnetic ExposureThis topic describes safety precautions for electromagnetic exposure.

1.6.3 Forbidden AreasThe topic describes requirements for a forbidden area.

1.6.4 LaserThis topic describes safety precautions for lasers.

1.6.5 MicrowaveWhen installing and maintaining the equipment of Huawei, follow the safety precautions ofmicrowave to ensure the safety of the human body and the equipment.

1.6.1 Safe Usage of Optical FibersThe laser beam can cause damage to your eyes. Hence, you must exercise caution when usingoptical fibers.



1-9

DANGERWhen installing or maintaining an optical interface board or optical fibers, avoid direct eyeexposure to the laser beams launched from the optical interface board or fiber connectors. Thelaser beam can cause damage to your eyes.

Cleaning Fiber Connectors and Optical Interfaces

CAUTIONIf fiber connectors or flanges are contaminated, optical power commissioning is seriouslyaffected. Therefore, the two endfaces and flange of every external fiber must be cleaned beforethe fiber is led into the equipment through the ODF for being inserted into an optical interfaceon the equipment.

The fiber connectors and optical interfaces of the lasers must be cleaned with the followingspecial cleaning tools and materials:

l Special cleaning solvent: It is preferred to use isoamylol. Propyl alcohol, however, can alsobe used. It is prohibited that you use alcohol and formalin.

l Non-woven lens tissue

l Special compressed gas

l Cotton stick (medical cotton or long fiber cotton)

l Special cleaning roll, used with the recommended cleaning solvent

l Special magnifier for fiber connectors

For cleaning steps, see Task Collection "Cleaning Fiber Connectors and Adapters" in the OptiXRTN 950 Radio Transmission System Maintenance and Troubleshooting.

Replacing Optical Fibers

When replacing an optical fiber, cover the fiber connector of the unused optical fiber with aprotective cap.

Connecting Optical Fibersl Use an attenuator if the optical power is excessively high. A high received optical power

damages the optical interface.

l Directly connect an attenuator to a slanting optical interface. Install the attenuator on theIN port instead of the OUT port.

l Do not directly connect an attenuator to the level optical interface. Use the opticaldistribution frame (ODF) to connect an attenuator to a level optical interface.

Figure 1-2 shows a slanting optical interface, and Figure 1-3 shows a level optical interface.




Issue 05 (2010-07-30)

Figure 1-2 Slanting optical interface

Slanting opticalinterface

Figure 1-3 Level optical interface

Level opticalinterface

1.6.2 Electromagnetic ExposureThis topic describes safety precautions for electromagnetic exposure.

DANGERDanger indicates a hazard that, if not avoided, will result in death or serious injury.



1-11

WARNINGWarning indicates a hazard that, if not avoided, could result in moderate or serious injury.

CAUTIONCaution indicates a hazard that, if not avoided, could result in minor or moderate injury.

If multiple transmit antennas are installed on a tower or backstay, keep away from the transmitdirections of the antennas when you install or maintain an antenna locally.

CAUTIONEnsure that all personnel are beyond the transmit direction of a working antenna.

1.6.3 Forbidden AreasThe topic describes requirements for a forbidden area.

l Before entering an area where the electromagnetic radiation is beyond the specified range,the associated personnel must shut down the electromagnetic radiator or stay at least 10meters away from the electromagnetic radiator, if in the transmit direction.

l A physical barrier and an eye-catching warning flag should be available in each forbiddenarea.

1.6.4 LaserThis topic describes safety precautions for lasers.

WARNINGWhen handling optical fibers, do not stand close to, or look into the optical fiber outlet directlywithout eye protection.

Laser transceivers are used in the optical transmission system and associated test tools. The lasertransmitted through the bare optical fiber produces a small beam of light, and thus it has veryhigh power density and is invisible to human eyes. When a beam of light enters eyes, the eyesmay be damaged.

In normal cases, viewing an un-terminated optical fiber or a damaged optical fiber without eyeprotection at a distance greater than 150 mm does not cause eye injury. Eye injury may occur,however, if an optical tool such as a microscope, magnifying glass, or eye loupe is used to viewan un-terminated optical fiber.




Issue 05 (2010-07-30)

Safety Instructions Regarding LasersTo avoid laser radiation, obey the following instructions:

l All operations should be performed by authorized personnel who have completed therequired training courses.

l Wear a pair of eye-protective glasses when you are handling lasers or fibers.

l Ensure that the optical source is switched off before disconnecting optical fiber connectors.

l Do not look into the end of an exposed fiber or an open connector when you are not surewhether the optical source is switched off.

l Use an optical power meter to measure the optical power and ensure that the optical sourceis switched off.

l Before opening the front door of an optical transmission device, ensure that you are notexposed to laser radiation.

l Do not use an optical tool such as a microscope, a magnifying glass, or an eye loupe toview the optical connector or fiber that is transmitting optical signals.

Instructions Regarding Fiber HandlingRead and abide by the following instructions before handling fibers:

l Only trained personnel are permitted to cut and splice fibers.

l Before cutting or splicing a fiber, ensure that the fiber is disconnected from the opticalsource. After disconnecting the fiber, cap to the fiber connectors.

1.6.5 MicrowaveWhen installing and maintaining the equipment of Huawei, follow the safety precautions ofmicrowave to ensure the safety of the human body and the equipment.

WARNINGStrong radio frequency can harm the human body.

When installing or maintaining an aerial on the tower or mast that is installed with multipleaerials, switch off the transmitter in advance.

1.7 Working at HeightsThis topic describes safety precautions for working at heights.

WARNINGWhen working at heights, be cautious to prevent objects from falling down.

The requirements for working at heights are as follows:



1-13

l The personnel who work at heights must be trained.

l Carry and handle the operating machines and tools with caution to prevent them from fallingdown.

l Safety measures, such as wearing a helmet and a safety belt, must be taken.

l Wear cold-proof clothes when working at heights in cold areas.

l Check all lifting appliances thoroughly before starting the work, and ensure that they areintact.

1.7.1 Hoisting Heavy ObjectsThis topic describes the safety precautions for hoisting heavy objects that you must follow wheninstalling, operating, and maintaining Huawei devices.

1.7.2 Using LaddersThis topic describes safety precautions for using ladders.

1.7.1 Hoisting Heavy ObjectsThis topic describes the safety precautions for hoisting heavy objects that you must follow wheninstalling, operating, and maintaining Huawei devices.

WARNINGWhen heavy objects are being hoisted, do not walk below the cantilever or hoisted objects.

l Only trained and qualified personnel can perform hoisting operations.

l Before hoisting heavy objects, check that the hoisting tools are complete and in goodcondition.

l Before hoisting heavy objects, ensure that the hoisting tools are fixed to a secure object orwall with good weight-bearing capacity.

l Issue orders with short and explicit words to ensure correct operations.

l Ensure that the angle between the two cables is less than or equal to 90 degrees during thelifting, as shown in Figure 1-4.




Issue 05 (2010-07-30)

Figure 1-4 Hoisting heavy objects

1.7.2 Using LaddersThis topic describes safety precautions for using ladders.

Checking Laddersl Before using a ladder, check whether the ladder is damaged. After checking that the ladder

is in good condition, you can use the ladder.l Before using a ladder, you should know the maximum weight capacity of the ladder. Avoid

overweighing the ladder.

Placing LaddersThe proper slant angle of the ladder is 75 degrees. You can measure the slant angle of the ladderwith an angle square or your arms, as shown in Figure 1-5. When using a ladder, to prevent theladder from sliding, ensure that the wider feet of the ladder are downward, or take protectionmeasures for the ladder feet. Ensure that the ladder is placed securely.



1-15

Figure 1-5 Slanting a ladder

Climbing Up a Ladder

When climbing up a ladder, pay attention to the following points:

l Ensure that the center of gravity of your body does not deviate from the edges of the twolong sides.

l Before operations, ensure that your body is stable to reduce risks.

l Do not climb higher than the fourth rung of the ladder (counted from up to down).

If you want to climb up a roof, ensure that the ladder top is at least one meter higher than theroof, as shown in Figure 1-6.

Figure 1-6 Ladder top being one meter higher than the roof




Issue 05 (2010-07-30)

1.8 Mechanical SafetyThis topic describes safety precautions for drilling holes, handling sharp objects, operating fans,and carrying heavy objects.

Drilling Holes

WARNINGDo not drill holes on the cabinet without prior permission. Drilling holes without complyingwith the requirements affects the electromagnetic shielding performance of the cabinet anddamages the cables inside the cabinet. In addition, if the scraps caused by drilling enter thecabinet, the printed circuit boards (PCBs) may be short-circuited.

l Before drilling a hole on the cabinet, remove the cables inside the cabinet.

l Wear an eye protector when drilling holes. This is to prevent eyes from being injured bythe splashing metal scraps.

l Wear protection gloves when drilling holes.

l Take measures to prevent the metallic scraps from falling into the cabinet. After the drilling,clean up the metallic scraps.

Sharp Objects

WARNINGWear protection gloves when carrying the device. This is to prevent hands from being injuredby the sharp edges of the device.

Fansl When replacing parts, place the objects such as the parts, screws, and tools properly. This

is to prevent them from falling into the operating fans, which damages the fans or device.

l When replacing the parts near fans, keep your fingers or boards from touching operatingfans before the fans are powered off and stop running. Otherwise, the hands or the boardsare damaged.

Carrying Heavy Objects

Wear protection gloves when carrying heavy objects. This is to prevent hands from being hurt.



1-17

WARNINGl The carrier must be prepared for load bearing before carrying heavy objects. This is to prevent

the carrier from being strained or pressed by the heavy objects.l When you pull a chassis out of the cabinet, pay attention to the unstable or heavy objects on

the cabinet. This is to prevent the heavy objects on the cabinet top from falling down, whichmay hurt you.

l Generally, two persons are needed to carry a chassis. It is prohibited that only one personcarries a heavy chassis. When carrying a chassis, the carriers should stretch their backs andmove stably to avoid being strained.

l When moving or lifting a chassis, hold the handles or bottom of the chassis. Do not holdthe handles of the modules installed in the chassis, such as the power modules, fan modules,and boards.

1.9 Other PrecautionsThis topic describes safety precautions for removing and inserting boards, binding signal cables,and routing cables.

Removing and Inserting a Board

CAUTIONWhen inserting a board, wear an ESD wrist strap or ESD gloves, and handle the board gently toavoid distorting pins on the backplane.

l Slide the board along the guide rails.

l Do not contact one board with another to avoid short-circuits or damage.

l When holding a board in hand, do not touch the board circuits, components, connectors,or connection slots of the board to prevent damage caused by ESD of the human body tothe electrostatic-sensitive components.

Binding Signal Cables

CAUTIONBind the signal cables separately from the high-current or high-voltage cables.

Routing CablesIn the case of extremely low temperature, heavy shock or vibration may damage the plastic skinof the cables. To ensure the construction safety, comply with the following requirements:




Issue 05 (2010-07-30)

l When installing cables, ensure that the environment temperature is above 0°C.

l If the cables are stored in a place where the ambient temperature is below 0°C, transferthem to a place at room temperature and store the cables for more than 24 hours beforeinstallation.

l Handle the cables gently, especially in a low-temperature environment. Do not performany improper operations, for example, pushing the cables down directly from a truck.

High Temperature

WARNINGIf the ambient temperature exceeds 55°C, the temperature of the front panel surface marked the

flag may exceed 70°C. When touching the front panel of the board in such an environment,you must wear the protection gloves.

IF Cables

WARNINGBefore installing or removing an IF cable, you must turn off the power switch of the IF board.



1-19

2 Guides to High-Risk Operations

About This Chapter

This chapter provides guides to the operations that may cause injury on human bodies anddamage on the equipment if they are misconducted during the commissioning and maintenanceof microwave equipment.

2.1 Operation Guide to the Toggle Lever SwitchThe ODU-PWR switch on the IF board is a toggle lever switch. When you turn on or turn offthe toggle lever switch, perform the operations in strict compliance with the guidelines.Otherwise, the IF board may be damaged.

2.2 Operation Guide to the IF JumperBefore removing or installing an IF jumper, turn off the ODU-PWR. Otherwise, the body injurymay be caused, and the IF board or the ODU may be damaged.

2.3 Operation Guide to the IF CableBefore removing or installing an IF cable, turn off the ODU-PWR. Otherwise, the body injurymay be caused, and the IF board or the ODU may be damaged.

2.4 Operation Guide to the IF BoardBefore removing or installing an IF board, turn off the ODU-PWR. Otherwise, the IF board orthe ODU may be damaged.

OptiX RTN 950Maintenance Guide (U2000) 2 Guides to High-Risk Operations


2-1

2.1 Operation Guide to the Toggle Lever SwitchThe ODU-PWR switch on the IF board is a toggle lever switch. When you turn on or turn offthe toggle lever switch, perform the operations in strict compliance with the guidelines.Otherwise, the IF board may be damaged.

Position and Description of the Toggle Lever SwitchThe toggle lever switch resides on the IF board and controls the power that is fed to the ODU,as shown in Figure 2-1.

Figure 2-1 Toggle lever switch

I : ON

O: OFF

Turning On the Toggle Lever Switch1. Pull the toggle lever switch out slightly.

2 Guides to High-Risk OperationsOptiX RTN 950



Issue 05 (2010-07-30)

2. Turn it to the left.

3. Release the toggle lever switch.

Turning Off the Toggle Lever Switch1. Pull the toggle lever switch out slightly.



2-3

2. Turn it to the right.

3. Release the toggle lever switch.

2.2 Operation Guide to the IF JumperBefore removing or installing an IF jumper, turn off the ODU-PWR. Otherwise, the body injurymay be caused, and the IF board or the ODU may be damaged.

Procedure

Step 1 Turn off the ODU power switch on the IF board. For details, see 2.1 Operation Guide to theToggle Lever Switch.




Issue 05 (2010-07-30)

21

DANGERDo not remove the IF jumper before the ODU is powered off!

Step 2 Remove or install the IF jumper.

----End

2.3 Operation Guide to the IF CableBefore removing or installing an IF cable, turn off the ODU-PWR. Otherwise, the body injurymay be caused, and the IF board or the ODU may be damaged.

Procedure




2-5

21

DANGERDo not remove or install the IF cable before the ODU is powered off!

Step 2 Install or remove the IF cable.

----End

2.4 Operation Guide to the IF BoardBefore removing or installing an IF board, turn off the ODU-PWR. Otherwise, the IF board orthe ODU may be damaged.

Procedure





Issue 05 (2010-07-30)

321

3

DANGERDo not remove or install the IF board before the ODU is powered off!

Step 2 Disconnect the IF jumper or IF cable.

Step 3 Remove or install the IF board.

----End



2-7

3 Routine Maintenance

About This Chapter

The routine maintenance operations are performed to detect and rectify hidden faults before thehidden faults result in the damage to the equipment and thus affect the services.

3.1 Routine Maintenance ItemsRoutine maintenance items are classified into three categories: routine maintenance items carriedout through the NMS, field maintenance items for indoor equipment, and field maintenanceitems for outdoor equipment.

3.2 Operation Guide to the Routine Maintenance ItemsThis topic describes the operation guidelines to each routine maintenance item.

OptiX RTN 950Maintenance Guide (U2000) 3 Routine Maintenance


3-1

3.1 Routine Maintenance ItemsRoutine maintenance items are classified into three categories: routine maintenance items carriedout through the NMS, field maintenance items for indoor equipment, and field maintenanceitems for outdoor equipment.

Routine Maintenance Items Carried Out Through the NMSMaintenance Item Recomm

endedMaintenanceCycle

Remarks

3.2.1 Checking the NE Status Every day -

3.2.2 Browsing the Current Alarms Every day -

3.2.3 Browsing the History Alarms Everyweek

-

3.2.4 Browsing the Abnormal Events Everyweek

-

3.2.5 Browsing CurrentPerformance Events

Everyweek

-

3.2.6 Browsing the HistoryPerformance Events

Everyweek

-

3.2.7 Browsing the History TransmitPower and Receive Power

Everyweek

-

3.2.8 Testing the IF 1+1 Switching Half ayear

Applies only to the equipment that isconfigured in 1+1 protection mode.During the 1+1 protection switching(< 200 ms), the protected services areinterrupted. Hence, it is recommendedthat you perform the 1+1 protectionswitching when the traffic is light.

3.2.9 Testing the IF N+1 Switching Half ayear

Applies only to the equipment that isconfigured in N+1 protection mode.

Field Maintenance Items for Indoor EquipmentMaintenance Item Recommended

Maintenance CycleRemarks

3.2.10 Checking theTelecommunications Room

Every two months -

3 Routine MaintenanceOptiX RTN 950



Issue 05 (2010-07-30)

Field Maintenance Items for Outdoor Equipment

Maintenance Item RecommendedMaintenanceCycle

Remarks

3.2.11 Checking the ODU Half a year Carry out acomplete checkafter a level-8 orhigher hurricane,an earthquake, orother exceptionalcircumstances.

3.2.12 Checking the Hybrid Coupler Half a year

3.2.13 Checking the Antenna Half a year

3.2.14 Checking the IF Cable Half a year

3.2.15 Checking the LOS Condition Half a year

3.2 Operation Guide to the Routine Maintenance ItemsThis topic describes the operation guidelines to each routine maintenance item.

3.2.1 Checking the NE StatusThis topic describes how to check the NE status. By periodically checking the NE status, youcan detect the NE faults in time.

3.2.2 Browsing the Current AlarmsA current alarm is an alarm that is not cleared. Periodically browsing the current alarms helpsin detecting and rectifying faults in time.

3.2.3 Browsing the History AlarmsA history alarm is an alarm that is cleared. Periodically browsing and storing the history alarminformation helps in locating and rectifying faults.

3.2.4 Browsing the Abnormal EventsThis topic describes how to browse the abnormal events. An abnormal event is an abnormalitythat arises in the system at a particular time and not an abnormality that persists for a long time.Periodically browsing the abnormal events helps in detecting equipment faults in time.

3.2.5 Browsing Current Performance EventsPeriodically browsing the performance events helps you to check the long-term running statusof the equipment. Hence, the latent hazards can be detected and cleared in time. The count ofcurrent performance events measures all the performance events that arise between the start timeof the monitoring period and the current time.

3.2.6 Browsing the History Performance EventsPeriodically browsing and storing the history performance events helps in locating faults.

3.2.7 Browsing the History Transmit Power and Receive PowerBy periodically browsing the history transmit power and receive power, you can know the changetrend of the history transmit power and receive power, which provides references fortroubleshooting the radio link.

3.2.8 Testing the IF 1+1 SwitchingPeriodically testing the IF 1+1 switching helps in checking whether switchings can be performedon the equipment normally.



3-3

3.2.9 Testing the IF N+1 SwitchingPeriodically testing the IF N+1 switching helps in checking whether switchings can be performedon the equipment normally.

3.2.10 Checking the Telecommunications RoomPeriodically checking the telecommunications room not only ensures that the equipment canoperate normally in appropriate temperature and humidity conditions, but also reduces the faultrate and increases the service life of the equipment.

3.2.11 Checking the ODUPeriodically checking the ODU helps in detecting the faults and hidden troubles of the ODU intime.

3.2.12 Checking the Hybrid CouplerPeriodically checking the hybrid coupler helps in detecting the faults and hidden troubles of thehybrid coupler in time.

3.2.13 Checking the AntennaPeriodically checking the antenna helps in detecting the faults and hidden troubles of the antennain time.

3.2.14 Checking the IF CableChecking the IF cable periodically helps you detect the faults in and hidden troubles of the IFcable in a timely manner.

3.2.15 Checking the LOS ConditionPeriodically checking the LOS condition of the transmission link helps to detect hidden LOSobstacles on the transmission link.

3.2.1 Checking the NE StatusThis topic describes how to check the NE status. By periodically checking the NE status, youcan detect the NE faults in time.

PrerequisiteYou must be an NM user with NE monitor authority or higher.

Tools, Equipment, and MaterialsU2000

PrecautionsNOTE

By default, the color of the NE icon on the NMS indicates the NE status.

Procedure

Step 1 Check the NE icon in the Main Topology.TIP

In the toolbar of the Main Topology, click the icon, and click the Legend tab in the window that isdisplayed on the right. By moving the vertical scrolling bar, you can view all the status legends of the NE.

The NE icon should be green. In other cases, you can infer as follows:




Issue 05 (2010-07-30)

l Gray: indicates that the communication between the NE and the NMS is interrupted.

l Purple: indicates that the NE status is unknown.

l Red: indicates that a critical alarm is generated.

l Orange: indicates that a major alarm is generated.

l Yellow: indicates that a minor alarm is generated.

l Light blue: indicates that a warning is generated.

Step 2 Double-click the NE. Then, the NE Panel is displayed. The NE should be in Running Status.

NOTE

If the NE is in another state, query the current alarms based on A Alarm Reference.

Step 3 Click the icon. Then, the legend description is displayed.

Step 4 Check the running status of the boards by referring to the legend description. If a board is runningnormally, the board icon should be green.

----End

Postrequisite

If the NE status indicates that alarms exist on the NE, check the current alarms to locate thefaults on the NE.

3.2.2 Browsing the Current AlarmsA current alarm is an alarm that is not cleared. Periodically browsing the current alarms helpsin detecting and rectifying faults in time.

Prerequisite

You must be an NM user with NE monitor authority or higher.

Tools, Equipment, and Materials

U2000

Procedure

Step 1 Choose Fault > Browse Current Alarm from the Main Menu.TIP

In the toolbar, click the icon to browse the current alarms.

Then, the Filter dialog box is displayed.

Step 2 Set the alarm filter conditions according to the requirements. Click OK. Then, the filtered alarmsare displayed in the Current Alarms window.

Step 3 Select Display latest alarms.

Step 4 Browse the displayed alarms.



3-5

Step 5 Select the newly generated alarms, record the details about the alarms, and clickAcknowledge.

Step 6 Notify the fault handling personnel of the alarms in time.

----End

Related InformationYou can browse the network-wide alarms based on alarm severity, by clicking the alarmindicators in the upper right corner.

l You can click (red) to browse the network-wide current critical alarms.

l You can click (orange) to browse the network-wide current major alarms.

l You can click (yellow) to browse the network-wide current minor alarms.

l You can click (light blue) to browse the network-wide current warnings.

NOTE

l By default, the number in the icon of each indicator indicates the number of network-wide current alarmsof the specific severity that are not cleared.

l If a square frame is displayed around an alarm indicator, it indicates that there are unacknowledged alarms.

3.2.3 Browsing the History AlarmsA history alarm is an alarm that is cleared. Periodically browsing and storing the history alarminformation helps in locating and rectifying faults.



Procedure

Step 1 Choose Fault > Browse History Alarm from the Main Menu.Then, the Filter dialog box is displayed.

Step 2 Set the alarm filter conditions according to the requirements.1. Click the Basic Setting tab. Specify the parameters, including Generated Time and

Cleared Time.

NOTEThe start time should be the time when the last history alarm browsing operation was performed, andthe end time should be the current time.

2. Click OK.Then, the filtered alarms are displayed in the History Alarms window.




Issue 05 (2010-07-30)

Step 3 Browse the displayed history alarms.

----End

3.2.4 Browsing the Abnormal EventsThis topic describes how to browse the abnormal events. An abnormal event is an abnormalitythat arises in the system at a particular time and not an abnormality that persists for a long time.Periodically browsing the abnormal events helps in detecting equipment faults in time.

Prerequisite



U2000

Procedure

Step 1 Choose Fault > Browse Event from the Main Menu.Then, the Filter dialog box is displayed.

Step 2 Set the event filter conditions according to the requirements. Click OK.Then, the filtered abnormal events are displayed in the Events window.

Step 3 Select Display latest events.

Step 4 Browse the abnormal events.

For details on how to handle an abnormal event, see B.2 Abnormal Performance Events andHandling Procedures.

----End

Related Information

Compared with an alarm, an abnormal event has only the occurrence time and has no clearancetime.

3.2.5 Browsing Current Performance EventsPeriodically browsing the performance events helps you to check the long-term running statusof the equipment. Hence, the latent hazards can be detected and cleared in time. The count ofcurrent performance events measures all the performance events that arise between the start timeof the monitoring period and the current time.

Prerequisitel The performance monitoring function must be enabled. For details about how to enable the

performance monitoring function, see 8.12 Configuring the Performance MonitoringStatus of NEs.

l You must be an NM user with NE monitor authority or higher.



3-7

Tools, Equipment, MaterialsU2000

Procedure

Step 1 Choose Performance > Browse SDH Performance from the Main Menu, and then selectCurrent Performance Data.

Step 2 Select one or multiple NEs from the left pane, and click .

Step 3 Select All in Monitored Object Filter Condition.

Step 4 Select 15-Minute in the Monitor Period field.

Step 5 Select Gauge, select Select All in the displayed tab page, and select Display Current Valueand Display Maximum and Minimum Values in the right pane.

Step 6 Click Query to browse the current performance events.Compared with the history records, the gauge indicators, such as board temperature, do notchange drastically.

Step 7 Select Count, select Select All in the displayed tab page, and select Display ContinuousSeverely Errored Seconds in the right pane.

Step 8 Click Query to browse the current performance events.In normal cases, no bit error performance events are displayed, and the number of pointerjustification events is less than six per day on each port.

Step 9 Redefine the time span by setting Monitor Period to 24-Hour.

Step 10 Repeat Step 5 to Step 8 to query the performance events in a period of 24 hours.

----End

3.2.6 Browsing the History Performance EventsPeriodically browsing and storing the history performance events helps in locating faults.

Prerequisitel The performance monitoring function must be enabled. If the performance monitoring

function is not enabled, see 8.12 Configuring the Performance Monitoring Status ofNEs and enable the function.



Procedure

Step 1 Choose Performance > Browse SDH Performance from the Main Menu. Click the HistoryPerformance Data tab.




Issue 05 (2010-07-30)



Step 4 Set Monitor Period to 15-Minute.

Step 5 Specify the start time and end time of a specific time span.The time span ranges from the time when the last history performance event browsing operationwas performed to the current time.

Step 6 Specify Data Source.

NOTE

If this is the first browsing operation, you should select Query from NE and Save to Database. Otherwise,you should select Query from NMS. As a result, the history performance databases on the NMS and NEare synchronized.

Step 7 Select Gauge, select Select All in the displayed tab page, and select Display Current Valueand Display Maximum and Minimum Values in the right pane.

Step 8 Click Query to browse the history performance events.

Step 9 Set Monitor Period to 24-Hour.

Step 10 Repeat Step 5 to Step 8 to query the history performance events that occur during the period of24 hours.

----End

Related InformationCurrently, U2000 can query six 24-hour history performance events and sixteen 15-minutehistory performance events from the NE side and query the history performance data of monthsfrom the NMS side.

3.2.7 Browsing the History Transmit Power and Receive PowerBy periodically browsing the history transmit power and receive power, you can know the changetrend of the history transmit power and receive power, which provides references fortroubleshooting the radio link.



Procedure

Step 1 In the NE Explorer, select the ODU whose history transmit power and receive power need to bequeried from the Object Tree and choose Configuration > Performance Graph Analyse fromthe Function Tree.

Step 2 Specify the start time and the end time of a specific time span.



3-9

The time span ranges from the last routine maintenance time to the current time.

Step 3 Set Monitoring Period to 15M.

Step 4 Click Draw.Then, the history transmit and receive power curve of the ODU in the specified time span isdisplayed.

Step 5 Analyze the power curve. If the receive power fading of two adjacent points exceeds 20 dB andthe weather does not change, contact the troubleshooting engineers.

----End

3.2.8 Testing the IF 1+1 SwitchingPeriodically testing the IF 1+1 switching helps in checking whether switchings can be performedon the equipment normally.

PrerequisiteYou must be an NM user with NE operator authority or higher.


Precautionsl In this task, the IF 1+1 switching is performed manually. That is, the IF 1+1 switching is

an HSB switching (switching of the equipment). During the 1+1 protection switching (<200 ms), the protected services are interrupted. Hence, you are recommended to performthe IF 1+1 protection switching when the traffic is light.

l Before you perform the switching, ensure that the standby equipment is normal. If theswitching fails, contact Huawei engineers for troubleshooting.

Procedure

Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > IF 1+1Protection from the Function Tree.

Step 2 In Protection Group, select the IF 1+1 protection group that is to be switched over.

Step 3 In Slot Mapping Relation, right-click the main IF board and choose Manual to Protectionfrom the shortcut menu.

Step 4 Click OK to start the protection switching.

Step 5 Close the dialog box that is displayed.

Step 6 Click Query Switch Status to check the protection switching status.After the switching is completed, the Switching Status of Device of the main IF board shouldbe Manual Switching. At this time, in Protection Group, the main IF board on the equipmentside is the standby board.

Step 7 After the equipment runs normally for a period, query the current alarms and performance events.There should be no new alarms or performance events.




Issue 05 (2010-07-30)

Step 8 Repeat Step 1 to Step 2.

Step 9 In Slot Mapping Relation, right-click the IF board and choose Clear from the shortcut menu.

Step 10 Click OK to switch the services back to the main IF board.


Step 12 Click Query Switch Status to check the protection switching status.Then, in Protection Group, Switching Status of Device of the main IF board should beNormal.

Step 13 After the equipment runs normally for a period, query the current alarms and performance events.There should be no new alarms or performance events.

----End

3.2.9 Testing the IF N+1 SwitchingPeriodically testing the IF N+1 switching helps in checking whether switchings can be performedon the equipment normally.

Prerequisite

You must be an NM user with NE operator authority or higher.


Precautionsl This task is performed as an exercise switching to check whether the NE can implement

the IF N+1 switching. Hence, the service signals are actually not switched.l Before you perform the switching, ensure that the standby equipment is working properly.

If the switching fails, contact Huawei engineers for troubleshooting.

Procedure

Step 1 In the NE Explorer, select the NE and choose Configuration > N+1 Protection from theFunction Tree.

Step 2 In Slot Mapping Relation, right-click a working unit and choose Exercise from the shortcutmenu.The system displays a prompt message, indicating that the switching command is issuedsuccessfully.

Step 3 Click Query Switch Status to check the protection switching status.The status of the working unit should be Exercise.

Step 4 Repeat Step 1.

Step 5 In Slot Mapping Relation, right-click the protection unit or a working unit and choose Clearfrom the shortcut menu.



3-11

The system displays a prompt message, indicating that the switching command is issuedsuccessfully.

Step 6 Click Query Switch Status to check the protection switching status.The status of the working unit should be Normal.

----End

3.2.10 Checking the Telecommunications RoomPeriodically checking the telecommunications room not only ensures that the equipment canoperate normally in appropriate temperature and humidity conditions, but also reduces the faultrate and increases the service life of the equipment.

PrerequisiteNone.


None.

Procedure

Step 1 Record the reading of the thermometer in the telecommunications room.The normal temperature should be between -5ºC and +55ºC.

Step 2 Record the reading of the humidity meter in the telecommunications room.The normal humidity should be between 5% and 95%.

Step 3 Check whether the telecommunications room meets the disaster protection requirements.Ensure the following points:

l There are portable foam fire extinguishers in the telecommunications room. The fireextinguishers should be in their service life.

l There is no rain leakage or water penetration in the telecommunications room.

l There are no mice or insects in the telecommunications room.

Step 4 Clean the telecommunications room.Ensure that there is no dust on the cabinets, on the equipment shelves, in the equipment, on thedesks, or on the floor. The equipment should be tidy.

----End

3.2.11 Checking the ODUPeriodically checking the ODU helps in detecting the faults and hidden troubles of the ODU intime.

PrerequisiteNone.




Issue 05 (2010-07-30)

Tools, Equipment, and MaterialsNone.

Procedure

Step 1 Ensure that the ODU is located within the protected area of the lightning arrester.In plain areas, the lightning arrester protects the areas within an angle of 45° under it. Inmountainous areas and the areas where lightning frequently occurs, the lightning arrester protectsthe area within an angle of 30° under it.

Step 2 Ensure that the ODU is properly fixed on the antenna.

Step 3 Ensure that the ODU is not damaged.

Step 4 Ensure that the interface between the ODU and the hybrid coupler/antenna is waterproof.

Step 5 Ensure that the protection grounding cable of the ODU is firmly and reliably grounded.

----End

3.2.12 Checking the Hybrid CouplerPeriodically checking the hybrid coupler helps in detecting the faults and hidden troubles of thehybrid coupler in time.

PrerequisiteNone.


Procedure

Step 1 Ensure that the hybrid coupler is located within the protected area of the lightning arrester.In plain areas, the lightning arrester protects the areas within an angle of 45° under it. Inmountainous areas and the areas where lightning frequently occurs, the lightning arrester protectsthe area within an angle of 30° under it.

Step 2 Ensure that the hybrid coupler is properly fixed on the antenna.

Step 3 Ensure that the hybrid coupler is not damaged.

Step 4 Ensure that the interface between the hybrid coupler and the antenna is waterproof.

Step 5 Ensure that the interface between the hybrid coupler and the ODU is waterproof.

----End

3.2.13 Checking the AntennaPeriodically checking the antenna helps in detecting the faults and hidden troubles of the antennain time.



3-13

PrerequisiteNone.


Procedure

Step 1 Ensure that the antenna is located within the protected area of the lightning arrester.In plain areas, the lightning arrester protects the areas within an angle of 45° under it. Inmountainous areas and the areas where lightning frequently occurs, the lightning arrester protectsthe area within an angle of 30° under it.

Step 2 Ensure that the antenna is reliably fixed on the pole.

Step 3 Ensure that the antenna radome is not damaged.

Step 4 Ensure that there is no accumulated water in the antenna.

Step 5 Ensure that the fastening bolts are fastened. Ensure that the azimuth angle and the elevationangle of the antenna meet the design requirements

Step 6 In the case of separate mounting, ensure that the installation parts are installed firmly and thatthe connectors are fastened.

Step 7 Check and ensure that the interface of the feed boom is sealed and waterproofed properly.

----End

3.2.14 Checking the IF CableChecking the IF cable periodically helps you detect the faults in and hidden troubles of the IFcable in a timely manner.

PrerequisiteNone.


Procedure

Step 1 Check the IF cable.l The IF cable must not be bent or twisted.

l There must be no bare copper wire.

l The bending radius of the IF cable must be larger than 30 cm.

l The IF cables are bound in accordance with IF Cable Routing and Binding Specificationsspecified in the Installation Reference. The feeder clip or binding strap is not loose.

Step 2 Check the connectors of the IF cable.




Issue 05 (2010-07-30)

l The connectors of the IF cable must be securely connected to the ODU.

l The connectors of the IF cable must be waterproof.

Step 3 Check the grounding of the IF cable.l The grounding clip must be waterproof.

l The grounding cable must be routed from top downwards. The angle between the groundingcable and the IF cable must not be more than 15 degrees.

----End

3.2.15 Checking the LOS ConditionPeriodically checking the LOS condition of the transmission link helps to detect hidden LOSobstacles on the transmission link.

PrerequisiteNone.

Tools, Equipment, and MaterialsTelescope.

Procedure

Step 1 Use the telescope to search for the antenna at the opposite end from a location nearby the localantenna. No buildings or mountains exist on the transmission link, which may block the LOS.

Step 2 Check whether the spanning tree in the transmission path blocks the LOS.

Step 3 Check whether any new buildings exist in the transmission path.

----End



3-15

4 Emergency Maintenance

About This Chapter

Emergency maintenance operations are performed in the case of emergencies or natural factorsthat may result in emergencies during the operation of the equipment.

4.1 Definition of EmergencyIn the case of the microwave equipment, an emergency refers to the interruption of microwaveservices.

4.2 Purposes of Emergency MaintenanceEmergency maintenance operations are performed to restore the services quickly. This isdifferent from troubleshooting, whose purposes are to locate and rectify the faults.

4.3 Procedure of Emergency MaintenanceThe procedure of emergency maintenance consists of a main procedure and a sub-procedure forfield troubleshooting.

OptiX RTN 950Maintenance Guide (U2000) 4 Emergency Maintenance


4-1

4.1 Definition of EmergencyIn the case of the microwave equipment, an emergency refers to the interruption of microwaveservices.

4.2 Purposes of Emergency MaintenanceEmergency maintenance operations are performed to restore the services quickly. This isdifferent from troubleshooting, whose purposes are to locate and rectify the faults.

4.3 Procedure of Emergency MaintenanceThe procedure of emergency maintenance consists of a main procedure and a sub-procedure forfield troubleshooting.

NOTE

In the case of emergency events, the customers in China can contact the 24-hour technical support center ofHuawei at 400-830-2118, and the customers in areas outside China can contact the local Huawei offices.

4 Emergency MaintenanceOptiX RTN 950



Issue 05 (2010-07-30)

Main Procedure of Emergency Maintenance

Figure 4-1 Main procedure of emergency maintenance

Start

Is there any backuptransmission resource?

Yes Switch the service tothe backup resource

Is the Ethernetservice interrupted?

No

Is the power down?

No

Yes

Troubleshoot the Ethernet servicefault

No

Is the service configuredwith protection?

Contact the power supplyengineer

YesTroubleshoot the switching

failure

Is there any alarm onthe NE?

No

Clear the alarm

Is there an incorrectoperation?

Cancel the operation1

Yes

No

Yes

Is the interconnectionfaulty?

Troubleshoot theinterconnection fault

Yes

Yes

No

Is the service restored? Contact Huawei engineersNo

Proceed with the next step Is the servicerestored?

NoLocate the fault by performingloopback operations section by

section

End

Yes

Check the troubleshooting result

3

4

5

2

Yes

No



4-3

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

CommentNo.

Description

1 The common incorrect operations are as follows:l Modifying the data configuration

l Performing loopback operations

l Shutting down the laser

l Muting the ODU

l Changing boards/cables

l Loading the software

2 Faults owing to external factors, including the power supply, optical fibers,environment, and terminal equipment (such as switch devices)

3 The procedure is as follows:1. Check the NE status.2. If the NE is unreachable to the NMS, perform the field troubleshooting

according to Figure 4-2. If alarms are reported on the NE, browse thecurrent alarms.

4 Generally, the following alarms can be cleared on the NMS:APS_MANUAL_STOP, APS_FAIL, BD_NOT_INSTALLED,DBMS_ERROR, HP_TIM, HP_UNEQ, J0_MM, LOOP_ALM,LPS_UNI_BI_M, LP_SIZE_ERR, LP_SLM, LP_TIM, LP_UNEQ,NESOFT_MM, NESF_LOST, RADIO_MUTE, WRG_BD_TYPE, andWRG_DEV_TYPE.

5 After the fault is rectified, proceed as follows:1. Check the alarms, and ensure that the system is running normally.2. Assign personnel to monitor the operation of the system during the peak

service hour, ensuring that subsequent faults can be handled in time.3. Fill in the field maintenance operation sheet, record the fault symptoms

and troubleshooting results, and then send them to Huawei. Table 4-2shows the field maintenance operation sheet.

Table 4-2 Field maintenance operation sheet

Maintained on Maintained by

Actual Step Step in the EntireProcedure

TroubleshootingResult

Remarks




Issue 05 (2010-07-30)

Field Troubleshooting Sub-Procedure

Figure 4-2 Field troubleshooting sub-procedure

Equipmentalarm?

3

No

4

YesClear the alarm

YesClear the alarm

No

5 YesClear the alarm

No


No

End

Proceed to the nextstep

Is the servicerestored?

Yes

No

Start

Obvious equipmentdamage?

Yes Repair or replacethe equipment

No Troubleshoot thepower input

Browse alarmslocally by using the

LCT

2

1

No

Yes Clear the alarm

Locate the fault byperforming loopbackoperations section by

section

7

YesClear the alarm

8

Radio linkalarm?

No

Yes

Is the PWR indicatoron the PIU on?

High orderpath alarm?

Low orderpath alarm?

Faulty inter-connection with SDH/

PDH equipment?

Ethernetservice fault?

No



4-5

Table 4-3 Description of the field troubleshooting sub-procedure

CommentNo.

Description

1 The troubleshooting procedure is as follows:1. Check whether the air circuit breaker for the input power is off. If the air

circuit breaker is automatically turned off, locate the cause (such as shortcircuits or insufficient fuse capacity), and rectify the fault accordingly.

2. Check the power cables, especially the connectors of the power cables. Ifthe power cables or connectors of the power cables are incorrect, replacethe power cables or remake the connectors of the power cables.

3. Check the voltage and polarization of the input power. If the voltage orpolarization of the input power does not meet the requirements, contact thepower engineers for troubleshooting.

NOTEThe fuse capacity can be no less than 20A. The standard voltage of the input power is-48 V and the permitted voltage ranges from -38.4 V to -57.6 V.

2 The troubleshooting procedure is as follows:1. Connecting the Web LCT to the IDU.2. Creating NEs by Using the Search Method.3. Logging In to an NE.4. Checking Alarms.NOTE

If you fail to log in to the created NE, ensure that the operations you performed arecorrect, and then locate and rectify the fault according to the indicators of the Systemcontrol Switch&Clock board. For details about the indicators, see the OptiX RTN 950Hardware Description.

3 Pay special attention to the following alarms:l HARD_BAD

l POWER_ALM

l FAN_FAIL

l BD_STATUS

l NESF_LOST

l TEMP_ALARM

l RADIO_RSL_HIGH

l RADIO_RSL_LOW

l RADIO_TSL_HIGH

l RADIO_TSL_LOW

l IF_INPWR_ABN

l IF_CABLE_OPEN

l VOLT_LOS




Issue 05 (2010-07-30)

CommentNo.

Description

4 Pay special attention to the following alarms:l MW_LIM

l MW_LOF

l R_LOS

l R_LOF

l R_LOC

l MS_AIS

l AU_AIS

l AU_LOP

l B1_EXC

l B2_EXC

l MW_BER_EXC

5 Pay special attention to the following alarms:l HP_LOM

l B3_EXC

l HP_UNEQ

6 Pay special attention to the following alarms:l TU_AIS

l TU_LOP

l BIP_EXC

l LP_UNEQ

l T_ALOS

l E1_LOC

7 See 5.6 Troubleshooting the Interconnection with SDH Equipment or 5.7Troubleshooting the Interconnection with PDH Equipment.

8 See 5.8 Troubleshooting Ethernet Service Faults.



4-7

5 Troubleshooting

About This Chapter

This guide describes the general troubleshooting procedure and the methods of rectifying thecommon faults.

5.1 General Troubleshooting ProcedureWhen handling a fault, make a detailed record of the fault phenomena. The customers in Chinacan contact our 24-hour technical support center at 400-830-2118, and the customers in areasoutside China can contact the local Huawei offices.

5.2 Troubleshooting Service InterruptionsThe service interruption fault indicates the service transmission failure due to an equipment faultor a link fault.

5.3 Troubleshooting the Radio LinkWhen an NE reports MW_LOF or MW_FEC_UNCOR due to failure or performancedeterioration of a radio link, there is a radio link fault.

5.4 Troubleshooting Bit Errors in TDM ServicesWhen an NE reports an alarm or a performance event on the IF board, regenerator section (RS),multiplex section (MS), higher order path (HP), or lower order path (LP), there are bit errors inservices.

5.5 Troubleshooting Pointer JustificationsWhen an NE reports a large number of justification events about the administrative unit (AU)pointer or the tributary unit (TU) pointer, there are pointer justification faults.

5.6 Troubleshooting the Interconnection with SDH EquipmentAn interconnection fault occurs when the NE fails in transmitting SDH services with other SDHequipment.

5.7 Troubleshooting the Interconnection with PDH EquipmentAn interconnection fault occurs when the NE fails in transmitting PDH services with other PDHequipment.

5.8 Troubleshooting Ethernet Service FaultsAn Ethernet service fault may be the Ethernet service interruption or Ethernet servicedeterioration.

OptiX RTN 950Maintenance Guide (U2000) 5 Troubleshooting


5-1

5.9 Troubleshooting Orderwire FaultsIf orderwire calls cannot get through when services are normal, there is an orderwire fault.

5 TroubleshootingOptiX RTN 950



Issue 05 (2010-07-30)

5.1 General Troubleshooting ProcedureWhen handling a fault, make a detailed record of the fault phenomena. The customers in Chinacan contact our 24-hour technical support center at 400-830-2118, and the customers in areasoutside China can contact the local Huawei offices.



5-3

General Troubleshooting Procedure

Figure 5-1 General troubleshooting procedure

Start

Record the fault phenomena

Analyze fault causes and locatethe fault

Is the faultrectified?

Report to Huawei

Make a solution together

Attempt to rectify the fault

Is the service restored?

Observe the operation


Fill in the troubleshootingreport

End

Other troubleshootingprocedures

No

Yes

Yes

Yes

No

No

No

Caused by external factors?

Yes

4

3

2

1




Issue 05 (2010-07-30)

Table 5-1 General troubleshooting procedure

CommentNo.

Description

1 When recording the fault phenomena, make a true and detailed record of theentire process of the fault. Record the exact time when the fault occurs andthe operations performed before and after the fault occurs. Save the alarms,performance events, and other important information.

2 Faults owing to external factors, including the power supply, cables,environment, and terminal equipment (such as switch devices)

3 If the fault is caused by the equipment, see 5.2 Troubleshooting ServiceInterruptions.

4 The customers in China can contact the 24-hour technical support center at400-830-2118, and the customers in areas outside China can contact the localHuawei offices.

5.2 Troubleshooting Service InterruptionsThe service interruption fault indicates the service transmission failure due to an equipment faultor a link fault.

Fault Causesl The operation is improper.

The configuration data changes, the loopback is performed, the cable is replaced, or theboard is replaced.

l The transmission NE or link is faulty.

l The interconnection is improper.

If the transmission equipment functions normally and the connection is normal, checkwhether the interconnection between the transmission equipment is proper and whether theswitch equipment is faulty.

Fault Locating Methods1. Check the operations before the service interruption to determine whether the service

interruption results from an incorrect operation.

2. Query alarms on the centralized NMS or the NMS that is used on the site, and then locatethe fault based on the alarm analysis.

If multiple NEs report alarms, analyze the alarms in the following order: equipment alarm,line alarm, higher order path alarm, and lower order path alarm.

3. If the fault cannot be located through the alarm analysis method, locate the fault byperforming loopback section by section or replacing the corresponding parts.



5-5

CAUTIONIf the fault cannot be rectified immediately, restore the services quickly by adjusting the serviceroute or performing a forced switching.

Troubleshooting Procedure

Figure 5-2 General procedure for troubleshooting the service interruption

Cancel the operation

Contact relateddepartments to solve

the problem

Proceed with thenext step Service restored?

Yes

No

Clear the alarm

Start

Incorrectoperation?

Service interruptedby external causes?

End

Query NE status and alarmsby using the centralized NMS

NE access successfuland alarms cleared?

Rectify the fault on site

Yes

Yes

No

No

No

Yes

4

3

2

1




Issue 05 (2010-07-30)

Table 5-2 Description of the general procedure for troubleshooting the service interruption

CommentNo.

Description

1 The common incorrect operations are as follows:l Modifying the data configuration

l Loopback

l Shutting down the laser

l Muting the ODU

l Changing the board or cable

l Loading the software

2 Faults owing to external factors, including the power supply, cables,environment, and terminal equipment (such as switch devices)

3 For details, see 8.3.1 Checking the NE Status and 8.3.3 Browsing CurrentAlarms.

4 Generally, the following alarms can be cleared on the NMS:APS_MANUAL_STOP, APS_FAIL, BD_NOT_INSTALLED,DBMS_ERROR, HP_TIM, HP_UNEQ, J0_MM, LOOP_ALM,LPS_UNI_BI_M, LP_SIZE_ERR, LP_SLM, LP_TIM, LP_UNEQ,NESOFT_MM, NESF_LOST, NESTATE_INSTALL, RADIO_MUTE,WRG_BD_TYPE, and WRG_DEV_TYPE.



5-7

Figure 5-3 Field troubleshooting sub-procedure

Equipmentalarm?

3

No

4

YesClear the alarm

YesClear the alarm

No


No


No

End

Proceed to the nextstep

Is the servicerestored?

Yes

No

Start

Obvious equipmentdamage?

Yes Repair or replacethe equipment

No Troubleshoot thepower input

Browse alarmslocally by using the

LCT

2

1

No

Yes Clear the alarm

Locate the fault byperforming loopbackoperations section by

section

7

YesClear the alarm

8

Radio linkalarm?

No

Yes

Is the PWR indicatoron the PIU on?

High orderpath alarm?

Low orderpath alarm?

Faulty inter-connection with SDH/

PDH equipment?

Ethernetservice fault?

No




Issue 05 (2010-07-30)

Table 5-3 Description of the field troubleshooting sub-procedure

CommentNo.

Description

1 The troubleshooting procedure is as follows:1. Check whether the air circuit breaker for the input power is off. If the air

circuit breaker is automatically turned off, locate the cause (such as shortcircuits or insufficient fuse capacity), and rectify the fault accordingly.

2. Check the power cables, especially the connectors of the power cables. Ifthe power cables or connectors of the power cables are incorrect, replacethe power cables or remake the connectors of the power cables.

3. Check the voltage and polarization of the input power. If the voltage orpolarization of the input power does not meet the requirements, contact thepower engineers for troubleshooting.

NOTEThe fuse capacity can be no less than 20A. The standard voltage of the input power is-48 V and the permitted voltage ranges from -38.4 V to -57.6 V.

2 The troubleshooting procedure is as follows:1. Connecting the Web LCT to the IDU.2. Creating NEs by Using the Search Method.3. Logging In to an NE.4. Checking Alarms.NOTE

If you fail to log in to the created NE, ensure that the operations you performed arecorrect, and then locate and rectify the fault according to the indicators of the Systemcontrol Switch&Clock board. For details about the indicators, see the OptiX RTN 950Hardware Description.

3 Pay special attention to the following alarms:l HARD_BAD

l POWER_ALM

l FAN_FAIL

l BD_STATUS

l NESF_LOST

l TEMP_ALARM

l RADIO_RSL_HIGH

l RADIO_RSL_LOW

l RADIO_TSL_HIGH

l RADIO_TSL_LOW

l IF_INPWR_ABN

l IF_CABLE_OPEN

l VOLT_LOS



5-9

CommentNo.

Description

4 Pay special attention to the following alarms:l MW_LIM

l MW_LOF

l R_LOS

l R_LOF

l R_LOC

l MS_AIS

l AU_AIS

l AU_LOP

l B1_EXC

l B2_EXC

l MW_BER_EXC

5 Pay special attention to the following alarms:l HP_LOM

l B3_EXC

l HP_UNEQ

6 Pay special attention to the following alarms:l TU_AIS

l TU_LOP

l BIP_EXC

l LP_UNEQ

l T_ALOS

l E1_LOC

7 See 5.6 Troubleshooting the Interconnection with SDH Equipment or 5.7Troubleshooting the Interconnection with PDH Equipment.

8 See 5.8 Troubleshooting Ethernet Service Faults.

Experience and SummaryThe maintenance personnel need to perform the routine maintenance operations periodically, todetect and rectify faults before the faults affect the services and thus to reduce the equipmentfault rate.

5.3 Troubleshooting the Radio LinkWhen an NE reports MW_LOF or MW_FEC_UNCOR due to failure or performancedeterioration of a radio link, there is a radio link fault.




Issue 05 (2010-07-30)

Context

The key to locating a radio link fault is to check whether the transmit power and the receivepower are normal and whether there is an external interference.

In the following two cases, the transmit power is abnormal. The first case is that the transmitpower exceeds the range that the ODU supports. The second case is that the difference betweenthe actual transmit power and the preset value is more than 2 dB when the ATPC is disabled.The relevant alarms and performance events are as follows:

l RADIO_TSL_HIGH

l RADIO_TSL_LOW

l TSL_CUR

l TSL_MAX

l TSL_MIN

l TSL_AVG

NOTE

For the range of the transmit power, see the OptiX RTN 950 Radio Transmission System ProductDescription.

In the following two cases, the receive power is abnormal. In the first case, the receive poweris lower than the normal value (Normal value = Planned value - 3 dB). In the second case, thereceive power is lower than the receiver sensitivity or higher than the free space receive powerdue to fading. The relevant alarms and performance events are as follows:

l RADIO_RSL_HIGH

l RADIO_RSL_LOW

l RSL_CUR

l RSL_MAX

l RSL_MIN

l RSL_AVG

NOTE

In the case of the radio link whose AM function is enabled, the receiver sensitivity is the specific receiversensitivity at the guaranteed capacity.

For details on the receiver sensitivity, see the OptiX RTN 950 Radio Transmission System ProductDescription.

Generally, external interference is classified into co-channel interference and adjacent channelinterference.

l Co-channel interference refers to crosstalk from two different radio transmitters that usethe same frequency channel. Hence, the entire spectrum may be affected.

l Adjacent channel interference refers to signal impairment to one frequency, due to presenceof another signal on a nearby frequency. Hence, a part of the spectrum is affected.

Interference is closely related to the frequency. Hence, the radio link may be faulty in onedirection if interference exists on the radio link.



5-11

Fault Causes

Table 5-4 Causes of radio link faults

Fault Common Fault Cause

The transmit power is abnormal. The ODU is faulty.

The receive power is always lower than thenormal value.

l The antenna direction is not adjustedproperly.

l The antennas have different polarizationdirections.

l There is a mountain or building in thetransmit direction.

l The antenna is faulty or the connectionbetween the antenna and the ODU isabnormal (for example, the waveguideinterface of the ODU is wet or the flexiblewaveguide is not connected properly).

l The ODU is faulty.

The receive power is abnormal due to slow upfading.

There is external interference.

The receive power is abnormal due to slowdown fading.

The fading margin is insufficient.

The receive power is abnormal due to fastfading.

The multipath fading is fast.

The receive power is normal, but faults occuron the radio link intermittently.

There is external interference.

NOTE

Based on the RSL, fading is classified into up fading and down fading.

l Up fading

The RSL is higher than the RSL in the free space. The difference can be 10-odd decibels.

l Down fading

The RSL is lower than the RSL after free space fading. The difference can be tens of decibels.

Based on the fading time, fading is classified into fast fading and slow fading.

l Fast fading

The fading lasts from several milliseconds to tens of seconds.

l Slow fading

The fading lasts from tens of seconds to several hours.

Generally, slow down fading and fast fading are caused by factors related to the transmission link. Hence,the radio link may be faulty in both directions in the case of slow down fading or fast fading.




Issue 05 (2010-07-30)

Fault Locating Methods1. Check whether the ODU is muted, powered off, or looped back. Check whether the data

configuration is correct.2. Check whether the ODU and the IF board are faulty.3. If the transmit power is abnormal, replace the ODU.4. If the receive power is abnormal, analyze and locate the causes according to the fading

type.5. If the receive power is normal but faults occur on the radio link intermittently, check

whether there is interference before you proceed.6. If the transmit power and receive power are normal, perform loopback operations.



5-13


Figure 5-4 Procedure for troubleshooting the radio link

Start

ODU or IF relatedalarm?

Yes

Clear the alarm

No

Proceed tothe next step


End

Yes

No

Transmit powernormal?

Yes

No

2

Rectify the fault

Perform loopbackoperations

9

No

Rectify the fault

YesRectify the fault

Slow up fadingcauses abnormal

RSL?

No

Rectify the fault

3

Cancel theoperation

1

4

5

6

Yes

No

Yes

No

Rectify the fault

8Yes

Yes

No

No

Rectify the fault

7Yes

Incorrect operation?

RSL always lowerthan the normal

value?

Slow down fadingcauses abnormal

RSL?

Fast fadingcauses abnormal

RSL?

Radio linkfaulty in onedirection?




Issue 05 (2010-07-30)

Table 5-5 Description of the procedure for troubleshooting the radio link

Comment No. Description

1 Rectifyincorrectoperations.

Check the following points:l Check whether the ODU is powered off.

l Check whether the ODU is muted.

l Check whether the IF board is looped back.

l Check whether the data configuration at the transmit end is the sameas the data configuration at the receive end.

l Check whether the data configuration matches the types of the ODUand the hybrid coupler.

2 Rectifyequipment faults.

Pay special attention to the following alarms:l VOLT_LOS

l CONFIG_NOSUPPORT

l HARD_BAD

l TEMP_ALARM

l IF_INPWR_ABN

l RADIO_MUTE

l RADIO_TSL_HIGH

l RADIO_TSL_LOW

l RADIO_RSL_HIGH

l RADIO_RSL_LOW

l IF_CABLE_OPEN

3 Troubleshootthe anomaly ofthe transmitpower.

Replace the ODU.



5-15


4 Troubleshootthe anomaly thatthe receive poweris lower than thenormal value.

The troubleshooting procedure is as follows:1. If the receive power decreases sharply and does not recover, check the

installation of the antenna. Ensure that the azimuth angle of the antennameets the requirement.Check whether the antenna is aligned properly. Check whether thereceived signal is from the main lobe.If the antenna direction is not aligned properly, adjust the antenna in awide range.

2. If the difference between the receive power of the main ODU andstandby ODU at one end of the 1+1 HSB radio link is beyond the rangefrom 0 dB to 9 dB (in the case of an unbalanced hybrid coupler) orbeyond the range from 0 dB to 5 dB (in the case of a balanced hybridcoupler), perform 1+1 HSB switching or replace the ODUs and hybridcoupler to narrow down the fault to a specific part.

3. If the difference between the RSL at the receive end and transmit endis larger than 10 dB, replace the ODUs to check whether the main orstandby ODU is faulty.

4. Check whether the setting of the polarization direction of the antennais correct. Rectify the wrong polarization direction.

5. Replace the ODUs and hybrid coupler to narrow down the fault to aspecific part.

6. Check whether there is a mountain or building in the transmit direction.7. Check whether the gains of the antennas at the receive and transmit

ends comply with the specifications. Replace the antenna whose gaindoes not comply with the specifications.

5 Troubleshootslow up fading.

The troubleshooting procedure is as follows:1. Check whether there is co-channel interference.

1. Mute the ODU at the opposite end.2. Check the RSL at the local end. If the RSL exceeds -90 dBm, it

indicates that there is co-channel interference that may affect thelong-term availability and performance of the system.

2. Use a spectrum analyzer to analyze the interference source.3. Contact the spectrum management department to clear the interference

spectrum or change plans to reduce the interference.

6 Troubleshootslow downfading.

Contact the network planning department to make the following changes:l Increase the installation height of the antenna.

l Reduce the transmission distance.

l Increase the antenna gain.

l Increase the transmit power.




Issue 05 (2010-07-30)


7 Troubleshootfast fading.

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 reflectioncoefficient, thus reducing the multipath fading.

l Adjust the RF configuration to change the radio link to the 1+1 SDmode.

l In the case of a 1+1 SD radio link, adjust the height difference betweentwo antennas to ensure that the receive power of one antenna is higherthan the receive power of the other antenna.

l Increase the fading margin, by replacing the original antennas withantennas of a larger diameter or increasing the transmit power of theoriginal antennas.

8 Troubleshootinterference.

The troubleshooting procedure is as follows:1. Check whether there is co-channel interference.

1. Mute the ODU at the opposite end.2. Check the RSL at the local end. If the RSL exceeds -90 dBm, it

indicates that there is co-channel interference that may affect thelong-term availability and performance of the system.

2. Check whether there is adjacent channel interference.1. Mute the ODU at the opposite end.2. Adjust the microwave working mode at the local end and use the

minimum channel spacing.3. Decrease the receive frequency at the local end by a half of the

channel spacing.4. Test and record the RSL.5. Increase the receive frequency at the local end, with a step of 0.5

MHz or 1 MHz. Record the RSL accordingly until the receivefrequency is equal to the original receive frequency plus a half ofthe channel spacing.

6. Compare the recorded RSL values, and check whether the RSL ina certain spectrum is abnormal if the received frequency is withinthe permitted range.

3. Use a spectrum analyzer to analyze the interference source.4. Contact the spectrum management department to clear the interference

spectrum or change plans to reduce the interference.



5-17


9 Performloopbackoperations tolocate the fault.

The troubleshooting procedure is as follows:1. Perform an inloop at the IF port.

If the fault persists after the inloop is performed, replace the IFboard.

2. Check whether the cable connector is made in accordance withspecifications. If any cable connectors do not comply with thespecifications, see the Installation Reference and remake cableconnectors.

3. Check whether the IF cable is soggy, broken, or pressed. If yes, replacethe IF cable.

4. Replace the ODU.If the fault is rectified after the ODU is replaced, it indicates that theODU is faulty.

Experience and Summaryl During the commissioning, ensure that the antenna is aligned properly, to prevent possible

incipient faults.l Periodically collect and analyze the data about the changes in the transmit power and receive

power so that you can detect and then rectify the incipient faults accordingly in time.

5.4 Troubleshooting Bit Errors in TDM ServicesWhen an NE reports an alarm or a performance event on the IF board, regenerator section (RS),multiplex section (MS), higher order path (HP), or lower order path (LP), there are bit errors inservices.

Fault PhenomenaThe IF bit errors refer to the bit errors that the Hybrid IF board detects through the self-definedoverhead byte in the microwave frame. The related alarms and performance events are asfollows:

l MW_BER_EXC

l MW_BER_SD

l IFBBE

l IFES

l IFSES

l IFCSES

l IFUAS

The RS bit errors refer to the bit errors that the line processing unit or the IF board that worksin SDH mode through the B1 overhead byte in the RS overhead. The related alarms andperformance events are as follows:




Issue 05 (2010-07-30)

l B1_EXC

l B1_SD

l RS_CROSSTR

l RSBBE

l RSES

l RSSES

l RSCSES

l RSUAS

NOTE

The IF board that works in PDH mode may also detect the previous RS bit error alarms and performanceevents. In this case, the IF board detects bit error alarms and performance events in the PDH microwaveframe through the self-defined B1 byte.

The MS bit errors refer to the bit errors that the line board detects through the B2 byte in the MSoverhead. The related alarms and performance events are as follows:

l B2_EXC

l B2_SD

l MS_CROSSTR

l MSBBE

l MSES

l MSSES

l MSCSES

l MSUAS

The HP bit errors refer to the bit errors that the line processing unit or the IF board that worksin SDH mode through the B3 byte in the HP overhead. The related alarms and performanceevents are as follows:

l B3_EXC

l B3_SD

l HP_CROSSTR

l HPBBE

l HPES

l HPSES

l HPCSES

l HPUAS

The LP bit errors refer to the bit errors that the tributary board or Hybrid IF board detects throughthe V5 byte in the VC-12 overhead. The related alarms and performance events are as follows:

l BIP_EXC

l BIP_SD

l LP_CROSSTR

l LPBBE



5-19

l LPES

l LPSES

l LPCSES

l LPUAS

Fault Causes

Table 5-6 Causes of bit errors


There are IF bit errors. l The radio link is faulty.Check whether the MW_FEC_UNCORor RPS_INDI alarm is reported. If yes, theradio link is faulty.

l The IF board at the local end or oppositeend is faulty.

There are RS bit errors. l The line is faulty.– The common causes for bit errors on the

optical line are as follows: the opticalfiber line, the optical power is abnormal,the fiber performance deteriorates, orthe fiber connector is not clean.

– In the case of bit errors on the radio link,check whether theMW_FEC_UNCOR or RPS_INDIalarm is reported. If yes, the radio linkis faulty.

l The line processing unit or IF board isfaulty.

l The clock unit is faulty.

l The quality of the clock over the networkdeclines.When the quality of the clock over thenetwork declines, a pointer justificationevent occurs.

There are not any RS bit errors but there areMS bit errors or HP bit errors.

l The line processing unit or IF board isfaulty.

l The quality of the clock over the networkdeclines.When the quality of the clock over thenetwork declines, a pointer justificationevent occurs.

l The working temperature of the lineprocessing unit or IF board is excessivelyhigh.




Issue 05 (2010-07-30)


There are only LP bit errors. l The tributary board is faulty.

l The cross-connect unit is faulty.

l The working temperature of the board isexcessively high.

l The working temperature of the cross-connect unit is excessively high.

l There is a power surge or an externalinterference source, or the equipment is notproperly grounded. (This cause does notneed to be considered during thetroubleshooting of a Hybrid IF board.)

Fault Locating Methods1. Analyze the equipment alarms and performance events that are related to bit errors.2. When there are many types of alarms and performance events on a service path, first analyze

RS bit errors, then MS bit errors, HP bit errors, and finally LP bit errors.3. When multiple paths have bit errors, first check whether the overlapping part of the service

paths is faulty.4. If you fail to locate the fault by analyzing the alarms and performance events, perform

loopback operations section by section.5. Replace the parts whose performance may deteriorate with new ones.



5-21


Figure 5-5 Procedure for troubleshooting bit errors

Start

Is there anequipment alarm?

No

Yes Clear the alarm

Is there an RS bit error alarm or a

performanceevent?

Yes

Troubleshoot RS bit errorson the IF board

No

Is there anMS/ HP alarm or

performanceevent?

Yes Troubleshoot MS/HP biterrors

No

Is there an LPalarm?

Yes Troubleshoot LP biterrors

Locate the fault by performingloopback operations section

by section

No

Proceed with the next stepIs the faultrectified?

End

Yes

No

Is there a pointerjustification event?

Yes Troubleshoot the pointerjustification

No

If thealarmingboard is

Troubleshoot RS bit errorson the SDH optical interface

board

IF board

SDH opticalinterface board

2

3

4

5

6

1




Issue 05 (2010-07-30)

Table 5-7 Description of the procedure for troubleshooting bit errors

CommentNo.

Description

1 Pay special attention to the following alarms:l TEMP_ALARM

l HARD_BAD

2 See 5.5 Troubleshooting Pointer Justifications.

3 The troubleshooting procedure is as follows:1. Check whether the line board reports the B1_EXC, B1_SD, or

RS_CROSSTR alarm.2. Interchange the Tx fiber core and the Rx fiber core at both ends of the

service path. If bit errors change after the exchange, it indicates that thefiber is faulty. Otherwise, the equipment at both ends of the service path isfaulty.

3. In the case of a fiber fault, check whether the fiber between the equipmentand the ODF and the section of the fiber that is led out of thetelecommunications room are pressed. In addition, check whether the fiberconnectors are clean.

4. In the case of faults at both ends of the service path, use a fiber jumper toloop back the optical ports. If the fault persists after the loopback, the lineboard may be faulty.

5. In the case of faults at both ends of the service path, you can also replacethe board where the line unit is located or interchange between the boardand another board of the same type that is working normally. If the alarmchanges after the exchange, it indicates that the board is faulty.

4 The troubleshooting procedure is as follows:1. Check whether the IF board reports the MW_FEC_UNCOR,

RPS_INDI, B1_EXC, B1_SD, or RS_CROSSTR alarm.2. If the MW_FEC_UNCOR and RPS_INDI alarms are reported, see 5.3

Troubleshooting the Radio Link and rectify the fault.3. If none of the alarms occurs, replace the IF board.

5 The troubleshooting procedure is as follows:1. Perform a loopback on the line board that reports the alarm.

If the fault persists after the loopback, replace the line board.If the fault is rectified after the loopback, replace the line board at thetransmit end.

2. If you fail to rectify the fault by replacing the line board, check whetherthere is a power surge or an external interference source or whether theequipment is not properly grounded.



5-23

CommentNo.

Description

6 The troubleshooting procedure is as follows:1. Replace the board where the services are configured based on how the

service paths that have bit errors overlap each other.2. If you fail to rectify the fault by replacing the board, check whether there

is a power surge or an external interference source or whether theequipment is not properly grounded.

Experience and Summaryl During the routine maintenance, check bit error performance events periodically and handle

them in time.

l To locate a fault, prefer the method of analyzing alarms and performance events to themethod of performing loopback operations and the method of replacing the parts.

5.5 Troubleshooting Pointer JustificationsWhen an NE reports a large number of justification events about the administrative unit (AU)pointer or the tributary unit (TU) pointer, there are pointer justification faults.

Fault Phenomena

When the position of the first byte of the VC-4 in the AU-4 payload changes, the AU pointermakes a justification accordingly. The performance events related to the AU pointer justificationare as follows:

l AUPJCHIGH

l AUPJCLOW

l AUPJCNEW

NOTE

The AU pointer justification is made 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 reframing process to terminatethe AU pointer justification. The terminating method is to transform the AU pointer justificationinto the TU pointer justification. The performance events related to the TU pointer justificationare as follows:

l TUPJCHIGH

l TUPJCLOW

l TUPJCNEW

NOTE

The TU pointer justification is made 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.




Issue 05 (2010-07-30)

Fault Causesl The clock sources or the clock source levels are configured incorrectly. As a result, there

are two clock sources on the same network or a timing loop occurs.l The fiber connections are incorrect. As a result, a timing loop occurs.

l The quality of the clock source declines, the clock unit is faulty, or there are other clock-related faults.

l The tributary board is faulty (only for the TU pointer justification).

Fault Locating MethodsWhen there are both AU pointer justifications and TU pointer justifications on a service path,first handle the AU pointer justifications and then the TU pointer justifications.

Fault Fault Locating Method

AU pointer justification 1. Analyze and clear clock alarms.2. Rectify the incorrect data configuration

and incorrect fiber connections.3. Change the clock configuration to locate

the station whose clock is asynchronouswith the entire network.

4. Replace the parts whose performance maydeteriorate with new ones.

TU pointer justification 1. Analyze and clear clock alarms.2. Rectify the incorrect data configuration

and incorrect fiber connections.3. Change the clock and service

configuration to locate the station whoseclock is asynchronous with the entirenetwork.

4. Replace the parts whose performance maydeteriorate with new ones.



5-25


Figure 5-6 Procedure for troubleshooting pointer justifications

Start

Is there a clock-relatedalarm?

No

YesClear the alarm

Incorrect fiberconnection?

YesReconnect the fibers

No

An AU pointerjustification event?

Yes

No

A TU pointerjustification event?

Yes

Proceed with thenext step Is the fault rectified?

End

Yes

No

Incorrectconfiguration?

Modify the dataconfiguration

No

Check the clockconfiguration

Yes

Check the fiberconnection

Locate the faulty boardLocate the NE whose clockis out of synchronization

Locate the faulty boardLocate the NE whose clockis out of synchronization

No

1

2

3

4

6

5

7




Issue 05 (2010-07-30)

Table 5-8 Description of the procedure for troubleshooting pointer justifications

CommentNo.

Description

1 Pay special attention to the following alarms:l TEMP_ALARM

l HARD_BAD

l LTI

l SYNC_C_LOS

l S1_SYN_CHANGE

l EXT_SYNC_LOS

2 Check the following points:l Check whether there are two clock reference sources on the entire network.

l Check whether a timing loop is generated.

3 Query ECC routes to check whether the fibers are connected correctly. Checkthe fiber connections in the east and west directions of the NE that reports thepointer justification event.

4 The troubleshooting procedure is as follows:1. Locate a VC-4 channel that reports an AU pointer justification event.2. Along the service source direction of the VC-4 channel, locate the source

NE of the entire VC-4 service (not the source NE of a timeslot in the VC-4).3. Set the clock of the source NE to the free-run mode. Set the other NEs to

trace the clock of the source NE along the direction of the VC-4 service.4. Along the clock tracing direction, locate the line board that is the first to

report the AU pointer justification of the VC-4 path.The clock of the remote NE to which the line board is connected isasynchronous with the reference clock. Hence, the line board on the remoteNE that receives the clock signal, the line board that sends the clock signalto the remote NE, and the clock unit of the remote NE, may be faulty.

5. Set the clock of the sink NE to the free-run mode. Set the other NEs to tracethe clock of the sink NE along the direction of the VC-4 service.

6. Along the clock tracing direction, locate the line board that is the first toreport the AU pointer justification of the VC-4 path.The clock of the remote NE to which the line board is connected isasynchronous with the reference clock. Hence, the line board on the NEthat receives the clock signal, the line board that sends the clock signal tothe NE, and the clock unit of the NE, may be faulty.

7. Compare the results and find out the common points.

5 Replace the possibly faulty boards.



5-27

CommentNo.

Description

6 The troubleshooting procedure is as follows:1. Modify the service configuration to ensure that the NE where the clock

reference source functions as the central NE and that the other NEs havethe E1 services of the central NE.

2. Along the clock tracing direction, locate the NE that is the first to reportthe TU pointer justification event.The clock of the NE is asynchronous with the reference clock. Hence, theline board on the NE that receives the clock signal, the line board that sendsthe clock signal to the NE, and the clock unit of the NE, may be faulty.

3. Modify the configuration data to ensure that all the NEs trace the clockalong the other direction.

4. Along the clock tracing direction, locate the NE that is the first to reportthe TU pointer justification event.The clock of the NE is asynchronous with the reference clock. Hence, theline board on the NE that receives the clock signal, the line board that sendsthe 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 to locating an AU pointer justification event.

7 Replace the possibly faulty boards. In the case of a TU pointer justificationevent, check whether the line board, the clock board, and the tributary boardare faulty.

Experience and Summary

On a properly synchronized network, there are few pointer justifications (less than six per dayon each port). Hence, monitoring the pointer of an SDH transmission system is an effective wayto check the synchronization status of the system.

5.6 Troubleshooting the Interconnection with SDHEquipment

An interconnection fault occurs when the NE fails in transmitting SDH services with other SDHequipment.

Fault Causesl The VC-12 numbering method of the OptiX equipment is different from the numbering

method of the equipment of certain vendors.

The OptiX equipment applies the timeslot numbering method. The numbering formula is:VC-12 number = TUG-3 number + (TUG-2 number - 1) x 3 + (TU-12 number - 1) x 21.This method is also called as the method of numbering by order.




Issue 05 (2010-07-30)

Certain equipment applies the line numbering method. The numbering formula is: VC-12number = (TUG-3 number - 1) x 21 + (TUG-2 number - 1) x 3 + TU-12 number. Thismethod is also called as the interleaved method.

l The overhead bytes at both ends are inconsistent.

l The indexes of the SDH interfaces do not meet the requirements.

NOTE

In the case of interconnection with ATM or Ethernet equipment, the common cause for an interconnectionfailure is that the service is not set to the VC-4 pass-through service and thus the overheads are processedin the terminating mode instead of the pass-through mode.

Fault Locating MethodsAnalyze the fault phenomena and alarms that are generated on the equipment. Check the possiblefault causes one after another.



5-29


Figure 5-7 Procedure for troubleshooting the interconnection with SDH equipment

Start

Interconnected with ATM/IP equipment?

No

Yes Set the interconnectedservice to be the VC-4 pass-

through service

An alarm related to theoverhead settings?

YesClear the alarm

No

Proceed with the next step Is the fault rectified?

End

Yes

No

Line numbering?Modify the data configuration.and use the line numbering

method to set the VC-12

No

Query the VC-12 numberingmethod of the interconnected

equipment

Yes

Test the indexes of interfaces

Do the interfaces meetrelevant standards?

Handle the faults of the localequipment

Troubleshoot the faults on theinterconnected equipment

No

Yes

2

1




Issue 05 (2010-07-30)

Table 5-9 Description of the procedure for troubleshooting the interconnection with SDHequipment

CommentNo.

Description

1 Pay special attention to the following alarms:l J0_MM

l HP_TIM

l LP_TIM

l HP_SLM

l LP_SLM

2 Common indexes of the optical interfaces are as follows:l Mean launched optical power

l Receiver sensitivity

l Overload optical power

l Permitted frequency deviation of the input interface

Experience and SummaryTo rectify an interconnection fault, you must be familiar with the characteristics of the interfaceson the interconnected equipment.

5.7 Troubleshooting the Interconnection with PDHEquipment

An interconnection fault occurs when the NE fails in transmitting PDH services with other PDHequipment.

Fault Causesl There is an impedance mismatch between interfaces.

l The equipment is not grounded properly.

l The cable performance deteriorates.

l The indexes of the PDH interfaces do not meet the requirements.

Fault Locating MethodsAnalyze the fault phenomena and alarms that are generated on the equipment. Check the possiblefault causes one after another.



5-31


Figure 5-8 Procedure for troubleshooting the interconnection with PDH equipment

Start

Is there animpedance mismatch?

Yes Replace the cable or thetributary board

Check the cables

Is in good conditions?No

Yes


End

Yes

No

Is the cable acoaxial cable?

No

Check the impedance ofthe interfaces

Yes

Adjust the cables

Test the indexes ofinterfaces

Do the interfacesmeet standards?

Troubleshoot the faultson the local equipment

Troubleshoot the faults onthe interconnected

equipment

Yes

No

Check the grounding

No

1

2

3

4




Issue 05 (2010-07-30)

Table 5-10 Description of the procedure for troubleshooting the interconnection with PDHequipment

CommentNo.

Description

1 Check the impedance of the E1 path. Ensure that the impedance of the E1path is consistent with the cable type.

2 Check the following points:l Check whether all the equipment and the DDF in the telecommunications

room are jointly grounded.l Check whether the shielding layers of the coaxial cable connectors on the

DDF are connected to the protection ground.l Check whether the shielding layers of coaxial cables are grounded in the

same manner.NOTE

Disconnect all the signal cables between the interconnecting equipment sets. Use amultimeter to measure the level between the shielding layers of the coaxial cables at thereceive and transmit ends of the PDH equipment and the level between the shieldinglayers of the coaxial cables at the receive and transmit ends of the equipment at theopposite end. If the potential difference is large (about 0.5 V), the fault may be causeddue to the improper grounding.

3 Check the following points:l Check whether the wires of the cable are correctly connected.

l Check whether the cable is broken or pressed.

l Check whether the cable signal is interfered (for example, when the trunkcable is bound with the power cable, the cable signal is interfered by thepower signal).NOTE

Checking the cables involves checking the cables from the DDF to the client sideand checking the cables from the DDF to the transmission equipment side.

4 Check the following indexes:l Input jitter tolerance

l Permitted frequency deviation of the input interface

l Output jitter

l Output frequency deviation

Experience and SummaryIn the case of interconnection with PDH equipment, improper grounding is the most commoncause for an interconnection failure.

5.8 Troubleshooting Ethernet Service FaultsAn Ethernet service fault may be the Ethernet service interruption or Ethernet servicedeterioration.



5-33

Prerequisite

The Ethernet service interruption indicates that the Ethernet service is completely interrupted.The Ethernet service deterioration indicates that the Ethernet service is abnormal. For example,the network access speed is low, the equipment delay is long, the packet loss occurs, or incorrectpackets exist in the received or transmitted data.

Fault Phenomena

The Ethernet service interruption indicates that the Ethernet service is completely interrupted.The Ethernet service deterioration indicates that the Ethernet service is abnormal. For example,the network access speed is low, the equipment delay is long, the packet loss occurs, or incorrectpackets exist in the received or transmitted data.

Table 5-11 Common faults of Ethernet services

Symptom Alarm Board

Ethernet services areinterrupted.

HARD_BAD,TEMP_ALARM,MWRG_BD_TYPE, orBD_STATUS

EM6F or EM6T

COMMUN_FAIL,LAG_DOWN

EM6F or EM6T

ETH_LOS,ETH_EFM_LOOPBACK,or LOOP_ALM

EM6F or EM6T

LASER_MOD_ERR EM6F

Ethernet services aredegraded.

HARD_BAD orTEMP_ALARM

EM6F or EM6T

FLOW_OVER orLAG_MEMBER_DOWN

EM6F or EM6T

AM_DOWNSHIFT IFU2 or IFX2

Fault Causesl The possible human factors are as follows:

– An Ethernet board loopback or a transmission line loopback occurs.

– The parameter settings of the Ethernet ports, such as the port enabled state, workingmode, and flow control, are different from the parameter settings of the Ethernet portson the interconnected equipment.

– The service configuration is incorrect.

l The equipment at the local end is faulty.

l The line board is faulty or has bit errors.




Issue 05 (2010-07-30)

l When the AM function is enabled, the Ethernet service bandwidth decreases due to thedownward AM switch.

l The interconnected equipment is faulty.

l The network cable is faulty.

l The external electromagnetic interference is severe.

Fault Locating Methods1. Rectify the human-caused faults such as a loopback and a data configuration error.2. Locate the fault cause according to the equipment alarms.3. Locate the fault cause according to the RMON performance events and alarms.


Figure 5-9 Procedure for troubleshooting Ethernet service faults

Any bnormal RMONperformance events?

Clear the alarm

5

No

YesAn equipment alarm oralarm on the radio link?

An Ethernet alarm?Yes Query the port and service traffic

and analyze the fault causes

No

Fault on theopposite equipment?

Yes Troubleshoot the fault according tothe flow of handling RMON

performance events

Yes Troubleshoot faults on theopposite equipment

No

3

2

Troubleshoot equipmentfaults by performing

loopbacks section bysection or replacing boards

Proceedwith thenext step


End

Yes

No

A loop formed by theE-LAN service trails?

No

No

YesRelease the loop

Start

Incorrect operation?1

Cancel this operation

No

Yes

Clear the alarm

4

5

4

3

2

1



5-35

Table 5-12 Description of the procedure for troubleshooting Ethernet service faults

CommentNo.

Description

1 Check the following points:l Whether a loopback is set for the Ethernet port

l Whether a loopback is set for the transmission line

l Whether the parameter settings of the Ethernet port, such as the portenabled state, working mode, and flow control, are the same as theparameter settings of the Ethernet port on the interconnected equipment

l Check whether the Ethernet protocol and the Ethernet service configuration(especially the attributes of the Ethernet port) are correct.

2 Pay special attention to the following equipment alarms:l POWER_ALM

l FAN_FAIL

l HARD_BAD

l BD_STATUS

l NESF_LOST

l TEMP_ALARM

l RADIO_RSL_HIGH

l RADIO_RSL_LOW

l RADIO_TSL_HIGH

l RADIO_TSL_LOW

l IF_INPWR_ABN

l AM_DOWNSHIFT

Pay special attention to the following line alarms:l MW_LIM

l MW_LOF

l MW_BER_EXC

l MW_BER_SD

l MW_RDI

l MW_FEC_UNCOR

3 Pay special attention to the following alarms:l ETH_LOS

l LAG_DOWN

l LAG_MEMBER_DOWN

l FLOW_OVER

4 Querying the AM Status, and check whether sufficient service bandwidth isavailable in the current microwave working mode. If not, replan the servicedata of the site.




Issue 05 (2010-07-30)

CommentNo.

Description

5 If the ETH_EFM_LOOPBACK alarm is reported after the configuring theAdvanced Attributes of Ethernet Interfaces operation is performed, itindicates that the network to which Ethernet ports are connected has loops.

6 For RMON performance events, see the Feature Description.

Figure 5-10 Procedure for troubleshooting an RMON performance event

Is it a MTU settingproblem?

Yes Modify the MTUvalue

No

Proceed withthe next step


End

Yes

No

No

Is the test passed?

No

Yes

Use a meter to perform the test

Rectify the fault of theinterconnected equipment

Rectify the equipment fault byloopback section by section or

replacing the board

5

Are broadcast packetsexcessive?

No

Yes Handle the problem onexcessive broadcast

packets

4

Start

Rectify the fault of line biterrors

No

YesIs there any FCS error?

Is there any collisionor fragment?

Yes Check the working modeof the port

2

3

View the statistics groupperformance on an Ethernet port

1



5-37

Table 5-13 Description of the procedure for troubleshooting an RMON performance event

CommentNo.

Description

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

2 The troubleshooting procedure is as follows:l Check the Ethernet cable. If the Ethernet cable is not qualified, replace it

with a new one.l Change the Ethernet port that accesses the services on the Ethernet board.

If the new port does not have the RMON performance of an FCS error, itindicates that the hardware of the original port is faulty. Otherwise, thehardware of the Ethernet port on the equipment at the opposite end is faulty.

3 Check the following points:l Whether the port operating rates on the equipment at both ends are the same

l Whether the working modes (full duplex or half duplex) of the Ethernetport on the equipment at both ends are the same

l Whether the Ethernet port is set to auto-negotiation mode at one end andthe Ethernet port is set to full duplex mode at the opposite end (When theEthernet port is set to auto-negotiation mode at one end, the Ethernet portmust not be set to full duplex mode at the opposite end.)

4 Check for the cause for excessive broadcast packets (for example, you haveset the loopback for the Ethernet interface board or set the VB filteringtable incorrectly) and solve the problem. If the problem is caused on theequipment at the opposite end, set the threshold of broadcast packetsuppression for an Ethernet port to reduce broadcast packets.

5 Test the MTU of the network by using a test meter. The maximum framelength that is set for a port should be longer than the MTU of the network.

Experience and Summary

To troubleshoot an Ethernet service fault, you must be familiar with the characteristics, workingmode, and configured protocols of interfaces on the Ethernet equipment.

5.9 Troubleshooting Orderwire FaultsIf orderwire calls cannot get through when services are normal, there is an orderwire fault.

Fault Causesl The phone set is set incorrectly.

l The phone line is connected incorrectly.

l The orderwire is configured incorrectly.

l The orderwire unit is faulty.




Issue 05 (2010-07-30)

l The system control unit is faulty.

l The line unit or radio link is faulty.

Fault Locating Methodsl Check whether the phone set is set correctly, whether the phone line is connected correctly,

and whether the orderwire is configured correctly.l Replace the possibly faulty board to locate the fault.


Figure 5-11 Procedure for troubleshooting orderwire faults

Start

Is the phonecorrectly set?

NoModify the phone setting

Check the orderwireconfiguration

Is the configurationcorrect?

No

Yes


End

Yes

No

Is the phone linecorrectly connected?

Yes

Check the phone setting

No

Modify the configuration

Replace the possibly faultyboard

Reconnect the phone line

Yes

3

2

1



5-39

Table 5-14 Description of the procedure for troubleshooting orderwire faults

CommentNo.

Description

1 Check the following points:l Check whether the ring current switch "RING" on the phone set is set to

"ON".l Check whether the dialing mode switch is set to "T", namely, the dual tone

multi-frequency mode.l An orderwire phone set should be in on-hook state when it is not in

communication, and the upper-right red indicator in the front view of theorderwire phone set should be off.If the red indicator is on, it indicates that the phone set is in off-hook state.Press the "TALK" button in the front of phone set to hook it up. In certainoccasions, the maintenance personnel press the "TALK" button is pressedby mistake. As a result, the phone set stay in off-hook state all the time andthe orderwire call from the other NEs cannot get through.

2 Check the following points:l Whether all orderwire phone numbers on a subnet are of the same length

l Whether all orderwire phone numbers on a subnet are unique

l Whether the overhead bytes of all the NEs on a subnet are the same

l Whether the orderwire port is set correctly

3 Replace the boards where the orderwire unit, system control unit, andline unit are located to locate the fault.

Experience and SummaryTo troubleshoot orderwire faults, you must check the orderwire phone periodically.




Issue 05 (2010-07-30)

6 Part Replacement

About This Chapter

Part replacement is a method frequently used to locate faults. The replacement operation variesaccording to the specific part type.

Background Information

Table 6-1 Part replacement description

Part Name Operation Tool

SL1D 6.3 Replacing the SDH OpticalInterface Board

l ESD wrist strapl Screwdriverl U2000SP3D and SP3S 6.4 Replacing the PDH Interface

Board

EM6T andEM6F

6.5 Replacing the EthernetInterface Board

IF1, IFU2, andIFX2

6.6 Replacing the IF Board

CF card 6.7 Replacing the CF Card

CST and CSH 6.8 Replacing the System Control,Switch&Clock Board

AUX 6.9 Replacing the AuxiliaryBoard

FAN 6.10 Replacing the Fan Tray

PIU 6.11 Replacing the Power Board

OptiX RTN 950Maintenance Guide (U2000) 6 Part Replacement


6-1

Part Name Operation Tool

ODU 6.13 Replacing the ODU l Ejector lever (torque wrench)

l U2000

l Silicon

l Waterproof adhesive tape

Replacing theIF cable

6.14 Replacing the IF Cable l Ejector lever

l Electro-technical knife

l File

l Installation parts and accessoriesof the connector

l IF cable


6 Part ReplacementOptiX RTN 950



Issue 05 (2010-07-30)

6.1 Removing a BoardRemoving a board is a basic operation for replacing a board.

ProcedureStep 1 Insert one end of the ESD wrist strap into the ESD connector on the cabinet. Wear the ESD wrist

strap.

Step 2 Optional: If cables are connected to the board, make labels for the cables and then remove thecables.

Step 3 Remove the board.l Remove the fan tray assembly.

1

2

l Remove the other boards.

1. Loosen the screws on the panel of the board.

Figure 6-1 Removing a board (1)



6-3

2. Hold the left and right ejector levers with hands. Push them outwards to disengage the

board from the backplane.


NOTE

As shown in Figure 6-3, there is a tack switches on each ejector lever of the System controlSwitch&Clock board. To remove the System control Switch&Clock board, you need to pushthe tack switches when pulling the ejector levers outward.

Figure 6-3 Removing the System control Switch&Clock board

3. Pull out the board gently along the slot guide rail.





Issue 05 (2010-07-30)

CAUTIONRemove the board slowly to prevent the components on the boards from colliding.

Step 4 Put the removed board into the antistatic box or bag.

----End

6.2 Inserting a BoardInserting a board is a basic operation for replacing a board.

Procedure

Step 1 Insert one end of the ESD wrist strap into the ESD connector on the cabinet. Wear the ESD wriststrap.

Step 2 Insert the board.

l Insert the fan tray assembly.

1

2

l Insert the other boards.

1. Hold the ejector levers on the panel with both hands. Push them outwards so that theangle between the ejector lever and the panel is about 45 degrees.

2. Push the board gently along the slot guide rail until the board cannot slide further.



6-5

Figure 6-5 Inserting a board (1)

CAUTIONInsert the board slowly to prevent the components on the boards from colliding.

3. Press the two ejector levers inward with force.


4. Tighten screws on the panel.




Issue 05 (2010-07-30)


Step 3 Optional: If cables are connected to the board, recover the original cable connections accordingto the labels that are made previously.

----End

6.3 Replacing the SDH Optical Interface BoardWhen the SDH optical interface board is replaced, the unprotected services on the board areinterrupted.

Prerequisitel You must know the impact of board replacement.

l You must know the specific position of the board to be replaced.

l You must know the service protection and protection channels of the board to be replaced.

l The spare SDH optical interface board must be available, and the version and type of thespare board must be the same as the version and type of the board to be replaced. You canquery the board manufacturing information to obtain the version of the board to bereplaced.


l ESD wrist strap

l Screwdriver

l U2000

Procedure

Step 1 Query the current alarms of the board.

Step 2 Optional: If the services on the board are configured with SNCP, ensure that the services arealready switched to the protection channel.

1. Query the SNCP protection group.



6-7

2. Perform the forced switching, if the port on the board functions as the current workingchannel, the current protection channel is not on the board, and the state of the currentprotection channel is normal or SD.

Step 3 Optional: If the services on the board are configured with linear MSP, ensure that the servicesare already switched to the protection channel.

1. Query the linear MSP group.

2. Perform the forced switching, if the port on the board functions as the current workingchannel, the current protection channel is not on the board, and the state of the currentprotection channel is normal or SD.

Step 4 Remove the board.

Step 5 Check whether the version and SFP type of the spare board are the same as the version and SFPtype of the board to be replaced.


Step 7 After the board starts to work, check the STAT indicator on the board. The STAT indicatorshould be on and green.

Step 8 Query the current alarms of the board.There should be no new alarms on the board.

Step 9 Optional: If the forced switching has been performed on the board, release the forced switching.

Step 10 Optional: If the linear MSP switching has been performed for the services, release the forcedswitching.

----End

6.4 Replacing the PDH Interface BoardWhen the PDH interface board is replaced, the services on the board are interrupted.




l The spare board must be made available, and the version and type of the spare board mustbe the same as those of the board to be replaced. You can query the board manufacturinginformation to obtain the version of the board to be replaced.


l ESD wrist strap

l Screwdriver

l U2000




Issue 05 (2010-07-30)

Procedure



Step 3 Check and ensure that the version and type of the spare board are the same as the version andtype of the board to be replaced.


Step 5 After the board starts to work, check the indicators on the board. The STAT indicator should beon and green.


----End

6.5 Replacing the Ethernet Interface BoardWhen the Ethernet interface board is replaced, the unprotected services on the board areinterrupted.





Tools, Equipment, and Materialsl ESD wrist strap

l Screwdriver

l U2000

Procedure



Step 3 Check and ensure that the board version and the model of the SFP module on the spare boardare the same as the board version and the model of the SFP module on the board to be replaced.






6-9

There should be no new alarms on the board.

----End

6.6 Replacing the IF BoardWhen the IF board is replaced, the unprotected services on the board are interrupted.




l The spare board must be available, and the version and type of the spare board must be thesame as the version and type of the board to be replaced. You can query the boardmanufacturing information to obtain the version of the board to be replaced.


l Screwdriver

l U2000

Procedure


Step 2 Optional: If the services on the board are configured with SNCP, ensure that the services arealready switched to the protection channel.

1. Query the SNCP protection group.

2. If the port on the board functions as the current working channel, the current protectionchannel is not on the board, perform the forced switching.

Step 3 Optional: If the services on the radio link are configured with 1+1 protection, switch the serviceto the protection IF board.

1. Query the IF 1+1 protection group.

2. If the board functions as the current working board, perform the forced switching.

Step 4 Optional: If the services on the radio link are configured with N+1 protection, ensure that theservices are already switched to the protection IF board.

1. Query the IF N+1 protection group.

2. If the board functions as the current working board, perform the forced switching.

Step 5 If the IF board is configured with the XPIC function, see Setting the State of an ODU Transmitterand mute the ODU at the opposite end.

Step 6 Turn off the ODU-PWR switch on the front panel of the IF board to be replaced.




Issue 05 (2010-07-30)

CAUTIONTo turn off the ODU-PWR switch, you need to pull the switch lever outwards slightly and thenset the switch to the "O" position.



Step 9 Ensure that the ODU-PWR switch on the front panel of the spare IF board is turned off.



Step 12 Turn on the ODU-PWR switch on the front panel of the IF board.

CAUTIONTo turn on the ODU-PWR switch, you need to pull the switch lever outwards slightly and thenset the switch to the "I" position.


Step 14 Optional: If the forced SNCP switching has been performed for the services, release the forcedswitching.

Step 15 Optional: If the forced protection switching has been performed for the radio link, release theforced switching.

Step 16 If the IF board is configured with the XPIC function, see Setting the State of an ODU Transmitterand unmute the ODU at the opposite end.

----End

6.7 Replacing the CF CardIf the NE is configured with only one System control Switch&Clock board, all the services areinterrupted during the replacement of the CF card.

Prerequisitel You must be aware of the impact of CF card replacement.

l You must know the specific position of the CF card to be replaced.

l You must be a user with "NE maintainer" authority or higher.



6-11


l ESD wrist strap

l U2000

Procedure


Step 2 Optional: If the board is configured with 1+1 protection, ensure that the services are switchedfrom the current working board to the protection board.1. See 8.16 Switching the System Control Unit and the Cross-Connect Unit, and ensure

that the current working board functions as the protection board.2. If the board functions as the current working board, perform the manual switching.


Step 4 Remove the CF card according to the illustration in the following figure.

Step 5 Check the spare CF card.

Step 6 Install the spare CF card according to the illustration in the following figure.


Step 8 After the board starts to work, observe the indicators on the board. The STAT indicator shouldbe on and green.

Step 9 Query the current alarms of the board.There should be no new alarms.




Issue 05 (2010-07-30)

Step 10 Optional: If the manual switching has been performed on the board, release the manualswitching.

----End

6.8 Replacing the System Control, Switch&Clock BoardAll the services are interrupted during the period of replacing the System control Switch&Clockboard, if the NE is configured with only one System control Switch&Clock board.

Prerequisitel You must be aware of the impact of board replacement.



l The spare board must be made available, and the version and type of the spare board mustbe the same as those of the board to be replaced. You can query the board manufacturinginformation to learn about the version of the board to be replaced.

Impact on SystemIf no protection board is available, the replacement of the System control Switch&Clock boardresults in service interruption.


l Screwdriver

l U2000

ContextNOTE

After the NE database is restored successfully, a cold reset is automatically performed on the NE.

Procedure


Step 2 Replace the System control Switch&Clock board.

Option Description

If... Then...



6-13

Option Description

One System control Switch&Clock board isconfigured

1. Notify the onsite maintenance personnel toremove the board.

2. Check and ensure that the version and typeof the spare board (including the patchversion) are correct.NOTE

If the spare board and the board to be replacedhave different patch versions, contact Huaweiengineers for loading correct patches.

3. Remove the CF card from the original boardand then install the CF card to the spareboard. For details about how to install theCF card, see 6.7 Replacing the CF Card.NOTE

After the NE starts up normally, the STATindicator on the board is green, and the PROGindicator on the board is off.

4. Insert the spare board into the chassis.5. Press and hold the CF RCV button on the

board for 8 seconds so that the boardautomatically restores the NE databases,system parameters, software packages, andNE logs from the CF card.NOTE

l In the process of restoring the NE database,the PROG indicator on the board blinks greenfor about 20 minutes.

l If the database restoration is successful, theNE resets automatically. After the NE resetssuccessfully, the STAT indicator is on andgreen and the PROG indicator is off.

l If the database restoration fails, the NE doesnot reset, and the PROG is off. In this case,contact Huawei technical support engineersfor rectifying the fault.




Issue 05 (2010-07-30)

Option Description

Two System control Switch&Clock boardsare configured

1. Before replacing the main system controlboard, switch the system control unit andcross-connect unit to the protection board.For details, see 8.16 Switching the SystemControl Unit and the Cross-ConnectUnit.NOTE

Replacing the standby system control boarddoes not need to switch the system control unitand cross-connect unit to the protection board.

2. Remove the board to be replaced.3. Check whether the version and type of the

spare board are the same as the version andtype of the board to be replaced.

4. Insert the spare board.5. Wait for about 10 minutes to complete the

backup of the data on the main and standbysystem control units.

6. Switch the system control unit and cross-connect unit to the working board. Fordetails, see 8.16 Switching the SystemControl Unit and the Cross-ConnectUnit.

Step 3 Query the current alarms of the board. There should be no new alarms.

----End

6.9 Replacing the Auxiliary BoardWhen the auxiliary board is replaced, the services on the auxiliary board are interrupted.





l ESD wrist strap

l Screwdriver

l U2000



6-15

Procedure






Step 6 Query the current alarms of the board.There should be no new alarms on the auxiliary board.

----End

6.10 Replacing the Fan TrayThe IDU cannot perform air cooling in the process of replacing the fan tray. Therefore, you needto replace the fan tray quickly.



l The spare board must be made available, and the version and type of the spare board mustbe the same as those of the board to be replaced. You can query the board manufacturinginformation to learn about the version of the board to be replaced.

l You must be an NM user with NE maintainer authority or higher.


l Screwdriver

l U2000

Precautions

WARNINGDo not touch the blades until the fan has stopped rotating.

Procedure





Issue 05 (2010-07-30)

Step 2 Move the cables away from the front panel of the fan tray assembly.





Step 7 Query the current alarms of the board.There should be no new alarms.

----End

6.11 Replacing the Power BoardIf another power board works normally during the replacement period, the services at the IDUare not affected.



l The spare chassis must be made available, and the version and type of the spare chassismust be the same as the version and type of the board to be replaced. The chassis isconfigured with the power board and the fan tray. You can query the boardmanufacturing information to learn about the version of the board to be replaced.


l ESD wrist strap

l Screwdriver

l U2000

Precautions

WARNINGBefore replacing the board, you must turn off the power switch of the PDU. Do not connect theinterface to the power plug. After inserting the PIU properly, insert the power plug, and thenturn on the power switch of the PDU.

Procedure




6-17

Step 2 Notify the onsite maintenance personnel to turn off the output power switch on the equipment.

Step 3 Remove the cables connected to the board.

Step 4 Remove the power board gently and horizontally along the guide rail.


Step 6 Insert the spare board steadily along the guide rail.

Step 7 Reconnect the cables between the board and the power supply equipment.

Step 8 Notify the onsite maintenance personnel to turn on the output power switch on the equipment.


----End

6.12 Replacing the SFPWhen the small form pluggable (SFP) is replaced, the unprotected services on the optical/electrical port are interrupted.

Prerequisitel You must know the impact of SFP replacement.

l You must know the specific position of the SFP to be replaced.

l You must know the service protection and protection channels of the SFP to be replaced.

l The spare SFP must be available, and the version and type of the spare SFP must be thesame as the version and type of the SFP to be replaced. You can query the boardmanufacturing information to obtain the version of the SFP to be replaced.

ContextNOTE

The SL1D can be equipped with the SFP to provide 2xSTM-1 optical interfaces. The EM6F can be equippedwith the SFP to provide 2xGE optical interfaces or 2xGE electrical interfaces.

Tools, Equipment and Materialsl ESD wrist strap

l Screwdriver

l U2000

Procedure


Step 2 Optional: If SNCP is configured for services at the optical interface, ensure that the servicesare already switched to the protection channel.1. Query the status of the SNCP group.




Issue 05 (2010-07-30)

2. If the port on the local board functions as the working channel, the protection channel doesnot involve the local board, and the protection channel is in the normal or SD state, performforced switching.

Step 3 Optional: If linear MSP is configured for services at the optical interface, ensure that the servicesare already switched to the protection channel.1. Query the status of the linear MSP group.2. If the port on the local board functions as the working channel, the protection channel does

not involve the local board, and the protection channel is in the normal or SD state, performforced switching.

Step 4 Record the cable connections of the SFP, and then disconnect cables.

Step 5 Check the types of the spare SFP and the SFP to be replaced.

Step 6 Reconnect cables based on the record.


Step 8 Optional: If the forced switching has been performed on the board, release the forced switching.

Step 9 Optional: If the linear MSP switching has been performed for the services, release the forcedswitching.

----End

6.13 Replacing the ODUWhen the ODU is replaced, the unprotected services on the ODU are interrupted.

Prerequisitel You must know the impact of ODU replacement.

l You must know the specific positions of the ODU to be replaced and the IF board connectedto the ODU.

l The spare ODU must be at hand, whose type must be the same as the type of the ODU tobe replaced.

Tools, Equipment, and Materialsl Ejector lever (torque spanner)

l U2000

l Silicon


PrecautionsBefore you replace an ODU that is installed on the coupler, power off the ODU to be replaced,but do not power off or mute the other ODU. Otherwise, the services may be affected. Theinterface of the coupler ejects little RF radiation, thus meeting the safety standards for microwaveradiation.



6-19

Procedure

Step 1 Query the current alarms on the ODU and then record the results.

Step 2 Turn off the ODU-PWR switch on the front panel of the IF board.

Step 3 Remove the IF cable and the PGND cable from the ODU.

Step 4 Remove the ODU.

Option Description

If... Then...

You need to remove the ODU with awaveguide interface

Loosen the four latches of the ODU anddisconnect the ODU from the antenna, thehybrid coupler, or ODU adapter.

You need to remove the ODU with acoaxial interface

Remove the ODU from the post.

You need to remove the RTN XMC ODU Loosen the captive screws on the ODU anddisconnect the ODU from the antenna, thehybrid coupler, or ODU adapter.

Step 5 Ensure the type of the spare ODU is the same as the type of the ODU to be replaced.

Step 6 Install the ODU.

Option Description

If... Then...

You need to install a new ODU with awaveguide interface

See the RTN 600 ODU Quick InstallationGuide.

You need to install a new ODU with acoaxial interface

See the RTN 600 ODU Quick InstallationGuide.

You need to install a new RTN XMC ODU See the RTN XMC ODU Installation Guide.

Step 7 Connect the PGND cable and the IF cable to the ODU.

Step 8 Waterproof the IF interface on the ODU.


Step 10 After the ODU starts to work, check the ODU indicator and LINK indicator on the IF board.The ODU indicator and LINK indicator should be on and green.

Step 11 Query the current alarms of the ODU. There should be no new alarms on the ODU.

----End

6.14 Replacing the IF CableWhen the IF cable is replaced, the unprotected services on the IF cable are interrupted.




Issue 05 (2010-07-30)

Prerequisitel You must know the impact of IF cable replacement.

l You must know the specific positions of the IF cable to be replaced and the IF boardconnected to the IF jumper.

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

Tools, Equipment, and Materialsl Multimeter

l Ejector lever

l Electro-technical knife

l File

l Installation parts and accessories of the connector

l IF cable


Procedure

Step 1 Query and record the current alarm of the IDU.

Step 2 Turn off the ODU-PWR switch on the front panel of the IF board.

Step 3 Disconnect the IF cable from the IF jumper and from the ODU.

Step 4 Use a multimeter to test the connectivity of the IF cable to determine whether you need to makenew connectors for the IF cable or replace the IF cable with a new one.

If... Then...

You need to make new connectors for theIF cable

See the Installation Reference and make newconnectors for the IF cable.

You need to replace the IF cable with a newone

Replace the IF cable with a new one.

Step 5 Connect the IF cable to the IF jumper and to the ODU.

Step 6 Waterproof the connectors at the two ends of the IF cable with the waterproof adhesive tape.


Step 8 After the ODU starts to work, check the ODU and LINK indicators on the IF board.The ODU indicator and LINK indicator should be on and green.

Step 9 Query the current alarms of the IDU.There should be no new alarms on the IDU.

----End



6-21

7 Database Backup and Restoration

About This Chapter

The OptiX RTN 950 supports database backup and restoration through the NMS.

7.1 NE DatabaseAn NE database stores the communication data, security data, alarm data, performance data, andconfiguration data of an NE in a certain structure to facilitate the relevant query and modification,hence ensuring that the data can be restored after the NE is reset.

7.2 Backing Up the Database ManuallyThe NE configuration data is stored in the database of an NE. To prevent the database frombeing damaged due to certain risky operations such as replacing a faulty system control, cross-connect, and timing board or upgrading the software, you need to manually back up the databaseon a regular basis and before performing any risk operation.

7.3 Setting the Database Backup PolicyYou can set the policy of backing up a database to realize the function of periodically backingup the database.

7.4 Restoring the DatabaseIf the database is damaged, you can restore the NE database by using the database files that aresaved previously.

OptiX RTN 950Maintenance Guide (U2000) 7 Database Backup and Restoration


7-1

7.1 NE DatabaseAn NE database stores the communication data, security data, alarm data, performance data, andconfiguration data of an NE in a certain structure to facilitate the relevant query and modification,hence ensuring that the data can be restored after the NE is reset.

An NE database includes the following types:

l Memory database (MDB)The data in the MDB varies according to the configuration and is lost when the systemcontrol unit is reset or when the NE is powered off.

l Dynamic random database (DRDB)The DRDB automatically stores the data that is checked successfully. The DRDB is residentin the reserved memory. Hence, the data in the DRDB is not lost when a warm reset isperformed on the system control unit. The data, however, is lost when a cold reset isperformed on the system control unit or when the NE is powered off.

l Flash database (FDB)The FDB includes FDB0 and FDB1. The FDB is resident in the flash memory on the board.Hence, the data in the FDB is permanently stored.

After being delivered to the system control unit, the NE configuration data is stored in the MDB.After checking the NE configuration data successfully, the system control unit automaticallycopies the data from the MDB to the DRDB and delivers the board configuration data generatedafter successful check to the relevant board.

The NE supports two backup schemes:l Five minutes after the data configuration on the NE is completed, the NE backs up the

DRDB database into the FDB0 and FDB1 databases of the flash memory.l The NE backs up the DRDB database into the FDB0 and FDB1 databases of the flash

memory at an interval of 30 minutes.After the NE is restarted because of power-off, the system control unit checks whether theconfiguration data in the DRDB is available. If yes, the system control unit restores the data. Ifthe configuration data in the DRDB is damaged, the system control unit restores the data fromFDB0 or FDB1.

The system control, switching and timing board on the OptiX RTN 950 is installed with a CFcard. When automatically copying data to the FDB, the DRDB in the system control unit copiesthe data to the database on the CF card accordingly.

On the CF card, NE databases, system parameters (including NE-IP, NE-ID, and subnet mask),software packages, and NE logs are stored. After the CRV button on the system control,switching and timing board is pressed and held for eight seconds, the data stored on the CF cardis loaded to the board. To synchronize the data on the CF card with the NE databases, systemparameters, and NE logs on the system control, switching and timing board, the regular backupfunction needs to be enabled.

NOTE

The software packages on the CF card are updated with those on the system control, switching and timing boardduring package diffusion. Therefore, no automatic or manual operation is performed to synchronize the softwarepackages. When the system control, switching and timing board and the CF card have different software packagesor data, the SWDL_PKGVER_MM alarm is reported.

7 Database Backup and RestorationOptiX RTN 950



Issue 05 (2010-07-30)

7.2 Backing Up the Database ManuallyThe NE configuration data is stored in the database of an NE. To prevent the database frombeing damaged due to certain risky operations such as replacing a faulty system control, cross-connect, and timing board or upgrading the software, you need to manually back up the databaseon a regular basis and before performing any risk operation.

Prerequisitel You must be an NM user with NE operator authority or higher.

l You must log in to the NE.


ProcedureStep 1 On the NMS, choose Administration > NE Software Management > NE Data Backup/

Restoration from the Main Menu.

Step 2 In NE View, click Search.

Step 3 In the Search Device(s) dialog box, set the search conditions and search for the NE that requiresdatabase backup.

Step 4 Close the Search Device(s) dialog box.

Step 5 Click Backup.NOTE

You can select multiple NEs to back up the data at one time.

Step 6 Set the data backup path to NMS Server or NMS Client according to the requirements.NOTE

If NMS Client is selected, you can click to set the path in which the client data is stored.

Step 7 Click Start to start backing up the NE data. In NE View, Operation Status indicates the progressof backing up the data. After the data backup is successful, Operation Status displays a message,indicating that the operation is successful.

----End

7.3 Setting the Database Backup PolicyYou can set the policy of backing up a database to realize the function of periodically backingup the database.

7.3.1 Setting the Default Backup PolicyThrough this task, you can set the default backup policy for all the NEs on the network.

7.3.2 Setting the User-Defined Backup Policy



7-3

Through this task, you can set the backup policy for a specific NE.

7.3.3 Executing the Backup Policy of the DeviceThrough this task, you can set the backup policy of a device to the running state.

7.3.4 Suspending the Backup Policy of the DeviceThrough this task, you can set the backup policy of a device to the suspended state.

7.3.1 Setting the Default Backup PolicyThrough this task, you can set the default backup policy for all the NEs on the network.




ContextThe backup policy refers to the method of backing up the data stored in the flash memory ofNEs to the databases of the NMS.

Procedure

Step 1 Choose Administration > NE Software Management > Default Policy from the Main Menu.Then, the Default Policy dialog box is displayed.

Step 2 Click Backup Policy, and set Period, Day, Time, and Policy Status.NOTE

l If Policy Status is set to Running, the NMS performs the backup operation within the specified period,day, and time.

l If Policy Status is set to Suspended, the backup policy is still in the Paused state although the policyperiod reaches the specified period, day, and time.

Step 3 Click OK, and close the dialog box.

----End

7.3.2 Setting the User-Defined Backup PolicyThrough this task, you can set the backup policy for a specific NE.







Issue 05 (2010-07-30)

Procedure

Step 1 Choose Administration > NE Software Management > User-Defined Policy from the MainMenu.Then, the User-Defined Policy dialog box is displayed.

Step 2 In the NE Tree, set NE type and Device Version.In NE View, the version, name, and IP address of the selected NE are displayed.

Step 3 Optional: Click to import the IP addresses of the NEs.The imported IP addresses of the NEs are displayed in Device View.

Step 4 Optional: Click to export the IP address information of the NEs.The IP addresses of the selected NEs are stored in the specified location.

Step 5 In NE Table, select one or more NEs.

Step 6 Click Next.Then, the User-Defined Policy dialog box is displayed.

Step 7 Set Period, Day, Time, and Policy Status.

NOTE

l If Policy Status is set to Running, the NMS performs the backup operation within the specified period,day, and time.

l If Policy Status is set to Suspended, the backup policy is still in the Paused state although the policyperiod reaches the specified period, day, and time.

Step 8 Click Finish.

Step 9 Close the prompt dialog box.

----End

7.3.3 Executing the Backup Policy of the DeviceThrough this task, you can set the backup policy of a device to the running state.



Procedure

Step 1 On the NMS, choose Administration > NE Software Management > NE Data Backup/Restoration from the Main Menu.The NE Data Backup/Restoration window is displayed.

Step 2 In NE View, click Search.



7-5

Then, the Search Device(s) dialog box is displayed.

Step 3 Set the search conditions to search for the NEs that need to execute the backup policy.


Step 5 Select and right-click the NE. Choose Backup Policy > Run Policy from the shortcut menu.


----End

7.3.4 Suspending the Backup Policy of the DeviceThrough this task, you can set the backup policy of a device to the suspended state.

Prerequisite

You must be an NM user with NE operator authority or higher.


U2000

Procedure


Step 2 In NE View, click Search.Then, the Search Device(s) dialog box is displayed.

Step 3 Set the search conditions to search for the NEs that need to execute the backup policy.


Step 5 Select and right-click the NE. Choose Backup Policy > Suspend Policy from the shortcut menu.


----End

7.4 Restoring the DatabaseIf the database is damaged, you can restore the NE database by using the database files that aresaved previously.


l The data to be restored must be backed up.





Issue 05 (2010-07-30)


Procedure


Step 2 In NE View, click Search.Then, the Search Device(s) dialog box is displayed.

Step 3 Set the search conditions to search for the NEs that need to restore databases.


Step 5 Select the NE whose data needs to be recovered, and click Recover.Then, the Recover dialog box is displayed.

Step 6 Select Browse in File Name.Then, the Select File dialog box is displayed.

Step 7 Select files from NMS Server or NMS Client, and then choose the files to be recovered. ClickOK.

Step 8 In the Recover dialog box, click Start.

Step 9 Click Yes in the prompt dialog box.The system starts recovering the selected data files on the specified NE.In the NE list of NE View, Operation Status indicates the progress of recovering the data.After the data is recovered, Operation Status displays a message, indicating that the operationis successful.

Step 10 In NE View, right-click the NE and choose Activation Database from the shortcut menu.The Activation Database dialog box is displayed.

Step 11 Click Start to start activating the database.

NOTE

Do not select Deliver to Board.

In NE View, Operation Status indicates the progress of activating the database. After thedatabase is activated, Operation Status indicates that the operation is successful.

----End



7-7

8 Supporting Task

About This Chapter

This topic describes the common maintenance operations.

8.1 Hardware LoopbackHardware loopback refers to the loopback operation performed by changing the physicalconnection.

8.2 Cleaning Fiber Connectors and AdaptersThe optical connectors are easily contaminated in the maintenance process. The minute dustparticles that can be seen only in the microscope can also affect the quality of optical signals. Inthis case, the system performance deteriorates. Hence, the fiber connectors or adapters that areterminated need to be cleaned in time.

8.3 Browsing Alarms, Abnormal Events, and Performance EventsThe U2000 is used to browse alarms, abnormal events, and performance events at the networklayer.

8.4 Querying a ReportYou can obtain the version, manufacture, and microwave link information of all the boards byquerying the corresponding report.

8.5 Software LoopbackSoftware loopback refers to the loopback operation that is implemented by using the NMS.During software loopback, you need not visit the engineering site. Hence, software loopback isused more widely than hardware loopback.

8.6 ResetReset is an important method of troubleshooting software faults. Reset is classified into coldreset, warm reset.

8.7 PRBS TestThe pseudorandom binary sequence (PRBS) test is an important method of network maintenanceand self-check.

8.8 Querying the License CapacityYou can check whether the loaded license file meets the requirements by querying the licensecapacity.

OptiX RTN 950Maintenance Guide (U2000) 8 Supporting Task


8-1

8.9 Setting the On/Off State of the LaserWhen performing operations such as testing a fiber cut, you can set the on/off state of the laserrather than removing and re-inserting the optical fiber on site.

8.10 Setting the ALS FunctionThe SDH optical interface board supports the automatic laser shutdown (ALS) function. Thisfunction enables the board to turn off a laser when the board does not transmit services, theoptical fiber is faulty, or the received optical signals are lost.

8.11 Setting the Automatic Release FunctionTo protect the communication between the NMS and NE against improper operations, an NEsupports the automatic release of the ODU muting, software loopback, and other operations thatrequire you to exercise caution. The automatic release time is five minutes by default. You canset whether to enable the automatic release function and the automatic release time through theNMS.

8.12 Configuring the Performance Monitoring Status of NEsBy default, the performance monitoring of NEs is enabled. You can disable or enable thisfunction manually and set the period of the performance monitoring of NEs manually.

8.13 Querying the Impedance of an E1 ChannelThe impedance of an E1 channel is 75 ohms or 120 ohms, which cannot be set through the NMS.

8.14 Monitoring Ethernet Packets Through Port MirroringTo monitor and analyze the Ethernet packets at a port, you can enable the port mirroring functionso that the received or transmitted packets on the port are duplicated to another Ethernet port towhich the Ethernet tester is connected. Then, you can monitor and analyze the packets.

8.15 Querying the Attributes of an Ethernet PortThrough the operation, you can learn about the attributes of an Ethernet port, such as rate, MACaddress, and actual working mode.

8.16 Switching the System Control Unit and the Cross-Connect UnitWhen the OptiX RTN 950 is configured with two system control, cross-connect, and timingboards, you can manually switch the system control unit and the cross-connect unit as required.

8 Supporting TaskOptiX RTN 950



Issue 05 (2010-07-30)

8.1 Hardware LoopbackHardware loopback refers to the loopback operation performed by changing the physicalconnection.

Background Information

Hardware loopback is classified into optical cable loopback, PDH cable loopback, and Ethernetport loopback.

l Optical cable loopback indicates that the receive and transmit optical fibers are connectedthrough a fiber jumper on the ODF. In certain occasions, an optical attenuator is addedbased on the actual situation, to prevent the optical board from being damaged by theexcessive receive optical power.

l PDH cable loopback indicates that the receive and transmit PDH cables are connectedthrough a short-circuiting cable or connector on the DDF.

l Ethernet port loopback indicates that the receive and transmit service signals on oneEthernet port are looped back through a special loopback Ethernet cable.

8.2 Cleaning Fiber Connectors and AdaptersThe optical connectors are easily contaminated in the maintenance process. The minute dustparticles that can be seen only in the microscope can also affect the quality of optical signals. Inthis case, the system performance deteriorates. Hence, the fiber connectors or adapters that areterminated need to be cleaned in time.

8.2.1 Cleaning Fiber Connectors by Using Cartridge CleanersWhen there are special cartridge cleaners (such as the CLETOP cassette cleaner), use them forcleaning the fiber connectors.

8.2.2 Cleaning Fiber Connectors by Using Lens TissueWhen there is no cartridge cleaners, use the lens tissue for cleaning fiber connectors.

8.2.3 Cleaning Fiber Adapters by Using Optical Cleaning SticksThe fiber adapters need to be cleaned with optical cleaning sticks. This topic describes themethod of cleaning fiber adapters on the optical interface board. The same method can be usedto clean fiber adapters on the optical attenuators and flanges.

8.2.1 Cleaning Fiber Connectors by Using Cartridge CleanersWhen there are special cartridge cleaners (such as the CLETOP cassette cleaner), use them forcleaning the fiber connectors.

Prerequisitel Disconnect both ends of the fiber. Ensure that there is no laser light on the fiber connectors.

l Inspect the fiber connector with a fiber microscope to ensure that the fiber connectors arecontaminated.



8-3

Tools, Equipment, and MaterialsCartridge cleaner

Procedure

Step 1 Press down and hold the lever. Then, the shutter slides back and exposes a new cleaning area.

Figure 8-1 Using the CLETOP cassette cleaner

Step 2 Position the fiber tip slightly against the cleaning area and drag the fiber tip slightly in thedownward direction.




Issue 05 (2010-07-30)

Figure 8-2 Dragging the fiber tip slightly on one cleaning area

Step 3 Repeat the same in the other cleaning area in the same direction as Step 2.

Figure 8-3 Dragging the fiber tip slightly on the other cleaning area



8-5

Step 4 Release the lever to close the cleaning area.

----End

8.2.2 Cleaning Fiber Connectors by Using Lens TissueWhen there is no cartridge cleaners, use the lens tissue for cleaning fiber connectors.

Prerequisitel Disconnect both ends of the fiber. ensure that there is no laser light on the fiber connectors.l Inspect the fiber connector with a fiber microscope to ensure that the fiber connectors are

contaminated.

Tools, Equipment, and Materialsl Clean solventl Non-woven lens tissuel Special compressed gas

NOTE

l The isoamylol is preferred as the clean solvent, and the propyl can also be used as the clean solvent.Do not use alcohol or formalin.

l The fiber cleaning tissue or lint-free wipes can substitute the non-woven lens tissue.

l The special cleaning roll can substitute the special compressed gas.

ProcedureStep 1 Place a small amount of cleaning solvent on the lens tissue.

Step 2 Drag the fiber tip slightly on the lens tissue.

Figure 8-4 Cleaning the fiber with the lens tissue




Issue 05 (2010-07-30)

Step 3 Repeat Step 2 several times on the areas of the lens tissue that have not been used.

Step 4 Use the compressed gas to blow the fiber tip.When using compressed gas, note the following points:l First spray it into the air because the initial spray of condensation may contain certain

sediment.l Ensure that the injector nozzle is as close as possible to (but does not toubch) the connector

surface.

----End

8.2.3 Cleaning Fiber Adapters by Using Optical Cleaning SticksThe fiber adapters need to be cleaned with optical cleaning sticks. This topic describes themethod of cleaning fiber adapters on the optical interface board. The same method can be usedto clean fiber adapters on the optical attenuators and flanges.

Prerequisitel Before you clean the fiber adapter, remove the optical fiber and shut down the laser. For

details about how to shut down a laser, see 8.9 Setting the On/Off State of the Laser.l Inspect the fiber adapter with a fiber microscope to ensure that the fiber adapter is

contaminated.

Tools, Equipment, and Materialsl Optical cleaning sticks

l Clean solvent

l Special compressed gas

NOTE

l In the case of the SC and FC optical interface, use the cleaning stick with a diameter of 2.5 mm. In thecase of the LC optical interface, use the cleaning stick with a diameter of 1.25 mm.

l The medical cotton or long fiber cotton can substitute the optical cleaning stick.

l The isoamylol is preferred as the clean solvent, and the propyl can also be used as the clean solvent.Do not use alcohol or formalin.

l The special cleaning roll can substitute the special compressed gas.

Procedure

Step 1 Apply a small amount of cleaning solvent on the optical cleaning stick.

Step 2 Touch the adapter gently with the optical cleaning stick and turn the stick clockwise four to fivetimes.Ensure that there is direct contact between the stick tip and fiber tip so that the solvent can cleanthe adapter tip.

Step 3 Use the compressed gas to blow the fiber adapter.When using compressed gas, note the following points:



8-7

l First spray the compressed gas into the air because the initial spray of condensation gas maycontain some sediment.

l Ensure that the injector nozzle is as close as possible to (but does not touch) the inner surfaceof the connector.

----End

8.3 Browsing Alarms, Abnormal Events, and PerformanceEvents

The U2000 is used to browse alarms, abnormal events, and performance events at the networklayer.

8.3.1 Checking the NE StatusYou can learn about the basic information such as whether the NE fails to communicate withthe NMS and whether any alarms are reported by checking the NE status.

8.3.2 Checking the Board StatusYou can learn about the board status in a visual manner by checking the slot diagram.

8.3.3 Browsing Current AlarmsYou can find the faults that occur on the equipment by browsing current alarms.

8.3.4 Browsing Abnormal EventsYou can find the faults that occur on the equipment in a specific time by browsing abnormalevents. An abnormal event refers to an exception that occurs on the system at a particular timerather than an exception that persists for a certain time of period.

8.3.5 Browsing Current Performance EventsYou can know the running status of the equipment by browsing current SDH/PDH performanceevents.The counter of current performance events measures all the performance events that arisebetween the start time of the monitoring period and the current time.

8.3.6 Browsing History AlarmsYou can know the faults that occur on the equipment in a past period of time by browsing historyalarms. A history alarm refers to an alarm that is already cleared.

8.3.7 Browsing History Performance EventsYou can know the faults that occur on the equipment in a past period of time by browsing historyperformance events.

8.3.8 Browsing the Performance Event Threshold-Crossing RecordsYou can learn about the threshold-crossing information of the performance events of an NE bybrowsing the performance event threshold-crossing records.

8.3.1 Checking the NE StatusYou can learn about the basic information such as whether the NE fails to communicate withthe NMS and whether any alarms are reported by checking the NE status.

Prerequisite





Issue 05 (2010-07-30)


PrecautionsNOTE

By default, the color of the NE icon on the NMS indicates the NE status.

Procedure

Step 1 Check the NE icon on the Main Topology.

The NE icon is green. The other colors indicate the following situations:

l Gray: indicates that the communication between the NE and the NMS is interrupted.

l Purple: indicates that the NE status is unknown.

l Red: indicates that a critical alarm is generated.

l Orange: indicates that a major alarm is generated.

l Yellow: indicates that a minor alarm is generated.

l Light blue: indicates that a warning is generated.

Step 2 Double-click the NE. The slot diagram is displayed. The NE is in Running Status.

Step 3 Click the icon. The legend description is displayed.

----End

8.3.2 Checking the Board StatusYou can learn about the board status in a visual manner by checking the slot diagram.



Procedure

Step 1 On the Main Topology, double-click the desired NE. The NE Panel is displayed. The NE is inRunning Status.

Step 2 Click the icon. The legend description is displayed.

Step 3 In the NE Explorer, click the NE Panel tab.

Step 4 Check the running status of the boards based on the legend description. If a board is runningnormally, the board icon is green.

----End



8-9

8.3.3 Browsing Current AlarmsYou can find the faults that occur on the equipment by browsing current alarms.



ProcedureStep 1 Choose Fault > Browse Current Alarm from the Main Menu.

Step 2 In the Filter dialog box, click the Alarm Source tab.

Step 3 Optional: Select one or more NEs from the left pane, and click .

Step 4 Click OK.

Step 5 Browse the displayed alarms.

Step 6 Select the newly generated alarms, record the details of the alarms, and click OK.

Step 7 Notify the troubleshooting personnel to clear the alarms in time.For the details, see A.3 Alarms and Handling Procedures.

----End

Related InformationA current alarm refers to an alarm that is not cleared.

You can browse the network-wide alarms based on the alarm severity by clicking the alarmindicators in the upper right corner.

l You can click (red) to browse the network-wide critical alarms.

l You can click (orange) to browse the network-wide major alarms.

l You can click (yellow) to browse the network-wide minor alarms.

l You can click (light-blue) to browse the network-wide warning alarms.

NOTE

By default, the number shown by each indicator indicates the number of current network-wide alarms, whichare not cleared, of the specific severity.

8.3.4 Browsing Abnormal EventsYou can find the faults that occur on the equipment in a specific time by browsing abnormalevents. An abnormal event refers to an exception that occurs on the system at a particular timerather than an exception that persists for a certain time of period.




Issue 05 (2010-07-30)



Procedure

Step 1 Choose Fault > Browse Event from the Main Menu.

Step 2 In the Filter dialog box, click the Event Source tab.

Step 3 Select one or more NEs from the left pane, and click .

Step 4 Click OK.

Step 5 Browse the abnormal events.

For details on how to handle an abnormal event, see B.2 Abnormal Performance Events andHandling Procedures.

----End

Related InformationBeing different from an alarm that has both the occurrence time and the clearance time, anabnormal event has only the occurrence time.

8.3.5 Browsing Current Performance EventsYou can know the running status of the equipment by browsing current SDH/PDH performanceevents.The counter of current performance events measures all the performance events that arisebetween the start time of the monitoring period and the current time.





Procedure

Step 1 Choose Performance > Browse SDH Performance from the Main Menu, and then click theCurrent Performance Data tab.




8-11


Step 4 Select 15-Minute in the Monitor Period field.

Step 5 Click the Count tab, and then select Display Continuous Severely Errored Seconds.

Step 6 Click Query to browse the current performance events.In normal cases, no bit error performance events should be displayed, and the number of pointerjustification events should be less than six per day.

Step 7 Click the Gauge tab, select All for the performance event type, and then select Display CurrentValue and Display Maximum and Minimum Values in the right pane.

Step 8 Click Query to browse the displayed performance events.In normal cases, compared with the history records, the gauge indicators, such as the boardtemperature, do not change drastically.

Step 9 Re-define the time span by setting Monitor Period to 24-Hour.

Step 10 Repeat Step 5 through Step 8 to query the current performance events in a period of 24 hours.

----End

8.3.6 Browsing History AlarmsYou can know the faults that occur on the equipment in a past period of time by browsing historyalarms. A history alarm refers to an alarm that is already cleared.

Prerequisite



U2000

Procedure

Step 1 Choose Fault > Browse History Alarms from the Main Menu.

Step 2 Optional: In the Filter dialog box, click the Basic Settings tab.1. In Severity, select the alarm severity to be queried.2. In Type, select the alarm type.3. In Generated Time, specify the alarm generation time.4. In Cleared Time, specify the alarm clearance time.

The time span starts from the time when the last history alarm browsing operation wasperformed to the current time.

Step 3 In the Filter dialog box, click the Alarm Source tab.


Step 5 Click OK.




Issue 05 (2010-07-30)

Step 6 Browse the displayed history alarms.

----End

8.3.7 Browsing History Performance EventsYou can know the faults that occur on the equipment in a past period of time by browsing historyperformance events.





Procedure

Step 1 Choose Performance > Browse SDH Performance from the main menu, and then click theHistory Performance Data tab.


Step 3 Set the parameters, such as Monitored Object Filter Condition, Monitor Period, DataSource.

Step 4 Click the Gauge tab, and set Performance Event Type.

Step 5 Click the Count tab, and set Performance Event Type.

Step 6 Click Query.

----End

8.3.8 Browsing the Performance Event Threshold-Crossing RecordsYou can learn about the threshold-crossing information of the performance events of an NE bybrowsing the performance event threshold-crossing records.



Procedure

Step 1 Browse the performance event threshold-crossing records that is displayed.



8-13

Step 2 Choose Performance > Browse SDH Performance from the Main Menu.

Step 3 Select an NE from the Object Tree in the NE Explorer. Click .

Step 4 Click the Performance Threshold-Crossing Record tab.

Step 5 Set the parameters such as Monitored Object Filter Condition, Monitor Period, andPerformance Event Type.

Step 6 Click Query.

----End

8.4 Querying a ReportYou can obtain the version, manufacture, and microwave link information of all the boards byquerying the corresponding report.

8.4.1 Querying the Board Information ReportYou can obtain the PCB version, logic version, and software version of each board by queryingthe board information report.

8.4.2 Querying the Board Manufacturing Information ReportYou can obtain the manufacturing information about each board and the SFP module by queryingthe board manufacturing information report.

8.4.3 Querying the Microwave Link Information ReportYou can obtain the the current and recent transmit/receive power of microwave links by queryingthe microwave link information report.

8.4.1 Querying the Board Information ReportYou can obtain the PCB version, logic version, and software version of each board by queryingthe board information report.



ProcedureStep 1 Choose Inventory > Physical Inventory > Board from the Main Menu.

Step 2 In Physical Inventory, click the Board List tab.

Step 3 Click Filter.In Set Board Filter Criteria window, set the board attributes that need to be queried. ClickOK.

Step 4 Optional: Click Save As. Then, you can save and archive the board information as a text file.

----End




Issue 05 (2010-07-30)

8.4.2 Querying the Board Manufacturing Information ReportYou can obtain the manufacturing information about each board and the SFP module by queryingthe board manufacturing information report.

Prerequisite



U2000

Procedure

Step 1 Choose Inventory > Project Document > Board Manufacture Information from the MainMenu.

Step 2 In Board Manufacture Information, click the Board Manufacture Information tab.


Step 4 Optional: Click Save As. Then, you can save and archive the board manufacturing informationas a text file.

----End

8.4.3 Querying the Microwave Link Information ReportYou can obtain the the current and recent transmit/receive power of microwave links by queryingthe microwave link information report.

Prerequisite



U2000

Procedure

Step 1 In Main Menu, choose Inventory > Microwave Report > Microwave Link Report.

Step 2 In the left pane of the Microwave Link Information Report tab page, choose one or more NEs,

and click .

Step 3 Optional: Click Save As. Then, you can save and archive the microwave link information reportas a text file.

----End



8-15

8.5 Software LoopbackSoftware loopback refers to the loopback operation that is implemented by using the NMS.During software loopback, you need not visit the engineering site. Hence, software loopback isused more widely than hardware loopback.

8.5.1 Setting Loopback for the SDH Optical Interface BoardThe SDH optical interface board supports the optical interface inloop/outloop and the VC-4 pathinloop/outloop.

8.5.2 Setting Loopback for the Tributary BoardThe tributary board supports the tributary inloop and outloop.

8.5.3 Setting a Loopback for the Ethernet Interface BoardThe Ethernet interface board supports the Ethernet port inloop (at the MAC layer and PHY layer).

8.5.4 Setting Loopback for the IF BoardLoopbacks on the IF board are classified into IF port loopback, composite port loopback, andIF_ETH port MAC loopback. The IF1 board supports the IF port inloop, and IF port outloop.The IFU2 board supports the IF port inloop, IF port outloop, composite port inloop, compositeport outloop, and IF_ETH port MAC inloop. The IFX2 board supports the IF port inloop, IFport outloop, composite port inloop, composite port outloop, and IF_ETH port MAC inloop.

8.5.5 Locating a Fault by Performing Loopback OperationsLoopback is a common method of locating the fault.

8.5.1 Setting Loopback for the SDH Optical Interface BoardThe SDH optical interface board supports the optical interface inloop/outloop and the VC-4 pathinloop/outloop.

PrerequisiteYou must be an NM user with NE maintainer authority or higher.


ContextThe optical interface inloop is a process wherein the signals over an SDH port are looped backat the overhead processing unit towards the backplane.

Figure 8-5 Optical interface inloop

SDH opticalinterface boardBackplane

SDH




Issue 05 (2010-07-30)

The optical interface outloop is a process wherein the signals over an SDH port are looped backat the overhead processing unit towards the remote equipment.

Figure 8-6 Optical interface outloop


SDH

The VC-4 path outloop is a process wherein the signals on a VC-4 path are looped back at thelogic processing unit towards the remote equipment.

Figure 8-7 VC-4 path outloop


VC-4

The VC-4 path inloop is a process wherein the signals on a VC-4 path are looped back at thelogic processing unit towards the backplane.

Figure 8-8 VC-4 path inloop

SDH opticalboardBackplane

VC-4



8-17

Precautions

CAUTIONl The services may be interrupted at the port or on the path where the loopback is performed.

l A software loopback may be released automatically after a certain period (five minutes, bydefaults). For details, see 8.11 Setting the Automatic Release Function.

Procedure

Step 1 Select the SDH optical interface board from the Object Tree.

Step 2 Choose Configuration > SDH Interface from the Function Tree.

Step 3 Select By Function, and select the loopback mode from the drop-down list.

To Perform... Choose...

Optical interface loopback Optical(Electrical) Interface Loopback

VC-4 path loopback VC4 Loopback

Step 4 Set the loopback status of the port or path based on the requirements.

Step 5 Click Apply.Then, the Confirm dialog box is displayed.

Step 6 Click OK.


----End

8.5.2 Setting Loopback for the Tributary BoardThe tributary board supports the tributary inloop and outloop.

Prerequisite

You must be an NM user with NE maintainer authority or higher.


U2000

Context

The tributary inloop is a process wherein the signals over a PDH port are looped back at thecoding/decoding unit towards the backplane.




Issue 05 (2010-07-30)

Figure 8-9 Tributary inloop

PDH interface boardBackplane

PDH

The tributary outloop is a process wherein the signals on a tributary path are looped back at thePDH interface board of the local IDU towards the remote equipment.

Figure 8-10 Tributary outloop

PDH

PDH interface boardBackplane

Precautions

CAUTIONThe services may be interrupted on the port or on the path where the loopback is performed.

Procedure

Step 1 Select the PDH interface board from the Object Tree.

Step 2 Choose Configuration > PDH Interface from the Function Tree.

Step 3 Select By Function, and select Tributary Loopback from the drop-down list.

Step 4 Set the loopback status of the path based on the requirements.


Step 6 Click OK.



8-19


----End

8.5.3 Setting a Loopback for the Ethernet Interface BoardThe Ethernet interface board supports the Ethernet port inloop (at the MAC layer and PHY layer).



ContextThe Ethernet port MAC inloop is a process wherein the Ethernet physical signals are loopedback at the service processing module of the board at the MAC layer towards the backplane.The Ethernet port PHY inloop is a process wherein the Ethernet frame signals are looped backat the interface module of the board at the PHY layer towards the backplane.

Figure 8-11 Ethernet port inloop

Ethernet serviceprocessing boardBackplane

PHYMAC

Precautions

CAUTIONl A loopback operation results in service interruption.


Procedure

Step 1 Select an Ethernet processing board from the Object Tree.

Step 2 Select the corresponding function options from the Function Tree based on the loopback type.




Issue 05 (2010-07-30)


PHY loopback 1. Choose Configuration > Interface Management > EthernetInterface from the Function Tree.

2. Click the Advanced Attributes tab.

MAC loopback 1. Choose Configuration > Interface Management > EthernetInterface from the Function Tree.


Step 3 Set the loopback status of the port based on the requirements.


Step 5 Click OK.


----End

8.5.4 Setting Loopback for the IF BoardLoopbacks on the IF board are classified into IF port loopback, composite port loopback, andIF_ETH port MAC loopback. The IF1 board supports the IF port inloop, and IF port outloop.The IFU2 board supports the IF port inloop, IF port outloop, composite port inloop, compositeport outloop, and IF_ETH port MAC inloop. The IFX2 board supports the IF port inloop, IFport outloop, composite port inloop, composite port outloop, and IF_ETH port MAC inloop.



ContextThe IF port inloop is a process wherein the IF signals are looped back at the modem unit towardsthe backplane.

Figure 8-12 IF port inloop

IF boardBackplane

IF signal



8-21

The IF port outloop is a process wherein the IF signals are looped back at the modem unit of theboard towards the remote equipment.

Figure 8-13 IF port outloop

IF boardBackplaneIF signal

The composite port inloop is a process wherein the microwave baseband signal is looped backat the MUX/DEMUX unit of the board towards the backplane.

Figure 8-14 Composite port inloop

IF boardBackplaneMicrowave

baseband signal

The composite outloop is a process wherein the microwave baseband signal is looped back atthe MUX/DEMUX unit of the board towards the remote equipment.

Figure 8-15 Composite port outloop

IF boardBackplaneMicrowavebaseband

signal




Issue 05 (2010-07-30)

Precautions

CAUTIONl The services may be interrupted at the port or on the path where the loopback is performed.


l To perform the software loopback on the standby IF board of the 1+1 HSB/FD/SD protectiongroup, switch the standby IF board to the working state forcedly. Otherwise, the operationmay fail.

l Before performing the loopback operation for the IFU2/IFX2 board, disable the AM functionat both ends of the radio link.

Procedure

Step 1 Select the corresponding operation object from the Object Tree.

Option Description


IF port loopback IF board

Composite port loopback Hybrid IF board

MAC loopback NE

Step 2 Select the corresponding function options from the Function Tree based on the loopback type.

Option Description


IF port loopback 1. Choose Configuration > IF Interface from the Function Tree.2. Select By Function.3. Choose IF Port Loopback from the drop-down list.4. Select the port where the loopback needs to be performed and

set IF Port Loopback.

Composite port loopback 1. Choose Configuration > Digital Interface from the FunctionTree.

2. Select By Function.3. Choose Optical(Electrical) Interface Loopback from the

drop-down list.4. Select the port where the loopback needs to be performed and

set Optical (Electrical) Interface Loopback.



8-23

Option Description

MAC loopback 1. Choose Configuration > Interface Management >Microwave Interface from the Function Tree.

2. Select Advanced Attributes.3. Select the port where the loopback needs to be performed and

set MAC Loopback.


Step 4 Click OK to close the dialog box.Then, a dialog box is displayed.


----End

8.5.5 Locating a Fault by Performing Loopback OperationsLoopback is a common method of locating the fault.



Service TrailFigure 8-16 shows how to locate a fault by performing a loopback operation.

Figure 8-16 Service trail

IFboard

Cross-connectboard

SDHtributaryboard

ODU

NE2

IFboard

Cross-connectboard

SDHtributaryboard

ODU

NE3

Optical cable

IFboard

Cross-connectboard ODU

NE4

PDHtributaryboard

IFboard

Cross-connectboard ODU

NE1

PDHtributaryboard




Issue 05 (2010-07-30)

Procedure

Step 1 If the services are available on the radio links, perform the inter-station loopbacks to narrowdown the fault to a specific hop.

1. Set the outloops for the SDH optical interface boards on NE2 and NE3, and then performthe inter-station loopbacks to locate the fault.

Step 2 After the fault is located on the specific radio link, perform the intra-station loopbacks to narrowdown the fault to a specific NE or board.

1. Set inloop for the IF board on the NEs at both ends of the radio link where the fault occurs,to check whether the service receiver or the radio link is faulty.

2. If the fault is located in the service receiver, set outloop for the PDH tributary board tocheck whether the interface board or cross-connect board is faulty.

3. If the radio link is faulty, replace the IF board and ODU to check whether the IF board orODU is faulty.

----End

8.6 ResetReset is an important method of troubleshooting software faults. Reset is classified into coldreset, warm reset.

8.6.1 Cold ResetCold reset is a process wherein the board software is reset and the board is re-initiated. Thesoftware of each board runs as a software module in the CPU on the system control, cross-connect, and timing board. During the board initialization, the FPGA, if any, is re-loaded.

8.6.2 Warm ResetWarm reset is a process wherein the board software is reset but the board is not re-initiated. Thesoftware of each board runs as a software module in the CPU on the integrated board of thesystem control unit, cross-connect unit, and timing unit.

8.6.1 Cold ResetCold reset is a process wherein the board software is reset and the board is re-initiated. Thesoftware of each board runs as a software module in the CPU on the system control, cross-connect, and timing board. During the board initialization, the FPGA, if any, is re-loaded.

Prerequisite



U2000



8-25

Precautions

CAUTIONCold reset causes service interruption because it is similar to the procedure of removing andinserting a board.

Procedure

Step 1 In NE Panel, right-click the board where the cold reset needs to be performed.

Step 2 Choose Cold Reset from the shortcut menu.Then, the Warning dialog box is displayed.

Step 3 Click OK.


----End

8.6.2 Warm ResetWarm reset is a process wherein the board software is reset but the board is not re-initiated. Thesoftware of each board runs as a software module in the CPU on the integrated board of thesystem control unit, cross-connect unit, and timing unit.

Prerequisite



U2000

Precautions

During warm reset, the board software is reset but the services are not interrupted.

Procedure

Step 1 In NE Panel, right-click the board where the warm reset needs to be performed.

Step 2 Choose Warm Reset from the shortcut menu.Then, the Warning dialog box is displayed.

Step 3 Click OK.


----End




Issue 05 (2010-07-30)

8.7 PRBS TestThe pseudorandom binary sequence (PRBS) test is an important method of network maintenanceand self-check.

8.7.1 Performing a PRBS Test for the Tributary BoardIf a special test tool is unavailable, you can perform the PRBS test by using the embedded testsystem on the tributary board.

8.7.2 Performing a PRBS Test for the IF BoardIf a special test tool is unavailable, you can perform the PRBS test by using the embedded testsystem on the IF board.

8.7.1 Performing a PRBS Test for the Tributary BoardIf a special test tool is unavailable, you can perform the PRBS test by using the embedded testsystem on the tributary board.

Prerequisite



U2000

Context

The OptiX RTN 950 supports the PRBS test in the tributary direction and in the cross-connectdirection.

The PRBS test in the tributary direction can be performed to check the connection between thetributary board and the DDF, as shown in Figure 8-17.

Figure 8-17 PRBS test in the tributary direction

PRBSTransmitter

PRBSRecevicer

PDH interface boardDDF frame

1

1 Loopback at the DDF frame

The PRBS test in the cross-connect direction can be performed to check the connection betweenthe tributary board and the remote NE, as shown in Figure 8-18.



8-27

Figure 8-18 PRBS test in the cross-connect direction

Cross-connectboard

PRBStransmitter

PRBSreceiver

PDH interfaceboard IF board

NE at the local end NE at the opposite end

IN

OUT

VC-4 inloop orcomposite port inloop

IF port inloop IF port outloop1

2 3

2 3

IF board

1

a) IF board working as the line board

Cross-connect board

PRBStransmitter

PRBSreceiver

PDH interface board

NE at the local end NE at the opposite end

IN

OUT

VC-4 inloop Port inloop Port outloop1

2 3

2 3

SDH opticalinterface board

1

b) Line board working as the SDH optical interface board

Precautions

CAUTIONl During the PRBS test, the services in the tested path are interrupted.

l The PRBS test can be performed only in one path and in one direction at one time.

Procedure

Step 1 Set the loopback at the proper location. For details, see Figure 8-17 and Figure 8-18.

Step 2 Select the E1 interface board from the Object Tree.

Step 3 Choose Configuration > PRBS Test from the Function Tree.

Step 4 Select the port to be tested.




Issue 05 (2010-07-30)

Step 5 Set Duration and Measured in Time.NOTE

l The PRBS test supports three time units: one second, 10 minutes, and one hour.

l A maximum of 255 test cycles is permissible for the PRBS test.

Step 6 Optional: Select Accumulating Mode.

Step 7 Click Start to Test.A prompt is displayed.

Step 8 Click OK.

Step 9 When Process is displayed as 100%, click Query to check the test result.NOTE

The result of a PRBS test can be normal, error, or invalid.

l Invalid: indicates that no bit is received. In this case, the curve is yellow.

l Normal: indicates that the path is in normal state. In this case, the number of PRBSs is zero, and thecurve is green.

l Error: indicates that the path has errors. In this case, the number of total PRBSs is a non-zero number,and the curve is red.

----End

8.7.2 Performing a PRBS Test for the IF BoardIf a special test tool is unavailable, you can perform the PRBS test by using the embedded testsystem on the IF board.



Precautions

Figure 8-19 PRBS test of the IF board

11

PRBStransmitter

PRBS

ODU

1

ODU

NE at the local end NE at the opposite endIF port outloop1

transmitter

IF board IF board



8-29

CAUTIONl During the PRBS test, the services in the tested path are interrupted.

l The PRBS test can be performed only in one path and in one direction at one time.

l Before you perform the PRBS test for the standby IF board of a 1+1 HSB/FD/SD protectiongroup, you must switch the standby IF board to the working state.

l The standby IF unit does not support the PRBS test. To test the standby radio link, you needto power off the main ODU and perform the PRBS test on the main IF board. In this case,the PRBS signals are sent out of the standby IF board through the protection bus, thusimplementing the PRBS test of the radio link.

Procedure

Step 1 Perform an outloop on the IF board. For details, see 8.5.4 Setting Loopback for the IFBoard.

Step 2 Select the IF board from the Object Tree.

Step 3 Choose Configuration > PRBS Test from the Function Tree.

Step 4 Select the port to be tested.

Step 5 Set Duration and Measured in Time.

NOTE

l The time unit of the PRBS test can be one second, 10 minutes, or one hour.

l A maximum of 255 test cycles is permissible for the PRBS test.

Step 6 Optional: Select Accumulating Mode.

Step 7 Click Start to Test.A prompt is displayed.

Step 8 Click OK.

Step 9 When Process is displayed as 100%, click Query to check the test result.

NOTE

The result of a PRBS test can be normal, error, or invalid.

l Invalid: indicates that no bit is received. In this case, the curve is yellow.

l Normal: indicates that the path is in normal state. In this case, the number of PRBSs is zero, and thecurve is green.

l Error: indicates that the path has errors. In this case, the number of total PRBSs is a non-zero number,and the curve is red.

----End




Issue 05 (2010-07-30)

8.8 Querying the License CapacityYou can check whether the loaded license file meets the requirements by querying the licensecapacity.



Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer.

Step 2 Choose Configuration > License Management.

Step 3 Click Query, browse the license capacity of the NE.

----End

8.9 Setting the On/Off State of the LaserWhen performing operations such as testing a fiber cut, you can set the on/off state of the laserrather than removing and re-inserting the optical fiber on site.



Procedure

Step 1 Select the desired SDH optical interface board from the Object Tree.

Step 2 Choose Configuration > SDH Interface from the Function Tree.

Step 3 Select By Function.

Step 4 Select Laser Switch from the drop-down list.

Step 5 Select a port, and then set Laser Switch.

Step 6 Click Apply.A confirmation dialog box is displayed.

Step 7 Click OK.



8-31

A prompt is displayed.

Step 8 Click OK.

----End

8.10 Setting the ALS FunctionThe SDH optical interface board supports the automatic laser shutdown (ALS) function. Thisfunction enables the board to turn off a laser when the board does not transmit services, theoptical fiber is faulty, or the received optical signals are lost.



Procedure

Step 1 Select the desired SDH optical interface board from the Object Tree.

Step 2 Choose Configuration > Automatic Laser Shutdown from the Function Tree.

Step 3 Select a port, and then set Automatic Shutdown to Enabled.

Step 4 Click Apply to save the settings.

----End

8.11 Setting the Automatic Release FunctionTo protect the communication between the NMS and NE against improper operations, an NEsupports the automatic release of the ODU muting, software loopback, and other operations thatrequire you to exercise caution. The automatic release time is five minutes by default. You canset whether to enable the automatic release function and the automatic release time through theNMS.



Procedure

Step 1 Choose Configuration > NE Batch Configuration > Automatic Disabling of NE Functionfrom the Main Menu.




Issue 05 (2010-07-30)

Step 2 Select the desired NE from the Object Tree. Click .

Step 3 In Automatic Disabling of NE Function, set Auto Disabling and Auto Disabling Time(min).

Step 4 Click Apply to complete the settings for the automatic release function.

----End

8.12 Configuring the Performance Monitoring Status of NEsBy default, the performance monitoring of NEs is enabled. You can disable or enable thisfunction manually and set the period of the performance monitoring of NEs manually.



Procedure

Step 1 In the NE Explorer, select the NE from the Object Tree, and then choose Performance > NEPerformance Monitoring Time from the Function Tree.

Step 2 Configure the parameters of the performance monitoring of NEs.1. Select 15-Minute or 24-Hour.2. Select Enabled or Disabled in Set 15-Minute Monitoring or Set 24-Hour Monitoring.3. Set the start time and end time of the performance monitoring of NEs.

NOTE

l Generally, both Set 15-Minute Monitoring and Set 24-Hour Monitoring are enabled.

l You can specify the start time of the performance monitoring function, only after selecting Enable inthe Set 15-Minute Monitoring or Set 24-Hour Monitoring area.

l You can specify the end time of the performance monitoring function, only after selecting Enable andthen selecting To in the Set 15-Minute Monitoring or Set 24-Hour Monitoring area.



8-33

4. Click Apply, and then close the dialog box that is displayed.

----End

8.13 Querying the Impedance of an E1 ChannelThe impedance of an E1 channel is 75 ohms or 120 ohms, which cannot be set through the NMS.

Prerequisite



U2000

Procedure

Step 1 Select a PDH tributary board from the Object Tree.

Step 2 Choose Configuration > PDH Interface from the Function Tree.

Step 3 Select By Board/Port(Channel).

Step 4 Select Port in the list.

Step 5 Select a port, and check Port Impedance.

----End

8.14 Monitoring Ethernet Packets Through Port MirroringTo monitor and analyze the Ethernet packets at a port, you can enable the port mirroring functionso that the received or transmitted packets on the port are duplicated to another Ethernet port towhich the Ethernet tester is connected. Then, you can monitor and analyze the packets.




Issue 05 (2010-07-30)



ContextThe OptiX RTN 950 supports the mirroring, monitoring, and analyzing of the Ethernet packetsthat are received or transmitted on the port.

Figure 8-20 Schematic diagram of Ethernet port mirroring

Mirroringport

Ethernet processing unit

Monitoringport

Ethernetequipment

Ethernet testerDuplication

To monitor the data in different directions, port mirroring can be performed in the ingressdirection and in the egress direction.

l In the ingress directionAlso in the upstream direction. The equipment duplicates the packets received from themirroring port to the observing port, and then transmits the packets from the observing portto the Ethernet tester.

l In the egress directionAlso in the downstream direction. The equipment duplicates the packets transmitted by themirroring port to the observing port, and then transmits the packets from the observing portto the Ethernet tester.

NOTEThe Ethernet packets at Ethernet ports and IF_ETH ports can be monitored through the port mirroring function.

Procedure

Step 1 Select the desired NE from the Object Tree.

Step 2 Choose Configuration > Port Mirroring from the Function Tree.

Step 3 Click New. Set Direction, Mirror Listener Port, and Listened Port.



8-35

Step 4 Click OK.

Step 5 Choose Configuration > Ethernet Interface Management > Port Mirroring from theFunction Tree.

----End

8.15 Querying the Attributes of an Ethernet PortThrough the operation, you can learn about the attributes of an Ethernet port, such as rate, MACaddress, and actual working mode.

Prerequisite


Tools, Instruments, and Materials

U2000

Procedure

Step 1 Optional: Query the attributes of the FE or GE port.

1. In NE Explorer, select the required NE from the Object Tree.

2. Choose Configuration > Interface Management > Ethernet Interface from the FunctionTree.


4. Check the parameters such as Port Physical Parameters, Transmitting Rate, andReceiving Rate.

Step 2 Optional: Querying the attributes of the IF_ETH port.

1. In NE Explorer, select the required NE from the Object Tree.

2. Choose Configuration > Interface Management > Microwave Interface from theFunction Tree.


4. Check the parameters such as Transmitting Rate and Receiving Rate.

----End




Issue 05 (2010-07-30)

8.16 Switching the System Control Unit and the Cross-Connect Unit

When the OptiX RTN 950 is configured with two system control, cross-connect, and timingboards, you can manually switch the system control unit and the cross-connect unit as required.



Procedure

Step 1 Select the desired NE from the Object Tree.

Step 2 Choose Configuration > Board 1+1 Protection from the Function Tree.

Step 3 In 1+1 Protection List, select Cross-Connect Protection Pair.

Step 4 Perform the 1+1 protection switching on the board.

Option Description

If... Then...

Active Board is set to Working Board Click Working/Protection Switching.

Active Board is set to Protection Board Click Restore Working/Protection.

Step 5 In the prompt that is displayed, click OK.

----End



8-37

A Alarm Reference

Alarms are important indicators when abnormalities occur on the equipment. This topicdescribes all the possible alarms on the OptiX RTN 950 and how to handle these alarms.

A.1 Alarm List (in Alphabetical Order)The following table lists all the possible alarms generated by the OptiX RTN 950 in alphabeticalorder.

A.2 Alarm List (Classified by Logical Boards)This part lists the alarms that are reported by each board.

A.3 Alarms and Handling ProceduresThis topic describes all the alarms on the OptiX RTN 950 in alphabetical order and how to handlethese alarms.

OptiX RTN 950Maintenance Guide (U2000) A Alarm Reference


A-1

A.1 Alarm List (in Alphabetical Order)The following table lists all the possible alarms generated by the OptiX RTN 950 in alphabeticalorder.

Table A-1 Alarm list

Alarm Name Description Alarm Severity

A_LOC Add to bus - loss of clock Major

AM_DOWNSHIFT The downshift of the AMscheme

Major

APS_FAIL The MS protectionswitching fails

Major

APS_INDI The MS protectionswitching occurs

Major

APS_MANUAL_STOP The MSP protocol isstopped manually

Minor

AU_AIS AU alarm indication Major

AU_LOP AU loss of pointer Major

B1_EXC Regenerator section (B1)excessive errors

Minor

B1_SD Regenerator section (B1)signal degraded

Minor

B2_EXC Multiplex section (B2)excessive errors

Major

B2_SD Multiplex section (B2)signal degraded

Minor

B3_EXC Higher order path (B3)excessive errors

Major

B3_SD Higher order path (B3)signal degraded

Minor

BD_NOT_INSTALLED Slot not installed with thecorresponding logicalboard

Minor

BD_STATUS Board not in position Major

BIP_EXC BIP excessive errors Minor

BIP_SD BIP signal degrade Minor

BIOS_STATUS BIOS status Major

A Alarm ReferenceOptiX RTN 950


A-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 05 (2010-07-30)


BOOTROM_BAD BOOTROM data checkfailure

Major

BUS_ERR Bus Errors Critical

CFCARD_FAILED CF card operation failed Major

CFCARD_FULL CF card capacity full Major

CFCARD_OFFLINE CF card offline Major

CFCARD_W_R_DISABLED Reading and writing theCF card disabled

Major

CONFIG_NOSUPPORT Configuration notsupported

Major

COMMUN_FAIL The inter-boardcommunication failure

Major

DBMS_ERROR Database error Major

DBMS_PROTECT_MODE Database in protectionmode

Critical

DOWN_E1_AIS 2M down signal alarmindication

Major

E1_LOC Loss of E1 uplink clock Major

E1_LOS Loss of 2M line signal Minor

MULTI_RPL_OWNER The ring network containsseveral RPL_OWNERnodes

Minor

ETH_CFM_LOC The loss of connectivity Critical

ETH_CFM_MISMERGE Misconnection Critical

ETH_CFM_RDI Remote end CCM packetreceiving failure

Minor

ETH_CFM_UNEXPERI Error frame alarm Critical

ETH_EFM_DF Negotiation failure Major

ETH_EFM_EVENT The performance eventreported on the oppositeNE

Major

ETH_EFM_LOOPBACK The loopback Major

ETH_EFM_REMFAULT The fault on the oppositeNE

Critical



A-3


ETH_LOS The loss of Ethernet portconnection

Critical

ETHOAM_SELF_LOOP MAC port loopback ofpoint-to-point OAMprotocol

Major

EXT_SYNC_LOS The loss of the externalclock source

Critical

FAN_AGING An alarm of the aged fan Minor

FAN_FAIL The fan is faulty Major

FLOW_OVER The data flow received bythe Ethernet port exceedsthe threshold

Minor

HARD_BAD Hardware error Critical

HP_CROSSTR Higher order pathperformance overthreshold

Minor

HP_LOM Higher order path loss ofmultiframe

Major

HP_RDI Higher order path remotedefect indication

Minor

HP_REI Higher order path remoteerror indication

Warning

HP_SLM Higher order path signallabel mismatch

Minor

HP_TIM Higher order path traceidentifier mismatch

Minor

HP_UNEQ Higher order pathunequipped

Minor

HPAD_CROSSTR Higher order pathadaptation performanceover threshold

Minor

IF_CABLE_OPEN IF cable disconnected Major

IF_INPWR_ABN Abnormal input IF powerof the ODU

Major

IF_MODE_UNSUPPORTED Preset IF working modenot supported

Major

IN_PWR_HIGH Input power too high Critical




Issue 05 (2010-07-30)


IN_PWR_LOW Input power too low Critical

J0_MM Trace identifier mismatch Minor

K1_K2_M K1 and K2 mismatch Minor

K2_M K2 mismatch Minor

LAG_BWMM The bandwidthinconsistency in the LAGgroup

Major

LAG_DOWN The LAG is unavailable Major

LAG_MEMBER_DOWN A member port of a linkaggregation group (LAG)is unavailable

Minor

LASER_CLOSED The laser is shut down Major

LASER_MOD_ERR The type of the pluggableoptical module on theboard does not match thetype of the opticalinterface

Major

LASER_MOD_ERR_EX The type of the pluggableoptical module on theboard does not match thetype of the opticalinterface

Major

LCS_LIMITED Service capacityconfigured for the NEbeyond the authorizationrange of the license

Major

LCS_MISMATCH Boards in a protectiongroup are loaded withinconsistent license files

Major

LICENSE_LOST The NE fails to detect thelicense file

Major

LOOP_ALM A loop occurs Minor

LP_CROSSTR Threshold crossing ofperformance in the lowerorder path

Minor

LP_R_FIFO FIFO overflow on thereceiving side of the lowerorder path

Minor



A-5


LP_RDI Lower order path remotereceiving defectindication

Minor

LP_REI Lower order path remoteerror indication

Minor

LP_RFI Lower order path remotefailure indication

Minor

LP_SIZE_ERR TU size error Minor

LP_SLM Lower order path signallabel mismatch

Minor

LP_T_FIFO FIFO overflow on thetransmission side of thelower order path

Minor

LP_TIM Lower order path traceidentifier mismatch

Minor

LP_UNEQ Lower order pathunequipped

Minor

LPS_UNI_BI_M Mismatch inunidirectional operationand bidirectionaloperation in linear MSP

Minor

LSR_NO_FITED Laser not installed Critical

LTI The synchronizationsources are lost

Major

MS_AIS Multiplex section alarmindication

Major

MS_CROSSTR Multiplex sectionperformance overthreshold

Minor

MS_RDI Multiplex section remotedefect indication

Minor

MS_REI Multiplex section remoteerror indication

Warning

MSAD_CROSSTR Multiplex sectionadaptation performanceover threshold

Minor

NESOFT_MM Master and slave softwaredifferent alarm

Major




Issue 05 (2010-07-30)


MW_BER_EXC Excessive microwave linkbit errors

Minor

MW_BER_SD Microwave link signaldegradation

Minor

MW_FEC_UNCOR Microwave FECuncorrectable

Minor

MW_LIM Microwave link identifiermismatch

Major

MW_LOF Loss of microwave frame Critical

MW_RDI Microwave link remotedefect indication

Minor

NESF_LOST Loss of NE software Critical

NESTATE_INSTALL NE in the installation state Critical

NP1_MANUAL_STOP N+1 protection protocolmanually disabled

Minor

NP1_SW_FAIL N+1 protection switchingfailed

Major

NP1_SW_INDI N+1 protection switchingindication

Major

POWER_ALM Power module alarm Major

POWER_ABNORMAL A power supply failure Major

R_F_RST Receiving FIFO reset Minor

R_LOC Receive loss of clock Critical

R_LOF Receive loss of frame Critical

R_LOS Receive loss of signal thesignals on the receive lineside

Critical

R_S_ERR Receive signal error Critical

RADIO_FADING_MARGIN_INSUFF

Insufficient radio fadingmargin

Minor

RADIO_MUTE Radio transmission mute Warning

RADIO_RSL_BEYONDTH The antennas are notaligned

Minor

RADIO_RSL_HIGH Too high radio receivepower

Critical



A-7


RADIO_RSL_LOW Too low radio receivepower

Critical

RADIO_TSL_HIGH Too high radio transmitpower

Critical

RADIO_TSL_LOW Too low radio transmitpower

Critical

RELAY_ALARM_CRITICAL Critical alarm input Critical

RELAY_ALARM_MAJOR Major alarm input Major

RELAY_ALARM_MINOR Minor alarm input Minor

RELAY_ALARM_IGNORE Warning alarm input Ignor

RP_LOC Loss of receive phaselockring clock

Major

RPS_INDI Microwave protectionswitching alarm

Major

RS_CROSSTR Regenerator sectionperformance thresholdcrossing

Minor

RTC_FAIL The real-time clock (RTC)on the system controlboard fails

Major

S1_SYN_CHANGE Reference source changein S1_Mode

Major

SWDL_ACTIVATED_TIME-OUT

The activation timeout ofthe software package

Critical

SWDL_AUTOMATCH_INH The automatic matchfunction is disabled

Minor

SWDL_CHGMNG_NO-MATCH

The board softwareversion and the runningsoftware version areinconsistent

Critical

SWDL_COMMIT_FAIL The commissionoperation on the NE fails

Minor

SWDL_INPROCESS The package diffusion isin process on the NE

Warning

SWDL_NEPKGCHECK Files of the package storedin the flash memory of theNE are lost

Critical




Issue 05 (2010-07-30)


SWDL_PKG_NOBDSOFT Certain board software ismissing from the softwarepackage during the fullpackage diffusion

Minor

SWDL_PKGVER_MM Consistency check of thesoftware package versionfails

Critical

SWDL_ROLLBACK_FAIL The rollback on the NEfails

Minor

SYNC_C_LOS Synchronous source levelloss

Warning

T_ALOS E1 interface loss of analogsignal

Major

T_F_RST Transmit FIFO reset Minor

T_LOC Transmit loss of clock Major

TEMP_ALARM Temperature overthreshold

Minor

THUNDERALM The lightning protectionfailure

Minor

TU_AIS TU alarm indication Major

TU_LOP TU loss of pointer Major

UP_E1_AIS 2M up signal alarmindication

Minor

VOLT_LOS Loss of voltage Major

WRG_BD_TYPE Wrong board type Major

WRG_DEV_TYPE Wrong device type Critical

XPIC_LOS Loss of XPIC signal Critical

A.2 Alarm List (Classified by Logical Boards)This part lists the alarms that are reported by each board.

A.2.1 CST

APS_FAIL APS_INDI APS_MANUAL_STOP

BD_NOT_INSTALLED

BD_STATUS



A-9

BOOTROM_BAD

CFCARD_FAILED

CFCARD_FULL

CFCARD_OFFLINE

CFCARD_W_R_DISABLED

DBMS_ERROR

DBMS_PROTECT_MODE

EXT_SYNC_LOS

HARD_BAD K1_K2_M

K2_M LCS_MISMATCH

LPS_UNI_BI_M

LTI NESOFT_MM

NESF_LOST NESTATE_INSTALL

NP1_MANUAL_STOP

NP1_SW_FAIL NP1_SW_INDI

POWER_ALM RPS_INDI RTC_FAIL S1_SYN_CHANGE

SWDL_ACTIVATED_TIMEOUT

SWDL_AUTOMATCH_INH

SWDL_CHGMNG_NOMATCH

SWDL_COMMIT_FAIL

SWDL_INPROCESS

SWDL_NEPKGCHECK

SWDL_PKG_NOBDSOFT

SWDL_PKGVER_MM

SWDL_ROLLBACK_FAIL

SYNC_C_LOS TEMP_ALARM

WRG_BD_TYPE

WRG_DEV_TYPE

BIOS_STATUS

- -

A.2.2 CSHAPS_FAIL APS_INDI APS_MANUA

L_STOPBD_NOT_INSTALLED

BD_STATUS

BOOTROM_BAD

CFCARD_FAILED

CFCARD_FULL

CFCARD_OFFLINE

CFCARD_W_R_DISABLED

DBMS_ERROR

DBMS_PROTECT_MODE

EXT_SYNC_LOS

HARD_BAD K1_K2_M

K2_M LAG_BWMM LCS_MISMATCH

LPS_UNI_BI_M

LTI

NESOFT_MM NESF_LOST NESTATE_INSTALL

NP1_MANUAL_STOP

NP1_SW_FAIL

NP1_SW_INDI POWER_ALM RPS_INDI RTC_FAIL S1_SYN_CHANGE

SWDL_ACTIVATED_TIMEOUT

SWDL_AUTOMATCH_INH

SWDL_CHGMNG_NOMATCH

SWDL_COMMIT_FAIL

SWDL_INPROCESS

SWDL_NEPKGCHECK

SWDL_PKG_NOBDSOFT

SWDL_PKGVER_MM

SWDL_ROLLBACK_FAIL

SYNC_C_LOS




Issue 05 (2010-07-30)

TEMP_ALARM

WRG_BD_TYPE

WRG_DEV_TYPE

BIOS_STATUS

-

A.2.3 IF1AU_AIS AU_LOP B1_EXC B1_SD B2_EXC

B2_SD B3_EXC B3_SD BD_STATUS HARD_BAD

HP_CROSSTR HP_LOM HP_RDI HP_REI HP_SLM

HP_TIM HP_UNEQ IF_CABLE_OPEN

IF_MODE_UNSUPPORTED

LCS_LIMITED

LICENSE_LOST

LOOP_ALM MS_AIS MS_CROSSTR MS_RDI

MS_REI MSAD_CROSSTR

MW_FEC_UNCOR

MW_LIM MW_LOF

MW_RDI R_LOC R_LOF R_LOS RS_CROSSTR

T_LOC TEMP_ALARM

VOLT_LOS WRG_BD_TYPE

-

A.2.4 IFU2AM_DOWNSHIFT

BD_STATUS BIP_EXC BIP_SD BUS_ERR

HARD_BAD IF_CABLE_OPEN

LCS_LIMITED LICENSE_LOST

LOOP_ALM

LP_RDI LP_REI LP_UNEQ MW_BER_EXC

MW_BER_SD

MW_FEC_UNCOR

MW_LIM MW_LOF MW_RDI R_LOC

R_LOF TEMP_ALARM

TU_AIS TU_LOP VOLT_LOS

WRG_BD_TYPE

MW_CFG_MISMATCH

- - -



A-11

A.2.5 IFX2

AM_DOWNSHIFT

BD_STATUS BIP_EXC BIP_SD BUS_ERR

HARD_BAD IF_CABLE_OPEN

LCS_LIMITED LICENSE_LOST

LOOP_ALM

LP_RDI LP_REI LP_UNEQ MW_BER_EXC

MW_BER_SD

MW_FEC_UNCOR

MW_LIM MW_LOF MW_RDI R_LOC

R_LOF TEMP_ALARM

TU_AIS TU_LOP VOLT_LOS

WRG_BD_TYPE

XPIC_LOS MW_CFG_MISMATCH

- -

A.2.6 SL1D

AU_AIS AU_LOP B1_EXC B1_SD B2_EXC

B2_SD B3_EXC B3_SD BD_STATUS HARD_BAD

HP_CROSSTR HP_LOM HP_RDI HP_REI HP_SLM

HP_TIM HP_UNEQ IN_PWR_HIGH

IN_PWR_LOW J0_MM

LASER_CLOSED

LASER_MOD_ERR_EX

LOOP_ALM LSR_NO_FITED

MS_AIS

MS_CROSSTR MS_RDI MS_REI MSAD_CROSSTR

R_LOC

R_LOF R_LOS RS_CROSSTR T_LOC WRG_BD_TYPE

A.2.7 EM6T

BD_STATUS COMMUN_FAIL

ETH_CFM_LOC

ETH_CFM_MISMERGE

ETH_CFM_RDI

ETH_CFM_UNEXPERI

ETH_EFM_DF ETH_EFM_EVENT

ETH_EFM_LOOPBACK

ETH_EFM_REMFAULT

ETH_LOS ETHOAM_SELF_LOOP

FLOW_OVER HARD_BAD LAG_DOWN




Issue 05 (2010-07-30)

LAG_MEMBER_DOWN

LOOP_ALM MULTI_RPL_OWNER

TEMP_ALARM

WRG_BD_TYPE

A.2.8 EM6F

BD_STATUS COMMUN_FAIL

ETH_CFM_LOC

ETH_CFM_MISMERGE

ETH_CFM_RDI

ETH_CFM_UNEXPERI

ETH_EFM_DF ETH_EFM_EVENT

ETH_EFM_LOOPBACK

ETH_EFM_REMFAULT

ETH_LOS ETHOAM_SELF_LOOP

FLOW_OVER HARD_BAD LAG_DOWN

LAG_MEMBER_DOWN

LASER_MOD_ERR

WRG_BD_TYPE

LOOP_ALM LSR_NO_FITED

MULTI_RPL_OWNER

TEMP_ALARM

- - -

A.2.9 SP3S/SP3D

A_LOC BD_STATUS BIP_EXC BIP_SD DOWN_E1_AIS

E1_LOC E1_LOS HARD_BAD HPAD_CROSSTR

LOOP_ALM

LP_CROSSTR LP_R_FIFO LP_RDI LP_REI LP_RFI

LP_SIZE_ERR LP_SLM LP_T_FIFO LP_TIM LP_UNEQ

R_F_RST R_S_ERR RP_LOC T_ALOS T_F_RST

TU_AIS TU_LOP UP_E1_AIS WRG_BD_TYPE

-

A.2.10 AUX

BD_STATUS HARD_BAD RELAY_ALARM_CRITICAL

RELAY_ALARM_IGNORE

RELAY_ALARM_MAJOR

RELAY_ALARM_MINOR

WRG_BD_TYPE

- - -



A-13

A.2.11 PIU

BD_STATUS POWER_ABNORMAL

THUNDERALM WRG_BD_TYPE

A.2.12 FAN

BD_STATUS FAN_AGING FAN_FAIL POWER_ALM WRG_BD_TYPE

A.2.13 ODU

BD_STATUS CONFIG_NOSUPPORT

HARD_BAD IF_INPWR_ABN

LOOP_ALM POWER_ALM RADIO_FADING_MARGIN_INSUFF

RADIO_MUTE

RADIO_RSL_BE-YONDTH

RADIO_RSL_HIGH

RADIO_RSL_LOW RADIO_TSL_HIGH

RADIO_TSL_LOW TEMP_ALARM WRG_BD_TYPE -

A.3 Alarms and Handling ProceduresThis topic describes all the alarms on the OptiX RTN 950 in alphabetical order and how to handlethese alarms.

A.3.1 A_LOC

Description

The A_LOC is an alarm indicating that a clock signal is lost in the uplink bus.

Attribute

Alarm Severity Alarm Type

Major Equipment alarm

Parameters

None.




Issue 05 (2010-07-30)

Impact on the SystemWhen the A_LOC alarm occurs, the services carried by the board are interrupted.

Possible CausesCause 1: Board failure occurs.

Procedure

Step 1 Cause 1: Board failure occurs.(1) Replace the board where the tributary unit that reports the alarm is located.

----End

Related InformationNone.

A.3.2 AM_DOWNSHIFT

DescriptionThe AM_DOWNSHIFT is an alarm indicating the downshift of the AM scheme. This alarmoccurs when the AM scheme is downshifted from the highest-efficiency scheme to the lower-efficiency scheme. When the AM scheme is upshifted from the lower-efficiency scheme to thehighest-efficiency scheme, this alarm is cleared.

Attribute


Major Communication alarm

ParametersNone.

Impact on the SystemWhen the AM_DOWNSHIFT alarm occurs, the transmission capacity is reduced.

Possible CausesThe possible cause of the AM_DOWNSHIFT alarm is that working channels are degraded.l Cause 1: The external factors (for example, the climate) cause the degradation of the

working channels.l Cause 2: There are interferences around the working channels.

l Cause 3: The ODU at the transmit end has abnormal transmit power.



A-15

l Cause 4: The ODU at the receive end has abnormal receive power.

Procedure

Step 1 Cause 1: The external factors (for example, the climate) cause the degradation of the workingchannels.

(1) When the external factors (for example, the climate) cause the degradation of the workingchannels, the downshift of the AM scheme is normal. Hence, no measures should be takento handle the alarm.

Step 2 Cause 2: There are interferences around the working channels.

(1) Eliminate the interferences around the working channels.

Step 3 Cause 3: The ODU at the transmit end has abnormal transmit power.

(1) Use the NMS to check whether the transmit power of the ODU at the transmit end is normal.For details on troubleshooting at the transmit end, see Troubleshooting MicrowaveLinks.

Step 4 Cause 4: The ODU at the receive end has abnormal receive power.

(1) Use the NMS to check whether the receive power of the ODU at the receive end is normal.For details on troubleshooting at the receive end, see Troubleshooting MicrowaveLinks.

----End

Related Information

None.

A.3.3 APS_FAIL

Description

The APS_FAIL is an alarm indicating that the MS protection switching fails.

Attribute



Parameters

When you view an alarm on the network management system, select the alarm. In the AlarmDetails field display the related parameters of the alarm. The alarm parameters are in thefollowing format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the followingtable.




Issue 05 (2010-07-30)

Name Meaning

Parameter 1 Indicates the type of the protection group.

l 0x01: linear MS protection

l 0x02: ring MS protection

Parameter 2 Indicates the ID of the protection group that reports the alarm. For example, 0x01indicates that the alarm is reported by protection group 1.

Impact on the System

When the APS_FAIL alarm occurs, the services cannot be switched. If the current paths areunavailable, the services are interrupted.

Possible Causesl Cause 1: The parameters of the MSP protocol are set incorrectly.

l Cause 2: The parameters of the MSP protocol are lost.

Procedure

Step 1 Cause 1: The parameters of the MSP protocol are set incorrectly.(1) Check whether the parameters of the MSP protocol are set correctly.

If... Then...

The parameters are set incorrectly Set the parameters correctly.

The parameters are set correctly Go to the next step.

Step 2 Cause 2: The parameters of the MSP protocol are lost.(1) Check whether the MSP protocol is normal on the network.(2) Check whether the MSP protocol is normal on the network. For details, see Enabling/

Disabling the linear MSP protocol.

If... Then...

The alarm is cleared after the protocol isrestarted

End the alarm handling.

The alarm persists after the protocol isrestarted

Contact Huawei engineers to handle thealarm.

----End

Related Information

None.

A.3.4 APS_INDI



A-17

DescriptionThe APS_INDI is an alarm indicating that the MS protection switching occurs.

Attribute



ParametersWhen you view an alarm on the network management system, select the alarm. In the AlarmDetails field display the related parameters of the alarm. The alarm parameters are in thefollowing format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the followingtable.

Name Meaning


l 0x01: linear MS protection.

l 0x02: ring MS protection.


Impact on the SystemDuring the switching (≤ 50 ms), the service is interrupted. After the switching is complete, theservices are restored to normal. In the case of 1:N protection, after the switching starts and beforethe switching is complete, the extra traffic is interrupted.

Possible CausesCause 1: The linear MS protection switching occurs.

Procedure

Step 1 Cause 1: The linear MS protection switching occurs.(1) Query the linear MSP group.(2) Check whether the MSP protocol is in the manual switching state, forced switching state,

or locked switching state. If yes, release the switching and check whether the alarm iscleared.

(3) Check whether the MSP protocol is in the automatic switching state. Do as follows:

a. Handle the R_LOS, R_LOF, MS_AIS, B2_EXC, or B2_SD alarm that the equipmentreports. After the alarms are cleared, wait until the MSP protocol is changed from theautomatic switching state to the normal state. Then, check whether the APS_INDIalarm is cleared.




Issue 05 (2010-07-30)

b. Check whether the service board configured with the MSP protocol is faulty. If yes,replace the faulty board and then check whether the APS_INDI alarm is cleared.

c. Check whether the currently working system control and cross-connect board is faulty.If the currently working system control and cross-connect board is faulty and aprotection system control and cross-connect board is available, switch the service tothe protection system control and cross-connect board and replace the faulty systemcontrol and cross-connect board. Then, check whether the APS_INDI alarm iscleared.

----End

Related Information

None.

A.3.5 APS_MANUAL_STOP

Description

The APS_MANUAL_STOP is an alarm indicating that the MSP protocol is stopped manually.

Attribute


Minor Processing alarm

Parameters


Name Meaning


l 0x01: linear MS protection.




When the APS_MANUAL_STOP alarm occurs, the MSP protocol may fail and thus theprotection switching may fail.



A-19

Possible CausesCause 1: The MSP protocol is stopped manually.

Procedure

Step 1 Cause 1: The MSP protocol is stopped manually.(1) Enable/Disable the linear MSP protocol.

----End


A.3.6 AU_AIS

DescriptionThe AU_AIS is an alarm indicating the administrative unit (AU). This alarm occurs when theboard detects the AU pointer of all 1s for three consecutive frames.

Attribute



ParametersNone.

Impact on the SystemWhen the AU_AIS alarm occurs, the service in the AU-4 path that reports the alarm isinterrupted. If the service is configured with protection, protection switching may be triggered.

Possible Causesl Cause 1: The opposite NE inserts the AU_AIS alarm.

l Cause 2: The transmit unit of the opposite NE is faulty.

l Cause 3: The receive unit of the local NE is faulty.

Procedure

Step 1 Cause 1: The opposite NE inserts the AU_AIS alarm.

If... Then...

The alarm that triggers the AU_AIS insertion occurs Clear the alarm immediately.




Issue 05 (2010-07-30)

If... Then...

No such alarms that trigger the AU_AIS insertion occur Go to Cause 2.

Step 2 Cause 2: The transmit unit of the opposite NE is faulty.(1) Replace the board where the line unit is located or the IF board.

If... Then...

The alarm is cleared after the board isreplaced

The fault is rectified. End the alarmhandling.

The alarm persists after the board isreplaced

Go to the next step.

(2) Replace the system control board on the opposite NE.

Step 3 Cause 3: The receive unit of the local NE is faulty.(1) Replace the board that reports the alarm.

----End


A.3.7 AU_LOP

DescriptionThe AU_LOP is an alarm indicating the loss of the AU pointer. This alarm occurs when a boarddetects the AU pointer of invalid values or with the NDF for eight consecutive frames.

Attribute



ParametersNone.

Impact on the SystemWhen the AU_LOP alarm occurs, the service in the AU-4 path that reports the alarm isinterrupted. If the service is configured with protection, protection switching may be triggered.

Possible Causesl Cause 1: The transmit unit of the opposite NE is faulty.




A-21

Procedure

Step 1 Cause 1: The transmit unit of the opposite NE is faulty.(1) Replace the board where the line unit is located on the opposite NE.

If... Then...





(2) Replace the system control board on the opposite NE.

Step 2 Cause 2: The receive unit of the local NE is faulty.(1) Replace the board that reports the alarm.

----End


A.3.8 B1_EXC

DescriptionThe B1_EXC is an alarm indicating that the B1 errors (in the regenerator section) exceed thethreshold. This alarm occurs when the board detects that the B1 errors exceed the preset B1_EXCalarm threshold (10-3 by default).

An IF board that works in PDH mode may also report this alarm. This alarm is detected by usingthe self-defined overhead byte B1 in PDH microwave frames.

Attribute


Minor Service alarm

ParametersNone.

Impact on the SystemWhen the B1_EXC alarm occurs, the services on the port are interrupted.

Possible Causesl Cause 1: The line performance degrades (if the alarm is reported by an SDH optical interface

board).




Issue 05 (2010-07-30)

l Cause 2: The line performance degrades (if the alarm is reported by an IF board).

l Cause 3: The network clock quality degrades.

l Cause 4: The board is faulty (if the alarm is reported by an SDH optical interface board).

l Cause 5: The board is faulty (if the alarm is reported by an IF board).

Procedure

Step 1 Cause 1: The line performance degrades (if the alarm is reported by an SDH optical interfaceboard).

(1) Check whether the transmit power at the opposite end and the receive power at the localend meet the specifications of the optical interfaces. For details, see 8.3.5 BrowsingCurrent Performance Events.

If... Then...

The transmit power of the opposite NE isover low

Replace the board where the SDHoptical interface unit is located on theopposite NE.

The transmit power of the opposite NE isnormal, but the receive power of the localNE is close to the value (for example,within ±3 dB) of the receiver sensitivity.

The fiber is faulty. Go to the next step.

(2) Exchange the core fibers of the optical cables in the receive and transmit directions of achannel.

If... Then...

The errors vary with the change of the fiber The fiber is faulty. Go to the next step.

The errors do not vary with the change of thefiber.

Ensure that the board is normal.

(3) If the fiber is faulty, check whether the fiber jumper from the equipment to the opticaldistribution frame (ODF) and the fiber that is led out of the equipment room are pressed,and whether the fiber connector is dirty. If yes, replace the fiber jumper or fiber connector.

Step 2 Cause 2: The line performance degrades (if the alarm is reported by an IF board).

(1) Check whether the MW_FEC_UNCOR or RPS_INDI alarm is reported. If yes, clear thealarm.

Step 3 Cause 3: The network clock quality degrades.

(1) Check the network clock status of the NE that reports the alarm.

If... Then...

The clock source of the local NE isdifferent from the clock source of theopposite NE

The clock may become asynchronous and B1errors may occur. Reconfigure the clocksource, and ensure that the clock issynchronized on the local NE and oppositeNE.



A-23

If... Then...

The clock of the local NE and the clockof the opposite NE form a timing loop

This may cause errors and even serviceinterruption. In this case, reconfigure the clocksource and release the timing loop.

Step 4 Cause 4: The board is faulty (if the alarm is reported by an SDH optical interface board).(1) The board of the SDH line unit on the local NE is faulty. Loop back the optical interfaces

of the NE by using a fiber jumper to locate the fault.

If... Then...

The fault is not rectified after the opticalinterfaces are looped back

Replace the board where the tributaryunit that reports the alarm is located onthe local NE.

The fault is rectified after the opticalinterfaces are looped back

Replace the board where the line unit islocated on the opposite NE.

Step 5 Cause 5: The board is faulty (if the alarm is reported by an IF board).(1) Perform an inloop for the multiplexing interface of the IF board on the local NE.

If... Then...

The fault is not rectified after themultiplexing interface is looped back

Replace the IF board that reports thealarm on the local NE.

The fault is rectified after the multiplexinginterface is looped back

Replace the IF board that reports thealarm on the opposite NE.

----End

Related Information

Handle the errors of TDM services.

A.3.9 B1_SD

Description

The B1_SD is an alarm indicating that the signal degrades due to the excessive B1 errors (in theregenerator section). This alarm occurs when the board detects that the B1 errors exceed thepreset B1_SD alarm threshold (10-6 by default) but do not reach the preset B1_EXC alarmthreshold (10-3 by default).

An IF board that works in PDH mode may also report this alarm. This alarm is detected by usingthe self-defined overhead byte B1 in PDH microwave frames.

Attribute


Minor Service alarm




Issue 05 (2010-07-30)

Parameters

None.


When the B1_SD alarm occurs, the service performance on the port degrades.

If the alarm is reported by an IF board and the equipment is configured with the 1+1 FD/SDprotection, the HSM switching is triggered.


board).l Cause 2: The line performance degrades (if the alarm is reported by an IF board).




Procedure

Step 1 Cause 1: The line performance degrades (if the alarm is reported by an SDH optical interfaceboard).(1) Check whether the transmit power at the opposite end and the receive power at the local

end meet the specifications of the optical interfaces. For details, see 8.3.5 BrowsingCurrent Performance Events.

If... Then...



The transmit power of the opposite NE isnormal, but the receive power of the localNE is close to the value (for example,within ±3 dB) of the receiver sensitivity


(2) Exchange the core fibers of the optical cables in the receive and transmit directions of achannel.

If... Then...


The errors do not vary with the change of thefiber



Step 2 Cause 2: The line performance degrades (if the alarm is reported by an IF board).



A-25

(1) Check whether the MW_FEC_UNCOR alarm is generated. If yes, clear the alarm.

Step 3 Cause 3: The network clock quality degrades.(1) Check the network clock status of the NE that reports the alarm.

If... Then...


The clock may become asynchronous anderrors may occur. Reconfigure the clocksource, and ensure that the clock issynchronized on the local NE and oppositeNE.



Step 4 Cause 4: The board is faulty (if the alarm is reported by an SDH optical interface board).(1) The SDH optical line board of the local NE is faulty. Loop back the optical interfaces of

the NE by using a fiber jumper to locate the fault.

If... Then...






If... Then...





----End

Related InformationHandle the errors of TDM services.

A.3.10 B2_EXC

DescriptionThe B2_EXC is an alarm indicating that the B2 errors (in the multiplex section) exceed thethreshold. This alarm occurs when the board detects that the number of B2 errors exceeds thepreset B2_EXC alarm threshold (10-3 by default).




Issue 05 (2010-07-30)

Attribute


Major Service alarm

Parameters

None.


The services on the port are interrupted.


board).





Procedure



If... Then...





(2) Exchange the core fibers of the optical cables in the receive and transmit directions of achannel to locate the fault.

If... Then...






A-27


Step 2 Cause 2: The line performance degrades (if the alarm is reported by an IF board).(1) Check whether the MW_FEC_UNCOR or RPS_INDI alarm is reported. If yes, clear the

alarm.


If... Then...







If... Then...






If... Then...





----End

Related Information


A.3.11 B2_SD




Issue 05 (2010-07-30)

DescriptionThe B2_SD is an alarm indicating that the signal degrades due to the excessive B2 errors (in themultiplex section). This alarm occurs when the board detects that the number of B2 errorsexceeds the preset B2_EXC alarm threshold (10-6 by default).

Attribute


Minor Service alarm

ParametersNone.

Impact on the SystemThe service performance on the port degrades.







Procedure



If... Then...



The transmit power of the opposite NE isnormal, but the receive power of the localNE is close to the value (for example,within ± 3dB) of the receiver sensitivity





A-29

If... Then...





Step 2 Cause 2: The line performance degrades (if the alarm is reported by an IF board).(1) Check whether the MW_FEC_UNCOR alarm is generated. If yes, clear the alarm.


If... Then...





Step 4 Cause 4: The board is faulty (if the alarm is reported by an SDH optical interface board).(1) The SDH optical/electrical line board of the local NE is faulty. Loop back the optical

interfaces of the station by using a fiber jumper to locate the fault.

If... Then...






If... Then...





----End





Issue 05 (2010-07-30)

A.3.12 B3_EXC

Description

The B3_EXC is an alarm indicating that the B3 errors (in the higher order path) exceed thethreshold. This alarm occurs when the board detects that the number of B3 errors exceeds thepreset B3_EXC alarm threshold (10-3 by default).

Attribute


Major Service alarm

Parameters

None.


When the B3_EXC alarm occurs, the service on the path that reports the alarm is interrupted.






Procedure



If... Then...







A-31


If... Then...





Step 2 Cause 2: The line performance degrades (if the alarm is reported by an IF board).(1) Check whether the MW_FEC_UNCOR or RPS_INDI alarm is reported. If yes, clear the

alarm.


If... Then...


In this case, the clock may becomeasynchronous and errors may occur.Reconfigure the clock source, and ensure thatthe clock is synchronized on the local NE andopposite NE.





If... Then...






If... Then...





----End




Issue 05 (2010-07-30)

Related Information


A.3.13 B3_SD

Description

The B3_SD is an alarm indicating that the signal degrades due to the excessive B3 errors (in thehigher order path). This alarm occurs when the board detects that the number of B3 errors exceedsthe preset B3_SD alarm threshold (10-6 by default).

Attribute


Minor Service alarm

Parameters

None.


The service performance on the port degrades.



board).





Procedure





A-33

If... Then...






If... Then...





Step 2 Cause 2: The line performance degrades (if the alarm is reported by an IF board).(1) Check whether the MW_FEC_UNCOR alarm is generated. If yes, clear the alarm.


If... Then...


In this case, the clock may becomeasynchronous and errors may occur.Reconfigure the clock source, and ensure thatthe clock is synchronized on the local NE andopposite NE.



Step 4 Cause 4: The board is faulty (if the alarm is reported by an SDH optical interface board).(1) The SDH optical/electrical line board of the local NE is faulty. Loop back the optical

interfaces of the station by using a fiber jumper to locate the fault.

If... Then...





Step 5 Cause 5: The board is faulty (if the alarm is reported by an IF board).




Issue 05 (2010-07-30)

(1) Perform an inloop for the multiplexing interface of the IF board on the local NE.

If... Then...





----End

Related Information

None.

A.3.14 BD_NOT_INSTALLED

Description

The BD_NOT_INSTALLED is an alarm indicating that the physical board is installed in acertain slot, but the logical board is not added.

Attribute


Minor Equipment alarm

Parameters


Name Meaning

Parameter 1, Parameter 2 Indicates the ID of the slot.


When the BD_NOT_INSTALLED alarm occurs, the physical board in this slot cannot work.

Possible Causesl Cause 1: The logical board is not added in the corresponding logical slot.

l Cause 2: The physical board is installed incorrectly during the replacement of boards.



A-35

Procedure

Step 1 Cause 1: The logical board is not added in the corresponding logical slot.(1) Configure the logical board.

Step 2 Cause 2: The physical board is installed incorrectly during the replacement of boards.(1) Check whether the physical board is installed in the correct slot. If not, reinstall the physical

board in the correct slot.

----End

Related Information

None.

A.3.15 BD_STATUS

Description

The BD_STATUS is an alarm indicating that the board is not in position.

Attribute



Parameters

None.


When the BD_STATUS alarm occurs, the board that reports the alarm fails to work.

Possible Causes

If the alarm is reported by a board of the IDU, the possible causes are as follows:l Cause 1 of the alarm reported by a board of the IDU: The board is installed in an incorrect

slot.l Cause 2 of the alarm reported by a board of the IDU: The board and the backplane are not

connected properly.l Cause 3 of the alarm reported by a board of the IDU: The slot is faulty.

l Cause 4 of the alarm reported by a board of the IDU: The board is faulty.

If the alarm is reported by the ODU, the possible causes are as follows:l Cause 1 of the alarm reported by the ODU: The other alarms are generated.

l Cause 2 of the alarm reported by the ODU: The ODU is faulty.




Issue 05 (2010-07-30)

Procedure

Step 1 Cause 1 of the alarm reported by a board of the IDU: The board is installed in an incorrect slot.(1) Check whether the logical slot and physical slot of the board that reports the alarm are

consistent. For details, see 8.3.2 Checking the Board Status.

If... Then...

The board that reports the alarm isinstalled in an incorrect slot

Install the board in a correct slot.

The board that reports the alarm isinstalled in a correct slot

Ensure that the board and the backplaneare connected properly.

Step 2 Cause 2 of the alarm reported by a board of the IDU: The board and the backplane are notconnected properly.(1) Remove and insert the board that reports the alarm.

If... Then...

The alarm is cleared after the board isremoved and inserted


The alarm persists after the board isremoved and inserted


Step 3 Cause 3 of the alarm reported by a board of the IDU: The slot is faulty.(1) Contact Huawei engineers to handle the fault of the slot.

TIPGenerally, the slot becomes faulty due to the broken pin or bent pin. Remove the board, and use atorch to observe whether there is any broken pin or bent pin.

(2) If an idle slot is available, insert the board in the idle slot and add the board again. Then,the board can work normally.

Step 4 Cause 4 of the alarm reported by a board of the IDU: The board is faulty.(1) Replace the board that reports the alarm.

If... Then...




Ensure that the slot is normal.

Step 5 Cause 1 of the alarm reported by the ODU: The other alarms are generated.(1) Query whether the IF board reports the HARD_BAD, BD_STATUS,

IF_CABLE_OPEN, or VOLT_LOS alarm.

If... Then...

The IF board reports any of thepreceding alarms

Clear the alarm immediately.

The IF board does not report any of thepreceding alarms

Replace the board that reports the alarm.



A-37

Step 6 Cause 2 of the alarm reported by the ODU: The ODU is faulty.(1) Replace the board that reports the alarm.

----End

Related Information

None.

A.3.16 BIOS_STATUS

Description

The BIOS_STATUS is an alarm indicating that the board is in BIOS state.

Attribute


Major Processing alarm

Parameters

Name Meaning

Parameter 1 Indicates the higher eight bits of the dual-byte ID of the board that is inBIOS state.

Parameter 2 Indicates the lower eight bits of the dual-byte ID of the board that is in BIOSstate.

Parameters 3 to 5 Parameters 3 to 5 are reserved, and their values are always 0xff.


When the alarm occurs, services are interrupted.

Possible Causesl Cause 1: The board is reset for three times continuously.

l Cause 2: The board software is lost.

l Cause 3: The board software becomes abnormal.

Procedure

Step 1 Perform a cold reset on the standby SCC, cross-connect, and clock board that reports the alarm,and then check whether the alarm is cleared.

Step 2 If the alarm persists, remove the standby SCC, cross-connect, and clock board, and thenreseat the board.




Issue 05 (2010-07-30)

Step 3 If the alarm persists, replace the board.

----End


A.3.17 BIP_EXC

DescriptionThe BIP_EXC is an alarm indicating that the BIP errors exceed the threshold. This alarm occurswhen the board detects that the number of BIP-2 errors (in byte V5) exceeds the preset BIP_EXCalarm threshold (10-3 by default).

Attribute


Minor Service alarm

ParametersNone.

Impact on the SystemWhen the BIP_EXC alarm occurs, the service on the path that reports the alarm is interrupted.

Possible Causesl Cause 1: The line performance degrades (if the alarm is reported by an E1 service board).

l Cause 2: The line performance degrades (if the alarm is reported by a Hybrid IF board).

l Cause 3: The board is faulty (if the alarm is reported by an E1 service board).

l Cause 4: The board is faulty (if the alarm is reported by a Hybrid IF board).

Procedure

Step 1 Cause 1: The line performance degrades (if the alarm is reported by an E1 service board).(1) Check whether the performance degradation alarm occurs on the STM-1 path or radio link

along which the E1 service signal travels. If yes, clear the alarm immediately.

The common line performance degradation alarms are as follows:

B1_EXC, B1_SD, B2_EXC, B2_SD, B3_EXC, B3_SD, MW_FEC_UNCOR,RPS_INDI, MW_BER_EXC, and MW_BER_SD.

If... Then...

There is any of the preceding alarms Clear the alarm immediately.



A-39

If... Then...

No such alarms occur Ensure that the board is normal.

Step 2 Cause 2: The line performance degrades (if the alarm is reported by a Hybrid IF board).(1) Check whether any alarm occurs on the tributary board or IF board that transmits the service

signal. If yes, clear the alarm immediately.

Step 3 Cause 3: The board is faulty (if the alarm is reported by an E1 service board).(1) Replace the board where the E1 service unit is located. Then, check whether the alarm

is cleared.

If... Then...

The alarm is cleared End the alarm handling.

The alarm persists Replace the system control and cross-connect board.

Step 4 Cause 4: The board is faulty (if the alarm is reported by a Hybrid IF board).(1) Replace the Hybrid IF board. Then, check whether the alarm is cleared.

If... Then...



----End


A.3.18 BIP_SD

DescriptionThe BIP_SD is an alarm indicating that the signal degrades due to the BIP errors. This alarmoccurs when the board detects that the number of BIP-2 errors (in byte V5) exceeds the presetBIP_SD alarm threshold (10-6 by default).

Attribute


Minor Service alarm

ParametersNone.

Impact on the SystemWhen the BIP_SD alarm occurs, the service on the path that reports the alarm degrades.




Issue 05 (2010-07-30)

Possible Causesl Cause 1: The line performance degrades (if the alarm is reported by an E1 service board).

l Cause 2: The line performance degrades (if the alarm is reported by a Hybrid IF board).

l Cause 3: The board is faulty (if the alarm is reported by an E1 service board).

l Cause 4: The board is faulty (if the alarm is reported by a Hybrid IF board).

Procedure

Step 1 Cause 1: The line performance degrades (if the alarm is reported by an E1 service board).

(1) Check whether the performance degradation alarm occurs on the STM-1 path or radio linkalong which the E1 service signal travels. If yes, clear the alarm immediately.

The common line performance degradation alarms are as follows:

B1_EXC, B1_SD, B2_EXC, B2_SD, B3_EXC, B3_SD, MW_FEC_UNCOR,RPS_INDI, MW_BER_EXC, and MW_BER_SD.

If... Then...

There is any of the preceding alarms Clear the alarm immediately.

No such alarms occur Ensure that the board is normal.

Step 2 Cause 2: The line performance degrades (if the alarm is reported by a Hybrid IF board).

(1) Check whether any alarm occurs on the tributary board or IF board that transmits the servicesignal.

If... Then...

An alarm occurs Clear the alarm immediately.

No alarm occurs Ensure that the board is normal.

Step 3 Cause 3: The board is faulty (if the alarm is reported by an E1 service board).

(1) Replace the board where the E1 service unit is located. Then, check whether the alarmis cleared.

If... Then...



Step 4 Cause 4: The board is faulty (if the alarm is reported by a Hybrid IF board).

(1) Replace the Hybrid IF board. Then, check whether the alarm is cleared.

If... Then...



----End



A-41


A.3.19 BOOTROM_BAD

DescriptionThe BOOTROM_BAD is an alarm indicating that the BOOTROM data consistency check fails.This alarm occurs when the BOOTROM data is damaged during a periodical check by thesystem.

Attribute




Name Meaning

Parameter 1 The value is always 0x01.

Parameter 2, Parameter 3 Indicates the type of the BOOTROM damage.l 0x00, 0x01: damage of the basic BIOS

l 0x00, 0x02: damage of the extended BIOS

Parameter 4, Parameter 5 The values are always 0xff 0xff.

Impact on the SystemWhen the BOOTROM_BAD alarm occurs, it indicates that errors occur in the system databaseprocessing. The system configuration may be lost. As a result, the failure indication is returnedfor certain query and setting commands, and certain system functions cannot work.

l When the NE is already started, the BOOTROM_BAD alarm does not affect the systemand services.

l If the BOOTROM_BAD alarm occurs and a hard reset is performed on a board, the boardfails to load the BIOS and cannot be started.

Possible Causesl Cause 1: The basic BIOS is damaged.

l Cause 2: The extended BIOS is damaged.




Issue 05 (2010-07-30)

l Cause 3: The BOOTROM database is damaged.

Procedure

Step 1 Replace the board that reports the alarm.

----End

Related Information

None.

A.3.20 BUS_ERR

Description

The BUS_ERR is an alarm of bus errors. This alarm occurs when the bus becomes abnormal.

Attribute


Critical Equipment alarm

Parameters


Name Meaning

Parameter 1 Indicates the type of bus errors.

l 0x01: BUS_LOS.

l 0x02: BUS_OOF.

l 0x03: BUS_LOF.

l 0x04: BUS_OOA.

l 0x05: BUS_RX_DOWN.

l 0x06: BUS_TX_DOWN.

l 0x07: BUS_SPI_DOWN.

l 0x08: BUS_SCI_ERR.

l 0x09: BUS_OPP_CLK_LOC.

Parameter 2 Indicates the ID of the bus that has errors.



A-43

Impact on the Systeml When the BUS_ERR alarm occurs, the services that travel along the faulty bus are

interrupted or have errors.

l The HARD_BAD alarm suppresses the report of the BUS_ERR alarm.

Possible Causes

The possible causes of the BUS_ERR alarm are as follows:

l Cause 1: The board is not properly inserted.

l Cause 2: Board failure occurs.

Procedure

Step 1 Cause 1: The board is not properly inserted.

(1) Remove and insert the board.

Step 2 Cause 2: Board failure occurs.

(1) Perform a hard reset on the board that reports the alarm. Then, check whether the alarmis cleared.

If... Then...

The alarm is cleared The fault is rectified. End the alarm handling.

The alarm persists Replace the board that reports the alarm.

----End

Related Information

None.

A.3.21 CFCARD_FAILED

Description

The CFCARD_FAILED is an alarm indicating that the operation on the CF card fails.

Attribute



Parameters

None.




Issue 05 (2010-07-30)


When the CFCARD_FAILED alarm occurs, the database cannot be backed up to the CF cardor be restored from the CF card. This alarm may cause rollback of the package loading upgrade.

Possible Causesl Cause 1: The CF card fails to be initialized.

l Cause 2: The file system of the CF card does not match.

l Cause 3: The system control and communication board is faulty, and the file system of theCF card fails to be created.

Procedure

Step 1 Cause 1: The CF card fails to be initialized.

Cause 2: The file system of the CF card does not match.

(1) Replace the CF card and check whether the alarm is cleared.

If... Then...

Yes End the alarm handling.

No Go to Cause 3.

Step 2 Cause 3: The system control and communication board is faulty, and the file system of the CFcard fails to be created.

(1) Check whether the HARD_BAD alarm occurs on the system control and communicationboard.

(2) If yes, perform a cold reset on the system control and communication board. Then, checkwhether the alarm is cleared.

If... Then...


No Replace the system control and communication board.

----End

Related Information

None.

A.3.22 CFCARD_FULL

Description

The CFCARD_FAILED is an alarm indicating that all capacity of the CF card is used



A-45

Attribute




Name Meaning

Parameter 1, Parameter 2 Indicates the slot number of the board where the CFCARD_FULLalarm is reported.

Parameter 3 Indicates the CF card number.

Parameter 4 Indicates the partition number of the CF card. Different bitscorrespond to different partitions. If the bit is 1, it indicates thatthis alarm is reported in this partition. If the bit is 0, it indicatesthat this alarm is not reported in this partition.

l bit[0] corresponds to SFS1.

l bit[1] corresponds to SFS2.

l bit[2] corresponds to SFS3.NOTE

Bit (0) is the least significant bit.

Parameters 5, Parameter 6 Reserved.

Impact on the SystemIn the case of the CFCARD_FULL alarm, services are not affected. The CFCARD_FULL alarmis reported to indicate that all capacity of the CF card is used and the new configuration datacannot be saved.

Possible CausesCause 1: The used capacity of the partitions of the CF card crosses the threshold, which is 80%of the capacity.

Procedure

Step 1 Cause 1: The used capacity of the partitions of the CF card crosses the threshold, which is 80%of the capacity.(1) Replace the CF card with one of a larger capacity. For details, see 6.7 Replacing the CF

Card.

----End




Issue 05 (2010-07-30)


A.3.23 CFCARD_OFFLINE

DescriptionThe CFCARD_OFFLINE is an alarm indicating that the CF card is out of service.

Attribute



ParametersNone.

Impact on the SystemWhen the CFCARD_OFFLINE alarm occurs, the database cannot be backed up to the CF cardor be restored from the CF card. This alarm may cause rollback of the package loading upgrade.

Possible Causesl Cause 1: The CF card is not inserted.

l Cause 2: The CF card is in poor contact with the system control and communication board.

l Cause 3: The CF card is faulty.

l Cause 4: The system control and communication board is faulty.

Procedure

Step 1 Cause 1: The CF card is not inserted.(1) Check whether the CF card is installed on the system control and communication board.

If... Then...

No Install the CF card.

Yes Go to Cause 2.

Step 2 Cause 2: The CF card is in poor contact with the system control and communication board.(1) Check whether the CF card is loosened. If yes, re-insert the CF card.(2) Check whether the alarm is cleared.

If... Then...


No Go to Cause 3.



A-47

Step 3 Cause 3: The CF card is faulty.(1) Replace the CF card.(2) Check whether the alarm is cleared.

If... Then...


No Go to Cause 4.

Step 4 Cause 4: The system control and communication board is faulty.(1) Check whether the HARD_BAD alarm occurs on the system control and communication

board.(2) If yes, perform a cold reset on the system control and communication board. Then, check

whether the alarm is cleared.(3) If the alarm persists, replace the system control and communication board.

----End

Related Information

None.

A.3.24 CFCARD_W_R_DISABLED

Description

The CFCARD_W_R_DISABLED is an alarm indicating that reading and writing the CF cardare disabled.

Attribute



Parameters

None.


When the CFCARD_R_R_DISABLED alarm occurs, the system is not affected. In this case,however, reading and writing the CF card are disabled. Consequently, the database cannot bebacked up to the CF card or be restored from the CF card. This alarm may cause rollback of thepackage loading upgrade.

Possible Causes

Cause 1: Hold the button on the CF card for more than five seconds.




Issue 05 (2010-07-30)

Procedure

Step 1 Cause 1: Hold the button on the CF card for more than 5 seconds.(1) Press the button on the CF card again for more than 5 seconds.

----End


A.3.25 CONFIG_NOSUPPORT

DescriptionThe CONFIG_NOSUPPORT is an alarm indicating that the configuration is not supported. Thisalarm is reported if the ODU detects that the specified parameters do not meet the requirementsof the ODU.

Attribute




Name Meaning

Parameter 1 Indicates that the configuration data does not meet the requirements.l 0x01: The frequency is set incorrectly.

l 0x02: The T/R spacing is set incorrectly.

l 0x03: The transmit power is set incorrectly.

l 0x04: The ATPC threshold is set incorrectly.

l 0x05: The bandwidth is set incorrectly.

l 0x06: The modulation mode is set incorrectly.

Impact on the SystemWhen the CONFIG_NOSUPPORT alarm occurs, the ODU fails to work normally. If theequipment is configured with the 1+1 FD protection, the active ODU generates theCONFIG_NOSUPPORT alarm. In this case, the IF 1+1 protection switching may be triggered.



A-49

Possible Causes

Cause 1: The type and configuration parameters of the ODU do not match the requirements.

Procedure

Step 1 Cause 1: The type and configuration parameters of the ODU do not match the requirements.

(1) Determine the parameter that does not meet the requirement according to the alarmparameter. Then, handle the fault accordingly.

If... Then...

The alarm parameter takes a value from0x01 to 0x03

Perform the operation described in Step1.2.

The alarm parameter takes a value from0x04 to 0x06

Perform the operation described in Step1.3.

(2) Check whether the parameters of the ODU interface meet the requirements of networkplanning. For details, see Setting the Parameters of ODU Ports.

If... Then...

The parameters meet the requirements ofnetwork planning

Use the ODU of the proper model.

The parameters do not meet therequirements of network planning

Modify the ODU interface parameters.

(3) Check whether the parameters of the IF interface meet the requirements of networkplanning. For details, see Configuring the IF/ODU Information of a Radio Link.

If... Then...

The parameters meet the requirements ofnetwork planning

Replace the IF board.

The parameters do not meet therequirements of network planning

Modify the IF interface parameters. Fordetails, see Configuring the IF/ODUInformation of a Radio Link.

----End

Related Information

None.

A.3.26 COMMUN_FAIL

Description

The COMMUN_FAIL is an alarm indicating the inter-board communication failure. This alarmis reported when the communication between a board and the SCC board is interrupted.




Issue 05 (2010-07-30)

Attribute



Parameters


Name Meaning

Parameter 1 Indicates the ID of the port. The value is always 0x01.

Parameter 2, Parameter 3 Indicates the ID of the path on which the alarm is generated.Parameter 2 is always 0x00. Parameter 3 has the followingmeanings:

l 0x03: inter-board Ethernet communication

Parameter 4, Parameter 5 Parameters 4 and 5 are reserved, and their values are always 0xFF.


The NE configuration cannot be delivered to the board or the board cannot work. Consequently,the services cannot be configured or the protection switching function is unavailable.

Possible Causesl Cause 1: A certain board is reset.

l Cause 2: A board and the backplane are connected improperly.

l Cause 3: A certain board is faulty.

l Cause 4: A slot is faulty.

Procedure

Step 1 Cause 1: A certain board is reset.

(1) After you reset the board, the alarm disappears automatically.

Step 2 Cause 2: A board and the backplane are connected improperly.

(1) Remove and insert the alarmed board. For details, see 6.1 Removing a Board and 6.2Inserting a Board. Then, check whether the alarm is cleared.



A-51

If... Then...

The alarm disappears after the board isremoved and inserted


The alarm persists after the board isreplaced.

Clear the alarm according to the solutionfor the alarm that is generated when aboard is faulty.

Step 3 Cause 3: A certain board is faulty.(1) Replace the board that reports the alarm, and then check whether the alarm is cleared. For

details, see 6 Part Replacement.

If... Then...

The alarm disappears after the board isreplaced



Clear the alarm according to the solutionfor the alarm that is generated when aslot is faulty.

Step 4 Cause 3: A slot is faulty.(1) Contact Huawei engineers to handle the faulty slot.

TIPThe slot becomes faulty due to broken pins or bent pins. Remove the board, and use a torch to checkwhether any pins are broken or bent.

(2) If an idle slot is available, insert the board in the idle slot, and then update the data on theNMS so that the board can work normally.

----End


A.3.27 DBMS_ERROR

DescriptionThe DBMS_ERROR is an alarm indicating that errors occur in the processing of the systemdatabase.

Attribute



ParametersWhen you view an alarm on the network management system, select the alarm. In the AlarmDetails field display the related parameters of the alarm. The alarm parameters are in the




Issue 05 (2010-07-30)

following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the followingtable.

Name Meaning

Parameter 1 Indicates the types of the database errors.l 0x01: The input parameters are illegal.

l 0x02: The database files do not exist.

l 0x03: The database memory area numbers are incorrect.

l 0x04: The database overwriting occurs.

l 0x05: Errors occur in the header information check in the database backuparea.

l 0x06: Errors occur in the FAT table structure check in the database storagearea.

l 0x07: Errors occur in the database check in the database backup area.

l 0x08: Recovering the database fails.

l 0x09: The database ID is invalid.

l 0x0A: The databases are different.

l 0x0B: The data is unchecked.

l 0x0E: The semaphore handle is invalid.

l 0x0F: Errors occur in applying for memory.

l 0x10: Errors occur in releasing memory.

l 0x12: Transmitting the message capsule fails.

l 0x13: The starting and ending records of the database are incorrect.

l 0x14: The database is null.

l 0x15: The flag is incorrectly set.

l 0x16: The input command parameters are incorrect.

l 0x17: Non-backup database.

l 0x18: The database is in the protection mode.

l 0x19: The configuration is not verified.

Parameter 2 Indicates the errored data storage area.l 0x00: database in fdb0

l 0x01: database in fdb1

l 0x02: database in drdb

Parameter 3 Indicates the ID of the errored database.l 0x00: all databases in the entire storage area.

l 0x01-0xff: ID of the errored database



A-53


When the DBMS_ERROR alarm occurs, it indicates that errors occur in the system databaseprocessing. The system configuration may be lost. As a result, the failure indication is returnedfor certain query and setting commands, and certain system functions cannot work.

Possible Causesl Cause 1: The database processing fails or the database is damaged.


Procedure

Step 1 Cause 1: The database processing fails or the database is damaged.

(1) Reset the system control board.

If... Then...

The alarm is cleared after the board isreset

End the fault handling.

The alarm persists after the board isreset

Ensure that the system control board isnormal.


(1) Replace the system control, cross-connect, and timing board.

----End

Related Information

None.

A.3.28 DBMS_PROTECT_MODE

Description

The DBMS_PROTECT_MODE is an alarm indicating that the system database is in protectionmode.

Attribute


Critical Processing alarm

Parameters

None.




Issue 05 (2010-07-30)

Impact on the SystemWhen the DBMS_PROTECT_MODE alarm occurs, it indicates that errors occur in the systemdatabase processing. The system configuration may be lost. As a result, the failure indication isreturned for certain query and setting commands, and certain system functions cannot work.

Possible CausesCause 1: The data enters the protection mode due to frequent resets of the NE software.

ProcedureStep 1 Cause 1: The data enters the protection mode due to frequent resets of the NE software.

(1) Replace the system control, cross-connect, and timing board.

----End


A.3.29 DOWN_E1_AIS

DescriptionThe DOWN_E1_AIS is an alarm of the 2 Mbit/s downlink signal. This alarm occurs when thetributary board detects the 2 Mbit/s downlink signal of all 1s.

Attribute


Minor Communication alarm


Name Meaning

Parameter 1 0x01, indicates optical interface number.

Parameter 2–Parameter 3 Indicates the number of the path.

Impact on the SystemWhen the DOWN_E1_AIS alarm occurs, the E1 signal in the path that reports the alarm isunavailable.



A-55

Possible Causesl Cause 1: The opposite NE transmits the E1_AIS alarm.

l Cause 2: On the local NE, the receive unit of the tributary board or the system control andcross-connect board is faulty.

Procedure

Step 1 Cause 1: The opposite NE transmits the E1_AIS alarm.(1) Check whether the opposite NE reports the UP_E1_AIS or T_ALOS alarm.

If... Then...

The opposite NE reports the UP_E1_AISor T_ALOS alarm

Clear the alarm immediately.

The opposite NE does not report theUP_E1_AIS or T_ALOS alarm

Ensure that the board on the local NE isnormal.

Step 2 Cause 2: On the local NE, the receive unit of the tributary board or the system control and cross-connect board is faulty.(1) Replace the board where the tributary unit that reports the alarm is located. Then,

check whether the alarm is cleared.

If... Then...


The alarm persists Replace the system control and cross-connect board on thelocal NE.

----End


A.3.30 E1_LOC

DescriptionThe E1_LOC is an alarm indicating that the uplink 2M clock is lost. This alarm occurs whenthe tributary board fails to extract the clock from the E1 signal.

Attribute



ParametersNone.




Issue 05 (2010-07-30)


When the E1_LOC occurs, the service is not affected.

Possible Causesl Cause 1: The opposite NE is faulty.

l Cause 2: The wiring sequence of the cable is incorrect.

l Cause 3: The receive unit of the tributary board on the local NE is faulty.

l Cause 4: The input E1 signal has an abnormal waveform.

Procedure

Step 1 Cause 1: The opposite NE is faulty.

(1) Rectify the fault on the opposite NE.

Step 2 Cause 2: The wiring sequence of the cable is incorrect.

(1) Redo the cable.

Step 3 Cause 3: The receive unit of the tributary board on the local NE is faulty.

(1) Replace the board where the line unit is located.

Step 4 Cause 4: The input E1 signal has an abnormal waveform.

(1) Check whether any external interference causes the abnormal waveform of the E1 signal.

If... Then...

There is the external interference The fault is rectified. End the alarm handling.

There is no external interference Contact Huawei engineers.

----End

Related Information

None.

A.3.31 E1_LOS

Description

The E1_LOS is an alarm indicating the loss of the E1 signal. This alarm occurs when the tributaryboard detects the uplink E1 signal of all 0s.

Attribute





A-57

Parameters

None.


When the E1_LOS alarm occurs, the E1 service is interrupted.

Possible Causesl Cause 1: The cable is not connected or the cable is faulty.

l Cause 2: The opposite NE is faulty.

l Cause 3: The tributary board on the local NE is faulty.

Procedure

Step 1 Cause 1: The cable is not connected or the cable is faulty.(1) Check whether the cable is connected properly.

If... Then...

The cable is not connected properly Connect the cable properly.

The cable is prepared incorrectly Redo the cable.

Step 2 Cause 2: The opposite NE is faulty.(1) Rectify the fault on the opposite NE.

Step 3 Cause 3: The tributary board on the local NE is faulty.(1) Replace the board where the tributary unit is located.

----End

Related Information

None.

A.3.32 ETH_CFM_LOC

Description

The ETH_CFM_LOC is an alarm indicating the loss of connectivity. This alarm occurs whenthe system fails to receive the CCM packet from the remote MEP in 3.5 connectivity check (CC)periods successively.

Attribute


Critical Communication alarm




Issue 05 (2010-07-30)

Parameters


Name Meaning

Parameter 1, Parameter 2, Parameter 3,Parameter 4 (Port)

Indicates the ID of the port that reports thealarm.

Parameter 5, Parameter 6 (VLAN ID) Indicates the VLAN ID of the MEP.

Parameter 7 (Direction) Indicates the direction of the local MEP.l 0x00: The port is direction insensitive.

l 0x01: The port is in the ingress direction.

l 0x02: The port is in the egress direction.

Parameter 8 (Level) Indicates the MD level of the local MEP.l 0x00: consumer MEP level (low)

l 0x01: consumer MEP level (medium)

l 0x02: consumer MEP level (high)

l 0x03: provider MEP level (low)

l 0x04: provider MEP level (high)

l 0x05: operator MEP level (low)

l 0x06: operator MEP level (medium)

l 0x07: operator MEP level (high)NOTE

Consumer indicates the user, provider indicates thesupplier, and operator indicates the carrier.

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

Impact on the Systeml When the ETH_CFM_LOC alarm occurs, the LB and LT detection functions of IEEE

802.1ag ETH-OAM are unavailable.

l The service between the relevant standard MEPs may be interrupted.

Possible Causesl Cause 1: The line between the local standard MEP and the remote standard MEP is

interrupted.

l Cause 2: The Ethernet service in the maintenance association (MA) to which the local MEPbelongs is faulty.

l Cause 3: Serious congestion occurs on the network.



A-59

ProcedureStep 1 Cause 1: The line between the local standard MEP and the remote standard MEP is interrupted.

(1) Check whether the physical links (such as network cables and fibers) between the standardMEPs are connected properly.

If... Then...

The physical links are connected improperly Connect the physical links properly.

The physical links are connected properly Go to Cause 2.

Step 2 Cause 2: The Ethernet service in the maintenance association (MA) to which the local MEPbelongs is faulty.(1) Check whether Ethernet service in the maintenance association (MA) to which the local

MEP belongs is configured correctly.

If... Then...

The service is configured incorrectly Modify the configuration of the service to ensureconsistency at two ends.

The service is configured correctly Go to Cause 3.

Step 3 Cause 3: Serious congestion occurs on the network.(1) Check the utilization of bandwidth. If the bandwidth is exhausted, increase the bandwidth

or eliminate the source that transmits a large amount of invalid data.

----End


A.3.33 ETH_CFM_MISMERGE

DescriptionThe ETH_CFM_MISMERGE is an alarm indicating an incorrect connection. This alarm occurswhen the system receives the CCM packet whose MA mismatches or whose priority is lower.

Attribute







Issue 05 (2010-07-30)

Name Meaning
















Parameter 9, Parameter 10 Indicates the ID of the local MEP.

Impact on the SystemWhen the ETH_CFM_MISMERGE alarm occurs, the service between the relevant standardMEPs may be interrupted, and the data flow may be routed incorrectly.

Possible Causesl Cause 1: The names of the maintenance domain and the maintenance alliance that the

standard MEPs correspond to are inconsistent.l Cause 2: The levels of the maintenance domains that the standard MEPs correspond to are

different.l Cause 3: The physical connection is incorrect.

Procedure

Step 1 Cause 1: The names of the maintenance domain and the maintenance alliance that the standardMEPs correspond to are inconsistent.(1) Check whether the names of the maintenance domain and the maintenance alliance that the

standard MEPs correspond to are consistent.



A-61

If... Then...

The names are inconsistent Set the other names of maintenance domain andmaintenance alliance to ensure consistency at both ends.

The names are consistent Go to Cause 2.

Step 2 Cause 2: The levels of the maintenance domains that the standard MEPs correspond to aredifferent.(1) Check whether the MD levels of the standard MEPs are the same.

If... Then...

The levels are different Set the MD levels again to ensure consistency at both ends.

The levels are the same Go to Cause 3.

Step 3 Cause 3: The physical connection is incorrect.(1) Check the physical connection of the Ethernet service route and rectify the fault of the

physical connection if any.

----End


A.3.34 ETH_CFM_RDI

DescriptionThe ETH_CFM_RDI is an alarm indicating the CCM packet with RDI received from the remoteMEP. This alarm occurs when the system receives the CCM packet with RDI from the remoteMEP.

Attribute




Name Meaning






Issue 05 (2010-07-30)

Name Meaning





Parameter 8 (Level) Indicates the MD level of the local MEP.l 0x00: consumer MEP level (low).

l 0x01: consumer MEP level (medium).

l 0x02: consumer MEP level (high).

l 0x03: provider MEP level (low).

l 0x04: provider MEP level (high).

l 0x05: operator MEP level (low).

l 0x06: operator MEP level (medium).

l 0x07: operator MEP level (high).NOTE


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

Impact on the Systeml When the ETH_CFM_RDI alarm occurs, the loopback (LB) and link trace (LT) detection

functions of IEEE 802.1ag ETH-OAM are unavailable.l The service between the relevant standard MEPs may be interrupted.

Possible Causesl Cause 1: The remote MEP fails to receive the correct CCM packet.

l Cause 2: The software is reset or the other software fault occurs at the remote MEP.

Procedure

Step 1 Cause 1: The remote MEP fails to receive the correct CCM packet.(1) Determine the port that reports the alarm according to the alarm parameter.(2) Check whether the remote MEP that is connected to the port reports the

ETH_CFM_MISMERGE, ETH_CFM_UNEXPERI, or ETH_CFM_LOC alarm.

If... Then...

Any of the preceding alarms occurs Clear the alarm at the remote end.

No such alarms occur Go to Cause 2.

Step 2 Cause 2: The software is reset or the other software fault occurs at the remote MEP.



A-63

(1) Check whether the equipment at the remote MEP is reset.

If... Then...

The equipment is reset Rectify the fault and then end the alarm handling.

The equipment is not reset Perform a warm reset on the board where the remoteMEP is located.

----End


A.3.35 ETH_CFM_UNEXPERI

DescriptionThe ETH_CFM_UNEXPERI is an alarm indicating the errored frame. This alarm occurs whenthe system receives invalid CCM packets.

Attribute




Name Meaning










Issue 05 (2010-07-30)

Name Meaning










Parameter 9, Parameter 10 Indicates the ID of the local MEP.

Impact on the Systeml When the ETH_CFM_UNEXPERI alarm occurs, the LB and LT detection functions of

IEEE 802.1ag ETH-OAM are unavailable.

l The service may become abnormal due to the loop.

Possible Causesl Cause 1: No remote MEP is configured.

l Cause 2: The configuration of the MEPs at both ends are inconsistent. For example, theconnectivity check (CC) periods are different, and the IDs of the MEPs are in conflict.

l Cause 3: The service is looped back and the looped packet is received.

l Cause 4: A software fault occurs at the MEP at the transmit end.

Procedure

Step 1 Cause 1: No remote MEP is configured.

(1) Check whether the remote MEP is configured. If not, configure the remote MEP first.

Step 2 Cause 2: The configuration of the MEPs at both ends are inconsistent. For example, theconnectivity check (CC) periods are different, and the IDs of the MEPs are in conflict.

(1) Check whether the CC periods set at the MEPs are the same.

If... Then...

The CC periods are different Change the CC periods to ensure consistency at bothends.

The CC periods are the same Go to the next step.

(2) Check whether the IDs of the MEPs in the maintenance domain are in conflict.



A-65

If... Then...

The IDs are in conflict Change the conflicting IDs.

The IDs are not in conflict Go to Cause 2.

Step 3 Cause 3: The service is looped back and the looped packet is received.(1) Check whether any loop exists at each IP port of the service trail. If yes, release the loop

and clear the alarm.

Step 4 Cause 4: A software fault occurs at the MEP at the transmit end.(1) Perform a warm reset on the Ethernet board where the remote MEP is located.

----End

Related Information

None.

A.3.36 ETH_EFM_DF

Description

The ETH_EFM_DF is an alarm indicating negotiation failure. This alarm occurs when the point-to-point OAM protocol negotiation fails at the Ethernet port.

Attribute



Parameters


Name Meaning

Parameter 1 Indicates the reason why the negotiation fails.

l 0x01: The local link is faulty.

l 0x02: The local end fails to receive any OAM packets in a specified period.

l 0x03: The OAM settings of the opposite end do not meet the requirements ofthe local end.

l 0x04: The OAM settings of the local end do not meet the requirements of theopposite end.




Issue 05 (2010-07-30)

Impact on the SystemWhen the ETH_EFM_Discover alarm occurs, the service at the port that reports the alarm maybe interrupted.

Possible Causesl Cause 1: The physical port of the local end is faulty.

l Cause 2: The point to point OAM protocol is not enabled at the opposite end.

l Cause 3: The OAM configuration at both ends is inconsistent.

Procedure

Step 1 Cause 1: The physical port of the local end is faulty.(1) Check whether the physical port is faulty. If yes, replace the board where the Ethernet

port is located.

Step 2 Cause 2: The point to point OAM protocol is not enabled at the opposite end.(1) Enable the point to point OAM protocol at the opposite end.

Step 3 Cause 3: The OAM configuration at both ends is inconsistent.(1) Reconfigure the point to point OAM protocol and ensure the consistency at both ends.

----End


A.3.37 ETH_EFM_EVENT

DescriptionThe ETH_EFM_EVENT is an alarm indicating the performance event reported on the oppositeNE. This alarm occurs when the local end receives the link error indication packet (OAMPDUM)from the opposite end.

Attribute






A-67

Name Meaning

Parameter 1 Indicates the type of the link event.

l 0x01: errored symbol period.

l 0x02: errored frame.

l 0x03: errored frame period.

l 0x04: errored frame seconds summary.

Impact on the SystemWhen the ETH_EFM_EVENT alarm occurs, the service at the port that reports the alarm maybe interrupted.

Possible Causesl Cause 1: The physical port at the local end is faulty.l Cause 2: The equipment at the opposite end is faulty.

ProcedureStep 1 Cause 1: The physical port at the local end is faulty.

(1) Check whether the physical port is faulty. If yes, replace the board where the Ethernetport is located.

Step 2 Cause 2: The equipment at the opposite end is faulty.(1) Rectify the fault of the equipment at the opposite end.

----End


A.3.38 ETH_EFM_LOOPBACK

DescriptionThe ETH_EFM_LOOPBACK is an alarm indicating the loopback. This alarm occurs when thelocal end initiates a loopback or responds to a loopback request from the opposite end.

Attribute







Issue 05 (2010-07-30)


Name Meaning

Parameter 1 Indicates the state of the loopback.

l 0x01: The local end initiates a loopback.

l 0x02: The local end responds to a loop request from the opposite end.


When the ETH_EFM_LOOPBACK alarm occurs, the service at the port that reports the alarmis looped back.

Possible Causesl Cause 1: The local end initiates a loopback.

l Cause 2: The opposite end initiates a loopback.

Procedure

Step 1 Cause 1: The local end initiates a loopback.

(1) According to the alarm parameter, it is determined that the local end initiates a loopback.Determine the causes of the loopback initiated at the local end and release the loopback assoon as possible.

Step 2 Cause 2: The opposite end initiates a loopback.

(1) According to the alarm parameter, it is determined that the opposite end initiates a loopback.Determine the causes of the loopback initiated at the opposite port and release the loopbackas soon as possible.

----End

Related Information

None.

A.3.39 ETH_EFM_REMFAULT

Description

The ETH_EFM_REMFAULT is an alarm indicating the fault on the opposite NE. This alarmoccurs when the local end receives the fault indication packet (OAMPDUM) from the oppositeend.



A-69

Attribute




Name Meaning

Parameter 1 Indicates the fault type at the opposite end.

l 0x01: link fault.

l 0x02: dying gasp.

l 0x03: critical event.

Impact on the SystemWhen the ETH_EFM_REMFAULT alarm occurs, the service at the port that reports the alarmmay be interrupted.

Possible Causesl Cause 1: The opposite NE is reset.


Procedure

Step 1 Cause 1: The opposite NE is reset.(1) Check whether the opposite NE is reset frequently.

If... Then...

The opposite NE is reset frequently Rectify the fault on the opposite NE.

The opposite NE is not reset frequently Reset the opposite NE, and the alarm iscleared.

Step 2 Cause 2: The opposite NE is faulty.(1) Rectify the fault on the opposite NE.

----End





Issue 05 (2010-07-30)

A.3.40 ETH_LOS

DescriptionThe ETH_LOS is an alarm indicating the loss of Ethernet port connection.

Attribute



ParametersNone.

Impact on the SystemWhen the ETH_LOS alarm occurs, the service at the port that reports the alarm is interrupted.

Possible Causesl Cause 1: The negotiation fails because the transmit port and receive port work in different

modes.l Cause 2: The cable or fiber is faulty.


Procedure

Step 1 Cause 1: The negotiation fails because the transmit port and receive port work in different modes.(1) Check whether the transmit port and receive port work in the same mode.

If... Then...

The transmit port and receive port workin different modes

Correctly set the working modes of thetransmit port and receive port.

The transmit port and receive port workin the same mode

Go to Cause 2.

Step 2 Cause 2: The cable or fiber is faulty.(1) Check the network cable or fiber jumper connected to the port that reports the alarm.

If... Then...

The network cable is loose or damaged Connect the network cable properly orreplace the damaged network cable.

The connector of the fiber jumper is dirty Clean the connector.

The connector is loosely connected ordamaged

Insert the connector properly or replace thedamaged fiber jumper.



A-71

If... Then...

The connection is normal Go to Cause 3.

Step 3 Cause 3: The opposite NE is faulty.

(1) Check whether any fault occurs on the equipment interconnected with the port that reportsthe alarm.

If... Then...

The equipment is faulty Rectify the fault.

The equipment is normal Replace the board that reports the alarm on the localNE.

----End

Related Information

None.

A.3.41 ETHOAM_SELF_LOOP

Description

The ETHOAM_SELF_LOOP is an alarm indicating the loopback of the MAC port that runs thepoint-to-point OAM protocol. This alarm occurs when the MAC port of a board receives theOAM protocol packet sent by the port itself or the board after the loop detection function isenabled.

Attribute


Major Environmental alarms

Parameters


Name Meaning

Parameter 1 Indicates the loopback type.

l 0x01: self-loop of the port.

l 0x02: self-loop of the board.




Issue 05 (2010-07-30)

Impact on the SystemWhen the ETHOAM_SELF_LOOP alarm occurs, a network storm may occur due to theloopback.

Possible Causesl Cause 1: The cable connected to the port is self-looped, or the port is accessed to a LAN

that has a loopback, or the PHY/MAC loopback is manually configured at the port.l Cause 2: Two ports of the board are connected through cables or two ports of the board are

accessed to the same LAN.

ProcedureStep 1 Determine the loopback type according to Parameter 4, and then handle the loopback

accordingly.

If... Then...

The value of Parameter 4 is 0x01 Go to Cause 1.

The value of Parameter 4 is 0x02 Go to Cause 2.

Step 2 Cause 1: The cable connected to the port is self-looped, or the port is accessed to a LAN thathas a loopback, or the PHY/MAC loopback is manually configured at the port.

If... Then...

The PHY/MAC loopback is manuallyconfigured at the port

Manually release the PHY/MAC loopback (orwait five minutes for the automatic release bythe NE). Then, the self-loop is released.

The cable connected to the port is self-looped

Connect the cable properly to release the self-loop.

The port is accessed to a LAN that has aloopback

Release the loopback on the LAN, or break theconnection between the port and the LAN, torelease the self-loop.

Step 3 Cause 2: Two ports of the board are connected through cables or two ports of the board areaccessed to the same LAN.(1) Check whether two ports of the board are connected through cables or whether two ports

of the board are accessed to the same LAN.

If... Then...

The two ports are connected throughcables

Disconnect the cables to release the self-loop.

The two ports are accessed to the samenetwork

Break the connection between a port and theLAN to release the self-loop.

----End




A-73

A.3.42 EXT_SYNC_LOS

DescriptionThe EXT_SYNC_LOS is an alarm of the loss of the external clock source.

Attribute



ParametersNone.

Impact on the Systeml When the EXT_SYNC_LOS alarm occurs, if only the external clock source and internal

clock source are configured in the clock source priority list, the NE traces the internal clocksource after the external clock source is lost and enters the free-run state 24 hours later.

l If another valid clock source of higher priority and good quality is configured in the clocksource priority list, however, the clock protection switching occurs.

Possible CausesCause 1: The external clock source is configured in the clock source priority list, but the externalclock source cannot be detected or become invalid.

ProcedureStep 1 Cause 1: The external clock source is configured in the clock source priority list, but the external

clock source cannot be detected or become invalid.(1) Check whether the equipment that provides the external clock source is faulty.

If... Then...


The equipment is normal Go to the next step.

(2) Check whether the cable that connects the external clock source is normal.

If... Then...

The cable is abnormal Replace the cable.

The cable is normal Replace the board that reports the alarm.

----End





Issue 05 (2010-07-30)

A.3.43 FAN_AGING

DescriptionThe FAN_AGING is an alarm of the aged fan. This alarm occurs when the fan runs at a speedlower than 80% of the rated value.

Attribute




Name Meaning

Parameter 1 Indicates the ID of the fan that reports the alarm.

Impact on the SystemWhen the FAN_AGING alarm occurs, it indicates that the NE has an over high temperature,which affects the long-time NE operation.

Possible CausesCause 1: The fan is aged.

Procedure

Step 1 Cause 1: The fan is aged.(1) Replace the fan.

----End


A.3.44 FAN_FAIL

DescriptionThe FAN_FAIL is an alarm indicating that the fan is faulty.



A-75

Attribute




Name Meaning

Parameter 1 Indicates the number of the fan.

The values 0x01 to 0x06 separately represent each fan.

Impact on the SystemWhen the FAN_FAIL alarm occurs, the heat dissipation of the system is affected.

Possible Causesl Cause 1: The board and the backplane are connected improperly.

l Cause 2: Fan failure occurs.

Procedure

Step 1 Cause 1: The board and the backplane are connected improperly.(1) Remove the fan board. Clean the dust on the fan and reinsert the fan board.

If... Then...




Go to Cause 2.

Step 2 Cause 2: Fan failure occurs.(1) Replace the fan board that reports the alarm.

----End


A.3.45 FLOW_OVER




Issue 05 (2010-07-30)

DescriptionThe FLOW_OVER is an alarm indicating that the data flow received by the Ethernet port exceedsthe threshold.

Attribute



ParametersNone.

Impact on the SystemWhen the FLOW_OVER alarm occurs, the extra data may be discarded by the port.

Possible Causesl Cause 1: The traffic threshold of the local port is very low.

l Cause 2: The opposite end transmits excessive data flow.

Procedure

Step 1 Cause 1: The traffic threshold of the local port is very low.(1) Increase the traffic threshold of the local port to a value that is lower than the rate of the

local port.

Step 2 Cause 2: The opposite end transmits excessive data flow.(1) Configure the QoS policies at the opposite end to reduce the data flow that the opposite

end transmits.

----End


A.3.46 HARD_BAD

DescriptionThe HARD_BAD is an alarm indicating hardware errors.

Attribute





A-77

Parameters


Name Meaning

Parameter 1 Indicates the cause of the fault.l 0x01: The power module is working abnormally.

l 0x02: The board is installed improperly.

l 0x03: 38 MHz system clock 1 is abnormal.

l 0x04: 38 MHz system clock 2 is abnormal.

l 0x05: The 2 MHz clock source is abnormal.

l 0x06: The digital phase-locked loop is abnormal.

l 0x07: The 38 MHz service clock is lost.

l 0x08: The bus is abnormal.

l 0x09: The TPS protection board is abnormal.

l 0x0A: The primary crystal oscillator stops oscillating.

l 0x0B: The frequency offset of the primary crystal oscillator is excessive.

l 0x0C: The secondary crystal oscillator stops oscillating.

l 0x0D: The processor (CPU/DSP/coprocessor) is faulty.

l 0x0E: The storage components are faulty.

l 0x0F: The programmable logic device is faulty.

l 0x10: The SDH components are faulty.

l 0x11: The data communication components are faulty.

l 0x12: The clock components are faulty.

l 0x13: The interface components are faulty.

l 0x14: The power components are faulty.

l 0x15: The other fault occurs.

l 0x16: The analog phase-locked loop is abnormal.

l 0x17: The 32 MHz clock is unavailable.



l 0x1A: The ring of cross-connect chip is damaged.


The board that reports the alarm fails to work. If the board is configured with the 1+1 protection,the protection switching may be triggered.




Issue 05 (2010-07-30)

Possible Causesl Cause 1: The board and the backplane are connected improperly.


l Cause 3: The slot is faulty.

Procedure

Step 1 Cause 1: The board and backplane are connected improperly.(1) Remove and insert the board that reports the alarm. For details, see 6.1 Removing a

Board and 6.2 Inserting a Board. Then, check whether the alarm is cleared.

If... Then...





Step 2 Cause 2: Board failure occurs.(1) Replace the board that reports the alarm, and then check whether the alarm is cleared. For

details, see 6 Part Replacement.

If... Then...




Ensure that the slot is normal.

Step 3 Cause 3: The slot is faulty.(1) Contact Huawei engineers to handle the faulty slot.

TIPGenerally, the slot becomes faulty due to the broken pin or bent pin. Remove the board, and use anelectric torch to observe whether there is any broken pin or bent pin.

(2) If an idle slot is available, insert the board in the idle slot and add the board again. Then,the board can work normally.

----End


A.3.47 HP_CROSSTR

DescriptionThe HP_CROSSTR is an alarm indicating that the higher order path error crosses the threshold.This alarm occurs when the board detects that the performance event that the higher order patherror crosses the preset threshold.



A-79

Attribute


Minor Service alarm

Parameters


Name Meaning

Parameter 1 Indicates the performance monitoring period:

l 0x01: 15 minutes

l 0x02: 24 hours

Parameter 2, Parameter 3 Indicate the ID of a performance event that causes the alarm.


When the HP_CROSSTR alarm occurs, a large number of errors occur in the service, and theservice may be interrupted.

Possible Causes

Cause 1: The higher order path error crosses the preset threshold.

Procedure

Step 1 Cause 1: The higher order path error crosses the preset threshold.

(1) Check the threshold crossing records to find out the performance event that the higher orderpath error crosses the preset threshold. For details, see 8.3.8 Browsing the PerformanceEvent Threshold-Crossing Records.

(2) Handle the threshold-crossing performance event.

----End

Related Information

None.

A.3.48 HP_LOM




Issue 05 (2010-07-30)

Description

The HP_LOM is an alarm indicating the loss of the higher order path multiframe. This alarmoccurs when the board detects that byte H4 is inconsistent with the expected multiframesequence.

Attribute



Parameters

None.


When the HP_LOM alarm occurs, the service on the path that reports the alarm is interrupted.If the services are configured with protection, the protection switching may be triggered.

Possible Causesl Cause 1: The transmit unit of the opposite NE is faulty.


Procedure

Step 1 Cause 1: The transmit unit of the opposite NE is faulty.

(1) Replace the board where the line unit is located on the opposite NE. Then, checkwhether the alarm is cleared.

If... Then...


The alarm persists Replace the system control, cross-connect, and timing boardon the opposite NE.

Step 2 Cause 2: The receive unit of the local NE is faulty.

(1) Replace the board that reports the alarm.

----End

Related Information

None.

A.3.49 HP_RDI



A-81

DescriptionThe HP_RDI is an alarm indicating the higher order path remote receive failure. This alarmoccurs when the board detects that bit 5 of byte G1 is 1.

Attribute



ParametersNone.

Impact on the SystemWhen the HP_RDI occurs, the service on the local NE is not affected. The service received bythe opposite NE, however, is interrupted.

Possible CausesCause 1: The local NE detects the message that is returned by the opposite NE and indicates thehigher order path remote receive failure.

Procedure

Step 1 Cause 1: The local NE detects the message that is returned by the opposite NE and indicates thehigher order path remote receive failure.(1) Clear the alarms such as HP_LOM and B3_EXC that the AU-4 path reports on the opposite

NE.

----End


A.3.50 HP_REI

DescriptionThe HP_REI is an alarm indicating the higher order path remote error. This alarm occurs whenthe board detects that bits 1-4 of G1 take a value from 1 to 8.

Attribute


Warning Communication alarm




Issue 05 (2010-07-30)

ParametersNone.

Impact on the SystemThe service on the local station is not affected. The service received by the opposite station,however, has errors.

Possible CausesCause 1: The local NE detects the message that is returned by the opposite NE and indicates thehigher order path remote errors.

Procedure

Step 1 Cause 1: The local NE detects the message that is returned by the opposite NE and indicates thehigher order path remote receive failure.(1) Handle the HP_BBE performance event that the AU-4 path reports on the opposite NE.

----End


A.3.51 HP_SLM

DescriptionThe HP_SLM is an alarm indicating the lower order path label mismatch. This alarm occurswhen the board detects the C2 byte mismatch.

Attribute



ParametersNone.

Impact on the SystemNone.

Possible Causesl Cause 1: The C2 byte received by the local NE does not match with the C2 byte transmitted

by the remote NE.



A-83

l Cause 2: Configuration data is incorrect.

ProcedureStep 1 Cause 1: The C2 byte received by the local NE does not match with the C2 byte transmitted by

the remote NE.(1) Configure the same service type at the source and sink of the AU-4 path. For details, see

Configuring Overhead Bytes.

Step 2 Cause 2: Configuration data is incorrect.(1) If the port that reports the alarm is the SDH port that is interconnected with the ATM/

Ethernet equipment, configure the service as VC-4 pass-through service. For details, seeCreating Cross-Connections of SNCP Services.

----End


A.3.52 HP_TIM

DescriptionThe HP_TIM is an alarm indicating the higher order path trace identifier mismatch. This alarmoccurs when the board detects the J1 byte mismatch.

Attribute



ParametersNone.

Impact on the SystemIf the service is configured with the protection that considers the HP_TIM alarm as a triggercondition, the protection switching is triggered.

Possible Causesl Cause 1: The receivable J1 byte on the local NE does not match with the J1 byte transmitted

on the opposite NE.l Cause 2: Configuration data is incorrect.

ProcedureStep 1 Cause 1: The receivable J1 byte on the local NE does not match with the J1 byte transmitted on

the opposite NE.




Issue 05 (2010-07-30)

(1) Disable the receivable J1 byte on the local NE or set the receivable J1 byte on the local NEto the same as the transmitted J1 byte on the opposite NE. For details, see ConfiguringVC-4 POHs.

Step 2 Cause 2: Configuration data is incorrect.

(1) If the port that reports the alarm is the SDH port that is interconnected with the ATM/Ethernet equipment, configure the service as VC-4 pass-through service. For details, seeCreating Cross-Connections of SNCP Services or Creating the Cross-Connections of Point-to-Point Services.

If... Then...

The alarm is cleared after the configurationis changed


The alarm persists after the configurationis changed


(2) Check whether the cross-connections are configured correctly at the intermediate nodeswhere the service travels. If not, reconfigure the cross-connections. For details, see CreatingCross-Connections of SNCP Services or Creating the Cross-Connections of Point-to-PointServices.

----End

Related Information

None.

A.3.53 HP_UNEQ

Description

The HP_UNEQ is an alarm indicating the unequipped higher order path. This alarm occurs whenthe board detects that the C2 byte is 0.

Attribute



Parameters




A-85

Name Meaning

Parameter 1 Indicates the ID of the line port that reports the alarm. For example,0x01 indicates that the alarm is reported by port 1 of the relatedboard.

Parameter 2, Parameter 3 Indicates the ID of the AU-4 path that reports the alarm. Forexample, 0x00 0x01 indicates that the alarm is reported by path 1of the SDH signal.

Impact on the SystemWhen the HP_UNEQ alarm occurs, the service in the AU-4 path that reports the alarm isunavailable. If the service is configured with the protection that considers the alarm as a triggercondition, the protection switching is triggered.

Possible Causesl Cause 1: The line port at the local NE is configured with services, but the corresponding

line port at the opposite NE is not configured with services.l Cause 2: Byte C2 is set to 0 at the opposite NE.

Procedure

Step 1 Cause 1: The line port at the local NE is configured with services, but the corresponding lineport at the opposite NE is not configured with services.(1) Configure line services on the opposite NE. For details, see Creating Cross-Connections

of SNCP Services or Creating the Cross-Connections of Point-to-Point Services.

Step 2 Cause 2: Byte C2 is set to 0 at the opposite NE.(1) Change the setting of byte C2. For details, see Configuring VC-4 POHs.

----End


A.3.54 HPAD_CROSSTR

DescriptionThe HPAD_CROSSTR is an alarm indicating that the higher order path adaptation performancecrosses the threshold. This alarm occurs when a board detects that the performance event of TUpointer justification crosses the preset threshold.

Attribute


Minor Service alarm




Issue 05 (2010-07-30)


Name Meaning


l 0x01: 15 minutes

l 0x02: 24 hours


Impact on the SystemWhen the HPAD_CROSSTR alarm occurs, bit errors may occur in the service.

Possible CausesCause 1: The performance event of TU pointer justification crosses the preset threshold.

Procedure

Step 1 Cause 1: The performance event of TU pointer justification crosses the preset threshold.(1) Check the threshold crossing records to find out the performance event of TU pointer

justification that crosses the preset threshold. For details, see 8.3.8 Browsing thePerformance Event Threshold-Crossing Records.

(2) Handle the threshold-crossing performance event.

----End


A.3.55 IF_CABLE_OPEN

DescriptionThe IF_CABLE_OPEN is an alarm indicating that the IF cable is open.

Attribute





A-87

Parameters

None.


When the IF_CABLE_OPEN alarm occurs, the service on the IF port that reports the alarm isinterrupted.

Possible Causes

l Cause 1: The IF cable is loose or faulty.

l Cause 2: The IF port on the IF board is damaged.

l Cause 3: The power module of the ODU is faulty.

Procedure

Step 1 Cause 1: The IF cable is loose or faulty.

(1) Check whether the connector of the IF cable is loose or whether the connector is madeproperly.

The connectors to be checked include the connector between the IF fiber jumper and theIF board, the connector between the IF fiber jumper and the IF cable, and the connectorbetween the IF cable and the ODU.

If... Then...

The connector is loose Connect the connector tightly.

The connector is made improperly Make a new IF cable connector.

None of the above Go to the next step.

(2) Check whether the surface of the IF fiber jumper and the IF cable is damaged, and test theconnectivity between the IF fiber jumper and the IF cable. For details, see Testing theconnectivity between cables.

If... Then...

The cable does not meet the requirement Replace the cable with a qualified one.

The cable meets the requirement Go to Cause 2 or Cause 3.

Step 2 Cause 2: The IF port on the IF board is damaged.

(1) Replace the IF board that reports the alarm.

Step 3 Cause 3: The power module of the ODU is faulty.

(1) Replace the ODU connected to the IF board that reports the alarm.

----End




Issue 05 (2010-07-30)

Related InformationNOTEWhen rectifying the faults of the IF cable, IF port, and ODU, you must turn off the ODU before theoperation. You can turn on the ODU only after the operation is complete.

A.3.56 IF_INPWR_ABN

DescriptionThe IF_INPWR_ABN is an alarm indicating that the power that the IF cable inputs into the ODUis abnormal.

Attribute




Name Meaning

Parameter 1 l 0x01: input power of the ODU is over high.

l 0x02: input power of the ODU is over low.

Impact on the SystemWhen the IF_INPWR_ABN alarm occurs, the service on the ODU is interrupted. If the 1+1protection is configured, the 1+1 HSB switching is triggered.

Possible Causesl Cause 1: The IF board is faulty.

l Cause 2: The IF cable is faulty.

l Cause 3: The ODU is faulty.

ProcedureStep 1 Cause 1: The IF board is faulty.

(1) Replace the IF board connected to the ODU that reports the alarm.

Step 2 Cause 2: The IF cable is faulty.(1) Check whether the connector of the IF cable is loose or whether the connector is made

properly.



A-89

The connectors to be checked include the connector between the IF fiber jumper and theIF board, the connector between the IF fiber jumper and the IF cable, and the connectorbetween the IF cable and the ODU.

If... Then...

The connector is loose Connect the connector tightly.

The connector is made improperly Terminate the IF cable with connectorsagain.

None of the above Go to the next step.

(2) Check whether the surface of the IF fiber jumper and the IF cable is damaged or deformed,

and test the connectivity between the IF fiber jumper and the IF cable. For details, seeTesting the Connectivity of the IF Cable.

If... Then...

The cable does not meet the requirement Replace the cable with a qualified one.

The cable meets the requirement The IF board or ODU may be faulty.

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

----End

Related InformationThe logical slot of the ODU is the slot ID of the IF board connected to the ODU plus 20.

A.3.57 IF_MODE_UNSUPPORTED

DescriptionThe IF_MODE_UNSUPPORTED is an alarm indicating that the configured IF working modeis not supported. This alarm occurs if the board is not loaded with the FPGA file that supportsthe configured IF working mode.

Attribute



ParametersWhen you view an alarm on the network management system, select the alarm. In the AlarmDetails field display the related parameters of the alarm. The alarm parameters are in thefollowing format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,




Issue 05 (2010-07-30)

Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the followingtable.

Name Meaning

Parameter 1 Indicates the ID of the FPGA file that is loaded to the board.

l 0x01 indicates that FPGA file 250 is loaded.

l 0x02 indicates that FPGA file 002 is loaded.


When the IF_MODE_UNSUPPORTED alarm occurs, the service on the IF port that reports thealarm is interrupted.

Possible Causes

Cause 1: The board is not loaded with the FPGA file that supports the configured IF workingmode, or the FPGA file that supports the configured IF working mode is damaged.

Procedure

l Cause 1: The board is not loaded with the FPGA file that supports the configured IF workingmode, or the FPGA file that supports the configured IF working mode is damaged.

1. Contact Huawei engineers to upgrade the software and the FPGA file.

----End

Related Information

None.

A.3.58 IN_PWR_HIGH

Description

The IN_PWR_HIGH is an alarm indicating that the input optical power is over high.

Attribute



Parameters

None.



A-91

Impact on the SystemWhen the IN_PWR_HIGH alarm occurs, the service at the optical interface that reports the alarmhas errors.

Possible Causesl Cause 1: The transmit power of the opposite NE is over high.

l Cause 2: The model of the selected optical module is incorrect.

l Cause 3: The optical module at the receive end is faulty.

Procedure

Step 1 Cause 1: The transmit power of the opposite site is over high.(1) Browse current performance events, and query the performance event of the transmit

optical power on the opposite NE.

If... Then...

The transmit optical power does not meetthe requirement

Contact Huawei engineers to replace theoptical module.

The transmit optical power meets therequirement

Add a proper attenuator to reduce thereceive optical power.

Step 2 Cause 2: The model of the selected optical module is incorrect.(1) Query the board manufacturing information report, and check whether the models of

the SFP optical modules used at both ends are correct.

If... Then...

The models are incorrect Contact Huawei engineers to replace the optical module.

The models are correct Go to Cause 3.

Step 3 Cause 3: The optical module at the receive end is faulty.(1) Use the optical power meter to test the receive optical power, and check whether the receive

optical power meets the requirement. If yes, contact Huawei engineers to replace the opticalmodule.

----End

Related InformationThe optical power threshold set for the IN_PWR_HIGH alarm is lower than the overload point.

SDH Optical Interface Performance.

A.3.59 IN_PWR_LOW

DescriptionThe IN_PWR_LOW is an alarm indicating that the input optical power is over low.




Issue 05 (2010-07-30)

Attribute



Parameters

None.


When the IN_PWR_LOW alarm occurs, the service at the optical interface that reports the alarmhas errors.

Possible Causesl Cause 1: The transmit power of the opposite NE is over low.

l Cause 2: The model of the selected optical module is incorrect.

l Cause 3: The optical module at the receive end is faulty.

l Cause 4: The fiber performance degrades.

Procedure

Step 1 Cause 1: The transmit power of the opposite NE is over low.

(1) Browse current performance events, and query the performance event of the transmitoptical power on the opposite NE.

If... Then...

The transmit optical power does not meetthe requirement


The transmit optical power meets therequirement

Go to Cause 2.

Step 2 Cause 2: The model of the selected optical module is incorrect.

(1) Query the board manufacturing information report, and check whether the models ofthe SFP optical modules used at both ends are correct.

If... Then...

The models are incorrect Contact Huawei engineers to replace the optical module.

The models are correct Go to Cause 3.

Step 3 Cause 3: The optical module at the receive end is faulty.

(1) Use the optical power meter to test the receive optical power, and check whether the receiveoptical power meets the requirement.



A-93

If... Then...

The receive optical power meets therequirement


The receive optical power does not meet therequirement

Go to Cause 4.

Step 4 Cause 4: The fiber performance degrades.(1) Clean fiber connectors and adapters.

If... Then...

The alarm is cleared after the connector iscleaned

The fault is rectified. End the alarm handling.

The alarm persists after the connector iscleaned

Replace the fiber.

----End

Related Information

The optical power threshold set for the IN_PWR_LOW alarm is higher than the sensitivity point.

SDH Optical Interface Performance.

A.3.60 J0_MM

Description

The J0_MM is an alarm indicating the trace identifier mismatch. This alarm occurs when theboard detects the J0 byte mismatch.

Attribute



Parameters

None.


None.

Possible Causes

Cause 1: The receivable J0 byte on the local NE does not match the transmitted J0 byte on theopposite NE.




Issue 05 (2010-07-30)

Procedure

Step 1 Cause 1: The receivable J0 byte on the local NE does not match the transmitted J0 byte on theopposite NE.

(1) Disable the receivable J0 byte on the local NE. For details, see Configuring RSOHs.

----End

Related Information

None.

A.3.61 K1_K2_M

Description

The K1_K2_M is an alarm indicating the K1/K2 byte mismatch. This alarm occurs when theboard detects inconsistent channel numbers that the transmitted K1 byte (bits 5-8) and thereceived K2 byte (bits 1-4) indicate.

Attribute



Parameters


Name Meaning

Parameter 1 Indicates the protection group type.l 0x01: linear MS protection.




When the K1_K2_M alarm occurs, the MSP protocol may fail and thus the protection switchingmay fail.



A-95

Possible Causesl Cause 1: The switching modes configured at both ends are single-ended switching and dual-

ended switching separately.

l Cause 2: The fiber connection is incorrect.


Procedure

Step 1 Cause 1: The switching modes configured at both ends are single-ended switching and dual-ended switching separately.

(1) Check whether the switching modes at both ends are the same.

If... Then...

The switching modes are different Configure the switching modes as the same.

The switching modes are the same Go to Cause 2.

Step 2 Cause 2: The fiber connection is incorrect.

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

If... Then...

The fiber connection is incorrect Connect the fiber properly.

The connection is correct Go to Cause 3.


(1) Replace the board where the line unit is located on the opposite NE. Then, checkwhether the alarm is cleared.

If... Then...



----End

Related Information

None.

A.3.62 K2_M

Description

The K2_M is an alarm indicating the K2 byte mismatch. This alarm occurs when the boarddetects that the protection mode indicated by the received K2 (bit 5) is different from theprotection mode of the NE.




Issue 05 (2010-07-30)

Attribute




Name Meaning

Parameter 1 Indicates the protection group type.l 0x01: linear MS protection.



Impact on the SystemWhen the K2_M alarm occurs, the MSP protocol may fail and thus the protection switching mayfail.

Possible Causesl Cause 1: Two NEs of the linear MSP group are configured with different protection modes

(1+1 or 1:N).l Cause 2: The MSP protocol is stopped when the protection switching occurs.

l Cause 3: The fiber connection is incorrect.


Procedure

Step 1 Cause 1: Two NEs of the linear MSP group are configured with different protection modes (1+1 or 1:N).(1) Query the status of the linear MSP, and check whether two NEs of the linear MSP group

are configured with different protection modes (1+1 or 1:1).

If... Then...

The protection modes are different Configure the protection modes as the same.

The protection modes are the same Go to Cause 2.

Step 2 Cause 2: The MSP protocol is stopped when the protection switching occurs.(1) Query the status of the linear MSP, and check whether the MSP protocol is stopped on the

opposite NE.



A-97

If... Then...

The protocol is stopped Restart the MSP protocol on the opposite NE. For details, seeStarting/Stopping the Linear MSP Protocol.

The protocol is running Go to Cause 3.

Step 3 Cause 3: The fiber connection is incorrect.(1) Check whether the fiber connection is correct. For example, the fiber at the receive or

transmit port may be incorrectly connected, or disconnected.

If... Then...

The connection is incorrect Connect the fiber properly

The connection is correct Go to Cause 4.

Step 4 Cause 4: Board failure occurs.(1) Replace the board where the line unit is located on the opposite NE. Then, check

whether the alarm is cleared.

If... Then...



----End

Related Information

None.

A.3.63 LAG_BWMM

Description

LAG_BWMM is an alarm indicating the bandwidth inconsistency in the LAG group.

Attribute



Parameters

None.


The configuration of the LAG is invalid.




Issue 05 (2010-07-30)

Possible Causes

Cause 1: In the LAG group, the license capacities of the ports differ from each other.

Procedure

Step 1 Cause 1: In the LAG group, the license capacities of the ports differ from each other.

(1) Query the license capacities of the ports of the LAG group by using the NMS.

(2) If the license capacities of the ports differ from each other, reload a license file of anappropriate capacity.

----End

Related Information

None.

A.3.64 LAG_DOWN

Description

The LAG_DOWN alarm is an alarm indicating that the link aggregation group (LAG) isunavailable. This alarm occurs when the LAG does not have activated members.

Attribute



Parameters

None.


When the LAG_DOWN alarm occurs, the service at the member port of the LAG is interrupted.

Possible Causes

Cause 1: All the member ports of the aggregation group are invalid for the same causes as theLAG_MEMBER_DOWN alarm.

Procedure

Step 1 Cause 1: All the member ports of the LAG are invalid for the same causes as theLAG_MEMBER_DOWN alarm.

(1) Determine the port that reports the alarm according to the alarm parameter.



A-99

(2) Rectify the fault at each member port according to the description ofLAG_MEMBER_DOWN.

----End

Related Information

None.

A.3.65 LAG_MEMBER_DOWN

Description

The LAG_MEMBER_DOWN alarm is an alarm indicating that a member port of a linkaggregation group (LAG) is unavailable. This alarm occurs when a member port of an LAG canneither be activated nor function as a protection port.

Attribute



Parameters


Name Meaning

Parameter 1, Parameter 2 Indicates the ID of the board that reports the alarm.

Parameter 3 Indicates the ID of the subboard that reports the alarm. The valueis always 0xff.

Parameter 4, Parameter 5 Indicates the ID of the port that reports the alarm.

Parameter 6 Indicates the cause that makes the port unavailable.l 0x01: The port link is faulty or disabled.

l 0x02: The port fails to receive the LACP packets.

l 0x03: The port works in half-duplex mode.

l 0x04: The port is self-looped.


When the LAG_MEMBER_DOWN alarm occurs, the faulty member port of the LAG cannotshare the service load, and the service is not transmitted or received through this port.




Issue 05 (2010-07-30)

Possible Causesl Cause 1: The port link is faulty or disabled.

l Cause 2: The port receives no LACP packets.

l Cause 3: The port works in half-duplex mode.

l Cause 4: The port is self-looped.

Procedure

Step 1 Determine the port that reports the alarm and the cause of the alarm according to the alarmparameters.

If... Then...

The value of Parameter 4 is 0x01 Perform the operations described in step Step 2.




Step 2 Cause 1: The port link is faulty or disabled.(1) On the NMS, check whether the port in the LAG is enabled. For details, see Querying the

Protocol Information of the LAG.

If... Then...

The port is not enabled Enable the port in the LAG.

The port is enabled Go to the next step.

(2) Check the link status of all ports and check whether the ETH_LOS alarm is reported.

If... Then...

The alarm is reported Clear the ETH_LOS alarm immediately and rectify thefault of the port link.

The alarm is not reported Go to Cause 2.

Step 3 Cause 2: The port receives no LACP packets.(1) Check whether the local port and the remote port transmit the LACP packets. For details,

see Querying the Protocol Information of the LAG. If the LACP packets are not transmitted,configure the ports at two ends to ensure that the packets can be normally transmitted.

Step 4 Cause 3: The port works in half-duplex mode.(1) On the NMS, check whether the port in the LAG is enabled. For details, see Querying the

Protocol Information of the LAG. If the port is in half-duplex mode, change the workingmode of the port into full-duplex.

Step 5 Cause 4: The port is self-looped.(1) Check whether the port is self-looped. For details, see 8.15 Querying the Attributes of

an Ethernet Port. If the port is self-looped, release the self-loop. For details, see 8.5.3Setting a Loopback for the Ethernet Interface Board.

----End



A-101

Related Information

None.

A.3.66 LASER_CLOSED

Description

The LASER_CLOSED is an alarm indicating that the laser is shut down. This alarm occurs whenthe laser is shut down by using the NMS.

Attribute



Parameters

None.


When the LASER_CLOSED alarm occurs, the optical interface fails to carry services.

Possible Causes

Cause 1: The laser on the local NE is shut down by using the NMS.

Procedure

Step 1 Cause 1: The laser on the local NE is shut down by using the NMS.

(1) Find out the cause of shutting down the laser and start up the laser as soon as possible.

----End

Related Information

None.

A.3.67 LASER_MOD_ERR

Description

The LASER_MOD_ERR is an alarm indicating that the type of the pluggable optical moduleon the board does not match the type of the optical interface.




Issue 05 (2010-07-30)

Attribute



ParametersNone.

Impact on the SystemWhen the LASER_MOD_ERR alarm occurs, the performance of the optical interface degradesand serious degradation even causes service interruption.

Possible Causesl Cause 1: The optical module installed at the optical interface does not match the rate of the

optical interface.l Cause 2: The optical module is faulty.


l Cause 4: The small form-factor pluggable (SFP) module does not match the interface type.

Procedure

Step 1 Cause 1: The optical module installed at the optical interface does not match the rate of theoptical interface.(1) Check whether the optical module installed at the optical interface matches the rate of the

optical interface. For details, see 8.4.2 Querying the Board Manufacturing InformationReport .

If... Then...

The optical module does not match therate of the optical interface

Contact Huawei engineers to replace theoptical module with one that matches therate of the optical interface.

The optical module matches the rate ofthe optical interface

Go to Cause 2.

Step 2 Cause 2: The optical module is faulty.(1) Replace the faulty optical module.

If... Then...

The alarm is cleared after the optical module is replaced End the alarm handling.

The alarm persists after the optical module is replaced Go to Cause 3.

Step 3 Cause 3: Board failure occurs.(1) Replace the board that reports the alarm.

Step 4 Cause 4: The SFP module does not match the interface type.



A-103

(1) Replace the existing SFP module with a proper SFP module.

----End

Related Information

None.

A.3.68 LASER_MOD_ERR_EX

Description

The LASER_MOD_ERR is an alarm indicating that the type of the pluggable optical moduleon the board does not match the type of the optical interface.

Attribute



Parameters

None.


When the LASER_MOD_ERR_EX alarm occurs, the performance of the optical interfacedegrades and serious degradation even causes service interruption.

Possible Causesl Cause 1: The optical module installed at the optical interface does not match the rate of the

optical interface.

l Cause 2: The optical module is faulty.


l Cause 4: The small form-factor pluggable (SFP) module does not match the interface type.

Procedure

Step 1 Cause 1: The optical module installed at the optical interface does not match the rate of theoptical interface.

(1) Check whether the optical module installed at the optical interface matches the rate of theoptical interface. For details, see 8.4.2 Querying the Board Manufacturing InformationReport .




Issue 05 (2010-07-30)

If... Then...

The optical module does not match therate of the optical interface

Contact Huawei engineers to replace theoptical module with one that matches therate of the optical interface.

The optical module matches the rate ofthe optical interface

Go to Cause 2.

Step 2 Cause 2: The optical module is faulty.

(1) Replace the faulty optical module.

If... Then...

The alarm is cleared after the optical module is replaced End the alarm handling.

The alarm persists after the optical module is replaced Go to Cause 3.



Step 4 Cause 4: The SFP module does not match the interface type.

(1) Replace the existing SFP module with a proper SFP module.

----End

Related Information

None.

A.3.69 LCS_LIMITED

Description

The LCS_LIMITED is an alarm indicating that the configuration capacity of an NE exceeds thecapacity authorized by the license file.

Attribute



Parameters




A-105

Name Meaning

Parameter 1 Indicates the alarm cause.

l 0x01: The service capacity exceeds the capacity authorized by the license file.

l 0x02: The AM license file is not loaded.

l 0x03: In the case of IF protection, the bandwidth at the standby port authorizedby the license file is lower than the bandwidth at the main port authorized bythe license file.


When the LCS_LIMITED alarm occurs, the change of radio service capacity cannot take effecton the NE.

Possible Causesl Cause 1: The services configured on the NE exceed the capacity authorized by the license

file.l Cause 2: The AM configuration on the NE exceeds the limit authorized by the license file.

l Cause 3: In the case of IF protection, the bandwidth at the standby port authorized by thelicense file is lower than the bandwidth at the main port authorized by the license file.

Procedure

Step 1 Query the capacity of the license by using the NMS.

Step 2 Cause 1: The services configured on the NE exceed the capacity authorized by the license file.(1) Check whether the radio service configuration exceeds the capacity of the license. If yes,

delete the excessive cross-connections of radio services.

Step 3 Cause 2: The AM configuration on the NE exceeds the limit authorized by the license file.(1) Check the AM enabling status. If the license does not allow the AM to be enabled, set the

AM function to disabled.

Step 4 Cause 3: In the case of IF protection, the bandwidth at the standby port authorized by the licensefile is lower than the bandwidth at the main port authorized by the license file.(1) Check whether the capacities that are authorized by the license files for the main and

standby IF boards in an IF protection group are consistent with the capacities specified inthe contract. If not, contact Huawei technical support engineers to reload correct licensefiles.

----End

Related Information

None.

A.3.70 LCS_MISMATCH




Issue 05 (2010-07-30)

Description

The LCS_MISMATCH is an alarm indicating that boards in a protection group are loaded withinconsistent license files.

Attribute



Parameters


Name Meaning


0x03: N+1 IF protection



None.

Possible Causes

Cause 1: The boards in a protection group are loaded with inconsistent license files.

Procedure

Step 1 Query the capacity of the license on the NMS to obtain the capacities that are authorized bythe license files for all the IF boards in the protection group.

Step 2 Check whether the capacities that are authorized by the license files for all the IF boards in theprotection group are consistent with the capacities specified in the contract. If not, contactHuawei technical support engineers to reload correct license files.

----End

Related Information

The license files of all the IF boards in the N+1 protection group must be consistent.



A-107

A.3.71 LICENSE_LOST

Description

The LICENSE_LOST is an alarm indicating that the NE fails to detect the license file.

Attribute



Parameters


Name Meaning

Parameter 1 Indicates the type of the license file.

l 0x01: AM license

l 0x02: Hybrid license

l 0x03: TDM license


When the LICENSE_LOST alarm occurs, the functions authorized by the license file cannottake effect.

Possible Causes

Cause 1: The license file is lost or is not loaded.

Procedure

Step 1 Cause 1: The license file is lost or is not loaded.(1) Contact Huawei engineers to reload the license file to the NE.

----End

Related Information

The NE calculates the radio service capacity according to the service cross-connections on theIF board.




Issue 05 (2010-07-30)

A.3.72 LOOP_ALM

DescriptionThe LOOP_ALM is an alarm indicating that a loop occurs.

Attribute






A-109

Name Meaning

Parameter 1 Indicates the type of loopback.

l 0x00: optical/electrical port inloop.

l 0x01: optical/electrical port outloop.

l 0x02: path inloop.

l 0x03: path outloop.

l 0x04: loopback on the user side.

l 0x05: loopback on the multiplexing side.

l 0x06: SPI inloop.

l 0x07: SPI outloop.

l 0x08: ATM layer inloop.

l 0x09: ATM layer outloop.

l 0x0A: PHY layer inloop.

l 0x0B: PHY layer outloop.

l 0x0C: MAC layer inloop.

l 0x0D: MAC layer outloop.

l 0x0E: VC-4 timeslot inloop.

l 0x0F: VC-4 timeslot outloop.

l 0x10: VC-3 timeslot inloop.

l 0x11: VC-3 timeslot outloop.

l 0x12: VC-12 timeslot inloop.

l 0x13: VC-12 timeslot outloop.

l 0x14: IF outloop.

l 0x15: IF inloop.

l 0x16: RF inloop.

l 0xFF: any of the preceding loopback modes.

Impact on the SystemWhen the LOOP_ALM alarm occurs, the looped port or path cannot carry services.

Possible CausesCause 1: A loop is performed on the local NE.

ProcedureStep 1 Cause 1: A loop is performed on the local NE.

(1) Determine the type of loopback according to the alarm parameter.(2) Find out the cause of the loopback, and set the loopback status of the port that reports the

alarm to Non-Loopback.




Issue 05 (2010-07-30)

For details, see 8.5 Software Loopback.

----End

Related Information

None.

A.3.73 LP_CROSSTR

Description

The LP_CROSSTR is an alarm indicating that the lower order path error crosses the threshold.This alarm occurs when the board detects the performance event that the lower order path errorcrosses the preset threshold.

Attribute


Minor Service alarm

Parameters


Name Meaning


l 0x01: 15 minutes

l 0x02: 24 hours



When the LP_CROSSTR alarm occurs, a large number of errors occur in the service, and theservice may even be interrupted.

Possible Causes

Cause 1: The lower order path error crosses the preset threshold.



A-111

Procedure

Step 1 Cause 1: The lower order path error crosses the preset threshold.(1) Check the threshold crossing records to find out the performance event that the lower order

path error crosses the preset threshold.(2) Handle the threshold-crossing performance event.

----End


A.3.74 LP_R_FIFO

DescriptionThe LP_R_FIFO is an alarm indicating that the FIFO overflows on the transmit side of the lowerorder path.

Attribute



ParametersNone.

Impact on the SystemWhen the LP_R_FIFO alarm occurs, the service has errors.

Possible Causesl Cause 1: The clock of the local NE is not synchronized with the clock of the opposite NE.


Procedure

Step 1 Cause 1: The clock of the local NE is not synchronized with the clock of the opposite NE.(1) Browse current performance events, and check whether the performance event of TU

pointer justification occurs on the local NE and the opposite NE.

If... Then...

The TU pointer justification occurs Handle the performance event. For details,see C.3.21 TUPJCHIGH, TUPJCLOW,and TUPJCNEW.




Issue 05 (2010-07-30)

If... Then...

The TU pointer justification does notoccur

Go to Cause 2.

Step 2 Cause 2: Board failure occurs.(1) Replace the board that reports the alarm.

----End


A.3.75 LP_RDI

DescriptionThe LP_RDI is an alarm indicating the lower order path remote receive failure. This alarm occurswhen the board detects that bit 8 of byte V5 is 1.

Attribute



ParametersNone.

Impact on the SystemWhen the LP_RDI occurs, the service on the local NE is not affected. The service received bythe opposite NE, however, is interrupted.

Possible CausesCause 1: The local NE detects the message that is returned by the opposite NE and indicates thelower order path remote receive failure.

Procedure

Step 1 Cause 1: The local NE detects the message that is returned by the opposite NE and indicates thelower order path remote receive failure.(1) Handle the lower order path alarm on the opposite NE.

----End




A-113

A.3.76 LP_REI

Description

The LP_REI is an alarm indicating the lower order path remote error. This alarm occurs whenthe board detects that bits 3 of V5 is 1.

Attribute


Minor Service alarm

Parameters

None.


When the LP_REI alarm occurs, the service on the local NE is not affected. The service receivedby the opposite NE, however, has errors.

Possible Causes

Cause 1: The local NE detects the message that is returned by the opposite NE and indicates thelower order path remote errors.

Procedure

Step 1 Cause 1: The local NE detects the message that is returned by the opposite NE and indicates thelower order path remote errors.

(1) Handle the LP_BBE performance event on the opposite NE.

----End

Related Information

None.

A.3.77 LP_RFI

Description

The LP_RFI is an alarm indicating the lower order path remote failure. This alarm occurs whenthe board detects that bits 4 of V5 is 1.




Issue 05 (2010-07-30)

Attribute



ParametersNone.

Impact on the SystemWhen the LP_RFI alarm occurs, the service on the local NE is not affected. The alarm onlyindicates that the lower order paths on the opposite NE cannot carry services.

Possible CausesCause 1: The local NE detects the message that is returned by the opposite NE and indicates thelower order path remote failure.

Procedure

Step 1 Cause 1: The local NE detects the message that is returned by the opposite NE and indicates thelower order path remote failure.(1) Handle the lower order path alarm on the opposite NE.

----End


A.3.78 LP_SIZE_ERR

DescriptionThe LP_SIZE_ERR is an alarm indicating that the size of the TU pointer is incorrect.

Attribute


Minor Service alarm

ParametersNone.

Impact on the SystemThe services on the board are interrupted.



A-115

Possible Causesl Cause 1: The configuration of the mapping structure at the local end or remote end is

incorrect.

l Cause 2: The tributary board is faulty.

Procedure

Step 1 Cause 1: The configuration of the mapping structure at the local end or remote end is incorrect.

(1) Check whether the types of the add/drop services configured on the board at the local endor remote end are the same as the service types supported by the board. For details, seeQuerying TDM Services.

If... Then...

The service types are different Change the configuration data.

The service types are the same Go to Cause 2.

Step 2 Cause 2: The tributary unit is faulty.

(1) Replace the board where the faulty tributary unit is.

----End

Related Information

None.

A.3.79 LP_SLM

Description

The LP_SLM is an alarm indicating that a mismatched signal label is detected in the lower orderpath. This alarm is reported when the board detects a signal label mismatch between the V5bytes.

Attribute



Parameters

None.


The services in the lower order path are unavailable.




Issue 05 (2010-07-30)

Possible CausesCause 1: The signal label contained in the V5 byte that is received by the local station does notmatch with the signal label contained in the V5 byte that is transmitted by the remote station.

Procedure

Step 1 Cause 1: The signal label contained in the V5 byte that is received by the local station does notmatch with the signal label contained in the V5 byte that is transmitted by the remote station.(1) Modify the signal label contained in the V5 byte that is to be received by the local station

or is to be transmitted by the remote station. Ensure that the signal labels at both ends matchwith each other. For details, see Configuring VC-12 POHs.

----End


A.3.80 LP_T_FIFO

DescriptionThe LP_T_FIFO is an alarm indicating that the FIFO overflows on the transmission side of thelower order path.

Attribute



ParametersNone.

Impact on the SystemBit errors occur in the services.

Possible Causesl Cause 1: The frequency offset of the input signal is very large.

l Cause 2: The board is faulty.

Procedure

Step 1 Cause 1: The frequency offset of the input signal is very large.(1) Use an SDH analyzer to check whether the frequency offset of the input signal is within

50 ppm.



A-117

If... Then...

The frequency offset is very large Troubleshoot the remote site.

The frequency offset is within 50 ppm Go to Cause 2.

Step 2 Cause 2: The board is faulty.(1) Replace the board that reports the alarm..

----End


A.3.81 LP_TIM

DescriptionThe LP_TIM is an alarm indicating a mismatched trace identifier is detected in the lower orderpath. This alarm is reported when the board detects a mismatch between the J2 bytes at bothends.

Attribute



ParametersNone.

Impact on the SystemNone.

Possible Causesl Cause 1: The J2 byte to be received by the local station does not match with the J2 byte to

be transmitted by the remote station.l Cause 2: The data configuration at the intermediate nodes is incorrect.

Procedure

Step 1 Cause 1: The J2 byte to be received by the local station does not match with the J2 byte to betransmitted by the remote station.(1) Set the byte mode of the J2 byte to be received by the local station to the disable mode.

Alternatively, set the J2 byte to be received by the local station to match with the J2 byteto be transmitted by the remote station. For details, see Configuring VC-12 POHs.

Step 2 Cause 2: The data configuration at the intermediate nodes is incorrect.




Issue 05 (2010-07-30)

(1) Check whether the cross-connections of the intermediate nodes where the service travelsare configured correctly. If not, reconfigure the cross-connections. For details, see QueryingTDM Services.

----End


A.3.82 LP_UNEQ

DescriptionThe LP_UNEQ is an alarm indicating that the lower order path is unequipped. This alarm isreported when the board detects that the V5 byte signal label is 0.

Attribute



ParametersNone.

Impact on the SystemThe services in the path are unavailable. If the services are configured with protection, protectionswitching may be triggered.

Possible CausesThe data configuration is incorrect.

l Cause 1: The tributary path at the local station is configured with services, but the tributarypath at the remote station is not configured with services.

l Cause 2: The cross-connection configuration at the intermediate nodes is incorrect.

Procedure

Step 1 Cause 1: The tributary path at the local station is configured with services, but the tributary pathat the remote station is not configured with services.(1) Check whether the tributary path at the remote station is configured with services. For

details, see Querying TDM Services.

If... Then...

The tributary path at the remote stationis not configured with services

Configure services for the tributary path atthe remote station.



A-119

If... Then...

The tributary path at the remote stationis configured with services

Go to Cause 2.

Step 2 Cause 2: The cross-connection configuration at the intermediate nodes is incorrect.(1) Check whether the cross-connection configuration at the intermediate nodes is correct. If

not, reconfigure the cross-connections. For details, see Querying TDM Services.

----End


A.3.83 LPS_UNI_BI_M

DescriptionThe LPS_UNI_BI_M is an alarm indicating that switching modes (single-ended or dual-ended)at both ends of the linear MSP do not match with each other.

Attribute




Name Meaning


0x01: linear MS protection.


Impact on the SystemThe system performs protection switching in single-ended mode.

Possible CausesCause 1: The linear MSP is configured incorrectly.




Issue 05 (2010-07-30)

The LPS_UNI_BI_M alarm is generated only when the following conditions are met:

l The switching modes (single-ended or dual-ended) at the local and remote stations aredifferent.

l The last three bits of the K2 byte are set to the indicated mode.

l The type of the protocol is set to a restructure protocol.

Procedure

Step 1 Cause 1: The linear MSP is configured incorrectly.(1) Change the MSP switching modes at both ends, and ensure that they are the same. For

details, see Querying the Status of the Linear MSP.

----End


A.3.84 LSR_NO_FITED

DescriptionThe LSR_NO_FITED is an alarm indicating that the SFP optical module is not installed.

Attribute



ParametersNone.

Impact on the SystemThe optical interface fails to carry services.

Possible CausesCause 1: The laser of the local station is not installed.

Procedure

Step 1 Cause 1: The SFP optical module of the local station is not installed.(1) Find out why the SFP optical module is not installed, and contact Huawei technical support

engineers for the installation.

----End



A-121


A.3.85 LTI

DescriptionThe LTI is an alarm indicating that the synchronization sources are lost. This alarm is reportedwhen all the synchronization sources for the NE are lost.

Attribute




Name Meaning


Impact on the SystemThe clock enters the free-run mode and loses synchronization with other NE clocks.

Possible Causesl Cause 1: The clock configuration is incorrect.

l Cause 2: All the clock sources in the clock source priority table fail.

Procedure

Step 1 Cause 1: The clock configuration is incorrect.(1) Check whether the data in the clock source priority table meets the network planning

requirement. For details, see Querying the Clock Synchronization Status.

If... Then...

The configuration is incorrect Correct the configurations.

The configuration is correct Go to Cause 2.

Step 2 Cause 2: All the clock sources in the clock source priority table fail.




Issue 05 (2010-07-30)

(1) Troubleshoot the synchronization sources based on the clock source priority table.

If... Then...

The synchronization source is theexternal clock

Handle the EXT_SYNC_LOS alarm.

The synchronization source is the lineclock

Handle the alarm that occurs on the lineboard.

The synchronization source is the IFclock

Handle the alarm that occurs on the IF board.

The synchronization source is thetributary clock

Handle the alarm that occurs on the tributaryboard.

The synchronization source is theEthernet clock

Handle the alarm that occurs on the Ethernetboard.

----End

Related Information

None.

A.3.86 MS_AIS

Description

The MS_AIS is an alarm indicating multiplex section alarms. This alarm is reported when theboard detects that bits 6-8 of the K2 byte in the three consecutive frames are 111.

Attribute



Parameters

None.


The services on the line port are interrupted. If the services are configured with protection,protection switching may be triggered.

Possible Causesl Cause 1: The transmit unit at the opposite station is faulty.

l Cause 2: The receive unit at the local station is faulty.



A-123

Procedurel Cause 1: The transmit unit at the opposite station is faulty.

1. Replace the line board at the opposite site based on the type of the board that reportsthe alarm.

If... Then...

The line board reports the alarm Replace the line board at the opposite end.

The IF board reports the alarm Replace the IF board at the opposite end.

2. Replace the board and then check whether the alarm is cleared.

If... Then...

The alarm is cleared after the board replacement End the fault handling.

The alarm persists after the board replacement Go to the next step.

3. Replace the system control, cross-connect, and timing board at the oppositeend.

If... Then...

The alarm is cleared after the board replacement End the fault handling.

The alarm persists after the board replacement Go to Cause 2.

l Cause 2: The receive unit at the local station is faulty.1. Replace the board that reports the alarm.

----End


A.3.87 MS_CROSSTR

DescriptionThe MS_CROSSTR is an alarm indicating that a performance indicator of the multiplex sectioncrosses the threshold. This alarm is reported when the board detects that the MS BERperformance indicator crosses the preset threshold.

Attribute


Minor Service alarm





Issue 05 (2010-07-30)


Name Meaning


l 0x01: 15 minutes

l 0x02: 24 hours


Impact on the SystemA large number of bit errors occur in the services, and the services may be interrupted.

Possible CausesCause 1: The MS BER performance indicator crosses the preset threshold.

ProcedureStep 1 Cause 1: The MS BER performance indicator crosses the preset threshold.

(1) Check the threshold crossing records of MS BER performance events to find out theperformance event that crosses the preset threshold. For details, see 8.3.8 Browsing thePerformance Event Threshold-Crossing Records.

(2) Handle the performance event that crosses the threshold.

----End


A.3.88 MS_RDI

DescriptionThe MS_RDI is an alarm indicating that data reception at the remote end of the multiplex sectionfails. This alarm is reported when the board detects that bits 6-8 of the K2 byte are 110.

Attribute



ParametersNone.



A-125

Impact on the SystemThe services on the local station are not affected. The services received by the opposite station,however, are interrupted.

Possible CausesCause 1: The local station receives a message from the opposite station, and the messageindicates that data reception at the remote end of the multiplex section fails.

Procedure

Step 1 Cause 1: The local station receives a message from the opposite station, and the messageindicates that data reception at the remote end of the multiplex section fails.(1) Rectify the fault that occurs on the opposite station.

The possible alarms are as follows:

l MS_AISl R_LOSl R_LOFl B2_EXCl B2_SD

----End


A.3.89 MS_REI

DescriptionThe MS_REI is an alarm indicating that bit errors occur on the remote end of the multiplexsection. This alarm is reported when the board detects that the M1 byte is non-zero.

Attribute


Warning Service alarm

ParametersNone.

Impact on the SystemThe services on the local station is not affected. The services received by the opposite station,however, has bit errors.




Issue 05 (2010-07-30)

Possible CausesCause 1: The local station receives a message from the opposite station, and the messageindicates that bit errors occur on the remote end of the multiplex section.

ProcedureStep 1 Cause 1: The local station receives a message from the opposite station, and the message

indicates that bit errors occur on the remote end of the multiplex section.(1) Handle the MS_BBE performance event on the port of the opposite station.

----End


A.3.90 MSAD_CROSSTR

DescriptionThe MSAD_CROSSTR is an alarm indicating that the adaptation performance indicator of themultiplex section crosses the threshold. This alarm is reported when the board detects that anAU pointer adaptation performance indicator crosses the preset threshold.

Attribute


Minor Service alarm


Name Meaning


l 0x01: 15 minutes

l 0x02: 24 hours


Impact on the SystemBit errors may occur in the services.



A-127

Possible Causes

Cause 1: An AU pointer adaptation performance indicator crosses the preset threshold.

Procedure

Step 1 Cause 1: An AU pointer adaptation performance indicator crosses the preset threshold.

(1) Check the threshold crossing records of the AU pointer adaptation performance events tofind out the performance event that crosses the preset threshold. For details, see 8.3.8Browsing the Performance Event Threshold-Crossing Records.

(2) Handle the performance event that crosses the threshold.

----End

Related Information

None.

A.3.91 NESOFT_MM

Description

The NESOFT_MM is an alarm indicating that the first software system is different from thesecond software system. This alarm is reported when the NE detects that the first software systemand the second software system of the system control, cross-connect, and timing board mismatchwith each other.

Attribute



Parameters


Name Meaning

Parameter 1 Indicates the location of the file.l 0x01: the files in the flash memory

l 0x02: the software that is currently running




Issue 05 (2010-07-30)

Name Meaning

Parameter 2, Parameter 3 Indicate the IDs of the inconsistent files in the flash memory of thesystem control board if the value of Parameter 1 is 0x01,l 0x01: FPGA of the system control board in ofs1

l 0x02: FPGA of the system control board in ofs2

l 0x03: ofs1/hwx/nesoft.hwx


l 0x05: ofs1/hwx/ne.ini


l 0x07: ofs1/hwx/ocp.ini


l 0x09: ofs1/fpga/if1_002.pga

l 0x0a: ofs2/fpga/if1_002.pga

l 0x0b: ofs1/fpga/if1_250.pga

l 0x0c: ofs2/fpga/if1_250.pga

l 0x0d: ofs1/fpga/sl1d.pga

l 0x0e: ofs2/fpga/sl1d.pga

l 0x0f: ofs1/fpga/sl91ifu2.pga

l 0x10: ofs2/fpga/sl91ifu2.pga

l 0x11: ofs1/fpga/sl91ifx2.pga


l 0x13: ofs1/fpga/sl91aux.pga


l 0x15: ofs1/hwx/lusoft.hwx


l 0x17: ofs1/hwx/lusoft.ini


l 0x19: ofs1/fpga/sl91em6t.pga

l 0x1a: ofs2/fpga/sl91em6t.pga

l 0x1b: ofs1/fpga/pvg610.pga

l 0x1c: ofs2/fpga/pvg610.pga

l 0x1d: ofs1/fpga/pvg610x.pga

l 0x1e: ofs2/fpga/pvg610x.pga

Indicate the IDs of the inconsistent files in the currently runningsoftware if the value of Parameter 1 is 0x02.

l 0x01: NeSoft(D)

l 0x02: Platform(D)

l 0x03: BIOS



A-129

Name Meaning

l 0x04: ExtBios

l 0x05: Logic

l 0x06: Dsp

Parameter 4, Parameter 5 Indicate the cause of the alarm.l 0x04: The file versions in the master and slave areas of a single

system control board are inconsistent.l 0x08: The file versions in the active and standby system control

boards are inconsistent, or that the files in the correspondingdirectories of the active and standby system control boards havedifferent names.

l 0x0c: The file versions in the master and slave areas of a singlesystem control board are inconsistent and the file versions on theactive and standby system control boards are also inconsistent.

Impact on the SystemIf the currently running software is lost, the backup software fails to take over. If no NE softwareexists in the flash memory, the system is unable to restart after power-off or reset.

Possible CausesCause 1: The software fails to be loaded.

Procedure

Step 1 Cause 1: The software fails to be loaded.(1) Contact the Huawei technical support engineers to reload the software.

----End


A.3.92 MULTI_RPL_OWNER

DescriptionThe MULTI_RPL_OWNER is an alarm indicating that the ring network contains severalRPL_OWNER nodes.

Attribute






Issue 05 (2010-07-30)

Parameters


Name Meaning

Parameter 1, Parameter 2 Indicate the ID of the ERPS instance.


The ERPS protection fails.

Possible Causes

Cause 1: The related data is configured incorrectly.

Procedure

Step 1 Cause 1: The related data is configured incorrectly.(1) Reconfigure the ERPS protection. For details, see Creating Ethernet Ring Protection

Instances.

----End

Related Information

None.

A.3.93 MW_BER_EXC

Description

The MW_BER_EXC is an alarm indicating that excessive bit errors occur on the radio link. Thisalarm is reported when the bit errors on the radio link exceed the specified threshold (10-3 bydefault).

Attribute


Minor Service alarm

Parameters

None.



A-131


When the MW_BER_EXC alarm occurs, the service on the port is interrupted.

Possible Causesl Cause 1: Signal attenuation on the radio link is very heavy.

l Cause 2: The receive unit at the local station is faulty.

l Cause 3: The transmit unit at the opposite station is faulty.

Procedure

Step 1 Cause 1: Signal attenuation on the radio link is very heavy.(1) Check whether the MW_FEC_UNCOR alarm is generated. If yes, clear the alarm.

Step 2 Cause 2: The receive unit at the local station is faulty.(1) Replace the IF board.

Step 3 Cause 3: The transmit unit at the opposite station is faulty.(1) Rectify the fault in the transmit unit at the opposite station.

----End

Related Information

None.

A.3.94 MW_BER_SD

Description

The MW_BER_SD is an alarm indicating that signal deteriorates on the radio link. This alarmis reported when the bit errors on the radio link exceed the specified threshold (10-6 by default)but does not reach the MW_BER_EXC alarm threshold (10-3 by default).

Attribute


Minor Service alarm

Parameters

None.


The service performance on the port deteriorates. If the equipment is configured with 1+1 FD/SD protection, switching on the channel side may be triggered.




Issue 05 (2010-07-30)

Possible Causesl Cause 1: Signal attenuation on the radio link is very heavy.

l Cause 2: The receive unit of the local station is faulty.

l Cause 3: The transmit unit of the opposite station is faulty.

Procedure

Step 1 Cause 1: Signal attenuation on the radio link is very heavy.(1) Check whether the MW_FEC_UNCOR alarm is generated. If yes, clear the alarm.

Step 2 Cause 2: The receive unit of the local station is faulty.(1) Replace the IF board.

Step 3 Cause 3: The transmit unit of the opposite station is faulty.(1) Rectify the fault in the transmit unit of the opposite station.

----End


A.3.95 MW_FEC_UNCOR

DescriptionThe MW_FEC_UNCOR is an alarm indicating that radio frames forward error correction (FEC)encoding cannot be corrected.

Attribute



ParametersNone.

Impact on the SystemBit errors occur in the services. If the equipment is configured with 1+1 FD/SD protection, HSMchannel protection switching may be triggered.

Possible Causesl Cause 1: The receive power of the ODU is abnormal.





A-133

l Cause 4: An interference event occurs.

Procedure

Step 1 Cause 1: The receive power of the ODU is abnormal.(1) At the local end, check whether the receive power of the ODU is normal. If yes, determine

the abnormality and take proper measures. For details, see Querying the History TransmitPower and Receive Power

If... Then...

The RSL is lower than the receiversensitivity

Follow the steps:

1. Check the installation of the antenna to ensurethat the azimuth of the antenna meets therequirement.

2. Check the antenna direction. Check whetherthe received signal is from the main lobe.If the antenna direction does not meet therequirement, adjust the antenna in a widerange.

3. Check whether the setting of the polarizationdirection of the antenna is correct. Adjust theincorrect polarization direction.

4. Check whether the antenna gain at both thetransmit and receive ends meets thespecifications. Replace the antennas that donot meet the requirement.

5. Check whether any mountain or buildingobstacle exists in the transmit direction.If yes, contact the network planningdepartment for proper modification of theplanning design, hence preventing the blockof the mountain or building obstacle.




Issue 05 (2010-07-30)

If... Then...

The RSL is higher than the specified RSLof the network. The offset value is tens ofdecibels. The duration is from tens ofseconds to several hours.

Slow up fading occurs. Follow the steps:

1. Check whether any co-channel interferenceoccurs.a. Mute the ODU at the opposite end. For

details, see Configuring the IF/ODUInformation of a Radio Link.

b. Check the RSL at the local end. For details,see Configuring the IF/ODU Information ofa Radio Link. If the RSL exceeds -90 dBm,it indicates that there is co-channelinterference that may affect the long-termavailability and errored-secondperformance of the system.

2. Use a spectrum analyzer to analyze theinterference source.

3. Contact the spectrum managementdepartment to clear the interference spectrumor change plans to minimize the interference.

The RSL is lower than the specified RSLof the network. The offset value is tens ofdecibels. The duration is from tens ofseconds to several hours.

Slow down fading occurs. Generally, the radiolink may be faulty in both directions, becauseslow fading is imposed by the transmission path.Contact the network planning department tomake the following changes:

l Increase the installation height of the antenna.




If the RSL is lower than or higher thanthe specified RSL of the network and ifthe duration is from several millisecondsto tens of seconds.

Fast fading occurs. Contact the network planningdepartment to make the following changes:

l Adjust the position of the antenna to block thereflected wave or make the reflection point fallon the ground that has a small reflectioncoefficient, thus reducing the multipathfading.

l Adjust the RF configuration to make the linksin the 1+1 SD configuration.

l If the links are configured with the 1+1 SDprotection, adjust the height offset betweentwo antennas to make the receive power of oneantenna stronger than the receive power of theother antenna.

l Increase the fading margin.



A-135

Step 2 Cause 2: The transmit unit of the opposite station is faulty.

Locate the fault by looping back the opposite station and excluding the position one by one.Follow the steps:

(1) Perform an inloop on the IF port at the opposite end. For details, see 8.5.4 Setting Loopbackfor the IF Board. Check whether the fault at the opposite end is rectified after the loopback.

If... Then...

The fault at the opposite end is not rectified Replace the IF board.

The fault at the opposite end is rectified Go to the next step.

(2) Check whether the cable connector is prepared according to the requirement. If any cableconnector does not meet the requirement, make a new connector.

(3) Check whether the IF cable is wet, broken, or pressed. Replace the cable that does not meetthe requirement.

(4) Then, check whether the fault at the opposite end is rectified.

If... Then...

The fault at the opposite end is not rectified Replace the ODU at the opposite end.

The fault at the opposite end is rectified End the alarm handling.

Step 3 Cause 3: The receive unit of the local station is faulty.

Locate the fault by looping back the opposite station and excluding the position one by one.Follow the steps:

(1) Perform an inloop on the IF port at the local end. For details, see 8.5.4 Setting Loopbackfor the IF Board. Check whether the fault at the local end is rectified after the loopback.

If... Then...



(2) Check whether the cable connector is prepared according to the requirement. If any cableconnector does not meet the requirement, make a new connector.

(3) Check whether the IF cable is wet, broken, or pressed. Replace the cable that does not meetthe requirement.

(4) Then, check whether the fault at the opposite end is rectified.

If... Then...

The fault at the opposite end is not rectified Replace the ODU at the local end.

The fault at the opposite end is rectified End the alarm handling.

Step 4 Cause 4: An interference event occurs.(1) Check whether any co-channel interference occurs.

a. Mute the ODU at the opposite end.b. Check the RSL at the local end. For details, see Configuring the IF/ODU Information

of a Radio Link. If the RSL exceeds -90 dBm, it indicates that there is co-channel




Issue 05 (2010-07-30)

interference that may affect the long-term availability and errored-secondperformance of the system.

(2) Check whether any adjacent channel interference occurs.

a. Mute the ODU at the opposite end.b. Adjust the radio working mode at the local end and use the minimum channel spacing.

For details, see Configuring the IF/ODU Information of a Radio Link.c. Decrease the received frequency at the local end by a half of the channel spacing. For

details, see Configuring the IF/ODU Information of a Radio Link.d. Test and record the RSL.e. Increase the received frequency at the local end, with a step length of 0.5 MHz or 1

MHz, and record the RSL accordingly until the received frequency is equal to theoriginal received frequency plus a half of the channel spacing.

f. Compare the recorded RSLs, and check whether the RSL in a certain spectrum isabnormal if the received frequency is within the permitted range.

(3) Use a spectrum analyzer to analyze the interference source.(4) Contact the spectrum management department to clear the interference spectrum or change

plans to minimize the interference.

----End

Related Information

None.

A.3.96 MW_LIM

Description

The MW_LIM is an alarm indicating that a mismatched radio link identifier is detected. Thisalarm is reported if an IF board detects that the link ID in the radio frame overheads is inconsistentwith the specified link ID.

Attribute



Parameters

None.


After the IDU IF board reports the MW_LIM alarm, the IF board inserts the AIS alarm into thereceived signal. Then, the services on the radio link are interrupted. If the services are configuredwith SNCP, the protection switching may be triggered.



A-137

Possible Causesl Cause 1: The link ID of the local station does not match with the link ID of the opposite

station.l Cause 2: The services on other radio links are received due to the incorrect configuration

of the radio link receive frequency at the local or opposite station.l Cause 3: The antenna receives the radio from the other stations, because the direction of

the antenna is set incorrectly.l Cause 4: The polarization direction of the XPIC is incorrect.

Procedure

Step 1 Cause 1: The link ID of the local station does not match with the link ID of the opposite station.(1) Check whether the link ID of the local station matches with the link ID of the opposite

station. For details, see Configuring the IF/ODU Information of a Radio Link. If not, setthe link IDs of the two stations to the same value according to the requirements of thenetworking planning.

Step 2 Cause 2: The services on other radio links are received due to the incorrect configuration of theradio link receive frequency at the local or opposite station.(1) Check whether the receive and transmit frequencies of the local station are consistent with

the receive and transmit frequencies of the opposite station. For details, see Configuringthe IF/ODU Information of a Radio Link. If not, set the receive and transmit frequenciesof the two stations again.

Step 3 Cause 3: The antenna receives radio signals from the other stations, because the direction of theantenna is set incorrectly.(1) Adjust the direction of the antenna and ensure that the antennas at both ends are aligned.

Step 4 Cause 4: The polarization direction of the XPIC is incorrect.(1) If XPIC protection groups are configured, check whether the XPIC configuration is correct.

For details, see Creating an XPIC Protection Group.

a. Check whether the settings of IFX board in polarization direction-V andpolarization direction-H meet the requirement of the planning.

If... Then...

The polarization direction does not meetthe requirement of the planning

Delete the working XPIC group that isconfigured incorrectly and create theother working XPIC group again.

The polarization direction meets therequirement of the planning


b. Check whether Link ID-V and Link ID-H meet the requirement of the planning.

If... Then...

The link ID does not meet therequirement of the planning

Reset the ID of the radio link of the IFX2board according to the planning. Fordetails, see Creating an XPIC WorkingGroup.




Issue 05 (2010-07-30)

The link ID meets the requirement of theplanning


(2) Check and modify the IFX2 board and ODU, and the mapping relationship between the

ODU and the feed bottom. Ensure that the IFX2 boards in the polarization direction V ofthe two ends are interconnected with each other through the radio link in the polarizationdirection V, and the IFX2 boards in the polarization direction H of the two ends areinterconnected with each other through the radio link in the polarization direction H.

----End

Related InformationThe MW_LIM alarm is generated due to the inconsistency between the specified link ID andthe received link ID. When the MW-LOF alarm is generated on the link, the received link ID isa random value. In this case, the link ID is invalid. The MW-LIM alarm is also suppressed bythe MW-LOF alarm.

A.3.97 MW_LOF

DescriptionThe MW_LOF is an alarm indicating that the radio frame is lost.

Attribute



ParametersNone.

Impact on the SystemThe services are interrupted. If the system is configured with protection, protection switchingmay be triggered.

Possible Causesl Cause 1: The other alarms are generated.

l Cause 2: In the case of TDM radio services, the IF working modes at the local station andthe opposite station are different. In the case of Hybrid radio services, the channelbandwidth and modulation modes at the local station and the opposite station are different.

l Cause 3: The operating frequency of the ODU at the local station is inconsistent with theoperating frequency of the ODU at the opposite station.





A-139

l Cause 6: The receive power of the ODU is abnormal.

l Cause 7: An interference event occurs.

Procedure

Step 1 Cause 1: The other alarms are generated.(1) Check whether any alarms are generated in the equipment of the local station. If yes, take

priority to clear them.The relevant alarms are as follows:l HARD_BAD

l VOLT_LOS

l IF_CABLE_OPEN

l BD_STATUS

l RADIO_RSL_LOW

l CONFIG_NOSUPPORT

l TEMP_ALARM

Step 2 Cause 2: In the case of TDM radio services, the IF working modes at the local station and theopposite station are different. In the case of Hybrid radio services, the channel bandwidth andmodulation modes at the local station and the opposite station are different.(1) In the case of TDM radio services, check whether the working mode of the IF board at the

local station is consistent with the working mode of the IF board at the opposite station.For details, see Configuring the IF/ODU Information of a Radio Link. If not, reset theworking mode of the IF board according to the network planning.

In the case of Hybrid radio services, check whether the channel bandwidth and modulationmodes are the same at both ends. If not, change the channel bandwidth and modulationmodes according to the network planning. For details, see Configuring Hybrid/AMAttributes.

Step 3 Cause 3: The operating frequency of the ODU at the local station is inconsistent with theoperating frequency of the ODU at the opposite station.(1) Ensure that the type of the ODU at the local station is consistent with the type of the ODU

at the opposite station.(2) Reset the operating frequency of the ODU according to the network planning. For details,

see Setting the Transmit Frequency Attribute of the ODU.Set the transmit frequency of the local station to the same as the receive frequency of theopposite station. Then, set the receive frequency of the local station to the same as thetransmit frequency of the opposite station.

Step 4 Cause 4: The transmit unit of the opposite station is faulty.(1) Check whether any alarms are generated in the equipment of the local station. If yes, take

priority to clear them.The relevant alarms are as follows:l HARD_BAD

l BD_STATUS

l VOLT_LOS




Issue 05 (2010-07-30)

l IF_CABLE_OPEN

l RADIO_MUTE

l RADIO_TSL_HIGH

l RADIO_TSL_LOW

l TEMP_ALARM

(2) Locate the fault by looping back the opposite station.

Follow the steps:

a. Perform an inloop on the IF port at the opposite end. For details, see 8.5.4 SettingLoopback for the IF Board. Check whether the fault at the opposite end is rectifiedafter the loopback.

If... Then...



b. Check whether the cable connector is prepared according to the requirement. If anycable connector does not meet the requirement, make a new connector.

c. Check whether the IF cable is wet, broken, or pressed. Replace the cable that does notmeet the requirement.

d. Then, check whether the fault at the opposite end is rectified.


(1) Locate the fault by looping back the opposite station.

Follow the steps:

a. Perform an inloop on the IF port at the local end. For details, see 8.5.4 SettingLoopback for the IF Board. Check whether the fault at the local end is rectified afterthe loopback.

If... Then...



b. Check whether the cable connector is prepared according to the requirement. If anycable connector does not meet the requirement, make a new connector.

c. Check whether the IF cable is wet, broken, or pressed. Replace the cable that does notmeet the requirement.

d. Check whether the fault at the local end is rectified.

Step 6 Cause 6: The receive power of the ODU is abnormal.

(1) At the local station, check whether the receive power of the ODU is abnormal. For details,see Browse history performance events. If yes, determine the abnormality and take propermeasures.



A-141

If... Then...

The RSL is lower than the receiversensitivity

Follow the steps:

1. Check the installation of the antenna to ensurethat the azimuth of the antenna meets therequirement.

2. Check the antenna direction. Check whetherthe received signal is from the main lobe.If the antenna direction does not meet therequirement, adjust the antenna in a widerange.

3. Check whether the setting of the polarizationdirection of the antenna is correct. Adjust theincorrect polarization direction.

4. Check whether the antenna gain at both thetransmit and receive ends meets thespecifications. Replace the antennas that doesnot meet the requirement.

5. Check whether any mountain or buildingobstacle exists in the transmit direction.If yes, contact the network planningdepartment for proper modification of theplanning design, hence preventing the blockof the mountain or building obstacle.

The RSL is higher than the specified RSLof the network. The offset value is tens ofdecibels. The duration is from tens ofseconds to several hours.

Slow up fading occurs. Follow the steps:

1. Check whether any co-channel interferenceoccurs.a. Mute the ODU at the opposite end. For

details, see Configuring the IF/ODUInformation of a Radio Link.

b. Check the RSL at the local end. For details,see Configuring the IF/ODU Information ofa Radio Link. If the RSL exceeds -90 dBm,it indicates that there is co-channelinterference that may affect the long-termavailability and errored-secondperformance of the system.

2. Use a spectrum analyzer to analyze theinterference source.

3. Contact the spectrum managementdepartment to clear the interference spectrumor change plans to minimize the interference.




Issue 05 (2010-07-30)

If... Then...

The RSL is lower than the specified RSLof the network. The offset value is tens ofdecibels. The duration is from tens ofseconds to several hours.

Slow down fading occurs. Generally, the radiolink may be faulty in both directions, becauseslow fading is imposed by the transmission path.Contact the network planning department tomake the following changes:

l Increase the installation height of the antenna.




If the RSL is lower than or higher thanthe specified RSL of the network and ifthe duration is from several millisecondsto tens of seconds.

Fast fading occurs. Contact the network planningdepartment to make the following changes:

l Adjust the position of the antenna to block thereflected wave or make the reflection point fallon the ground that has a small reflectioncoefficient, thus reducing the multipathfading.

l Adjust the RF configuration to make the linksin the 1+1 SD configuration.

l If the links are configured with the 1+1 SDprotection, adjust the height offset betweentwo antennas to make the receive power of oneantenna stronger than the receive power of theother antenna.

l Increase the fading margin.

Step 7 Cause 7: An interference event occurs.

Follow the steps:

(1) Check whether any co-channel interference occurs.

a. Mute the ODU at the opposite end.b. Check the RSL at the local end. For details, see Configuring the IF/ODU Information

of a Radio Link. If the RSL exceeds -90 dBm, it indicates that there is co-channelinterference that may affect the long-term availability and errored-secondperformance of the system.

(2) Check whether any adjacent channel interference occurs.

a. Mute the ODU at the opposite end.b. Adjust the radio working mode at the local end and use the minimum channel spacing.

For details, see Configuring the IF/ODU Information of a Radio Link.c. Decrease the received frequency at the local end by a half of the channel spacing. For

details, see Configuring the IF/ODU Information of a Radio Link.d. Test and record the RSL.



A-143

e. Increase the received frequency at the local end, with a step length of 0.5 MHz or 1MHz, and record the RSL accordingly until the received frequency is equal to theoriginal received frequency plus a half of the channel spacing.

f. Compare the recorded RSLs, and check whether the RSL in a certain spectrum isabnormal if the received frequency is within the permitted range.

(3) Use a spectrum analyzer to analyze the interference source.(4) Contact the spectrum management department to clear the interference spectrum or change

plans to minimize the interference.

----End


A.3.98 MW_RDI

DescriptionThe MW_RDI is an alarm indicating that there are defects at the remote end of the radio link.This alarm is reported when the IF board detects an RDI in the radio frame overheads.

Attribute



ParametersNone.

Impact on the SystemIf the local station is configured with the reverse switching function, the 1+1 switching istriggered on the IF board when the working and protection IF boards receive the MW_RDI alarmat the same time. This alarm also indicates that the services received by the opposite station areinterrupted.

Possible CausesAfter detecting a service alarm that is caused by the fault in a radio link, the receive stationreturns a radio link fault indication to the transmit station.

Procedure

Step 1 Clear the radio alarms that occur at the opposite station. The possible alarms are as follows:l MW_LOF

l R_LOF




Issue 05 (2010-07-30)

l R_LOC

----End


A.3.99 NESF_LOST

DescriptionThe NESF_LOST is an alarm indicating that the NE software is lost. This alarm is reported whenthe system control, cross-connect, and timing board detects that the NE software is lost.

Attribute




Name Meaning




A-145

Name Meaning

Parameter 2, Parameter 3 Indicate the ID of the routine inspection object.









l 0x09: ofs1/fpga/if1_002.pga

l 0x0a: ofs2/fpga/if1_002.pga

l 0x0b: ofs1/fpga/if1_250.pga

l 0x0c: ofs2/fpga/if1_250.pga

l 0x0d: ofs1/fpga/sl1d.pga

l 0x0e: ofs2/fpga/sl1d.pga

l 0x0f: ofs1/fpga/sl91ifu2.pga

l 0x10: ofs2/fpga/sl91ifu2.pga









l 0x19: ofs1/fpga/sl91em6t.pga

l 0x1a: ofs2/fpga/sl91em6t.pga

l 0x1b: ofs1/fpga/pvg610.pga

l 0x1c: ofs2/fpga/pvg610.pga

l 0x1d: ofs1/fpga/pvg610x.pga

l 0x1e: ofs2/fpga/pvg610x.pga

Parameter 4 Indicates the specific alarm cause when a different bit is 1.

l 0x01: If the first bit is 1, it indicates that the file does not exist.

l 0x02: If the second bit is 1, it indicates that verification of thefile fails.




Issue 05 (2010-07-30)


If the NE software does not exist in the active and standby areas, an NE cannot be restarted afterit is powered off or reset.

Possible Causesl Cause 1: No new NE software is loaded after the existing NE software is erased.

l Cause 2: Loading the NE software is unsuccessful.


Procedure

Step 1 Cause 1: No new NE software is loaded after the existing NE software is erased.

Cause 2: Loading the NE software is unsuccessful.

(1) Check whether the alarm is caused by the loading operation.

If... Then...

The alarm is caused by the loadingoperation

Contact the Huawei technical supportengineers to reload the software.

The alarm is not caused by the loadingoperation


Step 2 Cause 3: The board is faulty.(1) For details, see 6.8 Replacing the System Control, Switch&Clock Board.

----End

Related Information

None.

A.3.100 NESTATE_INSTALL

Description

The NESTATE_INSTALL is an alarm indicating that the NE is in the install state.

Attribute



Parameters

None.



A-147


The NE fails to work.

Possible Causes

Cause 1: The configuration data check fails.

Procedure

Step 1 Cause 1: The configuration data check fails.(1) Restore the data from the backup database.

----End

Related Information

None.

A.3.101 NP1_MANUAL_STOP

Description

The NP1_MANUAL_STOP is an alarm indicating that the N+1 protection protocol is disabledmanually.

Attribute



Parameters


Name Meaning

Parameter 1, Parameter 2 Indicates the ID of the protection group that reports the alarm. Forexample, 0x01 indicates that the alarm is reported by protectiongroup 1.


The N+1 protection may fail, or the protection switching may fail.




Issue 05 (2010-07-30)

Possible CausesCause 1: The N+1 protection protocol is disabled manually.

Procedure

Step 1 Cause 1: The N+1 protection protocol is disabled manually.(1) Start the N+1 protection protocol.

----End


A.3.102 NP1_SW_FAIL

DescriptionThe NP1_SW_FAIL is an alarm indicating that the N+1 protection switching fails.

Attribute




Name Meaning

Parameter 1, Parameter2 Indicates the ID of the protection group that reports the alarm. Forexample, 0x01 indicates that the alarm is reported by protectiongroup 1.

Impact on the SystemThe services cannot be switched. If the current paths are unavailable, the services are interrupted.

Possible Causesl Cause 1: The parameters of the N+1 protection for the node that reports the alarm are set

incorrectly.l Cause 2: The networkwide N+1 protection protocol runs abnormally.



A-149

Procedure

Step 1 Cause 1: The parameters of the N+1 protection for the node that reports the alarm are setincorrectly.(1) Check whether the parameters of the N+1 protection are set correctly according to the

planning. For details, see Creating an N+1 Protection Group.

If... Then...

The parameters of the N+1 protection areset incorrectly

Set the parameters of the N+1 protectioncorrectly.

The parameters of the N+1 protection areset correctly

Go to Cause 2.

Step 2 Cause 2: The networkwide N+1 protection protocol runs abnormally.(1) Stop and restart the protocol manually. For details, see Starting/Stopping the N+1

Protection Protocol.

If... Then...

The alarm is cleared after the protocol isrestarted.


The alarm persists after the protocol isrestarted

Contact the Huawei technical supportengineers to handle the alarm.

----End

Related Information

None.

A.3.103 NP1_SW_INDI

Description

The NP1_SW_INDI is an alarm indicating that the N+1 protection switching is detected.

Attribute



Parameters





Issue 05 (2010-07-30)

Name Meaning

Parameter1, Parameter2 Indicates the ID of the protection group that reports the alarm. Forexample, 0x01 indicates that the alarm is reported by protectiongroup 1.


During the N+1 protection switching (not more than 50 ms), the services are interrupted. Afterthe N+1 switching is complete, the services are restored to normal. After the switching startsand before the switching is complete, the extra traffic is interrupted.

Possible Causes

Cause 1: The N+1 protection switching is performed.

Procedure

Step 1 Cause 1: The N+1 protection switching is performed.

(1) Find out the cause of switching, and take appropriate measures.

----End

Related Information

None.

A.3.104 POWER_ALM

Description

The POWER_ALM is an alarm indicating that the power module is abnormal.

Attribute



Parameters




A-151

Name Meaning

Parameter 1 If the POWER_ALM alarm is reported on a board on the IDU, this parameterindicates the ID of the power module that reports the alarm. For example, 0x01indicates that the alarm is reported by power module 1 of the board.

If the POWER_ALM is reported on the ODU, this parameter indicates the typeof the power fault.l 0x01: The -5 V power supply is faulty.

l 0x02: The power supply for the power amplifier is faulty.

Parameter 2 l 0x01: under-voltage

l 0x02: over-voltage


The power modules are configured with protection. If only one power module reports thePOWER_ALM alarm, the system is not affected.

Possible Causes

If the alarm is reported on the board on the IDU, the possible causes are as follows:

l Cause 1: The input power or the PIU is abnormal.

l Cause 2: The power module is abnormal.

If the alarm is reported on the ODU, the cause is as follows:

l The power module of the ODU is faulty.

Procedure

Step 1 (POWER_ALM reported on the board on the IDU) Cause 1: The input power or the PIU isabnormal.

(1) Check whether alarms are reported on the PIU, If yes, clear these alarms immediately.

Step 2 (POWER_ALM reported on the board on the IDU) Cause 2: The power module is abnormal.

(1) Replace the board that reports the alarm. For details, see 6 Part Replacement.

Step 3 (POWER_ALM reported on the ODU) Cause: The power module of the ODU is faulty.

(1) Replace the ODU. For details, see 6.13 Replacing the ODU.

----End

Related Information

None.

A.3.105 POWER_ABNORMAL




Issue 05 (2010-07-30)

DescriptionThe POWER_ABNORMAL is an alarm indicating that the input power supply is abnormal.

Attribute




Name Meaning

Parameter 1 Indicates the number of the voltage channel.

l 0x01: the first channel of voltage

l 0x01: the second channel of voltage

Parameter 2 Indicates the type of the alarm.

l 0x00: voltage loss

l 0x01: undervoltage

l 0x02: overvoltage

Impact on the SystemWhen the POWER_ABNORMAL alarm occurs, the power supply is abnormal, and thus theboard may fail to work normally.

Possible Causesl Cause 1: The power cable is cut, damaged, or incorrectly connected.

l Cause 2: The input power is abnormal.

ProcedureStep 1 Cause 1: The power cable is cut, damaged, or incorrectly connected.

(1) Check whether the power cable is cut, damaged, or incorrectly connected. If the powercable is cut or damaged, replace it with a proper power cable. If the power cable isincorrectly connected, reconnect the power cable.

Step 2 Cause 2: The input power is abnormal.(1) Contact the engineers for power supply to rectify the fault.

----End



A-153


A.3.106 R_F_RST

DescriptionThe R_F_RST is an alarm indicating that the receive FIFO is reset.

Attribute



ParametersNone.

Impact on the SystemThe services are interrupted.

Possible Causesl Cause 1: The clocks at both stations are not synchronous.


Procedure

Step 1 Cause 1: The clocks at both stations are not synchronous.(1) Query whether a TU pointer adaptation performance event is reported at both ends. For

details, see 8.3.5 Browsing Current Performance Events.

If... Then...

An AU pointer adaptation performanceevent is reported

Handle the performance event. For details,see C.3.21 TUPJCHIGH, TUPJCLOW,and TUPJCNEW.

An AU pointer adaptation performanceevent is not reported

Go to Cause 2.

Step 2 Cause 2: The board is faulty.(1) Replace the board that reports the alarm.

----End





Issue 05 (2010-07-30)

A.3.107 R_LOC

DescriptionThe R_LOC is an alarm indicating that the clock is lost on the receive line side. This alarm isreported when the line board fails to extract clock signal from the line signal or the IF board failsto extract clock signal from the IF signal.

Attribute



ParametersNone.

Impact on the SystemThe services on the line port or the IF port are interrupted. If the system is configured withprotection, protection switching may be triggered.

Possible Causesl Cause 1: The receive unit of the local station is faulty.


Procedure

Step 1 Cause 1: The receive unit of the local station is faulty.(1) At the local end, perform an inloop on the port of the board that reports the alarm. For

details, see 8.5 Software Loopback.

If... Then...

The alarm persists after the loopback Replace the local board that reports thealarm.

The alarm is cleared after the loopback Go to Cause 2.

Step 2 Cause 2: The transmit unit of the opposite station is faulty.(1) Replace the opposite board that reports the alarm.

If... Then...




Replace the cross-connect and timingboard at the opposite end.

----End



A-155

Related Information

None.

A.3.108 R_LOF

Description

The R_LOF is an alarm indicating that frames are lost on the receive side. This alarm is reportedwhen the OOF state lasts for three milliseconds.

Attribute


Critical Commucation alarm

Parameters

None.


The services are interrupted. If the system is configured with protection, protection switchingmay be triggered.

Possible Causesl Cause 1: Certain alarms are generated (if the alarm is reported by an IF board).

l Cause 2: The line performance degrades (if the alarm is reported by an SDH optical interfaceboard).



Procedure

Step 1 Cause 1: Certain high-level alarms are generated (if the alarm is reported by an IF board).

(1) If the alarm is reported by the IF board, check whether the MW_FEC_UNCOR alarm isgenerated.

If... Then...

The alarm is generated Take priority to clear theMW_FEC_UNCOR alarm.

The alarm is not generated Go to the next step.

(2) Set the inloop on the IF port that reports the alarm.




Issue 05 (2010-07-30)

If... Then...

The alarm persists after the inloop isperformed

Go to Cause 4.

The alarm is cleared after the inloop isperformed

Go to Cause 3.


(1) If the alarm is reported by an optical interface board, exchange the transmit and receivefiber jumpers at both ends.

If... Then...

The alarm persists after the exchange Go to Cause 3 or 4

The line port of the opposite station reportsthe R_LOF alarm

Troubleshoot the optical fibers.


(1) Replace the opposite board where the line unit is or the opposite IF board.

If... Then...

The alarm is cleared after the boardreplacement

The fault is rectified, and the alarmhandling is complete.

The alarm persists after the boardreplacement


(2) Replace the system control and cross-connect board at the opposite end.

If... Then...




Go to Cause 4.



----End

Related Information

None.



A-157

A.3.109 R_LOS

Description

In the case of SDH boards, the R_LOS is an alarm indicating that the signals on the receive lineside are lost. In the case of IF boards, the R_LOS is an alarm indicating that the radio frames onthe receive line side are lost.

Attribute



Parameters

None.


The services are interrupted. If the system is configured with protection, the protection switchingmay be triggered.

Possible Causesl Cause 1: Certain alarms are generated (if the alarm is reported by an IF board).

l Cause 2: The line performance degrades (if the alarm is reported by an SDH line board).



Procedure

Step 1 Cause 1: Certain alarms are generated (if the alarm is reported by an IF board).(1) If the alarm is reported by the IF board, check whether the MW_FEC_UNCOR alarm is

generated.

If... Then...

The alarm is generated Take priority to clear theMW_FEC_UNCOR alarm.

The alarm is not generated Go to the next step.

(2) Set the inloop on the IF port that reports the alarm.

If... Then...

The alarm persists after the inloop isperformed

Go to Cause 4.




Issue 05 (2010-07-30)

If... Then...

The alarm is cleared after the inloop isperformed

Go to Cause 3.

Step 2 Cause 2: The line performance degrades (if the alarm is reported by an SDH line board).

(1) If the alarm is reported by an optical interface board, exchange the transmit and receivefiber jumpers at both ends.

If... Then...

The alarm persists after the exchange Go to Cause 3 or 4

The line port of the opposite station reportsthe R_LOF alarm

Troubleshoot the optical fibers.


(1) Replace the opposite board where the line unit is or the opposite IF board.

If... Then...




Proceed to the next step.

(2) Replace the system control and cross-connect board at the opposite end.

If... Then...




Go to Cause 4.



----End

Related Information

None.

A.3.110 R_S_ERR



A-159

Description

The R_S_ERR is an alarm indicating that the received signal has errors.

Attribute



Parameters

None.


The services are interrupted.



Procedure

Step 1 Cause 1: The frequency offset of the input signal is very large.

(1) Check whether the tributary board supports the type of the input signal.

If... Then...

The tributary board does not support thetype of the input signal.

Change the type of the output signal of theremote site.

The tributary board supports the type ofthe input signal.


(2) Test the frequency offset of the input signal.

If... Then...


The frequency offset meets the requirement Go to Cause 2.

Step 2 Cause 2: The board is faulty.


----End

Related Information

None.




Issue 05 (2010-07-30)

A.3.111 RADIO_FADING_MARGIN_INSUFF

DescriptionThe RADIO_FADING_MARGIN_INSUFF is an alarm indicating that the mean receive powerof the ODUs are lower than the threshold of the receive power (the threshold value is about thereceiver sensitivity + 14dB).

When the receive power of the ODUs in consecutive six hours is lower than the threshold, thesystem reports the alarm. When the mean receive power of the ODUs becomes normal in threeminutes after the alarm is reported, the alarm is cleared.

Attribute



ParametersNone.

Impact on the SystemIf the MW_LOF or MW_FEC_UNCOR alarm is not generated, the service is not affected.

Possible Causesl Cause 1: The ODU fault of the transmit end causes the abnormal transmit power.

l Cause 2: The direction of the antenna is deflected.

l Cause 3: The transmission environment changes.

l Cause 4: The fade margin in the case of rain and fog in the network planning is insufficient.

Procedure

Step 1 Cause 1: The ODU fault of the transmit end causes the abnormal transmit power.(1) Check whether the ODU at the transmit end reports the RADIO_TSL_LOW alarm.

If... Then...

The ODU at the transmit end reports theRADIO_TSL_LOW alarm

Handle the RADIO_TSL_LOW alarm.

The ODU at the transmit end does not report theRADIO_TSL_LOW alarm

Go to Cause 2.

Step 2 Cause 2: The direction of the antenna is deflected.(1) Check whether the direction of the antenna is deflected.

If... Then...

The direction of the antenna is deflected Adjust the direction of the antenna.



A-161

If... Then...

The direction of the antenna is not deflected Go to Cause 3.

Step 3 Cause 3: The transmission environment changes.(1) Check whether the transmission environment changes. For example, check whether any

building blocks the transmission and increases the link fading significantly.

If... Then...

The transmission environment changes Contact the network planning department forre-planning the transmission trail.

The transmission environment does notchange

Go to Cause 4.

Step 4 Cause 4: The fade margin in the case of rain and fog in the network planning is insufficient.(1) If the alarm is reported frequently, contact the network planning department to increase the

fade margin by re-planning the transmission trail.

----End


A.3.112 RADIO_MUTE

DescriptionThe RADIO_MUTE is an alarm indicating that radio transmitter is muted.

Attribute


Warning Equipment alarm

ParametersNone.

Impact on the SystemThe transmitter does not transmit services.

Possible Causesl Cause 1: The other alarms are generated.

l Cause 2: The transmitter of the local station is muted manually.

l Cause 3: The IF board is faulty, causing abnormal IF output.




Issue 05 (2010-07-30)

l Cause 4: The data output is abnormal because the ODU is faulty.

Procedure

Step 1 Cause 1: The other alarms are generated.(1) Check whether the CONFIG_NOSUPPORT or IF_INPWR_ABN alarm is generated. If

yes, take priority to clear the alarm.

Step 2 Cause 2: The transmitter of the local station is muted manually.(1) Check whether the transmitter of the ODU is muted. For details, see Configuring the IF/

ODU Information of a Radio Link. If yes, cancel the muting operation. Then, set thetransmitting status of the ODU to "Transmit".

Step 3 Cause 3: The IF board is faulty, causing abnormal IF output.(1) Replace the IF Board.

Step 4 Cause 4: The data output is abnormal because the ODU is faulty.(1) Replace the ODU.

----End

Related InformationThe number of the logical slot for the ODU is the number of the slot for the IF board connectedto the ODU plus +20.

A.3.113 RADIO_RSL_BEYONDTH

DescriptionThe RADIO_RSL_BEYONDTH is an alarm indicating that the antennas are not aligned. Whenthe receive power is set on the NE, the NE enables the antenna alignment indication function.If the actual receive power of the ODU is beyond the range of preset receive power +/-3 dB, theRADIO_RSL_BEYONDTH alarm is reported. Then, if the antennas are aligned for continuos30 minutes, the antenna alignment indication function is disabled automatically. Afterwards, theRADIO_RSL_BEYONDTH alarm is reported only when theRADIO_FADING_MARGIN_INSUFF alarm is reported.

Attribute



ParametersNone.

Impact on the SystemIf the MW_LOF or MW_FEC_UNCOR alarm is not generated, the service is not affected.



A-163

Possible Causesl Cause 1: Antennas are not aligned during the equipment commissioning.

l Cause 2: The RADIO_FADING_MARGIN_INSUFF is reported when the NE is running.

Procedure

Step 1 Cause 1: Antennas are not aligned during the equipment commissioning.(1) Align the antennas, and ensure that the actual receive power is within the range of preset

receive power +/-3 dB.

Step 2 Cause 2: The RADIO_FADING_MARGIN_INSUFF is reported when the NE is running.(1) Handle the RADIO_FADING_MARGIN_INSUFF alarm. When the

RADIO_FADING_MARGIN_INSUFF alarm is cleared, the RADIO_RSL_BEYONDTHalarm is cleared.

----End


A.3.114 RADIO_RSL_HIGH

DescriptionThe RADIO_RSL_HIGH is an alarm indicating that the radio receive power is very high. Thisalarm is reported if the detected receive power is equal to or higher than the upper threshold ofthe ODU (-20 dBm).

Attribute


Critical Service alarm

ParametersNone.

Impact on the SystemThe service transmission is affected. If the system is configured with 1+1 protection, protectionswitching may be triggered.

Possible Causesl Cause 1: The local ODU is faulty.

l Cause 2: There is a strong interference source nearby.

l Cause 3: The transmit power of the opposite ODU is very high.




Issue 05 (2010-07-30)

Procedure

Step 1 Cause 1: The local ODU is faulty.

(1) 6.13 Replacing the ODU.

Step 2 Cause 2: There is a strong interference source nearby.

(1) Check whether any nearby signal source transmits signals whose frequency is close to thespecified range. If yes, check whether the signal source can be shut down or removed. Ifnot, contact the network planning department for replanning the frequency.

Step 3 Cause 3: The transmit power of the opposite ODU is very high

(1) Reset the transmit power of the ODU at the opposite end. For details, see Configuring theIF/ODU Information of a Radio Link.

----End

Related Information

None.

A.3.115 RADIO_RSL_LOW

Description

The RADIO_RSL_LOW is an alarm indicating that the radio receive power is very low. Thisalarm is reported if the detected receive power is equal to or lower than the upper threshold ofthe ODU (-90 dBm).

Attribute



Parameters

None.


If no MW_LOF or MW_FEC_UNCOR alarm is generated, the services are not affected.

Possible Causesl Cause 1: Other alarms occur at the opposite station.

l Cause 2: The transmit power of the opposite station is very low.

l Cause 3: The local ODU is faulty.

l Cause 4: Signal attenuation on the radio link is very heavy.



A-165

Procedure

Step 1 Cause 1: Other alarms occur at the opposite station.Check whether any of the following alarms is generated in the equipment of the opposite station.If yes, take priority to clear the alarm.

l RADIO_MUTE

l CONFIG_NOSUPPORT

l RADIO_TSL_LOW

l BD_STATUS

Step 2 Cause 2: The transmit power of the opposite station is very low.

(1) See Configuring the IF/ODU Information of a Radio Link. Check whether the transmitpower of the opposite station is normal. If not, replace the ODU of the opposite station.

Step 3 Cause 3: The local ODU is faulty.

(1) Replace the ODU at the local end.

Step 4 Cause 4: Signal attenuation on the radio link is very heavy.

(1) Browse history alarms and check whether the alarm is generated continuously.

If the alarm is generated occasionally, contact the network planning department to changethe design to increase the anti-fading performance.

(2) Check whether the antennas at both ends are adjusted properly.

If not, align the antennas again.

(3) Check whether any mountain or building obstacle exists in the transmit direction.

If yes, contact the network planning department for proper modification of the planningdesign, hence preventing the block of the mountain or building obstacle.

(4) Check whether the polarization direction of the antenna, ODU, and hybrid coupler is setcorrectly.

If not, correct the polarization direction.

(5) Check whether the outdoor units such as antennas, combiner, ODU, and flexible waveguideare wet, damp, or damaged.

If yes, replace the unit that is wet, damp, or damaged. For the operations, see 6 PartReplacement

(6) Check whether the antenna gain at both the transmit and receive ends meets the requirement.

If not, replace the antenna.

----End

Related Information

None.

A.3.116 RADIO_TSL_HIGH




Issue 05 (2010-07-30)

Description

The RADIO_TSL_HIGH is an alarm indicating that the radio transmit power is too high. Thisalarm is reported when the detected transmit power is higher than the upper power threshold ofthe ODU.

Attribute



Parameters

None.


The service transmission is affected. If the system is configured with 1+1 protection, protectionswitching may be triggered.

Possible Causes

Cause 1: The local ODU is faulty.

Procedure

Step 1 Cause 1: The local ODU is faulty.(1) Replace the ODU.

----End

Related Information

None.

A.3.117 RADIO_TSL_LOW

Description

The RADIO_TSL_LOW is an alarm indicating that the radio transmit power is very low. Thisalarm is reported when the detected transmit power is less than the lower power threshold of theODU.

Attribute





A-167

ParametersNone.

Impact on the SystemThe service transmission is affected. If the system is configured with 1+1 protection, protectionswitching may be triggered.

Possible CausesCause 1: The local ODU is faulty.

Procedure

Step 1 Cause 1: The local ODU is faulty.(1) Replace the ODU.

----End


A.3.118 RELAY_ALARM_CRITICAL

DescriptionThe RELAY_ALARM_CRITICAL is an alarm indicating the critical alarm inputs. This alarmoccurs when the user sets the severity of an available alarm input to critical and there is such analarm input.

Attribute




Name Meaning

Parameter 1 Indicates the number of the alarm input/output.

The value ranges from 0x01 to 0x08.




Issue 05 (2010-07-30)


When the RELAY_ALARM_CRITICAL alarm occurs, it does not affect the operation of theboard or the services on the NE.

Possible Causes

There is a critical alarm input.

Procedure

Step 1 Cause: There is a critical alarm input.

(1) Check the alarm parameters and confirm the number of the alarm input/output.

(2) Clear the alarms of the external equipment according to the defined meanings of the alarms.Then, the RELAY_ALARM_CRITICAL alarm is cleared.

----End

Related Information

None.

A.3.119 RELAY_ALARM_MAJOR

Description

The RELAY_ALARM_MAJOR is an alarm indicating the major alarm inputs. This alarm occurswhen the user sets the severity of an available alarm input to major and there is such an alarminput.

Attribute



Parameters


Name Meaning





A-169


When the RELAY_ALARM_MAJOR alarm occurs, it does not affect the operation of the boardor the services on the NE.

Possible Causes

There is a major alarm input.

Procedure

Step 1 Cause: There is a major alarm input.(1) Check the alarm parameters and confirm the number of the alarm input/output.(2) Clear the alarms of the external equipment according to the defined meanings of the alarms.

Then, the RELAY_ALARM_MAJOR alarm is cleared.

----End

Related Information

None.

A.3.120 RELAY_ALARM_MINOR

Description

The RELAY_ALARM_MINOR is an alarm indicating the minor alarm inputs. This alarm occurswhen the user sets the severity of an available alarm input to minor and there is such an alarminput.

Attribute



Parameters


Name Meaning






Issue 05 (2010-07-30)


When the RELAY_ALARM_MINOR alarm occurs, it does not affect the operation of the boardor the services on the NE.

Possible Causes

There is a minor alarm input.

Procedure

Step 1 Cause: There is a minor alarm input.

(1) Check the alarm parameters and confirm the number of the alarm input/output.

(2) Clear the alarms of the external equipment according to the defined meanings of the alarms.Then, the RELAY_ALARM_MINOR alarm is cleared.

----End

Related Information

None.

A.3.121 RELAY_ALARM_IGNORE

Description

The RELAY_ALARM_IGNORE is an alarm indicating the warning alarm inputs. This alarmoccurs when the user sets the severity of an available alarm input to warning and there is suchan alarm input.

Attribute



Parameters


Name Meaning





A-171

Impact on the SystemWhen the RELAY_ALARM_IGNORE alarm occurs, it does not affect the operation of the boardor the services on the NE.

Possible CausesThere is a warning alarm input.

Procedure

Step 1 Cause: There is a warning alarm input.(1) Check the alarm parameters and confirm the number of the alarm input/output.(2) Clear the alarms of the external equipment according to the defined meanings of the alarms.

Then, the RELAY_ALARM_IGNORE alarm is cleared.

----End


A.3.122 RP_LOC

DescriptionThe RP_LOC is an alarm indicating that the receiving phaselock ring clock is lost.

Attribute



ParametersNone.

Impact on the SystemThe services on the board are interrupted.

Possible Causesl Cause 1: The related data is configured incorrectly.


Procedure

Step 1 Cause 1: The related data is configured incorrectly.




Issue 05 (2010-07-30)

(1) Check whether the services are correctly configured.

If... Then...

The services are configured incorrectly Reconfigure services.

The services are configured correctly Go to Cause 2.

Step 2 Cause 2: The board is faulty.(1) Replace the board.

----End


A.3.123 RPS_INDI

DescriptionThe HSM_INDI is an alarm indicating that the radio protection switching is detected.

Attribute




Name Meaning

Parameter 1 Indicates the ID of the protection group.

Parameter 2 Indicates the type of protection switching.

0x01: HSB protection switching

0x02: HSM protection switching

Impact on the SystemDuring the HSB protection switching, services are interrupted. After the HSB switching iscomplete, the services are restored to normal.

During the HSM protection switching, no bit errors occur and the services are not affected.



A-173

Possible Causesl The possible causes of HSB protection switching are as follows:

– Cause 1: An external switching event occurs

– Cause 2: An automatic switching event occurs.

– Cause 3: A reverse switching event occurs.

l The possible causes of HSM protection switching are as follows:– In the case of Hybrid radio, the automatic switching condition of the HSM is that the

quality of the main channel degrades.– In the case of SDH/PDH radio, an alarm that triggers HSM switching is reported on the

radio link.

Procedure

Step 1 Determine the type of the protection switching based on the alarm parameters.

Step 2 Cause 1 of HSB switching: An external switching event occurs. That is, the NMS issues acommand to trigger the switching.(1) Check whether the switching is the forced switching or manual switching. For details, see

Querying the IF 1+1 Protection Status.

If... Then...

The switching is the forced switching ormanual switching

Find the cause and release the switchingimmediately.

The switching is not the forcedswitching or manual switching

Go to Cause 2 of HSB switching.

Step 3 Cause 2 of HSB switching: An automatic switching event occurs. That is, the equipment is faulty,or the service is defective.(1) Check whether the following faults or alarms occur. If yes, rectify the faults or clear the

alarms.l The hardware of the IF board or the ODU is faulty.

l VOLT_LOS

l RADIO_TSL_HIGH, RADIO_TSL_LOW, or RADIO_RSL_HIGH

l IF_INPWR_ABN or CONFIG_NOSUPPORT

l R_LOC, R_LOF, R_LOS, or MW_LOF

NOTE

l If the switching is non-revertive, the services are not automatically switched to the working pathwhen the working path is restored to normal, and the RPS_INDI alarm persists. In this case, youneed to manually switch the services from the protection path to the working path. The RPS_INDIalarm is cleared only when the switching is successful.

l If the switching is revertive, the services are automatically switched to the working path onlywhen the specified wait-to-restore (WTR) time expires after the working path is restored tonormal. The RPS_INDI alarm is cleared only when the switching is successful.

Step 4 Cause 3 of HSB switching: A reverse switching event occurs.(1) Query whether the active and standby IF boards report the MW_RDI alarm. If yes, take

priority to clear the MW_RDI alarm.




Issue 05 (2010-07-30)

Step 5 Cause 1 of HSM switching: In the case of Hybrid radio, the quality of the main channel degrades.(1) Check whether the AM_DOWNSHIFT alarm is reported by an IF board. If the alarm is

reported by an IF board, refer to AM_DOWNSHIFT to rectify the fault that causes thequality of the main channel to degrade. If the alarm is not reported by an IF board, thequality of the main channel degrades possibly due to the weather. In this case, you do notneed to handle the problem, because this is a normal situation.

Step 6 Cause 2 of HSM switching: In the case of SDH/PDH radio, an alarm that triggers HSM switchingis reported on the radio link.(1) Check whether any alarm that triggers HSM switching is reported by an IF board of the IF

1+1 protection group. If yes, take priority to clear the alarm.HSM switching may be triggered by any of the following alarms:l R_LOC, R_LOF, R_LOS, or MW_LOF

l MW_FEC_UNCOR

l B1_SD or B2_SD

----End


A.3.124 RS_CROSSTR

DescriptionThe RS_CROSSTR is an alarm indicating that a regenerator section performance indicatorcrosses the threshold. This alarm is reported if a board detects that a regenerator section bit errorperformance event crosses the preset threshold.

Attribute


Minor Service alarm




A-175

Name Meaning


l 0x01: 15 minutes

l 0x02: 24 hours


Impact on the SystemA large number of bit errors occur in the services, and the services may be interrupted.

Possible CausesCause 1: The regenerator section bit error performance indicator crosses the preset threshold.

Procedure

Step 1 Cause 1: The regenerator section bit error performance indicator crosses the preset threshold.(1) Find out the performance event that crosses the preset threshold. For details, see 8.3.8

Browsing the Performance Event Threshold-Crossing Records.(2) Handle the performance event that crosses the threshold.

----End


A.3.125 RTC_FAIL

DescriptionThe RTC_FAIL is an alarm indicating that the real-time clock (RTC) on the system controlboard fails.

Attribute



ParametersNone.

Impact on the SystemThe service is not affected.




Issue 05 (2010-07-30)

Possible Causes

Cause 1: The RTC on the system control board is abnormal.

Procedure

Step 1 Cause 1: The RTC on the system control board is abnormal.(1) Replace the system control, switching, and timing board.

----End

Related Information

None.

A.3.126 S1_SYN_CHANGE

Description

The S1_SYN_CHANGE is an alarm indicating that the clock source is switched in S1 bytemode.

Attribute



Parameters


Name Meaning



If the new clock source has a lower quality, pointer justifications and bit errors are generatedafter the switching of clock source. As a result, the quality of services is affected.

Possible Causes

Cause 1: The original clock source is lost when the SSM protocol or extended SSM protocol isenabled.



A-177

Procedure

Step 1 Cause 1: The original clock source is lost when the SSM protocol or extended SSM protocol isenabled.(1) Handle the SYNC_C_LOS alarm that is related to the original clock source.

----End


A.3.127 SWDL_ACTIVATED_TIMEOUT

DescriptionThe SWDL_ACTIVATED_TIMEOUT is an alarm indicating the activation timeout of thesoftware package. During the package loading, the system reports the alarm if no data issubmitted within 30 minutes after activation of the NE software or board software.

Attribute



ParametersNone.

Impact on the SystemThe NE does not perform the submit operation. As a result, the software in the two areas of thedouble-area boards on the NE is inconsistent.

Possible CausesCause 1: The radio link is faulty. As a result, the NE involved in the package loading fails toreceive the submit command.

Procedure

Step 1 Cause 1: The radio link is faulty. As a result, the NE involved in the package loading fails toreceive the submit command.(1) Check whether the radio link is faulty.

If... Then...

The radio link is faulty Troubleshoot the radio link to ensure that the linkbetween the nodes to be loaded is normal.




Issue 05 (2010-07-30)

If... Then...

The radio link is normal Perform the package loading to the NE again.

----End


A.3.128 SWDL_AUTOMATCH_INH

DescriptionThe SWDL_AUTOMATCH_INH is an alarm indicating that the automatic match function isdisabled. When the automatic match function of the board is disabled, the system reports thealarm if the board cannot match the software from the system control board.

Attribute



ParametersNone.

Impact on the SystemWhen a board whose version is not consistent with the software version of the NE is installed,the software versions of the whole NE are not consistent if the board cannot automatically matchthe software from the system control board. As a result, certain functions of the NE cannot runnormally.

Possible CausesCause 1: The automatic match function is disabled.

Procedure

Step 1 Cause 1: The automatic match function is disabled.(1) Contact the Huawei technical support engineers for troubleshooting.

----End


A.3.129 SWDL_CHGMNG_NOMATCH



A-179

Description

The SWDL_CHGMNG_NOMATCH is an alarm of software inconsistency. After an NE ispower recycled and the boards on the NE become online, if the system detects that the softwareversion of any board is different from that in the software package on the SCC board, or detectsthat the CF card and flash memory on the SCC board are inconsistent in software packages, thesystem reports the SWDL_CHGMNG_NOMATCH alarm.

Attribute



Parameters

None.


When the SWDL_CHGMNG_NOMATCH alarm is reported, certain functions of the NE maybe affected because the board software version is inconsistent with the running software version.

Possible Causes

Cause 1: The software package of the system control board does not match with the softwareversion of the board after the system control board is replaced.

Procedure

Step 1 Cause 1: The software package of the system control board does not match with the softwareversion of the board after the system control board is replaced.

(1) Perform the package diffusion again on the NE where the SWDL_CHGMNG_NOMATCHalarm is reported.

----End

Related Information

None.

A.3.130 SWDL_COMMIT_FAIL

Description

The SWDL_COMMIT_FAIL is an alarm indicating that the commission operation on the NEfails. This alarm is reported when the commission operation fails in the package diffusion.




Issue 05 (2010-07-30)

Attribute



Parameters

None.


When the SWDL_COMMIT_FAIL alarm occurs, the software versions in the two areas of thedouble-area board are inconsistent.

Possible Causes

Cause 1: The loaded package is incorrect.

Procedure

Step 1 Cause 1: The loaded package is incorrect.

(1) Check whether the loaded package is correct.

(2) Perform the package diffusion again on the NE where the alarm is reported.

----End

Related Information

None.

A.3.131 SWDL_INPROCESS

Description

The SWDL_INPROCESS is an alarm indicating that the package diffusion is in process on theNE.

Attribute


Warning Processing alarm

Parameters

None.



A-181


When the SWDL_INPROCESS alarm is reported, the operations, such as modifyingconfiguration, uploading/downloading files, and backing up the database, are not allowed,because the software package is being loaded to the NE.

Possible Causes

The package diffusion is being performed on the NE.

Procedure

Step 1 The SWDL_INPROCESS alarm is cleared automatically after the loading or rollback iscomplete. Hence, this alarm can be neglected.

----End

Related Information

None.

A.3.132 SWDL_NEPKGCHECK

Description

The SWDL_NEPKGCHECK is an alarm of software inconsistency. This alarm is reported inthe following two situations: the CF card and flash memory are inconsistent in software packageand the flash memory has a software package; in a routine check (the check is not initiated byissuing commands), the system detects that some files are missing from the software packagestored in the CF card or from the software package stored in the flash memory.

Attribute



Parameters

None.


The NE may run abnormally because certain files of the package are missing.

Possible Causes

Cause 1: Certain files of the package are missing and cannot be recovered.




Issue 05 (2010-07-30)

Procedure

Step 1 Cause 1: Certain files of the package are missing and cannot be recovered.(1) Ensure that the loaded software package is correct. Perform the package diffusion again on

the NE where the SWDL_NEPKGCHECK alarm is reported.

----End


A.3.133 SWDL_PKG_NOBDSOFT

DescriptionThe SWDL_PKG_NOBDSOFT is an alarm indicating that certain board software is missingfrom the software package. This alarm is reported when the required software is missing fromthe software package during the automatic match of the board.

Attribute



ParametersNone.

Impact on the SystemThe board cannot perform automatic match, because the board software is missing from thesoftware package. Thus, the board software version is inconsistent with the NE software version,and certain functions of the NE may be affected.

Possible CausesCause 1: Certain board software is uninstalled during the software package loading.

Procedure

Step 1 Cause 1: Certain board software is uninstalled during the software package loading.(1) Add the required board software to the software package. Alternatively, perform the

software package loading again.

----End




A-183

A.3.134 SWDL_PKGVER_MM

Description

The SWDL_PKGVER_MM is an alarm indicating that the consistency check on the softwarepackage version fails. This alarm is reported when the consistency check on the software packageversion fails.

Attribute



Parameters

None.


The software version of the software package is inconsistent with the software version describedin the software package. As a result, certain functions of the NE may be affected.

Possible Causes

Cause 1: The software version information in the description file of the software package isinconsistent with the actual software version information.

Procedure

Step 1 Cause 1: The software version information in the description file of the software package isinconsistent with the actual software version information.

(1) Ensure that the loaded software package is correct. Perform the package diffusion again onthe NE where the alarm is reported.

----End

Related Information

None.

A.3.135 SWDL_ROLLBACK_FAIL

Description

The SWDL_ROLLBACK_FAIL is an alarm indicating that the rollback on the NE fails. Thisalarm is reported when the rollback fails for any board on the NE.




Issue 05 (2010-07-30)

Attribute



ParametersNone.

Impact on the SystemThe board software version and the NE software version may mismatch, and certain functionsof the NE may be affected.

Possible CausesCause 1: Certain board software is uninstalled during the software package loading.

Procedure

Step 1 Cause 1: Certain board software is uninstalled during the software package loading.(1) Add the required board software to the software package. Alternatively, perform the

software package loading again.

----End


A.3.136 SYNC_C_LOS

DescriptionThe SYNC_C_LOS is an alarm indicating that the synchronization source is lost.

Attribute



ParametersNone.

Impact on the SystemThe NE clock degrades or enters the free-run mode.



A-185

Possible CausesCause 1: The clock source is lost.

Procedure

Step 1 Cause 1: The clock source is lost.(1) Troubleshoot the synchronization sources of the lost clock source based on the clock source

priority table.

If... Then...

The synchronization source is theexternal clock

Handle the EXT_SYNC_LOS alarm.

The synchronization source is the lineclock

Handle the alarm that occurs on the lineboard.

The synchronization source is the IFclock

Handle the alarm that occurs on the IF board.

The synchronization source is thetributary clock

Handle the alarm that occurs on the tributaryboard.

----End


A.3.137 T_ALOS

DescriptionThe T_ALOS is an alarm indicating that the 2 Mbit/s analog signal is lost at the specific port.

Attribute



ParametersNone.

Impact on the SystemThe 2Mbit/s services are interrupted.

Possible Causesl Cause 1: No 2 Mbit/s services are accessed into the port.




Issue 05 (2010-07-30)


l Cause 3: The IF cable is faulty.

l Cause 4: The board that reports the alarm is faulty.

Procedure

Step 1 Cause 1: No 2 Mbit/s services are accessed into the port.

(1) Check whether the port that reports the alarm accesses the 2 Mbit/s service.

If... Then...

The services are not accessed Access the services to the port or delete the unnecessaryservice configuration.

The services are accessed Go to Cause 2.

Step 2 Cause 2: The equipment at the opposite end is faulty.

(1) Check whether the equipment at the opposite end is faulty.

If... Then...


The equipment is normal Go to Cause 3.

Step 3 Cause 3: The IF cable is faulty.

(1) Check whether the IF cable is faulty.

If... Then...

The IF cable is faulty Rectify the fault.

The IF cable is not faulty Go to Cause 4.

Step 4 Cause 4: The board that reports the alarm is faulty.


----End

Related Information

None.

A.3.138 T_F_RST

Description

The T_F_RST is an alarm indicating that the transmit FIFO is reset.



A-187

Attribute



Parameters

None.


The services in the PDH path are interrupted.



Procedure

Step 1 Cause 1: The frequency offset of the input signal is very large.(1) Measure the frequency offset of the input signal.

If... Then...


The frequency offset is within 50 ppm Go to Cause 2.

Step 2 Cause 2: The board is faulty.(1) Replace the board that reports the alarm.

----End

Related Information

None.

A.3.139 T_LOC

Description

The T_LOC is an alarm indicating that the clock is lost on the transmit line side.

Attribute






Issue 05 (2010-07-30)

ParametersNone.

Impact on the SystemThe services in the AU-4 path that reports the alarm are interrupted.

Possible Causesl Cause 1: The cross-connect and timing board is faulty.

l Cause 2: The line board is faulty.

Procedure

Step 1 Cause 1: The cross-connect and timing board is faulty.(1) Replace the cross-connect and timing board at the local station.

If... Then...




Go to Cause 2.

Step 2 Cause 2: The line board is faulty.(1) Replace the board that reports the alarm.

----End


A.3.140 TEMP_ALARM

DescriptionThe TEMP_ALARM is an alarm indicating that the board temperature crosses the threshold.

Attribute


Minor Environmental alarm

ParametersWhen you view an alarm on the network management system, select the alarm. In the AlarmDetails field display the related parameters of the alarm. The alarm parameters are in thefollowing format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,



A-189

Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the followingtable.

Name Meaning

Parameter 1 l 0x01: The temperature crosses the upper threshold.

l 0x02: The temperature crosses the lower threshold.


The board fails to work normally.

Possible Causesl Cause 1: The board temperature crosses the threshold.

l Cause 2: The temperature detection circuit of the board is faulty.

Procedure

Step 1 Cause 1: The board temperature crosses the threshold.

(1) If the alarm is reported by the ODU, take appropriate measures (for example, installing asunshade) to control the temperature.

(2) If the alarm is reported by the board on the IDU, check whether the temperature controldevices, such as air-conditioners, work normally.

If... Then...

The temperature control devices workabnormally

Adjust the temperature control devices.

The temperature control devices worknormally


(3) Check whether the heat dissipation hole on the IDU is covered or blocked.

If... Then...

The heat dissipation hole is covered orblocked

Clear or remove the covering materials orobstacles.

The heat dissipation hole is not covered orblocked

Go to Cause 2.

Step 2 Cause 2: The temperature detection circuit of the board is faulty.

(1) If the ambient temperature is normal and no other heat dissipation problems exist, replacethe board that reports the alarm.

----End

Related Information

None.




Issue 05 (2010-07-30)

A.3.141 THUNDERALM

DescriptionThe THUNDERALM is an alarm indicating the lightning protection failure. If the system detectsthe lightning protection circuit fails, the THUNDERALM occurs.

Attribute


Minor Environment alarm

ParametersNone.

Impact on the SystemWhen the THUNDERALM occurs, the system operation and services are not affected, but thelightning protection function fails.

Possible CausesThe possible causes of the THUNDERALM alarm are as follows:

l Cause 1: The fuse tube of the lightning protection circuit is interrupted.


Procedure

Step 1 Cause 1: The fuse tube of the lightning protection circuit is interrupted.(1) Replace the fuse tube, and then check whether the alarm is cleared.

Step 2 Cause 2: The board is faulty.(1) Replace the board that reports the THUNDERALM alarm.

----End


A.3.142 TU_AIS

DescriptionThe AU_AIS is an alarm indicating that the TU has errors. This alarm is reported if a boarddetects that the signal in the TU path is all 1s.



A-191

Attribute



ParametersNone.

Impact on the SystemThe service in the TU path that reports the alarm is interrupted. If the service is configured withprotection, the protection switching is also triggered.

Possible Causesl Cause 1: Configuration data is incorrect.

l Cause 2: The line is faulty.

l Cause 3: The board at the opposite end is faulty.

l Cause 4: The board at the local end is faulty.

Procedure

Step 1 Cause 1: Configuration data is incorrect.(1) See Creating the Cross-Connections of Point-to-Point Services to check whether the SDH

service data is incorrect.

If... Then...

The SDH service data is incorrect Change the configuration data.

The SDH service data is correct Go to Cause 2.

Step 2 Cause 2: The line is faulty.(1) Check whether a line alarm that causes AIS insertion is reported on the service trail.

NOTEFor details about the line alarms that cause AIS insertion, see E.2.6 AIS Insertion.

If... Then...

The line alarm is reported Clear the line alarms that cause AIS insertion.

No line alarms are reported Go to the next step.

(2) See 8.5 Software Loopback to locate whether the board at the local end or at the oppositeend is faulty.

If... Then...

The board at the opposite end is faulty Go to Cause 3.

The board at the local end is faulty Go to Cause 4.




Issue 05 (2010-07-30)

Step 3 Cause 3: The board at the opposite end is faulty.(1) Replace the faulty board at the opposite end.

Step 4 Cause 4: The board at the local end is faulty.(1) Replace the board where the local line unit resides.

If... Then...





(2) Replace the system control, cross-connect, and timing board at the local end.

If... Then...






----End

Related Information

None.

A.3.143 TU_LOP

Description

The TU_LOP is an alarm indicating that the TU pointer is lost. This alarm is reported if a boarddetects that the TU-PTR value is an invalid pointer or NDF reversion in eight consecutive frames.

Attribute



Parameters

None.


The service in the TU path that reports the alarm is interrupted. If the service is configured withprotection, the protection switching is also triggered.



A-193

Possible Causesl Cause 1: The system control, cross-connect, and timing board is faulty.

l Cause 2: The tributary board is faulty.

Procedure

Step 1 Cause 1: The system control, cross-connect, and timing board is faulty.(1) Replace the system control, cross-connect, and timing board at the local end.

If... Then...




Go to Cause 2.

Step 2 Cause 2: The tributary board is faulty.(1) Replace the board where the tributary unit resides.

----End


A.3.144 UP_E1_AIS

DescriptionThe UP_E1_AIS is an alarm indication of the 2 Mbit/s uplink signal. This alarm is reportedwhen the tributary board detects that the 2 Mbit/s uplink signal is all 1s.

Attribute



ParametersNone.

Impact on the SystemE1 signals are unavailable.

Possible Causesl Cause 1: The opposite equipment transmits the AIS signal.

l Cause 2: The receive unit of the tributary board on the local equipment is faulty.




Issue 05 (2010-07-30)

Procedure

Step 1 Cause 1: The opposite equipment transmits the AIS signal.(1) Check whether the opposite equipment transmits the AIS signal.

If... Then...

The opposite equipment transmits theAIS signal

Rectify the fault on the opposite equipment.

The opposite equipment does nottransmit the AIS signal

Go to Cause 2.

Step 2 Cause 2: The receive unit of the tributary board on the local equipment is faulty.(1) Replace the alarmed board.

----End


A.3.145 VOLT_LOS

DescriptionThe VOLT_LOS is an alarm indicating that the power voltage is unavailable.

Attribute



ParametersNone.

Impact on the SystemThe ODU that is connected to the IF board that reports this alarm fails to work.

Possible Causesl Cause 1: The output power is abnormal.

l Cause 2: The input power is abnormal.

l Cause 3: Lightning occurs.

Procedure

Step 1 Cause 1: The output power is abnormal.



A-195

(1) Check the power switch of the ODU.

If... Then...

The power switch is turned off Turn on the power switch.

The power switch is turned on Go to the next step.

(2) Use the multimeter to check the IF fiber jumper, IF cable, or ODU section by section for

a short circuit.

If... Then...

A short circuit exists Replace the short-circuited component,and then replace the IF board thatreports the alarm.

No short circuits exist Replace the IF board that reports thealarm.

CAUTIONIf the alarm is reported due to a short circuit, replace the short-circuited cable or ODU, andthen replace the IF board. Otherwise, the new IF board may be damaged again.

Step 2 Cause 2: The input power is abnormal.(1) Replace the IF board that reports the alarm.

Step 3 Cause 3: Lightning occurs.(1) Contact the engineers for power supply to check the grounding lightning facilities.

----End

Related Information

None.

A.3.146 WRG_BD_TYPE

Description

The WRG_BD_TYPE is an alarm indicating that the type of the board is incorrect.

Attribute






Issue 05 (2010-07-30)

Parameters

None.


The board fails to work.


l Cause 2: The board of an incorrect type is installed.

Procedure

Step 1 Cause 1: Configuration data is incorrect.(1) See Configuring the Logical Board to check whether the board type complies with the

planning requirement.

If... Then...

The board type does not meet the planningrequirement

Change the configuration data.

The board type meets the planning requirement Go to Cause 2.

Step 2 Cause 2: The board of an incorrect type is installed.(1) Replace the board of an incorrect type.

----End

Related Information

None.

A.3.147 WRG_DEV_TYPE

Description

The WRG_DEV_TYPE is an alarm indicating that the type of the equipment is incorrect.

Attribute



Parameters

None.



A-197

Impact on the SystemThe equipment fails to work.

Possible CausesCause 1: Configuration data is incorrect.

Procedure

Step 1 Cause 1: Configuration data is incorrect.(1) By using the method of creating an NE, change the type of the NE so that it is consistent

with the equipment type.

----End


A.3.148 XPIC_LOS

DescriptionThe XPIC_LOS is an alarm indicating that the XPIC compensation signals are lost.

Attribute



ParametersNone.

Impact on the SystemBit errors may occur in the service at the port, and the service may even be interrupted.


l Cause 2: The radio link is faulty.

l Cause 3: The XPIC cable is faulty.

l Cause 4: The IF board or ODU is faulty.

Procedure

Step 1 Cause 1: Configuration data is incorrect.




Issue 05 (2010-07-30)

(1) Check whether the XPIC function needs to be enabled. If not, see Setting IF Attributes todisable the XPIC function, and then perform a self-loop at the XPIC port on the board byusing the XPIC cable.

Step 2 Cause 2: The radio link is faulty.

(1) Check whether the paired board that is connected to the IFX2 board through the XPIC cablereports the MW_LOF alarm. If yes, first clear the MW_LOF alarm.

Step 3 Cause 3: The XPIC cable is faulty.

(1) Check the connection of the XPIC cable.

If... Then...

The cable is improperly connected Connect the XPIC cable properly.

The cable is properly connected Go to the next step.

(2) Test the make and break of the XPIC cable by using the multimeter. If the XPIC cable isdamaged, replace it.

Step 4 Cause 4: The IF board or ODU is faulty.

Locate the fault by replacing the IF board or ODU.

(1) Replace the paired board of the IFX2 board.

The paired board of the IFX2 board refers to the other IFX2 board connected to the IFX2board that reports the alarm through the XPIC cable.

If... Then...





(2) Replace the ODU that is connected to the paired IFX2 board.

If... Then...

The alarm is cleared after the ODU isreplaced


The alarm persists after the ODU isreplaced

Replace the IFX2 board that reports thealarm.

----End

Related Information

None.



A-199

B Abnormal Event Reference

Abnormal events are important indicators when abnormalities occur on the equipment. Thistopic describes all the possible important abnormal events on the OptiX RTN 950 and how tohandle these events.

B.1 Major Abnormal Performance Event ListAbnormal events are important indicators when abnormalities occur on the equipment. Thistopic describes all the possible important abnormal events on the OptiX RTN 950 and how tohandle these events.

B.2 Abnormal Performance Events and Handling ProceduresThis topic describes all the important abnormal performance events on the OptiX RTN 950 inan alphabetical order and how to handle these abnormal performance events.

OptiX RTN 950Maintenance Guide (U2000) B Abnormal Event Reference


B-1

B.1 Major Abnormal Performance Event ListAbnormal events are important indicators when abnormalities occur on the equipment. Thistopic describes all the possible important abnormal events on the OptiX RTN 950 and how tohandle these events.

Table B-1 Major performance event list

Event Name Source

B.2.1 Intermediate Frequency 1+1Protection Switching

CST and CSH

B.2.2 N+1 Protection Switching

B.2.3 SNCP Switching

B.2.4 Linear MS Switching

B.2.5 System Control Board Switching CST and CSH

B.2.6 RMON Performance Value Belowthe Lower Limit

EM6F and EM6T

B.2.7 RMON Performance Value Abovethe Upper Limit

B.2 Abnormal Performance Events and HandlingProcedures

This topic describes all the important abnormal performance events on the OptiX RTN 950 inan alphabetical order and how to handle these abnormal performance events.

B.2.1 Intermediate Frequency 1+1 Protection Switching




B.2.5 System Control Board Switching

B.2.6 RMON Performance Value Below the Lower Limit

B.2.7 RMON Performance Value Above the Upper Limit

B.2.1 Intermediate Frequency 1+1 Protection Switching

DescriptionThis abnormal event indicates that the 1+1 HSB/FD/SD switching occurs on the equipment.

B Abnormal Event ReferenceOptiX RTN 950


B-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 05 (2010-07-30)

AttributeSeverity Type

Major Service

ParametersName Meaning

Protection Group ID Indicates the ID of the protection group wherethe IF 1+1 protection switching occurs.

Current Working Board Slot Indicates the slot ID of the current workingboard.

Current Working Board Sub Slot Indicates the slot ID of the current workingboard.The value is always 0xff.

Current Working Port No. Indicates the ID of the working port.

Current Active Board Indicates the current working board.l Active on Working Board

l Active on Protection Board

Active Board Status Indicates the current state of the workingboard.l Normal

l Failed

l MW_RDI

Standby Board Status Indicates the current status of the protectionboard.l Normal

l Failed

l MW_RDI

Switching Request Indicates the type of an IF 1+1 protectionswitching request.l No Request

l Automatic Switching

l Manual Switching

l Forced Switching

l Lockout of Switching

l Wait-to-Restore

l RDI Switching



B-3

NOTEThe parameter names and parameter values may vary with the version of the NMS.

Impact on Systeml During the HSB protection switching, services are interrupted. After the HSB switching is

complete, the services are restored to normal.

l During the HSM protection switching, no bit errors occur and the services are not affected.

Related Alarms

When the IF 1+1 protection switching occurs, the RPS_INDI alarm is reported.

Possible Causesl The possible causes of the HSB protection switching are as follows:

– The hardware of the ODU or IF unit at the local end is faulty.

– The working channel of the local end receives the MW_RDI alarm.

– The external switching, which is triggered by the switching command issued from theNMS software, occurs. The external switching includes lockout of switching, forcedswitching, and manual switching.

l The possible causes of the HSM protection switching are as follows:

– In the case of Hybrid radio, the quality of the main channel degrades.

– In the case of SDH/PDH radio, an alarm that triggers the HSM switching is reported onthe radio link. These alarms include R_LOC, R_LOF, R_LOS, MW_LOF,MW_FEC_UNCOR, B1_SD, and B2_SD.

Procedure

Step 1 Rectify the fault according to the switching request type indicated by the parameter and thedescription in RPS_INDI.

----End


Description

This abnormal event indicates that the N+1 protection switching occurs on the equipment.

Attribute

Severity Type

Major Service




Issue 05 (2010-07-30)


Protection Group ID Indicates the ID of the protection group wherethe IF N+1 protection switching occurs.

Path Name ID Indicates the ID of the path where the IF N+1protection switching occurs.

Switching Request Indicates the type of an IF N+1 protectionswitching request.l Lockout of Protection Channel

l Forced Switching

l SF Switching

l SD Switching

l Manual Switching

l Wait-to-Restore

l Exercise

l Reverse Request

l No Request

Switching Status Indicates the state of an N+1 protectiongroup.l Protocol Unstarted

l Idle Status

l Switching Status

l Protocol Starting

Protected Unit Indicates the ID of the protected channel.The ID is 0xff if no switching is performed.

Switching Local/Remote End Indication Indicates the local or remote switching.l Local End

l Remote End

The switching status reason is changed Indicates the cause of the IF N+1 protectionswitching.l Local Request

l External Command

l K-byte request

l Timer expiry




B-5

Impact on SystemDuring the N+1 protection switching (not more than 50 ms), the services are interrupted. Afterthe N+1 switching is complete, the services are restored to normal. After the switching startsand before the switching is complete, the extra services are interrupted.

NOTEIf the IF N+1 protection switching is caused by exercise switching, service signals are not switched actuallybecause the exercise switching is used to check whether the NE can run the N+1 protocol normally.

Related Alarms

When the IF N+1 protection switching occurs, the NP1_SW_INDI alarm is reported.

Possible Causesl The external switching occurs.

– Lockout of protection channel

– Forced switching

– Manual switching

l The automatic switching occurs.

– The hardware of the IDU or IF board is faulty. Focus on checking whether theHARD_BAD or BD_STATUS alarm is reported.

– The MW_LOF, R_LOC, R_LOF, R_LOS, MS_AIS, or B2_EXC alarm is reportedon the working path.

Procedure

Step 1 Rectify the fault according to the switching request type and the switching cause indicated bythe parameters.

If... Then...

The switching is caused by the externalswitching

Find the cause of the external switching, andthen release the external switchingimmediately.

The switching is caused by the automaticswitching

Clear the alarm that triggers the automaticswitching.

----End


Description

This abnormal event indicates that the SDH SNCP switching occurs in the service that isconfigured with the SNCP.




Issue 05 (2010-07-30)


Major Service


Source Indicates the service source of the SNCPprotection group.

Sink Indicates the service sink of the SNCPprotection group.

Status Indicates the current working path.l Working at protection channel

l Working at working channel

Switching Status Indicates the switching status.l Manual to Standby

l Force to Active

l Force to Standby

l Lockout Switching

l SF Switching

l SD Switching

l Wait-to-Restore

l Idle

Working Channel Current Status Indicates the current status of the SNCPworking path.l Normal

l SD

l SF

Protection Channel Current Status Indicates the current status of the SNCPprotection path.l Normal

l SD

l SF




B-7

Impact on SystemWhen the SNCP switching occurs, you must find the cause. If the related link is faulty, recoverthe link immediately. Ensure that the states of the SNCP working path and the SNCP protectionpath are NORMAL.

Possible Causesl The SDH SNCP switching is automatically triggered.

– The hardware of the line board is faulty.

– The R_LOS, R_LOF, R_LOC, MS_AIS, B2_EXC, AU_LOP, AU_AIS,HP_LOM, MW_LOF (only when the IF board functions as the line board),MW_LIM (only when the IF board functions as the line board), B3_EXC, B3_SD,HP_TIM (in the case of VC-4 services), HP_UNEQ (in the case of VC-4 services),TU_AIS (in the case of VC-12 services) or TU_LOP (in the case of VC-12 services),LP_UNEQ (Optional condition), LP_TIM (Optional condition), BIP_SD (Optionalcondition), BIP_EXC (Optional condition), or MW_BER_EXC (E1 servicestransmitted over the Hybrid microwave) alarm is reported.

l The SDH SNCP switching is manually triggered.– Forced switching

– Manual switching

ProcedureStep 1 On the NMS, query the type of the SDH SNCP switching request.

Step 2 Rectify the fault according to the switching request type.

If... Then...

The SDH SNCP switching is automaticallytriggered

Rectify the fault according to the relatedalarm, and eliminate the conditions of theautomatic switching.

The SDH SNCP switching is manuallytriggered

Find the cause of the manual switching, andthen release the manual switchingimmediately.

----End


DescriptionThis abnormal event indicates that linear MSP switching occurs on the equipment that isconfigured with services.


Major Service




Issue 05 (2010-07-30)


Protection Group ID Indicates the ID of the protection group wherelinear MSP switching occurs.

Current Working Path Indicates the current working path of thelinear MS.l Working path

l Protection path

Linear MSP Switching Request Indicates the type of a linear MSP switchingrequest.l Lock out protection channel

l Forced Switching

l Switch upon signal failure

l Switch upon signal degradation

l Manual Switching

l Wait-To-Restore

l Exercise

l Reverse Request

l Non-Revertive Request

l Not Requested

Switching Status Indicates the switching state.l Protocol Not Started

l Idle

l Switching

l Protocol Being Started

Switching Remote/Local End Indication Indicates the remote or local end.l No Remote/Local End

l Local End

l Remote End

The switching status reason is changed Indicates the cause of changing the switchingstate.l Local Request

l External Command

l K Byte Request

l Timer Timeout



B-9

Impact on the Systeml During the MSP switching (not more than 50 ms), the services are interrupted. After the

MSP switching is complete, the services become normal. During the MSP switching,additional services are interrupted.

l When linear MSP switching occurs, fiber cut may occur or the terminal node may be invalid.You must rectify the fault immediately.

Related AlarmsWhen linear MSP switching occurs, the APS_INDI alarm may be reported.

Possible Causesl An external switching command such as manual, forced, or excise switching command is

issued.l Automatic switching occurs.

After the R_LOS, R_LOF, MS_AIS, B2_EXC, B2_SD, B3_EXC, B3_SD, HP_TIM (forVC-4 services), HP_UNEQ (for VC-4 services), TU_AIS (for VC-12 services), orTU_LOP (for VC-12 services) alarm is reported, the MSP group changes to the switchingstate, and the automatic switching alarm is reported.

l The hardware or line is faulty.

Procedure

Step 1 Query the switching type and the protection group ID on the NMS.

Step 2 Rectify the fault according to the switching request type.

If... Then...

The switching is caused by externalswitching

Find the cause of the external switching, andthen clear manual switching as soon aspossible.

The switching is caused by automaticswitching

Clear the related alarm, and rectify thehardware or line fault.

----End

B.2.5 System Control Board Switching

DescriptionThis abnormal event indicates that the system control boards are external switched when theworking system control board on the equipment that is configured with the 1+1 protectionbecomes faulty.


Major Equipment




Issue 05 (2010-07-30)


Group ID Indicates the group ID.

Protection Type XC board protection.

Working Unit Indicates the slot ID of the current workingboard.

Protection Unit Indicates the slot ID of the current protectionboard.

Current Working Unit Indicates the current status of the board.l Work at protection unit

l Work at working unit

Switching Type Indicates the switching type.External Switching


Impact on SystemNone.

Possible Causesl The switching is manually triggered.

Procedure

Step 1 On the NMS, check whether the manual switching operation is performed.

If... Then...

The manual switching operation isperformed on the NMS

Find the cause of the manual switching, andthen release the manual switching immediately.

No manual switching operations areperformed on the NMS


----End



B-11

B.2.6 RMON Performance Value Below the Lower Limit

DescriptionThis abnormal event indicates that the current RMON performance value is lower than the presetlower limit.


Minor Communication


Performance ID Indicates the ID of the current RMONperformance event.

Current Performance Value Indicates the value of the current RMONperformance event.

Lower Limit Indicates the lower limit of the currentRMON performance event.

Impact on SystemDifferent abnormal performance events have different impacts on the system. For details, seeD.3 RMON Events and Handling Procedures.

Related AlarmsDifferent alarms are reported when different RMON performance values are lower than thelower limits. For details, see D.3 RMON Events and Handling Procedures.

Possible CausesThe lower limit of a performance event is set to a non-zero value.

Procedure

Step 1 Set the lower limit of the performance event to 0.

----End




Issue 05 (2010-07-30)

B.2.7 RMON Performance Value Above the Upper Limit

Description

This abnormal event indicates that the current RMON performance value is higher than the presetupper limit.

Attribute

Severity Type

Minor Communication

Parameters

Name Meaning

Performance ID Indicates the ID of the current RMONperformance event.

Current Performance Value Indicates the value of the current RMONperformance event.

Upper Limit Indicates the upper limit of the currentRMON performance event.

Impact on SystemDifferent abnormal performance events have different impacts on the system. For details, seeD.3 RMON Events and Handling Procedures.

Related Alarms

Different alarms are reported when different RMON performance values are higher than theupper limits. For details, see D.3 RMON Events and Handling Procedures.

Possible Causes

When the performance values of different abnormal RMON performance events are higher thanthe upper limits, the causes are different. For details, see D.3 RMON Events and HandlingProcedures.

Procedure

Step 1 See D.3 RMON Events and Handling Procedures to handle different abnormal performanceevents.

----End



B-13

C Performance Event Reference

Performance events are important indicators when the equipment performance changes. Thistopic describes all the possible performance events on the OptiX RTN 950 and how to handlethese performance events.

C.1 Performance Events (by Event Type)The list is categorized based on the performance event type, and includes all the events of theOptiX RTN 950.

C.2 Performance Events (by Logical Board)This part lists all the performance events that are reported by each board.

C.3 Performance Events and Handling ProceduresBased on the type of a performance event, this topic describes all the performance events on theOptiX RTN 950 and how to handle these performance events.

OptiX RTN 950Maintenance Guide (U2000) C Performance Event Reference


C-1

C.1 Performance Events (by Event Type)The list is categorized based on the performance event type, and includes all the events of theOptiX RTN 950.

C.1.1 SDH/PDH Performance EventsSDH performance events are classified into five types: pointer justification, regenerator sectionerror, multiplex section error, higher order path error, and lower order path error.

C.1.2 Radio Performance EventsThe radio performance events are performance events of the radio link bit errors, ATPC, AM,and power.

C.1.3 Other Performance EventsIn addition to the SDH and radio performance events, the OptiX RTN 950 supports performanceevents of the optical power and the temperature.

C.1.1 SDH/PDH Performance EventsSDH performance events are classified into five types: pointer justification, regenerator sectionerror, multiplex section error, higher order path error, and lower order path error.

Table C-1 Pointer justification performance events

Event Name Description

AUPJCHIGH Count of positive AU pointer justification

AUPJCLOW Count of negative AU pointer justification

AUPJCNEW Count of new AU pointer justifications

TUPJCHIGH Count of positive TU pointer justifications

TUPJCLOW Count of negative TU pointer justifications

TUPJCNEW Count of new TU pointer justifications

Table C-2 Regenerator section error performance events


RSBBE Regenerator section block of backgrounderror

RSES Regenerator section errored second

RSSES Regenerator section severely errored second

RSUAS Regenerator section unavailable second

RSCSES Regenerator section consecutive severelyerrored second

C Performance Event ReferenceOptiX RTN 950


C-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 05 (2010-07-30)


RSOFS Regenerator section out-of-frame second

RSOOF Regenerator section out of frame

NOTE

The regenerator section error performance events also occur in the case of the PDH radio. The PDH radioframe is detected through the overheads that are used for frame location and bit error detection.

Table C-3 Multiplex section error performance events


MSBBE Multiplex section block of background error

MSES Multiplex section errored second

MSSES Multiplex section severely errored second

MSCSES Multiplex section consecutive severelyerrored second

MSUAS Multiplex section unavailable second

MSFEBBE Multiplex section far end block ofbackground error

MSFEES Multiplex section far end errored second

MSFESES Multiplex section far end severely erroredsecond

MSFECSES Multiplex section far end consecutiveseverely errored second

MSFEUAS Multiplex section far end unavailable second

Table C-4 Higher order path error performance events


HPBBE Higher order path background block error

HPES Higher order path errored second

HPSES Higher order path severely errored second

HPCSES Higher order path consecutive severelyerrored second

HPUAS Higher order path unavailable second



C-3


HPFEBBE Higher order path far end background blockerror

HPFEES Higher order path far end errored second

HPFESES Higher order path far end severely erroredsecond

HPFECSES Higher order path far end consecutiveseverely errored second

HPFEUAS Higher order path far end unavailable second

Table C-5 Lower order path error performance events


LPBBE Lower order path block of background error

LPES Lower order path errored second

LPSES Lower order path severely errored second

LPCSES Lower order path continuous severe bit errorsecond

LPUAS Lower order path unavailable second

LPFEBBE Lower order path far end block of backgrounderror

LPFEES Lower order path far end errored second

LPFESES Lower order path far end severely erroredsecond

LPFECSES Lower order path far end consecutiveseverely errored second

LPFEUAS Lower order far end unavailable second

C.1.2 Radio Performance EventsThe radio performance events are performance events of the radio link bit errors, ATPC, AM,and power.

Table C-6 Radio power performance events


TSL_MAX Maximum value of radio transmit signal level




Issue 05 (2010-07-30)


TSL_MIN Minimum value of radio transmit signal level

TSL_CUR Current value of radio transmit signal level

TSL_AVG Average value of radio transmit signal level

RSL_MAX Maximum value of radio receive signal level

RSL_MIN Minimum value of radio receive signal level

RSL_CUR Current value of radio receive signal level

RSL_AVG Average value of radio receive signal level

TLHTT The duration when the ODU at the local endhas a transit power higher than the upperthreshold

TLLTT The duration when the ODU at the local endhas a transit power higher than the lowerthreshold

RLHTT The duration when the ODU at the local endhas a receive power lower than the upperthreshold

RLLTT The duration when the ODU at the local endhas a receive power lower than the lowerthreshold

Table C-7 FEC performance events


FEC_BEF_COR_ER FEC bit error rate before correction

FEC_UNCOR_BLOCK_CNT FEC uncorrected block count

FEC_COR_BYTE_CNT The number of bytes that are correctedthrough the FEC

Table C-8 Radio link error performance events


IF_BBE Radio link background block errors

IF_ES Radio link errored seconds

IF_SES Radio link severely errored seconds

IF_UAS Radio link unavailable second



C-5


IF_CSES Radio link consecutive severely erroredseconds

Table C-9 ATPC performance events


ATPC_P_ADJUST Positive ATPC adjustment

ATPC_N_ADJUST Negative ATPC adjustment

Table C-10 AM performance events


QPSKWS Working time of the QPSK mode

QAMWS16 Working time of the 16QAM mode





AMDOWNCNT Count of the downshift of the AM scheme

AMUPCNT Count of the upshift of the AM scheme

C.1.3 Other Performance EventsIn addition to the SDH and radio performance events, the OptiX RTN 950 supports performanceevents of the optical power and the temperature.

Table C-11 Optical power performance events

Event Name Description Source

TPLMAX Maximum value of transmitoptical power

SL1D

TPLMIN Minimum value of transmitoptical power

TPLCUR Current value of transmitoptical power




Issue 05 (2010-07-30)


RPLMAX Maximum value of receiveoptical power

RPLMIN Minimum value of receiveoptical power

RPLCUR Current value of receiveoptical power

Table C-12 Board temperature performance events


BDTEMPMAX Maximum value of boardtemperature

ODU, IF1, IFU2, IFX2, CST,and CSH

BDTEMPMIN Minimum value of boardtemperature

BDTEMPCUR Current value of boardtemperature

C.2 Performance Events (by Logical Board)This part lists all the performance events that are reported by each board.

C.2.1 CST/CSHThe CST/CSH board reports only the board temperature performance events.

C.2.2 IF1The IF1 board reports three types of performance events: SDH/PDH performance events,microwave performance events, and temperature performance events.

C.2.3 IFU2The IFU2 board reports three types of performance events: PDH performance events, radioperformance events, and board temperature performance events.

C.2.4 IFX2The IFX2 board reports three types of performance events: PDH performance events, radioperformance events, and board temperature performance events.

C.2.5 SL1DThe SL1D board reports three types of performance events: SDH performance events, opticalpower performance events, and board temperature performance events.

C.2.6 SP3S/SP3DThe SP3S/SP3D board reports only the PDH performance events.

C.2.7 ODUThe ODU reports radio performance events.



C-7

C.2.1 CST/CSHThe CST/CSH board reports only the board temperature performance events.



BDTEMPMAX Maximum value of board temperature

BDTEMPMIN Minimum value of board temperature

BDTEMPCUR Current value of board temperature

C.2.2 IF1The IF1 board reports three types of performance events: SDH/PDH performance events,microwave performance events, and temperature performance events.

SDH/PDH Performance Events


















Issue 05 (2010-07-30)

NOTE

The regenerator section error performance events also occur in the case of the PDH radio. The PDH radioframe is detected through the overheads that are used for frame location and bit error detection.

























C-9




Radio Performance Events




FEC_UNCOR_BLOCK_CNT Frame count uncorrect by FEC

Other Performance Events






C.2.3 IFU2The IFU2 board reports three types of performance events: PDH performance events, radioperformance events, and board temperature performance events.

PDH Performance Events










Issue 05 (2010-07-30)



























C-11













C.2.4 IFX2The IFX2 board reports three types of performance events: PDH performance events, radioperformance events, and board temperature performance events.

PDH Performance Events













Issue 05 (2010-07-30)



























C-13










C.2.5 SL1DThe SL1D board reports three types of performance events: SDH performance events, opticalpower performance events, and board temperature performance events.

SDH Performance Events















Issue 05 (2010-07-30)



























C-15







Table C-34 Optical power performance events


TPLMAX Maximum value of transmit optical power

TPLMIN Minimum value of transmit optical power

TPLCUR Current value of transmit optical power

RPLMAX Maximum value of receive optical power

RPLMIN Minimum value of receive optical power

RPLCUR Current value of receive optical power






C.2.6 SP3S/SP3DThe SP3S/SP3D board reports only the PDH performance events.



TUPJCHIGH Count of positive TU pointer justifications




Issue 05 (2010-07-30)


TUPJCLOW Count of negative TU pointer justifications

TUPJCNEW Count of new TU pointer justifications













C.2.7 ODUThe ODU reports radio performance events.

Table C-38 Radio power performance events


TSL_MAX Maximum value of radio transmit signal level

TSL_MIN Minimum value of radio transmit signal level

TSL_CUR Current value of radio transmit signal level

TSL_AVG Average value of radio transmit signal level

RSL_MAX Maximum value of radio receive signal level

RSL_MIN Minimum value of radio receive signal level



C-17


RSL_CUR Current value of radio receive signal level

RSL_AVG Average value of radio receive signal level

TLHTT The duration when the ODU at the local endhas a transit power higher than the upperthreshold

TLLTT The duration when the ODU at the local endhas a transit power higher than the lowerthreshold

RLHTT The duration when the ODU at the local endhas a receive power lower than the upperthreshold

RLLTT The duration when the ODU at the local endhas a receive power lower than the lowerthreshold

Table C-39 ATPC performance events


ATPC_P_ADJUST Positive ATPC adjustment

ATPC_N_ADJUST Negative ATPC adjustment

C.3 Performance Events and Handling ProceduresBased on the type of a performance event, this topic describes all the performance events on theOptiX RTN 950 and how to handle these performance events.

C.3.1 AMDOWNCNT and AMUPCNT

Descriptionl AMDOWNCNT indicates the count of the AM downshifts on a board in the current

performance statistics period.l AMUPCNT indicates the count of the AM upshifts on a board in the current performance

statistics period.

Attribute

Attribute Description

Performance event cell AMDOWNCNT and AMUPCNT




Issue 05 (2010-07-30)


Unit -

Impact on System

AMDOWNCNT and AMUPCNT indicate only statistical values and do not affect the system.

Related Alarms

AM_DOWNSHIFT

Possible Causes

When the AM function is enabled, the transmission modulation scheme that the IF port on theIF board uses varies according to the quality of the link. Accordingly, the system counts theperformance events of the modulation scheme shift. When the low-efficiency modulationscheme is shifted to the high-efficiency modulation scheme, an upshift is recorded and oneAMUPCNT event is counted. Similarly, when the high-efficiency modulation scheme is shiftedto the low-efficiency modulation scheme, a downshift is recorded and one AMDOWNCNTevent is counted.

C.3.2 ATPC_P_ADJUST and ATPC_N_ADJUST

Descriptionl ATPC_P_ADJUST indicates the positive ATPC adjustment event.

This performance event indicates that the quality of a communication link declines. Thus,you must increase the transmit power of the ODU to maintain the communication quality.

l ATPC_N_ADJUST indicates the negative ATPC adjustment event.This performance event indicates that the quality of a communication link becomes wellor the transmit power of the ODU is very large. Thus, you can decrease the transmit powerof the ODU.

Attribute


Performance event cell ATPCPADJUST (ATPC_P_ADJUST) andATPCNADJUST (ATPC_N_ADJUST)

Unit -


The ATPC adjustment indicates only the stability of a communication link and it does not affectservices. When the value of the performance event is larger, more adjustments are made.



C-19

When the factors that affect a communication link, such as sudden change of the weather, donot exist, and when the ATPC adjustment count is very large, the communication link may befaulty. You must check the communication link to prevent it from failure.

Related AlarmsNone.

C.3.3 AUPJCHIGH, AUPJCLOW, and AUPJCNEW

Descriptionl AUPJCHIGH indicates the count of positive AU pointer justifications.

l AUPJCLOW indicates the count of negative AU pointer justifications.

l AUPJCNEW indicates the count of new AU pointer justifications.

AttributeAttribute Description

Performance event cell PPJE (AUPJCHIGH)NPJE (AUPJCLOW)NDF (AUPJCNEW)

Unit Block

Impact on SystemLess than six AUPJCHIGH and AUPJCLOW events do not affect the system. If the pointer isjustified for many times, or the AUPJCNEW event occurs, bit errors may occur in the service.

Related AlarmsWhen the AUPJCHIGH, AUPJCLOW, or AUPJCNEW performance event crosses the presetthreshold, the MSAD_CROSSTR alarm is reported.

Performance Event Default 15-MinuteThreshold

Default 24-HourThreshold

AUPJCHIGH 1500 30000

AUPJCLOW 1500 30000

AUPJCNEW 1500 30000

Possible CausesThe NE clock is out-of-synchronization.




Issue 05 (2010-07-30)

Procedure

Step 1 See 5.5 Troubleshooting Pointer Justifications for handling.

----End

C.3.4 BDTEMPMAX, BDTEMPMIN, and BDTEMPCUR

Descriptionl BDTEMPMAX indicates the maximum temperature of a board.

l BDTEMPMIN indicates the minimum temperature of a board.

l BDTEMPCUR indicates the current temperature of a board.

Attribute


Performance event cell -

Unit 0.1°C

Impact on SystemIf the temperature of a board is very high or very low, the performance of the board declines,and bit errors or other faults occur.

Related Alarms

If the temperature of a board crosses the specific threshold, the TEMP_ALARM alarm isreported.

C.3.5 FEC_BEF_COR_ER, FEC_UNCOR_BLOCK_CNT andFEC_COR_BYTE_CNT

Descriptionl FEC_BEF_COR_ER indicates the BER before the FEC is performed.

This event indicates the impact of the external environment on the transmission.

l FEC_COR_BYTE_CNT indicates the number of bytes corrected through the FEC.

This event indicates the impact of the FEC.

l FEC_UNCOR_BLOCK_CNT indicates the number of frames that cannot be correctedthrough the FEC.

This event indicates the number of blocks that cannot be corrected through the FEC.



C-21

Attribute


Performance event cell FECBEFCORER (FEC_BEF_COR_ER)FECCORBYTECNT(FEC_COR_BYTE_CNT)FECUNCORBLOCKCNT(FEC_UNCOR_BLOCK_CNT)

Unit None (FEC_BEF_COR_ER)None (FEC_COR_BYTE_CNT)Block (FEC_UNCOR_BLOCK_CNT)

Impact on System

If the value of FEC_BEF_COR_ER is very high, residual bit errors exist in the service after theFEC is performed.

If the value of FEC_UNCOR_BLOCK_CNT is not zero, it can be inferred that bit errors thatcannot be corrected exist on a radio link. Bit errors exist in the service accordingly.

Related Alarms

If a byte cannot be corrected, the MW_FEC_UNCOR alarm is reported.

C.3.6 HPBBE, HPES, HPSES, HPCSES, and HPUAS

Descriptionl HPBBE indicates the higher order path background block error.

BBE refers to the errored blocks excluding the errored blocks in the unavailable andseverely errored seconds.

l HPES indicates the higher order path errored second.

ES refers to a second in which one or more errored blocks are detected.

l HPSES indicates the higher order path severely errored second.

SES refers to a second in which 30% or more than 30% errored blocks exist or at least oneSDP exists. SDP is the period in which the BER of all the consecutive blocks in a periodof less than four consecutive blocks or 1 ms (the longer period is applied) is equal to orhigher than 10-2 or the signal is lost.

l HPCSES indicates the higher order path consecutive severely errored second.

CSES refers to a second in which the SES occurs continuously for less than 10 seconds.

l HPUAS indicates the higher order path unavailable second.

The unavailable time begins at the onset of 10 consecutive SESs, with the 10 SESs included.When SESs disappear for 10 consecutive seconds, the available time begins from theeleventh second, with the previous 10 seconds included.




Issue 05 (2010-07-30)


Performance event cell B3CNT

Unit Block (HPBBE)Second (HPES, HPSES, HPCSES, andHPUAS)

Impact on SystemExcessive bit errors interrupt the service (the BER should be less than 10-3 for the voice service,and 10-6 for the data service).

Related Alarms

When the HPBBE, HPES, HPSES, HPCSES, or HPUAS performance event crosses the presetthreshold, the HP_CROSSTR alarm is reported.



HPBBE 1500 15000

HPES 50 100

HPSES 20 50

HPUAS 20 50

HPCSES 4 (number of consecutive SESs)

Possible Causes

The system detects higher order path bit errors through the B3 byte.

Procedure

Step 1 See 5.4 Troubleshooting Bit Errors in TDM Services for handling.

----End

C.3.7 HPFEBBE, HPFEES, HPFESES, HPFECSES, and HPFEUAS

Descriptionl HPFEBBE indicates the higher order path far end background block error.

Far end background block error (FEBBE) indicates that the BBE occurs at the oppositeend.



C-23

l HPFEES indicates the higher order path far end errored second.FEES indicates that the ES occurs at the opposite end.

l HPFESES indicates the higher order path far end severely errored second.FESES indicates that the SES occurs at the opposite end.

l HPFECSES indicates the higher order path far end consecutive severely errored second.FECSES indicates that the CSES occurs at the opposite end.

l HPFEUAS indicates the higher order path far end unavailable second.FEUAS indicates that the UAS occurs at the opposite end.


Performance event cell PFEBE

Unit Block (HPFEBBE)Second (HPFEES, HPFESES, HPFECSES,and HPFEUAS)


Related Alarms

The HP_REI alarm is reported at the local end.

Possible Causes

The system detects the higher order path far end bit errors through bits 1 to 4 in the G1 byte.

Procedure

Step 1 Clear the corresponding performance event at the opposite end.

----End

C.3.8 IF_BBE, IF_ES, IF_SES, IF_CSES, and IF_UAS

Descriptionl IF_BBE indicates the radio link background block error.


l IF_ES indicates the radio link errored second.ES refers to a second in which one or more errored blocks are detected.




Issue 05 (2010-07-30)

l IF_SES indicates the radio link severely errored second.SES refers to a second in which 30% or more than 30% errored blocks exist or at least oneSDP exists. SDP is the period in which the BER of all the consecutive blocks in a periodof less than four consecutive blocks or 1 ms (the longer period is applied) is equal to orhigher than 10-2 or the signal is lost.

l IF_CSES indicates the radio link consecutively severely errored second.CSES refers to a second in which the SES occurs continuously for less than 10 seconds.

l IF_UAS indicates the radio link unavailable second.The unavailable time begins at the onset of 10 consecutive SESs, with the 10 SESs included.When SESs disappear for 10 consecutive seconds, the available time begins from theeleventh second, with the previous 10 seconds included.


Performance event cell IFCNT

Unit Block (IFBBE)Second (IFES, IFSES, IFCSES, and IFUAS)

Impact on System

Excessive bit errors interrupt the service (the BER should be less than 10-3 for the voice service,and 10-6 for the data service).

Related AlarmsIn the case of the IFU2 or IFX2 board, the MW_BER_SD or MW_BER_EXC alarm is reportedwhen the BER crosses the specific threshold.

Possible CausesThe system detects bit errors on the radio link through the bit error detection overheads in a radioframe.

Procedure


----End

C.3.9 LPBBE, LPES, LPSES, LPCSES, and LPUAS

Descriptionl LPBBE indicates the lower order path background block error.




C-25

l LPES indicates the lower order path errored second.


l LPSES indicates the lower order path severely errored second.


l LPCSES indicates the lower order path consecutive severely errored second.


l LPUAS indicates the lower order path unavailable second.


Attribute


Performance event cell LPBIP2CNT

Unit Block (LPBBE)Second (LPES, LPSES, LPCSES, andLPUAS)

Impact on System


Related Alarms

When the LPBBE, LPES, LPSES, LPCSES, or LPUAS performance event crosses the presetthreshold, the LP_CROSSTR alarm is reported.



LPBBE 1500 15000

LPES 50 100

LPSES 20 50

LPUAS 20 50

LPCSES 4 (number of consecutive SESs)




Issue 05 (2010-07-30)

Possible CausesThe system detects lower order path bit errors through the BIP2 in the V5 byte (E1 interfaceboard or Hybrid IF board).

Procedure


----End

C.3.10 LPFEBBE, LPFEES, LPFESES, LPFECSES, and LPFEUAS

Descriptionl LPFEBBE indicates the lower order path far end background block error.

FEBBE indicates that the BBE occurs at the opposite end.l LPFEES indicates the lower order path far end errored second.

FEES indicates that the ES occurs at the opposite end.l LPFESES indicates the lower order path far end severely errored second.

FESES indicates that the SES occurs at the opposite end.l LPFECSES indicates the lower order path far end consecutive severely errored second.

FECSES indicates that the CSES occurs at the opposite end.l LPFEUAS indicates the lower order path far end unavailable second.

FEUAS indicates that the UAS occurs at the opposite end.


Performance event cell LPFEBE

Unit Block (LPFEBBE)Second (LPFEES, LPFESES, LPFECSES,and LPFEUAS)


Related AlarmsThe LP_REI alarm is reported at the local end.

Possible CausesThe system detects the lower order path far end bit errors through bit 3 in the V5 byte.



C-27

Procedure


----End

C.3.11 MSBBE, MSES, MSSES, MSCSES, and MSUAS

Descriptionl MSBBE indicates the multiplex section background block error.


l MSES indicates the multiplex section errored second.


l MSSES indicates the multiplex section severely errored second.


l MSCSES indicates the multiplex section consecutive severely errored second.


l MSUAS indicates the multiplex section unavailable second.


Attribute



Unit Block (MSBBE)Second (MSES, MSSES, MSCSES, andMSUAS)

Impact on System


Related Alarms

When the MSBBE, MSES, MSSES, MSCSES, or MSUAS performance event crosses the presetthreshold, the MS_CROSSTR alarm is reported.




Issue 05 (2010-07-30)



MSBBE 1500 15000

MSES 50 100

MSES 20 50

MSUAS 20 50

MSCSES 4 (number of consecutive SESs)

Possible CausesThe system detects multiplex section bit errors through the B2 byte.

Procedure


----End

C.3.12 MSFEBBE, MSFEES, MSFESES, MSFECSES, and MSFEUAS

Descriptionl MSFEBBE indicates the multiplex section far end background block error.

Far end background block error (FEBBE) indicates that the BBE occurs at the oppositeend.

l MSFEES indicates the multiplex section far end errored second.Far end errored second (FEES) indicates that the ES occurs at the opposite end.

l MSFESES indicates the multiplex section far end severely errored second.Far end severely errored second (FESES) indicates that the SES occurs at the opposite end.

l MSFECSES indicates the multiplex section far end consecutive severely errored second.Far end consecutive severely errored second (FECSES) indicates that the CSES occurs atthe opposite end.

l MSFEUAS indicates the multiplex section far end unavailable second.Far end unavailable second (FEUAS) indicates that the UAS occurs at the opposite end.


Performance event cell LFEBE

Unit Block (MSFEBBE)Second (MSFEES, MSFESES, MSFECSES,and MSFEUAS)



C-29



Related Alarms

The MS_REI alarm is reported at the local end.

Possible Causes

The system detects multiplex section far end bit errors through the M1 byte.

Procedure


----End

C.3.13 QPSKWS, QAMWS16, QAMWS32, QAMWS64,QAMWS128, and QAMWS256

Descriptionl QPSKWS indicates the working duration of the QPSK modulation scheme.

l QAMWS16 indicates the working duration of the 16QAM modulation scheme.





Attribute


Performance event cell QPSKWSSECOND (QPSKWS)QAMWS16SECOND (16QAMWS)QAMWS32SECOND (32QAMWS)QAMWS64SECOND (64QAMWS)QAMWS128SECOND (128QAMWS)QAMWS256SECOND (256QAMWS)

Unit Second




Issue 05 (2010-07-30)

Impact on SystemWhen the AM function is disabled, the performance event does not affect the system.

When the AM function is enabled, in normal cases, the seconds of the modulation scheme formaximum capacity should account for a larger percentage. In the duration set for good weather,if the seconds of the low-efficiency modulation scheme account for a larger percentage, theperformance of the radio link is abnormal.

Related AlarmsNone.

C.3.14 RPLMAX, RPLMIN, and RPLCUR

Descriptionl RPLMAX indicates the maximum receive optical power at an optical interface.

l RPLMAX indicates the minimum receive optical power at an optical interface.

l RPLCUR indicates the current receive optical power at an optical interface.


Performance event cell IPM

Unit dBm

Impact on SystemIn normal cases, the receive optical power should be 3 dB higher than the receiver sensitivity,and 5 dB lower than the overload power.

If the receive optical power is very low or very high, bit errors occur and even services areinterrupted.

Related Alarmsl If the receive optical power is lower than the receiver sensitivity, the IN_PWR_LOW

alarm is reported.l If the receive optical power is higher than the overload power, the IN_PWR_HIGH alarm

is reported.

C.3.15 RSBBE, RSES, RSSES, RSCSES, and RSUAS

Descriptionl RSBBE indicates the regenerator section background block error.

Background block error (BBE) refers to the errored blocks excluding the errored blocks inthe unavailable and severely errored seconds.



C-31

l RSES indicates the regenerator section errored second.Errored second (ES) refers to a second in which one or more errored blocks are detected.

l RSSES indicates the regenerator section severely errored second.Severely errored second (SES) refers to a second in which 30% or more than 30% erroredblocks exist or at least one severely disturbed period (SDP) exists. SDP is the period inwhich the BER of all the consecutive blocks in a period of less than four consecutive blocksor 1 ms (the longer period is applied) is equal to or higher than 10-2 or the signal is lost.

l RSCSES indicates the regenerator section consecutive severely errored second.Consecutive severely errored second (CSES) refers to a second in which the SES occurscontinuously for less than 10 seconds.

l RSUAS indicates the regenerator section unavailable second.The unavailable time begins at the onset of 10 consecutive SESs, with the 10 SESs included.When SESs disappear for 10 consecutive seconds, the available time begins from theeleventh second, with the previous 10 seconds included.

NOTE

When the IF board works in PDH mode, these performance events may also be reported. These events aredetected through the self-defined overhead byte B1 in the PDH radio frame.

Attribute



Unit Block (RSBBE)Second (RSES, RSSES, RSCSES, andRSUAS)

Impact on System


Related Alarms

When the RSBBE, RSES, RSSES, RSCSES, or RSUAS performance event crosses the presetthreshold, the RS_CROSSTR alarm is reported.



RSBBE 1500 15000

RSES 50 100

RSSES 20 50

RSUAS 20 50




Issue 05 (2010-07-30)



RSCSES 4 (number of consecutive SESs)

Possible Causes

The system detects the regenerator section bit errors through the B1 byte.

Procedure


----End

C.3.16 RSL_MAX, RSL_MIN, RSL_CUR, and RSL_AVG

Descriptionl RSL_MAX indicates the maximum radio received signal level.

l RSL_MIN indicates the minimum radio received signal level.

l RSL_CUR indicates the current radio received signal level.

l RSL_AVG indicates the average radio received signal level.

Attribute


Performance event cell RSL

Unit 0.1 dBm

Impact on SystemWhen the radio received signal level is very low or very high, bit errors occur and even servicesare interrupted.

Related Alarms

If the radio received signal level crosses the specific threshold, the RADIO_RSL_HIGH orRADIO_RSL_LOW alarm is reported.

C.3.17 RSOOF and RSOFS

Descriptionl RSOOF indicates the regenerator section out of frame.



C-33

The out-of-frame (OOF) block refers to a data block in which incorrect A1 and A2 bytesare detected.

l RSOFS indicates the regenerator section out-of-frame second.The out-of-frame second (OFS) refers to a second in which one or more OOF blocks aredetected.

Attribute


Performance event cell OOF

Unit Block (RSOOF)Second (RSOFS)

Impact on System

The system discards OOF data blocks. Thus, an RSOOF event is equivalent to a big error (if oneRSOOF exists in a second, the BER is not less than 1.25 x 10-5).

Related Alarms

If RSOOF is received in five consecutive frames, the equipment changes to the OOF state. Ifthe OOF state lasts for 3 ms, the R_LOF alarm is reported and all the services are interrupted.

Possible Causes

The system detects incorrect A1 and A2 bytes.

Procedure

Step 1 If the R_LOF alarm, as well as the performance event, is reported, eliminate the errors accordingto the alarm. Otherwise, see 5.4 Troubleshooting Bit Errors in TDM Services for handling.

----End

C.3.18 RLHTT, RLLTT, TLHTT, TLLTT

Descriptionl The RLHTT indicates the duration when the ODU at the local end has a receive power

lower than the upper threshold.l The RLLTT indicates the duration when the ODU at the local end has a receive power

lower than the lower threshold.l The TLHTT indicates the duration when the ODU at the local end has a transit power higher

than the upper threshold.l The TLLTT indicates the duration when the ODU at the local end has a transit power higher

than the lower threshold.




Issue 05 (2010-07-30)

Attribute


Basic unit of a performance event RLHTS, RLLTS, TLHTS, and TLLTS

Unit Second

Impact on System

None.

Related Alarms

None.

C.3.19 TPLMAX, TPLMIN, and TPLCUR

Descriptionl TPLMAX indicates the maximum transmit optical power at an optical interface.

l TPLMIN indicates the minimum transmit optical power at an optical interface.

l TPLCUR indicates the current transmit optical power at an optical interface.

Attribute


Performance event cell OPM

Unit 0.1 dBm

Impact on System

In normal cases, the receive optical power should be 3 dB higher than the receiver sensitivity,and 5 dB lower than the overload power.

If the transmit optical power is very low or very high, the receive optical power at the oppositesite is accordingly very low or very high. As a result, bit errors occur and even services areinterrupted.

Related Alarmsl If the transmit optical power at the opposite site is lower than the receiver sensitivity, the

IN_PWR_LOW alarm is reported.

l If the receive optical power at the opposite site is higher than the overload power, theIN_PWR_HIGH alarm is reported.



C-35

C.3.20 TSL_MAX, TSL_MIN, TSL_CUR, and TSL_AVG

Descriptionl TSL_MAX indicates the maximum radio transmitted signal level.

l TSL_MIN indicates the minimum radio transmitted signal level.

l TSL_CUR indicates the current radio transmitted signal level.

l TSL_AVG indicates the average radio transmitted signal level.

Attribute


Performance event cell TSL

Unit 0.1 dBm

Impact on System

When the radio transmitted signal level is very low or very high, the radio received signal levelat the opposite site is very low or very high. As a result, bit errors occur and even services areinterrupted.

Related Alarms

If the radio transmitted signal level is not within the range supported by the ODU, theRADIO_TSL_HIGH or RADIO_TSL_LOW alarm is reported.

C.3.21 TUPJCHIGH, TUPJCLOW, and TUPJCNEW

Descriptionl TUPJCHIGH indicates the count of positive TU pointer justifications.

l TUPJCLOW indicates the count of negative TU pointer justifications.

l TUPJCNEW indicates the count of new TU pointer justifications.

Attribute


Performance event cell TUPPJE (TUPJCHIGH)TUNPJE (TUPJCLOW)TUNDF (TUPJCNEW)

Unit Block




Issue 05 (2010-07-30)

Impact on SystemLess than six TUPJCHIGH and TUPJCLOW events on each port do not affect the system. If thepointer is justified for many times, or the TUPJCNEW event even occurs, bit errors may occurin the service.

Related AlarmsWhen the TUPJCHIGH, TUPJCLOW, or TUPJCNEW performance event crosses the presetthreshold, the HPAD_CROSSTR alarm is reported.



TUPJCHIGH 1500 30000

TUPJCLOW 1500 30000

TUPJCNEW 1500 30000

Possible CausesThe NE clock is out-of-synchronization.

Procedure

Step 1 See 5.5 Troubleshooting Pointer Justifications for handling.

----End



C-37

D RMON Event Reference

RMON events reflect the running of the Ethernet services. This topic describes the possibleRMON events on the OptiX RTN 950 and how to handle these events.

OptiX RTN 950Maintenance Guide (U2000) D RMON Event Reference


D-1

D.1 List of RMON Alarm EntriesThe RMON alarm entries refer to the table entries in the RMON alarm group.

Table D-1 List of RMON alarm entries

Alarm Name Description Source

ETHDROP The number of packet loss eventscrosses the threshold.

EM6T, EM6F, IFU2, and IFX2

ETHEXCCOL

The number of frames that fail to betransmitted after continuouscollisions crosses the threshold.

ETHLATECOL

The number of collisions that aredetected after a timeslot periodelapses crosses the threshold.

RXBBAD The number of received bad packetscrosses the threshold.

TXDEFFRM The number of frames whosetransmission is delayed crosses thethreshold.

ETHUNDER The number of received undersizedpackets crosses the threshold.

ETHOVER The number of received oversizedpackets crosses the threshold.

ETHFRG The number of received fragmentedpackets crosses the threshold.

ETHJAB The number of received erroredoversized packets crosses thethreshold.

ETHCOL The number of received collisionscrosses the threshold.

ETHFCS The number of frames that have FCScheck errors crosses the threshold.

D.2 List of RMON Performance EntriesThe RMON performance entries refer to the table entries in the RMON statistics group or historygroup.

D RMON Event ReferenceOptiX RTN 950


D-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 05 (2010-07-30)

Table D-2 List of RMON performance entries

Category ofPerformanceEntries

Abbreviation Name of aPerformance Entry

Source

Basicperformance

RXPKTS Packets received(packets)

EM6T, EM6F, IFU2, andIFX2

ETHDROP Drop events (times)

RXOCTETS Bytes received (bytes)

RXMULCAST Multicast packetsreceived (packets)

RXBRDCAST Broadcast packetsreceived (packets)

ETHOVER Oversized packetsreceived (packets)

EM6T, EM6F

ETHJAB Jabbers received(packets)

ETHUNDER Undersized packetsreceived (packets)

EM6T, and EM6F

ETHFRG Fragments received(packets)

ETHCOL Collisions (times)

Extendedperformance

ETHFCS FCS errored frames(frames)

EM6T, EM6F, IFU2, andIFX2

RXBGOOD Good bytes received(bytes)

TXBGOOD Good bytes transmitted(bytes)

RXBBAD Bad bytes received(bytes)

TXUNICAST Unicast packetstransmitted (packets)

RXUNICAST Unicast packets received(packets)

TXMULCAST Multicast packetstransmitted (packets)



D-3

Category ofPerformanceEntries

Abbreviation Name of aPerformance Entry

Source

TXBRDCAST Broadcast packetstransmitted (packets)

RXGOODFULLFRAMESPEED

Rate of good full-framebytes received (bytes/second)

TXGOODFULLFRAMESPEED

Rate of good full-framebytes transmitted (bytes/second)

RXFULLBGOOD Good full-frame bytesreceived (bytes)

TXFULLBGOOD Good full-frame bytestransmitted (bytes)

RXPAUSE Pause frames received(frames)

EM6T, EM6F

TXPAUSE Pause frames transmitted(frames)

ETHLATECOL Late collisions (times) EM6T, and EM6F

ETHEXCCOL Frames unsuccessfullytransmitted aftersuccessive collisions(frames)

TXDEFFRM Delayed frames (frames)

D.3 RMON Events and Handling ProceduresThis topic describes the RMON events that indicate Ethernet service abnormalities and how tohandle these events.

D.3.1 ETHCOL

Description

ETHCOL indicates the number of detected packet collisions. An RMON threshold-crossingevent is reported when the number of collisions is higher than the upper threshold or lower thanthe lower threshold.




Issue 05 (2010-07-30)

Impact on System

The opposite equipment fails to normally receive services.

Possible Causes

Generally, this event is caused when the local port is connected to a large number of devicesthat work in half-duplex mode.

Procedure

Step 1 Handle this alarm according to the specific performance event.

If... Then...

The number is lower than the lower threshold Change the lower threshold to 0.

The number is higher than the upper threshold Go to the next step.

Step 2 On the NMS, query the working modes of the ports on the equipment at both ends.

If... Then...

The ports on the equipment at both endswork in inconsistent modes, or any portworks in half-duplex mode

Set the working modes of the ports on theequipment at both ends to full-duplex or auto-negotiation, so that these ports work inconsistent modes.

The ports on the equipment at both endswork in consistent modes and no ports workin half-duplex mode


Step 3 Replace the involved part.

----End

Reference

None.

D.3.2 ETHDROP

Description

ETHDROP indicates the number of events in which packet loss occurs due to resourcedeficiency. An RMON threshold-crossing event is reported when the number of packet lossevents is higher than the upper threshold or lower than the lower threshold.

Impact on System

When packet loss occurs frequently, services are affected and the system is affected seriously.Hence, you must rectify the fault immediately.



D-5

Possible CausesThis performance event indicates packet loss due to the full MAC buffer, FIFO overflow, orbackward pressure.

l The lower threshold is not set to a non-zero value.

l The hardware at the local end is faulty.

Procedure


If... Then...

The number is lower than the lowerthreshold

Change the lower threshold to 0.

The number is higher than the upperthreshold

Manually decrease the traffic transmitted fromthe opposite end. If the problem persists, go tothe next step.


----End

ReferenceNone.

D.3.3 ETHEXCCOL

DescriptionETHEXCCOL indicates the number of frames that fail to be transmitted due to continuous portcollisions. An RMON threshold-crossing event is reported when the number of frames that failto be transmitted is higher than the upper threshold or lower than the lower threshold. Generally,the value indicates that 16 port collisions occur continuously when the same frame is transmitted.

Impact on SystemThe opposite equipment fails to normally receive services.

Possible CausesGenerally, this event is caused when the local port is connected to a large number of devicesthat work in half-duplex mode.

Procedure


If... Then...





Issue 05 (2010-07-30)

If... Then...



If... Then...






----End

ReferenceNone.

D.3.4 ETHFCS

DescriptionETHFCS indicates the number of received Ethernet data frames with FCS check errors at thelocal end (excluding the oversized and undersized frames). An RMON threshold-crossing eventis reported when the number is higher than the upper threshold or lower than the lower threshold.

Impact on SystemMost ports discard the packets with FCS check errors. The system services are interrupted inthe worst case.

Possible Causes1. The local port and opposite port work in inconsistent modes. For example, one port works

in half-duplex mode, and the opposite port works in half-duplex mode.2. The transmission line is of the poor quality and bit errors exist.3. The hardware at the local end is faulty.

Procedure

Step 1 Thus, handle the alarm according to the specific performance event.

If... Then...





D-7


If... Then...

The ports on the equipment at both endswork in inconsistent modes

Change the working modes of the ports on theequipment at both ends so that they can workin consistent modes

The ports on the equipment at both endswork in consistent modes



----End

Reference

None.

D.3.5 ETHFRG

Description

ETHFRG indicates that an RMON threshold-crossing event is reported when the number ofreceived packets that are shorter than 64 bytes and have FCS or alignment errors exceeds thepreset upper threshold.

Impact on System

Data transmission is delayed or packet loss occurs.

Possible Causesl The working modes of the ports on the equipment at both ends are not consistent.


l The ports on the equipment at both ends work in half-duplex mode, and the data traffic isvery heavy.

Procedure

Step 1 Check whether the working modes of the ports on the equipment at both ends are consistent.

If... Then...

The working modes are consistent Go to the next step.

The working modes are not consistent Change the working mode of the local port so thatthe ports on the equipment at both ends work inconsistent modes.

Step 2 Check whether the working modes of the ports on the equipment at both ends are set to the half-duplex mode.




Issue 05 (2010-07-30)

If... Then...

The working modes are not set to the half-duplex mode


The working modes are set to the half-duplex mode

Change the working modes of the ports on theequipment at both ends to the full-duplex modeor adaptive mode.


----End

D.3.6 ETHJAB

Description

ETHJAB indicates that an RMON threshold-crossing alarm is reported when the number ofreceived packets that are longer than 1518 bytes and have FCS or alignment errors is higher thanthe upper threshold.


Data transmission is delayed or packet loss occurs.

Possible Causesl The working modes of the ports on the equipment at both ends are not consistent.


Procedure

Step 1 Check whether the working modes of the ports on the equipment at both ends are consistent.

If... Then...

The working modes are consistent Go to the next step.

The working modes are not consistent Change the working mode of the local port so thatthe ports on the equipment at both ends work inconsistent modes.


----End

D.3.7 ETHLATECOL

Description

ETHLATECOL indicates the number of collisions detected within a timeslot period after apacket is transmitted. An RMON threshold-crossing event is reported when the number ofcollisions is higher than the upper threshold or lower than the lower threshold.



D-9

Impact on System

The opposite equipment fails to normally receive services.

Possible Causes

Generally, this performance event is caused by a large network diameter.

Procedure


If... Then...




If... Then...





Step 3 Check whether the network diameter of the LAN is very large according to the networkingplanning information.

If... Then...

The network diameter is very large Divide the network and deploy equipment todifferent buses or physically shared devices (such ashubs).NOTE

In the case of the 10 Mbit/s port rate, the maximum Ethernetdiameter is 2000 m. In the case of the 100 Mbit/s port rate,the maximum Ethernet diameter is 200 m.

The network diameter is appropriate Go to the next step.


----End

Reference

None.




Issue 05 (2010-07-30)

D.3.8 ETHOVER

Description

ETHOVER indicates that an RMON threshold-crossing event is reported when the number ofpackets that are longer than 1518 bytes and are received at a port crosses the preset threshold.

Impact on System

If the length of the data frame received at a port is more than the preset maximum frame length,the data frame is discarded and thus the system services are affected.

Possible Causes1. The preset maximum frame length is less than the length of the frame that is received at a

port.

2. The hardware at the local end is faulty.

Procedure

Step 1 Check whether the opposite equipment transmits the packet that is longer than the maximumframe length set for the local equipment.

Option Description

If... Then...

The opposite equipment transmits thepacket that is longer than the maximumframe length set for the local equipment

Notify the opposite equipment that the lengthof transmitted frames should be changed.

The opposite equipment does not transmitthe packet that is longer than themaximum frame length set for the localequipment



----End

Reference

None.

D.3.9 ETHUNDER

Description

ETHUNDER indicates that an RMON threshold-crossing event is reported when the number ofpackets that are shorter than 64 bytes and are received on the line side crosses the preset threshold.



D-11

Impact on SystemThe data frames whose length is not within the specific range are discarded. As a result, thesystem services are affected.

Possible Causes1. The length of a data frame that is received at a port is shorter than 64 bytes.2. The hardware at the local end is faulty.

Procedure

Step 1 Check whether the opposite equipment transmits the packet that is shorter than 64 bytes.

If... Then...

The opposite equipment transmits the packetthat is shorter than 64 bytes

Rectify the fault on the opposite equipment.

The opposite end does not transmit thepacket that is shorter than 64 bytes



----End

ReferenceNone.

D.3.10 RXBBAD

DescriptionRXBBAD indicates the total number of bytes in received bad packets, excluding the framingbit but including the FCS byte. An RMON threshold-crossing event is reported when the totalnumber of bytes in received bad packets is higher than the upper threshold or lower than thelower threshold.

Impact on SystemA port discards bad packets. This may even interrupt system services.

Possible Causes1. Errors occur when the opposite end transmits packets.2. The transmission line is of the poor quality and bit errors exist.3. The hardware at the local end is faulty.

Procedure





Issue 05 (2010-07-30)

If... Then...



Step 2 Correct the errors that occur when the opposite end transmits packets.See 8.14 Monitoring Ethernet Packets Through Port Mirroring to check the Ethernet packetsreceived at the local end. If bit errors exist, rectify the fault at the opposite end.

Step 3 Handle the problem of poor quality of the transmission line.Check whether the ETH_LOS alarm is reported at the local end because the external line isdamaged or over attenuated. If yes, see the related handling method to clear the alarm.


----End

Reference

None.

D.3.11 TXDEFFRM

Description

TXDEFFRM indicates the number of frames the first transmission of which is delayed due tothe congestion on the transmission media, excluding the number of frames the first transmissionof which is delayed due to collisions. An RMON threshold-crossing event is reported when thenumber of frames that fail to be transmitted is higher than the upper threshold and lower thanthe lower threshold.

Impact on System

The rate of frame transmission decreases, and thus packets are congested at a port and thethroughput of the port decreases.

Possible Causes

Generally, this event is caused when the external port at the local end is connected to a largenumber of devices that work in half-duplex mode.

Procedure


If... Then...






D-13

If... Then...






----End

ReferenceNone.




Issue 05 (2010-07-30)

E Alarm Management

The alarm management on the OptiX RTN 950 is classified into the NE alarm management andboard alarm management.

E.1 NE Alarm ManagementThe NE alarm management function set by user is applicable to all the boards on the NE.

E.2 Board Alarm ManagementThe board alarm management function is only applicable to the board on which users haveconfigured this function.

OptiX RTN 950Maintenance Guide (U2000) E Alarm Management


E-1

E.1 NE Alarm ManagementThe NE alarm management function set by user is applicable to all the boards on the NE.

The equipment supports the following NE alarm management functions:

l Settings of the alarm storage mode

l Setting of the alarm delay

l Setting of the alarm reversion mode

For details about these functions, see the manuals or online Help of the NMS.

E.2 Board Alarm ManagementThe board alarm management function is only applicable to the board on which users haveconfigured this function.

E.2.1 Setting the Alarm LevelAlarms are classified into four levels: critical, major, minor, and warning, according to theirseverities. The maintenance personnel can change the alarm level by using the NMS.

E.2.2 Alarm SuppressionThe maintenance personnel can change the alarm monitoring attribute by setting the alarmsuppression function. A board detects only the alarms that are not suppressed. The alarmsuppression function helps users to ignore their unconcerned alarms.

E.2.3 Alarm Auto-ReportIf Alarm Auto-Report is set to Reported, all the detected alarms are reported to the NMS in atimely manner. If Alarm Auto-Report is set to Not Report, the alarms are reported only whenalarm query is performed on the NMS. The maintenance personnel can change the setting onthe NMS.

E.2.4 Alarm ReversionIn the case of a port that is not configured with services, certain alarms may be reported. To filterthe alarms that users are not concerned, set these alarms to be reversed. In this manner, the alarmstatus at this port is the opposite to the actual case. That is, the status is displayed as normalwhen an alarm is actually reported.

E.2.5 Setting of the Bit Error Alarm ThresholdWhen the number of bit errors detected by a board exceeds a specified number, the boardgenerates a bit error alarm. This specific number is the bit error alarm threshold, and the settingof this threshold is supported by all the bit error threshold-crossing and degrading alarms on theNE.

E.2.6 AIS InsertionAIS insertion can be set for certain alarms reported on a board. When the board detects thealarms, it inserts all 1s into the lower level service to indicate the remote end that the service isunavailable.

E.2.7 UNEQ InsertionWhen a board detects that the service path is not in use or that the LOS alarm exists, it insertsall 0s into the service signal to notify the remote end that this signal is unavailable.

E Alarm ManagementOptiX RTN 950


E-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 05 (2010-07-30)

E.2.1 Setting the Alarm LevelAlarms are classified into four levels: critical, major, minor, and warning, according to theirseverities. The maintenance personnel can change the alarm level by using the NMS.

This function is supported by all the boards.

E.2.2 Alarm SuppressionThe maintenance personnel can change the alarm monitoring attribute by setting the alarmsuppression function. A board detects only the alarms that are not suppressed. The alarmsuppression function helps users to ignore their unconcerned alarms.


E.2.3 Alarm Auto-ReportIf Alarm Auto-Report is set to Reported, all the detected alarms are reported to the NMS in atimely manner. If Alarm Auto-Report is set to Not Report, the alarms are reported only whenalarm query is performed on the NMS. The maintenance personnel can change the setting onthe NMS.


E.2.4 Alarm ReversionIn the case of a port that is not configured with services, certain alarms may be reported. To filterthe alarms that users are not concerned, set these alarms to be reversed. In this manner, the alarmstatus at this port is the opposite to the actual case. That is, the status is displayed as normalwhen an alarm is actually reported.

The alarm reversion function is available in three modes, namely, non-revertive, automaticreversion, and manual reversion.

l Non-revertiveIn this mode, the alarms are monitored by default and alarm reversion cannot be enabledfor a port.

l Auto reversionIn this mode, alarm reversion can be enabled for a port where alarms are reported. Afteralarm reversion is enabled at a port, alarms are not reported. When the current alarm iscleared, the alarm reversion automatically changes to the disabled status. That is, it changesto the non-revertive mode. Then, the alarm reporting status at the port is the same as theactual status.

l Manual reversionIn this mode, alarm reversion can be enabled for a port regardless of whether any alarmsare reported at the port. After alarm reversion is enabled, the alarm reporting status at theport is the same as the actual status. After alarm reversion is manually disabled, the alarmreversion status changes to the non-revertive mode. Then, the alarm reporting status at theport is the same as the actual status.

Pay attention to the following points when you set the alarm reversion function:

l Alarm reversion does not change the actual status of alarms on the board, as well as theindication status of the alarm indicators.



E-3

l Alarm reversion is realized on the NE software. The alarm data is the same on the NE andthe NMS, which indicates the status after the alarm reversion. If you directly query thealarm data of a board, however, the actual alarm status is returned.

l Alarm reversion is set based on ports. It is supported by each port on the SL1D, SP3S,SP3D, IFX2, IFU2, EM6T, and EM6Fboards.

E.2.5 Setting of the Bit Error Alarm ThresholdWhen the number of bit errors detected by a board exceeds a specified number, the boardgenerates a bit error alarm. This specific number is the bit error alarm threshold, and the settingof this threshold is supported by all the bit error threshold-crossing and degrading alarms on theNE.

Table E-1 Setting of the bit error alarm threshold

Alarm Name Default Alarm Threshold Applicable Board

B1_EXC 10-3 SL1D and IF1

B1_SD 10-6


B2_SD 10-6


B3_SD 10-6

BIP_EXC 10-3 SP3S, SP3D, IFU2, and IFX2

BIP_SD 10-6

MW_BER_EXC 10-3 IFU2 and IFX2

MW_BER_SD 10-6

E.2.6 AIS InsertionAIS insertion can be set for certain alarms reported on a board. When the board detects thealarms, it inserts all 1s into the lower level service to indicate the remote end that the service isunavailable.

Table E-2 Setting of the AIS insertion

Trigger Condition Default Value Applicable Board

B1_EXC Enabled SL1D and IF1

B2_SD Disabled SL1D and IF1

B2_EXC Disabled SL1D and IF1

E Alarm ManagementOptiX RTN 950


E-4 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 05 (2010-07-30)


HP_LOM Enabled

HP_TIM Disabled

HP_SLM Disabled

HP_UNEQ Disabled

B3_EXC Enabled SL1D and IF1

B3_SD Disabled

B1_SD Disabled SL1D and IF1

LP_TIM Disabled SP3S and SP3D

LP_UNEQ Disabled

LP_SLM Disabled

T_ALOS Enabled

BIP_EXC Disabled

BIP_SD Disabled

MW_BER_EXC Enabled IFX2 and IFU2

MW_BER_SD Disabled

NOTE

l When the SL1D board detects the R_LOS, R_LOF, MS_AIS, AU_AIS, or AU_LOP alarm, it forciblyinserts the AIS.

l When the IF1 board detects the MW_LOF, MW_LIM, R_LOF, MS_AIS, AU_AIS, or AU_LOPalarm, it forcibly inserts the AIS.

l When the IFX2 and IFU2 board detect the MW_LOF, MW_LIM, or R_LOF alarm, it forcibly insertsthe AIS.

E.2.7 UNEQ InsertionWhen a board detects that the service path is not in use or that the LOS alarm exists, it insertsall 0s into the service signal to notify the remote end that this signal is unavailable.

Table E-3 Setting of the UNEQ insertion


T_ALOS Disabled SP3S and SP3D

Service path being not in use Disabled



E-5

F Performance Event Management

The performance event management is classified into the NE performance event managementand board performance event management.

F.1 NE Performance Event ManagementThe NE performance event management function set by user is applicable to all the boards onthe NE.

F.2 Board Performance Event ManagementThe performance event management function is only applicable to the board on which usershave configured this function.

OptiX RTN 950Maintenance Guide (U2000) F Performance Event Management


F-1

F.1 NE Performance Event ManagementThe NE performance event management function set by user is applicable to all the boards onthe NE.

The OptiX RTN 950 supports the following NE performance event management functions:

l Setting NE performance event monitoring

l Setting the start/end time of performance events

l Enabling/Disabling the reporting of UAT events

For details about these functions, see the manuals or online Help of the NMS.

F.2 Board Performance Event ManagementThe performance event management function is only applicable to the board on which usershave configured this function.

Table F-1 Board performance event management function

Function Applicable Board

Setting 15-minute/24-hour performancemonitoring

SL1D, SP3S, SP3D, CSH, CST, ODU, IFX2, IFU2, and IF1

Setting 15-minute/24-hour performance eventauto-reporting

SL1D, SP3S, SP3D, CSH, CST, ODU, IFX2, IFU2, and IF1

Setting performancethresholds

SL1D, SP3S, SP3D, IFX2, IFU2, and IF1

Resetting theperformance register

SL1D, SP3S, SP3D, ODU, IFX2, IFU2, and IF1

Generating performancethreshold-crossingalarms

SL1D, SP3S, SP3D, ODU, IFX2, IFU2, and IF1

Monitoring UAT events SL1D, SP3S, SP3D, IFX2, IFU2, and IF1

Monitoring CSESperformance events

SL1D, SP3S, SP3D, IFX2, IFU2, and IF1

F Performance Event ManagementOptiX RTN 950


F-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 05 (2010-07-30)

G Alarm Suppression Relationship

When the alarm suppression function is disabled on an NE, the root alarm and certain correlatedalarms are reported if a fault occurs on this NE. After the alarm suppression function is enabled,the reporting of the correlated alarms is suppressed according to the relationship between alarmswhen the root alarm is reported. The alarm suppression relationship can be classified into thesuppression relationship between intra-board alarms and suppression relationship between inter-board alarms.

Table G-1 Suppression relationship between intra-board alarms

Alarm Identifier Identifier of the Suppressed Alarm

MW_LOF R_LOS, R_LOF, R_LOC,MW_FEC_UNCOR, MW_RDI,MW_LIM, MS_AIS, B1_EXC, B1_SD,MS_RDI, B2_EXC, B2_SD, MS_REI,AU_AIS, AU_LOP, B3_EXC, B3_SD,HP_TIM, HP_UNEQ, HP_SLM,HP_RDI, HP_LOM, HP_REI,MW_BER_EXC, and MW_BER_SD

R_LOS or R_LOC R_LOF, J0_MM, B1_EXC, B1_SD,MS_AIS, MS_RDI, B2_EXC, B2_SD,MS_REI, AU_AIS, AU_LOP, HP_TIM,HP_UNEQ, HP_SLM, HP_RDI, B3_EXC,B3_SD, HP_LOM, HP_REI,IN_PWR_LOW, MW_RDI, andMW_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, andMW_LIM

OptiX RTN 950Maintenance Guide (U2000) G Alarm Suppression Relationship


G-1


MS_AIS B2_SD, MS_REI, MS_RDI, AU_AIS,AU_LOP, HP_TIM, HP_UNEQ,HP_SLM, HP_RDI, B3_EXC, B3_SD,HP_LOM, and HP_REI, B2_EXC

MS_RDI MS_REI

AU_AIS or AU_LOP B3_EXC, B3_SD, HP_TIM, HP_SLM,HP_UNEQ, HP_RDI, HP_LOM, andHP_REI

HP_UNEQ HP_TIM, HP_LOM, and HP_RDI

HP_RDI HP_REI

LP_UNEQ LP_TIM, LP_RDI, LP_RFI, LP_REI,BIP_SD, and BIP_EXC

B1_EXC B1_SD

B2_EXC B2_SD

B3_EXC B3_SD

TU_AIS LP_TIM, LP_SIZE_ERR, LP_UNEQ,LP_RDI, LP_REI, LP_RFI, LP_R_FIFO,BIP_EXC, BIP_SD, LP_SLM, TU_LOP,DOWN_E1_AIS

TU_LOP LP_TIM, LP_SIZE_ERR, LP_UNEQ,LP_RDI, LP_REI, LP_RFI, LP_R_FIFO,BIP_EXC, BIP_SD, LP_SLM,DOWN_E1_AIS

T_ALOS E1_LOS and UP_E1_AIS

E1_LOS UP_E1_AIS

BIP_EXC BIP_SD

LSR_NO_FITED ETH_LOS, LASER_MOD_ERR, andLASER_CLOSED

LASER_MOD_ERR LASER_CLOSED

Table G-2 Suppression relationship between intra-board alarms


R_LOS, R_LOC, MS_AIS, AU_AIS, orAU_LOP

TU_AIS

MW_LOF or MW_LIM TU_AIS

G Alarm Suppression RelationshipOptiX RTN 950


G-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 05 (2010-07-30)

H Glossary

Terms are listed in an alphabetical order.

H.1 0-9This section provides the terms starting with numbers.

H.2 A-EThis section provides the terms starting with letters A to E.

H.3 F-JThis section provides the terms starting with letters F to J.

H.4 K-OThis section provides the terms starting with letters K to O.

H.5 P-TThis section provides the terms starting with letters P to T.

H.6 U-ZThis section provides the terms starting with letters U to Z.

OptiX RTN 950Maintenance Guide (U2000) H Glossary


H-1

H.1 0-9This section provides the terms starting with numbers.

1+1 protection An architecture that has one normal traffic signal, one working SNC/trail, one protectionSNC/trail and a permanent bridge. At the source end, the normal traffic signal ispermanently bridged to both the working and protection SNC/trail. At the sink end, thenormal traffic signal is selected from the better of the two SNCs/trails. Due to thepermanent bridging, the 1+1 architecture does not allow an extra unprotected trafficsignal to be provided.

1U The standard electronics industries association (EIA) rack unit (44 mm/1.75 in.)

802.1Q in 802.1Q 802.1Q in 802.1Q (QinQ) is a VLAN feature that allows the equipment to add a VLANtag to a tagged frame.The implementation of QinQ is to add a public VLAN tag to aframe with a private VLAN tag, making the frame encapsulated with two layers of VLANtags. The frame is forwarded over the service provider's backbone network based on thepublic VLAN tag. By this, a layer 2 VPN tunnel is provided to customers.The QinQfeature enables the transmission of the private VLANs to the peer end transparently.

H.2 A-EThis section provides the terms starting with letters A to E.

A

ACAP See adjacent channel alternate polarization

adaptive modulation A technology that is used to automatically adjust the modulation mode according to thechannel quality. When the channel quality is favorable, the equipment adopts a high-efficiency modulation mode to improve the transmission efficiency and the spectrumutilization of the system. When the channel quality is degraded, the equipment adoptsthe low-efficiency modulation mode to improve the anti-interference capability of thelink that carries high-priority services.

ADC See Analog to Digital Converter

add/drop multiplexer Add/Drop Multiplexing. Network elements that provide access to all or some subset ofthe constituent signals contained within an STM-N signal. The constituent signals areadded to (inserted), and/or dropped from (extracted) the STM-N signal as it passedthrough the ADM.

Address ResolutionProtocol

Address Resolution Protocol (ARP) is an Internet Protocol used to map IP addresses toMAC addresses. It allows hosts and routers to determine the link layer addresses throughARP requests and ARP responses. The address resolution is a process in which the hostconverts the target IP address into a target MAC address before transmitting a frame.The basic function of the ARP is to query the MAC address of the target equipmentthrough its IP address.

adjacent channelalternate polarization

A channel configuration method, which uses two adjacent channels (a horizontalpolarization wave and a vertical polarization wave) to transmit two signals.

ADM See add/drop multiplexer

H GlossaryOptiX RTN 950


H-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 05 (2010-07-30)

Administrative Unit The information structure which provides adaptation between the higher order path layerand the multiplex section layer. It consists of an information payload (the higher orderVC) and an AU pointer which indicates the offset of the payload frame start relative tothe multiplex section frame start.

AGC See Automatic Gain Control

AM See adaptive modulation

Analog to DigitalConverter

An electronic circuit that converts continuous signals to discrete digital numbers. Thereverse operation is performed by a digital-to-analog converter (DAC).

APS See Automatic Protection Switching

ARP See Address Resolution Protocol

ASK amplitude shift keying

ATPC See automatic transmit power control

AU See Administrative Unit

Automatic GainControl

A process or means by which gain is automatically adjusted in a specified manner as afunction of a specified parameter, such as received signal level.

Automatic ProtectionSwitching

Automatic Protection Switching (APS) is the capability of a transmission system todetect a failure on a working facility and to switch to a standby facility to recover thetraffic.

automatic transmitpower control

A method of adjusting the transmit power based on fading of the transmit signal detectedat the receiver

B

Base Station Controller A logical entity that connects the BTS with the MSC in a GSM network. It interworkswith the BTS through the Abis interface, the MSC through the A interface. It providesthe following functions: Radio resource management, Base station management, Powercontrol, Handover control, and Traffic measurement. One BSC controls and managesone or more BTSs in an actual network.

BER See Bit Error Rate

BIOS Basic Input Output System

BIP Bit-Interleaved Parity

bit error An incompatibility between a bit in a transmitted digital signal and the correspondingbit in the received digital signal.

Bit Error Rate Bit error rate. Ratio of received bits that contain errors. BER is an important index usedto measure the communications quality of a network.

BPDU See Bridge Protocol Data Unit

Bridge Protocol DataUnit

The data messages that are exchanged across the switches within an extended LAN thatuses a spanning tree protocol (STP) topology. BPDU packets contain information onports, addresses, priorities and costs and ensure that the data ends up where it wasintended to go. BPDU messages are exchanged across bridges to detect loops in anetwork topology. The loops are then removed by shutting down selected bridgesinterfaces and placing redundant switch ports in a backup, or blocked, state.

BSC See Base Station Controller



H-3

C

C-VLAN Customer VLAN

CAR See committed access rate

CBS See Committed Burst Size

CCDP See Co-Channel Dual Polarization

Central ProcessingUnit

The CPU is the brains of the computer. Sometimes referred to simply as the processoror central processor, the CPU is where most calculations take place.

CF See compact flash

CGMP Cisco Group Management Protocol

CIR See Committed Information Rate

CIST See Common and Internal Spanning Tree

Class of Service A class object that stores the priority mapping rules. When network congestion occurs,the class of service (CoS) first processes services by different priority levels from highto low. If the bandwidth is insufficient to support all services, the CoS dumps the servicesof low priority.

Co-Channel DualPolarization

A channel configuration method, which uses a horizontal polarization wave and a verticalpolarization wave to transmit two signals. The Co-Channel Dual Polarization is twicethe transmission capacity of the single polarization.

committed access rate A traffic control method that uses a set of rate limits to be applied to a router interface.CAR is a configurable method by which incoming and outgoing packets can be classifiedinto QoS (Quality of Service) groups, and by which the input or output transmission ratecan be defined.

Committed Burst Size committed burst size. A parameter used to define the capacity of token bucket C, that is,the maximum burst IP packet size when the information is transferred at the committedinformation rate. This parameter must be larger than 0. It is recommended that thisparameter should be not less than the maximum length of the IP packet that might beforwarded.

CommittedInformation Rate

The rate at which a frame relay network agrees to transfer information in normalconditions. Namely, it is the rate, measured in bit/s, at which the token is transferred tothe leaky bucket.

Common and InternalSpanning Tree

Common and Internal Spanning Tree. The single Spanning Tree calculated by STP andRSTP together with the logical continuation of that connectivity through MST Bridgesand regions, calculatedby MSTP to ensure that all LANs in the Bridged Local AreaNetwork are simply and fully connected.

compact flash Compact flash (CF) was originally developed as a type of data storage device used inportable electronic devices. For storage, CompactFlash typically uses flash memory ina standardized enclosure.

CoS See Class of Service

CPU See Central Processing Unit

CRC See Cyclic Redundancy Check




Issue 05 (2010-07-30)

cross polarizationinterferencecancellation

A technology used in the case of the Co-Channel Dual Polarization (CCDP) to eliminatethe cross-connect interference between two polarization waves in the CCDP.

Cyclic RedundancyCheck

A procedure used in checking for errors in data transmission. CRC error checking usesa complex calculation to generate a number based on the data transmitted. The sendingdevice performs the calculation before transmission and includes it in the packet that itsends to the receiving device. The receiving device repeats the same calculation aftertransmission. If both devices obtain the same result, it is assumed that the transmissionwas error free. The procedure is known as a redundancy check because each transmissionincludes not only data but extra (redundant) error-checking values.

D

Data CommunicationNetwork

A communication network used in a TMN or between TMNs to support the DataCommunication Function (DCF).

Data CommunicationsChannel

The data channel that uses the D1-D12 bytes in the overhead of an STM-N signal totransmit information on operation, management, maintenance and provision (OAM&P)between NEs. The DCC channels that are composed of bytes D1-D3 is referred to as the192 kbit/s DCC-R channel. The other DCC channel that are composed of bytes D4-D12is referred to as the 576 kbit/s DCC-M channel.

DC See Direct Current

DC-C See DC-Return Common (with Ground)

DC-I See DC-Return Isolate (with Ground)

DC-Return Common(with Ground)

A power system, in which the BGND of the DC return conductor is short-circuited withthe PGND on the output side of the power supply cabinet and also on the line betweenthe output of the power supply cabinet and the electric equipment.

DC-Return Isolate(with Ground)

A power system, in which the BGND of the DC return conductor is short-circuited withthe PGND on the output side of the power supply cabinet and is isolated from the PGNDon the line between the output of the power supply cabinet and the electric equipment.

DCC See Data Communications Channel

DCN See Data Communication Network

Differentiated ServicesCode Point

Differentiated Services CodePoint. A marker in the header of each IP packet using bits0-6 in the DS field. Routers provide differentiated classes of services to various servicestreams/flows based on this marker. In other words, routers select corresponding PHBaccording to the DSCP value.

digital modulation A digital modulation controls the changes in amplitude, phase, and frequency of thecarrier based on the changes in the baseband digital signal. In this manner, theinformation can be transmitted by the carrier.

Direct Current Electrical current whose direction of flow does not reverse. The current may stop orchange amplitude, but it always flows in the same direction.

Distance VectorMulticast RoutingProtocol

Distance Vector Multicast Routing Protocol. The DVMRP protocol is an Internetgateway protocol mainly based on the RIP. The protocol implements a typical densemode IP multicast solution. The DVMRP protocol uses IGMP to exchange routingdatagrams with its neighbors.

DSCP See Differentiated Services Code Point



H-5

dual-polarized antenna An antenna intended to radiate or receive simultaneously two independent radio wavesorthogonally polarized.

DVMRP See Distance Vector Multicast Routing Protocol

E

E-LAN Ethernet-LAN

ECC See Embedded Control Channel

Electro MagneticInterference

Any electromagnetic disturbance that interrupts, obstructs, or otherwise degrades orlimits the effective performance of electronics/electrical equipment.

electromagneticcompatibility

Electromagnetic compatibility is the condition which prevails when telecommunicationsequipment is performing its individually designed function in a common electromagneticenvironment without causing or suffering unacceptable degradation due to unintentionalelectromagnetic interference to or from other equipment in the same environment.[NTIA]

Embedded ControlChannel

An ECC provides a logical operations channel between SDH NEs, utilizing a datacommunications channel (DCC) as its physical layer.

EMC See electromagnetic compatibility

EMI See Electro Magnetic Interference

EPL See Ethernet Private Line

EPLAN See ethernet private lan service

equalization A method of avoiding selective fading of frequencies. Equalization can compensate forthe changes of amplitude frequency caused by frequency selective fading.

ERPS See ethernet ring protection switching

ES-IS End System to Intermediate System

ethernet private lanservice

An Ethernet service type, which carries Ethernet characteristic information over adedocated bridge, point-to-multipoint connections, provided by SDH, PDH, ATM, orMPLS server layer networks.

Ethernet Private Line A point-to-point interconnection between two UNIs without SDH bandwidth sharing.Transport bandwidth is never shared between different customers.

ethernet ringprotection switching

protection switching mechanisms for ETH layer Ethernet ring topologies.

ethernet virtual privatelan service

An Ethernet service type, which carries Ethernet characteristic information over a sharedbridge, point-to-multipoint connections, provided by SDH, PDH, ATM, or MPLS serverlayer networks.

ethernet virtual privateline service

An Ethernet service type, which carries Ethernet characteristic information over sharedbandwidth, point-to-point connections, provided by SDH, PDH, ATM, or MPLS serverlayer networks.

ETSI See European Telecommunications Standards Institute

EuropeanTelecommunicationsStandards Institute

A standards-setting body in Europe. Also the standards body responsible for GSM.




Issue 05 (2010-07-30)

EVPL See ethernet virtual private line service

EVPLAN See ethernet virtual private lan service

H.3 F-JThis section provides the terms starting with letters F to J.

F

Fast Ethernet A type of Ethernet with a maximum transmission rate of 100 Mbit/s. It complies withthe IEEE 802.3u standard and extends the traditional media-sharing Ethernet standard.

fast link pulse The likn pulse that is used to encode information during automatic negotiation.

FCS Frame Check Sequence

FD See frequency diversity

FE See Fast Ethernet

FEC See Forward Error Correction

Field ProgrammableGate Array

A type of semi-customized circuit used in the Application Specific Integrated Circuit(ASIC) field. It is developed on the basis of the programmable components, such as thePAL, GAL, and EPLD. It not only remedies the defects of customized circuits, but alsoovercomes the disadvantage of the original programmable components in terms of thelimited number of gate arraies.

FIFO See First in First out

File Transfer Protocol A member of the TCP/IP suite of protocols, used to copy files between two computerson the Internet. Both computers must support their respective FTP roles: one must be anFTP client and the other an FTP server.

First in First out A stack management mechanism. The first saved data is first read and invoked.

FLP See fast link pulse

Forward ErrorCorrection

A bit error correction technology that adds the correction information to the payload atthe transmit end. Based on the correction information, the bit errors generated duringtransmission are corrected at the receive end.

FPGA See Field Programmable Gate Array

frequency diversity A diversity scheme that enables two or more microwave frequencies with a certainfrequency interval are used to transmit/receive the same signal and selection is thenperformed between the two signals to ease the impact of fading.

FTP See File Transfer Protocol

G

gateway networkelement

A network element that is used for communication between the NE application layer andthe NM application layer

GE See Gigabit Ethernet



H-7

Generic traffic shaping A traffic control measure that initiatively adjusts the output speed of the traffic. This isto adapt the traffic to network resources that can be provided by the downstream routerto avoid packet discarding and congestion.

GFP Generic Framing Procedure

Gigabit Ethernet GE adopts the IEEE 802.3z. GE is compatible with 10 Mbit/s and 100 Mbit/s Ethernet.Itruns at 1000Mbit/s. Gigabit Ethernet uses a private medium, and it does not supportcoaxial cables or other cables. It also supports the channels in the bandwidth mode. IfGigabit Ethernet is, however, deployed to be the private bandwidth system with a bridge(switch) or a router as the center, it gives full play to the performance and the bandwidth.In the network structure, Gigabit Ethernet uses full duplex links that are private, causingthe length of the links to be sufficient for backbone applications in a building and campus.

GNE See gateway network element

Graphical UserInterface

A visual computer enviroment that represents programs, files, and options with graphicalimages, such as icons, menus, and dialog boxes, on the screen.

GTS See Generic traffic shaping

GUI See Graphical User Interface

H

HDB3 High Density Bipolar Code 3

HDLC See High level Data Link Control procedure

High level Data LinkControl procedure

A data link protocol from ISO for point-to-point communications over serial links.Derived from IBM's SDLC protocol, HDLC has been the basis for numerous protocolsincluding X.25, ISDN, T1, SS7, GSM, CDPD, PPP and others. Various subsets of HDLChave been developed under the name of Link Access Procedure (LAP).

hot standby A mechanism of ensuring device running security. The environment variables andstorage information of each running device are synchronized to the standby device. Whenthe faults occur on the running device, the standby device can take over the services inthe faulty device in automatic or manual way to ensure the normal running of the entiresystem.

HSM Hitless Switch Mode

hybrid radio The hybrid transmission of Native E1 and Native Ethernet signals. Hybrid radio supportsthe AM function.

I

ICMP See Internet Control Messages Protocol

IDU See indoor unit

IEC See International Electrotechnical Commission

IEEE See Institute of Electrical and Electronics Engineers

IETF The Internet Engineering Task Force

IF See intermediate frequency

IGMP See Internet Group Management Protocol




Issue 05 (2010-07-30)

IGMP snooping A multicast constraint mechanism running on a layer 2 device. This protocol managesand controls the multicast group by listening to and analyze the Internet GroupManagement Protocol (IGMP) packet between hosts and layer 3 devices. In this manner,the spread of the multicast data on layer 2 network can be prevented efficiently.

indoor unit The indoor unit of the split-structured radio equipment. It implements accessing,multiplexing/demultiplexing, and IF processing for services.

Institute of Electricaland ElectronicsEngineers

A society of engineering and electronics professionals based in the United States butboasting membership from numerous other countries. The IEEE focuses on electrical,electronics, computer engineering, and science-related matters.

intermediate frequency The transitional frequency between the frequencies of a modulated signal and an RFsignal.

intermediate frequency The transitional frequency between the frequencies of a modulated signal and an RFsignal.

Intermediate System toIntermediate System

A protocol used by network devices (routers) .IS-IS is a kind of Interior Gateway Protocol(IGP), used within the ASs. It is a link status protocol using Shortest Path First (SPF)algorithm to calculate the route.

InternationalElectrotechnicalCommission

The International Electrotechnical Commission (IEC) is an international and non-governmental standards organization dealing with electrical and electronical standards.

InternationalOrganization forStandardization

ISO (International Organization for Standardization) is the world's largest developer andpublisher of International Standards.

Internet ControlMessages Protocol

ICMP belongs to the TCP/IP protocol suite. It is used to send error and control messagesduring the transmission of IP-type data packets.

Internet GroupManagement Protocol

The protocol for managing the membership of Internet Protocol multicast groups amongthe TCP/IP protocols. It is used by IP hosts and adjacent multicast routers to establishand maintain multicast group memberships.

Internet Protocol The TCP/IP standard protocol that defines the IP packet as the unit of information sentacross an internet and provides the basis for connectionless, best-effort packet deliveryservice. IP includes the ICMP control and error message protocol as an integral part. Theentire protocol suite is often referred to as TCP/IP because TCP and IP are the twofundamental protocols. IP is standardized in RFC 791.

Internet ProtocolVersion 6

A update version of IPv4. It is also called IP Next Generation (IPng). The specificationsand standardizations provided by it are consistent with the Internet Engineering TaskForce (IETF).Internet Protocol Version 6 (IPv6) is also called. It is a new version of theInternet Protocol, designed as the successor to IPv4. The specifications andstandardizations provided by it are consistent with the Internet Engineering Task Force(IETF).The difference between IPv6 and IPv4 is that an IPv4 address has 32 bits whilean IPv6 address has 128 bits.

IP See Internet Protocol

IPv6 See Internet Protocol Version 6

IS-IS See Intermediate System to Intermediate System

ISO See International Organization for Standardization

ITU-T International Telecommunication Union - Telecommunication Standardization Sector



H-9

IVL Independence VLAN learning

H.4 K-OThis section provides the terms starting with letters K to O.

L

LAG See link aggregation group

LAN See Local Area Network

LAPD Link Access Procedure on the D channel

LAPS Link Access Procedure-SDH

layer 2 switch A data forwarding method. In LAN, a network bridge or 802.3 Ethernet switch transmitsand distributes packet data based on the MAC address. Since the MAC address is thesecond layer of the OSI model, this data forwarding method is called layer 2 switch.

LB See Loopback

LCAS See Link Capacity Adjustment Scheme

LDPC Low-Density Parity Check code

link aggregation group An aggregation that allows one or more links to be aggregated together to form a linkaggregation group so that a MAC clientcan treat the link aggregation group as if it werea single link.

Link CapacityAdjustment Scheme

The Link Capacity Adjustment Scheme (LCAS) is designed to allow the dynamicprovisioning of bandwidth, using VCAT, to meet customer requirements.

LMSP Linear Multiplex Section Protection

Local Area Network A network formed by the computers and workstations within the coverage of a few squarekilometers or within a single building. It features high speed and low error rate. Ethernet,FDDI, and Token Ring are three technologies used to implement a LAN. Current LANsare generally based on switched Ethernet or Wi-Fi technology and running at 1,000 Mbit/s (that is, 1 Gbit/s).

Loopback A troubleshooting technique that returns a transmitted signal to its source so that thesignal or message can be analyzed for errors.

LPT Link State Path Through

M

MA See Maintenance Association

MAC See Medium Access Control

MADM Multi Add-Drop Multiplexer

MaintenanceAssociation

That portion of a Service Instance, preferably all of it or as much as possible, theconnectivity of which is maintained by CFM. It is also a full mesh of MaintenanceEntities.




Issue 05 (2010-07-30)

Maintenance Domain The Maintenance Domain (MD) refers to the network or the part of the network for whichconnectivity is managed by CFM. The devices in an MD are managed by a single ISP.

Maintenance Point Maintenance Point (MP) is one of either a MEP or a MIP.

ManagementInformation Base

A type of database used for managing the devices in a communications network. Itcomprises a collection of objects in a (virtual) database used to manage entities (such asrouters and switches) in a network.

Maximum TransferUnit

The MTU (Maximum Transmission Unit) is the size of the largest datagram that can besent over a network.

MBS Maximum Burst Size

MD See Maintenance Domain

MDI See Medium Dependent Interface

Mean Time To Repair The average time that a device will take to recover from a failure.

Medium AccessControl

A general reference to the low-level hardware protocols used to access a particularnetwork. The term MAC address is often used as a synonym for physical addresses.

Medium DependentInterface

The electrical and mechanical interface between the equipment and the mediatransmission.

MEP Maintenance End Point

MIB See Management Information Base

MP See Maintenance Point

MSP See multiplex section protection

MSTP See Multiple Spanning Tree Protocol

MTBF Mean Time Between Failure

MTTR See Mean Time To Repair

MTU See Maximum Transfer Unit

Multiple SpanningTree Protocol

Multiple spanning tree protocol. The MSTP can be used in a loop network. Using analgorithm, the MSTP blocks redundant paths so that the loop network can be trimmedas a tree network. In this case, the proliferation and endless cycling of packets is avoidedin the loop network.The protocol that introduces the mapping between VLANs andmultiple spanning trees. This solves the problem that data cannot be normally forwardedin a VLAN because in STP/RSTP, only one spanning tree corresponds to all the VLANs.

multiplex sectionprotection

A function, which is performed to provide capability for switching a signal between andincluding two multiplex section termination (MST) functions, from a "working" to a"protection" channel.

N

N+1 protection A radio link protection system composed of N working channels and one protectionchannel.

NE See Network Element

Network Element A network element (NE) contains both the hardware and the software running on it. OneNE is at least equipped with one system control board which manages and monitors theentire network element. The NE software runs on the system control board.



H-11

network managementsystem

The network management system in charge of the operation, administration, andmaintenance of a network.

Network Service AccessPoint

A network address defined by ISO, through which entities on the network layer canaccess OSI network services.

NLP Normal Link Pulse

NMS See network management system

NNI Network-to-Network Interface or Network Node Interface

non-gateway networkelement

A network element whose communication with the NM application layer must betransferred by the gateway network element application layer.

non-GNE See non-gateway network element

NSAP See Network Service Access Point

O

OAM Operations, Administration and Maintenance

ODU See outdoor unit

Open Shortest PathFirst

A link-state, hierarchical interior gateway protocol (IGP) for network routing. Dijkstra'salgorithm is used to calculate the shortest path tree. It uses cost as its routing metric. Alink state database is constructed of the network topology which is identical on all routersin the area.

Open SystemsInterconnection

A standard or "reference model" (officially defined by the International Organization ofStandards (ISO)) for how messages should be transmitted between any two points in atelecommunication network. The reference model defines seven layers of functions thattake place at each end of a communication.

orderwire A channel that provides voice communication between operation engineers ormaintenance engineers of different stations.

OSI See Open Systems Interconnection

OSPF See Open Shortest Path First

outdoor unit The outdoor unit of the split-structured radio equipment. It implements frequencyconversion and amplification for RF signals.

H.5 P-TThis section provides the terms starting with letters P to T.

P

PDH See Plesiochronous Digital Hierarchy

Peak Information Rate Peak Information Rate . A traffic parameter, expressed in bit/s, whose value should benot less than the committed information rate.

PIM-DM Protocol Independent Multicast-Dense Mode

PIM-SM See Protocol Independent Multicast-Sparse Mode




Issue 05 (2010-07-30)

PIR See Peak Information Rate

Plesiochronous DigitalHierarchy

A multiplexing scheme of bit stuffing and byte interleaving. It multiplexes the minimumrate 64 kit/s into the 2 Mbit/s, 34 Mbit/s, 140 Mbit/s, and 565 Mbit/s rates.

Point-to-Point Protocol A protocol on the data link layer, provides point-to-point transmission and encapsulatesdata packets on the network layer. It is located in layer 2 of the IP protocol stack.

polarization A kind of electromagnetic wave, the direction of whose electric field vector is fixed orrotates regularly. Specifically, if the electric field vector of the electromagnetic wave isperpendicular to the plane of horizon, this electromagnetic wave is called verticallypolarized wave; if the electric field vector of the electromagnetic wave is parallel to theplane of horizon, this electromagnetic wave is called horizontal polarized wave; if thetip of the electric field vector, at a fixed point in space, describes a circle, thiselectromagnetic wave is called circularly polarized wave.

PPP See Point-to-Point Protocol

PRBS Pseudo-Random Binary Sequence

Protocol IndependentMulticast-Sparse Mode

A protocol for efficiently routing to multicast groups that may span wide-area (and inter-domain) internets. This protocol is named protocol independent because it is notdependent on any particular unicast routing protocol for topology discovery, and sparse-mode because it is suitable for groups where a very low percentage of the nodes (andtheir routers) will subscribe to the multicast session. Unlike earlier dense-mode multicastrouting protocols such as DVMRP and PIM-DM which flooded packets everywhere andthen pruned off branches where there were no receivers, PIM-SM explicitly constructsa tree from each sender to the receivers in the multicast group. Multicast packets fromthe sender then follow this tree.

Q

QoS See Quality of Service

QPSK See Quadrature Phase Shift Keying

Quadrature Phase ShiftKeying

Quadrature Phase Shift Keying (QPSK) is a modulation method of data transmissionthrough the conversion or modulation and the phase determination of the referencesignals (carrier). It is also called the fourth period or 4-phase PSK or 4-PSK. QPSK usesfour dots in the star diagram. The four dots are evenly distributed on a circle. On thesephases, each QPSK character can perform two-bit coding and display the codes in Graycode on graph with the minimum BER.

Quality of Service Quality of Service, which determines the satisfaction of a subscriber for a service. QoSis influenced by the following factors applicable to all services: service operability,service accessibility, service maintainability, and service integrity.

R

Radio Freqency A type of electric current in the wireless network using AC antennas to create anelectromagnetic field. It is the abbreviation of high-frequency AC electromagnetic wave.The AC with the frequency lower than 1 kHz is called low-frequency current. The ACwith frequency higher than 10 kHz is called high-frequency current. RF can be classifiedinto such high-frequency current.

Radio NetworkController

A device used in the RNS to control the usage and integrity of radio resources.



H-13

Rapid Spanning TreeProtocol

An evolution of the Spanning Tree Protocol, providing for faster spanning treeconvergence after a topology change. The RSTP protocol is backward compatible withthe STP protocol.

Received signal level The signal level at a receiver input terminal.

Received SignalStrength Indicator

The received wide band power, including thermal noise and noise generated in thereceiver, within the bandwidth defined by the receiver pulse shaping filter, for TDDwithin a specified timeslot. The reference point for the measurement shall be the antenna

RF See Radio Freqency

RFC Request For Comment

RIP See Routing Information Protocol

RMON Remote Monitoring

RNC See Radio Network Controller

Routing InformationProtocol

Routing Information Protocol: A simple routing protocol that is part of the TCP/IPprotocol suite. It determines a route based on the smallest hop count between source anddestination. RIP is a distance vector protocol that routinely broadcasts routinginformation to its neighboring routers and is known to waste bandwidth.

RS Reed-Solomon encoding

RSL Received Signal Level

RSSI See Received Signal Strength Indicator

RSTP See Rapid Spanning Tree Protocol

RTN Radio Transmission Node

S

SD See space diversity

SDH See Synchronous Digital Hierarchy

SFP See Small Form-Factor Pluggable

Signal Noise Ratio The SNR or S/N (Signal to Noise Ratio) of the amplitude of the desired signal to theamplitude of noise signals at a given point in time. SNR is expressed as 10 times thelogarithm of the power ratio and is usually expressed in dB (Decibel).

Simple NetworkManagement Protocol

A network management protocol of TCP/IP. It enables remote users to view and modifythe management information of a network element. This protocol ensures thetransmission of management information between any two points. The pollingmechanism is adopted to provide basic function sets. According to SNMP, agents, whichcan be hardware as well as software, can monitor the activities of various devices on thenetwork and report these activities to the network console workstation. Controlinformation about each device is maintained by a management information block.

Small Form-FactorPluggable

A specification for a new generation of optical modular transceivers.

SNC See SubNetwork Connection

SNCP See SubNetwork Connection Protection

SNMP See Simple Network Management Protocol




Issue 05 (2010-07-30)

SNR See Signal Noise Ratio

SP Strict Priority

space diversity A diversity scheme that enables two or more antennas separated by a specific distanceto transmit/receive the same signal and selection is then performed between the twosignals to ease the impact of fading. Currently, only receive SD is used.

Spanning Tree Protocol Spanning Tree Protocol. STP is a protocol that is used in the LAN to remove the loop.STP applies to the redundant network to block some undesirable redundant paths throughcertain algorithms and prune a loop network into a loop-free tree network.

SSM See Synchronization Status Message

STM See synchronous transport module

STM-1 SDH Transport Module -1

STM-1e STM-1 Electrical Interface

STM-1o STM-1 Optical Interface

STM-N SDH Transport Module -N

STP See Spanning Tree Protocol

sub-network Sub-network is the logical entity in the transmission network and comprises a group ofnetwork management objects. The network that consists of a group of interconnected orcorrelated NEs, according to different functions. For example, protection subnet, clocksubnet and so on. A sub-network can contain NEs and other sub-networks. Generally, asub-network is used to contain the equipments which are located in adjacent regions andclosely related with one another, and it is indicated with a sub-network icon on atopological view. The U2000 supports multilevels of sub-networks. A sub-networkplanning can better the organization of a network view. On the one hand, the view spacecan be saved, on the other hand, it helps the network management personnel focus onthe equipments under their management.

SubNetworkConnection

A "transport entity" that transfers information across a subnetwork, it is formed by theassociation of "ports" on the boundary of the subnetwork.

SubNetworkConnection Protection

A working subnetwork connection is replaced by a protection subnetwork connection ifthe working subnetwork connection fails, or if its performance falls below a requiredlevel.

SVL Shared VLAN Learning

Synchronization StatusMessage

A message that is used to transmit the quality levels of timing signals on the synchronoustiming link. Through this message, the node clocks of the SDH network and thesynchronization network can aquire upper stream clock information, and the two performoperations on the corresponding clocks, such as tracing, switchover, or converting hold),and then forward the synchronization information of this node to down stream.

Synchronous DigitalHierarchy

SDH is a transmission scheme that follows ITU-T G.707, G.708, and G.709. It definesthe transmission features of digital signals such as frame structure, multiplexing mode,transmission rate level, and interface code. SDH is an important part of ISDN and B-ISDN. It interleaves the bytes of low-speed signals to multiplex the signals to high-speedcounterparts, and the line coding of scrambling is only used only for signals. SDH issuitable for the fiber communication system with high speed and a large capacity sinceit uses synchronous multiplexing and flexible mapping structure.



H-15

synchronous transportmodule

An STM is the information structure used to support section layer connections in theSDH. It consists of information payload and Section Overhead (SOH) information fieldsorganized in a block frame structure which repeats every 125 . The information is suitablyconditioned for serial transmission on the selected media at a rate which is synchronizedto the network. A basic STM is defined at 155 520 kbit/s. This is termed STM-1. Highercapacity STMs are formed at rates equivalent to N times this basic rate. STM capacitiesfor N = 4, N = 16 and N = 64 are defined; higher values are under consideration.

T

TCI Tag Control Information

TCP See TransmissionControl Protocol

TDM See Time Division Multiplexing

TelecommunicationManagement Network

The Telecommunications Management Network is a protocol model defined by ITU-Tfor managing open systems in a communications network.An architecture formanagement, including planning, provisioning, installation, maintenance, operation andadministration of telecommunications equipment, networks and services.

Time DivisionMultiplexing

It is a multiplexing technology. TDM divides the sampling cycle of a channel into timeslots (TSn, n=0, 1, 2, 3...), and the sampling value codes of multiple signals engross timeslots in a certain order, forming multiple multiplexing digital signals to be transmittedover one channel.

TMN See Telecommunication Management Network

trail A type of transport entity, mainly engaged in transferring signals from the input of thetrail source to the output of the trail sink, and monitoring the integrality of the transferredsignals.

TransmissionControlProtocol

The protocol within TCP/IP that governs the breakup of data messages into packets tobe sent via IP (Internet Protocol), and the reassembly and verification of the completemessages from packets received by IP. A connection-oriented, reliable protocol (reliablein the sense of ensuring error-free delivery), TCP corresponds to the transport layer inthe ISO/OSI reference model.

TU Tributary Unit

H.6 U-ZThis section provides the terms starting with letters U to Z.

U

UDP See User Datagram Protocol

UNI See User Network Interface




Issue 05 (2010-07-30)

User DatagramProtocol

A TCP/IP standard protocol that allows an application program on one device to send adatagram to an application program on another. User Datagram Protocol (UDP) uses IPto deliver datagrams. UDP provides application programs with the unreliableconnectionless packet delivery service. Thus, UDP messages can be lost, duplicated,delayed, or delivered out of order.UDP is used to try to transmit the data packet, that is,the destination device does not actively confirm whether the correct data packet isreceived.

User Network Interface A type of ATM Forum specification that defines an interoperability standard for theinterface between ATM-based products (a router or an ATM switch) located in a privatenetwork and the ATM switches located within the public carrier networks. Also used todescribe similar connections in Frame Relay networks.

V

VC See Virtual Container

VC-12 Virtual Container -12



VCG See virtual concatenation group

VCTRUNK A virtual concatenation group applied in data service mapping, also called the internalport of a data service processing board

virtual concatenationgroup

A group of co-located member trail termination functions that are connected to the samevirtual concatenation link

Virtual Container A Virtual Container is the information structure used to support path layer connectionsin the SDH. It consists of information payload and path Overhead (POH) informationfields organized in a block frame structure which repeats every 125 or 500 μs.

Virtual Local AreaNetwork

A logical grouping of two or more nodes which are not necessarily on the same physicalnetwork segment but which share the same IP network number. This is often associatedwith switched Ethernet.

Virtual PrivateNetwork

The extension of a private network that encompasses encapsulated, encrypted, andauthenticated links across shared or public networks. VPN connections can provideremote access and routed connections to private networks over the Internet.

VLAN See Virtual Local Area Network

Voice over IP An IP telephony term for a set of facilities used to manage the delivery of voiceinformation over the Internet. VoIP involves sending voice information in a digital formin discrete packets rather than by using the traditional circuit-committed protocols of thepublic switched telephone network (PSTN).

VoIP See Voice over IP

VPN See Virtual Private Network

W

Wait to Restore Time A period of time that must elapse before a - from a fault recovered - trail/connection canbe used again to transport the normal traffic signal and/or to select the normal trafficsignal from.



H-17

WAN See Wide Area Network

Web LCT The local maintenance terminal of a transport network, which is located on the NEmanagement layer of the transport network

Wide Area Network A network composed of computers which are far away from each other which arephysically connected through specific protocols. WAN covers a broad area, such as aprovince, a state or even a country.

WRR Weighted Round Robin

WTR See Wait to Restore Time

X

XPD Cross-Polarization Discrimination

XPIC See cross polarization interference cancellation




Issue 05 (2010-07-30)

159930386-RTN-950-Maintenance-Guide-U2000-V100R002C00-05

Documents

huawei trademarks

huawei proprietary

huawei industrial basebantian

versionoptix rtn

additional information

multilevel menus

high level of risk

data loss