RTN 620 Maintenance Guide(V100R005C00_04)

OptiX RTN 620 Radio Transmission SystemV100R005C00

Maintenance Guide

Issue 04

Date 2010-10-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 04 (2010-10-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 620 V100R005C00

iManager U2000 V100R002C00

Intended AudienceThis document is intended for the maintenance engineers of the OptiX RTN 620. Before readingthis document, you need to:

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 620 Radio Transmission SystemMaintenance Guide 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.

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

Convention Description

Times New Roman Normal paragraphs are in Times New Roman.

Boldface Names of files, directories, folders, and users are inboldface. For example, log in as user root.

Italic Book titles are in italics.

Courier New Examples of information displayed on the screen are inCourier New.

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


Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

[ ] Items (keywords or arguments) in brackets [ ] are optional.

{ x | y | ... } Optional items are grouped in braces and separated byvertical bars. One item is selected.

[ x | y | ... ] Optional items are grouped in brackets and separated byvertical bars. One item is selected or no item is selected.

About This DocumentOptiX RTN 620 Radio Transmission System

Maintenance Guide

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

Issue 04 (2010-10-30)


{ x | y | ... }* Optional items are grouped in braces and separated byvertical bars. A minimum of one item or a maximum of allitems can be selected.

[ x | y | ... ]* Optional items are grouped in brackets and separated byvertical bars. Several items or no item can be selected.

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


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.

Change HistoryUpdates between document versions are cumulative. Therefore, the latest document versioncontains all updates made to previous versions.

Updates in Issue 04 (2010-10-30)

This document is the fourth release of the V100R005C00 version.

Update Description

A Alarm Reference Added descriptions of the LFA, LMFA, andRMFA alarms.

Updates in Issue 03 (2010-05-30)

This document is the third release of the V100R005C00 version.

Update Description

7 Supporting Task Added 7.20 Monitoring Ethernet PacketsThrough Port Mirroring.

OptiX RTN 620 Radio Transmission SystemMaintenance Guide About This Document


v

Updates in Issue 02 (2010-03-30)This document is the second release of the V100R005C00 version.

Update Description

A Alarm Reference Deleted the alarm SWDL_PKGVER_MM.

Updates in Issue 01 (2009-12-30)This document is the first release of the V100R005C00 version.

About This DocumentOptiX RTN 620 Radio Transmission System

Maintenance Guide

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

Issue 04 (2010-10-30)

Contents

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

1 Safety Precautions......................................................................................................................1-11.1 General Safety Precautions.............................................................................................................................1-11.2 Electrical Safety..............................................................................................................................................1-31.3 Flammable Air Environment...........................................................................................................................1-51.4 Radiation.........................................................................................................................................................1-51.5 Working at Heights.........................................................................................................................................1-71.6 Mechanical Safety.........................................................................................................................................1-101.7 Other Precautions..........................................................................................................................................1-11

2 Guides to High-Risk Operations............................................................................................2-12.1 Operation Guide to a Toggle Lever Switch.....................................................................................................2-22.2 Operation Guide to IF Jumpers.......................................................................................................................2-32.3 Operation Guide to IF Cables..........................................................................................................................2-42.4 Operation Guide to IF Boards.........................................................................................................................2-5

3 Routine Maintenance................................................................................................................3-13.1 Routine Maintenance Items.............................................................................................................................3-23.2 Guidelines for Routine Maintenance Items.....................................................................................................3-3

3.2.1 Checking the Status of NEs....................................................................................................................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 the Current Performance........................................................................................................3-73.2.6 Browsing the History Performance........................................................................................................3-83.2.7 Browsing the History Transmit Power and Receive Power...................................................................3-93.2.8 Testing IF 1+1 Switching.....................................................................................................................3-103.2.9 Testing IF N+1 Switching....................................................................................................................3-113.2.10 Testing Two-Fiber Bidirectional MSP Ring Switching.....................................................................3-123.2.11 Cleaning the Air Filter........................................................................................................................3-133.2.12 Checking the Equipment Room.........................................................................................................3-143.2.13 Checking the ODU.............................................................................................................................3-143.2.14 Checking the Hybrid Coupler............................................................................................................3-153.2.15 Checking the Antenna........................................................................................................................3-15

OptiX RTN 620 Radio Transmission SystemMaintenance Guide Contents


vii

3.2.16 Checking the IF Cables......................................................................................................................3-163.2.17 Checking the LOS Condition.............................................................................................................3-17

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

5 Troubleshooting.........................................................................................................................5-15.1 General Troubleshooting Procedure................................................................................................................5-35.2 Troubleshooting Service Interruption.............................................................................................................5-55.3 Troubleshooting Radio Links........................................................................................................................5-105.4 Troubleshooting Bit Errors in TDM Services...............................................................................................5-195.5 Troubleshooting the Interconnection with the SDH Equipment...................................................................5-245.6 Troubleshooting the Interconnection with the PDH Equipment...................................................................5-275.7 Troubleshooting SDH/PDH Radio-Based Ethernet Service Faults..............................................................5-295.8 Troubleshooting Faults in Hybrid Radio-Based Ethernet Services..............................................................5-355.9 Troubleshooting Pointer Justifications..........................................................................................................5-415.10 Troubleshooting Orderwire Faults..............................................................................................................5-46

6 Part Replacement........................................................................................................................6-16.1 Removing a Board...........................................................................................................................................6-46.2 Inserting a Board.............................................................................................................................................6-56.3 Replacing the SDH Optical Interface Board...................................................................................................6-76.4 Replacing the SDH Electrical Interface Board................................................................................................6-86.5 Replacing the PDH Interface Board................................................................................................................6-96.6 Replacing the Ethernet Service Processing Board........................................................................................6-106.7 Replacing the IF Board.................................................................................................................................6-116.8 Replacing the PXC Board.............................................................................................................................6-126.9 Replacing the Storage Card...........................................................................................................................6-146.10 Replacing the SCC Board...........................................................................................................................6-186.11 Replacing the Fan Tray...............................................................................................................................6-196.12 Replacing an ODU......................................................................................................................................6-216.13 Replacing the IF Cable................................................................................................................................6-22

7 Supporting Task.........................................................................................................................7-17.1 Hardware Loopback........................................................................................................................................7-37.2 Cleaning Fiber Connectors and Adapters........................................................................................................7-3

7.2.1 Cleaning Fiber Connectors Using Cartridge Cleaners...........................................................................7-37.2.2 Cleaning Fiber Connectors Using Lens Tissue......................................................................................7-57.2.3 Cleaning Fiber Adapters Using Optical Cleaning Sticks.......................................................................7-6

7.3 Browsing Alarms, Abnormal Events, and Performance Events.....................................................................7-77.3.1 Checking the NE Status..........................................................................................................................7-87.3.2 Checking the Board Status.....................................................................................................................7-97.3.3 Browsing the Current Alarms................................................................................................................7-9

ContentsOptiX RTN 620 Radio Transmission System

Maintenance Guide

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

Issue 04 (2010-10-30)

7.3.4 Browsing History Alarms.....................................................................................................................7-107.3.5 Browsing the Abnormal Events...........................................................................................................7-117.3.6 Browsing Current Performance Events................................................................................................7-127.3.7 Browsing the History Performance......................................................................................................7-127.3.8 Browsing the Performance Event Threshold-Crossing Records..........................................................7-14

7.4 Querying a Report.........................................................................................................................................7-147.4.1 Querying a Board Information Report Through the Web LCT............................................................7-157.4.2 Querying a Board Manufacture Information Report............................................................................7-157.4.3 Querying the Status of a Radio Link....................................................................................................7-16

7.5 Software loopback.........................................................................................................................................7-177.5.1 Setting Loopback for the SDH Optical Interface Board......................................................................7-177.5.2 Setting Loopback for the SDH Electrical Interface Board...................................................................7-197.5.3 Setting Loopback for the Tributary Board...........................................................................................7-217.5.4 Setting Loopback for the IF Board.......................................................................................................7-227.5.5 Setting Loopback for the Ethernet Service Processing Board.............................................................7-257.5.6 Locating the Fault by Performing Loopbacks......................................................................................7-27

7.6 Resetting........................................................................................................................................................7-287.6.1 Cold Resetting......................................................................................................................................7-297.6.2 Warm Resetting....................................................................................................................................7-297.6.3 SCC Resetting......................................................................................................................................7-30

7.7 PRBS Test.....................................................................................................................................................7-307.7.1 PRBS Test of the Tributary Board.......................................................................................................7-317.7.2 PRBS Test of the IF Board...................................................................................................................7-33

7.8 Querying the License Capacity.....................................................................................................................7-347.9 Setting the State of a Laser............................................................................................................................7-347.10 Setting the ALS function.............................................................................................................................7-357.11 Setting the Automatic Release Function.....................................................................................................7-357.12 Switching PXC Boards................................................................................................................................7-367.13 Configuring Performance Monitoring Status of NEs..................................................................................7-367.14 Querying the Impedance of an E1 Channel.................................................................................................7-377.15 Using Ethernet Test Frames........................................................................................................................7-387.16 Querying the Working Status of an Ethernet Port.......................................................................................7-397.17 Setting the Threshold of Received Traffic Flow on an Ethernet Port.........................................................7-407.18 Performing Statistics for the Traffic Flow on an Ethernet Port..................................................................7-417.19 Performing Statistics for the Traffic Flow of Ethernet Services.................................................................7-427.20 Monitoring Ethernet Packets Through Port Mirroring................................................................................7-42

A Alarm Reference.......................................................................................................................A-1A.1 Alarm List......................................................................................................................................................A-2A.2 Alarms and Handling Procedures................................................................................................................A-13

A.2.1 A_LOC...............................................................................................................................................A-13A.2.2 ALM_GFP_dCSF...............................................................................................................................A-14A.2.3 ALM_GFP_dLFD..............................................................................................................................A-15



ix

A.2.4 AM_DOWNSHIFT............................................................................................................................A-16A.2.5 APS_FAIL..........................................................................................................................................A-17A.2.6 APS_INDI..........................................................................................................................................A-19A.2.7 APS_MANUAL_STOP.....................................................................................................................A-20A.2.8 AU_AIS..............................................................................................................................................A-21A.2.9 AU_LOP.............................................................................................................................................A-23A.2.10 B1_EXC...........................................................................................................................................A-24A.2.11 B1_SD..............................................................................................................................................A-27A.2.12 B2_EXC...........................................................................................................................................A-30A.2.13 B2_SD..............................................................................................................................................A-33A.2.14 B3_EXC...........................................................................................................................................A-35A.2.15 B3_EXC_VC3..................................................................................................................................A-38A.2.16 B3_SD..............................................................................................................................................A-41A.2.17 B3_SD_VC3.....................................................................................................................................A-43A.2.18 BD_NOT_INSTALLED..................................................................................................................A-46A.2.19 BD_STATUS...................................................................................................................................A-47A.2.20 BIP_EXC..........................................................................................................................................A-49A.2.21 BIP_SD.............................................................................................................................................A-50A.2.22 BOOTROM_BAD............................................................................................................................A-52A.2.23 C2_VCAIS.......................................................................................................................................A-53A.2.24 CONFIG_NOSUPPORT..................................................................................................................A-54A.2.25 DBMS_ERROR...............................................................................................................................A-56A.2.26 DBMS_PROTECT_MODE.............................................................................................................A-58A.2.27 DOWN_E1_AIS...............................................................................................................................A-59A.2.28 E1_LOC............................................................................................................................................A-60A.2.29 E1_LOS............................................................................................................................................A-61A.2.30 ESN_INVALID................................................................................................................................A-62A.2.31 ETH_CFM_MISMERGE.................................................................................................................A-63A.2.32 ETH_CFM_UNEXPERI..................................................................................................................A-65A.2.33 ETH_CFM_LOC..............................................................................................................................A-67A.2.34 ETH_CFM_RDI...............................................................................................................................A-69A.2.35 ETH_LOS.........................................................................................................................................A-71A.2.36 ETHOAM_DISCOVER_FAIL........................................................................................................A-72A.2.37 ETHOAM_RMT_CRIT_FAULT....................................................................................................A-74A.2.38 ETHOAM_RMT_LOOP..................................................................................................................A-75A.2.39 ETHOAM_RMT_SD.......................................................................................................................A-77A.2.40 ETHOAM_SELF_LOOP.................................................................................................................A-78A.2.41 ETHOAM_VCG_SELF_LOOP.......................................................................................................A-80A.2.42 EX_ETHOAM_CC_LOS.................................................................................................................A-81A.2.43 EX_ETHOAM_MPID_CNFLCT....................................................................................................A-83A.2.44 EXT_SYNC_LOS............................................................................................................................A-85A.2.45 F1PORT_FAILED...........................................................................................................................A-86


Maintenance Guide

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

Issue 04 (2010-10-30)

A.2.46 FAN_FAIL.......................................................................................................................................A-87A.2.47 FCS_ERR.........................................................................................................................................A-88A.2.48 FLOW_OVER..................................................................................................................................A-90A.2.49 HARD_BAD....................................................................................................................................A-91A.2.50 HP_CROSSTR.................................................................................................................................A-93A.2.51 HP_LOM..........................................................................................................................................A-94A.2.52 HP_RDI............................................................................................................................................A-96A.2.53 HP_REI.............................................................................................................................................A-97A.2.54 HP_SLM...........................................................................................................................................A-98A.2.55 HP_TIM............................................................................................................................................A-99A.2.56 HP_UNEQ......................................................................................................................................A-100A.2.57 HPAD_CROSSTR.........................................................................................................................A-102A.2.58 IF_CABLE_OPEN.........................................................................................................................A-103A.2.59 IF_INPWR_ABN...........................................................................................................................A-104A.2.60 IF_MODE_UNSUPPORTED........................................................................................................A-106A.2.61 IN_PWR_HIGH.............................................................................................................................A-107A.2.62 IN_PWR_LOW..............................................................................................................................A-108A.2.63 J0_MM...........................................................................................................................................A-110A.2.64 K1_K2_M.......................................................................................................................................A-111A.2.65 K2_M..............................................................................................................................................A-113A.2.66 LAG_PORT_FAIL.........................................................................................................................A-115A.2.67 LAG_VC_PORT_FAIL.................................................................................................................A-117A.2.68 LASER_CLOSED..........................................................................................................................A-118A.2.69 LASER_MOD_ERR_EX...............................................................................................................A-119A.2.70 LCAS_FOPR..................................................................................................................................A-121A.2.71 LCAS_FOPT..................................................................................................................................A-122A.2.72 LCAS_PLCR..................................................................................................................................A-124A.2.73 LCAS_PLCT..................................................................................................................................A-125A.2.74 LCAS_TLCR..................................................................................................................................A-127A.2.75 LCAS_TLCT..................................................................................................................................A-129A.2.76 LCS_LIMITED..............................................................................................................................A-130A.2.77 LFA.................................................................................................................................................A-132A.2.78 LICENSE_LOST............................................................................................................................A-133A.2.79 LICENSE_ERR..............................................................................................................................A-134A.2.80 LINK_ERR.....................................................................................................................................A-135A.2.81 LMFA.............................................................................................................................................A-137A.2.82 LOOP_ALM...................................................................................................................................A-138A.2.83 LP_CROSSTR................................................................................................................................A-140A.2.84 LP_R_FIFO....................................................................................................................................A-141A.2.85 LP_RDI...........................................................................................................................................A-142A.2.86 LP_RDI_VC12...............................................................................................................................A-143A.2.87 LP_RDI_VC3.................................................................................................................................A-144



xi

A.2.88 LP_REI...........................................................................................................................................A-145A.2.89 LP_REI_VC12...............................................................................................................................A-146A.2.90 LP_REI_VC3.................................................................................................................................A-147A.2.91 LP_RFI...........................................................................................................................................A-148A.2.92 LP_SIZE_ERR...............................................................................................................................A-149A.2.93 LP_SLM.........................................................................................................................................A-150A.2.94 LP_SLM_VC12..............................................................................................................................A-151A.2.95 LP_SLM_VC3................................................................................................................................A-152A.2.96 LP_T_FIFO....................................................................................................................................A-153A.2.97 LP_TIM..........................................................................................................................................A-154A.2.98 LP_TIM_VC12...............................................................................................................................A-155A.2.99 LP_TIM_VC3.................................................................................................................................A-156A.2.100 LP_UNEQ....................................................................................................................................A-157A.2.101 LP_UNEQ_VC12.........................................................................................................................A-159A.2.102 LP_UNEQ_VC3...........................................................................................................................A-160A.2.103 LPS_UNI_BI_M...........................................................................................................................A-161A.2.104 LPT_INEFFECT..........................................................................................................................A-162A.2.105 LPT_RFI.......................................................................................................................................A-163A.2.106 LSR_NO_FITED..........................................................................................................................A-165A.2.107 LSR_WILL_DIE..........................................................................................................................A-166A.2.108 LTI................................................................................................................................................A-167A.2.109 MOD_TYPE_MISMATCH.........................................................................................................A-168A.2.110 MS_AIS........................................................................................................................................A-170A.2.111 MS_CROSSTR.............................................................................................................................A-171A.2.112 MS_RDI.......................................................................................................................................A-172A.2.113 MS_REI........................................................................................................................................A-174A.2.114 MSAD_CROSSTR.......................................................................................................................A-175A.2.115 MSSW_DIFFERENT...................................................................................................................A-176A.2.116 MULTI_RPL_OWNER...............................................................................................................A-178A.2.117 MW_BER_EXC...........................................................................................................................A-179A.2.118 MW_BER_SD..............................................................................................................................A-180A.2.119 MW_FEC_UNCOR.....................................................................................................................A-181A.2.120 MW_LIM.....................................................................................................................................A-186A.2.121 MW_LOF.....................................................................................................................................A-188A.2.122 MW_RDI......................................................................................................................................A-193A.2.123 NESF_LOST................................................................................................................................A-194A.2.124 NESTATE_INSTALL..................................................................................................................A-196A.2.125 NO_BD_SOFT.............................................................................................................................A-196A.2.126 NP1_MANUAL_STOP................................................................................................................A-197A.2.127 NP1_SW_FAIL............................................................................................................................A-198A.2.128 NP1_SW_INDI.............................................................................................................................A-200A.2.129 OPM_FAIL...................................................................................................................................A-201


Maintenance Guide

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

Issue 04 (2010-10-30)

A.2.130 P_AIS...........................................................................................................................................A-202A.2.131 P_LOS..........................................................................................................................................A-203A.2.132 PROT_CONN_ERR.....................................................................................................................A-204A.2.133 PORT_MODULE_OFFLINE......................................................................................................A-206A.2.134 POWER_ALM.............................................................................................................................A-208A.2.135 PS..................................................................................................................................................A-209A.2.136 R_F_RST......................................................................................................................................A-210A.2.137 R_LOC.........................................................................................................................................A-211A.2.138 R_LOF..........................................................................................................................................A-213A.2.139 R_LOS..........................................................................................................................................A-215A.2.140 R_S_ERR.....................................................................................................................................A-217A.2.141 RADIO_FADING_MARGIN_INSUFF......................................................................................A-218A.2.142 RADIO_MUTE............................................................................................................................A-220A.2.143 RADIO_RSL_BEYONDTH........................................................................................................A-221A.2.144 RADIO_RSL_HIGH....................................................................................................................A-222A.2.145 RADIO_RSL_LOW.....................................................................................................................A-223A.2.146 RADIO_TSL_HIGH....................................................................................................................A-225A.2.147 RADIO_TSL_LOW.....................................................................................................................A-226A.2.148 RELAY_ALARM........................................................................................................................A-227A.2.149 RMFA...........................................................................................................................................A-228A.2.150 RP_LOC.......................................................................................................................................A-229A.2.151 RPS_INDI.....................................................................................................................................A-229A.2.152 RS_CROSSTR.............................................................................................................................A-231A.2.153 RTC_FAIL...................................................................................................................................A-232A.2.154 S1_SYN_CHANGE.....................................................................................................................A-233A.2.155 SWDL_ACTIVATED_TIMEOUT..............................................................................................A-234A.2.156 SWDL_AUTOMATCH_INH......................................................................................................A-235A.2.157 SWDL_COMMIT_FAIL.............................................................................................................A-236A.2.158 SWDL_CHGMNG_NOMATCH.................................................................................................A-237A.2.159 SWDL_INPROCESS...................................................................................................................A-238A.2.160 SWDL_NEPKGCHECK..............................................................................................................A-239A.2.161 SWDL_PKG_NOBDSOFT..........................................................................................................A-239A.2.162 SWDL_ROLLBACK_FAIL........................................................................................................A-240A.2.163 SYN_BAD....................................................................................................................................A-241A.2.164 SYNC_C_LOS.............................................................................................................................A-242A.2.165 T_ALOS.......................................................................................................................................A-243A.2.166 T_F_RST......................................................................................................................................A-245A.2.167 T_LOC..........................................................................................................................................A-246A.2.168 T_LOS..........................................................................................................................................A-247A.2.169 TEMP_ALARM...........................................................................................................................A-249A.2.170 TU_AIS........................................................................................................................................A-250A.2.171 TU_AIS_VC12.............................................................................................................................A-252



xiii

A.2.172 TU_AIS_VC3...............................................................................................................................A-254A.2.173 TU_LOP.......................................................................................................................................A-256A.2.174 TU_LOP_VC12............................................................................................................................A-258A.2.175 TU_LOP_VC3..............................................................................................................................A-260A.2.176 UP_E1_AIS..................................................................................................................................A-262A.2.177 VCAT_LOA.................................................................................................................................A-263A.2.178 VCAT_LOM_VC12.....................................................................................................................A-264A.2.179 VCAT_LOM_VC3.......................................................................................................................A-266A.2.180 VCAT_SQM_VC12.....................................................................................................................A-267A.2.181 VCAT_SQM_VC3.......................................................................................................................A-268A.2.182 VOLT_LOS..................................................................................................................................A-270A.2.183 W_R_Failure................................................................................................................................A-272A.2.184 WRG_BD_TYPE.........................................................................................................................A-273A.2.185 WRG_DEV_TYPE.......................................................................................................................A-274A.2.186 WS_LOS.......................................................................................................................................A-275A.2.187 XCP_INDI....................................................................................................................................A-276A.2.188 XPIC_LOS...................................................................................................................................A-277

B Abnormal Event Reference.....................................................................................................B-1B.1 Important Abnormal Events...........................................................................................................................B-2B.2 Important Abnormal Events and Handling Procedures.................................................................................B-2

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

C Performance Event Reference................................................................................................C-1C.1 Performance Event List..................................................................................................................................C-2

C.1.1 SDH/PDH Performance Events............................................................................................................C-2C.1.2 Microwave Performance Events...........................................................................................................C-7C.1.3 Other Performance Events....................................................................................................................C-9

C.2 Performance Events and Handling Procedures............................................................................................C-11C.2.1 AUPJCHIGH, AUPJCLOW, and AUPJCNEW.................................................................................C-11C.2.2 ATPC_P_ADJUST and ATPC_N_ADJUST.....................................................................................C-12C.2.3 TUPJCHIGH, TUPJCLOW, and TUPJCNEW..................................................................................C-12C.2.4 RSBBE, RSES, RSSES, RSCSES, and RSUAS................................................................................C-13C.2.5 RSOOF and RSOFS............................................................................................................................C-15C.2.6 MSBBE, MSES, MSSES, MSCSES, and MSUAS............................................................................C-16C.2.7 MSFEBBE, MSFEES, MSFESES, MSFECSES, and MSFEUAS.....................................................C-17


Maintenance Guide

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

Issue 04 (2010-10-30)

C.2.8 HPBBE, HPES, HPSES, HPCSES, and HPUAS...............................................................................C-18C.2.9 HPFEBBE, HPFEES, HPFESES, HPFECSES, and HPFEUAS........................................................C-20C.2.10 IF_BBE, IF_ES, IF_SES, IF_CSES, and IF_UAS...........................................................................C-21C.2.11 VC3BBE, VC3ES, VC3SES, VC3CSES, and VC3UAS.................................................................C-22C.2.12 VC3FEBBE, VC3FEES, VC3FESES, VC3FECSES, and VC3FEUAS..........................................C-23C.2.13 LPBBE, LPES, LPSES, LPCSES, and LPUAS................................................................................C-24C.2.14 LPFEBBE, LPFEES, LPFESES, LPFECSES, and LPFEUAS........................................................C-26C.2.15 E3_LCV_SDH, E3_LES_SDH, and E3_LSES_SDH......................................................................C-27C.2.16 T3_LCV_SDH, T3_LES_SDH, and T3_LSES_SDH......................................................................C-28C.2.17 TSL_MAX, TSL_MIN, TSL_CUR, and TSL_AVG.......................................................................C-29C.2.18 RSL_MAX, RSL_MIN, RSL_CUR, and RSL_AVG......................................................................C-29C.2.19 RLHTT, RLLTT, TLHTT, and TLLTT............................................................................................C-30C.2.20 ACMDOWNCNT and ACMUPCNT...............................................................................................C-30C.2.21 FEC_BEF_COR_ER, FEC_COR_BYTE_CNT, and FEC_UNCOR_BLOCK_CNT.....................C-31C.2.22 QPSKWS, QAMWS16, QAMWS32, QAMWS64, QAMWS128, and QAMWS256.....................C-32C.2.23 TPLMAX, TPLMIN, and TPLCUR.................................................................................................C-33C.2.24 RPLMAX, RPLMIN, and RPLCUR................................................................................................C-33C.2.25 BDTMPMAX, BDTMPMIN, and BDTMPCUR.............................................................................C-34C.2.26 OSPITMPMAX, OSPITMPMIN, and OSPITMPCUR....................................................................C-35

D RMON Event Reference.........................................................................................................D-1D.1 List of RMON Alarm Entries........................................................................................................................D-2D.2 List of RMON Performance Entries..............................................................................................................D-2D.3 RMON Alarm Clearance Reference..............................................................................................................D-6

D.3.1 DropEvent.............................................................................................................................................D-6D.3.2 UndersizePkts.......................................................................................................................................D-7D.3.3 OversizePkts.........................................................................................................................................D-8D.3.4 Fragments.............................................................................................................................................D-9D.3.5 Jabbers................................................................................................................................................D-10D.3.6 FCSErrors...........................................................................................................................................D-10

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

E.2.1 Setting the Alarm Severity....................................................................................................................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-6

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



xv

F.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-11H.4 K-O..............................................................................................................................................................H-16H.5 P-T...............................................................................................................................................................H-22H.6 U-Z..............................................................................................................................................................H-30


Maintenance Guide

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

Issue 04 (2010-10-30)

Figures

Figure 1-1 Wearing an ESD wrist strap...............................................................................................................1-5Figure 1-2 Weight lifting......................................................................................................................................1-8Figure 1-3 Schematic diagram of slanting a ladder..............................................................................................1-9Figure 1-4 Schematic diagram of the ladder one meter higher than the eave......................................................1-9Figure 2-1 Toggle lever switch............................................................................................................................2-2Figure 4-1 Main procedure of emergency maintenance.......................................................................................4-3Figure 4-2 Procedure of on-site fault handling.....................................................................................................4-6Figure 5-1 General fault locating procedures.......................................................................................................5-4Figure 5-2 Flow of handling a service interruption..............................................................................................5-6Figure 5-3 Procedure of on-site fault handling.....................................................................................................5-8Figure 5-4 Flow of handling radio link faults....................................................................................................5-15Figure 5-5 Flow of handling bit errors...............................................................................................................5-22Figure 5-6 Flow of troubleshooting the interconnection with the SDH equipment...........................................5-25Figure 5-7 Flow of troubleshooting the interconnection with the PDH equipment...........................................5-28Figure 5-8 Flow of handling Ethernet service faults..........................................................................................5-31Figure 5-9 Flow of handling RMON abnormal performance events.................................................................5-34Figure 5-10 Flow of handling an Ethernet service fault.....................................................................................5-37Figure 5-11 Flow of handling an abnormal RMON performance event............................................................5-40Figure 5-12 Flow of handling pointer justifications...........................................................................................5-44Figure 5-13 Flow of handling orderwire faults..................................................................................................5-47Figure 6-1 Removing a board (1).........................................................................................................................6-4Figure 6-2 Removing a board (2) ........................................................................................................................6-4Figure 6-3 Removing a board (3).........................................................................................................................6-5Figure 6-4 Inserting a board (1)...........................................................................................................................6-5Figure 6-5 Inserting a board (2)...........................................................................................................................6-6Figure 6-6 Inserting a board (3)...........................................................................................................................6-6Figure 6-7 Positions of the jumpers and storage card........................................................................................6-15Figure 6-8 Removing a Storage Card.................................................................................................................6-17Figure 6-9 Installing a Storage Card..................................................................................................................6-18Figure 6-10 Removing the front panel of the fan tray........................................................................................6-20Figure 6-11 Removing the fan tray....................................................................................................................6-20Figure 7-1 CLETOP cassette cleaner...................................................................................................................7-4Figure 7-2 Dragging the fiber tip slightly on one cleaning area...........................................................................7-4

OptiX RTN 620 Radio Transmission SystemMaintenance Guide Figures


xvii

Figure 7-3 Dragging the fiber tip slightly on the other cleaning area..................................................................7-5Figure 7-4 Cleaning the fiber with the lens tissue ...............................................................................................7-6Figure 7-5 Inloop................................................................................................................................................7-17Figure 7-6 Outloop.............................................................................................................................................7-18Figure 7-7 VC-4 path outloop............................................................................................................................7-18Figure 7-8 VC-4 path inloop..............................................................................................................................7-18Figure 7-9 Inloop................................................................................................................................................7-20Figure 7-10 Outloop...........................................................................................................................................7-20Figure 7-11 VC-4 path outloop..........................................................................................................................7-20Figure 7-12 Inloop..............................................................................................................................................7-21Figure 7-13 Outloop...........................................................................................................................................7-22Figure 7-14 Inloop..............................................................................................................................................7-23Figure 7-15 Outloop...........................................................................................................................................7-23Figure 7-16 Inloop..............................................................................................................................................7-23Figure 7-17 Outloop...........................................................................................................................................7-24Figure 7-18 VC-4 path inloop............................................................................................................................7-24Figure 7-19 Inloop..............................................................................................................................................7-25Figure 7-20 VC-3 path inloop............................................................................................................................7-26Figure 7-21 VC-3 path outloop..........................................................................................................................7-26Figure 7-22 Service Trail...................................................................................................................................7-28Figure 7-23 PRBS test in the tributary direction................................................................................................7-31Figure 7-24 PRBS test in the cross-connect direction........................................................................................7-31Figure 7-25 Ethernet test frames between Ethernet boards................................................................................7-38Figure 7-26 Schematic diagram of Ethernet port mirroring...............................................................................7-43Figure 7-27 Uplink mirroring direction..............................................................................................................7-43Figure 7-28 Downlink mirroring direction.........................................................................................................7-44

FiguresOptiX RTN 620 Radio Transmission System

Maintenance Guide

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

Issue 04 (2010-10-30)

Tables

Table 4-1 Description of the main procedure of emergency maintenance...........................................................4-4Table 4-2 Sheet for on-site operations..................................................................................................................4-5Table 4-3 Procedure of on-site fault handling......................................................................................................4-7Table 5-1 Flow description...................................................................................................................................5-5Table 5-2 Flow description...................................................................................................................................5-7Table 5-3 Procedure of on-site fault handling......................................................................................................5-9Table 5-4 Causes of radio link faults..................................................................................................................5-11Table 5-5 Flow description.................................................................................................................................5-16Table 5-6 Causes of bit errors.............................................................................................................................5-21Table 5-7 Flow description.................................................................................................................................5-23Table 5-8 Flow description.................................................................................................................................5-26Table 5-9 Flow description.................................................................................................................................5-29Table 5-10 Flow description...............................................................................................................................5-32Table 5-11 Flow description...............................................................................................................................5-34Table 5-12 Flow description...............................................................................................................................5-38Table 5-13 Flow description...............................................................................................................................5-40Table 5-14 Flow description...............................................................................................................................5-45Table 5-15 Flow description...............................................................................................................................5-48Table 6-1 Part replacement description ...............................................................................................................6-1Table 6-2 Setting the jumpers.............................................................................................................................6-15Table A-1 Alarm list............................................................................................................................................A-2Table B-1 Important abnormal events.................................................................................................................B-2Table C-1 Pointer justification performance events............................................................................................C-2Table C-2 Regenerator section error performance events...................................................................................C-3Table C-3 Multiplex section error performance events.......................................................................................C-3Table C-4 Higher order path error performance events.......................................................................................C-4Table C-5 VC-3 path error performance events..................................................................................................C-5Table C-6 Lower order path error performance events.......................................................................................C-6Table C-7 Line side code violation performance events.....................................................................................C-6Table C-8 Microwave power performance events...............................................................................................C-7Table C-9 FEC performance events....................................................................................................................C-8Table C-10 Performance events regarding radio link bit errors..........................................................................C-8Table C-11 ATPC performance events................................................................................................................C-9

OptiX RTN 620 Radio Transmission SystemMaintenance Guide Tables


xix

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

TablesOptiX RTN 620 Radio Transmission System

Maintenance Guide

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

Issue 04 (2010-10-30)

1 Safety Precautions

1.1 General Safety PrecautionsThe general safety precautions include parts of the safety precautions. Read and follow thesesafety precautions before installing, operating, and maintaining the equipment. This topic alsoprovides guidelines on how to select the appropriate measuring instruments and test devices.

Specific Safety PrecautionsBefore installing, operating, and maintaining the equipment, read through the instructions andprecautions carefully to minimize the possibility of accidents. The Danger, Caution, Warning,and Note items in this document do not cover all the safety precautions that must be followed.They are only parts of the safety precautions as a whole.

Symbols

DANGERIndicates a hazard with a high level of risk that, if not avoided, could result in death or seriousinjury.

WARNINGIndicates a hazard with a medium or low level of risk that, if not avoided, could result in minoror moderate injury.

OptiX RTN 620 Radio Transmission SystemMaintenance Guide 1 Safety Precautions


1-1

CAUTIONIndicates a potentially hazardous situation that, if not avoided, could cause equipment damage,data loss, performance degradation, or unexpected results.

NOTE

Provides additional information to emphasize or supplement important points of the main text.

Local Rules and RegulationsWhen operating the equipment, you must obey the local rules and regulations. The safetyprecautions provided in this document are supplementary and should be in compliance with thelocal safety regulations.

Basic Requirements for InstallationThe installation and maintenance personnel of Huawei equipment must receive strict trainingand be familiar with the proper operation methods and safety precautions before any operation.

l Only the qualified and skilled personnel are allowed to install, operate, and maintain theequipment.

l Only the certified professionals are allowed to remove the safety facilities, and totroubleshoot and maintain the equipment.

l Any replacement or change of the equipment or parts of the equipment (including thesoftware) must be performed by the certified or authorized personnel of Huawei.

l Any fault or error that may cause a safety problem must be reported immediately to theperson in charge.

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

l When installing the equipment, always connect the grounding facilities first. Whenremoving the equipment, always disconnect the grounding facilities last.

l Do not damage the grounding conductor.l Do not operate the equipment in the absence of a suitably installed grounding conductor.l The equipment should be connected to the protection ground permanently. Before operating

the equipment, check the electrical connections of the equipment, and ensure that theequipment is properly grounded.

Human Safetyl Do not operate the equipment and cables in the case of lightning.l To avoid electric shocks, do not connect the safety extra-low voltage (SELV) circuits to

the telephone-network voltage (TNV) circuits.l To prevent laser radiation from injuring your eyes, do not look at the optical port directly.l Before operating the equipment, put on the electrostatic discharge (ESD) work uniforms,

wear ESD gloves or an ESD wrist strap, and take off metallic articles, such as watch,bracelet, and ring, to prevent electric stock or injury of the human body.

1 Safety PrecautionsOptiX RTN 620 Radio Transmission System

Maintenance Guide

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

Issue 04 (2010-10-30)

l In the case of fire, keep away from the building or the area where the equipment is locatedand press the fire alarm system or dial the phone number for a fire call. In this case, do notenter the building which is on fire.

Equipment Safetyl Before operation, install the equipment firmly on the ground or other rigid objects, such as

a wall or a rack.

l When the system is operating, ensure that the ventilation hole is not blocked.

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

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

1.2 Electrical Safety

High Voltage

DANGERl The high-voltage power supply provides the power for the equipment. Direct or indirect

contact of high voltage and mains supply through damp objects may result in fatal danger.

l Non-standard and improper high-voltage operations may result in certain accidents such asfire or electric shock.

l The personnel who perform high-voltage operations must be certified for high-voltage andAC operations.

l The AC cables must be bridged and routed according to the local rules and regulations.

l When operating AC power supply facilities, obey the local rules and regulations.

l When performing high-voltage and AC operations, use special tools rather than generaltools.

l When performing operations in a damp environment, ensure that the equipment is keptaway from water. Switch off the power supply immediately if you find any water in therack or if the rack is damp.

Thunderstorm

DANGERDo not perform operations on high voltage, AC power, iron tower, or backstay in stormy weatherconditions.



1-3

Power Cable

CAUTIONDo not install or remove the power cable with the power on. Transient contact between the coreof the power cable and the conductor may generate electric arc or spark, which may cause fireor injury to the eye.

l Before installing or removing the power cable, switch off the power supply.l Before connecting the power cable, ensure that the power cable and label conform to the

requirements for the installation.

Fuse

CAUTIONIf the fuse on the equipment blows, replace the fuse with a fuse of the same type and specificationsto ensure safe operation of the equipment.

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 generates a static electromagnetic field in the following situations: movingof the human body, friction of the clothes, friction between shoes and the ground, andholding ordinary plastic in hand. The static electromagnetic field will remain within thehuman body for a long time.

l Before operating the equipment, parts, circuit boards, or ASICs, wear an ESD wrist strapthat is properly grounded. The ESD wrist strap can prevent the electrostatic-sensitivecomponents from being damaged by the static electricity in the human body.

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


Maintenance Guide


Issue 04 (2010-10-30)

Figure 1-1 Wearing an ESD wrist strap

1.3 Flammable Air Environment

DANGERDo not place or operate the equipment in an environment where flammable gas, explosive gas,or smog exists.

Operations on any electronic device in an environment where explosive gas exists may causeextreme risks.

1.4 Radiation

Electromagnetic Exposure

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

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



1-5

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.

Forbidden AreaThe following requirements should be met:

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.

Laser

CAUTIONWhen handling optical fibers, do not stand close to, or look into the optical fiber outlet directlywith unaided eyes.

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

In normal cases, viewing an un-terminated fiber or a damaged fiber with the unaided eye atdistances greater than 150 mm does not cause eye injury. Eye injury may occur, however, if anoptical tool such as a microscope, magnifying glass, or eye loupe is used to view the bare fiberend.

To avoid laser radiation, read the following guidelines:

l All the operations should be performed by authorized personnel who have completed theapproved 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 sure

whether the optical source is switched off.


Maintenance Guide


Issue 04 (2010-10-30)

l Use an optical power meter to check and ensure that the optical source is switched off bymeasuring the optical power.

l Before opening the front door of an optical transmission equipment, ensure that you arenot exposed 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.

Read the following instructions before handling fibers:

l Cutting and splicing fibers must be performed by the trained personnel only.

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

1.5 Working at Heights

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

The requirements for working at heights are as follows:

l The personnel who work at heights must be trained.

l The operating machines and tools should be carried and handled safely to prevent themfrom falling down.

l Safety measures, such as wearing a helmet and a safety belt, should 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.

Weight Lifting

CAUTIONDo not enter the areas under the jib arm and the goods in suspension when lifting weight.

l Ensure that the operators have completed the related training and have been certified.

l Check the weight lifting tools and ensure that they are intact.

l Lift the weight only when the weight lifting tools are firmly fixed onto the weight-bearingobject or the wall.

l Use a concise command to prevent any incorrect operation.

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



1-7

Figure 1-2 Weight lifting

Using the LadderChecking the Ladder

l Before using the ladder, check and ensure that the ladder is intact.l Before using the ladder, check the maximum weight that the ladder can support. Overweight

on the ladder is strictly prohibited.

Placing the Ladder

A slant angle of 75 degrees is recommended. The slant can be measured with the angle squareor with arms, as shown in Figure 1-3. When a ladder is used, the wide part of the ladder shouldstand on the ground. Otherwise, take certain protective measures on the base part of the ladderto prevent against sliding. Place the ladder on a rigid ground.


Maintenance Guide


Issue 04 (2010-10-30)

Figure 1-3 Schematic diagram of slanting a ladder

When climbing the ladder, note the following points:

l Ensure that the gravity center of your body does not deviate from the ladder edge.l To lessen the danger and ensure the safety, keep your balance on the ladder before any

operation.l Do not climb higher than the forth highest step of the ladder.

If you intend to climb to the top, the length of the ladder should be at least one meter higher thanthe eave, as shown in Figure 1-4.

Figure 1-4 Schematic diagram of the ladder one meter higher than the eave



1-9

1.6 Mechanical Safety

Drilling Holes

CAUTIONDo not drill holes on the cabinet without prior permission. Improper drilling may cause damageto the internal cables and the EMC function of the cabinet. Metallic scraps produced by thedrilling may fall into the cabinet and cause short circuits of the circuit boards.

l Before drilling a hole on the cabinet, remove the cables inside the cabinet.l During the drilling, ensure that your eyes are protected properly. The flying metallic scraps

may cause injury to your eyes.l Before drilling a hole on the cabinet, wear the protection gloves.l Take measures to prevent the metallic scraps from falling into the cabinet. After the drilling,

clean up the metallic scraps.

Sharp Objects

CAUTIONWhen handling the equipment by hands, wear the protection gloves to avoid injury by sharpobjects.

Fansl When replacing components, ensure that no objects such as components, screws, and tools

fall into a fan that is running, to prevent damage to the fan or equipment.l When replacing the equipment close to a fan, do not put a finger or a board into a fan that

is running before the fan is switched off and stops running, to prevent injury to your handsor damage to the equipment.

Handling Heavy ObjectsWhen handling heavy objects, wear the protection gloves to prevent injury to your hands.

CAUTIONl When handling heavy objects, ensure that the weight bearing measures are taken to prevent

you from being pressed or sprained.l When taking the chassis out from the cabinet, draw attention to the equipment that is unstable

or heavy on the cabinet, to prevent any pressing or smashing injury.


Maintenance Guide


Issue 04 (2010-10-30)

l When handling a chassis, generally, two persons rather than one person are required tohandle a heavy chassis. When handling a chassis, keep your back straight and move gentlyto prevent you from being sprained.

l When moving or lifting a chassis, hold the handle or bottom of the chassis rather than thehandle of a module (such as a power supply module, a fan module, or a board) that hasbeen installed inside the chassis.

1.7 Other Precautions

Removing and Inserting Boards

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

l Insert the board along the guiding slot.

l The contact of board circuits is not allowed to avoid short circuits or scratches.

l Do not touch the circuit, components, connectors, or routing channels of the board toprevent damage caused by electrostatic discharge of the human body to the electrostatic-sensitive components.

Binding Signal Cables

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

Routing Cables

In the case of extremely low temperature, heavy shock or vibration may damage the externalplastic coatings of the cables. The following requirements should be observed to ensure safeimplementation:

l All the cables can be routed only when the ambient temperature is higher than zero degrees.

l If the cables are stored in a place where the ambient temperature is lower than zero degrees,you must transfer them to a place where the ambient temperature is room temperature atleast 24 hours before the operation.

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.



1-11

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.


Maintenance Guide


Issue 04 (2010-10-30)

2 Guides to High-Risk Operations

About This Chapter

This topic describes the operations that easily cause human body injuries and equipment damagein the process of commissioning and maintenance.

2.1 Operation Guide to a Toggle Lever SwitchThe ODU-PWR switch and the SYS-PWR switch are toggle lever switches. When you turn onor turn off the toggle lever switch, perform the operations in strict compliance with the guidelines.Otherwise, the IF board or the power board may be damaged.

2.2 Operation Guide to IF JumpersBefore removing or installing an IF jumper, turn off the ODU-PWR switch. Otherwise, humanbody injuries may be caused, and the IF board or the ODU may be damaged.

2.3 Operation Guide to IF CablesBefore removing or installing an IF cable, turn off the ODU-PWR switch. Otherwise, humanbody injuries may be caused, and the IF board or the ODU may be damaged.

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

OptiX RTN 620 Radio Transmission SystemMaintenance Guide 2 Guides to High-Risk Operations


2-1

2.1 Operation Guide to a Toggle Lever SwitchThe ODU-PWR switch and the SYS-PWR switch are toggle lever switches. When you turn onor turn off the toggle lever switch, perform the operations in strict compliance with the guidelines.Otherwise, the IF board or the power board may be damaged.

Position and Description of the Toggle Lever Switch

A toggle lever switch is used on the power board or IF board to control the power supply to theIDU or ODU. as shown in Figure 2-1.

Figure 2-1 Toggle lever switch

O:OFF

I:ON

Turning On the Toggle Lever Switch

2 Guides to High-Risk OperationsOptiX RTN 620 Radio Transmission System

Maintenance Guide


Issue 04 (2010-10-30)

1. Pull the toggle lever switch out slightly.2. Turn it to the left.3. Release the toggle lever switch.

Turning Off the Toggle Lever Switch

1. Pull the toggle lever switch out slightly.2. Turn it to the right.3. Release the toggle lever switch.

2.2 Operation Guide to IF JumpersBefore removing or installing an IF jumper, turn off the ODU-PWR switch. Otherwise, humanbody injuries may 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 aToggle Lever Switch.



2-3

21

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

Step 2 Remove or install an IF jumper.

----End

2.3 Operation Guide to IF CablesBefore removing or installing an IF cable, turn off the ODU-PWR switch. Otherwise, humanbody injuries may be caused, and the IF board or the ODU may be damaged.

Procedure



Maintenance Guide


Issue 04 (2010-10-30)

21

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

Step 2 Install or remove an IF cable.

----End

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

Procedure




2-5

321

3

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

Step 2 Disconnect the IF jumper or IF cable.

Step 3 Remove or install an IF board.

----End


Maintenance Guide


Issue 04 (2010-10-30)

3 Routine Maintenance

About This Chapter

The aim of routine maintenance is to detect and rectify latent faults in time before the equipmentbecomes faulty and services are affected.

3.1 Routine Maintenance ItemsRoutine maintenance items are classified into the routine maintenance items carried out throughthe network management system (NMS), field maintenance items for indoor equipment, andfield maintenance items for outdoor equipment.

3.2 Guidelines for Routine Maintenance ItemsThis topic describes the guidelines for each routine maintenance item.

OptiX RTN 620 Radio Transmission SystemMaintenance Guide 3 Routine Maintenance


3-1

3.1 Routine Maintenance ItemsRoutine maintenance items are classified into the routine maintenance items carried out throughthe network management system (NMS), field maintenance items for indoor equipment, andfield maintenance items for outdoor equipment.

Routine Maintenance Items Carried Out Through the NMSMaintenance Item Recomm

endedCycle

Remarks

3.2.1 Checking the Status of NEs Every day -

3.2.2 Browsing the Current Alarms Every day -

3.2.3 Browsing the History Alarms Everyweek

-

3.2.4 Browsing the Abnormal Events Everyweek

-

3.2.5 Browsing the CurrentPerformance

Everyweek

-

3.2.6 Browsing the HistoryPerformance

Everyweek

-

3.2.7 Browsing the History TransmitPower and Receive Power

Everyweek

-

3.2.8 Testing IF 1+1 Switching Half ayear

Applies to only the equipment that isconfigured in 1+1 protection mode.During the 1+1 protection switchingtime (<500 ms), the protected servicesare interrupted. Hence, it isrecommended that you perform 1+1protection switching when the trafficis light.

3.2.9 Testing IF N+1 Switching Half ayear

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

3.2.10 Testing Two-FiberBidirectional MSP Ring Switching

Half ayear

-

Field Maintenance Items for Indoor EquipmentMaintenance Item Recommended Cycle Remarks

3.2.11 Cleaning the AirFilter

Every two months -

3 Routine MaintenanceOptiX RTN 620 Radio Transmission System

Maintenance Guide


Issue 04 (2010-10-30)

Maintenance Item Recommended Cycle Remarks

3.2.12 Checking theEquipment Room

Every two months -

Field Maintenance Items for Outdoor Equipment

Maintenance Item RecommendedCycle

Remarks

3.2.13 Checking the ODU Half a year Perform acomplete checkafter a level-8 orhigher-levelhurricane, anearthquake, orother exceptionalcircumstances.

3.2.14 Checking the Hybrid Coupler Half a year

3.2.15 Checking the Antenna Half a year

3.2.16 Checking the IF Cables Half a year

3.2.17 Checking the LOS Condition Half a year

3.2 Guidelines for Routine Maintenance ItemsThis topic describes the guidelines for each routine maintenance item.

3.2.1 Checking the Status of NEsBy checking the NE status periodically, you can detect the abnormal statuses of one or moreNEs in time.

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

3.2.3 Browsing the History 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 EventsAn abnormal event refers to an exception that arises in the system at a particular time. Bybrowsing the abnormal events periodically, you can find the exceptions that occur in theequipment in time.

3.2.5 Browsing the Current PerformanceThe counter of current performance events measures all the performance events that arisebetween the start time of the monitoring period and the current time. By browsing the currentperformance events periodically, you can learn about the performance change of the equipmentin time. Hence, you can detect the latent hazards in time when the performance of the equipmentstarts to degrade.

3.2.6 Browsing the History PerformanceA history alarm is an alarm that is cleared. By browsing and saving the history performanceevents periodically, you can provide fault locating information for troubleshooting.



3-3

3.2.7 Browsing the History Transmit Power and Receive PowerBy browsing the history transmit power and receive power periodically, you can learn about thechange trend of the transmit power and receive power, which provides a reference fortroubleshooting radio links.

3.2.8 Testing IF 1+1 SwitchingBy testing IF 1+1 switching periodically, you can check whether the equipment is normallyswitched over.

3.2.9 Testing IF N+1 SwitchingBy testing IF N+1 switching periodically, you can check whether the equipment is normallyswitched over.

3.2.10 Testing Two-Fiber Bidirectional MSP Ring SwitchingBy testing two-fiber bidirectional MSP ring switching periodically, you can check whether theequipment is normally switched over.

3.2.11 Cleaning the Air FilterPeriodically checking the air filter ensures that the air intake path of the fans is not blocked andthus prevents excessively high board temperature caused by degraded heat dissipation.

3.2.12 Checking the Equipment RoomPeriodically checking the equipment room not only ensures that the equipment can operatenormally at appropriate temperature and humidity conditions, but also reduces the fault rate, andincreases the service life of the equipment.

3.2.13 Checking the ODUBy checking an ODU periodically, you can detect faults and latent hazards of the ODU in time.

3.2.14 Checking the Hybrid CouplerBy checking a hybrid coupler periodically, you can detect faults and latent hazards of the hybridcoupler in time.

3.2.15 Checking the AntennaBy checking an antenna periodically, you can detect faults and latent hazards of the antenna intime.

3.2.16 Checking the IF CablesBy checking the IF cables periodically, you can detect faults and latent hazards of the IF cablesin time.

3.2.17 Checking the LOS ConditionBy checking the LOS condition of the transmission link periodically, you can detect latent LOSfaults on the transmission link in time.

3.2.1 Checking the Status of NEsBy checking the NE status periodically, you can detect the abnormal statuses of one or moreNEs in time.

PrerequisiteThe NE user must have the authority of NE monitor or higher.

Tools, Instruments, and MaterialsWeb LCT


Maintenance Guide


Issue 04 (2010-10-30)

Procedure

Step 1 In NE List, query Communication Status of an NE. Communication Status needs to beNormal.

Step 2 Check Login Status of an NE. If the Login Status column of an NE is Not Logged In, log into the NE.1. Select an NE, and then click NE Login.

The NE Login dialog box is displayed.2. Enter a user name in User Name and a password in Password.

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

NOTE

The user lct has the authority at the system level.

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

----End

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



Procedure

Step 1 In the NE Explorer, select the required NE from the Object Tree, and then click the icon onthe toolbar.

TIP

You can also click an alarm indicator on the toolbar to display the alarms of the specific severity.

From left to right, the alarm indicators and corresponding alarm severities are as follows:

l Red: critical alarm

l Orange: major alarm

l Yellow: minor alarm

l Purple: warning

l Light blue: abnormal event

The Browse Current Alarms tab is displayed by default.

Step 2 Browse the displayed alarms.



3-5

Step 3 If there are newly generated alarms after the last maintenance, select the newly generated alarms,record the details of these newly generated alarms, and then notify the troubleshooting personnelto clear these alarms in time.For details about how to handle an alarm, refer to A Alarm Reference.

Step 4 Optional: Click Save As.

A text file that lists the current alarms is displayed in the IE system.

NOTE

You can save and archive the text file as required.

----End

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

Prerequisite

The NE user must have the authority of NE monitor or higher.

Tools, Instruments, and Materials

Web LCT

Procedure

Step 1 In the NE Explorer, select the required NE from the Object Tree, and then click the icon onthe toolbar.

Step 2 Click the Browse History Alarms tab.

Step 3 Click Filter.The Filter dialog box is displayed.

Step 4 Specify Rising Time and Cleared Time, and then click Filter.The time span starts from the time when the last history alarm browsing operation was performedto the current time.

Step 5 Browse the filtered history alarms.

Step 6 Click Save As.

A text file that lists the history alarms is displayed in the IE system.

NOTE


----End


Maintenance Guide


Issue 04 (2010-10-30)

3.2.4 Browsing the Abnormal EventsAn abnormal event refers to an exception that arises in the system at a particular time. Bybrowsing the abnormal events periodically, you can find the exceptions that occur in theequipment in time.

Prerequisite



Web LCT

Procedure

Step 1 In the NE Explorer, select the required NE from the Object Tree, and then choose Alarm >Browse Abnormal Events from the Function Tree.

TIP

In the NE Explorer, you can also select the required NE from the Object Tree and click the icon tonavigate to the Browse Abnormal Events tab.

Step 2 Click Filter.The Filter dialog box is displayed.

Step 3 In the Abnormal Event combo box, select Select All, and then click OK.

Step 4 Browse the displayed abnormal events.

For details on how to handle an abnormal event, see B Abnormal Event Reference.


A text file that lists the abnormal events is displayed in the IE system.

NOTE


----End

Related Information

An abnormal event refers to an exception that arises in the system at a particular time rather thanpersists for a period. Being different from alarms, an abnormal event has the occurrence timerather than the clearance time.

3.2.5 Browsing the Current PerformanceThe counter of current performance events measures all the performance events that arisebetween the start time of the monitoring period and the current time. By browsing the currentperformance events periodically, you can learn about the performance change of the equipmentin time. Hence, you can detect the latent hazards in time when the performance of the equipmentstarts to degrade.



3-7

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

enable the performance monitoring function, see 7.13 Configuring PerformanceMonitoring Status of NEs.

l The NE user must have the authority of NE monitor or higher.


Web LCT

Procedure

Step 1 In the NE Explorer, select the required board, and then choose Performance > CurrentPerformance from the Function Tree.

Step 2 Select All in Monitored Object Filter Condition.

Step 3 Select 15-Minute next to Monitor Period.

Step 4 Select all the available performance events in Count, and select Consecutive Severely ErroredSecond in Display Options.

Step 5 Click Query.

Step 6 Browse the displayed performance events.In normal cases, no bit error performance events are displayed, and the number of pointerjustification events is less than six per day on each port.

Step 7 Select all the available performance events in Gauge, and select Current Value and Maximum/Minimum Value in Display Options.

Step 8 Click Query.

Step 9 Browse the displayed performance events.Compared with the history records, the gauge indicators, such as board temperature, do notchange drastically.

Step 10 Select 24-Hour next to Monitor Period.

Step 11 Repeat Step 4 to Step 9 to query the current performance events in a period of 24 hours.

----End

3.2.6 Browsing the History PerformanceA history alarm is an alarm that is cleared. By browsing and saving the history performanceevents periodically, you can provide fault locating information for troubleshooting.





Maintenance Guide


Issue 04 (2010-10-30)


Web LCT

Procedure

Step 1 In the NE Explorer, select the requried board, and then choose Performance > HistoryPerformance from the Function Tree.



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

Step 5 Select all the available performance events in Count.

Step 6 Click Query to browse the history performance events.


A text file that lists the history performance events is displayed in the IE system.

NOTE






NOTE



Step 12 Repeat Step 4 to Step 10 to query the history performance events in a period of 24 hours.


----End

3.2.7 Browsing the History Transmit Power and Receive PowerBy browsing the history transmit power and receive power periodically, you can learn about thechange trend of the transmit power and receive power, which provides a reference fortroubleshooting radio links.



3-9





Web LCT

Procedure

Step 1 In the NE Explorer, select the required ODU for the history transmit power and receive power,and then choose Configuration > Performance Graph Analyse from the Function Tree.

Step 2 Specify the start time and end time of a time span.The time span starts from the last routing maintenance time to the current time.

Step 3 Set CounterType to 15M.

Step 4 Click Drawing.The history transmit and receive power curve of the ODU in the specified time span is displayed.

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

----End

3.2.8 Testing IF 1+1 SwitchingBy testing IF 1+1 switching periodically, you can check whether the equipment is normallyswitched over.

Prerequisite



Precautionsl This task carries out IF 1+1 switching in manual switching mode, which is used for

equipment switching (that is, HSB switching). During the 1+1 protection switching time(< 500 ms), the protected services are interrupted. Hence, it is recommended that youperform IF 1+1 protection switching when the traffic is light.

l Before you perform the switching, ensure that the standby equipment works properly. Ifthe switching fails, contact Huawei engineers for further assistance.


Maintenance Guide


Issue 04 (2010-10-30)

Procedure

Step 1 In the NE Explorer, select the required NE from the Object Tree, and then chooseConfiguration > Link Configuration from the Function Tree.

Step 2 Click the IF 1+1 Protection tab.

Step 3 In Protection Group, select the protection group for IF 1+1 switching.

Step 4 In Slot Mapping Relation, right-click an IF board and choose Manual Switch to from theshortcut menu.

Step 5 Click OK to start the protection switching.

Step 6 Click Query to check the protection switching status.After the switching is completed, Switching Status of Device in Protection Group changes toManual Switching, and the current board functions as the standby board.

Step 7 After the equipment works for a period of time, query the current alarms and performance eventsof the service.There should be no new alarms or bit error performance events.

Step 8 Repeat Step 1 to Step 3.

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

Step 10 Click OK to restore the protection switching.

Step 11 Click Query to check the protection switching status.After the switching is completed, Switching Status of Device in Protection Group changes toAutomatic Switching.

Step 12 After the equipment runs properly for a period of time, query the current alarms and performanceevents.There should be no new alarms or performance events.

----End

3.2.9 Testing IF N+1 SwitchingBy testing IF N+1 switching periodically, you can check whether the equipment is normallyswitched over.

Prerequisite



Precautionsl This task carries out IF N+1 switching in exercise switching mode to check whether an NE

can run the N+1 protocol properly. Therefore, the service is not switched over.



3-11

l Before you perform the switching, ensure that the standby equipment works properly. Ifthe switching fails, contact Huawei engineers for further assistance.

Procedure

Step 1 In the NE Explorer, select the required NE from the Object Tree, and then chooseConfiguration > Link Configuration from the Function Tree.

Step 2 Click the N+1 Protection tab.

Step 3 In the Slot Mapping Relation window, right-click a working unit, and then choose ExerciseSwitching from the shortcut menu.A prompt dialog box is displayed, indicating that the command is delivered successfully.

Step 4 Click OK.

Step 5 Click Query to query the status of protection switching.The status of the switched working unit should be Exercise Switching.


Step 7 In the Slot Mapping Relation window, right-click a protection or working unit, and then chooseClear from the shortcut menu.

Step 8 Click OK.

Step 9 Click Query to query the status of protection switching.The status of the switched working unit should be Normal.

----End

3.2.10 Testing Two-Fiber Bidirectional MSP Ring SwitchingBy testing two-fiber bidirectional MSP ring switching periodically, you can check whether theequipment is normally switched over.

Prerequisite



Precautionsl This task carries out two-fiber bidirectional MSP ring switching in exercise switching mode

to check whether an NE can run the MSP protocol properly. Therefore, the service is notswitched over.

l Before you perform MSP ring switching, ensure that the standby equipment works properly.If the switching fails, contact Huawei engineers for further assistance.


Maintenance Guide


Issue 04 (2010-10-30)

ProcedureStep 1 In the NE Explorer, select the required NE from the Object Tree, and then choose

Configuration > Ring MS from the Function Tree.

Step 2 In Protection Group, select the protection group for exercise switching.

Step 3 In Slot Mapping Relation, right-click East Line and choose Ring Exercise from the shortcutmenu.

Step 4 Click Query to query the protection switching status. Switching Status of the east line boardchanges to Excise Ring Switching.

Step 5 Select and right-click the line direction for exercise switching and choose Clear RingExercise from the shortcut menu.

Step 6 Click Query to query the protection switching status. Switching Status of the east line boardchanges to Normal.

Step 7 In Slot Mapping Relation, right-click West Line of the selected protection group in Step 2 andchoose Ring Exercise from the shortcut menu.


----End

3.2.11 Cleaning the Air FilterPeriodically checking the air filter ensures that the air intake path of the fans is not blocked andthus prevents excessively high board temperature caused by degraded heat dissipation.

PrerequisiteNone.

Tools, Instruments, and MaterialsAn air blower or a clean brush

ProcedureStep 1 Loosen the captive screws on the panel of the fan Tray.

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

Step 3 Draw out the air filter at the left side.



3-13

Step 4 Use an air blower or a clean brush to clean the air filter.

Step 5 After the cleaning, insert the air filter back to its original position.

Step 6 Tighten the screws on the panel of the fan Tray.

----End

3.2.12 Checking the Equipment RoomPeriodically checking the equipment room not only ensures that the equipment can operatenormally at appropriate temperature and humidity conditions, but also reduces the fault rate, andincreases the service life of the equipment.

PrerequisiteNone.


None.

Procedure

Step 1 Record the reading of the thermometer in the equipment room.The normal temperature ranges from -5°C to +55°C

Step 2 Record the reading of the humidity meter in the equipment room.The normal humidity ranges from 5% to 95%.

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

l Certain portable foam fire extinguishers are available in the equipment room and theseextinguishers need to be within their service life.

l No rain leakage or water penetration is found in the equipment room.

l No mice or insects are found in the equipment room.

Step 4 Clean the equipment room.Ensure that the cabinets, equipment shelves, equipment, desks, and floors are clean. Theequipment needs to be tidy.

----End

3.2.13 Checking the ODUBy checking an ODU periodically, you can detect faults and latent hazards of the ODU in time.

PrerequisiteNone.


Maintenance Guide


Issue 04 (2010-10-30)

Tools, Instruments, and MaterialsNone.

ProcedureStep 1 Ensure that the ODU is located within the protected area of a lightning arrester.

In the case of plain areas, a lightning arrester protects an area that is located within an angle of45° under the lightning arrester. In the case of mountainous areas and the areas where lightningfrequently occurs, a lightning arrester protects an area that is located within an angle of 30° underthe lightning arrester.

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

Step 3 Ensure that the ODU is not damaged.

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

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

----End

3.2.14 Checking the Hybrid CouplerBy checking a hybrid coupler periodically, you can detect faults and latent hazards of the hybridcoupler in time.

PrerequisiteNone.


ProcedureStep 1 Ensure that the hybrid coupler is located within the protected area of the lightning arrester.

In the case of plain areas, a lightning arrester protects an area that is located within an angle of45° under the lightning arrester. In the case of mountainous areas and the areas where lightningfrequently occurs, a lightning arrester protects the area that is located within an angle of 30°under the lightning arrester.

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

Step 3 Ensure that the coupler is not damaged.

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

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

----End

3.2.15 Checking the AntennaBy checking an antenna periodically, you can detect faults and latent hazards of the antenna intime.



3-15

PrerequisiteNone.


Procedure

Step 1 Ensure that the antenna is located within the protected area of the lightning arrester.In the case of plain areas, a lightning arrester protects an area that is located within an angle of45° under lightning arrester. In the case of mountainous areas and the areas where lightningfrequently occurs, a lightning arrester protects an area that is located within an angle of 30° underthe lightning arrester.

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

Step 3 Ensure that the antenna radome is not damaged.

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

Step 5 Check whether the fastening bolts on the antenna are loose. Check whether the antenna slantsfrom the original position. Ensure that the azimuth angle and the elevation angle of the antennameet the design requirements.

Step 6 In the case of split mounting, ensure that the installation parts (ODU adapter, antenna adapter,and flexible waveguide) are installed firmly, and that the connectors are fastened.

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

----End

3.2.16 Checking the IF CablesBy checking the IF cables periodically, you can detect faults and latent hazards of the IF cablesin time.

PrerequisiteNone.


Procedure

Step 1 Check the cables.l No cables are bent or twisted.l No bare copper wires are found.l The bending radius of a cable needs to greater than 30 cm.l The IF cables are bound in accordance with IF Cable Routing and Binding Specifications

specified in the Installation Reference. The feeder clip or binding strap is not loosen.


Maintenance Guide


Issue 04 (2010-10-30)

Step 2 Check the cable connectors.l The cable connector needs to be connected reliably to the ODU.l The cable connector needs to be waterproof.

Step 3 Check the grounding of the cables.l The grounding clip needs to be waterproof.l The grounding cable needs to be routed from top downwards. The angle between the

grounding cable and an IF cable needs to be not more than 15 degrees.

----End

3.2.17 Checking the LOS ConditionBy checking the LOS condition of the transmission link periodically, you can detect latent LOSfaults on the transmission link in time.

PrerequisiteNone.

Tools, Instruments, 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 maintains exist on the transmission link, which may block the LOS.

Step 2 Check whether the spanning tree in the transmission path is blocked.

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

----End



3-17

4 Emergency Maintenance

About This Chapter

Emergency maintenance is performed when emergencies occur or possible emergencies owingto natural factors may occur during the operation of the equipment.

4.1 Definition of EmergencyIn the case of the microwave equipment, an emergency situation is where the microwave servicesare interrupted.

4.2 Purposes of Emergence MaintenanceEmergency maintenance is performed to restore the normal operation of a system or a devicerapidly. This is different from troubleshooting, which helps 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 thathandles faults on site.

OptiX RTN 620 Radio Transmission SystemMaintenance Guide 4 Emergency Maintenance


4-1

4.1 Definition of EmergencyIn the case of the microwave equipment, an emergency situation is where the microwave servicesare interrupted.

4.2 Purposes of Emergence MaintenanceEmergency maintenance is performed to restore the normal operation of a system or a devicerapidly. This is different from troubleshooting, which helps 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 thathandles faults on site.

NOTE

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

4 Emergency MaintenanceOptiX RTN 620 Radio Transmission System

Maintenance Guide


Issue 04 (2010-10-30)

Main Procedure of Emergency Maintenance

Figure 4-1 Main procedure of emergency maintenance

Start

Is there anincorrect operation? Cancel the operation

Is there any backuptransmission resource?

Switch the service tothe backup resource

Is the power down Contact the powersupply engineer

Troubleshoot theswitching failure

Proceed to the nextstep

Is the servicerestored?

Is the service restored? Contact Huaweiengineers

Check thetroubleshooting result

End

Is there any alarm onthe NE? Clear the alarm

1

2

Yes

Yes

Yes

Yes

Yes

No

No

No

No

No

Yes

Yes

No

Yes Troubleshoot theinterconnection fault

No

No

3

Yes

No

4Is the Ethernet

service interrupted

5

Is the serviceconfigured with

protection

Is theinterconnection

faulty?

Troubleshoot theEthernet service fault

Locate the fault byperforming loopback

operations section by section

6



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 configurationsl Performing loopback operationsl Shutting down the laserl Muting the ODUl Changing boards/cablesl Loading software

2 Check the notice issued by associated departments, and check whether thereare any external factors that may cause service faults, such as faults in thepower supply, cables, environment, and terminal equipment (such asswitching devices).

3 See 7.3.1 Checking the NE Status and 7.3.3 Browsing the CurrentAlarms.

4 The following alarms can be cleared through theNM:APS_MANUAL_STOP, ALM_GFP_dLFD, APS_FAIL,BD_NOT_INSTALLED, DBMS_ERROR, ESN_INVALID, FCS_ERR,HP_TIM, HP_UNEQ, J0_MM, LOOP_ALM, LPS_UNI_BI_M,LP_SIZE_ERR, LP_SLM, LP_SLM_VC12, LP_SLM_VC3, LP_TIM,LP_TIM_VC12, LP_TIM_VC3, LP_UNEQ, LP_UNEQ_VC12,LP_UNEQ_VC3, MSSW_DIFFERENT, NESF_LOST,NESTATE_INSTALL, NO_BD_SOFT, RADIO_MUTE,WRG_BD_TYPE, and WRG_DEV_TYPE.

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

6 After the fault is handled, proceed as follows:1. Check the alarms, and ensure that the system is running smoothly.2. Arrange personnel to watch and guard the system during the peak service

hours, and be sure to solve the problems promptly, if any.3. Fill in the sheet for on-site operations, record the fault symptoms and

handling results, and then send them to Huawei. Table 4-2 shows the sheetfor on-site operations.


Maintenance Guide


Issue 04 (2010-10-30)

Table 4-2 Sheet for on-site operations

Maintained on maintained by

Actual Step Step in the WholeProcedure

Handling Result Remarks



4-5

Procedure of On-Site Fault Handling

Figure 4-2 Procedure of on-site fault handling

Equipmentalarm?

3

No

4

YesClear the alarm

YesClear the alarm

No

5 YesClear the alarm

No


No

End



Yes

No

Start

Obviousequipmentdamage?

Yes Repair or replacethe equipment

No Troubleshoot thepower input

Browse alarmslocally by using the

Web 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 PXC on?

High orderpath alarm?

Low orderpath alarm?

Faulty inter-connection with SDH/

PDH equipment?

Ethernetservice fault?


Maintenance Guide


Issue 04 (2010-10-30)

Table 4-3 Procedure of on-site fault handling

CommentNo.

Description

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

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

2. Check the power cables, especially the power connectors, and replace thepower cables or re-make power connectors if required.

3. Check the voltage and polarization of the input power. If the voltage orpolarization of the input power does not meet the requirements, contactthe power engineers and handle the fault.

NOTEFor detailed specifications of the fuse capacity and input power, refer to the topic of"Powering On the Equipment" in the Commissioning Guide.

2 The handling procedure is as follows:1. Refer to the Commissioning Guide and Connecting the Web LCT to the

IDU.2. Refer to the Configuration Guide and Creating NEs by Using the Search

Method.3. Refer to Commissioning Guide, and Checking Alarms.NOTE

If you fail to log in to a created NE, ensure that the operations you performed are correct,and then identify and rectify the fault according to the indicators of the PXC and SCC.For details about the indicators, refer to the IDU Hardware Description.

3 Pay special attention to the following alarms:l HARD_BADl POWER_ALMl FAN_FAILl BD_STATUSl SYN_BADl NESF_LOSTl TEMP_ALARMl RADIO_RSL_HIGHl RADIO_RSL_LOWl RADIO_TSL_HIGHl RADIO_TSL_LOWl IF_INPWR_ABNl IF_CABLE_OPENl VOLT_LOS



4-7

CommentNo.

Description

4 Pay special attention to the following alarms:l MW_LIMl MW_LOFl R_LOSl R_LOFl R_LOCl MS_AISl AU_AISl AU_LOPl B1_EXCl B2_EXC

5 Pay special attention to the following alarms:l HP_LOMl B3_EXCl HP_UNEQ

6 Pay special attention to the following alarms:l TU_AISl TU_LOPl BIP_EXCl P_LOSl LP_UNEQl T_ALOSl E1_LOC

7 See 5.5 Troubleshooting the Interconnection with the SDH Equipment or5.6 Troubleshooting the Interconnection with the PDH Equipment.

8 See 5.7 Troubleshooting SDH/PDH Radio-Based Ethernet ServiceFaults or 5.8 Troubleshooting Faults in Hybrid Radio-Based EthernetServices.


Maintenance Guide


Issue 04 (2010-10-30)

5 Troubleshooting

About This Chapter

This guide describes the general troubleshooting procedures for the OptiX RTN 620 and providestroubleshooting methods for common faults.

5.1 General Troubleshooting ProcedureWhen handling a fault, make a detailed record of the fault phenomenon. 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 InterruptionThe service interruption fault indicates the service transmission failure due to an equipment faultor a link fault.

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

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

5.5 Troubleshooting the Interconnection with the SDH EquipmentIn the case that the NE is interconnected with the SDH equipment, if the SDH service cannot betransmitted between the equipment sets, there is an interconnection fault.

5.6 Troubleshooting the Interconnection with the PDH EquipmentIn the case that the OptiX RTN equipment is interconnected with the PDH equipment, if thePDH service cannot be transmitted between the equipment sets, there is an interconnection fault.

5.7 Troubleshooting SDH/PDH Radio-Based Ethernet Service FaultsEoS/EoPDH-based Ethernet services can be transmitted through SDH/PDH radio networks orTDM networks. The associated service faults include Ethernet service interruption and Ethernetservice degradation.

5.8 Troubleshooting Faults in Hybrid Radio-Based Ethernet ServicesHybrid radio-based Ethernet services can be transmitted over Hybrid radio networks but cannottraverse a TDM network. The associated faults include Ethernet service interruption and Ethernetservice degradation.

OptiX RTN 620 Radio Transmission SystemMaintenance Guide 5 Troubleshooting


5-1

5.9 Troubleshooting Pointer JustificationsWhen an NE reports a large amount of justification events of the administrative unit (AU) pointeror the tributary unit (TU) pointer, there are pointer justification faults.

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

5 TroubleshootingOptiX RTN 620 Radio Transmission System

Maintenance Guide


Issue 04 (2010-10-30)

5.1 General Troubleshooting ProcedureWhen handling a fault, make a detailed record of the fault phenomenon. 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

Figure 5-1 General fault locating procedures

Start

Record the fault phenomenon

Analyze fault causes and locatethe fault

Is the fault cleared?

Report to Huawei

Make a solution together

Attempt to clear the fault

Is the service restored?

Observe the operating


Fill in the fault handling report

End

Other handling procedures

1

3

4

No

Yes

Yes

Yes

No

No

No

Caused by external factors?2

Yes


Maintenance Guide


Issue 04 (2010-10-30)

Table 5-1 Flow description

Note Description

1 When recording the fault phenomenon, makea true and detailed record of the entire processof the fault. Record the exact time when thefault occurs, and the operations performedbefore and after the fault occurs. Save thealarms, performance events, and otherimportant information.

2 Check the notice issued by associateddepartments, and check whether there are anyexternal factors that may cause service faults,such as faults in the power supply, cables,environment, and terminal equipment (suchas switching devices).

3 If the fault is caused by the equipment, referto 5.2 Troubleshooting ServiceInterruption.

4 The customers in China can contact our 24-hour technical support center at400-830-2118, and the customers in areasoutside China can contact the local Huaweioffices.

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

Fault Causesl The operation is improper.

If the configuration data changes, the loopback occurs, or the board/cable is replaced, theservices may be interrupted.

l The transmission NE or link is faulty.l The interconnection is improper.

If the transmission equipment functions properly and the connection is proper, checkwhether the interconnection between the transmission equipment is proper and whether theswitching equipment is faulty.

Fault Locating Methods1. Check whether an abnormal operation causes the service interruption by performing a

loopback on the previous operations.2. Query alarms on the centralized NMS or the NMS on the site, and then locate the fault

based on the alarm analysis.



5-5

If multiple nodes report the alarm, analyze the alarms reported by the nodes in the sequenceof equipment alarms, line alarms, higher order path alarms, and lower order path alarms.

3. If the fault cannot be located through the alarm analysis method, locate the fault by loopbacksection by section and part replacement.

CAUTIONIf the fault cannot be rectified immediately, focus on the service recovery. You can recover theservices by adjusting the service route or performing forced switching as soon as possible.

Fault Locating Procedure

Figure 5-2 Flow of handling a service interruption

End

Service interruptedby external causes?

Maloperation

NE accesssuccessful and alarm

cleared?

Rectify the fault on site

Query NE status andalarm by using the

NMS

Contact relateddepartments to

handle the problem

Cancel the operation

Start

Handle the alarm

Go to the next step Servicerestored?

Yes

No

1

2

3

4

No

Yes

Yes

Yes

No

No


Maintenance Guide


Issue 04 (2010-10-30)


Note Description

1 The common abnormal operations are as follows:l Modifying the data configurationl Loopbackl Shutting down the laserl Muting the ODUl Replacing the board/cable.l Loading the software

2 Check the notice issued by associated departments, and check whether thereare any external factors that may cause service faults, such as faults in thepower supply, cables, environment, and terminal equipment (such asswitching devices).

3 See 3.2.1 Checking the Status of NEs and 3.2.2 Browsing the CurrentAlarms.

4 The alarms that can be cleared through the operations on the NMS are asfollows: APS_MANUAL_STOP, ALM_GFP_dLFD, APS_FAIL,BD_NOT_INSTALLED, DBMS_ERROR, ESN_INVALID, FCS_ERR,HP_TIM, HP_UNEQ, J0_MM, LOOP_ALM, LPS_UNI_BI_M,LP_SIZE_ERR, LP_SLM, LP_SLM_VC12, LP_SLM_VC3, LP_TIM,LP_TIM_VC12, LP_TIM_VC3, LP_UNEQ, LP_UNEQ_VC12,LP_UNEQ_VC3, MSSW_DIFFERENT, NESF_LOST,NESTATE_INSTALL, NO_BD_SOFT, RADIO_MUTE,WRG_BD_TYPE, and WRG_DEV_TYPE.



5-7

Figure 5-3 Procedure of on-site fault handling

Equipmentalarm?

3

No

4

YesClear the alarm

YesClear the alarm

No


No


No

End



Yes

No

Start

Obviousequipmentdamage?

Yes Repair or replacethe equipment

No Troubleshoot thepower input

Browse alarmslocally by using the

Web 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 PXC on?

High orderpath alarm?

Low orderpath alarm?

Faulty inter-connection with SDH/

PDH equipment?

Ethernetservice fault?


Maintenance Guide


Issue 04 (2010-10-30)

Table 5-3 Procedure of on-site fault handling

CommentNo.

Description

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

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

2. Check the power cables, especially the power connectors, and replace thepower cables or re-make power connectors if required.

3. Check the voltage and polarization of the input power. If the voltage orpolarization of the input power does not meet the requirements, contactthe power engineers and handle the fault.

NOTEFor detailed specifications of the fuse capacity and input power, refer to the topic of"Powering On the Equipment" in the Commissioning Guide.

2 The handling procedure is as follows:1. Refer to the Commissioning Guide and Connecting the Web LCT to the

IDU.2. Refer to the Configuration Guide and Creating NEs by Using the Search

Method.3. Refer to Commissioning Guide, and Checking Alarms.NOTE

If you fail to log in to a created NE, ensure that the operations you performed are correct,and then identify and rectify the fault according to the indicators of the PXC and SCC.For details about the indicators, refer to the IDU Hardware Description.

3 Pay special attention to the following alarms:l HARD_BADl POWER_ALMl FAN_FAILl BD_STATUSl SYN_BADl NESF_LOSTl TEMP_ALARMl RADIO_RSL_HIGHl RADIO_RSL_LOWl RADIO_TSL_HIGHl RADIO_TSL_LOWl IF_INPWR_ABNl IF_CABLE_OPENl VOLT_LOS



5-9

CommentNo.

Description

4 Pay special attention to the following alarms:l MW_LIMl MW_LOFl R_LOSl R_LOFl R_LOCl MS_AISl AU_AISl AU_LOPl B1_EXCl B2_EXC

5 Pay special attention to the following alarms:l HP_LOMl B3_EXCl HP_UNEQ

6 Pay special attention to the following alarms:l TU_AISl TU_LOPl BIP_EXCl P_LOSl LP_UNEQl T_ALOSl E1_LOC

7 See 5.5 Troubleshooting the Interconnection with the SDH Equipment or5.6 Troubleshooting the Interconnection with the PDH Equipment.

8 See 5.7 Troubleshooting SDH/PDH Radio-Based Ethernet ServiceFaults or 5.8 Troubleshooting Faults in Hybrid Radio-Based EthernetServices.

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

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


Maintenance Guide


Issue 04 (2010-10-30)

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

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

l RADIO_TSL_HIGHl RADIO_TSL_LOWl TSL_CURl TSL_MAXl TSL_MINl TSL_AVG

NOTE

For a detailed description of the range of the transmit power, refer to the Product Description.

In the following two cases, the RSL is abnormal. The first case is that the receive power is lowerthan the normal value (Normal value = Planned value - 3 dB). The second case is that the receivepower is lower than the receiver sensitivity or higher than the free space receive power due tofading. The relevant alarms and performance events are as follows:

l RADIO_RSL_HIGHl RADIO_RSL_LOWl RSL_CURl RSL_MAXl RSL_MINl RSL_AVG

NOTE

For a detailed description of the receiver sensitivity, refer to the Product Description.

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

l Co-channel interference is crosstalk from two different radio transmitters reusing the samefrequency channel. Therefore, the entire spectrum may be impaired.

l Adjacent channel interference is signal impairment to one frequency due to presence ofanother signal on a nearby frequency. Therefore, a part of the spectrum is impaired.

Because interference is closely related to the frequency in use, the transmission over a radio linkmay be faulty in one direction only.

Fault Causes

Table 5-4 Causes of radio link faults

Fault Common Fault Causes

The transmit power is abnormal. The ODU is faulty.



5-11

Fault Common Fault Causes

The receive power is always lower than thenormal value.

l The antenna direction is not properlyadjusted.

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 slowup-fading.

There is an external interference.

The receive power is abnormal due to slowdown-fading.

The fading margin is not sufficient.

The receive power is abnormal due to fastfading.

The multipath fading is fast.

The receive power is normal, but the radiolink is faulty in one direction.

There is external interference.

NOTE

Depending on the received level, there is up fading and down fading.

l Up fading

The received level is higher than the value after free space fading. The difference can be 10-odd decibels.

l Down fading

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

Depending on the fading time, there is fast fading and slow fading.

l Fast fading

The fading duration time ranges from several milliseconds to tens of seconds.

l Slow fading

The fading duration time ranges from tens of seconds to several hours.

Because slow down fading and fast fading are imposed by the propagation paths, the radio link may be faultyin both directions.

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

configuration is correct.2. Check whether the ODU and the IF board are faulty.3. If the transmit power is abnormal, replace the ODU.4. If the receive power is abnormal, check out the possible causes based on the fading type.


Maintenance Guide


Issue 04 (2010-10-30)

5. If the receive power is normal but faults occur on the radio link intermittently, checkwhether there is interference before you proceed.

6. If the transmit/receive power is normal, perform loopback operations.



5-13

Fault Locating Procedures


Maintenance Guide


Issue 04 (2010-10-30)

Figure 5-4 Flow of handling radio link faults

Start

ODU or IF relatedalarm?

Yes

Clear the alarm

No

Proceed tothe next step

Is the faultrectified?

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?



5-15


Note Description

1 Handleincorrectoperations.

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 same as

the data configuration at the receive end.l Check whether the data configuration matches the type of the ODU and

the hybrid coupler.

2 Handleequipmentfaults.

Pay special attention to:l VOLT_LOSl CONFIG_NOSUPPORTl HARD_BADl TEMP_ALARMl IF_INPWR_ABNl RADIO_MUTEl RADIO_TSL_HIGHl RADIO_TSL_LOWl RADIO_RSL_HIGHl IF_CABLE_OPEN

3 Handle theexception oftransmitpower.

6.12 Replacing an ODU


Maintenance Guide


Issue 04 (2010-10-30)

Note Description

4 Handle theexceptionthat thereceivepower issmaller thanthe normalvalue.

Follow the steps below: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 a widerange.

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

3. If the difference between the RSL at the receive end and transmit end islarger than 10 dB, replace the ODUs to check whether the main or standbyODU is faulty.

4. Check whether the setting of the polarization direction of the antenna iscorrect. Rectify the wrong polarization direction.

5. Replace the ODUs and hybrid coupler to identify the faulty part.6. Check whether there is a mountain or building in the transmit direction.7. Check whether the gains of the antennas at the receive and transmit ends

comply with the specifications. Replace the antenna whose gain does notcomply with the specifications.

5 Handle theup slowfading fault.

Follow the steps below:1. Check whether there is co-channel interference.

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

infer that there is co-channel interference that may impair the long-term availability and performance of the system.

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

spectrum or change plans to reduce the interference.

6 Handle thedown slowfading fault.

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.



5-17

Note Description

7 Handle thefast fadingfault.

Contact the network planning department to make the following changes:l Adjust the position of the antenna to block the reflected wave or make the

reflection point fall on the ground that has a small reflection coefficient,thus reducing the multipath fading.

l Adjust the RF configuration to make the links in the 1+1 SD configuration.l For the links in the 1+1 SD configuration, adjust the height difference

between two antennas to make the receive power of one antenna muchstronger than that of another.

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

8 Handle theinterferencefault.

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

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

infer that there is co-channel interference that may impair the long-term availability and performance of the system.

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

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

spacing.4. Test and record the RSL.5. Increase the received frequency at the local end, with a step length of

0.5 MHz or 1 MHz, and record the RSL accordingly until the receivedfrequency is equal to the original received frequency plus a half of thechannel spacing.

6. Compare the recorded RSLs, and check whether the RSL in a certainspectrum is abnormal if the received frequency is within the permittedrange.

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.


Maintenance Guide


Issue 04 (2010-10-30)

Note Description

9 Use theloopbackmethod tolocate a fault.

Follow the steps below:1. Perform an inloop on the IF port.

If the fault is not cleared after the loopback, replace the IF board.2. Check whether the IF cable is soggy, broken or pressed. Make the

connector again.3. Check whether the IF cable is soggy, broken, or pressed. If yes, replace

the IF board.4. Replace the ODU.

If the fault is cleared after the replacement, the original ODU is faulty.

Experience and Summaryl During a commissioning process, make sure that the antenna direction is correctly adjusted

to prevent possible incipient faults.l Periodically collect the change data of the transmit power and receive power, and analyze

the change data to remove incipient faults in time.

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

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

l B1_EXCl B1_SDl RS_CROSSTRl RSBBEl RSESl RSSESl RSCSESl RSUAS

NOTE

When the IF board works in the PDH mode, the above RS bit error alarms and performance events may also bereported. Such alarms and performance events are detected by the B1 that is defined in the PDH microwaveframe.

The line board detects MS bit errors by the MS overhead byte B2. Related alarms andperformance events are listed below:

l B2_EXCl B2_SD



5-19

l MS_CROSSTRl MSBBEl MSESl MSSESl MSCSESl MSUAS

The line board detects HP bit errors by the HP overhead byte B3. Related alarms and performanceevents are listed below:

l B3_EXCl B3_SDl HP_CROSSTRl HPBBEl HPESl HPSESl HPCSESl HPUAS

LP bit errors are detected by PDH service processing boards or Ethernet service processingboards using the VC-3 overhead byte B3 or VC-12 overhead byte V5. Related alarms andperformance events are listed below:

l B3_EXC_VC3_l B3_SD_VC3l BIP_EXCl BIP_SDl LP_CROSSTRl VC3BBEl VC3ESl VC3SESl VC3CSESl VC3UASl LPBBEl LPESl LPSESl LPCSESl LPUAS


Maintenance Guide


Issue 04 (2010-10-30)

Fault Causes

Table 5-6 Causes of bit errors

Fault Type Common Cause

There are some RS bit errors. l The line is faulty.– For the optical fiber line, the optical

power is abnormal, the fiberperformance degrades, or the fiberconnector is not clean.

– For the STM-1 cable line, the cableperformance degrades, the cable is notproperly grounded, or the cableconnector is not in good contact.

– For the radio line, check whether thereis an MW_FEC_UNCOR alarm or anRPS_INDI alarm.

l The line board is faulty.l The clock unit is faulty.l The quality of the clock over the network

degrades.When the quality of the clock over thenetwork degrades, there will be a pointerjustification event.

There is no RS bit error, but there are MS biterrors or HP bit errors.

l The line board is faulty.l The quality of the clock over the network

degrades.When the quality of the clock over thenetwork degrades, there will be a pointerjustification event.

l The working temperature of the line boardis excessively high.

There are only LP bit errors. l The PDH service processing board or theEthernet service processing board isfaulty.

l The cross-connect unit is faulty.l The working temperature of the PDH

service processing board or the Ethernetservice processing board is excessivelyhigh.

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

l There is power surge or an externalinterference source, or the equipment isnot properly grounded.



5-21

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, first analyze RS bit errors,

then MS bit errors, HP bit errors, and finally LP bit errors.3. When multiple paths have bit errors, first check whether the overlapping part is faulty.4. When the fault is not located after you analyze the alarms and performance events, perform

loopback operations section by section.5. For a possibly degraded part, replace it with a new one.


Figure 5-5 Flow of handling bit errors

Start

Is there anequipment alarm?

1

No

Yes Handle the alarm

Is there an RS bit error alarm or a

performanceevent?

Yes Handle the RS bit error of theIF board

No

Is there anMS/HP alarm or a

performanceevent?

Yes Handle the MS/HP bit error

No

Is there an LP alarm? Yes Handle the LP bit error

Perform loopback operationssection by section

No

Go to the nextstep


End

Yes

No

4

6

7

Is there a pointerjustification event?

Yes Handle the pointer justification event

No

2

If thealarmingboard is

Handle the RS bit error of theSDH optical interface board

3

STM-1 electricalinterface board

SDH opticalinterface board

Handle the RS bit error of theSTM-1 electrical interface

board

5

IF board


Maintenance Guide


Issue 04 (2010-10-30)


Note Description

1 Pay special attention to:l TEMP_ALARMl SYN_BADl HARD_BAD

2 Refer to 5.9 Troubleshooting Pointer Justifications.

3 Follow the steps below:1. Interchange the Tx fiber core and the Rx fiber core at both ends of the path.

If bit errors change after the exchange, the fiber is faulty. Otherwise, theequipment at the two ends is faulty.

2. In the case that the fiber is faulty, check whether the fiber between theequipment and the ODF and the section of the fiber that is led out of theequipment room are pressed. In addition, check whether the fiberconnector is clean.

3. In the case that the equipment at the two ends is faulty, use a fiber jumperto loop back the optical ports. After the loopback, if the fault is not cleared,the line board is most likely to be faulty.

4. For the case that the equipment at the two ends is faulty, to locate the fault,you can also replace the SDH optical interface board or make anexchange between the board and another board of the same type that isworking normally. If the alarm changes after the exchange, the board isfaulty.

4 Follow the steps below:1. Check whether there is an MW_FEC_UNCOR alarm or an RPS_INDI

alarm.2. If yes, refer to 5.3 Troubleshooting Radio Links.3. If no, replace the IF board.

5 Follow the steps below:1. Make an exchange between the Tx cable and the Rx cable at both ends of

the path. If bit errors change after the exchange, the cable is faulty.Otherwise, the equipment at the two ends is faulty.

2. In the case that the cable is faulty, check the cable connector. Also checkwhether the cable is properly grounded and if the cable is broken.

3. In the case that the equipment at the two ends is faulty, use a cable to loopback the electrical ports. After the loopback, if the fault is not cleared, theline board is most likely faulty.

4. For the case that the equipment at the two ends is faulty, to locate the fault,you can also replace the SDH electrical interface board or make anexchange between the board and another board of the same type that isworking normally. If the alarm changes after the exchange, the board isfaulty.



5-23

Note Description

6 Follow the steps below:1. Loop back the alarming line board.

If the fault is not cleared, replace the line board.If the fault is cleared, replace the line board at the transmit side.

2. If the fault is still not cleared, check whether there is power surge or anexternal interference source, or if the equipment is not properly grounded(primarily for the SDH electrical interface board).

7 Follow the steps below:1. Replace the PDH service processing board or Ethernet service

processing board or cross-connect board based on how the service pathsthat have bit errors overlap each other.

2. If the fault is not cleared, check whether there is power surge or an externalinterference source, or if the equipment is properly grounded.

Experience and Summaryl Check bit error performance events and handle them routinely in time.l To locate a fault, primarily use the method of analyzing alarms and performance events.

In addition, consider the loopback method and the replacement method.

5.5 Troubleshooting the Interconnection with the SDHEquipment

In the case that the NE is interconnected with the SDH equipment, if the SDH service cannot betransmitted between the equipment sets, there is an interconnection fault.

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 ordering method.Some 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 interval method.

l The overhead bytes at the two sides are inconsistent.l The indexes of SDH interfaces do not meet requirements.l The equipment is not properly grounded (only for the STM-1 electrical interface).

NOTE

When the interconnected equipment is the ATM or Ethernet equipment, the common cause for theinterconnection fault is that the service is not set to the VC-4 pass-through service. As a result, the overheadsare processed in the terminating mode instead of the pass-through mode.


Maintenance Guide


Issue 04 (2010-10-30)

Fault Locating MethodsAnalyze the fault phenomenon and alarms. Check the possible fault causes one by one.


Figure 5-6 Flow of troubleshooting the interconnection with the SDH equipment

Start

Is theinterconnected equipmentthe ATM/IP equipment?

No

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

through service

Is there an overheadsetting related alarm?

YesHandle the alarm

No

Is the interface theSTM-1 electrical

interface?

Yes

No

Go to the nextstep Is the fault cleared?

End

Yes

No

Is thenumbering mode the

line numbering?

Modify the data configuration.Use the line numbering

method to set the VC-12

No

Query the VC-12 numberingmethod of the interconnected

equipment

Yes

1

Check the grounding

2

Test the indexes of interfaces

Do the interfaces meetrelevant standards?

Handle the faults of the localequipment

Handle the faults of theinterconnected equipment

Yes

No

3



5-25


Note Description

1 Pay special attention to:l J0_MMl HP_TIMl LP_TIMl LP_TIM_VC12l LP_TIM_VC3l HP_SLMl LP_SLMl LP_SLM_VC12l LP_SLM_VC3

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

jointly grounded.l Check whether the shielding layer of the coaxial cable connector on the

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

same way.NOTE

Disconnect all the signal cables between the interconnecting equipment. Use amultimeter to measure the level between the shielding layers of the coaxial cables at thereceive and transmit ends of the SDH equipment. In addition, measure the level betweenthe shielding layers of the coaxial cables at the receive and transmit ends of the oppositeequipment. If the potential difference is large (about 0.5 V), the fault may be caused bythe grounding.

3 Common indexes of the optical interfaces:l Mean launched optical powerl Receiver sensitivityl Overload optical powerl Permitted frequency deviation of the input interfaceCommon indexes of the electrical interfaces:l Permitted frequency deviation of the input interfacel Allowed attenuation of the input interface

Experience and SummaryTo clear any interconnection fault, you need to have a knowledge of the characteristics of theinterfaces of the interconnected equipment.


Maintenance Guide


Issue 04 (2010-10-30)

5.6 Troubleshooting the Interconnection with the PDHEquipment

In the case that the OptiX RTN equipment is interconnected with the PDH equipment, if thePDH service cannot be transmitted between the equipment sets, there is an interconnection fault.

Fault Causesl There is an impedance mismatch between interfaces.l The equipment is not properly grounded.l The cable performance degrades.l The indexes of PDH interfaces do not meet the requirements.

Fault Locating MethodsAnalyze the fault phenomenon and alarms. Check the possible fault causes one by one.



5-27


Figure 5-7 Flow of troubleshooting the interconnection with the 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 thecoaxial cable?

No

Check the impedance ofthe interfaces

Yes

1

Adjust the cables

Test the indexes ofinterfaces

Do the interfacesmeet standards?

Handle the faults of thelocal equipment

Handle the faults of theinterconnected equipment

Yes

No

4

Check the grounding

2

3

No


Maintenance Guide


Issue 04 (2010-10-30)


Note Description

1 Check whether the type of the tributary board

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

jointly grounded.l Check whether the shielding layer of the coaxial cable connector on the

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

same way.NOTE

Disconnect all the signal cables between the interconnecting equipment. Use amultimeter to measure the level between the shielding layers of the coaxial cables at thereceive and transmit ends of the PDH equipment. Also measure the level between theshielding layers of the coaxial cables at the receive and transmit ends of the oppositeequipment. If the potential difference is large (about 0.5 V), the fault may be caused bythe 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 trunk

cable is bound with the power cable, the cable signal is interfered by thepower signal).

NOTEChecking the cables involves checking the cables from the DDF to the client side andchecking the cables from the DDF to the transmission equipment side.

4 Check the following indexes:l Input jitter tolerancel Permitted input frequency deviationl Output jitterl Output frequency deviation

Experience and Summary

Grounding problems are the most common reasons that cause an interconnection failure whenthe OptiX RTN 600 is interconnected with the PDH equipment.

5.7 Troubleshooting SDH/PDH Radio-Based EthernetService Faults

EoS/EoPDH-based Ethernet services can be transmitted through SDH/PDH radio networks orTDM networks. The associated service faults include Ethernet service interruption and Ethernetservice degradation.



5-29

Ethernet service interruption indicates that the Ethernet service is completely interrupted.Ethernet service degradation indicates that the Ethernet service is abnormal. For example, thenetwork speed is low, the equipment delay is long, loss of packets occurs, or incorrect packetsexist in the received or transmitted data.

Fault Causesl The possible human factors are as follows:

– Loopback is performed on an Ethernet board, or loopback is performed on atransmission line.

– The settings of parameters of an Ethernet port such as port enabled, working mode, andflow control are different from those of its interconnected equipment.

– The configuration of the encapsulation/mapping protocol or the LCAS protocol isdifferent from that of the opposite equipment.

– The VCTRUNK-bound timeslot is different from that of the opposite equipment.– The service configuration is incorrect.

l The equipment at the local end is faulty.l The line board is faulty or has bit errors.l Certain E1 services are transmitted on the transmission lines for EoS-based Ethernet

services.l The interconnected equipment is faulty.l The network cable is faulty.l External electromagnetic interference is severe.

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


Maintenance Guide


Issue 04 (2010-10-30)


Figure 5-8 Flow of handling Ethernet service faults

Clear the alarm

5

No

Yes

No

Yes

Yes Troubleshoot theopposite equipment

No

3

2

Troubleshoot the equipmentby performing loopbackoperations section by

section by replacing boards



End

Yes

No

Ethernetservice alarm?

No

Yes

Clear the alarm

Start

Incorrectoperation?

1Cancel the operation

No

Yes

Equipment alarmor radio link

alarm?

Loop formed by theE-LAN service

trails?

Release the loop

Yes Query the port andservice traffic and

analyze the fault causes

Rectify the fault accordingto the flow of handling

abnormal RMONperformance events

Fault on theopposite

equipment?

RMON performanceevents?

Abnormal

4



5-31


Note Description

1 Check the following points:l Whether a loopback is set for the Ethernet portl Whether a loopback is set for the transmission linel Whether the settings of parameters of an Ethernet port such as port

enabled, working mode, and flow control are the same as those of itsinterconnected equipment

l Whether the configuration of the encapsulation/mapping protocol or theLCAS protocol is the same as that of the opposite equipment

l Whether the VCTRUNK-bound timeslot is the same as that of the oppositeequipment

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

2 Check the following equipment alarms:l POWER_ALMl FAN_FAILl HARD_BADl BD_STATUSl SYN_BADl NESF_LOSTl TEMP_ALARMl RADIO_RSL_HIGHl RADIO_RSL_LOWl RADIO_TSL_HIGHl RADIO_TSL_LOWl IF_INPWR_ABNCheck the following line alarms:l MW_LIMl MW_LOFl R_LOSl R_LOFl MS_AISl AU_AISl AU_LOPl B1_EXCl B2_EXC


Maintenance Guide


Issue 04 (2010-10-30)

Note Description

3 Check the following:l ETH_LOSl FLOW_OVERl ALM_GFP_dCSFl ALM_GFP_dLFDl FCS_ERRl LCAS_PLCTl LCAS_TLCTl LCAS_PLCRl LCAS_TLCRl LCAS_FOPTl LCAS_FOPRl LFA

4 Check whether loops occur in the Ethernet LAN services.TIP

You can check whether a loop occurs by using the self-loop test function of the EMS6.

5 For RMON performance events, refer to D RMON Event Reference.



5-33

Figure 5-9 Flow of handling RMON abnormal performance events

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

Is it a MTU settingproblem?

YesModify the MTU value

No

2

Proceed withthe next step


End

Yes

No

Is there anyPAUSE frame?

3

No

No

Yes Handle the flow controlproblem or increase the

bandwidth

View the statistics groupperformance on an Ethernet port

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

1

4

6

Are broadcast packetsexcessive?

No

Yes Handle the problem onexcessive broadcast

packets

5


Note Description

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


Maintenance Guide


Issue 04 (2010-10-30)

Note Description

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

with a new one.l Access the Ethernet services by using another Ethernet port. If the new

port does not report the "FCS error " of RMON performance, you can inferthat the hardware of the previous port is faulty. Otherwise, you can inferthat the hardware of the Ethernet port at the opposite side is faulty.

3 Check the following points:l Whether the port operating rate of this equipment is the same as that of its

interconnected equipmentl Whether the duplex/half-duplex mode of ports on this equipment is the

same as that on its interconnected equipmentl Do not set one port to auto-negotiation and the opposite port to full-duplex.

4 Check the following points:l Whether the flow control mode of this equipment is the same as that of its

interconnected equipmentl Whether the Ethernet service volume is larger that the configured

VCTRUNK bandwidth

5 Identify the causes of generating excessive broadcast packets, such as 7.5.5Setting Loopback for the Ethernet Service Processing Board or incorrectsetting of the VB filtering table, and handle the problem accordingly. If thefault lies in the opposite equipment, you can reduce the number of broadcastpackets by setting a broadcast packet suppression threshold for the Ethernetport.

6 The Maximum Transmission Unit (MTU) of a network can be tested by a testmeter. The maximum frame length that is set for a port must be longer thanthis maximum network MTU.


Understand the features, working mode, and configured protocols of interfaces on Ethernetequipment, which is required to troubleshoot Ethernet faults.

5.8 Troubleshooting Faults in Hybrid Radio-Based EthernetServices

Hybrid radio-based Ethernet services can be transmitted over Hybrid radio networks but cannottraverse a TDM network. The associated faults include Ethernet service interruption and Ethernetservice degradation.

The Ethernet service interruption indicates that the Ethernet service is completely interrupted.The Ethernet service degradation indicates that the Ethernet service is abnormal. For example,



5-35

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 Causesl The human factors are as follows:

– An Ethernet board loopback or a transmission line loopback occurs.– The settings of the parameters of an Ethernet port, such as the port enabling, working

mode, and flow control are different from those of the interconnected equipment.– The configuration of the encapsulation/mapping or LCAS protocol is different from

that of the remote equipment.– The VCTRUNK-bound timeslot is different from that of the remote equipment.– The service configuration is incorrect.

l The local equipment is faulty.l The line board is faulty or has bit errors.l The modulation mode changes because of the degradation of the link performance when

the AM function is enabled.l The interconnected equipment is faulty.l The network cable is faulty.l The external electromagnetic interference is severe.

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 alarm.3. Locate the fault cause according to the RMON performance event and alarm.


Maintenance Guide


Issue 04 (2010-10-30)

Fault Locating Procedure

Figure 5-10 Flow of handling an Ethernet service fault

Clear the alarm

5

No

Yes

No

Yes

Yes Troubleshoot theopposite equipment

No

3

2

Troubleshoot the equipmentby performing loopbackoperations section by

section by replacing boards



End

Yes

No

Ethernetservice alarm?

No

Yes

Clear the alarm

Start

Incorrectoperation?

1Cancel the operation

No

Yes

Equipment alarmor radio link

alarm?

Loop formed by theE-LAN service

trails?

Release the loop

Yes Query the port andservice traffic and

analyze the fault causes

Rectify the fault accordingto the flow of handling

abnormal RMONperformance events

Fault on theopposite

equipment?

RMON performanceevents?

Abnormal

4



5-37


Note Description

1 Check the following points:l Whether a loopback is set for the Ethernet boardl Whether a loopback is set for the transmission linel Whether the settings of the parameters of an Ethernet port, such as the port

enabling, working mode, and flow control are the same as those of theinterconnected equipment

l Whether the configuration of the encapsulation/mapping or LCASprotocol is the same as that of the remote equipment

l Whether the VCTRUNK-bound timeslot is the same as that of the remoteequipment

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

2 Check the following equipment alarms:l POWER_ALMl FAN_FAILl HARD_BADl BD_STATUSl SYN_BADl NESF_LOSTl TEMP_ALARMl RADIO_RSL_HIGHl RADIO_RSL_LOWl RADIO_TSL_HIGHl RADIO_TSL_LOWl IF_INPWR_ABNCheck the following line alarms:l MW_LIMl MW_LOFl MW_BER_EXCl MW_BER_SDl MW_LIMl MW_LOFl MW_RDIl MW_FEC_UNCOR

3 Check the following alarms:l ETH_LOSl ALM_GFP_dCSF


Maintenance Guide


Issue 04 (2010-10-30)

Note Description

4 Check the following alarms:l ALM_GFP_dLFDl FCS_ERRl LCAS_PLCTl LCAS_TLCTl LCAS_PLCRl LCAS_TLCRl LCAS_FOPTl LCAS_FOPR

5 For RMON performance events, refer to the D RMON Event Reference.



5-39

Figure 5-11 Flow of handling an abnormal RMON performance event

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

Is it a MTU settingproblem?

YesModify the MTU value

No

2

Proceed withthe next step


End

Yes

No

Is there anyPAUSE frame?

3

No

No

Yes Handle the flow controlproblem or increase the

bandwidth

View the statistics groupperformance on an Ethernet port

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

1

4

6

Are broadcast packetsexcessive?

No

Yes Handle the problem onexcessive broadcast

packets

5


Note Description

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


Maintenance Guide


Issue 04 (2010-10-30)

Note Description

2 The handling procedure is as follows:l Check the network cable. If the network cable does not meet the

requirements, replace the network cable.l Change the Ethernet port of the access services on the Ethernet board. If

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

3 Check the following points:l Whether the port operating rate of the equipment is the same as that of the

interconnected equipmentl Whether the full-duplex/half-duplex mode of a port on the equipment is

the same as that on the interconnected equipmentl Do not set the auto-negotiation at one end and the full-duplex at the other

end.

4 Check the following points:l Whether the flow control mode of the equipment is the same as that of the

interconnected equipmentl Whether the Ethernet service volume is greater than the configured

VCTRUNK bandwidth

5 Find out of the reason of excessive broadcast packets (such as 7.5.5 SettingLoopback for the Ethernet Service Processing Board or improper VB filtertable setting) and solve the problem. If the problem is caused by the oppositeequipment, set the threshold of broadcast packet suppression for an Ethernetport to reduce broadcast packets.

6 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.


Understand the features, working mode, and configured protocols of interfaces on the Ethernetequipment, which is required to troubleshoot Ethernet faults.

5.9 Troubleshooting Pointer JustificationsWhen an NE reports a large amount of justification events of the administrative unit (AU) pointeror the tributary unit (TU) pointer, there are pointer justification faults.

When the position of the first byte of the VC-4 in the AU-4 payload changes, the AU pointermakes a justification accordingly. The performance events of the AU pointer justification are asfollows:

l AUPJCHIGHl AUPJCLOW



5-41

l AUPJCNEWNOTE

The AU pointer justification is generated at an upstream NE but is detected and reported at a downstream NE.

When the service is configured to be at the VC-12 level, apply the re-framing process to terminatethe AU pointer justification. The terminating method is to transform the AU pointer justificationinto the TU pointer justification. The performance events of the TU pointer justification are asfollows:

l TUPJCHIGHl TUPJCLOWl TUPJCNEW

NOTE

The TU pointer justification is generated at the NE where the AU pointer is transformed into the TU pointer,but is detected and reported by the tributary board of the NE where services are terminated.

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

two clock sources in the same network or mutual clock tracing occurs.l The optical fibers links are wrongly connected. As a result, mutual clock tracing occurs.l The quality of the clock source degrades, the clock unit is faulty, or there are other clock-

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

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

Fault Types Fault Locating Methods

AU pointer justifications 1. Analyze and clear clock alarms.2. Correct wrong data configurations and

wrong fiber connections.3. Change the clock and service

configurations to find the stations whoseclock is asynchronous with the entirenetwork.

4. Replace the components whoseperformance is possibly poor or degradedto locate a fault.


Maintenance Guide


Issue 04 (2010-10-30)

Fault Types Fault Locating Methods

TU pointer justifications 1. Analyze and clear clock alarms.2. Correct wrong data configurations and

wrong fiber connections.3. Change the clock and service

configurations to find the stations whoseclock is asynchronous with the entirenetwork.

4. Replace the components whoseperformance is possibly poor or degradedto locate a fault.



5-43


Figure 5-12 Flow of handling pointer justifications

Start

Is there a clock relatedalarm?

1

No

YesHandle the alarm

Wrongly connected?Yes

Re-connect the fiber

No

Is there an AU pointerjustification event?

Yes

No

Is there a TU pointerjustification event?

Yes

Go to the next step Is the fault cleared?

End

Yes

No

Wrong configuration?Modify the dataconfiguration

No

Check the clockconfiguration

2

Yes

Check the fiber connection

3

Locate the faulty board

5

Find the NE whose clock isout of synchronization

4

Find the faulty board

7

Find the NE whose clock isout of synchronization

6

No


Maintenance Guide


Issue 04 (2010-10-30)


Note Description

1 Pay special attention to:l TEMP_ALARMl SYN_BADl HARD_BADl LTIl SYNC_C_LOSl S1_SYN_CHANGEl EXT_SYNC_LOS

2 Check the following points:l Check whether there are two clock reference sources in the entire network.l Check whether mutual clock tracing occurs.

3 Query ECC routes to check whether the fibers are correctly connected. Check thefiber connection in the east and west directions of the NE that reports the pointerjustification event.

4 Follow the steps below:1. Locate the VC-4 channel that reports an AU pointer justification event.2. Along the service source direction of the VC-4 channel, locate the source NE

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

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

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

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

6. Along the clock tracing direction, find the line board that is the first to reportthe AU pointer justification of the VC-4 channel.The clock of the remote NE to which the line board is connected isasynchronous with the reference clock. Hence, the line board in the remoteNE that receives the clock signal, the line board that sends the clock signal tothe remote NE, and the clock unit of the remote NE, may be faulty.

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

5 Replace the possibly faulty boards.



5-45

Note Description

6 Follow the steps below:1. Modify the service configuration to make the NE where the clock reference

source is as the central NE. Other NEs has the E1 service of the central NE.2. Along the clock tracing direction, find the NE that is the first to report the TU

pointer justification.The clock of the NE is asynchronous with the reference clock. Hence, the lineboard in the NE that receives the clock signal, the line board that sends theclock signal to the NE, and the clock unit of the NE, may be faulty.

3. Modify the configuration data to make all NEs trace the clock in anotherdirection.

4. Along the clock tracing direction, find the NE that is the first to report the TUpointer justification.The clock of the NE is asynchronous with the reference clock. Hence, the lineboard in the NE that receives the clock signal, the line board that sends theclock signal to the NE, and the clock unit of the NE, may be faulty.

5. Compare the results and find out the common points.NOTE

This method is also applicable in locating an AU pointer justification event.

7 Replace the possibly faulty boards. For a TU pointer justification, check the lineboard, the clock board, and the tributary board.

Experience and SummaryIn a well synchronized network, there are few pointer justifications (less than six per day). Hence,monitoring the pointer of an SDH transmission system is an effective way to check thesynchronization of the system.

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

Fault Causesl The phone set is incorrectly set.l The phone line is connected incorrectly.l The orderwire is incorrectly configured.

NOTEWhen services are transmitted over E1 lines, the orderwire traffic needs to be transmitted in othermeans, for example, through the synchronous data interface or external clock interface.

l The system control unit is faulty.l The line unit is faulty.


Maintenance Guide


Issue 04 (2010-10-30)

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

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


Figure 5-13 Flow of handling orderwire faults

Start

Is the phonecorrectly set?

No Modify 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

1

Modify the configuration

Replace the possibly faultyboard

3

Re-connect the phone line

2

Yes



5-47


Note 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", that is, the dual tone

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

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

2 Check the following points:l Check whether all orderwire phone numbers in a subnet are of the same

length.l Check whether all orderwire phone numbers in a subnet are unique.l Check whether the overhead bytes of all NEs in a subnet are the same.l Check whether the orderwire port is correctly set.

3 Replace the SCC board and the line board that extracts the orderwire byteto locate the fault.

Experience and SummaryIt is necessary to periodically check the orderwire phone set.


Maintenance Guide


Issue 04 (2010-10-30)

6 Part Replacement

About This Chapter

Part replacement is a method frequently used to locate faults. The replacement operation varieswith the part types.

Table 6-1 Part replacement description

Part Name Operation Tool

SL1, SD1, andSL4

6.3 Replacing the SDH OpticalInterface Board

l ESD wrist strapl Screwdriverl Web LCTSLE and SDE 6.4 Replacing the SDH Electrical

Interface Board

PH1, PO1, PD1,and PL3

6.5 Replacing the PDH InterfaceBoard

EFT4, EMS6,and EFP6

6.6 Replacing the EthernetService Processing Board

IF1A, IF1B,IFX, IF0A,IF0B, and IFH2

6.7 Replacing the IF Board

PXC 6.8 Replacing the PXC Board

SCC 6.10 Replacing the SCC Board

FAN 6.11 Replacing the Fan Tray

ODU 6.12 Replacing an ODU l Ejector lever (torque wrench)l Web LCTl Siliconl Waterproof adhesive tape

OptiX RTN 620 Radio Transmission SystemMaintenance Guide 6 Part Replacement


6-1

Part Name Operation Tool

Replacing theIF Cable

6.13 Replacing the IF Cable l Multimeterl Ejector leverl Electro-technical knifel Filel Installation parts and

accessories of the connectorl IF cablel Waterproof adhesive tape

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

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

6.3 Replacing the SDH Optical Interface BoardWhen the SDH optical interface board is replaced, the service of the board without any protectionis interrupted.

6.4 Replacing the SDH Electrical Interface BoardWhen the SDH electrical interface board is replaced, the service of the board without anyprotection is interrupted.

6.5 Replacing the PDH Interface BoardWhen the PDH interface board is replaced, the services of the board are interrupted.

6.6 Replacing the Ethernet Service Processing BoardWhen the Ethernet service processing board is replaced, the services on this board areinterrupted.

6.7 Replacing the IF BoardIf the IF board is not configured with 1+1 protection and the services of the board are notconfigured with any protection, the services on the board are interrupted during boardreplacement. If the IF board is configured with XPIC, the XPIC-related services are also affected.

6.8 Replacing the PXC BoardIf the PXC board is not configured with the 1+1 backup, all services of the system are interruptedduring this process.

6.9 Replacing the Storage CardWhen replacing the storage card, do not perform any operations on the NMS, and do not performswitching.

6.10 Replacing the SCC BoardDuring this process, no NM operation and switching can be performed.

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

6.12 Replacing an ODUIf the radio link provided by an ODU is not configured with protection and the services on theODU are not configured with protection, replacing the ODU interrupts the services. In addition,

6 Part ReplacementOptiX RTN 620 Radio Transmission System

Maintenance Guide


Issue 04 (2010-10-30)

the services on the radio link of the other polarization direction are affected if the radio linkprovided by the ODU is configured with XPIC.

6.13 Replacing the IF CableThe IF cable cannot transmit radio services when it is replaced.



6-3

6.1 Removing a BoardRemoving 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 Optional: If the board is connected with cables, remove the cables after marking them.

Step 3 Loosen the screws on the panel of the board.

Figure 6-1 Removing a board (1)

Step 4 Hold the left and right ejector levers with hands. Push them outwards to disengage the boardfrom the backplane.


Step 5 Pull out the board gently along the guide rail in the slot. At this time, the board is in a parallelmanner.


Maintenance Guide


Issue 04 (2010-10-30)


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

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

----End

6.2 Inserting a BoardInserting 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 Hold the ejector levers with hands on the panel. Push them outwards so that the angle betweenthe ejector lever and the panel is 45 degrees or so.

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

Figure 6-4 Inserting a board (1)



6-5

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

Step 4 Press the two ejector levers inward with force.


Step 5 Tighten screws on the panel.


Step 6 Optional: If the board is connected to cables originally, connect the cables based on the labelmarked on them.

----End


Maintenance Guide


Issue 04 (2010-10-30)

6.3 Replacing the SDH Optical Interface BoardWhen the SDH optical interface board is replaced, the service of the board without any protectionis interrupted.

Prerequisitel You must be aware of the impact of board replacement.l You must know the specific position of the board to be replaced.l You must know the service protection and protection channels of the board to be replaced.l The spare SDH optical interface board must be at hand and that the version and type of the

spare board must be consistent with those of the board to be replaced. You can perform thetask in 7.4.2 Querying a Board Manufacture Information Report to learn the versionof the board to be replaced.

NOTE

You can identify the type of a board through the board feature code in the bar code on the ejector lever.


l ESD wrist strapl Screwdriverl Web LCT

Procedure

Step 1 Use the Web LCT to query the current alarms of the board.

Step 2 Optional: If the services on the board are configured with the SNCP, ensure that the servicesare switched to the protection channel.1. Query the SNCP protection group.2. If the port on the board functions as the current working channel, the current protection

channel is not on the board, and the state of the current protection channel is normal or SD,perform forced switching.

Step 3 Optional: If the services on the board are configured with the linear MSP, ensure that the servicesare switched to the protection channel.1. Query the linear MSP group.2. If the port on the board functions as the current working channel, the current protection


Step 4 Optional: If the services on the board are configured with the ring MSP, ensure that the servicesare switched to the protection channel.1. Query the linear MSP group.2. If the port on the board functions as the current working channel, the current protection




6-7

Step 5 Remove the board according to 6.1 Removing a Board.

Step 6 Check whether the version and SFP type of the spare board are the same as those of the boardto be replaced.

Step 7 Insert the spare board according to 6.2 Inserting a Board.

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

Step 9 Query the current alarms on the board using the Web LCT.There should be no new alarms.

Step 10 Optional: If the forced SNCP switching has been performed for the services, clear the forcedswitching using the Web LCT.

Step 11 Optional: If the linear MSP switching has been performed for the services, clear the forcedswitching using the Web LCT.

Step 12 Optional: If the ring MSP switching has been performed for the services, clear the forcedswitching using the Web LCT.

----End

6.4 Replacing the SDH Electrical Interface BoardWhen the SDH electrical interface board is replaced, the service of the board without anyprotection is interrupted.

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

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

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

l The spare SDH electrical interface board must be at hand and that the version and type ofthe spare board must be consistent with those of the board to be replaced. You can querythe board manufacturing information to obtain the version of the board to be replaced.


l ESD wrist strap

l Screwdriver

l Web LCT

Procedure


Step 2 If the services on the board are configured with the SNCP, ensure that the services are switchedto the protection channel.

1. Query the SNCP protection group.


Maintenance Guide


Issue 04 (2010-10-30)

2. If the port on the board functions as the current working channel, the current protectionchannel is not on the board, and the state of the current protection channel is normal or SD,perform forced switching.

Step 3 If the services on the board are configured with the linear MSP, ensure that the services areswitched to the protection channel.1. Query the linear MSP group.2. If the port on the board functions as the current working channel, the current protection


Step 4 If the services on the board are configured with the ring MSP, ensure that the services areswitched to the protection channel.1. Query the ring MSP group.2. If the port on the board functions as the current working channel, the current protection



Step 6 Ensure that the version of the spare board is the same as the version of the board to be replaced.





Step 11 Optional: If the linear MSP switching has been performed for the services, clear the forcedswitching using the Web LCT.

Step 12 Optional: If the ring MSP switching has been performed for the services, clear the forcedswitching using the Web LCT.

----End

6.5 Replacing the PDH Interface BoardWhen the PDH interface board is replaced, the services of the board are interrupted.

Prerequisitel You must be aware of the impact of board replacement.l You must know the specific position of the board to be replaced.l You must know the service protection and protection channels of the board to be replaced.l The spare PDH interface board must be at hand and that the version and type of the spare

board must be consistent with those of the board to be replaced. You can query the boardmanufacturing information to obtain the version of the board to be replaced.



6-9

NOTE

l The SL61PO1, PH1, and PD1 have two types: A and B. The A type is of 75-ohm interface impedance, andthe B type is of 120-ohm interface impedance. You can identify them by the bar code on the board ejectorlever.

l The E1 interface of the SL62PO1 is RJ45. The interface impedance is 120 ohms.

l The interface impedance of the PL3 is 75 ohms only.


l ESD wrist strap

l Screwdriver

l Web LCT

Procedure



Step 3 Make sure the version and type of the spare board are consistent with those of the board to bereplaced.




----End

6.6 Replacing the Ethernet Service Processing BoardWhen the Ethernet service processing board is replaced, the services on this board areinterrupted.



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

l The spare Ethernet service processing board must be at hand and that the version and typeof the spare board must be consistent with those of the board to be replaced. You canperform the task in 7.4.2 Querying a Board Manufacture Information Report to learnthe version of the board to be replaced. In the case of the EMS6 board, the type of the spareboard also must be consistent with the board to be replaced.

NOTE

You can identify the type of a board through the board feature code in the bar code on the ejector lever.


Maintenance Guide


Issue 04 (2010-10-30)

Tools, Instruments, and Materialsl ESD wrist strapl Screwdriverl Web LCT

Procedure



Step 3 Check whether the version and type of the backup part are the same as those of the board to bereplaced.




----End

6.7 Replacing the IF BoardIf the IF board is not configured with 1+1 protection and the services of the board are notconfigured with any protection, the services on the board are interrupted during boardreplacement. If the IF board is configured with XPIC, the XPIC-related services are also affected.

Prerequisitel You must be aware of the impact of board replacement.l You must know the specific position of the board to be replaced.l You must understand the configuration of the board 1+1 protection.l You must know the service protection and protection channels of the board to be replaced.l The spare IF board must be at hand and that the version and type of the spare board must

be consistent with those of the board to be replaced. You can perform the task in 7.4.2Querying a Board Manufacture Information Report to learn the version of the boardto be replaced.


Procedure




6-11

Step 2 Optional: If the services on the board are configured with the SNCP, ensure that the servicesare 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, and the state of the current protection channel is normal or SD,perform forced switching.

Step 3 Optional: If the services on the radio link are configured with the 1+1 protection, ensure thatthe services are switched to the protection IF board.

1. Query the IF 1+1 protection group.

2. If the board functions as the current working board, and the state of the current protectionboard is normal or SD, perform forced switching.

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

1. Query the IF N+1 protection group.

2. If the board functions as the current working board, and the state of the current protectionboard is normal or SD, perform forced switching.

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


Step 7 Check whether the version and type of the spare board are the same as those of the board to bereplaced.

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



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


Step 13 If the new IF board is an IF1A/IF1B board and reports the new alarm NO_BD_SOFT, load andactivate the FPGA file of the IF board again according to the upgrade guide.


Step 15 Optional: If the forced protection switching has been performed for the microwave line, clearthe forced switching using the Web LCT.

----End

6.8 Replacing the PXC BoardIf the PXC board is not configured with the 1+1 backup, all services of the system are interruptedduring this process.


Maintenance Guide


Issue 04 (2010-10-30)

Prerequisitel You must be aware of the impact of board replacement.l You must know the specific position of the board to be replaced.l You must understand the configuration of the board 1+1 protection.l The spare PXC board must be at hand and that the version and type of the spare board must

be consistent with those of the board to be replaced. You can perform the task in 7.4.2Querying a Board Manufacture Information Report to learn the version of the boardto be replaced.


PrecautionWhen the PXC is configured with 1+1 protection and only one-channel power is accessed, it isrecommended to provide one-channel -48 V/-60 V power for the standby PXC boardtemporarily. After the board is replaced, stop providing power for the standby board. This canensure that the equipment does not power off during the PXC replacement.

Procedure


Step 2 Optional: If the board to be replaced works in 1+1 mode and it is the main board, see 7.12Switching PXC Boards.

Step 3 Turn off the SYS-PWR switch of the PXC board to be replaced.

Step 4 Turn off the switch of the power that provides power for the PXC board to be replaced.


Step 6 Ensure that the version and type of the spare board are consistent with those of the board to bereplaced.


Step 8 Turn on the switch of the power that provides power for the PXC board.

Step 9 Turn on the SYS-PWR switch of the PXC board.



Step 12 Optional: If the switching is performed before the replacement, perform a switchover operationon the Web LCT to make the working board be the active board, not the standby board.

----End



6-13

6.9 Replacing the Storage CardWhen replacing the storage card, do not perform any operations on the NMS, and do not performswitching.

Prerequisitel You must be aware of the impact of storage card replacement.l You must know the specific position of the storage card to be replaced.

Tools, Equipment and Materialsl ESD wrist strapl Screwdriverl Web LCT


Maintenance Guide


Issue 04 (2010-10-30)

Background Information

Figure 6-7 Positions of the jumpers and storage card

2

1

JUMP1JUMP2JUMP3JUMP4

2

1

JUMP4JUMP3

JUMP2JUMP1

SL61SCCVER.B

Jumper definition

10

21

9

JUMP1JUMP2JUMP3JUMP4

SL61SCCVER.C or SL61SCCVER.E

1. Jumpers 2. Storage card

Table 6-2 Setting the jumpers

Jumper Setting (1: disconnected, 0: short circuit) Function

JUMP4 JUMP3 JUMP2 JUMP1

0 0 0 0 Normaloperating state.

0 0 0 1 Reserved.

0 0 1 0 Reserved.



6-15



0 0 1 1 Commissioningstate.

0 1 0 0 Operating state,with theWatchDogdisabled andmemoryundergone fullcheck.

0 1 0 1 BIOS holdoverstate. Even if theNE softwareexists, it is notrunning. The IPaddress isalways129.9.0.5. TheIP in theparameter areadoes not changefor theconvenience ofquerying.

0 1 1 0 Exhibitionmode.

0 1 1 1 Data recoverstate.

1 0 0 0 Reserved.

1 0 0 1 Reserved.

1 0 1 0 To erase thesystemparameter area.

1 0 1 1 To erasedatabase.

1 1 0 0 To erase NEsoftware and itspatches.

1 1 0 1 To erasedatabase, NEsoftware and itspatches.


Maintenance Guide


Issue 04 (2010-10-30)



1 1 1 0 To format thefile system sothat all the datais erased.

1 1 1 1 To format thefile system sothat all the datais erased (filesystem +extended BIOS+ systemparameter area).

Procedure



Step 3 Set the jumpers on the SCC board to positions 0111.

Step 4 Remove the storage card from the SCC board.1. Wear an ESD wrist strap.2. Unscrew the storage card, and remove the plug of the storage card from the socket of the

SCC board.

Figure 6-8 Removing a Storage Card



6-17

Step 5 Install the spare storage card onto the SCC board.

Figure 6-9 Installing a Storage Card

Step 6 Insert the SCC board.

Step 7 When the SCC board changes to BIOS state, remove the SCC board.

NOTEWhen the SCC board works in BIOS state, the PROG indicator on the front panel blinks slowly (300 ms on and300 ms off).

Step 8 Set the jumpers on the SCC board to positions 0000 (default setting).

Step 9 Insert the SCC board.


----End

6.10 Replacing the SCC BoardDuring this process, no NM operation and switching can be performed.



l The spare SCC board must be available and that the version and type of the spare boardmust be consistent with the version and type of the board to be replaced. You can performthe task in 7.4.2 Querying a Board Manufacture Information Report to learn the versionof the board to be replaced.


Maintenance Guide


Issue 04 (2010-10-30)



Procedure


Step 2 Press the RST button on the SCC front panel.During the reset of the SCC board, the PROG indicator is on, off, flashing, and off sequentially.

Step 3 When the PROG indicator is operating, Refer to section 3.2.1 Removing a Board, remove theboard.

Step 4 Make sure the version and the jumper settings of the spare board are consistent with the versionand the jumper settings of the board to be replaced.

Step 5 See 6.9 Replacing the Storage Card to remove the CF card from the original board and theninstall the CF card to the spare board.


Step 7 After the board starts to work, observe the indicators on the board.The STAT indicator should be on and green.


----End

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

PrerequisiteThe spare board must be made available, and the version and type of the spare board must bethe 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.

Tools, Equipment and Materials


Procedure




6-19

Step 2 Loosen the captive screws on the front panel of the fan tray.

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

Step 4 Remove the front panel of the fan tray.

Figure 6-10 Removing the front panel of the fan tray

NOTE

If the IDU is installed in a dustproof environment, no air filter is installed.

Step 5 Remove the fan board gently and horizontally along the guide rail.

Figure 6-11 Removing the fan tray

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

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

Step 7 Insert the spare fan board steadily along the guide rail.

Step 8 Install the front panel of the fan tray.


Maintenance Guide


Issue 04 (2010-10-30)

Step 9 Tighten the captive screws on the front panel of the fan tray.

Step 10 Observe the indicators on the front panel.The FAN indicator should be on and green.


----End

6.12 Replacing an ODUIf the radio link provided by an ODU is not configured with protection and the services on theODU are not configured with protection, replacing the ODU interrupts the services. In addition,the services on the radio link of the other polarization direction are affected if the radio linkprovided by the ODU is configured with XPIC.

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

l You must know the specific positions of the ODU to be replaced and the IF board connectedto the ODU.

l The spare ODU must be available and the type must be the same as the type of the ODUto be replaced.

Tools, Instruments, and Materialsl Torque wrench

l Web LCT

l Silicon

l Waterproof adhesive tape

Notes

Before you replace an ODU that is installed on the coupler, power off the ODU to be replaced,but do not power off or mute the other ODU. Otherwise, the services may be affected. Theinterface of the coupler generates little RF radiation, thus meeting the safety standards forelectromagnetic radiation.

Procedure

Step 1 Query the current alarms on the ODU.

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

Step 3 Remove the IF cable and the PGND cable connected to the ODU.

Step 4 Remove the ODU.



6-21

If... Then...

You need to remove the OptiX RTN 600ODU with a waveguide interface

Loosen the four latches of the ODU anddisconnect the ODU from the antenna, thehybrid coupler, or ODU adapter.

You need to remove the OptiX RTN 600ODU with a coaxial interface

Remove the ODU from the post.

You need to remove the RTN XMC ODUwith a coaxial interface

Loosen the four M6 captive screws of theODU cornerwise, Remove the ODU.

Step 5 Ensure that the type of the spare ODU is the same as the type of the ODU to be replaced.

Step 6 Install the ODU.

If... Then...

You need to install a new OptiX RTN 600ODU with a waveguide interface

See the OptiX RTN 600 ODU QuickInstallation Guide to install the ODU.

You need to install a new OptiX RTN 600ODU with a coaxial interface

See the OptiX RTN 600 ODU QuickInstallation Guide to install the ODU.

You need to install a new RTN XMC ODUwith a coaxial interface

See the RTN XMC ODU Quick InstallationGuide to install the ODU.

Step 7 Connect the PGND cable and the IF cable to the ODU.

Step 8 Waterproof the IF interface on the ODU.


Step 10 After the ODU starts to work, observe the ODU and LINK indicators on the front panel of theIF board.The two indicators should be on and green.

Step 11 Query the current alarms of the ODU.There should be no new alarms.

----End

6.13 Replacing the IF CableThe IF cable cannot transmit radio services when it is replaced.

Prerequisitel You must be aware of the impact of IF cable replacement.l You must know the specific positions of the IF cable to be replaced and the IF board

connected to the IF jump.l In the case of the RG-8U IF cable or the 1/2-inch IF cable, an IF jumper is required to

connect the IF cable to the IDU and both ends of the IF cable should be terminated with


Maintenance Guide


Issue 04 (2010-10-30)

type-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, Instruments, and Materialsl Ejector leverl Electro-technical knifel Filel Installation parts and accessories of the connectorl IF cablel Waterproof adhesive tape

Procedure


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

Step 3 Disconnect the IF cable and the IF jump, and the IF cable and the ODU.

Step 4 Use a multimeter to test the cable circuit so as to determine whether to make the IF cable withconnectors again or replace the IF cable.

If... Then...

If the IF cable with connectors need be made again Make new connectors for the IF cable.

If the IF cable need be replaced Replace with a new IF cable.

Step 5 Connect the IF cable and the IF jump, and the IF cable and the ODU.

Step 6 Waterproof the connectors at the two ends of the IF cable with the waterproof adhesive tape.


Step 8 After the ODU starts to work, observe the ODU and LINK indicators on the front panel of theIF board.The two indicators should be on and green.

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

----End



6-23

7 Supporting Task

About This Chapter

This topic describes the common maintenance operations.

7.1 Hardware LoopbackHardware loopback refers to the loopback operation performed by changing the physicalconnection.

7.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.

7.3 Browsing Alarms, Abnormal Events, and Performance EventsThe Web LCT is used to browse alarms, abnormal events, and performance events at the NElayer.

7.4 Querying a ReportYou can obtain the version, manufacture, and radio link information of all the boards by queryingthe corresponding report.

7.5 Software loopbackSoftware loopback refers to the loopback operation that is implemented by using the NMS. Inthe OptiX RTN 620, the SDH optical interface board, SDH electrical interface board, PDHinterface board, IF board, Ethernet service processing board, and ODU support loopback.

7.6 ResettingResetting is an important method for handling software faults. The OptiX RTN 620 supportscold resetting, warm resetting, and SCC resetting.

7.7 PRBS TestThe pseudorandom binary sequence (PRBS) test is an important method for networkmaintenance and self-check.

7.8 Querying the License CapacityYou can check whether the loaded license file meets the requirements by querying the licensecapacity.

OptiX RTN 620 Radio Transmission SystemMaintenance Guide 7 Supporting Task


7-1

7.9 Setting the State of a LaserA laser on the port of the SDH optical interface board transmits optical signals only when thelaser is turned on. You can turn a laser on or off by using the NMS.

7.10 Setting the ALS functionThe SDH optical interface board supports the automatic laser shutdown (ALS) function. It canturn off a laser when it does not carry services, the optical fiber is faulty, or the received opticalsignals are lost.

7.11 Setting the Automatic Release FunctionTo protect the NM and NE communication from improper operations, an NE supports theautomatic release of the ODU mute, loopback, and other operations that require you to exercisecaution. The automatic release time is five minutes by default. You can set whether to enablethe automatic release function and the automatic release time using the NMS.

7.12 Switching PXC BoardsManual PXC switching is an important maintenance operation.

7.13 Configuring 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.

7.14 Querying the Impedance of an E1 ChannelThe impedance of an E1 channel is 75 ohms or 120 ohms, which can be queried through theNMS but cannot be set through the NMS.

7.15 Using Ethernet Test FramesBy using the Ethernet test frames on the OptiX RTN 620, you can check the connectivity of theVCTRUNK.

7.16 Querying the Working Status of an Ethernet PortThrough the operation, you can learn about the enable/disable state, loopback status, and theactual working mode of an Ethernet port.

7.17 Setting the Threshold of Received Traffic Flow on an Ethernet PortThe FLOW_OVER alarm is reported when the traffic flow received on an Ethernet port exceedsthe specified threshold.

7.18 Performing Statistics for the Traffic Flow on an Ethernet PortYou can perform this operation to perform statistics for the traffic flow on an Ethernet port withina specified period.

7.19 Performing Statistics for the Traffic Flow of Ethernet ServicesYou can perform this operation to perform statistics for the traffic flow of Ethernet serviceswithin a specified period.

7.20 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.

7 Supporting TaskOptiX RTN 620 Radio Transmission System

Maintenance Guide


Issue 04 (2010-10-30)

7.1 Hardware LoopbackHardware loopback refers to the loopback operation performed by changing the physicalconnection.

Hardware loopback is classified into optical cable loopback, SDH/PDH cable loopback, andEthernet port loopback.l Optical cable loopback indicates that the receive and transmit optical fibers are connected

through a fiber jumper on the ODF. In certain occasions, an optical attenuator is addedbased on the actual situation, to prevent the optical board from being damaged by theexcessive receive optical power.

l SDH/PDH cable loopback indicates that the receive and transmit SDH/PDH cables areconnected through 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.

7.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.

7.2.1 Cleaning Fiber Connectors Using Cartridge CleanersWhen there are special cartridge cleaners (such as the CLETOP cassette cleaner), use them forcleaning the fiber connectors.

7.2.2 Cleaning Fiber Connectors Using Lens TissueWhen there is no cartridge cleaners, use the lens tissue for cleaning fiber connectors.

7.2.3 Cleaning Fiber Adapters Using Optical Cleaning SticksClean fiber adapters with optical cleaning sticks. This part describes the method of cleaning fiberadapters on the optical interface board. The method of cleaning fiber adapters on the opticalattenuators and flanges is the same.

7.2.1 Cleaning Fiber Connectors 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. Make sure that there is no laser light on the fiber

connector.l Inspect the fiber connector with a fiber microscope to make sure that the fiber connector

is contaminated.

Tools, Equipment, and MaterialsCartridge cleaner



7-3

Procedure

Step 1 Press down and hold the lever, and the shutter slides back and exposes a new cleaning area.

Figure 7-1 CLETOP cassette cleaner

Step 2 Position the fiber tip slightly against the cleaning area and drag the fiber tip slightly in thedownward direction.

Figure 7-2 Dragging the fiber tip slightly on one cleaning area


Maintenance Guide


Issue 04 (2010-10-30)

Step 3 Repeat the same in the other cleaning area in the same direction as Step 2.

Figure 7-3 Dragging the fiber tip slightly on the other cleaning area

Step 4 Release the lever to close the cleaning area.

----End

7.2.2 Cleaning Fiber Connectors Using Lens TissueWhen there is no cartridge cleaners, use the lens tissue for cleaning fiber connectors.

Prerequisitel Disconnect both ends of the fiber to be inspected. Make sure there is no laser light present

on the fiber connector.

l Inspect the fiber connector with a fiber microscope to make sure that the fiber connectoris contaminated.

Tools, Equipment, and Materialsl Clean solvent

l Non-woven lens tissue

l Special compressed gas



7-5

NOTE

l Using the isoamylol as the clean solvent is recommended, and the propyl can also be used. Do not use alcoholor formalin.

l The fiber cleaning tissue or lint-free wipes can replace the non-woven lens tissue.

l The special cleaning roll can replace the special compressed gas.

Procedure

Step 1 Place a small amount of cleaning solvent on the lens tissue.

Step 2 Drag the fiber tip slightly on the lens tissue.

Figure 7-4 Cleaning the fiber with the lens tissue

Step 3 Repeat step 2 several times on the areas of the lens tissue that have not been used.

Step 4 Using compressed gas, blow off the fiber tip.When using compressed gas:

l First spray it into the air as the initial spray of condensation can contain some sediment.

l Keep the injector nozzle as close as possible to the connector surface without touching it.

----End

7.2.3 Cleaning Fiber Adapters Using Optical Cleaning SticksClean fiber adapters with optical cleaning sticks. This part describes the method of cleaning fiberadapters on the optical interface board. The method of cleaning fiber adapters on the opticalattenuators and flanges is the same.


Maintenance Guide


Issue 04 (2010-10-30)

Prerequisitel Before you clean the fiber adapter, ensure that you remove the optical fiber and shut down

the laser. For details about how to shut down a laser, refer to 7.9 Setting the State of aLaser.

l Inspect the fiber adapter with a fiber microscope to ensure that the fiber adapter iscontaminated.

Tools, Equipment, and Materialsl Optical cleaning sticksl Clean solventl Special compressed gas

NOTE

l For the SC and FC optical interface, use the cleaning stick with a diameter of 2.5 mm, for the LC opticalinterface, use the cleaning stick with a diameter of 1.25 mm.

l The medical cotton or long fiber cotton can replace the optical cleaning stick.

l Using the isoamylol as the clean solvent is preferred, and the propyl can also be used. Do not use alcoholor formalin.

l The special cleaning roll can replace the special compressed gas.

Procedure

Step 1 Place a small amount of cleaning solvent on the optical cleaning stick.

Step 2 Hold the stick straight out from the adapter and turn the stick clockwise four to five times.Ensure that there is direct contact between the stick tip and fiber tip so that the solvent can cleanthe adapter tip.

Step 3 Using compressed gas, blow off the fiber tip.When using compressed gas:l First spray it into the air as the initial spray of condensation can contain some sediment.l Keep the injector nozzle as close as possible to the connector surface without touching it.

----End

7.3 Browsing Alarms, Abnormal Events, and PerformanceEvents

The Web LCT is used to browse alarms, abnormal events, and performance events at the NElayer.

7.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.

7.3.2 Checking the Board StatusYou can learn about the board status in a visual manner by checking the slot diagram.

7.3.3 Browsing the Current AlarmsYou can find the faults that occur on the equipment by browsing current alarms.



7-7

7.3.4 Browsing History AlarmsYou can know the faults that occur on the equipment in a past period of time by browsing historyalarms.

7.3.5 Browsing the Abnormal EventsPeriodically browsing abnormal events helps you to find abnormalities in the equipment in time.

7.3.6 Browsing Current Performance EventsPeriodically browsing the performance events helps you to check the long-term running statusof the equipment.

7.3.7 Browsing the History PerformancePeriodically browsing the performance events helps you to check the long-term running statusof the equipment.

7.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.

7.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


Tools, Equipment, and Materials

Web LCT

Procedure

Step 1 In NE List, check Communication Status of the NE.In normal cases, Communication Status is Normal.

Step 2 If Login Status of the NE is Not Logged In, log in to the NE.1. Select the NE, and choose NE Login.

The NE Login dialog box is displayed.2. Specify User Name and Password.

l The user name is lct by default.

l The password of user lct is password by default.

NOTE

User lct has the authority at the system level.

3. Click OK.The Login Status column switches to Logged In.

Step 3 Click NE Explorer.

Step 4 Check NE STATE above Slot Layout.


Maintenance Guide


Issue 04 (2010-10-30)

In normal cases, NE STATE is Running.

----End

7.3.2 Checking the Board StatusYou can learn about the board status in a visual manner by checking the slot diagram.


Tools, Equipment, and MaterialsWeb LCT

Procedure

Step 1 Double-click an NE in the Main Topology. Then, the Slot Layout is displayed. The NE shouldbe in Running Status.

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

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

----End

7.3.3 Browsing the Current AlarmsYou can find the faults that occur on the equipment by browsing current alarms.



Procedure

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



7-9

TIP

You can also click an alarm indicator on the toolbar to display the alarms of the specific severity.

From left to right, the alarm indicators and related alarm severities are as follows:

l Red: critical alarm

l Orange: major alarm

l Yellow: minor alarm

l Purple: warning

l Light blue: abnormal event

NOTE

The number shown by each indicator indicates the number of current network-wide alarms, which are notcleared, of the specific severity.

The Browse Current Alarms tab is displayed by default.

Step 2 Browse the displayed alarms.

Step 3 Select the newly generated alarms, record the details of the alarms.

Step 4 Notify the troubleshooting personnel to clear the alarms in time.

----End

Related InformationA current alarm refers to an alarm that is not cleared.

7.3.4 Browsing History AlarmsYou can know the faults that occur on the equipment in a past period of time by browsing historyalarms.



Procedure

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

Step 2 Click the Browse History Alarm tab.

Step 3 Click Filter. The Filter dialog box is displayed.1. In Severity, select the alarm severity to be queried.2. In Alarm Type, select the alarm type.3. In Rising Time, specify the alarm generation time.4. In Cleared Time, specify the alarm clearance time.


Maintenance Guide


Issue 04 (2010-10-30)

The start time should be the time when the last history alarm browsing operation wasperformed, and the end time should be the current time.

Step 4 Click Filter.

Step 5 Browse the displayed history alarms.

Step 6 Optional: Click Save As. Then, the history alarms are saved and archived as a file.

----End

Related Information

A history alarm is an alarm that has been cleared. An NE stores a maximum of 1,000 historyalarms.

7.3.5 Browsing the Abnormal EventsPeriodically browsing abnormal events helps you to find abnormalities in the equipment in time.



Web LCT

Procedure

Step 1 Select an NE from the NE Explorer, and choose Alarm > Browse Abnormal Events from theFunction Tree.

TIP

Alternatively, you can select an NE and then click the icon to switch to the Browse AbnormalEvents tab page.

Step 2 Click Filter. The Filter dialog box is displayed.1. Set Level and Type.2. In Abnormal Event, select Select All.

Step 3 Click OK.

Step 4 Browse the abnormal events.

Step 5 Optional: Click Save As. Then, the abnormal events are saved and archived as a file.

----End

Related Information

An abnormal event is an abnormality that arises in the system at a particular time and not anabnormality that persists for a long time. Being different from alarms, an abnormal event hasonly occurrence time, with clearance time not provided.



7-11

7.3.6 Browsing Current Performance EventsPeriodically browsing the performance events helps you to check the long-term running statusof the equipment.

Prerequisitel The performance monitoring function must be enabled.l The NE user must have the authority of NE monitor or higher.


Procedure

Step 1 In the NE Explorer, select the required board from the Object Tree, and then choosePerformance > Current Performance from the Function Tree.


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

Step 4 Click Count, select all the performance events, and select Consecutive Severely ErroredSecond in Display Options.

Step 5 Click Query.

Step 6 Browse the current performance events.In normal cases, no bit error performance events is displayed, and the number of pointerjustification events is less than six per day on each port.

Step 7 Click Gauge, select all the performance events, and select Current Value and Maximum/Minimum Value in Display Options.

Step 8 Click Query.

Step 9 Browse the current performance events.Compared with the history records, the gauge indicators, such as board temperature, do notchange drastically.

Step 10 Set Monitor Period to 24-Hour.

Step 11 Repeat steps Step 4 to Step 9 query the performance events in a period of 24 hours.

----End

Related InformationThe counter of current performance events measures all the performance events that arisebetween the start time of the monitoring period and the current time.

7.3.7 Browsing the History PerformancePeriodically browsing the performance events helps you to check the long-term running statusof the equipment.


Maintenance Guide


Issue 04 (2010-10-30)



Web LCT

Procedure

Step 1 Select a specific board from the NE Explorer, and choose Performance > HistoryPerformance from the Function Tree.


Step 3 Select 15-Minute after Monitor Period.

Step 4 Specify the start time and end time of a specific time span. The time span starts from the timewhen the last history performance event browsing operation was performed to the current time.

Step 5 Select all the available performance events in Count, and select Zero Data in DisplayOptions.


Step 7 Click Save As.The system displays the text file that lists the history performance events.

NOTE

You can also save the text file as required.



Step 10 Click Save As to save the performance events.The system displays the text file that lists the history performance events.

NOTE

You can also save the text file as required.

Step 11 Select 24-Hour after Monitor Period.

Step 12 Repeat Step 4 to Step 10 to query the history performance events in a period of 24 hours.

----End

Related Information

The history performance event refers to a performance event whose statistics period ends in thepast. Only the performance events on the NE side can be queried using the Web LCT. Currently,the NE can store thirty 24-hour and six hundreds and seventy-two 15-minute history performanceevents related to the receive level and bit errors on the radio link; the NE can store a maximumof six 24-hour and sixteen 15-minute other history performance events.



7-13

7.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 In the NE Explorer, select the required board, and then choose Performance > PerformanceThreshold-Crossing from the Function Tree.The Performance Threshold-Crossing dialog box is displayed.



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

Step 5 In Performance Event Type, select Select All.

Step 6 Optional: Specify Display Options.

Step 7 Click Query. Browsing the threshold-crossing performance events.



NOTE



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

----End

7.4 Querying a ReportYou can obtain the version, manufacture, and radio link information of all the boards by queryingthe corresponding report.

7.4.1 Querying a Board Information Report Through the Web LCTYou can know the PCB version, logic version, and software version of each board by queryinga board information report.


Maintenance Guide


Issue 04 (2010-10-30)

7.4.2 Querying a Board Manufacture Information ReportYou can know the manufacture information of each board and the SFP module by querying aboard manufacture information report.

7.4.3 Querying the Status of a Radio LinkThe Web LCT supports the end-to-end management of a microwave link. You can query theinformation about the two ends of a radio link in an interface.

7.4.1 Querying a Board Information Report Through the Web LCTYou can know the PCB version, logic version, and software version of each board by queryinga board information report.



Web LCT

Procedure

Step 1 Select an NE from the Object Tree in the NE Explorer.

Step 2 Choose Report > Board Information Report from the Function Tree.

Step 3 All the board version information of the NE is displayed in the Board Information Report tabpage.


The text file that describes the board information is displayed on the Internet Explorer.

NOTE

You can save the text file as required.

----End

Related Information

Focus on the PCB version, logic version, and software version of each board when you querythe board information.

7.4.2 Querying a Board Manufacture Information ReportYou can know the manufacture information of each board and the SFP module by querying aboard manufacture information report.

Prerequisitel The communication between the Web LCT and the NE must be normal.




7-15


Web LCT

Procedure


Step 2 Choose Report > Board Detail Information Report from the Function Tree.

Step 3 All the board manufacture information of the NE is displayed in the Board Detail InformationReport tab page.


The text file that describes the detailed board information is displayed on the Internet Explorer.

NOTE

You can save the text file as required.

----End

7.4.3 Querying the Status of a Radio LinkThe Web LCT supports the end-to-end management of a microwave link. You can query theinformation about the two ends of a radio link in an interface.


l The NE user must have the authority of Maintenance Level or higher.

Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer, and then choose Configuration > LinkConfiguration from the Function Tree.

Step 2 Click the IF/ODU Configuration tab page, right-click the corresponding IF board, and thenchoose HOP Management from the shortcut menu.

Step 3 In the HOP Management Function Tree, choose Configuration > Link Configuration, andthen click the IF/ODU Configuration tab.

Step 4 Select the corresponding IF board in the IF/ODU Configuration tab page, and then clickQuery.The configuration information of the links at two ends is displayed.

Step 5 Check whether the configuration information of the link at one end is consistent with theconfiguration information of the link at the other end and whether the configuration informationof the links at the two ends is correct.

----End


Maintenance Guide


Issue 04 (2010-10-30)

7.5 Software loopbackSoftware loopback refers to the loopback operation that is implemented by using the NMS. Inthe OptiX RTN 620, the SDH optical interface board, SDH electrical interface board, PDHinterface board, IF board, Ethernet service processing board, and ODU support loopback.

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

7.5.1 Setting Loopback for the SDH Optical Interface BoardThe optical interface board (SL1/SD1/SL4) supports the optical interface inloop and the VC-4path outloop. The SL4 board also supports the VC-4 path inloop.

Prerequisitel The communication between the Web LCT and the NE must be normal.l The NE user must have the authority of Maintenance Level or higher.

ContextThe optical interface inloop is a process where the signals at an SDH port are looped back at theoverhead processing unit towards the backplane.

Figure 7-5 Inloop

SDH opticalinterface boardBackplane

SDH



7-17

The optical interface outloop is a process where the signals at an SDH port are looped back atthe overhead processing unit towards the remote equipment.

Figure 7-6 Outloop


SDH

The VC-4 path outloop is a process where the signals on a VC-4 path are looped back at thelogic processing unit towards the remote equipment.

Figure 7-7 VC-4 path outloop


VC-4

The VC-4 path inloop is a process where the signals on a VC-4 path are looped back at the logicprocessing unit towards the backplane.

Figure 7-8 VC-4 path inloop

SDH opticalboardBackplane

VC-4


Maintenance Guide


Issue 04 (2010-10-30)

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 cleared automatically after some time (by default, it is cleared

within five minutes). For details, see 7.11 Setting the Automatic Release Function.

Procedure

Step 1 Select the SDH optical interface board from the Object Tree.

Step 2 Choose Configuration > SDH Interface from the Function Tree.

Step 3 Choose By Function, and select the loopback mode from the drop-down list.

To Perform Select

Optical interface loopback Optical (Electrical) Interface Loopback

VC-4 path loopback VC-4 Loopback

Step 4 Set the loopback status of the port or path according to the requirements.

Step 5 Click Apply.The system displays a prompt dialog box for confirmation.

Step 6 Click OK.

----End

7.5.2 Setting Loopback for the SDH Electrical Interface BoardThe electrical interface board supports the electrical interface inloop/outloop and the VC-4 pathoutloop.


ContextThe electrical interface inloop is a process where the signals at an SDH port are looped back atthe coding/decoding unit towards the backplane.



7-19

Figure 7-9 Inloop

SDH electricalinterface boardBackplane

SDH

The electrical interface outloop is a process where the signals at an SDH port are looped backat the coding/decoding unit towards the remote equipment.

Figure 7-10 Outloop

SDH


The VC-4 path outloop is a process where the signals on a VC-4 path are looped back at thelogical processing unit towards the remote equipment.


VC-4



Maintenance Guide


Issue 04 (2010-10-30)

Precautions



ProcedureStep 1 Select the SDH electrical interface board from the Object Tree.

Step 2 Choose Configuration > SDH Interface from the Function Tree.


To Perform Select

Optical interface loopback Optical (Electrical) Interface Loopback




Step 6 Click OK.

----End

7.5.3 Setting Loopback for the Tributary BoardThe tributary board supports the tributary inloop/outloop.


ContextThe tributary inloop is a process where the signals at a PDH port are looped back at the coding/decoding unit towards the backplane.

Figure 7-12 Inloop

PDH interface boardBackplane

PDH



7-21

The tributary inloop is a process where the signals on a tributary path are looped back at thePDH interface board of the local IDU towards the remote equipment.

Figure 7-13 Outloop

PDH

PDH interface boardBackplane

Precautions



Procedure

Step 1 Select the PDH interface board from the Object Tree.

Step 2 Choose Configuration > PDH Interface from the Function Tree.

Step 3 Choose By Function, and select Tributary Loopback from the drop-down list.



Step 6 Click OK.

----End

7.5.4 Setting Loopback for the IF BoardThe loopbacks on the IF board are classified into IF port loopback, port loopback, and VC-4path loopback. The IF1A/IF1B board supports the IF port inloop/outloop and VC-4 path inloop.The IF0A/IF0B board supports the IF port inloop/outloop and port inloop/outloop. The IFXboard supports port inloop/outloop and VC-4 path inloop. The IFH2 board supports the IF portoutloop and the port inloop/outloop.


Maintenance Guide


Issue 04 (2010-10-30)


ContextThe IF port inloop is a process where the IF signals are looped back at the modem unit towardsthe backplane.

Figure 7-14 Inloop

IF boardBackplane

IF signal

The IF port outloop of the IDU 620 is a process where the IF signals are looped back at themodem unit of the board towards the remote equipment.

Figure 7-15 Outloop

IF boardBackplaneIF signal

The port inloop is a process where the microwave frame baseband signals are looped back atthe MUX/DEMUX unit of the board towards the backplane.

Figure 7-16 Inloop

IF boardBackplaneMicrowave

baseband signal



7-23

The port outloop is a process where the microwave frame baseband signals are looped back atthe MUX/DEMUX unit of the board towards the remote equipment.

Figure 7-17 Outloop

IF boardBackplaneMicrowavebaseband

signal

The VC-4 path inloop is a process where the signals on a VC-4 path are looped back at the logicalprocessing unit of the board towards the backplane.


IF boardBackplane

VC-4 signal

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 cleared automatically after some time (by default, it is clearedwithin five minutes). For details, see 7.11 Setting the Automatic Release Function.

l To perform the software loopback on the protection IF board of 1+1 HSB/FD/SD, switch theprotection IF board to the working state manually. Otherwise, the operation may fail.

l Before performing the loopback operation for the IFH2, disable the AM function at the twoends of a link.


Maintenance Guide


Issue 04 (2010-10-30)

ProcedureStep 1 Select the IF board from the Object Tree.

Step 2 Select the corresponding menu from the Function Tree according to the loopback mode.

To Perform Choose

IF port loopback Configuration > IF Interface.

Port loopback Configuration > Digital Interface

VC-4 path loopback Configuration > Digital Interface


To Perform Choose

IF port loopback IF Port Loopback

Port loopback Optical (Electrical) Interface Loopback




Step 6 Click OK.

----End

7.5.5 Setting Loopback for the Ethernet Service Processing BoardThe Ethernet service processing board supports the Ethernet port inloop (at the MAC layer andPHY layer) and VC-3 path inloop and outloop.


ContextThe Ethernet port MAC inloop is a process where the Ethernet physical signals are looped backat the service processing module of the board at the MAC layer toward the backplane. TheEthernet port PHY inloop is a process where the Ethernet frame signals are looped back at theinterface module of the board at the MAC layer toward the backplane.

Figure 7-19 Inloop

Ethernet serviceprocessing boardBackplane

PHYMAC



7-25

The VC-3 path inloop is a process where the signals on a VC-3 path are looped back at the logicalprocessing unit of the board towards the backplane.


Ethernet serviceprocessing board

Backplane

VC-3 signal

The VC-3 path outloop is a process where the signals on a VC-3 path are looped back at thelogical processing unit towards the remote equipment.


VC-3 signal

Ethernet serviceprocessing boardBackplane

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 cleared automatically after some time (by default, it is clearedwithin five minutes). For details, see 7.11 Setting the Automatic Release Function.

Procedure

Step 1 Select the Ethernet processing board from the Object Tree.

Step 2 Select the corresponding menu from the Function Tree according to the loopback mode.


Maintenance Guide


Issue 04 (2010-10-30)

To perform Choose

PHY loopback Configuration > Ethernet Interface Management > EthernetInterface > External Port > Basic Attributes

MAC loopback Configuration > Ethernet Interface Management > EthernetInterface > External Port > Basic Attributes

VC-3 path loopback Configuration > SDH Interface

Step 3 Select the loopback mode.

To perform Select

PHY loopback PHY Loopback

MAC loopback MAC Loopback

VC-3 path loopback VC-3 loopback



Step 6 Click OK.

----End

7.5.6 Locating the Fault by Performing LoopbacksLoopback is a common method to locate the fault.


Service TrailFigure 7-22 shows how to locate a fault by performing the loopback.



7-27

Figure 7-22 Service Trail

IF Board PXC SDH InterfaceBoard

ODU

NE2

ODU

NE3

Fiber

ODU

NE4

IF BoardPXC ODU

NE1

PDH TributaryBoard

PDH TributaryBoard

PXC IF Board IF Board PXC SDH InterfaceBoard

ProcedureStep 1 If the services are available on the radio links, first perform the inter-station loopback to locate

the fault on a certain hop when using the loopback method.1. Set the outloops for the SDH optical interface boards on NE2 and NE3, and then perform

the inter-station loopback to locate the fault.

Step 2 After the fault is located to a certain radio link, perform the intra-station loopback to locate thefault to a certain NE or board.1. Set inloop for the IF board on the NEs at two ends of the radio link where the fault occurs,

and then locate the fault to the service receiver or the radio link.2. If the fault is located in the service receiver, set outloop for the PDH tributary board to

locate the fault to the interface board or the cross-connect board.3. If the radio link is faulty, replace the board to locate the fault to the IF board or the ODU.

----End

7.6 ResettingResetting is an important method for handling software faults. The OptiX RTN 620 supportscold resetting, warm resetting, and SCC resetting.

7.6.1 Cold ResettingCold resetting is a process where the board software is reset and the board is re-initiated. Exceptthat the board software of the EMS6 is independently located, the software modules of all otherboards are located in the SCC. During the board initialization, the FPGA, if any, is re-loaded.

7.6.2 Warm Resetting


Maintenance Guide


Issue 04 (2010-10-30)

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

7.6.3 SCC ResettingSCC resetting is a process in which all the software modules on the SCC are reset, the SCC isre-initiated.

7.6.1 Cold ResettingCold resetting is a process where the board software is reset and the board is re-initiated. Exceptthat the board software of the EMS6 is independently located, the software modules of all otherboards are located in the SCC. During the board initialization, the FPGA, if any, is re-loaded.

Prerequisitel The Web LCT is in normal communication with the NE.l The NE user must have the authority of Maintenance Level or higher.

Precautions

CAUTIONCold resetting causes service interruption because it is similar to the procedure of removing andinserting a board.

Procedure

Step 1 In Slot Layout of the Web LCT, right-click the board to be cold reset.

Step 2 Choose Cold Reset in the popup menu.The system displays the Operation success dialog box.

Step 3 Click Close.

----End

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


PrecautionsDuring the warm resetting, the running services are not affected.



7-29

Procedure

Step 1 In the Slot Layout of the Web LCT, right-click the board to be reset.

Step 2 Choose Warm Resetting in the popup menu.The system displays the Operation Succeed dialog box.

Step 3 Click Close.

----End

7.6.3 SCC ResettingSCC resetting is a process in which all the software modules on the SCC are reset, the SCC isre-initiated.

Prerequisitel The Web LCT is in normal communication with the NE.


Precautions

During the resetting, protection switching and NMS operations are unavailable although therunning services are not affected.

Procedure

Step 1 In the Slot Layout of the Web LCT, right-click the SCC to be reset.

Step 2 Choose SCC Reset from the shortcut menu.A prompt dialog box is displayed.

Step 3 Click OK.The system displays the Operation Succeed dialog box.

Step 4 Click Close.

----End

7.7 PRBS TestThe pseudorandom binary sequence (PRBS) test is an important method for networkmaintenance and self-check.

7.7.1 PRBS Test of the Tributary BoardIn the absence of a special test tool, you can perform the PRBS test by using the embedded testsystem on the PDH interface board.

7.7.2 PRBS Test of the IF BoardIn the absence of a special test tool, you can perform the PRBS test by using the embedded testsystem on the IFH2 IF board.


Maintenance Guide


Issue 04 (2010-10-30)

7.7.1 PRBS Test of the Tributary BoardIn the absence of a special test tool, you can perform the PRBS test by using the embedded testsystem on the PDH interface board.


ContextThe OptiX RTN 620 supports the PRBS test in the tributary direction and the cross-connectdirection.

The PRBS test in the tributary direction can be used to check the connection between the tributaryboard and the DDF, as shown in Figure 7-23.

Figure 7-23 PRBS test in the tributary direction

PRBSTransmitter

PRBSRecevicer

PDH interface boardDDF frame

1

1 Inloop at the DDF frame

The PRBS test in the cross-connect direction can be used to check the connection between thetributary board and the remote NE, as shown in Figure 7-24.

Figure 7-24 PRBS test in the cross-connect direction

Cross-connectboard

PRBSTransmitter

PRBSReceiver

PDH interfaceboard IF board

Local NE Remote NE

IN

OUT

VC4 inloop orport inloop IF port inloop IF port outloop1

2 3

2 3

IF board

1

a) IF board working as line board



7-31

Cross-connectboard

PRBSTransmitter

PRBSReceiver

PDH interfaceboard

SDH optical/electrical board

Local NE Remote NE

IN

OUT

VC4 inloop Port inloop Port outloop1

2 3

2 3

1

SDH optical/electrical board

b) SDH optical/electrical board working as line 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.

ProcedureStep 1 Set the loopback at the proper location. For details, see Figure 7-23 and Figure 7-24.

Step 2 Select an E1 interface board from the Object Tree in the NE Explorer.

Step 3 Choose Configuration > PRBS Test from the Function Tree.The PRBS Test tab page is displayed.

Step 4 Select the port to be tested.

Step 5 Specify Direction, Duration, and Measured in Time.NOTE

l The PRBS test supports three time units: one second, 10 minutes, and one hour.l A maximum of 255 test cycles is permissible for the PRBS test.

Step 6 Optional: Select Accumulating Mode.

Step 7 Click Start the test.The The operation may interrupt the service. Are you sure to continue? dialog box isdisplayed.

Step 8 Click OK.

Step 9 When Progress in the PRBS Test tab page is displayed as 100%, click Query to check the testresult.


Maintenance Guide


Issue 04 (2010-10-30)

NOTE

The result of the PRBS test can be normal, error, or invalid.

l Normal: It indicates that the path is working properly. The number of PRBSs should be zero, and thecurve should be in green.

l Error: It indicates that the path has errors. The number of PRBSs should be greater than zero, and thecurve should be in red.

l Invalid: It indicates that no bit is received. The curve should be in yellow.

----End

7.7.2 PRBS Test of the IF BoardIn the absence of a special test tool, you can perform the PRBS test by using the embedded testsystem on the IFH2 IF 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.

l To perform the PRBS test for the protection IF board of the 1+1 HSB/FD/SD, you mustswitch the protection IF board to the working state manually.

Procedure

Step 1 See 7.5.4 Setting Loopback for the IF Board to perform the inloop on the ODU.

Step 2 Select an IF board from the Object Tree in the NE Explorer.

Step 3 Choose Configuration > PRBS Test from the Function Tree.The PRBS Test tab page is displayed.

Step 4 Select the port to be tested.

Step 5 Specify Direction, Duration, and Measured in Time.

NOTE

l The PRBS test supports three time units: one second, 10 minutes, and one hour.

l A maximum of 255 test cycles is permissible for the PRBS test.

Step 6 Optional: Select Accumulating Mode.

Step 7 Click Start the test.



7-33

The The operation may interrupt the service. Are you sure to continue? dialog box isdisplayed.

Step 8 Click OK.

Step 9 When Progress in the PRBS Test tab page is displayed as 100%, click Query to check the testresult.

NOTE

The result of the PRBS test can be normal, error, or invalid.

l Normal: It indicates that the path is working properly. The number of PRBSs should be zero, and thecurve should be in green.

l Error: It indicates that the path has errors. The number of PRBSs should be greater than zero, and thecurve should be in red.

l Invalid: It indicates that no bit is received. The curve should be in yellow.

----End

7.8 Querying the License CapacityYou can check whether the loaded license file meets the requirements by querying the licensecapacity.



Procedure


Step 2 Choose Configuration > License Management from the Function Tree.

Step 3 Click Query in the License Management tab page.

Step 4 Browse the license information that is displayed.

----End

7.9 Setting the State of a LaserA laser on the port of the SDH optical interface board transmits optical signals only when thelaser is turned on. You can turn a laser on or off by using the NMS.



Maintenance Guide


Issue 04 (2010-10-30)

Procedure

Step 1 Select an SDH optical interface board from the NE Explorer.

Step 2 Choose Configuration > SDH Interface from the Function Tree, and then click the SDHInterface tab.

Step 3 Select By Function.

Step 4 Select Laser Switch from the drop-down list.

Step 5 Select a port, and then specify Laser Switch.

Step 6 Click Apply.

----End

7.10 Setting the ALS functionThe SDH optical interface board supports the automatic laser shutdown (ALS) function. It canturn off a laser when it does not carry services, the optical fiber is faulty, or the received opticalsignals are lost.



Procedure

Step 1 Select an SDH optical interface board from the Object Tree in the NE Explorer.

Step 2 Choose Configuration > Automatic Laser Shutdown from the Function Tree, and then clickthe Laser Auto Shutdown tab.

Step 3 Select Enable for Auto Shutdown.

Step 4 Click Apply to save the settings.

----End

7.11 Setting the Automatic Release FunctionTo protect the NM and NE communication from improper operations, an NE supports theautomatic release of the ODU mute, loopback, and other operations that require you to exercisecaution. The automatic release time is five minutes by default. You can set whether to enablethe automatic release function and the automatic release time using the NMS.





7-35

Procedure


Step 2 Choose Configuration > Automatic Disabling of NE Function from the Function Tree.

Step 3 Specify Auto Disabling and Auto Disabling Time (min).

Step 4 Click Apply to complete the settings for the automatic release function.

----End

7.12 Switching PXC BoardsManual PXC switching is an important maintenance operation.


l Two PXC boards must be configured.

l The user must have the system level authority.

Procedure

Step 1 Select an NE from the Object Tree in the NE Explorer, and then choose Configuration > Board1+1 Protection from the Function Tree.

Step 2 Select the ID of the protection group where the PXC board resides in the Board 1+1Protection tab page.

Step 3 Click Working/Protection Switching.

Step 4 Click OK to perform switching.

Step 5 Click Query.The switching status is displayed.

----End

7.13 Configuring 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.

Prerequisite

The NE user must have the authority of Operation Level or higher.


Web LCT


Maintenance Guide


Issue 04 (2010-10-30)

Procedure

Step 1 In the NE Explorer, select the NE and then choose Performance > NE Performance MonitorTime from the Function Tree.

Step 2 Set the parameters of NE performance monitoring.

1. Select 15-Minute or 24-Hour.2. Select Enable or Disable in Set 15-Minute Monitoring or Set 24-Hour Monitoring.3. Set the start time and end time of the performance monitoring of NEs.

NOTE

l Set 15-Minute Monitoring and Set 24-Hour Monitoring are generally set to Enable.

l You can specify the start time of the performance monitoring function, only after selecting Enable 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.

Step 3 Click Apply.

----End

7.14 Querying the Impedance of an E1 ChannelThe impedance of an E1 channel is 75 ohms or 120 ohms, which can be queried through theNMS but cannot be set through the NMS.




7-37



Procedure

Step 1 Select A PDH tributary board from the Object Tree in the NE Explorer.

Step 2 Choose Configuration > PDH Interface from the Function Tree.

Step 3 Select By Board/Port(Channel).

Step 4 Select Port in the list.

Step 5 Select a port, and check Port Impedance.

----End

7.15 Using Ethernet Test FramesBy using the Ethernet test frames on the OptiX RTN 620, you can check the connectivity of theVCTRUNK.

Prerequisitel The communication between the Web LCT and the NE must be normal.l The NE user must have the authority of Maintenance Level or higher.l The service traffic must be encapsulated or mapped through the GFP method.

ContextFor test purposes, the Ethernet board transmits, at an interval of about one second, one specificGFP management frame or Ethernet frame to the opposite Ethernet board, which then returnswith a response frame. After receiving the response frame, the local Ethernet board can determinethe connectivity of the VCTRUNK in between.

Figure 7-25 Ethernet test frames between Ethernet boards

LocalEhernetboard

RemoteEhernetboard

Test frame

Response frame


Maintenance Guide


Issue 04 (2010-10-30)

Precautions

CAUTIONDo not use the test frames when the network traffic is heavy.

Procedure

Step 1 Select an Ethernet board from the Object Tree in the NE Explorer.

Step 2 Choose Configuration > Ethernet Maintenance > Ethernet Test from the Function Tree.The Ethernet Test tab page is displayed.

Step 3 Select the port to be tested, click Clear Counters, and then select Clear All Counters from thedrop-down list.

Step 4 Specify Send Mode and Frames to Send.

NOTE

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

Step 5 Click Apply.The test frames start to be received and transmitted.

Step 6 When Status changes to Finished Sending, click Query.

Step 7 View Counter of Frames Sent and Counter of Received Response of Test Frame.Test frames are used to check the network connectivity. If certain test frames are lost but noalarm is reported on the SDH side, you can infer that the network connectivity is in a goodcondition. If no test frame is received, you can infer that network is faulty.

----End

Related InformationIf you choose the "Continue" mode, the local port transmits test frames continuously after youstart the test until the mode changes to "Disable".

7.16 Querying the Working Status of an Ethernet PortThrough the operation, you can learn about the enable/disable state, loopback status, and theactual working mode of an Ethernet port.





7-39

Procedure

Step 1 Select an Ethernet board or IFH2 board from the Object Tree.

Step 2 Choose Configuration > Ethernet Interface Management > Ethernet Interface from theFunction Tree.

Step 3 Select External Port.

Step 4 By default, click the Basic Attributes tab page.

Step 5 Check Enabled/Disabled, Working Mode, and Port Physical Parameters of the associatedport.

----End

7.17 Setting the Threshold of Received Traffic Flow on anEthernet Port

The FLOW_OVER alarm is reported when the traffic flow received on an Ethernet port exceedsthe specified threshold.



Web LCT

Context

This operation can be performed on the PORT port of the EMS6 board.

Procedure

Step 1 Select the required Ethernet board from the Object Tree.

Step 2 Choose Configuration > Ethernet Interface Management > Ethernet Interface from theFunction Tree.

Step 3 Select External Port.

Step 4 Select the Advanced Attributes tab.

Step 5 Set Zero-Flow Monitor to Enable.

Step 6 Set Flow Threshold(Mbps).

Step 7 Optional: Set Zero-Flow Monitor Interval(min).l If this parameter takes the default value of 0, the FLOW_OVER alarm is reported whenever

the traffic flow received on the port exceeds Flow Threshold(Mbps).


Maintenance Guide


Issue 04 (2010-10-30)

l If the value of this parameter is not 0, the FLOW_OVER alarm is reported only when thetraffic flow received on the port within a period of Zero-Flow Monitor Interval(min) alwaysexceeds Flow Threshold(Mbps).

Step 8 Click Apply.

----End

7.18 Performing Statistics for the Traffic Flow on an EthernetPort

You can perform this operation to perform statistics for the traffic flow on an Ethernet port withina specified period.

Prerequisitel The Web LCT is in normal communication with the NE.l The NE user must have the authority of Maintenance Level or higher.l The flow monitoring function must be enabled on the associated Ethernet port. To enable

the flow monitoring function on a port, do as follows:

1. Select the required Ethernet board from the Object Tree.2. Choose Performance > Ethernet Port Traffic Monitor from the Function Tree.3. Select the Set Monitoring tab.4. Set Monitor Status to Enabled for the Ethernet port.

Tools, Equipment and MaterialsWeb LCT

Contextl After the flow monitoring function is enabled, the system saves the statistics about the

received traffic and transmitted traffic with an interval of 15 minutes. In normal cases, thesystem stores the statistics that are collected in the last 30 days. In the system, everymeasurement entry shows the average transmit rate and average receive rate within a periodof 15 minutes. You can query the statistics in the last 30 days.

l This operation can be performed on the PORT port and VCTRUNK port of the EMS6board.

Procedure


Step 2 Choose Performance > Ethernet Port Traffic Monitor from the Function Tree.

Step 3 Select the Query traffic tab.

Step 4 Set the object to be queried, the required time, and display mode, and then click Query.The system displays the query result in a table or in a graph.

----End



7-41

7.19 Performing Statistics for the Traffic Flow of EthernetServices

You can perform this operation to perform statistics for the traffic flow of Ethernet serviceswithin a specified period.

Prerequisitel The Web LCT is in normal communication with the NE.


l The flow monitoring function must be enabled. To enable the flow monitoring function,do as follows:

1. Select the required Ethernet board from the Object Tree.

2. Choose Configuration > QoS Management > Flow Management from the FunctionTree.

3. Set Monitor Status to Enabled for the traffic flow.


Web LCT

Contextl After the flow monitoring function is enabled, the system saves the statistics about the

received traffic and transmitted traffic with an interval of 15 minutes. In normal cases, thesystem stores the statistics that are collected in the last 30 days. In the system, everymeasurement entry shows the average transmit rate and average receive rate within a periodof 15 minutes. You can query the statistics in the last 30 days.

l This operation can be performed on the EMS6 board.

Procedure


Step 2 Choose Performance > Flow Traffic Monitor from the Function Tree.

Step 3 Set the object to be queried, the required time, and display mode, and then click Query.The system displays the query result in a table or in a graph.

----End

7.20 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.


Maintenance Guide


Issue 04 (2010-10-30)

Prerequisite

The NE user must have the authority of Maintenance Level or higher.


Web LCT

Context

A mirror listened port carries the Ethernet data that needs to be monitored and analyzed. A mirrorlistener port is not configured with any services. The Ethernet data received or transmitted bythe mirror listened port is duplicated and then sent to the mirror listener port that is connectedto an Ethernet analyzer.

Figure 7-26 Schematic diagram of Ethernet port mirroring

Mirror listened port

Ethernet processing unit

Mirror listener port

Ethernet equipment

Ethernet analyzerDuplication

Port mirroring is available in uplink port mirroring and downlink port mirroring. That is, theport mirroring function can monitor Ethernet data in the uplink and downlink directions.

As shown in Figure 7-27, the uplink mirroring direction refers to the direction from an externalEthernet port to the SDH/PDH side. After uplink mirroring is configured for PORT1, theEthernet data in the uplink direction of the mirror listened port PORT1 is duplicated and sent tothe mirror listener port PORT2. In the manner, you can monitor the Ethernet data in the uplinkdirection of PORT1 by means of PORT2.

Figure 7-27 Uplink mirroring direction

DA SA CVLAN SVLAN PayloadDA SA CVLAN PayloadEthernet

processing unit

PORT1 VCTRUNK1

PORT2

DA SA CVLAN Payload

As shown in Figure 7-28, the downlink mirroring direction refers to the direction from the SDH/PDH side to an external Ethernet port. After downlink mirroring is configured for PORT1, theEthernet data in the downlink direction of the mirror listened port PORT1 is duplicated and sentto the mirror listener port PORT2. In the manner, you can monitor the Ethernet data in thedownlink direction of PORT1 by means of PORT2.



7-43

Figure 7-28 Downlink mirroring direction

DA SA CVLAN SVLAN PayloadDA SA CVLAN PayloadEthernet

processing unit

PORT1 VCTRUNK1

PORT2

DA SA CVLAN Payload

Procedure

Step 1 Select the required Ethernet board in the Object Tree.

Step 2 Choose Configuration > Ethernet Interface Management > Port Mirroring from theFunction Tree.

Step 3 Click New. In the Port Mirror Management dialog box that is displayed, set Mirror ListenerPort, Uplink Listened Port, and Downlink Listened Port. Then, click OK.

NOTE

l You need to set an idle port that is not configured with services as Mirror Listener Port.l If Mirror Listener Port is an external port, duplicated packets flow along the downlink direction of

the external port. If Mirror Listener Port is a VCTRUNK port, duplicated packets flow along theuplink direction of the VCTRUNK port.

----End


Maintenance Guide


Issue 04 (2010-10-30)

A Alarm Reference

Alarms are important indicators when exceptions occur on the equipment. This topic describesall the possible alarms on the OptiX RTN 620 and how to handle these alarms.

A.1 Alarm ListThe following table lists all the possible alarms generated by the OptiX RTN 620 in alphabeticalorder.

A.2 Alarms and Handling ProceduresThis topic describes all the alarms on the OptiX RTN 620 in an alphabet order and how to handlethese alarms.

OptiX RTN 620 Radio Transmission SystemMaintenance Guide A Alarm Reference


A-1

A.1 Alarm ListThe following table lists all the possible alarms generated by the OptiX RTN 620 in alphabeticalorder.

Table A-1 Alarm list

Alarm Name Description AlarmSeverity

Source

A_LOC Loss of clock on the adding bus Major PO1, PH1, PD1, PL3

APS_MANUAL_STOP

MSP protocol stopped manually Minor SCC

ALM_GFP_dCSF Loss of GFP client signals Critical EFT4, EMS6, EFP6

ALM_GFP_dLFD GFP frames are out of frame. Major EFT4, EMS6, EFP6

AM_DOWNSHIFT Downshift of AM modes Major IFH2

APS_FAIL The APS protection switchingfails.

Major SCC

APS_INDI Indication of the APS protectionswitching

Major SCC

AU_AIS AU alarm indication Major SD1, SL1, SDE,SLE, IF1A, IF1B,IFX, SL4

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

B1_EXC Excessive regenerator section(B1) errors

Minor SD1, SL1, SDE,SLE, IF1A, IF1B,IF0A, IF0B, IFX,SL4

B1_SD Signal degradation due toexcessive regenerator section(B1) errors

Minor SD1, SL1, SDE,SLE, IF1A, IF1B,IF0A, IF0B, IFX,SL4

B2_EXC Excessive multiplex section (B2)errors

Major SD1, SL1, SDE,SLE, IF1A, IF1B,IFX, SL4

B2_SD Signal degradation due toexcessive multiplex section (B2)errors

Minor SD1, SL1, SDE,SLE, IF1A, IF1B,IFX, SL4

A Alarm ReferenceOptiX RTN 620 Radio Transmission System

Maintenance Guide

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

Issue 04 (2010-10-30)


Source

B3_EXC Excessive higher order path (B3)bit errors

Major SD1, SL1, SDE,SLE, IF1A, IF1B,IFX, SL4, PL3

B3_EXC_VC3 Excessive VC-3 path (B3) biterrors

Major EFT4, EMS6

B3_SD Signal degradation due toexcessive higher order path (B3)errors

Minor SD1, SL1, SDE,SLE, IF1A, IF1B,IFX, SL4, PL3

B3_SD_VC3 Signal degradation due toexcessive VC-3 path (B3) biterrors

Minor EFT4, EMS6

BD_NOT_INSTALLED

The logical board is not added onthe NMS.

Minor SCC

BD_STATUS Board not in position Major SD1, SL1, SDE,SLE, IF1A, IF1B,PO1, PH1, EFT4,EMS6, PXC, ODU,FAN, EOW, IF0A,IF0B, IFX, PD1,SL4, IFH2, EFP6

BIP_EXC Excessive BIP errors Minor PO1, PH1, EFT4,EMS6, IF0A, IF0B,IFX, PD1, IFH2,EFP6

BIP_SD Signal degradation due toexcessive BIP errors

Minor PO1, PH1, EFT4,EMS6, IF0A, IF0B,PD1, IFH2, EFP6

BOOTROM_BAD BOOTROM data check fails. Major SCC

C2_VCAIS C2 byte mismatch Minor PL3

CONFIG_NOSUPPORT

Configuration is not supported. Major ODU

DBMS_ERROR Errors in the processing of systemdatabases

Major SCC

DBMS_PROTECT_MODE

System databases in protectionmode

Critical SCC

DOWN_E1_AIS Alarm indication of 2 Mbit/sdownstream signals

Minor PO1, PH1, PD1,EFP6

E1_LOC Loss of 2M clock in upstreamsignals

Major PO1, PH1, PD1



A-3


Source

E1_LOS Loss of 2 Mbit/s line signals Minor PO1, PH1, PD1

ESN_INVALID Invalid ESN Major SCC

ETH_CFM_LOC Loss of connectivity Critical EMS6, EFP6

ETH_CFM_MISMERGE

Misconnection Critical EMS6, EFP6

ETH_CFM_RDI Failure in receiving CCMpackets at the remote end

Minor EMS6, EFP6

ETH_CFM_UNEXPERI

Errored frames Critical EMS6, EFP6

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

ETHOAM_DISCOVER_FAIL

Discovery failure detected bypoint-to-point Ethernet OAM

Minor EFT4, EMS6, EFP6

ETHOAM_RMT_CRIT_FAULT

Severe fault detected by point-to-point Ethernet OAM at theremote end

Minor EMS6, EFP6

ETHOAM_RMT_LOOP

Remote loopback detected bypoint-to-point Ethernet OAM

Minor EMS6, EFP6

ETHOAM_RMT_SD

Remote Ethernet performancedegradation detected by point-to-point Ethernet OAM

Minor EMS6, EFP6

ETHOAM_SELF_LOOP

MAC port loopback detected bypoint-to-point Ethernet OAM

Major EMS6, EFP6

ETHOAM_VCG_SELF_LOOP

VCTRUNK loopback detectedby point-to-point Ethernet OAM

Minor EMS6, EFP6

EX_ETHOAM_CC_LOS

Loss of periodical connectivitycheck packets

Critical EMS6, EFP6

EX_ETHOAM_MPID_CNFLCT

Conflict of MPIDs Major EMS6, EFP6

EXT_SYNC_LOS Loss of external clock sources Critical SCC

F1PORT_FAILED Failure of synchronous datainterfaces

Minor SCC

FAN_FAIL Failure of fan boards Major FAN

FCS_ERR FCS errors Critical EFT4, EMS6, EFP6


Maintenance Guide


Issue 04 (2010-10-30)


Source

FLOW_OVER Excessive data traffic received byEthernet ports

Minor EMS6

HARD_BAD Hardware errors Critical SD1, SL1, SDE,SLE, IF1A, IF1B,PO1, PH1, EFT4,PXC, SCC, ODU,EMS6, IF0A, IF0B,IFX, PD1, SL4,IFH2, EFP6

HP_CROSSTR Threshold-crossing performanceevent of the higher order path


HP_LOM Loss of multi-frames in thehigher order path


HP_RDI Higher order path remote defectindication


HP_REI Higher order path remote errorindication

Warning SD1, SL1, SDE,SLE, IF1A, IF1B,IFX, SL4

HP_SLM Higher order path signal labelmismatch


HP_TIM High order path trace identifiermismatch


HP_UNEQ Unequipped higher order path Minor SD1, SL1, SDE,SLE, IF1A, IF1B,IFX, SL4

HPAD_CROSSTR Adaptation performancethreshold-crossing of the higherorder path

Minor PO1, PH1, PD1

IF_CABLE_OPEN IF cables are disconnected. Major IF1A, IF1B, IF0A,IF0B, IFX, IFH2

IF_INPWR_ABN Abnormal power supplied by anIF board to an ODU

Major ODU

IF_MODE_UNSUPPORTED

Preset IF working mode notsupported

Major IF1A, IF1B



A-5


Source

IN_PWR_HIGH Over high input optical power Critical SD1, SL1, SL4

IN_PWR_LOW Over low input optical power Critical SD1, SL1, SL4

J0_MM Trace identifier mismatch Minor SD1, SL1, SDE,SLE, IF1A, IF1B,SL4

K1_K2_M K1 and K2 mismatch Minor SCC

K2_M K2 mismatch Minor SCC

LAG_PORT_FAIL A port of an LAG fails Minor EMS6, EFP6

LAG_VC_PORT_FAIL

A VCG port of an LAG fails Minor EMS6, EFP6

LASER_CLOSED A laser is closed. Major SD1, SL1, SL4

LASER_MOD_ERR_EX

The type of the pluggable opticalmodule on the board does notmatch the type of the opticalinterface.

Major SD1, SL1, SL4

LCAS_FOPR LCAS protocol fails in thereceive direction.

Major EFT4, EMS6, EFP6

LCAS_FOPT LCAS protocol fails in thetransmit direction


LCAS_PLCR Loss of partial bandwidth in theLCAS receive direction


LCAS_PLCT Loss of partial bandwidth in theLCAS transmit direction


LCAS_TLCR Loss of total bandwidth in theLCAS receive direction


LCAS_TLCT Loss of total bandwidth in theLCAS transmit direction


LCS_LIMITED The capacity of the configuredservices exceeds the rangepermitted by the license file

Major SCC, IFH2

LFA Out of frame alignment state ofE1 frames

Major EFP6

LICENSE_LOST The license file is not detected Major SCC, IFH2

LICENSE_ERR License file check fails Major SCC, IFH2

LINK_ERR Data link errors Critical EMS6


Maintenance Guide


Issue 04 (2010-10-30)


Source

LMFA Out of frame alignment state ofE1 multiframes

Major EFP6

LPS_UNI_BI_M The switching mode is single-ended at one end and dual-endedat the other end.

Minor SCC

LOOP_ALM A loopback occurs. Minor SD1, SL1, SDE,SLE, IF1A, IF1B,PO1, PH1, EFT4,EMS6, ODU, IF0A,IF0B, IFX, PD1,SL4, IFH2, EFP6

LPT_INEFFECT Link state pass-through functionfails.

Major EFT4, EMS6

LPT_RFI Link state pass-through functionfails at the remote end.

Critical EFP6, EFT4, EMS6

LP_CROSSTR Performance threshold-crossingof the lower order path

Minor PO1, PH1, PD1

LP_R_FIFO FIFO overflow at the receive sideof the lower order path

Minor PO1, PH1, PD1, PL3

LP_RDI Lower order path remote defectindication

Minor PO1, PH1, IF0A,IF0B, PD1, PL3,IFH2

LP_RDI_VC12 Remote defect indication in theVC-12 lower order path


LP_RDI_VC3 Remote defect indication in theVC-3 lower order path

Minor EFT4, EMS6

LP_REI Lower order path remote errorindication

Minor PO1, PH1, IF0A,IF0B, PD1, PL3,IFH2

LP_REI_VC12 Remote error indication in theVC-12 lower order path


LP_REI_VC3 Remote error indication in theVC-3 lower order path

Minor EFT4, EMS6

LP_RFI Lower order path remote failureindication

Minor PO1, PH1, PD1,IFH2

LP_SIZE_ERR Errors of TU specifications Minor PO1, PH1, PD1

LP_SLM Lower order path signal labelmismatch




A-7


Source

LP_SLM_VC12 Signal label mismatch in theVC-12 lower order path


LP_SLM_VC3 Signal label mismatch in theVC-3 lower order path

Minor EFT4, EMS6

LP_T_FIFO FIFO overflow at the transmitside of the lower order path


LP_TIM Lower order path trace identifiermismatch


LP_TIM_VC12 Lower order path trace identifiermismatch at VC-12 level


LP_TIM_VC3 Lower order path trace identifiermismatch at VC-3 level

Minor EFT4, EMS6

LP_UNEQ Unequipped lower order paths Minor PO1, PH1, IF0A,IF0B, PD1, PL3,IFH2

LP_UNEQ_VC12 Unequipped VC-12 lower orderpaths


LP_UNEQ_VC3 Unequipped VC-3 lower orderpaths

Minor EFT4, EMS6

LSR_NO_FITED Laser not installed Critical SD1, SL1, SL4

LSR_WILL_DIE The life of the laser is close to theend.

Critical SL4

LTI Loss of all clock sources Major SCC

MOD_TYPE_MIS-MATCH

Port module type mismatch Critical EMS6

MS_AIS Multiplex section alarmindication


MS_CROSSTR Multiplex section performancethreshold-crossing

Minor SD1, SL1, SDE,SLE, IF1A, IF1B,SL4

MS_RDI Multiplex section remote defectindication


MS_REI Multiplex section remote errorindication

Warning SD1, SL1, SDE,SLE, IF1A, IF1B,IFX, SL4


Maintenance Guide


Issue 04 (2010-10-30)


Source

MSAD_CROSSTR Multiplex section adaptationperformance threshold-crossing


MSSW_DIFFERENT

The active board and the standbyboard have inconsistent software.

Major SCC

MULTI_RPL_OWNER

The ring network has multipleRPL_OWNER nodes.

Minor EMS6

MW_BER_EXC Excessive errors on radio links Minor IFH2

MW_BER_SD Signal degradation due toexcessive errors on radio links

Minor IFH2

MW_FEC_UNCOR

FEC errors are uncorrectable. Minor IF1A, IF1B, IF0A,IF0B, IFX, IFH2

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

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

MW_RDI Remote defect indication onradio links

Minor IF1A, IF1B, IF0A,IF0B, IFX, IFH2

NESF_LOST Loss of NE software Critical SCC

NESTATE_INSTALL

The NE is in the installation state. Critical SCC

NO_BD_SOFT No board software exists Critical SD1, SL1, SDE,SLE, IF1A, IF1B,PXC, IF0A, IF0B,IFX, SL4, EMS6,IFH2, EFP6

NP1_MANUAL_STOP

The N+1 protection protocol isstopped manually.

Minor SCC

NP1_SW_FAIL The N+1 protection switchingfails

Major SCC

NP1_SW_INDI N+1 protection switchingindication

Major SCC

OPM_FAIL Output of optical power fails. Major SL4

PROT_CONN_ERR

The connections of the protectionpair are abnormal.

Major EMS6, EFP6

PORT_MODULE_OFFLINE

Port not in position Major EMS6



A-9


Source

POWER_ALM Power module alarm Major PXC, SCC, FAN,ODU

P_AIS PDH interface signal alarmindication

Major PL3

P_LOS Loss of signals at PDH interfaces Major PL3

PS Indication of the triggeredprotection switching

Major PO1, PH1, PD1

RADIO_FADING_MARGIN_INSUFF

Radio fading margin isinsufficient.

Minor ODU

RADIO_RSL_BE-YONDTH

Antennas are not aligned. Minor ODU

R_F_RST Reset of the receive FIFO Minor PO1, PH1, PD1

R_LOC Loss of clock on the receive lineside

Critical SD1, SL1, SDE,SLE, IF1A, IF1B,IF0A, IF0B, IFX,SL4, IFH2

R_LOF Loss of frame on the receive lineside

Critical SD1, SL1, SDE,SLE, IF1A, IF1B,IF0A, IF0B, IFX,SL4, IFH2

R_LOS Loss of signal on the receive lineside

Critical SD1, SL1, SDE,SLE, IF1A, IF1B,IFX, IF0A, IF0B,SL4

R_S_ERR Errors in the received signal Critical PO1, PH1, PD1

RADIO_MUTE The radio transmitter is muted. Warning ODU

RADIO_RSL_HIGH

Over high radio receive signallevel

Critical ODU

RADIO_RSL_LOW

Over low radio receive signallevel

Critical ODU

RADIO_TSL_HIGH

Over high radio transmit signallevel

Critical ODU

RADIO_TSL_LOW

Over low radio transmit signallevel

Critical ODU

RELAY_ALARM Relay alarm Critical EOW

RMFA Loss of multiframe alignment atthe remote end

Minor EFP6


Maintenance Guide


Issue 04 (2010-10-30)


Source

RP_LOC Loss of the received phase-locked clock

Major PO1, PH1, PD1

RPS_INDI Indication of the radio protectionswitching

Major SCC

RS_CROSSTR Regenerator section performancethreshold-crossing


RTC_FAIL The real time clock (RTC) of theequipment fails.

Major SCC

S1_SYN_CHANGE

Clock source switching in S1byte mode

Major SCC

SWDL_ACTIVATED_TIMEOUT

The activation timeout of thesoftware package

Critical SCC

SWDL_AUTOMATCH_INH

The automatic match function isdisabled

Minor SCC

SWDL_CHGMNG_NOMATCH

The board software version andthe running software version areinconsistent

Critical SCC

SWDL_COMMIT_FAIL

NE submission failure Minor SCC

SWDL_INPROCESS

The NE is in the process ofpackage loading.

Minor SCC

SWDL_NEPKGCHECK

Loss of files in a softwarepackage

Critical SCC

SWDL_PKG_NOBDSOFT

Files are deleted when they arecustomized.

Minor SCC

SWDL_ROLLBACK_FAIL

The version rollback on an NEfails.

Minor SCC

SYN_BAD Synchronous source degradation Minor PXC

SYNC_C_LOS The priority of the synchronousclock source is lost.

Warning SCC

T_ALOS Loss of analog signals at 2 Mbit/s interfaces

Major PO1, PH1, PD1

T_F_RST Reset of the transmit FIFO Minor PO1, PH1, PD1

T_LOC Loss of clock on the transmit lineside

Major SD1, SL1, SDE,SLE, SL4



A-11


Source

T_LOS Loss of signal on the transmit lineside

Major SD1, SL1, SDE,SLE, SL4

TEMP_ALARM The ambient temperature of theboard crosses the threshold.

Minor IF1A, IF1B, EFT4,PXC, SCC, EMS6,IF0A, IF0B, IFX,IFH2, EFP6, ODU

TU_AIS TU alarm indication Major PO1, PH1, IF0A,IF0B, PD1, PL3,IFH2

TU_AIS_VC12 TU alarm indication at VC-12level


TU_AIS_VC3 TU alarm indication at VC-3level

Major EFT4, EMS6

TU_LOP Loss of TU pointers Major PO1, PH1, IF0A,IF0B, PD1, PL3,IFH2

TU_LOP_VC12 Loss of TU pointers at VC-12level


TU_LOP_VC3 Loss of TU pointers at VC-3 level Major EFT4, EMS6

UP_E1_AIS Alarm indication of 2 Mbit/supstream signals

Minor PO1, PH1, PD1

VCAT_LOA Loss of virtual concatenationalignment

Critical EFT4, EMS6, EFP6

VCAT_LOM_VC12

Loss of multiframe of VC-12path virtual concatenation


VCAT_LOM_VC3 Loss of multiframe of VC-3 pathvirtual concatenation

Major EFT4, EMS6

VCAT_SQM_VC12

SQ mismatch of VC-12 pathvirtual concatenation


VCAT_SQM_VC3 SQ mismatch of VC-3 pathvirtual concatenation

Major EFT4, EMS6

VOLT_LOS Loss of voltage Major PXC, IF1A, IF1B,IF0A, IF0B, IFX,IFH2

WRG_BD_TYPE Errors of board types Major SCC

WRG_DEV_TYPE Errors of equipment types Critical SCC


Maintenance Guide


Issue 04 (2010-10-30)


Source

WS_LOS Loss of wayside signals at 2 Mbit/s electrical interfaces

Major PXC

W_R_FAILURE Read and write registers of theboard chip fail.

Major EMS6, EFP6

XCP_INDI The active/standby switching ofcross-connect and timing boardsoccurs.

Major SCC

XPIC_LOS Loss of XPIC compensationsignals

Critical IFX

NOTEAll alarmed boards refer to the logical boards displayed on the NMS.

A.2 Alarms and Handling ProceduresThis topic describes all the alarms on the OptiX RTN 620 in an alphabet order and how to handlethese alarms.

A.2.1 A_LOC

Description

The A_LOC is an alarm indicating that the clock signal is lost in the adding bus.

Attribute

Alarm Severity Alarm Type

Major Equipment alarm

Parameters

When you view an alarm on the network management system, select the alarm. In the 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

Parameter 1 The value is always 0x01.



A-13

Name Meaning

Parameter 2, Parameter 3 Indicate the ID of the path that reports the alarm. For example, 0x000x01 indicates that the alarm is reported in path 1.

Impact on the SystemWhen the A_LOC alarm occurs, the services carried by the alarmed board are interrupted.

Possible CausesThe board is faulty.

Procedure

Step 1 Replace the board that reports the alarm.

----End

Related InformationNone.

A.2.2 ALM_GFP_dCSF

DescriptionThe ALM_GFP_dCSF is an alarm indicating that the generic framing procedure (GFP) customersignal is lost. This alarm occurs when a board detects that a GFP customer signal managementframe, which indicates the loss of customer signals, is received from the remote station.

Attribute


Critical Communication 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,Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the followingtable.

Name Meaning


Parameter 2, Parameter 3 Indicate the ID of the VCTRUNK that reports the alarm. Forexample, 0x00 0x01 indicate that the alarm is reported byVCTRUNK 1.


Maintenance Guide


Issue 04 (2010-10-30)

Impact on the System

When the ALM_GFP_dCSF alarm occurs, the services are interrupted.

Possible Causes

The associated Ethernet port on the remote board is not well connected.

Procedure

Step 1 Handle the alarm reported by the remote board.

----End

Related Information

None.

A.2.3 ALM_GFP_dLFD

Description

The ALM_GFP_dLFD is an alarm indicating that the GFP frame is out of frame. This alarmoccurs when a board detects that the GFP frame is out of frame.

Attribute


Major Communication alarm

Parameters


Name Meaning


Parameter 2, Parameter 3 Indicate the ID of the VCTRUNK that reports the alarm. Forexample, 0x00 0x01 indicate that the alarm is reported byVCTRUNK 1.


The services are interrupted.



A-15

Possible Causesl Cause 1: The source and the sink VCTRUNKs are configured with different timeslots or

different numbers of paths.l Cause 2: Errors occur on certain links or certain links are faulty.

Procedure

Step 1 Cause 1: The source and the sink VCTRUNKs are configured with different timeslots or differentnumbers of paths.(1) Check whether the sink and source VCTRUNKs are bound with the same number of

physical paths or bound with the same timeslots.

If... Then...

The sink and source VCTRUNKs are notbound with the same number of physicalpaths or bound with the same timeslots

Correct the configuration data. For details,see Configuring the Internal Port of theEthernet Board.

The sink and source VCTRUNKs arebound with the same number of physicalpaths and bound with the same timeslots

Go to Cause 2.

Step 2 Cause 2: Errors occur on certain links or certain links are faulty.(1) Check whether the links that the service travels by have errors or become faulty.

If... Then...

The links are faulty Rectify the fault.

The links are normal Replace the alarmed board. .

----End


A.2.4 AM_DOWNSHIFT

DescriptionThe AM_DOWNSHIFT is an alarm indicating the downshift of AM modes. This alarm occurswhen the AM mode is downshifted from the highest-efficiency mode to the lower-efficiencymode. When the AM mode is upshifted from the lower-efficiency mode to the highest-efficiencymode, this alarm clears.

Attribute




Maintenance Guide


Issue 04 (2010-10-30)

Parameters

None.


When the AM_DOWNSHIFT alarm occurs, the transmission capacity is reduced.

Possible Causes

The possible cause of the AM_DOWNSHIFT alarm is the degradation of the working channels.l Cause 1: The external factors (for example, the climate) cause the degradation of the

working channels.l Cause 2: There are interferences around the working channels.l Cause 3: The ODU at the transmit end has abnormal transmit power.l Cause 4: The ODU at the receive end has abnormal receive power.

Procedure

Step 1 Cause 1: The external factors (for example, the climate) cause the degradation of the workingchannels.(1) When the external factors (for example, the climate) cause the degradation of the working

channels, the downshift of the AM mode is normal. Therefore, no measures should be 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 the fault at the transmit end, see TroubleshootingMicrowave Links.

Step 4 Cause 4: The ODU at the receive end has abnormal receive power.(1) Use the NMS to check whether the transmit power of the ODU at the transmit end is normal.

For details on troubleshooting the fault at the receive end, see Troubleshooting MicrowaveLinks.

----End

Related Information

None.

A.2.5 APS_FAIL

Description

The APS_FAIL is an alarm indicating that the MS protection switching fails.



A-17

Attribute



Parameters


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.


The services cannot be switched. If the current paths are unavailable, the services are interrupted.

Possible Causesl Cause 1: The parameters of the MS protection are set incorrectly.

l Cause 2: The parameter settings of the MS protection are lost.

Procedure

Step 1 Cause 1: The parameters of the MS protection are set incorrectly.

(1) Check whether the parameters of the MS protection are set correctly.

If... Then...

The connection is not correct Set the parameters correctly. For details, seeConfiguring Ring MSP or Configuring Linear MSP.

The connection is correct Go to Cause 2.

Step 2 Cause 2: The parameter settings of the MS protection are lost.

(1) Check whether the network-wide MSP protocol is normal.

(2) Restart the protocol. For details, see Starting/Stopping the Ring MSP Protocol or Starting/Stopping the Linear MSP Protocol.


Maintenance Guide


Issue 04 (2010-10-30)

If... Then...

The alarm clears after the protocol isrestarted

End the alarm handling.

The alarm persists after the protocol isrestarted

Contact Huawei technical supportengineers to handle the alarm.

----End


A.2.6 APS_INDI

DescriptionThe APS_INDI is an alarm indicating that the MS protection switching occurs.

Attribute




Name Meaning




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

Possible CausesWhen the APS_INDI alarm occurs, the MS protection switching occurs.



A-19

Procedure

Step 1 Query the switching status of MS protection groups according to Parameter 1 and Parameter 2.

If... Then...

Parameter 1 = 0x01 Query linear MSP groups.

Parameter 1 = 0x02 Query ring MSP groups.

Step 2 Check whether the MSP protocol is in the manual switching state, forced switching state, orlocked switching state. If yes, release the switching and check whether the alarm clears.

Step 3 Check whether the MSP protocol is in the automatic switching state. Do as follows:(1) Handle the R_LOS, R_LOF, MS_AIS, B2_EXC, or B2_SD alarm that the equipment

reports. After the alarm clears, wait until the MSP protocol is changed from the automaticswitching state to the normal state. Then, check whether the APS_INDI alarm clears.

(2) Check whether the service board configured with the MSP protocol is faulty. If yes, replacethe faulty board and then check whether the APS_INDI alarm clears.

(3) Check whether the cross-connect board is faulty. If yes, replace the PXC board, and thencheck whether the APS_INDI alarm clears.

----End


A.2.7 APS_MANUAL_STOP

DescriptionThe APS_MANUAL_STOP is an alarm indicating that the MSP protocol is stopped manually.

Attribute


Minor Processing alarm



Maintenance Guide


Issue 04 (2010-10-30)

Name Meaning




Impact on the SystemWhen the APS_MANUAL_STOP alarm occurs, the MSP protocol may fail and the protectionswitching may fail.

Possible CausesThe MSP protocol is stopped manually.

Procedure

Step 1 Determine the MSP protocol that needs to be enabled according to Parameter 1.

If... Then...

Parameter 1 = 0x01 Enable the linear MSP protocol.

Parameter 1 = 0x02 Enable the ring MSP protocol.

----End


A.2.8 AU_AIS

DescriptionThe AU_AIS is an alarm indication of the administrative unit (AU). This alarm occurs when theboard detects the AU pointer of all 1s for three consecutive frames.

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,



A-21

Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the followingtable.

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 Indicate the ID of the AU-4 path that reports the alarm. For example,0x00 0x01 indicate that the alarm is reported by AU-4 path 1 of theSDH signal.


When the AU_AIS alarm occurs, the service in the alarmed AU-4 path is interrupted. If theservice is configured with protection, the protection switching is also triggered.

Possible Causesl Cause 1: The opposite site inserts the AU_AIS alarm.

l Cause 2: The transmit unit at the opposite site is faulty.

l Cause 3: The receive unit at the local site is faulty.

Procedure

Step 1 Determine the AU-4 path that reports the alarm according to the alarm parameters.

Step 2 Cause 1: The opposite NE inserts the AU_AIS alarm.

If... Then...

The alarm that triggers the AU_AIS insertion occurs Clear the alarm immediately.

No such alarms that trigger the AU_AIS insertion occur Go to Cause 2.

Step 3 Cause 2: The transmit unit at the opposite site is faulty.

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

If... Then...

The alarm clears after the board isreplaced

The fault is rectified. End the alarmhandling.

The alarm persists after the board isreplaced

Go to the next step.

(2) Replace the PXC board of the opposite site.

Step 4 Cause 3: The receive unit at the local site is faulty.

(1) Replace the alarmed board.

----End


Maintenance Guide


Issue 04 (2010-10-30)

Related Information

None.

A.2.9 AU_LOP

Description

The AU_LOP is an alarm indicating the loss of AU pointers. This alarm occurs when a boarddetects the AU pointers of invalid values or with NDFs for eight consecutive frames.

Attribute



Parameters


Name Meaning




When the AU_LOP alarm occurs, the service in the alarmed AU-4 path is interrupted. If theservice is configured with protection, the protection switching is also triggered.

Possible Causesl Cause 1: The transmit unit at the opposite site is faulty.l Cause 2: The receive unit at the local site is faulty.

Procedure

Step 1 Determine the AU-4 path that reports the alarm according to the alarm parameters.

Step 2 Cause 1: The transmit unit at the opposite site is faulty.(1) Replace the line board or IF board of the opposite site.



A-23

If... Then...







(1) Replace the alarmed board.

----End

Related Information

None.

A.2.10 B1_EXC

Description

The B1_EXC is an alarm indicating that the regenerator section (B1) has excessive errors. Thisalarm occurs when the board detects that the B1 errors exceed the preset B1_EXC alarmthreshold (10-3 by default).

An IF boards that works in the PDH mode may also report this alarm. This alarm is detected bythe self-defined overhead byte B1 in PDH microwave frames.

Attribute


Minor Service alarm

Parameters


Name Meaning


Parameter 2, Parameter 3 Indicate the path ID. For example, 0x00 0x01 indicate that the alarmis reported in path 1.


Maintenance Guide


Issue 04 (2010-10-30)

Impact on the SystemThe 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).l Cause 2: The line performance degrades (if the alarm is reported by an SDH electrical

interface board).l Cause 3: The line performance degrades (if the alarm is reported by an IF board).l Cause 4: The network clock quality degrades.l Cause 5: The board is faulty (if the alarm is reported by an SDH optical interface board or

SDH electrical interface board).l Cause 6: The board is faulty (if the alarm is reported by an IF board).

ProcedureStep 1 Cause 1: The line performance degrades (if the alarm is reported by an SDH optical interface

board).(1) Check whether the transmit power at the opposite end and the receive power at the local

end meet the specifications of the optical interfaces. For details, see Browsing CurrentPerformance Events.

If... Then...

The transmit power of the opposite site isextremely low

Replace the SDH optical interface boardof the opposite site.

The transmit power of the opposite site isnormal, but the receive power of the localsite is close to the value (for example,within ±3 dB) of receiver sensitivity

The fiber is faulty. Proceed 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 thefibers


The errors do not vary with the changeof the fibers

Solve the problem according to the solutionfor the problem that occurs when a board isfaulty.

(3) If the fibers are faulty, check whether the fiber jumper from the equipment to the opticaldistribution frame (ODF) and the fiber that is led out from the equipment room are pressed,and whether any fiber connector is dirty or damaged. If yes, replace the fiber jumper orclean the fiber connector.

Step 2 Cause 2: The line performance degrades (if the alarm is reported by an SDH electrical interfaceboard).(1) Exchange the electrical cables that are possibly faulty in the receive and transmit directions

to locate the fault.



A-25

If... Then...

The bit errors vary with the change ofthe cables


The bit errors do not vary with thechange of the cables

The boards of the stations at the two ends arefaulty. Solve the problem according to thesolution for the problem that occurs when aboard is faulty.

(2) Check whether the cable grounding, cable connectors, and cables are damaged or deformed.If yes, replace the faulty cables.

Step 3 Cause 3: The line performance degrades (if the alarm is reported by an IF board).

(1) Check whether the MW_FEC_UNCOR alarm is generated. If yes, clear the alarm.

Step 4 Cause 4: The network clock quality degrades.

(1) Check the clock status of the alarmed NE. For details, see Querying the ClockSynchronization Status.

If... Then...

The clock source of the local NE isdifferent from the clock source of theopposite NE

In this case, the clock may becomeasynchronous and B1 errors may occur.Reconfigure the clock source, and ensure thatthe clock is synchronized on the local NE andopposite NE.

The clock of the local NE and the clockof the opposite NE form a timing loop

This may cause errors and even serviceinterruptions. In this case, reconfigure theclock source and release the timing loop.

Step 5 Cause 5: The board is faulty (if the alarm is reported by an SDH optical interface board or SDHelectrical interface board).

(1) The SDH optical/electrical line board of the local NE is faulty. Loop back the opticalinterfaces or electrical interfaces of the NE by using a fiber jumper or an electrical cableto locate the fault.

If... Then...

The fault is not rectified after the opticalinterfaces or electrical interfaces arelooped back

Replace the SDH line board of the localsite.

The fault is rectified after the opticalinterfaces or electrical interfaces arelooped back

Replace the SDH line board of theopposite site.

Step 6 Cause 6: The board is faulty (if the alarm is reported by an IF board).

(1) Perform an inloop for the multiplexing interface of the IF board on the local site.

If... Then...

The fault is not rectified after the opticalinterfaces are looped back

Replace the alarmed IF board of thelocal site.


Maintenance Guide


Issue 04 (2010-10-30)

If... Then...

The fault is rectified after the multiplexinginterface is looped back

Replace the IF board of the oppositesite.

----End

Related Information

Handle the errors of TDM services.

A.2.11 B1_SD

Description

The B1_SD is an alarm indicating that the regenerator section (B1) signal degrades. This alarmoccurs when the board detects that the B1 errors exceed the preset B1_SD alarm threshold(10-6 by default) but do not reach the preset B1_EXC alarm threshold (10-3 by default).

An IF board that works in PDH mode may also report this alarm. This alarm is detected by theself-defined overhead byte B1 in PDH microwave frames.

Attribute


Minor Service alarm

Parameters


Name Meaning

Parameter 1 Indicates the ID of the port that reports the alarm. For example,0x01 indicates that the alarm is reported by port 1 of the relatedboard.

Parameter 2, Parameter 3 Indicate the path ID. For example, 0x00 0x01 indicate that the alarmis reported in path 1.


The service performance on the port degrades.

If the alarm is reported by an IF board and the equipment is configured with 1+1 FD/SDprotection, the HSM switching is triggered.



A-27


board).

l Cause 2: The line performance degrades (if the alarm is reported by an SDH electricalinterface board).

l Cause 3: The line performance degrades (if the alarm is reported by an IF board).

l Cause 4: The network clock quality degrades.

l Cause 5: The board is faulty (if the alarm is reported by an SDH optical interface board orSDH electrical interface board).

l Cause 6: The board is faulty (if the alarm is reported by an IF board).

Procedure

Step 1 Cause 1: The line performance degrades (if the alarm is reported by an SDH optical 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 Browsing CurrentPerformance Events.

If... Then...






If... Then...


The fibers are faulty. Proceed to the next step.




Step 2 Cause 2: The line performance degrades (if the alarm is reported by an SDH electrical interfaceboard).

(1) Exchange the cables that are possibly faulty in the receive and transmit directions to locatethe fault.

If... Then...


Maintenance Guide


Issue 04 (2010-10-30)

The bit errors vary with the change of thecables


The bit errors do not vary with the changeof the cables

The boards of the stations at the two endsare faulty. Solve the problem according tothe solution for the problem that occurswhen a board is faulty.

(2) Check whether the cable grounding, cable connectors, and cables are damaged or deformed.If yes, replace the cables that are faulty.



Step 4 Cause 4: The network clock quality degrades.

(1) Check the clock status of the alarmed NE. For details, see Querying the ClockSynchronization Status.

If... Then...







If... Then...






(1) Perform an inloop for the multiplexing interface of the IF board on the local site.

If... Then...

The fault is not rectified after themultiplexing interface is looped back




A-29

If... Then...



----End

Related InformationHandle the errors of TDM services.

A.2.12 B2_EXC

DescriptionThe B2_EXC is an alarm indicating that B2 errors (in multiplex section) exceed the threshold.This alarm occurs when the board detects that the number of B2 errors exceeds the presetB2_EXC alarm threshold (10-3 by default).

Attribute


Major Service alarm


Name Meaning


Parameter 2, Parameter 3 Indicate the path ID.

Impact on the SystemThe services on the port are interrupted.



interface board).


Maintenance Guide


Issue 04 (2010-10-30)

l Cause 3: The line performance degrades (if the alarm is reported by an IF board).l Cause 4: The network clock quality degrades.l Cause 5: The board is faulty (if the alarm is reported by an SDH optical interface board or


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


If... Then...






If... Then...






Step 2 Cause 2: The line performance degrades (if the alarm is reported by an SDH electrical interfaceboard).(1) Exchange the cables that are possibly faulty in the receive and transmit directions to locate

the fault.

If... Then...







A-31

(2) Check whether the cable grounding, cable connectors, and cables are damaged or deformed.

If yes, replace the faulty cables.

Step 3 Cause 3: The line performance degrades (if the alarm is reported by an IF board).(1) Check whether the MW_FEC_UNCOR alarm is generated. If yes, clear the alarm.

Step 4 Cause 4: The network clock quality degrades.(1) Check the clock status of the alarmed NE. For details, see Querying the Clock

Synchronization Status.

If... Then...





Step 5 Cause 5: The board is faulty (if the alarm is reported by an SDH optical interface board or SDHelectrical interface board).(1) The SDH optical/electrical line board of the local NE is faulty. Loop back the optical

interfaces or electrical interfaces of the NE by using a fiber jumper or an electrical cableto locate the fault.

If... Then...

The fault is not rectified after the opticalinterfaces or electrical interface arelooped back




Step 6 Cause 6: The board is faulty (if the alarm is reported by an IF board).(1) Perform an inloop for the multiplexing interface of the IF board on the local NE.

If... Then...





----End



Maintenance Guide


Issue 04 (2010-10-30)

A.2.13 B2_SD

Description

The B2_SD is an alarm indicating that the signal degrades due to 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

Parameters


Name Meaning




The service performance on the port degrades.



board).

l Cause 2: The line performance degrades (if the alarm is reported by an SDH electricalinterface board).

l Cause 3: The line performance degrades (if the alarm is reported by an IF board).

l Cause 4: The network clock quality degrades.

l Cause 5: The board is faulty (if the alarm is reported by an SDH optical interface board orSDH electrical interface board).

l Cause 6: The board is faulty (if the alarm is reported by an IF board).



A-33

Procedure



If... Then...






If... Then...








If... Then...









Maintenance Guide


Issue 04 (2010-10-30)



If... Then...







If... Then...





Step 6 Cause 6: The board is faulty (if the alarm is reported by an IF board).(1) Perform an inloop for the multiplexing interface of the IF board on the local site.

If... Then...





----End


A.2.14 B3_EXC



A-35

Description

The B3_EXC is an alarm indicating that B3 errors (in the higher order path) exceed the threshold.This alarm occurs when the board detects that the number of B3 errors exceeds the presetB3_EXC alarm threshold (10-3 by default).

Attribute


Major Service alarm

Parameters


Name Meaning


Parameter 2, Parameter 3 Indicate the ID of the AU-4 path that reports the alarm. For example,0x00 0x01 indicates that the alarm is reported by AU-4 path 1 ofthe related board.


When the B3_EXC alarm occurs, the service on the path that reports the alarm is interrupted.





Procedure



Maintenance Guide


Issue 04 (2010-10-30)


If... Then...


Replace the board that contains the SDHoptical interface unit on the oppositesite.




If... Then...






Step 2 Cause 2: The line performance degrades (if the alarm is reported by an SDH electrical interfaceboard).(1) Exchange the cables that are possibly faulty in the receive and transmit directions to locate

the fault.

If... Then...





(2) Check whether the cable grounding, cable connectors, and cables are damaged or deformed.

If yes, replace the faulty cables.

Step 3 Cause 3: The line performance degrades (if the alarm is reported by an IF board).(1) Check whether the MW_FEC_UNCOR or RPS_INDI alarm is reported. If yes, clear the

alarm.





A-37

If... Then...







If... Then...






(1) Perform an inloop for the multiplexing interface of the IF board on the local NE.

If... Then...





----End

Related Information

Handle the errors of TDM services.

A.2.15 B3_EXC_VC3

Description

The B3_EXC_VC3 is an alarm indicating that the B3 errors (in VC-3 paths) exceed the threshold.This alarm occurs when a board detects that the number of B3 errors exceeds the presetB3_EXC_VC3 alarm threshold (10-3 by default).


Maintenance Guide


Issue 04 (2010-10-30)

Attribute


Major Service alarm

Parameters


Name Meaning


Parameter 2, Parameter 3 Indicate the ID of the VC-3 path that reports the alarm. For example,0x00 0x01 indicate that the alarm is reported by VC-3 path 1.


The services carried by the alarmed path have a large number of errors.

Possible Causesl Cause 1: Higher-level bit error alarms occur in the system.l Cause 2: The line performance degrades (if the alarm is reported by an Ethernet optical

interface).l Cause 3: The line performance degrades (if the alarm is reported by an Ethernet electrical

interface).l Cause 4: The board is faulty.

Procedure

Step 1 Cause 1: Higher-level bit error alarms occur in the system.(1) Check whether the local site or the upstream station detects the B1_EXC, B1_SD,

B2_EXC, B2_SD, B3_EXC, or B3_SD alarm. If yes, clear the higher-level alarm.(2) Then, check whether the B3_EXC_VC3 alarm clears.

If... Then...

Yes End the alarm handling.

No Go to Cause 2 or Cause 3.

Step 2 Cause 2: The line performance degrades (if the alarm is reported by an Ethernet optical interface).(1) Check whether the transmit power at the opposite end and the receive power at the local




A-39

If... Then...


Replace the Ethernet board of theopposite site.

The transmit power of the opposite site isnormal, but the receive power of the localsite is close to the value (for example,within ±3 dB) of receiver sensitivity.

The fibers are faulty. Proceed to the nextstep.


If... Then...

The errors vary with the change of the fibers Go to the next step.

The errors do not vary with the change of the fibers Ensure that the board is normal.

(3) If the fibers are faulty, check whether the fiber jumper from the equipment to the opticaldistribution frame (ODF) and the fiber that is led out from the equipment room are pressed,and whether any fiber connector is dirty or damaged. If yes, replace the fiber jumper orfiber connector. Then, check whether the alarm clears.

If... Then...


No Ensure that the board is normal.

Step 3 Cause 3: The line performance degrades (if the alarm is reported by an Ethernet electricalinterface).(1) Check whether the cable grounding, cable connectors, and cables are damaged or deformed.

If yes, replace the faulty cables.(2) Then, check whether the alarm clears.

If... Then...



Step 4 Cause 4: The board is faulty.(1) Perform an inloop on the Ethernet port that is connected to the alarmed VC-3 path.

If... Then...

The fault is not rectified after theEthernet port is looped back

Replace the alarmed Ethernet processingboard of the local site.

The fault is rectified after the Ethernetport is looped back

Replace the Ethernet processing board ofthe opposite site.

----End



Maintenance Guide


Issue 04 (2010-10-30)

A.2.16 B3_SD

DescriptionThe B3_SD is an alarm indicating that the signal degrades due to excessive B3 errors (in thehigher order path). This alarm occurs when a board detects that the number of B3 errors exceedsthe preset B3_SD alarm threshold (10-6 by default).

Attribute


Minor Service alarm


Name Meaning


Parameter 2, Parameter 3 Indicate the ID of the AU-4 path that reports the alarm. For example,0x00 0x01 indicate that the alarm is reported by AU-4 path 1 of therelated board.

Impact on the SystemThe service performance on the alarmed port degrades.








A-41

Procedure



If... Then...






If... Then...








If... Then...









Maintenance Guide


Issue 04 (2010-10-30)



If... Then...







If... Then...





Step 6 Cause 6: The board is faulty (if the alarm is reported by an IF board).(1) Perform an inloop for the multiplexing interface of the IF board on the local NE.

If... Then...





----End


A.2.17 B3_SD_VC3



A-43

DescriptionThe B3_SD_VC3 is an alarm indicating that the signal degrades due to excessive B3 errors (inVC-3 paths). This alarm occurs when the board detects that the number of B3 errors exceeds thepreset B3_SD_VC3 alarm threshold (10-6 by default).

Attribute


Minor Service alarm


Name Meaning


Parameter 2, Parameter 3 Indicate the ID of the path that reports the alarm. For example, 0x000x01 indicate that the alarm is reported by VC-3 path 1.

Impact on the SystemWhen the B3_SD_VC3 alarm occurs, the service on the path that reports the alarm degrades.

Possible Causesl Cause 1: Higher-level bit error alarms occur in the system.l Cause 2: The line performance degrades (if the alarm is reported by an Ethernet optical

interface).l Cause 3: The line performance degrades (if the alarm is reported by an Ethernet electrical

interface).l Cause 4: The board is faulty.

Procedure

Step 1 Cause 1: Higher-level bit error alarms occur in the system.(1) Check whether the local site or the upstream station detects the B1_EXC, B1_SD,

B2_EXC, B2_SD, B3_EXC, or B3_SD alarm. If yes, clear the higher-level alarm.(2) Then, check whether the alarm clears.

If... Then...


No Go to Cause 2 or Cause 3.


Maintenance Guide


Issue 04 (2010-10-30)

Step 2 Cause 2: The line performance degrades (if the alarm is reported by an Ethernet optical interface).(1) Check whether the transmit power at the opposite end and the receive power at the local


If... Then...


Replace the Ethernet board of theopposite site.




If... Then...

The errors vary with the change of the fibers Go to the next step.

The errors do not vary with the change of the fibers Ensure that the board is normal.

(3) If the fibers are faulty, check whether the fiber jumper from the equipment to the opticaldistribution frame (ODF) and the fiber that is led out from the equipment room are pressed,and whether any fiber connector is dirty or damaged. If yes, replace the fiber jumper orclean the fiber connector. Then, check whether the alarm clears.

If... Then...



Step 3 Cause 3: The line performance degrades (if the alarm is reported by an Ethernet electricalinterface).(1) Check whether the cable grounding, cable connectors, and cables are damaged or deformed.

If yes, replace the faulty cables.(2) Then, check whether the alarm clears.

If... Then...



Step 4 Cause 4: The board is faulty.(1) Perform an inloop on the Ethernet port that is connected to the alarmed VC-3 path.

If... Then...

The fault is not rectified after theEthernet port is looped back

Replace the alarmed Ethernet processingboard of the local site.

The fault is rectified after the Ethernetport is looped back

Replace the Ethernet processing board ofthe opposite site.

----End



A-45


A.2.18 BD_NOT_INSTALLED

DescriptionThe BD_NOT_INSTALLED is an alarm indicating that a physical board is installed in a certainslot, but the logical board is not added.

Attribute


Minor Equipment alarm


Name Meaning

Parameter 0, Parameter 1 Indicate the ID of the slot.

Impact on the SystemWhen 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.

ProcedureStep 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



Maintenance Guide


Issue 04 (2010-10-30)

A.2.19 BD_STATUS

DescriptionThe BD_STATUS is an alarm indicating that the board is not in position.

Attribute



ParametersNone.

Impact on the SystemThe board that reports the alarm fails to work.

Possible CausesIf the alarm is reported by a board of the IDU, the possible causes are as follows:l Cause 1 of the alarm reported by a board of the IDU: The board is installed in an incorrect

slot.l Cause 2 of the alarm reported by a board of the IDU: The board and the backplane are not

connected properly.l Cause 3 of the alarm reported by a board of the IDU: The slot is faulty.l Cause 4 of the alarm reported by a board of the IDU: The board is faulty.

If the alarm is reported by the ODU, the possible causes are as follows:

l Cause 1 of the alarm reported by the ODU: Other alarms are generated.l Cause 2 of the alarm reported by the ODU: The ODU is faulty.

Procedure

Step 1 Cause 1 of the alarm reported by a board of the IDU: The board is installed in an incorrect slot.(1) Check whether the logical slot and the physical slot of the alarmed board are consistent.

For details, see Checking Board Status.

If... Then...

The board that reports the alarm is installedin an incorrect slot

Install the board in a correct slot.

The board that reports the alarm is installedin a correct slot

Clear the alarm according to the solutionfor the alarm that is generated when theboard and the backplane are not connectedproperly.



A-47

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 alarmed board. For details, see 6.1 Removing a Board and 6.2

Inserting a Board.

If... Then...

The alarm disappears after the board isremoved and inserted



Clear the alarm according to the solutionfor the alarm that is generated when theboard or the slot is faulty.

Step 3 Cause 3 of the alarm reported by a board of the IDU: The slot is faulty.(1) Contact Huawei engineers to handle the faulty slot.

TIPGenerally, the slot becomes faulty due to broken pins or bent pins. Remove the board, and use a torchto check whether there is any broken pin or bent pin.

(2) If an idle slot is available, insert the board in the idle slot and add the board again. Then,the board can work normally.

Step 4 Cause 4 of the alarm reported by a board of the IDU: The board is faulty.(1) Replace the alarmed board. For details, see 6 Part Replacement.

If... Then...

The alarm clears after the board is replaced The fault is rectified. End the alarmhandling.


Clear the alarm according to the solutionfor the alarm that is generated when the slotis faulty.

Step 5 Cause 1 of the alarm reported by the ODU: Other alarms are generated.(1) Query the IF board to see whether the HARD_BAD, BD_STATUS,

IF_CABLE_OPEN or VOLT_LOS alarm is generated.

If... Then...

Yes Clear these alarms first.

No Clear the alarm according to the solutionfor the alarm that is generated when theODU is faulty.

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

----End


Maintenance Guide


Issue 04 (2010-10-30)


A.2.20 BIP_EXC

DescriptionThe BIP_EXC is an alarm indicating that BIP errors exceed the preset threshold. This alarmoccurs when a board detects that the number of BIP-2 errors (in byte V5) exceeds the presetBIP_EXC alarm threshold (10-3 by default).

Attribute


Minor Service alarm


Name Meaning


Parameter 2, Parameter 3 Indicate the ID of the path that reports the alarm. For example, 0x000x01 indicate that the alarm is reported in path 1.

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

or Ethernet processing board).l Cause 2: The line performance degrades (if the alarm is reported by an IF board).l Cause 3: The board is faulty (if the alarm is reported by an E1 service board or Ethernet

processing board).l Cause 4: 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 E1 service board orEthernet service processing board).



A-49

(1) Check whether any performance degradation alarm occurs on the STM-1 path or radio linkalong which the E1 service or Ethernet service travels. If yes, clear the alarm immediately.

The following are the performance degradation alarms that commonly occur on an opticalline or radio link:

B1_EXC, B1_SD, B2_EXC, B2_SD, B3_EXC, B3_SD, MW_FEC_UNCOR,RPS_INDI, MW_BER_EXC, and MW_BER_SD.

If... Then...

Yes Handle the relevant alarms first.



(1) Check whether any performance degradation alarm occurs on the tributary board or IFboard that transmits service signals. If yes, clear the alarm immediately.

The following are the performance degradation alarms that commonly occur on thetributary board or IF board:

BIP_EXC, BIP_SD, MW_FEC_UNCOR, RPS_INDI, MW_BER_EXC, andMW_BER_SD.

Step 3 Cause 3: The board is faulty (if the alarm is reported by an E1 service board or Ethernet serviceprocessing board).

(1) Replace the E1 service board or replace the Ethernet service processing board. Then,check whether the alarm clears.

If... Then...


No Replace the PXC board.


(1) Replace the IF board. Then, check whether the alarm clears.

If... Then...



----End

Related Information

5.4 Troubleshooting Bit Errors in TDM Services.

A.2.21 BIP_SD


Maintenance Guide


Issue 04 (2010-10-30)

DescriptionThe BIP_SD is an alarm indicating that the signal degrades due to excessive BIP errors. Thisalarm occurs when the board detects that the number of BIP-2 errors (in byte V5) exceeds thepreset BIP_SD alarm threshold (10-6 by default).

Attribute


Minor Service alarm


Name Meaning



Impact on the SystemWhen the BIP_SD alarm occurs, the service on the alarmed path degrades.

Possible Causesl Cause 1: The line performance degrades (if the alarm is reported by an E1 service board

or Ethernet service processing board).l Cause 2: The line performance degrades (if the alarm is reported by an IF board).l Cause 3: The board is faulty (if the alarm is reported by an E1 service board or Ethernet

service processing board).l Cause 4: 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 E1 service board orEthernet processing board).(1) Check whether any performance degradation alarm occurs on the STM-1 path or radio link

along which the E1 service or Ethernet service travels. If yes, clear the alarm immediately.

The following are the performance degradation alarms that commonly occur on an opticalline or radio link:

B1_EXC, B1_SD, B2_EXC, B2_SD, B3_EXC, B3_SD, MW_FEC_UNCOR,RPS_INDI, MW_BER_EXC, and MW_BER_SD.



A-51

If... Then...

Yes Handle the relevant alarms first.


Step 2 Cause 2: The line performance degrades (if the alarm is reported by an IF board).(1) Check whether any performance degradation alarm occurs on the tributary board or IF

board that transmits service signals. If yes, clear the alarm immediately.

The following are the performance degradation alarms that commonly occur on thetributary board or IF board:

BIP_EXC, BIP_SD, MW_FEC_UNCOR, RPS_INDI, MW_BER_EXC, andMW_BER_SD.

Step 3 Cause 3: The board is faulty (if the alarm is reported by an E1 service board or Ethernet serviceprocessing board).(1) Replace the E1 service board or replace the Ethernet service processing board. Then,

check whether the alarm clears.

If... Then...



Step 4 Cause 4: The board is faulty (if the alarm is reported by an IF board).(1) Replace the IF board. Then, check whether the alarm clears.

If... Then...



----End


A.2.22 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




Maintenance Guide


Issue 04 (2010-10-30)

Parameters


Name Meaning

Parameter 1 Indicates the type of the BOOTROM damage.l 0x01: damage of basic BIOSl 0x02: damage of extended BIOS

Parameter 2, Parameter 3 The values are always 0xff 0xff.


When the BOOTROM_BAD alarm occurs, it indicates that errors occur in the system 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 has no impacts on 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.

l Cause 3: The BOOTROM database is damaged.

Procedure

Step 1 Replace the SCC board.

----End

Related Information

None.

A.2.23 C2_VCAIS

Description

The C2_VCAIS is an indication of the path signal label byte (C2) alarm. This alarm occurs whena board detects that the C2 byte is 0xff.



A-53

Attribute


Minor Communication alarm

Parameters


Name Meaning




None.

Possible Causes

Cause 1: The transmitted C2 byte at the remote end is incorrectly set.

Procedure

Step 1 Cause 1: The transmitted C2 byte at the remote end is incorrectly set.

(1) Determine the ID of the VC path that reports the alarm according to the alarm parameter.

(2) Rectify the setting of C2 to be Sent on the remote station.

----End

Related Information

None.

A.2.24 CONFIG_NOSUPPORT

Description

The CONFIG_NOSUPPORT is an alarm indicating that the configuration is not supported. Thisalarm is reported if an ODU detects that the specified parameters do not meet the requirementsof the ODU.


Maintenance Guide


Issue 04 (2010-10-30)

Attribute


Major Processing alarm

Parameters


Name Meaning

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


The ODU fails to work normally. If the equipment is configured with 1+1 FD protection, theactive ODU generates the CONFIG_NOSUPPORT alarm. In this case, IF 1+1 protectionswitching may be triggered.

Possible Causes

Cause 1: The type and configuration parameters of the ODU do not match the requirements.

Procedure

Step 1 Cause 1: The type and configuration parameters of the ODU do not match the requirements.

(1) Determine the parameter that does not meet the requirement according to the alarmparameter. Then, handle the fault accordingly.

If... Then...

The alarm parameter takes a value from 0x01 to 0x03 Run Step 1.2.

The alarm parameter takes a value from 0x04 to 0x06 Run Step 1.3.

(2) Check whether the parameters of the ODU interface meet the requirements of networkplanning. For details, see Setting Parameters of ODU Interfaces.



A-55

If... Then...

Yes Replace the ODU with a correct one.

No Modify the parameters of the ODU interface.

(3) Check whether the parameters of the IF interface meet the requirements of networkplanning. For details, see Configuring the IF/ODU Information of a Radio Link.

If... Then...

Yes Replace the IF board.

No Configure the IF/ODU information of radio links.

----End


A.2.25 DBMS_ERROR

DescriptionThe DBMS_ERROR is an alarm indicating that errors occur in the processing of the systemdatabase.

Attribute





Maintenance Guide


Issue 04 (2010-10-30)

Name Meaning

Parameter 1 Indicates the types of the database errors.l 0x01: The input parameters are invalid.l 0x02: The database files do not exist.l 0x03: The database memory area numbers are incorrect.l 0x04: The database overwriting occurs.l 0x05: Errors occur in the header information check in the database backup

area.l 0x06: Errors occur in the FAT table structure check in the database storage

area.l 0x07: Errors occur in the database check in the database backup area.l 0x08: Restoring the database fails.l 0x09: The database ID is invalid.l 0x0A: The databases are different.l 0x0B: The data is unchecked.l 0x0E: The semaphore handle is invalid.l 0x0F: Errors occur in applying for memory.l 0x10: Errors occur in releasing memory.l 0x12: Transmitting the message capsule fails.l 0x13: The starting and ending records of the database are incorrect.l 0x14: The database is null.l 0x15: The flag is incorrectly set.l 0x16: The input command parameters are incorrect.l 0x17: Non-backup database.l 0x18: The database is in protection mode.l 0x19: The configuration is not verified.

Parameter 2 Indicates the errored data storage area.l 0x00: database in fdb0l 0x01: database in fdb1l 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

Impact on the SystemWhen 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.



A-57

Possible Causesl Cause 1: The database processing fails or the database is damaged.l Cause 2: The SCC board is faulty.

Procedure

Step 1 Cause 1: The database operation fails.(1) Reset the SCC board. For details, see Resetting the SCC board.

If... Then...

The alarm clears after the board is reset End the fault handling.

The alarm persists after the board is reset Go to Cause 2.

Step 2 Cause 2: The SCC board is faulty.(1) Replace the alarmed SCC board.

----End


A.2.26 DBMS_PROTECT_MODE

DescriptionThe DBMS_PROTECT_MODE is an alarm indicating that the system database is in protectionmode.

Attribute


Critical Processing alarm

ParametersNone.

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.


Maintenance Guide


Issue 04 (2010-10-30)

Procedure

Step 1 Cause 1: The data enters the protection mode due to frequent resets of the NE software.(1) Replace the SCC board.

----End


A.2.27 DOWN_E1_AIS

DescriptionThe DOWN_E1_AIS is an alarm of the 2 Mbit/s downlink signal. This alarm occurs when thetributary board or EoPDH borad detects the 2 Mbit/s downlink signal of all 1s.

Attribute




Name Meaning


Parameter 2, Parameter 3 Indicate the ID of the path that reports the alarm. For example, 0x000x01 indicates that the alarm is reported in path 1.

Impact on the SystemThe E1 signal is unavailable.

Possible Causesl Cause 1: The opposite site transmits the E1_AIS alarm.l Cause 2: The board on the local site is faulty.

Procedure

Step 1 Cause 1: The opposite site transmits the E1_AIS alarm.



A-59

(1) Check whether the opposite site reports the UP_E1_AIS or T_ALOS alarm.

If... Then...

The opposite site reports the UP_E1_AISor T_ALOS alarm

Clear the alarm immediately.

The opposite site does not report theUP_E1_AIS or T_ALOS alarm


Step 2 Cause 2: The board on the local site is faulty.(1) Replace the alarmed board.

If... Then...




Replace the PXC board of the local site.

----End


A.2.28 E1_LOC

DescriptionThe E1_LOC is an alarm indicating that the upstream 2M clock is lost. This alarm occurs whena tributary board fails to extract the clock from E1 signals.

Attribute




Name Meaning

Parameter 1 Indicates the ID of the tributary port (path) that reports the alarm. For example,0x01 indicates that the alarm is reported by port (path) 1 of the tributary board.


Maintenance Guide


Issue 04 (2010-10-30)


When E1_LOC occurs, the service is not affected.

Possible Causesl Cause 1: The opposite NE is faulty.

l Cause 2: The line sequence of the cable is incorrect.

l Cause 3: The receive unit of the tributary board on the local NE is faulty.

l Cause 4: The input E1 signal has an abnormal waveform.

Procedure

Step 1 Cause 1: The opposite NE is faulty.

(1) Rectify the fault on the opposite NE.

Step 2 Cause 2: The line sequence of the cable is incorrect.

(1) Redo the cable.

Step 3 Cause 3: The receive unit of the tributary board on the local NE is faulty.

(1) Replace the tributary board of the local site.

Step 4 Cause 4: The input E1 signal has an abnormal waveform.

(1) Check whether any external interference causes the abnormal waveform of the E1 signal.

If... Then...

There is external interference The fault is rectified. End the alarm handling.

There is no external interference Contact Huawei engineers.

----End

Related Information

None.

A.2.29 E1_LOS

Description

The E1_LOS is an alarm indicating the loss of E1 signals. This alarm occurs when a tributaryboard detects upstream E1 signals of all 0s.

Attribute





A-61

Parameters


Name Meaning




When E1_LOS alarm occurs, E1 services are 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 site is faulty.

Procedure

Step 1 Cause 1: The cable is not connected or the cable is faulty.

(1) Check whether the cable is connected properly.

If... Then...

The cable is not connected properly Connect the cable properly.

The cable is prepared incorrectly Redo the cable.

Step 2 Cause 2: The opposite NE is faulty.

(1) Rectify the fault on the opposite NE.

Step 3 Cause 3: The tributary board on the local site is faulty.

(1) Replace the tributary board of the local site.

----End

Related Information

None.

A.2.30 ESN_INVALID


Maintenance Guide


Issue 04 (2010-10-30)

DescriptionThe ESN_INVALID is an alarm indicating that the electronic serial number (ESN) of theequipment is invalid.

Attribute




Name Meaning

Parameter 1 Indicates the slot number of the alarmed SCC board.

Impact on the SystemNone.

Possible CausesCause 1: Verification of the ESN that is read from the SCC board is normal, but the ESN cannotbe identified.

Procedure

Step 1 Cause 1: Verification of the ESN that is read from the SCC board is normal, but the ESN cannotbe identified.(1) Contact Huawei technical support engineers for upgrading the software.

----End


A.2.31 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 ID mismatches or whose priority is lower.



A-63

Attribute




Name Meaning

Parameter 1, Parameter 2, Parameter 3,Parameter 4 (Port)

Indicate the ID of the port that reports the alarm.

Parameter 5, Parameter 6 (VLAN ID) Indicate the VLAN ID of the MEP.

Parameter 7 (Direction) Indicates the direction of the local MEP.l 0x00: The port is direction insensitive.l 0x01: The port is in the ingress direction.l 0x02: The port is in the egress direction.

Parameter 8 (Level) Indicates the MD level of the local MEP.l 0x00: consumer MEP level (low).l 0x01: consumer MEP level (medium).l 0x02: consumer MEP level (high).l 0x03: provider MEP level (low).l 0x04: provider MEP level (high).l 0x05: operator MEP level (low).l 0x06: operator MEP level (medium).l 0x07: operator MEP level (high).NOTE

Consumer indicates the customer, provider indicatesthe supplier, and operator indicates the carrier.

Impact on the SystemThe services among relevant standard MEPs may be interrupted or the data flow may beincorrectly routed.

Possible Causesl Cause 1: The names of the MDs and the MAs that the standard MEPs correspond to are

inconsistent.l Cause 2: The levels of the MDs that the standard MEPs correspond to are different.l Cause 3: The physical connection is incorrect.


Maintenance Guide


Issue 04 (2010-10-30)

Procedure

Step 1 Cause 1: The names of the MDs and the MAs that the standard MEPs correspond to areinconsistent.(1) Check whether the names of the MDs and the MAs that the standard MEPs correspond to

are the same.

If... Then...

The MD names or MA names aredifferent

Re-configure the MA names and MA namesto ensure consistency at both ends.

The MD names or MA names are thesame at both ends

Go to Cause 2.

Step 2 Cause 2: The levels of the MDs that the standard MEPs correspond to are different.(1) Check whether the MD levels of the standard MEPs are the same.

If... Then...

The MD levels are different Re-configure the MD levels to ensureconsistency at both ends.

The MD levels are the same at both ends Go to Cause 3.

Step 3 Cause 3: The physical connection is incorrect.(1) Check the physical connection of the Ethernet service route and rectify the fault on the

physical connection if any.

----End


A.2.32 ETH_CFM_UNEXPERI

DescriptionThe ETH_CFM_UNEXPERI is an alarm indicating the errored frame. This alarm occurs whenthe system receives invalid CCM packets.

Attribute






A-65


Name Meaning







Impact on the Systeml 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, the

connectivity check (CC) periods are different, and the IDs of the MEPs are in conflict.l Cause 3: The service is looped back and the looped packet is received.l Cause 4: A software fault occurs at the MEP at the transmit end.

Procedure

Step 1 Cause 1: No remote MEP is configured.(1) Check whether the remote MEP is configured. If not, configure the remote MEP first.

Step 2 Cause 2: The configuration of the MEPs at both ends are inconsistent. For example, 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.


Maintenance Guide


Issue 04 (2010-10-30)

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.

If... Then...

The IDs are in conflict Change the conflicting IDs.

The IDs are not in conflict Go to Cause 2.

Step 3 Cause 3: The service is looped back and the looped packet is received.

(1) Enable the loop detection function of IEEE 802.3ah ETH-OAM. Check whether any loopexists at each IP port of the service trail. If yes, release the loop and clear the alarm.

Step 4 Cause 4: A software fault occurs at the MEP at the transmit end.

(1) Perform a warm reset on the Ethernet board where the remote MEP is located. For details,see 7.6.2 Warm Resetting.

----End

Related Information

None.

A.2.33 ETH_CFM_LOC

Description

The ETH_CFM_LOC is an alarm indicating the loss of connectivity. This alarm occurs whenthe system fails to receive CCM packets from the remote MEP in 3.5 connectivity check (CC)periods successively.

Attribute



Parameters




A-67

Name Meaning


Indicate the number of the port where the alarmis reported.





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

Impact on the Systeml The LB and LT detection functions of IEEE 802.1ag ETH-OAM are unavailable.l The services among relevant standard MEPs may be interrupted.

Possible 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 MEP

belongs is faulty.l Cause 3: Serious congestion occurs on the network.

Procedure

Step 1 Cause 1: The line between the local standard MEP and the remote standard MEP is interrupted.(1) Check whether the physical links (such as cables or fibers) connecting the services at the

MEPs of the two ends are correct.

If... Then...

The connection is not correct Re-connect the cables to rectify the faults on physicallinks.


Maintenance Guide


Issue 04 (2010-10-30)

If... Then...


Step 2 Cause 2: The Ethernet service in the maintenance association (MA) to which the local MEPbelongs is faulty.(1) Check whether the Ethernet service in the maintenance association (MA) to which the local

MEP belongs is configured correctly.

If... Then...

The connection is not correct Modify the configuration of the Ethernet services toensure consistency at both ends.


Step 3 Cause 3: Serious congestion occurs on the network.(1) Check the utilization of bandwidth. If the bandwidth is exhausted, increase the bandwidth

or eliminate the source that transmits a large amount of invalid data.

----End


A.2.34 ETH_CFM_RDI

DescriptionThe ETH_CFM_RDI is an alarm indicating CCM packets with RDI received from the remoteMEP. This alarm occurs when the system receives CCM packets with RDI from the remoteMEP.

Attribute




Name Meaning





A-69

Name Meaning


Parameter 7 (Direction) Indicate 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: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) Indicate the ID of the remote MEP.

Impact on the Systeml The LoopBack (LB) and LinkTrace (LT) detection functions of IEEE 802.1ag ETH-OAM

are unavailable.l The services among relevant standard MEPs may be interrupted.

Possible Causesl Cause 1: The remote MEP fails to receive correct CCM packets.l Cause 2: The software is reset or another software fault occurs at the remote MEP.

Procedure

Step 1 Cause 1: The remote MEP fails to receive correct CCM packets.(1) Determine the port that reports the alarm according to the alarm parameters.(2) Check whether the remote MEP that is connected to the port reports the

ETH_CFM_LOC, ETH_CFM_MISMERGE, or ETH_CFM_UNEXPERI alarm.

If... Then...

Any of the preceding alarms occurs Clear the alarm at the remote end.

No such alarms occur Go to Cause 2.

Step 2 Cause 2: The software is reset or another software fault occurs at the remote MEP.(1) Check whether the equipment at the remote MEP is reset.


Maintenance Guide


Issue 04 (2010-10-30)

If... Then...

The equipment is reset Rectify the fault and then end the alarm handling.

The alarm is not reported Perform a warm reset on the board where the remote MEPis located. For details, see 7.6.2 Warm Resetting.

----End

Related Information

None.

A.2.35 ETH_LOS

Description

The ETH_LOS is an alarm indicating the loss of Ethernet port connection.

Attribute



Parameters


Name Meaning

Parameter 1 Indicates the ID of the port that reports the alarm. For example,0x01 indicates that the alarm is reported by Ethernet port 1 of theboard.

Parameter 2, Parameter 3 The values are always 0x00 0x01.


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

Possible Causesl Cause 1: The negotiation fails because the transmit port and receive port work in different

modes.l Cause 2: The link of electrical cable or optical fiber is faulty.l Cause 3: The equipment is faulty.



A-71

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 link of electrical cable or optical fiber is faulty.(1) Check the network cable or optical fiber connected to the port that reports the alarm.

If... Then...

The network cable is loose or damaged Connect the network cable properly 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.

The connection is normal Go to Cause 3.

Step 3 Cause 3: The equipment is faulty.(1) Check whether any fault occurs on the equipment interconnected with the port that reports

the alarm.

If... Then...

The equipment is faulty Rectify the fault.

The equipment is normal Replace the alarmed board of the local site.

----End


A.2.36 ETHOAM_DISCOVER_FAIL

DescriptionThe ETHOAM_DISCOVER_FAIL is an alarm indicating that the point-to-point Ethernet OAMnegotiation fails. This alarm occurs when the OAM function is enabled at a port of a board andthe negotiation between the port and the opposite equipment fails.


Maintenance Guide


Issue 04 (2010-10-30)

Attribute



Parameters


Name Meaning

Parameter 1 Indicates the ID of the port that reports the alarm.


Parameter 4 Indicates the reason why the negotiation fails.

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

the requirements of the local end.l 0x05: The OAM configuration of the local end does not meet

the requirements of the opposite end.l 0x06-0xFF: Other unknown reasons.


The OAM function based on IEEE802.3ah is unavailable.

Possible Causesl Cause 1: The physical port of the local end is faulty.

l Cause 2: The P2P OAM protocol is not enabled at the opposite end.

l Cause 3: The OAM configuration at both ends is inconsistent.

Procedure

Step 1 Cause 1: The physical port of the local end is faulty.

(1) Check whether the physical port is faulty. Replace the alarmed board.

Step 2 Cause 2: The P2P OAM protocol is not enabled at the opposite end.



A-73

(1) Enable the P2P OAM protocol at the opposite end. For details, see Enabling the OAMAuto-Discovery Function.

Step 3 Cause 3: The OAM configuration at both ends is inconsistent.

(1) Reconfigure the P2P OAM protocol and ensure the consistency at both ends. For details,see Enabling the OAM Auto-Discovery Function.

----End

Related Information

None.

A.2.37 ETHOAM_RMT_CRIT_FAULT

Description

The ETHOAM_RMT_CRIT_FAULT is an alarm indicating that a critical fault occurs regardingthe point-to-point Ethernet OAM function at the remote end. This alarm occurs when a port withthe OAM function enabled receives the OAM packets that contain critical fault information fromthe opposite end.

Attribute



Parameters


Name Meaning



Parameter 4 Indicates the type of the fault.

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

opposite end.l 0x03-0xFF: Other faults.


Maintenance Guide


Issue 04 (2010-10-30)


When the ETHOAM_RMT_CRIT_FAULT alarm occurs, the services on the link may beinterrupted.

Possible Causesl Cause 1: A link fault occurs at the remote MEP.

l Cause 2: Irrecoverable problems such as power failure occur at the remote MEP.

l Cause 3: Other faults occur at the remote MEP.

Procedure

Step 1 Determine the fault type according to Parameter 4 and handle the fault accordingly.

If... Then...

The value of Parameter 4 is 0x01 Go to Cause 1.


The value of Parameter 4 is 0x03-0xFF, Go to Cause 3.

Step 2 Cause 1: A link fault occurs at the remote MEP.(1) Handle ETH_LOS and LINK_ERR of the remote port.

Step 3 Cause 2: Irrecoverable problems such as power failure occur at the remote MEP.(1) Handle the problems such as power failure at the remote MEP.

Step 4 Cause 3: Other faults occur at the remote MEP.(1) Contact Huawei technical support engineers.

----End

Related Information

None.

A.2.38 ETHOAM_RMT_LOOP

Description

The ETHOAM_RMT_LOOP is an alarm indicating that the point-to-point Ethernet OAMfunction detects a remote loopback. This alarm occurs when the local equipment initiates aremote loopback or responds to the remote loopback initiated by the opposite equipment.

Attribute





A-75


Name Meaning



Parameter 4 l 0x01: The local equipment initiates a remote loopback.l 0x02: The local equipment responds to the remote loopback

initiated by the opposite equipment.

Impact on the SystemWhen the ETHOAM_RMT_LOOP alarm occurs, the services on the link are interrupted.

Possible Causesl Cause 1: The local end issues a loopback command and the opposite end responds to the

command.l Cause 2: The opposite end issues a loopback command and the local end responds to the

command.

Procedure

Step 1 Check whether the loopback is initiated by the local end or by the remote end.

Step 2 Cause 1: The local end issues a loopback command and the opposite end responds to thecommand.(1) Determine the causes of the loopback at the local end and release the loopback.

Step 3 Cause 2: The opposite end issues a loopback command and the local end responds to thecommand.(1) Determine the causes of the loopback at the opposite end and release the loopback.

----End



Maintenance Guide


Issue 04 (2010-10-30)

A.2.39 ETHOAM_RMT_SD

DescriptionThe ETHOAM_RMT_SD is an alarm indicating that the point-to-point Ethernet OAM functiondetects signal degradation at the remote end. This alarm occurs when a port with the OAMfunction enabled receives link event notification packets from the opposite end.

Attribute




Name Meaning



Parameter 4 Indicates the type of the received link event:

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

Impact on the SystemWhen the ETHOAM_RMT_SD alarm occurs, the performance of services degrade.

Possible Causesl Cause 1: The link event notification function is enabled at the opposite end.l Cause 2: The link performance thresholds of the opposite end are inappropriate.l Cause 3: The link performance deteriorates.

Procedure

Step 1 Cause 1: The link event notification function is enabled at the opposite end.(1) Check whether the link event notification function is enabled at the opposite end.



A-77

If... Then...

The link event notification function isenabled at the opposite end

Disable the link event notification functionat the opposite end.

The link event notification function isdisabled at the opposite end

Go to Cause 2.

Step 2 Cause 2: The link performance thresholds of the opposite end are inappropriate.(1) Check whether the link performance thresholds of the opposite end are appropriate.

If... Then...

The link performance thresholds of theopposite end are inappropriate

Set the thresholds to appropriate values.

The link performance thresholds of theopposite end are appropriate

Go to Cause 3.

Step 3 Cause 3: The link performance deteriorates.(1) Improve the link performance at the opposite end so that the opposite end does not send

any link event packet to the local end. Then, the ETHOAM_RMT_SD alarm at the localend clears automatically.

----End

Related Information

None.

A.2.40 ETHOAM_SELF_LOOP

Description

The ETHOAM_SELF_LOOP is an alarm indicating the loopback of the MAC port that runs thepoint-to-point OAM protocol. This alarm occurs when the MAC port of a board receives theOAM protocol packets sent by the port or the board after the loopback detection function isenabled.

Attribute


Major Environmental alarms

Parameters



Maintenance Guide


Issue 04 (2010-10-30)

Name Meaning

Parameter 1 Indicates the port ID.


Parameter 4 Indicates the loopback type.

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

Impact on the SystemA network storm may occur owing to the loopback.

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 a PHY/MAC loopback is manually configured at the port.l Cause 2: Two ports of the board are connected through cables or two ports of the board are

accessed to the same LAN.

Procedure

Step 1 Determine the loopback type according to Parameter 4, and then handle the loopbackaccordingly.

If... Then...



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 a 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 NMS). Then, the self-loop is released.

A self-loop is performed at the cables of theport

Reconnect the cables to release the self-loop.

The port is accessed to a LAN with a self-loop

Release the loopback of the LAN, ordisconnect the port from the LAN.

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.



A-79

If... Then...

The two ports are connected throughcables

Disconnect the cables to release the self-loop.

The two ports are accessed to the sameLAN

Disconnect a port from the LAN to releasethe self-loop.

----End

Related Information

None.

A.2.41 ETHOAM_VCG_SELF_LOOP

Description

The ETHOAM_VCG_SELF_LOOP is an alarm indicating that the point-to-point OAM functiondetects a loopback at the VCTRUNK port. This alarm occurs when the loopback detectionfunction is enabled and the VCTRUNK port receives the OAM protocol packets transmitted bythe port itself or the board where the VCTRUNK port resides.

Attribute


Major Environment alarm

Parameters


Name Meaning


Parameter 2, Parameter 3 Indicate the ID of the VCTRUNK port. Parameter 2 indicates themost significant bit (MSB) and Parameter 3 indicates the leastsignificant bit (LSB).

Parameter 4 Indicates the loopback type.

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


Maintenance Guide


Issue 04 (2010-10-30)

Impact on the SystemWhen the ETHOAM_VCG_SELF_LOOP alarm occurs, a network storm may occur owing tothe loopback.

Possible Causesl Cause 1: A loopback occurs on the lines connected to one VCTRUNK.l Cause 2: The lines connected to two VCTRUNKs on the same board are interconnected.

Procedure

Step 1 Browse alarms on the NMS and determine the alarmed VCTRUNK according to Parameter 2.Then, determine the loopback type according to Parameter 4.

If... Then...



Step 2 Cause 1: A loopback occurs on the lines connected to one VCTRUNK.(1) Reconfigure the lines connected to the VCTRUNK port and ensure that the port is not self-

looped.

Step 3 Cause 2: The lines connected to two VCTRUNKs on the same board are interconnected.(1) Reconfigure the lines connected to the VCTRUNK ports and ensure that the lines connected

to any two VCTRUNK ports on the same board are not interconnected.

----End


A.2.42 EX_ETHOAM_CC_LOS

DescriptionThe EX_ETHOAM_CC_LOS is an alarm indicating the loss of periodic connectivity check(CC) packets. This alarm occurs when the sink MEP fails to receive CC packets from the samesource MEP in a period (3.5 transmission periods of CC packets at the source MEP).

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



A-81

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 ID of the MEP that reports the alarm.

Parameter 2, Parameter 3 Indicates the number of the Ethernet port that reports the alarm.

l Port number: 0x0001-0x0000 + MAX_ETH_PORT.l VCTRUNK port number: 0x8001-0x8000 +

MAX_ETH_VCTRUNK.NOTEl MAX_ETH_PORT indicates the maximum MAC port number

supported by a board.

l MAX_ETH_VCTRUNK indicates the maximum VCTRUNK portnumber supported by a board.

Parameter 4, Parameter 5 Indicate the service VLAN ID.

l For a service with a VLAN tag, the VLAN ID ranges from0x0000 to 0x0FFF.

l For a service without any VLAN tag, the VLAN ID is 0xFFFF.

Parameter 6 Indicates the maintenance domain level.

l 0x00: consumer MEP level (high).l 0x01: consumer MEP level (medium).l 0x02: consumer MEP level (low).l 0x03: provider MEP level (high).l 0x04: provider MEP level (low).l 0x05: operator MEP level (high).l 0x06: operator MEP level (medium).l 0x07: operator MEP level (low).NOTE

Consumer indicates the customer, provider indicates the supplier, andoperator indicates the carrier.

Parameter 7 Indicates the source MEP ID of CC packets.

Parameter 8 Indicates the sink MEP ID of CC packets.

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

Impact on the SystemA unidirectional connectivity failure occurs in the Ethernet service between two MEPs.


Maintenance Guide


Issue 04 (2010-10-30)

Possible Causesl Cause 1: The line between two MEPs is interrupted.l Cause 2: The Ethernet services in the MA to which the alarmed MEP belongs are faulty.l Cause 3: The services between two MEPs are congested or interrupted.

Procedure

Step 1 Cause 1: The line between two MEPs is interrupted.(1) Check whether the physical links (such as network cables or optical fibers) that carry

services between the two MEPs are correctly connected.

If... Then...

The physical links are incorrectlyconnected

Re-connect the cables to rectify the faultson physical links.

The physical links are correctly connected Go to Cause 2.

Step 2 Cause 2: The Ethernet services in the MA to which the alarmed MEP belongs are faulty.(1) Check whether the Ethernet services in the MA to which the alarmed MEP belongs are

configured correctly.

If... Then...

The Ethernet services are configuredincorrectly

Change the configuration and ensureconsistency at both ends.

The Ethernet services are configuredcorrectly

Go to Cause 3.

Step 3 Cause 3: The services between two MEPs are congested or interrupted.(1) Check the bandwidth utilization. If the bandwidth is exhausted, increase the bandwidth or

eliminate any source that transmits a large amount of invalid data.

----End


A.2.43 EX_ETHOAM_MPID_CNFLCT

DescriptionThe EX_ETHOAM_MPID_CNFLCT is an alarm indicating the conflict of MPIDs. This alarmoccurs when two MEPs on one MD have the same maintenance point identity (MPID) and oneMEP receives the packets from the other MEP.



A-83

Attribute


Major Environment alarm

Parameters


Name Meaning

Parameter 1 Indicates the MPID associated with the alarm.

Parameters 2, Parameter 3 Indicate the number of the Ethernet port that reports the alarm.

l MAC port number: 0x0001-0x0000 + MAX_ETH_PORT.l VCTRUNK port number: 0x8001-0x8000 +

MAX_ETH_VCTRUNK.NOTEl MAX_ETH_PORT indicates the maximum MAC port number

supported by a board.

l MAX_ETH_VCTRUNK indicates the maximum VCTRUNK portnumber supported by a board.

Parameters 4, Parameter 5 Indicate the service VLAN ID.

l For a service with a VLAN tag, the VLAN ID ranges from0x0000 to 0x0FFF.

l For a service without any VLAN tag, the VLAN ID is 0xFFFF.

Parameter 6 Indicates the maintenance domain level.

l 0x00: Consumer MEP level (high).l 0x01: Consumer MEP level (middle).l 0x02: Consumer MEP level (low).l 0x03: Provider MEP level (high).l 0x04: Provider MEP level (low).l 0x05: Operator MEP level (high).l 0x06: Operator MEP level (medium).l 0x07: Operator MEP level (low).NOTE

Consumer indicates the customer, provider indicates the supplier, andoperator indicates the carrier.


Maintenance Guide


Issue 04 (2010-10-30)

Name Meaning

Parameter 7 Indicates the ID of the local MEP.

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


MPIDs must be unique on a network. When the EX_ETHOAM_MPID_CNFLCT alarm occurs,the LB and LT functions are abnormal and OAM packets are received incorrectly.

Possible Causes

Cause 1: At least two MEPs in an MD have the same MPID.

Procedure

Step 1 Cause 1: At least two MEPs in an MD have the same MPID.(1) Check this alarm on the NMS. Determine the associated MPID according to Parameter 1.(2) Query the information about the MEP. Delete the incorrect MEPs and create MEPs with

unique MPIDs.

----End

Related Information

None.

A.2.44 EXT_SYNC_LOS

Description

The EXT_SYNC_LOS is an alarm of the loss of external clock sources.

Attribute


Critical Equipment alarm

Parameters




A-85

Name Meaning

Parameter 1 Indicates the ID of the lost external clock source. For example, 0x01 indicatesthat external clock source 1 is lost.

Impact on the Systeml When the EXT_SYNC_LOS alarm occurs, if only the external clock source and the internal

clock source are configured in the clock source priority list, the NE traces the internal 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 Causes

Cause 1: The external clock source is configured in the clock source priority list, but the externalclock source cannot be detected or become invalid.

Procedure

Step 1 Cause 1: The external clock source is configured in the clock source priority list, but the externalclock source cannot be detected or become invalid.

(1) Check whether the equipment that provides the external clock source is faulty.

If... Then...


The equipment is normal Go to the next step.

(2) Check whether the cable that connects the external clock source is normal.

If... Then...

The cable is abnormal Replace the cable.

The cable is normal Replace the PXC board.

----End

Related Information

None.

A.2.45 F1PORT_FAILED

Description

The F1PORT_FAILED is an alarm indicating that synchronous data interfaces fail. This alarmoccurs when the software configures data of synchronous data interfaces but the hardware ofthe SCC board does not support the data.


Maintenance Guide


Issue 04 (2010-10-30)

Attribute



Parameters

None.


When the F1PORT_FAILED alarm occurs, the service configuration for synchronous datainterfaces is invalid.

Possible Causes

Cause 1: The pluggable storage card installed on the SCC board stores the configuration datafor synchronous data interfaces, but the hardware of the SCC board does not support anysynchronous data interface.

Procedure

Step 1 Cause 1: The pluggable storage card installed on the SCC board stores the configuration datafor synchronous data interfaces, but the hardware of the SCC board does not support anysynchronous data interface.

(1) Determine whether the data of synchronous data interfaces is necessary.

If... Then...

The data is necessary Go to the next step.

The data is unnecessary Delete the data of synchronous data interfaces through theNMS.

(2) Use the SCC board of SL61 VER.C or a later version.

----End

Related Information

None.

A.2.46 FAN_FAIL

Description

The FAN_FAIL is an alarm indicating that the fan is faulty.



A-87

Attribute



Parameters

None.


When the FAN_FAIL alarm occurs, the heat dissipation of the system is affected.

Possible Causesl Cause 1: The board and the backplane are connected incorrectly.

l Cause 2: The board is faulty.

Procedure

Step 1 Cause 1: The board and the backplane are connected incorrectly.

(1) Remove the fan board. Clean the dust on the fan and reinsert the fan board.

If... Then...

The alarm clears after the board isremoved and inserted


The alarm persists after the board isremoved and inserted

Go to Cause 2.

Step 2 Cause 2: The board is faulty.

(1) Replace the alarmed fan board.

----End

Related Information

None.

A.2.47 FCS_ERR

Description

The FCS_ERR is an alarm indicating the errors of frame check sequence (FCS). This alarmoccurs when a board detects FCS errors in the received frames.


Maintenance Guide


Issue 04 (2010-10-30)

Attribute




Name Meaning



Impact on the SystemWhen the FCS_ERR alarm occurs, if the encapsulation protocols or encapsulation parametersare inconsistent at both ends of Ethernet services, the services may have errors and even becomeinterrupted.

Possible Causesl Cause 1: The encapsulation protocols or encapsulation parameters are inconsistent at both

ends of services.l Cause 2: Service channels have errors.l Cause 3: The board is faulty.

Procedure

Step 1 Cause 1: The encapsulation protocols or encapsulation parameters are inconsistent at both endsof services.(1) Check whether the encapsulation protocols or encapsulation parameters are consistent at

both ends of services.

If... Then...

The protocols are inconsistent Correct the configuration data.

The protocols are consistent Go to the next step.

Step 2 Cause 2: Service channels have errors.(1) Check whether the encapsulation parameters are consistent at both ends of services.

If... Then...

The parameters are inconsistent Correct the configuration data.



A-89

If... Then...

The parameters are consistent Go to the next step.

(2) Check whether any error alarm or performance event occurs on the line board that carriesthe services.

If... Then...

Yes Handle the alarm or performance event.

No Go to the next step.

Step 3 Cause 3: The board is faulty.(1) Replace the alarmed board.

If... Then...




Replace the PXC board.

----End


A.2.48 FLOW_OVER

DescriptionThe FLOW_OVER is an alarm indicating that the data flow received by the Ethernet port exceedsthe threshold.

Attribute




Name Meaning

Parameter 1 Indicates the ID of the path that reports the alarm.


Maintenance Guide


Issue 04 (2010-10-30)

Name Meaning

Parameter 2 Indicates the ID of the subboard.

Parameter 3 Indicates the port ID. For example, 0x01 indicates that the alarm is reported byEthernet port 1 of the board.


When the FLOW_OVER alarm occurs, the extra data may be discarded by the port.

Possible Causes

Cause 1: The opposite end transmits excessive data flow.

Procedure

Step 1 Cause 1: The opposite end transmits excessive data flow.

(1) Configure the QoS policies at the opposite end to reduce the data flow that the oppositeend transmits to the local end.

----End

Related Information

None.

A.2.49 HARD_BAD

Description

The HARD_BAD is an alarm indicating hardware errors.

Attribute



Parameters




A-91

Name Meaning

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

Impact on the SystemThe board that reports the alarm fails to work. If the board is configured with 1+1 protection,the protection switching may be triggered.

Possible Causesl Cause 1 of the alarm reported by a board of the IDU: The board and backplane are connected

improperly.l Cause 2 of the alarm reported by a board of the IDU: The board is faulty.l Cause 3 of the alarm reported by a board of the IDU: The slot is faulty.

Cause of the alarm reported by a board of the ODU: The ODU is faulty.


Maintenance Guide


Issue 04 (2010-10-30)

Procedure

Step 1 Cause 1 of the alarm reported by a board of the IDU: The board and backplane are connectedimproperly.

(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 clears.

If... Then...

The alarm disappears after the board isremoved and inserted



Ensure that the board is normal.

Step 2 Cause 2 of the alarm reported by a board of the IDU: The board is faulty.

(1) Check whether the IDU is properly grounded.

(2) Replace the board that reports the alarm, and then check whether the alarm clears. Fordetails, see 6 Part Replacement.

If... Then...




Ensure that the slot is normal.

Step 3 Cause 3 of the alarm reported by a board of the IDU: The slot is faulty.

(1) Contact Huawei engineers to handle the faulty slot.TIPThe slot becomes faulty due to broken pins or bent pins. Remove the board, and use a torch to observewhether there is any broken pin or bent pin.

(2) If an idle slot is available, insert the board in the idle slot and add the board on the NMSagain. Then, the board can work normally.

Step 4 Cause of the alarm reported by a board of the ODU: The ODU is faulty.

(1) Replace the ODU that reports the alarm. For details, see 6.12 Replacing an ODU.

----End

Related Information

None.

A.2.50 HP_CROSSTR

Description

The HP_CROSSTR is an alarm indicating a threshold-crossing event of the higher order path.This alarm occurs when a board detects any threshold-crossing event of the higher order path.



A-93

Attribute


Minor Service alarm

Parameters


Name Meaning

Parameter 1 Indicates the performance monitoring period.

l 0x01: 15 minutesl 0x02: 24 hours

Parameter 2, Parameter 3 Indicate the ID of the performance event that causes the alarm.


When the HP_CROSSTR alarm occurs, a large number of errors occur in services, and servicesmay be interrupted.

Possible Causes

Cause 1: Higher order path errors cross the preset threshold.

Procedure

Step 1 Cause 1: Higher order path errors cross the preset threshold.

(1) Check the threshold-crossing records to find out the performance event that causes thealarm. For details, see 7.3.8 Browsing the Performance Event Threshold-CrossingRecords.

(2) Handle the threshold-crossing performance event.

----End

Related Information

None.

A.2.51 HP_LOM


Maintenance Guide


Issue 04 (2010-10-30)

Description

The HP_LOM is an alarm of the loss of the higher order path multiframe. This alarm occurswhen the board detects that byte H4 is inconsistent with the expected multiframe sequence.

Attribute



Parameters


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 thecorresponding board.

Parameter 2, Parameter 3 Indicates the ID of the AU-4 path that reports the alarm. Forexample, 0x00 0x01 indicate that the alarm is reported by path 1 ofthe SDH signal.


When the HP_LOM alarm occurs, the service on the path that reports the alarm is interrupted.If the service is configured with protection, the protection switching is also triggered.

Possible Causesl Cause 1: The transmit unit of the opposite site is faulty.

l Cause 2: The receive unit of the local site is faulty.

Procedure

Step 1 Cause 1: The transmit unit of the opposite site is faulty.(1) Replace the line board or IF board of the opposite site. For details, see 6 Part

Replacement. Then, check whether the alarm clears.

If... Then...

The alarm clears The fault is rectified. End the alarm handling.

The alarm persists Replace the PXC board of the local site.

Step 2 Cause 2: The receive unit of the local site is faulty.



A-95

(1) Replace the board that reports the alarm. For details, see 6 Part Replacement.

----End


A.2.52 HP_RDI

DescriptionThe HP_RDI is an alarm indicating a remote defect in the higher order path. This alarm occurswhen the board detects that bit 5 of byte G1 is 1.

Attribute




Name Meaning



Impact on the SystemWhen the HP_RDI occurs, the service at the local site is not affected. The service received bythe opposite site, however, is interrupted.

Possible CausesCause 1: The local site detects the message that is returned by the opposite site and indicates thehigher order path remote receive failure.

ProcedureStep 1 Cause 1: The local site detects the message that is returned by the opposite site and indicates the

higher order path remote receive failure.


Maintenance Guide


Issue 04 (2010-10-30)

(1) Determine the AU-4 path that reports the alarm based on the alarm parameter.(2) Clear the alarms such as HP_LOM and B3_EXC that the AU-4 path reports at the opposite

site.

----End

Related Information

None.

A.2.53 HP_REI

Description

The HP_REI is an alarm indicating the higher order path remote error. This alarm occurs whenthe board detects that bits 1-4 of byte G1 take a value from 1 to 8.

Attribute


Warning Communication alarm

Parameters


Name Meaning




The service at the local site is not affected. The service received by the opposite site, however,has errors.

Possible Causes

The local site detects the message that is returned by the opposite site and indicates the higherorder path remote errors.



A-97

Procedure

Step 1 Cause: The local site detects the message that is returned by the opposite site and indicates thehigher order path remote receive failure.

(1) Determine the AU-4 path that reports the alarm based on the alarm parameter.

(2) Handle the HP_BBE performance event that the AU-4 path reports on the opposite NE.

----End

Related Information

None.

A.2.54 HP_SLM

Description

The HP_SLM is an alarm indicating signal label mismatch in the higher order path. This alarmoccurs when the board detects the C2 byte mismatch.

Attribute



Parameters


Name Meaning




None.


Maintenance Guide


Issue 04 (2010-10-30)

Possible Causesl Cause 1: The receivable C2 byte at the local site does not match with the C2 byte transmitted

at the opposite site.l Cause 2: Configuration data is incorrect.

Procedure

Step 1 Determine the line port and AU-4 path that report the alarm based on the alarm parameter.

Step 2 Cause 1: The receivable C2 byte at the local site does not match with the C2 byte transmitted atthe opposite site.(1) Configure the same service type at the source and sink of the AU-4 path. For details, see

Configuring VC-4 POHs.

Step 3 Cause 2: Configuration data is incorrect.(1) If the port that reports the alarm is the SDH port that is interconnected with the ATM/

Ethernet equipment, configure the service as VC-4 pass-through service. For details, seeCreating Cross-Connections for SNCP Services.

----End


A.2.55 HP_TIM

DescriptionThe HP_TIM is an alarm indicating that the higher order path trace identifier is mismatched.This alarm occurs when the board detects the J1 byte mismatch.

Attribute




Name Meaning




A-99

Name Meaning


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 J1 byte to be received at the local site does not match the J1 byte transmitted

at the opposite site.l Cause 2: Configuration data is incorrect.

Procedure

Step 1 Determine the line port and AU-4 path that report the alarm based on the alarm parameter.

Step 2 Cause 1: The J1 byte to be received at the local site does not match the J1 byte transmitted atthe opposite site.(1) Disable the J1 byte to be received at the local site or set the J1 byte to be received at the

local site to the same as the transmitted J1 byte at the opposite site. For details, seeConfiguring VC-4 POHs.

Step 3 Cause 2: Configuration data is incorrect.(1) If the port that reports the alarm is the SDH port that is interconnected with the ATM/

Ethernet equipment, configure the service as VC-4 pass-through service. For details, seeCreating Cross-Connections of Point-to-Point Services or Creating Cross-Connections forSNCP Services.

If... Then...

The alarm clears after the configuration ischanged


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 Point-to-Point Services or Creating Cross-Connections for SNCPServices.

----End


A.2.56 HP_UNEQ


Maintenance Guide


Issue 04 (2010-10-30)

DescriptionThe HP_UNEQ is an alarm indicating the unequipped higher order path. This alarm occurs whenthe board detects that the C2 byte is 0.

Attribute




Name Meaning



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 site is configured with services, but the corresponding

line port at the opposite site is not configured with services.l Cause 2: The C2 byte on the opposite end is set to 0.

Procedure

Step 1 Cause 1: The line port at the local site is configured with services, but the corresponding lineport at the opposite site is not configured with services.(1) Configure line services at the opposite site. For details, see Creating Cross-Connections of

Point-to-Point Services or Creating Cross-Connections for SNCP Services.

Step 2 Cause 2: The C2 byte at the opposite site is set to 0.(1) Change the setting of the C2 byte. For details, see Configuring VC-4 POHs.

----End



A-101

Related Information

None.

A.2.57 HPAD_CROSSTR

Description

The 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

Parameters


Name Meaning


Parameter 2, Parameter 3 Indicate the ID of the path that reports the alarm.

Parameter 4, Parameter 5 l The higher two bits of Parameter 4 indicate the performancemonitoring period (01 for 15 minutes, and 02 for 24 hours).

l The lower six bits of Parameter 4 and Parameter 5 indicate theID of a performance event.


When the HPAD_CROSSTR alarm occurs, bit errors may occur in the service.

Possible Causes

The performance event of TU pointer justification crosses the preset threshold.

Procedure

Step 1 Cause: The performance event of TU pointer justification crosses the preset threshold.


Maintenance Guide


Issue 04 (2010-10-30)

(1) Check the threshold crossing records to find out the performance event of TU pointerjustification that crosses the preset threshold. For details, see 7.3.8 Browsing thePerformance Event Threshold-Crossing Records.


----End


A.2.58 IF_CABLE_OPEN

DescriptionThe IF_CABLE_OPEN is an alarm indicating that the IF cable is open-circuited.

Attribute




Name Meaning

Parameter 1 Indicates the ID of the IF port that reports the alarm. For example, 0x01 indicatesthat the alarm is reported by IF port 1 of the corresponding board.

Impact on the SystemThe services on the IF port are interrupted.

Possible Causesl Cause 1: The IF cable is loose or faulty.l Cause 2: The IF port of the IF board is damaged.l Cause 3: The power module of the ODU is faulty.

Procedure

Step 1 Cause 1: The IF cable is loose or faulty. Check whether the connector of the IF cable is loose orwhether the connector is not made properly.



A-103

(1) Check whether the connector of the IF cable is loose or whether the connector is not 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 not made properly Make a new IF cable connector.

None of the above Go to the next step.

(2) Check whether the surface of the IF fiber jumper and the IF cable is damaged, and test 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 specifiedrequirement

Replace the cable with a proper one.

The cable meets the specified requirement Go to Cause 2 or Cause 3.

Step 2 Cause 2: The IF port of the IF board is damaged.

(1) Replace the IF board that reports the alarm.

Step 3 Cause 3: The power module of the ODU is faulty.

(1) Replace the ODU connected to the IF board that reports the alarm.

----End

Related InformationNOTEWhen rectifying the faults on 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.2.59 IF_INPWR_ABN

Description

The IF_INPWR_ABN is an alarm indicating that the input IF power of the ODU is abnormal.

Attribute




Maintenance Guide


Issue 04 (2010-10-30)

Parameters


Name Meaning

Parameter 1 l 0x01: Indicates that the input power of the ODU is over high.l 0x02: Indicates that the input power of the ODU is over low.


The services on the ODU are interrupted. If 1+1 protection is configured, 1+1 HSB switchingmay be 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.

Procedure

Step 1 Cause 1: The IF board is faulty.

(1) Reseat the board. For details, see 6.1 Removing a Board or 6.2 Inserting a Board. Then,check whether the alarm clears.

If... Then...

The alarm clears End the alarm handling.

The alarm persists Go to the next step.

(2) Replace the IF board connected to the ODU that reports the alarm.

Step 2 Cause 2: The IF cable is faulty.

(1) Check whether the connector of the IF cable is loose or whether the connector is not 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 not made properly Terminating the IF Cable with Connectors again.

None of the above Go to the next step.



A-105

(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 specifiedrequirement

Replace the cable with a proper one.

The cable meets the specified requirement The IF board or ODU may be faulty.

Step 3 Cause 3: The ODU is faulty.(1) Replace the ODU that reports the alarm.

----End

Related InformationThe number of the logical slot for the ODU is the slot number of the IF board connected to theODU plus 10.

A.2.60 IF_MODE_UNSUPPORTED

DescriptionThe IF_MODE_UNSUPPORTED is an alarm indicating that the configured IF working modeis not supported. This alarm occurs when the board is not loaded with the FPGA file that supportsthe configured IF working mode.

Attribute




Name Meaning

Parameter 1 Indicates the number of the FPGA file that is loaded to the board.

l 0x01: Indicates that the ID of the FPGA file loaded to the board is 250.l 0x02: Indicates that the ID of the FPGA file loaded to the board is 002.

Impact on the SystemThe services on the IF port are interrupted.


Maintenance Guide


Issue 04 (2010-10-30)

Possible CausesThe board is not loaded with the FPGA file that supports the configured IF working mode, orthe FPGA file that supports the configured IF working mode is damaged.

Procedure

Step 1 Cause 1: The board is not loaded with the FPGA file that supports the configured IF workingmode, or the FPGA file that supports the configured IF working mode is damaged.(1) Contact Huawei engineers to upgrade the board software and the FPGA file.

----End


A.2.61 IN_PWR_HIGH

DescriptionThe IN_PWR_HIGH is an alarm indicating that the input optical power is over high.

Attribute




Name Meaning

Parameter 1 Indicates the ID of the optical interface that reports the alarm. For example, 0x01indicates that the alarm is reported by optical interface 1 of the correspondingboard.

Impact on the SystemThe service at the optical interface that reports the alarm has errors.

Possible Causesl Cause 1: The transmit power of the opposite site is over high.l Cause 2: The model of the selected optical module is incorrect.



A-107

l Cause 3: The optical module at the receive end is faulty.

Procedure

Step 1 Determine the optical interface that reports the alarm based on the alarm parameter.

Step 2 Cause 1: The transmit power of the opposite site is over high.

(1) Browse current performance events, and query the performance events of the transmitoptical 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 thereceived optical power.

Step 3 Cause 2: The model of the selected optical module is incorrect.

(1) Query the board manufacturing information report, and check whether the models ofthe SFP optical modules on both ends are proper.

If... Then...

The models are incorrect Contact Huawei engineers to replace the optical module.

The models are correct Go to Cause 3.

Step 4 Cause 3: The optical module at the receive end is faulty.

(1) Use the optical power meter to test the received optical power, and check whether thereceived optical power meets the requirement. If not, contact Huawei engineers to replacethe optical module.

----End

Related Information

The optical power threshold set for the IN_PWR_HIGH alarm is lower than the overload point.

SDH Interface Performance.

A.2.62 IN_PWR_LOW

Description

The IN_PWR_LOW is an alarm indicating that the input optical power is over low.

Attribute




Maintenance Guide


Issue 04 (2010-10-30)


Name Meaning


Impact on the SystemWhen 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 site is over low.l Cause 2: The model of the selected optical module is incorrect.l Cause 3: The optical module at the receive end is faulty.l Cause 4: The optical fiber performance degrades.

ProcedureStep 1 Determine the optical interface that reports the alarm based on the alarm parameter.

Step 2 Cause 1: The transmit power of the opposite site is over low.(1) Browse current performance events, and query the performance events of the transmit

optical power at the opposite site.

If... Then...

The transmit optical power does not meetthe requirement


The transmit optical power meets therequirement

Go to Cause 2.

Step 3 Cause 2: The model of the selected optical module is incorrect.(1) Query the board manufacturing information report, and check whether the models of

the SFP optical modules on both ends are proper.

If... Then...

The models are incorrect Contact Huawei engineers to replace the optical module.

The models are correct Go to Cause 3.

Step 4 Cause 3: The optical module at the receive end is faulty.(1) Use the optical power meter to test the received optical power, and check whether the

received optical power meets the requirement.



A-109

If... Then...

The received optical power meets therequirement


The received optical power does not meetthe requirement

Go to Cause 4.

Step 5 Cause 4: The optical fiber performance degrades.(1) Cleaning Fiber Connectors and Adapters.

If... Then...

The alarm clears after the connector iscleaned

The fault is rectified. End the alarm handling.

The alarm persists after the connector iscleaned

Replace the optical fiber.

----End

Related InformationThe optical power threshold set for the IN_PWR_LOW alarm is higher than the sensitivity point.

SDH Interface Performance.

A.2.63 J0_MM

DescriptionThe J0_MM is an alarm indicating that the trace identifier is mismatched. This alarm occurswhen the board detects a mismatch between the J0 bytes at both ends.

Attribute




Name Meaning



Maintenance Guide


Issue 04 (2010-10-30)

Name Meaning



None.

Possible Causes

The J0 byte to be received at the local site does not match the J0 byte transmitted at the oppositesite.

Procedure

Step 1 Cause: The J0 byte to be received at the local site does not match the J0 byte transmitted at theopposite site.

(1) Determine the line port that reports the alarm based on the alarm parameters.

(2) Disable the J0 byte to be received at the local site. For details, see Configuring RSOHs.

----End

Related Information

None.

A.2.64 K1_K2_M

Description

The K1_K2_M is an alarm indicating the K1/K2 byte mismatch. This alarm occurs when theboard detects that the channel numbers that are indicated by the transmitted K1 byte (bits 5-8)and the received K2 byte (bits 1-4) are different.

Attribute



Parameters




A-111

Name Meaning

Parameter 1 Indicates the type of the protection group.l 0x01: Indicates linear MSP.l 0x02: Indicates ring MSP.



When the K1_K2_M alarm occurs, the MSP protocol may fail and thus the protection switchingmay fail.

Possible Causesl Cause 1: The switching modes configured at both ends are different, that is, single-ended

switching mode at one end and dual-ended switching mode at the other end.

l Cause 2: The optical fiber connection is incorrect.


Procedure

Step 1 Cause 1: The switching modes configured at both ends are different, that is, single-endedswitching mode at one end and dual-ended switching mode at the other end.

(1) Check whether the switching modes configured at both ends are the same. For details, seeQuerying the Status of Linear MSP.

If... Then...

The switching modes configured at both endsare different

Set the switching modes to the same.

The switching modes configured at both endsare the same

Go to Cause 2.

Step 2 Cause 2: The optical fiber connection is incorrect.

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

If... Then...

The connection is not correct Connect the optical fiber properly.



(1) Replace the line board at the opposite site. Then, check whether the alarm clears.

If... Then...

Yes The fault is rectified. End the alarm handling.


Maintenance Guide


Issue 04 (2010-10-30)

If... Then...

No Replace the board that reports the alarm.

----End


A.2.65 K2_M

DescriptionThe 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 local NE.

Attribute




Name Meaning

Parameter 1 Indicates the type of the protection group.l 0x01: Indicates linear MSP.l 0x02: Indicates ring MSP.


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.



A-113

l Cause 3: The optical fiber connection is incorrect.


Procedure

Step 1 Cause 1: Two NEs of the linear MSP group are configured with different protection modes (1+1 or 1:N).

(1) Check whether two NEs of the linear MSP group are configured with different protectionmodes (1+1 or 1:1). For details, see Querying the Status of Linear MSP.

If... Then...

The protection modes are different Set the protection modes to the same.

The protection modes are the same Go to Cause 2.

Step 2 Cause 2: The MSP protocol is stopped on the opposite NE when the protection switching occurs.

(1) Check whether the MSP protocol is stopped on the opposite NE. For details, see Queryingthe Status of Linear MSP.

If... Then...

Yes Restart the MSP protocol on the opposite NE. For details, see Starting/Stopping theLinear MSP Protocol.

No Go to Cause 3.

Step 3 Cause 3: The optical fiber connection is incorrect.

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

If... Then...

The connection is not correct Connect the optical fiber properly.



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

If... Then...

Yes The fault is rectified. End the alarm handling.

No Replace the SCC board that reports the alarm. For details, see 6.10 Replacing theSCC Board.

----End

Related Information

None.


Maintenance Guide


Issue 04 (2010-10-30)

A.2.66 LAG_PORT_FAIL

DescriptionThe LAG_PORT_FAIL is an alarm indicating that a port in the LAG of the Ethernet fails. Thisalarm occurs when a port in the LAG is unavailable.

Attribute




Name Meaning

Parameter 1 Indicates the ID of the IP port.


Parameter 4 Indicates the cause of the protection failure.

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

Parameter 5 The value is always 0xff.

Impact on the SystemThe port in the LAG cannot share the service load, or the port does not transmit or receive anyservices.

Possible Causesl Cause 1: The port is disabled or the link is faulty.l Cause 2: The port is in the half-duplex mode.l Cause 3: The port fails to receive LACP packets.l Cause 4: The port detects a self-loop.



A-115

l Cause 5: other unknown reasons.

Procedure

Step 1 Determine the port where the alarm occurs and the alarm cause based on the alarm parameter.

If... Then...






Step 2 Cause 1: The port is disabled or the link is faulty.

(1) On the NMS, check whether the port in the LAG is enabled.

If... Then...

The port is not enabled Enable the port in the LAG group.

The port is enabled Check the link state of each port. If any link is faulty, rectifythe fault.

Step 3 Cause 2: The port is in the half-duplex mode.

(1) On the NMS, check the working mode of the port in the LAG group. If the port is in half-duplex mode, change the working mode of the port into full-duplex.

Step 4 Cause 3: The port fails to receive the LACP packets.

(1) On the NMS, check whether the LAG group is properly configured on the opposite end.

If... Then...

The LAG group is not properly configured Reconfigure the LAG group.

The LAG group is properly configured Go to the next step.

(2) Check whether the local port and the remote port transmit the LACP packets. If the LACPpackets are not transmitted, configure the ports at both ends to ensure that the packets canbe normally transmitted.

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

(1) Release the self-loop of the port.

Step 6 Cause 5: other unknown reasons

(1) Contact Huawei engineers to handle the fault.

----End

Related Information

None.


Maintenance Guide


Issue 04 (2010-10-30)

A.2.67 LAG_VC_PORT_FAIL

Description

The LAG_VC_PORT_FAIL is an alarm indicating that a VCG port in the LAG fails. This alarmoccurs when the VCTRUNK is unavailable.

Attribute



Parameters


Name Meaning


Parameter 2, Parameter 3 Indicate the number of the faulty VCG port in the LAG. Parameter2 indicates the most significant bit (MSB) and Parameter 3 indicatesthe least significant bit (LSB).

Parameter 4 Indicates the cause of the protection failure.

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

loop.l 0x05: Other unknown reasons.

Parameter 5 The value is always 0xff.


The port in the LAG cannot share the service load, and the port does not transmit or receive anyservices.

Possible Causesl Cause 1: The link of the port is faulty or fails.l Cause 2: The port fails to receive the LACP packets.



A-117

l Cause 3: The port detects a self-loop.

l Cause 4: other unknown reasons.

Procedure

Step 1 Determine the port where the alarm occurs and the alarm cause based on the alarm parameter.

If... Then...





Step 2 Cause 1: The port is disabled or the link is faulty.

(1) Check the link state of each port. If any link is faulty, rectify the fault.

Step 3 Cause 2: The port fails to receive the LACP packets.

(1) On the NMS, check whether the LAG group is properly configured on the opposite end.

If... Then...

The LAG group is not properly configured Reconfigure the LAG group.

The LAG group is properly configured Go to the next step.

(2) Check whether the local port and the remote port transmit the LACP packets. If the LACPpackets are not transmitted, configure the ports at both ends to ensure that the packets canbe normally transmitted.

Step 4 Cause 3: The port detects a self-loop.

(1) Release the self-loop of the port.

Step 5 Cause 4: other unknown reasons.

(1) Contact Huawei engineers to handle the fault.

----End

Related Information

None.

A.2.68 LASER_CLOSED

Description

The LASER_CLOSED is an alarm indicating that the laser is shut down. This alarm occurs whenthe laser is shut down by using the NMS.


Maintenance Guide


Issue 04 (2010-10-30)

Attribute



Parameters


Name Meaning



The optical interface fails to carry services.

Possible Causes

Cause 1: The laser on the local NE is shut down by using the NMS.

Procedure

Step 1 Cause 1: The laser on the local NE is shut down by using the NMS.

(1) Determine the optical interface that reports the alarm based on the alarm parameter.

(2) Find out the cause of shutting down the laser and start up the laser as soon as possible.

----End

Related Information

None.

A.2.69 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.



A-119

Attribute



Parameters


Name Meaning



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.


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 7.4.2 Querying a Board Manufacture 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) Contact Huawei engineers to replace the faulty optical module.


Maintenance Guide


Issue 04 (2010-10-30)

If... Then...

The alarm clears after the board is replaced End the alarm handling.

The alarm persists after the optical module is replaced Go to Cause 3.

Step 3 Cause 3: The board is faulty.(1) Replace the board that reports the alarm.

----End


A.2.70 LCAS_FOPR

DescriptionThe LCAS_FOPR is an alarm indicating that the Link Capacity Adjustment Scheme (LCAS)protocol in the transmit direction fails. This alarm occurs when the source end of the LCASmodule detects an abnormally that the LCAS negotiation is unavailable or incorrect.

Attribute




Name Meaning


Parameter 2, Parameter 3 Indicate the ID of the VCTRUNK that reports the alarm. Forexample, 0x00 0x01 indicate that the alarm is reported inVCTRUNK 1.

Impact on the SystemThe Ethernet service is not normal.

Possible Causesl Cause 1: Configuration data of the LCAS protocol is incorrect.



A-121

l Cause 2: The link is faulty.

ProcedureStep 1 Cause 1: Configuration data of the LCAS protocol is incorrect.

(1) Check whether the LCAS enable state and the LCAS parameters are the same at both endsof the link.

If... Then...

The LCAS enable state and the LCASparameters are not the same

Properly enable the LCAS protocol atboth ends.

The LCAS enable state and the LCASparameters are the same

Go to Cause 2.

(2) Check whether the configurations of the local and opposite NEs are correct. That is, checkwhether a VCG at one NE is connected to multiple VCGs at the opposite NE.

If... Then...

The configurations of the local and opposite NEs areincorrect

Correct the configuration data.

The configurations of the local and opposite NEs arecorrect

Go to Cause 2.

Step 2 Cause 2: The link is faulty.(1) Check whether the link where the service travels has errors or becomes faulty.

If... Then...

The link is faulty Rectify the fault.

The link is not faulty Go to the next step.

(2) Restart the LCAS protocol at both ends. Then, check whether the alarm clears.

If... Then...


The alarm persists Replace the board that reports the alarm.

----End


A.2.71 LCAS_FOPT

DescriptionThe LCAS_FOPT is an alarm indicating that the LCAS protocol in the transmit direction fails.This alarm occurs if the transmit unit of the LCAS module of a board detects an abnormal statein which the LCAS might fail to negotiate or cannot negotiate correctly.


Maintenance Guide


Issue 04 (2010-10-30)

Attribute



Parameters


Name Meaning




The Ethernet service is not normal.

Possible Causesl Cause 1: Configuration data of the LCAS protocol is incorrect.

l Cause 2: The link is faulty.

Procedure

Step 1 Cause 1: Configuration data of the LCAS protocol is incorrect.

(1) Check whether the LCAS enable state and the LCAS parameters are the same at both endsof the link.

If... Then...

The LCAS enable state and the LCASparameters are different

Properly enable the LCAS protocol atboth ends.

The LCAS enable state and the LCASparameters are the same

Go to Cause 2.

(2) Check whether configurations of the local and opposite NEs are correct. That is, checkwhether a VCG at one NE is connected to multiple VCGs at the opposite NE.

If... Then...

The configurations of the local and opposite NEs areincorrect

Correct the configuration data.



A-123

If... Then...

The configurations of the local and opposite NEs arecorrect

Go to Cause 2.

Step 2 Cause 2: The link is faulty.(1) Check whether the link where the service travels has errors or become faulty.

If... Then...

The link is faulty Rectify the fault.

The link is not faulty Go to the next step.

(2) Restart the LCAS protocol at both ends. Then, check whether the alarm clears.

If... Then...


The alarm persists Replace the board that reports the alarm.

----End


A.2.72 LCAS_PLCR

DescriptionThe LCAS_PLCR is an alarm indicating that a part of the LCAS bandwidth in the receivedirection is lost. This alarm occurs when a board detects that the number of paths that carry theoverloads in the receive direction of the VCTRUNK with the LCAS enabled is less than thepreset number and is not zero.

Attribute


Minor Service alarm


Name Meaning



Maintenance Guide


Issue 04 (2010-10-30)

Name Meaning


Impact on the SystemThe available Ethernet service bandwidth is smaller than the configured bandwidth.

Possible Causesl Cause 1: The number of paths or timeslots that are configured for the VCTRUNK at the

remote site is different from that at the local site.l Cause 2: Some paths in the transmit direction of the remote site are faulty.l Cause 3: Some paths in the receive direction of the local site are faulty.

Procedure

Step 1 Cause 1: The number of paths or timeslots that are configured for the VCTRUNK at the remotesite is different from that at the local site.(1) Check whether the VCTRUNKs at both ends are configured with the same number of

physical paths and timeslots.

If... Then...

The VCTRUNKs at both ends areconfigured with a different number ofphysical paths and timeslots

Correct the configuration data. For details,see Dynamically Increasing/Decreasing theVCTRUNK Bandwidth.

The VCTRUNKs at both ends areconfigured with the same number ofphysical paths and timeslots

Go to Cause 2.

Step 2 Cause 2: Some paths in the transmit direction of the remote site are faulty.(1) Check whether any path alarm exists in the transmit direction of the remote site.

If... Then...

The alarm is reported Clear the alarm immediately.

No alarm is reported Go to Cause 3.

Step 3 Cause 3: Some paths in the receive direction of the local site are faulty.(1) Replace the board that reports the alarm.

----End


A.2.73 LCAS_PLCT



A-125

DescriptionThe LCAS_PLCT is an alarm indicating that part of the LCAS bandwidth in the transmitdirection is lost. This alarm occurs when a board detects that the number of paths that carry theoverloads in the transmit direction of the VCTRUNK with the LCAS enabled is less than thepreset number and is not zero.

Attribute


Minor Service alarm


Name Meaning



Impact on the SystemThe available Ethernet service bandwidth is smaller than the configured bandwidth.


remote site is different from that at the local site.l Cause 2: Some paths in the receive direction of the remote site are faulty.l Cause 3: Some paths in the transmit direction of the local site are faulty.

Procedure

Step 1 Cause 1: The number of paths or timeslots that are configured for the VCTRUNK at the remotesite is different from that at the local site.(1) Check whether the sink and source VCTRUNKs are bound with the same number of

physical paths or bound with the same timeslots.


Maintenance Guide


Issue 04 (2010-10-30)

If... Then...

The sink and source VCTRUNKs arebound with the different number ofphysical paths or bound with thedifferent timeslots


The sink and source VCTRUNKs arebound with the same number of physicalpaths or bound with the same timeslots

Go to Cause 2.

Step 2 Cause 2: Some paths in the receive direction of the remote site are faulty.

(1) Check whether any path alarm exists in the receive direction of the remote site.

If... Then...


No alarm is reported Go to the next step.

Step 3 Cause 3: Some paths in the transmit direction of the local site are faulty.

(1) Replace the board that reports the alarm.

----End

Related Information

None.

A.2.74 LCAS_TLCR

Description

The LCAS_TLCR is an alarm indicating that all the LCAS bandwidth in the receive directionis lost. This alarm occurs when no path in the receive direction of the VCTRUNK with LCASenabled carries the overload but paths are configured to carry the overload.

Attribute


Major Service alarm

Parameters




A-127

Name Meaning




The Ethernet service is interrupted.


remote site is different from that at the local site.l Cause 2: Some paths in the transmit direction of the remote site are faulty.l Cause 3: Some paths in the receive direction of the local site are faulty.

Procedure

Step 1 Cause 1: The number of paths or timeslots that are configured for the VCTRUNK at the remotesite is different from that at the local site.(1) Check whether the VCTRUNKs at both ends are configured with the same number of

physical paths and timeslots.

If... Then...

The VCTRUNKs at both ends areconfigured with a different number ofphysical paths and timeslots


The VCTRUNKs at both ends areconfigured with the same number ofphysical paths and timeslots

Go to Cause 2.

Step 2 Cause 2: Some paths in the transmit direction of the remote site are faulty.(1) Check whether any path alarm exists in the transmit direction of the remote site.

If... Then...


No alarm is reported Go to Cause 3.

Step 3 Cause 3: Some paths in the receive direction of the local site are faulty.(1) Replace the board that reports the alarm.

----End

Related Information

None.


Maintenance Guide


Issue 04 (2010-10-30)

A.2.75 LCAS_TLCT

Description

The LCAS_TLCT is an alarm indicating that all the LCAS bandwidth in the transmit directionis lost. This alarm occurs when no path in the transmit direction of the VCTRUNK with LCASenabled carries the overload but paths are configured to carry the overload.

Attribute


Major Service alarm

Parameters


Name Meaning




The Ethernet service is interrupted.


remote site is different from that at the local site.

l Cause 2: Some paths in the receive direction of the remote site are faulty.

l Cause 3: Some paths in the transmit direction of the local site are faulty.

Procedure

Step 1 Cause 1: The number of paths or timeslots that are configured for the VCTRUNK at the remotesite is different from that at the local site.

(1) Check whether the sink and source VCTRUNKs are bound with the same number ofphysical paths or bound with the same timeslots.



A-129

If... Then...

The sink and source VCTRUNKs arebound with a different number ofphysical paths or bound with differenttimeslots


The sink and source VCTRUNKs arebound with the same number of physicalpaths or bound with the same timeslots

Go to Cause 2.

Step 2 Cause 2: Some paths in the receive direction of the remote site are faulty.

(1) Check whether any path alarm exists in the receive direction of the remote site.

If... Then...


No alarm is reported Go to the next step.

Step 3 Cause 3: Some paths in the transmit direction of the local site are faulty.


----End

Related Information

None.

A.2.76 LCS_LIMITED

Description

The LCS_LIMITED is an alarm indicating that the capacity of the microwave servicesconfigured for an NE crosses the limit specified in the license file.

Attribute



Parameters



Maintenance Guide


Issue 04 (2010-10-30)

Name Meaning

Parameter 0 Indicates the type of the license alarm.

l 0x01 indicate the service capacity exceeds the license limit.l 0x02 indicate the AM license is not loaded.l 0x03 indicate that in the IF protection group, the licensed bandwidth on the

protection port is lower than the licensed bandwidth on the working port.


Changing the capacity of the microwave services through an NE does not take effect.

Possible Causes

The capacity of the configured microwave services crosses the limit defined in the license file.

Procedure

Step 1 The capacity of the configured microwave services crosses the limit defined in the license file.

(1) Check whether the change in the capacity of the microwave services meet the requirementof the NE.

If... Then...

The change in the capacity of themicrowave services meet therequirement of the NE


The change in the capacity of themicrowave services does not meet therequirement of the NE

Delete the unauthorized microwave cross-connection.

(2) Check whether the service capacity complies with the latest authorization agreement. Fordetails, see 7.8 Querying the License Capacity.

If... Then...

The service capacity complies with thelatest authorization agreement


The service capacity does not comply withthe latest authorization agreement

Contact Huawei engineers to load a newlicense file.

(3) Contact the local office of Huawei to apply for a license authorization of greater servicecapacity.

----End

Related Information

The microwave service capacity of an NE is calculated based on the cross-connections on theIF board.



A-131

A.2.77 LFA

Description

The LFA is an alarm indicating that the E1 frame alignment at the local end of the inversemultiplexing for E1 virtual concatenation group in the receive direction is lost.

Attribute



Parameters


Name Meaning

Parameter 1 Indicates the ID of the optical interface. The value is always 0x01.

Parameter 2, Parameter 3 Indicates the path ID.

Parameter 4, Parameter 5 Reserved. The values are always 0xff.

Impact on the Systeml When this alarm occurs, the E1 link that reports the alarm is unavailable, and the available

links in the E1 virtual concatenation group are reduced.l If the VCTRUNK link binds only one member, the service is interrupted when the LFA

alarm occurs.l After this alarm clears, the E1 link in the E1 virtual concatenation group will be recovered

automatically.

Possible Causes

The possible causes of the LFA alarm are as follows:

l Cause 1: The demultiplexing module of the E1 frame cannot perform the frame alignmentfunction, and therefore the frame alignment loss alarms are reported. These alarms includeTU_LOP, TU_AIS, and alarm indicating that the cross-connection is not configured.

l Cause 2: A certain board is faulty.

Procedure

Step 1 Cause 1: Check for the TU_LOP and TU_AIS alarms on the NMS. If these alarms occur, handlethese alarms first.


Maintenance Guide


Issue 04 (2010-10-30)

Step 2 Cause 2: A certain board is faulty.(1) Check whether the HARD_BAD alarm occurs on the board.(2) If the alarm occurs, perform a cold reset on the board that reports the hardware failure

alarm, and check whether the alarm clears.

CAUTIONIf the service on the board is not protected, a cold reset on the board causes serviceinterruptions.

(3) If the alarm persists, replace the board. For details, see 6.6 Replacing the Ethernet ServiceProcessing Board.

----End

Related InformationBasic frame

As defined in ITU-T G.704, a basic frame is an even frame with frame alignment sequence (FAS)or an odd frame with non frame alignment sequence (NFAS).

A.2.78 LICENSE_LOST

DescriptionThe LICENSE_LOST is an alarm indicating that the license file is not detected.

Attribute


Major alarm Equipment alarm


Name Meaning

Parameter 0 Indicates the type of the license.l 0x01: AM Licensel 0x02: Hybrid Licensel 0x03: TDM License



A-133

Impact on the SystemIf no microwave service is configured, the microwave services with a default capacity of 4xE1are configured. If microwave services are configured, there is no impact on the system exceptthat an alarm is reported.

Possible CausesThe license file is lost or not loaded.

Procedure

Step 1 Contact the technical support engineers of Huawei to reload the associated license file.

----End

Related InformationThe microwave service capacity of an NE is calculated based on the cross-connections on theIF board.

A.2.79 LICENSE_ERR

DescriptionThe LICENSE_ERR is an alarm indicating that license verification of an NE fails.

Attribute





Maintenance Guide


Issue 04 (2010-10-30)

Name Meaning

Parameter 1 Indicates the cause of verification failure.

l 0x01: Indicates that the license file is illegal.l 0x02: Indicates that the license file is incorrect in file format.l 0x03: Indicates that the characteristic segment (signature) verification fails.l 0x04: Indicates that the equipment serial number specified in the

characteristic segment does not match the equipment.l 0x05: Indicates that the trial usage of the characteristic segment expires.l 0x06: Indicates that the characteristic segment is incorrect in format.l 0x07: Indicates that the characteristic segment expires.


If no microwave service is configured, the microwave services with a default capacity of 4xE1are configured. If microwave services are configured, there is no impact on the system exceptthat an alarm is reported.

Possible Causes

Cause 1: The verification of the license file fails.

Procedure

Step 1 Cause 1: The verification of the license file fails.

(1) Contact Huawei engineers to load a new license file.

----End

Related Information

The microwave service capacity of an NE is calculated based on the cross-connections on theIF board.

A.2.80 LINK_ERR

Description

The LINK_ERR is an alarm indicating that the data link fails.

Attribute





A-135


Name Meaning

Parameter 1 Indicates the ID of the optical interface. For example, 0x01indicates that the alarm is reported by optical interface 1 of thecorresponding board.

Parameter 2, Parameter 3 Indicate the ID of the path that reports the alarm. 0x00 0x01 indicatethat the alarm is reported by path 1.

Impact on the SystemThe services carried over the path are interrupted.

Possible Causesl Cause 1: The optical fiber connected to the Ethernet optical interface is faulty.l Cause 2: The working modes of the ports at both ends are different.l Cause 3: The equipment at the local end or the remote end is faulty.

Procedure

Step 1 Cause 1: The optical fiber connected to the Ethernet optical interface is faulty.(1) Check whether the optical fiber connected to the Ethernet optical interface is faulty.

If... Then...

The optical fiber connected to the Ethernet opticalinterface is faulty

Replace the optical fiber.

The optical fiber connected to the Ethernet opticalinterface is not faulty

Go to Cause 2.

Step 2 Cause 2: The working modes of the ports at both ends are different.(1) Check whether the working modes of the ports at both ends are different.

If... Then...

The working modes of the ports at bothends are different

Set the working modes of the ports to thesame.

The working modes of the ports at bothends are the same


Step 3 Cause 3: The equipment at the local end or the remote end is faulty.(1) Use an optical fiber to perform a loopback at the port that reports the alarm. For details,

see 7.1 Hardware Loopback.


Maintenance Guide


Issue 04 (2010-10-30)

If... Then...

The alarm clears Replace the Ethernet board at the remote end.

The alarm persists Replace the Ethernet board at the local end.

----End

Related Information

None.

A.2.81 LMFA

Description

The LMFA is an alarm indicating the E1 multiframe alignment is lost when the E1 frame is aCRC-4 multiframe.

Attribute



Parameters


Name Meaning


Parameter 2, Parameter 3 Indicates the path ID.



When the alarm occurs, services are not affected.

Possible Causes

The possible cause of the LMFA alarm is as follows:




A-137

Procedure

Step 1 Cause 1: A certain board is faulty.

(1) Check whether the HARD_BAD alarm occurs on the board.

(2) If the alarm occurs, perform a cold reset on the board that reports the hardware failurealarm, and check whether the alarm clears.

CAUTIONIf the service on the board is not protected, a cold reset on the board causes serviceinterruptions.

(3) If the alarm persists, replace the alarmed board. For details, see 6.6 Replacing the EthernetService Processing Board.

----End

Related Information

Basic frame

As defined in ITU-T G.704, a basic frame is an even frame with frame alignment sequence (FAS)or an odd frame with non frame alignment sequence (NFAS).

Multiframe

A multiframe is composed of eight basic frames, and can implement cyclic redundancy check(CRC).

A.2.82 LOOP_ALM

Description

The LOOP_ALM is an alarm indicating that a loopback event occurs.

Attribute



Parameters



Maintenance Guide


Issue 04 (2010-10-30)

Name Meaning



Parameter 4 Indicates the type of loopback.

l 0x00: Indicates optical/electrical port inloop.l 0x01: Indicates optical/electrical port outloop.l 0x02: Indicates path inloop.l 0x03: Indicates path outloop.l 0x04: Indicates loopback on the user side.l 0x05: Indicates loopback on the combination wave side.l 0x06: Indicates SPI inloop.l 0x07: Indicates SPI outloop.l 0x08: Indicates ATM layer inloop.l 0x09: Indicates ATM layer outloop.l 0x0A: Indicates PHY layer inloop.l 0x0B: Indicates PHY layer outloop.l 0x0C: Indicates MAC layer inloop.l 0x0D: Indicates MAC layer outloop.l 0x0E: Indicates VC-4 timeslot inloop.l 0x0F: Indicates VC-4 timeslot outloop.l 0x10: Indicates VC-3 timeslot inloop.l 0x11: Indicates VC-3 timeslot outloop.l 0x12: Indicates VC-12 timeslot inloop.l 0x13: Indicates VC-12 timeslot outloop.l 0x14: Indicates IF outloop.l 0x15: Indicates IF inloop.l 0x16: Indicates RF inloop.l 0xFF: Indicates any of the preceding loopback modes.

Impact on the SystemThe loopback port or path fails to transmit services.

Possible CausesLoopback is performed at the local site.



A-139

Procedure

Step 1 Cause: Loopback is performed at the local site.

(1) Determine the type of loopback based on the alarm parameters.

(2) Find out the cause of loopback, and set the loopback status of the port that reports the alarmto Non-Loopback.

For more information about the loopback operation, see 7.5 Software loopback.

----End

Related Information

None.

A.2.83 LP_CROSSTR

Description

The LP_CROSSTR is an alarm indicating that a lower order path performance indicator crossesthe related threshold. This alarm occurs when a board detects that a lower order path bit errorperformance indicator crosses the preset threshold.

Attribute


Minor Service alarm

Parameters


Name Meaning






Maintenance Guide


Issue 04 (2010-10-30)


The services contain a large amount of bit errors and the services may be interrupted.

Possible Causes

Lower order path bit error performance events cross the preset threshold.

Procedure

Step 1 Cause: The lower order path error crosses the preset threshold.

(1) Check the threshold crossing records to find out the performance event that the lower orderpath error crosses the preset threshold. For details, see 7.3.8 Browsing the PerformanceEvent Threshold-Crossing Records.

Step 2 Handle the threshold-crossing performance event.

----End

Related Information

None.

A.2.84 LP_R_FIFO

Description

The LP_R_FIFO is an alarm indicating that the FIFO overflows on the reception side of thelower order path.

Attribute



Parameters

None.


Bit errors occur in the services.

Possible Causesl Cause 1: The clocks on both sites are not synchronous.




A-141

Procedure

Step 1 Cause 1: The clocks on both sites are not synchronous.

(1) Query whether a TU pointer adaptation performance event is reported at both ends. Fordetails, see 7.3.6 Browsing Current Performance Events.

If... Then...

A TU pointer adaptation performanceevent is reported

Handle the performance event. For details,see C.2.3 TUPJCHIGH, TUPJCLOW,and TUPJCNEW.

A TU pointer adaptation performanceevent is not reported

Go to Cause 2.



----End

Related Information

None.

A.2.85 LP_RDI

Description

The LP_RDI is an alarm indicating a remote defect in the lower order path. This alarm occurswhen the board detects that bit 8 of byte V5 is 1.

Attribute



Parameters


Name Meaning




Maintenance Guide


Issue 04 (2010-10-30)


The service at the local site is not affected. The service received by the opposite site, however,is interrupted.

Possible Causes

Cause 1: The local site detects the message that is returned by the opposite site and indicates thelower order path remote receive failure.

Procedure

Step 1 Cause 1: The local site detects the message that is returned by the opposite site and indicates thelower order path remote receive failure.

(1) Handle the alarm of the lower order path at the remote site.

----End

Related Information

None.

A.2.86 LP_RDI_VC12

Description

The LP_RDI_VC12 is an alarm indicating that data reception fails at the remote end of VC-12path. This alarm occurs when the board detects that bit 8 of byte V5 is 1.

Attribute



Parameters


Name Meaning


Parameter 2, Parameter 3 Indicate the ID of the VC-12 path that reports the alarm. Forexample, 0x00 0x01 indicate that the alarm is reported by VC-12path 1.



A-143



Possible Causes

Cause 1: The local site receives a message from the remote site, and the message says that datareception fails at the remote end of a lower order path.

Procedure

Step 1 Cause 1: The local site receives a message from the remote site, and the message says that datareception fails at the remote end of a lower order path.


----End

Related Information

None.

A.2.87 LP_RDI_VC3

Description

The LP_RDI_VC3 is an alarm indicating that data reception at the remote end of a VC-3 pathfails. This alarm occurs when the board detects that bit 5 of byte G1 is 1.

Attribute



Parameters


Name Meaning




Maintenance Guide


Issue 04 (2010-10-30)



Possible Causes

The local site receives a message from the remote site, and the message says that data receptionfails at the remote end of a lower order path.

Procedure

Step 1 Cause: The local site detects the message that is returned by the opposite site and indicates thehigher order path remote receive failure.


----End

Related Information

None.

A.2.88 LP_REI

Description

The LP_REI is an alarm indicating that there are bit errors over the lower order path of the remotesite. This alarm occurs when the board detects that bit 3 of byte V5 is 1.

Attribute



Parameters


Name Meaning





A-145


The local site is not affected, but there are bit errors in the received signals of the remote site.

Possible Causes

Cause: The local site receives a message from the remote site, and the message says that thereare bit errors in the lower order path of the remote site.

Procedure

Step 1 Cause: The local site receives a message from the remote site, and the message says that thereare bit errors in the lower order path of the remote site.

(1) Handle the LPBBE performance event of the remote site.

----End

Related Information

None.

A.2.89 LP_REI_VC12

Description

The LP_REI_VC12 is an alarm indicating that there are bit errors at the remote end of a VC-12lower order path. This alarm occurs when a board detects that bit 3 of byte V5 is 1.

Attribute



Parameters


Name Meaning




Maintenance Guide


Issue 04 (2010-10-30)

Impact on the SystemBit errors exist in the service in the receive direction of the remote site.

Possible CausesCause: The local site receives a message from the remote site, and the message says that thereare bit errors in the lower order path.

Procedure

Step 1 Cause: The local site receives a message from the remote site, and the message says that thereare bit errors in the lower order path.(1) Handle the LPBBE performance event of the remote site.

----End


A.2.90 LP_REI_VC3

DescriptionThe LP_REI_VC3 is an alarm indicating that there are bit errors at the remote end of a VC-3path. This alarm occurs when a board detects that any one of bits 1-4 of byte G1 is 1.

Attribute




Name Meaning



Impact on the SystemBit errors exist in the service in the receive direction of the remote site.



A-147

Possible Causes

Cause 1: The local site receives a message from the remote site, and the message says that thereare bit errors at the remote end of a lower order path.

Procedure

Step 1 Cause 1: The local site receives a message from the remote site, and the message says that thereare bit errors at the remote end of a lower order path.

(1) Handle the VC3BBE performance event of the remote site.

----End

Related Information

None.

A.2.91 LP_RFI

Description

The LP_RFI is an alarm indicating that the remote end of the lower order path fails. This alarmoccurs when a board detects that bit 4 of byte V5 is 1.

Attribute



Parameters


Name Meaning




The local site is not affected. The lower order path at the remote site, however, cannot bearservices.


Maintenance Guide


Issue 04 (2010-10-30)

Possible Causes

Cause 1: The local site detects the message that is returned by the opposite site and indicates thelower order path remote receive failure.

Procedure

Step 1 Cause 1: The local site detects the message that is returned by the opposite site and indicates thelower order path remote receive failure.


----End

Related Information

None.

A.2.92 LP_SIZE_ERR

Description

The LP_SIZE_ERR is an alarm indicating that the size of the TU pointer is incorrect.

Attribute


Minor Service alarm

Parameters

None.


The services carried by the alarmed board are interrupted.

Possible 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 are the samewith the service types supported by the board. For details, see Querying TDM Services.



A-149

If... Then...

The service types are different Change the configuration data.

The service types are the same Go to Cause 2.

Step 2 Cause 2: The tributary board is faulty.(1) Replace the board that reports the alarm.

----End


A.2.93 LP_SLM

DescriptionThe 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




Name Meaning



Impact on the SystemThe services in the lower order path are unavailable.

Possible CausesCause 1: The signal label contained in the V5 byte that is received by the local site does notmatch the signal label contained in the V5 byte that is transmitted by the remote site.


Maintenance Guide


Issue 04 (2010-10-30)

Procedure

Step 1 Cause 1: The signal label contained in the V5 byte that is received by the local site does notmatch the signal label contained in the V5 byte that is transmitted by the remote site.(1) Modify the signal label contained in the V5 byte that is to be received by the local site or

is to be transmitted by the remote site. Ensure that the signal labels at both ends match eachother. For details, see Configuring VC-12 POHs.

----End


A.2.94 LP_SLM_VC12

DescriptionThe LP_SLM_VC12 is an alarm indicating that a mismatched signal label is detected in theVC-12 path. This alarm occurs when the board detects a signal label mismatch between the V5bytes.

Attribute




Name Meaning



Impact on the SystemThe service in this lower order path is unavailable.

Possible CausesThe signal label contained in the V5 byte that is received by the local site does not match thesignal label contained in the V5 byte that is transmitted by the remote site.



A-151

Procedure

Step 1 Cause: The signal label contained in the V5 byte that is received by the local site does not matchthe signal label contained in the V5 byte that is transmitted by the remote site.(1) Modify the signal label contained in the V5 byte that is to be received by the local site or

that is to be transmitted by the remote site. Ensure that the signal labels at both ends matcheach other. For details, see Configuring VC-12 POHs.

----End

Related Information

None.

A.2.95 LP_SLM_VC3

Description

The LP_SLM_VC3 is an alarm indicating that a mismatched signal label is detected in the VC-3path. This alarm occurs when the board detects a signal label mismatch between the C2 bytes.

Attribute



Parameters


Name Meaning




The services in the lower order path are unavailable.

Possible Causes

Cause 1: The signal label contained in the C2 byte that is received by the local site does notmatch the signal label contained in the C2 byte that is transmitted by the remote site.


Maintenance Guide


Issue 04 (2010-10-30)

Procedure

Step 1 Cause 1: The signal label contained in the C2 byte that is received by the local site does notmatch the signal label contained in the C2 byte that is transmitted by the remote site.(1) Modify the signal label contained in the C2 byte that is to be received by the local site or

that is to be transmitted by the remote site. Ensure that the signal labels at both ends matcheach other. For details, see Configuring VC-3 POHs.

----End


A.2.96 LP_T_FIFO

DescriptionThe LP_T_FIFO is an alarm indicating that the FIFO overflows on the transmission side of thelower order path.

Attribute




Name Meaning



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.



A-153

Procedure

Step 1 Cause 1: The frequency offset of the input signal is very large.(1) Use an SDH analyzer to check whether the frequency offset of the input signal is within

50 ppm.

If... Then...

The frequency offset is very large Troubleshoot the remote site.

The frequency offset is within 50 ppm Go to Cause 2.


----End


A.2.97 LP_TIM

DescriptionThe LP_TIM is an alarm indicating that a mismatched trace identifier is detected in the lowerorder path. This alarm occurs when the board detects a mismatch between the J2 bytes at bothends.

Attribute




Name Meaning





Maintenance Guide


Issue 04 (2010-10-30)

Possible Causesl Cause 1: The J2 byte to be received by the local site does not match the J2 byte to be

transmitted by the remote site.

l Cause 2: The data configuration at the intermediate nodes is incorrect.

Procedure

Step 1 Cause 1: The J2 byte to be received by the local site does not match the J2 byte to be transmittedby the remote site.

(1) Set the byte mode of the J2 byte to be received by the local site to the disabled mode.Alternatively, set the J2 byte to be received by the local site to match the J2 byte to betransmitted by the remote site. For details, see Configuring VC-12 POHs.

Step 2 Cause 2: The data configuration at the intermediate nodes is incorrect.

(1) Check whether the cross-connections of the intermediate nodes where the service travelsare configured correctly. If not, re-configure the cross-connections. For details, seeQuerying TDM Services.

----End

Related Information

None.

A.2.98 LP_TIM_VC12

Description

The LP_TIM_VC12 is an alarm indicating a mismatched trace identifier is detected in the VC-12path. This alarm occurs when the board detects a mismatch between the J2 bytes at both ends.

Attribute



Parameters


Name Meaning




A-155

Name Meaning

Parameter 2, Parameter 3 Indicate the ID of the VC-12 path that reports the alarm. Forexample, 0x00 0x01 indicate that the alarm is reported by VC-12path 1 of the corresponding board.


Possible Causesl Cause 1: The J2 byte to be received by the local site does not match the J2 byte to be

transmitted by the remote site.l Cause 2: The data configuration at the intermediate nodes is incorrect.

ProcedureStep 1 Cause 1: The J2 byte to be received by the local site does not match the J2 byte to be transmitted

by the remote site.(1) Set the byte mode of the J2 byte to be received by the local site to the disabled mode.

Alternatively, set the J2 byte to be received by the local site to match the J2 byte to betransmitted by the remote site. For details, see Configuring VC-12 POHs.

Step 2 Cause 2: The data configuration at the intermediate nodes is incorrect.(1) Check whether the cross-connections of the intermediate nodes where the service travels

are configured correctly. If not, re-configure the cross-connections. For details, seeQuerying TDM Services.

----End


A.2.99 LP_TIM_VC3

DescriptionThe LP_TIM_VC3 is an alarm indicating a mismatched trace identifier is detected in the VC-3path. This alarm occurs when the board detects the J1 byte mismatch.

Attribute





Maintenance Guide


Issue 04 (2010-10-30)


Name Meaning


Parameter 2, Parameter 3 Indicate the ID of the VC-3 path that reports the alarm. For example,0x00 0x01 indicate that the alarm is reported by VC-3 path 1 of thecorresponding board.


None.

Possible Causesl Cause 1: The receivable J1 byte at the local site does not match the J1 byte transmitted at

the opposite site.

l Cause 2: The data configuration at the intermediate nodes is incorrect.

Procedure

Step 1 Cause 1: The receivable J1 byte at the local site does not match the J1 byte transmitted at theopposite site.

(1) Set the byte mode of the J1 byte to be received by the local site to the disabled mode.Alternatively, set the J1 byte to be received by the local site to match the J1 byte to betransmitted by the remote site. For details, see Configuring VC-3 POHs.

Step 2 Cause 2: The data configuration at the intermediate nodes is incorrect.

(1) Check whether the cross-connections of the intermediate nodes where the service travelsare configured correctly. If not, re-configure the cross-connections. For details, seeQuerying TDM Services.

----End

Related Information

None.

A.2.100 LP_UNEQ

Description

The LP_UNEQ is an alarm indicating that the lower order path is unequipped. This alarm occurswhen the board detects that the V5 byte signal label is 0.



A-157

Attribute




Name Meaning



Impact on the SystemThe service in the path is unavailable. If the service is configured with protection, the protectionswitching is also triggered.

Possible CausesThe data configuration is incorrect.

l Cause 1: The tributary path at the local site is configured with services, but the tributarypath at the remote site is not configured with services.

l Cause 2: The cross-connection configuration at the intermediate nodes is incorrect.

Procedure

Step 1 Cause 1: The tributary path at the local site is configured with services, but the tributary path atthe remote site is not configured with services.(1) Check whether the tributary path at the remote site is configured with services. For details,

see Querying TDM Services.

If... Then...

The tributary path at the remote site is not configured withservices

Configure services.

The tributary path at the remote site is configured with services Go to Cause 2.

Step 2 Cause 2: The cross-connection configuration at the intermediate nodes is incorrect.(1) Check whether the cross-connection configuration at the intermediate nodes is correct. If

not, re-configure the cross-connections. For details, see Querying TDM Services.

----End


Maintenance Guide


Issue 04 (2010-10-30)


A.2.101 LP_UNEQ_VC12

DescriptionThe LP_UNEQ_VC12 is an alarm indicating that the VC-12 path is unequipped. This alarmoccurs when the board detects that the V5 byte signal label is 0.

Attribute




Name Meaning


Parameter 2, Parameter 3 Indicate the ID of the VC-12 path that reports the alarm. Forexample, 0x00 0x01 indicate that the alarm is reported by VC-12path 1 of the corresponding board.

Impact on the SystemThe service in the path is unavailable. If the service is configured with protection, the protectionswitching is also triggered.




Procedure





A-159

If... Then...


Configure services.


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. Ifnot, re-configure the cross-connections. For details, see Querying TDM Services.

----End

Related Information

None.

A.2.102 LP_UNEQ_VC3

Description

The LP_UNEQ_VC3 is an alarm indicating that the VC-3 path is unequipped. This alarm occurswhen the board detects that the C2 byte signal label is 0.

Attribute



Parameters


Name Meaning


Parameter 2, Parameter 3 Indicate the ID of the VC-3 path that reports the alarm. For example,0x00 0x01 indicate that the alarm is reported by VC-3 path 1 of thecorresponding board.


The service in the path is unavailable. If the service is configured with protection, the protectionswitching is also triggered.


Maintenance Guide


Issue 04 (2010-10-30)




Procedure



If... Then...


Configure services.


Step 2 Cause 2: The cross-connection configuration at the intermediate nodes is incorrect.(1) Check whether the cross-connection configuration at the intermediate nodes is correct. If

not, re-configure the cross-connections. For details, see Querying TDM Services.

----End


A.2.103 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






A-161

Name Meaning


Impact on the SystemThe system performs protection switching in single-ended mode.

Possible CausesCause 1: The linear MSP is configured incorrectly.

The LPS_UNI_BI_M alarm is generated only when the following conditions are met:

l The switching modes (single-ended or dual-ended) at the local and remote sites 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 Linear MSP.

----End


A.2.104 LPT_INEFFECT

DescriptionThe LPT_INEFFECT is an alarm indicating that the LPT function fails. This alarm occurs whenthe user configures the LPT function but the board does not support the LPT function.

Attribute





Maintenance Guide


Issue 04 (2010-10-30)


Name Meaning


Parameter 2, Parameter 3 Indicate the port ID.

The values are always 0x00 0x01.



The services are not affected. If the board hardware is of a very early version, the board softwareautomatically stops the state machine of the LPT protocol, but reserves the LPT configuration.

Possible Causes

Cause 1: The board hardware is of a very early version, and the user configures the LPT function.

Procedure

Step 1 Cause 1: The board hardware is of a very early version, and the user configures the LPT function.

(1) Check whether the LPT function is required.

If... Then...

The LPT function is required Replace the board with a board of a proper version.For details, see 6.6 Replacing the EthernetService Processing Board.

The LPT function is not required Delete the configuration of the LPT function. Fordetails, see Configuring LPT for Point-to-PointServices.

----End

Related Information

None.

A.2.105 LPT_RFI

Description

The LPT_RFI is an alarm indicating that the link state pass-through function fails at the remoteend. This alarm occurs when the link path through (LPT) function detects the failure of theremote port or the LPT service network.



A-163

Attribute




Name Meaning


Parameter 2, Parameter 3 Indicate the port ID.

The values are always 0x00 0x01.


Impact on the SystemDuring the data transmission, the link is unavailable and the services are interrupted when theLPT function detects the failure of the remote port or the service network. In addition, enablingthe link backup is triggered. If the backup link is available, the service can be restored on thebackup link.

Possible Causesl Cause 1: The remote port fails. For example, there are alarms such as ETH_LOS,

LINK_ERR, LSR_NO_FITED, or the remote port is disabled.l Cause 2: The LPT service network is faulty.

– The communication link is interrupted.– There are the bit error threshold-crossing alarms BIP_EXC and B3_EXC_VC3.– There are alarms such as TU_LOP, TU_AIS, VCAT_LOA, VCAT_LOM_VC12,

VCAT_LOM_VC3, LP_UNEQ_VC12, and LP_UNEQ_VC3.

Procedure

Step 1 Check the alarm on the NMS, determine the board that reports the alarm, and then determinethe ID of the port on the board according to Parameter 1.

Step 2 Cause 1: The remote port is faulty.(1) Check whether the corresponding opposite ports are enabled according to the ports

indicated by the parameter.


Maintenance Guide


Issue 04 (2010-10-30)

If... Then...

The opposite port is not enabled Enable the opposite port.

The opposite port is enabled Go to the next step.

(2) Check whether any link fault alarm occurs on the line board.

If... Then...

Any link fault alarm occurs Handle the link fault alarms first, especially the R_LOSand MW_LOF alarms.

No link fault alarm occurs Go to Cause 2.

Step 3 Cause 2: The LPT service network is faulty.

(1) Check whether the following alarms occur on the Ethernet boards of the MEPs at both ends.Then, handle the alarms.

l ETH_LOSl LINK_ERRl LSR_NO_FITEDl BIP_EXC and B3_EXC_VC3l TU_LOP, TU_AIS, VCAT_LOA, VCAT_LOM_VC12, VCAT_LOM_VC3,

LP_UNEQ_VC12, and LP_UNEQ_VC3

----End

Related Information

None.

A.2.106 LSR_NO_FITED

Description

The LSR_NO_FITED is an alarm indicating that the laser is not installed.

Attribute



Parameters




A-165

Name Meaning



The optical interface fails to carry services.

Possible Causes

Cause 1: The laser of the local site is not installed.

Procedure

Step 1 Cause 1: The laser of the local site is not installed.


(2) Find out why the laser is not installed, and contact Huawei engineers for the installation.

----End

Related Information

None.

A.2.107 LSR_WILL_DIE

Description

The LSR_WILL_DIE is an alarm indicating that the life of the laser is close to the end.

Attribute



Parameters



Maintenance Guide


Issue 04 (2010-10-30)

Name Meaning



The SFP optical module may not function reliably, and thus the services may be interrupted.

Possible Causes

The laser is aged.

Procedure

Step 1 Cause: The laser is aged.


(2) Contact Huawei engineers to replace the faulty SFP optical module with a new one of thesame type.

----End

Related Information

None.

A.2.108 LTI

Description

The LTI is an alarm indicating that the synchronization sources are lost. This alarm occurs whenall the synchronization sources for the NE are lost.

Attribute



Parameters




A-167

Name Meaning

Parameter 1 l 0x01: Indicates that all the synchronization sources of the system clock arelost.

l 0x02: Indicates that all the synchronization sources of the 2 MHz phase-locked source are lost.


The clock enters the free-run mode and loses synchronization with other NE clocks.

Possible 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.(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.

----End

Related Information

None.

A.2.109 MOD_TYPE_MISMATCH


Maintenance Guide


Issue 04 (2010-10-30)

Description

The MOD_TYPE_MISMATCH is an alarm indicating that a mismatched port module isdetected.

Attribute


Critical Maloperation

Parameters


Name Meaning

Parameter 1 Indicates the ID of the port that reports the alarm. For example, 0x01 indicatesthat the alarm is reported by port 1 of the corresponding board.


The service on the port is interrupted.

Possible Causes

The type specified by the customer for the SFP module is different from the actual module type.

Procedure

Step 1 Cause: The type specified by the customer for the SFP module is different from the actual moduletype.

(1) Determine the port that reports the alarm based on the alarm parameter.

(2) Check whether the configured type of the SFP module is the same as the type of the actualmodule.

If... Then...

The configured type of the SFP module isthe same as the type of the actual module

Contact Huawei engineers to install an SFPmodule of the correct type.

The configured type of the SFP module isdifferent from the type of the actualmodule

Change the configured type of the SFPmodule.

----End



A-169

Related Information

None.

A.2.110 MS_AIS

Description

The MS_AIS is an alarm indicating multiplex section alarms. This alarm occurs when a boarddetects that bits 6-8 of the K2 byte in three consecutive frames are 111.

Attribute



Parameters


Name Meaning




The service on the line port is interrupted. If the service is configured with protection, theprotection switching is also triggered.

Possible Causesl Cause 1: The transmit unit at the opposite site is faulty.


Procedure


(1) Replace the line board at the opposite site based on the type of the board that reports thealarm.


Maintenance Guide


Issue 04 (2010-10-30)

If... Then...

The line board reports the alarm Replace the optical-interface line board at theopposite site.

The line board reports the alarm Replace the electrical-interface line board at theopposite site.

The IF board reports the alarm Replace the IF board at the opposite site.

(2) Replace the board and then check whether the alarm clears.

If... Then...

The alarm clears after the board is replaced End the fault handling.

The alarm persists after the board is replaced Go to the next step.

(3) Replace the PXC board at the opposite site.

If... Then...

The alarm clears after the board is replaced End the fault handling.

The alarm persists after the board is replaced Go to Cause 2.

Step 2 Cause 2: The receive unit at the local site is faulty.(1) Replace the board that reports the alarm on the local end.

If... Then...

The SDH optical-interface line boardreports the alarm

Replace the SDH optical-interface lineboard.

The SDH electrical-interface line boardreports the alarm

Replace the SDH electrical-interface lineboard.

The IF board reports the alarm Replace the IF board that reports thealarm.

----End


A.2.111 MS_CROSSTR

DescriptionThe MS_CROSSTR alarm indicates that a performance indicator of the multiplex section crossesthe threshold. This alarm occurs when a board detects that the multiplex section bit errorperformance indicator crosses the preset threshold.



A-171

Attribute


Minor Service alarm

Parameters


Name Meaning




l The lower six bits of Parameter 4 and Parameter 5 indicate theID of the performance event.


A large number of errors occur in the service, and the service may be interrupted.

Possible Causes

Cause 1: A multiplex section bit error performance indicator crosses the preset threshold.

Procedure

Step 1 Cause 1: A multiplex section bit error performance indicator crosses the preset threshold.(1) Check the threshold crossing records of multiplex section bit error performance events to

find out the performance event that crosses the preset threshold. For details, see 7.3.8Browsing the Performance Event Threshold-Crossing Records.


----End

Related Information

None.

A.2.112 MS_RDI


Maintenance Guide


Issue 04 (2010-10-30)

DescriptionThe MS_RDI is an alarm indicating that data reception fails at the remote end of the multiplexsection. This alarm occurs when a board detects that bits 6-8 of the K2 byte are 110.

Attribute




Name Meaning



Impact on the SystemThe service at the local site is not affected. The service received by the opposite site, however,is interrupted.

Possible CausesThe local site receives a message from the opposite site, and the message indicates that datareception at the remote end of the multiplex section fails.

ProcedureStep 1 The local site receives a message from the opposite site, and the message indicates that data

reception at the remote end of the multiplex section fails.(1) Rectify the fault that occurs on the regenerator section and the multiplex section at the

opposite site.

The possible alarms are as follows:

l MS_AISl R_LOSl R_LOFl B2_EXCl B2_SD

----End



A-173

Related Information

None.

A.2.113 MS_REI

Description

The MS_REI is an alarm indicating that bit errors occur on the remote end of the multiplexsection. This alarm occurs when the board detects that the M1 byte is not zero.

Attribute


Warning Service alarm

Parameters


Name Meaning




The service at the local site is not affected. The service received by the opposite site, however,has errors.

Possible Causes

Cause 1: The local site receives a message from the opposite site, and the message indicates thatbit errors occur on the remote end of the multiplex section.

Procedure

Step 1 Cause 1: The local site receives a message from the opposite site, and the message indicates thatbit errors occur on the remote end of the multiplex section.(1) Handle the MS_BBE performance event on the port of the opposite site.

----End


Maintenance Guide


Issue 04 (2010-10-30)


A.2.114 MSAD_CROSSTR

DescriptionThe MSAD_CROSSTR alarm indicates that the adaptation performance indicator of themultiplex section crosses the threshold. This alarm occurs when a board detects that an AUpointer adaptation performance indicator crosses the preset threshold.

Attribute


Minor Service alarm


Name Meaning




l The lower six bits of Parameter 4 and Parameter 5 indicate theID of a performance event.– 0x2a: AUPJCHIGH– 0x2b: AUPJCLOW– 0x2c: AUPJCNEW– 0xff: not used

Impact on the SystemBit errors may occur in the service.

Possible CausesAn AU pointer adaptation performance indicator crosses the preset threshold.



A-175

Procedure

Step 1 Cause: An AU pointer adaptation performance indicator crosses the preset threshold.(1) Check the threshold crossing records of the AU pointer adaptation performance events to

find out the performance event that crosses the preset threshold. For details, see 7.3.8Browsing the Performance Event Threshold-Crossing Records.


----End


A.2.115 MSSW_DIFFERENT

DescriptionThe MSSW_DIFFERENT is an alarm indicating that the master and slave software areasmismatches with each other. This alarm occurs 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




Name Meaning

Parameter 1 Indicates the location of the file.l 0x01: Indicates the files in the flash memoryl 0x02: Indicates the software that is currently running


Maintenance Guide


Issue 04 (2010-10-30)

Name Meaning

Parameter 2, Parameter 3 Indicate the IDs of the inconsistent files on the system controlboard.l 0x01: FPGA of the system control board in ofs1l 0x02: FPGA of the system control board in ofs2l 0x03: ofs1/hwx/nesoft.hwxl 0x04: ofs2/hwx/nesoft.hwxl 0x05: ofs1/hwx/ne.inil 0x06: ofs2/hwx/ne.inil 0x07: ofs1/hwx/ocp.inil 0x08: ofs2/hwx/ocp.inil 0x09: ofs1/fpga/if1_002.pgal 0x0a: ofs2/fpga/if1_002.pgal 0x0b: ofs1/fpga/if1_250.pgal 0x0c: ofs2/fpga/if1_250.pgal 0x0d: ofs1/fpga/sl1d.pgal 0x0e: ofs2/fpga/sl1d.pgal 0x0f: ofs1/fpga/sl91ifu2.pgal 0x10: ofs2/fpga/sl91ifu2.pgal 0x11: ofs1/fpga/sl91ifx2.pgal 0x12: ofs2/fpga/sl91ifx2.pgal 0x13: ofs1/fpga/sl91aux.pgal 0x14: ofs2/fpga/sl91aux.pgal 0x15: ofs1/hwx/lusoft.hwxl 0x16: ofs2/hwx/lusoft.hwxl 0x17: ofs1/hwx/lusoft.inil 0x18: ofs2/hwx/lusoft.inil 0x19: ofs1/fpga/sl91em6t.pgal 0x1a: ofs2/fpga/sl91em6t.pgal 0x1b: ofs1/fpga/pvg610.pgal 0x1c: ofs2/fpga/pvg610.pgal 0x1d: ofs1/fpga/pvg610x.pgal 0x1e: ofs2/fpga/pvg610x.pga



A-177

Name Meaning

Parameter 4, Parameter 5 Indicate the cause of the alarm.l 0x04: The file versions in the master and slave areas of a single

system control board are inconsistent.l 0x08: The file versions in the active and standby system control

boards are inconsistent, or that the files in the 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 onthe active and standby system control boards are alsoinconsistent.

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: An exception occurs during the software loading.

ProcedureStep 1 Cause 1: An exception occurs during the software loading.

(1) Contact Huawei engineers to re-load the software.

----End


A.2.116 MULTI_RPL_OWNER

DescriptionThe MULTI_RPL_OWNER is an alarm indicating that the ring network contains severalRPL_OWNER nodes.

Attribute





Maintenance Guide


Issue 04 (2010-10-30)


Name Meaning

Parameter 1 Indicates the port ID.

Parameter 2, Parameter 3 Indicate the ID of the ERPS instance.


The ERPS protection fails.

Possible Causes

The associated data is configured incorrectly.

Procedure

Step 1 Cause: The associated data is configured incorrectly.(1) Reconfigure the ERPS protection. For details, see Creating ERPS Instances.

----End

Related Information

None.

A.2.117 MW_BER_EXC

Description

The MW_BER_EXC is an alarm indicating that there are excessive bit errors on the radio link.This alarm occurs when the bit errors on the radio link exceed the specified threshold (10-3 bydefault).

Attribute


Minor Service alarm

Parameters




A-179

Name Meaning




The services on the port are interrupted.

Possible Causesl Cause 1: Signal attenuation on the radio link is too heavy.

l Cause 2: The transmit unit at the opposite site is faulty.


Procedure

Step 1 Cause 1: Signal attenuation on the radio link is too heavy.

(1) Check whether the MW_FEC_UNCOR alarm is reported. If so, clear the alarm.


(1) Replace the IF board at the local site.


(1) Replace the IF board at the opposite site.

----End

Related Information

None.

A.2.118 MW_BER_SD

Description

The MW_BER_SD is an alarm indicating that signal deteriorates on the radio link. This alarmoccurs when the bit errors on the radio link exceed the specified threshold (10-6 by default) butdoes not reach the MW_BER_EXC alarm threshold (10-3 by default).

Attribute


Minor Service alarm


Maintenance Guide


Issue 04 (2010-10-30)


Name Meaning



Impact on the SystemThe service performance on the port deteriorates. If the equipment is configured with 1+1 FD/SD protection, HSM channel switching may be triggered.

Possible Causesl Cause 1: Signal attenuation on the radio link is too heavy.l Cause 2: The transmit unit of the opposite site is faulty.l Cause 3: The receive unit of the local site is faulty.

Procedure

Step 1 Cause 1: Signal attenuation on the radio link is too heavy.(1) Check whether the MW_FEC_UNCOR alarm is reported. If so, clear the alarm.

Step 2 Cause 2: The receive unit at the local site is faulty.(1) Replace the IF board at the local site.

Step 3 Cause 3: The transmit unit at the opposite site is faulty.(1) Replace the IF board at the opposite site.

----End


A.2.119 MW_FEC_UNCOR

DescriptionThe MW_FEC_UNCOR alarm indicates that microwave frames forward error correction (FEC)encoding cannot be corrected.



A-181

Attribute


Minor Service alarm


Name Meaning

Parameter 1 Indicates the ID of the IF port that reports the alarm. For example, 0x01 indicatesthat the alarm is reported by port 1 of the corresponding board.

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.l Cause 2: The transmit unit of the opposite site is faulty.l Cause 3: The receive unit of the local site is faulty.l Cause 4: An interference event occurs.

Procedure

Step 1 Cause 1: The receive power of the ODU is abnormal.(1) Check whether the receive power of the ODU at the local site is normal. If yes, determine

the abnormality and take proper measures. For details, see Querying History TransmitPower and Receive Power.


Maintenance Guide


Issue 04 (2010-10-30)

If... Then...

The RSL is lower than the receiversensitivity

Follow the steps:

1. Check the installation of the antenna to ensurethat the azimuth angle 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.

The RSL is higher than the specifiedRSL of the network. The offset value istens of decibles. The duration is fromtens of seconds 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, seeConfiguring the IF/ODUInformation of a Radio Link.

b. Check the RSL at the local end. For details,seeConfiguring the IF/ODU Informationof a Radio Link. If the RSL exceeds -90dBm, you can infer 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.



A-183

If... Then...

The RSL is lower than the specified RSLof the network. The offset value is tens ofdecibles. 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 to makethe 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.

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 in the 1+1 SD configuration,adjust the height offset between two antennasto make the receive power of one antennamuch stronger than the receive power of theother antenna.

l Increase the fading margin.

Step 2 Cause 2: The transmit unit of the opposite site is faulty.

Locate the fault by looping back the opposite site and excluding the position one by one. Followthe steps:

(1) Perform an inloop on the IF port at the opposite end. For details, see 7.5.4 Setting Loopbackfor the IF Board. Check whether the fault at the opposite end is rectified after the loopback.

If... Then...

The alarm persists Replace the IF board.

The alarm clears Go to the next step.

(2) Check whether the cable connector workmanship meets the requirement. If any cableconnector does not meet the requirement, make a new connector.

(3) Check whether the IF cable is soggy, broken, or pressed. Replace the cable that does notmeet the requirement.

(4) Then, check whether the alarm clears.

If... Then...

The alarm persists Replace the ODU at the opposite site.


Maintenance Guide


Issue 04 (2010-10-30)

If... Then...


Step 3 Cause 3: The receive unit of the local site is faulty.

Locate the fault by looping back the opposite site and excluding the position one by one. Followthe steps:

(1) Perform an inloop on the IF port at the local end. For details, see 7.5.4 Setting Loopbackfor the IF Board. Check whether the fault at the opposite end is rectified after the loopback.

If... Then...



(2) Check whether the cable connector workmanship meets the requirement. If any cableconnector does not meet the requirement, make a new connector.

(3) Check whether the IF cable is soggy, broken, or pressed. Replace the cable that does notmeet the requirement.

(4) Then, check whether the alarm clears.

If... Then...

The alarm persists Replace the ODU of the local site.


Step 4 Cause 4: An interference event occurs.

(1) Check whether any co-channel interference occurs.

a. Mute the opposite ODU.

b. Check the RSL at the local end. For details, see Configuring the IF/ODU Informationof a Radio Link. If the RSL exceeds -90 dBm, you can infer 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 opposite ODU.

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. Fordetails, 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 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.



A-185

(4) Contact the spectrum management department to clear the interference spectrum or changeplans to minimize the interference.

----End


A.2.120 MW_LIM

DescriptionThe MW_LIM is an alarm indicating that a mismatched radio link identifier is detected. Thisalarm occurs when the IF board detects that the link ID in the microwave frame overheads isinconsistent with the specified link ID.

Attribute




Name Meaning


Impact on the SystemAfter reporting the MW_LIM alarm, the IF board inserts the AIS alarm to the received signals.Then, the services on the radio link are interrupted. If the services are configured with SNCP,the protection switching may be triggered.

Possible Causesl Cause 1: The link ID of the local site does not match the link ID of the opposite site.l Cause 2: The services on other radio links are received due to the incorrect configuration

of the radio link receive frequency at the local or opposite site.l Cause 3: The antenna receives microwave signals from the other site, because the direction

of the antenna is set incorrectly.l Cause 4: The polarization direction of the XPIC is configured incorrectly.


Maintenance Guide


Issue 04 (2010-10-30)

ProcedureStep 1 Determine the IF port that reports the alarm based on the alarm parameters.

Step 2 Cause 1: The link ID of the local site does not match the link ID of the opposite site.(1) Check whether the link ID of the local site matches with the link ID of the opposite site.

For details, see Configuring the IF/ODU Information of a Radio Link. If not, set the linkIDs at both ends to the same according to the network planning.

Step 3 Cause 2: The services on other radio links are received due to the incorrect configuration of theradio link receive frequency at the local or opposite site.(1) Check whether the receive and transmit frequencies of the local site are consistent with the

receive and transmit frequencies of the opposite site. For details, see Configuring the IF/ODU Information of a Radio Link. If not, set the receive and transmit frequencies of thetwo sites again according to the network planning.

Step 4 Cause 3: The antenna receives microwave signals from the other sites, because the direction ofthe antenna is set incorrectly.(1) Adjust the direction of the antenna and ensure that the antennas at both ends are aligned.

Step 5 Cause 4: The polarization direction of the XPIC is configured incorrectly.(1) If XPIC protection groups are configured, check whether the XPIC configuration is correct.

For details, see Creating an XPIC Workgroup.a. Check whether the settings of IFX boards in polarization direction-V and

polarization direction-H meet the requirement of the network planning.

If... Then...

No Delete the XPIC workgroups that are configured incorrectly and create XPICworkgroups again.

Yes Go to the next step.

b. Check whether Link ID-V and Link ID-H meet the requirement of the networkplanning.

If... Then...

No Reset the ID of the radio link of the IFXboard according to the network planning.For details, see Creating XPICWorkgroups.

The link ID meets the requirement ofthe network planning


(2) Check and modify the IFX board and ODU, and the mapping relation between the ODUand the antenna feed. Ensure that the IFX boards in the polarization direction V of bothends are interconnected to each other through the radio link in the polarization direction V,and the IFX boards in the polarization direction H of both ends are interconnected to eachother 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



A-187

is a random value. In this case, the link ID is invalid. The MW_LIM alarm is also suppressedby the MW_LOF alarm.

A.2.121 MW_LOF

DescriptionThe MW_LOF is an alarm indicating that the Reed Solomon (RS) frame is lost.

Attribute




Name Meaning


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 site and the

opposite site are different. In the case of Hybrid radio services, the channel bandwidth andmodulation modes at the local site and the opposite site are different.

l Cause 3: The working frequency of the ODU at the local site is inconsistent with theworking frequency of the ODU at the opposite site.

l Cause 4: The transmit unit of the opposite site is faulty.l Cause 5: The receive unit of the local site is faulty.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.


Maintenance Guide


Issue 04 (2010-10-30)

(1) Check whether any alarms are generated in the equipment at the local site. If yes, takepriority to clear them.The relevant alarms are as follows:l HARD_BADl VOLT_LOSl IF_CABLE_OPENl BD_STATUSl RADIO_RSL_LOWl CONFIG_NOSUPPORTl TEMP_ALARM

Step 2 Cause 2: In the case of TDM radio services, the IF working modes at the local site and theopposite site are different. In the case of Hybrid radio services, the channel bandwidth andmodulation modes at the local site and the opposite site are different.(1) In the case of TDM radio services, check whether the working mode of the IF board at the

local site is consistent with the working mode of the IF board at the opposite site. For details,see Configuring the IF/ODU Information of a Radio Link. If not, reset the working modeof 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 Setting the Hybrid/AM Attribute.

Step 3 Cause 3: The working frequency of the ODU at the local site is inconsistent with the workingfrequency of the ODU at the opposite site.(1) Ensure that the type of the ODU at the local site is consistent with the type of the ODU at

the opposite site.(2) Reset the working frequency of the ODU according to the network planning. For details,

see Setting Parameters of ODU Interfaces.Set the value of the transmit frequency of the local site the same as the value of the receivefrequency of the opposite site. Then, set the value of the receive frequency of the local sitethe same as the value of the transmit frequency of the opposite site.

Step 4 Cause 4: The transmit unit of the opposite site is faulty.(1) Check whether any alarms are generated in the equipment of the local site. If yes, take

priority to clear them.The relevant alarms are as follows:l HARD_BADl BD_STATUSl VOLT_LOSl IF_CABLE_OPENl RADIO_MUTEl RADIO_TSL_HIGHl RADIO_TSL_LOWl TEMP_ALARM

(2) Locate the fault by looping back the opposite site.

Follow the steps:



A-189

a. Perform an inloop on the IF port at the opposite end. For details, see 7.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 workmanship meets the requirement. If any cableconnector does not meet the requirement, make a new connector.

c. Check whether the IF cable is soggy, broken, or pressed. Replace the cable that doesnot meet the requirement.

d. Then, check whether the alarm clears.

Step 5 Cause 5: The receive unit of the local site is faulty.(1) Locate the fault by looping back the opposite site.

Follow the steps:

a. Perform an inloop on the IF port at the local end. For details, see 7.5.4 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 workmanship meets the requirement. If any cableconnector does not meet the requirement, make a new connector.

c. Check whether the IF cable is soggy, broken, or pressed. Replace the cable that doesnot meet the requirement.

d. Then, check whether the alarm clears.

Step 6 Cause 6: The receive power of the ODU is abnormal.(1) Check whether the receive power of the ODU at the local site is abnormal. If yes, determine

the abnormality and take proper measures. For details, see 7.3.7 Browsing the HistoryPerformance.


Maintenance Guide


Issue 04 (2010-10-30)

If... Then...

The RSL is lower than the receiversensitivity

Follow the steps:

1. Check the installation of the antenna to ensurethat the azimuth angle 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.

The RSL is higher than the specifiedRSL of the network. The offset value istens of decibles. The duration is fromtens of seconds 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 Informationof a Radio Link. If the RSL exceeds -90dBm, you can infer 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.



A-191

If... Then...

The RSL is lower than the specified RSLof the network. The offset value is tens ofdecibles. 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 to makethe 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.

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 in the 1+1 SD configuration,adjust the height offset between two antennasto make the receive power of one antennamuch 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 opposite ODU.b. Check the RSL at the local end. For details, see Configuring the IF/ODU Information

of a Radio Link. If the RSL exceeds -90 dBm, you can infer that there is co-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 opposite ODU.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.


Maintenance Guide


Issue 04 (2010-10-30)

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.2.122 MW_RDI

DescriptionThe MW_RDI alarm indicates that there are defects at the remote end of a radio link. This alarmoccurs when the IF board detects an RDI in the radio frame overheads.

Attribute




Name Meaning


Impact on the SystemIf the local site is configured with reverse switching, 1+1 switching on the IF board is triggeredwhen the working and protection boards receive the MW_RDI alarm at the same time. Thisalarm also indicates that the services received at the opposite site are interrupted.

Possible CausesAfter detecting a service alarm that is caused by the fault on a radio link, the receive end returnsa radio link fault indication to the transmit end.



A-193

Procedure

Step 1 Cause: After detecting a service alarm that is caused by the fault on a radio link, the receive endreturns a radio link fault indication to the transmit end.

(1) Clear the microwave alarms that occur at the opposite site. The possible alarms are asfollows:

l MW_LOF

l R_LOF

l R_LOC

----End

Related Information

None.

A.2.123 NESF_LOST

Description

The NESF_LOST is an alarm indicating that the NE software is lost. This alarm occurs whenthe system control, cross-connect, and timing board detects that the NE software in the flashmemory is lost.

Attribute



Parameters


Name Meaning

Parameter 1 Indicates the routine inspection object.

l 0x01: Indicates an ordinary filel 0x02: Indicates the version of the running softwarel 0x03: Indicates a special routine inspection object


Maintenance Guide


Issue 04 (2010-10-30)

Name Meaning

Parameter 2, Parameter 3 Indicate the ID of the routine inspection object.

l 0x01, 0x03, 0x05, and 0x07 indicate the scc.fpga, nesoft.hwx,ne.ini, and ocp.ini in the ofs1, respectively.

l 0x02, 0x04, 0x06, and 0x08 indicate the scc.fpga, nesoft.hwx,ne.ini, and ocp.ini in the ofs2, respectively.

Parameter 4 Alarm Cause

l If the first bit is 1, it indicates that the file does not exist.l If the second bit is 1, it indicates that verification of the file fails.l If the third bit is 1, it indicates that the version of the file in the

active area is different from the version of the file in the standbyarea.

l If the fourth bit is 1, it indicates that the version of the file of theactive board is different from the version of the file in thestandby board.


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 fails.

l Cause 3: The portable flash memory card is not in position or is faulty.

Procedure

Step 1 Cause 1: No new NE software is loaded after the existing NE software is erased.

Cause 2: Loading the NE software fails.

(1) Check whether the alarm is caused by the loading operation.

If... Then...

The alarm is caused by the loadingoperation

Contact the Huawei engineers to re-load thesoftware.

The alarm is not caused by the loadingoperation


Step 2 Cause 3: The portable flash memory card is not in position or is faulty.

(1) Re-install or replace the portable flash memory card.

----End



A-195


A.2.124 NESTATE_INSTALL

DescriptionThe NESTATE_INSTALL is an alarm indicating that the NE is in the install state.

Attribute



ParametersNone.

Impact on the SystemThe NE fails to work.

Possible Causesl Cause 1: The logical cross-connect board is not configured.l Cause 2: The NE database check fails.

Procedure

Step 1 Cause 1: The logical cross-connect board is not configured.(1) Check whether the logical cross-connect board is configured in the slot layout on the NMS.

For details, see Configuring Logical Boards.

Step 2 Cause 2: The NE database check fails.(1) Restore the data from the backup database.

----End


A.2.125 NO_BD_SOFT

DescriptionThe NO_BD_SOFT is an alarm indicating that the board software is lost.


Maintenance Guide


Issue 04 (2010-10-30)

Attribute



Parameters


Name Meaning


Parameter 2, Parameter 3 Indicate the type of the lost software.l 0x01: board softwarel 0x02: active FPGAl 0x03: standby FPGA

Impact on the Systeml If the board software is lost, the board fails to work normally.l If the FPGA is lost, the FPGA has no backup copy.

Possible Causes

Cause 1: Software loading fails to be performed correctly.

Procedure

Step 1 Cause 1: Software loading fails to be performed correctly.(1) Contact Huawei technical support engineers to re-load the software.

----End

Related Information

None.

A.2.126 NP1_MANUAL_STOP

Description

The NP1_MANUAL_STOP is an alarm indicating that the N+1 protection protocol is stoppedmanually.



A-197

Attribute




Name Meaning

Parameter 1, Parameter 2 Indicate the ID of the protection group that reports the alarm. Forexample, 0x01 indicates that the alarm is reported by protectiongroup 1.

Impact on the SystemN+1 protection may fail, or protection switching may fail.

Possible CausesCause 1: The N+1 protection protocol is stopped manually.

Procedure

Step 1 Cause 1: The N+1 protection protocol is stopped manually.(1) Start the N+1 protection protocol.

----End


A.2.127 NP1_SW_FAIL

DescriptionThe NP1_SW_FAIL is an alarm indicating that N+1 protection switching fails.

Attribute




Maintenance Guide


Issue 04 (2010-10-30)


Name Meaning

Parameter 1, Parameter 2 Indicate the ID of the protection group that reports the alarm. Forexample, 0x01 indicates that the alarm is reported by protectiongroup 1.

Impact on the SystemServices 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.

ProcedureStep 1 Cause 1: The parameters of the N+1 protection for the node that reports the alarm are set

incorrectly.(1) Check whether the parameters of the N+1 protection are set correctly based on the planning

information. For details, see Creating an N+1 Protection Group.

If... Then...

The parameters of the N+1 protection are setincorrectly

Set the parameters correctly.

The parameters of the N+1 protection are set correctly Go to Cause 2.

Step 2 Cause 2: The networkwide N+1 protection protocol runs abnormally.(1) Stop and restart the protocol manually. For details, see Starting/Stopping the N+1

Protection Protocol.

If... Then...

The alarm clears after the protocol isrestarted


The alarm persists after the protocol isrestarted

Contact Huawei technical supportengineers to handle the alarm.

----End




A-199

A.2.128 NP1_SW_INDI

Description

The NP1_SW_INDI is an alarm indicating N+1 protection switching. When the N+1 protectionswitching is successful, the NP1_SW_INDI alarm is reported. When the switching status ischanged to the idle status, the NP1_SW_INDI alarm clears.

Attribute



Parameters


Name Meaning



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.

When the services are switched from the working path to the protection path, the extra servicesin the protection path are interrupted. When the services are switched back to the working path,the extra services in the protection path continue to be transmitted.

Possible Causes

Cause: The N+1 protection switching is performed.

Procedure

Step 1 Cause: The N+1 protection switching is performed.

(1) Find out the cause of switching and take proper measures.

l Possible external switching operations: forced switching and manual switching

l Possible causes for automatic switching: fault in the hardware of the ODU or the IFboard, MW_LOF, R_LOC, R_LOF, R_LOS, MS_AIS, and B2_EXC alarm


Maintenance Guide


Issue 04 (2010-10-30)

If... Then...

The switching is caused by externalswitching operations

Clear the external switching operation. Fordetails, see Performing IF N+1 ProtectionSwitching.

The switching is automatic switching Clear the alarm that triggers the automaticswitching.

----End

Related Information

None.

A.2.129 OPM_FAIL

Description

The OPM_FAIL is an alarm indicating that the system fails to launch optical power.

Attribute



Parameters


Name Meaning



The services at the optical interface that reports the alarm are interrupted.

Possible Causes

Cause 1: The SFP optical module is faulty.



A-201

Procedure

Step 1 Cause 1: The SFP optical module is faulty.


(2) Contact Huawei technical support engineers to replace the faulty SFP optical module witha new one of the same type.

----End

Related Information

None.

A.2.130 P_AIS

Description

The P_AIS is an alarm indication at a PDH interface. This alarm occurs when the tributary boarddetects that uplink PDH signals are all 1s.

Attribute



Parameters


Name Meaning




The signals at a specific PDH interface are unavailable.

Possible Causesl Cause 1: The opposite PDH equipment transmits the AIS signal.

l Cause 2: The receive unit of the tributary board on the local equipment is faulty.


Maintenance Guide


Issue 04 (2010-10-30)

Procedure

Step 1 Check whether the opposite equipment transmits the AIS signal.

If... Then...

The opposite equipment transmits the AISsignal

Rectify the fault on the opposite equipment.

The opposite equipment does not transmitthe AIS signal


Step 2 Replace the board that reports the alarm.

----End

Related Information

None.

A.2.131 P_LOS

Description

The P_LOS is an alarm indicating that signals at a PDH interface are lost.

Attribute



Parameters


Name Meaning




PDH services are interrupted.



A-203

Possible Causesl Cause 1: The port does not access PDH services.l Cause 2: The opposite equipment is faulty.l Cause 3: The trunk cable is faulty.l Cause 4: The board that reports the alarm is faulty.

Procedure

Step 1 Cause 1: The port does not access PDH services.(1) Check whether the port accesses PDH services.

If... Then...

The port does not access PDH services Enable the port to access PDH services ordelete unnecessary services.

The port accesses PDH services Go to Cause 2.

Step 2 Cause 2: The opposite equipment is faulty.(1) Check whether the opposite equipment is faulty.

If... Then...


The equipment functions normally Go to Cause 3.

Step 3 Cause 3: The trunk cable is faulty.(1) Check whether the trunk cable is broken or cut.

If... Then...

The trunk cable is broken or cut Rectify the corresponding fault.

The trunk cable is in normal status Go to Cause 4.

Step 4 Cause 4: The board that reports the alarm is faulty.(1) Replace the board that reports the alarm.

----End


A.2.132 PROT_CONN_ERR

DescriptionThe PROT_CONN_ERR is an alarm indicating that an exception occurs in the connection ofthe protection pair. This alarm is reported when the system detects any of the followingconditions: A cross-connection or incorrect connection exists between the protection pair


Maintenance Guide


Issue 04 (2010-10-30)

configured on the EMS6/EFP6 board and the IFH2 board, or the connection between theprotection pair configured on the EMS6/EFP6 board and the IFH2 board is incorrect.

Attribute


Major Service alarm


Name Meaning

Parameter 1 Indicates the ID of the optical interface that reports the alarm.

Parameter 2 Indicates the type of incorrect connection.l 0x00: loss of the protection group connectionl 0x01: protection group mismatchl 0x02: disabled protection group

Parameter 3, Parameter 4 Indicate the information about the opposite site.l When the value of Parameter 2 is 0x00, the values of Parameter

3 and Parameter 4 are 0x00 0x00.l When the value of Parameter 2 is 0x01:

Parameter 3 indicates the slot ID of the board that does not matchthe protection group.Parameter 4 indicates the ID of the port that does not match theprotection group.

l When the value of Parameter 2 is 0x02:Parameter 3 indicates the slot ID of the connected board.Parameter 4 indicates the ID of the port that is connected to theport that reports the alarm.

Impact on the SystemThe services that travel through the protection group are unavailable or the protection functionfails.

Possible Causesl Cause 1: The connection between the local protection group and the opposite protection

group (IFH2) fails.l Cause 2: The opposite ports connected to the ports of the local protection group are not in

the same protection group or are non-protection ports.



A-205

l Cause 3: The non-protection ports at the local site are connected to the protection ports ofthe opposite site (IFH2).

Procedure

Step 1 Handle the alarm based on the value of Parameter 2.

If... Then...

The value of Parameter 2 is 0x00 See Step 2.

The value of Parameter 2 is 0x01 See Step 3 or Step 4.

The value of Parameter 2 is 0x02 Enable the ports of the local protection group.

Step 2 Cause 1: The connection between the local protection group and the opposite protection group(IFH2) is faulty.(1) Check whether the network cables connecting the port that reports the alarm and the two

IFH2 boards of the IF 1+1 protection are incorrectly connected or faulty.

If... Then...

The network cables are loose or not connected Connect the network cables properly.

The network cables are faulty Replace the network cables.

Step 3 Cause 2: The opposite ports connected to the ports of the local protection group are not in thesame protection group or are non-protection ports.(1) Check whether the IFH2 board connected to the port that reports the alarm is in the mapping

IF 1+1 protection group.

If... Then...

The opposite ports are not in the sameprotection group

Connect the ports that are in the sameprotection group.

The opposite ports are non-protectionports

Enable the ports of the opposite protectiongroup.

Step 4 Cause 3: The non-protection Ethernet ports at the local site are connected to the protection portsof the opposite site (IFH2).(1) Check whether the Ethernet ports at the local site are in the protection group. If not,

configure these Ethernet ports into LAGs. For details, see Creating a LAG.

----End


A.2.133 PORT_MODULE_OFFLINE

DescriptionThe PORT_MODULE_OFFLINE is an alarm indicating that a port is off line.


Maintenance Guide


Issue 04 (2010-10-30)

Attribute



Parameters


Name Meaning




The services at the port that reports the alarm are interrupted.

Possible Causes

The port is enabled, but the SFP module is not installed.

Procedure

Step 1 Cause: The port is enabled, but the SFP module is not installed.

(1) Check whether the port needs to access services.

If... Then...

The port needs to access services Go to the next step.

The port need not access services Disable the port.

(2) Check whether the SFP module is installed.

If... Then...

The SFP module is not installed Contact Huawei technical support engineers to installthe required SFP module.

The SFP module is installed Go to the next step.

(3) Re-install the SFP module.

If... Then...

The alarm clears The fault is rectified. End the alarm handling.



A-207

If... Then...

The alarm persists Contact Huawei technical support engineers to replace the faultySFP module.

----End

Related Information

None.

A.2.134 POWER_ALM

Description

The POWER_ALM is a power module alarm indication.

Attribute



Parameters


Name Meaning

Parameter 1 Indicates 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.

Parameter 2 l 0x01: under-voltagel 0x02: over-voltage


The power module is under protection. Therefore, if only one power module reports thePOWER_ALM alarm, the system is not affected.

Possible Causesl Cause 1: The accessed power is abnormal.

l Cause 2: The power module is abnormal.


Maintenance Guide


Issue 04 (2010-10-30)

Procedure

Step 1 Cause 1: The accessed power is abnormal.

(1) Use a multimeter to test the power voltage supplied to the chassis.

If... Then...

The voltage is beyond the range of -38.4 V to -72 V Clear the alarm immediately.

The voltage is within the range of -38.4 V to -72 V Go to Cause 2.

Step 2 Cause 2: The power module is abnormal.

(1) Check whether the IDU is properly grounded.


----End

Related Information

l In the case of the IDU 620, the power modules on the two PXC boards provide 1+1 powersupply backup for the system.

l In the case of the IDU 620, the power modules on the two FAN boards provide 1+1 powersupply backup for the fan.

A.2.135 PS

Description

The PS is a protection switching alarm indication.

Attribute



Parameters


Name Meaning

Parameter 1 The value is always 1.

Parameter 2, Parameter 3 Indicate the ID of the path that reports the alarm. For example, 0x01indicates that the alarm is reported in path 1.



A-209


During the switching (less than 50 ms), services are interrupted. After the switching, the servicesare restored to normal.

Possible Causes

Cause: Protection switching occurs in the services.

Procedure

Step 1 Cause: Protection switching occurs in the services.

(1) Find out the cause of the switching.

(2) Cancel the manual switching command if it is carried out.

(3) Browse current alarms, and check whether the path where the switching occurs reportsalarms. If yes, handle the alarms.

----End

Related Information

None.

A.2.136 R_F_RST

Description

The R_F_RST is an alarm indicating that the receive FIFO is reset.

Attribute



Parameters


Name Meaning




Maintenance Guide


Issue 04 (2010-10-30)

Impact on the SystemServices are interrupted.

Possible Causesl Cause 1: The clocks at both sites are not synchronous.l Cause 2: A certain board is faulty.

Procedure

Step 1 Cause 1: The clocks at both sites are not synchronous.(1) Check whether a TU pointer justification performance event is reported at both sites. For

details, see 7.3.6 Browsing Current Performance Events.

If... Then...

A TU pointer justification performanceevent is reported

Handle the performance event. For details,see C.2.3 TUPJCHIGH, TUPJCLOW,and TUPJCNEW.

No TU pointer justificationperformance event is reported

Go to Cause 2.

Step 2 Cause 2: A certain board is faulty.(1) Replace the board that reports the alarm.

----End


A.2.137 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 the clock signal from the line signal or the IF boardfails to extract the clock signal from the IF signal.

Attribute






A-211


Name Meaning


Parameter 2, Parameter 3 Indicate the ID of the path.

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 at the local site is faulty.l Cause 2: The transmit unit at the opposite site is faulty.

Procedure

Step 1 Cause 1: The receive unit at the local site is faulty.(1) At the local site, perform an inloop on the port of the board that reports the alarm. For

details, see 7.5 Software loopback.

If... Then...

The alarm persists after the loopback Replace the board that reports the alarm atthe local site.

The alarm clears after the loopback Go to Cause 2.


If... Then...




Replace the PXC board of the local site.

Step 2 Cause 2: The transmit unit at the opposite site is faulty.(1) Replace the board of the opposite site.

If... Then...




Replace the PXC board of the oppositesite.

----End


Maintenance Guide


Issue 04 (2010-10-30)


A.2.138 R_LOF

DescriptionThe R_LOF is an alarm indicating that frames are lost on the receive side. This alarm is reportedwhen the OOF state lasts for 3 ms.

Attribute




Name Meaning


Parameter 2, Parameter 3 Indicate the ID of the path.

Impact on the SystemServices are interrupted. If the system is configured with protection, protection switching maybe triggered.

Possible Causesl Cause 1: Certain other alarms occur (if the alarm is reported by an IF board).l Cause 2: The line performance declines (if the alarm is reported by an SDH optical or

electrical line board).l Cause 3: The transmit unit of the opposite site is faulty.l Cause 4: The receive unit of the local site is faulty.

Procedure

Step 1 Based on the alarm parameters, determine the line port that reports the alarm.

Step 2 Cause 1: Certain high-level alarms occur (if the alarm is reported by an IF board).



A-213

(1) Check whether the MW_FEC_UNCOR alarm is reported if the alarm is reported by an IFboard.

If... Then...

The MW_FEC_UNCOR alarm isreported

Handle the MW_FEC_UNCOR alarmimmediately.

The MW_FEC_UNCOR alarm is notreported


(2) Perform an inloop on the IF port that reports the alarm.

If... Then...

The alarm clears after the inloop isperformed

Clear the alarm according to the solutionfor the alarm that is reported when thetransmit unit of the opposite site is faulty.

The alarm persists after the inloop isperformed

Clear the alarm according to the solutionfor the alarm that is reported when thereceive unit of the local site is faulty.

Step 3 Cause 2: The line performance declines (if the alarm is reported by an SDH optical or electricalline board).(1) Exchange the receive/transmit fiber jumpers or cables at the receive and transmit ends.

If... Then...

The alarm persists after the exchange Clear the alarm according to the solution forthe alarm that is reported when the transmitunit of the opposite site is faulty.

The line port of the opposite site reportsthe R_LOF alarm

Rectify the fault on fibers or cables.

Step 4 Cause 3: The transmit unit of the opposite site is faulty.(1) Replace the line board (SDH optical/electrical line board or IF board) of the opposite site.

For details, see 6 Part Replacement.

If... Then...






If... Then...




Clear the alarm according to the solution forthe alarm that is reported when the receiveunit of the local site is faulty.


Maintenance Guide


Issue 04 (2010-10-30)

Step 5 Cause 4: The receive unit of the local site is faulty.(1) Replace the board that reports the alarm. For details, see 6 Part Replacement.

----End


A.2.139 R_LOS

DescriptionIn the case of SDH line boards, the R_LOS is an alarm indicating that the signals on the receiveline side are lost. In the case of IF boards, the R_LOS is an alarm indicating that the microwaveframes on the receive line side are lost.

Attribute




Name Meaning


Parameter 2, Parameter 3 Indicate the ID of the path. For example, 0x00 0x01 indicate thatthe alarm is reported in path 1.

Impact on the SystemServices are interrupted. If the system is configured with protection, protection switching maybe triggered.

Possible Causesl Cause 1: Certain other alarms occur (if the alarm is reported by an IF board).l Cause 2: The line performance declines (if the alarm is reported by an SDH optical or

electrical line board).l Cause 3: The transmit unit of the opposite site is faulty.



A-215

l Cause 4: The receive unit of the local site is faulty.

Procedure

Step 1 Based on the alarm parameter, determine the line port that reports the alarm.

Step 2 Cause 1: Certain high-level alarms occur (if the alarm is reported by an IF board).

(1) Check whether the MW_FEC_UNCOR alarm is reported if the alarm is reported by an IFboard.

If... Then...

The MW_FEC_UNCOR alarm isreported

Handle the MW_FEC_UNCOR alarmimmediately.

The MW_FEC_UNCOR alarm is notreported


(2) Perform an inloop on the IF port that reports the alarm.

If... Then...

The alarm clears after the inloop isperformed

Clear the alarm according to the solutionfor the alarm that is reported when thetransmit unit of the opposite site is faulty.

The alarm persists after the inloop isperformed

Clear the alarm according to the solutionfor the alarm that is reported when thereceive unit of the local site is faulty.

Step 3 Cause 2: The line performance declines (if the alarm is reported by an SDH optical or electricalline board).

(1) Exchange the receive/transmit fiber jumpers or cables at the receive and transmit ends.

If... Then...

The alarm persists after the exchange Clear the alarm according to the solution forthe alarm that is reported when the transmitunit of the opposite site is faulty.

The line port of the opposite site reportsthe R_LOF alarm

Rectify the fault on fibers or cables.

Step 4 Cause 3: The transmit unit of the opposite site is faulty.

(1) Replace the line board (SDH optical/electrical line board or IF board) of the opposite site.For details, see 6 Part Replacement.

If... Then...







Maintenance Guide


Issue 04 (2010-10-30)

If... Then...




Clear the alarm according to the solution forthe alarm that is reported when the receiveunit of the local site is faulty.

Step 5 Cause 4: The receive unit of the local site is faulty.(1) Replace the board that reports the alarm. For details, see 6 Part Replacement.

----End


A.2.140 R_S_ERR

DescriptionThe R_S_ERR is an alarm indicating that the received signal has errors.

Attribute




Name Meaning



Impact on the SystemServices are interrupted.

Possible Causesl Cause 1: The frequency offset of the received signal is large.



A-217


Procedure

Step 1 Cause 1: The frequency offset of the received signal is large.(1) Check whether the tributary board supports the type of the received signal.

If... Then...

The tributary board does not supportthe type of the received signal

Change the type of the signal transmittedfrom the opposite site.

The tributary board supports the type ofthe received signal


(2) Test the frequency offset of the received signal.

If... Then...

The frequency offset is large Troubleshoot the opposite site.

The frequency offset meets the requirement Go to Cause 2.


----End


A.2.141 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 plus 14 dB).

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 clears.

Attribute





Maintenance Guide


Issue 04 (2010-10-30)


Name Meaning




Impact on the SystemIf the MW_LOF or MW_FEC_UNCOR alarm is not generated, services are not affected.

Possible Causesl Cause 1: The ODU fault at the transmit end causes abnormal transmit power.l Cause 2: The direction of the antenna is deflected.l Cause 3: Transmission environment changes.l Cause 4: The fading margin in the case of rain and fog in the network planning is

insufficient.

Procedure

Step 1 Cause 1: The ODU fault at the transmit end causes abnormal transmit power.(1) Check whether the ODU at the transmit end reports the RADIO_TSL_LOW alarm.

If... Then...

The ODU at the transmit end reports theRADIO_TSL_LOW alarm

Handle the RADIO_TSL_LOW alarm.

The ODU at the opposite 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.

The direction of the antenna is not deflected Go to Cause 3.

Step 3 Cause 3: Transmission environment changes.(1) Check whether the transmission environment changes. For example, check whether any

building blocks the transmission and increases the link fading significantly.

If... Then...

The transmission environment changes Contact the network planning department forreplanning the transmission trail.



A-219

If... Then...

The transmission environment does notchange

Go to Cause 4.

Step 4 Cause 4: The fading margin in the case of rain and fog in the network planning is insufficient.(1) If the alarm is reported frequently, contact the network planning department for increasing

the fading margin by replanning the transmission trail.

----End

Related Information

None.

A.2.142 RADIO_MUTE

Description

The RADIO_MUTE is an alarm indicating that the radio transmitter is muted.

Attribute


Warning Equipment alarm

Parameters


Name Meaning

Parameter 1 Indicates the RF port that reports the alarm.


The transmitter does not transmit services.

Possible Causesl Cause 1: Certain other alarms occur.l Cause 2: The transmitter of the local site is muted manually.l Cause 3: The IF board is faulty, causing abnormal IF output.l Cause 4: The data output is abnormal because the ODU is faulty.


Maintenance Guide


Issue 04 (2010-10-30)

Procedure

Step 1 Cause 1: Certain other alarms occur.

(1) Check whether the CONFIG_NOSUPPORT or IF_INPWR_ABN alarm is generated. Ifyes, clear the alarm immediately.

Step 2 Cause 2: The transmitter of the local site is muted manually.

(1) Check whether the transmitter of the ODU is muted. For details, see Configuring the IF/ODU Information of a Radio Link. If yes, unmute the ODU. Then, enable the ODU totransmit signals.

Step 3 Cause 3: The IF board is faulty, causing abnormal IF output.

(1) Replace the IF board.

Step 4 Cause 4: The data output is abnormal because the ODU is faulty.

(1) 6.12 Replacing an ODU.

----End

Related Information

The number of the logical slot for the ODU is the number of the slot for the IF board connectedto the ODU plus 10.

A.2.143 RADIO_RSL_BEYONDTH

Description

The RADIO_RSL_BEYONDTH is an alarm indicating that antennas are not aligned. When thereceivable power is set on an NE, the NE enables the antenna alignment indication functionautomatically. If the actual receive power of the ODU is lower than the preset receive powerminus 3 dB, the RADIO_RSL_BEYONDTH alarm is reported. Then, if the antennas are alignedfor continuous 30 minutes, the antenna alignment indication function is disabled automatically.Afterwards, the RADIO_RSL_BEYONDTH alarm is reported only when theRADIO_FADING_MARGIN_INSUFF alarm is reported.

Attribute



Parameters




A-221

Name Meaning




Impact on the SystemIf the MW_LOF or MW_FEC_UNCOR alarm is not generated, services are not affected.

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 clears, the RADIO_RSL_BEYONDTHalarm clears.

----End


A.2.144 RADIO_RSL_HIGH

DescriptionThe RADIO_RSL_HIGH is an alarm indicating that the radio receive power is high. This alarmis reported if the detected receive power is equal to or higher than the upper threshold of theODU (-20 dBm).

Attribute


Critical Service alarm



Maintenance Guide


Issue 04 (2010-10-30)


Name Meaning



Normal transmission of services is affected. If the system is configured with 1+1 protection,protection switching 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 high.

Procedure

Step 1 Cause 1: The local ODU is faulty.

(1) Replace the ODU.

Step 2 Cause 2: There is a strong interference source nearby.

(1) Check whether any nearby signal source transmits signals whose frequency is close to thespecified range. If yes, check whether the signal source can be closed or moved. If not,contact the network planning department for replanning the frequency.

Step 3 Cause 3: The transmit power of the opposite ODU is high.

(1) Reset the transmit power of the opposite ODU. For details, see Configuring the IF/ODUInformation of a Radio Link.

----End

Related Information

None.

A.2.145 RADIO_RSL_LOW

Description

The RADIO_RSL_LOW is an alarm indicating that the radio receive power is low. This alarmis reported if the detected receive power is equal to or lower than the lower threshold of the ODU(-90 dBm).



A-223

Attribute




Name Meaning


Impact on the SystemIf no MW_LOF or MW_FEC_UNCOR alarm is generated, services are not affected.

Possible Causesl Cause 1: Certain other alarms occur at the opposite site.l Cause 2: The transmit power of the opposite site is low.l Cause 3: The local ODU is faulty.l Cause 4: Signal attenuation on the radio link is heavy.

Procedure

Step 1 Cause 1: Certain other alarms occur at the opposite site.Check whether any of the following alarms is generated on the equipment of the opposite site.If yes, clear the alarm immediately.l RADIO_MUTEl CONFIG_NOSUPPORTl RADIO_TSL_LOWl BD_STATUS

Step 2 Cause 2: The transmit power of the opposite site is low.(1) Check whether the transmit power of the opposite site is normal. For details, see

Configuring the IF/ODU Information of a Radio Link. If the transmit power is abnormal,replace the ODU of the opposite site.

Step 3 Cause 3: The local ODU is faulty.(1) Replace the ODU of the local site.

Step 4 Cause 4: Signal attenuation on the radio link is heavy.(1) Browse history alarms, and check whether the RADIO_RSL_LOW alarm occurs

continuously.


Maintenance Guide


Issue 04 (2010-10-30)

If the alarm occurs occasionally, contact the network planning department to change thedesign to improve anti-fading performance.

(2) Check whether the antennas at both ends are aligned.

If the antennas are not aligned, align the antennas again.(3) Check whether any mountain or building obstacle exists in the transmit direction.

If yes, contact the network planning department for proper modification to the planningdesign, therefore avoiding the block of the mountain or building obstacle.

(4) Check whether the polarization direction of the antenna, ODU, and hybrid coupler at bothends is set correctly.

If not, correct the polarization direction.(5) Check whether the outdoor units such as the antenna, hybrid coupler, ODU, and flexible

waveguide are wet, damp, or damaged.

If yes, replace the unit that is wet, damp, or damaged. For details, see 6 PartReplacement.

(6) Check whether the antenna gain at both the transmit and receive ends meets the requirement.

If not, replace the antenna.

----End


A.2.146 RADIO_TSL_HIGH

DescriptionThe RADIO_TSL_HIGH is an alarm indicating that the radio transmit power is high. This alarmis reported if the detected transmit power is higher than the upper power threshold of the ODU.

Attribute




Name Meaning




A-225



Possible Causes

Cause 1: The ODU is faulty.

Procedure

Step 1 Cause 1: The ODU is faulty.(1) Replace the ODU.

----End

Related Information

None.

A.2.147 RADIO_TSL_LOW

Description

The RADIO_TSL_LOW is an alarm indicating that the radio transmit power is low. This alarmis reported if the detected transmit power is less than the lower power threshold of the ODU.

Attribute



Parameters


Name Meaning





Maintenance Guide


Issue 04 (2010-10-30)

Possible CausesCause 1: The ODU is faulty.

Procedure

Step 1 Cause 1: The ODU is faulty.(1) Replace the ODU.

----End


A.2.148 RELAY_ALARM

DescriptionThe RELAY_ALARM is an alarm indicating relay errors.

Attribute


Critical Environment alarm


Name Meaning

Parameter 1 Indicates the ID of the input alarm signal. For example, 0x01 indicates that thereported external alarm is from the first input alarm signal.


Possible CausesCause 1: There is an input alarm signal.

Procedure

Step 1 Cause 1: There is an input alarm signal.



A-227

(1) Based on the alarm parameter, determine the ID of the input alarm signal.(2) Rectify the fault according the meaning of the input alarm signal.

----End


A.2.149 RMFA

DescriptionThe RMFA is an alarm indicating the loss of multiframe alignment at the remote end. This alarmoccurs when the local end detects all 1s of the remote indication bits in Z consecutive CASmultiframes (Z = 1 to 5) of the framed E1/T1 input.

Attribute




Name Meaning




Impact on the SystemWhen the alarm occurs, the services at the local site are not affected. The alarm indicates thatthe LMFA alarm occurs at the opposite end.

Possible CausesThe LMFA alarm occurs at the opposite end.

ProcedureStep 1 Check whether the opposite end of the alarmed path reports the LMFA alarm. If yes, clear the

LMFA alarm. Then, the RMFA alarm at the local end clears.

----End


Maintenance Guide


Issue 04 (2010-10-30)


A.2.150 RP_LOC

DescriptionThe RP_LOC is an alarm indicating that the clock of the receive phase-locked loop is lost.

Attribute



ParametersNone.

Impact on the SystemThe services on the board are interrupted.

Possible Causesl Cause 1: The service configuration data is incorrect.l Cause 2: The board is faulty.

Procedure

Step 1 Cause 1: The service configuration data is incorrect.(1) Check whether the service is correctly configured.

If... Then...

The service is configured incorrectly Reconfigure the service.

The service is configured correctly Go to Cause 2.


----End


A.2.151 RPS_INDI



A-229

DescriptionThe RPS_INDI is a radio protection switching alarm indication.

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 services are not affected.

Possible Causesl The possible causes of the HSB protection switching are as follows:

– Cause 1: An external switching event occurs.– Cause 2: An automatic switching event occurs.– Cause 3: A reverse switching event occurs.

l Possible cause of the HSM protection switching: At the local site, the radio link in thereceive direction is faulty.

Procedure

Step 1 Determine the type of the protection switching based on the alarm parameter.

Step 2 Cause 1 of HSB switching: An external switching event occurs. That is, a command is issuedon the NMS to trigger the switching.(1) Check whether the switching is the forced switching or manual switching. For details, see

Querying the IF 1+1 Protection Status.


Maintenance Guide


Issue 04 (2010-10-30)

If... Then...

The switching is the forced switching ormanual switching

Find the cause and clear 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 Hardware fault on the IF board, or hardware fault on the ODUl POWER_ALM or VOLT_LOSl RADIO_TSL_HIGH, RADIO_TSL_LOW, or RADIO_RSL_HIGHl IF_INPWR_ABN or CONFIG_NOSUPPORTl R_LOC, R_LOF, R_LOS, or MW_LOF

NOTE

l If the switching is non-revertive, the services are not automatically switched back to the workingpath when the working path is restored to normal, and the RPS_INDI alarm persists. In this case,you need to manually switch the services from the protection path to the working path. TheRPS_INDI alarm clears only when the switching is successful.

l If the switching is revertive, the services are automatically switched back to the working pathwhen the specified wait-to-restore (WTR) time expires after the working path is restored tonormal. The RPS_INDI alarm clears only when the switching is successful.

Step 4 Cause 3 of HSB switching: A reverse switching event occurs.(1) Check whether the active and standby IF boards report the MW_RDI alarm. If yes, clear

the MW_RDI alarm immediately.

Step 5 Cause of the HSM switching: The radio link is faulty.(1) Check whether any alarm that triggers HSM switching is generated on the IF board in the

IF 1+1 protection group. If yes, clear the alarm immediately.HSM switching may be triggered by any of the following alarms:l R_LOC, R_LOF, R_LOS, or MW_LOFl MW_FEC_UNCORl B1_SD or B2_SD

----End


A.2.152 RS_CROSSTR

DescriptionThe RS_CROSSTR is an alarm indicating that the regenerator section performance indicatorcrosses the threshold. This alarm is reported if a board detects that the regenerator sectionperformance event crosses the preset threshold.



A-231

Attribute


Minor Service alarm

Parameters


Name Meaning






A large number of bit errors occur in services, and the services may be interrupted.

Possible Causes

Cause 1: The regenerator section bit error performance event crosses the preset threshold.

Procedure

Step 1 Cause 1: The regenerator section bit error performance event crosses the preset threshold.

(1) Find out the regenerator section bit error performance event that crosses the threshold. Fordetails, see 7.3.8 Browsing the Performance Event Threshold-Crossing Records.

(2) Handle the performance event that crosses the threshold.

----End

Related Information

None.

A.2.153 RTC_FAIL


Maintenance Guide


Issue 04 (2010-10-30)

DescriptionThe RTC_FAIL is an alarm indicating that the real-time clock (RTC) of the equipment fails.

Attribute



ParametersNone.


Possible Causesl Cause 1: The synchronization period on the NMS is long.l Cause 2: The RTC on the SCC board malfunctions.

Procedure

Step 1 Cause 1: The synchronization period on the NMS is long.(1) Modify the synchronization period on the NMS to one day. For details, see Synchronizing

NE Time.

Step 2 Cause 2: The RTC on the SCC board malfunctions.(1) Reset the SCC board.

If... Then...

The alarm clears after the board is reset Reset the NE clock and end the alarmhandling.

The alarm persists after the board isreset

Replace the SCC board.

----End


A.2.154 S1_SYN_CHANGE

DescriptionThe S1_SYN_CHANGE is an alarm indicating that the clock source is switched in S1 bytemode.



A-233

Attribute



Parameters


Name Meaning

Parameter 1 l 0x01: The system clock is switched.l 0x02: The 2M phase-locked loop is switched.


After the clock source is switched, the lower quality of the newly traced clock source causespointer justifications and some bit errors. As a result, the quality of services is affected.

Possible Causes

The original clock source is lost when the SSM protocol or extended SSM protocol is enabled.

Procedure

Step 1 Cause: The original clock source is lost when the SSM protocol or extended SSM protocol isenabled.

(1) Handle the SYNC_C_LOS alarm reported by the original clock source.

----End

Related Information

None.

A.2.155 SWDL_ACTIVATED_TIMEOUT

Description

The SWDL_ACTIVATED_TIMEOUT is an alarm indicating that the commit operation is notperformed during software package loading. During package loading, the system reports thealarm if the commit operation is not performed within 30 minutes after activation of the board.


Maintenance Guide


Issue 04 (2010-10-30)

Attribute



Parameters

None.


If an NE fails to perform the commit operation for a long period, the software in the two areasof the double-area boards is inconsistent.

Possible Causes

Certain radio links are faulty. As a result, the NE involved in the package loading fails to receivethe commit command.

Procedure

Step 1 Cause: Certain radio links are faulty. As a result, the NE involved in the package loading failsto receive the commit command.

(1) Check whether any radio link is faulty.

If... Then...

Certain radio links are faulty Rectify the faults on the radio links and ensure thatthe links between the nodes on which the softwarepackage is loaded are normal.

Radio links are normal Perform the package loading to the NE again.

----End

Related Information

None.

A.2.156 SWDL_AUTOMATCH_INH

Description

The 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 find out the mapping software from the software on the SCC board.



A-235

Attribute



Parameters

None.


When an NE is installed with a board whose software version is not consistent, and if the boardfails to find out the mapping software from the software on the SCC board, the software versionsof the entire NE are inconsistent. As a result, certain functions of the NE cannot run normally.

Possible Causes

The automatic match function is disabled.

Procedure

Step 1 Cause: The automatic match function is disabled.

(1) Contact Huawei technical support engineers for troubleshooting.

----End

Related Information

None.

A.2.157 SWDL_COMMIT_FAIL

Description

The SWDL_COMMIT_FAIL is an alarm indicating that the commit operation on an NE fails.This alarm is reported when the commit operation fails in the package diffusion.

Attribute



Parameters

None.


Maintenance Guide


Issue 04 (2010-10-30)

Impact on the SystemWhen the SWDL_COMMIT_FAIL alarm occurs, the software versions in the two areas of thedouble-area board are inconsistent.

Possible CausesCause 1: The loaded software package is incorrect.

Procedure

Step 1 Cause 1: The loaded software package is incorrect.(1) Check whether the loaded software package is correct.(2) Perform the package diffusion again for the NE that reports the SWDL_COMMIT_FAIL

alarm.

----End


A.2.158 SWDL_CHGMNG_NOMATCH

DescriptionThe SWDL_CHGMNG_NOMATCH is an alarm indicating that the board software version andthe version of the running software are inconsistent. This alarm is reported when the systemdetects that the software version of any online board is inconsistent with the version of therunning software after the SCC board is replaced.

Attribute



ParametersNone.

Impact on the SystemWhen the SWDL_CHGMNG_NOMATCH alarm is reported, certain functions of the NE maybe affected because the board software version is inconsistent with the version of the runningsoftware.

Possible CausesThe software package of the SCC board does not match the software version of the board afterthe SCC board is replaced. In this case, the SWDL_CHGMNG_NOMATCH alarm is reported.



A-237

Procedure

Step 1 Cause: The software package of the SCC board does not match the software version of the boardafter the SCC board is replaced. In this case, the SWDL_CHGMNG_NOMATCH alarm isreported.(1) Perform the package diffusion again for the NE that reports the

SWDL_CHGMNG_NOMATCH alarm.

----End


A.2.159 SWDL_INPROCESS

DescriptionThe SWDL_INPROCESS is an alarm indicating that the package diffusion is in process on theNE.

Attribute


Warning Processing alarm

ParametersNone.

Impact on the SystemWhen 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 CausesCause: The package diffusion is being performed on the NE.

Procedure

Step 1 Cause: The package diffusion is being performed on the NE.(1) The SWDL_INPROCESS alarm clears automatically after the loading or rollback is

complete. Hence, this alarm does not require handling.

----End



Maintenance Guide


Issue 04 (2010-10-30)

A.2.160 SWDL_NEPKGCHECK

DescriptionThe SWDL_NEPKGCHECK is an alarm indicating that a certain file of the package stored inthe flash memory of the NE is lost. During the routine inspection on the flash memory in thedouble areas of the SCC board, the NE software detects that a certain file of the package in onearea is missing or cannot be verified. If the corresponding file in the other area is normal, theNE software recovers the missing or faulty file with the normal one. This alarm is reported whenthe file is found missing and cannot be recovered at the end of the routine inspection. This alarmclears when the file is recovered in the next routine inspection.

Attribute



ParametersNone.

Impact on the SystemA certain file of the package is missing and the NE may malfunction.

Possible CausesCause 1: Certain files are missing and cannot be recovered.

Procedure

Step 1 Cause 1: Certain files are missing and cannot be recovered.(1) Ensure that the loaded software package is correct. Perform package diffusion again for

the NE that reports the SWDL_NEPKGCHECK alarm.

----End


A.2.161 SWDL_PKG_NOBDSOFT

DescriptionThe SWDL_PKG_NOBDSOFT is an alarm indicating that certain board software is missing inthe software package. This alarm is reported when the required software is missing in thesoftware package during the automatic match of the board.



A-239

Attribute



Parameters

None.


The board cannot perform automatic match, because the required board software is missing inthe software package. Therefore, the board software version is inconsistent with the NE softwareversion, and certain functions of the NE may be affected.

Possible Causes

Cause 1: Certain board software is not loaded during software package loading.

Procedure

Step 1 Cause 1: Certain board software is not loaded during software package loading.

(1) Add the required board software to the software package, Alternatively, perform softwarepackage loading again.

----End

Related Information

None.

A.2.162 SWDL_ROLLBACK_FAIL

Description

The SWDL_ROLLBACK_FAIL is an alarm indicating that an NE rollback fails. If a boardrollback fails when the NE rollback is being performed, this alarm is reported.

Attribute



Parameters

None.


Maintenance Guide


Issue 04 (2010-10-30)

Impact on the SystemThe board software version fails to match the NE software version, and therefore certainfunctions of the NE may be affected.

Possible CausesCause 1: Certain board software is not loaded during software package loading.

Procedure

Step 1 Cause 1: Certain board software is not loaded during software package loading.(1) Add the required board software to the software package. Alternatively, perform software

package loading again.

----End


A.2.163 SYN_BAD

DescriptionThe SYN_BAD is an alarm indicating that the quality of the synchronization source declines.

Attribute



ParametersNone.

Impact on the SystemThe NE clock fails to be locked.

Possible Causesl Cause 1: The quality of the synchronization source declines.l Cause 2: The cross-connect unit is faulty.

Procedure

Step 1 Cause 1: The quality of the synchronization source declines.(1) Take different measures based on the traced synchronization source.



A-241

If... Then...

The traced synchronization source is anexternal clock

Perform Steps Step 1.2 to Step 1.4.

The traced synchronization source is a lineclock

Replace the PXC board of theupstream NE.

(2) Check whether the configuration of the external clock is correct.

If... Then...

The configuration is incorrect Change the configuration data.

The configuration is correct Go to the next step.

(3) Check whether the opposite equipment that provides the clock source is faulty.

If... Then...


The equipment functions normally Go to the next step.

(4) Check whether the cable that is connected to the external clock source is in normal status.

If... Then...

The cable is not in normal status Replace the cable.

The cable is in normal status Go to Cause 2.

Step 2 Cause 2: The cross-connect unit is faulty.(1) Replace the PXC board.

----End


A.2.164 SYNC_C_LOS

DescriptionThe SYNC_C_LOS is an alarm indicating that the synchronization source is lost.

Attribute


Warning Equipment alarm



Maintenance Guide


Issue 04 (2010-10-30)


Name Meaning

Parameter 1, Parameter 2 Indicate one lost clock source.l If the line clock source is lost, the first parameter indicates the

slot ID of the clock source, and the second parameter indicatesthe port ID of the clock source.

l If the external clock source is lost, "0xf0, 1" indicate externalclock 1, and "0xf0, 2" indicate external clock 2.

Impact on the SystemThe performance of the NE clock declines, or even the NE clock enters the free-run mode.

Possible CausesThe clock source is lost.

ProcedureStep 1 Cause: The clock source is lost.

(1) Based on the alarm parameter, determine the lost clock source.(2) Based on the clock source priority table, determine the synchronization source

corresponding to the lost clock source.

If... Then...

The synchronization source is anexternal clock

Handle the EXT_SYNC_LOS alarm.

The synchronization source is a lineclock

Handle the alarm that occurs on the lineboard.

The synchronization source is an IFclock

Handle the alarm that occurs on the IF board.

The synchronization source is atributary clock

Handle the alarm that occurs on the tributaryboard.

----End


A.2.165 T_ALOS

DescriptionThe T_ALOS is an alarm indicating that analog signals are lost at the 2 Mbit/s interface.



A-243

Attribute



Parameters


Name Meaning




2 Mbit/s services are interrupted.

Possible Causesl Cause 1: The interface does not access 2 Mbit/s services.l Cause 2: The opposite equipment is faulty.l Cause 3: The trunk cable is faulty.l Cause 4: The board that reports the alarm is faulty.

Procedure

Step 1 Cause 1: The interface does not access 2 Mbit/s services.(1) Check whether the interface accesses 2 Mbit/s services.

If... Then...

The interface does not access services Enable the port to access services or deleteunnecessary services.

The interface accesses services Go to Cause 2.

Step 2 Cause 2: The opposite equipment is faulty.(1) Check whether the opposite equipment is faulty.

If... Then...


The equipment runs normally Go to Cause 3.


Maintenance Guide


Issue 04 (2010-10-30)

Step 3 Cause 3: The trunk cable is faulty.(1) Check whether the trunk cable is faulty.

If... Then...

The trunk cable is faulty Rectify the fault.

The trunk cable is in normal status Go to Cause 4.

Step 4 Cause 4: The board that reports the alarm is faulty.(1) Replace the board that reports the alarm.

----End


A.2.166 T_F_RST

DescriptionThe T_F_RST is an alarm indicating that the transmit FIFO is reset.

Attribute




Name Meaning



Impact on the SystemServices in the PDH path are interrupted.

Possible Causesl Cause 1: The frequency offset of the transmitted signal is large.



A-245


Procedure

Step 1 Cause 1: The frequency offset of the transmitted signal is large.(1) Test the frequency offset of the transmitted signal.

If... Then...

The frequency offset is large Troubleshoot the opposite site.

The frequency offset meets the requirement Go to Cause 2.


----End

Related Information

None.

A.2.167 T_LOC

Description

The T_LOC is an alarm indicating that the clock is lost on the transmit line side.

Attribute



Parameters


Name Meaning


Parameter 2, Parameter 3 Indicates the ID of the AU-4 path that reports the alarm. Forexample, 0x00 0x01 indicate that the alarm is reported by AU-4path 1 of the SDH signal.


Maintenance Guide


Issue 04 (2010-10-30)


Services in the AU-4 path that reports the alarm are interrupted.

Possible Causesl Cause 1: The PXC board is faulty.l Cause 2: The line board is faulty.

Procedure

Step 1 Cause 1: The PXC board is faulty.(1) Replace the PXC board of the local site.

If... Then...




Go to Cause 2.

Step 2 Cause 2: The line board is faulty.(1) Replace the board that reports the alarm. For details, see 6.3 Replacing the SDH Optical

Interface Board or 6.4 Replacing the SDH Electrical Interface Board.

----End

Related Information

None.

A.2.168 T_LOS

Description

The T_LOS is an alarm indicating that signals are lost on the transmit line side.

Attribute



Parameters




A-247

Name Meaning




Services in the AU-4 path that reports the alarm are interrupted.

Possible Causesl Cause 1: The SDH service configuration does not match the type of the line board.l Cause 2: The PXC board is faulty.l Cause 3: The line board is faulty.

Procedure

Step 1 Cause 1: The SDH service configuration does not match the type of the line board.(1) Check the SDH service configuration.

If... Then...

The SDH service configuration does notmatch the type of the line board


The SDH service configuration is correct Go to Cause 2.

Step 2 Cause 2: The PXC board is faulty.(1) Replace the PXC board of the local site.

If... Then...




Go to Cause 3.

Step 3 Cause 3: The line board is faulty.(1) Replace the line board that reports the alarm at the local site. For details, see 6.3 Replacing

the SDH Optical Interface Board or 6.4 Replacing the SDH Electrical InterfaceBoard.

----End

Related Information

None.


Maintenance Guide


Issue 04 (2010-10-30)

A.2.169 TEMP_ALARM

DescriptionThe TEMP_ALARM alarm indicates that the board temperature crosses the threshold.

Attribute


Minor Environment alarm


Name Meaning

Parameter 1 l 0x01: The temperature crosses the upper threshold.l 0x02: The temperature crosses the lower threshold.

Impact on the SystemThe 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 a

sunshade) to control the temperature.(2) If the alarm is reported by a board of the IDU, check whether the temperature control

devices, such as air-conditioners, operate normally.

If... Then...

The temperature control devicesmalfunction

Adjust the temperature control devices.

The temperature control devices worknormally




A-249

(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


(4) Clear the alarm according to the type of the IDU.

If... Then...

The IDU is not equipped with a dust filter Clear the alarm according to the solutionfor the alarm that is generated when thetemperature detection circuit of a board isfaulty.

The IDU is equipped with a dust filter Go to the next step.

(5) Clean the dust filter.

If... Then...

The alarm clears after the dust filter iscleaned


The alarm persists after the dust filter iscleaned

Clear the alarm according to the solutionfor the alarm that is generated when thetemperature detection circuit of a board isfaulty.

Step 2 Cause 2: The temperature detection circuit of the board is faulty.

(1) If the ambient temperature is normal and no heat dissipation problem exists, replace theboard that reports the alarm.

----End

Related Information

None.

A.2.170 TU_AIS

Description

The AU_AIS is an indication of TU alarms. This alarm occurs when a board detects the TU pathof all 1s.


Maintenance Guide


Issue 04 (2010-10-30)

Attribute



Parameters


Name Meaning




When the TU_AIS alarm occurs, the services in the alarmed TU path are interrupted. If theservices are configured with protection, 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) Check whether the SDH service data is correct. For details, see Creating Cross-Connectionsof Point-to-Point Services.

If... Then...

The SDH service data is incorrect Change the configuration data.

The SDH service data is correct Go to Cause 2.

Step 2 Cause 2: The line is faulty.

(1) Check whether a line alarm that causes AIS insertion is reported on the service trail.

NOTEFor details about the line alarms that cause AIS insertion, see E.2.6 AIS Insertion.



A-251

If... Then...

The line alarm is reported Change the configuration data.

No line alarms are reported Go to step 3.

Step 3 Locate whether the board at the local end or at the opposite end is faulty. For details, see 7.5Software loopback.

If... Then...

The board at the opposite end is faulty Go to Cause 3.

The board at the local end is faulty Go to Cause 4.

Step 4 Cause 3: The board at the opposite end is faulty.

(1) In this case, replace the faulty board at the opposite end.

Step 5 Cause 4: The board at the local end is faulty.

(1) Replace the line board at the local site. For details, see 6.3 Replacing the SDH OpticalInterface Board or 6.4 Replacing the SDH Electrical Interface Board.

If... Then...





(2) Replace the PXC board of the local site.

If... Then...






If... Then...

A tributary board reports the alarm Replace the PDH interface board.

An IF board reports the alarm Replace the IF board.

----End

Related Information

None.

A.2.171 TU_AIS_VC12


Maintenance Guide


Issue 04 (2010-10-30)

DescriptionThe TU_AIS_VC12 is an indication of TU alarms at VC-12 level. This alarm occurs when aboard detects TU pointers of all 1s.

Attribute




Name Meaning


Parameter 2, Parameter 3 Indicate the ID of the VC-12 path that reports the alarm. Forexample, 0x00 0x01 indicate that the alarm is reported by VC-12path 1 of the related board.

Impact on the SystemWhen the TU_AIS_VC12 alarm occurs, the services in the alarmed VC-12 path are interrupted.If the service is configured with protection, the protection switching is also triggered.

Possible 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 Cross-Connections of Point-to-Point Services to check whether the SDH

service data is incorrect.

If... Then...






A-253



If... Then...


No line alarms are reported Go to step 3.

Step 3 Locate whether the board at the local end or at the opposite end is faulty. For details, see 7.5.5Setting Loopback for the Ethernet Service Processing Board.

If... Then...



Step 4 Cause 3: The board at the opposite end is faulty.(1) In this case, replace the faulty board at the opposite end.

Step 5 Cause 4: The board at the local end is faulty.(1) Replace the line board at the local site. For details, see 6.3 Replacing the SDH Optical


If... Then...






If... Then...




Replace the alarmed board.

----End


A.2.172 TU_AIS_VC3

DescriptionThe TU_AIS_VC3 is a TU alarm indication at VC-3 level. This alarm occurs when a boarddetects TU pointers of all 1s.


Maintenance Guide


Issue 04 (2010-10-30)

Attribute



Parameters


Name Meaning




When the TU_AIS_VC3 alarm occurs, the services in the alarmed VC-3 path are interrupted. Ifthe services are configured with protection, the protection switching is triggered.


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


(1) Check whether the SDH service data is correct. For details, see Creating Cross-Connectionsof Point-to-Point Services.

If... Then...








A-255

If... Then...


No line alarms are reported Go to Step 3.

Step 3 Locate whether the board at the local end or at the opposite end is faulty. For details, see 7.5.5Setting Loopback for the Ethernet Service Processing Board.

If... Then...



Step 4 Cause 3: The board at the opposite end is faulty.

(1) Replace the faulty board at the opposite end.

Step 5 Cause 4: The board at the local end is faulty.

(1) Replace the line board at the local end. For details, see 6.3 Replacing the SDH OpticalInterface Board or 6.4 Replacing the SDH Electrical Interface Board.

If... Then...






If... Then...




Replace the alarmed board.

----End

Related Information

None.

A.2.173 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.


Maintenance Guide


Issue 04 (2010-10-30)

Attribute




Name Meaning



Impact on the SystemServices in the TU path that reports the alarm are interrupted. If the services are configured withprotection, protection switching is also triggered.

Possible Causesl Cause 1: Configuration data is incorrect.l Cause 2: The board at the opposite site is faulty.l Cause 3: The board at the local site is faulty.

Procedure

Step 1 Cause 1: Configuration data is incorrect.(1) Check whether the SDH service data is correct. For details, see Creating Cross-Connections

of Point-to-Point Services.

If... Then...


The SDH service data is correct Go to Step 2.

Step 2 Locate whether the board at the local site or at the opposite site is faulty. For details, see 7.5Software loopback.

If... Then...

The board at the opposite site is faulty Go to Cause 2.

The board at the local site is faulty Go to Cause 3.

Step 3 Cause 2: The board at the opposite site is faulty.



A-257

(1) In this case, replace the faulty board at the opposite site.

Step 4 Cause 3: The board at the local site is faulty.(1) Replace the line board at the local site. For details, see 6.3 Replacing the SDH Optical


If... Then...






If... Then...






If... Then...



----End


A.2.174 TU_LOP_VC12

DescriptionThe TU_LOP_VC12 is an alarm indicating that the VC-12 TU pointer is lost. This alarm isreported if a board detects that the VC-12 TU-PTR value is an invalid pointer or NDF reversionin eight consecutive frames.

Attribute





Maintenance Guide


Issue 04 (2010-10-30)


Name Meaning


Parameter 2, Parameter 3 Indicate the ID of the VC-12 path that reports the alarm. Forexample, 0x00 0x01 indicate that the alarm is reported in VC-12path 1 of the corresponding board.



Procedure



If... Then...



Step 2 Locate whether the board at the local site or at the opposite site is faulty. For details, see 7.5.5Setting Loopback for the Ethernet Service Processing Board.

If... Then...



Step 3 Cause 2: The board at the opposite site is faulty.(1) In this case, replace the faulty board at the opposite site.



If... Then...





A-259

If... Then...




If... Then...




Replace the board that reports thealarm.

----End


A.2.175 TU_LOP_VC3

DescriptionThe TU_LOP_VC3 is an alarm indicating that the VC-3 TU pointer is lost. This alarm is reportedif a board detects that the VC-3 TU-PTR value is an invalid pointer or NDF reversion in eightconsecutive frames.

Attribute




Name Meaning


Parameter 2, Parameter 3 Indicate the ID of the VC-3 path that reports the alarm. For example,0x00 0x01 indicate that the alarm is reported in VC-3 path 1.



Maintenance Guide


Issue 04 (2010-10-30)


Procedure



If... Then...



Step 2 Locate whether the board at the local site or at the opposite site is faulty. For details, see 7.5Software loopback.

If... Then...



Step 3 Cause 2: The board at the opposite site is faulty.(1) Replace the faulty board at the opposite site.



If... Then...






If... Then...






If... Then...




A-261

If... Then...


----End


A.2.176 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




Name Meaning



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 at the local site is faulty.

Procedure

Step 1 Cause 1: The opposite equipment transmits the AIS signal.(1) Check whether the opposite equipment transmits the AIS signal.


Maintenance Guide


Issue 04 (2010-10-30)

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 at the local site is faulty.


----End

Related Information

None.

A.2.177 VCAT_LOA

Description

The VCAT_LOA is an alarm indicating alignment loss of virtual concatenations. This alarm isreported if a board detects that the time delays between the timeslots bound to a VCTRUNK areout of the permissible limit.

Attribute



Parameters


Name Meaning


Parameter 2, Parameter 3 Indicates the ID of the VCTRUNK that reports the alarm. Forexample, 0x00 0x01 indicate that the alarm is reported in path 1.


The virtually concatenated services are interrupted.



A-263

Possible Causes

Cause 1: The timeslots bound to a VCTRUNK travel through different physical links, so thedelays between the virtually concatenated links are long.

Procedure

Step 1 Cause 1: The timeslots bound to a VCTRUNK travel through different physical links, so thedelays between the virtually concatenated links are long.

(1) Determine the ID of the VCTRUNK path that reports the alarm based on the alarmparameter.

(2) Check whether the transmission routes of the paths bound to a VCTRUNK are the same.If not, adjust their routes to the same.

----End

Related Information

None.

A.2.178 VCAT_LOM_VC12

Description

The VCAT_LOM_VC12 is an alarm indicating the loss of virtual concatenation multiframes inthe VC-12 path. This alarm is reported if the board detects that the K4 byte of the VC-12 pathdoes not match the expected multiframe sequence.

Attribute



Parameters


Name Meaning


Parameter 2, Parameter 3 Indicate the ID of the VC-12 path that reports the alarm. Forexample, 0x00 0x01 indicate that the alarm is reported in VC-12path 1.


Maintenance Guide


Issue 04 (2010-10-30)

Impact on the SystemThe path that reports the alarm is unavailable. If the LCAS function is disabled, services areinterrupted.

Possible Causesl Cause 1: Bit errors occur in the line.l Cause 2: The MFI field in the K4 byte sent from the opposite site is incorrect.l Cause 3: The delays between virtual concatenations are long.

ProcedureStep 1 Cause 1: Bit errors occur in the line.

(1) Check whether the bit error alarm BIP_EXC or BIP_SD occurs.

If... Then...

Such an alarm occurs Handle the alarm immediately.

No alarm occurs Go to Cause 2.

Step 2 Cause 2: The MFI field in the K4 byte sent from the opposite site is incorrect.(1) Replace the board at the opposite site. For details, see 6.6 Replacing the Ethernet Service

Processing Board.(2) Replace the board and then check whether the alarm clears.

If... Then...


The alarm persists Go to Cause 3.

Step 3 Cause 3: The delays between virtual concatenations are long.(1) Check whether the VCAT_LOA alarm is reported in this path.

If... Then...

The VCAT_LOA alarm is reported Handle the VCAT_LOA alarm immediately.

No VCAT_LOA alarm is reported Go to Cause 2.

(2) Check whether the VCAT_LOM_VC12 alarm clears after handling the VCAT_LOAalarm.

If... Then...


The alarm persists Replace the board that reports the alarm at the local site. For details,see 6.6 Replacing the Ethernet Service Processing Board.

----End




A-265

A.2.179 VCAT_LOM_VC3

DescriptionThe VCAT_LOM_VC3 is an alarm indicating the loss of virtual concatenation multiframes inthe VC-3 path. This alarm is reported if the board detects that the H4 byte of the VC-3 path doesnot match the expected multiframe sequence.

Attribute




Name Meaning




Possible Causesl Cause 1: Bit errors occur in the line.l Cause 2: The MFI field in the K4 byte sent from the opposite site is incorrect.l Cause 3: The delays between virtual concatenations are long.

Procedure

Step 1 Cause 1: Bit errors occur in the line.(1) Check whether the bit error alarm BIP_EXC or BIP_SD occurs.

If... Then...

Such an alarm occurs Handle the alarm immediately.

No alarm occurs Go to Cause 2.

Step 2 Cause 2: The MFI field in the K4 byte sent from the opposite site is incorrect.


Maintenance Guide


Issue 04 (2010-10-30)

(1) Replace the board at the opposite site. For details, see 6.6 Replacing the Ethernet ServiceProcessing Board.


If... Then...


The alarm persists Go to Cause 3.

Step 3 Cause 3: The delays between virtual concatenations are long.(1) Check whether the VCAT_LOA alarm is reported in this path.

If... Then...

The VCAT_LOA alarm is reported Handle the VCAT_LOA alarm immediately.

No VCAT_LOA alarm is reported Go to Cause 2.

(2) Check whether the VCAT_LOM_VC3 alarm clears after handling the VCAT_LOA alarm.

If... Then...


The alarm persists Replace the board that reports the alarm at the local site. For details,see 6.6 Replacing the Ethernet Service Processing Board.

----End


A.2.180 VCAT_SQM_VC12

DescriptionThe VCAT_SQM_VC12 is an alarm indicating the SQ number mismatch of a virtualconcatenation in the VC-12 path. This alarm is reported if the board detects that the SQ of avirtual concatenation does not match the expected value.

Attribute






A-267

Name Meaning


Parameter 2, Parameter 3 Indicate the ID of the VC-12 path that reports the alarm. Forexample, 0x00 0x01 indicate that the alarm is reported in VC-12path 1.


The path that reports the alarm is unavailable. If the LCAS function is disabled, services areinterrupted.

Possible Causesl Cause 1: Bit errors occur on certain links or certain links are faulty.

l Cause 2: The SQ number sent from the opposite site is incorrect.

Procedure

Step 1 Cause 1: Bit errors occur on certain links or certain links are faulty.

(1) Check whether bit errors or line alarms occur. Focus on the bit error alarm BIP_EXC orBIP_SD.

If... Then...

Bit errors or line alarms occur Clear these alarms.

No bit errors or line alarms occur Go to the next step.


Step 2 Cause 2: The SQ number sent from the opposite site is incorrect.

(1) Replace the corresponding board at the opposite site.

If... Then...




Contact Huawei technical support engineersto handle the alarm.

----End

Related Information

None.

A.2.181 VCAT_SQM_VC3


Maintenance Guide


Issue 04 (2010-10-30)

DescriptionThe VCAT_SQM_VC3 is an alarm indicating the sequence (SQ) number mismatch of a virtualconcatenation in the VC-3 path. This alarm is reported if the board detects that the SQ of a virtualconcatenation does not match the expected value.

Attribute




Name Meaning




Possible Causesl Cause 1: Bit errors occur on certain links or certain links are faulty.l Cause 2: The SQ number sent from the opposite site is incorrect.

Procedure

Step 1 Cause 1: Bit errors occur on certain links or certain links are faulty.(1) Check whether bit errors or line alarms occur. Focus on the bit error alarm BIP_EXC or

BIP_SD.

If... Then...

Bit errors or line alarms occur Clear these alarms.

No bit errors or line alarms occur Go to the next step.


Step 2 Cause 2: The SQ number sent from the opposite site is incorrect.(1) Replace the corresponding board at the opposite site.



A-269

If... Then...




Contact Huawei technical support engineersto handle the alarm.

----End

Related Information

None.

A.2.182 VOLT_LOS

Description

The VOLT_LOS is an alarm indicating that the power voltage is unavailable.

Attribute



Parameters


Name Meaning

Parameter 1 Indicates the type of the power that reports the alarm.l 0x01: -48 V/+24 V power outputl 0x02: -48 V/+24 V power inputl 0x03: +5 V power outputl 0x04: +3.3 V power outputl 0x05: lightning

Impact on the Systeml If the alarm is reported by the PXC board, the power module that reports the alarm fail to

work. If the system is not configured with a protection power module, the system fails towork normally.

l If the alarm is reported by the IF board, the ODU connected to the IF board fails to work.


Maintenance Guide


Issue 04 (2010-10-30)

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 Determine the type of the power supply that reports the alarm based on the alarm parameter.

Step 2 Cause 1: The output power is abnormal.(1) Clear the alarm according to the type of the power supply that reports the alarm.

If... Then...

The alarm is reported by the PXC board Replace the PXC board that reports thealarm.

The alarm is reported by the IF board Go to the next step.

(2) 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.

(3) Check the IF fiber jumper, IF cable, or ODU section by section for a short circuit.

If... Then...

A short circuit exists Replace the short-circuited component, and then replace the IFboard that reports the alarm.

No short circuit exists Replace the IF board that reports the alarm.

CAUTIONIf the alarm is caused by a short circuit, replace the short-circuited cable or ODU, and thenreplace the IF board. Otherwise, the new IF board may be damaged.

Step 3 Cause 2: The input power is abnormal.(1) Clear the alarm according to the type of the power supply that reports the alarm.

If... Then...

The alarm is reported by the IF board Replace the IF board that reports thealarm.

The alarm is reported by the PXC board Go to the next step.

(2) Check the configuration of the input power.NOTE

The IDU 620 can be configured with two PXC boards to provide 1+1 protection of the input power.



A-271

If... Then...

No power being supplied to the input isconsidered normal

Suppress the alarm for the board. For details,see E.2.2 Alarm Suppression.

No power being supplied to the input isconsidered abnormal


(3) Check the power switch.

If... Then...

The power switch is turned off Turn on the power switch.

The power switch is turned on Contact the engineers for power supply to rectify thefault.

Step 4 Cause 3: Lightning occurs.(1) Contact the engineers for power supply to check the grounding lightning facilities.

----End


A.2.183 W_R_Failure

DescriptionThe W_R_FAILURE is an alarm indicating a failure of reading or writing the chip register.

Attribute




Name Meaning

Parameter 1 Indicates the ID of the register.


Impact on the SystemServices in the path that reports the alarm are interrupted.


Maintenance Guide


Issue 04 (2010-10-30)

Possible CausesCause 1: The chip register is faulty or the read/write time sequence is incorrect.

Procedure

Step 1 Cause 1: The chip register is faulty or the read/write time sequence is incorrect.(1) Replace the board that reports the alarm.

----End


A.2.184 WRG_BD_TYPE

DescriptionThe WRG_BD_TYPE is an alarm indicating that the type of the board is incorrect.

Attribute




Name Meaning

Parameter 1 Indicates the slot ID of the board whose type is incorrect.

Impact on the SystemThe board fails to work.

Possible Causesl Cause 1: Configuration data is incorrect.l Cause 2: The board of an incorrect type is installed.

Procedure




A-273

(1) Check whether the board type complies with the planning requirement. For details, seeConfiguring Logical Boards.

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. For details, see 6 Part Replacement.

----End

Related Information

None.

A.2.185 WRG_DEV_TYPE

Description

The WRG_DEV_TYPE is an alarm indicating that the type of the equipment is incorrect.

Attribute



Parameters

None.


The equipment fails to work.

Possible Causes

Cause 1: Configuration data is incorrect.

Procedure

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


Maintenance Guide


Issue 04 (2010-10-30)

Related Information

None.

A.2.186 WS_LOS

Description

The WS_LOS is an alarm indicating that the signals at the 2 Mbit/s wayside interface are lost.

Attribute



Parameters


Name Meaning

Parameter 1 Indicates the ID of the wayside service that reports the alarm. For example, 0x01indicates that the alarm is reported by wayside service 1.


Wayside services are interrupted.

Possible Causesl Cause 1: The data of the wayside service is configured, but the service is not accessed.l Cause 2: The cable of the wayside service is loose or damaged.l Cause 3: The interconnected equipment of the wayside service is faulty.l Cause 4: A certain board is faulty.

Procedure

Step 1 Cause 1: The data of the wayside service is configured, but the service is not accessed.(1) Check the configuration planning of the wayside service.

If... Then...

The wayside service needs to beconfigured

Access the relevant service.



A-275

If... Then...

The wayside service need not beconfigured

Set the wayside service of the relevant IFboard to the disabled status. For details, seeSetting Parameters of IF Interfaces.

Step 2 Cause 2: The cable of the wayside service is loose or damaged.(1) Check whether the connectors at the two ends of the wayside service cable are loose. If

yes, connect the cable properly.(2) Test the connectivity of the wayside service cable. For details, see Testing Connectivity of

Cables. If the cable is damaged, replace the cable or prepare the connectors of the cableagain.

Step 3 Cause 3: The interconnected equipment of the wayside service is faulty.(1) Check whether the interconnected equipment of the wayside service is faulty. If yes, rectify

the fault.

Step 4 Cause 4: A certain board is faulty.(1) If the preceding causes are excluded, replace the PXC board that reports the alarm.

----End

Related Information

None.

A.2.187 XCP_INDI

Description

The XCP_INDI is an alarm indicating that the working and protection PXC boards are switched.

Attribute



Parameters


Name Meaning

Parameter 1 Indicates the slot ID of the working board.


Maintenance Guide


Issue 04 (2010-10-30)

Impact on the SystemDuring the protection switching (less than 50 ms), the VC-3/VC-12 services are interrupted.

Possible CausesProtection switching occurs on the PXC board.

Procedure

Step 1 Cause: Protection switching occurs on the PXC board.(1) Check whether the PXC board reports alarms. For details, see 7.3.3 Browsing the Current

Alarms.

If... Then...

The PXC board reports alarms Replace the PXC board.

The PXC board does not report any alarms Go to the next step.

(2) Check whether the manual switching command is run. If yes, clear the manual switching.

----End


A.2.188 XPIC_LOS

DescriptionThe XPIC_LOS is an alarm indicating that XPIC compensation signals are lost.

Attribute




Name Meaning

Parameter 1 Indicates the ID of the IF port that reports the alarm. For example, 0x01 indicatesthat the alarm is reported by IF port 1 of the corresponding board.



A-277


Bit 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


(1) Check whether the XPIC function needs to be enabled. If the XPIC function need not beenabled, see Setting Parameters of IF Interfaces and set the XPIC function to the disabledstatus, and then perform a self-loop at the XPIC port on the board by using 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, clear the MW_LOF alarm.

Step 3 Cause 3: The XPIC cable is faulty.

(1) Check the connection of the XPIC cable.

If... Then...

The cable is connected incorrectly Connect the XPIC cable properly.

The cable is properly connected Go to the next step.

(2) Test the connectivity of the XPIC cable by using the multimeter. If the XPIC cable isdamaged, replace it.

Step 4 Cause 4: The IF board or ODU is faulty.

In the case, locate the fault by replacing the IF board or ODU.

(1) Replace the paired board of the IFX board.

The paired board of the IFX2 board refers to the other IFX2 board that is connected to theIFX2 board that reports the alarm through the XPIC cable.

If... Then...

The alarm clears after the board is replaced End the alarm handling.



(2) Replace the ODU that is connected to the paired IFX board.


Maintenance Guide


Issue 04 (2010-10-30)

If... Then...

The alarm clears after the ODU is replaced End the alarm handling.

The alarm persists after the ODU isreplaced

Replace the paired board of the IFXboard.

----End




A-279

B Abnormal Event Reference

An abnormal event is an important indicator when a fault occurs on the equipment. This topicdescribes all the possible important abnormal events of the OptiX RTN 620 and how to handlethese events.

B.1 Important Abnormal EventsImportant abnormal events include protection switching events and RMON alarms.

B.2 Important Abnormal Events and Handling ProceduresThis topic describes all the important abnormal performance events of the OptiX RTN 620 inalphabetic order and how to handle these events.

OptiX RTN 620 Radio Transmission SystemMaintenance Guide B Abnormal Event Reference


B-1

B.1 Important Abnormal EventsImportant abnormal events include protection switching events and RMON alarms.

Table B-1 Important abnormal events

Event Name Source

IF 1+1 Protection Switching IF1A, IF1B, IF0A, IF0B, IFX, and IFH2

N+1 Protection Switching SCC

SNCP Protection Switching SCC

MSP Switching SCC

Linear MSP Switching SCC

Cross-Connect and Timing BoardSwitching

PXC

ERPS Event EMS6

RMON Performance Value Below theLower Limit

EMS6, EFT4, IFH2, and EFP6

RMON Performance Value Above theUpper Limit

EMS6, EFT4, IFH2, and EFP6

NOTEAll alarmed boards refer to the logical boards that are displayed on the NMS.

B.2 Important Abnormal Events and Handling ProceduresThis topic describes all the important abnormal performance events of the OptiX RTN 620 inalphabetic order and how to handle these events.

B.2.1 IF 1+1 Protection Switching

B.2.2 N+1 Protection Switching

B.2.3 SDH SNCP Protection Switching

B.2.4 Ring MS Switching

B.2.5 Linear MS Switching

B.2.6 Cross-Connect and Timing Board Switching

B.2.7 ERPS Protection Switching

B.2.8 RMON Performance Value Below the Lower Limit

B.2.9 RMON Performance Value Above the Upper Limit

B Abnormal Event ReferenceOptiX RTN 620 Radio Transmission System

Maintenance Guide

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

Issue 04 (2010-10-30)

B.2.1 IF 1+1 Protection Switching

DescriptionThis abnormal event indicates that 1+1 HSB, 1+1 FD, or 1+1 SD switching occurs on theequipment.

AttributeSeverity Type

Major Service

ParametersName Meaning

Protection Group ID Indicates the ID of the protection group wherean IF 1+1 protection switching occurs.

Slot ID of Working Board Indicates the slot ID of the current workingboard.

Current Working Board Indicates the current working board.l 0: main boardl 1: standby board

Main Board State Indicates the current state of the main board.l Normall Failedl MW_RDI

Standby Board State Indicates the current state of the standbyboard.l Normall Failedl MW_RDI



B-3

Name Meaning

Switching Request Type Indicates the type of an IF 1+1 protectionswitching request.l No requestl Automatic switchingl Manual switchingl Forced switchingl Lockout of switchingl Wait-to-restorel RDI switching

Impact on Systeml During HSB protection switching, the services are interrupted. After the switching is

completed, the services are restored to normal.

l During HSM protection switching, no bit errors occur and the services are not affected.When the AM function is enabled, the protection path works in modulation mode forensuring capacity after HSM switching is completed. Hence, the services of lower prioritiesare impaired.

Relevant Alarms

When 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 path at the local end receives the MW_RDI alarm.

– An external switching, which is triggered by the switching command that is issued fromthe NMS software, occurs. The external switching includes lockout of switching, forcedswitching, and manual switching.

l The possible causes of HSM protection switching are as follows:

– The radio link in the receive direction of the local end is faulty.

– An external switching, which is triggered by the switching command that is issued fromthe NMS software, occurs. The external switching includes lockout of switching, forcedswitching, and manual switching.

Procedure

Step 1 Rectify the fault according to the switching request type indicated by the parameter and thedescription in RPS_INDI.

----End


Maintenance Guide


Issue 04 (2010-10-30)

B.2.2 N+1 Protection Switching

DescriptionThis abnormal event indicates that N+1 protection switching occurs on the equipment.


Major Service


Protection Group ID Indicates the ID of the protection group wherean IF N+1 protection switching occurs.

Path ID Indicates the ID of the path where an IF N+1protection switching occurs.

Switching Request Type Indicates the type of an IF N+1 protectionswitching request.l Lockout of protection channell Forced switchingl SF switchingl SD switchingl Manual switchingl Wait-to-restorel Exercisel Reverse requestl No request

N+1 Protection Group State Indicates the state of an N+1 protectiongroup.l Protocol unstartedl Idle statusl Switching statusl Protocol starting

N+1 Switching Local/Remote End Indication Indicates the local or remote switching.l Local endl Remote end



B-5

Name Meaning

N+1 Switching Cause Indicates the cause of an IF N+1 protectionswitching.l Local requestl External commandl K-byte requestl Timer expiry

Impact on SystemDuring the N+1 protection switching time (not more than 50 ms), the services are interrupted.After the switching is completed, the services are restored to normal. After the switching startsand before the switching is completed, the extra services are interrupted.

NOTEIf an 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.

Relevant AlarmsWhen an IF N+1 protection switching occurs, the NP1_SW_INDI alarm is reported.

Possible Causesl An external switching occurs.

– Lockout of protection channel– Forced switching– Manual switching

l An automatic switching occurs.– The hardware of the IDU or IF board is faulty. Focus on checking whether the

HARD_BAD or BD_STATUS alarm is reported.– The MW_LOF, R_LOC, R_LOF, R_LOS, MS_AIS, or B2_EXC alarm is reported

on the working path.

Procedure

Step 1 Rectify the fault according to the switching request type and the switching cause indicated bythe parameters.

If... Then...

The switching is caused by an externalswitching

Find the cause of the external switching, andthen release the external switchingimmediately.

The switching is caused by an automaticswitching

Clear the alarm that triggers the automaticswitching.

----End


Maintenance Guide


Issue 04 (2010-10-30)

B.2.3 SDH SNCP Protection Switching

Description

This abnormal event indicates that an SDH SNCP switching occurs in the service that isconfigured with the SNCP scheme.

Attribute

Severity Type

Major Service

Parameters

Name Meaning

Protection Group ID Indicates the protection group ID of theservice where SNCP switching occurs.

Switching Request Indicates the type of an SNCP switchingrequest.l Lockout of protection channell Forced switchingl Manual switchingl Signal failurel Signal degradationl Wait-to-restorel No request

Current Working Path Indicates the current working path.l Main pathl Standby path

SNCP Working Path Status Indicates the current status of the SNCPworking path.l Normall SDl SF

SNCP Protection Path Status Indicates the current status of the SNCPprotection path.l Normall SDl SF



B-7

Impact on SystemWhen an SNCP switching occurs, you must find the cause. If the relevant link is faulty, recoverthe link immediately. Ensure that the SNCP working and protection paths are in normal state.

Possible Causesl The switching is triggered automatically.

– The hardware of the line board is faulty.

– The R_LOS, R_LOF, R_LOC, MS_AIS, B2_EXC, AU_LOP, AU_AIS,HP_LOM, MW_LOF (only when the IF board functions as the line board),MW_LIM (only when the IF board functions as the line board), B3_EXC, B3_SD,HP_TIM (in the case of VC-4 services), HP_UNEQ (in the case of VC-4 services),TU_AIS (in the case of VC-12 services) or TU_LOP (in the case of VC-12 services)alarm is reported.

l The switching is triggered manually.

– Forced switching

– Manual switching

Procedure

Step 1 On the NMS, query the type of the SDH SNCP switching request.

Step 2 Rectify the fault according to the switching request type.

If... Then...

The SDH SNCP switching is triggeredautomatically

Rectify the fault according to the relevantalarm, and eliminate the conditions of theautomatic switching.

The SDH SNCP switching is triggeredmanually

Find the cause of the manual switching, andthen release the manual switchingimmediately.

----End

B.2.4 Ring MS Switching

Description

This abnormal event indicates that a ring MSP switching occurs on the equipment that isconfigured with services.

Attribute

Severity Type

Major Service


Maintenance Guide


Issue 04 (2010-10-30)


Protection Group ID Indicates the ID of the protection group wherea ring MSP switching occurs.

Westward Protection Switching TypeEastward Protection Switching Type

Indicates the type of a ring MSP switchingrequest.l Clear alll Lock out protection channell Unlock protection channell Forced switchingl Clear forced switchingl Manual switchingl Clear manual switchingl Exercisel Clear exercise switching

Westward Switching StateEastward Switching State

Indicates the switching state.l Protocol being startedl Idlel Switchingl Pass-through state

Eastward Switching FlagWestward Switching Flag

Indicates the flag when switching occurs.l No switching or full pass-through is

performed for the servicel The switching or full pass-through is

performed for the service

Impact on Systeml During the switching time (not more than 50 ms), the services are interrupted. After the

switching is completed, the services are restored to normal. After the switching starts andbefore the switching is completed, the extra services are interrupted.

l When a ring MSP switching occurs, a fiber cut may occur or the terminal node may befaulty. In this case, you must rectify the fault immediately.

l If a fiber cut or another fault occurs on a two-fiber ring MS, the services are interrupted.

Relevant AlarmsWhen a ring MSP switching occurs, the APS_INDI alarm may be reported.



B-9

Possible Causesl External switching such as manual switching, forced switching, or exercise switching

occurs.l An automatic switching occurs.

– The hardware or line is faulty. Focus on the HARD_BAD and BD_STATUS alarms.– After the R_LOS, R_LOF, MS_AIS, B2_EXC, B2_SD, B3_EXC, B3_SD,

HP_TIM (in the case of VC-4 services), HP_UNEQ (in the case of VC-4 services),TU_AIS (in the case of VC-3 or VC-12 services), or TU_LOP (in the case of VC-3 orVC-12 services) alarm is reported on the working path, the MSP group changes to theswitching state, and an automatic switching alarm is reported.

Procedure

Step 1 On the NMS, query the switching type and the protection group ID.


If... Then...


Find the cause of the external switching, andthen clear manual switching immediately.


Clear the relevant alarm, and rectify the faultthat occurs on the hardware or line immediately.

----End

B.2.5 Linear MS Switching

DescriptionThis abnormal event indicates that a linear MSP switching occurs on the equipment that isconfigured with services.


Major Service


Protection Group ID Indicates the ID of the protection group wherea linear MSP switching occurs.


Maintenance Guide


Issue 04 (2010-10-30)

Name Meaning

Current Working Path Indicates the current working path of thelinear MS.l Working pathl Protection path

Linear MSP Switching Request Indicates the type of a linear MSP switchingrequest.l Lock out protection pathl Forced switchingl Switch upon signal failurel Switch upon signal degradationl Manual switchingl Wait-to-restorel Exercisel Reverse requestl Non-revertive requestl Not requested

Switching Status Indicates the switching state.l Protocol not startedl Idlel Switchingl Protocol being started

Remote/Local End Indication Indicates the remote or local end.l No remote/local endl Local endl Remote end

Cause for Switching Status Change Indicates the cause of changing the switchingstate.l Local requestl External commandl K-byte requestl Timer timeout

Impact on Systeml During the switching time (not more than 50 ms), the services are interrupted. After the

switching is completed, the services are restored to normal. After the switching starts andbefore the switching is completed, the extra services are interrupted.



B-11

l When a linear MSP switching occurs, a fiber cut may occur or the terminal node may befaulty. In this case, you must rectify the fault immediately.

Relevant Alarms

When a linear MSP switching occurs, the APS_INDI alarm may be reported.

Possible Causesl An external switching command such as manual, forced, or excise switching command is

issued.

l An automatic switching occurs.

After the R_LOS, R_LOF, MS_AIS, B2_EXC, B2_SD, B3_EXC, B3_SD, HP_TIM (inthe case of VC-4 services), HP_UNEQ (in the case of VC-4 services), TU_AIS (in thecase of VC-3 or VC-12 services), or TU_LOP (in the case of VC-3 or VC-12 services)alarm is reported, the MSP group changes to the switching state, and an automatic switchingalarm is reported.

l The hardware or line is faulty.

Procedure

Step 1 On the NMS, query the switching type and the protection group ID.


If... Then...


Find the cause of the external switching, andthen clear manual switching immediately.


Clear the relevant alarm, and rectify thehardware or line fault immediately.

----End

B.2.6 Cross-Connect and Timing Board Switching

Description

This abnormal event indicates that the cross-connect and timing boards are switched when theworking cross-connect and timing board on the equipment that is configured with the 1+1protection scheme is faulty.

Attribute

Severity Type

Major Service


Maintenance Guide


Issue 04 (2010-10-30)


Working Board ID Indicates the slot ID of the current workingboard.

Protection Board ID Indicates the slot ID of the current protectionboard.

Impact on SystemWhen a fault occurs on the protection cross-connect and timing board, you must find theswitching cause. If the protection cross-connect and timing board is faulty, rectify the faultimmediately. Otherwise, the services are interrupted when a fault occurs on the current workingcross-connect and timing board.

Possible Causesl The switching is triggered.l The switching is triggered manually.

The hardware of a board is faulty. Focus on the BD_STATUS, VOLT_LOS andHARD_BAD alarms reported by the original working board.

Procedure

Step 1 On the NMS, check whether the cross-connect and timing board reports a relevant alarm that istriggered automatically.

If... Then...

The cross-connect and timing boardreports a relevant alarm

Clear the alarm immediately according to theclearance method of the relevant alarm.

The cross-connect and timing board doesnot report a relevant alarm


Step 2 Check whether the hardware of the cross-connect and timing board is faulty.

If... Then...

The hardware of the cross-connect andtiming board is faulty

Replace the cross-connect and timing boardaccording to the descriptions in the PartReplacement.

The hardware of the cross-connect andtiming board is not faulty

Clear manual switching.

----End



B-13

B.2.7 ERPS Protection Switching

Description

This abnormal event indicates that Ethernet ring protection switching (ERPS) occurs on theequipment. When the state of a ring network is changed, an ERPS event is reported by a node.

Attribute

Severity Type

Major Service

Parameters

Name Meaning

Ethernet Protection Protocol Instance ID Indicates the ID of the protection group wherean ERPS event occurs.

Switching Request Type Indicates the type of a switching request.l 0x01: The R-APS (NR) packet is received

at the local end.l 0x02: The R-APS (NR or RB) packet is

received at the local end.l 0x03: WTR runningl 0x04: WTR expiresl 0x05: The R-APS (SF) packet is received

at the local end.l 0x06: Local SFl 0x07: Local clear SFl 0x08: Initial request

Switching State Indicates the switching state.l Idlel Protection

Impact on System

During the ERPS switching time (<100 ms), the services are interrupted. After the switching iscompleted, the services are restored to normal.

Relevant Alarms

None.


Maintenance Guide


Issue 04 (2010-10-30)

Possible Causesl The link is faulty.l The R-APS packet is received at the local end.

Procedure


----End

B.2.8 RMON Performance Value Below the Lower Limit

DescriptionThis abnormal event indicates that the current RMON performance value is lower than the presetlower limit.


Major Service


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, seeList of RMON Alarm Entries.

Relevant AlarmsDifferent alarms are reported when different RMON performance values are lower than thelower limits. For details, see D.3 RMON Alarm Clearance Reference.

Possible CausesThe lower limit of a performance event is set to a non-zero value.



B-15

Procedure

Step 1 Set the lower limit of the performance event to zero.

----End

B.2.9 RMON Performance Value Above the Upper Limit

Description

This abnormal event indicates that the current RMON performance value is higher than the presetupper limit.

Attribute

Severity Type

Major Service

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, seeList of RMON Alarm Entries.

Relevant Alarms

Different alarms are reported when different RMON performance values are higher than theupper limits. For details, see D.3 RMON Alarm Clearance Reference.

Possible Causes

When the performance values of different abnormal RMON performance events are higher thanthe upper limits, the causes are different from each other. For details, see D RMON EventReference.


Maintenance Guide


Issue 04 (2010-10-30)

Procedure

Step 1 See D.3 RMON Alarm Clearance Reference to handle different abnormal performance events.

----End



B-17

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 620 and how to handlethese performance events.

C.1 Performance Event ListPerformance events are categorized on the basis of the performance event type, and include allthe events of the OptiX RTN 620.

C.2 Performance Events and Handling ProceduresBased on the type of a performance event, this topic describes all the performance events on theOptiX RTN 620 and how to handle these performance events.

OptiX RTN 620 Radio Transmission SystemMaintenance Guide C Performance Event Reference


C-1

C.1 Performance Event ListPerformance events are categorized on the basis of the performance event type, and include allthe events of the OptiX RTN 620.

C.1.1 SDH/PDH Performance EventsSDH/PDH performance events are classified into five categories: pointer justification,regenerator section error, multiplex section error, higher order path error, and lower order patherror.

C.1.2 Microwave Performance EventsMicrowave performance events include the performance events regarding the microwave power,FEC, and radio link bit errors.

C.1.3 Other Performance EventsIn addition to the SDH and microwave performance events, the OptiX RTN 620 supportsperformance events regarding the optical power and temperature.

C.1.1 SDH/PDH Performance EventsSDH/PDH performance events are classified into five categories: pointer justification,regenerator section error, multiplex section error, higher order path error, and lower order patherror.

Table C-1 Pointer justification performance events

Event Name Description Source

AUPJCHIGH Indicates the count ofpositive AU pointerjustifications.

SL1, SD1, SLE, SDE, SL4,IF1A, IF1B, and IFX

AUPJCLOW Indicates the count ofnegative AU pointerjustifications.

AUPJCNEW Indicates the count of newAU pointer justifications.

TUPJCHIGH Indicates the count ofpositive TU pointerjustifications.

PH1, PO1, PD1, and PL3

TUPJCLOW Indicates the count ofnegative TU pointerjustifications.

TUPJCNEW Indicates the count of newTU pointer justifications.

C Performance Event ReferenceOptiX RTN 620 Radio Transmission System

Maintenance Guide

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

Issue 04 (2010-10-30)

Table C-2 Regenerator section error performance events


RSBBE Indicates the regeneratorsection block of backgrounderror.

SD1, SL1, SDE, SLE, IF1A,IF1B, IFX, IF0A, IF0B, andSL4

RSES Indicates the errored secondof the RS.

RSSES Indicates the severely erroredseconds of the RS.

RSUAS Indicates the unavailablesecond of the RS.

RSCSES Indicates RS consecutivesevere error seconds.

RSOFS Indicates the regeneratorsection out-of-frame second.

RSOOF Indicates the regeneratorsection of OOF performanceseconds.

NOTE

In the case of PDH radio, regenerator section bit error performance events also exist and they are detectedaccording to the overheads used for detecting frame alignment and bit errors in the PDH microwave frames.

Table C-3 Multiplex section error performance events


MSBBE Indicates the backgroundblock error of the multiplexsection (MS).

SD1, SL1, SDE, SLE, IF1A,IF1B, IFX, and SL4

MSES Indicates the errored secondof the MS.

MSSES Indicates the errored secondof the MS.

MSCSES Indicates the consecutivelyand severely errored secondsof the MS.

MSUAS Indicates the unavailablesecond of the MS.



C-3


MSFEBBE Indicates the multiplexsection far end block ofbackground error.

MSFEES Indicates MS far end erroredsecond.

MSFESES Indicates the multiplexsection far end severelyerrored second.

MSFECSES Indicates the multiplexsection far end consecutiveseverely errored second.

MSFEUAS Indicates the multiplexsection far end unavailablesecond.

Table C-4 Higher order path error performance events


HPBBE Indicates the higher orderpath background block error.

SD1, SL1, SDE, SLE, IF1A,IF1B, IFX, and SL4

HPES Indicates the higher orderpath errored second.

HPSES Indicates the higher orderpath severely errored second.

HPCSES Indicates the higher orderpath consecutive severelyerrored second.

HPUAS Indicates the higher orderpath unavailable second.

HPFEBBE Indicates the higher orderpath far end backgroundblock error.

HPFEES Indicates the higher orderpath far end errored second.

HPFESES Indicates the higher orderpath far end severely erroredsecond.


Maintenance Guide


Issue 04 (2010-10-30)


HPFECSES Indicates the higher orderpath far end consecutiveseverely errored second.

HPFEUAS Indicates the higher orderpath far end unavailablesecond.

Table C-5 VC-3 path error performance events


VC3BBE Indicates the VC-3background block error.

EFT4

VC3ES Indicates the VC-3 erroredsecond.

VC3SES Indicates the VC-3 severelyerrored second.

VC3CSES Indicates the VC-3consecutive severely erroredsecond.

VC3UAS Indicates the VC-3unavailable second.

VC3FEBBE Indicates the VC-3 far endblock of the backgrounderror.

VC3FEES Indicates the VC-3 far enderrored second.

VC3FESES Indicates the VC-3 far endconsecutive severely erroredsecond.

VC3FECSES Indicates the VC-3 far endconsecutive severely erroredsecond.

VC3FEUAS Indicates the VC-3 far endunavailable second.



C-5

Table C-6 Lower order path error performance events


LPBBE Indicates the lower order pathblock of background error.

PO1, PH1, PD1, PL3, EFT4,EMS6, IF0A, IF0B, andEFP6

LPES Indicates the lower order patherrored second.

LPSES Indicates the lower order pathseverely errored second.

LPCSES Indicates the lower order pathconsecutive severely erroredsecond.

LPUAS Indicates the lower order pathunavailable second.

LPFEBBE Indicates the lower order pathfar end block of backgrounderror.

LPFEES Indicates the lower order pathfar end errored second.

LPFESES Indicates the lower order pathfar end severely erroredsecond.

LPFECSES Indicates the Lower orderpath far end consecutiveseverely errored second.

LPFEUAS Indicates the lower order farend unavailable second.

PO1, PH1, PD1, PL3, EFT4,IF0A, and IF0B

Table C-7 Line side code violation performance events


E3_LCV_SDH Indicates the E3 line sidecode violation count.

PL3

E3_LES_SDH Indicates the E3 line sidecode violation erroredsecond.

E3_LSES_SDH Indicates the E3 line sidecode violation severelyerrored second.

T3_LCV_SDH Indicates the T3 line sidecode violation count.


Maintenance Guide


Issue 04 (2010-10-30)


T3_LES_SDH Indicates the T3 line sidecode violation erroredsecond.

T3_LSES_SDH Indicates the T3 line sidecode violation severelyerrored second.


C.1.2 Microwave Performance EventsMicrowave performance events include the performance events regarding the microwave power,FEC, and radio link bit errors.

Table C-8 Microwave power performance events


TSL_MAX Indicates the maximum radiotransmit signal level.

ODU

TSL_MIN Indicates the minimum radiotransmit signal level.

TSL_CUR Indicates the current radiotransmit signal level.

TSL_AVG Indicates the average radiotransmit signal level.

RSL_MAX Indicates the maximum radioreceived signal level.

RSL_MIN Indicates the minimum radioreceived signal level.

RSL_CUR Indicates the current radioreceived signal level.

RSL_AVG Indicates the average radioreceived signal level.

TLHTT Indicates the duration whenthe transmit power is higherthan the upper threshold.

TLLTT Indicates the duration whenthe transmit power is higherthan the lower threshold.



C-7


RLHTT Indicates the duration whenthe receive power is lowerthan the upper threshold.

RLLTT Indicates the duration whenthe receive power is lowerthan the lower threshold.

Table C-9 FEC performance events


FEC_BEF_COR_ER Indicates the BER before theFEC is performed.

IF1A, IF1B, IF0A, IF0B,IFX, and IFH2

FEC_COR_BYTE_CNT Indicates the number of bytesthat are corrected through theFEC.

IF1A, IF1B, IF0A, IF0B, andIFX

FEC_UNCOR_BLOCK_CNT

Indicates the number offrames that cannot becorrected through the FEC.

IFH2

Table C-10 Performance events regarding radio link bit errors


IF_BBE Indicates the radio linkbackground block error.

IF0A, IF0B,and IFH2

IF_ES Indicates the radio linkerrored second.

IF_SES Indicates the radio linkseverely errored second.

IF_UAS Indicates the radio linkunavailable second.

IF_CSES Indicates the radio linkconsecutively severelyerrored second.


Maintenance Guide


Issue 04 (2010-10-30)

Table C-11 ATPC performance events


ATPC_P_ADJUST Indicates the positive ATPCadjustment event.

ODU

ATPC_N_ADJUST Indicates the negative ATPCadjustment event.

Table C-12 AM performance events


QPSKWS Indicates the workingduration of the QPSK mode.

IFH2

QAMWS16 Indicates the workingduration of the 16QAMmode.





ACMDOWNCNT Indicates the count of thedownshift of the AM scheme.

ACMUPCNT Indicates the count of theupshift of the AM scheme.


C.1.3 Other Performance EventsIn addition to the SDH and microwave performance events, the OptiX RTN 620 supportsperformance events regarding the optical power and temperature.



C-9

Table C-13 Performance events regarding optical power


TPLMAX Indicates the maximumtransmit power of the opticalport on the laser.

SD1, SL1, SL4, and EMS6

TPLMIN Indicates the minimumtransmit power of the opticalport on the laser.

TPLCUR Indicates the current transmitpower of the optical port onthe laser.

RPLMAX Indicates the maximumreceive power of the opticalport on the laser.

RPLMIN Indicates the minimumreceive power of the opticalport on the laser.

RPLCUR Indicates the current receivepower of the optical port onthe laser.

Table C-14 Performance events regarding board temperature


BDTEMPMAX Indicates the maximumboard temperature.

IF1A, IF1B, IFX, IF0A,IF0B, PXC, ODU, SCC,EFT4, EMS6, and EFP6

BDTEMPMIN Indicates the minimum boardtemperature.

BDTEMPCUR Indicates the current boardtemperature.

Table C-15 Performance events regarding temperature of a laser core


OSPITMPMAX Indicates the maximumtemperature of a laser core.

EMS6

OSPITMPMIN Indicates the minimumtemperature of a laser core.

OSPITMPCUR Indicates the currenttemperature of a laser core.


Maintenance Guide


Issue 04 (2010-10-30)


C.2 Performance Events and Handling ProceduresBased on the type of a performance event, this topic describes all the performance events on theOptiX RTN 620 and how to handle these performance events.

C.2.1 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 SystemIf the number of TUPJCHIGH and TUPJCLOW events is less than six per day on each port, thesystem is not affected. If the pointer is justified for more than six times, or if the TUPJCNEWevent is generated, bit errors may occur in the service.

Relevant AlarmsWhen the number of TUPJCHIGH, TUPJCLOW, or TUPJCNEW events exceeds the specifiedthreshold, the MSAD_CROSSTR alarm is reported.

Performance Event Default Threshold in 15-Minute Monitoring

Default Threshold in 24-Hour Monitoring

AUPJCHIGH 1500 30000

AUPJCLOW 1500 30000

AUPJCNEW 1500 30000



C-11

Possible Causes

The NE clock is out-of-synchronization.

Procedure

Step 1 See 5.9 Troubleshooting Pointer Justifications.

----End

C.2.2 ATPC_P_ADJUST and ATPC_N_ADJUST

Descriptionl ATPC_P_ADJUST indicates the positive ATPC adjustment event.

This performance event indicates that the quality of a communications link degrades.Therefore, you must increase the transmit power of the ODU to maintain thecommunication 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. Therefore, you can decrease the transmitpower of the ODU.


Performance event cell ATPCPADJUST (ATPC_P_ADJUST) andATPCNADJUST (ATPC_N_ADJUST)

Unit None

Impact on System

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.

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.

Relevant Alarms

None.

C.2.3 TUPJCHIGH, TUPJCLOW, and TUPJCNEW

Descriptionl TUPJCHIGH indicates the count of positive TU pointer justifications.


Maintenance Guide


Issue 04 (2010-10-30)

l TUPJCLOW indicates the count of negative TU pointer justifications.

l TUPJCNEW indicates the count of new TU pointer justifications.

Attribute

Attribute Description

Performance event cell TUPPJE (TUPJCHIGH)TUNPJE (TUPJCLOW)TUNDF (TUPJCNEW)

Unit Block

Impact on SystemIf the number of TUPJCHIGH and TUPJCLOW events is less than six per day on each port, thesystem is not affected. If the pointer is justified for more than six times, or if the TUPJCNEWevent is generated, bit errors may occur in the service.

Related Alarms

When the number of TUPJCHIGH, TUPJCLOW, or TUPJCNEW events exceeds the specifiedthreshold, the HPAD_CROSSTR alarm is reported.



TUPJCHIGH 1500 30000

TUPJCLOW 1500 30000

TUPJCNEW 1500 30000

Possible Causes

The NE clock is out-of-synchronization.

Procedure

Step 1 See 5.9 Troubleshooting Pointer Justifications.

----End

C.2.4 RSBBE, RSES, RSSES, RSCSES, and RSUAS

Descriptionl RSBBE indicates the regenerator section background block error.



C-13

A BBE refers to the errored block excluding the errored block in the unavailable andseverely errored second.

l RSES indicates the regenerator section errored second.An ES refers to a second in which one or more errored blocks are detected.

l RSSES indicates the regenerator section severely errored second.An SES refers to a second in which 30% or more than 30% errored blocks exist or at leastone SDP exists. The SDP refers to a period of at least four consecutive blocks or 1 ms(whichever longer) in which the BER of all the consecutive blocks is equal to or higherthan 10-2 or the signal is lost.

l RSCSES indicates the regenerator section consecutive severely errored second.A CSES refers to a second in which an SES event occurs continuously for less than 10seconds.

l RSUAS indicates the regenerator section unavailable second.A UAS period is counted from the first second of 10 consecutive SES events. These tenseconds are considered to be a part of the unavailable time. A new available second periodstarts from the first second of ten consecutive non-SES events. These ten seconds areconsidered to be a part of the available time.

NOTE

When an IF board works in PDH mode, these performance events may also be reported. These events aredetected through the self-defined overhead byte B1 in the PDH microwave frame.


Performance event cell B1CNT

Unit Block (RSBBE)Second (RSES, RSSES, RSCSES, andRSUAS)

Impact on SystemA small number of bit errors do not affect the services. In the case of excessive bit errors,however, the services are interrupted. Generally, the BER is less than 10-3 in the case of voiceservices, and 10-6 in the case of data services.

Relevant AlarmsWhen the number of RSBBE, RSES, RSSES, RSCSES, or RSUAS events exceeds the specifiedthreshold, the RS_CROSSTR alarm is reported.



RSBBE 1500 15000

RSES 50 100


Maintenance Guide


Issue 04 (2010-10-30)



RSSES 20 50

RSUAS 20 50

RSCSES 4 (number of consecutive SES events)

Possible Causes

The system detects the regenerator section bit errors through the B1 byte.

Procedure

Step 1 See 5.4 Troubleshooting Bit Errors in TDM Services.

----End

C.2.5 RSOOF and RSOFS

Descriptionl RSOOF indicates the regenerator section out of frame.

The out-of-frame (OOF) block refers to a data block in which incorrect A1 and A2 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 SystemThe 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).

Relevant 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.



C-15

Possible CausesThe system detects incorrect A1 and A2 bytes.

Procedure

Step 1 If the R_LOF alarm is reported, eliminate the errors according to the alarm. Otherwise, see 5.4Troubleshooting Bit Errors in TDM Services for handling.

----End

C.2.6 MSBBE, MSES, MSSES, MSCSES, and MSUAS

Descriptionl MSBBE indicates the multiplex section background block error.


l MSES indicates the multiplex section errored second.An ES refers to a second in which one or more errored blocks are detected.

l MSSES indicates the multiplex section severely errored second.An SES refers to a second in which 30% or more than 30% errored blocks exist or at leastone SDP exists. The SDP refers to a period of at least four consecutive blocks or 1 ms(whichever longer) in which the BER of all the consecutive blocks is equal to or higherthan 10-2 or the signal is lost.

l MSCSES indicates the multiplex section consecutive severely errored second.A CSES refers to a second in which an SES event occurs continuously for less than 10seconds.

l MSUAS indicates the multiplex section unavailable second.A UAS period is counted from the first second of 10 consecutive SES events. These tenseconds are considered to be a part of the unavailable time. A new available second periodstarts from the first second of ten consecutive non-SES events. These ten seconds areconsidered to be a part of the available time.



Unit Block (MSBBE)Second (MSES, MSSES, MSCSES, andMSUAS)



Maintenance Guide


Issue 04 (2010-10-30)

Relevant Alarms

When the number of MSBBE, MSES, MSSES, MSCSES, or MSUAS events exceeds thespecified threshold, the MS_CROSSTR alarm is reported.



MSBBE 1500 15000

MSES 50 100

MSES 20 50

MSUAS 20 50

MSCSES 4 (number of consecutive SES events)

Possible Causes

The system detects multiplex section bit errors through the B2 byte.

Procedure


----End

C.2.7 MSFEBBE, MSFEES, MSFESES, MSFECSES, and MSFEUAS

Descriptionl MSFEBBE indicates the multiplex section far end background block error.

FEBBE indicates that the BBE occurs at the opposite site.

l MSFEES indicates the multiplex section far end errored second.

An FEES indicates that an ES event is detected at the opposite site.

l MSFESES indicates the multiplex section far end severely errored second.

An FESES indicates that an SES event is detected at the opposite site.

l MSFECSES indicates the multiplex section far end consecutive severely errored second.

FECSES indicates that an CSES event occurs at the opposite site.

l MSFEUAS indicates the multiplex section far end unavailable second.

FEUAS indicates that an UAS event occurs at the opposite site.

Attribute


Performance event cell LFEBE



C-17


Unit Block (MSFEBBE)Second (MSFEES, MSFESES, MSFECSES,and MSFEUAS)


Relevant Alarms

The MS_REI alarm is reported at the local end.

Possible Causes

The system detects multiplex section far end bit errors through the M1 byte.

Procedure

Step 1 Clear the corresponding performance events at the opposite site.

----End

C.2.8 HPBBE, HPES, HPSES, HPCSES, and HPUAS

Descriptionl HPBBE indicates the higher order path background block error.


l HPES indicates the higher order path errored second.

An ES refers to a second in which one or more errored blocks are detected.

l HPSES indicates the higher order path severely errored second.

An SES refers to a certain second in which 30% or more than 30% errored blocks aredetected or at least one serious disturbance period (SDP) exists. The SDP refers to a periodof at least four consecutive blocks or 1 ms (whichever longer) in which the BER of all theconsecutive blocks is equal to or higher than 10-2 or the signal is lost.

l HPCSES indicates the higher order path consecutive severely errored second.

A CSES refers to a second in which an SES event occurs continuously for less than 10seconds.

l HPUAS indicates the higher order path unavailable second.

A UAS period is counted from the first second of 10 consecutive SES events. These tenseconds are considered to be a part of the unavailable time. A new available second period


Maintenance Guide


Issue 04 (2010-10-30)

starts from the first second of ten consecutive non-SES events. These ten seconds areconsidered to be a part of the available time.



Unit Block (HPBBE)Second (HPES, HPSES, HPCSES, andHPUAS)


Relevant AlarmsWhen the number of HPBBE, HPES, HPSES, HPCSES, or HPUAS performance events exceedsthe specified threshold, the HP_CROSSTR alarm is reported.



HPBBE 1500 15000

HPES 50 100

HPSES 20 50

HPUAS 20 50

HPCSES 4 (number of consecutive SES events)

Possible CausesThe system detects higher order path bit errors through the B3 byte.

Procedure


----End



C-19

C.2.9 HPFEBBE, HPFEES, HPFESES, HPFECSES, and HPFEUAS

Descriptionl HPFEBBE indicates the higher order path far end background block error.

FEBBE indicates that a BBE event occurs at the opposite end.

l HPFEES indicates the higher order path far end errored second.

FEES indicates that an ES event occurs at the opposite end.

l HPFESES indicates the higher order path far end severely errored second.

FESES indicates that an SES event occurs at the opposite end.

l HPFECSES indicates the higher order path far end consecutive severely errored second.

FECSES indicates that a CSES event occurs at the opposite end.

l HPFEUAS indicates the higher order path far end unavailable second.

FEUAS indicates that a UAS event occurs at the opposite end.

Attribute


Performance event cell PFEBE

Unit Block (HPFEBBE)Second (HPFEES, HPFESES, HPFECSES,and HPFEUAS)


Relevant Alarms

The HP_REI alarm is reported at the local end.

Possible Causes

The system detects the higher order path far end bit errors through bits 1 to 4 in the G1 byte.

Procedure

Step 1 Clear the corresponding performance event at the opposite end.

----End


Maintenance Guide


Issue 04 (2010-10-30)

C.2.10 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.


l IF_SES indicates the radio link severely errored second.

An SES refers to a certain second in which 30% or more than 30% errored blocks aredetected or at least one serious disturbance period (SDP) exists. The SDP refers to a periodof at least four consecutive blocks or 1 ms (whichever longer) in which the BER of all theconsecutive blocks is equal to or higher than 10-2 or the signal is lost.

l IF_CSES indicates the radio link consecutively severely errored second.


l IF_UAS indicates the radio link unavailable second.

A UAS period is counted from the first second of 10 consecutive SES events. These tenseconds are considered to be a part of the unavailable time. A new available second periodstarts from the first second of ten consecutive non-SES events. These ten seconds areconsidered to be a part of the available time.

Attribute


Performance event cell IFCNT

Unit Block (IFBBE)Second (IFES, IFSES, IFCSES, and IFUAS)


Relevant Alarms

In the case of the IFH2 board, the MW_BER_SD or MW_BER_EXC alarm is reported whenthe BER exceeds the specified threshold.

In the case of the IF1 board, the B1_SD or B1_EXC alarm is reported when the BER exceedsthe specified threshold.



C-21

Possible CausesThe system detects bit errors on the radio link through the bit error detection overheads in theoverheads of a microwave frame.

Procedure


----End

C.2.11 VC3BBE, VC3ES, VC3SES, VC3CSES, and VC3UAS

Descriptionl VC3BBE indicates VC-3 background block error.

A BBE refers to the errored block excluding the errored block in the unavailable time andseverely errored second.

l VC3ES indicates VC-3 errored second.An ES refers to a certain second in which one or more errored blocks are detected.

l VC3SES indicates VC-3 severely errored second.An SES refers to a certain second in which 30% or more errored blocks are detected or atleast one serious disturbance period (SDP) exists. The SDP refers to a period of at leastfour consecutive blocks or 1 ms (whichever longer) in which the BER of all the consecutiveblocks is equal to or higher than 10-2 or the signal is lost.

l VC3CSES indicates VC-3 consecutive severely errored second.A CSES refers to a second of the period in which an SES event occurs continuously within10 seconds.

l VC3UAS indicates VC-3 unavailable second.A UAS period is counted from the first second of 10 consecutive SES events. These tenseconds are considered to be a part of the unavailable time. A new available second periodstarts from the first second of ten consecutive non-SES events. These ten seconds areconsidered to be a part of the available time.



Unit Block (VC3BBE)Second (VC3ES, VC3SES, VC3CSES, andVC3UAS)



Maintenance Guide


Issue 04 (2010-10-30)

Related AlarmsIf the number of VC3BBE, VC3ES, VC3SES, VC3CSES, or VC3UAS performance eventsexceeds the specified threshold, the LP_CROSSTR alarm is reported.



VC3BBE 1500 15000

VC3ES 50 100

VC3SES 20 50

VC3UAS 20 50

VC3CSES 4 (number of consecutive SES events)

Possible CausesThe system detects VC-3 path bit errors through the B3 byte.

Procedure


----End

C.2.12 VC3FEBBE, VC3FEES, VC3FESES, VC3FECSES, andVC3FEUAS

Descriptionl VC3FEBBE indicates VC-3 far end background block error.

A VC3FEBBE indicates that a BBE event is detected at the opposite site.l VC3FEES indicates VC-3 far end errored second.

An FEES indicates that an ES event is detected at the opposite site.l VC3FESES indicates VC-3 far end severely errored second.

An FESES indicates that an SES event is detected at the opposite site.l VC3FECSES indicates VC-3 far end consecutive severely errored second.

An FECSES indicates that a CSES event is detected at the opposite site.l VC3FEUAS indicates VC-3 far end unavailable second.

An FEUAS indicates that a UAS event is detected at opposite site.


Performance event cell VC3FEBE



C-23


Unit Block (VC3FEBBE)Second (VC3FEES, VC3FESES,VC3FECSES, and VC3FEUAS)


Relevant Alarms

The LP_REI_VC3 alarm is reported at the local end.

Possible Causes

The system detects the VC-3 path far end bit errors through bits 1 to 4 in the G1 byte.

Procedure


----End

C.2.13 LPBBE, LPES, LPSES, LPCSES, and LPUAS

Descriptionl LPBBE indicates the lower order path background block error.


l LPES indicates the lower order path errored second.


l LPSES indicates the lower order path severely errored second.

An SES refers to a second in which 30% or more than 30% errored blocks exist or at leastone SDP exists. The SDP is a period when loss of signal is detected or the BER of all theconsecutive blocks are greater than or equal to 10-2 in at least four consecutive blocks or 1ms (whichever longer).

l LPCSES indicates the lower order path consecutive severely errored second.


l LPUAS indicates the lower order path unavailable second.

An unavailable second (UAS) is counted from the first second of ten SES events, whichare considered to be part of the unavailable time. A new available second period starts from


Maintenance Guide


Issue 04 (2010-10-30)

the first second of ten consecutive non-SES events, which are considered to be part of theavailable time.

Attribute


Performance event cell LPBIP2CNT

Unit Block (LPBBE)Second (LPES, LPSES, LPCSES, andLPUAS)

Impact on SystemA small number of bit errors do not affect the service. In the case of excessive bit errors, however,the services are interrupted. Generally, the BER is less than 10-3 in the case of voice servicesand less than 10-6 in the case of data services.

Relevant Alarms

When the number of LPBBE, LPES, LPSES, LPCSES, or LPUAS events exceeds the specifiedthreshold, the LP_CROSSTR alarm is reported.



LPBBE 1500 15000

LPES 50 100

LPSES 20 50

LPUAS 20 50

LPCSES 4 (number of consecutive SES events)

Possible Causes

The system detects lower order path bit errors through the V5 byte (BIP-2 check) (in the caseof an E1 interface board or an Ethernet board) or B3 byte (in the case of an E3/T3 interfaceboard).

Procedure


----End



C-25

C.2.14 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 site.l LPFEES indicates the lower order path far end errored second.

FEES indicates that the ES occurs at the opposite site.l LPFESES indicates the lower order path far end severely errored second.

FESES indicates that the SES occurs at the opposite site.l LPFECSES indicates the lower order path far end consecutive severely errored second.

FECSES indicates that the CSES occurs at the opposite site.l LPFEUAS indicates the lower order path far end unavailable second.

FEUAS indicates that the UAS occurs at the opposite site.


Performance event cell LPFEBE

Unit Block (LPFEBBE)Second (LPFEES, LPFESES, LPFECSES,and LPFEUAS)

Impact on SystemA small number of bit errors do not affect the service. In the case of excessive bit errors, however,the services are interrupted. Generally, the BER is less than 10-3 in the case of voice servicesand less than 10-6 in the case of data services.

Relevant AlarmsIf a performance event is generated on a tributary board, the LP_REI alarm is generated at thelocal end. If a performance event is generated on an Ethernet board, the LP_REI_VC12 alarmis generated at the local end.

Possible CausesThe system detects lower order path bit errors through bit 3 in the V5 byte (in the case of an E1interface board or an Ethernet board) or bits 1-4 in the G1 byte (in the case of an E3/T3 interfaceboard).

Procedure


----End


Maintenance Guide


Issue 04 (2010-10-30)

C.2.15 E3_LCV_SDH, E3_LES_SDH, and E3_LSES_SDH

Descriptionl E3_LCV_SDH indicates the statistics of the E3 line side codes that do not meet the relevant

requirements.l E3_LES_SDH indicates the severely errored second of the E3 line side codes.l E3_LSES_SDH indicates the E3 line side code violation severely errored second.


Performance event cell DS3_BPV_CNT

Unit Block

Impact on SystemBit errors may occur in the services.

Possible CausesInterference signals exist on the transmission lines.

ProcedureStep 1 Check whether the services gain access to the receive end.

If... Then...

No services gain access to the receive end Enable the services to gain access to thereceive end.

Certain services gain access to the receiveend


Step 2 Check whether the ground cable is connected properly

If... Then...

The ground cable is connected incorrectly oris disconnected

Connect the ground cable correctly toeliminate the interference.

The connection is correct Go to the next step.

Step 3 Check whether the connectors of the transmission cables are made properly.

If... Then...

The connector is made improperly Make a new connector.

The connection is correct Eliminate the external interference signals.

----End



C-27

C.2.16 T3_LCV_SDH, T3_LES_SDH, and T3_LSES_SDH

Descriptionl T3_LCV_SDH indicates the statistics of the T3 line side codes that do not meet the relevant

requirements.l T3_LES_SDH indicates the severely errored second of the T3 line side codes.l T3_LSES_SDH indicates the severely errored second of the T3 line side codes.


Performance event cell DS3_BPV_CNT

Unit Block

Impact on SystemBit errors may occur in the services.

Possible CausesInterference signals exist on the transmission lines.

ProcedureStep 1 Check whether the services gain access to the receive end.

If... Then...

No services gain access to the receive end Enable the services to gain access to thereceive end.

Certain services gain access to the receiveend


Step 2 Check whether the ground cable is connected properly

If... Then...

The ground cable is connected incorrectly oris disconnected

Connect the ground cable correctly toeliminate the interference.

The ground cable is connected correctly Go to the next step.

Step 3 Check whether the connectors of the transmission cables are made properly.

If... Then...

The connectors are made inappropriately Make new connectors.

The connections are correct Eliminate the external interference signals.

----End


Maintenance Guide


Issue 04 (2010-10-30)

C.2.17 TSL_MAX, TSL_MIN, TSL_CUR, and TSL_AVG

Descriptionl TSL_MAX indicates the maximum radio transmit signal level.l TSL_MIN indicates the minimum radio transmit signal level.l TSL_CUR indicates the current radio transmit signal level.l TSL_AVG indicates the average radio transmit signal level.


Performance event cell TSL

Unit dBm

Impact on SystemWhen the radio transmit signal level is very low or very high, the radio received signal level atthe opposite site is very low or very high. As a result, bit errors occur and even services areinterrupted.

Related AlarmsIf the radio transmit signal level is beyond the range supported by the ODU, theRADIO_TSL_HIGH or RADIO_TSL_LOW alarm is reported.

C.2.18 RSL_MAX, RSL_MIN, RSL_CUR, and RSL_AVG

Descriptionl RSL_MAX indicates the maximum radio received signal level.l RSL_MAX indicates the minimum radio received signal level.l RSL_CUR indicates the current radio received signal level.l RSL_AVG indicates the average radio received signal level.


Performance event cell RSL

Unit dBm

Impact on SystemWhen the radio received signal level is very low or very high, bit errors occur and even servicesare interrupted.



C-29

Relevant AlarmsIf the radio received signal level exceeds the specified threshold, the RADIO_RSL_HIGH orRADIO_RSL_LOW alarm is reported.

C.2.19 RLHTT, RLLTT, TLHTT, and TLLTT

Descriptionl RLHTT indicates the duration when the ODU at the local end has a receive power lower

than the upper threshold.l RLLTT indicates the duration when the ODU at the local end has a receive power lower

than the lower threshold.l TLHTT indicates the duration when the ODU at the local end has a transit power higher

than the upper threshold.l TLLTT indicates the duration when the ODU at the local end has a transit power higher

than the lower threshold.


Performance event cell RLHTS, RLLTS, TLHTS, and TLLTS

Unit Second

Impact on SystemNone.

Relevant AlarmsNone.

C.2.20 ACMDOWNCNT and ACMUPCNT

Descriptionl ACMDOWNCNT indicates the count of AM switching on a board from a high-efficiency

modulation scheme to a low-efficiency modulation scheme in the current performancestatistics period.

l ACMUPCNT indicates the count of AM switching on a board from a low-efficiencymodulation scheme to a high-efficiency modulation scheme in the current performancestatistics period.


Performance event cell AMDOWNCNT and AMUPCNT


Maintenance Guide


Issue 04 (2010-10-30)


Unit None

Impact on System

ACMDOWNCNT and ACMUPCNT indicate only statistical values, and do not affect thesystem.

Relevant Alarms

AM_DOWNSHIFT

Possible Causes

When the AM function is enabled, the modulation scheme used by the IF port on an IF boardvaries according to the quality of the link. Accordingly, the system counts the performanceduring the change of the modulation scheme. When a low-efficiency modulation scheme isswitched to a high-efficiency modulation scheme, an upward switching action is recorded andone ACMUPCNT event is counted. Similarly, when a high-efficiency modulation scheme isswitched to a low-efficiency modulation scheme, a downward switching action is recorded andone ACMDOWNCNT event is counted.

C.2.21 FEC_BEF_COR_ER, FEC_COR_BYTE_CNT, andFEC_UNCOR_BLOCK_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_CN indicates the number of frames that cannot be correctedthrough the FEC.

This event indicates the number of error blocks after the FEC is performed.

Attribute


Performance event cell FECBEFCORER (FEC_BEF_COR_ER),FECUNCORBLOCKCNT(FEC_COR_BYTE_CNT), andFECUNCORBLOCKCNT(FEC_UNCOR_BLOCK_CNT)



C-31


Unit None (FEC_BEF_COR_ER)None (FEC_COR_BYTE_CNT)Block (FEC_UNCOR_BLOCK_CNT)

Impact on SystemIf the value of FEC_BEF_COR is very high, residual bit errors are generated after the FEC isperformed.

If the value of FEC_UNCOR_BLOCK_CNT is not zero, bit errors that cannot be corrected aregenerated on a radio link, and bit errors are generated in the service accordingly.

Relevant AlarmsIf a byte cannot be corrected, the MW_FEC_UNCOR alarm is reported.

C.2.22 QPSKWS, QAMWS16, QAMWS32, QAMWS64,QAMWS128, and QAMWS256

Descriptionl QPSKWS indicates the working duration of the QPSK mode.l QAMWS16 indicates the working time of the 16QAM mode.l QAMWS32 indicates the working time of the 32QAM mode.l QAMWS64 indicates the working time of the 64QAM mode.l QAMWS128 indicates the working time of the 128QAM mode.l QAMWS256 indicates the working time of the 256QAM mode.


Performance event cell QPSKWSSECOND (QPSKWS)QAMWS16SECOND (QAMWS16)QAMWS32SECOND (QAMWS32)QAMWS64SECOND (QAMWS64)QAMWS128SECOND (QAMWS128)QAMWS256SECOND (QAMWS256)

Unit Second

Impact on SystemWhen the AM function is not enabled, the performance event does not affect the system.


Maintenance Guide


Issue 04 (2010-10-30)

When the AM function is enabled, in normal cases, the seconds of the modulation mode forensuring capacity account for a larger percentage. In the duration set for good weather, if theseconds of the low-efficiency modulation mode account for a larger percentage, the performanceof the radio link is abnormal.

Relevant Alarms

None.

C.2.23 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 dBm

Impact on System

In normal cases, the receive optical power is 3 dB higher than the receiver sensitivity, and 5 dBlower 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.

Relevant Alarmsl If the transmit optical power at the opposite site is lower than the receiver sensitivity, the

IN_PWR_LOW is reported.

l If the receive optical power at the opposite site is higher than the overload power, theIN_PWR_HIGH alarm is reported.

C.2.24 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.



C-33

Attribute


Performance event cell IPM

Unit dBm

Impact on System

In normal cases, the receive optical power is 3 dB higher than the receiver sensitivity, and 5 dBlower than the overload power.

If the receive optical power is very low or very high, bit errors occur and even services areinterrupted.

Relevant 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 alarmis reported.

C.2.25 BDTMPMAX, BDTMPMIN, and BDTMPCUR

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 None.

Unit °C

Impact on SystemIf the temperature of a board is very high or very low, the performance of the board degrades,and bit errors or other faults occur.

Relevant Alarms

If the temperature of a board exceeds the specified threshold, the TEMP_ALARM alarm isreported.


Maintenance Guide


Issue 04 (2010-10-30)

C.2.26 OSPITMPMAX, OSPITMPMIN, and OSPITMPCUR

Descriptionl OSPITMPMAX indicates the maximum temperature of a laser core.l OSPITMPMIN indicates the minimum temperature of a laser core.l OSPITMPCUR indicates the current temperature of a laser core.


Performance event cell TMP

Unit °C

Impact on SystemIf the temperature of a laser core is very high or very low, the performance of the laser degrades,and bit errors or other faults occur.

Relevant AlarmsNone.



C-35

D RMON Event Reference

RMON events reflect the running status of the Ethernet services. This topic describes all thepossible RMON events on the OptiX RTN 620 and how to handle these events.

D.1 List of RMON Alarm EntriesRMON alarm entries refer to the table entries in the RMON alarm group.

D.2 List of RMON Performance EntriesRMON performance entries refer to the table entries in the RMON statistics group or historygroup.

D.3 RMON Alarm Clearance ReferenceThis topic describes the RMON events of the OptiX RTN 620 and how to handle these events.

OptiX RTN 620 Radio Transmission SystemMaintenance Guide D RMON Event Reference


D-1

D.1 List of RMON Alarm EntriesRMON alarm entries refer to the table entries in the RMON alarm group.

Table D-1 List of RMON alarm entries

Alarm Name Description Source

Dropevent Number of packet loss eventsexceeding the threshold

EMS6, EFT4, IFH2, EFP6

UndersizePkts Number of undersized packetsexceeding the threshold

OversizePkts Number of oversized packetsexceeding the threshold

Fragments Number of fragment packetsexceeding the threshold

EMS6, EFT4, EFP6

Jabbers Number of jabber packets exceedingthe threshold

FCSErrors Number of packets with FCS errorsexceeding the threshold

D.2 List of RMON Performance EntriesRMON performance entries refer to the table entries in the RMON statistics group or historygroup.

Table D-2 List of RMON performance entries

CategoryofPerformanceEntries

Name of a Performance Entry Source

Basicperformance

Packets received (packets) EMS6, EFT4, IFH2, EFP6

Packets received (64 bytes in length)(packets)

Packets received (65-127 bytes inlength) (packets)


D RMON Event ReferenceOptiX RTN 620 Radio Transmission System

Maintenance Guide

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

Issue 04 (2010-10-30)






Bytes received (bytes)

Oversized packets received (packets)

Undersized packets received(packets)

Multicast packets received (packets)

Broadcast packets received (packets)

Undersized error packets received(packets)

IFH2, EFP6

Oversized error packets received(packets)

EMS6, EFT4, EFP6

Packet loss events EMS6, EFT4, IFH2

Fragments received (packets) EMS6, EFT4,EFP6

Collisions (times) EMS6, EFT4

FCS and alignment error packets(packets)

EFT4, EFP6

Extendedperformance

Packets transmitted (64 bytes inlength) (packets)

EMS6, EFT4, IFH2, EFP6

Packets transmitted (65-127 bytes inlength) (packets)



Packets transmitted (512-1023 bytesin length) (packets)

Packets transmitted (1024-1518 bytesin length) (packets)



D-3



Packets received and transmitted (64bytes in length) (packets)

Packets received and transmitted(65-127 bytes in length) (packets)





Unicast packets transmitted (packets)

Pause frames received (frames)

Pause frames transmitted (frames)

FCS error frames (frames)

Oversized packets transmitted(packets)

Packets transmitted (packets)

Bytes transmitted (bytes)

Packets received (1519 bytes to theMTU in length) (packets)

IFH2

Packets transmitted (1519 bytes to theMTU in length) (packets)

Packets received and transmitted(1519 bytes to the MTU in length)(packets)

Transmitting packet loss events(packets)

Unicast packets received (packets) EMS6, EFT4, EFP6

Multicast packets transmitted(packets)


Maintenance Guide


Issue 04 (2010-10-30)



Broadcast packets transmitted(packets)

Rate of good full-frame bytes received(bytes/second)

Rate of good full-frame bytestransmitted (bytes/second)

Good full-frame bytes received(bytes)

Good full-frame bytes transmitted(bytes)

Control frames received (frame) EMS6, EFT4

Control frames transmitted (frame) EMS6, EFT4, EFP6

Alignment error frames (frame) EMS6, EFT4, EFP6

Control packets transmitted (packets) EFP6

Frames properly transmitted after onlyone collision (frame)

EMS6, EFT4

Frames properly transmitted aftermultiple collisions (frame)

Late collisions (times)

Frames unsuccessfully transmittedafter successive collisions (frame)

Delayed frames (frame)

VCGperformance

Packets received (packets) EMS6, EFP6

Packets transmitted (packets)

Good packets received (packets)

Good packets transmitted (packets)

Rate of good full-frame bytes received(bytes/second)

Rate of good full-frame bytestransmitted (bytes/second)

Octects Received(octets)

Octects Transmitted(octets)



D-5

NOTE

The ports of the EMS6, EFP6, EFT4, and IFH2 boards support the basic performance and the extendedperformance. The VCTRUNK of the EMS6 and EFP6 board supports the VCG performance. The VCTRUNKof the EFT4 board does not support RMON.

D.3 RMON Alarm Clearance ReferenceThis topic describes the RMON events of the OptiX RTN 620 and how to handle these events.

D.3.1 DropEvent

D.3.2 UndersizePkts

D.3.3 OversizePkts

D.3.4 Fragments

D.3.5 Jabbers

D.3.6 FCSErrors

D.3.1 DropEvent

Description

DropEvent indicates the number of events that packet loss occurs due to resource deficiency.An RMON threshold-crossing event is reported when the number of packet loss events is higherthan the upper threshold or lower than the lower threshold.

Impact on System

When packet loss occurs frequently, services are affected and the system is affected seriously.Therefore, you must rectify the fault immediately.

Possible Causes

This performance event indicates packet loss due to the full MAC buffer, FIFO overflow, flowcontrol, or backward pressure.

l The lower threshold is not set to a non-zero value.l The local data board is faulty.

Procedure

Step 1 Rectify the fault according to the specific performance event.

If... Then...

The number of packet loss events is lower than the lowerthreshold

Change the lower threshold to 0.


Maintenance Guide


Issue 04 (2010-10-30)

If... Then...

The number of packet loss events is higher than theupper threshold


Step 2 Replace the board that reports an alarm at the local end. Clear the alarm according to the typeof the board.

If... Then...

The alarm is reported by an IF board See 6.7 Replacing the IF Board.

The alarm is reported by an Ethernetboard

See 6.6 Replacing the Ethernet ServiceProcessing Board.

----End

Relevant InformationAll the RMON performance events are threshold-crossing events. That is, you can check whetherthe count of RMON performance events in a sampling period exceeds the specified threshold.You can set the sampling period, which is defaulted to 10 seconds.

D.3.2 UndersizePkts

DescriptionUndersizePkts indicates that an RMON threshold-crossing event is reported when the numberof packets that are shorter than 64 bytes and are received on the line side crosses the presetthreshold.

Impact on SystemThe data frames whose length is beyond the specific range are discarded. As a result, the systemservices are affected.

Possible Causes1. The length of a data frame that is received by the board is shorter than 64 bytes.2. The hardware of a local board is faulty.

Procedure

Step 1 Check whether the opposite equipment transmits a packet that is shorter than 64 bytes.

If... Then...

The opposite equipment transmits a packet that isshorter than 64 bytes

Rectify the fault on the opposite NE.

The opposite end does not transmit a packet that isshorter than 64 bytes





D-7

If... Then...




----End

Relevant Informationl The length range of the data frames that are processed by each type of board is different.

The length of the data frames transmitted by the opposite end is within the normal range,but it may be beyond the length range of the data frames that can be processed by the localend.

l Undersized frames may be relevant to services. The opposite equipment may change thelength of data frames by an operation such as encapsulation. As a result, a downstreamnode considers the data frames as undersized frames.

D.3.3 OversizePkts

DescriptionOversizePkts indicates that an RMON threshold-crossing event is reported when the number ofpackets that are longer than the MTU specified for the port and are received on the line sidecrosses the preset threshold.

Impact on SystemIf the length of a data frame received at a port is longer than the preset maximum frame length,the data frame is discarded and thus the system services are affected.

Possible Causes1. The length of an oversized frame configured for a board is shorter than the length of a frame

that is received by the board.2. The hardware of the local board is faulty.

ProcedureStep 1 Check whether the opposite equipment transmits a frame that is longer than the maximum frame

of the local equipment.

If... Then...

The opposite equipment transmits a framethat is longer than the maximum framelength set for the local equipment

Notify the opposite equipment that the lengthof transmitted frames is changed.

The opposite equipment does not transmita frame that is longer than the maximumframe length set for the local equipment




Maintenance Guide


Issue 04 (2010-10-30)

If... Then...




----End

Relevant Informationl The length range of the data frames that are processed by each type of board is different.

The length of the data frames transmitted by the opposite end is within the normal range,but it may be beyond the length range of the data frames that can be processed by the localend.

l Oversized frames may be relevant to services. The opposite equipment may change thelength of data frames by an operation such as encapsulation. As a result, a downstreamnode considers the data frames as oversized frames.

D.3.4 Fragments

DescriptionFragments 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 thespecified upper threshold.

Impact on SystemData transmission is delayed or packet loss occurs.

Possible Causesl The working modes of the ports on the equipment at both ends are different from each

other.l The hardware of the local board is faulty.

Procedure

Step 1 Check whether the working modes of the ports on the equipment at both ends are the same.

If... Then...

The working modes are the same Go to the next step.

The working modes are different fromeach other

Change the working mode of the port on thelocal equipment to ensure that the workingmodes of the ports on the equipment at bothends are the same.

Step 2 Replace the board that reports an alarm at the local end. For details, see 6.6 Replacing theEthernet Service Processing Board.

----End



D-9

D.3.5 Jabbers

Description

Jabbers indicates that an RMON threshold-crossing event is reported when the received packetsare longer than 1518 bytes and have FCS or alignment errors.

Impact on System

Data transmission is delayed or packet loss occurs.


other.

l The hardware of the local board is faulty.

Procedure

Step 1 Check whether the working modes of the ports on the equipment at both ends are the same.

If... Then...

The working modes are the same Go to the next step.

The working modes are different fromeach other

Change the working mode of the port on thelocal equipment to ensure that the workingmodes of the ports on the equipment at bothends are the same.


----End

D.3.6 FCSErrors

Description

FCSErrors indicates that the number of Ethernet data frames that contain FCS check errors(excluding the oversized and undersized frames) and are received by the local end exceeds thespecified threshold. FCSErrors includes FCSErrOv and FCSErrUd. FCSErrOv indicates that thenumber of Ethernet data frames that contain FCS check errors is higher than the upper threshold,and FCSErrUd indicates the number of Ethernet data frames that contain FCS check errors islower than the lower threshold.

Impact on System

Most boards discard the packets of FCS check errors. The system services are interrupted in theworst case.


Maintenance Guide


Issue 04 (2010-10-30)


other. For example, the port at one end works in half-duplex mode, and the port at the otherend works in half-duplex mode.

l The transmission line is of the poor quality and bit errors exist.l The hardware of the local board is faulty.

Procedure

Step 1 Rectify the fault based on the alarm parameters.

If... Then...

The FCSErrUd performance event occurs Change the lower threshold to 0.

The FCSErrOv performance event occurs Go to the next step.

Step 2 If the FCSErrOv performance event occurs, on the NMS, check whether the working modes ofthe ports on the equipment at both ends are the same.

If... Then...

The ports on the equipment at both ends aredifferent from each other

Change the working modes of the ports on theequipment at both ends to ensure that they arethe same.

The ports on the equipment at both ends arethe same



----End

Relevant InformationAll the RMON performance events are threshold-crossing events. That is, you can check whetherthe count of RMON performance events in a sampling period exceeds the specified threshold.You can set the sampling period, which is defaulted to 10 seconds.



D-11

E Alarm Management

Alarm management of the OptiX RTN 620 is classified into NE alarm management and boardalarm management.

E.1 NE Alarm ManagementThe NE alarm management function set by a user is applicable to all the boards on an NE.

E.2 Board Alarm ManagementThe board alarm management function is valid for only a board on which a user configures thisfunction.

OptiX RTN 620 Radio Transmission SystemMaintenance Guide E Alarm Management


E-1

E.1 NE Alarm ManagementThe NE alarm management function set by a user is applicable to all the boards on an NE.

The NE alarm management function of the OptiX RTN 620 includes:

l Sets the method for saving an alarm.

l Sets the delay of an alarm.

l Sets the reversion mode of an alarm.

For details about these functions, see the manuals or online Help of the NMS.

E.2 Board Alarm ManagementThe board alarm management function is valid for only a board on which a user configures thisfunction.

E.2.1 Setting the Alarm SeverityAlarms are classified into four severity levels: critical, major, minor, and warning. Themaintenance personnel can change the alarm severity by using the NMS.

E.2.2 Alarm SuppressionA board detects only the alarms whose Alarm Monitoring is set to Yes. If the alarms need notbe monitored, the maintenance personnel can set alarm suppression.

E.2.3 Alarm Auto-ReportIf Alarm Auto-Report is set to Reported, all the detected alarms are reported immediately tothe NMS. If Alarm Auto-Report is set to Not Report, the alarms are reported only when alarmquery is performed on the NMS. The maintenance personnel can change the setting as requiredon the NMS.

E.2.4 Alarm ReversionIf a port is not configured with a service, certain alarms may be reported. To filter the alarmsthat are not concerned, set these alarms to be reversed. In this manner, the alarm status at thisport is contrary to the actual status. That is, the status is displayed to be normal when an alarmis actually reported.

E.2.5 Setting of the Bit Error Alarm ThresholdWhen the number of bit errors detected by a board exceeds a specified value, the board generatesa bit error alarm. This specified value is the bit error alarm threshold, and the setting of thisthreshold is supported by all the bit error threshold-crossing and degrading alarms on the OptiXRTN 620.

E.2.6 AIS InsertionAIS insertion can be set for certain alarms reported on a board. When a board detects the alarms,it inserts all 1s into the lower level service signal to indicate the opposite end that the servicesignal is unavailable.

E.2.7 UNEQ InsertionWhen a board detects that the service path is not in use or that the LOS alarm is generated, theboard inserts all 0s into the service signal to notify the opposite end that the service signal isunavailable.

E Alarm ManagementOptiX RTN 620 Radio Transmission System

Maintenance Guide

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

Issue 04 (2010-10-30)

E.2.1 Setting the Alarm SeverityAlarms are classified into four severity levels: critical, major, minor, and warning. Themaintenance personnel can change the alarm severity by using the NMS.

This function is supported by all the boards.

E.2.2 Alarm SuppressionA board detects only the alarms whose Alarm Monitoring is set to Yes. If the alarms need notbe monitored, the maintenance personnel can set alarm suppression.


E.2.3 Alarm Auto-ReportIf Alarm Auto-Report is set to Reported, all the detected alarms are reported immediately tothe NMS. If Alarm Auto-Report is set to Not Report, the alarms are reported only when alarmquery is performed on the NMS. The maintenance personnel can change the setting as requiredon the NMS.


E.2.4 Alarm ReversionIf a port is not configured with a service, certain alarms may be reported. To filter the alarmsthat are not concerned, set these alarms to be reversed. In this manner, the alarm status at thisport is contrary to the actual status. That is, the status is displayed to be normal when an alarmis 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 changes automatically to the disabled status. That is, the alarmreversion changes to the non-revertive mode. Then, the alarm reporting status at the portis the same as the actual 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 implemented by the NE software. The alarm data is the same on the NEand the 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 on the basis of a port. Alarm reversion is supported by each port ofthe SD1, SL1, SDE, SLE, SL4, IF1A, IF1B, IFX, IF0A, IF0B, PH1, PO1, PD1, PL3, EFT4,and EFP6.

E.2.5 Setting of the Bit Error Alarm ThresholdWhen the number of bit errors detected by a board exceeds a specified value, the board generatesa bit error alarm. This specified value is the bit error alarm threshold, and the setting of thisthreshold is supported by all the bit error threshold-crossing and degrading alarms on the OptiXRTN 620.

Table E-1 Setting of the bit error alarm threshold

Alarm Name Default Alarm Threshold Applicable Board

B1_EXC 10-3 SD1, SL1, SDE, SLE, IF1A,IF1B, IF0A, IF0B, IFX, andSL4B1_SD 10-6

B2_EXC 10-3 SD1, SL1, SDE, SLE, IF1A,IF1B, IFX, and SL4

B2_SD 10-6

B3_EXC 10-3 SD1, SL1, SDE, SLE, IF1A,IF1B, IFX, SL4, and PL3

B3_SD 10-6

BIP_EXC 10-3 PO1, PH1, EFT4, EMS6,EFP6, PD1, IF0A, and IF0B

BIP_SD 10-6

B3_EXC_VC3 10-3 EFT4 and EMS6

B3_SD_VC3 10-6

MW_BER_EXC 10-3 IFH2

MW_BER_SD 10-6

E.2.6 AIS InsertionAIS insertion can be set for certain alarms reported on a board. When a board detects the alarms,it inserts all 1s into the lower level service signal to indicate the opposite end that the servicesignal is unavailable.


Maintenance Guide


Issue 04 (2010-10-30)

Table E-2 Setting of the AIS insertion

Trigger Condition Default Value Applicable Board

B1_EXC Enabled SD1, SL1, SDE, SLE, IF1A,IF1B, IFX, and SL4

Disabled IF0A and IF0B

B2_SD Disabled SD1, SL1, SDE, SLE, IF1A,IF1B, and IFX

Enabled SL4

B2_EXC Disabled SD1, SL1, SDE, SLE, IF1A,IF1B, IFX, and SL4

HP_LOM Enabled

HP_TIM Disabled

HP_SLM Disabled

HP_UNEQ Disabled

B3_EXC Enabled SD1, SL1, SDE, SLE, IF1A,IF1B, IFX, PL3, and SL4

B3_SD Disabled

B1_SD Disabled SD1, SL1, SDE, SLE, IF1A,IF1B, IFX, IF0A, IF0B, andSL4

LP_TIM Disabled PH1, PO1, PD1, and PL3

LP_UNEQ Disabled

LP_SLM Disabled

T_ALOS Enabled

BIP_EXC Disabled

BIP_SD Disabled

P_LOS Enabled PL3

MW_BER_EXC Enabled IFH2

MW_BER_SD Forbidden



E-5

NOTE

l When the SD1, SL1, SDE, SLE, or SL4 board detects the R_LOS, R_LOF, MS_AIS, AU_AIS, orAU_LOP alarm, this board forcibly inserts the AIS.

l When the IFX, IF1A, or IF1B board detects the MW_LOF, R_LOS, R_LOF, MS_AIS, AU_AIS, orAU_LOP alarm, this board forcibly inserts the AIS.

l When the IF0A or IF0B board detects the MW_LOF, R_LOS, or R_LOF alarm, this board forciblyinserts the AIS.

l When the IFH2 board detects the MW_BER_EXC alarm, this board forcibly inserts the AIS.

E.2.7 UNEQ InsertionWhen a board detects that the service path is not in use or that the LOS alarm is generated, theboard inserts all 0s into the service signal to notify the opposite end that the service signal isunavailable.

Table E-3 Setting of the UNEQ insertion

Trigger Condition Default Value Applicable Board

T_ALOS Disabled PH1, PO1, PD1, PL3

Service path being not in use Disabled

P_LOS Disabled PL3


Maintenance Guide


Issue 04 (2010-10-30)

F Performance Event Management

Performance event management of the OptiX RTN 620 is classified into NE performance eventmanagement and board performance event management.

F.1 NE Performance Event ManagementThe NE performance event management function set by a user is applicable to all the boards onan NE.

F.2 Board Performance Event ManagementThe performance event management function is valid for only a board on which a user configuresthis function.

OptiX RTN 620 Radio Transmission SystemMaintenance Guide F Performance Event Management


F-1

F.1 NE Performance Event ManagementThe NE performance event management function set by a user is applicable to all the boards onan NE.

The NE performance event management function supported by OptiX RTN 620 includes:

l Sets the monitoring of NE performance eventsl Sets the start/end time of performance eventsl Enables/Disables the reporting of UAT events

For details about these functions, see the manuals or online Help of the NMS.

F.2 Board Performance Event ManagementThe performance event management function is valid for only a board on which a user configuresthis function.

Table F-1 Board performance event management function

Function Applicable Board

Sets 15-minute/24-hourperformancemonitoring.

SD1, SL1, SDE, SLE, SL4, IFX, IF0A, IF0B, IF1A, IF1B, IFH2,PO1, PH1, PD1, PL3, EFT4, EMS6, EFP6, PXC, ODU, and SCC

Sets 15-minute/24-hourperformance event auto-reporting.

SD1, SL1, SDE, SLE, SL4, IFX, IF0A, IF0B, IF1A, IF1B, IFH2,PO1, PH1, PD1, PL3, EFT4, EMS6, EFP6, PXC, ODU, and SCC

Sets performancethresholds.

SD1, SL1, SDE, SLE, SL4, IFX, IF0A, IF0B, IF1A, IF1B, IFH2,PO1, PH1, PD1, PL3, EFT4, EMS6, and EFP6

Resets the performanceregister.

SD1, SL1, SDE, SLE, SL4, IFX, IF0A, IF0B, IF1A, IF1B, IFH2,PO1, PH1, PD1, PL3, EFT4, EMS6, EFP6, and ODU

Generates performancethreshold-crossingalarms.


Monitors UAT events. SD1, SL1, SDE, SLE, SL4, IFX, IF0A, IF0B, IF1A, IF1B, IFH2,PO1, PH1, PD1, PL3, EFT4, EMS6, and EFP6

Monitors CSESperformance events.


F Performance Event ManagementOptiX RTN 620 Radio Transmission System

Maintenance Guide

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

Issue 04 (2010-10-30)

G Alarm Suppression Relationship

Table G-1 Suppression relationship between intra-board alarms

Alarm Identifier Identifier of the Suppressed Alarm

MW_LOF R_LOS, R_LOF, R_LOC,MW_FEC_UNCOR, MW_RDI, andMW_LIM

R_LOS and R_LOC R_LOF, J0_MM, B1_EXC, B1_SD,MS_AIS, MS_RDI, B2_EXC, B2_SD,MS_REI, AU_AIS, AU_LOP, HP_TIM,HP_UNEQ, HP_SLM, HP_RDI, B3_EXC,B3_SD, HP_LOM, HP_REI, MW_RDI,and MW_LIM

R_LOF J0_MM, B1_EXC, B1_SD, MS_AIS,MS_RDI, B2_EXC, B2_SD, MS_REI,AU_AIS, AU_LOP, HP_TIM, HP_UNEQ,HP_SLM, HP_RDI, B3_EXC, B3_SD,HP_LOM, HP_REI, MW_RDI, andMW_LIM

MS_AIS B2_SD, MS_REI, MS_RDI, AU_AIS,AU_LOP, HP_TIM, HP_UNEQ,HP_SLM, HP_RDI, B3_EXC, B3_SD,HP_LOM, and HP_REI

MS_RDI MS_REI

AU_AIS and AU_LOP B3_EXC, B3_SD, HP_TIM, HP_SLM,HP_UNEQ, HP_RDI, HP_LOM, andHP_REI

HP_UNEQ HP_TIM and HP_RDI

HP_TIMa HP_SLM, HP_LOM, B3_EXC, and B3_SD

HP_TIMa HP_LOM

HP_RDI HP_REI

OptiX RTN 620 Radio Transmission SystemMaintenance Guide G Alarm Suppression Relationship


G-1


LP_UNEQ LP_TIM, LP_RDI, and LP_SLM

LP_TIM LP_RDI

B1_EXC B1_SD

B2_EXC B2_SD

B3_EXC B3_SD

TU_AIS P_AIS, LP_TIM, LP_SIZE_ERR,LP_UNEQ, LP_RDI, LP_REI, LP_RFI,LP_R_FIFO, BIP_EXC, BIP_SD,LP_SLM, B3_EXC, B3_SD, andC2_VCAIS

TU_LOP TU_AIS, LP_TIM, LP_SIZE_ERR,LP_UNEQ, LP_RDI, LP_REI, LP_RFI,LP_R_FIFO, BIP_EXC, BIP_SD,LP_SLM, B3_EXC, B3_SD, andC2_VCAIS

T_ALOS E1_LOS and UP_E1_AIS

E1_LOS UP_E1_AIS

BIP_EXC BIP_SD

P_LOS A_LOC and P_AIS

C2_VCAIS LP_SLM

NOTE

a: The alarm suppression relationship is valid only when the AIS insertion function is enabled.

Table G-2 Suppression relationship between inter-board alarms


R_LOS, R_LOC, MS_AIS, AU_AIS, andAU_LOP

TU_AIS

MW_LOF and MW_LIM TU_AIS

G Alarm Suppression RelationshipOptiX RTN 620 Radio Transmission System

Maintenance Guide

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

Issue 04 (2010-10-30)

H Glossary

Terms are listed in an alphabetical order.

H.1 0-9

H.2 A-E

H.3 F-J

H.4 K-O

H.5 P-T

H.6 U-Z

OptiX RTN 620 Radio Transmission SystemMaintenance Guide H Glossary


H-1

H.1 0-91+1 protection An architecture that has one normal traffic signal, one working SNC/trail, one protection

SNC/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-E

A

ABR See Available Bit Rate

ACAP See adjacent channel alternate polarization

Access Control List Access Control List (ACL) is a list of IP address. The addresses listed in the ACL areused for authentication. If the ACL for the user is not null, it indicates that the addresswhere the user logged in is contained in the list.

ACL See Access Control List

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.

H GlossaryOptiX RTN 620 Radio Transmission System

Maintenance Guide

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

Issue 04 (2010-10-30)

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

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.

AF See Assured Forwarding

AGC See Automatic Gain Control

aggregation A collection of objects that makes a whole. An aggregation can be a concrete orconceptual set of whole-part relationships among objects.

AIS See Alarm Indication Signal

Alarm automaticreport

When an alarm is generated on the device side, the alarm is reported to the N2000. Then,an alarm panel prompts and the user can view the details of the alarm.

alarm cascading The shunt-wound output of the alarm signals of several subracks or cabinets.

Alarm Filtering An NE reports the detected alarm to the element management system (EMS). Based onthe filter state of the alarm, the EMS determines whether to display or save the alarminformation. If the filter state of an alarm is set to Filter, the alarm is not displayed orstored on the EMS. The alarm, however, is still monitored by the NE.

Alarm IndicationSignal

A code sent downstream in a digital network as an indication that an upstream failurehas been detected and alarmed. It is associated with multiple transport layers. Note: SeeITU-T Rec. G.707/Y.1322 for specific AIS signals.

Alarm suppression A function used not to monitor alarms for a specific object, which may be thenetworkwide equipment, a specific NE, a specific board and even a specific functionmodule of a specific board.

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

Assured Forwarding Assured Forwarding (AF) is one of the four per-hop behaviors (PHB) defined by theDiff-Serv workgroup of IETF. AF is suitable for certain key data services that requireassured bandwidth and short delay. For traffic within the limit, AF assures quality inforwarding. For traffic that exceeds the limit, AF degrades the service class and continuesto forward the traffic instead of discarding the packets.

AsynchronousTransfer Mode

A data transfer technology based on cell, in which packets allocation relies on channeldemand. It supports fast packet switching to achieve efficient utilization of networkresources. The size of a cell is 53 bytes, which consist of 48-byte payload and 5-byteheader.

ATM See Asynchronous Transfer Mode

ATM PVC ATM Permanent Virtual Circuit



H-3

ATPC See automatic transmit power control

attenuator A device used to increase the attenuation of an Optical Fibre Link. Generally used toensure that the signal at the receive end is not too strong.

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

Available Bit Rate A kind of service categories defined by the ATM forum. ABR only provides possibleforwarding service and applies to the connections that does not require the real-timequality. It does not provide any guarantee in terms of cell loss or delay.

B

Backward DefectIndication

When detecting a defect, the sink node of a LSP uses backward defect indication (BDI)to inform the upstream end of the LSP of a downstream defect along the return path.

bandwidth A range of transmission frequencies that a transmission line or channel can carry in anetwork. In fact, it is the difference between the highest and lowest frequencies thetransmission line or channel. The greater the bandwidth, the faster the data transfer rate.

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.

Base TransceiverStation

A Base Transceiver Station terminates the radio interface. It allows transmission of trafficand signaling across the air interface. The BTS includes the baseband processing, radioequipment, and the antenna.

BDI See Backward Defect Indication

BE See best effort

BER See Bit Error Rate

best effort A kind of PHB (Per-Hop-Behavior). In the forwarding process of a DS domain, the trafficof this PHB type features reachability but the DS node does not guarantee the forwardingquality.

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.


Maintenance Guide


Issue 04 (2010-10-30)

blank filler panel A piece of board to cover vacant slots, to keep the frame away from dirt, to keep properairflow inside the frame, and to beautify the frame appearance.

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.

Broadcast A means of delivering information to all members in a network. The broadcast range isdetermined by the broadcast address.

BSC See Base Station Controller

BTS See Base Transceiver Station

Buffer A storage area used for handling data in transit. Buffers are used in internetworking tocompensate for differences in processing speed between network devices. Bursts of datacan be stored in buffers until they can be handled by slower processing devices.

C

C-VLAN Customer VLAN

Cable distribution plate A component which is used to arrange the cables in order.

cable ladder (1) A cable ladder is a frame which supports electrical cables. (2) Two metal cablesusually made of stainless steel with rungs of lightweight metal tubing such as aluminum,six or eight inches wide spaced about eighteen inches apart. It can be rolled into a compactlightweight bundle for transport ease.

cable tie The tape used to bind the cables.

cabling trough The trough which is used for cable routing in the cabinet.

captive nut Captive nuts (or as they are more correctly named, 'tee nuts') have a range of uses butare more commonly used in the hobby for engine fixing (securing engine mounts to thefirewall), wing fixings, and undercarriage fixing.

CAR See committed access rate

CBR See Constant Bit Rate

CCC See Circuit Cross Connect

CCDP See Co-Channel Dual Polarization

CCM See continuity check message

CE See Customer Edge

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.

CES See Circuit Emulation Service

CF See compact flash

CGMP Cisco Group Management Protocol



H-5

CIR See Committed Information Rate

Circuit Cross Connect An implementation of MPLS L2VPN through the static configuration of labels.

Circuit EmulationService

A function with which the E1/T1 data can be transmitted through ATM networks. At thetransmission end, the interface module packs timeslot data into ATM cells. These ATMcells are sent to the reception end through the ATM network. At the reception end, theinterface module re-assigns the data in these ATM cells to E1/T1 timeslots. The CEStechnology guarantees that the data in E1/T1 timeslots can be recovered to the originalsequence at the reception end.

CIST See Common and Internal Spanning Tree

CIST root A switch of the highest priority is elected as the root in an MSTP network.

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.

Clock tracing The method to keep the time on each node being synchronized with a clock source in anetwork.

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.

Coarse WavelengthDivision Multiplexing

A signal transmission technology that multiplexes widely-spaced optical channels intothe same fiber. CWDM widely spaces wavelengths at a spacing of several nm. CWDMdoes not support optical amplifiers and is applied in short-distance chain networking.

Colored packet A packet whose priority is determined by defined colors.

Combined cabinet Two or multiple BTS cabinets of the same type are combined to serve as one BTS.

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.

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.

Concatenation A process that combines multiple virtual containers. The combined capacities can beused a single capacity. The concatenation also keeps the integrity of bit sequence.

connecting plate forcombining cabinets

A plate that connects two adjacent cabinet together at the cabinet top for fixing.


Maintenance Guide


Issue 04 (2010-10-30)

Connectivity Check Ethernet CFM can detect the connectivity between MEPs. The detection is achieved byeach MEP transmitting a Continuity Check Message (CCM) periodically. This detectionis called CC detection.

Constant Bit Rate constant bit rate. A kind of service categories defined by the ATM forum. CBR transferscells based on the constant bandwidth. It is applicable to service connections that dependon precise clocking to ensure undistorted transmission.

Constraint ShortestPath First

An extension of shortest path algorithms like OSPF and IS-IS. The path computed usingCSPF is a shortest path fulfilling set of constrains. It simply means that it runs shortestpath algorithm after pruning those links that violate a given set of constraints. Aconstraint could be minimum bandwidth required per link (also know as bandwidthguaranteed constraint), end-to-end delay, maximum number of link traversed etc. CSPFis widely used in MPLS Traffic Engineering. The routing using CSPF is known asConstraint Based Routing (CBR).

Constraint-basedRouted-LabelDistribution Protocol

An alternative to RSVP (Resource ReSerVation Protocol) in MPLS (MultiProtocolLabel Switching) networks. RSVP, which works at the IP (Internet Protocol) level, usesIP or UDP datagrams to communicate between LSR (Label Switched Routing) peers.RSVP does not require the maintenance of TCP (Transmission Control Protocol)sessions, although RSVP must assume responsibility for error control. CR-LDP isdesigned to facilitate the routing of LSPs (Label Switched Paths) through TCP sessionsbetween LSR peers through the communication of label distribution messages duringthe session.

continuity checkmessage

CCM is used to detect the link status.

corrugated tube A pipe which is used for fiber routing.

CoS See Class of Service

CPU See Central Processing Unit

CR-LDP See Constraint-based Routed-Label Distribution Protocol

CRC See Cyclic Redundancy Check

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.

CSPF See Constraint Shortest Path First

Customer Edge A part of BGP/MPLS IP VPN model. It provides interfaces for direct connection to theService Provider (SP) network. A CE can be a router, switch, or host.

CWDM See Coarse Wavelength Division Multiplexing

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.



H-7

D

Data Circuit-terminalEquipment

Also Data Communications Equipment (DCE) and Data Carrier Equipment (DCE). Thebasic function of a DCE is to convert data from one interface, such as a digital signal, toanother interface, such as an analog signal. One example of DCE is a modem.

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.

Datagram A kind of PDU which is used in Connectionless Network Protocol, such as IP datagram,UDP datagram.

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

DCE See Data Circuit-terminal Equipment

DCN See Data Communication Network

DDF See Digital Distribution Frame

DDN See Digital Data Network

DE See discard eligible

Detour LSP The LSP that is used to re-route traffic around a failure in one-to-one backup.

diamond-shaped nut A type of nut that is used to fasten the wiring frame to the cabinet.

Differentiated Services A service architecture that provides the end-to-end QoS function. It consists of a seriesof functional units implemented at the network nodes, including a small group of per-hop forwarding behaviors, packet classification functions, and traffic conditioningfunctions such as metering, marking, shaping and policing.

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.

DiffServ See Differentiated Services

Digital Data Network A high-quality data transport tunnel that combines the digital channel (such as fiberchannel, digital microwave channel, or satellite channel) and the cross multiplextechnology.


Maintenance Guide


Issue 04 (2010-10-30)

Digital DistributionFrame

A type of equipment used between the transmission equipment and the exchange withtransmission rate of 2 to 155 Mbit/s to provide the functions such as cables connection,cable patching, and test of loops that transmitting digital signals.

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.

discard eligible A bit in the frame relay header. It indicates the priority of a packet. If a node supportsthe FR QoS, the rate of the accessed FR packets is controlled. When the packet trafficexceeds the specified traffic, the DE value of the redundant packets is set to 1. In thecase of network congestion, the packets with DE value as 1 are discarded at the node.

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.

DS boundary node A DS node that connects one DS domain to a node either in another DS domain or in adomain that is not DS-capable.

DS domain In the DifferServ mechanism, the DS domain is a domain consisting of a group ofnetwork nodes that share the same service provisioning policy and same PHB. It providespoint-to-point QoS guarantees for services transmitted over this domain.

DS interior node A DS node located at the center of a DS domain. It is a non-DS boundary node.

DS node A DS-compliant node, which is subdivided into DS boundary node and ID interior node.

DSCP See Differentiated Services Code Point

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-AGGR Ethernet-Aggregation

E-LAN See Ethernet LAN

E-Tree See Ethernet-Tree

EBS See Excess Burst Size

ECC See Embedded Control Channel

EF See Expedited Forwarding

EFM See Ethernet in the First mile

Electro MagneticInterference

Any electromagnetic disturbance that interrupts, obstructs, or otherwise degrades orlimits the effective performance of electronics/electrical equipment.



H-9

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]

ElectroStatic Discharge The sudden and momentary electric current that flows between two objects at differentelectrical potentials caused by direct contact or induced by an electrostatic field.

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

Engineering label A mark on a cable, a subrack, or a cabinet for identification.

EPLn See Ethernet Private LAN

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

ESD See ElectroStatic Discharge

ESD jack Electrostatic discharge jack. A hole in the cabinet or shelf, which connect the shelf orcabinet to the insertion of ESD wrist strap.

ETH-CC Ethernet Continuity Check

ETH-LB Ethernet Loopback

ETH-LT Ethernet Link Trace

Ethernet A technology complemented in LAN. It adopts Carrier Sense Multiple Access/CollisionDetection. The speed of an Ethernet interface can be 10 Mbit/s, 100 Mbit/s, 1000 Mbit/s or 10000 Mbit/s. The Ethernet network features high reliability and easy maintaining..

Ethernet in the Firstmile

Last mile access from the broadband device to the user community. The EFM takes theadvantages of the SHDSL.bis technology and the Ethernet technology. The EFMprovides both the traditional voice service and internet access service of high speed. Inaddition, it meets the users' requirements on high definition television system (HDTV)and Video On Demand (VOD).

Ethernet LAN Ethernet LAN. A L2VPN service type that is provided for the user Ethernet in differentdomains over the PSN network. For the user Ethernet, the entire PSN network serves asa Layer 2 switch.

Ethernet Private LAN Both a LAN service and a private service. Transport bandwidth is never shared betweendifferent customers.

ethernet ringprotection switching

protection switching mechanisms for ETH layer Ethernet ring topologies.

Ethernet VirtualPrivate LAN

A service that is both a LAN service and a virtual private service.

Ethernet-Tree etherenet tree. An Ethernet service type that is based on a Point-to-multipoint EthernetVirtual Connection.


Maintenance Guide


Issue 04 (2010-10-30)

ETS European Telecommunication Standards

ETSI See European Telecommunications Standards Institute

ETSI 300mm cabinet A cabinet which is 600mm in width and 300mm in depth, compliant with the standardsof the ETSI.

EuropeanTelecommunicationsStandards Institute

A standards-setting body in Europe. Also the standards body responsible for GSM.

EVPL Ethernet Virtual Private Line

EVPLn See Ethernet Virtual Private LAN

Excess Burst Size excess burst size. In the single rate three color marker (srTCM) mode, the traffic controlis realized by the token buckets C and E. Excess burst size is a parameter used to definethe capacity of token bucket E, that is, the maximum burst IP packet size when theinformation is transferred at the committed information rate. This parameter must belarger than 0. It is recommended that this parameter should be not less than the maximumlength of the IP packet that might be forwarded.

Exercise Switching An operation to check if the protection switching protocol functions normally. Theprotection switching is not really performed.

Expedited Forwarding Expedited Forwarding (EF) is the highest order QoS in the Diff-Serv network. EF PHBis suitable for services that demand low packet loss ratio, short delay, and broadbandwidth. In all the cases, EF traffic can guarantee a transmission rate equal to or fasterthan the set rate. The DSCP value of EF PHB is "101110".

H.3 F-J

F

Failure If the fault persists long enough to consider the ability of an item with a required functionto be terminated. The item may be considered as having failed; a fault has now beendetected.

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

FDI See Forward Defect Indication

FE See Fast Ethernet

FEC See Forward Error Correction

FFD Fast Failure Detection

Fiber Connector A device installed at the end of a fiber, optical source or receive unit. It is used to couplethe optical wave to the fiber when connected to another device of the same type. Aconnector can either connect two fiber ends or connect a fiber end and a optical source(or a detector).



H-11

fiber patch cord A kind of fiber used for connections between the subrack and the ODF, and forconnections between subracks or inside a subrack.

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

Forced switch This function forces the service to switch from the working channel to the protectionchannel, with the service not to be restored automatically. This switch occurs regardlessof the state of the protection channels or boards, unless the protection channels or boardsare satisfying a higher priority bridge request.

Forward DefectIndication

Forward defect indication (FDI) is generated and traced forward to the sink node of theLSP by the node that first detects defects. It includes fields to indicate the nature of thedefect and its location. Its primary purpose is to suppress alarms being raised at affectedhigher level client LSPs and (in turn) their client layers.

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.

Forwarding plane Also referred to as the data plane. The forwarding plane is connection-oriented, and canbe used in Layer 2 networks such as an ATM network.

FPGA See Field Programmable Gate Array

Fragment Piece of a larger packet that has been broken down to smaller units.

Fragmentation Process of breaking a packet into smaller units when transmitting over a network mediumthat can not support the original size of the packet.

frame A frame, starting with a header, is a string of bytes with a specified length. Frame lengthis represented by the sampling circle or the total number of bytes sampled during a circle.A header comprises one or a number of bytes with pre-specified values. In other words,a header is a code segment that reflects the distribution (diagram) of the elements pre-specified by the sending and receiving parties.

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

Full duplex The system that can transmit information in both directions on a communication link.Onthe communication link, both parties can send and receive data at the same time.


Maintenance Guide


Issue 04 (2010-10-30)

G

gateway networkelement

A network element that is used for communication between the NE application layer andthe NM application layer

GCP See GMPLS control plan

GE See Gigabit Ethernet

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.

Global PositioningSystem

A global navigation satellite system. It provides reliable positioning, navigation, andtiming services to worldwide users .

GMPLS control plan The OptiX GMPLS control plan (GCP) is the ASON software developed by Huawei.The OptiX GCP applies to the OptiX OSN product series. By using this software, thetraditional network can evolve into the ASON network. The OptiX OSN product seriessupport the ASON features.

GNE See gateway network element

GPS See Global Positioning System

GR See Graceful Restart

Graceful Restart In IETF, protocols related to Internet Protocol/Multiprotocol Label Switching (IP/MPLS) such as Open Shortest Path First (OSPF), Intermediate System-IntermediateSystem (IS-IS), Border Gateway Protocol (BGP), Label Distribution Protocol (LDP),and Resource Reservation Protocol (RSVP) are extended to ensure that the forwardingis not interrupted when the system is restarted. This reduces the flapping of the protocolsat the control plane when the system performs the active/standby switchover. This seriesof standards is called Graceful Restart.

Graphical UserInterface

A visual computer enviroment that represents programs, files, and options with graphicalimages, such as icons, menus, and dialog boxes, on the screen.

ground resistance (electricity) Opposition of the earth to the flow of current through it; its value dependson the nature and moisture content of the soil, on the material, composition, and natureof connections to the earth, and on the electrolytic action present.

GTS See Generic traffic shaping

GUI See Graphical User Interface

guide rail Components to guide, position, and support plug-in boards.



H-13

H

H-QoS Hierarchical Quality of Service

HA See High Availability

half-duplex A transmitting mode in which a half-duplex system provides for communication in bothdirections, but only one direction at a time (not simultaneously). Typically, once a partybegins receiving a signal, it must wait for the transmitter to stop transmitting, beforereplying.

HDB3 High Density Bipolar Code 3

HDLC See High level Data Link Control procedure

High Availability The ability of a system to continuously perform its functions during a long period, whichmay exceeds the suggested working time of the independent components. You can obtainthe high availability (HA) by using the error tolerance method. Based on learning casesone by one, you must also clearly understand the limitations of the system that requiresan HA ability and the degree to which the ability can reach.

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).

High Speed DownlinkPacket Access

A modulating-demodulating algorithm put forward in 3GPP R5 to meet the requirementfor asymmetric uplink and downlink transmission of data services. It enables themaximum downlink data service rate to reach 14.4 Mbit/s without changing theWCDMA network topology.

Hold priority The priority of the tunnel with respect to holding resources, ranging from 0 (indicatesthe highest priority) to 7. It is used to determine whether the resources occupied by thetunnel can be preempted by other tunnels.

Hop A network connection between two distant nodes. For Internet operation a hop representsa small step on the route from one main computer to another.

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.

HP Higher Order Path

HSDPA See High Speed Downlink Packet Access

HSM Hitless Switch Mode

HTB High Tributary Bus

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


Maintenance Guide


Issue 04 (2010-10-30)

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

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.

IMA See Inverse Multiplexing over ATM

indoor unit The indoor unit of the split-structured radio equipment. It implements accessing,multiplexing/demultiplexing, and IF processing for services.

Inloop A method of looping the signals from the cross-connect unit back to the cross-connectunit.

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.

Interface board area The area for the interface boards on the subrack.

intermediate frequency The transitional frequency between the frequencies of a modulated signal and an RFsignal.

Intermediate System The basic unit in the IS-IS protocol used to transmit routing information and generateroutes.

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.

Internal Spanning Tree Internal spanning tree. A segment of CIST in a certain MST region. An IST is a specialMSTI whose ID is 0.

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.



H-15

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.

Inverse Multiplexingover ATM

Inverse Multiplexing over ATM. The ATM inverse multiplexing technique involvesinverse multiplexing and de-multiplexing of ATM cells in a cyclical fashion among linksgrouped to form a higher bandwidth logical link whose rate is approximately the sum ofthe link rates. This is referred to as an IMA group.

IP See Internet Protocol

IPv6 See Internet Protocol Version 6

IS-IS See Intermediate System to Intermediate System

ISO See International Organization for Standardization

IST See Internal Spanning Tree

ITU-T International Telecommunication Union - Telecommunication Standardization Sector

IVL Independence VLAN learning

J

Jitter Short waveform variations caused by vibration, voltage fluctuations, and control systeminstability.

H.4 K-O

L

L2VPN See Layer 2 virtual private network

Label Switched Path A sequence of hops (R0...Rn) in which a packet travels from R0 to Rn through labelswitching mechanisms. A label-switched path can be chosen dynamically, based onnormal routing mechanisms, or through configuration.

Label Switching Router The Label Switching Router (LSR) is the basic element of MPLS network. All LSRssupport the MPLS protocol. The LSR is composed of two parts: control unit andforwarding unit. The former is responsible for allocating the label, selecting the route,creating the label forwarding table, creating and removing the label switch path; the latterforwards the labels according to groups received in the label forwarding table.

LACP See Link Aggregation Control Protocol

LAG See link aggregation group

LAN See Local Area Network

LAPD Link Access Procedure on the D channel

LAPS Link Access Procedure-SDH


Maintenance Guide


Issue 04 (2010-10-30)

Laser A component that generates directional optical waves of narrow wavelengths. The laserlight has better coherence than ordinary light. The fiber system takes the semi-conductorlaser as the light source.

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.

Layer 2 virtual privatenetwork

A virtual private network realized in the packet switched (IP/MPLS) network by Layer2 switching technologies.

LB See Loopback

LCAS See Link Capacity Adjustment Scheme

LDPC Low-Density Parity Check code

line rate forwarding The line rate equals the maximum transmission rate capable on a given type of media.

Link AggregationControl Protocol

Link Aggregation Control Protocol (LACP) is part of an IEEE specification (802.3ad)that allows you to bundle several physical ports to form a single logical channel. LACPallows a switch to negotiate an automatic bundle by sending LACP packets to the peer.

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.

Link Protection Protection provided by the bypass tunnel for the link on the working tunnel. The link isa downstream link adjacent to the PLR. When the PLR fails to provide node protection,the link protection should be provided.

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).

Locked switching When the switching condition is satisfied, this function disables the service from beingswitched from the working channel to the protection channel. When the service has beenswitched, the function enables the service to be restored from the protection channel tothe working channel.

LOF See Loss Of Frame

LOM Loss Of Multiframe

Loopback A troubleshooting technique that returns a transmitted signal to its source so that thesignal or message can be analyzed for errors.

LOP See Loss Of Pointer

LOS See Loss Of Signal

Loss Of Frame A condition at the receiver or a maintenance signal transmitted in the PHY overheadindicating that the receiving equipment has lost frame delineation. This is used to monitorthe performance of the PHY layer.



H-17

Loss Of Pointer Loss of Pointer: A condition at the receiver or a maintenance signal transmitted in thePHY overhead indicating that the receiving equipment has lost the pointer to the start ofcell in the payload. This is used to monitor the performance of the PHY layer.

Loss Of Signal Loss of signal (LOS) indicates that there are no transitions occurring in the receivedsignal.

Lower subrack The subrack close to the bottom of the cabinet when a cabinet contains several subracks.

LP Lower Order Path

LPT Link State Path Through

LSP See Label Switched Path

LSR See Label Switching Router

M

MA See Maintenance Association

MAC See Medium Access Control

MAC See Media 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.

Maintenanceassociation End Point

A MEP is an actively managed CFM Entity, associated with a specific DSAP of a ServiceInstance, which can generate and receive CFM frames and track any responses. It is anend point of a single Maintenance Association, and terminates a separate MaintenanceEntity for each of the other MEPs in the same Maintenance Association.

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.

Manual switching A protection switching. When the protection path is normal and there is no request of ahigher level switching, the service is manually switched from the working path to theprotection path, to test whether the network still has the protection capability.

Maximum TransferUnit

The MTU (Maximum Transmission Unit) is the size of the largest datagram that can besent over a network.

MBS Maximum Burst Size

MCF See Message Communication Function

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.


Maintenance Guide


Issue 04 (2010-10-30)

Media Access Control A protocol at the media access control sublayer. The protocol is at the lower part of thedata link layer in the OSI model and is mainly responsible for controlling and connectingthe physical media at the physical layer. When transmitting data, the MAC protocolchecks whether to be able to transmit data. If the data can be transmitted, certain controlinformation is added to the data, and then the data and the control information aretransmitted in a specified format to the physical layer. When receiving data, the MACprotocol checks whether the information is correct and whether the data is transmittedcorrectly. If the information is correct and the data is transmitted correctly, the controlinformation is removed from the data and then the data is transmitted to the LLC layer.

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 See Maintenance association End Point

MessageCommunicationFunction

The MCF is composed of a protocol stack that allows exchange of managementinformation with their prs .

MIB See Management Information Base

MIP Maintenance Intermediate Point

MLPPP See Multi-link Point to Point Protocol

mount angle An L-shape steel sheet. One side is fixed on the front panel with screws, and the otherside is fixed on the installation hole with screws. On both sides of a rack, there is an L-shaped metal fastener. This ensures that internal components are closely connected withthe rack. Normally, an internal component is installed with two mount angles.

MP See Maintenance Point

MPID Maintenance Point Identification

MPLS See Multi-Protocol Label Switch

MPLS L2VPN The MPLS L2VPN provides the Layer 2 VPN service based on an MPLS network.Inthis case, on a uniform MPLS network, the carrier is able to provide Layer 2 VPNs ofdifferent media types, such as ATM, FR, VLAN, Ethernet, and PPP.

MPLS OAM The MPLS OAM provides continuity check for a single LSP, and provides a set of faultdetection tools and fault correct mechanisms for MPLS networks. The MPLS OAM andrelevant protection switching components implement the detection function for the CR-LSP forwarding plane, and perform the protection switching in 50 ms after a fault occurs.In this way, the impact of a fault can be lowered to the minimum.

MPLS TE Multiprotocol Label Switching Traffic Engineering

MPLS TE tunnel In the case of reroute deployment, or when traffic needs to be transported throughmultiple trails, multiple LSP tunnels might be used. In traffic engineering, such a groupof LSP tunnels are referred to as TE tunnels. An LSP tunnel of this kind has twoidentifiers. One is the Tunnel ID carried by the SENDER object, and is used to uniquelydefine the TE tunnel. The other is the LSP ID carried by the SENDER_TEMPLATE orFILTER_SPEC object.

MS See Multiplex Section

MSP See multiplex section protection



H-19

MSTI See Multiple Spanning Tree Instance

MSTP See Multiple Spanning Tree Protocol

MTBF Mean Time Between Failure

MTTR See Mean Time To Repair

MTU See Maximum Transfer Unit

Multi-link Point toPoint Protocol

A protocol used in ISDN connections. MLPPP lets two B channels act as a single line,doubling connection rates to 128Kbps.

Multi-Protocol LabelSwitch

A technology that uses short tags of fixed length to encapsulate packets in different linklayers, and provides connection-oriented switching for the network layer on the basis ofIP routing and control protocols. It improves the cost performance and expandability ofnetworks, and is beneficial to routing.

Multicast A process of transmitting packets of data from one source to many destinations. Thedestination address of the multicast packet uses Class D address, that is, the IP addressranges from 224.0.0.0 to 239.255.255.255. Each multicast address represents a multicastgroup rather than a host.

Multiple SpanningTree Instance

Multiple spanning tree instance. One of a number of Spanning Trees calculated by MSTPwithin an MST Region, to provide a simply and fully connected active topology forframes classified as belonging to a VLAN that is mapped to the MSTI by the MSTConfiguration. A VLAN cannot be assigned to multiple MSTIs.

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.

Multiple SpanningTree Region

The MST region consists of switches that support the MSTP in the LAN and links amongthem. Switches physically and directly connected and configured with the same MSTregion attributes belong to the same MST region. The attributes for the same MST regionare as follows: Same region name Same revision level Same mapping relation betweenthe VLAN ID to MSTI

Multiplex Section The trail between and including two multiplex section trail termination functions.

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

NE Explorer The main operation interface, of the U2000, which is used to manage the OptiXequipment. In the NE Explorer, the user can configure, manage and maintain the NE,boards, and ports on a per-NE basis.


Maintenance Guide


Issue 04 (2010-10-30)

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.

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.

Network to NetworkInterface

This is an internal interface within a network linking two or more elements.

next hop The next router to which a packet is sent from any given router as it traverses a networkon its journey to its final destination.

NLP Normal Link Pulse

NMS See network management system

NNHOP Next-Next-Hop

NNI See Network to Network Interface

Node A node stands for a managed device in the network.For a device with a single frame, onenode stands for one device.For a device with multiple frames, one node stands for oneframe of the device.Therefore, a node does not always mean a device.

Node Protection A parameter of the FRR protection. It indicates that the bypass tunnel should be able toprotect the downstream node that is involved in the working tunnel and adjacent to thePLR. The node cannot be a merge point, and the bypass tunnel should also be able toprotect the downstream link that is involved in the working tunnel and adjacent to thePLR.

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

NSF Not Stop Forwarding

NSMI Network Serial Multiplexed Interface

O

OAM See Operation, Administration and Maintenanc

ODF See Optical Distribution Frame

ODU See outdoor unit

One-to-One Backup A local repair method in which a backup tunnel is separately created for each protectedtunnel at a PLR.

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.



H-21

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.

Operation,Administration andMaintenanc

Operation, Administration and Maintenance. A group of network support functions thatmonitor and sustain segment operation, activities that are concerned with, but not limitedto, failure detection, notification, location, and repairs that are intended to eliminate faultsand keep a segment in an operational state and support activities required to provide theservices of a subscriber access network to users/subscribers.

Optical DistributionFrame

A frame which is used to transfer and spool fibers.

orderwire A channel that provides voice communication between operation engineers ormaintenance engineers of different stations.

OSI See Open Systems Interconnection

OSP OptiX Software Platform

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.

Outloop A method of looping back the input signals received at an port to an output port withoutchanging the structure of the signals.

Output optical power The ranger of optical energy level of output signals.

H.5 P-T

P

Packet over SDH/SONET

A MAN and WAN technology that provides point-to-point data connections. The POSinterface uses SDH/SONET as the physical layer protocol, and supports the transport ofpacket data (such as IP packets) in MAN and WAN.

packet switchednetwork

A telecommunication network which works in packet switching mode.

Packing case A case which is used for packing the board or subrack.

Path/Channel A logical connection between the point at which a standard frame format for the signalat the given rate is assembled, and the point at which the standard frame format for thesignal is disassembled.

PBS See peak burst size

PCB See Printed Circuit Board

PCI bus PCI (Peripheral Component Interconnect) bus. A high performance bus, 32-bit or 64-bitfor interconnecting chips, expansion boards, and processor/memory subsystems.

PDH See Plesiochronous Digital Hierarchy

PDU Protocol Data Unit

PE See Provider Edge


Maintenance Guide


Issue 04 (2010-10-30)

peak burst size A parameter used to define the capacity of token bucket P, that is, the maximum burstIP packet size when the information is transferred at the peak information rate. Thisparameter must be larger than 0. It is recommended that this parameter should be notless than the maximum length of the IP packet that might be forwarded.

Peak Information Rate Peak Information Rate . A traffic parameter, expressed in bit/s, whose value should benot less than the committed information rate.

Penultimate HopPopping

Penultimate Hop Popping (PHP) is a function performed by certain routers in an MPLSenabled network. It refers to the process whereby the outermost label of an MPLS taggedpacket is removed by a Label Switched Router (LSR) before the packet is passed to anadjacent Label Edge Router (LER).

Per-Hop-Behavior A forwarding behavior applied at a DS-compliant node. This behavior belongs to thebehavior aggregate defined in the DiffServ domain.

PHB See Per-Hop-Behavior

PHP See Penultimate Hop Popping

PIM-DM Protocol Independent Multicast-Dense Mode

PIM-SM See Protocol Independent Multicast-Sparse Mode

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.

POS See Packet over SDH/SONET

Power box A direct current power distribution box at the upper part of a cabinet, which suppliespower for the subracks in the cabinet.

PPP See Point-to-Point Protocol

PPVPN Provider Provisioned VPN

PQ See Priority Queuing

PRBS Pseudo-Random Binary Sequence

PRC Primary Reference Clock

Printed Circuit Board A board used to mechanically support and electrically connect electronic componentsusing conductive pathways, tracks, or traces, etched from copper sheets laminated ontoa non-conductive substrate.



H-23

Priority Queuing A priority queue is an abstract data type in computer programming that supports thefollowing three operations: 1) InsertWithPriority: add an element to the queue with anassociated priority 2) GetNext: remove the element from the queue that has the highestpriority, and return it (also known as "PopElement(Off)", or "GetMinimum") 3)PeekAtNext (optional): look at the element with highest priority without removing it

Processing board area An area for the processing boards on the subrack.

protection groundingcable

A cable which connects the equipment and the protection grounding bar. Usually, onehalf of the cable is yellow; while the other half is green.

Protection path A specific path that is part of a protection group and is labeled protection.

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.

Provider Edge A device that is located in the backbone network of the MPLS VPN structure. A PE isresponsible for VPN user management, establishment of LSPs between PEs, andexchange of routing information between sites of the same VPN. During the process, aPE performs the mapping and forwarding of packets between the private network andthe public channel. A PE can be a UPE, an SPE, or an NPE.

Pseudo wire An emulated connection between two PEs for transmitting frames. The PW is establishedand maintained by PEs through signaling protocols. The status information of a PW ismaintained by the two end PEs of a PW.

Pseudo WireEmulation Edge-to-Edge

Pseudo-Wire Emulation Edge to Edge (PWE3) is a type of end-to-end Layer 2transmitting technology. It emulates the essential attributes of a telecommunicationservice such as ATM, FR or Ethernet in a Packet Switched Network (PSN). PWE3 alsoemulates the essential attributes of low speed Time Division Multiplexed (TDM) circuitand SONET/SDH. The simulation approximates to the real situation.

PSN See packet switched network

PTN Packet Transport Network

PW See Pseudo wire

PWE3 See Pseudo Wire Emulation Edge-to-Edge

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.


Maintenance Guide


Issue 04 (2010-10-30)

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.

Random EarlyDetection

A packet loss algorithm used in congestion avoidance. It discards the packet accordingto the specified higher limit and lower limit of a queue so that global TCP synchronizationresulted in traditional Tail-Drop can be prevented.

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.

RDI See Remote Defect Indication

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

Receiver Sensitivity Receiver sensitivity is defined as the minimum acceptable value of average receivedpower at point R to achieve a 1 x 10-10 BER.

RED See Random Early Detection

REI See Remote Error Indication

Remote DefectIndication

A signal transmitted at the first opportunity in the outgoing direction when a terminaldetects specific defects in the incoming signal.

Remote ErrorIndication

A remote error indication (REI) is sent upstream to signal an error condition. There aretwo types of REI alarms: Remote error indication line (REI-L) is sent to the upstreamLTE when errors are detected in the B2 byte. Remote error indication path (REI-P) issent to the upstream PTE when errors are detected in the B3 byte.

remote networkmonitoring

A manage information base (MIB) defined by the Internet Engineering Task Force(IETF). RMON is mainly used to monitor the data flow of one network segment or theentire network.

Resource ReservationProtocol

The Resource Reservation Protocol (RSVP) is designed for Integrated Service and isused to reserve resources on every node along a path. RSVP operates on the transportlayer; however, RSVP does not transport application data. RSVP is a network controlprotocol like Internet Control Message Protocol (ICMP).

Reverse pressure A traffic control method. In telecommunication, when detecting that the transmit endtransmits a large volume of traffic, the receive end sends signals to ask the transmit endto slow down the transmission rate.

RF See Radio Freqency

RFC Request For Comment



H-25

RIP See Routing Information Protocol

RMON See remote network monitoring

RNC See Radio Network Controller

Root alarm An alarm directly caused by anomaly events or faults in the network. Some lower-levelalarms always accompany a root alarm.

route A route is the path that network traffic takes from its source to its destination. In a TCP/IP network, each IP packet is routed independently. Routes can change dynamically.

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.

routing table A table that stores and updates the locations (addresses) of network devices. Routersregularly share routing table information to be up to date. A router relies on thedestination address and on the information in the table that gives the possible routes--inhops or in number of jumps--between itself, intervening routers, and the destination.Routing tables are updated frequently as new information is available.

RS Reed-Solomon encoding

RSL Received Signal Level

RSSI See Received Signal Strength Indicator

RSTP See Rapid Spanning Tree Protocol

RSVP See Resource Reservation Protocol

RTN Radio Transmission Node

S

SD See space diversity

SDH See Synchronous Digital Hierarchy

SDP Serious Disturbance Period

SEMF Synchronous Equipment Management Function

Service LevelAgreement

A management-documented agreement that defines the relationship between serviceprovider and its customer. It also provides specific, quantifiable information aboutmeasuring and evaluating the delivery of services. The SLA details the specific operatingand support requirements for each service provided. It protects the service provider andcustomer and allows the service provider to provide evidence that it has achieved thedocumented target measure.

SES Severely Errored Second

Setup Priority The priority of the tunnel with respect to obtaining resources, ranging from 0 (indicatesthe highest priority) to 7. It is used to determine whether the tunnel can preempt theresources required by other backup tunnels.

SF See Signal Fail

SFP See Small Form-Factor Pluggable


Maintenance Guide


Issue 04 (2010-10-30)

side trough The trough on the side of the cable rack, which is used to place nuts so as to fix thecabinet.

signal cable Common signal cables cover the E1cable, network cable, and other non-subscriber signalcable.

Signal Fail SF is a signal indicating the associated data has failed in the sense that a near-end defectcondition (not being the degraded defect) is active.

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.

simplex Of or relating to a telecommunications system in which only one message can be sentin either direction at one time.

SLA See Service Level Agreement

Slicing To divide data into the information units proper for transmission.

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

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

Static Virtual Circuit Static virtual circuit. A static implementation of MPLS L2VPN that transfers L2VPNinformation by manual configuration of VC labels, instead of by a signaling protocol.

Statistical multiplexing A multiplexing technique whereby information from multiple logical channels can betransmitted across a single physical channel. It dynamically allocates bandwidth only toactive input channels, to make better use of available bandwidth and allow more devicesto be connected than with other multiplexing techniques. Compare with TDM.

STM See synchronous transport module

STM-1 SDH Transport Module -1



H-27

STM-1e STM-1 Electrical Interface

STM-1o STM-1 Optical Interface

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.

subnet mask The technique used by the IP protocol to determine which network segment packets aredestined for. The subnet mask is a binary pattern that is stored in the client machine,server or router and is matched with the IP address.

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.

SVC See Static Virtual Circuit

SVL Shared VLAN Learning

Switch To filter, forward frames based on label or the destination address of each frame. Thisbehavior operates at the data link layer of the OSI model.

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.

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.


Maintenance Guide


Issue 04 (2010-10-30)

T

tail drop A type of QoS. When a queue within a network router reaches its maximum length,packet drops can occur. When a packet drop occurs, connection-based protocols such asTCP slow down their transmission rates in an attempt to let queued packets be serviced,thereby letting the queue empty. This is also known as tail drop because packets aredropped from the input end (tail) of the queue.

Tail drop A congestion management mechanism, in which packets arrive later are discarded whenthe queue is full. This policy of discarding packets may result in network-widesynchronization due to the TCP slow startup mechanism.

TCI Tag Control Information

TCP See TransmissionControl Protocol

TDM See Time Division Multiplexing

TE See traffic engineering

TEDB See Traffic Engineering DataBase

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.

TIM Trace Identifier Mismatch

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 engrosstime slots in a certain order, forming multiple multiplexing digital signals to betransmitted over one channel.

Time To Live A technique used in best-effort delivery systems to prevent packets that loop endlessly.The TTL is set by the sender to the maximum time the packet is allowed to be in thenetwork. Each router in the network decrements the TTL field when the packet arrives,and discards any packet if the TTL counter reaches zero.

TMN See Telecommunication Management Network

ToS priority A ToS sub-field (the bits 0 to 2 in the ToS field) in the ToS field of the IP packet header.

TPS See Tributary Protection Switch

traffic engineering A task that effectively maps the service flows to the existing physical topology.

Traffic EngineeringDataBase

TEDB is the abbreviation of the traffic engineering database. MPLS TE needs to knowthe features of the dynamic TE of every links by expanding the current IGP, which usesthe link state algorithm, such as OSPF and IS-IS. The expanded OSPF and IS-IS containsome TE features, such as the link bandwidth and color. The maximum reservedbandwidth of the link and the unreserved bandwidth of every link with priority are ratherimportant. Every router collects the information about TE of every links in its area andgenerates TE DataBase. TEDB is the base of forming the dynamic TE path in the MPLSTE network.

Traffic shaping It is a way of controlling the network traffic from a computer to optimize or guaranteethe performance and minimize the delay. It actively adjusts the output speed of trafficin the scenario that the traffic matches network resources provided by the lower layerdevices, avoiding packet loss and congestion.



H-29

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.

Tributary ProtectionSwitch

Tributary protection switching, a function provided by the equipment, is intended toprotect N tributary processing boards through a standby tributary processing board.

trTCM See Two Rate Three Color Marker

TTL See Time To Live

TU Tributary Unit

Tunnel A channel on the packet switching network that transmits service traffic between PEs.In VPN, a tunnel is an information transmission channel between two entities. The tunnelensures secure and transparent transmission of VPN information. In most cases, a tunnelis an MPLS tunnel.

Two Rate Three ColorMarker

The trTCM meters an IP packet stream and marks its packets based on two rates, PeakInformation Rate (PIR) and Committed Information Rate (CIR), and their associatedburst sizes to be either green, yellow, or red. A packet is marked red if it exceeds thePIR. Otherwise it is marked either yellow or green depending on whether it exceeds ordoesn't exceed the CIR.

H.6 U-Z

U

UAS Unavailable Second

UBR See Unspecified Bit Rate

UDP See User Datagram Protocol

underfloor cabling The cables connected cabinets and other devices are routed underfloor.

UNI See User Network Interface

Unicast The process of sending data from a source to a single recipient.

Unspecified Bit Rate No commitment to transmission. No feedback to congestion. This type of service is idealfor the transmission of IP datagrams. In case of congestion, UBR cells are discarded,and no feedback or request for slowing down the data rate is delivered to the sender.

Upper subrack The subrack close to the top of the cabinet when a cabinet contains several subracks.

UPS Uninterruptible Power Supply

upward cabling Cables or fibres connect the cabinet with other equipment from the top of the cabinet.


Maintenance Guide


Issue 04 (2010-10-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

V-NNI See virtual network-network interface

V-UNI See Virtual User-Network Interface

Variable Bit Rate One of the traffic classes used by ATM (Asynchronous Transfer Mode). Unlike apermanent CBR (Constant Bit Rate) channel, a VBR data stream varies in bandwidthand is better suited to non real time transfers than to real-time streams such as voice calls.

VBR See Variable Bit Rate

VC See Virtual Channel

VC-12 Virtual Container -12



VCC Virtual Channel Connection

VCC,VPL See Virtual Chanel Connection

VCG See virtual concatenation group

VCI See Virtual Channel Identifier

Virtual ChanelConnection

Virtual Channel Connection. The VC logical trail that carries data between two endpoints in an ATM network. A logical grouping of multiple virtual channel connectionsinto one virtual connection.

Virtual Channel Any logical connection in the ATM network. A VC is the basic unit of switching in theATM network uniquely identified by a virtual path identifier (VPI)/virtual channelidentifier (VCI) value. It is the channel on which ATM cells are transmitted by the sw

Virtual ChannelIdentifier

virtual channel identifier. A 16-bit field in the header of an ATM cell. The VCI, togetherwith the VPI, is used to identify the next destination of a cell as it passes through a seriesof ATM switches on its way to its destination.

virtual concatenationgroup

A group of co-located member trail termination functions that are connected to the samevirtual concatenation link

Virtual Leased Line A point-to-point, layer-2 channel that behaves like a leased line by transparentlytransporting different protocols with a guaranteed throughput.



H-31

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 network-network interface

A virtual network-network interface (V-NNI) is a network-side interface.

Virtual Path Identifier The field in the ATM (Asynchronous Transfer Mode) cell header that identifies to whichVP (Virtual Path) the cell belongs.

Virtual Private LANService

A type of point-to-multipoint L2VPN service provided over the public network. VPLSenables geographically isolated user sites to communicate with each other through theMAN/WAN as if they are on the same LAN.

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.

Virtual Private WireService

A technology that bears Layer 2 services. VPWS emulates services such as ATM, FR,Ethernet, low-speed TDM circuit, and SONET/SDH in a PSN.

Virtual Routing andForwarding

A technology included in IP (Internet Protocol) network routers that allows multipleinstances of a routing table to exist in a router and work simultaneously.

Virtual Switch Instance An instance through which the physical access links of VPLS can be mapped to thevirtual links. Each VSI provides independent VPLS service. VSI has Ethernet bridgefunction and can terminate PW.

Virtual User-NetworkInterface

virtual user-network interface. A virtual user-network interface, works as an action pointto perform service claissification and traffic control in HQoS.

VLAN See Virtual Local Area Network

VLL See Virtual Leased Line

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

VPI See Virtual Path Identifier

VPLS See Virtual Private LAN Service

VPN See Virtual Private Network

VPWS See Virtual Private Wire Service

VRF See Virtual Routing and Forwarding

VSI See Virtual Switch Instance

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.

WAN See Wide Area Network


Maintenance Guide


Issue 04 (2010-10-30)

Web LCT The local maintenance terminal of a transport network, which is located on the NEmanagement layer of the transport network

Weighted Fair Queuing Weighted Fair Queuing (WFQ) is a fair queue scheduling algorithm based on bandwidthallocation weights. This scheduling algorithm allocates the total bandwidth of aninterface to queues, according to their weights and schedules the queues cyclically. Inthis manner, packets of all priority queues can be scheduled.

Weighted RandomEarly Detection

A packet loss algorithm used for congestion avoidance. It can prevent the global TCPsynchronization caused by traditional tail-drop. WRED is favorable for the high-prioritypacket when calculating the packet loss ratio.

WFQ See Weighted Fair Queuing

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.

Winding pipe A tool for fiber routing, which acts as the corrugated pipe.

wire speed Wire speed refers to the maximum packet forwarding capacity on a cable. The value ofwire speed equals the maximum transmission rate capable on a given type of media.

WMS Wholesale Managed Services

WRED See Weighted Random Early Detection

WRR Weighted Round Robin

WTR See Wait to Restore Time

X

XPD Cross-Polarization Discrimination

XPIC See cross polarization interference cancellation



H-33

Documents

RTN 620 Maintenance Guide(V100R005C00_04)