RTN 950 V100R005C00 Maintenance Guide 03

OptiX RTN 950 Radio Transmission System V100R005C00
Maintenance Guide
Issue Date 03 2012-07-30
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2012. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

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

Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China http://www.huawei.com support@huawei.com
Website: Email:
Issue 03 (2012-07-30)
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.
OptiX RTN 950 Radio Transmission System Maintenance Guide
About This Document
About This Document
Related Versions
The following table lists the product versions related to this document. Product Name OptiX RTN 950 iManager U2000 Version V100R005C00 V100R006C02
Intended Audience
This document provides the guidelines to maintaining the OptiX RTN 950. It also describes the alarms and performance events that are required for troubleshooting during the maintenance. This document is intended for: l l l Network planning engineer Data configuration engineer System maintenance engineer
Symbol Conventions
The symbols that may be found in this document are defined as follows. Symbol Description Indicates a hazard with a high level of risk, which if not avoided, will result in death or serious injury. Indicates a hazard with a medium or low level of risk, which if not avoided, could result in minor or moderate injury.
Issue 03 (2012-07-30)
ii
About This Document
Symbol
Description Indicates a potentially hazardous situation, which if not avoided, could result in equipment damage, data loss, performance degradation, or unexpected results. Indicates a tip that may help you solve a problem or save time. Provides additional information to emphasize or supplement important points of the main text.
General Conventions
The general conventions that may be found in this document are defined as follows. Convention Times New Roman Boldface Italic Courier New Description Normal paragraphs are in Times New Roman. Names of files, directories, folders, and users are in boldface. For example, log in as user root. Book titles are in italics. Examples of information displayed on the screen are in Courier New.
Command Conventions
The command conventions that may be found in this document are defined as follows. Convention Boldface Italic [] { x | y | ... } [ x | y | ... ] Description The keywords of a command line are in boldface. Command arguments are in italics. Items (keywords or arguments) in brackets [ ] are optional. Optional items are grouped in braces and separated by vertical bars. One item is selected. Optional items are grouped in brackets and separated by vertical bars. One item is selected or no item is selected.
Issue 03 (2012-07-30)
iii
About This Document
Convention { x | y | ... }*
Description Optional items are grouped in braces and separated by vertical bars. A minimum of one item or a maximum of all items can be selected. Optional items are grouped in brackets and separated by vertical bars. Several items or no item can be selected.
[ x | y | ... ]*
GUI Conventions
The GUI conventions that may be found in this document are defined as follows. Convention Boldface > Description Buttons, menus, parameters, tabs, window, and dialog titles are in boldface. For example, click OK. Multi-level menus are in boldface and separated by the ">" signs. For example, choose File > Create > Folder.
Change History
Updates between document issues are cumulative. Therefore, the latest document issue contains all updates made in previous issues.
Updates in Issue 03 (2012-07-30) Based on Product Version V100R005C00

This document is the third issue of the V100R005C00 product version. Update 8.9.1 Performing a PRBS Test for the Tributary Board 8.9.2 Performing a PRBS Test for the IF Board 8.9.3 Performing a PRBS Test for the Smart E1 Processing Board Description Added the operation of saving report.

This document is the second issue of the V100R005C00 product version.
Issue 03 (2012-07-30)
iv
About This Document
Update 3 Routine Maintenance 4 Emergency Maintenance 5 Troubleshooting 7 Database Backup and Restoration 8 Supporting Task A.2 Alarm List (Classified by Logical Boards)
Description Added the routine maintenance. Added the emergency maintenance. Added the troubleshooting. Added the database backup and restoration. Added the supporting task. Added the SSL_CERT_NOENC alarm to the system control, switching, and timing boards. Added the ERPS_IN_PROTECTION alarm to the Ethernet boards and IF boards (except for IF1).

This document is the first issue of the V100R005C00 product version.
Issue 03 (2012-07-30)
Contents
Contents
About This Document.....................................................................................................................ii 1 Safety Precautions.........................................................................................................................1
1.1 General Safety Precautions.................................................................................................................................2 1.2 Warning and Safety Symbols.............................................................................................................................3 1.3 Electrical Safety..................................................................................................................................................4 1.4 Environment of Flammable Gas.........................................................................................................................7 1.5 Storage Batteries.................................................................................................................................................7 1.6 Radiation.............................................................................................................................................................9 1.6.1 Safe Usage of Optical Fibers.....................................................................................................................9 1.6.2 Electromagnetic Exposure.......................................................................................................................11 1.6.3 Forbidden Areas......................................................................................................................................11 1.6.4 Laser........................................................................................................................................................11 1.6.5 Microwave...............................................................................................................................................12 1.7 Working at Heights...........................................................................................................................................13 1.7.1 Hoisting Heavy Objects...........................................................................................................................13 1.7.2 Using Ladders..........................................................................................................................................14 1.8 Mechanical Safety............................................................................................................................................16 1.9 Other Precautions.............................................................................................................................................17
2 Notices for High-Risk Operations...........................................................................................19

2.1 Operation Guide for the Toggle Lever Switch.................................................................................................20 2.2 Operation Guide for the IF Jumper...................................................................................................................22 2.3 Operation Guide for the IF Cables...................................................................................................................23 2.4 Operation Guide for the IF Board.....................................................................................................................24
3 Routine Maintenance..................................................................................................................26 4 Emergency Maintenance............................................................................................................28

4.1 Definition of Emergency..................................................................................................................................29 4.2 Purposes of Emergency Maintenance...............................................................................................................29 4.3 Procedure for Emergency Maintenance............................................................................................................29
5 Troubleshooting..........................................................................................................................36
5.1 General Troubleshooting Procedure.................................................................................................................38 5.2 Troubleshooting Service Interruptions.............................................................................................................40 Issue 03 (2012-07-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. vi
Contents
5.3 Troubleshooting the Radio Link.......................................................................................................................46 5.4 Troubleshooting Bit Errors in TDM Services..................................................................................................51 5.5 Troubleshooting Pointer Justifications.............................................................................................................57 5.6 Troubleshooting the Interconnection with SDH Equipment............................................................................61 5.7 Troubleshooting the Interconnection with PDH Equipment............................................................................64 5.8 Troubleshooting Native Ethernet Service Faults..............................................................................................68 5.9 Troubleshooting Ethernet Service on the EoS/EoPDH Plane..........................................................................75 5.10 Troubleshooting MPLS Tunnels....................................................................................................................81 5.11 Troubleshooting CES Services.......................................................................................................................85 5.12 Troubleshooting ATM Services.....................................................................................................................90 5.13 Troubleshooting Ethernet Services Carried by PWs......................................................................................94 5.14 Troubleshooting Orderwire Faults................................................................................................................102
6 Part Replacement.......................................................................................................................105
6.1 Removing a Board..........................................................................................................................................107 6.2 Inserting a Board............................................................................................................................................110 6.3 Replacing the SDH Optical Interface Board..................................................................................................112 6.4 Replacing the Channelized STM-1 Processing Board...................................................................................113 6.5 Replacing the PDH Interface Board...............................................................................................................114 6.6 Replacing the Smart E1 Interface Board........................................................................................................115 6.7 Replacing the Ethernet Interface Board..........................................................................................................116 6.8 Replacing the IF Board...................................................................................................................................117 6.9 Replacing the CF Card...................................................................................................................................119 6.10 Replacing the System Control, Switch and Timing Board...........................................................................120 6.11 Replacing the Auxiliary Board.....................................................................................................................122 6.12 Replacing the Fan Board..............................................................................................................................123 6.13 Replacing the Power Board..........................................................................................................................125 6.14 Replacing the SFP........................................................................................................................................126 6.15 Replacing the ODU......................................................................................................................................128 6.16 Replacing the IF Cable.................................................................................................................................129
7 Database Backup and Restoration.........................................................................................131

7.1 NE Database...................................................................................................................................................132 7.2 Backing Up the Database Manually...............................................................................................................133 7.3 Setting the Database Backup Policy...............................................................................................................135 7.3.1 Setting the User-Defined Backup Policy...............................................................................................135 7.3.2 Enable the Backup Policy of the Device...............................................................................................137 7.3.3 Disable the Backup Policy of the Device..............................................................................................138 7.4 Restoring the Database by NMS....................................................................................................................139
8 Supporting Task........................................................................................................................142
8.1 Hardware Loopback.......................................................................................................................................145 8.2 Cleaning Fiber Connectors and Adapters.......................................................................................................145 8.2.1 Cleaning Fiber Connectors by Using Cartridge Cleaners.....................................................................145 Issue 03 (2012-07-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. vii
Contents
8.2.2 Cleaning Fiber Connectors by Using Lens Tissue................................................................................147 8.2.3 Cleaning Fiber Adapters by Using Optical Cleaning Sticks.................................................................148 8.3 Browsing Alarms, Abnormal Events, and Performance Events.....................................................................149 8.3.1 Checking the NE Status.........................................................................................................................149 8.3.2 Checking the Board Status....................................................................................................................151 8.3.3 Browsing Current Alarms......................................................................................................................151 8.3.4 Browsing Current Performance Events of the radio link.......................................................................154 8.3.5 Browsing Historical Performance Data of a Radio Link.......................................................................155 8.3.6 Browsing Current Ethernet Performance..............................................................................................156 8.3.7 Browsing Historical Ethernet Performance Data..................................................................................159 8.3.8 Browsing Abnormal Events...................................................................................................................163 8.3.9 Browsing Current Performance Events.................................................................................................164 8.3.10 Browsing History Alarms....................................................................................................................165 8.3.11 Browsing History Performance Events...............................................................................................167 8.3.12 Browsing the Performance Event Threshold-Crossing Records.........................................................168 8.3.13 Browsing UAT Events.........................................................................................................................169 8.4 Using the RMON............................................................................................................................................170 8.4.1 Browsing Current Ethernet Performance..............................................................................................170 8.4.2 Configuring Ethernet Performance Threshold-Crossing Parameters....................................................173 8.4.3 Configuring the Parameters for Monitoring Historical Ethernet Performance.....................................176 8.4.4 Browsing Historical Ethernet Performance Data..................................................................................177 8.5 Setting Alarm and Performance Management Functions...............................................................................180 8.5.1 Configuring the Performance Monitoring Status of NEs......................................................................180 8.5.2 Setting Severity and Auto Reporting Status of Alarms.........................................................................181 8.5.3 Suppressing Alarms for Monitored Objects..........................................................................................182 8.5.4 Suppressing Alarms for NEs.................................................................................................................183 8.5.5 Reversing Alarms for Service Ports......................................................................................................184 8.5.6 Setting Trigger Conditions of AIS Insertion.........................................................................................185 8.5.7 Setting Trigger Conditions of UNEQ Insertion.....................................................................................186 8.5.8 Setting Bit Error Thresholds for Service Ports......................................................................................187 8.5.9 Setting Monitoring and Auto-Report Status of Performance Events....................................................188 8.5.10 Setting Performance Thresholds..........................................................................................................189 8.5.11 Resetting Performance Registers.........................................................................................................190 8.6 Querying a Report..........................................................................................................................................190 8.6.1 Querying the Board Information Report ..............................................................................................191 8.6.2 Querying the Board Manufacturing Information Report ......................................................................193 8.6.3 Querying the Microwave Link Information Report...............................................................................194 8.6.4 Querying the Network-wide License Report.........................................................................................195 8.7 Software Loopback.........................................................................................................................................196 8.7.1 Setting Loopback for the SDH Optical Interface Board........................................................................196 8.7.2 Setting Loopback for the Channelized STM-1 Processing Board.........................................................198 8.7.3 Setting Loopback for the Tributary Board............................................................................................200 Issue 03 (2012-07-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. viii
Contents
8.7.4 Setting a Loopback for the Smart E1 Processing Board.......................................................................202 8.7.5 Setting a Loopback for the Packet-plane Ethernet Interface Board......................................................203 8.7.6 Setting Loopbacks for the EOS/EoPDH-Plane Ethernet Interface Board.............................................205 8.7.7 Setting Loopback for the IF Board........................................................................................................208 8.7.8 Setting Software Loopback for the NE..................................................................................................211 8.7.9 Setting Software Loopback for the Microwave Link............................................................................212 8.7.10 Locating a Fault by Performing Loopback Operations.......................................................................213 8.8 Reset...............................................................................................................................................................214 8.8.1 Cold Reset..............................................................................................................................................214 8.8.2 Warm Reset...........................................................................................................................................215 8.9 PRBS Test.......................................................................................................................................................216 8.9.1 Performing a PRBS Test for the Tributary Board.................................................................................216 8.9.2 Performing a PRBS Test for the IF Board.............................................................................................218 8.9.3 Performing a PRBS Test for the Smart E1 Processing Board...............................................................220 8.10 Querying the License Capacity.....................................................................................................................222 8.11 Scanning Interfering Signals........................................................................................................................222 8.12 Setting the On/Off State of the Laser...........................................................................................................223 8.13 Setting the ALS Function.............................................................................................................................224 8.14 Setting the Automatic Release Function......................................................................................................225 8.15 Querying Power Consumption of Boards.....................................................................................................225 8.16 Querying the Impedance of an E1 Channel..................................................................................................226 8.17 Monitoring Ethernet Packets Through Port Mirroring.................................................................................226 8.18 Querying the Attributes of an Ethernet Port.................................................................................................228 8.19 Setting Traffic, Physical Bandwidth, or Bandwidth Utilization of Ethernet Ports.......................................229 8.20 Querying Traffic, Physical Bandwidth, or Bandwidth Utilization...............................................................230 8.21 Setting the Threshold of Received Traffic Flow on an Ethernet Port..........................................................231 8.22 Using the Ethernet Test Frames....................................................................................................................232 8.23 Switching the System Control Unit and the Cross-Connect Unit................................................................233 8.24 Using IP Ping Commands to Locate Ethernet Service Faults......................................................................234 8.25 End-to-End Management on Fibers, Tunnels, and PWE3 Services.............................................................237 8.25.1 Expanding/Collapsing Fibers and Cables............................................................................................237 8.25.2 Querying Optical Power of Fibers and Cables....................................................................................238 8.25.3 Querying the Radio Link Information.................................................................................................239 8.25.4 Querying the Radio Link Performance................................................................................................239 8.25.5 Managing E-Line Services Transmitted in Native Ethernet Mode.....................................................240 8.25.6 Managing MPLS Tunnels in an End-to-End Mode.............................................................................241 8.25.7 Managing and Maintaining PWE3 Services........................................................................................241 8.25.8 Verifying Native Ethernet Services.....................................................................................................242 8.25.9 Verifying MPLS Tunnels in an End-to-End Mode.............................................................................244 8.25.10 Verifying PW Configurations in an End-to-End Mode.....................................................................246 8.25.11 Verifying PW-Based E-Line Service Configurations (in an End-to-End Mode)..............................248 8.25.12 Performing Intelligent Service Fault Diagnosis for Ethernet Services..............................................251 Issue 03 (2012-07-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. ix
Contents
A Alarm Reference.......................................................................................................................253
A.1 Alarm List (in Alphabetical Order)...............................................................................................................254 A.2 Alarm List (Classified by Logical Boards)....................................................................................................276 A.2.1 CST.......................................................................................................................................................278 A.2.2 CSH.......................................................................................................................................................278 A.2.3 IF1.........................................................................................................................................................280 A.2.4 IFU2......................................................................................................................................................280 A.2.5 IFX2......................................................................................................................................................281 A.2.6 SL1D/SL1DA.......................................................................................................................................282 A.2.7 EM6T....................................................................................................................................................282 A.2.8 EM6TA.................................................................................................................................................283 A.2.9 EM6F....................................................................................................................................................283 A.2.10 EM6FA...............................................................................................................................................284 A.2.11 EFP8...................................................................................................................................................284 A.2.12 EMS6..................................................................................................................................................285 A.2.13 SP3S/SP3D.........................................................................................................................................286 A.2.14 AUX....................................................................................................................................................286 A.2.15 PIU......................................................................................................................................................286 A.2.16 FAN....................................................................................................................................................286 A.2.17 ISU2....................................................................................................................................................286 A.2.18 ISX2....................................................................................................................................................287 A.2.19 ML1/MD1...........................................................................................................................................288 A.2.20 ODU....................................................................................................................................................289 A.2.21 PMU....................................................................................................................................................289 A.2.22 TCU....................................................................................................................................................289 A.2.23 CQ1.....................................................................................................................................................290 A.2.24 ISV3....................................................................................................................................................290 A.2.25 EG4.....................................................................................................................................................291 A.2.26 EG4P...................................................................................................................................................292 A.3 Alarms and Handling Procedures..................................................................................................................292 A.3.1 A_LOC.................................................................................................................................................292 A.3.2 ACR_LOCK_FAIL..............................................................................................................................293 A.3.3 ALM_E1RAI........................................................................................................................................295 A.3.4 ALM_GFP_dCSF.................................................................................................................................295 A.3.5 ALM_GFP_dLFD.................................................................................................................................296 A.3.6 ALM_IMA_LIF....................................................................................................................................298 A.3.7 ALM_IMA_LODS...............................................................................................................................299 A.3.8 ALM_IMA_RE_RX_UNUSABLE......................................................................................................300 A.3.9 ALM_IMA_RE_TX_UNUSABLE......................................................................................................302 A.3.10 ALM_IMA_RFI.................................................................................................................................303 A.3.11 AM_DOWNSHIFT............................................................................................................................305 A.3.12 APS_FAIL..........................................................................................................................................306 Issue 03 (2012-07-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. x
Contents
A.3.13 APS_INDI...........................................................................................................................................307 A.3.14 APS_MANUAL_STOP......................................................................................................................308 A.3.15 ATMPW_UNKNOWNCELL_EXC..................................................................................................309 A.3.16 AU_AIS..............................................................................................................................................310 A.3.17 AU_LOP.............................................................................................................................................311 A.3.18 B1_EXC..............................................................................................................................................312 A.3.19 B1_SD.................................................................................................................................................314 A.3.20 B2_EXC..............................................................................................................................................317 A.3.21 B2_SD.................................................................................................................................................319 A.3.22 B3_EXC..............................................................................................................................................321 A.3.23 B3_EXC_VC3....................................................................................................................................323 A.3.24 B3_SD.................................................................................................................................................325 A.3.25 B3_SD_VC3.......................................................................................................................................327 A.3.26 BAT1TEMP_SENSOR_FAIL...........................................................................................................330 A.3.27 BAT2TEMP_SENSOR_FAIL...........................................................................................................331 A.3.28 BD_NOT_INSTALLED.....................................................................................................................332 A.3.29 BD_STATUS......................................................................................................................................333 A.3.30 BDTEMP_SENSOR_FAIL................................................................................................................335 A.3.31 BIOS_STATUS..................................................................................................................................336 A.3.32 BIP_EXC............................................................................................................................................337 A.3.33 BIP_SD...............................................................................................................................................338 A.3.34 BOOTROM_BAD..............................................................................................................................340 A.3.35 BUS_ERR...........................................................................................................................................341 A.3.36 CES_ACR_LOCK_ABN...................................................................................................................343 A.3.37 CES_APS_INDI.................................................................................................................................345 A.3.38 CES_APS_MANUAL_STOP............................................................................................................347 A.3.39 CES_JTROVR_EXC..........................................................................................................................348 A.3.40 CES_JTRUDR_EXC..........................................................................................................................349 A.3.41 CES_K1_K2_M..................................................................................................................................350 A.3.42 CES_K2_M.........................................................................................................................................351 A.3.43 CES_LOSPKT_EXC..........................................................................................................................352 A.3.44 CES_MALPKT_EXC.........................................................................................................................353 A.3.45 CES_MISORDERPKT_EXC.............................................................................................................354 A.3.46 CES_RDI............................................................................................................................................355 A.3.47 CES_STRAYPKT_EXC....................................................................................................................356 A.3.48 CESPW_OPPOSITE_ACFAULT......................................................................................................357 A.3.49 CESPW_OPPOSITE_RAI.................................................................................................................358 A.3.50 CFCARD_FAILED............................................................................................................................358 A.3.51 CFCARD_OFFLINE..........................................................................................................................359 A.3.52 CHCS..................................................................................................................................................361 A.3.53 CLK_LOCK_FAIL.............................................................................................................................362 A.3.54 CLK_NO_TRACE_MODE................................................................................................................364 Issue 03 (2012-07-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xi
Contents
A.3.55 COMMUN_FAIL...............................................................................................................................365 A.3.56 COM_EXTECC_FULL......................................................................................................................367 A.3.57 CONFIG_NOSUPPORT....................................................................................................................368 A.3.58 DBMS_DELETE................................................................................................................................370 A.3.59 DBMS_ERROR..................................................................................................................................370 A.3.60 DBMS_PROTECT_MODE...............................................................................................................371 A.3.61 DCNSIZE_OVER...............................................................................................................................372 A.3.62 DDN_LFA..........................................................................................................................................373 A.3.63 DOWN_E1_AIS.................................................................................................................................374 A.3.64 DROPRATIO_OVER.........................................................................................................................375 A.3.65 E1_LOC..............................................................................................................................................376 A.3.66 E1_LOS..............................................................................................................................................377 A.3.67 ENVHUM_SENSOR_FAIL...............................................................................................................379 A.3.68 ENVTEMP_SENSOR_FAIL.............................................................................................................380 A.3.69 ENVTEMP1_SENSOR_FAIL...........................................................................................................381 A.3.70 ENVTEMP2_SENSOR_FAIL...........................................................................................................382 A.3.71 ERPS_IN_PROTECTION..................................................................................................................383 A.3.72 ETH_APS_LOST...............................................................................................................................385 A.3.73 ETH_APS_PATH_MISMATCH.......................................................................................................386 A.3.74 ETH_APS_SWITCH_FAIL...............................................................................................................387 A.3.75 ETH_APS_TYPE_MISMATCH........................................................................................................388 A.3.76 ETH_CFM_AIS..................................................................................................................................389 A.3.77 ETH_CFM_LOC................................................................................................................................390 A.3.78 ETH_CFM_MISMERGE...................................................................................................................393 A.3.79 ETH_CFM_RDI.................................................................................................................................396 A.3.80 ETH_CFM_UNEXPERI....................................................................................................................398 A.3.81 ETH_EFM_DF...................................................................................................................................401 A.3.82 ETH_EFM_EVENT...........................................................................................................................402 A.3.83 ETH_EFM_LOOPBACK...................................................................................................................403 A.3.84 ETH_EFM_REMFAULT...................................................................................................................404 A.3.85 ETH_LOS...........................................................................................................................................405 A.3.86 ETH_NO_FLOW...............................................................................................................................406 A.3.87 ETH_PWR_SUPPLY_FAIL..............................................................................................................408 A.3.88 ETHOAM_DISCOVER_FAIL..........................................................................................................409 A.3.89 ETHOAM_RMT_CRIT_FAULT.......................................................................................................410 A.3.90 ETHOAM_RMT_LOOP....................................................................................................................411 A.3.91 ETHOAM_RMT_SD.........................................................................................................................413 A.3.92 ETHOAM_SELF_LOOP...................................................................................................................414 A.3.93 ETHOAM_VCG_SELF_LOOP.........................................................................................................416 A.3.94 EX_ETHOAM_CC_LOS...................................................................................................................417 A.3.95 EX_ETHOAM_MPID_CNFLCT.......................................................................................................419 A.3.96 EXT_SYNC_LOS..............................................................................................................................420 Issue 03 (2012-07-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xii
Contents
A.3.97 EXT_TIME_LOC...............................................................................................................................421 A.3.98 FAN_AGING.....................................................................................................................................422 A.3.99 FAN_FAIL.........................................................................................................................................423 A.3.100 FCS_ERR.........................................................................................................................................424 A.3.101 FLOW_OVER..................................................................................................................................426 A.3.102 HARD_BAD.....................................................................................................................................427 A.3.103 HARD_NONSUPPORT...................................................................................................................428 A.3.104 HP_CROSSTR.................................................................................................................................429 A.3.105 HP_LOM..........................................................................................................................................431 A.3.106 HP_RDI............................................................................................................................................432 A.3.107 HP_REI.............................................................................................................................................432 A.3.108 HP_SLM...........................................................................................................................................433 A.3.109 HP_TIM............................................................................................................................................434 A.3.110 HP_UNEQ........................................................................................................................................435 A.3.111 HPAD_CROSSTR............................................................................................................................436 A.3.112 IF_CABLE_OPEN...........................................................................................................................437 A.3.113 IF_INPWR_ABN.............................................................................................................................438 A.3.114 IF_MODE_UNSUPPORTED..........................................................................................................440 A.3.115 IMA_GROUP_LE_DOWN..............................................................................................................441 A.3.116 IMA_GROUP_RE_DOWN.............................................................................................................442 A.3.117 IMA_TXCLK_MISMATCH............................................................................................................443 A.3.118 IN_PWR_ABN.................................................................................................................................444 A.3.119 IN_PWR_HIGH...............................................................................................................................446 A.3.120 IN_PWR_LOW................................................................................................................................447 A.3.121 INTEMP_SENSOR_FAIL...............................................................................................................449 A.3.122 J0_MM..............................................................................................................................................450 A.3.123 K1_K2_M.........................................................................................................................................451 A.3.124 K2_M................................................................................................................................................452 A.3.125 LAG_BWMM...................................................................................................................................454 A.3.126 LAG_DOWN....................................................................................................................................455 A.3.127 LAG_MEMBER_DOWN................................................................................................................455 A.3.128 LAG_PORT_FAIL...........................................................................................................................457 A.3.129 LAG_VC_PORT_FAIL...................................................................................................................459 A.3.130 LAN_LOC........................................................................................................................................461 A.3.131 LASER_CLOSED............................................................................................................................462 A.3.132 LASER_MOD_ERR.........................................................................................................................463 A.3.133 LASER_MOD_ERR_EX.................................................................................................................464 A.3.134 LASER_SHUT.................................................................................................................................466 A.3.135 LCAS_FOPR....................................................................................................................................467 A.3.136 LCAS_FOPT....................................................................................................................................468 A.3.137 LCAS_PLCR....................................................................................................................................470 A.3.138 LCAS_PLCT....................................................................................................................................471 Issue 03 (2012-07-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xiii
Contents
A.3.139 LCAS_TLCR....................................................................................................................................473 A.3.140 LCAS_TLCT....................................................................................................................................474 A.3.141 LCD..................................................................................................................................................475 A.3.142 LCS_LIMITED.................................................................................................................................477 A.3.143 LFA...................................................................................................................................................479 A.3.144 LICENSE_LOST..............................................................................................................................481 A.3.145 LINK_ERR.......................................................................................................................................482 A.3.146 LMFA...............................................................................................................................................483 A.3.147 LOOP_ALM.....................................................................................................................................484 A.3.148 LP_CROSSTR..................................................................................................................................487 A.3.149 LP_R_FIFO......................................................................................................................................488 A.3.150 LP_RDI.............................................................................................................................................489 A.3.151 LP_RDI_VC12.................................................................................................................................490 A.3.152 LP_RDI_VC3...................................................................................................................................491 A.3.153 LP_REI.............................................................................................................................................492 A.3.154 LP_REI_VC12..................................................................................................................................493 A.3.155 LP_REI_VC3....................................................................................................................................494 A.3.156 LP_RFI.............................................................................................................................................495 A.3.157 LP_SLM...........................................................................................................................................495 A.3.158 LP_SLM_VC12................................................................................................................................496 A.3.159 LP_SLM_VC3..................................................................................................................................497 A.3.160 LP_T_FIFO.......................................................................................................................................498 A.3.161 LP_TIM............................................................................................................................................499 A.3.162 LP_TIM_VC12.................................................................................................................................500 A.3.163 LP_TIM_VC3...................................................................................................................................501 A.3.164 LP_UNEQ.........................................................................................................................................503 A.3.165 LP_UNEQ_VC12.............................................................................................................................504 A.3.166 LP_UNEQ_VC3...............................................................................................................................505 A.3.167 LPS_UNI_BI_M...............................................................................................................................506 A.3.168 LPT_CFG_CLOSEPORT.................................................................................................................507 A.3.169 LPT_INEFFECT...............................................................................................................................508 A.3.170 LPT_RFI...........................................................................................................................................510 A.3.171 LSR_BCM_ALM.............................................................................................................................511 A.3.172 LSR_NO_FITED..............................................................................................................................512 A.3.173 LSR_WILL_DIE..............................................................................................................................513 A.3.174 LTI....................................................................................................................................................514 A.3.175 MAC_EXT_EXC.............................................................................................................................515 A.3.176 MAC_FCS_EXC..............................................................................................................................517 A.3.177 MOD_COM_FAIL...........................................................................................................................518 A.3.178 MOD_TYPE_MISMATCH.............................................................................................................519 A.3.179 MP_DELAY.....................................................................................................................................520 A.3.180 MP_DOWN......................................................................................................................................521 Issue 03 (2012-07-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xiv
Contents
A.3.181 MPLS_PW_AIS...............................................................................................................................523 A.3.182 MPLS_PW_BDI...............................................................................................................................524 A.3.183 MPLS_PW_Excess...........................................................................................................................525 A.3.184 MPLS_PW_LOCV...........................................................................................................................526 A.3.185 MPLS_PW_MISMATCH................................................................................................................528 A.3.186 MPLS_PW_MISMERGE.................................................................................................................529 A.3.187 MPLS_PW_OAMFAIL....................................................................................................................529 A.3.188 MPLS_PW_RDI...............................................................................................................................531 A.3.189 MPLS_PW_SD.................................................................................................................................531 A.3.190 MPLS_PW_SF.................................................................................................................................532 A.3.191 MPLS_PW_UNEXPMEG................................................................................................................533 A.3.192 MPLS_PW_UNEXPMEP................................................................................................................534 A.3.193 MPLS_PW_UNEXPPER.................................................................................................................535 A.3.194 MPLS_PW_UNKNOWN.................................................................................................................536 A.3.195 MPLS_TUNNEL_AIS.....................................................................................................................537 A.3.196 MPLS_TUNNEL_BDI.....................................................................................................................537 A.3.197 MPLS_TUNNEL_Excess.................................................................................................................538 A.3.198 MPLS_TUNNEL_FDI.....................................................................................................................539 A.3.199 MPLS_TUNNEL_LOCV.................................................................................................................540 A.3.200 MPLS_TUNNEL_MISMATCH......................................................................................................541 A.3.201 MPLS_TUNNEL_MISMERGE.......................................................................................................542 A.3.202 MPLS_TUNNEL_OAMFAIL..........................................................................................................543 A.3.203 MPLS_TUNNEL_RDI.....................................................................................................................544 A.3.204 MPLS_TUNNEL_SD.......................................................................................................................545 A.3.205 MPLS_TUNNEL_SF.......................................................................................................................546 A.3.206 MPLS_TUNNEL_UNEXPMEG......................................................................................................547 A.3.207 MPLS_TUNNEL_UNEXPMEP......................................................................................................548 A.3.208 MPLS_TUNNEL_UNEXPPER.......................................................................................................549 A.3.209 MPLS_TUNNEL_UNKNOWN.......................................................................................................549 A.3.210 MS_AIS............................................................................................................................................550 A.3.211 MS_CROSSTR.................................................................................................................................552 A.3.212 MS_RDI............................................................................................................................................553 A.3.213 MS_REI............................................................................................................................................554 A.3.214 MSAD_CROSSTR...........................................................................................................................555 A.3.215 MULTI_RPL_OWNER....................................................................................................................556 A.3.216 MW_AM_TEST...............................................................................................................................557 A.3.217 MW_BER_EXC...............................................................................................................................558 A.3.218 MW_BER_SD..................................................................................................................................561 A.3.219 MW_CFG_MISMATCH..................................................................................................................565 A.3.220 MW_CONT_WAVE........................................................................................................................566 A.3.221 MW_E1_LOST.................................................................................................................................567 A.3.222 MW_FEC_UNCOR..........................................................................................................................568 Issue 03 (2012-07-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xv
Contents
A.3.223 MW_LIM..........................................................................................................................................571 A.3.224 MW_LOF.........................................................................................................................................573 A.3.225 MW_RDI..........................................................................................................................................578 A.3.226 NESF_LOST.....................................................................................................................................579 A.3.227 NESOFT_MM..................................................................................................................................581 A.3.228 NO_BD_SOFT.................................................................................................................................584 A.3.229 NP1_MANUAL_STOP....................................................................................................................585 A.3.230 NP1_SW_FAIL................................................................................................................................586 A.3.231 NP1_SW_INDI.................................................................................................................................587 A.3.232 NTP_SYNC_FAIL...........................................................................................................................588 A.3.233 OCD..................................................................................................................................................589 A.3.234 ODC_BATTERY_CURRENT_ABN..............................................................................................590 A.3.235 ODC_BATTERY_PWRDOWN......................................................................................................592 A.3.236 ODC_DOOR_OPEN........................................................................................................................594 A.3.237 ODC_FAN_FAILED........................................................................................................................596 A.3.238 ODC_HUMI_ABN...........................................................................................................................597 A.3.239 ODC_LOAD_PWRDOWN..............................................................................................................598 A.3.240 ODC_MDL_ABN.............................................................................................................................601 A.3.241 ODC_POWER_FAIL.......................................................................................................................603 A.3.242 ODC_SMOKE_OVER.....................................................................................................................605 A.3.243 ODC_SURGE_PROTECTION_FAIL.............................................................................................606 A.3.244 ODC_TEC_ALM.............................................................................................................................608 A.3.245 ODC_TEMP_ABN...........................................................................................................................609 A.3.246 ODC_WATER_ALM.......................................................................................................................611 A.3.247 OUT_PWR_ABN.............................................................................................................................612 A.3.248 OUT1TEMP_SENSOR_FAIL.........................................................................................................614 A.3.249 OUT2TEMP_SENSOR_FAIL.........................................................................................................615 A.3.250 PASSWORD_NEED_CHANGE.....................................................................................................616 A.3.251 PATCH_ACT_TIMEOUT...............................................................................................................617 A.3.252 PATCH_DEACT_TIMEOUT..........................................................................................................618 A.3.253 PATCH_PKGERR...........................................................................................................................618 A.3.254 PG_LINK_FAIL...............................................................................................................................619 A.3.255 PG_PRT_DEGRADED....................................................................................................................620 A.3.256 PLA_CFG_MISMATCH.................................................................................................................621 A.3.257 PORTMODE_MISMATCH.............................................................................................................622 A.3.258 PORT_EXC_TRAFFIC....................................................................................................................623 A.3.259 PORT_MODULE_OFFLINE...........................................................................................................625 A.3.260 POWER_ABNORMAL...................................................................................................................626 A.3.261 POWER_ALM.................................................................................................................................627 A.3.262 PPP_LCP_FAIL...............................................................................................................................628 A.3.263 PPP_NCP_FAIL...............................................................................................................................630 A.3.264 PTP_SOURCE_SWITCH................................................................................................................630 Issue 03 (2012-07-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xvi
Contents
A.3.265 PTP_TIMESTAMP_ABN................................................................................................................632 A.3.266 PW_DROPPKT_EXC......................................................................................................................633 A.3.267 PW_NO_TRAFFIC..........................................................................................................................634 A.3.268 PWAPS_LOST.................................................................................................................................635 A.3.269 PWAPS_PATH_MISMATCH.........................................................................................................636 A.3.270 PWAPS_SWITCH_FAIL.................................................................................................................637 A.3.271 PWAPS_TYPE_MISMATCH.........................................................................................................638 A.3.272 R_LOC..............................................................................................................................................639 A.3.273 R_LOF..............................................................................................................................................640 A.3.274 R_LOS..............................................................................................................................................642 A.3.275 R_OOF..............................................................................................................................................644 A.3.276 RADIO_FADING_MARGIN_INSUFF...........................................................................................646 A.3.277 RADIO_MUTE................................................................................................................................647 A.3.278 RADIO_RSL_BEYONDTH............................................................................................................648 A.3.279 RADIO_RSL_HIGH........................................................................................................................649 A.3.280 RADIO_RSL_LOW.........................................................................................................................650 A.3.281 RADIO_TSL_HIGH.........................................................................................................................652 A.3.282 RADIO_TSL_LOW.........................................................................................................................652 A.3.283 RELAY_ALARM_CRITICAL........................................................................................................653 A.3.284 RELAY_ALARM_IGNORE...........................................................................................................654 A.3.285 RELAY_ALARM_MAJOR.............................................................................................................655 A.3.286 RELAY_ALARM_MINOR.............................................................................................................655 A.3.287 RMFA...............................................................................................................................................656 A.3.288 RPS_INDI.........................................................................................................................................657 A.3.289 RS_CROSSTR..................................................................................................................................659 A.3.290 RTC_FAIL........................................................................................................................................661 A.3.291 S1_SYN_CHANGE.........................................................................................................................661 A.3.292 SCCDATA_BACKUP_FAIL...........................................................................................................663 A.3.293 SEC_RADIUS_FAIL.......................................................................................................................664 A.3.294 SECU_ALM.....................................................................................................................................665 A.3.295 SRV_SHUTDOWN_LD..................................................................................................................666 A.3.296 SSL_CERT_NOENC.......................................................................................................................667 A.3.297 SWDL_ACTIVATED_TIMEOUT..................................................................................................668 A.3.298 SWDL_AUTOMATCH_INH..........................................................................................................669 A.3.299 SWDL_CHGMNG_NOMATCH.....................................................................................................669 A.3.300 SWDL_COMMIT_FAIL..................................................................................................................670 A.3.301 SWDL_INPROCESS.......................................................................................................................671 A.3.302 SWDL_NEPKGCHECK..................................................................................................................672 A.3.303 SWDL_PKG_NOBDSOFT..............................................................................................................673 A.3.304 SWDL_PKGVER_MM....................................................................................................................673 A.3.305 SWDL_ROLLBACK_FAIL.............................................................................................................674 A.3.306 SYN_BAD........................................................................................................................................675 Issue 03 (2012-07-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xvii
Contents
A.3.307 SYNC_C_LOS.................................................................................................................................676 A.3.308 SYSLOG_COMM_FAIL.................................................................................................................677 A.3.309 T_ALOS...........................................................................................................................................678 A.3.310 T_LOC..............................................................................................................................................679 A.3.311 TEM_HA..........................................................................................................................................680 A.3.312 TEM_LA...........................................................................................................................................681 A.3.313 TEMP_ALARM...............................................................................................................................682 A.3.314 TEMP_OVER...................................................................................................................................683 A.3.315 TF......................................................................................................................................................684 A.3.316 THUNDERALM..............................................................................................................................685 A.3.317 TIME_LOCK_FAIL.........................................................................................................................686 A.3.318 TIME_NO_TRACE_MODE............................................................................................................687 A.3.319 TR_LOC...........................................................................................................................................688 A.3.320 TU_AIS.............................................................................................................................................690 A.3.321 TU_AIS_VC12.................................................................................................................................691 A.3.322 TU_AIS_VC3...................................................................................................................................693 A.3.323 TU_LOP...........................................................................................................................................695 A.3.324 TU_LOP_VC12................................................................................................................................696 A.3.325 TU_LOP_VC3..................................................................................................................................697 A.3.326 TUNNEL_APS_DEGRADED.........................................................................................................699 A.3.327 UHCS................................................................................................................................................700 A.3.328 UP_E1_AIS......................................................................................................................................701 A.3.329 V5_VCAIS.......................................................................................................................................702 A.3.330 VC_AIS............................................................................................................................................703 A.3.331 VC_LOC...........................................................................................................................................705 A.3.332 VC_RDI............................................................................................................................................706 A.3.333 VCAT_LOA.....................................................................................................................................708 A.3.334 VCAT_LOM_VC12.........................................................................................................................709 A.3.335 VCAT_LOM_VC3...........................................................................................................................711 A.3.336 VCAT_SQM_VC12.........................................................................................................................712 A.3.337 VCAT_SQM_VC3...........................................................................................................................714 A.3.338 VOLT_LOS......................................................................................................................................715 A.3.339 VP_AIS.............................................................................................................................................716 A.3.340 VP_LOC...........................................................................................................................................718 A.3.341 VP_RDI............................................................................................................................................720 A.3.342 W_R_FAIL.......................................................................................................................................722 A.3.343 WRG_BD_TYPE.............................................................................................................................723 A.3.344 XPIC_LOS........................................................................................................................................723
B Abnormal Event Reference.....................................................................................................726

B.1 Major Abnormal Events List.........................................................................................................................727 B.2 Abnormal Events and Handling Procedures..................................................................................................727 B.2.1 IF 1+1 Protection Switching.................................................................................................................727 Issue 03 (2012-07-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xviii
Contents
B.2.2 N+1 Protection Switching.....................................................................................................................729 B.2.3 SNCP Switching...................................................................................................................................731 B.2.4 Linear MSP Switching..........................................................................................................................733 B.2.5 Status Change of an APS Protection Group.........................................................................................735 B.2.6 Reporting of PW APS Switching Events..............................................................................................737 B.2.7 System Control Board Switching..........................................................................................................738 B.2.8 RMON Performance Value Below the Lower Limit............................................................................740 B.2.9 RMON Performance Value Above the Upper Limit............................................................................741
C Performance Event Reference................................................................................................742

C.1 Performance Events (by Event Type)............................................................................................................743 C.1.1 SDH/PDH Performance Event List......................................................................................................743 C.1.2 Radio Performance Events....................................................................................................................747 C.1.3 Other Performance Events....................................................................................................................750 C.2 Performance Events (by Logical Board)........................................................................................................751 C.2.1 CST/CSH..............................................................................................................................................752 C.2.2 IF1.........................................................................................................................................................754 C.2.3 IFU2/ISU2.............................................................................................................................................756 C.2.4 IFX2/ISX2.............................................................................................................................................760 C.2.5 SL1D/SL1DA.......................................................................................................................................764 C.2.6 EM6T....................................................................................................................................................766 C.2.7 EM6TA.................................................................................................................................................767 C.2.8 EM6F....................................................................................................................................................767 C.2.9 EM6FA.................................................................................................................................................768 C.2.10 EFP8....................................................................................................................................................768 C.2.11 EMS6..................................................................................................................................................769 C.2.12 SP3S/SP3D.........................................................................................................................................771 C.2.13 ML1/MD1...........................................................................................................................................772 C.2.14 ODU....................................................................................................................................................773 C.2.15 CQ1.....................................................................................................................................................774 C.2.16 ISV3....................................................................................................................................................777 C.2.17 EG4/EG4P...........................................................................................................................................780 C.3 Performance Events and Handling Procedures..............................................................................................781 C.3.1 AUPJCHIGH, AUPJCLOW, and AUPJCNEW...................................................................................781 C.3.2 TUPJCHIGH, TUPJCLOW, and TUPJCNEW....................................................................................782 C.3.3 RSBBE, RSES, RSSES, RSCSES, and RSUAS..................................................................................783 C.3.4 RSOOF and RSOFS..............................................................................................................................785 C.3.5 MSBBE, MSES, MSSES, MSCSES, and MSUAS..............................................................................786 C.3.6 MSFEBBE, MSFEES, MSFESES, MSFECSES, and MSFEUAS.......................................................787 C.3.7 HPBBE, HPES, HPSES, HPCSES, and HPUAS.................................................................................788 C.3.8 HPFEBBE, HPFEES, HPFESES, HPFECSES, and HPFEUAS..........................................................789 C.3.9 IF_BBE, IF_ES, IF_SES, IF_CSES, and IF_UAS...............................................................................790 C.3.10 LPBBE, LPES, LPSES, LPCSES, and LPUAS..................................................................................792 Issue 03 (2012-07-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xix
Contents
C.3.11 LPFEBBE, LPFEES, LPFESES, LPFECSES, and LPFEUAS..........................................................793 C.3.12 E1_LCV_SDH, E1_LLOSS_SDH, E1_LES_SDH, and E1_LSES_SDH.........................................794 C.3.13 TSL_MAX, TSL_MIN, TSL_CUR, and TSL_AVG.........................................................................795 C.3.14 RSL_MAX, RSL_MIN, RSL_CUR, and RSL_AVG........................................................................796 C.3.15 FEC_BEF_COR_ER, FEC_COR_BYTE_CNT and FEC_UNCOR_BLOCK_CNT........................796 C.3.16 QPSKWS, QPSK_S_WS, QAMWS16, QAM_S_WS16, QAMWS32, QAMWS64, QAMWS128, QAMWS256, QAMWS512, QAM_L_WS512, QAMWS1024, and QAM_L_WS1024..............................797 C.3.17 ATPC_P_ADJUST and ATPC_N_ADJUST.....................................................................................798 C.3.18 AMDOWNCNT and AMUPCNT......................................................................................................799 C.3.19 RLHTT, RLLTT, TLHTT, TLLTT....................................................................................................800 C.3.20 TPLMAX, TPLMIN, and TPLCUR...................................................................................................800 C.3.21 RPLMAX, RPLMIN, and RPLCUR..................................................................................................801 C.3.22 BDTEMPMAX, BDTEMPMIN, and BDTEMPCUR........................................................................802 C.3.23 XPIC_XPD_VALUE..........................................................................................................................802 C.3.24 PG_IF_BBE, PG_IF_ES, PG_IF_SES, PG_IF_CSES, and PG_IF_UAS..........................................803 C.3.25 E1_BBE, E1_ES, E1_SES, E1_CSES, and E1_UAS.........................................................................804 C.3.26 IF_SNR_MAX, IF_SNR_MIN, and IF_SNR_AVG..........................................................................806 C.3.27 OSPITMPMAX, OSPITMPMIN, and OSPITMPCUR......................................................................806 C.3.28 MAXMEANPATHDELAY, MINMEANPATHDELAY, and AVGMEANPATHDELAY.............807 C.3.29 MAXPHASEOFFSET, MINPHASEOFFSET, and AVGPHASEOFFSET.......................................808 C.3.30 CURPOSITIVEPDV and CURNEGATIVEPDV..............................................................................808 C.3.31 MAXPOSITIVEDELAY, MINPOSITIVEDELAY, and AVGPOSITIVEDELAY..........................809 C.3.32 MAXFREQDEV, MINFREQDEV, and AVGFREQDEV.................................................................810 C.3.33 MPLS_PW_LS, MPLS_PW_SLS, MPLS_PW_CSLS, and MPLS_PW_UAS.................................810 C.3.34 TLBMAX, TLBMIN, and TLBCUR..................................................................................................811
D RMON Event Reference..........................................................................................................812

D.1 List of RMON Alarm Entries........................................................................................................................813 D.2 List of RMON Performance Entries on the Packet-Plane.............................................................................816 D.3 List of RMON Performance Entries on the EoS/EoPDH Plane....................................................................842 D.4 RMON Events and Handling Procedures......................................................................................................850 D.4.1 ETHDROP............................................................................................................................................850 D.4.2 ETHEXCCOL.......................................................................................................................................851 D.4.3 ETHLATECOL....................................................................................................................................852 D.4.4 RXBBAD..............................................................................................................................................853 D.4.5 TXDEFFRM.........................................................................................................................................854 D.4.6 ETHUNDER.........................................................................................................................................855 D.4.7 ETHOVER............................................................................................................................................855 D.4.8 ETHFRG...............................................................................................................................................856 D.4.9 ETHJAB...............................................................................................................................................857 D.4.10 ETHCOL.............................................................................................................................................858 D.4.11 ETHFCS.............................................................................................................................................858 D.4.12 ATMPW_LOSPKTS..........................................................................................................................859 Issue 03 (2012-07-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xx
Contents
D.4.13 ATMPW_MISORDERPKTS.............................................................................................................860 D.4.14 ATMPW_UNKNOWNCELLS..........................................................................................................861 D.4.15 ATM_CORRECTED_HCSERR........................................................................................................861 D.4.16 ATM_UNCORRECTED_HCSERR..................................................................................................862 D.4.17 CES_MISORDERPKTS.....................................................................................................................863 D.4.18 CES_STRAYPKTS............................................................................................................................863 D.4.19 CES_MALPKTS................................................................................................................................864 D.4.20 CES_JTRUDR....................................................................................................................................865 D.4.21 CES_JTROVR....................................................................................................................................865 D.4.22 CES_LOSPKTS..................................................................................................................................866
E Alarm Management..................................................................................................................868
E.1 NE Alarm Management.................................................................................................................................869 E.2 Board Alarm Management.............................................................................................................................869 E.2.1 Setting the Alarm Severity....................................................................................................................869 E.2.2 Alarm Suppression................................................................................................................................869 E.2.3 Alarm Auto-Report...............................................................................................................................869 E.2.4 Alarm Reversion...................................................................................................................................870 E.2.5 Setting of the Bit Error Alarm Threshold.............................................................................................870 E.2.6 AIS Insertion.........................................................................................................................................871 E.2.7 UNEQ Insertion....................................................................................................................................872
F Performance Event Management...........................................................................................873

F.1 NE Performance Event Management.............................................................................................................874 F.2 Board Performance Event Management.........................................................................................................874
G Alarm Suppression Relationship..........................................................................................875 H Indicators of Boards.................................................................................................................879 I Glossary.......................................................................................................................................900
Issue 03 (2012-07-30)
xxi
1 Safety Precautions
1
About This Chapter
Safety Precautions
This topic describes the safety precautions that you must follow when installing, operating, and maintaining Huawei devices. 1.1 General Safety Precautions This topic describes essential safety precautions that instruct you in the selection of measuring and testing instruments when you install, operate, and maintain Huawei devices. 1.2 Warning and Safety Symbols Before using the equipment, note the following warning and safety symbols on the equipment. 1.3 Electrical Safety This topic describes safety precautions for high voltage, lightning strikes, high leakage current, power cables, fuses, and ESD. 1.4 Environment of Flammable Gas This topic describes safety precautions for the operating environment of a device. 1.5 Storage Batteries This topic describes safety precautions for operations of storage batteries. 1.6 Radiation This topic describes safety precautions for electromagnetic exposure and lasers. 1.7 Working at Heights This topic describes safety precautions for working at heights. 1.8 Mechanical Safety This topic describes safety precautions for drilling holes, handling sharp objects, operating fans, and carrying heavy objects. 1.9 Other Precautions This topic describes safety precautions for removing and inserting boards, binding signal cables, and routing cables.
Issue 03 (2012-07-30)
1.1 General Safety Precautions

This topic describes essential safety precautions that instruct you in the selection of measuring and testing instruments when you install, operate, and maintain Huawei devices.
All Safety Precautions

To ensure the safety of humans and a device, follow the marks on the device and all the safety precautions in this document when installing, operating, and maintaining a device. The "CAUTION", "WARNING", and "DANGER" marks in this document do not cover all the safety precautions that must be followed. They are supplements to the safety precautions.
Local Laws and Regulations

When operating a device, always comply with the local laws and regulations. The safety precautions provided in the documents are in addition/supplementary to the local laws and regulations.
Basic Installation Requirements

The installation and maintenance personnel of Huawei devices must receive strict training and be familiar with the proper operation methods and safety precautions before any operation. l l l l Only trained and qualified personnel are permitted to install, operate, and maintain a device. Only certified professionals are permitted to remove the safety facilities, and to troubleshoot and maintain the device. Only the personnel authenticated or authorized by Huawei are permitted to replace or change the device or parts of the device (including software). The operating personnel must immediately report the faults or errors that may cause safety problems to the person in charge.
Grounding Requirements
The grounding requirements are applicable to the device that needs to be grounded. l l l l When installing the device, always connect the grounding facilities first. When removing the device, always disconnect the grounding facilities last. Ensure that the grounding conductor is intact. Do not operate the device in the absence of a suitably installed grounding conductor. 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 properly grounded.
Human Safety
l l When there is a risk of a lightning strike, do not operate the fixed terminal or touch the cables. 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.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2
Issue 03 (2012-07-30)

NOTE
The preceding requirements apply to wireless fixed station terminals.
l l l
To avoid electric shocks, do not connect safety extra-low voltage (SELV) circuits to telephone-network voltage (TNV) circuits. Do not look into optical ports without eye protection. Otherwise, human eyes may be hurt by laser beams. Before operating the device, wear an ESD protective coat, ESD gloves, and an ESD wrist strap. In addition, you need to get off the conductive objects, such as jewelry and watches, to prevent electric shock and burn. In case of fire, escape from the building or site where the device is located and press the fire alarm bell or dial the telephone number for fire alarms. Do not enter the burning building again in any situation.
Device Safety
l l l l Before any operation, install the device firmly on the ground or other rigid objects, such as on a wall or in a rack. When the system is working, ensure that the ventilation hole is not blocked. When installing the front panel, use a tool to tighten the screws firmly, if required. After installing the device, clean up the packing materials.
1.2 Warning and Safety Symbols

Before using the equipment, note the following warning and safety symbols on the equipment. Table 1-1 lists the warning and safety symbols of the OptiX RTN 950 and their meanings. Table 1-1 Warning and safety symbols of the OptiX RTN 950 Symbol Indication This symbol is for ESD protection. A notice with this symbol indicates that you should wear an ES wrist strap or glove when you touch a board. Otherwise, you may cause damage to the board.
CLASS 1 LASER PRODUCT
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 may damage you eyes or skin.
LASER RADIATION
DO NOT VIEW DIRECTLY WITH OPTICAL INSTRUMENTS CLASS 1M LASER PRODUCT
Issue 03 (2012-07-30)
Symbol
Indication A notice with this symbol indicates where the subrack is grounded.
ATTENTION
CLEAN PERIODICALLY
A notice with this symbol indicates that the air filter should be cleaned periodically.
DON'T TOUCH THE FAN LEAVES BEFORE THEY SLOW DOWN !
This symbol is for fan safety. A notice with this symbol indicates that the fan leaves should not be touched when the fan is rotating.
1.3 Electrical Safety

This topic describes safety precautions for high voltage, lightning strikes, high leakage current, power cables, fuses, and ESD.
High Voltage
DANGER
l 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.
Thunderstorm
The requirements apply only to wireless base stations or devices with antennas and feeders.
DANGER
Do not perform operations on high voltage, AC power, towers, or backstays in stormy weather conditions.
Issue 03 (2012-07-30)
High Leakage Current
WARNING
Before powering on a device, ground the device. Otherwise, the safety of humans and the device cannot be ensured. If a high leakage current mark is labeled near the power connector of the device, you must connect the PGND terminal on the shell to the ground before connecting the device to an A/C input power supply. This is to prevent the electric shock caused by leakage current of the device.
Power Cables
DANGER
Do not install or remove the power cable with a live line. Transient contact between the core of the power cable and the conductor may generate electric arc or spark, which may cause fire or eye injury. l l Before installing or removing power cables, you must power off the device. Before connecting a power cable, you must ensure that the label on the power cable is correct.
Device with Power On
DANGER
Installing or removing a device is prohibited if the device is on.
DANGER
Do 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 in accordance with regulations to avoid short-circuits caused by metal objects.
Issue 03 (2012-07-30)
CAUTION
To avoid short-circuits when using a tool (such as a screwdriver), do not place the tool on the ventilation plate of the subrack.
CAUTION
Prevent any screws from dropping into the subrack or chassis to avoid short-circuits.
Fuse
WARNING
If the fuse on a device blows, replace the fuse with a fuse of the same type and specifications to ensure safe operation of the device.
Electrostatic Discharge
CAUTION
The static electricity generated by the human body may damage the electrostatic sensitive components 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 in the hand. Such static electromagnetic effects can remain for an appreciable time. Before operating a device, circuit boards, or ASICs, wear an ESD wrist strap that is properly grounded. The ESD wrist strap can prevent the electrostatic-sensitive components from being damaged by the static electricity in the human body.
Figure 1-1 shows the method of wearing an ESD wrist strap.
Issue 03 (2012-07-30)
Figure 1-1 Wearing an ESD wrist strap
1.4 Environment of Flammable Gas

This topic describes safety precautions for the operating environment of a device.
DANGER
Do 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 Batteries

This topic describes safety precautions for operations of storage batteries.
DANGER
Before operating a storage battery, you must read the safety precautions carefully and be familiar with the method of connecting a storage battery. l l l Incorrect operations of storage batteries cause hazards. During operation, prevent any shortcircuit, and prevent the electrolyte from overflowing or leakage. If the electrolyte overflows, it causes potential hazards to the device. The electrolyte may corrode metal parts and the circuit boards, and ultimately damage the circuit boards. A storage battery contains a great deal of energy. Misoperations may cause a short-circuit, which leads to human injuries.
Issue 03 (2012-07-30)
Basic Precautions
To ensure safety, note the following points before installing or maintaining the storage battery: l l l l l Use special insulation tools. Wear an eye protector and take effective protection measures. Wear rubber gloves and a protection coat to prevent the hazard caused by the overflowing electrolyte. When handling the storage battery, ensure that its electrodes are upward. Leaning or reversing the storage battery is prohibited. 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
DANGER
A battery short-circuit may cause human injuries. Although the voltage of an ordinary battery is 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 working battery before performing other operations.
Hazardous Gas
CAUTION
Do not use any unsealed lead-acid storage battery. Lay a storage battery horizontally and fix it properly to prevent the battery from emitting flammable gas, which may cause fire or device erosion. Working lead-acid storage batteries emit flammable gas. Therefore, ventilation and fireproofing measures must be taken at the sites where lead-acid storage batteries are placed.
Battery Temperature
CAUTION
If a battery overheats, the battery may be deformed or damaged, and the electrolyte may overflow. When the temperature of the battery is higher than 60C, you need to check whether the electrolyte overflows. If the electrolyte overflows, take appropriate measures immediately.
Issue 03 (2012-07-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 8
Battery Leakage
CAUTION
In 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. When you find the electrolyte leaks, you can use the following substances to counteract and absorb the leaking electrolyte: l l Sodium bicarbonate (NaHCO3) Sodium carbonate (Na2CO3)
In the event of acid overflow or spillage, neutralize the acid and clean it up as recommended by the battery manufacturer and any local regulations for acid disposal. If a person contacts battery electrolyte, clean the skin that contacts the battery electrolyte immediately by using water. In case of a severe situation, the person must be sent to a hospital immediately.
1.6 Radiation
This topic describes safety precautions for electromagnetic exposure and lasers.
1.6.1 Safe Usage of Optical Fibers

The laser beam can cause damage to your eyes. Hence, you must exercise caution when using optical fibers.
DANGER
When installing or maintaining an optical interface board or optical fibers, avoid direct eye exposure to the laser beams launched from the optical interface board or fiber connectors. The laser beam can cause damage to your eyes.
Cleaning Fiber Connectors and Optical Interfaces
CAUTION
If fiber connectors or flanges are contaminated, optical power commissioning is seriously affected. Therefore, the two endfaces and flange of every external fiber must be cleaned before the fiber is led into the equipment through the ODF for being inserted into an optical interface on the equipment.
Issue 03 (2012-07-30)
The fiber connectors and optical interfaces of the lasers must be cleaned with the following special cleaning tools and materials: l l l l l l Special cleaning solvent: It is preferred to use isoamylol. Propyl alcohol, however, can also be used. It is prohibited that you use alcohol and formalin. Non-woven lens tissue Special compressed gas Cotton stick (medical cotton or long fiber cotton) Special cleaning roll, used with the recommended cleaning solvent Special magnifier for fiber connectors
For cleaning steps, see Task Collection "Cleaning Fiber Connectors and Adapters" in the OptiX RTN 950 Radio Transmission System Maintenance and Troubleshooting.
Replacing Optical Fibers

When replacing an optical fiber, cover the fiber connector of the unused optical fiber with a protective cap.
Connecting Optical Fibers

l l l Use an attenuator if the optical power is excessively high. A high received optical power damages the optical interface. Directly connect an attenuator to a slanting optical interface. Install the attenuator on the IN port instead of the OUT port. Do not directly connect an attenuator to the level optical interface. Use the optical distribution 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 optical interface
Issue 03 (2012-07-30)
10
Figure 1-3 Level optical interface
Level optical interface
1.6.2 Electromagnetic Exposure

This topic describes safety precautions for electromagnetic exposure. If multiple transmit antennas are installed on a tower or backstay, keep away from the transmit directions of the antennas when you install or maintain an antenna locally.
CAUTION
Ensure that all personnel are beyond the transmit direction of a working antenna.
1.6.3 Forbidden Areas

The 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 10 meters away from the electromagnetic radiator, if in the transmit direction. A physical barrier and an eye-catching warning flag should be available in each forbidden area.
1.6.4 Laser
This topic describes safety precautions for lasers.
WARNING
When handling optical fibers, do not stand close to, or look into the optical fiber outlet directly without eye protection.
Issue 03 (2012-07-30)
11
Laser transceivers are used in the optical transmission system and associated test tools. The laser transmitted through the bare optical fiber produces a small beam of light, and therefore it has very high power density and is invisible to human eyes. When a beam of light enters eyes, the eyes may be damaged. In normal cases, viewing an un-terminated optical fiber or a damaged optical fiber without eye protection 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 view an un-terminated optical fiber.
Safety Instructions Regarding Lasers

To avoid laser radiation, obey the following instructions: l l l l l l l All operations should be performed by authorized personnel who have completed the required training courses. Wear a pair of eye-protective glasses when you are handling lasers or fibers. Ensure that the optical source is switched off before disconnecting optical fiber connectors. Do not look into the end of an exposed fiber or an open connector when you are not sure whether the optical source is switched off. Use an optical power meter to measure the optical power and ensure that the optical source is switched off. Before opening the front door of an optical transmission device, ensure that you are not exposed to laser radiation. Do not use an optical tool such as a microscope, a magnifying glass, or an eye loupe to view 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 l Only trained personnel are permitted to cut and splice fibers. Before cutting or splicing a fiber, ensure that the fiber is disconnected from the optical source. After disconnecting the fiber, cap to the fiber connectors.
1.6.5 Microwave
When installing and maintaining the equipment of Huawei, follow the safety precautions of microwave to ensure the safety of the human body and the equipment.
WARNING
Strong radio frequency can harm the human body. When installing or maintaining an aerial on the tower or mast that is installed with multiple aerials, switch off the transmitter in advance.
Issue 03 (2012-07-30)
12
1.7 Working at Heights

This topic describes safety precautions for working at heights.
WARNING
When working at heights, be cautious to prevent objects from falling down. The requirements for working at heights are as follows: l l l l l The personnel who work at heights must be trained. Carry and handle the operating machines and tools with caution to prevent them from falling down. Safety measures, such as wearing a helmet and a safety belt, must be taken. Wear cold-proof clothes when working at heights in cold areas. Check all lifting appliances thoroughly before starting the work, and ensure that they are intact.
1.7.1 Hoisting Heavy Objects

This topic describes the safety precautions for hoisting heavy objects that you must follow when installing, operating, and maintaining Huawei devices.
WARNING
When heavy objects are being hoisted, do not walk below the cantilever or hoisted objects. l l l l l Only trained and qualified personnel can perform hoisting operations. Before hoisting heavy objects, check that the hoisting tools are complete and in good condition. Before hoisting heavy objects, ensure that the hoisting tools are fixed to a secure object or wall with good weight-bearing capacity. Issue orders with short and explicit words to ensure correct operations. 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.
Issue 03 (2012-07-30)
13
Figure 1-4 Hoisting heavy objects
1.7.2 Using Ladders

This topic describes safety precautions for using ladders.
Checking Ladders
l l Before using a ladder, check whether the ladder is damaged. After checking that the ladder is in good condition, you can use the ladder. Before using a ladder, you should know the maximum weight capacity of the ladder. Avoid overweighing the ladder.
Placing Ladders
The proper slant angle of the ladder is 75 degrees. You can measure the slant angle of the ladder with an angle square or your arms, as shown in Figure 1-5. When using a ladder, to prevent the ladder from sliding, ensure that the wider feet of the ladder are downward, or take protection measures for the ladder feet. Ensure that the ladder is placed securely.
Issue 03 (2012-07-30)
14
Figure 1-5 Slanting a ladder
Climbing Up a Ladder
When climbing up a ladder, pay attention to the following points: l l l Ensure that the center of gravity of your body does not deviate from the edges of the two long sides. Before operations, ensure that your body is stable to reduce risks. 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 the roof, as shown in Figure 1-6. Figure 1-6 Ladder top being one meter higher than the roof
Issue 03 (2012-07-30)
15
1.8 Mechanical Safety

This topic describes safety precautions for drilling holes, handling sharp objects, operating fans, and carrying heavy objects.
Drilling Holes
WARNING
Do not drill holes on the cabinet without prior permission. Drilling holes without complying with the requirements affects the electromagnetic shielding performance of the cabinet and damages the cables inside the cabinet. In addition, if the scraps caused by drilling enter the cabinet, the printed circuit boards (PCBs) may be short-circuited. l l l l Before drilling a hole on the cabinet, remove the cables inside the cabinet. Wear an eye protector when drilling holes. This is to prevent eyes from being injured by the splashing metal scraps. Wear protection gloves when drilling holes. Take measures to prevent the metallic scraps from falling into the cabinet. After the drilling, clean up the metallic scraps.
Sharp Objects
WARNING
Wear protection gloves when carrying the device. This is to prevent hands from being injured by the sharp edges of the device.
Fans
l l 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. When replacing the parts near fans, keep your fingers or boards from touching operating fans before the fans are powered off and stop running. Otherwise, the hands or the boards are damaged.
Carrying Heavy Objects

Wear protection gloves when carrying heavy objects. This is to prevent hands from being hurt.
Issue 03 (2012-07-30)
16
WARNING
l 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, which may hurt you. l Generally, two persons are needed to carry a chassis. It is prohibited that only one person carries a heavy chassis. When carrying a chassis, the carriers should stretch their backs and move stably to avoid being strained. When moving or lifting a chassis, hold the handles or bottom of the chassis. Do not hold the handles of the modules installed in the chassis, such as the power modules, fan modules, and boards.
1.9 Other Precautions

This topic describes safety precautions for removing and inserting boards, binding signal cables, and routing cables.
Removing and Inserting a Board
CAUTION
When inserting a board, wear an ESD wrist strap or ESD gloves, and handle the board gently to avoid distorting pins on the backplane. l l l Slide the board along the guide rails. Do not contact one board with another to avoid short-circuits or damage. 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 to the electrostatic-sensitive components.
Binding Signal Cables
CAUTION
Bind the signal cables separately from the high-current or high-voltage cables.
Routing Cables
In the case of extremely low temperature, heavy shock or vibration may damage the plastic skin of the cables. To ensure the construction safety, comply with the following requirements:
l l
When installing cables, ensure that the environment temperature is above 0C. If the cables are stored in a place where the ambient temperature is below 0C, transfer them to a place at room temperature and store the cables for more than 24 hours before installation. Handle the cables gently, especially in a low-temperature environment. Do not perform any improper operations, for example, pushing the cables down directly from a truck.
High Temperature
WARNING
If the ambient temperature exceeds 55C, the temperature of the front panel surface marked the flag may exceed 70C. When touching the front panel of the board in such an environment, you must wear the protection gloves.
IF Cables
WARNING
Before installing or removing an IF cable, you must turn off the power switch of the IF board.
Issue 03 (2012-07-30)
18
2 Notices for High-Risk Operations
Notices for High-Risk Operations
About This Chapter

This topic provides notices for the operations that may cause bodily injury or equipment damage if they are not performed properly during the commissioning and maintenance of microwave equipment. 2.1 Operation Guide for the Toggle Lever Switch The ODU-PWR switch on the IF board is a toggle lever switch which must be turned on and off as per the following instructions to avoid damaging the IF board. 2.2 Operation Guide for the IF Jumper Before installing or removing IF jumpers, shut down the ODU power supply to prevent personal injuries and damaged to the IF boards or ODU. 2.3 Operation Guide for the IF Cables Before installing or removing IF cables, shut down the ODU power supply to prevent personal injuries and damaged to the IF boards or ODU. 2.4 Operation Guide for the IF Board Before removing or installing an IF board, turn off the ODU-PWR switch to avoid bodily injury or damage to the IF board and ODU.
Issue 03 (2012-07-30)
19
2.1 Operation Guide for the Toggle Lever Switch

The ODU-PWR switch on the IF board is a toggle lever switch which must be turned on and off as 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
O: OFF
I : ON
Turning On the Toggle Lever Switch

1. Gently pull on the toggle lever switch out.
Issue 03 (2012-07-30)
20
2.
Turn it to the left.
3.
Release the toggle lever switch.
Turning Off the Toggle Lever Switch

1. Gently pull on the toggle lever switch.
2.
Issue 03 (2012-07-30)
Turn it to the right.

3.
Release the toggle lever switch.
2.2 Operation Guide for the IF Jumper

Before installing or removing IF jumpers, shut down the ODU power supply to prevent personal injuries and damaged to the IF boards or ODU.
Procedure
Step 1 Follow instructions in 2.1 Operation Guide for the Toggle Lever Switch to power off the ODU.
Issue 03 (2012-07-30)
22
DANGER
Ensure 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 Cables

Before installing or removing IF cables, shut down the ODU power supply to prevent personal injuries and damaged to the IF boards or ODU.
Procedure
Step 1 Follow instructions in 2.1 Operation Guide for the Toggle Lever Switch to power off the ODU.
Issue 03 (2012-07-30)
23
DANGER
Ensure that the ODU is completely powered off before removing or installing the IF cable. Step 2 Install or remove the IF cables. ----End
2.4 Operation Guide for the IF Board

Before removing or installing an IF board, turn off the ODU-PWR switch to avoid bodily injury or 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 the Toggle Lever Switch.
Issue 03 (2012-07-30)
24
DANGER
Ensure 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
Issue 03 (2012-07-30)
25
3 Routine Maintenance
3
Maintenance Item
Routine Maintenance
Routine maintenance operations are performed to detect and rectify hidden faults before the hidden faults cause damage to equipment and affect services. Routine maintenance operations are preventive measures. For the , routine maintenance items are classified into routine maintenance items carried out on the network management system (NMS), field maintenance items for indoor equipment, and field maintenance items for outdoor equipment.
Routine Maintenance Items Carried Out on the NMS

Recomm ended Mainten ance Cycle Every day Every day Every week Every week Every week Every week Every week Remarks
Checking the NE Status Browsing Current Alarms Browsing History Alarms Browsing Abnormal Events Browsing Current Performance Events Browsing History Performance Events Browsing History Transmit Power and Receive Power
Issue 03 (2012-07-30)
26
3 Routine Maintenance
Maintenance Item
Recomm ended Mainten ance Cycle Half a year
Remarks
Testing IF 1+1 Switching
Applies only to the equipment that is configured in 1+1 protection mode. During the 1+1 protection switching, the protected services are interrupted. Hence, it is recommended that you perform the 1+1 protection switching when the traffic is light. Applies only to the equipment that is configured with N+1 protection.
Testing the IF N+1 Switching
Half a year
Field Maintenance Items for Indoor Equipment

Maintenance Item Checking the Telecommunications Room Maintaining the Environment of Outdoor Cabinets Recommended Maintenance Cycle Every two months Half a year Remarks -
Field Maintenance Items for Outdoor Equipment

Maintenance Item Recommended Maintenance Cycle Half a year Half a year Half a year Half a year Half a year Remarks
Checking the ODU Checking the Hybrid Coupler Checking the Antenna Checking the IF Cable Checking the LOS Condition
Carry out a complete check after a level-8 or higher hurricane, an earthquake, or other exceptional circumstances.
Issue 03 (2012-07-30)
27
4 Emergency Maintenance
4
About This Chapter
Emergency Maintenance
Emergency maintenance operations are performed in the case of emergencies or natural factors that may result in emergencies during the operation of the equipment. 4.1 Definition of Emergency For microwave equipment, an emergency refers to interruption of microwave services. 4.2 Purposes of Emergency Maintenance Emergency maintenance operations are performed to restore the services quickly. This is different from troubleshooting, whose purposes are to locate and rectify the faults. 4.3 Procedure for Emergency Maintenance The procedure for emergency maintenance consists of a main procedure and a sub-procedure for field troubleshooting.
Issue 03 (2012-07-30)
28
4.1 Definition of Emergency

For microwave equipment, an emergency refers to interruption of microwave services.
4.2 Purposes of Emergency Maintenance

Emergency maintenance operations are performed to restore the services quickly. This is different from troubleshooting, whose purposes are to locate and rectify the faults.
4.3 Procedure for Emergency Maintenance

The procedure for emergency maintenance consists of a main procedure and a sub-procedure for field troubleshooting.
NOTE
In the case of emergency events, the customers in China can contact the 24-hour technical support center of Huawei at 400-830-2118, and the customers in areas outside China can contact the local Huawei offices.
Issue 03 (2012-07-30)
29
Main Procedure for Emergency Maintenance

Figure 4-1 Main procedure for emergency maintenance
Start
Is there an incorrect operation? No
Yes Cancel the operation
Service interruoted by external causes?
Yes
Contact related departments to handle the problem
No Query NE status and alarms by using the NMS
NE access successful and alaarms cleared? No Rectify the fault on site
Yes Clear the alarm
Proceed with the next step
No
Is the service restored? Yes
Is the service restored? Yes 5 Check the troubleshooting result
No
Contact Huawei engineers
End
Issue 03 (2012-07-30)
30
Table 4-1 Description of the main procedure for emergency maintenance Comment No. 1 Description The common incorrect operations are as follows: l Modifying data configuration l Performing loopback operations l Shutting down the laser l Muting the ODU l Replacing boards/cables l Loading the software 2 3 Faults owing to external factors, including the power supply, cables, environment, and terminal equipment (such as switch devices) 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 the current 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. 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-2 shows the field maintenance operation sheet.
Table 4-2 Field maintenance operation sheet Maintained on Actual Step Step in the Entire Procedure Maintained by Troubleshooting Result Remarks
Issue 03 (2012-07-30)
31
Maintained on Actual Step Step in the Entire Procedure
Maintained by Troubleshooting Result Remarks
Issue 03 (2012-07-30)
32
Field Troubleshooting Sub-Procedure

Figure 4-2 Field troubleshooting sub-procedure
Start
Obvious equipment Yes damage? No
Repair or replace the equipment
Is the PWR indicator on the PIU on?

2 Yes Browse alarms locally by using the LCT 3 Equipment alarm? No 4 Radio link alarm? No 5 Yes Yes
No
Troubleshoot the power input
Clear the alarm
Clear the alarm
High order path alarm?

No
Yes
Clear the alarm
Low order path alarm?

No
Yes
Clear the alarm
Faulty interconnection with SDH/PDH equipment?

No
Yes
7 Troubleshoot the inter-connection faulty 8
Packet service fault?

No
Yes
Troubleshoot the packet service fault
Locate the fault by performing loopback operations section by section
Proceed to the next step
No
Is the service restored?
Yes End
Issue 03 (2012-07-30)
33
Table 4-3 Description of the field troubleshooting sub-procedure Comment No. 1 Description 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 circuits or insufficient fuse capacity), and rectify the fault accordingly. 2. Check the power cables, especially the connectors of the power cables. If the power cables or connectors of the power cables are incorrect, replace the power cables or re-prepare the connectors of the power cables. 3. Check the voltage and polarization of the input power. If the voltage or polarization of the input power does not meet the requirements, contact power engineers for troubleshooting.
NOTE The recommended fuse capacity of 10 A can meet requirements under the maximum power consumption. The following formula can be used to calculate the fuse capacity: Fuse capacity = (Total power consumption x 1.5) / (Rated voltage x 87.5%). The rated voltage of the input power is -48 V/-60 V and the permitted voltage ranges from -38.4 V to -72.0 V.
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 (Web LCT). 4. Checking Alarms.
NOTE If you fail to log in to the created NE, ensure that the operations you performed are correct, and then locate and rectify the fault according to the indicators of the system control, switching, and timing board. For details about the indicators, see the IDU Hardware Description.
Pay special attention to the following alarms: l HARD_BAD l POWER_ALM l FAN_FAIL l BD_STATUS l NESF_LOST l TEMP_ALARM l RADIO_RSL_HIGH l RADIO_RSL_LOW l RADIO_TSL_HIGH l RADIO_TSL_LOW l IF_INPWR_ABN l IF_CABLE_OPEN l VOLT_LOS
Issue 03 (2012-07-30)
34
Comment No. 4
Description Pay special attention to the following alarms: l PG_LINK_FAIL l PG_PRT_DEGRADED l MW_LIM l MW_LOF l R_LOS l R_LOF l R_LOC l MS_AIS l AU_AIS l AU_LOP l B1_EXC l B2_EXC l MW_BER_EXC
Pay special attention to the following alarms: l HP_LOM l B3_EXC l HP_UNEQ
Pay special attention to the following alarms: l TU_AIS l TU_LOP l BIP_EXC l LP_UNEQ l T_ALOS l E1_LOC
7 8
See 5.6 Troubleshooting the Interconnection with SDH Equipment or 5.7 Troubleshooting the Interconnection with PDH Equipment. See 5.8 Troubleshooting Native Ethernet Service Faults, 5.9 Troubleshooting Ethernet Service on the EoS/EoPDH Plane, 5.11 Troubleshooting CES Services, 5.12 Troubleshooting ATM Services, and 5.13 Troubleshooting Ethernet Services Carried by PWs.
Issue 03 (2012-07-30)
35
5 Troubleshooting
5
About This Chapter
Troubleshooting
This guide describes the general troubleshooting procedure and the methods of rectifying the common faults. 5.1 General Troubleshooting Procedure When handling a fault, make a detailed record of the fault phenomena. The customers in China can contact our 24-hour technical support center at 400-830-2118, and the customers in areas outside China can contact the local Huawei offices. 5.2 Troubleshooting Service Interruptions The service interruption fault indicates the service transmission failure due to an equipment fault or a link fault. 5.3 Troubleshooting the Radio Link When an NE reports MW_LOF, MW_BER_EXC, MW_BER_SD or MW_FEC_UNCOR due to failure or performance deterioration of a radio link, there is a radio link fault. 5.4 Troubleshooting Bit Errors in TDM Services When an NE reports an alarm or 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 in services. 5.5 Troubleshooting Pointer Justifications When 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 Equipment An interconnection fault occurs when the NE fails in transmitting SDH services with other SDH equipment. 5.7 Troubleshooting the Interconnection with PDH Equipment An interconnection fault occurs when the NE fails in transmitting PDH services with other PDH equipment. 5.8 Troubleshooting Native Ethernet Service Faults An Ethernet service fault may be the Ethernet service interruption or Ethernet service deterioration.
5 Troubleshooting
5.9 Troubleshooting Ethernet Service on the EoS/EoPDH Plane The Ethernet services transmitted on the EoS/EoPDH plane can be transmitted over a TDM network. The faults of the EoS/EoPDH-plane Ethernet services include service interruption and service degradation. 5.10 Troubleshooting MPLS Tunnels This section describes how to troubleshoot MPLS tunnels by using the MPLS OAM function or MPLS Ping/Traceroute function. 5.11 Troubleshooting CES Services This section describes how to troubleshoot CES services that are interrupted or degraded. 5.12 Troubleshooting ATM Services This section describes how to troubleshoot ATM services that are interrupted or degraded. 5.13 Troubleshooting Ethernet Services Carried by PWs This section describes how to troubleshoot Ethernet services that are carried by PWs and transmitted in the PSN. These Ethernet services are considered faulty when they are interrupted or deteriorate. 5.14 Troubleshooting Orderwire Faults If orderwire calls cannot get through when services are normal, there is an orderwire fault.
Issue 03 (2012-07-30)
37
5 Troubleshooting
5.1 General Troubleshooting Procedure

When handling a fault, make a detailed record of the fault phenomena. The customers in China can contact our 24-hour technical support center at 400-830-2118, and the customers in areas outside China can contact the local Huawei offices.
Issue 03 (2012-07-30)
38
5 Troubleshooting
General Troubleshooting Procedure

Figure 5-1 General troubleshooting procedure
Start
1
Record the fault phenomena
Caused by external factors? No
Yes
Other troubleshooting procedures
Analyze fault causes and locate the fault
Is the fault rectified?

4
Yes
No Report to Huawei
Make a solution together
Attempt to rectify the fault
No
Is the service restored? Yes Observe the operation
No
Is the fault rectified? Yes Fill in the troubleshooting report
End
Issue 03 (2012-07-30)
39
5 Troubleshooting
Table 5-1 General troubleshooting procedure Comment No. 1 Description When recording the fault phenomena, make a true and detailed record of the entire process of the fault. Record the exact time when the fault occurs and the operations performed before and after the fault occurs. Save the alarms, performance events, and other important information. You can use the clickto-collect function on the NMS to collect data. Faults owing to external factors, including the power supply, cables, environment, and terminal equipment (such as switch devices) If the fault is caused by the equipment, see 5.2 Troubleshooting Service Interruptions. To provide feedbacks or obtain technical support, customers in China can contact the 24-hour technical support center at 400-830-2118, and the customers in areas outside China can contact the local Huawei offices.
2 3 4
5.2 Troubleshooting Service Interruptions

The service interruption fault indicates the service transmission failure due to an equipment fault or a link fault.
Fault Causes
l The operation is improper. The configuration data changes, the loopback is performed, the cable is replaced, or the board is replaced. l l The transmission NE or link is faulty. The interconnection is improper. If the transmission equipment functions normally and the connection is normal, check whether the interconnection between the transmission equipment is proper and whether the switch equipment is faulty.
Fault Locating Methods

1. 2. Check the operations before the service interruption to determine whether the service interruption results from an incorrect operation. 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 by performing loopback section by section or replacing the corresponding parts.
Issue 03 (2012-07-30)
5 Troubleshooting
CAUTION
If the fault cannot be rectified immediately, restore the services quickly by adjusting the service route or performing a forced switching.
Troubleshooting Procedure
Figure 5-2 General procedure for troubleshooting the service interruption
Start
Incorrect operation?
Yes
Cancel the operation
No
Service interrupted by external causes? No

Query NE status and alarms by using the centralized NMS
Yes
Contact related departments to solve the problem
NE access successful and alarms cleared? No
Yes
Clear the alarm
Rectify the fault on site
No Service restored?
Yes
End
Issue 03 (2012-07-30)
41
5 Troubleshooting
Table 5-2 Description of the general procedure for troubleshooting the service interruption Comment No. 1 Description The common incorrect operations are as follows: l Modifying the data configuration l Loopback l Shutting down the laser l Muting the ODU l Replacing the board or cable l Loading the software 2 3 4 Faults owing to external factors, including the power supply, cables, environment, and terminal equipment (such as switch devices) For details, see 8.3.1 Checking the NE Status and 8.3.3 Browsing Current Alarms. 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, MW_CFG_MISMATCH, RADIO_MUTE, and WRG_BD_TYPE
Issue 03 (2012-07-30)
42
5 Troubleshooting
Figure 5-3 Field troubleshooting sub-procedure

Start
Obvious equipment Yes damage? No
Repair or replace the equipment
Is the PWR indicator on the PIU on?

2 Yes Browse alarms locally by using the LCT 3 Equipment alarm? No 4 Radio link alarm? No 5 Yes Yes
No
Troubleshoot the power input
Clear the alarm
Clear the alarm
High order path alarm?

No
Yes
Clear the alarm
Low order path alarm?

No
Yes
Clear the alarm
Faulty interconnection with SDH/PDH equipment?

No
Yes
7 Troubleshoot the inter-connection faulty 8
Packet service fault?

No
Yes
Troubleshoot the packet service fault
Locate the fault by performing loopback operations section by section
Proceed to the next step
No
Is the service restored?
Yes End
Issue 03 (2012-07-30)
43
5 Troubleshooting
Table 5-3 Description of the field troubleshooting sub-procedure Comment No. 1 Description 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 circuits or insufficient fuse capacity), and rectify the fault accordingly. 2. Check the power cables, especially the connectors of the power cables. If the power cables or connectors of the power cables are incorrect, replace the power cables or re-prepare the connectors of the power cables. 3. Check the voltage and polarization of the input power. If the voltage or polarization of the input power does not meet the requirements, contact power engineers for troubleshooting.
NOTE The fuse capacity should meet the requirement of actual power consumption. The following formula can be used to calculate the fuse capacity: Fuse capacity = (Total power consumption x 1.5) / (Rated voltage x 87.5%). The rated voltage of the input power is -48 V/-60 V and the permitted voltage ranges from -38.4 V to -72.0 V.
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 (Web LCT) 4. Checking Alarms
NOTE If you fail to log in to the created NE, ensure that the operations you performed are correct, and then locate and rectify the fault according to the indicators of the system control, switching, and timing board. For details about the indicators, see the IDU Hardware Description.
Pay special attention to the following alarms: l HARD_BAD l POWER_ALM l FAN_FAIL l BD_STATUS l NESF_LOST l TEMP_ALARM l RADIO_RSL_HIGH l RADIO_RSL_LOW l RADIO_TSL_HIGH l RADIO_TSL_LOW l IF_INPWR_ABN l IF_CABLE_OPEN l VOLT_LOS
Issue 03 (2012-07-30)
44
5 Troubleshooting
Comment No. 4
Description Pay special attention to the following alarms: l PG_LINK_FAIL l PG_PRT_DEGRADED l MW_LIM l MW_LOF l R_LOS l R_LOF l R_LOC l MS_AIS l AU_AIS l AU_LOP l B1_EXC l B2_EXC l MW_BER_EXC
Pay special attention to the following alarms: l HP_LOM l B3_EXC l HP_UNEQ
Pay special attention to the following alarms: l TU_AIS l TU_LOP l BIP_EXC l LP_UNEQ l T_ALOS l E1_LOC
7 8
See 5.6 Troubleshooting the Interconnection with SDH Equipment or 5.7 Troubleshooting the Interconnection with PDH Equipment. See 5.8 Troubleshooting Native Ethernet Service Faults, 5.9 Troubleshooting Ethernet Service on the EoS/EoPDH Plane, 5.11 Troubleshooting CES Services, 5.12 Troubleshooting ATM Services, and 5.13 Troubleshooting Ethernet Services Carried by PWs.
Experience and Summary

The maintenance personnel need to perform the routine maintenance operations periodically, to detect and rectify faults before the faults affect the services and therefore to reduce the equipment fault rate.
Issue 03 (2012-07-30)
45
5 Troubleshooting
5.3 Troubleshooting the Radio Link

When an NE reports MW_LOF, MW_BER_EXC, MW_BER_SD or MW_FEC_UNCOR due to failure or performance deterioration of a radio link, there is a radio link fault.
Radio Link Faults

Radio link faults are classified into: l l l Equipment faults, including outdoor component faults, cable faults, and power supply faults Propagation faults, including fading, interference, and poor line of sight (LOS) Poor construction quality, including poor antenna/component installation, poor grounding, and poor waterproofing
Figure 5-4 Radio link faults

Causes of radio link faults
Propagation faults
Poor construction quality
Equipment faults
Interference
Fading
Poor LOS
Antenna installation
Cables
External interference Over-reach interference
Rain fading Multipath fading Reflection
LOS not achieved Near-field blocking
Antennas not aligned Antennas loosened or offset
Poor grounding
Hardware Faults Power faults
Poor waterproofing
Damaged cable components
Fading Phenomena and Causes

During microwave network maintenance, link fading is the main cause for radio link faults. Link fading is more difficult to locate and handle than hardware faults. Table 5-4 Fading phenomena and causes Fading Type Classifie d by RSL Down fading Fading Phenomena The RSL is lower than the RSL after free space fading. The difference can be tens of decibels. Fading Cause l Multi-path fading l Duct-type fading l Rain fading
Issue 03 (2012-07-30)
46
5 Troubleshooting
Fading Type Up fading
Fading Phenomena The RSL is higher than the RSL in the free space. The difference can be 10-odd decibels. 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 fading occurs in the period from 18:00 to 20:00 of a day or in a certain season of a year.
Fading Cause l Interference l Long delay caused by terrain reflection l Multi-path fading l Duct-type fading l Long delay caused by terrain reflection
Classifie d by fading duration
Fast fading
Slow fading
The fading lasts from tens of seconds to several hours.
l Generally, slow up fading is caused by interference. l Slow down fading is caused by rain, and therefore is also called rain fading. Rain fading occurs on links working at a frequency of 10 GHz or in areas where heavy rain occurs.
Issue 03 (2012-07-30)
47
5 Troubleshooting
Figure 5-5 Procedure for troubleshooting the radio link
Start
Is there an incorrect operation? No
Yes
Undo the operation.
Hardware alarms exist? No
Yes Rectify equipment faults.
Are there IF or RF alarms on the link? No
Yes
4 Analyze the historical RSL records and the current RSL value 5 Co-channel or adjacentchannel interference Long delay caused by terrain reflection The link is blocked. 6 Is the RSL value always less than the designed value? No 7 Yes Yes The antennas are offset. Passive components like hybrid couplers or flexible waveguides are faulty. Rain fading
Troubleshoot the fault as a non-radio link fault.
RSL greater than the receiver sensitivity? No
Yes
Is it raining when the fault occurs? No
Does the fault occur regularly? No Troubleshoot the fault by replacing the suspected faulty parts.
Yes
Multipath fading Terrain reflection
Is the fault rectified? No
Yes
End
Issue 03 (2012-07-30)
48
5 Troubleshooting
Table 5-5 Description of the procedure for troubleshooting the radio link Mark 1 Description Check whether any misoperation has been performed: l Shutting down the power supply, which caused the local or remote NE to be unreachable to the NMS l Muting the radio transmitter, which caused the RADIO_MUTE alarm to be reported l Looping back IF ports, which caused the LOOP_ALM alarm to be reported l Configuring incorrect radio link data, which caused the MW_CFG_MISMATCH alarm to be reported l Enabling an AM self-check, which caused the MW_AM_TEST alarm l Enabling IF consecutive wave output 2 Hardware fault alarms include: l HARD_BAD l RADIO_TSL_HIGH, RADIO_TSL_LOW 6.15 Replacing the ODU. 3 IF and RF alarms include: l MW_LOF, MW_LIM, MW_RDI l MW_BER_EXC, MW_BER_SD, MW_FEC_UNCOR l RADIO_RSL_HIGH, RADIO_RSL_LOW l RADIO_RSL_BEYONDTH l AM_DOWNSHIFT 4 RSL is the major reference for locating and handling propagation faults. Follow instructions in 8.3.4 Browsing Current Performance Events of the radio link and 8.3.5 Browsing Historical Performance Data of a Radio Link to browse and analyze the historical RSL records and the current RSL value. Mute the opposite NE and check the RSL at the local NE. 1. If the RSL value is larger than -90 dBm, there may be co-channel interference that affects long-term availability and error-second performance of the system. Follow instructions in 8.11 Scanning Interfering Signals or use a frequency spectrum analyzer to locate the possible interfering frequencies. 2. If a third-party RF device is the interfering source, contact the local frequency spectrum management department to clear the interference. If interference is caused due to improper route planning, modify the frequency plan to minimize the interference impacts. If receive power changes radically within seconds (fluctuation range varying from more than 10 dB to dozens of dB) and the change occurs periodically (for example, always at midnight), there may be a fault caused by terrain reflection. Check whether there are rivers or lakes on the propagation trail. If there is an intensively reflective terrain, adjust the mounting height of the antenna to change the link elevation, therefore minimizing reflection impacts. Alternatively, replan the route to avoid the intensively reflective terrain.
Issue 03 (2012-07-30)
49
5 Troubleshooting
Mark 6
Description If the RSL value had been smaller than the designed value for a long time before the fault occurred, the propagation trail is faulty. Proceed as follows: l Check whether the antenna connection is loose or the antenna is unaligned. If yes, re-align the antenna. l Check whether there are any blocks in the radio transmission trail or in the near field of the antenna. If yes, adjust the mounting height of the antenna to avoid blocks, replan the radio link route. l Check whether loss increases because the antenna, hybrid coupler, and flexible waveguide are not intact or are wet. If yes, replace the faulty components.
If a radio link fault occurred in poor weather conditions (such as rainy, snowy, or foggy) and was rectified after the conditions disappeared, the fault cause was weather fading. For a fault caused by weather fading, check whether the link fading margin is insufficient. 1. Calculate the actual link availability. Calculate the total link fault time within one year or half a year. Calculate the actual link availability using the following formula: <Link availability> = <Total fault time>/<Calculation period>. l If the actual link availability is lower than the designed value by an order of magnitude, the link fading margin is insufficient. Re-plan the radio link parameters. l If the difference between the actual link availability and the designed value is small, no special handling operations are required. 2. Before re-planning a radio link, check whether the rain zone parameters, the refractivity gradient, and the planning algorithm are incorrect. The practicable measure could be as follows: l Increase the transmit power or replace the original antenna with a new one having a larger diameter to increase the system gain and the fading margin. l Use a frequency band on which rain fading has smaller impacts.
If the receive power fluctuates greatly and fast (by more than 10 dB or several 10 dB within several seconds or several 10 seconds), fast fading occurs. Fast fading may occur due to: l Multi-path fading: Faults occur periodically, for example, at the day-and-night alternating time period. l Duct-type fading: random fast fading To handle fast fading, proceed as follows: l Increase the path inclination: That is, adjust the antenna mount heights at both ends to increase the height differences between the antennas at both ends. l Reduce surface reflection. For apparent strong reflection surfaces, for example, large areas of water, flat lands, and bold mountain tops, adjust antennas to move reflection points out of the strong reflection areas or mask the reflection by using landforms. l Reduce the path clearance. With LOS conditions guaranteed, lower antenna mount heights as much as possible.
Issue 03 (2012-07-30)
50
5 Troubleshooting
Mark 9
Description If all preceding actions cannot rectify the fault, replace the ODU at both ends. Then, check whether services are functional. If the fault persists, replan the radio link by changing the operating frequency, using antennas with a larger diameter, changing the antenna heights, or changing the routes.

l l During the commissioning, ensure that the antenna is aligned properly, to prevent possible incipient faults. Periodically collect and analyze the data about the changes in the transmit power and receive power so that you can detect and then rectify the incipient faults accordingly in time.
5.4 Troubleshooting Bit Errors in TDM Services

When 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 in services.
Fault Phenomena
The IF bit errors refer to the bit errors that the IF board detects through the self-defined overhead byte in the microwave frame. The related alarms and performance events are as follows: l l l l l l l l l MW_BER_EXC MW_BER_SD MW_CFG_MISMATCH MW_LOF IF_BBE IF_ES IF_SES IF_CSES IF_UAS
The RS bit errors refer to the bit errors that the line processing unit or the IF board that works in SDH mode through the B1 overhead byte in the RS overhead. The related alarms and performance events are as follows: l l l l l l l
Issue 03 (2012-07-30)
B1_EXC B1_SD RS_CROSSTR RSBBE RSES RSSES RSCSES

5 Troubleshooting
RSUAS
NOTE
The IF board that works in PDH mode may also detect the previous RS bit error alarms and performance events. In this case, the IF board detects bit error alarms and performance events in the PDH microwave frame 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 MS overhead. The related alarms and performance events are as follows: l l l l l l l l B2_EXC B2_SD MS_CROSSTR MSBBE MSES MSSES MSCSES MSUAS
The HP bit errors refer to the bit errors that the line processing unit or the IF board that works in SDH mode through the B3 byte in the HP overhead. The related alarms and performance events are as follows: l l l l l l l l B3_EXC B3_SD HP_CROSSTR HPBBE HPES HPSES HPCSES HPUAS
The LP bit errors refer to the bit errors that the tributary board or IF board detects through the V5 byte in the VC-12 overhead. The related alarms and performance events are as follows: l l l l l l l l BIP_EXC BIP_SD LP_CROSSTR LPBBE LPES LPSES LPCSES LPUAS
Issue 03 (2012-07-30)
52
5 Troubleshooting
Fault Causes
Table 5-6 Causes of bit errors Fault There are IF bit errors. Common Fault Cause l The radio link is faulty. Check whether the MW_BER_EXC, MW_BER_SD, MW_FEC_UNCOR, MW_LOF or RPS_INDI alarm is reported. If yes, the radio link is faulty. l The services are incorrectly configured. Check whether the MW_CFG_MISMATCH alarm is reported. If yes, the number of E1 services is inconsistent on both ends of the radio link. l The IF board at the local end or opposite end is faulty. There are RS bit errors. l The line is faulty. The common causes for bit errors on the optical line are as follows: the optical fiber line, the optical power is abnormal, the fiber performance deteriorates, or the fiber connector is not clean. In the case of bit errors on the radio link, check whether the MW_BER_EXC, MW_BER_SD, MW_FEC_UNCOR or RPS_INDI alarm is reported. If yes, the radio link is faulty. l The line processing unit or IF board is faulty. l The clock unit is faulty. l The quality of the clock over the network declines. When the quality of the clock over the network declines, a pointer justification event occurs.
Issue 03 (2012-07-30)
53
5 Troubleshooting
Fault There are not any RS bit errors but there are MS bit errors or HP bit errors.
Common Fault Cause l The line processing unit or IF board is faulty. l The quality of the clock over the network declines. When the quality of the clock over the network declines, a pointer justification event occurs. l The working temperature of the line processing unit or IF board is excessively high.
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 crossconnect unit is excessively high. l There is a power surge or an external interference source, or the equipment is not properly grounded. (This cause does not need to be considered during the troubleshooting of an IF board.)

1. 2. 3. 4. 5. Analyze the equipment alarms and performance events that are related to service configuration errors and bit errors. 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. When multiple paths have bit errors, first check whether the overlapping part of the service paths is faulty. If you fail to locate the fault by analyzing the alarms and performance events, perform loopback operations section by section. Replace the parts whose performance may deteriorate with new ones.
Issue 03 (2012-07-30)
54
5 Troubleshooting
Figure 5-6 Procedure for troubleshooting bit errors
Start
2
Is there an equipment alarm? No Yes Clear the alarm
3
Is there a pointer justification event? No Yes Troubleshoot the pointer justification SDH optical interface board
Troubleshoot RS bit errors on the SDH optical interface board
Is there an RS bit error alarm or a performance event?
Yes
If the alarming board is IF board
No
4
Troubleshoot RS bit errors on the IF board
Is there an MS/ HP alarm or performance event? No
5
Yes Troubleshoot MS/HP bit errors
6
Is there an LP alarm? No Locate the fault by performing loopback operations section by section Yes Troubleshoot LP bit errors
No
Is the fault rectified? Yes End
Issue 03 (2012-07-30)
55
5 Troubleshooting
Table 5-7 Description of the procedure for troubleshooting bit errors Comment No. 1 Description Pay special attention to the following alarms: l TEMP_ALARM l HARD_BAD l MW_CFG_MISMATCH 2 3 See 5.5 Troubleshooting Pointer Justifications. 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 the fiber is faulty. Otherwise, the equipment at both ends of the service path is faulty. 3. In the case of a fiber fault, check whether the fiber between the equipment and the ODF and the section of the fiber that is led out of the telecommunications room are pressed. In addition, check whether the fiber connectors are clean. 4. In the case of faults at both ends of the service path, use a fiber jumper to loop back the optical ports. If the fault persists after the loopback, the line board may be faulty. 5. In the case of faults at both ends of the service path, you can also replace the board where the line unit is located or interchange between the board and another board of the same type that is working normally. If the alarm changes 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 Radio Link and rectify the fault. 3. If none of the alarms occurs, replace the IF board. 5 The troubleshooting procedure is as follows: 1. Perform a loopback on the line board that reports the alarm. If the fault persists after the loopback, replace the line board. If the fault is rectified after the loopback, replace the line board at the transmit end. 2. If you fail to rectify the fault by replacing the line board, check whether there is a power surge or an external interference source or whether the equipment is not properly grounded.
Issue 03 (2012-07-30)
56
5 Troubleshooting
Comment No. 6
Description 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 the equipment is not properly grounded.

NOTE
The TDM services mentioned refer to Native TDM services. The handling procedure applies when the STM-1e port. is faulty
l l
During the routine maintenance, check bit error performance events periodically and handle them in time. To locate a fault, prefer the method of analyzing alarms and performance events to the method of performing loopback operations and the method of replacing the parts.
5.5 Troubleshooting Pointer Justifications

When an NE reports a large number of justification events about the administrative unit (AU) pointer or the tributary unit (TU) pointer, there are pointer justification faults.
Fault Phenomena
When the position of the first byte of the VC-4 in the AU-4 payload changes, the AU pointer makes a justification accordingly. The performance events related to the AU pointer justification are as follows: l l l AUPJCHIGH AUPJCLOW 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 terminate the AU pointer justification. The terminating method is to transform the AU pointer justification into the TU pointer justification. The performance events related to the TU pointer justification are as follows: l l l TUPJCHIGH TUPJCLOW TUPJCNEW
NOTE
The TU pointer justification is made at the NE where the AU pointer is transformed into the TU pointer, but is detected and reported by the tributary board of the NE where services are terminated.
Issue 03 (2012-07-30)
57
5 Troubleshooting
Fault Causes
l l l l 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. The fiber connections are incorrect. As a result, a timing loop occurs. The quality of the clock source declines, the clock unit is faulty, or there are other clockrelated faults. The tributary board is faulty (only for the TU pointer justification).

When 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 AU pointer justification Fault Locating Method 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 asynchronous with the entire network. 4. Replace the parts whose performance may deteriorate 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 whose clock is asynchronous with the entire network. 4. Replace the parts whose performance may deteriorate with new ones.
Issue 03 (2012-07-30)
58
5 Troubleshooting
Figure 5-7 Procedure for troubleshooting pointer justifications
Start
Is there a clock-related alarm? No Check the clock configuration
Yes
Clear the alarm
Incorrect configuration? No Check the fiber connection
Yes
Modify the data configuration
Incorrect fiber connection? No
Yes Reconnect the fibers
4
An AU pointer justification event? Yes Locate the NE whose clock is out of synchronization
5
Locate the faulty board
No
6
A TU pointer justification event? Yes Locate the NE whose clock is out of synchronization
7
Locate the faulty board
No
No
Yes End
Issue 03 (2012-07-30)
59
5 Troubleshooting
Table 5-8 Description of the procedure for troubleshooting pointer justifications Comment No. 1 Description Pay special attention to the following alarms: l TEMP_ALARM l HARD_BAD l LTI l SYNC_C_LOS l S1_SYN_CHANGE l EXT_SYNC_LOS 2 Check the following points: l Check whether there are two clock reference sources on the entire network. l Check whether a timing loop is generated. 3 Query ECC routes to check whether the fibers are connected correctly. Check the fiber connections in the east and west directions of the NE that reports the pointer justification event. 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 is asynchronous with the reference clock. Hence, the line board on the remote NE that receives the clock signal, the line board that sends the clock signal to the remote NE, and the clock unit of the remote NE, may be faulty. 5. Set the clock of the sink NE to the free-run mode. Set the other NEs to trace 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 to report the AU pointer justification of the VC-4 path. The clock of the remote NE to which the line board is connected is asynchronous with the reference clock. Hence, the line board on the NE that receives the clock signal, the line board that sends the clock signal to the NE, and the clock unit of the NE, may be faulty. 7. Compare the results and find out the common points. 5 Replace the possibly faulty boards.
Issue 03 (2012-07-30)
60
5 Troubleshooting
Comment No. 6
Description 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 have the E1 services of the central NE. 2. Along the clock tracing direction, locate the NE that is the first to report the TU pointer justification event. The clock of the NE is asynchronous with the reference clock. Hence, the line board on the NE that receives the clock signal, the line board that sends the clock signal to the NE, and the clock unit of the NE, may be faulty. 3. Modify the configuration data to ensure that all the NEs trace the clock along the other direction. 4. Along the clock tracing direction, locate the NE that is the first to report the TU pointer justification event. The clock of the NE is asynchronous with the reference clock. Hence, the line board on the NE that receives the clock signal, the line board that sends the clock signal to the NE, and the clock unit of the NE, may be faulty. 5. Compare the results and find out the common points.
NOTE This method is also applicable to locating an AU pointer justification event.
Replace the possibly faulty boards. In the case of a TU pointer justification event, check whether the line board, the clock board, and the tributary board are faulty.

On a properly synchronized network, there are few pointer justifications (less than six per day on each port). Hence, monitoring the pointer of an SDH transmission system is an effective way to check the synchronization status of the system.
5.6 Troubleshooting the Interconnection with SDH Equipment

An interconnection fault occurs when the NE fails in transmitting SDH services with other SDH equipment.
Fault Causes
l The VC-12 numbering method of the OptiX equipment is different from the numbering method of the equipment of certain vendors. The OptiX equipment applies the timeslot numbering method. The numbering formula is: VC-12 number = TUG-3 number + (TUG-2 number - 1) x 3 + (TU-12 number - 1) x 21. This method is also called as the method of numbering by order.
Issue 03 (2012-07-30)
61
5 Troubleshooting
Certain equipment applies the line numbering method. The numbering formula is: VC-12 number = (TUG-3 number - 1) x 21 + (TUG-2 number - 1) x 3 + TU-12 number. This method is also called as the interleaved method. l l The overhead bytes at both ends are inconsistent. 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 interconnection failure is that the service is not set to the VC-4 pass-through service and thus the overheads are processed in the terminating mode instead of the pass-through mode.

Analyze the fault phenomena and alarms that are generated on the equipment. Check the possible fault causes one after another.
Issue 03 (2012-07-30)
62
5 Troubleshooting
Figure 5-8 Procedure for troubleshooting the interconnection with SDH equipment
Start
Is the interconnected equipment Yes the ATM/IP equipment? No Query the VC-12 numbering method of the interconnected equipment
Set the interconnection service to be the VC-4 passthrough service
Is the numbering mode the line numbering? No 1 Is there an overhead setting related alarm? No Is the interface the STM-1 electrical interface? 3 No
Yes
Modify the data configuration. Use the line numbering method to set the VC-12
Yes
Handle the alarm
2 Yes Check the grounding
Test the indexes of interfaces
Do the interfaces meet relevant standards? Yes
No
Handle the faults of the interconnected equipment
Go to the next step Handle the faults of the local equipment
No
Is the fault cleared? Yes
End
Issue 03 (2012-07-30)
63
5 Troubleshooting
Table 5-9 Description of the procedure for troubleshooting the interconnection with SDH equipment Comment No. 1 Description Pay special attention to the following alarms: l J0_MM l HP_TIM l LP_TIM l HP_SLM l 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 a multimeter to measure the level between the shielding layers of the coaxial cables at the receive and transmit ends of the SDH equipment. In addition, measure the level between the shielding layers of the coaxial cables at the receive and transmit ends of the opposite equipment. If the potential difference is large (about 0.5 V), the fault may be caused by the grounding.
Common indexes of the optical interfaces are as follows: l Mean launched optical power l Receiver sensitivity l Overload optical power l Permitted frequency deviation of the input interface Common indexes of the electrical interfaces: l Permitted frequency deviation of the input interface l Allowed attenuation of the input interface

To rectify an interconnection fault, you must be familiar with the characteristics of the interfaces on the interconnected equipment.
5.7 Troubleshooting the Interconnection with PDH Equipment

An interconnection fault occurs when the NE fails in transmitting PDH services with other PDH equipment.
5 Troubleshooting
Fault Causes
l l l l There is an impedance mismatch between interfaces. The equipment is not grounded properly. The cable performance deteriorates. The indexes of the PDH interfaces do not meet the requirements.

Analyze the fault phenomena and alarms that are generated on the equipment. Check the possible fault causes one after another.
Issue 03 (2012-07-30)
65
5 Troubleshooting
Figure 5-9 Procedure for troubleshooting the interconnection with PDH equipment
Start 1 Check the impedance of the interfaces.
Is there an impedance mismatch? No Is the cable a coaxial cable? No 3 Check the cables.
Yes
Replace the cable or the tributary board
Yes
2 Check the grounding.
Is in good conditions?
No
Adjust the cables.
Yes Test the indexes of Interfaces.
Do the interfaces meet standards? Yes Troubleshoot the faults on the local equipment.
No
Troubleshoot the faults on the interconnected Equipment.
Proceed with the next step.
No
Yes
End
Issue 03 (2012-07-30)
66
5 Troubleshooting
Table 5-10 Description of the procedure for troubleshooting the interconnection with PDH equipment Comment No. 1 2 Description Check the impedance of the E1 path. Ensure that the impedance of the E1 path is consistent with the cable type. Check the following points: l Check whether all the equipment and the DDF in the telecommunications room are jointly grounded. l Check whether the shield layers of the coaxial cable connectors on the DDF are connected to the protection ground. l Check whether the shield layers of coaxial cables are grounded in the same manner.
NOTE Disconnect all the signal cables between the interconnecting equipment sets. Use a multimeter to measure the level between the shield layers of the coaxial cables at the receive and transmit ends of the PDH equipment and the level between the shield layers of the coaxial cables at the receive and transmit ends of the equipment at the opposite end. If the potential difference is large (about 0.5 V), the fault may be caused due to the improper grounding.
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 the power signal).
NOTE Checking the cables involves checking the cables from the DDF to the client side and checking the cables from the DDF to the transmission equipment side.
Check the following indexes: l Input jitter tolerance l Permitted frequency deviation of the input interface l Output jitter l Output frequency deviation

NOTE
The PDH services mentioned refer to Native E1 services.
In the case of interconnection with PDH equipment, improper grounding is the most common cause for an interconnection failure.
Issue 03 (2012-07-30)
67
5 Troubleshooting
5.8 Troubleshooting Native Ethernet Service Faults

An Ethernet service fault may be the Ethernet service interruption or Ethernet service deterioration.
Prerequisites
The Ethernet service interruption indicates that the Ethernet service is 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 incorrect packets exist in the received or transmitted data.
Fault Phenomena
The Ethernet service interruption indicates that the Ethernet service is 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 incorrect packets exist in the received or transmitted data. Table 5-11 Common faults of Ethernet services Symptom Ethernet services are interrupted. Alarm HARD_BAD, TEMP_ALARM, WRG_BD_TYPE, or BD_STATUS PORTMODE_MISMATCH, COMMUN_FAIL, LAG_DOWN, ETH_NO_FLOW ETH_LOS, ETH_EFM_LOOPBACK, or LOOP_ALM LASER_MOD_ERR Ethernet services suffer degradation. HARD_BAD or TEMP_ALARM PORTMODE_MISMATCH, FLOW_OVER or LAG_MEMBER_DOWN AM_DOWNSHIFT MAC_FCS_EXC MAC_EXT_EXC DROPRATIO_OVER EG4, EG4P, EM6F EG4, EG4P, EM6TA, EM6FA, EM6F or EM6T EG4, EG4P, EM6TA, EM6FA, EM6F or EM6T ISV3, ISU2, ISX2, IFU2 or IFX2 Board EG4, EG4P, EM6TA, EM6FA, EM6F or EM6T
Issue 03 (2012-07-30)
68
5 Troubleshooting
Fault Causes
l 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 ports on the interconnected equipment. The service configuration is incorrect. l l l l l l The equipment at the local end is faulty. The line board is faulty or has bit errors. When the AM function is enabled, the Ethernet service bandwidth decreases due to the downward AM switch. The interconnected equipment is faulty. The network cable is faulty. External electromagnetic interference is severe.

1. 2. 3. Rectify the human-caused faults such as a loopback and a data configuration error. Locate the fault cause according to the equipment alarms. Locate the fault cause according to the RMON performance events and alarms.
Issue 03 (2012-07-30)
69
5 Troubleshooting
Troubleshooting Ethernet Services Configured on a Per NE Basis

Figure 5-10 Procedure for troubleshooting Ethernet services configured on a per NE basis
Start
Incorrect operation? No
Yes
Cancel this operation
An equipment alarm or alarm on the radio link? No
Yes
Clear the alarm
An Ethernet alarm? No
Yes
Clear the alarm
5 Query the port and service traffic and analyze the fault causes No 6 Any abnormal RMON performance events? No Troubleshoot equipment faults by performing loopbacks section by section or replacing boards Yes
A loop formed by the E-LAN service trails? No
Yes
Release the loop
Troubleshoot the fault according to the flow of handling RMON performance events
No
Is the fault rectified? Yes End
Issue 03 (2012-07-30)
70
5 Troubleshooting
Table 5-12 Description of the procedure for troubleshooting Ethernet services configured on a per NE basis Comment No. 1 Description Check the following points: l Whether a loopback is set for the Ethernet port l Whether a loopback is set for the transmission line l Whether the parameter settings of the Ethernet port, such as the port enabled state, working mode, and flow control, are the same as the parameter settings of the Ethernet port on the interconnected equipment l Check whether the Ethernet protocol and the Ethernet service configuration (especially the attributes of the Ethernet port) are correct. 2 Pay special attention to the following equipment alarms: l POWER_ALM l FAN_FAIL l HARD_BAD l BD_STATUS l NESF_LOST l TEMP_ALARM l RADIO_RSL_HIGH l RADIO_RSL_LOW l RADIO_TSL_HIGH l RADIO_TSL_LOW l IF_INPWR_ABN Pay special attention to the following line alarms: l MW_LIM l MW_LOF l MW_BER_EXC l MW_BER_SD l MW_RDI l MW_FEC_UNCOR 3 Pay special attention to the following alarms: l ETH_LOS l ETH_NO_FLOW l LAG_DOWN l LAG_MEMBER_DOWN l FLOW_OVER 4 Follow the instructions in Detecting E-LAN Service Loops to check whether E-LAN services are looped back. Release the loops if any are formed.
Issue 03 (2012-07-30)
71
5 Troubleshooting
Comment No. 5
Description Query Ethernet service rates on various ports to analyze the service rates and locate faults. 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 port approaches or reaches the license capacity of the IF port, the license capacity is too low and you need to apply for a license allowing for a higher capacity. l If the transmit rate of the port approaches or reaches the maximum Ethernet bandwidth of the IF port, the bandwidth of the IF port is too low and needs to be increased by the network planning personnel. l If the transmit rate of the port is much lower than the receive rate of the Ethernet port, or if the receive rate of the port is much higher than the transmit rate of the Ethernet port, the local end is faulty. Locate the fault as follows: Check the Ethernet service configuration and QoS configuration. By Querying port flow classification or packet loss performance of egress queues 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, create flows specific to the VLANs in the port policy, and check if sufficient bandwidth is available for the flows by querying flow traffic.
For RMON performance events, see the D RMON Event Reference.
Issue 03 (2012-07-30)
72
5 Troubleshooting
Figure 5-11 Procedure for troubleshooting an RMON performance event

Start 1 View the statistics group performance on an Ethernet port
Is there any FCS error? No Is there any collision or fragment? No Are broadcast packets excessive? No
Yes
Rectify the fault of line bit errors
Yes
Check the working mode of the port
Yes
Handle the problem on excessive broadcast packets
Use a meter to perform the test
Is the test passed? No 5 Is it a MTU setting problem? No Rectify the equipment fault by loopback section by section or replacing the board
Yes
Rectify the fault of the interconnected equipment
Yes
Modify the MTU value
No
Is the fault rectified? Yes
End
Table 5-13 Description of the procedure for troubleshooting an RMON performance event No. 1 Description 8.20 Querying Traffic, Physical Bandwidth, or Bandwidth Utilization to obtain the real-time performance statistics data of the Ethernet port.
Issue 03 (2012-07-30)
73
5 Troubleshooting
No. 2
Description 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, it indicates that the hardware of the original port is faulty. Otherwise, the hardware of the Ethernet port on the equipment at the opposite end is faulty.
Check the following points: l Whether the port operating rates on the equipment at both ends are the same l Whether the working modes (full duplex or half duplex) of the Ethernet port on the equipment at both ends are the same l 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 the Ethernet port is set to auto-negotiation mode at one end, the Ethernet port must not be set to full duplex mode at the opposite end.)
Check for the cause for excessive broadcast packets and solve the problem. If the problem is caused on the equipment at the opposite end, set the threshold of broadcast packet suppression for an Ethernet port to reduce broadcast packets. Test the MTU of the network by using a test meter. The maximum frame length that is set for a port should be longer than the MTU of the network.
Troubleshooting Ethernet Services Configured in an End-to-End Manner

Figure 5-12 Procedure for troubleshooting faults in Ethernet services configured in an end-toend manner
Start
1 Incorrect operation?
Yes
Cancel this operation.
No 2 Perform intelligent diagnosis on Ethernet services. Failure Refer to the procedure for troubleshooting Ethernet services configured on a per NE basis. Success Troubleshoot according to the relevant handling suggestions.
No
Yes
End
Issue 03 (2012-07-30)
74
5 Troubleshooting
Table 5-14 Description of the procedure for troubleshooting Ethernet services configured in an end-to-end manner Comment No. 1 Description Check the following points: l Whether a loopback is set for the Ethernet port l Whether a loopback is set for the transmission line l Whether the Ethernet port parameters, such as port enabling/disabling status, working mode, and flow control, are configured consistently at the local end and peer end l Whether Ethernet protocol and Ethernet service configurations (especially Ethernet port attributes) are correct 2 Intelligent fault diagnosis uses OAM to implement fault diagnosis over services, PWs, and tunnels, and the physical layer, and supports the output of diagnostic results for further troubleshooting.
NOTE Only the Native E-Line services configured end to end support intelligent fault diagnosis. For the troubleshooting of E-LAN services, see the instructions in the Troubleshooting Ethernet Services Configured on a Per NE Basis section.

To troubleshoot an Ethernet service fault, you must be familiar with the characteristics, working mode, and configured protocols of interfaces on the Ethernet equipment.
5.9 Troubleshooting Ethernet Service on the EoS/EoPDH Plane

The Ethernet services transmitted on the EoS/EoPDH plane can be transmitted over a TDM network. The faults of the EoS/EoPDH-plane Ethernet services include service interruption and service degradation.
Fault Phenomena
The Ethernet service interruption indicates that the Ethernet service is completely interrupted. The Ethernet service deterioration indicates that the Ethernet service is abnormal. For example, the network access speed is low, the equipment delay is long, the packet loss occurs, or incorrect packets exist in the received or transmitted data.
Issue 03 (2012-07-30)
75
5 Troubleshooting
Table 5-15 Common faults of Ethernet services Symptom Ethernet services are interrupted. Alarm HARD_BAD, TEMP_ALARM, WRG_BD_TYPE, or BD_STATUS ALM_GFP_dLFD or ALM_GFP_dCSF ETH_LOS or LOOP_ALM LAG_PORT_FAIL, LAG_VC_PORT_FAIL, LCAS_TLCT, or LCAS_TLCR Ethernet services are abnormal. HARD_BAD or TEMP_ALARM FLOW_OVER LCAS_FOPT, LCAS_FOPR, LCAS_PLCT, or LCAS_PLCR Board EMS6/EFP8
Fault Causes
l 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 ports on the interconnected equipment. The configuration of the encapsulation/mapping protocol or the LCAS protocol is inconsistent 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 l l l l The equipment at the local end is faulty. The line board is faulty or has bit errors. The interconnected equipment is faulty. The network cable is faulty. The external electromagnetic interference is severe.

1. 2.
Issue 03 (2012-07-30)
Rectify the human-caused faults such as a loopback and a data configuration error. Locate the fault cause according to the equipment alarms.
5 Troubleshooting
3.
Locate the fault cause according to the RMON performance events and alarms.
Figure 5-13 Procedure for troubleshooting Ethernet service faults
Start
1 1
Incorrect operation? No
Yes
Cancel this operation
2 An equipment alarm Yes or alarm on the radio link? No 3 An Ethernet alarm? No 4 A loop formed by the Yes E-LAN service trails? No 5 Any abnormal RMON performance events? No Fault on the opposite equipment? No Troubleshoot equipment faults by performing loopbacks section by section or replacing boards Yes Yes Yes Clear the alarm
Clear the alarm
Query the port and service traffic and analyze the fault causes
Release the loop
Troubleshoot the fault according to the flow of handling RMON performance events
Troubleshoot faults on the opposite equipment
No
Is the fault rectified? Yes En d
Issue 03 (2012-07-30)
77
5 Troubleshooting
Table 5-16 Description of the procedure for troubleshooting Ethernet service faults Comment No. 1 Description Check the following points: l Whether a loopback is set for the Ethernet port l Whether a loopback is set for the transmission line l Whether the parameter settings of the Ethernet port, such as the port enabled state, working mode, and flow control, are the same as the parameter settings of the Ethernet port on the interconnected equipment l The configuration of the encapsulation/mapping protocol or the LCAS protocol is inconsistent on both ends of the link. l The timeslot binding of VCTRUNKs is inconsistent on both ends of the link. l Check whether the Ethernet protocol and the Ethernet service configuration (especially the attributes of the Ethernet port) are correct. 2 Pay special attention to the following equipment alarms: l POWER_ALM l FAN_FAIL l HARD_BAD l BD_STATUS l NESF_LOST l TEMP_ALARM l RADIO_RSL_HIGH l RADIO_RSL_LOW l RADIO_TSL_HIGH l RADIO_TSL_LOW l IF_INPWR_ABN Pay special attention to the following line alarms: l MW_LIM l MW_LOF l R_LOS l R_LOF l MS_AIS l AU_AIS l AU_LOP l B1_EXC l B2_EXC
Issue 03 (2012-07-30)
78
5 Troubleshooting
Comment No. 3
Description Pay special attention to the following alarms: l ETH_LOS l FLOW_OVER l ALM_GFP_dCSF l ALM_GFP_dLFD l FCS_ERR l LCAS_PLCT l LCAS_TLCT l LCAS_PLCR l LCAS_TLCR l LCAS_FOPT l LCAS_FOPR
If the LOOP_ALM alarm is reported after the configuring the Advanced Attributes of Ethernet Interfaces operation is performed, it indicates that the network to which Ethernet ports are connected has loops. For RMON performance events, see C Performance Event Reference.
Issue 03 (2012-07-30)
79
5 Troubleshooting
Figure 5-14 Procedure for troubleshooting an RMON performance event

Start 1 View the statistics group performance on an Ethernet port
Is there any FCS error? No Is there any collision or fragment? No Is there any PAUSE frame? No Are broadcast packets excessive? No
Yes
Rectify the fault of line bit errors
Yes
Check the working mode of the port
4 Yes Handle the flow control problem or increase the bandwidth 5
Yes
Handle the problem on excessive broadcast packets
Use a meter to perform the test
Is the test passed? No 6 Is it a MTU setting problem? No Rectify the equipment fault by loopback section by section or replacing the board
Yes
Rectify the fault of the interconnected equipment
Yes
Modify the MTU value
No
Is the fault rectified? Yes
End
Table 5-17 Description of the procedure for troubleshooting an RMON performance event Comment No. 1 Description View the statistics group performance on an Ethernet port to obtain the real-time performance statistics data of the Ethernet port.
Issue 03 (2012-07-30)
80
5 Troubleshooting
Comment No. 2
Description 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, it indicates that the hardware of the original port is faulty. Otherwise, the hardware of the Ethernet port on the equipment at the opposite end is faulty.
Check the following points: l Whether the port operating rates on the equipment at both ends are the same l Whether the working modes (full duplex or half duplex) of the Ethernet port on the equipment at both ends are the same l 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 the Ethernet port is set to auto-negotiation mode at one end, the Ethernet port must not be set to full duplex mode at the opposite end.)
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.
Check for the cause for excessive broadcast packets (for example, you have set the loopback for the Ethernet interface board or set the VB filtering table incorrectly) and solve the problem. If the problem is caused on the equipment at the opposite end, set the threshold of broadcast packet suppression for an Ethernet port to reduce broadcast packets. Test the MTU of the network by using a test meter. The maximum frame length that is set for a port should be longer than the MTU of the network.

To troubleshoot an Ethernet service fault, you must be familiar with the characteristics, working mode, and configured protocols of interfaces on the Ethernet equipment.
5.10 Troubleshooting MPLS Tunnels

This section describes how to troubleshoot MPLS tunnels by using the MPLS OAM function or MPLS Ping/Traceroute function.
Fault Phenomena
Common faults of MPLS tunnels are as follows:
5 Troubleshooting
l l l
MPLS tunnels fail to be created, and services are unavailable. MPLS tunnels are faulty, and services are interrupted. MPLS APS switching fails, services are interrupted, and packet loss or bit errors occur.
Table 5-18 Common faults of MPLS tunnels Symptom MPLS tunnels are faulty. Alarm HARD_BAD, TEMP_ALARM, WRG_BD_TYPE, BUS_ERR, BD_STATUS, MPLS_TUNNEL_OAMFAIL, MPLS_TUNNEL_LOCV, MPLS_TUNNEL_Excess, MPLS_TUNNEL_MISMATCH, MPLS_TUNNEL_MISMERGE, MPLS_TUNNEL_UNKNOWN, MPLS_TUNNEL_BDI, MPLS_TUNNEL_FDI, MPLS_TUNNEL_SD, MPLS_TUNNEL_SF, MPLS_TUNNEL_AIS, MPLS_TUNNEL_RDI, MPLS_TUNNEL_UNEXPMEG, MPLS_TUNNEL_UNEXPMEG, MPLS_TUNNEL_UNEXPPER AM_DOWNSHIFT MW_CFG_MISMATCH MW_LIM MW_LOF Board CSH
ISV3, ISU2, ISX2, IFU2 or IFX2
Fault Causes
l 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 l
Issue 03 (2012-07-30)
The local NE is faulty. The transmission link is faulty or has bit errors.
5 Troubleshooting
l l l
Service bandwidth decreases due to an AM downshift. The opposite NE is faulty. External electromagnetic interference is severe.

1. 2. 3. 4. Check whether the data is modified, whether the line is looped back, and whether any boards are replaced. Handle the link alarms on the MPLS server trail. Locate the faulty section by using the LSP Traceroute or MPLS-TP OAM function. Locate the fault by replacing boards.
Figure 5-15 Procedure for troubleshooting MPLS tunnels
Start
Any incorrect operation? No
Yes
Cancel the operation.
Any equipment- or link-related alarm? No
Yes Clear the alarm.
3 Any alarm related to MPLS tunnel ? No Any fault in interconnection equipment? No
Yes Clear the alarm using LB/LT/LSP Ping/LSP Tracerout.
Yes Handle the fault.
Troubleshoot equipment faults by performing loopbacks on sections or replacing boards.
Contact Huawei technical engineers.
No
Faults are rectified?
Yes
End
Issue 03 (2012-07-30)
83
5 Troubleshooting
Table 5-19 Description of the procedure for troubleshooting MPLS tunnels Comment No. 1 Description Check the following points: l Whether a loopback is set for E1 ports l Whether a loopback is set for the transmission link l Whether the parameter settings such as the working mode of Ethernet ports match those of the opposite NE l Whether the parameter settings such as frame format and frame mode at E1 ports match those of the opposite NE l Whether MPLS service configuration is correct, especially whether tunnel attributes are set correctly 2 Pay special attention to the following equipment alarms: l POWER_ALM l FAN_FAIL l HARD_BAD l BD_STATUS l BUS_ERR l NESF_LOST l TEMP_ALARM l RADIO_RSL_HIGH l RADIO_RSL_LOW l RADIO_TSL_HIGH l RADIO_TSL_LOW l IF_INPWR_ABN l AM_DOWNSHIFT l MW_CFG_MISMATCH Pay special attention to the following line alarms: l MW_LIM l MW_LOF l MW_BER_EXC l MW_BER_SD l MW_RDI l MW_FEC_UNCOR
Issue 03 (2012-07-30)
84
5 Troubleshooting
Comment No. 3
Description Check whether the tunnel is faulty using LSP Ping, LSP Tracerout, or MPLSTP Tunnel OAM. Pay special attention to the following alarms: l MPLS_TUNNEL_BDI l MPLS_TUNNEL_Excess l MPLS_TUNNEL_FDI l MPLS_TUNNEL_LOCV l MPLS_TUNNEL_MISMATCH l MPLS_TUNNEL_MISMERGE l MPLS_TUNNEL_OAMFAIL l MPLS_TUNNEL_SD l MPLS_TUNNEL_SF l MPLS_TUNNEL_UNKNOWN l MPLS_TUNNEL_AIS l MPLS_TUNNEL_RDI l MPLS_TUNNEL_UNEXPMEG l MPLS_TUNNEL_UNEXPMEP l MPLS_TUNNEL_UNEXPPER

Learn about the working principle and protocol configuration of MPLS tunnels before troubleshooting MPLS tunnels.
5.11 Troubleshooting CES Services

This 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 if they have packet loss or incorrect packets. Table 5-20 Common faults of CES services Symptom CES services are interrupted. Alarm HARD_BAD, TEMP_ALARM, WRG_BD_TYPE, BUS_ERR, BD_STATUS, CES_LOSPKT_EXC Board CSH, ML1, MD1
Issue 03 (2012-07-30)
85
5 Troubleshooting
Symptom
Alarm AM_DOWNSHIFT MW_CFG_MISMATCH
Board ISU2, ISX2, IFU2, or IFX2
CES services are degraded.
HARD_BAD, TEMP_ALARM, CES_JTROVR_EXC, CES_JTRUDR_EXC, CES_MALPKT_EXC, CES_MISORDERPKT_EX C, CES_STRAYPKT_EXC AM_DOWNSHIFT MW_CFG_MISMATCH
CSH, ML1, MD1
ISU2, ISX2, IFU2, or IFX2
Fault Causes
l 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 l l l l l l The clock source is asynchronous. Jitters and delays on the network are too great. The local NE is faulty. The transmission link is faulty or has bit errors. Service bandwidth decreases due to an AM downshift. The opposite NE is faulty. External electromagnetic interference is severe.

1. 2. Check whether the data is modified, whether the line is looped back, and whether any boards are replaced. 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 the MPLS tunnel works properly, check whether the PW has the same configuration at both ends. If the configuration is the same, replace the board on the NNI side. 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. Check whether UNI-side data and CE-side data are consistent. Analyze the RMON performance events of CES services. Check whether there is impedance mismatch on channels and whether any electrical cables are connected incorrectly. Replace Smart E1 interface boards.
3. 4. 5. 6. 7.
Issue 03 (2012-07-30)
5 Troubleshooting
Figure 5-16 Procedure for troubleshooting CES services
Start
Yes
Yes Clear the alarm
3 Any alarm related to tunnels/PWs? No 4
Yes Clear the alarm
Any alarm related to CES services?
Yes Clear the alarm
Any alarm on E1 ports? No
Yes Clear the alarm
Any RMON performance event? No
Yes Handle the performance event
Any fault of interconnection with PDH equipment No
Yes Handle the fault
Troubleshoot equipment faults by performing loopbacks on sections or replacing boards
Contact Huawei technical engineers
No
Yes
End
Issue 03 (2012-07-30)
87
5 Troubleshooting
Table 5-21 Description of the procedure for troubleshooting CES services Commen t No. 1 Description Check the following points: l Whether a loopback is set for the E1 port l Whether a loopback is set for the transmission link l 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. 2 Pay special attention to the following equipment alarms: l POWER_ALM l FAN_FAIL l HARD_BAD l BD_STATUS l BUS_ERR l NESF_LOST l TEMP_ALARM l RADIO_RSL_HIGH l RADIO_RSL_LOW l RADIO_TSL_HIGH l RADIO_TSL_LOW l IF_INPWR_ABN l AM_DOWNSHIFT l MW_CFG_MISMATCH Pay special attention to the following line alarms: l MW_LIM l MW_LOF l MW_BER_EXC l MW_BER_SD l MW_RDI l MW_FEC_UNCOR
Issue 03 (2012-07-30)
88
5 Troubleshooting
Commen t No. 3
Description Pay special attention to the following alarms: l MPLS_TUNNEL_BDI l MPLS_TUNNEL_Excess l MPLS_TUNNEL_FDI l MPLS_TUNNEL_LOCV l MPLS_TUNNEL_MISMATCH l MPLS_TUNNEL_MISMERGE l MPLS_TUNNEL_OAMFAIL l MPLS_TUNNEL_SD l MPLS_TUNNEL_SF l MPLS_TUNNEL_UNKNOWN
Pay special attention to the following alarms: l CES_JTROVR_EXC l CES_JTRUDR_EXC l CES_LOSPKT_EXC l CES_MALPKT_EXC l CES_MISORDERPKT_EXC l CES_STRAYPKT_EXC
Pay special attention to the following alarms: l T_ALOS l UP_E1_AIS l LFA l LMFA l DOWN_E1_AIS l ALM_E1RAI
Pay special attention to the following alarms: l CES_MISORDERPKT l CES_LOSPKT l CES_MALPKT l CES_JTRUDR l CES_JTROVR l CES_STRAYPKT
Troubleshoot the interconnection with the PDH equipment.
Issue 03 (2012-07-30)
89
5 Troubleshooting

Learn about the working principle and protocol configuration of CES services before troubleshooting CES services.
5.12 Troubleshooting ATM Services

This 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 if they have packet loss or incorrect packets. Table 5-22 Common faults of ATM services Symptom ATM services are interrupted. Alarm HARD_BAD, TEMP_ALARM, WRG_BD_TYPE, BUS_ERR, BD_STATUS, ALM_IMA_LIF, ALM_IMA_LODS, ALM_IMA_RE_RX_UNUSABLE, ALM_IMA_RE_TX_UNUSABLE, IMA_GROUP_LE_DOWN, IMA_GROUP_RE_DOWN, LCD AM_DOWNSHIFT MW_CFG_MISMATCH ATM services are degraded. HARD_BAD, TEMP_ALARM, ALM_IMA_LIF, ALM_IMA_LODS, ALM_IMA_RE_RX_UNUSABLE, ALM_IMA_RE_TX_UNUSABLE, OCD AM_DOWNSHIFT MW_CFG_MISMATCH CSH, ML1, MD1 Board CSH, ML1, MD1
Fault Causes
l
Issue 03 (2012-07-30)
Incorrect operations are performed.

5 Troubleshooting
The transmission link is looped back. Service configuration data is inconsistent between the local end and the opposite end. Service configuration is incorrect. l l l l l The local NE is faulty. The transmission link is faulty or has bit errors. Service bandwidth decreases due to an AM downshift. The opposite NE is faulty. External electromagnetic interference is severe.

1. 2. Check whether the data is modified, whether the link is looped back, and whether any boards are replaced. 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 the MPLS tunnel works properly, check whether the PW has the same configuration at both ends. If the configuration is the same, replace the board on the NNI side. 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. Check whether UNI-side data and CE-side data are consistent. Analyze the RMON performance events of ATM services. Check whether there is impedance mismatch on channels and whether any electrical cables are connected incorrectly. Replace Smart E1 processing boards.
3. 4. 5. 6. 7.
Issue 03 (2012-07-30)
91
5 Troubleshooting
Figure 5-17 Procedure for troubleshooting ATM services
Start
Yes
Yes Clear the alarm
Yes Any alarm related to ATM services? No 4 Any alarm at the E1 port? No 5 Yes Clear the alarm Clear the alarm
Any RMON performance event? No
Yes Handle the performance event
Any fault of interconnection with PDH equipment No
Yes Handle the fault
Troubleshoot equipment faults by performing loopbacks on sections or replacing boards
Contact Huawei technical engineers
No
Yes
End
Issue 03 (2012-07-30)
92
5 Troubleshooting
Table 5-23 Description of the procedure for troubleshooting ATM services Comment No. 1 Description Check the following points: l Whether a loopback is set for the E1 port l Whether a loopback is set for the transmission link l 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 timeslot mode (30/31) are correctly configured Whether IMA parameters (including protocol version, clock mode, frame length, and maximum differential delay) are correctly configured l Check whether the network bandwidth is sufficient for the service traffic. 2 Pay special attention to the following equipment alarms: l POWER_ALM l FAN_FAIL l HARD_BAD l BD_STATUS l BUS_ERR l NESF_LOST l TEMP_ALARM l RADIO_RSL_HIGH l RADIO_RSL_LOW l RADIO_TSL_HIGH l RADIO_TSL_LOW l IF_INPWR_ABN l AM_DOWNSHIFT l MW_CFG_MISMATCH Pay special attention to the following line alarms: l MW_LIM l MW_LOF l MW_BER_EXC l MW_BER_SD l MW_RDI l MW_FEC_UNCOR
Issue 03 (2012-07-30)
93
5 Troubleshooting
Comment No. 3
Description Pay special attention to the following alarms: l ALM_IMA_LIF l ALM_IMA_LODS l ALM_IMA_RE_RX_UNUSABLE l ALM_IMA_RE_TX_UNUSABLE l IMA_GROUP_LE_DOWN l IMA_GROUP_RE_DOWN l OCD l LCD
Pay special attention to the following alarms: l T_ALOS l UP_E1_AIS l LFA l LMFA l DOWN_E1_AIS
Pay special attention to the following alarms: l ATMPW_UNKNOWNCELLS l ATM_UNCORRECTED_HCSERR
Troubleshoot the interconnection with the PDH equipment.

Learn about the working principle and protocol configuration of ATM services before troubleshooting ATM services.
5.13 Troubleshooting Ethernet Services Carried by PWs

This section describes how to troubleshoot Ethernet services that are carried by PWs and transmitted in the PSN. These Ethernet services are considered faulty when they are interrupted or deteriorate.
Fault Symptoms
Ethernet services are interrupted if they are unavailable. Ethernet services deteriorate if they have great delays, packet loss, or incorrect packets.
Issue 03 (2012-07-30)
94
5 Troubleshooting
Table 5-24 Common faults of Ethernet services Symptom Ethernet services are interrupted. Alarm HARD_BAD, TEMP_ALARM, WRG_BD_TYPE, BUS_ERR, BD_STATUS COMMUN_FAIL, LAG_DOWN ETH_LOS, ETH_EFM_LOOPBACK, or LOOP_ALM LASER_MOD_ERR Ethernet services deteriorate. HARD_BAD or TEMP_ALARM PORTMODE_MISMATCH, FLOW_OVER or LAG_MEMBER_DOWN MAC_FCS_EXC MAC_EXT_EXC DROPRATIO_OVER AM_DOWNSHIFT MAC_FCS_EXC MAC_EXT_EXC DROPRATIO_OVER ISV3, ISU2, ISX2, IFU2 or IFX2 EG4, EG4P, EM6FA, EM6F EG4, EG4P, EM6TA, EM6FA, EM6F or EM6T EG4, EG4P, EM6TA, EM6FA, EM6F or EM6T Board EG4, EG4P, EM6TA, EM6FA, EM6F or EM6T
Fault Causes
l 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 l l l l The local NE is faulty. The transmission link is faulty or has bit errors. Service bandwidth decreases due to an AM downshift. The opposite NE is faulty. External electromagnetic interference is severe.

1. Check whether the data is modified, whether the link is looped back, and whether any boards are replaced.
Issue 03 (2012-07-30)
5 Troubleshooting
2.
Check whether the PW works properly by using the PW ping or MPLS-TP PW OAM function. If the PW is faulty, check whether the MPLS tunnel works properly by using the LSP ping or MPLS-TP Tunnel OAM function. If the MPLS tunnel works properly, check whether the PW has the same configuration at both ends. If the configuration is the same, replace the boardon the NNI side. 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. Check whether UNI-side data and CE-side data are consistent. Analyze the RMON performance events of Ethernet services. Check whether there is impedance mismatch on channels and whether any electrical cables are connected incorrectly. Replace Ethernet interface board.
3. 4. 5. 6. 7.
Issue 03 (2012-07-30)
96
5 Troubleshooting
Troubleshooting Ethernet Services Configured on a Per NE Basis

Figure 5-18 Procedure for troubleshooting PW-carried Ethernet services configured on a per NE basis
Start
Yes
Cancel the operation.
Any equipmentor link-related alarm? No
Any PW-related alarm? No
Can the PW be pinged after a PW ping test is enabled? No 5 Any fault in the tunnel that carries the PW? No 6 Incorrect PW configuration? No 7 Analyze PW traffic. Yes
Yes
Handle the UNI-side fault.
Yes
Handle the tunnel fault.
Re-configure the PW.
Contact Huawei technical engineers.
No
Yes
End
Issue 03 (2012-07-30)
97
5 Troubleshooting
Table 5-25 Description of the procedure for troubleshooting PW-carried Ethernet services configured on a per NE basis No. 1 Description Check the following points: l Whether a loopback is set for the E1 port l Whether a loopback is set for the transmission link l 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 timeslot mode (30/31) are correctly configured Whether IMA parameters (including protocol version, clock mode, frame length, and maximum differential delay) are correctly configured l Check whether the network bandwidth is sufficient for the service traffic. 2 Pay special attention to the following equipment alarms: l POWER_ALM l FAN_FAIL l HARD_BAD l BD_STATUS l BUS_ERR l NESF_LOST l TEMP_ALARM l RADIO_RSL_HIGH l RADIO_RSL_LOW l RADIO_TSL_HIGH l RADIO_TSL_LOW l IF_INPWR_ABN l AM_DOWNSHIFT l MW_CFG_MISMATCH Pay special attention to the following radio link alarms: l MW_LIM l MW_LOF l MW_BER_EXC l MW_BER_SD l MW_RDI l MW_FEC_UNCOR
Issue 03 (2012-07-30)
98
5 Troubleshooting
No. 3
Description Pay special attention to the following alarms: l MPLS_TUNNEL_BDI l MPLS_TUNNEL_Excess l MPLS_TUNNEL_FDI l MPLS_TUNNEL_LOCV l MPLS_TUNNEL_MISMATCH l MPLS_TUNNEL_MISMERGE l MPLS_TUNNEL_OAMFAIL l MPLS_TUNNEL_SD l MPLS_TUNNEL_SF l MPLS_TUNNEL_UNKNOWN l MPLS_TUNNEL_AIS l MPLS_TUNNEL_RDI l MPLS_TUNNEL_UNEXPMEG l MPLS_TUNNEL_UNEXPMEP l MPLS_TUNNEL_UNEXPPER l MPLS_PW_AIS l MPLS_PW_BDI l MPLS_PW_RDI l MPLS_PW_Excess l MPLS_PW_LOCV l MPLS_PW_MISMATCH l MPLS_PW_MISMERGE l MPLS_PW_OAMFAIL l MPLS_PW_SD l MPLS_PW_SF l MPLS_PW_UNEXPMEG l MPLS_PW_UNEXPMEP l MPLS_PW_UNEXPPER l MPLS_PW_UNKNOWN
Issue 03 (2012-07-30)
99
5 Troubleshooting
No. 4
Description Check whether the PW is faulty using PW Ping. If the PW cannot be pinged, check the following points: l Whether the UNI-side hardware and cables are normal l Whether the UNI-side PWE3 service configurations are correct l Whether the working mode and tag attribute of the UNI are consistent with those at the peer port Pay special attention to the following alarms: l ETH_LOS l ETH_CFM_UNEXPERI l ETH_NO_FLOW l MAC_FCS_EXC l MAC_EXT_EXC
Check whether the MPLS tunnel is faulty using LSP Ping or LSP Tracerout. Handle tunnel faults by following the instructions in 5.10 Troubleshooting MPLS Tunnels.
6 7
Check PW configurations. If the PW configurations are incorrect, reconfigure the PW according to the network plan. Check if packet loss occurs by querying the received and transmitted packets on L2VPN PWs on the PEs at both ends. If packet loss occurs, identify the cause by querying packet loss of egress queues on all nodes of a PW. Handle UNI-side faults by following the instructions in step 4.
Issue 03 (2012-07-30)
100
5 Troubleshooting
Troubleshooting Ethernet Services Configured in an End-to-End Manner

Figure 5-19 Procedure for troubleshooting Ethernet services configured in an end-to-end manner
Start
1 Incorrect operation?
Yes
Cancel this operation.
No 2 Perform intelligent diagnosis on Ethernet services. Failure Refer to the procedure for troubleshooting Ethernet services configured on a per NE basis. Success Troubleshoot according to the relevant handling suggestions.
No
Yes
End
Table 5-26 Description of the procedure for troubleshooting Ethernet services configured in an end-to-end manner Comment No. 1 Description Check the following points: l Whether a loopback is set for the Ethernet port l Whether a loopback is set for the transmission link l Whether the Ethernet port parameters, such as port enabling/disabling status, working mode, and flow control, are configured consistently at the local end and peer end l Whether Ethernet protocol and Ethernet service configurations (especially Ethernet port attributes) are correct 2 Intelligent fault diagnosis uses OAM to implement fault diagnosis over services, PWs, and tunnels, and the physical layer, and supports the output of diagnostic results for further troubleshooting.

Learn about the working principle and protocol configuration of Ethernet services carried by PWs before troubleshooting these services.
5 Troubleshooting
5.14 Troubleshooting Orderwire Faults

If orderwire calls cannot get through when services are normal, there is an orderwire fault.
Fault Causes
l l l l l l The phone set is set incorrectly. The phone line is connected incorrectly. The orderwire is configured incorrectly. The orderwire unit is faulty. The system control unit is faulty. The line unit or radio link is faulty.

l l Check whether the phone set is set correctly, whether the phone line is connected correctly, and whether the orderwire is configured correctly. Replace the possibly faulty board to locate the fault.
Issue 03 (2012-07-30)
102
5 Troubleshooting
Figure 5-20 Procedure for troubleshooting orderwire faults
Start
Check the phone setting
Is the phone correctly set? Yes
No
Modify the phone setting
Is the phone line correctly connected? Yes

2
No
Reconnect the phone line
Check the orderwire configuration
Is the configuration correct? Yes Replace the possibly faulty board
No
Modify the configuration
No Proceed with the next step
Yes
End
Issue 03 (2012-07-30)
103
5 Troubleshooting
Table 5-27 Description of the procedure for troubleshooting orderwire faults Comment No. 1 Description 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 the orderwire 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 certain occasions, the maintenance personnel press the "TALK" button is pressed by mistake. As a result, the phone set stay in off-hook state all the time and 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 length l Whether all orderwire phone numbers on a subnet are unique l Whether the overhead bytes of all the NEs on a subnet are the same l Whether the orderwire port is set correctly 3 Replace the boards where the orderwire unit, system control unit, and line unit are located to locate the fault.

To troubleshoot orderwire faults, you must check the orderwire phone periodically.
Issue 03 (2012-07-30)
104
6 Part Replacement
6
About This Chapter
Background Information
Table 6-1 Part replacement description Part Name CQ1 SL1D, SL1DA EG4, EG4P, EM6T, EM6F, EMS6, EM6TA, EM6FA, and EFP8 CF card CST and CSH Operation 6.4 Replacing the Channelized STM-1 Processing Board
Part Replacement
Part replacement is a method frequently used to locate faults. The replacement operation varies according to the specific part type.
Tool l l l l ESD wrist strap Screwdriver U2000 Fiber remover
6.3 Replacing the SDH Optical Interface Board 6.7 Replacing the Ethernet Interface Board
6.9 Replacing the CF Card 6.10 Replacing the System Control, Switch and Timing Board 6.11 Replacing the Auxiliary Board 6.5 Replacing the PDH Interface Board l ESD wrist strap l Screwdriver l U2000
105
AUX SP3D and SP3S
Issue 03 (2012-07-30)
6 Part Replacement
Part Name ISV3, IF1, IFU2, ISX2, ISU2, and IFX2 PIU ML1 and MD1 FAN
Operation 6.8 Replacing the IF Board
Tool
6.13 Replacing the Power Board 6.6 Replacing the Smart E1 Interface Board 6.12 Replacing the Fan Board l ESD wrist strap l U2000
ODU
6.15 Replacing the ODU
l Ejector lever (torque wrench) l U2000 l Silicon l Waterproof adhesive tape
IF cable
6.16 Replacing the IF Cable
l Multimeter l Ejector lever l Electro-technical knife l File l Installation parts and accessories of the connector l IF cable l Waterproof adhesive tape
SFP
6.14 Replacing the SFP
l ESD wrist strap l Tweezer fiber remover l U2000
Issue 03 (2012-07-30)
106
6 Part Replacement
6.1 Removing a Board

Removing a board is a basic operation for replacing a board.
Procedure
Step 1 Insert one end of the ESD wrist strap into the ESD connector on the cabinet. Wear the ESD wrist strap. 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 the cables.
NOTE
Use fiber removers to remove fibers or network cables.
Issue 03 (2012-07-30)
107
6 Part Replacement
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.
Issue 03 (2012-07-30)
108
6 Part Replacement
Figure 6-4 Removing a board (2)
NOTE
As shown in Figure 6-5, there is a latch on each ejector lever of the System control Switch&Timing board. To remove the System control Switch&Timing board, you need to push the latches when pulling the ejector levers outward.
Figure 6-5 Removing the System control Switch&Timing board
3.
Pull out the board gently along the slot guide rail. Figure 6-6 Removing a board (3)
Issue 03 (2012-07-30)
109
6 Part Replacement
CAUTION
Remove 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 Board

Inserting a board is a basic operation for replacing a board.
Procedure
Step 1 Insert one end of the ESD wrist strap into the ESD connector on the cabinet. Wear the ESD wrist strap. Figure 6-7 Wear the ESD wrist strap
Step 2 Insert the board. 1. 2.

Issue 03 (2012-07-30)
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. Push the board gently along the slot guide rail until the board cannot slide further.
6 Part Replacement
Figure 6-8 Inserting a board (1)
CAUTION
Insert the board slowly to prevent the components on the boards from colliding. 3. Press the two ejector levers inward with force. Figure 6-9 Inserting a board (2)
4.
Tighten screws on the panel.
Issue 03 (2012-07-30)
111
6 Part Replacement
Figure 6-10 Inserting a board (3)
Step 3 Optional: If cables are connected to the board, recover the original cable connections according to the labels that are made previously. ----End
6.3 Replacing the SDH Optical Interface Board

When the SDH optical interface board is replaced, the unprotected services on the board are interrupted.
Prerequisites
l l l l You must know the impact of board replacement. You must know the specific position of the board to be replaced. You must know the service protection and protection channels of the board to be replaced. The spare SDH optical interface 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 board manufacturing information to obtain the version of the board to be replaced.
Tools, Equipment, and Materials

l l l l ESD wrist strap Screwdriver U2000 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 are already switched to the protection channel. 1.
Issue 03 (2012-07-30)
Query the SNCP protection group.

6 Part Replacement
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 current protection channel is normal or SD.
Step 3 Optional: If the services on the board are configured with linear MSP, ensure that the services are already switched to the protection channel. 1. 2. Query the linear MSP group. 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 current protection 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 SFP type 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 indicator should 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 forced switching. ----End
6.4 Replacing the Channelized STM-1 Processing Board

When the channelized STM-1 processing board is replaced, the unprotected services on the board are interrupted.
Prerequisites
l l l l You must know the impact of board replacement. You must know the specific position of the board to be replaced. You must know the service protection and protection channels of the board to be replaced. The spare channelized STM-1 processing 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 board manufacturing information to obtain the version of the board to be replaced.

l l l l
Issue 03 (2012-07-30)
ESD wrist strap Screwdriver U2000 Fiber remover

6 Part Replacement
Procedure
Step 1 Query the current alarms of the board. Step 2 Optional: If the services on the board are configured with linear MSP, ensure that the services are already switched to the protection channel. 1. 2. Query the linear MSP group. 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 current protection channel is normal or SD.
Step 3 Remove the board. Step 4 Check whether the version and SFP type of the spare board are the same as the version and SFP type of the board to be replaced. Step 5 Insert the board. Step 6 After the board starts to work, check the STAT indicator on the board. The STAT indicator should be on and green. Step 7 Query the current alarms of the board. There should be no new alarms on the board. Step 8 Optional: If the linear MSP switching has been performed for the services, release the forced switching. ----End
6.5 Replacing the PDH Interface Board

When the PDH interface board is replaced, the services on the board are interrupted.
Prerequisites
l l l l You must know the impact of board replacement. You must know the specific position of the board to be replaced. You must know the service protection and protection channels of the board to be replaced. The spare board must be made available, and the version and type of the spare board must be the same as those of the board to be replaced. You can query the board manufacturing information to obtain the version of the board to be replaced.

l l l ESD wrist strap Screwdriver U2000
Procedure
Step 1 Query the current alarms of the board. Step 2 Remove the board.
6 Part Replacement
Step 3 Check and ensure that the version and type of the spare board are the same as the version and type of the board to be replaced. Step 4 Insert the board. Step 5 After the board starts to work, check the indicators on the board. The STAT indicator should be on and green. Step 6 Query the current alarms of the board. There should be no new alarms on the board. ----End
6.6 Replacing the Smart E1 Interface Board

When the Smart E1 Interface board is replaced, the services on the board are interrupted.
Prerequisites
l l l l You must know the impact of board replacement. You must know the specific position of the board to be replaced. You must know the service protection and protection channels of the board to be replaced. 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 board manufacturing information to obtain the version of the board to be replaced.
Tools, Instruments and Materials

Procedure
Step 1 Query the current alarms of the board to be replaced. Step 2 Remove the board. 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 indicator is on and green.
NOTE
Smart E1 boards are hot-swappable. After the spare board is installed, it enters initialization state and starts to work 2 minutes later.
Step 6 Query the current alarms of the substitute board. There is no new alarm on the board. ----End
6 Part Replacement
6.7 Replacing the Ethernet Interface Board

When the Ethernet interface board is replaced, the unprotected services on the board are interrupted.
Prerequisites
l l l l You must know the impact of board replacement. You must know the specific position of the board to be replaced. You must know the service protection and protection channels of the board to be replaced. The spare board must be made available, and the version and type of the spare board must be the same as those of the board to be replaced. You can query the board manufacturing information to obtain the version of the board to be replaced.

Procedure
Step 1 Query the current alarms of the board. Step 2 Optional: If the services are configured with MPLS APS, ensure that the services are already switched to the protection tunnel. 1. 2. Querying MPLS APS Status. 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 already switched to the protection PW. 1. 2. Querying PW APS Status. If the board functions as the current working board, perform the forced switching.
Step 4 Remove the board. Step 5 Check and ensure that the board version and the model of the SFP module on the spare board are the same as the board version and the model of the SFP module on the board to be replaced. Step 6 Insert the board.
NOTE
Ethernet interface boards are hot-swappable. After the substitute board is installed, it enters initialization state and 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 static ARP table entries of the opposite NE.
Step 7 After the board starts to work, check the indicators on the board. The STAT indicator should be on and green.
6 Part Replacement
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 for the services, release the forced switching. ----End
6.8 Replacing the IF Board

When the IF board is replaced, the unprotected services on the board are interrupted.
Prerequisites
l l l l You must know the impact of board replacement. You must know the specific position of the board to be replaced. You must know the service protection and protection channels of the board to be replaced. 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 board manufacturing information to obtain the version of the board to be replaced.

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 are already switched to the protection channel. 1. 2. Query the SNCP protection group. If the port on the board functions as the current working channel, the current protection channel 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 service to the protection IF board. 1. 2. Query the IF 1+1 protection group. If the board functions as the current working board, perform the forced switching.
Step 4 Optional: If the services on the radio link are configured with N+1 protection, ensure that the services are already switched to the protection IF board. 1. 2. Query the IF N+1 protection group. If the board functions as the current working board, perform the forced switching.
Step 5 Optional: If the services are configured with MPLS APS, ensure that the services are already switched to the protection tunnel. 1.
Issue 03 (2012-07-30)
Querying MPLS APS Status.

6 Part Replacement
2.
If the board functions as the current working board, perform the forced switching.
Step 6 Optional: If the services are configured with PW APS, ensure that the services are already switched to the protection PW. 1. 2. Querying PW APS Status. If the board functions as the current working board, perform the forced switching.
Step 7 Optional: If the IF board is configured with the XPIC function, see Setting the ODU Transmitter State 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.
CAUTION
To turn off the ODU-PWR switch, you need to pull the switch lever outwards slightly and then set the switch to the "O" position. Step 9 Remove the board. Step 10 Check and ensure that the version and type of the spare board are the same as the version and type of the board to be replaced. Step 11 Ensure that the ODU-PWR switch on the front panel of the spare IF board is turned off. Step 12 Insert the board. Step 13 After the board starts to work, check the indicators on the board. The STAT indicator should be on and green. Step 14 Turn on the ODU-PWR switch on the front panel of the IF board.
CAUTION
To turn on the ODU-PWR switch, you need to pull the switch lever outwards slightly and then set the switch to the "I" position. IF boards are hot-swappable. After the substitute board is installed, it enters initialization state and 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 static ARP table entries of the opposite NE. Step 15 Query the current alarms of the board. There should be no new alarms on the board. Step 16 Optional: If the forced switching has been performed for the services, release the forced switching. Step 17 Optional: If the forced protection switching has been performed for the radio link, release the forced switching.
6 Part Replacement
Step 18 If the IF board is configured with the XPIC function, see Setting the ODU Transmitter State and unmute the ODU at the opposite end. ----End
6.9 Replacing the CF Card

If the NE is configured with only one System control Switch&Timing board, all the services are interrupted during the replacement of the CF card.
Prerequisites
l l l l You must be aware of the impact of CF card replacement. You must know the specific position of the CF card to be replaced. You must be a user with "NE maintainer" authority or higher. You must obtain a spare CF card that has the same capacity as the CF card to be replaced.

l l l ESD wrist strap U2000 Fiber remover
Procedure
Step 1 Query the current alarms of the board. Step 2 Optional: If the board is configured with 1+1 protection, ensure that the services are switched from the current working board to the protection board. 1. 2. See 8.23 Switching the System Control Unit and the Cross-Connect Unit, and ensure that the current working board functions as the protection board. If the board functions as the current working board, perform the manual switching.
Step 3 Remove the board. Step 4 Remove the CF card according to the illustration in the following figure.
Issue 03 (2012-07-30)
119
6 Part Replacement
Step 5 Check the spare CF card. Step 6 Install the spare CF card according to the illustration in the following figure.
Step 7 Insert the board. Step 8 After the board starts to work, observe the indicators on the board. The STAT indicator should be on and green. Step 9 Query the current alarms of the board. There should be no new alarms. Step 10 Optional: If the manual switching has been performed on the board, release the manual switching. ----End
6.10 Replacing the System Control, Switch and Timing Board

All the services are interrupted during the period of replacing the system control switch and timing board, if the NE is configured with only one system control switch and timing board.
Prerequisites
l l l l You must be aware of the impact of board replacement. You must know the specific position of the board to be replaced. You must know the service protection and protection channels of the board to be replaced. The spare board must be made available, and the version and type of the spare board must be the same as those of the board to be replaced. You can query the board manufacturing information to learn about the version of the board to be replaced.
Impact on System
If no protection board is available, the replacement of the System Control Switch and Timing board results in service interruption.

l l l
Issue 03 (2012-07-30)
ESD wrist strap Screwdriver U2000

6 Part Replacement
Fiber remover
Context
NOTE
After the NE database is restored successfully, a cold reset is automatically performed on the NE.
Procedure
Step 1 Query the current alarms of the board. Step 2 Replace the System control Switch&Timing board. If... One System control Switch and Timing board is configured Then... 1. Notify the onsite maintenance personnel to remove the board. 2. Check and ensure that the version and type of the spare board (including the patch version) are correct.
NOTE If the spare board and the board to be replaced have different patch versions, contact Huawei engineers for loading correct patches.
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.9 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 the CF card.
NOTE l In the process of restoring the NE database, the PROG indicator on the board blinks green for about 20 minutes. l If the database restoration is successful, the NE resets automatically. After the NE resets successfully, the STAT and PROG indicators are on and green. l If the database restoration fails, the NE does not reset, and the PROG is red. In this case, contact Huawei technical support engineers for rectifying the fault. NOTE After the NE starts up normally, the STAT and PROG indicators on the board are green.
Issue 03 (2012-07-30)
121
6 Part Replacement
If... Two System control Switch and Timing boards are configured
Then... 1. Before replacing the main system control board, switch the main system control board to the protection board. For details, see 8.23 Switching the System Control Unit and the Cross-Connect Unit.
NOTE Replacing the standby system control board does not need to switch the system control board to the protection board.
2. Remove the board to be replaced. 3. Check whether the version and type of the spare board are the same as the version and type of the board to be replaced. 4. Insert the spare board. 5. Wait for about 10 minutes to complete the backup of the data on the main and standby system control units.
NOTE After 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.11 Replacing the Auxiliary Board

When the auxiliary board is replaced, the services on the auxiliary board are interrupted.
Prerequisites
l l l You must know the impact of board replacement. You must know the specific position of the board to be replaced. The spare board must be made available, and the version and type of the spare board must be the same as those of the board to be replaced. You can query the board manufacturing information to obtain the version of the board to be replaced.

Procedure
Step 1 Query the current alarms of the board.
6 Part Replacement
Step 2 Remove the board. Step 3 Check and ensure that the version and type of the spare board are the same as the version and type of the board to be replaced. Step 4 Insert the spare board. Step 5 After the board starts to work, check the indicators on the board. The STAT indicator should be on and green. Step 6 Query the current alarms of the board. There should be no new alarms on the auxiliary board. ----End
6.12 Replacing the Fan Board

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

l l ESD wrist strap U2000
Precautions
WARNING
Do not touch the blades until the fan has stopped rotating.
Procedure
Step 1 Query the current alarms of the board. Step 2 Move the cables away from the front panel of the fan board assembly. Step 3 Remove the fan board.
Issue 03 (2012-07-30)
123
6 Part Replacement
Step 4 Check and ensure that the version and type of the spare board are the same as the version and type of the board to be replaced. Step 5 Insert the standby fan board.
2
Step 6 After the board starts to work, observe the indicators on the board. The FAN indicator should be on and green. Step 7 Query the current alarms of the board. There should be no new alarms. ----End
6 Part Replacement
6.13 Replacing the Power Board

If another power board works normally during the replacement period, the services at the IDU are not affected.
Prerequisites
l l l You must be aware of the impact of board replacement. You must know the specific position of the board to be replaced. The spare board must be made available, and the version and type of the spare board must be the same as those of the board to be replaced. You can query the board manufacturing information to obtain the version of the board to be replaced.

Precautions
WARNING
Before replacing the board, you must turn off the power switch of the PDU. Do not connect the interface to the power plug. After inserting the PIU properly, insert the power plug, and then turn on the power switch of the PDU.
Procedure
Step 1 Query the current alarms of the board. Step 2 Notify the onsite maintenance personnel to turn off the output power switch on the power supply equipment. Step 3 Remove the cables connected to the board.
NOTE
When removing the power cable, press the former section of the red button and pull the red button.
Issue 03 (2012-07-30)
125
6 Part Replacement
1 2 1 2
1
Press
1 2
Press the front of the red latch. Properly move the red latch outwards.
Step 4 Remove the power board gently and horizontally along the guide rail. Step 5 Check and ensure that the version and type of the spare board are the same as the version and type of the board to be replaced. Step 6 Insert the spare board steadily along the guide rail. Step 7 Reconnect the cables between the board and the power supply equipment. Step 8 Notify the onsite maintenance personnel to turn on the output power switch on the equipment. Step 9 After the board starts to work, observe the indicators on the board. The PWR indicator should be on and green. ----End
6.14 Replacing the SFP

When the small form pluggable (SFP) is replaced, the unprotected services on the optical/ electrical port are interrupted.
Prerequisites
l l
Issue 03 (2012-07-30)
You must know the impact of SFP replacement. You must know the specific position of the SFP to be replaced.
6 Part Replacement
l l
You must know the service protection and protection channels of the SFP to be replaced. 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 board manufacturing information to obtain the version of the SFP to be replaced.
Tools, Equipment and Materials

l l l ESD wrist strap Tweezer fiber remover U2000
Procedure
Step 1 Query the current alarms of the board. Step 2 Optional: If SNCP is configured for services at the optical interface, ensure that the services are already switched to the protection channel. 1. 2. Query the status of the SNCP group. 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, perform forced switching.
Step 3 Optional: If linear MSP is configured for services at the optical interface, ensure that the services are already switched to the protection channel. 1. 2. Query the status of the linear MSP group. 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, perform forced 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 STM1 electrical module, press the blcak button first.
1 2
1 Press the unclocking button. 2 Remove the STM-1 electical module.
Step 6 Insert the standby SFP module and reconnect cables based on the record. Step 7 Query the current alarms of the board.
6 Part Replacement
There should be no new alarms on the board. 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 forced switching. ----End
6.15 Replacing the ODU

When the ODU is replaced, the unprotected services on the ODU are interrupted.
Prerequisites
l l l You must know the impact of ODU replacement. You must know the specific positions of the ODU to be replaced and the IF board connected to the ODU. The spare ODU must be at hand, whose type must be the same as the type of the ODU to be replaced.

l l l l Ejector lever (torque spanner) U2000 Silicon 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. The interface of the coupler ejects little RF radiation, thus meeting the safety standards for microwave radiation. Do not damage the coating when you replace an ODU. In the case of any coating damage, repair the coating timely.
Procedure
Step 1 Query the current alarms on the ODU and then record the results. Step 2 Turn off the ODU-PWR switch on the front panel of the IF board. Step 3 Remove the IF cable and the PGND cable from the ODU. Step 4 Remove the ODU. Option If...
Issue 03 (2012-07-30)
Description Then...
6 Part Replacement
Option You need to remove the RTN 600 ODU with a waveguide interface You need to remove the RTN 600 ODU with a coaxial interface
Description Loosen the four latches of the ODU and disconnect the ODU from the antenna, the hybrid coupler, or ODU adapter. Remove the ODU from the post.
You need to remove the RTN XMC ODU Loosen the captive screws on the ODU and disconnect the ODU from the antenna, the hybrid 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 If... You need to install a new RTN 600 ODU with a waveguide interface You need to install a new RTN 600 ODU with a coaxial interface Description Then... See the RTN 600 ODU Quick Installation Guide. See the RTN 600 ODU Quick Installation Guide.
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 9 Turn on the ODU-PWR switch on the front panel of the IF board. Step 10 After the ODU starts to work, check the LINK indicator and ODU 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.16 Replacing the IF Cable

When the IF cable is replaced, the unprotected services on the IF cable are interrupted.
Prerequisites
l l l You must know the impact of IF cable replacement. You must know the specific positions of the IF cable to be replaced and the IF board connected to the IF jumper. In the case of the RG-8U IF cable or the 1/2-inch IF cable, an IF jumper is required to connect the IF cable to the IDU and both ends of the IF cable should be terminated with type-N connectors. In the case of the 5D IF cable, the IF cable is connected directly to the IDU and the cable end connecting to the IDU should be terminated with the TNC connector and the cable end connecting to the ODU should be terminated with the type-N connector.
Issue 03 (2012-07-30)
6 Part Replacement

l l l l l l l Multimeter Ejector lever Electro-technical knife File Installation parts and accessories of the connector IF cable 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 make new connectors for the IF cable or replace the IF cable with a new one. If... You need to make new connectors for the IF cable Then... See the Installation Reference and make new connectors for the IF cable.
You need to replace the IF cable with a new Replace the IF cable with a new one. 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 7 Turn on the ODU-PWR switch on the front panel of the IF board. Step 8 After the ODU starts to work, check the LINK and ODU 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
Issue 03 (2012-07-30)
130
7 Database Backup and Restoration
Database Backup and Restoration
About This Chapter

The OptiX RTN supports database backup and restoration through the NMS. 7.1 NE Database An NE database stores communication data, security data, alarm data, performance data, and configuration data of an NE in a certain structure, to facilitate data query and modification and to ensure that the data can be restored after the NE is reset. 7.2 Backing Up the Database Manually The NE configuration data is stored in the database of an NE. To prevent the database from being damaged due to certain risky operations such as replacing a faulty system control, crossconnect, and timing board or upgrading the software, you need to manually back up the database on a regular basis and before performing any risk operation. 7.3 Setting the Database Backup Policy You can set the policy of backing up a database to realize the function of periodically backing up the database. 7.4 Restoring the Database by NMS If the database is damaged, you can restore the NE database by using the database files that are saved previously.
Issue 03 (2012-07-30)
131
7.1 NE Database
An NE database stores communication data, security data, alarm data, performance data, and configuration data of an NE in a certain structure, to facilitate data query and modification and to ensure that the data can be restored after the NE is reset. Three types of NE databases are available: l Memory database (MDB) The data in the MDB varies according to the configuration and is lost when the system control 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 resident in the reserved memory. Hence, the data in the DRDB is not lost when a warm reset is performed on the system control unit. The data, however, is lost when a cold reset is performed 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.
NE Database Backup
NE configuration data, after being delivered to the system control unit, is stored in the MDB. Upon successful verification of the configuration data, the system control unit copies the data from the MDB to DRDB and delivers the data to boards. Two modes are available to back up DRDB data to the FDB: l l An NE backs up DRDB data to the FDB within five minutes after NE configuration data is modified. An NE backs up DRDB data to the FDB every 24 hours.
The following modes are available to back up FDB data: l l l Upon a scheduled backup of DRDB data to the FDB, the NE backs up FDB data to a dedicated partition of the flash memory (other than FDB0 and FDB1). On the NMS, FDB data can be backed up to an NMS server manually or at specified intervals. Upon a scheduled backup of DRDB data to the FDB, the NE backs up FDB data to a CF card.
NOTE
A CF card stores NE databases, system parameters (including NE-IPs, NE-IDs, subnet masks, and LSR IDs), software packages, and NE logs. The software packages on a CF card are synchronized with those on the system control, switching, and timing board only during package diffusion. Automatic or manual backup is not needed for software package synchronization. If the software packages on the system control, switching, and timing board are inconsistent with those in a CF card, the SWDL_CHGMNG_NOMATCH alarm is reported. Other data such as NE databases, system parameters, and NE logs are backed up regularly from an NE to a CF card.
Issue 03 (2012-07-30)
132

NOTE
When you use the NMS to back up FDB data, system parameters such as NE-IPs, NE-IDs, or subnet masks are not backed up, but LSR IDs are backed up.
NE Database Restoration
l When an NE is warm reset, the system control unit checks whether configuration data is available in the DRDB. If configuration data is available in the DRDB, the system control unit restores data from the DRDB. If the configuration data in the DRDB is damaged, the system control unit restores data from FDB0 and FDB1. When the NE is cold reset, the system control unit restores data from FDB0 and FDB1. When the data in both FDB0 and FDB1 is damaged, data can be restored from the CF card. On the NMS, the FDB data in flash memory can be restored from an NMS server without interruption of TDM services. After you press the CRV button on the system control, switching, and timing board and hold it for 8 seconds, the data stored on the CF card will be loaded to the board.
l l l l
7.2 Backing Up the Database Manually

The NE configuration data is stored in the database of an NE. To prevent the database from being damaged due to certain risky operations such as replacing a faulty system control, crossconnect, and timing board or upgrading the software, you need to manually back up the database on a regular basis and before performing any risk operation.
Prerequisites
l l You must be an NM user with NE monitor authority or higher. You must log in to the NE.

U2000
NOTE
The Web LCT does not support this operation.
Procedure
Step 1 On the NMS, choose Administration > NE Software Management > NE Data Backup/ Restoration from the Main Menu.
Issue 03 (2012-07-30)
133
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 database backup. 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.
Issue 03 (2012-07-30)
134
Step 7 Click Start to start backing up the NE data. In NE View, Operation Status indicates the progress of 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 Policy

You can set the policy of backing up a database to realize the function of periodically backing up the database.
Precautions
NOTE
During the database backup by the NMS, do not recover or backup data by USB flash drive.
7.3.1 Setting the User-Defined Backup Policy

Through this task, you can set the backup policy for a specific NE.
Prerequisites
l l You must be an NM user with NE monitor authority or higher. You must log in to the NE.

U2000
NOTE
Each NE has a default data backup policy.
l l l l
Database packages are backed up once at 2:00. The default backup policy is disabled by default. A maximum of five database packages can be backed up at a time. Data changes do not trigger any backup operations.
Procedure
Step 1 Choose Administration > NE Software Management > NE Backup Policy Management from 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 Step 5 Optional: Click to import the information of the NEs. 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 within the 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 state although the policy period reaches the specified period, day, and time.
Step 9 Click Advanced Settings, and set Backup Type, Max Backup Num, and Configuration Change 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 Device

Through this task, you can set the backup policy of a device to the running state.
Prerequisites
You must be an NM user with NE monitor authority or higher.

U2000
NOTE
Procedure
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 Right click the selected NE, Click Enable Backup Policy. ----End
7.3.3 Disable the Backup Policy of the Device

Through this task, you can set the backup policy of a device to the suspended state.
Prerequisites

U2000
NOTE
Procedure
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 Right click the selected NE, Click Disable Backup Policy. ----End
7.4 Restoring the Database by NMS

If the database is damaged, you can restore the NE database by using the database files that are saved previously.
Prerequisites
l l l You must be an NM user with NE maintainer authority or higher. The data to be restored must be backed up. You must log in to the NE.

U2000
Issue 03 (2012-07-30)
139
Precautions
NOTE
During the database restoring by the NMS, do not recover or backup data by USB flash drive.
Procedure
Step 1 On the NMS, choose Administration > NE Software Management > NE Data Backup/ Restoration from the Main Menu.
NOTE
The equivalent operations on the Web LCT are as follows: In NE List, click In Login, click OK. For the DC, the default user name is szhw and the default password is nesoft. For the license tool, the default user name is lct and the default password is password. If the user name or password has been changed, use the latest one. .
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 restore databases. 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. Click OK. 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 operation is 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 the database is activated, Operation Status indicates that the operation is successful. ----End
Issue 03 (2012-07-30)
141
8 Supporting Task
8
About This Chapter
Supporting Task
This chapter describes the common maintenance operations. 8.1 Hardware Loopback Hardware loopback refers to the loopback operation performed by changing the physical connection. 8.2 Cleaning Fiber Connectors and Adapters The optical connectors are easily contaminated in the maintenance process. The minute dust particles that can be seen only in the microscope can also affect the quality of optical signals. In this case, the system performance deteriorates. Hence, the fiber connectors or adapters that are terminated need to be cleaned in time. 8.3 Browsing Alarms, Abnormal Events, and Performance Events The is used to browse alarms, abnormal events, and performance events at the network layer. 8.4 Using the RMON Remote monitoring (RMON) is mainly used to monitor the data traffic on a network segment or on the entire network. Currently, it is one of the widely used network management standards. 8.5 Setting Alarm and Performance Management Functions The OptiX RTN 950 supports various alarm and performance management functions. 8.6 Querying a Report You can obtain the version, manufacture, and microwave link information of all the boards by querying the corresponding report. 8.7 Software Loopback Software 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 is used more widely than hardware loopback. 8.8 Reset Reset is an important method of troubleshooting software faults. Reset is classified into cold reset, warm reset. 8.9 PRBS Test
8 Supporting Task
The pseudorandom binary sequence (PRBS) test is an important method of network maintenance and self-check. 8.10 Querying the License Capacity You can check whether the loaded license file meets the requirements by querying the license capacity. 8.11 Scanning Interfering Signals You can learn whether intra-frequency or inter-frequency interference exists by scanning frequency spectra in microwave channels. 8.12 Setting the On/Off State of the Laser When performing operations such as testing a fiber cut, you can set the on/off state of the laser rather than removing and re-inserting the optical fiber on site. 8.13 Setting the ALS Function The SDH optical interface board supports the automatic laser shutdown (ALS) function. This function enables the board to turn off a laser when the board does not transmit services, the optical fiber is faulty, or the received optical signals are lost. 8.14 Setting the Automatic Release Function To protect the communication between the NMS and NE against improper operations, an NE supports the automatic release of the ODU muting, software loopback, and other operations that require you to exercise caution. The automatic release time is five minutes by default. You can set whether to enable the automatic release function and the automatic release time through the NMS. 8.15 Querying Power Consumption of Boards This section describes how to query power consumption of the ODU and each board. 8.16 Querying the Impedance of an E1 Channel The impedance of an E1 channel is 75 ohms or 120 ohms. 8.17 Monitoring Ethernet Packets Through Port Mirroring To monitor and analyze the Ethernet packets at a port, you can enable the port mirroring function so that the received or transmitted packets on the port are duplicated to another Ethernet port to which the Ethernet tester is connected. Then, you can monitor and analyze the packets. This function is supported by the EFP8/EMS6 board. 8.18 Querying the Attributes of an Ethernet Port Through the operation, you can learn about the attributes of an Ethernet port, such as rate. 8.19 Setting Traffic, Physical Bandwidth, or Bandwidth Utilization of Ethernet Ports To query the traffic, physical bandwidth, or bandwidth utilization of Ethernet ports within a certain period, you need to enable the monitoring for the object before that period starts. The FE/GE ports and ports on the packet plane support this operation. 8.20 Querying Traffic, Physical Bandwidth, or Bandwidth Utilization This section describes how to query the change curve of the traffic, physical bandwidth, or bandwidth utilization within a certain period. The FE/GE ports and ports on the packet plane support this operation. 8.21 Setting the Threshold of Received Traffic Flow on an Ethernet Port The FLOW_OVER alarm is reported when the traffic flow received on an Ethernet port exceeds the specified threshold. Only the FE port on the EFP8 board supports this operation. 8.22 Using the Ethernet Test Frames By using the Ethernet test frames, you can check the connectivity of VCTRUNKs. Only the EFP8 board supports this operation.
8 Supporting Task
8.23 Switching the System Control Unit and the Cross-Connect Unit When the is configured with two system control, cross-connect, and timing boards, you can manually switch the system control unit and the cross-connect unit as required. 8.24 Using IP Ping Commands to Locate Ethernet Service Faults The OptiX RTN 950 can respond to IP ping commands, facilitating Ethernet fault diagnosis. 8.25 End-to-End Management on Fibers, Tunnels, and PWE3 Services This section describes the common maintenance operations for end-to-end management on fibers, MPLS tunnels, and PWE3 services.
Issue 03 (2012-07-30)
144
8 Supporting Task
8.1 Hardware Loopback

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

The optical connectors are easily contaminated in the maintenance process. The minute dust particles that can be seen only in the microscope can also affect the quality of optical signals. In this case, the system performance deteriorates. Hence, the fiber connectors or adapters that are terminated need to be cleaned in time.
8.2.1 Cleaning Fiber Connectors by Using Cartridge Cleaners

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

Cartridge cleaner
Procedure
Step 1 Press down and hold the lever. Then, the shutter slides back and exposes a new cleaning area.
Issue 03 (2012-07-30)
145
8 Supporting Task
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 the downward 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.
8 Supporting Task
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 Tissue

When there is no cartridge cleaners, use the lens tissue for cleaning fiber connectors.
Prerequisites
l l Disconnect both ends of the fiber. ensure that there is no laser light on the fiber connectors. Inspect the fiber connector with a fiber microscope to ensure that the fiber connectors are contaminated.

l l l Clean solvent Non-woven lens tissue 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.
Issue 03 (2012-07-30)
147
8 Supporting Task
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 Sticks

The fiber adapters need to be cleaned with optical cleaning sticks. This section describes the method of cleaning fiber adapters on the optical interface board. The same method can be used to clean fiber adapters on the optical attenuators and flanges.
Prerequisites
l l 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.12 Setting the On/Off State of the Laser. Inspect the fiber adapter with a fiber microscope to ensure that the fiber adapter is contaminated.
Issue 03 (2012-07-30)
8 Supporting Task

l l l Optical cleaning sticks Clean solvent 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 the case 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 five times. Ensure that there is direct contact between the stick tip and fiber tip so that the solvent can clean the adapter tip. Step 3 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 Performance Events

The is used to browse alarms, abnormal events, and performance events at the network layer.
8.3.1 Checking the NE Status

You can learn about the basic information such as whether the NE fails to communicate with the NMS and whether any alarms are reported by checking the NE status.
Prerequisites
You must be an NM user with NE maintainer authority or higher.

U2000
8 Supporting Task
Precautions
NOTE
By default, the color of the NE icon on the U2000 indicates the NE status.
Procedure
Step 1 In Main Topology, select the required NE.
NOTE
Step 2 In Main Topology, click

NOTE
Skip this step when the Web LCT is used for configuration.
Step 3 Click the Attribute tab.
Issue 03 (2012-07-30)
150

NOTE
8 Supporting Task
The equivalent operations on the Web LCT are as follows: 1. In NE List, check Communication Status of the NE. 2. If Login Status of the NE is Not Logged In, log in to the NE. 3. Select the desired NE, and choose NE Login. 4. Specify User Name and Password.
NOTE
The user name is lct by default. User lct has the authority at the system level. The password of user lct is password by default.
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 description at the Legend tab.
----End
8.3.2 Checking the Board Status

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

U2000
Procedure
Step 1 On the Main Topology, double-click the desired NE. The is displayed. The NE is in Running Status.
NOTE
The equivalent operations on the Web LCT are as follows: In the NE Explorer, click the Slot Layout tab.
Step 2 Click the

NOTE
icon. The legend description is displayed.
Web LCT also supports this operation and the steps are the same as those on the U2000.
Step 3 Check the running status of the boards based on the legend description. If a board is running normally, the board icon is green. ----End
8.3.3 Browsing Current Alarms

You can find the faults that occur on the equipment by browsing current alarms.
8 Supporting Task
Prerequisites

U2000
Procedure
Step 1 Choose Fault > Browse Current Alarm from the Main Menu.
NOTE
The equivalent operations on the Web LCT are as follows: In the NE Explorer, select the required NE from the Object Tree, and then click the The Browse Current Alarms tab is displayed by default. icon on the toolbar.
Step 2 Optional: In the Filter dialog box, click the Basic Settings tab.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Issue 03 (2012-07-30)
152
8 Supporting Task
1. 2. 3. 4. 5.
In Severity, select the alarm severity to be queried. In Status, select the alarm status to be queried. In Type, select the alarm type. In Last Occurrence Time Segment, specify the alarm generation time. In Clearance Time Segment, specify the alarm clearance time.
Step 3 In the Filter dialog box, click the Alarm Source tab.
NOTE
Step 4 Select the object to be queried. Option Browse all alarms on the NE. Description Select All Objects. 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.
NOTE
Browse certain alarms on the NE. 1. Select Custom.
Step 6 Browse the displayed alarms.

NOTE
Step 7 Select the newly generated alarms, record the details of the alarms, and click Acknowledge.
8 Supporting Task
The Confirm dialog box is displayed. Step 8 Click Yes.

NOTE
Step 9 Notify the troubleshooting personnel to clear the alarms in time. For the details, see A.3 Alarms and Handling Procedures. ----End
Related Information
A current alarm refers to an alarm that is not cleared. By U2000, you can browse the network-wide alarms based on the alarm severity by clicking the alarm indicators in the upper right corner. l l l l You can click You can click You can click You can click
NOTE
(red) to browse the network-wide critical alarms. (orange) to browse the network-wide major alarms. (yellow) to browse the network-wide minor alarms. (light-blue) to browse the network-wide warning alarms.
By default, the number shown by each indicator indicates the number of current network-wide alarms, which are not cleared, of the specific severity.
By Web LCT, you can also click an alarm indicator on the toolbar to display the NE alarms of the specific severity.
From left to right, the alarm indicators and corresponding alarm severities are as follows: l l l l l Red: critical alarm Orange: major alarm Yellow: minor alarm Purple: warning Light blue: abnormal event
8.3.4 Browsing Current Performance Events of the radio link

You can learn about the current operating status of a radio link by browsing its current performance data.
Prerequisites
8 Supporting Task

U2000
NOTE
Procedure
Step 1 In the Main topology, right click the desired radio link, choose Radio Link Performance Statistics from the shortcut list.
NOTE
The equivalent operations on the Web LCT are as follows: Select the desired radio link from the Object Tree in the NE Explorer, and choose Configuration > Radio Link Performance from the Function Tree.
Step 2 Optional: Deselect Auto Refresh and click Save As... to save the exported performance data in a text format.
NOTE
----End
8.3.5 Browsing Historical Performance Data of a Radio Link

You can learn about the operating status of a radio link by browsing its historical performance data over a specific period.
Prerequisites

U2000
Procedure
Step 1 In the Main topology, right click the desired radio link, choose Radio Link Performance Statistics from the shortcut list.
NOTE
The equivalent operations on the Web LCT are as follows: Select the desired radio link from the Object Tree in the NE Explorer, and choose Configuration > Radio Link Performance from the Function Tree.
Step 2 Click the History Performance tab.
Issue 03 (2012-07-30)
155
8 Supporting Task
NOTE
Step 3 Optional: Select the Display Format for the query result. The default value is Chart.
NOTE
Step 4 Select Link Tx/Rx Power or Link Errors.

NOTE
Step 5 Optional: Click Save As... to save the exported data as a .jpg file or in a text format.
NOTE
----End
8.3.6 Browsing Current Ethernet Performance

After setting the RMON statistics group. you can browse real-time Ethernet performance statistics.
Prerequisites
l l You must be an NM user with NE operator authority or higher. The corresponding board must be added in the NE Panel.

U2000
NOTE
Procedure
Step 1 In the NE Explorer, navigate to the performance query interfaces for different objects according to the following tables.
8 Supporting Task
Table 8-1 Packet plane Performa nce Object Basic performan ce Extended performan ce MPLS tunnel performan ce MPLS Tunnel Browsed Object Ethernet porta Navigation Path
Select the corresponding board from the Object Tree in the NE Explorer. Choose Performance > RMON Performance from the Function Tree.
NOTE a: Packet Ethernet ports include FE/GE ports, Integrated IP radio ports, PORT8 on the EMS6 board, and PORT10 on the EFP8 board.
1. In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > Unicast Tunnel Management from the Function Tree. 2. Click the Static Tunnel tab. 3. Select one or more tunnels, right-click the tunnel(s), and choose Browse Performance from the shortcut menu.
L2 VPNPW performan ce
ETH PWE3 service
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-Line Service from the Function Tree. 2. Select one or more ETH PWE3 services, right-click the service (s), and choose Browse Performance from the shortcut menu.
L2 VPN performan ce
UNI-UNI E-Line service
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-Line Service from the Function Tree. 2. Select one or more UNI-UNI E-Line services, right-click the service(s), and choose Browse Performance from the shortcut menu.
CES-PW performan ce CES performan ce ATM/IMA (access side) performan ce
CES service
1. In the NE Explorer, select the NE from the Object Tree and choose Configuration > CES Service Management from the Function Tree. 2. Select one or more CES services, right-click the service(s), and choose Browse Performance from the shortcut menu.
Smart E1 port
Issue 03 (2012-07-30)
157
8 Supporting Task
Performa nce Object ATM-PW performan ce ATM PWE3 performan ce Port traffic classificati on performan ce
Browsed Object ATM PWE3 service
Navigation Path
1. In the NE Explorer, select the NE from the Object Tree and choose Configuration > ATM Service Management from the Function Tree. 2. Select one or more ATM PWE3 services, right-click the service(s), and choose Browse Performance from the shortcut menu.
Ports that perform complex traffic classificati on
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS Management > Policy Management > Port Policy from the Function Tree. 2. Click the Application Object tab. 3. Select one or multiple ports, right-click and choose Browse Performance from the shortcut menu.
NOTE Complete the operation Creating Traffic before monitoring the port traffic classification performance.
Port priority performan ce
Egress queues
For FE/GE ports: 1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Ethernet Interface from the Function Tree. 2. Click the Basic Attributes tab. 3. Select one or multiple ports, right-click and choose Browse Performance from the shortcut menu. 4. Select the desired egress queue in the Object drop-down list. For Integrated IP radio ports: 1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Microwave Interface from the Function Tree. 2. Click the Basic Attributes tab. 3. Select one or multiple ports, right-click and choose Browse Performance from the shortcut menu. 4. Select the desired egress queue in the Object drop-down list.
Port DS domain performan ce
Ports in a DS domain
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS Management > Diffserv Domain Management > Diffserv Domain Management from the Function Tree. 2. Select the desired DS domain. 3. Click the Application Object tab. 4. Select one or multiple ports, right-click and choose Browse Performance from the shortcut menu.
Issue 03 (2012-07-30)
158
8 Supporting Task
Table 8-2 EoS/EoPDH plane Performa nce Object Basic performan ce Extended performan ce VCG-other performan ce VCTRUN K port Obrowse Object Ethernet portb Navigation Path
In the NE Explorer, select the EFP8 or EMS6 board from the Object Tree and choose Performance > RMON Performance from the Function Tree.
NOTE b: EoPDH Ethernet ports include PORT1 to PORT9 on the EFP8 board. EoS Ethernet ports include PORT1 to PORT7 on the EMS6 board.
NOTE
If you browse current Ethernet performance using the Web LCT: Select the corresponding board from the Object Tree in the NE Explorer. Choose Performance > RMON Performance from the Function Tree.
Step 2 Click the Statistics Group tab. Step 3 Set the required parameters for the statistics group. 1. 2. 3. Select the desired object or port from the drop-down list. Select the performance items for which statistics need to be collected. Set Sampling Period. Sampling Period represents the time unit of the performance statistics. Step 4 Click Resetting begins.
NOTE
If you click Start, the register of the statistics group is not reset to clear the existing data.
----End
8.3.7 Browsing Historical Ethernet Performance Data

After configuring an history group, you can browse the historical performance statistics.
Prerequisites
l l l You must be an NM user with NE operator authority or higher. The corresponding boards must be added in the NE Panel. The objects and performance events to be monitored must be set.

U2000

NOTE
8 Supporting Task
Procedure
Step 1 In the NE Explorer, navigate to the performance query interfaces for different objects according to the following tables. Table 8-3 Packet plane Performa nce Object Basic performan ce Extended performan ce MPLS tunnel performan ce MPLS Tunnel Browsed Object Ethernet porta Navigation Path
ETH PWE3 service
L2 VPN performan ce
CES-PW performan ce CES performan ce
CES service
Issue 03 (2012-07-30)
160
8 Supporting Task
Performa nce Object ATM/IMA (access side) performan ce ATM-PW performan ce ATM PWE3 performan ce Port traffic classificati on performan ce
Browsed Object Smart E1 port
Navigation Path
ATM PWE3 service
Egress queues
Issue 03 (2012-07-30)
161
8 Supporting Task
Performa nce Object Port DS domain performan ce
Browsed Object Ports in a DS domain
Navigation Path
NOTE
Step 2 Click the History Group tab. Step 3 Set the parameters of the historical group. 1. 2. 3. 4. Select the desired object or port from the drop-down list. Click and specify the required time span. Select the performance items to browse. Under History Table Type, set the time span for the performance items to be browsed.
Step 4 Click Query. ----End
Issue 03 (2012-07-30)
162
8 Supporting Task
8.3.8 Browsing Abnormal Events

You can find the faults that occur on the equipment in a specific time by browsing abnormal events. An abnormal event refers to an exception that occurs on the system at a particular time rather than an exception that persists for a certain time of period.
Prerequisites

U2000
Procedure
Step 1 Choose Fault > Browse Event Logs from the Main Menu.
NOTE
The equivalent operations on the Web LCT are as follows: In the NE Explorer, select the required NE from the Object Tree, and then choose Alarm > Browse Abnormal Events from the Function Tree.
Step 2 In the Filter dialog box, click the Event Source tab.
NOTE
Step 3 Select the object to be queried. Option Description
Browse all performance events on the NE. Select All Objects. Browse certain performance events on the 1. Select Custom. NE. 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 Event Source. .
NOTE
Step 4 Click OK.

NOTE
Step 5 Browse the abnormal events. For details on how to handle an abnormal event, see B.2 Abnormal Events and Handling Procedures.

NOTE
8 Supporting Task
----End
Related Information
Being different from an alarm that has both the occurrence time and the clearance time, an abnormal event has only the occurrence time.
8.3.9 Browsing Current Performance Events

You can know the running status of the equipment by browsing current SDH/PDH performance events. The counter of current performance events measures all the performance events that arise between the start time of the monitoring period and the current time.
Prerequisites
l The performance monitoring function must be enabled. For details about how to enable the performance monitoring function, see Configuring the Performance Monitoring Status of NEs. You must be an NM user with NE maintainer authority or higher.

U2000
Procedure
Step 1 Choose Performance > Browse SDH Performance from the Main Menu, and then click the Current Performance Data tab.
NOTE
The equivalent operations on the Web LCT are as follows: In the NE Explorer, select the required board, and then choose Performance > Current Performance from the Function Tree.
Step 2 Select one or more NEs from the left pane, and click
NOTE
Step 3 Select All in Monitored Object Filter Condition.

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

NOTE
Step 5 Click the Count tab, and then select Display Continuous Severely Errored Seconds.
8 Supporting Task
NOTE
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 pointer justification events should be less than six per day. Step 7 Click the Measure tab, click Select All.
NOTE
Step 8 Click Query to browse the displayed performance events. In normal cases, compared with the history records, the gauge indicators, such as the board temperature, do not change drastically.
NOTE
Step 9 Re-define the time span by setting Monitor Period to 24-Hour.

NOTE
Step 10 Repeat Step 5 through Step 8 to query the current performance events in a period of 24 hours.
NOTE
----End
8.3.10 Browsing History Alarms

You can know the faults that occur on the equipment in a past period of time by browsing history alarms. A history alarm refers to an alarm that is already cleared.
Prerequisites
8 Supporting Task

U2000
Procedure
Step 1 Choose Fault > Browse History Alarm from the Main Menu.
NOTE
The equivalent operations on the Web LCT are as follows: In the NE Explorer, select the required NE from the Object Tree, and then click the Click the Browse History Alarms tab. icon on the toolbar.
Step 2 Optional: In the Filter dialog box, click the Basic Settings tab.
NOTE
1. 2. 3. 4.
In Severity, select the alarm severity to be queried. In Type, select the alarm type. In Occurrence Time Segment, specify the alarm generation time. In Clearance Time Segment, specify the alarm clearance time. The time span starts from the time when the last history alarm browsing operation was performed to the current time.
Step 3 In the Filter dialog box, click the Alarm Source tab.
NOTE
Step 4 Select the object to be queried.

NOTE
Issue 03 (2012-07-30)
166
8 Supporting Task
Option Browse all alarms on the NE.
Description Select All Objects. 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. .
Browse certain alarms on the NE. 1. Select Custom.
Step 5 Click OK.

NOTE
Step 6 Browse the displayed history alarms.

NOTE
----End
8.3.11 Browsing History Performance Events

You can know the faults that occur on the equipment in a past period of time by browsing history performance events.
Prerequisites
l The performance monitoring function must be enabled. For details about how to enable the performance monitoring function, see Configuring the Performance Monitoring Status of NEs. You must be an NM user with NE maintainer authority or higher.

U2000
Procedure
Step 1 Choose Performance > Browse SDH Performance from the main menu, and then click the History Performance Data tab.
NOTE
The equivalent operations on the Web LCT are as follows: In the NE Explorer, select the required board, and then choose Performance > History Performance from the Function Tree.
Step 2 Select one or more NEs from the left pane, and click
NOTE
Issue 03 (2012-07-30)
167
8 Supporting Task
Step 3 Set the parameters, such as Monitored Object Filter Condition, Monitor Period, Data Source.
NOTE
Step 4 Click the Gauge tab, and set Performance Event Type.
NOTE
Step 5 Click Query.

NOTE
Step 6 Click the Count tab, and set Performance Event Type.
NOTE
Step 7 Click Query.

NOTE
----End
8.3.12 Browsing the Performance Event Threshold-Crossing Records

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

U2000
Procedure
Step 1 Choose Performance > Browse SDH Performance from the Main Menu.
NOTE
The equivalent operations on the Web LCT are as follows: In the NE Explorer, select the required board, and then choose Performance > Performance ThresholdCrossing from the Function Tree.
Step 2 Click the Performance Threshold-Crossing Record tab.

NOTE
Step 3 Select an NE from the Object Tree in the NE Explorer. Click

Issue 03 (2012-07-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.
.
168

NOTE
8 Supporting Task
Step 4 Set the parameters such as Monitored Object Filter Condition, Monitor Period, and Performance Event Type.
NOTE
Step 5 Click Query.

NOTE
Step 6 Browse the performance event threshold-crossing records that are displayed.
NOTE
----End
8.3.13 Browsing UAT Events

Learn about the severe abnormalities on the transmission line by browsing UAT events.
Prerequisites

U2000
NOTE
Context
UAT refers to a period of 10 consecutive seconds during which the bit error ratio per second of the digital signal in either of the transmission directions of a transmission system is inferior to 10-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 Supporting Task
8.4 Using the RMON

Remote monitoring (RMON) is mainly used to monitor the data traffic on a network segment or on the entire network. Currently, it is one of the widely used network management standards.
8.4.1 Browsing Current Ethernet Performance

After setting the RMON statistics group. you can browse real-time Ethernet performance statistics.
Prerequisites
l l You must be an NM user with NE operator authority or higher. The corresponding board must be added in the NE Panel.

U2000
NOTE
Procedure
Step 1 In the NE Explorer, navigate to the performance query interfaces for different objects according to the following tables. Table 8-5 Packet plane Performa nce Object Basic performan ce Extended performan ce MPLS tunnel performan ce MPLS Tunnel Browsed Object Ethernet porta Navigation Path
Issue 03 (2012-07-30)
170
8 Supporting Task
Performa nce Object L2 VPNPW performan ce
Browsed Object ETH PWE3 service
Navigation Path
L2 VPN performan ce
CES-PW performan ce CES performan ce ATM/IMA (access side) performan ce ATM-PW performan ce ATM PWE3 performan ce Port traffic classificati on performan ce
CES service
Smart E1 port
ATM PWE3 service
Issue 03 (2012-07-30)
171
8 Supporting Task
Performa nce Object Port priority performan ce
Browsed Object Egress queues
Navigation Path
Issue 03 (2012-07-30)
172

NOTE
8 Supporting Task
Step 2 Click the Statistics Group tab. Step 3 Set the required parameters for the statistics group. 1. 2. 3. Select the desired object or port from the drop-down list. Select the performance items for which statistics need to be collected. Set Sampling Period. Sampling Period represents the time unit of the performance statistics. Step 4 Click Resetting begins.
NOTE
If you click Start, the register of the statistics group is not reset to clear the existing data.
----End
8.4.2 Configuring Ethernet Performance Threshold-Crossing Parameters

After setting the RMON alarm group. you can monitor whether the Ethernet performance value crosses its threshold for a long time.
Prerequisites
l l You must be an NM user with NE operator authority or higher. The corresponding boards must be added in the NE Panel.

U2000
NOTE
Procedure
Step 1 In the NE Explorer, navigate to the performance query interfaces for different objects according to the following tables. Table 8-7 Packet plane Performa nce Object Basic performan ce
Issue 03 (2012-07-30)
Browsed Object Ethernet porta
Navigation Path
173
8 Supporting Task
Performa nce Object Extended performan ce MPLS tunnel performan ce
Browsed Object
Navigation Path
MPLS Tunnel
ETH PWE3 service
L2 VPN performan ce
CES-PW performan ce CES performan ce ATM/IMA (access side) performan ce ATM-PW performan ce ATM PWE3 performan ce
CES service
Smart E1 port
ATM PWE3 service
Issue 03 (2012-07-30)
174
8 Supporting Task
Performa nce Object Port traffic classificati on performan ce
Browsed Object Ports that perform complex traffic classificati on
Navigation Path
Egress queues
Issue 03 (2012-07-30)
175
8 Supporting Task
NOTE
Step 2 Click the Object tab and set the corresponding parameters. Step 3 Click the Event tab and set the corresponding parameters.
NOTE
If you configure Ethernet performance threshold-crossing parameters using the Web LCT, perform the following steps: 1. Select the boards that need to report RMON performance threshold-crossing alarms. 2. Set the parameters in the Event tab page.
Step 4 Click Apply. Close the displayed dialog box. ----End
8.4.3 Configuring the Parameters for Monitoring Historical Ethernet Performance

After configuring a historical control group, you can specify how the historical Ethernet performance data is monitored. An Ethernet board monitors the historical performance data of each port at the default sampling interval of 30 minutes. An Ethernet board stores 50 historical performance data items.
Prerequisites
l l You must be an NM user with NE operator authority or higher. The corresponding boards must be added in the NE Panel.

U2000

NOTE
8 Supporting Task
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Performance > RMON History Control Group. Step 2 Set the parameters of the historical control group. Step 3 Click Apply. Close the displayed dialog box. ----End
8.4.4 Browsing Historical Ethernet Performance Data

After configuring an history group, you can browse the historical performance statistics.
Prerequisites
l l l You must be an NM user with NE operator authority or higher. The corresponding boards must be added in the NE Panel. The objects and performance events to be monitored must be set.

U2000
NOTE
Procedure
Step 1 In the NE Explorer, navigate to the performance query interfaces for different objects according to the following tables. Table 8-9 Packet plane Performa nce Object Basic performan ce Extended performan ce Browsed Object Ethernet porta Navigation Path
Issue 03 (2012-07-30)
177
8 Supporting Task
Performa nce Object MPLS tunnel performan ce
Browsed Object MPLS Tunnel
Navigation Path
ETH PWE3 service
L2 VPN performan ce
CES-PW performan ce CES performan ce ATM/IMA (access side) performan ce ATM-PW performan ce ATM PWE3 performan ce
CES service
Smart E1 port
ATM PWE3 service
Issue 03 (2012-07-30)
178
8 Supporting Task
Performa nce Object Port traffic classificati on performan ce
Browsed Object Ports that perform complex traffic classificati on
Navigation Path
Egress queues
Issue 03 (2012-07-30)
179
8 Supporting Task
NOTE
Step 2 Click the History Group tab. Step 3 Set the parameters of the historical group. 1. 2. 3. 4. Select the desired object or port from the drop-down list. Click and specify the required time span. Select the performance items to browse. Under History Table Type, set the time span for the performance items to be browsed.
Step 4 Click Query. ----End
8.5 Setting Alarm and Performance Management Functions

The OptiX RTN 950 supports various alarm and performance management functions.
8.5.1 Configuring the Performance Monitoring Status of NEs

By performing this operation task, you can manually enable or disable performance monitoring for NEs, or set the performance monitoring period.
Prerequisites
You must be an NM user with NE operator authority or higher.

U2000

NOTE
8 Supporting Task
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree, and then choose Performance > NE Performance Monitoring Time from the Function Tree. Step 2 Configure the performance monitoring parameters of the NEs. 1. 2. 3. Select 15-Minute or 24-Hour. Select Enabled or Disabled in Set 15-Minute Monitoring or Set 24-Hour Monitoring. Set the start time and end time of the performance monitoring of NEs.
NOTE
l Generally, both Set 15-Minute Monitoring and Set 24-Hour Monitoring are enabled. l You can specify the start time of the performance monitoring function, only after selecting 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.5.2 Setting Severity and Auto Reporting Status of Alarms

This section describes how to set the severity and auto reporting status of specific alarms.
Prerequisites

U2000
8 Supporting Task
Procedure
Step 1 In the NE Explorer, select the desired object.
NOTE
Step 2 Choose Alarm > Alarm Severity and Auto Reporting from the Function Tree.
NOTE
Step 3 Select any items in the column Event and set Severity and Auto Reporting Status for them.
NOTE
Step 4 Click Apply to save the settings.

NOTE
Step 5 Close the dialog box that is displayed.

NOTE
----End
8.5.3 Suppressing Alarms for Monitored Objects

This section describes how to suppress specific alarms for a specific monitored object.
Prerequisites

U2000
Procedure
Step 1 In the NE Explorer, select the desired board.
NOTE
Step 2 Choose Alarm > Alarm Suppression from the Function Tree.
8 Supporting Task
NOTE
Step 3 Set Monitored Object and click Query.

NOTE
Step 4 Set Status in Alarm Suppression.

NOTE
Step 5 Click Apply.

NOTE

NOTE
----End
8.5.4 Suppressing Alarms for NEs

This section describes how to suppress certain alarms for NEs.
Prerequisites

U2000
8 Supporting Task
Procedure
Step 1 In the NE Explorer, select the NE. Step 2 Choose Alarm > Alarm Suppression from the Function Tree.
NOTE
Step 3 Set Status in Alarm Suppression.

NOTE
Step 4 Click Apply.

NOTE

NOTE
----End
8.5.5 Reversing Alarms for Service Ports

This section describes how to reverse alarms for service ports.
Prerequisites

U2000
Procedure
Step 1 In the NE Explorer, select the NE.
NOTE
Step 2 Choose Alarm > NE Alarm Attribute from the Function Tree.
NOTE
Step 3 Set Alarm Reversion to Enable (Manually Restore).
Issue 03 (2012-07-30)
184

NOTE
8 Supporting Task
Step 4 Click Apply.

NOTE

NOTE

NOTE
Step 7 Choose Alarm > Alarm Reversion from the Function Tree.
NOTE
Step 8 Set Reversion Status for the required port.
NOTE
Step 9 Click Apply.

NOTE

NOTE
----End
8.5.6 Setting Trigger Conditions of AIS Insertion

This section describes how to set the trigger conditions of AIS insertion for specific monitored objects.
Prerequisites

U2000
8 Supporting Task
Procedure
NOTE
Step 2 Choose Alarm > QoS Alarm > AIS Insertion from the Function Tree.
NOTE
Step 3 Set the trigger conditions of AIS insertion. If you select Enabled under an alarm, the AIS signal is inserted when this alarm occurs; otherwise, the AIS signal is not inserted when this alarm occurs.
NOTE
Step 4 Click Apply.

NOTE

NOTE
----End
8.5.7 Setting Trigger Conditions of UNEQ Insertion

This section describes how to set the trigger conditions of UNEQ insertion for service ports.
Prerequisites

U2000
Procedure
NOTE
Step 2 Choose Alarm > QoS Alarm > UNEQ Insertion Switch from the Function Tree.
NOTE
Issue 03 (2012-07-30)
186
8 Supporting Task
Step 3 Set the trigger conditions of UNEQ insertion. If you select Enabled under an alarm, the UNEQ signal (all 0s) is inserted when this alarm occurs; otherwise, the UNEQ signal is not inserted when this alarm occurs.
NOTE
Step 4 Click Apply.

NOTE

NOTE
----End
8.5.8 Setting Bit Error Thresholds for Service Ports

This section describes how to set bit error thresholds for service ports.
Prerequisites

U2000
Procedure
NOTE
Step 2 Choose Alarm > QoS Alarm > Bit Error Alarm Threshold from the Function Tree.
NOTE
Step 3 Set bit error thresholds.
NOTE
Step 4 Click Apply.


NOTE
8 Supporting Task

NOTE
----End
8.5.9 Setting Monitoring and Auto-Report Status of Performance Events

This section describes how to set monitoring and auto-report status of specific performance events for monitored objects.
Prerequisites

U2000
Procedure
NOTE
Step 2 Choose Performance > Performance Monitor Status from the Function Tree.
NOTE
Step 3 Set the following parameters: Monitor Status, 15-Minute Auto-Report, and 24-Hour AutoReport.
Issue 03 (2012-07-30)
188

NOTE
8 Supporting Task
Step 4 Click Apply.

NOTE

NOTE
----End
8.5.10 Setting Performance Thresholds

This section describes how to set the thresholds of specific performance events for monitored objects.
Prerequisites

U2000
NOTE
Procedure
Step 1 In the NE Explorer, select the desired board. Step 2 Choose Performance > Performance Threshold from the Function Tree. Step 3 Set Threshold Value.
Step 4 Click Apply. Step 5 Close the dialog box that is displayed. ----End
8 Supporting Task
8.5.11 Resetting Performance Registers

This section describes how to reset performance registers. After performance registers are reset, their counts are cleared and they immediately start a new counting period.
Prerequisites

U2000
NOTE
Procedure
Step 1 In the NE Explorer, select the desired board. 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. Step 6 Close the dialog box that is displayed. ----End
8.6 Querying a Report

You can obtain the version, manufacture, and microwave link information of all the boards by querying the corresponding report.
8 Supporting Task
8.6.1 Querying the Board Information Report

You can obtain the logic version, and software version of each board by querying the board information report.
Prerequisites

U2000
Procedure
Step 1 Choose Inventory > Physical Inventory from the Main Menu.
NOTE
The equivalent operations on the Web LCT are as follows: Select the NE in the NE Explorer. Choose Report > Board Information Report from the Function Tree. All the board version information about the NE is displayed on the Board Information Report tab.
Step 2 Select Board from Physical Inventory Type in the Physical Inventory window.
NOTE
Step 3 In Physical Inventory, click the Board List tab.

NOTE
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.
Issue 03 (2012-07-30)
191

TIP
8 Supporting Task
To specify board parameters to be queried, right-click the parameter name column and choose desired parameters from the drop-down list.
NOTE
Step 6 Optional: Click Save As.

NOTE
Set the parameters in Saving Options. Step 7 Click OK. Then, you can save and archive the board information as a text file.
NOTE

NOTE
----End
8 Supporting Task
8.6.2 Querying the Board Manufacturing Information Report

You can obtain the manufacturing information about each board and the SFP module by querying the board manufacturing information report.
Prerequisites

U2000
Procedure
Step 1 Choose Inventory > Project Document > Board Manufacturer Information from the Main Menu.
NOTE
The equivalent operations on the Web LCT are as follows: Select the NE in the NE Explorer. Choose Report > Board Detail Information Report from the Function Tree. All the board manufacture information about the NE is displayed on the Board Detail Information Report tab.
Step 2 In Board Manufacturer Information, click the Board Manufacturer Information tab.
NOTE
Step 3 Select one or multiple NEs from the left pane, and click
.
193

NOTE
8 Supporting Task

NOTE
Step 5 Click Query.

NOTE
The Query processing bar is displayed. Step 6 Close the dialog box that is displayed.
NOTE
Step 7 Optional: Click Save As.

NOTE
Step 8 Set the parameters in Saving Options.

NOTE
Step 9 Click OK. Then, you can save and archive the board manufacturing information as a text file.
NOTE
----End
8.6.3 Querying the Microwave Link Information Report

You can obtain the current and recent transmit/receive power of microwave links by querying the microwave link information report.
Prerequisites

U2000
NOTE
Procedure
Step 1 In Main Menu, choose Inventory > Microwave Report > Microwave Link Report.
8 Supporting Task
Step 2 In the left pane of the Microwave Link Report tab page, choose one or more NEs, and click . Step 3 Close the dialog box that is displayed. Step 4 Optional: Click Save As. Step 5 Set the parameters in Saving Options. Step 6 Click OK. Then, you can save and archive the microwave link information as a text file. ----End
8.6.4 Querying the Network-wide License Report

By querying the network-wide license report, you can check the license information of each NE.
Prerequisites
Tools, Instruments, and Materials

U2000
NOTE
Procedure
Step 1 Choose Inventory > Microwave Report > Microwave License Capacity Report from the Main Menu.
Issue 03 (2012-07-30)
195
8 Supporting Task
Step 2 Select one or more NEs in the left pane, and click Step 3 Close the dialog box that is displayed.
Step 4 Optional: Click Save As. Save the license report as a file and archive the file properly. Step 5 Set the parameters in Saving Options. Step 6 Click OK. Then, the license report is saved and archived as a file. ----End
8.7 Software Loopback

Software 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 is used more widely than hardware loopback.
8.7.1 Setting Loopback for the SDH Optical Interface Board

The SDH optical interface board supports the optical/electrical interface inloop/outloop and the VC-4 path inloop/outloop.
Prerequisites

U2000
NOTE
Issue 03 (2012-07-30)
196
8 Supporting Task
Context
The optical/electrical interface inloop is a process wherein the signals over an SDH port are looped back at the overhead processing unit towards the backplane. Figure 8-5 Optical/electrical interface inloop
SDH optical interface board SDH
Backplane
The optical/electrical interface outloop is a process wherein the signals over an SDH port are looped back at the overhead processing unit towards the remote equipment. Figure 8-6 Optical/electrical interface outloop
Backplane SDH optical interface board SDH
The VC-4 path outloop is a process wherein the signals on a VC-4 path are looped back at the logic processing unit towards the remote equipment. Figure 8-7 VC-4 path outloop
Backplane SDH optical interface board VC-4
The VC-4 path inloop is a process wherein the signals on a VC-4 path are looped back at the logic processing unit towards the backplane.
8 Supporting Task
Figure 8-8 VC-4 path inloop

Backplane SDH optical board VC-4
Precautions
CAUTION
l The services may be interrupted at the port or on the path where the loopback is performed. l A software loopback may be released automatically after a certain period (five minutes, by defaults). For details, see 8.14 Setting the Automatic Release Function.
Procedure
Step 1 Select the SDH optical interface board from the NE Explorer. 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... Optical/electrical interface loopback VC-4 path loopback Choose... Optical(Electrical) Interface 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. Step 7 Close the dialog box that is displayed. ----End
8.7.2 Setting Loopback for the Channelized STM-1 Processing Board

The channelized STM-1 processing board supports the optical/electrical interface inloop/ outloop.
8 Supporting Task
Prerequisites

U2000
NOTE
Context
The optical/electrical interface inloop is a process wherein the signals over an STM-1 port are looped back at the overhead processing unit towards the backplane. Figure 8-9 Optical/electrical interface inloop
backplane Channelized STM-1 Processing Board VC-12
The optical/electrical interface outloop is a process wherein the signals over an STM-1 port are looped back at the overhead processing unit towards the remote equipment. Figure 8-10 Optical/electrical interface outloop
Channelized STM-1 backplane Processing Board VC-12
Issue 03 (2012-07-30)
199
8 Supporting Task
Precautions
CAUTION
Procedure
Step 1 Select the channelized STM-1 processing board from the Object Tree. Step 2 Choose Configuration > Interface Management > SDH Interface from the Function Tree. Step 3 Select Advanced Attributes tab.
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. Step 7 Close the dialog box that is displayed. ----End
8.7.3 Setting Loopback for the Tributary Board

The tributary board supports the tributary inloop and outloop.
Prerequisites

U2000
NOTE
Context
The tributary inloop is a process wherein the signals over a PDH port are looped back at the coding/decoding unit towards the backplane.
8 Supporting Task
Figure 8-11 Tributary inloop
Backplane
PDH interface board PDH
The tributary outloop is a process wherein the signals on a tributary path are looped back at the PDH interface board of the local IDU towards the remote equipment. Figure 8-12 Tributary outloop
Backplane PDH interface board PDH
Precautions
CAUTION
The 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 in the NE Explorer. 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.
8 Supporting Task
Step 5 Click Apply. Then, the Confirm dialog box is displayed. Step 6 Click OK. Step 7 Close the dialog box that is displayed. ----End
8.7.4 Setting a Loopback for the Smart E1 Processing Board

A Smart E1 processing board supports inloops and outloops on E1 ports.
Prerequisites

U2000
NOTE
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-13 E1 inloop
Smart E1 Processing Board E1
Backplane
The E1 outloop is a process wherein the signals over an E1 port are looped back from the Smart E1 processing board of the local IDU to the remote equipment. Figure 8-14 E1 outloop
Smart E1 Backplane Processing Boards E1
Issue 03 (2012-07-30)
202
8 Supporting Task
Precautions
CAUTION
l The services may be interrupted at the port or on the path where the loopback is performed. l A software loopback may be released automatically within a period (5 minutes, by default). For details, see 8.14 Setting the Automatic Release Function.
Procedure
Step 1 Select the Smart E1 processing board from the Object Tree in the NE Explorer. Step 2 Choose Configuration > Interface Management > PDH Interface from the Function Tree.
Backplane
Smart E1 Processing Board E1
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.7.5 Setting a Loopback for the Packet-plane Ethernet Interface Board

The Packet-plane Ethernet interface board supports the Ethernet port inloop (at the MAC layer and PHY layer).
8 Supporting Task
Prerequisites

U2000
NOTE
Context
The Ethernet port MAC inloop is a process wherein the Ethernet physical signals are looped back 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 back at the interface module of the board at the PHY layer towards the backplane. Figure 8-15 Ethernet port inloop
Backplane Ethernet service processing board
MAC
PHY
Precautions
NOTE
PORT 10 on the EFP8 board can not be configured with loops. PORT 8 on the EMS6 board can not be configured with loops.
CAUTION
l 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.14 Setting the Automatic Release Function.
CAUTION
When 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.
Issue 03 (2012-07-30)
204
8 Supporting Task
Procedure
Step 1 Select an Ethernet processing board from the Object Tree in the NE Explorer. Step 2 Select the corresponding function options from the Function Tree based on the loopback type. To Perform... Choose...
PHY loopback 1. Choose Configuration > Interface Management > Ethernet Interface from the Function Tree. 2. Click the Advanced Attributes tab. MAC loopback 1. Choose Configuration > Interface Management > Ethernet Interface from the Function Tree. 2. Click the Advanced Attributes tab. Step 3 Set the loopback status of the port based on the requirements. Step 4 Click Apply. Then, the Confirm dialog box is displayed. Step 5 Click OK. Step 6 Close the dialog box that is displayed. ----End
8.7.6 Setting Loopbacks for the EOS/EoPDH-Plane Ethernet Interface Board

EPF8 board supports the inloop at Ethernet ports (at the MAC layer and PHY layer) and the inloop in VC-12 paths. EMS6 board supports the inloop at Ethernet ports (at the MAC layer and PHY layer) and the inloop in VC-3 paths.
Prerequisites

U2000
NOTE
Context
A MAC layer inloop is an inloop where the service processing module loops back the Ethernet physical signals towards the backplane through the MAC layer. A PHY layer inloop is an inloop where the interface module loops back the Ethernet frame signals towards the backplane through the 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.
Issue 03 (2012-07-30)
205
8 Supporting Task
Figure 8-16 Ethernet port inloop

Backplane Ethernet service processing board
MAC
PHY
An inloop in a VC-12 path is an inloop where the logic processing unit of a board loops back the signals in a specific VC-12 path towards the backplane. Figure 8-17 VC-12 path inloop
Backplane EOPDH EFP8
An inloop in a VC-3 path is an inloop where the logic processing unit of a board loops back the signals in a specific VC-3 path towards the backplane. Figure 8-18 VC-3 path inloop
Backplane EOS EMS6
Issue 03 (2012-07-30)
206
8 Supporting Task
Precautions
CAUTION
l 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.14 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 loopback type. To Perform... PHY loopback Choose... 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. 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 Supporting Task
8.7.7 Setting Loopback for the IF Board

Loopbacks on the IF board are classified into IF port loopback, composite port loopback, and port MAC loopback. The IF1 board supports the IF port inloop, IF port outloop, composite port inloop, and composite port outloop. The IFU2/IFX2 board supports the IF port inloop, IF port outloop, composite port inloop, composite port outloop, and port MAC inloop. The ISU2/ISX2/ ISV3 board supports the IF port inloop, IF port outloop, composite port inloop, and composite port outloop.
Prerequisites

U2000
Context
The IF port inloop is a process wherein the IF signals are looped back at the modem unit towards the backplane. Figure 8-19 IF port inloop
Backplane IF signal IF board
The IF port outloop is a process wherein the IF signals are looped back at the modem unit of the board towards the remote equipment. Figure 8-20 IF port outloop
Backplane
IF board IF signal
The composite port inloop is a process wherein the microwave baseband signal is looped back at the MUX/DEMUX unit of the board towards the backplane.
8 Supporting Task
Figure 8-21 Composite port inloop

Backplane IF board
Microwave baseband signal
The composite outloop is a process wherein the microwave baseband signal is looped back at the MUX/DEMUX unit of the board towards the remote equipment. Figure 8-22 Composite port outloop
Backplane IF board Microwave baseband signal
Precautions
CAUTION
l The services may be interrupted at the port or on the path where the loopback is performed. l A software loopback may be released automatically after a certain period (five minutes, by defaults). For details, see 8.14 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 operation may fail. l Before performing the loopback operation for the IFU2/IFX2 board, disable the AM function at both ends of the radio link.
CAUTION
When Port Mode of an port is set to Layer 3, do not perform any loopback on the port. In this case, LSP Traceroute is recommended for locating faults.
Issue 03 (2012-07-30)
209
8 Supporting Task
Procedure
Step 1 Select the corresponding IF board from the Object Tree in the NE explorer.
NOTE
Step 2 Choose Configuration > Interface Management > Microwave Interface from the Function Tree.
NOTE
The equivalent operations on the Web LCT are as follows: Select the corresponding function options from the Function Tree based on the loopback type.
To Perform... IF port loopback
Choose... 1. Choose Configuration > IF Interface from the Function Tree. 2. Select IF Attributes tab. 3. Select the port where the loopback needs to be performed and set IF Port Loopback.
Composite port loopback 1. Choose Configuration > Digital Interface from the Function Tree. 2. Select By Function. 3. Choose Optical(Electrical) Interface Loopback from the drop-down list. 4. Select the port where the loopback needs to be performed and set Optical (Electrical) Interface Loopback. MAC loopback 1. Choose Configuration > Interface Management > Microwave Interface from the Function Tree. 2. Select Advanced Attributes. 3. Select the port where the loopback needs to be performed and set MAC Loopback. Step 3 Select Loopback Attributes.
NOTE
Step 4 Select the port where the loopback needs to be performed and set loopback type.
NOTE
Step 5 Click Apply.

NOTE
Then, the Confirm dialog box is displayed. Step 6 Click OK to close the dialog box.

NOTE
8 Supporting Task
Then, a dialog box is displayed. Step 7 Close the dialog box that is displayed.
NOTE
----End
8.7.8 Setting Software Loopback for the NE

This task sets the loopback for the object on an NE.
Prerequisites

U2000
NOTE
Precautions
CAUTION
Procedure
Step 1 Select the NE in the NE Explorer. Step 2 Choose Diagnoses&Maintenance > NE Lookback from the Function Tree. Step 3 Select the desired loopback status for the desired port in the table.
NOTE
Composite loopback displays as Optical(Electrical) Interface Loopback.
Issue 03 (2012-07-30)
211
8 Supporting Task
Step 4 Click Apply. ----End
8.7.9 Setting Software Loopback for the Microwave Link

This task sets the loopback for the object on a single-hop radio link.
Prerequisites

U2000
NOTE
Precautions
CAUTION
The services may be interrupted at the port or on the path where the loopback is performed.
Procedure
Step 1 Select the NE in the NE Explorer. Step 2 ChooseDiagnoses&Maintenance > Radio Link Lookback from the Function Tree. Step 3 Select the local IF board.
8 Supporting Task
Step 4 Select the desired loopback status for the desired object. Step 5 Click Apply. Then, the dialog box is displayed. Step 6 Click OK. ----End
8.7.10 Locating a Fault by Performing Loopback Operations

Loopback is a common method of locating the fault.
Prerequisites

U2000
Service Trail
Figure 8-23 shows how to locate a fault by performing a loopback operation. Figure 8-23 Service trail
PDH tributary board Cross-connect IF board board ODU ODU SDH IF Cross-connect tributary board board board
NE1
NE2
PDH Cross-connect tributary board board
IF board
ODU
ODU
IF Cross-connect board board
SDH tributary board
NE4
NE3
Optical cable
Issue 03 (2012-07-30)
213
8 Supporting Task
Precautions
The LSP Traceroute method, instead of sectional loopbacks, is recommended for locating the faults of PWE3 services.
Procedure
Step 1 If the services are available on the radio links, perform the inter-station loopbacks to narrow down the fault to a specific hop. 1. Set the outloops for the SDH optical interface boards on NE2 and NE3, and then perform the 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 narrow down the fault to a specific NE or board. 1. 2. 3. 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. 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. If the radio link is faulty, replace the IF board and ODU to check whether the IF board or ODU is faulty.
----End
8.8 Reset
Reset is an important method of troubleshooting software faults. Reset is classified into cold reset, warm reset.
8.8.1 Cold Reset

Cold reset is a process wherein the board software is reset and the board is re-initiated. During the board initialization, the FPGA, if any, is re-loaded.
Prerequisites

U2000
NOTE
Issue 03 (2012-07-30)
214
8 Supporting Task
Precautions
CAUTION
Cold reset causes service interruption because it is similar to the procedure of removing and inserting a board.
Procedure
Step 1 In Running Status of the U2000, right-click the board where the cold reset needs to be performed. Step 2 Choose Cold Reset from the shortcut menu. Then, the dialog box is displayed. Step 3 Click OK. Step 4 Close the dialog box that is displayed. ----End
8.8.2 Warm Reset

Warm reset is a process wherein the board software is reset but the board is not re-initiated.
Prerequisites

U2000
NOTE
Precautions
During warm reset, the board software is reset but the services are not interrupted.
Procedure
Step 1 In Running Status of the U2000, right-click the board where the warm reset needs to be performed. Step 2 Choose Warm Reset from the shortcut menu. Then, the dialog box is displayed. Step 3 Click OK. Step 4 Close the dialog box that is displayed. ----End
8 Supporting Task
8.9 PRBS Test

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

If a special test tool is unavailable, you can perform the PRBS test by using the embedded test system on the tributary board.
Prerequisites

U2000
Context
The OptiX RTN 950 supports the PRBS test in the tributary direction and in the cross-connect direction. The PRBS test in the tributary direction can be performed to check the connection between the tributary board and the DDF, as shown in Figure 8-24. Figure 8-24 PRBS test in the tributary direction
DDF frame PDH unit PRBS Transmitter 1 PRBS Recevicer 1 Loopback at the DDF frame
The PRBS test in the cross-connect direction can be performed to check the connection between the tributary board and the remote NE, as shown in Figure 8-25.
Issue 03 (2012-07-30)
216
8 Supporting Task
Figure 8-25 PRBS test in the cross-connect direction

a) IF board working as the line board PDH interface board PRBS transmitter 1 PRBS receiver 2 IN Cross-connect board IF board OUT IF board
NE at the local end 1 VC-4 inloop or composite port inloop 2 IF port inloop 3 IF port outloop
NE at the opposite end
b) Line board working as the SDH optical interface board PDH interface board PRBS transmitter 1 PRBS receiver 2 IN Cross-connect board OUT SDH optical interface board
NE at the local end 1 VC-4 inloop 2 Port inloop 3 Port outloop
NE at the opposite end
Precautions
CAUTION
l During the PRBS test, the services in the tested path are interrupted. l The PRBS test can be performed only in one path and in one direction at one time. l If you perform a PRBS test in the tributary direction of a port on the SP3S/SP3D board, the services carried on the other ports may be interrupted transiently.
NOTE
Procedure
Step 1 Set the loopback at the proper location. For details, see Figure 8-24 and Figure 8-25.
8 Supporting Task
Step 2 Select the E1 interface board from the NE Explorer in 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 Click Start to Test. A prompt is displayed. Step 7 Click OK. Step 8 When Process is displayed as 100%, click Query to check the test result. Step 9 On the Test Result tab page, check BitErrors and BER(%). ----End
8.9.2 Performing a PRBS Test for the IF Board

If a special test tool is unavailable, you can perform the PRBS test by using the embedded test system on the IF board.
Prerequisites

U2000
NOTE
Issue 03 (2012-07-30)
218
8 Supporting Task
Precautions
Figure 8-26 PRBS test of the IF board
IF board PRBS transmitter
ODU
ODU
IF board
1 PRBS transmitter
NE at the local end
NE at the opposite end 1 IF port outloop
CAUTION
l During the PRBS test, the services in the tested path are interrupted. l The PRBS test can be performed only in one path and in one direction 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 standby IF board to the working state.
Procedure
Step 1 Perform an outloop on the opposite IF board. For details, see 8.7.7 Setting Loopback for the IF 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 Click Start to Test. A prompt is displayed. Step 7 Click OK.

8 Supporting Task
Step 8 When Process is displayed as 100%, click Query to check the test result. Step 9 On the Test Result tab page, check BitErrors and BER(%). ----End
8.9.3 Performing a PRBS Test for the Smart E1 Processing Board

If a special test tool is unavailable, you can perform the PRBS test by using the embedded test system on the Smart E1 processing board.
Prerequisites

U2000
NOTE
Context
The OptiX RTN 950 supports the PRBS test in the UNI direction and in the NNI direction. The PRBS test in the UNI direction can be performed to check the cable connect to the Smart E1 processing board, as shown in Figure 8-27. Figure 8-27 PRBS test in the tributary direction
Smart E1 processing unit PRBS Transmitter 1 PRBS Recevicer 1 Loopback at the port
The PRBS test in the NNI direction can be performed to check the connection between the Smart E1 processing board and the remote NE, as shown in Figure 8-28.
Issue 03 (2012-07-30)
220
8 Supporting Task
Figure 8-28 PRBS test in the NNI direction

Smart E1 processing unit PRBS transmitter 1 PRBS receiver 2 IN Cross-connect Unit ETH service processing unit ETH service processing unit OUT
NE at the local end 1 ETH port inloop 2 ETH port outloop 3
NE at the opposite end ETH port inloop
Precautions
CAUTION
l During the PRBS test, the services in the tested path are interrupted. l The PRBS test can be performed only in one path and in one direction at one time. l A PRBS test can be performed for a CES service that is encapsulated in CESoPSN mode and is carried by timeslots 1 to 31 on either UNI or NNI side. l In a PRBS test in the NNI direction for an SATOP CES service, the LOOP_ALM alarm will be reported on the E1 service where this service is deployed.
NOTE
Procedure
Step 1 Set the loopback at the proper location. For details, see Figure 8-27 and Figure 8-28. Step 2 Select the E1 interface board from the Object Tree in the NE Explorer. Step 3 Choose Configuration > PRBS Test from the Function Tree. Step 4 Select the port to be tested. Step 5 Set Diraction and Frame Format.
Issue 03 (2012-07-30)
221

NOTE
8 Supporting Task
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 Click Start to Test. A prompt is displayed. Step 7 Click OK. Step 8 When Process is displayed as 100%, click Query to check the test result. Step 9 On the Test Result tab page, check BitErrors and BER(%). ----End
8.10 Querying the License Capacity

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

U2000
NOTE
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.11 Scanning Interfering Signals

You can learn whether intra-frequency or inter-frequency interference exists by scanning frequency spectra in microwave channels.
Prerequisites
l l
Issue 03 (2012-07-30)
You must be an NM user with NE maintainer authority or higher. Mute the ODU at the opposite end, before scanning the reference signal.
8 Supporting Task

U2000
Procedure
Step 1 Select the NE from Object tree in the NE Explorer.
NOTE
Step 2 Choose Diagnosis&Maintenance > ODU Frequency Scan.

NOTE
The equivalent operations on the Web LCT are as follows: Choose Diagnosis&Maintenance > ODU Frequency Scan. Set the parameters, colick Start to Scan.
Step 3 Set the parameters, click Start to Scan.

NOTE
----End
8.12 Setting the On/Off State of the Laser

When performing operations such as testing a fiber cut, you can set the on/off state of the laser rather than removing and re-inserting the optical fiber on site.
Prerequisites

U2000
NOTE
Procedure
Step 1 Select the desired SDH optical interface board or the channelized STM-1 processing board from the Object Tree in the NE Explorer.
8 Supporting Task
Operation object SDH optical interface board
Operation Steps 1. Choose Configuration > SDH Interface from the Function Tree. 2. Choose By Function. 3. Select Laser Switchfrom the drop-down list. 4. Select a port, and then set Laser Switch.
channelized STM-1 processing board
1. Choose Configuration > Interface Management > SDH Interface from the Function Tree. 2. Select Basic Attributes. 3. Select a port, and then set Laser Interface Status.
Step 2 Click Apply. A confirmation dialog box is displayed. Step 3 Click OK. A prompt is displayed. Step 4 Click OK. ----End
8.13 Setting the ALS Function

The SDH optical interface board supports the automatic laser shutdown (ALS) function. This function enables the board to turn off a laser when the board does not transmit services, the optical fiber is faulty, or the received optical signals are lost.
Prerequisites

U2000
NOTE
Procedure
Step 1 Select the desired SDH optical interface board from the Object Tree in the NE Explorer. Step 2 Choose Configuration > Automatic Laser Shutdown from the Function Tree. Step 3 Select a port, and then set Automatic Shutdown to Enabled.
8 Supporting Task
Step 4 Click Apply to save the settings. Step 5 Close the dialog box that is displayed. ----End
8.14 Setting the Automatic Release Function

To protect the communication between the NMS and NE against improper operations, an NE supports the automatic release of the ODU muting, software loopback, and other operations that require you to exercise caution. The automatic release time is five minutes by default. You can set whether to enable the automatic release function and the automatic release time through the NMS.
Prerequisites

U2000
Procedure
Step 1 Choose Configuration > NE Batch Configuration > Automatic Disabling of NE Function from 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
8.15 Querying Power Consumption of Boards

This section describes how to query power consumption of the ODU and each board.
Prerequisites

U2000
NOTE
Issue 03 (2012-07-30)
225
8 Supporting Task
Procedure
Step 1 Choose Configuration > NE Batch Configuration > Power Management from the Main Menu. 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 5 Close the dialog box that is displayed. Step 6 On the Board Power tab page, browse Nominal Power Consumption and Current Power Consumption of the selected board. ----End .
8.16 Querying the Impedance of an E1 Channel

The impedance of an E1 channel is 75 ohms or 120 ohms.
Prerequisites

U2000
NOTE
Procedure
Step 1 Select a PDH tributary board from the Object Tree in the NE Explorer. Step 2 Choose Configuration > PDH Interface from the Function Tree. Step 3 Select By Board/Port(Channel). Step 4 Select Port in the list. Step 5 Select a port, and check Port Impedance. ----End
8.17 Monitoring Ethernet Packets Through Port Mirroring

To monitor and analyze the Ethernet packets at a port, you can enable the port mirroring function so that the received or transmitted packets on the port are duplicated to another Ethernet port to which the Ethernet tester is connected. Then, you can monitor and analyze the packets. This function is supported by the EFP8/EMS6 board.
8 Supporting Task
Prerequisites

U2000
NOTE
Context
The supports the mirroring, monitoring, and analyzing of the Ethernet packets that are received or transmitted on the port. Figure 8-29 Schematic diagram of Ethernet port mirroring
Ethernet processing unit Mirroring port Ethernet equipment Duplication Monitoring port Ethernet tester
To monitor the data in different directions, port mirroring can be performed in the ingress direction and in the egress direction. For the ports on EFP8/EMS6 board: l In the ingress direction Also in the upstream direction. The equipment duplicates the packets received from the mirroring port to the observing port, and then transmits the packets from the observing port to the Ethernet tester. l In the egress direction Also in the downstream direction. The equipment duplicates the packets transmitted by the mirroring port to the observing port, and then transmits the packets from the observing port to the Ethernet tester. In the ingress direction, the ports mirror the data transmitted from the VCTRUNK to the TDM side. In the egress direction, the ports mirror the data transmitted from the TDM side to the VCTRUNK.
Procedure
Step 1 In NE Explorer, select the EFP8 or EMS6 board. Step 2 Choose Configuration > Ethernet Interface Management > Port Mirroring from the Function Tree. Step 3 Click New, and set Mirror Listener Port, Uplink Listened Port, and Downlink Listened Port.
8 Supporting Task
Step 4 Click OK. ----End
8.18 Querying the Attributes of an Ethernet Port

Through the operation, you can learn about the attributes of an Ethernet port, such as rate.
Prerequisites

U2000
Procedure
Step 1 Optional: Query the attributes of the FE or GE port on the packet plane.
NOTE
1. 2. 3. 4.
In NE Explorer, select the required NE from the Object Tree. Choose Configuration > Interface Management > Ethernet Interface from the Function Tree. Click the Advanced Attributes tab. Check the parameters such as Port Physical Parameters, Transmitting Rate, and Receiving Rate.
Step 2 Optional: Querying the attributes of the port.

NOTE
1. 2. 3. 4.
In NE Explorer, select the required NE from the Object Tree. Choose Configuration > Interface Management > Microwave Interface from the Function Tree. Click the Advanced Attributes tab. Check the parameters such as Transmitting Rate and Receiving Rate.
Step 3 Optional: Query the attributes of the external port on the EFP8 board.

NOTE
8 Supporting Task
1. 2. 3. 4. 5.
In NE Explorer, select the EFP8 board from the Object Tree. Choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. Select External Port. Click the Advanced Attributes tab. 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 to PORT8) and the attributes of the bridging port on the EFP8 board (PORT9).
----End
8.19 Setting Traffic, Physical Bandwidth, or Bandwidth Utilization of Ethernet Ports

To query the traffic, physical bandwidth, or bandwidth utilization of Ethernet ports within a certain period, you need to enable the monitoring for the object before that period starts. The FE/GE ports and ports on the packet plane support this operation.
Prerequisites
You must be an NM user with NE maintainer authority or higher. The flow monitoring function is enabled on the Ethernet port. To enable the flow monitoring function on a port, see 8.19 Setting Traffic, Physical Bandwidth, or Bandwidth Utilization of Ethernet Ports.

U2000
NOTE
After the flow monitoring function is enabled, the system saves the statistics about the received traffic and transmitted traffic with an interval of 15 minutes. In normal cases, the system stores the statistics that are collected in the last 30 days. In the system, every measurement entry shows the average transmit rate and average receive rate within a period of 15 minutes. You can query the statistics in the last 30 days.
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.
8 Supporting Task
Step 3 Select the Set Monitoring tab. Set Flow Monitoring, Physical Bandwidth Monitoring, Bandwidth Usage Monitoring to Enabled for the Ethernet port. Step 4 Click Apply. Step 5 Close the displayed Result dialog box. ----End
8.20 Querying Traffic, Physical Bandwidth, or Bandwidth Utilization

This section describes how to query the change curve of the traffic, physical bandwidth, or bandwidth utilization within a certain period. The FE/GE ports and ports on the packet plane support this operation.
Prerequisites
You must be an NM user with NE maintainer authority or higher. The flow monitoring function is enabled on the Ethernet port. To enable the flow monitoring function on a port, see 8.19 Setting Traffic, Physical Bandwidth, or Bandwidth Utilization of Ethernet Ports.

U2000
NOTE
After the flow monitoring function is enabled, the system saves the statistics about the received traffic and transmitted traffic with an interval of 15 minutes. In normal cases, the system stores the statistics that are collected in the last 30 days. In the system, every measurement entry shows the average transmit rate and average receive rate within a period of 15 minutes. You can query the statistics in the last 30 days. This operation allows only the queries about port-based Ethernet traffic by using U2000. For how to query Tunnel- or PW-based traffic, see 8.4.1 Browsing Current Ethernet Performance.
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 Display Mode.
8 Supporting Task
Step 5 Click Query. The system displays the query result in a table or in a graph. Step 6 Close the displayed Result dialog box. ----End
8.21 Setting the Threshold of Received Traffic Flow on an Ethernet Port

The FLOW_OVER alarm is reported when the traffic flow received on an Ethernet port exceeds the specified threshold. Only the FE port on the EFP8 board supports this operation.
Prerequisites

U2000
NOTE
Precautions
NOTE
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 the Function 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 Time Window. Step 6 Click Apply. ----End
8 Supporting Task
8.22 Using the Ethernet Test Frames

By using the Ethernet test frames, you can check the connectivity of VCTRUNKs. Only the EFP8 board supports this operation.
Prerequisites
l l You must be an NM user with NE maintainer authority or higher. The service traffic is encapsulated or mapped by using the GFP method.

U2000
NOTE
The 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 test frame, the Ethernet board returns the response frame. Upon receiving the response frame, the Ethernet service processing board at the local end can judge the connectivity of the VCTRUNK in between. Figure 8-30 Ethernet test frames between Ethernet boards
Test frame Local Ethernet board Remote Ethernet board
Response frame
Precautions
CAUTION
Do 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.
8 Supporting Task
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 each time.
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. Test frames are used to check the network connectivity. If some of the test frames are lost but no alarm is reported on the SDH side, you can infer that the network is normal. If all the test frames are lost, you can infer that the network is faulty. ----End
Related Information
If you choose the continue mode, the local port transmits test frames continuously until the test is disabled.
8.23 Switching the System Control Unit and the CrossConnect Unit
When the is configured with two system control, cross-connect, and timing boards, you can manually switch the system control unit and the cross-connect unit as required.
Prerequisites

U2000
NOTE
Procedure
Step 1 Select the desired NE from the Object Tree in the NE Explorer.
NOTE
Step 2 Choose Configuration > Board 1+1 Protection from the Function Tree.

NOTE
8 Supporting Task
Step 3 In 1+1 Protection List, select Cross-Connect Protection Pair.

NOTE
Step 4 Perform the 1+1 protection switching on the board. If... Active Board is set to Working Board Active Board is set to Protection Board Step 5 In the prompt that is displayed, click OK.
NOTE
Then... Click Working/Protection Switching. Click Restore Working/Protection.
----End
8.24 Using IP Ping Commands to Locate Ethernet Service Faults

The OptiX RTN 950 can respond to IP ping commands, facilitating Ethernet fault diagnosis.
Prerequisites

U2000
NOTE
Context
Two types of IP ping functions are supported: l Near-end IP ping The customer edge equipment (CE) initiates IP ping packets to a UNI port on a near-end transmission NE. The transmission NE responds to the IP ping packets. The near-end IP ping function is generally used to check whether a fault occurs on the CE or its near-end transmission NE. For example, the RNC initiates IP ping packets to the UNI port on NE1, as shown in Figure 8-31. l Far-end IP ping The customer edge equipment (CE) initiates IP ping packets to a UNI port on a far-end transmission NE. The transmission NE responds to the IP ping packets. The far-end IP ping function is generally used to check whether a fault occurs on the CE or its far-end
8 Supporting Task
transmission NE. For example, the RNC initiates IP ping packets to the UNI port on NE2, as shown in Figure 8-31. Figure 8-31 Application of the IP ping functions
Far-end IP Ping Near-end IP Ping
NodeB
NE2
NE1
RNC Near-end IP Ping
Far-end IP Ping
Precautions
l l l l IP ping can be enabled only for UNI Ethernet ports. IP ping can be enabled only for a maximum of four ports on an NE. IP ping is inapplicable for E-Aggr services. To support far-end IP ping, the protocol VLAN ID (if any) must be configured to the same value as the VLAN ID carried by IP packets initiated by the local CE. This enables NEs enabled with the IP ping function can select the correct PW for transmitting IP ping packets based on the configured protocol VLAN ID. If IP ping packets initiated by the local CE do not carry any VLAN ID (for example, when the port tag attribute is access), the protocol VLAN ID must be set to 0 or /. This enables NEs enabled with the IP ping function to select the correct service for transmitting IP ping packets based on the PVIDs of UNI ports. The CE initiating IP ping packets must support non-strict ARP learning mode. That is, the CE must be able to learn MAC addresses based on ARP request packets.
Sample IP Ping Connection

Figure 8-32 shows the test procedure, using the Ethernet service between PORT1 on NE1 and PORT1 on NE2 as an example.
Issue 03 (2012-07-30)
235
8 Supporting Task
Figure 8-32 Networking diagram

137.0.0.2/ 255.255.255.0 137.0.0.4/ 255.255.255.0 PORT 1 VLAN ID=100 NodeB NE 2 NE 1 137.0.0.3/ 255.255.255.0 PORT 1 VLAN ID=100 RNC 137.0.0.1/ 255.255.255.0
The Ethernet service between NE1 and NE2 has the VLAN ID 100. The tag attributes of both PORT1s on NE2 and NE1 are tag aware.
Procedure
Step 1 On NE1, configure IP ping parameters to implement the near-end IP ping function. 1. 2. In the NE Explorer, click the NE and choose Configuration > IP Ping Test. Set the IP ping parameters.
NOTE
If NE1 and the RNC are in the same network segment, set Next Hop IP Address to the IP address of the RNC. If NE1 and the RNC are not in the same network segment, set Next Hop IP Address to the IP address of the router port on the NE1 side.
3.
Click Apply.
Step 2 Configure the far-end IP ping agent. 1. 2. In the NE Explorer, click the NE and choose Configuration > IP Ping Test. Set the far-end IP ping agent to NE2.
3.
Click Apply.
Step 3 Refer to step 1 to configure IP ping parameters on NE 2, to implement the far-end IP ping function.
NOTE
Next Hop IP Address applies to near-end IP ping only. It is recommended to set Next Hop IP Address here to the IP address of the NodeB, so that NE2 can respond to near-end IP ping commands.
Step 4 On the RNC, initiate IP ping to the NodeB (that is, ping 137.0.0.2).
Issue 03 (2012-07-30)
236
8 Supporting Task
Option If... The operation result is normal The operation times out
Description Then... Services are normal. Therefore, end fault diagnosis. Go to the next step.
Step 5 On the RNC, initiate IP ping to NE1 (that is, ping 137.0.0.3). Option If... Description Then...
The operation result is normal Go to the next step. The operation times out A fault occurs between NE1 and the RNC. Handle the fault.
Step 6 On the RNC, initiate IP ping to NE2 (that is, ping 137.0.0.4). Option If... Description Then...
The operation result is normal A fault occurs between NE2 and the NodeB. Handle the fault. The operation times out ----End Handle the transmission network fault.
8.25 End-to-End Management on Fibers, Tunnels, and PWE3 Services

This section describes the common maintenance operations for end-to-end management on fibers, MPLS tunnels, and PWE3 services.
8.25.1 Expanding/Collapsing Fibers and Cables

If multiple fibers, cables, or tunnels are available between network elements (NEs), you can collapse them to form a link, which is displayed in the topology. You can also expand the link to display the fibers, cables, or tunnels.
Prerequisites

U2000
NOTE
Issue 03 (2012-07-30)
237
8 Supporting Task
Procedure
Step 1 Optional: Expand fibers and cables. 1. In the main topology, if an NE link is displayed as
, select the link and right-click it. Then choose Expand Link from the shortcut menu. Step 2 Optional: Collapse fibers and cables.
1.
In the main topology, if an NE link is displayed as , select the link and right-click it. Then choose Collapse Link from the shortcut menu.
----End
8.25.2 Querying Optical Power of Fibers and Cables

When fiber connections are available between network elements (NEs), you can query the optical power related to the fibers.
Prerequisites

U2000
NOTE
Procedure
Step 1 In the main topology, select the required radio link and right-click it. Then choose Query Relevant Optical Power from the shortcut menu. The Optical Power Management dialog box is displayed. Step 2 Click the Port Optical Power tab. Step 3 Click Query. The input and output optical power of the fiber is displayed in the dialog box. Step 4 In the Result dialog box that is displayed, click Close. Step 5 Click the Graphic tab to display the statistical graphics regarding optical power of the source and sink ends of a fiber. ----End
8 Supporting Task
8.25.3 Querying the Radio Link Information

When fiber links are available between network elements (NEs), you can query the relevant information about radio links.
Prerequisites

U2000
NOTE
Procedure
Step 1 In the main topology, select the required radio link and right-click it. Then choose Microwave Link Information from the shortcut menu. The Microwave Link Report dialog box is displayed. Step 2 Select the required NE or board from the object tree, and then click Step 3 Click Query. Step 4 In the Result dialog box that is displayed, click Close. ----End .
8.25.4 Querying the Radio Link Performance

When fiber links are available between network elements (NEs), you can query the relevant performance information about radio links.
Prerequisites

U2000
Procedure
Step 1 In the main topology, select the required radio link and right-click it. Then choose Radio Link Performance Statistics from the shortcut menu.
NOTE
The equivalent operations on the Web LCT are as follows: In the NE Explorer, choose the sink NE or source NE, choose Configuration > Radio Link Performance Statistics in the function.
The Radio Link Performance Statistics dialog box is displayed.

8 Supporting Task
Step 2 In the Radio Link Performance Statistics dialog box, choose Current Performance tab.
NOTE
Step 3 In the Current Performance dialog box, choose Auto Refresh to see the current performance of the radio link.
NOTE
Step 4 In the Radio Link Performance Statistics dialog box, choose History Performance tab.
NOTE
Step 5 In the Radio Link Performance Statistics dialog box, set Monitor Period, Ended From, To, and Options. Then click OK below Options.
NOTE
Step 6 Click Query.

NOTE
Step 7 Click Save as, and save the data displayed in the current dialog box.
NOTE
----End
8.25.5 Managing E-Line Services Transmitted in Native Ethernet Mode

This section describes how to perform management and maintenance operations, such as querying information about E-Line services transmitted in Native Ethernet mode and deploying/ deleting E-Line services.
Prerequisites
You must be an NM user with NE administrator authority or higher.
Procedure
Step 1 Choose Service > Native Ethernet Service > Manage E-Line Service from the Main Menu. Step 2 In the Set Filter Criteria dialog box that is displayed, set filter conditions and click Filter. The E-Line services that meet the criteria are listed in the query result. Step 3 Optional: Select the desired E-Line service from the query result, and view information in the Topology and Interface Information tab pages.
8 Supporting Task
Step 4 Optional: Select the desired E-Line service from the query result, click functional buttons under the query result or right-click the service and choose options from the shortcut menu to perform related maintenance operations. ----End
8.25.6 Managing MPLS Tunnels in an End-to-End Mode

This section describes how to perform management and maintenance operations on MPLS tunnels, such as querying tunnel information, running/deploying/deleting an MPLS tunnel, and troubleshooting MPLS tunnels.
Prerequisites
Procedure
Step 1 Choose Service > Tunnel > Manage Tunnel from the Main Menu. Step 2 In the Set Filter Criteria dialog box that is displayed, set filter conditions and click Filter. The MPLS tunnels that meet the criteria are listed in the query result. Step 3 Optional: Select a desired tunnel, and browse the tunnel information in the Topology, Hop Information, QoS Information, and Relevant Service tab pages at the bottom. Step 4 Optional: Select the desired tunnels from the query result, click functional buttons under the query result or right-click the service and choose options from the shortcut menu to perform related maintenance operations. ----End
8.25.7 Managing and Maintaining PWE3 Services

This section describes how to perform management and maintenance operations, including querying PWE3 service information, deploying or deleting a PWE3 service, and detecting PW faults.
Prerequisites
Procedure
Step 1 Choose Service > PWE3 Service > Manage PWE3 Service from the Main Menu. Step 2 In the Set Filter Criteria dialog box that is displayed, set filter conditions and click Filter. The PWE3 services that meet the criteria are listed in the query result. Step 3 Optional: Select a desired PWE3 service and browse the service information in the Topology, SAI, Service Parameter, and PW tab pages at the bottom.
8 Supporting Task
Step 4 Optional: Select the desired PWE3 service from the query result, click functional buttons under the query result or right-click the service and choose options from the shortcut menu to perform related maintenance operations. ----End
8.25.8 Verifying Native Ethernet Services

This section describes how to use ETH OAM to verify connectivity of Native Ethernet services.
Prerequisites
l l l You must be an NM user with NE operator authority or higher. Native Ethernet services are configured in end-to-end mode and ETH OAM CC are enabled. The data on the NE and the NMS is synchronized.
Procedure
Step 1 Choose Service > Native Ethernet Service > Manage Native Ethernet Service from the main menu. Step 2 In the Set Filter Criteria dialog box, set filter conditions and click Filter. The Native Ethernet services that meet the criteria are listed in the query result. Step 3 Right-click the desired Native Ethernet service, and choose Ethernet OAM > LB Test from the shortcut menu.
Step 4 Optional: If Ethernet OAM has not been configured during end-to-end E-LAN service configuration, the Prompt dialog box is displayed. 1. 2. Click Add. Set OAM parameters.
Issue 03 (2012-07-30)
242
8 Supporting Task
3.
Click OK.
Step 5 Optional: If Ethernet OAM has not been configured during end-to-end E-Line service configuration, the Prompt dialog box is displayed. Click OK. Ethernet OAM will be automatically configured. Step 6 In the LB Test dialog box, select the desired service trail.
NOTE
l An LB test checks whether a service is bidirectional available. For a bidirectional service, select the NE at either end to initiate an LB test. l If Ethernet services are in different VLANs, the U2000 automatically selects the service in a VLAN for an LB test. l One NE cannot be involved in multiple LB tests simultaneously.
Step 7 Optional: Choose Config LB Parameter from the shortcut menu. Set Sent Packets, Sent Packets Length, and Sent Packets Priority. Then, click OK.
Step 8 Click Run. Step 9 Click the LB Testing Information and LB Statistics Information tabs, and determine whether the service is available based on the displayed information. Normally, Test Results indicates Test Succeeded.
8 Supporting Task
----End
8.25.9 Verifying MPLS Tunnels in an End-to-End Mode

This section describes how to verify that an MPLS tunnel is available using the LSP ping test or LSP traceroute function.
Prerequisites
l l You must be an NM user with NE administrator authority or higher. MPLS tunnels have already been deployed.
Procedure
Step 1 Choose Service > Tunnel > Manage Tunnel from the Main Menu. Step 2 In the Set Filter Criteria dialog box that is displayed, set filter conditions and click Filter. The MPLS tunnels that meet the criteria are listed in the query result. Step 3 Right-click the tunnel to verify. Choose Test and Check from the shortcut menu.
TIP
You can select and verify several MPLS tunnels concurrently.
Step 4 Select LSP Ping or LSP Traceroute from Diagnosis Option.
Issue 03 (2012-07-30)
244
8 Supporting Task
Step 5 Optional: Click the on the right and set parameters about the LSP ping/LSP traceroute test in the dialog box that is displayed. The values for the related parameters are provided as follows. l Packet Size: Set this parameter according to requirements. l Response Mode: Set this parameter to Application Control Channel if the tunnel is bidirectional and its egress node supports reverse channel response. Set this parameter to IPv4 UDP Response if the egress node does not support reverse channel response, but support DCN channel response based on IP protocols. In other scenarios, set this parameter to No Response. l Other parameters: Other parameters take their default values.
Step 6 Click Run. Step 7 After the verification, query the verification result of each MPLS tunnel. ----End
Issue 03 (2012-07-30)
245
8 Supporting Task
8.25.10 Verifying PW Configurations in an End-to-End Mode

This section describes how to verify connectivity of a PW using the PW ping test or PW traceroute function.
Prerequisites
You must be an NM user with NE operator authority or higher.

U2000
Procedure
Step 1 Choose Service > PWE3 Service > Manage PWE3 Service from the Main Menu. The Set Filter Criteria dialog box is displayed. Step 2 Click Filter.
NOTE
After you click Filter, all configured PWE3 services will be displayed.
Step 3 Right-click the PWE3 service to verify and choose Test And Check from the shortcut menu.
The Diagnosis Option tab page is displayed. Step 4 Perform a PW service connectivity test. If... You perform a PW ping test Then... Perform Step 5 and Step 9.
You perform a PW traceroute test Perform Step 10 and Step 14. Step 5 Select VCCV Ping from the Diagnosis Option list.
Issue 03 (2012-07-30)
246
8 Supporting Task
Step 6 Click
on the right of VCCV Ping.
The VCCV ping dialog box is displayed. Step 7 Set the connectivity test parameters.
Set the parameters as follows: l Response Mode: Application Control Channel l Unless otherwise specified, it is recommended that other parameters take their default values. Step 8 Click OK. Step 9 Click Run. Step 10 Select VCCV Traceroute from the Diagnosis Option list.
Step 11 Click
Issue 03 (2012-07-30)
on the right of VCCV Traceroute.

8 Supporting Task
The VCCV Traceroute dialog box is displayed. Step 12 Set the connectivity test parameters.
Set the parameters as follows: l Response Mode: Application Control Channel l Unless otherwise specified, it is recommended that other parameters take their default values. Step 13 Click OK. Step 14 Click Run. ----End
8.25.11 Verifying PW-Based E-Line Service Configurations (in an End-to-End Mode)

This section describes how to use Ethernet OAM to verify connectivity of a PW-based E-Line service.
Prerequisites
l l You must be an NM user with NE administrator authority or higher. The Configuring PW-Based E-Line Services (in an End-to-End Mode) task has been completed.
Procedure
Step 1 Choose Service > PWE3 Service > Manage PWE3 Service from the Main Menu. Step 2 In the Set Filter Criteria window, select Source NE and Sink Node. Click Filter.
Issue 03 (2012-07-30)
248
8 Supporting Task
Step 3 Right-click the PWE3 service to verify, and choose Ethernet OAM > LB Test... from the shortcut menu.
Step 4 In the Eth Oam LB Test dialog box that is displayed, select the source NE for initiating an LB test.
NOTE
l An LB test detects whether a service is bidirectionally available. For a bidirectional service, it is recommended that you select either end of a PW as the source NE for initiating the LB test. l If a PW carries Ethernet services from different VLANs, the U2000 automatically select the service of a VLAN for the LB test.
Step 5 Optional: Right-click the service that is selected for an LB test, and choose Configure... from the shortcut menu. In the Config Eth Oam LB Test Parameter dialog box that is displayed, set Sent Packets, Sent Packets Length, and Sent Packets Priority. Then, click OK.
8 Supporting Task
Step 6 Right-click the service that is selected for an LB test, and choose Run from the shortcut menu. Step 7 Click the LB Statistic Information tab and determines whether the service is available based on the displayed information. If Test Result displays Test Succeeded, the service is available.
If Packet Loss Ratio(%) displays 100 and Test Result displays Test Failed, the service is unavailable. If the service is unavailable, check whether the service configurations are incorrect.
Issue 03 (2012-07-30)
250
8 Supporting Task
----End
8.25.12 Performing Intelligent Service Fault Diagnosis for Ethernet Services

When a fault occurs in Ethernet services, you can quickly locate the fault using the intelligent service fault diagnosis function.
Prerequisites
The intelligent service fault diagnosis function applies to end-to-end E-Line services, including both native Ethernet services and ETH pseudo wire emulation edge-to-edge (PWE3) services.
Precautions
This task uses intelligent service fault diagnosis of Ethernet PWE3 services as an example. The procedures for intelligent service fault diagnosis of native Ethernet services are similar.
Procedure
Step 1 Choose Service > PWE3 Service > Manage PWE3 Service from the main menu.
NOTE
For intelligent service fault diagnosis of native Ethernet services, choose Service > Native Ethernet Service > Manage Ethernet Service from the main menu.
Step 2 In the dialog box that is displayed, set filter criteria and click Filter. If click Filter without seting filter criteria, all Ethernet PWE3 services are displayed. Step 3 Right-click the target service and choose Diagnose > Service Fault Diagnosis from the shortcut menu.
Issue 03 (2012-07-30)
251

NOTE
8 Supporting Task
For intelligent service fault diagnosis of native Ethernet services, right-click the target service and choose Service Fault Diagnosis from the shortcut menu.
Step 4 Click Start Diagnosis. The system uses OAM to implement fault diagnosis over services, PWs, tunnels, and the physical layer. Then, the system exports diagnostic results. Step 5 Optional: Click Export Result to export the diagnosis results into an HTML file. Step 6 Rectify the fault according to the diagnosis results. ----End
Issue 03 (2012-07-30)
252
A Alarm Reference
Alarm Reference
Alarms are important indicators when abnormalities occur on the equipment. This chapter describes all the possible alarms on the OptiX RTN 950 and how to handle these alarms. A.1 Alarm List (in Alphabetical Order) The following table lists all the possible alarms generated by the OptiX RTN 950 in alphabetical order. A.2 Alarm List (Classified by Logical Boards) This part lists the alarms that are reported by each board.
Issue 03 (2012-07-30)
253
A Alarm Reference
A.1 Alarm List (in Alphabetical Order)

The following table lists all the possible alarms generated by the OptiX RTN 950 in alphabetical order. Table A-1 Alarm list Alarm Name A_LOC ACR_LOCK_FAIL ALM_E1RAI ALM_GFP_dCSF ALM_GFP_dLFD Description Loss of clock in the upstream bus 1588 ACR locking fails E1 link remote alarm indication Loss of GFP client signals Out of frame state of generic framing procedure (GFP) frames Frame delimitation is out-of-frame at the local end of the IMA link. Differential delay of the IMA link crosses the threshold. The IMA link on the opposite NE fails in the receive direction. The IMA link on the opposite NE fails in the transmit direction. Frame delimitation is out-of-frame at the remote end of the IMA link. Downshift of AM modes Alarm Severity Major Major Minor Critical Major
ALM_IMA_LIF
Major
ALM_IMA_LODS
Major
ALM_IMA_RE_RX_UNUSABLE
Minor
ALM_IMA_RE_TX_UNUSABLE
Minor
ALM_IMA_RFI
Major
AM_DOWNSHIFT
Major
Issue 03 (2012-07-30)
254
A Alarm Reference
Alarm Name APS_FAIL
Description Failure indication of MS protection switching Indication of the APS protection switching MS protocol stopped manually The number of unknown ATM cells exceeds the specified threshold in a time unit. AU alarm indication Loss of AU pointers Excessive regenerator section errors (B1) Signal degradation due to excessive regenerator section errors (B1) Excessive multiplex section errors (B2) Signal degradation due to excessive multiplex section errors (B2) Excessive higher order path bit errors (B3) Excessive B3 bit errors in a VC-3 path Signal degradation due to excessive higher order path bit errors (B3) Signal degradation due to excessive VC-3 path (B3) bit errors
Alarm Severity Major
APS_INDI APS_MANUAL_STOP ATMPW_UNKNOWNCELL_EXC
Major Minor Major
AU_AIS AU_LOP B1_EXC
Major Major Minor
B1_SD
Minor
B2_EXC B2_SD
Major Minor
B3_EXC
Major
B3_EXC_VC3 B3_SD
Major Minor
B3_SD_VC3
Minor
Issue 03 (2012-07-30)
255
A Alarm Reference
Alarm Name BAT1TEMP_SENSOR_FAIL
Description The temperature sensor of battery group 1 fails. The temperature sensor of battery group 2 fails. The logical board is not added on the NMS. The board is out-ofposition. The board temperature sensor of the cabinet fails. The board is in BIOS state. Excessive BIP errors Signal degradation due to excessive BIP errors BOOTROM data check fails. Bus errors The locking function of CES ACR service clock is abnormal. Packet MSP protocol state indication The MSP protocol is disabled manually. The amount of jitter buffer overflow crosses the specified threshold. The amount of jitter buffer underflow crosses the specified threshold. K1 and K2 mismatch
BAT2TEMP_SENSOR_FAIL
Major
BD_NOT_INSTALLED
Minor
BD_STATUS BDTEMP_SENSOR_FAIL
Major Major
BIOS_STATUS BIP_EXC BIP_SD
Major Minor Minor
BOOTROM_BAD BUS_ERR CES_ACR_LOCK_ABN
Major Critical Minor
CES_APS_INDI CES_APS_MANUAL_STOP CES_JTROVR_EXC
Major Minor Major
CES_JTRUDR_EXC
Major
CES_K1_K2_M
Minor
Issue 03 (2012-07-30)
256
A Alarm Reference
Alarm Name CES_K2_M CES_LOSPKT_EXC
Description K2 mismatch The number of lost packets crosses the specified threshold in a time unit. The number of deformed packets crosses the specified threshold in a time unit. The number of lost disordered packets crosses the specified threshold in a time unit. Remote defect indication The number of error packets crosses the specified threshold in a time unit. The AC circuit on the opposite NE is faulty. Remote alarm indication The operation on the CF card fails. The CF card is offline. Correctable cell errors Clock locking fails The clock source is not in locked mode. Inter-board communication fails. Excessive TCP connections between automatically extended ECC NEs
Alarm Severity Minor Major
CES_MALPKT_EXC
Major
CES_MISORDERPKT_EXC
Major
CES_RDI CES_STRAYPKT_EXC
Minor Major
CESPW_OPPOSITE_ACFAULT CESPW_OPPOSITE_RAI CFCARD_FAILED CFCARD_OFFLINE CHCS CLK_LOCK_FAIL CLK_NO_TRACE_MODE COMMUN_FAIL COM_EXTECC_FULL
Major Major Major Major Minor Major Minor Major Major
Issue 03 (2012-07-30)
257
A Alarm Reference
Alarm Name CONFIG_NOSUPPORT DBMS_DELETE DBMS_ERROR
Description Configuration is not supported. The status of databases is delete. Errors in the processing of system databases System databases in protection mode Oversized DCN network The frame alignment signal of framed E1 services is lost. Alarm indication of 2 Mbit/s downstream signals The number of lost packets due to port congestion crosses the threshold. Loss of 2 Mbit/s clock in upstream signals Loss of 2 Mbit/s line signals The ambient humidity sensor of the cabinet fails. The ambient temperature sensor of the cabinet fails. The ambient temperature sensor 1 of the cabinet fails. The ambient temperature sensor 2 of the cabinet fails. Loss of APS frames
Alarm Severity Major Major Major
DBMS_PROTECT_MODE DCNSIZE_OVER DDN_LFA
Critical Major Major
DOWN_E1_AIS
Minor
DROPRATIO_OVER
Minor
E1_LOC
Major
E1_LOS ENVHUM_SENSOR_FAIL
Minor Major
ENVTEMP_SENSOR_FAIL
Major
ENVTEMP1_SENSOR_FAIL
Major
ENVTEMP2_SENSOR_FAIL
Major
ETH_APS_LOST
Minor
Issue 03 (2012-07-30)
258
A Alarm Reference
Alarm Name ETH_APS_PATH_MISMATCH
Description The working and protection paths of the APS protection group differ between the two ends. Protection switching failure Protection scheme mismatch A local MEP_AIS occurs. Loss of connectivity Misconnection The maintenance association end point (MEP) fails to receive CCM packets. Error frames Discovery failure Performance events at the opposite end A loopback occurs. Faults occur at the opposite end. Loss of Ethernet port connection No flow on the Ethernet port Power output failure of an Ethernet port Discovery failure is detected by point-topoint Ethernet OAM. A remote loopback is detected by point-topoint Ethernet OAM.
ETH_APS_SWITCH_FAIL ETH_APS_TYPE_MISMATCH ETH_CFM_AIS ETH_CFM_LOC ETH_CFM_MISMERGE ETH_CFM_RDI
Major Major Major Critical Critical Minor
ETH_CFM_UNEXPERI ETH_EFM_DF ETH_EFM_EVENT ETH_EFM_LOOPBACK ETH_EFM_REMFAULT ETH_LOS ETH_NO_FLOW ETH_PWR_SUPPLY_FAIL ETHOAM_DISCOVER_FAIL
Minor Major Major Major Critical Critical Major Critical Minor
ETHOAM_RMT_LOOP
Minor
Issue 03 (2012-07-30)
259
A Alarm Reference
Alarm Name ETHOAM_RMT_SD
Description Remote Ethernet performance degradation is detected by point-topoint Ethernet OAM. Severe faults are detected by point-topoint Ethernet OAM at the remote end. An MAC port loopback is detected by point-to-point Ethernet OAM. A VCTRUNK port loopback is detected by point-to-point Ethernet OAM. Loss of periodical continuity check packets Conflict of maintenance point IDs Loss of external clock sources Aged fans Failure of fan boards Frame check sequence (FCS) errors Excessive data traffic received by Ethernet ports Hardware faults Board hardware does not support a certain function. Threshold-crossing performance event of the higher order path
Alarm Severity Minor
ETHOAM_RMT_CRIT_FAULT
Minor
ETHOAM_SELF_LOOP
Major
ETHOAM_VCG_SELF_LOOP
Major
EX_ETHOAM_CC_LOS
Critical
EX_ETHOAM_MPID_CNFLCT
Major
EXT_SYNC_LOS FAN_AGING FAN_FAIL FCS_ERR
Critical Minor Major Critical
FLOW_OVER
Minor
HARD_BAD HARD_NONSUPPORT
Critical Major
HP_CROSSTR
Minor
Issue 03 (2012-07-30)
260
A Alarm Reference
Alarm Name HP_LOM
Description Loss of multiframes in the higher order path Higher order path remote defect indication Higher order path remote error indication Higher order path signal label mismatch High order path trace identifier mismatch Unequipped higher order path Adaptation performance threshold-crossing of the higher order path IF cables are disconnected. The power supplied by an IF board to an ODU is abnormal. Preset IF working mode is not supported. The IMA group at the local end fails. The IMA group at the remote end fails. The transmit clock modes at the two ends of the IMA group are different. Abnormal input optical power Over high input optical power
HP_RDI
Minor
HP_REI
Warning
HP_SLM
Minor
HP_TIM HP_UNEQ HPAD_CROSSTR
Minor Minor Minor
IF_CABLE_OPEN IF_INPWR_ABN
Major Major
IF_MODE_UNSUPPORTED
Major
IMA_GROUP_LE_DOWN IMA_GROUP_RE_DOWN IMA_TXCLK_MISMATCH
Major Major Minor
IN_PWR_ABN IN_PWR_HIGH
Major Critical
Issue 03 (2012-07-30)
261
A Alarm Reference
Alarm Name IN_PWR_LOW INTEMP_SENSOR_FAIL
Description Over low input optical power The air intake vent temperature sensor of the cabinet fails. Trace identifier mismatch K1 and K2 mismatch K2 mismatch Bandwidth inconsistency in the LAG group The LAG is unavailable. A member port of a link aggregation group (LAG) is unavailable. A member port of a LAG fails. A VCG port of an LAG fails. Ethernet communication failure The laser is shut down. The type of the pluggable optical module on the board does not match the type of the optical interface. The type of the pluggable optical module on the board does not match the type of the optical interface. The laser is shut down.
Alarm Severity Critical Major
J0_MM K1_K2_M K2_M LAG_BWMM
Minor Minor Minor Major
LAG_DOWN LAG_MEMBER_DOWN
Major Minor
LAG_PORT_FAIL LAG_VC_PORT_FAIL LAN_LOC
Minor Minor Major
LASER_CLOSED LASER_MOD_ERR
Major Major
LASER_MOD_ERR_EX
Major
LASER_SHUT
Major
Issue 03 (2012-07-30)
262
A Alarm Reference
Alarm Name LCAS_FOPR
Description LCAS protocol fails in the receive direction. LCAS protocol fails in the transmit direction. Loss of partial bandwidth in the LCAS receive direction Loss of partial bandwidth in the LCAS transmit direction Loss of total bandwidth in the LCAS receive direction Loss of total bandwidth in the LCAS transmit direction Loss of cell delimitation The capacity of the configured services exceeds the range permitted by the license file. Out of frame state of E1 frames The NE fails to detect any license file. Faults occur in a data link. Out of frame state of E1 multiframes A loopback occurs. Performance threshold-crossing of the lower order path
LCAS_FOPT
Major
LCAS_PLCR
Minor
LCAS_PLCT
Minor
LCAS_TLCR
Major
LCAS_TLCT
Major
LCD LCS_LIMITED
Major Major
LFA LICENSE_LOST LINK_ERR LMFA LOOP_ALM LP_CROSSTR
Major Major Critical Major Minor Minor
Issue 03 (2012-07-30)
263
A Alarm Reference
Alarm Name LP_R_FIFO
Description FIFO overflow on the receive side of the lower order path Lower order path remote defect indication VC-12 path remote defect indication VC-3 path remote defect indication Lower order path remote error indication VC-12 path remote error indication VC-3 path remote bit error indication Lower order path remote failure indication Lower order path signal label mismatch VC-12 path signal label mismatch VC-3 path signal label mismatch FIFO overflow on the transmit side of the lower order path Lower order path trace identifier mismatch VC-12 path trace identifier mismatch VC-3 path tracking identification mismatch Unequipped lower order paths
LP_RDI
Minor
LP_RDI_VC12 LP_RDI_VC3 LP_REI
Minor Minor Minor
LP_REI_VC12 LP_REI_VC3 LP_RFI
Minor Minor Minor
LP_SLM
Minor
LP_SLM_VC12 LP_SLM_VC3 LP_T_FIFO
Minor Minor Minor
LP_TIM
Minor
LP_TIM_VC12 LP_TIM_VC3
Minor Minor
LP_UNEQ
Minor
Issue 03 (2012-07-30)
264
A Alarm Reference
Alarm Name LP_UNEQ_VC12 LP_UNEQ_VC3 LPS_UNI_BI_M
Description Unequipped VC-12 paths VC-3 path unequipped The switching mode is single-ended at one end and dual-ended at the other end. The LPT closes the access port of the local NE. LPT function failed Link state passthrough function fails at the remote end. Laser bias current crossing the threshold Laser not installed Laser going to expire Loss of clock synchronization source The number of bit errors at the MAC layer crosses the threshold. The software detects that the number of bit errors at the MAC layer crosses the threshold. Module communication failure Port module type mismatch The group member delay MP group failure
Alarm Severity Minor Minor Minor
LPT_CFG_CLOSEPORT
Major
LPT_INEFFECT LPT_RFI
Major Critical
LSR_BCM_ALM
Major
LSR_NO_FITED LSR_WILL_DIE LTI
Critical Critical Major
MAC_EXT_EXC
Major
MAC_FCS_EXC
Major
MOD_COM_FAIL
Critical
MOD_TYPE_MISMATCH MP_DELAY MP_DOWN
Critical Major Major
Issue 03 (2012-07-30)
265
A Alarm Reference
Alarm Name MPLS_PW_AIS MPLS_PW_BDI MPLS_PW_Excess
Description PW forward defect indication PW backward defect indication Excessive trail termination source identifiers (TTSIs) are received on the PW. Loss of PW connectivity The trail termination source identifiers (TTSIs) on the PW do not match with the specified one. The trail termination source identifiers (TTSIs) are mismerged on the PW. OAM protocol negotiation failure PW backward defect indication Signal degradation on the PW Signal failure on the PW The MEP receives a packet with correct MEG level but incorrect MEG ID. The CCM information of a PW OAM packet is incorrect. The PW does not receive a CCM packet in the expected period.
Alarm Severity Major Minor Minor
MPLS_PW_LOCV MPLS_PW_MISMATCH
Critical Critical
MPLS_PW_MISMERGE
Major
MPLS_PW_OAMFAIL MPLS_PW_RDI MPLS_PW_SD MPLS_PW_SF MPLS_PW_UNEXPMEG
Minor Minor Major Major Critical
MPLS_PW_UNEXPMEP
Major
MPLS_PW_UNEXPPER
Major
Issue 03 (2012-07-30)
266
A Alarm Reference
Alarm Name MPLS_PW_UNKNOWN MPLS_TUNNEL_AIS MPLS_TUNNEL_BDI MPLS_TUNNEL_Excess
Description Unknown defects on the PW Tunnel forward defect indication Tunnel backward defect indication Excessive trail termination source identifiers (TTSIs) are received on the tunnel. Tunnel forward defect indication Loss of tunnel connectivity The trail termination source identifiers (TTSIs) on the tunnel do not match with the specified one. The trail termination source identifiers (TTSIs) are mismerged on the tunnel. The OAM protocol negotiation between the two ends of the tunnel fails. Tunnel backward defect indication Signal degradation on the tunnel Signal failure on the tunnel Unknown defects on the tunnel Unexpected MEG ID in the CCM packet Unexpected MEP ID in the CCM packet
Alarm Severity Major Major Minor Minor
MPLS_TUNNEL_FDI MPLS_TUNNEL_LOCV MPLS_TUNNEL_MISMATCH
Major Critical Critical
MPLS_TUNNEL_MISMERGE
Major
MPLS_TUNNEL_OAMFAIL
Minor
MPLS_TUNNEL_RDI MPLS_TUNNEL_SD MPLS_TUNNEL_SF MPLS_TUNNEL_UNKNOWN MPLS_TUNNEL_UNEXPMEG MPLS_TUNNEL_UNEXPMEP
Minor Major Major Major Critical Major
Issue 03 (2012-07-30)
267
A Alarm Reference
Alarm Name MPLS_TUNNEL_UNEXPPER MS_AIS MS_CROSSTR
Description Unexpected period of the CCM packet Multiplex section alarm indication Multiplex section performance threshold-crossing Multiplex section remote defect indication Multiplex section remote error indication Multiplex section adaptation performance threshold-crossing The ring network has multiple RPL_OWNER nodes. The IF port is in the AM testing state. Excessive errors on radio links Signal degradation due to excessive errors on radio links Configuration mismatch on radio links Continuous wave Loss of E1 signals Microwave frames have the errors that cannot be corrected by using the forward error correction (FEC) technology. Label mismatch on radio links
Alarm Severity Major Major Minor
MS_RDI
Minor
MS_REI
Warning
MSAD_CROSSTR
Minor
MULTI_RPL_OWNER
Minor
MW_AM_TEST MW_BER_EXC MW_BER_SD
Minor Minor Minor
MW_CFG_MISMATCH
Critical
MW_CONT_WAVE MW_E1_LOST MW_FEC_UNCOR
Minor Major Minor
MW_LIM
Major
Issue 03 (2012-07-30)
268
A Alarm Reference
Alarm Name MW_LOF MW_RDI
Description Loss of microwave frames Remote defect indication on radio links The NE software is lost. The software in the main area is different from that in the standby area. The board software is lost. The N+1 protection protocol is stopped manually. The N+1 protection switching fails. N+1 protection switching indication Synchronization with the NTP time fails. Out of cell delimitation Abnormal current of the storage battery The storage battery fails to supply power for the equipment. The door of an outdoor cabinet is open. Fan failure The relative humidity in the cabinet environment crosses the specified threshold. The secondary load is powered off.
Alarm Severity Critical Minor
NESF_LOST NESOFT_MM
Critical Major
NO_BD_SOFT NP1_MANUAL_STOP
Critical Minor
NP1_SW_FAIL NP1_SW_INDI NTP_SYNC_FAIL OCD ODC_BATTERY_CURRENT_ABN ODC_BATTERY_PWRDOWN
Major Major Minor Major Major Major
ODC_DOOR_OPEN
Critical
ODC_FAN_FAILED ODC_HUMI_ABN
Major Minor
ODC_LOAD_PWRDOWN
Major
Issue 03 (2012-07-30)
269
A Alarm Reference
Alarm Name ODC_MDL_ABN ODC_POWER_FAIL
Description The power module is abnormal. Exceptions occur in the AC input power voltage. Smoke occurs in an outdoor cabinet. The surge protection function of the outdoor cabinet fails. The TEC air conditioning module in the cabinet fails. The ambient temperature of the cabinet or the temperature of the storage battery is inappropriate. Water in the outdoor cabinet Abnormal output optical power The air outlet temperature sensor of the cabinet fails. The external recycling outlet temperature sensor of the cabinet fails. Activating patch packages times out. Deactivating patch packages times out. Abnormal patch package Links of the 1+1 protection group fail.
Alarm Severity Major Major
ODC_SMOKE_OVER ODC_SURGE_PROTECTION_FAIL
Critical Critical
ODC_TEC_ALM
Major
ODC_TEMP_ABN
Minor
ODC_WATER_ALM OUT_PWR_ABN OUT1TEMP_SENSOR_FAIL
Critical Critical Major
OUT2TEMP_SENSOR_FAIL
Major
PATCH_ACT_TIMEOUT PATCH_DEACT_TIMEOUT PATCH_PKGERR PG_LINK_FAIL
Minor Minor Minor Critical
Issue 03 (2012-07-30)
270
A Alarm Reference
Alarm Name PG_PRT_DEGRADED
Description The working link or protection link of the 1+1 protection group is faulty. Inconsistent PLA configurations The traffic is higher than the port bandwidth threshold. Port not in position The working mode of the remote FE port does not match that of the local FE port. Power input alarm Power module alarm LCP negotiation failure NCP negotiation failure PTP time source switching PTP time stamp abnormality The number of lost packets in a PW crosses the threshold. The PW has no traffic. Loss of APS frames The working and protection paths of the APS protection group differ between the two ends. Protection switching failure Protection scheme mismatch
PLA_CFG_MISMATCH PORT_EXC_TRAFFIC
Critical Warning
PORT_MODULE_OFFLINE PORTMODE_MISMATCH
Major Minor
POWER_ABNORMAL POWER_ALM PPP_LCP_FAIL PPP_NCP_FAIL PTP_SOURCE_SWITCH PTP_TIMESTAMP_ABN PW_DROPPKT_EXC
Major Major Major Major Minor Major Warning
PW_NO_TRAFFIC PWAPS_LOST PWAPS_PATH_MISMATCH
Critical Minor Major
PWAPS_SWITCH_FAIL PWAPS_TYPE_MISMATCH
Major Major
Issue 03 (2012-07-30)
271
A Alarm Reference
Alarm Name R_LOC R_LOF R_LOS
Description Loss of clock on the receive line side Loss of frame on the receive line side Loss of signal or loss of microwave frame on the receive line side The out-of-frame fault occurs on the receive line side. Radio fading margin is insufficient. The radio transmitter is muted. Antennas are not aligned. Over high radio receive signal level Over low radio receive signal level Over high radio transmit signal level Over low radio transmit signal level There are critical alarm inputs. There are warning inputs. There are major alarm inputs. There are minor alarm inputs. Loss of multiframe alignment at the remote end Radio protection switching indication
Alarm Severity Critical Critical Critical
R_OOF
Critical
RADIO_FADING_MARGIN_INSUFF RADIO_MUTE RADIO_RSL_BEYONDTH RADIO_RSL_HIGH RADIO_RSL_LOW RADIO_TSL_HIGH RADIO_TSL_LOW RELAY_ALARM_CRITICAL RELAY_ALARM_IGNORE RELAY_ALARM_MAJOR RELAY_ALARM_MINOR RMFA
Minor Warning Minor Critical Critical Critical Critical Critical Warning Major Minor Minor
RPS_INDI
Major
Issue 03 (2012-07-30)
272
A Alarm Reference
Alarm Name RS_CROSSTR
Description Regenerator section performance threshold-crossing The real-time clock (RTC) of the system control board fails. Clock source switching in S1 mode RADIUS authentication fails. Security alarm Ethernet services are interrupted. The commit operation is not performed during software package loading. The automatic match function is disabled. The board software version and the version of the running software are inconsistent. The submit operation fails. The package diffusion is being performed on the NE. Certain files in the package stored in flash memory are lost. The software package does not contain any board software. Software package version consistency check fails.
RTC_FAIL
Major
S1_SYN_CHANGE SEC_RADIUS_FAIL SECU_ALM SRV_SHUTDOWN_LD SWDL_ACTIVATED_TIMEOUT
Major Major Major Warning Critical
SWDL_AUTOMATCH_INH SWDL_CHGMNG_NOMATCH
Minor Critical
SWDL_COMMIT_FAIL SWDL_INPROCESS
Minor Warning
SWDL_NEPKGCHECK
Critical
SWDL_PKG_NOBDSOFT
Minor
SWDL_PKGVER_MM
Minor
Issue 03 (2012-07-30)
273
A Alarm Reference
Alarm Name SWDL_ROLLBACK_FAIL SYN_BAD SYNC_C_LOS
Description The version rollback on an NE fails. Synchronous source degradation Loss of synchronization clock sources Batch backup of SCC boards fails. Loss of analog signals at 2 Mbit/s interfaces Loss of clock on the transmit line side Too high laser temperature Too low laser temperature Excessive board temperature Excessive board temperature Laser transmission fails. Surge protection fails. Time locking fails. The high precision time of the NE is in the non-traced status. Clock failure TU alarm indication VC-12 path TU alarm indication TU of VC-3 level alarm indication Loss of TU pointers
Alarm Severity Minor Minor Warning
SCCDATA_BACKUP_FAIL T_ALOS
Minor Major
T_LOC TEM_HA TEM_LA TEMP_ALARM TEMP_OVER TF THUNDERALM TIME_LOCK_FAIL TIME_NO_TRACE_MODE
Major Major Major Minor Major Critical Minor Major Minor
TR_LOC TU_AIS TU_AIS_VC12 TU_AIS_VC3 TU_LOP
Major Major Major Major Major
Issue 03 (2012-07-30)
274
A Alarm Reference
Alarm Name TU_LOP_VC12 TU_LOP_VC3 TUNNEL_APS_DEGRADED UHCS UP_E1_AIS
Description Loss of TU pointers in VC-12 paths TU of VC-3 level loss of pointer The tunnel protection group degrades. Uncorrectable cell errors Alarm indication of 2 Mbit/s upstream signals Bits 5-7 in the V5 byte of a VC-12 path are set to "1"s. Alarm indication signal of the VC connection Loss of VC continuity check Remote defect indication of the VC connection Excessive virtual concatenation delay Loss of multiframe of VC-12 path virtual concatenation The virtually concatenated multiframes in a VC-3 path are lost. SQ mismatch of VC-12 path virtual concatenation SQ mismatch of VC-3 path virtual concatenation Loss of voltage
Alarm Severity Major Major Major Minor Minor
V5_VCAIS
Major
VC_AIS
Critical
VC_LOC VC_RDI
Major Major
VCAT_LOA VCAT_LOM_VC12
Critical Major
VCAT_LOM_VC3
Major
VCAT_SQM_VC12
Major
VCAT_SQM_VC3
Major
VOLT_LOS
Major
Issue 03 (2012-07-30)
275
A Alarm Reference
Alarm Name VP_AIS
Description Alarm indication signal of the VP connection Loss of VP continuity check Remote defect indication of the VP connection Failure in reading and writing chip registers Error board types Loss of XPIC compensation signals The communication between the NE and the syslog server fails. Password of the user who logs in is unchanged. Certificate file of SSL is not encrypted Indicates that a node on the EPRS ring is faulty.
Alarm Severity Critical
VP_LOC VP_RDI
Major Major
W_R_FAIL
Major
WRG_BD_TYPE XPIC_LOS SYSLOG_COMM_FAIL
Major Critical Major
PASSWORD_NEED_CHANGE
Major
SSL_CERT_NOENC ERPS_IN_PROTECTION
Major Minor
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. Table A-2 shows the logical boards corresponding to all physical boards
Table A-2 Mappings between the physical boards and logical boards Physical Board CST Logical Board CST in the same slot
Issue 03 (2012-07-30)
276
A Alarm Reference
Physical Board CSH AUX IF1 IFU2 IFX2 ISU2 ISX2 ISV3 SL1D SL1DA EM6T EM6TA EM6F EM6FA EG4 EG4P EFP8 EMS6 SP3S SP3D ML1 MD1 CQ1 PIU FAN ODU
Logical Board CSH in the same slot AUX in the same slot IF1 in the same slot IFU2 in the same slot IFX2 in the same slot ISU2 in the same slot ISX2 in the same slot ISV3 in the same slot SL1D in the same slot SL1DA in the same slot EM6T in the same slot EM6TA in the same slot EM6F in the same slot EM6FA in the same slot EG4 in the same slot EG4P in the same slot EFP8 in the same slot EMS6 in the same slot SP3S in the same slot SP3D in the same slot ML1 in the same slot MD1 in the same slot CQ1 in the same slot PIU in the same slot FAN in the same slot ODU in the slot whose number is 20 plus the slot number for the IF board that is connected to the ODU
Issue 03 (2012-07-30)
277
A Alarm Reference
A.2.1 CST
APS_FAIL BD_STATUS CFCARD_OFFLIN E DBMS_DELETE EXT_SYNC_LOS LAN_LOC LTI NP1_SW_FAIL PATCH_ACT_TIM EOUT PG_PRT_DEGRAD ED RTC_FAIL SWDL_ACTIVATE D_TIMEOUT SWDL_INPROCES S SWDL_ROLLBAC K_FAIL TEMP_ALARM APS_INDI BIOS_STATUS CLK_LOCK_FAIL DBMS_ERROR HARD_BAD LCS_LIMITED NESF_LOST NP1_SW_INDI PATCH_DEACT_T IMEOUT PLA_CFG_MISMA TCH S1_SYN_CHANGE SWDL_AUTOMAT CH_INH SWDL_NEPKGCH ECK SYN_BAD WRG_BD_TYPE APS_MANUAL_ST OP BOOTROM_BAD CLK_NO_TRACE_ MODE DBMS_PROTECT_ MODE K1_K2_M LICENSE_LOST NESOFT_MM NTP_SYNC_FAIL PATCH_PKGERR POWER_ALM SEC_RADIUS_FAI L SWDL_CHGMNG_ NOMATCH SWDL_PKG_NOB DSOFT SYNC_C_LOS SSL_CERT_NOEN C BD_NOT_INSTAL LED CFCARD_FAILED COM_EXTECC_F ULL DCNSIZE_OVER K2_M LPS_UNI_BI_M NP1_MANUAL_ST OP PASSWORD_NEE D_CHANGE PG_LINK_FAIL RPS_INDI SECU_ALM SWDL_COMMIT_ FAIL SWDL_PKGVER_ MM SCCDATA_BACK UP_FAIL SYSLOG_COMM_ FAIL
A.2.2 CSH
ACR_LOCK_FAIL BD_NOT_INSTAL LED CES_APS_INDI APS_FAIL BD_STATUS CES_APS_MANU AL_STOP APS_INDI BIOS_STATUS CES_K1_K2_M APS_MANUAL_ST OP BOOTROM_BAD CES_K2_M
Issue 03 (2012-07-30)
278
A Alarm Reference
CFCARD_FAILED COM_EXTECC_F ULL DCNSIZE_OVER ETH_APS_TYPE_ MISMATCH FLOW_OVER K2_M LICENSE_LOST MOD_COM_FAIL MPLS_PW_LOCV MPLS_PW_RDI MPLS_PW_UNEX PMEP MPLS_TUNNEL_B DI MPLS_TUNNEL_ MISMATCH MPLS_TUNNEL_S D MPLS_TUNNEL_U NEXPPER NP1_MANUAL_ST OP PASSWORD_NEE D_CHANGE PG_LINK_FAIL PTP_SOURCE_SW ITCH PWAPS_LOST
CFCARD_OFFLIN E DBMS_DELETE ETH_APS_LOST ETH_NO_FLOW HARD_BAD LAG_BWMM LPS_UNI_BI_M MPLS_PW_AIS MPLS_PW_MISM ATCH MPLS_PW_SD MPLS_PW_UNEX PPER MPLS_TUNNEL_E xcess MPLS_TUNNEL_ MISMERGE MPLS_TUNNEL_S F MPLS_TUNNEL_U NKNOWN NP1_SW_FAIL PATCH_ACT_TIM EOUT PG_PRT_DEGRAD ED PTP_TIMESTAMP _ABN PWAPS_PATH_MI SMATCH
CLK_LOCK_FAIL DBMS_ERROR ETH_APS_PATH_ MISMATCH EXT_SYNC_LOS HARD_NONSUPP ORT LAN_LOC LPT_CFG_CLOSEPORT MPLS_PW_BDI MPLS_PW_MISME RGE MPLS_PW_SF MPLS_PW_UNKN OWN MPLS_TUNNEL_F DI MPLS_TUNNEL_O AMFAIL MPLS_TUNNEL_U NEXPMEG NESF_LOST NP1_SW_INDI PATCH_DEACT_T IMEOUT PLA_CFG_MISMA TCH PW_DROPPKT_EX C PWAPS_SWITCH_ FAIL
CLK_NO_TRACE_ MODE DBMS_PROTECT_ MODE ETH_APS_SWITC H_FAIL EXT_TIME_LOC K1_K2_M LCS_LIMITED LTI MPLS_PW_Excess MPLS_PW_OAMF AIL MPLS_PW_UNEX PMEG MPLS_TUNNEL_A IS MPLS_TUNNEL_L OCV MPLS_TUNNEL_R DI MPLS_TUNNEL_U NEXPMEP NESOFT_MM NTP_SYNC_FAIL PATCH_PKGERR POWER_ALM PW_NO_TRAFFIC PWAPS_TYPE_MI SMATCH
Issue 03 (2012-07-30)
279
A Alarm Reference
RPS_INDI SECU_ALM SWDL_CHGMNG_ NOMATCH SWDL_PKG_NOB DSOFT SYNC_C_LOS TIME_NO_TRACE _MODE SYSLOG_COMM_ FAIL
RTC_FAIL SRV_SHUTDOWN _LD SWDL_COMMIT_ FAIL SWDL_PKGVER_ MM SCCDATA_BACK UP_FAIL TUNNEL_APS_DE GRADED -
S1_SYN_CHANGE SWDL_ACTIVATE D_TIMEOUT SWDL_INPROCES S SWDL_ROLLBAC K_FAIL TEMP_ALARM WRG_BD_TYPE -
SEC_RADIUS_FAI L SWDL_AUTOMAT CH_INH SWDL_NEPKGCH ECK SYN_BAD TIME_LOCK_FAIL SSL_CERT_NOEN C -
A.2.3 IF1
AU_AIS B2_EXC BD_STATUS HP_RDI HP_UNEQ LICENSE_LOST MS_RDI MW_FEC_UNCOR R_LOC T_LOC AU_LOP B2_SD HARD_BAD HP_REI IF_CABLE_OPEN LOOP_ALM MS_REI MW_LIM R_LOF TEMP_ALARM B1_EXC B3_EXC HP_CROSSTR HP_SLM IF_MODE_UNSUP PORTED MS_AIS MSAD_CROSSTR MW_LOF R_LOS VOLT_LOS B1_SD B3_SD HP_LOM HP_TIM LCS_LIMITED MS_CROSSTR MW_CONT_WAV E MW_RDI RS_CROSSTR WRG_BD_TYPE
A.2.4 IFU2
AM_DOWNSHIFT DROPRATIO_OVE R BD_STATUS ETH_CFM_AIS BIP_EXC ETH_CFM_LOC BIP_SD ETH_CFM_MISME RGE
Issue 03 (2012-07-30)
280
A Alarm Reference
ETH_CFM_RDI ETH_EFM_LOOPB ACK HARD_BAD LAG_MEMBER_D OWN LP_RDI MAC_FCS_EXC MW_CFG_MISMA TCH MW_LIM R_LOC TU_LOP
ETH_CFM_UNEXP ERI ETH_EFM_REMF AULT IF_CABLE_OPEN LCS_LIMITED LP_REI MULTI_RPL_OWN ER MW_CONT_WAV E MW_LOF R_LOF VOLT_LOS
ETH_EFM_DF ETHOAM_SELF_L OOP LAG_BWMM LICENSE_LOST LP_UNEQ MW_BER_EXC MW_E1_LOST MW_RDI TEMP_ALARM WRG_BD_TYPE
ETH_EFM_EVENT FLOW_OVER LAG_DOWN LOOP_ALM MAC_EXT_EXC MW_BER_SD MW_FEC_UNCOR PORT_EXC_TRAF FIC TU_AIS ERPS_IN_PROTEC TION
A.2.5 IFX2
AM_DOWNSHIFT DROPRATIO_OVE R ETH_CFM_RDI ETH_EFM_LOOPB ACK HARD_BAD LAG_MEMBER_D OWN LP_RDI MAC_FCS_EXC MW_CFG_MISMA TCH MW_LIM BD_STATUS ETH_CFM_AIS ETH_CFM_UNEXP ERI ETH_EFM_REMF AULT IF_CABLE_OPEN LCS_LIMITED LP_REI MULTI_RPL_OWN ER MW_CONT_WAV E MW_LOF BIP_EXC ETH_CFM_LOC ETH_EFM_DF ETHOAM_SELF_L OOP LAG_BWMM LICENSE_LOST LP_UNEQ MW_BER_EXC MW_E1_LOST MW_RDI BIP_SD ETH_CFM_MISME RGE ETH_EFM_EVENT FLOW_OVER LAG_DOWN LOOP_ALM MAC_EXT_EXC MW_BER_SD MW_FEC_UNCOR PORT_EXC_TRAF FIC
281
Issue 03 (2012-07-30)
A Alarm Reference
R_LOC TU_LOP ERPS_IN_PROTEC TION
R_LOF VOLT_LOS -
TEMP_ALARM WRG_BD_TYPE -
TU_AIS XPIC_LOS -
A.2.6 SL1D/SL1DA
AU_AIS B2_EXC BD_STATUS HP_RDI HP_UNEQ LASER_CLOSED MS_AIS MSAD_CROSSTR RS_CROSSTR AU_LOP B2_SD HARD_BAD HP_REI IN_PWR_HIGH LASER_MOD_ER R_EX MS_CROSSTR R_LOC T_LOC B1_EXC B3_EXC HP_CROSSTR HP_SLM IN_PWR_LOW LOOP_ALM MS_RDI R_LOF WRG_BD_TYPE B1_SD B3_SD HP_LOM HP_TIM J0_MM LSR_NO_FITED MS_REI R_LOS -
A.2.7 EM6T
BD_STATUS ETH_CFM_AIS ETH_CFM_UNEXP ERI ETH_EFM_REMF AULT FLOW_OVER LOOP_ALM MULTI_RPL_OWN ER TEMP_ALARM
Issue 03 (2012-07-30)
BUS_ERR ETH_CFM_LOC ETH_EFM_DF ETH_LOS HARD_BAD LPT_CFG_CLOSEPORT PORT_EXC_TRAF FIC WRG_BD_TYPE
COMMUN_FAIL ETH_CFM_MISME RGE ETH_EFM_EVENT ETH_NO_FLOW LAG_DOWN MAC_EXT_EXC PORTMODE_MISMATCH -
DROPRATIO_OVE R ETH_CFM_RDI ETH_EFM_LOOPB ACK ETHOAM_SELF_L OOP LAG_MEMBER_D OWN MAC_FCS_EXC ERPS_IN_PROTEC TION 282
A Alarm Reference
A.2.8 EM6TA
BD_STATUS ETH_CFM_AIS ETH_CFM_UNEXP ERI ETH_EFM_REMF AULT FLOW_OVER LOOP_ALM MULTI_RPL_OWN ER WRG_BD_TYPE BUS_ERR ETH_CFM_LOC ETH_EFM_DF ETH_LOS HARD_BAD LPT_CFG_CLOSEPORT PORT_EXC_TRAF FIC ERPS_IN_PROTEC TION COMMUN_FAIL ETH_CFM_MISME RGE ETH_EFM_EVENT ETH_NO_FLOW LAG_DOWN MAC_EXT_EXC PORTMODE_MISMATCH DROPRATIO_OVE R ETH_CFM_RDI ETH_EFM_LOOPB ACK ETHOAM_SELF_L OOP LAG_MEMBER_D OWN MAC_FCS_EXC TEMP_ALARM -
A.2.9 EM6F
BD_STATUS ETH_CFM_AIS ETH_CFM_UNEXP ERI ETH_EFM_REMF AULT FLOW_OVER LAG_MEMBER_D OWN LPT_CFG_CLOSEPORT MULTI_RPL_OWN ER BUS_ERR ETH_CFM_LOC ETH_EFM_DF ETH_LOS HARD_BAD LASER_MOD_ER R LSR_NO_FITED PORT_EXC_TRAF FIC COMMUN_FAIL ETH_CFM_MISME RGE ETH_EFM_EVENT ETH_NO_FLOW IN_PWR_ABN LASER_SHUT MAC_EXT_EXC PORTMODE_MISMATCH DROPRATIO_OVE R ETH_CFM_RDI ETH_EFM_LOOPB ACK ETHOAM_SELF_L OOP LAG_DOWN LOOP_ALM MAC_FCS_EXC TEMP_ALARM
Issue 03 (2012-07-30)
283
A Alarm Reference
WRG_BD_TYPE
ERPS_IN_PROTEC TION
A.2.10 EM6FA
BD_STATUS ETH_CFM_AIS ETH_CFM_UNEXP ERI ETH_EFM_REMF AULT FLOW_OVER LAG_MEMBER_D OWN LPT_CFG_CLOSEPORT MULTI_RPL_OWN ER WRG_BD_TYPE BUS_ERR ETH_CFM_LOC ETH_EFM_DF ETH_LOS HARD_BAD LASER_MOD_ER R LSR_NO_FITED PORT_EXC_TRAF FIC ERPS_IN_PROTEC TION COMMUN_FAIL ETH_CFM_MISME RGE ETH_EFM_EVENT ETH_NO_FLOW IN_PWR_ABN LASER_SHUT MAC_EXT_EXC PORTMODE_MISMATCH DROPRATIO_OVE R ETH_CFM_RDI ETH_EFM_LOOPB ACK ETHOAM_SELF_L OOP LAG_DOWN LOOP_ALM MAC_FCS_EXC TEMP_ALARM -
A.2.11 EFP8
ALM_GFP_dCSF BIP_SD ETH_CFM_LOC ETH_LOS ETHOAM_RMT_S D EX_ETHOAM_MPI D_CNFLCT LAG_PORT_FAIL ALM_GFP_dLFD COMMUN_FAIL ETH_CFM_MISME RGE ETHOAM_DISCO VER_FAIL ETHOAM_SELF_L OOP FCS_ERR LAG_VC_PORT_F AIL BD_STATUS DOWN_E1_AIS ETH_CFM_RDI ETHOAM_RMT_C RIT_FAULT ETHOAM_VCG_S ELF_LOOP FLOW_OVER LCAS_FOPR BIP_EXC ETH_CFM_AIS ETH_CFM_UNEXP ERI ETHOAM_RMT_L OOP EX_ETHOAM_CC _LOS HARD_BAD LCAS_FOPT
Issue 03 (2012-07-30)
284
A Alarm Reference
LCAS_PLCR LFA LP_REI_VC12 LPT_RFI TU_AIS_VC12 VCAT_SQM_VC12
LCAS_PLCT LMFA LP_SLM_VC12 NO_BD_SOFT TU_LOP_VC12 W_R_FAIL
LCAS_TLCR LOOP_ALM LP_TIM_VC12 RMFA VCAT_LOA WRG_BD_TYPE
LCAS_TLCT LP_RDI_VC12 LP_UNEQ_VC12 TEMP_ALARM VCAT_LOM_VC12 -
A.2.12 EMS6
ALM_GFP_dCSF BD_STATUS COMMUN_FAIL ETH_CFM_UNEXP ERI ETHOAM_RMT_L OOP EX_ETHOAM_MPI D_CNFLCT IN_PWR_ABN LCAS_FOPT LCAS_TLCT LP_RDI_VC3 LP_SLM_VC3 LP_UNEQ_VC3 MULTI_RPL_OWN ER TEMP_ALARM TU_LOP_VC3 VCAT_SQM_VC12 ALM_GFP_dLFD BIP_EXC ETH_CFM_LOC ETH_LOS ETHOAM_RMT_S D FCS_ERR LAG_PORT_FAIL LCAS_PLCR LINK_ERR LP_REI_VC12 LP_TIM_VC12 LPT_INEFFECT NO_BD_SOFT TU_AIS_VC12 VCAT_LOA VCAT_SQM_VC3 B3_EXC_VC3 BIP_SD ETH_CFM_MISME RGE ETHOAM_DISCO VER_FAIL ETHOAM_SELF_L OOP FLOW_OVER LAG_VC_PORT_F AIL LCAS_PLCT LOOP_ALM LP_REI_VC3 LP_TIM_VC3 LPT_RFI OUT_PWR_ABN TU_AIS_VC3 VCAT_LOM_VC12 WRG_BD_TYPE B3_SD_VC3 BUS_ERR ETH_CFM_RDI ETHOAM_RMT_C RIT_FAULT EX_ETHOAM_CC _LOS HARD_BAD LCAS_FOPR LCAS_TLCR LP_RDI_VC12 LP_SLM_VC12 LP_UNEQ_VC12 MOD_TYPE_MISMATCH PORT_MODULE_ OFFLINE TU_LOP_VC12 VCAT_LOM_VC3 ERPS_IN_PROTEC TION
Issue 03 (2012-07-30)
285
A Alarm Reference
A.2.13 SP3S/SP3D
A_LOC DDN_LFA HARD_BAD LP_R_FIFO LP_SLM T_ALOS WRG_BD_TYPE BD_STATUS DOWN_E1_AIS HPAD_CROSSTR LP_RDI LP_T_FIFO TU_AIS BIP_EXC E1_LOC LOOP_ALM LP_REI LP_TIM TU_LOP BIP_SD E1_LOS LP_CROSSTR LP_RFI LP_UNEQ UP_E1_AIS -
A.2.14 AUX
BD_STATUS RELAY_ALARM_ MAJOR HARD_BAD RELAY_ALARM_ MINOR RELAY_ALARM_ CRITICAL WRG_BD_TYPE RELAY_ALARM_I GNORE -
A.2.15 PIU
BD_STATUS WRG_BD_TYPE HARD_BAD POWER_ABNORM AL THUNDERALM -
A.2.16 FAN
BD_STATUS WRG_BD_TYPE FAN_AGING FAN_FAIL POWER_ALM -
A.2.17 ISU2
AM_DOWNSHIFT B1_SD B3_SD
Issue 03 (2012-07-30)
AU_AIS B2_EXC BD_STATUS
AU_LOP B2_SD BIP_EXC
B1_EXC B3_EXC BIP_SD

286
A Alarm Reference
DROPRATIO_OVE R ETH_CFM_RDI ETH_EFM_LOOPB ACK HARD_BAD HP_REI IF_CABLE_OPEN LCS_LIMITED LP_REI MS_AIS MSAD_CROSSTR MW_BER_SD MW_FEC_UNCOR PORT_EXC_TRAF FIC T_LOC VOLT_LOS
ETH_CFM_AIS ETH_CFM_UNEXP ERI ETH_EFM_REMF AULT HP_CROSSTR HP_SLM LAG_BWMM LICENSE_LOST LP_UNEQ MS_CROSSTR MULTI_RPL_OWN ER MW_CFG_MISMA TCH MW_LIM R_LOC TEMP_ALARM WRG_BD_TYPE
ETH_CFM_LOC ETH_EFM_DF ETHOAM_SELF_L OOP HP_LOM HP_TIM LAG_DOWN LOOP_ALM MAC_EXT_EXC MS_RDI MW_AM_TEST MW_CONT_WAV E MW_LOF R_LOF TU_AIS ERPS_IN_PROTEC TION
ETH_CFM_MISME RGE ETH_EFM_EVENT FLOW_OVER HP_RDI HP_UNEQ LAG_MEMBER_D OWN LP_RDI MAC_FCS_EXC MS_REI MW_BER_EXC MW_E1_LOST MW_RDI RS_CROSSTR TU_LOP -
A.2.18 ISX2
AM_DOWNSHIFT B1_SD B3_SD DROPRATIO_OVE R ETH_CFM_RDI ETH_EFM_LOOPB ACK AU_AIS B2_EXC BD_STATUS ETH_CFM_AIS ETH_CFM_UNEXP ERI ETH_EFM_REMF AULT AU_LOP B2_SD BIP_EXC ETH_CFM_LOC ETH_EFM_DF ETHOAM_SELF_L OOP B1_EXC B3_EXC BIP_SD ETH_CFM_MISME RGE ETH_EFM_EVENT FLOW_OVER
Issue 03 (2012-07-30)
287
A Alarm Reference
HARD_BAD HP_REI IF_CABLE_OPEN LCS_LIMITED LP_REI MS_AIS MSAD_CROSSTR MW_BER_SD MW_FEC_UNCOR PORT_EXC_TRAF FIC T_LOC VOLT_LOS
HP_CROSSTR HP_SLM LAG_BWMM LICENSE_LOST LP_UNEQ MS_CROSSTR MULTI_RPL_OWN ER MW_CFG_MISMA TCH MW_LIM R_LOC TEMP_ALARM WRG_BD_TYPE
HP_LOM HP_TIM LAG_DOWN LOOP_ALM MAC_EXT_EXC MS_RDI MW_AM_TEST MW_CONT_WAV E MW_LOF R_LOF TU_AIS XPIC_LOS
HP_RDI HP_UNEQ LAG_MEMBER_D OWN LP_RDI MAC_FCS_EXC MS_REI MW_BER_EXC MW_E1_LOST MW_RDI RS_CROSSTR TU_LOP ERPS_IN_PROTEC TION
A.2.19 ML1/MD1
ALM_E1RAI ALM_IMA_RE_TX _UNUSABLE BUS_ERR CES_LOSPKT_EX C CES_STRAYPKT_ EXC HARD_BAD LCD MP_DELAY PPP_LCP_FAIL ALM_IMA_LIF ALM_IMA_RFI CES_ACR_LOCK_ ABN CES_MALPKT_EX C CESPW_OPPOSIT E_ACFAULT IMA_GROUP_LE_ DOWN LFA MP_DOWN PPP_NCP_FAIL ALM_IMA_LODS ATMPW_UNKNO WNCELL_EXC CES_JTROVR_EX C CES_MISORDERP KT_EXC CESPW_OPPOSIT E_RAI IMA_GROUP_RE_ DOWN LMFA OCD T_ALOS ALM_IMA_RE_RX _UNUSABLE BD_STATUS CES_JTRUDR_EX C CES_RDI CHCS IMA_TXCLK_MISMATCH LOOP_ALM POWER_ABNORM AL TEMP_ALARM
Issue 03 (2012-07-30)
288
A Alarm Reference
TR_LOC VC_LOC VP_RDI
UHCS VC_RDI WRG_BD_TYPE
UP_E1_AIS VP_AIS -
VC_AIS VP_LOC -
A.2.20 ODU
BD_STATUS LOOP_ALM RADIO_RSL_BEYONDTH RADIO_TSL_LOW CONFIG_NOSUPP ORT POWER_ALM RADIO_RSL_HIG H TEMP_ALARM HARD_BAD RADIO_FADING_ MARGIN_INSUFF RADIO_RSL_LOW WRG_BD_TYPE IF_INPWR_ABN RADIO_MUTE RADIO_TSL_HIG H -
A.2.21 PMU
BAT1TEMP_SENS OR_FAIL ENVTEMP1_SENS OR_FAIL ODC_BATTERY_P WRDOWN ODC_MDL_ABN ODC_TEMP_ABN BAT2TEMP_SENS OR_FAIL ENVTEMP2_SENS OR_FAIL ODC_DOOR_OPE N ODC_POWER_FAI L ODC_WATER_AL M BD_STATUS HARD_BAD ODC_HUMI_ABN ODC_SMOKE_OV ER WRG_BD_TYPE ENVHUM_SENSO R_FAIL ODC_BATTERY_C URRENT_ABN ODC_LOAD_PWR DOWN ODC_SURGE_PRO TECTION_FAIL -
A.2.22 TCU
BD_STATUS INTEMP_SENSOR _FAIL ODC_SURGE_PRO TECTION_FAIL BDTEMP_SENSOR _FAIL ODC_DOOR_OPE N ODC_TEC_ALM ENVTEMP_SENSO R_FAIL ODC_FAN_FAILE D ODC_TEMP_ABN HARD_BAD ODC_SMOKE_OV ER ODC_WATER_AL M
Issue 03 (2012-07-30)
289
A Alarm Reference
OUT1TEMP_SENS OR_FAIL
OUT2TEMP_SENS OR_FAIL
WRG_BD_TYPE
A.2.23 CQ1
ALM_E1RAI B1_SD B3_SD BUS_ERR CES_MALPKT_EX C CESPW_OPPOSIT E_ACFAULT HP_REI IN_PWR_ABN LASER_MOD_ER R LOOP_ALM LP_SLM_VC12 LSR_NO_FITED MS_AIS POWER_ABNORM AL R_LOF TEM_LA TU_AIS_VC12 WRG_BD_TYPE AU_AIS B2_EXC BD_STATUS CES_JTROVR_EX C CES_MISORDERP KT_EXC CESPW_OPPOSIT E_RAI HP_SLM IN_PWR_HIGH LASER_SHUT LP_RDI_VC12 LP_TIM_VC12 LSR_WILL_DIE MS_RDI PPP_LCP_FAIL R_LOS TEMP_OVER TU_LOP_VC12 AU_LOP B2_SD BIP_EXC CES_JTRUDR_EX C CES_RDI HARD_BAD HP_TIM IN_PWR_LOW LFA LP_REI_VC12 LP_UNEQ_VC12 MP_DELAY MS_REI PPP_NCP_FAIL R_OOF TF UP_E1_AIS B1_EXC B3_EXC BIP_SD CES_LOSPKT_EX C CES_STRAYPKT_ EXC HP_RDI HP_UNEQ J0_MM LMFA LP_RFI LSR_BCM_ALM MP_DOWN OUT_PWR_ABN R_LOC TEM_HA TR_LOC V5_VCAIS -
A.2.24 ISV3
AM_DOWNSHIFT B1_SD AU_AIS B2_EXC AU_LOP B2_SD B1_EXC B3_EXC
Issue 03 (2012-07-30)
290
A Alarm Reference
B3_SD DROPRATIO_OVE R ETH_CFM_RDI ETH_EFM_LOOPB ACK HARD_BAD HP_REI IF_CABLE_OPEN LCS_LIMITED LP_REI MS_AIS MSAD_CROSSTR MW_BER_SD MW_FEC_UNCOR PORT_EXC_TRAF FIC T_LOC VOLT_LOS
BD_STATUS ETH_CFM_AIS ETH_CFM_UNEXP ERI ETH_EFM_REMF AULT HP_CROSSTR HP_SLM LAG_BWMM LICENSE_LOST LP_UNEQ MS_CROSSTR MULTI_RPL_OWN ER MW_CFG_MISMA TCH MW_LIM R_LOC TEMP_ALARM WRG_BD_TYPE
BIP_EXC ETH_CFM_LOC ETH_EFM_DF ETHOAM_SELF_L OOP HP_LOM HP_TIM LAG_DOWN LOOP_ALM MAC_EXT_EXC MS_RDI MW_AM_TEST MW_CONT_WAV E MW_LOF R_LOF TU_AIS XPIC_LOS
BIP_SD ETH_CFM_MISME RGE ETH_EFM_EVENT FLOW_OVER HP_RDI HP_UNEQ LAG_MEMBER_D OWN LP_RDI MAC_FCS_EXC MS_REI MW_BER_EXC MW_E1_LOST MW_RDI RS_CROSSTR TU_LOP ERPS_IN_PROTEC TION
A.2.25 EG4
BD_STATUS ETH_CFM_AIS ETH_CFM_UNEXP ERI ETH_EFM_REMF AULT FLOW_OVER BUS_ERR ETH_CFM_LOC ETH_EFM_DF ETH_LOS HARD_BAD COMMUN_FAIL ETH_CFM_MISME RGE ETH_EFM_EVENT ETH_NO_FLOW IN_PWR_ABN DROPRATIO_OVE R ETH_CFM_RDI ETH_EFM_LOOPB ACK ETHOAM_SELF_L OOP LAG_DOWN
Issue 03 (2012-07-30)
291
A Alarm Reference
LAG_MEMBER_D OWN LPT_CFG_CLOSEPORT MULTI_RPL_OWN ER WRG_BD_TYPE
LASER_MOD_ER R LSR_NO_FITED PORT_EXC_TRAF FIC ERPS_IN_PROTEC TION
LASER_SHUT MAC_EXT_EXC PORTMODE_MISMATCH -
LOOP_ALM MAC_FCS_EXC TEMP_ALARM -
A.2.26 EG4P
BD_STATUS ETH_CFM_AIS ETH_CFM_UNEXP ERI ETH_EFM_REMF AULT ETHOAM_SELF_L OOP LAG_DOWN LOOP_ALM MAC_FCS_EXC TEMP_ALARM BUS_ERR ETH_CFM_LOC ETH_EFM_DF ETH_LOS FLOW_OVER LAG_MEMBER_D OWN LPT_CFG_CLOSEPORT MULTI_RPL_OWN ER WRG_BD_TYPE COMMUN_FAIL ETH_CFM_MISME RGE ETH_EFM_EVENT ETH_NO_FLOW HARD_BAD LASER_MOD_ER R LSR_NO_FITED PORT_EXC_TRAF FIC ERPS_IN_PROTEC TION DROPRATIO_OVE R ETH_CFM_RDI ETH_EFM_LOOPB ACK ETH_PWR_SUPPL Y_FAIL IN_PWR_ABN LASER_SHUT MAC_EXT_EXC PORTMODE_MISMATCH -
A.3 Alarms and Handling Procedures

This chapter describes all the alarms on the OptiX RTN 950 in alphabetical order and how to handle these alarms.
A.3.1 A_LOC
Issue 03 (2012-07-30)
292
A Alarm Reference
Description
The A_LOC is an alarm indicating that a clock signal is lost in the uplink bus.
Attribute
Alarm Severity Major Alarm Type Equipment alarm
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 ACR_LOCK_FAIL
Description
The ACR_LOCK_FAIL is an alarm indicating an IEEE 1588 ACR locking failure. This alarm is reported when the NE works in 1588 ACR mode and the clock fails to be locked.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table.
A Alarm Reference
Name
Meaning
Parameter 1 l 0x01: indicates that the phase-locked loop (PLL) is in holdover or free-run mode. l 0x02: indicates that the Sync timestamp remains unchanged when the Precision Time Protocol (PTP) clock is synchronized. l 0x03: indicates that the PDV on the transport network exceeds the upper threshold. l 0x04: indicates that the ACR algorithm is in the quick lockout phase.

When this alarm occurs, the clock of the downstream NE is abnormal.
Possible Causes
l l Cause 1: The frequency deviation of the clock source or the delay of the intermediate network exceeds the upper threshold. Cause 2: The physical link where the traced clock source resides is faulty.
Procedure
Step 1 Handle the alarm according to the alarm parameters. If... Then...
Parameter 1 = 0x01 Go to steps 3 and 4. Parameter 1 = 0x02 Go to step 4. Parameter 1 = 0x03 Go to step 3. Parameter 1 = 0x04 No further action is required. Wait for a while (about 15 minutes). Then, check whether the alarm is cleared. Step 2 Check whether a hardware alarm such as HARD_BAD occurs on the SCC board or interface board that accesses clocks. If yes, clear the alarm immediately. Step 3 Query the PDV performance of the NE to determine whether the third-party network is running properly. If not, ask the customer to optimize the PDV. For details about how to query PDV performance of the local NE, see C.3.30 CURPOSITIVEPDV and CURNEGATIVEPDV. Step 4 Check the status of the master NE. If the master NE is abnormal, troubleshoot the abnormality first. ----End
Related Information
None.
A Alarm Reference
A.3.3 ALM_E1RAI
Description
The ALM_E1RAI is an alarm indicating that the E1 link on the opposite NE reports alarms. This alarm is reported on the local NE when the T_ALOS, UP_E1_AIS, DOWN_E1_AIS, LFA, or LMFA alarm is reported on the opposite NE.
Attribute
Alarm Severity Minor Alarm Type Communication alarm
Parameters
None.

When this alarm occurs, the services on the local NE in the downstream direction are interrupted.
Possible Causes
l Cause 1: The E1 link on the opposite NE reports the T_ALOS, LFA, LMFA, UP_E1_AIS, or DOWN_E1_AIS alarm.
Procedure
Step 1 Cause 1: The E1 link on the opposite NE reports the T_ALOS, LFA, LMFA, UP_E1_AIS, or DOWN_E1_AIS alarm. Step 2 Handle these alarms first. ----End
Related Information
None.
A.3.4 ALM_GFP_dCSF
Description
The ALM_GFP_dCSF is an alarm indicating that the generic framing procedure (GFP) customer signal is lost. When the source end fails to receive the GFP customer signal, it sends the management frame to the sink end. The ALM_GFP_dCSF alarm is reported when the sink end receives the management frame.
Issue 03 (2012-07-30)
295
A Alarm Reference
Attribute
Alarm Severity Critical Alarm Type Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning The value is always 0x01.
Parameter 2, Parameter 3 Indicate the ID of the alarmed VCTRUNK. For example, 0x00 0x01 indicate that the alarm is reported in VCTRUNK 1.

When this alarm occurs, services are interrupted.
Possible Causes
l l l Cause 1: Timeslot binding is different at the source and sink VCTRUNKs. Cause 2: The radio link performance degrades. Cause 3: The alarmed board is faulty.
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
Related Information
None.
A.3.5 ALM_GFP_dLFD
A Alarm Reference
Description
The ALM_GFP_dLFD is an alarm indicating that the GFP frame is out of frame. This alarm occurs when a board detects that the GFP frame is out of frame.
Attribute
Alarm Severity Major Alarm Type Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the ID of the logical port, and the value is always 0x01.

Possible Causes
l l Cause 1: Bit errors occur on certain links or certain links are faulty. Cause 2: When the LCAS is disabled, the source and the sink VCTRUNKs are configured with 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... The links are faulty The links are normal Then... Rectify the fault. Replace the alarmed board.
Step 2 Cause 2: When the LCAS is disabled, the source and the sink VCTRUNKs are configured with different timeslots or different numbers of paths. 1. Correct the configuration data. For details, see Configuring VCTRUNKs on an Ethernet Board.
----End
A Alarm Reference
Related Information
None.
A.3.6 ALM_IMA_LIF
Description
The ALM_IMA_LIF is an alarm indicating that the IMA link is out of frame in the receive direction. This alarm occurs when the frame alignment is lost on the IMA link in the receive direction.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1, Parameter 2 Meaning Indicate the ATM Trunk ID.

l 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 for the IMA group exceeds the total bandwidth of available IMA links, congestion occurs on the IMA port, causing loss of cells. After this alarm is cleared, the affected IMA link becomes available.
Possible Causes
l l l Cause 1: The path that carries the IMA link reports the SDH alarms, such as R_LOS, R_LOF, and MS_AIS. Cause 2: The IMA protocol negotiation fails between the two ends. 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... The path reports any SDH alarm
Issue 03 (2012-07-30)
Then... Handle the relevant alarms first.

298
A Alarm Reference
If... The path does not report any SDH alarm
Then... Go to Cause 2.
Step 2 Cause 2: The IMA protocol negotiation fails between the two ends. 1. 2. 3. 4. Disable the IMA protocol at the two ends. Check the IMA group configuration at the two ends and ensure that the configuration is consistent. Enable the IMA protocol at the two ends. Then, check whether the alarm clears. If... The alarm is cleared The alarm persists Step 3 Cause 3: The IMA link is faulty. 1. Replace the board. For details, see 6.6 Replacing the Smart E1 Interface Board. Then... End the alarm handling. Go to Cause 3.
----End
Related Information
Loss of frame alignment A frame alignment word, provided at the physical layer, occupies the initial position of a frame and defines the start of information field. An Out Of Frame (OOF) defect is declared when the position of frame alignment word cannot be determined in the input bit stream.
A.3.7 ALM_IMA_LODS
Description
The ALM_IMA_LODS is an alarm indicating the differential delay on the IMA link crosses the threshold. This alarm occurs when the maximum differential delay on the IMA link exceeds the preset value.
Attribute
Parameters
A Alarm Reference
Name Parameter 1, Parameter 2
Meaning Indicate the ATM Trunk ID.

The IMA links are unavailable.
Possible Causes
l l Cause 1: The maximum differential delay is configured incorrectly. Cause 2: Within one IMA group, the transmission distances of member links have too large gaps.
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 CES Service Parameters.
Step 2 Cause 2: Within one IMA group, the transmission distances of member links have too large gaps. 1. Use the meter to measure the transmission time on E1 links. If the transmission time on different links has a gap larger than 25 ms (default value), adjust the IMA links or delete the member link with over long transmission time from the IMA group.
----End
Related Information
Differential delay Differential delay refers to the service delay difference between E1 links.
A.3.8 ALM_IMA_RE_RX_UNUSABLE
Description
The ALM_IMA_RE_RX_UNUSABLE is an alarm indicating that the IMA link on the opposite NE fails in the receive direction.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the
A Alarm Reference
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1, Parameter 2 Meaning Indicate the ATM Trunk ID.

Possible Causes
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... The path reports any SDH alarm The path does not report any SDH alarm Then... Handle the relevant alarms first. Go to Cause 2.
----End
A Alarm Reference
Related Information
None.
A.3.9 ALM_IMA_RE_TX_UNUSABLE
Description
The ALM_IMA_RE_TX_UNUSABLE is an alarm indicating that the IMA link on the opposite NE fails in the transmit direction.
Attribute
Parameters

Possible Causes
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... The path reports any SDH alarm
Issue 03 (2012-07-30)
Then... Handle the relevant alarms first.

302
A Alarm Reference
If... The path does not report any SDH alarm
----End
Related Information
None.
A.3.10 ALM_IMA_RFI
Description
The 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 IMA link of the opposite NE and the opposite NE notifies the local NE of its OOF state.
Attribute
Parameters
Issue 03 (2012-07-30)
303
A Alarm Reference

Possible Causes
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... The path reports any SDH alarm The path does not report any SDH alarm Then... Handle the relevant alarms first. Go to Cause 2.
----End
Related Information
Frame alignment loss A frame alignment word, provided at the physical layer, occupies the initial position of a frame and defines the start of information field. An Out Of Frame (OOF) defect is declared when the position of frame alignment word cannot be determined in the input bit stream.
A Alarm Reference
A.3.11 AM_DOWNSHIFT
Description
The AM_DOWNSHIFT alarm indicates the downshift of the AM scheme. This alarm occurs after the AM mode is downshifted from the highest-order modulation scheme to the lower-order modulation scheme. After the AM mode is upshifted from the lower-order modulation scheme to the highest-order modulation scheme, this alarm is cleared.
Attribute
Parameters
None.

When the AM_DOWNSHIFT alarm occurs, the transmission capacity is reduced.
Possible Causes
l l l l Cause 1: The external factors (for example, the climate) cause the degradation of the working channels. Cause 2: There are interferences around the working channels. Cause 3: The ODU at the transmit end has abnormal transmit power. Cause 4: The ODU at the receive end has abnormal receive power.
Procedure
Step 1 Cause 1: The external factors (for example, the climate) cause the degradation of the working channels. 1. When the external factors (for example, the climate) cause the degradation of the working channels, the downshift of the AM scheme is normal. Hence, no measures should be taken to handle the alarm.
Step 2 Cause 2: There are interferences around the working channels. 1. Eliminate the interferences around the working channels.
Step 3 Cause 3: The ODU at the transmit end has abnormal transmit power. 1. Use the NMS to check whether the transmit power of the ODU at the transmit end is normal. For details on troubleshooting at the transmit end, see Troubleshooting Microwave Links.
Step 4 Cause 4: The ODU at the receive end has abnormal receive power.
A Alarm Reference
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 Microwave Links.
----End
Related Information
None.
A.3.12 APS_FAIL
Description
The APS_FAIL is an alarm indicating that the MS protection switching fails.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. 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 indicates that the alarm is reported by protection group 1.

When the APS_FAIL alarm occurs, the services cannot be switched. If the current paths are unavailable, the services are interrupted.
Possible Causes
l l Cause 1: The parameters of the MSP protocol are set incorrectly. Cause 2: The parameters of the MSP protocol are lost.
Procedure
Step 1 Cause 1: The parameters of the MSP protocol are set incorrectly.
A Alarm Reference
1.
Check whether the parameters of the MSP protocol are set correctly. If... The parameters are set incorrectly The parameters are set correctly Then... Set the parameters correctly. Go to the next step.
Step 2 Cause 2: The parameters of the MSP protocol are lost. 1. 2. Check whether the MSP protocol is normal on the network. 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 is End the alarm handling. restarted The alarm persists after the protocol is restarted ----End Contact Huawei engineers to handle the alarm.
Related Information
None.
A.3.13 APS_INDI
Description
The APS_INDI is an alarm indicating that the MS protection switching occurs.
Attribute
Parameters
Parameter 1 Indicates the type of the protection group. l 0x01: linear MS protection.
A Alarm Reference
Name
Meaning
Parameter 2 Indicates the ID of the alarmed protection group. For example, 0x01 indicates that the alarm is reported by protection group 1.

During the switching ( 50 ms), the service is interrupted. After the switching is complete, the services are restored to normal. In the case of 1:N MS protection, after the switching starts and before the switching is complete, the extra services are interrupted.
Possible Causes
Cause 1: The MS protection switching occurs.
Procedure
Step 1 Cause 1: The MS protection switching occurs. 1. 2. Query the linear MSP group. 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 is cleared. 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 equipment reports. After the alarms are cleared, wait until the MSP protocol is changed from the automatic switching state to the normal state. Then, check whether the APS_INDI alarm is cleared. 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. Check whether the currently working system control and cross-connect board is faulty. If the currently working system control and cross-connect board is faulty and a protection system control and cross-connect board is available, switch the service to the protection system control and cross-connect board and replace the faulty system control and cross-connect board. Then, check whether the APS_INDI alarm is cleared.
3.
b. c.
----End
Related Information
None.
A.3.14 APS_MANUAL_STOP
Description
The APS_MANUAL_STOP is an alarm indicating that the MSP protocol is stopped manually.
A Alarm Reference
Attribute
Alarm Severity Minor Alarm Type Processing alarm
Parameters
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 indicates that the alarm is reported by protection group 1.

When the APS_MANUAL_STOP alarm occurs, the MSP protocol may fail and therefore the protection switching may fail.
Possible Causes
Cause 1: The MSP protocol is stopped manually.
Procedure
Step 1 Cause 1: The MSP protocol is stopped manually. 1. Enable/Disable the linear MSP protocol.
----End
Related Information
None.
A.3.15 ATMPW_UNKNOWNCELL_EXC
Description
The ATMPW_UNKNOWNCELL_EXC is an alarm indicating that the number of unknown cells exceeds the specified threshold in a time unit. This alarm occurs when the board detects that, within a period (2.5s), the number of unknown cells crosses the specified threshold.
A Alarm Reference
Attribute
Parameters
None.

An unknown cell is discarded once it is detected. As a result, the packet loss rate increases and services are affected.
Possible Causes
l l l Cause 1: PW control words mismatch. Cause 2: PW types mismatch. 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 the configuration. Step 2 Check whether connections are correct. If not, reconnect fibers or reconfigure connections. ----End
Related Information
None.
A.3.16 AU_AIS
Description
The AU_AIS is an alarm indicating the administrative unit (AU). This alarm occurs when the board detects the AU pointer of all 1s for three consecutive frames.
Attribute
Parameters
None.
A Alarm Reference

When the AU_AIS alarm occurs, the service in the alarmed AU-4 path is interrupted. If the services are configured with protection, protection switching may be triggered.
Possible Causes
l l l Cause 1: The opposite NE inserts the AU_AIS alarm. Cause 2: The transmit unit of the opposite NE is faulty. 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... The alarm that triggers the AU_AIS insertion occurs No such alarms that trigger the AU_AIS insertion occur 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... The alarm is cleared after the board is replaced The alarm persists after the board is replaced 2. Then... The fault is rectified. End the alarm handling. Go to the next step. Then... Clear the alarm immediately. Go to Cause 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
Related Information
None.
A.3.17 AU_LOP
Description
The AU_LOP is an alarm indicating the loss of the AU pointer. This alarm occurs when a board detects the AU pointer of invalid values or with the NDF for eight consecutive frames.
Issue 03 (2012-07-30)
311
A Alarm Reference
Attribute
Parameters
None.

When the AU_LOP alarm occurs, the service in the alarmed AU-4 path is interrupted. If the services are configured with protection, protection switching may be triggered.
Possible Causes
l l Cause 1: The transmit unit of the opposite NE is faulty. 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... The alarm is cleared after the board is replaced The alarm persists after the board is replaced 2. 1. Then... The fault is rectified. End the alarm handling. Go to the next step.
Replace the system control board on the opposite NE. Replace the alarmed board.
Step 2 Cause 2: The receive unit of the local NE is faulty. ----End
Related Information
None.
A.3.18 B1_EXC
Description
The B1_EXC is an alarm indicating that the B1 errors (in the regenerator section) exceed the threshold. This alarm occurs when the board detects that the B1 errors exceed the preset B1_EXC alarm threshold (10-3 by default). An IF board that works in PDH mode may also report this alarm. This alarm is detected by using the self-defined overhead byte B1 in PDH microwave frames.
A Alarm Reference
Attribute
Alarm Severity Minor Alarm Type Service alarm
Parameters
None.

When the B1_EXC alarm occurs, the services on the port are interrupted.
Possible Causes
l l l l l Cause 1: The line performance degrades (if the alarm is reported by an SDH optical interface board). Cause 2: The line performance degrades (if the alarm is reported by an IF board). Cause 3: The network clock quality degrades. Cause 4: The board is faulty (if the alarm is reported by an SDH optical interface board). 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 interface board). 1. Check whether the transmit power at the opposite end and the receive power at the local end meet the specifications of the optical interfaces. For details, see 8.3.9 Browsing Current Performance Events. If... Then...
The transmit power of the opposite NE is Replace the board where the SDH over low optical interface unit is located on the opposite NE. The transmit power of the opposite NE is The fiber is faulty. Go to the next step. normal, but the receive power of the local NE 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 a channel. 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 the Ensure that the board is normal. fiber.
A Alarm Reference
3.
If the fiber is faulty, check whether the fiber jumper from the equipment to the optical distribution 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. Check whether the MW_BER_EXC, MW_BER_SD, MW_FEC_UNCOR or RPS_INDI alarm is reported. If yes, clear the alarm. Check the network clock status of the alarmed NE. If... The clock source of the local NE is different from the clock source of the opposite NE Then... The clock may become asynchronous and B1 errors may occur. Reconfigure the clock source, and ensure that the clock is synchronized on the local NE and opposite NE.
Step 2 Cause 2: The line performance degrades (if the alarm is reported by an IF board). 1.
Step 3 Cause 3: The network clock quality degrades. 1.
The clock of the local NE and the clock This may cause errors and even service of the opposite NE form a timing loop interruption. In this case, reconfigure the clock source 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 optical Replace the board where the alarmed interfaces are looped back line unit is located on the local NE. The fault is rectified after the optical interfaces are looped back Replace the board where the line unit is located on the opposite NE.
Step 5 Cause 5: The board is faulty (if the alarm is reported by an IF board). 1. Perform an inloop for the multiplexing interface of the IF board on the local NE. If... The fault is not rectified after the multiplexing interface is looped back Then... Replace the alarmed IF board on the local NE.
The fault is rectified after the multiplexing Replace the alarmed IF board on the interface is looped back opposite NE. ----End
Related Information
The handling procedure applies when this alarm is reported by the STM-1e port. Handle the errors of TDM services.
A.3.19 B1_SD
A Alarm Reference
Description
The B1_SD is an alarm indicating that the signal degrades due to the excessive B1 errors (in the regenerator section). This alarm occurs when the board detects that the B1 errors exceed the preset B1_SD alarm threshold (10-6 by default) but do not reach the preset B1_EXC alarm threshold (10-3 by default). An IF board that works in PDH mode may also report this alarm. This alarm is detected by using the self-defined overhead byte B1 in PDH microwave frames.
Attribute
Parameters
None.

When the B1_SD alarm occurs, the service performance on the port degrades.
Possible Causes
Procedure
The transmit power of the opposite NE is Replace the board where the SDH over low optical interface unit is located on the opposite NE. The transmit power of the opposite NE is The fiber is faulty. Go to the next step. normal, but the receive power of the local NE is close to the value (for example, within 3 dB) of the receiver sensitivity
A Alarm Reference
2.
Exchange the core fibers of the optical cables in the receive and transmit directions of a channel. If... Then...
The errors vary with the change of the fiber The fiber is faulty. Go to the next step. The errors do not vary with the change of the Ensure that the board is normal. fiber 3. If the fiber is faulty, check whether the fiber jumper from the equipment to the optical distribution 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 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... The clock source of the local NE is different from the clock source of the opposite NE Then... The clock may become asynchronous and errors may occur. Reconfigure the clock source, and ensure that the clock is synchronized on the local NE and opposite NE.
The clock of the local NE and the clock This may cause errors and even service of the opposite NE form a timing loop interruption. In this case, reconfigure the clock source 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 SDH optical line board of the local NE is faulty. Loop back the optical interfaces of the NE by using a fiber jumper to locate the fault. If... Then...
A Alarm Reference
Related Information
A.3.20 B2_EXC
Description
The B2_EXC is an alarm indicating that the B2 errors (in the multiplex section) exceed the threshold. This alarm occurs when the board detects that the number of B2 errors exceeds the preset B2_EXC alarm threshold (10-3 by default).
Attribute
Alarm Severity Major Alarm Type Service alarm
Parameters
None.

The services on the port are interrupted.
Possible Causes
Procedure
The transmit power of the opposite NE is Replace the board where the SDH over low optical interface unit is located on the opposite NE.
A Alarm Reference
If...
Then...
The transmit power of the opposite NE is The fiber is faulty. Go to the next step. normal, but the receive power of the local NE 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 a channel to locate the fault. 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 or RPS_INDI alarm is reported. If yes, clear the alarm.
The clock of the local NE and the clock This may cause errors and even service of the opposite NE form a timing loop interruption. In this case, reconfigure the clock source 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...
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.
Issue 03 (2012-07-30)
318
A Alarm Reference
If... The fault is not rectified after the multiplexing interface is looped back
Then... Replace the alarmed IF board on the local NE.
Related Information
A.3.21 B2_SD
Description
The B2_SD is an alarm indicating that the signal degrades due to the excessive B2 errors (in the multiplex section). This alarm occurs when the board detects that the number of B2 errors is higher than the preset B2_SD alarm threshold (10-6 by default) and lower than the preset B2_EXC alarm threshold (10-3 by default).
Attribute
Parameters
None.

The service performance on the port degrades.
Possible Causes
Procedure
Step 1 Cause 1: The line performance degrades (if the alarm is reported by an SDH optical interface board).
A Alarm Reference
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.9 Browsing Current Performance Events. If... Then...
The transmit power of the opposite NE is Replace the board where the SDH over low optical interface unit is located on the opposite NE. The transmit power of the opposite NE is The fiber is faulty. Go to the next step. normal, but the receive power of the local NE 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 a channel to locate the fault. 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.
The clock of the local NE and the clock This may cause errors and even service of the opposite NE form a timing loop interruption. In this case, reconfigure the clock source 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 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...
The fault is not rectified after the optical Replace the board where the alarmed interfaces are looped back line unit is located on the local NE.
A Alarm Reference
If... The fault is rectified after the optical interfaces are looped back
Then... Replace the board where the line unit is located on the opposite NE.
Related Information
A.3.22 B3_EXC
Description
The B3_EXC is an alarm indicating that the B3 errors (in the higher order path) exceed the threshold. This alarm occurs when the board detects that the number of B3 errors exceeds the preset B3_EXC alarm threshold (10-3 by default).
Attribute
Parameters
None.

When the B3_EXC alarm occurs, the service on the alarmed path is interrupted.
Possible Causes
l l l
Issue 03 (2012-07-30)
Cause 1: The line performance degrades (if the alarm is reported by an SDH optical interface board). Cause 2: The line performance degrades (if the alarm is reported by an IF board). Cause 3: The network clock quality degrades.
A Alarm Reference
l l
Cause 4: The board is faulty (if the alarm is reported by an SDH optical interface board). Cause 5: The board is faulty (if the alarm is reported by an IF board).
Procedure
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... The clock source of the local NE is different from the clock source of the opposite NE Then... In this case, the clock may become asynchronous and errors may occur. Reconfigure the clock source, and ensure that the clock is synchronized on the local NE and opposite NE.
The clock of the local NE and the clock This may cause errors and even service of the opposite NE form a timing loop interruption. In this case, reconfigure the clock source and release the timing loop. Step 4 Cause 4: The board is faulty (if the alarm is reported by an SDH optical interface board).
A Alarm Reference
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...
Related Information
A.3.23 B3_EXC_VC3
Description
The B3_EXC_VC3 alarm indicates that the number of B3 bit errors in a VC-3 path crosses the threshold. A board reports this alarm when detecting that the number of B3 bit errors crosses the B3_EXC_VC3 alarm threshold (10-3, by default).
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1
Issue 03 (2012-07-30)
Meaning Has a fixed value of 0x01.

A Alarm Reference
Name
Meaning
Parameter 2, Parameter 3 Indicate the ID of the VC-3 path that reports the alarm. For example, 0x00 0x01 indicate that the alarm is reported in VC-3 path 1.

The services in the alarmed path have a large number of bit errors.
Possible Causes
l l l l Cause 1: Higher-level bit error alarms occur in the system. Cause 2: The line performance deteriorates (the alarm is reported by an Ethernet optical port). Cause 3: The line performance deteriorates (the alarm is reported by an Ethernet electrical port). Cause 4: A board is faulty.
Procedure
Step 1 Cause 1: Higher-level bit error alarms occur in the system. 1. 2. 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. Check whether the alarm is cleared. If... The alarm is cleared The alarm persists Then... End the alarm handling. 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 Current Performance Events. If... Then...
The transmit power at the opposite site is Replace the optical module at the too low opposite site. The transmit power at the opposite site is A fiber is faulty. Go to the next step. normal, but the receive power at the local site is close to the receiver sensitivity (for example, a difference within 3 dB) 2. Exchange the optical fibers in the receive and transmit directions of an optical path segment. If... The number of bit errors changes The number of bit errors does not change
Then... Go to the next step. Go to Cause 4.

324
A Alarm Reference
3.
If a fiber is faulty, check whether the fiber jumper from the equipment to the optical distribution frame (ODF) and the fiber that is led out from the equipment room are pressed, and whether any fiber connector is dirty or damaged. If yes, clean or replace the fiber connector, or replace the fiber jumper. Check whether the alarm is cleared. If... The alarm is cleared The alarm persists Then... End the alarm handling. Go to Cause 4.
Step 3 Cause 3: The line performance deteriorates (the alarm is reported by an Ethernet electrical port). 1. 2. Check whether the cable grounding, cable connectors, and cables are damaged. If yes, replace the faulty cables. Check whether the alarm is cleared. If... The alarm is cleared The alarm persists 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... The fault is not rectified after the Ethernet port is looped back Then... Replace the alarmed Ethernet processing board at the local site. Then... End the alarm handling. Go to Cause 4.
The fault is rectified after the Ethernet Replace the Ethernet processing board at port is looped back the opposite site. ----End
Related Information
None.
A.3.24 B3_SD
Description
The B3_SD is an alarm indicating that the signal degrades due to the excessive B3 errors (in the higher order path). This alarm occurs when the board detects that the number of B3 errors is higher than the preset B3_SD alarm threshold (10-6 by default) and lower than the preset B3_EXC alarm threshold (10-3 by default).
Attribute
Issue 03 (2012-07-30)
Alarm Type Service alarm
325
A Alarm Reference
Parameters
None.

The service performance on the port degrades.
Possible Causes
Procedure
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 the Ensure that the board is normal. fiber 3. If the fiber is faulty, check whether the fiber jumper from the equipment to the optical distribution 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. Check whether the MW_BER_EXC, MW_BER_SD, MW_FEC_UNCOR alarm is generated. If yes, clear the alarm.
Step 2 Cause 2: The line performance degrades (if the alarm is reported by an IF board). 1.
Step 3 Cause 3: The network clock quality degrades.

A Alarm Reference
1.
Check the network clock status of the alarmed NE. If... The clock source of the local NE is different from the clock source of the opposite NE Then... In this case, the clock may become asynchronous and errors may occur. Reconfigure the clock source, and ensure that the clock is synchronized on the local NE and opposite NE.
The clock of the local NE and the clock This may cause errors and even service of the opposite NE form a timing loop interruption. In this case, reconfigure the clock source 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 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...
Related Information
A.3.25 B3_SD_VC3
Description
The B3_SD_VC3 alarm indicates a signal degrade (SD) condition caused by excessive B3 bit errors in VC-3 paths. A board reports this alarm when detecting that the number of B3 bit errors crosses the B3_SD_VC3 alarm threshold (10-6, by default).
Issue 03 (2012-07-30)
327
A Alarm Reference
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Has a fixed value of 0x01.
Parameter 2, Parameter 3 Indicate the ID of the path that reports the alarm. For example, 0x00 0x01 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.
Possible Causes
l l l l Cause 1: Higher-level bit error alarms occur in the system. Cause 2: The line performance deteriorates (the alarm is reported by an Ethernet optical port). Cause 3: The line performance deteriorates (the alarm is reported by an Ethernet electrical port). Cause 4: A board is faulty.
Procedure
Step 1 Cause 1: Higher-level bit error alarms occur in the system. 1. 2. 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. Check whether the alarm is cleared. If... The alarm is cleared The alarm persists Then... End the alarm handling. 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 Current Performance Events.
Issue 03 (2012-07-30)
A Alarm Reference
If...
Then...
The transmit power at the opposite site is Replace the optical module at the too low opposite site. The transmit power at the opposite site is A fiber is faulty. Go to the next step. normal, but the receive power at the local site is close to the receiver sensitivity (for example, a difference within 3 dB) 2. Exchange the optical fibers in the receive and transmit directions of an optical path segment. If... The number of bit errors changes The number of bit errors does not change 3. Then... Go to the next step. Go to Cause 4.
If a fiber is faulty, check whether the fiber jumper from the equipment to the optical distribution frame (ODF) and the fiber that is led out from the equipment room are pressed, and whether any fiber connector is dirty or damaged. If yes, clean or replace the fiber connector, or replace the fiber jumper. Check whether the alarm is cleared. If... The alarm is cleared The alarm persists Then... End the alarm handling. Go to Cause 4.
Step 3 Cause 3: The line performance deteriorates (the alarm is reported by an Ethernet electrical port). 1. 2. Check whether the cable grounding, cable connectors, and cables are damaged. If yes, replace the faulty cables. Check whether the alarm is cleared. If... The alarm is cleared The alarm persists 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... The fault is not rectified after the Ethernet port is looped back Then... Replace the alarmed Ethernet processing board at the local site. Then... End the alarm handling. Go to Cause 4.
The fault is rectified after the Ethernet Replace the Ethernet processing board at port is looped back the opposite site. ----End
Related Information
None.
A Alarm Reference
A.3.26 BAT1TEMP_SENSOR_FAIL
Description
The BAT1TEMP_SENSOR_FAIL is an alarm indicating that the temperature sensor of battery group 1 fails.
Attribute
Parameters
None.

The temperature data of battery group 1 cannot be collected.
Possible Causes
l l l l Cause 1: The temperature sensor of battery group 1 is faulty. Cause 2: The control board of the cabinet is faulty. Cause 3: Cables are misconnected or damaged. Cause 4: The temperature sensor is not installed.
Procedure
Step 1 Cause 1: The temperature sensor of battery group 1 is faulty. 1. 2. Replace the temperature sensor of battery group 1. Then, check whether the alarm clears. If... The alarm clears The alarm persists Then... End the alarm handling. Go to Cause 2.
Step 2 Cause 2: The control board of the cabinet is faulty. 1. 2. Replace the cabinet. Then, check whether the alarm clears. If... The alarm clears The alarm persists Then... End the alarm handling. Go to Cause 3.
Step 3 Cause 3: Cables are misconnected or damaged.

A Alarm Reference
1. 2. 1.
Replace damaged cables. Connect cables correctly. Install the temperature sensor.
Step 4 Cause 4: The temperature sensor is not installed.
----End
Related Information
None.
A.3.27 BAT2TEMP_SENSOR_FAIL
Description
The BAT2TEMP_SENSOR_FAIL is an alarm indicating that the temperature sensor of battery group 2 fails.
Attribute
Parameters
None.

The temperature data of battery group 2 cannot be collected.
Possible Causes
l l l l Cause 1: The temperature sensor of battery group 2 is faulty. Cause 2: The control board of the cabinet is faulty. Cause 3: Cables are misconnected or damaged. Cause 4: The temperature sensor is not installed.
Procedure
Step 1 Cause 1: The temperature sensor of battery group 2 is faulty. 1. 2. Replace the temperature sensor of battery group 2. Then, check whether the alarm clears. If... The alarm clears The alarm persists
Issue 03 (2012-07-30)
Then... End the alarm handling. Go to Cause 2.

331
A Alarm Reference
Step 3 Cause 3: Cables are misconnected or damaged. 1. 2. Replace damaged cables. Connect cables correctly.
Step 4 Cause 4: The temperature sensor is not installed. 1. Install the board temperature sensor.
----End
Related Information
None.
A.3.28 BD_NOT_INSTALLED
Description
The BD_NOT_INSTALLED is an alarm indicating that the physical board is installed in a certain slot, but the logical board is not added.
Attribute
Alarm Severity Minor Alarm Type Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1, Parameter 2 Meaning Indicates the ID of the slot.

When the BD_NOT_INSTALLED alarm occurs, the physical board in this slot cannot work.
A Alarm Reference
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.29 BD_STATUS
Description
The BD_STATUS is an alarm indicating that the board cannot be detected.
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 l l l Cause 1 of the alarm reported by a board of the IDU: The board is installed in an incorrect slot. Cause 2 of the alarm reported by a board of the IDU: The board and the backplane are not connected properly. Cause 3 of the alarm reported by a board of the IDU: The slot is faulty. 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 l
Issue 03 (2012-07-30)
Cause 1 of the alarm reported by the ODU: The other alarms are generated. Cause 2 of the alarm reported by the ODU: The ODU is faulty.
A Alarm Reference
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... The alarmed board is installed in an incorrect slot The alarmed board is installed in a correct slot Then... Install the board in a correct slot. Ensure that the board and the backplane are connected properly.
Step 2 Cause 2 of the alarm reported by a board of the IDU: The board and the backplane are not connected properly. 1. Remove and insert the alarmed board. If... The alarm is cleared after the board is removed and inserted The alarm persists after the board is removed and inserted Then... The fault is rectified. End the alarm handling. Ensure that the board is normal.
Step 3 Cause 3 of the alarm reported by a board of the IDU: The slot is faulty. 1. Contact Huawei engineers to handle the fault of the slot.
TIP
Generally, the slot becomes faulty due to the broken pin or bent pin. Remove the board, and use a torch 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. 1. Replace the alarmed board. If... The alarm is cleared after the board is replaced The alarm persists after the board is replaced Then... The fault is rectified. End the alarm handling. 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... The IF board reports any of the preceding alarms The IF board does not report any of the preceding alarms
Then... Clear the alarm immediately. Replace the alarmed ODU.
334
A Alarm Reference
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.30 BDTEMP_SENSOR_FAIL
Description
The BDTEMP_SENSOR_FAIL is an alarm indicating that the board temperature sensor of the cabinet fails.
Attribute
Parameters
None.

The board temperature data of the TCU cannot be collected.
Possible Causes
l l l l Cause 1: The board temperature sensor is faulty. Cause 2: The control board of the cabinet is faulty. Cause 3: Cables are misconnected or damaged. Cause 4: The board temperature sensor is not installed.
Procedure
Step 1 Cause 1: The board temperature sensor is faulty. 1. 2. Replace the board temperature sensor. Then, check whether the alarm clears. If... The alarm clears The alarm persists Then... End the alarm handling. Go to Cause 2.
Step 2 Cause 2: The control board of the cabinet is faulty. 1.

Issue 03 (2012-07-30)
Replace the cabinet.

A Alarm Reference
2.
Then, check whether the alarm clears. If... The alarm clears The alarm persists Then... End the alarm handling. Go to Cause 3.
Step 3 Cause 3: Cables are misconnected or damaged. 1. 2. 1. Replace damaged cables. Connect cables correctly. Install the board temperature sensor.
Step 4 Cause 4: The board temperature sensor is not installed.
----End
Related Information
None.
A.3.31 BIOS_STATUS
Description
The BIOS_STATUS is an alarm indicating that the board is in BIOS state.
Attribute
Alarm Severity Major Alarm Type Processing alarm
Parameters
Name Parameter 1 Meaning Indicates the slot ID of the board that is in BIOS state.

The services on the alarmed board are interrupted.
Possible Causes
l l Cause 1: The board software is lost. Cause 2: The board software becomes abnormal.
Procedure
Step 1 Perform a cold reset on the alarmed standby system control, switching, and timing board, and then check whether the alarm is cleared.
A Alarm Reference
Step 2 If the alarm persists, remove the standby system control, switching, and timing board, and then reseat the board. Step 3 If the alarm persists, replace the board. ----End
Related Information
None.
A.3.32 BIP_EXC
Description
The BIP_EXC is an alarm indicating that the BIP errors exceed the threshold. This alarm occurs when the board detects that the number of BIP-2 errors (in byte V5) exceeds the preset BIP_EXC alarm threshold (10-3 by default).
Attribute
Parameters
None.

When the BIP_EXC alarm occurs, the service on the alarmed path is interrupted.
Possible Causes
l l l l Cause 1: The line performance degrades (if the alarm is reported by an E1 service board). Cause 2: The line performance degrades (if the alarm is reported by a Hybrid IF board). Cause 3: The board is faulty (if the alarm is reported by an E1 service board). 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.
A Alarm Reference
If... There is any of the preceding alarms No such alarms occur
Then... Clear the alarm immediately. Ensure that the board is normal.
Step 2 Cause 2: The line performance degrades (if the alarm is reported by a Hybrid IF board). 1. Check whether any alarm occurs on the tributary board or IF board that transmits the service signal. If yes, clear the alarm immediately. Replace the board where the E1 service unit is located. Then, check whether the alarm is cleared. If... The alarm is cleared The alarm persists Then... End the alarm handling. Replace the system control and cross-connect board.
Step 3 Cause 3: The board is faulty (if the alarm is reported by an E1 service board). 1.
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... The alarm is cleared The alarm persists ----End Then... End the alarm handling. Replace the system control and cross-connect board.
Related Information
Handle the errors of TDM services. 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 Parameter 1 Parameter 2, Parameter 3 Meaning The value is always 0x01. Indicate the ID of the path that reports the alarm. For example, 0x00 0x01 indicate that the alarm is reported in path 1.
A.3.33 BIP_SD
Description
The BIP_SD is an alarm indicating that the signal degrades due to the BIP errors. This alarm occurs when the board detects that the number of BIP-2 errors (in byte V5) is higher than the
A Alarm Reference
preset BIP_SD alarm threshold (10-6 by default) and lower than the preset BIP_EXC alarm threshold (10-3 by default).
Attribute
Parameters
None.

When the BIP_SD alarm occurs, the service on the alarmed path degrades.
Possible Causes
l l l l Cause 1: The line performance degrades (if the alarm is reported by an E1 service board). Cause 2: The line performance degrades (if the alarm is reported by a Hybrid IF board). Cause 3: The board is faulty (if the alarm is reported by an E1 service board). 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... There is any of the preceding alarms No such alarms occur Then... Clear the alarm immediately. Ensure that the board is normal.
Step 2 Cause 2: The line performance degrades (if the alarm is reported by a Hybrid IF board). 1. Check whether any alarm occurs on the tributary board or IF board that transmits the service signal. If... An alarm occurs No alarm occurs Then... Clear the alarm immediately. 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 alarm is cleared.
Issue 03 (2012-07-30)
A Alarm Reference
If... The alarm is cleared The alarm persists
Then... End the alarm handling. 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... The alarm is cleared The alarm persists ----End Then... End the alarm handling. Replace the system control and cross-connect board.
Related Information
Handle the errors of TDM services. The alarm parameters have the meanings listed in Table A-4 when EMS6 board report the alarm. Table A-4 Alarm Parameters of EMS6 Name Parameter 1 Parameter 2, Parameter 3 Meaning The value is always 0x01. Indicate the ID of the path that reports the alarm. For example, 0x00 0x01 indicate that the alarm is reported in path 1.
A.3.34 BOOTROM_BAD
Description
The BOOTROM_BAD is an alarm indicating that the BOOTROM data consistency check fails. This alarm occurs when the BOOTROM data is damaged during a periodical check by the system.
Attribute
Parameters
A Alarm Reference
Name Parameter 1 Parameter 2, Parameter 3
Meaning The value is always 0x01. Indicates the type of the BOOTROM damage. l 0x00, 0x01: damage of the basic BIOS l 0x00, 0x02: damage of the extended BIOS
Parameter 4, Parameter 5
The values are always 0xff 0xff.

When the BOOTROM_BAD alarm occurs, it indicates that errors occur in the system database processing. The system configuration may be lost. As a result, the failure indication is returned for certain query and setting commands, and certain system functions cannot work. l l When the NE is already started, the BOOTROM_BAD alarm does not affect the system and services. If the BOOTROM_BAD alarm occurs and a hard reset is performed on a board, the board fails to load the BIOS and cannot be started.
Possible Causes
l l l l Cause 1: The basic BIOS is damaged. Cause 2: The extended BIOS is damaged. Cause 3: The BOOTROM database is damaged. Cause 4: The system control switch and timing boardis faulty.
Procedure
Step 1 Replace the alarmed board. ----End
Related Information
None.
A.3.35 BUS_ERR
Description
The BUS_ERR alarm indicates bus errors. This alarm occurs when the bus becomes abnormal.
Attribute
Issue 03 (2012-07-30)
Alarm Type Equipment alarm
341
A Alarm Reference
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the bus error types. l 0x01: BUS_LOS l 0x02: BUS_OOF l 0x03: BUS_LOF l 0x04: BUS_OOA l 0x05: BUS_RX_DOWN l 0x06: BUS_TX_DOWN l 0x07: BUS_SPI_DOWN l 0x08: BUS_SCI_ERR l 0x09: BUS_OPP_CLK_LOC l 0x0a:BUS_SERDS_ERR l 0x0b:BUS_MII_ERR l 0x0c:BUS_HW_ERR l 0x0d:BUS_FE_ERR l 0x0e:BUS_EMIF_ERR l 0x0f:BUS_IIC_ERR l 0x10:BUS_GE_LINK_ERR l 0x11:BUS_EMIF Parameter 2 Parameter 3 Indicates the ID of the bus that has errors. This parameter is self-defined.

When the BUS_ERR alarm occurs, the services that travel along the faulty bus are interrupted or have errors.
Possible Causes
The possible causes of the BUS_ERR alarm are as follows: l l Cause 1: The board is not properly inserted. Cause 2: A certain board is faulty.
Issue 03 (2012-07-30)
342
A Alarm Reference
Procedure
Step 1 Cause 1: The board is not properly inserted. 1. Remove and insert the board.
Step 2 Cause 2: A certain board is faulty. 1. Perform a cold reset on the alarmed board. Then, check whether the alarm is cleared. If... The alarm is cleared The alarm persists ----End Then... The fault is rectified. End the alarm handling. Replace the alarmed board.
Related Information
The alarm parameters have the meanings listed in Table A-5 when EMS6 board report the alarm. Table A-5 Alarm parameters of EMS6 Name Parameter 1 Meaning Indicates the bus error type. 0x10: The Serdes bus of the GE bridge is faulty.
A.3.36 CES_ACR_LOCK_ABN
Description
The CES_ACR_LOCK_ABN is an alarm indicating that the locking function of CES ACR service clock is abnormal.
Attribute
Parameters
Name Meaning
Parameter 1 to Parameter 4 Indicate the index of PW that carries the services associated with the ACR clock source.
Issue 03 (2012-07-30)
343
A Alarm Reference
Name Parameter 5
Meaning 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 Causes
l l l Cause 1: CES ACR services are unavailable or have alarms. Cause 2: The network is unstable. Cause 3: NEs on the service path are abnormal.
Procedure
Step 1 Cause 1: CES ACR services are unavailable or have alarms. 1. 2. Query the CES services associated with the ACR clock source. For details, see Configuring the Primary Clock for an ACR Clock Domain. Check whether these services have alarms. For details, see 8.3.3 Browsing Current Alarms.
Step 2 Cause 2: The network is unstable. 1. 2. Check for jitters and delays on the network. Query service performance statistics. For details, see 8.3.9 Browsing Current Performance Events. 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. 2. Query alarms reported by the NEs on the service path. For details, see 8.3.3 Browsing Current Alarms. Handle the alarms. For details, see A.3 Alarms and Handling Procedures.
----End
Related Information
None.
Issue 03 (2012-07-30)
344
A Alarm Reference
A.3.37 CES_APS_INDI
Description
The CES_APS_INDI is an alarm indicating the status of the packet linear MSP. This alarm is reported when the configured packet linear MSP is in the switching state.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the ID of the MSP protection group.

l When this alarm occurs, automatic protection switching or switching triggered by an external command occurs. As a result, services are switched to the protection channel for transmission. This alarm does not affect the services. If the protection channel fails at this time, the services are interrupted.
Possible Causes
l l l l Cause 1: An external command is issued to trigger switching (such as manual switching, forced switching, exercise switching, and lockout of switching). Cause 2: There is an alarm (such as the R_LOS, R_LOF, MS_AIS, B2_EXC, or B2_SD alarm) or a cold reset that triggers automatic MSP switching. Cause 3: The attributes of the MSP protection group are incorrectly configured. Cause 4: The interface board is faulty.
Procedure
Step 1 Cause 1: An external command is issued to trigger switching (such as manual switching, forced switching, exercise switching, and lockout of switching). 1.
Issue 03 (2012-07-30)
Check the switching status of the protection group.

A Alarm Reference
If... The MSP is in the state of manual switching, forced switching, or exercise switching The MSP is not in any of the preceding switching state
Then... Clear the switching status. Check whether the alarm is cleared. If the alarm persists, go to Step 2. Go to Step 2.
Step 2 Cause 2: There is an alarm (such as the R_LOS, R_LOF, MS_AIS, B2_EXC, or B2_SD alarm) or a cold reset that triggers automatic MSP switching. 1. Check whether the protection group is in the automatic switching state. If... Then...
The local NE reports the R_LOS, The MSP protection group changes to the R_LOF, MS_AIS, or B2_EXC alarm switching state, and the CES_APS_INDI alarm is reported. Clear the alarm immediately. Then check whether the CES_APS_INDI alarm is cleared. If the alarm persists, go to the next step. The local NE reports the B2_SD alarm Clear the alarm immediately. Then check whether the CES_APS_INDI alarm is cleared. If the alarm persists, go to the next step. The interface board is in the cold resetting state After the cold resetting ends, go to step 3 and identify the cause of the cold resetting.
The MSP is not in any of the preceding Go to the next step. switching state 2. Check the method for setting the revertive mode of the protection group. If... Revertive Mode is set to Revertive Then... After the working channel recovers, the services are automatically switched from the protection channel to the working channel once the preset wait to restore (WTR) time expires. The CES_APS_INDI alarm will be cleared after the switching succeeds. Wait until the MSP protection group changes from the switching status to the normal status. Then check whether the CES_APS_INDI alarm is cleared. If the alarm persists, go to Step 3.
Issue 03 (2012-07-30)
346
A Alarm Reference
If... Revertive Mode is set to NonRevertive
Then... The services are not switched from the protection channel to the working channel after the working channel recovers, and the CES_APS_INDI alarm persists. To clear the CES_APS_INDI alarm, manually switch the services from the protection channel to the working channel. Then go to the next step.
3.
After the manual switching succeeds, check whether the alarm is cleared. If the alarm persists, go to Step 3. If the packet linear MSP is configured on a per-NE basis, check whether the MSP parameters such as the protection type, switching mode, and mapping unit are configured correctly. If any of the preceding parameter values are incorrect, change the values and apply correct settings to the NE. For details, see Configuring Linear MSP. Check whether the alarm is cleared. If the alarm persists, go to Step 4. Check whether the interface board that is configured with the packet linear MSP is functioning properly. If a hardware alarm such as HARD_BAD occurs on the interface board, clear the alarm immediately. Replace the interface board. For details, see 6 Part Replacement.
Step 3 Cause 3: The attributes of the MSP protection group are incorrectly configured. 1.
2. 1. 2. 3.
Step 4 Cause 4: The interface board is faulty.
----End
Related Information
None.
A.3.38 CES_APS_MANUAL_STOP
Description
The CES_APS_MANUAL_STOP is an alarm indicating that the packet linear MSP protocol is stopped manually. This alarm is reported when the packet linear MSP protocol is stopped manually.
Attribute
Parameters
A Alarm Reference
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the ID of the MSP protection group.

When this alarm occurs, the packet linear MSP protocol is stopped and the MSP fails. As a result, STM-1 services cannot be protected.
Possible Causes
Cause 1: The APS protocol for the corresponding protection group is manually stopped.
Procedure
Step 1 Cause 1: The APS protocol for the corresponding protection group is manually stopped. 1. 2. Determine the ID of the MSP protection group whose APS protocol is stopped according to alarm parameters. Restart the MSP protocol for the protection group.
----End
Related Information
None.
A.3.39 CES_JTROVR_EXC
Description
The CES_JTROVR_EXC is an alarm indicating that the number of jitter buffer overflows crosses the specified threshold. This alarm occurs when the board detects that, the number of jitter buffer overflows per second crosses the specified threshold.
Attribute
Parameters
None.

The buffer area does not have sufficient space for the received frames. As a result, packets are discarded.
A Alarm Reference
Possible Causes
l l Cause 1: The size of buffer area is set to a low value. Cause 2: The PSN network clocks used for the transmission of CES services are not synchronized.
Procedure
Step 1 Cause 1: The size of buffer area is set to a low value. 1. 2. Query the size of buffer area. For details, see Querying CES Service Information. 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 not synchronized. 1. Synchronize the PSN network clock by setting clock synchronization, reducing transmission nodes, and optimizing transmission routes.
----End
Related Information
None.
A.3.40 CES_JTRUDR_EXC
Description
The CES_JTRUDR_EXC is an alarm indicating that the number of jitter buffer underflows crosses 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
Parameters
None.

When this alarm occurs, no packets are available in the buffer area for transmission. As a result, underflows occur in the buffer area.
Possible Causes
l
Issue 03 (2012-07-30)
Cause 1: Signals degrade on the link.

A Alarm Reference
l l l l
Cause 2: The PSN network clocks used for the transmission of CES services are not synchronized. Cause 3: The link is looped. Cause 4: The link is congested. 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 not synchronized. 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. 2. Query the size of buffer area. For details, see Querying CES Service Information. 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
Related Information
None.
A.3.41 CES_K1_K2_M
Description
The CES_K1_K2_M is an alarm indicating that the K1 byte and K2 byte of the packet MSP mismatch. This alarm is reported when the channel numbers indicated in the transmitted K1 byte and the received K2 byte are inconsistent and the inconsistency lasts for a period of time (160 ms by default).
Attribute
Issue 03 (2012-07-30)
350
A Alarm Reference
Parameters
None.

When this alarm occurs, MSP fails. If a fiber cut or another fault occurs at this time, services may be interrupted.
Possible Causes
l l Cause 1: MSP is incorrectly configured. Cause 2: The interface board is faulty.
Procedure
Step 1 Cause 1: MSP is incorrectly configured. 1. Check whether the MSP configurations are consistent between the local and opposite NEs. For example, ensure that the other end is configured as the working unit if one end of a fiber is configured as the working unit; otherwise, the CES_K1_K2_M alarm is reported. Ensure that MSP is configured correctly. Then, check whether the alarm is cleared. If the alarm persists, go to Step 2. Check whether the interface boards on which MSP is configured are functioning properly on the local and opposite NEs. If a hardware alarm such as HARD_BAD occurs on the interface board, clear the alarm immediately. If the alarm persists, replace the interface board. For details, see 6.10 Replacing the System Control, Switch and Timing Board.
2.
Step 2 Cause 2: The interface board is faulty. 1. 2. 3.
----End
Related Information
None.
A.3.42 CES_K2_M
Description
The CES_K2_M is an alarm indicating that a mismatched K2 byte of the packet MSP is detected. This alarm is reported when the protection mode used on the opposite NE, which is indicated by bit 5 of the received K2 byte, is different from that used on the local NE for a period of time (2s by default).
Issue 03 (2012-07-30)
351
A Alarm Reference
Attribute
Parameters
None.

When this alarm occurs, MSP fails. If a fiber cut or another fault occurs at this time, services may be interrupted.
Possible Causes
l l Cause 1: Different protection modes are configured at both ends of a protection group. Cause 2: The interface board is faulty.
Procedure
Step 1 Cause 1: Different protection modes are configured at both ends of a protection group. 1. Check whether the same protection mode is configured at both ends of a protection group. If 1+1 protection is configured at one end and 1:N protection is configured at the other end, the CES_K2_M alarm is reported. For details, see Creating a Linear MSP Protection Group.
Step 2 Cause 2: The interface board is faulty. 1. 2. 3. Check whether the interface boards on which MSP is configured are functioning properly on the local and opposite NEs. If a hardware alarm such as HARD_BAD occurs on the interface board, clear the alarm immediately. If the alarm persists, replace the interface board. For details, see 6.10 Replacing the System Control, Switch and Timing Board.
----End
Related Information
None.
A.3.43 CES_LOSPKT_EXC
Description
The CES_LOSPKT_EXC is an alarm indicating that the number of lost packets of CES services crosses the threshold in a time unit. This alarm occurs when the board detects that the number of lost packets per second crosses the specified threshold.
A Alarm Reference
Attribute
Parameters
None.

When this alarm occurs, all 1s are inserted and services are interrupted.
Possible Causes
l l l Cause 1: Signals degrade on the link. Cause 2: The link is looped. Cause 3: The link is congested.
Procedure
Step 1 Cause 1: Signals degrade on the link. 1. 1. 1. Troubleshoot the link. For details, see 5.3 Troubleshooting the Radio Link. Release the loop. 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 2 Cause 2: The link is looped. Step 3 Cause 3: The link is congested.
----End
Related Information
Packets are lost when the sequence numbers of received packets are greater than expected.
A.3.44 CES_MALPKT_EXC
Description
The CES_MALPKT_EXC is an alarm indicating that, in a time unit, the number of deformed frames in CES services crosses the threshold. This alarm occurs when the board detects that the number of deformed frames in CES services crosses the specified threshold.
Attribute
Issue 03 (2012-07-30)
Alarm Type Communication alarm
353
A Alarm Reference
Parameters
None.

A deformed frame is discarded once it is detected. As a result, the packet loss rate increases and services are affected.
Possible Causes
l l Cause 1: The RTP head enabling status is different between the two ends of the PW. 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. Troubleshoot the link. For details, see 5.3 Troubleshooting the Radio Link.
Step 2 Cause 2: Bit errors occur on the link. 1. ----End
Related Information
If a CESoPSN frame contains valid TDM data and does not contain any error indication, but the size of the CESoPSN frame is not consistent with the specified size, a deformed CESoPSN frame is generated.
A.3.45 CES_MISORDERPKT_EXC
Description
The CES_MISORDERPKT_EXC is an alarm indicating that, in a unit time, the number of lost disordered packets crosses the specified threshold. This alarm occurs when the board detects that the number of lost disordered packets per second crosses the specified threshold.
Attribute
Parameters
None.

The packets are disordered. As a result, the packet loss rate increases and services are affected.
A Alarm Reference
Possible Causes
l l l Cause 1: Signals degrade on the link. Cause 2: The link is looped. Cause 3: The link is congested.
Procedure
Step 1 Cause 1: Signals degrade on the link. 1. 1. 1. See 5.3 Troubleshooting the Radio Link. Release the loop. 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 2 Cause 2: The link is looped. Step 3 Cause 3: The link is congested.
----End
Related Information
Packets are disordered when the sequence numbers of received packets are smaller than expected.
A.3.46 CES_RDI
Description
The CES_RDI is an alarm of remote defect indication. When the CES_LOSPKT_EXC alarm is reported at the remote end, the remote end sets the R bit in control word to 1. Upon receiving a packet in which the R bit is 1, the local end reports the CES_RDI alarm.
Attribute
Parameters
None.

The packet loss rate at the remote end crosses the specified threshold.
Possible Causes
l l
Issue 03 (2012-07-30)
Cause 1: Signals degrade on the link. Cause 2: The link is looped.

A Alarm Reference
Cause 3: The link is congested.
Procedure
Step 1 Cause 1: Signals degrade on the link. 1. See 5.3 Troubleshooting the Radio Link. Step 2 Cause 2: The link is looped. 1. Release the loop. Step 3 Cause 3: 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.
----End
Related Information
None.
A.3.47 CES_STRAYPKT_EXC
Description
The CES_STRAYPKT_EXC is an alarm indicating that, in a time unit, the number of errored packets in CES services crosses the threshold. This alarm occurs when the board detects that the number of errored packets in CES services per second crosses the specified threshold.
Attribute
Parameters
None.

An errored packet is discarded once it is detected. As a result, the packet loss rate increases and services are affected.
Possible Causes
Cause 1: Links are misconnected.
Procedure
Step 1 Cause 1: Links are misconnected.
A Alarm Reference
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 from expected.
A.3.48 CESPW_OPPOSITE_ACFAULT
Description
The CESPW_OPPOSITE_ACFAULT is an alarm indicating that the AC circuit on the remote NE is faulty. On detection of an AC circuit fault, the remote NE sets the L bit in the control word to 1. When receiving a packet in which the L bit is 1, the local NE reports the CESPW_OPPOSITE_ACFAULT alarm.
Attribute
Parameters
None.

Possible Causes
Cause 1: The remote NE reports the T_ALOS, UP_E1_AIS, LFA, LMFA, R_LOS, R_LOF, or MS_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 Alarm Reference
A.3.49 CESPW_OPPOSITE_RAI
Description
The CESPW_OPPOSITE_RAI is a remote alarm indication. On detection of the RAI alarm, the remote NE sets the L bit of the control word to 0 and the M field of the control word to 10. When receiving the packet in which the L bit is 0 and the M field is 10, the local NE reports the CESPW_OPPOSITE_RAI alarm.
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.50 CFCARD_FAILED
Description
The CFCARD_FAILED is an alarm indicating that the operation on the CF card fails.
Attribute
Issue 03 (2012-07-30)
358
A Alarm Reference
Parameters
None.

When the CFCARD_FAILED alarm occurs, the database cannot be backed up to the CF card or be restored from the CF card. This alarm may cause rollback of the package loading upgrade.
Possible Causes
l l l Cause 1: The CF card fails to be initialized. Cause 2: The file system of the CF card does not match. Cause 3: The system control and communication board is faulty, and the file system of the CF card fails to be created.
Procedure
Step 1 Cause 1: The CF card fails to be initialized. Cause 2: The file system of the CF card does not match. 1. Replace the CF card and check whether the alarm is cleared. If... Yes No Then... End the alarm handling. Go to Cause 3.
Step 2 Cause 3: The system control and communication board is faulty, and the file system of the CF card fails to be created. 1. 2. Check whether the HARD_BAD alarm occurs on the system control and communication board. If yes, perform a cold reset on the system control and communication board. Then, check whether the alarm is cleared. If... Yes No ----End Then... End the alarm handling. Replace the system control and communication board.
Related Information
None.
A.3.51 CFCARD_OFFLINE
Description
The CFCARD_OFFLINE is an alarm indicating that the CF card is offline.
A Alarm Reference
Attribute
Parameters
None.

When the CFCARD_OFFLINE alarm occurs, the database cannot be backed up to the CF card or be restored from the CF card. This alarm may cause rollback of the package loading upgrade.
Possible Causes
l l l l Cause 1: The CF card is not inserted. Cause 2: The CF card is in poor contact with the system control and communication board. Cause 3: The CF card is faulty. 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... No Yes Then... Install the CF card. Go to Cause 2.
Step 2 Cause 2: The CF card is in poor contact with the system control and communication board. 1. 2. Check whether the CF card is loosened. If yes, re-insert the CF card. Check whether the alarm is cleared. If... Yes No Then... End the alarm handling. Go to Cause 3.
Step 3 Cause 3: The CF card is faulty. 1. 2. Replace the CF card. Check whether the alarm is cleared. If... Yes No
Issue 03 (2012-07-30)

A Alarm Reference
Step 4 Cause 4: The system control and communication board is faulty. 1. 2. 3. Check whether the HARD_BAD alarm occurs on the system control and communication board. If yes, perform a cold reset on the system control and communication board. Then, check whether the alarm is cleared. If the alarm persists, replace the system control and communication board.
----End
Related Information
None.
A.3.52 CHCS
Description
The CHCS is an alarm indicating the correctable cell error. When a correctable bit error is detected in the cell header, the CHCS alarm occurs.
Attribute
Parameters
None.

When the CHCS alarm occurs, the services are not affected. The alarm only indicates that some cells with a bit error are detected during cell delimitation at the ATM port.
Possible Causes
l l Cause 1: A few bit errors occur in the receive tunnel corresponding to the alarmed ATM port. 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. 2. 3. On the NMS, check whether the receive tunnel reports any alarms about excessive bit errors, such as B1_SD, B2_SD, and B3_SD. On the NMS, check whether the service is looped. If yes, modify the service configuration to release the loop, and then check whether the alarm is cleared.
Issue 03 (2012-07-30)
A Alarm Reference
Step 2 Cause 2: The ATM physical-layer processing chip of the board is faulty. 1. 2. Perform a cold reset on the board that reports the CHCS alarm and check whether the alarm is cleared. For details, see 8.8.1 Cold Reset. 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.6 Replacing the Smart E1 Interface Board.
NOTE
Board replacement is not recommended because the alarm does not affect the services.
----End
Related Information
None.
A.3.53 CLK_LOCK_FAIL
Description
The CLK_LOCK_FAIL is an alarm indicating a clock locking failure.
Attribute
Parameters
Parameter 1 l 0x01: indicates that the phase-locked loop (PLL) is in holdover or free-run mode. l 0x02: indicates that the timestamp in the Sync message remains the same in Precision Time Protocol (PTP) synchronization mode. l 0x03: indicates that the phase discrimination value within the given time has crossed the upper threshold.

When this alarm occurs, the clock of the slave NE fails to trace that of the master NE, and bit errors may occur.
A Alarm Reference
Possible Causes
l l l l Cause 1: Frequency deviation of the clock source has crossed the upper threshold in physical synchronization mode. Cause 2: The physical link where the clock source resides is faulty in physical synchronization mode. Cause 3: Frequency deviation of the clock source has crossed the upper threshold in IEEE 1588v2 synchronization mode. Cause 4: The physical link where the clock source resides is faulty in IEEE 1588v2 synchronization mode.
Procedure
Step 1 Cause 1: Frequency deviation of the clock source has crossed the upper threshold in physical synchronization mode. 1. 2. 3. Check whether high-level bit error alarms or performance events have been reported on the NMS. If yes, handle them immediately. If there is an external clock source, check whether its clock signals are normal. If no, replace the external clock source. For details, see Configuring the Clock Sources. Check whether clock configurations are correct. For example, if the input and output modes of the external clock source do not match each other, modify the configurations. For details, see Modifying the Parameters of the Clock Output.
Step 2 Cause 2: The physical link where the clock source resides is faulty in physical synchronization mode. 1. 2. If there is an external clock source, check whether the NE reports the SYNC_C_LOS alarm. If yes, clear the alarm immediately. If the CLK_LOCK_FAIL alarm persists, 6.10 Replacing the System Control, Switch and Timing Board and .
Step 3 Cause 3: Frequency deviation of the clock source has crossed the upper threshold in IEEE 1588v2 synchronization mode. 1. 2. Check whether high-level bit error alarms or performance events have been reported on the NMS. If yes, handle them immediately. If there is an external clock source, check whether its clock signals are normal. If no, replace the IEEE 1588v2 clock port. For details, see Replacing the IEEE 1588v2 Clock Port.
Step 4 Cause 4: The physical link where the clock source resides is faulty in IEEE 1588v2 synchronization mode. 1. 2. If the SYN_BAD alarm exists, clear the alarm immediately. If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
Issue 03 (2012-07-30)
363
A Alarm Reference
A.3.54 CLK_NO_TRACE_MODE
Description
The CLK_NO_TRACE_MODE alarm indicates that a clock source is not in locked mode. This alarm is reported when the current clock does not trace any clock sources.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the clock mode. l 0x01: holdover l 0x02: free-run

When the clock source is not in the locked mode, the system clock is not of high quality. Services may have bit errors when the clocks of the NEs are not synchronized. Pointer justification may occur in TDM services. If a base station traces a clock that is carried by an Ethernet service, an alarm indicating a large clock frequency deviation may occur.
Possible Causes
l l Cause 1: The system clock source priority table is not configured. 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. 1. Troubleshoot the synchronization sources that are listed in the clock source priority table.
Issue 03 (2012-07-30)
364
A Alarm Reference
If... The synchronization source is an external clock The synchronization source is a line clock The synchronization source is an IF clock The synchronization source is a tributary clock The synchronization source is an Ethernet clock ----End
Then... Handle the EXT_SYNC_LOS alarm. Handle the alarm that occurs on the line board. Handle the alarm that occurs on the IF board. Handle the alarm that occurs on the tributary board. Handle the alarm that occurs on the Ethernet board.
Related Information
None.
A.3.55 COMMUN_FAIL
Description
The COMMUN_FAIL is an alarm indicating the inter-board communication failure. This alarm is reported when the communication between a board and the SCC board is interrupted.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the ID of the port. The value is always 0x01.
Parameter 2, Parameter 3 Indicates the ID of the path on which the alarm is generated. Parameter 2 is always 0x00. Parameter 3 has the following meanings: 0x03: inter-board Ethernet communication
Issue 03 (2012-07-30)
365
A Alarm Reference
Name
Meaning
Parameter 4, Parameter 5 Parameters 4 and 5 are reserved, and their values are always 0xFF.

The NE configuration cannot be delivered to the board or the board cannot work. Consequently, the services cannot be configured or the protection switching function is unavailable.
Possible Causes
l l l l Cause 1: A certain board is reset. Cause 2: A board and the backplane are connected improperly. Cause 3: The alarmed board is faulty. Cause 4: A slot is faulty.
Procedure
Step 1 Cause 1: A certain board is reset. 1. After you reset the board, the alarm is cleared 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... The alarm is cleared after the board is removed and inserted The alarm persists after the board is replaced. 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... The alarm is cleared after the board is replaced The alarm persists after the board is replaced Step 4 Cause 3: A slot is faulty. 1. Contact Huawei engineers to handle the faulty slot.
TIP
Then... The fault is rectified. End the alarm handling. Clear the alarm according to the solution for the alarm that is generated when a board is faulty.
Then... The fault is rectified. End the alarm handling. Clear the alarm according to the solution for the alarm that is generated when a slot is faulty.
The slot becomes faulty due to broken pins or bent pins. Remove the board, and use a torch to check whether any pins are broken or bent.
Issue 03 (2012-07-30)
366
A Alarm Reference
2.
If a vacant slot is available, insert the board in the vacant slot, and then update the data on the NMS so that the board can work normally.
----End
Related Information
None.
A.3.56 COM_EXTECC_FULL
Description
The COM_EXTECC_FULL is an alarm indicating an excessive number of TCP connections between automatically extended ECC NEs.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameters 1 to 5 Meaning The value is always 0x00.

An excessive number of extended ECC NEs impacts NE performance.
Possible Causes
The number of TCP connections between automatically extended ECC NEs is larger than four.
Procedure
Step 1 Set ECC Extended Mode to Specified mode by referring to Configuring Extended ECC Communication. ----End
Related Information
None.
A Alarm Reference
A.3.57 CONFIG_NOSUPPORT
Description
The CONFIG_NOSUPPORT is an alarm indicating that the configuration is not supported. This alarm is reported if the ODU detects that the specified parameters do not meet the requirements of the ODU.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning 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.

When the CONFIG_NOSUPPORT alarm occurs, the ODU fails to work normally. If the equipment is configured with the 1+1 FD protection, the active ODU generates the CONFIG_NOSUPPORT alarm. In this case, the IF 1+1 protection switching may be triggered.
Possible Causes
l l Cause 1: The type and configuration parameters of the ODU do not match the requirements. 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 enabled on the radio link; the transmit power configured for the ODU is lower than the maximum rated power in AM guaranteed capacity mode.
Issue 03 (2012-07-30)
368
A Alarm Reference
Procedure
Step 1 Cause 1: The type and configuration parameters of the ODU do not match the requirements. 1. Determine the parameter that does not meet the requirement according to the alarm parameter. Then, handle the fault accordingly. If... Then...
The alarm parameter takes a value from Perform the operation described in Step 0x01 to 0x03 1.2. The alarm parameter takes a value from Perform the operation described in Step 0x04 to 0x06 1.3. 2. Check whether the parameters of the ODU interface meet the requirements of network planning. For details, see Configuring a Single-Hop Radio Link. If... The parameters meet the requirements of network planning The parameters do not meet the requirements of network planning 3. Then... Use the ODU of the proper model. Modify the ODU interface parameters.
Check whether the parameters of the IF interface meet the requirements of network planning. For details, see Configuring a Single-Hop Radio Link. If... Then...
The parameters meet the requirements of Replace the IF board. network planning The parameters do not meet the requirements of network planning Modify the IF interface parameters. For details, see Configuring a Single-Hop Radio Link.
Step 2 Cause 2: The AM parameters are incorrectly changed. (This cause can be verified only when Parameter 1 is 0x03.) 1. Verify that the alarm is caused by incorrect change of AM parameters. 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 transmit Perform a cold reset for the alarmed power needs to be changed ODU. The conditions are met but the transmit Change the parameters of ODU interfaces power does not need to be changed to recover the original value of transmit power. ----End
A Alarm Reference
Related Information
None.
A.3.58 DBMS_DELETE
Description
The DBMS_DELETE alarm indicates that a database is being deleted. This alarm is reported when a user runs a command to delete the database and the NE is in Deleting Database state.
Attribute
Alarm Severity Critical Alarm Type Equipment alarm
Parameters
None

All data is lost if an NE is powered off or a system control board is cold reset within 48 hours.
Possible Causes
l Cause 1: A database is deleted.
Procedure
Step 1 Follow instructions in 7.4 Restoring the Database by NMS to restore the database. ----End
Related Information
None
A.3.59 DBMS_ERROR
Description
The DBMS_ERROR is an alarm indicating that errors occur in the processing of the system database.
Attribute
Issue 03 (2012-07-30)
Alarm Type Processing alarm
370
A Alarm Reference
Parameters
None.

When the DBMS_ERROR alarm occurs, it indicates that errors occur in the system database processing. The system configuration may be lost. As a result, the failure indication is returned for certain query and setting commands, and certain system functions cannot work.
Possible Causes
l l Cause 1: The database processing fails or the database is damaged. 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. If... The alarm is cleared after the board is reset The alarm persists after the board is reset Step 2 Cause 2: A certain board is faulty. 1. 6.10 Replacing the System Control, Switch and Timing Board. Then... End the fault handling. Go to the next step.
----End
Related Information
None.
A.3.60 DBMS_PROTECT_MODE
Description
The DBMS_PROTECT_MODE is an alarm indicating that the system database is in protection mode.
Attribute
Alarm Severity Critical Alarm Type Processing alarm
Parameters
None.
A Alarm Reference

When this alarm occurs, it indicates that errors occur in the system database processing and the system configuration may be lost. As a result, the failure indication is returned for some query and 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.10 Replacing the System Control, Switch and Timing Board.
----End
Related Information
None.
A.3.61 DCNSIZE_OVER
Description
The DCNSIZE_OVER is an alarm indicating an over-sized DCN network.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1, Parameter 2 Meaning Indicate the size of the DCN network.

l l
Issue 03 (2012-07-30)
Some NEs become unreachable to the NMS because DCN packets cannot be forwarded timely due to insufficient CPU resources. The DCN network is prone to route flapping and storms.
A Alarm Reference
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
The DCNSIZE_OVER alarm occurs when the number of nodes (NEs, NMS servers, and NMS clients in a network segment) on an L2 DCN subnet is greater than 30. The solution is to divide the L2 DCN subnet. The DCNSIZE_OVER alarm occurs when the number of nodes (NEs, NMS servers, and NMS clients in a network segment) on an HWECC subnet is greater than 150. The solution is to divide the HWECC subnet.
A.3.62 DDN_LFA
Description
The DDN_LFA is an alarm indicating loss of basic frame alignment for framed E1 services. This alarm occurs when DDN (digital data network) side fails to receive the basic frame alignment signal for framed E1 services.
Attribute
Parameters
None.

E1 services on the alarmed board are unavailable.
Possible Causes
l l l
Issue 03 (2012-07-30)
Cause 1: The interconnected user equipment is faulty. Cause 2: The service frame format is configured incorrectly. Cause 3: The alarmed board has hardware faults.
A Alarm Reference
Procedure
Step 1 Cause 1: The interconnected user equipment is faulty. 1. 1. 1. 2. Troubleshoot the interconnected user equipment. Set the E1 frame format of the local port to the same as that of the opposite port. Check whether the alarmed board also reports any hardware alarms, such as HARD_BAD. If yes, perform a cold reset on the alarmed board and check whether the DDN_LFA alarm is cleared. Step 2 Cause 2: The service frame format is configured incorrectly. Step 3 Cause 3: The alarmed board has hardware faults.
CAUTION
If the service on the alarmed board is not protected, a cold reset on the board causes service interruptions. 3. If the alarm persists, replace the board.
----End
Related Information
Basic frame As defined in ITU-T G.704, a basic frame is an even frame with frame alignment sequence (FAS) or an odd frame with non frame alignment sequence (NFAS).
A.3.63 DOWN_E1_AIS
Description
The DOWN_E1_AIS is an alarm of the 2 Mbit/s downlink signal. This alarm occurs when the tributary board detects the 2 Mbit/s downlink signal of all 1s.
Attribute
Parameters
None.

When the DOWN_E1_AIS alarm occurs, the E1 signal in the alarmed path is unavailable.
A Alarm Reference
Possible Causes
l l Cause 1: The opposite NE transmits the E1_AIS alarm. 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_AIS Clear the alarm immediately. or T_ALOS alarm The opposite NE does not report the UP_E1_AIS or T_ALOS alarm Ensure that the board on the local NE is normal.
Step 2 Cause 2: On the local NE, the receive unit of the tributary board or the system control and crossconnect board is faulty. 1. Replace the board where the alarmed tributary unit is located. 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 system control and cross-connect board on the local 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 Parameter 1 Parameter 2, Parameter 3 Meaning 0x01, indicates optical interface number. Indicates the number of the path.
A.3.64 DROPRATIO_OVER
Description
The DROPRATIO_OVER alarm indicates that the number of lost packets crosses the threshold when queue congestion occurs at a port. This alarm is reported when the ratio of lost packets on an object under performance monitoring is higher than the expected ratio.
A Alarm Reference
Attribute
Parameters
Name Parameter 1 Meaning 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.
Possible Causes
l l Cause 1: Service configuration is incorrect. Cause 2: Actual traffic exceeds the configured port bandwidth or committed information rate (CIR).
Procedure
Step 1 Cause 1: Service configuration is incorrect. 1. 1. Check and reconfigure services according to the network plan. 8.20 Querying Traffic, Physical Bandwidth, or Bandwidth Utilization. If traffic is large, check whether a network storm has occurred, and eliminate the source that illegally sends a large amount of data. If the port bandwidth is too low, follow instructions in Modifying the Port Policy to increase port bandwidth or expand the network. Step 2 Cause 2: Actual traffic exceeds the configured port bandwidth or CIR.
2.
----End
Related Information
If packet loss is indicated in the receive direction, check the method of handling red packets in the 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.65 E1_LOC
Description
The E1_LOC is an alarm indicating that the uplink 2M clock is lost. This alarm occurs when the tributary board fails to extract the clock from the E1 signal.
A Alarm Reference
Attribute
Parameters
None.

When the E1_LOC occurs, the service is not affected.
Possible Causes
l l l l Cause 1: The opposite NE is faulty. Cause 2: The wiring sequence of the cable is incorrect. Cause 3: The receive unit of the tributary board on the local NE is faulty. 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... There is the external interference There is no external interference ----End Then... The fault is rectified. End the alarm handling. Contact Huawei engineers.
Related Information
None.
A.3.66 E1_LOS
A Alarm Reference
Description
The E1_LOS is an alarm indicating the loss of the E1 signal. This alarm occurs when the tributary board detects the uplink E1 signal of all 0s.
Attribute
Parameters
None.

When the E1_LOS alarm occurs, the E1 service is interrupted.
Possible Causes
l l l Cause 1: The cable is not connected or the cable is faulty. Cause 2: The opposite NE is faulty. 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... The cable is not connected properly The cable is prepared incorrectly Step 2 Cause 2: The opposite NE is faulty. 1. Rectify the fault on the opposite NE. Then... Connect the cable properly. 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.
Issue 03 (2012-07-30)
378
A Alarm Reference
A.3.67 ENVHUM_SENSOR_FAIL
Description
The ENVHUM_SENSOR_FAIL is an alarm indicating that the ambient humidity sensor of the cabinet fails.
Attribute
Parameters
None.

The ambient humidity data of the PMU cannot be collected.
Possible Causes
l l l l Cause 1: The ambient humidity sensor is faulty. Cause 2: The control board of the cabinet is faulty. Cause 3: Cables are misconnected or damaged. Cause 4: The ambient humidity sensor is not installed.
Procedure
Step 1 Cause 1: The ambient humidity sensor is faulty. 1. 2. Replace the ambient humidity sensor. Then, check whether the alarm clears. If... The alarm clears The alarm persists Then... End the alarm handling. Go to Cause 2.

A Alarm Reference
1. 2. 1.
Replace damaged cables. Connect cables correctly. Install the ambient humidity sensor.
Step 4 Cause 4: The ambient humidity sensor is not installed.
----End
Related Information
None.
A.3.68 ENVTEMP_SENSOR_FAIL
Description
The ENVTEMP_SENSOR_FAIL is an alarm indicating that the ambient temperature sensor of the cabinet fails.
Attribute
Parameters
None.

The ambient temperature data of the TCU cannot be collected.
Possible Causes
l l l l Cause 1: The ambient temperature sensor is faulty. Cause 2: The control board of the cabinet is faulty. Cause 3: Cables are misconnected or damaged. Cause 4: The ambient temperature sensor is not installed.
Procedure
Step 1 Cause 1: The ambient temperature sensor is faulty. 1. 2. Replace the ambient temperature sensor. Then, check whether the alarm clears. If... The alarm clears The alarm persists
Issue 03 (2012-07-30)

380
A Alarm Reference
Step 4 Cause 4: The ambient temperature sensor is not installed. 1. Install the ambient temperature sensor.
----End
Related Information
None.
A.3.69 ENVTEMP1_SENSOR_FAIL
Description
The ENVTEMP1_SENSOR_FAIL is an alarm indicating that ambient temperature sensor 1 of the cabinet fails.
Attribute
Parameters
None.

Ambient temperature data 1 of the PMU cannot be collected.
Possible Causes
l l l l
Issue 03 (2012-07-30)
Cause 1: Ambient temperature sensor 1 is faulty. Cause 2: The control board of the cabinet is faulty. Cause 3: Cables are misconnected or damaged. Cause 4: Ambient temperature sensor 1 is not installed.
A Alarm Reference
Procedure
Step 1 Cause 1: Ambient temperature sensor 1 is faulty. 1. 2. Replace ambient temperature sensor 1. Then, check whether the alarm clears. If... The alarm clears The alarm persists Then... End the alarm handling. Go to Cause 2.
Step 4 Cause 4: Ambient temperature sensor 1 is not installed. 1. Install ambient temperature sensor 1.
----End
Related Information
None.
A.3.70 ENVTEMP2_SENSOR_FAIL
Description
The ENVTEMP2_SENSOR_FAIL is an alarm indicating that ambient temperature sensor 2 of the cabinet fails.
Attribute
Parameters
None.
A Alarm Reference

Ambient temperature data 2 of the PMU cannot be collected.
Possible Causes
l l l l Cause 1: Ambient temperature sensor 2 is faulty. Cause 2: The control board of the cabinet is faulty. Cause 3: Cables are misconnected or damaged. Cause 4: Ambient temperature sensor 2 is not installed.
Procedure
Step 1 Cause 1: Ambient temperature sensor 2 is faulty. 1. 2. Replace ambient temperature sensor 2. Then, check whether the alarm clears. If... The alarm clears The alarm persists Then... End the alarm handling. Go to Cause 2.
Step 4 Cause 4: Ambient temperature sensor 2 is not installed. 1. Install ambient temperature sensor 2.
----End
Related Information
None.
A.3.71 ERPS_IN_PROTECTION
Description
ERPS_IN_PROTECTION indicates that EPRS ring is in protection mode.
A Alarm Reference
Attribute
Alarm Severity Minor Alarm Type Equipment Alarm
Parameters
Parameter 1 - Parameter 2 ERPS ID. Parameter 3 DIR, indicating whether the faulty node is in the east or west direction of the ERPS RPL-OWNER node. l 0x01: east l 0x00: west Parameter 4 - Parameter 9 NODE ID, indicating the MAC address of the faulty node.

At least one node on the ring is unreachable. Services (if any) on this node may be interrupted.
Possible Causes
Cause 1: This alarm is reported when EPRS switching is triggered by a fault on the ERPS ring.
Procedure
Step 1 Cause 1: This alarm is reported when EPRS switching is triggered by a fault on the ERPS ring. 1. 2. 3. Locate the faulty node on the ERPS ring based on the alarm parameters. Locate the ERPS blocked port on the faulty node. Rectify the fault.
----End
Related Information
None.
Issue 03 (2012-07-30)
384
A Alarm Reference
A.3.72 ETH_APS_LOST
Description
The ETH_APS_LOST is an alarm indicating that the APS frame is lost. This alarm occurs when no APS frame is received from the protection channel.
Attribute
Parameters
None.

When this alarm occurs, the APS protection may fail.
Possible Causes
l l l l Cause 1: The opposite NE is not configured with the APS protection. Cause 2: The APS protection group is deactivated. Cause 3: The settings of the APS protection group differ between the two ends. Cause 4: The service on the protection channel is interrupted.
Procedure
Step 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. For details, see Querying MPLS APS Status. If... The opposite NE is not configured with the APS protection The opposite NE is configured with the APS protection 2. 3. Then... Go to the next step. Go to Cause 2.
Create a matching APS protection group on the opposite NE, and activate the APS protocol. Check whether the alarm clears. 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... The APS protocol is deactivated at one end The APS protocol is activated at both ends
Issue 03 (2012-07-30)
Then... Activate the APS protocol at the end. Go to Cause 3.

385
A Alarm Reference
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. Check whether the alarm clears. If the alarm persists, go to Cause 4.
2.
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
Related Information
None.
A.3.73 ETH_APS_PATH_MISMATCH
Description
The ETH_APS_PATH_MISMATCH is an alarm indicating that the working and protection paths of the APS protection group differ between the two ends. This alarm is reported when the working and protection paths of one APS protection group at one end are different from those at the other end.
Attribute
Parameters
None.

When this alarm occurs, service protection fails.
Possible Causes
l l Cause 1: The configured working and protection paths differ between the two ends. Cause 2: The physical link is connected incorrectly.
Procedure
Step 1 Cause 1: The configured working and protection paths differ between the two ends.
A Alarm Reference
1. 2. 3.
Check whether the APS settings at the two ends are the same. For details, see Querying MPLS APS Status. If the APS settings are different, change the settings to the same. Then, deactivate and activate the APS protection group at the two ends. Then, check whether the alarm clears. 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.74 ETH_APS_SWITCH_FAIL
Description
The ETH_APS_SWITCH_FAIL is an alarm of a protection switching failure. This alarm is reported when the request signal in the transmitted Automatic Protection Switching (APS) frame is different from the bridge signal in the received APS frame and this symptom lasts for 50 ms.
Attribute
Parameters
None.

When this alarm occurs, service protection fails.
Possible Causes
Cause 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 Alarm Reference
Related Information
None.
A.3.75 ETH_APS_TYPE_MISMATCH
Description
The ETH_APS_TYPE_MISMATCH is an alarm of protection scheme mismatch. This alarm is reported when the information in the received Automatic Protection Switching (APS) frame is different from the APS settings at the local end.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning 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.

This alarm may cause the APS protection failure, and therefore the service protection fails.
Possible Causes
l l l Cause 1: The switching type is different. Cause 2: The switching direction is different. Cause 3: The revertive mode is different.
Procedure
Step 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 group at the two ends.
----End
A Alarm Reference
Related Information
None.
A.3.76 ETH_CFM_AIS
Description
The ETH_CFM_AIS is an alarm indicating that an AIS packet is received by the local MEP. This alarm is reported when the system receives an AIS packet, which indicates that the Ethernet server layer is faulty.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameters 1 to 4 (port) Meaning Indicate the ID of the port that reports the alarm.
Parameters 5 and 6 (VLAN ID) Indicate the VLAN ID of the MEP. Parameter 7 (direction) Indicate the direction of the local MEP. l 0x01: The port is in the ingress direction. l 0x02: The port is in the egress direction. Parameter 8 (level) Indicates the maintenance domain (MD) level of the local MEP. l 0x00: operator MEP level (low) l 0x01: operator MEP level (medium) l 0x02: operator MEP level (high) l 0x03: provider MEP level (low) l 0x04: provider MEP level (high) l 0x05: consumer MEP level (low) l 0x06: consumer MEP level (medium) l 0x07: consumer MEP level (high)
NOTE Consumer indicates the customer, provider indicates the supplier, and operator indicates the carrier.
Issue 03 (2012-07-30)
389
A Alarm Reference

l l When this alarm occurs, the loopback (LB) and link trace (LT) detection functions are disabled. In addition, the service between the relevant standard MEPs may be interrupted.
Possible Causes
Cause 1: The upstream NE on which AIS is activated detects a fault at the Ethernet server layer.
Procedure
Step 1 Troubleshoot the faulty Ethernet server layer. ----End
Related Information
None.
A.3.77 ETH_CFM_LOC
Description
The ETH_CFM_LOC is an alarm indicating the loss of connectivity. This alarm occurs when the system fails to receive the CCM packet from the remote MEP in 3.5 connectivity check (CC) periods successively.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1, Parameter 2, Parameter 3, Parameter 4 (Port) Parameter 5, Parameter 6 (VLAN ID) Parameter 7 (Direction) Meaning Indicates the ID of the alarmed port. Indicates the VLAN ID of the MEP. 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.
A Alarm Reference
Name Parameter 8 (Level)
Meaning Indicates the MD level of the local MEP. l 0x00: operator MEP level (low) l 0x01: operator MEP level (medium) l 0x02: operator MEP level (high) l 0x03: provider MEP level (low) l 0x04: provider MEP level (high) l 0x05: consumer MEP level (low) l 0x06: consumer MEP level (medium) l 0x07: consumer MEP level (high)
NOTE Consumer indicates the user, provider indicates the supplier, and operator indicates the carrier.
Parameter 9, Parameter 10 (RMEPID)
Indicates the ID of the remote MEP.

l l When the ETH_CFM_LOC alarm occurs, the LB and LT detection functions of Ethernet service OAM are unavailable. The service between the relevant standard MEPs may be interrupted.
Possible Causes
l l l Cause 1: The line between the local standard MEP and the remote standard MEP is interrupted. Cause 2: The Ethernet service in the maintenance association (MA) to which the local MEP belongs is faulty. 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. If... The physical links are connected improperly The physical links are connected properly Then... Connect the physical links properly. Go to Cause 2.
Step 2 Cause 2: The Ethernet service in the maintenance association (MA) to which the local MEP belongs is faulty. 1. Check whether Ethernet service in the maintenance association (MA) to which the local MEP belongs is configured correctly.
Issue 03 (2012-07-30)
391
A Alarm Reference
If...
Then...
The service is configured incorrectly Modify the configuration of the service to ensure consistency 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 Information
The Table A-7 describes the meanings of the parameters in the ETH_CFM_LOC alarm reported by the EoS/EoPDH plane. Table A-7 Alarm Parameters Name Parameter 1 to Parameter 4 Parameter 5 to Parameter 8 Parameter 9, Parameter 10 Parameter 11 to Parameter 14 Meaning MD MA MEP ID Indicates the ID of the alarmed port. When these parameters indicate the VCTRUNK ID, parameter values = (0x01 0x10) + 0x80. Indicates the VLAN ID of the MEP. 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 18 Indicates the MD level of the local MEP. l 0x00: operator MEP level (low) l 0x01: operator MEP level (medium) l 0x02: operator MEP level (high) l 0x03: provider MEP level (low) l 0x04: provider MEP level (high) l 0x05: consumer MEP level (low) l 0x06: consumer MEP level (medium) l 0x07: consumer MEP level (high)
Parameter 15, Parameter 16 Parameter 17
Issue 03 (2012-07-30)
392
A Alarm Reference
Meaning Indicates the ID of the remote MEP.

NOTE If the alarmed port is a VCTRUNK, these parameters are not supported.
A.3.78 ETH_CFM_MISMERGE
Description
The ETH_CFM_MISMERGE is an alarm indicating an incorrect connection. This alarm occurs when the system receives the CCM packet whose MA mismatches or whose priority is lower.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1, Parameter 2, Parameter 3, Parameter 4 (Port) Parameter 5, Parameter 6 (VLAN ID) Parameter 7 (Direction) Meaning Indicates the ID of the alarmed port. Indicates the VLAN ID of the MEP. 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.
Issue 03 (2012-07-30)
393
A Alarm Reference
Name Parameter 8 (Level)

When the ETH_CFM_MISMERGE alarm occurs, the service between the relevant standard MEPs may be interrupted, and the data flow may be routed incorrectly.
Possible Causes
l l l Cause 1: The names of the maintenance domain and the maintenance alliance that the standard MEPs correspond to are inconsistent. Cause 2: The levels of the maintenance domains that the standard MEPs correspond to are different. Cause 3: The physical connection is incorrect.
Procedure
Step 1 Cause 1: The names of the maintenance domain and the maintenance alliance that the standard MEPs 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 and maintenance 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 are different. 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.
A Alarm Reference
If...
Then...
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
Related Information
Issue 03 (2012-07-30)
395
A Alarm Reference
A.3.79 ETH_CFM_RDI
Description
The ETH_CFM_RDI is an alarm indicating the CCM packet with RDI received from the remote MEP. This alarm occurs when the system receives the CCM packet with RDI from the remote maintenance end point (MEP).
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1, Parameter 2, Parameter 3, Parameter 4 (Port) Parameter 5, Parameter 6 (VLAN ID) Parameter 7 (Direction) Meaning Indicates the ID of the alarmed port. Indicates the VLAN ID of the MEP. 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: operator MEP level (low) l 0x01: operator MEP level (medium) l 0x02: operator MEP level (high) l 0x03: provider MEP level (low) l 0x04: provider MEP level (high) l 0x05: consumer MEP level (low) l 0x06: consumer MEP level (medium) l 0x07: consumer MEP level (high)
Parameter 9, Parameter 10 (RMEPID)
Issue 03 (2012-07-30)
396
A Alarm Reference

l l When the ETH_CFM_RDI alarm occurs, the loopback (LB) and link trace (LT) detection functions of Ethernet service OAM are unavailable. The service between the relevant standard MEPs may be interrupted.
Possible Causes
l 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. 2. Determine the alarmed port according to the alarm parameter. 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
Related Information
The Table A-9 describes the meanings of the parameters in the ETH_CFM_LOC alarm reported by the EoS/EoPDH plane. Table A-9 Alarm Parameters Name Parameter 1 to Parameter 4 Parameter 5 to Parameter 8 Parameter 9, Parameter 10 Parameter 11 to Parameter 14 Meaning MD MA MEP ID Indicates the ID of the alarmed port. When these parameters indicate the VCTRUNK ID, parameter values = (0x01 0x10) + 0x80. Indicates the VLAN ID of the MEP. 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.
Issue 03 (2012-07-30)
397
A Alarm Reference
Name Parameter 18

NOTE If the alarmed port is a VCTRUNK, these parameters are not supported.
A.3.80 ETH_CFM_UNEXPERI
Description
The ETH_CFM_UNEXPERI is an alarm indicating the errored frame. This alarm occurs when the system receives invalid CCM packets.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1, Parameter 2, Parameter 3, Parameter 4 (Port) Parameter 5, Parameter 6 (VLAN ID)
Issue 03 (2012-07-30)
Meaning Indicates the ID of the alarmed port. Indicates the VLAN ID of the MEP.
398
A Alarm Reference
Name Parameter 7 (Direction)
Meaning 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: operator MEP level (low) l 0x01: operator MEP level (medium) l 0x02: operator MEP level (high) l 0x03: provider MEP level (low) l 0x04: provider MEP level (high) l 0x05: consumer MEP level (low) l 0x06: consumer MEP level (medium) l 0x07: consumer MEP level (high)

l l When the ETH_CFM_UNEXPERI alarm occurs, the LB and LT detection functions of Ethernet service OAM are unavailable. The service may become abnormal due to the loop.
Possible Causes
l l l Cause 1: No remote MEP is configured. 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. 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, the connectivity 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 both ends. The CC periods are the same Go to the next step. 2.
Issue 03 (2012-07-30)
Check whether the IDs of the MEPs in the maintenance domain are in conflict.
A Alarm Reference
If... The IDs are in conflict The IDs are not in conflict
Then... Change the conflicting IDs. 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 loop and clear the alarm.
----End
Related Information
Issue 03 (2012-07-30)
400
A Alarm Reference
A.3.81 ETH_EFM_DF
Description
The ETH_EFM_DF is an alarm indicating negotiation failure. This alarm occurs when the pointto-point OAM protocol negotiation fails at the Ethernet port.
Attribute
Parameters
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 Causes
l l l Cause 1: The physical port of the local end is faulty. Cause 2: The point to point OAM protocol is not enabled at the opposite end. Cause 3: The OAM configuration at both ends is inconsistent.
Procedure
Step 1 Cause 1: The physical port of the local end is faulty. 1. Check whether the physical port is faulty. If yes, replace the board where the Ethernet port is located.
Step 2 Cause 2: The point to point OAM protocol is not enabled at the opposite end. 1.
Issue 03 (2012-07-30)
Enable the point to point OAM protocol at the opposite end.

A Alarm Reference
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.82 ETH_EFM_EVENT
Description
The ETH_EFM_EVENT is an alarm indicating the performance event reported on the opposite NE. This alarm occurs when the local end receives the link error indication packet (OAMPDUM) from the opposite end.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning 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 Causes
l l
Issue 03 (2012-07-30)
Cause 1: The physical port at the local end is faulty. Cause 2: The equipment at the opposite end is faulty.
A Alarm Reference
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 Ethernet port 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.83 ETH_EFM_LOOPBACK
Description
The ETH_EFM_LOOPBACK is an alarm indicating the loopback. This alarm occurs when the local end initiates a loopback or responds to a loopback request from the opposite end.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the state of the loopback. l 0x01: The local end initiates a loopback. l 0x02: The local end responds to a loop request from the opposite end.

When the ETH_EFM_LOOPBACK alarm occurs, the service at the alarmed port is looped back.
Possible Causes
l l
Issue 03 (2012-07-30)
Cause 1: The local end initiates a loopback. Cause 2: The opposite end initiates a loopback.
A Alarm Reference
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 as soon as possible. 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 loopback as soon as possible.
Step 2 Cause 2: The opposite end initiates a loopback. 1.
----End
Related Information
None.
A.3.84 ETH_EFM_REMFAULT
Description
The ETH_EFM_REMFAULT is an alarm indicating the fault on the opposite NE. This alarm occurs when the local end receives the fault indication packet (OAMPDUM) from the opposite end.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning 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 be interrupted.
A Alarm Reference
Possible Causes
l l Cause 1: The opposite NE is reset. Cause 2: The opposite NE is faulty.
Procedure
Step 1 Cause 1: The opposite NE is reset. 1. Check whether the opposite NE is reset frequently. If... The opposite NE is reset frequently Then... Rectify the fault on the opposite NE.
The opposite NE is not reset frequently Reset the opposite NE, and the alarm is cleared. Step 2 Cause 2: The opposite NE is faulty. 1. Rectify the fault on the opposite NE.
----End
Related Information
None.
A.3.85 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 Causes
l l l
Issue 03 (2012-07-30)
Cause 1: The negotiation fails because the transmit port and receive port work in different modes. Cause 2: The cable or fiber is faulty. Cause 3: The local NE is faulty.
A Alarm Reference
Cause 4: The opposite 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. If... Then...
The transmit port and receive port work Correctly set the working modes of the in different modes transmit port and receive port. The transmit port and receive port work Go to Cause 2. in the same mode Step 2 Cause 2: The cable or fiber is faulty. 1. Check the network cable or fiber jumper connected to the alarmed port. If... The network cable is loose or damaged Then... Connect the network cable properly or replace the damaged network cable.
The connector of the fiber jumper is dirty Clean the connector. The connector or fiber is damaged The connection is normal Step 3 Cause 3: The local NE is faulty. 1. Check whether any fault occurs on the alarmed port. If... The equipment is faulty The equipment is normal Step 4 Cause 4: The opposite NE is faulty. 1. 2. Check whether any fault occurs on the equipment interconnected with the alarmed port. Rectify the fault. Then... Replace the alarmed board on the local. Go to Cause 4. Insert the connector properly or replace the damaged fiber jumper. Go to Cause 3.
----End
Related Information
None.
A.3.86 ETH_NO_FLOW
Description
The ETH_NO_FLOW is an alarm indicating that the Ethernet port has no flow. This alarm is reported when an enabled Ethernet port is in link up state but has no flow.
A Alarm Reference
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the MAC port number.
Parameter 2, Parameter 3 Indicate the path ID. Parameter 2 indicates the most significant bits and the value is always 0x00. Parameter 3 indicates the least significant bits and the value 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 Causes
l l l Cause 1: The port is enabled and in link up state, but is configured with no service. 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. 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.
Issue 03 (2012-07-30)
407
A Alarm Reference
If... No services are available in the transmit direction No services are available in the receive direction ----End
Then... Check whether the service is normal at the local end. Check whether the service is normal at the remote end.
Related Information
None.
A.3.87 ETH_PWR_SUPPLY_FAIL
Description
The ETH_PWR_SUPPLY_FAIL is an alarm indicating a power outputting failure of an Ethernet port. This alarm is reported when an Ethernet port is enabled with the PE function but outputs no power.
Attribute
Parameters
None.

When this alarm occurs, the NE that is connected to the Ethernet port outputs no power.
Possible Causes
l Cause: The board is faulty.
Procedure
Step 1 Cause: The board is faulty. 1. 6.7 Replacing the Ethernet Interface Board.
----End
Related Information
None.
A Alarm Reference
A.3.88 ETHOAM_DISCOVER_FAIL
Description
The ETHOAM_DISCOVER_FAIL alarm indicates a discovery failure when the point-to-point ETH-OAM function is enabled. This alarm occurs when the OAM function is enabled at a port of a board and the negotiation between the port and the opposite equipment fails.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning 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.
Possible Causes
l l l
Issue 03 (2012-07-30)
Cause 1: The physical port of the local end is faulty. Cause 2: The P2P OAM protocol is not enabled at the opposite end. Cause 3: The OAM configuration at both ends is inconsistent.
A Alarm Reference
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 OAM Auto-Discovery Function.
Step 3 Cause 3: The OAM configuration at both ends is inconsistent. 1. Reconfigure the P2P OAM protocol and ensure the consistency at both ends. For details, see Enabling the OAM Auto-Discovery Function.
----End
Related Information
None.
A.3.89 ETHOAM_RMT_CRIT_FAULT
Description
The ETHOAM_RMT_CRIT_FAULT is an alarm indicating that the point-to-point Ethernet OAM detects a critical fault at the remote end. This alarm occurs when a port with the OAM function enabled receives the OAM packets that contain critical fault information from the opposite end.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the ID of the alarmed port.
Parameter 2, Parameter 3 The values are always 0x00 0x01.
Issue 03 (2012-07-30)
410
A Alarm Reference
Name Parameter 4
Meaning 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 Causes
l l l Cause 1: A link fault occurs at the remote MEP. Cause 2: Irrecoverable problems such as power failure occur at the remote MEP. Cause 3: Other faults occur at the remote MEP.
Procedure
Step 1 Determine the fault type according to Parameter 4. If... The value of Parameter 4 is 0x01 The value of Parameter 4 is 0x02 Parameter 4 is a value from 0x03 to 0xff. Step 2 Cause 1: A link fault occurs at the remote MEP. 1. 1. Handle the ETH_LOS alarm at the remote port. Handle the problems such as power failure at the remote MEP, and recover the power supply to the remote MEP. Contact Huawei technical support engineers. Step 3 Cause 2: Irrecoverable problems such as power failure occur at the remote MEP. Then... Go to Cause 1. Go to Cause 2. Go to Cause 3.
Step 4 Cause 3: Other faults occur at the remote MEP. 1. ----End
Related Information
None.
A.3.90 ETHOAM_RMT_LOOP
Description
The ETHOAM_RMT_LOOP is an alarm indicating that a remote loopback is initiated when the point-to-point Ethernet OAM function is enabled. This alarm occurs when the local equipment
A Alarm Reference
initiates a remote loopback or responds to the remote loopback initiated by the opposite equipment.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Parameter 2, Parameter 3 Parameter 4 Meaning Indicates the ID of the alarmed port. The values are always 0x00 0x01. 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. The services and other protocol packets are interrupted.
Possible Causes
l l Cause 1: The local end issues a loopback command and the opposite end responds to the command. Cause 2: The opposite end issues a loopback command and the local end responds to the command.
Procedure
Step 1 Check the alarm on the NMS and determine the type of loopback according to the alarm parameters. If... The value of Parameter 4 is 0x01 The value of Parameter 4 is 0x02 Then... Go to Cause 1. Go to Cause 2.
Step 2 Cause 1: The local end issues a loopback command and the opposite end responds to the command. 1.
Issue 03 (2012-07-30)
Determine the causes of the loopback at the local end and release the loopback.
A Alarm Reference
Step 3 Cause 2: The opposite end issues a loopback command and the local end responds to the command. 1. Determine the causes of the loopback at the opposite end and release the loopback.
----End
Related Information
None.
A.3.91 ETHOAM_RMT_SD
Description
The ETHOAM_RMT_SD alarm indicates that the point-to-point Ethernet-OAM detects the degradation of remote Ethernet performance. This alarm occurs when a port with the OAM function enabled receives link event notification packets from the opposite end.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Parameter 2, Parameter 3 Parameter 4 Meaning Indicates the ID of the alarmed port. The values are always 0x00 0x01. Indicates the type of the received link event. l 0x01: errored frame event l 0x02: errored frame period event l 0x03: errored frame second event

When this alarm occurs, the performance of services degrades.
Possible Causes
l
Issue 03 (2012-07-30)
Cause 1: The link event notification function is enabled at the opposite end.
A Alarm Reference
l l
Cause 2: The link performance thresholds of the opposite end are inappropriate. 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... If yes If not Then... Disable the link event notification function at the opposite end. Go to Cause 2.
Step 2 Cause 2: The link performance thresholds of the opposite end are inappropriate. 1. Check whether the link performance thresholds of the opposite end are appropriate. If... If not If yes Then... Set the thresholds to appropriate values. Go to Cause 3.
Step 3 Cause 3: The link performance deteriorates. 1. Improve the link performance at the opposite end so that the opposite end does not send any link event notification packet to the local end. Then, the alarm at the local end is cleared automatically.
----End
Related Information
None.
A.3.92 ETHOAM_SELF_LOOP
Description
The ETHOAM_SELF_LOOP is an alarm indicating the loopback of the MAC port that runs the point-to-point OAM protocol. This alarm occurs when the MAC port of a board receives the OAM protocol packet sent by the port itself or the board after the loop detection function is enabled.
Attribute
Alarm Severity Major Alarm Type Environmental alarms
Parameters
A Alarm Reference
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the loopback type. l 0x01: selfloop of the port. l 0x02: selfloop of the board.

When the ETHOAM_SELF_LOOP alarm occurs, a network storm may occur due to the loopback.
Possible Causes
l l 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. 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 loopback accordingly. If... The value of Parameter 1 is 0x01 The value of Parameter 1 is 0x02 Then... Go to Cause 1. Go to Cause 2.
Step 2 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. If... The PHY/MAC loopback is manually configured at the port Then... Manually release the PHY/MAC loopback (or wait five minutes for the automatic release by the NE if the automatic loopback release function is enabled on the NE). Then, the selfloop is released. Connect the cable properly to release the selfloop. Release the loopback on the LAN, or break the connection between the port and the LAN, to release the selfloop.
The cable connected to the port is selflooped The port is connected to a LAN that has a loopback
Step 3 Cause 2: Two ports of the board are connected through cables or two ports of the board are connected 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.
Issue 03 (2012-07-30)
A Alarm Reference
If... The two ports are connected through cables
Then... Disconnect the cables to release the selfloop.
The two ports are connected to the same Break the connection between a port and the network LAN to release the selfloop. ----End
Related Information
None.
A.3.93 ETHOAM_VCG_SELF_LOOP
Description
The ETHOAM_VCG_SELF_LOOP alarm indicates that a VCTRUNK port is looped back when the point-to-point Ethernet OAM function is enabled. This alarm occurs when the loopback detection function is enabled and the VCTRUNK port receives the OAM protocol packets transmitted by the port itself or the board where the VCTRUNK port resides.
Attribute
Alarm Severity Major Alarm Type Environment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning 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.
A Alarm Reference
Possible Causes
l l Cause 1: A loopback occurs on the lines connected to one VCTRUNK. 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 alarm parameters. If... The value of Parameter 4 is 0x01 The value of Parameter 4 is 0x02 Step 2 Cause 1: The port is self-looped. 1. 2. Release the loopback at the port. Reconfigure the lines connected to the VCTRUNK port and ensure that the port is not selflooped. Then... Go to Cause 1. Go to Cause 2.
Step 3 Cause 2: The board is self-looped. 1. Reconfigure the lines connected to the VCTRUNK ports and ensure that the lines connected to any two VCTRUNK ports on the same board are not interconnected.
----End
Related Information
None.
A.3.94 EX_ETHOAM_CC_LOS
Description
The EX_ETHOAM_CC_LOS is an alarm indicating the loss of periodic connectivity check (CC) packets. This alarm occurs when the sink MEP fails to receive CC packets from the same source MEP in a period (3.5 transmission periods of CC packets at the source MEP).
Attribute
Parameters
A Alarm Reference
Name Parameter 1 to Parameter 4 Parameter 5 to Parameter 8 Parameter 9, Parameter 10
Meaning Indicates the ID of the remote MEP. Indicates the ID of the local MEP. Indicates the ID of the alarmed port. l PORT number, Parameter 9 is 0x00. l VCTRUNK number, Parameter 9 is 0x80.
Parameter 11, Parameter 12 Parameter 13 Parameter 14 to Parameter 17 Parameter 18 - Parameter 21
Indicates the VLAN ID of the MEP. Indicates the MD level of the local MEP. Indicates the ID of the remote MEP. Indicates the ID of the local MEP.

A unidirectional connectivity failure occurs in the Ethernet service between two MEPs.
Possible Causes
l l l Cause 1: The line between two MEPs is interrupted. Cause 2: The Ethernet services in the MA to which the alarmed MEP belongs are faulty. Cause 3: The services between two MEPs are congested or interrupted.
Procedure
Step 1 Cause 1: The line between two MEPs is interrupted. 1. Check whether the physical links (such as network cables or optical fibers) that carry services between the two MEPs are correctly connected. If... If not If yes Then... Re-connect the cables to rectify the faults on physical links. Go to Cause 2.
Step 2 Cause 2: The Ethernet services in the MA to which the alarmed MEP belongs are faulty. 1. Check whether the Ethernet services in the MA to which the alarmed MEP belongs are configured correctly. If... If not If yes Then... Modify the configuration to ensure consistency at both ends. Go to Cause 3.
Step 3 Cause 3: The services between two MEPs are congested or interrupted.
A Alarm Reference
1.
Check the bandwidth utilization. If the bandwidth is exhausted, increase the bandwidth or eliminate any source that transmits a large amount of invalid data.
----End
Related Information
None.
A.3.95 EX_ETHOAM_MPID_CNFLCT
Description
The EX_ETHOAM_MPID_CNFLCT is an alarm indicating the conflict of MPIDs. This alarm occurs when two MEPs in one MD have the same maintenance point identity (MPID) and one MEP receives the packets from the other MEP.
Attribute
Alarm Severity Major Alarm Type Environment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 to Parameter 4 Parameter 5, Parameter 6 Meaning Indicates the ID of the local MEP. Indicates the ID of the alarmed port. l PORT number, Parameter 9 is 0x00. l VCTRUNK number, Parameter 9 is 0x80. Parameter 7, Parameter 8 Parameter 9 Parameter 10 to Parameter 13 Indicates the VLAN ID of the MEP. Indicates the MD level of the local MEP. Indicates the ID of the local MEP.

MPIDs must be unique on a network. When this alarm occurs, the LB and LT functions are abnormal and OAM packets are received incorrectly.
A Alarm Reference
Possible Causes
Cause 1: At least two MEPs in an MD have the same MPID.
Procedure
Step 1 Cause 1: At least two MEPs in an MD have the same MPID. 1. 2. Check the alarm on the NMS and determine the associated MP ID according to the alarm parameters. Query the information about the MEP. Delete the incorrect MEPs and create MEPs with unique MP IDs.
----End
Related Information
None.
A.3.96 EXT_SYNC_LOS
Description
The EXT_SYNC_LOS is an alarm of the loss of the external clock source.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning l 0x01: the first external clock source l 0x02: the second external clock source

l 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 clock source after the external clock source is lost and enters the free-run state 24 hours later. The system saves 24-hour holdover data. The system works in 24-hour holdover mode instead of permanent holdover mode. If another valid clock source of higher priority and good quality is configured in the clock source priority list, however, the clock protection switching occurs.
Issue 03 (2012-07-30)
A Alarm Reference
Possible Causes
Cause 1: The external clock source is configured in the clock source priority list, but the external clock source cannot be detected or become invalid.
Procedure
Step 1 Cause 1: The external clock source is configured in the clock source priority list, but the external clock source cannot be detected or become invalid. 1. Check whether the equipment that provides the external clock source is faulty. If... The equipment is faulty The equipment is normal 2. Then... Rectify the fault. Go to the next step.
Check whether the cable that connects the external clock source is normal. If... The cable is abnormal The cable is normal Then... Replace the cable. Replace the alarmed board.
----End
Related Information
None.
A.3.97 EXT_TIME_LOC
Description
The EXT_TIME_LOC is an alarm of the loss of the external time source.
Attribute
Parameters
Issue 03 (2012-07-30)
421
A Alarm Reference
Name
Meaning
Parameter 1 l 0x01: link failure on a port l 0x02: unchanged second value in time of day (TOD) information, or unavailable second pulse, or degraded second pulse l 0x03: CRC errors in TOD information

The time of a local NE cannot be synchronized to the external time device to which the NE's enabled external time port is connected.
Possible Causes
l l Cause 1: The link at a port is faulty. Cause 2: The external time device is faulty.
Procedure
Step 1 Cause 1: The link at a port is faulty. 1. 1. Check cable connections. If cables are incorrectly connected, connect the cables again. Check whether the external time device is faulty. Step 2 Cause 2: The external time device is faulty.
----End
Related Information
None.
A.3.98 FAN_AGING
Description
The FAN_AGING is an alarm of the aged fan. This alarm occurs when the fan rotates at a speed lower than eighty percent of the nominal speed.
Attribute
Parameters
A Alarm Reference
Name Parameter 1
Meaning Indicates the number of the alarmed fan.

When this alarm occurs, the temperature of the NE is too high and impacts the long-term operation 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.99 FAN_FAIL
Description
The FAN_FAIL is an alarm indicating that the fan is faulty.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the number of the fan.

When the FAN_FAIL alarm occurs, the heat dissipation of the system is affected.
A Alarm Reference
After an alarm is reported, clear it immediately. Otherwise, services may be interrupted or equipment may be damaged. When a fan is faulty, perform the following operations: l l Replace the faulty fan with one that works properly within a period of 96 hours if the ambient temperature ranges from 0C to 40C . Replace the faulty fan with one that works properly within a period of 24 hours if the ambient temperature is higher than 40C .
When multiple fans are faulty, replace them immediately.
Possible Causes
l l Cause 1: The board and the backplane are connected improperly. 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... The alarm is cleared after the board is removed and inserted The alarm persists after the board is removed and inserted Step 2 Cause 2: Fan failure occurs. 1. Replace the alarmed fan board. Then... The fault is rectified. End the alarm handling. Go to Cause 2.
----End
Related Information
None.
A.3.100 FCS_ERR
Description
The FCS_ERR is an alarm indicating the errors of frame check sequence (FCS). This alarm occurs when a board detects FCS errors in the received frames.
Attribute
Issue 03 (2012-07-30)
424
A Alarm Reference
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Parameter 2, Parameter 3 Meaning The value is always 0x01. Indicate the VCTRUNK number where the alarm occurs.

When the FCS_ERR alarm occurs, if the encapsulation protocols or encapsulation parameters are inconsistent at both ends of Ethernet services, the services may have errors and even become interrupted.
Possible Causes
l l l Cause 1: The encapsulation protocols or encapsulation parameters are inconsistent at both ends of services. Cause 2: Service channels have errors. Cause 3: The alarmed board is faulty.
Procedure
Step 1 Cause 1: The encapsulation protocols or encapsulation parameters are inconsistent at both ends of services. 1. Check whether the encapsulation protocols or encapsulation parameters are consistent at both ends of services. If... The protocols are inconsistent The protocols are consistent 2. Then... Correct the configuration data. Go to the next step.
Check whether the encapsulation parameters are consistent at both ends of services. If... The parameters are inconsistent The parameters are consistent Then... Correct the configuration data. 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 board that carries the services.
Issue 03 (2012-07-30)
425
A Alarm Reference
If... Yes No
Then... Handle the alarm or performance event. 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.101 FLOW_OVER
Description
The FLOW_OVER is an alarm indicating that the data flow received exceeds the threshold.
Attribute
Parameters
Parameter 1 Indicates the receive or transmit direction in which traffic crosses the specified threshold. l 0x00: the receive direction l 0x01: the transmit direction

When the FLOW_OVER alarm occurs, the extra data may be discarded .
Possible Causes
l l
Issue 03 (2012-07-30)
Cause 1: The traffic threshold is very low. Cause 2: The opposite end transmits excessive data flow.
A Alarm Reference
Procedure
Step 1 Cause 1: The traffic threshold is very low. 1. Increase the traffic threshold to a value that is lower than the rate of the local threshold.
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
Related Information
None.
A.3.102 HARD_BAD
Description
The HARD_BAD is an alarm indicating hardware errors.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 to Parameter 3 Meaning Indicate the internal faults detected by the board.

The alarmed board fails to work. If the board is configured with the 1+1 protection, protection switching may be triggered.
Possible Causes
l l l
Issue 03 (2012-07-30)
Cause 1: The board and the backplane are connected improperly. Cause 2: A certain board is faulty. Cause 3: The slot is faulty.
A Alarm Reference
Procedure
Step 1 Cause 1: The 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... The alarm is cleared after the board is removed and inserted The alarm persists after the board is removed and inserted 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... The alarm is cleared after the board is replaced The alarm persists after the board is replaced Step 3 Cause 3: The slot is faulty. 1. Contact Huawei engineers to handle the faulty slot.
TIP
Then... The fault is rectified. End the alarm handling. Check for the faults in boards.
Then... The fault is rectified. End the alarm handling. Check for the faults in slots.
Generally, the slot becomes faulty due to the broken pin or bent pin. Remove the board, and use a torch 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
Related Information
None.
A.3.103 HARD_NONSUPPORT
Description
The HARD_NONSUPPORT is an alarm indicating that a certain function is not supported by a board. A function is configured on the device and a command is issued by the system to enable the function on a board. If the board hardware does not support this function, this alarm is reported.
Issue 03 (2012-07-30)
428
A Alarm Reference
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates functions that are not supported by a board. l 0x01: ETH PWE3 control word l 0x02: 2.5 Gbit/s bus rate

The function is unavailable if this alarm is reported.
Possible Causes
Cause: The board does not support the function even though it is configured on the device.
Procedure
Step 1 Replace the board with a new one that supports the function. ----End
Related Information
None.
A.3.104 HP_CROSSTR
Description
The 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 path error crosses the preset threshold.
Issue 03 (2012-07-30)
429
A Alarm Reference
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the performance monitoring period: l 0x01: 15 minutes l 0x02: 24 hours Parameter 2, Parameter 3 Indicate the ID of a performance event that causes the alarm. l 0x30: HPBBE l 0x31: HPES l 0x32: HPSES l 0x33: HPFEBBE l 0x34: HPFEES l 0x35: HPFESES l 0x36: HPUAS l 0x37: HPCSES l 0x38: HPFECSES l 0x4c: HPFEUAS

When the HP_CROSSTR alarm occurs, a large number of errors occur in the service, and the service may be interrupted.
Possible Causes
Cause 1: The higher order path error crosses the preset threshold.
Procedure
Step 1 Cause 1: The higher order path error crosses the preset threshold. 1. Check the threshold crossing records to find out the performance event that the higher order path error crosses the preset threshold. For details, see 8.3.12 Browsing the Performance Event Threshold-Crossing Records.
Issue 03 (2012-07-30)
A Alarm Reference
2.
Handle the threshold-crossing performance event.
----End
Related Information
None.
A.3.105 HP_LOM
Description
The HP_LOM is an alarm indicating the loss of the higher order path multiframe. This alarm occurs when the board detects that byte H4 is inconsistent with the expected multiframe sequence.
Attribute
Parameters
None.

When the HP_LOM alarm occurs, the service on the alarmed path is interrupted. If the services are configured with protection, protection switching may be triggered.
Possible Causes
l l Cause 1: The transmit unit of the opposite NE is faulty. 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. 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 system control, cross-connect, and timing board on the opposite NE.
Step 2 Cause 2: The receive unit of the local NE is faulty. 1. Replace the alarmed board. ----End
A Alarm Reference
Related Information
None.
A.3.106 HP_RDI
Description
The HP_RDI is an alarm indicating the higher order path remote receive failure. This alarm occurs when the board detects that bit 5 of byte G1 is 1.
Attribute
Parameters
None.

When the HP_RDI alarm occurs, the service on the local NE is not affected. The service received by the opposite NE, however, is interrupted.
Possible Causes
Cause 1: The local NE detects the message that is returned by the opposite NE and indicates the higher 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 the higher order path remote receive failure. 1. Clear the alarms such as HP_LOM and B3_EXC that the AU-4 path reports on the opposite NE.
----End
Related Information
None.
A.3.107 HP_REI
Description
The HP_REI is an alarm indicating the higher order path remote error. This alarm occurs when the board detects that bits 1-4 of G1 take a value from 1 to 8.
A Alarm Reference
Attribute
Alarm Severity Warning Alarm Type 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 the higher order path remote errors.
Procedure
Step 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. 1. Handle the HP_BBE performance event that the AU-4 path reports on the opposite NE.
----End
Related Information
None.
A.3.108 HP_SLM
Description
The HP_SLM is an alarm indicating the lower order path label mismatch. This alarm occurs when the board detects the C2 byte mismatch.
Attribute
Parameters
None.
A Alarm Reference

None.
Possible Causes
l l Cause 1: The C2 byte received by the local NE does not match with the C2 byte transmitted by the remote NE. 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 by the remote NE. 1. Configure the same service type at the source and sink of the AU-4 path. For details, see Configuring Overhead Bytes.
Step 2 Cause 2: Configuration data is incorrect. 1. If the 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 CrossConnections of SNCP Services.
----End
Related Information
None.
A.3.109 HP_TIM
Description
The HP_TIM is an alarm indicating the higher order path trace identifier mismatch. This alarm occurs when the board detects the J1 byte mismatch.
Attribute
Parameters
None.

If the service is configured with the protection that considers the HP_TIM alarm as a trigger condition, the protection switching is triggered.
A Alarm Reference
Possible Causes
l l Cause 1: The receivable J1 byte on the local NE does not match with the J1 byte transmitted on the opposite NE. 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 on the 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 Configuring VC-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 CrossConnections of SNCP Services or Creating the Cross-Connections of Point-to-Point Services. If... Then...
The alarm is cleared after the configuration The fault is rectified. End the alarm is changed handling. The alarm persists after the configuration is changed 2. Go to the next step.
Check whether the cross-connections are configured correctly at the intermediate nodes where the service travels. If not, reconfigure the cross-connections. For details, see Creating Cross-Connections of SNCP Services or Creating the Cross-Connections of Point-to-Point Services.
----End
Related Information
None.
A.3.110 HP_UNEQ
Description
The HP_UNEQ is an alarm indicating the unequipped higher order path. This alarm occurs when the board detects that the C2 byte is 0.
Attribute
Issue 03 (2012-07-30)
435
A Alarm Reference
Parameters
None.

When the HP_UNEQ alarm occurs, the service in the alarmed AU-4 path is unavailable. If the service is configured with the protection that considers the alarm as a trigger condition, the protection switching is triggered.
Possible Causes
l l 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. 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 line port at the opposite NE is not configured with services. 1. Configure line services on the opposite NE. For details, see Creating Cross-Connections of SNCP Services or Creating the Cross-Connections of Point-to-Point Services. Change the setting of byte C2. For details, see Configuring VC-4 POHs.
Step 2 Cause 2: Byte C2 is set to 0 at the opposite NE. 1. ----End
Related Information
None.
A.3.111 HPAD_CROSSTR
Description
The HPAD_CROSSTR is an alarm indicating that the higher order path adaptation performance crosses the threshold. This alarm occurs when a board detects that the performance event of TU pointer justification crosses the preset threshold.
Attribute
Parameters
A Alarm Reference
Name Parameter 1
Meaning Indicates the performance monitoring period: l 0x01: 15 minutes l 0x02: 24 hours
Indicate the ID of a performance event that causes the alarm. l 0xaa: TUPJCHIGH l 0xab: TUPJCLOW l 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.12 Browsing the Performance Event Threshold-Crossing Records. Handle the threshold-crossing performance event.
2.
----End
Related Information
None.
A.3.112 IF_CABLE_OPEN
Description
The IF_CABLE_OPEN is an alarm indicating that the IF cable is open.
Attribute
Parameters
None.
A Alarm Reference

When the IF_CABLE_OPEN alarm occurs, the service on the alarmed IF port is interrupted.
Possible Causes
l l l Cause 1: The IF cable is loose or faulty. Cause 2: The IF port on the IF board is damaged. Cause 3: The power module of the ODU is faulty.
NOTE
When rectifying the faults of the IF cable, IF port, and ODU, you must turn off the ODU before the operation. You can turn on the ODU only after the operation is complete.
Procedure
Step 1 Cause 1: The IF cable is loose or faulty. 1. Check whether the connector of the IF cable is loose or whether the connector is made properly. The connectors to be checked include the connector between the IF fiber jumper and the IF board, the connector between the IF fiber jumper and the IF cable, and the connector between the IF cable and the ODU. If... The connector is loose Then... Connect the connector tightly.
The connector is made improperly See the Installation Reference and make new connectors for the IF cable. None of the above 2. Go to the next step.
Check whether the surface of the IF fiber jumper and the IF cable is damaged. If... The cable does not meet the requirement The cable meets the requirement Then... Replace the cable with a qualified one. Go to Cause 2 or Cause 3.
Step 2 Cause 2: The IF port on the IF board is damaged. 1. 1. Replace the alarmed IF board. Replace the ODU connected to the alarmed IF port. Step 3 Cause 3: The power module of the ODU is faulty.
----End
Related Information
None.
A.3.113 IF_INPWR_ABN
A Alarm Reference
Description
The IF_INPWR_ABN is an alarm indicating that the power supplied by an IF board to an ODU is abnormal.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning 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.

When 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 Causes
l l l l Cause 1: The IF board is faulty. Cause 2: The IF cable is faulty. Cause 3: The ODU is faulty. 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 the IF board, the connector between the IF fiber jumper and the IF cable, and the connector between the IF cable and the ODU. If... Any of the connectors is loose
Issue 03 (2012-07-30)
Then... Connect the connector tightly.

439
A Alarm Reference
If... Any of the connectors is prepared incorrectly All connectors are normal
Then... See the Installation Reference and make new connectors for the IF cable. Go to the next step.
2.
Check whether the surface of the IF fiber jumper and the IF cable is damaged or deformed, and test the connectivity between the IF fiber jumper and the IF cable. For details, see Testing the Connectivity of the IF Cable. If... The IF cable is below standard The IF cable is up to standard Then... Replace the IF cable. The IF board or ODU may be faulty.
Step 3 Cause 3: The ODU is faulty. 1. 1. Replace the alarmed ODU. Connect the IF fiber jumper and the IF board correctly. Step 4 Cause 4: The IF fiber jumper and the IF board are connected incorrectly.
----End
Related Information
The logical slot ID of the ODU is obtained by adding 20 to the slot ID of the IF board connected to the ODU.
A.3.114 IF_MODE_UNSUPPORTED
Description
The IF_MODE_UNSUPPORTED is an alarm indicating that the configured IF working mode is not supported. This alarm occurs if the board is not loaded with the FPGA file that supports the configured IF working mode.
Attribute
Parameters
A Alarm Reference
Name Parameter 1
Meaning 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 is interrupted.
Possible Causes
Cause 1: The board is not loaded with the FPGA file that supports the configured IF working mode, or the FPGA file that supports the configured IF working mode is damaged.
Procedure
l Cause 1: The board is not loaded with the FPGA file that supports the configured IF working mode, or the FPGA file that supports the configured IF working mode is damaged. 1. ----End Contact Huawei engineers to upgrade the software and the FPGA file.
Related Information
None.
A.3.115 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 the activated 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.
A Alarm Reference
Possible Causes
l l Cause 1: The IMA links on the local NE are faulty. Cause 2: The activated links of the IMA group on the local NE are less than the minimum number.
Procedure
Step 1 Cause 1: The IMA links on the local NE are faulty. 1. 2. Check whether the T_ALOS alarm is reported at the E1 port. If yes, clear this alarm. 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 local NE.
When the number of activated links of the IMA group reaches the minimum number, the alarm clears automatically. ----End
Related Information
None.
A.3.116 IMA_GROUP_RE_DOWN
Description
The IMA_GROUP_RE_DOWN is an alarm indicating that the IMA group at the remote end fails. This alarm occurs when the IMA group is in non-Active state on the remote NE or when the 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.
A Alarm Reference
Possible Causes
l l Cause 1: The IMA links on the remote NE are faulty. Cause 2: The activated links of the IMA group on the remote NE are less than the minimum number.
Procedure
Step 1 Cause 1: The IMA links on the remote NE are faulty. 1. 2. Check whether the T_ALOS alarm is reported at the E1 port. If yes, clear this alarm. 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 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 opposite NE. No other alarm occurs Reconfigure the links of the IMA group on the remote NE.
When the number of activated links of the IMA group reaches the minimum number, the alarm clears automatically. ----End
Related Information
None.
A.3.117 IMA_TXCLK_MISMATCH
Description
The IMA_TXCLK_MISMATCH is an alarm indicating that the transmit clock modes of an IMA group are inconsistent at the two ends.
Attribute
Parameters
None.
A Alarm Reference

The IMA_TXCLK_MISMATCH alarm may cause loss of ATM cells.
Possible Causes
Cause 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. 2. Check the alarm information and determine the NE, board, and ATM trunk related to the alarm. 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 Information
The Clock Mode parameter can be set to two modes. l l CTC mode: Common transmit clock mode. In CTC mode, all transmit clocks of the links in an IMA group are from the same clock source. ITC mode: Independent transmit clock mode. In ITC mode, the transmit clocks of the links in an IMA group are from different clock sources. When the IMA group is set to the line clock mode, the ITC mode is recommended.
A.3.118 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 errors and even becomes unavailable.
Possible Causes
l
Issue 03 (2012-07-30)
Cause 1: The transmit power of the opposite NE is over high or over low.
A Alarm Reference
l l l
Cause 2: The model of the selected optical module is incorrect. Cause 3: The optical module at the receive end is faulty. 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 transmit optical power on the opposite NE. If... Then...
The transmit optical power does not meet Replace the optical module. the requirement The transmit optical power is over high Add a proper attenuator to reduce the receive 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... The models are incorrect The models are correct Then... Replace the optical module. 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 optical module.
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 the damaged fiber jumper.
----End
Related Information
The following table describes the meanings of the parameters in the IN_PWR_ABN alarm reported by the EMS6. Name Parameter 1 Meaning Indicates the port number.
Issue 03 (2012-07-30)
445
A Alarm Reference
Meaning The value of Parameter 2 is always 0x00, and the value of Parameter 3 is always 0x01. The two parameters indicate the path ID. Reserved. The values are always 0xFF.
A.3.119 IN_PWR_HIGH
Description
The IN_PWR_HIGH is an alarm indicating that the input optical power is over high.
Attribute
Parameters
None.

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

A Alarm Reference
1.
Query the board manufacturing information report, and check whether the models of the SFP optical modules used at both ends are correct. If... The models are incorrect The models are correct Then... Contact Huawei engineers to replace the optical module. 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 optical module.
----End
Related Information
The optical power threshold set for the IN_PWR_HIGH alarm is lower than the overload point. SDH Interface Performance.
A.3.120 IN_PWR_LOW
Description
The IN_PWR_LOW is an alarm indicating that the input optical power is over low.
Attribute
Parameters
None.

When the IN_PWR_LOW alarm occurs, the service at the alarmed optical interface has errors.
Possible Causes
l l l l Cause 1: The transmit power of the opposite NE is over low. Cause 2: The model of the selected optical module is incorrect. Cause 3: The optical module at the receive end is faulty. Cause 4: The fiber performance degrades.
Procedure
Step 1 Cause 1: The transmit power of the opposite NE is over low.
A Alarm Reference
1.
Browse current performance events, and query the performance event of the transmit optical power on the opposite NE. If... Then...
The transmit optical power does not meet Contact Huawei engineers to replace the the requirement optical module. The transmit optical power meets the requirement 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... The models are incorrect The models are correct Then... Contact Huawei engineers to replace the optical module. 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... The receive optical power meets the requirement Then... Contact Huawei engineers to replace the optical module.
The receive optical power does not meet the Go to Cause 4. requirement Step 4 Cause 4: The fiber performance degrades. 1. If... The alarm is cleared after the connector is cleaned The alarm persists after the connector is cleaned ----End Clean fiber connectors and adapters. Then... The fault is rectified. End the alarm handling. Replace the fiber.
Related Information
The optical power threshold set for the IN_PWR_LOW alarm is higher than the sensitivity point. SDH Interface Performance.
Issue 03 (2012-07-30)
448
A Alarm Reference
A.3.121 INTEMP_SENSOR_FAIL
Description
The INTEMP_SENSOR_FAILL is an alarm indicating that the air inlet temperature sensor of the cabinet fails.
Attribute
Parameters
None.

The air inlet temperature data of the TCU cannot be collected.
Possible Causes
l l l l Cause 1: The air inlet temperature sensor is faulty. Cause 2: The control board of the cabinet is faulty. Cause 3: Cables are misconnected or damaged. Cause 4: The air inlet temperature sensor is not installed.
Procedure
Step 1 Cause 1: The air inlet temperature sensor is faulty. 1. 2. Replace the air inlet temperature sensor. Then, check whether the alarm clears. If... The alarm clears The alarm persists Then... End the alarm handling. Go to Cause 2.

A Alarm Reference
1. 2.
Replace damaged cables. Connect cables correctly.
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.122 J0_MM
Description
The J0_MM is an alarm indicating the trace identifier mismatch. This alarm occurs when the board detects the J0 byte mismatch.
Attribute
Parameters
None.

None.
Possible Causes
Cause 1: The receivable J0 byte on the local NE does not match the transmitted J0 byte on the opposite NE.
Procedure
Step 1 Cause 1: The receivable J0 byte on the local NE does not match the transmitted J0 byte on the opposite NE. 1. Disable the receivable J0 byte on the local NE. For details, see Configuring RSOHs.
----End
Related Information
None.
A Alarm Reference
A.3.123 K1_K2_M
Description
The K1_K2_M is an alarm indicating the K1/K2 byte mismatch. This alarm occurs when the board detects inconsistent channel numbers that the transmitted K1 byte (bits 5-8) and the received K2 byte (bits 1-4) indicate.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Meaning l 0x01: linear MS protection. l 0x02: ring MS protection. Parameter 2 Indicates the ID of the alarmed protection group. For example, 0x01 indicates that the alarm is reported by protection group 1.
Parameter 1 Indicates the protection group type.

When the K1_K2_M alarm occurs, the MSP protocol may fail and therefore the protection switching may fail.
Possible Causes
l l l Cause 1: The switching modes configured at both ends are single-ended switching and dualended switching separately. Cause 2: The fiber connection is incorrect. Cause 3: A certain board is faulty.
Procedure
Step 1 Cause 1: The switching modes configured at both ends are single-ended switching and dualended switching separately. 1.
Issue 03 (2012-07-30)
Check whether the switching modes at both ends are the same.
A Alarm Reference
If... The switching modes are different The switching modes are the same Step 2 Cause 2: The fiber connection is incorrect. 1.
Then... Configure the switching modes as the same. Go to Cause 2.
Check whether the fiber connection is correct. For example, the fiber at the receive or transmit port may be incorrectly connected, or disconnected. If... The fiber connection is incorrect The connection is correct Then... Connect the fiber properly. Go to Cause 3.
Step 3 Cause 3: 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... The alarm is cleared The alarm persists ----End Then... The fault is rectified. End the alarm handling. Replace the alarmed board.
Related Information
None.
A.3.124 K2_M
Description
The K2_M is an alarm indicating the K2 byte mismatch. This alarm occurs when the board detects that the protection mode indicated by the received K2 (bit 5) is different from the protection mode of the NE.
Attribute
Parameters
A Alarm Reference
Name
Meaning l 0x01: linear MS protection. l 0x02: ring MS protection.
Parameter 1 Indicates the protection group type.
Parameter 2 Indicates the ID of the alarmed protection group. For example, 0x01 indicates that the alarm is reported by protection group 1.

When the K2_M alarm occurs, the MSP protocol may fail and therefore the protection switching may fail.
Possible Causes
l l l l Cause 1: Two NEs of the linear MSP group are configured with different protection modes (1+1 or 1:N). Cause 2: The MSP protocol is stopped when the protection switching occurs. Cause 3: The fiber connection is incorrect. Cause 4: A certain board is faulty.
Procedure
Step 1 Cause 1: Two NEs of the linear MSP group are configured with different protection modes (1 +1 or 1:N). 1. Query the status of the linear MSP, and check whether two NEs of the linear MSP group are configured with different protection modes (1+1 or 1:N). If... The protection modes are different The protection modes are the same Then... Configure the protection modes as 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, see Starting/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... The connection is incorrect
Issue 03 (2012-07-30)
Then... Connect the fiber properly

453
A Alarm Reference
If... The connection is correct 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... The alarm is cleared The alarm persists Then... The fault is rectified. End the alarm handling. Replace the alarmed board.
----End
Related Information
None.
A.3.125 LAG_BWMM
Description
LAG_BWMM is an alarm indicating the bandwidth inconsistency in the LAG group.
Attribute
Parameters
None.

For a LAG group in load-sharing mode, data services may be lost.
Possible Causes
Cause 1: In the LAG group, the license capacities of the ports differ from each other.
Procedure
Step 1 Cause 1: In the LAG group, the license capacities of the ports differ from each other. 1. 2. Query the license capacities of the ports of the LAG group by using the NMS. If the license capacities of the ports differ from each other, reload a license file of an appropriate capacity.
----End
A Alarm Reference
Related Information
None.
A.3.126 LAG_DOWN
Description
The 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
Parameters
None.

When the LAG_DOWN alarm occurs, the service at the member port of the LAG is interrupted.
Possible Causes
Cause 1: All the member ports of the aggregation group are invalid for the same causes as the LAG_MEMBER_DOWN alarm.
Procedure
Step 1 Cause 1: All the member ports of the LAG are invalid for the same causes as the LAG_MEMBER_DOWN alarm. 1. 2. Determine the alarmed port according to the alarm parameter. Rectify the fault at each member port according to the description of LAG_MEMBER_DOWN.
----End
Related Information
None.
A.3.127 LAG_MEMBER_DOWN
Description
The LAG_MEMBER_DOWN is an alarm indicating that a member port of a link aggregation group (LAG) is unavailable. This alarm occurs when a member port of an LAG can neither be activated nor function as a protection port.
A Alarm Reference
Attribute
Parameters
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 4, Parameter 5 Indicates the ID of the alarmed port. 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.

The port in the LAG cannot share the service load, and the port does not transmit or receive any services.
Possible Causes
l l l l Cause 1: The port link is faulty or disabled. Cause 2: The port receives no LACP packets. Cause 3: The port works in half-duplex mode or not in Auto-Negotiation mode. 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... The value of Parameter 4 is 0x01 The value of Parameter 4 is 0x02 The value of Parameter 4 is 0x03 The value of Parameter 4 is 0x04
Issue 03 (2012-07-30)
Then... Perform the operations described in step Step 2. Perform the operations described in step Step 3. Perform the operations described in step Step 4. Perform the operations described in step Step 5.
456
A Alarm Reference
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... The port is not enabled The port is enabled 2. Then... Enable the port in the LAG. Go to the next step.
Check the link status of all ports and check whether the ETH_LOS alarm is reported. If... The alarm is reported Then... Clear the ETH_LOS alarm immediately and rectify the fault 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. On the NMS, change the working mode of the port into full-duplex and Auto-Negotiation.
2.
Step 5 Cause 4: The port is self-looped. 1. Check whether the port is self-looped. For details, see 8.18 Querying the Attributes of an Ethernet Port. If the port is self-looped, release the selfloop. For details, see 8.7.5 Setting a Loopback for the Packet-plane Ethernet Interface Board.
----End
Related Information
None.
A.3.128 LAG_PORT_FAIL
Description
The LAG_PORT_FAIL is an alarm indicating that a port in the LAG fails. When a port in the LAG is unavailable, the LAG_PORT_FAIL alarm is reported.
Attribute
Issue 03 (2012-07-30)
457
A Alarm Reference
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Parameter 2, Parameter 3 Parameter 4 Meaning Indicates the number of the IP port. The values are always 0x00 0x01. 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.

Possible Causes
l l l l l Cause 1: The port is disabled or the link is faulty. Cause 2: The port is in the half-duplex mode. Cause 3: The port fails to receive the LCAP packets. Cause 4: The port detects a selfloop. 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... The value of Parameter 4 is 0x01 The value of Parameter 4 is 0x02 The value of Parameter 4 is 0x03 The value of Parameter 4 is 0x04 The value of Parameter 4 is 0x05
Then... Go to Cause 1. Go to Cause 2. Go to Cause 3. Go to Cause 4. Go to Cause 5.

458
A Alarm Reference
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 the Basic 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, rectify the fault.
Step 3 Cause 2: The port is in the half-duplex mode. 1. On the NMS, check the working mode of the port in the LAG group. If the port is in halfduplex mode, change the working mode of the port into full-duplex. For details, see Setting the Basic Attributes of Ethernet Ports. 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... The LAG group is not properly configured The LAG group is properly configured 2. Then... Reconfigure the LAG group. Go to the next step.
Step 4 Cause 3: The port fails to receive the LCAP packets. 1.
Check whether the local port and the remote port transmit the LACP packets. If the LACP packets are not transmitted, configure the ports at both ends to ensure that the packets can be normally transmitted. For details, see Querying the Protocol Information of the LAG. Release the selfloop of the port with reference to Enabling Self-Loop Detection. Contact Huawei engineers.
Step 5 Cause 4: The port detects a selfloop. 1. 1. Step 6 Cause 5: other unknown reasons
----End
Related Information
None.
A.3.129 LAG_VC_PORT_FAIL
Description
The LAG_VC_PORT_FAIL is an alarm indicating that a VCG port in the LAG fails. When the VCTRUNK is unavailable, the alarm is reported.
Attribute
Issue 03 (2012-07-30)
459
A Alarm Reference
Parameters
Parameter 2, Parameter 3 Indicate the number of the faulty VCG port in the LAG. Parameter 2 indicates the most significant bits and Parameter 3 indicates the least significant bits. 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. Parameter 5 The value is always 0xff.

Possible Causes
l l l l Cause 1: The link of the port is faulty or fails. Cause 2: The port fails to receive the LCAP packets. Cause 3: The port detects a selfloop. 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... The value of Parameter 4 is 0x01 The value of Parameter 4 is 0x03 The value of Parameter 4 is 0x04 The value of Parameter 4 is 0x05 Step 2 Cause 1: The port is disabled or the link is faulty. 1.
Issue 03 (2012-07-30)
Then... Go to Cause 1. Go to Cause 2. Go to Cause 3. Go to Cause 4.
Check the link state of each VCG port. If any link is faulty, rectify the fault.
A Alarm Reference
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... The LAG group is not properly configured The LAG group is properly configured 2. Then... Reconfigure the LAG group. Go to the next step.
Check whether the local port and the remote port transmit the LACP packets. If the LACP packets are not transmitted, configure the ports at both ends to ensure that the packets can be normally transmitted.
Step 4 Cause 3: The port detects a selfloop. 1. Release the selfloop of the port.
Step 5 Cause 4: other unknown reasons 1. Contact Huawei engineers.
----End
Related Information
None.
A.3.130 LAN_LOC
Description
The LAN_LOC is an alarm indicating the Ethernet communication failure.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the network port ID. For example, 0x01 indicates network port 1 and 0x02 indicates network port 2.
Issue 03 (2012-07-30)
461
A Alarm Reference
Name
Meaning
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 is always 0x00. Parameter 3 indicates the least significant bits and the value is always 0x01.

When 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 Causes
l l l Cause 1: The cable is not connected to the network port, or the cable is faulty. Cause 2: The network port is faulty. 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 parameter 1. 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.10 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.10 Replacing the System Control, Switch and Timing Board.
----End
Related Information
None.
A.3.131 LASER_CLOSED
Description
The LASER_CLOSED is an alarm indicating that the laser is shut down. This alarm occurs when the laser is shut down by using the NMS.
A Alarm Reference
Attribute
Parameters
None.

When the LASER_CLOSED alarm occurs, the optical interface fails to carry services.
Possible Causes
Cause 1: The laser on the local NE is shut down by using the NMS.
Procedure
Step 1 Cause 1: The laser on the local NE is shut down by using the NMS. 1. Find out the cause of shutting down the laser and start up the laser as soon as possible.
----End
Related Information
None.
A.3.132 LASER_MOD_ERR
Description
The LASER_MOD_ERR is an alarm indicating that the type of the pluggable optical module on the board does not match the type of the optical interface.
Attribute
Parameters
None.

When the LASER_MOD_ERR alarm occurs, the performance of the optical interface degrades and serious degradation even causes service interruption.
A Alarm Reference
Possible Causes
l l l l Cause 1: The optical module installed at the optical interface does not match the rate of the optical interface. Cause 2: The small form-factor pluggable (SFP) module does not match the interface type. Cause 3: The optical module is faulty. 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 the optical interface. 1. Check whether the optical module installed at the optical interface matches the rate of the optical interface. For details, see 8.6.2 Querying the Board Manufacturing Information Report . If... The optical module does not match the rate of the optical interface The optical module matches the rate of the optical interface Then... Contact Huawei engineers to replace the optical module with one that matches the rate of the 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... The alarm is cleared after the optical module is replaced The alarm persists after the optical module is replaced Step 4 Cause 4: A certain board is faulty. 1. Replace the alarmed board. Then... End the alarm handling. Go to Cause 3.
----End
Related Information
None.
A.3.133 LASER_MOD_ERR_EX
Description
The LASER_MOD_ERR is an alarm indicating that the type of the pluggable optical module on the board does not match the type of the optical interface.
A Alarm Reference
Attribute
Parameters
None.

When the LASER_MOD_ERR_EX alarm occurs, the performance of the optical interface degrades and serious degradation even causes service interruption.
Possible Causes
l l l l Cause 1: The optical module installed at the optical interface does not match the rate of the optical interface. Cause 2: The small form-factor pluggable (SFP) module does not match the interface type. Cause 3: The optical module is faulty. 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 the optical interface. 1. Check whether the optical module installed at the optical interface matches the rate of the optical interface. For details, see 8.6.2 Querying the Board Manufacturing Information Report . If... The optical module does not match the rate of the optical interface The optical module matches the rate of the optical interface Then... Contact Huawei engineers to replace the optical module with one that matches the rate of the 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. If.. Then...
The port type is incorrectly set See Configuring an SFP Port.to rectify the port type setting The SFP type is incorrect Step 3 Cause 3: The optical module is faulty. 1.
Issue 03 (2012-07-30)
Replace it with an SFP module of the correct type.
Replace the faulty optical module.

A Alarm Reference
If... The alarm is cleared after the optical module is replaced The alarm persists after the optical module is replaced Step 4 Cause 4: A certain board is faulty. 1. Replace the alarmed board.
----End
Related Information
None.
A.3.134 LASER_SHUT
Description
The LASER_SHUT is an alarm indicating that the laser is shut down. This alarm occurs when the laser is shut down by using the NMS.
Attribute
Parameters
None.

When the laser_shut alarm occurs, the optical interface fails to carry services.
Possible Causes
Cause 1: The laser on the local NE is shut down by using the NMS.
Procedure
Step 1 Cause 1: The laser on the local NE is shut down by using the NMS. 1. Find out the cause of shutting down the laser and start up the laser as soon as possible.
----End
Related Information
None.
A Alarm Reference
A.3.135 LCAS_FOPR
Description
The 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 state in which the LCAS might fail to negotiate or cannot negotiate correctly.
Attribute
Parameters

The Ethernet service is not normal.
Possible Causes
l l Cause 1: Configuration data of the LCAS protocol is incorrect. 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... The settings of the LCAS protocols are not consistent The settings of the LCAS protocols at both ends are consistent
Issue 03 (2012-07-30)
Then... Properly enable the LCAS protocols at both ends. Go to Cause 2.
467
A Alarm Reference
2.
Check whether configurations of the local and opposite NEs are correct. For example, check whether a VCG on one NE is connected to multiple VCGs on the opposite NE. If... Then...
The configurations of the local and opposite NEs are Correct the configuration data. incorrect The configurations of the local and opposite NEs are Go to Cause 2. correct Step 2 Cause 2: The link is faulty. 1. Check whether the link where the service travels has errors or becomes faulty. If... The link is faulty The link is normal 2. Then... Rectify the fault. Go to the next step.
Restart the LCAS protocols at both ends. Then, check whether the alarm clears. If... The alarm clears The alarm persists Then... End the alarm handling. Replace the alarmed board.
----End
Related Information
None.
A.3.136 LCAS_FOPT
Description
The LCAS_FOPT is an alarm indicating that the LCAS protocol in the transmit direction fails. This alarm occurs if the transmit unit of the LCAS module of a board detects an abnormal state in which the LCAS might fail to negotiate or cannot negotiate correctly.
Attribute
Parameters
A Alarm Reference
Name Parameter 1
Meaning The value is always 0x01.

The Ethernet service is not normal.
Possible Causes
l l Cause 1: Configuration data of the LCAS protocol is incorrect. 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... The settings of the LCAS protocols are not consistent Then... Properly enable the LCAS protocols at both ends.
The settings of the LCAS protocol at both Go to Cause 2. ends are consistent 2. Check whether configurations of the local and opposite NEs are correct. For example, check whether a VCG on one NE is connected to multiple VCGs on the opposite NE. If... Then...
The configurations of the local and opposite NEs are Correct the configuration data. incorrect The configurations of the local and opposite NEs are Go to Cause 2. correct Step 2 Cause 2: The link is faulty. 1. Check whether the link where the service travels has errors or becomes faulty. If... The link is faulty The link is normal 2. Then... Rectify the fault. Go to the next step.
Restart the LCAS protocols at both ends. Then, check whether the alarm clears. If... The alarm clears Then... End the alarm handling.
469
Issue 03 (2012-07-30)
A Alarm Reference
If... The alarm persists ----End
Then... Replace the alarmed board.
Related Information
None.
A.3.137 LCAS_PLCR
Description
The LCAS_PLCR is an alarm indicating that a part of the LCAS bandwidth in the receive direction is lost. This alarm occurs when a board detects that the number of paths that carry the overloads in the receive direction of the VCTRUNK with the LCAS function enabled is less than the preset number but is not zero.
Attribute
Parameters

The available Ethernet service bandwidth is smaller than the configured bandwidth.
Possible Causes
l l l
Issue 03 (2012-07-30)
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. Cause 2: Some paths in the transmit direction of the remote site are faulty. Cause 3: Some paths in the receive direction of the local site are faulty.
A Alarm Reference
Procedure
Step 1 Cause 1: The number of paths or timeslots that are configured for the VCTRUNK at the remote site is different from that at the local site. 1. Check whether the VCTRUNKs at 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 are Correct the configuration data. For details, bound with different number of physical see Dynamically Increasing/Decreasing the paths or bound with different timeslots VCTRUNK Bandwidth. If yes Go to Cause 2.
Step 2 Cause 2: Some paths in the transmit direction of the remote site are faulty. 1. Check whether any path alarm exists in the transmit direction of the remote site. If... Any of the preceding alarms occurs No alarm occurs Then... Clear the alarm immediately. Go to Cause 3.
Step 3 Cause 3: Some paths in the receive direction of the local site are faulty. 1. Replace the alarmed board. ----End
Related Information
None.
A.3.138 LCAS_PLCT
Description
The LCAS_PLCT is an alarm indicating that part of the LCAS bandwidth in the transmit direction is lost. This alarm occurs when a board detects that the number of paths that carry the overloads in the transmit direction of the VCTRUNK with the LCAS function enabled is less than the preset number but is not zero.
Attribute
Parameters
A Alarm Reference
Name Parameter 1
Meaning The value is always 0x01.
Parameter 2, Parameter 3 Indicate the ID of the alarmed VCTRUNK. For example, 0x00 0x01 indicate that the alarm is reported in VCTRUN 1.

The available transmit bandwidth of Ethernet services is less than the preset bandwidth. When the transmitted services are more than the available transmit bandwidth, packet loss occurs.
Possible Causes
l l l Cause 1: The number of paths or timeslots that are configured for the VCTRUNK at the remote site is different from that at the local site. Cause 2: Some paths in the receive direction of the remote site are faulty. Cause 3: Some paths in the transmit direction of the local site are faulty.
Procedure
Step 1 Cause 1: The number of paths or timeslots that are configured for the VCTRUNK at the remote site is different from that at the local site. 1. Check whether the sink and source VCTRUNKs are bound with the same number of physical paths or the same timeslots. If... Then...
The sink and source VCTRUNKs are Correct the configuration data. For details, bound with different number of physical see Dynamically Increasing/Decreasing the paths or different timeslots VCTRUNK Bandwidth. The sink and source VCTRUNKs are Go to Cause 2. bound with the same number of physical paths or the same timeslots Step 2 Cause 2: Some paths in the receive direction of the remote site are faulty. 1. Check whether any path alarm exists in the receive direction of the remote site. If... Any of the preceding alarms occurs No alarm occurs Then... Clear the alarm immediately. Go to the next step.
Step 3 Cause 3: Some paths in the transmit direction of the local site are faulty. 1. Replace the alarmed board. ----End
Related Information
None.
A Alarm Reference
A.3.139 LCAS_TLCR
Description
The LCAS_TLCR is an alarm indicating that all the LCAS bandwidth in the receive direction is lost. This alarm occurs when no path in the receive direction of the VCTRUNK with LCAS enabled carries the overload but paths are configured to carry the overload.
Attribute
Parameters
Parameter 2, Parameter 3 Indicates the ID of the alarmed VCTRUNK. For example, 0x00 0x01 indicate that the alarm is reported in VCTRUN 1.

There is no available bandwidth in the receive direction, and the Ethernet services are interrupted.
Possible Causes
l l l Cause 1: No VCTRUNK is bound to the remote port. Cause 2: Paths in the transmit direction of the remote site are faulty. Cause 3: Paths in the receive direction of the local site are faulty.
Procedure
Step 1 Cause 1: No VCTRUNK is bound to the remote port. 1. Check whether VCTRUNKs have been added in the receive direction at the local end and in the transmit direction at the remote end. If... VCTRUNKs has been added, Then... Correct the configuration data. For details, see Configuring VCTRUNKs on an Ethernet Board.
No VCTRUNK has been added, Go to Cause 2.

A Alarm Reference
Step 2 Cause 2: Paths in the transmit direction of the remote site are faulty. 1. Check whether any path alarm exists in the transmit direction of the remote site. If... Any of the preceding alarms occurs No alarm occurs Then... Clear the alarm immediately. Go to Cause 3.
Step 3 Cause 3: Paths in the receive direction of the local site are faulty. 1. Replace the alarmed board.
----End
Related Information
None.
A.3.140 LCAS_TLCT
Description
The LCAS_TLCT is an alarm indicating that all the LCAS bandwidth in the transmit direction is lost. This alarm occurs when no path in the transmit direction of the VCTRUNK with LCAS enabled carries the overload but paths are configured to carry the overload.
Attribute
Parameters

There is no available bandwidth in the transmit direction, and the Ethernet services are interrupted.
A Alarm Reference
Possible Causes
l l l Cause 1: No VCTRUNK is bound to the remote port. Cause 2: Paths in the receive direction of the remote site are faulty. Cause 3: Paths in the transmit direction of the local site are faulty.
Procedure
Step 1 Cause 1: No VCTRUNK is bound to the remote port. 1. Check whether VCTRUNKs have been added in the receive direction at the local end and in the transmit direction at the remote end. If... VCTRUNKs has been added, Then... Correct the configuration data. For details, see Configuring VCTRUNKs on an Ethernet Board.
No VCTRUNK has been added, Go to Cause 2. Step 2 Cause 2: 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... Any of the preceding alarms occurs No alarm occurs Then... Clear the alarm immediately. Go to the next step.
Step 3 Cause 3: Paths in the transmit direction of the local site are faulty. 1. Replace the alarmed board.
----End
Related Information
None.
A.3.141 LCD
Description
The LCD is an alarm indicating loss of cell delimitation. This alarm occurs when the OCD alarm continuously occurs within the transmission period of N cells. The letter "N" indicates the LCD alarm threshold value. For different ports, the threshold value is different.
Attribute
Issue 03 (2012-07-30)
475
A Alarm Reference
Parameters
None.

l 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 the downstream.
Possible Causes
l l l 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. 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. 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. For example, the MS_AIS, AU_AIS or AU_LOP alarm occurs. 1. 2. Check whether the MS_AIS, AU_AIS, or AU_LOP alarm occurs in the path connected to the ATM port. 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 alarms indicating excessive bit errors, such as B1_EXC, B2_EXC, and B3_EXC. 1. 2. 1. 2. Check whether the B1_EXC, B2_EXC, or B3_EXC alarm occurs in the receive path. If yes, clear these alarms first, and then check whether the LCD alarm is cleared. Perform a cold reset on the board that reports the LCD alarm. For details, see 8.8.1 Cold Reset. If the LCD alarm persists, replace the alarmed board. For details, see 6.6 Replacing the Smart E1 Interface Board.
Step 3 Cause 3: The ATM processing chip of the board is faulty.
----End
Related Information
End 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. Thresholds of generating the LCD alarm at different ports l l l For the external ATM port, the threshold of generating the LCD alarm is seven cells. For a VC-4 VCTRUNK port, the threshold of generating the LCD alarm is 360 cells. 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,
Issue 03 (2012-07-30)
A Alarm Reference
the LCD alarm is reported when the ALM_IMA_LINK_LCD alarm occurs. If the VCTRUNK is bound with multiple E1 links in the IMA group, and if the number of E1 links in which the ALM_IMA_LINK_LCD alarm occurs is greater than the value derived from the total number of bound E1 links subtracted by the minimum number of activated links in the receive direction of the IMA group, the LCD alarm is reported at the VCTRUNK port. Otherwise, the LCD alarm is not reported.
A.3.142 LCS_LIMITED
Description
The LCS_LIMITED alarm indicates that the configuration capacity of an NE exceeds the capacity authorized by the license file.
Attribute
Parameters
Issue 03 (2012-07-30)
477
A Alarm Reference
Name
Meaning
Parameter 1 Indicates the alarm cause. l 0x01: The service capacity exceeds the capacity authorized by the license file. l 0x02: The AM license file is not loaded. l 0x03: 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 the license file. l 0x04: The 1588v2 capacity exceeds the capacity authorized by the license file. l 0x05: The ATM/IMA capacity exceeds the capacity authorized by the license file. l 0x06: The air port LAG capacity exceeds the capacity authorized by the license file. l 0x07: The E1 priority capacity exceeds the capacity authorized by the license file. l 0x08: The synchronous Ethernet capacity exceeds the capacity authorized by the license file. l 0x09: The air port compression capacity exceeds the capacity authorized by the license file l 0x0a: The MPLS service license capacity exceeds the capacity authorized by the license file. l 0x0b: The PLA license capacity exceeds the capacity authorized by the license file. l 0x0c: The total service bandwidth (TDM service bandwidth and data service bandwidth) exceeds the bandwidth allowed by the Ethernet license file for the working and protection links. l 0x0d: The GE port capacity exceeds the capacity authorized by the license file. l 0x0e: No XPIC license is available. l 0x0f: No ERPS license is available. l 0x10: The number of configured VC-12 cross connections exceeds the number authorized by the license file. l 0x11: The number of ports configured high modulation exceeds the number authorized by the license file.

When the LCS_LIMITED alarm occurs, the change of radio service capacity cannot take effect on the NE.
Possible Causes
l Cause 1: The AM configuration on the NE exceeds the capacity authorized by the license file.
Issue 03 (2012-07-30)
478
A Alarm Reference
l l
Cause 2: 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 the license file. Cause 3: The services configured on the NE exceed the capacity authorized by the license file.
Procedure
Step 1 Query the capacity of the license by using the NMS. 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 the AM function to disabled.
Step 3 Cause 2: 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 the license file. 1. Check whether the capacities that are authorized by the license files for the main and standby IF boards in an IF protection group are consistent with the capacities specified in the contract. If not, contact Huawei technical support engineers to reload correct license files. when the alarm parameter is 0x01, check whether the radio service configuration exceeds the capacity authorized by the license file. For details, see Configuring a Single-Hop Radio Link. If yes, reduce the number of E1 services. Purchase and load the corresponding service license.
Step 4 Cause 3: The services configured on the NE exceed the capacity authorized by the license file. 1.
2.
----End
Related Information
For TDM services, radio service capacities of NEs are calculated based on the service crossconnections on IF boards.
A.3.143 LFA
Description
The LFA is an alarm indicating that the E1 frame alignment at the local end of the inverse multiplexing for ATM (IMA) link in the receive direction is lost.
Attribute
Parameters
A Alarm Reference
Name Parameter 1
Meaning Indicates the ID of the optical interface. The value is always 0x01.
Parameter 2, Parameter 3 Indicates the path ID.

l l l When this alarm occurs, the alarmed E1 link is unavailable, and the available links in the IMA group are reduced. If the VCTRUNK link binds only one member, the service is interrupted when the LFA alarm occurs. After this alarm clears, the E1 link in the IMA group will be recovered automatically.
Possible Causes
The possible causes of the LFA alarm are as follows: l Cause 1: The demultiplexing module of the E1 frame cannot perform the frame alignment function, and therefore the frame alignment loss alarms are reported. These alarms include TU_LOP, TU_AIS, and alarm indicating that the cross-connection is not configured. Cause 2: The alarmed board is faulty.
Procedure
Step 1 Cause 1: Check for the TU_LOP and TU_AIS alarms on the NMS. If these alarms occur, handle these alarms first. Step 2 Cause 2: The alarmed board is faulty. 1. 2. Check whether the HARD_BAD alarm occurs on the board. If the alarm occurs, perform a cold reset on the board that reports the hardware failure alarm, and check whether the alarm clears.
CAUTION
If the service on the board is not protected, a cold reset on the board causes service interruptions. 3. If the alarm persists, replace the board. For details, see 6.7 Replacing the Ethernet Interface Board or 6.6 Replacing the Smart E1 Interface Board.
----End
Related Information
Basic frame As defined in ITU-T G.704, a basic frame is an even frame with frame alignment sequence (FAS) or an odd frame with non frame alignment sequence (NFAS).
A Alarm Reference
A.3.144 LICENSE_LOST
Description
The LICENSE_LOST is an alarm indicating that the NE fails to detect the license file.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the type of the license file. l 0x01: AM license l 0x02: Hybrid license l 0x03: TDM license l 0x04: 1588V2 license l 0x05: ATM/IMA license l 0x06: NE license

When the LICENSE_LOST alarm occurs, the functions authorized by the license file cannot take effect.
Possible Causes
Cause 1: The license file is lost or is not loaded.
Procedure
Step 1 Cause 1: The license file is lost or is not loaded. 1. Contact Huawei engineers to reload the license file to the NE.
----End
Related Information
None.
A Alarm Reference
A.3.145 LINK_ERR
Description
The LINK_ERR alarm indicates that a data link is faulty.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the ID of the optical port. For example, 0x01 indicates that the alarm is reported by optical port 1.
Parameter 2, Parameter 3 Indicate the ID of the path that reports the alarm. For example, 0x00 0x01 indicate that the alarm is reported by path 1.

Services in the alarmed path are interrupted.
Possible Causes
l l l Cause 1: The optical fiber connected to the Ethernet optical port is faulty. Cause 2: The working modes of the ports at the local and opposite ends are different. 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... The optical fiber is faulty The optical fiber is not faulty Then... Replace the fiber. Go to Cause 2.
Step 2 Cause 2: The working modes of the ports at the local and opposite ends are different. 1.
Issue 03 (2012-07-30)
Check whether the working modes of the ports at the local and opposite ends are different.
A Alarm Reference
If... The working modes of the ports at the local and opposite ends are different The working modes of the ports at the local and opposite ends are the same
Then... Set the working modes of the ports to the same. Go to the next step.
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... The alarm is cleared The alarm persists ----End Then... Replace the Ethernet board at the opposite end. Replace the Ethernet board at the local end.
Related Information
None.
A.3.146 LMFA
Description
The LMFA is an alarm indicating the E1 multiframe alignment is lost when the E1 frame is a CRC-4 multiframe.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the ID of the optical interface. The value is always 0x01.
Parameter 2, Parameter 3 Indicates the path ID.

When this alarm occurs, the alarmed E1 links become unavailable. As a result, fewer links of the IMA group are available. If the IMA group is comprised of only one link, services will be interrupted.
A Alarm Reference
Possible Causes
The possible cause of the LMFA alarm is as follows: l l Cause 1: The alarmed board is faulty. Cause 2: The frame format is incorrect.
Procedure
Step 1 Cause 1: The alarmed board is faulty. 1. 2. Check whether the HARD_BAD alarm occurs on the board. If the alarm occurs, perform a cold reset on the board that reports the hardware failure alarm, and check whether the alarm clears.
CAUTION
If the service on the board is not protected, a cold reset on the board causes service interruptions. 3. 1. 2. If the alarm persists, replace the board. Check the frame format of the opposite port. For details, see Setting Advanced Attributes of Smart E1 Ports. Set the frame format to CRC-4 Multiframe if it is incorrect.
Step 2 Cause 2: The frame format is incorrect.
----End
Related Information
Basic frame As defined in ITU-T G.704, a basic frame is an even frame with frame alignment sequence (FAS) or an odd frame with non frame alignment sequence (NFAS). Multiframe A multiframe is composed of sixteen PCM frames, and can implement cyclic redundancy check (CRC).
A.3.147 LOOP_ALM
Description
The LOOP_ALM is an alarm indicating that a loop occurs.
Attribute
Issue 03 (2012-07-30)
484
A Alarm Reference
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning 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.
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.
A Alarm Reference
1. 2.
Determine the type of loopback according to the alarm parameter. Find out the cause of the loopback, and set the loopback status of the alarmed port to NonLoopback. For details, see 8.7 Software Loopback.
----End
Related Information
This table provides parameters and their meanings for LOOP_ALM alarms reported by ports 1 to 7 on an EMS6 board. Name Parameter 1 Parameter 2, Parameter 3 Parameter 4 Meaning Indicates the optical port ID. The parameter takes a fixed value of 0x01. Indicate the path ID (the value 1 indicates that the optical port is looped back). Indicates loopback types. l 0x00: inloops at optical/electrical ports l 0x01: outloops at optical/electrical ports l 0x02: inloops at paths l 0x03: outloops at paths l 0x04: loopbacks on the client side l 0x05: loopbacks on the combination wave side l 0x08: inloops at the ATM layer l 0x09: outloops at the ATM layer l 0x0A: inloops at the PHY layer l 0x0B: outloops at the PHY layer l 0x0C: inloops at the MAC layer l 0x0D: outloops at the MAC layer l 0x0E: inloops at VC-4 timeslots l 0x0F: outloops at VC-4 timeslots l 0x10: inloops at VC-3 timeslots l 0x11: outloops at VC-3 timeslots l 0x12: inloops at VC-12 timeslots l 0x13: outloops at VC-12 timeslots l 0x14: outloops at IF ports l 0x15: inloops at IF ports l 0x16: inloops at RF ports l 0xFF: any of the preceding loopback modes
Issue 03 (2012-07-30)
486
A Alarm Reference
This table provides parameters and their meanings for LOOP_ALM alarms reported by ports VC-3 channels on an EMS6 board. Name Parameter 1 Parameter 2, Parameter 3 Meaning Indicates the optical port ID. The parameter takes a fixed value of 0x01. Indicates the VC-3 channel ID.
A.3.148 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 path error crosses the preset threshold.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the performance monitoring period: l 0x01: 15 minutes l 0x02: 24 hours
Issue 03 (2012-07-30)
487
A Alarm Reference
Meaning Indicate the ID of a performance event that causes the alarm. l 0x90: LPBBE l 0x91: LPES l 0x92: LPSES l 0x93: LPFEBBE l 0x94: LPFEES l 0x95: LPFESES l 0x96: LPUAS l 0x8e: LPFEUAS l 0x97: LPCSES l 0x98: LPFECSES

When the LP_CROSSTR alarm occurs, a large number of errors occur in the service, and the service 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. 2. Check the threshold crossing records to find out the performance event that the lower order path error crosses the preset threshold. Handle the threshold-crossing performance event.
----End
Related Information
None.
A.3.149 LP_R_FIFO
Description
The LP_R_FIFO is an alarm indicating that the FIFO overflows on the receive side of the lower order path.
Issue 03 (2012-07-30)
488
A Alarm Reference
Attribute
Parameters
None.

When the LP_R_FIFO alarm occurs, the service has errors.
Possible Causes
l l Cause 1: The clock of the local NE is not synchronized with the clock of the opposite NE. Cause 2: A certain board is faulty.
Procedure
Step 1 Cause 1: The clock of the local NE is not synchronized with the clock of the opposite NE. 1. Browse current performance events, and check whether the performance event of TU pointer justification occurs on the local NE and the opposite NE. If... The TU pointer justification occurs Then... Handle the performance event. For details, see C.3.2 TUPJCHIGH, TUPJCLOW, and TUPJCNEW. Go to Cause 2.
The TU pointer justification does not occur Step 2 Cause 2: A certain board is faulty. 1. Replace the alarmed board.
----End
Related Information
None.
A.3.150 LP_RDI
Description
The LP_RDI is an alarm indicating the lower order path remote receive failure. This alarm occurs when the board detects that bit 8 of byte V5 is 1.
A Alarm Reference
Attribute
Parameters
None.

When the LP_RDI alarm occurs, the service on the local NE is not affected. The service received by the opposite NE, however, is interrupted.
Possible Causes
Cause 1: The local NE detects the message that is returned by the opposite NE and indicates the lower 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 the lower order path remote receive failure. 1. Handle the lower order path alarm on the opposite NE.
----End
Related Information
None.
A.3.151 LP_RDI_VC12
Description
The LP_RDI_VC12 is an alarm indicating that data reception fails at the remote end of VC-12 lower order path. This alarm occurs when the board detects that bit 8 of byte V5 is 1.
Attribute
Parameters
A Alarm Reference
Name Parameter 1
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 the opposite NE, however, is interrupted.
Possible Causes
Cause 1: The local site receives a message from the remote site, and the message says that data reception fails at the remote end of a lower order path.
Procedure
Step 1 Cause 1: The local site receives a message from the remote site, and the message says that data reception fails at the remote end of a lower order path. 1. Handle the alarm of the lower order path on the remote site.
----End
Related Information
None.
A.3.152 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
Issue 03 (2012-07-30)
Meaning Has a fixed value of 0x01.

A Alarm Reference
Name
Meaning

When the LP_RDI_VC3 alarm occurs, the services at the local site are not affected, but the opposite site cannot receive services.
Possible Causes
The local site receives a message from the opposite site, and the message says that data reception fails 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 data reception 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
Related Information
None.
A.3.153 LP_REI
Description
The LP_REI is an alarm indicating the lower order path remote error. This alarm occurs when the board detects that bit 3 of V5 is 1.
Attribute
Parameters
None.

When the LP_REI alarm occurs, the service on the local NE is not affected. The service received by the opposite NE, however, has errors.
A Alarm Reference
Possible Causes
Cause 1: The local NE detects the message that is returned by the opposite NE and indicates the lower order path remote errors.
Procedure
Step 1 Cause 1: The local NE detects the message that is returned by the opposite NE and indicates the lower order path remote errors. 1. Handle the LP_BBE performance event on the opposite NE.
----End
Related Information
None.
A.3.154 LP_REI_VC12
Description
The LP_REI_VC12 is an alarm indicating that there are bit errors at the remote end of a VC-12 lower order path. This alarm occurs when the board detects that bit 3 of byte V5 is 1.
Attribute
Parameters

Bit errors exist in the service in the receive direction of the remote site.
Possible Causes
Cause 1: The local site receives a message from the remote site, and the message says that there are bit errors in the lower order path.
A Alarm Reference
Procedure
Step 1 Cause 1: The local site receives a message from the remote site, and the message says that there are bit errors in the lower order path. 1. Handle the LPBBE performance event of the remote site. ----End
Related Information
None.
A.3.155 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 is 1.
Attribute
Parameters

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 bit errors 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 there are bit errors at the remote end of a lower order (VC-3) path.
A Alarm Reference
1.
Handle the alarm in the lower order (VC-3) path at the opposite site.
----End
Related Information
None.
A.3.156 LP_RFI
Description
The LP_RFI is an alarm indicating the lower order path remote failure. This alarm occurs when the board detects that bit 4 of V5 is 1.
Attribute
Parameters
None.

When the LP_RFI alarm occurs, the service on the local NE is not affected. The alarm only indicates that the lower order paths on the opposite NE cannot carry services.
Possible Causes
Cause 1: The local NE detects the message that is returned by the opposite NE and indicates the lower order path remote failure.
Procedure
Step 1 Cause 1: The local NE detects the message that is returned by the opposite NE and indicates the lower order path remote failure. 1. Handle the lower order path alarm on the opposite NE.
----End
Related Information
None.
A.3.157 LP_SLM
A Alarm Reference
Description
The LP_SLM is an alarm indicating that a mismatched signal label is detected in the lower order path. This alarm is reported when the board detects a signal label mismatch between the V5 bytes.
Attribute
Parameters
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 not match 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 not match 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 with each other. For details, see Configuring VC-12 POHs.
----End
Related Information
None.
A.3.158 LP_SLM_VC12
Description
The LP_SLM_VC12 is an alarm indicating that a mismatched signal label is detected in the lower order path. This alarm is reported when the board detects a signal label mismatch between the V5 bytes.
Issue 03 (2012-07-30)
496
A Alarm Reference
Attribute
Parameters

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 not match 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 not match 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 with each other. For details, see Configuring VC-12 POHs.
----End
Related Information
None.
A.3.159 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.
A Alarm Reference
Attribute
Parameters

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 label in 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 the signal 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 both sites. For details, see Configuring VC-4 POHs.
----End
Related Information
None.
A.3.160 LP_T_FIFO
Description
The LP_T_FIFO is an alarm indicating that the FIFO overflows on the transmit side of the lower order path.
A Alarm Reference
Attribute
Parameters
None.

Bit errors occur in the services.
Possible Causes
l l Cause 1: The frequency offset of the input signal is very large. Cause 2: A certain board is faulty.
Procedure
Step 1 Cause 1: The frequency offset of the input signal is very large. 1. Use an SDH analyzer to check whether the frequency offset of the input signal is within 50 ppm. If... The frequency offset is very large The frequency offset is within 50 ppm Step 2 Cause 2: A certain board is faulty. 1. Replace the alarmed board. Then... Troubleshoot the remote site. Go to Cause 2.
----End
Related Information
None.
A.3.161 LP_TIM
Description
The LP_TIM is an alarm indicating a mismatched trace identifier is detected in the lower order path. This alarm is reported when the board detects a mismatch between the J2 bytes at both ends.
Issue 03 (2012-07-30)
499
A Alarm Reference
Attribute
Parameters
None.

None.
Possible Causes
l l 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. 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 be transmitted 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 to be transmitted by the remote site. For details, see Configuring VC-12 POHs.
Step 2 Cause 2: The data configuration at the intermediate nodes is incorrect. 1. Check whether the cross-connections of the intermediate nodes where the service travels are configured correctly. If not, reconfigure the cross-connections. For details, see Querying TDM Services.
----End
Related Information
None.
A.3.162 LP_TIM_VC12
Description
The LP_TIM_VC12 is an alarm indicating a mismatched trace identifier is detected in the lower order path. This alarm is reported when the board detects a mismatch between the J2 bytes at both ends.
Issue 03 (2012-07-30)
500
A Alarm Reference
Attribute
Parameters

None.
Possible Causes
l l 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. 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 be transmitted 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 to be transmitted by the remote site. For details, see Configuring VC-12 POHs.
Step 2 Cause 2: The data configuration at the intermediate nodes is incorrect. 1. Check whether the cross-connections of the intermediate nodes where the service travels are configured correctly. If not, reconfigure the cross-connections. For details, see Querying TDM Services.
----End
Related Information
None.
A.3.163 LP_TIM_VC3
A Alarm Reference
Description
The 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
Parameters

None.
Possible Causes
l l Cause 1: Byte J1 to be received at the local site does not match with byte J1 to be transmitted at the opposite site. 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 at the 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 Querying TDM Services.
----End
Related Information
None.
A Alarm Reference
A.3.164 LP_UNEQ
Description
The LP_UNEQ is an alarm indicating that the lower order path is unequipped. This alarm is reported 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, protection switching may be triggered.
Possible Causes
The data configuration is incorrect. l l Cause 1: The tributary path at the local site is configured with services, but the tributary path at the remote site is not configured with services. Cause 2: The cross-connection configuration at the intermediate nodes is incorrect.
Procedure
Step 1 Cause 1: The tributary path at the local site is configured with services, but the tributary path at the remote site is not configured with services. 1. Check whether the tributary path at the remote site is configured with services. For details, see Querying TDM Services. If... Then...
The tributary path at the remote site is not Configure services for the tributary path at configured with services the remote site. 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 Alarm Reference
Related Information
None.
A.3.165 LP_UNEQ_VC12
Description
The LP_UNEQ_VC12 is an alarm indicating that the VC-12 path is unequipped. This alarm occurs when the board detects that the V5 byte signal label is 0.
Attribute
Parameters

If the alarm is generated due to incorrect service configurations, the services are interrupted.
Possible Causes
The data configuration is incorrect. l l Cause 1: The tributary path at the local site is configured with services, but the tributary path at the remote site is not configured with services. Cause 2: The cross-connection configuration at the intermediate nodes is incorrect.
Procedure
Step 1 Cause 1: The tributary path at the local site is configured with services, but the tributary path at the remote site is not configured with services. 1. Check whether the tributary path at the remote site is configured with services. For details, see Querying TDM Services.
Issue 03 (2012-07-30)
A Alarm Reference
If... The tributary path at the remote site is not configured with services
Then... 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
Related Information
None.
A.3.166 LP_UNEQ_VC3
Description
The LP_UNEQ_VC3 alarm indicates that a lower order (VC-3) path is unequipped. A board reports this alarm when detecting that the C2 byte signal label is 0.
Attribute
Parameters

The services in the path are unavailable. If the services are configured with protection, protection switching is triggered.
Possible Causes
The data configuration is incorrect.
A Alarm Reference
l l
Cause 1: The tributary path at the local site is configured with services, but the tributary path at the opposite site is not. 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 at the 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... The tributary path at the opposite site is not configured with services The tributary path at the opposite site is configured with services Then... Configure services. 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. If not, reconfigure the cross-connections. For details, see Querying TDM Services.
----End
Related Information
None.
A.3.167 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
Issue 03 (2012-07-30)
506
A Alarm Reference
Name
Meaning
Parameter 1 Indicates the type of the protection group. 0x01: linear MS protection. Parameter 2 Indicates the ID of the alarmed protection group. For example, 0x01 indicates that the alarm is reported by protection group 1.

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 l l The switching modes (single-ended or dual-ended) at the local and remote sites are different. The last three bits of the K2 byte are set to the indicated mode. 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.168 LPT_CFG_CLOSEPORT
Description
The LPT_CFG_CLOSEPORT is an alarm indicating that the LPT closes the access port of the local NE. Upon detecting that the convergence port of the local NE or the access port of the remote NE is faulty, the LPT automatically closes the access port of the local NE. Then, the LPT_CFG_CLOSEPORT alarm is reported.
Attribute
Issue 03 (2012-07-30)
507
A Alarm Reference
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1, Parameter 2 Parameter 3 Parameter 4, Parameter 5 Meaning Indicates the board ID. Indicates the ID of the sub-board. Indicate the port ID.

When this alarm occurs, services are switched to the backup network and the LPT closes the access port of the remote NE at the same time.
Possible Causes
l 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 convergence port of the remote NE report the ETH_LOS alarm or other alarms related to boards and optical modules. If yes, clear these alarms. Then, check whether the LPT_CFG_CLOSEPORT alarm is cleared.
2.
----End
Related Information
None.
A.3.169 LPT_INEFFECT
Description
The LPT_INEFFECT is an alarm indicating that the LPT function fails. If the user configures the LPT function but the board does not support the LPT function, the LPT_INEFFECT alarm is reported.
Issue 03 (2012-07-30)
508
A Alarm Reference
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Parameter 2, Parameter 3 Meaning Indicates the ID of the IP port. Indicate the port ID. The values are always 0x00 0x01. Parameter 4, Parameter 5 The values are always 0xff 0xff.

When the alarm is generated, the services are not affected. If the board hardware is of a very early version, the board software automatically prevents the LPT protocol state machine from running, but reserves the LPT configuration.
Possible Causes
Cause 1: The board hardware is of a very early version, and the user configures the LPT function.
Procedure
Step 1 Cause 1: The board hardware is of a very early version, and the user configures the LPT function. 1. Check whether the LPT function is required. If... The LPT function is required Then... Replace the board with a board of the proper version. For details, see 6 Part Replacement.
The LPT function is not required Delete the configuration of the LPT. For details, see LPT Configuration. ----End
Related Information
None.
A Alarm Reference
A.3.170 LPT_RFI
Description
The LPT_RFI is a remote failure indication of the link path through (LPT) function. This alarm occurs when the LPT function detects the failure of the remote port or the LPT service network.
Attribute
Alarm Severity Critical Alarm Type Service alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the ID of the IP port.
Parameter 2, Parameter 3 Indicate the ID of the optical interface. The values are always 0x00 0x01. Parameter 4 The value is always 0xff.

During the data transmission, the links are unavailable and the services are interrupted when the LPT function detects the failure of the remote port or the service network. At the same time, the backup links are enabled. If the backup links are available, the services can be restored on the backup links.
Possible Causes
l l Cause 1: The remote port fails due to the alarms such as ETH_LOS and LSR_NO_FITED, or the remote port is disabled. 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.
Procedure
Step 1 Check the alarms on the NMS, determine the board that reports the LPT_RFI alarm, and then determine the ID of the alarmed port on the board according to Parameter 1.
A Alarm Reference
Step 2 Cause 1: The remote port fails due to the alarms such as ETH_LOS and LSR_NO_FITED, or the remote port is disabled. 1. Check whether the corresponding opposite port is enabled. If... The opposite port is disabled The opposite port is enabled 2. Then... Enable the opposite port. Go to the next step.
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 and MW_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_LOS l LSR_NO_FITED l BIP_EXC and B3_EXC l TU_LOP, TU_AIS, VCAT_LOA, VCAT_LOM_VC12, and LP_UNEQ_VC12 ----End
Related Information
None.
A.3.171 LSR_BCM_ALM
Description
The LSR_BCM_ALM is an alarm indicating a threshold-crossing of the bias current of a laser. This alarm is reported when the bias current of a laser exceeds the threshold.
Attribute
Parameters
None.
A Alarm Reference

When this alarm occurs, the laser is functioning improperly. An over-high current burns out the laser, and an over-low current causes insufficient gains. Both can interrupt services.
Possible Causes
l l Cause 1: The laser is aged. Cause 2: The laser is faulty.
Procedure
Step 1 Browse alarms on the NMS and determine the board that reports the alarm. Step 2 Replace the pluggable optical module. For details, see Replacing Pluggable Optical Modules. ----End
Related Information
None.
A.3.172 LSR_NO_FITED
Description
The LSR_NO_FITED is an alarm indicating that the SFP optical module is not installed.
Attribute
Parameters
None.

The optical interface fails to carry services.
Possible Causes
l l Cause 1: The laser of the local site is not installed. Cause 2: The optical module is faulty.
Procedure
Step 1 Cause 1: The SFP optical module of the local site is not installed.
A Alarm Reference
1.
Find out why the SFP optical module is not installed, and contact Huawei technical support engineers for the installation. If SFP module is not needed, see Configuring an SFP Port to delete this port. 6.14 Replacing the SFP.
Step 2 Cause 2: The optical module is faulty. 1. ----End
Related Information
None.
A.3.173 LSR_WILL_DIE
Description
The LSR_WILL_DIE is an alarm indicating that the laser is to stop working.
Attribute
Parameters
None.

When this alarm occurs, bit errors occur in the service. If the board is not replaced in a timely manner, services are interrupted after the laser is damaged.
Possible Causes
l l Cause 1: The laser is aged. Cause 2: The detection circuit of the board is faulty.
Procedure
Step 1 Cause 1: The laser is aged. 1. 1. 6.14 Replacing the SFP. 6.4 Replacing the Channelized STM-1 Processing Board. Step 2 Cause 2: The detection circuit of the board is faulty. ----End
Related Information
None.
A Alarm Reference
A.3.174 LTI
Description
The LTI is an alarm indicating that the synchronization sources are lost. This alarm is reported when all the synchronization sources for the NE are lost.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning 0x01: system priority list 0x02: external clock priority list

The clock enters the free-run mode and loses synchronization with other NE clocks.
Possible Causes
l l l l l l Cause 1: The clock configuration is incorrect. Cause 2: All the clock sources in the clock source priority table fail. Cause 3: A fiber cut or a cable cut occurs. Cause 4: The synchronization source is set to the manual reversion mode. Cause 5: No input is available from the external clock source. Cause 6: The board is faulty.
Procedure
Step 1 Cause 1: The clock configuration is incorrect. 1. Check whether the data in the clock source priority table meets the network planning requirement. For details, see Querying the Clock Synchronization Status. If... The configuration is incorrect The configuration is correct
Issue 03 (2012-07-30)
Then... Correct the configuration. Go to Cause 2.

514
A Alarm Reference
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... The synchronization source is an external clock The synchronization source is a line clock The synchronization source is an IF clock The synchronization source is a tributary clock The synchronization source is an Ethernet clock Step 3 Cause 3: A fiber cut or a cable cut occurs. 1. Connect the fiber or cable properly. Then... Handle the EXT_SYNC_LOS alarm. Handle the alarm that occurs on the line board. Handle the alarm that occurs on the IF board. Handle the alarm that occurs on the tributary board. Handle the alarm that occurs on the Ethernet board.
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.
Step 6 Cause 6: The board is faulty. 1. 6 Part Replacement.
----End
Related Information
None.
A.3.175 MAC_EXT_EXC
Description
The MAC_EXT_EXC alarm indicates that the number of bit errors at the MAC layer crosses the threshold.
Attribute
Issue 03 (2012-07-30)
515
A Alarm Reference
Parameters Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the threshold crossing type. l 0x01: ETHDROP threshold crossing l 0x02: ETHEXCCOL threshold crossing l 0x03: RXBBAD threshold crossing

When the MAC_EXT_EXC alarm occurs, the performance of services degrades.
Possible Causes
l l l Cause 1: ETHDROP threshold crossing. The number of packet loss events crosses the upper threshold. Cause 2: ETHEXCCOL threshold crossing. The number of frames unsuccessfully transmitted after successive collisions crosses the upper threshold. Cause 3: RXBBAD threshold crossing. The number of bytes in received bad packets crosses the 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 receive Set the working modes of the ports at the ends work in different modes or in half- transmit and receive ends to full-duplex or duplex mode auto-negotiation. Ensure that the working modes of the ports at the transmit and receive ends are the same. For details, see Setting the Basic Attributes of Ethernet Ports. The ports at the transmit and receive Go to the next step. ends work in the same mode and neither port 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.
A Alarm Reference
Check whether the local end reports alarms such as ETH_LOS as the external line is damaged or 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.176 MAC_FCS_EXC
Description
The MAC_FCS_EXC alarm indicates that the software detects that the number of bit errors at the MAC layer crosses the threshold. The software periodically detects the number of bytes received by the MAC chip and the number of bytes that have bit errors. The MAC_FCS_EXC alarm is reported when the number of bit errors crosses the threshold.
Attribute
Parameters
None.

When the MAC_FCS_EXC alarm occurs, the performance of services degrades.
Possible Causes
l l l Cause 1: The performance of the line signals degrades. Cause 2: The input optical power is abnormal. Cause 3: A fiber connector is dirty.
Procedure
Step 1 Cause 1: The performance of the line signals degrades. 1. 2. On the NMS, check for a LOOP_ALM alarm. If there is any, clear it. For details, see 8.7 Software Loopback. If the MAC_FCS_EXC 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, and then check whether the MAC_FCS_EXC alarm is cleared. If the MAC_FCS_EXC alarm persists, check whether a cable or fiber is faulty. Replace the faulty cable or fiber, and then check whether the MAC_FCS_EXC alarm is cleared.
3.
Issue 03 (2012-07-30)
A Alarm Reference
Step 2 Cause 2: The input optical power is abnormal. 1. 2. Check whether the alarmed port reports an IN_PWR_ABN alarm as well. 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
Related Information
None.
A.3.177 MOD_COM_FAIL
Description
The MOD_COM_FAIL is an alarm indicating that Module communicates abnormally.
Attribute
Parameters
Parameter 1 0x11 indicates that the communication between the system control unit and packet switching unit is failed.

The related operations cannot be performed by using the NMS and the performance information of each module cannot be queried.
Possible Causes
l l
Issue 03 (2012-07-30)
Cause 1: The software processing of the related modules of the boardis faulty. Cause 2: The board hardware is faulty.
A Alarm Reference
Procedure
Step 1 Cause 1: The software processing of the related modules of the board is faulty. 1. 2. Perform a cold reset on the faulty board by using the NMS. For details, refer to 8.8.1 Cold Reset. 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.10 Replacing the System Control, Switch and Timing Board.
----End
Related Information
None.
A.3.178 MOD_TYPE_MISMATCH
Description
The MOD_TYPE_MISMATCH alarm indicates that a mismatched port module is detected.
Attribute
Alarm Severity Critical Alarm Type Maloperation
Parameters
Parameter 1 Indicates the ID of the port that reports the alarm. For example, 0x01 indicates that 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.
A Alarm Reference
Procedure
Step 1 Cause 1: The preset type of the SFP module is different from the actual type of the SFP module. 1. 2. Find out the port that reports the alarm according to the alarm parameters. Check whether the preset type of the SFP module is the same as the actual type of the SFP module. If... Then...
The preset type of the SFP module is the Replace the optical/electrical SFP same as the actual type of the SFP module module. Ensure that the new SFP module is of the correct type. The preset type of the SFP module is Reset the type of the SFP module. different from the actual type of the SFP module ----End
Related Information
None.
A.3.179 MP_DELAY
Description
The MP_DELA is an alarm indicating a delay of the Multi-link Point-to-Point (ML-PPP) group. This alarm is reported when the differential delay between MP group members exceeds the threshold.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Parameter 2 Meaning Indicates the ID of the board. Indicates the ID of the subborad.
Issue 03 (2012-07-30)
520
A Alarm Reference
Name Parameter 3, Parameter 4 Parameter 5
Meaning Indicates the ID of the port. Indicates the ID of the timeslot or channel. 0xFF indicates that the parameter value is reserved.

When this alarm occurs, the service quality of the MP group deteriorates.
Possible Causes
l l Cause 1: The signal quality of the MP group members deteriorates. Cause 2: The maximum differential delay is configured low.
Procedure
Step 1 Cause 1: The signal quality of the MP group members deteriorates. 1. 2. Check whether the network is congested. If yes, expand the network and then check whether the alarm is cleared. If the alarm persists, replace the cable connecting to the port that reports the alarm. Then, check whether the alarm is cleared. Check whether the maximum differential delay is configured properly on the NMS. For details, see Creating MP Groups. If the maximum differential delay is configured low, increase the value based on the actual situation or disable the fragment function.
Step 2 Cause 2: The maximum differential delay is configured low. 1. 2.
----End
Related Information
None.
A.3.180 MP_DOWN
Description
The MP_DOWN is an alarm indicating a failure of the Multi-link Point-to-Point (ML-PPP) group. This alarm is reported when the number of the valid activated MP group members is less than that of the specified minimum activated links. The minimum activated links is 1 by default.
Issue 03 (2012-07-30)
521
A Alarm Reference
Attribute
Parameters
Parameter 1 Indicates the cause of the failure. l 0x00: unknown l 0x01: indicates that the number of the MP group members is less than the specified number. l 0x02: indicates that the configurations at both ends of the MP group are inconsistent. l 0x03: indicates that the NCP protocol of the MP group is running improperly.

l l When this alarm occurs, all services that the MP group carries are interrupted. This alarm is cleared automatically when the number of the valid activated MP group members is greater than the specified minimum activated links and the MP group is configured with an IP address.
Possible Causes
l l l l l Cause 1: The number of the valid activated MP group members is less than that of the minimum activated links. Cause 2: The configurations at both ends of the MP group are inconsistent. Cause 3: The NCP protocol on the member links of the MP group is running improperly. Cause 4: The physical link is interrupted. Cause 5: The MP group is not configured with an IP address or a subnet mask.
Procedure
Step 1 Cause 1: The number of the valid activated MP group members is less than that of the minimum activated links. 1. On the NMS, check whether the number of the valid activated MP group members is less than that of the minimum activated links. For details, see Querying the MP Group Protocol Information. If the number is less than that of the minimum activated links, change the minimum activated links to a value less than the number of configured MP group members.
2.
Issue 03 (2012-07-30)
A Alarm Reference
Step 2 Cause 2: The configurations at both ends of the MP group are inconsistent. 1. On the NMS, check whether the configurations at both ends of the MP group are consistent. If not, modify the parameters. For details, see Creating MP Groups. On the NMS, check whether the PPP_LCP_FAIL or PPP_NCP_FAIL alarm exists on the member links of the MP group. If yes, clear the PPP_LCP_FAIL or PPP_NCP_FAIL alarm immediately. Then, check whether the MP_DOWN alarm is cleared. On the NMS, check whether a signal alarm such as R_LOS or T_ALOS exists on the member links of the MP group. If yes, clear the R_LOS or T_ALOS alarm immediately. Configure an IP address and a subnet mask for the MP group. For details, see Creating MP Groups.
Step 3 Cause 3: The NCP protocol on the member links of the MP group is running improperly. 1. 2.
Step 4 Cause 4: The physical link is interrupted. 1. 2. 1.
Step 5 Cause 5: The MP group is not configured with an IP address or a subnet mask.
----End
Related Information
None.
A.3.181 MPLS_PW_AIS
Description
The MPLS_PW_AIS is an alarm indicating a defect in the forward direction of a PW. This alarm is reported when the Ethernet port receives an AIS packet, indicating that a fault occurs on the tunnel at the server layer of the PW.
Attribute
Parameters
None.

When this alarm occurs, services may be interrupted.
Possible Causes
Cause 1: The MPLS-TP OAM is incorrectly configured for tunnels between upstream NEs. Cause 2: An upstream NE detects a fault on the tunnel at the PW server layer.
A Alarm Reference
Procedure
Step 1 Cause 1: The MPLS-TP OAM is incorrectly configured for tunnels between upstream NEs. 1. Check whether the MPLS-TP OAM is configured correctly for tunnels between the local NE and its upstream NEs. If not, modify the configuration. For details, see Configuring MEP Parameters for MPLS-TP PW OAM. Check whether a tunnel fault occurs on the S-PE. If an alarm such as MPLS_TUNNEL_LOCV exists, clear the alarm immediately.
Step 2 Cause 2: An upstream NE detects a fault on the tunnel at the PW server layer. 1.
----End
Related Information
None.
A.3.182 MPLS_PW_BDI
Description
The MPLS_PW_BDI is an alarm of PW backward defect indication. This alarm occurs when the local NE receives the BDI packet, notifying that the remote NE detects that the PW is faulty.
Attribute
Parameters
None.

The services on the transmit side of the local NE are faulty.
Possible Causes
Cause 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... A board on the remote NE is reset or faulty The physical link between the local NE and the remote NE is faulty
Issue 03 (2012-07-30)
Then... Rectify the fault on the remote NE. Rectify the fault on the physical link.
524
A Alarm Reference
If... The bandwidth allocated to the PW is fully occupied. ----End
Then... Increase the bandwidth of the PW.
Related Information
None.
A.3.183 MPLS_PW_Excess
Description
The 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 packets are received within three consecutive CV/FFD periods.
Attribute
Parameters
None.

Services may be interrupted if excessive redundant packets are received.
Possible Causes
l l Cause 1: Multiple PWs are configured with the same label and PW ID. Cause 2: Physical links are misconnected.
Procedure
Step 1 Cause 1: Multiple PWs are configured with the same label and PW ID. 1. 2. 3. Check whether multiple PWs are configured with the same label and PW ID. If yes, delete the redundant PWs or change the PW ID and label of each PW to unique values. Then, check whether the alarm clears. If... The alarm clears The alarm persists
Issue 03 (2012-07-30)

525
A Alarm Reference
Step 2 Cause 2: Physical links are misconnected. 1. 2. Check whether any fiber or cable is misconnected. If yes, rectify the fault.
----End
Related Information
None.
A.3.184 MPLS_PW_LOCV
Description
The MPLS_PW_LOCV is an alarm of PW connectivity loss. This alarm occurs when no expected CV/FFD packets are received within three consecutive CV/FFD periods.
Attribute
Parameters
None.

Possible Causes
l l l l l l Cause 1: The remote NE of the PW stops transmitting CV/FFD packets. Cause 2: The OAM is different between the ends of the PW. Cause 3: The PW that carries services is faulty. Cause 4: The remote NE of the PW is faulty. Cause 5: The service interface is configured incorrectly. 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... The remote NE of the PW stops transmitting CV/FFD packets
Issue 03 (2012-07-30)
Then... Enable the CV/FFD detection and then check whether the alarm clears.
526
A Alarm Reference
If... The remote NE of the PW keeps transmitting CV/FFD packets
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 (Y.1711) Parameters according to the plan. If yes, go to cause 3. 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. Check whether any link-related alarm is reported. If yes, clear the alarm. Then, check whether the MPLS_PW_LOCV alarm is cleared. If... The alarm is cleared The alarm persists 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 check whether the MPLS_PW_LOCV alarm is cleared. 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... The alarm is cleared The alarm persists Then... End the alarm handling. Go to Cause 5. Then... End the alarm handling. Go to Cause 4.
Step 3 Cause 3: The PW that carries services is faulty. 1. 2.
2.
Step 5 Cause 5: The service interface is configured incorrectly. 1. 2. Check whether the service interface is configured correctly according to service planning. If not, reconfigure the service interface. Then, check whether the MPLS_PW_LOCV alarm is cleared. If... The alarm is cleared The alarm persists Then... End the alarm handling. Go to Cause 6.
Step 6 Cause 6: Serious congestion occurs on the network. 1. 2. Check whether the bandwidth allocated to the faulty tunnel is fully occupied. If yes, increase the bandwidth of the PW or eliminate the sources that transmit a large amount of invalid data.
----End
Related Information
None.
A Alarm Reference
A.3.185 MPLS_PW_MISMATCH
Description
The 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 packets with wrong TTSIs are received within three consecutive CV/FFD periods.
Attribute
Parameters
None.

Services are interrupted or the packets from other PWs are received.
Possible Causes
l l Cause 1: The ingress node or egress node of the faulty PW is configured incorrectly. Cause 2: Physical links are misconnected.
Procedure
Step 1 Cause 1: The ingress node or egress node of the faulty PW is configured incorrectly. 1. 2. Check whether the ingress node and egress node of the faulty PW are configured correctly according to NE planning. If the ingress node or egress node is configured incorrectly, correct the configuration and then check whether the alarm clears.
Step 2 Cause 2: Physical links are misconnected. 1. 2. Check whether any fiber or cable is misconnected. If yes, rectify the fault.
----End
Related Information
None.
Issue 03 (2012-07-30)
528
A Alarm Reference
A.3.186 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 correct TTSIs 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.
Possible Causes
l l Cause 1: The PW is configured incorrectly. Cause 2: Physical links are misconnected.
Procedure
Step 1 Cause 1: The PW is configured incorrectly. 1. 2. Check whether the PW are configured correctly according to NE planning. If the PW is configured incorrectly, correct the configuration and then check whether the alarm clears. Check whether any fiber or cable is misconnected. If yes, rectify the fault.
Step 2 Cause 2: Physical links are misconnected. 1. 2.
----End
Related Information
None.
A.3.187 MPLS_PW_OAMFAIL
Description
The MPLS_PW_OAMFAIL is an alarm indicating a failure of the OAM protocol negotiation. This alarm is reported when the OAM protocol negotiation fails on NEs at both ends of the PW.
A Alarm Reference
Attribute
Parameters
None.

When this alarm occurs, the PW APS protection switching is triggered, and services are switched to the protection PW.
Possible Causes
Cause 1: The OAM function is enabled only on the NE at one end of the PW.
NOTE
Only the NE that is enabled with the OAM function reports the MPLS_PW_OAMFAIL alarm.
Cause 2: The PW has been interrupted when enabling the OAM function.
NOTE
When the PW is interrupted in the forward or reverse direction, the peer or local NE reports the MPLS_PW_OAMFAIL alarm.
Procedure
Step 1 Cause 1: The OAM function is enabled only on the NE at one end of the PW. 1. On the NMS, query this alarm and check whether the OAM function is enabled on NEs at both ends of the PW. If the OAM function is enabled only on one NE, set OAM Status to Enabled on the other NE.
Step 2 Cause 2: The PW has been interrupted when enabling the OAM function. 1. On the NMS, check whether tunnel-related alarms such as A.3.202 MPLS_TUNNEL_OAMFAIL occur on NEs at both ends of the PW. If yes, clear them immediately. Check whether service-related alarms such as A.3.184 MPLS_PW_LOCV occur on NEs at both ends of the PW. If yes, clear them immediately.
2.
----End
Related Information
None.
Issue 03 (2012-07-30)
530
A Alarm Reference
A.3.188 MPLS_PW_RDI
Description
The MPLS_PW_RDI is an alarm indicating a defect in the backward direction of a PW. The local MEP sends an RDI packet to the remote MEP when detecting a PW fault. The MPLS_PW_RDI alarm is reported when the remote MEP receives the RDI packet.
Attribute
Parameters
None.

When this alarm occurs, services in the transmit direction on the remote MEP are affected.
Possible Causes
The local MEP NE detects a PW fault.
Procedure
Step 1 Handle the PW fault according to the MPLS-TP OAM-related alarm reported by the remote MEP. Step 2 If the alarm persists, check whether the physical link between faulty NEs is faulty. For example, the optical fiber or cable is damaged or pressed. If yes, replace the faulty optical fiber or cable. Step 3 Check whether the bandwidth allocated to the PW is used up. If yes, increase the bandwidth allocated to the PW. ----End
Related Information
None.
A.3.189 MPLS_PW_SD
Description
The MPLS_PW_SD is an alarm of signal degrade on the PW. This alarm is reported when the packet loss rate of the connectivity check (CC) crosses the SD threshold but is lower than the SF threshold.
A Alarm Reference
Attribute
Parameters
None.

Services degrade and moderate packet loss occurs.
Possible Causes
l l l Cause 1: The bandwidth of the PW is fully occupied. Cause 2: The physical port has bit errors or packet loss. Cause 3: The fiber connector or the optical module is dirty.
Procedure
Step 1 Cause 1: The bandwidth of the PW is fully occupied. 1. 2. Check whether the bandwidth allocated to the faulty PW is fully occupied. 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
Related Information
None.
A.3.190 MPLS_PW_SF
Description
The MPLS_PW_SF is an alarm of signal failure on the PW. This alarm occurs when the number of received connectivity check (CC) packets is less than the signal failure (SF) threshold.
Issue 03 (2012-07-30)
532
A Alarm Reference
Attribute
Parameters
None.

Services fail and severe packet loss occurs.
Possible Causes
l l l Cause 1: The bandwidth of the PW is fully occupied. Cause 2: The physical port has bit errors or packet loss. Cause 3: The fiber connector or the optical module is dirty.
Procedure
Step 1 Cause 1: The bandwidth of the PW is fully occupied. 1. 2. Check whether the bandwidth allocated to the faulty PW is fully occupied. 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.191 MPLS_PW_UNEXPMEG
Description
The MPLS_PW_UNEXPMEG is an alarm indicating that the MEP receives a packet with correct MEG level but incorrect MEG ID.
Issue 03 (2012-07-30)
533
A Alarm Reference
Attribute
Parameters
None.

When this alarm occurs, the MEP receives CCM packets of other PWs.
Possible Causes
l l Cause 1: MEG IDs configured on NEs at both ends of the PW are different. Cause 2: The PW is configured incorrectly. Multiple PWs use the same label.
Procedure
Step 1 Cause 1: MEG IDs configured on NEs at both ends of the PW are different. 1. Check whether the PW configurations are consistent between NEs at both ends of the PW. MEG IDs on NEs at both ends of a PW must be set to the same value. For details, see Querying Information and Running Status of PWs. Check whether the PW label is configured correctly. If multiple PWs use the same label, reconfigure the PW label. For details, see Querying Information and Running Status of PWs.
Step 2 Cause 2: The PW is configured incorrectly. Multiple PWs use the same label. 1.
----End
Related Information
None.
A.3.192 MPLS_PW_UNEXPMEP
Description
The MPLS_PW_UNEXPMEP is an alarm indicating an error in the PW OAM CCM information. This alarm is reported when the sink NE of the PW receives a CCM packet with an unexpected MEP ID.
Attribute
Issue 03 (2012-07-30)
534
A Alarm Reference
Parameters
None.

When this alarm occurs, services are interrupted or the sink NE receives CCM packets of other PWs.
Possible Causes
MEP IDs are inconsistent between NEs at both ends of a PW.
Procedure
Step 1 MEP IDs are inconsistent between NEs at both ends of a PW. 1. Check whether the remote MEP ID on the source NE is correctly configured with the MEP ID of the sink NE. If not, reconfigure the remote MEP ID on the source NE.
----End
Related Information
None.
A.3.193 MPLS_PW_UNEXPPER
Description
The MPLS_PW_UNEXPPER is an alarm indicating that the PW does not receive the CCM packet in the expected period. This alarm is reported when the sink NE of the PW receives a CCM packet with correct MEG level, MEG ID, and MEP ID but in an unexpected period. For example, the transmit interval configured on the source and sink NEs is 10 ms, but the sink NE receives the CCM packet from the source NE after 20 ms.
Attribute
Parameters
None.

When this alarm occurs, services are interrupted or the sink NE receives CCM packets of other PWs.
A Alarm Reference
Possible Causes
CCM packet periods are inconsistent between the source and sink NEs at both ends of the PW.
Procedure
Step 1 CCM packet periods are inconsistent between the source and sink NEs at both ends of the PW. 1. Check whether PW configurations are consistent between the source and sink NEs. CCM packet periods on NEs at both ends of a PW must be set to the same value. For details, see Querying Information and Running Status of PWs.
----End
Related Information
None.
A.3.194 MPLS_PW_UNKNOWN
Description
The MPLS_PW_UNKNOWN is an alarm of unknown defects on the PW. This alarm occurs when the connectivity check (CC) packets of unexpected types, periods, and values are received within 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
A Alarm Reference
Related Information
None.
A.3.195 MPLS_TUNNEL_AIS
Description
The MPLS_TUNNEL_AIS is an alarm indicating a defect in the forward direction of a tunnel. This alarm is reported when the Ethernet port receives an AIS packet, indicating that a fault occurs on the physical link at the server layer of the tunnel.
Attribute
Parameters
None.

Possible Causes
An upstream NE detects a fault on the physical link at the server layer of the tunnel.
Procedure
Step 1 An upstream NE detects a fault on the physical link at the server layer of the tunnel. 1. Check whether the physical link is faulty between the local NE and the upstream NE. Physical link faults may be caused by a fiber cut, a faulty optical module, a faulty board, or a faulty . If yes, rectify the faults.
----End
Related Information
None.
A.3.196 MPLS_TUNNEL_BDI
Description
The MPLS_TUNNEL_BDI is an alarm of tunnel backward defect indication. This alarm occurs when the port of the local NE receives the backward defect indication (BDI) packet, notifying that the opposite NE detects that the tunnel is faulty.
A Alarm Reference
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.197 MPLS_TUNNEL_Excess
Description
The MPLS_TUNNEL_Excess is an alarm indicating that excessive trail termination source identifiers (TTSIs) are received in the tunnel. This alarm occurs when the Ethernet port of the local NE receives five or more correct CV/FFD packets within three consecutive CV/FFD periods.
Attribute
Parameters
None.
A Alarm Reference

Services may be interrupted if excessive redundant packets are received.
Possible Causes
l Cause 1: Physical links are misconnected.
Procedure
Step 1 Cause 1: Physical links are misconnected. 1. Check whether any fiber or cable is misconnected between the two ends. If yes, reconnect the fiber or cable.
----End
Related Information
None.
A.3.198 MPLS_TUNNEL_FDI
Description
The MPLS_TUNNEL_FDI is an alarm of tunnel forward defect indication. This alarm is reported when the local NE receives the forward defect indication (FDI) packet, notifying that the upstream tunnel at the physical layer is faulty.
Attribute
Parameters
None.

When this alarm occurs, services may be interrupted.
Possible Causes
Cause 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.
A Alarm Reference
If... The link-related alarms, such as MW_BER_EXC, MW_BER_SD, MW_FEC_UNCOR and MW_LOF, are reported The transmit board of the local NE reports hardware-related alarms (alarms on the optical modules or boards), such as HARD_BAD and LSR_NO_FITED ----End
Then... Clear these alarms first.
Clear these alarms first.
Related Information
None.
A.3.199 MPLS_TUNNEL_LOCV
Description
The MPLS_TUNNEL_LOCV is an alarm of tunnel connectivity loss. This alarm occurs when the 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, and value.)
Attribute
Parameters
None.

When this alarm occurs, the services that the faulty tunnel carries are interrupted.
Possible Causes
l l l l 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. Cause 2: Severe congestion occurs on the network. Cause 3: A certain board is faulty. 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 type and detection packet period, differ at the two ends.
A Alarm Reference
1. 2.
Check whether the MPLS OAM settings are the same at the two ends. If the MPLS OAM settings are different at the two ends, change them to the same. If... The alarm is cleared The alarm persists Then... End the alarm handling. Go to Cause 2.
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 eliminate the sources that transmit a large amount of invalid data. If... The alarm is cleared The alarm persists 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... The alarm is cleared The alarm persists 2. 3. Then... End the alarm handling. Go to the next step. Then... End the alarm handling. Go to Cause 3.
Check whether the local NE and the remote NE report alarms related to optical modules or boards, such as HARD_BAD and LSR_NO_FITED. If yes, clear these alarms first. Then, check whether the MPLS_TUNNEL_LOCV alarm clears. If... The alarm is cleared The alarm persists Then... End the alarm handling. Go to Cause 4.
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
Related Information
None.
A.3.200 MPLS_TUNNEL_MISMATCH
Description
The MPLS_TUNNEL_MISMATCH is an alarm indicating that the trail termination source identifiers (TTSIs) on the tunnel do not match with the specified one. This alarm is reported if no CV/FFD packets with correct TTSIs are received in three consecutive CV/FFD periods.
A Alarm Reference
Attribute
Parameters
None.

When this alarm occurs, services are interrupted or packets from other tunnels are received.
Possible Causes
l l Cause 1: The tunnel settings are incorrect. For example, the LSR IDs or tunnel IDs differ at the two ends of the tunnel. Cause 2: Physical links are misconnected.
Procedure
Step 1 Cause 1: The tunnel settings are incorrect. For example, the LSR IDs or tunnel IDs differ at the two 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 sink NE 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.
Step 2 Cause 2: Physical links are misconnected. 1. Check whether any fiber or cable is misconnected between the two ends. If yes, connect the fiber or cable properly.
----End
Related Information
None.
A.3.201 MPLS_TUNNEL_MISMERGE
Description
The MPLS_TUNNEL_MISMERGE is an alarm indicating that the trail termination source identifiers (TTSIs) are mismerged in the tunnel. This alarm is reported if the CV/FFD packets with correct TTSIs and those with wrong TTSIs are received in three consecutive CV/FFD periods.
A Alarm Reference
Attribute
Parameters
None.

When this alarm occurs, the packets from other tunnels are received.
Possible Causes
l l Cause 1: Multiple tunnels are configured with the same label. Cause 2: Physical links are misconnected.
Procedure
Step 1 Cause 1: Multiple tunnels are configured with the same label. 1. 2. Check whether multiple tunnels are configured with the same label. If multiple tunnels are configured with the same label, delete the redundant labels or change the label of each tunnel to a unique value.
Step 2 Cause 2: Physical links are misconnected. 1. Check whether any fiber or cable is misconnected between the two ends. If yes, connect the fiber or cable properly.
----End
Related Information
On the NE, the label of each MPLS tunnel is unique.
A.3.202 MPLS_TUNNEL_OAMFAIL
Description
The MPLS_TUNNEL_OAMFAIL is an alarm indicating that the OAM protocol negotiation between the two ends of the tunnel fails.
Attribute
Issue 03 (2012-07-30)
543
A Alarm Reference
Parameters
None.

When this alarm occurs, services are switched to the backup network and the LPT closes the access port of the remote NE at the same time.
Possible Causes
l l Cause 1: The OAM function is enabled and the detection mode is auto-sensing on one end and is disabled on the other end. 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 and is 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 mode is auto-sensing. 1. 2. Check whether the sink node of the alarmed tunnel reports the HARD_BAD, ETH_LOS, or R_LOS alarm. If yes, clear the alarm. After the OAM protocol negotiation succeeds, the MPLS_TUNNEL_OAMFAIL alarm clears.
----End
Related Information
None.
A.3.203 MPLS_TUNNEL_RDI
Description
The MPLS_TUNNEL_RDI is an alarm indicating a defect in the backward direction of a tunnel. The local MEP sends an RDI packet to the remote MEP when detecting a tunnel fault. The MPLS_TUNNEL_RDI alarm is reported when the remote MEP receives the RDI packet.
Attribute
Parameters
None.
A Alarm Reference

When this alarm occurs, services are affected in the transmit direction on the remote MEP.
Possible Causes
The local MEP NE detects a tunnel fault.
Procedure
Step 1 Handle the tunnel fault according to the MPLS-TP OAM-related alarm reported by the remote MEP. Then, check whether the MPLS_TUNNEL_RDI alarm is cleared. Step 2 If the alarm persists, check whether the physical link is faulty between faulty NEs. For example, the optical fiber or cable is damaged or pressed. If yes, replace the faulty optical fiber or cable. ----End
Related Information
None.
A.3.204 MPLS_TUNNEL_SD
Description
The MPLS_TUNNEL_SD is an alarm of signal degrade on the tunnel. This alarm is reported when the packet loss rate of the CV/FFD crosses the SD threshold but is lower than the SF threshold.
Attribute
Parameters
None.

Services degrade and moderate packet loss occurs.
Possible Causes
l l
Issue 03 (2012-07-30)
Cause 1: Excessive bit errors occur. Cause 2: The bandwidth of the tunnel is fully used.
A Alarm Reference
Procedure
Step 1 Cause 1: Excessive bit errors occur. 1. 2. Check whether the FCS_ERR alarm is reported. If yes, clear the FCS_ERR alarm and then check whether the MPLS_TUNNEL_SD alarm is cleared. 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 the faulty tunnel is exhausted, increase the bandwidth or eliminate the sources that transmit a large amount of invalid data. Check whether the alarm clears.
----End
Related Information
None.
A.3.205 MPLS_TUNNEL_SF
Description
The MPLS_TUNNEL_SF is an alarm indicating that the tunnel signal degrades severely. This alarm 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 packets are lost.
Possible Causes
l l Cause 1: Excessive bit errors occur. Cause 2: The bandwidth of the tunnel is fully used.
Procedure
Step 1 Cause 1: Excessive bit errors occur.
A Alarm Reference
1. 2.
On the NMS, check whether the FCS_ERR alarm is reported. If yes, clear the FCS_ERR, and then check whether the MPLS_TUNNEL_SF is cleared. 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 of the tunnel is fully used, increase the bandwidth allocated to the tunnel or eliminate any source that transmits a large amount of invalid data. Check whether the alarm is cleared.
----End
Related Information
None.
A.3.206 MPLS_TUNNEL_UNEXPMEG
Description
The MPLS_TUNNEL_UNEXPMEG is an alarm indicating an error in the tunnel OAM CCM information. This alarm is reported when the sink NE receives a CCM packet with an unexpected MEG ID.
Attribute
Parameters
None.

When this alarm occurs, the sink NE receives CCM packets of other tunnels.
Possible Causes
l l Cause 1: MEG IDs are inconsistent between NEs at both ends of a tunnel. Cause 2: There are multiple tunnels with the same label between the source and sink NEs.
Procedure
Step 1 Cause 1: MEG IDs are inconsistent between NEs at both ends of a tunnel. 1. Check whether PW configurations are consistent between the source and sink NEs. MEG IDs must be set to the same value on NEs at both ends of a tunnel. For details, see Querying MPLS Tunnel Information.
Step 2 Cause 2: There are multiple tunnels with the same label between the source and sink NEs.
A Alarm Reference
1.
Check whether there are multiple tunnels with the same label on the source and sink NEs. If yes, reconfigure labels for tunnels. For details, see Querying MPLS Tunnel Information.
----End
Related Information
None.
A.3.207 MPLS_TUNNEL_UNEXPMEP
Description
The MPLS_TUNNEL_UNEXPMEP is an alarm indicating an error in the tunnel OAM CCM information. This alarm is reported when the sink NE receives a CCM packet with an unexpected MEP ID.
Attribute
Parameters
None.

When this alarm occurs, services are interrupted or the sink NE receives CCM packets of other tunnels.
Possible Causes
MEP IDs are inconsistent between NEs at both ends of the tunnel.
Procedure
Step 1 MEP IDs are inconsistent between NEs at both ends of the tunnel. 1. Check whether the remote MEP ID on the source NE is correctly configured with the MEP ID of the sink NE. If not, reconfigure the remote MEP ID on the source NE.
----End
Related Information
None.
A Alarm Reference
A.3.208 MPLS_TUNNEL_UNEXPPER
Description
The MPLS_TUNNEL_UNEXPPER is an alarm indicating that the tunnel does not receive the CCM packet in the expected period. This alarm is reported when the sink NE of the PW receives a CCM packet with correct MEG level, MEG ID, and MEP ID but in an unexpected period. For example, the transmit interval is set to 10 ms on the source and sink NEs, but the sink NE receives the CCM packet from the source NE after 20 ms.
Attribute
Parameters
None.

When this alarm occurs, services are interrupted or the sink NE receives CCM packets of other tunnels.
Possible Causes
CCM packet periods are inconsistent between the source and sink NEs at both ends of the tunnel.
Procedure
Step 1 CCM packet periods are inconsistent between the source and sink NEs at both ends of the tunnel. 1. Check whether tunnel configurations are consistent between the source and sink NEs. CCM packet periods on NEs at both ends of a PW must be set to the same value. For details, see Querying MPLS Tunnel Information.
----End
Related Information
None.
A.3.209 MPLS_TUNNEL_UNKNOWN
Description
The MPLS_TUNNEL_UNKNOWN is an alarm indicating that certain unknown defects exist on the tunnel. This alarm is reported when the port receives the CV packets and the FFD packets.
A Alarm Reference
Attribute
Parameters
None.

When this alarm occurs, the OAM function is affected.
Possible Causes
l l Cause 1: The OAM settings differ at the two ends. Cause 2: The NE receives packets from an unknown source.
Procedure
Step 1 Cause 1: The OAM settings differ at the two ends. 1. 2. If the MPLS_TUNNEL_UNKNOWN alarm is reported transiently, check whether Tunnel OAM configuration is changed on the local NE and the opposite NE. If the local NE and the opposite NE have different Tunnel OAM configuration, the MPLS_TUNNEL_UNKNOWN alarm is reported transiently and then the MPLS_TUNNEL_LOCV alarm is reported. Ensure that both ends have the same Tunnel OAM configuration. Then, check whether the alarm is cleared.
Step 2 Cause 2: The NE receives packets from an unknown source. 1. 2. Check whether there is any service configured between the NE and an unknown source, or whether the NE is connected to an unknown source. If yes, modify the incorrect configuration or reconnect the fibers.
----End
Related Information
None.
A.3.210 MS_AIS
Description
The MS_AIS is an alarm indicating multiplex section alarms. This alarm is reported when the board detects that bits 6-8 of the K2 byte in the three consecutive frames are 111.
A Alarm Reference
Attribute
Parameters
None.

The services on the line port are interrupted. If the services are configured with protection, protection switching may be triggered.
Possible Causes
l l Cause 1: The transmit unit of the opposite station is faulty. 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... The line board reports the alarm The IF board reports the alarm 2. Then... Replace the line board at the opposite end. Replace the IF board at the opposite end.
Replace the board and then check whether the alarm is cleared. If... The alarm is cleared after the board replacement The alarm persists after the board replacement Then... End the fault handling. Go to the next step.
3.
Replace the system control, cross-connect, and timing board at the opposite end. If... The alarm is cleared after the board replacement The alarm persists after the board replacement Then... End the fault handling. Go to Cause 2.
Step 2 Cause 2: The receive unit of the local site is faulty. 1. Replace the alarmed board.
----End
Related Information
None.
A Alarm Reference
A.3.211 MS_CROSSTR
Description
The MS_CROSSTR is an alarm indicating that a performance indicator of the multiplex section crosses the threshold. This alarm is reported when the board detects that the MS BER performance indicator crosses the preset threshold.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the performance monitoring period: l 0x01: 15 minutes l 0x02: 24 hours Parameter 2, Parameter 3 Parameter 2 is always 0x00. Parameter 3 indicate the ID of a performance event that causes the alarm and has the following meanings: l 0x10: MSBBE l 0x11: MSES l 0x12: MSSES l 0x13: MSFEBBE l 0x14: MSFEES l 0x15: MSFESES l 0x16: MSUAS l 0x17: MSCSES l 0x18: MSFECSES l 0x21: MSFEUAS

A large number of bit errors occur in the services, and the services may be interrupted.
A Alarm Reference
Possible Causes
l l Cause 1: Services are interrupted for a long time. Cause 2: The MS BER performance indicator crosses the preset threshold.
Procedure
Step 1 Cause 1: Services are interrupted for a long time.
NOTE
Handle the alarm as follows if the value of parameter 3 is 0x16:
1. 2.
Check whether fibers are properly connected. If not, connect the fibers again according to planning information. Check whether cross-connections are configured for service ports. If not, configure crossconnections 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 the performance event that crosses the preset threshold. For details, see 8.3.12 Browsing the Performance Event Threshold-Crossing Records. Handle the performance event that crosses the threshold.
2.
----End
Related Information
None.
A.3.212 MS_RDI
Description
The MS_RDI is an alarm indicating that data reception at the remote end of the multiplex section fails. This alarm is reported when the board detects that bits 6-8 of the K2 byte are 110.
Attribute
Parameters
None.

The services on the local site are not affected. The services received by the opposite station, however, are interrupted.
A Alarm Reference
Possible Causes
Cause 1: The local site receives a message from the opposite station, and the message indicates that 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 indicates that data reception at the remote end of the multiplex section fails. 1. Rectify the fault that occurs on the opposite station. The possible alarms are as follows: l MS_AIS l R_LOS l R_LOF l B2_EXC l B2_SD ----End
Related Information
None.
A.3.213 MS_REI
Description
The MS_REI is an alarm indicating that bit errors occur on the remote end of the multiplex section. This alarm is reported when the board detects that the M1 byte is non-zero.
Attribute
Alarm Severity Warning Alarm Type Communication alarm
Parameters
None.

The services on the local site are not affected. The services received by the opposite station, however, has bit errors.
Possible Causes
Cause 1: The local site receives a message from the opposite station, and the message indicates that bit errors occur on the remote end of the multiplex section.
A Alarm Reference
Procedure
Step 1 Cause 1: The local site receives a message from the opposite station, and the message indicates that bit errors occur on the remote end of the multiplex section. 1. Handle the MS_BBE performance event on the port of the opposite station.
----End
Related Information
None.
A.3.214 MSAD_CROSSTR
Description
The MSAD_CROSSTR is an alarm indicating that the adaptation performance indicator of the multiplex section crosses the threshold. This alarm is reported when the board detects that an AU pointer adaptation performance indicator crosses the preset threshold.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the performance monitoring period: l 0x01: 15 minutes l 0x02: 24 hours Parameter 2, Parameter 3 Indicate the ID of a performance event that causes the alarm. l 0x2a: AUPJCHIGH l 0x2b: AUPJCLOW l 0x2c: AUPJCNEW

Bit errors may occur in the services.
A Alarm Reference
Possible Causes
Cause 1: An AU pointer adaptation performance indicator crosses the preset threshold.
Procedure
Step 1 Cause 1: An AU pointer adaptation performance indicator crosses the preset threshold. 1. Check the threshold crossing records of the AU pointer adaptation performance events to find out the performance event that crosses the preset threshold. For details, see 8.3.12 Browsing the Performance Event Threshold-Crossing Records. Handle the performance event that crosses the threshold.
2.
----End
Related Information
None.
A.3.215 MULTI_RPL_OWNER
Description
The MULTI_RPL_OWNER is an alarm indicating that the ring network contains several RPL_OWNER nodes.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1, Parameter 2 Meaning Indicate the ID of the ERPS instance.

The ERPS protection fails and the services configured on the Ethernet ring are interrupted.
Possible Causes
Cause 1: The related data is configured incorrectly.
A Alarm Reference
Procedure
Step 1 Cause 1: The related data is configured incorrectly. 1. Reconfigure the ERPS protection. For details, see Creating Ethernet Ring Protection Instances.
----End
Related Information
The following table describes the meanings of the parameters in the MULTI_RPL_OWNER alarm reported by the EMS6. Name Parameter 1 to Parameter 4 Parameter 5, Parameter 6 Meaning Indicates the port ID. Indicate the ID of the ERPS instance.
A.3.216 MW_AM_TEST
Description
The MW_AM_TEST is an alarm indicating that the IF port is in the AM testing state.
Attribute
Alarm Severity Minor Alarm Type Other alarms
Parameters
None.

The transmission capacity is reduced during the AM test, and services with low priorities may be interrupted.
Possible Causes
l Cause: The AM testing is enabled.
Procedure
Step 1 Cause: The AM testing is enabled. 1. After the AM testing ends, disable the AM testing. ----End
A Alarm Reference
Related Information
None.
A.3.217 MW_BER_EXC
Description
The MW_BER_EXC is an alarm indicating that excessive bit errors occur on the radio link. This alarm is reported when the bit errors on the radio link exceed the specified threshold (10-3 by default).
Attribute
Parameters
None.

When the MW_BER_EXC alarm occurs, the service on the port is interrupted.
Possible Causes
l l l l Cause 1: Signal attenuation on the radio link is very heavy. Cause 2: The transmit unit of the opposite station is faulty. Cause 3: The receive unit of the local site is faulty. 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, determine the abnormality and take proper measures. For details, see Querying the Historical Transmit Power and Receive Power
Issue 03 (2012-07-30)
558
A Alarm Reference
If... The RSL is lower than the receiver sensitivity
Then... Follow the steps: 1. Check the installation of the antenna to ensure that the azimuth of the antenna meets the requirement. 2. Check the antenna direction. Check whether the received signal is from the main lobe. If the antenna direction does not meet the requirement, adjust the antenna in a wide range. 3. Check whether the setting of the polarization direction of the antenna is correct. Adjust the incorrect polarization direction. 4. Check whether the antenna gain at both the transmit and receive ends meets the specifications. Replace the antennas that do not meet the requirement. 5. Check whether any mountain or building obstacle exists in the transmit direction. If yes, contact the network planning department for proper modification of the planning design, hence preventing the block of the mountain or building obstacle.
The RSL is higher than the specified RSL Slow up fading occurs. Follow the steps: of the network. The offset value is tens of 1. Follow instructions in 8.11 Scanning decibels. The duration is from tens of Interfering Signals to scan the frequency seconds to several hours. spectrum around the radio link and check for co-frequency interference and biasfrequency interference. 2. Use a spectrum analyzer to analyze the interference source. 3. Contact the spectrum management department to clear the interference spectrum or change plans to minimize the interference. The RSL is lower than the specified RSL of the network. The offset value is tens of decibels. The duration is from tens of seconds to several hours. Slow down fading occurs. Generally, the radio link may be faulty in both directions, because slow fading is imposed by the transmission path. Contact the network planning department to make the following changes: l Increase the installation height of the antenna. l Reduce the transmission distance. l Increase the antenna gain. l Increase the transmit power.
Issue 03 (2012-07-30)
559
A Alarm Reference
If...
Then...
If the RSL is lower than or higher than Fast fading occurs. Contact the network planning the specified RSL of the network and if department to make the following changes: the duration is from several milliseconds l Adjust the position of the antenna to block the to tens of seconds. reflected wave or make the reflection point fall on the ground that has a small reflection coefficient, therefore reducing the multipath fading. l Adjust the RF configuration to make the links in the 1+1 SD configuration. l If the links are configured with the 1+1 SD protection, adjust the height offset between two antennas to make the receive power of one antenna stronger than the receive power of the other 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.7.7 Setting Loopback for the IF Board. Check whether the fault at the opposite end is rectified after the loopback. If... The fault at the opposite end is not rectified The fault at the opposite end is rectified 2. 3. 4. Then... Replace the IF board. Go to the next step.
Check whether the cable connector is prepared according to the requirement. If any cable connector does not meet the requirement, make a new connector. Check whether the IF cable is wet, broken, or pressed. Replace the cable that does not meet the requirement. Then, check whether the fault at the opposite end is rectified. If... Then...
The fault at the opposite end is not rectified Replace the ODU at the opposite end. The fault at the opposite end is rectified Step 3 Cause 3: The receive unit of the local site is faulty. Locate the fault by looping back the opposite station and excluding the position one by one. Follow the steps: 1. Perform an inloop on the IF port at the local end. For details, see 8.7.7 Setting Loopback for the IF Board. Check whether the fault at the local end is rectified after the loopback. If... Then... End the alarm handling.
The fault at the opposite end is not rectified Replace the IF boardReplace the IDU.
A Alarm Reference
If... The fault at the opposite end is rectified 2. 3. 4.
Then... Go to the next step.
Check whether the cable connector is prepared according to the requirement. If any cable connector does not meet the requirement, make a new connector. Check whether the IF cable is wet, broken, or pressed. Replace the cable that does not meet the requirement. Then, check whether the fault at the opposite end is rectified. If... The fault at the opposite end is not rectified The fault at the opposite end is rectified Then... Replace the ODU at the local end. End the alarm handling.
Step 4 Cause 4: An interference event occurs. 1. Follow instructions in 8.11 Scanning Interfering Signals to scan the frequency spectrum around the radio link and check for co-frequency interference and bias-frequency interference. Use a spectrum analyzer to analyze the interference source. Contact the spectrum management department to clear the interference spectrum or change plans to minimize the interference.
2. 3.
----End
Related Information
None.
A.3.218 MW_BER_SD
Description
The MW_BER_SD is an alarm indicating that signal deteriorates on the radio link. This alarm is 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
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.
A Alarm Reference
Possible Causes
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 Transmit Power and Receive Power Then... Follow the steps: 1. Check the installation of the antenna to ensure that the azimuth of the antenna meets the requirement. 2. Check the antenna direction. Check whether the received signal is from the main lobe. If the antenna direction does not meet the requirement, adjust the antenna in a wide range. 3. Check whether the setting of the polarization direction of the antenna is correct. Adjust the incorrect polarization direction. 4. Check whether the antenna gain at both the transmit and receive ends meets the specifications. Replace the antennas that do not meet the requirement. 5. Check whether any mountain or building obstacle exists in the transmit direction. If yes, contact the network planning department for proper modification of the planning design, hence preventing the block of the mountain or building obstacle.
Issue 03 (2012-07-30)
562
A Alarm Reference
If...
Then...
The RSL is higher than the specified RSL Slow up fading occurs. Follow the steps: of the network. The offset value is tens of 1. Follow instructions in 8.11 Scanning decibels. The duration is from tens of Interfering Signals to scan the frequency seconds to several hours. spectrum around the radio link and check for co-frequency interference and biasfrequency interference. 2. Use a spectrum analyzer to analyze the interference source. 3. Contact the spectrum management department to clear the interference spectrum or change plans to minimize the interference. The RSL is lower than the specified RSL of the network. The offset value is tens of decibels. The duration is from tens of seconds to several hours. Slow down fading occurs. Generally, the radio link may be faulty in both directions, because slow fading is imposed by the transmission path. Contact the network planning department to make the following changes: l Increase the installation height of the antenna. l Reduce the transmission distance. l Increase the antenna gain. l Increase the transmit power. If the RSL is lower than or higher than Fast fading occurs. Contact the network planning the specified RSL of the network and if department to make the following changes: the duration is from several milliseconds l Adjust the position of the antenna to block the to tens of seconds. reflected wave or make the reflection point fall on the ground that has a small reflection coefficient, therefore reducing the multipath fading. l Adjust the RF configuration to make the links in the 1+1 SD configuration. l If the links are configured with the 1+1 SD protection, adjust the height offset between two antennas to make the receive power of one antenna stronger than the receive power of the other 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.7.7 Setting Loopback for the IF Board. Check whether the fault at the opposite end is rectified after the loopback.
Issue 03 (2012-07-30)
563
A Alarm Reference
If...
Then...
The fault at the opposite end is not rectified Replace the IF boardReplace the IDU. The fault at the opposite end is rectified 2. 3. 4. Go to the next step.
The fault at the opposite end is not rectified Replace the ODU at the opposite end. The fault at the opposite end is rectified Step 3 Cause 3: The receive unit of the local site is faulty. Locate the fault by looping back the opposite station and excluding the position one by one. Follow the steps: 1. Perform an inloop on the IF port at the local end. For details, see 8.7.7 Setting Loopback for the IF Board. Check whether the fault at the local end is rectified after the loopback. If... The fault at the opposite end is not rectified The fault at the opposite end is rectified 2. 3. 4. Then... Replace the IF board. Go to the next step. End the alarm handling.
Step 4 Cause 4: An interference event occurs. 1. Check whether any co-channel interference occurs. a. b. Mute the ODU at the opposite end. Check the RSL at the local end. For details, see Configuring a Single-Hop Radio Link. If the RSL exceeds -90 dBm, it indicates that there is co-channel interference that may affect the long-term availability and errored-second performance of the system.
2.
Follow instructions in 8.11 Scanning Interfering Signals to scan the frequency spectrum around the radio link and check for co-frequency interference and bias-frequency interference. Use a spectrum analyzer to analyze the interference source.
3.
Issue 03 (2012-07-30)
A Alarm Reference
4.
Contact the spectrum management department to clear the interference spectrum or change plans to minimize the interference.
----End
Related Information
None.
A.3.219 MW_CFG_MISMATCH
Description
The MW_CFG_MISMATCH is an alarm of configuration mismatch on radio links. This alarm occurs 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
Parameter 1 Indicates the cause of the fault. l 0x01: The number of E1 signals or the E1 timeslot priority at the local end of a radio link is different from that at the other end. 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.
Issue 03 (2012-07-30)
565
A Alarm Reference

When 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 Causes
l l l l l l l l Cause 1: The number of E1 signals or the E1 timeslot priority at the local end of a radio link is different from that at the other end. Cause 2: The AM enabling is different on both ends of a radio link. Cause 3: The 1588 overhead enabling is different on both ends of a radio link. Cause 4: The modulation mode is different on both ends of a radio link. Cause 5: The service mode is different on both ends of a radio link. Cause 6: The IP header compression is different on both ends of a radio link. Cause 7: The air interface compression at L2 or L3 is different. Cause 8: The number of STM-1 signals is different on both ends of a radio link.
Procedure
Step 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 same on both ends of the radio link. For details, see Managing Radio Links. ----End
Related Information
None.
A.3.220 MW_CONT_WAVE
Description
The MW_CONT_WAVE is an alarm of continuous wave. This alarm occurs if the continuous wave is output by the IF board.
Attribute
Parameters
None.

If the continuous wave function is enabled, radio links cannot transmit services.
A Alarm Reference
Possible Causes
l l l Cause 1: The continuous wave function is enabled. Cause 2: The MW_LOF alarm exists on the radio link and an outloop is performed on the IF port or composite port. Cause 3: The IF unit is faulty.
Procedure
Step 1 Cause 1: The continuous wave function is enabled. 1. Disable the continuous wave function. For details, see Setting IF Attributes. Step 2 Cause 2: The MW_LOF alarm exists on the radio link and an outloop is performed on the IF port or composite port. 1. 2. Release the loopback by referring to 8.7.7 Setting Loopback for the IF Board. Clear the MW_LOF alarm.
Step 3 Cause 3: The IF unit is faulty. 1. 6.8 Replacing the IF Board.
----End
Related Information
The continuous wave function tests the frequency stability and frequency consistency and should be disabled after a test is completed.
A.3.221 MW_E1_LOST
Description
The MW_E1_LOST is an alarm indicating that E1 services are lost. When the AM modulation scheme is downshifted, this alarm is reported by the discarded E1 services.
Attribute
Parameters
Issue 03 (2012-07-30)
Meaning Indicates the timeslots of E1 services.

A Alarm Reference

Some E1 services are lost.
Possible Causes
Cause 1: The AM downshifts the modulation scheme.
Procedure
Step 1 Cause 1: The AM downshifts the modulation scheme. 1. Handle the alarm according to AM_DOWNSHIFT. ----End
Related Information
None.
A.3.222 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, HSM channel protection switching may be triggered.
Possible Causes
Procedure
Step 1 Cause 1: Signal attenuation on the radio link is very heavy.
A Alarm Reference
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 Transmit Power and Receive Power Then... Follow the steps: 1. Check the installation of the antenna to ensure that the azimuth of the antenna meets the requirement. 2. Check the antenna direction. Check whether the received signal is from the main lobe. If the antenna direction does not meet the requirement, adjust the antenna in a wide range. 3. Check whether the setting of the polarization direction of the antenna is correct. Adjust the incorrect polarization direction. 4. Check whether the antenna gain at both the transmit and receive ends meets the specifications. Replace the antennas that do not meet the requirement. 5. Check whether any mountain or building obstacle exists in the transmit direction. If yes, contact the network planning department for proper modification of the planning design, hence preventing the block of the mountain or building obstacle.
The RSL is higher than the specified RSL Slow up fading occurs. Follow the steps: of the network. The offset value is tens of 1. Check whether intra-frequency or interdecibels. The duration is from tens of frequency interference exists by scanning seconds to several hours. frequency spectra in microwave channels. For details, see 8.11 Scanning Interfering Signals. 2. Use a spectrum analyzer to analyze the interference source. 3. Contact the spectrum management department to clear the interference spectrum or change plans to minimize the interference.
Issue 03 (2012-07-30)
569
A Alarm Reference
If... The RSL is lower than the specified RSL of the network. The offset value is tens of decibels. The duration is from tens of seconds to several hours.
Then... Slow down fading occurs. Generally, the radio link may be faulty in both directions, because slow fading is imposed by the transmission path. Contact the network planning department to make the following changes: l Increase the installation height of the antenna. l Reduce the transmission distance. l Increase the antenna gain. l Increase the transmit power.
If the RSL is lower than or higher than Fast fading occurs. Contact the network planning the specified RSL of the network and if department to make the following changes: the duration is from several milliseconds l Adjust the position of the antenna to block the to tens of seconds. reflected wave or make the reflection point fall on the ground that has a small reflection coefficient, therefore reducing the multipath fading. l Adjust the RF configuration to make the links in the 1+1 SD configuration. l If the links are configured with the 1+1 SD protection, adjust the height offset between two antennas to make the receive power of one antenna stronger than the receive power of the other 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.7.7 Setting Loopback for the IF Board. Check whether the fault at the opposite end is rectified after the loopback. If... The fault at the opposite end is not rectified The fault at the opposite end is rectified 2. 3. 4. Then... Replace the IF board. Go to the next step.
The fault at the opposite end is not rectified Replace the ODU at the opposite end.
A Alarm Reference
If... The fault at the opposite end is rectified Step 3 Cause 3: The receive unit of the local site is faulty.
Then... End the alarm handling.
Locate the fault by looping back the opposite station and excluding the position one by one. Follow the steps: 1. Perform an inloop on the IF port at the local end. For details, see 8.7.7 Setting Loopback for the IF Board. Check whether the fault at the local end is rectified after the loopback. If... Then...
The fault at the opposite end is not rectified Replace the IF boardReplace the IDU. The fault at the opposite end is rectified 2. 3. 4. Go to the next step.
Step 4 Cause 4: An interference event occurs. 1. 2. 3. 4. Check for co-channel interference. For details, see 8.11 Scanning Interfering Signals. Check for co-channel interference. For details, see 8.11 Scanning Interfering Signals. Use a spectrum analyzer to analyze the interference source. Contact the spectrum management department to clear the interference spectrum or change plans to minimize the interference.
----End
Related Information
None.
A.3.223 MW_LIM
Description
The MW_LIM is an alarm indicating that a mismatched radio link identifier is detected. This alarm is reported if an IF board detects that the link ID in the radio frame overheads is inconsistent with the specified link ID.
Issue 03 (2012-07-30)
571
A Alarm Reference
Attribute
Parameters
None.

After the IDU IF board reports the MW_LIM alarm, the IF board inserts the AIS alarm into the received signal. Then, the services on the radio link are interrupted. If the services are configured with SNCP, protection switching may be triggered.
Possible Causes
l l l l Cause 1: The link ID of the local site does not match with the link ID of the opposite station. Cause 2: The services on other radio links are received due to the incorrect configuration of the radio link receive frequency at the local or opposite station. Cause 3: The antenna receives the radio signals from the other stations, because the direction of the antenna is set incorrectly. 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 a Single-Hop Radio Link. If not, set the link IDs of the two stations to the same value according to the requirements of the networking planning.
Step 2 Cause 2: The services on other radio links are received due to the incorrect configuration of the radio link receive frequency at the local or opposite station. 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 a Single-Hop Radio Link. If not, set the receive and transmit frequencies of the two stations again.
Step 3 Cause 3: The antenna receives radio signals from the other stations, because the direction of the antenna is set incorrectly. 1. Adjust the direction of the antenna and ensure that the antennas at both ends are aligned.
Step 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 Configuring a Single-Hop Radio Link. a. Check whether the settings of XPIC IF board in polarization direction-V and polarization direction-H meet the requirement of the planning.
Issue 03 (2012-07-30)
A Alarm Reference
If... The polarization direction does not meet the requirement of the planning The polarization direction meets the requirement of the planning
Then... Delete the working XPIC group that is configured incorrectly and create the other working XPIC group again. Go to the next step.
b.
Check whether Link ID-V and Link ID-H meet the requirement of the planning. If... The link ID does not meet the requirement of the planning Then... Reset the ID of the radio link of the XPIC IF board according to the planning. For details, see Creating an XPIC Working Group. Go to the next step.
The link ID meets the requirement of the planning
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 board in the polarization direction V of the two ends are interconnected with each other through the radio link in the polarization direction V, and the XPIC IF board in the polarization direction H of the two ends are interconnected with each other through the radio link in the polarization direction H.
----End
Related Information
The MW_LIM alarm is generated due to the inconsistency between the specified link ID and the received link ID. When the MW_LOF alarm is generated on the link, the received link ID is a random value. In this case, the link ID is invalid. The MW_LIM alarm is also suppressed by the MW_LOF alarm.
A.3.224 MW_LOF
Description
The MW_LOF is an alarm indicating that the radio frame is lost.
Attribute
Parameters
None.
A Alarm Reference

The services are interrupted. If the system is configured with protection, protection switching may be triggered.
Possible Causes
l l Cause 1: The other alarms are generated. 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 services, the channel bandwidth and modulation modes at the local site and the opposite station are different. Cause 3: The operating frequency of the ODU at the local site is inconsistent with the operating frequency of the ODU at the opposite station. Cause 4: The transmit unit of the opposite station is faulty. Cause 5: The receive unit of the local site is faulty. Cause 6: The receive power of the ODU is abnormal. Cause 7: An interference event occurs.
l l l l l
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_BAD l VOLT_LOS l IF_CABLE_OPEN l BD_STATUS l RADIO_RSL_LOW l CONFIG_NOSUPPORT l TEMP_ALARM Step 2 Cause 2: In the case of TDM radio services, the IF working modes at the local site and the opposite station are different. In the case of services, the channel bandwidth and 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. For details, see Configuring a Single-Hop Radio Link. If not, reset the working mode of the IF board according to the network planning. In the case of Hybrid radio services, check whether the channel bandwidth and modulation modes are the same at both ends. If not, change the channel bandwidth and modulation modes according to the network planning. For details, see Configuring a Single-Hop Radio Link. Step 3 Cause 3: The operating frequency of the ODU at the local site is inconsistent with the operating frequency 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.
Issue 03 (2012-07-30)
A Alarm Reference
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 the opposite station. Then, set the receive frequency of the local site to the same as the transmit frequency of the opposite station. Check whether any alarms are generated in the equipment of the local site. If yes, take priority to clear them. The relevant alarms are as follows: l HARD_BAD l BD_STATUS l VOLT_LOS l IF_CABLE_OPEN l RADIO_MUTE l RADIO_TSL_HIGH l RADIO_TSL_LOW l TEMP_ALARM
Step 4 Cause 4: The transmit unit of the opposite station is faulty. 1.
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.7.7 Setting Loopback for the IF Board. Check whether the fault at the opposite end is rectified after the loopback. If... The fault at the opposite end is not rectified The fault at the opposite end is rectified b. c. d. Then... Replace the IF board. Go to the next step.
Check whether the cable connector is prepared according to the requirement. If any cable connector does not meet the requirement, make a new connector. Check whether the IF cable is wet, broken, or pressed. Replace the cable that does not meet the requirement. Then, check whether the fault at the opposite end is rectified. If... The fault at the opposite end is not rectified Then... Replace the ODU at the opposite end.
The fault at the opposite end is rectified End the alarm handling. Step 5 Cause 5: The receive unit of the local site is faulty. 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.7.7 Setting Loopback for the IF Board. Check whether the fault at the local end is rectified after the loopback.
Issue 03 (2012-07-30)
A Alarm Reference
If... The fault at the opposite end is not rectified
Then... Replace the IF boardReplace the IDU.
The fault at the opposite end is rectified Go to the next step. b. c. d. 1. Check whether the cable connector is prepared according to the requirement. If any cable connector does not meet the requirement, make a new connector. Check whether the IF cable is wet, broken, or pressed. Replace the cable that does not meet the requirement. Check whether the fault at the local end is rectified.
Step 6 Cause 6: The receive power of the ODU is abnormal. At the local site, check whether the receive power of the ODU is abnormal. For details, see Browse history performance events. If yes, determine the abnormality and take proper measures. Then... Follow the steps: 1. Check the installation of the antenna to ensure that the azimuth of the antenna meets the requirement. 2. Check the antenna direction. Check whether the received signal is from the main lobe. If the antenna direction does not meet the requirement, adjust the antenna in a wide range. 3. Check whether the setting of the polarization direction of the antenna is correct. Adjust the incorrect polarization direction. 4. Check whether the antenna gain at both the transmit and receive ends meets the specifications. Replace the antennas that do not meet the requirement. 5. Check whether any mountain or building obstacle exists in the transmit direction. If yes, contact the network planning department for proper modification of the planning design, hence preventing the block of the mountain or building obstacle.
Issue 03 (2012-07-30)
576
A Alarm Reference
If...
Then...
The RSL is higher than the specified RSL Slow up fading occurs. Follow the steps: of the network. The offset value is tens of 1. Check for co-channel interference. For decibels. The duration is from tens of details, see 8.11 Scanning Interfering seconds to several hours. Signals. 2. Use a spectrum analyzer to analyze the interference source. 3. Contact the spectrum management department to clear the interference spectrum or change plans to minimize the interference. The RSL is lower than the specified RSL of the network. The offset value is tens of decibels. The duration is from tens of seconds to several hours. Slow down fading occurs. Generally, the radio link may be faulty in both directions, because slow fading is imposed by the transmission path. Contact the network planning department to make the following changes: l Increase the installation height of the antenna. l Reduce the transmission distance. l Increase the antenna gain. l Increase the transmit power. If the RSL is lower than or higher than Fast fading occurs. Contact the network planning the specified RSL of the network and if department to make the following changes: the duration is from several milliseconds l Adjust the position of the antenna to block the to tens of seconds. reflected wave or make the reflection point fall on the ground that has a small reflection coefficient, therefore reducing the multipath fading. l Adjust the RF configuration to make the links in the 1+1 SD configuration. l If the links are configured with the 1+1 SD protection, adjust the height offset between two antennas to make the receive power of one antenna stronger than the receive power of the other antenna. l Increase the fading margin. Step 7 Cause 7: An interference event occurs. Follow the steps: 1. 2. 3. Check for co-channel interference. For details, see 8.11 Scanning Interfering Signals. Use a spectrum analyzer to analyze the interference source. Contact the spectrum management department to clear the interference spectrum or change plans to minimize the interference.
----End
A Alarm Reference
Related Information
None.
A.3.225 MW_RDI
Description
The 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
Parameters
None.

If the local site is configured with the reverse switching function, the 1+1 switching is triggered on the IF board when the working and protection IF boards receive the MW_RDI alarm at the same time. This alarm also indicates that the services received by the opposite station are interrupted.
Possible Causes
After detecting a service alarm that is caused by the fault in a radio link, the receive station returns a radio link fault indication to the transmit station.
Procedure
Step 1 Clear the radio alarms that occur at the opposite station. The possible alarms are as follows: l MW_LOF l R_LOF l R_LOC l MW_FEC_UNCOR l XPIC_LOS l MW_BER_SD l MW_BER_EXC ----End
Related Information
None.
A Alarm Reference
A.3.226 NESF_LOST
Description
The NESF_LOST is an alarm indicating that the NE software is lost. This alarm is reported when the system control, cross-connect, and timing board detects that the NE software is lost.
Attribute
Parameters
Issue 03 (2012-07-30)
579
A Alarm Reference
Name
Meaning
Parameter 2, Parameter 3 Indicate the ID of the routine inspection object. l 0x01: FPGA of the system control board in ofs1 l 0x02: FPGA of the system control board in ofs2 l 0x03: ofs1/hwx/nesoft.hwx l 0x04: ofs2/hwx/nesoft.hwx l 0x05: ofs1/hwx/ne.ini l 0x06: ofs2/hwx/ne.ini l 0x07: ofs1/hwx/ocp.ini l 0x08: ofs2/hwx/ocp.ini l 0x09: ofs1/fpga/if1_002.pga l 0x0a: ofs2/fpga/if1_002.pga l 0x0b: ofs1/fpga/if1_250.pga l 0x0c: ofs2/fpga/if1_250.pga l 0x0d: ofs1/fpga/sl1d.pga l 0x0e: ofs2/fpga/sl1d.pga l 0x0f: ofs1/fpga/sl91ifu2.pga l 0x10: ofs2/fpga/sl91ifu2.pga l 0x11: ofs1/fpga/sl91ifx2.pga l 0x12: ofs2/fpga/sl91ifx2.pga l 0x13: ofs1/fpga/sl91aux.pga l 0x14: ofs2/fpga/sl91aux.pga l 0x15: ofs1/hwx/lusoft.hwx l 0x16: ofs2/hwx/lusoft.hwx l 0x17: ofs1/hwx/lusoft.ini l 0x18: ofs2/hwx/lusoft.ini l 0x19: ofs1/fpga/sl91em6t.pga l 0x1a: ofs2/fpga/sl91em6t.pga l 0x1b: ofs1/fpga/pvg610.pga l 0x1c: ofs2/fpga/pvg610.pga l 0x1d: ofs1/fpga/pvg610x.pga l 0x1e: ofs2/fpga/pvg610x.pga l 0x1f: ofs1/hwx/extbios.hwx l 0x20: ofs2/hwx/extbios.hwx l 0x21: ofs1/hwx/luexbios.hwx l 0x22: ofs2/hwx/luexbios.hwx
Issue 03 (2012-07-30)
580
A Alarm Reference
Name Parameter 4
Meaning 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.

If the NE software does not exist in the active and standby areas, an NE cannot be restarted after it is powered off or reset.
Possible Causes
l l l Cause 1: No new NE software is loaded after the existing NE software is erased. Cause 2: Loading the NE software is unsuccessful. 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... The alarm is caused by the loading operation The alarm is not caused by the loading operation Step 2 Cause 3: A certain board is faulty. 1. For details, see 6.10 Replacing the System Control, Switch and Timing Board. Then... Contact the Huawei technical support engineers to reload the software. Go to the next step.
----End
Related Information
None.
A.3.227 NESOFT_MM
Description
The NESOFT_MM is an alarm indicating that the first software system is different from the second software system. This alarm is reported when the NE detects that the first software system and the second software system of the system control, cross-connect, and timing board mismatch with each other.
A Alarm Reference
Attribute
Parameters
Name Parameter 1 Meaning Indicates the location of the file. l 0x01: the files in the flash memory l 0x02: the software that is currently running l 0x03: the software in the CF card
Issue 03 (2012-07-30)
582
A Alarm Reference
Name
Meaning
Parameter 2, Parameter 3 Indicate the IDs of the inconsistent files in the flash memory of the system control board if the value of Parameter 1 is 0x01, l 0x01: FPGA of the system control board in ofs1 l 0x02: FPGA of the system control board in ofs2 l 0x03: ofs1/hwx/nesoft.hwx l 0x04: ofs2/hwx/nesoft.hwx l 0x05: ofs1/hwx/ne.ini l 0x06: ofs2/hwx/ne.ini l 0x07: ofs1/hwx/ocp.ini l 0x08: ofs2/hwx/ocp.ini l 0x09: ofs1/fpga/if1_002.pga l 0x0a: ofs2/fpga/if1_002.pga l 0x0b: ofs1/fpga/if1_250.pga l 0x0c: ofs2/fpga/if1_250.pga l 0x0d: ofs1/fpga/sl1d.pga l 0x0e: ofs2/fpga/sl1d.pga l 0x0f: ofs1/fpga/sl91ifu2.pga l 0x10: ofs2/fpga/sl91ifu2.pga l 0x11: ofs1/fpga/sl91ifx2.pga l 0x12: ofs2/fpga/sl91ifx2.pga l 0x13: ofs1/fpga/sl91aux.pga l 0x14: ofs2/fpga/sl91aux.pga l 0x15: ofs1/hwx/lusoft.hwx l 0x16: ofs2/hwx/lusoft.hwx l 0x17: ofs1/hwx/lusoft.ini l 0x18: ofs2/hwx/lusoft.ini l 0x19: ofs1/fpga/sl91em6t.pga l 0x1a: ofs2/fpga/sl91em6t.pga l 0x1b: ofs1/fpga/pvg610.pga l 0x1c: ofs2/fpga/pvg610.pga l 0x1d: ofs1/fpga/pvg610x.pga l 0x1e: ofs2/fpga/pvg610x.pga l 0x1f: ofs1/hwx/luexbios.hwx l 0x20: ofs2/hwx/luexbios.hwx l 0x21: ofs1/fpga/plc034.pga l 0x22: ofs2/fpga/plc034.pga Indicate the IDs of the inconsistent files in the currently running software if the value of Parameter 1 is 0x02. l 0x01: NeSoft(D)
A Alarm Reference
Name
Meaning l 0x02: Platform(D) l 0x04: ExtBios l 0x05: Logic l 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 on the active and standby system control boards are also inconsistent.

l l This alarm affects active/standby switching of system control boards if the active and standby system control boards have different NE software versions. If no NE software exists in the flash memory, the system is unable to restart after poweroff or reset.
Possible Causes
l l l Cause 1: The software running on the active and standby SCC boards has different versions. Cause 2: The software stored in the ofs1 and ofs2 areas of the active SCC board has different versions. Cause 3: The software stored in the mapping directories of active and standby SCC boards has different versions.
Procedure
Step 1 Contact Huawei technical support engineers for reloading the software. ----End
Related Information
None.
A.3.228 NO_BD_SOFT
Description
The NO_BD_SOFT is an alarm indicating that the board software is lost.
A Alarm Reference
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Parameter 2, Parameter 3 Meaning The value is always 0x01. Indicates the number of the lost file.

l l If the board software is lost, the board fails to work normally. If the FPGA is lost, the FPGA does not have a backup copy.
Possible Causes
Cause 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
Related Information
None.
A.3.229 NP1_MANUAL_STOP
Description
The NP1_MANUAL_STOP is an alarm indicating that the N+1 protection protocol is disabled manually.
Attribute
Issue 03 (2012-07-30)
585
A Alarm Reference
Parameters
Parameter 1, Parameter 2 Indicates the ID of the alarmed protection group. For example, 0x01 indicates that the alarm is reported by protection group 1.

The N+1 protection may fail, or the protection switching may fail.
Possible Causes
Cause 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
Related Information
None.
A.3.230 NP1_SW_FAIL
Description
The NP1_SW_FAIL is an alarm indicating that the N+1 protection switching fails.
Attribute
Parameters
A Alarm Reference
Name
Meaning
Parameter 1, Parameter 2 Indicates the ID of the alarmed protection group. For example, 0x01 indicates that the alarm is reported by protection group 1.

The services cannot be switched. If the current paths are unavailable, the services are interrupted.
Possible Causes
l l Cause 1: The parameters of the N+1 protection for the alarmed node are set incorrectly. 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 are Set the parameters of the N+1 protection set incorrectly correctly. The parameters of the N+1 protection are Go to Cause 2. set correctly 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 is End the alarm handling. restarted. The alarm persists after the protocol is restarted ----End Contact the Huawei technical support engineers to handle the alarm.
Related Information
None.
A.3.231 NP1_SW_INDI
Description
The NP1_SW_INDI is an alarm indicating that the N+1 protection switching is detected.
A Alarm Reference
Attribute
Parameters
Parameter1, Parameter 2 Indicates the ID of the alarmed protection group. For example, 0x01 indicates that the alarm is reported by protection group 1.

During the N+1 protection switching, the services are interrupted. After the N+1 switching is complete, the services are restored to normal. After the switching starts and before the switching is complete, the extra services are interrupted.
Possible Causes
Cause 1: The N+1 protection switching is performed.
Procedure
Step 1 Cause 1: The N+1 protection switching is performed. 1. Find out the cause of switching, and take appropriate measures.
----End
Related Information
None.
A.3.232 NTP_SYNC_FAIL
Description
The NTP_SYNC_FAIL is an alarm indicating that NTP time synchronization fails.
Attribute
Issue 03 (2012-07-30)
588
A Alarm Reference
Parameters
None.

Time on the alarmed NE is different from time on the NTP server. The records on the NE, such as performance events, alarms, and operations, cannot be kept with exact time.
Possible Causes
l l l Cause 1: The NTP server is not configured or is configured incorrectly. Cause 2: The NTP server cannot communicate with the NE. Cause 3: The NTP server fails.
Procedure
Step 1 Cause 1: The NTP server is not configured or is configured incorrectly. 1. 2. Configure the NTP server correctly. Re-configure the NTP parameters for the NE.
Step 2 Cause 2: The NTP server cannot communicate with the NE. 1. 2. Check whether the cable connecting the gateway NE to the NTP server is normal. If not, rectify the connection fault. 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
Related Information
None.
A.3.233 OCD
Description
The OCD is an alarm indicating out-of-cell delimitation. This alarm occurs when the cell delimitation state machine is in the HUNT or PRESYN state.
Attribute
Issue 03 (2012-07-30)
589
A Alarm Reference
Parameters
None.

When the OCD alarm occurs, all the services in the receive direction of the alarmed ATM port lose cells.
Possible Causes
l l 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. Cause 2: The ATM processing chip of the board is faulty.
Procedure
Step 1 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. 1. 2. 1. 2. Check whether the B1_EXC, B2_EXC, or B3_EXC alarm occurs in the receive path. If yes, clear these alarms first, and then check whether the OCD alarm is cleared. Perform a cold reset on the board that reports the OCD alarm. For details, see 8.8.1 Cold Reset. If the OCD alarm persists, replace the alarmed board. For details, see 6.6 Replacing the Smart E1 Interface Board.
Step 2 Cause 2: The ATM processing chip of the board is faulty.
----End
Related Information
None.
A.3.234 ODC_BATTERY_CURRENT_ABN
Description
The ODC_BATTERY_CURRENT_ABN is an alarm indicating that the current of the storage battery is abnormal.
Attribute
Parameters
A Alarm Reference
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the cause of the alarm. 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.

The equipment may fail to work normally, or event the equipment is damaged.
Possible Causes
l l l l l Cause 1: The circuit breaker or fuse of the storage battery in the cabinet is off. Cause 2: The positive and negative polarities of the storage battery are connected inversely. Cause 3: The power module frame is faulty. Cause 4: The power monitoring module is faulty. 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... The circuit breaker of the storage battery is open The fuse of the storage battery is broken Then... Close the circuit breaker. 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 solution to the ODC_MDL_ABN alarm.
A Alarm Reference
If... The ODC_MDL_ABN alarm is not reported ----End
Then... Replace the power module.
Related Information
None.
A.3.235 ODC_BATTERY_PWRDOWN
Description
The ODC_BATTERY_PWRDOWN is an alarm indicating that the storage battery fails to provide power for the equipment.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the cause of the alarm. l 0x01: power-off due to low voltage l 0x02: power-off due to NMS control l 0x03: power-off due to human interference l 0x04: power-off due to high temperature

The equipment does not have backup a power supply.
Possible Causes
l l Cause 1 of power-off due to NMS control: The storage battery fails to provide power for the equipment due to NMS control. Cause 1 of power-off due to local human interference: The BAT button on the front panel of the PMU is set to OFF.
Issue 03 (2012-07-30)
A Alarm Reference
l l l l l l
Cause 1 of power-off due to low voltage: The AC input power is abnormal. Cause 2 of power-off due to low voltage: The power module is faulty. Cause 3 of power-off due to low voltage: The power monitoring module is faulty. 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. Cause 2 of power-off due to high temperature: The temperature of the storage battery is very high. 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 the equipment due to NMS control. 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 the PMU 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 planning information. If... The threshold is inappropriate The threshold is appropriate 2. Then... Set the threshold to an appropriate value. Go to the next step.
Check whether the AC circuit breaker is closed. If... The AC circuit breaker is open The AC circuit breaker is closed Then... Close the AC circuit breaker. Go to the next step.
3.
Check the connection of the AC power cable. If... The connection of the AC power cable is incorrect. The AC power cable is deteriorated and damaged. Then... Connect the cable properly. 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.
A Alarm Reference
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 the power 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 planning information. If... Then...
The threshold is inappropriate Set the threshold to an appropriate value. The threshold is appropriate Perform the operations required when the alarm is generated by cause 2 of power-off due to high temperature.
Step 8 Cause 2 of power-off due to high temperature: The temperature of the storage battery is very high. 1. Replace the storage battery.
Step 9 Cause 3 of power-off due to high temperature: The temperature sensor of the power module is faulty. 1. Replace the temperature sensor of the power module.
----End
Related Information
None.
A.3.236 ODC_DOOR_OPEN
Description
The ODC_DOOR_OPEN is an alarm indicating that the door of an outdoor cabinet is open.
Attribute
Parameters
None.

If the cabinet door is open, the temperature, ambient humidity, and dust-proof measures of the equipment are affected by the external environment. In addition, the equipment may be damaged or stolen.
A Alarm Reference
Possible Causes
l l l l l l Cause 1: The door access alarm is set incorrectly. Cause 2: The cabinet door is open. Cause 3: The cable between the door sensor and the monitor device is connected incorrectly. Cause 4: The door sensor is faulty. Cause 5: The monitor device is faulty. 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... The door access alarm is set correctly The door access alarm is set incorrectly Step 2 Cause 2: The cabinet door is open. 1. Close the cabinet door. Then... Go to Cause 2. Set the door access alarm correctly.
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... The cable is connected incorrectly or is loose The cable is deteriorated or damaged The connection is correct Step 4 Cause 4: The door sensor is faulty. 1. 2. Rectify the fault of the door sensor. Then, check whether the alarm clears. If... The alarm clears The alarm persists Step 5 Cause 5: The monitor device is faulty. 1. Rectify the fault of the monitor device. Then... End the alarm handling. Go to Cause 5. Then... Connect the cable properly. Replace the cable. Go to Cause 4.
Step 6 Cause 6: No door sensor is installed. 1. Install a door sensor.
----End
A Alarm Reference
Related Information
None.
A.3.237 ODC_FAN_FAILED
Description
The ODC_FAN_FAILED is an alarm indicating that the fan is faulty.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning 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 the services may be affected.
Possible Causes
l l l Cause 1: The fan cable is connected incorrectly. Cause 2: The fan is faulty. 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.
Issue 03 (2012-07-30)
Replace the fan module.

A Alarm Reference
Step 4 Cause 3: The fan is not installed. 1. Install the TEC module that contains a fan.
----End
Related Information
None.
A.3.238 ODC_HUMI_ABN
Description
The ODC_HUMI_ABN is an alarm indicating that the relative humidity in the cabinet environment exceeds the specified threshold.
Attribute
Alarm Severity Minor Alarm Type Environment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the cause of the alarm. 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 relative humidity, the life of the equipment may be shortened.
Possible Causes
l l l l
Issue 03 (2012-07-30)
Cause 1: The threshold that results in an alarm is set incorrectly. Cause 2: The cable between the humidity sensor and the monitoring equipment is connected incorrectly. Cause 3: The humidity sensor is faulty. Cause 4: The associated monitoring equipment is faulty.
A Alarm Reference
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 and planning information. If... The humidity threshold is set correctly Then... Perform the operations required when the alarm is generated due to cause 2.
The humidity threshold is set incorrectly Set the humidity threshold to an appropriate value. Step 2 Cause 2: The cable between the humidity sensor and the monitoring equipment is connected incorrectly. If... Then...
The cable is connected incorrectly or is loose Connect the cable properly. The cable is deteriorated and damaged The cable is not deteriorated and damaged Handle the exceptions of the cable. Perform the operations required when the alarm is generated due to cause 3.
Step 3 Cause 3: The humidity sensor is faulty. 1. 2. Rectify the fault of the sensor. Check whether the alarm is cleared. If... Then...
The alarm is cleared End the alarm handling. The alarm persists Perform the operations required when the alarm is generated due to cause 4.
Step 4 Cause 4: The monitoring equipment is faulty. 1. Rectify the fault of the monitoring equipment.
----End
Related Information
None.
A.3.239 ODC_LOAD_PWRDOWN
Description
The ODC_LOAD_PWRDOWN is an alarm indicating that the secondary load is powered off.
Issue 03 (2012-07-30)
598
A Alarm Reference
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the cause of the alarm. l 0x01: power-off due to low voltage l 0x02: power-off due to background control l 0x03: power-off due to startup in the case of low temperature l 0x04: power-off due to high temperature

The services on the secondary load are interrupted.
Possible Causes
l l l l l l l l l Cause 1 of power-off due to NMS control: The load is powered off due to NMS control. Cause 1 of power-off due to low voltage: The AC input power is abnormal. Cause 2 of power-off due to low voltage: The power module is faulty. Cause 3 of power-off due to low voltage: The power monitoring module is faulty. Cause 1 of power-off due to low temperature: The cabinet temperature is very low. Cause 2 of power-off due to low temperature: The ambient temperature sensor is faulty. 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. Cause 2 of power-off due to high temperature: The cabinet temperature is very high. 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. 1. Turn on the storage battery for the equipment. 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 planning information.
Step 3 Cause 1 of power-off due to low voltage: The AC input power is abnormal.
Issue 03 (2012-07-30)
A Alarm Reference
If... The threshold is inappropriate The threshold is appropriate 2.
Then... Set the threshold to an appropriate value. Go to the next step.
Check whether the AC circuit breaker is closed. If... The AC circuit breaker is closed The AC circuit breaker is open Then... Go to the next step. Close the AC circuit breaker.
3.
Check the connection of the AC power cable. If... The connection of the AC power cable is incorrect. The AC power cable is deteriorated and damaged. Then... Connect the cable properly. 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 the ODC_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... The heat exchanger does not work properly The heat exchanger works properly Then... Rectify the fault of the heat exchange. Perform the operations required when the alarm is generated by cause 2 of power-off due 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 the load 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 temperature of the load. Then, determine whether the threshold is appropriate according to the configuration and planning information. If... Then...
The threshold is inappropriate Set the threshold to an appropriate value.
Issue 03 (2012-07-30)
600
A Alarm Reference
If... The threshold is appropriate
Then... Perform the operations required when the alarm is generated by cause 2 of power-off due to high temperature.
Step 9 Cause 2 of power-off due to high temperature: The cabinet temperature is very high. 1. 2. Check whether the ambient temperature is very high all the time. Check whether the heat exchanger works properly. If... The heat exchanger does not work properly The heat exchanger works properly Then... Rectify the fault of the heat exchange. Perform the operations required when the alarm is generated by cause 3 of power-off due 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 Information
The secondary load refers to the load that the DC power outlet of the cabinet corresponds to.
A.3.240 ODC_MDL_ABN
Description
The ODC_MDL_ABN is an alarm indicating that the power module is abnormal.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the ID of the alarmed power module.
Issue 03 (2012-07-30)
601
A Alarm Reference
Name
Meaning
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 number of PSUs configured on the NMS is incorrect. l 0x06: The power module status cannot be identified.

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 powered off.
Possible Causes
l l l l Cause 1: The number of PSUs configured on the NMS is incorrect. Cause 2: The power module is not in position. Cause 3: The power module is faulty. 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... The power module is not in position The power module is not inserted securely Step 3 Cause 3: The power module is faulty. 1. Replace the power module. Then... Install the power module. Install the power module properly.
Step 4 Cause 4: The power monitoring unit is abnormal. 1. Rectify the fault of the power monitoring unit.
----End
Related Information
None.
A Alarm Reference
A.3.241 ODC_POWER_FAIL
Description
The ODC_POWER_FAIL is an alarm indicating that the AC input power voltage and DC output power voltage of an outdoor cabinet are abnormal.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning 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.

l l If the AC input power voltage is abnormal, the equipment is powered on by the storage battery and cannot work for a long time. If the DC output power voltage is abnormal, the services on the equipment are interrupted.
Possible Causes
l l Cause 1: The AC input power voltage is abnormal. 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.
Issue 03 (2012-07-30)
603
A Alarm Reference
If... The threshold is set incorrectly The threshold is set correctly 2. The AC circuit breaker is open. If... The AC circuit breaker is open The AC circuit breaker is closed 3.
Then... Close the AC circuit breaker. Go to the next step.
The AC power cable is connected incorrectly. If... The cable is connected incorrectly or is loose The cable is deteriorated and damaged The cable is connected correctly Then... Connect the cable properly. Handle the exceptions of the cable. Go to the next step.
4.
The AC power grid distributes the power abnormally. If... The AC power grid distributes the power abnormally The AC power grid distributes the power normally Then... Rectify the fault of the power module at the base station. Go to the next step.
5.
The monitoring equipment is faulty. If... The monitoring equipment is faulty Then... Rectify the fault of the monitoring equipment.
The monitoring equipment is not faulty Perform the operations required when the alarm 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... The threshold is set incorrectly The threshold is set correctly 2. The PSU module is faulty. If... The PSU module is faulty The PSU module is not faulty 3.
Issue 03 (2012-07-30)
Then... Rectify the fault of the PSU module. Go to the next step.
The power of the storage battery is insufficient.

A Alarm Reference
If... The power of the storage battery is insufficient The power of the storage battery is sufficient ----End
Then... Recharge the storage battery. Rectify the fault of the monitoring equipment.
Related Information
None.
A.3.242 ODC_SMOKE_OVER
Description
The ODC_SMOKE_OVER is an alarm indicating that smoke occurs in an outdoor cabinet.
Attribute
Alarm Severity Critical Alarm Type Environment alarm
Parameters
None.

The equipment may be burned.
Possible Causes
l l l l l Cause 1: The smoke alarm is set incorrectly. Cause 2: A fire and heavy smoke occur at the equipment in the cabinet. Cause 3: The cable between the smoke sensor and the monitoring equipment is connected incorrectly. Cause 4: The smoke sensor is faulty. Cause 5: The associated monitoring equipment 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 planning information.
Issue 03 (2012-07-30)
A Alarm Reference
If... The smoke alarm is set correctly
Then... Perform the operations required when the alarm 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 connected incorrectly. 1. Check whether the cable between the sensor and the monitoring equipment is connected correctly. If... The cable is connected incorrectly or is loose The cable is deteriorated and damaged Then... Connect the cable properly. Replace the cable.
The cable is not deteriorated and damaged Perform the operations required when the alarm is generated due to cause 4. Step 4 Cause 4: The smoke sensor is faulty. 1. 2. Rectify the fault of the sensor. Check whether the alarm is cleared. 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.243 ODC_SURGE_PROTECTION_FAIL
Description
The ODC_SURGE_PROTECTION_FAIL is an alarm indicating that the surge protection function of the outdoor cabinet is abnormal.
Issue 03 (2012-07-30)
606
A Alarm Reference
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the type of the alarm. l 0x01: AC surge protection alarm l 0x02: DC surge protection alarm

The AC surge protection function of the cabinet is disabled.
Possible Causes
l l l l l Cause 1: The alarm is set incorrectly. Cause 2: The cable between the lightning sensor and the monitoring equipment is connected incorrectly. Cause 3: The lightning sensor is faulty. Cause 3: The lightning arrestor is faulty. Cause 5: The associated monitoring equipment 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 planning information. If... The alarm is set correctly Then... Perform the operations required when the alarm is generated 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 connected incorrectly. 1.
Issue 03 (2012-07-30)
Check the cable connection between the sensor and the monitoring equipment.
A Alarm Reference
If... The cable is connected incorrectly or is loose The cable is deteriorated and damaged
Then... Connect the cable properly. Replace the cable.
The cable is not deteriorated and damaged Perform the operations required when the alarm is generated due to cause 3. Step 3 Cause 3: The lightning sensor is faulty. 1. 2. Rectify the fault of the sensor. Check whether the alarm is cleared. 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... The alarm output end of the lightning arrestor works properly The alarm output end of the lightning arrestor does not work properly Then... Perform the operations required when the alarm is generated due to cause 5. Replace the lightning arrestor.
Step 5 Cause 5: The associated monitoring equipment is faulty. 1. Rectify the fault of the monitoring equipment.
----End
Related Information
None.
A.3.244 ODC_TEC_ALM
Description
The ODC_TEC_ALM is an alarm indicating that the TEC air conditioning module in the cabinet does not work properly.
Attribute
Issue 03 (2012-07-30)
608
A Alarm Reference
Parameters
None.

If the TEC air conditioning module does not work properly, the storage battery may operate at very high or low temperature and therefore the safety performance of the storage battery degrades.
Possible Causes
l l l Cause 1: The TEC cable is connected incorrectly. Cause 2: The TEC module is faulty. Cause 3: The monitoring equipment is faulty.
Procedure
Step 1 Cause 1: The TEC cable is connected incorrectly. 1. 1. 1. Connect the TEC cable correctly. Replace the TEC module. Rectify the fault of the monitoring equipment. Step 2 Cause 2: The TEC module is faulty. Step 3 Cause 3: The monitoring equipment is faulty. ----End
Related Information
None.
A.3.245 ODC_TEMP_ABN
Description
The ODC_TEMP_ABN is an alarm indicating that the ambient temperature of the cabinet or the temperature of the storage battery is abnormal.
Attribute
Parameters
A Alarm Reference
Name Parameter 1
Meaning Indicates the cause of the alarm. l 0x01: The ambient temperature is higher than the upper threshold. l 0x01: The ambient temperature is lower than the lower threshold.
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.

If the temperature is abnormal, the equipment performance degrades and the life of the equipment decreases.
Possible Causes
l l l l Cause 1: The temperature threshold that results in an alarm is set incorrectly. Cause 2: The cable between the temperature sensor and the monitoring equipment is connected incorrectly. Cause 3: The temperature sensor is faulty. 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... The temperature alarm is set correctly Then... Perform the operations required when the 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 connected incorrectly. 1. Check whether the cable between the sensor and the monitoring equipment is connected correctly. If... The cable is connected incorrectly or is loose The cable is deteriorated and damaged
Issue 03 (2012-07-30)
Then... Connect the cable properly. Handle the exceptions of the cable.
610
A Alarm Reference
If...
Then...
The cable is not deteriorated and damaged Perform the operations required when the alarm is generated due to cause 3. Step 3 Cause 3: The temperature sensor is faulty. 1. 2. Rectify the fault of the sensor. Check whether the alarm is cleared. If... Then...
Step 4 Cause 4: The monitoring equipment is faulty. 1. Rectify the fault of the monitoring equipment.
----End
Related Information
None.
A.3.246 ODC_WATER_ALM
Description
The ODC_WATER_ALM is an alarm indicating that certain water enters the cabinet.
Attribute
Alarm Severity Critical Alarm Type Environment alarm
Parameters
None.

The moisture in the cabinet increases, and the equipment in the cabinet may be damaged.
Possible Causes
l l l l
Issue 03 (2012-07-30)
Cause 1: The water alarm is set incorrectly. Cause 2: Certain water enters the cabinet. Cause 3: The cable between the water sensor and the monitoring equipment is connected incorrectly. Cause 4: The water sensor is faulty.
A Alarm Reference
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. If... The water alarm is set correctly Then... Perform the operations required when the alarm 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. 1. Dry the cabinet and take waterproof measures for the cabinet. Check whether the cable between the sensor and the monitoring equipment is connected correctly. If... The cable is connected incorrectly or is loose The cable is deteriorated and damaged Then... Connect the cable properly. Handle the exceptions of the cable. Step 3 Cause 3: The cable between the sensor and the monitoring equipment is connected incorrectly.
The cable is not deteriorated and damaged Perform the operations required when the alarm is generated due to cause 4. Step 4 Cause 4: The sensor is faulty. 1. 1. Rectify the fault of the sensor. Rectify the fault of the monitoring equipment. Step 5 Cause 5: The monitoring equipment is faulty. ----End
Related Information
None.
A.3.247 OUT_PWR_ABN
Description
The OUT_PWR_ABN alarm indicates that the output optical power is abnormal.
Issue 03 (2012-07-30)
612
A Alarm Reference
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the port ID.
Parameter 2, Parameter 3 Indicate the path ID. The parameters have a fixed value of 0x00 0x01. Parameter 4, Parameter 5 Are reserved. The value is always 0xFF.

The OUT_PWR_ABN alarm affects the transmission performance of services, and may even result in service interruption.
Possible Causes
l l Cause 1: The output optical power is too high or low. 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 the Replace the optical module. requirement The output optical power is too high Step 2 Cause 2: A board is faulty. 1. Replace the alarmed board. Add a proper attenuator to reduce the input optical power.
----End
Related Information
None.
A Alarm Reference
A.3.248 OUT1TEMP_SENSOR_FAIL
Description
The OUT1TEMP_SENSOR_FAIL is an alarm indicating that the air outlet temperature sensor of the cabinet fails.
Attribute
Parameters
None.

The air outlet temperature data of the TCU cannot be collected.
Possible Causes
l l l l Cause 1: The air outlet temperature sensor is faulty. Cause 2: The control board of the cabinet is faulty. Cause 3: Cables are misconnected or damaged. Cause 4: The air outlet temperature sensor is not installed.
Procedure
Step 1 Cause 1: The air outlet temperature sensor is faulty. 1. 2. Replace the air outlet temperature sensor. Then, check whether the alarm clears. If... The alarm clears The alarm persists Then... End the alarm handling. Go to Cause 2.

A Alarm Reference
1. 2. 1.
Replace damaged cables. Connect cables correctly. Install the air outlet temperature sensor.
Step 4 Cause 4: The air outlet temperature sensor is not installed.
----End
Related Information
None.
A.3.249 OUT2TEMP_SENSOR_FAIL
Description
The OUT2TEMP_SENSOR_FAIL is an alarm indicating that the external cycling air outlet temperature sensor of the cabinet fails.
Attribute
Parameters
None.

The external cycling air outlet temperature data of the TCU cannot be collected.
Possible Causes
l l l l Cause 1: The external cycling air outlet temperature sensor is faulty. Cause 2: The control board of the cabinet is faulty. Cause 3: Cables are misconnected or damaged. 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. 2. Replace the external cycling air outlet temperature sensor. Then, check whether the alarm clears. If... The alarm clears The alarm persists
Issue 03 (2012-07-30)

615
A Alarm Reference
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.250 PASSWORD_NEED_CHANGE
Description
The PASSWORD_NEED_CHANGE alarm indicates that the password of the user who logs in is unchanged. This alarm is reported if any one default user's default password is not changed in time.
Attribute
Parameters
None.

The default user's default password must be changed to reduce risks.
Possible Causes
Cause 1: The default user's default password must be changed to reduce risks.
Issue 03 (2012-07-30)
616
A Alarm Reference
Procedure
Step 1 Modify the default user's password. ----End
Related Information
None.
A.3.251 PATCH_ACT_TIMEOUT
Description
The PATCH_ACT_TIMEOUT is an alarm indicating that activating the patch package times out. This alarm occurs when the patch package is in the active state for a period longer than the specified 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 of time.
Procedure
Step 1 Cause: The patch package is in the active state for a period longer than the specified period of time. 1. 2. Check whether the activated patch package is normal. If yes, run the patch package to make the it valid. If not, delete the patch package. Then, the alarm is cleared automatically.
----End
Related Information
None.
A Alarm Reference
A.3.252 PATCH_DEACT_TIMEOUT
Description
The PATCH_DEACT_TIMEOUT is an alarm indicating that deactivating the patch package times out. This alarm occurs when the patch package is in the inactive state for a period longer than the specified period of time. In this case, the user needs to process the patch package.
Attribute
Parameters
None.

When the PATCH_DEACT_TIMEOUT alarm occurs, it does not affect services.
Possible Causes
Cause: The patch package is in the inactive state for a period longer than the specified period of time.
Procedure
Step 1 Cause: The patch package is in the inactive state for a period longer than the specified period of time. 1. 2. To make the patch package valid, activate the patch package. Otherwise, delete the patch package. Then, the alarm is cleared automatically.
----End
Related Information
None.
A.3.253 PATCH_PKGERR
Description
The PATCH_PKGERR alarm indicates that a patch package is incorrect or has been damaged or deleted.
A Alarm Reference
Attribute
Alarm Severity Minor alarm Alarm Type Equipment alarm
Parameters
None.

If a patch package is incorrect or has been damaged or deleted, the patch package cannot be successfully loaded, activated, or run.
NOTE
When this alarm is reported, services are not interrupted.
Possible Causes
l l l Cause 1: A patch package is incorrect. Cause 2: A patch package has been damaged. Cause 3: A patch package has been deleted.
Procedure
Step 1 Load a correct patch package. ----End
Related Information
None.
A.3.254 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.
A Alarm Reference

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 Querying the IF 1+1 Protection Status.
NOTE
When alarms with different priorities occur on a board at the same time, the board reports only the alarms with 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.255 PG_PRT_DEGRADED
Description
The PG_PRT_DEGRADED is an alarm indicating that the main link or standby link in a 1+1 protection group is faulty.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the board ID.

The services at the NE are not affected, but radio link protection fails.
A Alarm Reference
Possible Causes
l l Cause 1: Service alarms occur on the main board. 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 Querying the IF 1+1 Protection Status.
NOTE
When service alarms with different priorities occur on a board at the same time, the board reports only the alarms 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
Related Information
None.
A.3.256 PLA_CFG_MISMATCH
Description
The PLA_CFG_MISMATCH alarm indicates that the PLA configuration data is inconsistent between two ends of a radio link.
Attribute
Parameters
Parameter 1, Parameter 2 Indicate the ID of a PLA group.
Issue 03 (2012-07-30)
621
A Alarm Reference
Name
Meaning
Parameter 3, Parameter 4 Indicate the error type. l 0x00: indicates that no PLA group is configured at the opposite end of a radio link. l 0x01: indicates that the enabled status of Layer 2 header compression function at the local end of a radio link is different from that at the opposite end. l 0x02: indicates that the enabled status of Layer 3 header compression function at the local end of a radio link is different from that at the opposite end.

Services at both ends of a radio link are unavailable.
Possible Causes
l l Cause 1: A PLA group is configured at the local end but no PLA group is configured at the opposite end. Cause 2: The enabled status of the header compression function at the local end of a 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 the opposite end. 1. Follow instructions in Creating a PLA Group to configure a PLA group at the opposite end of the radio link.
Step 2 Cause 2: The enabled status of the header compression function at the local end of a radio link is different from that at the opposite end. 1. 2. Follow instructions in Querying the PLA Group Status to determine the ports whose configuration data needs to be changed according to planning information. Follow instructions in Setting the Advanced Attributes of IF_ETH Ports to change the enabled status of the header compression function for PLA member ports.
----End
Related Information
None.
A.3.257 PORTMODE_MISMATCH
Description
The PORTMODE_MISMATCH is an alarm indicating that the working mode of the remote FE port does not match with that of the local FE port. This alarm is reported when the local FE port works in auto-negotiation mode and the opposite FE port works in non-auto-negotiation mode.

NOTE
A Alarm Reference
Both GE and FE ports support the PORTMODE_MISMATCH alarm.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1, Parameter 2 Meaning Indicate the working mode of the FE port.

When the PORTMODE_MISMATCH alarm occurs, the service on the local NE is not affected.
Possible Causes
l Cause 1: The local port works in auto-negotiation mode and the opposite port works in nonauto-negotiation mode.
Procedure
Step 1 Cause 1: The local port works in auto-negotiation mode and the opposite port works in nonauto-negotiation mode. 1. 2. Disable the opposite port. For details, refer to Setting the Basic Attributes of Ethernet Ports. Enable the opposite port and set work mode of the port to auto-negotiation. For details, refer to Setting the Basic Attributes of Ethernet Ports.
----End
Related Information
None.
A.3.258 PORT_EXC_TRAFFIC
Description
The PORT_EXC_TRAFFIC alarm indicates that the traffic over a port exceeds its threshold.
A Alarm Reference
Attribute
Parameters
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.

Services are congested.
Possible Causes
l l Cause 1: The configured bandwidth limit is too low. Cause 2: The port traffic is too high.
Procedure
Step 1 Cause 1: The configured bandwidth limit is too low. 1. 2. Follow instructions in Configuring Traffic Shaping for Egress Queues to check the configured bandwidth limit. 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 network expansion.
Step 2 Cause 2: The configured port traffic is too high. 1. 2. Follow instruction in 8.20 Querying Traffic, Physical Bandwidth, or Bandwidth Utilization to query the bandwidth utilization over a port. 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 of invalid data.
----End
Related Information
None.
A Alarm Reference
A.3.259 PORT_MODULE_OFFLINE
Description
The PORT_MODULE_OFFLINE alarm indicates that a port is offline.
Attribute
Parameters
Name Parameter 1 Parameter 2, Parameter 3 Parameter 4, Parameter 5 Meaning Indicates the ID of the port that reports the alarm. Have a fixed value of 0x00 0x01. 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... The alarmed port needs to receive/ transmit a service Then... Go to the next step.
The alarm port does not need to receive/ Follow instructions in Setting the Basic transmit a service Attributes of Ethernet Ports to disable the alarmed port. 2. Check whether the alarmed port houses an SFP module. If... The alarmed port houses no SFP module The alarmed port houses an SFP module
Issue 03 (2012-07-30)
Then... Follow instructions in Installing an SFP Module to add an SFP module. Go to the next step.
625
A Alarm Reference
3.
Re-install the SFP module. If... The alarm clears Then... No further action is required.
The alarm persists Follow instructions in Replacing an SFP Module to replace the SFP module. ----End
Related Information
None.
A.3.260 POWER_ABNORMAL
Description
The POWER_ABNORMAL is an alarm indicating that the input power supply is abnormal.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the number of the voltage channel. l 0x01: the first channel of voltage l 0x02: the second channel of voltage Parameter 2 Indicates the type of the alarm. l 0x00: voltage loss l 0x01: undervoltage l 0x02: overvoltage

When the POWER_ABNORMAL alarm occurs, the power supply is abnormal, and therefore the board may fail to work normally.
A Alarm Reference
Possible Causes
l l Cause 1: The power cable is cut, damaged, or incorrectly connected. 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 is incorrectly 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
Related Information
None.
A.3.261 POWER_ALM
Description
The POWER_ALM is an alarm indicating that the power module is abnormal.
Attribute
Parameters
Parameter 1 If the POWER_ALM alarm is reported on a board on the IDU, this parameter indicates the ID of the alarmed power module. For example, 0x01 indicates that the alarm is reported by power module 1 of the board. If the POWER_ALM is reported on the ODU, this parameter indicates the type of the power fault. l 0x01: The -5 V power supply is faulty. l 0x02: The power supply for the power amplifier is faulty.
Issue 03 (2012-07-30)
627
A Alarm Reference
Name
Meaning l 0x01: under-voltage l 0x02: over-voltage
Parameter 2 Indicates the alarm types.

The power modules are configured with protection. If only one power module reports the POWER_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 l l Cause 1: The input power or the PIU is abnormal. Cause 2: The power module is abnormal. Cause 1: The power module of the ODU is faulty.
If the alarm is reported on the ODU, the cause is as follows:
Procedure
Step 1 (POWER_ALM reported by a board of the IDU) Cause 1: The input power or the PIU is abnormal. 1. 1. 1. Check whether alarms are reported on the PIU, If yes, clear these alarms immediately. Replace the alarmed board. For details, see 6 Part Replacement. Replace the ODU. For details, see 6.15 Replacing the ODU. Step 2 (POWER_ALM reported by a board of the IDU) Cause 2: The power module is abnormal. Step 3 (POWER_ALM reported on the ODU) Cause 1: The power module of the ODU is faulty. ----End
Related Information
None.
A.3.262 PPP_LCP_FAIL
Description
The PPP_LCP_FAIL is an alarm indicating an LCP negotiation failure. This alarm is reported when the port uses the PPP encapsulation type and fails to negotiate with the opposite port.
Issue 03 (2012-07-30)
628
A Alarm Reference
Attribute
Parameters
None.

When this alarm occurs, the LCP negotiation fails and services are interrupted.
Possible Causes
l l l Cause 1: Parameter configurations on the opposite port are inconsistent with those on the local port. Cause 2: The network is congested or its quality is poor, which causes improper running of the LCP protocol. Cause 3: The physical link is interrupted.
Procedure
Step 1 Cause 1: Parameter configurations on the opposite port are inconsistent with those on the local port. 1. 2. 3. On the NMS, check whether parameter configurations on the peer port are consistent with those on the local port. If the parameter configurations are inconsistent, modify the parameters. Then, check whether the alarm is cleared. For an optical interface, shut down and then start the laser. Then, check whether the alarm is cleared.
Step 2 Cause 2: The network is congested or its quality is poor, which causes improper running of the LCP protocol. 1. 2. On the NMS, check whether the bandwidth for the tunnel connected to the ports is configured low. For details, see Querying MPLS Tunnel Information. If yes, configure the tunnel with a higher bandwidth. Then, check whether the alarm is cleared.
Step 3 Cause 3: The physical link is interrupted. 1. 2. Check whether the physical link is connected properly. If not, restore the faulty physical link. Then, check whether the alarm is cleared.
----End
Related Information
None.
A Alarm Reference
A.3.263 PPP_NCP_FAIL
Description
The PPP_NCP_FAIL is an alarm indicating an NCP negotiation failure. This alarm is reported when the NCP configuration attributes are inconsistent between the local and opposite NEs.
Attribute
Parameters
None.

When this alarm occurs, the NCP negotiation fails and services are interrupted.
Possible Causes
l The NCP configurations are inconsistent between the local and opposite NEs.
Procedure
Step 1 The NCP configurations are inconsistent between the local and opposite NEs. 1. Reconfigure the NCP attributes on the local and opposite NEs and ensure they are consistent.
----End
Related Information
None.
A.3.264 PTP_SOURCE_SWITCH
Description
The PTP_SOURCE_SWITCH is an alarm indicating a switchover between PTP time sources.
Attribute
Issue 03 (2012-07-30)
630
A Alarm Reference
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1, Parameter 2 Parameter 3 Parameter 4, Parameter 5 Parameters 6 to 9 Parameters 10 to 13 Meaning Indicates the slot ID of the board before the switching. Indicates the ID of the subboard before the switching. 0xFF indicates that there is no subboard. Indicates the ID of the port before the switching. Indicates the ID 1 of the grandmaster clock before the switching. Indicates the ID 2 of the grandmaster clock before the switching.
Parameter 14, Parameter 15 Indicates the slot ID of the board after the switching. Parameter 16 Indicates the ID of the subboard after the switching. 0xFF indicates that there is no subboard.
Parameter 17, Parameter 18 Indicates the ID of the port after the switching. Parameters 19 to 22 Parameters 23 to 26 Indicates the ID 1 of the grandmaster clock after the switching. Indicates the ID 2 of the grandmaster clock after the switching.

When this alarm occurs, a switchover occurs on the IEEE 1588v2 clock source traced by the NE, which will cause clock switchover in the entire clock domain.
Possible Causes
l l l Cause 1: The physical link between the local NE and the clock source is faulty. Cause 2: Information about the grandmaster clock such as the priority 1, quality level, and priority 2 has changed. Cause 3: The network topology has changed.
Procedure
Step 1 Cause 1: The physical link between the local NE and the clock source is faulty. 1. Check the physical link between the NE and the clock source for troubleshooting. Step 2 Cause 2: Information about the grandmaster clock such as the priority 1, quality level, and priority 2 has changed. 1. If NE configurations are correct, no further action is required.
Step 3 Cause 3: The network topology has changed. 1. Replan the network and modify clock tracing relationships.
----End
A Alarm Reference
Related Information
None.
A.3.265 PTP_TIMESTAMP_ABN
Description
The PTP_TIMESTAMP_ABN is an alarm indicating an exception of the PTP timestamp. This alarm is reported when the PTP (IEEE 1588V2) timestamp is abnormal.
Attribute
Parameters
Parameter 1 l 0x02: indicates that timestamp t1 remains unchanged in three consecutive seconds. l 0x03: indicates that timestamp t2 remains unchanged in three consecutive seconds. l 0x04: indicates that timestamps t1 and t2 remain unchanged in three consecutive seconds. Parameter 2 l 0x02: indicates that timestamp t3 remains unchanged in 17 consecutive seconds. l 0x03: indicates that timestamp t4 remains unchanged in 17 consecutive seconds. l 0x04: indicates that timestamps t3 and t4 remain unchanged in 17 consecutive seconds.

When this alarm occurs, the slave NE fails to trace the time of the master NE. Bit errors may occur in the service.
Possible Causes
l l l
Issue 03 (2012-07-30)
Cause 1: The P/E attributes are different on the PTP ports of the local and opposite NEs. Cause 2: The transmit NE is faulty. Cause 3: The receive NE is faulty.
A Alarm Reference
Procedure
Step 1 Cause 1: The P/E attributes are different on the PTP ports of the local and opposite NEs. 1. 1. 1. Reconfigure the P/E attribute. For details, see Setting the PTP NE Attributes. Check the transmit NE for troubleshooting, or replace the clock source. and 6.10 Replacing the System Control, Switch and Timing Board. Step 2 Cause 2: The transmit NE is faulty. Step 3 Cause 3: The receive NE is faulty. ----End
Related Information
None.
A.3.266 PW_DROPPKT_EXC
Description
The PW_DROPPKT_EXC alarm indicates that the packet loss ratio on a PW exceeds its threshold.
Attribute
Alarm Severity Warning Alarm Type Processing alarm
Parameters Parameters
Parameter 1 Has a fixed value of 0x00, indicating that the traffic in the ingress or egress direction 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.
A Alarm Reference
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 the bandwidth utilization of the alarmed PW. If the PW bandwidth is exhausted, increase the bandwidth or eliminate any source that transmits a large amount of invalid data.
----End
Related Information
None.
A.3.267 PW_NO_TRAFFIC
Description
The PW_NO_TRAFFIC is an alarm indicating that a PW has no traffic. This alarm is reported when the PW that carries services has no traffic.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the direction in which traffic is unavailable. l 0x00: RX direction l 0x01: TX direction

When this alarm occurs, the PW has no traffic and PW services are interrupted.
Possible Causes
l l Cause 1: No service is configured. Cause 2: The local services are abnormal and therefore no packet is transmitted to the peer end.
Issue 03 (2012-07-30)
A Alarm Reference
l l
Cause 3: The peer services are abnormal and therefore no packet is transmitted to the local end. Cause 4: The port that corresponds to the faulty PW works improperly.
Procedure
Step 1 Determine the alarmed board, alarmed , and direction in which traffic is unavailable according to the alarm information on the NMS. If... Then...
The PW_NO_TRAFFIC alarm is reported in both the receive and transmit Go to Step 2. directions 0x00 0x01 Step 2 Cause 1: No service is configured. 1. Check whether the port is configured with any services. If not, configure services correctly. Go to Step 4. Go to Step 3.
Step 3 Cause 2: The local services are abnormal and therefore no packet is transmitted to the peer end. 1. Check whether the local PW services are correctly configured. For details, see Querying Information and Running Status of PWs.
Step 4 Cause 3: The peer services are abnormal and therefore no packet is transmitted to the local end. 1. Check whether the opposite PW services are correctly configured.
Step 5 Cause 4: The port that corresponds to the faulty PW works improperly. 1. 2. Replace the board that reports the alarm on the local NE. For details, see 6 Part Replacement. Check whether the alarm is cleared. If the alarm persists, replace the corresponding board of the opposite NE.
----End
Related Information
None.
A.3.268 PWAPS_LOST
Description
The PWAPS_LOST is an alarm indicating that the APS frame is lost. This alarm occurs when no APS frame is received from the protection channel.
Issue 03 (2012-07-30)
635
A Alarm Reference
Attribute
Parameters
None.

When this alarm occurs, the service protection fails.
Possible Causes
l l Cause 1: The remote NE of the PW is not configured with any protection group. 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.269 PWAPS_PATH_MISMATCH
Description
The PWAPS_PATH_MISMATCH is an alarm indicating that the working and protection paths of the APS protection group differ between the two ends. This alarm is reported when the working and protection paths of one APS protection group at one end are different from those at the other end.
Attribute
Issue 03 (2012-07-30)
636
A Alarm Reference
Parameters
None.

Possible Causes
l l Cause 1: The configured working and protection paths differ between the two ends. 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. 2. Check whether the APS settings at the two ends are the same. 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.270 PWAPS_SWITCH_FAIL
Description
The PWAPS_SWITCH_FAIL is an alarm indicating a switching failure of the PW APS protection group. This alarm is reported when the request signal in the transmitted Automatic Protection Switching (APS) frame is different from the bridge signal in the received APS frame and this symptom lasts for 50 ms.
Attribute
Parameters
None.

A Alarm Reference
Possible Causes
l l Cause 1: The configured working and protection paths differ between the two ends. 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. 2. Check whether the APS settings at the two ends are the same. 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.271 PWAPS_TYPE_MISMATCH
Description
The PWAPS_TYPE_MISMATCH is an alarm indicating that the local NE and the opposite NE are configured with different PW protection types. This alarm occurs when the information in the received APS frames is inconsistent with the APS protection scheme configured at the local end.
Attribute
Parameters
None.

Possible Causes
l l Cause 1: The configured protection modes (1+1 protection or 1:1 protection) differ at the two ends of the PW. Cause 2: The configured switching modes (single-ended or dual-ended) differ at the two ends of the PW.
Issue 03 (2012-07-30)
A Alarm Reference
Cause 3: The configured revertive modes (revertive or non-revertive) differ at the two ends of the PW.
Procedure
Step 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. For details, see Querying PW APS Status. Step 2 If the APS protection settings are different, change the settings to the same. ----End
Related Information
None.
A.3.272 R_LOC
Description
The R_LOC is an alarm indicating that the clock is lost on the receive line side. This alarm is reported when the line board fails to extract clock signal from the line signal or the IF board fails to extract clock signal from the IF signal.
Attribute
Parameters
None.

The services on the line port or the IF port are interrupted. If the system is configured with protection, protection switching may be triggered.
Possible Causes
l l Cause 1: The receive unit of the local site is faulty. 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.7 Software Loopback.
Issue 03 (2012-07-30)
A Alarm Reference
If... The alarm persists after the loopback The alarm is cleared after the loopback
Then... Replace the alarmed local board. Go to Cause 2.
Step 2 Cause 2: The transmit unit of the opposite station is faulty. 1. Replace alarmed opposite board. If... Then...
The alarm is cleared after the board is The fault is rectified. End the alarm handling. replaced The alarm persists after the board is Replace the system control, switch&timing replaced board at the opposite end. ----End
Related Information
None.
A.3.273 R_LOF
Description
The R_LOF is an alarm indicating that frames are lost on the receive side. This alarm is reported when the OOF state lasts for three milliseconds.
Attribute
Parameters
None.

Possible Causes
l l l l
Issue 03 (2012-07-30)
Cause 1: Certain alarms are generated (if the alarm is reported by an IF board). Cause 2: The line performance degrades (if the alarm is reported by an SDH optical interface board). Cause 3: The transmit unit of the opposite station is faulty. Cause 4: The receive unit of the local site is faulty.
A Alarm Reference
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... The alarm is generated Then... Take priority to clear the MW_BER_EXC, MW_BER_SD, MW_FEC_UNCOR alarm. Go to the next step.
The alarm is not generated 2. Set the inloop on the alarmed IF port. If... The alarm persists after the inloop is performed The alarm is cleared after the inloop is performed
Then... Go to Cause 4. Go to Cause 3.
Step 2 Cause 2: The line performance degrades (if the alarm is reported by an SDH optical interface board). 1. If the alarm is reported by an optical interface board, exchange the transmit and receive fiber jumpers at both ends. If... The alarm persists after the exchange The line port of the opposite station reports the R_LOF alarm Then... Go to Cause 3 or 4 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... The alarm is cleared after the board replacement The alarm persists after the board replacement 2. Then... The fault is rectified, and the alarm handling is complete. Go to the next step.
Replace the system control and cross-connect board at the opposite end.
Issue 03 (2012-07-30)
641
A Alarm Reference
If... The alarm is cleared after the board replacement The alarm persists after the board replacement
Then... The fault is rectified, and the alarm handling is complete. Go to Cause 4.
----End
Related Information
The handling procedure applies when this alarm is reported by the STM-1e port.
A.3.274 R_LOS
Description
In the case of SDH boards, the R_LOS is an alarm indicating that the signals on the receive line side are lost. In the case of IF boards, the R_LOS is an alarm indicating that the radio frames on the receive line side are lost.
Attribute
Parameters
None.

Possible Causes
l l l l Cause 1: Certain alarms are generated (if the alarm is reported by an IF board). Cause 2: The line performance degrades (if the alarm is reported by an SDH line board). Cause 3: The transmit unit of the opposite station is faulty. Cause 4: The receive unit of the local site is faulty.
Procedure
Step 1 Cause 1: Certain alarms are generated. (if the alarm is reported by an IF board).
A Alarm Reference
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... The alarm is generated Then... Take priority to clear the MW_BER_EXC, MW_BER_SD, MW_FEC_UNCOR alarm. Go to the next step.
The alarm is not generated
2.
Set the inloop on the alarmed IF port. If... The alarm persists after the inloop is performed The alarm is cleared after the inloop is performed Then... Go to Cause 4. 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... The alarm persists after the exchange The line port of the opposite station reports the R_LOF alarm Then... Go to Cause 3 or 4 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... The alarm is cleared after the board replacement The alarm persists after the board replacement Then... The fault is rectified, and the alarm handling is complete. Proceed to the next step.
2.
Replace the system control and cross-connect board at the opposite end. If... The alarm is cleared after the board replacement The alarm persists after the board replacement Then... The fault is rectified, and the alarm handling is complete. Go to Cause 4.
Issue 03 (2012-07-30)
643
A Alarm Reference
----End
Related Information
The handling procedure applies when this alarm is reported by the STM-1e port.
A.3.275 R_OOF
Description
The R_OOF is an alarm indicating an out-of-frame event on the receive side of the line.
Attribute
Parameters
None.

l l When this alarm occurs, services are interrupted, and the AIS signal is inserted on the downstream NE. When this alarm occurs, the system automatically returns the MS_RDI message to the upstream NE. Then, the upstream NE reports the MS_RDI alarm.
Possible Causes
l l l Cause 1: The transmit cable is faulty, and the fiber connector is loose or contaminated. Cause 2: The receive board on the local NE is faulty. Cause 3: The transmit board on the opposite NE is faulty.
Procedure
Step 1 Cause 1: The transmit cable is faulty, and the fiber connector is loose or contaminated. 1. Check whether the transmit optical power of the board connected to the board that reports the alarm is within the normal range. If... Then...
The transmit optical power of the opposite board is abnormal Go to Step 3.
Issue 03 (2012-07-30)
644
A Alarm Reference
If... The transmit optical power of the opposite board is normal 2.
On the NMS, check whether the receive optical power of the local board is within the normal range. If... The receive optical power of the local board is too low The receive optical power of the local board is too high Then... Go to the next step. Go to Step 2.
3. 4.
Check whether the bend radius of the fiber jumper is within the normal range. If the bend radius is less than 6 cm, re-roll the tail fiber. Check whether the alarm is cleared. If the alarm persists, check whether the optical interface on the board is firmly connected to the fiber jumper. Ensure that the fiber connector is firmly connected. Then, check whether the R_LOS alarm is cleared. If the alarm persists, check whether the fiber connector is contaminated. If yes, clean the fiber and fiber connector. For details, see 8.2 Cleaning Fiber Connectors and Adapters. Check whether the optical cable is aged out, damaged, or pressed. If yes, replace the optical cable.
5.
6.
Step 2 Cause 2: The receive board on the local NE is faulty. 1. Perform a hardware inloop for the transmit and receive interfaces of the port that reports the alarm on the local NE. For details, see 8.1 Hardware Loopback.
CAUTION
A loopback causes service interruption. To prevent optical power overload during hardware inloop, you can add an optical attenuator to the optical interface according to the optical power specifications of the board. If... The alarm persists The alarm is cleared 2. Then... The local board is faulty. Go to the next step. Go to Step 3.
Replace the board that reports the R_OOF alarm on the local NE. If the board supports the pluggable optical module, replace the pluggable optical module. For details, see 6.14 Replacing the SFP. Otherwise, replace the faulty board. For details, see 6.4 Replacing the Channelized STM-1 Processing Board.
Step 3 Cause 3: The transmit board on the opposite NE is faulty. 1. Rectify the fault on the opposite board.
----End
A Alarm Reference
Related Information
None.
A.3.276 RADIO_FADING_MARGIN_INSUFF
Description
The RADIO_FADING_MARGIN_INSUFF is an alarm indicating that the mean receive power of the ODUs are lower than the threshold of the receive power (the threshold value is about the receiver sensitivity + 14 dB). When the receive power of the ODUs in consecutive six hours is lower than the threshold, the system reports the alarm. When the mean receive power of the ODUs becomes normal and lasts for three minutes after the alarm is reported, the alarm is cleared.
Attribute
Parameters
None.

If the MW_BER_EXC, MW_BER_SD, MW_LOF or MW_FEC_UNCOR alarm is not generated, the service is not affected.
Possible Causes
l l l l Cause 1: The ODU fault of the transmit end causes the abnormal transmit power. Cause 2: The direction of the antenna is deflected. Cause 3: The transmission environment changes. 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. If... The ODU at the transmit end reports the RADIO_TSL_LOW alarm Check whether the ODU at the transmit end reports the RADIO_TSL_LOW alarm. Then... Handle the RADIO_TSL_LOW alarm.
The ODU at the transmit end does not report the Go to Cause 2. RADIO_TSL_LOW alarm Step 2 Cause 2: The direction of the antenna is deflected.
A Alarm Reference
1.
Check whether the direction of the antenna is deflected. If... The direction of the antenna is deflected The direction of the antenna is not deflected Then... Adjust the direction of the antenna. Go to Cause 3.
Step 3 Cause 3: The transmission environment changes. 1. If... The transmission environment changes The transmission environment does not change Check whether the transmission environment changes. For example, check whether any building blocks the transmission and increases the link fading significantly. Then... Contact the network planning department for re-planning the transmission trail. 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
Related Information
None.
A.3.277 RADIO_MUTE
Description
The RADIO_MUTE is an alarm indicating that radio transmitter is muted.
Attribute
Alarm Severity Warning Alarm Type Equipment alarm
Parameters
None.

The transmitter does not transmit services.
Possible Causes
l
Issue 03 (2012-07-30)
Cause 1: The other alarms are generated.

A Alarm Reference
l l l
Cause 2: The transmitter of the local site is muted manually. Cause 3: The IF board is faulty, causing abnormal IF output. 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 a SingleHop Radio Link. If yes, cancel the muting operation. Then, set the transmitting 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 Information
The logical slot ID of the ODU is obtained by adding 20 to the slot ID of the IF board connected to the ODU.
A.3.278 RADIO_RSL_BEYONDTH
Description
The RADIO_RSL_BEYONDTH is an alarm indicating that the antennas are not aligned. When the receive power is set on the NE, the NE enables the antenna alignment indication function. If the actual receive power of the ODU is lower than the power to be received 3 dB, the RADIO_RSL_BEYONDTH alarm is reported. Then, if the antennas are aligned for continuous 30 minutes, the antenna alignment indication function is disabled automatically. Afterwards, the RADIO_RSL_BEYONDTH alarm is reported only when the RADIO_FADING_MARGIN_INSUFF alarm is reported.
Attribute
Parameters
None.
A Alarm Reference

If the MW_BER_EXC, MW_BER_SD, MW_LOF or MW_FEC_UNCOR alarm is not generated, the service is not affected.
Possible Causes
l l Cause 1: Antennas are not aligned during the equipment commissioning. 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_BEYONDTH alarm is cleared.
----End
Related Information
None.
A.3.279 RADIO_RSL_HIGH
Description
The RADIO_RSL_HIGH is an alarm indicating that the radio receive power is very high. This alarm is reported if the detected receive power is equal to or higher than the upper threshold of the ODU (-20 dBm).
Attribute
Parameters
None.

The service transmission is affected. If the system is configured with 1+1 protection, protection switching may be triggered.
A Alarm Reference
Possible Causes
l l l Cause 1: The local ODU is faulty. Cause 2: There is a strong interference source nearby. Cause 3: The transmit power of the opposite ODU is very high.
Procedure
Step 1 Cause 1: The local ODU is faulty. 1. 6.15 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 the specified range. If yes, check whether the signal source can be shut down or removed. If not, 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 a Single-Hop Radio Link.
----End
Related Information
None.
A.3.280 RADIO_RSL_LOW
Description
The RADIO_RSL_LOW is an alarm indicating that the radio receive power is very low. This alarm is reported if the detected receive power is equal to or lower than the upper threshold of the ODU (-90 dBm).
Attribute
Parameters
None.

If no MW_BER_EXC, MW_BER_SD, MW_LOF or MW_FEC_UNCOR alarm is generated, the services are not affected.
A Alarm Reference
Possible Causes
l l l l Cause 1: Other alarms occur at the opposite station. Cause 2: The transmit power of the opposite station is very low. Cause 3: The local ODU is faulty. 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_MUTE l CONFIG_NOSUPPORT l RADIO_TSL_LOW l BD_STATUS Step 2 Cause 2: The transmit power of the opposite station is very low. 1. See Configuring a Single-Hop 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 change the 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 planning design, hence preventing the block of the mountain or building obstacle. 4. Check whether the polarization direction of the antenna, ODU, and hybrid coupler is set correctly. 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 Part Replacement 6. Check whether the antenna gain at both the transmit and receive ends meets the requirement. If not, replace the antenna. ----End
A Alarm Reference
Related Information
None.
A.3.281 RADIO_TSL_HIGH
Description
The RADIO_TSL_HIGH is an alarm indicating that the radio transmit power is too high. This alarm is reported when the detected transmit power is higher than the upper power threshold of the ODU.
Attribute
Parameters
None.

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.282 RADIO_TSL_LOW
Description
The RADIO_TSL_LOW is an alarm indicating that the radio transmit power is very low. This alarm is reported when the detected transmit power is less than the lower power threshold of the ODU.
A Alarm Reference
Attribute
Parameters
None.

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.283 RELAY_ALARM_CRITICAL
Description
The RELAY_ALARM_CRITICAL is an alarm indicating the critical alarm inputs. This alarm occurs when the user sets the severity of an available alarm input to critical and there is such an alarm input.
Attribute
Parameters
None.

When the RELAY_ALARM_CRITICAL alarm occurs, it does not affect the operation of the board or the services on the NE.
A Alarm Reference
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.284 RELAY_ALARM_IGNORE
Description
The RELAY_ALARM_IGNORE is an alarm indicating the warning alarm inputs. This alarm occurs when the user sets the severity of an available alarm input to warning and there is such an alarm input.
Attribute
Parameters
None.

When the RELAY_ALARM_IGNORE alarm occurs, it does not affect the operation of the board or the services on the NE.
Possible Causes
Cause 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 Alarm Reference
Related Information
None.
A.3.285 RELAY_ALARM_MAJOR
Description
The RELAY_ALARM_MAJOR is an alarm indicating the major alarm inputs. This alarm occurs when the user sets the severity of an available alarm input to major and there is such an alarm input.
Attribute
Parameters
None.

When the RELAY_ALARM_MAJOR alarm occurs, it does not affect the operation of the board or or the services on the NE.
Possible Causes
Cause 1: There is a major alarm input.
Procedure
Step 1 Cause 1: There is a major alarm input. 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.286 RELAY_ALARM_MINOR
Description
The RELAY_ALARM_MINOR is an alarm indicating the minor alarm inputs. This alarm occurs when the user sets the severity of an available alarm input to minor and there is such an alarm input.
A Alarm Reference
Attribute
Parameters
None.

When the RELAY_ALARM_MINOR alarm occurs, it does not affect the operation of the board or or 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.
A.3.287 RMFA
Description
The RMFA is an alarm indicating the loss of multiframe alignment at the remote end. This alarm occurs when the local end detects all 1s of the remote indication bits in Z consecutive CAS multiframes (Z = 1-5) of the framed E1/T1 input.
Attribute
Parameters
A Alarm Reference
Name Parameter 1
Parameter 2, Parameter 3 Indicate the path ID.

When this alarm occurs, the services at the local site are not affected. The alarm indicates that the 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 the LMFA alarm. Then, the RMFA alarm at the local end clears. ----End
Related Information
None.
A.3.288 RPS_INDI
Description
The RPS_INDI is an alarm indicating that the radio protection switching is detected.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Parameter 2 Meaning Indicates the ID of the protection group. Indicates the type of protection switching. 0x01: HSB protection switching
Issue 03 (2012-07-30)
657
A Alarm Reference

l l During the HSB protection switching, services are interrupted. After the HSB switching is complete, the services are restored to normal. During the HSM protection switching, no bit errors occur and the services are not affected.
Possible Causes
l The possible causes of the HSB protection switching are as follows: Cause 1: An external switching event occurs Cause 2: An automatic switching event occurs. Cause 3: A reverse switching event occurs. l 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. Step 2 Cause 1 of HSB switching: An external switching event occurs. That is, the NMS issues a command to trigger the switching. 1. Check whether the switching is the forced switching or manual switching. For details, see Querying the IF 1+1 Protection Status. If... Then...
The switching is the forced switching or Find the cause and release the switching manual switching immediately. The switching is not the forced switching or manual switching Go to Cause 2 of HSB switching.
Step 3 Cause 2 of HSB switching: An automatic switching event occurs. That is, the equipment is faulty, or the service is defective. 1. Check whether the following faults or alarms occur. If yes, rectify the faults or clear the alarms. l The hardware of the IF board or the ODU is faulty. l VOLT_LOS l RADIO_TSL_HIGH, RADIO_TSL_LOW, or RADIO_RSL_HIGH l IF_INPWR_ABN or CONFIG_NOSUPPORT l R_LOC, R_LOF, R_LOS, or MW_LOF
Issue 03 (2012-07-30)
658

NOTE
A Alarm Reference
l If the switching is non-revertive, the services are not automatically switched to the working path when the working path is restored to normal, and the RPS_INDI alarm persists. In this case, you need to manually switch the services from the protection path to the working path. The RPS_INDI alarm is cleared only when the switching is successful. l If the switching is revertive, the services are automatically switched to the working path only when the specified wait-to-restore (WTR) time expires after the working path is restored to normal. 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 the quality of the main channel to degrade. If the alarm is not reported by an IF board, the quality of the main channel degrades possibly due to the weather. In this case, you do not need 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 HSM switching 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_LOF l MW_BER_EXC, MW_BER_SD, MW_FEC_UNCOR l B1_SD or B2_SD ----End
Related Information
None.
A.3.289 RS_CROSSTR
Description
The RS_CROSSTR is an alarm indicating that a regenerator section performance indicator crosses the threshold. This alarm is reported if a board detects that a regenerator section bit error performance event crosses the preset threshold.
Attribute
Issue 03 (2012-07-30)
659
A Alarm Reference
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the performance monitoring period: l 0x01: 15 minutes l 0x02: 24 hours Parameter 2, Parameter 3 Parameter 2 is always 0x00. Parameter 3 indicate the ID of a performance event that causes the alarm and has the following meanings: l 0x01: RSBBE l 0x02: RSES l 0x03: RSSES l 0x04: RSOOF l 0x05: RSOFS l 0x06: RSUAS l 0x07: RSCSES

A large number of bit errors occur in the services, and the services may be interrupted.
Possible Causes
l l Cause 1: Services are interrupted for a long time. Cause 2: The regenerator section bit error performance indicator crosses the preset threshold.
Procedure
Step 1 Cause 1: Services are interrupted for a long time.
NOTE
Handle the alarm as follows if the value of parameter 3 is 0x06:
1. 2.
Check whether fibers are properly connected. If not, connect the fibers again according to planning information. Check whether cross-connections are configured for service ports. If not, configure crossconnections 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.12 Browsing the Performance Event Threshold-Crossing Records.
Issue 03 (2012-07-30)
A Alarm Reference
2.
Handle the performance event that crosses the threshold.
----End
Related Information
None.
A.3.290 RTC_FAIL
Description
The RTC_FAIL is an alarm indicating that the real-time clock (RTC) on the system control board fails.
Attribute
Parameters
None.

The service is not affected.
Possible Causes
l l Cause 1: The RTC on the system control board is abnormal. Cause 2: The board temperature is too high.
Procedure
Step 1 Cause 1: The RTC on the system control board is abnormal. 1. 1. Replace the system control, switching, and timing board. 8.3.3 Browsing Current Alarms, and if the board reports the TEMP_ALARM alarm, clear this alarm first. Step 2 Cause 2: The board temperature is too high.
----End
Related Information
None.
A.3.291 S1_SYN_CHANGE
A Alarm Reference
Description
The S1_SYN_CHANGE is an alarm indicating that the clock source is switched in S1 byte mode.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning 0x01: system priority list 0x02: external clock priority list

If the new clock source has a lower quality, pointer justifications and bit errors are generated after the switching of clock source. As a result, the quality of services is affected.
Possible Causes
When the SSM protocol or extended SSM protocol is enabled. l l l l Cause 1: The original clock source is lost. Cause 2: The fiber is cut off. Cause 3: The external BITS is interrupted. 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.
A Alarm Reference
1.
Handle the S1_SYN_CHANGE alarm reported at the upstream station.
----End
Related Information
None.
A.3.292 SCCDATA_BACKUP_FAIL
Description
The SCCDATA_BACKUP_FAIL is an alarm indicating that the batch backup on SCC boards fails.
Attribute
Parameters
Parameter 1 Indicates the cause of the failure. l 0x1F: The database backup fails. l 0x20: Software version verification fails on the main and standby SCC boards. l 0x21: Communication between the main and standby SCC boards fails. l 0x22: The main and standby SCC boards have different data after an upgrade.

Data synchronization between the main and standby SCC boards fails, and the switching between the two boards is unavailable.
Possible Causes
l l l l
Issue 03 (2012-07-30)
Cause 1: The main and standby SCC boards have different versions of software. Cause 2: Communication between the main and standby SCC boards fails. Cause 3: Databases on the main and standby SCC boards are damaged. Cause 4: The main and standby SCC boards have different data after an upgrade.
A Alarm Reference
Procedure
Step 1 Cause 1: The main and standby SCC boards have different versions of software. 1. 2. Query and record the software versions of the main and standby SCC boards according to 8.6.1 Querying the Board Information Report . 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.10 Replacing the System Control, Switch and Timing Board.
Step 2 Cause 2: Communication between the main and standby SCC boards fails. 1. 2. Check whether the system reports the COMMUN_FAIL alarm. 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. 2. Check whether the system reports the DBMS_ERROR alarm. For details, see 8.3.3 Browsing Current Alarms. 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
Related Information
None.
A.3.293 SEC_RADIUS_FAIL
Description
The SEC_RADIUS_FAIL is an alarm indicating that RADIUS authentication fails over many times. This alarm is reported when the RADIUS authentication fails for five consecutive times.
Attribute
Parameters
A Alarm Reference
Name Parameter 1 to Parameter 16
Meaning Indicates the username.

A user cannot log in to an NE.
Possible Causes
l l l l Cause 1: The active period of the account expires. Cause 2: Configurations on the RADIUS server are incorrect, such as passwords and access policies. Cause 3: There are unauthenticated login attempts. 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 access policies. 1. 2. 1. 1. Enter the correct password. Set correct access policies. Eliminate the source that initiates the unauthenticated login attempts. Set the shared key correctly.
Step 3 Cause 3: There are unauthenticated login attempts. Step 4 Cause 4: The shared key for the NE and the RADIUS server is configured incorrectly.
----End
Related Information
None.
A.3.294 SECU_ALM
Description
The SECU_ALM is an alarm indicating that an illegal user fails to log in to the NE.
Attribute
Issue 03 (2012-07-30)
665
A Alarm Reference
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Parameters 2 and 3 Parameters 4 and 5 Meaning Indicates the terminal type used in the login attempt. Indicate the errors that occur in the login attempt. Indicate the first two characters of the user name.

The SECU_ALM alarm is ended soon after it is reported, and the alarm does not affect the system and 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 logins is less than 3 minutes, the two logins are consecutive logins), the SECU_ALM alarm is reported upon each subsequent login failure and meanwhile the user is locked for 60 seconds. During the 60 seconds, the user cannot log in to the NE.
A.3.295 SRV_SHUTDOWN_LD
Description
The SRV_SHUTDOWN_LD alarm indicates that an Ethernet service is deactivated. This alarm is reported when an Ethernet service is deactivated due to a service loop. This alarm is cleared after the Ethernet service is reactivated.
Attribute
Issue 03 (2012-07-30)
666
A Alarm Reference
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. 2. Check whether a service is looped back on the path of the alarmed Ethernet service. Re-configure the preceding service based on the network plan.
----End
Related Information
None.
A.3.296 SSL_CERT_NOENC
Description
SSL_CERT_NOEN indicates the certificate file of SSL is not encrypted.
Attribute
Alarm Severity Major Alarm Type Equipment Alarm
Parameters
None.

Plaintext certificate file is stored on device, private key of the file maybe be get illegally.
Possible Causes
Certificate file of SSL is not encrypted.
A Alarm Reference
Procedure
Step 1 Download and verify the encrypted SSL certificate by NMS. ----End
Related Information
None.
A.3.297 SWDL_ACTIVATED_TIMEOUT
Description
The SWDL_ACTIVATED_TIMEOUT is an alarm indicating the activation timeout of the software package. During the package loading, the system reports the alarm if no data is submitted within 30 minutes after activation of the NE software or board software.
Attribute
Parameters
None.

The NE does not perform the submit operation. As a result, the software in the two areas of the double-area boards on the NE is inconsistent.
Possible Causes
Cause 1: The radio link is faulty. As a result, the NE involved in the package loading fails to receive the submit command.
Procedure
Step 1 Cause 1: The radio link is faulty. As a result, the NE involved in the package loading fails to receive the submit command. 1. Check whether the radio link is faulty. If... The radio link is faulty Then... Troubleshoot the radio link to ensure that the link between the nodes to be loaded is normal.
The radio link is normal Perform the package loading to the NE again. ----End
A Alarm Reference
Related Information
None.
A.3.298 SWDL_AUTOMATCH_INH
Description
The SWDL_AUTOMATCH_INH is an alarm indicating that the automatic match function is disabled. When the automatic match function of the board is disabled, the system reports the alarm if the board cannot match the software from the system control board.
Attribute
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 match the software from the system control board. As a result, certain functions of the NE cannot run normally.
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.299 SWDL_CHGMNG_NOMATCH
Description
The SWDL_CHGMNG_NOMATCH is an alarm of software inconsistency. After an NE is power recycled and the boards on the NE become online, if the system detects that the system
A Alarm Reference
control board and the CF card are inconsistent in software packages, the system reports the SWDL_CHGMNG_NOMATCH alarm.
Attribute
Parameters
None.

When the SWDL_CHGMNG_NOMATCH alarm is reported, certain functions of the NE may be affected.
Possible Causes
Cause 1: After a system control board is replaced, the software package in the new system control board 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 control board 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
Related Information
None.
A.3.300 SWDL_COMMIT_FAIL
Description
The SWDL_COMMIT_FAIL is an alarm indicating that the commission operation on the NE fails. This alarm is reported when the commission operation fails in the package diffusion.
Attribute
Issue 03 (2012-07-30)
670
A Alarm Reference
Parameters
None.

When the SWDL_COMMIT_FAIL alarm occurs, the software versions in the two areas of the double-area board are inconsistent.
Possible Causes
Cause 1: File backup fails.
Procedure
Step 1 Cause 1: File backup fails. 1. 2. Check whether the loaded package is correct. Perform the package diffusion again on the NE where the alarm is reported.
----End
Related Information
None.
A.3.301 SWDL_INPROCESS
Description
The SWDL_INPROCESS is an alarm indicating that the NE is loading the software package.
Attribute
Alarm Severity Warning Alarm Type Processing alarm
Parameters
None.

The NE is loading the software package. The operations including modifying configurations, uploading/downloading files, and backing up the database are prohibited.
Possible Causes
The NE is loading the software package.
A Alarm Reference
Procedure
Step 1 The SWDL_INPROCESS alarm is cleared automatically after the loading or rollback is complete. Hence, this alarm can be neglected. ----End
Related Information
None.
A.3.302 SWDL_NEPKGCHECK
Description
The SWDL_NEPKGCHECK is an alarm indicating that a file in the loaded software package is lost or cannot be recovered after a file check failure. This alarm is reported when the NE software initiates a package file check, detects the loss of a file, and fails to recover the file from any complete package in other areas.
Attribute
Parameters
None.

l l If this alarm occurs during package loading, package loading fails. 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 loading again on the NE where the SWDL_NEPKGCHECK alarm is reported.
----End
Related Information
None.
A Alarm Reference
A.3.303 SWDL_PKG_NOBDSOFT
Description
The SWDL_PKG_NOBDSOFT is an alarm indicating that certain board software is missing from the software package. This alarm is reported when the required software is missing from the software package during the automatic match of the board.
Attribute
Parameters
None.

The board cannot perform automatic match, because the board software is missing from the software package. Therefore, the board software version is inconsistent with the NE software version, and certain functions of the NE may be affected.
Possible Causes
Cause 1: Certain board software is 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.304 SWDL_PKGVER_MM
Description
The SWDL_PKGVER_MM is an alarm indicating that the consistency check on the software package version fails. This alarm is reported when the consistency check on the software package version fails.
A Alarm Reference
Attribute
Parameters
None.

The software version of the software package is inconsistent with the software version described in the software package. As a result, certain functions of the NE may be affected.
Possible Causes
Cause 1: The software version information in the description file of the software package is inconsistent with the actual software version information.
Procedure
Step 1 Cause 1: The software version information in the description file of the software package is inconsistent 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
Related Information
None.
A.3.305 SWDL_ROLLBACK_FAIL
Description
The SWDL_ROLLBACK_FAIL is an alarm indicating that the rollback on the NE fails. This alarm is reported when the rollback fails for any board on the NE.
Attribute
Parameters
None.
A Alarm Reference

The board software version and the NE software version may mismatch, 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.306 SYN_BAD
Description
The SYN_BAD is an alarm indicating that the quality of the synchronization source declines.
Attribute
Parameters
None.

The NE clock fails to be locked.
Possible Causes
l l Cause 1: The quality of the synchronization source declines. Cause 2: A certain board is faulty.
Procedure
Step 1 Cause 1: The quality of the synchronization source declines. 1.
Issue 03 (2012-07-30)
Take different measures based on the traced synchronization source.

A Alarm Reference
If...
Then...
The traced synchronization source is an Perform Steps Step 1.2 to Step 1.4. external clock The traced synchronization source is a line clock 2. Replace the system control, switching&timing board of the upstream NE.
Check whether the configuration of the external clock is correct. If... The configuration is incorrect The configuration is correct Then... Change the configuration data. Go to the next step.
3.
Check whether the opposite equipment that provides the clock source is faulty. If... The equipment is faulty The equipment functions normally Then... Rectify the fault. Go to the next step.
4.
Check whether the cable that is connected to the external clock source is in normal status. If... The cable is not in normal status The cable is in normal status Then... Replace the cable. Go to Cause 2.
Step 2 Cause 2: A certain board is faulty. 1. 6.10 Replacing the System Control, Switch and Timing Board.
----End
Related Information
None.
A.3.307 SYNC_C_LOS
Description
The SYNC_C_LOS is an alarm indicating that the synchronization source is lost.
Attribute
Parameters
None.
A Alarm Reference

The NE clock degrades or enters the free-run mode.
Possible Causes
Cause 1: The clock source is lost.
Procedure
Step 1 Cause 1: The clock source is lost. 1. See Querying the Clock Synchronization Status, troubleshoot the synchronization sources of the lost clock source based on the clock source priority table. If... The synchronization source is an external clock The synchronization source is an IF clock The synchronization source is a line clock The synchronization source is a tributary clock ----End Then... Handle the EXT_SYNC_LOS alarm. Handle the alarm that occurs on the IF board. Handle the alarm that occurs on the line board. Handle the alarm that occurs on the tributary board.
Related Information
None.
A.3.308 SYSLOG_COMM_FAIL
Description
The SYSLOG_COMM_FAIL is an alarm indicating that the communication between the NE and the syslog server fails.
Attribute
Parameters
None.

The syslog information of the NE cannot be sent to the syslog server.
A Alarm Reference
Possible Causes
Cause 1: In the TCP mode, the connection between the NE and syslog server is interrupted, or the session between the NE and server is abnormal.
Procedure
Step 1 Rectify the fault of the link between the NE and syslog server, or rectify the fault of the protocol. ----End
Related Information
None.
A.3.309 T_ALOS
Description
The T_ALOS is an alarm indicating that the 2Mbit/s analog signal is lost at the specific port.
Attribute
Parameters
None.

The 2Mbit/s services are interrupted.
Possible Causes
l l l l Cause 1: No 2Mbit/s services are received on the port. Cause 2: The opposite NE is faulty. Cause 3: The IF cable is faulty. Cause 4: The alarmed board is faulty.
Procedure
Step 1 Cause 1: No 2Mbit/s services are received on the port. 1. Check whether the alarmed port receives the 2 Mbit/s service. If... Then...
The services are not received Transmit the services to the port or delete the unnecessary service configuration.
A Alarm Reference
If... The services are received
Step 2 Cause 2: The equipment at the opposite end is faulty. 1. Check whether the equipment at the opposite end is faulty. If... The equipment is faulty The equipment is normal Step 3 Cause 3: The IF cable is faulty. 1. Check whether the IF cable is faulty. If... The IF cable is faulty The IF cable is not faulty Step 4 Cause 4: The alarmed board is faulty. 1. Replace the alarmed board. Then... Rectify the fault. Go to Cause 4. Then... Rectify the fault. Go to Cause 3.
----End
Related Information
None.
A.3.310 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.
A Alarm Reference
Possible Causes
l l Cause 1: The cross-connect and timing board is faulty. Cause 2: The line board is faulty.
Procedure
Step 1 Cause 1: The cross-connect and timing board is faulty. 1. Replace the cross-connect and timing board at the local site. If... The alarm is cleared after the board is replaced The alarm persists after the board is replaced Step 2 Cause 2: The line board is faulty. 1. Replace the alarmed board. Then... The fault is rectified. End the alarm handling. Go to Cause 2.
----End
Related Information
None.
A.3.311 TEM_HA
Description
The TEM_HA is an alarm indicating that the laser temperature is too high.
Attribute
Parameters
None.

When this alarm occurs, the laser is functioning improperly. As a result, services are interrupted.
Possible Causes
l l
Issue 03 (2012-07-30)
Cause 1: The ambient temperature of the board is too high. Cause 2: The optical module is faulty.
A Alarm Reference
Procedure
Step 1 Check whether the temperature of the equipment room is too high. If yes, decrease the temperature to an appropriate temperature. Then, check whether the alarm is cleared. Step 2 If the alarm persists, the optical module may be faulty. Replace the faulty board. For details, see 6.14 Replacing the SFP or Replacing the Alarming Board. ----End
Related Information
None.
A.3.312 TEM_LA
Description
The TEM_LA is an alarm indicating that the laser temperature is too low.
Attribute
Parameters
None.

When this alarm occurs, the laser is functioning improperly. As a result, services are interrupted.
Possible Causes
l l Cause 1: The ambient temperature of the board is too low. Cause 2: The optical module is faulty.
Procedure
Step 1 Check whether the temperature of the equipment room is too low. If yes, increase the temperature to an appropriate temperature. Then, check whether the alarm is cleared. Step 2 If the alarm persists, the optical module may be faulty. Replace the faulty board. For details, see 6.14 Replacing the SFP or Replacing the Alarming Board. ----End
Related Information
None.
A Alarm Reference
A.3.313 TEMP_ALARM
Description
The TEMP_ALARM is an alarm indicating that the board temperature crosses the threshold.
Attribute
Alarm Severity Minor Alarm Type Environmental alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning l 0x01: The temperature crosses the upper threshold. l 0x02: The temperature crosses the lower threshold.

The board fails to work normally.
Possible Causes
l l Cause 1: The board temperature crosses the threshold. Cause 2: The temperature detection circuit of the board is faulty.
Procedure
Step 1 Cause 1: The board temperature crosses the threshold. 1. 2. If the alarm is reported by the ODU, take appropriate measures (for example, installing a sunshade) to control the temperature. If the alarm is reported by the board on the IDU, check whether the temperature control devices, such as air-conditioners, work normally. If... The temperature control devices work abnormally The temperature control devices work normally 3.
Issue 03 (2012-07-30)
Then... Adjust the temperature control devices. Go to the next step.
Check whether the heat dissipation hole on the IDU is covered or blocked.
A Alarm Reference
If... The heat dissipation hole is covered or blocked
Then... Clear or remove the covering materials or obstacles.
The heat dissipation hole is not covered or Go to Cause 2. blocked 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
Related Information
None.
A.3.314 TEMP_OVER
Description
The TEMP_OVER is an alarm indicating that the working temperature of the board crosses the threshold.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning l 0x01: The temperature crosses the upper threshold. l 0x02: The temperature crosses the lower threshold.

When this alarm occurs, the board cannot work properly.
Possible Causes
l l
Issue 03 (2012-07-30)
Cause 1: The board temperature crosses the threshold. Cause 2: The temperature detection circuit of the board is faulty.
A Alarm Reference
Procedure
Step 1 Cause 1: The board temperature crosses the threshold. 1. Check whether temperature control devices, such as air-conditioners, work properly. If... The temperature control devices malfunction The temperature control devices work properly 2. Then... Adjust the temperature control devices. Go to the next step.
Check whether the heat dissipation hole on the IDU is covered or blocked. If... The heat dissipation hole is covered or blocked Then... Clear or remove the covering materials or obstacles.
The heat dissipation hole is not covered or Go to the next step. blocked 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 board that reports the alarm. For details see Replacing the Alarming Board.
----End
Related Information
None.
A.3.315 TF
Description
The TF is an alarm indicating that the laser transmission fails. This alarm is reported when a board detects that the output optical power of the laser exceeds the preset failure alarm threshold.
Attribute
Parameters
None.

When this alarm occurs, the laser transmission fails. As a result, services are interrupted.
A Alarm Reference
Possible Causes
l l Cause 1: The laser module is damaged. Cause 2: The laser is aged out.
Procedure
Step 1 6.14 Replacing the SFP. ----End
Related Information
None.
A.3.316 THUNDERALM
Description
The THUNDERALM is an alarm indicating the surge protection failure. If the system detects the surge protection circuit fails, the THUNDERALM occurs.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the PIU that reports the alarm. l 0x01: PIU1 l 0x02: PIU2

When the THUNDERALM occurs, the system operation and services are not affected, but the surge protection function fails.
Possible Causes
The possible causes of the THUNDERALM alarm are as follows: l
Issue 03 (2012-07-30)
Cause 1: The fuse tube of the surge protection circuit is interrupted.

A Alarm Reference
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.317 TIME_LOCK_FAIL
Description
The TIME_LOCK_FAIL is an alarm indicating a time locking failure.
Attribute
Parameters
Name Meaning
Parameter 1 l 0x01: indicates that the time synchronization is disabled or the 1588v2 port is not traced. l 0x02: indicates that the clock is unlocked because phase discrimination value within the given time exceeds the upper threshold. l 0x03: indicates that the forward delay is abnormal. l 0x04: indicates that the backward delay is abnormal. l 0x05: indicates that the accumulated offset value within the given time exceeds 240 ns. l 0x06: indicates that the accumulated offset value within the given time is greater than 100 ns but less than 240 ns.

When this alarm occurs, the time of the slave NE fails to trace that of the master NE. Bit errors may occur in the service.
A Alarm Reference
Possible Causes
The timestamp change on the NE is too large.
Procedure
Step 1 Check whether there are CLK_LOCK_FAIL or TIME_NO_TRACE_MODE alarms on the NE. If yes, clear them before you proceed. Step 2 Adjust the time on the upstream NE. ----End
Related Information
None.
A.3.318 TIME_NO_TRACE_MODE
Description
The TIME_NO_TRACE_MODE is an alarm indicating that the high precision time of the boards is in the non-traced status. This alarm is reported when the high precision time function of an NE is enabled and the current tracing source is the internal time source.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicate the cause of the alarm. 0x01: indicates that the IEEE 1588v2 function is enabled on a port. 0x02: indicates that an external clock interface is set to the input status.

When this alarm occurs, time between the NE and the upstream NEs cannot be synchronized.
A Alarm Reference
Possible Causes
l l l Cause 1: The clock source priority table is not configured when an external clock interface is used to trace the upstream NE clock. Cause 2: The link between the traced upstream time source and the NE is faulty. Cause 3: The announce attribute of the local NE is inconsistent with that of the upstream NE. As a result, the time source cannot be traced.
Procedure
Step 1 Cause 1: The clock source priority table is not configured when an external clock interface is used to trace the upstream NE clock. 1. Set the clock source priority. For details, see Configuring the Clock Sources.
Step 2 Cause 2: The link between the traced upstream time source and the NE is faulty. 1. Check the link fault.
Step 3 Cause 3: The announce attribute of the local NE is inconsistent with that of the upstream NE. As a result, the time source cannot be traced. 1. Check clock tracing relationships on the entire network based on the network plan.
----End
Related Information
None.
A.3.319 TR_LOC
Description
The TR_LOC is an alarm indicating that the clock is faulty. This alarm is reported when a board detects that the clock signal transmitted from the clock unit to the board is lost.
Attribute
Parameters
Issue 03 (2012-07-30)
688
A Alarm Reference
Name Parameter 1
Meaning Indicates the slot ID of the board that loses the clock. l 0x01: board with a smaller slot ID. l 0x02: board with a larger slot ID. l 0x03: two boards.

l l If the protection cross-connect board is faulty, the services are not affected. If the working cross-connect board is faulty, the services are switched, therefore causing transient service interruption.
Possible Causes
l l Cause 1: If one board reports this alarm, the board hardware is faulty. Cause 2: If multiple boards report this alarm, the clock cable of the cross-connect board is faulty.
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 Resetting a Boards. If the alarm persists, remove the alarmed board and check whether certain pins on the backplane are bent. Insert the board again, and then check whether the alarm is cleared. If the alarm persists, replace the alarmed board. For details, see Replacing a Board.
2. 3.
Step 3 Cause 2: If multiple boards report this alarm, the clock cable of the cross-connect board is faulty. 1. 2. 3. 4. If the working cross-connect board is faulty, perform 1+1 protection switching on the crossconnect board. For details, see Performing 1+1 Protection Switching. Perform a cold reset on the protection cross-connect board, and then check whether the alarm is cleared. If the alarm persists, remove and insert the protection cross-connect board, and then check whether the alarm is cleared. If the alarm persists, replace the protection cross-connect board.
----End
Related Information
None.
Issue 03 (2012-07-30)
689
A Alarm Reference
A.3.320 TU_AIS
Description
The AU_AIS is an alarm indicating that the TU has errors. This alarm is reported if a board detects that the signal in the TU path is all 1s.
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 Causes
l l l l Cause 1: Configuration data is incorrect. Cause 2: The line is faulty. Cause 3: The board at the opposite end is faulty. 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 service data is incorrect. If... The service data is incorrect The service data is correct Step 2 Cause 2: The line is faulty. 1. Check whether a line alarm that causes AIS insertion is reported on the service trail.
NOTE
Then... Change the configuration data. Go to Cause 2.
For details about the line alarms that cause AIS insertion, see E.2.6 AIS Insertion.
If... The line alarm is reported No line alarms are reported

Issue 03 (2012-07-30)
Then... Clear the line alarms that cause AIS insertion. Go to the next step.
690
A Alarm Reference
2.
See 8.7 Software Loopback to locate whether the board at the local end or at the opposite end is faulty. If... The board at the opposite end is faulty The board at the local end is faulty Then... Go to Cause 3. Go to Cause 4.
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. 6 Part Replacement. If... The alarm is cleared after the board is replaced The alarm persists after the board is replaced 2. Then... The fault is rectified. End the alarm handling. Go to the next step.
Replace the system control, cross-connect, and timing board at the local end. If... The alarm is cleared after the board is replaced The alarm persists after the board is replaced Then... The fault is rectified. End the alarm handling. Go to the next step.
3.
Replace the alarmed board.
----End
Related Information
None.
A.3.321 TU_AIS_VC12
Description
The TU_AIS_VC12 is an indication of TU alarms at VC-12 level. This alarm occurs when a board detects TU pointers of all 1s.
Attribute
Issue 03 (2012-07-30)
691
A Alarm Reference
Parameters

When this alarm occurs, the services in the alarmed VC-12 path are interrupted. If the services are configured with protection, protection switching is also triggered.
Possible Causes
l l l l Cause 1: Configuration data is incorrect. Cause 2: The line is faulty. Cause 3: The board at the opposite site is faulty. 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 CrossConnections of Point-to-Point Services. If... The SDH service data is incorrect The SDH service data is correct Step 2 Cause 2: The line is faulty. 1. Check whether a line alarm that causes AIS insertion is reported on the service trail.
NOTE
Then... Change the configuration data. Go to Cause 2.
For details about the line alarms that cause AIS insertion, see E.2.6 AIS Insertion.
If... The line alarm is reported No line alarms are reported
Then... Change the configuration data. Go to Step 3.
Step 3 Check whether the fault occurs at the local site or at the opposite site. For details, see 8.7.6 Setting Loopbacks for the EOS/EoPDH-Plane Ethernet Interface Board. If... The board at the opposite site is faulty
692
A Alarm Reference
If... The board at the local site is faulty 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. 1. Replace the line board at the local site. For details, see 6.3 Replacing the SDH Optical Interface Board. If... The alarm clears after the board is replaced The alarm persists after the board is replaced 2. Then... The fault is rectified. End the alarm handling. Go to the next step.
Replace the alarmed board at the local site.
----End
Related Information
None.
A.3.322 TU_AIS_VC3
Description
The TU_AIS_VC3 is a TU-3 alarm indication. The alarm is reported when a board detects TU pointers of all "1"s.
Attribute
Parameters
A Alarm Reference

The services in the alarmed TU-3 paths are interrupted. If the services are configured with protection, protection switching is triggered.
Possible Causes
l l l l Cause 1: SDH service configuration data is incorrect. Cause 2: The service path is faulty. Cause 3: The board at the opposite end is faulty. Cause 4: 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... The SDH service configuration data is incorrect The SDH service configuration data is correct 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.
NOTE
Then... Rectify the SDH service configuration data. Go to cause 2.
For the line alarms that will cause AIS insertion, see E.2.6 AIS Insertion.
If... A line alarm that will cause AIS insertion is reported No line alarm is reported
Then... Rectify the SDH service configuration data. Go to step 3.
Step 3 Follow instructions in 8.7.5 Setting a Loopback for the Packet-plane Ethernet Interface Board to identify whether the board at the local end or at the opposite end is faulty. If... The board at the opposite end is faulty The board at the local end is faulty Step 4 Cause 3: The board at the opposite end is faulty. 1. Replace the faulty board at the opposite end. Then... Go to cause 3. Go to cause 4.
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.
Issue 03 (2012-07-30)
A Alarm Reference
If... The alarm clears The alarm persists 2.
Then... No further action is required. Go to the next step.
Follow instructions in 6.10 Replacing the System Control, Switch and Timing Board to replace the system control, switching, and timing board. If... The alarm clears Then... No further action is required.
The alarm persists Follow instructions in Replacing an Alarmed Board to replace the board that reports the alarm. ----End
Related Information
None.
A.3.323 TU_LOP
Description
The TU_LOP is an alarm indicating that the TU pointer is lost. This alarm is reported if a board detects that the TU-PTR value is an invalid pointer or NDF reversion in eight consecutive frames.
Attribute
Parameters
None.

The service in the alarmed TU path is interrupted. If the services are configured with protection, protection switching is also triggered.
Possible Causes
l l Cause 1: The system control, cross-connect, and timing board is faulty. Cause 2: The tributary board is faulty.
Procedure
Step 1 Cause 1: The system control, cross-connect, and timing board is faulty. 1.
Issue 03 (2012-07-30)
Replace the system control, cross-connect, and timing board at the local end.
A Alarm Reference
If... The alarm is cleared after the board is replaced The alarm persists after the board is replaced Step 2 Cause 2: The tributary board is faulty. 1.
Then... The fault is rectified. End the alarm handling. Go to Cause 2.
Replace the board where the tributary unit resides.
----End
Related Information
None.
A.3.324 TU_LOP_VC12
Description
The TU_LOP_VC12 is an alarm indicating that the VC-12 TU pointer is lost. This alarm is reported when a board receives invalid pointers or new data flags (NDFs) in eight consecutive VC-12 frames.
Attribute
Parameters

Services in the alarmed TU path are interrupted. If the services are configured with protection, protection switching is also triggered.
Possible Causes
l
Issue 03 (2012-07-30)
Cause 1: Configuration data is incorrect.

A Alarm Reference
l l
Cause 2: The board at the opposite site is faulty. Cause 3: The board at the local site is faulty.
Procedure
Step 1 Cause 1: Configuration data is incorrect. 1. Check whether the SDH service data is correct. For details, see Creating the CrossConnections of Point-to-Point Services. If... The SDH service data is incorrect The SDH service data is correct Then... Change the configuration data. Go to Step 2.
Step 2 Check whether the fault occurs at the local site or at the opposite site. For details, see 8.7.6 Setting Loopbacks for the EOS/EoPDH-Plane Ethernet Interface Board. If... The board at the opposite site is faulty The board at the local site is faulty 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... The alarm clears after the board is replaced The alarm persists after the board is replaced 2. Then... The fault is rectified. End the alarm handling. Go to the next step. Then... Go to Cause 2. Go to Cause 3.
Replace the alarmed board at the local site.
----End
Related Information
None.
A.3.325 TU_LOP_VC3
Description
The TU_LOP_VC3 alarm indicates that a TU-3 pointer is lost. This alarm is reported if a board detects that eight consecutive VC-3 TU-PTR values are invalid or the NDF field in eight consecutive VC-3 TU-PTR values are reversed.
A Alarm Reference
Attribute
Parameters

The services in the alarmed TU-3 path are interrupted. If the services are configured with protection, protection switching is triggered.
Possible Causes
l l l Cause 1: SDH service configuration data is incorrect. Cause 2: The board at the opposite end is faulty. 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... The SDH service configuration data is incorrect The SDH service configuration data is correct Then... Rectify the SDH service configuration data. Go to step 2.
Step 2 Follow instructions in 8.7.5 Setting a Loopback for the Packet-plane Ethernet Interface Board to identify whether the board at the local end or at the opposite end is faulty. If... The board at the opposite end is faulty The board at the local end is faulty
Then... Go to cause 2. Go to cause 3.

698
A Alarm Reference
Step 3 Cause 2: The board at the opposite end is faulty. 1. 1. Replace the faulty board at the opposite end. Follow instructions in 6.3 Replacing the SDH Optical Interface Board to replace the line board at the local end. If... The alarm clears The alarm persists 2. Then... No further action is required. Go to the next step. Step 4 Cause 3: The board at the local end is faulty.
Follow instructions in 6.10 Replacing the System Control, Switch and Timing Board to replace the system control, switching, and timing board. If... The alarm clears The alarm persists Then... No further action is required. Go to the next step.
3.
Follow instructions in Replacing an Alarmed Board to replace the board that reports the alarm.
----End
Related Information
None.
A.3.326 TUNNEL_APS_DEGRADED
Description
The TUNNEL_APS_DEGRADED is an alarm indicating that a tunnel protection group degrades.
Attribute
Parameters
None.

The protection tunnel is faulty and the protection group fails. The working tunnel is unprotected.
Possible Causes
Cause: The protection tunnel in the tunnel protection group is faulty.
A Alarm Reference
Procedure
Step 1 Cause: The protection tunnel in the tunnel protection group is faulty. 1. 2. Check the status of the tunnel protection group and the port where the failed protection channel is configured. 8.3.3 Browsing Current Alarms and clear alarms on the port, if any.
----End
Related Information
None.
A.3.327 UHCS
Description
The UHCS is an alarm of uncorrected header check sequence. This alarm occurs when multiple uncorrectable bit errors exist in the cell headers.
Attribute
Parameters
None.

When the UHCS alarm occurs, some cells with multiple bit errors are detected during cell delimitation at the ATM port. Consequently, the user cells are lost.
Possible Causes
l l Cause 1: A few bit errors occur in the receive path related to the ATM port which reports the UHCS alarm. 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 the UHCS alarm. 1. 2.
Issue 03 (2012-07-30)
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. On the NMS, check whether the service is looped.
A Alarm Reference
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. 2. Perform a cold reset on the board that reports the UHCS alarm and check whether the alarm is cleared. For details, see 8.8.1 Cold Reset. Optional: If the UHCS alarm persists after the cold reset, replace the alarmed board and check whether the alarm is cleared. For details, see 6.6 Replacing the Smart E1 Interface Board.
----End
Related Information
None.
A.3.328 UP_E1_AIS
Description
The UP_E1_AIS is an alarm indication of the 2 Mbit/s uplink signal. This alarm is reported when the tributary board detects that the 2 Mbit/s uplink signal is all 1s.
Attribute
Parameters
None.

E1 signals are unavailable.
Possible Causes
l l Cause 1: The opposite equipment transmits the AIS signal. 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... The opposite equipment transmits the AIS signal
Issue 03 (2012-07-30)
Then... Rectify the fault on the opposite equipment.
701
A Alarm Reference
If... The opposite equipment does not transmit the AIS signal
Step 2 Cause 2: The receive unit of the tributary board on the local equipment is faulty. 1. Replace the alarmed board.
----End
Related Information
None.
A.3.329 V5_VCAIS
Description
The V5_VCAIS is an alarm indicating that bits 5-7 in the V5 byte of a VC-12 path are set to "1"s.
Attribute
Parameters
None.

When this alarm occurs, services are interrupted in the TU path of the board.
Possible Causes
l l Cause 1: Hardware fault alarms occur on boards of an upstream NE. Cause 2: The alarmed board is faulty.
Procedure
Step 1 Check whether any hardware fault alarms occur on boards of an upstream NE. If yes, clear them. Then, check whether the V5_VCAIS alarm is cleared. Step 2 If the alarm persists, the alarmed board is faulty. Cold Reset the board and check whether the alarm is cleared. Step 3 If the alarm persists, Replace the alarming board. ----End
A Alarm Reference
Related Information
None.
A.3.330 VC_AIS
Description
The VC_AIS is an alarm indication of the virtual channel (VC) connection. This alarm occurs when 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
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the direction of ATM connection. l 0x01: forward l 0x02: backward Parameter 2 Indicates the status of ATM connection. l 0x01: working connection l 0x00: protection connection Parameter 3 Indicates the segment and end attribute of ATM connection. l 0x01: segment l 0x02: end

l 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, though not interrupted, is not loaded with any user service. In other cases, when the local NE detects that the VC connection is interrupted, the AIS cells are inserted in the downstream direction and the RDI cells are returned to the upstream NE.
Issue 03 (2012-07-30)
A Alarm Reference
Possible Causes
l l l Cause 1: An upstream NE reports the VC_LOC, and the AIS cells are inserted to the downstream. 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. 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. 2. On the NMS, check whether the VC_LOC occurs and the ATM connections that report the VC_LOC have the same ID. 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 abnormal in the receive direction and therefore inserts AIS cells to the downstream. 1. 2. 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. If yes, clear these alarms and then the AIS insertion stops.
Step 3 Cause 3: The board on the local NE is faulty. 1. 2. Perform a cold reset on the alarmed board. If the alarm persists, replace the alarmed board.
----End
Related Information
Unidirectional Connection A complete bidirectional connection consists of two unidirectional connections: a forward connection and a backward connection. The direction of the forward and backward connections is 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 the whole 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 l l If an NE is set with the segment end point attribute, it can retrieve the alarms that are generated at the segment and end. If an NE is set with the segment point attribute, it can retrieve the alarms that are generated at a segment. If an NE is set with the end point attribute, it can retrieve the alarms that are generated at an end.
Issue 03 (2012-07-30)
A Alarm Reference
If an NE is set with the non segment end point attribute, it fails to retrieve the alarms that are generated at the segment and end.
A.3.331 VC_LOC
Description
The VC_LOC is an alarm indicating loss of connectivity on the virtual channel (VC). This alarm is reported when the CC is enabled but no cell is received within 3.5s (0.5s).
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the direction of ATM connection. l 0x01: forward l 0x02: backward Parameter 2 Indicates the status of ATM connection. l 0x01: working connection l 0x00: protection connection Parameter 3 Indicates the segment and end attribute of ATM connection. l 0x01: segment l 0x02: end l 0x03: segment and end

l l l 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. In other cases, the service is interrupted when the alarm occurs. When this alarm occurs, the system automatically inserts AIS cells to the downstream.
Issue 03 (2012-07-30)
705
A Alarm Reference
Possible Causes
l l l l Cause 1: The CC sink is enabled on the local NE, but no CC source is enabled on the upstream NE. Cause 2: No bandwidth is available on the local NE. Cause 3: On the local NE, the ATM port connected to a faulty upstream SDH path is abnormal in the receive direction. 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 upstream NE. 1. 2. 1. 2. Check whether the CC function on the local NE is activated. If yes, Deactivate the CC function on the local NE. Then, check whether the alarm is cleared. On the NMS, check whether the bandwidth allocated to the tunnel is fully used. If yes, increase the bandwidth or eliminate the sources that transmit a large amount of invalid data.
Step 2 Cause 2: No bandwidth is available on the local NE.
Step 3 Cause 3: On the local NE, the ATM port connected to a faulty upstream SDH path is abnormal in the receive direction. 1. 2. 1. 2. 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. If yes, clear these alarms and check whether the VC_LOC is cleared. Perform a cold reset on the alarmed board. If the alarm persists, replace the alarmed board.
Step 4 Cause 4: The board on the local NE is faulty.
----End
Related Information
None.
A.3.332 VC_RDI
Description
The 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 with the segment end point attribute receives the RDI cells, indicating that the downstream services are abnormal.
Issue 03 (2012-07-30)
706
A Alarm Reference
Attribute
Parameters

l 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 the local end are not affected.
Possible Causes
l l Cause 1: The VC_AIS occurs in the receive direction of the downstream VC connection. 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. 2. Check whether the VC_AIS occurs in the receive direction of the downstream VC connection. 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.

Issue 03 (2012-07-30)
Perform a cold reset on the alarmed board.

A Alarm Reference
2.
If the alarm persists, replace the alarmed board.
----End
Related Information
Unidirectional Connection A complete bidirectional connection consists of two unidirectional connections: a forward connection and a backward connection. The direction of the forward and backward connections is 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 the whole 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 l l l If an NE is set with the segment end point attribute, it can retrieve the alarms that are generated at the segment and end. If an NE is set with the segment point attribute, it can retrieve the alarms that are generated at a segment. If an NE is set with the end point attribute, it can retrieve the alarms that are generated at an end. If an NE is set with the non segment end point attribute, it fails to retrieve the alarms that are generated at the segment and end.
A.3.333 VCAT_LOA
Description
The VCAT_LOA is an alarm indicating alignment loss of virtual concatenations. This alarm is reported if a board detects that the time delays between the timeslots bound to a VCTRUNK exceed the permissible limit.
Attribute
Parameters
A Alarm Reference
Name Parameter 1 Parameter 2, Parameter 3
Meaning The value is always 0x01. Indicate the ID of the VCTRUNK path.

The virtually concatenated services are interrupted.
Possible Causes
Cause 1: The timeslots bound to a VCTRUNK travel through different physical links, so the delays between the virtually concatenated links are long.
Procedure
Step 1 Cause 1: The timeslots bound to a VCTRUNK travel through different physical links, so the delays between the virtually concatenated links are long. 1. 2. Determine the ID of the alarmed VCTRUNK path based on the alarm parameters. Check whether the transmission routes of the paths bound to a VCTRUNK are the same. If not, adjust their routes to the same.
----End
Related Information
None.
A.3.334 VCAT_LOM_VC12
Description
The VCAT_LOM_VC12 is an alarm indicating the loss of virtual concatenation multiframes in the VC-12 path. This alarm is reported if the board detects that the K4 byte of the VC-12 path does not match the expected multiframe sequence.
Attribute
Parameters
A Alarm Reference
Name Parameter 1

The alarmed path is unavailable. If the LCAS function is disabled, the services in the path are interrupted.
Possible Causes
l l l Cause 1: Bit errors occur on the line. Cause 2: The MFI field in the K4 byte sent from the opposite site is incorrect. 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... A bit error alarm occurs No bit error alarm occurs Then... Handle the alarm immediately. Go to Cause 2.
Step 2 Cause 2: The MFI field in the K4 byte sent from the opposite site is incorrect. 1. 2. Replace the board at the opposite site. For details, see 6.7 Replacing the Ethernet Interface Board. Replace the board and then check whether the alarm clears. If... The alarm clears The alarm persists Then... End the alarm handling. Go to Cause 3.
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... The VCAT_LOA alarm is reported Then... 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_LOA alarm. If... The alarm clears
Issue 03 (2012-07-30)
Then... End the alarm handling.

710
A Alarm Reference
If...
Then...
The alarm persists Replace the alarmed board at the local site. For details, see Replace the alarmed board. ----End
Related Information
None.
A.3.335 VCAT_LOM_VC3
Description
The VCAT_LOM_VC3 alarm indicates the loss of virtually concatenated multiframes in a VC-3 path. A board reports this alarm when detecting that byte H4 in the VC-3 path does not match the expected multiframe sequence.
Attribute
Parameters

The path that reports the alarm is unavailable. If the LCAS function is disabled, services are interrupted.
Possible Causes
l l l
Issue 03 (2012-07-30)
Cause 1: Bit errors occur in the line. Cause 2: The MFI field in byte K4 sent from the opposite site is incorrect. Cause 3: The delays between virtual concatenations are too long.
A Alarm Reference
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... The bit error alarms exist The bit error alarms do not exist Then... Handle the alarms immediately. Go to Cause 2.
Step 2 Cause 2: The MFI field in byte K4 sent from the opposite site is incorrect. 1. 2. Follow instructions in 6.7 Replacing the Ethernet Interface Board to replace the board at the opposite site. Replace the alarmed board and then check whether the alarm clears. If... The alarm clears The alarm persists Then... End the alarm handling. Go to Cause 3.
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 this Handle the VCAT_LOA alarm path immediately. No VCAT_LOA alarm is reported in this Go to Cause 2. path 2. Check whether the VCAT_LOM_VC3 alarm clears after handling the VCAT_LOA alarm. If... The VCAT_LOM_VC3 alarm clears Then... End the alarm handling.
The VCAT_LOM_VC3 alarm persists Follow instructions in 6.7 Replacing the Ethernet Interface Board to replace the alarmed board at the local site. ----End
Related Information
None.
A.3.336 VCAT_SQM_VC12
Description
The VCAT_SQM_VC12 is an alarm indicating the SQ number mismatch of a virtual concatenation in the VC-12 path. This alarm is reported if the board detects that the SQ of a virtual concatenation does not match the expected value.
A Alarm Reference
Attribute
Parameters

The alarmed path is unavailable. If the LCAS function is disabled, services are interrupted.
Possible Causes
l l Cause 1: Bit errors occur on certain links or certain links are faulty. 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... Bit errors or line alarms occur No bit errors or line alarms occur 2. Replace the alarmed board. Then... Clear these alarms. 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... The alarm clears after the board is replaced The alarm persists after the board is replaced ----End
Then... End the alarm handling. Contact Huawei technical support engineers for handling the alarm.
A Alarm Reference
Related Information
None.
A.3.337 VCAT_SQM_VC3
Description
The VCAT_SQM_VC3 alarm indicates that the sequence (SQ) number mismatch of a virtual concatenation in a VC-3 path. A board reports this alarm when detecting that the SQ of a virtual concatenation does not match the expected value.
Attribute
Parameters

The path that reports the alarm is unavailable. If the LCAS function is disabled, services are interrupted.
Possible Causes
l l Cause 1: Bit errors occur on a link or a link is faulty. 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... Bit error alarms or line alarms occur No bit error alarms or line alarms occur
Then... Clear these alarms. Go to Cause 2.

714
A Alarm Reference
2.
Replace the alarmed board.
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 the End the alarm handling. board is replaced The VCAT_SQM_VC3 alarm persists after the board is replaced ----End Contact Huawei technical support engineers.
Related Information
None.
A.3.338 VOLT_LOS
Description
The VOLT_LOS is an alarm indicating that the power voltage is unavailable.
Attribute
Parameters

The ODU that is connected to the IF board that reports this alarm fails to work.
Possible Causes
l l
Issue 03 (2012-07-30)
Cause 1: The output power is abnormal. Cause 2: The input power is abnormal.
A Alarm Reference
Procedure
Step 1 Cause 1: The output power is abnormal. 1. Check the power switch of the ODU. If... The power switch is turned off The power switch is turned on Then... Turn on the power switch. Go to the next step.
2.
Use the multimeter to check the IF fiber jumper, IF cable, or ODU section by section for a short circuit.
CAUTION
If the alarm is reported due to a short circuit, replace the short-circuited cable or ODU, and then replace the IF board. Otherwise, the new IF board may be damaged again. If... A short circuit exists No short circuits exist Then... Replace the short-circuited component, and then replace the alarmed IF board. Replace the alarmed IF board.
Step 2 Cause 2: The input power is abnormal. 1. Replace the alarmed IF board.
----End
Related Information
None.
A.3.339 VP_AIS
Description
The VP_AIS is an alarm indication of the virtual path (VP) connection. When a forward or backward 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.
Attribute
Issue 03 (2012-07-30)
716
A Alarm Reference
Parameters

l 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, though not interrupted, is not loaded with any user service. In other cases, when the local NE detects that the VP connection is interrupted, the AIS cells are inserted to the downstream and the RDI cells are returned to the upstream NE.
Possible Causes
l l l Cause 1: An upstream NE reports the VP_LOC, and the AIS cells are inserted to the downstream. Cause 2: On the local NE, the ATM port connected to a faulty upstream SDH path is abnormal in the receive direction and inserts AIS cells to the downstream. 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. 1. 2. On the NMS, check whether the VP_LOC occurs and the ATM connections that report the VP_LOC have the same ID. 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 abnormal in 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.
Issue 03 (2012-07-30)
A Alarm Reference
2. 1. 2.
If yes, clear these alarms and then the AIS insertion stops. Perform a cold reset on the alarmed board. If the alarm persists, replace the alarmed board.
Step 3 Cause 3: The board on the local NE is faulty.
----End
Related Information
Unidirectional Connection A complete bidirectional connection consists of two unidirectional connections: a forward connection and a backward connection. The direction of the forward and backward connections is 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 the whole 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 l l l If an NE is set with the segment end point attribute, it can retrieve the alarms that are generated at the segment and end. If an NE is set with the segment point attribute, it can retrieve the alarms that are generated at a segment. If an NE is set with the end point attribute, it can retrieve the alarms that are generated at an end. If an NE is set with the non segment end point attribute, it fails to retrieve the alarms that are generated at the segment and end.
A.3.340 VP_LOC
Description
The VP_LOC is an alarm indicating loss of connectivity on the virtual path (VP). This alarm is reported when the CC is enabled but no cell is received within 3.5s (0.5s). When any cell is received, the alarm is cleared automatically.
Attribute
Parameters
A Alarm Reference
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the direction of ATM connection. l 0x01: forward l 0x02: backward Parameter 2 Indicates the status of ATM connection. l 0x01: working connection l 0x00: protection connection Parameter 3 Indicates the segment and end attribute of ATM connection. l 0x01: segment l 0x02: end l 0x03: segment and end

l l l l 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. In other cases, the service is interrupted when the alarm occurs. When this alarm occurs, the system automatically inserts AIS cells to the downstream. The VP_LOC is suppressed when the VP_AIS occurs.
Possible Causes
l l l l Cause 1: The CC sink is enabled on the local NE, but no CC source is enabled on the upstream NE. Cause 2: No bandwidth is available on the local NE. Cause 3: On the local NE, the ATM port connected to a faulty upstream SDH path is abnormal in the receive direction. Cause 4: A certain board is faulty.
Procedure
Step 1 Cause 1: The CC sink is enabled on the local NE, but no CC source is enabled on the upstream NE. 1. 1. 2. Deactivate the CC function on the local NE. On the NMS, check whether the bandwidth allocated to the tunnel is fully used. If yes, increase the bandwidth or eliminate the sources that transmit a large amount of invalid data. Step 2 Cause 2: No bandwidth is available on the local NE.
Step 3 Cause 3: On the local NE, the ATM port connected to a faulty upstream SDH path is abnormal in the receive direction.
A Alarm Reference
1. 2.
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. If yes, clear these alarms.
Step 4 Cause 4: A certain board is faulty. 1. 2. Perform a cold reset on the alarmed board. Check whether the alarm is cleared. If not, replace the alarmed board.
----End
Related Information
None.
A.3.341 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 the segment end point attribute receives the RDI cells, indicating that the downstream services are abnormal.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the direction of ATM connection. l 0x01: forward l 0x02: backward Parameter 2 Indicates the status of ATM connection. l 0x01: working connection l 0x00: protection connection
Issue 03 (2012-07-30)
720
A Alarm Reference
Name Parameter 3
Meaning Indicates the segment and end attribute of ATM connection. l 0x01: segment l 0x02: end

l 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 AIS cells are received in a segment point of the connection, and the RDI cells are returned to the upstream VP connection.
Possible Causes
l l Cause 1: The VP_AIS occurs in the receive direction of the downstream VP connection. 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. 2. l 1. 2. ----End Check whether the VP_AIS occurs in the receive direction of the downstream VP connection. If yes, clear the VP_AIS and then check whether the VP_RDI is cleared. Perform a cold reset on the alarmed board. For details, see 8.8.1 Cold Reset. If the alarm persists, replace the alarmed board. For details, see 6.6 Replacing the Smart E1 Interface Board.
Related Information
Unidirectional Connection A complete bidirectional connection consists of two unidirectional connections: a forward connection and a backward connection. The direction of the forward and backward connections is 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 the whole 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.
A Alarm Reference
l l l l
If an NE is set with the segment end point attribute, it can retrieve the alarms that are generated at the segment and end. If an NE is set with the segment point attribute, it can retrieve the alarms that are generated at a segment. If an NE is set with the end point attribute, it can retrieve the alarms that are generated at an end. If an NE is set with the non segment end point attribute, it fails to retrieve the alarms that are generated at the segment and end.
A.3.342 W_R_FAIL
Description
The W_R_FAIL is an alarm indicating a failure of reading or writing chip register.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the ID of the chip.

Services in the alarmed path are interrupted.
Possible Causes
Cause 1: The chip register is faulty or the read/write timing is incorrect.
Procedure
Step 1 Cause 1: The chip register is faulty or the read/write timing is incorrect. 1. Replace the alarmed board.
----End
Related Information
None.
A Alarm Reference
A.3.343 WRG_BD_TYPE
Description
The WRG_BD_TYPE is an alarm indicating that the type of the board is incorrect.
Attribute
Parameters
None.

The board fails to work.
Possible Causes
l l Cause 1: Configuration data is incorrect. Cause 2: The board of an incorrect type is installed.
Procedure
Step 1 Cause 1: Configuration data is incorrect. 1. See Configuring the Logical Board to check whether the board type complies with the planning requirement. If... The board type does not meet the planning requirement The board type meets the planning requirement Step 2 Cause 2: The board of an incorrect type is installed. 1. Replace the board of an incorrect type. ----End Then... Change the configuration data. Go to Cause 2.
Related Information
None.
A.3.344 XPIC_LOS
Description
The XPIC_LOS is an alarm indicating that the XPIC compensation signals are lost.
A Alarm Reference
Attribute
Parameters
None.

Bit errors may occur in the service at the port, and the service may even be interrupted.
Possible Causes
l l l l Cause 1: Configuration data is incorrect. Cause 2: The radio link is faulty. Cause 3: The XPIC cable is faulty. 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 by using the XPIC cable.
Step 2 Cause 2: The radio link is faulty. 1. Check whether the paired board that is connected to the 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... The cable is improperly connected The cable is properly connected Then... Connect the XPIC cable properly. Go to the next step.
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 the alarmed XPIC IF board through the XPIC cable.
A Alarm Reference
If... The alarm is cleared after the board is replaced The alarm persists after the board is replaced 2.
Then... End the alarm handling. Go to the next step.
Replace the ODU that is connected to the paired XPIC IF board. If... The alarm is cleared after the ODU is replaced The alarm persists after the ODU is replaced Then... End the alarm handling. Replace the alarmed XPIC IF board.
----End
Related Information
None.
Issue 03 (2012-07-30)
725
B Abnormal Event Reference
Abnormal Event Reference
Abnormal events are important indicators when abnormalities occur on the equipment. This chapter describes all the possible important abnormal events on the OptiX RTN 950 and how to handle these events. B.1 Major Abnormal Events List Abnormal events are important indicators when abnormalities occur on the equipment. This chapter describes all the possible important abnormal events on the OptiX RTN 950 and how to handle these events. B.2 Abnormal Events and Handling Procedures This chapter describes all the important abnormal events on the OptiX RTN 950 in an alphabetical order and how to handle these abnormal performance events.
Issue 03 (2012-07-30)
726
B.1 Major Abnormal Events List

Abnormal events are important indicators when abnormalities occur on the equipment. This chapter describes all the possible important abnormal events on the OptiX RTN 950 and how to handle these events. Table B-1 Major performance event list Event Name B.2.1 IF 1+1 Protection Switching 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 Protection Group B.2.6 Reporting of PW APS Switching Events B.2.7 System Control Board Switching B.2.8 RMON Performance Value Below the Lower Limit B.2.9 RMON Performance Value Above the Upper Limit CST and CSH EM6FA, EM6TA, EFP8, EMS6, EM6F and EM6T Source CST and CSH
B.2 Abnormal Events and Handling Procedures

This chapter describes all the important abnormal events on the OptiX RTN 950 in 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 Major Type Service
Issue 03 (2012-07-30)
727
Parameters
Name Protection Group ID Current Working Board Slot Current Working Board Sub Slot Meaning Indicates the ID of the protection group where the IF 1+1 protection switching occurs. Indicates the slot ID of the current working board. Indicates the sub slot ID of the current working board. The value is always 0xff. Current Working Port No. Current Active Board Indicates the ID of the working port. Indicates the current working board. l Active on working board l Active on protection board Active Board Status Indicates the current state of the working board. l Normal l Failed l MW_RDI l Unknown Standby Board Status Indicates the current status of the protection board. l Normal l Failed l MW_RDI l Unknown Switching Request Indicates the type of an IF 1+1 protection switching request. l No request l Automatic switching l Manual switching l Forced switching l Lockout of switching l Wait-to-restore l RDI switching
NOTE
The parameter names and parameter values may vary with the version of the NMS.
Issue 03 (2012-07-30)
728
Impact on System
l l During the HSB protection switching, services are interrupted. After the HSB switching is complete, the services are restored to normal. During the HSM protection switching, no bit errors occur and the services are not affected.
Related Alarms
When the IF 1+1 protection switching occurs, the RPS_INDI alarm is reported.
Possible Causes
l The possible causes of the HSB protection switching are as follows: The hardware of the ODU or IF unit at the local end is faulty. The working 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, forced switching, 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, MW_BER_SD, B1_SD(IF1).
Procedure
Step 1 Rectify the fault according to the switching request type indicated by the parameter and the description in RPS_INDI. ----End
B.2.2 N+1 Protection Switching

Description
This abnormal event indicates that the N+1 protection switching occurs on the equipment.
Attribute
Issue 03 (2012-07-30)
729
Parameters
Name Protection Group ID Path Name ID Switching Request Meaning Indicates the ID of the protection group where the IF N+1 protection switching occurs. Indicates the ID of the path where the IF N+1 protection switching occurs. Indicates the type of an IF N+1 protection switching request. l Lockout of protection channel l Forced switching l SF switching l SD switching l Manual switching l Wait-to-restore l Exercise l No request Switching Status Indicates the state of an N+1 protection group. l Protocol unstarted l Idle status l Switching status l Protocol starting Protected Unit Indicates the ID of the protected channel. The ID is 0xff if no switching is performed. Switching Local/Remote End Indication Indicates the local or remote switching. l Local end l Remote end The switching status reason is changed Indicates the cause of the IF N+1 protection switching. l Local request l External command l K-byte request l Timer expiry
NOTE
Issue 03 (2012-07-30)
730
Impact on System
During the N+1 protection switching (not more than 50 ms), the services are interrupted. After the N+1 switching is complete, the services are restored to normal. After the switching starts and before the switching is complete, the extra services are interrupted.
NOTE
If the IF N+1 protection switching is caused by exercise switching, service signals are not switched actually because the exercise switching is used to check whether the NE can run the N+1 protocol normally.
Related Alarms
When the IF N+1 protection switching occurs, the NP1_SW_INDI alarm is reported.
Possible Causes
l 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 the HARD_BAD or BD_STATUS alarm is reported. The MW_LOF, R_LOC, R_LOF, R_LOS, MS_AIS, or B2_EXC alarm is reported on the working path.
Procedure
Step 1 Rectify the fault according to the switching request type and the switching cause indicated by the parameters. If... The switching is caused by the external switching Then... Find the cause of the external switching, and then release the external switching immediately.
The switching is caused by the automatic Clear the alarm that triggers the automatic switching switching. ----End
B.2.3 SNCP Switching

Description
This abnormal event indicates that the SDH SNCP switching occurs in the service that is configured with the SNCP.
Issue 03 (2012-07-30)
731
Attribute
Parameters
Name Source Sink Status Meaning Indicates the service source of the SNCP protection group. Indicates the service sink of the SNCP protection group. Indicates the current working path. l Working at protection channel l Working at working channel Switching Status Indicates the switching status. l Manual to standby l Force to active l Force to standby l Lockout switching l SF switching l SD switching l Wait-to-restore l Idle Working Channel Current Status Indicates the current status of the SNCP working path. l Normal l SD l SF Protection Channel Current Status Indicates the current status of the SNCP protection path. l Normal l SD l SF
NOTE
Issue 03 (2012-07-30)
732
Impact on System
When the SNCP switching occurs, you must find the cause. If the related link is faulty, recover the link immediately. Ensure that the states of the SNCP working path and the SNCP protection path are normal.
Possible Causes
l 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 (Optional condition), 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... The SDH SNCP switching is automatically triggered The SDH SNCP switching is manually triggered Then... Rectify the fault according to the related alarm, and eliminate the conditions of the automatic switching. Find the cause of the manual switching, and then release the manual switching immediately.
----End
B.2.4 Linear MSP Switching

Abnormal Event Description
This abnormal event indicates that a linear MSP switching occurs in the service that is configured with the MSP.
Abnormal Event Attributes

Level Major Type Service
Issue 03 (2012-07-30)
733
Abnormal Event Parameters

Parameter Name Indicates the ID of the protection group. Current working path Definition Indicates the ID of the protection group where a linear MSP switching occurs. Indicates the current working path of the linear MSP group. l Working unit l Protection unit Switching request type Indicates the type of a linear MSP switching request. l Locked switching l Forced switching l SF switching l SD switching l Manual switching l Wait-to-restore l Exercise l Reverse request l Non-revertive request l No request Switching status Indicates the switching status. l Protocol not started l Idle l Switching l Protocol being started Remote/local end indication Indicates the remote or local end. l No remote/local end l Local end l Remote end Cause of switching status change Indicates the cause of switching status change. l Local request l External command l K-byte request l Timer expiry
NOTE
Issue 03 (2012-07-30)
734
Impact on System
l 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 and before the switching is complete, the extra services are interrupted. Troubleshooting measures need to be taken immediately when an MSP switching occurs because 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 Causes
l l An external switching command is issued to trigger manual, forced, or exercise switching. An automatic switching occurs. After the R_LOS, R_LOF, MS_AIS, B2_EXC, B2_SD, B3_EXC, B3_SD, HP_TIM (in the case of VC-4 services), HP_UNEQ (in the case of VC-4 services), TU_AIS (in the case of VC-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 alarm is reported. l The hardware or line is faulty.
Procedure
Step 1 On the NMS, query the switching type and the protection group ID. Step 2 Rectify the fault according to the switching request type. If... The switching is caused by external switching The switching is an automatic switching Then... Find out the cause and clear the switching immediately. Clear the relevant alarm, and rectify the hardware 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
Issue 03 (2012-07-30)
735
Parameters
Name Protection Group ID APS Protection Group Switching Status Meaning ID of the protection group whose APS status is changed Current working status of the APS protection group l Working path l Protection path APS Protection Group Protocol Status Working Path Status of the APS Protection Group APS protection group protocol status Working path status of the APS protection group: l Valid l Invalid Protection Path Status of the APS Protection Group Protection path status of the APS protection group: l Valid l Invalid
NOTE
The 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 services are restored. After the switching starts and before the switching is complete, the extra services are interrupted.
Related Alarms
None.
Possible Causes
l l An external switching command (for example, manual switching) is issued. 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, or MPLS_TUNNEL_UNKNOWN alarm occurs on the working path.
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 and the switching cause indicated by the parameters. If... The switching is an external switching Then... Find the cause of the external switching, and then clear manual switching immediately.
The switching is an automatic switching Handle the relevant alarms first. ----End
B.2.6 Reporting of PW APS Switching Events

Description
This abnormal event indicates that a PW APS protection group switches.
Attribute
Parameters
Name Protection Group ID APS Protection Group Switching Status Meaning ID of the protection group whose APS status is changed Current working status of the APS protection group l Working path l Protection path APS Protection Group Protocol Status Working Path Status of the APS Protection Group APS protection group protocol status Working path status of the APS protection group: l Valid l Invalid Protection Path Status of the APS Protection Group Protection path status of the APS protection group: l Valid l Invalid
NOTE
The parameter names and parameter values may vary according to the version of the NMS.
Issue 03 (2012-07-30)
737

During the switching, the services are interrupted. After the switching is complete, the services are restored. After the switching starts and before the switching is complete, the extra services are interrupted.
Related Alarms
None.
Possible Causes
l l An external switching command (for example, manual switching) is issued. 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, or MPLS_PW_UNKNOWN alarm occurs on the working path.
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 and the switching cause indicated by the parameters. If... The switching is an external switching Then... Find the cause of the external switching, and then clear manual switching immediately.
The switching is an automatic switching Handle the relevant alarms first. ----End
B.2.7 System Control Board Switching

Description
This abnormal event indicates that the system control boards are switched when the working system control board on the equipment that is configured with the 1+1 protection becomes faulty.
Attribute
Severity Major Type Equipment
Issue 03 (2012-07-30)
738
Parameters
Name Group ID Protection Type Working Unit Protection Unit Current Working Unit Meaning Indicates the group ID. Cross-connect board protection. Indicates the slot ID of the current working board. Indicates the slot ID of the current protection board. Indicates the current status of the board. l Work at protection unit l Work at working unit Switching Type Indicates the switching type. Manual Switching
NOTE
Impact on System
If the system control boards are switched because the original working system control board is faulty, rectify the fault on the original working system control board immediately. Otherwise, the services are interrupted if the current working system control board becomes faulty.
Possible Causes
l l The switching is manually triggered. The switching is automatically triggered. Generally, the switching is automatically triggered when the hardware of the board becomes faulty. Hence, focus on the following alarms reported on the original working system control board: HARD_BAD.
Procedure
Step 1 On the NMS, check whether the manual switching operation is performed. If... The manual switching operation is performed on the NMS No manual switching operations are performed on the NMS Then... Find the cause of the manual switching, and then release the manual switching immediately. Go to the next step.
Step 2 On the NMS, check whether any alarms indicating the board hardware fault are reported. If yes, clear the alarms and rectify the fault. ----End
B.2.8 RMON Performance Value Below the Lower Limit

Description
This abnormal event indicates that the current RMON performance value is lower than the preset lower limit.
Attribute
Severity Minor Type Communication
Parameters
Name Performance ID Current Performance Value Lower Limit Meaning Indicates the ID of the current RMON performance event. Indicates the value of the current RMON performance event. Indicates the lower limit of the current RMON performance event.
Impact on System
Different abnormal performance events have different impacts on the system. For details, see D.4 RMON Events and Handling Procedures.
Related Alarms
Different alarms are reported when different RMON performance values are lower than the lower limits. For details, see D.4 RMON Events and Handling Procedures.
Possible Causes
The lower limit of a performance event is set to a non-zero value.
Procedure
Step 1 Set the lower limit of the performance event to 0. ----End
Issue 03 (2012-07-30)
740
B.2.9 RMON Performance Value Above the Upper Limit

Description
This abnormal event indicates that the current RMON performance value is higher than the preset upper limit.
Attribute
Severity Minor Type Communication
Parameters
Name Performance ID Current Performance Value Upper Limit Meaning Indicates the ID of the current RMON performance event. Indicates the value of the current RMON performance event. Indicates the upper limit of the current RMON performance event.
Impact on System
Different abnormal performance events have different impacts on the system. For details, see D.4 RMON Events and Handling Procedures.
Related Alarms
Different alarms are reported when different RMON performance values are higher than the upper limits. For details, see D.4 RMON Events and Handling Procedures.
Possible Causes
When the performance values of different abnormal RMON performance events are higher than the upper limits, the causes are different. For details, see D.4 RMON Events and Handling Procedures.
Procedure
Step 1 See D.4 RMON Events and Handling Procedures to handle different abnormal performance events. ----End
C Performance Event Reference
Performance Event Reference
Performance events are important indicators when the equipment performance changes. This chapter describes all the possible performance events on the and how to handle these 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 the OptiX RTN 950. C.2 Performance Events (by Logical Board) This part lists all the performance events that are reported by each board. C.3 Performance Events and Handling Procedures Based on the type of a performance event, this chapter describes all the performance events on the and how to handle these performance events.
Issue 03 (2012-07-30)
742
C.1 Performance Events (by Event Type)

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

SDH/PDH performance events are classified into six categories: pointer justification, regenerator section error, multiplex section error, PW carried ATM, CSE and L2VPN Services, higher order path error, lower order path error, E1 Error Performance Eventsand E1 line side code violation. Table C-1 Pointer Justification Performance Events Event Name AUPJCHIGH AUPJCLOW AUPJCNEW TUPJCHIGH TUPJCLOW TUPJCNEW Description Indicates the count of positive AU pointer justifications. Indicates the count of negative AU pointer justifications. Indicates the count of new AU pointer justifications. Indicates the count of positive TU pointer justifications. Indicates the count of negative TU pointer justifications. Indicates the count of new TU pointer justifications.
Table C-2 Regenerator Section Error Performance Events Event Name RSBBE RSES RSSES RSUAS Description Indicates the regenerator section background block error. Indicates the regenerator section errored second. Indicates the regenerator section severely errored second. Indicates the regenerator section unavailable second.
Issue 03 (2012-07-30)
743
Event Name RSCSES RSOFS RSOOF
Description Indicates the regenerator section consecutive severely errored second. Indicates the regenerator section out-offrame second. Indicates the count of regenerator section outof-frame events.
NOTE
In the case of PDH radio, regenerator section bit error performance events also exist and they are detected according to the overheads used for detecting frame alignment and bit errors in the PDH microwave frames.
Table C-3 Multiplex Section Error Performance Events Event Name MSBBE MSES MSSES MSCSES MSUAS MSFEBBE MSFEES MSFESES MSFECSES MSFEUAS Description Indicates the multiplex section background block error. Indicates the multiplex section errored second. Indicates the multiplex section severely errored second. Indicates the multiplex section consecutive severely errored second. Indicates the multiplex section unavailable second. Indicates the multiplex section far end background block error. Indicates the multiplex section far end errored second. Indicates the multiplex section far end severely errored second. Indicates the multiplex section far end consecutive severely errored second. Indicates the multiplex section far end unavailable second.
Issue 03 (2012-07-30)
744
Table C-4 Higher Order Path Error Performance Events Event Name HPBBE HPES HPSES HPCSES HPUAS HPFEBBE HPFEES HPFESES HPFECSES HPFEUAS Description Indicates the higher order path background block error. Indicates the higher order path errored second. Indicates the higher order path severely errored second. Indicates the higher order path consecutive severely errored second. Indicates the higher order path unavailable second. Indicates the higher order path far end background block error. Indicates the higher order path far end errored second. Indicates the higher order path far end severely errored second. Indicates the higher order path far end consecutive severely errored second. Indicates the higher order path far end unavailable second.
Table C-5 Lower Order Path Error Performance Events Event Name LPBBE LPES LPSES LPCSES LPUAS LPFEBBE Description Indicates the lower order path background block error. Indicates the lower order path errored second. Indicates the lower order path severely errored second. Indicates the lower order path consecutive severely errored second. Indicates the lower order path unavailable second. Indicates the lower order path far end background block error.
Issue 03 (2012-07-30)
745
Event Name LPFEES LPFESES LPFECSES LPFEUAS
Description Indicates the lower order path far end errored second. Indicates the lower order path far end severely errored second. Indicates the lower order path far end consecutive severely errored second. Indicates the lower order far end unavailable second.
Table C-6 E1 Line Side Code Violation Performance Events Event Name E1_LCV_SDH E1_LLOSS_SDH E1_LES_SDH E1_LSES_SDH Description Indicates the count of E1 line side code violations. Indicates the E1 line side loss-of-signal second. Indicates the E1 line side code violation errored second. Indicates the E1 line side code violation severely errored second.
Table C-7 E1 Error Performance Events Event Name E1_BBE E1_ES E1_SES E1_CSES E1_UAS Description Indicates the E1 background block error. Indicates the E1 errored second. Indicates the E1 severely errored second. Indicates the E1 consecutive severely errored second. Indicates the E1 unavailable second.
Table C-8 PW carried ATM, CSE and L2VPN Services Performance Events Event Name MPLS_PW_LS Description Indicates the packet loss seconds of PW carried services.
746
Issue 03 (2012-07-30)
Event Name MPLS_PW_SLS MPLS_PW_CSLS MPLS_PW_UAS
Description Indicates the severe packet loss seconds of PW carried services. Indicates the consecutive severe packet loss seconds of PW carried services. Indicates the unavailable seconds of PW carried services.
NOTE
Only the SL92CSH board supports MPLS-TP OAM.
C.1.2 Radio Performance Events

The radio performance events are performance events of the radio link bit errors, ATPC, AM, and power. Table C-9 Radio power performance events Event Name TSL_MAX TSL_MIN TSL_CUR TSL_AVG RSL_MAX RSL_MIN RSL_CUR RSL_AVG TLHTT Description Maximum value of radio transmit signal level Minimum value of radio transmit signal level Current value of radio transmit signal level Average value of radio transmit signal level Maximum value of radio receive signal level Minimum value of radio receive signal level Current value of radio receive signal level Average value of radio receive signal level The duration when the ODU at the local end has a transit power higher than the upper threshold The duration when the ODU at the local end has a transit power higher than the lower threshold The duration when the ODU at the local end has a receive power lower than the upper threshold The duration when the ODU at the local end has a receive power lower than the lower threshold
TLLTT
RLHTT
RLLTT
Issue 03 (2012-07-30)
747
Table C-10 FEC performance events Event Name FEC_BEF_COR_ER FEC_UNCOR_BLOCK_CNT FEC_COR_BYTE_CNT Description FEC bit error rate before correction FEC uncorrected block count The number of bytes that are corrected through the FEC
Table C-11 Radio link error performance events Event Name IF_BBE IF_ES IF_SES IF_UAS IF_CSES IF_BER Description Radio link background block errors Radio link errored seconds Radio link severely errored seconds Radio link unavailable second Radio link consecutive severely errored seconds Radio link bit error rate
Table C-12 ATPC performance events Event Name ATPC_P_ADJUST ATPC_N_ADJUST Description Positive ATPC adjustment Negative ATPC adjustment
Table C-13 AM performance events Event Name QPSKWS QAMWS16 QAMWS32 QAMWS64 QAMWS128 QAMWS256 QAMWS512
Issue 03 (2012-07-30)
Description Working time of the QPSK mode Working time of the 16QAM mode Working time of the 32QAM mode Working time of the 64QAM mode Working time of the 128QAM mode Working time of the 256QAM mode Working time of the 512QAM mode
Event Name QAMWS1024 QPSK_S_WS QAM_S_WS16 QAM_L_WS512 QAM_L_WS1024 AMDOWNCNT AMUPCNT
Description Working time of the 1024QAM mode Working time of the QPSKSTRONG mode Working time of the 16QAMSTRONG mode Working time of the 512QAMLIGHT mode Working time of the 1024QAMLIGHT mode Count of the downshift of the AM scheme Count of the upshift of the AM scheme
Table C-14 XPIC performance events Event Name XPIC_XPD_VALUE Description XPIC XPD value
Table C-15 IF 1+1 protection group error performance events Event Name PG_IF_BBE PG_IF_ES PG_IF_SES PG_IF_UAS PG_IF_CSES Description IF 1+1 protection group background block errors IF 1+1 protection group errored seconds IF 1+1 protection group severely errored seconds IF 1+1 protection group unavailable second IF 1+1 protection group consecutive severely errored seconds
Table C-16 IF port error performance events Event Name IF_SNR_MAX IF_SNR_MIN IF_SNR_AVG Description Maximum signal to noise ratio Minimum signal to noise ratio Average signal to noise ratio
Issue 03 (2012-07-30)
749
C.1.3 Other Performance Events

In addition to the SDH/PDH and radio performance events, the OptiX RTN 950 supports performance events of the optical power, the temperature, laser, PW and clock. Table C-17 Optical power performance events Event Name TPLMAX TPLMIN TPLCUR RPLMAX RPLMIN RPLCUR Description Maximum value of transmit optical power Minimum value of transmit optical power Current value of transmit optical power Maximum value of receive optical power Minimum value of receive optical power Current value of receive optical power
Table C-18 Board temperature performance events Event Name BDTEMPMAX BDTEMPMIN BDTEMPCUR Description Maximum value of board temperature Minimum value of board temperature Current value of board temperature
Table C-19 Laser temperature performance events Event Name OSPITMPMAX OSPITMPMIN OSPITMPCUR Description Maximum temperature of a laser core Minimum temperature of a laser core Current temperature of a laser core
Table C-20 Transmitted bias current performance events Performance Event Name TLBMAX TLBMIN TLBCUR Description Maximum transmitted bias current of the laser Minimum transmitted bias current of the laser Current transmitted bias current of the laser
Issue 03 (2012-07-30)
750
Table C-21 Clock performance events Event Name MAXFREQDEV MINFREQDEV AVGFREQDEV CURPOSITIVEPDV MAXPOSITIVEDELAY MINPOSITIVEDELAY AVGPOSITIVEDELAY MAXPHASEOFFSET MINPHASEOFFSET AVGPHASEOFFSET MAXMEANPATHDELAY MINMEANPATHDELAY AVGMEANPATHDELAY Description Maximum frequency deviation Minimum frequency deviation Average frequency deviation Current positive PDV Maximum positive delay Minimum positive delay Average positive delay Maximum phase offset Minimum phase offset Average phase offset Maximum path delay Minimum path delay Average path delay
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. Table A-2 shows the logical boards corresponding to all physical boards
Table C-22 Mappings between the physical boards and logical boards Physical Board CST CSH AUX IF1 IFU2 IFX2 ISU2
Issue 03 (2012-07-30)
Logical Board CST in the same slot CSH in the same slot AUX in the same slot IF1 in the same slot IFU2 in the same slot IFX2 in the same slot ISU2 in the same slot
751
Physical Board ISX2 ISV3 SL1D SL1DA EM6T EM6TA EM6F EM6FA EG4 EG4P EFP8 EMS6 SP3S SP3D ML1 MD1 CQ1 PIU FAN ODU
Logical Board ISX2 in the same slot ISV3 in the same slot SL1D in the same slot SL1DA in the same slot EM6T in the same slot EM6TA in the same slot EM6F in the same slot EM6FA in the same slot EG4 in the same slot EG4P in the same slot EFP8 in the same slot EMS6 in the same slot SP3S in the same slot SP3D in the same slot ML1 in the same slot MD1 in the same slot CQ1 in the same slot PIU in the same slot FAN in the same slot ODU in the slot whose number is 20 plus the slot number for the IF board that is connected to the ODU
C.2.1 CST/CSH
The CST/CSH board reports only the board temperature performance events and IF 1+1 protection group error performance events. Table C-23 Board temperature performance events Event Name BDTEMPMAX BDTEMPMIN Description Maximum value of board temperature Minimum value of board temperature
Issue 03 (2012-07-30)
752
Event Name BDTEMPCUR
Description Current value of board temperature
Table C-24 IF 1+1 protection group error performance events Event Name PG_IF_BBE PG_IF_ES PG_IF_SES PG_IF_UAS PG_IF_CSES Description IF 1+1 protection group background block errors IF 1+1 protection group errored seconds IF 1+1 protection group severely errored seconds IF 1+1 protection group unavailable second IF 1+1 protection group consecutive severely errored seconds
Table C-25 Clock performance events (only CSH supports) Event Name MAXFREQDEV MINFREQDEV AVGFREQDEV CURPOSITIVEPDV MAXPOSITIVEDELAY MINPOSITIVEDELAY AVGPOSITIVEDELAY MAXPHASEOFFSET MINPHASEOFFSET AVGPHASEOFFSET MAXMEANPATHDELAY MINMEANPATHDELAY AVGMEANPATHDELAY Description Maximum frequency deviation Minimum frequency deviation Average frequency deviation Current positive PDV Maximum positive delay Minimum positive delay Average positive delay Maximum phase offset Minimum phase offset Average phase offset Maximum path delay Minimum path delay Average path delay
Issue 03 (2012-07-30)
753
Table C-26 PW carried service performance events (only CSH supports) Event Name MPLS_PW_LS MPLS_PW_SLS MPLS_PW_CSLS MPLS_PW_UAS Description Packet loss seconds of PW carried services Severe packet loss seconds of PW carried services Consecutive severe packet loss seconds of PW carried services Unavailable seconds of PW carried services
C.2.2 IF1
The 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-27 Pointer justification performance events Event Name AUPJCHIGH AUPJCLOW AUPJCNEW Description Count of positive AU pointer justification Count of negative AU pointer justification Count of new AU pointer justifications
Table C-28 Regenerator section error performance events Event Name RSBBE RSES RSSES RSUAS RSCSES RSOFS RSOOF Description Regenerator section block of background error Regenerator section errored second Regenerator section severely errored second Regenerator section unavailable second Regenerator section consecutive severely errored second Regenerator section out-of-frame second Regenerator section out of frame
Issue 03 (2012-07-30)
754

NOTE
The regenerator section error performance events also occur in the case of the PDH radio. The PDH radio frame is detected through the overheads that are used for frame location and bit error detection.
Table C-29 Multiplex section error performance events Event Name MSBBE MSES MSSES MSCSES MSUAS MSFEBBE MSFEES MSFESES MSFECSES MSFEUAS Description Multiplex section block of background error Multiplex section errored second Multiplex section severely errored second Multiplex section consecutive severely errored second Multiplex section unavailable second Multiplex section far end block of background error Multiplex section far end errored second Multiplex section far end severely errored second Multiplex section far end consecutive severely errored second Multiplex section far end unavailable second
Table C-30 Higher order path error performance events Event Name HPBBE HPES HPSES HPCSES HPUAS HPFEBBE HPFEES HPFESES Description Higher order path background block error Higher order path errored second Higher order path severely errored second Higher order path consecutive severely errored second Higher order path unavailable second Higher order path far end background block error Higher order path far end errored second Higher order path far end severely errored second
Issue 03 (2012-07-30)
755
Event Name HPFECSES HPFEUAS
Description Higher order path far end consecutive severely errored second Higher order path far end unavailable second
Radio Performance Events

Table C-31 FEC performance events Event Name FEC_BEF_COR_ER FEC_COR_BYTE_CNT Description FEC bit error rate before correction Frame count incorrect by FEC
Other Performance Events

C.2.3 IFU2/ISU2
The IFU2/ISU2 board reports three types of performance events: PDH performance events, radio performance events, and board temperature performance events.
Issue 03 (2012-07-30)
756
SDH Performance Events (Only reported by ISU2)

Table C-36 Multiplex section error performance events Event Name MSBBE MSES MSSES MSCSES MSUAS MSFEBBE MSFEES MSFESES Description Multiplex section block of background error Multiplex section errored second Multiplex section severely errored second Multiplex section consecutive severely errored second Multiplex section unavailable second Multiplex section far end block of background error Multiplex section far end errored second Multiplex section far end severely errored second
Issue 03 (2012-07-30)
Event Name MSFECSES MSFEUAS
Description Multiplex section far end consecutive severely errored second Multiplex section far end unavailable second
Table C-37 Higher order path error performance events Event Name HPBBE HPES HPSES HPCSES HPUAS HPFEBBE HPFEES HPFESES HPFECSES HPFEUAS Description Higher order path background errored block Higher order path errored second Higher order path severely errored second Higher order path consecutive severely errored second Higher order path unavailable second Higher order path far end background errored block Higher order path far end errored second Higher order path far end severely errored second Higher order path far end consecutive severely errored second Higher order path far end unavailable second
PDH Performance Events

Table C-38 Lower order path error performance events Event Name LPBBE LPES LPSES LPCSES LPUAS Description Lower order path block of background error Lower order path errored second Lower order path severely errored second Lower order path continuous severe bit error second Lower order path unavailable second
Issue 03 (2012-07-30)
758
Event Name LPFEBBE LPFEES LPFESES LPFECSES LPFEUAS
Description Lower order path far end block of background error Lower order path far end errored second Lower order path far end severely errored second Lower order path far end consecutive severely errored second Lower order far end unavailable second

Table C-39 FEC performance events Event Name FEC_BEF_COR_ER FEC_UNCOR_BLOCK_CNT Description FEC bit error rate before correction FEC uncorrected block count
Table C-41 AM performance events Event Name QPSKWS QAMWS16 QAMWS32

Issue 03 (2012-07-30)
Description Working time of the QPSK mode Working time of the 16QAM mode Working time of the 32QAM mode
Event Name QAMWS64 QAMWS128 QAMWS256 AMDOWNCNT AMUPCNT
Description Working time of the 64QAM mode Working time of the 128QAM mode Working time of the 256QAM mode Count of the downshift of the AM scheme Count of the upshift of the AM scheme

C.2.4 IFX2/ISX2
The IFX2/ISX2 board reports three types of performance events: SDH\PDH performance events, radio performance events, and board temperature performance events.
SDH Performance Events (Only reported by ISX2)

Table C-44 Pointer justification performance events Event Name AUPJCHIGH AUPJCLOW
Issue 03 (2012-07-30)
Description Count of positive AU pointer justification Count of negative AU pointer justification

Event Name AUPJCNEW
Description Count of new AU pointer justifications
Issue 03 (2012-07-30)
761

Table C-48 Lower order path error performance events Event Name LPBBE LPES LPSES LPCSES LPUAS LPFEBBE LPFEES LPFESES LPFECSES Description Lower order path block of background error Lower order path errored second Lower order path severely errored second Lower order path continuous severe bit error second Lower order path unavailable second Lower order path far end block of background error Lower order path far end errored second Lower order path far end severely errored second Lower order path far end consecutive severely errored second
Issue 03 (2012-07-30)
762
Event Name LPFEUAS
Description Lower order far end unavailable second

Table C-51 AM performance events Event Name QPSKWS QAMWS16 QAMWS32 QAMWS64 QAMWS128 QAMWS256 AMDOWNCNT AMUPCNT Description Working time of the QPSK mode Working time of the 16QAM mode Working time of the 32QAM mode Working time of the 64QAM mode Working time of the 128QAM mode Working time of the 256QAM mode Count of the downshift of the AM scheme Count of the upshift of the AM scheme
Issue 03 (2012-07-30)
763

C.2.5 SL1D/SL1DA
The SL1D/SL1DA board reports three types of performance events: SDH performance events, and optical power performance events.
SDH Performance Events

Issue 03 (2012-07-30)
764
Table C-58 Higher order path error performance events Event Name HPBBE HPES
Issue 03 (2012-07-30)
Description Higher order path background errored block Higher order path errored second
Event Name HPSES HPCSES HPUAS HPFEBBE HPFEES HPFESES HPFECSES HPFEUAS
Description Higher order path severely errored second Higher order path consecutive severely errored second Higher order path unavailable second Higher order path far end background errored block Higher order path far end errored second Higher order path far end severely errored second Higher order path far end consecutive severely errored second Higher order path far end unavailable second

Table C-59 Optical power performance events Event Name TPLMAX TPLMIN TPLCUR RPLMAX RPLMIN RPLCUR Description Maximum value of transmit optical power Minimum value of transmit optical power Current value of transmit optical power Maximum value of receive optical power Minimum value of receive optical power Current value of receive optical power
C.2.6 EM6T
The EM6T board reports only the board temperature performance events. Table C-60 Board temperature performance events Event Name BDTEMPMAX BDTEMPMIN BDTEMPCUR
Issue 03 (2012-07-30)
Description Maximum value of board temperature Minimum value of board temperature Current value of board temperature
766
C.2.7 EM6TA
The EM6TA board reports only the board temperature performance events. Table C-61 Board temperature performance events Event Name BDTEMPMAX BDTEMPMIN BDTEMPCUR Description Maximum value of board temperature Minimum value of board temperature Current value of board temperature
C.2.8 EM6F
The EM6F board reports optical power performance events and board temperature performance events. Table C-62 Optical power performance events Event Name TPLMAX TPLMIN TPLCUR RPLMAX RPLMIN RPLCUR Description Maximum value of transmit optical power Minimum value of transmit optical power Current value of transmit optical power Maximum value of receive optical power Minimum value of receive optical power Current value of receive optical power
Issue 03 (2012-07-30)
767
C.2.9 EM6FA
The EM6FA board reports optical power performance events and board temperature performance events. Table C-64 Optical power performance events Event Name TPLMAX TPLMIN TPLCUR RPLMAX RPLMIN RPLCUR Description Maximum value of transmit optical power Minimum value of transmit optical power Current value of transmit optical power Maximum value of receive optical power Minimum value of receive optical power Current value of receive optical power
C.2.10 EFP8
The EFP8 board reports the temperature and PDH performance events. Table C-66 Board temperature performance events Event Name BDTEMPMAX BDTEMPMIN BDTEMPCUR Description Maximum value of board temperature Minimum value of board temperature Current value of board temperature
Table C-67 Lower order path error performance events Event Name LPBBE
Issue 03 (2012-07-30)
Description Lower order path block of background error

Event Name LPES LPSES LPCSES LPUAS LPFEBBE LPFEES LPFESES LPFECSES LPFEUAS
Description Lower order path errored second Lower order path severely errored second Lower order path continuous severe bit error second Lower order path unavailable second Lower order path far end block of background error Lower order path far end errored second Lower order path far end severely errored second Lower order path far end consecutive severely errored second Lower order far end unavailable second
C.2.11 EMS6
The EMS6 board reports the SDH performance events, board temperature performance events, laser temperature performance events, and optical power performance events. Table C-68 Lower order path error performance events Event Name LPBBE LPES LPSES LPCSES LPUAS LPFEBBE LPFEES LPFESES LPFECSES Description Lower order path block of background error Lower order path errored second Lower order path severely errored second Lower order path continuous severe bit error second Lower order path unavailable second Lower order path far end block of background error Lower order path far end errored second Lower order path far end severely errored second Lower order path far end consecutive severely errored second
Issue 03 (2012-07-30)
769
Table C-69 Higher order path error performance events Event Name HPBBE HPES HPSES HPCSES HPUAS HPFEBBE HPFEES HPFESES HPFECSES Description Higher order path background errored block Higher order path errored second Higher order path severely errored second Higher order path consecutive severely errored second Higher order path unavailable second Higher order path far end background errored block Higher order path far end errored second Higher order path far end severely errored second Higher order path far end consecutive severely errored second
Table C-71 Laser temperature performance events Event Name OSPITMPMAX OSPITMPMIN OSPITMPCUR Description Maximum temperature of a laser core Minimum temperature of a laser core Current temperature of a laser core
Table C-72 Optical power performance events Event Name TPLMAX Description Maximum value of transmit optical power
Issue 03 (2012-07-30)
770
Event Name TPLMIN TPLCUR RPLMAX RPLMIN RPLCUR
Description Minimum value of transmit optical power Current value of transmit optical power Maximum value of receive optical power Minimum value of receive optical power Current value of receive optical power
C.2.12 SP3S/SP3D
The SP3S/SP3D board reports only the PDH performance events. Table C-73 Pointer justification performance events Event Name TUPJCHIGH TUPJCLOW TUPJCNEW Description Count of positive TU pointer justifications Count of negative TU pointer justifications Count of new TU pointer justifications
Table C-74 Lower order path error performance events Event Name LPBBE LPES LPSES LPCSES LPUAS LPFEBBE LPFEES LPFESES LPFECSES LPFEUAS Description Lower order path block of background error Lower order path errored second Lower order path severely errored second Lower order path continuous severe bit error second Lower order path unavailable second Lower order path far end block of background error Lower order path far end errored second Lower order path far end severely errored second Lower order path far end consecutive severely errored second Lower order far end unavailable second
Issue 03 (2012-07-30)
771
Table C-75 E1 Error Performance Events Event Name E1_BBE E1_ES E1_SES E1_CSES E1_UAS Description Indicates the E1 background block error. Indicates the E1 errored second. Indicates the E1 severely errored second. Indicates the E1 consecutive severely errored second. Indicates the E1 unavailable second.
C.2.13 ML1/MD1
The ML1/MD1 board reports E1 performance events, PW performance events and board temperature performance events. Table C-76 E1 Performance Event List Event Name E1_LCV_SDH E1_LLOSS_SDH E1_LES_SDH E1_LSES_SDH Description Indicates the count of E1 line side code violations. Indicates the E1 line side loss-of-signal second. Indicates the E1 line side code violation errored second. Indicates the E1 line side code violation severely errored second.
Table C-77 PW carried services performance events Event Name MPLS_PW_LS MPLS_PW_SLS MPLS_PW_CSLS MPLS_PW_UAS Description Indicates the packet loss seconds of PW carried services Indicates the severe packet loss seconds of PW carried services Indicates the consecutive severe packet loss seconds of PW carried services Indicates the unavailable seconds of PW carried services
Issue 03 (2012-07-30)
772
Table C-78 Board Temperature Performance Events Event Name BDTEMPMAX BDTEMPMIN BDTEMPCUR Description Indicates the maximum board temperature. Indicates the minimum board temperature. Indicates the current board temperature.
C.2.14 ODU
The ODU reports radio performance events and board temperature performance events. Table C-79 Radio power performance events Event Name TSL_MAX TSL_MIN TSL_CUR TSL_AVG RSL_MAX RSL_MIN RSL_CUR RSL_AVG TLHTT Description Maximum value of radio transmit signal level Minimum value of radio transmit signal level Current value of radio transmit signal level Average value of radio transmit signal level Maximum value of radio receive signal level Minimum value of radio receive signal level Current value of radio receive signal level Average value of radio receive signal level The duration when the ODU at the local end has a transit power higher than the upper threshold The duration when the ODU at the local end has a transit power higher than the lower threshold The duration when the ODU at the local end has a receive power lower than the upper threshold The duration when the ODU at the local end has a receive power lower than the lower threshold
TLLTT
RLHTT
RLLTT
Issue 03 (2012-07-30)
773
Table C-80 ATPC performance events Event Name ATPC_P_ADJUST ATPC_N_ADJUST Description Positive ATPC adjustment Negative ATPC adjustment
Table C-81 Board Temperature Performance Events Event Name BDTEMPMAX BDTEMPMIN BDTEMPCUR Description Indicates the maximum board temperature. Indicates the minimum board temperature. Indicates the current board temperature.
C.2.15 CQ1
The CQ1 board reports the board temperature performance events and SDH performance events. Table C-82 Board temperature performance events Event Name BDTEMPMAX BDTEMPMIN BDTEMPCUR Description Maximum value of board temperature Minimum value of board temperature Current value of board temperature
Table C-83 Pointer Justification Performance Events Event Name AUPJCHIGH AUPJCLOW AUPJCNEW TUPJCHIGH Description Indicates the count of positive AU pointer justifications. Indicates the count of negative AU pointer justifications. Indicates the count of new AU pointer justifications. Indicates the count of positive TU pointer justifications.
Issue 03 (2012-07-30)
774
Event Name TUPJCLOW
Description Indicates the count of negative TU pointer justifications.
Table C-84 Regenerator Section Error Performance Events Event Name RSBBE RSES RSSES RSUAS RSCSES Description Indicates the regenerator section background block error. Indicates the regenerator section errored second. Indicates the regenerator section severely errored second. Indicates the regenerator section unavailable second. Indicates the regenerator section consecutive severely errored second.
Issue 03 (2012-07-30)
775
Table C-87 Lower order path error performance events Event Name LPBBE LPES LPSES LPCSES LPUAS LPFEBBE LPFEES LPFESES LPFECSES LPFEUAS Description Lower order path block of background error Lower order path errored second Lower order path severely errored second Lower order path continuous severe bit error second Lower order path unavailable second Lower order path far end block of background error Lower order path far end errored second Lower order path far end severely errored second Lower order path far end consecutive severely errored second Lower order far end unavailable second
Issue 03 (2012-07-30)
776
C.2.16 ISV3
The ISV3 board reports three types of performance events: SDH\PDH performance events, radio performance events, and board temperature performance events.
SDH Performance Events

Issue 03 (2012-07-30)
777

Table C-91 Lower order path error performance events Event Name LPBBE LPES LPSES LPCSES LPUAS LPFEBBE LPFEES LPFESES LPFECSES Description Lower order path block of background error Lower order path errored second Lower order path severely errored second Lower order path continuous severe bit error second Lower order path unavailable second Lower order path far end block of background error Lower order path far end errored second Lower order path far end severely errored second Lower order path far end consecutive severely errored second
Issue 03 (2012-07-30)
778
Event Name LPFEUAS
Description Lower order far end unavailable second

Table C-94 AM performance events Event Name QPSKWS QAMWS16 QAMWS32 QAMWS64 QAMWS128 QAMWS256 QAMWS512 QAMWS1024 Description Working time of the QPSK mode Working time of the 16QAM mode Working time of the 32QAM mode Working time of the 64QAM mode Working time of the 128QAM mode Working time of the 256QAM mode Working time of the 512QAM mode Working time of the 1024QAM mode
Issue 03 (2012-07-30)
779
Event Name QPSK_S_WS QAM_S_WS16 QAM_L_WS512 QAM_L_WS1024 AMDOWNCNT AMUPCNT
Description Working time of the QPSK strong mode Working time of the 16QAM strong mode Working time of the 512QAM light mode Working time of the 1024QAM light mode Count of the downshift of the AM scheme Count of the upshift of the AM scheme

C.2.17 EG4/EG4P
The EG4/EG4P board reports optical power performance events and board temperature performance events.
Issue 03 (2012-07-30)
780
Table C-98 Optical power performance events Event Name TPLMAX TPLMIN TPLCUR RPLMAX RPLMIN RPLCUR Description Maximum value of transmit optical power Minimum value of transmit optical power Current value of transmit optical power Maximum value of receive optical power Minimum value of receive optical power Current value of receive optical power
C.3 Performance Events and Handling Procedures

Based on the type of a performance event, this chapter describes all the performance events on the and how to handle these performance events.
C.3.1 AUPJCHIGH, AUPJCLOW, and AUPJCNEW

Description
l l l AUPJCHIGH indicates the count of positive AU pointer justifications. AUPJCLOW indicates the count of negative AU pointer justifications. AUPJCNEW indicates the count of new AU pointer justifications.
Attribute
Attribute Performance event cell Description PPJE (AUPJCHIGH) NPJE (AUPJCLOW) NDF (AUPJCNEW) Unit Block
Issue 03 (2012-07-30)
781
Impact on System
Less than six AUPJCHIGH and AUPJCLOW events do not affect the system. If the pointer is justified 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 preset threshold, the MSAD_CROSSTR alarm is reported. Performance Event AUPJCHIGH AUPJCLOW AUPJCNEW Default 15-Minute Threshold 1500 1500 1500 Default 24-Hour Threshold 30000 30000 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

Description
l l l TUPJCHIGH indicates the count of positive TU pointer justifications. TUPJCLOW indicates the count of negative TU pointer justifications. TUPJCNEW indicates the count of new TU pointer justifications.
Attribute
Attribute Performance event cell Description TUPPJE (TUPJCHIGH) TUNPJE (TUPJCLOW) TUNDF (TUPJCNEW) Unit Block
Issue 03 (2012-07-30)
782
Impact on System
Less than six TUPJCHIGH and TUPJCLOW events on each port do not affect the system. If the pointer is justified for many times, or the TUPJCNEW event occurs, bit errors may occur in the service.
Related Alarms
When the TUPJCHIGH, TUPJCLOW, or TUPJCNEW performance event crosses the preset threshold, the HPAD_CROSSTR alarm is reported. Performance Event TUPJCHIGH TUPJCLOW TUPJCNEW Default 15-Minute Threshold 1500 1500 1500 Default 24-Hour Threshold 30000 30000 30000
Possible Causes
The 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

Description
l RSBBE indicates the regenerator section background block error. Background block error (BBE) refers to the errored blocks excluding the errored blocks in the unavailable and severely errored seconds. l l RSES indicates the regenerator section errored second. Errored second (ES) refers to a second in which one or more errored blocks are detected. RSSES indicates the regenerator section severely errored second. Severely errored second (SES) refers to a second in which 30% or more than 30% errored blocks exist or at least one severely disturbed period (SDP) exists. SDP is the period in which the BER of all the consecutive blocks in a period of less than four consecutive blocks or 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 occurs continuously for less than 10 seconds. l
Issue 03 (2012-07-30)
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 the eleventh 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 are detected through the self-defined overhead byte B1 in the PDH radio frame.
Attribute
Attribute Performance event cell Unit Description B1CNT Block (RSBBE) Second (RSES, RSSES, RSCSES, and RSUAS)
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 preset threshold, the RS_CROSSTR alarm is reported. Performance Event RSBBE RSES RSSES RSUAS RSCSES Default 15-Minute Threshold 1500 50 20 20 Default 24-Hour Threshold 15000 100 50 50
4 (number of consecutive SESs)
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 are configured and whether fibers are properly connected at service ports. If cross-connections are
not configured, configure cross-connections again according to planning information; if fibers are incorrectly connected, connect the fibers again according to planning information. ----End
C.3.4 RSOOF and RSOFS

Description
l RSOOF indicates the regenerator section out of frame. The out-of-frame (OOF) block refers to a data block in which incorrect A1 and A2 bytes are detected. l RSOFS indicates the regenerator section out-of-frame second. The out-of-frame second (OFS) refers to a second in which one or more OOF blocks are detected.
Attribute
Attribute Performance event cell Unit Description OOF 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. If the OOF state lasts for 3 ms, the R_LOF alarm is reported and all the services are interrupted.
Possible Causes
The system detects incorrect A1 and A2 bytes.
Procedure
Step 1 If the R_LOF alarm, as well as the performance event, is reported, eliminate the errors according to the alarm. Otherwise, see 5.4 Troubleshooting Bit Errors in TDM Services for handling. ----End
Issue 03 (2012-07-30)
785
C.3.5 MSBBE, MSES, MSSES, MSCSES, and MSUAS

Description
l MSBBE indicates the multiplex section background block error. BBE refers to the errored blocks excluding the errored blocks in the unavailable and severely errored seconds. l l MSES indicates the multiplex section errored second. ES refers to a second in which one or more errored blocks are detected. 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 one SDP exists. SDP is the period in which the BER of all the consecutive blocks in a period of less than four consecutive blocks or 1 ms (the longer period is applied) is equal to or higher than 10-2 or the signal is lost. l 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. 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 the eleventh second, with the previous 10 seconds included.
Attribute
Attribute Performance event cell Unit Description B2CNT Block (MSBBE) Second (MSES, MSSES, MSCSES, and MSUAS)
Impact on System
Related Alarms
When the MSBBE, MSES, MSSES, MSCSES, or MSUAS performance event crosses the preset threshold, the MS_CROSSTR alarm is reported. Performance Event MSBBE MSES
Issue 03 (2012-07-30)
Default 15-Minute Threshold 1500 50
Default 24-Hour Threshold 15000 100

786
Performance Event MSES MSUAS MSCSES
Possible Causes
The system detects multiplex section bit errors through the B2 byte.
Procedure
Step 1 See 5.4 Troubleshooting Bit Errors in TDM Services for handling. Step 2 When an MSUAS performance event is reported, check whether cross-connections are configured and whether fibers are properly connected at service ports. If cross-connections are not configured, configure cross-connections again according to planning information; if fibers are incorrectly connected, connect the fibers again according to planning information. ----End
C.3.6 MSFEBBE, MSFEES, MSFESES, MSFECSES, and MSFEUAS

Description
l MSFEBBE indicates the multiplex section far end background block error. Far end background block error (FEBBE) indicates that the BBE occurs at the opposite end. l l l MSFEES indicates the multiplex section far end errored second. Far end errored second (FEES) indicates that the ES occurs at the opposite end. 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. MSFECSES indicates the multiplex section far end consecutive severely errored second. Far end consecutive severely errored second (FECSES) indicates that the CSES occurs at the 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.
Attribute
Attribute Performance event cell Description LFEBE
Issue 03 (2012-07-30)
787
Attribute Unit
Description 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

Description
l HPBBE indicates the higher order path background block error. BBE refers to the errored blocks excluding the errored blocks in the unavailable and severely errored seconds. l l HPES indicates the higher order path errored second. ES refers to a second in which one or more errored blocks are detected. 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 one SDP exists. SDP is the period in which the BER of all the consecutive blocks in a period of less than four consecutive blocks or 1 ms (the longer period is applied) is equal to or higher than 10-2 or the signal is lost. l 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. HPUAS indicates the higher order path unavailable second. The unavailable time begins at the onset of 10 consecutive SESs, with the 10 SESs included. When SESs disappear for 10 consecutive seconds, the available time begins from the eleventh second, with the previous 10 seconds included.
Attribute
Attribute Performance event cell Unit Description B3CNT Block (HPBBE) Second (HPES, HPSES, HPCSES, and HPUAS)
Impact on System
Related Alarms
When the HPBBE, HPES, HPSES, HPCSES, or HPUAS performance event crosses the preset threshold, the HP_CROSSTR alarm is reported. Performance Event HPBBE HPES HPSES HPUAS HPCSES Default 15-Minute Threshold 1500 50 20 20 Default 24-Hour Threshold 15000 100 50 50
Possible Causes
The system detects higher order path bit errors through the B3 byte.
Procedure
Step 1 See 5.4 Troubleshooting Bit Errors in TDM Services for handling. ----End
C.3.8 HPFEBBE, HPFEES, HPFESES, HPFECSES, and HPFEUAS

Description
l HPFEBBE indicates the higher order path far end background block error. Far end background block error (FEBBE) indicates that the BBE occurs at the opposite end.
l l l l
HPFEES indicates the higher order path far end errored second. FEES indicates that the ES occurs at the opposite end. HPFESES indicates the higher order path far end severely errored second. FESES indicates that the SES occurs at the opposite end. HPFECSES indicates the higher order path far end consecutive severely errored second. FECSES indicates that the CSES occurs at the opposite end. HPFEUAS indicates the higher order path far end unavailable second. FEUAS indicates that the UAS occurs at the opposite end.
Attribute
Attribute Performance event cell Unit Description PFEBE Block (HPFEBBE) Second (HPFEES, HPFESES, HPFECSES, and HPFEUAS)
Impact on System
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
C.3.9 IF_BBE, IF_ES, IF_SES, IF_CSES, and IF_UAS

Description
l IF_BBE indicates the radio link background block error. BBE refers to the errored blocks excluding the errored blocks in the unavailable and severely errored seconds. l IF_ES indicates the radio link errored second. ES refers to a second in which one or more errored blocks are detected.
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 one SDP exists. SDP is the period in which the BER of all the consecutive blocks in a period of less than four consecutive blocks or 1 ms (the longer period is applied) is equal to or higher than 10-2 or the signal is lost.
l 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. 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 the eleventh second, with the previous 10 seconds included.
IF_BER indicates the radio link bit error rate.
Attribute
Attribute Performance event cell Description IF_BIP8 IF_BER_15M(IF_BER) IF_BER_24H(IF_BER) Unit IF_BBE(block) Second(IF_ES, IF_SES, IF_CSES, IF_UAS)
Impact on System
Related Alarms
The MW_BER_SD or MW_BER_EXC alarm is reported when the BER crosses the specific threshold.
Possible Causes
The system detects bit errors on the radio link through the bit error detection overheads in a radio frame.
Procedure
Issue 03 (2012-07-30)
791
C.3.10 LPBBE, LPES, LPSES, LPCSES, and LPUAS

Description
l LPBBE indicates the lower order path background block error. BBE refers to the errored blocks excluding the errored blocks in the unavailable and severely errored seconds. l l LPES indicates the lower order path errored second. ES refers to a second in which one or more errored blocks are detected. 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 one SDP exists. SDP is the period in which the BER of all the consecutive blocks in a period of less than four consecutive blocks or 1 ms (the longer period is applied) is equal to or higher than 10-2 or the signal is lost. l 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. 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 the eleventh second, with the previous 10 seconds included.
Attribute
Attribute Performance event cell Unit Description LPBIP2CNT Block (LPBBE) Second (LPES, LPSES, LPCSES, and LPUAS)
Impact on System
Related Alarms
When the LPBBE, LPES, LPSES, LPCSES, or LPUAS performance event crosses the preset threshold, the LP_CROSSTR alarm is reported. Performance Event LPBBE LPES
Issue 03 (2012-07-30)

792
Performance Event LPSES LPUAS LPCSES
Possible Causes
The system detects lower order path bit errors through the BIP2 in the V5 byte (E1 interface board or Hybrid IF board).
Procedure
C.3.11 LPFEBBE, LPFEES, LPFESES, LPFECSES, and LPFEUAS

Description
l l l l l LPFEBBE indicates the lower order path far end background block error. FEBBE indicates that the BBE occurs at the opposite end. LPFEES indicates the lower order path far end errored second. FEES indicates that the ES occurs at the opposite end. LPFESES indicates the lower order path far end severely errored second. FESES indicates that the SES occurs at the opposite end. LPFECSES indicates the lower order path far end consecutive severely errored second. FECSES indicates that the CSES occurs at the opposite end. LPFEUAS indicates the lower order path far end unavailable second. FEUAS indicates that the UAS occurs at the opposite end.
Attribute
Attribute Performance event cell Unit Description LPFEBE Block (LPFEBBE) Second (LPFEES, LPFESES, LPFECSES, and LPFEUAS)
Issue 03 (2012-07-30)
793
Impact on System
Related Alarms
The LP_REI alarm is reported at the local end.
Possible Causes
The system detects the lower order path far end bit errors through bit 3 in the V5 byte.
Procedure
C.3.12 E1_LCV_SDH, E1_LLOSS_SDH, E1_LES_SDH, and E1_LSES_SDH

Description
l l l The E1_LCV_SDH is a performance event indicating the E1 line side code violation count. The E1_LLOSS_SDH is a performance event indicating the E1 line side loss-of-signal seconds. 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 violation severely errored second. An SES refers to a certain second in which 30% or more errored blocks are detected or at least one serious disturbance period (SDP) exists. The SDP refers to a period of at least four consecutive blocks or 1 ms (taking the longer one) in which the BER of all the consecutive blocks is equal to or higher than 10-2 or the signal is lost.
Attribute
Attribute Performance event cell Unit Description LCV_BPVCNT None Second

If bit errors occur in the services, you need to find out the causes and troubleshoot the problem in a timely manner. Otherwise, the signal transmission quality will be affected.
Related Alarms
None.
Possible Causes
l 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 low or 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 services received by a board by setting the code type of the board. ----End
C.3.13 TSL_MAX, TSL_MIN, TSL_CUR, and TSL_AVG

Description
l l l l TSL_MAX indicates the maximum radio transmitted signal level. TSL_MIN indicates the minimum radio transmitted signal level. TSL_CUR indicates the current radio transmitted signal level. TSL_AVG indicates the average radio transmitted signal level.
Attribute
Attribute Performance event cell Unit Description TSL 0.1dBm
Impact on System
When the radio transmitted signal level is very low or very high, the radio received signal level at the opposite site is very low or very high. As a result, bit errors occur and even services are interrupted.
Related Alarms
If the radio transmitted signal level is not within the range supported by the ODU, the RADIO_TSL_HIGH or RADIO_TSL_LOW alarm is reported.
C.3.14 RSL_MAX, RSL_MIN, RSL_CUR, and RSL_AVG

Description
l l l l RSL_MAX indicates the maximum radio received signal level. RSL_MIN indicates the minimum radio received signal level. RSL_CUR indicates the current radio received signal level. RSL_AVG indicates the average radio received signal level.
Attribute
Attribute Performance event cell Unit Description RSL 0.1dBm
Impact on System
When the radio received signal level is very low or very high, bit errors occur and even services are interrupted.
Related Alarms
If the radio received signal level crosses the specific threshold, the RADIO_RSL_HIGH or RADIO_RSL_LOW alarm is reported.
C.3.15 FEC_BEF_COR_ER, FEC_COR_BYTE_CNT and FEC_UNCOR_BLOCK_CNT

Description
l l l FEC_BEF_COR_ER indicates the BER before the FEC is performed. This event indicates the impact of the external environment on the transmission. FEC_COR_BYTE_CNT indicates the number of bytes corrected through the FEC. This event indicates the impact of the FEC. FEC_UNCOR_BLOCK_CNT indicates the number of frames that cannot be corrected through the FEC. This event indicates the number of blocks that cannot be corrected through the FEC.
Issue 03 (2012-07-30)
796
Attribute
Attribute Performance event cell Description FECBEFCORER (FEC_BEF_COR_ER) FECCORBYTECNT (FEC_COR_BYTE_CNT) FECUNCORBLOCKCNT (FEC_UNCOR_BLOCK_CNT) Unit None (FEC_BEF_COR_ER) None (FEC_COR_BYTE_CNT) Block (FEC_UNCOR_BLOCK_CNT)
Impact on System
If the value of FEC_BEF_COR_ER is very high, residual bit errors exist in the service after the FEC is performed. If the value of FEC_UNCOR_BLOCK_CNT is not zero, it can be inferred that bit errors that cannot be corrected exist on a radio link. Bit errors exist in the service accordingly.
Related Alarms
If a byte cannot be corrected, the MW_FEC_UNCOR alarm is reported.
C.3.16 QPSKWS, QPSK_S_WS, QAMWS16, QAM_S_WS16, QAMWS32, QAMWS64, QAMWS128, QAMWS256, QAMWS512, QAM_L_WS512, QAMWS1024, and QAM_L_WS1024
Description
l l l l l l l l l l l l
Issue 03 (2012-07-30)
QPSKWS indicates the working duration of the QPSK mode. QPSK_S_WS indicates the working duration of the QPSKWS Strong mode. QAMWS16 indicates the working duration of the 16QAM mode. QAM_S_WS16 indicates the working duration of the 16QAM Strong mode. QAMWS32 indicates the working duration of the 32QAM mode. QAMWS64 indicates the working duration of the 64QAM mode. QAMWS128 indicates the working duration of the 128QAM mode. QAMWS256 indicates the working duration of the 256QAM mode. QAMWS512 indicates the working duration of the 512QAM mode. QAM_L_WS512 indicates the working duration of the 512QAM Light mode. QAMWS1024 indicates the working duration of the 1024QAM mode. QAM_L_WS1024 indicates the working duration of the 1024QAM Light mode.
Attribute
Attribute Performance event cell Description QPSKWSSECOND (QPSK) QPSK_S_WSSECOND (QPSK Strong) QAMWS16SECOND (16QAM) QAM_S_WS16SECOND (16QAM Strong) QAMWS32SECOND (32QAM) QAMWS64SECOND (64QAM) QAMWS128SECOND (128QAM) QAMWS256SECOND (256QAM) QAMWS512SECOND (512QAM) QAM_L_WS512SECOND (512QAM Light) QAMWS1024SECOND (1024QAM) QAM_L_WS1024SECOND (1024QAM Light) 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 for maximum 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, the performance of the radio link is abnormal.
Related Alarms
None.
C.3.17 ATPC_P_ADJUST and ATPC_N_ADJUST

Description
l ATPC_P_ADJUST indicates the positive ATPC adjustment event. This performance event indicates that the quality of a communication link declines. Therefore, you must increase the transmit power of the ODU to maintain the communication quality. l ATPC_N_ADJUST indicates the negative ATPC adjustment event. This performance event indicates that the quality of a communication link becomes well or the transmit power of the ODU is very large. Therefore, you can decrease the transmit power of the ODU.
Attribute
Attribute Performance event cell Unit Description ATPCPADJUST (ATPC_P_ADJUST) and ATPCNADJUST (ATPC_N_ADJUST) times

The ATPC adjustment indicates only the stability of a communication link and it does not affect services. When the value of the performance event is larger, more adjustments are made. When the factors that affect a communication link, such as sudden change of the weather, do not exist, and when the ATPC adjustment count is very large, the communication link may be faulty. You must check the communication link to prevent it from failure.
Related Alarms
None.
C.3.18 AMDOWNCNT and AMUPCNT

Description
l l AMDOWNCNT indicates the count of the AM downshifts on a board in the current performance statistics period. AMUPCNT indicates the count of the AM upshifts on a board in the current performance statistics period.
Attribute
Attribute Performance event cell Unit Description ACMDCNT(AMDOWNCNT) and ACMUCNT(AMUPCNT) times
Impact on System
l l When the value of the performance event is larger, more AM scheme are made. 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 may be faulty. You must check the communication link to prevent it from failure.
Related Alarms
AM_DOWNSHIFT
Possible Causes
When the AM function is enabled, the transmission modulation scheme that the IF port on the IF board uses varies according to the quality of the link. Accordingly, the system counts the performance events of the modulation scheme shift. When the low-efficiency modulation scheme is shifted to the high-efficiency modulation scheme, an upshift is recorded and one AMUPCNT event is counted. Similarly, when the high-efficiency modulation scheme is shifted to the low-efficiency modulation scheme, a downshift is recorded and one AMDOWNCNT event is counted.
C.3.19 RLHTT, RLLTT, TLHTT, TLLTT

Description
l l l l The RLHTT indicates the duration when the ODU at the local end has a receive power lower than the upper threshold. The RLLTT indicates the duration when the ODU at the local end has a receive power lower than the lower threshold. The TLHTT indicates the duration when the ODU at the local end has a transit power higher than the upper threshold. The TLLTT indicates the duration when the ODU at the local end has a transit power higher than the lower threshold.
Attribute
Attribute Performance event cell Unit Description RLHTS(RLHTT), RLLTS(RLLTT), TLHTS (TLHTT), and TLLTS(TLLTT) Second
Impact on System
None.
Related Alarms
None.
C.3.20 TPLMAX, TPLMIN, and TPLCUR

Description
l l l
Issue 03 (2012-07-30)
TPLMAX indicates the maximum transmit optical power at an optical interface. TPLMIN indicates the minimum transmit optical power at an optical interface. TPLCUR indicates the current transmit optical power at an optical interface.
Attribute
Attribute Performance event cell Unit Description OPM 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 transmit optical power is very low or very high, the receive optical power at the opposite site is accordingly very low or very high. As a result, bit errors occur and even services are interrupted.
Related Alarms
l l If the transmit optical power at the opposite site is lower than the receiver sensitivity, the IN_PWR_LOW alarm is reported. If the receive optical power at the opposite site is higher than the overload power, the IN_PWR_HIGH alarm is reported.
C.3.21 RPLMAX, RPLMIN, and RPLCUR

Description
l l l RPLMAX indicates the maximum receive optical power at an optical interface. RPLMIN indicates the minimum receive optical power at an optical interface. RPLCUR indicates the current receive optical power at an optical interface.
Attribute
Attribute Performance event cell Unit Description IPM 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 are interrupted.
Issue 03 (2012-07-30)
801
Related Alarms
l l If the transmit optical power is lower than the receiver sensitivity, the IN_PWR_LOW alarm is reported. If the receive optical power is higher than the overload power, the IN_PWR_HIGH alarm is reported.
C.3.22 BDTEMPMAX, BDTEMPMIN, and BDTEMPCUR

Description
l l l BDTEMPMAX indicates the maximum temperature of a board. BDTEMPMIN indicates the minimum temperature of a board. BDTEMPCUR indicates the current temperature of a board.
Attribute
Attribute Performance event cell Unit Description XCS_TEMP 0.1C
Impact on System
If the temperature of a board is very high or very low, the performance of the board declines, and bit errors or other faults occur.
Related Alarms
If the temperature of a board crosses the specific threshold, the TEMP_ALARM alarm is reported.
C.3.23 XPIC_XPD_VALUE
Description
The XPIC_XPD_VALUE indicates the XPD value after the XPIC function is enabled.
Attribute
Attribute Performance event cell Unit Description XPD dB
Issue 03 (2012-07-30)
802
Impact on System
l l When the XPIC function is disabled, the performance event does not affect the system. 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 value indicates more interference and worse signaling environment. If the XPD value is smaller than a specific threshold, errors and even interruptions occur on the radio link.
Related Alarms
None.
C.3.24 PG_IF_BBE, PG_IF_ES, PG_IF_SES, PG_IF_CSES, and PG_IF_UAS

Description
l PG_IF_BBE indicates the protection group background block error. Background block error (BBE) refers to the errored blocks excluding the errored blocks in the unavailable and severely errored seconds. l 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. 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% errored blocks exist or at least one severely disturbed period (SDP) exists. SDP is the period in which the BER of all the consecutive blocks in a period of less than four consecutive blocks or 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 occurs continuously 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 the eleventh second, with the previous 10 seconds included.
Attribute
Attribute Performance event cell Unit Description IF_BIP8 Block (PG_IF_BBE) Second (PG_IF_ES, PG_IF_SES, PG_IF_CSES, and PG_IF_UAS)
Issue 03 (2012-07-30)
803
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. Performance Event PG_IF_BBE PG_IF_ES PG_IF_SES PG_IF_UAS PG_IF_CSES Default 15-Minute Threshold 1500 50 20 20 Default 24-Hour Threshold 15000 100 50 50
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

Description
l E1_BBE indicates the E1 background block error. Background block error (BBE) refers to the errored blocks excluding the errored blocks in the unavailable and severely errored seconds. This performance event can be detected only when the E1 frame format is CRC-4. l l E1_ES indicates the E1 errored second. Errored second (ES) refers to a second in which one or more errored blocks are detected. E1_SES indicates the E1 severely errored second. Severely errored second (SES) refers to a second in which 30% or more than 30% errored blocks exist or at least one severely disturbed period (SDP) exists. SDP is the period in
which the BER of all the consecutive blocks in a period of less than four consecutive blocks or 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 occurs continuously 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 the eleventh second, with the previous 10 seconds included.
Attribute
Attribute Performance event cell Unit Description E1CRC_ERR_CNT Block (E1_BBE) Second (E1_ES, E1_SES, E1_CSES, and E1_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. Performance Event E1_BBE E1_ES E1_SES E1_UAS E1_CSES Default 15-Minute Threshold 1500 50 20 20 Default 24-Hour Threshold 15000 100 50 50
Possible Causes
The 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
C.3.26 IF_SNR_MAX, IF_SNR_MIN, and IF_SNR_AVG

Description
l l l IF_SNR_MAX indicates the maximum signal to noise ratio. IF_SNR_MIN indicates the minimum signal to noise ratio. IF_SNR_AVG indicates the average signal to noise ratio.
Attribute
Attribute Performance event cell Description IF_SNR(IF_SNR_MAX, IF_SNR_MIN) IF_SNR_AVG_15M, and IF_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 radio link, errors and even interruptions occur on the radio link.
Related Alarms
None.
C.3.27 OSPITMPMAX, OSPITMPMIN, and OSPITMPCUR

Description
l l l OSPITMPMAX indicates the maximum temperature of a laser core. OSPITMPMIN indicates the minimum temperature of a laser core. OSPITMPCUR indicates the current temperature of a laser core.
Attribute
Attribute Performance event cell Unit Description TMP C
Issue 03 (2012-07-30)
806
Impact on System
If the temperature of a laser core is very high or very low, the performance of the laser degrades, and bit errors or other faults occur.
Relevant Alarms
None.
C.3.28 MAXMEANPATHDELAY, MINMEANPATHDELAY, and AVGMEANPATHDELAY

Description
l l l MAXMEANPATHDELAY indicates the maximum path delay between the master and slave clocks. MINMEANPATHDELAY indicates the minimum path delay between the master and slave clocks. AVGMEANPATHDELAY indicates the average path delay between the master and slave clocks.
Attribute
Attribute Performance event cell Description MAXMEANPATHDELAY (MAXMEANPATHDELAY) MINMEANPATHDELAY (MINMEANPATHDELAY) AVGMEANPATHDELAY (AVGMEANPATHDELAY) Unit ns
Impact on System
The deviation between the maximum and minimum path delays indicates the delay and jitter. If the deviation exceeds the acceptable range, clock performance will be affected.
Related Alarms
None.
Issue 03 (2012-07-30)
807
C.3.29 MAXPHASEOFFSET, MINPHASEOFFSET, and AVGPHASEOFFSET

Description
l l l MAXPHASEOFFSET indicates the maximum time deviation between the master and slave clocks. MINPHASEOFFSET indicates the minimum time deviation between the master and slave clocks. AVGPHASEOFFSET indicates the average time deviation between the master and slave clocks.
Attribute
Attribute Performance event cell Description MAXPHASEOFFSET (MAXPHASEOFFSET), MINPHASEOFFSET (MINPHASEOFFSET), AVGPHASEOFFSET (AVGPHASEOFFSET) ns
Unit
Impact on System
This performance indicates the time deviation between the local and upstream NEs. If the time deviation exceeds the acceptable range (greater than 100 ns), the time of the upstream NE cannot be locked, and NE time synchronization fails.
Related Alarms
When the time deviation between the master and slave clocks is greater than 100 ns, the TIME_LOCK_FAIL alarm is reported.
C.3.30 CURPOSITIVEPDV and CURNEGATIVEPDV

Description
l l CURPOSITIVEPDV indicates the current positive packet delay variation (PDV). CURNEGATIVEPDV indicates the current negative PDV.
Issue 03 (2012-07-30)
808
Attribute
Attribute Performance event cell Description PTP_N_PDV_15M (15-minute negative PDV) PTP_N_PDV_24H (24-hour negative PDV) Unit ns
Impact on System
The less the PDV, the better the clock performance.
Related Alarms
When the PDV exceeds the acceptable range, the clock is unlocked and the ACR_LOCK_FAIL alarm is reported.
C.3.31 MAXPOSITIVEDELAY, MINPOSITIVEDELAY, and AVGPOSITIVEDELAY

Description
l l l MAXPOSITIVEDELAY indicates the maximum positive delay between the master and slave clocks. MINPOSITIVEDELAY indicates the minimum positive delay between the master and slave clocks. AVGPOSITIVEDELAY indicates the average positive delay between the master and slave clocks.
Attribute
Attribute Performance event cell Unit Description PTP_PTD ns
Impact on System
The deviation between the maximum and minimum positive delays indicates the delay and jitter. If the deviation exceeds the acceptable range, clock performance will be affected.
Related Alarms
None.
C.3.32 MAXFREQDEV, MINFREQDEV, and AVGFREQDEV

Description
l l l MAXFREQDEV indicates the maximum frequency offset. MINFREQDEV indicates the minimum frequency offset. AVGFREQDEV indicates the average frequency offset.
Attribute
Attribute Performance event cell Unit Description PTP_DA ns
Impact on System
If the frequency offset exceeds the acceptable range, clock signals deteriorate.
Related Alarms
If the frequency offset exceeds the acceptable range, the SYN_BAD alarm is reported.
C.3.33 MPLS_PW_LS, MPLS_PW_SLS, MPLS_PW_CSLS, and MPLS_PW_UAS

Description
l l l l MPLS_PW_LS indicates the packet loss seconds of the PW service. MPLS_PW_SLS indicates the severe packet loss seconds of the PW service. MPLS_PW_CSLS indicates the consecutive severe packet loss seconds of the PW service. MPLS_PW_UAS indicates the unavailable seconds of the PW service.
Attribute
Attribute Performance event cell Unit Description MPLS_PW_FL s
Impact on System
The greater of the seconds of packets that are lost in one measurement period (for example, 15 minutes or 24 hours), the more packets are lost. Then, the QoS will be affected.
Procedure
Check the bandwidth utilization. If the bandwidth utilization equals to or exceeds the specified bandwidth threshold, expand the network.
C.3.34 TLBMAX, TLBMIN, and TLBCUR

Description
l l l TLBMAX indicates the maximum transmit bias current of the laser. TLBMIN indicates the minimum transmit bias current of the laser. TLBCUR indicates the current transmit bias current of the laser.
Attribute
Attribute Performance event cell Unit Description LSBCM 0.1 mA
Impact on System
If the bias current of the laser is over-high or over-low, the laser is damaged.
Related Alarms
If the receive optical power on the opposite NE is abnormal, the IN_PWR_ABN alarm is reported.
Issue 03 (2012-07-30)
811
D RMON Event Reference
RMON Event Reference
RMON events reflect the running of the Ethernet services. This chapter describes the possible RMON events on the OptiX RTN 950 and how to handle these events. D.1 List of RMON Alarm Entries The RMON alarm entries refer to the table entries in the RMON alarm group. D.2 List of RMON Performance Entries on the Packet-Plane The RMON performance entries on the packet plane refer to the table entries in the RMON statistics group or history group. D.3 List of RMON Performance Entries on the EoS/EoPDH Plane 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 RMON performance events on the EoPDH plane include PORT1 to PORT8, and VCTRUNK1 to VCTRUNK8 on the EMS6 board. D.4 RMON Events and Handling Procedures This chapter describes the RMON events that indicate Ethernet service abnormalities and how to handle these events.
Issue 03 (2012-07-30)
812
D.1 List of RMON Alarm Entries

The RMON alarm entries refer to the table entries in the RMON alarm group. Table D-1 List of RMON alarm entries Alarm Name ETHDR OP Description The number of packet loss events Remarks ETHDROP indicates the number of packet loss events caused by insufficient Ethernet chip resources. The count is not the number of discarded packets but the number of times packet loss is detected. FCS bytes are included but framing bits are excluded. FCS error frames exclude oversized frames and undersized frames. Source ISU2, ISX2, ISV3, IFU2 and IFX2
RXBBA D ETHFCS
The number of bytes in received bad packets The number of frames that have FCS check errors
Table D-2 List of RMON alarm entries Alarm Name ETHDR OP Description The number of packet loss events Remarks ETHDROP indicates the number of packet loss events caused by insufficient Ethernet chip resources. The count is not the number of discarded packets but the number of times packet loss is detected. Indicates the number of frames that fail to be transmitted due to consecutive collisions. Source EM6T, EM6F, EM6FA, EM6TA, EG4, EG4P
ETHEX CCOL
The number of frames that fail to be transmitted after continuous collisions
Issue 03 (2012-07-30)
813
Alarm Name ETHLAT ECOL
Description The number of collisions that are detected after a timeslot period elapses
Remarks Indicates the number of collisions that are detected after a timeslot period elapses. The late collisions indicate that the diameter of a LAN is too large. FCS bytes are included but framing bits are excluded. Indicates the number of frames whose first transmission is delayed because transmission media are busy, excluding the number of frames whose transmission is delayed due to collisions. Undersized packets are the packets shorter than 64 bytes (including FCS bytes but not framing bits). Oversized packets are the packets larger than MTU (including FCS bytes but not framing bits). ETHFRG indicates the number of received packets that are shorter than 64 bytes (including FCS bytes but not framing bits) and contain FCS errors or alignment errors. ETHJAB indicates the number of received packets that are larger than MTU (including FCS bytes but not framing bits) and contain FCS errors or alignment errors.
Source
RXBBA D TXDEFF RM
The number of bytes in received bad packets The number of frames whose transmission is delayed
ETHUN DER
The number of received undersized packets
ETHOV ER
The number of received oversized packets
ETHFRG
The number of received fragmented packets
ETHJAB
The number of received errored oversized packets
Issue 03 (2012-07-30)
814
Alarm Name ETHFCS
Description The number of frames that have FCS check errors Indicates the bandwidth utilization at a port in the receive direction.
Remarks FCS error frames exclude oversized frames and undersized frames. Bandwidth utilization ratio = (Number of received bytes x 8/ Monitoring period)/ Configured or actual bandwidth Bandwidth utilization ratio = (Number of transmitted bytes x 8/ Monitoring period)/ Configured or actual bandwidth
Source
PORT_R X_BW_ UTILIZ ATION
EM6T, EM6F, EM6FA, EM6TA, ISU2, ISX2, ISV3, EG4, EG4P, IFU2 and IFX2
PORT_T X_BW_ UTILIZ ATION
Indicates the bandwidth utilization at a port in the transmit direction.
Table D-3 List of EMS6\EFP8 RMON alarm entries Alarm Name ETHDR OP Description The number of packet loss events Remarks ETHDROP indicates the number of packet loss events caused by insufficient Ethernet chip resources. The count is not the number of discarded packets but the number of times packet loss is detected. FCS bytes are included but framing bits are excluded. Undersized packets are the packets shorter than 64 bytes (including FCS bytes but not framing bits). Oversized packets are the packets larger than MTU (including FCS bytes but not framing bits). Source EMS6, EFP8
RXBBA D ETHUN DER
The number of bytes in received bad packets The number of received undersized packets
ETHOV ER
The number of received oversized packets
Issue 03 (2012-07-30)
815
Alarm Name ETHFRG
Description The number of received fragmented packets
Remarks ETHFRG indicates the number of received packets that are shorter than 64 bytes (including FCS bytes but not framing bits) and contain FCS errors or alignment errors. ETHJAB indicates the number of received packets that are larger than MTU (including FCS bytes but not framing bits) and contain FCS errors or alignment errors. FCS error frames exclude oversized frames and undersized frames. An alignment error means that the frame contains a fractional number of bytes and fails to pass the FCS check.
Source
ETHJAB
The number of received errored oversized packets
ETHFCS
The number of frames that have FCS check errors The number of alignment error frames
ETHALI
D.2 List of RMON Performance Entries on the Packet-Plane

The RMON performance entries on the packet plane refer to the table entries in the RMON statistics group or history group. Table D-4 Packet-Plane RMON Performance Entry List Perf orm anc e Typ e Basi c perf orm ance
Issue 03 (2012-07-30)
Performance Name
Description
Remarks
Source
RXPKTS
Indicates the packets received (packets).
Bad packets, broadcast packets, and multicast packets are included.
EM6T, EM6F, EFP8, IFU2, IFX2, ISU2, ISX2, EM6FA, EM6TA,
816
Perf orm anc e Typ e
Performance Name
Description
Remarks
Source
ETHDROP
Indicates the packet loss events (times).
ETHDROP indicates the number of packet loss events caused by insufficient Ethernet chip resources. The count is not the number of discarded packets but the number of times packet loss is detected. RXOCTETS indicates the total number of bytes in received packets (including bad packets), including framing bits but not FCS bytes. RXMULCAST indicates the total number of received good packets with multicast destination addresses, excluding broadcast packets. RXMULCAST indicates the total number of received good packets with multicast destination addresses, excluding broadcast packets.
EMS6, EG4, EG4P, ISV3
RXOCTETS
Indicates the bytes received (bytes).
RXMULCAST
Indicates the multicast packets received (packets).
RXBRDCAST
Indicates the broadcast packets received (packets).
Issue 03 (2012-07-30)
817
Performance Name
Description
Remarks
Source
ETHOVER
Indicates the oversized packets received (packets).
Oversized packets are the packets larger than MTU (including FCS bytes but not framing bits). ETHJAB indicates the number of received packets that are larger than MTU (including FCS bytes but not framing bits) and contain FCS errors or alignment errors. Undersized packets are the packets shorter than 64 bytes (including FCS bytes but not framing bits). ETHFRG indicates the number of received packets that are shorter than 64 bytes (including FCS bytes but not framing bits) and contain FCS errors or alignment errors. Increase of the count is normal because noise collisions exist. -
EM6T, EM6F, EFP8, EM6FA, EM6TA, EMS6, EG4, EG4P
ETHJAB
Indicates the oversized error packets received (packets).
ETHUNDER
Indicates the undersized packets received (packets).
EM6T, EM6F, EM6FA, EM6TA, EG4, EG4P
ETHFRG
Indicates the fragments received (packets).
ETHCOL
Indicates the collisions (times).
Issue 03 (2012-07-30)
818
Performance Name
Description
Remarks
Source
PORT_RX_BW_ UTILIZATION
Indicates the bandwidth utilization on a port in the receive direction.
Bandwidth utilization ratio = (Number of received bytes x 8/ Monitoring period)/ Configured or actual bandwidth Bandwidth utilization ratio = (Number of transmitted bytes x 8/Monitoring period)/ Configured or actual bandwidth FCS bytes are included but framing bits are excluded. FCS bytes are included but framing bits are excluded. FCS bytes are included but framing bits are excluded. FCS bytes are included but framing bits are excluded. FCS bytes are included but framing bits are excluded. FCS bytes are included but framing bits are excluded.
EM6T, EM6F, EM6FA, EM6TA, ISU2, ISX2, IFU2, IFX2, ISV3, EG4, EG4P
PORT_TX_BW_ UTILIZATION
Indicates the bandwidth utilization on a port in the transmit direction.
RXPKT64
Packets received (64 bytes in length) (packets) Packets received (65-127 bytes in length) (packets) Packets received (128-255 bytes in length) (packets) Packets received (256-511 bytes in length) (packets) Packets received (512-1023 bytes in length) (packets) Packets received (1024-1518 bytes in length) (packets)
ISU2, ISX2, ISV3,
RXPKT65
RXPKT128
RXPKT256
RXPKT512
RXPKT1024
Issue 03 (2012-07-30)
819
Perf orm anc e Typ e Exte nded perf orm ance
Performance Name
Description
Remarks
Source
TXPKTS
Indicates the packets transmitted (packets).
Bad packets, broadcast packets, and multicast packets are included. Indicates the total number of bytes in transmitted packets (including bad packets), including framing bits but not FCS bytes. -
EM6T, EM6F, EFP8, IFU2, IFX2, ISU2, ISX2, ISV3, EM6FA, EM6TA, EMS6, EG4, EG4P
TXOCTETS
Indicates the bytes transmitted
ETHFCS
Indicates the FCS errored frames (frames). Indicates the bytes in received good packets (bytes). Indicates the bytes in transmitted good packets (bytes). Indicates the bytes in received bad packets (bytes). Indicates the unicast packets transmitted (packets). Indicates the unicast packets received (packets).
RXBGOOD
FCS bytes are included but framing bits are excluded. FCS bytes are included but framing bits are excluded. FCS bytes are included but framing bits are excluded. The unicast packets that are discarded or fail to be transmitted are included. RXUNICAST indicates the number of good unicast packets.
TXBGOOD
RXBBAD
TXUNICAST
RXUNICAST
Issue 03 (2012-07-30)
820
Performance Name
Description
Remarks
Source
TXMULCAST
Indicates the multicast packets transmitted (packets). Indicates the broadcast packets transmitted (packets). Indicates the rate of good full-frame bytes received (Kbit/s). Indicates the rate of good full-frame bytes transmitted (Kbit/s). Indicates the good full-frame bytes received (bytes). Indicates the good full-frame bytes transmitted (bytes). Indicates the pause frames received (frames).
The multicast packets that are discarded or fail to be transmitted are included. The broadcast packets that are discarded or fail to be transmitted are included. Framing bits (20 bytes) and FCS bytes are included. Framing bits (20 bytes) and FCS bytes are included. Framing bits (20 bytes) and FCS bytes are included. Framing bits (20 bytes) and FCS bytes are included. RXPAUSE indicates the number of MAC flow control frames with the PAUSE opcode. TXPAUSE indicates the number of MAC flow control frames with the PAUSE opcode. EM6T, EM6F, EFP8, EM6FA, EM6TA, EMS6, EG4, EG4P
TXBRDCAST
RXGOODFULLF RAMESPEED
TXGOODFULLF RAMESPEED
RXFULLBGOOD
TXFULLBGOOD
RXPAUSE
TXPAUSE
Indicates the pause frames transmitted (frames).
Issue 03 (2012-07-30)
821
Performance Name
Description
Remarks
Source
ETHLATECOL
Indicates the late collisions (times).
Indicates the number of collisions that are detected after a timeslot period elapses. The late collisions indicate that the diameter of a LAN is too large. -
EM6T, EM6F, EM6FA, EM6TA, EG4, EG4P,
ETHEXCCOL
Indicates the frames unsuccessfully transmitted after consecutive collisions (frames). Indicates the frames that are deferred in transmission (frames).
TXDEFFRM
Indicates the number of frames whose first transmission is delayed because transmission media are busy, excluding the number of frames whose transmission is delayed due to collisions. FCS bytes are included but framing bits are excluded. ISU2, ISX2, ISV3,
RXPKT1519
Indicates the count of received packets with a length of over 1518 bytes (errored packets included) Indicates the count of transmitted 64byte packets (errored packets included)
TXPKT64
FCS bytes are included but framing bits are excluded.
Issue 03 (2012-07-30)
822
Performance Name
Description
Remarks
Source
TXPKT65
Indicates the count of transmitted packets with a length of 65 to 127 bytes (errored packets included) Indicates the count of transmitted packets with a length of 128 to 255 bytes (errored packets included) Indicates the count of transmitted packets with a length of 256 to 511 bytes (errored packets included) Indicates the count of transmitted packets with a length of 512 to 1023 bytes (errored packets included) Indicates the count of transmitted packets with a length of 1024 to 1518 bytes (errored packets included) Indicates the count of transmitted packets with a length of over 1518 bytes (errored packets included)
TXPKT128
TXPKT256
TXPKT512
TXPKT1024
TXPKT1519
Issue 03 (2012-07-30)
823
Performance Name
Description
Remarks
Source
ETH_RX_THRO UGHPUT_MAX
Indicates the maximum throughput on a port in the receive direction.
Maximum throughput = Number of received bytes (including interframe gaps and preambles)/ Monitoring period Minimum throughput = Number of received bytes (including interframe gaps and preambles)/ Monitoring period Average throughput = Number of received bytes (including interframe gaps and preambles)/ Monitoring period -
EM6T, EM6F, EM6FA, EM6TA, EG4, EG4P,
ETH_RX_THRO UGHPUT_MIN
Indicates the minimum throughput on a port in the receive direction.
ETH_RX_THRO UGHPUT_AVG
Indicates the average throughput on a port in the receive direction.
AT M PW E3 perf orm ance
ATMPW_SNDCE LLS ATMPW_RCVCE LLS ATMPW_UNKN OWNCELLS PORT_RX_BW_ UTILIZATION
Indicates the count of transmitted cells. Indicates the count of received cells. Indicates the count of unknown cells. Indicates the bandwidth utilization on a port in the receive direction.
ML1, MD1
Bandwidth utilization = (Number of received bytes x 8/ Monitoring period)/ Configured or actual bandwidth
AT M/ IMA perf orm ance even ts on the acce
Issue 03 (2012-07-30)
824
Perf orm anc e Typ e ss side
Performance Name
Description
Remarks
Source
Indicates the bandwidth utilization on a port in the transmit direction.
Bandwidth utilization = (Number of transmitted bytes x 8/Monitoring period)/ Configured or actual bandwidth ATM_CORRECT ED_HCSERR is used to evaluate the service quality. ATM_UNCORRE CTED_HCSERR is used to determine whether cell loss occurs on a port. ATM_RCVCELL S is used to determine whether ATM connections are normal. ATM_RCVIDLE CELLS is used to determine whether cells are properly processed at the ATM physical layer. ATM_SNDCELL S is used to determine whether a port transmits services normally. -
ATM_CORRECT ED_HCSERR
Indicates the number of correctable HCS error cells received. Indicates the number of uncorrectable HCS error cells received. Indicates the total number of received cells.
ATM_UNCORRE CTED_HCSERR
ATM_RCVCELL S
ATM_RCVIDLE CELLS
Indicates the total number of received idle cells.
ATM_SNDCELL S
Indicates the total number of transmitted cells.
ATM_IF_INRAT E_MAX
Indicates the maximum rate of normal cells received on the port.
Issue 03 (2012-07-30)
825
Performance Name
Description
Remarks
Source
ATM_IF_INRAT E_MIN
Indicates the minimum rate of normal cells received on the port. Indicates the average rate of normal cells received on the port. Indicates the maximum rate of normal cells transmitted on the port. Indicates the minimum rate of normal cells transmitted on the port. Indicates the average rate of normal cells transmitted on the port. Indicates the percentage of valid cells.
ATM_IF_INRAT E_AVG
ATM_IF_OUTRA TE_MAX
ATM_IF_OUTRA TE_MIN
ATM_IF_OUTRA TE_AVG
ATM_CELL_AV AILABILITY
Percentage of valid cells = (Total number of cells Number of HECdetected error cells)/Total number of cells Bandwidth utilization = (Number of received bytes x 8/ Monitoring period)/ Configured or actual bandwidth
PORT_RX_BW_ UTILIZATION
Indicates the bandwidth utilization rate (0.01%) of the port in the receive direction.
Issue 03 (2012-07-30)
826
Performance Name
Description
Remarks
Source
Indicates the bandwidth utilization rate (0.01%) of the port in the transmit direction.
Bandwidth utilization = (Number of transmitted bytes x 8/Monitoring period)/ Configured or actual bandwidth ATM_UNI1_INR ATE_MAX is based on VPIs/ VCIs.
ATM_UNI1_INR ATE_MAX
Indicates the maximum rate of receiving correct cells on the UNI1 side of ATM connections. Indicates the minimum rate of receiving correct cells on the UNI1 side of ATM connections. Indicates the average rate of receiving correct cells on the UNI1 side of ATM connections. Indicates the maximum rate of transmitting correct cells on the UNI1 side of ATM connections. Indicates the minimum rate of transmitting correct cells on the UNI1 side of ATM connections.
ATM_UNI1_INR ATE_MIN
ATM_UNI1_INR ATE_MIN is based on VPIs/VCIs.
ATM_UNI1_INR ATE_AVG
ATM_UNI1_INR ATE_AVG is based on VPIs/ VCIs.
ATM_UNI1_OUT RATE_MAX
ATM_UNI1_OUT RATE_MAX is based on VPIs/ VCIs.
ATM_UNI1_OUT RATE_MIN
ATM_UNI1_OUT RATE_MIN is based on VPIs/ VCIs.
Issue 03 (2012-07-30)
827
Performance Name
Description
Remarks
Source
ATM_UNI1_OUT RATE_AVG
Indicates the average rate of transmitting correct cells on the UNI1 side of ATM connections. Indicates the maximum rate of receiving correct cells on the UNI2 side of ATM connections. Indicates the minimum rate of receiving correct cells on the UNI2 side of ATM connections. Indicates the average rate of receiving correct cells on the UNI2 side of ATM connections. Indicates the maximum rate of transmitting correct cells on the UNI2 side of ATM connections. Indicates the minimum rate of transmitting correct cells on the UNI2 side of ATM connections.
ATM_UNI1_OUT RATE_AVG is based on VPIs/ VCIs.
ATM_UNI2_INR ATE_MAX
ATM_UNI2_INR ATE_MAX is based on VPIs/ VCIs.
ATM_UNI2_INR ATE_MIN
ATM_UNI2_INR ATE_MIN is based on VPIs/VCIs.
ATM_UNI2_INR ATE_AVG
ATM_UNI2_INR ATE_AVG is based on VPIs/ VCIs.
ATM_UNI2_OUT RATE_MAX
ATM_UNI2_OUT RATE_MAX is based on VPIs/ VCIs.
ATM_UNI2_OUT RATE_MIN
ATM_UNI2_OUT RATE_MIN is based on VPIs/ VCIs.
Issue 03 (2012-07-30)
828
Performance Name
Description
Remarks
Source
ATM_UNI2_OUT RATE_AVG
Indicates the average rate of transmitting correct cells on the UNI2 side of ATM connections. Indicates the total number of receiving correct cells on the UNI1 side of ATM connections. Indicates the total number of transmitting correct cells on the UNI1 side of ATM connections. Indicates the total number of receiving correct cells on the UNI2 side of ATM connections. Indicates the total number of transmitting correct cells on the UNI2 side of ATM connections. Indicates the number of lost disordered packets. Indicates the number of misconnected packets. Indicates the number of deformed frames.
ATM_UNI2_OUT RATE_AVG is based on VPIs/ VCIs.
ATM_UNI1_INC ELLS
ATM_UNI1_INC ELLS is used to determine whether ATM connections are normal. ATM_UNI1_OUT CELLS is used to determine whether ATM connections are normal. ATM_UNI2_INC ELLS is used to determine whether ATM connections are normal. ATM_UNI2_OUT CELLS is used to determine whether ATM connections are normal. CQ1, ML1, MD1
ATM_UNI1_OUT CELLS
ATM_UNI2_INC ELLS
ATM_UNI2_OUT CELLS
CES perf orm ance even t
CES_MISORDER PKTS CES_STRAYPKT S CES_MALPKTS
Issue 03 (2012-07-30)
829
Performance Name
Description
Remarks
Source
CES_JTRUDR
Indicates the number of jitter buffer underflows. Indicates the number of jitter buffer overflows. Indicates the number of lost packets. Indicates the number of received packets. Indicates the number of packets received from PWs. Indicates the number of bytes received from PWs. Indicates the number of packets received at the VUNI VLAN. Indicates the number of bytes in the packets received at the VUNI VLAN. Indicates the number of packets received on the VUNI. Indicates the number of bytes received on the VUNI.
CES_JTROVR
CES_LOSPKTS
CES_RX_PKTS
PW perf orm ance of AT M/ CES L2V PNa perf orm ance
PW_RCVPKTS
PW_RCVBYTES
VLAN_RCVPKT S
CSH
VLAN_RCVBYT ES
VUNI_RCVPKTS
Indicates the number of packets received on a VUNI of a service. Indicates the number of bytes received on a VUNI of a service.
VUNI_RCVBYTE S
Issue 03 (2012-07-30)
830
Perf orm anc e Typ e Tun nel perf orm ance
Performance Name
Description
Remarks
Source
TUNNEL_REVE RSE_RCVPKTS
Indicates the number of packets received in the reverse tunnel.
Indicates the number of packets received in the reverse tunnel of a bidirectional transit tunnel. Indicates the number of bytes received in the reverse tunnel of a bidirectional transit tunnel. Indicates the number of packets received in a tunnel. Indicates the number of bytes received in a tunnel. Bit rate = Number of received bytes x 8/Monitoring period Packet rate = Number of received packets/ Monitoring period Bit rate = Number of received bytes x 8/Monitoring period Packet rate = Number of received packets/ Monitoring period -
TUNNEL_REVE RSE_RCVBYTES
Indicates the number of bytes received in the reverse tunnel.
TUNNEL_RCVP KTS
Indicates the number of packets received in the tunnel. Indicates the number of bytes received in the tunnel. Indicates the bit rate in the receive direction of a reverse tunnel. Indicates the packet rate in the receive direction of a reverse tunnel. Indicates the bit rate in the receive direction of a monitored object. Indicates the packet rate in the receive direction of a monitored object. Indicates the number of packets received on the PW.
TUNNEL_RCVB YTES
TUNNEL_REVE RSE_RX_BPS
TUNNEL_REVE RSE_RX_PPS
TUNNEL_RX_BP S
TUNNEL_RX_PP S
PW perf orm ance
PW_RCVPKTS
Issue 03 (2012-07-30)
831
Perf orm anc e Typ e of L2V PN
Performance Name
Description
Remarks
Source
PW_RCVBYTES
Indicates the number of bytes received on the PW. Indicates the number of packets discarded on the PW. Indicates the bit rate in the receive direction of a monitored object. Indicates the packet rate in the receive direction of a monitored object. Indicates the E_Line service packet loss ratio.
PW_DROPPKTS
PW_RX_BPS
Bit rate = Number of received bytes x 8/Monitoring period Packet rate = Number of received packets/ Monitoring period Packet loss ratio = (Number of packets transmitted by the source MEP Number of packets received by the sink MEP)/ Number of packets transmitted by the source MEP Number of lost packets = Number of packets transmitted by the source - Number of packets received by the sink (Both numbers are detected by the performance monitoring scheme of OAM.)
PW_RX_PPS
ETH OA M 802. 1ag
ETH_CFM_FLR
ETH_CFM_FL
Indicates the number of discarded E_Line service packets.
Issue 03 (2012-07-30)
832
Performance Name
Description
Remarks
Source
ETH_CFM_FD
Indicates the E_Line service delay.
Frame delay = Time when the source MEP sends a request packet Time when the source MEP receives the response packet Frame delay variation is the difference between two frame delay test results. EM6T, EM6F, IFU2, IFX2, ISU2, ISX2, ISV3, EM6FA, EM6TA, EG4, EG4P
ETH_CFM_FDV
Indicates the E_Line service delay variation.
Port traffi c class ifica tion
QOS_PORTCAR_ MarkedRedPKTS
Indicates the number of red packets after traffic monitoring is enabled. Indicates the number of yellow packets after traffic monitoring is enabled. Indicates the number of green packets after traffic monitoring is enabled. Indicates the number of packets received in the matched flow. Indicates the number of packets transmitted in the matched flow.
QOS_PORTCAR_ MarkedYellowPK TS
QOS_PORTCAR_ MarkedGreenPKT S
QOS_PORTSTR M_RCVMATCHP KTS QOS_PORTSTR M_SNDMATCHP KTS
Issue 03 (2012-07-30)
833
Performance Name
Description
Remarks
Source
PORTSTRM_SH APING_DROPPK TS
Indicates the number of packets discarded due to network congestion when the traffic shaping function is enabled in the egress direction. Indicates the ratio of packet loss due to network congestion when the traffic shaping function is enabled in the egress direction.
PORTSTRM_SH APING_DROPRA TIO
Packet loss ratio in the egress direction = Number of discarded packets in the egress direction/Number of packets matching the traffic classification rule in the egress direction Proportion of packets marked in red in the ingress direction = Number of packets marked in red in the ingress direction/Number of packets matching the traffic classification rule in the ingress direction
QOS_PORTCAR_ MarkedRedRATI O
Indicates the proportion of packets marked in red when the traffic policing function is enabled.
Issue 03 (2012-07-30)
834
Perf orm anc e Typ e Port prior ity
Performance Name
Description
Remarks
Source
QOS_PORTQUE UE_DROPRATIO
Indicates the ratio of packet loss due to congestion in egress queues with different priorities.
Packet loss ratio in an egress queue = Number of discarded packets with a priority in the egress queue/ Number of packets with the priority in the egress queue -
QOS_PRI_DROP PKTS
Indicates the number of packets discarded in the services with different priorities. Indicates the number of bytes discarded in the services with different priorities. Indicates the number of packets transmitted in egress queues with different priorities. Indicates the number of bytes in the packets transmitted in egress queues with different priorities. Indicates the number of packets with matched CVLAN priorities in the DS domain Indicates the number of bytes in the packets with matched C-VLAN priorities in the DS domain.
QOS_PRI_DROPBYTES
PORT_PRI_SND PKTS
PORT_PRI_SND BYTES
Port DS dom ain
DS_CVLANPRI_ PKTS
DS_CVLANPRI_ BYTES
Issue 03 (2012-07-30)
835
Performance Name
Description
Remarks
Source
DS_SVLANPRI_ PKTS
Indicates the number of packets with matched SVLAN priorities in the DS domain. Indicates the number of bytes in the packets with matched S-VLAN priorities in the DS domain. Indicates the number of packets with matched IP DSCP priorities in the DS domain. Indicates the number of bytes in the packets with matched IP DSCP priorities in the DS domain. Indicates the packet loss rate on the PW.
DS_SVLANPRI_ BYTES
DS_DSCP_PKTS
DS_DSCP_BYTE S
MP LSTP OA M
MPLS_PW_FLR
Packet loss ratio = (Number of packets transmitted by the source PW Number of packets received by the sink PW)/Number of packets transmitted by the source PW
CSH
Issue 03 (2012-07-30)
836
Performance Name
Description
Remarks
Source
MPLS_PW_FL
Indicates the packet loss number on the PW.
Number of lost packets = Number of packets transmitted by the source - Number of packets received by the sink (Both numbers are detected by the performance monitoring scheme of OAM.) Frame delay = Time when the source PW sends a request packet Time when the source PW receives the response packet Frame delay variation is the difference between two frame delay test results. Packet loss ratio = (Number of packets transmitted by the source TUNNEL Number of packets received by the sink TUNNEL)/ Number of packets transmitted by the source TUNNEL
MPLS_PW_FD
Indicates the frame delay on the PW.
MPLS_PW_FDV
Indicates the frame delay variation on the PW.
MPLS_TUNNEL_ FLR
Indicates the packet loss rate in the tunnel.
Issue 03 (2012-07-30)
837
Performance Name
Description
Remarks
Source
MPLS_TUNNEL_ FL
Indicates the packet loss number in the tunnel.
Number of lost packets = Number of packets transmitted by the source - Number of packets received by the sink (Both numbers are detected by the performance monitoring scheme of OAM.) Frame delay = Time when the source TUNNEL sends a request packet - Time when the source TUNNEL receives the response packet Frame delay variation is the difference between two frame delay test results. Packet loss ratio = (Number of packets transmitted by the source PW Number of packets received by the sink PW)/Number of packets transmitted by the source PW ML1, MD1
MPLS_TUNNEL_ FD
Indicates the frame delay in the tunnel.
MPLS_TUNNEL_ FDV
Indicates the frame delay variation in the tunnel.
AT M PW E3 perf orm ance / CES perf orm ance even ts
MPLS_PW_FLR
Indicates the packet loss rate on the PW.
Issue 03 (2012-07-30)
838
Performance Name
Description
Remarks
Source
MPLS_PW_FL
Indicates the packet loss number on the PW.
Number of lost packets = Number of packets transmitted by the source - Number of packets received by the sink (Both numbers are detected by the performance monitoring scheme of OAM.) Frame delay = Time when the source PW sends a request packet Time when the source PW receives the response packet Frame delay variation is the difference between two frame delay test results. ML1, MD1, CQ1
MPLS_PW_FD
Indicates the frame delay on the PW.
MPLS_PW_FDV
Indicates the frame delay variation on the PW.
PPP
PPP_TX_PKTS
Indicates the number of transmitted PPP packets. Indicates the number of bytes of transmitted PPP packets. Indicates the number of received PPP packets. Indicates the number of bytes of received PPP packets.
PPP_TX_BYTES
PPP_RX_PKTS
PPP_RX_BYTES
Issue 03 (2012-07-30)
839
Performance Name
Description
Remarks
Source
PPP_RX_FCSPK TS
Indicates the number of PPP packets that received FCS faults. Indicates the number of PPP packets dropped in the transmitting process. Indicates the number of relieved abnormal PPP packets. Indicates the PPP bandwidth usage in the receive direction.
PPP_TX_LOSPK TS
PPP_RX_LOSPK TS
PPP_RX_BW_UT ILIZATION
PPP bandwidth usage = (Number of received bytes x 8/Monitoring period)/ Configured or actual bandwidth PPP bandwidth usage = (Number of transmitted bytes x 8/ Monitoring period)/ Configured or actual bandwidth ML1, MD1, CQ1
PPP_TX_BW_UT ILIZATION
Indicates the PPP bandwidth usage in the transmit direction.
ML PPP
MP_TX_PKTS
Indicates the number of transmitted MP packets. Indicates the number of bytes of transmitted MP packets. Indicates the number of received MP packets.
MP_TX_BYTES
MP_RX_PKTS
Issue 03 (2012-07-30)
840
Performance Name
Description
Remarks
Source
MP_RX_BYTES
Indicates the number of bytes of received MP packets. Indicates the number of received MP packets. Indicates the total number of transmitted MP packets. Indicates the total number of received MP packets. Indicates the MP bandwidth usage in the receive direction.
MP_RX_ERRPK TS MP_TX_TOTALP KTS
The transmitted MP packets include service and protocol packets. The received MP packets include service and protocol packets. MP bandwidth usage = (Number of received bytes x 8/Monitoring period)/ Configured or actual bandwidth MP bandwidth usage = (Number of transmitted bytes x 8/ Monitoring period)/ Configured or actual bandwidth
MP_RX_TOTAL PKTS
MP_RX_BW_UTI LIZATION
MP_TX_BW_UTI LIZATION
Indicates the MP bandwidth usage in the transmit direction.
Issue 03 (2012-07-30)
841

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 950 do not support the VLAN-based and VUNI-based RMON performance statistics. l Integrated IP radio ports support this parameter. l Only the SL92CSH board support MPLS-TP OAM. l Ports whose Port Mode is Layer 3 do not support RMON performance events of traffic classifications or port DS domains.
D.3 List of RMON Performance Entries on the EoS/EoPDH Plane

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 RMON performance events on the EoPDH plane include PORT1 to PORT8, and VCTRUNK1 to VCTRUNK8 on the EMS6 board. Table D-5 List of RMON performance entries on the EoS/EoPDH plane Cat egor y of Perf orm anc e Entr ies Basi c perf orm ance Brief Name of a Performance Entry Full Name of a Performance Entry Remarks Source Port
RXOCTETS
Indicates the bytes received (bytes).
RXOCTETS indicates the total number of bytes in received packets (including bad packets), including framing bits but not FCS bytes. RXBRDCAST indicates the total number of received good packets with broadcast destination addresses, excluding multicast packets.
PORT1 to PORT9 on the EFP8 board PORT1 to PORT7 on the EMS6 board
RXBRDCAST
Issue 03 (2012-07-30)
842
Cat egor y of Perf orm anc e Entr ies
Brief Name of a Performance Entry
Full Name of a Performance Entry
Remarks
Source Port
RXMULCAST
RXMULCAST indicates the total number of received good packets with multicast destination addresses, excluding broadcast packets. Oversized packets are the packets larger than MTU (including FCS bytes but not framing bits). Bad packets, broadcast packets, and multicast packets are included. ETHJAB indicates the number of received packets that are larger than MTU (including FCS bytes but not framing bits) and contain FCS errors or alignment errors. -
ETHOVER
Indicates the oversized packets received (packets).
RXPKTS
Indicates the packets received (packets).
ETHJAB
Indicates the oversized error packets received (packets).
ETHFCS
The number of frames that have FCS check errorsThe number of alignment error frames
ETHALI
An alignment error frame contains a fractional number of bytes and fails to pass the FCS check.
PORT3 to PORT6 on the EMS6 board
Issue 03 (2012-07-30)
843
Remarks
Source Port
ETHUNDER
Undersized packets received (packets)
Indicates the number of received packets that are shorter than 64 bytes (including FCS bytes but not framing bits) and do not contain any other errors except for FCS errors. Indicates the total number of received packets that have FCS or alignment errors (FCS bytes are included but framing bits are excluded). The count increases because of noise collisions. FCS bytes are included but framing bits are excluded. FCS bytes are included but framing bits are excluded. FCS bytes are included but framing bits are excluded. FCS bytes are included but framing bits are excluded.
ETHFRG
Fragments received (packets)
RXPKT64
Packets received (64 bytes in length) (packets) Packets received (65-127 bytes in length) (packets) Packets received (128-255 bytes in length) (packets) Packets received (256-511 bytes in length) (packets)
RXPKT65
RXPKT128
RXPKT256
Issue 03 (2012-07-30)
844
Remarks
Source Port
RXPKT512
Packets received (512-1023 bytes in length) (packets) Packets received (1024-1518 bytes in length) (packets) Control frames received (frames) Bytes transmitted (bytes)
FCS bytes are included but framing bits are excluded. FCS bytes are included but framing bits are excluded. Indicates the total number of bytes (including those in bad packets) transmitted (including FCS bytes but not framing bits). Bad packets, broadcast packets, and multicast packets are included. FCS bytes are included but framing bits are excluded. FCS bytes are included but framing bits are excluded. FCS bytes are included but framing bits are excluded. PORT1 to PORT9 on the EFP8 board PORT1 to PORT7 on the EMS6 board
RXPKT1024
Exte nded perf orm ance
RXCTLPKTS TXOCTETS
TXPKTS
Packets transmitted (packets)
TXCTLPKTS TXPKT64
Control frames transmitted (frame) Packets transmitted (64 bytes in length) (packets) Packets transmitted (65-127 bytes in length) (packets) Packets transmitted (128-255 bytes in length) (packets)
TXPKT65
TXPKT128
Issue 03 (2012-07-30)
845
Remarks
Source Port
TXPKT256
Packets transmitted (256-511 bytes in length) (packets) Packets transmitted (512-1023 bytes in length) (packets) Packets transmitted (1024-1518 bytes in length) (packets) Alignment error frames (frames)
FCS bytes are included but framing bits are excluded. FCS bytes are included but framing bits are excluded. FCS bytes are included but framing bits are excluded. An alignment error frame contains a fractional number of bytes and fails to pass the FCS check. FCS bytes are included but framing bits are excluded. FCS bytes are included but framing bits are excluded. FCS bytes are included but framing bits are excluded. FCS bytes are included but framing bits are excluded.
TXPKT512
TXPKT1024
ETHALI
PKT64
Packets received and transmitted (64 bytes in length) (packets) Packets received and transmitted (65-127 bytes in length) (packets) Packets received and transmitted (128-255 bytes in length) (packets) Packets received and transmitted (256-511 bytes in length) (packets)
PKT65
PKT128
PKT256
Issue 03 (2012-07-30)
846
Remarks
Source Port
PKT512
Packets received and transmitted (512-1023 bytes in length) (packets) Packets received and transmitted (1024-1518 bytes in length) (packets) Indicates the maximum throughput at a port in the receive direction.
FCS bytes are included but framing bits are excluded. FCS bytes are included but framing bits are excluded. Maximum throughput = Number of received bytes (including interframe gaps and preambles)/ Monitoring period Minimum throughput = Number of received bytes (including interframe gaps and preambles)/ Monitoring period Average throughput = Number of received bytes (including interframe gaps and preambles)/ Monitoring period Framing bits (20 bytes) and FCS bytes are included. PORT1 to PORT9 on the EFP8 board PORT1 to PORT7 on the EMS6 board PORT1 to PORT9 on the EFP8 board
PKT1024
ETH_RX_THRO UGHPUT_MAX
ETH_RX_THRO UGHPUT_MIN
Indicates the minimum throughput at a port in the receive direction.
ETH_RX_THRO UGHPUT_AVG
Indicates the average throughput at a port in the receive direction.
RXGOODFULLF RAMESPEED
Indicates the rate of good full-frame bits received (Kbit/ s).
Issue 03 (2012-07-30)
847
Remarks
Source Port
TXGOODFULLF RAMESPEED
Indicates the rate of good full-frame bits transmitted (Kbit/s). Indicates the good full-frame bytes received (bytes). Indicates the good full-frame bytes transmitted (bytes). Indicates the multicast packets transmitted (packets). Indicates the unicast packets received (packets). Indicates the unicast packets transmitted (packets). Indicates the broadcast packets transmitted (packets). Indicates the pause frames received (frames).
Framing bits (20 bytes) and FCS bytes are included. Framing bits (20 bytes) and FCS bytes are included. Framing bits (20 bytes) and FCS bytes are included. The multicast packets that are discarded or fail to be transmitted are included. RXUNICAST indicates the number of good unicast packets. The unicast packets that are discarded or fail to be transmitted are included. The broadcast packets that are discarded or fail to be transmitted are included. RXPAUSE indicates the number of MAC flow control frames with the PAUSE opcode.
RXFULLBGOOD
TXFULLBGOOD
TXMULCAST
RXUNICAST
TXUNICAST
TXBRDCAST
RXPAUSE
Issue 03 (2012-07-30)
848
Remarks
Source Port
TXPAUSE
Indicates the pause frames transmitted (frames).
TXPAUSE indicates the number of MAC flow control frames with the PAUSE opcode. VCTRUNK1 to VCTRUNK16 on the EFP8 board VCTRUNK1 to VCTRUNK8 on the EMS6 board
VC G perf orm ance
VCG_TXGOODP ACKETS VCG_TXPACKE TS
Good packets transmitted (packets) Packets transmitted (packets)
Bad packets, broadcast packets, and multicast packets are included. Bad packets are included (FCS bytes are included but framing bits are excluded). Bad packets, broadcast packets, and multicast packets are included. Bad packets are included (FCS bytes are included but framing bits are excluded). Bad packets are included (FCS bytes are included but framing bits are excluded).
VCG_TXOCTET S
Bytes transmitted (bytes)
VCG_RXGOODP ACKETS VCG_RXPACKE TS
Good packets received (packets) Packets received (packets)
VCG_RXOCTET S
Bytes received (bytes)
VCG_TXSPEED
Speed of bytes transmitted (bytes)
Issue 03 (2012-07-30)
849
Remarks
Source Port
VCG_RXSPEED
Speed of bytes received (bytes)
Bad packets are included (FCS bytes are included but framing bits are excluded).
D.4 RMON Events and Handling Procedures

This chapter describes the RMON events that indicate Ethernet service abnormalities and how to handle these events.
D.4.1 ETHDROP
Description
ETHDROP indicates the number of events in which packet loss occurs due to resource deficiency of Ethernet chips. An RMON threshold-crossing event is reported when the number of packet loss events is higher than the upper threshold or lower than the lower threshold.
NOTE
ETHDROP counts only the packets that are lost due to resource deficiency of Ethernet chips.
Impact on System
When packet loss occurs frequently, services are affected and the system is affected seriously. Hence, you must rectify the fault immediately.
Possible Causes
This performance event indicates packet loss due to the full MAC buffer, FIFO overflow, or backward pressure. l l The lower threshold is not set to a non-zero value. The hardware at the local end is faulty.
Procedure
Step 1 Handle this alarm according to the specific performance event.
If... The number is lower than the lower threshold The number is higher than the upper threshold Step 2 Replace the involved part. ----End
Then... Change the lower threshold to 0. Manually decrease the traffic transmitted from the opposite end. If the problem persists, go to the next step.
Reference
None.
D.4.2 ETHEXCCOL
Description
ETHEXCCOL indicates the number of frames that fail to be transmitted due to continuous port collisions. An RMON threshold-crossing event is reported when the number of frames that fail to 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 device that work in halfduplex mode.
Procedure
Step 1 Handle this alarm according to the specific performance event. If... The number is lower than the lower threshold The number is higher than the upper threshold Then... Change the lower threshold to 0. Go to the next step.
Step 2 On the NMS, query the working modes of the ports on the equipment at both ends. If... The ports on the equipment at both ends work in inconsistent modes, or any port works in half-duplex mode Then... Set the working modes of the ports on the equipment at both ends to full-duplex or autonegotiation, so that these ports work in consistent modes.
851
Issue 03 (2012-07-30)
If...
Then...
The ports on the equipment at both ends Go to the next step. work in consistent modes and no ports work in half-duplex mode Step 3 Replace the involved part. ----End
Reference
None.
D.4.3 ETHLATECOL
Description
ETHLATECOL indicates the number of collisions detected within a timeslot period after a packet is transmitted. An RMON threshold-crossing event is reported when the number of collisions is higher than the upper threshold or lower than the lower threshold.
Impact on System
Possible Causes
Generally, this performance event is caused by a large network diameter.
Procedure
The ports on the equipment at both ends Go to the next step. work in consistent modes and no ports work in half-duplex mode Step 3 Check whether the network diameter of the LAN is very large according to the networking planning information.
If... The network diameter is very large
Then... Divide the network and deploy equipment to different buses or physically shared devices (such as hubs).
NOTE In the case of the 10 Mbit/s port rate, the maximum Ethernet diameter 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. Step 4 Replace the involved part. ----End
Reference
None.
D.4.4 RXBBAD
Description
RXBBAD indicates the total number of bytes in received bad packets, excluding the framing bit but including the FCS byte. An RMON threshold-crossing event is reported when the total number of bytes in received bad packets is higher than the upper threshold or lower than the lower threshold.
Impact on System
A port discards bad packets. This may even interrupt system services.
Possible Causes
1. 2. 3. Errors occur when the opposite end transmits packets. The transmission line is of the poor quality and bit errors exist. The hardware at the local end is faulty.
Procedure
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 is damaged or over attenuated. If yes, see the related handling method to clear the alarm.
Step 4 Replace the involved part. ----End
Reference
None.
D.4.5 TXDEFFRM
Description
TXDEFFRM indicates the number of frames the first transmission of which is delayed due to the congestion on the transmission media, excluding the number of frames the first transmission of which is delayed due to collisions. An RMON threshold-crossing event is reported when the number of frames that fail to be transmitted is higher than the upper threshold and lower than the lower threshold.
Impact on System
The rate of frame transmission decreases, and therefore packets are congested at a port and the throughput of the port decreases.
Possible Causes
Generally, this event is caused when the external port at the local end is connected to a device that work in half-duplex mode.
Procedure
Reference
None.
D.4.6 ETHUNDER
Description
ETHUNDER indicates that an RMON threshold-crossing event is reported when the number of packets that are shorter than 64 bytes and are received on the line side crosses the preset threshold.
Impact on System
The data frames whose length is not within the specific range are discarded. As a result, the system services are affected.
Possible Causes
1. 2. The length of a data frame that is received at a port is shorter than 64 bytes. 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 packet Rectify the fault on the opposite equipment. that is shorter than 64 bytes The opposite end does not transmit the packet that is shorter than 64 bytes Step 2 Replace the involved part. ----End Go to the next step.
Reference
None.
D.4.7 ETHOVER
Description
ETHOVER indicates that an RMON threshold-crossing event is reported when the number of packets that are longer than MTU and are received at a port crosses the preset threshold.
Impact on System
If the length of the data frame received at a port is more than the preset maximum frame length, the data frame is discarded and therefore the system services are affected.
Possible Causes
1. 2. The preset maximum frame length is less than the length of the frame that is received at a port. The hardware at the local end is faulty.
Procedure
Step 1 Check whether the opposite equipment transmits the packet that is longer than the maximum frame length set for the local equipment. If... The opposite equipment transmits the packet that is longer than the maximum frame length set for the local equipment Then... Notify the opposite equipment that the length of transmitted frames should be changed.
The opposite equipment does not transmit Go to the next step. the packet that is longer than the maximum frame length set for the local equipment Step 2 Replace the involved part. ----End
Reference
None.
D.4.8 ETHFRG
Description
ETHFRG indicates that an RMON threshold-crossing event is reported when the number of received packets that are shorter than 64 bytes and have FCS or alignment errors exceeds the preset upper threshold.
Impact on System
Data transmission is delayed or packet loss occurs.
Possible Causes
l l l The working modes of the ports on the equipment at both ends are not consistent. The hardware at the local end is faulty. The ports on the equipment at both ends work in half-duplex mode, and the data traffic is very heavy.
Procedure
Step 1 Check whether the working modes of the ports on the equipment at both ends are consistent.
If... The working modes are consistent
The working modes are not consistent Change the working mode of the local port so that the ports on the equipment at both ends work in consistent modes. Step 2 Check whether the working modes of the ports on the equipment at both ends are set to the halfduplex mode. If... Then...
The working modes are not set to the half- Go to the next step. duplex mode The working modes are set to the halfduplex mode Step 3 Replace the involved part. ----End Change the working modes of the ports on the equipment at both ends to the full-duplex mode or adaptive mode.
D.4.9 ETHJAB
Description
ETHJAB indicates that an RMON threshold-crossing alarm is reported when the number of received packets that are longer than MTU and have FCS or alignment errors is higher than the upper threshold.

Data transmission is delayed or packet loss occurs.
Possible Causes
l l The working modes of the ports on the equipment at both ends are not consistent. The hardware at the local end is faulty.
Procedure
Step 1 Check whether the working modes of the ports on the equipment at both ends are consistent. If... The working modes are consistent Then... Go to the next step.
The working modes are not consistent Change the working mode of the local port so that the ports on the equipment at both ends work in consistent modes. Step 2 Replace the involved part. ----End
D.4.10 ETHCOL
Description
ETHCOL indicates the number of detected packet collisions. An RMON threshold-crossing event is reported when the number of collisions is higher than the upper threshold or lower than the lower threshold.
Impact on System
Possible Causes
Generally, this event is caused when the local port is connected to a large number of devices that work in half-duplex mode.
Procedure
Reference
None.
D.4.11 ETHFCS
Description
ETHFCS indicates the number of received Ethernet data frames with FCS check errors at the local end (excluding the oversized and undersized frames). An RMON threshold-crossing event is 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 in the worst case.
Possible Causes
1. 2. 3. 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. The transmission line is of the poor quality and bit errors exist. The hardware at the local end is faulty.
Procedure
Step 1 Therefore, handle the alarm according to the specific performance event. If... The number is lower than the lower threshold The number is higher than the upper threshold Then... Change the lower threshold to 0. Go to the next step.
Step 2 On the NMS, query the working modes of the ports on the equipment at both ends. If... The ports on the equipment at both ends work in inconsistent modes The ports on the equipment at both ends work in consistent modes Step 3 Replace the involved part. ----End Then... Change the working modes of the ports on the equipment at both ends so that they can work in consistent modes Go to the next step.
Reference
None.
D.4.12 ATMPW_LOSPKTS
Description
The ATMPW_LOSPKTS is a performance event indicating the number of lost ATM PW packets.

None.
Possible Causes
1. 2. 3. 4. Signals on the radio link deteriorate. A strong interference source is present near the equipment. A board at the transmit or receive end is faulty. 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 performance event is cleared. Step 3 On the NMS, query the working modes of the ports on the equipment at both ends. 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 disordered ATM PW packets.

None.
Possible Causes
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 performance event is cleared. Step 3 On the NMS, query the working modes of the ports on the equipment at both ends.
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.14 ATMPW_UNKNOWNCELLS
Description
The ATMPW_UNKNOWNCELLS a performance event indicating the number of unknown cells in an ATM PW service.

None.
Possible Causes
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 performance event is cleared. Step 3 On the NMS, query the working modes of the ports on the equipment at both ends. 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.15 ATM_CORRECTED_HCSERR
Description
The ATM_CORRECTED_HCSERR is a performance event indicating the number of cells that are received by an ATM port and contain correctable header check sequence (HCS) errors.

None.
Possible Causes
1. 2. 3. A strong interference source is present near the equipment. A board at the transmit or receive end is faulty. The operating temperature of the equipment is very high.
Procedure
Step 1 Remove the interference source near the equipment and then check whether the performance event is cleared. Step 2 On the NMS, query the working modes of the ports on the equipment at both ends. Step 3 Replace the faulty board and then check whether the performance event is cleared. Step 4 Rectify the fault in the fan so that the fan lowers the operating temperature of the equipment. ----End
Related Information
None.
D.4.16 ATM_UNCORRECTED_HCSERR
Description
The ATM_UNCORRECTED_HCSERR is a performance event indicating the number of cells that are received by an ATM port and contain uncorrectable header check sequence (HCS) errors.

None.
Possible Causes
Procedure
Step 1 Refer to 5.3 Troubleshooting the Radio Link and handle the fault on the radio link. Step 2 Remove the interference source near the equipment and then check whether the performance event is cleared. Step 3 Replace the faulty board and then check whether the performance event is cleared.
Step 4 Rectify the fault in the fan so that the fan lowers the operating temperature of the equipment. ----End
Related Information
None.
D.4.17 CES_MISORDERPKTS
Description
The CES_MISORDERPKTS is a performance event indicating the count of lost disordered CES PW packets.

The packets are disordered. As a result, the packet loss rate increases and services are affected.
Possible Causes
1. 2. 3. Signals degrade on the link. The link is looped. The link is congested.
Related Alarms
CES_MISORDERPKT_EXC
Procedure
Step 1 See 5.3 Troubleshooting the Radio Link. Step 2 Release the loop. Step 3 Check the bandwidth utilization. If the bandwidth is exhausted, increase the bandwidth or eliminate any source that transmits a large amount of invalid data. ----End
Related Information
None.
D.4.18 CES_STRAYPKTS
Description
The CES_STRAYPKTS is a performance event indicating the number of misconnected packets in a period.

The packets are discarded. As a result, the packet loss rate increases and services are affected.
Possible Causes
1. Links are misconnected.
Related Alarms
CES_STRAYPKT_EXC
Procedure
Step 1 Check the link configuration and rectify the fault. ----End
Related Information
None.
D.4.19 CES_MALPKTS
Description
The CES_MALPKTS is a performance event indicating the number of deformed CES packets in a period.

The packets are discarded. As a result, the packet loss rate increases and services are affected.
Possible Causes
1. 2. The RTP head enabling status is different between the two ends of the PW. Bit errors occur on the link.
Related Alarms
CES_MALPKT_EXC
Procedure
Step 1 Set the RTP head enabling status to the same on the two ends of the PW. For details, see Modifying CES Service Parameters. ----End
Related Information
None.
D.4.20 CES_JTRUDR
Description
The CES_JTRUDR is a performance event indicating the number of jitter buffer underflows.

When no packets are transmitted from the jitter buffer, the buffer underflows.
Possible Causes
1. 2. 3. 4. 5. Signals degrade on the link. The PSN network clocks used for the transmission of CES services are not synchronized. The link is looped. The link is congested. The size of buffer area is set to a low value.
Related Alarms
CES_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 transmission nodes, and optimizing transmission routes. Step 3 Release the loop. Step 4 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 Query the size of buffer area. For details, see Querying CES Service Information. Step 6 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
Related Information
None.
D.4.21 CES_JTROVR
Description
The CES_JTROVR is a performance event indicating the number of jitter buffer overflows.

The jitter buffer is insufficient. As a result, the buffer overflows.
Possible Causes
1. 2. 3. 4. The jitter buffer area is too small. The clocks are not synchronous. Link quality deteriorates, causing more jitters. There are too many hops of radio link on the network side, causing a large number of jitters.
Related Alarms
CES_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 3 Handle the fault on the radio link. For details, see 5.3 Troubleshooting the Radio Link. Step 4 Determine whether the hops can be reduced according to network planning. If yes, reduce the hops of radio link on the network side. ----End
Related Information
None.
D.4.22 CES_LOSPKTS
Description
The CES_LOSPKTS is a performance event indicating the number of CES packets lost in a period.

When this alarm occurs, all 1s are inserted and services are interrupted.
Possible Causes
1. 2. 3. The link transmission quality is poor. The link is configured as a loop. Link congestion occurs.
Related Alarms
CES_LOSPKT_EXC
Procedure
Step 1 Handle the fault on the radio link. For details, see 5.3 Troubleshooting the Radio Link.
Step 2 Release the loop. Step 3 Check the bandwidth utilization. If the bandwidth is exhausted, increase the bandwidth or eliminate any source that transmits a large amount of invalid data. ----End
Related Information
None.
Issue 03 (2012-07-30)
867
E Alarm Management
Alarm Management
The alarm management on the OptiX RTN 950 is classified into the NE alarm management and board alarm management. E.1 NE Alarm Management The NE alarm management function set by user is applicable to all the boards on the NE. E.2 Board Alarm Management The board alarm management function is only applicable to the board on which users have configured this function.
Issue 03 (2012-07-30)
868
E Alarm Management
E.1 NE Alarm Management

The 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 l l Settings of the alarm storage mode Setting of the alarm delay Setting of the alarm reversion mode
For details about these functions, see the manuals or online Help of the NMS.
E.2 Board Alarm Management

The board alarm management function is only applicable to the board on which users have configured this function.
E.2.1 Setting the Alarm Severity

Alarms are classified into four levels: critical, major, minor, and warning, according to their severities. 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 critical problem can be the failure, overload, or system restart of mission-critical boards. It must be cleared immediately. Otherwise, system breakdown may occur. Major alarm: A major alarm indicates failure of certain boards or links, such as communication links. Urgent action is required to rectify the fault as this type of alarms affects the QoS of the system. Minor alarm: A minor alarm indicates a non-service affecting problem that needs to be solved, for example, fan speed exceeds threshold alarm. This type of alarms does not affect the QoS of the system, but you need to locate and remove these faults in time. Warning alarm: A warning alarm indicates a potential error that may affect the QoS of the system, for example, License file expiring precaution alarm. This type of alarms needs to be handled based on actual conditions.
Critical alarms and major alarms need to be handled immediately to avoid system failures and service interruptions.
E.2.2 Alarm Suppression

The maintenance personnel can change the alarm monitoring attribute by setting the alarm suppression function. A board detects only the alarms that are not suppressed. The alarm suppression function helps users to ignore their unconcerned alarms. This function is supported by all the boards.
E.2.3 Alarm Auto-Report

If Alarm Auto-Report is set to Reported, all the detected alarms are reported to the NMS in a timely manner. If Alarm Auto-Report is set to Not Report, the alarms are reported only when
E Alarm Management
alarm query is performed on the NMS. The maintenance personnel can change the setting on the NMS. This function is supported by all the boards.
E.2.4 Alarm Reversion

In the case of a port that is not configured with services, certain alarms may be reported. To filter the alarms that users are not concerned, set these alarms to be reversed. In this manner, the alarm status at this port is the opposite to the actual case. That is, the status is displayed as normal when an alarm is actually reported. The alarm reversion function is available in three modes, namely, non-reversion, automatic reversion, and manual reversion. l Non-revertive In this mode, the alarms are monitored by default and alarm reversion cannot be enabled for a port. l Auto reversion In this mode, alarm reversion can be enabled for a port where alarms are reported. After alarm reversion is enabled at a port, alarms are not reported. When the current alarm is cleared, the alarm reversion automatically changes to the disabled status. That is, it changes to the non-reversion mode. Then, the alarm reporting status at the port is the same as the actual status. l Manual reversion In this mode, alarm reversion can be enabled for a port regardless of whether any alarms are reported at the port. After alarm reversion is enabled, the alarm reporting status at the port is opposite to the actual status. After alarm reversion is manually disabled, the alarm reversion status changes to the non-reversion mode. Then, the alarm reporting status at the port is the same as the actual status. Pay attention to the following points when you set the alarm reversion function: l l Alarm reversion does not change the actual status of alarms on the board, as well as the indication status of the alarm indicators. Alarm reversion is realized on the NE software. The alarm data is the same on the NE and the NMS, which indicates the status after the alarm reversion. If you directly query the alarm data of a board, however, the actual alarm status is returned. Alarm reversion is set based on ports. It is supported by each port on the SP3S, SL1D, SP3D, IFX2, IFU2, IF1, EM6TA, EM6FA, SL1DA, ISU2, ISX2, ISV3, EM6T, EM6F, EG4, EG4P boards.
E.2.5 Setting of the Bit Error Alarm Threshold

When the number of bit errors detected by a board exceeds a specified number, the board generates a bit error alarm. This specific number is the bit error alarm threshold, and the setting of this threshold is supported by all the bit error threshold-crossing and degrading alarms on the NE.
Issue 03 (2012-07-30)
870
E Alarm Management
Table E-1 Setting of the bit error alarm threshold Alarm Name B1_EXC B1_SD B2_EXC B2_SD B3_EXC B3_SD BIP_EXC BIP_SD MW_BER_EXC MW_BER_SD Default Alarm Threshold 10-3 10-6 10-3 10-6 10-3 10-6 10-3 10-6 10-3 10-6 ISV3, ISU2, ISX2, EFP8, EMS6, SP3S, SP3D, IFU2, and IFX2 ISV3, ISU2, ISX2, IFU2 and IFX2 ISV3, SL1DA, SL1D and IF1 ISV3, SL1DA, SL1D and IF1 Applicable Board ISV3, SL1DA, SL1D and IF1
E.2.6 AIS Insertion

AIS insertion can be set for certain alarms reported on a board. When the board detects the alarms, it inserts all 1s into the lower level service to indicate the remote end that the service is unavailable. Table E-2 Setting of the AIS insertion Trigger Condition B1_EXC B2_SD B2_EXC HP_LOM HP_TIM HP_SLM HP_UNEQ B3_EXC B3_SD B1_SD LP_TIM Default Value Enabled Disabled Disabled Enabled Disabled Disabled Disabled Enabled Disabled Disabled Disabled ISV3, SL1DA, SL1D and IF1 SP3S and SP3D ISV3, SL1DA, SL1D and IF1 Applicable Board ISV3, SL1DA, SL1D and IF1 ISV3, SL1DA, SL1D and IF1 ISV3, SL1DA, SL1D and IF1
Issue 03 (2012-07-30)
871
E Alarm Management
Trigger Condition LP_UNEQ LP_SLM T_ALOS BIP_EXC BIP_SD MW_BER_EXC MW_BER_SD
Default Value Disabled Disabled Enabled Disabled Disabled Enabled Disabled
Applicable Board
ISV3, ISU2, ISX2, IFX2 and IFU2
NOTE
l When the SL1D/SL1DA//ISU2/ISX2/ISV3 board detects the R_LOS, R_LOF, MS_AIS, AU_AIS, or AU_LOP alarm, it forcibly inserts the AIS. l When the IF1/ISU2/ISX2/ISV3 board detects the MW_LOF, MW_LIM, R_LOF, MS_AIS, AU_AIS, or AU_LOP alarm, it forcibly inserts the AIS. l When the ISV3, ISU2, ISX2, IFX2 and IFU2 board detect the MW_LOF, MW_LIM, or R_LOF alarm, it forcibly inserts the AIS.
E.2.7 UNEQ Insertion

When a board detects that the service path is not in use or that the LOS alarm exists, it inserts all 0s into the service signal to notify the remote end that this signal is unavailable. Table E-3 Setting of the UNEQ insertion Trigger Condition T_ALOS Service path being not in use Default Value Disabled Disabled Applicable Board SP3S and SP3D
Issue 03 (2012-07-30)
872
F Performance Event Management
Performance Event Management
The performance event management is classified into the NE performance event management and board performance event management. F.1 NE Performance Event Management The NE performance event management function set by user is applicable to all the boards on the NE. F.2 Board Performance Event Management The performance event management function is only applicable to the board on which users have configured this function.
Issue 03 (2012-07-30)
873
F Performance Event Management
F.1 NE Performance Event Management

The NE performance event management function set by user is applicable to all the boards on the NE. The supports the following NE performance event management functions: l l l Setting NE performance event monitoring Setting the start/end time of performance events 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 Management

The performance event management function is only applicable to the board on which users have configured this function. Table F-1 Board performance event management function Function Setting 15-minute/24hour performance monitoring Setting 15-minute/24hour performance event auto-reporting Setting performance thresholds Resetting the performance register Generating performance threshold-crossing alarms Monitoring UAT events Monitoring CSES performance events Applicable Board ISV3, CQ1, SL1DA, EMS6, SL1D, SP3S, SP3D, CSH, CST, ODU, IFX2, IFU2, ISU2, ISX2, ML1, MD1, EFP8, and IF1 ISV3, CQ1, SL1DA, EMS6, SL1D, SP3S, SP3D, CSH, CST, ODU, IFX2, IFU2, ISU2, ISX2, ML1, MD1, EFP8, and IF1 ISV3, CQ1, SL1DA, EMS6, SL1D, SP3S, SP3D, IFX2, IFU2, ISU2, ISX2, ML1, MD1, EFP8, and IF1 ISV3, SL1DA, SL1D, SP3S, SP3D, ODU, IFX2, IFU2, ISU2, ISX2, and IF1 ISV3, CQ1, SL1DA, EMS6, SL1D, SP3S, SP3D, ODU, IFX2, IFU2, ISU2, ISX2, ML1, MD1, EFP8, and IF1 ISV3, CQ1, SL1DA, EMS6, SL1D, SP3S, SP3D, IFX2, IFU2, ISU2, ISX2, EFP8, and IF1 ISV3, CQ1, SL1DA, EMS6, SL1D, SP3S, SP3D, IFX2, IFU2, ISU2, ISX2, EFP8, and IF1
Issue 03 (2012-07-30)
874
G Alarm Suppression Relationship
G
MW_LOF
Alarm Suppression Relationship
When the alarm suppression function is disabled on an NE, the root alarm and certain correlated alarms 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 alarms when the root alarm is reported. The alarm suppression relationship can be classified into the suppression relationship between intra-board alarms and suppression relationship between interboard alarms. Table G-1 Suppression relationship between intra-board alarms Alarm Identifier Identifier of the Suppressed Alarm 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_RDI MW_BER_SD 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, IN_PWR_HIGH, LASER_CLOSED, LASER_MOD_ERR_EX 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 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, and MW_BER_SD
MW_LIM MW_BER_EXC LSR_NO_FITED
R_LOS or R_LOC
R_LOF
Issue 03 (2012-07-30)
875
Alarm Identifier MS_AIS
Identifier of the Suppressed Alarm 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_REI AU_LOP, B3_EXC, B3_SD, HP_TIM, HP_SLM, HP_UNEQ, HP_RDI, HP_LOM, and HP_REI B3_EXC, B3_SD, HP_TIM, HP_SLM, HP_UNEQ, HP_RDI, HP_LOM, and HP_REI HP_TIM, HP_LOM, and HP_RDI HP_REI LP_TIM, LP_RDI, LP_RFI, LP_REI, BIP_SD, and BIP_EXC LP_REI B1_SD, and MS_REI B2_SD, and MS_REI B3_SD LP_TIM, LP_UNEQ, LP_RDI, LP_REI, LP_RFI, LP_R_FIFO, BIP_EXC, BIP_SD, LP_SLM, TU_LOP, and DOWN_E1_AIS LP_TIM, LP_UNEQ, LP_RDI, LP_REI, LP_RFI, LP_R_FIFO, BIP_EXC, BIP_SD, LP_SLM, and DOWN_E1_AIS DOWN_E1_AIS, E1_LOS, DDN_LFA and UP_E1_AIS UP_E1_AIS BIP_SD ETH_LOS LFA, DDN_LFA, and ALM_E1RAI LMFA, ALM_IMA_LIF, and ALM_E1RAI ALM_IMA_LIF ALM_IMA_RFI, and ALM_IMA_RE_RX_UNUSABLE ETH_EFM_REMFAULT ETH_EFM_EVENT ALM_IMA_LODS VC_LOC, and VP_LOC
MS_RDI AU_AIS AU_LOP HP_UNEQ HP_RDI LP_UNEQ LP_RDI B1_EXC B2_EXC B3_EXC TU_AIS TU_LOP T_ALOS E1_LOS BIP_EXC LASER_MOD_ER R UP_E1_AIS LFA LMFA ALM_E1RAI ETH_EFM_DF ETH_EFM_REMF AULT ALM_IMA_LIF IMA_GROUP_LE _DOWN
Issue 03 (2012-07-30)
876
Alarm Identifier MPLS_TUNNEL_ LOCV MPLS_TUNNEL_ SF MPLS_TUNNEL_ FDI ETH_APS_PATH_ MISMATCH ETH_APS_LOST MPLS_PW_AIS
Identifier of the Suppressed Alarm MPLS_TUNNEL_UNKNOWN, MPLS_TUNNEL_Excess, and MPLS_TUNNEL_SF MPLS_TUNNEL_SD MPLS_TUNNEL_LOCV ETH_APS_LOST, ETH_APS_TYPE_MISMATCH, and ETH_APS_SWITCH_FAIL ETH_APS_TYPE_MISMATCH, and ETH_APS_SWITCH_FAIL MPLS_PW_LOCV, MPLS_PW_UNKNOWN, MPLS_PW_Excess, MPLS_PW_SF, MPLS_PW_SD, MPLS_PW_UNEXPMEP, and MPLS_PW_UNEXPPER MPLS_PW_UNKNOWN, MPLS_PW_Excess, and MPLS_PW_SF MPLS_PW_SD PWAPS_LOST, PWAPS_TYPE_MISMATCH, and PWAPS_SWITCH_FAIL PWAPS_TYPE_MISMATCH, and PWAPS_SWITCH_FAIL ETH_CFM_LOC
MPLS_PW_LOCV MPLS_PW_SF PWAPS_PATH_M ISMATCH PWAPS_LOST ETH_CFM_MISM ERGE ETH_CFM_UNEX PERI ETH_CFM_AIS CES_LOSPKT_EX C CES_STRAYPKT_ EXC PG_LINK_FAIL
CES_STRAYPKT_EXC, CES_JTROVR_EXC, and CES_JTRUDR_EXC CES_MISORDERPKT_EXC, and CES_MALPKT_EXC PG_PRT_DEGRADED
Table G-2 Suppression relationship between intra-board alarms Alarm Identifier R_LOS, R_LOC, MS_AIS, AU_AIS, or AU_LOP MW_LOF or MW_LIM Identifier of the Suppressed Alarm TU_AIS TU_AIS
Issue 03 (2012-07-30)
877
Alarm Identifier ETH_LOS MPLS_TUNNEL_LOCV MPLS_TUNNEL_BDI
Identifier of the Suppressed Alarm MPLS_TUNNEL_LOCV, MPLS_TUNNEL_OAMFAIL MPLS_PW_LOCV MPLS_PW_BDI
Issue 03 (2012-07-30)
878
H Indicators of Boards
H
Indicators of Boards
Indicator STAT State On (green) On (red) Off
Indicators of Boards
Table H-1 Status explanation for indicators on the CST Meaning The board is working properly. The board hardware is faulty. 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 at 100 ms intervals Blinks on (green) and off at 300 ms intervals On (green) Software is being loaded to the board during the power-on or resetting process of the board. The board software is in BIOS boot state during the power-on or resetting process of the board. l When the board is being powered on or being reset, the upper layer software is being initialized. l When the board is running, the software is running normally. Blinks on (red) and off at 100 ms intervals The BOOTROM self-check fails during the power-on or resetting process of the board.
Issue 03 (2012-07-30)
879
Indicator
State On (red)
Meaning l The memory self-check fails or loading upper layer software fails during the power-on or resetting process of the board. l The logic file or upper layer software is lost during the running process of the board. l The pluggable storage card is faulty. l When database synchronization between the active and standby system control boards fails, the PROG indicator on the standby system control board is steady red.
SYNC
On (green) On (red)
The clock is working properly. The clock source is lost or a clock switchover occurs. The system is working properly. A critical or major alarm occurs in the system. A minor or remote alarm occurs in the system. In a 1+1 protected system, the board works as the active one. In an unprotected system, the board has been activated.
SRV
On (green) On (red) On (yellow)
ACT
On (green)
Off
In a 1+1 protected system, the board works as the standby one. In an unprotected system, the board is not activated.
Table H-2 Status explanation for indicators on the CSH Indicator STAT State On (green) On (red) Off Meaning The board is working properly. The board hardware is faulty. l The board is not working. l The board is not created. l There is no power supplied to the board.
Issue 03 (2012-07-30)
880
Indicator PROG
State Blinks on (green) and off at 100 ms intervals Blinks on (green) and off at 300 ms intervals On (green)
Meaning Software is being loaded to the board during the power-on or resetting process of the board. The board software is in BIOS boot state during the power-on or resetting process of the board. l When the board is being powered on or being reset, the upper layer software is being initialized. l When the board is running, the software is running normally.
Blinks on (red) and off at 100 ms intervals On (red)
The BOOTROM self-check fails during the power-on or resetting process of the board. l The memory self-check fails or loading upper layer software fails during the power-on or resetting process of the board. l The logic file or upper layer software is lost during the running process of the board. l The pluggable storage card is faulty. l When database synchronization between the active and standby system control boards fails, the PROG indicator on the standby system control board is steady red.
SYNC
On (green) On (red)
The clock is working properly. The clock source is lost or a clock switchover occurs. The system is working properly. A critical or major alarm occurs in the system. A minor or remote alarm occurs in the system. In a 1+1 protected system, the board works as the active one. In an unprotected system, the board has been activated.
SRV
ACT
On (green)
Issue 03 (2012-07-30)
881
Indicator
State Off
Meaning In a 1+1 protected system, the board works as the standby one. In an unprotected system, the board is not activated.
Table H-3 Status explanation for indicators on the IF1 Indicator STAT State On (green) On (red) Off Meaning The board is working properly. The board hardware is faulty. l The board is not working. l The board is not created. l There is no power supplied to the board. SRV On (green) On (red) On (yellow) LINK On (green) On (red) ODU On (green) On (red) The services are normal. A critical or major alarm occurs in the services. A minor or remote alarm occurs in the services. The radio link is normal. The radio link is faulty. The ODU is working properly. l The ODU is reporting critical or major alarms. l There is no power supplied to the ODU. On (yellow) Blinks on (yellow) and off at 300 ms intervals Off RMT On (yellow) Off The ODU is reporting minor alarms. The antennas are not aligned. The ODU is offline. The remote equipment is reporting defects. The remote equipment is free of defects.
882
Issue 03 (2012-07-30)
Indicator ACT
State On (green)
Meaning l In a 1+1 protected system, the board works as the active one. l In an unprotected system, the board has been activated.
Off
l In a 1+1 protected system, the board works as the standby one. l In an unprotected system, the board is not activated.
Table H-4 Status explanation for indicators on the IFU2 Indicator STAT State On (green) On (red) Off Meaning The board is working properly. The board hardware is faulty. l The board is not working. l The board is not created. l There is no power supplied to the board. SRV On (green) On (red) On (yellow) LINK On (green) On (red) ODU On (green) On (red) The services are normal. A critical or major alarm occurs in the services. A minor or remote alarm occurs in the services. The radio link is normal. The radio link is faulty. The ODU is working properly. l The ODU is reporting critical or major alarms. l There is no power supplied to the ODU. On (yellow) Blinks on (yellow) and off at 300 ms intervals Off The ODU is reporting minor alarms. The antennas are not aligned.
The ODU is offline.
Issue 03 (2012-07-30)
883
Indicator RMT
State On (yellow) Off
Meaning The remote equipment is reporting defects. The remote equipment is free of defects. l In a 1+1 protected system, the board works as the active one. l In an unprotected system, the board has been activated.
ACT
On (green)
Off
Table H-5 Status explanation for indicators on the ISU2 Indicator STAT State On (green) On (red) Off Meaning The board is working properly. The board hardware is faulty. l The board is not working. l The board is not created. l There is no power supplied to the board. SRV On (green) On (red) On (yellow) LINK On (green) On (red) ODU On (green) On (red) The services are normal. A critical or major alarm occurs in the services. A minor or remote alarm occurs in the services. The radio link is normal. The radio link is faulty. The ODU is working properly. l The ODU is reporting critical or major alarms. l There is no power supplied to the ODU. On (yellow) The ODU is reporting minor alarms.
Issue 03 (2012-07-30)
884
Indicator
State Blinks on (yellow) and off at 300 ms intervals Off
Meaning The antennas are not aligned. The ODU is offline. The remote equipment is reporting defects. The remote equipment is free of defects. l In a 1+1 protected system, the board works as the active one. l In an unprotected system, the board has been activated.
RMT
On (yellow) Off
ACT
On (green)
Off
Table H-6 Status explanation for indicators on the IFX2 Indicator XPIC State On (green) On (red) Off STAT On (green) On (red) Off Meaning The XPIC input signal is normal. The XPIC input signal is lost. The XPIC function is disabled. The board is working properly. The board hardware is faulty. l The board is not working. l The board is not created. l There is no power supplied to the board. SRV On (green) On (red) The services are normal. A critical or major alarm occurs in the services.
Issue 03 (2012-07-30)
885
Indicator
State On (yellow)
Meaning A minor or remote alarm occurs in the services. The radio link is normal. The radio link is faulty. The ODU is working properly. l The ODU is reporting critical or major alarms. l There is no power supplied to the ODU.
LINK
On (green) On (red)
ODU
On (green) On (red)
On (yellow) Blinks on (yellow) and off at 300 ms intervals Off RMT On (yellow) Off ACT On (green)
The ODU is reporting minor alarms. The antennas are not aligned. The ODU is offline. The remote equipment is reporting defects. The remote equipment is free of defects. l In a 1+1 protected system, the board works as the active one. l In an unprotected system, the board has been activated.
Off
Table H-7 Status explanation for indicators on the ISX2 Indicator XPIC State On (green) On (red) Meaning The XPIC input signal is normal. The XPIC input signal is lost.
Issue 03 (2012-07-30)
886
Indicator
State Off
Meaning The XPIC function is disabled. The board is working properly. The board hardware is faulty. l The board is not working. l The board is not created. l There is no power supplied to the board.
STAT
On (green) On (red) Off
SRV
The services are normal. A critical or major alarm occurs in the services. A minor or remote alarm occurs in the services. The radio link is normal. The radio link is faulty. The ODU is working properly. l The ODU is reporting critical or major alarms. l There is no power supplied to the ODU.
LINK
On (green) On (red)
ODU
On (green) On (red)
On (yellow) Blinks on (yellow) and off at 300 ms intervals Off RMT On (yellow) Off ACT On (green)
The ODU is reporting minor alarms. The antennas are not aligned. The ODU is offline. The remote equipment is reporting defects. The remote equipment is free of defects. l In a 1+1 protected system, the board works as the active one. l In an unprotected system, the board has been activated.
Issue 03 (2012-07-30)
887
Indicator
State Off
Meaning l In a 1+1 protected system, the board works as the standby one. l In an unprotected system, the board is not activated.
Table H-8 Status explanation for indicators on an ISV3 board Indicator XPIC State On (green) On (red) Off STAT On (green) On (red) Off SRV On (green) On (red) On (yellow) LINK On (green) On (red) ODU On (green) On (red) Meaning XPIC input signals are normal. XPIC input signals are lost. XPIC is disabled. The board is working properly. The board hardware is faulty. The board is not working, not created, or not powered on. Services are normal. A critical or major alarm has been reported. A minor or remote alarm has been reported. The radio link is normal. The radio link is faulty. The ODU is working properly. The ODU has reported a critical or major alarm, or was not powered on. The ODU has reported a minor alarm. Antennas are not well aligned. The ODU is offline.
On (yellow) Blinks on (yellow) and off at 300 ms intervals Off
Issue 03 (2012-07-30)
888
Indicator RMT
Meaning The remote equipment has reported a defect. The remote equipment is free of defects. In a 1+1 protected system, the board is working as the main board. In an unprotected system, the board has been activated.
ACT
On (green)
Off
In a 1+1 protected system, the board is working as the standby board. In an unprotected system, the board has not been activated.
Table H-9 Status explanation for indicators on the EM6T/EM6F Indicator STAT State On (green) On (red) Off Meaning The board is working properly. The board hardware is faulty. l The board is not working. l The board is not created. l There is no power supplied to the board. SRV On (green) On (red) On (yellow) Off PROG Blinks on (green) and off at 100 ms intervals Blinks on (green) and off at 300 ms intervals The system is working properly. A critical or major alarm occurs in the system. A minor alarm occurs in the system. There is no power supplied to the system. Software is being loaded to the board during the power-on or resetting process of the board. The board software is in BIOS boot state during the power-on or resetting process of the board.
Issue 03 (2012-07-30)
889
Indicator
State On (green)
Meaning l When the board is being powered on or being reset, the upper layer software is being initialized. l When the board is running, the software is running normally.
The BOOTROM self-check fails during the power-on or resetting process of the board. l The memory self-check fails or loading upper layer software fails during the power-on or resetting process of the board. l The logic file or upper layer software is lost during the running process of the board. l The pluggable storage card is faulty.
LINK1a
On (green) Blinking (green) Off
The GE1 port is connected correctly and is not receiving or transmitting data. The GE1 port is receiving or transmitting data. The GE1 port is not connected or is connected incorrectly. The GE2 port is connected correctly and is not receiving or transmitting data. The GE2 port is receiving or transmitting data. The GE2 port is not connected or is connected incorrectly.
LINK2a
On (green) Blinking (green) Off
NOTE a: The LINK1 and LINK2 indicators are available only on the EM6F and indicate the states of the corresponding GE ports.
Table H-10 Status explanation for indicators on the EM6TA/EM6FA Indicator STAT State On (green) On (red) Off Meaning The board is working properly. The board hardware is faulty. l The board is not working. l The board is not created. l There is no power supplied to the board.
Issue 03 (2012-07-30)
890
Indicator SRV
State On (green) On (red) On (yellow) Off
Meaning The system is working properly. A critical or major alarm occurs in the system. A minor alarm occurs in the system. There is no power supplied to the system. Software is being loaded to the board during the power-on or resetting process of the board. The board software is in BIOS boot state during the power-on or resetting process of the board. l When the board is being powered on or being reset, the upper layer software is being initialized. l When the board is running, the software is running normally.
PROG
Blinks on (green) and off at 100 ms intervals Blinks on (green) and off at 300 ms intervals On (green)
The BOOTROM self-check fails during the power-on or resetting process of the board. The memory self-check fails or loading upper layer software fails during the poweron or resetting process of the board. The logic file or upper layer software is lost during the running process of the board. The pluggable storage card is faulty.
L/A1a
On (green) Blinking (yellow) Off
The GE1 port is connected correctly and is not receiving or transmitting data. The GE1 port is receiving or transmitting data. The GE1 port is not connected or is connected incorrectly. The GE2 port is connected correctly and is not receiving or transmitting data. The GE2 port is receiving or transmitting data. The GE2 port is not connected or is connected incorrectly.
L/A2a
On (green) Blinking (yellow) Off
NOTE a: The L/A1 and L/A2 indicators are available only on the EM6FA and indicate the states of the corresponding GE ports.
Issue 03 (2012-07-30)
891
Table H-11 Status explanation for indicators on an EG4/EG4P board Indicator STAT State On (green) On (red) Off SRV On (green) On (red) On (yellow) Off L/A1 (optical/ electrical port 1) On (green) Blinks on (red) and off at 300 ms intervals Blinks on (red) for 300 ms and off for 700 ms at 1000 ms intervals Blinks (yellow) Off L/A2 (optical/ electrical port 2) On (green) Blinks on (red) and off at 300 ms intervals Blinks on (red) for 300 ms and off for 700 ms at 1000 ms intervals Blinks (yellow) Off L/A3 (electrical port 3) On (green) Blinks (yellow) Meaning The board is working properly. The board hardware is faulty. The board is not working, not created, or not powered on. Services are normal. A critical or major alarm has been reported. A minor alarm has been reported. No service is configured. Port GE1 is connected correctly but is not receiving or transmitting data. Port GE1 has received extremely high optical power (applicable only to an optical port). Port GE1 has received extremely low optical power (applicable only to an optical port). Port GE1 is receiving or transmitting data. Port GE1 is not connected or is incorrectly connected. Port GE2 is connected correctly but is not receiving or transmitting data. Port GE2 has received extremely high optical power (applicable only to an optical port). Port GE2 has received extremely low optical power (applicable only to an optical port). Port GE2 is receiving or transmitting data. Port GE2 is not connected or is incorrectly connected. Port GE3 is connected correctly but is not receiving or transmitting data. Port GE3 is receiving or transmitting data.
Issue 03 (2012-07-30)
892
Indicator
State Off
Meaning Port GE3 is not connected or is incorrectly connected. Port GE4 is connected correctly but is not receiving or transmitting data. Port GE4 is receiving or transmitting data. Port GE4 is not connected or is incorrectly connected. Power over Ethernet port 1 is enabled. Power over Ethernet port 1 is disabled or is working abnormally. Power over Ethernet port 2 is enabled. Power over Ethernet port 2 is disabled or is working abnormally.
L/A4 (electrical port 4)
On (green) Blinks (yellow) Off
P1
On (green) Off
P2
On (green) Off
NOTE Indicators P1 and P2 are available only on the front panels of EG4P boards, indicating the power supply status of power-over-Ethernet ports.
Table H-12 Status explanation for indicators on the EMS6 Indicator STAT State On (green) On (red) Off Meaning The board is working properly. The board hardware is faulty. 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 at 100 ms intervals Blinks on (green) and off at 300 ms intervals On (green) Software is being loaded to the board during the power-on or resetting process of the board. The board software is in BIOS boot state during the power-on or resetting process of the board. l The upper layer software is being initialized during the power-on or resetting process of the board. l The software is running properly during the running process of the board. Blinks on (red) and off at 100 ms intervals
Issue 03 (2012-07-30)
The BOOTROM self-check fails during the power-on or resetting process of the board.
893
Indicator
State On (red)
Meaning l The memory self-check fails or loading upper layer software fails during the power-on or resetting process of the board. l The logic file or upper layer software is lost during the running process of the board. l The pluggable storage card is faulty.
SRV
On (green) On (red) On (yellow) Off
The system is working normally. A critical or major alarm occurs in the system. A minor alarm occurs in the system. There is no power supplied to the system. The GE1 port is connected correctly. The receive optical power at the GE1 optical port is higher than the upper threshold. The receive optical power at the GE1 optical port is lower than the lower threshold. The GE1 port is not connected or is connected incorrectly. The GE1 port is receiving or transmitting data. The GE1 port is not receiving or transmitting data. The GE2 port is connected correctly. The receive optical power at the GE2 optical port is higher than the upper threshold. The receive optical power at the GE2 optical port is lower than the lower threshold. The GE1 port is not connected or is connected incorrectly. The GE2 port is receiving or transmitting data. The GE2 port is not receiving or transmitting data.
LINK1
On (green) Blinks on (red) and off at 300 ms intervals Blinks 300 ms on (red) and 700 ms off Off
ACT1
Blinking (yellow) Off
LINK2
On (green) Blinks on (red) and off at 300 ms intervals Blinks 300 ms on (red) and 700 ms off Off
ACT2
Blinking (yellow) Off
Issue 03 (2012-07-30)
894
Table H-13 Status explanation for indicators on the EFP8 Indicator STAT State On (green) On (red) Off Meaning The board is working properly. The board hardware is faulty. 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 at 100 ms intervals Blinks on (green) and off at 300 ms intervals On (green) Software is being loaded to the board during the power-on or resetting process of the board. The board software is in BIOS boot state during the power-on or resetting process of the board. l When the board is being powered on or being reset, the upper layer software is being initialized. l When the board is running, the software is running normally. Blinks on (red) and off at 100 ms intervals On (red) The BOOTROM self-check fails during the power-on or resetting process of the board. l The memory self-check fails or loading upper layer software fails during the power-on or resetting process of the board. l The logic file or upper layer software is lost during the running process of the board. l The pluggable storage card is faulty. SRV On (green) On (red) On (yellow) Off The system is working properly. A critical or major alarm occurs in the system. A minor alarm occurs in the system. There is no power supplied to the system.
Table H-14 Status explanation for indicators on the SL1D/SL1DA Indicator STAT State On (green) Meaning The board is working properly.
Issue 03 (2012-07-30)
895
Indicator
State On (red) Off
Meaning The board hardware is faulty. l The board is not working. l The board is not created. l There is no power supplied to the board.
SRV
On (green) On (red) On (yellow) Off
The services are normal. A critical or major alarm occurs in the services. A minor or remote alarm occurs in the services. The services are not configured. The first port of the SL1D/ SL1DA is reporting the R_LOS alarm. The first port of the SL1D/ SL1DA is free of R_LOS alarms. The second port of the SL1D/SL1DA is reporting the R_LOS alarm. The second port of the SL1D/SL1DA is free of R_LOS alarms.
LOS1
On (red)
Off
LOS2
On (red)
Off
Table H-15 Status explanation for indicators on the SP3S/SP3D Indicator STAT State On (green) On (red) Off Meaning The board is working properly. The board hardware is faulty. 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.
Issue 03 (2012-07-30)
896
Indicator
State On (red) On (yellow) Off
Meaning A critical or major alarm occurs in the services. A minor or remote alarm occurs in the services. The services are not configured.
Table H-16 Status explanation for indicators on the ML1/MD1 Indicator STAT State On (green) On (red) Off Meaning The board is working properly. The board hardware is faulty. l The board is not working. l The board is not created. l There is no power supplied to the board. SRV On (green) On (red) On (yellow) Off The services are normal. A critical or major alarm occurs in the services. A minor or remote alarm occurs in the services. The services are not configured.
Table H-17 Status explanation for indicators on a CQ1 board Indicator STAT State On (green) On (red) Off SRV On (green) On (red) Meaning The board is working properly. The board hardware is faulty. The board is not working, not created, or not powered on. Services are normal. A critical or major alarm has been reported.
Issue 03 (2012-07-30)
897
Indicator
Meaning A minor or remote alarm has been reported. No service is configured. The first port has reported an R_LOS alarm. The first port does not report any R_LOS alarms. The second port has reported an R_LOS alarm. The second port does not report any R_LOS alarms. The third port has reported an R_LOS alarm. The third port does not report any R_LOS alarms. The fourth port has reported an R_LOS alarms. The fourth port does not report any R_LOS alarms.
LOS1
On (red) Off
LOS2
On (red) Off
LOS3
On (red) Off
LOS4
On (red) Off
Table H-18 Status explanation for indicators on the AUX Indicator STAT State On (green) On (red) Off Meaning The board is working properly. The board hardware is faulty. l The board is not working. l The board is not created. l There is no power supplied to the board. SRV On (green) On (red) On (yellow) Off The system is working properly. A critical or major alarm occurs in the system. A minor or remote alarm occurs in the system. There is no power supplied to the system.
Issue 03 (2012-07-30)
898
Table H-19 Status explanation for indicators on the PIU Indicator PWR Status On (green) Off Description The power supply is connected. There is no power supplied to the PIU or the power supply is connected incorrectly.
Table H-20 Status explanation for indicators on the FAN Indicator FAN State On (green) On (red) Off Meaning The fan is working properly. The fan is faulty. The fan is not powered on or is not installed.
NOTE
The CRIT, MAJ, or MIN indicator on the front panel of the FAN indicates the current alarm severity of the subrack.
Issue 03 (2012-07-30)
899
I Glossary
I
Numerics 3G 3GPP 3rd Generation (3G) See 3rd Generation. 3rd Generation Partnership Project 802.1Q in 802.1Q
Glossary
The third generation of digital wireless technology, as defined by the International Telecommunications Union (ITU). Third generation technology is expected to deliver data transmission speeds between 144 kbit/s and 2 Mbit/s, compared to the 9.6 kbit/s to 19.2 kbit/s offered by second generation technology. A VLAN feature that allows the equipment to add a VLAN tag to a tagged frame. The implementation of QinQ is to add a public VLAN tag to a frame with a private VLAN tag to allow the frame with double VLAN tags to be transmitted over the service provider's backbone network based on the public VLAN tag. This provides a Layer 2 VPN tunnel for customers and enables transparent transmission of packets over private VLANs.
A A/D ABR ACAP ACL ADC ADM AF AIS ALS AM APS ARP ASBR analog/digit See available bit rate. See adjacent channel alternate polarization. See access control list. analog to digital converter add/drop multiplexer See assured forwarding. alarm indication signal See automatic laser shutdown. See adaptive modulation. automatic protection switching See Address Resolution Protocol. See autonomous system boundary router.
Issue 03 (2012-07-30)
900
I Glossary
ASIC ATM ATPC AU Address Resolution Protocol (ARP) access control list (ACL) adaptive modulation (AM)
See application-specific integrated circuit. asynchronous transfer mode See automatic transmit power control. See administrative unit. An Internet Protocol used to map IP addresses to MAC addresses. It allows hosts and routers to determine the link layer addresses through ARP requests and ARP responses. A list of entities, together with their access rights, which are authorized to have access to a resource. A technology that is used to automatically adjust the modulation mode according to the channel quality. When the channel quality is favorable, the equipment uses a highefficiency modulation mode to improve the transmission efficiency and the spectrum utilization of the system. When the channel quality is degraded, the equipment uses the low-efficiency modulation mode to improve the anti-interference capability of the link that carries high-priority services. A channel configuration method, which uses two adjacent channels (a horizontal polarization wave and a vertical polarization wave) to transmit two signals. The information structure which provides adaptation between the higher order path layer and the multiplex section layer. It consists of an information payload (the higher order VC) and an AU pointer which indicates the offset of the payload frame start relative to the multiplex section frame start. An alarm management method. Alarms that are set to be suppressed are not reported from NEs any more. A signal in which information is represented with a continuously variable physical quantity, such as voltage. Because of this constant changing of the wave shape with regard to its passing a given point in time or space, an analog signal might have a virtually indefinite number of states or values. This contrasts with a digital signal that is expressed as a square wave and therefore has a very limited number of discrete states. Analog signals, with complicated structures and narrow bandwidth, are vulnerable to external interference. A special type of chip that starts out as a nonspecific collection of logic gates. Late in the manufacturing process, a layer is added to connect the gates for a specific function. By changing the pattern of connections, the manufacturer can make the chip suitable for many needs. 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 that exceeds the bandwidth limit, AF degrades the service class and continues to forward the traffic instead of discarding the packets. A device used to increase the attenuation of an Optical Fiber Link. Generally used to ensure that the signal at the receive end is not too strong. A technique (procedure) to automatically shutdown the output power of laser transmitters and optical amplifiers to avoid exposure to hazardous levels.
adjacent channel alternate polarization (ACAP) administrative unit (AU)
alarm suppression analog signal
application-specific integrated circuit (ASIC) assured forwarding (AF)
attenuator automatic laser shutdown (ALS)
automatic transmit A method of adjusting the transmit power based on fading of the transmit signal detected power control (ATPC) at the receiver
Issue 03 (2012-07-30)
901
I Glossary
autonomous system boundary router (ASBR)
A router that exchanges routing information with other ASs.
available bit rate (ABR) A kind of service categories defined by the ATM forum. ABR only provides possible forwarding service and applies to the connections that does not require the real-time quality. It does not provide any guarantee in terms of cell loss or delay. B B-ISDN BDI BE BER BFD BGP BIOS BIP BPDU BSC BTS Bidirectional Forwarding Detection (BFD) See broadband integrated services digital network. See backward defect indication. See best effort. bit error rate See Bidirectional Forwarding Detection. Border Gateway Protocol See basic input/output system. See bit interleaved parity. See bridge protocol data unit. See base station controller. base transceiver station A simple Hello protocol, similar to the adjacent detection in the route protocol. Two systems periodically send BFD detection messages on the channel between the two systems. If one system does not receive the detection message from the other system for a long time, you can infer that the channel is faulty. Under some conditions, the TX and RX rates between systems need to be negotiated to reduce traffic load. A network that forms the central interconnection for a connected network. The communication backbone for a country is WAN. The backbone network is an important architectural element for building enterprise networks. It provides a path for the exchange of information between different LANs or subnetworks. A backbone can tie together diverse networks in the same building, in different buildings in a campus environment, or over wide areas. Generally, the backbone network's capacity is greater than the networks connected to it. A function that the sink node of a LSP, when detecting a defect, uses to inform the upstream end of the LSP of a downstream defect along the return path. A range of transmission frequencies that a transmission line or channel can carry in a network. In fact, it is the difference between the highest and lowest frequencies the transmission line or channel. The greater the bandwidth, the faster the data transfer rate. A logical entity that connects the BTS with the MSC in a GSM/CDMA network. It interworks with the BTS through the Abis interface, the MSC through the A interface. It provides the following functions: radio resource management, base station management, power control, handover control, and traffic measurement. One BSC controls and manages one or more BTSs in an actual network.
backbone network
backward defect indication (BDI) bandwidth
base station controller (BSC)
Issue 03 (2012-07-30)
902
I Glossary
basic input/output system (BIOS) baud rate
A firmware stored in the computer mainboard. It contains basic input/output control programs, power-on self test (POST) programs, bootstraps, and system setting information. The BIOS provides hardware setting and control functions for the computer. The number of times per second the signal can change on a transmission line. Commonly, the transmission line uses only two signal states, making the baud rate equal to the number of bits per second that can be transferred. The underlying transmission technique may use some of the bandwidth, so it may not be the case that user data transfers at the line's specified bit rate. A traditional IP packet transport service. In this service, the diagrams are forwarded following the sequence of the time they reach. All diagrams share the bandwidth of the network and routers. The amount of resource that a diagram can use depends of the time it reaches. BE service does not ensure any improvement in delay time, jitter, packet loss ratio, and high reliability. A method of error monitoring. With even parity an X-bit code is generated by equipment at the transmit end over a specified portion of the signal in such a manner that the first bit of the code provides even parity over the first bit of all X-bit sequences in the covered portion of the signal, the second bit provides even parity over the second bit of all X-bit sequences within the specified portion, and so on. Even parity is generated by setting the BIP-X bits so that there is an even number of 1s in each monitored partition of the signal. A monitored partition comprises all bits which are in the same bit position within the Xbit sequences in the covered portion of the signal. The covered portion includes the BIPX. A device that connects two or more networks and forwards packets among them. Bridges operate at the physical network level. Bridges differ from repeaters because bridges store and forward complete packets, while repeaters forward all electrical signals. Bridges differ from routers because bridges use physical addresses, while routers use IP addresses. The data messages that are exchanged across the switches within an extended LAN that uses a spanning tree protocol (STP) topology. BPDU packets contain information on ports, addresses, priorities and costs and ensure that the data ends up where it was intended to go. BPDU messages are exchanged across bridges to detect loops in a network topology. The loops are then removed by shutting down selected bridges interfaces and placing redundant switch ports in a backup, or blocked, state.
best effort (BE)
bit interleaved parity (BIP)
bridge
bridge protocol data unit (BPDU)
broadband integrated A standard defined by the ITU-T to handle high-bandwidth applications, such as voice. services digital network It currently uses the ATM technology to transmit data over SONNET-based circuits at (B-ISDN) 155 to 622 Mbit/s or higher speed. broadcast broadcast domain A means of delivering information to all members in a network. The broadcast range is determined by the broadcast address. A group of network stations that receives broadcast packets originating from any device within the group. The broadcast domain also refers to the set of ports between which a device forwards a multicast, broadcast, or unknown destination frame.
C CAR CBR CBS committed access rate See constant bit rate. See committed burst size.
Issue 03 (2012-07-30)
903
I Glossary
CC CCDP CDMA CE CES CGMP CIST CLNP CM CORBA CPU CRC CSES CSMA/CD CTC CW
See continuity check. See co-channel dual polarization. See Code Division Multiple Access. See customer edge. See circuit emulation service. Cisco Group Management Protocol See Common and Internal Spanning Tree. connectionless network protocol connection management See Common Object Request Broker Architecture. See central processing unit. See cyclic redundancy check. consecutive severely errored second See carrier sense multiple access with collision detection. common transmit clock control word
Code Division Multiple A communication scheme that forms different code sequences by using the frequency Access (CDMA) expansion technology. Subscribers with different addresses can use different code sequences for multi-address connection. Common Object A specification developed by the Object Management Group in 1992 in which pieces of Request Broker programs (objects) communicate with other objects in other programs, even if the two Architecture (CORBA) programs are written in different programming languages and are running on different platforms. A program makes its request for objects through an object request broker, or ORB, and thus does not need to know the structure of the program from which the object comes. CORBA is designed to work in object-oriented environments. See also IIOP, object (definition 2), Object Management Group, object-oriented. Common and Internal The single spanning tree jointly calculated by STP and RSTP, the logical connectivity Spanning Tree (CIST) using MST bridges and regions, and MSTP. The CIST ensures that all LANs in the bridged local area network are simply and fully connected. cable tie carrier sense multiple access with collision detection (CSMA/CD) A tape used to bind cables. Carrier sense multiple access with collision detection (CSMA/CD) is a computer networking access method in which: l l A carrier sensing scheme is used. A transmitting data station that detects another signal while transmitting a frame, stops transmitting that frame, transmits a jam signal, and then waits for a random time interval before trying to send that frame again.
central processing unit The computational and control unit of a computer. The CPU is the device that interprets and executes instructions. The CPU has the ability to fetch, decode, and execute (CPU) instructions and to transfer information to and from other resources over the computer's main data-transfer path, the bus.
Issue 03 (2012-07-30)
904
I Glossary
channel
A telecommunication path of a specific capacity and/or at a specific speed between two or more locations in a network. Channels can be established through wire, radio (microwave), fiber or a combination of the three. The amount of information transmitted per second in a channel is the information transmission speed, expressed in bits per second. For example, b/s, kb/s, Mb/s, Gb/s, and Tb/s. A function with which the E1/T1 data can be transmitted through ATM networks. At the transmission end, the interface module packs timeslot data into ATM cells. These ATM cells are sent to the reception end through the ATM network. At the reception end, the interface module re-assigns the data in these ATM cells to E1/T1 timeslots. The CES technology guarantees that the data in E1/T1 timeslots can be recovered to the original sequence at the reception end. The method to keep the time on each node synchronized with a clock source in a network. A channel configuration method, which uses a horizontal polarization wave and a vertical polarization wave to transmit two signals. The Co-Channel Dual Polarization has twice the transmission capacity of the single polarization. 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 committed information rate. This parameter must be larger than 0. It is recommended that this parameter should be not less than the maximum length of the IP packet that might be forwarded.
circuit emulation service (CES)
clock tracing co-channel dual polarization (CCDP) committed burst size (CBS)
constant bit rate (CBR) A kind of service categories defined by the ATM forum. CBR transfers cells based on the constant bandwidth. It is applicable to service connections that depend on precise clocking to ensure undistorted transmission. continuity check (CC) cross polarization interference cancellation (XPIC) customer edge (CE) cyclic redundancy check (CRC) Ethernet CFM can detect the connectivity between MEPs. The detection is achieved after MEPs transmit Continuity Check Messages (CCMs) periodically. A technology used in the case of the Co-Channel Dual Polarization (CCDP) to eliminate the cross-connect interference between two polarization waves in the CCDP. A part of BGP/MPLS IP VPN model. It provides interfaces for direct connection to the Service Provider (SP) network. A CE can be a router, switch, or host. A procedure used in checking for errors in data transmission. CRC error checking uses a complex calculation to generate a number based on the data transmitted. The sending device performs the calculation before transmission and includes it in the packet that it sends to the receiving device. The receiving device repeats the same calculation after transmission. If both devices obtain the same result, it is assumed that the transmission was error free. The procedure is known as a redundancy check because each transmission includes not only data but extra (redundant) error-checking values.
D DC DC-C DC-I DC-return common (with ground) (DC-C) direct current See DC-return common (with ground). See DC-return isolate (with ground). A power system, in which the BGND of the DC return conductor is short-circuited with the PGND on the output side of the power supply cabinet and also on the line between the output of the power supply cabinet and the electric equipment.
Issue 03 (2012-07-30)
905
I Glossary
DC-return isolate (with A power system, in which the BGND of the DC return conductor is short-circuited with ground) (DC-I) the PGND on the output side of the power supply cabinet and is isolated from the PGND on the line between the output of the power supply cabinet and the electric equipment. DCC DCN DDF DDN DE DM DS boundary node DS interior node DS node DSCP DVMRP DiffServ See data communications channel. See data communication network. digital distribution frame See digital data network. discard eligible See delay measurement. A DS node that connects one DS domain to a node either in another DS domain or in a domain that is not DS-capable. A DS node located at the center of a DS domain. It is a non-DS boundary node. A DS-compliant node, which is subdivided into DS boundary node and ID interior node. See differentiated services code point. See Distance Vector Multicast Routing Protocol. See Differentiated Services.
Differentiated Services An IETF standard that defines a mechanism for controlling and forwarding traffic in a (DiffServ) differentiated manner based on CoS settings to handle network congestion. Distance Vector Multicast Routing Protocol (DVMRP) data communication network (DCN) data communications channel (DCC) An Internet gateway protocol mainly based on the RIP. The protocol implements a typical dense mode IP multicast solution. The DVMRP protocol uses IGMP to exchange routing datagrams with its neighbors. A communication network used in a TMN or between TMNs to support the data communication function. The data channel that uses the D1D12 bytes in the overhead of an STM-N signal to transmit information about operation, management, maintenance and provision (OAM&P) between NEs. The DCC channels that are composed of bytes D1D3 are referred to as the 192 kbit/s DCC-R channel. The other DCC channels that are composed of bytes D4D12 are referred to as the 576 kbit/s DCC-M channel. The time elapsed since the start of transmission of the first bit of the frame by a source node until the reception of the last bit of the loopbacked frame by the same source node, when the loopback is performed at the frame's destination node. According to the QoS classification standard of the Differentiated Service (Diff-Serv), the type of services (ToS) field in the IP header consists of six most significant bits and two currently unused bits, which are used to form codes for priority marking. Differentiated services code point (DSCP) is the six most important bits in the ToS. It is the combination of IP precedence and types of service. The DSCP value is used to ensure that routers supporting only IP precedence can be used because the DSCP value is compatible with IP precedence. Each DSCP maps a per-hop behavior (PHB). Therefore, terminal devices can identify traffic using the DSCP value. A high-quality data transport tunnel that combines the digital channel (such as fiber channel, digital microwave channel, or satellite channel) and the cross multiplex technology.
delay measurement (DM) differentiated services code point (DSCP)
digital data network (DDN)
Issue 03 (2012-07-30)
906
I Glossary
digital modulation
A method that controls the changes in amplitude, phase, and frequency of the carrier based on the changes in the baseband digital signal. In this manner, the information can be transmitted by the carrier.
dual-polarized antenna An antenna intended to simultaneously radiate or receive two independent radio waves orthogonally polarized. E E-Aggr E-LAN E-Line ECC EMC EMI EPL EPLAN EPLD ERPS ESD ETS ETSI EVPL EVPLAN Ethernet See Ethernet aggregation. See Ethernet local area network. See Ethernet line. See embedded control channel. See electromagnetic compatibility. See electromagnetic interference. See Ethernet private line. See Ethernet private LAN service. See erasable programmable logical device. Ethernet ring protection switching electrostatic discharge European Telecommunication Standards See European Telecommunications Standards Institute. See Ethernet virtual private line. See Ethernet virtual private LAN service. A LAN technology that uses Carrier Sense Multiple Access/Collision Detection. The speed of an Ethernet interface can be 10 Mbit/s, 100 Mbit/s, 1000 Mbit/s or 10000 Mbit/ s. An Ethernet network features high reliability and is easy to maintain. A type of Ethernet service that is based on a multipoint-to-point EVC (Ethernet virtual connection). A type of Ethernet service that is based on a point-to-point EVC (Ethernet virtual connection). A type of Ethernet service that is based on a multipoint-to-multipoint EVC (Ethernet virtual connection). A type of Ethernet service provided by SDH, PDH, ATM, or MPLS networks. This service is carried over a dedicated bridge and point-to-multipoint connections. A type of Ethernet service that is provided with dedicated bandwidth and point-to-point connections on an SDH, PDH, ATM, or MPLS server layer network. A type of Ethernet service provided by SDH, PDH, ATM, or MPLS networks. This service is carried over a shared bridge and point-to-multipoint connections. A type of Ethernet service provided by SDH, PDH, ATM, or MPLS networks. This service is carried over a shared bridge and point-to-point connections.
Ethernet aggregation (E-Aggr) Ethernet line (E-Line) Ethernet local area network (E-LAN) Ethernet private LAN service (EPLAN) Ethernet private line (EPL) Ethernet virtual private LAN service (EVPLAN) Ethernet virtual private line (EVPL)
Issue 03 (2012-07-30)
907
I Glossary
European Telecommunications Standards Institute (ETSI) electromagnetic compatibility (EMC)
A standards-setting body in Europe. Also the standards body responsible for GSM.
A condition which prevails when telecommunications equipment is performing its individually designed function in a common electromagnetic environment without causing or suffering unacceptable degradation due to unintentional electromagnetic interference to or from other equipment in the same environment. Any electromagnetic disturbance that interrupts, obstructs, or otherwise degrades or limits the effective performance of electronics/electrical equipment. 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. A mark on a cable, a subrack, or a cabinet for identification. A logical array device which can be used to implement the required functions by programming the array. In addition, a user can modify and program the array repeatedly until the program meets the requirement.
electromagnetic interference (EMI) embedded control channel (ECC) engineering label erasable programmable logical device (EPLD) F FD FDDI FDI FE FEC FFD FFD packet
See frequency diversity. See fiber distributed data interface. See forward defect indication. See fast Ethernet. See forward error correction. fast failure detection A path failure detection method independent from CV. Different from a CV packet, the frequency for generating FFD packets is configurable to satisfy different service requirements. By default, the frequency is 20/s. An FFD packet contains information the same as that in a CV packet. The destination end LSR processes FFD packets in the same way for processing CV packets. See first in first out. See field programmable gate array. File Transfer Protocol Any network that supports transmission rate of 100 Mbit/s. The Fast Ethernet is 10 times faster than 10BaseT, and inherits frame format, MAC addressing scheme, MTU, and so on. Fast Ethernet is extended based on the IEEE802.3 standard, and it uses the following three 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 optical fibers). A standard developed by the American National Standards Institute (ANSI) for highspeed fiber-optic local area networks (LANs). FDDI provides specifications for transmission rates of 100 megabits (100 million bits) per second on networks based on the token ring network.
FIFO FPGA FTP fast Ethernet (FE)
fiber distributed data interface (FDDI)
Issue 03 (2012-07-30)
908
I Glossary
field programmable gate array (FPGA)
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 the PAL, GAL, and EPLD. It not only remedies the defects of customized circuits but also overcomes the disadvantage of the original programmable components in terms of the limited number of gate arrays. A packet generated and traced forward to the sink node of the LSP by the node that first detects defects. It includes fields to indicate the nature of the defect and its location. Its primary purpose is to suppress alarms being raised at affected higher level client LSPs and (in turn) their client layers. A bit error correction technology that adds the correction information to the payload at the transmit end. Based on the correction information, the bit errors generated during transmission are corrected at the receive end. A process of breaking a packet into smaller units when transmitting over a network node that does not support the original size of the packet. A diversity scheme in which two or more microwave frequencies with a certain frequency interval are used to transmit/receive the same signal and selection is then performed between the two signals to ease the impact of fading.
first in first out (FIFO) A stack management mechanism. The first saved data is first read and invoked. forward defect indication (FDI)
forward error correction (FEC) fragmentation frequency diversity (FD)
G GCRA GE GFC GFP GNE GPS GTS GUI Generic Framing Procedure (GFP) Global Positioning System (GPS) gateway gateway network element (GNE) generic cell rate algorithm See gigabit Ethernet. generic flow control See Generic Framing Procedure. See gateway network element. See Global Positioning System. See generic traffic shaping. graphical user interface A framing and encapsulation method which can be applied to any data type. It has been standardized by ITU-T SG15. A global navigation satellite system. It provides reliable positioning, navigation, and timing services to worldwide users. A device that connects two network segments using different protocols. It is used to translate the data in the two network segments. A network element that is used for communication between the NE application layer and the NM application layer.
generic traffic shaping A traffic control measure that proactively adjusts the output speed of the traffic. This is (GTS) to adapt the traffic to network resources that can be provided by the downstream router to avoid packet discarding and congestion.
Issue 03 (2012-07-30)
909
I Glossary
gigabit Ethernet (GE)
A collection of technologies for transmitting Ethernet frames at a rate of a gigabit per second, as defined by the IEEE 802.3z standard. 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 support coaxial cables or other cables. It also supports the channels in the bandwidth mode. If Gigabit 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, causing the length of the links to be sufficient for backbone applications in a building and campus.
H HDLC HQoS HSDPA HSM High Speed Downlink Packet Access (HSDPA) hierarchical quality of service (HQoS) High-Level Data Link Control See hierarchical quality of service. See High Speed Downlink Packet Access. hitless switch mode A modulating-demodulating algorithm put forward in 3GPP R5 to meet the requirement for asymmetric uplink and downlink transmission of data services. It enables the maximum downlink data service rate to reach 14.4 Mbit/s without changing the WCDMA network topology. A type of QoS that controls the traffic of users and performs the scheduling according to the priority of user services. HQoS has an advanced traffic statistics function, and the administrator can monitor the usage of bandwidth of each service. Hence, the bandwidth can be allocated reasonably through traffic analysis. The hybrid transmission of Native E1 and Native Ethernet signals. Hybrid radio supports the AM function.
hybrid radio
I I/O ICMP IDU IEEE IETF IF IGMP IGMP snooping input/output See Internet Control Message Protocol. See indoor unit. See Institute of Electrical and Electronics Engineers. See Internet Engineering Task Force. See intermediate frequency. See Internet Group Management Protocol. A multicast constraint mechanism running on a layer 2 device. This protocol manages and controls the multicast group by listening to and analyzing Internet Group Management Protocol (IGMP) packets between hosts and Layer 3 devices. In this manner, the spread of the multicast data on layer 2 network can be prevented efficiently. See Interior Gateway Protocol. See inverse multiplexing over ATM. Internet Protocol See Internet Protocol version 4.
IGP IMA IP IPv4

Issue 03 (2012-07-30)
I Glossary
IPv6 IS-IS ISDN ISO IST ITU ITU-T IWF Institute of Electrical and Electronics Engineers (IEEE) Interior Gateway Protocol (IGP)
See Internet Protocol version 6. See Intermediate System to Intermediate System. integrated services digital network International Organization for Standardization internal spanning tree See International Telecommunication Union. See International Telecommunication Union-Telecommunication Standardization Sector. Interworking Function A society of engineering and electronics professionals based in the United States but boasting membership from numerous other countries. The IEEE focuses on electrical, electronics, computer engineering, and science-related matters. A routing protocol that is used within an autonomous system. The IGP runs in smallsized and medium-sized networks. The commonly used IGPs are the routing information protocol (RIP), the interior gateway routing protocol (IGRP), the enhanced IGRP (EIGRP), and the open shortest path first (OSPF).
Intermediate System to A protocol used by network devices (routers) to determine the best way to forward Intermediate System datagram or packets through a packet-based network. (IS-IS) International Telecommunication Union (ITU) International Telecommunication UnionTelecommunication Standardization Sector (ITU-T) Internet Control Message Protocol (ICMP) Internet Engineering Task Force (IETF) A United Nations agency, one of the most important and influential recommendation bodies, responsible for recommending standards for telecommunication (ITU-T) and radio networks (ITU-R). An international body that develops worldwide standards for telecommunications technologies. These standards are grouped together in series which are prefixed with a letter indicating the general subject and a number specifying the particular standard. For example, X.25 comes from the "X" series which deals with data networks and open system communications and number "25" deals with packet switched networks. A network-layer (ISO/OSI level 3) Internet protocol that provides error correction and other information relevant to IP packet processing. For example, it can let the IP software on one machine inform another machine about an unreachable destination. See also communications protocol, IP, ISO/OSI reference model, packet (definition 1). A worldwide organization of individuals interested in networking and the Internet. Managed by the Internet Engineering Steering Group (IESG), the IETF is charged with studying technical problems facing the Internet and proposing solutions to the Internet Architecture Board (IAB). The work of the IETF is carried out by various working groups that concentrate on specific topics such as routing and security. The IETF is the publisher of the specifications that led to the TCP/IP protocol standard. One of the TCP/IP protocols for managing the membership of Internet Protocol multicast groups. It is used by IP hosts and adjacent multicast routers to establish and maintain multicast group memberships.
Internet Group Management Protocol (IGMP)
Issue 03 (2012-07-30)
911
I Glossary
Internet Protocol version 4 (IPv4)
The current version of the Internet Protocol (IP). IPv4 utilizes a 32bit address which is assigned to hosts. An address belongs to one of five classes (A, B, C, D, or E) and is written as 4 octets separated by periods and may range from 0.0.0.0 through to 255.255.255.255. Each IPv4 address consists of a network number, an optional subnetwork number, and a host number. The network and subnetwork numbers together are used for routing, and the host number is used to address an individual host within the network or subnetwork. An update version of IPv4, which is designed by the Internet Engineering Task Force (IETF) and is also called IP Next Generation (IPng). It is a new version of the Internet Protocol. The difference between IPv6 and IPv4 is that an IPv4 address has 32 bits while an IPv6 address has 128 bits. The indoor unit of the split-structured radio equipment. It implements accessing, multiplexing/demultiplexing, and intermediate frequency (IF) processing for services.
Internet Protocol version 6 (IPv6)
indoor unit (IDU)
intermediate frequency The transitional frequency between the frequencies of a modulated signal and an RF (IF) signal. inverse multiplexing over ATM (IMA) A technique that involves inverse multiplexing and de-multiplexing of ATM cells in a cyclical fashion among links grouped to form a higher bandwidth logical link whose rate is approximately the sum of the link rates.
L L2VPN LACP LAG LAN LAPS LB LCAS LM LOS LPT LSDB LSP LSP tunnel LSR LTE Layer 2 switching Layer 2 virtual private network See Link Aggregation Control Protocol. See link aggregation group. See local area network. Link Access Protocol-SDH See loopback. See link capacity adjustment scheme. See loss measurement. See loss of signal. link-state pass through link state database See label switched path. An LSP over which traffic is transmitted based on labels that are assigned to FECs on the ingress. The traffic is transparent to the intermediate nodes See label switching router. Long Term Evolution A data forwarding method. In a LAN, a network bridge or 802.3 Ethernet switch transmits and distributes packet data based on the MAC address. Since the MAC address is at the second layer of the OSI model, this data forwarding method is called Layer 2 switching.
Issue 03 (2012-07-30)
912
I Glossary
Link Aggregation Control Protocol (LACP) label switched path (LSP) label switching router (LSR)
A method of bundling a group of physical interfaces together as a logical interface to increase bandwidth and reliability. For related protocols and standards, refer to IEEE 802.3ad. A sequence of hops (R0...Rn) in which a packet travels from R0 to Rn through label switching mechanisms. A label-switched path can be chosen dynamically, based on common routing mechanisms or through configuration. Basic element of an MPLS network. All LSRs support the MPLS protocol. The LSR is composed of two parts: control unit and forwarding unit. The former is responsible for allocating the label, selecting the route, creating the label forwarding table, creating and removing the label switch path; the latter forwards the labels according to groups received in the label forwarding table. A component that generates directional optical waves of narrow wavelengths. The laser light has better coherence than ordinary light. The fiber system takes the semi-conductor laser as the light source. The maximum packet forwarding capacity on a cable. The value of line rate equals the maximum transmission rate capable on a given type of media. linear multiplex section protection
laser
line rate linear MSP
link aggregation group An aggregation that allows one or more links to be aggregated together to form a link (LAG) aggregation group so that a MAC client can treat the link aggregation group as if it were a single link. link capacity adjustment scheme (LCAS) LCAS in the virtual concatenation source and sink adaptation functions provides a control mechanism to hitless increase or decrease the capacity of a link to meet the bandwidth needs of the application. It also provides a means of removing member links that 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 the responsibility of the network and element management systems. A network formed by the computers and workstations within the coverage of a few square kilometers 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 LANs are generally based on switched Ethernet or Wi-Fi technology and running at 1,000 Mbit/ s (that is, 1 Gbit/s). A troubleshooting technique that returns a transmitted signal to its source so that the signal or message can be analyzed for errors. The loopback can be a inloop or outloop.
local area network (LAN)
loopback (LB)
loss measurement (LM) A method used to collect counter values applicable for ingress and egress service frames where the counters maintain a count of transmitted and received data frames between a pair of MEPs. loss of signal (LOS) M MA MAC MADM MBS MD maintenance association See Media Access Control. multiple add/drop multiplexer maximum burst size See maintenance domain. No transitions occurring in the received signal.
Issue 03 (2012-07-30)
913
I Glossary
MD5 MDI MEP MIB MIP MLPPP MP MPLS MPLS L2VPN
See message digest algorithm 5. medium dependent interface maintenance association end point See management information base. maintenance intermediate point Multi-Link Point-to-Point Protocol maintenance point See Multiprotocol Label Switching. A network that provides the Layer 2 VPN service based on an MPLS network. In this case, on a uniform MPLS network, the carrier is able to provide Layer 2 VPNs of different media types, such as ATM, FR, VLAN, Ethernet, and PPP. multiprotocol label switching traffic engineering See multiprotocol label switching virtual private network. See multiprotocol label switching transport profile. multiplex section See multiplex section protection. See Multiple Spanning Tree region. See multiple spanning tree instance. See Multiple Spanning Tree Protocol. See mean time between failures. See mean time to repair. See maximum transmission unit. A protocol at the media access control sublayer. The protocol is at the lower part of the data link layer in the OSI model and is mainly responsible for controlling and connecting the physical media at the physical layer. When transmitting data, the MAC protocol checks whether to be able to transmit data. If the data can be transmitted, certain control information is added to the data, and then the data and the control information are transmitted in a specified format to the physical layer. When receiving data, the MAC protocol checks whether the information is correct and whether the data is transmitted correctly. If the information is correct and the data is transmitted correctly, the control information is removed from the data and then the data is transmitted to the LLC layer. A protocol that can be used in a loop network. Using an algorithm, the MSTP blocks redundant paths so that the loop network can be trimmed as a tree network. In this case, the proliferation and endless cycling of packets is avoided in the loop network. The protocol that introduces the mapping between VLANs and multiple spanning trees. This solves the problem that data cannot be normally forwarded in a VLAN because in STP/ RSTP, only one spanning tree corresponds to all the VLANs. A region that consists of switches that support the MSTP in the LAN and links among them. Switches physically and directly connected and configured with the same MST region attributes belong to the same MST region.
MPLS TE MPLS VPN MPLS-TP MS MSP MST region MSTI MSTP MTBF MTTR MTU Media Access Control (MAC)
Multiple Spanning Tree Protocol (MSTP)
Multiple Spanning Tree region (MST region)
Issue 03 (2012-07-30)
914
I Glossary
Multiprotocol Label Switching (MPLS)
A technology that uses short tags of fixed length to encapsulate packets in different link layers, and provides connection-oriented switching for the network layer on the basis of IP routing and control protocols. It improves the cost performance and expandability of networks, and is beneficial to routing. The network or the part of the network for which connectivity is managed by connectivity fault management (CFM). The devices in a maintenance domain are managed by a single Internet service provider (ISP).
maintenance domain (MD)
management A type of database used for managing the devices in a communications network. It information base (MIB) comprises a collection of objects in a (virtual) database used to manage entities (such as routers and switches) in a network. maximum transmission The largest packet of data that can be transmitted on a network. MTU size varies, unit (MTU) depending on the network576 bytes on X.25 networks, for example, 1500 bytes on Ethernet, and 17,914 bytes on 16 Mbit/s token ring. Responsibility for determining the size of the MTU lies with the link layer of the network. When packets are transmitted across networks, the path MTU, or PMTU, represents the smallest packet size (the one that all networks can transmit without breaking up the packet) among the networks involved. mean time between failures (MTBF) mean time to repair (MTTR) message digest algorithm 5 (MD5) The average time between consecutive failures of a piece of equipment. It is a measure of the reliability of the system. The average time that a device will take to recover from a failure. A hash function that is used in a variety of security applications to check message integrity. MD5 processes a variable-length message into a fixed-length output of 128 bits. It breaks up an input message into 512-bit blocks (sixteen 32-bit little-endian integers). After a series of processing, the output consists of four 32-bit words, which are then cascaded into a 128-bit hash number. A process of transmitting data packets from one source to many destinations. The destination address of the multicast packet uses Class D address, that is, the IP address ranges from 224.0.0.0 to 239.255.255.255. Each multicast address represents a multicast group rather than a host.
multicast
multiple spanning tree A type of spanning trees calculated by MSTP within an MST Region, to provide a simply instance (MSTI) and fully connected active topology for frames classified as belonging to a VLAN that is mapped to the MSTI by the MST Configuration. A VLAN cannot be assigned to multiple MSTIs. multiplex section protection (MSP) multiprotocol label switching transport profile (MPLS-TP) multiprotocol label switching virtual private network (MPLS VPN) A function, which is performed to provide capability for switching a signal between and including two multiplex section termination (MST) functions, from a "working" to a "protection" channel. A packet transport technology proposed by IETF that combines the packet experience of MPLS with the operational experience of transport networks. An Internet Protocol (IP) virtual private network (VPN) based on the multiprotocol label switching (MPLS) technology. It applies the MPLS technology for network routers and switches, simplifies the routing mode of core routers, and combines traditional routing technology and label switching technology. It can be used to construct the broadband Intranet and Extranet to meet various service requirements.
N
I Glossary
N+1 protection NE NE Explorer
A radio link protection system composed of N working channels and one protection channel. network element The main operation interface, of the network management system, which is used to manage the telecommunication equipment. In the NE Explorer, the user can query, manage and maintain the NE, boards, and ports on a per-NE basis. network-to-network interface network provider edge See network service access point. non-stop forwarding
NNI NPE NSAP NSF
network service access A network address defined by ISO, through which entities on the network layer can point (NSAP) access OSI network services. network storm A phenomenon that occurs during data communication. To be specific, mass broadcast packets are transmitted in a short time; the network is congested; transmission quality and availability of the network decrease rapidly. The network storm is caused by network connection or configuration problems. 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 for one frame of the device. See non-gateway network element. A network element that communicates with the NM application layer through the gateway NE application layer.
node
non-GNE non-gateway network element (non-GNE) O O&M OAM OAMPDU ODF ODU OSI OSPF Open Shortest Path First (OSPF)
operation and maintenance See operation, administration and maintenance. operation, administration and maintenance protocol data unit optical distribution frame See outdoor unit. See open systems interconnection. See Open Shortest Path First. A link-state, hierarchical interior gateway protocol (IGP) for network routing. Dijkstra's algorithm is used to calculate the shortest path tree. It uses cost as its routing metric. A link state database is constructed with the network topology which is identical on all routers in the area. A framework of ISO standards for communication between different systems made by different vendors, in which the communications process is organized into seven different categories 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 source and destination, and layers 3 through 1 deal with network functions.
open systems interconnection (OSI)
Issue 03 (2012-07-30)
916
I Glossary
operation, administration and maintenance (OAM)
A group of network support functions that monitor and sustain segment operation, support 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 an operational state, and support activities required to provide the services of a subscriber access network to users/subscribers. A channel that provides voice communication between operation engineers or maintenance engineers of different stations. The outdoor unit of the split-structured radio equipment. It implements frequency conversion and amplification for radio frequency (RF) signals.
orderwire outdoor unit (ODU)
P P2P PBS PCB PDH PDU PE PHB PIR PLA PLL PPP PRBS PRI PSN PSTN PTN PTP PTP clock PVP PW PWE3 Precision Time Protocol clock (PTP clock) packet switched network (PSN) paired slots See point-to-point service. See peak burst size. See printed circuit board. See plesiochronous digital hierarchy. protocol data unit See provider edge. See per-hop behavior. peak information rate See physical link aggregation. See phase-locked loop. Point-to-Point Protocol See pseudo random binary sequence. primary rate interface See packet switched network. See public switched telephone network. packet transport network Precision Time Protocol See Precision Time Protocol clock. See permanent virtual path. See pseudo wire. See pseudo wire emulation edge-to-edge. A type of high-decision clock defined by the IEEE 1588 V2 standard. The IEEE 1588 V2 standard specifies the precision time protocol (PTP) in a measurement and control system. The PTP protocol ensures clock synchronization precise to sub-microseconds. A telecommunications network that works in packet switching mode. Two slots of which the overheads can be passed through by using the bus on the backplane.
Issue 03 (2012-07-30)
917
I Glossary
peak burst size (PBS)
A parameter that is used to define the capacity of token bucket P, that is, the maximum burst IP packet size when the information is transferred at the peak information rate. This parameter must be larger than 0. It is recommended that PBS should be not less than the maximum length of the IP packet that might be forwarded. See also CIR, CBS, and PIR. IETF Diff-Serv workgroup defines forwarding behaviors of network nodes as per-hop behaviors (PHB), such as, traffic scheduling and policing. A device in the network should select the proper PHB behaviors, based on the value of DSCP. At present, the IETF defines four types of PHB. They are class selector (CS), expedited forwarding (EF), assured forwarding (AF), and best-effort (BE).
per-hop behavior (PHB)
permanent virtual path Virtual path that consists of PVCs. (PVP) phase-locked loop (PLL) A circuit that consists essentially of a phase detector which compares the frequency of a voltage-controlled oscillator with that of an incoming carrier signal or referencefrequency generator; the output of the phase detector, after passing through a loop filter, is fed back to the voltage-controlled oscillator to keep it exactly in phase with the incoming or reference frequency. Being a technology providing load balancing based on physical layer bandwidths, physical link aggregation (PLA) combines Ethernet transmission paths in several Integrated IP radio links into a logical Ethernet link for higher Ethernet bandwidth and Ethernet transmission reliability. A multiplexing scheme of bit stuffing and byte interleaving. It multiplexes the minimum rate 64 kit/s into the 2 Mbit/s, 34 Mbit/s, 140 Mbit/s, and 565 Mbit/s rates. A service between two terminal users. In P2P services, senders and recipients are terminal users. A kind of electromagnetic wave, the direction of whose electric field vector is fixed or rotates regularly. Specifically, if the electric field vector of the electromagnetic wave is perpendicular to the plane of horizon, this electromagnetic wave is called vertically polarized wave; if the electric field vector of the electromagnetic wave is parallel to the plane of horizon, this electromagnetic wave is called horizontal polarized wave; if the tip of the electric field vector, at a fixed point in space, describes a circle, this electromagnetic wave is called circularly polarized wave. A board used to mechanically support and electrically connect electronic components using conductive pathways, tracks, or traces, etched from copper sheets laminated onto a non-conductive substrate. A device that is located in the backbone network of the MPLS VPN structure. A PE is responsible for managing VPN users, establishing LSPs between PEs, and exchanging routing information between sites of the same VPN. A PE performs the mapping and forwarding of packets between the private network and the public channel. A PE can be a UPE, an SPE, or an NPE.
physical link aggregation (PLA)
plesiochronous digital hierarchy (PDH) point-to-point service (P2P) polarization
printed circuit board (PCB) provider edge (PE)
pseudo random binary A sequence that is random in a sense that the value of an element is independent of the sequence (PRBS) values of any of the other elements, similar to real random sequences. pseudo wire (PW) An emulated connection between two PEs for transmitting frames. The PW is established and maintained by PEs through signaling protocols. The status information of a PW is maintained by the two end PEs of a PW.
Issue 03 (2012-07-30)
918
I Glossary
pseudo wire emulation An end-to-end Layer 2 transmission technology. It emulates the essential attributes of a edge-to-edge (PWE3) telecommunication service such as ATM, FR or Ethernet in a packet switched network (PSN). PWE3 also emulates the essential attributes of low speed time division multiplexing (TDM) circuit and SONET/SDH. The simulation approximates to the real situation. public switched telephone network (PSTN) Q QAM QPSK QinQ See quadrature amplitude modulation. See quadrature phase shift keying. A layer 2 tunnel protocol based on IEEE 802.1Q encapsulation. It add a public VLAN tag to a frame with a private VLAN tag to allow the frame with double VLAN tags to be transmitted over the service provider's backbone network based on the public VLAN tag. This provides a layer 2 VPN tunnel for customers and enables transparent transmission of packets over private VLANs. See quality of service. Both an analog and a digital modulation scheme. It conveys two analog message signals, or two digital bit streams, by changing (modulating) the amplitudes of two carrier waves, using the amplitude-shift keying (ASK) digital modulation scheme or amplitude modulation (AM) analog modulation scheme. These two waves, usually sinusoids, are out of phase with each other by 90 and are thus called quadrature carriers or quadrature components hence the name of the scheme. A telecommunications network established to perform telephone services for the public subscribers. Sometimes it is called POTS.
QoS quadrature amplitude modulation (QAM)
quadrature phase shift A modulation method of data transmission through the conversion or modulation and keying (QPSK) the phase determination of the reference signals (carrier). It is also called the fourth period or 4-phase PSK or 4-PSK. QPSK uses four dots in the star diagram. The four dots are evenly distributed on a circle. On these phases, each QPSK character can perform twobit coding and display the codes in Gray code on graph with the minimum BER. quality of service (QoS) 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 loss ratio, bit error ratio, and signal-to-noise ratio. It functions to measure the quality of the transmission system and the effectiveness of the services, as well as the capability of a service provider to meet the demands of users. R RADIUS RADIUS accounting RDI RED REI RF RFC
Issue 03 (2012-07-30)
See Remote Authentication Dial-In User Service. An accounting mode in which the BRAS sends the accounting packets to the RADIUS server. Then the RADIUS server performs accounting. remote defect indication See random early detection. remote error indication See radio frequency. See Request For Comments.
I Glossary
RMEP RMON RNC RSL RSSI RSTP RSVP RTN RTSP Rapid Spanning Tree Protocol (RSTP)
remote maintenance association end point remote network monitoring See radio network controller. See received signal level. See received signal strength indicator. See Rapid Spanning Tree Protocol. See Resource Reservation Protocol. radio transmission node Real-Time Streaming Protocol An evolution of the Spanning Tree Protocol, providing for faster spanning tree convergence after a topology change. The RSTP protocol is backward compatible with the STP protocol.
Remote Authentication A security service that authenticates and authorizes dial-up users and is a centralized Dial-In User Service access control mechanism. RADIUS uses the User Datagram Protocol (UDP) as its (RADIUS) transmission protocol to ensure real-time quality. RADIUS also supports the retransmission and multi-server mechanisms to ensure good reliability. Request For Comments A document in which a standard, a protocol, or other information pertaining to the (RFC) operation of the Internet is published. The RFC is actually issued, under the control of the IAB, after discussion and serves as the standard. RFCs can be obtained from sources such as InterNIC. Resource Reservation Protocol (RSVP) RoHS radio frequency (RF) A network control protocol like Internet Control Message Protocol (ICMP) and designed for Integrated Service and used to reserve resources on every node along a path. RSVP operates on the transport layer; however, RSVP does not transport application data. restriction of the use of certain hazardous substances A type of electric current in the wireless network using AC antennas to create an electromagnetic 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 AC with frequency higher than 10 kHz is called high-frequency current. RF can be classified into such high-frequency current. A piece of equipment in the RNS which is in charge of controlling the use and the integrity of the radio resources.
radio network controller (RNC)
random early detection A packet loss algorithm used in congestion avoidance. It discards the packet according (RED) to the specified higher limit and lower limit of a queue so that global TCP synchronization resulting from traditional tail drop can be prevented. real-time variable bit rate (rt-VBR) A parameter intended for real-time applications, such as compressed voice over IP (VoIP) and video conferencing. The rt-VBR is characterized by a peak cell rate (PCR), sustained cell rate (SCR), and maximum burst size (MBS). You can expect the source device to transmit in bursts and at a rate that varies with time. The signal level at a receiver input terminal.
received signal level (RSL)
received signal strength The received wide band power, including thermal noise and noise generated in the indicator (RSSI) receiver, within the bandwidth defined by the receiver pulse shaping filter, for TDD within a specified timeslot. The reference point for the measurement shall be the antenna
Issue 03 (2012-07-30)
920
I Glossary
receiver sensitivity regeneration route router
The minimum acceptable value of average received power at point R to achieve a 1 x 10-12 BER (The FEC is open). The process of receiving and reconstructing a digital signal so that the amplitudes, waveforms and timing of its signal elements are constrained within specified limits. 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. A device on the network layer that selects routes in the network. The router selects the optimal route according to the destination address of the received packet through a network and forwards the packet to the next router. The last router is responsible for sending the packet to the destination host. Can be used to connect a LAN to a LAN, a WAN to a WAN, or a LAN to the Internet. See real-time variable bit rate.
rt-VBR S SAI SAToP SCSI SD SDH SEC SES SETS SF SFP SLA SNCP SNMP SNR SRN SSL SSM STM STM-1 STM-4 STM-N STP Secure Sockets Layer (SSL)
service area identifier Structure-Agnostic Time Division Multiplexing over Packet small computer system interface See space diversity. See synchronous digital hierarchy. security screening severely errored second SDH equipment timing source See signal fail. small form-factor pluggable See service level agreement. subnetwork connection protection See Simple Network Management Protocol. See signal-to-noise ratio. serial number See Secure Sockets Layer. See Synchronization Status Message. See synchronous transport module. See Synchronous Transport Module level 1. Synchronous Transport Module level 4 Synchronous Transport Module level N Spanning Tree Protocol A security protocol that works at a socket level. This layer exists between the TCP layer and the application layer to encrypt/decode data and authenticate concerned entities.
Issue 03 (2012-07-30)
921
I Glossary
Simple Network Management Protocol (SNMP)
A network management protocol of TCP/IP. It enables remote users to view and modify the management information of a network element. This protocol ensures the transmission of management information between any two points. The polling mechanism is adopted to provide basic function sets. According to SNMP, agents, which can be hardware as well as software, can monitor the activities of various devices on the network and report these activities to the network console workstation. Control information about each device is maintained by a management information block.
Synchronization Status 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 clock Message (SSM) information through this message. Then the nodes can perform proper operations on their clocks, such as tracing, switching, or converting to holdoff, and forward the synchronization information to downstream nodes. Synchronous Synchronous transfer mode at 155 Mbit/s. Transport Module level 1 (STM-1) service level agreement A service agreement between a customer and a service provider. SLA specifies the (SLA) service level for a customer. The customer can be a user organization (source domain) or another differentiated services domain (upstream domain). An SLA may include traffic conditioning rules which constitute a traffic conditioning agreement as a whole or partially. signal fail (SF) signal-to-noise ratio (SNR) A signal indicating that associated data has failed in the sense that a near-end defect condition (non-degrade defect) is active. The ratio of the amplitude of the desired signal to the amplitude of noise signals at a given point in time. SNR is expressed as 10 times the logarithm of the power ratio and is usually expressed in dB (Decibel).
single-ended switching A protection operation method that takes switching action only at the affected end of the protected entity (for example, trail, subnetwork connection), in the case of a unidirectional failure. single-polarized antenna space diversity (SD) An antenna intended to radiate or receive radio waves with only one specified polarization. A diversity scheme that enables two or more antennas separated by a specific distance to transmit/receive the same signal and selection is then performed between the two signals to ease the impact of fading. Currently, only receive SD is used. The technique used by the IP protocol to determine which network segment packets are destined for. The subnet mask is a binary pattern that is stored in the client machine, server or router matches with the IP address. A transmission scheme that follows ITU-T G.707, G.708, and G.709. It defines the transmission features of digital signals such as frame structure, multiplexing mode, transmission rate level, and interface code. SDH is an important part of ISDN and BISDN. It interleaves the bytes of low-speed signals to multiplex the signals to high-speed counterparts, and the line coding of scrambling is used only for signals. SDH is suitable for the fiber communication system with high speed and a large capacity since it uses synchronous multiplexing and flexible mapping structure.
subnet mask
synchronous digital hierarchy (SDH)
Issue 03 (2012-07-30)
922
I Glossary
synchronous transport An information structure used to support section layer connections in the SDH. It consists module (STM) of information payload and Section Overhead (SOH) information fields organized in a block frame structure which repeats every 125. The information is suitably conditioned for serial transmission on the selected media at a rate which is synchronized to the network. A basic STM is defined at 155 520 kbit/s. This is termed STM-1. Higher capacity STMs are formed at rates equivalent to N times this basic rate. STM capacities for N = 4, N = 16 and N = 64 are defined; higher values are under consideration. T T1 TCI TCP TCP/IP TD-SCDMA TDD TDM TDMA TE TEDB TIM TMN TOS TTL TUG Telnet A North American standard for high-speed data transmission at 1.544Mbps. It provides 24 x 64 kbit/s channels. tag control information See Transmission Control Protocol. Transmission Control Protocol/Internet Protocol See Time Division-Synchronous Code Division Multiple Access. time division duplex See time division multiplexing. See Time Division Multiple Access. See traffic engineering. See traffic engineering database. trace identifier mismatch See telecommunications management network. test operation system See time to live. tributary unit group A standard terminal emulation protocol in the TCP/IP protocol stack. Telnet allows users to log in to remote systems and use resources as if they were connected to a local system. Telnet is defined in RFC 854.
Time Division Multiple An approach used for allocating a single channel among many users, by dividing the Access (TDMA) channel into different timeslots during which each user has access to the medium. Time DivisionSynchronous Code Division Multiple Access (TD-SCDMA) A 3G mobile communications standard found in UMTS mobile telecommunications networks in China as an alternative to W-CDMA. TD-SCDMA integrates technologies of CDMA, TDMA, and FDMA, and makes use of technologies including intelligent antenna, joint detection, low chip rate (LCR), and adaptive power control. With the flexibility of service processing, a TD-SCDMA network can connect to other networks through the RNC. The protocol within TCP/IP that governs the breakup of data messages into packets to be sent using Internet Protocol (IP), and the reassembly and verification of the complete messages from packets received by IP. A connection-oriented, reliable protocol (reliable in the sense of ensuring error-free delivery), TCP corresponds to the transport layer in the ISO/OSI reference model.
Transmission Control Protocol (TCP)
Issue 03 (2012-07-30)
923
I Glossary
tail drop
A congestion management mechanism, in which packets arrive later are discarded when the queue is full. This policy of discarding packets may result in network-wide synchronization due to the TCP slow startup mechanism. A concept borrowed from geometry. Two tangent rings have a common node between them. The common node often leads to single-point failures. A protocol model defined by ITU-T for managing open systems in a communications network. An architecture for management, including planning, provisioning, installation, maintenance, operation and administration of telecommunications equipment, networks and services. 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 time slots in a certain order, forming multiple multiplexing digital signals to be transmitted over one channel. 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 the network. Each router in the network decrements the TTL value when the packet arrives, and discards any packet if the TTL counter reaches zero. See two rate three color marker.
tangent ring telecommunications management network (TMN) time division multiplexing (TDM)
time to live (TTL)
trTCM
traffic engineering (TE) A technology that is used to dynamically monitor the traffic of the network and the load of the network elements, to adjust in real time the parameters such as traffic management parameters, route parameters and resource restriction parameters, and to optimize the utilization of network resources. The purpose is to prevent the congestion caused by unbalanced loads. traffic engineering database (TEDB) tributary loopback A type of database that every router generates after collecting the information about TE of every links in its area. TEDB is the base of forming the dynamic TE path in the MPLS TE network. A fault can be located for each service path by performing loopback to each path of the tributary board. There are three kinds of loopback modes: no loopback, outloop, and inloop. 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 tunnel ensures secure and transparent transmission of VPN information. In most cases, a tunnel is an MPLS tunnel. An algorithm that meters an IP packet stream and marks its packets based on two rates, Peak Information Rate (PIR) and Committed Information Rate (CIR), and their associated burst sizes to be either green, yellow, or red. A packet is marked red if it exceeds the PIR. Otherwise it is marked either yellow or green depending on whether it exceeds or does not exceed the CIR.
tunnel
two rate three color marker (trTCM)
U UART UAS UBR UBR+ UDP

Issue 03 (2012-07-30)
universal asynchronous receiver/transmitter unavailable second unspecified bit rate Unspecified Bit Rate Plus See User Datagram Protocol.
I Glossary
UI UNI UPC User Datagram Protocol (UDP)
user interface See user-to-network interface. See usage parameter control. A TCP/IP standard protocol that allows an application program on one device to send a datagram to an application program on another. User Datagram Protocol (UDP) uses IP to deliver datagram. UDP provides application programs with the unreliable connectionless packet delivery service. There is a possibility that UDP messages will be lost, duplicated, delayed, or delivered out of order. The destination device does not confirm whether a data packet is received. The process of sending data from a source to a single recipient. During communications, UPC is implemented to monitor the actual traffic on each virtual circuit that is input to the network. Once the specified parameter is exceeded, measures will be taken to control. NPC is similar to UPC in function. The difference is that the incoming traffic monitoring function is divided into UPC and NPC according to their positions. UPC locates at the user/network interface, while NPC at the network interface. The interface between user equipment and private or public network equipment (for example, ATM switches).
unicast usage parameter control (UPC)
user-to-network interface (UNI) V V-NNI V-UNI VB VBR VC VCC VCCV VCG VCI VCTRUNK VLAN VPI VPLS VPN VSWR VoIP
virtual network-network interface See virtual user-network interface. virtual bridge See variable bit rate. See virtual container. See virtual channel connection. virtual circuit connectivity verification See virtual concatenation group. virtual channel identifier A virtual concatenation group applied in data service mapping, also called the internal port of a data service processing board. virtual local area network See virtual path identifier. virtual private LAN segment virtual private network voltage standing wave ratio See voice over IP.
variable bit rate (VBR) One of the traffic classes used by ATM (Asynchronous Transfer Mode). Unlike a permanent CBR (Constant Bit Rate) channel, a VBR data stream varies in bandwidth and is better suited to non real time transfers than to real-time streams such as voice calls.
Issue 03 (2012-07-30)
925
I Glossary
virtual channel connection (VCC) virtual circuit
A VC logical trail that carries data between two end points in an ATM network. A pointto-multipoint VCC is a set of ATM virtual connections between two or multiple end points. A channel or circuit established between two points on a data communications network with packet switching. Virtual circuits can be permanent virtual circuits (PVCs) or switched virtual circuits (SVCs) . A group of co-located member trail termination functions that are connected to the same virtual concatenation link The information structure used to support path layer connections in the SDH. It consists of information payload and path overhead (POH) information fields organized in a block frame structure which repeats every 125 or 500 s. The field in the Asynchronous Transfer Mode (ATM) cell header that identifies to which virtual path the cell belongs. A virtual user-network interface, works as an action point to perform service classification and traffic control in HQoS. An IP telephony term for a set of facilities used to manage the delivery of voice information over the Internet. VoIP involves sending voice information in a digital form in discrete packets rather than by using the traditional circuit-committed protocols of the public switched telephone network (PSTN).
virtual concatenation group (VCG) virtual container (VC)
virtual path identifier (VPI) virtual user-network interface (V-UNI) voice over IP (VoIP)
W WAN WCDMA WDM WEEE WFQ WRED WRR WTR Web LCT Wi-Fi Wideband Code Division Multiple Access (WCDMA) Wireless Fidelity (WiFi) wait to restore (WTR) weighted fair queuing (WFQ) See wide area network. See Wideband Code Division Multiple Access. wavelength division multiplexing waste electrical and electronic equipment See weighted fair queuing. See weighted random early detection. weighted round robin See wait to restore. The local maintenance terminal of a transport network, which is located at the NE management layer of the transport network. See Wireless Fidelity. A standard defined by the ITU-T for the third-generation wireless technology derived from the Code Division Multiple Access (CDMA) technology. A short-distant wireless transmission technology. It enables wireless access to the Internet within a range of hundreds of feet wide. The number of minutes to wait before services are switched back to the working line. A fair queue scheduling algorithm based on bandwidth allocation weights. This scheduling algorithm allocates the total bandwidth of an interface to queues, according to their weights and schedules the queues cyclically. In this manner, packets of all priority queues can be scheduled.
Issue 03 (2012-07-30)
926
I Glossary
weighted random early A packet loss algorithm used for congestion avoidance. It can prevent the global TCP detection (WRED) synchronization caused by traditional tail-drop. WRED is favorable for the high-priority packet when calculating the packet loss ratio. wide area network (WAN) winding pipe X XPIC See cross polarization interference cancellation. A network composed of computers which are far away from each other which are physically connected through specific protocols. WAN covers a broad area, such as a province, a state or even a country. A tool for fiber routing, which acts as the corrugated pipe.
Issue 03 (2012-07-30)
927

RTN 950 V100R005C00 Maintenance Guide 03

Încărcat de

Informații document

Descriere originală:

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

RTN 950 V100R005C00 Maintenance Guide 03

Încărcat de

Drepturi de autor:

Formate disponibile

OptiX RTN 950 Radio Transmission System V100R005C00

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

OptiX RTN 950 Radio Transmission System Maintenance Guide

About This Document

About This Document

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

OptiX RTN 950 Radio Transmission System Maintenance Guide

About This Document

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

OptiX RTN 950 Radio Transmission System Maintenance Guide

About This Document

Updates in Issue 03 (2012-07-30) Based on Product Version V100R005C00

Updates in Issue 02 (2012-06-30) Based on Product Version V100R005C00

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

OptiX RTN 950 Radio Transmission System Maintenance Guide

About This Document

Updates in Issue 01 (2012-04-30) Based on Product Version V100R005C00

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

OptiX RTN 950 Radio Transmission System Maintenance Guide

2 Notices for High-Risk Operations...........................................................................................19

3 Routine Maintenance..................................................................................................................26 4 Emergency Maintenance............................................................................................................28

OptiX RTN 950 Radio Transmission System Maintenance Guide

7 Database Backup and Restoration.........................................................................................131

OptiX RTN 950 Radio Transmission System Maintenance Guide

OptiX RTN 950 Radio Transmission System Maintenance Guide

OptiX RTN 950 Radio Transmission System Maintenance Guide

OptiX RTN 950 Radio Transmission System Maintenance Guide

OptiX RTN 950 Radio Transmission System Maintenance Guide

OptiX RTN 950 Radio Transmission System Maintenance Guide

OptiX RTN 950 Radio Transmission System Maintenance Guide

OptiX RTN 950 Radio Transmission System Maintenance Guide

OptiX RTN 950 Radio Transmission System Maintenance Guide

OptiX RTN 950 Radio Transmission System Maintenance Guide

OptiX RTN 950 Radio Transmission System Maintenance Guide

B Abnormal Event Reference.....................................................................................................726

OptiX RTN 950 Radio Transmission System Maintenance Guide

C Performance Event Reference................................................................................................742

OptiX RTN 950 Radio Transmission System Maintenance Guide

D RMON Event Reference..........................................................................................................812

OptiX RTN 950 Radio Transmission System Maintenance Guide

F Performance Event Management...........................................................................................873

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

OptiX RTN 950 Radio Transmission System Maintenance Guide

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

OptiX RTN 950 Radio Transmission System Maintenance Guide

1.1 General Safety Precautions

All Safety Precautions

Local Laws and Regulations

Basic Installation Requirements

OptiX RTN 950 Radio Transmission System Maintenance Guide

The preceding requirements apply to wireless fixed station terminals.

1.2 Warning and Safety Symbols

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

OptiX RTN 950 Radio Transmission System Maintenance Guide

DON'T TOUCH THE FAN LEAVES BEFORE THEY SLOW DOWN !

1.3 Electrical Safety

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

OptiX RTN 950 Radio Transmission System Maintenance Guide

High Leakage Current

Device with Power On