RTN_910_Maintenance_Guide(U2000)-(V100R003C03_01)

OptiX RTN 910 Radio Transmission SystemV100R003C03

Maintenance Guide (U2000)

Issue 01

Date 2011-10-30

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2011. 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 01 (2011-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 910 V100R003C03

iManager U2000 V100R006C00

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

This document is intended for:

l Network planning engineerl Data configuration engineerl 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 910 Radio Transmission SystemMaintenance Guide (U2000) About This Document


ii

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.



iii


{ 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 issues are cumulative. Therefore, the latest document issue containsall updates made in previous issues.

Updates in Issue 01 (2011-10-30) Based on Product Version V100R003C03This document is the first issue of the V100R003C03 product version.



iv

Contents

About This Document.....................................................................................................................ii

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

1.6.1 Safe Usage of Optical Fibers.....................................................................................................................91.6.2 Electromagnetic Exposure.......................................................................................................................111.6.3 Forbidden Areas......................................................................................................................................111.6.4 Laser........................................................................................................................................................111.6.5 Microwave...............................................................................................................................................12

1.7 Working at Heights...........................................................................................................................................131.7.1 Hoisting Heavy Objects...........................................................................................................................131.7.2 Using Ladders..........................................................................................................................................14

1.8 Mechanical Safety............................................................................................................................................161.9 Other Precautions.............................................................................................................................................17

2 Notices for High-Risk Operations...........................................................................................192.1 Operation Guide for the Toggle Lever Switch.................................................................................................202.2 Operation Guide for the IF Jumper...................................................................................................................222.3 Operation Guide for the IF Cable.....................................................................................................................232.4 Operation Guide for the IF Board.....................................................................................................................24

3 Routine Maintenance..................................................................................................................25

4 Emergency Maintenance............................................................................................................274.1 Definition of Emergency..................................................................................................................................284.2 Purposes of Emergency Maintenance...............................................................................................................284.3 Procedure for Emergency Maintenance............................................................................................................28

5 Troubleshooting..........................................................................................................................355.1 General Troubleshooting Procedure.................................................................................................................375.2 Troubleshooting Service Interruptions.............................................................................................................39

OptiX RTN 910 Radio Transmission SystemMaintenance Guide (U2000) Contents


v

5.3 Troubleshooting the Radio Link.......................................................................................................................455.4 Troubleshooting Bit Errors in TDM Services..................................................................................................535.5 Troubleshooting Pointer Justifications.............................................................................................................595.6 Troubleshooting the Interconnection with SDH Equipment............................................................................635.7 Troubleshooting the Interconnection with PDH Equipment............................................................................665.8 Troubleshooting Native Ethernet Service Faults..............................................................................................705.9 Troubleshooting Ethernet Service on the EoS/EoPDH Plane..........................................................................765.10 Troubleshooting MPLS Tunnels....................................................................................................................825.11 Troubleshooting CES Services.......................................................................................................................865.12 Troubleshooting ATM Services.....................................................................................................................915.13 Troubleshooting Ethernet Services Carried by PWs......................................................................................955.14 Troubleshooting Orderwire Faults..................................................................................................................99

6 Part Replacement.......................................................................................................................1026.1 Removing a Board..........................................................................................................................................1046.2 Inserting a Board............................................................................................................................................1066.3 Replacing the SDH Optical Interface Board..................................................................................................1086.4 Replacing the PDH Interface Board...............................................................................................................1096.5 Replacing the Smart E1 Board.......................................................................................................................1106.6 Replacing the Ethernet Interface Board..........................................................................................................1116.7 Replacing the IF Board...................................................................................................................................1126.8 Replacing the CF Card...................................................................................................................................1146.9 Replacing the System Control, Switch and Timing Board.............................................................................1156.10 Replacing the Fan Board..............................................................................................................................1166.11 Replacing the Power Board..........................................................................................................................1186.12 Replacing the SFP........................................................................................................................................1196.13 Replacing the ODU......................................................................................................................................1216.14 Replacing the IF Cable.................................................................................................................................122

7 Database Backup and Restoration.........................................................................................1247.1 NE Database...................................................................................................................................................1257.2 Backing Up the Database Manually...............................................................................................................1257.3 Setting the Database Backup Policy...............................................................................................................126

7.3.1 Setting the User-Defined Backup Policy...............................................................................................1267.3.2 Enable the Backup Policy of the Device...............................................................................................1277.3.3 Disable the Backup Policy of the Device..............................................................................................128

7.4 Restoring the Database...................................................................................................................................128

8 Supporting Task........................................................................................................................1308.1 Hardware Loopback.......................................................................................................................................1328.2 Cleaning Fiber Connectors and Adapters.......................................................................................................132

8.2.1 Cleaning Fiber Connectors by Using Cartridge Cleaners.....................................................................1328.2.2 Cleaning Fiber Connectors by Using Lens Tissue................................................................................1348.2.3 Cleaning Fiber Adapters by Using Optical Cleaning Sticks.................................................................135



vi

8.3 Browsing Alarms, Abnormal Events, and Performance Events.....................................................................1368.3.1 Checking the NE Status.........................................................................................................................1368.3.2 Checking the Board Status....................................................................................................................1378.3.3 Browsing Current Alarms......................................................................................................................1378.3.4 Browsing Abnormal Events...................................................................................................................1398.3.5 Browsing Current Performance Events.................................................................................................1408.3.6 Browsing History Alarms......................................................................................................................1408.3.7 Browsing History Performance Events.................................................................................................1418.3.8 Browsing the Performance Event Threshold-Crossing Records...........................................................1428.3.9 Browsing UAT Events...........................................................................................................................1428.3.10 Configuring the Performance Monitoring Status of NEs....................................................................1438.3.11 Setting Severity and Auto Reporting Status of Alarms.......................................................................1448.3.12 Suppressing Alarms for Monitored Objects........................................................................................1448.3.13 Suppressing Alarms for NEs...............................................................................................................1458.3.14 Reversing Alarms for Service Ports....................................................................................................1458.3.15 Setting Trigger Conditions of AIS Insertion.......................................................................................1468.3.16 Setting Trigger Conditions of UNEQ Insertion...................................................................................1478.3.17 Setting Bit Error Thresholds for Service Ports....................................................................................1478.3.18 Setting Monitoring and Auto-Report Status of Performance Events..................................................1488.3.19 Setting Performance Thresholds..........................................................................................................1488.3.20 Resetting Performance Registers.........................................................................................................149

8.4 Querying a Report..........................................................................................................................................1498.4.1 Querying the Board Information Report ..............................................................................................1498.4.2 Querying the Board Manufacturing Information Report ......................................................................1508.4.3 Querying the Microwave Link Information Report...............................................................................1508.4.4 Querying the Network-wide License Report.........................................................................................151

8.5 Software Loopback.........................................................................................................................................1528.5.1 Setting Loopback for the SDH Optical Interface Board........................................................................1528.5.2 Setting Loopback for the Tributary Board............................................................................................1548.5.3 Setting a Loopback for the Smart E1 Processing Board.......................................................................1558.5.4 Setting a Loopback for the Packet-plane Ethernet Interface Board......................................................1578.5.5 Setting Loopbacks for the EOS/EoPDH-Plane Ethernet Interface Board.............................................1598.5.6 Setting Loopback for the IF Board........................................................................................................1618.5.7 Locating a Fault by Performing Loopback Operations.........................................................................164

8.6 Reset...............................................................................................................................................................1658.6.1 Cold Reset..............................................................................................................................................1658.6.2 Warm Reset...........................................................................................................................................166

8.7 PRBS Test.......................................................................................................................................................1668.7.1 Performing a PRBS Test for the Tributary Board.................................................................................1668.7.2 Performing a PRBS Test for the IF Board.............................................................................................169

8.8 Querying the License Capacity.......................................................................................................................1708.9 Setting the On/Off State of the Laser.............................................................................................................171



vii

8.10 Setting the ALS Function.............................................................................................................................1718.11 Setting the Automatic Release Function......................................................................................................1728.12 Querying Power Consumption of Boards.....................................................................................................1738.13 Querying the Impedance of an E1 Channel..................................................................................................1738.14 Monitoring Ethernet Packets Through Port Mirroring.................................................................................1748.15 Querying the Attributes of an Ethernet Port.................................................................................................1758.16 Setting Traffic, Physical Bandwidth, or Bandwidth Utilization of Ethernet Ports.......................................1768.17 Querying Traffic, Physical Bandwidth, or Bandwidth Utilization of Ethernet Ports...................................1778.18 Setting the Threshold of Received Traffic Flow on an Ethernet Port..........................................................1788.19 Using the Ethernet Test Frames....................................................................................................................178

A Alarm Reference.......................................................................................................................181A.1 Alarm List (in Alphabetical Order)...............................................................................................................182A.2 Alarm List (Classified by Logical Boards)....................................................................................................202

A.2.1 CSTA....................................................................................................................................................203A.2.2 CSHA/CSHB/CSHC/CSHD/CSHE.....................................................................................................204A.2.3 IF1.........................................................................................................................................................205A.2.4 IFU2......................................................................................................................................................205A.2.5 IFX2......................................................................................................................................................206A.2.6 SL1D/SL1DA.......................................................................................................................................207A.2.7 EM6T....................................................................................................................................................207A.2.8 EM6TA.................................................................................................................................................208A.2.9 EM6TB.................................................................................................................................................208A.2.10 EM6F..................................................................................................................................................208A.2.11 EM6FA...............................................................................................................................................209A.2.12 EM4T..................................................................................................................................................209A.2.13 EM4F..................................................................................................................................................210A.2.14 EFP8...................................................................................................................................................210A.2.15 EMS6..................................................................................................................................................211A.2.16 SP3S/SP3D.........................................................................................................................................212A.2.17 AUX....................................................................................................................................................212A.2.18 PIU......................................................................................................................................................212A.2.19 FAN....................................................................................................................................................213A.2.20 ISU2....................................................................................................................................................213A.2.21 ISX2....................................................................................................................................................214A.2.22 ML1/MD1...........................................................................................................................................214A.2.23 MP1.....................................................................................................................................................215A.2.24 EM6X.................................................................................................................................................216A.2.25 ODU....................................................................................................................................................216A.2.26 PMU....................................................................................................................................................217A.2.27 TCU....................................................................................................................................................217

A.3 Alarms and Handling Procedures..................................................................................................................217A.3.1 A_LOC.................................................................................................................................................217



viii

A.3.2 ALM_E1RAI........................................................................................................................................218A.3.3 ALM_GFP_dCSF.................................................................................................................................219A.3.4 ALM_GFP_dLFD.................................................................................................................................220A.3.5 ALM_IMA_LIF....................................................................................................................................221A.3.6 ALM_IMA_LODS...............................................................................................................................223A.3.7 ALM_IMA_RE_RX_UNUSABLE......................................................................................................224A.3.8 ALM_IMA_RE_TX_UNUSABLE......................................................................................................225A.3.9 ALM_IMA_RFI...................................................................................................................................227A.3.10 AM_DOWNSHIFT............................................................................................................................228A.3.11 APS_FAIL..........................................................................................................................................229A.3.12 APS_INDI...........................................................................................................................................230A.3.13 APS_MANUAL_STOP......................................................................................................................232A.3.14 ATMPW_UNKNOWNCELL_EXC..................................................................................................233A.3.15 AU_AIS..............................................................................................................................................233A.3.16 AU_LOP.............................................................................................................................................235A.3.17 B1_EXC..............................................................................................................................................236A.3.18 B1_SD.................................................................................................................................................238A.3.19 B2_EXC..............................................................................................................................................240A.3.20 B2_SD.................................................................................................................................................242A.3.21 B3_EXC..............................................................................................................................................244A.3.22 B3_EXC_VC3....................................................................................................................................247A.3.23 B3_SD.................................................................................................................................................249A.3.24 B3_SD_VC3.......................................................................................................................................251A.3.25 BAT1TEMP_SENSOR_FAIL...........................................................................................................253A.3.26 BAT2TEMP_SENSOR_FAIL...........................................................................................................254A.3.27 BD_NOT_INSTALLED.....................................................................................................................255A.3.28 BD_STATUS......................................................................................................................................256A.3.29 BDTEMP_SENSOR_FAIL................................................................................................................258A.3.30 BIP_EXC............................................................................................................................................260A.3.31 BIP_SD...............................................................................................................................................261A.3.32 BOOTROM_BAD..............................................................................................................................263A.3.33 BUS_ERR...........................................................................................................................................264A.3.34 CES_ACR_LOCK_ABN...................................................................................................................266A.3.35 CES_JTROVR_EXC..........................................................................................................................267A.3.36 CES_JTRUDR_EXC..........................................................................................................................268A.3.37 CES_LOSPKT_EXC..........................................................................................................................269A.3.38 CES_MALPKT_EXC.........................................................................................................................270A.3.39 CES_MISORDERPKT_EXC.............................................................................................................271A.3.40 CES_RDI............................................................................................................................................272A.3.41 CES_STRAYPKT_EXC....................................................................................................................273A.3.42 CESPW_OPPOSITE_ACFAULT......................................................................................................274A.3.43 CESPW_OPPOSITE_RAI.................................................................................................................274



ix

A.3.44 CFCARD_FAILED............................................................................................................................275A.3.45 CFCARD_OFFLINE..........................................................................................................................276A.3.46 CHCS..................................................................................................................................................278A.3.47 CLK_NO_TRACE_MODE................................................................................................................279A.3.48 COMMUN_FAIL...............................................................................................................................280A.3.49 CONFIG_NOSUPPORT....................................................................................................................282A.3.50 DBMS_ABNORMAL........................................................................................................................284A.3.51 DBMS_ERROR..................................................................................................................................285A.3.52 DBMS_PROTECT_MODE...............................................................................................................286A.3.53 DCNSIZE_OVER...............................................................................................................................287A.3.54 DDN_LFA..........................................................................................................................................288A.3.55 DOWN_E1_AIS.................................................................................................................................289A.3.56 DROPRATIO_OVER.........................................................................................................................290A.3.57 E1_LOC..............................................................................................................................................291A.3.58 E1_LOS..............................................................................................................................................292A.3.59 ENVHUM_SENSOR_FAIL...............................................................................................................293A.3.60 ENVTEMP_SENSOR_FAIL.............................................................................................................294A.3.61 ENVTEMP1_SENSOR_FAIL...........................................................................................................296A.3.62 ENVTEMP2_SENSOR_FAIL...........................................................................................................297A.3.63 ETH_APS_LOST...............................................................................................................................298A.3.64 ETH_APS_PATH_MISMATCH.......................................................................................................299A.3.65 ETH_APS_SWITCH_FAIL...............................................................................................................300A.3.66 ETH_APS_TYPE_MISMATCH........................................................................................................301A.3.67 ETH_CFM_LOC................................................................................................................................302A.3.68 ETH_CFM_MISMERGE...................................................................................................................305A.3.69 ETH_CFM_RDI.................................................................................................................................308A.3.70 ETH_CFM_UNEXPERI....................................................................................................................310A.3.71 ETH_EFM_DF...................................................................................................................................313A.3.72 ETH_EFM_EVENT...........................................................................................................................314A.3.73 ETH_EFM_LOOPBACK...................................................................................................................315A.3.74 ETH_EFM_REMFAULT...................................................................................................................317A.3.75 ETH_LOS...........................................................................................................................................318A.3.76 ETH_NO_FLOW...............................................................................................................................319A.3.77 ETHOAM_DISCOVER_FAIL..........................................................................................................321A.3.78 ETHOAM_RMT_CRIT_FAULT.......................................................................................................322A.3.79 ETHOAM_RMT_LOOP....................................................................................................................324A.3.80 ETHOAM_RMT_SD.........................................................................................................................325A.3.81 ETHOAM_SELF_LOOP...................................................................................................................327A.3.82 ETHOAM_VCG_SELF_LOOP.........................................................................................................328A.3.83 EX_ETHOAM_CC_LOS...................................................................................................................330A.3.84 EX_ETHOAM_MPID_CNFLCT.......................................................................................................331A.3.85 EXT_SYNC_LOS..............................................................................................................................333



x

A.3.86 EXT_TIME_LOC...............................................................................................................................334A.3.87 FAN_AGING.....................................................................................................................................334A.3.88 FAN_FAIL.........................................................................................................................................335A.3.89 FCS_ERR...........................................................................................................................................337A.3.90 FLOW_OVER....................................................................................................................................338A.3.91 HARD_BAD.......................................................................................................................................339A.3.92 HP_CROSSTR...................................................................................................................................341A.3.93 HP_LOM............................................................................................................................................342A.3.94 HP_RDI..............................................................................................................................................343A.3.95 HP_REI...............................................................................................................................................344A.3.96 HP_SLM.............................................................................................................................................344A.3.97 HP_TIM..............................................................................................................................................345A.3.98 HP_UNEQ..........................................................................................................................................347A.3.99 HPAD_CROSSTR..............................................................................................................................347A.3.100 IF_CABLE_OPEN...........................................................................................................................349A.3.101 IF_INPWR_ABN.............................................................................................................................350A.3.102 IF_MODE_UNSUPPORTED..........................................................................................................351A.3.103 IMA_GROUP_LE_DOWN..............................................................................................................353A.3.104 IMA_GROUP_RE_DOWN.............................................................................................................354A.3.105 IMA_TXCLK_MISMATCH............................................................................................................355A.3.106 IN_PWR_ABN.................................................................................................................................356A.3.107 IN_PWR_HIGH...............................................................................................................................357A.3.108 IN_PWR_LOW................................................................................................................................358A.3.109 INTEMP_SENSOR_FAIL...............................................................................................................360A.3.110 J0_MM..............................................................................................................................................361A.3.111 K1_K2_M.........................................................................................................................................362A.3.112 K2_M................................................................................................................................................363A.3.113 LAG_BWMM...................................................................................................................................365A.3.114 LAG_DOWN....................................................................................................................................366A.3.115 LAG_MEMBER_DOWN................................................................................................................367A.3.116 LAG_PORT_FAIL...........................................................................................................................369A.3.117 LAG_VC_PORT_FAIL...................................................................................................................371A.3.118 LAN_LOC........................................................................................................................................373A.3.119 LASER_CLOSED............................................................................................................................374A.3.120 LASER_MOD_ERR.........................................................................................................................375A.3.121 LASER_MOD_ERR_EX.................................................................................................................376A.3.122 LASER_SHUT.................................................................................................................................377A.3.123 LCAS_FOPR....................................................................................................................................378A.3.124 LCAS_FOPT....................................................................................................................................380A.3.125 LCAS_PLCR....................................................................................................................................381A.3.126 LCAS_PLCT....................................................................................................................................383A.3.127 LCAS_TLCR....................................................................................................................................384



xi

A.3.128 LCAS_TLCT....................................................................................................................................386A.3.129 LCD..................................................................................................................................................387A.3.130 LCS_LIMITED.................................................................................................................................389A.3.131 LFA...................................................................................................................................................391A.3.132 LICENSE_DIFF...............................................................................................................................392A.3.133 LICENSE_LOST..............................................................................................................................396A.3.134 LINK_ERR.......................................................................................................................................397A.3.135 LMFA...............................................................................................................................................398A.3.136 LOOP_ALM.....................................................................................................................................399A.3.137 LP_CROSSTR..................................................................................................................................401A.3.138 LP_R_FIFO......................................................................................................................................402A.3.139 LP_RDI.............................................................................................................................................403A.3.140 LP_RDI_VC12.................................................................................................................................404A.3.141 LP_RDI_VC3...................................................................................................................................405A.3.142 LP_REI.............................................................................................................................................406A.3.143 LP_REI_VC12..................................................................................................................................407A.3.144 LP_REI_VC3....................................................................................................................................408A.3.145 LP_RFI.............................................................................................................................................409A.3.146 LP_SLM...........................................................................................................................................410A.3.147 LP_SLM_VC12................................................................................................................................410A.3.148 LP_SLM_VC3..................................................................................................................................411A.3.149 LP_T_FIFO.......................................................................................................................................412A.3.150 LP_TIM............................................................................................................................................413A.3.151 LP_TIM_VC12.................................................................................................................................414A.3.152 LP_TIM_VC3...................................................................................................................................415A.3.153 LP_UNEQ.........................................................................................................................................417A.3.154 LP_UNEQ_VC12.............................................................................................................................418A.3.155 LP_UNEQ_VC3...............................................................................................................................419A.3.156 LPS_UNI_BI_M...............................................................................................................................420A.3.157 LPT_CFG_CLOSEPORT.................................................................................................................421A.3.158 LPT_INEFFECT...............................................................................................................................422A.3.159 LPT_RFI...........................................................................................................................................424A.3.160 LSR_NO_FITED..............................................................................................................................425A.3.161 LTI....................................................................................................................................................426A.3.162 MAC_EXT_EXC.............................................................................................................................428A.3.163 MAC_FCS_EXC..............................................................................................................................429A.3.164 MOD_COM_FAIL...........................................................................................................................430A.3.165 MOD_TYPE_MISMATCH.............................................................................................................431A.3.166 MPLS_PW_BDI...............................................................................................................................433A.3.167 MPLS_PW_Excess...........................................................................................................................433A.3.168 MPLS_PW_LOCV...........................................................................................................................434A.3.169 MPLS_PW_MISMATCH................................................................................................................436



xii

A.3.170 MPLS_PW_MISMERGE.................................................................................................................437A.3.171 MPLS_PW_SD.................................................................................................................................438A.3.172 MPLS_PW_SF.................................................................................................................................439A.3.173 MPLS_PW_UNKNOWN.................................................................................................................440A.3.174 MPLS_TUNNEL_BDI.....................................................................................................................441A.3.175 MPLS_TUNNEL_Excess.................................................................................................................441A.3.176 MPLS_TUNNEL_FDI.....................................................................................................................442A.3.177 MPLS_TUNNEL_LOCV.................................................................................................................443A.3.178 MPLS_TUNNEL_MISMATCH......................................................................................................445A.3.179 MPLS_TUNNEL_MISMERGE.......................................................................................................446A.3.180 MPLS_TUNNEL_OAMFAIL..........................................................................................................446A.3.181 MPLS_TUNNEL_SD.......................................................................................................................448A.3.182 MPLS_TUNNEL_SF.......................................................................................................................449A.3.183 MPLS_TUNNEL_UNKNOWN.......................................................................................................450A.3.184 MS_AIS............................................................................................................................................450A.3.185 MS_CROSSTR.................................................................................................................................452A.3.186 MS_RDI............................................................................................................................................453A.3.187 MS_REI............................................................................................................................................454A.3.188 MSAD_CROSSTR...........................................................................................................................455A.3.189 MULTI_RPL_OWNER....................................................................................................................456A.3.190 MW_AM_TEST...............................................................................................................................457A.3.191 MW_BER_EXC...............................................................................................................................458A.3.192 MW_BER_SD..................................................................................................................................462A.3.193 MW_CFG_MISMATCH..................................................................................................................466A.3.194 MW_CONT_WAVE........................................................................................................................467A.3.195 MW_E1_LOST.................................................................................................................................468A.3.196 MW_FEC_UNCOR..........................................................................................................................469A.3.197 MW_LIM..........................................................................................................................................473A.3.198 MW_LOF.........................................................................................................................................475A.3.199 MW_RDI..........................................................................................................................................480A.3.200 NESF_LOST.....................................................................................................................................481A.3.201 NESOFT_MM..................................................................................................................................483A.3.202 NESTATE_INSTALL......................................................................................................................486A.3.203 NO_BD_SOFT.................................................................................................................................487A.3.204 NP1_MANUAL_STOP....................................................................................................................488A.3.205 NP1_SW_FAIL................................................................................................................................489A.3.206 NP1_SW_INDI.................................................................................................................................490A.3.207 NTP_SYNC_FAIL...........................................................................................................................491A.3.208 OCD..................................................................................................................................................492A.3.209 ODC_BATTERY_CURRENT_ABN..............................................................................................493A.3.210 ODC_BATTERY_PWRDOWN......................................................................................................494A.3.211 ODC_DOOR_OPEN........................................................................................................................497



xiii

A.3.212 ODC_FAN_FAILED........................................................................................................................498A.3.213 ODC_HUMI_ABN...........................................................................................................................499A.3.214 ODC_LOAD_PWRDOWN..............................................................................................................501A.3.215 ODC_MDL_ABN.............................................................................................................................504A.3.216 ODC_POWER_FAIL.......................................................................................................................505A.3.217 ODC_SMOKE_OVER.....................................................................................................................508A.3.218 ODC_SURGE_PROTECTION_FAIL.............................................................................................509A.3.219 ODC_TEC_ALM.............................................................................................................................511A.3.220 ODC_TEMP_ABN...........................................................................................................................512A.3.221 ODC_WATER_ALM.......................................................................................................................514A.3.222 OUT_PWR_ABN.............................................................................................................................515A.3.223 OUT1TEMP_SENSOR_FAIL.........................................................................................................516A.3.224 OUT2TEMP_SENSOR_FAIL.........................................................................................................518A.3.225 PATCH_ACT_TIMEOUT...............................................................................................................519A.3.226 PATCH_DEACT_TIMEOUT..........................................................................................................520A.3.227 PATCH_PKGERR...........................................................................................................................520A.3.228 PG_LINK_FAIL...............................................................................................................................521A.3.229 PG_PRT_DEGRADED....................................................................................................................522A.3.230 PLA_CFG_MISMATCH.................................................................................................................523A.3.231 PORTMODE_MISMATCH.............................................................................................................524A.3.232 PORT_EXC_TRAFFIC....................................................................................................................525A.3.233 PORT_MODULE_OFFLINE...........................................................................................................527A.3.234 POWER_ABNORMAL...................................................................................................................528A.3.235 POWER_ALM.................................................................................................................................529A.3.236 PW_DROPPKT_EXC......................................................................................................................531A.3.237 PWAPS_LOST.................................................................................................................................532A.3.238 PWAPS_PATH_MISMATCH.........................................................................................................532A.3.239 PWAPS_SWITCH_FAIL.................................................................................................................533A.3.240 PWAPS_TYPE_MISMATCH.........................................................................................................534A.3.241 R_F_RST..........................................................................................................................................535A.3.242 R_LOC..............................................................................................................................................536A.3.243 R_LOF..............................................................................................................................................537A.3.244 R_LOS..............................................................................................................................................539A.3.245 R_S_ERR..........................................................................................................................................541A.3.246 RADIO_FADING_MARGIN_INSUFF...........................................................................................542A.3.247 RADIO_MUTE................................................................................................................................543A.3.248 RADIO_RSL_BEYONDTH............................................................................................................544A.3.249 RADIO_RSL_HIGH........................................................................................................................545A.3.250 RADIO_RSL_LOW.........................................................................................................................546A.3.251 RADIO_TSL_HIGH.........................................................................................................................548A.3.252 RADIO_TSL_LOW.........................................................................................................................549A.3.253 RELAY_ALARM_CRITICAL........................................................................................................549



xiv

A.3.254 RELAY_ALARM_IGNORE...........................................................................................................550A.3.255 RELAY_ALARM_MAJOR.............................................................................................................551A.3.256 RELAY_ALARM_MINOR.............................................................................................................552A.3.257 RMFA...............................................................................................................................................553A.3.258 RPS_INDI.........................................................................................................................................553A.3.259 RS_CROSSTR..................................................................................................................................556A.3.260 RTC_FAIL........................................................................................................................................557A.3.261 S1_SYN_CHANGE.........................................................................................................................558A.3.262 SCCDATA_BACKUP_FAIL...........................................................................................................559A.3.263 SEC_RADIUS_FAIL.......................................................................................................................561A.3.264 SECU_ALM.....................................................................................................................................562A.3.265 SRV_SHUTDOWN_LD..................................................................................................................563A.3.266 SWDL_ACTIVATED_TIMEOUT..................................................................................................563A.3.267 SWDL_AUTOMATCH_INH..........................................................................................................564A.3.268 SWDL_CHGMNG_NOMATCH.....................................................................................................565A.3.269 SWDL_COMMIT_FAIL..................................................................................................................566A.3.270 SWDL_INPROCESS.......................................................................................................................567A.3.271 SWDL_NEPKGCHECK..................................................................................................................567A.3.272 SWDL_PKG_NOBDSOFT..............................................................................................................568A.3.273 SWDL_PKGVER_MM....................................................................................................................569A.3.274 SWDL_ROLLBACK_FAIL.............................................................................................................570A.3.275 SYN_BAD........................................................................................................................................571A.3.276 SYNC_C_LOS.................................................................................................................................572A.3.277 T_ALOS...........................................................................................................................................573A.3.278 T_F_RST..........................................................................................................................................574A.3.279 T_LOC..............................................................................................................................................575A.3.280 TEMP_ALARM...............................................................................................................................576A.3.281 THUNDERALM..............................................................................................................................577A.3.282 TR_LOC...........................................................................................................................................578A.3.283 TU_AIS.............................................................................................................................................579A.3.284 TU_AIS_VC12.................................................................................................................................581A.3.285 TU_AIS_VC3...................................................................................................................................583A.3.286 TU_LOP...........................................................................................................................................585A.3.287 TU_LOP_VC12................................................................................................................................586A.3.288 TU_LOP_VC3..................................................................................................................................587A.3.289 TUNNEL_APS_DEGRADED.........................................................................................................589A.3.290 UHCS................................................................................................................................................590A.3.291 UP_E1_AIS......................................................................................................................................591A.3.292 VC_AIS............................................................................................................................................592A.3.293 VC_LOC...........................................................................................................................................594A.3.294 VC_RDI............................................................................................................................................595A.3.295 VCAT_LOA.....................................................................................................................................597



xv

A.3.296 VCAT_LOM_VC12.........................................................................................................................598A.3.297 VCAT_LOM_VC3...........................................................................................................................600A.3.298 VCAT_SQM_VC12.........................................................................................................................601A.3.299 VCAT_SQM_VC3...........................................................................................................................603A.3.300 VOLT_LOS......................................................................................................................................604A.3.301 VP_AIS.............................................................................................................................................605A.3.302 VP_LOC...........................................................................................................................................607A.3.303 VP_RDI............................................................................................................................................609A.3.304 W_R_FAIL.......................................................................................................................................611A.3.305 WRG_BD_TYPE.............................................................................................................................612A.3.306 XPIC_LOS........................................................................................................................................613

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

B.2.1 IF 1+1 Protection Switching.................................................................................................................616B.2.2 N+1 Protection Switching.....................................................................................................................618B.2.3 SNCP Switching...................................................................................................................................620B.2.4 Linear MSP Switching..........................................................................................................................622B.2.5 Status Change of an APS Protection Group.........................................................................................624B.2.6 Reporting of PW APS Switching Events..............................................................................................626B.2.7 RMON Performance Value Below the Lower Limit............................................................................627B.2.8 RMON Performance Value Above the Upper Limit............................................................................628

C Performance Event Reference................................................................................................630C.1 Performance Events (by Event Type)............................................................................................................631

C.1.1 SDH/PDH Performance Event List......................................................................................................631C.1.2 Radio Performance Events....................................................................................................................634C.1.3 Other Performance Events....................................................................................................................637

C.2 Performance Events (by Logical Board)........................................................................................................638C.2.1 CSTA/CSHA/CSHB/CSHC/CSHD/CSHE..........................................................................................638C.2.2 IF1.........................................................................................................................................................639C.2.3 IFU2/ISU2.............................................................................................................................................642C.2.4 IFX2/ISX2.............................................................................................................................................646C.2.5 SL1D/SL1DA.......................................................................................................................................650C.2.6 EM6T....................................................................................................................................................652C.2.7 EM6TA.................................................................................................................................................652C.2.8 EM6X....................................................................................................................................................652C.2.9 EM6F....................................................................................................................................................653C.2.10 EM6FA...............................................................................................................................................654C.2.11 EFP8....................................................................................................................................................654C.2.12 EMS6..................................................................................................................................................655C.2.13 SP3S/SP3D.........................................................................................................................................657C.2.14 MP1.....................................................................................................................................................658



xvi

C.2.15 ML1/MD1...........................................................................................................................................659C.2.16 ODU....................................................................................................................................................660

C.3 Performance Events and Handling Procedures..............................................................................................661C.3.1 AUPJCHIGH, AUPJCLOW, and AUPJCNEW...................................................................................661C.3.2 TUPJCHIGH, TUPJCLOW, and TUPJCNEW....................................................................................662C.3.3 RSBBE, RSES, RSSES, RSCSES, and RSUAS..................................................................................663C.3.4 RSOOF and RSOFS..............................................................................................................................665C.3.5 MSBBE, MSES, MSSES, MSCSES, and MSUAS..............................................................................666C.3.6 MSFEBBE, MSFEES, MSFESES, MSFECSES, and MSFEUAS.......................................................667C.3.7 HPBBE, HPES, HPSES, HPCSES, and HPUAS.................................................................................668C.3.8 HPFEBBE, HPFEES, HPFESES, HPFECSES, and HPFEUAS..........................................................670C.3.9 IF_BBE, IF_ES, IF_SES, IF_CSES, and IF_UAS...............................................................................671C.3.10 LPBBE, LPES, LPSES, LPCSES, and LPUAS..................................................................................672C.3.11 LPFEBBE, LPFEES, LPFESES, LPFECSES, and LPFEUAS..........................................................673C.3.12 E1_LCV_SDH, E1_LLOSS_SDH, E1_LES_SDH, and E1_LSES_SDH.........................................674C.3.13 TSL_MAX, TSL_MIN, TSL_CUR, and TSL_AVG.........................................................................675C.3.14 RSL_MAX, RSL_MIN, RSL_CUR, and RSL_AVG........................................................................676C.3.15 FEC_BEF_COR_ER, FEC_COR_BYTE_CNT and FEC_UNCOR_BLOCK_CNT........................676C.3.16 QPSKWS, QAMWS16, QAMWS32, QAMWS64, QAMWS128, and QAMWS256.......................677C.3.17 ATPC_P_ADJUST and ATPC_N_ADJUST.....................................................................................678C.3.18 FB_AMDCNT and FB_AMUCNT....................................................................................................679C.3.19 RLHTT, RLLTT, TLHTT, TLLTT....................................................................................................680C.3.20 TPLMAX, TPLMIN, and TPLCUR...................................................................................................680C.3.21 RPLMAX, RPLMIN, and RPLCUR..................................................................................................681C.3.22 BDTEMPMAX, BDTEMPMIN, and BDTEMPCUR........................................................................681C.3.23 XPIC_XPD_VALUE..........................................................................................................................682C.3.24 PG_IF_BBE, PG_IF_ES, PG_IF_SES, PG_IF_CSES, and PG_IF_UAS..........................................683C.3.25 E1_BBE, E1_ES, E1_SES, E1_CSES, and E1_UAS.........................................................................684C.3.26 IF_SNR_MAX, IF_SNR_MIN, and IF_SNR_AVG..........................................................................686C.3.27 OSPITMPMAX, OSPITMPMIN, and OSPITMPCUR......................................................................686

D RMON Event Reference..........................................................................................................688D.1 List of RMON Alarm Entries........................................................................................................................689D.2 List of RMON Performance Entries on the Packet-Plane.............................................................................690D.3 List of RMON Performance Entries on the EoS/EoPDH Plane....................................................................701D.4 RMON Events and Handling Procedures......................................................................................................704

D.4.1 ETHDROP............................................................................................................................................704D.4.2 ETHEXCCOL.......................................................................................................................................705D.4.3 ETHLATECOL....................................................................................................................................706D.4.4 RXBBAD..............................................................................................................................................707D.4.5 TXDEFFRM.........................................................................................................................................708D.4.6 ETHUNDER.........................................................................................................................................709D.4.7 ETHOVER............................................................................................................................................710



xvii

D.4.8 ETHFRG...............................................................................................................................................710D.4.9 ETHJAB...............................................................................................................................................711D.4.10 ETHCOL.............................................................................................................................................712D.4.11 ETHFCS.............................................................................................................................................713D.4.12 ATMPW_LOSPKTS..........................................................................................................................714D.4.13 ATMPW_MISORDERPKTS.............................................................................................................714D.4.14 ATMPW_UNKNOWNCELLS..........................................................................................................715D.4.15 ATM_CORRECTED_HCSERR........................................................................................................716D.4.16 ATM_UNCORRECTED_HCSERR..................................................................................................716D.4.17 CES_MISORDERPKTS.....................................................................................................................717D.4.18 CES_STRAYPKTS............................................................................................................................718D.4.19 CES_MALPKTS................................................................................................................................718D.4.20 CES_JTRUDR....................................................................................................................................719D.4.21 CES_JTROVR....................................................................................................................................720D.4.22 CES_LOSPKTS..................................................................................................................................720

E Alarm Management..................................................................................................................722E.1 NE Alarm Management.................................................................................................................................723E.2 Board Alarm Management.............................................................................................................................723

E.2.1 Setting the Alarm Severity....................................................................................................................723E.2.2 Alarm Suppression................................................................................................................................723E.2.3 Alarm Auto-Report...............................................................................................................................723E.2.4 Alarm Reversion...................................................................................................................................724E.2.5 Setting of the Bit Error Alarm Threshold.............................................................................................724E.2.6 AIS Insertion.........................................................................................................................................725E.2.7 UNEQ Insertion....................................................................................................................................726

F Performance Event Management...........................................................................................727F.1 NE Performance Event Management.............................................................................................................728F.2 Board Performance Event Management.........................................................................................................728

G Alarm Suppression Relationship..........................................................................................729

H Indicators of Boards.................................................................................................................733

I Glossary.......................................................................................................................................753I.1 0-9....................................................................................................................................................................754I.2 A-E..................................................................................................................................................................754I.3 F-J....................................................................................................................................................................763I.4 K-O..................................................................................................................................................................768I.5 P-T...................................................................................................................................................................774I.6 U-Z..................................................................................................................................................................783



xviii

1 Safety Precautions

About This Chapter

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

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

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

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

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

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

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

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

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

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

OptiX RTN 910 Radio Transmission SystemMaintenance Guide (U2000) 1 Safety Precautions


1

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

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

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

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

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

l Only trained and qualified personnel are permitted to install, operate, and maintain a device.l Only certified professionals are permitted to remove the safety facilities, and to troubleshoot

and maintain the device.l Only the personnel authenticated or authorized by Huawei are permitted to replace or

change the device or parts of the device (including software).l The operating personnel must immediately report the faults or errors that may cause safety

problems to the person in charge.

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

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

l Ensure that the grounding conductor is intact.l Do not operate the device in the absence of a suitably installed grounding conductor.l The device must be connected to the PGND permanently. Before operating the device,

check the electrical connections of the device, and ensure that the device is properlygrounded.

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

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

fixed terminal or touch the terminal or antenna connector.



2

NOTEThe preceding requirements apply to wireless fixed station terminals.

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

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

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

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

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

on a wall or in a rack.l When the system is working, ensure that the ventilation hole is not blocked.l When installing the front panel, use a tool to tighten the screws firmly, if required.l After installing the device, clean up the packing materials.

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

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

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

Symbol Indication

This symbol is for ESD protection.A notice with this symbol indicates that you should wearan ES wrist strap or glove when you touch a board.Otherwise, you may cause damage to the board.

CLASS 1LASER

PRODUCT

LASERRADIATION

DO NOT VIEW DIRECTLYWITH OPTICALINSTRUMENTS

CLASS 1M LASERPRODUCT

This symbol is for the laser class.A notice with this symbol indicates the class of the laser.Avoid direct exposure to the laser beams. Otherwise, it maydamage you eyes or skin.



3

Symbol Indication

A notice with this symbol indicates where the subrack isgrounded.

ATTENTION 警告

CLEAN PERIODICALLY定期清洗

A notice with this symbol indicates that the air filter shouldbe cleaned periodically.

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

DON'T TOUCH THEFAN LEAVES BEFORETHEY SLOW DOWN !

This symbol is for fan safety.A notice with this symbol indicates that the fan leavesshould not be touched when the fan is rotating.

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

High Voltage

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

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

both.

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

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



4

High Leakage Current

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

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

Power Cables

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

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

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

Device with Power On

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

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

Short Circuits

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



5

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

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

Fuse

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

Electrostatic Discharge

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

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

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

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



6

Figure 1-1 Wearing an ESD wrist strap

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

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

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

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

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

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

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

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



7

Basic Precautions

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

l Use special insulation tools.l Wear an eye protector and take effective protection measures.l Wear rubber gloves and a protection coat to prevent the hazard caused by the overflowing

electrolyte.l When handling the storage battery, ensure that its electrodes are upward. Leaning or

reversing the storage battery is prohibited.l Before installing or maintaining the storage battery, ensure that the storage battery is

disconnected from the power supply that charges the storage battery.

Short-Circuit

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

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

Hazardous Gas

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

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

Battery Temperature

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

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



8

Battery Leakage

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

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

l Sodium bicarbonate (NaHCO3)

l Sodium carbonate (Na2CO3)

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

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

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

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

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

Cleaning Fiber Connectors and Optical Interfaces

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



9

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

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

l Non-woven lens tissue

l Special compressed gas

l Cotton stick (medical cotton or long fiber cotton)

l Special cleaning roll, used with the recommended cleaning solvent

l Special magnifier for fiber connectors

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

Replacing Optical Fibers

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

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

damages the optical interface.

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

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

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

Figure 1-2 Slanting optical interface

Slanting opticalinterface



10

Figure 1-3 Level optical interface

Level opticalinterface

1.6.2 Electromagnetic ExposureThis topic describes safety precautions for electromagnetic exposure.

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

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

1.6.3 Forbidden AreasThe topic describes requirements for a forbidden area.

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

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

1.6.4 LaserThis topic describes safety precautions for lasers.

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



11

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

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

Safety Instructions Regarding Lasers

To avoid laser radiation, obey the following instructions:

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

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

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

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

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

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

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

Instructions Regarding Fiber Handling

Read and abide by the following instructions before handling fibers:

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

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

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

WARNINGStrong radio frequency can harm the human body.

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



12

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

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

The requirements for working at heights are as follows:

l The personnel who work at heights must be trained.l Carry and handle the operating machines and tools with caution to prevent them from falling

down.l Safety measures, such as wearing a helmet and a safety belt, must be taken.l Wear cold-proof clothes when working at heights in cold areas.l Check all lifting appliances thoroughly before starting the work, and ensure that they are

intact.

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

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

l Only trained and qualified personnel can perform hoisting operations.l Before hoisting heavy objects, check that the hoisting tools are complete and in good

condition.l Before hoisting heavy objects, ensure that the hoisting tools are fixed to a secure object or

wall with good weight-bearing capacity.l Issue orders with short and explicit words to ensure correct operations.l Ensure that the angle between the two cables is less than or equal to 90 degrees during the

lifting, as shown in Figure 1-4.



13

Figure 1-4 Hoisting heavy objects

1.7.2 Using LaddersThis topic describes safety precautions for using ladders.

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

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

overweighing the ladder.

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



14

Figure 1-5 Slanting a ladder

Climbing Up a Ladder

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

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

l Before operations, ensure that your body is stable to reduce risks.l Do not climb higher than the fourth rung of the ladder (counted from up to down).

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

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



15

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

Drilling Holes

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

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

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

l Wear protection gloves when drilling holes.

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

Sharp Objects

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

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

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

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

Carrying Heavy Objects

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



16

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

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

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

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

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

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

Removing and Inserting a Board

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

l Slide the board along the guide rails.l Do not contact one board with another to avoid short-circuits or damage.l When holding a board in hand, do not touch the board circuits, components, connectors,

or connection slots of the board to prevent damage caused by ESD of the human body tothe electrostatic-sensitive components.

Binding Signal Cables

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

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



17

l When installing cables, ensure that the environment temperature is above 0°C.l If the cables are stored in a place where the ambient temperature is below 0°C, transfer

them to a place at room temperature and store the cables for more than 24 hours beforeinstallation.

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

High Temperature

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

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

IF Cables

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



18

2 Notices for High-Risk Operations

About This Chapter

This chapter provides notices for the operations that may cause bodily injury or equipmentdamage if they are not performed properly during the commissioning and maintenance ofmicrowave equipment.

2.1 Operation Guide for the Toggle Lever SwitchThe ODU-PWR switch on the IF board is a toggle lever switch which must be turned on and offas per the following instructions to avoid damaging the IF board.

2.2 Operation Guide for the IF JumperBefore removing or installing an IF jumper, turn off the ODU-PWR switch to avoid bodily injuryor damage to the IF board and ODU.

2.3 Operation Guide for the IF CableBefore removing or installing an IF cable, turn off the ODU-PWR switch to avoid bodily injuryor damage to the IF board and ODU.

2.4 Operation Guide for the IF BoardBefore removing or installing an IF board, turn off the ODU-PWR switch to avoid bodily injuryor damage to the IF board and ODU.

OptiX RTN 910 Radio Transmission SystemMaintenance Guide (U2000) 2 Notices for High-Risk Operations


19

2.1 Operation Guide for the Toggle Lever SwitchThe ODU-PWR switch on the IF board is a toggle lever switch which must be turned on and offas per the following instructions to avoid damaging the IF board.

Position and Description of the Toggle Lever Switch

The toggle lever switch is located on the IF board and controls the power that is fed to the ODU,as shown in Figure 2-1.

Figure 2-1 Toggle lever switch

I : ON

O: OFF

Turning On the Toggle Lever Switch1. Gently pull on the toggle lever switch out.

2. Turn it to the left.



20

3. Release the toggle lever switch.

Turning Off the Toggle Lever Switch1. Gently pull on the toggle lever switch.

2. Turn it to the right.



21

3. Release the toggle lever switch.

2.2 Operation Guide for the IF JumperBefore removing or installing an IF jumper, turn off the ODU-PWR switch to avoid bodily injuryor damage to the IF board and ODU.

Procedure

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

1 2



22

DANGEREnsure that the ODU is completely powered off before removing or installing the IF jumper.

Step 2 Remove or install the IF jumper.

----End

2.3 Operation Guide for the IF CableBefore removing or installing an IF cable, turn off the ODU-PWR switch to avoid bodily injuryor damage to the IF board and ODU.

Procedure

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

1 2

DANGEREnsure that the ODU is completely powered off before removing or installing the IF cable.

Step 2 Install or remove the IF cable.

----End



23

2.4 Operation Guide for the IF BoardBefore removing or installing an IF board, turn off the ODU-PWR switch to avoid bodily injuryor damage to the IF board and ODU.

Procedure

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

2

3

31

DANGEREnsure that the ODU is completely powered off before removing or installing the IF board.

Step 2 Disconnect the IF jumper or IF cable.

Step 3 Remove or install the IF board.

----End



24

3 Routine Maintenance

Routine maintenance operations are performed to detect and rectify hidden faults before thehidden faults cause damage to equipment and affect services. Routine maintenance operationsare preventive measures.

For the OptiX RTN 910, routine maintenance items are classified into routine maintenance itemscarried out on the network management system (NMS), field maintenance items for indoorequipment, and field maintenance items for outdoor equipment.

Routine Maintenance Items Carried Out on the NMSMaintenance Item Recomm

endedMaintenanceCycle

Remarks

Checking the NE Status Every day -

Browsing Current Alarms Every day -

Browsing History Alarms Everyweek

-

Browsing Abnormal Events Everyweek

-

Browsing Current Performance Events Everyweek

-

Browsing History Performance Events Everyweek

-

Browsing History Transmit Power andReceive Power

Everyweek

-

OptiX RTN 910 Radio Transmission SystemMaintenance Guide (U2000) 3 Routine Maintenance


25

Maintenance Item RecommendedMaintenanceCycle

Remarks

Testing IF 1+1 Switching Half ayear

Applies only to the equipment that isconfigured in 1+1 protection mode.During the 1+1 protection switching,the protected services are interrupted.Hence, it is recommended that youperform the 1+1 protection switchingwhen the traffic is light.

Testing the IF N+1 Switching Half ayear

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

Field Maintenance Items for Indoor EquipmentMaintenance Item Recommended

Maintenance CycleRemarks

Checking theTelecommunications Room

Every two months -

Maintaining theEnvironment of OutdoorCabinets

Half a year -

Field Maintenance Items for Outdoor EquipmentMaintenance Item Recommended

MaintenanceCycle

Remarks

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

Checking the Hybrid Coupler Half a year

Checking the Antenna Half a year

Checking the IF Cable Half a year

Checking the LOS Condition Half a year

OptiX RTN 910 Radio Transmission SystemMaintenance Guide (U2000) 3 Routine Maintenance


26

4 Emergency Maintenance

About This Chapter

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

4.1 Definition of EmergencyFor microwave equipment, an emergency refers to interruption of microwave services.

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

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

OptiX RTN 910 Radio Transmission SystemMaintenance Guide (U2000) 4 Emergency Maintenance


27

4.1 Definition of EmergencyFor microwave equipment, an emergency refers to interruption of microwave services.

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

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

NOTE

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



28

Main Procedure for Emergency Maintenance

Figure 4-1 Main procedure for emergency maintenance

Start

Service interruoted byexternal causes?

Yes Contact tealted departmentsto handle the problem

No

NE access successful andalaarms cleared?

Query NE status andalarms by using the NMS

YesClear the alarm

No

Rectify the fault on site

Is there an incorrectoperation?

Cancel the operation1 Yes

No

Is the service restored? Contact Huawei engineersNo

Proceed with the next step Is the servicerestored?

No

End

Yes

Check the troubleshooting result

5

4

Yes

2

3



29

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

CommentNo.

Description

1 The common incorrect operations are as follows:l Modifying data configurationl Performing loopback operationsl Shutting down the laserl Muting the ODUl Replacing boards/cablesl Loading the software

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

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

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

4 Generally, the following alarms can be cleared on the NMS:APS_MANUAL_STOP, APS_FAIL, BD_NOT_INSTALLED,DBMS_ERROR, ETH_APS_LOST, ETH_APS_SWITCH_FAIL,ETH_APS_TYPE_MISMATCH, HP_TIM, HP_UNEQ,IMA_GROUP_LE_DOWN, IMA_GROUP_RE_DOWN, J0_MM,LOOP_ALM, LPS_UNI_BI_M, LP_SLM, LP_TIM, LP_UNEQ,NESOFT_MM, NESF_LOST, RADIO_MUTE, WRG_BD_TYPE,ETH_CFM_UNEXPERI, ETH_EFM_LOOPBACK,MW_CFG_MISMATCH.

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

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

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

Table 4-2 Field maintenance operation sheet

Maintained on Maintained by

Actual Step Step in the EntireProcedure

TroubleshootingResult

Remarks



30

Maintained on Maintained by

Actual Step Step in the EntireProcedure

TroubleshootingResult

Remarks



31

Field Troubleshooting Sub-Procedure

Figure 4-2 Field troubleshooting sub-procedure

Equipment alarm?

3

No

4

YesClear the alarm

YesClear the alarm

No

5 YesClear the alarm

No


No

End

Proceed to the next step

Is the service restored?

Yes

No

Start

Obvious equipment damage?

Yes Repair or replace the equipment

No Troubleshoot the power input

Browse alarms locally by using the

LCT

2

1

No

Yes Troubleshoot the inter-connection

faulty

Locate the fault by performing loopback operations section by

section

7

Yes Troubleshoot the packet service fault

8

Radio link alarm?

No

Yes

Is the PWR indicator on the PIU on?

High order path alarm?

Low order path alarm?

Faulty inter-connection with

SDH/PDH equipment?

Packet service fault?

No



32

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

CommentNo.

Description

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

breaker is automatically turned off, find the cause (such as short circuitsor insufficient fuse capacity), and rectify the fault accordingly.

2. Check the power cables, especially the connectors of the power cables. Ifthe power cables or connectors of the power cables are incorrect, replacethe power cables or re-prepare the connectors of the power cables.

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

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

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

If you fail to log in to the created NE, ensure that the operations you performed arecorrect, and then locate and rectify the fault according to the indicators of the systemcontrol, switching, and timing board. For details about the indicators, see the OptiX RTN910 IDU Hardware Description.

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



33

CommentNo.

Description

4 Pay special attention to the following alarms:l PG_LINK_FAILl PG_PRT_DEGRADEDl MW_LIMl MW_LOFl R_LOSl R_LOFl R_LOCl MS_AISl AU_AISl AU_LOPl B1_EXCl B2_EXCl MW_BER_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 LP_UNEQl T_ALOSl E1_LOC

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

8 See 5.8 Troubleshooting Native Ethernet Service Faults, 5.9Troubleshooting Ethernet Service on the EoS/EoPDH Plane, 5.11Troubleshooting CES Services, 5.12 Troubleshooting ATM Services, and5.13 Troubleshooting Ethernet Services Carried by PWs.



34

5 Troubleshooting

About This Chapter

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

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

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

5.3 Troubleshooting the Radio LinkWhen an NE reports MW_LOF, MW_BER_EXC, MW_BER_SD or MW_FEC_UNCOR dueto failure or performance deterioration of a radio link, there is a radio link fault.

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

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

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

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

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

OptiX RTN 910 Radio Transmission SystemMaintenance Guide (U2000) 5 Troubleshooting


35

5.9 Troubleshooting Ethernet Service on the EoS/EoPDH PlaneThe Ethernet services transmitted on the EoS/EoPDH plane can be transmitted over a TDMnetwork. The faults of the EoS/EoPDH-plane Ethernet services include service interruption andservice degradation.

5.10 Troubleshooting MPLS TunnelsThis section describes how to troubleshoot MPLS tunnels by using the MPLS OAM function orMPLS Ping/Traceroute function.

5.11 Troubleshooting CES ServicesThis section describes how to troubleshoot CES services that are interrupted or degraded.

5.12 Troubleshooting ATM ServicesThis section describes how to troubleshoot ATM services that are interrupted or degraded.

5.13 Troubleshooting Ethernet Services Carried by PWsThis section describes how to troubleshoot Ethernet services that are carried by PWs andtransmitted in the PSN. These Ethernet services are considered faulty when they are interruptedor deteriorate.

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



36

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



37

General Troubleshooting Procedure

Figure 5-1 General troubleshooting procedure

Start

Record the fault phenomena

Analyze fault causes and locatethe fault

Is the faultrectified?

Report to Huawei

Make a solution together

Attempt to rectify the fault


Observe the operation


Fill in the troubleshootingreport

End

Other troubleshootingprocedures

No

Yes

Yes

Yes

No

No

No

Caused by external factors?

Yes

4

3

2

1



38

Table 5-1 General troubleshooting procedure

CommentNo.

Description

1 When recording the fault phenomena, make a true and detailed record of theentire process of the fault. Record the exact time when the fault occurs andthe operations performed before and after the fault occurs. Save the alarms,performance events, and other important information.You can use the click-to-collect function on the U2000 to collect data.


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

4 To provide feedbacks or obtain technical support, customers in China cancontact the 24-hour technical support center at 400-830-2118, and thecustomers in areas outside China can contact the local Huawei offices.

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

Fault Causesl The operation is improper.

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

l The transmission NE or link is faulty.

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

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

interruption results from an incorrect operation.2. Query alarms on the centralized NMS or the NMS that is used on the site, and then locate

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

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



39

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

Troubleshooting Procedure

Figure 5-2 General procedure for troubleshooting the service interruption

Cancel the operation

Contact relateddepartments to solve

the problem

Proceed with thenext step Service restored?

Yes

No

Clear the alarm

Start

Incorrectoperation?

Service interruptedby external causes?

End

Query NE status and alarmsby using the centralized NMS

NE access successfuland alarms cleared?

Rectify the fault on site

Yes

Yes

No

No

No

Yes

4

3

2

1



40

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

CommentNo.

Description

1 The common incorrect operations are as follows:l Modifying the data configurationl Loopbackl Shutting down the laserl Muting the ODUl Replacing the board or cablel Loading the software


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

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



41

Figure 5-3 Field troubleshooting sub-procedure

Equipment alarm?

3

No

4

YesClear the alarm

YesClear the alarm

No


No


No

End



Yes

No

Start

Obvious equipment damage?

Yes Repair or replace the equipment

No Troubleshoot the power input

Browse alarms locally by using the

LCT

2

1

No

Yes Troubleshoot the inter-connection

faulty

Locate the fault by performing loopback operations section by

section

7

Yes Troubleshoot the packet service fault

8

Radio link alarm?

No

Yes

Is the PWR indicator on the PIU on?

High order path alarm?

Low order path alarm?

Faulty inter-connection with

SDH/PDH equipment?

Packet service fault?

No



42

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

CommentNo.

Description

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

breaker is automatically turned off, find the cause (such as short circuitsor insufficient fuse capacity), and rectify the fault accordingly.

2. Check the power cables, especially the connectors of the power cables. Ifthe power cables or connectors of the power cables are incorrect, replacethe power cables or re-prepare the connectors of the power cables.

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

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

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

If you fail to log in to the created NE, ensure that the operations you performed arecorrect, and then locate and rectify the fault according to the indicators of the systemcontrol, switching, and timing board. For details about the indicators, see the OptiX RTN910 IDU Hardware Description.

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



43

CommentNo.

Description

4 Pay special attention to the following alarms:l PG_LINK_FAILl PG_PRT_DEGRADEDl MW_LIMl MW_LOFl R_LOSl R_LOFl R_LOCl MS_AISl AU_AISl AU_LOPl B1_EXCl B2_EXCl MW_BER_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 LP_UNEQl T_ALOSl E1_LOC

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

8 See 5.8 Troubleshooting Native Ethernet Service Faults, 5.9Troubleshooting Ethernet Service on the EoS/EoPDH Plane, 5.11Troubleshooting CES Services, 5.12 Troubleshooting ATM Services, and5.13 Troubleshooting Ethernet Services Carried by PWs.

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



44

5.3 Troubleshooting the Radio LinkWhen an NE reports MW_LOF, MW_BER_EXC, MW_BER_SD or MW_FEC_UNCOR dueto failure or performance deterioration of a radio link, there is a radio link fault.

Context

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

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

l RADIO_TSL_HIGHl RADIO_TSL_LOWl TSL_CURl TSL_MAXl TSL_MINl TSL_AVG

NOTE

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

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

l RADIO_FADING_MARGIN_INSUFFl RADIO_RSL_BEYONDTHl RADIO_RSL_HIGHl RADIO_RSL_LOWl RSL_CURl RSL_MAXl RSL_MINl RSL_AVG

NOTE

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

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

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



45

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

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

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

Fault Causes

Table 5-4 Causes of radio link faults

Fault Common Fault Cause

The transmit power is abnormal. The ODU is faulty.

The receive power is always lower than thenormal value.

l The antenna direction is not adjustedproperly.

l The antennas have different polarizationdirections.

l There is a mountain or building in thetransmit direction.

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

l The ODU is faulty.

The receive power is abnormal due to slowdown fading.

The fading margin is insufficient.

The receive power is abnormal due to fastfading.

The multipath fading is fast.

The receive power is normal or slow upfading occurs, but the signal-noise ratio(SNR) is abnormal.

There is external interference.



46

NOTE

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

l Up fading

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

l Down fading

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

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

l Fast fading

The fading lasts from several milliseconds to tens of seconds.

Generally, fast fading is caused by multipath fading. It occurs periodically. To be specific, fast fadingoccurs in the period from 18:00 to 20:00 of a day or in a certain season of a year.

l Slow fading

The fading lasts from tens of seconds to several hours.

Generally, slow up fading is caused by interference. Slow down fading is caused by rain, and thereforeis also called rain fading. Rain fading occurs on links working at a frequency of 10 GHz or in areaswhere heavy rain occurs.

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

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

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

type.5. If the receive power is normal but the SNR is abnormal, check whether there is interference

before you proceed.6. If the preceding methods cannot locate faults, perform loopback operations.



47


Figure 5-4 Procedure for troubleshooting the radio link

Start

ODU or IF related alarm?

Yes

Clear the alarm

No


Is the fault rectified?

End

Yes

No

Transmit power normal?

Yes

No

2

Rectify the fault

Perform loopback operations

9

No

Rectify the fault

YesRectify the fault

No

4


1

5

6Yes

No

Rectify the fault

8Yes

Yes

No

No

Rectify the fault

7Yes

Incorrect operation?

RSL always lower than the normal

value?

Slow down fading causes abnormal

RSL?

Fast fading causes abnormal

RSL?

Radio link faulty in one direction?

Query the receive/transmit power

and SNR

3



48

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

Comment No. Description

1 Rectifyincorrectoperations.

Check the following points:l Check whether the ODU is powered off.l Check whether the ODU is muted.l Check whether the IF board is looped back.l Check whether the data configuration at the transmit end is the same

as the data configuration at the receive end.l Check whether the data configuration matches the types of the ODU

and the hybrid coupler.

2 Rectifyequipment faults.

Pay special attention to the following alarms:l VOLT_LOSl CONFIG_NOSUPPORTl HARD_BADl TEMP_ALARMl IF_INPWR_ABNl RADIO_MUTEl RADIO_TSL_HIGHl RADIO_TSL_LOWl RADIO_RSL_HIGHl RADIO_RSL_LOWl IF_CABLE_OPENl MW_CFG_MISMATCH

3 Query thereceive/transmitpower, and theSNR

Query the receive/transmit power, and the SNR in the latest one week.For details, refer to Querying the Historical Transmit Power and ReceivePower and Querying the SNR Values of a Radio Link.

4 Troubleshootthe anomaly ofthe transmitpower.

Replace the ODU.



49


5 Troubleshootthe anomaly thatthe receive poweris lower than thenormal value.

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

installation of the antenna. Ensure that the azimuth angle of theantenna meets 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 ina wide range.

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

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

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

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

6. Check whether the IF cable is soggy, broken, or pressed. If yes,replace the IF cable.

7. Check whether there is a mountain or building in the transmitdirection. If the line of sight (LOS) is unavailable, adjust the height orposition of the antenna.

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

9. Check whether the gains of the antennas at the receive and transmitends comply with the specifications. Replace the antenna whose gaindoes not comply with the specifications.

6 Troubleshootslow downfading.

Contact the network planning department to make the following changes:l Increase the fade margin on links.l Use low-frequency ODUs.l Use vertical polarization instead of horizontal polarization.



50


7 Troubleshootfast fading.

Contact the network planning department to make the following changes:l Adjust the position of the antenna to reduce the multipath fading.

1. Adjust the height of the antennas at both ends to increase the heightdifference between the antennas.

2. In the case of strong reflection surfaces such as water surfaces,plains, and smooth mountaintops, adjust the antenna to removereflection points. Alternatively, use the actual terrain to masksurface reflection.

3. Lower the antenna height to reduce the path margin with LOSconditions guaranteed.

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

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

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



51


8 Troubleshootinterference.

The troubleshooting procedure is as follows:1. There is co-channel interference.

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

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

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

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

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

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

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

3. Use Huawei frequency scanning scripts or a spectrum analyzer toanalyze the interference source.

4. Contact the network planning department to modify the networkingplanning and design.1. Plan Tx high sites and Tx low sites correctly to avoid using them

at the same time.2. Plan frequencies or polarization modes correctly to avoid the same

polarization direction for microwave signals and interferencesignals. Plan routes correctly.

5. Contact the spectrum management department to clear theinterference spectrum.

9 Performloopbackoperations tolocate the fault.

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

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

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



52

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

incipient faults.

l Periodically collect and analyze the data about the changes in the transmit power and receivepower so that you can detect and then rectify the incipient faults accordingly in time.

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

Fault Phenomena

The IF bit errors refer to the bit errors that the IF board detects through the self-defined overheadbyte in the microwave frame. The related alarms and performance events are as follows:

l MW_BER_EXCl MW_BER_SDl MW_CFG_MISMATCHl MW_LOFl IF_BBEl IF_ESl IF_SESl IF_CSESl IF_UAS

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

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

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



53

l B2_EXCl B2_SDl MS_CROSSTRl MSBBEl MSESl MSSESl MSCSESl MSUAS

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

l B3_EXCl B3_SDl HP_CROSSTRl HPBBEl HPESl HPSESl HPCSESl HPUAS

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

l BIP_EXCl BIP_SDl LP_CROSSTRl LPBBEl LPESl LPSESl LPCSESl LPUAS



54

Fault Causes

Table 5-6 Causes of bit errors


There are IF bit errors. l The radio link is faulty.Check whether the MW_BER_EXC,MW_BER_SD, MW_FEC_UNCOR,MW_LOF or RPS_INDI alarm isreported. If yes, the radio link is faulty.

l The services are incorrectly configured.Check whether theMW_CFG_MISMATCH alarm isreported. If yes, the number of E1 servicesis inconsistent on both ends of the radiolink.

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

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

the optical line are as follows: theoptical fiber line, the optical power isabnormal, the fiber performancedeteriorates, or the fiber connector isnot clean.

– In the case of bit errors on the radiolink, check whether theMW_BER_EXC, MW_BER_SD,MW_FEC_UNCOR or RPS_INDIalarm is reported. If yes, the radio linkis faulty.

l The line processing unit or IF board isfaulty.

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

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



55


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

l The line processing unit or IF board isfaulty.

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

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

There are only LP bit errors. l The tributary board is faulty.l The cross-connect unit is faulty.l The working temperature of the board is

excessively high.l The working temperature of the cross-

connect unit is excessively high.l There is a power surge or an external

interference source, or the equipment isnot properly grounded. (This cause doesnot need to be considered during thetroubleshooting of an IF board.)

Fault Locating Methods1. Analyze the equipment alarms and performance events that are related to service

configuration errors and bit errors.2. When there are many types of alarms and performance events on a service path, first analyze

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

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

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



56


Figure 5-5 Procedure for troubleshooting bit errors

Start

Is there anequipment alarm?

No

Yes Clear the alarm

Is there an RS bit error alarm or a

performanceevent?

Yes

Troubleshoot RS bit errorson the IF board

No

Is there anMS/ HP alarm or

performanceevent?

Yes Troubleshoot MS/HP biterrors

No

Is there an LPalarm?

Yes Troubleshoot LP biterrors

Locate the fault by performingloopback operations section

by section

No

Proceed with the next stepIs the faultrectified?

End

Yes

No

Is there a pointerjustification event?

Yes Troubleshoot the pointerjustification

No

If thealarmingboard is

Troubleshoot RS bit errorson the SDH optical interface

board

IF board

SDH opticalinterface board

2

3

4

5

6

1



57

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

CommentNo.

Description

1 Pay special attention to the following alarms:l TEMP_ALARMl HARD_BADl MW_CFG_MISMATCH

2 See 5.5 Troubleshooting Pointer Justifications.

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

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

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

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

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

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

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

MW_BER_SD, MW_FEC_UNCOR, MW_LOF, RPS_INDI,B1_EXC, B1_SD, or RS_CROSSTR alarm.

2. If any of the alarms are reported, see 5.3 Troubleshooting the RadioLink and rectify the fault.

3. If none of the alarms occurs, replace the IF board.

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

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

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



58

CommentNo.

Description

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

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

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

Experience and SummaryNOTE

The TDM services mentioned refer to Native TDM services.The handling procedure applies when the STM-1e port. is faulty

l During the routine maintenance, check bit error performance events periodically and handlethem in time.

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

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

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

l AUPJCHIGHl AUPJCLOWl AUPJCNEW

NOTE

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

When the service is configured to be at the VC-12 level, apply the reframing process to terminatethe AU pointer justification. The terminating method is to transform the AU pointer justificationinto the TU pointer justification. The performance events related to the TU pointer justificationare as follows:

l TUPJCHIGHl TUPJCLOWl TUPJCNEW

NOTE

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



59

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

are two clock sources on the same network or a timing loop occurs.l The fiber connections are incorrect. As a result, a timing loop occurs.l The quality of the clock source declines, the clock unit is faulty, or there are other clock-

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

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

Fault Fault Locating Method

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

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

the station whose clock is asynchronouswith the entire network.

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

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

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

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

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



60


Figure 5-6 Procedure for troubleshooting pointer justifications

Start

Is there a clock-relatedalarm?

No

YesClear the alarm

Incorrect fiberconnection?

YesReconnect the fibers

No

An AU pointerjustification event?

Yes

No

A TU pointerjustification event?

Yes

Proceed with thenext step Is the fault rectified?

End

Yes

No

Incorrectconfiguration?

Modify the dataconfiguration

No

Check the clockconfiguration

Yes

Check the fiberconnection

Locate the faulty boardLocate the NE whose clockis out of synchronization

Locate the faulty boardLocate the NE whose clockis out of synchronization

No

1

2

3

4

6

5

7



61

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

CommentNo.

Description

1 Pay special attention to the following alarms:l TEMP_ALARMl 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 on the entire network.l Check whether a timing loop is generated.

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

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

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

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

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

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

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

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

5 Replace the possibly faulty boards.



62

CommentNo.

Description

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

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

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

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

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

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

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

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

Experience and Summary

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

5.6 Troubleshooting the Interconnection with SDHEquipment

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

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

method of the equipment of certain vendors.

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



63

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

l The overhead bytes at both ends are inconsistent.l The indexes of the SDH interfaces do not meet the requirements.

NOTE

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

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



64


Figure 5-7 Procedure for troubleshooting the interconnection with 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



65

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

CommentNo.

Description

1 Pay special attention to the following alarms:l J0_MMl HP_TIMl LP_TIMl HP_SLMl LP_SLM

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 are as follows: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 rectify an interconnection fault, you must be familiar with the characteristics of the interfaceson the interconnected equipment.

5.7 Troubleshooting the Interconnection with PDHEquipment

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



66

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

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



67


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

Start

Is there animpedance mismatch?

Yes Replace the cable or thetributary board

Check the cables

Is in good conditions?No

Yes

Proceed with the next step Is the fault rectified?

End

Yes

No

Is the cable acoaxial cable?

No

Check the impedance ofthe interfaces

Yes

Adjust the cables

Test the indexes ofinterfaces

Do the interfacesmeet standards?

Troubleshoot the faultson the local equipment

Troubleshoot the faults onthe interconnected

equipment

Yes

No

Check the grounding

No

1

2

3

4



68

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

CommentNo.

Description

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

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

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

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

same manner.NOTE

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

3 Check the following points:l Check whether the wires of the cable are correctly connected.l Check whether the cable is broken or pressed.l Check whether the cable signal is interfered (for example, when the trunk

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

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

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

Experience and SummaryNOTE

The PDH services mentioned refer to Native E1 services.

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



69

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

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

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

Table 5-11 Common faults of Ethernet services

Symptom Alarm Board

Ethernet services areinterrupted.

HARD_BAD,TEMP_ALARM,WRG_BD_TYPE, orBD_STATUS

EM6TB, EM4F, EM4T,EM6X, EM6TA, EM6FA,EM6F, EM6T

COMMUN_FAIL,LAG_DOWN

ETH_LOS,ETH_EFM_LOOPBACK,or LOOP_ALM

LASER_MOD_ERR EM6F, EM6X or EM4F

Ethernet services aredegraded.

HARD_BAD orTEMP_ALARM

EM4F, EM4T, EM6X,EM6TA, EM6FA, EM6F orEM6T

FLOW_OVER orLAG_MEMBER_DOWN

EM4F, EM4T, EM6X,EM6TA, EM6FA, EM6F orEM6T

AM_DOWNSHIFT ISU2, ISX2, IFU2 or IFX2

Fault Causesl The possible human factors are as follows:

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



70

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

– The service configuration is incorrect.l The equipment at the local end is faulty.l The line board is faulty or has bit errors.l When the AM function is enabled, the Ethernet service bandwidth decreases due to the

downward AM switch.l The interconnected equipment is faulty.l The network cable is faulty.l The external electromagnetic interference is severe.

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



71


Figure 5-9 Procedure for troubleshooting Ethernet service faults

Any abnormal RMON performance

events?

Clear the alarm

6

No

YesAn equipment alarm or alarm on

the radio link?

An Ethernet alarm?Yes

No

YesTroubleshoot the fault

according to the flow of handling RMON

performance events

3

2

Troubleshoot equipmentfaults by performingloopbacks section by

section or replacing boards

Proceedwith the

next stepIs the fault rectified?

End

Yes

No

A loop formed by the E-LAN service

trails?

No

No

YesRelease the loop

Start

Incorrect operation?1

Cancel this operation

No

Yes

44

3

2

1

Query the port and service traffic and analyze the fault

causes

Clear the alarm

5

No



72

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

CommentNo.

Description

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

enabled state, working mode, and flow control, are the same as theparameter settings of the Ethernet port on the interconnected equipment

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

2 Pay special attention to the following equipment alarms:l POWER_ALMl FAN_FAILl HARD_BADl BD_STATUSl NESF_LOSTl TEMP_ALARMl RADIO_RSL_HIGHl RADIO_RSL_LOWl RADIO_TSL_HIGHl RADIO_TSL_LOWl IF_INPWR_ABNl AM_DOWNSHIFTPay special attention to the following line alarms:l MW_LIMl MW_LOFl MW_BER_EXCl MW_BER_SDl MW_RDIl MW_FEC_UNCOR

3 Pay special attention to the following alarms:l ETH_LOSl ETH_NO_FLOWl LAG_DOWNl LAG_MEMBER_DOWNl FLOW_OVER

4 Follow instructions in Detecting E-LAN Service Loops to check whether E-LAN services are looped back. Release the loops if any are formed.



73

CommentNo.

Description

5 Query the rate of an Ethernet port and locate faults based on the analysisof Ethernet port rates.l If the Ethernet port connecting the peer equipment has a too high or too

low receive rate, the peer equipment is faulty.l If the rate of the Integrated IP radio port approaches or reaches the license

capacity of the IF port, the license capacity is too low and you need toapply for a license allowing for a higher capacity.

l If the transmit rate of the Integrated IP radio port approaches or reachesthe maximum Ethernet bandwidth of the IF port, the bandwidth of the IFport is too low and needs to be increased by the network planningpersonnel.

l If the transmit rate of the Integrated IP radio port is much lower than thereceive rate of the Ethernet port, or if the receive rate of the Integrated IPradio port is much higher than the transmit rate of the Ethernet port, thelocal end is faulty. Locate the fault as follows:– Check the Ethernet service configuration and QoS configuration.– By querying QoS packet loss data in RMON events on the NMS, check

whether QoS settings are correct according to the packet loss data.– Check the Ethernet interface board, IF board, and system control,

switching and timing board by means of board replacement.If the transmitted traffic is equal to the received traffic, query the traffic onthe same port in each VLAN to check whether bandwidth preemption occurs.

6 For RMON performance events, see the D RMON Event Reference.



74

Figure 5-10 Procedure for troubleshooting an RMON performance event

Is it a MTU settingproblem?

Yes Modify the MTUvalue

No

Proceed withthe next step


End

Yes

No

No

Is the test passed?

No

Yes

Use a meter to perform the test

Rectify the fault of theinterconnected equipment

Rectify the equipment fault byloopback section by section or

replacing the board

5

Are broadcast packetsexcessive?

No

Yes Handle the problem onexcessive broadcast

packets

4

Start

Rectify the fault of line biterrors

No

YesIs there any FCS error?

Is there any collisionor fragment?

Yes Check the working modeof the port

2

3

View the statistics groupperformance on an Ethernet port

1

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

CommentNo.

Description

1 8.17 Querying Traffic, Physical Bandwidth, or Bandwidth Utilization ofEthernet Ports to obtain the real-time performance statistics data of theEthernet port.



75

CommentNo.

Description

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

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

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

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

samel Whether the working modes (full duplex or half duplex) of the Ethernet

port on the equipment at both ends are the samel Whether the Ethernet port is set to auto-negotiation mode at one end and

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

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

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

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

5.9 Troubleshooting Ethernet Service on the EoS/EoPDHPlane

The Ethernet services transmitted on the EoS/EoPDH plane can be transmitted over a TDMnetwork. The faults of the EoS/EoPDH-plane Ethernet services include service interruption andservice degradation.

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



76


Symptom Alarm Board


HARD_BAD,TEMP_ALARM,WRG_BD_TYPE, orBD_STATUS

EMS6/EFP8

ALM_GFP_dLFD orALM_GFP_dCSF

ETH_LOS or LOOP_ALM

LAG_PORT_FAIL,LAG_VC_PORT_FAIL,LCAS_TLCT, orLCAS_TLCR

Ethernet services areabnormal.

HARD_BAD orTEMP_ALARM

FLOW_OVER

LCAS_FOPT,LCAS_FOPR,LCAS_PLCT, orLCAS_PLCR

Fault Causesl The possible human factors are as follows:

– An Ethernet board loopback or a transmission line loopback occurs.– The parameter settings of the Ethernet ports, such as the port enabled state, working

mode, and flow control, are different from the parameter settings of the Ethernet portson the interconnected equipment.

– The configuration of the encapsulation/mapping protocol or the LCAS protocol isinconsistent on both ends of the link.

– The timeslot binding of VCTRUNKs is inconsistent on both ends of the link– 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 The interconnected equipment is faulty.l The network cable is faulty.l The external electromagnetic interference is severe.

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



77

3. Locate the fault cause according to the RMON performance events and alarms.


Figure 5-11 Procedure for troubleshooting Ethernet service faults

Any abnormal RMON performance

events?

Clear the alarm

5

No

YesAn equipment alarm or alarm on the radio

link?

An Ethernet alarm?

Yes Query the port and service traffic and analyze the fault

causes

No

Fault on theopposite

equipment?

Yes Troubleshoot the fault according to the flow of handling RMON

performance events

Yes Troubleshoot faults on theopposite equipment

No

3

2

Troubleshoot equipmentfaults by performing

loopbacks section bysection or replacing boards

Proceedwith thenext step

Is the fault rectified?

End

Yes

No

A loop formed by the E-LAN service trails?

No

No

YesRelease the loop

Start

Incorrect operation?1

Cancel this operation

No

Yes

Clear the alarm

4

5

4

3

2

1



78

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

CommentNo.

Description

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

enabled state, working mode, and flow control, are the same as theparameter settings of the Ethernet port on the interconnected equipment

l The configuration of the encapsulation/mapping protocol or the LCASprotocol is inconsistent on both ends of the link.

l The timeslot binding of VCTRUNKs is inconsistent on both ends of thelink.

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

2 Pay special attention to the following equipment alarms:l POWER_ALMl FAN_FAILl HARD_BADl BD_STATUSl NESF_LOSTl TEMP_ALARMl RADIO_RSL_HIGHl RADIO_RSL_LOWl RADIO_TSL_HIGHl RADIO_TSL_LOWl IF_INPWR_ABNPay special attention to the following line alarms:l MW_LIMl MW_LOFl R_LOSl R_LOFl MS_AISl AU_AISl AU_LOPl B1_EXCl B2_EXC



79

CommentNo.

Description

3 Pay special attention to the following alarms:l ETH_LOSl FLOW_OVERl ALM_GFP_dCSFl ALM_GFP_dLFDl FCS_ERRl LCAS_PLCTl LCAS_TLCTl LCAS_PLCRl LCAS_TLCRl LCAS_FOPTl LCAS_FOPR

4 If the LOOP_ALM alarm is reported after the configuring the AdvancedAttributes of Ethernet Interfaces operation is performed, it indicates that thenetwork to which Ethernet ports are connected has loops.

5 For RMON performance events, see C Performance Event Reference.



80

Figure 5-12 Procedure for troubleshooting an 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

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

CommentNo.

Description

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



81

CommentNo.

Description

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

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

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

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

samel Whether the working modes (full duplex or half duplex) of the Ethernet

port on the equipment at both ends are the samel Whether the Ethernet port is set to auto-negotiation mode at one end and

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

4 Check the following points:l Whether the flow control method is the same.l Whether the Ethernet service traffic exceeds the bandwidth of the

VCTRUNK.

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

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.

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

5.10 Troubleshooting MPLS TunnelsThis section describes how to troubleshoot MPLS tunnels by using the MPLS OAM function orMPLS Ping/Traceroute function.

Fault PhenomenaCommon faults of MPLS tunnels are as follows.



82

l MPLS tunnels fail to be created, and services are unavailable.l MPLS tunnels are faulty, and services are interrupted.l MPLS APS switching fails, services are interrupted, and packet loss or bit errors occur.

Table 5-17 Common faults of MPLS tunnels

Symptom Alarm Board

MPLS tunnels are faulty. HARD_BAD,TEMP_ALARM,WRG_BD_TYPE,BUS_ERR, BD_STATUS,MPLS_TUNNEL_OAM-FAIL,MPLS_TUNNEL_LOCV,MPLS_TUNNEL_Excess,MPLS_TUNNEL_MIS-MATCH,MPLS_TUNNEL_MIS-MERGE,MPLS_TUNNEL_UN-KNOWN,MPLS_TUNNEL_BDI,MPLS_TUNNEL_FDI,MPLS_TUNNEL_SD,MPLS_TUNNEL_SF

CSHA, CSHB, CSHC,CSHD, CSHE

AM_DOWNSHIFTMW_CFG_MISMATCHMW_LIMMW_LOF

ISU2, ISX2, IFU2, or IFX2

Fault Causesl Incorrect operations are performed.

– The transmission link is looped back.– Service configuration data is inconsistent between the local end and the opposite end.– Service configuration is incorrect.

l The local NE is faulty.l The transmission link is faulty or has bit errors.l Service bandwidth decreases due to an AM downshift.l The opposite NE is faulty.l External electromagnetic interference is severe.

Fault Locating Methods1. Check whether the data is modified, whether the line is looped back, and whether any boards

are replaced.



83

2. Handle the link alarms on the MPLS server trail.

3. Locate the faulty section by using the LSP Traceroute function.

4. Locate the fault by replacing boards.


Figure 5-13 Procedure for troubleshooting MPLS tunnels

Clear the alarm

No

Yes

Yes

Troubleshoot equipment faults byperforming loopbacks on sections

or replacing boards

Contact Huaweitechnical engineers

Faults are rectified?

End

Yes

No

Clear the alarm

Start

Any incorrectoperation?


No

Yes

Any equipment- orlink-related alarm?

No

Any alarm related to MPLStunnel ?

YesHandle the fault

No

Any fault ofinterconnection

equipment

3

2

1

Table 5-18 Description of the procedure for troubleshooting MPLS tunnels

CommentNo.

Description

1 Check the following points:l Whether a loopback is set for E1 portsl Whether a loopback is set for the transmission linkl Whether the parameter settings such as the working mode of Ethernet ports

match those of the opposite NEl Whether the parameter settings such as frame format and frame mode at

E1 ports match those of the opposite NEl Whether MPLS service configuration is correct, especially whether tunnel

attributes are set correctly



84

CommentNo.

Description

2 Pay special attention to the following equipment alarms:l POWER_ALMl FAN_FAILl HARD_BADl BD_STATUSl BUS_ERRl NESF_LOSTl TEMP_ALARMl RADIO_RSL_HIGHl RADIO_RSL_LOWl RADIO_TSL_HIGHl RADIO_TSL_LOWl IF_INPWR_ABNl AM_DOWNSHIFTl MW_CFG_MISMATCHPay special attention to the following line alarms:l MW_LIMl MW_LOFl MW_BER_EXCl MW_BER_SDl MW_RDIl MW_FEC_UNCOR

3 Pay special attention to the following alarms:l MPLS_TUNNEL_BDIl MPLS_TUNNEL_Excessl MPLS_TUNNEL_FDIl MPLS_TUNNEL_LOCVl MPLS_TUNNEL_MISMATCHl MPLS_TUNNEL_MISMERGEl MPLS_TUNNEL_OAMFAILl MPLS_TUNNEL_SDl MPLS_TUNNEL_SFl MPLS_TUNNEL_UNKNOWN

Experience and SummaryLearn about the working principle and protocol configuration of MPLS tunnels beforetroubleshooting MPLS tunnels.



85

5.11 Troubleshooting CES ServicesThis section describes how to troubleshoot CES services that are interrupted or degraded.

Fault Phenomena

CES services are interrupted if they are completely unavailable. CES services are degraded ifthey have packet loss or incorrect packets.

Table 5-19 Common faults of CES services

Symptom Alarm Board

CES services are interrupted. HARD_BAD,TEMP_ALARM,WRG_BD_TYPE,BUS_ERR, BD_STATUS,CES_LOSPKT_EXC

CSHA, CSHB, CSHC,CSHD, CSHE, ML1, MD1,MP1

AM_DOWNSHIFTMW_CFG_MISMATCH


CES services are degraded. HARD_BAD,TEMP_ALARM,CES_JTROVR_EXC,CES_JTRUDR_EXC,CES_MALPKT_EXC,CES_MISORDERPKT_EXC, CES_STRAYPKT_EXC





– The transmission link is looped back.

– Service configuration data is inconsistent between the local end and the opposite end.

– Service configuration is incorrect.l The clock source is asynchronous.l Jitters and delays on the network are too great.l The local NE is faulty.l The transmission link is faulty or has bit errors.l Service bandwidth decreases due to an AM downshift.l The opposite NE is faulty.l External electromagnetic interference is severe.



86

Fault Locating Methods1. Check whether the data is modified, whether the line is looped back, and whether any boards

are replaced.2. Check whether the PW works properly by using the PW ping function. If the PW is faulty,

check whether the MPLS tunnel works properly by using the LSP ping function. If theMPLS tunnel works properly, check whether the PW has the same configuration at bothends. If the configuration is the same, replace the board on the NNI side.

3. If the PW works properly, check whether the PE data configured at both ends is the same.If the PE data is different, change the PE data to the same.

4. Check whether UNI-side data and CE-side data are consistent.5. Analyze the RMON performance events of CES services.6. Check whether there is impedance mismatch on channels and whether any electrical cables

are connected incorrectly.7. Replace Smart E1 processing boards.



87


Figure 5-14 Procedure for troubleshooting CES services

Clear the alarm

No

Yes

Yes

YesClear the alarm


or replacing boards



End

Yes

No

Clear the alarm

Start



No

Yes


No

No

Any alarm related totunnels/PWs?

Any alarm on E1ports?

YesHandle the fault

No

Any fault ofinterconnection with

PDH equipment

7

5

3

2

1

YesHandle the performance event

No

Any RMONperformance event?

6

YesClear the alarm

Any alarm related toCES services?

4



88

Table 5-20 Description of the procedure for troubleshooting CES services

Comment No.

Description

1 Check the following points:l Whether a loopback is set for the E1 portl Whether a loopback is set for the transmission linkl Check whether the parameter settings of CES services, PWs, and tunnels are

consistent at the source end and sink end.l Check whether the parameter settings of physical ports (including frame

format, code, electrical port impedance, and overhead byte), are consistent.l Check whether the network bandwidth is sufficient for the service traffic.




89

Comment No.

Description


4 Pay special attention to the following alarms:l CES_JTROVR_EXCl CES_JTRUDR_EXCl CES_LOSPKT_EXCl CES_MALPKT_EXCl CES_MISORDERPKT_EXCl CES_STRAYPKT_EXC

5 Pay special attention to the following alarms:l T_ALOSl UP_E1_AISl LFAl LMFAl DOWN_E1_AISl ALM_E1RAI

6 Pay special attention to the following alarms:l CES_MISORDERPKTl CES_LOSPKTl CES_MALPKTl CES_JTRUDRl CES_JTROVRl CES_STRAYPKT

7 Troubleshoot the interconnection with the PDH equipment.



90


Learn about the working principle and protocol configuration of CES services beforetroubleshooting CES services.

5.12 Troubleshooting ATM ServicesThis section describes how to troubleshoot ATM services that are interrupted or degraded.

Fault Phenomena

ATM services are interrupted if they are completely unavailable. ATM services are degraded ifthey have packet loss or incorrect packets.

Table 5-21 Common faults of ATM services

Symptom Alarm Board

ATM services areinterrupted.

HARD_BAD,TEMP_ALARM,WRG_BD_TYPE,BUS_ERR, BD_STATUS,ALM_IMA_LIF,ALM_IMA_LODS,ALM_IMA_RE_RX_UN-USABLE,ALM_IMA_RE_TX_UN-USABLE,IMA_GROUP_LE_DOWN,IMA_GROUP_RE_DOWN,LCD




ATM services are degraded. HARD_BAD,TEMP_ALARM,ALM_IMA_LIF,ALM_IMA_LODS,ALM_IMA_RE_RX_UN-USABLE,ALM_IMA_RE_TX_UN-USABLE, OCD







91

– The transmission link is looped back.– Service configuration data is inconsistent between the local end and the opposite end.– Service configuration is incorrect.

l The local NE is faulty.l The transmission link is faulty or has bit errors.l Service bandwidth decreases due to an AM downshift.l The opposite NE is faulty.l External electromagnetic interference is severe.

Fault Locating Methods1. Check whether the data is modified, whether the link is looped back, and whether any

boards are replaced.2. Check whether the PW works properly by using the PW ping function. If the PW is faulty,

check whether the MPLS tunnel works properly by using the LSP ping function. If theMPLS tunnel works properly, check whether the PW has the same configuration at bothends. If the configuration is the same, replace the board on the NNI side.


4. Check whether UNI-side data and CE-side data are consistent.5. Analyze the RMON performance events of ATM services.6. Check whether there is impedance mismatch on channels and whether any electrical cables

are connected incorrectly.7. Replace Smart E1 processing boards.



92


Figure 5-15 Procedure for troubleshooting ATM services

Clear the alarm

No

Yes

Yes

YesClear the alarm


or replacing boards



End

Yes

No

Clear the alarm

Start



No

Yes


No

No

Any alarm related to ATMservices?

Any alarm at the E1port?

YesHandle the fault

No


PDH equipment

6

4

3

2

1


No


5



93

Table 5-22 Description of the procedure for troubleshooting ATM services

CommentNo.

Description

1 Check the following points:l Whether a loopback is set for the E1 portl Whether a loopback is set for the transmission linkl Whether the parameter settings of ATM VPI/VCI, PWE3 CW, PW, and

Tunnel are consistent between the source end and the sink end.l Whether the parameter settings of interconnected ports are consistent

– Whether E1 frame format, coding, overhead bytes, and E1 timeslotmode (30/31) are correctly configured

– Whether IMA parameters (including protocol version, clock mode,frame length, and maximum differential delay) are correctlyconfigured

l Check whether the network bandwidth is sufficient for the service traffic.




94

CommentNo.

Description

3 Pay special attention to the following alarms:l ALM_IMA_LIFl ALM_IMA_LODSl ALM_IMA_RE_RX_UNUSABLEl ALM_IMA_RE_TX_UNUSABLEl IMA_GROUP_LE_DOWNl IMA_GROUP_RE_DOWNl OCDl LCD

4 Pay special attention to the following alarms:l T_ALOSl UP_E1_AISl LFAl LMFAl DOWN_E1_AIS

5 Pay special attention to the following alarms:l ATMPW_UNKNOWNCELLSl ATM_UNCORRECTED_HCSERR


Experience and SummaryLearn about the working principle and protocol configuration of ATM services beforetroubleshooting ATM services.

5.13 Troubleshooting Ethernet Services Carried by PWsThis section describes how to troubleshoot Ethernet services that are carried by PWs andtransmitted in the PSN. These Ethernet services are considered faulty when they are interruptedor deteriorate.

Fault SymptomsEthernet services are interrupted if they are completely unavailable. Ethernet services deteriorateif they have great delays, packet loss, or incorrect packets.



95


Symptom Alarm Board


HARD_BAD,TEMP_ALARM,WRG_BD_TYPE,BUS_ERR, BD_STATUS

EM6TB, EM4F, EM4T,EM6X, EM6TA, EM6FA,EM6F or EM6T

COMMUN_FAIL,LAG_DOWN

ETH_LOS,ETH_EFM_LOOPBACK,or LOOP_ALM

LASER_MOD_ERR EM6FA, EM6F, EM6X orEM4F

Ethernet services deteriorate. HARD_BAD orTEMP_ALARM


FLOW_OVER orLAG_MEMBER_DOWN


AM_DOWNSHIFT ISU2, ISX2, IFU2 or IFX2


– The transmission link is looped back.

– Service configuration data is inconsistent between the local end and the opposite end.

– Service configuration is incorrect.

l The local NE is faulty.

l The transmission link is faulty or has bit errors.

l Service bandwidth decreases due to an AM downshift.

l The opposite NE is faulty.

l External electromagnetic interference is severe.

Fault Locating Methods1. Check whether the data is modified, whether the link is looped back, and whether any

boards are replaced.

2. Check whether the PW works properly by using the PW ping function. If the PW is faulty,check whether the MPLS tunnel works properly by using the LSP ping function. If theMPLS tunnel works properly, check whether the PW has the same configuration at bothends. If the configuration is the same, replace the board on the NNI side.



96


4. Check whether UNI-side data and CE-side data are consistent.5. Analyze the RMON performance events of Ethernet services.6. Check whether there is impedance mismatch on channels and whether any electrical cables

are connected incorrectly.7. Replace Ethernet interface boards.


Figure 5-16 Procedure for troubleshooting Ethernet services carried by PWs

Clear the alarm

No

Yes

Yes

YesClear the alarm


or replacing boards



End

Yes

No

Clear the alarm

Start



No

Yes


No

No

Any alarm related to tunnels/PWsthat carry services?

Any alarm on theUNI side?

YesHandle the fault

No


PDH equipment

6

4

3

2

1


No


5



97

Table 5-24 Description of the procedure for troubleshooting Ethernet services carried by PWs

CommentNo.

Description

1 Check the following points:l Whether a loopback is set for the E1 portl Whether a loopback is set for the transmission linkl Whether the parameter settings of ATM VPI/VCI, PWE3 CW, PW, and

tunnel are consistent between the source end and the sink endl Whether the parameter settings of interconnected ports are consistent

– Whether E1 frame format, coding, overhead bytes, and E1 timeslotmode (30/31) are correctly configured

– Whether IMA parameters (including protocol version, clock mode,frame length, and maximum differential delay) are correctlyconfigured

l Check whether the network bandwidth is sufficient for the service traffic.




98

CommentNo.

Description


4 Check the following points:l Whether the UNI-side performance of the faulty service is normall Whether the working mode and tag attribute of the UNI are the same as

those of its interconnected portPay special attention to the following alarms:l ETH_LOSl ETH_CFM_UNEXPERI

5 For RMON performance events, see D RMON Event Reference.



Learn about the working principle and protocol configuration of Ethernet services carried byPWs before troubleshooting these services.

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

Fault Causesl The phone set is set incorrectly.

l The phone line is connected incorrectly.

l The orderwire is configured incorrectly.

l The orderwire unit is faulty.

l The system control unit is faulty.

l The line unit or radio link is faulty.



99

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

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


Figure 5-17 Procedure for troubleshooting orderwire faults

Start

Is the phonecorrectly set?

NoModify the phone setting

Check the orderwireconfiguration

Is the configurationcorrect?

No

Yes

Proceed with the next step Is the fault rectified?

End

Yes

No

Is the phone linecorrectly connected?

Yes

Check the phone setting

No

Modify the configuration

Replace the possibly faultyboard

Reconnect the phone line

Yes

3

2

1



100

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

CommentNo.

Description

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

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

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

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

2 Check the following points:l Whether all orderwire phone numbers on a subnet are of the same lengthl Whether all orderwire phone numbers on a subnet are uniquel Whether the overhead bytes of all the NEs on a subnet are the samel Whether the orderwire port is set correctly

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

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



101

6 Part Replacement

About This Chapter

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

Background Information

Table 6-1 Part replacement description

Part Name Operation Tool

SL1D, SL1DA 6.3 Replacing the SDH OpticalInterface Board

l ESD wrist strapl Screwdriverl U2000l Fiber remover

EMS6,EM6TA,EM6FA,EM6T, EM6Fand EFP8

6.6 Replacing the EthernetInterface Board

CSTA, CSHA,CSHB, CSHC,CSHE, andCSHD

6.9 Replacing the System Control,Switch and Timing Board

CF card 6.8 Replacing the CF Card

SP3D and SP3S 6.4 Replacing the PDH InterfaceBoard

l ESD wrist strapl Screwdriverl U2000IF1, IFU2,

ISX2, ISU2,and IFX2

6.7 Replacing the IF Board

PIU 6.11 Replacing the Power Board

ML1 and MD1 6.5 Replacing the Smart E1 Board

OptiX RTN 910 Radio Transmission SystemMaintenance Guide (U2000) 6 Part Replacement


102

Part Name Operation Tool

FAN 6.10 Replacing the Fan Board l ESD wrist strapl U2000

ODU 6.13 Replacing the ODU l Ejector lever (torque wrench)l U2000l Siliconl Waterproof adhesive tape

Replacing theIF cable

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

accessories of the connectorl IF cablel Waterproof adhesive tape



103

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.

Figure 6-1 Wear the ESD wrist strap

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

NOTE

Use fiber removers to remove fibers or network cables.



104

Figure 6-2 Tweezer fiber remover

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

Figure 6-3 Removing a board (1)

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

from the backplane.



105


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


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

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

----End

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

Procedure

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



106

Figure 6-6 Wear the ESD wrist strap

Step 2 Insert the board.1. Hold the ejector levers on the panel with both hands. Push them outwards so that the angle

between the ejector lever and the panel is about 45 degrees.2. Push the board gently along the slot guide rail until the board cannot slide further.

Figure 6-7 Inserting a board (1)

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



107

3. Press the two ejector levers inward with force.


4. Tighten screws on the panel.


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

----End

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

Prerequisitel You must know the impact of board replacement.l You must know the specific position of the board to be replaced.l You must know the service protection and protection channels of the board to be replaced.



108

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

Tools, Equipment, and Materialsl ESD wrist strapl Screwdriverl U2000l Fiber remover

Procedure

Step 1 Query the current alarms of the board.

Step 2 Optional: If the services on the board are configured with SNCP, ensure that the services arealready switched to the protection channel.1. Query the SNCP protection group.2. Perform the forced switching, 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 currentprotection channel is normal or SD.

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

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

Step 4 Remove the board.

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

Step 6 Insert the board.

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

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

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

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

----End

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



109

Prerequisitel You must know the impact of board replacement.l You must know the specific position of the board to be replaced.l You must know the service protection and protection channels of the board to be replaced.l The spare board must be made available, and the version and type of the spare board must

be the same as those of the board to be replaced. You can query the board manufacturinginformation to obtain the version of the board to be replaced.

Tools, Equipment, and Materialsl ESD wrist strapl Screwdriverl U2000

Procedure



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


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


----End

6.5 Replacing the Smart E1 BoardWhen the Smart E1 board is replaced, the services on the board are interrupted.

Prerequisitel You must know the impact of board replacement.l You must know the specific position of the board to be replaced.l You must know the service protection and protection channels of the board to be replaced.l The spare board must be available, and the version and type of the spare board must be the

same as the version and type of the board to be replaced. You can query the boardmanufacturing information to obtain the version of the board to be replaced.

Tools, Instruments and Materialsl ESD wrist strapl Screwdriver



110

l U2000

Procedure

Step 1 Query the current alarms of the board to be replaced.


Step 3 Verify that the spare board has the same board version and board type as the board to be replaced.

Step 4 Insert the spare board.

Step 5 After the substitute board starts to work, check the indicators on the board. The STAT indicatoris on and green.

NOTE

Smart E1 boards are hot-swappable. After the spare board is installed, it enters initialization state and starts towork 2 minutes later.

Step 6 Query the current alarms of the substitute board.There is no new alarm on the board.

----End

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

Prerequisitel You must know the impact of board replacement.l You must know the specific position of the board to be replaced.l You must know the service protection and protection channels of the board to be replaced.l The spare board must be made available, and the version and type of the spare board must

be the same as those of the board to be replaced. You can query the board manufacturinginformation to obtain the version of the board to be replaced.


Procedure


Step 2 Optional: If the services are configured with MPLS APS, ensure that the services are alreadyswitched to the protection tunnel.1. Querying MPLS APS Status.



111

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

Step 3 Optional: If the services are configured with PW APS, ensure that the services are alreadyswitched to the protection PW.1. Querying PW APS Status.2. If the board functions as the current working board, perform the forced switching.


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


NOTE

Ethernet interface boards are hot-swappable. After the substitute board is installed, it enters initialization stateand starts working two minutes later.

If dynamic ARP is disabled on the NE at the opposite end of an MPLS tunnel, you need to change the staticARP table entries of the opposite NE.



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

----End

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

Prerequisitel You must know the impact of board replacement.l You must know the specific position of the board to be replaced.l You must know the service protection and protection channels of the board to be replaced.l The spare board must be available, and the version and type of the spare board must be the

same as the version and type of the board to be replaced. You can query the boardmanufacturing information to obtain the version of the board to be replaced.


Procedure




112

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

1. Query the SNCP protection group.

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

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

1. Query the IF 1+1 protection group.


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

1. Query the IF N+1 protection group.


Step 5 Optional: If the services are configured with MPLS APS, ensure that the services are alreadyswitched to the protection tunnel.

1. Querying MPLS APS Status.


Step 6 Optional: If the services are configured with PW APS, ensure that the services are alreadyswitched to the protection PW.

1. Querying PW APS Status.


Step 7 Optional: If the IF board is configured with the XPIC function, see Setting the ODU TransmitterState and mute the ODU at the opposite end.

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

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



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



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



113

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

IF boards are hot-swappable. After the substitute board is installed, it enters initialization stateand starts working two minutes later.

If dynamic ARP is disabled on the NE at the opposite end of an MPLS tunnel, you need to changethe static ARP table entries of the opposite NE.


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

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

Step 18 If the IF board is configured with the XPIC function, see Setting the ODU Transmitter State andunmute the ODU at the opposite end.

----End

6.8 Replacing the CF Cardall the services are interrupted during the replacement of the CF card.

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

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

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

l You must obtain a spare CF card that has the same capacity as the CF card to be replaced.

Tools, Equipment, and Materials

l ESD wrist strap

l U2000

l Fiber remover

Procedure



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



114

Step 4 Check the spare CF card.

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


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

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

----End

6.9 Replacing the System Control, Switch and Timing BoardAll the services are interrupted during the period of replacing the system control switch andtiming board.

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 board must be made available, and the version and type of the spare board mustbe the same as those of the board to be replaced. You can query the board manufacturinginformation to learn about the version of the board to be replaced.



115

Impact on SystemThe replacement of the System control Switch and Timing board results in service interruption.


ContextNOTE

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

Procedure


Step 2 Replace the System control Switch&Timing board.

1. Notify the onsite maintenance personnel to remove the board.2. Check whether the version of the spare board and the model of the SFP on the spare board

are the same as the version of the board to be replaced and the model of the SFP on theboard to be replaced.

3. Remove the CF card from the original board and then install the CF card to the spare board.For details about how to install the CF card, see 6.8 Replacing the CF Card.

4. Insert the spare board into the chassis.5. Press and hold the CF RCV button on the board for 8 seconds so that the board automatically

restores the NE databases, system parameters, software packages, and NE logs from theCF card.

NOTE

l In the process of restoring the NE database, the PROG indicator on the board blinks in green for about11 minutes.

l If the database restoration is successful, the NE resets automatically. After the NE resets successfully,the STAT and PROG indicator is on and green.

l If the database restoration fails, the NE does not reset, and the PROG is red. In this case, contactHuawei technical support engineers for rectifying the fault.

NOTEAfter the NE starts up normally, the STAT and PROG indicator on the board is green.

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

----End

6.10 Replacing the Fan BoardThe IDU cannot perform air cooling in the process of replacing the fan board. Therefore, youneed to replace the fan board quickly.



116

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

be the same as those of the board to be replaced. You can query the board manufacturinginformation to learn about the version of the board to be replaced.

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


l ESD wrist strapl U2000

Precautions

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

Procedure


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

Step 3 Remove the fan board.

12




117

Step 5 Insert the standby fan board.

12

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

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

----End

6.11 Replacing the Power BoardAll the services at the IDU are interrupted during the period of replacing the power board.

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 The spare chassis must be made available, and the version and type of the spare chassis

must be the same as the version and type of the board to be replaced. The spare chassismust be made available, and the chassis is configured with the power board and the fantray. You can query the board manufacturing information to learn about the version ofthe board to be replaced.




118

Precautions

WARNINGBefore replacing the board, you must turn off the power switch of the PDU. After inserting thePIU properly, turn on the power switch of the PDU.When removing the mounting ears of the chassis, hold the bottom of the chassis to prevent injuryto human body or damage to other equipment caused by falloff of the chassis.

Procedure


Step 2 Take a record about the slot ID of each board and the mapping relations between the interfacesand cables so that the original wiring method is used after the board is replaced.

Step 3 Notify the onsite maintenance personnel to turn off the output power switch on the power supplyequipment.

Step 4 Pull out other boards except for the power board and fan board.

Step 5 Remove the mounting ears on the chassis and remove the chassis. (Skip this step when the chassisis installed on the desk.)

WARNINGWhen removing the mounting ears of the chassis, hold the bottom of the chassis to prevent injuryto human body or damage to other equipment caused by falloff of the chassis.

Step 6 See the OptiX RTN 910IDU Quick Installation Guide, install the spare chassis, and thenreconnect the cables to the chassis according to the record.

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

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

----End

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

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



119

l You must know the service protection and protection channels of the SFP to be replaced.l The spare SFP must be available, and the version and type of the spare SFP must be the

same as the version and type of the SFP to be replaced. You can query the boardmanufacturing information to obtain the version of the SFP to be replaced.

ContextNOTE

The CSHC, CSTA and SL1D can be equipped with the SFP to provide 2xSTM-1 optical or 2xSTM-1 electricalinterfaces. The CSHC, CSHD, EM6F can be equipped with the SFP to provide 2xGE optical interfaces or 2xGEelectrical interfaces.

Tools, Equipment and Materialsl ESD wrist strapl Screwdriverl U2000

Procedure


Step 2 Optional: If SNCP is configured for services at the optical interface, ensure that the servicesare already switched to the protection channel.1. Query the status of the SNCP group.2. If the port on the local board functions as the working channel, the protection channel does

not involve the local board, and the protection channel is in the normal or SD state, performforced switching.

Step 3 Optional: If linear MSP is configured for services at the optical interface, ensure that the servicesare already switched to the protection channel.1. Query the status of the linear MSP group.2. If the port on the local board functions as the working channel, the protection channel does

not involve the local board, and the protection channel is in the normal or SD state, performforced switching.

Step 4 Record the cable connections of the SFP, and then disconnect cables.

Step 5 Check the types of the spare SFP and the SFP to be replaced, and remove the SFP module.

NOTE

When removing the SFP electrical module, press the blcak button first.



120

2

1

Press the unclocking button.

Remove the SFP electical module.

1

2

Step 6 Insert the standby SFP module and reconnect cables based on the record.


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

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

----End

6.13 Replacing the ODUWhen the ODU is replaced, the unprotected services on the ODU are interrupted.

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

to the ODU.l The spare ODU must be at hand, whose type must be the same as the type of the ODU to

be replaced.

Tools, Equipment, and Materialsl Ejector lever (torque spanner)l U2000l Siliconl Waterproof adhesive tape

Precautions

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 ejects little RF radiation, thus meeting the safety standards for microwaveradiation.



121

If the XPIC work group is configured for the IF board that is connected to the ODU to be replaced,the ODU at the opposite end of the XPIC work group needs to be muted.

ProcedureStep 1 Query the current alarms on the ODU and then record the results.

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

Step 3 Remove the IF cable and the PGND cable from the ODU.

Step 4 Remove the ODU.

Option Description

If... Then...

You need to remove the ODU with awaveguide interface

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

You need to remove the ODU with acoaxial interface

Remove the ODU from the post.

You need to remove the RTN XMC ODU Loosen the captive screws on the ODU anddisconnect the ODU from the antenna, thehybrid coupler, or ODU adapter.

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

Step 6 Install the ODU.

Option Description

If... Then...

You need to install a new ODU with awaveguide interface

See the RTN 600 ODU Quick InstallationGuide.

You need to install a new ODU with acoaxial interface

See the RTN 600 ODU Quick InstallationGuide.

You need to install a new RTN XMC ODU See the RTN XMC ODU Installation Guide.

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

Step 8 Waterproof the IF interface on the ODU.


Step 10 After the ODU starts to work, check the ODU indicator and LINK indicator on the IF board.The ODU indicator and LINK indicator should be on and green.

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

----End

6.14 Replacing the IF CableWhen the IF cable is replaced, the unprotected services on the IF cable are interrupted.



122

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

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

connect the IF cable to the IDU and both ends of the IF cable should be terminated withtype-N connectors. In the case of the 5D IF cable, the IF cable is connected directly to theIDU and the cable end connecting to the IDU should be terminated with the TNC connectorand the cable end connecting to the ODU should be terminated with the type-N connector.

Tools, Equipment, and Materialsl Multimeterl Ejector leverl Electro-technical knifel Filel Installation parts and accessories of the connectorl IF cablel Waterproof adhesive tape

Procedure

Step 1 Query and record the current alarm of the IDU.

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

Step 3 Disconnect the IF cable from the IF jumper and from the ODU.

Step 4 Use a multimeter to test the connectivity of the IF cable to determine whether you need to makenew connectors for the IF cable or replace the IF cable with a new one.

If... Then...

You need to make new connectors for theIF cable

See the Installation Reference and make newconnectors for the IF cable.

You need to replace the IF cable with a newone

Replace the IF cable with a new one.

Step 5 Connect the IF cable to the IF jumper and to the ODU.

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


Step 8 After the ODU starts to work, check the ODU and LINK indicators on the IF board.The ODU indicator and LINK indicator should be on and green.

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

----End



123

7 Database Backup and Restoration

About This Chapter

The OptiX RTN 910 supports database backup and restoration through the NMS.

7.1 NE DatabaseAn NE database stores the communication data, security data, alarm data, performance data, andconfiguration data of an NE in a certain structure to facilitate the relevant query and modification,hence ensuring that the data can be restored after the NE is reset.

7.2 Backing Up the Database ManuallyThe NE configuration data is stored in the database of an NE. To prevent the database frombeing damaged due to certain risky operations such as replacing a faulty system control, cross-connect, and timing board or upgrading the software, you need to manually back up the databaseon a regular basis and before performing any risk operation.

7.3 Setting the Database Backup PolicyYou can set the policy of backing up a database to realize the function of periodically backingup the database.

7.4 Restoring the DatabaseIf the database is damaged, you can restore the NE database by using the database files that aresaved previously.

OptiX RTN 910 Radio Transmission SystemMaintenance Guide (U2000) 7 Database Backup and Restoration


124

7.1 NE DatabaseAn NE database stores the communication data, security data, alarm data, performance data, andconfiguration data of an NE in a certain structure to facilitate the relevant query and modification,hence ensuring that the data can be restored after the NE is reset.

An NE database includes the following types:

l Memory database (MDB)The data in the MDB varies according to the configuration and is lost when the systemcontrol unit is reset or when the NE is powered off.

l Dynamic random database (DRDB)The DRDB automatically stores the data that is checked successfully. The DRDB is residentin the reserved memory. Hence, the data in the DRDB is not lost when a warm reset isperformed on the system control unit. The data, however, is lost when a cold reset isperformed on the system control unit or when the NE is powered off.

l Flash database (FDB)The FDB includes FDB0 and FDB1. The FDB is resident in the flash memory on the board.Hence, the data in the FDB is permanently stored.

After being delivered to the system control unit, the NE configuration data is stored in the MDB.After checking the NE configuration data successfully, the system control unit automaticallycopies the data from the MDB to the DRDB and delivers the board configuration data generatedafter successful check to the relevant board.

The NE backs up the DRDB database into the FDB0 and FDB1 databases of the flash memoryat an interval of 30 minutes.

After the NE is restarted because of power-off, the system control unit checks whether theconfiguration data in the DRDB is available. If yes, the system control unit restores the data. Ifthe configuration data in the DRDB is damaged, the system control unit restores the data fromFDB0 or FDB1.

On the CF card, NE databases, system parameters (including NE-IP, NE-ID, and subnet mask),software packages, and NE logs are stored. After the CRV button on the system control,switching and timing board is pressed and held for 8 seconds, the data stored on the CF card isloaded to the board. To synchronize the data on the CF card with the NE databases, systemparameters, and NE logs on the system control, switching and timing board, the regular backupfunction needs to be enabled. By default, the data is backed up every 24 hours.

NOTE

The software packages on the CF card are updated with those on the system control, switching and timing boardduring package diffusion. Therefore, no automatic or manual operation is performed to synchronize the softwarepackages.

The system control, switching and timing board and the CF card must have same software packages. If theyhave different software packages, the SWDL_CHGMNG_NOMATCH alarm is reported.

7.2 Backing Up the Database ManuallyThe NE configuration data is stored in the database of an NE. To prevent the database frombeing damaged due to certain risky operations such as replacing a faulty system control, cross-



125

connect, and timing board or upgrading the software, you need to manually back up the databaseon a regular basis and before performing any risk operation.

Prerequisitel You must be an NM user with NE operator authority or higher.l You must log in to the NE.

Tools, Equipment, and MaterialsU2000

Procedure

Step 1 On the NMS, choose Administration > NE Software Management > NE Data Backup/Restoration from the Main Menu.

Step 2 In NE View, click Find.

Step 3 In the Find NE dialog box, set the search conditions and search for the NE that requires databasebackup.

Step 4 Click OK.

Step 5 Click Backup.

NOTE

Press and hold the Ctrl button on the keyboard, you can select multiple NEs to back up the data at one time.

Step 6 Set the data backup path to NMS Server or NMS Client according to the requirements.

Step 7 Click Start to start backing up the NE data. In NE View, Operation Status indicates the progressof backing up the data. After the data backup is successful, Operation Status displays a message,indicating that the operation is successful.

----End

7.3 Setting the Database Backup PolicyYou can set the policy of backing up a database to realize the function of periodically backingup the database.

7.3.1 Setting the User-Defined Backup PolicyThrough this task, you can set the backup policy for a specific NE.

Prerequisitel You must be an NM user with NE operator authority or higher.l You must log in to the NE.




126

Background InformationEach NE has a default data backup policy.

l Database packages are backed up once at 2:00.l The default backup policy is disabled by default.l A maximum of five database packages can be backed up at a time.l Data changes do not trigger any backup operations.

Procedure

Step 1 Choose Administration > NE Software Management > NE Backup Policy Managementfrom the Main Menu.Then, the NE Backup Policy Management dialog box is displayed.

Step 2 In Auto Backup Policy window, set NE type.The version, name, and IP address of the selected NE are displayed.

Step 3 Click New Policy.

Step 4 Optional: Click to import the information of the NEs.

Step 5 Optional: Click to export the information of the NEs.The information of the selected NEs is stored in the specified location.

Step 6 In NE Table, select one or more NEs.

Step 7 Click Next.Then, the Setting Policy dialog box is displayed.

Step 8 Set Policy Name, Period Backup Policy, and Period Save Policy.

NOTE

l If The Added NE's Policy Status is set to Enable, the NMS performs the backup operation withinthe specified period, day, and time.

l If The Added NE's Policy Status is set to Disable, the backup policy is still in the Disable statealthough the policy period reaches the specified period, day, and time.

Step 9 Click Advanced Settings, and set Backup Type, Max Backup Num, and ConfigurationChange Backup for a certain type of NEs.

Step 10 Click OK.

Step 11 Click OK.

----End

7.3.2 Enable the Backup Policy of the DeviceThrough this task, you can set the backup policy of a device to the running state.

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



127


Procedure



Step 3 Right click the selected NE, Click Enable Backup Policy.

----End

7.3.3 Disable the Backup Policy of the DeviceThrough this task, you can set the backup policy of a device to the suspended state.

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


Procedure



Step 3 Right click the selected NE, Click Disable Backup Policy.

----End

7.4 Restoring the DatabaseIf the database is damaged, you can restore the NE database by using the database files that aresaved previously.

Prerequisitel You must be an NM user with NE operator authority or higher.l The data to be restored must be backed up.l You must log in to the NE.



128


U2000

Procedure

Step 1 On the NMS, choose Administration > NE Software Management > NE Data Backup/Restoration from the Main Menu.The NE Data Backup/Restoration window is displayed.

Step 2 In NE View, click Find.Then, the Find NE dialog box is displayed.

Step 3 In the Find NE dialog box, set the search conditions to search for the NEs that need to restoredatabases.

Step 4 Click OK.

Step 5 Select the NE whose data needs to be recovered, and click Recover.

NOTE

You can select multiple NEs to recover the data at one time.

Then, the Recover dialog box is displayed.

Step 6 Select Browse in File Name.Then, the Select File dialog box is displayed.

Step 7 Select files from NMS Server or NMS Client, and then choose the files to be recovered. ClickOK.

Step 8 In the Recover dialog box, click Start.

Step 9 Click Yes in the prompt dialog box.The system starts recovering the selected data files on the specified NE.

In the NE list of NE View, Operation Status indicates the progress of recovering the data.

After the data is recovered, Operation Status displays a message, indicating that the operationis successful.

Step 10 In NE View, right-click the NE and choose Active Database from the shortcut menu.The Active Database dialog box is displayed.

Step 11 Click Start to start activating the database.

NOTE

If the NE transmits data services, select Deliver to Board.

Services are interrupted during the activation of databases.

In NE View, Operation Status indicates the progress of activating the database. After thedatabase is activated, Operation Status indicates that the operation is successful.

----End



129

8 Supporting Task

About This Chapter

This chapter describes the common maintenance operations.

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

8.2 Cleaning Fiber Connectors and AdaptersThe optical connectors are easily contaminated in the maintenance process. The minute dustparticles that can be seen only in the microscope can also affect the quality of optical signals. Inthis case, the system performance deteriorates. Hence, the fiber connectors or adapters that areterminated need to be cleaned in time.

8.3 Browsing Alarms, Abnormal Events, and Performance EventsThe U2000 is used to browse alarms, abnormal events, and performance events at the networklayer.

8.4 Querying a ReportYou can obtain the version, manufacture, and microwave link information of all the boards byquerying the corresponding report.

8.5 Software LoopbackSoftware loopback refers to the loopback operation that is implemented by using the NMS.During software loopback, you need not visit the engineering site. Hence, software loopback isused more widely than hardware loopback.

8.6 ResetReset is an important method of troubleshooting software faults. Reset is classified into coldreset, warm reset.

8.7 PRBS TestThe pseudorandom binary sequence (PRBS) test is an important method of network maintenanceand self-check.

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

OptiX RTN 910 Radio Transmission SystemMaintenance Guide (U2000) 8 Supporting Task


130

8.9 Setting the On/Off State of the LaserWhen performing operations such as testing a fiber cut, you can set the on/off state of the laserrather than removing and re-inserting the optical fiber on site.

8.10 Setting the ALS FunctionThe SDH optical interface board supports the automatic laser shutdown (ALS) function. Thisfunction enables the board to turn off a laser when the board does not transmit services, theoptical fiber is faulty, or the received optical signals are lost.

8.11 Setting the Automatic Release FunctionTo protect the communication between the NMS and NE against improper operations, an NEsupports the automatic release of the ODU muting, software loopback, and other operations thatrequire you to exercise caution. The automatic release time is five minutes by default. You canset whether to enable the automatic release function and the automatic release time through theNMS.

8.12 Querying Power Consumption of BoardsThis section describes how to query power consumption of the ODU and each board.

8.13 Querying the Impedance of an E1 ChannelThe impedance of an E1 channel is 75 ohms or 120 ohms.

8.14 Monitoring Ethernet Packets Through Port MirroringTo monitor and analyze the Ethernet packets at a port, you can enable the port mirroring functionso that the received or transmitted packets on the port are duplicated to another Ethernet port towhich the Ethernet tester is connected. Then, you can monitor and analyze the packets. Thisfunction is supported by the EFP8/EMS6 board of the OptiX RTN 910.

8.15 Querying the Attributes of an Ethernet PortThrough the operation, you can learn about the attributes of an Ethernet port, such as rate.

8.16 Setting Traffic, Physical Bandwidth, or Bandwidth Utilization of Ethernet PortsTo query the traffic, physical bandwidth, or bandwidth utilization of Ethernet ports within acertain period, you need to enable the monitoring for the object before that period starts. TheFE/GE ports and Integrated IP radio ports on the packet plane support this operation.

8.17 Querying Traffic, Physical Bandwidth, or Bandwidth Utilization of Ethernet PortsThis section describes how to query the change curve of the traffic, physical bandwidth, orbandwidth utilization of Ethernet ports within a certain period. The FE/GE ports and IntegratedIP radio ports on the packet plane support this operation.

8.18 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. Only the FE port on the EFP8 board supports this operation.

8.19 Using the Ethernet Test FramesBy using the Ethernet test frames, you can check the connectivity of VCTRUNKs. Only theEFP8 board supports this operation.



131

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

Background InformationHardware loopback is classified into optical cable loopback, PDH cable loopback, and Ethernetport loopback.l Optical cable loopback indicates that the receive and transmit optical fibers are 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 PDH cable loopback indicates that the receive and transmit PDH cables are connectedthrough a short-circuiting cable or connector on the DDF.

l Ethernet port loopback indicates that the receive and transmit service signals on oneEthernet port are looped back through a special loopback Ethernet cable.

8.2 Cleaning Fiber Connectors and AdaptersThe optical connectors are easily contaminated in the maintenance process. The minute dustparticles that can be seen only in the microscope can also affect the quality of optical signals. Inthis case, the system performance deteriorates. Hence, the fiber connectors or adapters that areterminated need to be cleaned in time.

8.2.1 Cleaning Fiber Connectors by Using Cartridge CleanersWhen there are special cartridge cleaners (such as the CLETOP cassette cleaner), use them forcleaning the fiber connectors.

Prerequisitel Disconnect both ends of the fiber. Ensure that there is no laser light on the fiber connectors.l Inspect the fiber connector with a fiber microscope to ensure that the fiber connectors are

contaminated.

Tools, Equipment, and MaterialsCartridge cleaner

Procedure

Step 1 Press down and hold the lever. Then, the shutter slides back and exposes a new cleaning area.



132

Figure 8-1 Using the CLETOP cassette cleaner

Step 2 Position the fiber tip slightly against the cleaning area and drag the fiber tip slightly in thedownward direction.

Figure 8-2 Dragging the fiber tip slightly on one cleaning area

Step 3 Repeat the same in the other cleaning area in the same direction as Step 2.



133

Figure 8-3 Dragging the fiber tip slightly on the other cleaning area

Step 4 Release the lever to close the cleaning area.

----End

8.2.2 Cleaning Fiber Connectors by Using Lens TissueWhen there is no cartridge cleaners, use the lens tissue for cleaning fiber connectors.

Prerequisitel Disconnect both ends of the fiber. ensure that there is no laser light on the fiber connectors.

l Inspect the fiber connector with a fiber microscope to ensure that the fiber connectors arecontaminated.

Tools, Equipment, and Materialsl Clean solvent

l Non-woven lens tissue

l Special compressed gas

NOTE

l The isoamylol is preferred as the clean solvent, and the propyl can also be used as the clean solvent.Do not use alcohol or formalin.

l The fiber cleaning tissue or lint-free wipes can substitute the non-woven lens tissue.

l The special cleaning roll can substitute the special compressed gas.



134

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 8-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 Use the compressed gas to blow the fiber tip.When using compressed gas, note the following points:l First spray it into the air because the initial spray of condensation may contain certain

sediment.l Ensure that the injector nozzle is as close as possible to (but does not touch) the connector

surface.

----End

8.2.3 Cleaning Fiber Adapters by Using Optical Cleaning SticksThe fiber adapters need to be cleaned with optical cleaning sticks. This section describes themethod of cleaning fiber adapters on the optical interface board. The same method can be usedto clean fiber adapters on the optical attenuators and flanges.

Prerequisitel Before you clean the fiber adapter, remove the optical fiber and shut down the laser. For

details about how to shut down a laser, see 8.9 Setting the On/Off State of the Laser.l Inspect the fiber adapter with a fiber microscope to ensure that the fiber adapter is

contaminated.



135

Tools, Equipment, and Materialsl Optical cleaning sticksl Clean solventl Special compressed gas

NOTE

l In the case of the SC and FC optical interface, use the cleaning stick with a diameter of 2.5 mm. In thecase of the LC optical interface, use the cleaning stick with a diameter of 1.25 mm.

l The medical cotton or long fiber cotton can substitute the optical cleaning stick.

l The isoamylol is preferred as the clean solvent, and the propyl can also be used as the clean solvent.Do not use alcohol or formalin.

l The special cleaning roll can substitute the special compressed gas.

Procedure

Step 1 Apply a small amount of cleaning solvent on the optical cleaning stick.

Step 2 Touch the adapter gently with the optical cleaning stick and turn the stick clockwise four to fivetimes.Ensure that there is direct contact between the stick tip and fiber tip so that the solvent can cleanthe adapter tip.

Step 3 Use the compressed gas to blow the fiber adapter.When using compressed gas, note the following points:l First spray the compressed gas into the air because the initial spray of condensation gas may

contain some sediment.l Ensure that the injector nozzle is as close as possible to (but does not touch) the inner surface

of the connector.

----End

8.3 Browsing Alarms, Abnormal Events, and PerformanceEvents

The U2000 is used to browse alarms, abnormal events, and performance events at the networklayer.

8.3.1 Checking the NE StatusYou can learn about the basic information such as whether the NE fails to communicate withthe NMS and whether any alarms are reported by checking the NE status.

Prerequisite

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


U2000



136

PrecautionsNOTE

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

ProcedureStep 1 In Main Topology, select the required NE.

Step 2 In Main Topology, click .

Step 3 Click the Attribute tab.

Step 4 View the NE status and alarm status.TIP

You can also determine the NE status based on the comparison between the NE icon and the descriptionat the Legend tab.

----End

8.3.2 Checking the Board StatusYou can learn about the board status in a visual manner by checking the slot diagram.

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


ProcedureStep 1 On the Main Topology, double-click the desired NE. The NE Panel is displayed. The NE is in

Running Status.

Step 2 Click the icon. The legend description is displayed.

Step 3 Check the running status of the boards based on the legend description. If a board is runningnormally, the board icon is green.

----End

8.3.3 Browsing Current AlarmsYou can find the faults that occur on the equipment by browsing current alarms.





137

Procedure

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

Step 2 Optional: In the Filter dialog box, click the Basic Settings tab.1. In Severity, select the alarm severity to be queried.2. In Status, select the alarm status to be queried.3. In Type, select the alarm type.4. In Last Occurrence Time Segment, specify the alarm generation time.5. In Clearance Time Segment, specify the alarm clearance time.

Step 3 In the Filter dialog box, click the Alarm Source tab.

Step 4 Select the object to be queried.

Option Description

Browse all alarms on the NE. Select All Objects.

Browse certain alarms on the NE. 1. Select Custom.2. Choose Add > Object below NE.3. Select the required NE in the left pane of Object

below NE, and click .4. Click OK.

Alarm Source displays Selected Alarm Source.

Step 5 Click OK.

Step 6 Browse the displayed alarms.

Step 7 Select the newly generated alarms, record the details of the alarms, and click Acknowledge.The Confirm dialog box is displayed.

Step 8 Click Yes.

Step 9 Notify the troubleshooting personnel to clear the alarms in time.For the details, see A.3 Alarms and Handling Procedures.

----End

Related InformationA current alarm refers to an alarm that is not cleared.

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

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

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

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



138

l You can click (light-blue) to browse the network-wide warning alarms.

NOTE

By default, the number shown by each indicator indicates the number of current network-wide alarms, whichare not cleared, of the specific severity.

8.3.4 Browsing Abnormal EventsYou can find the faults that occur on the equipment in a specific time by browsing abnormalevents. An abnormal event refers to an exception that occurs on the system at a particular timerather than an exception that persists for a certain time of period.



Procedure

Step 1 Choose Fault > Browse Event Logs from the Main Menu.

Step 2 In the Filter dialog box, click the Event Source tab.


Option Description

Browse all performance events on the NE. Select All Objects.

Browse certain performance events on theNE.

1. Select Custom.2. Choose Add > Object below NE.3. Select the required NE in the left pane of

Object below NE, and click .4. Click OK.

Event Source displays Selected EventSource.

Step 4 Click OK.

Step 5 Browse the abnormal events.

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

----End

Related InformationBeing different from an alarm that has both the occurrence time and the clearance time, anabnormal event has only the occurrence time.



139

8.3.5 Browsing Current Performance EventsYou can know the running status of the equipment by browsing current SDH/PDH performanceevents. The counter of current performance events measures all the performance events that arisebetween the start time of the monitoring period and the current time.

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

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

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


Procedure

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

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

Step 3 Select All in Monitored Object Filter Condition.

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

Step 5 Click the Count tab, and then select Display Continuous Severely Errored Seconds.

Step 6 Click Query to browse the current performance events.In normal cases, no bit error performance events should be displayed, and the number of pointerjustification events should be less than six per day.

Step 7 Click the Gauge tab, select All for the performance event type, and then select Display CurrentValue and Display Maximum and Minimum Values in the right pane.

Step 8 Click Query to browse the displayed performance events.In normal cases, compared with the history records, the gauge indicators, such as the boardtemperature, do not change drastically.

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

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

----End

8.3.6 Browsing History AlarmsYou can know the faults that occur on the equipment in a past period of time by browsing historyalarms. A history alarm refers to an alarm that is already cleared.




140


Procedure

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

Step 2 Optional: In the Filter dialog box, click the Basic Settings tab.1. In Severity, select the alarm severity to be queried.2. In Type, select the alarm type.3. In Occurrence Time Segment, specify the alarm generation time.4. In Clearance Time Segment, specify the alarm clearance time.

The time span starts from the time when the last history alarm browsing operation wasperformed to the current time.

Step 3 In the Filter dialog box, click the Alarm Source tab.


Option Description

Browse all alarms on the NE. Select All Objects.

Browse certain alarms on the NE. 1. Select Custom.2. Choose Add > Object below NE.3. Select the required NE in the left pane of Object

below NE, and click .4. Click OK.

Alarm Source displays Selected Alarm Source.

Step 5 Click OK.

Step 6 Browse the displayed history alarms.

----End

8.3.7 Browsing History Performance EventsYou can know the faults that occur on the equipment in a past period of time by browsing historyperformance events.

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

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

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




141

Procedure

Step 1 Choose Performance > Browse SDH Performance from the main menu, and then click theHistory Performance Data tab.

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

Step 3 Set the parameters, such as Monitored Object Filter Condition, Monitor Period, DataSource.

Step 4 Click the Gauge tab, and set Performance Event Type.

Step 5 Click the Count tab, and set Performance Event Type.

Step 6 Click Query.

----End

8.3.8 Browsing the Performance Event Threshold-Crossing RecordsYou can learn about the threshold-crossing information of the performance events of an NE bybrowsing the performance event threshold-crossing records.



Procedure

Step 1 Browse the performance event threshold-crossing records that are displayed.

Step 2 Choose Performance > Browse SDH Performance from the Main Menu.

Step 3 Click the Performance Threshold-Crossing Record tab.

Step 4 Select an NE from the Object Tree in the NE Explorer. Click .

Step 5 Set the parameters such as Monitored Object Filter Condition, Monitor Period, andPerformance Event Type.

Step 6 Click Query.

----End

8.3.9 Browsing UAT EventsLearn about the severe abnormalities on the transmission line by browsing UAT events.




142

Tools, Instruments and Materials

U2000

Context

UAT refers to a period of 10 consecutive seconds during which the bit error ratio per second ofthe digital signal in either of the transmission directions of a transmission system is inferior to10-3. These 10 seconds are considered to be part of the unavailable time.

Procedure

Step 1 In the NE Explorer, select the desired board.

Step 2 Choose Performance > UAT Event from the Function Tree.

Step 3 Set Monitored Object Filter Condition, From, To, and Data Source.

Step 4 Set Function Block Type and Display Options.

Step 5 Click Query.

Step 6 Close the dialog box that is displayed.

----End

8.3.10 Configuring the Performance Monitoring Status of NEsBy performing this operation task, you can manually enable or disable performance monitoringfor NEs, or set the performance monitoring period.

Prerequisite

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


U2000

Procedure

Step 1 In the NE Explorer, select the NE from the Object Tree, and then choose Performance > NEPerformance Monitoring Time from the Function Tree.

Step 2 Configure the performance monitoring parameters of the NEs.

1. Select 15-Minute or 24-Hour.

2. Select Enabled or Disabled in Set 15-Minute Monitoring or Set 24-Hour Monitoring.

3. Set the start time and end time of the performance monitoring of NEs.



143

NOTE

l Generally, both Set 15-Minute Monitoring and Set 24-Hour Monitoring are enabled.l You can specify the start time of the performance monitoring function, only after selecting Enabled

in the Set 15-Minute Monitoring or Set 24-Hour Monitoring area.l You can specify the end time of the performance monitoring function, only after selecting Enabled

and then selecting To in the Set 15-Minute Monitoring or Set 24-Hour Monitoring area.

4. Click Apply. Close the displayed dialog box.

----End

8.3.11 Setting Severity and Auto Reporting Status of AlarmsThis section describes how to set the severity and auto reporting status of specific alarms.

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

Tools, Instruments and MaterialsU2000

ProcedureStep 1 In the NE Explorer, select the desired object.

Step 2 Choose Alarm > Alarm Severity and Auto Reporting from the Function Tree.

Step 3 Select any items in the column Event and set Severity and Auto Reporting Status for them.

Step 4 Click Apply to save the settings.


----End

8.3.12 Suppressing Alarms for Monitored ObjectsThis section describes how to suppress specific alarms for a specific monitored object.



144



Procedure


Step 2 Choose Alarm > Alarm Suppression from the Function Tree.

Step 3 Set Monitored Object and click Query.

Step 4 Set Status in Alarm Suppression.

Step 5 Click Apply.


----End

8.3.13 Suppressing Alarms for NEsThis section describes how to suppress certain alarms for NEs.



Procedure

Step 1 In the NE Explorer, select the desired NE.

Step 2 Choose Alarm > NE Alarm Suppression from the Function Tree.

Step 3 Set Status in Alarm Suppression.

Step 4 Click Apply.


----End

8.3.14 Reversing Alarms for Service PortsThis section describes how to reverse alarms for service ports.




145


U2000

Procedure

Step 1 In the NE Explorer, select the desired NE.

Step 2 Choose Alarm > NE Alarm Attribute from the Function Tree.

Step 3 Set Reversion Mode to Manual Restoration.

Step 4 Click Apply.



Step 7 Choose Alarm > Alarm Reversion from the Function Tree.

Step 8 Set Reversion Status for the required port.

Step 9 Click Apply.


----End

8.3.15 Setting Trigger Conditions of AIS InsertionThis section describes how to set the trigger conditions of AIS insertion for specific monitoredobjects.

Prerequisite

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


U2000

Procedure

Step 1 In the NE Explorer, select the desired board. Choose Alarm > QoS Alarm > AIS Insertionfrom the Function Tree.

Step 2 Set the trigger conditions of AIS insertion. If you select Enabled under an alarm, the AIS signalis inserted when this alarm occurs; otherwise, the AIS signal is not inserted when this alarmoccurs.

Step 3 Click Apply.


----End



146

8.3.16 Setting Trigger Conditions of UNEQ InsertionThis section describes how to set the trigger conditions of UNEQ insertion for service ports.

Prerequisite



U2000

Procedure


Step 2 Choose Alarm > QoS Alarm > UNEQ Insertion Switch from the Function Tree.

Step 3 Set the trigger conditions of UNEQ insertion. If you select Enabled under an alarm, the UNEQsignal (all 0s) is inserted when this alarm occurs; otherwise, the UNEQ signal is not insertedwhen this alarm occurs.

Step 4 Click Apply.


----End

8.3.17 Setting Bit Error Thresholds for Service PortsThis section describes how to set bit error thresholds for service ports.

Prerequisite



U2000

Procedure


Step 2 Choose Alarm > QoS Alarm > Bit Error Alarm Threshold from the Function Tree.

Step 3 Set bit error thresholds.

Step 4 Click Apply.


----End



147

8.3.18 Setting Monitoring and Auto-Report Status of PerformanceEvents

This section describes how to set monitoring and auto-report status of specific performanceevents for monitored objects.



Procedure


Step 2 Choose Performance > Performance Monitor Status from the Function Tree.

Step 3 Set the following parameters: Monitor Status, 15-Minute Auto-Report, and 24-Hour Auto-Report.

Step 4 Click Apply.


----End

8.3.19 Setting Performance ThresholdsThis section describes how to set the thresholds of specific performance events for monitoredobjects.



Procedure


Step 2 Choose Performance > Performance Threshold from the Function Tree.

Step 3 Set Threshold Value.

Step 4 Click Apply.


----End



148

8.3.20 Resetting Performance RegistersThis section describes how to reset performance registers. After performance registers are reset,their counts are cleared and they immediately start a new counting period.



Procedure


Step 2 Choose Performance > Reset Board Performance Register from the Function Tree.

Step 3 Set Monitored Object and register types.

Step 4 Click Reset.

Step 5 In the Hint dialog box that is displayed, click Yes.


----End

8.4 Querying a ReportYou can obtain the version, manufacture, and microwave link information of all the boards byquerying the corresponding report.

8.4.1 Querying the Board Information ReportYou can obtain the logic version, and software version of each board by querying the boardinformation report.



Procedure

Step 1 Choose Inventory > Physical Inventory from the Main Menu.

Step 2 Select Board from Physical Inventory Type in the Physical Inventory window.

Step 3 In Physical Inventory, click the Board List tab.



149

Step 4 Click Filter.In Filter window, set the board or board attributes that need to be queried. Click OK.

Step 5 The board information displayed in the Board List.

Step 6 Optional: Click Save As.Set the parameters in Saving Options.

Step 7 Click OK. Then, you can save and archive the board information as a text file.


----End

8.4.2 Querying the Board Manufacturing Information ReportYou can obtain the manufacturing information about each board and the SFP module by queryingthe board manufacturing information report.

Prerequisite



U2000

Procedure

Step 1 Choose Inventory > Project Document > Board Manufacturer Information from the MainMenu.

Step 2 In Board Manufacturer Information, click the Board Manufacturer Information tab.

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


Step 5 Click Query.The Query processing bar is displayed.


Step 7 Optional: Click Save As.

Step 8 Set the parameters in Saving Options.

Step 9 Click OK. Then, you can save and archive the board manufacturing information as a text file.

----End

8.4.3 Querying the Microwave Link Information ReportYou can obtain the current and recent transmit/receive power of microwave links by queryingthe microwave link information report.



150

Prerequisite



U2000

Procedure

Step 1 In Main Menu, choose Inventory > Microwave Report > Microwave Link Report.

Step 2 In the left pane of the Microwave Link Report tab page, choose one or more NEs, and click

.


Step 4 Optional: Click Save As.


Step 6 Click OK. Then, you can save and archive the microwave link information as a text file.

----End

8.4.4 Querying the Network-wide License ReportBy querying the network-wide license report, you can check the license information of each NE.

Prerequisite


Tools, Instruments, and Materials

U2000

Procedure

Step 1 Choose Inventory > Microwave Report > Microwave License Capacity Report from theMain Menu.

Step 2 Select one or more NEs in the left pane, and click .


Step 4 Optional: Click Save As. Save the license report as a file and archive the file properly.


Step 6 Click OK. Then, the license report is saved and archived as a file.

----End



151

8.5 Software LoopbackSoftware loopback refers to the loopback operation that is implemented by using the NMS.During software loopback, you need not visit the engineering site. Hence, software loopback isused more widely than hardware loopback.

8.5.1 Setting Loopback for the SDH Optical Interface BoardThe SDH optical interface board supports the optical/electrical interface inloop/outloop and theVC-4 path inloop/outloop.



ContextThe optical/electrical interface inloop is a process wherein the signals over an SDH port arelooped back at the overhead processing unit towards the backplane.

Figure 8-5 Optical/electrical interface inloop

SDH opticalinterface boardBackplane

SDH

The optical/electrical interface outloop is a process wherein the signals over an SDH port arelooped back at the overhead processing unit towards the remote equipment.

Figure 8-6 Optical/electrical interface outloop


SDH



152

The VC-4 path outloop is a process wherein the signals on a VC-4 path are looped back at thelogic processing unit towards the remote equipment.

Figure 8-7 VC-4 path outloop


VC-4

The VC-4 path inloop is a process wherein the signals on a VC-4 path are looped back at thelogic processing unit towards the backplane.

Figure 8-8 VC-4 path inloop

SDH opticalboardBackplane

VC-4

Precautions

CAUTIONl The services may be interrupted at the port or on the path where the loopback is performed.l A software loopback may be released automatically after a certain period (five minutes, by

defaults). For details, see 8.11 Setting the Automatic Release Function.

Procedure

Step 1 Select the SDH optical interface board from the Object Tree.

NOTEThe SDH optical interface boards described in this section include the physical SL1D and SL1DA board andthe logical SL1D board that the physical CSTA/CSHC board maps.



153

Step 2 Choose Configuration > SDH Interface from the Function Tree.

Step 3 Select By Function, and select the loopback mode from the drop-down list.

To Perform... Choose...

Optical/electrical interface loopback Optical(Electrical) Interface Loopback

VC-4 path loopback VC4 Loopback

Step 4 Set the loopback status of the port or path based on the requirements.

Step 5 Click Apply.Then, the Confirm dialog box is displayed.

Step 6 Click OK.


----End

8.5.2 Setting Loopback for the Tributary BoardThe tributary board supports the tributary inloop and outloop.

Prerequisite



U2000

Context

The tributary inloop is a process wherein the signals over a PDH port are looped back at thecoding/decoding unit towards the backplane.

Figure 8-9 Tributary inloop

PDH interface boardBackplane

PDH

The tributary outloop is a process wherein the signals on a tributary path are looped back at thePDH interface board of the local IDU towards the remote equipment.



154

Figure 8-10 Tributary outloop

PDH

PDH interface boardBackplane

Precautions

CAUTIONThe services may be interrupted on the port or on the path where the loopback is performed.

Procedure

Step 1 Select the PDH interface board from the Object Tree.

NOTEThe tributary boards described in this section include the physical SP3S and SP3D boards and the logical SP3Sand SP3D boards that the physical CSTA, CSHA, CSHB, and CSHC boards map.

Step 2 Choose Configuration > PDH Interface from the Function Tree.

Step 3 Select By Function, and select Tributary Loopback from the drop-down list.

Step 4 Set the loopback status of the path based on the requirements.


Step 6 Click OK.


----End

8.5.3 Setting a Loopback for the Smart E1 Processing BoardA Smart E1 processing board supports inloops and outloops on E1 ports.


Before setting a loopbacks on the ports of the MP1 board, set PDH ports to Smart E1 portsaccording to Setting Working Modes of E1 Ports.



155


U2000

Context

The E1 inloop is a process wherein the signals over an E1 port are looped back from the coding/decoding unit to the backplane.

Figure 8-11 E1 inloop

Smart E1Processing BoardBackplane

E1

The E1 outloop is a process wherein the signals over an E1 port are looped back from the SmartE1 processing board of the local IDU to the remote equipment.

Figure 8-12 E1 outloop

E1

Smart E1Processing BoardsBackplane

Precautions

CAUTIONl The services may be interrupted at the port or on the path where the loopback is performed.l A software loopback may be released automatically within a period (5 minutes, by default).

For details, see 8.11 Setting the Automatic Release Function.

NOTE

The MP1 is a logical board derived from mapping of the tributary unit of the CSHD/CSHE board.



156

ProcedureStep 1 Select the operation object from the Object Tree.


Loopback on the MP1 board NE

Loopback on the other Smart E1 boards Smart E1 processing board

Step 2 Choose Configuration > Interface Management > PDH Interface from the Function Tree.

Step 3 In the Advanced Attributes tab, select the required port.

Step 4 Set the loopback status of the port as required.

Step 5 Click Apply.The system displays a prompt dialog box for confirmation.

Step 6 Click OK.

Step 7 Close the dialog box.

----End

8.5.4 Setting a Loopback for the Packet-plane Ethernet InterfaceBoard

The Packet-plane Ethernet interface board supports the Ethernet port inloop (at the MAC layerand PHY layer).



ContextThe Ethernet port MAC inloop is a process wherein the Ethernet physical signals are loopedback at the service processing module of the board at the MAC layer towards the backplane.The Ethernet port PHY inloop is a process wherein the Ethernet frame signals are looped backat the interface module of the board at the PHY layer towards the backplane.

Figure 8-13 Ethernet port inloop

Ethernet serviceprocessing boardBackplane

PHYMAC



157

Precautions

NOTE

The tributary boards described in this section include the physical EM6TA, EM6FA, EM6T and EM6F boardsand the logical EM4T, EM4F, boards that the physical CSHA, CSHB, CSHC, CSHD and CSHE boards map.

PORT 10 on the EFP8 board can not be configured with loops.

PORT 8 on the EMS6 board can not be configured with loops.

CAUTIONl A loopback operation results in service interruption.l A software loopback may be released automatically after a certain period (five minutes, by

defaults). For details, see 8.11 Setting the Automatic Release Function.

CAUTIONWhen Port Mode of an Ethernet port is set to Layer 3, do not perform any loopback on the port.In this case, LSP Traceroute is recommended for locating faults.

Procedure

Step 1 Select an Ethernet processing board from the Object Tree.

Step 2 Select the corresponding function options from the Function Tree based on the loopback type.


PHY loopback 1. Choose Configuration > Interface Management > EthernetInterface from the Function Tree.

2. Click the Advanced Attributes tab.

MAC loopback 1. Choose Configuration > Interface Management > EthernetInterface from the Function Tree.

2. Click the Advanced Attributes tab.

Step 3 Set the loopback status of the port based on the requirements.


Step 5 Click OK.


----End



158

8.5.5 Setting Loopbacks for the EOS/EoPDH-Plane EthernetInterface Board

EPF8 board supports the inloop at Ethernet ports (at the MAC layer and PHY layer) and theinloop in VC-12 paths. EMS6 board supports the inloop at Ethernet ports (at the MAC layer andPHY layer) and the inloop in VC-3 paths.


Tools, Instruments, and MaterialsU2000

ContextA MAC layer inloop is an inloop where the service processing module loops back the Ethernetphysical signals towards the backplane through the MAC layer. A PHY layer inloop is an inloopwhere the interface module loops back the Ethernet frame signals towards the backplane throughthe PHY layer.

NOTE

PORT 9 in the EFP8 board only supports inloop at the MAC layer.

PORT 7 in the EMS6 board only supports inloop at the MAC layer.

Figure 8-14 Ethernet port inloop

Ethernet serviceprocessing boardBackplane

PHYMAC

An inloop in a VC-12 path is an inloop where the logic processing unit of a board loops backthe signals in a specific VC-12 path towards the backplane.


EOPDH

Backplane EFP8



159

An inloop in a VC-3 path is an inloop where the logic processing unit of a board loops back thesignals in a specific VC-3 path towards the backplane.


EOS

Backplane EMS6

Precautions

CAUTIONl A loopback operation may interrupt the services on the port where the loopback is performed.

l A software loopback may be automatically released within a period (five minutes by default).For details, see 8.11 Setting the Automatic Release Function.

NOTE

A VC-3 loopback can be performed only after the EMS6 is configured with services.

Procedure

Step 1 In NE Explorer, select the required board from the Object Tree.

Step 2 Select the corresponding function options from the Function Tree according to the loopbacktype.


PHY loopback 1. Choose Configuration > Ethernet Interface Management >Ethernet Interface from the Function Tree.

2. Select External Port.3. Click the Basic Attributes tab.

MAC loopback 1. Choose Configuration > Ethernet Interface Management >Ethernet Interface from the Function Tree.

2. Select External Port.3. Click the Basic Attributes tab.



160


VC-12 path inloop 1. Choose Configuration > SDH Interface from the Function Tree.2. Select By Function.3. Select the required VC-12 path.

VC-3 path inloop 1. Choose Configuration > SDH Interface from the Function Tree.2. Select By Board/Port(Channel).3. Select the required VC-3 path.

Step 3 Set the loopback status of the port as required.

Step 4 Click Apply.The confirmation dialog box is displayed.

Step 5 Click OK.The prompt dialog box is displayed.

Step 6 Click OK.

Step 7 Close the prompt dialog box.

----End

8.5.6 Setting Loopback for the IF BoardLoopbacks on the IF board are classified into IF port loopback, composite port loopback, andIntegrated IP radio port MAC loopback. The IF1 board supports the IF port inloop, IF portoutloop, composite port inloop, and composite port outloop. The IFU2/IFX2 board supports theIF port inloop, IF port outloop, composite port inloop, composite port outloop, and IntegratedIP radio port MAC inloop. The ISU2/ISX2 board supports the IF port inloop, IF port outloop,composite port inloop, and composite port outloop.



ContextThe IF port inloop is a process wherein the IF signals are looped back at the modem unit towardsthe backplane.



161

Figure 8-17 IF port inloop

IF boardBackplane

IF signal

The IF port outloop is a process wherein the IF signals are looped back at the modem unit of theboard towards the remote equipment.

Figure 8-18 IF port outloop

IF boardBackplaneIF signal

The composite port inloop is a process wherein the microwave baseband signal is looped backat the MUX/DEMUX unit of the board towards the backplane.

Figure 8-19 Composite port inloop

IF boardBackplaneMicrowave

baseband signal

The composite outloop is a process wherein the microwave baseband signal is looped back atthe MUX/DEMUX unit of the board towards the remote equipment.



162

Figure 8-20 Composite port outloop

IF boardBackplaneMicrowavebaseband

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 released automatically after a certain period (five minutes, by

defaults). For details, see 8.11 Setting the Automatic Release Function.l To perform the software loopback on the standby IF board of the 1+1 HSB/FD/SD protection

group, switch the standby IF board to the working state forcedly. Otherwise, the operationmay fail.

l Before performing the loopback operation for the IFU2/IFX2 board, disable the AM functionat both ends of the radio link.

CAUTIONWhen Port Mode of an Integrated IP radio port is set to Layer 3, do not perform any loopbackon the port. In this case, LSP Traceroute is recommended for locating faults.

Procedure

Step 1 Select the corresponding IF board from the Object Tree in the NE explorer.

Step 2 Choose Configuration > Interface Management > Microwave Interface from the FunctionTree.

Step 3 Select Loopback Attributes.

Step 4 Select the port where the loopback needs to be performed and set loopback type.


Step 6 Click OK to close the dialog box.Then, a dialog box is displayed.



163


----End

8.5.7 Locating a Fault by Performing Loopback OperationsLoopback is a common method of locating the fault.



Service TrailFigure 8-21 shows how to locate a fault by performing a loopback operation.

Figure 8-21 Service trail

IFboard

Cross-connectboard

SDHtributaryboard

ODU

NE2

IFboard

Cross-connectboard

SDHtributaryboard

ODU

NE3

Optical cable

IFboard

Cross-connectboard ODU

NE4

PDHtributaryboard

IFboard

Cross-connectboard ODU

NE1

PDHtributaryboard

PrecautionsThe LSP Traceroute method, instead of sectional loopbacks, is recommended for locating thefaults of PWE3 services.

Procedure

Step 1 If the services are available on the radio links, perform the inter-station loopbacks to narrowdown the fault to a specific hop.



164

1. Set the outloops for the SDH optical interface boards on NE2 and NE3, and then performthe inter-station loopbacks to locate the fault.

Step 2 After the fault is located on the specific radio link, perform the intra-station loopbacks to narrowdown the fault to a specific NE or board.1. Set inloop for the IF board on the NEs at both ends of the radio link where the fault occurs,

to check whether the service receiver or the radio link is faulty.2. If the fault is located in the service receiver, set outloop for the PDH tributary board to

check whether the interface board or switch unit is faulty.3. If the radio link is faulty, replace the IF board and ODU to check whether the IF board or

ODU is faulty.

----End

8.6 ResetReset is an important method of troubleshooting software faults. Reset is classified into coldreset, warm reset.

8.6.1 Cold ResetCold reset is a process wherein the board software is reset and the board is re-initiated. Thesoftware of each board runs as a software module in the CPU on the system control, switching,and timing board. During the board initialization, the FPGA, if any, is re-loaded.

Prerequisite



U2000

Precautions

CAUTIONCold reset causes service interruption because it is similar to the procedure of removing andinserting a board.

Procedure

Step 1 In NE Panel, right-click the board where the cold reset needs to be performed.

Step 2 Choose Cold Reset from the shortcut menu.Then, the Warning dialog box is displayed.

Step 3 Click OK.



165


----End

8.6.2 Warm ResetWarm reset is a process wherein the board software is reset but the board is not re-initiated. Thesoftware of each board runs as a software module in the CPU on the integrated board of thesystem control unit, cross-connect unit, and timing unit.



PrecautionsDuring warm reset, the board software is reset but the services are not interrupted.

Procedure

Step 1 In NE Panel, right-click the board where the warm reset needs to be performed.

Step 2 Choose Warm Reset from the shortcut menu.Then, the Warning dialog box is displayed.

Step 3 Click OK.


----End

8.7 PRBS TestThe pseudorandom binary sequence (PRBS) test is an important method of network maintenanceand self-check.

8.7.1 Performing a PRBS Test for the Tributary BoardIf a special test tool is unavailable, you can perform the PRBS test by using the embedded testsystem on the tributary board.





166

ContextThe OptiX RTN 910 supports the PRBS test in the tributary direction and in the cross-connectdirection.

The PRBS test in the tributary direction can be performed to check the connection between thetributary board and the DDF, as shown in Figure 8-22.

Figure 8-22 PRBS test in the tributary direction

PRBSTransmitter

PRBSRecevicer

PDH interface boardDDF frame

1

1 Loopback at the DDF frame

The PRBS test in the cross-connect direction can be performed to check the connection betweenthe tributary board and the remote NE, as shown in Figure 8-23.

Figure 8-23 PRBS test in the cross-connect direction

Cross-connectboard

PRBStransmitter

PRBSreceiver

PDH interfaceboard IF board

NE at the local end NE at the opposite end

IN

OUT

VC-4 inloop orcomposite port inloop

IF port inloop IF port outloop1

2 3

2 3

IF board

1

a) IF board working as the line board



167

Cross-connect board

PRBStransmitter

PRBSreceiver

PDH interface board

NE at the local end NE at the opposite end

IN

OUT

VC-4 inloop Port inloop Port outloop1

2 3

2 3

SDH opticalinterface board

1

b) Line board working as the SDH optical interface board

Precautions

CAUTIONl During the PRBS test, the services in the tested path are interrupted.

l The PRBS test can be performed only in one path and in one direction at one time.

Procedure

Step 1 Set the loopback at the proper location. For details, see Figure 8-22 and Figure 8-23.

Step 2 Select the E1 interface board from the Object Tree.

Step 3 Choose Configuration > PRBS Test from the Function Tree.

Step 4 Select the port to be tested.

Step 5 Set Duration and Measured in Time.

NOTE

l The PRBS test supports three time units: one second, 10 minutes, and one hour.

l A maximum of 255 test cycles is permissible for the PRBS test.

Step 6 Optional: Select Accumulating Mode.

Step 7 Click Start to Test.A prompt is displayed.

Step 8 Click OK.

Step 9 When Process is displayed as 100%, click Query to check the test result.



168

NOTE

The result of a PRBS test can be normal, error, or invalid.

l Invalid: indicates that no bit is received. In this case, the curve is yellow.

l Normal: indicates that the path is in normal state. In this case, the number of PRBSs is zero, and thecurve is green.

l Error: indicates that the path has errors. In this case, the number of total PRBSs is a non-zero number,and the curve is red.

----End

8.7.2 Performing a PRBS Test for the IF BoardIf a special test tool is unavailable, you can perform the PRBS test by using the embedded testsystem on the IF board.



Precautions

Figure 8-24 PRBS test of the IF board

11

PRBStransmitter

PRBS

ODU

1

ODU

NE at the local end NE at the opposite endIF port outloop1

transmitter

IF board IF board



169

CAUTIONl During the PRBS test, the services in the tested path are interrupted.l The PRBS test can be performed only in one path and in one direction at one time.l The standby IF unit does not support the PRBS test. Before you perform the PRBS test for

the standby IF board of a 1+1 HSB/FD/SD protection group, you must switch the standbyIF board to the working state.

Procedure

Step 1 Perform an outloop on the opposite IF board. For details, see 8.5.6 Setting Loopback for theIF Board.

Step 2 Select the IF board from the Object Tree.

Step 3 Choose Configuration > PRBS Test from the Function Tree.

Step 4 Select the port to be tested.

Step 5 Set Duration and Measured in Time.

NOTE

l The time unit of the PRBS test can be one second, 10 minutes, or one hour.

l A maximum of 255 test cycles is permissible for the PRBS test.

Step 6 Optional: Select Accumulating Mode.

Step 7 Click Start to Test.A prompt is displayed.

Step 8 Click OK.

Step 9 When Process is displayed as 100%, click Query to check the test result.

NOTE

The result of a PRBS test can be normal, error, or invalid.

l Invalid: indicates that no bit is received. In this case, the curve is yellow.

l Normal: indicates that the path is in normal state. In this case, the number of PRBSs is zero, and thecurve is green.

l Error: indicates that the path has errors. In this case, the number of total PRBSs is a non-zero number,and the curve is red.

----End

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




170


Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer.

Step 2 Choose Configuration > License Management.

Step 3 Click Query, browse the license capacity of the NE.

----End

8.9 Setting the On/Off State of the LaserWhen performing operations such as testing a fiber cut, you can set the on/off state of the laserrather than removing and re-inserting the optical fiber on site.



Procedure

Step 1 Select the desired SDH optical interface board from the Object Tree.

Step 2 Choose Configuration > SDH Interface from the Function Tree.

Step 3 Select By Function.

Step 4 Select Laser Switch from the drop-down list.

Step 5 Select a port, and then set Laser Switch.

Step 6 Click Apply.A confirmation dialog box is displayed.

Step 7 Click OK.A prompt is displayed.

Step 8 Click OK.

----End

8.10 Setting the ALS FunctionThe SDH optical interface board supports the automatic laser shutdown (ALS) function. Thisfunction enables the board to turn off a laser when the board does not transmit services, theoptical fiber is faulty, or the received optical signals are lost.



171

Prerequisite



U2000

Procedure

Step 1 Select the desired SDH optical interface board from the Object Tree.

Step 2 Choose Configuration > Automatic Laser Shutdown from the Function Tree.

Step 3 Select a port, and then set Automatic Shutdown to Enabled.

Step 4 Click Apply to save the settings.


----End

8.11 Setting the Automatic Release FunctionTo protect the communication between the NMS and NE against improper operations, an NEsupports the automatic release of the ODU muting, software loopback, and other operations thatrequire you to exercise caution. The automatic release time is five minutes by default. You canset whether to enable the automatic release function and the automatic release time through theNMS.

Prerequisite



U2000

Procedure

Step 1 Choose Configuration > NE Batch Configuration > Automatic Disabling of NE Functionfrom the Main Menu.

Step 2 Select the desired NE from the Object Tree. Click .

Step 3 In Automatic Disabling of NE Function, set Auto Disabling and Auto Disabling Time(min).

Step 4 Click Apply to complete the settings for the automatic release function.

----End



172

8.12 Querying Power Consumption of BoardsThis section describes how to query power consumption of the ODU and each board.



Procedure

Step 1 Choose Configuration > NE Batch Configuration > Power Management from the MainMenu.

Step 2 In the NE Power dialog box, select the Board Power tab.

Step 3 Select the required NE or board from the object tree, and then click .

Step 4 Click Query.The Query progress bar is displayed.


Step 6 On the Board Power tab page, browse Nominal Power Consumption and Current PowerConsumption of the selected board.

----End

8.13 Querying the Impedance of an E1 ChannelThe impedance of an E1 channel is 75 ohms or 120 ohms.



Procedure

Step 1 Select a PDH tributary board from the Object Tree.

Step 2 Choose Configuration > PDH Interface from the Function Tree.

Step 3 Select By Board/Port(Channel).

Step 4 Select Port in the list.



173

Step 5 Select a port, and check Port Impedance.

----End

8.14 Monitoring Ethernet Packets Through Port MirroringTo monitor and analyze the Ethernet packets at a port, you can enable the port mirroring functionso that the received or transmitted packets on the port are duplicated to another Ethernet port towhich the Ethernet tester is connected. Then, you can monitor and analyze the packets. Thisfunction is supported by the EFP8/EMS6 board of the OptiX RTN 910.



ContextThe OptiX RTN 910 supports the mirroring, monitoring, and analyzing of the Ethernet packetsthat are received or transmitted on the port.

Figure 8-25 Schematic diagram of Ethernet port mirroring

Mirroringport

Ethernet processing unit

Monitoringport

Ethernetequipment

Ethernet testerDuplication

To monitor the data in different directions, port mirroring can be performed in the ingressdirection and in the egress direction. For the ports on EFP8/EMS6 board:

l In the ingress directionAlso in the upstream direction. The equipment duplicates the packets received from themirroring port to the observing port, and then transmits the packets from the observing portto the Ethernet tester.

l In the egress directionAlso in the downstream direction. The equipment duplicates the packets transmitted by themirroring port to the observing port, and then transmits the packets from the observing portto the Ethernet tester.

In the ingress direction, the ports mirror the data transmitted from the VCTRUNK to the TDMside. In the egress direction, the ports mirror the data transmitted from the TDM side to theVCTRUNK.



174

Procedure

Step 1 In NE Explorer, select the EFP8or EMS6 board.

Step 2 Choose Configuration > Ethernet Interface Management > Port Mirroring from theFunction Tree.

Step 3 Click New, and set Mirror Listener Port, Uplink Listened Port, and Downlink ListenedPort.

Step 4 Click OK.

----End

8.15 Querying the Attributes of an Ethernet PortThrough the operation, you can learn about the attributes of an Ethernet port, such as rate.

Prerequisite



U2000

Procedure

Step 1 Optional: Query the attributes of the FE or GE port on the packet plane.1. In NE Explorer, select the required NE from the Object Tree.2. Choose Configuration > Interface Management > Ethernet Interface from the Function

Tree.3. Click the Advanced Attributes tab.4. Check the parameters such as Port Physical Parameters, Transmitting Rate, and

Receiving Rate.

Step 2 Optional: Querying the attributes of the Integrated IP radio port.1. In NE Explorer, select the required NE from the Object Tree.2. Choose Configuration > Interface Management > Microwave Interface from the

Function Tree.3. Click the Advanced Attributes tab.



175

4. Check the parameters such as Transmitting Rate and Receiving Rate.

Step 3 Optional: Query the attributes of the external port on the EFP8 board.1. In NE Explorer, select the EFP8 board from the Object Tree.2. Choose Configuration > Ethernet Interface Management > Ethernet Interface from

the Function Tree.3. Select External Port.4. Click the Advanced Attributes tab.5. Check the parameters such as Transmitting Rate and Receiving Rate.

NOTE

By performing this operation, you can query the attributes of the external ports on the EFP8 board (PORT1 toPORT8) and the attributes of the bridging port on the EFP8 board (PORT9).

----End

8.16 Setting Traffic, Physical Bandwidth, or BandwidthUtilization of Ethernet Ports

To query the traffic, physical bandwidth, or bandwidth utilization of Ethernet ports within acertain period, you need to enable the monitoring for the object before that period starts. TheFE/GE ports and Integrated IP radio ports on the packet plane support this operation.


The flow monitoring function is enabled on the Ethernet port. To enable the flow monitoringfunction on a port, see 8.16 Setting Traffic, Physical Bandwidth, or Bandwidth Utilizationof Ethernet Ports.


Background InformationAfter the flow monitoring function is enabled, the system saves the statistics about the receivedtraffic and transmitted traffic with an interval of 15 minutes. In normal cases, the system storesthe statistics that are collected in the last 30 days. In the system, every measurement entry showsthe average transmit rate and average receive rate within a period of 15 minutes. You can querythe statistics in the last 30 days.

Procedure

Step 1 Select a board from the Object Tree in the NE Explorer.

Step 2 Choose Performance > Ethernet Port Flow Monitoring from the Function Tree.

Step 3 Select the Set Monitoring tab. Set Flow Monitoring, Physical Bandwidth Monitoring,Bandwidth Usage Monitoring to Enabled for the Ethernet port.



176

Step 4 Click Apply.

Step 5 Close the displayed Result dialog box.

----End

8.17 Querying Traffic, Physical Bandwidth, or BandwidthUtilization of Ethernet Ports

This section describes how to query the change curve of the traffic, physical bandwidth, orbandwidth utilization of Ethernet ports within a certain period. The FE/GE ports and IntegratedIP radio ports on the packet plane support this operation.

Prerequisite


The flow monitoring function is enabled on the Ethernet port. To enable the flow monitoringfunction on a port, see 8.16 Setting Traffic, Physical Bandwidth, or Bandwidth Utilizationof Ethernet Ports.


U2000

Background Information

After the flow monitoring function is enabled, the system saves the statistics about the receivedtraffic and transmitted traffic with an interval of 15 minutes. In normal cases, the system storesthe statistics that are collected in the last 30 days. In the system, every measurement entry showsthe average transmit rate and average receive rate within a period of 15 minutes. You can querythe statistics in the last 30 days.

Procedure

Step 1 Select a board from the Object Tree in the NE Explorer.

Step 2 Choose Performance > Ethernet Port Flow Monitoring from the Function Tree.

Step 3 Select the Query Flow tab.

Step 4 Set the Monitored Object, Monitored Indicator, Start Time, End Time, and DisplayMode.

Step 5 Click Query.The system displays the query result in a table or in a graph.



177

Step 6 Close the displayed Result dialog box.

----End

8.18 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. Only the FE port on the EFP8 board supports this operation.

Prerequisite



U2000

PrecautionsNOTE

The receive traffic threshold cannot be set for the Ethernet ports on the packet domain.

Procedure

Step 1 In NE Explorer, select an Ethernet processing 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 Select an Ethernet port and set Traffic Threshold and Port Traffic Threshold TimeWindow.

Step 6 Click Apply.

----End

8.19 Using the Ethernet Test FramesBy using the Ethernet test frames, you can check the connectivity of VCTRUNKs. Only theEFP8 board supports this operation.

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

l The service traffic is encapsulated or mapped by using the GFP method.



178


Background InformationThe Ethernet board uses the specific GFP management frame or Ethernet frame as the test frame.One frame is transmitted to the opposite Ethernet board per second. After receiving the testframe, the Ethernet board returns the response frame. Upon receiving the response frame, theEthernet service processing board at the local end can judge the connectivity of the VCTRUNKin between.

Figure 8-26 Ethernet test frames between Ethernet boards

LocalEthernet

board

RemoteEthernet

board

Test frame

Response frame

Precautions

CAUTIONDo not use the test frames when the network traffic is heavy.

Procedure

Step 1 In NE Explorer, select the EFP8 board.

Step 2 Choose Configuration > Ethernet Maintenance > Ethernet Test from the Function Tree.Then, the Ethernet Test dialog box is displayed.

Step 3 Select the test port and click Clear Counters. Select Clear All Counters .

Step 4 Set Send Mode and Frames to Send.

NOTE

It is recommended that you choose "Burst mode", and a maximum of 10 frames can be transmitted eachtime.

Step 5 Click Apply.The system starts transmitting and receiving test frames.

Step 6 After Status displays Finished Sending, click Query.

Step 7 Check Counter of Frames Sent and Counter of Received Response of Test Frame.



179

Test frames are used to check the network connectivity. If some of the test frames are lost butno alarm is reported on the SDH side, you can infer that the network is normal. If all the testframes are lost, you can infer that the network is faulty.

----End

Related InformationIf you choose the continue mode, the local port transmits test frames continuously until the testis disabled.



180

A Alarm Reference

Alarms are important indicators when abnormalities occur on the equipment. This chapterdescribes all the possible alarms on the OptiX RTN 910 and how to handle these alarms.

A.1 Alarm List (in Alphabetical Order)The following table lists all the possible alarms generated by the OptiX RTN 910 in alphabeticalorder.

A.2 Alarm List (Classified by Logical Boards)This part lists the alarms that are reported by each board.

OptiX RTN 910 Radio Transmission SystemMaintenance Guide (U2000) A Alarm Reference


181

A.1 Alarm List (in Alphabetical Order)The following table lists all the possible alarms generated by the OptiX RTN 910 in alphabeticalorder.

Table A-1 Alarm list

Alarm Name Description Alarm Severity

A_LOC Loss of clock in theupstream bus

Major

ALM_E1RAI E1 link remote alarmindication

Minor

ALM_GFP_dCSF Loss of GFP clientsignals

Critical

ALM_GFP_dLFD Out of frame state ofgeneric framingprocedure (GFP)frames

Major

ALM_IMA_LIF Frame delimitation isout-of-frame at thelocal end of the IMAlink.

Major

ALM_IMA_LODS Differential delay ofthe IMA link crossesthe threshold.

Major

ALM_IMA_RE_RX_UNUSABLE The IMA link on theopposite NE fails inthe receive direction.

Minor

ALM_IMA_RE_TX_UNUSABLE The IMA link on theopposite NE fails inthe transmitdirection.

Minor

ALM_IMA_RFI Frame delimitation isout-of-frame at theremote end of theIMA link.

Major

AM_DOWNSHIFT Downshift of AMmodes

Major

APS_FAIL Failure indication ofMS protectionswitching

Major



182


APS_INDI Indication of the APSprotection switching

Major

APS_MANUAL_STOP MS protocol stoppedmanually

Minor

ATMPW_UNKNOWNCELL_EXC The number ofunknown ATM cellsexceeds the specifiedthreshold in a timeunit.

Major

AU_AIS AU alarm indication Major

AU_LOP Loss of AU pointers Major

B1_EXC Excessiveregenerator sectionerrors (B1)

Minor

B1_SD Signal degradationdue to excessiveregenerator sectionerrors (B1)

Minor

B2_EXC Excessive multiplexsection errors (B2)

Major

B2_SD Signal degradationdue to excessivemultiplex sectionerrors (B2)

Minor

B3_EXC Excessive higherorder path bit errors(B3)

Major

B3_EXC_VC3 Excessive B3 biterrors in a VC-3 path

Major

B3_SD Signal degradationdue to excessivehigher order path biterrors (B3)

Minor

B3_SD_VC3 Signal degradationdue to excessiveVC-3 path (B3) biterrors

Minor

BAT1TEMP_SENSOR_FAIL The temperaturesensor of batterygroup 1 fails.

Major



183


BAT2TEMP_SENSOR_FAIL The temperaturesensor of batterygroup 2 fails.

Major

BD_NOT_INSTALLED The logical board isnot added on theNMS.

Minor

BD_STATUS The board is out-of-position.

Major

BDTEMP_SENSOR_FAIL The boardtemperature sensor ofthe cabinet fails.

Major

BIP_EXC Excessive BIP errors Minor

BIP_SD Signal degradationdue to excessive BIPerrors

Minor

BOOTROM_BAD BOOTROM datacheck fails.

Major

BUS_ERR Bus errors Critical

CES_ACR_LOCK_ABN The locking functionof CES ACR serviceclock is abnormal.

Minor

CES_JTROVR_EXC The number of jitterbuffer overflowscrosses the specifiedthreshold.

Major

CES_JTRUDR_EXC The number of jitterbuffer underflowscrosses the specifiedthreshold.

Major

CES_LOSPKT_EXC The number of lostpackets crosses thespecified threshold ina time unit.

Major

CES_MALPKT_EXC The number ofdeformed packetscrosses the specifiedthreshold in a timeunit.

Major



184


CES_MISORDERPKT_EXC The number of lostdisordered packetscrosses the specifiedthreshold in a timeunit.

Major

CES_RDI Remote defectindication

Minor

CES_STRAYPKT_EXC The number oferrored packetscrosses the specifiedthreshold in a timeunit.

Major

CESPW_OPPOSITE_ACFAULT The AC circuit on theopposite NE is faulty.

Major

CESPW_OPPOSITE_RAI Remote alarmindication

Major

CFCARD_FAILED The operation on theCF card fails.

Major

CFCARD_OFFLINE The CF card is off-line.

Major

CHCS Correctable cellerrors

Minor

CLK_NO_TRACE_MODE The clock source isnot in locked mode.

Minor

COMMUN_FAIL Inter-boardcommunication fails.

Major

CONFIG_NOSUPPORT Configuration is notsupported.

Major

DBMS_ABNORMAL The status ofdatabases isabnormal.

Major

DBMS_ERROR Errors in theprocessing of systemdatabases

Major

DBMS_PROTECT_MODE System databases inprotection mode

Critical

DCNSIZE_OVER Over-sized DCNnetwork

Major



185


DDN_LFA The frame alignmentsignal of framed E1services is lost.

Major

DOWN_E1_AIS Alarm indication of 2Mbit/s downstreamsignals

Minor

DROPRATIO_OVER The number of lostpackets due to portcongestion crossesthe threshold.

Minor

E1_LOC Loss of 2M clock inupstream signals

Major

E1_LOS Loss of 2 Mbit/s linesignals

Minor

ENVHUM_SENSOR_FAIL The ambienthumidity sensor ofthe cabinet fails.

Major

ENVTEMP_SENSOR_FAIL The ambienttemperature sensor ofthe cabinet fails.

Major

ENVTEMP1_SENSOR_FAIL The ambienttemperature sensor 1of the cabinet fails.

Major

ENVTEMP2_SENSOR_FAIL The ambienttemperature sensor 2of the cabinet fails.

Major

ETH_APS_LOST Loss of APS frames Minor

ETH_APS_PATH_MISMATCH The working andprotection paths ofthe APS protectiongroup differ betweenthe two ends.

Major

ETH_APS_SWITCH_FAIL Protection switchingfailure

Major

ETH_APS_TYPE_MISMATCH Protection schememismatch

Major

ETH_CFM_LOC Loss of connectivity Critical

ETH_CFM_MISMERGE Misconnection Critical



186


ETH_CFM_RDI The maintenanceassociation end point(MEP) fails toreceive CCMpackets.

Minor

ETH_CFM_UNEXPERI Errored frames Minor

ETH_EFM_DF Discovery failure Major

ETH_EFM_EVENT Performance eventsat the opposite end

Major

ETH_EFM_LOOPBACK A loopback occurs. Major

ETH_EFM_REMFAULT Faults occur at theopposite end.

Critical

ETH_LOS Loss of Ethernet portconnection

Critical

ETH_NO_FLOW No flow on theEthernet port

Major

ETHOAM_DISCOVER_FAIL Discovery failure isdetected by point-to-point Ethernet OAM.

Minor

ETHOAM_RMT_LOOP A remote loopback isdetected by point-to-point Ethernet OAM.

Minor

ETHOAM_RMT_SD Remote Ethernetperformancedegradation isdetected by point-to-point Ethernet OAM.

Minor

ETHOAM_RMT_CRIT_FAULT Severe faults aredetected by point-to-point Ethernet OAMat the remote end.

Minor

ETHOAM_SELF_LOOP An MAC portloopback is detectedby point-to-pointEthernet OAM.

Major

ETHOAM_VCG_SELF_LOOP A VCTRUNK portloopback is detectedby point-to-pointEthernet OAM.

Major



187


EX_ETHOAM_CC_LOS Loss of periodicalconnectivity checkpackets

Critical

EX_ETHOAM_MPID_CNFLCT Conflict ofmaintenance pointIDs

Major

EXT_SYNC_LOS Loss of externalclock sources

Critical

EXT_TIME_LOC Loss of external timesources

Major

FAN_AGING Aged fans Minor

FAN_FAIL Failure of fan boards Major

FCS_ERR Frame checksequence (FCS)errors

Critical

FLOW_OVER Excessive data trafficreceived by Ethernetports

Minor

HARD_BAD Hardware faults Critical

HP_CROSSTR Threshold-crossingperformance event ofthe higher order path

Minor

HP_LOM Loss of multiframesin the higher orderpath

Major

HP_RDI Higher order pathremote defectindication

Minor

HP_REI Higher order pathremote errorindication

Warning

HP_SLM Higher order pathsignal labelmismatch

Minor

HP_TIM High order path traceidentifier mismatch

Minor

HP_UNEQ Unequipped higherorder path

Minor



188


HPAD_CROSSTR Adaptationperformancethreshold-crossing ofthe higher order path

Minor

IF_CABLE_OPEN IF cables aredisconnected.

Major

IF_INPWR_ABN The power suppliedby an IF board to anODU is abnormal.

Major

IF_MODE_UNSUPPORTED Preset IF workingmode is notsupported.

Major

IMA_GROUP_LE_DOWN The IMA group at thelocal end fails.

Major

IMA_GROUP_RE_DOWN The IMA group at theremote end fails.

Major

IMA_TXCLK_MISMATCH The transmit clockmodes at the two endsof the IMA group aredifferent.

Minor

IN_PWR_ABN Abnormal inputoptical power

Major

IN_PWR_HIGH Over high inputoptical power

Critical

IN_PWR_LOW Over low inputoptical power

Critical

INTEMP_SENSOR_FAIL The air inlettemperature sensor ofthe cabinet fails.

Major

J0_MM Trace identifiermismatch

Minor

K1_K2_M K1 and K2 mismatch Minor

K2_M K2 mismatch Minor

LAG_BWMM Bandwidthinconsistency in theLAG group

Major

LAG_DOWN The LAG isunavailable.

Major



189


LAG_MEMBER_DOWN A member port of alink aggregationgroup (LAG) isunavailable.

Minor

LAG_PORT_FAIL A member port of aLAG fails.

Minor

LAG_VC_PORT_FAIL A VCG port of anLAG fails.

Minor

LAN_LOC Ethernetcommunicationfailure

Major

LASER_CLOSED The laser is shutdown.

Major

LASER_MOD_ERR The type of thepluggable opticalmodule on the boarddoes not match thetype of the opticalinterface.

Major

LASER_MOD_ERR_EX The type of thepluggable opticalmodule on the boarddoes not match thetype of the opticalinterface.

Major

LASER_SHUT The laser is shutdown.

Major

LCAS_FOPR LCAS protocol failsin the receivedirection.

Major

LCAS_FOPT LCAS protocol failsin the transmitdirection.

Major

LCAS_PLCR Loss of partialbandwidth in theLCAS receivedirection

Minor

LCAS_PLCT Loss of partialbandwidth in theLCAS transmitdirection

Minor



190


LCAS_TLCR Loss of totalbandwidth in theLCAS receivedirection

Major

LCAS_TLCT Loss of totalbandwidth in theLCAS transmitdirection

Major

LCD Loss of celldelimitation

Major

LCS_LIMITED The capacity of theconfigured servicesexceeds the rangepermitted by thelicense file.

Major

LFA Out of frame state ofE1 frames

Major

LICENSE_DIFF The license file on theIF board is differentfrom the backup fileon the system controlboard.

Warning

LICENSE_LOST The NE fails to detectany license file.

Major

LINK_ERR Faults occur in a datalink.

Critical

LMFA Out of frame state ofE1 multiframes

Major

LOOP_ALM A loopback occurs. Minor

LP_CROSSTR Performancethreshold-crossing ofthe lower order path

Minor

LP_R_FIFO FIFO overflow on thereceive side of thelower order path

Minor

LP_RDI Lower order pathremote defectindication

Minor

LP_RDI_VC12 VC-12 path remotedefect indication

Minor



191


LP_RDI_VC3 VC-3 path remotedefect indication

Minor

LP_REI Lower order pathremote errorindication

Minor

LP_REI_VC12 VC-12 path remoteerror indication

Minor

LP_REI_VC3 VC-3 path remote biterror indication

Minor

LP_RFI Lower order pathremote failureindication

Minor

LP_SLM Lower order pathsignal labelmismatch

Minor

LP_SLM_VC12 VC-12 path signallabel mismatch

Minor

LP_SLM_VC3 VC-3 path signallabel mismatch

Minor

LP_T_FIFO FIFO overflow on thetransmit side of thelower order path

Minor

LP_TIM Lower order pathtrace identifiermismatch

Minor

LP_TIM_VC12 VC-12 path traceidentifier mismatch

Minor

LP_TIM_VC3 VC-3 path trackingidentificationmismatch

Minor

LP_UNEQ Unequipped lowerorder paths

Minor

LP_UNEQ_VC12 Unequipped VC-12paths

Minor

LP_UNEQ_VC3 VC-3 pathunequipped

Minor

LPS_UNI_BI_M The switching modeis single-ended at oneend and dual-ended atthe other end.

Minor



192


LPT_CFG_CLOSEPORT The LPT closes theaccess port of thelocal NE.

Major

LPT_INEFFECT LPT function failed Major

LPT_RFI Link state pass-through function failsat the remote end.

Critical

LSR_NO_FITED Laser not installed Critical

LTI Loss of clocksynchronizationsource

Major

MAC_EXT_EXC The number of biterrors at the MAClayer crosses thethreshold.

Major

MAC_FCS_EXC The software detectsthat the number of biterrors at the MAClayer crosses thethreshold.

Major

MOD_COM_FAIL Modulecommunicationfailure

Major

MOD_TYPE_MISMATCH Port module typemismatch

Critical

MPLS_PW_BDI PW backward defectindication

Minor

MPLS_PW_Excess Excessive trailtermination sourceidentifiers (TTSIs)are received on thePW.

Minor

MPLS_PW_LOCV Loss of PWconnectivity

Critical

MPLS_PW_MISMATCH The trail terminationsource identifiers(TTSIs) on the PW donot match with thespecified one.

Critical



193


MPLS_PW_MISMERGE The trail terminationsource identifiers(TTSIs) aremismerged on thePW.

Major

MPLS_PW_SD Signal degradationon the PW

Major

MPLS_PW_SF Signal failure on thePW

Major

MPLS_PW_UNKNOWN Unknown defects onthe PW

Major

MPLS_TUNNEL_BDI Tunnel backwarddefect indication

Minor

MPLS_TUNNEL_Excess Excessive trailtermination sourceidentifiers (TTSIs)are received on thetunnel.

Minor

MPLS_TUNNEL_FDI Tunnel forwarddefect indication

Major

MPLS_TUNNEL_LOCV Loss of tunnelconnectivity

Critical

MPLS_TUNNEL_MISMATCH The trail terminationsource identifiers(TTSIs) on the tunneldo not match with thespecified one.

Critical

MPLS_TUNNEL_MISMERGE The trail terminationsource identifiers(TTSIs) aremismerged on thetunnel.

Major

MPLS_TUNNEL_OAMFAIL The OAM protocolnegotiation betweenthe two ends of thetunnel fails.

Minor

MPLS_TUNNEL_SD Signal degradationon the tunnel

Major

MPLS_TUNNEL_SF Signal failure on thetunnel

Major



194


MPLS_TUNNEL_UNKNOWN Unknown defects onthe tunnel

Major

MS_AIS Multiplex sectionalarm indication

Major

MS_CROSSTR Multiplex sectionperformancethreshold-crossing

Minor

MS_RDI Multiplex sectionremote defectindication

Minor

MS_REI Multiplex sectionremote errorindication

Warning

MSAD_CROSSTR Multiplex sectionadaptationperformancethreshold-crossing

Minor

MULTI_RPL_OWNER The ring network hasmultipleRPL_OWNERnodes.

Minor

MW_AM_TEST The IF port is in theAM testing state.

Minor

MW_BER_EXC Excessive errors onradio links

Minor

MW_BER_SD Signal degradationdue to excessiveerrors on radio links

Minor

MW_CFG_MISMATCH Configurationmismatch on radiolinks

Critical

MW_CONT_WAVE Continuous wave Minor

MW_E1_LOST Loss of E1 signals Major

MW_FEC_UNCOR Microwave frameshave the errors thatcannot be correctedby using the forwarderror correction(FEC) technology.

Minor

MW_LIM Label mismatch onradio links

Major



195


MW_LOF Loss of microwaveframes

Critical

MW_RDI Remote defectindication on radiolinks

Minor

NESF_LOST The NE software islost.

Critical

NESOFT_MM The software in themain area is differentfrom that in thestandby area.

Major

NESTATE_INSTALL The NE is in theinstallation state.

Critical

NO_BD_SOFT The board software islost.

Critical

NP1_MANUAL_STOP The N+1 protectionprotocol is stoppedmanually.

Minor

NP1_SW_FAIL The N+1 protectionswitching fails.

Major

NP1_SW_INDI N+1 protectionswitching indication

Major

NTP_SYNC_FAIL Synchronization withthe NTP time fails.

Minor

OCD Out of celldelimitation

Major

ODC_BATTERY_CURRENT_ABN Abnormal current ofthe storage battery

Major

ODC_BATTERY_PWRDOWN The storage batteryfails to supply powerfor the equipment.

Major

ODC_DOOR_OPEN The door of anoutdoor cabinet isopen.

Critical

ODC_FAN_FAILED Fan failure Major

ODC_HUMI_ABN The relative humidityin the cabinetenvironment crossesthe specifiedthreshold.

Minor



196


ODC_LOAD_PWRDOWN The secondary load ispowered off.

Major

ODC_MDL_ABN The power module isabnormal.

Major

ODC_POWER_FAIL Exceptions occur inthe AC input powervoltage.

Major

ODC_SMOKE_OVER Smoke occurs in anoutdoor cabinet.

Critical

ODC_SURGE_PROTECTION_FAIL The surge protectionfunction of theoutdoor cabinet fails.

Critical

ODC_TEC_ALM The TEC airconditioning modulein the cabinet fails.

Major

ODC_TEMP_ABN The ambienttemperature of thecabinet or thetemperature of thestorage battery isinappropriate.

Minor

ODC_WATER_ALM Water in the outdoorcabinet

Critical

OUT_PWR_ABN Abnormal outputoptical power

Critical

OUT1TEMP_SENSOR_FAIL The air outlettemperature sensor ofthe cabinet fails.

Major

OUT2TEMP_SENSOR_FAIL The externalrecycling outlettemperature sensor ofthe cabinet fails.

Major

PATCH_ACT_TIMEOUT Activating patchpackages times out.

Minor

PATCH_DEACT_TIMEOUT Deactivating patchpackages times out.

Minor

PATCH_PKGERR Abnormal patchpackage

Minor

PG_LINK_FAIL Links of the 1+1protection group fail.

Critical



197


PG_PRT_DEGRADED The working link orprotection link of the1+1 protection groupis faulty.

Major

PLA_CFG_MISMATCH Inconsistent PLAconfigurations

Critical

PORT_EXC_TRAFFIC The traffic is higherthan the portbandwidth threshold.

Warning

PORT_MODULE_OFFLINE Port not in position Major

PORTMODE_MISMATCH The working mode ofthe remote FE portdoes not match that ofthe local FE port.

Minor

POWER_ABNORMAL Power input alarm Major

POWER_ALM Power module alarm Major

PW_DROPPKT_EXC The number of lostpackets in a PWcrosses the threshold.

Warning

PWAPS_LOST Loss of APS frames Minor

PWAPS_PATH_MISMATCH The working andprotection paths ofthe APS protectiongroup differ betweenthe two ends.

Major

PWAPS_SWITCH_FAIL Protection switchingfailure

Major

PWAPS_TYPE_MISMATCH Protection schememismatch

Major

R_F_RST Reset of the receiveFIFO

Minor

R_LOC Loss of clock on thereceive line side

Critical

R_LOF Loss of frame on thereceive line side

Critical

R_LOS Loss of signal or lossof microwave frameon the receive lineside

Critical



198


R_S_ERR Errors in the receivedsignal

Critical

RADIO_FADING_MARGIN_INSUFF Radio fading marginis insufficient.

Minor

RADIO_MUTE The radio transmitteris muted.

Warning

RADIO_RSL_BEYONDTH Antennas are notaligned.

Minor

RADIO_RSL_HIGH Over high radioreceive signal level

Critical

RADIO_RSL_LOW Over low radioreceive signal level

Critical

RADIO_TSL_HIGH Over high radiotransmit signal level

Critical

RADIO_TSL_LOW Over low radiotransmit signal level

Critical

RELAY_ALARM_CRITICAL There are criticalalarm inputs.

Critical

RELAY_ALARM_IGNORE There are warninginputs.

Warning

RELAY_ALARM_MAJOR There are majoralarm inputs.

Major

RELAY_ALARM_MINOR There are minoralarm inputs.

Minor

RMFA Loss of multiframealignment at theremote end

Minor

RPS_INDI Radio protectionswitching indication

Major

RS_CROSSTR Regenerator sectionperformancethreshold-crossing

Minor

RTC_FAIL The real-time clock(RTC) of the systemcontrol board fails.

Major

S1_SYN_CHANGE Clock sourceswitching in S1 mode

Major

SEC_RADIUS_FAIL RADIUSauthentication fails.

Major



199


SECU_ALM Security alarm Major

SRV_SHUTDOWN_LD Ethernet services areinterrupted.

Warning

SWDL_ACTIVATED_TIMEOUT The commitoperation is notperformed duringsoftware packageloading.

Critical

SWDL_AUTOMATCH_INH The automatic matchfunction is disabled.

Minor

SWDL_CHGMNG_NOMATCH The board softwareversion and theversion of therunning software areinconsistent.

Critical

SWDL_COMMIT_FAIL The submit operationfails.

Minor

SWDL_INPROCESS The packagediffusion is beingperformed on the NE.

Warning

SWDL_NEPKGCHECK Certain files in thepackage stored inflash memory arelost.

Critical

SWDL_PKG_NOBDSOFT The softwarepackage does notcontain any boardsoftware.

Minor

SWDL_PKGVER_MM Software packageversion consistencycheck fails.

Minor

SWDL_ROLLBACK_FAIL The version rollbackon an NE fails.

Minor

SYN_BAD Synchronous sourcedegradation

Minor

SYNC_C_LOS Loss ofsynchronizationclock sources

Warning

T_ALOS Loss of analogsignals at 2 Mbit/sinterfaces

Major



200


T_F_RST Reset of the transmitFIFO

Minor

T_LOC Loss of clock on thetransmit line side

Major

TEMP_ALARM Excessive boardtemperature

Minor

THUNDERALM Surge protectionfails.

Minor

TR_LOC Clock failure Major

TU_AIS TU alarm indication Major

TU_AIS_VC12 VC-12 path TU alarmindication

Major

TU_AIS_VC3 TU of VC-3 levelalarm indication

Major

TU_LOP Loss of TU pointers Major

TU_LOP_VC12 Loss of TU pointersin VC-12 paths

Major

TU_LOP_VC3 TU of VC-3 level lossof pointer

Major

TUNNEL_APS_DEGRADED The tunnel protectiongroup degrades.

Major

UP_E1_AIS Alarm indication of 2Mbit/s upstreamsignals

Minor

UHCS Uncorrectable cellerrors

Minor

VC_AIS Alarm indicationsignal of the VCconnection

Critical

VC_LOC Loss of VCconnectivity check

Major

VC_RDI Remote defectindication of the VCconnection

Major

VCAT_LOA Excessive virtualconcatenation delay

Critical



201


VCAT_LOM_VC12 Loss of multiframe ofVC-12 path virtualconcatenation

Major

VCAT_LOM_VC3 The virtuallyconcatenatedmultiframes in aVC-3 path are lost.

Major

VCAT_SQM_VC12 SQ mismatch ofVC-12 path virtualconcatenation

Major

VCAT_SQM_VC3 SQ mismatch ofVC-3 path virtualconcatenation

Major

VOLT_LOS Loss of voltage Major

VP_AIS Alarm indicationsignal of the VPconnection

Critical

VP_LOC Loss of VPconnectivity check

Major

VP_RDI Remote defectindication of the VPconnection

Major

W_R_FAIL Failure in reading andwriting chip registers

Major

WRG_BD_TYPE Errored board types Major

XPIC_LOS Loss of XPICcompensation signals

Critical

A.2 Alarm List (Classified by Logical Boards)This part lists the alarms that are reported by each board.

NOTE

The NE software consider a physical board as one or more logical boards when managing the physical board.The NMS also considers a physical board as one or more logical boards when managing the physical board.

For OptiX RTN 910, all physical boards, except the system control, switching, and timing board, correspond tological boards of the same names. Table A-2 shows the logical boards corresponding to the system control,switching, and timing board.



202

Table A-2 Logical boards corresponding to the system control, switching, and timing board

Physical Board Logical Board

CSTA CSTA in slot 1 + SL1D in slot 8 + SP3S inslot 9 + AUX in slot 10

CSHA CSHA in slot 1 + EM4T in slot 7 + SP3S inslot 9 + AUX in slot 10

CSHB CSHB in slot 1 + EM4T in slot 7 + SP3D inslot 9 + AUX in slot 10

CSHC CSHC in slot 1 + EM4F in slot 7 + SL1D inslot 8 + SP3S in slot 9 + AUX in slot 10

CSHD CSHD in slot 1 + EM6X in slot 7 + MP1 inslot 9 + AUX in slot 10

CSHE CSHE in slot 1 + EM6TB in slot 7 + MP1 inslot 9 + AUX in slot 10

A.2.1 CSTAAPS_FAIL APS_INDI APS_MANUAL_ST

OPBD_NOT_INSTALLED

BD_STATUS BOOTROM_BAD CFCARD_FAILED CFCARD_OFFLINE

CLK_NO_TRACE_MODE

DBMS_ABNORMAL

DBMS_ERROR DBMS_PROTECT_MODE

DCNSIZE_OVER EXT_SYNC_LOS HARD_BAD K1_K2_M

K2_M LAN_LOC LCS_LIMITED LICENSE_LOST

LPS_UNI_BI_M LTI NESF_LOST NESOFT_MM

NESTATE_INSTALL

NP1_MANUAL_STOP

NP1_SW_FAIL NP1_SW_INDI

NTP_SYNC_FAIL PATCH_ACT_TIMEOUT

PATCH_DEACT_TIMEOUT

PATCH_PKGERR

PG_LINK_FAIL PG_PRT_DEGRADED

PLA_CFG_MISMATCH

POWER_ALM

RPS_INDI RTC_FAIL S1_SYN_CHANGE SEC_RADIUS_FAIL

SECU_ALM SWDL_ACTIVATED_TIMEOUT

SWDL_AUTOMATCH_INH

SWDL_CHGMNG_NOMATCH



203

SWDL_COMMIT_FAIL

SWDL_INPROCESS

SWDL_NEPKGCHECK

SWDL_PKG_NOBDSOFT

SWDL_PKGVER_MM

SWDL_ROLLBACK_FAIL

SYN_BAD SYNC_C_LOS

TEMP_ALARM WRG_BD_TYPE - -

A.2.2 CSHA/CSHB/CSHC/CSHD/CSHEAPS_FAIL APS_INDI APS_MANUAL_ST

OPBD_NOT_INSTALLED

BD_STATUS BOOTROM_BAD CFCARD_FAILED CFCARD_OFFLINE

CLK_NO_TRACE_MODE

DBMS_ABNORMAL

DBMS_ERROR DBMS_PROTECT_MODE

DCNSIZE_OVER ETH_APS_LOST ETH_APS_PATH_MISMATCH

ETH_APS_SWITCH_FAIL

ETH_APS_TYPE_MISMATCH

EXT_SYNC_LOS EXT_TIME_LOC FLOW_OVER

HARD_BAD K1_K2_M K2_M LAG_BWMM

LAN_LOC LCS_LIMITED LICENSE_LOST LPS_UNI_BI_M

LPT_CFG_CLOSE-PORT

LTI MPLS_PW_BDI MPLS_PW_Excess

MPLS_PW_LOCV MPLS_PW_MISMATCH

MPLS_PW_MISMERGE

MPLS_PW_SD

MPLS_PW_SF MPLS_PW_UNKNOWN

MPLS_TUNNEL_BDI

MPLS_TUNNEL_Excess

MPLS_TUNNEL_FDI

MPLS_TUNNEL_LOCV

MPLS_TUNNEL_MISMATCH

MPLS_TUNNEL_MISMERGE

MPLS_TUNNEL_OAMFAIL

MPLS_TUNNEL_SD

MPLS_TUNNEL_SF

MPLS_TUNNEL_UNKNOWN

NESF_LOST NESOFT_MM NESTATE_INSTALL

NP1_MANUAL_STOP

NP1_SW_FAIL NP1_SW_INDI NTP_SYNC_FAIL PATCH_ACT_TIMEOUT

PATCH_DEACT_TIMEOUT

PATCH_PKGERR PG_LINK_FAIL PG_PRT_DEGRADED

PLA_CFG_MISMATCH

POWER_ALM PW_DROPPKT_EXC

PWAPS_LOST



204

PWAPS_PATH_MISMATCH

PWAPS_SWITCH_FAIL

PWAPS_TYPE_MISMATCH

RPS_INDI

RTC_FAIL S1_SYN_CHANGE SEC_RADIUS_FAIL

SECU_ALM

SRV_SHUTDOWN_LD

SWDL_ACTIVATED_TIMEOUT

SWDL_AUTOMATCH_INH

SWDL_CHGMNG_NOMATCH

SWDL_COMMIT_FAIL

SWDL_INPROCESS

SWDL_NEPKGCHECK

SWDL_PKG_NOBDSOFT

SWDL_PKGVER_MM

SWDL_ROLLBACK_FAIL

SYN_BAD SYNC_C_LOS

TEMP_ALARM TUNNEL_APS_DEGRADED

WRG_BD_TYPE MOD_COM_FAIL(Only reported byCSHD\CSHE)

A.2.3 IF1AU_AIS AU_LOP B1_EXC B1_SD

B2_EXC B2_SD B3_EXC B3_SD

BD_STATUS HARD_BAD HP_CROSSTR HP_LOM

HP_RDI HP_REI HP_SLM HP_TIM

HP_UNEQ IF_CABLE_OPEN IF_MODE_UNSUPPORTED

LCS_LIMITED

LICENSE_DIFF LICENSE_LOST LOOP_ALM MS_AIS

MS_CROSSTR MS_RDI MS_REI MSAD_CROSSTR

MW_CONT_WAVE

MW_FEC_UNCOR MW_LIM MW_LOF

MW_RDI R_LOC R_LOF R_LOS

RS_CROSSTR T_LOC TEMP_ALARM VOLT_LOS

WRG_BD_TYPE - - -

A.2.4 IFU2AM_DOWNSHIFT BD_STATUS BIP_EXC BIP_SD

BUS_ERR DROPRATIO_OVER

ETH_CFM_LOC ETH_CFM_MISMERGE



205

ETH_CFM_RDI ETH_CFM_UNEXPERI

ETH_EFM_DF ETH_EFM_LOOPBACK

ETH_EFM_REMFAULT

ETHOAM_SELF_LOOP

FLOW_OVER HARD_BAD

IF_CABLE_OPEN LAG_BWMM LAG_DOWN LAG_MEMBER_DOWN

LCS_LIMITED LICENSE_DIFF LICENSE_LOST LOOP_ALM

LP_RDI LP_REI LP_UNEQ MAC_EXT_EXC

MAC_FCS_EXC MULTI_RPL_OWNER

MW_BER_EXC MW_BER_SD

MW_CFG_MISMATCH

MW_CONT_WAVE

MW_E1_LOST MW_FEC_UNCOR

MW_LIM MW_LOF MW_RDI PORT_EXC_TRAFFIC

R_LOC R_LOF TEMP_ALARM TU_AIS

TU_LOP VOLT_LOS WRG_BD_TYPE

A.2.5 IFX2AM_DOWNSHIFT BD_STATUS BIP_EXC BIP_SD





ETH_EFM_REMFAULT

ETHOAM_SELF_LOOP

FLOW_OVER HARD_BAD

IF_CABLE_OPEN LAG_BWMM LAG_DOWN LAG_MEMBER_DOWN

LCS_LIMITED LICENSE_DIFF LICENSE_LOST LOOP_ALM

LP_RDI LP_REI LP_UNEQ MAC_EXT_EXC

MAC_FCS_EXC MULTI_RPL_OWNER


MW_CFG_MISMATCH

MW_CONT_WAVE

MW_E1_LOST MW_FEC_UNCOR

MW_LIM MW_LOF MW_RDI PORT_EXC_TRAFFIC



206

R_LOC R_LOF TEMP_ALARM TU_AIS

TU_LOP VOLT_LOS WRG_BD_TYPE XPIC_LOS

A.2.6 SL1D/SL1DAAU_AIS AU_LOP B1_EXC B1_SD

B2_EXC B2_SD B3_EXC B3_SD

BD_STATUS HARD_BAD HP_CROSSTR HP_LOM

HP_RDI HP_REI HP_SLM HP_TIM

HP_UNEQ IN_PWR_HIGH IN_PWR_LOW J0_MM

LASER_CLOSED LASER_MOD_ERR_EX

LOOP_ALM LSR_NO_FITED

MS_AIS MS_CROSSTR MS_RDI MS_REI

MSAD_CROSSTR R_LOC R_LOF R_LOS

RS_CROSSTR T_LOC WRG_BD_TYPE -

A.2.7 EM6TBD_STATUS BUS_ERR COMMUN_FAIL DROPRATIO_OVE

R



ETH_EFM_DF ETH_EFM_EVENT ETH_EFM_LOOPBACK

ETH_EFM_REMFAULT

ETH_LOS ETH_NO_FLOW ETHOAM_SELF_LOOP

FLOW_OVER

HARD_BAD LAG_DOWN LAG_MEMBER_DOWN

LOOP_ALM

LPT_CFG_CLOSE-PORT

MAC_EXT_EXC MAC_FCS_EXC MULTI_RPL_OWNER

PORT_EXC_TRAFFIC

PORTMODE_MIS-MATCH

TEMP_ALARM WRG_BD_TYPE



207

A.2.8 EM6TA

BD_STATUS BUS_ERR COMMUN_FAIL DROPRATIO_OVER




ETH_EFM_REMFAULT


FLOW_OVER

HARD_BAD LAG_DOWN LAG_MEMBER_DOWN

LOOP_ALM

LPT_CFG_CLOSE-PORT


PORT_EXC_TRAFFIC

PORTMODE_MIS-MATCH


A.2.9 EM6TB





ETH_EFM_REMFAULT


FLOW_OVER

LAG_DOWN LAG_MEMBER_DOWN

LOOP_ALM LPT_CFG_CLOSE-PORT


PORT_EXC_TRAFFIC

PORTMODE_MIS-MATCH

WRG_BD_TYPE - -

A.2.10 EM6F




208




ETH_EFM_REMFAULT


FLOW_OVER

HARD_BAD IN_PWR_ABN LAG_DOWN LAG_MEMBER_DOWN

LASER_MOD_ERR

LASER_SHUT LOOP_ALM LPT_CFG_CLOSE-PORT

LSR_NO_FITED MAC_EXT_EXC MAC_FCS_EXC MULTI_RPL_OWNER

PORT_EXC_TRAFFIC

PORTMODE_MIS-MATCH


A.2.11 EM6FABD_STATUS BUS_ERR COMMUN_FAIL DROPRATIO_OVE

R




ETH_EFM_REMFAULT


FLOW_OVER

HARD_BAD IN_PWR_ABN LAG_DOWN LAG_MEMBER_DOWN

LASER_MOD_ERR


LSR_NO_FITED MAC_EXT_EXC MAC_FCS_EXC MULTI_RPL_OWNER

PORT_EXC_TRAFFIC

PORTMODE_MIS-MATCH


A.2.12 EM4TBD_STATUS COMMUN_FAIL DROPRATIO_OVE

RETH_CFM_LOC



209

ETH_CFM_MISMERGE


ETH_EFM_DF

ETH_EFM_EVENT ETH_EFM_LOOPBACK

ETH_EFM_REMFAULT

ETH_LOS

ETH_NO_FLOW ETHOAM_SELF_LOOP

FLOW_OVER HARD_BAD

LAG_DOWN LAG_MEMBER_DOWN

LOOP_ALM LPT_CFG_CLOSE-PORT


PORT_EXC_TRAFFIC

PORTMODE_MIS-MATCH

WRG_BD_TYPE - -

A.2.13 EM4FBD_STATUS COMMUN_FAIL DROPRATIO_OVE

RETH_CFM_LOC

ETH_CFM_MISMERGE


ETH_EFM_DF

ETH_EFM_EVENT ETH_EFM_LOOPBACK

ETH_EFM_REMFAULT

ETH_LOS

ETH_NO_FLOW ETHOAM_SELF_LOOP

FLOW_OVER HARD_BAD

IN_PWR_ABN LAG_DOWN LAG_MEMBER_DOWN

LASER_MOD_ERR


LSR_NO_FITED


PORT_EXC_TRAFFIC

PORTMODE_MIS-MATCH

WRG_BD_TYPE - -

A.2.14 EFP8ALM_GFP_dCSF ALM_GFP_dLFD BD_STATUS BIP_EXC

BIP_SD COMMUN_FAIL DOWN_E1_AIS ETH_CFM_LOC



210

ETH_CFM_MISMERGE


ETH_LOS

ETHOAM_DISCOVER_FAIL

ETHOAM_RMT_CRIT_FAULT

ETHOAM_RMT_LOOP

ETHOAM_RMT_SD

ETHOAM_SELF_LOOP

ETHOAM_VCG_SELF_LOOP

EX_ETHOAM_CC_LOS

EX_ETHOAM_MPID_CNFLCT

FCS_ERR FLOW_OVER HARD_BAD LAG_PORT_FAIL

LAG_VC_PORT_FAIL

LCAS_FOPR LCAS_FOPT LCAS_PLCR

LCAS_PLCT LCAS_TLCR LCAS_TLCT LFA

LMFA LOOP_ALM LP_RDI_VC12 LP_REI_VC12

LP_SLM_VC12 LP_TIM_VC12 LP_UNEQ_VC12 LPT_RFI

NO_BD_SOFT RMFA TEMP_ALARM TU_AIS_VC12

TU_LOP_VC12 VCAT_LOA VCAT_LOM_VC12 VCAT_SQM_VC12

W_R_FAIL WRG_BD_TYPE - -

A.2.15 EMS6ALM_GFP_dCSF ALM_GFP_dLFD B3_EXC_VC3 B3_SD_VC3

BD_STATUS BIP_EXC BIP_SD BUS_ERR

COMMUN_FAIL ETH_CFM_LOC ETH_CFM_MISMERGE

ETH_CFM_RDI

ETH_CFM_UNEXPERI

ETH_LOS ETHOAM_DISCOVER_FAIL

ETHOAM_RMT_CRIT_FAULT

ETHOAM_RMT_LOOP

ETHOAM_RMT_SD

ETHOAM_SELF_LOOP

EX_ETHOAM_CC_LOS

EX_ETHOAM_MPID_CNFLCT

FCS_ERR FLOW_OVER HARD_BAD

IN_PWR_ABN LAG_PORT_FAIL LAG_VC_PORT_FAIL

LCAS_FOPR

LCAS_FOPT LCAS_PLCR LCAS_PLCT LCAS_TLCR

LCAS_TLCT LINK_ERR LOOP_ALM LP_RDI_VC12

LP_RDI_VC3 LP_REI_VC12 LP_REI_VC3 LP_SLM_VC12

LP_SLM_VC3 LP_TIM_VC12 LP_TIM_VC3 LP_UNEQ_VC12



211

LP_UNEQ_VC3 LPT_INEFFECT LPT_RFI MOD_TYPE_MIS-MATCH

MULTI_RPL_OWNER

NO_BD_SOFT OUT_PWR_ABN PORT_MODULE_OFFLINE

TEMP_ALARM TU_AIS_VC12 TU_AIS_VC3 TU_LOP_VC12

TU_LOP_VC3 VCAT_LOA VCAT_LOM_VC12 VCAT_LOM_VC3

VCAT_SQM_VC12 VCAT_SQM_VC3 WRG_BD_TYPE -

A.2.16 SP3S/SP3DA_LOC BD_STATUS BIP_EXC BIP_SD

DOWN_E1_AIS E1_LOC E1_LOS HARD_BAD

HPAD_CROSSTR LOOP_ALM LP_CROSSTR LP_R_FIFO

LP_RDI LP_REI LP_RFI LP_SLM

LP_T_FIFO LP_TIM LP_UNEQ R_F_RST

R_S_ERR WRG_BD_TYPE T_ALOS T_F_RST

TU_AIS TU_LOP UP_E1_AIS DDN_LFA

A.2.17 AUXBD_STATUS HARD_BAD RELAY_ALARM_

CRITICALRELAY_ALARM_IGNORE

RELAY_ALARM_MAJOR

RELAY_ALARM_MINOR

WRG_BD_TYPE -

A.2.18 PIUBD_STATUS HARD_BAD POWER_ABNORM

ALTHUNDERALM

WRG_BD_TYPE - - -



212

A.2.19 FANBD_STATUS FAN_AGING FAN_FAIL POWER_ALM

WRG_BD_TYPE - - -

A.2.20 ISU2AM_DOWNSHIFT AU_AIS AU_LOP B1_EXC

B1_SD B2_EXC B2_SD B3_EXC

B3_SD BD_STATUS BIP_EXC BIP_SD





ETH_EFM_REMFAULT

ETHOAM_SELF_LOOP

FLOW_OVER HARD_BAD

HP_CROSSTR HP_LOM HP_RDI HP_REI

HP_SLM HP_TIM HP_UNEQ IF_CABLE_OPEN

LAG_BWMM LAG_DOWN LAG_MEMBER_DOWN

LCS_LIMITED

LICENSE_DIFF LICENSE_LOST LOOP_ALM LP_RDI

LP_REI LP_UNEQ MAC_EXT_EXC MAC_FCS_EXC


MSAD_CROSSTR MULTI_RPL_OWNER

MW_AM_TEST MW_BER_EXC

MW_BER_SD MW_CFG_MISMATCH

MW_CONT_WAVE

MW_E1_LOST

MW_FEC_UNCOR MW_LIM MW_LOF MW_RDI

PORT_EXC_TRAFFIC

R_LOC R_LOF RS_CROSSTR

T_LOC TEMP_ALARM TU_AIS TU_LOP

VOLT_LOS WRG_BD_TYPE - -



213

A.2.21 ISX2

AM_DOWNSHIFT AU_AIS AU_LOP B1_EXC

B1_SD B2_EXC B2_SD B3_EXC

B3_SD BD_STATUS BIP_EXC BIP_SD





ETH_EFM_REMFAULT

ETHOAM_SELF_LOOP

FLOW_OVER HARD_BAD

HP_CROSSTR HP_LOM HP_RDI HP_REI

HP_SLM HP_TIM HP_UNEQ IF_CABLE_OPEN

LAG_BWMM LAG_DOWN LAG_MEMBER_DOWN

LCS_LIMITED

LICENSE_DIFF LICENSE_LOST LOOP_ALM LP_RDI

LP_REI LP_UNEQ MAC_EXT_EXC MAC_FCS_EXC


MSAD_CROSSTR MULTI_RPL_OWNER

MW_AM_TEST MW_BER_EXC

MW_BER_SD MW_CFG_MISMATCH

MW_CONT_WAVE

MW_E1_LOST

MW_FEC_UNCOR MW_LIM MW_LOF MW_RDI

PORT_EXC_TRAFFIC

R_LOC R_LOF RS_CROSSTR

T_LOC TEMP_ALARM TU_AIS TU_LOP

VOLT_LOS WRG_BD_TYPE XPIC_LOS -

A.2.22 ML1/MD1

ALM_E1RAI ALM_IMA_LIF ALM_IMA_LODS ALM_IMA_RE_RX_UNUSABLE

ALM_IMA_RE_TX_UNUSABLE

ALM_IMA_RFI ATMPW_UNKNOWNCELL_EXC

BD_STATUS

CES_ACR_LOCK_ABN

CES_JTROVR_EXC

CES_JTRUDR_EXC

CES_LOSPKT_EXC



214

CES_MALPKT_EXC

CES_MISORDERPKT_EXC

CES_RDI CES_STRAYPKT_EXC

CESPW_OPPOSITE_ACFAULT

CESPW_OPPOSITE_RAI

CHCS WRG_BD_TYPE

HARD_BAD IMA_GROUP_LE_DOWN

IMA_GROUP_RE_DOWN

IMA_TXCLK_MIS-MATCH

LCD LFA LMFA LOOP_ALM

OCD POWER_ABNORMAL

T_ALOS TEMP_ALARM

TR_LOC UHCS UP_E1_AIS VC_AIS

VC_LOC VC_RDI VP_AIS VP_LOC

VP_RDI BUS_ERR - -

A.2.23 MP1A_LOC ALM_E1RAI ALM_IMA_LIF ALM_IMA_LODS

ALM_IMA_RE_RX_UNUSABLE

ALM_IMA_RE_TX_UNUSABLE

ALM_IMA_RFI ATMPW_UNKNOWNCELL_EXC

BD_STATUS BIP_EXC BIP_SD CES_ACR_LOCK_ABN

CES_JTROVR_EXC

CES_JTRUDR_EXC

CES_LOSPKT_EXC

CES_MALPKT_EXC

CES_MISORDERPKT_EXC

CES_RDI CES_STRAYPKT_EXC

CESPW_OPPOSITE_ACFAULT

CESPW_OPPOSITE_RAI

CHCS DOWN_E1_AIS E1_LOC

E1_LOS HARD_BAD HPAD_CROSSTR IMA_GROUP_LE_DOWN

IMA_GROUP_RE_DOWN

IMA_TXCLK_MIS-MATCH

LCD LFA

LMFA LOOP_ALM LP_CROSSTR LP_R_FIFO

LP_RDI LP_REI LP_RFI LP_SLM

LP_T_FIFO LP_TIM LP_UNEQ OCD

POWER_ABNORMAL

R_F_RST R_S_ERR T_ALOS

T_F_RST TR_LOC TU_AIS TU_LOP



215

UHCS UP_E1_AIS VC_AIS VC_LOC

VC_RDI VP_AIS VP_LOC VP_RDI

WRG_BD_TYPE - - -

A.2.24 EM6XBD_STATUS BUS_ERR COMMUN_FAIL DROPRATIO_OVE

R




ETH_EFM_REMFAULT


FLOW_OVER

IN_PWR_ABN LAG_DOWN LAG_MEMBER_DOWN

LASER_MOD_ERR


LSR_NO_FITED


PORT_EXC_TRAFFIC

PORTMODE_MIS-MATCH

WRG_BD_TYPE - -

A.2.25 ODUBD_STATUS CONFIG_NOSUPP

ORTHARD_BAD IF_INPWR_ABN

LOOP_ALM POWER_ALM RADIO_FADING_MARGIN_INSUFF

RADIO_MUTE

RADIO_RSL_BE-YONDTH

RADIO_RSL_HIGH

RADIO_RSL_LOW RADIO_TSL_HIGH

RADIO_TSL_LOW TEMP_ALARM WRG_BD_TYPE -



216

A.2.26 PMU

BAT1TEMP_SENSOR_FAIL

BAT2TEMP_SENSOR_FAIL

BD_STATUS ENVHUM_SENSOR_FAIL

ENVTEMP1_SENSOR_FAIL

ENVTEMP2_SENSOR_FAIL

HARD_BAD ODC_BATTERY_CURRENT_ABN

ODC_BATTERY_PWRDOWN

ODC_DOOR_OPEN

ODC_HUMI_ABN ODC_LOAD_PWRDOWN

ODC_MDL_ABN ODC_POWER_FAIL

ODC_SMOKE_OVER

ODC_SURGE_PROTECTION_FAIL

ODC_TEMP_ABN ODC_WATER_ALM

WRG_BD_TYPE -

A.2.27 TCU

BD_STATUS BDTEMP_SENSOR_FAIL

ENVTEMP_SENSOR_FAIL

HARD_BAD

INTEMP_SENSOR_FAIL

ODC_DOOR_OPEN

ODC_FAN_FAILED

ODC_SMOKE_OVER

ODC_SURGE_PROTECTION_FAIL

ODC_TEC_ALM ODC_TEMP_ABN ODC_WATER_ALM

OUT1TEMP_SENSOR_FAIL

OUT2TEMP_SENSOR_FAIL

WRG_BD_TYPE -

A.3 Alarms and Handling ProceduresThis chapter describes all the alarms on the OptiX RTN 910 in alphabetical order and how tohandle these alarms.

A.3.1 A_LOC

Description

The A_LOC is an alarm indicating that a clock signal is lost in the uplink bus.

Attribute

Alarm Severity Alarm Type

Major Equipment alarm



217

Parameters

None.

Impact on the System

When the A_LOC alarm occurs, the services carried by the board are interrupted.

Possible Causes

Cause 1: A certain board is faulty.

Procedure

Step 1 Cause 1: A certain board is faulty.

1. Replace the board where the alarmed tributary unit is located.

----End

Related Information

None.

A.3.2 ALM_E1RAI

Description

The ALM_E1RAI is an alarm indicating that the E1 link on the opposite NE reports alarms. Thisalarm is reported on the local NE when the T_ALOS, UP_E1_AIS, DOWN_E1_AIS, LFA, orLMFA alarm is reported on the opposite NE.

Attribute


Minor Communication alarm

Parameters

None.


When this alarm occurs, the services on the local NE in the downstream direction are interrupted.

Possible Causesl Cause 1: The E1 link on the opposite NE reports the T_ALOS, LFA, LMFA, UP_E1_AIS,

or DOWN_E1_AIS alarm.



218

Procedure

Step 1 Cause 1: The E1 link on the opposite NE reports the T_ALOS, LFA, LMFA, UP_E1_AIS, orDOWN_E1_AIS alarm.

Step 2 Handle these alarms first.

----End

Related InformationNone.

A.3.3 ALM_GFP_dCSF

DescriptionThe ALM_GFP_dCSF is an alarm indicating that the generic framing procedure (GFP) customersignal is lost. When the source end fails to receive the GFP customer signal, it sends themanagement frame to the sink end. The ALM_GFP_dCSF alarm is reported when the sink endreceives the management frame.

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 1 The value is always 0x01.

Parameter 2, Parameter 3 Indicate the ID of the alarmed VCTRUNK. For example, 0x00 0x01indicate that the alarm is reported in VCTRUNK 1.

Impact on the SystemWhen this alarm occurs, services are interrupted.

Possible Causesl Cause 1: Timeslot binding is different at the source and sink VCTRUNKs.l Cause 2: The radio link performance degrades.l Cause 3: The alarmed board is faulty.



219

Procedure

Step 1 Cause 1: Timeslot binding is different at the source and sink VCTRUNKs.1. Reconfigure the timeslot binding at the source and sink VCTRUNKs.

Step 2 Cause 2: The radio link performance degrades.1. Troubleshoot the radio link.

Step 3 Cause 3: The alarmed board is faulty.1. Replace the faulty board.

----End


A.3.4 ALM_GFP_dLFD

DescriptionThe 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


Name Meaning

Parameter 1 Indicates the ID of the logical port, and the value is always 0x01.



Possible Causesl Cause 1: Bit errors occur on certain links or certain links are faulty.



220

l Cause 2: When the LCAS is disabled, the source and the sink VCTRUNKs are configuredwith different timeslots or different numbers of paths.

Procedure

Step 1 Cause 1: Bit errors occur on certain links or certain links are faulty.

1. Check whether the links where the service travels have errors or become faulty.

If... Then...

The links are faulty Rectify the fault.

The links are normal Replace the alarmed board.

Step 2 Cause 2: When the LCAS is disabled, the source and the sink VCTRUNKs are configured withdifferent timeslots or different numbers of paths.

1. Correct the configuration data. For details, see Configuring VCTRUNKs on an EthernetBoard.

----End

Related Information

None.

A.3.5 ALM_IMA_LIF

Description

The ALM_IMA_LIF is an alarm indicating that the IMA link is out of frame in the receivedirection. This alarm occurs when the frame alignment is lost on the IMA link in the receivedirection.

Attribute



Parameters

When you view an alarm on the network management system, select the alarm. In the AlarmDetails field display the related parameters of the alarm. The alarm parameters are in thefollowing format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the followingtable.

Name Meaning

Parameter 1, Parameter 2 Indicate the ATM Trunk ID.



221

Impact on the Systeml When this alarm occurs, the alarmed IMA link is unavailable. Therefore, the number of

available links in the IMA group decreases. If the bandwidth of the services configured forthe IMA group exceeds the total bandwidth of available IMA links, congestion occurs onthe IMA port, causing loss of cells.

l After this alarm is cleared, the affected IMA link becomes available.

Possible Causesl Cause 1: The path that carries the IMA link reports the SDH alarms, such as R_LOS,

R_LOF, and MS_AIS.

l Cause 2: The IMA protocol negotiation fails between the two ends.

l Cause 3: The IMA link is faulty.

Procedure

Step 1 Cause 1: The path that carries the IMA link reports the SDH alarms, such as R_LOS,R_LOF, and MS_AIS.

If... Then...

The path reports any SDH alarm Handle the relevant alarms first.

The path does not report any SDH alarm Go to Cause 2.

Step 2 Cause 2: The IMA protocol negotiation fails between the two ends.

1. Disable the IMA protocol at the two ends.

2. Check the IMA group configuration at the two ends and ensure that the configuration isconsistent.

3. Enable the IMA protocol at the two ends.

4. Then, check whether the alarm clears.

If... Then...

The alarm is cleared End the alarm handling.

The alarm persists Go to Cause 3.

Step 3 Cause 3: The IMA link is faulty.

1. Replace the board. For details, see 6.5 Replacing the Smart E1 Board.

----End

Related Information

Loss of frame alignment

A frame alignment word, provided at the physical layer, occupies the initial position of a frameand defines the start of information field. An Out Of Frame (OOF) defect is declared when theposition of frame alignment word cannot be determined in the input bit stream.



222

A.3.6 ALM_IMA_LODS

Description

The ALM_IMA_LODS is an alarm indicating the differential delay on the IMA link crosses thethreshold. This alarm occurs when the maximum differential delay on the IMA link exceeds thepreset value.

Attribute



Parameters


Name Meaning



The IMA links are unavailable.

Possible Causesl Cause 1: The maximum differential delay is configured incorrectly.

l Cause 2: Within one IMA group, the transmission distances of member links have too largegaps.

Procedure

Step 1 Cause 1: The maximum differential delay is configured incorrectly.

1. Change the maximum differential delay to a greater value. For details, see Modifying CESService Parameters.

Step 2 Cause 2: Within one IMA group, the transmission distances of member links have too largegaps.

1. Use the meter to measure the transmission time on E1 links. If the transmission time ondifferent links has a gap larger than 25 ms (default value), adjust the IMA links or deletethe member link with over long transmission time from the IMA group.

----End



223

Related Information

Differential delay

Differential delay refers to the service delay difference between E1 links.

A.3.7 ALM_IMA_RE_RX_UNUSABLE

Description

The ALM_IMA_RE_RX_UNUSABLE is an alarm indicating that the IMA link on the oppositeNE fails in the receive direction.

Attribute



Parameters


Name Meaning






R_LOF, and MS_AIS.l Cause 2: The IMA protocol negotiation fails between the two ends.l Cause 3: The IMA link is faulty.

Procedure




224

If... Then...



Step 2 Cause 2: The IMA protocol negotiation fails between the two ends.1. Disable the IMA protocol at the two ends.2. Check the IMA group configuration at the two ends and ensure that the configuration is

consistent.3. Enable the IMA protocol at the two ends.4. Then, check whether the alarm clears.

If... Then...



Step 3 Cause 3: The IMA link is faulty.1. Replace the board. For details, see 6.5 Replacing the Smart E1 Board.

----End


A.3.8 ALM_IMA_RE_TX_UNUSABLE

DescriptionThe ALM_IMA_RE_TX_UNUSABLE is an alarm indicating that the IMA link on the oppositeNE fails in the transmit direction.

Attribute




Name Meaning




225






Procedure


If... Then...



Step 2 Cause 2: The IMA protocol negotiation fails between the two ends.1. Disable the IMA protocol at the two ends.2. Check the IMA group configuration at the two ends and ensure that the configuration is

consistent.3. Enable the IMA protocol at the two ends.4. Then, check whether the alarm clears.

If... Then...



Step 3 Cause 3: The IMA link is faulty.1. Replace the board. For details, see 6.5 Replacing the Smart E1 Board.

----End




226

A.3.9 ALM_IMA_RFI

DescriptionThe ALM_IMA_RFI is an alarm indicating that the IMA link on the opposite NE is out of frame(OOF) in the receive direction. This alarm occurs when the frame alignment is lost on the IMAlink of the opposite NE and the opposite NE notifies the local NE of its OOF state.

Attribute




Name Meaning







Procedure


If... Then...





227

Step 2 Cause 2: The IMA protocol negotiation fails between the two ends.

1. Disable the IMA protocol at the two ends.

2. Check the IMA group configuration at the two ends and ensure that the configuration isconsistent.

3. Enable the IMA protocol at the two ends.


If... Then...



Step 3 Cause 3: The IMA link is faulty.

1. Replace the board. For details, see 6.5 Replacing the Smart E1 Board.

----End

Related Information

Frame alignment loss

A frame alignment word, provided at the physical layer, occupies the initial position of a frameand defines the start of information field. An Out Of Frame (OOF) defect is declared when theposition of frame alignment word cannot be determined in the input bit stream.

A.3.10 AM_DOWNSHIFT

Description

The AM_DOWNSHIFT is an alarm indicating the downshift of the AM scheme. This alarmoccurs when the AM scheme is downshifted from the highest-efficiency scheme to the lower-efficiency scheme. When the AM scheme is upshifted from the lower-efficiency scheme to thehighest-efficiency scheme, this alarm is cleared.

Attribute



Parameters

None.


When the AM_DOWNSHIFT alarm occurs, the transmission capacity is reduced.



228

Possible Causesl 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 scheme is normal. Hence, no measures should be takento handle the alarm.

Step 2 Cause 2: There are interferences around the working channels.1. Eliminate the interferences around the working channels.

Step 3 Cause 3: The ODU at the transmit end has abnormal transmit power.1. Use the NMS to check whether the transmit power of the ODU at the transmit end is normal.

For details on troubleshooting at the transmit end, see Troubleshooting MicrowaveLinks.

Step 4 Cause 4: The ODU at the receive end has abnormal receive power.1. Use the NMS to check whether the receive power of the ODU at the receive end is normal.

For details on troubleshooting at the receive end, see Troubleshooting MicrowaveLinks.

----End


A.3.11 APS_FAIL

DescriptionThe APS_FAIL is an alarm indicating that the MS protection switching fails.

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



229

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 type of the protection group.

l 0x01: linear MS protection

Parameter 2 Indicates the ID of the alarmed protection group. For example, 0x01 indicatesthat the alarm is reported by protection group 1.

Impact on the SystemWhen the APS_FAIL alarm occurs, the services cannot be switched. If the current paths areunavailable, the services are interrupted.

Possible Causesl Cause 1: The parameters of the MSP protocol are set incorrectly.l Cause 2: The parameters of the MSP protocol are lost.

ProcedureStep 1 Cause 1: The parameters of the MSP protocol are set incorrectly.

1. Check whether the parameters of the MSP protocol are set correctly.

If... Then...

The parameters are set incorrectly Set the parameters correctly.

The parameters are set correctly Go to the next step.

Step 2 Cause 2: The parameters of the MSP protocol are lost.1. Check whether the MSP protocol is normal on the network.2. Check whether the MSP protocol is normal on the network. For details, see Enabling/

Disabling the linear MSP protocol.

If... Then...

The alarm is cleared after the protocol isrestarted

End the alarm handling.

The alarm persists after the protocol isrestarted

Contact Huawei engineers to handle thealarm.

----End


A.3.12 APS_INDI



230

DescriptionThe APS_INDI is an alarm indicating that the MS protection switching occurs.

Attribute




Name Meaning


l 0x01: linear MS protection.


Impact on the SystemDuring the switching (≤ 50 ms), the service is interrupted. After the switching is complete, theservices are restored to normal. In the case of 1:N MS protection, after the switching starts andbefore the switching is complete, the extra services are interrupted.

Possible CausesCause 1: The MS protection switching occurs.

Procedure

Step 1 Cause 1: The MS protection switching occurs.1. Query the linear MSP group.2. Check whether the MSP protocol is in the manual switching state, forced switching state,

or locked switching state. If yes, release the switching and check whether the alarm iscleared.

3. Check whether the MSP protocol is in the automatic switching state. Do as follows:

a. Handle the R_LOS, R_LOF, MS_AIS, B2_EXC, or B2_SD alarm that the equipmentreports. After the alarms are cleared, wait until the MSP protocol is changed from theautomatic switching state to the normal state. Then, check whether the APS_INDIalarm is cleared.

b. Check whether the service board configured with the MSP protocol is faulty. If yes,replace the faulty board and then check whether the APS_INDI alarm is cleared.



231

c. Check the system control and cross-connect board is faulty. If yes, replace the systemcontrol and cross-connect board, and then check whether the APS_INDI alarm iscleared.

----End


A.3.13 APS_MANUAL_STOP

DescriptionThe APS_MANUAL_STOP is an alarm indicating that the MSP protocol is stopped manually.

Attribute


Minor Processing alarm


Name Meaning


l 0x01: linear MS protection.


Impact on the SystemWhen the APS_MANUAL_STOP alarm occurs, the MSP protocol may fail and therefore theprotection switching may fail.

Possible CausesCause 1: The MSP protocol is stopped manually.

Procedure

Step 1 Cause 1: The MSP protocol is stopped manually.



232

1. Enable/Disable the linear MSP protocol.

----End


A.3.14 ATMPW_UNKNOWNCELL_EXC

DescriptionThe ATMPW_UNKNOWNCELL_EXC is an alarm indicating that the number of unknowncells exceeds the specified threshold in a time unit. This alarm occurs when the board detectsthat, within a period (2.5s), the number of unknown cells crosses the specified threshold.

Attribute



ParametersNone.

Impact on the SystemAn unknown cell is discarded once it is detected. As a result, the packet loss rate increases andservices are affected.

Possible Causesl Cause 1: PW control words mismatch.l Cause 2: PW types mismatch.l Cause 3: Fragments are received on the network side.

Procedure

Step 1 Check whether the configuration at the two ends of the PW is consistent. If not, modify theconfiguration.

Step 2 Check whether connections are correct. If not, reconnect fibers or reconfigure connections.

----End


A.3.15 AU_AIS



233

Description

The AU_AIS is an alarm indicating the administrative unit (AU). This alarm occurs when theboard detects the AU pointer of all 1s for three consecutive frames.

Attribute



Parameters

None.


When the AU_AIS alarm occurs, the service in the alarmed AU-4 path is interrupted. If theservices are configured with protection, protection switching may be triggered.

Possible Causesl Cause 1: The opposite NE inserts the AU_AIS alarm.l Cause 2: The transmit unit of the opposite NE is faulty.l Cause 3: The receive unit of the local NE is faulty.

Procedure

Step 1 Cause 1: The opposite NE inserts the AU_AIS alarm.

If... Then...

The alarm that triggers the AU_AIS insertion occurs Clear the alarm immediately.

No such alarms that trigger the AU_AIS insertion occur Go to Cause 2.

Step 2 Cause 2: The transmit unit of the opposite NE is faulty.1. Replace the board where the line unit is located or the IF board.

If... Then...

The alarm is cleared after the board isreplaced

The fault is rectified. End the alarmhandling.

The alarm persists after the board isreplaced

Go to the next step.

2. Replace the system control board on the opposite NE.

Step 3 Cause 3: The receive unit of the local NE is faulty.1. Replace the alarmed board.

----End



234

Related Information

None.

A.3.16 AU_LOP

Description

The AU_LOP is an alarm indicating the loss of the AU pointer. This alarm occurs when a boarddetects the AU pointer of invalid values or with the NDF for eight consecutive frames.

Attribute



Parameters

None.


When the AU_LOP alarm occurs, the service in the alarmed AU-4 path is interrupted. If theservices are configured with protection, protection switching may be triggered.

Possible Causesl Cause 1: The transmit unit of the opposite NE is faulty.

l Cause 2: The receive unit of the local NE is faulty.

Procedure

Step 1 Cause 1: The transmit unit of the opposite NE is faulty.

1. Replace the board where the line unit is located on the opposite NE.

If... Then...





2. Replace the system control board on the opposite NE.

Step 2 Cause 2: The receive unit of the local NE is faulty.

1. Replace the alarmed board.

----End



235

Related Information

None.

A.3.17 B1_EXC

Description

The B1_EXC is an alarm indicating that the B1 errors (in the regenerator section) exceed thethreshold. This alarm occurs when the board detects that the B1 errors exceed the preset B1_EXCalarm threshold (10-3 by default).

An IF board that works in PDH mode may also report this alarm. This alarm is detected by usingthe self-defined overhead byte B1 in PDH microwave frames.

Attribute


Minor Service alarm

Parameters

None.


When the B1_EXC alarm occurs, the services on the port are interrupted.

Possible Causesl Cause 1: The line performance degrades (if the alarm is reported by an SDH optical interface

board).

l Cause 2: The line performance degrades (if the alarm is reported by an IF board).

l Cause 3: The network clock quality degrades.

l Cause 4: The board is faulty (if the alarm is reported by an SDH optical interface board).

l Cause 5: The board is faulty (if the alarm is reported by an IF board).

Procedure

Step 1 Cause 1: The line performance degrades (if the alarm is reported by an SDH optical interfaceboard).

1. Check whether the transmit power at the opposite end and the receive power at the localend meet the specifications of the optical interfaces. For details, see 8.3.5 BrowsingCurrent Performance Events.



236

If... Then...

The transmit power of the opposite NE isover low

Replace the board where the SDHoptical interface unit is located on theopposite NE.

The transmit power of the opposite NE isnormal, but the receive power of the localNE is close to the value (for example,within ±3 dB) of the receiver sensitivity.

The fiber is faulty. Go to the next step.

2. Exchange the core fibers of the optical cables in the receive and transmit directions of achannel.

If... Then...

The errors vary with the change of the fiber The fiber is faulty. Go to the next step.

The errors do not vary with the change of thefiber.

Ensure that the board is normal.

3. If the fiber is faulty, check whether the fiber jumper from the equipment to the opticaldistribution frame (ODF) and the fiber that is led out of the equipment room are pressed,and whether the fiber connector is dirty. If yes, replace the fiber jumper or fiber connector.

Step 2 Cause 2: The line performance degrades (if the alarm is reported by an IF board).1. Check whether the MW_BER_EXC, MW_BER_SD, MW_FEC_UNCOR or

RPS_INDI alarm is reported. If yes, clear the alarm.

Step 3 Cause 3: The network clock quality degrades.1. Check the network clock status of the alarmed NE.

If... Then...

The clock source of the local NE isdifferent from the clock source of theopposite NE

The clock may become asynchronous and B1errors may occur. Reconfigure the clocksource, and ensure that the clock issynchronized on the local NE and oppositeNE.

The clock of the local NE and the clockof the opposite NE form a timing loop

This may cause errors and even serviceinterruption. In this case, reconfigure the clocksource and release the timing loop.

Step 4 Cause 4: The board is faulty (if the alarm is reported by an SDH optical interface board).1. The board of the SDH line unit on the local NE is faulty. Loop back the optical interfaces

of the NE by using a fiber jumper to locate the fault.

If... Then...

The fault is not rectified after the opticalinterfaces are looped back

Replace the board where the alarmedline unit is located on the local NE.

The fault is rectified after the opticalinterfaces are looped back

Replace the board where the line unit islocated on the opposite NE.

Step 5 Cause 5: The board is faulty (if the alarm is reported by an IF board).



237

1. Perform an inloop for the multiplexing interface of the IF board on the local NE.

If... Then...

The fault is not rectified after themultiplexing interface is looped back

Replace the alarmed IF board on thelocal NE.

The fault is rectified after the multiplexinginterface is looped back

Replace the alarmed IF board on theopposite NE.

----End

Related InformationThe handling procedure applies when this alarm is reported by the STM-1e port.

Handle the errors of TDM services.

A.3.18 B1_SD

DescriptionThe B1_SD is an alarm indicating that the signal degrades due to the excessive B1 errors (in theregenerator section). This alarm occurs when the board detects that the B1 errors exceed thepreset B1_SD alarm threshold (10-6 by default) but do not reach the preset B1_EXC alarmthreshold (10-3 by default).

An IF board that works in PDH mode may also report this alarm. This alarm is detected by usingthe self-defined overhead byte B1 in PDH microwave frames.

Attribute


Minor Service alarm

ParametersNone.

Impact on the SystemWhen the B1_SD alarm occurs, the service performance on the port degrades.


board).l Cause 2: The line performance degrades (if the alarm is reported by an IF board).l Cause 3: The network clock quality degrades.l Cause 4: The board is faulty (if the alarm is reported by an SDH optical interface board).l Cause 5: The board is faulty (if the alarm is reported by an IF board).



238

Procedure



If... Then...



The transmit power of the opposite NE isnormal, but the receive power of the localNE is close to the value (for example,within ±3 dB) of the receiver sensitivity


2. Exchange the core fibers of the optical cables in the receive and transmit directions of achannel.

If... Then...


The errors do not vary with the change of thefiber



Step 2 Cause 2: The line performance degrades (if the alarm is reported by an IF board).

1. Check whether the MW_BER_EXC, MW_BER_SD, MW_FEC_UNCOR alarm isgenerated. If yes, clear the alarm.

Step 3 Cause 3: The network clock quality degrades.

1. Check the network clock status of the alarmed NE.

If... Then...


The clock may become asynchronous anderrors may occur. Reconfigure the clocksource, and ensure that the clock issynchronized on the local NE and oppositeNE.



Step 4 Cause 4: The board is faulty (if the alarm is reported by an SDH optical interface board).

1. The SDH optical line board of the local NE is faulty. Loop back the optical interfaces ofthe NE by using a fiber jumper to locate the fault.



239

If... Then...





Step 5 Cause 5: The board is faulty (if the alarm is reported by an IF board).1. Perform an inloop for the multiplexing interface of the IF board on the local NE.

If... Then...





----End

Related InformationThe handling procedure applies when this alarm is reported by the STM-1e port.


A.3.19 B2_EXC

DescriptionThe B2_EXC is an alarm indicating that the B2 errors (in the multiplex section) exceed thethreshold. This alarm occurs when the board detects that the number of B2 errors exceeds thepreset B2_EXC alarm threshold (10-3 by default).

Attribute


Major Service alarm

ParametersNone.

Impact on the SystemThe services on the port are interrupted.


board).



240





Procedure



If... Then...





2. Exchange the core fibers of the optical cables in the receive and transmit directions of achannel to locate the fault.

If... Then...






1. Check whether the MW_BER_EXC, MW_BER_SD, MW_FEC_UNCOR orRPS_INDI alarm is reported. If yes, clear the alarm.



If... Then...





241

If... Then...




1. The board of the SDH line unit on the local NE is faulty. Loop back the optical interfacesof the NE by using a fiber jumper to locate the fault.

If... Then...







If... Then...





----End

Related Information

The handling procedure applies when this alarm is reported by the STM-1e port.


A.3.20 B2_SD

Description

The B2_SD is an alarm indicating that the signal degrades due to the excessive B2 errors (in themultiplex section). This alarm occurs when the board detects that the number of B2 errors ishigher than the preset B2_SD alarm threshold (10-6 by default) and lower than the presetB2_EXC alarm threshold (10-3 by default).

Attribute


Minor Service alarm



242

ParametersNone.

Impact on the SystemThe service performance on the port degrades.



Procedure

Step 1 Cause 1: The line performance degrades (if the alarm is reported by an SDH optical interfaceboard).1. Check whether the transmit power at the opposite end and the receive power at the local

end meet the specifications of the optical interfaces. For details, see 8.3.5 BrowsingCurrent Performance Events.

If... Then...



The transmit power of the opposite NE isnormal, but the receive power of the localNE is close to the value (for example,within ± 3 dB) of the receiver sensitivity



If... Then...





Step 2 Cause 2: The line performance degrades (if the alarm is reported by an IF board).1. Check whether the MW_BER_EXC, MW_BER_SD, MW_FEC_UNCOR alarm is

generated. If yes, clear the alarm.




243


If... Then...






1. The SDH optical/electrical line board of the local NE is faulty. Loop back the opticalinterfaces of the station by using a fiber jumper to locate the fault.

If... Then...







If... Then...





----End

Related Information



A.3.21 B3_EXC

Description

The B3_EXC is an alarm indicating that the B3 errors (in the higher order path) exceed thethreshold. This alarm occurs when the board detects that the number of B3 errors exceeds thepreset B3_EXC alarm threshold (10-3 by default).



244

Attribute


Major Service alarm

Parameters

None.


When the B3_EXC alarm occurs, the service on the alarmed path is interrupted.


board).





Procedure



If... Then...






If... Then...






245



1. Check whether the MW_BER_EXC, MW_BER_SD, MW_FEC_UNCOR orRPS_INDI alarm is reported. If yes, clear the alarm.



If... Then...


In this case, the clock may becomeasynchronous and errors may occur.Reconfigure the clock source, and ensure thatthe clock is synchronized on the local NE andopposite NE.




1. The board of the SDH line unit on the local NE is faulty. Loop back the optical interfacesof the NE by using a fiber jumper to locate the fault.

If... Then...







If... Then...





----End

Related Information





246

A.3.22 B3_EXC_VC3

Description

The B3_EXC_VC3 alarm indicates that the number of B3 bit errors in a VC-3 path crosses thethreshold. A board reports this alarm when detecting that the number of B3 bit errors crossesthe B3_EXC_VC3 alarm threshold (10-3, by default).

Attribute


Major Service alarm

Parameters


Name Meaning

Parameter 1 Has a fixed value of 0x01.

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.


The services in the alarmed path have a large number of bit errors.

Possible Causesl Cause 1: Higher-level bit error alarms occur in the system.

l Cause 2: The line performance deteriorates (the alarm is reported by an Ethernet opticalport).

l Cause 3: The line performance deteriorates (the alarm is reported by an Ethernet electricalport).

l Cause 4: A board is faulty.

Procedure

Step 1 Cause 1: Higher-level bit error alarms occur in the system.

1. Check whether the local or upstream site detects B1_EXC, B1_SD, B2_EXC, B2_SD,B3_EXC, or B3_SD alarms. If yes, clear the higher-level alarms.

2. Check whether the alarm is cleared.



247

If... Then...


The alarm persists Go to Cause 2 or Cause 3.

Step 2 Cause 2: The line performance deteriorates (the alarm is reported by an Ethernet optical port).1. Check whether the transmit power at the opposite site and the receive power at the local

site meet the specifications of the optical ports. For details, see Browsing CurrentPerformance Events.

If... Then...

The transmit power at the opposite site istoo low

Replace the optical module at theopposite site.

The transmit power at the opposite site isnormal, but the receive power at the localsite is close to the receiver sensitivity (forexample, a difference within ±3 dB)

A fiber is faulty. Go to the next step.

2. Exchange the optical fibers in the receive and transmit directions of an optical path segment.

If... Then...

The number of bit errors changes Go to the next step.

The number of bit errors does not change Go to Cause 4.

3. If a fiber is 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, clean or replace the fiberconnector, or replace the fiber jumper. Check whether the alarm is cleared.

If... Then...



Step 3 Cause 3: The line performance deteriorates (the alarm is reported by an Ethernet electrical port).1. Check whether the cable grounding, cable connectors, and cables are damaged. If yes,

replace the faulty cables.2. Check whether the alarm is cleared.

If... Then...



Step 4 Cause 4: A board is faulty.1. Perform an inloop at the Ethernet port that connects to the alarmed VC-3 path.

If... Then...

The fault is not rectified after theEthernet port is looped back

Replace the alarmed Ethernet processingboard at the local site.



248

If... Then...

The fault is rectified after the Ethernetport is looped back

Replace the Ethernet processing board atthe opposite site.

----End


A.3.23 B3_SD

DescriptionThe B3_SD is an alarm indicating that the signal degrades due to the excessive B3 errors (in thehigher order path). This alarm occurs when the board detects that the number of B3 errors ishigher than the preset B3_SD alarm threshold (10-6 by default) and lower than the presetB3_EXC alarm threshold (10-3 by default).

Attribute


Minor Service alarm

ParametersNone.

Impact on the SystemThe service performance on the port degrades.



Procedure

Step 1 Cause 1: The line performance degrades (if the alarm is reported by an SDH optical interfaceboard).1. Check whether the transmit power at the opposite end and the receive power at the local

end meet the specifications of the optical interfaces. For details, see 8.3.5 BrowsingCurrent Performance Events.



249

If... Then...






If... Then...





Step 2 Cause 2: The line performance degrades (if the alarm is reported by an IF board).1. Check whether the MW_BER_EXC, MW_BER_SD, MW_FEC_UNCOR alarm is

generated. If yes, clear the alarm.

Step 3 Cause 3: The network clock quality degrades.1. Check the network clock status of the alarmed NE.

If... Then...


In this case, the clock may becomeasynchronous and errors may occur.Reconfigure the clock source, and ensure thatthe clock is synchronized on the local NE andopposite NE.



Step 4 Cause 4: The board is faulty (if the alarm is reported by an SDH optical interface board).1. The SDH optical/electrical line board of the local NE is faulty. Loop back the optical

interfaces of the station by using a fiber jumper to locate the fault.

If... Then...








250


If... Then...





----End

Related Information



A.3.24 B3_SD_VC3

Description

The B3_SD_VC3 alarm indicates a signal degrade (SD) condition caused by excessive B3 biterrors in VC-3 paths. A board reports this alarm when detecting that the number of B3 bit errorscrosses the B3_SD_VC3 alarm threshold (10-6, by default).

Attribute


Minor Service alarm

Parameters


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 VC-3 path 1.


When the B3_SD_VC3 alarm occurs, the services in the alarmed path deteriorate.



251

Possible Causesl Cause 1: Higher-level bit error alarms occur in the system.

l Cause 2: The line performance deteriorates (the alarm is reported by an Ethernet opticalport).

l Cause 3: The line performance deteriorates (the alarm is reported by an Ethernet electricalport).

l Cause 4: A board is faulty.

Procedure

Step 1 Cause 1: Higher-level bit error alarms occur in the system.

1. Check whether the local or upstream site detects B1_EXC, B1_SD, B2_EXC, B2_SD,B3_EXC, or B3_SD alarms. If yes, clear the higher-level alarms.


If... Then...


The alarm persists Go to Cause 2 or Cause 3.

Step 2 Cause 2: The line performance deteriorates (the alarm is reported by an Ethernet optical port).

1. Check whether the transmit power at the opposite site and the receive power at the localsite meet the specifications of the optical ports. For details, see Browsing CurrentPerformance Events.

If... Then...

The transmit power at the opposite site istoo low

Replace the optical module at theopposite site.

The transmit power at the opposite site isnormal, but the receive power at the localsite is close to the receiver sensitivity (forexample, a difference within ±3 dB)

A fiber is faulty. Go to the next step.

2. Exchange the optical fibers in the receive and transmit directions of an optical path segment.

If... Then...

The number of bit errors changes Go to the next step.

The number of bit errors does not change Go to Cause 4.

3. If a fiber is 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, clean or replace the fiberconnector, or replace the fiber jumper. Check whether the alarm is cleared.

If... Then...





252

Step 3 Cause 3: The line performance deteriorates (the alarm is reported by an Ethernet electrical port).1. Check whether the cable grounding, cable connectors, and cables are damaged. If yes,

replace the faulty cables.2. Check whether the alarm is cleared.

If... Then...



Step 4 Cause 4: A board is faulty.1. Perform an inloop at the Ethernet port that connects to the alarmed VC-3 path.

If... Then...

The fault is not rectified after theEthernet port is looped back

Replace the alarmed Ethernet processingboard at the local site.

The fault is rectified after the Ethernetport is looped back

Replace the Ethernet processing board atthe opposite site.

----End


A.3.25 BAT1TEMP_SENSOR_FAIL

DescriptionThe BAT1TEMP_SENSOR_FAIL is an alarm indicating that the temperature sensor of batterygroup 1 fails.

Attribute



ParametersNone.

Impact on the SystemThe temperature data of battery group 1 cannot be collected.

Possible Causesl Cause 1: The temperature sensor of battery group 1 is faulty.l Cause 2: The control board of the cabinet is faulty.



253

l Cause 3: Cables are misconnected or damaged.

l Cause 4: The temperature sensor is not installed.

Procedure

Step 1 Cause 1: The temperature sensor of battery group 1 is faulty.

1. Replace the temperature sensor of battery group 1.


If... Then...

The alarm clears End the alarm handling.


Step 2 Cause 2: The control board of the cabinet is faulty.

1. Replace the cabinet.


If... Then...



Step 3 Cause 3: Cables are misconnected or damaged.

1. Replace damaged cables.

2. Connect cables correctly.

Step 4 Cause 4: The temperature sensor is not installed.

1. Install the temperature sensor.

----End

Related Information

None.

A.3.26 BAT2TEMP_SENSOR_FAIL

Description

The BAT2TEMP_SENSOR_FAIL is an alarm indicating that the temperature sensor of batterygroup 2 fails.

Attribute





254

ParametersNone.

Impact on the SystemThe temperature data of battery group 2 cannot be collected.

Possible Causesl Cause 1: The temperature sensor of battery group 2 is faulty.l Cause 2: The control board of the cabinet is faulty.l Cause 3: Cables are misconnected or damaged.l Cause 4: The temperature sensor is not installed.

Procedure

Step 1 Cause 1: The temperature sensor of battery group 2 is faulty.1. Replace the temperature sensor of battery group 2.2. Then, check whether the alarm clears.

If... Then...



Step 2 Cause 2: The control board of the cabinet is faulty.1. Replace the cabinet.2. Then, check whether the alarm clears.

If... Then...



Step 3 Cause 3: Cables are misconnected or damaged.1. Replace damaged cables.2. Connect cables correctly.

Step 4 Cause 4: The temperature sensor is not installed.1. Install the board temperature sensor.

----End


A.3.27 BD_NOT_INSTALLED



255

Description

The BD_NOT_INSTALLED is an alarm indicating that the physical board is installed in acertain slot, but the logical board is not added.

Attribute


Minor Equipment alarm

Parameters


Name Meaning

Parameter 1, Parameter 2 Indicates the ID of the slot.


When the BD_NOT_INSTALLED alarm occurs, the physical board in this slot cannot work.

Possible Causes

Cause 1: The logical board is not added in the corresponding logical slot.

Procedure

Step 1 Cause 1: The logical board is not added in the corresponding logical slot.

1. Configure the logical board.

----End

Related Information

None.

A.3.28 BD_STATUS

Description

The BD_STATUS is an alarm indicating that the board is not in position.



256

Attribute



Parameters

None.


When the BD_STATUS alarm occurs, the alarmed board fails to work.

Possible Causes

If the alarm is reported by a board of the IDU, the possible causes are as follows:

l Cause 1 of the alarm reported by a board of the IDU: The board is installed in an incorrectslot.

l Cause 2 of the alarm reported by a board of the IDU: The board and the backplane are notconnected 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: A certain board is faulty.

If the alarm is reported by the ODU, the possible causes are as follows:

l Cause 1 of the alarm reported by the ODU: The other alarms are generated.

l Cause 2 of the alarm reported by the ODU: The ODU is faulty.

Procedure

Step 1 Cause 1 of the alarm reported by a board of the IDU: The board is installed in an incorrect slot.1. Check whether the logical slot and physical slot of the alarmed board are consistent. For

details, see 8.3.2 Checking the Board Status.

If... Then...

The alarmed board is installed in anincorrect slot

Install the board in a correct slot.

The alarmed board is installed in acorrect slot

Ensure that the board and the backplaneare connected properly.

Step 2 Cause 2 of the alarm reported by a board of the IDU: The board and the backplane are notconnected properly.1. Remove and insert the alarmed board.

If... Then...

The alarm is cleared after the board isremoved and inserted




257

If... Then...

The alarm persists after the board isremoved and inserted


Step 3 Cause 3 of the alarm reported by a board of the IDU: The slot is faulty.

1. Contact Huawei engineers to handle the fault of the slot.TIPGenerally, the slot becomes faulty due to the broken pin or bent pin. Remove the board, and use atorch to observe whether there is any broken pin or bent pin.

2. If a vacant slot is available, insert the board in the vacant 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: A certain board is faulty.


If... Then...




Ensure that the slot is normal.

Step 5 Cause 1 of the alarm reported by the ODU: The other alarms are generated.

1. Query whether the IF board reports the HARD_BAD, BD_STATUS,IF_CABLE_OPEN, BD_NOT_INSTALLED or VOLT_LOS alarm.

If... Then...

The IF board reports any of the preceding alarms Clear the alarm immediately.

The IF board does not report any of the precedingalarms

Replace the alarmed ODU.

Step 6 Cause 2 of the alarm reported by the ODU: The ODU is faulty.

1. Replace the alarmed ODU.

----End

Related Information

None.

A.3.29 BDTEMP_SENSOR_FAIL

Description

The BDTEMP_SENSOR_FAIL is an alarm indicating that the board temperature sensor of thecabinet fails.



258

Attribute



Parameters

None.


The board temperature data of the TCU cannot be collected.

Possible Causesl Cause 1: The board temperature sensor is faulty.l Cause 2: The control board of the cabinet is faulty.l Cause 3: Cables are misconnected or damaged.l Cause 4: The board temperature sensor is not installed.

Procedure

Step 1 Cause 1: The board temperature sensor is faulty.1. Replace the board temperature sensor.2. Then, check whether the alarm clears.

If... Then...




If... Then...




Step 4 Cause 4: The board temperature sensor is not installed.1. Install the board temperature sensor.

----End



259


A.3.30 BIP_EXC

DescriptionThe BIP_EXC is an alarm indicating that the BIP errors exceed the threshold. This alarm occurswhen the board detects that the number of BIP-2 errors (in byte V5) exceeds the preset BIP_EXCalarm threshold (10-3 by default).

Attribute


Minor Service alarm

ParametersNone.

Impact on the SystemWhen the BIP_EXC alarm occurs, the service on the alarmed path is interrupted.

Possible Causesl Cause 1: The line performance degrades (if the alarm is reported by an E1 service board).l Cause 2: The line performance degrades (if the alarm is reported by a Hybrid IF board).l Cause 3: The board is faulty (if the alarm is reported by an E1 service board).l Cause 4: The board is faulty (if the alarm is reported by a Hybrid IF board).

Procedure

Step 1 Cause 1: The line performance degrades (if the alarm is reported by an E1 service board).1. Check whether the performance degradation alarm occurs on the STM-1 path or radio link

along which the E1 service signal travels. If yes, clear the alarm immediately.

The common line performance degradation alarms are as follows:

B1_EXC, B1_SD, B2_EXC, B2_SD, B3_EXC, B3_SD, MW_FEC_UNCOR,RPS_INDI, MW_BER_EXC, and MW_BER_SD.

If... Then...

There is any of the preceding alarms Clear the alarm immediately.

No such alarms occur Ensure that the board is normal.

Step 2 Cause 2: The line performance degrades (if the alarm is reported by a Hybrid IF board).



260

1. Check whether any alarm occurs on the tributary board or IF board that transmits the servicesignal. If yes, clear the alarm immediately.

Step 3 Cause 3: The board is faulty (if the alarm is reported by an E1 service board).

1. Replace the board where the E1 service unit is located. Then, check whether the alarmis cleared.

If... Then...


The alarm persists Replace the system control and cross-connect board.

Step 4 Cause 4: The board is faulty (if the alarm is reported by a Hybrid IF board).

1. Replace the Hybrid IF board. Then, check whether the alarm is cleared.

If... Then...



----End

Related Information


The alarm parameters have the meanings listed in Table A-3 when EMS6 board report the alarm.

Table A-3 Alarm Parameters of EMS6

Name Meaning


Parameter 2, Parameter 3 Indicate the ID of the path that reports thealarm. For example, 0x00 0x01 indicate thatthe alarm is reported in path 1.

A.3.31 BIP_SD

Description

The BIP_SD is an alarm indicating that the signal degrades due to the BIP errors. This alarmoccurs when the board detects that the number of BIP-2 errors (in byte V5) is higher than thepreset BIP_SD alarm threshold (10-6 by default) and lower than the preset BIP_EXC alarmthreshold (10-3 by default).



261

Attribute


Minor Service alarm

Parameters

None.


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

l Cause 2: The line performance degrades (if the alarm is reported by a Hybrid IF board).

l Cause 3: The board is faulty (if the alarm is reported by an E1 service board).

l Cause 4: The board is faulty (if the alarm is reported by a Hybrid IF board).

Procedure

Step 1 Cause 1: The line performance degrades (if the alarm is reported by an E1 service board).

1. Check whether the performance degradation alarm occurs on the STM-1 path or radio linkalong which the E1 service signal travels. If yes, clear the alarm immediately.

The common line performance degradation alarms are as follows:

B1_EXC, B1_SD, B2_EXC, B2_SD, B3_EXC, B3_SD, MW_FEC_UNCOR,RPS_INDI, MW_BER_EXC, and MW_BER_SD.

If... Then...

There is any of the preceding alarms Clear the alarm immediately.

No such alarms occur Ensure that the board is normal.

Step 2 Cause 2: The line performance degrades (if the alarm is reported by a Hybrid IF board).

1. Check whether any alarm occurs on the tributary board or IF board that transmits the servicesignal.

If... Then...

An alarm occurs Clear the alarm immediately.

No alarm occurs Ensure that the board is normal.

Step 3 Cause 3: The board is faulty (if the alarm is reported by an E1 service board).

1. Replace the board where the E1 service unit is located. Then, check whether the alarmis cleared.



262

If... Then...



Step 4 Cause 4: The board is faulty (if the alarm is reported by a Hybrid IF board).1. Replace the Hybrid IF board. Then, check whether the alarm is cleared.

If... Then...



----End

Related InformationHandle the errors of TDM services.


Table A-4 Alarm Parameters of EMS6

Name Meaning


Parameter 2, Parameter 3 Indicate the ID of the path that reports thealarm. For example, 0x00 0x01 indicate thatthe alarm is reported in path 1.

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



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,



263

Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the followingtable.

Name Meaning


Parameter 2, Parameter 3 Indicates the type of the BOOTROM damage.l 0x00, 0x01: damage of the basic BIOSl 0x00, 0x02: damage of the extended BIOS

Parameter 4, Parameter 5 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 does not affect the systemand services.

l If the BOOTROM_BAD alarm occurs and a hard reset is performed on a board, the boardfails to load the BIOS and cannot be started.

Possible Causesl Cause 1: The basic BIOS is damaged.

l Cause 2: The extended BIOS is damaged.

l Cause 3: The BOOTROM database is damaged.

l Cause 4: The system control switch and timing board is faulty.

Procedure

Step 1 Replace the alarmed board.

----End

Related Information

None.

A.3.33 BUS_ERR

Description

The BUS_ERR alarm indicates bus errors. This alarm occurs when the bus becomes abnormal.



264

Attribute


Critical Equipment alarm

Parameters


Name Meaning

Parameter 1, Parameter 2 Indicates the ID of the board that has errors.


When the BUS_ERR alarm occurs, the services that travel along the faulty bus are interruptedor have errors.

Possible Causes

The possible causes of the BUS_ERR alarm are as follows:

l Cause 1: The board is not properly inserted.

l Cause 2: A certain board is faulty.

Procedure

Step 1 Cause 1: The board is not properly inserted.

1. Remove and insert the board.


1. Perform a cold reset on the alarmed board. Then, check whether the alarm is cleared.

If... Then...

The alarm is cleared The fault is rectified. End the alarm handling.

The alarm persists Replace the alarmed board.

----End

Related Information




265

Table A-5 Alarm parameters of EMS6

Name Meaning

Parameter 1 Indicates the bus error type.0x10: The Serdes bus of the GE bridge isfaulty.

A.3.34 CES_ACR_LOCK_ABN

Description

The CES_ACR_LOCK_ABN is an alarm indicating that the locking function of CES ACRservice clock is abnormal.

Attribute


Minor Service alarm

Parameters

Name Meaning

Parameter 1 to Parameter 4 Indicate the index of PW that carries the services associated withthe ACR clock source.

Parameter 5 Indicates clock mode.l 0x01: tracing mode.l 0x02: holdover mode.l 0x03: free-run mode.

Parameter 6 Indicates whether the clock is locked.l 0x00: unlocked.l 0x01: locked.


Service quality is affected.

Possible Causesl Cause 1: CES ACR services are unavailable or have alarms.

l Cause 2: The network is unstable.

l Cause 3: NEs on the service path are abnormal.



266

Procedure

Step 1 Cause 1: CES ACR services are unavailable or have alarms.1. Query the CES services associated with the ACR clock source. For details, see Configuring

the Primary Clock for an ACR Clock Domain.2. Check whether these services have alarms. For details, see 8.3.3 Browsing Current

Alarms.

Step 2 Cause 2: The network is unstable.1. Check for jitters and delays on the network. Query service performance statistics. For

details, see 8.3.5 Browsing Current Performance Events.2. Analyze service performance statistics. If the network is unstable, rectify the faults on the

network, or switch the affected services to a stable network.

Step 3 Cause 3: NEs on the service path are abnormal.1. Query alarms reported by the NEs on the service path. For details, see 8.3.3 Browsing

Current Alarms.2. Handle the alarms. For details, see A.3 Alarms and Handling Procedures.

----End


A.3.35 CES_JTROVR_EXC

DescriptionThe CES_JTROVR_EXC is an alarm indicating that the number of jitter buffer overflowscrosses the specified threshold. This alarm occurs when the board detects that, the number ofjitter buffer overflows per second crosses the specified threshold.

Attribute



ParametersNone.

Impact on the SystemThe buffer area does not have sufficient space for the received frames. As a result, packets arediscarded.

Possible Causesl Cause 1: The size of buffer area is set to a low value.



267

l Cause 2: The PSN network clocks used for the transmission of CES services are notsynchronized.

Procedure

Step 1 Cause 1: The size of buffer area is set to a low value.1. Query the size of buffer area. For details, see Querying CES Service Information.2. Determine whether the size can be increased according to network planning. If yes, change

the size to a greater value. For details, see Managing CES Services.

Step 2 Cause 2: The PSN network clocks used for the transmission of CES services are notsynchronized.1. Synchronize the PSN network clock by setting clock synchronization, reducing

transmission nodes, and optimizing transmission routes.

----End


A.3.36 CES_JTRUDR_EXC

DescriptionThe CES_JTRUDR_EXC is an alarm indicating that the number of jitter buffer underflowscrosses the specified threshold. This alarm occurs when the board detects that, within a period(10s), the number of jitter buffer underflows per second crosses the specified threshold.

Attribute



ParametersNone.

Impact on the SystemWhen this alarm occurs, no packets are available in the buffer area for transmission. As a result,underflows occur in the buffer area.

Possible Causesl Cause 1: Signals degrade on the link.l Cause 2: The PSN network clocks used for the transmission of CES services are not

synchronized.l Cause 3: The link is looped.l Cause 4: The link is congested.



268

l Cause 5: The size of buffer area is set to a low value.

Procedure

Step 1 Cause 1: Signals degrade on the link.1. Troubleshoot the link. For details, see 5.3 Troubleshooting the Radio Link.

Step 2 Cause 2: The PSN network clocks used for the transmission of CES services are notsynchronized.1. Synchronize the PSN network clock by setting clock synchronization, reducing

transmission nodes, and optimizing transmission routes.

Step 3 Cause 3: The link is looped.1. Release the loop.

Step 4 Cause 4: The link is congested.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.

Step 5 Cause 5: The size of buffer area is set to a low value.1. Query the size of buffer area. For details, see Querying CES Service Information.2. Determine whether the size can be increased according to network planning. If yes, change

the size to a greater value. For details, see Managing CES Services.

----End


A.3.37 CES_LOSPKT_EXC

DescriptionThe CES_LOSPKT_EXC is an alarm indicating that the number of lost packets of CES servicescrosses the threshold in a time unit. This alarm occurs when the board detects that, within aperiod (10s), the number of lost packets per second crosses the specified threshold.

Attribute



ParametersNone.

Impact on the SystemWhen this alarm occurs, all 1s are inserted and services are interrupted.



269

Possible Causesl Cause 1: Signals degrade on the link.l Cause 2: The link is looped.l Cause 3: The link is congested.

Procedure

Step 1 Cause 1: Signals degrade on the link.1. Troubleshoot the link. For details, see 5.3 Troubleshooting the Radio Link.




----End

Related InformationPackets are lost when the sequence numbers of received packets are greater than expected.

A.3.38 CES_MALPKT_EXC

DescriptionThe CES_MALPKT_EXC is an alarm indicating that, in a time unit, the number of deformedframes in CES services crosses the threshold. This alarm occurs when the board detects that,within a period (10s), the number of deformed frames in CES services crosses the specifiedthreshold.

Attribute



ParametersNone.

Impact on the SystemA deformed frame is discarded once it is detected. As a result, the packet loss rate increases andservices are affected.

Possible Causesl Cause 1: The RTP head enabling status is different between the two ends of the PW.



270

l Cause 2: Bit errors occur on the link.

Procedure

Step 1 Cause 1: The RTP head enabling status is different between the two ends of the PW.1. Set the RTP head enabling status to the same on the two ends of the PW. For details, see

Modifying CES Service Parameters.

Step 2 Cause 2: Bit errors occur on the link.1. Troubleshoot the link. For details, see 5.3 Troubleshooting the Radio Link.

----End

Related InformationIf a CESoPSN frame contains valid TDM data and does not contain any error indication, but thesize of the CESoPSN frame is not consistent with the specified size, a deformed CESoPSN frameis generated.

A.3.39 CES_MISORDERPKT_EXC

DescriptionThe CES_MISORDERPKT_EXC is an alarm indicating that, in a unit time, the number of lostdisordered packets crosses the specified threshold. This alarm occurs when the board detectsthat, within a period (10s), the number of lost disordered packets per second crosses the specifiedthreshold.

Attribute



ParametersNone.

Impact on the SystemThe packets are disordered. As a result, the packet loss rate increases and services are affected.


Procedure

Step 1 Cause 1: Signals degrade on the link.



271

1. See 5.3 Troubleshooting the Radio Link.




----End

Related InformationPackets are disordered when the sequence numbers of received packets are smaller thanexpected.

A.3.40 CES_RDI

DescriptionThe CES_RDI is an alarm of remote defect indication. When the CES_LOSPKT_EXC alarm isreported at the remote end, the remote end sets the R bit in control word to 1. Upon receiving apacket in which the R bit is 1, the local end reports the CES_RDI alarm.

Attribute



ParametersNone.

Impact on the SystemThe packet loss rate at the remote end crosses the specified threshold.


Procedure

Step 1 Cause 1: Signals degrade on the link.1. See 5.3 Troubleshooting the Radio Link.




272

Step 3 Cause 3: The link is congested.

1. Check the bandwidth utilization. If the bandwidth is exhausted, increase the bandwidth oreliminate any source that transmits a large amount of invalid data.

----End

Related Information

None.

A.3.41 CES_STRAYPKT_EXC

Description

The CES_STRAYPKT_EXC is an alarm indicating that, in a time unit, the number of erroredpackets in CES services crosses the threshold. This alarm occurs when the board detects that,within a period (10s), the number of errored packets in CES services per second crosses thespecified threshold.

Attribute



Parameters

None.


An errored packet is discarded once it is detected. As a result, the packet loss rate increases andservices are affected.

Possible Causes

Cause 1: Links are misconnected.

Procedure

Step 1 Cause 1: Links are misconnected.

1. Check the link configuration and rectify the fault.

----End

Related Information

Incorrect packets are received when the tracing source field in the RTP head is different fromexpected.



273

A.3.42 CESPW_OPPOSITE_ACFAULT

Description

The CESPW_OPPOSITE_ACFAULT is an alarm indicating that the AC circuit on the remoteNE is faulty. On detection of an AC circuit fault, the remote NE sets the L bit in the control wordto 1. When receiving a packet in which the L bit is 1, the local NE reports theCESPW_OPPOSITE_ACFAULT alarm.

Attribute



Parameters

None.


When this alarm occurs, services are interrupted.

Possible Causes

Cause 1: The remote NE reports the T_ALOS, UP_E1_AIS, LFA, LMFA, R_LOS, R_LOF, orMS_AIS alarm.

Procedure

Step 1 Check whether the remote NE reports the T_ALOS, UP_E1_AIS, LFA, LMFA, R_LOS,R_LOF, or MS_AIS alarm.

1. If yes, handle these alarms.

----End

Related Information

None.

A.3.43 CESPW_OPPOSITE_RAI

Description

The CESPW_OPPOSITE_RAI is a remote alarm indication. On detection of the RAI alarm, theremote NE sets the L bit of the control word to 0 and the M field of the control word to 10. Whenreceiving the packet in which the L bit is 0 and the M field is 10, the local NE reports theCESPW_OPPOSITE_RAI alarm.



274

Attribute



Parameters

None.


The services in the downstream direction of the remote NE are interrupted.

Possible Causes

Cause 1: The remote NE detects the RAI alarm.

Procedure

Step 1 Cause 1: The remote NE detects the RAI alarm.1. Clear the ALM_E1RAI alarm on the remote NE.

----End

Related Information

None.

A.3.44 CFCARD_FAILED

Description

The CFCARD_FAILED is an alarm indicating that the operation on the CF card fails.

Attribute



Parameters

None.


When the CFCARD_FAILED alarm occurs, the database cannot be backed up to the CF cardor be restored from the CF card. This alarm may cause rollback of the package loading upgrade.



275

Possible Causesl Cause 1: The CF card fails to be initialized.l Cause 2: The file system of the CF card does not match.l Cause 3: The system control and communication board is faulty, and the file system of the

CF card fails to be created.

ProcedureStep 1 Cause 1: The CF card fails to be initialized.

Cause 2: The file system of the CF card does not match.

1. Replace the CF card and check whether the alarm is cleared.

If... Then...

Yes End the alarm handling.

No Go to Cause 3.

Step 2 Cause 3: The system control and communication board is faulty, and the file system of the CFcard fails to be created.1. Check whether the HARD_BAD alarm occurs on the system control and communication

board.2. If yes, perform a cold reset on the system control and communication board. Then, check

whether the alarm is cleared.

If... Then...


No Replace the system control and communication board.

----End


A.3.45 CFCARD_OFFLINE

DescriptionThe CFCARD_OFFLINE is an alarm indicating that the CF card is out of service.

Attribute



ParametersNone.



276


When the CFCARD_OFFLINE alarm occurs, the database cannot be backed up to the CF cardor be restored from the CF card. This alarm may cause rollback of the package loading upgrade.

Possible Causesl Cause 1: The CF card is not inserted.

l Cause 2: The CF card is in poor contact with the system control and communication board.

l Cause 3: The CF card is faulty.

l Cause 4: The system control and communication board is faulty.

Procedure

Step 1 Cause 1: The CF card is not inserted.

1. Check whether the CF card is installed on the system control and communication board.

If... Then...

No Install the CF card.

Yes Go to Cause 2.

Step 2 Cause 2: The CF card is in poor contact with the system control and communication board.

1. Check whether the CF card is loosened. If yes, re-insert the CF card.


If... Then...


No Go to Cause 3.

Step 3 Cause 3: The CF card is faulty.

1. Replace the CF card.


If... Then...


No Go to Cause 4.

Step 4 Cause 4: The system control and communication board is faulty.

1. Check whether the HARD_BAD alarm occurs on the system control and communicationboard.

2. If yes, perform a cold reset on the system control and communication board. Then, checkwhether the alarm is cleared.

3. If the alarm persists, replace the system control and communication board.

----End



277


A.3.46 CHCS

DescriptionThe CHCS is an alarm indicating the correctable cell error. When a correctable bit error isdetected in the cell header, the CHCS alarm occurs.

Attribute



ParametersNone.

Impact on the SystemWhen the CHCS alarm occurs, the services are not affected. The alarm only indicates that somecells with a bit error are detected during cell delimitation at the ATM port.

Possible Causesl Cause 1: A few bit errors occur in the receive tunnel corresponding to the alarmed ATM

port.l Cause 2: The ATM physical-layer processing chip of the board is faulty.

Procedure

Step 1 Cause 1: A few bit errors occur in the receive tunnel corresponding to the alarmed ATM port.1. On the NMS, check whether the receive tunnel reports any alarms about excessive bit errors,

such as B1_SD, B2_SD, and B3_SD.2. On the NMS, check whether the service is looped.3. If yes, modify the service configuration to release the loop, and then check whether the

alarm is cleared.

Step 2 Cause 2: The ATM physical-layer processing chip of the board is faulty.1. Perform a cold reset on the board that reports the CHCS alarm and check whether the alarm

is cleared. For details, see 8.6.1 Cold Reset.2. Optional: If the CHCS alarm persists after the cold reset, replace the alarmed board and

check whether the alarm is cleared. For details, see 6.5 Replacing the Smart E1 Board.NOTE

Board replacement is not recommended because the alarm does not affect the services.

----End



278


A.3.47 CLK_NO_TRACE_MODE

DescriptionThe CLK_NO_TRACE_MODE alarm indicates that a clock source is not in locked mode. Thisalarm is reported when the current clock does not trace any clock sources.

Attribute




Name Meaning

Parameter 1 Indicates the clock mode.

l 0x01: holdoverl 0x02: free-run

Impact on the SystemWhen the clock source is not in the locked mode, the system clock is not of high quality. Servicesmay have bit errors when the clocks of the NEs are not synchronized. Pointer justification mayoccur in TDM services. If a base station traces a clock that is carried by an Ethernet service, analarm indicating a large clock frequency deviation may occur.

Possible Causesl Cause 1: The system clock source priority table is not configured.l Cause 2: All the clock sources in the clock source priority table fail.

Procedure

Step 1 Cause 1: The system clock source priority table is not configured.1. Configure the system clock source priority table. For details, see Configuring the Clock

Sources.

Step 2 Cause 2: All the clock sources in the clock source priority table fail.



279

1. Troubleshoot the synchronization sources that are listed in the clock source priority table.

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.

The synchronization source is anEthernet clock

Handle the alarm that occurs on the Ethernetboard.

----End

Related Information

None.

A.3.48 COMMUN_FAIL

Description

The COMMUN_FAIL is an alarm indicating the inter-board communication failure. This alarmis reported when the communication between a board and the SCC board is interrupted.

Attribute



Parameters


Name Meaning

Parameter 1 Indicates the ID of the port. The value is always 0x01.



280

Name Meaning

Parameter 2, Parameter 3 Indicates the ID of the path on which the alarm is generated.Parameter 2 is always 0x00. Parameter 3 has the followingmeanings:

l 0x03: inter-board Ethernet communication

Parameter 4, Parameter 5 Parameters 4 and 5 are reserved, and their values are always 0xFF.

Impact on the SystemThe NE configuration cannot be delivered to the board or the board cannot work. Consequently,the services cannot be configured or the protection switching function is unavailable.

Possible Causesl Cause 1: A certain board is reset.l Cause 2: A board and the backplane are connected improperly.l Cause 3: The alarmed board is faulty.l Cause 4: A slot is faulty.

Procedure

Step 1 Cause 1: A certain board is reset.1. After you reset the board, the alarm disappears automatically.

Step 2 Cause 2: A board and the backplane are connected improperly.1. Remove and insert the alarmed board. For details, see 6.1 Removing a Board and 6.2

Inserting a Board. Then, check whether the alarm is cleared.

If... Then...

The alarm disappears after the board isremoved and inserted


The alarm persists after the board isreplaced.

Clear the alarm according to the solutionfor the alarm that is generated when aboard is faulty.

Step 3 Cause 3: The alarmed board is faulty.1. Replace the alarmed board, and then check whether the alarm is cleared. For details, see 6

Part Replacement.

If... Then...

The alarm disappears after the board isreplaced



Clear the alarm according to the solutionfor the alarm that is generated when aslot is faulty.



281

Step 4 Cause 3: A slot is faulty.

1. Contact Huawei engineers to handle the faulty slot.TIPThe slot becomes faulty due to broken pins or bent pins. Remove the board, and use a torch to checkwhether any pins are broken or bent.

2. If a vacant slot is available, insert the board in the vacant slot, and then update the dataon the NMS so that the board can work normally.

----End

Related Information

None.

A.3.49 CONFIG_NOSUPPORT

Description

The CONFIG_NOSUPPORT is an alarm indicating that the configuration is not supported. Thisalarm is reported if the ODU detects that the specified parameters do not meet the requirementsof the ODU.

Attribute



Parameters


Name Meaning

Parameter 1 Indicates that the configuration data does not meet the requirements.l 0x01: The frequency is set incorrectly.l 0x02: The T/R spacing is set incorrectly.l 0x03: The transmit power is set incorrectly.l 0x04: The ATPC threshold is set incorrectly.l 0x05: The bandwidth is set incorrectly.l 0x06: The modulation mode is set incorrectly.



282

Impact on the SystemWhen the CONFIG_NOSUPPORT alarm occurs, the ODU fails to work normally. If theequipment is configured with the 1+1 FD protection, the active ODU generates theCONFIG_NOSUPPORT alarm. In this case, the IF 1+1 protection switching may be triggered.

Possible Causesl Cause 1: The type and configuration parameters of the ODU do not match the requirements.l Cause 2: The AM parameters are incorrectly changed. (This cause can be verified only

when Parameter 1 is 0x03.)

NOTE

Perform the handling procedure of Cause 2 if the following conditions are met: The AM function is enabledon the radio link; the transmit power configured for the ODU is lower than the maximum rated power inAM guaranteed capacity mode.

Procedure

Step 1 Cause 1: The type and configuration parameters of the ODU do not match the requirements.1. Determine the parameter that does not meet the requirement according to the alarm

parameter. Then, handle the fault accordingly.

If... Then...

The alarm parameter takes a value from0x01 to 0x03

Perform the operation described in Step1.2.

The alarm parameter takes a value from0x04 to 0x06

Perform the operation described in Step1.3.

2. Check whether the parameters of the ODU interface meet the requirements of networkplanning. For details, see Configuring the IF/ODU Information of a Radio Link.

If... Then...

The parameters meet the requirements ofnetwork planning

Use the ODU of the proper model.

The parameters do not meet therequirements of network planning

Modify the ODU interface parameters.

3. Check whether the parameters of the IF interface meet the requirements of networkplanning. For details, see Configuring the IF/ODU Information of a Radio Link.

If... Then...

The parameters meet the requirements ofnetwork planning

Replace the IF board.

The parameters do not meet therequirements of network planning

Modify the IF interface parameters. Fordetails, see Configuring the IF/ODUInformation of a Radio Link.

Step 2 Cause 2: The AM parameters are incorrectly changed. (This cause can be verified only whenParameter 1 is 0x03.)1. Verify that the alarm is caused by incorrect change of AM parameters.



283

Perform the handling procedure of Cause 2 if the following conditions are met:

l The AM function is enabled on the radio link.l The transmit power configured for the ODU is lower than the maximum rated power in

AM guaranteed capacity mode

If... Then...

The conditions are met and the transmitpower needs to be changed

Perform a cold reset for the alarmedODU.

The conditions are met but the transmitpower does not need to be changed

Change the parameters of ODU interfacesto recover the original value of transmitpower.

----End


A.3.50 DBMS_ABNORMAL

DescriptionThe DBMS_ABNORMAL is an alarm indicating that the database status is abnormal.

Attribute




Name Meaning

Parameter 1 Indicates the cause of the alarm.

l 0x01: NVRAM is faulty.l 0x02: Space is insufficient.l 0x03: Transaction commit times out.l 0x04: A database is deleted.

Impact on the SystemIf data changes are made after this alarm occurs, data changes cannot take effect.



284

Possible Causesl Cause 1: NVRAM is faulty.l Cause 2: Space is insufficient.l Cause 3: Transaction commit times out.l Cause 4: A database is deleted.

Procedure

Step 1 Reset the alarmed board.

Step 2 Check whether the alarm is cleared. If the alarm persists, replace the alarmed board.

----End


A.3.51 DBMS_ERROR

DescriptionThe DBMS_ERROR is an alarm indicating that errors occur in the processing of the systemdatabase.

Attribute


Major Processing alarm

ParametersNone.

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.

Possible Causesl Cause 1: The database processing fails or the database is damaged.l Cause 2: A certain board is faulty.

Procedure

Step 1 Cause 1: The database processing fails or the database is damaged.1. Reset the system control board.



285

If... Then...

The alarm is cleared after the board isreset

End the fault handling.

The alarm persists after the board isreset

Ensure that the system control board isnormal.

Step 2 Cause 2: A certain board is faulty.1. 6.9 Replacing the System Control, Switch and Timing Board.

----End

Related Information

None.

A.3.52 DBMS_PROTECT_MODE

Description

The DBMS_PROTECT_MODE is an alarm indicating that the system database is in protectionmode.

Attribute


Critical Processing alarm

Parameters

None.


When this alarm occurs, it indicates that errors occur in the system database processing and thesystem configuration may be lost. As a result, the failure indication is returned for some queryand setting commands, and some system functions are unavailable.

Possible Causes

Cause 1: The database enters the protection mode due to frequent resets of the NE software.

Procedure

Step 1 Cause 1: The database enters the protection mode due to frequent resets of the NE software.1. 6.9 Replacing the System Control, Switch and Timing Board.

----End



286

Related Information

None.

A.3.53 DCNSIZE_OVER

Description

The DCNSIZE_OVER is an alarm indicating an over-sized DCN network.

Attribute



Parameters


Name Meaning

Parameter 1, Parameter 2 Indicate the size of the DCN network.

Impact on the Systeml Some NEs become unreachable to the NMS because DCN packets cannot be forwarded

timely due to insufficient CPU resources.

l The DCN network is prone to route flapping and storms.

Possible Causes

Cause: The size of the DCN network crosses the preset threshold.

Procedure

Step 1 Cause: The size of the DCN network crosses the preset threshold.

1. Replan the DCN network based on actual networking conditions.

----End

Related Information

None.



287

A.3.54 DDN_LFA

DescriptionThe DDN_LFA is an alarm indicating loss of basic frame alignment for framed E1 services.This alarm occurs when DDN side fails to receive the basic frame alignment signal for framedE1 services.

Attribute



ParametersNone.

Impact on the SystemE1 services on the alarmed board are unavailable.

Possible Causesl Cause 1: The interconnected user equipment is faulty.l Cause 2: The service frame format is configured incorrectly.l Cause 3: The alarmed board has hardware faults.

ProcedureStep 1 Cause 1: The interconnected user equipment is faulty.

1. Troubleshoot the interconnected user equipment.

Step 2 Cause 2: The service frame format is configured incorrectly.1. Set the E1 frame format of the local port to the same as that of the opposite port.

Step 3 Cause 3: The alarmed board has hardware faults.1. Check whether the alarmed board also reports any hardware alarms, such as

HARD_BAD.2. If yes, perform a cold reset on the alarmed board and check whether the DDN_LFA alarm

is cleared.

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.

----End



288

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

A.3.55 DOWN_E1_AIS

Description

The DOWN_E1_AIS is an alarm of the 2 Mbit/s downlink signal. This alarm occurs when thetributary board detects the 2 Mbit/s downlink signal of all 1s.

Attribute



Parameters

None.


When the DOWN_E1_AIS alarm occurs, the E1 signal in the alarmed path is unavailable.

Possible Causesl Cause 1: The opposite NE transmits the E1_AIS alarm.l Cause 2: On the local NE, the receive unit of the tributary board or the system control and

cross-connect board is faulty.

Procedure

Step 1 Cause 1: The opposite NE transmits the E1_AIS alarm.1. Check whether the opposite NE reports the UP_E1_AIS or T_ALOS alarm.

If... Then...

The opposite NE reports the UP_E1_AISor T_ALOS alarm

Clear the alarm immediately.

The opposite NE does not report theUP_E1_AIS or T_ALOS alarm

Ensure that the board on the local NE isnormal.

Step 2 Cause 2: On the local NE, the receive unit of the tributary board or the system control and cross-connect board is faulty.1. Replace the board where the alarmed tributary unit is located. Then, check whether

the alarm is cleared.



289

If... Then...


The alarm persists Replace the system control and cross-connect board on thelocal NE.

----End

Related Information

If EFP8 reports the alarm, the alarm parameters have the meanings listed inTable A-6.

Table A-6 Alarm Parameters of EFP8

Name Meaning

Parameter 1 0x01, indicates optical interface number.

Parameter 2, Parameter 3 Indicates the number of the path.

A.3.56 DROPRATIO_OVER

Description

The DROPRATIO_OVER alarm indicates that the number of lost packets crosses the thresholdwhen queue congestion occurs at a port. This alarm is reported when the ratio of lost packets onan object under performance monitoring is higher than the expected ratio.

Attribute


Minor Service alarm

Parameters

Name Meaning

Parameter 1 Indicates the direction in which traffic crosses the threshold.

l 0x00: Traffic crosses the threshold in the receive direction.l 0x01: Traffic crosses the threshold in the transmit direction.


Service packet loss occurs.



290

Possible Causesl Cause 1: Service configuration is incorrect.l Cause 2: Actual traffic exceeds the configured port bandwidth or committed information

rate (CIR).

Procedure

Step 1 Cause 1: Service configuration is incorrect.1. Check and reconfigure services according to the network plan.

Step 2 Cause 2: Actual traffic exceeds the configured port bandwidth or CIR.1. 8.17 Querying Traffic, Physical Bandwidth, or Bandwidth Utilization of Ethernet

Ports. If traffic is large, check whether a network storm has occurred, and eliminate thesource that illegally sends a large amount of data.

2. If the port bandwidth is too low, follow instructions in Modifying Port Policies to increaseport bandwidth or expand the network.

----End

Related InformationIf packet loss is indicated in the receive direction, check the method of handling red packets inthe traffic classification configuration. If the method of handling red packets is non-discard,packets may not be actually lost in the receive direction.

A.3.57 E1_LOC

DescriptionThe E1_LOC is an alarm indicating that the uplink 2M clock is lost. This alarm occurs whenthe tributary board fails to extract the clock from the E1 signal.

Attribute



ParametersNone.

Impact on the SystemWhen the E1_LOC occurs, the service is not affected.

Possible Causesl Cause 1: The opposite NE is faulty.l Cause 2: The wiring sequence of the cable is incorrect.



291

l Cause 3: The receive unit of the tributary board on the local NE is faulty.

l Cause 4: The input E1 signal has an abnormal waveform.

Procedure

Step 1 Cause 1: The opposite NE is faulty.

1. Rectify the fault on the opposite NE.

Step 2 Cause 2: The wiring sequence of the cable is incorrect.

1. Redo the cable.

Step 3 Cause 3: The receive unit of the tributary board on the local NE is faulty.

1. Replace the board where the line unit is located.

Step 4 Cause 4: The input E1 signal has an abnormal waveform.

1. Check whether any external interference causes the abnormal waveform of the E1 signal.

If... Then...

There is the external interference The fault is rectified. End the alarm handling.

There is no external interference Contact Huawei engineers.

----End

Related Information

None.

A.3.58 E1_LOS

Description

The E1_LOS is an alarm indicating the loss of the E1 signal. This alarm occurs when the tributaryboard detects the uplink E1 signal of all 0s.

Attribute



Parameters

None.


When the E1_LOS alarm occurs, the E1 service is interrupted.



292

Possible Causesl Cause 1: The cable is not connected or the cable is faulty.

l Cause 2: The opposite NE is faulty.

l Cause 3: The tributary board on the local NE is faulty.

Procedure

Step 1 Cause 1: The cable is not connected or the cable is faulty.

1. Check whether the cable is connected properly.

If... Then...

The cable is not connected properly Connect the cable properly.

The cable is prepared incorrectly Redo the cable.



Step 3 Cause 3: The tributary board on the local NE is faulty.

1. Replace the board where the tributary unit is located.

----End

Related Information

None.

A.3.59 ENVHUM_SENSOR_FAIL

Description

The ENVHUM_SENSOR_FAIL is an alarm indicating that the ambient humidity sensor of thecabinet fails.

Attribute



Parameters

None.


The ambient humidity data of the PMU cannot be collected.



293

Possible Causesl Cause 1: The ambient humidity sensor is faulty.

l Cause 2: The control board of the cabinet is faulty.


l Cause 4: The ambient humidity sensor is not installed.

Procedure

Step 1 Cause 1: The ambient humidity sensor is faulty.

1. Replace the ambient humidity sensor.


If... Then...






If... Then...






Step 4 Cause 4: The ambient humidity sensor is not installed.

1. Install the ambient humidity sensor.

----End

Related Information

None.

A.3.60 ENVTEMP_SENSOR_FAIL

Description

The ENVTEMP_SENSOR_FAIL is an alarm indicating that the ambient temperature sensor ofthe cabinet fails.



294

Attribute



Parameters

None.


The ambient temperature data of the TCU cannot be collected.

Possible Causesl Cause 1: The ambient temperature sensor is faulty.l Cause 2: The control board of the cabinet is faulty.l Cause 3: Cables are misconnected or damaged.l Cause 4: The ambient temperature sensor is not installed.

Procedure

Step 1 Cause 1: The ambient temperature sensor is faulty.1. Replace the ambient temperature sensor.2. Then, check whether the alarm clears.

If... Then...




If... Then...




Step 4 Cause 4: The ambient temperature sensor is not installed.1. Install the ambient temperature sensor.

----End



295


A.3.61 ENVTEMP1_SENSOR_FAIL

DescriptionThe ENVTEMP1_SENSOR_FAIL is an alarm indicating that ambient temperature sensor 1 ofthe cabinet fails.

Attribute



ParametersNone.

Impact on the SystemAmbient temperature data 1 of the PMU cannot be collected.

Possible Causesl Cause 1: Ambient temperature sensor 1 is faulty.l Cause 2: The control board of the cabinet is faulty.l Cause 3: Cables are misconnected or damaged.l Cause 4: Ambient temperature sensor 1 is not installed.

Procedure

Step 1 Cause 1: Ambient temperature sensor 1 is faulty.1. Replace ambient temperature sensor 1.2. Then, check whether the alarm clears.

If... Then...




If... Then...




296

If... Then...



Step 4 Cause 4: Ambient temperature sensor 1 is not installed.1. Install ambient temperature sensor 1.

----End


A.3.62 ENVTEMP2_SENSOR_FAIL

DescriptionThe ENVTEMP2_SENSOR_FAIL is an alarm indicating that ambient temperature sensor 2 ofthe cabinet fails.

Attribute



ParametersNone.

Impact on the SystemAmbient temperature data 2 of the PMU cannot be collected.

Possible Causesl Cause 1: Ambient temperature sensor 2 is faulty.l Cause 2: The control board of the cabinet is faulty.l Cause 3: Cables are misconnected or damaged.l Cause 4: Ambient temperature sensor 2 is not installed.

Procedure

Step 1 Cause 1: Ambient temperature sensor 2 is faulty.1. Replace ambient temperature sensor 2.2. Then, check whether the alarm clears.



297

If... Then...




If... Then...




Step 4 Cause 4: Ambient temperature sensor 2 is not installed.1. Install ambient temperature sensor 2.

----End


A.3.63 ETH_APS_LOST

DescriptionThe ETH_APS_LOST is an alarm indicating that the APS frame is lost. This alarm occurs whenno APS frame is received from the protection channel.

Attribute



ParametersNone.

Impact on the SystemWhen this alarm occurs, the APS protection may fail.

Possible Causesl Cause 1: The opposite NE is not configured with the APS protection.



298

l Cause 2: The APS protection group is deactivated.l Cause 3: The settings of the APS protection group differ between the two ends.l Cause 4: The service on the protection channel is interrupted.

ProcedureStep 1 Cause 1: The opposite NE is not configured with the APS protection.

1. On the NMS, check whether the opposite NE is configured with the APS protection. Fordetails, see Querying MPLS APS Status.

If... Then...

The opposite NE is not configured with the APS protection Go to the next step.

The opposite NE is configured with the APS protection Go to Cause 2.

2. Create a matching APS protection group on the opposite NE, and activate the APS protocol.Check whether the alarm clears.

3. If the alarm persists, proceed to cause 4.

Step 2 Cause 2: The APS protection group is deactivated.1. Check whether the APS protocol is activated at both ends.

If... Then...

The APS protocol is deactivated at one end Activate the APS protocol at the end.

The APS protocol is activated at both ends Go to Cause 3.

2. Check whether the alarm clears. If the alarm persists, go to Cause 3.

Step 3 Cause 3: The settings of the APS protection group differ between the two ends.1. On the NMS, check whether the settings of the APS protection group are the same at the

two ends. If the settings differ between the two ends, change them to the same. Then,deactivate and activate the APS protection group at the two ends.

2. Check whether the alarm clears. If the alarm persists, go to Cause 4.

Step 4 Cause 4: The service on the protection channel is interrupted.1. Check whether the protection channel reports an alarm related to signal loss or signal

degrade, such as ETH_LOS. If yes, clear the alarm immediately.

----End


A.3.64 ETH_APS_PATH_MISMATCH

DescriptionThe ETH_APS_PATH_MISMATCH is an alarm indicating that the working and protectionpaths of the APS protection group differ between the two ends. This alarm is reported when theworking and protection paths of one APS protection group at one end are different from thoseat the other end.



299

Attribute



Parameters

None.


When this alarm occurs, service protection fails.

Possible Causesl Cause 1: The configured working and protection paths differ between the two ends.

l Cause 2: The physical link is connected incorrectly.

Procedure

Step 1 Cause 1: The configured working and protection paths differ between the two ends.

1. Check whether the APS settings at the two ends are the same. For details, see QueryingMPLS APS Status.

2. If the APS settings are different, change the settings to the same. Then, deactivate andactivate the APS protection group at the two ends. Then, check whether the alarm clears.

3. If the alarm persists, go to Cause 2.

Step 2 Cause 2: The physical link is connected incorrectly.

1. Check whether the fiber or cable is correctly connected between the two ends. If not,connect the fiber or cable properly.

----End

Related Information

None.

A.3.65 ETH_APS_SWITCH_FAIL

Description

The ETH_APS_SWITCH_FAIL is an alarm of a protection switching failure. This alarm isreported when the request signal in the transmitted Automatic Protection Switching (APS) frameis different from the bridge signal in the received APS frame and this symptom lasts for 50 ms.



300

Attribute



ParametersNone.

Impact on the SystemWhen this alarm occurs, service protection fails.

Possible CausesCause 1: The settings of the APS protection group differ between the two ends.

Procedure

Step 1 Cause 1: The settings of the APS protection group differ between the two ends.1. Change the settings to the same. For details, see Creating an MPLS APS Protection Group.

Then, deactivate and activate the APS protection group at the two ends.

----End


A.3.66 ETH_APS_TYPE_MISMATCH

DescriptionThe ETH_APS_TYPE_MISMATCH is an alarm of protection scheme mismatch. This alarm isreported when the information in the received Automatic Protection Switching (APS) frame isdifferent from the APS settings at the local end.

Attribute






301


Name Meaning

Parameter 1 Indicates the specific difference.

l 0x01: Indicates that the switching type is different.l 0x02: Indicates that the switching direction is different.l 0x03: Indicates that the revertive mode is different.

Impact on the SystemThis alarm may cause the APS protection failure, and therefore the service protection fails.

Possible Causesl Cause 1: The switching type is different.l Cause 2: The switching direction is different.l Cause 3: The revertive mode is different.

ProcedureStep 1 Determine the possible cause of the alarm according to the alarm parameters.

1. Change the settings of the APS protection group to the same at the two ends. For details,see Querying MPLS APS Status. Then, deactivate and activate the APS protection groupat the two ends.

----End


A.3.67 ETH_CFM_LOC

DescriptionThe ETH_CFM_LOC is an alarm indicating the loss of connectivity. This alarm occurs whenthe system fails to receive the CCM packet from the remote MEP in 3.5 connectivity check (CC)periods successively.

Attribute






302


Name Meaning

Parameter 1, Parameter 2, Parameter 3,Parameter 4 (Port)

Indicates the ID of the alarmed port.

Parameter 5, Parameter 6 (VLAN ID) Indicates the VLAN ID of the MEP.

Parameter 7 (Direction) Indicates the direction of the local MEP.l 0x00: The port is direction insensitive.l 0x01: The port is in the ingress direction.l 0x02: The port is in the egress direction.

Parameter 8 (Level) Indicates the MD level of the local MEP.l 0x00: consumer MEP level (low)l 0x01: consumer MEP level (medium)l 0x02: consumer MEP level (high)l 0x03: provider MEP level (low)l 0x04: provider MEP level (high)l 0x05: operator MEP level (low)l 0x06: operator MEP level (medium)l 0x07: operator MEP level (high)NOTE

Consumer indicates the user, provider indicates thesupplier, and operator indicates the carrier.

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

Impact on the Systeml When the ETH_CFM_LOC alarm occurs, the LB and LT detection functions of Ethernet

service OAM are unavailable.l The service between the relevant standard MEPs may be interrupted.

Possible Causesl Cause 1: The line between the local standard MEP and the remote standard MEP is

interrupted.l Cause 2: The Ethernet service in the maintenance association (MA) to which the local 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 network cables and fibers) between the standard

MEPs are connected properly.



303

If... Then...

The physical links are connected improperly Connect the physical links properly.

The physical links are connected properly Go to Cause 2.

Step 2 Cause 2: The Ethernet service in the maintenance association (MA) to which the local MEPbelongs is faulty.1. Check whether Ethernet service in the maintenance association (MA) to which the local

MEP belongs is configured correctly.

If... Then...

The service is configured incorrectly Modify the configuration of the service to ensureconsistency at two ends.

The service is configured correctly Go to Cause 3.

Step 3 Cause 3: Serious congestion occurs on the network.1. Check the utilization of bandwidth. If the bandwidth is exhausted, increase the bandwidth

or eliminate any source that transmits a large amount of invalid data.

----End

Related InformationThe Table A-7 describes the meanings of the parameters in the ETH_CFM_LOC alarm reportedby the EoS/EoPDH plane.

Table A-7 Alarm Parameters

Name Meaning

Parameter 1 to Parameter 4 MD

Parameter 5 to Parameter 8 MA

Parameter 9, Parameter 10 MEP ID

Parameter 11 to Parameter 14 Indicates the ID of the alarmed port.When these parameters indicate theVCTRUNK ID, parameter values = (0x01 -0x10) + 0x80.

Parameter 15, Parameter 16 Indicates the VLAN ID of the MEP.

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



304

Name Meaning

Parameter 18 Indicates the MD level of the local MEP.l 0x00: consumer MEP level (low)l 0x01: consumer MEP level (medium)l 0x02: consumer MEP level (high)l 0x03: provider MEP level (low)l 0x04: provider MEP level (high)l 0x05: operator MEP level (low)l 0x06: operator MEP level (medium)l 0x07: operator MEP level (high)NOTE

Consumer indicates the user, provider indicatesthe supplier, and operator indicates the carrier.

Parameter 19, Parameter 20 Indicates the ID of the remote MEP.NOTE

If the alarmed port is a VCTRUNK, theseparameters are not supported.

A.3.68 ETH_CFM_MISMERGE

Description

The ETH_CFM_MISMERGE is an alarm indicating an incorrect connection. This alarm occurswhen the system receives the CCM packet whose MA mismatches or whose priority is lower.

Attribute



Parameters


Name Meaning






305

Name Meaning





When the ETH_CFM_MISMERGE alarm occurs, the service between the relevant standardMEPs may be interrupted, and the data flow may be routed incorrectly.

Possible Causesl Cause 1: The names of the maintenance domain and the maintenance alliance that the

standard MEPs correspond to are inconsistent.l Cause 2: The levels of the maintenance domains that the standard MEPs correspond to are

different.l Cause 3: The physical connection is incorrect.

Procedure

Step 1 Cause 1: The names of the maintenance domain and the maintenance alliance that the standardMEPs correspond to are inconsistent.1. Check whether the names of the maintenance domain and the maintenance alliance that the

standard MEPs correspond to are consistent.

If... Then...

The names are inconsistent Set the other names of maintenance domain andmaintenance alliance to ensure consistency at both ends.

The names are consistent Go to Cause 2.

Step 2 Cause 2: The levels of the maintenance domains that the standard MEPs correspond to aredifferent.



306

1. Check whether the MD levels of the standard MEPs are the same.

If... Then...

The levels are different Set the MD levels again to ensure consistency at both ends.

The levels are the same Go to Cause 3.

Step 3 Cause 3: The physical connection is incorrect.1. Check the physical connection of the Ethernet service route and rectify the fault of the

physical connection if any.

----End



Name Meaning









307

Name Meaning



A.3.69 ETH_CFM_RDI

DescriptionThe ETH_CFM_RDI is an alarm indicating the CCM packet with RDI received from the remoteMEP. This alarm occurs when the system receives the CCM packet with RDI from the remotemaintenance end point (MEP).

Attribute




Name Meaning






308

Name Meaning


Parameter 8 (Level) Indicates the MD level of the local MEP.l 0x00: consumer MEP level (low).l 0x01: consumer MEP level (medium).l 0x02: consumer MEP level (high).l 0x03: provider MEP level (low).l 0x04: provider MEP level (high).l 0x05: operator MEP level (low).l 0x06: operator MEP level (medium).l 0x07: operator MEP level (high).NOTE


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

Impact on the Systeml When the ETH_CFM_RDI alarm occurs, the loopback (LB) and link trace (LT) detection

functions of Ethernet service OAM are unavailable.l The service between the relevant standard MEPs may be interrupted.

Possible Causesl Cause 1: The remote MEP fails to receive the correct CCM packet.

Procedure

Step 1 Cause 1: The remote MEP fails to receive the correct CCM packet.1. Determine the alarmed port according to the alarm parameter.2. Check whether the remote MEP that is connected to the port reports the

ETH_CFM_MISMERGE, ETH_CFM_UNEXPERI, or ETH_CFM_LOC alarm.

----End




309


Name Meaning









Parameter 19, Parameter 20 Indicates the ID of the remote MEP.NOTE

If the alarmed port is a VCTRUNK, theseparameters are not supported.

A.3.70 ETH_CFM_UNEXPERI

DescriptionThe ETH_CFM_UNEXPERI is an alarm indicating the errored frame. This alarm occurs whenthe system receives invalid CCM packets.



310

Attribute




Name Meaning







Impact on the Systeml When the ETH_CFM_UNEXPERI alarm occurs, the LB and LT detection functions of

Ethernet service 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 is inconsistent. For example, the

connectivity check (CC) periods are different, and the IDs of the MEPs are in conflict.



311

l Cause 3: The service is looped back and the looped packet is received.

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 is inconsistent. For example, theconnectivity check (CC) periods are different, and the IDs of the MEPs are in conflict.

1. Check whether the CC periods set at the MEPs are the same.

If... Then...

The CC periods are different Change the CC periods to ensure consistency at bothends.

The CC periods are the same Go to the next step.

2. Check whether the IDs of the MEPs in the maintenance domain are in conflict.

If... Then...

The IDs are in conflict Change the conflicting IDs.

The IDs are not in conflict Go to Cause 3.

Step 3 Cause 3: The service is looped back and the looped packet is received.

1. Check whether any loop exists at each IP port of the service trail. If yes, release the loopand clear the alarm.

----End

Related Information

The Table A-10 describes the meanings of the parameters in the ETH_CFM_LOC alarmreported by the EoS/EoPDH plane.


Name Meaning








312

Name Meaning




A.3.71 ETH_EFM_DF

DescriptionThe ETH_EFM_DF is an alarm indicating negotiation failure. This alarm occurs when the point-to-point OAM protocol negotiation fails at the Ethernet port.

Attribute






313

Name Meaning

Parameter 1 Indicates the reason why the negotiation fails.

l 0x01: The local link is faulty.l 0x02: The local end fails to receive any OAM packets in a specified period.l 0x03: The OAM settings of the opposite end do not meet the requirements of

the local end.l 0x04: The OAM settings of the local end do not meet the requirements of the

opposite end.


When the ETH_EFM_DF alarm occurs, the service at the alarmed port may be interrupted.

Possible Causesl Cause 1: The physical port of the local end is faulty.

l Cause 2: The point to point OAM protocol is not enabled at the opposite end.

l Cause 3: The OAM configuration at both ends is inconsistent.

Procedure

Step 1 Cause 1: The physical port of the local end is faulty.

1. Check whether the physical port is faulty. If yes, replace the board where the Ethernetport is located.

Step 2 Cause 2: The point to point OAM protocol is not enabled at the opposite end.

1. Enable the point to point OAM protocol at the opposite end.

Step 3 Cause 3: The OAM configuration at both ends is inconsistent.

1. Reconfigure the point to point OAM protocol and ensure the consistency at both ends.

----End

Related Information

None.

A.3.72 ETH_EFM_EVENT

Description

The ETH_EFM_EVENT is an alarm indicating the performance event reported on the oppositeNE. This alarm occurs when the local end receives the link error indication packet (OAMPDUM)from the opposite end.



314

Attribute



Parameters


Name Meaning

Parameter 1 Indicates the type of the link event.

l 0x01: errored symbol period.l 0x02: errored frame.l 0x03: errored frame period.l 0x04: errored frame seconds summary.


When the ETH_EFM_EVENT alarm occurs, the service at the alarmed port may be interrupted.

Possible Causesl Cause 1: The physical port at the local end is faulty.

l Cause 2: The equipment at the opposite end is faulty.

Procedure

Step 1 Cause 1: The physical port at the local end is faulty.

1. Check whether the physical port is faulty. If yes, replace the board where the Ethernetport is located.

Step 2 Cause 2: The equipment at the opposite end is faulty.

1. Rectify the fault of the equipment at the opposite end.

----End

Related Information

None.

A.3.73 ETH_EFM_LOOPBACK



315

DescriptionThe ETH_EFM_LOOPBACK is an alarm indicating the loopback. This alarm occurs when thelocal end initiates a loopback or responds to a loopback request from the opposite end.

Attribute




Name Meaning

Parameter 1 Indicates the state of the loopback.

l 0x01: The local end initiates a loopback.l 0x02: The local end responds to a loop request from the opposite end.

Impact on the SystemWhen the ETH_EFM_LOOPBACK alarm occurs, the service at the alarmed port is looped back.

Possible Causesl Cause 1: The local end initiates a loopback.l Cause 2: The opposite end initiates a loopback.

Procedure

Step 1 Cause 1: The local end initiates a loopback.1. According to the alarm parameter, it is determined that the local end initiates a loopback.

Determine the causes of the loopback initiated at the local end and release the loopback assoon as possible.

Step 2 Cause 2: The opposite end initiates a loopback.1. According to the alarm parameter, it is determined that the opposite end initiates a loopback.

Determine the causes of the loopback initiated at the opposite port and release the loopbackas soon as possible.

----End




316

A.3.74 ETH_EFM_REMFAULT

Description

The ETH_EFM_REMFAULT is an alarm indicating the fault on the opposite NE. This alarmoccurs when the local end receives the fault indication packet (OAMPDUM) from the oppositeend.

Attribute



Parameters


Name Meaning

Parameter 1 Indicates the fault type at the opposite end.

l 0x01: link fault.l 0x02: dying gasp.l 0x03: critical event.


When the ETH_EFM_REMFAULT alarm occurs, the service at the alarmed port may beinterrupted.

Possible Causesl Cause 1: The opposite NE is reset.


Procedure

Step 1 Cause 1: The opposite NE is reset.

1. Check whether the opposite NE is reset frequently.

If... Then...

The opposite NE is reset frequently Rectify the fault on the opposite NE.



317

If... Then...

The opposite NE is not reset frequently Reset the opposite NE, and the alarm iscleared.



----End

Related Information

None.

A.3.75 ETH_LOS

Description

The ETH_LOS is an alarm indicating the loss of Ethernet port connection.

Attribute



Parameters

None.


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

Possible Causesl Cause 1: The negotiation fails because the transmit port and receive port work in different

modes.

l Cause 2: The cable or fiber is faulty.

l Cause 3: The local NE is faulty.


Procedure

Step 1 Cause 1: The negotiation fails because the transmit port and receive port work in different modes.

1. Check whether the transmit port and receive port work in the same mode.



318

If... Then...

The transmit port and receive port workin different modes

Correctly set the working modes of thetransmit port and receive port.

The transmit port and receive port workin the same mode

Go to Cause 2.

Step 2 Cause 2: The cable or fiber is faulty.1. Check the network cable or fiber jumper connected to the alarmed port.

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 or fiber is damaged Insert the connector properly or replace thedamaged fiber jumper.

The connection is normal Go to Cause 3.

Step 3 Cause 3: The local NE is faulty.1. Check whether any fault occurs on the alarmed port.

If... Then...

The equipment is faulty Replace the alarmed board on the local NE.

The equipment is normal Go to Cause 4.

Step 4 Cause 4: The opposite NE is faulty.1. Check whether any fault occurs on the equipment interconnected with the alarmed port.2. Rectify the fault.

----End


A.3.76 ETH_NO_FLOW

DescriptionThe ETH_NO_FLOW is an alarm indicating that the Ethernet port has no flow. This alarm isreported when an enabled Ethernet port is in link up state but has no flow.

Attribute


Major Service alarm



319

Parameters


Name Meaning

Parameter 1 Indicates the MAC port number.

Parameter 2, Parameter 3 Indicate the path ID.

Parameter 2 indicates the most significant bits and the value isalways 0x00. Parameter 3 indicates the least significant bits and thevalue is always 0x01.

Parameter 4 Indicates the direction in which the flow is unavailable.

l 0x00: Rx direction.l 0x01: Tx direction.


When this alarm occurs, it indicates that the alarmed port has no flow.

Possible Causesl Cause 1: The port is enabled and in link up state, but is configured with no service.l Cause 2: The port is enabled and in link up state, but does not transmit any packet due to

the service fault at the local end.l Cause 3: The port is enabled and in link up state, but does not receive any packet due to

the service fault at the remote end.

Procedure

Step 1 Determine the MAC port number, alarmed board, and cause according to the parameters.

Step 2 Cause 1: No services are configured.1. Configure the Ethernet service.

Step 3 Cause 2: No services are available.

If... Then...

No services are available in the transmitdirection

Check whether the service is normal at thelocal end.

No services are available in the receivedirection

Check whether the service is normal at theremote end.

----End



320

Related Information

None.

A.3.77 ETHOAM_DISCOVER_FAIL

Description

The ETHOAM_DISCOVER_FAIL alarm indicates a discovery failure when the point-to-pointETH-OAM function is enabled. This alarm occurs when the OAM function is enabled at a portof a board and the negotiation between the port and the opposite equipment fails.

Attribute



Parameters


Name Meaning

Parameter 1 Indicates the ID of the alarmed port.

Parameter 2, Parameter 3 The values are always 0x00 0x01.

Parameter 4 Indicates the reason why the negotiation fails.

l 0x01: A fault occurs at 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 IEEE 802.3ah is unavailable.



321

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. If yes, replace the alarmed board.

Step 2 Cause 2: The P2P OAM protocol is not enabled at the opposite end.

1. Enable the P2P OAM protocol at the opposite end. For details, see Enabling the 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.3.78 ETHOAM_RMT_CRIT_FAULT

Description

The ETHOAM_RMT_CRIT_FAULT is an alarm indicating that the point-to-point EthernetOAM detects a critical fault at the remote end. This alarm occurs when a port with the OAMfunction enabled receives the OAM packets that contain critical fault information from theopposite end.

Attribute



Parameters




322

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 the power failure occur at

the opposite end.l 0x03-0xff: other faults.


When this alarm occurs, the services on the link may be interrupted.

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.

If... Then...

The value of Parameter 4 is 0x01 Go to Cause 1.


Parameter 4 is a value from 0x03 to 0xff. Go to Cause 3.

Step 2 Cause 1: A link fault occurs at the remote MEP.

1. Handle the ETH_LOS alarm at 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, and recover the power supplyto the remote MEP.

Step 4 Cause 3: Other faults occur at the remote MEP.

1. Contact Huawei technical support engineers.

----End

Related Information

None.



323

A.3.79 ETHOAM_RMT_LOOP

Description

The ETHOAM_RMT_LOOP is an alarm indicating that a remote loopback is initiated when thepoint-to-point Ethernet OAM function is enabled. This alarm occurs when the local equipmentinitiates a remote loopback or responds to the remote loopback initiated by the oppositeequipment.

Attribute



Parameters


Name Meaning



Parameter 4 l 0x01: The loopback is initiated.l 0x02: The loopback is responded.


The services are looped back between the local equipment and the opposite equipment. Theservices and other protocol packets 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 thecommand.

Procedure

Step 1 Check the alarm on the NMS and determine the type of loopback according to the alarmparameters.



324

If... Then...



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

Related Information

None.

A.3.80 ETHOAM_RMT_SD

Description

The ETHOAM_RMT_SD alarm indicates that the point-to-point Ethernet-OAM detects thedegradation of remote Ethernet performance. This alarm occurs when a port with the OAMfunction enabled receives link event notification packets from the opposite end.

Attribute



Parameters


Name Meaning





325

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


When this alarm occurs, the performance of services degrades.

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.

If... Then...

If yes Disable the link event notification function at the opposite end.

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

If not Set the thresholds to appropriate values.

If yes 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 sendany link event notification packet to the local end. Then, the alarm at the local end is clearedautomatically.

----End

Related Information

None.



326

A.3.81 ETHOAM_SELF_LOOP

DescriptionThe ETHOAM_SELF_LOOP is an alarm indicating the loopback of the MAC port that runs thepoint-to-point OAM protocol. This alarm occurs when the MAC port of a board receives theOAM protocol packet sent by the port itself or the board after the loop detection function isenabled.

Attribute


Major Environmental alarms


Name Meaning

Parameter 1 Indicates the loopback type.

l 0x01: selfloop of the port.l 0x02: selfloop of the board.

Impact on the SystemWhen the ETHOAM_SELF_LOOP alarm occurs, a network storm may occur due to theloopback.

Possible Causesl Cause 1: The cable connected to the port is self-looped, or the port is connected to a LAN

that has a loopback, or the PHY/MAC loopback is manually configured at the port.l Cause 2: Two ports of the board are connected through cables or two ports of the board are

connected to the same LAN.

Procedure

Step 1 Determine the loopback type according to Parameter 1, and then handle the loopbackaccordingly.

If... Then...




327

If... Then...


Step 2 Cause 1: The cable connected to the port is self-looped, or the port is connected to a LAN thathas a loopback, or the PHY/MAC loopback is manually configured at the port.

If... Then...

The PHY/MAC loopback is manuallyconfigured at the port

Manually release the PHY/MAC loopback (orwait five minutes for the automatic release bythe NE if the automatic loopback releasefunction is enabled on the NE). Then, theselfloop is released.

The cable connected to the port is self-looped

Connect the cable properly to release theselfloop.

The port is connected to a LAN that has aloopback

Release the loopback on the LAN, or break theconnection between the port and the LAN, torelease the selfloop.

Step 3 Cause 2: Two ports of the board are connected through cables or two ports of the board areconnected to the same LAN.1. Check whether two ports of the board are connected through cables or whether two ports

of the board are connected to the same LAN.

If... Then...

The two ports are connected throughcables

Disconnect the cables to release theselfloop.

The two ports are connected to the samenetwork

Break the connection between a port and theLAN to release the selfloop.

----End


A.3.82 ETHOAM_VCG_SELF_LOOP

DescriptionThe ETHOAM_VCG_SELF_LOOP alarm indicates that a VCTRUNK port is looped back whenthe point-to-point Ethernet OAM function is enabled. This alarm occurs when the loopbackdetection function is enabled and the VCTRUNK port receives the OAM protocol packetstransmitted by the port itself or the board where the VCTRUNK port resides.



328

Attribute


Major Environment alarm

Parameters


Name Meaning

Parameter 1 Indicates the loopback type.

l 0x01: The port is self-looped.l 0x02: The board is self-looped.l 0x03-0xff: unknown types.


If the function of automatic shutdown in the case of a selfloop is enabled at the alarmed port,the services at the alarmed port are interrupted. Otherwise, a network storm may occur.

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 Check the alarm on the NMS and determine the type of loopback according to the alarmparameters.

If... Then...



Step 2 Cause 1: The port is self-looped.

1. Release the loopback at the port.

2. Reconfigure the lines connected to the VCTRUNK port and ensure that the port is not self-looped.

Step 3 Cause 2: The board is self-looped.



329

1. Reconfigure the lines connected to the VCTRUNK ports and ensure that the lines connectedto any two VCTRUNK ports on the same board are not interconnected.

----End

Related Information

None.

A.3.83 EX_ETHOAM_CC_LOS

Description

The EX_ETHOAM_CC_LOS is an alarm indicating the loss of periodic connectivity check(CC) packets. This alarm occurs when the sink MEP fails to receive CC packets from the samesource MEP in a period (3.5 transmission periods of CC packets at the source MEP).

Attribute



Parameters


Name Meaning

Parameter 1 to Parameter 4 Indicates the ID of the remote MEP.

Parameter 5 to Parameter 8 Indicates the ID of the local MEP.

Parameter 9, Parameter 10 Indicates the ID of the alarmed port.

l PORT number, Parameter 9 is 0x00.l VCTRUNK number, Parameter 9 is 0x80.


Parameter 13 Indicates the MD level of the local MEP.

Parameter 14 to Parameter 17 Indicates the ID of the remote MEP.

Parameter 18 - Parameter 21 Indicates the ID of the local MEP.



330


A unidirectional connectivity failure occurs in the Ethernet service between two MEPs.

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 carryservices between the two MEPs are correctly connected.

If... Then...

If not Re-connect the cables to rectify the faults on physical links.


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

If... Then...

If not Modify the configuration to ensure consistency at both ends.


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 oreliminate any source that transmits a large amount of invalid data.

----End

Related Information

None.

A.3.84 EX_ETHOAM_MPID_CNFLCT

Description

The EX_ETHOAM_MPID_CNFLCT is an alarm indicating the conflict of MPIDs. This alarmoccurs when two MEPs in one MD have the same maintenance point identity (MPID) and oneMEP receives the packets from the other MEP.



331

Attribute


Major Environment alarm


Name Meaning



l PORT number, Parameter 9 is 0x00.l VCTRUNK number, Parameter 9 is 0x80.


Parameter 9 Indicates the MD level of the local MEP.


Impact on the SystemMPIDs must be unique on a network. When this alarm occurs, the LB and LT functions areabnormal and OAM packets are received incorrectly.

Possible CausesCause 1: At least two MEPs in an MD have the same MPID.

ProcedureStep 1 Cause 1: At least two MEPs in an MD have the same MPID.

1. Check the alarm on the NMS and determine the associated MP ID according to the alarmparameters.

2. Query the information about the MEP. Delete the incorrect MEPs and create MEPs withunique MP IDs.

----End




332

A.3.85 EXT_SYNC_LOS

DescriptionThe EXT_SYNC_LOS is an alarm of the loss of the external clock source.

Attribute



ParametersNone.

Impact on the Systeml When the EXT_SYNC_LOS alarm occurs, if only the external clock source and internal

clock source are configured in the clock source priority list, the NE traces the internal clocksource after the external clock source is lost and enters the free-run state 24 hours later.

l If another valid clock source of higher priority and good quality is configured in the clocksource priority list, however, the clock protection switching occurs.

Possible CausesCause 1: The external clock source is configured in the clock source priority list, but the externalclock source cannot be detected or become invalid.

ProcedureStep 1 Cause 1: The external clock source is configured in the clock source priority list, but the external

clock source cannot be detected or become invalid.1. Check whether the equipment that provides the external clock source is faulty.

If... Then...

The equipment is faulty Rectify the fault.

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

----End




333

A.3.86 EXT_TIME_LOC

Description

The EXT_TIME_LOC is an alarm of the loss of the external time source.

Attribute



Parameters

None.


The time of a local NE cannot be synchronized to the external time device to which the NE'senabled external time port is connected.

Possible Causesl Cause 1: The link at a port is faulty.

l Cause 2: The external time device is faulty.

Procedure

Step 1 Cause 1: The link at a port is faulty.

1. Check cable connections. If cables are incorrectly connected, connect the cables again.

Step 2 Cause 2: The external time device is faulty.

1. Check whether the external time device is faulty.

----End

Related Information

None.

A.3.87 FAN_AGING

Description

The FAN_AGING is an alarm of the aged fan. This alarm occurs when the fan rotates at a speedlower than eighty percent of the nominal speed.



334

Attribute



Parameters


Name Meaning

Parameter 1 Indicates the number of the alarmed fan.


When this alarm occurs, the temperature of the NE is too high and impacts the long-termoperation of the NE.

Possible Causes

Cause 1: The fan is aged.

Procedure

Step 1 Cause 1: The fan is aged.1. Replace the fan.

----End

Related Information

None.

A.3.88 FAN_FAIL

Description

The FAN_FAIL is an alarm indicating that the fan is faulty.

Attribute





335


Name Meaning

Parameter 1 Indicates the number of the fan.

Impact on the SystemWhen the FAN_FAIL alarm occurs, the heat dissipation of the system is affected.

After an alarm is reported, clear it immediately. Otherwise, services may be interrupted orequipment may be damaged.

When a fan is faulty, perform the following operations:

l Replace the faulty fan with one that works properly within a period of 96 hours if theambient temperature ranges from 0°C to 40°C .

l Replace the faulty fan with one that works properly within a period of 24 hours if theambient temperature is higher than 40°C .

When multiple fans are faulty, replace them immediately.

Possible Causesl Cause 1: The board and the backplane are connected improperly.l Cause 2: Fan failure occurs.

Procedure

Step 1 Cause 1: The board and the backplane are connected improperly.1. Remove the fan board. Clean the dust on the fan and reinsert the fan board.

If... Then...




Go to Cause 2.

Step 2 Cause 2: Fan failure occurs.1. Replace the alarmed fan board.

----End




336

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

Attribute



Parameters


Name Meaning


Parameter 2, Parameter 3 Indicate the VCTRUNK number where the alarm occurs.


When 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 alarmed 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 atboth ends of services.



337

If... Then...

The protocols are inconsistent Correct the configuration data.

The protocols are consistent Go to the next step.

2. Check whether the encapsulation parameters are consistent at both ends of services.

If... Then...

The parameters are inconsistent Correct the configuration data.

The parameters are consistent Go to the next step.

Step 2 Cause 2: Service channels have errors.1. Check whether any error alarm or performance event occurs on the line board that carries

the services.

If... Then...

Yes Handle the alarm or performance event.

No Go to the next step.

Step 3 Cause 3: The alarmed board is faulty.1. Replace the alarmed board.

----End

Related Information

None.

A.3.90 FLOW_OVER

Description

The FLOW_OVER is an alarm indicating that the data flow received by the Ethernet port exceedsthe threshold.

Attribute


Minor Service alarm

Parameters




338

Name Meaning

Parameter 1 Indicates the receive or transmit direction in which traffic crosses the specifiedthreshold.

l 0x00: the receive directionl 0x01: the transmit direction

Impact on the SystemWhen the FLOW_OVER alarm occurs, the extra data may be discarded by the port.

Possible Causesl Cause 1: The traffic threshold of the local port is very low.l Cause 2: The opposite end transmits excessive data flow.

Procedure

Step 1 Cause 1: The traffic threshold of the local port is very low.1. Increase the traffic threshold of the local port to a value that is lower than the rate of the

local port.

Step 2 Cause 2: The opposite end transmits excessive data flow.1. Configure the QoS policies at the opposite end to reduce the data flow that the opposite

end transmits.

----End


A.3.91 HARD_BAD

DescriptionThe HARD_BAD is an alarm indicating hardware errors.

Attribute






339


Name Meaning

Parameter 1 to Parameter 3 Indicate the internal faults detected by the board.

Impact on the SystemThe alarmed board fails to work. If the board is configured with the 1+1 protection, protectionswitching may be triggered.

Possible Causesl Cause 1: The board and the backplane are connected improperly.l Cause 2: A certain board is faulty.l Cause 3: The slot is faulty.

Procedure

Step 1 Cause 1: The board and backplane are connected improperly.1. Remove and insert the alarmed board. For details, see 6.1 Removing a Board and 6.2

Inserting a Board. Then, check whether the alarm is cleared.

If... Then...





Step 2 Cause 2: A certain board is faulty.1. Replace the alarmed board, and then check whether the alarm is cleared. For details, see 6

Part Replacement.

If... Then...




Ensure that the slot is normal.

Step 3 Cause 3: The slot is faulty.1. Contact Huawei engineers to handle the faulty slot.

TIPGenerally, the slot becomes faulty due to the broken pin or bent pin. Remove the board, and use atorch to observe whether there is any broken pin or bent pin.

2. If a vacant slot is available, insert the board in the vacant slot and add the board again.Then, the board can work normally.

----End



340


A.3.92 HP_CROSSTR

DescriptionThe HP_CROSSTR is an alarm indicating that the higher order path error crosses the threshold.This alarm occurs when the board detects that the performance event that the higher order patherror crosses the preset threshold.

Attribute


Minor Service alarm


Name Meaning

Parameter 1 Indicates the performance monitoring period:

l 0x01: 15 minutesl 0x02: 24 hours

Parameter 2, Parameter 3 Indicate the ID of a performance event that causes the alarm.

l 0x30: HPBBEl 0x31: HPESl 0x32: HPSESl 0x33: HPFEBBEl 0x34: HPFEESl 0x35: HPFESESl 0x36: HPUASl 0x37: HPCSESl 0x38: HPFECSESl 0x4c: HPFEUAS



341

Impact on the SystemWhen the HP_CROSSTR alarm occurs, a large number of errors occur in the service, and theservice may be interrupted.

Possible CausesCause 1: The higher order path error crosses the preset threshold.

Procedure

Step 1 Cause 1: The higher order path error crosses the preset threshold.1. Check the threshold crossing records to find out the performance event that the higher order

path error crosses the preset threshold. For details, see 8.3.8 Browsing the PerformanceEvent Threshold-Crossing Records.

2. Handle the threshold-crossing performance event.

----End


A.3.93 HP_LOM

DescriptionThe HP_LOM is an alarm indicating the loss of the higher order path multiframe. This alarmoccurs when the board detects that byte H4 is inconsistent with the expected multiframesequence.

Attribute



ParametersNone.

Impact on the SystemWhen the HP_LOM alarm occurs, the service on the alarmed path is interrupted. If the servicesare configured with protection, protection switching may be triggered.

Possible Causesl Cause 1: The transmit unit of the opposite NE is faulty.l Cause 2: The receive unit of the local NE is faulty.



342

ProcedureStep 1 Cause 1: The transmit unit of the opposite NE is faulty.

1. Replace the board where the line unit is located on the opposite NE. Then, checkwhether the alarm is cleared.

If... Then...


The alarm persists Replace the system control, cross-connect, and timing boardon the opposite NE.

Step 2 Cause 2: The receive unit of the local NE is faulty.1. Replace the alarmed board.

----End


A.3.94 HP_RDI

DescriptionThe HP_RDI is an alarm indicating the higher order path remote receive failure. This alarmoccurs when the board detects that bit 5 of byte G1 is 1.

Attribute



ParametersNone.

Impact on the SystemWhen the HP_RDI alarm occurs, the service on the local NE is not affected. The service receivedby the opposite NE, however, is interrupted.

Possible CausesCause 1: The local NE detects the message that is returned by the opposite NE and indicates thehigher order path remote receive failure.

ProcedureStep 1 Cause 1: The local NE detects the message that is returned by the opposite NE and indicates the

higher order path remote receive failure.



343

1. Clear the alarms such as HP_LOM and B3_EXC that the AU-4 path reports on the oppositeNE.

----End

Related Information

None.

A.3.95 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 G1 take a value from 1 to 8.

Attribute


Warning Service alarm

Parameters

None.


The service on the local site is not affected. The service received by the opposite station, however,has errors.

Possible Causes

Cause 1: The local NE detects the message that is returned by the opposite NE and indicates thehigher order path remote errors.

Procedure

Step 1 Cause 1: The local NE detects the message that is returned by the opposite NE and indicates thehigher order path remote receive failure.1. Handle the HP_BBE performance event that the AU-4 path reports on the opposite NE.

----End

Related Information

None.

A.3.96 HP_SLM



344

Description

The HP_SLM is an alarm indicating the lower order path label mismatch. This alarm occurswhen the board detects the C2 byte mismatch.

Attribute



Parameters

None.


None.

Possible Causesl Cause 1: The C2 byte received by the local NE does not match with the C2 byte transmitted

by the remote NE.

l Cause 2: Configuration data is incorrect.

Procedure

Step 1 Cause 1: The C2 byte received by the local NE does not match with the C2 byte transmitted bythe remote NE.

1. Configure the same service type at the source and sink of the AU-4 path. For details, seeConfiguring Overhead Bytes.

Step 2 Cause 2: Configuration data is incorrect.

1. If the alarmed port is the SDH port that is interconnected with the ATM/Ethernet equipment,configure the service as VC-4 pass-through service. For details, see Creating Cross-Connections of SNCP Services.

----End

Related Information

None.

A.3.97 HP_TIM

Description

The HP_TIM is an alarm indicating the higher order path trace identifier mismatch. This alarmoccurs when the board detects the J1 byte mismatch.



345

Attribute



ParametersNone.

Impact on the SystemIf the service is configured with the protection that considers the HP_TIM alarm as a triggercondition, the protection switching is triggered.

Possible Causesl Cause 1: The receivable J1 byte on the local NE does not match with the J1 byte transmitted

on the opposite NE.l Cause 2: Configuration data is incorrect.

Procedure

Step 1 Cause 1: The receivable J1 byte on the local NE does not match with the J1 byte transmitted onthe opposite NE.1. Disable the receivable J1 byte on the local NE or set the receivable J1 byte on the local NE

to the same as the transmitted J1 byte on the opposite NE. For details, see ConfiguringVC-4 POHs.

Step 2 Cause 2: Configuration data is incorrect.1. If the alarmed port is the SDH port that is interconnected with the ATM/Ethernet equipment,

configure the service as VC-4 pass-through service. For details, see Creating Cross-Connections of SNCP Services or Creating the Cross-Connections of Point-to-PointServices.

If... Then...

The alarm is cleared after the configurationis changed


The alarm persists after the configurationis changed


2. Check whether the cross-connections are configured correctly at the intermediate nodeswhere the service travels. If not, reconfigure the cross-connections. For details, see CreatingCross-Connections of SNCP Services or Creating the Cross-Connections of Point-to-PointServices.

----End




346

A.3.98 HP_UNEQ

Description

The HP_UNEQ is an alarm indicating the unequipped higher order path. This alarm occurs whenthe board detects that the C2 byte is 0.

Attribute



Parameters

None.


When the HP_UNEQ alarm occurs, the service in the alarmed AU-4 path is unavailable. If theservice is configured with the protection that considers the alarm as a trigger condition, theprotection switching is triggered.

Possible Causesl Cause 1: The line port at the local NE is configured with services, but the corresponding

line port at the opposite NE is not configured with services.

l Cause 2: Byte C2 is set to 0 at the opposite NE.

Procedure

Step 1 Cause 1: The line port at the local NE is configured with services, but the corresponding lineport at the opposite NE is not configured with services.

1. Configure line services on the opposite NE. For details, see Creating Cross-Connectionsof SNCP Services or Creating the Cross-Connections of Point-to-Point Services.

Step 2 Cause 2: Byte C2 is set to 0 at the opposite NE.

1. Change the setting of byte C2. For details, see Configuring VC-4 POHs.

----End

Related Information

None.

A.3.99 HPAD_CROSSTR



347

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




l 0xaa: TUPJCHIGHl 0xab: TUPJCLOWl 0xac: TUPJCNEW


When the HPAD_CROSSTR alarm occurs, bit errors may occur in the service.

Possible Causes

Cause 1: The performance event of TU pointer justification crosses the preset threshold.

Procedure

Step 1 Cause 1: The performance event of TU pointer justification crosses the preset threshold.1. Check the threshold crossing records to find out the performance event of TU pointer

justification that crosses the preset threshold. For details, see 8.3.8 Browsing thePerformance Event Threshold-Crossing Records.


----End



348


A.3.100 IF_CABLE_OPEN

DescriptionThe IF_CABLE_OPEN is an alarm indicating that the IF cable is open.

Attribute



ParametersNone.

Impact on the SystemWhen the IF_CABLE_OPEN alarm occurs, the service on the alarmed IF port is interrupted.

Possible Causesl Cause 1: The IF cable is loose or faulty.l Cause 2: The IF port on the IF board is damaged.l Cause 3: The power module of the ODU is faulty.

ProcedureStep 1 Cause 1: The IF cable is loose or faulty.

1. Check whether the connector of the IF cable is loose or whether the connector is madeproperly.

The connectors to be checked include the connector between the IF fiber jumper and theIF board, the connector between the IF fiber jumper and the IF cable, and the connectorbetween the IF cable and the ODU.

If... Then...

The connector is loose Connect the connector tightly.

The connector is made improperly See the Installation Reference and make newconnectors for the IF cable.

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.

If... Then...

The cable does not meet the requirement Replace the cable with a qualified one.

The cable meets the requirement Go to Cause 2 or Cause 3.



349

Step 2 Cause 2: The IF port on the IF board is damaged.1. Replace the alarmed IF board.

Step 3 Cause 3: The power module of the ODU is faulty.1. Replace the ODU connected to the alarmed IF board.

----End

Related InformationNOTEWhen rectifying the faults of the IF cable, IF port, and ODU, you must turn off the ODU before theoperation. You can turn on the ODU only after the operation is complete.

A.3.101 IF_INPWR_ABN

DescriptionThe IF_INPWR_ABN is an alarm indicating that the power supplied by an IF board to an ODUis abnormal.

Attribute




Name Meaning

Parameter 1 l 0x01: Indicates that the input power of the ODU is too high.l 0x02: Indicates that the input power of the ODU is too low.

Impact on the SystemWhen this alarm occurs, the services on the ODU are interrupted. If 1+1 protection is configured,this alarm also triggers 1+1 HSB switching.

Possible Causesl Cause 1: The IF board is faulty.l Cause 2: The IF cable is faulty.



350

l Cause 3: The ODU is faulty.

l Cause 4: The IF fiber jumper and the IF board are connected incorrectly.

Procedure

Step 1 Cause 1: The IF board is faulty.

1. Replace the IF board connected to the alarmed ODU.

Step 2 Cause 2: The IF cable is faulty.

1. Check whether the connectors of the IF cable are loose or prepared incorrectly.

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

Any of the connectors is loose Connect the connector tightly.

Any of the connectors is preparedincorrectly

See the Installation Reference and makenew connectors for the IF cable.

All connectors are normal Go to the next step.

2. Check whether the surface of the IF fiber jumper and the IF cable is damaged or deformed,and test the connectivity between the IF fiber jumper and the IF cable. For details, seeTesting the Connectivity of the IF Cable.

If... Then...

The IF cable is below standard Replace the IF cable.

The IF cable is up to standard The IF board or ODU may be faulty.

Step 3 Cause 3: The ODU is faulty.

1. Replace the alarmed ODU.

Step 4 Cause 4: The IF fiber jumper and the IF board are connected incorrectly.

1. Connect the IF fiber jumper and the IF board correctly.

----End

Related Information

The logical slot ID of the ODU is obtained by adding 20 to the slot ID of the IF board connectedto the ODU.

A.3.102 IF_MODE_UNSUPPORTED



351

Description

The IF_MODE_UNSUPPORTED is an alarm indicating that the configured IF working modeis not supported. This alarm occurs if the board is not loaded with the FPGA file that supportsthe configured IF working mode.

Attribute



Parameters


Name Meaning

Parameter 1 Indicates the ID of the FPGA file that is loaded to the board.

l 0x01 indicates that FPGA file 250 is loaded.l 0x02 indicates that FPGA file 002 is loaded.


When the IF_MODE_UNSUPPORTED alarm occurs, the service on the alarmed IF port isinterrupted.

Possible Causes

Cause 1: The board is not loaded with the FPGA file that supports the configured IF workingmode, or the FPGA file that supports the configured IF working mode is damaged.

Procedure

l Cause 1: The board is not loaded with the FPGA file that supports the configured IF workingmode, or the FPGA file that supports the configured IF working mode is damaged.

1. Contact Huawei engineers to upgrade the software and the FPGA file.

----End

Related Information

None.



352

A.3.103 IMA_GROUP_LE_DOWN

Description

The IMA_GROUP_LE_DOWN is an alarm indicating that the IMA group at the local end fails.This alarm occurs when the IMA group is in non-Active state on the local NE or when theactivated links of the IMA group on the local NE are less than the minimum number.

Attribute



Parameters

None.


When this alarm occurs, all links of the alarmed IMA group are unavailable.

Possible Causesl Cause 1: The IMA links on the local NE are faulty.

l Cause 2: The activated links of the IMA group on the local NE are less than the minimumnumber.

Procedure

Step 1 Cause 1: The IMA links on the local NE are faulty.

1. Check whether the T_ALOS alarm is reported at the E1 port. If yes, clear this alarm.

2. Check whether the IMA_GROUP_RE_DOWN alarm is cleared. If the alarm persists,configure the related services at other ports or replace the related board.

Step 2 Cause 2: The activated links of the IMA group on the local NE are less than the minimum number.

If... Then...

The ALM_IMA_LIF alarm occurs Clear the ALM_IMA_LIF alarm immediately.Activate the links of the IMA group on the local NE.

No other alarm occurs Reconfigure the links of the IMA group on the localNE.

When the number of activated links of the IMA group reaches the minimum number, the alarmclears automatically.

----End



353

Related Information

None.

A.3.104 IMA_GROUP_RE_DOWN

Description

The IMA_GROUP_RE_DOWN is an alarm indicating that the IMA group at the remote endfails. This alarm occurs when the IMA group is in non-Active state on the remote NE or whenthe activated links of the IMA group on the remote NE are less than the minimum number.

Attribute



Parameters

None.


When this alarm occurs, the ports of the IMA group are congested and services have bit errors.

Possible Causesl Cause 1: The IMA links on the remote NE are faulty.

l Cause 2: The activated links of the IMA group on the remote NE are less than the minimumnumber.

Procedure

Step 1 Cause 1: The IMA links on the remote NE are faulty.1. Check whether the T_ALOS alarm is reported at the E1 port. If yes, clear this alarm.2. Check whether the IMA_GROUP_RE_DOWN alarm is cleared. If the alarm persists,

configure the related services at other ports or replace the related board.

Step 2 Cause 2: The activated links of the IMA group on the remote NE are less than the minimumnumber.

If... Then...

The ALM_IMA_LIF alarm occurs Clear the ALM_IMA_LIF alarm immediately.Activate the links of the IMA group on the opposite NE.

No other alarm occurs Reconfigure the links of the IMA group on the remoteNE.



354

When the number of activated links of the IMA group reaches the minimum number, the alarmclears automatically.

----End


A.3.105 IMA_TXCLK_MISMATCH

DescriptionThe IMA_TXCLK_MISMATCH is an alarm indicating that the transmit clock modes of an IMAgroup are inconsistent at the two ends.

Attribute



ParametersNone.

Impact on the SystemThe IMA_TXCLK_MISMATCH alarm may cause loss of ATM cells.

Possible CausesCause 1: The transmit clock modes of an IMA group are inconsistent at the two ends.

Procedure

Step 1 Cause 1: The transmit clock modes of an IMA group are inconsistent at the two ends.1. Check the alarm information and determine the NE, board, and ATM trunk related to the

alarm.2. Modify the Clock Mode parameter of the alarmed ATM trunk to the same value as that of

the opposite end. Then, check whether the alarm is cleared.

----End

Related InformationThe Clock Mode parameter can be set to two modes.

l CTC mode: Common transmit clock mode. In CTC mode, all transmit clocks of the linksin an IMA group are from the same clock source.



355

l ITC mode: Independent transmit clock mode. In ITC mode, the transmit clocks of the linksin an IMA group are from different clock sources. When the IMA group is set to the lineclock mode, the ITC mode is recommended.

A.3.106 IN_PWR_ABN

Description

The IN_PWR_ABN is an alarm indicating that the input optical power is abnormal.

Attribute



Parameters

None.


When the IN_PWR_ABN alarm occurs, the service at the alarmed optical interface has errorsand even becomes unavailable.

Possible Causesl Cause 1: The transmit power of the opposite NE is over high or over low.

l Cause 2: The model of the selected optical module is incorrect.

l Cause 3: The optical module at the receive end is faulty.

l Cause 4: The fiber performance degrades.

Procedure

Step 1 Cause 1: The transmit power of the opposite NE is over high or over low.

1. Browse current performance events, and query the performance event of the transmitoptical power on the opposite NE.

If... Then...

The transmit optical power does not meetthe requirement

Replace the optical module.

The transmit optical power is over high Add a proper attenuator to reduce thereceive optical power.

Step 2 Cause 2: The model of the selected optical module is incorrect.

1. Query the board manufacturing information report, and check whether the models ofthe SFP optical modules used at both ends are correct.



356

If... Then...

The models are incorrect Replace the optical module.

The models are correct Go to Cause 3.

Step 3 Cause 3: The optical module at the receive end is faulty.1. Use the optical power meter to test the receive optical power, and check whether the receive

optical power meets the requirement. If yes, contact Huawei engineers to replace the opticalmodule.

Step 4 Cause 4: The fiber performance degrades.

If... Then...

The connector of the fiber jumper is dirty Clean fiber connectors.

The connector or fiber is damaged Insert the connector properly or replace thedamaged fiber jumper.

----End

Related InformationThe following table describes the meanings of the parameters in the IN_PWR_ABN alarmreported by the EMS6.

Name Meaning

Parameter 1 Indicates the port number.

Parameter 2, Parameter 3 The value of Parameter 2 is always 0x00, andthe value of Parameter 3 is always 0x01. Thetwo parameters indicate the path ID.

Parameter 4, Parameter 5 Reserved. The values are always 0xFF.

A.3.107 IN_PWR_HIGH

DescriptionThe IN_PWR_HIGH is an alarm indicating that the input optical power is over high.

Attribute



ParametersNone.



357


When the IN_PWR_HIGH alarm occurs, the service at the alarmed optical interface has errors.

Possible Causesl Cause 1: The transmit power of the opposite NE is over high.l Cause 2: The model of the selected optical module is incorrect.l Cause 3: The optical module at the receive end is faulty.

Procedure

Step 1 Cause 1: The transmit power of the opposite site is over high.1. Browse current performance events, and query the performance event of the transmit

optical power on the opposite NE.

If... Then...


Contact Huawei engineers to replace theoptical module.

The transmit optical power meets therequirement

Add a proper attenuator to reduce thereceive optical power.

Step 2 Cause 2: The model of the selected optical module is incorrect.1. Query the board manufacturing information report, and check whether the models of

the SFP optical modules used at both ends are correct.

If... Then...

The models are incorrect Contact Huawei engineers to replace the optical module.



optical power meets the requirement. If yes, contact Huawei engineers to replace the opticalmodule.

----End

Related Information

The optical power threshold set for the IN_PWR_HIGH alarm is lower than the overload point.

SDH Interface Performance.

A.3.108 IN_PWR_LOW

Description

The IN_PWR_LOW is an alarm indicating that the input optical power is over low.



358

Attribute



ParametersNone.

Impact on the SystemWhen the IN_PWR_LOW alarm occurs, the service at the alarmed optical interface has errors.

Possible Causesl Cause 1: The transmit power of the opposite NE is over low.l Cause 2: The model of the selected optical module is incorrect.l Cause 3: The optical module at the receive end is faulty.l Cause 4: The fiber performance degrades.

Procedure

Step 1 Cause 1: The transmit power of the opposite NE is over low.1. Browse current performance events, and query the performance event of the transmit

optical power on the opposite NE.

If... Then...



The transmit optical power meets therequirement

Go to Cause 2.

Step 2 Cause 2: The model of the selected optical module is incorrect.1. Query the board manufacturing information report, and check whether the models of

the SFP optical modules used at both ends are correct.

If... Then...

The models are incorrect Contact Huawei engineers to replace the optical module.



optical power meets the requirement.

If... Then...

The receive optical power meets therequirement




359

If... Then...

The receive optical power does not meet therequirement

Go to Cause 4.

Step 4 Cause 4: The fiber performance degrades.1. Clean fiber connectors and adapters.

If... Then...

The alarm is cleared after the connector iscleaned

The fault is rectified. End the alarm handling.

The alarm persists after the connector iscleaned

Replace the fiber.

----End

Related Information

The optical power threshold set for the IN_PWR_LOW alarm is higher than the sensitivity point.

SDH Interface Performance.

A.3.109 INTEMP_SENSOR_FAIL

Description

The INTEMP_SENSOR_FAILL is an alarm indicating that the air inlet temperature sensor ofthe cabinet fails.

Attribute



Parameters

None.


The air inlet temperature data of the TCU cannot be collected.

Possible Causesl Cause 1: The air inlet temperature sensor is faulty.l Cause 2: The control board of the cabinet is faulty.l Cause 3: Cables are misconnected or damaged.l Cause 4: The air inlet temperature sensor is not installed.



360

Procedure

Step 1 Cause 1: The air inlet temperature sensor is faulty.1. Replace the air inlet temperature sensor.2. Then, check whether the alarm clears.

If... Then...




If... Then...




Step 4 Cause 4: The air inlet temperature sensor is not installed.1. Install the air inlet temperature sensor.

----End

Related Information

None.

A.3.110 J0_MM

Description

The J0_MM is an alarm indicating the trace identifier mismatch. This alarm occurs when theboard detects the J0 byte mismatch.

Attribute



Parameters

None.



361

Impact on the SystemNone.

Possible CausesCause 1: The receivable J0 byte on the local NE does not match the transmitted J0 byte on theopposite NE.

Procedure

Step 1 Cause 1: The receivable J0 byte on the local NE does not match the transmitted J0 byte on theopposite NE.1. Disable the receivable J0 byte on the local NE. For details, see Configuring RSOHs.

----End


A.3.111 K1_K2_M

DescriptionThe K1_K2_M is an alarm indicating the K1/K2 byte mismatch. This alarm occurs when theboard detects inconsistent channel numbers that the transmitted K1 byte (bits 5-8) and thereceived K2 byte (bits 1-4) indicate.

Attribute




Name Meaning

Parameter 1 Indicates the protection group type.l 0x01: linear MS protection.l 0x02: ring MS protection.




362


When the K1_K2_M alarm occurs, the MSP protocol may fail and therefore the protectionswitching may fail.

Possible Causesl Cause 1: The switching modes configured at both ends are single-ended switching and dual-

ended switching separately.

l Cause 2: The fiber connection is incorrect.


Procedure

Step 1 Cause 1: The switching modes configured at both ends are single-ended switching and dual-ended switching separately.

1. Check whether the switching modes at both ends are the same.

If... Then...

The switching modes are different Configure the switching modes as the same.

The switching modes are the same Go to Cause 2.

Step 2 Cause 2: The fiber connection is incorrect.

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

If... Then...

The fiber connection is incorrect Connect the fiber properly.

The connection is correct Go to Cause 3.


1. Replace the board where the line unit is located on the opposite NE. Then, checkwhether the alarm is cleared.

If... Then...



----End

Related Information

None.

A.3.112 K2_M



363

Description

The K2_M is an alarm indicating the K2 byte mismatch. This alarm occurs when the boarddetects that the protection mode indicated by the received K2 (bit 5) is different from theprotection mode of the NE.

Attribute



Parameters


Name Meaning

Parameter 1 Indicates the protection group type.l 0x01: linear MS protection.l 0x02: ring MS protection.



When the K2_M alarm occurs, the MSP protocol may fail and therefore the protection switchingmay fail.

Possible Causesl Cause 1: Two NEs of the linear MSP group are configured with different protection modes

(1+1 or 1:N).

l Cause 2: The MSP protocol is stopped when the protection switching occurs.

l Cause 3: The fiber connection is incorrect.


Procedure

Step 1 Cause 1: Two NEs of the linear MSP group are configured with different protection modes (1+1 or 1:N).

1. Query the status of the linear MSP, and check whether two NEs of the linear MSP groupare configured with different protection modes (1+1 or 1:N).



364

If... Then...

The protection modes are different Configure the protection modes as the same.

The protection modes are the same Go to Cause 2.

Step 2 Cause 2: The MSP protocol is stopped when the protection switching occurs.1. Query the status of the linear MSP, and check whether the MSP protocol is stopped on the

opposite NE.

If... Then...

The protocol is stopped Restart the MSP protocol on the opposite NE. For details, seeStarting/Stopping the Linear MSP Protocol.

The protocol is running Go to Cause 3.

Step 3 Cause 3: The fiber connection is incorrect.1. Check whether the fiber connection is correct. For example, the fiber at the receive or

transmit port may be incorrectly connected, or disconnected.

If... Then...

The connection is incorrect Connect the fiber properly


Step 4 Cause 4: A certain board is faulty.1. Replace the board where the line unit is located on the opposite NE. Then, check

whether the alarm is cleared.

If... Then...



----End

Related Information

None.

A.3.113 LAG_BWMM

Description

LAG_BWMM is an alarm indicating the bandwidth inconsistency in the LAG group.

Attribute





365

ParametersNone.

Impact on the SystemFor a LAG group in load-sharing mode, data services may be lost.

Possible CausesCause 1: In the LAG group, the license capacities of the ports differ from each other.

Procedure

Step 1 Cause 1: In the LAG group, the license capacities of the ports differ from each other.1. Query the license capacities of the ports of the LAG group by using the NMS.2. If the license capacities of the ports differ from each other, reload a license file of an

appropriate capacity.

----End


A.3.114 LAG_DOWN

DescriptionThe LAG_DOWN is an alarm indicating that the link aggregation group (LAG) is unavailable.This alarm occurs when the LAG does not have activated members.

Attribute



ParametersNone.

Impact on the SystemWhen the LAG_DOWN alarm occurs, the service at the member port of the LAG is interrupted.

Possible CausesCause 1: All the member ports of the aggregation group are invalid for the same causes as theLAG_MEMBER_DOWN alarm.



366

Procedure

Step 1 Cause 1: All the member ports of the LAG are invalid for the same causes as theLAG_MEMBER_DOWN alarm.

1. Determine the alarmed port according to the alarm parameter.

2. Rectify the fault at each member port according to the description ofLAG_MEMBER_DOWN.

----End

Related Information

None.

A.3.115 LAG_MEMBER_DOWN

Description

The LAG_MEMBER_DOWN is an alarm indicating that a member port of a link aggregationgroup (LAG) is unavailable. This alarm occurs when a member port of an LAG can neither beactivated nor function as a protection port.

Attribute



Parameters


Name Meaning

Parameter 1, Parameter 2 Indicates the slot ID of the alarmed board.

Parameter 3 Indicates the ID of the alarmed subboard. The value is always 0xff.


Parameter 6 Indicates the cause that makes the port unavailable.l 0x01: The port link is faulty or disabled.l 0x02: The port fails to receive the LACP packets.l 0x03: The port works in half-duplex mode.l 0x04: The port is self-looped.



367


The port in the LAG cannot share the service load, and the port does not transmit or receive anyservices.

Possible Causesl Cause 1: The port link is faulty or disabled.l Cause 2: The port receives no LACP packets.l Cause 3: The port works in half-duplex mode or not in Auto-Negotiation mode.l Cause 4: The port is self-looped.

Procedure

Step 1 Determine the alarmed port and the cause of the alarm according to the alarm parameters.

If... Then...

The value of Parameter 4 is 0x01 Perform the operations described in step Step 2.




Step 2 Cause 1: The port link is faulty or disabled.1. On the NMS, check whether the port in the LAG is enabled. For details, see Querying the

Protocol Information of the LAG.

If... Then...

The port is not enabled Enable the port in the LAG.

The port is enabled Go to the next step.

2. Check the link status of all ports and check whether the ETH_LOS alarm is reported.

If... Then...

The alarm is reported Clear the ETH_LOS alarm immediately and rectify thefault of the port link.

The alarm is not reported Go to Cause 2.

Step 3 Cause 2: The port receives no LACP packets.1. Check whether the local port and the remote port transmit the LACP packets. For details,

see Querying the Protocol Information of the LAG. If the LACP packets are not transmitted,configure the ports at two ends to ensure that the packets can be normally transmitted.

Step 4 Cause 3: The port works in half-duplex mode or not in Auto-Negotiation mode.1. On the NMS, check whether the port in the LAG works in half-duplex mode. For details,

see Querying the Protocol Information of the LAG. If the port works in half-duplex mode,change the working mode of the port into full-duplex.

2. On the NMS, change the working mode of the port into full-duplex and Auto-Negotiation.



368

Step 5 Cause 4: The port is self-looped.

1. Check whether the port is self-looped. For details, see 8.15 Querying the Attributes ofan Ethernet Port. If the port is self-looped, release the selfloop. For details, see 8.5.4Setting a Loopback for the Packet-plane Ethernet Interface Board.

----End

Related Information

None.

A.3.116 LAG_PORT_FAIL

Description

The LAG_PORT_FAIL is an alarm indicating that a port in the LAG fails. When a port in theLAG is unavailable, the LAG_PORT_FAIL alarm is reported.

Attribute



Parameters


Name Meaning

Parameter 1 Indicates the number of the IP port.


Parameter 4 Indicates the cause of the protection failure.

l 0x01: The link of the port is faulty or fails.l 0x02: The port is in half-duplex mode.l 0x03: The port fails to receive the LACP packets.l 0x04: The port detects the selfloop.l 0x05: Other unknown reasons.

Parameter 5 The value is always 0xff.



369


The port in the LAG cannot share the service load, and 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 the LCAP packets.

l Cause 4: The port detects a selfloop.

l Cause 5: other unknown reasons

Procedure

Step 1 Determine the port where the alarm occurs and the alarm cause according to 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. For details, see Setting theGeneral Attributes of Ethernet Ports.

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. For details, see Settingthe General Attributes of Ethernet Ports.

Step 4 Cause 3: The port fails to receive the LCAP packets.

1. On the NMS, check whether the LAG group is properly configured on the opposite end.For details, see Querying the Protocol Information of the LAG.

If... Then...

The LAG group is not properly configured Reconfigure the LAG group.

The LAG group is properly configured Go to the next step.



370

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. For details, see Querying the Protocol Information of the LAG.

Step 5 Cause 4: The port detects a selfloop.1. Release the selfloop of the port with reference to Enabling Self-Loop Detection.

Step 6 Cause 5: other unknown reasons1. Contact Huawei engineers.

----End


A.3.117 LAG_VC_PORT_FAIL

DescriptionThe LAG_VC_PORT_FAIL is an alarm indicating that a VCG port in the LAG fails. When theVCTRUNK is unavailable, the alarm is reported.

Attribute




Name Meaning


Parameter 2, Parameter 3 Indicate the number of the faulty VCG port in the LAG. Parameter2 indicates the most significant bits and Parameter 3 indicates theleast significant bits.



371

Name Meaning

Parameter 4 Indicates the cause of the protection failure.

l 0x01: The link of the port is faulty or fails.l 0x03: The port fails to receive the LACP packets.l 0x04: The link of the port is configured into a loop.l 0x05: other unknown reasons.


Impact on the SystemThe 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 LCAP packets.l Cause 3: The port detects a selfloop.l Cause 4: other unknown reasons

Procedure

Step 1 Determine the port where the alarm occurs and the alarm cause according to 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 VCG port. If any link is faulty, rectify the fault.

Step 3 Cause 2: The port fails to receive the LCAP 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 selfloop.



372

1. Release the selfloop of the port.

Step 5 Cause 4: other unknown reasons1. Contact Huawei engineers.

----End


A.3.118 LAN_LOC

DescriptionThe LAN_LOC is an alarm indicating the Ethernet communication failure.

Attribute




Name Meaning

Parameter 1 Indicates the network port ID. For example, 0x01 indicates networkport 1 and 0x02 indicates network port 2.

Parameter 2, Parameter 3 Indicates the number of the path on which the alarm is reported.

Parameter 2 indicates the most significant bits and the value isalways 0x00. Parameter 3 indicates the least significant bits and thevalue is always 0x01.

Impact on the SystemWhen the alarm is reported, the communication of the network port is interrupted. As a result,the NE is out of control. The existing services of the NE, however, are not affected.

Possible Causesl Cause 1: The cable is not connected to the network port, or the cable is faulty.



373

l Cause 2: The network port is faulty.l Cause 3: The system control, switching, and timing board is faulty.

Procedure

Step 1 View the alarm on the NMS. Determine the network port ID according to the alarm parameter1.

Step 2 Cause 1: The cable is not connected to the network port, or the cable is faulty.1. Check whether the cable of the network port is loose or no cable is connected. Properly

connect the NMS to the network port. The LINK indicator is in green.

Step 3 Cause 2: The network port is faulty.1. Replace the faulty board. For details, see 6.9 Replacing the System Control, Switch and

Timing Board.

Step 4 Cause 3: The system control, switching, and timing board is faulty.1. Replace the system control, switching, and timing board. For details, see 6.9 Replacing

the System Control, Switch and Timing Board.

----End


A.3.119 LASER_CLOSED

DescriptionThe LASER_CLOSED is an alarm indicating that the laser is shut down. This alarm occurs whenthe laser is shut down by using the NMS.

Attribute



ParametersNone.

Impact on the SystemWhen the LASER_CLOSED alarm occurs, the optical interface fails to carry services.

Possible CausesCause 1: The laser on the local NE is shut down by using the NMS.



374

Procedure

Step 1 Cause 1: The laser on the local NE is shut down by using the NMS.1. Find out the cause of shutting down the laser and start up the laser as soon as possible.

----End

Related Information

None.

A.3.120 LASER_MOD_ERR

Description

The LASER_MOD_ERR is an alarm indicating that the type of the pluggable optical moduleon the board does not match the type of the optical interface.

Attribute



Parameters

None.


When the LASER_MOD_ERR alarm occurs, the performance of the optical interface degradesand serious degradation even causes service interruption.

Possible Causesl Cause 1: The optical module installed at the optical interface does not match the rate of the

optical interface.

l Cause 2: The small form-factor pluggable (SFP) module does not match the interface type.

l Cause 3: 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 the

optical interface. For details, see 8.4.2 Querying the Board Manufacturing InformationReport .



375

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 SFP module does not match the interface type.1. Replace the existing SFP module with a proper SFP module.

Step 3 Cause 3: The optical module is faulty.1. Replace the faulty optical module.

If... Then...

The alarm is cleared after the optical module is replaced End the alarm handling.

The alarm persists after the optical module is replaced Go to Cause 3.

Step 4 Cause 4: A certain board is faulty.1. Replace the alarmed board.

----End

Related Information

None.

A.3.121 LASER_MOD_ERR_EX

Description

The LASER_MOD_ERR is an alarm indicating that the type of the pluggable optical moduleon the board does not match the type of the optical interface.

Attribute



Parameters

None.


When the LASER_MOD_ERR_EX alarm occurs, the performance of the optical interfacedegrades and serious degradation even causes service interruption.



376

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 small form-factor pluggable (SFP) module does not match the interface type.l Cause 3: The optical module is faulty.l Cause 4: A certain board 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 the

optical interface. For details, see 8.4.2 Querying the Board Manufacturing InformationReport .

If... Then...

The optical module does not match therate of the optical interface

Contact Huawei engineers to replace theoptical module with one that matches therate of the optical interface.

The optical module matches the rate ofthe optical interface

Go to Cause 2.

Step 2 Cause 2: The SFP module does not match the interface type.1. Replace the existing SFP module with a proper SFP module.

Step 3 Cause 3: The optical module is faulty.1. Replace the faulty optical module.

If... Then...

The alarm is cleared after the optical module is replaced End the alarm handling.

The alarm persists after the optical module is replaced Go to Cause 3.


----End

Related Information

None.

A.3.122 LASER_SHUT

Description

The LASER_SHUT is an alarm indicating that the laser is shut down. This alarm occurs whenthe laser is shut down by using the NMS.



377

Attribute



ParametersNone.

Impact on the SystemWhen the laser_shut alarm occurs, the optical interface fails to carry services.

Possible CausesCause 1: The laser on the local NE is shut down by using the NMS.

Procedure

Step 1 Cause 1: The laser on the local NE is shut down by using the NMS.1. Find out the cause of shutting down the laser and start up the laser as soon as possible.

----End


A.3.123 LCAS_FOPR

DescriptionThe LCAS_FOPR is an alarm indicating that the LCAS protocol in the receive direction fails.This alarm occurs if the receive unit of the LCAS module of a board detects an abnormal statein which the LCAS might fail to negotiate or cannot negotiate correctly.

Attribute






378

Name Meaning



Impact on the SystemThe 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 enabling state and the LCAS parameters are the same at both

ends of the link.

If... Then...

The settings of the LCAS protocols arenot consistent

Properly enable the LCAS protocols at bothends.

The settings of the LCAS protocols atboth ends are consistent

Go to Cause 2.

2. Check whether configurations of the local and opposite NEs are correct. For example, checkwhether a VCG on one NE is connected to multiple VCGs on 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 normal Go to the next step.

2. Restart the LCAS protocols at both ends. Then, check whether the alarm clears.

If... Then...




379

If... Then...


----End

Related Information

None.

A.3.124 LCAS_FOPT

Description

The LCAS_FOPT is an alarm indicating that the LCAS protocol in the transmit direction fails.This alarm occurs if the transmit unit of the LCAS module of a board detects an abnormal statein which the LCAS might fail to negotiate or cannot negotiate correctly.

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.



380

Procedure

Step 1 Cause 1: Configuration data of the LCAS protocol is incorrect.1. Check whether the LCAS enabling state and the LCAS parameters are the same at both

ends of the link.

If... Then...

The settings of the LCAS protocols arenot consistent

Properly enable the LCAS protocols at bothends.

The settings of the LCAS protocol at bothends are consistent

Go to Cause 2.

2. Check whether configurations of the local and opposite NEs are correct. For example, checkwhether a VCG on one NE is connected to multiple VCGs on 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 normal Go to the next step.

2. Restart the LCAS protocols at both ends. Then, check whether the alarm clears.

If... Then...



----End


A.3.125 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 function enabled is lessthan the preset number but is not zero.



381

Attribute


Minor Service alarm

Parameters


Name Meaning




The 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 the transmit and the receive directions at the local siteare configured with the same number of physical paths and timeslots.

If... Then...

The sink and source VCTRUNKs arebound with different number of physicalpaths or bound with different timeslots

Correct the configuration data. For details,see Dynamically Increasing/Decreasing theVCTRUNK Bandwidth.


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.



382

If... Then...

Any of the preceding alarms occurs Clear the alarm immediately.

No alarm occurs Go to Cause 3.

Step 3 Cause 3: Some paths in the receive direction of the local site are faulty.


----End

Related Information

None.

A.3.126 LCAS_PLCT

Description

The 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 function enabled is lessthan the preset number but is not zero.

Attribute


Minor Service alarm

Parameters


Name Meaning


Parameter 2, Parameter 3 Indicate the ID of the alarmed VCTRUNK. For example, 0x00 0x01indicate that the alarm is reported in VCTRUN 1.


The available transmit bandwidth of Ethernet services is less than the preset bandwidth. Whenthe transmitted services are more than the available transmit bandwidth, packet loss occurs.



383



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


1. Check whether the sink and source VCTRUNKs are bound with the same number ofphysical paths or the same timeslots.

If... Then...

The sink and source VCTRUNKs arebound with different number of physicalpaths or different timeslots


The sink and source VCTRUNKs arebound with the same number of physicalpaths or 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 occurs 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.3.127 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.



384

Attribute


Major Service alarm


Name Meaning


Parameter 2, Parameter 3 Indicates the ID of the alarmed VCTRUNK. For example, 0x000x01 indicate that the alarm is reported in VCTRUN 1.

Impact on the SystemThere is no available bandwidth in the receive direction, and the Ethernet services are 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 the transmit and the receive directions at the local site

are configured with the same number of physical paths and timeslots.

If... Then...



The sink and source VCTRUNKs arebound with the same number of physicalpaths or the same 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.



385

If... Then...


No alarm occurs Go to Cause 3.

Step 3 Cause 3: Some paths in the receive direction of the local site are faulty.


----End

Related Information

None.

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




There is no available bandwidth in the transmit direction, and the Ethernet services areinterrupted.



386



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


1. Check whether the sink and source VCTRUNKs are bound with the same number ofphysical paths or the same timeslots.

If... Then...



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 occurs 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.3.129 LCD

Description

The LCD is an alarm indicating loss of cell delimitation. This alarm occurs when the OCD alarmcontinuously occurs within the transmission period of N cells. The letter "N" indicates the LCDalarm threshold value. For different ports, the threshold value is different.



387

Attribute



ParametersNone.

Impact on the Systeml When the LCD alarm occurs, all the services in the receive direction of the port are

interrupted and all the connections at the port insert segment or end AIS cells to thedownstream.

Possible Causesl Cause 1: The path connected to the ATM port receives signals in an incorrect manner. For

example, the MS_AIS, AU_AIS or AU_LOP alarm occurs.l Cause 2: A great number of bit errors occur in the receive path. The receive path reports

alarms indicating excessive bit errors, such as B1_EXC, B2_EXC, and B3_EXC.l Cause 3: The ATM processing chip of the board is faulty.

Procedure

Step 1 Cause 1: The path connected to the ATM port receives signals in an incorrect manner. Forexample, the MS_AIS, AU_AIS or AU_LOP alarm occurs.1. Check whether the MS_AIS, AU_AIS, or AU_LOP alarm occurs in the path connected

to the ATM port.2. If yes, clear these alarms first, and then check whether the LCD alarm is cleared.

Step 2 Cause 2: A great number of bit errors occur in the receive path. The receive path reports alarmsindicating excessive bit errors, such as B1_EXC, B2_EXC, and B3_EXC.1. Check whether the B1_EXC, B2_EXC, or B3_EXC alarm occurs in the receive path.2. If yes, clear these alarms first, and then check whether the LCD alarm is cleared.

Step 3 Cause 3: The ATM processing chip of the board is faulty.1. Perform a cold reset on the board that reports the LCD alarm. For details, see 8.6.1 Cold

Reset.2. If the LCD alarm persists, replace the alarmed board. For details, see 6.5 Replacing the

Smart E1 Board.

----End

Related InformationEnd and segment

The end point, used to monitor the entire virtual connection, is set at the end of the chain network.

The segment point is used to monitor a segment of the entire link.



388

Thresholds of generating the LCD alarm at different ports

l For the external ATM port, the threshold of generating the LCD alarm is seven cells.l For a VC-4 VCTRUNK port, the threshold of generating the LCD alarm is 360 cells.l For a VC-12 VCTRUNK port, the threshold of generating the ALM_IMA_LINK_LCD

alarm in the bound E1 link is 104 cells. If only one E1 link is bound with the VCTRUNK,the LCD alarm is reported when the ALM_IMA_LINK_LCD alarm occurs. If theVCTRUNK is bound with multiple E1 links in the IMA group, and if the number of E1links in which the ALM_IMA_LINK_LCD alarm occurs is greater than the value derivedfrom the total number of bound E1 links subtracted by the minimum number of activatedlinks in the receive direction of the IMA group, the LCD alarm is reported at the VCTRUNKport. Otherwise, the LCD alarm is not reported.

A.3.130 LCS_LIMITED

DescriptionThe LCS_LIMITED alarm indicates that the configuration capacity of an NE exceeds thecapacity authorized by the license file.

Attribute






389

Name Meaning

Parameter 1 Indicates the alarm cause.

l 0x01: The E1 service capacity exceeds the capacity authorized by the licensefile.

l 0x02: The AM license file is not loaded.l 0x03: For IF protection, the bandwidth at the standby port authorized by the

license file is lower than the bandwidth at the main port authorized by thelicense file.

l 0x04: The 1588v2 capacity exceeds the capacity authorized by the licensefile.

l 0x05: The ATM/IMA capacity exceeds the capacity authorized by the licensefile.

l 0x06: The air port LAG capacity exceeds the capacity authorized by thelicense file.

l 0x07: The E1 priority capacity exceeds the capacity authorized by the licensefile.

l 0x08: The synchronous Ethernet capacity exceeds the capacity authorized bythe license file.

l 0x09: The air port compression capacity exceeds the capacity authorized bythe license file

l 0x10: The MPLS service license capacity exceeds the capacity authorized bythe license file.

l 0x11: The PLA license capacity exceeds the capacity authorized by thelicense file.

l 0x12: The total service bandwidth (TDM service bandwidth and data servicebandwidth) exceeds the bandwidth allowed by the Ethernet license file forthe working and protection links.


When the LCS_LIMITED alarm occurs, the change of radio service capacity cannot take effecton the NE.

Possible Causesl Cause 1: The AM configuration on the NE exceeds the capacity authorized by the license

file.

l Cause 2: For IF protection, the bandwidth at the standby port authorized by the license fileis lower than the bandwidth at the main port authorized by the license file.

l Cause 3: The services configured on the NE exceed the capacity authorized by the licensefile.

Procedure

Step 1 Query the capacity of the license by using the NMS.



390

Step 2 Cause 1: The AM configuration on the NE exceeds the capacity authorized by the license file.

1. Check the AM enabling status. If the license does not allow the AM to be enabled, set theAM function to disabled.

Step 3 Cause 2: For IF protection, the bandwidth at the standby port authorized by the license file islower than the bandwidth at the main port authorized by the license file.

1. Check whether the capacities that are authorized by the license files for the main andstandby IF boards in an IF protection group are consistent with the capacities specified inthe contract. If not, contact Huawei technical support engineers to reload correct licensefiles.

Step 4 Cause 3: The services configured on the NE exceed the capacity authorized by the license file.

1. when the alarm parameter is 0x01, check whether the radio service configuration exceedsthe capacity authorized by the license file. For details, see Setting the Hybrid/AMAttributes. If yes, reduce the number of E1 services.

2. Purchase and load the corresponding service license.

----End

Related Information

For TDM services, radio service capacities of NEs are calculated based on the service cross-connections on IF boards.

A.3.131 LFA

Description

The LFA is an alarm indicating that the E1 frame alignment at the local end of the inversemultiplexing for ATM (IMA) link 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.



391

Impact on the Systeml When this alarm occurs, the alarmed E1 link is unavailable, and the available links in the

IMA 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 IMA group will be recovered automatically.

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


Procedure

Step 1 Cause 1: Check for the TU_LOP and TU_AIS alarms on the NMS. If these alarms occur, handlethese alarms first.

Step 2 Cause 2: The alarmed 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.


3. If the alarm persists, replace the board. For details, see 6.6 Replacing the EthernetInterface Board or 6.5 Replacing the Smart E1 Board.

----End

Related InformationBasic frame


A.3.132 LICENSE_DIFF

DescriptionThe LICENSE_DIFF is an alarm indicating that the license file on the IF board is different fromthe backup file on the system control board. After the IF board or system control board is



392

replaced, the license file on the IF board may be different from the backup file on the systemcontrol board.

Attribute


Warning Equipment alarm


Name Meaning

Parameter 1 Indicates the type of the license file.

l 0x01: AM license.l 0x02: Hybrid license.l 0x03: TDM license.



393

Name Meaning

Parameter 2 Indicates the capacity of the license file on the IF board.

When the value of Parameter 1 is 0x01:

l 0x01: The AM function is disabled.l 0x02: The AM function is enabled.


l 0x01: The hybrid capacity is 10 Mbit/s.l 0x02: The hybrid capacity is 20 Mbit/s.l 0x03: The hybrid capacity is 50 Mbit/s.l 0x04: The hybrid capacity is 100 Mbit/s.l 0x05: The hybrid capacity is 150 Mbit/s.l 0x06: The hybrid capacity is 200 Mbit/s.l 0x07: The hybrid capacity is 300 Mbit/s.l 0x08: The hybrid capacity is 400 Mbit/s.l 0x09: The hybrid capacity is beyond the control of licenses.


l 0x01: The TDM radio transmission capacity is 8xE1.l 0x02: The TDM radio transmission capacity is 16xE1.l 0x03: The TDM radio transmission capacity is 32xE1.l 0x04: The TDM radio transmission capacity is 48xE1.l 0x05: The TDM radio transmission capacity is 64xE1.l 0x06: The TDM radio transmission capacity is 128xE1.l 0x07: The TDM radio transmission capacity is beyond the control of licenses.



394

Name Meaning

Parameter 3 Indicates the capacity of the license file on the system control board.


l 0x01: The AM function is disabled.l 0x02: The AM function is enabled.


l 0x01: The hybrid capacity is 10 Mbit/s.l 0x02: The hybrid capacity is 20 Mbit/s.l 0x03: The hybrid capacity is 50 Mbit/s.l 0x04: The hybrid capacity is 100 Mbit/s.l 0x05: The hybrid capacity is 150 Mbit/s.l 0x06: The hybrid capacity is 200 Mbit/s.l 0x07: The hybrid capacity is 300 Mbit/s.l 0x08: The hybrid capacity is 400 Mbit/s.l 0x09: The hybrid capacity is beyond the control of licenses.


l 0x01: The TDM radio transmission capacity is 8xE1.l 0x02: The TDM radio transmission capacity is 16xE1.l 0x03: The TDM radio transmission capacity is 32xE1.l 0x04: The TDM radio transmission capacity is 48xE1.l 0x05: The TDM radio transmission capacity is 64xE1.l 0x06: The TDM radio transmission capacity is 128xE1.l 0x07: The TDM radio transmission capacity is beyond the control of licenses.


Possible Causesl Cause 1: After the IF board or system control board is replaced, the license file on the IF

board may be different from the backup file on the system control board.

Procedure

Step 1 This alarm only warns the user of the different license capacities on the IF board and the systemcontrol board. No handling is required. Software patrol is performed automatically 48 hours laterand synchronizes the license capacities. Then, the alarm clears.

----End



395


A.3.133 LICENSE_LOST

DescriptionThe LICENSE_LOST is an alarm indicating that the NE fails to detect the license file.

Attribute




Name Meaning

Parameter 1 Indicates the type of the license file.

l 0x02: Hybrid licensel 0x03: TDM licensel 0x04: 1588V2 licensel 0x05: ATM/IMA licensel 0x06: NE license

Impact on the SystemWhen the LICENSE_LOST alarm occurs, the functions authorized by the license file cannottake effect.

Possible CausesCause 1: The license file is lost or is not loaded.

Procedure

Step 1 Cause 1: The license file is lost or is not loaded.1. Contact Huawei engineers to reload the license file to the NE.

----End



396


A.3.134 LINK_ERR

DescriptionThe LINK_ERR alarm indicates that a data link is faulty.

Attribute




Name Meaning

Parameter 1 Indicates the ID of the optical port. For example, 0x01 indicatesthat the alarm is reported by optical port 1.

Parameter 2, Parameter 3 Indicate the ID of the path that reports the alarm. For example, 0x000x01 indicate that the alarm is reported by path 1.

Impact on the SystemServices in the alarmed path are interrupted.

Possible Causesl Cause 1: The optical fiber connected to the Ethernet optical port is faulty.l Cause 2: The working modes of the ports at the local and opposite ends are different.l Cause 3: The equipment at the local or opposite end is faulty.

Procedure

Step 1 Cause 1: The optical fiber connected to the Ethernet optical port is faulty.1. Check whether the optical fiber connected to the Ethernet optical port is faulty.

If... Then...

The optical fiber is faulty Replace the fiber.

The optical fiber is not faulty Go to Cause 2.



397

Step 2 Cause 2: The working modes of the ports at the local and opposite ends are different.1. Check whether the working modes of the ports at the local and opposite ends are different.

If... Then...

The working modes of the ports at thelocal and opposite ends are different

Set the working modes of the ports to thesame.

The working modes of the ports at thelocal and opposite ends are the same


Step 3 Cause 3: The equipment at the local or opposite end is faulty.1. Use an optical fiber to perform a loopback at the the alarmed port. For details, see 8.1

Hardware Loopback.

If... Then...

The alarm is cleared Replace the Ethernet board at the opposite end.

The alarm persists Replace the Ethernet board at the local end.

----End

Related Information

None.

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



398

Impact on the SystemWhen this alarm occurs, the alarmed E1 links become unavailable. As a result, fewer links ofthe IMA group are available. If the IMA group is comprised of only one link, services will beinterrupted.

Possible CausesThe possible cause of the LMFA alarm is as follows:

l Cause 1: The alarmed board is faulty.l Cause 2: The frame format is incorrect.

Procedure

Step 1 Cause 1: The alarmed 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.


3. If the alarm persists, replace the board.

Step 2 Cause 2: The frame format is incorrect.1. Check the frame format of the opposite port. For details, see Setting Advanced Attributes

of Smart E1 Ports.2. Set the frame format to CRC-4 Multiframe if it is incorrect.

----End

Related InformationBasic frame


Multiframe

A multiframe is composed of sixteen PCM frames, and can implement cyclic redundancy check(CRC).

A.3.136 LOOP_ALM

DescriptionThe LOOP_ALM is an alarm indicating that a loop occurs.



399

Attribute



Parameters


Name Meaning

Parameter 1 Indicates the type of loopback.

l 0x00: optical/electrical port inloop.l 0x01: optical/electrical port outloop.l 0x02: path inloop.l 0x03: path outloop.l 0x04: loopback on the user side.l 0x05: loopback on the multiplexing side.l 0x08: ATM layer inloop.l 0x09: ATM layer outloop.l 0x0A: PHY layer inloop.l 0x0B: PHY layer outloop.l 0x0C: MAC layer inloop.l 0x0D: MAC layer outloop.l 0x0E: VC-4 timeslot inloop.l 0x0F: VC-4 timeslot outloop.l 0x10: VC-3 timeslot inloop.l 0x11: VC-3 timeslot outloop.l 0x12: VC-12 timeslot inloop.l 0x13: VC-12 timeslot outloop.l 0x14: IF outloop.l 0x15: IF inloop.l 0x16: RF inloop.l 0xFF: any of the preceding loopback modes.


When the LOOP_ALM alarm occurs, the looped port or path cannot carry services.



400

Possible Causes

Cause 1: A loop is performed on the local NE.

Procedure

Step 1 Cause 1: A loop is performed on the local NE.

1. Determine the type of loopback according to the alarm parameter.

2. Find out the cause of the loopback, and set the loopback status of the alarmed port to Non-Loopback.

For details, see 8.5 Software Loopback.

----End

Related Information

None.

A.3.137 LP_CROSSTR

Description

The LP_CROSSTR is an alarm indicating that the lower order path error crosses the threshold.This alarm occurs when the board detects that the performance event that the lower order patherror crosses the preset threshold.

Attribute


Minor Service alarm

Parameters


Name Meaning





401

Name Meaning


l 0x90: LPBBEl 0x91: LPESl 0x92: LPSESl 0x93: LPFEBBEl 0x94: LPFEESl 0x95: LPFESESl 0x96: LPUASl 0x8e: LPFEUASl 0x97: LPCSESl 0x98: LPFECSES


When the LP_CROSSTR alarm occurs, a large number of errors occur in the service, and theservice may even be interrupted.

Possible Causes

Cause 1: The lower order path error crosses the preset threshold.

Procedure

Step 1 Cause 1: The lower order path error crosses the preset threshold.

1. Check the threshold crossing records to find out the performance event that the lower orderpath error crosses the preset threshold.


----End

Related Information

None.

A.3.138 LP_R_FIFO

Description

The LP_R_FIFO is an alarm indicating that the FIFO overflows on the transmit side of the lowerorder path.



402

Attribute



Parameters

None.


When the LP_R_FIFO alarm occurs, the service has errors.

Possible Causesl Cause 1: The clock of the local NE is not synchronized with the clock of the opposite NE.


Procedure

Step 1 Cause 1: The clock of the local NE is not synchronized with the clock of the opposite NE.

1. Browse current performance events, and check whether the performance event of TUpointer justification occurs on the local NE and the opposite NE.

If... Then...

The TU pointer justification occurs Handle the performance event. For details,see C.3.2 TUPJCHIGH, TUPJCLOW,and TUPJCNEW.

The TU pointer justification does notoccur

Go to Cause 2.



----End

Related Information

None.

A.3.139 LP_RDI

Description

The LP_RDI is an alarm indicating the lower order path remote receive failure. This alarm occurswhen the board detects that bit 8 of byte V5 is 1.



403

Attribute



ParametersNone.

Impact on the SystemWhen the LP_RDI alarm occurs, the service on the local NE is not affected. The service receivedby the opposite NE, however, is interrupted.

Possible CausesCause 1: The local NE detects the message that is returned by the opposite NE and indicates thelower order path remote receive failure.

Procedure

Step 1 Cause 1: The local NE detects the message that is returned by the opposite NE and indicates thelower order path remote receive failure.1. Handle the lower order path alarm on the opposite NE.

----End


A.3.140 LP_RDI_VC12

DescriptionThe LP_RDI_VC12 is an alarm indicating that data reception fails at the remote end of VC-12lower order path. This alarm occurs when the board detects that bit 8 of byte V5 is 1.

Attribute






404


Name Meaning


Parameter 2, Parameter 3 Indicate the ID of the VC-12 path.


When this alarm occurs, the service on the local NE is not affected. The service received by theopposite NE, however, is interrupted.

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.1. Handle the alarm of the lower order path on the remote site.

----End

Related Information

None.

A.3.141 LP_RDI_VC3

Description

The LP_RDI_VC3 alarm indicates that data reception at the remote end of a lower order (VC-3)path fails. A board reports this alarm when detecting that bit 5 in byte G1 is 1.

Attribute



Parameters




405

Name Meaning



Impact on the SystemWhen the LP_RDI_VC3 alarm occurs, the services at the local site are not affected, but theopposite site cannot receive services.

Possible CausesThe local site receives a message from the opposite site, and the message says that data receptionfails at the remote end of a lower order (VC-3) path.

Procedure

Step 1 Cause: The local site receives a message from the opposite site, and the message says that datareception fails at the remote end of a lower order (VC-3) path.1. Handle the alarm in the lower order (VC-3) path at the opposite site.

----End


A.3.142 LP_REI

DescriptionThe LP_REI is an alarm indicating the lower order path remote error. This alarm occurs whenthe board detects that bit 3 of V5 is 1.

Attribute


Minor Service alarm

ParametersNone.

Impact on the SystemWhen the LP_REI alarm occurs, the service on the local NE is not affected. The service receivedby the opposite NE, however, has errors.



406

Possible CausesCause 1: The local NE detects the message that is returned by the opposite NE and indicates thelower order path remote errors.

Procedure

Step 1 Cause 1: The local NE detects the message that is returned by the opposite NE and indicates thelower order path remote errors.1. Handle the LP_BBE performance event on the opposite NE.

----End


A.3.143 LP_REI_VC12

DescriptionThe 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 the board detects that bit 3 of byte V5 is 1.

Attribute


Minor Service alarm


Name Meaning



Impact on the SystemBit errors exist in the service in the receive direction of the remote site.

Possible CausesCause 1: The local site receives a message from the remote site, and the message says that thereare bit errors in the lower order path.



407

Procedure

Step 1 Cause 1: 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

Related Information

None.

A.3.144 LP_REI_VC3

Description

The LP_REI_VC3 alarm indicates that there are bit errors at the remote end of a lower order(VC-3) path. A board reports this alarm when detecting that any one of bits 1 to 4 in byte G1 is1.

Attribute



Parameters


Name Meaning




Bit errors exist in received services at the opposite site.

Possible Causes

The local site receives a message from the opposite site, and the message says that there are biterrors at the remote end of a lower order (VC-3) path.



408

Procedure

Step 1 Cause: The local site receives a message from the opposite site, and the message says that thereare bit errors at the remote end of a lower order (VC-3) path.1. Handle the alarm in the lower order (VC-3) path at the opposite site.

----End


A.3.145 LP_RFI

DescriptionThe LP_RFI is an alarm indicating the lower order path remote failure. This alarm occurs whenthe board detects that bit 4 of V5 is 1.

Attribute



ParametersNone.

Impact on the SystemWhen the LP_RFI alarm occurs, the service on the local NE is not affected. The alarm onlyindicates that the lower order paths on the opposite NE cannot carry services.

Possible CausesCause 1: The local NE detects the message that is returned by the opposite NE and indicates thelower order path remote failure.

Procedure

Step 1 Cause 1: The local NE detects the message that is returned by the opposite NE and indicates thelower order path remote failure.1. Handle the lower order path alarm on the opposite NE.

----End




409

A.3.146 LP_SLM

Description

The LP_SLM is an alarm indicating that a mismatched signal label is detected in the lower orderpath. This alarm is reported when the board detects a signal label mismatch between the V5bytes.

Attribute



Parameters

None.


The services in the lower order path are unavailable.

Possible Causes

Cause 1: The signal label contained in the V5 byte that is received by the local site does notmatch with the signal label contained in the V5 byte that is transmitted by the remote site.

Procedure

Step 1 Cause 1: The signal label contained in the V5 byte that is received by the local site does notmatch with 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 witheach other. For details, see Configuring VC-12 POHs.

----End

Related Information

None.

A.3.147 LP_SLM_VC12

Description

The LP_SLM_VC12 is an alarm indicating that a mismatched signal label is detected in thelower order path. This alarm is reported when the board detects a signal label mismatch betweenthe V5 bytes.



410

Attribute



Parameters


Name Meaning




The service in this lower order path is unavailable.

Possible Causes

Cause 1: The signal label contained in the V5 byte that is received by the local site does notmatch with the signal label contained in the V5 byte that is transmitted by the remote site.

Procedure

Step 1 Cause 1: The signal label contained in the V5 byte that is received by the local site does notmatch with 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 oris to be transmitted by the remote site. Ensure that the signal labels at both ends match witheach other. For details, see Configuring VC-12 POHs.

----End

Related Information

None.

A.3.148 LP_SLM_VC3

Description

The LP_SLM_VC3 alarm indicates that a mismatched signal label is detected in a lower order(VC-3) path. A board reports this alarm when detecting a mismatched signal label in byte C2.



411

Attribute



Parameters


Name Meaning




The services in the lower order (VC-3) path are unavailable.

Possible Causes

The signal label in byte C2 that is received at the local site does not match with the signal labelin byte C2 that is transmitted at the opposite site.

Procedure

Step 1 Cause 1: The signal label in byte C2 that is received at the local site does not match with thesignal label in byte C2 that is transmitted at the opposite site.1. Reset the signal label in byte C2 that is received at the local site or the signal label in byte

C2 that is transmitted at the local site. Ensure that the signal labels are the same at bothsites. For details, see Configuring VC-4 POHs.

----End

Related Information

None.

A.3.149 LP_T_FIFO

Description

The LP_T_FIFO is an alarm indicating that the FIFO overflows on the transmit side of the lowerorder path.



412

Attribute



Parameters

None.


Bit errors occur in the services.

Possible Causesl Cause 1: The frequency offset of the input signal is very large.


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

If... Then...

The frequency offset is very large Troubleshoot the remote site.

The frequency offset is within 50 ppm Go to Cause 2.



----End

Related Information

None.

A.3.150 LP_TIM

Description

The LP_TIM is an alarm indicating a mismatched trace identifier is detected in the lower orderpath. This alarm is reported when the board detects a mismatch between the J2 bytes at bothends.



413

Attribute



Parameters

None.


None.

Possible Causesl Cause 1: The J2 byte to be received by the local site does not match with 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 with the J2 byte to betransmitted by the remote site.

1. Set the byte mode of the J2 byte to be received by the local site to the disable mode.Alternatively, set the J2 byte to be received by the local site to match with the J2 byte tobe transmitted by the remote site. For details, see Configuring VC-12 POHs.

Step 2 Cause 2: The data configuration at the intermediate nodes is incorrect.

1. Check whether the cross-connections of the intermediate nodes where the service travelsare configured correctly. If not, reconfigure the cross-connections. For details, see QueryingTDM Services.

----End

Related Information

None.

A.3.151 LP_TIM_VC12

Description

The LP_TIM_VC12 is an alarm indicating a mismatched trace identifier is detected in the lowerorder path. This alarm is reported when the board detects a mismatch between the J2 bytes atboth ends.



414

Attribute



Parameters


Name Meaning




None.

Possible Causesl Cause 1: The J2 byte to be received by the local site does not match with 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 with the J2 byte to betransmitted by the remote site.1. Set the byte mode of the J2 byte to be received by the local site to the disable mode.

Alternatively, set the J2 byte to be received by the local site to match with the J2 byte tobe transmitted by the remote site. For details, see Configuring VC-12 POHs.

Step 2 Cause 2: The data configuration at the intermediate nodes is incorrect.1. Check whether the cross-connections of the intermediate nodes where the service travels

are configured correctly. If not, reconfigure the cross-connections. For details, see QueryingTDM Services.

----End

Related Information

None.

A.3.152 LP_TIM_VC3



415

DescriptionThe LP_TIM_VC3 alarm indicates that a mismatched trace identifier is detected in a lower order(VC-3) path. A board reports this alarm when detecting a mismatched trace identifier in byte J1.

Attribute




Name Meaning




Possible Causesl Cause 1: Byte J1 to be received at the local site does not match with byte J1 to be transmitted

at the opposite site.l Cause 2: The data configuration at intermediate sites is incorrect.

Procedure

Step 1 Cause 1: Byte J1 to be received at the local site does not match with byte J1 to be transmitted atthe opposite site.1. Set byte J1 to be received at the local site to the disable mode or the same as byte J1 to be

transmitted at the opposite site. For details, see Configuring VC-4 POHs.

Step 2 Cause 2: The data configuration at intermediate sites is incorrect.1. Check whether the cross-connections of intermediate sites where the services travel are

configured correctly. If not, reconfigure the cross-connections. For details, see QueryingTDM Services.

----End




416

A.3.153 LP_UNEQ

Description

The LP_UNEQ is an alarm indicating that the lower order path is unequipped. This alarm isreported when the board detects that the V5 byte signal label is 0.

Attribute



Parameters

None.


The services in the path are unavailable. If the services are configured with protection, protectionswitching may be triggered.

Possible Causes

The 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 notconfigured with services

Configure services for the tributary path atthe remote site.

The tributary path at the remote site isconfigured with services

Go to Cause 2.

Step 2 Cause 2: The cross-connection configuration at the intermediate nodes is incorrect.1. Check whether the cross-connection configuration at the intermediate nodes is correct. If

not, reconfigure the cross-connections. For details, see Querying TDM Services.

----End



417

Related Information

None.

A.3.154 LP_UNEQ_VC12

Description

The 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



Parameters


Name Meaning




If the alarm is generated due to incorrect service configurations, the services are interrupted.

Possible Causes

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



418

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, reconfigure the cross-connections. For details, see Querying TDM Services.

----End


A.3.155 LP_UNEQ_VC3

DescriptionThe LP_UNEQ_VC3 alarm indicates that a lower order (VC-3) path is unequipped. A boardreports this alarm when detecting that the C2 byte signal label is 0.

Attribute




Name Meaning



Impact on the SystemThe services in the path are unavailable. If the services are configured with protection, protectionswitching is triggered.

Possible CausesThe data configuration is incorrect.



419

l Cause 1: The tributary path at the local site is configured with services, but the tributarypath at the opposite site is not.

l Cause 2: The cross-connection configuration at the intermediate sites is incorrect.

Procedure

Step 1 Cause 1: The tributary path at the local site is configured with services, but the tributary path atthe opposite site is not.

1. Check whether the tributary path at the opposite site is configured with services. For details,see Querying TDM Services.

If... Then...

The tributary path at the opposite site is not configured withservices

Configure services.

The tributary path at the opposite site is configured withservices

Go to Cause 2.

Step 2 Cause 2: The cross-connection configuration at the intermediate sites is incorrect.

1. Check whether the cross-connection configuration at the intermediate sites is correct. Ifnot, reconfigure the cross-connections. For details, see Querying TDM Services.

----End

Related Information

None.

A.3.156 LPS_UNI_BI_M

Description

The LPS_UNI_BI_M is an alarm indicating that switching modes (single-ended or dual-ended)at both ends of the linear MSP do not match with each other.

Attribute



Parameters




420

Name Meaning


0x01: linear MS protection.



The system performs protection switching in single-ended mode.

Possible Causes

Cause 1: The linear MSP is configured incorrectly.

The LPS_UNI_BI_M alarm is generated only when the following conditions are met:

l The switching modes (single-ended or dual-ended) at the local and remote sites aredifferent.

l The last three bits of the K2 byte are set to the indicated mode.l The type of the protocol is set to a restructure protocol.

Procedure

Step 1 Cause 1: The linear MSP is configured incorrectly.1. Change the MSP switching modes at both ends, and ensure that they are the same. For

details, see Querying the Status of the Linear MSP.

----End

Related Information

None.

A.3.157 LPT_CFG_CLOSEPORT

Description

The LPT_CFG_CLOSEPORT is an alarm indicating that the LPT closes the access port of thelocal NE. Upon detecting that the convergence port of the local NE or the access port of theremote NE is faulty, the LPT automatically closes the access port of the local NE. Then, theLPT_CFG_CLOSEPORT alarm is reported.

Attribute





421

Parameters


Name Meaning

Parameter 1, Parameter 2 Indicates the board ID.

Parameter 3 Indicates the ID of the sub-board.

Parameter 4, Parameter 5 Indicate the port ID.


When this alarm occurs, services are switched to the backup network and the LPT closes theaccess port of the remote NE at the same time.

Possible Causesl Cause 1: The convergence port of the local NE or the access port of the remote NE is faulty.

Procedure

Step 1 Cause 1: The convergence port of the local NE or the access port of the remote NE is faulty.

1. Check whether the convergence port of the local NE, the access port and the convergenceport of the remote NE report the ETH_LOS alarm or other alarms related to boards andoptical modules.

2. If yes, clear these alarms. Then, check whether the LPT_CFG_CLOSEPORT alarm iscleared.

----End

Related Information

None.

A.3.158 LPT_INEFFECT

Description

The LPT_INEFFECT is an alarm indicating that the LPT function fails. If the user configuresthe LPT function but the board does not support the LPT function, the LPT_INEFFECT alarmis reported.



422

Attribute




Name Meaning

Parameter 1 Indicates the ID of the IP port.

Parameter 2, Parameter 3 Indicate the port ID.

The values are always 0x00 0x01.

Parameter 4, Parameter 5 The values are always 0xff 0xff.

Impact on the SystemWhen the alarm is generated, the services are not affected. If the board hardware is of a veryearly version, the board software automatically prevents the LPT protocol state machine fromrunning, but reserves the LPT configuration.

Possible CausesCause 1: The board hardware is of a very early version, and the user configures the LPT function.

ProcedureStep 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 the properversion. For details, see 6 Part Replacement.

The LPT function is not required Delete the configuration of the LPT. For details, seeLPT Configuration.

----End




423

A.3.159 LPT_RFI

Description

The LPT_RFI is a remote failure indication of the link path through (LPT) function. This alarmoccurs when the LPT function detects the failure of the remote port or the LPT service network.

Attribute


Critical Service alarm

Parameters


Name Meaning

Parameter 1 Indicates the ID of the IP port.

Parameter 2, Parameter 3 Indicate the ID of the optical interface. The values are always 0x000x01.



During the data transmission, the links are unavailable and the services are interrupted when theLPT function detects the failure of the remote port or the service network. At the same time, thebackup links are enabled. If the backup links are available, the services can be restored on thebackup links.

Possible Causesl Cause 1: The remote port fails due to the alarms such as ETH_LOS and

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.

– There are the alarms such as TU_LOP, TU_AIS, VCAT_LOA,VCAT_LOM_VC12, and LP_UNEQ_VC12.



424

Procedure

Step 1 Check the alarms on the NMS, determine the board that reports the LPT_RFI alarm, and thendetermine the ID of the alarmed port on the board according to Parameter 1.

Step 2 Cause 1: The remote port fails due to the alarms such as ETH_LOS and LSR_NO_FITED, orthe remote port is disabled.1. Check whether the corresponding opposite port is enabled.

If... Then...

The opposite port is disabled 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. Focus on the R_LOS andMW_LOF alarms and handle them first.

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 LSR_NO_FITEDl BIP_EXC and B3_EXCl TU_LOP, TU_AIS, VCAT_LOA, VCAT_LOM_VC12, and LP_UNEQ_VC12

----End


A.3.160 LSR_NO_FITED

DescriptionThe LSR_NO_FITED is an alarm indicating that the SFP optical module is not installed.

Attribute



ParametersNone.



425


The optical interface fails to carry services.

Possible Causesl Cause 1: The laser of the local site is not installed.l Cause 2: The optical module is faulty.

Procedure

Step 1 Cause 1: The SFP optical module of the local site is not installed.1. Find out why the SFP optical module is not installed, and contact Huawei technical support

engineers for the installation.

Step 2 Cause 2: The optical module is faulty.1. 6.12 Replacing the SFP.

----End

Related Information

None.

A.3.161 LTI

Description

The LTI is an alarm indicating that the synchronization sources are lost. This alarm is reportedwhen all the synchronization sources for the NE are lost.

Attribute



Parameters


Name Meaning

Parameter 1 0x01: system priority list

0x02: external clock priority list



426

Impact on the SystemThe clock enters the free-run mode and loses synchronization with other NE clocks.

Possible Causesl Cause 1: The clock configuration is incorrect.l Cause 2: All the clock sources in the clock source priority table fail.l Cause 3: A fiber cut or a cable cut occurs.l Cause 4: The synchronization source is set to the manual reversion mode.l Cause 5: No input is available from the external clock source.l Cause 6: The board is faulty.

ProcedureStep 1 Cause 1: The clock configuration is incorrect.

1. Check whether the data in the clock source priority table meets the network planningrequirement. For details, see Querying the Clock Synchronization Status.

If... Then...

The configuration is incorrect Correct the configuration.

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 anEthernet clock

Handle the alarm that occurs on the Ethernetboard.

Step 3 Cause 3: A fiber cut or a cable cut occurs.1. Connect the fiber or cable properly.

Step 4 Cause 4: The synchronization source is set to the manual reversion mode.1. See Modifying the Recovery Parameter of the Clock Source, and set the clock source to

the automatic reversion mode.

Step 5 Cause 5: No input is available from the external clock source.1. See Configuring Clock Sources for External Clock Output, and configure the clock source

that provides external clock signals.



427

Step 6 Cause 6: The board is faulty.1. Replace the board.

----End

Related Information

None.

A.3.162 MAC_EXT_EXC

Description

The MAC_EXT_EXC alarm indicates that the number of bit errors at the MAC layer crossesthe threshold.

Attribute



Parameters

Parameters


Name Meaning

Parameter 1 Indicates the threshold crossing type.

l 0x01: ETHDROP threshold crossingl 0x02: ETHEXCCOL threshold crossingl 0x03: RXBBAD threshold crossing


When the MAC_EXT_EXC alarm occurs, the performance of services degrades.

Possible Causesl Cause 1: ETHDROP threshold crossing. The number of packet loss events crosses the upper

threshold.



428

l Cause 2: ETHEXCCOL threshold crossing. The number of frames unsuccessfullytransmitted after successive collisions crosses the upper threshold.

l Cause 3: RXBBAD threshold crossing. The number of bytes in received bad packets crossesthe upper threshold.

Procedure

Step 1 Check whether the working modes of the ports at the transmit and receive ends are the same.

1. On the NMS, query the working modes of the ports at the transmit and receive ends.

If... Then...

The ports at the transmit and receiveends work in different modes or in half-duplex mode

Set the working modes of the ports at thetransmit and receive ends to full-duplex orauto-negotiation. Ensure that the workingmodes of the ports at the transmit and receiveends are the same. For details, see Setting theGeneral Attributes of Ethernet Ports.

The ports at the transmit and receiveends work in the same mode and neitherport works in half-duplex mode.


Step 2 Handle the problem that the opposite site transmits packets abnormally.

Step 3 Handle the quality problem with the transmission line.Check whether the local end reports alarms such as ETH_LOS as the external line is damagedor over attenuated. If yes, see the related handling method to clear the alarms.

Step 4 Replace the faulty board.

----End

Related Information

None.

A.3.163 MAC_FCS_EXC

Description

The MAC_FCS_EXC alarm indicates that the software detects that the number of bit errors atthe MAC layer crosses the threshold. The software periodically detects the number of bytesreceived by the MAC chip and the number of bytes that have bit errors. The MAC_FCS_EXCalarm is reported when the number of bit errors crosses the threshold.

Attribute





429

ParametersNone.

Impact on the SystemWhen the MAC_FCS_EXC alarm occurs, the performance of services degrades.

Possible Causesl Cause 1: The performance of the line signals degrades.l Cause 2: The input optical power is abnormal.l Cause 3: A fiber connector is dirty.

Procedure

Step 1 Cause 1: The performance of the line signals degrades.1. On the NMS, check for a LOOP_ALM alarm. If there is any, clear it. For details, see 8.5

Software Loopback.2. If the LOOP_ALM alarm persists, check whether the NMS is under a denial-of-service

(DOS) attack. If yes, eliminate the source that transmits a large amount of invalid data, andthen check whether the LOOP_ALM alarm is cleared.

3. If the LOOP_ALM alarm persists, check whether a cable or fiber is faulty. Replace thefaulty cable or fiber, and then check whether the LOOP_ALM alarm is cleared.

Step 2 Cause 2: The input optical power is abnormal.1. Check whether the alarmed port reports an IN_PWR_ABN alarm as well.2. If there is any, clear the IN_PWR_ABN alarm.

Step 3 Cause 3: A fiber connector is dirty.1. Clean the fiber connector and the optical receive port. For details, see 8.2 Cleaning Fiber

Connectors and Adapters.

----End


A.3.164 MOD_COM_FAIL

DescriptionThe MOD_COM_FAIL is an alarm indicating that Module communicates abnormally.

Attribute





430

Parameters


Name Meaning

Parameter 1 0x11 indicates that the communication between the system control unit andpacket switching unit is failed.


The related operations cannot be performed by using the NMS and the performance informationof each module cannot be queried.

Possible Causesl Cause 1: The software processing of the related modules of the board is faulty.

l Cause 2: The board hardware is faulty.

Procedure

Step 1 Cause 1: The software processing of the related modules of the board is faulty.

1. Perform a cold reset on the faulty board by using the NMS. For details, refer to 8.6.1 ColdReset.

2. remove the faulty board and insert it again.

Step 2 Cause 2: The board hardware is faulty.

1. Replace the faulty board. For details, refer to 6.9 Replacing the System Control, Switchand Timing Board.

----End

Related Information

None.

A.3.165 MOD_TYPE_MISMATCH

Description

The MOD_TYPE_MISMATCH alarm indicates that a mismatched port module is detected.



431

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.


The services at the alarmed port are interrupted.

Possible Causes

Cause 1: The preset type of the SFP module is different from the actual type of the SFP module.

Procedure

Step 1 Cause 1: The preset type of the SFP module is different from the actual type of the SFP module.

1. Find out the port that reports the alarm according to the alarm parameters.

2. Check whether the preset type of the SFP module is the same as the actual type of the SFPmodule.

If... Then...

The preset type of the SFP module is thesame as the actual type of the SFP module

Replace the optical/electrical SFPmodule. Ensure that the new SFP module isof the correct type.

The preset type of the SFP module isdifferent from the actual type of the SFPmodule

Reset the type of the SFP module.

----End

Related Information

None.



432

A.3.166 MPLS_PW_BDI

DescriptionThe MPLS_PW_BDI is an alarm of PW backward defect indication. This alarm occurs whenthe local NE receives the BDI packet, notifying that the remote NE detects that the PW is faulty.

Attribute



ParametersNone.

Impact on the SystemThe services on the transmit side of the local NE are faulty.

Possible CausesCause 1: The remote NE detects that the PW is faulty.

Procedure

Step 1 Cause 1: The remote NE detects that the PW is faulty.

If... Then...

A board on the remote NE is reset or faulty Rectify the fault on the remote NE.

The physical link between the local NE and theremote NE is faulty

Rectify the fault on the physical link.

The bandwidth allocated to the PW is fullyoccupied.

Increase the bandwidth of the PW.

----End


A.3.167 MPLS_PW_Excess

DescriptionThe MPLS_PW_Excess is an alarm indicating that excessive trail termination source identifiers(TTSIs) are received on the PW. This alarm occurs when five or more correct CV/FFD packetsare received within three consecutive CV/FFD periods.



433

Attribute



Parameters

None.


Services may be interrupted if excessive redundant packets are received.

Possible Causesl Cause 1: Multiple PWs are configured with the same label and PW ID.

l Cause 2: Physical links are misconnected.

Procedure

Step 1 Cause 1: Multiple PWs are configured with the same label and PW ID.

1. Check whether multiple PWs are configured with the same label and PW ID.

2. If yes, delete the redundant PWs or change the PW ID and label of each PW to uniquevalues.


If... Then...



Step 2 Cause 2: Physical links are misconnected.

1. Check whether any fiber or cable is misconnected.

2. If yes, rectify the fault.

----End

Related Information

None.

A.3.168 MPLS_PW_LOCV

Description

The MPLS_PW_LOCV is an alarm of PW connectivity loss. This alarm occurs when noexpected CV/FFD packets are received within three consecutive CV/FFD periods.



434

Attribute



ParametersNone.


Possible Causesl Cause 1: The remote NE of the PW stops transmitting CV/FFD packets.l Cause 2: The OAM is different between the ends of the PW.l Cause 3: The PW that carries services is faulty.l Cause 4: The remote NE of the PW is faulty.l Cause 5: The service interface is configured incorrectly.l Cause 6: Serious congestion occurs on the network.

Procedure

Step 1 Cause 1: The remote NE of the PW stops transmitting CV/FFD packets.1. Check whether the remote NE of the PW stops transmitting CV/FFD packets.

If... Then...

The remote NE of the PW stopstransmitting CV/FFD packets

Enable the CV/FFD detection and thencheck whether the alarm clears.

The remote NE of the PW keepstransmitting CV/FFD packets

Go to Cause 2.

Step 2 Cause 2: The OAM is different between the ends of the PW.1. Check whether the OAM is different between the ends of the PW. If no, Setting PW OAM

Parameters according to the plan. If yes, go to cause 3.

Step 3 Cause 3: The PW that carries services is faulty.1. Check whether the local NE and remote NE of the PW report any alarm related to boards.

If yes, clear the alarm. Then, check whether the MPLS_PW_LOCV alarm is cleared.2. Check whether any link-related alarm is reported. If yes, clear the alarm. Then, check

whether the MPLS_PW_LOCV alarm is cleared.

If... Then...





435

Step 4 Cause 4: The remote NE of the PW is faulty.1. Check whether the interconnected board of the remote NE reports the COMMUN_FAIL

alarm. If yes, the board is being reset. Clear the COMMUN_FAIL alarm and then checkwhether the MPLS_PW_LOCV alarm is cleared.

2. If the interconnected board of the remote NE reports other alarms, clear these alarms. Then,check whether the MPLS_PW_LOCV alarm is cleared.

If... Then...



Step 5 Cause 5: The service interface is configured incorrectly.1. Check whether the service interface is configured correctly according to service planning.2. If not, reconfigure the service interface. Then, check whether the MPLS_PW_LOCV alarm

is cleared.

If... Then...



Step 6 Cause 6: Serious congestion occurs on the network.1. Check whether the bandwidth allocated to the faulty tunnel is fully occupied.2. If yes, increase the bandwidth of the PW or eliminate the sources that transmit a large

amount of invalid data.

----End


A.3.169 MPLS_PW_MISMATCH

DescriptionThe MPLS_PW_MISMATCH is an alarm indicating that the trail termination source identifiers(TTSIs) on the PW do not match with the specified one. This alarm occurs when only the packetswith wrong TTSIs are received within three consecutive CV/FFD periods.

Attribute



ParametersNone.



436


Services are interrupted or the packets from other PWs are received.

Possible Causesl Cause 1: The ingress node or egress node of the faulty PW is configured incorrectly.


Procedure

Step 1 Cause 1: The ingress node or egress node of the faulty PW is configured incorrectly.

1. Check whether the ingress node and egress node of the faulty PW are configured correctlyaccording to NE planning.

2. If the ingress node or egress node is configured incorrectly, correct the configuration andthen check whether the alarm clears.


1. Check whether any fiber or cable is misconnected.

2. If yes, rectify the fault.

----End

Related Information

None.

A.3.170 MPLS_PW_MISMERGE

Description

The MPLS_PW_MISMERGE is an alarm indicating that the trail termination source identifiers(TTSIs) are mismerged on the PW. This alarm is reported if the CV/FFD packets with correctTTSIs and those with wrong TTSIs are received in three consecutive CV/FFD periods.

Attribute



Parameters

None.


Services are interrupted or the packets from other PWs are received.



437

Possible Causesl Cause 1: The PW is configured incorrectly.l Cause 2: Physical links are misconnected.

Procedure

Step 1 Cause 1: The PW is configured incorrectly.1. Check whether the PW are configured correctly according to NE planning.2. If the PW is configured incorrectly, correct the configuration and then check whether the

alarm clears.

Step 2 Cause 2: Physical links are misconnected.1. Check whether any fiber or cable is misconnected.2. If yes, rectify the fault.

----End


A.3.171 MPLS_PW_SD

DescriptionThe MPLS_PW_SD is an alarm of signal degrade on the PW. This alarm is reported when thepacket loss rate of the connectivity check (CC) crosses the SD threshold but is lower than theSF threshold.

Attribute



ParametersNone.

Impact on the SystemServices degrade and moderate packet loss occurs.

Possible Causesl Cause 1: The bandwidth of the PW is fully occupied.l Cause 2: The physical port has bit errors or packet loss.l Cause 3: The fiber connector or the optical module is dirty.



438

Procedure

Step 1 Cause 1: The bandwidth of the PW is fully occupied.1. Check whether the bandwidth allocated to the faulty PW is fully occupied.2. If yes, increase the bandwidth of the PW or eliminate the sources that transmit a large

amount of invalid data. Then, check whether the MPLS_PW_SD alarm is cleared.

Step 2 Cause 2: The physical port has bit errors or packet loss.1. Check whether the fiber connector is loose. If yes, insert the fiber connector securely.

Step 3 Cause 3: The fiber connector or the optical module is dirty.1. Clean the fiber connector or the optical module. For details, see Checking and cleaning

fiber connectors.

----End


A.3.172 MPLS_PW_SF

DescriptionThe MPLS_PW_SF is an alarm of signal failure on the PW. This alarm occurs when the numberof received connectivity check (CC) packets is less than the signal failure (SF) threshold.

Attribute



ParametersNone.

Impact on the SystemServices fail and severe packet loss occurs.

Possible Causesl Cause 1: The bandwidth of the PW is fully occupied.l Cause 2: The physical port has bit errors or packet loss.l Cause 3: The fiber connector or the optical module is dirty.

Procedure

Step 1 Cause 1: The bandwidth of the PW is fully occupied.



439

1. Check whether the bandwidth allocated to the faulty PW is fully occupied.2. If yes, increase the bandwidth of the PW or eliminate the sources that transmit a large

amount of invalid data. Then, check whether the MPLS_PW_SF alarm is cleared.

Step 2 Cause 2: The physical port has bit errors or packet loss.1. Check whether the fiber connector is loose. If yes, insert the fiber connector securely.

Step 3 Cause 3: The fiber connector or the optical module is dirty.1. Clean the fiber connector or the optical module. For details, see Checking and cleaning

fiber connectors.

----End

Related Information

None.

A.3.173 MPLS_PW_UNKNOWN

Description

The MPLS_PW_UNKNOWN is an alarm of unknown defects on the PW. This alarm occurswhen the connectivity check (CC) packets of unexpected types, periods, and values are receivedwithin three consecutive periods.

Attribute



Parameters

None.


PW OAM fails.

Possible Causes

Cause 1: The PW OAM configuration at the two ends is different.

Procedure

Step 1 Cause 1: The PW OAM configuration at the two ends is different.1. Change the PW OAM configuration to the same at the two ends.

----End



440

Related Information

None.

A.3.174 MPLS_TUNNEL_BDI

Description

The MPLS_TUNNEL_BDI is an alarm of tunnel backward defect indication. This alarm occurswhen the port of the local NE receives the backward defect indication (BDI) packet, notifyingthat the opposite NE detects that the tunnel is faulty.

Attribute



Parameters

None.


When this alarm occurs, the services on the local NE is normal.

Possible Causes

Cause 1: The opposite NE detects MPLS alarms.

Procedure

Step 1 Cause 1: The opposite NE detects MPLS alarms.1. Clear the MPLS alarms reported on the opposite NE.

----End

Related Information

None.

A.3.175 MPLS_TUNNEL_Excess

Description

The MPLS_TUNNEL_Excess is an alarm indicating that excessive trail termination sourceidentifiers (TTSIs) are received in the tunnel. This alarm occurs when the Ethernet port of thelocal NE receives five or more correct CV/FFD packets within three consecutive CV/FFDperiods.



441

Attribute



ParametersNone.

Impact on the SystemServices may be interrupted if excessive redundant packets are received.

Possible Causesl Cause 1: Physical links are misconnected.

ProcedureStep 1 Cause 1: Physical links are misconnected.

1. Check whether any fiber or cable is misconnected between the two ends. If yes, reconnectthe fiber or cable.

----End


A.3.176 MPLS_TUNNEL_FDI

DescriptionThe MPLS_TUNNEL_FDI is an alarm of tunnel forward defect indication. This alarm isreported when the local NE receives the forward defect indication (FDI) packet, notifying thatthe upstream tunnel at the physical layer is faulty.

Attribute



ParametersNone.

Impact on the SystemWhen this alarm occurs, services may be interrupted.



442

Possible CausesCause 1: The upstream NE detects that the physical link that carries the tunnel is faulty.

Procedure

Step 1 Cause 1: The upstream NE detects that the physical link that carries the tunnel is faulty.

If... Then...

The link-related alarms, such as MW_BER_EXC,MW_BER_SD, MW_FEC_UNCOR and MW_LOF, arereported

Clear these alarms first.

The transmit board of the local NE reports hardware-relatedalarms (alarms on the optical modules or boards), such asHARD_BAD and LSR_NO_FITED

Clear these alarms first.

----End


A.3.177 MPLS_TUNNEL_LOCV

DescriptionThe MPLS_TUNNEL_LOCV is an alarm of tunnel connectivity loss. This alarm occurs whenthe port of the local NE fails to receive expected CV/FFD packets within three CV/FFD periods.(The expected CV/FFD packets must carry correct TTSIs and have the correct type, period, andvalue.)

Attribute



ParametersNone.

Impact on the SystemWhen this alarm occurs, the services that the faulty tunnel carries are interrupted.

Possible Causesl Cause 1: In detection mode of manual, the MPLS OAM settings, such as detection packet

type and detection packet period, differ at the two ends.l Cause 2: Severe congestion occurs on the network.



443

l Cause 3: A certain board is faulty.l Cause 4: The physical link between the two ends is faulty.

Procedure

Step 1 Cause 1: In detection mode of manual, the MPLS OAM settings, such as detection packet typeand detection packet period, differ at the two ends.1. Check whether the MPLS OAM settings are the same at the two ends.2. If the MPLS OAM settings are different at the two ends, change them to the same.

If... Then...



Step 2 Cause 2: Severe congestion occurs on the network.1. If the alarm persists, check whether the bandwidth allocated to the faulty tunnel is fully

used. If the bandwidth of the faulty tunnel is exhausted, increase the bandwidth or eliminatethe sources that transmit a large amount of invalid data.

If... Then...



Step 3 Cause 3: A certain board is faulty.1. Check whether the remote NE reports the COMMUN_FAIL alarm. If yes, you can infer

that the remote NE is being reset. Wait until the COMMUN_FAIL alarm clears.

If... Then...


The alarm persists Go to the next step.

2. Check whether the local NE and the remote NE report alarms related to optical modules orboards, such as HARD_BAD and LSR_NO_FITED. If yes, clear these alarms first.

3. Then, check whether the MPLS_TUNNEL_LOCV alarm clears.

If... Then...



Step 4 Cause 4: The physical link between the two ends is faulty.1. Check whether any fiber or cable is damaged. If yes, replace the damaged fiber or cable.

----End




444

A.3.178 MPLS_TUNNEL_MISMATCH

Description

The MPLS_TUNNEL_MISMATCH is an alarm indicating that the trail termination sourceidentifiers (TTSIs) on the tunnel do not match with the specified one. This alarm is reported ifno CV/FFD packets with correct TTSIs are received in three consecutive CV/FFD periods.

Attribute



Parameters

None.


When this alarm occurs, services are interrupted or packets from other tunnels are received.

Possible Causesl Cause 1: The tunnel settings are incorrect. For example, the LSR IDs or tunnel IDs differ

at the two ends of the tunnel.


Procedure

Step 1 Cause 1: The tunnel settings are incorrect. For example, the LSR IDs or tunnel IDs differ at thetwo ends of the tunnel.

1. Check whether the tunnel settings are the same at the two ends.

l If the source NE is an ingress node, Sink Node is the LSR ID of the sink NE. If the sinkNE is an egress node, Source Node is the LSR ID of the source NE.

l Tunnel IDs of the source NE and sink NE of a tunnel must be set to the same.

2. If the tunnel IDs are different, change them to the same.


1. Check whether any fiber or cable is misconnected between the two ends. If yes, connectthe fiber or cable properly.

----End

Related Information

None.



445

A.3.179 MPLS_TUNNEL_MISMERGE

Description

The MPLS_TUNNEL_MISMERGE is an alarm indicating that the trail termination sourceidentifiers (TTSIs) are mismerged in the tunnel. This alarm is reported if the CV/FFD packetswith correct TTSIs and those with wrong TTSIs are received in three consecutive CV/FFDperiods.

Attribute



Parameters

None.


When this alarm occurs, the packets from other tunnels are received.

Possible Causesl Cause 1: Multiple tunnels are configured with the same label.


Procedure

Step 1 Cause 1: Multiple tunnels are configured with the same label.

1. Check whether multiple tunnels are configured with the same label.

2. If multiple tunnels are configured with the same label, delete the redundant labels or changethe label of each tunnel to a unique value.


1. Check whether any fiber or cable is misconnected between the two ends. If yes, connectthe fiber or cable properly.

----End

Related Information

On the NE, the label of each MPLS tunnel is unique.

A.3.180 MPLS_TUNNEL_OAMFAIL



446

DescriptionThe MPLS_TUNNEL_OAMFAIL is an alarm indicating that the OAM protocol negotiationbetween the two ends of the tunnel fails.

Attribute



ParametersNone.

Impact on the SystemWhen this alarm occurs, services are switched to the backup network and the LPT closes theaccess port of the remote NE at the same time.

Possible Causesl Cause 1: The OAM function is enabled and the detection mode is auto-sensing on one end

and is disabled on the other end.l Cause 2: The tunnel is unavailable when the OAM function is enabled and the detection

mode is auto-sensing.

Procedure

Step 1 Cause 1: The OAM function is enabled and the detection mode is auto-sensing on one end andis disabled on the other end.1. Enable the OAM function.

Step 2 Cause 2: The tunnel is unavailable when the OAM function is enabled and the detection modeis auto-sensing.1. Check whether the sink node of the alarmed tunnel reports the HARD_BAD,

ETH_LOS, or R_LOS alarm.2. If yes, clear the alarm. After the OAM protocol negotiation succeeds, the

MPLS_TUNNEL_OAMFAIL alarm clears.

----End




447

A.3.181 MPLS_TUNNEL_SD

Description

The MPLS_TUNNEL_SD is an alarm of signal degrade on the tunnel. This alarm is reportedwhen the packet loss rate of the CV/FFD crosses the SD threshold but is lower than the SFthreshold.

Attribute



Parameters

None.


Services degrade and moderate packet loss occurs.

Possible Causesl Cause 1: Excessive bit errors occur.

l Cause 2: The bandwidth of the tunnel is fully used.

Procedure

Step 1 Cause 1: Excessive bit errors occur.

1. Check whether the FCS_ERR alarm is reported. If yes, clear the FCS_ERR alarm and thencheck whether the MPLS_TUNNEL_SD alarm is cleared.

2. If the alarm persists, proceed to cause 2.

Step 2 Cause 2: The bandwidth of the tunnel is fully used.

1. Check whether the bandwidth allocated to the tunnel is fully used. If the bandwidth of thefaulty tunnel is exhausted, increase the bandwidth or eliminate the sources that transmit alarge amount of invalid data. Check whether the alarm clears.

----End

Related Information

None.



448

A.3.182 MPLS_TUNNEL_SF

Description

The MPLS_TUNNEL_SF is an alarm indicating that the tunnel signal degrades severely. Thisalarm is reported if the loss ratio of the CV/FFD packets is higher than the SF threshold and CV/FFD packets are received in three consecutive periods.

Attribute



Parameters

None.


When this alarm occurs, the quality of service degrades severely and a large number of packetsare lost.

Possible Causesl Cause 1: Excessive bit errors occur.

l Cause 2: The bandwidth of the tunnel is fully used.

Procedure

Step 1 Cause 1: Excessive bit errors occur.

1. On the NMS, check whether the FCS_ERR alarm is reported. If yes, clear theFCS_ERR, and then check whether the MPLS_TUNNEL_SF is cleared.

2. If the MPLS_TUNNEL_SF persists, go to Cause 2.

Step 2 Cause 2: The bandwidth of the tunnel is fully used.

1. On the NMS, check whether the bandwidth of the tunnel is fully used. If the bandwidth ofthe tunnel is fully used, increase the bandwidth allocated to the tunnel or eliminate anysource that transmits a large amount of invalid data. Check whether the alarm is cleared.

----End

Related Information

None.



449

A.3.183 MPLS_TUNNEL_UNKNOWN

Description

The MPLS_TUNNEL_UNKNOWN is an alarm indicating that certain unknown defects existon the tunnel. This alarm is reported when the port receives the CV packets and the FFD packets.

Attribute



Parameters

None.


When this alarm occurs, the OAM function is affected.

Possible Causesl Cause 1: The OAM settings differ at the two ends.l Cause 2: The NE receives packets from an unknown source.

Procedure

Step 1 Cause 1: The OAM settings differ at the two ends.1. If the MPLS_TUNNEL_UNKNOWN alarm is reported transiently, check whether Tunnel

OAM configuration is changed on the local NE and the opposite NE.2. If the local NE and the opposite NE have different Tunnel OAM configuration, the

MPLS_TUNNEL_UNKNOWN alarm is reported transiently and then theMPLS_TUNNEL_LOCV alarm is reported. Ensure that both ends have the same TunnelOAM configuration. Then, check whether the alarm is cleared.

Step 2 Cause 2: The NE receives packets from an unknown source.1. Check whether there is any service configured between the NE and an unknown source, or

whether the NE is connected to an unknown source.2. If yes, modify the incorrect configuration or reconnect the fibers.

----End

Related Information

None.

A.3.184 MS_AIS



450

DescriptionThe MS_AIS is an alarm indicating multiplex section alarms. This alarm is reported when theboard detects that bits 6-8 of the K2 byte in the three consecutive frames are 111.

Attribute



ParametersNone.

Impact on the SystemThe services on the line port are interrupted. If the services are configured with protection,protection switching may be triggered.

Possible Causesl Cause 1: The transmit unit of the opposite station 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 station is faulty.1. Replace the line board at the opposite site based on the type of the alarmed board.

If... Then...

The line board reports the alarm Replace the line board at the opposite end.

The IF board reports the alarm Replace the IF board at the opposite end.

2. Replace the board and then check whether the alarm is cleared.

If... Then...

The alarm is cleared after the board replacement End the fault handling.

The alarm persists after the board replacement Go to the next step.

3. Replace the system control, cross-connect, and timing board at the opposite end.

If... Then...

The alarm is cleared after the board replacement End the fault handling.

The alarm persists after the board replacement Go to Cause 2.

Step 2 Cause 2: The receive unit of the local site is faulty.1. Replace the alarmed board.

----End



451

Related Information

None.

A.3.185 MS_CROSSTR

Description

The MS_CROSSTR is an alarm indicating that a performance indicator of the multiplex sectioncrosses the threshold. This alarm is reported when the board detects that the MS BERperformance indicator crosses the preset threshold.

Attribute


Minor Service alarm

Parameters


Name Meaning



Parameter 2, Parameter 3 Parameter 2 is always 0x00. Parameter 3 indicate the ID of aperformance event that causes the alarm and has the followingmeanings:

l 0x10: MSBBEl 0x11: MSESl 0x12: MSSESl 0x13: MSFEBBEl 0x14: MSFEESl 0x15: MSFESESl 0x16: MSUASl 0x17: MSCSESl 0x18: MSFECSESl 0x21: MSFEUAS



452


A large number of bit errors occur in the services, and the services may be interrupted.

Possible Causesl Cause 1: Services are interrupted for a long time.

l Cause 2: The MS BER performance indicator crosses the preset threshold.

Procedure

Step 1 Cause 1: Services are interrupted for a long time.

NOTEHandle the alarm as follows if the value of parameter 3 is 0x16:

1. Check whether fibers are properly connected. If not, connect the fibers again according toplanning information.

2. Check whether cross-connections are configured for service ports. If not, configure cross-connections again according to planning information.

Step 2 Cause 2: The MS BER performance indicator crosses the preset threshold.

1. Check the threshold crossing records of MS BER performance events to find out theperformance event that crosses the preset threshold. For details, see 8.3.8 Browsing thePerformance Event Threshold-Crossing Records.

2. Handle the performance event that crosses the threshold.

----End

Related Information

None.

A.3.186 MS_RDI

Description

The MS_RDI is an alarm indicating that data reception at the remote end of the multiplex sectionfails. This alarm is reported when the board detects that bits 6-8 of the K2 byte are 110.

Attribute



Parameters

None.



453

Impact on the SystemThe services on the local site are not affected. The services received by the opposite station,however, are interrupted.

Possible CausesCause 1: The local site receives a message from the opposite station, and the message indicatesthat data reception at the remote end of the multiplex section fails.

Procedure

Step 1 Cause 1: The local site receives a message from the opposite station, and the message indicatesthat data reception at the remote end of the multiplex section fails.1. Rectify the fault that occurs on the opposite station.

The possible alarms are as follows:

l MS_AISl R_LOSl R_LOFl B2_EXCl B2_SD

----End


A.3.187 MS_REI

DescriptionThe MS_REI is an alarm indicating that bit errors occur on the remote end of the multiplexsection. This alarm is reported when the board detects that the M1 byte is non-zero.

Attribute


Warning Communication alarm

ParametersNone.

Impact on the SystemThe services on the local site are not affected. The services received by the opposite station,however, has bit errors.



454

Possible CausesCause 1: The local site receives a message from the opposite station, and the message indicatesthat bit errors occur on the remote end of the multiplex section.

Procedure

Step 1 Cause 1: The local site receives a message from the opposite station, and the message indicatesthat bit errors occur on the remote end of the multiplex section.1. Handle the MS_BBE performance event on the port of the opposite station.

----End


A.3.188 MSAD_CROSSTR

DescriptionThe MSAD_CROSSTR is an alarm indicating that the adaptation performance indicator of themultiplex section crosses the threshold. This alarm is reported when the board detects that anAU pointer adaptation performance indicator crosses the preset threshold.

Attribute


Minor Service alarm


Name Meaning




l 0x2a: AUPJCHIGHl 0x2b: AUPJCLOWl 0x2c: AUPJCNEW



455

Impact on the SystemBit errors may occur in the services.

Possible CausesCause 1: An AU pointer adaptation performance indicator crosses the preset threshold.

Procedure

Step 1 Cause 1: An AU pointer adaptation performance indicator crosses the preset threshold.1. Check the threshold crossing records of the AU pointer adaptation performance events to

find out the performance event that crosses the preset threshold. For details, see 8.3.8Browsing the Performance Event Threshold-Crossing Records.


----End


A.3.189 MULTI_RPL_OWNER

DescriptionThe MULTI_RPL_OWNER is an alarm indicating that the ring network contains severalRPL_OWNER nodes.

Attribute




Name Meaning

Parameter 1, Parameter 2 Indicate the ID of the ERPS instance.

Impact on the SystemThe ERPS protection fails and the services configured on the Ethernet ring are interrupted.



456

Possible Causes

Cause 1: The related data is configured incorrectly.

Procedure

Step 1 Cause 1: The related data is configured incorrectly.

1. Reconfigure the ERPS protection. For details, see Creating Ethernet Ring ProtectionInstances.

----End

Related Information

The following table describes the meanings of the parameters in the MULTI_RPL_OWNERalarm reported by the EMS6.

Name Meaning

Parameter 1 to Parameter 4 Indicates the port ID.

Parameter 5, Parameter 6 Indicate the ID of the ERPS instance.

A.3.190 MW_AM_TEST

Description

The MW_AM_TEST is an alarm indicating that the IF port is in the AM testing state.

Attribute


Minor Other alarms

Parameters

None.


The transmission capacity is reduced during the AM test.

Possible Causesl Cause: The AM testing is enabled.



457

Procedure

Step 1 Cause: The AM testing is enabled.

1. After the AM testing ends, disable the AM testing.

----End

Related Information

None.

A.3.191 MW_BER_EXC

Description

The MW_BER_EXC is an alarm indicating that excessive bit errors occur on the radio link. Thisalarm is reported when the bit errors on the radio link exceed the specified threshold (10-3 bydefault).

Attribute


Minor Service alarm

Parameters

None.


When the MW_BER_EXC alarm occurs, the service on the port is interrupted.

Possible Causesl Cause 1: Signal attenuation on the radio link is very heavy.

l Cause 2: The transmit unit of the opposite station 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: Signal attenuation on the radio link is very heavy.

1. At the local end, check whether the receive power of the ODU is normal. If yes, determinethe abnormality and take proper measures. For details, see Querying the Historical TransmitPower and Receive Power



458

If... Then...

The RSL is lower than the receiversensitivity

Follow the steps:

1. Check the installation of the antenna to ensurethat the azimuth of the antenna meets therequirement.

2. Check the antenna direction. Check whetherthe received signal is from the main lobe.If the antenna direction does not meet therequirement, adjust the antenna in a widerange.

3. Check whether the setting of the polarizationdirection of the antenna is correct. Adjust theincorrect polarization direction.

4. Check whether the antenna gain at both thetransmit and receive ends meets thespecifications. Replace the antennas that donot meet the requirement.

5. Check whether any mountain or buildingobstacle exists in the transmit direction.If yes, contact the network planningdepartment for proper modification of theplanning design, hence preventing the blockof the mountain or building obstacle.

The RSL is higher than the specifiedRSL of the network. The offset value istens of decibels. 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, it indicates that there is co-channelinterference that may affect the long-termavailability and errored-secondperformance of the system.

2. Use a spectrum analyzer to analyze theinterference source.

3. Contact the spectrum managementdepartment to clear the interference spectrumor change plans to minimize the interference.



459

If... Then...

The RSL is lower than the specified RSLof the network. The offset value is tens ofdecibels. The duration is from tens ofseconds to several hours.

Slow down fading occurs. Generally, the radiolink may be faulty in both directions, becauseslow fading is imposed by the transmission path.Contact the network planning department 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, therefore reducing the multipathfading.

l Adjust the RF configuration to make the linksin the 1+1 SD configuration.

l If the links are configured with the 1+1 SDprotection, adjust the height offset betweentwo antennas to make the receive power of oneantenna stronger than the receive power of theother antenna.

l Increase the fading margin.

Step 2 Cause 2: The transmit unit of the opposite station is faulty.

Locate the fault by looping back the opposite station and excluding the position one by one.Follow the steps:

1. Perform an inloop on the IF port at the opposite end. For details, see 8.5.6 Setting Loopbackfor the IF Board. Check whether the fault at the opposite end is rectified after the loopback.

If... Then...

The fault at the opposite end is not rectified Replace the IF board.

The fault at the opposite end is rectified Go to the next step.

2. Check whether the cable connector is prepared according to the requirement. If any cableconnector does not meet the requirement, make a new connector.

3. Check whether the IF cable is wet, broken, or pressed. Replace the cable that does not meetthe requirement.

4. Then, check whether the fault at the opposite end is rectified.

If... Then...

The fault at the opposite end is not rectified Replace the ODU at the opposite end.



460

If... Then...

The fault at the opposite end is rectified End the alarm handling.

Step 3 Cause 3: The receive unit of the local site is faulty.


1. Perform an inloop on the IF port at the local end. For details, see 8.5.6 Setting Loopbackfor the IF Board. Check whether the fault at the local end is rectified after the loopback.

If... Then...






If... Then...

The fault at the opposite end is not rectified Replace the ODU at the local end.


Step 4 Cause 4: An interference event occurs.

1. Check whether any co-channel interference occurs.

a. Mute the ODU at the opposite end.

b. Check the RSL at the local end. For details, see Configuring the IF/ODU Informationof a Radio Link. If the RSL exceeds -90 dBm, it indicates that there is co-channelinterference that may affect the long-term availability and errored-secondperformance of the system.

2. Check whether any adjacent channel interference occurs.


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.



461

4. Contact the spectrum management department to clear the interference spectrum or changeplans to minimize the interference.

----End

Related Information

None.

A.3.192 MW_BER_SD

Description

The MW_BER_SD is an alarm indicating that signal deteriorates on the radio link. This alarmis reported when the bit errors on the radio link exceed the specified threshold (10-6 by default)but does not reach the MW_BER_EXC alarm threshold (10-3 by default).

Attribute


Minor Service alarm

Parameters

None.


The service performance on the port deteriorates. If the equipment is configured with 1+1 FD/SD protection, switching on the channel side may be triggered.





Procedure

Step 1 Cause 1: Signal attenuation on the radio link is very heavy.

1. At the local end, check whether the receive power of the ODU is normal. If yes, determinethe abnormality and take proper measures. For details, see Querying the Historical TransmitPower and Receive Power



462

If... Then...


Follow the steps:















463

If... Then...













If... Then...






If... Then...




464

If... Then...





If... Then...






If... Then...






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, it indicates that there is co-channelinterference that may affect the long-term availability and errored-secondperformance of the system.



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.



3. Use a spectrum analyzer to analyze the interference source.



465

4. Contact the spectrum management department to clear the interference spectrum or changeplans to minimize the interference.

----End

Related Information

None.

A.3.193 MW_CFG_MISMATCH

Description

The MW_CFG_MISMATCH is an alarm of configuration mismatch on radio links. This alarmoccurs when an NE detects configuration mismatch on both ends of a radio link. For example,the number of E1 signals, the number of STM-1 signals, AM enabling, 1588 overhead enabling,modulation mode may be configured differently on both ends of a radio link.

Attribute



Parameters


Name Meaning

Parameter 1 Indicates the cause of the fault.

l 0x01: The number of E1 signals is different.l 0x02: The AM enabling is different.l 0x03: The 1588 overhead enabling is different.l 0x04: The modulation mode is different.l 0x05: The service mode is different.l 0x06: The number of STM-1 signals is different.l 0x09: The IP header compression enabling is different.

Parameter 2 When the value of Parameter 1 is 0x09:

l 0x01: The air interface compression at L2 is different.l 0x02: The air interface compression at L3 is different.

When Parameter 1 takes another value, Parameter 2 is reserved.



466

Impact on the SystemWhen this alarm occurs, the service configuration cannot take effect or services are interrupted.After the NE is power cycled or reset, this alarm may still affect services.

Possible Causesl Cause 1: The number of E1 signals is different on both ends of a radio link.l Cause 2: The AM enabling is different on both ends of a radio link.l Cause 3: The 1588 overhead enabling is different on both ends of a radio link.l Cause 4: The modulation mode is different on both ends of a radio link.l Cause 5: The service mode is different on both ends of a radio link.l Cause 6: The IP header compression is different on both ends of a radio link.l Cause 7: The air interface compression at L2 or L3 is different.l Cause 8: The number of STM-1 signals is different on both ends of a radio link.

ProcedureStep 1 Determine the possible cause of the alarm according to the alarm parameters.

Step 2 Check the configuration on both ends of the radio link. Ensure that the configuration is the sameon both ends of the radio link. For details, see Managing Radio Links.

----End


A.3.194 MW_CONT_WAVE

DescriptionThe MW_CONT_WAVE is an alarm of continuous wave. This alarm occurs if the continuouswave function is enabled on the IF board and clears after the continuous wave function isdisabled.

Attribute



ParametersNone.

Impact on the SystemIf the continuous wave function is enabled, radio links cannot transmit services.



467

Possible Causes

Cause 1: The continuous wave function is enabled.

Procedure

Step 1 Disable the continuous wave function.

1. In NE Explorer, select the IF board.

2. Choose Configuration > IF Interface from the Function Tree.

3. Select the alarmed port from IF Attribution.

4. Set 350MHz Consecutive Wave Status to Stop.

----End

Related Information

None.

A.3.195 MW_E1_LOST

Description

The MW_E1_LOST is an alarm indicating that E1 services are lost. This alarm occurs when theAM downshifts the modulation scheme or E1 bandwidth decreases in the current modulationscheme.

Attribute



Parameters


Name Meaning

Parameter 1 Indicates the timeslots of E1 services.


Some E1 services are lost.



468

Possible Causesl Cause 1: The AM downshifts the modulation scheme.

l Cause 2: E1 bandwidth decreases in the current modulation scheme.

Procedure

Step 1 Cause 1: The AM downshifts the modulation scheme.

1. Handle the alarm according to AM_DOWNSHIFT.

Step 2 Cause 2: E1 bandwidth decreases in the current modulation scheme.

1. Check whether the decrease of E1 bandwidth is caused by incorrect operations. If yes,restore E1 bandwidth to an appropriate value; if not, ignore the alarm.

----End

Related Information

None.

A.3.196 MW_FEC_UNCOR

Description

The MW_FEC_UNCOR is an alarm indicating that radio frames forward error correction (FEC)encoding cannot be corrected.

Attribute



Parameters

None.


Bit errors occur in the services. If the equipment is configured with 1+1 FD/SD protection, HSMchannel protection switching may be triggered.







469

Procedure

Step 1 Cause 1: Signal attenuation on the radio link is very heavy.1. At the local end, check whether the receive power of the ODU is normal. If yes, determine

the abnormality and take proper measures. For details, see Querying the Historical TransmitPower and Receive Power

If... Then...


Follow the steps:








470

If... Then...



















471




If... Then...






If... Then...






If... Then...






If... Then...



Step 4 Cause 4: An interference event occurs.1. Check whether any co-channel interference occurs.

a. Mute the ODU at the opposite end.b. Check the RSL at the local end. For details, see Configuring the IF/ODU Information

of a Radio Link. If the RSL exceeds -90 dBm, it indicates that there is co-channel



472

interference that may affect the long-term availability and errored-secondperformance of the system.


a. Mute the ODU at the opposite end.b. Adjust the radio working mode at the local end and use the minimum channel spacing.

For details, see Configuring the IF/ODU Information of a Radio Link.c. Decrease the received frequency at the local end by a half of the channel spacing. For

details, see Configuring the IF/ODU Information of a Radio Link.d. Test and record the RSL.e. Increase the received frequency at the local end, with a step length of 0.5 MHz or 1

MHz, and record the RSL accordingly until the received frequency is equal to theoriginal received frequency plus a half of the channel spacing.


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

plans to minimize the interference.

----End

Related Information

None.

A.3.197 MW_LIM

Description

The MW_LIM is an alarm indicating that a mismatched radio link identifier is detected. Thisalarm is reported if an IF board detects that the link ID in the radio frame overheads is inconsistentwith the specified link ID.

Attribute



Parameters

None.


After the IDU IF board reports the MW_LIM alarm, the IF board inserts the AIS alarm into thereceived signal. Then, the services on the radio link are interrupted. If the services are configuredwith SNCP, protection switching may be triggered.



473

Possible Causesl Cause 1: The link ID of the local site does not match with the link ID of the opposite station.

l Cause 2: The services on other radio links are received due to the incorrect configurationof the radio link receive frequency at the local or opposite station.

l Cause 3: The antenna receives the radio from the other stations, because the direction ofthe antenna is set incorrectly.

l Cause 4: The polarization direction of the XPIC is incorrect.

Procedure

Step 1 Cause 1: The link ID of the local site does not match with the link ID of the opposite station.1. Check whether the link ID of the local site matches with the link ID of the opposite station.

For details, see Configuring the IF/ODU Information of a Radio Link. If not, set the linkIDs of the two stations to the same value according to the requirements of the networkingplanning.

Step 2 Cause 2: The services on other radio links are received due to the incorrect configuration of theradio link receive frequency at the local or opposite station.1. Check whether the receive and transmit frequencies of the local site are consistent with the

receive and transmit frequencies of the opposite station. For details, see Configuring theIF/ODU Information of a Radio Link. If not, set the receive and transmit frequencies of thetwo stations again.

Step 3 Cause 3: The antenna receives radio signals from the other stations, because the direction of theantenna is set incorrectly.1. Adjust the direction of the antenna and ensure that the antennas at both ends are aligned.

Step 4 Cause 4: The polarization direction of the XPIC is incorrect.1. If XPIC protection groups are configured, check whether the XPIC configuration is correct.

For details, see Creating an XPIC Workgroup.

a. Check whether the settings of XPIC IF board in polarization direction-V andpolarization direction-H meet the requirement of the planning.

If... Then...

The polarization direction does not meetthe requirement of the planning

Delete the working XPIC group that isconfigured incorrectly and create theother working XPIC group again.

The polarization direction meets therequirement of the planning


b. Check whether Link ID-V and Link ID-H meet the requirement of the planning.

If... Then...

The link ID does not meet therequirement of the planning

Reset the ID of the radio link of the XPICIF board according to the planning. Fordetails, see Creating an XPIC WorkingGroup.



474

If... Then...

The link ID meets the requirement of theplanning


2. Check and modify the XPIC IF board and ODU, and the mapping relationship between the

ODU and the feed bottom. Ensure that the XPIC IF boards in the polarization direction Vof the two ends are interconnected with each other through the radio link in the polarizationdirection V, and the XPIC IF boards in the polarization direction H of the two ends areinterconnected with each other through the radio link in the polarization direction H.

----End

Related InformationThe MW_LIM alarm is generated due to the inconsistency between the specified link ID andthe received link ID. When the MW_LOF alarm is generated on the link, the received link IDis a random value. In this case, the link ID is invalid. The MW_LIM alarm is also suppressedby the MW_LOF alarm.

A.3.198 MW_LOF

DescriptionThe MW_LOF is an alarm indicating that the radio frame is lost.

Attribute



ParametersNone.

Impact on the SystemThe services are interrupted. If the system is configured with protection, protection switchingmay be triggered.

Possible Causesl Cause 1: The other alarms are generated.l Cause 2: In the case of TDM radio services, the IF working modes at the local site and the

opposite station are different. In the case of Integrated IP radio services, the channelbandwidth and modulation modes at the local site and the opposite station are different.

l Cause 3: The operating frequency of the ODU at the local site is inconsistent with theoperating frequency of the ODU at the opposite station.




475

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.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 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 station are different. In the case of Integrated IP radio services, the channel bandwidthand modulation modes at the local site and the opposite station are different.1. In the case of TDM radio services, check whether the working mode of the IF board at the

local site is consistent with the working mode of the IF board at the opposite station. Fordetails, see Configuring the IF/ODU Information of a Radio Link. If not, reset the workingmode of the IF board according to the network planning.

In the case of Hybrid radio services, check whether the channel bandwidth and modulationmodes are the same at both ends. If not, change the channel bandwidth and modulationmodes according to the network planning. For details, see Setting the Hybrid/AMAttributes.

Step 3 Cause 3: The operating frequency of the ODU at the local site is inconsistent with the operatingfrequency of the ODU at the opposite station.1. Ensure that the type of the ODU at the local site is consistent with the type of the ODU at

the opposite station.2. Reset the operating frequency of the ODU according to the network planning. For details,

see Setting ODU Transmit Frequency Attributes.Set the transmit frequency of the local site to the same as the receive frequency of theopposite station. Then, set the receive frequency of the local site to the same as the transmitfrequency of the opposite station.

Step 4 Cause 4: The transmit unit of the opposite station is faulty.1. Check whether any alarms are generated in the equipment of the local site. If yes, take

priority to clear them.The relevant alarms are as follows:l HARD_BADl BD_STATUSl VOLT_LOS



476

l IF_CABLE_OPENl RADIO_MUTEl RADIO_TSL_HIGHl RADIO_TSL_LOWl TEMP_ALARM

2. Locate the fault by looping back the opposite station.

Follow the steps:

a. Perform an inloop on the IF port at the opposite end. For details, see 8.5.6 SettingLoopback for the IF Board. Check whether the fault at the opposite end is rectifiedafter the loopback.

If... Then...



b. Check whether the cable connector is prepared according to the requirement. If anycable connector does not meet the requirement, make a new connector.

c. Check whether the IF cable is wet, broken, or pressed. Replace the cable that does notmeet the requirement.

d. Then, check whether the fault at the opposite end is rectified.

If... Then...

The fault at the opposite end is notrectified

Replace the ODU at the opposite end.



1. Locate the fault by looping back the opposite station.

Follow the steps:

a. Perform an inloop on the IF port at the local end. For details, see 8.5.6 SettingLoopback for the IF Board. Check whether the fault at the local end is rectified afterthe loopback.

If... Then...



b. Check whether the cable connector is prepared according to the requirement. If anycable connector does not meet the requirement, make a new connector.

c. Check whether the IF cable is wet, broken, or pressed. Replace the cable that does notmeet the requirement.

d. Check whether the fault at the local end is rectified.

Step 6 Cause 6: The receive power of the ODU is abnormal.



477

1. At the local site, check whether the receive power of the ODU is abnormal. For details, seeBrowse history performance events. If yes, determine the abnormality and take propermeasures.

If... Then...


Follow the steps:















478

If... Then...











Follow the steps:


a. Mute the ODU at the opposite end.b. Check the RSL at the local end. For details, see Configuring the IF/ODU Information

of a Radio Link. If the RSL exceeds -90 dBm, it indicates that there is co-channelinterference that may affect the long-term availability and errored-secondperformance of the system.


a. Mute the ODU at the opposite end.b. Adjust the radio working mode at the local end and use the minimum channel spacing.

For details, see Configuring the IF/ODU Information of a Radio Link.c. Decrease the received frequency at the local end by a half of the channel spacing. For

details, see Configuring the IF/ODU Information of a Radio Link.d. Test and record the RSL.



479



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

plans to minimize the interference.

----End


A.3.199 MW_RDI

DescriptionThe MW_RDI is an alarm indicating that there are defects at the remote end of the radio link.This alarm is reported when the IF board detects an RDI in the radio frame overheads.

Attribute



ParametersNone.

Impact on the SystemIf the local site is configured with the reverse switching function, the 1+1 switching is triggeredon the IF board when the working and protection IF boards receive the MW_RDI alarm at thesame time. This alarm also indicates that the services received by the opposite station areinterrupted.

Possible CausesAfter detecting a service alarm that is caused by the fault in a radio link, the receive stationreturns a radio link fault indication to the transmit station.

Procedure

Step 1 Clear the radio alarms that occur at the opposite station. The possible alarms are as follows:l MW_LOFl R_LOF



480

l R_LOCl MW_FEC_UNCORl XPIC_LOS

----End


A.3.200 NESF_LOST

DescriptionThe NESF_LOST is an alarm indicating that the NE software is lost. This alarm is reported whenthe system control, cross-connect, and timing board detects that the NE software is lost.

Attribute




Name Meaning




481

Name Meaning

Parameter 2, Parameter 3 Indicate the ID of the routine inspection object.

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.pgal 0x1f: ofs1/hwx/extbios.hwxl 0x20: ofs2/hwx/extbios.hwxl 0x21: ofs1/hwx/luexbios.hwxl 0x22: ofs2/hwx/luexbios.hwx



482

Name Meaning

Parameter 4 Indicates the specific alarm cause when a different bit is 1.

l 0x01: If the first bit is 1, it indicates that the file does not exist.l 0x02: If the second bit is 1, it indicates that verification of the

file fails.

Impact on the SystemIf the NE software does not exist in the active and standby areas, an NE cannot be restarted afterit is powered off or reset.

Possible Causesl Cause 1: No new NE software is loaded after the existing NE software is erased.l Cause 2: Loading the NE software is unsuccessful.l Cause 3: A certain board 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 is unsuccessful.

1. Check whether the alarm is caused by the loading operation.

If... Then...

The alarm is caused by the loadingoperation

Contact the Huawei technical supportengineers to reload the software.

The alarm is not caused by the loadingoperation


Step 2 Cause 3: A certain board is faulty.1. For details, see 6.9 Replacing the System Control, Switch and Timing Board.

----End


A.3.201 NESOFT_MM

DescriptionThe NESOFT_MM is an alarm indicating that the first software system is different from thesecond software system. This alarm is reported when the NE detects that the first software systemand the second software system of the system control, cross-connect, and timing board mismatchwith each other.



483

Attribute




Name Meaning

Parameter 1 Indicates the location of the file.l 0x01: the files in the flash memoryl 0x02: the software that is currently runningl 0x03: the software in the CF card



484

Name Meaning

Parameter 2, Parameter 3 Indicate the IDs of the inconsistent files in the flash memory of thesystem control board if the value of Parameter 1 is 0x01,l 0x01: FPGA of the system control board in 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.pgal 0x1f: ofs1/hwx/luexbios.hwxl 0x20: ofs2/hwx/luexbios.hwxl 0x21: ofs1/fpga/plc034.pgal 0x22: ofs2/fpga/plc034.pga

Indicate the IDs of the inconsistent files in the currently runningsoftware if the value of Parameter 1 is 0x02.

l 0x01: NeSoft(D)



485

Name Meaning

l 0x02: Platform(D)l 0x04: ExtBiosl 0x05: Logicl 0x06: Dsp

Parameter 4 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.l 0x0c: The file versions in the master and slave areas of a single

system control board are inconsistent and the file versions onthe active and standby system control boards are alsoinconsistent.

Impact on the Systeml This alarm affects active/standby switching of system control boards if the active and

standby system control boards have different NE software versions.

l If no NE software exists in the flash memory, the system is unable to restart after power-off or reset.

Possible Causesl Cause 1: The software running on the active and standby SCC boards has different versions.

l Cause 2: The software stored in the ofs1 and ofs2 areas of the active SCC board has differentversions.

l Cause 3: The software stored in the mapping directories of active and standby SCC boardshas different versions.

Procedure

Step 1 Contact Huawei technical support engineers for reloading the software.

----End

Related Information

None.

A.3.202 NESTATE_INSTALL

Description

The NESTATE_INSTALL is an alarm indicating that the NE is in the install state.



486

Attribute



Parameters

None.


The NE fails to work.

Possible Causes

Cause 1: The NE database check fails.

Procedure

Step 1 Cause 1: The NE database check fails.

1. Restore the data from the backup database on the CF card.

----End

Related Information

None.

A.3.203 NO_BD_SOFT

Description

The NO_BD_SOFT is an alarm indicating that the board software is lost.

Attribute



Parameters




487

Name Meaning


Parameter 2, Parameter 3 Indicates the number of the lost file.

Impact on the Systeml If the board software is lost, the board fails to work normally.l If the FPGA is lost, the FPGA does not have a backup copy.

Possible CausesCause 1: The software fails to be loaded.

Procedure

Step 1 Cause 1: The software fails to be loaded.1. Contact the Huawei technical support engineers to reload the software.

----End


A.3.204 NP1_MANUAL_STOP

DescriptionThe NP1_MANUAL_STOP is an alarm indicating that the N+1 protection protocol is disabledmanually.

Attribute




Name Meaning

Parameter 1, Parameter 2 Indicates the ID of the alarmed protection group. For example, 0x01indicates that the alarm is reported by protection group 1.



488

Impact on the SystemThe N+1 protection may fail, or the protection switching may fail.

Possible CausesCause 1: The N+1 protection protocol is disabled manually.

Procedure

Step 1 Cause 1: The N+1 protection protocol is disabled manually.1. Start the N+1 protection protocol.

----End


A.3.205 NP1_SW_FAIL

DescriptionThe NP1_SW_FAIL is an alarm indicating that the N+1 protection switching fails.

Attribute




Name Meaning

Parameter 1, Parameter 2 Indicates the ID of the alarmed protection group. For example, 0x01indicates that the alarm is reported by protection group 1.

Impact on the SystemThe services cannot be switched. If the current paths are unavailable, the services are interrupted.

Possible Causesl Cause 1: The parameters of the N+1 protection for the alarmed node are set incorrectly.



489

l Cause 2: The network-wide N+1 protection protocol runs abnormally.

Procedure

Step 1 Cause 1: The parameters of the N+1 protection for the alarmed node are set incorrectly.1. Check whether the parameters of the N+1 protection are set correctly according to the

planning. For details, see Creating an N+1 Protection Group.

If... Then...

The parameters of the N+1 protection areset incorrectly

Set the parameters of the N+1 protectioncorrectly.

The parameters of the N+1 protection areset correctly

Go to Cause 2.

Step 2 Cause 2: The network-wide N+1 protection protocol runs abnormally.1. Stop and restart the protocol manually. For details, see Starting/Stopping the N+1

Protection Protocol.

If... Then...

The alarm is cleared after the protocol isrestarted.


The alarm persists after the protocol isrestarted

Contact the Huawei technical supportengineers to handle the alarm.

----End


A.3.206 NP1_SW_INDI

DescriptionThe NP1_SW_INDI is an alarm indicating that the N+1 protection switching is detected.

Attribute






490

Name Meaning

Parameter1, Parameter 2 Indicates the ID of the alarmed protection group. For example, 0x01indicates that the alarm is reported by protection group 1.

Impact on the SystemDuring the N+1 protection switching, the services are interrupted. After the N+1 switching iscomplete, the services are restored to normal. After the switching starts and before the switchingis complete, the extra services are interrupted.

Possible CausesCause 1: The N+1 protection switching is performed.

Procedure

Step 1 Cause 1: The N+1 protection switching is performed.1. Find out the cause of switching, and take appropriate measures.

----End


A.3.207 NTP_SYNC_FAIL

DescriptionThe NTP_SYNC_FAIL is an alarm indicating that NTP time synchronization fails.

Attribute



ParametersNone.

Impact on the SystemTime on the alarmed NE is different from time on the NTP server. The records on the NE, suchas performance events, alarms, and operations, cannot be kept with exact time.

Possible Causesl Cause 1: The NTP server is not configured or is configured incorrectly.l Cause 2: The NTP server cannot communicate with the NE.



491

l Cause 3: The NTP server fails.

Procedure

Step 1 Cause 1: The NTP server is not configured or is configured incorrectly.1. Configure the NTP server correctly.2. Re-configure the NTP parameters for the NE.

Step 2 Cause 2: The NTP server cannot communicate with the NE.1. Check whether the cable connecting the gateway NE to the NTP server is normal. If not,

rectify the connection fault.2. Check whether the DCN communication between the NTP server and the NE is normal. If

not, configure the DCN communication correctly.

Step 3 Cause 3: The NTP server fails.1. Troubleshoot the NTP server.

----End


A.3.208 OCD

DescriptionThe OCD is an alarm indicating out-of-cell delimitation. This alarm occurs when the celldelimitation state machine is in the HUNT or PRESYN state.

Attribute



ParametersNone.

Impact on the SystemWhen the OCD alarm occurs, all the services in the receive direction of the alarmed ATM portlose cells.

Possible Causesl Cause 1: A great number of bit errors occur in the receive path. The receive path reports

the alarms indicating excessive bit errors, such as B1_EXC, B2_EXC, and B3_EXC.l Cause 2: The ATM processing chip of the board is faulty.



492

Procedure

Step 1 Cause 1: A great number of bit errors occur in the receive path. The receive path reports thealarms indicating excessive bit errors, such as B1_EXC, B2_EXC, and B3_EXC.1. Check whether the B1_EXC, B2_EXC, or B3_EXC alarm occurs in the receive path.2. If yes, clear these alarms first, and then check whether the OCD alarm is cleared.

Step 2 Cause 2: The ATM processing chip of the board is faulty.1. Perform a cold reset on the board that reports the OCD alarm. For details, see 8.6.1 Cold

Reset.2. If the OCD alarm persists, replace the alarmed board. For details, see 6.5 Replacing the

Smart E1 Board.

----End


A.3.209 ODC_BATTERY_CURRENT_ABN

DescriptionThe ODC_BATTERY_CURRENT_ABN is an alarm indicating that the current of the storagebattery is abnormal.

Attribute




Name Meaning


l 0x01: The internal current loop of the storage battery is broken.l 0x02: The recharge current of the storage battery is very high.l 0x03: The storage battery is discharged unevenly.

Impact on the SystemThe equipment may fail to work normally, or event the equipment is damaged.



493

Possible Causesl Cause 1: The circuit breaker or fuse of the storage battery in the cabinet is off.

l Cause 2: The positive and negative polarities of the storage battery are connected inversely.

l Cause 3: The power module frame is faulty.

l Cause 4: The power monitoring module is faulty.

l Cause 5: The power module is faulty.

Procedure

Step 1 Cause 1: The circuit breaker or fuse of the storage battery in the cabinet is off.

If... Then...

The circuit breaker of the storage battery is open Close the circuit breaker.

The fuse of the storage battery is broken Replace the fuse.

Step 2 Cause 2: The positive and negative polarities of the storage battery are connected inversely.

1. Connect the positive and negative polarities of the storage battery correctly.

Step 3 Cause 3: The power module frame is faulty.

1. Check whether the power module frame is damaged. If the power module frame is damaged,replace the power module frame.

Step 4 Cause 4: The power monitoring module is faulty.

1. Replace the power monitoring module.

Step 5 Cause 5: The power module is faulty.

1. Check whether the ODC_MDL_ABN alarm is reported.

If... Then...

The ODC_MDL_ABN alarm is reported Rectify the fault by referring the solutionto the ODC_MDL_ABN alarm.

The ODC_MDL_ABN alarm is notreported

Replace the power module.

----End

Related Information

None.

A.3.210 ODC_BATTERY_PWRDOWN

Description

The ODC_BATTERY_PWRDOWN is an alarm indicating that the storage battery fails toprovide power for the equipment.



494

Attribute




Name Meaning


l 0x01: power-off due to low voltagel 0x02: power-off due to NMS controll 0x03: power-off due to human interferencel 0x04: power-off due to high temperature

Impact on the SystemThe equipment does not have backup a power supply.

Possible Causesl Cause 1 of power-off due to NMS control: The storage battery fails to provide power for

the equipment due to NMS control.l Cause 1 of power-off due to local human interference: The BAT button on the front panel

of the PMU is set to OFF.l Cause 1 of power-off due to low voltage: The AC input power is abnormal.l Cause 2 of power-off due to low voltage: The power module is faulty.l Cause 3 of power-off due to low voltage: The power monitoring module is faulty.l Cause 1 of power-off due to high temperature: The temperature that results in power-off

of the storage battery due to high temperature is set to an inappropriate value.l Cause 2 of power-off due to high temperature: The temperature of the storage battery is

very high.l Cause 3 of power-off due to high temperature: The temperature sensor of the power module

is faulty.

Procedure

Step 1 Determine the cause of the alarm according to the alarm parameters displayed on the NMS.

Step 2 Cause 1 of power-off due to NMS control: The storage battery fails to provide power for theequipment due to NMS control.



495

1. Enable the battery to power on the equipment.

Step 3 Cause 1 of power-off due to local human interference: The BAT button on the front panel of thePMU is set to OFF.1. On the front panel of the PMU, hold the BAT ON button for 5-10 seconds to turn on the

storage battery.

Step 4 Cause 1 of power-off due to low voltage: The AC input power is abnormal.1. Query the threshold that results in an alarm when the AC power voltage is abnormal. Then,

determine whether the threshold is appropriate according to the configuration and planninginformation.

If... Then...

The threshold is inappropriate Set the threshold to an appropriate value.

The threshold is appropriate Go to the next step.

2. Check whether the AC circuit breaker is closed.

If... Then...

The AC circuit breaker is open Close the AC circuit breaker.

The AC circuit breaker is closed Go to the next step.

3. Check the connection of the AC power cable.

If... Then...

The connection of the AC power cable is incorrect. Connect the cable properly.

The AC power cable is deteriorated and damaged. Replace the cable.

Step 5 Cause 2 of power-off due to low voltage: The power module is faulty.1. Rectify the fault of the power module by referring to the solution to the

ODC_MDL_ABN alarm.

Step 6 Cause 3 of power-off due to low voltage: The power monitoring module is faulty.1. Rectify the fault of the power monitoring module.

Step 7 Cause 1 of power-off due to high temperature: The temperature that results in power-off of thepower module due to high temperature is set to an inappropriate value.1. Query the threshold that results in an alarm due to high temperature. Then, determine

whether the threshold is appropriate according to the configuration and planninginformation.

If... Then...


The threshold is appropriate Perform the operations required when the alarm isgenerated by cause 2 of power-off due to hightemperature.

Step 8 Cause 2 of power-off due to high temperature: The temperature of the storage battery is veryhigh.1. Replace the storage battery.



496

Step 9 Cause 3 of power-off due to high temperature: The temperature sensor of the power module isfaulty.1. Replace the temperature sensor of the power module.

----End


A.3.211 ODC_DOOR_OPEN

DescriptionThe ODC_DOOR_OPEN is an alarm indicating that the door of an outdoor cabinet is open.

Attribute



ParametersNone.

Impact on the SystemIf the cabinet door is open, the temperature, ambient humidity, and dust-proof measures of theequipment are affected by the external environment.

In addition, the equipment may be damaged or stolen.

Possible Causesl Cause 1: The door access alarm is set incorrectly.l Cause 2: The cabinet door is open.l Cause 3: The cable between the door sensor and the monitor device is connected incorrectly.l Cause 4: The door sensor is faulty.l Cause 5: The monitor device is faulty.l Cause 6: No door sensor is installed.

Procedure

Step 1 Cause 1: The door access alarm is set incorrectly.1. Check whether the door access alarm is set correctly according to the configuration and

planning information.

If... Then...

The door access alarm is set correctly Go to Cause 2.



497

If... Then...

The door access alarm is set incorrectly Set the door access alarm correctly.

Step 2 Cause 2: The cabinet door is open.1. Close the cabinet door.

Step 3 Cause 3: The cable between the door sensor and the monitor device is connected incorrectly.1. Check the cable between the door sensor and the monitor device.

If... Then...

The cable is connected incorrectly or is loose Connect the cable properly.

The cable is deteriorated or damaged Replace the cable.


Step 4 Cause 4: The door sensor is faulty.1. Rectify the fault of the door sensor.2. Then, check whether the alarm clears.

If... Then...



Step 5 Cause 5: The monitor device is faulty.1. Rectify the fault of the monitor device.

Step 6 Cause 6: No door sensor is installed.1. Install a door sensor.

----End


A.3.212 ODC_FAN_FAILED

DescriptionThe ODC_FAN_FAILED is an alarm indicating that the fan is faulty.

Attribute






498


Name Meaning

Parameter 1 Indicates the position of the fault.

l 0x01: The internal fan is faulty.l 0x02: The external fan is faulty.


The cabinet cannot dissipate heat properly. As a result, the equipment may be damaged and theservices may be affected.

Possible Causesl Cause 1: The fan cable is connected incorrectly.

l Cause 2: The fan is faulty.

l Cause 3: The fan is not installed.

Procedure

Step 1 Determine the faulty fan according to the alarm parameters displayed on the NMS.

Step 2 Cause 1: The fan cable is connected incorrectly.

1. Connect the cable properly to the fan according to the specified regulations or rules.

Step 3 Cause 2: The fan is faulty.

1. Replace the fan module.

Step 4 Cause 3: The fan is not installed.

1. Install the TEC module that contains a fan.

----End

Related Information

None.

A.3.213 ODC_HUMI_ABN

Description

The ODC_HUMI_ABN is an alarm indicating that the relative humidity in the cabinetenvironment exceeds the specified threshold.



499

Attribute


Minor Environment alarm

Parameters


Name Meaning


l 0x01: The relative humidity is very high.l 0x02: The relative humidity is very low.


In the case of high relative humidity, the equipment may be damaged. In the case of low relativehumidity, the life of the equipment may be shortened.

Possible Causesl Cause 1: The threshold that results in an alarm is set incorrectly.

l Cause 2: The cable between the humidity sensor and the monitoring equipment is connectedincorrectly.

l Cause 3: The humidity sensor is faulty.

l Cause 4: The associated monitoring equipment is faulty.

Procedure

Step 1 Cause 1: The threshold that results in an alarm is set incorrectly.

1. Check whether the humidity threshold is set correctly according to the configuration andplanning information.

If... Then...

The humidity threshold is set correctly Perform the operations required whenthe alarm is generated due to cause 2.

The humidity threshold is set incorrectly Set the humidity threshold to anappropriate value.

Step 2 Cause 2: The cable between the humidity sensor and the monitoring equipment is connectedincorrectly.



500

If... Then...


The cable is deteriorated and damaged Handle the exceptions of the cable.

The cable is not deteriorated and damaged Perform the operations required when thealarm is generated due to cause 3.

Step 3 Cause 3: The humidity sensor is faulty.1. Rectify the fault of the sensor.2. Check whether the alarm is cleared.

If... Then...


The alarm persists Perform the operations required when the alarm is generateddue to cause 4.

Step 4 Cause 4: The monitoring equipment is faulty.1. Rectify the fault of the monitoring equipment.

----End


A.3.214 ODC_LOAD_PWRDOWN

DescriptionThe ODC_LOAD_PWRDOWN is an alarm indicating that the secondary load is powered off.

Attribute






501

Name Meaning


l 0x01: power-off due to low voltagel 0x02: power-off due to background controll 0x03: power-off due to startup in the case of low temperaturel 0x04: power-off due to high temperature

Impact on the SystemThe services on the secondary load are interrupted.

Possible Causesl Cause 1 of power-off due to NMS control: The load is powered off due to NMS control.l Cause 1 of power-off due to low voltage: The AC input power is abnormal.l Cause 2 of power-off due to low voltage: The power module is faulty.l Cause 3 of power-off due to low voltage: The power monitoring module is faulty.l Cause 1 of power-off due to low temperature: The cabinet temperature is very low.l Cause 2 of power-off due to low temperature: The ambient temperature sensor is faulty.l Cause 1 of power-off due to high temperature: The temperature that results in power-off

of the load due to high temperature is set to an inappropriate value.l Cause 2 of power-off due to high temperature: The cabinet temperature is very high.l Cause 3 of power-off due to high temperature: The ambient temperature sensor is faulty.

Procedure

Step 1 Determine the cause of the alarm according to the alarm parameters displayed on the NMS.

Step 2 Cause 1 of power-off due to NMS control: The load is powered off due to NMS control.1. Turn on the storage battery for the equipment.

Step 3 Cause 1 of power-off due to low voltage: The AC input power is abnormal.1. Query the threshold that results in an alarm when the AC power voltage is abnormal. Then,

determine whether the threshold is appropriate according to the configuration and planninginformation.

If... Then...


The threshold is appropriate Go to the next step.

2. Check whether the AC circuit breaker is closed.

If... Then...





502

3. Check the connection of the AC power cable.

If... Then...

The connection of the AC power cable isincorrect.

Connect the cable properly.

The AC power cable is deteriorated anddamaged.

Handle the exceptions of the cable.

Step 4 Cause 2 of power-off due to low voltage: The power module is faulty.

1. Rectify the fault of the power module by referring to the solution to theODC_MDL_ABN alarm.

Step 5 Cause 3 of power-off due to low voltage: The power monitoring module is faulty.

1. Rectify the fault of the power monitoring module.

Step 6 Cause 1 of power-off due to low temperature: The cabinet temperature is very low.

1. Check whether the heat exchanger works properly.

If... Then...

The heat exchanger does not workproperly

Rectify the fault of the heat exchange.

The heat exchanger works properly Perform the operations required when thealarm is generated by cause 2 of power-offdue to low temperature.

Step 7 Cause 2 of power-off due to low temperature: The ambient temperature sensor is faulty.

1. Replace the temperature sensor of the power module.

Step 8 Cause 1 of power-off due to high temperature: The temperature that results in power-off of theload due to high temperature is set to an inappropriate value.

1. Query the threshold that results in an alarm in the case of power-off due to high temperatureof the load. Then, determine whether the threshold is appropriate according to theconfiguration and planning information.

If... Then...


The threshold is appropriate Perform the operations required when the alarm isgenerated by cause 2 of power-off due to hightemperature.

Step 9 Cause 2 of power-off due to high temperature: The cabinet temperature is very high.

1. Check whether the ambient temperature is very high all the time.

2. Check whether the heat exchanger works properly.

If... Then...

The heat exchanger does not workproperly

Rectify the fault of the heat exchange.



503

If... Then...

The heat exchanger works properly Perform the operations required when thealarm is generated by cause 3 of power-offdue to high temperature.

Step 10 Cause 3 of power-off due to high temperature: The ambient temperature sensor is faulty.1. Replace the ambient temperature sensor.

----End

Related InformationThe secondary load refers to the load that the DC power outlet of the cabinet corresponds to.

A.3.215 ODC_MDL_ABN

DescriptionThe ODC_MDL_ABN is an alarm indicating that the power module is abnormal.

Attribute




Name Meaning

Parameter 1 Indicates the ID of the alarmed power module.

Parameter 2, Parameter 3 Indicates the cause of the alarm.

l 0x01: The power module is switched off.l 0x02: The power module is faulty.l 0x03: The power module stops self-protection.l 0x04: The power module fails to communicate with the power

monitoring module, or the power module is not in position.l 0x05: The outdoor cabinet is not installed with a power module,

and the logical slot for a power module is not set on the NMS.l 0x06: The outdoor cabinet is installed with a power module, but

the logical slot for the power module is not set on the NMS.



504


If the power module is faulty, the loading capability of the power system is affected. As a result,the storage battery may discharge, or even the entire power system of the equipment is poweredoff.

Possible Causesl Cause 1: The power module is not configured on the NMS.

l Cause 2: The power module is not in position, or the power module is not inserted properly.

l Cause 3: The power module is faulty.

l Cause 4: The power monitoring unit is abnormal.

Procedure

Step 1 Cause 1: The power module is not configured on the NMS.

1. Set the logical slot of the power module on the NMS.

Step 2 Cause 2: The power module is not in position, or the power module is not inserted properly.

If... Then...

The power module is not in position Install the power module.

The power module is not inserted securely Install the power module properly.

Step 3 Cause 3: The power module is faulty.

1. Replace the power module.

Step 4 Cause 4: The power monitoring unit is abnormal.

1. Rectify the fault of the power monitoring unit.

----End

Related Information

None.

A.3.216 ODC_POWER_FAIL

Description

The ODC_POWER_FAIL is an alarm indicating that the AC input power voltage and DC outputpower voltage of an outdoor cabinet are abnormal.

Attribute





505


Name Meaning

Parameter 1 Indicates the type of the fault.

l 0x56: The AC input power is very high.l 0x57: The AC input power is very low.l 0x58: The DC output power is very high.l 0x59: The DC output power is very low.l 0x5b: No AC input power is available.l 0x5c: The AC power voltage is abnormal.

Impact on the Systeml If the AC input power voltage is abnormal, the equipment is powered on by the storage

battery and cannot work for a long time.l If the DC output power voltage is abnormal, the services on the equipment are interrupted.

Possible Causesl Cause 1: The AC input power voltage is abnormal.l Cause 2: The DC output power voltage is abnormal.

Procedure

Step 1 Cause 1: The AC input power voltage is abnormal.1. The threshold that results in an alarm due to the AC input power voltage is set incorrectly.

If... Then...

The threshold is set incorrectly Set the threshold to an appropriate value.

The threshold is set correctly Go to the next step.

2. The AC circuit breaker is open.

If... Then...



3. The AC power cable is connected incorrectly.

If... Then...




506

If... Then...


The cable is connected correctly Go to the next step.

4. The AC power grid distributes the power abnormally.

If... Then...

The AC power grid distributes the powerabnormally

Rectify the fault of the power moduleat the base station.

The AC power grid distributes the powernormally


5. The monitoring equipment is faulty.

If... Then...

The monitoring equipment is faulty Rectify the fault of the monitoringequipment.

The monitoring equipment is not faulty Perform the operations required when thealarm is generated due to cause 2.

Step 2 Cause 2: The DC output power voltage is abnormal.

1. The threshold that results in an alarm is set incorrectly.

If... Then...

The threshold is set incorrectly Set the threshold to an appropriate value.

The threshold is set correctly Go to the next step.

2. The PSU module is faulty.

If... Then...

The PSU module is faulty Rectify the fault of the PSU module.

The PSU module is not faulty Go to the next step.

3. The power of the storage battery is insufficient.

If... Then...

The power of the storage battery isinsufficient

Recharge the storage battery.

The power of the storage battery issufficient

Rectify the fault of the monitoringequipment.

----End

Related Information

None.



507

A.3.217 ODC_SMOKE_OVER

Description

The ODC_SMOKE_OVER is an alarm indicating that smoke occurs in an outdoor cabinet.

Attribute


Critical Environment alarm

Parameters

None.


The equipment may be burned.

Possible Causesl Cause 1: The smoke alarm is set incorrectly.

l Cause 2: A fire and heavy smoke occur at the equipment in the cabinet.

l Cause 3: The cable between the smoke sensor and the monitoring equipment is connectedincorrectly.

l Cause 4: The smoke sensor is faulty.


Procedure

Step 1 Cause 1: The smoke alarm is set incorrectly.

1. Check whether the smoke alarm is set correctly according to the configuration and planninginformation.

If... Then...

The smoke alarm is set correctly Perform the operations required when thealarm is generated due to cause 2.

The smoke alarm is set incorrectly Set the smoke alarm correctly.

Step 2 Cause 2: A fire and heavy smoke occur at the equipment in the cabinet.

1. Extinguish the fire in the cabinet.

Step 3 Cause 3: The cable between the smoke sensor and the monitoring equipment is connectedincorrectly.

1. Check whether the cable between the sensor and the monitoring equipment is connectedcorrectly.



508

If... Then...

The cable is connected incorrectly or isloose


The cable is deteriorated and damaged Replace the cable.

The cable is not deteriorated and damaged Perform the operations required whenthe alarm is generated due to cause 4.

Step 4 Cause 4: The smoke sensor is faulty.

1. Rectify the fault of the sensor.


If... Then...



Step 5 Cause 5: The associated monitoring equipment is faulty.

1. Rectify the fault of the monitoring equipment.

----End

Related Information

None.

A.3.218 ODC_SURGE_PROTECTION_FAIL

Description

The ODC_SURGE_PROTECTION_FAIL is an alarm indicating that the surge protectionfunction of the outdoor cabinet is abnormal.

Attribute



Parameters




509

Name Meaning

Parameter 1 Indicates the type of the alarm.

l 0x01: AC surge protection alarml 0x02: DC surge protection alarm


The AC surge protection function of the cabinet is disabled.

Possible Causesl Cause 1: The alarm is set incorrectly.

l Cause 2: The cable between the lightning sensor and the monitoring equipment is connectedincorrectly.

l Cause 3: The lightning sensor is faulty.

l Cause 3: The lightning arrestor is faulty.


Procedure

Step 1 Cause 1: The alarm is set incorrectly.

1. Check whether the alarm is set correctly according to the configuration and planninginformation.

If... Then...

The alarm is set correctly Perform the operations required when the alarm isgenerated due to cause 2.

The alarm is set incorrectly Set the surge protection alarm correctly.

Step 2 Cause 2: The cable between the lightning sensor and the monitoring equipment is connectedincorrectly.

1. Check the cable connection between the sensor and the monitoring equipment.

If... Then...



The cable is deteriorated and damaged Replace the cable.


Step 3 Cause 3: The lightning sensor is faulty.

1. Rectify the fault of the sensor.




510

If... Then...



Step 4 Cause 3: The lightning arrestor is faulty.1. Check whether the alarm output end of the lightning arrestor works properly.

If... Then...

The alarm output end of the lightningarrestor works properly

Perform the operations required when thealarm is generated due to cause 5.

The alarm output end of the lightningarrestor does not work properly

Replace the lightning arrestor.

Step 5 Cause 5: The associated monitoring equipment is faulty.1. Rectify the fault of the monitoring equipment.

----End


A.3.219 ODC_TEC_ALM

DescriptionThe ODC_TEC_ALM is an alarm indicating that the TEC air conditioning module in the cabinetdoes not work properly.

Attribute



ParametersNone.

Impact on the SystemIf the TEC air conditioning module does not work properly, the storage battery may operate atvery high or low temperature and therefore the safety performance of the storage batterydegrades.

Possible Causesl Cause 1: The TEC cable is connected incorrectly.



511

l Cause 2: The TEC module is faulty.

l Cause 3: The monitoring equipment is faulty.

Procedure

Step 1 Cause 1: The TEC cable is connected incorrectly.

1. Connect the TEC cable correctly.

Step 2 Cause 2: The TEC module is faulty.

1. Replace the TEC module.

Step 3 Cause 3: The monitoring equipment is faulty.

1. Rectify the fault of the monitoring equipment.

----End

Related Information

None.

A.3.220 ODC_TEMP_ABN

Description

The ODC_TEMP_ABN is an alarm indicating that the ambient temperature of the cabinet orthe temperature of the storage battery is abnormal.

Attribute



Parameters


Name Meaning


l 0x01: The ambient temperature is higher than the upper threshold.l 0x01: The ambient temperature is lower than the lower threshold.



512

Name Meaning

Parameter 2 Indicates the temperature type.

l 0x01: The temperature at the air outlet is very high or low.l 0x0b: Ambient temperature 1 is very high or low.l 0x0c: Ambient temperature 2 is very high or low.l 0x0d: The temperature of the battery group is very high or low.

Impact on the SystemIf the temperature is abnormal, the equipment performance degrades and the life of the equipmentdecreases.

Possible Causesl Cause 1: The temperature threshold that results in an alarm is set incorrectly.l Cause 2: The cable between the temperature sensor and the monitoring equipment is

connected incorrectly.l Cause 3: The temperature sensor is faulty.l Cause 4: The associated monitoring equipment is faulty.

Procedure

Step 1 Cause 1: The temperature threshold that results in an alarm is set incorrectly.1. Check whether the temperature alarm is set correctly according to the configuration and

planning information.

If... Then...

The temperature alarm is set correctly Perform the operations required whenthe alarm is generated due to cause 2.

The temperature alarm is set incorrectly Set the temperature alarm correctly.

Step 2 Cause 2: The cable between the temperature sensor and the monitoring equipment is connectedincorrectly.1. Check whether the cable between the sensor and the monitoring equipment is connected

correctly.

If... Then...





Step 3 Cause 3: The temperature sensor is faulty.1. Rectify the fault of the sensor.



513


If... Then...




----End


A.3.221 ODC_WATER_ALM

DescriptionThe ODC_WATER_ALM is an alarm indicating that certain water enters the cabinet.

Attribute


Critical Environment alarm

ParametersNone.

Impact on the SystemThe moisture in the cabinet increases, and the equipment in the cabinet may be damaged.

Possible Causesl Cause 1: The water alarm is set incorrectly.l Cause 2: Certain water enters the cabinet.l Cause 3: The cable between the water sensor and the monitoring equipment is connected

incorrectly.l Cause 4: The water sensor is faulty.l Cause 5: The associated monitoring equipment is faulty.

Procedure

Step 1 Cause 1: The water alarm is set incorrectly.1. Check whether the water alarm is set correctly according to the configuration and planning

information.



514

If... Then...

The water alarm is set correctly Perform the operations required when thealarm is generated due to cause 2.

The water alarm is set incorrectly Set the water alarm correctly.

Step 2 Cause 2: Certain water enters the cabinet.1. Dry the cabinet and take waterproof measures for the cabinet.

Step 3 Cause 3: The cable between the sensor and the monitoring equipment is connected incorrectly.1. Check whether the cable between the sensor and the monitoring equipment is connected

correctly.

If... Then...





Step 4 Cause 4: The sensor is faulty.1. Rectify the fault of the sensor.


----End


A.3.222 OUT_PWR_ABN

DescriptionThe OUT_PWR_ABN alarm indicates that the output optical power is abnormal.

Attribute






515

Name Meaning

Parameter 1 Indicates the port ID.

Parameter 2, Parameter 3 Indicate the path ID. The parameters have a fixed value of 0x000x01.

Parameter 4, Parameter 5 Are reserved. The value is always 0xFF.

Impact on the SystemThe OUT_PWR_ABN alarm affects the transmission performance of services, and may evenresult in service interruption.

Possible Causesl Cause 1: The output optical power is too high or low.l Cause 2: A board is faulty.

Procedure

Step 1 Cause 1: The output optical power is too high or low.1. Browse optical power performance events.

If... Then...

The output optical power does not meet therequirement

Replace the optical module.

The output optical power is too high Add a proper attenuator to reduce the inputoptical power.

Step 2 Cause 2: A board is faulty.1. Replace the alarmed board.

----End


A.3.223 OUT1TEMP_SENSOR_FAIL

DescriptionThe OUT1TEMP_SENSOR_FAIL is an alarm indicating that the air outlet temperature sensorof the cabinet fails.

Attribute





516

Parameters

None.


The air outlet temperature data of the TCU cannot be collected.

Possible Causesl Cause 1: The air outlet temperature sensor is faulty.

l Cause 2: The control board of the cabinet is faulty.


l Cause 4: The air outlet temperature sensor is not installed.

Procedure

Step 1 Cause 1: The air outlet temperature sensor is faulty.

1. Replace the air outlet temperature sensor.


If... Then...






If... Then...






Step 4 Cause 4: The air outlet temperature sensor is not installed.

1. Install the air outlet temperature sensor.

----End

Related Information

None.



517

A.3.224 OUT2TEMP_SENSOR_FAIL

DescriptionThe OUT2TEMP_SENSOR_FAIL is an alarm indicating that the external cycling air outlettemperature sensor of the cabinet fails.

Attribute



ParametersNone.

Impact on the SystemThe external cycling air outlet temperature data of the TCU cannot be collected.

Possible Causesl Cause 1: The external cycling air outlet temperature sensor is faulty.l Cause 2: The control board of the cabinet is faulty.l Cause 3: Cables are misconnected or damaged.l Cause 4: The external cycling air outlet temperature sensor is not installed.

Procedure

Step 1 Cause 1: The external cycling air outlet temperature sensor is faulty.1. Replace the external cycling air outlet temperature sensor.2. Then, check whether the alarm clears.

If... Then...




If... Then...






518



Step 4 Cause 4: The external cycling air outlet temperature sensor is not installed.

1. Install the external cycling air outlet temperature sensor.

----End

Related Information

None.

A.3.225 PATCH_ACT_TIMEOUT

Description

The PATCH_ACT_TIMEOUT is an alarm indicating that activating the patch package timesout. This alarm occurs when the patch package is in the active state for a period longer than thespecified period of time. In this case, the user needs to process the patch package.

Attribute



Parameters

None.


When the PATCH_ACT_TIMEOUT alarm occurs, it does not affect services.

Possible Causes

Cause: The patch package is in the active state for a period longer than the specified period oftime.

Procedure

Step 1 Cause: The patch package is in the active state for a period longer than the specified period oftime.

1. Check whether the activated patch package is normal.

2. If yes, run the patch package to make the it valid. If not, delete the patch package. Then,the alarm is cleared automatically.

----End



519


A.3.226 PATCH_DEACT_TIMEOUT

DescriptionThe PATCH_DEACT_TIMEOUT is an alarm indicating that deactivating the patch packagetimes out. This alarm occurs when the patch package is in the inactive state for a period longerthan the specified period of time. In this case, the user needs to process the patch package.

Attribute



ParametersNone.

Impact on the SystemWhen the PATCH_DEACT_TIMEOUT alarm occurs, it does not affect services.

Possible CausesCause: The patch package is in the inactive state for a period longer than the specified period oftime.

Procedure

Step 1 Cause: The patch package is in the inactive state for a period longer than the specified period oftime.1. To make the patch package valid, activate the patch package.2. Otherwise, delete the patch package. Then, the alarm is cleared automatically.

----End


A.3.227 PATCH_PKGERR

DescriptionThe PATCH_PKGERR alarm indicates that a patch package is incorrect or has been damagedor deleted.



520

Attribute


Minor alarm Equipment alarm

Parameters

None.


If a patch package is incorrect or has been damaged or deleted, the patch package cannot besuccessfully loaded, activated, or run.

NOTE

When this alarm is reported, services are not interrupted.

Possible Causesl Cause 1: A patch package is incorrect.l Cause 2: A patch package has been damaged.l Cause 3: A patch package has been deleted.

Procedure

Step 1 Load a correct patch package.

----End

Related Information

None.

A.3.228 PG_LINK_FAIL

Description

The PG_LINK_FAIL is an alarm indicating that the links in a 1+1 protection group fail.

Attribute



Parameters

None.



521


The services on the radio links are interrupted.

Possible Causes

Cause: Service alarms occur on the main and standby boards.

Procedure

Step 1 Set the Alarm Report Mode to Protection group and board alarms. For details, see Queryingthe IF 1+1 Protection Status.

NOTE

When alarms with different priorities occur on a board at the same time, the board reports only the alarmswith the highest priority. Alarms can be arranged in descending order by priority: hardware alarms >configuration alarms > service alarms.

Step 2 Handle the queried alarms.

----End

Related Information

None.

A.3.229 PG_PRT_DEGRADED

Description

The PG_PRT_DEGRADED is an alarm indicating that the main link or standby link in a 1+1protection group is faulty.

Attribute


Major Service alarm

Parameters


Name Meaning

Parameter 1 Indicates the board ID.



522

Impact on the SystemThe services at the NE are not affected, but radio link protection fails.

Possible Causesl Cause 1: Service alarms occur on the main board.l Cause 2: Service alarms occur on the standby board.

Procedure

Step 1 Locate the faulty board according to the alarm parameter.

Step 2 Set the Alarm Report Mode to Protection group and board alarms. For details, see Queryingthe IF 1+1 Protection Status.

NOTE

When service alarms with different priorities occur on a board at the same time, the board reports only thealarms with the highest priority. Alarms can be arranged in descending order by priority: hardware alarms> configuration alarms > service alarms.

Step 3 Handle the queried alarms.

----End


A.3.230 PLA_CFG_MISMATCH

DescriptionThe PLA_CFG_MISMATCH alarm indicates that the PLA configuration data is inconsistentbetween two ends of a radio link.

Attribute




Name Meaning

Parameter 1, Parameter 2 Indicate the ID of a PLA group.



523

Name Meaning

Parameter 3, Parameter 4 Indicate the error type.

l 0x00: indicates that no PLA group is configured at the oppositeend of a radio link.

l 0x01: indicates that the enabled status of Layer 2 headercompression function at the local end of a radio link is differentfrom that at the opposite end.


Services at both ends of a radio link are unavailable.

Possible Causesl Cause 1: A PLA group is configured at the local end but no PLA group is configured at the

opposite end.

l Cause 2: The enabled status of the Layer 2 header compression function at the local end ofa radio link is different from that at the opposite end.

Procedure

Step 1 Cause 1: A PLA group is configured at the local end but no PLA group is configured at theopposite end.

1. Follow instructions in Creating a PLA Group to configure a PLA group at the opposite endof the radio link.

Step 2 Cause 2: The enabled status of the Layer 2 header compression function at the local end of aradio link is different from that at the opposite end.

1. Follow instructions in Querying the PLA Group Status to determine the ports whoseconfiguration data needs to be changed according to planning information.

2. Follow instructions in Setting the Advanced Attributes of IF_ETH Ports to change theenabled status of the Layer 2 header compression function for PLA member ports.

----End

Related Information

None.

A.3.231 PORTMODE_MISMATCH

Description

The PORTMODE_MISMATCH is an alarm indicating that the working mode of the remote FEport does not match with that of the local FE port. This alarm is reported when the local FE portworks in auto-negotiation mode and the opposite FE port works in non-auto-negotiation mode.



524

Attribute


Minor Service alarm

Parameters


Name Meaning

Parameter 1, Parameter 2 Indicate the working mode of the FE port.


When the PORTMODE_MISMATCH alarm occurs, the service on the local NE is not affected. .

Possible Causesl Cause 1: The local FE port works in auto-negotiation mode and the opposite FE port works

in non-auto-negotiation mode.

Procedure

Step 1 Cause 1: The local FE port works in auto-negotiation mode and the opposite FE port works innon-auto-negotiation mode.

1. Disable the opposite FE port. For details, refer to Setting the General Attributes of EthernetPorts.

2. Enable the opposite FE port and set work mode of the port to auto-negotiation. For details,refer to Setting the General Attributes of Ethernet Ports.

----End

Related Information

None.

A.3.232 PORT_EXC_TRAFFIC

Description

The PORT_EXC_TRAFFIC alarm indicates that the traffic over a port exceeds its threshold.



525

Attribute




Name Meaning

Parameter 1 Indicates the traffic in the receive or transmit direction exceeds its threshold.

l 0x00: indicates the receive direction.l 0x01: indicates the transmit direction.

Impact on the SystemServices are congested.

Possible Causesl Cause 1: The configured bandwidth limit is too low.l Cause 2: The port traffic is too high.

Procedure

Step 1 Cause 1: The configured bandwidth limit is too low.1. Follow instructions in Configuring Traffic Shaping for Egress Queues to check the

configured bandwidth limit.2. If the configured bandwidth limit is too low, follow instructions in Configuring Traffic

Shaping for Egress Queues to increase the bandwidth limit value or perform networkexpansion.

Step 2 Cause 2: The configured port traffic is too high.1. Follow instruction in 8.17 Querying Traffic, Physical Bandwidth, or Bandwidth

Utilization of Ethernet Ports to query the bandwidth utilization over a port.2. If the port bandwidth utilization is higher than its threshold, check whether a network storm

occurs. If a network storm occurs, eliminate the source that transmits a large amount ofinvalid data.

----End




526

A.3.233 PORT_MODULE_OFFLINE

Description

The PORT_MODULE_OFFLINE alarm indicates that a port is offline.

Attribute



Parameters


Name Meaning

Parameter 1 Indicates the ID of the port that reports the alarm.

Parameter 2, Parameter 3 Have a fixed value of 0x00 0x01.

Parameter 4, Parameter 5 Are reserved and have a fixed value of 0xff.


The services over the alarmed port are interrupted.

Possible Causes

The alarmed port is enabled but house no SFP module.

Procedure

Step 1 Cause: The alarmed port is enabled but house no SFP module.

1. Check whether the alarmed port needs to receive/transmit a service.

If... Then...

The alarmed port needs to receive/transmit a service


The alarm port does not need to receive/transmit a service

Follow instructions in Setting the GeneralAttributes of Ethernet Ports to disable thealarmed port.

2. Check whether the alarmed port houses an SFP module.



527

If... Then...

The alarmed port houses no SFPmodule

Follow instructions in Installing an SFPModule to add an SFP module.

The alarmed port houses an SFPmodule


3. Re-install the SFP module.

If... Then...

The alarm clears No further action is required.

The alarm persists Follow instructions in Replacing an SFP Module to replace theSFP module.

----End

Related Information

None.

A.3.234 POWER_ABNORMAL

Description

The POWER_ABNORMAL is an alarm indicating that the input power supply is abnormal.

Attribute



Parameters


Name Meaning

Parameter 1 Indicates the number of the voltage channel.

l 0x01: the first channel of voltagel 0x02: the second channel of voltage



528

Name Meaning

Parameter 2 Indicates the type of the alarm.

l 0x00: voltage lossl 0x01: undervoltagel 0x02: overvoltage

Impact on the SystemWhen the POWER_ABNORMAL alarm occurs, the power supply is abnormal, and thereforethe board may fail to work normally.

Possible Causesl Cause 1: The power cable is cut, damaged, or incorrectly connected.l Cause 2: The input power is abnormal.

Procedure

Step 1 Cause 1: The power cable is cut, damaged, or incorrectly connected.1. Check whether the power cable is cut, damaged, or incorrectly connected. If the power

cable is cut or damaged, replace it with a proper power cable. If the power cable isincorrectly connected, reconnect the power cable.

Step 2 Cause 2: The input power is abnormal.1. Contact the engineers for power supply to rectify the fault.

----End


A.3.235 POWER_ALM

DescriptionThe POWER_ALM is an alarm indicating that the power module is abnormal.

Attribute






529


Name Meaning

Parameter 1 If the POWER_ALM alarm is reported on a board on the IDU, this parameterindicates the ID of the alarmed power module. For example, 0x01 indicates thatthe alarm is reported by power module 1 of the board.

If the POWER_ALM is reported on the ODU, this parameter indicates the typeof the power fault.l 0x01: The -5 V power supply is faulty.l 0x02: The power supply for the power amplifier is faulty.

Parameter 2 l 0x01: under-voltagel 0x02: over-voltage


The power modules are configured with protection. If only one power module reports thePOWER_ALM alarm, the system is not affected.

Possible Causes

If the alarm is reported by a board of the IDU, the possible causes are as follows:

l Cause 1: The input power or the PIU is abnormal.

l Cause 2: The power module is abnormal.

If the alarm is reported on the ODU, the cause is as follows:

l Cause 1: The power module of the ODU is faulty.

Procedure

Step 1 (POWER_ALM reported by a board of the IDU) Cause 1: The input power or the PIU isabnormal.

1. Check whether alarms are reported on the PIU, If yes, clear these alarms immediately.

Step 2 (POWER_ALM reported by a board of the IDU) Cause 2: The power module is abnormal.

1. Replace the alarmed board. For details, see 6 Part Replacement.

Step 3 (POWER_ALM reported on the ODU) Cause 1: The power module of the ODU is faulty.

1. Replace the ODU. For details, see 6.13 Replacing the ODU.

----End

Related Information

None.



530

A.3.236 PW_DROPPKT_EXC

Description

The PW_DROPPKT_EXC alarm indicates that the packet loss ratio on a PW exceeds itsthreshold.

Attribute


Warning Processing alarm

Parameters

Parameters


Name Meaning

Parameter 1 Has a fixed value of 0x00, indicating that the traffic in the ingress or egressdirection crosses its threshold.


A small number of packets are lost, affecting service real-time performance.

Possible Causes

Cause: A small number of packets are lost on the alarmed PW.

Procedure

Step 1 Cause: A small number of packets are lost on the alarmed PW.

1. Follow instructions in Querying Information and Running Status of PWs to check thebandwidth utilization of the alarmed PW. If the PW bandwidth is exhausted, increase thebandwidth or eliminate any source that transmits a large amount of invalid data.

----End

Related Information

None.



531

A.3.237 PWAPS_LOST

Description

The PWAPS_LOST is an alarm indicating that the APS frame is lost. This alarm occurs whenno APS frame is received from the protection channel.

Attribute



Parameters

None.


When this alarm occurs, the service protection fails.

Possible Causesl Cause 1: The remote NE of the PW is not configured with any protection group.l Cause 2: The service on the protection channel is interrupted.

Procedure

Step 1 Cause 1: The remote NE of the PW is not configured with any protection group.1. Check whether the remote NE of the PW is configured with a protection group. If yes,

ensure that the configuration is the same at the two ends.

Step 2 Cause 2: The service on the protection channel is interrupted.1. Check whether the protection channel is faulty. If yes, rectify the fault.

----End

Related Information

None.

A.3.238 PWAPS_PATH_MISMATCH

Description

The PWAPS_PATH_MISMATCH is an alarm indicating that the working and protection pathsof the APS protection group differ between the two ends. This alarm is reported when theworking and protection paths of one APS protection group at one end are different from thoseat the other end.



532

Attribute



Parameters

None.


When this alarm occurs, the service protection fails.

Possible Causesl Cause 1: The configured working and protection paths differ between the two ends.

l Cause 2: Certain physical links are incorrectly connected.

Procedure

Step 1 Cause 1: The configured working and protection paths differ between the two ends.1. Check whether the APS settings at the two ends are the same.2. If the APS settings are different, change the settings to the same.

Step 2 Cause 2: Certain physical links are incorrectly connected.1. Connect the fibers or cables properly.

----End

Related Information

None.

A.3.239 PWAPS_SWITCH_FAIL

Description

The PWAPS_SWITCH_FAIL is an alarm indicating a switching failure of the PW APSprotection group. This alarm is reported when the request signal in the transmitted AutomaticProtection Switching (APS) frame is different from the bridge signal in the received APS frameand this symptom lasts for 50 ms.

Attribute





533

ParametersNone.

Impact on the SystemWhen this alarm occurs, the service protection fails.

Possible Causesl Cause 1: The configured working and protection paths differ between the two ends.l Cause 2: Certain physical links are incorrectly connected.

Procedure

Step 1 Cause 1: The configured working and protection paths differ between the two ends.1. Check whether the APS settings at the two ends are the same.2. If the APS settings are different, change the settings to the same.

Step 2 Cause 2: Certain physical links are incorrectly connected.1. Connect the fibers or cables properly.

----End


A.3.240 PWAPS_TYPE_MISMATCH

DescriptionThe PWAPS_TYPE_MISMATCH is an alarm indicating that the local NE and the opposite NEare configured with different PW protection types. This alarm occurs when the information inthe received APS frames is inconsistent with the APS protection scheme configured at the localend.

Attribute



ParametersNone.

Impact on the SystemWhen this alarm occurs, the service protection fails.



534

Possible Causesl Cause 1: The configured protection modes (1+1 protection or 1:1 protection) differ at the

two ends of the PW.l Cause 2: The configured switching modes (single-ended or dual-ended) differ at the two

ends of the PW.l Cause 3: The configured revertive modes (revertive or non-revertive) differ at the two ends

of the PW.

ProcedureStep 1 Check whether the APS protection settings, such as protection mode, switching mode, and

revertive mode, are the same at the local and remote ends.

Step 2 If the APS protection settings are different, change the settings to the same.

----End


A.3.241 R_F_RST

DescriptionThe R_F_RST is an alarm indicating that the receive FIFO is reset.

Attribute



ParametersNone.

Impact on the SystemThe services are interrupted.

Possible Causesl Cause 1: The clocks at both stations are not synchronous.l Cause 2: A certain board is faulty.

ProcedureStep 1 Cause 1: The clocks at both stations are not synchronous.

1. Query whether a TU pointer adaptation performance event is reported at both ends. Fordetails, see 8.3.5 Browsing Current Performance Events.



535

If... Then...

An AU pointer adaptation performanceevent is reported

Handle the performance event. For details,see C.3.2 TUPJCHIGH, TUPJCLOW,and TUPJCNEW.

An AU pointer adaptation performanceevent is not reported

Go to Cause 2.


----End


A.3.242 R_LOC

DescriptionThe R_LOC is an alarm indicating that the clock is lost on the receive line side. This alarm isreported when the line board fails to extract clock signal from the line signal or the IF board failsto extract clock signal from the IF signal.

Attribute



ParametersNone.

Impact on the SystemThe services on the line port or the IF port are interrupted. If the system is configured withprotection, protection switching may be triggered.

Possible Causesl Cause 1: The receive unit of the local site is faulty.l Cause 2: The transmit unit of the opposite station is faulty.

Procedure

Step 1 Cause 1: The receive unit of the local site is faulty.1. At the local end, perform an inloop on the port of the alarmed board. For details, see 8.5

Software Loopback.



536

If... Then...

The alarm persists after the loopback Replace the alarmed local board.

The alarm is cleared after the loopback Go to Cause 2.

Step 2 Cause 2: The transmit unit of the opposite station is faulty.1. Replace the alarmed opposite board.

If... Then...


The fault is rectified. End the alarm handling.


Replace the system control, switch&timingboard at the opposite end.

----End


A.3.243 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 three milliseconds.

Attribute



ParametersNone.

Impact on the SystemThe services are interrupted. If the system is configured with protection, protection switchingmay be triggered.

Possible Causesl Cause 1: Certain alarms are generated (if the alarm is reported by an IF board).l Cause 2: The line performance degrades (if the alarm is reported by an SDH optical interface

board).l Cause 3: The transmit unit of the opposite station is faulty.l Cause 4: The receive unit of the local site is faulty.



537

Procedure

Step 1 Cause 1: Certain high-level alarms are generated (if the alarm is reported by an IF board).1. If the alarm is reported by the IF board, check whether the MW_BER_EXC,

MW_BER_SD, MW_FEC_UNCOR alarm is generated.

If... Then...

The alarm is generated Take priority to clear theMW_BER_EXC, MW_BER_SD,MW_FEC_UNCOR alarm.

The alarm is not generated Go to the next step.

2. Set the inloop on the alarmed IF port.

If... Then...

The alarm persists after the inloop isperformed

Go to Cause 4.

The alarm is cleared after the inloop isperformed

Go to Cause 3.

Step 2 Cause 2: The line performance degrades (if the alarm is reported by an SDH optical interfaceboard).1. If the alarm is reported by an optical interface board, exchange the transmit and receive

fiber jumpers at both ends.

If... Then...

The alarm persists after the exchange Go to Cause 3 or 4

The line port of the opposite station reportsthe R_LOF alarm

Troubleshoot the optical fibers.

Step 3 Cause 3: The transmit unit of the opposite station is faulty.1. Replace the opposite board where the line unit is or the opposite IF board.

If... Then...

The alarm is cleared after the boardreplacement

The fault is rectified, and the alarmhandling is complete.

The alarm persists after the boardreplacement


2. Replace the system control and cross-connect board at the opposite end.



538

If... Then...




Go to Cause 4.



----End

Related Information


A.3.244 R_LOS

Description

In the case of SDH boards, the R_LOS is an alarm indicating that the signals on the receive lineside are lost. In the case of IF boards, the R_LOS is an alarm indicating that the radio frames onthe receive line side are lost.

Attribute



Parameters

None.


The services are interrupted. If the system is configured with protection, protection switchingmay be triggered.

Possible Causesl Cause 1: Certain alarms are generated (if the alarm is reported by an IF board).

l Cause 2: The line performance degrades (if the alarm is reported by an SDH line board).





539

Procedure

Step 1 Cause 1: Certain alarms are generated (if the alarm is reported by an IF board).1. If the alarm is reported by the IF board, check whether the MW_BER_EXC,

MW_BER_SD, MW_FEC_UNCOR alarm is generated.

If... Then...

The alarm is generated Take priority to clear theMW_BER_EXC, MW_BER_SD,MW_FEC_UNCOR alarm.

The alarm is not generated Go to the next step.

2. Set the inloop on the alarmed IF port.

If... Then...

The alarm persists after the inloop isperformed

Go to Cause 4.

The alarm is cleared after the inloop isperformed

Go to Cause 3.

Step 2 Cause 2: The line performance degrades (if the alarm is reported by an SDH line board).1. If the alarm is reported by an optical interface board, exchange the transmit and receive

fiber jumpers at both ends.

If... Then...

The alarm persists after the exchange Go to Cause 3 or 4

The line port of the opposite station reportsthe R_LOF alarm

Troubleshoot the optical fibers.

Step 3 Cause 3: The transmit unit of the opposite station is faulty.1. Replace the opposite board where the line unit is or the opposite IF board.

If... Then...




Proceed to the next step.

2. Replace the system control and cross-connect board at the opposite end.



540

If... Then...




Go to Cause 4.



----End

Related Information


A.3.245 R_S_ERR

Description

The R_S_ERR is an alarm indicating that the received signal has errors.

Attribute



Parameters

None.


The services are interrupted.



Procedure


1. Check whether the tributary board supports the type of the input signal.



541

If... Then...

The tributary board does not support thetype of the input signal.

Change the type of the output signal of theremote site.

The tributary board supports the type ofthe input signal.


2. Test the frequency offset of the input signal.

If... Then...


The frequency offset meets the requirement Go to Cause 2.


----End


A.3.246 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 + 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 and lastsfor three minutes after the alarm is reported, the alarm is cleared.

Attribute



ParametersNone.

Impact on the SystemIf the MW_BER_EXC, MW_BER_SD, MW_LOF or MW_FEC_UNCOR alarm is notgenerated, the service is not affected.

Possible Causesl Cause 1: The ODU fault of the transmit end causes the abnormal transmit power.



542

l Cause 2: The direction of the antenna is deflected.l Cause 3: The transmission environment changes.l Cause 4: The fade margin in the case of rain and fog in the network planning is insufficient.

Procedure

Step 1 Cause 1: The ODU fault of the transmit end causes the abnormal transmit power.1. Check whether the ODU at the transmit end reports the RADIO_TSL_LOW alarm.

If... Then...

The ODU at the transmit end reports theRADIO_TSL_LOW alarm

Handle the RADIO_TSL_LOW alarm.

The ODU at the transmit end does not report theRADIO_TSL_LOW alarm

Go to Cause 2.

Step 2 Cause 2: The direction of the antenna is deflected.1. Check whether the direction of the antenna is deflected.

If... Then...

The direction of the antenna is deflected Adjust the direction of the antenna.

The direction of the antenna is not deflected Go to Cause 3.

Step 3 Cause 3: The transmission environment changes.1. Check whether the transmission environment changes. For example, check whether any

building blocks the transmission and increases the link fading significantly.

If... Then...

The transmission environment changes Contact the network planning department forre-planning the transmission trail.

The transmission environment does notchange

Go to Cause 4.

Step 4 Cause 4: The fade margin in the case of rain and fog in the network planning is insufficient.1. If the alarm is reported frequently, contact the network planning department to increase the

fade margin by re-planning the transmission trail.

----End


A.3.247 RADIO_MUTE

DescriptionThe RADIO_MUTE is an alarm indicating that radio transmitter is muted.



543

Attribute



ParametersNone.

Impact on the SystemThe transmitter does not transmit services.

Possible Causesl Cause 1: The other alarms are generated.l Cause 2: The transmitter of the local 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.

Procedure

Step 1 Cause 1: The other alarms are generated.1. Check whether the CONFIG_NOSUPPORT or IF_INPWR_ABN alarm is generated. If

yes, take priority to clear the alarm.

Step 2 Cause 2: The transmitter of the local 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, cancel the muting operation. Then, set thetransmitting status of the ODU to unmute.

Step 3 Cause 3: The IF board is faulty, causing abnormal IF output.1. Replace the IF board.

Step 4 Cause 4: The data output is abnormal because the ODU is faulty.1. Replace the ODU.

----End

Related InformationThe logical slot ID of the ODU is obtained by adding 20 to the slot ID of the IF board connectedto the ODU.

A.3.248 RADIO_RSL_BEYONDTH

DescriptionThe RADIO_RSL_BEYONDTH is an alarm indicating that the antennas are not aligned. Whenthe receive power is set on the NE, the NE enables the antenna alignment indication function.



544

If the actual receive power of the ODU is lower than the power to be received 3 dB, theRADIO_RSL_BEYONDTH alarm is reported. Then, if the antennas are aligned for continuous30 minutes, the antenna alignment indication function is disabled automatically. Afterwards, theRADIO_RSL_BEYONDTH alarm is reported only when theRADIO_FADING_MARGIN_INSUFF alarm is reported.

Attribute



Parameters

None.


If the MW_BER_EXC, MW_BER_SD, MW_LOF or MW_FEC_UNCOR alarm is notgenerated, the service is 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 is cleared, the RADIO_RSL_BEYONDTHalarm is cleared.

----End

Related Information

None.

A.3.249 RADIO_RSL_HIGH

Description

The RADIO_RSL_HIGH is an alarm indicating that the radio receive power is very high. Thisalarm is reported if the detected receive power is equal to or higher than the upper threshold ofthe ODU (-20 dBm).



545

Attribute



Parameters

None.


The service transmission is affected. If the system is configured with 1+1 protection, protectionswitching may be triggered.

Possible Causesl Cause 1: The local ODU is faulty.

l Cause 2: There is a strong interference source nearby.

l Cause 3: The transmit power of the opposite ODU is very high.

Procedure

Step 1 Cause 1: The local ODU is faulty.

1. 6.13 Replacing the ODU.

Step 2 Cause 2: There is a strong interference source nearby.

1. Check whether any nearby signal source transmits signals whose frequency is close to thespecified range. If yes, check whether the signal source can be shut down or removed. Ifnot, contact the network planning department for replanning the frequency.

Step 3 Cause 3: The transmit power of the opposite ODU is very high

1. Reset the transmit power of the ODU at the opposite end. For details, see Configuring theIF/ODU Information of a Radio Link.

----End

Related Information

None.

A.3.250 RADIO_RSL_LOW

Description

The RADIO_RSL_LOW is an alarm indicating that the radio receive power is very low. Thisalarm is reported if the detected receive power is equal to or lower than the upper threshold ofthe ODU (-90 dBm).



546

Attribute



ParametersNone.

Impact on the SystemIf no MW_BER_EXC, MW_BER_SD, MW_LOF or MW_FEC_UNCOR alarm isgenerated, the services are not affected.

Possible Causesl Cause 1: Other alarms occur at the opposite station.l Cause 2: The transmit power of the opposite station is very low.l Cause 3: The local ODU is faulty.l Cause 4: Signal attenuation on the radio link is very heavy.

Procedure

Step 1 Cause 1: Other alarms occur at the opposite station.Check whether any of the following alarms is generated in the equipment of the opposite station.If yes, take priority to clear the alarm.l RADIO_MUTEl CONFIG_NOSUPPORTl RADIO_TSL_LOWl BD_STATUS

Step 2 Cause 2: The transmit power of the opposite station is very low.1. See Configuring the IF/ODU Information of a Radio Link. Check whether the transmit

power of the opposite station is normal. If not, replace the ODU of the opposite station.

Step 3 Cause 3: The local ODU is faulty.1. Replace the ODU at the local end.

Step 4 Cause 4: Signal attenuation on the radio link is very heavy.1. Browse history alarms and check whether the alarm is generated continuously.

If the alarm is generated occasionally, contact the network planning department to changethe design to increase the anti-fading performance.

2. Check whether the antennas at both ends are adjusted properly.

If not, align the antennas again.3. Check whether any mountain or building obstacle exists in the transmit direction.

If yes, contact the network planning department for proper modification of the planningdesign, hence preventing the block of the mountain or building obstacle.



547

4. Check whether the polarization direction of the antenna, ODU, and hybrid coupler is setcorrectly.

If not, correct the polarization direction.5. Check whether the outdoor units such as antennas, combiner, ODU, and flexible waveguide

are wet, damp, or damaged.

If yes, replace the unit that is wet, damp, or damaged. For the operations, see 6 PartReplacement

6. Check whether the antenna gain at both the transmit and receive ends meets the requirement.

If not, replace the antenna.

----End


A.3.251 RADIO_TSL_HIGH

DescriptionThe RADIO_TSL_HIGH is an alarm indicating that the radio transmit power is too high. Thisalarm is reported when the detected transmit power is higher than the upper power threshold ofthe ODU.

Attribute



ParametersNone.

Impact on the SystemThe service transmission is affected. If the system is configured with 1+1 protection, protectionswitching may be triggered.

Possible CausesCause 1: The local ODU is faulty.

Procedure

Step 1 Cause 1: The local ODU is faulty.1. Replace the ODU.

----End



548

Related Information

None.

A.3.252 RADIO_TSL_LOW

Description

The RADIO_TSL_LOW is an alarm indicating that the radio transmit power is very low. Thisalarm is reported when the detected transmit power is less than the lower power threshold of theODU.

Attribute



Parameters

None.


The service transmission is affected. If the system is configured with 1+1 protection, protectionswitching may be triggered.

Possible Causes

Cause 1: The local ODU is faulty.

Procedure

Step 1 Cause 1: The local ODU is faulty.1. Replace the ODU.

----End

Related Information

None.

A.3.253 RELAY_ALARM_CRITICAL

Description

The RELAY_ALARM_CRITICAL is an alarm indicating the critical alarm inputs. This alarmoccurs when the user sets the severity of an available alarm input to critical and there is such analarm input.



549

Attribute



Parameters

None.


When the RELAY_ALARM_CRITICAL alarm occurs, it does not affect the operation of theboard or the services on the NE.

Possible Causes

Cause 1: There is a critical alarm input.

Procedure

Step 1 Cause 1: There is a critical alarm input.

1. Clear the alarms of the external equipment according to the defined meanings of the alarms.Then, the RELAY_ALARM_CRITICAL alarm is cleared.

----End

Related Information

None.

A.3.254 RELAY_ALARM_IGNORE

Description

The RELAY_ALARM_IGNORE is an alarm indicating the warning alarm inputs. This alarmoccurs when the user sets the severity of an available alarm input to warning and there is suchan alarm input.

Attribute



Parameters

None.



550

Impact on the SystemWhen the RELAY_ALARM_IGNORE alarm occurs, it does not affect the operation of the boardor the services on the NE.

Possible CausesCause 1: There is a warning alarm input.

Procedure

Step 1 Cause 1: There is a warning alarm input.1. Clear the alarms of the external equipment according to the defined meanings of the alarms.

Then, the RELAY_ALARM_IGNORE alarm is cleared.

----End


A.3.255 RELAY_ALARM_MAJOR

DescriptionThe RELAY_ALARM_MAJOR is an alarm indicating the major alarm inputs. This alarm occurswhen the user sets the severity of an available alarm input to major and there is such an alarminput.

Attribute



ParametersNone.

Impact on the SystemWhen the RELAY_ALARM_MAJOR alarm occurs, it does not affect the operation of the boardor the services on the NE.

Possible CausesCause 1: There is a major alarm input.

Procedure

Step 1 Cause 1: There is a major alarm input.



551

1. Clear the alarms of the external equipment according to the defined meanings of the alarms.Then, the RELAY_ALARM_MAJOR alarm is cleared.

----End

Related Information

None.

A.3.256 RELAY_ALARM_MINOR

Description

The RELAY_ALARM_MINOR is an alarm indicating the minor alarm inputs. This alarm occurswhen the user sets the severity of an available alarm input to minor and there is such an alarminput.

Attribute



Parameters

None.


When the RELAY_ALARM_MINOR alarm occurs, it does not affect the operation of the boardor the services on the NE.

Possible Causes

Cause 1: There is a minor alarm input.

Procedure

Step 1 Cause 1: There is a minor alarm input.

1. Clear the alarms of the external equipment according to the defined meanings of the alarms.Then, the RELAY_ALARM_MINOR alarm is cleared.

----End

Related Information

None.



552

A.3.257 RMFA

Description

The 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-5) of the framed E1/T1 input.

Attribute



Parameters


Name Meaning


Parameter 2, Parameter 3 Indicate the path ID.


When this alarm occurs, the services at the local site are not affected. The alarm indicates thatthe LMFA alarm occurs at the opposite end.

Possible Causes

The LMFA alarm occurs at the opposite end.

Procedure

Step 1 Check whether the opposite end of the alarmed path reports the LMFA alarm. If yes, clear theLMFA alarm. Then, the RMFA alarm at the local end clears.

----End

Related Information

None.

A.3.258 RPS_INDI



553

DescriptionThe RPS_INDI is an alarm indicating that the radio protection switching is detected.

Attribute




Name Meaning

Parameter 1 Indicates the ID of the protection group.

Parameter 2 Indicates the type of protection switching.

0x01: HSB protection switching

0x02: HSM protection switching

Impact on the Systeml During the HSB protection switching, services are interrupted. After the HSB switching is

complete, the services are restored to normal.l During the HSM protection switching, no bit errors occur and the services are not affected.

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 The possible causes of HSM protection switching are as follows:The quality of the main channel degrades.– In the case of Hybrid radio, the automatic switching condition of the HSM is that the

quality of the main channel degrades.– In the case of SDH/PDH radio, an alarm that triggers the HSM switching is reported on

the radio link.

Procedure

Step 1 Determine the type of the protection switching based on the alarm parameters.



554

Step 2 Cause 1 of HSB switching: An external switching event occurs. That is, the NMS issues acommand to trigger the switching.1. Check whether the switching is the forced switching or manual switching. For details, see

Querying the IF 1+1 Protection Status.

If... Then...

The switching is the forced switching ormanual switching

Find the cause and release the switchingimmediately.

The switching is not the forcedswitching or manual switching

Go to Cause 2 of HSB switching.

Step 3 Cause 2 of HSB switching: An automatic switching event occurs. That is, the equipment is faulty,or the service is defective.1. Check whether the following faults or alarms occur. If yes, rectify the faults or clear the

alarms.l The hardware of the IF board or the ODU is faulty.l VOLT_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 to the working pathwhen the working path is restored to normal, and the RPS_INDI alarm persists. In this case, youneed to manually switch the services from the protection path to the working path. The RPS_INDIalarm is cleared only when the switching is successful.

l If the switching is revertive, the services are automatically switched to the working path onlywhen the specified wait-to-restore (WTR) time expires after the working path is restored tonormal. The RPS_INDI alarm is cleared only when the switching is successful.

Step 4 Cause 3 of HSB switching: A reverse switching event occurs.1. Query whether the active and standby IF boards report the MW_RDI alarm. If yes, take

priority to clear the MW_RDI alarm.

Step 5 Cause 1 of HSM switching: In the case of Hybrid radio, the quality of the main channel degrades.1. Check whether the AM_DOWNSHIFT alarm is reported by an IF board. If the alarm is

reported by an IF board, refer to AM_DOWNSHIFT to rectify the fault that causes thequality of the main channel to degrade. If the alarm is not reported by an IF board, thequality of the main channel degrades possibly due to the weather. In this case, you do notneed to handle the problem, because this is a normal situation.

Step 6 Cause 2 of HSM switching: In the case of SDH/PDH radio, an alarm that triggers the HSMswitching is reported on the radio link.1. Check whether any alarm that triggers the HSM switching is reported by an IF board of the

IF 1+1 protection group. If yes, take priority to clear the alarm.HSM switching may be triggered by any of the following alarms:l R_LOC, R_LOF, R_LOS, or MW_LOFl MW_BER_EXC, MW_BER_SD, MW_FEC_UNCORl B1_SD or B2_SD

----End



555

Related Information

None.

A.3.259 RS_CROSSTR

Description

The RS_CROSSTR is an alarm indicating that a regenerator section performance indicatorcrosses the threshold. This alarm is reported if a board detects that a regenerator section bit errorperformance event crosses the preset threshold.

Attribute


Minor Service alarm

Parameters


Name Meaning



Parameter 2, Parameter 3 Parameter 2 is always 0x00. Parameter 3 indicate the ID of aperformance event that causes the alarm and has the followingmeanings:

l 0x01: RSBBEl 0x02: RSESl 0x03: RSSESl 0x04: RSOOFl 0x05: RSOFSl 0x06: RSUASl 0x07: RSCSES


A large number of bit errors occur in the services, and the services may be interrupted.



556

Possible Causesl Cause 1: Services are interrupted for a long time.

l Cause 2: The regenerator section bit error performance indicator crosses the presetthreshold.

Procedure

Step 1 Cause 1: Services are interrupted for a long time.

NOTEHandle the alarm as follows if the value of parameter 3 is 0x06:

1. Check whether fibers are properly connected. If not, connect the fibers again according toplanning information.

2. Check whether cross-connections are configured for service ports. If not, configure cross-connections again according to planning information.

Step 2 Cause 2: The regenerator section bit error performance indicator crosses the preset threshold.

1. Find out the performance event that crosses the preset threshold. For details, see 8.3.8Browsing the Performance Event Threshold-Crossing Records.


----End

Related Information

None.

A.3.260 RTC_FAIL

Description

The RTC_FAIL is an alarm indicating that the real-time clock (RTC) on the system controlboard fails.

Attribute



Parameters

None.


The service is not affected.



557

Possible Causesl Cause 1: The RTC on the system control board is abnormal.l Cause 2: The board temperature is too high.

Procedure

Step 1 Cause 1: The RTC on the system control board is abnormal.1. Replace the system control, switching, and timing board.

Step 2 Cause 2: The board temperature is too high.1. 8.3.3 Browsing Current Alarms, and if the board reports the TEMP_ALARM alarm,

clear this alarm first.

----End


A.3.261 S1_SYN_CHANGE

DescriptionThe S1_SYN_CHANGE is an alarm indicating that the clock source is switched in S1 bytemode.

Attribute




Name Meaning

Parameter 1 0x01: system priority list

0x02: external clock priority list

Impact on the SystemIf the new clock source has a lower quality, pointer justifications and bit errors are generatedafter the switching of clock source. As a result, the quality of services is affected.



558

Possible Causes

When the SSM protocol or extended SSM protocol is enabled.

l Cause 1: The original clock source is lost.

l Cause 2: The fiber is cut off.

l Cause 3: The external BITS is interrupted.

l Cause 4: The S1_SYN_CHANGE alarm occurs at the upstream station.

Procedure

Step 1 Cause 1: The original clock source is lost.

1. Handle the SYNC_C_LOS alarm that is related to the original clock source.

Step 2 Cause 2: The fiber is cut off.

1. Replace the faulty fiber.

Step 3 Cause 3: The external BITS is interrupted.

1. Check whether the cable connect NE to BITS is normal. If not, replace the faulty cable.

Step 4 Cause 4: The S1_SYN_CHANGE alarm reported at the upstream station.

1. Handle the S1_SYN_CHANGE alarm reported at the upstream station.

----End

Related Information

None.

A.3.262 SCCDATA_BACKUP_FAIL

Description

The SCCDATA_BACKUP_FAIL is an alarm indicating that the batch backup on SCC boardsfails.

Attribute



Parameters




559

Name Meaning

Parameter 1 Indicates the cause of the failure.

l 0x31: The database backup fails.l 0x32: Software version verification fails on the main and standby SCC

boards.l 0x33: Communication between the main and standby SCC boards fails.l 0x34: The main and standby SCC boards have different data after an upgrade.

Impact on the SystemData synchronization between the main and standby SCC boards fails, and the switching betweenthe two boards is unavailable.

Possible Causesl Cause 1: The main and standby SCC boards have different versions of software.l Cause 2: Communication between the main and standby SCC boards fails.l Cause 3: Databases on the main and standby SCC boards are damaged.l Cause 4: The main and standby SCC boards have different data after an upgrade.

Procedure

Step 1 Cause 1: The main and standby SCC boards have different versions of software.1. Query and record the software versions of the main and standby SCC boards according to

8.4.1 Querying the Board Information Report .2. If the software versions are different, determine the correct version based on the version

mapping table and replace the SCC board with an incorrect version. For details, see 6.9Replacing the System Control, Switch and Timing Board.

Step 2 Cause 2: Communication between the main and standby SCC boards fails.1. Check whether the system reports the COMMUN_FAIL alarm.2. If yes, clear the COMMUN_FAIL alarm. The system will start batch backup

automatically.

Step 3 Cause 3: Databases on the main and standby SCC boards are damaged.1. Check whether the system reports the DBMS_ERROR alarm. For details, see 8.3.3

Browsing Current Alarms.2. If yes, clear the DBMS_ERROR alarm. Then, check whether the SYNC_FAIL alarm is

cleared.

Step 4 Cause 4: The main and standby SCC boards have different data after an upgrade.1. Re-install the standby SCC board.

----End




560

A.3.263 SEC_RADIUS_FAIL

Description

The SEC_RADIUS_FAIL is an alarm indicating that RADIUS authentication fails overmanytimes. This alarm is reported when the RADIUS authentication fails for five consecutive times.

Attribute



Parameters


Name Meaning

Parameter 1 to Parameter 5 Indicates the most significant five characters of username.


A user cannot log in to an NE.

Possible Causesl Cause 1: The active period of the account expires.l Cause 2: Configurations on the RADIUS server are incorrect, such as passwords and access

policies.l Cause 3: There are unauthenticated login attempts.l Cause 4: The shared key for the NE and the RADIUS server is configured incorrectly.

Procedure

Step 1 Cause 1: The active period of the account expires.1. Use an active account.

Step 2 Cause 2: Configurations on the RADIUS server are incorrect, such as passwords and accesspolicies.1. Enter the correct password.2. Set correct access policies.

Step 3 Cause 3: There are unauthenticated login attempts.1. Eliminate the source that initiates the unauthenticated login attempts.



561

Step 4 Cause 4: The shared key for the NE and the RADIUS server is configured incorrectly.

1. Set the shared key correctly.

----End

Related Information

None.

A.3.264 SECU_ALM

Description

The SECU_ALM is an alarm indicating that an illegal user fails to log in to the NE.

Attribute



Parameters

None.


The SECU_ALM alarm is ended soon after it is reported, and the alarm does not affect the systemand services.

Possible Causes

An illegal user tries to log in to the NE.

Procedure

Step 1 An illegal user tries to log in to the NE.

1. Query the NE log to check the user name that is used for the login.

----End

Related Information

After a user fails to log in to an NE for five consecutive times (if the interval between two loginsis less than 3 minutes, the two logins are consecutive logins), the SECU_ALM alarm is reportedupon each subsequent login failure and meanwhile the user is locked for 60 seconds. During the60 seconds, the user cannot log in to the NE.



562

A.3.265 SRV_SHUTDOWN_LD

Description

The SRV_SHUTDOWN_LD alarm indicates that an Ethernet service is deactivated. This alarmis reported when an Ethernet service is deactivated due to a service loop. This alarm is clearedafter the Ethernet service is reactivated.

Attribute



Parameters

None.


The loop of the alarmed Ethernet service is released, and the Ethernet service is restored.

Possible Causes

Cause 1: A loop occurs in an Ethernet service and therefore the Ethernet service is deactivated.

Procedure

Step 1 Cause 1: A loop occurs in an Ethernet service and therefore the Ethernet service is deactivated.

1. Check whether a service is looped back on the path of the alarmed Ethernet service.

2. Re-configure the preceding service based on the network plan.

----End

Related Information

None.

A.3.266 SWDL_ACTIVATED_TIMEOUT

Description

The SWDL_ACTIVATED_TIMEOUT is an alarm indicating the activation timeout of thesoftware package. During the package loading, the system reports the alarm if no data issubmitted within 30 minutes after activation of the NE software or board software.



563

Attribute



ParametersNone.

Impact on the SystemThe NE does not perform the submit operation. As a result, the software in the two areas of thedouble-area boards on the NE is inconsistent.

Possible CausesCause 1: The radio link is faulty. As a result, the NE involved in the package loading fails toreceive the submit command.

Procedure

Step 1 Cause 1: The radio link is faulty. As a result, the NE involved in the package loading fails toreceive the submit command.1. Check whether the radio link is faulty.

If... Then...

The radio link is faulty Troubleshoot the radio link to ensure that the linkbetween the nodes to be loaded is normal.

The radio link is normal Perform the package loading to the NE again.

----End


A.3.267 SWDL_AUTOMATCH_INH

DescriptionThe SWDL_AUTOMATCH_INH is an alarm indicating that the automatic match function isdisabled. When the automatic match function of the board is disabled, the system reports thealarm if the board cannot match the software from the system control board.

Attribute





564

Parameters

None.


When a board whose version is not consistent with the software version of the NE is installed,the software versions of the whole NE are not consistent if the board cannot automatically matchthe software from the system control board. As a result, certain functions of the NE cannot runnormally.

Possible Causes

Cause 1: The automatic match function is disabled.

Procedure

Step 1 Cause 1: The automatic match function is disabled.1. Contact the Huawei technical support engineers for troubleshooting.

----End

Related Information

None.

A.3.268 SWDL_CHGMNG_NOMATCH

Description

The SWDL_CHGMNG_NOMATCH is an alarm of software inconsistency. After an NE ispower recycled and the boards on the NE become online, if the system detects that the systemcontrol board and the CF card are inconsistent in software packages, the system reports theSWDL_CHGMNG_NOMATCH alarm.

Attribute



Parameters

None.


When the SWDL_CHGMNG_NOMATCH alarm is reported, certain functions of the NE maybe affected.



565

Possible CausesCause 1: After a system control board is replaced, the software package in the new system controlboard is inconsistent with that in the CF card.

Procedure

Step 1 Cause 1: After a system control board is replaced, the software package in the new system controlboard is inconsistent with that in the CF card.1. Perform the package diffusion again on the NE where the SWDL_CHGMNG_NOMATCH

alarm is reported.

----End


A.3.269 SWDL_COMMIT_FAIL

DescriptionThe SWDL_COMMIT_FAIL is an alarm indicating that the commission operation on the NEfails. This alarm is reported when the commission operation fails in the package diffusion.

Attribute



ParametersNone.

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: File backup fails.

Procedure

Step 1 Cause 1: File backup fails.1. Check whether the loaded package is correct.2. Perform the package diffusion again on the NE where the alarm is reported.

----End



566


A.3.270 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 CausesThe package diffusion is being performed on the NE.

Procedure

Step 1 The SWDL_INPROCESS alarm is cleared automatically after the loading or rollback iscomplete. Hence, this alarm can be neglected.

----End


A.3.271 SWDL_NEPKGCHECK

DescriptionThe SWDL_NEPKGCHECK is an alarm of software inconsistency. This alarm is reported inthe following two situations: the CF card and flash memory are inconsistent in software packageand the flash memory has a software package; in a routine check (the check is not initiated byissuing commands), the system detects that some files are missing from the software packagestored in the CF card or from the software package stored in the flash memory.



567

Attribute



Parameters

None.

Impact on the Systeml If this alarm occurs during package loading, package loading fails.

l If this alarm occurs in other conditions, automatic file matching fails.

Possible Causes

Cause 1: Certain files of the package are missing and cannot be recovered.

Procedure

Step 1 Cause 1: Certain files of the package are missing and cannot be recovered.

1. Ensure that the loaded software package is correct. Perform the package diffusion again onthe NE where the SWDL_NEPKGCHECK alarm is reported.

----End

Related Information

None.

A.3.272 SWDL_PKG_NOBDSOFT

Description

The SWDL_PKG_NOBDSOFT is an alarm indicating that certain board software is missingfrom the software package. This alarm is reported when the required software is missing fromthe software package during the automatic match of the board.

Attribute



Parameters

None.



568


The board cannot perform automatic match, because the board software is missing from thesoftware 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 uninstalled during the software package loading.

Procedure

Step 1 Cause 1: Certain board software is uninstalled during the software package loading.1. Add the required board software to the software package. Alternatively, perform the

software package loading again.

----End

Related Information

None.

A.3.273 SWDL_PKGVER_MM

Description

The SWDL_PKGVER_MM is an alarm indicating that the consistency check on the softwarepackage version fails. This alarm is reported when the consistency check on the software packageversion fails.

Attribute



Parameters

None.


The software version of the software package is inconsistent with the software version describedin the software package. As a result, certain functions of the NE may be affected.

Possible Causes

Cause 1: The software version information in the description file of the software package isinconsistent with the actual software version information.



569

Procedure

Step 1 Cause 1: The software version information in the description file of the software package isinconsistent with the actual software version information.1. Ensure that the loaded software package is correct. Perform the package diffusion again on

the NE where the alarm is reported.

----End


A.3.274 SWDL_ROLLBACK_FAIL

DescriptionThe SWDL_ROLLBACK_FAIL is an alarm indicating that the rollback on the NE fails. Thisalarm is reported when the rollback fails for any board on the NE.

Attribute



ParametersNone.

Impact on the SystemThe board software version and the NE software version may mismatch, and certain functionsof the NE may be affected.

Possible CausesCause 1: Certain board software is uninstalled during the software package loading.

Procedure

Step 1 Cause 1: Certain board software is uninstalled during the software package loading.1. Add the required board software to the software package. Alternatively, perform the

software package loading again.

----End




570

A.3.275 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: A certain board is faulty.

Procedure

Step 1 Cause 1: The quality of the synchronization source declines.1. Take different measures based on the traced synchronization source.

If... Then...

The traced synchronization source is anexternal clock

Perform Steps Step 1.2 to Step 1.4.

The traced synchronization source is aline clock

Replace the system control,switching&timing board of the upstreamNE.

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.



571

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: A certain board is faulty.1. 6.9 Replacing the System Control, Switch and Timing Board.

----End


A.3.276 SYNC_C_LOS

DescriptionThe SYNC_C_LOS is an alarm indicating that the synchronization source is lost.

Attribute



ParametersNone.

Impact on the SystemThe NE clock degrades or enters the free-run mode.

Possible CausesCause 1: The clock source is lost.

Procedure

Step 1 Cause 1: The clock source is lost.1. Troubleshoot the synchronization sources of the lost clock source based on the clock source

priority table.

If... Then...





572

If... Then...







----End

Related Information

None.

A.3.277 T_ALOS

Description

The T_ALOS is an alarm indicating that the 2 Mbit/s analog signal is lost at the specific port.

Attribute



Parameters

None.


The 2Mbit/s services are interrupted.

Possible Causesl Cause 1: No 2 Mbit/s services are received on the port.


l Cause 3: The IF cable is faulty.


Procedure

Step 1 Cause 1: No 2 Mbit/s services are received on the port.

1. Check whether the alarmed port receives the 2 Mbit/s service.



573

If... Then...

The services are not received Transmit the services to the port or delete theunnecessary service configuration.

The services are received Go to Cause 2.

Step 2 Cause 2: The equipment at the opposite end is faulty.1. Check whether the equipment at the opposite end is faulty.

If... Then...


The equipment is normal Go to Cause 3.

Step 3 Cause 3: The IF cable is faulty.1. Check whether the IF cable is faulty.

If... Then...

The IF cable is faulty Rectify the fault.

The IF cable is not faulty Go to Cause 4.

Step 4 Cause 4: The alarmed board is faulty.1. Replace the alarmed board.

----End


A.3.278 T_F_RST

DescriptionThe T_F_RST is an alarm indicating that the transmit FIFO is reset.

Attribute



ParametersNone.

Impact on the SystemThe services in the PDH path are interrupted.



574



Procedure


1. Measure the frequency offset of the input signal.

If... Then...


The frequency offset is within 50 ppm Go to Cause 2.



----End

Related Information

None.

A.3.279 T_LOC

Description

The T_LOC is an alarm indicating that the clock is lost on the transmit line side.

Attribute



Parameters

None.


The services in the alarmed AU-4 path are interrupted.

Possible Causesl Cause 1: The cross-connect and timing board is faulty.

l Cause 2: The line board is faulty.



575

Procedure

Step 1 Cause 1: The cross-connect and timing board is faulty.1. Replace the cross-connect and timing board at the local site.

If... Then...




Go to Cause 2.

Step 2 Cause 2: The line board is faulty.1. Replace the alarmed board.

----End

Related Information

None.

A.3.280 TEMP_ALARM

Description

The TEMP_ALARM is an alarm indicating that the board temperature crosses the threshold.

Attribute


Minor Environmental alarm

Parameters


Name Meaning

Parameter 1 l 0x01: The temperature crosses the upper threshold.l 0x02: The temperature crosses the lower threshold.


The board fails to work normally.



576

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 the board on the IDU, check whether the temperature control

devices, such as air-conditioners, work normally.

If... Then...

The temperature control devices workabnormally

Adjust the temperature control devices.

The temperature control devices worknormally


3. Check whether the heat dissipation hole on the IDU is covered or blocked.

If... Then...

The heat dissipation hole is covered orblocked

Clear or remove the covering materials orobstacles.

The heat dissipation hole is not covered orblocked

Go to Cause 2.

Step 2 Cause 2: The temperature detection circuit of the board is faulty.1. If the ambient temperature is normal and no other heat dissipation problems exist, replace

the alarmed board.

----End


A.3.281 THUNDERALM

DescriptionThe THUNDERALM is an alarm indicating the surge protection failure. If the system detectsthe surge protection circuit fails, the THUNDERALM occurs.

Attribute





577

Parameters

None.


When the THUNDERALM occurs, the system operation and services are not affected, but thesurge protection function fails.

Possible Causes

The possible causes of the THUNDERALM alarm are as follows:

l Cause 1: The fuse tube of the surge protection circuit is interrupted.l Cause 2: A certain board is faulty.

Procedure

Step 1 Cause 1: The fuse tube of the surge protection circuit is interrupted.1. Replace the fuse tube, and then check whether the alarm is cleared.

Step 2 Cause 2: A certain board is faulty.1. Replace the board that reports the THUNDERALM alarm.

----End

Related Information

None.

A.3.282 TR_LOC

Description

The TR_LOC is an alarm indicating that the clock is faulty. This alarm is reported when a boarddetects that the clock signal transmitted from the clock unit to the board is lost.

Attribute



Parameters




578

Name Meaning

Parameter 1 Indicates the slot ID of the board that loses the clock. The value is always 0x01.


When this alarm occurs, the board fails to work.

Possible Causesl Cause 1: If one board reports this alarm, the board hardware is faulty.

l Cause 2: If multiple boards report this alarm, the clock cable of the cross-connect board isfaulty.

Procedure

Step 1 Locate the alarmed board according to the alarm parameter.

Step 2 Cause 1: If one board reports this alarm, the board hardware is faulty.

1. Perform a warm reset on the alarmed board, and then check whether the alarm is cleared.If the alarm persists, perform a cold reset on the alarmed board. For details, see Resettinga Boards.

2. If the alarm persists, remove the alarmed board and check whether certain pins on thebackplane are bent. Insert the board again, and then check whether the alarm is cleared.

3. If the alarm persists, replace the alarmed board. For details, see Replacing a Board.

Step 3 Cause 2: If multiple boards report this alarm, the clock cable of the cross-connect board is faulty.

1. Perform a cold reset on the cross-connect board, and then check whether the alarm iscleared.

2. If the alarm persists, remove and insert the cross-connect board, and then check whetherthe alarm is cleared.

3. If the alarm persists, replace the cross-connect board.

----End

Related Information

None.

A.3.283 TU_AIS

Description

The AU_AIS is an alarm indicating that the TU has errors. This alarm is reported if a boarddetects that the signal in the TU path is all 1s.



579

Attribute



Parameters

None.


The service in the alarmed TU path is interrupted. If the services are configured with protection,protection switching is also triggered.

Possible Causesl Cause 1: Configuration data is incorrect.l Cause 2: The line is faulty.l Cause 3: The board at the opposite end is faulty.l Cause 4: The board at the local end is faulty.

Procedure

Step 1 Cause 1: Configuration data is incorrect.1. See Creating the Cross-Connections of Point-to-Point Services to check whether the SDH

service data is incorrect.

If... Then...

The SDH service data is incorrect Change the configuration data.

The SDH service data is correct Go to Cause 2.

Step 2 Cause 2: The line is faulty.1. Check whether a line alarm that causes AIS insertion is reported on the service trail.

NOTEFor details about the line alarms that cause AIS insertion, see E.2.6 AIS Insertion.

If... Then...

The line alarm is reported Clear the line alarms that cause AIS insertion.

No line alarms are reported Go to the next step.

2. See 8.5 Software Loopback to locate whether the board at the local end or at the oppositeend is faulty.

If... Then...

The board at the opposite end is faulty Go to Cause 3.

The board at the local end is faulty Go to Cause 4.



580

Step 3 Cause 3: The board at the opposite end is faulty.

1. Replace the faulty board at the opposite end.

Step 4 Cause 4: The board at the local end is faulty.

1. Replace the board where the local line unit resides.

If... Then...





2. Replace the system control, cross-connect, and timing board at the local end.

If... Then...






----End

Related Information

None.

A.3.284 TU_AIS_VC12

Description

The 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



Parameters




581

Name Meaning



Impact on the SystemWhen this alarm occurs, the services in the alarmed VC-12 path are interrupted. If the servicesare configured with protection, 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 site is faulty.l Cause 4: 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 the Cross-

Connections of Point-to-Point Services.

If... Then...


The SDH service data is correct Go to Cause 2.

Step 2 Cause 2: The line is faulty.1. Check whether a line alarm that causes AIS insertion is reported on the service trail.

NOTEFor details about the line alarms that cause AIS insertion, see E.2.6 AIS Insertion.

If... Then...

The line alarm is reported Change the configuration data.

No line alarms are reported Go to Step 3.

Step 3 Check whether the fault occurs at the local site or at the opposite site. For details, see 8.5.5Setting Loopbacks for the EOS/EoPDH-Plane Ethernet Interface Board.

If... Then...

The board at the opposite site is faulty Go to Cause 3.

The board at the local site is faulty Go to Cause 4.

Step 4 Cause 3: The board at the opposite site is faulty.1. Replace the faulty board at the opposite site.

Step 5 Cause 4: The board at the local site is faulty.



582

1. Replace the line board at the local site. For details, see 6.3 Replacing the SDH OpticalInterface Board.

If... Then...

The alarm clears after the board isreplaced




2. Replace the alarmed board at the local site.

----End

Related Information

None.

A.3.285 TU_AIS_VC3

Description

The TU_AIS_VC3 is a TU-3 alarm indication. The alarm is reported when a board detects TUpointers of all "1"s.

Attribute



Parameters


Name Meaning




The services in the alarmed TU-3 paths are interrupted. If the services are configured withprotection, protection switching is triggered.



583

Possible Causesl Cause 1: SDH service configuration data is incorrect.l Cause 2: The service path is faulty.l Cause 3: The board at the opposite end is faulty.l Cause 4: The board at the local end is faulty.

ProcedureStep 1 Cause 1: SDH service configuration data is incorrect.

1. Follow instructions in Creating the Cross-Connections of Point-to-Point Services to checkwhether the SDH service configuration data is incorrect.

If... Then...

The SDH service configuration data isincorrect

Rectify the SDH service configurationdata.

The SDH service configuration data iscorrect

Go to cause 2.

Step 2 Cause 2: The service path is faulty.1. Check whether a line alarm that will cause AIS insertion is reported on the service path.

NOTEFor the line alarms that will cause AIS insertion, see E.2.6 AIS Insertion.

If... Then...

A line alarm that will cause AISinsertion is reported

Rectify the SDH service configuration data.

No line alarm is reported Go to step 3.

Step 3 Follow instructions in 8.5.4 Setting a Loopback for the Packet-plane Ethernet InterfaceBoard to identify whether the board at the local end or at the opposite end is faulty.

If... Then...

The board at the opposite end is faulty Go to cause 3.

The board at the local end is faulty Go to cause 4.

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. Follow instructions in 6.3 Replacing the SDH Optical Interface Board to replace the line

board at the local end.

If... Then...



2. Follow instructions in 6.9 Replacing the System Control, Switch and Timing Board toreplace the system control, switching, and timing board.



584

If... Then...


The alarm persists Follow instructions in Replacing an Alarmed Board to replace theboard that reports the alarm.

----End


A.3.286 TU_LOP

DescriptionThe TU_LOP is an alarm indicating that the TU pointer is lost. This alarm is reported if a boarddetects that the TU-PTR value is an invalid pointer or NDF reversion in eight consecutive frames.

Attribute



ParametersNone.

Impact on the SystemThe service in the alarmed TU path is interrupted. If the services are configured with protection,protection switching is also triggered.

Possible Causesl Cause 1: The system control, cross-connect, and timing board is faulty.l Cause 2: The tributary board is faulty.

Procedure

Step 1 Cause 1: The system control, cross-connect, and timing board is faulty.1. Replace the system control, cross-connect, and timing board at the local end.

If... Then...




Go to Cause 2.



585

Step 2 Cause 2: The tributary board is faulty.1. Replace the board where the tributary unit resides.

----End


A.3.287 TU_LOP_VC12

DescriptionThe TU_LOP_VC12 is an alarm indicating that the VC-12 TU pointer is lost. This alarm isreported when a board receives invalid pointers or new data flags (NDFs) in eight consecutiveVC-12 frames.

Attribute




Name Meaning



Impact on the SystemServices in the alarmed TU path are interrupted. If the services are configured with protection,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.



586

1. Check whether the SDH service data is correct. For details, see Creating the Cross-Connections of Point-to-Point Services.

If... Then...


The SDH service data is correct Go to Step 2.

Step 2 Check whether the fault occurs at the local site or at the opposite site. For details, see 8.5.5Setting Loopbacks for the EOS/EoPDH-Plane Ethernet Interface Board.

If... Then...

The board at the opposite site is faulty Go to Cause 2.

The board at the local site is faulty Go to Cause 3.

Step 3 Cause 2: The board at the opposite site is faulty.1. In this case, replace the faulty board at the opposite site.

Step 4 Cause 3: The board at the local site is faulty.1. Replace the line board at the local site. For details, see 6.3 Replacing the SDH Optical

Interface Board.

If... Then...





2. Replace the alarmed board at the local site.

----End

Related Information

None.

A.3.288 TU_LOP_VC3

Description

The TU_LOP_VC3 alarm indicates that a TU-3 pointer is lost. This alarm is reported if a boarddetects that eight consecutive VC-3 TU-PTR values are invalid or the NDF field in eightconsecutive VC-3 TU-PTR values are reversed.

Attribute





587


Name Meaning



Impact on the SystemThe services in the alarmed TU-3 path are interrupted. If the services are configured withprotection, protection switching is triggered.

Possible Causesl Cause 1: SDH service configuration data is incorrect.l Cause 2: The board at the opposite end is faulty.l Cause 3: The board at the local end is faulty.

Procedure

Step 1 Cause 1: SDH service configuration data is incorrect.1. Follow instructions in Creating the Cross-Connections of Point-to-Point Services to check

whether the SDH service configuration data is incorrect.

If... Then...

The SDH service configuration data isincorrect

Rectify the SDH service configurationdata.

The SDH service configuration data iscorrect

Go to step 2.

Step 2 Follow instructions in 8.5.4 Setting a Loopback for the Packet-plane Ethernet InterfaceBoard to identify whether the board at the local end or at the opposite end is faulty.

If... Then...

The board at the opposite end is faulty Go to cause 2.

The board at the local end is faulty Go to cause 3.

Step 3 Cause 2: The board at the opposite end is faulty.1. Replace the faulty board at the opposite end.

Step 4 Cause 3: The board at the local end is faulty.1. Follow instructions in 6.3 Replacing the SDH Optical Interface Board to replace the line

board at the local end.



588

If... Then...



2. Follow instructions in 6.9 Replacing the System Control, Switch and Timing Board toreplace the system control, switching, and timing board.

If... Then...



3. Follow instructions in Replacing an Alarmed Board to replace the board that reports thealarm.

----End


A.3.289 TUNNEL_APS_DEGRADED

DescriptionThe TUNNEL_APS_DEGRADED is an alarm indicating that a tunnel protection groupdegrades.

Attribute


Major Service alarm

ParametersNone.

Impact on the SystemThe protection tunnel is faulty and the protection group fails.

Possible CausesCause: The protection tunnel in the tunnel protection group is faulty.

Procedure

Step 1 Cause: The protection tunnel in the tunnel protection group is faulty.1. Check the status of the tunnel protection group and confirm that the protection tunnel is

faulty.



589

2. 8.3.3 Browsing Current Alarms and clear the alarms in the protection tunnel.

----End

Related Information

None.

A.3.290 UHCS

Description

The UHCS is an alarm of uncorrected header check sequence. This alarm occurs when multipleuncorrectable bit errors exist in the cell headers.

Attribute



Parameters

None.


When the UHCS alarm occurs, some cells with multiple bit errors are detected during celldelimitation at the ATM port. Consequently, the user cells are lost.

Possible Causesl Cause 1: A few bit errors occur in the receive path related to the ATM port which reports

the UHCS alarm.l Cause 2: The ATM physical-layer processing chip of the board is faulty.

Procedure

Step 1 Cause 1: A few bit errors occur in the receive path connected to the ATM port which reports theUHCS alarm.1. On the NMS, check whether the related receive path reports any alarms indicating excessive

bit errors, such as B1_SD, B2_SD, and B3_SD.2. On the NMS, check whether the service is looped.3. If yes, modify the service configuration to release the loop, and then check whether the

alarm is cleared.

Step 2 Cause 2: The ATM physical-layer processing chip of the board is faulty.1. Perform a cold reset on the board that reports the UHCS alarm and check whether the alarm

is cleared. For details, see 8.6.1 Cold Reset.



590

2. Optional: If the UHCS alarm persists after the cold reset, replace the alarmed board andcheck whether the alarm is cleared. For details, see 6.5 Replacing the Smart E1 Board.

----End


A.3.291 UP_E1_AIS

DescriptionThe UP_E1_AIS is an alarm indication of the 2 Mbit/s uplink signal. This alarm is reportedwhen the tributary board detects that the 2 Mbit/s uplink signal is all 1s.

Attribute



ParametersNone.

Impact on the SystemE1 signals are unavailable.

Possible Causesl Cause 1: The opposite equipment transmits the AIS signal.l Cause 2: The receive unit of the tributary board on the local equipment is faulty.

Procedure

Step 1 Cause 1: The opposite equipment transmits the AIS signal.1. Check whether the opposite equipment transmits the AIS signal.

If... Then...

The opposite equipment transmits theAIS signal

Rectify the fault on the opposite equipment.

The opposite equipment does nottransmit the AIS signal

Go to Cause 2.

Step 2 Cause 2: The receive unit of the tributary board on the local equipment is faulty.1. Replace the alarmed board.

----End



591

Related Information

None.

A.3.292 VC_AIS

Description

The VC_AIS is an alarm indication of the virtual channel (VC) connection. This alarm occurswhen the VC connection that is set with the segment end point attribute receives the AIS cells,indicating that the upstream ATM services are abnormal.

Attribute



Parameters


Name Meaning

Parameter 1 Indicates the direction of ATM connection.

l 0x01: forwardl 0x02: backward

Parameter 2 Indicates the status of ATM connection.

l 0x01: working connectionl 0x00: protection connection

Parameter 3 Indicates the segment and end attribute of ATM connection.

l 0x01: segmentl 0x02: end

Impact on the Systeml If the continuity check (CC) sink is enabled on an upstream NE but the upstream NE does

not receive any CC cells, the local NE reports the VP_AIS. Then, the connection, thoughnot interrupted, is not loaded with any user service.

l In other cases, when the local NE detects that the VC connection is interrupted, the AIScells are inserted in the downstream direction and the RDI cells are returned to the upstreamNE.



592

Possible Causesl Cause 1: An upstream NE reports the VC_LOC, and the AIS cells are inserted to the

downstream.l Cause 2: On the local NE, the ATM port connected to a faulty upstream SDH path is

abnormal in the receive direction and therefore inserts AIS cells to the downstream.l Cause 3: The board on the local NE is faulty.

Procedure

Step 1 Cause 1: An upstream NE reports the VC_LOC, and the AIS cells are inserted to the downstream.1. On the NMS, check whether the VC_LOC occurs and the ATM connections that report the

VC_LOC have the same ID.2. If the VC_LOC occurs, clear the VC_LOC and then the AIS insertion stops.

Step 2 Cause 2: On the local NE, the ATM port connected to a faulty upstream SDH path is abnormalin the receive direction and therefore inserts AIS cells to the downstream.1. Check whether any alarm, such as the R_LOS, R_LOF, MS_AIS, AU_AIS, AU_LOP,

TU_AIS or TU_LOP occurs in the upstream SDH path.2. If yes, clear these alarms and then the AIS insertion stops.

Step 3 Cause 3: The board on the local NE is faulty.1. Perform a cold reset on the alarmed board.2. If the alarm persists, replace the alarmed board.

----End

Related InformationUnidirectional Connection

A complete bidirectional connection consists of two unidirectional connections: a forwardconnection and a backward connection. The direction of the forward and backward connectionsis based on the same node.

End and Segment

The end point refers to the termination point in the chain network, and it is used to monitor thewhole virtual connection.

The segment point is, generally, used to monitor a segment of the whole link.

Segment End Point

This is one of the segment end attributes. The segment end attributes include: segment point,end point, segment and end point, non segment and end point.

l If an NE is set with the segment end point attribute, it can retrieve the alarms that aregenerated at the segment and end.

l If an NE is set with the segment point attribute, it can retrieve the alarms that are generatedat a segment.

l If an NE is set with the end point attribute, it can retrieve the alarms that are generated atan end.



593

l If an NE is set with the non segment end point attribute, it fails to retrieve the alarms thatare generated at the segment and end.

A.3.293 VC_LOC

Description

The VC_LOC is an alarm indicating loss of connectivity on the virtual channel (VC). This alarmis reported when the CC is enabled but no cell is received within 3.5s (±0.5s).

Attribute



Parameters


Name Meaning






l 0x01: segmentl 0x02: endl 0x03: segment and end

Impact on the Systeml If the CC sink is enabled on the local NE but the local NE does not receive any CC cells,

the service connection, though not interrupted, is not loaded with any user service.

l In other cases, the service is interrupted when the alarm occurs.

l When this alarm occurs, the system automatically inserts AIS cells to the downstream.



594

Possible Causesl Cause 1: The CC sink is enabled on the local NE, but no CC source is enabled on the

upstream NE.l Cause 2: No bandwidth is available on the local NE.l Cause 3: On the local NE, the ATM port connected to a faulty upstream SDH path is

abnormal in the receive direction.l Cause 4: The board on the local NE is faulty.

Procedure

Step 1 Cause 1: The CC sink is enabled on the local NE, but no CC source is enabled on the upstreamNE.1. Check whether the CC function on the local NE is activated.2. If yes, Deactivate the CC function on the local NE. Then, check whether the alarm is cleared.

Step 2 Cause 2: No bandwidth is available on the local NE.1. On the NMS, check whether the bandwidth allocated to the tunnel is fully used.2. If yes, increase the bandwidth or eliminate the sources that transmit a large amount of

invalid data.

Step 3 Cause 3: On the local NE, the ATM port connected to a faulty upstream SDH path is abnormalin the receive direction.1. Check whether any alarm, such as the R_LOS, R_LOF, MS_AIS, AU_AIS, AU_LOP,

TU_AIS or TU_LOP, occurs in an upstream SDH path.2. If yes, clear these alarms and check whether the VC_LOC is cleared.


----End


A.3.294 VC_RDI

DescriptionThe VC_RDI is an alarm indicating that defects occur at the remote end of the virtual channel(VC) connection. This alarm occurs when a forward or backward VC connection that is set withthe segment end point attribute receives the RDI cells, indicating that the downstream servicesare abnormal.



595

Attribute




Name Meaning







Impact on the Systeml When this alarm occurs, it indicates that a segment end point at the remote end of the VC

connection receives AIS cells and returns RDI cells to the local end, but the services at thelocal end are not affected.

Possible Causesl Cause 1: The VC_AIS occurs in the receive direction of the downstream VC connection.l Cause 2: A certain board is faulty.

Procedure

Step 1 Cause 1: The VC_AIS occurs in the receive direction of the downstream VC connection.1. Check whether the VC_AIS occurs in the receive direction of the downstream VC

connection.2. If yes, clear the VC_AIS and then check whether the VC_RDI is cleared.

Step 2 Cause 2: A certain board is faulty.1. Perform a cold reset on the alarmed board.



596

2. If the alarm persists, replace the alarmed board.

----End

Related InformationUnidirectional Connection


End and Segment



Segment End Point






A.3.295 VCAT_LOA

DescriptionThe 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 VCTRUNKexceed the permissible limit.

Attribute






597

Name Meaning


Parameter 2, Parameter 3 Indicate the ID of the VCTRUNK path.

Impact on the SystemThe virtually concatenated services are interrupted.

Possible CausesCause 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 alarmed VCTRUNK path based on the alarm parameters.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


A.3.296 VCAT_LOM_VC12

DescriptionThe 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






598

Name Meaning




The alarmed path is unavailable. If the LCAS function is disabled, the services in the path areinterrupted.

Possible Causesl Cause 1: Bit errors occur on 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 over long.

Procedure

Step 1 Cause 1: Bit errors occur on the line.1. Check whether any bit error alarm such as BIP_EXC and BIP_SD occurs.

If... Then...

A bit error alarm occurs Handle the alarm immediately.

No bit error 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

Interface Board.2. Replace the board and then check whether the alarm clears.

If... Then...



Step 3 Cause 3: The delays between virtual concatenations are over 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.

The VCAT_LOA alarm is not reported Go to Cause 2.

2. Check whether the VCAT_LOM_VC12 alarm clears after handling the VCAT_LOAalarm.

If... Then...




599

If... Then...

The alarm persists Replace the alarmed board at the local site. For details, see Replacethe alarmed board.

----End

Related Information

None.

A.3.297 VCAT_LOM_VC3

Description

The VCAT_LOM_VC3 alarm indicates the loss of virtually concatenated multiframes in a VC-3path. A board reports this alarm when detecting that byte H4 in the VC-3 path does not matchthe expected multiframe sequence.

Attribute



Parameters


Name Meaning




The 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 byte K4 sent from the opposite site is incorrect.l Cause 3: The delays between virtual concatenations are too long.



600

Procedure

Step 1 Cause 1: Bit errors occur in the line.1. Check for the bit error alarms such as BIP_EXC or BIP_SD.

If... Then...

The bit error alarms exist Handle the alarms immediately.

The bit error alarms do not exist Go to Cause 2.

Step 2 Cause 2: The MFI field in byte K4 sent from the opposite site is incorrect.1. Follow instructions in 6.6 Replacing the Ethernet Interface Board to replace the board

at the opposite site.2. Replace the alarmed board and then check whether the alarm clears.

If... Then...



Step 3 Cause 3: The delays between virtual concatenations are too long.1. Check whether a VCAT_LOA alarm is reported in this path.

If... Then...

A VCAT_LOA alarm is reported in thispath

Handle the VCAT_LOA alarmimmediately.

No VCAT_LOA alarm is reported in thispath

Go to Cause 2.

2. Check whether the VCAT_LOM_VC3 alarm clears after handling the VCAT_LOA alarm.

If... Then...

The VCAT_LOM_VC3 alarm clears End the alarm handling.

The VCAT_LOM_VC3 alarm persists Follow instructions in 6.6 Replacing theEthernet Interface Board to replace thealarmed board at the local site.

----End


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



601

Attribute




Name Meaning



Impact on the SystemThe alarmed path is unavailable. If the LCAS function is disabled, services are interrupted.

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.

If... Then...




Contact Huawei technical support engineersfor handling the alarm.

----End



602


A.3.299 VCAT_SQM_VC3

DescriptionThe VCAT_SQM_VC3 alarm indicates that the sequence (SQ) number mismatch of a virtualconcatenation in a VC-3 path. A board reports this alarm when detecting that the SQ of a virtualconcatenation does not match the expected value.

Attribute




Name Meaning



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 on a link or a link is faulty.l Cause 2: The SQ number sent from the opposite site is incorrect.

Procedure

Step 1 Cause 1: Bit errors occur on a link or a link is faulty.1. Check for bit error alarms or line alarms, especially BIP_EXC and BIP_SD.

If... Then...

Bit error alarms or line alarms occur Clear these alarms.



603

If... Then...

No bit error alarms or line alarms occur Go to Cause 2.


Step 2 Cause 2: The SQ number sent from the opposite site is incorrect.

1. Replace the related board at the opposite site.

If... Then...

The VCAT_SQM_VC3 alarm clears after theboard is replaced


The VCAT_SQM_VC3 alarm persists afterthe board is replaced

Contact Huawei technical supportengineers.

----End

Related Information

None.

A.3.300 VOLT_LOS

Description

The VOLT_LOS is an alarm indicating that the power voltage is unavailable.

Attribute



Parameters


Name Meaning



The ODU that is connected to the IF board that reports this alarm fails to work.



604

Possible Causesl Cause 1: The output power is abnormal.

l Cause 2: The input power is abnormal.

Procedure

Step 1 Cause 1: The output power is abnormal.

1. Check the power switch of the ODU.

If... Then...

The power switch is turned off Turn on the power switch.

The power switch is turned on Go to the next step.

2. Use the multimeter to check the IF fiber jumper, IF cable, or ODU section by section fora short circuit.

If... Then...

A short circuit exists Replace the short-circuited component,and then replace the alarmed IF board.

No short circuits exist Replace the alarmed IF board.

CAUTIONIf the alarm is reported due to a short circuit, replace the short-circuited cable or ODU, andthen replace the IF board. Otherwise, the new IF board may be damaged again.

Step 2 Cause 2: The input power is abnormal.

1. Replace the alarmed IF board.

----End

Related Information

None.

A.3.301 VP_AIS

Description

The VP_AIS is an alarm indication of the virtual path (VP) connection. When a forward orbackward VP connection that is set with the segment end point attribute receives the AIS cells,the alarm is reported, indicating that the upstream services are abnormal.



605

Attribute



Parameters


Name Meaning







Impact on the Systeml If the continuity check (CC) sink is enabled on an upstream NE but the upstream NE does

not receive any CC cells, the local NE reports the alarm. In this case, the connection, thoughnot interrupted, is not loaded with any user service.

l In other cases, when the local NE detects that the VP connection is interrupted, the AIScells are inserted to the downstream and the RDI cells are returned to the upstream NE.

Possible Causesl Cause 1: An upstream NE reports the VP_LOC, and the AIS cells are inserted to the

downstream.

l Cause 2: On the local NE, the ATM port connected to a faulty upstream SDH path isabnormal in the receive direction and inserts AIS cells to the downstream.

l Cause 3: The board on the local NE is faulty.

Procedure

Step 1 Cause 1: An upstream NE reports the VP_LOC, and the AIS cells are inserted to the downstream.



606

1. On the NMS, check whether the VP_LOC occurs and the ATM connections that report theVP_LOC have the same ID.

2. If the VP_LOC occurs, clear the VP_LOC and then the AIS insertion stops.

Step 2 Cause 2: On the local NE, the ATM port connected to a faulty upstream SDH path is abnormalin the receive direction and therefore inserts AIS cells to the downstream.1. Check whether any alarm, such as the R_LOS, R_LOF, MS_AIS, TU_AIS, TU_LOP,

AU_AIS or AU_LOP, occurs in an upstream SDH path.2. If yes, clear these alarms and then the AIS insertion stops.


----End

Related Information

Unidirectional Connection


End and Segment



Segment End Point






A.3.302 VP_LOC

Description

The VP_LOC is an alarm indicating loss of connectivity on the virtual path (VP). This alarm isreported when the CC is enabled but no cell is received within 3.5s (±0.5s). When any cell isreceived, the alarm is cleared automatically.



607

Attribute



Parameters


Name Meaning






l 0x01: segmentl 0x02: endl 0x03: segment and end

Impact on the Systeml If the CC sink is enabled on the local NE but the local NE does not receive any CC cells,

the service connection, though not interrupted, is not loaded with any user service.

l In other cases, the service is interrupted when the alarm occurs.

l When this alarm occurs, the system automatically inserts AIS cells to the downstream.

l The VP_LOC is suppressed when the VP_AIS occurs.

Possible Causesl Cause 1: The CC sink is enabled on the local NE, but no CC source is enabled on the

upstream NE.

l Cause 2: No bandwidth is available on the local NE.

l Cause 3: On the local NE, the ATM port connected to a faulty upstream SDH path isabnormal in the receive direction.




608

Procedure

Step 1 Cause 1: The CC sink is enabled on the local NE, but no CC source is enabled on the upstreamNE.

1. Deactivate the CC function on the local NE.

Step 2 Cause 2: No bandwidth is available on the local NE.

1. On the NMS, check whether the bandwidth allocated to the tunnel is fully used.

2. If yes, increase the bandwidth or eliminate the sources that transmit a large amount ofinvalid data.

Step 3 Cause 3: On the local NE, the ATM port connected to a faulty upstream SDH path is abnormalin the receive direction.

1. Check whether any alarm, such as the R_LOS, R_LOF, MS_AIS, TU_AIS, TU_LOP,AU_AIS or AU_LOP, occurs in an upstream SDH path.

2. If yes, clear these alarms.


1. Perform a cold reset on the alarmed board.

2. Check whether the alarm is cleared. If not, replace the alarmed board.

----End

Related Information

None.

A.3.303 VP_RDI

Description

The VP_RDI is an alarm indicating that defects occur at the remote end of the virtual path (VP)connection. This alarm occurs when a forward or backward VP connection that is set with thesegment end point attribute receives the RDI cells, indicating that the downstream services areabnormal.

Attribute



Parameters




609

Name Meaning







Impact on the Systeml When this alarm occurs, the services are not affected. This alarm just indicates that the

services in the receive direction of the downstream VP connection are abnormal. The AIScells are received in a segment point of the connection, and the RDI cells are returned tothe upstream VP connection.

Possible Causesl Cause 1: The VP_AIS occurs in the receive direction of the downstream VP connection.l Cause 2: A certain board is faulty.

Procedure

l Cause 1: The VP_AIS occurs in the receive direction of the downstream VP connection.1. Check whether the VP_AIS occurs in the receive direction of the downstream VP

connection.2. If yes, clear the VP_AIS and then check whether the VP_RDI is cleared.

l Cause 2: A certain board is faulty.1. Perform a cold reset on the alarmed board. For details, see 8.6.1 Cold Reset.2. If the alarm persists, replace the alarmed board. For details, see 6.5 Replacing the

Smart E1 Board.

----End

Related Information

Unidirectional Connection


End and Segment



610



Segment End Point






A.3.304 W_R_FAIL

DescriptionThe W_R_FAIL is an alarm indicating a failure of reading or writing chip register.

Attribute




Name Meaning

Parameter 1 Indicates the ID of the register.


Impact on the SystemServices in the alarmed path are interrupted.

Possible CausesCause 1: The chip register is faulty or the read/write timing is incorrect.



611

ProcedureStep 1 Cause 1: The chip register is faulty or the read/write timing is incorrect.


----End


A.3.305 WRG_BD_TYPE

DescriptionThe WRG_BD_TYPE is an alarm indicating that the type of the board is incorrect.

Attribute



ParametersNone.

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.

ProcedureStep 1 Cause 1: Configuration data is incorrect.

1. See Configuring the Logical Board to check whether the board type complies with theplanning requirement.

If... Then...

The board type does not meet the planningrequirement

Change the configuration data.

The board type meets the planning requirement Go to Cause 2.

Step 2 Cause 2: The board of an incorrect type is installed.1. Replace the board of an incorrect type.

----End



612


A.3.306 XPIC_LOS

DescriptionThe XPIC_LOS is an alarm indicating that the XPIC compensation signals are lost.

Attribute



ParametersNone.

Impact on the SystemBit errors may occur in the service at the port, and the service may even be interrupted.

Possible Causesl Cause 1: Configuration data is incorrect.l Cause 2: The radio link is faulty.l Cause 3: The XPIC cable is faulty.l Cause 4: The IF board or ODU is faulty.

Procedure

Step 1 Cause 1: Configuration data is incorrect.1. Check whether the XPIC function needs to be enabled. If not, see Setting IF Attributes to

disable the XPIC function, and then perform a self-loop at the XPIC port on the board byusing the XPIC cable.

Step 2 Cause 2: The radio link is faulty.1. Check whether the paired board that is connected to the XPIC IF board through the XPIC

cable reports the MW_LOF alarm. If yes, first clear the MW_LOF alarm.

Step 3 Cause 3: The XPIC cable is faulty.1. Check the connection of the XPIC cable.

If... Then...

The cable is improperly connected Connect the XPIC cable properly.

The cable is properly connected Go to the next step.



613

2. Test the make and break of the XPIC cable by using the multimeter. If the XPIC cable is

damaged, replace it.

Step 4 Cause 4: The IF board or ODU is faulty.

Locate the fault by replacing the IF board or ODU.

1. Replace the paired board of the XPIC IF board.

The paired board of the XPIC IF board refers to the other XPIC IF board connected to thealarmed XPIC IF board through the XPIC cable.

If... Then...





2. Replace the ODU that is connected to the paired XPIC IF board.

If... Then...

The alarm is cleared after the ODU isreplaced


The alarm persists after the ODU isreplaced

Replace the alarmed XPIC IF board.

----End




614

B Abnormal Event Reference

Abnormal events are important indicators when abnormalities occur on the equipment. Thischapter describes all the possible important abnormal events on the OptiX RTN 910 and how tohandle these events.

B.1 Major Abnormal Performance Event ListAbnormal events are important indicators when abnormalities occur on the equipment. Thischapter describes all the possible important abnormal events on the OptiX RTN 910 and how tohandle these events.

OptiX RTN 910 Radio Transmission SystemMaintenance Guide (U2000) B Abnormal Event Reference


615

B.1 Major Abnormal Performance Event ListAbnormal events are important indicators when abnormalities occur on the equipment. Thischapter describes all the possible important abnormal events on the OptiX RTN 910 and how tohandle these events.

Table B-1 Major performance event list

Event Name Source

B.2.1 IF 1+1 Protection Switching CSHA, CSHB, CSHC, CSHD, CSHE, andCSTA

B.2.2 N+1 Protection Switching

B.2.3 SNCP Switching

B.2.4 Linear MSP Switching

B.2.5 Status Change of an APS ProtectionGroup

B.2.6 Reporting of PW APS SwitchingEvents

B.2.7 RMON Performance Value Belowthe Lower Limit

EM6FA, EM6TA, EFP8, EM4F, EM4T,EM6X, EM6TB, EMS6, EM6F and EM6T

B.2.8 RMON Performance Value Abovethe Upper Limit

B.2 Abnormal Performance Events and HandlingProcedures

This chapter describes all the important abnormal performance events on the OptiX RTN 910in an alphabetical order and how to handle these abnormal performance events.

B.2.1 IF 1+1 Protection Switching

Description

This abnormal event indicates that the 1+1 HSB/FD/SD switching occurs on the equipment.

Attribute

Severity Type

Major Service



616

ParametersName Meaning

Protection Group ID Indicates the ID of the protection group wherethe IF 1+1 protection switching occurs.

Current Working Board Slot Indicates the slot ID of the current workingboard.

Current Working Board Sub Slot Indicates the sub slot ID of the currentworking board.The value is always 0xff.

Current Working Port No. Indicates the ID of the working port.

Current Active Board Indicates the current working board.l Active on working boardl Active on protection board

Active Board Status Indicates the current state of the workingboard.l Normall Failedl MW_RDIl Unknown

Standby Board Status Indicates the current status of the protectionboard.l Normall Failedl MW_RDIl Unknown

Switching Request 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

NOTEThe parameter names and parameter values may vary with the version of the NMS.



617

Impact on Systeml During the HSB protection switching, services are interrupted. After the HSB switching is

complete, the services are restored to normal.l During the HSM protection switching, no bit errors occur and the services are not affected.

Related AlarmsWhen the IF 1+1 protection switching occurs, the RPS_INDI alarm is reported.

Possible Causesl The possible causes of the HSB protection switching are as follows:

– The hardware of the ODU or IF unit at the local end is faulty.– The working channel of the local end receives the MW_RDI alarm.– The external switching, which is triggered by the switching command issued from the

NMS software, occurs. The external switching includes lockout of switching, forcedswitching, and manual switching.

l The possible causes of the HSM protection switching are as follows:The quality of the main channel degrades.– In the case of Hybrid radio, the quality of the main channel degrades.– In the case of SDH/PDH radio, an alarm that triggers the HSM switching is reported on

the radio link. These alarms include R_LOC, R_LOF, R_LOS, MW_LOF,MW_FEC_UNCOR, B1_SD(IF1).

Procedure

Step 1 Rectify the fault according to the switching request type indicated by the parameter and thedescription in RPS_INDI.

----End

B.2.2 N+1 Protection Switching

DescriptionThis abnormal event indicates that the N+1 protection switching occurs on the equipment.

AttributeSeverity Type

Major Service



618


Protection Group ID Indicates the ID of the protection group wherethe IF N+1 protection switching occurs.

Path Name ID Indicates the ID of the path where the IF N+1protection switching occurs.

Switching Request Indicates the type of an IF N+1 protectionswitching request.l Lockout of protection channell Forced switchingl SF switchingl SD switchingl Manual switchingl Wait-to-restorel Exercisel Reverse requestl No request

Switching Status Indicates the state of an N+1 protectiongroup.l Protocol unstartedl Idle statusl Switching statusl Protocol starting

Protected Unit Indicates the ID of the protected channel.The ID is 0xff if no switching is performed.

Switching Local/Remote End Indication Indicates the local or remote switching.l Local endl Remote end

The switching status reason is changed Indicates the cause of the IF N+1 protectionswitching.l Local requestl External commandl K-byte requestl Timer expiry




619

Impact on SystemDuring the N+1 protection switching (not more than 50 ms), the services are interrupted. Afterthe N+1 switching is complete, the services are restored to normal. After the switching startsand before the switching is complete, the extra services are interrupted.

NOTEIf the IF N+1 protection switching is caused by exercise switching, service signals are not switched actuallybecause the exercise switching is used to check whether the NE can run the N+1 protocol normally.

Related Alarms

When the IF N+1 protection switching occurs, the NP1_SW_INDI alarm is reported.

Possible Causesl The external switching occurs.

– Lockout of protection channel

– Forced switching

– Manual switching

l An automatic switching occurs.

– The hardware of the IDU or IF board is faulty. Focus on checking whether theHARD_BAD or BD_STATUS alarm is reported.

– The MW_LOF, R_LOC, R_LOF, R_LOS, MS_AIS, or B2_EXC alarm is reportedon the working path.

Procedure

Step 1 Rectify the fault according to the switching request type and the switching cause indicated bythe parameters.

If... Then...

The switching is caused by the externalswitching

Find the cause of the external switching, andthen release the external switchingimmediately.

The switching is caused by the automaticswitching

Clear the alarm that triggers the automaticswitching.

----End

B.2.3 SNCP Switching

Description

This abnormal event indicates that the SDH SNCP switching occurs in the service that isconfigured with the SNCP.



620


Major Service


Source Indicates the service source of the SNCPprotection group.

Sink Indicates the service sink of the SNCPprotection group.

Status Indicates the current working path.l Working at protection channell Working at working channel

Switching Status Indicates the switching status.l Manual to standbyl Force to activel Force to standbyl Lockout switchingl SF switchingl SD switchingl Wait-to-restorel Idle

Working Channel Current Status Indicates the current status of the SNCPworking path.l Normall SDl SF

Protection Channel Current Status Indicates the current status of the SNCPprotection path.l Normall SDl SF




621

Impact on SystemWhen the SNCP switching occurs, you must find the cause. If the related link is faulty, recoverthe link immediately. Ensure that the states of the SNCP working path and the SNCP protectionpath are normal.

Possible Causesl The SDH SNCP switching is automatically triggered.

– The hardware of the line board is faulty.– The R_LOS, R_LOF, R_LOC, MS_AIS, B2_EXC, AU_LOP, AU_AIS,

HP_LOM, MW_LOF (only when the IF board functions as the line board),MW_LIM (only when the IF board functions as the line board), B3_EXC, B3_SD,HP_TIM (in the case of VC-4 services), HP_UNEQ (in the case of VC-4 services),TU_AIS (in the case of VC-12 services) or TU_LOP (in the case of VC-12 services),LP_UNEQ (Optional condition), LP_TIM (Optional condition), BIP_SD (Optionalcondition), BIP_EXC (Optional condition), or MW_BER_EXC.

l The SDH SNCP switching is manually triggered.– 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 automaticallytriggered

Rectify the fault according to the relatedalarm, and eliminate the conditions of theautomatic switching.

The SDH SNCP switching is manuallytriggered

Find the cause of the manual switching, andthen release the manual switchingimmediately.

----End

B.2.4 Linear MSP Switching

Abnormal Event DescriptionThis abnormal event indicates that a linear MSP switching occurs in the service that is configuredwith the MSP.

Abnormal Event AttributesLevel Type

Major Service



622

Abnormal Event ParametersParameter Name Definition

Indicates the ID of the protection group. Indicates the ID of the protection group wherea linear MSP switching occurs.

Current working path Indicates the current working path of thelinear MSP group.l Working unitl Protection unit

Switching request type Indicates the type of a linear MSP switchingrequest.l Locked switchingl Forced switchingl SF switchingl SD switchingl Manual switchingl Wait-to-restorel Exercisel Reverse requestl Non-revertive requestl No request

Switching status Indicates the switching status.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 of switching status change Indicates the cause of switching statuschange.l Local requestl External commandl K-byte requestl Timer expiry




623

Impact on Systeml During the switching time (not more than 50 ms), the services are interrupted. After the

switching is complete, the services are restored to normal. After the switching starts andbefore the switching is complete, the extra services are interrupted.

l Troubleshooting measures need to be taken immediately when an MSP switching occursbecause the possible causes are fiber cuts and failures of terminal nodes.

Relevant Alarms

When a linear MSP switching occurs, the APS_INDI alarm may be reported.

Possible Causesl An external switching command is issued to trigger manual, forced, or exercise switching.

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-12 services), or TU_LOP (in the case of VC-12 services) alarm is reported,the MSP protection group changes to the switching status, and an automatic switching alarmis reported.

l The hardware or line is faulty.

Procedure

Step 1 On the NMS, query the switching type and the protection group ID.

Step 2 Rectify the fault according to the switching request type.

If... Then...

The switching is caused by externalswitching

Find out the cause and clear the switchingimmediately.

The switching is an automatic switching Clear the relevant alarm, and rectify thehardware or line fault first.

----End

B.2.5 Status Change of an APS Protection Group

Description

This abnormal event indicates that an APS protection group switches.

Attribute

Severity Type

Major Service



624

Parameters

Name Meaning

Protection Group ID ID of the protection group whose APS statusis changed

APS Protection Group Switching Status Current working status of the APS protectiongroupl Working pathl Protection path

APS Protection Group Protocol Status APS protection group protocol status

Working Path Status of the APS ProtectionGroup

Working path status of the APS protectiongroup:l Validl Invalid

Protection Path Status of the APS ProtectionGroup

Protection path status of the APS protectiongroup:l Validl Invalid

NOTEThe parameter names and parameter values may vary according to the version of the NMS.


During the switching, the services are interrupted. After the switching is complete, the servicesare restored. After the switching starts and before the switching is complete, the extra servicesare interrupted.

Related Alarms

None.

Possible Causesl An external switching command (for example, manual switching) is issued.l An automatic switching occurs.

When an MPLS link is faulty, the MPLS_TUNNEL_LOCV, MPLS_TUNNEL_FDI,MPLS_TUNNEL_SD, MPLS_TUNNEL_SF, MPLS_TUNNEL_MISMATCH,MPLS_TUNNEL_MISMERGE, MPLS_TUNNEL_Excess, orMPLS_TUNNEL_UNKNOWN alarm occurs on the working path.

Procedure




625


If... Then...

The switching is an external switching Find the cause of the external switching, and thenclear manual switching immediately.

The switching is an automatic switching Handle the relevant alarms first.

----End

B.2.6 Reporting of PW APS Switching Events

DescriptionThis abnormal event indicates that a PW APS protection group switches.


Major Service


Protection Group ID ID of the protection group whose APS statusis changed

APS Protection Group Switching Status Current working status of the APS protectiongroupl Working pathl Protection path

APS Protection Group Protocol Status APS protection group protocol status

Working Path Status of the APS ProtectionGroup

Working path status of the APS protectiongroup:l Validl Invalid

Protection Path Status of the APS ProtectionGroup

Protection path status of the APS protectiongroup:l Validl Invalid

NOTEThe parameter names and parameter values may vary according to the version of the NMS.



626

Impact on the SystemDuring the switching, the services are interrupted. After the switching is complete, the servicesare restored. After the switching starts and before the switching is complete, the extra servicesare interrupted.

Related AlarmsNone.

Possible Causesl An external switching command (for example, manual switching) is issued.l An automatic switching occurs.

When an MPLS link is faulty, the MPLS_PW_LOCV, MPLS_PW_MISMATCH,MPLS_PW_SD, MPLS_PW_SF, MPLS_PW_MISMERGE, MPLS_PW_Excess, orMPLS_PW_UNKNOWN alarm occurs on the working path.

Procedure



If... Then...

The switching is an external switching Find the cause of the external switching, and thenclear manual switching immediately.

The switching is an automatic switching Handle the relevant alarms first.

----End

B.2.7 RMON Performance Value Below the Lower Limit

DescriptionThis abnormal event indicates that the current RMON performance value is lower than the presetlower limit.


Minor Communication



627


Performance ID Indicates the ID of the current RMONperformance event.

Current Performance Value Indicates the value of the current RMONperformance event.

Lower Limit Indicates the lower limit of the currentRMON performance event.

Impact on SystemDifferent abnormal performance events have different impacts on the system. For details, seeD.4 RMON Events and Handling Procedures.

Related AlarmsDifferent alarms are reported when different RMON performance values are lower than thelower limits. For details, see D.4 RMON Events and Handling Procedures.

Possible CausesThe lower limit of a performance event is set to a non-zero value.

Procedure

Step 1 Set the lower limit of the performance event to 0.

----End

B.2.8 RMON Performance Value Above the Upper Limit

DescriptionThis abnormal event indicates that the current RMON performance value is higher than the presetupper limit.


Minor Communication



628


Performance ID Indicates the ID of the current RMONperformance event.

Current Performance Value Indicates the value of the current RMONperformance event.

Upper Limit Indicates the upper limit of the currentRMON performance event.

Impact on SystemDifferent abnormal performance events have different impacts on the system. For details, seeD.4 RMON Events and Handling Procedures.

Related AlarmsDifferent alarms are reported when different RMON performance values are higher than theupper limits. For details, see D.4 RMON Events and Handling Procedures.

Possible CausesWhen the performance values of different abnormal RMON performance events are higher thanthe upper limits, the causes are different. For details, see D.4 RMON Events and HandlingProcedures.

Procedure

Step 1 See D.4 RMON Events and Handling Procedures to handle different abnormal performanceevents.

----End



629

C Performance Event Reference

Performance events are important indicators when the equipment performance changes. Thischapter describes all the possible performance events on the OptiX RTN 910 and how to handlethese performance events.

C.1 Performance Events (by Event Type)The list is categorized based on the performance event type, and includes all the events of theOptiX RTN 910.

C.2 Performance Events (by Logical Board)This part lists all the performance events that are reported by each board.

C.3 Performance Events and Handling ProceduresBased on the type of a performance event, this chapter describes all the performance events onthe OptiX RTN 910 and how to handle these performance events.

OptiX RTN 910 Radio Transmission SystemMaintenance Guide (U2000) C Performance Event Reference


630

C.1 Performance Events (by Event Type)The list is categorized based on the performance event type, and includes all the events of theOptiX RTN 910.

C.1.1 SDH/PDH Performance Event ListSDH/PDH performance events are classified into six categories: pointer justification,regenerator section error, multiplex section error, higher order path error, lower order path error,and E1 line side code violation.

Table C-1 Pointer Justification Performance Events

Event Name Description

AUPJCHIGH Indicates the count of positive AU pointerjustifications.

AUPJCLOW Indicates the count of negative AU pointerjustifications.

AUPJCNEW Indicates the count of new AU pointerjustifications.

TUPJCHIGH Indicates the count of positive TU pointerjustifications.

TUPJCLOW Indicates the count of negative TU pointerjustifications.

TUPJCNEW Indicates the count of new TU pointerjustifications.

Table C-2 Regenerator Section Error Performance Events


RSBBE Indicates the regenerator section backgroundblock error.

RSES Indicates the regenerator section erroredsecond.

RSSES Indicates the regenerator section severelyerrored second.

RSUAS Indicates the regenerator section unavailablesecond.

RSCSES Indicates the regenerator section consecutiveseverely errored second.



631


RSOFS Indicates the regenerator section out-of-frame second.

RSOOF Indicates the count of regenerator section out-of-frame events.

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 multiplex section backgroundblock error.

MSES Indicates the multiplex section erroredsecond.

MSSES Indicates the multiplex section severelyerrored second.

MSCSES Indicates the multiplex section consecutiveseverely errored second.

MSUAS Indicates the multiplex section unavailablesecond.

MSFEBBE Indicates the multiplex section far endbackground block error.

MSFEES Indicates the multiplex section far end erroredsecond.

MSFESES Indicates the multiplex section far endseverely errored second.

MSFECSES Indicates the multiplex section far endconsecutive severely errored second.

MSFEUAS Indicates the multiplex section far endunavailable second.

Table C-4 Higher Order Path Error Performance Events


HPBBE Indicates the higher order path backgroundblock error.



632


HPES Indicates the higher order path erroredsecond.

HPSES Indicates the higher order path severelyerrored second.

HPCSES Indicates the higher order path consecutiveseverely errored second.

HPUAS Indicates the higher order path unavailablesecond.

HPFEBBE Indicates the higher order path far endbackground block error.

HPFEES Indicates the higher order path far end erroredsecond.

HPFESES Indicates the higher order path far endseverely errored second.

HPFECSES Indicates the higher order path far endconsecutive severely errored second.

HPFEUAS Indicates the higher order path far endunavailable second.

Table C-5 Lower Order Path Error Performance Events


LPBBE Indicates the lower order path backgroundblock error.

LPES Indicates the lower order path errored second.

LPSES Indicates the lower order path severelyerrored second.

LPCSES Indicates the lower order path consecutiveseverely errored second.

LPUAS Indicates the lower order path unavailablesecond.

LPFEBBE Indicates the lower order path far endbackground block error.

LPFEES Indicates the lower order path far end erroredsecond.

LPFESES Indicates the lower order path far endseverely errored second.



633


LPFECSES Indicates the lower order path far endconsecutive severely errored second.

LPFEUAS Indicates the lower order far end unavailablesecond.

Table C-6 E1 Line Side Code Violation Performance Events


E1_LCV_SDH Indicates the count of E1 line side codeviolations.

E1_LLOSS_SDH Indicates the E1 line side loss-of-signalsecond.

E1_LES_SDH Indicates the E1 line side code violationerrored second.

E1_LSES_SDH Indicates the E1 line side code violationseverely errored second.

Table C-7 E1 Error Performance Events


E1_BBE Indicates the E1 background block error.

E1_ES Indicates the E1 errored second.

E1_SES Indicates the E1 severely errored second.

E1_CSES Indicates the E1 consecutive severely erroredsecond.

E1_UAS Indicates the E1 unavailable second.

C.1.2 Radio Performance EventsThe radio performance events are performance events of the radio link bit errors, ATPC, AM,and power.

Table C-8 Radio power performance events


TSL_MAX Maximum value of radio transmit signal level



634


TSL_MIN Minimum value of radio transmit signal level

TSL_CUR Current value of radio transmit signal level

TSL_AVG Average value of radio transmit signal level

RSL_MAX Maximum value of radio receive signal level

RSL_MIN Minimum value of radio receive signal level

RSL_CUR Current value of radio receive signal level

RSL_AVG Average value of radio receive signal level

TLHTT The duration when the ODU at the local endhas a transit power higher than the upperthreshold

TLLTT The duration when the ODU at the local endhas a transit power higher than the lowerthreshold

RLHTT The duration when the ODU at the local endhas a receive power lower than the upperthreshold

RLLTT The duration when the ODU at the local endhas a receive power lower than the lowerthreshold

Table C-9 FEC performance events


FEC_BEF_COR_ER FEC bit error rate before correction

FEC_UNCOR_BLOCK_CNT FEC uncorrected block count

FEC_COR_BYTE_CNT The number of bytes that are correctedthrough the FEC

Table C-10 Radio link error performance events


IF_BBE Radio link background block errors

IF_ES Radio link errored seconds

IF_SES Radio link severely errored seconds

IF_UAS Radio link unavailable second



635


IF_CSES Radio link consecutive severely erroredseconds

Table C-11 ATPC performance events


ATPC_P_ADJUST Positive ATPC adjustment

ATPC_N_ADJUST Negative ATPC adjustment

Table C-12 AM performance events


QPSKWS Working time of the QPSK mode

QAMWS16 Working time of the 16QAM mode





FB_AMDCNT Count of the downshift of the AM scheme

FB_AMUCNT Count of the upshift of the AM scheme

Table C-13 XPIC performance events


XPIC_XPD_VALUE XPIC XPD value

Table C-14 IF 1+1 protection group error performance events


PG_IF_BBE IF 1+1 protection group background blockerrors

PG_IF_ES IF 1+1 protection group errored seconds



636


PG_IF_SES IF 1+1 protection group severely erroredseconds

PG_IF_UAS IF 1+1 protection group unavailable second

PG_IF_CSES IF 1+1 protection group consecutive severelyerrored seconds

Table C-15 IF port error performance events


IF_SNR_MAX Maximum signal to noise ratio

IF_SNR_MIN Minimum signal to noise ratio

IF_SNR_AVG Average signal to noise ratio

C.1.3 Other Performance EventsIn addition to the SDH and radio performance events, the OptiX RTN 910 supports performanceevents of the optical power and the temperature.

Table C-16 Optical power performance events


TPLMAX Maximum value of transmit optical power

TPLMIN Minimum value of transmit optical power

TPLCUR Current value of transmit optical power

RPLMAX Maximum value of receive optical power

RPLMIN Minimum value of receive optical power

RPLCUR Current value of receive optical power

Table C-17 Board temperature performance events


BDTEMPMAX Maximum value of board temperature

BDTEMPMIN Minimum value of board temperature

BDTEMPCUR Current value of board temperature



637

Table C-18 Laser temperature performance events


OSPITMPMAX Maximum temperature of a laser core

OSPITMPMIN Minimum temperature of a laser core

OSPITMPCUR Current temperature of a laser core

C.2 Performance Events (by Logical Board)This part lists all the performance events that are reported by each board.

NOTE

The NE software consider a physical board as one or more logical boards when managing the physical board.The NMS also considers a physical board as one or more logical boards when managing the physical board.

For OptiX RTN 910, all physical boards, except the system control, switching, and timing board, correspond tological boards of the same names. Table C-19 shows the logical boards corresponding to the system control,switching, and timing board.

Table C-19 Logical boards corresponding to the system control, switching, and timing board

Physical Board Logical Board

CSTA CSTA in slot 1 + SL1D in slot 8 + SP3S inslot 9 + AUX in slot 10

CSHA CSHA in slot 1 + EM4T in slot 7 + SP3S inslot 9 + AUX in slot 10

CSHB CSHB in slot 1 + EM4T in slot 7 + SP3D inslot 9 + AUX in slot 10

CSHC CSHC in slot 1 + EM4F in slot 7 + SL1D inslot 8 + SP3S in slot 9 + AUX in slot 10

CSHD CSHD in slot 1 + EM6X in slot 7 + MP1 inslot 9 + AUX in slot 10

CSHE CSHE in slot 1 + EM6TB in slot 7 + MP1 inslot 9 + AUX in slot 10

C.2.1 CSTA/CSHA/CSHB/CSHC/CSHD/CSHE






638




Table C-21 IF 1+1 protection group error performance events


PG_IF_BBE IF 1+1 protection group background blockerrors

PG_IF_ES IF 1+1 protection group errored seconds

PG_IF_SES IF 1+1 protection group severely erroredseconds

PG_IF_UAS IF 1+1 protection group unavailable second

PG_IF_CSES IF 1+1 protection group consecutive severelyerrored seconds

C.2.2 IF1The IF1 board reports three types of performance events: SDH/PDH performance events,microwave performance events, and temperature performance events.

SDH/PDH Performance Events

Table C-22 Pointer justification performance events


AUPJCHIGH Count of positive AU pointer justification

AUPJCLOW Count of negative AU pointer justification

AUPJCNEW Count of new AU pointer justifications

Table C-23 Regenerator section error performance events


RSBBE Regenerator section block of backgrounderror

RSES Regenerator section errored second



639


RSSES Regenerator section severely errored second

RSUAS Regenerator section unavailable second

RSCSES Regenerator section consecutive severelyerrored second

RSOFS Regenerator section out-of-frame second

RSOOF Regenerator section out of frame

NOTE

The regenerator section error performance events also occur in the case of the PDH radio. The PDH radioframe is detected through the overheads that are used for frame location and bit error detection.

Table C-24 Multiplex section error performance events


MSBBE Multiplex section block of background error

MSES Multiplex section errored second

MSSES Multiplex section severely errored second

MSCSES Multiplex section consecutive severelyerrored second

MSUAS Multiplex section unavailable second

MSFEBBE Multiplex section far end block ofbackground error

MSFEES Multiplex section far end errored second

MSFESES Multiplex section far end severely erroredsecond

MSFECSES Multiplex section far end consecutiveseverely errored second

MSFEUAS Multiplex section far end unavailable second

Table C-25 Higher order path error performance events


HPBBE Higher order path background block error

HPES Higher order path errored second



640


HPSES Higher order path severely errored second

HPCSES Higher order path consecutive severelyerrored second

HPUAS Higher order path unavailable second

HPFEBBE Higher order path far end background blockerror

HPFEES Higher order path far end errored second

HPFESES Higher order path far end severely erroredsecond

HPFECSES Higher order path far end consecutiveseverely errored second

HPFEUAS Higher order path far end unavailable second

Radio Performance Events




FEC_COR_BYTE_CNT Frame count incorrect by FEC






Other Performance Events






641




C.2.3 IFU2/ISU2The IFU2/ISU2 board reports three types of performance events: PDH performance events, radioperformance events, and board temperature performance events.

SDH Performance Events (Only reported by ISU2)





















642












HPBBE Higher order path background errored block





HPFEBBE Higher order path far end background erroredblock







643

PDH Performance Events

Table C-33 Lower order path error performance events


LPBBE Lower order path block of background error

LPES Lower order path errored second

LPSES Lower order path severely errored second

LPCSES Lower order path continuous severe bit errorsecond

LPUAS Lower order path unavailable second

LPFEBBE Lower order path far end block of backgrounderror

LPFEES Lower order path far end errored second

LPFESES Lower order path far end severely erroredsecond

LPFECSES Lower order path far end consecutiveseverely errored second

LPFEUAS Lower order far end unavailable second














644


























645

C.2.4 IFX2/ISX2The IFX2/ISX2 board reports three types of performance events: PDH performance events,radio performance events, and board temperature performance events.

SDH Performance Events (Only reported by ISX2)
























646


























647
























648
















Table C-48 XPIC performance events


XPIC_XPD_VALUE XPIC XPD value









649

C.2.5 SL1D/SL1DAThe SL1D/SL1DA board reports three types of performance events: SDH performance events,and optical power performance events.

SDH Performance Events
























650


























651






C.2.6 EM6TThe EM6T board reports only the board temperature performance events.






C.2.7 EM6TAThe EM6TA board reports only the board temperature performance events.






C.2.8 EM6XThe EM6X board reports optical power performance events.

Table C-57 Optical Power Performance Events


TPLMAX Indicates the maximum transmit opticalpower at an optical interface.



652


TPLMIN Indicates the minimum transmit opticalpower at an optical interface.

TPLCUR Indicates the current transmit power at anoptical interface.

RPLMAX Indicates the maximum receive optical powerat an optical interface.

RPLMIN Indicates the minimum receive optical powerat an optical interface.

RPLCUR Indicates the current receive power at anoptical interface.

C.2.9 EM6FThe EM6F board reports optical power performance events and board temperature performanceevents.
















653

C.2.10 EM6FAThe EM6FA board reports optical power performance events and board temperatureperformance events.














C.2.11 EFP8The EFP8 board reports the temperature and PDH performance events.











654











C.2.12 EMS6The EMS6 board reports the SDH performance events, board temperature performance events,laser temperature performance events, and optical power performance events.














655

















Table C-67 Laser temperature performance events


OSPITMPMAX Maximum temperature of a laser core

OSPITMPMIN Minimum temperature of a laser core

OSPITMPCUR Current temperature of a laser core






656







C.2.13 SP3S/SP3DThe SP3S/SP3D board reports only the PDH performance events.



TUPJCHIGH Count of positive TU pointer justifications

TUPJCLOW Count of negative TU pointer justifications

TUPJCNEW Count of new TU pointer justifications















657

Table C-71 E1 Error Performance Events


E1_BBE Indicates the E1 background block error.

E1_ES Indicates the E1 errored second.

E1_SES Indicates the E1 severely errored second.

E1_CSES Indicates the E1 consecutive severely erroredsecond.

E1_UAS Indicates the E1 unavailable second.

C.2.14 MP1The MP1 board reports PDH performance events and SDH performance events.


Table C-72 Performance Events of Lower Order Path Bit Errors


LPBBE Indicates the lower order path backgroundblock error.

LPES Indicates the lower order path errored second.

LPSES Indicates the lower order path severelyerrored second.

LPCSES Indicates the lower order path consecutiveseverely errored second.

LPUAS Indicates the lower order path unavailablesecond.

LPFEBBE Indicates the lower order path far endbackground block error.

LPFEES Indicates the lower order path far end erroredsecond.

LPFESES Indicates the lower order path far endseverely errored second.

LPFECSES Indicates the lower order path far endconsecutive severely errored second.

LPFEUAS Indicates the lower order far end unavailablesecond.



658

Table C-73 Pointer Justification Performance Events


TUPJCHIGH Indicates the count of positive TU pointerjustifications.

TUPJCLOW Indicates the count of negative TU pointerjustifications.

TUPJCNEW Indicates the count of new TU pointerjustifications.

SDH Performance Events

Table C-74 E1 Performance Event List






C.2.15 ML1/MD1The ML1/MD1 board reports E1 performance events and board temperature performance events.

E1 Performance Events

Table C-75 E1 Performance Event List







659




Table C-76 Board Temperature Performance Events


BDTEMPMAX Indicates the maximum boardtemperature.

BDTEMPMIN Indicates the minimum boardtemperature.

BDTEMPCUR Indicates the current board temperature.

C.2.16 ODUThe ODU reports radio performance events and board temperature performance events.

Table C-77 Radio power performance events


TSL_MAX Maximum value of radio transmit signal level

TSL_MIN Minimum value of radio transmit signal level

TSL_CUR Current value of radio transmit signal level

TSL_AVG Average value of radio transmit signal level

RSL_MAX Maximum value of radio receive signal level

RSL_MIN Minimum value of radio receive signal level

RSL_CUR Current value of radio receive signal level

RSL_AVG Average value of radio receive signal level

TLHTT The duration when the ODU at the local endhas a transit power higher than the upperthreshold

TLLTT The duration when the ODU at the local endhas a transit power higher than the lowerthreshold



660


RLHTT The duration when the ODU at the local endhas a receive power lower than the upperthreshold

RLLTT The duration when the ODU at the local endhas a receive power lower than the lowerthreshold

Table C-78 ATPC performance events


ATPC_P_ADJUST Positive ATPC adjustment

ATPC_N_ADJUST Negative ATPC adjustment

Table C-79 Board Temperature Performance Events


BDTEMPMAX Indicates the maximum boardtemperature.

BDTEMPMIN Indicates the minimum boardtemperature.

BDTEMPCUR Indicates the current board temperature.

C.3 Performance Events and Handling ProceduresBased on the type of a performance event, this chapter describes all the performance events onthe OptiX RTN 910 and how to handle these performance events.

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



661

Attribute

Attribute Description

Performance event cell PPJE (AUPJCHIGH)NPJE (AUPJCLOW)NDF (AUPJCNEW)

Unit Block

Impact on System

Less than six AUPJCHIGH and AUPJCLOW events do not affect the system. If the pointer isjustified for many times, or the AUPJCNEW event occurs, bit errors may occur in the service.

Related Alarms

When the AUPJCHIGH, AUPJCLOW, or AUPJCNEW performance event crosses the presetthreshold, the MSAD_CROSSTR alarm is reported.

Performance Event Default 15-MinuteThreshold

Default 24-HourThreshold

AUPJCHIGH 1500 30000

AUPJCLOW 1500 30000

AUPJCNEW 1500 30000

Possible Causes

The NE clock is out-of-synchronization.

Procedure

Step 1 See 5.5 Troubleshooting Pointer Justifications for handling.

----End

C.3.2 TUPJCHIGH, TUPJCLOW, and TUPJCNEW

Descriptionl TUPJCHIGH indicates the count of positive TU pointer justifications.

l TUPJCLOW indicates the count of negative TU pointer justifications.

l TUPJCNEW indicates the count of new TU pointer justifications.



662

AttributeAttribute Description

Performance event cell TUPPJE (TUPJCHIGH)TUNPJE (TUPJCLOW)TUNDF (TUPJCNEW)

Unit Block

Impact on SystemLess than six TUPJCHIGH and TUPJCLOW events on each port do not affect the system. If thepointer is justified for many times, or the TUPJCNEW event occurs, bit errors may occur in theservice.

Related AlarmsWhen the TUPJCHIGH, TUPJCLOW, or TUPJCNEW performance event crosses the presetthreshold, the HPAD_CROSSTR alarm is reported.



TUPJCHIGH 1500 30000

TUPJCLOW 1500 30000

TUPJCNEW 1500 30000

Possible CausesThe NE clock is out-of-synchronization.

Procedure

Step 1 See 5.5 Troubleshooting Pointer Justifications for handling.

----End

C.3.3 RSBBE, RSES, RSSES, RSCSES, and RSUAS

Descriptionl RSBBE indicates the regenerator section background block error.

Background block error (BBE) refers to the errored blocks excluding the errored blocks inthe unavailable and severely errored seconds.

l RSES indicates the regenerator section errored second.Errored second (ES) refers to a second in which one or more errored blocks are detected.



663

l RSSES indicates the regenerator section severely errored second.Severely errored second (SES) refers to a second in which 30% or more than 30% erroredblocks exist or at least one severely disturbed period (SDP) exists. SDP is the period inwhich the BER of all the consecutive blocks in a period of less than four consecutive blocksor 1 ms (the longer period is applied) is equal to or higher than 10-2 or the signal is lost.

l RSCSES indicates the regenerator section consecutive severely errored second.Consecutive severely errored second (CSES) refers to a second in which the SES occurscontinuously for less than 10 seconds.

l RSUAS indicates the regenerator section unavailable second.The unavailable time begins at the onset of 10 consecutive SESs, with the 10 SESs included.When SESs disappear for 10 consecutive seconds, the available time begins from theeleventh second, with the previous 10 seconds included.

NOTE

When the IF board works in PDH mode, these performance events may also be reported. These events aredetected through the self-defined overhead byte B1 in the PDH radio frame.


Performance event cell B1CNT

Unit Block (RSBBE)Second (RSES, RSSES, RSCSES, andRSUAS)

Impact on System

Excessive bit errors interrupt the service (the BER should be less than 10-3 for the voice service,and 10-6 for the data service).

Related Alarms

When the RSBBE, RSES, RSSES, RSCSES, or RSUAS performance event crosses the presetthreshold, the RS_CROSSTR alarm is reported.



RSBBE 1500 15000

RSES 50 100

RSSES 20 50

RSUAS 20 50

RSCSES 4 (number of consecutive SESs)



664

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

Step 2 When an RSUAS performance event is reported, check whether cross-connections areconfigured and whether fibers are properly connected at service ports. If cross-connections arenot configured, configure cross-connections again according to planning information; if fibersare incorrectly connected, connect the fibers again according to planning information.

----End

C.3.4 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 System

The system discards OOF data blocks. Therefore, an RSOOF event is equivalent to a big error(if one RSOOF exists in a second, the BER is not less than 1.25 x 10-5).

Related Alarms

If RSOOF is received in five consecutive frames, the equipment changes to the OOF state. Ifthe OOF state lasts for 3 ms, the R_LOF alarm is reported and all the services are interrupted.

Possible Causes

The system detects incorrect A1 and A2 bytes.



665

Procedure

Step 1 If the R_LOF alarm, as well as the performance event, is reported, eliminate the errors accordingto the alarm. Otherwise, see 5.4 Troubleshooting Bit Errors in TDM Services for handling.

----End

C.3.5 MSBBE, MSES, MSSES, MSCSES, and MSUAS

Descriptionl MSBBE indicates the multiplex section background block error.

BBE refers to the errored blocks excluding the errored blocks in the unavailable andseverely errored seconds.

l MSES indicates the multiplex section errored second.ES refers to a second in which one or more errored blocks are detected.

l MSSES indicates the multiplex section severely errored second.SES refers to a second in which 15% or more than 15% errored blocks exist or at least oneSDP exists. SDP is the period in which the BER of all the consecutive blocks in a periodof less than four consecutive blocks or 1 ms (the longer period is applied) is equal to orhigher than 10-2 or the signal is lost.

l MSCSES indicates the multiplex section consecutive severely errored second.CSES refers to a second in which the SES occurs continuously for less than 10 seconds.

l MSUAS indicates the multiplex section unavailable second.The unavailable time begins at the onset of 10 consecutive SESs, with the 10 SESs included.When SESs disappear for 10 consecutive seconds, the available time begins from theeleventh second, with the previous 10 seconds included.

Attribute



Unit Block (MSBBE)Second (MSES, MSSES, MSCSES, andMSUAS)

Impact on System


Related Alarms

When the MSBBE, MSES, MSSES, MSCSES, or MSUAS performance event crosses the presetthreshold, the MS_CROSSTR alarm is reported.



666



MSBBE 1500 15000

MSES 50 100

MSES 20 50

MSUAS 20 50

MSCSES 4 (number of consecutive SESs)

Possible CausesThe system detects multiplex section bit errors through the B2 byte.

Procedure


Step 2 When an MSUAS performance event is reported, check whether cross-connections areconfigured and whether fibers are properly connected at service ports. If cross-connections arenot configured, configure cross-connections again according to planning information; if fibersare incorrectly connected, connect the fibers again according to planning information.

----End

C.3.6 MSFEBBE, MSFEES, MSFESES, MSFECSES, and MSFEUAS

Descriptionl MSFEBBE indicates the multiplex section far end background block error.

Far end background block error (FEBBE) indicates that the BBE occurs at the oppositeend.

l MSFEES indicates the multiplex section far end errored second.Far end errored second (FEES) indicates that the ES occurs at the opposite end.

l MSFESES indicates the multiplex section far end severely errored second.Far end severely errored second (FESES) indicates that the SES occurs at the opposite end.

l MSFECSES indicates the multiplex section far end consecutive severely errored second.Far end consecutive severely errored second (FECSES) indicates that the CSES occurs atthe opposite end.

l MSFEUAS indicates the multiplex section far end unavailable second.Far end unavailable second (FEUAS) indicates that the UAS occurs at the opposite end.



667

Attribute


Performance event cell LFEBE

Unit Block (MSFEBBE)Second (MSFEES, MSFESES, MSFECSES,and MSFEUAS)



Related Alarms

The MS_REI alarm is reported at the local end.

Possible Causes

The system detects multiplex section far end bit errors through the M1 byte.

Procedure

Step 1 Clear the corresponding performance event at the opposite end.

----End

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

ES refers to a second in which one or more errored blocks are detected.

l HPSES indicates the higher order path severely errored second.

SES refers to a second in which 30% or more than 30% errored blocks exist or at least oneSDP exists. SDP is the period in which the BER of all the consecutive blocks in a periodof less than four consecutive blocks or 1 ms (the longer period is applied) is equal to orhigher than 10-2 or the signal is lost.

l HPCSES indicates the higher order path consecutive severely errored second.

CSES refers to a second in which the SES occurs continuously for less than 10 seconds.

l HPUAS indicates the higher order path unavailable second.



668

The unavailable time begins at the onset of 10 consecutive SESs, with the 10 SESs included.When SESs disappear for 10 consecutive seconds, the available time begins from theeleventh second, with the previous 10 seconds included.



Unit Block (HPBBE)Second (HPES, HPSES, HPCSES, andHPUAS)

Impact on SystemExcessive bit errors interrupt the service (the BER should be less than 10-3 for the voice service,and 10-6 for the data service).

Related AlarmsWhen the HPBBE, HPES, HPSES, HPCSES, or HPUAS performance event crosses the presetthreshold, the HP_CROSSTR alarm is reported.



HPBBE 1500 15000

HPES 50 100

HPSES 20 50

HPUAS 20 50

HPCSES 4 (number of consecutive SESs)

Possible CausesThe system detects higher order path bit errors through the B3 byte.

Procedure


----End



669

C.3.8 HPFEBBE, HPFEES, HPFESES, HPFECSES, and HPFEUAS

Descriptionl HPFEBBE indicates the higher order path far end background block error.

Far end background block error (FEBBE) indicates that the BBE occurs at the oppositeend.

l HPFEES indicates the higher order path far end errored second.

FEES indicates that the ES occurs at the opposite end.

l HPFESES indicates the higher order path far end severely errored second.

FESES indicates that the SES occurs at the opposite end.

l HPFECSES indicates the higher order path far end consecutive severely errored second.

FECSES indicates that the CSES occurs at the opposite end.

l HPFEUAS indicates the higher order path far end unavailable second.

FEUAS indicates that the UAS occurs at the opposite end.

Attribute


Performance event cell PFEBE

Unit Block (HPFEBBE)Second (HPFEES, HPFESES, HPFECSES,and HPFEUAS)


Related Alarms

The HP_REI alarm is reported at the local end.

Possible Causes

The system detects the higher order path far end bit errors through bits 1 to 4 in the G1 byte.

Procedure

Step 1 Clear the corresponding performance event at the opposite end.

----End



670

C.3.9 IF_BBE, IF_ES, IF_SES, IF_CSES, and IF_UAS

Descriptionl IF_BBE indicates the radio link background block error.


l IF_ES indicates the radio link errored second.ES refers to a second in which one or more errored blocks are detected.

l IF_SES indicates the radio link severely errored second.SES refers to a second in which 30% or more than 30% errored blocks exist or at least oneSDP exists. SDP is the period in which the BER of all the consecutive blocks in a periodof less than four consecutive blocks or 1 ms (the longer period is applied) is equal to orhigher than 10-2 or the signal is lost.

l IF_CSES indicates the radio link consecutively severely errored second.CSES refers to a second in which the SES occurs continuously for less than 10 seconds.

l IF_UAS indicates the radio link unavailable second.The unavailable time begins at the onset of 10 consecutive SESs, with the 10 SESs included.When SESs disappear for 10 consecutive seconds, the available time begins from theeleventh second, with the previous 10 seconds included.


Performance event cell IF_BIP8

Unit -

Impact on System


Related AlarmsThe MW_BER_SD or MW_BER_EXC alarm is reported when the BER crosses the specificthreshold.

Possible CausesThe system detects bit errors on the radio link through the bit error detection overheads in a radioframe.

ProcedureStep 1 See 5.4 Troubleshooting Bit Errors in TDM Services for handling.

----End



671

C.3.10 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.ES refers to a second in which one or more errored blocks are detected.

l LPSES indicates the lower order path severely errored second.SES refers to a second in which 30% or more than 30% errored blocks exist or at least oneSDP exists. SDP is the period in which the BER of all the consecutive blocks in a periodof less than four consecutive blocks or 1 ms (the longer period is applied) is equal to orhigher than 10-2 or the signal is lost.

l LPCSES indicates the lower order path consecutive severely errored second.CSES refers to a second in which the SES occurs continuously for less than 10 seconds.

l LPUAS indicates the lower order path unavailable second.The unavailable time begins at the onset of 10 consecutive SESs, with the 10 SESs included.When SESs disappear for 10 consecutive seconds, the available time begins from theeleventh second, with the previous 10 seconds included.

Attribute


Performance event cell LPBIP2CNT

Unit Block (LPBBE)Second (LPES, LPSES, LPCSES, andLPUAS)

Impact on System


Related Alarms

When the LPBBE, LPES, LPSES, LPCSES, or LPUAS performance event crosses the presetthreshold, the LP_CROSSTR alarm is reported.



LPBBE 1500 15000

LPES 50 100



672



LPSES 20 50

LPUAS 20 50

LPCSES 4 (number of consecutive SESs)

Possible Causes

The system detects lower order path bit errors through the BIP2 in the V5 byte (E1 interfaceboard or Hybrid IF board).

Procedure


----End

C.3.11 LPFEBBE, LPFEES, LPFESES, LPFECSES, and LPFEUAS

Descriptionl LPFEBBE indicates the lower order path far end background block error.

FEBBE indicates that the BBE occurs at the opposite end.

l LPFEES indicates the lower order path far end errored second.

FEES indicates that the ES occurs at the opposite end.

l LPFESES indicates the lower order path far end severely errored second.

FESES indicates that the SES occurs at the opposite end.

l LPFECSES indicates the lower order path far end consecutive severely errored second.

FECSES indicates that the CSES occurs at the opposite end.

l LPFEUAS indicates the lower order path far end unavailable second.

FEUAS indicates that the UAS occurs at the opposite end.

Attribute


Performance event cell LPFEBE

Unit Block (LPFEBBE)Second (LPFEES, LPFESES, LPFECSES,and LPFEUAS)



673


Related AlarmsThe LP_REI alarm is reported at the local end.

Possible CausesThe system detects the lower order path far end bit errors through bit 3 in the V5 byte.

ProcedureStep 1 Clear the corresponding performance event at the opposite end.

----End

C.3.12 E1_LCV_SDH, E1_LLOSS_SDH, E1_LES_SDH, andE1_LSES_SDH

Descriptionl The E1_LCV_SDH is a performance event indicating the E1 line side code violation count.l The E1_LLOSS_SDH is a performance event indicating the E1 line side loss-of-signal

seconds.l The E1_LES_SDH is a performance event indicating the E1 line side code violation errored

second.ES refers to a second in which one or more errored blocks are detected.

l The E1_LSES_SDH is a performance event indicating the E1 line side code violationseverely 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 (taking the longer one) in which the BER of all theconsecutive blocks is equal to or higher than 10-2 or the signal is lost.


Performance event cell LCV_BPVCNT

Unit NoneSecond

Impact on the SystemIf bit errors occur in the services, you need to find out the causes and troubleshoot the problemin a timely manner. Otherwise, the signal transmission quality will be affected.



674

Related AlarmsNone.

Possible Causesl External causes:

– The fiber performance is degraded, and the fiber has extremely high attenuation.– The fiber connector is dirty or incorrect.– The equipment is improperly grounded.– A strong interference source is present near the equipment.– The working temperature is extremely high or extremely low, and the opposite

equipment cannot tolerate such temperature.l Equipment problems:

– The service code types are incorrect.– The board becomes faulty, or the performance of the board is degraded.

Procedure

Step 1 First eliminate external causes, such as poor grounding, too high operating temperature, too lowor too high the receiving optical power of the line board.

Step 2 Check whether the correct E1 service code is selected. If not, modify the code of the servicesreceived by a board by setting the code type of the board.

----End

C.3.13 TSL_MAX, TSL_MIN, TSL_CUR, and TSL_AVG

Descriptionl TSL_MAX indicates the maximum radio transmitted signal level.l TSL_MIN indicates the minimum radio transmitted signal level.l TSL_CUR indicates the current radio transmitted signal level.l TSL_AVG indicates the average radio transmitted signal level.


Performance event cell TSL

Unit 0.1dBm

Impact on SystemWhen the radio transmitted signal level is very low or very high, the radio received signal levelat the opposite site is very low or very high. As a result, bit errors occur and even services areinterrupted.



675

Related Alarms

If the radio transmitted signal level is not within the range supported by the ODU, theRADIO_TSL_HIGH or RADIO_TSL_LOW alarm is reported.

C.3.14 RSL_MAX, RSL_MIN, RSL_CUR, and RSL_AVG

Descriptionl RSL_MAX indicates the maximum radio received signal level.

l RSL_MIN indicates the minimum radio received signal level.

l RSL_CUR indicates the current radio received signal level.

l RSL_AVG indicates the average radio received signal level.

Attribute


Performance event cell RSL

Unit 0.1dBm

Impact on SystemWhen the radio received signal level is very low or very high, bit errors occur and even servicesare interrupted.

Related Alarms

If the radio received signal level crosses the specific threshold, the RADIO_RSL_HIGH orRADIO_RSL_LOW alarm is reported.

C.3.15 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_CNT indicates the number of frames that cannot be correctedthrough the FEC.

This event indicates the number of blocks that cannot be corrected through the FEC.



676


Performance event cell FECBEFCORER (FEC_BEF_COR_ER)FECCORBYTECNT(FEC_COR_BYTE_CNT)FECUNCORBLOCKCNT(FEC_UNCOR_BLOCK_CNT)

Unit None (FEC_BEF_COR_ER)None (FEC_COR_BYTE_CNT)Block (FEC_UNCOR_BLOCK_CNT)

Impact on SystemIf the value of FEC_BEF_COR_ER is very high, residual bit errors exist in the service after theFEC is performed.

If the value of FEC_UNCOR_BLOCK_CNT is not zero, it can be inferred that bit errors thatcannot be corrected exist on a radio link. Bit errors exist in the service accordingly.

Related AlarmsIf a byte cannot be corrected, the MW_FEC_UNCOR alarm is reported.

C.3.16 QPSKWS, QAMWS16, QAMWS32, QAMWS64,QAMWS128, and QAMWS256

Descriptionl QPSKWS indicates the working duration of the QPSK modulation scheme.l QAMWS16 indicates the working duration of the 16QAM modulation scheme.l QAMWS32 indicates the working duration of the 32QAM modulation scheme.l QAMWS64 indicates the working duration of the 64QAM modulation scheme.l QAMWS128 indicates the working duration of the 128QAM modulation scheme.l QAMWS256 indicates the working duration of the 256QAM modulation scheme.



677

Attribute


Performance event cell QPSKWSSECOND (QPSKWS)QAMWS16SECOND (16QAMWS)QAMWS32SECOND (32QAMWS)QAMWS64SECOND (64QAMWS)QAMWS128SECOND (128QAMWS)QAMWS256SECOND (256QAMWS)

Unit Second

Impact on System

When the AM function is disabled, the performance event does not affect the system.

When the AM function is enabled, in normal cases, the seconds of the modulation scheme formaximum capacity should account for a larger percentage. In the duration set for good weather,if the seconds of the low-efficiency modulation scheme account for a larger percentage, theperformance of the radio link is abnormal.

Related Alarms

None.

C.3.17 ATPC_P_ADJUST and ATPC_N_ADJUST

Descriptionl ATPC_P_ADJUST indicates the positive ATPC adjustment event.

This performance event indicates that the quality of a communication link declines.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.

Attribute


Performance event cell ATPCPADJUST (ATPC_P_ADJUST) andATPCNADJUST (ATPC_N_ADJUST)

Unit times



678

Impact on the SystemThe 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.

Related AlarmsNone.

C.3.18 FB_AMDCNT and FB_AMUCNT

Descriptionl FB_AMDCNT indicates the count of the AM downshifts on a board in the current

performance statistics period.l FB_AMUCNT indicates the count of the AM upshifts on a board in the current performance

statistics period.


Performance event cell ACMDCNT(FB_AMDCNT) andACMUCNT(FB_AMUCNT)

Unit times

Impact on Systeml When the value of the performance event is larger, more AM scheme are made.l When the factors that affect a communication link, such as sudden change of the weather,

do not exist, and when the AM scheme count is very large, the communication link maybe faulty. You must check the communication link to prevent it from failure.

Related AlarmsAM_DOWNSHIFT

Possible CausesWhen the AM function is enabled, the transmission modulation scheme that the IF port on theIF board uses varies according to the quality of the link. Accordingly, the system counts theperformance events of the modulation scheme shift. When the low-efficiency modulationscheme is shifted to the high-efficiency modulation scheme, an upshift is recorded and oneFB_AMUCNT event is counted. Similarly, when the high-efficiency modulation scheme isshifted to the low-efficiency modulation scheme, a downshift is recorded and one FB_AMDCNTevent is counted.



679

C.3.19 RLHTT, RLLTT, TLHTT, TLLTT

Descriptionl The RLHTT indicates the duration when the ODU at the local end has a receive power

lower than the upper threshold.

l The RLLTT indicates the duration when the ODU at the local end has a receive powerlower than the lower threshold.

l The TLHTT indicates the duration when the ODU at the local end has a transit power higherthan the upper threshold.

l The TLLTT indicates the duration when the ODU at the local end has a transit power higherthan the lower threshold.

Attribute


Performance event cell RLHTS(RLHTT), RLLTS(RLLTT), TLHTS(TLHTT), and TLLTS(TLLTT)

Unit Second

Impact on System

None.

Related Alarms

None.

C.3.20 TPLMAX, TPLMIN, and TPLCUR

Descriptionl TPLMAX indicates the maximum transmit optical power at an optical interface.

l TPLMIN indicates the minimum transmit optical power at an optical interface.

l TPLCUR indicates the current transmit optical power at an optical interface.

Attribute


Performance event cell OPM

Unit 0.1dBm



680

Impact on System

In normal cases, the receive optical power should be 3 dB higher than the receiver sensitivity,and 5 dB lower than the overload power.

If the transmit optical power is very low or very high, the receive optical power at the oppositesite is accordingly very low or very high. As a result, bit errors occur and even services areinterrupted.

Related Alarmsl If the transmit optical power at the opposite site is lower than the receiver sensitivity, the

IN_PWR_LOW alarm is reported.

l If the receive optical power at the opposite site is higher than the overload power, theIN_PWR_HIGH alarm is reported.

C.3.21 RPLMAX, RPLMIN, and RPLCUR

Descriptionl RPLMAX indicates the maximum receive optical power at an optical interface.

l RPLMIN indicates the minimum receive optical power at an optical interface.

l RPLCUR indicates the current receive optical power at an optical interface.

Attribute


Performance event cell IPM

Unit 0.1dBm

Impact on System

In normal cases, the receive optical power should be 3 dB higher than the receiver sensitivity,and 5 dB lower than the overload power.

If the receive optical power is very low or very high, bit errors occur and even services areinterrupted.

Related Alarmsl If the transmit 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.3.22 BDTEMPMAX, BDTEMPMIN, and BDTEMPCUR



681

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.


Performance event cell XCS_TEMP

Unit 0.1°C

Impact on SystemIf the temperature of a board is very high or very low, the performance of the board declines,and bit errors or other faults occur.

Related AlarmsIf the temperature of a board crosses the specific threshold, the TEMP_ALARM alarm isreported.

C.3.23 XPIC_XPD_VALUE

DescriptionThe XPIC_XPD_VALUE indicates the XPD value after the XPIC function is enabled.


Performance event cell XPD

Unit dB

Impact on Systeml When the XPIC function is disabled, the performance event does not affect the system.l When the XPIC function is enabled, a greater XPD value indicates less interference between

H and V polarization directions and better signaling environment; a smaller XPD valueindicates more interference and worse signaling environment. If the XPD value is smallerthan a specific threshold, errors and even interruptions occur on the radio link.

Related AlarmsNone.



682

C.3.24 PG_IF_BBE, PG_IF_ES, PG_IF_SES, PG_IF_CSES, andPG_IF_UAS

Descriptionl PG_IF_BBE indicates the protection group background block error.

Background block error (BBE) refers to the errored blocks excluding the errored blocks inthe unavailable and severely errored seconds.

l PG_IF_ES indicates the protection group errored second.Errored second (ES) refers to a second in which one or more errored blocks are detected.

l PG_IF_SES indicates the protection group severely errored second.Severely errored second (SES) refers to a second in which 30% or more than 30% erroredblocks exist or at least one severely disturbed period (SDP) exists. SDP is the period inwhich the BER of all the consecutive blocks in a period of less than four consecutive blocksor 1 ms (the longer period is applied) is equal to or higher than 10-2 or the signal is lost.

l PG_IF_CSES indicates the protection group consecutive severely errored second.Consecutive severely errored second (CSES) refers to a second in which the SES occurscontinuously for less than 10 seconds.

l PG_IF_UAS indicates the protection group unavailable second.The unavailable time begins at the onset of 10 consecutive SESs, with the 10 SESs included.When SESs disappear for 10 consecutive seconds, the available time begins from theeleventh second, with the previous 10 seconds included.

Attribute


Performance event cell IF_BIP8

Unit Block (PG_IF_BBE)Second (PG_IF_ES, PG_IF_SES,PG_IF_CSES, and PG_IF_UAS)

Impact on System

Excessive bit errors interrupt the service (the BER should be less than -3 for the voice service,and 10-6 for the data service).

Related Alarms

None.



PG_IF_BBE 1500 15000



683



PG_IF_ES 50 100

PG_IF_SES 20 50

PG_IF_UAS 20 50

PG_IF_CSES 4 (number of consecutive SESs)

Possible Causes

The system detects the protection group bit errors.

Related Alarms

PG_LINK_FAIL, PG_PRT_DEGRADED

Procedure

Step 1 See PG_LINK_FAIL, PG_PRT_DEGRADED.

----End

C.3.25 E1_BBE, E1_ES, E1_SES, E1_CSES, and E1_UAS

Descriptionl E1_BBE indicates the E1 background block error.

Background block error (BBE) refers to the errored blocks excluding the errored blocks inthe unavailable and severely errored seconds. This performance event can be detected onlywhen the E1 frame format is CRC-4.

l E1_ES indicates the E1 errored second.

Errored second (ES) refers to a second in which one or more errored blocks are detected.

l E1_SES indicates the E1 severely errored second.

Severely errored second (SES) refers to a second in which 30% or more than 30% erroredblocks exist or at least one severely disturbed period (SDP) exists. SDP is the period inwhich the BER of all the consecutive blocks in a period of less than four consecutive blocksor 1 ms (the longer period is applied) is equal to or higher than 10-2 or the signal is lost.

l E1_CSES indicates the E1 consecutive severely errored second.

Consecutive severely errored second (CSES) refers to a second in which the SES occurscontinuously for less than 10 seconds.

l E1_UAS indicates the E1 unavailable second.

The unavailable time begins at the onset of 10 consecutive SESs, with the 10 SESs included.When SESs disappear for 10 consecutive seconds, the available time begins from theeleventh second, with the previous 10 seconds included.



684


Performance event cell E1CRC_ERR_CNT

Unit Block (E1_BBE)Second (E1_ES, E1_SES, E1_CSES, andE1_UAS)

Impact on System

Excessive bit errors interrupt the service (the BER should be less than -3 for the voice service,and 10-6 for the data service).

Related AlarmsNone.



E1_BBE 1500 15000

E1_ES 50 100

E1_SES 20 50

E1_UAS 20 50

E1_CSES 4 (number of consecutive SESs)

Possible CausesThe system detects the E1 bit errors.

Procedure

Step 1 Check whether the frame format of the local E1 port is the same as that of the opposite port.

Step 2 Check whether the E1 cable is intact. If it is damaged, replace it.

Step 3 Use another E1 port.

Step 4 Troubleshoot the interconnected equipment.

----End



685

C.3.26 IF_SNR_MAX, IF_SNR_MIN, and IF_SNR_AVG

Descriptionl IF_SNR_MAX indicates the maximum signal to noise ratio.l IF_SNR_MIN indicates the minimum signal to noise ratio.l IF_SNR_AVG indicates the average signal to noise ratio.

Attribute


Performance event cell IF_SNR(IF_SNR_MAX, IF_SNR_MIN)IF_SNR_AVG_15M, andIF_SNR_AVG_24H(IF_SNR_AVG)

Unit dB

Impact on System

A greater SNR value indicates a steady radio link; a smaller SNR value indicates a worse radiolink, errors and even interruptions occur on the radio link.

Related Alarms

None.

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

Attribute


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.



686

Relevant AlarmsNone.



687

D RMON Event Reference

RMON events reflect the running of the Ethernet services. This chapter describes the possibleRMON events on the OptiX RTN 910 and how to handle these events.

D.1 List of RMON Alarm EntriesThe RMON alarm entries refer to the table entries in the RMON alarm group.

D.2 List of RMON Performance Entries on the Packet-PlaneThe RMON performance entries on the packet plane refer to the table entries in the RMONstatistics group or history group.

D.3 List of RMON Performance Entries on the EoS/EoPDH PlaneThe ports that report RMON performance events on the EoPDH plane include PORT1 to PORT9,and VCTRUNK1 to VCTRUNK16 on the EFP8 board. The ports that report RMONperformance events on the EoPDH plane include PORT1 to PORT8, and VCTRUNK1 toVCTRUNK8 on the EMS6 board.

D.4 RMON Events and Handling ProceduresThis chapter describes the RMON events that indicate Ethernet service abnormalities and howto handle these events.

OptiX RTN 910 Radio Transmission SystemMaintenance Guide (U2000) D RMON Event Reference


688

D.1 List of RMON Alarm EntriesThe RMON alarm entries refer to the table entries in the RMON alarm group.

Table D-1 List of RMON alarm entries

AlarmName

Description Source

ETHDROP The number of packet loss eventscrosses the threshold.

ISU2, ISX2, IFU2 and IFX2

RXBBAD The number of bytes in received badpackets crosses the threshold.

ETHFCS The number of frames that have FCScheck errors crosses the threshold.

Table D-2 List of RMON alarm entries

Alarm Name Description Source


EM4F, EM4T, EM6X, EM6TB,EM6T, EM6F, EM6FA, EM6TA

ETHEXCCOL

The number of frames that fail to betransmitted after continuouscollisions crosses the threshold.

ETHLATECOL

The number of collisions that aredetected after a timeslot periodelapses crosses the threshold.


TXDEFFRM The number of frames whosetransmission is delayed crosses thethreshold.

ETHUNDER The number of received undersizedpackets crosses the threshold.

ETHOVER The number of received oversizedpackets crosses the threshold.

ETHFRG The number of received fragmentedpackets crosses the threshold.

ETHJAB The number of received erroredoversized packets crosses thethreshold.



689



PORT_RX_BW_UTILIZATION

Indicates the bandwidth utilizationat a port in the receive direction.

ISU2, ISX2, EM4F, EM4T, EM6X,EM6TB, EM6X, EM6T, EM6F,EM6FA, EM6TA, IFU2 and IFX2

PORT_TX_BW_UTILIZATION

Indicates the bandwidth utilizationat a port in the transmit direction.

Table D-3 List of EMS6\EFP8 RMON alarm entries



EMS6, EFP8


ETHUNDER The number of received undersizedpackets crosses the threshold.

ETHOVER The number of received oversizedpackets crosses the threshold.

ETHFRG The number of received fragmentedpackets crosses the threshold.

ETHJAB The number of received erroredoversized packets crosses thethreshold.


ETHALI The number of alignment errorframes

D.2 List of RMON Performance Entries on the Packet-PlaneThe RMON performance entries on the packet plane refer to the table entries in the RMONstatistics group or history group.



690

Table D-4 Packet-Plane RMON Performance Entry List

PerformanceType

Performance Name Description Source

Basicperformance

RXPKTS Indicates the packetsreceived (packets).

EM4T, EM4F, EM6X,EM6TB, EM6T, EM6F,EFP8, IFU2, IFX2, ISU2,ISX2, EM6FA, EM6TA,EMS6

ETHDROP Indicates the packet lossevents (times).

RXOCTETS Indicates the bytesreceived (bytes).

RXMULCAST Indicates the multicastpackets received(packets).

RXBRDCAST Indicates the broadcastpackets received(packets).

ETHOVER Indicates the oversizedpackets received(packets).

EM4T, EM4F, EM6X,EM6TB, EM6T, EM6F,EFP8, EM6FA, EM6TA,EMS6

ETHJAB Indicates the oversizederror packets received(packets).

ETHUNDER Indicates the undersizedpackets received(packets).

EM4T, EM4F, EM6X,EM6TB, EM6T, EM6F,EM6FA, EM6TA

ETHFRG Indicates the fragmentsreceived (packets).

ETHCOL Indicates the collisions(times).

PORT_RX_BW_UTI-LIZATION

Indicates the bandwidthutilization at a port in thereceive direction.

PORT_TX_BW_UTI-LIZATION

Indicates the bandwidthutilization at a port in thetransmit direction.

Extendedperformance

ETHFCS Indicates the FCS erroredframes (frames).

EM4T, EM4F, EM6X,EM6TB, EM6T, EM6F,EFP8, IFU2, IFX2, ISU2,ISX2, EM6FA, EM6TA,EMS6

RXBGOOD Indicates the bytes inreceived good packets(bytes).



691

PerformanceType


TXBGOOD Indicates the bytes intransmitted good packets(bytes).

RXBBAD Indicates the bytes inreceived bad packets(bytes).

TXUNICAST Indicates the unicastpackets transmitted(packets).

RXUNICAST Indicates the unicastpackets received(packets).

TXMULCAST Indicates the multicastpackets transmitted(packets).

TXBRDCAST Indicates the broadcastpackets transmitted(packets).

RXGOODFULLFRAMESPEED

Indicates the rate of goodfull-frame bytes received(bytes/second).

TXGOODFULLFRAMESPEED

Indicates the rate of goodfull-frame bytestransmitted (bytes/second).

RXFULLBGOOD Indicates the good full-frame bytes received(bytes).

TXFULLBGOOD Indicates the good full-frame bytes transmitted(bytes).

RXPAUSE Indicates the pauseframes received (frames).

EM4T, EM4F, EM6X,EM6TB, EM6T, EM6F,EFP8, EM6FA, EM6TA,EMS6TXPAUSE Indicates the pause

frames transmitted(frames).

ETHLATECOL Indicates the latecollisions (times).

EM4T, EM4F, EM6X,EM6TB, EM6T, EM6F,EM6FA, EM6TA



692

PerformanceType


ETHEXCCOL Indicates the framesunsuccessfullytransmitted afterconsecutive collisions(frames).

TXDEFFRM Indicates the frames thatare deferred intransmission (frames).

RXPKT64 Indicates the count ofreceived 64-byte packets(errored packetsincluded)

ISU2, ISX2

RXPKT65 Indicates the count ofreceived packets with alength of 65 to 127 bytes(errored packetsincluded)



RXPKT512 Indicates the count ofreceived packets with alength of 512 to 1023bytes (errored packetsincluded)

RXPKT1024 Indicates the count ofreceived packets with alength of 1024 to 1518bytes (errored packetsincluded)

RXPKT1519 Indicates the count ofreceived packets with alength of 1519 to MTUbytes (errored packetsincluded)



693

PerformanceType


TXPKT64 Indicates the count oftransmitted 64-bytepackets (errored packetsincluded)

TXPKT65 Indicates the count oftransmitted packets with alength of 65 to 127 bytes(errored packetsincluded)



TXPKT512 Indicates the count oftransmitted packets with alength of 512 to 1023bytes (errored packetsincluded)

TXPKT1024 Indicates the count oftransmitted packets with alength of 1024 to 1518bytes (errored packetsincluded)

TXPKT1519 Indicates the count oftransmitted packets with alength of 1519 to MTUbytes (errored packetsincluded)

ATMPWE3performance

ATMPW_SNDCELLS Indicates the count oftransmitted cells.

ML1, MD1, MP1

ATMPW_RCVCELLS Indicates the count ofreceived cells.

ATMPW_UNKNOWN-CELLS

Indicates the count ofunknown cells.



694

PerformanceType


ATM/IMAperformanceeventson theaccessside


Indicates the bandwidthutilization at a port in thereceive direction.


Indicates the bandwidthutilization at a port in thetransmit direction.

ATM_CORRECTED_HCSERR

Indicates the number ofcorrectable HCS errorcells received.

ATM_UNCORRECTED_HCSERR

Indicates the number ofuncorrectable HCS errorcells received.

ATM_RCVCELLS Indicates the total numberof received cells.

ATM_RCVIDLECELLS Indicates the total numberof received idle cells.

ATM_SNDCELLS Indicates the total numberof transmitted cells.

ATM_IF_INRATE_MAX

Indicates the maximumrate of normal cellsreceived on the port.

ATM_IF_INRATE_MIN Indicates the minimumrate of normal cellsreceived on the port.

ATM_IF_INRATE_AVG

Indicates the average rateof normal cells receivedon the port.

ATM_IF_OUTRATE_MAX

Indicates the maximumrate of normal cellstransmitted on the port.

ATM_IF_OUTRATE_MIN

Indicates the minimumrate of normal cellstransmitted on the port.

ATM_IF_OUTRATE_AVG

Indicates the average rateof normal cellstransmitted on the port.

ATM_CELL_AVAILA-BILITY

Indicates the percentageof valid cells.



695

PerformanceType



Indicates the bandwidthutilization rate (0.01%) ofthe port in the receivedirection.


Indicates the bandwidthutilization rate (0.01%) ofthe port in the transmitdirection.

ATM_UNI1_INRATE_MAX

Indicates the maximumrate of receiving correctcells on the UNI1 side ofATM connections.

ATM_UNI1_INRATE_MIN

Indicates the minimumrate of receiving correctcells on the UNI1 side ofATM connections.

ATM_UNI1_INRATE_AVG

Indicates the average rateof receiving correct cellson the UNI1 side of ATMconnections.

ATM_UNI1_OUTRATE_MAX

Indicates the maximumrate of transmittingcorrect cells on the UNI1side of ATM connections.

ATM_UNI1_OUTRATE_MIN

Indicates the minimumrate of transmittingcorrect cells on the UNI1side of ATM connections.

ATM_UNI1_OUTRATE_AVG

Indicates the average rateof transmitting correctcells on the UNI1 side ofATM connections.

ATM_UNI2_INRATE_MAX

Indicates the maximumrate of receiving correctcells on the UNI2 side ofATM connections.

ATM_UNI2_INRATE_MIN

Indicates the minimumrate of receiving correctcells on the UNI2 side ofATM connections.



696

PerformanceType


ATM_UNI2_INRATE_AVG

Indicates the average rateof receiving correct cellson the UNI2 side of ATMconnections.

ATM_UNI2_OUTRATE_MAX

Indicates the maximumrate of transmittingcorrect cells on the UNI2side of ATM connections.

ATM_UNI2_OUTRATE_MIN

Indicates the minimumrate of transmittingcorrect cells on the UNI2side of ATM connections.

ATM_UNI2_OUTRATE_AVG

Indicates the average rateof transmitting correctcells on the UNI2 side ofATM connections.

ATM_UNI1_INCELLS Indicates the total numberof receiving correct cellson the UNI1 side of ATMconnections.

ATM_UNI1_OUT-CELLS

Indicates the total numberof transmitting correctcells on the UNI1 side ofATM connections.

ATM_UNI2_INCELLS Indicates the total numberof receiving correct cellson the UNI2 side of ATMconnections.

ATM_UNI2_OUT-CELLS

Indicates the total numberof transmitting correctcells on the UNI2 side ofATM connections.

CESperformanceevent

CES_MISORDERPKTS Indicates the number oflost disordered packets.

CES_STRAYPKTS Indicates the number ofmis-connected packets.

CES_MALPKTS Indicates the number ofdeformed frames.

CES_JTRUDR Indicates the number ofjitter buffer underflows.



697

PerformanceType


CES_JTROVR Indicates the number ofjitter buffer overflows.

CES_LOSPKTS Indicates the number oflost packets.

CES_RX_PKTS Indicates the number ofreceived packets.

PWperformanceofATM/CES

PW_RCVPKTS Indicates the number ofpackets received fromPWs.

PW_RCVBYTES Indicates the number ofbytes received from PWs.

L2VPNa

performance

VLAN_RCVPKTS Indicates the number ofpackets received at the V-UNI VLAN.

CSHA, CSHB, CSHC,CSHD, CSHE

VLAN_RCVBYTES Indicates the number ofbytes in the packetsreceived at the V-UNIVLAN.

VUNI_RCVPKTS Indicates the number ofpackets received on theV-UNI.

VUNI_RCVBYTES Indicates the number ofbytes received on the V-UNI.

Tunnelperformance

TUNNEL_REVERSE_RCVPKTS

Indicates the number ofpackets received in thereverse tunnel.

TUNNEL_REVERSE_RCVBYTES

Indicates the number ofbytes received in thereverse tunnel.

TUNNEL_RCVPKTS Indicates the number ofpackets received in thetunnel.

TUNNEL_RCVBYTES Indicates the number ofbytes received in thetunnel.



698

PerformanceType


PWperformanceofL2VPN

PW_RCVPKTS Indicates the number ofpackets received on thePW.

PW_RCVBYTES Indicates the number ofbytes received on the PW.

PW_DROPPKTS Indicates the number ofpackets discarded on thePW.

ETHOAM802.1ag

ETH_CFM_FLR Indicates the E_Lineservice packet loss ratio.

ETH_CFM_FL Indicates the number ofdiscarded E_Line servicepackets.

ETH_CFM_FD Indicates the E_Lineservice delay.

ETH_CFM_FDV Indicates the E_Lineservice delay variation.

Porttrafficclassification

QOS_PORTCAR_Mar-kedRedPKTS

Indicates the number ofred packets after trafficmonitoring is enabled.

EM4T, EM4F, EM6X,EM6TB, EM6T, EM6F,IFU2, IFX2, ISU2, ISX2,EM6FA, EM6TA

QOS_PORTCAR_Mar-kedYellowPKTS

Indicates the number ofyellow packets aftertraffic monitoring isenabled.

QOS_PORTCAR_Mar-kedGreenPKTS

Indicates the number ofgreen packets after trafficmonitoring is enabled.

QOS_PORTSTRM_RCVMATCHPKTS

Indicates the number ofpackets received in thematched flow.

QOS_PORTSTRM_SNDMATCHPKTS

Indicates the number ofpackets transmitted in thematched flow.

PORTSTRM_SHAPING_DROPPKTS

Indicates the number ofpackets discarded due tonetwork congestion whenthe traffic shapingfunction is enabled in theegress direction.



699

PerformanceType


PORTSTRM_SHAPING_DROPRATIO

Indicates the ratio ofpacket loss due tonetwork congestion whenthe traffic shapingfunction is enabled in theegress direction.

QOS_PORTCAR_Mar-kedRedRATIO

Indicates the proportionof packets marked in redwhen the traffic policingfunction is enabled.

Portpriority

QOS_PORTQUEUE_DROPRATIO

Indicates the ratio ofpacket loss due tocongestion in egressqueues with differentpriorities.

QOS_PRI_DROPPKTS Indicates the number ofpackets discarded in theservices with differentpriorities.

QOS_PRI_DROP-BYTES

Indicates the number ofbytes discarded in theservices with differentpriorities.

PORT_PRI_SNDPKTS Indicates the number ofpackets transmitted inegress queues withdifferent priorities.

PORT_PRI_SNDBYTES

Indicates the number ofbytes in the packetstransmitted in egressqueues with differentpriorities.

PortDSdomain

DS_CVLANPRI_PKTS Indicates the number ofpackets with matched C-VLAN priorities in theDS domain

DS_CVLANPRI_BYTES

Indicates the number ofbytes in the packets withmatched C-VLANpriorities in the DSdomain.



700

PerformanceType


DS_SVLANPRI_PKTS Indicates the number ofpackets with matched S-VLAN priorities in theDS domain.

DS_SVLANPRI_BYTES

Indicates the number ofbytes in the packets withmatched S-VLANpriorities in the DSdomain.

DS_DSCP_PKTS Indicates the number ofpackets with matched IPDSCP priorities in the DSdomain.

DS_DSCP_BYTES Indicates the number ofbytes in the packets withmatched IP DSCPpriorities in the DSdomain.

NOTE

l a: L2VPN services include a variety of E-Line and E-LAN services supported by the equipment.

l VUNI represents virtual UNI, represents the sink or source of services on the UNI side.

l The E-LAN services transmitted by the OptiX RTN 910 do not support the VUNI-based RMON performancestatistics.

l Integrated IP radio ports support this parameter.

D.3 List of RMON Performance Entries on the EoS/EoPDHPlane

The ports that report RMON performance events on the EoPDH plane include PORT1 to PORT9,and VCTRUNK1 to VCTRUNK16 on the EFP8 board. The ports that report RMONperformance events on the EoPDH plane include PORT1 to PORT8, and VCTRUNK1 toVCTRUNK8 on the EMS6 board.



701

Table D-5 List of RMON performance entries on the EoS/EoPDH plane

Category ofPerformanceEntries

Brief Name of aPerformance Entry

Full Name of aPerformance Entry

Source Port

Basicperformance

ETHUNDER Undersized packetsreceived (packets)

PORT1 to PORT8 on theEFP8 boardPORT1 to PORT6 on theEMS6 boardETHFRG Fragments received

(packets)

RXPKT64 Packets received (64bytes in length) (packets)

PORT1 to PORT9 on theEFP8 boardPORT1 to PORT7 on theEMS6 boardRXPKT65 Packets received (65-127

bytes in length) (packets)

RXPKT128 Packets received(128-255 bytes in length)(packets)

RXPKT256 Packets received(256-511 bytes in length)(packets)

RXPKT512 Packets received(512-1023 bytes inlength) (packets)

RXPKT1024 Packets received(1024-1518 bytes inlength) (packets)

Extendedperformance

RXCTLPKTS Control frames received(frames)

PORT1 to PORT9 on theEFP8 boardPORT1 to PORT7 on theEMS6 boardTXOCTETS Bytes transmitted (bytes)

TXPKTS Packets transmitted(packets)

TXCTLPKTS Control framestransmitted (frame)

TXPKT64 Packets transmitted (64bytes in length) (packets)

TXPKT65 Packets transmitted(65-127 bytes in length)(packets)



702




Source Port



TXPKT512 Packets transmitted(512-1023 bytes inlength) (packets)

TXPKT1024 Packets transmitted(1024-1518 bytes inlength) (packets)

ETHALI Alignment error frames(frames)

PKT64 Packets received andtransmitted (64 bytes inlength) (packets)

PKT65 Packets received andtransmitted (65-127 bytesin length) (packets)

PKT128 Packets received andtransmitted (128-255bytes in length) (packets)




VCGperformance

VCG_TXGOODPACK-ETS

Good packets transmitted(packets)

VCTRUNK1 toVCTRUNK16 on theEFP8 board

VCG_TXPACKETS Packets transmitted(packets)



703




Source Port

VCG_TXOCTETS VCTRUNK1 toVCTRUNK8 on theEMS6 board

Bytes transmitted (bytes)

VCG_RXGOODPACK-ETS

Good packets received(packets)

VCG_RXPACKETS Packets received(packets)

VCG_RXOCTETS Bytes received (bytes)

VCG_TXSPEED Speed of bytestransmitted (bytes)

VCG_RXSPEED Speed of bytes received(bytes)

D.4 RMON Events and Handling ProceduresThis chapter describes the RMON events that indicate Ethernet service abnormalities and howto handle these events.

D.4.1 ETHDROP

DescriptionETHDROP indicates the number of events in which packet loss occurs due to resource deficiencyof Ethernet chips. An RMON threshold-crossing event is reported when the number of packetloss events is higher than the upper threshold or lower than the lower threshold.

NOTE

ETHDROP counts only the packets that are lost due to resource deficiency of Ethernet chips.

Impact on SystemWhen packet loss occurs frequently, services are affected and the system is affected seriously.Hence, you must rectify the fault immediately.

Possible CausesThis performance event indicates packet loss due to the full MAC buffer, FIFO overflow, orbackward pressure.

l The lower threshold is not set to a non-zero value.



704

l The hardware at the local end is faulty.

Procedure

Step 1 Handle this alarm according to the specific performance event.

If... Then...

The number is lower than the lowerthreshold

Change the lower threshold to 0.

The number is higher than the upperthreshold

Manually decrease the traffic transmitted fromthe opposite end. If the problem persists, go tothe next step.

Step 2 Replace the involved part.

----End

Reference

None.

D.4.2 ETHEXCCOL

Description

ETHEXCCOL indicates the number of frames that fail to be transmitted due to continuous portcollisions. An RMON threshold-crossing event is reported when the number of frames that failto be transmitted is higher than the upper threshold or lower than the lower threshold. Generally,the value indicates that 16 port collisions occur continuously when the same frame is transmitted.

Impact on System

The opposite equipment fails to normally receive services.

Possible Causes

Generally, this event is caused when the local port is connected to a large number of devicesthat work in half-duplex mode.

Procedure


If... Then...

The number is lower than the lower threshold Change the lower threshold to 0.

The number is higher than the upper threshold Go to the next step.

Step 2 On the NMS, query the working modes of the ports on the equipment at both ends.



705

If... Then...

The ports on the equipment at both endswork in inconsistent modes, or any portworks in half-duplex mode

Set the working modes of the ports on theequipment at both ends to full-duplex or auto-negotiation, so that these ports work inconsistent modes.

The ports on the equipment at both endswork in consistent modes and no ports workin half-duplex mode



----End

Reference

None.

D.4.3 ETHLATECOL

Description

ETHLATECOL indicates the number of collisions detected within a timeslot period after apacket is transmitted. An RMON threshold-crossing event is reported when the number ofcollisions is higher than the upper threshold or lower than the lower threshold.

Impact on System

The opposite equipment fails to normally receive services.

Possible Causes

Generally, this performance event is caused by a large network diameter.

Procedure


If... Then...




If... Then...





706

If... Then...



Step 3 Check whether the network diameter of the LAN is very large according to the networkingplanning information.

If... Then...

The network diameter is very large Divide the network and deploy equipment todifferent buses or physically shared devices (such ashubs).NOTE

In the case of the 10 Mbit/s port rate, the maximum Ethernetdiameter is 2000 m. In the case of the 100 Mbit/s port rate,the maximum Ethernet diameter is 200 m.

The network diameter is appropriate Go to the next step.


----End

Reference

None.

D.4.4 RXBBAD

Description

RXBBAD indicates the total number of bytes in received bad packets, excluding the framingbit but including the FCS byte. An RMON threshold-crossing event is reported when the totalnumber of bytes in received bad packets is higher than the upper threshold or lower than thelower threshold.

Impact on System

A port discards bad packets. This may even interrupt system services.

Possible Causes1. Errors occur when the opposite end transmits packets.

2. The transmission line is of the poor quality and bit errors exist.

3. The hardware at the local end is faulty.

Procedure




707

If... Then...



Step 2 Correct the errors that occur when the opposite end transmits packets.

Step 3 Handle the problem of poor quality of the transmission line.Check whether the ETH_LOS alarm is reported at the local end because the external line isdamaged or over attenuated. If yes, see the related handling method to clear the alarm.


----End

Reference

None.

D.4.5 TXDEFFRM

Description

TXDEFFRM indicates the number of frames the first transmission of which is delayed due tothe congestion on the transmission media, excluding the number of frames the first transmissionof which is delayed due to collisions. An RMON threshold-crossing event is reported when thenumber of frames that fail to be transmitted is higher than the upper threshold and lower thanthe lower threshold.

Impact on System

The rate of frame transmission decreases, and therefore packets are congested at a port and thethroughput of the port decreases.

Possible Causes

Generally, this event is caused when the external port at the local end is connected to a largenumber of devices that work in half-duplex mode.

Procedure


If... Then...






708

If... Then...






----End

ReferenceNone.

D.4.6 ETHUNDER

DescriptionETHUNDER indicates that an RMON threshold-crossing event is reported when the number ofpackets that are shorter than 64 bytes and are received on the line side crosses the preset threshold.

Impact on SystemThe data frames whose length is not within the specific range are discarded. As a result, thesystem services are affected.

Possible Causes1. The length of a data frame that is received at a port is shorter than 64 bytes.2. The hardware at the local end is faulty.

Procedure

Step 1 Check whether the opposite equipment transmits the packet that is shorter than 64 bytes.

If... Then...

The opposite equipment transmits the packetthat is shorter than 64 bytes

Rectify the fault on the opposite equipment.

The opposite end does not transmit thepacket that is shorter than 64 bytes



----End

ReferenceNone.



709

D.4.7 ETHOVER

DescriptionETHOVER indicates that an RMON threshold-crossing event is reported when the number ofpackets that are longer than 1518 bytes and are received at a port crosses the preset threshold.

Impact on SystemIf the length of the data frame received at a port is more than the preset maximum frame length,the data frame is discarded and therefore the system services are affected.

Possible Causes1. The preset maximum frame length is less than the length of the frame that is received at a

port.2. The hardware at the local end is faulty.

Procedure

Step 1 Check whether the opposite equipment transmits the packet that is longer than the maximumframe length set for the local equipment.

If... Then...

The opposite equipment transmits thepacket that is longer than the maximumframe length set for the local equipment

Notify the opposite equipment that the lengthof transmitted frames should be changed.

The opposite equipment does not transmitthe packet that is longer than the maximumframe length set for the local equipment



----End

ReferenceNone.

D.4.8 ETHFRG

DescriptionETHFRG indicates that an RMON threshold-crossing event is reported when the number ofreceived packets that are shorter than 64 bytes and have FCS or alignment errors exceeds thepreset upper threshold.

Impact on SystemData transmission is delayed or packet loss occurs.



710

Possible Causesl The working modes of the ports on the equipment at both ends are not consistent.


l The ports on the equipment at both ends work in half-duplex mode, and the data traffic isvery heavy.

Procedure

Step 1 Check whether the working modes of the ports on the equipment at both ends are consistent.

If... Then...

The working modes are consistent Go to the next step.

The working modes are not consistent Change the working mode of the local port so thatthe ports on the equipment at both ends work inconsistent modes.

Step 2 Check whether the working modes of the ports on the equipment at both ends are set to the half-duplex mode.

If... Then...

The working modes are not set to the half-duplex mode


The working modes are set to the half-duplex mode

Change the working modes of the ports on theequipment at both ends to the full-duplex modeor adaptive mode.


----End

D.4.9 ETHJAB

Description

ETHJAB indicates that an RMON threshold-crossing alarm is reported when the number ofreceived packets that are longer than 1518 bytes and have FCS or alignment errors is higher thanthe upper threshold.


Data transmission is delayed or packet loss occurs.

Possible Causesl The working modes of the ports on the equipment at both ends are not consistent.




711

Procedure

Step 1 Check whether the working modes of the ports on the equipment at both ends are consistent.

If... Then...

The working modes are consistent Go to the next step.

The working modes are not consistent Change the working mode of the local port so thatthe ports on the equipment at both ends work inconsistent modes.


----End

D.4.10 ETHCOL

DescriptionETHCOL indicates the number of detected packet collisions. An RMON threshold-crossingevent is reported when the number of collisions is higher than the upper threshold or lower thanthe lower threshold.

Impact on SystemThe opposite equipment fails to normally receive services.

Possible CausesGenerally, this event is caused when the local port is connected to a large number of devicesthat work in half-duplex mode.

Procedure


If... Then...




If... Then...







712


----End

Reference

None.

D.4.11 ETHFCS

Description

ETHFCS indicates the number of received Ethernet data frames with FCS check errors at thelocal end (excluding the oversized and undersized frames). An RMON threshold-crossing eventis reported when the number is higher than the upper threshold or lower than the lower threshold.

Impact on System

Most ports discard the packets with FCS check errors. The system services are interrupted inthe worst case.

Possible Causes1. The local port and opposite port work in inconsistent modes. For example, one port works

in full-duplex mode, and the opposite port works in half-duplex mode.

2. The transmission line is of the poor quality and bit errors exist.

3. The hardware at the local end is faulty.

Procedure

Step 1 Therefore, handle the alarm according to the specific performance event.

If... Then...




If... Then...

The ports on the equipment at both endswork in inconsistent modes

Change the working modes of the ports on theequipment at both ends so that they can workin consistent modes

The ports on the equipment at both endswork in consistent modes



----End



713

Reference

None.

D.4.12 ATMPW_LOSPKTS

Description

The ATMPW_LOSPKTS is a performance event indicating the number of lost ATM PWpackets.


None.

Possible Causes1. Signals on the radio link deteriorate.2. A strong interference source is present near the equipment.3. A board at the transmit or receive end is faulty.4. The operating temperature of the equipment is very high.

Procedure

Step 1 Handle the fault on the radio link. For details, see 5.3 Troubleshooting the Radio Link.

Step 2 Remove the interference source near the equipment and then check whether the performanceevent is cleared.


Step 4 Replace the faulty board and then check whether the performance event is cleared.

Step 5 Rectify the fault in the fan so that the fan lowers the operating temperature of the equipment.

----End

Related Information

None.

D.4.13 ATMPW_MISORDERPKTS

Description

The ATMPW_MISORDERPKTS is a performance event indicating the number of disorderedATM PW packets.


None.



714


Procedure






----End


D.4.14 ATMPW_UNKNOWNCELLS

DescriptionThe ATMPW_UNKNOWNCELLS a performance event indicating the number of unknowncells in an ATM PW service.



Procedure






715



----End


D.4.15 ATM_CORRECTED_HCSERR

DescriptionThe ATM_CORRECTED_HCSERR is a performance event indicating the number of cells thatare received by an ATM port and contain correctable header check sequence (HCS) errors.


Possible Causes1. A strong interference source is present near the equipment.2. A board at the transmit or receive end is faulty.3. The operating temperature of the equipment is very high.

Procedure





----End


D.4.16 ATM_UNCORRECTED_HCSERR

DescriptionThe ATM_UNCORRECTED_HCSERR is a performance event indicating the number of cellsthat are received by an ATM port and contain uncorrectable header check sequence (HCS) errors.




716

Possible Causes1. Signals on the radio link deteriorate.

2. A strong interference source is present near the equipment.

3. A board at the transmit or receive end is faulty.

4. The operating temperature of the equipment is very high.

Procedure

Step 1 Refer to 5.3 Troubleshooting the Radio Link and handle the fault on the radio link.




----End

Related Information

None.

D.4.17 CES_MISORDERPKTS

Description

The CES_MISORDERPKTS is a performance event indicating the count of lost disordered CESPW packets.


The packets are disordered. As a result, the packet loss rate increases and services are affected.

Possible Causes1. Signals degrade on the link.

2. The link is looped.

3. The link is congested.

Related Alarms

CES_MISORDERPKT_EXC

Procedure

Step 1 See 5.3 Troubleshooting the Radio Link.

Step 2 Release the loop.



717

Step 3 Check the bandwidth utilization. If the bandwidth is exhausted, increase the bandwidth oreliminate any source that transmits a large amount of invalid data.

----End


D.4.18 CES_STRAYPKTS

DescriptionThe CES_STRAYPKTS is a performance event indicating the number of misconnected packetsin a period.

Impact on the SystemThe packets are discarded. As a result, the packet loss rate increases and services are affected.

Possible Causes1. Links are misconnected.

Related AlarmsCES_STRAYPKT_EXC

Procedure

Step 1 Check the link configuration and rectify the fault.

----End


D.4.19 CES_MALPKTS

DescriptionThe CES_MALPKTS is a performance event indicating the number of deformed CES packetsin a period.

Impact on the SystemThe packets are discarded. As a result, the packet loss rate increases and services are affected.

Possible Causes1. The RTP head enabling status is different between the two ends of the PW.



718

2. Bit errors occur on the link.

Related AlarmsCES_MALPKT_EXC

Procedure

Step 1 Set the RTP head enabling status to the same on the two ends of the PW. For details, seeModifying CES Service Parameters.

----End


D.4.20 CES_JTRUDR

DescriptionThe CES_JTRUDR is a performance event indicating the number of jitter buffer underflows.

Impact on the SystemWhen no packets are transmitted from the jitter buffer, the buffer underflows.

Possible Causes1. Signals degrade on the link.2. The PSN network clocks used for the transmission of CES services are not synchronized.3. The link is looped.4. The link is congested.5. The size of buffer area is set to a low value.

Related AlarmsCES_JTRUDR_EXC

Procedure

Step 1 Troubleshoot the link. For details, see 5.3 Troubleshooting the Radio Link.

Step 2 Synchronize the PSN network clock by setting clock synchronization, reducing transmissionnodes, and optimizing transmission routes.



Step 5 Query the size of buffer area. For details, see Querying CES Service Information.



719

Step 6 Determine whether the size can be increased according to network planning. If yes, change thesize to a greater value. For details, see Managing CES Services.

----End


D.4.21 CES_JTROVR

DescriptionThe CES_JTROVR is a performance event indicating the number of jitter buffer overflows.

Impact on the SystemThe jitter buffer is insufficient. As a result, the buffer overflows.

Possible Causes1. The jitter buffer area is too small.2. The clocks are not synchronous.3. Link quality deteriorates, causing more jitters.4. There are too many hops of radio link on the network side, causing a large number of jitters.

Related AlarmsCES_JTROVR_EXC

Procedure

Step 1 Allocate a larger jitter buffer area.

Step 2 Check whether the LTI and other clock-related alarms are reported.


Step 4 Determine whether the hops can be reduced according to network planning. If yes, reduce thehops of radio link on the network side.

----End


D.4.22 CES_LOSPKTS

DescriptionThe CES_LOSPKTS is a performance event indicating the number of CES packets lost in aperiod.



720

Impact on the SystemWhen this alarm occurs, all 1s are inserted and services are interrupted.

Possible Causes1. The link transmission quality is poor.2. The link is configured as a loop.3. Link congestion occurs.

Related AlarmsCES_LOSPKT_EXC

Procedure




----End




721

E Alarm Management

The alarm management on the OptiX RTN 910 is classified into the NE alarm management andboard alarm management.

E.1 NE Alarm ManagementThe NE alarm management function set by user is applicable to all the boards on the NE.

E.2 Board Alarm ManagementThe board alarm management function is only applicable to the board on which users haveconfigured this function.

OptiX RTN 910 Radio Transmission SystemMaintenance Guide (U2000) E Alarm Management


722

E.1 NE Alarm ManagementThe NE alarm management function set by user is applicable to all the boards on the NE.

The equipment supports the following NE alarm management functions:

l Settings of the alarm storage model Setting of the alarm delayl Setting of the alarm reversion mode

For details about these functions, see the manuals or online Help of the NMS.

E.2 Board Alarm ManagementThe board alarm management function is only applicable to the board on which users haveconfigured this function.

E.2.1 Setting the Alarm SeverityAlarms are classified into four levels: critical, major, minor, and warning, according to theirseverities. The maintenance personnel can change the alarm severity by using the NMS.

This function is supported by all the boards.

l Critical alarm: A critical alarm indicates a critical problem with the network. A criticalproblem can be the failure, overload, or system restart of mission-critical boards. It mustbe cleared immediately. Otherwise, system breakdown may occur.

l Major alarm: A major alarm indicates failure of certain boards or links, such ascommunication links. Urgent action is required to rectify the fault as this type of alarmsaffects the QoS of the system.

l Minor alarm: A minor alarm indicates a non-service affecting problem that needs to besolved, for example, fan speed exceeds threshold alarm. This type of alarms does not affectthe QoS of the system, but you need to locate and remove these faults in time.

l Warning alarm: A warning alarm indicates a potential error that may affect the QoS of thesystem, for example, License file expiring precaution alarm. This type of alarms needs tobe handled based on actual conditions.

Critical alarms and major alarms need to be handled immediately to avoid system failures andservice interruptions.

E.2.2 Alarm SuppressionThe maintenance personnel can change the alarm monitoring attribute by setting the alarmsuppression function. A board detects only the alarms that are not suppressed. The alarmsuppression function helps users to ignore their unconcerned alarms.


E.2.3 Alarm Auto-ReportIf Alarm Auto-Report is set to Reported, all the detected alarms are reported to the NMS in atimely manner. If Alarm Auto-Report is set to Not Report, the alarms are reported only when



723

alarm query is performed on the NMS. The maintenance personnel can change the setting onthe NMS.


E.2.4 Alarm ReversionIn the case of a port that is not configured with services, certain alarms may be reported. To filterthe alarms that users are not concerned, set these alarms to be reversed. In this manner, the alarmstatus at this port is the opposite to the actual case. That is, the status is displayed as normalwhen an alarm is actually reported.

The alarm reversion function is available in three modes, namely, non-reversion, automaticreversion, and manual reversion.

l Non-revertiveIn this mode, the alarms are monitored by default and alarm reversion cannot be enabledfor a port.

l Auto reversionIn this mode, alarm reversion can be enabled for a port where alarms are reported. Afteralarm reversion is enabled at a port, alarms are not reported. When the current alarm iscleared, the alarm reversion automatically changes to the disabled status. That is, it changesto the non-reversion mode. Then, the alarm reporting status at the port is the same as theactual status.

l Manual reversionIn this mode, alarm reversion can be enabled for a port regardless of whether any alarmsare reported at the port. After alarm reversion is enabled, the alarm reporting status at theport is opposite to the actual status. After alarm reversion is manually disabled, the alarmreversion status changes to the non-reversion 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.

l Alarm reversion is realized on the NE software. The alarm data is the same on the NE andthe NMS, which indicates the status after the alarm reversion. If you directly query thealarm data of a board, however, the actual alarm status is returned.

l Alarm reversion is set based on ports. It is supported by each port on the SL1D, SP3S,SP3D, IFX2, IFU2, IF1, ISU2, ISX2, EM6X, MP1, EM4T, EM4F, EM6TB, EM6TA,EM6FA, SL1DA, EM6T, and EM6F boards.

E.2.5 Setting of the Bit Error Alarm ThresholdWhen the number of bit errors detected by a board exceeds a specified number, the boardgenerates a bit error alarm. This specific number is the bit error alarm threshold, and the settingof this threshold is supported by all the bit error threshold-crossing and degrading alarms on theNE.



724

Table E-1 Setting of the bit error alarm threshold

Alarm Name Default Alarm Threshold Applicable Board

B1_EXC 10-3 SL1DA, SL1D and IF1

B1_SD 10-6


B2_SD 10-6


B3_SD 10-6

BIP_EXC 10-3 ISU2, ISX2, MP1, EFP8,EMS6, SP3S, SP3D, IFU2,and IFX2BIP_SD 10-6

MW_BER_EXC 10-3 ISU2, ISX2, IFU2 and IFX2

MW_BER_SD 10-6

E.2.6 AIS InsertionAIS insertion can be set for certain alarms reported on a board. When the board detects thealarms, it inserts all 1s into the lower level service to indicate the remote end that the service isunavailable.

Table E-2 Setting of the AIS insertion

Trigger Condition Default Value Applicable Board

B1_EXC Enabled SL1DA, SL1D and IF1

B2_SD Disabled SL1DA, SL1D and IF1

B2_EXC Disabled SL1DA, SL1D and IF1

HP_LOM Enabled

HP_TIM Disabled

HP_SLM Disabled

HP_UNEQ Disabled

B3_EXC Enabled SL1DA, SL1D and IF1

B3_SD Disabled

B1_SD Disabled SL1DA, SL1D and IF1

LP_TIM Disabled MP1, SP3S and SP3D



725


LP_UNEQ Disabled

LP_SLM Disabled

T_ALOS Enabled

BIP_EXC Disabled

BIP_SD Disabled

MW_BER_EXC Enabled ISU2, ISX2, IFX2 and IFU2

MW_BER_SD Disabled

NOTE

l When the SL1D/SL1DA, board detects the R_LOS, R_LOF, MS_AIS, AU_AIS, or AU_LOP alarm,it forcibly inserts the AIS.

l When the IF1 board detects the MW_LOF, MW_LIM, R_LOF, MS_AIS, AU_AIS, or AU_LOPalarm, it forcibly inserts the AIS.

l When the ISU2, ISX2, IFX2 and IFU2 board detect the MW_LOF, MW_LIM, or R_LOF alarm, itforcibly inserts the AIS.

E.2.7 UNEQ InsertionWhen a board detects that the service path is not in use or that the LOS alarm exists, it insertsall 0s into the service signal to notify the remote end that this signal is unavailable.

Table E-3 Setting of the UNEQ insertion


T_ALOS Disabled MP1, SP3S and SP3D

Service path being not in use Disabled



726

F Performance Event Management

The performance event management is classified into the NE performance event managementand board performance event management.

F.1 NE Performance Event ManagementThe NE performance event management function set by user is applicable to all the boards onthe NE.

F.2 Board Performance Event ManagementThe performance event management function is only applicable to the board on which usershave configured this function.

OptiX RTN 910 Radio Transmission SystemMaintenance Guide (U2000) F Performance Event Management


727

F.1 NE Performance Event ManagementThe NE performance event management function set by user is applicable to all the boards onthe NE.

The OptiX RTN 910 supports the following NE performance event management functions:

l Setting NE performance event monitoringl Setting the start/end time of performance eventsl Enabling/Disabling the reporting of UAT events

For details about these functions, see the manuals or online Help of the NMS.

F.2 Board Performance Event ManagementThe performance event management function is only applicable to the board on which usershave configured this function.

Table F-1 Board performance event management function

Function Applicable Board

Setting 15-minute/24-hour performancemonitoring

SL1DA, EMS6, SL1D, SP3S, SP3D, CSHA, CSHB, CSHC,CSTA, CSHD, ODU, IFX2, IFU2, ISU2, ISX2, ML1, MD1,EFP8, and IF1

Setting 15-minute/24-hour performance eventauto-reporting

SL1DA, EMS6, SL1D, SP3S, SP3D, CSHA, CSHA, CSHC,CSTA, CSHD, MP1, CSHE, ODU, IFX2, IFU2, ISU2, ISX2,ML1, MD1, EFP8, and IF1

Setting performancethresholds

SL1DA, EMS6, SL1D, SP3S, SP3D, IFX2, IFU2, ISU2, ISX2,ML1, MD1, EFP8, CSHC, CSHD, CSHE, and IF1

Resetting theperformance register

SL1DA, SL1D, SP3S, SP3D, ODU, IFX2, IFU2, ISU2, ISX2, andIF1

Generating performancethreshold-crossingalarms

SL1DA, EMS6, SL1D, SP3S, SP3D, ODU, IFX2, IFU2, ISU2,ISX2, ML1, MD1, EFP8, MP1, and IF1

Monitoring UAT events SL1DA, EMS6, SL1D, SP3S, SP3D, IFX2, IFU2, ISU2, ISX2,EFP8, MP1, and IF1

Monitoring CSESperformance events

SL1DA, EMS6, SL1D, SP3S, SP3D, IFX2, IFU2, ISU2, ISX2,EFP8, MP1, and IF1

OptiX RTN 910 Radio Transmission SystemMaintenance Guide (U2000) F Performance Event Management


728

G Alarm Suppression Relationship

When the alarm suppression function is disabled on an NE, the root alarm and certain correlatedalarms are reported if a fault occurs on this NE. After the alarm suppression function is enabled,the reporting of the correlated alarms is suppressed according to the relationship between alarmswhen the root alarm is reported. The alarm suppression relationship can be classified into thesuppression relationship between intra-board alarms and suppression relationship between inter-board alarms.

Table G-1 Suppression relationship between intra-board alarms

Alarm Identifier Identifier of the Suppressed Alarm

MW_LOF R_LOS, R_LOF, R_LOC,MW_FEC_UNCOR, MW_RDI,MW_LIM, MS_AIS, B1_EXC, B1_SD,MS_RDI, B2_EXC, B2_SD, MS_REI,AU_AIS, AU_LOP, B3_EXC, B3_SD,HP_TIM, HP_UNEQ, HP_SLM,HP_RDI, HP_LOM, HP_REI,MW_BER_EXC, and MW_BER_SD

MW_LIM MW_RDI


LSR_NO_FITED R_LOS, R_LOC, R_LOF, J0_MM,B1_EXC, B1_SD, MS_AIS, MS_RDI,B2_EXC, B2_SD, MS_REI, AU_AIS,AU_LOP, HP_TIM, HP_UNEQ,HP_SLM, HP_RDI, B3_EXC, B3_SD,HP_LOM, HP_REI, IN_PWR_LOW,MW_RDI, and MW_LIM

OptiX RTN 910 Radio Transmission SystemMaintenance Guide (U2000) G Alarm Suppression Relationship


729


R_LOS or R_LOC R_LOF, J0_MM, B1_EXC, B1_SD,MS_AIS, MS_RDI, B2_EXC, B2_SD,MS_REI, AU_AIS, AU_LOP, HP_TIM,HP_UNEQ, HP_SLM, HP_RDI, B3_EXC,B3_SD, HP_LOM, HP_REI,IN_PWR_LOW, MW_RDI, andMW_LIM

R_LOF J0_MM, B1_EXC, B1_SD, MS_AIS,MS_RDI, B2_EXC, B2_SD, MS_REI,AU_AIS, AU_LOP, HP_TIM, HP_UNEQ,HP_SLM, HP_RDI, B3_EXC, B3_SD,HP_LOM, HP_REI, MW_RDI,MW_LIM, MW_BER_EXC, andMW_BER_SD

MS_AIS B2_SD, MS_REI, MS_RDI, AU_AIS,AU_LOP, HP_TIM, HP_UNEQ,HP_SLM, HP_RDI, B3_EXC, B3_SD,HP_LOM, HP_REI, and B2_EXC

MS_RDI MS_REI

AU_AIS AU_LOP, B3_EXC, B3_SD, HP_TIM,HP_SLM, HP_UNEQ, HP_RDI,HP_LOM, and HP_REI

AU_LOP B3_EXC, B3_SD, HP_TIM, HP_SLM,HP_UNEQ, HP_RDI, HP_LOM, andHP_REI

HP_UNEQ HP_TIM, HP_LOM, and HP_RDI

HP_RDI HP_REI

LP_UNEQ LP_TIM, LP_RDI, LP_RFI, LP_REI,BIP_SD, and BIP_EXC

LP_RDI LP_REI

B1_EXC B1_SD, and MS_REI

B2_EXC B2_SD, and MS_REI

B3_EXC B3_SD

TU_AIS LP_TIM, LP_UNEQ, LP_RDI, LP_REI,LP_RFI, LP_R_FIFO, BIP_EXC,BIP_SD, LP_SLM, TU_LOP, andDOWN_E1_AIS

TU_LOP LP_TIM, LP_UNEQ, LP_RDI, LP_REI,LP_RFI, LP_R_FIFO, BIP_EXC,BIP_SD, LP_SLM, and DOWN_E1_AIS



730


T_ALOS E1_LOS, DDN_LFA and UP_E1_AIS

E1_LOS UP_E1_AIS

BIP_EXC BIP_SD

LASER_MOD_ERR ETH_LOS

UP_E1_AIS LFA, DDN_LFA, and ALM_E1RAI

LFA LMFA, ALM_IMA_LIF, andALM_E1RAI

LMFA ALM_IMA_LIF

ALM_E1RAI ALM_IMA_RFI, andALM_IMA_RE_RX_UNUSABLE

ETH_EFM_DF ETH_EFM_REMFAULT

ETH_EFM_REMFAULT ETH_EFM_EVENT

ALM_IMA_LIF ALM_IMA_LODS

IMA_GROUP_LE_DOWN VC_LOC, and VP_LOC

MPLS_TUNNEL_LOCV MPLS_TUNNEL_UNKNOWN,MPLS_TUNNEL_Excess, andMPLS_TUNNEL_SF

MPLS_TUNNEL_SF MPLS_TUNNEL_SD

MPLS_TUNNEL_FDI MPLS_TUNNEL_LOCV

ETH_APS_PATH_MISMATCH ETH_APS_LOST,ETH_APS_TYPE_MISMATCH, andETH_APS_SWITCH_FAIL

ETH_APS_LOST ETH_APS_TYPE_MISMATCH, andETH_APS_SWITCH_FAIL

MPLS_PW_LOCV MPLS_PW_UNKNOWN,MPLS_PW_Excess, and MPLS_PW_SF

MPLS_PW_SF MPLS_PW_SD

PWAPSAPS_PATH_MISMATCH PWAPS_LOST, PWAPS_TYPE_MIS-MATCH, and PWAPS_SWITCH_FAIL

PWAPS_LOST PWAPS_TYPE_MISMATCH, andPWAPS_SWITCH_FAIL

ETH_CFM_MISMERGE ETH_CFM_LOC

CES_LOSPKT_EXC CES_STRAYPKT_EXC,CES_JTROVR_EXC, andCES_JTRUDR_EXC



731


CES_STRAYPKT_EXC CES_MISORDERPKT_EXC, andCES_MALPKT_EXC

PG_LINK_FAIL PG_PRT_DEGRADED

Table G-2 Suppression relationship between intra-board alarms


R_LOS, R_LOC, MS_AIS, AU_AIS, orAU_LOP

TU_AIS

MW_LOF or MW_LIM TU_AIS

ETH_LOS MPLS_TUNNEL_LOCV,MPLS_TUNNEL_OAMFAIL

MPLS_TUNNEL_LOCV MPLS_PW_LOCV

MPLS_TUNNEL_BDI MPLS_PW_BDI



732

H Indicators of Boards

Indicators of Boards

Table H-1 Status explanation for indicators on the CSTA

Indicator State Meaning

STAT On (green) The board is working properly.

On (red) The board hardware is faulty.

Off l The board is not working.l The board is not created.l There is no power supplied to the

board.

PROG Blinks on (green) and off at100 ms intervals

Software is being loaded to the boardduring the power-on or resetting processof the board.

Blinks on (green) and off at300 ms intervals

The board software is in BIOS boot stateduring the power-on or resetting processof the board.

On (green) l When the board is being powered onor being reset, the upper layersoftware is being initialized.

l When the board is running, thesoftware is running normally.

Blinks on (red) and off at100 ms intervals

The BOOTROM self-check fails duringthe power-on or resetting process of theboard.

OptiX RTN 910 Radio Transmission SystemMaintenance Guide (U2000) H Indicators of Boards


733


On (red) l The memory self-check fails orloading upper layer software failsduring the power-on or resettingprocess of the board.

l The logic file or upper layer softwareis lost during the running process ofthe board.

l The pluggable storage card is faulty.

SYNC On (green) The clock is working properly.

On (red) The clock source is lost or a clockswitchover occurs.

SRV On (green) The system is working properly.

On (red) A critical or major alarm occurs in thesystem.

On (yellow) A minor or remote alarm occurs in thesystem.

Off There is no power supplied to the system.

LOS1 On (red) The first STM-1 port on the line isreporting the R_LOS alarm.

Off The first STM-1 port on the line is freeof R_LOS alarms.

LOS2 On (red) The second STM-1 port on the line isreporting the R_LOS alarm.

Off The second STM-1 port on the line is freeof R_LOS alarms.

Table H-2 Status explanation for indicators on the CSHA/CSHB





board.



734



















Table H-3 Status explanation for indicators on the CSHC






735



board.


















LINK1 On (green) The connection at a specific port isworking properly.

Off The connection at a specific port isinterrupted.



736


ACT1 On or blinking (yellow) Data is being transmitted or received.

Off No data is being transmitted or received.

LINK2 On (green) The port connection is normal.

Off The port connection is interrupted.

ACT2 On or blinking (yellow) Data is being transmitted or received.

Off No data is being transmitted or received.

LOS1 On (red) The first port on the line is reporting theR_LOS alarm.

Off The first port on the line is free of R_LOSalarms.

LOS2 On (red) The second port on the line is reportingthe R_LOS alarm.

Off The second port on the line is free ofR_LOS alarms.

Table H-4 Status explanation for indicators on the CSHD/CSHE





board.









737













LINK1a On (green) The connection at the GE1 port isworking properly.

Off The connection at the GE1 port isinterrupted.

ACT1a On or blinking (yellow) Data is being transmitted or received atthe GE1 port.

Off No data is being transmitted or receivedat the GE1 port.

LINK2a On (green) The connection at the GE2 port isworking properly.

Off The connection at the GE2 port isinterrupted.

ACT2a On or blinking (yellow) Data is being transmitted or received atthe GE2 port.

Off No data is being transmitted or receivedat the GE2 port.



738

NOTEa: The LINK1, LINK2, ACT1, and ACT2 indicators are available only on the CSHD and indicate opticalport status.

Table H-5 Status explanation for indicators on the IF1


STAT On (green) The board is workingproperly.


Off l The board is not working.l The board is not created.l There is no power

supplied to the board.

SRV On (green) The services are normal.

On (red) A critical or major alarmoccurs in the services.

On (yellow) A minor or remote alarmoccurs in the services.

LINK On (green) The radio link is normal.

On (red) The radio link is faulty.

ODU On (green) The ODU is workingproperly.

On (red) l The ODU is reportingcritical or major alarms.

l There is no powersupplied to the ODU.

On (yellow) The ODU is reporting minoralarms.

Blinks on (yellow) and off at300 ms intervals

The antennas are not aligned.

RMT On (yellow) The remote equipment isreporting defects.

Off The remote equipment is freeof defects.

ACT On (green) l In a 1+1 protected system,the board works as theactive one.

l In an unprotected system,the board has beenactivated.



739


Off l In a 1+1 protected system,the board works as thestandby one.

l In an unprotected system,the board is not activated.

Table H-6 Status explanation for indicators on the IFU2




Off l The board is not working.l The board is not created.l There is no power supplied to the board.


On (red) A critical or major alarm occurs in theservices.

On (yellow) A minor or remote alarm occurs in theservices.



ODU On (green) The ODU is working properly.

On (red) l The ODU is reporting critical or majoralarms.

l There is no power supplied to the ODU.

On (yellow) The ODU is reporting minor alarms.

Blinks on (yellow)and off at 300 msintervals


RMT On (yellow) The remote equipment is reporting defects.

Off The remote equipment is free of defects.

ACT On (green) l In a 1+1 protected system, the boardworks as the active one.

l In an unprotected system, the board hasbeen activated.



740


Off l In a 1+1 protected system, the boardworks as the standby one.

l In an unprotected system, the board is notactivated.

Table H-7 Status explanation for indicators on the ISU2





















741






Table H-8 Status explanation for indicators on the IFX2


XPIC On (green) The XPIC input signal isnormal.

On (red) The XPIC input signal is lost.

Off The XPIC function isdisabled.













742













Table H-9 Status explanation for indicators on the ISX2


XPIC On (green) The XPIC input signal isnormal.

On (red) The XPIC input signal is lost.

Off The XPIC function isdisabled.







743



















Table H-10 Status explanation for indicators on the EM6T/EM6F






744





On (yellow) A minor alarm occurs in the system.



Software is being loaded to the board duringthe power-on or resetting process of theboard.


The board software is in BIOS boot stateduring the power-on or resetting process ofthe board.

On (green) l When the board is being powered on orbeing reset, the upper layer software isbeing initialized.

l When the board is running, the softwareis running normally.

Blinks on (red) and off at 100ms intervals

The BOOTROM self-check fails during thepower-on or resetting process of the board.

On (red) l The memory self-check fails or loadingupper layer software fails during thepower-on or resetting process of theboard.

l The logic file or upper layer software islost during the running process of theboard.


LINK1a On (green) The GE1 port is connected correctly and isnot receiving or transmitting data.

Blinking (green) The GE1 port is receiving or transmittingdata.

Off The GE1 port is not connected or isconnected incorrectly.

LINK2a On (green) The GE2 port is connected correctly and isnot receiving or transmitting data.

Blinking (green) The GE2 port is receiving or transmittingdata.



745



NOTE

a: The LINK1 and LINK2 indicators are available only on the EM6F and indicate the states of thecorresponding GE ports.

Table H-11 Status explanation for indicators on the EM6TA/EM6FA



















746


On (red) The memory self-check fails or loadingupper layer software fails during the power-on or resetting process of the board.The logic file or upper layer software is lostduring the running process of the board.The pluggable storage card is faulty.

L/A1a On (green) The GE1 port is connected correctly and isnot receiving or transmitting data.

Blinking (yellow) The GE1 port is receiving or transmittingdata.


L/A2a On (green) The GE2 port is connected correctly and isnot receiving or transmitting data.

Blinking (yellow) The GE2 port is receiving or transmittingdata.


NOTE

a: The L/A1 and L/A2 indicators are available only on the EM6FA and indicate the states of thecorresponding GE ports.

Table H-12 Status explanation for indicators on the EMS6











747


On (green) l The upper layer software is beinginitialized during the power-on orresetting process of the board.

l The software is running properly duringthe running process of the board.






SRV On (green) The system is working normally.




LINK1 On (green) The GE1 port is connected correctly.


The receive optical power at the GE1 opticalport is higher than the upper threshold.

Blinks 300 ms on (red) and 700ms off

The receive optical power at the GE1 opticalport is lower than the lower threshold.


ACT1 Blinking (yellow) The GE1 port is receiving or transmittingdata.

Off The GE1 port is not receiving ortransmitting data.

LINK2 On (green) The GE2 port is connected correctly.


The receive optical power at the GE2 opticalport is higher than the upper threshold.

Blinks 300 ms on (red) and 700ms off

The receive optical power at the GE2 opticalport is lower than the lower threshold.




748


ACT2 Blinking (yellow) The GE2 port is receiving or transmittingdata.

Off The GE2 port is not receiving ortransmitting data.

Table H-13 Status explanation for indicators on the EFP8





















749



Table H-14 Status explanation for indicators on the SL1D/SL1DA









Off The services are notconfigured.

LOS1 On (red) The first port of the SL1D/SL1DA is reporting theR_LOS alarm.

Off The first port of the SL1D/SL1DA is free of R_LOSalarms.

LOS2 On (red) The second port of theSL1D/SL1DA is reportingthe R_LOS alarm.

Off The second port of theSL1D/SL1DA is free ofR_LOS alarms.

Table H-15 Status explanation for indicators on the SP3S/SP3D





750









Table H-16 Status explanation for indicators on the ML1/MD1










Table H-17 Status explanation for indicators on the PIU

Indicator Status Description

PWRA On (green) The power supply is connected.



751

Indicator Status Description

Off There is no power supplied to the PIU or the powersupply is connected incorrectly.

PWRB On (green) The power supply is connected.

Off There is no power supplied to the PIU or the powersupply is connected incorrectly.

Table H-18 Status explanation for indicators on the FAN


FAN On (green) The fan is working properly.

On (red) The fan is faulty.

Off The fan is not powered on or is not installed.



752

I Glossary

Terms are listed in an alphabetical order.

I.1 0-9This section provides the terms starting with numbers.

I.2 A-EThis section provides the terms starting with letters A to E.

I.3 F-JThis section provides the terms starting with letters F to J.

I.4 K-OThis section provides the terms starting with letters K to O.

I.5 P-TThis section provides the terms starting with letters P to T.

I.6 U-ZThis section provides the terms starting with letters U to Z.

OptiX RTN 910 Radio Transmission SystemMaintenance Guide (U2000) I Glossary


753

I.1 0-9This section provides the terms starting with numbers.

1U The standard electronics industries association (EIA) rack unit (44 mm/1.75 in.)

I.2 A-EThis section provides the terms starting with letters A to E.

A

ABR See available bit rate

ACAP See adjacent channel alternate polarization

access control list A list of entities, together with their access rights, which are authorized to have accessto a resource.

ACL See access control list

adaptive modulation A technology that is used to automatically adjust the modulation scheme according tothe channel quality. When the channel quality is favorable, the equipment adopts a high-efficiency modulation scheme to improve the transmission efficiency and the spectrumutilization of the system. When the channel quality is degraded, the equipment adoptsthe low-efficiency modulation scheme to improve the anti-interference capability of thelink that carries high-priority services.

ADC See analog to digital converter

add/drop multiplexer Network elements that provide access to all or some subset of the constituent signalscontained within an STM-N signal. The constituent signals are added to (inserted), and/or dropped from (extracted) the STM-N signal as it passed through the ADM.

Address ResolutionProtocol

Address Resolution Protocol (ARP) is an Internet Protocol used to map IP addresses toMAC addresses. It allows hosts and routers to determine the link layer addresses throughARP requests and ARP responses. The address resolution is a process in which the hostconverts the target IP address into a target MAC address before transmitting a frame.The basic function of the ARP is to query the MAC address of the target equipmentthrough its IP address.

adjacent channelalternate polarization

A channel configuration method, which uses two adjacent channels (a horizontalpolarization wave and a vertical polarization wave) to transmit two signals.

ADM See add/drop multiplexer

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

aggregation A collection of objects that makes a whole. An aggregation can be a concrete orconceptual set of whole-part relationships among objects.



754

AIS See alarm indication signal

alarm automatic report When an alarm is generated on the device side, the alarm is reported to the NetworkManagement System (NMS). Then, an alarm panel prompts and the user can view thedetails 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 indication signal 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.

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

assured forwarding One of the four per-hop behaviors (PHB) defined by the Diff-Serv workgroup of IETF.It is suitable for certain key data services that require assured bandwidth and short delay.For traffic within the bandwidth limit, AF assures quality in forwarding. For traffic thatexceeds the bandwidth limit, AF degrades the service class and continues to forward thetraffic instead of discarding the packets.

AsynchronousTransfer Mode

A protocol for the transmission of a variety of digital signals using uniform 53 byte cells.A transfer mode in which the information is organized into cells; it is asynchronous inthe sense that the recurrence of cells depends on the required or instantaneous bit rate.Statistical and deterministic values may also be used to qualify the transfer mode.

ATM See Asynchronous Transfer Mode

ATM PVC ATM permanent virtual circuit

ATPC See automatic transmit power control

attenuator A device used to increase the attenuation of an Optical Fiber Link. Generally used toensure that the signal at the receive end is not too strong.

AU See administrative unit

automatic protectionswitching

Capability of a transmission system to detect a failure on a working facility and to switchto a standby facility to recover the traffic.

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.



755

B

backward defectindication

When detecting a defect, the sink node of an 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 manages oneor more BTSs in an actual network.

base transceiver station 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.

basic input/outputsystem

A firmware stored in the computer mainboard. It contains basic input/output controlprograms, power-on self test (POST) programs, bootstraps, and system settinginformation. The BIOS provides hardware setting and control functions for the computer.

BDI See backward defect indication

BE See best effort

BER See bit error rate

best effort A traditional IP packet transport service. In this service, the diagrams are forwardedfollowing the sequence of the time they reach. All diagrams share the bandwidth of thenetwork and routers. The amount of resource that a diagram can use depends of the timeit reaches. BE service does not ensure any improvement in delay time, jitter, packet lossratio, and high reliability.

binding strap The binding strap is 12.7 mm wide, with one hook side (made of transparentpolypropylene material) and one mat side (made of black nylon material).

BIOS See basic input/output system

BIP See 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 Ratio of received bits that contain errors. BER is an important index used to measure thecommunications quality of a network.

bit interleaved parity A method of error monitoring. With even parity an X-bit code is generated by thetransmitting equipment over a specified portion of the signal in such a manner that thefirst bit of the code provides even parity over the first bit of all X-bit sequences in thecovered portion of the signal, the second bit provides even parity over the second bit ofall X-bit sequences within the specified portion, etc. Even parity is generated by settingthe BIP-X bits so that there is an even number of 1s in each monitored partition of thesignal. A monitored partition comprises all bits which are in the same bit position withinthe X-bit sequences in the covered portion of the signal. The covered portion includesthe BIP-X.

BPDU See bridge protocol data unit



756

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 inter-networking 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. In aprogram, buffers are created to hold some amount of data from each of the files that willbe read or written. In a streaming media application, the program uses buffers to storean advance supply of audio or video data to compensate for momentary delays.

C

cable tie The tape used to bind the cables.

cable tray N/A

cable trough N/A

CAR See committed access rate

CBR See constant bit rate

CBS See committed burst size

CC See connectivity check

CCC See circuit cross connect

CCDP See co-channel dual polarization

CCM See continuity check message

CE See customer edge

central processing unit The computational and control unit of a computer. The CPU is the device that interpretsand executes instructions. The CPU has the ability to fetch, decode, and executeinstructions and to transfer information to and from other resources over the computer'smain data-transfer path, the bus.

CES See circuit emulation service

CF See compact flash

CGMP See Cisco Group Management Protocol

channel A telecommunication path of a specific capacity and/or at a specific speed between twoor more locations in a network. The channel can be established through wire, radio(microwave), fiber or a combination of the three. The amount of information transmittedper second in a channel is the information transmission speed, expressed in bits persecond. For example, b/s (100 bit/s), kb/s (103 bit/s), Mb/s (106 bit/s), Gb/s (109 bit/s),and Tb/s (1012 bit/s).



757

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.

Cisco GroupManagement Protocol

N/A

CIST See common and internal spanning tree

CIST root A switch of the highest priority is elected as the root in an MSTP network.

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 a short-distance chain network.

colored packet A packet whose priority is determined by defined colors.

committed access rate A traffic control method that uses a set of rate limits to be applied to a router interface.CAR is a configurable method by which incoming and outgoing packets can be classifiedinto QoS (Quality of Service) groups, and by which the input or output transmission ratecan be defined.

committed burst size committed burst size. A parameter used to define the capacity of token bucket C, that is,the maximum burst IP packet size when the information is transferred at the committedinformation rate. This parameter must be larger than 0. It is recommended that thisparameter should be not less than the maximum length of the IP packet that might beforwarded.

committed informationrate

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

The single spanning tree calculated by STP and RSTP together with the logicalcontinuation of that connectivity by using MST Bridges and regions, calculated by MSTPto ensure that all LANs in the bridged local area network 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.

connectivity check Ethernet CFM can detect the connectivity between MEPs. The detection is achieved byeach MEP transmitting a Continuity Check Message (CCM) periodically.



758

constant bit rate A kind of service categories defined by the ATM forum. CBR transfers cells based onthe constant bandwidth. It is applicable to service connections that depend on preciseclocking to ensure undistorted transmission.

continuity checkmessage

CCM is used to detect the link status.

corrugated pipe Used to protect optical fibers.

CPU See central processing unit

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.

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.

D

data communicationnetwork

A communication network used in a TMN or between TMNs to support the DataCommunication Function (DCF).

data communicationschannel

The data channel that uses the D1-D12 bytes in the overhead of an STM-N signal totransmit information on operation, management, maintenance and provision (OAM&P)between NEs. The DCC channels that are composed of bytes D1-D3 is referred to as the192 kbit/s DCC-R channel. The other DCC channel that are composed of bytes D4-D12is referred to as the 576 kbit/s DCC-M channel.

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-C DC-return common (with ground)

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



759

DC-return isolate (withground)

A power system, in which the BGND of the DC return conductor is short-circuited withthe PGND on the output side of the power supply cabinet and is isolated from the PGNDon the line between the output of the power supply cabinet and the electric equipment.

DCC See data communications channel

DCN See data communication network

DDF See digital distribution frame

DDN See digital data network

DE See discard eligible

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

A marker in the header of each IP packet that prompts network routers to applydifferentiated grades of service to various packet streams. It is specified by the DiffServpolicy proposed by the IETF (Internet Engineering Task Force). This allows Internet andother IP-based network service providers to offer different levels of service to customers.

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.

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

An Internet gateway protocol mainly based on the RIP. The protocol implements a typicaldense mode 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



760

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 See Ethernet aggregation

E-LAN See Ethernet LAN

E-Line See Ethernet line

E-Tree See Ethernet-tree

EBS See excess burst size

ECC See embedded control channel

EF See expedited forwarding

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.

electromagneticinterference

Any electromagnetic disturbance that interrupts, obstructs, or otherwise degrades orlimits the effective performance of electronics/electrical equipment.

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

A logical channel that uses a data communications channel (DCC) as its physical layer,to enable transmission of operation, administration, and maintenance (OAM)information between NEs.

EMC See electromagnetic compatibility

EMI See electromagnetic interference

Engineering label A mark on a cable, a subrack, or a cabinet for identification.

EPL See Ethernet private line

EPLAN See Ethernet private LAN service

equalization A method of avoiding selective fading of frequencies. Equalization can compensate forthe changes of amplitude frequency caused by frequency selective fading.

ERPS See Ethernet ring protection switching

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.

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



761

Ethernet aggregation A type of Ethernet service that is based on a multipoint-to-point EVC (Ethernet virtualconnection).

Ethernet LAN A type of Ethernet service that is based on a multipoint-to-multipoint EVC (Ethernetvirtual connection).

Ethernet line A type of Ethernet service that is based on a point-to-point EVC (Ethernet virtualconnection).

Ethernet private LANservice

An Ethernet service type, which carries Ethernet characteristic information over adedicated bridge, point-to-multipoint connections, provided by SDH, PDH, ATM, orMPLS server layer networks.

Ethernet private line A type of Ethernet service that is provided with dedicated bandwidth and point-to-pointconnections on an SDH, PDH, ATM, or MPLS server layer network.

Ethernet ringprotection switching

protection switching mechanisms for ETH layer Ethernet ring topologies.

Ethernet virtualprivate LAN service

An Ethernet service type, which carries Ethernet characteristic information over a sharedbridge, point-to-multipoint connections, provided by SDH, PDH, ATM, or MPLS serverlayer networks.

Ethernet virtualprivate line

An Ethernet service type, which carries Ethernet characteristic information over sharedbandwidth, point-to-point connections, provided by SDH, PDH, ATM, or MPLS serverlayer networks.

Ethernet-tree An Ethernet service type that is based on a Point-to-multipoint Ethernet VirtualConnection.

ETS European Telecommunication Standards

ETSI See European Telecommunications Standards Institute

EuropeanTelecommunicationsStandards Institute

A standards-setting body in Europe. Also the standards body responsible for GSM.

EVPL See Ethernet virtual private line

EVPLAN See Ethernet virtual private LAN service

excess burst size A parameter related to traffic. In the single rate three color marker (srTCM) mode, thetraffic control is achieved by the token buckets C and E. Excess burst size is a parameterused to define the capacity of token bucket E, that is, the maximum burst IP packet sizewhen the information is transferred at the committed information rate. This parametermust be larger than 0. It is recommended that this parameter should be not less than themaximum length 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.

expansion Connecting a storage system to more disk enclosures through connection cables,expanding the capacity of the storage system.

expedited forwarding The highest order QoS in the Diff-Serv network. EF PHB is suitable for services thatdemand low packet loss ratio, short delay, and broad bandwidth. In all the cases, EFtraffic can guarantee a transmission rate equal to or faster than the set rate. The DSCPvalue of EF PHB is "101110".



762

I.3 F-JThis section provides the terms starting with letters F to 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 Any network that supports transmission rate of 100Mbits/s. The Fast Ethernet is 10 timesfaster than 10BaseT, and inherits frame format, MAC addressing scheme, MTU, and soon. Fast Ethernet is extended from the IEEE802.3 standard, and it uses the followingthree types of transmission media: 100BASE-T4 (4 pairs of phone twisted-pair cables),100BASE-TX (2 pairs of data twisted-pair cables), and 100BASE-FX (2-core opticalfibers).

fast link pulse The link pulse that is used to encode information during automatic negotiation.

FD See frequency diversity

FDI See forward defect indication

FE See fast Ethernet

FEC See forward error correction

FFD fast failure detection

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

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.

Forced switch For normal traffic signals, switches normal traffic signal to the protection section, unlessan equal or higher priority switch command is in effect or SF condition exists on theprotection section, by issuing a forced switch request for that traffic signal.

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.



763

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 cannot 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 A full-duplex, or sometimes double-duplex system, allows communication in bothdirections, and, unlike half-duplex, allows this to happen simultaneously. Land-linetelephone networks are full-duplex, since they allow both callers to speak and be heardat the same time. A good analogy for a full-duplex system would be a two-lane road withone lane for each direction.

G

gateway networkelement

A network element that is used for communication between the NE application layer andthe NM application layer

GE See gigabit Ethernet

generic framingprocedure

A framing and encapsulated method which can be applied to any data type. It has beenstandardized by ITU-T SG15.

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 See generic framing procedure

gigabit Ethernet GE adopts the IEEE 802.3z. GE is compatible with 10 Mbit/s and 100 Mbit/s Ethernet.It runs at 1000 Mbit/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.

GNE See gateway network element

GPS See Global Positioning System



764

graphical user interface A visual computer environment that represents programs, files, and options withgraphical images, such as icons, menus, and dialog boxes, on the screen.

GTS See generic traffic shaping

GUI See graphical user interface

guide rail Components to guide, position, and support plug-in boards.

H

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.

HDLC See high level data link control

hierarchical quality ofservice

A type of QoS that can control the traffic of users, and perform the scheduling accordingto the priority of user services. HQoS has a perfect traffic statistics function, and theadministrator can monitor the usage of bandwidth of each service. Hence, the bandwidthcan be allocated reasonably through traffic analysis.

high availability Typically, a scheme in which two modules operate in active/standby mode to achievehigh availability. When the active module fails, the standby module automatically takesover the system functions of the active module.

high level data linkcontrol

The HDLC protocol is a general purpose protocol which operates at the data link layerof the OSI reference model. Each piece of data is encapsulated in an HDLC frame byadding a trailer and a header.

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.

higher order path In an SDH network, the higher order path layers provide a server network from the lowerorder path layers.

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 See higher order path

HQoS See hierarchical quality of service

HSB See hot standby

HSDPA See High Speed Downlink Packet Access



765

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 Message Protocol

IDU See indoor unit

IEC See International Electrotechnical Commission

IEEE See Institute of Electrical and Electronics Engineers

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

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 Systemrouting protocol

A protocol used by network devices (routers) to determine the best way to forwarddatagrams or packets through a packet-based network, a process called routing.

internal spanning tree A segment of CIST in a certain MST region. An IST is a special MSTI whose ID is 0.

InternationalElectrotechnicalCommission

The International Electrotechnical Commission (IEC) is an international and non-governmental standards organization dealing with electrical and electronic standards.

InternationalOrganization forStandardization

An international association that works to establish global standards for communicationsand information exchange. Primary among its accomplishments is the widely acceptedISO/OSI reference model, which defines standards for the interaction of computersconnected by communications networks.



766

InternationalTelecommunicationUnion-TelecommunicationStandardization Sector

An international body that develops worldwide standards for telecommunicationstechnologies. These standards are grouped together in series which are prefixed with aletter indicating the general subject and a number specifying the particular standard. Forexample, X.25 comes from the "X" series which deals with data networks and opensystem communications and number "25" deals with packet switched networks.

Internet ControlMessage Protocol

A network-layer (ISO/OSI level 3) Internet protocol that provides error correction andother information relevant to IP packet processing. For example, it can let the IP softwareon one machine inform another machine about an unreachable destination. See alsocommunications protocol, IP, ISO/OSI reference model, packet (definition 1).

Internet EngineeringTask Force

A worldwide organization of individuals interested in networking and the Internet.Managed by the Internet Engineering Steering Group (IESG), the IETF is charged withstudying technical problems facing the Internet and proposing solutions to the InternetArchitecture Board (IAB). The work of the IETF is carried out by various working groupsthat concentrate on specific topics, such as routing and security. The IETF is the publisherof the specifications that led to the TCP/IP protocol standard.

Internet GroupManagement Protocol

The protocol for managing the membership of Internet Protocol multicast groups amongthe TCP/IP protocols. It is used by IP hosts and adjacent multicast routers to establishand maintain multicast group memberships.

Internet Protocol The TCP/IP standard protocol that defines the IP packet as the unit of information sentacross an internet and provides the basis for connectionless, best-effort packet deliveryservice. IP includes the ICMP control and error message protocol as an integral part. Theentire protocol suite is often referred to as TCP/IP because TCP and IP are the twofundamental protocols. IP is standardized in RFC 791.

Internet protocolversion 6

A update version of IPv4. It is also called IP Next Generation (IPng). The specificationsand standardizations provided by it are consistent with the Internet Engineering TaskForce (IETF). IPv6 is also called. It is a new version of the Internet Protocol, designedas the successor to IPv4. The difference between IPv6 and IPv4 is that an IPv4 addresshas 32 bits while an IPv6 address has 128 bits.

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). IPv6 is also called. It is a new version of the Internet Protocol, designedas the successor to IPv4. The difference between IPv6 and IPv4 is that an IPv4 addresshas 32 bits while an IPv6 address has 128 bits.

inverse multiplexingover ATM

The ATM inverse multiplexing technique involves inverse multiplexing and de-multiplexing of ATM cells in a cyclical fashion among links grouped to form a higherbandwidth logical link whose rate is approximately the sum of the link rates. This isreferred to as an IMA group.

IP See Internet Protocol

IPV6 See Internet protocol version 6

IPv6 See Internet protocol version 6

IS-IS See Intermediate System to Intermediate System routing protocol

ISO See International Organization for Standardization

IST See internal spanning tree

ITU-T See International Telecommunication Union-Telecommunication StandardizationSector



767

J

Jitter Short waveform variations caused by vibration, voltage fluctuations, and control systeminstability.

I.4 K-OThis section provides the terms starting with letters K to 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 Basic element of MPLS network. All LSRs support the MPLS protocol. The LSR iscomposed of two parts: control unit and forwarding unit. The former is responsible forallocating the label, selecting the route, creating the label forwarding table, creating andremoving the label switch path; the latter forwards the labels according to groupsreceived in the label forwarding table.

LACP See Link Aggregation Control Protocol

LAG See link aggregation group

LAN See local area network

LAN See local area network

LAPS link access protocol-SDH

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 achieved by Layer 2 switching technologies in the packetswitched (IP/MPLS) network.

LB See loopback

LCAS See link capacity adjustment scheme

LCT local craft terminal

line rate The maximum packet forwarding capacity on a cable. The value of line rate equals themaximum transmission rate capable on a given type of media.

line rate forwarding The line rate equals the maximum transmission rate capable on a given type of media.

Link AggregationControl Protocol

A method of bundling a group of physical interfaces together as a logical interface toincrease bandwidth and reliability. For related protocols and standards, refer to IEEE802.3ad.



768

link aggregation group An aggregation that allows one or more links to be aggregated together to form a linkaggregation group so that a MAC client can treat the link aggregation group as if it werea single link.

link capacityadjustment scheme

LCAS in the virtual concatenation source and sink adaptation functions provides acontrol mechanism to hitlessly increase or decrease the capacity of a link to meet thebandwidth needs of the application. It also provides a means of removing member linksthat have experienced failure. The LCAS assumes that in cases of capacity initiation,increases or decreases, the construction or destruction of the end-to-end path is theresponsibility of the Network and Element Management Systems.

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

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.

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.

LP lower order path

LPT link-state pass through

LSP See label switched path



769

LSR See label switching router

M

MA See maintenance association

MAC See media access control

MAC See media access control

MADM multiple add/drop multiplexer

main topology A interface that displays the connection relationships of NEs on the NMS (screendisplay). The default client interface of the NMS, a basic component of the human-machine interactive interface. The topology clearly shows the structure of the network,the alarms of different NEs, subnets in the network, the communication status as well asthe basic network operation status. All topology management functions are accessedhere.

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 network or the part of the network for which connectivity is managed by CFM. Thedevices 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 switch Switches normal traffic signal to the protection section, unless a failure condition existson other sections (including the protection section) or an equal or higher priority switchcommand is in effect, by issuing a manual switch request for that normal traffic signal.

maximum transmissionunit

The largest packet of data that can be transmitted on a network. MTU size varies,depending on the network—576 bytes on X.25 networks, for example, 1500 bytes onEthernet, and 17,914 bytes on 16 Mbps Token Ring. Responsibility for determining thesize of the MTU lies with the link layer of the network. When packets are transmittedacross networks, the path MTU, or PMTU, represents the smallest packet size (the onethat all networks can transmit without breaking up the packet) among the networksinvolved.

MBS maximum burst size

MCF See message communication function

MD See maintenance domain

MDI See medium dependent interface

Mean Time BetweenFailures

The average time between consecutive failures of a piece of equipment. It is a measureof the reliability of the system.

Mean Time To Repair The average time that a device will take to recover from a failure.



770

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.

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 dependentinterface

The electrical and mechanical interface between the equipment and the mediatransmission.

MEP See maintenance association end point

MEP maintenance 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

mounting ear A piece of angle plate with holes in it on a rack. It is used to fix network elements orcomponents.

MP See maintenance point

MPID maintenance point identification

MPLS See Multiprotocol Label Switching

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 See multiprotocol label switching traffic engineering



771

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

MSTP See Multiple Spanning Tree Protocol

MTBF See Mean Time Between Failures

MTTR See Mean Time To Repair

MTU See maximum transmission unit

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 Protocol

Multiple spanning tree protocol. The MSTP can be used in a loop network. Using analgorithm, the MSTP blocks redundant paths so that the loop network can be trimmedas a tree network. In this case, the proliferation and endless cycling of packets is avoidedin the loop network. The protocol that introduces the mapping between VLANs andmultiple spanning trees. This solves the problem that data cannot be normally forwardedin a VLAN because in STP/RSTP, only one spanning tree corresponds to all the VLANs.

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

Multiprotocol LabelSwitching

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.

multiprotocol labelswitching trafficengineering

N/A

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 NMS, which is used to manage thetelecommunication equipment. In the NE Explorer, the user can query, manage andmaintain the NE, boards, and ports on a per-NE basis.



772

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 and communication(SCC) board whichmanages and monitors the entire network element. The NE software runs on the SCCboard.

Network ManagementSystem

A system in charge of the operation, administration, and maintenance 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

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

NNI See network to network interface

node A node stands for a managed device in the network. For a device with a single frame,one node stands for one device. For a device with multiple frames, one node stands forone frame 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

O

OAM See operation, administration and maintenance

ODF See optical distribution frame

ODU See outdoor unit

OM Operation and maintenance

One-to-One Backup A local repair method in which a backup tunnel is separately created for each protectedtunnel at a PLR.

open shortest path first 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.



773

Open SystemsInterconnection

A framework of ISO standards for communication between different systems made bydifferent vendors, in which the communications process is organized into seven differentcategories that are placed in a layered sequence based on their relationship to the user.Each layer uses the layer immediately below it and provides a service to the layer above.Layers 7 through 4 deal with end-to-end communication between the message sourceand destination, and layers 3 through 1 deal with network functions.

operation,administration andmaintenance

A group of network support functions that monitor and sustain segment operation,activities that are concerned with, but not limited to, failure detection, notification,location, and repairs that are intended to eliminate faults and keep a segment in anoperational state and support activities required to provide the services of a subscriberaccess network to users/subscribers.

optic 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 an optical source(or a detector).+

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

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 a port to an output port withoutchanging the structure of the signals.

Output optical power The ranger of optical energy level of output signals.

I.5 P-TThis section provides the terms starting with letters P to T.

P

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 A performance resource object defined in the network management system. The left endof a path is a device node whose port needs to be specified and the right end of a path isa certain IP address which can be configured by the user. By defining a path in thenetwork management system, a user can test the performance of a network path betweena device port and an IP address. The tested performance may be the path delay, packetloss ratio or other aspects.

PBS See peak burst size

PCB See printed circuit board



774

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 See protocol data unit

PE See provider edge

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 A traffic parameter, expressed in bit/s, whose value should be not less than the committedinformation 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 IETF Diff-Serv workgroup defines forwarding behaviors of network nodes as per-hopbehaviors (PHB), such as, traffic scheduling and policing. A device in the network shouldselect the proper PHB behaviors, based on the value of DSCP. At present, the IETFdefines four types of PHB. They are class selector (CS), expedited forwarding (EF),assured forwarding (AF), and best-effort (BE).

PHB See per-hop behavior

PHP See penultimate hop popping

PIR See peak information rate

PLA physical link aggregation

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.

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

PQ See priority queue

PRBS See pseudo random binary sequence

PRC primary reference clock



775

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.

priority queue An abstract data type in computer programming that supports the following threeoperations: (1) InsertWithPriority: add an element to the queue with an associatedpriority (2) GetNext: remove the element from the queue that has the highest priority,and return it (also known as "PopElement(Off)", or "GetMinimum") (3) PeekAtNext(optional): look at the element with highest priority without removing it

protection groundcable

A cable which connects the equipment and the protection ground bar. Usually, one halfof 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 data unit It is a data packet at the network layer of the OSI model.

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 random binarysequence

A sequence that is random in a sense that the value of an element is independent of thevalues of any of the other elements, similar to real random sequences.

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 wire emulationedge-to-edge

A type of end-to-end Layer 2 transmitting technology. It emulates the essential attributesof a telecommunication service such as ATM, FR or Ethernet in a Packet SwitchedNetwork (PSN). PWE3 also emulates the essential attributes of low speed Time DivisionMultiplexed (TDM) circuit and SONET/SDH. The simulation approximates to the realsituation.

PSN See packet switched network

PTN packet transport network

PW See pseudo wire

PWE3 See pseudo wire emulation edge-to-edge

Q

QinQ A layer 2 tunnel protocol based on IEEE 802.1Q encapsulation. It encapsulates the tagof the user's private virtual local area network (VLAN) into the tag of the public VLAN.The packet carries two layers of tags to travel through the backbone network of thecarrier. In this manner, the layer 2 virtual private network (VPN) is provided for the user.

QoS See quality of service

QPSK See quadrature phase shift keying

quadrature phase shiftkeying

A modulation method of data transmission through the conversion or modulation andthe phase determination of the reference signals (carrier). It is also called the fourth periodor 4-phase PSK or 4-PSK. QPSK uses four dots in the star diagram. The four dots areevenly distributed on a circle. On these phases, each QPSK character can perform two-bit coding and display the codes in Gray code on graph with the minimum BER.



776

quality of service A commonly-used performance indicator of a telecommunication system or channel.Depending on the specific system and service, it may relate to jitter, delay, packet lossratio, bit error ratio, and signal-to-noise ratio. It functions to measure the quality of thetransmission system and the effectiveness of the services, as well as the capability of aservice provider to meet the demands of users.

R

radio frequency 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 in the RNS which is in charge of controlling the use and the integrity of theradio resources.

random early detection 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 signal level The signal level at a receiver input terminal.

Received SignalStrength Indicator

The received wide band power, including thermal noise and noise generated in thereceiver, within the bandwidth defined by the receiver pulse shaping filter, for TDDwithin a specified timeslot. The reference point for the measurement shall be the antenna

Receiver Sensitivity Receiver sensitivity is defined as the minimum acceptable value of average receivedpower at point R to achieve a 1 x 10-12 BER (The FEC is open).

RED See random early detection

Reed-Solomon-Code A forward error correction code located before interleaving that enables correction oferrors induced by burst noise. Widely used error correction scheme to fight transmissionerrors at the receiver site.

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

Request For Comments A document in which a standard, a protocol, or other information pertaining to theoperation of the Internet is published. The RFC is actually issued, under the control ofthe IAB, after discussion and serves as the standard. RFCs can be obtained from sourcessuch as InterNIC.



777

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 frequency

RFC See Request For Comments

RIP See Routing Information Protocol

RMON remote network monitoring

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

route table A mapping table that stores the relationship between the original address, destinationaddress, short message (SM) protocol type and account. The SMSC delivers an SM tothe designated account according to the information set in the route table.

Routing InformationProtocol

A simple routing protocol that is part of the TCP/IP protocol suite. It determines a routebased on the smallest hop count between source and destination. RIP is a distance vectorprotocol that routinely broadcasts routing information to its neighboring routers and isknown 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.

RSL See 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

SEMF See synchronous equipment management function



778

service level agreement A service contract between a customer and a service provider that specifies theforwarding service a customer should receive. A customer may be a user organization(source domain) or another differentiated services domain (upstream domain). A SLAmay include traffic conditioning rules which constitute a traffic conditioning agreementas a whole or partially.

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

severely errored second A one-second period which has a bit error ratio ≥ X 10-3 or at least one defect. Timeinterval of one second during which a given digital signal is received with an error ratiogreater than 1 X 10 -3 (Rec. ITU R F. 592 needs correction).

SF See signal fail

SFP See small form-factor pluggable

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 E1 cable, network cable, and other non-subscribersignal cable.

signal fail A signal that indicates the associated data has failed in the sense that a near-end defectcondition (non-degrade defect) is active.

signal to noise ratio The ratio of the amplitude of the desired signal to the amplitude of noise signals at agiven point in time. SNR is expressed as 10 times the logarithm of the power ratio andis 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 Designating or pertaining to a method of operation in which information can betransmitted in either direction, but not simultaneously, between two points.

SLA See service level agreement

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



779

SNCP See subnetwork connection protection

SNMP See Simple Network Management Protocol

SNR See signal to noise ratio

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 STP is a protocol that is used in the LAN to remove the loop. STP applies to the redundantnetwork to block some undesirable redundant paths through certain algorithms and prunea 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 See synchronous transport mode-1

STM-N See synchronous transport module of order N

STP See Spanning Tree Protocol

sub-network Sub-network is the logical entity in the transmission network and comprises a group ofnetwork management objects. The network that consists of a group of interconnected orcorrelated NEs, according to different functions. For example, protection subnet, clocksubnet and so on. A sub-network can contain NEs and other sub-networks. Generally, asub-network is used to contain the equipment located in adjacent regions and closelyrelated with one another, and it is indicated with a sub-network icon on a topologicalview. The U2000 supports multilevels of sub-networks. A sub-network planning canbetter the organization of a network view. On the one hand, the view space can be saved,on the other hand, it helps the network management personnel focus on the equipmentunder 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.

subnetwork connection A "transport entity" that transfers information across a subnetwork, it is formed by theassociation of "ports" on the boundary of the subnetwork.

subnetwork connectionprotection

A function, which allows a working subnetwork connection to be replaced by a protectionsubnetwork connection if the working subnetwork connection fails, or if its performancefalls below a required level.

SVC See static virtual circuit

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.



780

Synchronization StatusMessage

A message that carries quality levels of timing signals on a synchronous timing link.Nodes on an SDH network and a synchronization network acquire upstream clockinformation through this message. Then the nodes can perform proper operations on theirclocks, such as tracing, switching, or converting to holdoff, and forward thesynchronization information to downstream nodes.

synchronous digitalhierarchy

A transmission scheme that follows ITU-T G.707, G.708, and G.709. It defines thetransmission 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 used only for signals. SDH is suitablefor the fiber communication system with high speed and a large capacity since it usessynchronous multiplexing and flexible mapping structure.

synchronousequipmentmanagement function

The SEMF converts performance data and implementation specific hardware alarms intoobject-oriented messages for transmission over DCCs and/or a Q interface.

synchronous transportmode-1

Synchronous Transfer Mode at 155 Mbit/s.

SynchronousTransport Module

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.

synchronous transportmodule of order N

A STM-N is the information structure used to support section layer connections in SDH.See ITU-T Recommendation G. 707 for STM modules of order 1, 4, 16 and 64.

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 Transmission Control Protocol

TDM See time division multiplexing

TE See traffic engineering

TEDB See traffic engineering database

TelecommunicationManagement Network

A protocol model defined by ITU-T for managing open systems in a communicationsnetwork. An architecture for management, including planning, provisioning, installation,maintenance, operation and administration of telecommunications equipment, networksand services.



781

TIM trace identifier mismatch

time divisionmultiplexing

A multiplexing technology. TDM divides the sampling cycle of a channel into time slots(TSn, n=0, 1, 2, 3, ...), and the sampling value codes of multiple signals engross timeslots in a certain order, forming multiple multiplexing digital signals to be transmittedover one channel.

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 technology that is used to dynamically monitor the traffic of the network and the loadof the network elements, to adjust in real time the parameters such as traffic managementparameters, route parameters and resource restriction parameters, and to optimize theutilization of network resources. The purpose is to prevent the congestion caused byunbalanced loads.

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.

Transmission ControlProtocol

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.



782

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.

I.6 U-ZThis section provides the terms starting with letters U to Z.

U

U-VLAN A VLAN attribute indicating that the current VLAN is a user VLAN of an M-VLAN.Multicast services are copied from the M-VLAN to the user VLAN.

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.

upload An operation to report some or all configuration data of an NE to the NMS(NetworkManagement system). The configuration data then covers the configuration data storedat the NMS side.

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. Therefore, 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 The interface between user equipment and private or public network equipment (forexample, ATM switches).

V

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 container



783

VCC See virtual channel connection

VCG See virtual concatenation group

VCI See virtual channel identifier

VCTRUNK A virtual concatenation group applied in data service mapping, also called the internalport of a data service processing board

virtual channelconnection

The VC logical trail that carries data between two end points in an ATM network. Alogical grouping of multiple virtual channel connections into one virtual connection.

virtual channelidentifier

A 16-bit field in the header of an ATM cell. The VCI, together with the VPI, is used toidentify the next destination of a cell as it passes through a series of ATM switches onits way to its destination.

virtual concatenationgroup

A group of co-located member trail termination functions that are connected to the samevirtual concatenation link

virtual container The information structure used to support path layer connections in the SDH. It consistsof information payload and path Overhead (POH) information fields organized in a blockframe structure which repeats every 125 or 500 μs.

virtual local areanetwork

A logical grouping of two or more nodes which are not necessarily on the same physicalnetwork segment but which share the same IP network number. This is often associatedwith switched Ethernet.

virtual path identifier The field in the Asynchronous Transfer Mode (ATM) cell header that identifies to whichvirtual 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 private network A system configuration, where the subscriber is able to build a private network viaconnections to different network switches that may include private network capabilities.

virtual route forward VRF performs the function of establishing multiple virtual routing devices on one actualrouting device. That is, the L3 interfaces of the device are distributed to different VRFs,performing the function of establishing multiple virtual route forwarding instances onthe device.

virtual user-networkinterface

A virtual user-network interface, works as an action point to perform serviceclassification and traffic control in HQoS.

VLAN See virtual local area network

voice over IP An IP telephony term for a set of facilities used to manage the delivery of voiceinformation over the Internet. VoIP involves sending voice information in a digital formin discrete packets rather than by using the traditional circuit-committed protocols of thepublic switched telephone network (PSTN).

VoIP See voice over IP

VPI See virtual path identifier

VPLS See virtual private LAN service

VPN See virtual private network

VRF See virtual route forward



784

W

wait to restore The number of minutes to wait before services are switched back to the working line.

WAN See wide area network

Web LCT The local maintenance terminal of a transport network, which is located on the NEmanagement layer of the transport network

weighted fair queuing A fair queue scheduling algorithm based on bandwidth allocation weights. Thisscheduling algorithm allocates the total bandwidth of an interface to queues, accordingto their weights and schedules the queues cyclically. In this manner, packets of all priorityqueues can be scheduled.

weighted random earlydetection

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.

weighted round Robin N/A

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.

WRED See weighted random early detection

WRR See weighted round Robin

WTR See wait to restore

X

XPIC See cross polarization interference cancellation



785

Documents

RTN_910_Maintenance_Guide(U2000)-(V100R003C03_01)